
From jason_livingood@cable.comcast.com  Fri Oct  1 11:29:19 2010
Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA12A3A6C80 for <v6ops@core3.amsl.com>; Fri,  1 Oct 2010 11:29:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.136
X-Spam-Level: 
X-Spam-Status: No, score=-107.136 tagged_above=-999 required=5 tests=[AWL=1.327, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wlTNviCWqbBx for <v6ops@core3.amsl.com>; Fri,  1 Oct 2010 11:29:19 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 622073A6C08 for <v6ops@ietf.org>; Fri,  1 Oct 2010 11:29:18 -0700 (PDT)
Received: from ([24.40.55.40]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.95406954; Fri, 01 Oct 2010 14:28:21 -0400
Received: from PACDCEXMB06.cable.comcast.com ([fe80::6134:ea50:286a:c0]) by pacdcexhub03.cable.comcast.com ([fe80::d1dd:b302:b617:3755%12]) with mapi id 14.01.0218.012; Fri, 1 Oct 2010 14:28:21 -0400
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: Soliciting feedback on draft-livingood-dns-whitelisting-implications
Thread-Index: AQHLYZZsVCE0+zqIz0+l2xjka9peKA==
Date: Fri, 1 Oct 2010 18:28:20 +0000
Message-ID: <C8CB9E88.5599%jason_livingood@cable.comcast.com>
In-Reply-To: <C8BFD127.F082%victor.kuarsingh@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.0.0.100802
x-originating-ip: [147.191.125.14]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1E7007A3DAD36043AE9EC48113C8EFDC@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [v6ops] Soliciting feedback on draft-livingood-dns-whitelisting-implications
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Oct 2010 18:29:20 -0000

Hi -

I am soliciting feeback on this new draft, available at http://tools.ietf.o=
rg/html/draft-livingood-dns-whitelisting-implications. In particular, I am =
looking for more text to add in the justifications / rationale for this pra=
ctice in an attempt to objectively examine the issue from many sides.  This=
 is only a first draft of course.

Regards
Jason Livingood

From fred@cisco.com  Fri Oct  1 11:34:47 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5737C3A6DD4 for <v6ops@core3.amsl.com>; Fri,  1 Oct 2010 11:34:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.213
X-Spam-Level: 
X-Spam-Status: No, score=-110.213 tagged_above=-999 required=5 tests=[AWL=-0.214, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YqHvTD-q+bw3 for <v6ops@core3.amsl.com>; Fri,  1 Oct 2010 11:34:45 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 939163A6D51 for <v6ops@ietf.org>; Fri,  1 Oct 2010 11:34:45 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEACrHpUyrRN+K/2dsb2JhbACiOHGsIpxBhUQEhFGFa4MC
X-IronPort-AV: E=Sophos;i="4.57,267,1283731200"; d="scan'208";a="194759271"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-4.cisco.com with ESMTP; 01 Oct 2010 18:35:34 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o91IZQcp000849; Fri, 1 Oct 2010 18:35:29 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Fri, 01 Oct 2010 11:35:34 -0700
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Fri, 01 Oct 2010 11:35:34 -0700
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <20101001161955.7BE263A6CEF@core3.amsl.com>
Date: Fri, 1 Oct 2010 11:35:19 -0700
Message-Id: <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com>
References: <20101001161955.7BE263A6CEF@core3.amsl.com>
To: IPv6 Operations <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: v6ops-ads@tools.ietf.org
Subject: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: V6ops Chairs <v6ops-chairs@tools.ietf.org>
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Oct 2010 18:34:47 -0000

On Oct 1, 2010, at 9:19 AM, IETF Secretariat wrote:
> Dear Fred Baker,
>=20
> The sessions that you have requested have been scheduled.
> Below is the scheduled session information followed by=20
> the information of sessions that you have requested.
>=20
> V6OPS Session 1 (2.5 hours)
> Wednesday, Morning Session I 0900-1130
> Room Name: Valley Ballroom B
> ----------------------------------------------
> V6OPS Session 2 (2.5 hours)
> Friday, Afternoon Session I 1300-1500
> Room Name: Valley Ballroom A
> ----------------------------------------------


On Oct 1, 2010, at 11:07 AM, IETF Agenda wrote:
> The DRAFT agenda is ready for viewing.  Please note the cutoff date =
for
> requests to reschedule Working Group and BOF meetings is October 11, =
2010
> 17:00 PT.  The final agenda will be published on October 15, 2010.
>=20
> https://datatracker.ietf.org/meeting/79/agenda.html
> https://datatracker.ietf.org/meeting/79/agenda.txt
>=20
> http://www.ietf.org/meeting/79/index.html
>=20
>=20
> Thanks,
> Wanda
>=20
> Only 36 days until the Beijing IETF!
> Online registration for the IETF meeting is at:
> http://www.ietf.org/meetings/79/


Joel, Kurtis, and I are starting to assemble the IETF 79 Agenda. What I =
have at this instant is at =
http://www.ietf.org/proceedings/79/agenda/v6ops.html. I requested two =
morning (2.5 hours) slots; I got one morning slot and "Friday afternoon =
until we stop talking" - nominally two hours, but Wanda tells me she has =
noted that we will likely run over. It looks like we will have a pretty =
full agenda; between the -v4v6tran- and -v6ops- work, we have a total of =
18 drafts. =20

Anything I have missed - drop us a note at v6ops-chairs@tools.ietf.org =
if you would. The chairs have not yet discussed this in detail amongst =
ourselves yet, so I'm not sure which day will get which topic, and there =
are other reorganizations that could happen. If folks have strong =
opinions, that too would be interesting to know.

This assumes, btw, that the WGLCs that we have been running mean that we =
don't need to discuss those drafts. Besides the drafts on the agenda, =
our status is:

To complete WGLC before IETF 79
	draft-arkko-ipv6-transition-guidelines    (waiting new draft)
	draft-ietf-v6ops-tunnel-security-concerns (waiting document =
writeup)
	draft-ietf-v6ops-incremental-cgn          (just completed WGLC)
	draft-ietf-v6ops-tunnel-loops             (in WGLC)
	draft-ietf-v6ops-v6-in-mobile-networks    (October 11-24)
	draft-ietf-v6ops-3177bis-48boundary       (Oct 24-Nov 7)

In IESG discussion:
	draft-gundavelli-v6ops-l2-unicast-04=09
	draft-ietf-v6ops-cpe-simple-security-14=09
	draft-ietf-v6ops-ra-guard-08
	draft-ietf-v6ops-rogue-ra-01 (Needs an updated draft from Tim)

RFC Editor Queue	=09
	draft-ietf-v6ops-ipv6-cpe-router-07
	draft-ietf-v6ops-isp-scenarios-00
	draft-thaler-v6ops-teredo-extensions-08

Dead?
	draft-sarikaya-v6ops-prefix-delegation-01	=09

Recent RFCs:

http://www.ietf.org/rfc/rfc5963.txt
5963 IPv6 Deployment in Internet Exchange Points (IXPs). R. Gagliano.
     August 2010. (Format: TXT=3D22786 bytes) (Status: INFORMATIONAL)

http://www.ietf.org/rfc/rfc5991.txt
5991 Teredo Security Updates. D. Thaler, S. Krishnan, J. Hoagland.
     September 2010. (Format: TXT=3D20847 bytes) (Updates RFC4380) =
(Status:
     PROPOSED STANDARD)

http://www.ietf.org/rfc/rfc6018.txt
6018 IPv4 and IPv6 Greynets. F. Baker, W. Harrop, G. Armitage.
     September 2010. (Format: TXT=3D21541 bytes) (Status: INFORMATIONAL)


From behcetsarikaya@yahoo.com  Fri Oct  1 13:58:45 2010
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B4FFF3A6E1E for <v6ops@core3.amsl.com>; Fri,  1 Oct 2010 13:58:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.014
X-Spam-Level: 
X-Spam-Status: No, score=-2.014 tagged_above=-999 required=5 tests=[AWL=0.251,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4TOeanxleg4G for <v6ops@core3.amsl.com>; Fri,  1 Oct 2010 13:58:45 -0700 (PDT)
Received: from web111406.mail.gq1.yahoo.com (web111406.mail.gq1.yahoo.com [67.195.15.162]) by core3.amsl.com (Postfix) with SMTP id E72AA3A6DA8 for <v6ops@ietf.org>; Fri,  1 Oct 2010 13:58:44 -0700 (PDT)
Received: (qmail 12191 invoked by uid 60001); 1 Oct 2010 20:59:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1285966772; bh=hLpvqIjV6n4illrmX8ud+HslDVpPxif5BcOFU3t3nUM=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=G66D2UGYaCj4kWWARU470f6tbpmTnhI23JS0Wr1ngVRdLJzM+IEmkmCKeklK2vnbmBWwxnrW7dOuhLqdBS4jRcNppM3KhNKQBzE8yCwxXVOq7Kn6yNj1e6SWpteshRLW4M/Cml5AZgt0IgeRZC+pSioExFIQtWFHJYQH2NgiyPU=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=Bb91a5B5O6lWzzXTa78JYYPFNLLC6GsULS7xJ3e1DZ4PB32iWsjs5fUjbFZ2UsPf72g6QAwI++WKjnM1xPBdcz6DMS+Pgr20zMVA16tfYWsYF/Rrj1XoIEpV9XJmfhCW63jPOghQNdo8/x9Dy3oR7rdIrKUFmM+YafK6yZgFLYs=;
Message-ID: <244761.11289.qm@web111406.mail.gq1.yahoo.com>
X-YMail-OSG: qZlg6CgVM1kH4BJtTmi6LJIek2Ste3hz2U98WCjcpiv.WPe MIJUGmFTZtHLeXWL0MDqNRS3szIdzHM.0GsD5iSbKt97Uhm0TLQt5U_FnUSC hbIP.LMkwH4IoW2Lb5KkvkMFHYBuZUKJwVGszW_K2ePY9aK9pWL8IR7bdbOw G6TnM8FJV1VqvzS1L7C8PoOwb51vGD58s1BOkYiNItFCqnxwQQNF.9nkSShh a542omBKD2RqnkKbJJ8TrHqowZ_2ruvLlNj1FrmLpewq_Q4WvY2z1n.YD.cV M6VWSeyJGj8..4zc9oQ--
Received: from [206.16.17.212] by web111406.mail.gq1.yahoo.com via HTTP; Fri, 01 Oct 2010 13:59:32 PDT
X-Mailer: YahooMailRC/497 YahooMailWebService/0.8.105.279950
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com>
Date: Fri, 1 Oct 2010 13:59:32 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: Fred Baker <fred@cisco.com>, IPv6 Operations <v6ops@ietf.org>
In-Reply-To: <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [v6ops] draft-sarikaya-v6ops-prefix-delegation-01
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Oct 2010 20:58:45 -0000

Hi Fred,



> 
> Dead?
>      draft-sarikaya-v6ops-prefix-delegation-01        
> 


We are waiting for Suresh's comments as he promised in Maastricht according to 
the official minutes.

Regards,

Behcet



      

From ek@google.com  Fri Oct  1 15:02:58 2010
Return-Path: <ek@google.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 234EE3A6BB0 for <v6ops@core3.amsl.com>; Fri,  1 Oct 2010 15:02:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.377
X-Spam-Level: 
X-Spam-Status: No, score=-105.377 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V9Jaztwj4TmE for <v6ops@core3.amsl.com>; Fri,  1 Oct 2010 15:02:56 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 7839B3A6B53 for <v6ops@ietf.org>; Fri,  1 Oct 2010 15:02:56 -0700 (PDT)
Received: from wpaz17.hot.corp.google.com (wpaz17.hot.corp.google.com [172.24.198.81]) by smtp-out.google.com with ESMTP id o91M3iNc001309 for <v6ops@ietf.org>; Fri, 1 Oct 2010 15:03:44 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1285970624; bh=OLF7gtVUqJHVszPjQcfB9ugO67o=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=TpJ6CstKIMfXh9cdxZwpI1dejk2ehzebrZg9AI9CPXkFlnoa0Ut1J5GOhq0dAF3ss RLdL8CC1f1CJ1zJMhme+w==
Received: from qyk8 (qyk8.prod.google.com [10.241.83.136]) by wpaz17.hot.corp.google.com with ESMTP id o91M2Dmv030429 for <v6ops@ietf.org>; Fri, 1 Oct 2010 15:03:43 -0700
Received: by qyk8 with SMTP id 8so2342141qyk.13 for <v6ops@ietf.org>; Fri, 01 Oct 2010 15:03:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=j8SoioI9d+vVSdUt1kptRI5lykfiySQkqXg3Wxlod70=; b=gP8PKpkOC9AiYkokOCIKNnrYXJpI/50DIOYM6W12YH8w5Zi0oXzViVxT1K3UvdwdG5 XjHNRJe0nTVB/Emg0bag==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=PlH7Gj/SBSCoRFNztvxOiztBZ8b7YWK5l7ZwaaPBtdslphVhPVC4X0XE8d0xultJxZ a53wtRpaUqlOT+FQgFyA==
MIME-Version: 1.0
Received: by 10.224.74.21 with SMTP id s21mr4309436qaj.155.1285970622583; Fri, 01 Oct 2010 15:03:42 -0700 (PDT)
Received: by 10.229.13.140 with HTTP; Fri, 1 Oct 2010 15:03:42 -0700 (PDT)
In-Reply-To: <C8CB9E88.5599%jason_livingood@cable.comcast.com>
References: <C8BFD127.F082%victor.kuarsingh@gmail.com> <C8CB9E88.5599%jason_livingood@cable.comcast.com>
Date: Fri, 1 Oct 2010 15:03:42 -0700
Message-ID: <AANLkTimgPDEofmH_-zp5bBs3xG=tUJS_-wFM9bcO4tfa@mail.gmail.com>
From: Erik Kline <ek@google.com>
To: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] Soliciting feedback on draft-livingood-dns-whitelisting-implications
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Oct 2010 22:02:58 -0000

On 1 October 2010 11:28, Livingood, Jason
<Jason_Livingood@cable.comcast.com> wrote:
> Hi -
>
> I am soliciting feeback on this new draft, available at http://tools.ietf=
.org/html/draft-livingood-dns-whitelisting-implications. In particular, I a=
m looking for more text to add in the justifications / rationale for this p=
ractice in an attempt to objectively examine the issue from many sides. =C2=
=A0This is only a first draft of course.
>
> Regards
> Jason Livingood
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

In general:

    * consider the similarities to DNS load balancing
    * consider the similarities in implication to DNS64
    * you should understand and document that no network-level access
control restrictions are implied

There seems to be some confusion wrt to this last point throughout the docu=
ment.

A few other, technical issues listed below.


[Section 2]

Your examples/diagrams imply that an end client requests a general
list of addresses for www.example.com.  [I actually might prefer it if
that were true.]  In practice however A RR lookups are separate, and
usually subsequent to, AAAA RR requests.  If a record of any kind
exists for the name being resolved but the server is not going to
return the RR type requested (usually because it genuinely doesn't
exist) then OK with 0 RRs in the answer section is what is returned.
In the case of whitelisting the code is slightly more complex in that
if an AAAA is the only record in the zone for the name being requested
and that name is not going to be returned then it's probably more
correct to return NXDOMAIN; otherwise if other RRs (e.g. A) then
SUCCESS with 0 RRs in the answer section is the proper response.
These examples and diagrams might be a bit more technically precise
wrt DNS mechanics (although I understand that there is no IETF RFC or
draft discussing the true mechanics of whitelisting wrt the DNS
protocol).


[Section 3]

"Some parties" requires a reference.  Otherwise "some parties" might
just be you.  Since I know this is not the case, and I also know that
references exist, please link to one from here (and elsewhere).

The "model" of DNS described is also not quite the current state of
the world.  "Everyone", in deliberate quotation marks, employs DNS
load balancing and any specific A RR may never be seen by some
requesters (usually because of geographic/network latency
considerations).  Your text implies that DNS for A RRs is currently
vastly more egalitarian than it actually is.  Perhaps discussion of
DNS load balancing and its relationship to whitelisting could
supplement section 4, which might then be relabeled "Similarities to
other DNS Operations", or something.


[Section 6]

All basically true; it's mostly about the end user experience.  This
is also the primary motivation behind DNS load balancing, the way CDNs
do it.

Although I'll add this odd anecdote.  In the course of discussing
whitelisting with a few different organizations I have actually been
told by some operators/administrators that they did not want us to
serve them AAAAs.  Upon further discussion what became clear is that
some folks don't want the full load of youtube traffic to shift to
their IPv6 infrastructure until they're ready to support it.

So yes, we've had requests from folks to /not/ be served AAAAs.  At
first I was surprised, but now I understand.


[Section 7.1]

The end-to-end model does not prevail on the IPv4 Internet today.  See
previous comment.

It is not clear how operators of authoritative servers for domains are
somehow "in the middle" of the network, except possibly as transit
points on the resolution path to subdomains.  Perhaps you mean "in the
middle" in some social or political sense?  In which case you may wish
to select a different document, or different subsection, to reference.


[Section 7.2]

Again: not true in the IPv4 Internet today where DNS load balancing is empl=
oyed.

Note also that "reachability", in the true sense, is unaffected by the
whitelisting you're talking about.  It's network "knowledge" or
"awareness" that's affected.  There is no discussion of ACLs that
prevent IPv6 connections from succeeding, just like there is no
discussion of ACLs that prevent IPv4 connections from succeeding.
Whitelisting, as I believe you're trying to discuss it, only refers to
a resolver's awareness that an IPv6 address is associated with a
hostname.  No barriers to true reachability exist.


[Section 7.4]

What is the definition of an "important domain"?


[Section 7.5]

The relationship to governmental censorship seems imprecise, or
inapplicable.  In the governmental censorship case, logical access to
a resource is denied, as mandated by law.  In the whitelisting case,
logical access to a resource /remains unrestricted/.


[Section 7.6]

Do you have a reference to anyone who has publicly stated they are not
deploying IPv6 and that the principal reason for their not deploying
IPv6 is somehow whitelisting-related?


[Section 9.1]

Quite the contrary: any implementation of DNS whitelisting that also
seeks to support DNSSEC must be extremely careful in doing so.  The
implications are very similar to those of DNS64.

From joelja@bogus.com  Fri Oct  1 23:56:39 2010
Return-Path: <joelja@bogus.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4FCCC3A6D87 for <v6ops@core3.amsl.com>; Fri,  1 Oct 2010 23:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.045
X-Spam-Level: 
X-Spam-Status: No, score=-102.045 tagged_above=-999 required=5 tests=[AWL=-0.046, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uy2wCYWMx3B0 for <v6ops@core3.amsl.com>; Fri,  1 Oct 2010 23:56:38 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id CA63A3A6C84 for <v6ops@ietf.org>; Fri,  1 Oct 2010 23:56:37 -0700 (PDT)
Received: from joelja-mac.lan (c-98-234-104-156.hsd1.ca.comcast.net [98.234.104.156]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id o926uir0068505 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sat, 2 Oct 2010 06:56:45 GMT (envelope-from joelja@bogus.com)
Message-ID: <4CA6D7AC.5050204@bogus.com>
Date: Fri, 01 Oct 2010 23:56:44 -0700
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: V6ops Chairs <v6ops-chairs@tools.ietf.org>
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com>
In-Reply-To: <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Sat, 02 Oct 2010 06:56:46 +0000 (UTC)
Cc: IPv6 Operations <v6ops@ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Oct 2010 06:56:39 -0000

On 10/1/10 11:35 AM, Fred Baker wrote:
> On Oct 1, 2010, at 9:19 AM, IETF Secretariat wrote:
>> Dear Fred Baker,
>> 
>> The sessions that you have requested have been scheduled. Below is
>> the scheduled session information followed by the information of
>> sessions that you have requested.
>> 
>> V6OPS Session 1 (2.5 hours) Wednesday, Morning Session I 0900-1130 
>> Room Name: Valley Ballroom B 
>> ---------------------------------------------- V6OPS Session 2 (2.5
>> hours) Friday, Afternoon Session I 1300-1500 Room Name: Valley
>> Ballroom A ----------------------------------------------
> 
> 
> On Oct 1, 2010, at 11:07 AM, IETF Agenda wrote:
>> The DRAFT agenda is ready for viewing.  Please note the cutoff date
>> for requests to reschedule Working Group and BOF meetings is
>> October 11, 2010 17:00 PT.  The final agenda will be published on
>> October 15, 2010.
>> 
>> https://datatracker.ietf.org/meeting/79/agenda.html 
>> https://datatracker.ietf.org/meeting/79/agenda.txt
>> 
>> http://www.ietf.org/meeting/79/index.html
>> 
>> 
>> Thanks, Wanda
>> 
>> Only 36 days until the Beijing IETF! Online registration for the
>> IETF meeting is at: http://www.ietf.org/meetings/79/
> 
> 
> Joel, Kurtis, and I are starting to assemble the IETF 79 Agenda. What
> I have at this instant is at
> http://www.ietf.org/proceedings/79/agenda/v6ops.html. I requested two
> morning (2.5 hours) slots; I got one morning slot and "Friday
> afternoon until we stop talking" - nominally two hours, but Wanda
> tells me she has noted that we will likely run over. It looks like we
> will have a pretty full agenda; between the -v4v6tran- and -v6ops-
> work, we have a total of 18 drafts.
> 
> Anything I have missed - drop us a note at
> v6ops-chairs@tools.ietf.org if you would. The chairs have not yet
> discussed this in detail amongst ourselves yet, so I'm not sure which
> day will get which topic, and there are other reorganizations that
> could happen. If folks have strong opinions, that too would be
> interesting to know.
> 
> This assumes, btw, that the WGLCs that we have been running mean that
> we don't need to discuss those drafts. Besides the drafts on the
> agenda, our status is:
> 
> To complete WGLC before IETF 79 
> draft-arkko-ipv6-transition-guidelines    (waiting new draft) 
> draft-ietf-v6ops-tunnel-security-concerns (waiting document writeup)

		actually this one is waiting an updated draft to clear
		one issued noted in last call.

> draft-ietf-v6ops-incremental-cgn          (just completed WGLC) 
> draft-ietf-v6ops-tunnel-loops             (in WGLC) 
> draft-ietf-v6ops-v6-in-mobile-networks    (October 11-24) 
> draft-ietf-v6ops-3177bis-48boundary       (Oct 24-Nov 7)
> 
> In IESG discussion: draft-gundavelli-v6ops-l2-unicast-04 
> draft-ietf-v6ops-cpe-simple-security-14 draft-ietf-v6ops-ra-guard-08 
> draft-ietf-v6ops-rogue-ra-01 (Needs an updated draft from Tim)
> 
> RFC Editor Queue draft-ietf-v6ops-ipv6-cpe-router-07 
> draft-ietf-v6ops-isp-scenarios-00 
> draft-thaler-v6ops-teredo-extensions-08
> 
> Dead? draft-sarikaya-v6ops-prefix-delegation-01
> 
> Recent RFCs:
> 
> http://www.ietf.org/rfc/rfc5963.txt 5963 IPv6 Deployment in Internet
> Exchange Points (IXPs). R. Gagliano. August 2010. (Format: TXT=22786
> bytes) (Status: INFORMATIONAL)
> 
> http://www.ietf.org/rfc/rfc5991.txt 5991 Teredo Security Updates. D.
> Thaler, S. Krishnan, J. Hoagland. September 2010. (Format: TXT=20847
> bytes) (Updates RFC4380) (Status: PROPOSED STANDARD)
> 
> http://www.ietf.org/rfc/rfc6018.txt 6018 IPv4 and IPv6 Greynets. F.
> Baker, W. Harrop, G. Armitage. September 2010. (Format: TXT=21541
> bytes) (Status: INFORMATIONAL)
> 
> _______________________________________________ v6ops mailing list 
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
> 


From tena@huawei.com  Sun Oct  3 02:52:00 2010
Return-Path: <tena@huawei.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B6E973A6E1A for <v6ops@core3.amsl.com>; Sun,  3 Oct 2010 02:52:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.048
X-Spam-Level: 
X-Spam-Status: No, score=-100.048 tagged_above=-999 required=5 tests=[AWL=-0.154, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10+wu2-4quaW for <v6ops@core3.amsl.com>; Sun,  3 Oct 2010 02:51:59 -0700 (PDT)
Received: from szxga05-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id B97483A69F2 for <v6ops@ietf.org>; Sun,  3 Oct 2010 02:51:58 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9P00J4OKRSSH@szxga05-in.huawei.com> for v6ops@ietf.org; Sun, 03 Oct 2010 17:52:40 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9P008JGKRRVQ@szxga05-in.huawei.com> for v6ops@ietf.org; Sun, 03 Oct 2010 17:52:40 +0800 (CST)
Received: from [192.168.5.101] ([113.116.107.22]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L9P006X7KRQQ2@szxml01-in.huawei.com>; Sun, 03 Oct 2010 17:52:39 +0800 (CST)
Date: Sun, 03 Oct 2010 17:52:38 +0800
From: Tina TSOU <tena@huawei.com>
In-reply-to: <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com>
To: V6ops Chairs <v6ops-chairs@tools.ietf.org>
Message-id: <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: multipart/alternative; boundary="Boundary_(ID_fmxu2VD7lsAD7SEQZqnOrQ)"
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com>
Cc: IPv6 Operations <v6ops@ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Oct 2010 09:52:00 -0000

--Boundary_(ID_fmxu2VD7lsAD7SEQZqnOrQ)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT

Hi Fred,
Just a minor reminder that you said 0.75 to 1.5 sessions will be  
allocated to v4v6tran work.
Here is the record.
https://cisco.webex.com/ciscosales/lsr.php?AT=pb&SP=MC&rID=46384302&rKey=10def3e927a116b3


B. R.
Tina
http://tinatsou.weebly.com




On Oct 2, 2010, at 2:35 AM, Fred Baker wrote:

> On Oct 1, 2010, at 9:19 AM, IETF Secretariat wrote:
>> Dear Fred Baker,
>>
>> The sessions that you have requested have been scheduled.
>> Below is the scheduled session information followed by
>> the information of sessions that you have requested.
>>
>> V6OPS Session 1 (2.5 hours)
>> Wednesday, Morning Session I 0900-1130
>> Room Name: Valley Ballroom B
>> ----------------------------------------------
>> V6OPS Session 2 (2.5 hours)
>> Friday, Afternoon Session I 1300-1500
>> Room Name: Valley Ballroom A
>> ----------------------------------------------
>
>
> On Oct 1, 2010, at 11:07 AM, IETF Agenda wrote:
>> The DRAFT agenda is ready for viewing.  Please note the cutoff date  
>> for
>> requests to reschedule Working Group and BOF meetings is October  
>> 11, 2010
>> 17:00 PT.  The final agenda will be published on October 15, 2010.
>>
>> https://datatracker.ietf.org/meeting/79/agenda.html
>> https://datatracker.ietf.org/meeting/79/agenda.txt
>>
>> http://www.ietf.org/meeting/79/index.html
>>
>>
>> Thanks,
>> Wanda
>>
>> Only 36 days until the Beijing IETF!
>> Online registration for the IETF meeting is at:
>> http://www.ietf.org/meetings/79/
>
>
> Joel, Kurtis, and I are starting to assemble the IETF 79 Agenda.  
> What I have at this instant is at http://www.ietf.org/proceedings/79/agenda/v6ops.html 
> . I requested two morning (2.5 hours) slots; I got one morning slot  
> and "Friday afternoon until we stop talking" - nominally two hours,  
> but Wanda tells me she has noted that we will likely run over. It  
> looks like we will have a pretty full agenda; between the -v4v6tran-  
> and -v6ops- work, we have a total of 18 drafts.
>
> Anything I have missed - drop us a note at v6ops- 
> chairs@tools.ietf.org if you would. The chairs have not yet  
> discussed this in detail amongst ourselves yet, so I'm not sure  
> which day will get which topic, and there are other reorganizations  
> that could happen. If folks have strong opinions, that too would be  
> interesting to know.
>
> This assumes, btw, that the WGLCs that we have been running mean  
> that we don't need to discuss those drafts. Besides the drafts on  
> the agenda, our status is:
>
> To complete WGLC before IETF 79
> 	draft-arkko-ipv6-transition-guidelines    (waiting new draft)
> 	draft-ietf-v6ops-tunnel-security-concerns (waiting document writeup)
> 	draft-ietf-v6ops-incremental-cgn          (just completed WGLC)
> 	draft-ietf-v6ops-tunnel-loops             (in WGLC)
> 	draft-ietf-v6ops-v6-in-mobile-networks    (October 11-24)
> 	draft-ietf-v6ops-3177bis-48boundary       (Oct 24-Nov 7)
>
> In IESG discussion:
> 	draft-gundavelli-v6ops-l2-unicast-04	
> 	draft-ietf-v6ops-cpe-simple-security-14	
> 	draft-ietf-v6ops-ra-guard-08
> 	draft-ietf-v6ops-rogue-ra-01 (Needs an updated draft from Tim)
>
> RFC Editor Queue		
> 	draft-ietf-v6ops-ipv6-cpe-router-07
> 	draft-ietf-v6ops-isp-scenarios-00
> 	draft-thaler-v6ops-teredo-extensions-08
>
> Dead?
> 	draft-sarikaya-v6ops-prefix-delegation-01		
>
> Recent RFCs:
>
> http://www.ietf.org/rfc/rfc5963.txt
> 5963 IPv6 Deployment in Internet Exchange Points (IXPs). R. Gagliano.
>     August 2010. (Format: TXT=22786 bytes) (Status: INFORMATIONAL)
>
> http://www.ietf.org/rfc/rfc5991.txt
> 5991 Teredo Security Updates. D. Thaler, S. Krishnan, J. Hoagland.
>     September 2010. (Format: TXT=20847 bytes) (Updates RFC4380)  
> (Status:
>     PROPOSED STANDARD)
>
> http://www.ietf.org/rfc/rfc6018.txt
> 6018 IPv4 and IPv6 Greynets. F. Baker, W. Harrop, G. Armitage.
>     September 2010. (Format: TXT=21541 bytes) (Status: INFORMATIONAL)
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


--Boundary_(ID_fmxu2VD7lsAD7SEQZqnOrQ)
Content-type: text/html; charset=US-ASCII
Content-transfer-encoding: 7BIT

<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Fred,<div>Just a minor reminder that you said 0.75 to 1.5 sessions will be allocated to v4v6tran work.</div><div>Here is the record.</div><div><span class="Apple-style-span" style="font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: small; "><a href="https://cisco.webex.com/ciscosales/lsr.php?AT=pb&amp;SP=MC&amp;rID=46384302&amp;rKey=10def3e927a116b3" target="_blank">https://cisco.webex.com/ciscosales/lsr.php?AT=pb&amp;SP=MC&amp;rID=46384302&amp;rKey=10def3e927a116b3</a></span><span class="Apple-style-span" style="font-family: Tahoma, Arial, sans-serif, Helvetica, Geneva; font-size: small; ">&nbsp;</span></div><div><br></div><div><br><div apple-content-edited="true"> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: 
 normal; 
ine-height: normal; orphans: 2; text-align: 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="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; 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="word-wrap: break-word; 
 -webkit-
-line-break: after-white-space; "><div><span class="Apple-style-span" style="font-size: 12px; "><div>B. R.</div><div>Tina</div><div><a href="http://tinatsou.weebly.com">http://tinatsou.weebly.com</a></div><div></div></span></div><div><br></div></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"> </div><br><div><div>On Oct 2, 2010, at 2:35 AM, Fred Baker wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On Oct 1, 2010, at 9:19 AM, IETF Secretariat wrote:<br><blockquote type="cite">Dear Fred Baker,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The sessions that you have requested have been scheduled.<br></blockquote><blockquote type="cite">Below is the scheduled session information followed by <br></blockquote><blockquote type="cite">the information of sessions that you have requested.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">
 V6OPS Se
blockquote><blockquote type="cite">Wednesday, Morning Session I 0900-1130<br></blockquote><blockquote type="cite">Room Name: Valley Ballroom B<br></blockquote><blockquote type="cite">----------------------------------------------<br></blockquote><blockquote type="cite">V6OPS Session 2 (2.5 hours)<br></blockquote><blockquote type="cite">Friday, Afternoon Session I 1300-1500<br></blockquote><blockquote type="cite">Room Name: Valley Ballroom A<br></blockquote><blockquote type="cite">----------------------------------------------<br></blockquote><br><br>On Oct 1, 2010, at 11:07 AM, IETF Agenda wrote:<br><blockquote type="cite">The DRAFT agenda is ready for viewing. &nbsp;Please note the cutoff date for<br></blockquote><blockquote type="cite">requests to reschedule Working Group and BOF meetings is October 11, 2010<br></blockquote><blockquote type="cite">17:00 PT. &nbsp;The final agenda will be published on October 15, 2010.<br></blockquote><blockquote type="cite"><br></blockquote
 ><blockq
"https://datatracker.ietf.org/meeting/79/agenda.html">https://datatracker.ietf.org/meeting/79/agenda.html</a><br></blockquote><blockquote type="cite"><a href="https://datatracker.ietf.org/meeting/79/agenda.txt">https://datatracker.ietf.org/meeting/79/agenda.txt</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><a href="http://www.ietf.org/meeting/79/index.html">http://www.ietf.org/meeting/79/index.html</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks,<br></blockquote><blockquote type="cite">Wanda<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Only 36 days until the Beijing IETF!<br></blockquote><blockquote type="cite">Online registration for the IETF meeting is at:<br></blockquote><blockquote type="cite"><a href="http://www.ietf.org/meetings/79/">http://www.ietf.org/meetings/79/</a><br></blockquote><br><br>Joel, Kurtis, and I
  are sta
F 79 Agenda. What I have at this instant is at <a href="http://www.ietf.org/proceedings/79/agenda/v6ops.html">http://www.ietf.org/proceedings/79/agenda/v6ops.html</a>. I requested two morning (2.5 hours) slots; I got one morning slot and "Friday afternoon until we stop talking" - nominally two hours, but Wanda tells me she has noted that we will likely run over. It looks like we will have a pretty full agenda; between the -v4v6tran- and -v6ops- work, we have a total of 18 drafts. &nbsp;<br><br>Anything I have missed - drop us a note at <a href="mailto:v6ops-chairs@tools.ietf.org">v6ops-chairs@tools.ietf.org</a> if you would. The chairs have not yet discussed this in detail amongst ourselves yet, so I'm not sure which day will get which topic, and there are other reorganizations that could happen. If folks have strong opinions, that too would be interesting to know.<br><br>This assumes, btw, that the WGLCs that we have been running mean that we don't need to discuss those draf
 ts. Besi
nda, our status is:<br><br>To complete WGLC before IETF 79<br><span class="Apple-tab-span" style="white-space:pre">	</span>draft-arkko-ipv6-transition-guidelines &nbsp;&nbsp;&nbsp;(waiting new draft)<br><span class="Apple-tab-span" style="white-space:pre">	</span>draft-ietf-v6ops-tunnel-security-concerns (waiting document writeup)<br><span class="Apple-tab-span" style="white-space:pre">	</span>draft-ietf-v6ops-incremental-cgn &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(just completed WGLC)<br><span class="Apple-tab-span" style="white-space:pre">	</span>draft-ietf-v6ops-tunnel-loops &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(in WGLC)<br><span class="Apple-tab-span" style="white-space:pre">	</span>draft-ietf-v6ops-v6-in-mobile-networks &nbsp;&nbsp;&nbsp;(October 11-24)<br><span class="Apple-tab-span" style="white-space:pre">	</span>draft-ietf-v6ops-3177bis-48boundary &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(Oct 24-Nov 7)<br><br>In IESG discu
 ssion:<b
span" style="white-space:pre">	</span>draft-gundavelli-v6ops-l2-unicast-04<span class="Apple-tab-span" style="white-space:pre">	</span><br><span class="Apple-tab-span" style="white-space:pre">	</span>draft-ietf-v6ops-cpe-simple-security-14<span class="Apple-tab-span" style="white-space:pre">	</span><br><span class="Apple-tab-span" style="white-space:pre">	</span>draft-ietf-v6ops-ra-guard-08<br><span class="Apple-tab-span" style="white-space:pre">	</span>draft-ietf-v6ops-rogue-ra-01 (Needs an updated draft from Tim)<br><br>RFC Editor Queue<span class="Apple-tab-span" style="white-space:pre">	</span><span class="Apple-tab-span" style="white-space:pre">	</span><br><span class="Apple-tab-span" style="white-space:pre">	</span>draft-ietf-v6ops-ipv6-cpe-router-07<br><span class="Apple-tab-span" style="white-space:pre">	</span>draft-ietf-v6ops-isp-scenarios-00<br><span class="Apple-tab-span" style="white-space:pre">	</span>draft-thaler-v6ops-teredo-extensions-08<br><br>Dead?<br><span
  class="
ite-space:pre">	</span>draft-sarikaya-v6ops-prefix-delegation-01<span class="Apple-tab-span" style="white-space:pre">	</span><span class="Apple-tab-span" style="white-space:pre">	</span><br><br>Recent RFCs:<br><br><a href="http://www.ietf.org/rfc/rfc5963.txt">http://www.ietf.org/rfc/rfc5963.txt</a><br>5963 IPv6 Deployment in Internet Exchange Points (IXPs). R. Gagliano.<br> &nbsp;&nbsp;&nbsp;&nbsp;August 2010. (Format: TXT=22786 bytes) (Status: INFORMATIONAL)<br><br>http://www.ietf.org/rfc/rfc5991.txt<br>5991 Teredo Security Updates. D. Thaler, S. Krishnan, J. Hoagland.<br> &nbsp;&nbsp;&nbsp;&nbsp;September 2010. (Format: TXT=20847 bytes) (Updates RFC4380) (Status:<br> &nbsp;&nbsp;&nbsp;&nbsp;PROPOSED STANDARD)<br><br>http://www.ietf.org/rfc/rfc6018.txt<br>6018 IPv4 and IPv6 Greynets. F. Baker, W. Harrop, G. Armitage.<br> &nbsp;&nbsp;&nbsp;&nbsp;September 2010. (Format: TXT=21541 bytes) (Status: INFORMATIONAL)<br><br>_______________________________________________<br>v6ops ma
 iling li
ttps://www.ietf.org/mailman/listinfo/v6ops<br></div></blockquote></div><br></div></body></html>

--Boundary_(ID_fmxu2VD7lsAD7SEQZqnOrQ)--

From fred@cisco.com  Sun Oct  3 22:43:27 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 518D63A6E0A for <v6ops@core3.amsl.com>; Sun,  3 Oct 2010 22:43:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.999
X-Spam-Level: 
X-Spam-Status: No, score=-109.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A65sS+0M1KrJ for <v6ops@core3.amsl.com>; Sun,  3 Oct 2010 22:43:25 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 4998C3A6DEB for <v6ops@ietf.org>; Sun,  3 Oct 2010 22:43:24 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAH8GqUxAZnwM/2dsb2JhbACiQnGIGZxlm0qFRwSKQIMC
X-IronPort-AV: E=Sophos;i="4.57,277,1283731200"; d="scan'208";a="166454528"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 04 Oct 2010 05:44:18 +0000
Received: from Freds-Computer.local (rtp-vpn2-1853.cisco.com [10.82.247.64]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o945i3fQ003204; Mon, 4 Oct 2010 05:44:12 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Mon, 04 Oct 2010 01:44:18 -0400
X-PGP-Universal: processed; by Freds-Computer.local on Mon, 04 Oct 2010 01:44:18 -0400
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com>
Date: Mon, 4 Oct 2010 01:37:34 -0400
Message-Id: <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com>
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com>
To: Tina TSOU <tena@huawei.com>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Oct 2010 05:43:27 -0000

On Oct 3, 2010, at 5:52 AM, Tina TSOU wrote:

> Hi Fred,
> Just a minor reminder that you said 0.75 to 1.5 sessions will be =
allocated to v4v6tran work.
> Here is the record.
> =
https://cisco.webex.com/ciscosales/lsr.php?AT=3Dpb&SP=3DMC&rID=3D46384302&=
rKey=3D10def3e927a116b3=20

After you look at the posted agenda, please feel free to comment on it.

> B. R.
> Tina
> http://tinatsou.weebly.com
>=20
>=20
>=20
>=20
> On Oct 2, 2010, at 2:35 AM, Fred Baker wrote:
>=20
>> On Oct 1, 2010, at 9:19 AM, IETF Secretariat wrote:
>>> Dear Fred Baker,
>>>=20
>>> The sessions that you have requested have been scheduled.
>>> Below is the scheduled session information followed by=20
>>> the information of sessions that you have requested.
>>>=20
>>> V6OPS Se blockquote>
>>>> Wednesday, Morning Session I 0900-1130
>>>> Room Name: Valley Ballroom B
>>>> ----------------------------------------------
>>>> V6OPS Session 2 (2.5 hours)
>>>> Friday, Afternoon Session I 1300-1500
>>>> Room Name: Valley Ballroom A
>>>> ----------------------------------------------
>>>=20
>>>=20
>>> On Oct 1, 2010, at 11:07 AM, IETF Agenda wrote:
>>>> The DRAFT agenda is ready for viewing.  Please note the cutoff date =
for
>>>> requests to reschedule Working Group and BOF meetings is October =
11, 2010
>>>> 17:00 PT.  The final agenda will be published on October 15, 2010.
>>>>=20
>>> https://datatracker.ietf.org/meeting/79/agenda.html
>>> https://datatracker.ietf.org/meeting/79/agenda.txt
>>>=20
>>> http://www.ietf.org/meeting/79/index.html
>>>=20
>>>=20
>>> Thanks,
>>> Wanda
>>>=20
>>> Only 36 days until the Beijing IETF!
>>> Online registration for the IETF meeting is at:
>>> http://www.ietf.org/meetings/79/
>>=20
>>=20
>> Joel, Kurtis, and I are sta F 79 Agenda. What I have at this instant =
is at http://www.ietf.org/proceedings/79/agenda/v6ops.html. I requested =
two morning (2.5 hours) slots; I got one morning slot and "Friday =
afternoon until we stop talking" - nominally two hours, but Wanda tells =
me she has noted that we will likely run over. It looks like we will =
have a pretty full agenda; between the -v4v6tran- and -v6ops- work, we =
have a total of 18 drafts. =20
>>=20
>> Anything I have missed - drop us a note at =
v6ops-chairs@tools.ietf.org if you would. The chairs have not yet =
discussed this in detail amongst ourselves yet, so I'm not sure which =
day will get which topic, and there are other reorganizations that could =
happen. If folks have strong opinions, that too would be interesting to =
know.
>>=20
>> This assumes, btw, that the WGLCs that we have been running mean that =
we don't need to discuss those draf ts. Besi nda, our status is:
>>=20
>> To complete WGLC before IETF 79
>> 	draft-arkko-ipv6-transition-guidelines    (waiting new draft)
>> 	draft-ietf-v6ops-tunnel-security-concerns (waiting document =
writeup)
>> 	draft-ietf-v6ops-incremental-cgn          (just completed WGLC)
>> 	draft-ietf-v6ops-tunnel-loops             (in WGLC)
>> 	draft-ietf-v6ops-v6-in-mobile-networks    (October 11-24)
>> 	draft-ietf-v6ops-3177bis-48boundary       (Oct 24-Nov 7)
>>=20
>> In IESG discu ssion:	draft-gundavelli-v6ops-l2-unicast-04=09
>> 	draft-ietf-v6ops-cpe-simple-security-14=09
>> 	draft-ietf-v6ops-ra-guard-08
>> 	draft-ietf-v6ops-rogue-ra-01 (Needs an updated draft from Tim)
>>=20
>> RFC Editor Queue	=09
>> 	draft-ietf-v6ops-ipv6-cpe-router-07
>> 	draft-ietf-v6ops-isp-scenarios-00
>> 	draft-thaler-v6ops-teredo-extensions-08
>>=20
>> Dead?
>> 	draft-sarikaya-v6ops-prefix-delegation-01	=09
>>=20
>> Recent RFCs:
>>=20
>> http://www.ietf.org/rfc/rfc5963.txt
>> 5963 IPv6 Deployment in Internet Exchange Points (IXPs). R. Gagliano.
>>     August 2010. (Format: TXT=3D22786 bytes) (Status: INFORMATIONAL)
>>=20
>> http://www.ietf.org/rfc/rfc5991.txt
>> 5991 Teredo Security Updates. D. Thaler, S. Krishnan, J. Hoagland.
>>     September 2010. (Format: TXT=3D20847 bytes) (Updates RFC4380) =
(Status:
>>     PROPOSED STANDARD)
>>=20
>> http://www.ietf.org/rfc/rfc6018.txt
>> 6018 IPv4 and IPv6 Greynets. F. Baker, W. Harrop, G. Armitage.
>>     September 2010. (Format: TXT=3D21541 bytes) (Status: =
INFORMATIONAL)
>>=20
>> _______________________________________________
>> v6ops mailing list
>> https://www.ietf.org/mailman/listinfo/v6ops
>>=20
>=20
>=20
> _______________________________________________
>=20
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From tena@huawei.com  Mon Oct  4 03:05:05 2010
Return-Path: <tena@huawei.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B26BF3A6F78 for <v6ops@core3.amsl.com>; Mon,  4 Oct 2010 03:05:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.742
X-Spam-Level: 
X-Spam-Status: No, score=-99.742 tagged_above=-999 required=5 tests=[AWL=-0.449, BAYES_50=0.001, FH_RELAY_NODNS=1.451, GB_I_LETTER=-2, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, HTML_NONELEMENT_30_40=0.001, J_CHICKENPOX_13=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6wGxI7m8JvdI for <v6ops@core3.amsl.com>; Mon,  4 Oct 2010 03:05:03 -0700 (PDT)
Received: from szxga05-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 54E933A6F4B for <v6ops@ietf.org>; Mon,  4 Oct 2010 03:05:03 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9R006J0FS4Z4@szxga05-in.huawei.com> for v6ops@ietf.org; Mon, 04 Oct 2010 18:00:04 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9R007W0FS3PZ@szxga05-in.huawei.com> for v6ops@ietf.org; Mon, 04 Oct 2010 18:00:04 +0800 (CST)
Received: from [192.168.1.4] ([113.116.36.142]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L9R008KAFS2X2@szxml02-in.huawei.com>; Mon, 04 Oct 2010 18:00:03 +0800 (CST)
Date: Mon, 04 Oct 2010 18:00:01 +0800
From: Tina TSOU <tena@huawei.com>
In-reply-to: <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com>
To: Fred Baker <fred@cisco.com>
Message-id: <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: multipart/alternative; boundary="Boundary_(ID_Qx2GOIUqi1cwOWLBTbpsQw)"
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com>
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Oct 2010 10:05:05 -0000

--Boundary_(ID_Qx2GOIUqi1cwOWLBTbpsQw)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT

Thank you for the arrangement. You made the agenda so quickly compared  
to the WG I chair;)

Some comments are below.

1)
"Welcome and introduction from the China Network Operators Group
Dong Yan, CNNOG and CNISP"

What's the implication from the China NOG introduction? In this case,  
do Asia, Europe and Oceania NOG also need to be given the  
introduction? These operators from North America, Europe, and Asia  
consider IETF is a global and original organization for IPv4 to IPv6  
transition.

What's the relationship between IETF WG v6ops and xNOG in v4 to v6  
transition area?

2)
"Problem Statements of IPv6 Transition of ISP
17-Sep-10, <draft-lee-v4v6tran-problem-02.txt>
Framework for IP Version Transition Scenarios
18-Aug-10, <draft-carpenter-v4v6tran-framework-00.txt>"

We have fully discussed the PS I-D and framework I-D in the v4v6tran  
WebEx meeting.
The target is a set of use cases I-Ds and transition guides I-Ds for  
broadband, cable, and mobile scenarios, which are aimed for  
information RFCs.
Do the PS I-D and framework I-D need to be discussed again in WG  
v6ops? Are they also aimed for informational RFCs? I don't have strong  
opinion about this.

3)
"Use Case For IPv6 Transition For a Large-Scale Broadband Service  
Provider
14-Sep-10, <draft-tian-v4v6tran-broadband-sp-usecase-00.txt>"
I don't know whether Can-Can would like to present this. I think it  
has been replaced by draft-huang-v6ops-v4v6tran-bb-usecase.

4)
"IPv6 Transition Guide For A Large ISP Providing Broadband Access
15-Sep-10, <draft-yang-v4v6tran-ipv6-transition-guide-00.txt>
IPv6 Transition Guide For A Large-scale Broadband Network
27-Sep-10, <draft-yang-v6ops-v4v6tran-bb-transition-guide-00.txt>"
I think only latter will be presented in WG v6ops Beijing meeting.
The latter is not China Telecom only any more. It is the initial  
version to invite contribution from all broadband networks. 90% of  
China Telecom's existing access network is PPPoE access network, which  
may be similar to some of the operators. They will focus on this type.  
This I-D leave space for those operators to contribute for existing  
DHCP access network.

Hope it helps.



B. R.
Tina
http://tinatsou.weebly.com




On Oct 4, 2010, at 1:37 PM, Fred Baker wrote:

>
> On Oct 3, 2010, at 5:52 AM, Tina TSOU wrote:
>
>> Hi Fred,
>> Just a minor reminder that you said 0.75 to 1.5 sessions will be  
>> allocated to v4v6tran work.
>> Here is the record.
>> https://cisco.webex.com/ciscosales/lsr.php?AT=pb&SP=MC&rID=46384302&rKey=10def3e927a116b3
>
> After you look at the posted agenda, please feel free to comment on  
> it.
>
>> B. R.
>> Tina
>> http://tinatsou.weebly.com
>>
>>
>>
>>
>> On Oct 2, 2010, at 2:35 AM, Fred Baker wrote:
>>
>>> On Oct 1, 2010, at 9:19 AM, IETF Secretariat wrote:
>>>> Dear Fred Baker,
>>>>
>>>> The sessions that you have requested have been scheduled.
>>>> Below is the scheduled session information followed by
>>>> the information of sessions that you have requested.
>>>>
>>>> V6OPS Se blockquote>
>>>>> Wednesday, Morning Session I 0900-1130
>>>>> Room Name: Valley Ballroom B
>>>>> ----------------------------------------------
>>>>> V6OPS Session 2 (2.5 hours)
>>>>> Friday, Afternoon Session I 1300-1500
>>>>> Room Name: Valley Ballroom A
>>>>> ----------------------------------------------
>>>>
>>>>
>>>> On Oct 1, 2010, at 11:07 AM, IETF Agenda wrote:
>>>>> The DRAFT agenda is ready for viewing.  Please note the cutoff  
>>>>> date for
>>>>> requests to reschedule Working Group and BOF meetings is October  
>>>>> 11, 2010
>>>>> 17:00 PT.  The final agenda will be published on October 15, 2010.
>>>>>
>>>> https://datatracker.ietf.org/meeting/79/agenda.html
>>>> https://datatracker.ietf.org/meeting/79/agenda.txt
>>>>
>>>> http://www.ietf.org/meeting/79/index.html
>>>>
>>>>
>>>> Thanks,
>>>> Wanda
>>>>
>>>> Only 36 days until the Beijing IETF!
>>>> Online registration for the IETF meeting is at:
>>>> http://www.ietf.org/meetings/79/
>>>
>>>
>>> Joel, Kurtis, and I are sta F 79 Agenda. What I have at this  
>>> instant is at http://www.ietf.org/proceedings/79/agenda/ 
>>> v6ops.html. I requested two morning (2.5 hours) slots; I got one  
>>> morning slot and "Friday afternoon until we stop talking" -  
>>> nominally two hours, but Wanda tells me she has noted that we will  
>>> likely run over. It looks like we will have a pretty full agenda;  
>>> between the -v4v6tran- and -v6ops- work, we have a total of 18  
>>> drafts.
>>>
>>> Anything I have missed - drop us a note at v6ops-chairs@tools.ietf.org 
>>>  if you would. The chairs have not yet discussed this in detail  
>>> amongst ourselves yet, so I'm not sure which day will get which  
>>> topic, and there are other reorganizations that could happen. If  
>>> folks have strong opinions, that too would be interesting to know.
>>>
>>> This assumes, btw, that the WGLCs that we have been running mean  
>>> that we don't need to discuss those draf ts. Besi nda, our status  
>>> is:
>>>
>>> To complete WGLC before IETF 79
>>> 	draft-arkko-ipv6-transition-guidelines    (waiting new draft)
>>> 	draft-ietf-v6ops-tunnel-security-concerns (waiting document  
>>> writeup)
>>> 	draft-ietf-v6ops-incremental-cgn          (just completed WGLC)
>>> 	draft-ietf-v6ops-tunnel-loops             (in WGLC)
>>> 	draft-ietf-v6ops-v6-in-mobile-networks    (October 11-24)
>>> 	draft-ietf-v6ops-3177bis-48boundary       (Oct 24-Nov 7)
>>>
>>> In IESG discu ssion:	draft-gundavelli-v6ops-l2-unicast-04	
>>> 	draft-ietf-v6ops-cpe-simple-security-14	
>>> 	draft-ietf-v6ops-ra-guard-08
>>> 	draft-ietf-v6ops-rogue-ra-01 (Needs an updated draft from Tim)
>>>
>>> RFC Editor Queue		
>>> 	draft-ietf-v6ops-ipv6-cpe-router-07
>>> 	draft-ietf-v6ops-isp-scenarios-00
>>> 	draft-thaler-v6ops-teredo-extensions-08
>>>
>>> Dead?
>>> 	draft-sarikaya-v6ops-prefix-delegation-01		
>>>
>>> Recent RFCs:
>>>
>>> http://www.ietf.org/rfc/rfc5963.txt
>>> 5963 IPv6 Deployment in Internet Exchange Points (IXPs). R.  
>>> Gagliano.
>>>    August 2010. (Format: TXT=22786 bytes) (Status: INFORMATIONAL)
>>>
>>> http://www.ietf.org/rfc/rfc5991.txt
>>> 5991 Teredo Security Updates. D. Thaler, S. Krishnan, J. Hoagland.
>>>    September 2010. (Format: TXT=20847 bytes) (Updates RFC4380)  
>>> (Status:
>>>    PROPOSED STANDARD)
>>>
>>> http://www.ietf.org/rfc/rfc6018.txt
>>> 6018 IPv4 and IPv6 Greynets. F. Baker, W. Harrop, G. Armitage.
>>>    September 2010. (Format: TXT=21541 bytes) (Status: INFORMATIONAL)
>>>
>>> _______________________________________________
>>> v6ops mailing list
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>
>>
>>
>> _______________________________________________
>>
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>


--Boundary_(ID_Qx2GOIUqi1cwOWLBTbpsQw)
Content-type: text/html; charset=US-ASCII
Content-transfer-encoding: 7BIT

<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Thank you for the arrangement. You made the agenda so quickly compared to the WG I chair;)</div><div><br></div><div>Some comments are below.</div><div><br></div><div>1)</div><div>"<span class="Apple-style-span" style="font-family: Times; "><b>Welcome and introduction from the China Network Operators Group</b></span></div><div><span class="Apple-style-span" style="font-family: Times; ">Dong Yan, CNNOG and CNISP</span>"</div><div><br></div><div>What's the implication from the China NOG introduction? In this case, do Asia, Europe and Oceania NOG also need to be given the introduction? These operators from North America, Europe, and Asia consider IETF is a global and original organization for IPv4 to IPv6 transition.</div><div><br></div><div>What's the relationship between IETF WG v6ops and xNOG in v4 to v6 transition area?</div><div><br></div><div>2)</div><div>"<span
  class="
font-family: Times; "><a href="http://tools.ietf.org/html/draft-lee-v4v6tran-problem"><b>Problem Statements of IPv6 Transition of ISP</b></a></span></div><dd style="font-family: Times; ">17-Sep-10, &lt;draft-lee-v4v6tran-problem-02.txt&gt;</dd><dt style="font-family: Times; "><a href="http://tools.ietf.org/html/draft-carpenter-v4v6tran-framework"><b>Framework for IP Version Transition Scenarios</b></a></dt><div><span class="Apple-style-span" style="font-family: Times; ">18-Aug-10, &lt;draft-carpenter-v4v6tran-framework-00.txt&gt;</span>"</div><div><br></div><div>We have fully&nbsp;discussed the PS I-D and framework I-D in the v4v6tran WebEx meeting.&nbsp;</div><div>The target is a set of use cases I-Ds and transition guides I-Ds for broadband, cable, and mobile scenarios, which are aimed for information RFCs.&nbsp;</div><div>Do the PS I-D and framework I-D need to be discussed again in WG v6ops? Are they also aimed for informational RFCs? I don't have strong opinion about thi
 s.</div>
iv><div>"<span class="Apple-style-span" style="font-family: Times; "><a href="http://tools.ietf.org/html/draft-tian-v4v6tran-broadband-sp-usecase"><b>Use Case For IPv6 Transition For a Large-Scale Broadband Service Provider</b></a></span></div><div><span class="Apple-style-span" style="font-family: Times; ">14-Sep-10, &lt;draft-tian-v4v6tran-broadband-sp-usecase-00.txt&gt;</span>"</div><div>I don't know whether Can-Can would like to present this. I think it has been replaced by&nbsp;<span class="Apple-style-span" style="font-family: Times; ">draft-huang-v6ops-v4v6tran-bb-usecase.</span></div><div><span class="Apple-style-span" style="font-family: Times; "><br></span></div><div><span class="Apple-style-span" style="font-family: Times; ">4)</span></div><div><span class="Apple-style-span" style="font-family: Times; ">"</span><span class="Apple-style-span" style="font-family: Times; "><a href="http://tools.ietf.org/html/draft-yang-v4v6tran-ipv6-transition-guide"><b>IPv6 Transitio
 n Guide 
 Broadband Access</b></a></span></div><dd style="font-family: Times; ">15-Sep-10, &lt;draft-yang-v4v6tran-ipv6-transition-guide-00.txt&gt;</dd><dt style="font-family: Times; "><a href="http://tools.ietf.org/html/draft-yang-v6ops-v4v6tran-bb-transition-guide"><b>IPv6 Transition Guide For A Large-scale Broadband Network</b></a></dt><div><span class="Apple-style-span" style="font-family: Times; ">27-Sep-10, &lt;draft-yang-v6ops-v4v6tran-bb-transition-guide-00.txt&gt;"</span></div><div><span class="Apple-style-span" style="font-family: Times; ">I think only latter will be presented in WG v6ops Beijing meeting.</span></div><div><span class="Apple-style-span" style="font-family: Times; ">The latter is not China Telecom only any more. It is the initial version to invite contribution from all broadband networks. 90% of&nbsp;China Telecom's&nbsp;existing access network is PPPoE access network, which may be similar to some of the operators. They will focus on this type. This I-D leave 
 space fo
ribute for existing DHCP access network.&nbsp;</span></div><div><span class="Apple-style-span" style="font-family: Times; "><br></span></div><div><span class="Apple-style-span" style="font-family: Times; ">Hope it helps.</span></div><div><font class="Apple-style-span" face="Times"><br></font></div><div><br></div><br><div apple-content-edited="true"> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); 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: 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="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-s
 pace; ">
span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; 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="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><span class="Apple-style-span" style="font-size: 12px; "><div>B. R.</div><div>Tina</div><div><a href="http://tinatsou.weebly.com">http://tinatsou.weebly.com</a></div><div></div></span></div><div><br></div></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"> </div><br><div><div>On Oct 4, 2010, at 1:37 PM, Fred Baker wrote:</div><br
  class="
"><blockquote type="cite"><div><br>On Oct 3, 2010, at 5:52 AM, Tina TSOU wrote:<br><br><blockquote type="cite">Hi Fred,<br></blockquote><blockquote type="cite">Just a minor reminder that you said 0.75 to 1.5 sessions will be allocated to v4v6tran work.<br></blockquote><blockquote type="cite">Here is the record.<br></blockquote><blockquote type="cite"><a href="https://cisco.webex.com/ciscosales/lsr.php?AT=pb&amp;SP=MC&amp;rID=46384302&amp;rKey=10def3e927a116b3">https://cisco.webex.com/ciscosales/lsr.php?AT=pb&amp;SP=MC&amp;rID=46384302&amp;rKey=10def3e927a116b3</a> <br></blockquote><br>After you look at the posted agenda, please feel free to comment on it.<br><br><blockquote type="cite">B. R.<br></blockquote><blockquote type="cite">Tina<br></blockquote><blockquote type="cite"><a href="http://tinatsou.weebly.com">http://tinatsou.weebly.com</a><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquo
 te><bloc
blockquote><blockquote type="cite">On Oct 2, 2010, at 2:35 AM, Fred Baker wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">On Oct 1, 2010, at 9:19 AM, IETF Secretariat wrote:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Dear Fred Baker,<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">The sessions that you have requested have been scheduled.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Below is the scheduled session information followed by <br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">the information of sessions that you have requested.<br></block
 quote></
blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">V6OPS Se blockquote&gt;<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Wednesday, Morning Session I 0900-1130<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Room Name: Valley Ballroom B<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">----------------------------------------------<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">V6OPS Session 2 (2.5 hours)<br></blockquote></blockquote></blockquote></bl
 ockquote
<blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Friday, Afternoon Session I 1300-1500<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Room Name: Valley Ballroom A<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">----------------------------------------------<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">On Oct 1, 2010, at 11:07 AM, IETF Agenda wrote:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockq
 uote typ
="cite">The DRAFT agenda is ready for viewing. &nbsp;Please note the cutoff date for<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">requests to reschedule Working Group and BOF meetings is October 11, 2010<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">17:00 PT. &nbsp;The final agenda will be published on October 15, 2010.<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="https://datatracker.ietf.org/meeting/79/agenda.html">https://datatracker.ietf.org/meeting/79/agenda.html</a><br></blockquote></blockquote></blockquote><blockquote type="
 cite"><b
ockquote type="cite"><a href="https://datatracker.ietf.org/meeting/79/agenda.txt">https://datatracker.ietf.org/meeting/79/agenda.txt</a><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="http://www.ietf.org/meeting/79/index.html">http://www.ietf.org/meeting/79/index.html</a><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Thanks,<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Wanda<br></blockquote></blockquote></blockquote><blockquote 
 type="ci
e"><blockquote type="cite"><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Only 36 days until the Beijing IETF!<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Online registration for the IETF meeting is at:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><a href="http://www.ietf.org/meetings/79/">http://www.ietf.org/meetings/79/</a><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Joel, Kurtis, and I are sta F 79 Agenda. What I have at this instant is at <a href="http://www.ietf.org/proceedings/79/agenda/v6ops.html">http://www.ietf.org/proceedings/79/agenda/v6ops.html</a>. I requested t
 wo morni
ot one morning slot and "Friday afternoon until we stop talking" - nominally two hours, but Wanda tells me she has noted that we will likely run over. It looks like we will have a pretty full agenda; between the -v4v6tran- and -v6ops- work, we have a total of 18 drafts. &nbsp;<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Anything I have missed - drop us a note at <a href="mailto:v6ops-chairs@tools.ietf.org">v6ops-chairs@tools.ietf.org</a> if you would. The chairs have not yet discussed this in detail amongst ourselves yet, so I'm not sure which day will get which topic, and there are other reorganizations that could happen. If folks have strong opinions, that too would be interesting to know.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">This assumes, btw, that
  the WGL
ing mean that we don't need to discuss those draf ts. Besi nda, our status is:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">To complete WGLC before IETF 79<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre">	</span>draft-arkko-ipv6-transition-guidelines &nbsp;&nbsp;&nbsp;(waiting new draft)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre">	</span>draft-ietf-v6ops-tunnel-security-concerns (waiting document writeup)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre">	</span>draft-ietf-v6ops-incremental-cgn &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(just completed WGLC)<br></blockquote></blockquote><blockquote type="cite"><b
 lockquot
="Apple-tab-span" style="white-space:pre">	</span>draft-ietf-v6ops-tunnel-loops &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(in WGLC)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre">	</span>draft-ietf-v6ops-v6-in-mobile-networks &nbsp;&nbsp;&nbsp;(October 11-24)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre">	</span>draft-ietf-v6ops-3177bis-48boundary &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(Oct 24-Nov 7)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">In IESG discu ssion:<span class="Apple-tab-span" style="white-space:pre">	</span>draft-gundavelli-v6ops-l2-unicast-04<span class="Apple-tab-span" style="white-space:pre">	</span><br></blockquote></blockquote><blockquote type="cite"><bloc
 kquote t
pple-tab-span" style="white-space:pre">	</span>draft-ietf-v6ops-cpe-simple-security-14<span class="Apple-tab-span" style="white-space:pre">	</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre">	</span>draft-ietf-v6ops-ra-guard-08<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre">	</span>draft-ietf-v6ops-rogue-ra-01 (Needs an updated draft from Tim)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">RFC Editor Queue<span class="Apple-tab-span" style="white-space:pre">	</span><span class="Apple-tab-span" style="white-space:pre">	</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre">	</span>draft-ietf-v6ops-ipv6-cpe-router-07<br></b
 lockquot
e type="cite"><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre">	</span>draft-ietf-v6ops-isp-scenarios-00<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre">	</span>draft-thaler-v6ops-teredo-extensions-08<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Dead?<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span class="Apple-tab-span" style="white-space:pre">	</span>draft-sarikaya-v6ops-prefix-delegation-01<span class="Apple-tab-span" style="white-space:pre">	</span><span class="Apple-tab-span" style="white-space:pre">	</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Recent RFCs:<br></blockquote></blockquote><blockquote type="c
 ite"><bl
</blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="http://www.ietf.org/rfc/rfc5963.txt">http://www.ietf.org/rfc/rfc5963.txt</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">5963 IPv6 Deployment in Internet Exchange Points (IXPs). R. Gagliano.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> &nbsp;&nbsp;&nbsp;August 2010. (Format: TXT=22786 bytes) (Status: INFORMATIONAL)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="http://www.ietf.org/rfc/rfc5991.txt">http://www.ietf.org/rfc/rfc5991.txt</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">5991 Teredo Security Updates. D. Thaler, S. Krishnan, J. Hoagland.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> &nbsp;&nbsp;&nbsp;September 2010. (Format: TXT=20847 bytes) (
 Updates 
ockquote></blockquote><blockquote type="cite"><blockquote type="cite"> &nbsp;&nbsp;&nbsp;PROPOSED STANDARD)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="http://www.ietf.org/rfc/rfc6018.txt">http://www.ietf.org/rfc/rfc6018.txt</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">6018 IPv4 and IPv6 Greynets. F. Baker, W. Harrop, G. Armitage.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"> &nbsp;&nbsp;&nbsp;September 2010. (Format: TXT=21541 bytes) (Status: INFORMATIONAL)<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">_______________________________________________<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">v6ops mailing list<br></blockquote></blockquote><blockquote
  type="c
te"><a href="https://www.ietf.org/mailman/listinfo/v6ops">https://www.ietf.org/mailman/listinfo/v6ops</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">_______________________________________________<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">v6ops mailing list<br></blockquote><blockquote type="cite"><a href="mailto:v6ops@ietf.org">v6ops@ietf.org</a><br></blockquote><blockquote type="cite"><a href="https://www.ietf.org/mailman/listinfo/v6ops">https://www.ietf.org/mailman/listinfo/v6ops</a><br></blockquote><br></div></blockquote></div><br></body></html>

--Boundary_(ID_Qx2GOIUqi1cwOWLBTbpsQw)--

From magnus.westerlund@ericsson.com  Mon Oct  4 05:46:32 2010
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 256353A6C9B for <v6ops@core3.amsl.com>; Mon,  4 Oct 2010 05:46:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.158
X-Spam-Level: 
X-Spam-Status: No, score=-106.158 tagged_above=-999 required=5 tests=[AWL=-0.159, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a1djR9gL1+Dp for <v6ops@core3.amsl.com>; Mon,  4 Oct 2010 05:46:31 -0700 (PDT)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id BB1323A6B41 for <v6ops@ietf.org>; Mon,  4 Oct 2010 05:46:30 -0700 (PDT)
X-AuditID: c1b4fb3d-b7cbfae00000264e-03-4ca9ccdc481e
Received: from esealmw127.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 94.2D.09806.CDCC9AC4; Mon,  4 Oct 2010 14:47:24 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 4 Oct 2010 14:47:24 +0200
Received: from [147.214.183.82] ([147.214.183.82]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 4 Oct 2010 14:47:24 +0200
Message-ID: <4CA9CCDB.2040006@ericsson.com>
Date: Mon, 04 Oct 2010 14:47:23 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sv-SE; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: v6ops@ietf.org
References: <1D12ED02-D4CB-4811-A59F-3823C82E22D9@apple.com>
In-Reply-To: <1D12ED02-D4CB-4811-A59F-3823C82E22D9@apple.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 04 Oct 2010 12:47:24.0488 (UTC) FILETIME=[4B184C80:01CB63C2]
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [v6ops] draft-ietf-v6ops-cpe-simple-security
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Oct 2010 12:46:32 -0000

Hi,

I just want to mention that I am satisfied with the resolution of my issue.

Cheers

Magnus

james woodyatt skrev 2010-09-30 03:50:
> everyone--
> 
> After conferring offline with the Julien Laganier, Arnaud Ebalard, Magnus Westerlund and Rémi Després, I think the -14 revision that I just posted may turn out to be the final draft.  Please see <http://tools.ietf.org/html/draft-ietf-v6ops-cpe-simple-security> for the differences going from -12 to -13 and from -13 to -14.  Highlights:
> 
>  - Improved normative and informative text for Mobility Support.
> 
>  - Clarified normative text for Encapsulated Security Payload to
>    cover path MTU discovery.
> 
>  - Improved normative text for generic upper-layer transports.
> 
>  - Explicitly note that the DEFAULT configuration of "transparent"
>    mode is optional.
> 
>  - Mention RFC 5386 in security considerations.
> 
>  - Minor editorial nits.
> 
> If there are still technical and editorial issues with the draft, then I don't know what they might be at this point.
> 
> 
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, communications engineering
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

From fred@cisco.com  Mon Oct  4 06:00:08 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CCEBF3A6F8D for <v6ops@core3.amsl.com>; Mon,  4 Oct 2010 06:00:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.999
X-Spam-Level: 
X-Spam-Status: No, score=-109.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4H0ldpvHPk-f for <v6ops@core3.amsl.com>; Mon,  4 Oct 2010 06:00:07 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 659873A6F8C for <v6ops@ietf.org>; Mon,  4 Oct 2010 06:00:07 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAHNsqUxAZnwM/2dsb2JhbACiQXGlEptign6CSQSKQIMC
X-IronPort-AV: E=Sophos;i="4.57,278,1283731200"; d="scan'208";a="166550302"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 04 Oct 2010 13:00:59 +0000
Received: from Freds-Computer.local (rtp-vpn2-1853.cisco.com [10.82.247.64]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o94D0oBw004793; Mon, 4 Oct 2010 13:00:52 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Mon, 04 Oct 2010 09:00:59 -0400
X-PGP-Universal: processed; by Freds-Computer.local on Mon, 04 Oct 2010 09:00:59 -0400
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com>
Date: Mon, 4 Oct 2010 09:00:42 -0400
Message-Id: <54BED382-7B8C-4C23-826C-054B31333970@cisco.com>
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com>
To: Tina TSOU <tena@huawei.com>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Oct 2010 13:00:08 -0000

On Oct 4, 2010, at 6:00 AM, Tina TSOU wrote:

> Thank you for the arrangement. You made the agenda so quickly compared =
to the WG I chair;)
>=20
> Some comments are below.
>=20
> 1)
> "Welcome and introduction from the China Network Operators Group
> Dong Yan, CNNOG and CNISP"
>=20
> What's the implication from the China NOG introduction? In this case, =
do Asia, Europe and Oceania NOG also need to be given the introduction? =
These operators from North America, Europe, and Asia consider IETF is a =
global and original organization for IPv4 to IPv6 transition.

It's not unusual to have a local group present a greeting, although it =
is more commonly done in the plenary. I sought this out as some on =
v4tov6transition seemed unaware of the local operational organizations.

> What's the relationship between IETF WG v6ops and xNOG in v4 to v6 =
transition area?

v6ops is a point of interface between the operational community and the =
IETF community; the operators can touch base with us anywhere they like, =
of course, but here they can explicitly get IETF involvement in their =
issues. The various RIR and *NOG communities, as in IPv4 networking, are =
strictly operational and deal with matters of operational policy and =
practice.

> 2)
> "Problem Statements of IPv6 Transition of ISP
>      17-Sep-10, <draft-lee-v4v6tran-problem-02.txt>
> Framework for IP Version Transition Scenarios
>      18-Aug-10, <draft-carpenter-v4v6tran-framework-00.txt>"
>=20
> We have fully discussed the PS I-D and framework I-D in the v4v6tran =
WebEx meeting.=20
> The target is a set of use cases I-Ds and transition guides I-Ds for =
broadband, cable, and mobile scenarios, which are aimed for information =
RFCs.=20
> Do the PS I-D and framework I-D need to be discussed again in WG =
v6ops? Are they also aimed for informational RFCs? I don't have strong =
opinion about this.

The authors haven't told me what their plans for the documents are. You =
asked for time to discuss them; I assume the authors would like to =
discuss them. I'll let the authors tell me if what further plans they =
have. But since, per Ron, this work is coming into v6ops, it seems like =
the v4v6tran group might want to talk with v6ops.

> iv>
> "Use Case For IPv6 Transition For a Large-Scale Broadband Service =
Provider
>      14-Sep-10, <draft-tian-v4v6tran-broadband-sp-usecase-00.txt>"
> I don't know whether Can-Can would like to present this. I think it =
has been replaced by draft-huang-v6ops-v4v6tran-bb-usecase.

Thanks for the heads-up; can-can had not communicated that to me.=20

> 4)
> "IPv6 Transition Guide Broadband Access
>      15-Sep-10, <draft-yang-v4v6tran-ipv6-transition-guide-00.txt>
> IPv6 Transition Guide For A Large-scale Broadband Network
>      27-Sep-10, =
<draft-yang-v6ops-v4v6tran-bb-transition-guide-00.txt>"
> I think only latter will be presented in WG v6ops Beijing meeting.
> The latter is not China Telecom only any more. It is the initial =
version to invite contribution from all broadband networks. 90% of China =
Telecom's existing access network is PPPoE access network, which may be =
similar to some of the operators. They will focus on this type. This I-D =
leave space fo ribute for existing DHCP access network.=20

Tell you what. I'll drop a note to each author I=20


From tena@huawei.com  Mon Oct  4 06:25:55 2010
Return-Path: <tena@huawei.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 36B4F3A6F86 for <v6ops@core3.amsl.com>; Mon,  4 Oct 2010 06:25:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.028
X-Spam-Level: 
X-Spam-Status: No, score=-100.028 tagged_above=-999 required=5 tests=[AWL=-0.133, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kvzcRHJd9RVH for <v6ops@core3.amsl.com>; Mon,  4 Oct 2010 06:25:50 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 03FB23A6CAA for <v6ops@ietf.org>; Mon,  4 Oct 2010 06:25:47 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9R005KXPC6J9@szxga03-in.huawei.com> for v6ops@ietf.org; Mon, 04 Oct 2010 21:26:30 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9R0039NPC6QP@szxga03-in.huawei.com> for v6ops@ietf.org; Mon, 04 Oct 2010 21:26:30 +0800 (CST)
Received: from [192.168.1.4] ([113.116.36.142]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L9R00HXCPC6CO@szxml01-in.huawei.com>; Mon, 04 Oct 2010 21:26:30 +0800 (CST)
Date: Mon, 04 Oct 2010 21:26:29 +0800
From: Tina TSOU <tena@huawei.com>
In-reply-to: <54BED382-7B8C-4C23-826C-054B31333970@cisco.com>
To: Fred Baker <fred@cisco.com>
Message-id: <C1805EE8-709A-4ED9-A0DC-BD2DC94AB535@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <54BED382-7B8C-4C23-826C-054B31333970@cisco.com>
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Oct 2010 13:25:55 -0000

B. R.
Tina
http://tinatsou.weebly.com




On Oct 4, 2010, at 9:00 PM, Fred Baker wrote:

>
> On Oct 4, 2010, at 6:00 AM, Tina TSOU wrote:
>
>> Thank you for the arrangement. You made the agenda so quickly  
>> compared to the WG I chair;)
>>
>> Some comments are below.
>>
>> 1)
>> "Welcome and introduction from the China Network Operators Group
>> Dong Yan, CNNOG and CNISP"
>>
>> What's the implication from the China NOG introduction? In this  
>> case, do Asia, Europe and Oceania NOG also need to be given the  
>> introduction? These operators from North America, Europe, and Asia  
>> consider IETF is a global and original organization for IPv4 to  
>> IPv6 transition.
>
> It's not unusual to have a local group present a greeting, although  
> it is more commonly done in the plenary. I sought this out as some  
> on v4tov6transition seemed unaware of the local operational  
> organizations.
>
>> What's the relationship between IETF WG v6ops and xNOG in v4 to v6  
>> transition area?
>
> v6ops is a point of interface between the operational community and  
> the IETF community; the operators can touch base with us anywhere  
> they like, of course, but here they can explicitly get IETF  
> involvement in their issues.
I like this statement.
> The various RIR and *NOG communities, as in IPv4 networking, are  
> strictly operational and deal with matters of operational policy and  
> practice.
>
>> 2)
>> "Problem Statements of IPv6 Transition of ISP
>>     17-Sep-10, <draft-lee-v4v6tran-problem-02.txt>
>> Framework for IP Version Transition Scenarios
>>     18-Aug-10, <draft-carpenter-v4v6tran-framework-00.txt>"
>>
>> We have fully discussed the PS I-D and framework I-D in the  
>> v4v6tran WebEx meeting.
>> The target is a set of use cases I-Ds and transition guides I-Ds  
>> for broadband, cable, and mobile scenarios, which are aimed for  
>> information RFCs.
>> Do the PS I-D and framework I-D need to be discussed again in WG  
>> v6ops? Are they also aimed for informational RFCs? I don't have  
>> strong opinion about this.
>
> The authors haven't told me what their plans for the documents are.  
> You asked for time to discuss them; I assume the authors would like  
> to discuss them. I'll let the authors tell me if what further plans  
> they have. But since, per Ron, this work is coming into v6ops, it  
> seems like the v4v6tran group might want to talk with v6ops.
>
>> iv>
>> "Use Case For IPv6 Transition For a Large-Scale Broadband Service  
>> Provider
>>     14-Sep-10, <draft-tian-v4v6tran-broadband-sp-usecase-00.txt>"
>> I don't know whether Can-Can would like to present this. I think it  
>> has been replaced by draft-huang-v6ops-v4v6tran-bb-usecase.
>
> Thanks for the heads-up; can-can had not communicated that to me.
>
>> 4)
>> "IPv6 Transition Guide Broadband Access
>>     15-Sep-10, <draft-yang-v4v6tran-ipv6-transition-guide-00.txt>
>> IPv6 Transition Guide For A Large-scale Broadband Network
>>     27-Sep-10, <draft-yang-v6ops-v4v6tran-bb-transition- 
>> guide-00.txt>"
>> I think only latter will be presented in WG v6ops Beijing meeting.
>> The latter is not China Telecom only any more. It is the initial  
>> version to invite contribution from all broadband networks. 90% of  
>> China Telecom's existing access network is PPPoE access network,  
>> which may be similar to some of the operators. They will focus on  
>> this type. This I-D leave space fo ribute for existing DHCP access  
>> network.
>
> Tell you what. I'll drop a note to each author I
>


From remi.despres@free.fr  Mon Oct  4 06:49:16 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E9B8D3A6F86 for <v6ops@core3.amsl.com>; Mon,  4 Oct 2010 06:49:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.125
X-Spam-Level: 
X-Spam-Status: No, score=-1.125 tagged_above=-999 required=5 tests=[AWL=0.224,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6SWzJy+i7TVV for <v6ops@core3.amsl.com>; Mon,  4 Oct 2010 06:49:16 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.19]) by core3.amsl.com (Postfix) with ESMTP id BF8453A6C91 for <v6ops@ietf.org>; Mon,  4 Oct 2010 06:49:15 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2318.sfr.fr (SMTP Server) with ESMTP id 68B117000097 for <v6ops@ietf.org>; Mon,  4 Oct 2010 15:50:10 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2318.sfr.fr (SMTP Server) with ESMTP id 393317000091 for <v6ops@ietf.org>; Mon,  4 Oct 2010 15:50:09 +0200 (CEST)
X-SFR-UUID: 20101004135010234.393317000091@msfrf2318.sfr.fr
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1081)
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <4CA9CCDB.2040006@ericsson.com>
Date: Mon, 4 Oct 2010 15:50:09 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C5CCB14-0E20-442C-B87F-F65E4D8EAC87@free.fr>
References: <1D12ED02-D4CB-4811-A59F-3823C82E22D9@apple.com> <4CA9CCDB.2040006@ericsson.com>
To: v6ops v6ops <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1081)
Subject: Re: [v6ops] draft-ietf-v6ops-cpe-simple-security
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Oct 2010 13:49:17 -0000

Le 4 oct. 2010 =E0 14:47, Magnus Westerlund a =E9crit :

> Hi,
>=20
> I just want to mention that I am satisfied with the resolution of my =
issue.

So am I.
Thanks James.
RD


>=20
> Cheers
>=20
> Magnus
>=20
> james woodyatt skrev 2010-09-30 03:50:
>> everyone--
>>=20
>> After conferring offline with the Julien Laganier, Arnaud Ebalard, =
Magnus Westerlund and R=E9mi Despr=E9s, I think the -14 revision that I =
just posted may turn out to be the final draft.  Please see =
<http://tools.ietf.org/html/draft-ietf-v6ops-cpe-simple-security> for =
the differences going from -12 to -13 and from -13 to -14.  Highlights:
>>=20
>> - Improved normative and informative text for Mobility Support.
>>=20
>> - Clarified normative text for Encapsulated Security Payload to
>>   cover path MTU discovery.
>>=20
>> - Improved normative text for generic upper-layer transports.
>>=20
>> - Explicitly note that the DEFAULT configuration of "transparent"
>>   mode is optional.
>>=20
>> - Mention RFC 5386 in security considerations.
>>=20
>> - Minor editorial nits.
>>=20
>> If there are still technical and editorial issues with the draft, =
then I don't know what they might be at this point.
>>=20
>>=20
>> --
>> james woodyatt <jhw@apple.com>
>> member of technical staff, communications engineering
>>=20
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>>=20
>=20
>=20
> --=20
>=20
> Magnus Westerlund
>=20
> ----------------------------------------------------------------------
> Multimedia Technologies, Ericsson Research EAB/TVM
> ----------------------------------------------------------------------
> Ericsson AB                | Phone  +46 10 7148287
> F=E4r=F6gatan 6                | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops



From randy@psg.com  Mon Oct  4 14:11:57 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F41F43A70C5 for <v6ops@core3.amsl.com>; Mon,  4 Oct 2010 14:11: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.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O3UxDvil99Ik for <v6ops@core3.amsl.com>; Mon,  4 Oct 2010 14:11:39 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 357D73A70CC for <v6ops@ietf.org>; Mon,  4 Oct 2010 14:11:39 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1P2sKV-0009zm-Fu; Mon, 04 Oct 2010 21:12:15 +0000
Date: Tue, 05 Oct 2010 06:12:13 +0900
Message-ID: <m2k4lxwtle.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Tina TSOU <tena@huawei.com>
In-Reply-To: <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com>
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Oct 2010 21:11:58 -0000

> Thank you for the arrangement. You made the agenda so quickly compared
> to the WG I chair;)

i am lost here.  what wg is that?

> What's the relationship between IETF WG v6ops and xNOG in v4 to v6
> transition area?

operators participate in the ietf.  and protocol geeks participate in
*nogs.  the internet is not the itu, we're an open culture.  yes, i tcan
be a bit chaotic and confusing, but the result is carrying this email to
you :)

> We have fully discussed the PS I-D and framework I-D in the v4v6tran  
> WebEx meeting.
> ...
and many more

i would hope your informal design group would present their discussions
at the meeting in beijing as part of the normal agenda.

randy

From suresh.krishnan@ericsson.com  Mon Oct  4 21:00:02 2010
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A37F3A6E10 for <v6ops@core3.amsl.com>; Mon,  4 Oct 2010 21:00:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.508
X-Spam-Level: 
X-Spam-Status: No, score=-102.508 tagged_above=-999 required=5 tests=[AWL=0.091, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id COfH0F4ZaJmd for <v6ops@core3.amsl.com>; Mon,  4 Oct 2010 21:00:00 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id B741E3A6DD4 for <v6ops@ietf.org>; Mon,  4 Oct 2010 21:00:00 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id o954G373021121; Mon, 4 Oct 2010 23:16:04 -0500
Received: from [142.133.10.113] (147.117.20.213) by eusaamw0706.eamcs.ericsson.se (147.117.20.91) with Microsoft SMTP Server id 8.2.234.1; Tue, 5 Oct 2010 00:00:49 -0400
Message-ID: <4CAAA2B5.1070901@ericsson.com>
Date: Mon, 4 Oct 2010 23:59:49 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: v6ops@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [v6ops] Review of draft-sarikaya-v6ops-prefix-delegation-01.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Oct 2010 04:00:02 -0000

Hi,
   I have read the draft draft-sarikaya-v6ops-prefix-delegation-01.txt 
and I have a few comments.

Meta-comment
============

It is unclear what the goal of this draft is

a) Is it expected to be a recommendation from the IETF to 3GPP, WiMAX 
forum etc. on how to perform DHCPv6-PD in their networks?

(or)

b) Is it an Informational document expected to document how DHCPv6-PD is 
being used in these networks?

There is more clarity required here.

Section 3.1
===========

* First paragraph: The text about the relay function is completely 
wrong. If the AR and the DHCPv6 server are not directly connected, there 
needs to be at least one relay between them but the relay is certainly 
not the AR. Can you please rewrite this?

* Same comment about the relay behavior for the sequence diagram. The AR 
  either sends Solicit messages (or) relays Solicit messages from 
somebody else. It does not relay-forward its own Solicit messages.

* Step 2: Need to refer to RFC3633 for describing how to create the IA_PD.

* Step 7: How is the prefix for the RA derived from the delegated prefix?

Section 3.2
===========

* Requires a different sequence diagram showing DHCPv6 messages 
originating from the MN and relay messages from the AR. This cannot be 
shared with Section 3.1


* Second paragraph
"AR as DHCP Relay forwards DHCP Request message in DHCP Relay
  Option and adds Option 82 to the message [RFC3046]"

This does not make sense at all. Option 82 is for DHCPv4, not for 
DHCPv6. What are you trying to convey here?

Section 3.5
===========

* Is this done after the UE gets a /64 prefix or a /128 address as 
described in the earlier sections or is it done before/in parallel?

Section 3.5.2
==============

* Last paragraph

RAs cannot be used to deliver the prefixes to the UE for further 
assignment downstream. Please clarify.


Section 3.6.2
==============

s/IMNI/IMSI/

Section 4
==========

* It is not clear what the AR needs to do with a Delegated-IPv6-Prefix 
that is received in a AAA message. How does the AR delegate this to the MN?


Thanks
Suresh



From tena@huawei.com  Mon Oct  4 21:50:48 2010
Return-Path: <tena@huawei.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 46CA03A6C7C for <v6ops@core3.amsl.com>; Mon,  4 Oct 2010 21:50:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.029
X-Spam-Level: 
X-Spam-Status: No, score=-100.029 tagged_above=-999 required=5 tests=[AWL=-0.134, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9OU-fey0xeFD for <v6ops@core3.amsl.com>; Mon,  4 Oct 2010 21:50:47 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 2991C3A6BCA for <v6ops@ietf.org>; Mon,  4 Oct 2010 21:50:47 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9S007F0W5VAZ@szxga02-in.huawei.com> for v6ops@ietf.org; Tue, 05 Oct 2010 12:51:31 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9S000OOW5V3C@szxga02-in.huawei.com> for v6ops@ietf.org; Tue, 05 Oct 2010 12:51:31 +0800 (CST)
Received: from [192.168.5.101] ([113.116.36.142]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L9S003K3W5UQO@szxml01-in.huawei.com>; Tue, 05 Oct 2010 12:51:31 +0800 (CST)
Date: Tue, 05 Oct 2010 12:51:29 +0800
From: Tina TSOU <tena@huawei.com>
In-reply-to: <m2k4lxwtle.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
Message-id: <7A072CBD-C19D-42A0-8897-46DC09DD39A8@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <m2k4lxwtle.wl%randy@psg.com>
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Oct 2010 04:50:48 -0000

B. R.
Tina
http://tinatsou.weebly.com




On Oct 5, 2010, at 5:12 AM, Randy Bush wrote:

>> Thank you for the arrangement. You made the agenda so quickly  
>> compared
>> to the WG I chair;)
>
> i am lost here.  what wg is that?
WG hokey. It is irrelevant, just my praise to Fred about his quickness.
>
>> What's the relationship between IETF WG v6ops and xNOG in v4 to v6
>> transition area?
>
> operators participate in the ietf.  and protocol geeks participate in
> *nogs.  the internet is not the itu, we're an open culture.  yes, i  
> tcan
> be a bit chaotic and confusing, but the result is carrying this  
> email to
> you :)
I asked this question simply because there was comment saying this  
kind of operational work should go to *NOG, not IETF.
Fred gave the simple answer that "the operators can touch base with us  
anywhere they like, of course, but here they can explicitly get IETF  
involvement in their issues. "
So everybody is happy now.
*NOG, IETF, ITU, ETSI are all part of Internet. Internet is  
everywhere. Everybody is equal, having fun right to participate in  
anywhere he or she likes.
>
>> We have fully discussed the PS I-D and framework I-D in the v4v6tran
>> WebEx meeting.
>> ...
> and many more
>
> i would hope your informal design group would present their  
> discussions
> at the meeting in beijing as part of the normal agenda.
Agreed.
>
> randy


From tena@huawei.com  Mon Oct  4 22:51:57 2010
Return-Path: <tena@huawei.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F09B53A6DF2 for <v6ops@core3.amsl.com>; Mon,  4 Oct 2010 22:51:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.025
X-Spam-Level: 
X-Spam-Status: No, score=-100.025 tagged_above=-999 required=5 tests=[AWL=-0.130, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jaozHpmul-E0 for <v6ops@core3.amsl.com>; Mon,  4 Oct 2010 22:51:54 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 085C63A6B2A for <v6ops@ietf.org>; Mon,  4 Oct 2010 22:51:54 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9S00FLSYZQEQ@szxga01-in.huawei.com> for v6ops@ietf.org; Tue, 05 Oct 2010 13:52:38 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9S00K03YZQ19@szxga01-in.huawei.com> for v6ops@ietf.org; Tue, 05 Oct 2010 13:52:38 +0800 (CST)
Received: from [192.168.5.101] ([113.116.36.142]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L9S00G43YZPD9@szxml01-in.huawei.com>; Tue, 05 Oct 2010 13:52:38 +0800 (CST)
Date: Tue, 05 Oct 2010 13:52:34 +0800
From: Tina TSOU <tena@huawei.com>
In-reply-to: <54BED382-7B8C-4C23-826C-054B31333970@cisco.com>
To: Fred Baker <fred@cisco.com>
Message-id: <641BFD35-D097-4E22-8A71-F3E75EB7CD4A@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <54BED382-7B8C-4C23-826C-054B31333970@cisco.com>
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Oct 2010 05:51:57 -0000

B. R.
Tina
http://tinatsou.weebly.com




On Oct 4, 2010, at 9:00 PM, Fred Baker wrote:

>
> On Oct 4, 2010, at 6:00 AM, Tina TSOU wrote:
>
>> Thank you for the arrangement. You made the agenda so quickly  
>> compared to the WG I chair;)
>>
>> Some comments are below.
0)
"IPv4 to IPv6 Deployment/Coexistence Discussion"
Would it be more precise to say "IPv4 to IPv6 Transition Discussion"?
>>
>> 1)
>> "Welcome and introduction from the China Network Operators Group
>> Dong Yan, CNNOG and CNISP"
>>
>> What's the implication from the China NOG introduction? In this  
>> case, do Asia, Europe and Oceania NOG also need to be given the  
>> introduction? These operators from North America, Europe, and Asia  
>> consider IETF is a global and original organization for IPv4 to  
>> IPv6 transition.
>
> It's not unusual to have a local group present a greeting, although  
> it is more commonly done in the plenary. I sought this out as some  
> on v4tov6transition seemed unaware of the local operational  
> organizations.
>
>> What's the relationship between IETF WG v6ops and xNOG in v4 to v6  
>> transition area?
>
> v6ops is a point of interface between the operational community and  
> the IETF community; the operators can touch base with us anywhere  
> they like, of course, but here they can explicitly get IETF  
> involvement in their issues. The various RIR and *NOG communities,  
> as in IPv4 networking, are strictly operational and deal with  
> matters of operational policy and practice.
>
>> 2)
>> "Problem Statements of IPv6 Transition of ISP
>>     17-Sep-10, <draft-lee-v4v6tran-problem-02.txt>
>> Framework for IP Version Transition Scenarios
>>     18-Aug-10, <draft-carpenter-v4v6tran-framework-00.txt>"
>>
>> We have fully discussed the PS I-D and framework I-D in the  
>> v4v6tran WebEx meeting.
>> The target is a set of use cases I-Ds and transition guides I-Ds  
>> for broadband, cable, and mobile scenarios, which are aimed for  
>> information RFCs.
>> Do the PS I-D and framework I-D need to be discussed again in WG  
>> v6ops? Are they also aimed for informational RFCs? I don't have  
>> strong opinion about this.
>
> The authors haven't told me what their plans for the documents are.  
> You asked for time to discuss them; I assume the authors would like  
> to discuss them. I'll let the authors tell me if what further plans  
> they have. But since, per Ron, this work is coming into v6ops, it  
> seems like the v4v6tran group might want to talk with v6ops.
I agree with you. Let's keep the Problem Statement I-D and Framework I- 
D in the v6ops Beijing agenda. They could also aimed for informational  
RFCs.
>
>> iv>
>> "Use Case For IPv6 Transition For a Large-Scale Broadband Service  
>> Provider
>>     14-Sep-10, <draft-tian-v4v6tran-broadband-sp-usecase-00.txt>"
>> I don't know whether Can-Can would like to present this. I think it  
>> has been replaced by draft-huang-v6ops-v4v6tran-bb-usecase.
>
> Thanks for the heads-up; can-can had not communicated that to me.
The whole China is in 7 days of golden week of Oct 1st to 7th. She is  
as well.
>
>> 4)
>> "IPv6 Transition Guide Broadband Access
>>     15-Sep-10, <draft-yang-v4v6tran-ipv6-transition-guide-00.txt>
>> IPv6 Transition Guide For A Large-scale Broadband Network
>>     27-Sep-10, <draft-yang-v6ops-v4v6tran-bb-transition- 
>> guide-00.txt>"
>> I think only latter will be presented in WG v6ops Beijing meeting.
>> The latter is not China Telecom only any more. It is the initial  
>> version to invite contribution from all broadband networks. 90% of  
>> China Telecom's existing access network is PPPoE access network,  
>> which may be similar to some of the operators. They will focus on  
>> this type. This I-D leave space fo ribute for existing DHCP access  
>> network.
>
> Tell you what. I'll drop a note to each author I
>


From fred@cisco.com  Tue Oct  5 03:15:20 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A4283A6F0C for <v6ops@core3.amsl.com>; Tue,  5 Oct 2010 03:15:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.186
X-Spam-Level: 
X-Spam-Status: No, score=-110.186 tagged_above=-999 required=5 tests=[AWL=-0.187, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WyQUCzFVCzSe for <v6ops@core3.amsl.com>; Tue,  5 Oct 2010 03:15:18 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 9D3A13A6F08 for <v6ops@ietf.org>; Tue,  5 Oct 2010 03:15:18 -0700 (PDT)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEADeYqkyrRN+K/2dsb2JhbACiQ3GlAJw5hUcEikCDAg
X-IronPort-AV: E=Sophos;i="4.57,283,1283731200"; d="scan'208";a="368091730"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-1.cisco.com with ESMTP; 05 Oct 2010 10:16:03 +0000
Received: from Freds-Computer.local (sjc-vpn7-195.cisco.com [10.21.144.195]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o95AFM0b005341; Tue, 5 Oct 2010 10:15:29 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Tue, 05 Oct 2010 06:15:55 -0400
X-PGP-Universal: processed; by Freds-Computer.local on Tue, 05 Oct 2010 06:15:55 -0400
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <641BFD35-D097-4E22-8A71-F3E75EB7CD4A@huawei.com>
Date: Tue, 5 Oct 2010 06:14:18 -0400
Message-Id: <94D16C01-3A30-4354-AD69-597AA5A7D103@cisco.com>
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <54BED382-7B8C-4C23-826C-054B31333970@cisco.com> <641BFD35-D097-4E22-8A71-F3E75EB7CD4A@huawei.com>
To: Tina TSOU <tena@huawei.com>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Oct 2010 10:15:20 -0000

On Oct 5, 2010, at 1:52 AM, Tina TSOU wrote:

> 0)
> "IPv4 to IPv6 Deployment/Coexistence Discussion"
> Would it be more precise to say "IPv4 to IPv6 Transition Discussion"?

That is a semantic question. Let me give you my view.

In the long term, there is a transition going on. The word "transition" =
signifies the entire change that will happen to something; for example, =
if I am driving and change lanes, the "transition" from one lane to =
another involves changing the direction of the car relative to the road, =
a period of time during which the car is to come extent in one lane and =
to some extent in another, and finally a period of time in which the car =
is only in the new lane (and presumably adjusts course to stay in it). =
Similarly, the transition of the Internet from IPv4 to IPv6 involves =
either deploying a new IPv6-only network (sudden change) or the process =
of (a) turning IPv6 on in one's existing IPv4 network (deployment), (b) =
existing with both on for a period of time (coexistence), and turning =
IPv4 off (transition).

For those who, like CERNET2, T-mobile, and Sprint, simply turn up a new =
network or its equivalent running only IPv6, more power to them. They =
will deal with issues of translation, and those issues will have a home =
in v6ops.

For most networks, it will be first the deployment process, which =
draft-lee-v4v6tran-problem addresses in detail. How should prefixes be =
allocated? If equipment cannot be readily upgraded but deployment is =
urgent, what temporary measures can help in deploying IPv6 as a service =
while those upgrades happen under the hood? What security issues have to =
be addressed?=20

With IPv6 turned on in the network, there are the questions Cancan has =
discussed in some detail - the fact that the ISP has turned on IPv6 =
doesn't mean that every user has upgraded their CPE or turned IPv6 on in =
their network. Since they are using IPv4 in an IPv4+IPv6 network, those =
are coexistence issues.=20

There will be issues such as Seiichi has alluded to, with operating =
systems choosing their peer addresses to connect to without regard to =
end to end connectivity issues (apple) or taking several seconds per =
attempt ratcheting through the choices. These will be operational issues =
in the network (can we get the neighboring network to not be a walled =
garden when our roaming customers are accessing our network's =
resources?), and they have a home here.

And eventually it will come time to turn IPv4 off. At that point, if =
nothing else, there will be some applications that are simply legacy =
applications. Dealing with those will be transition issues.

Yes, we will deal with transition issues. Eventually. Right now, I think =
there are more networks figuring out how to turn IPv6 on and how to get =
it to run they way they would like than there are networks turning IPv4 =
off.

So, yes, I don't know the timeframe, but we will be dealing with =
transition issues. Right now, what I'm hearing from the v4v6tran folks =
is discussion of deployment and coexistence issues.=

From fred@cisco.com  Tue Oct  5 03:20:32 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 173533A6D7E for <v6ops@core3.amsl.com>; Tue,  5 Oct 2010 03:20:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.925
X-Spam-Level: 
X-Spam-Status: No, score=-109.925 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A6TgzcCgkJoE for <v6ops@core3.amsl.com>; Tue,  5 Oct 2010 03:20:31 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 142AF3A6CAD for <v6ops@ietf.org>; Tue,  5 Oct 2010 03:20:31 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEACaZqkyrR7H+/2dsb2JhbACiQ3GlBJw5hUcEikCDAg
X-IronPort-AV: E=Sophos;i="4.57,283,1283731200"; d="scan'208";a="195976617"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-4.cisco.com with ESMTP; 05 Oct 2010 10:21:28 +0000
Received: from Freds-Computer.local (sjc-vpn7-195.cisco.com [10.21.144.195]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o95AKvQM007373; Tue, 5 Oct 2010 10:21:16 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Tue, 05 Oct 2010 06:21:24 -0400
X-PGP-Universal: processed; by Freds-Computer.local on Tue, 05 Oct 2010 06:21:24 -0400
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <641BFD35-D097-4E22-8A71-F3E75EB7CD4A@huawei.com>
Date: Tue, 5 Oct 2010 06:20:25 -0400
Message-Id: <C165683A-1C03-415A-806F-674620AB607B@cisco.com>
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <54BED382-7B8C-4C23-826C-054B31333970@cisco.com> <641BFD35-D097-4E22-8A71-F3E75EB7CD4A@huawei.com>
To: Tina TSOU <tena@huawei.com>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Oct 2010 10:20:32 -0000

On Oct 5, 2010, at 1:52 AM, Tina TSOU wrote:

> I agree with you. Let's keep the Problem Statement I-D and Framework =
I-D in the v6ops Beijing agenda. They could also aimed for informational =
RFCs.

That will be between the authors of those drafts and the chairs, =
operating within the working group process. You're out of order =
attempting to subvert and direct the working group process.=

From randy@psg.com  Tue Oct  5 03:24:38 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8ECBA3A6F08 for <v6ops@core3.amsl.com>; Tue,  5 Oct 2010 03:24:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.578
X-Spam-Level: 
X-Spam-Status: No, score=-2.578 tagged_above=-999 required=5 tests=[AWL=0.021,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8vT30eJAr8ue for <v6ops@core3.amsl.com>; Tue,  5 Oct 2010 03:24:37 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 988A13A6F1E for <v6ops@ietf.org>; Tue,  5 Oct 2010 03:24:37 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1P34iB-000CSX-3H; Tue, 05 Oct 2010 10:25:31 +0000
Date: Tue, 05 Oct 2010 19:25:27 +0900
Message-ID: <m2lj6dueaw.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Tina TSOU <tena@huawei.com>
In-Reply-To: <7A072CBD-C19D-42A0-8897-46DC09DD39A8@huawei.com>
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <m2k4lxwtle.wl%randy@psg.com> <7A072CBD-C19D-42A0-8897-46DC09DD39A8@huawei.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Oct 2010 10:24:38 -0000

> *NOG, IETF, ITU, ETSI are all part of Internet.

ROFL.  and pluto is part of earth.

randy

From tena@huawei.com  Tue Oct  5 09:03:44 2010
Return-Path: <tena@huawei.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D65D43A6E2E for <v6ops@core3.amsl.com>; Tue,  5 Oct 2010 09:03:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.39
X-Spam-Level: 
X-Spam-Status: No, score=-99.39 tagged_above=-999 required=5 tests=[AWL=-0.759, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, HTML_TAG_BALANCE_BODY=1.263, J_CHICKENPOX_13=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f1X82RzdPLLW for <v6ops@core3.amsl.com>; Tue,  5 Oct 2010 09:03:43 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 575EE3A6E25 for <v6ops@ietf.org>; Tue,  5 Oct 2010 09:03:43 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9T005F9RBIL9@szxga02-in.huawei.com> for v6ops@ietf.org; Wed, 06 Oct 2010 00:04:30 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9T005BPRBIYD@szxga02-in.huawei.com> for v6ops@ietf.org; Wed, 06 Oct 2010 00:04:30 +0800 (CST)
Received: from [192.168.5.101] ([113.116.36.142]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L9T00AXHRBH5K@szxml01-in.huawei.com>; Wed, 06 Oct 2010 00:04:30 +0800 (CST)
Date: Wed, 06 Oct 2010 00:04:21 +0800
From: Tina TSOU <tena@huawei.com>
In-reply-to: <C165683A-1C03-415A-806F-674620AB607B@cisco.com>
To: Fred Baker <fred@cisco.com>
Message-id: <8CAB4B14-B876-4069-A676-60B7CF74E8B3@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: multipart/alternative; boundary="Boundary_(ID_SpK1J01HNU4m3tYyIwqpXA)"
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <54BED382-7B8C-4C23-826C-054B31333970@cisco.com> <641BFD35-D097-4E22-8A71-F3E75EB7CD4A@huawei.com> <C165683A-1C03-415A-806F-674620AB607B@cisco.com>
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Oct 2010 16:03:45 -0000

--Boundary_(ID_SpK1J01HNU4m3tYyIwqpXA)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT


B. R.
Tina
http://tinatsou.weebly.com




On Oct 5, 2010, at 6:20 PM, Fred Baker wrote:

>
> On Oct 5, 2010, at 1:52 AM, Tina TSOU wrote:Eng
>
>> I agree with you. Let's keep the Problem Statement I-D and  
>> Framework I-D in the v6ops Beijing agenda. They could also aimed  
>> for informational RFCs.
>
> That will be between the authors of those drafts and the chairs,  
> operating within the working group process. You're out of order  
> attempting to subvert and direct the working group process.
Yes, agreed. Just my personal view. I have fundamental right to  
express my personal opinion. I should rephrase what I meant due to  
English is not my mother language. My concern was that the problem  
statement creates a set of goals, which logically would be translated  
into WG milestones. Then there is a moral obligation to achieve the  
milestones. Since
an Informational document has no authority in itself. If v6ops decides  
to work on the Problem Statement document, as long as it does not  
block the way of the use cases and transition guides, I am more than  
happy to clap.


--Boundary_(ID_SpK1J01HNU4m3tYyIwqpXA)
Content-type: text/html; charset=US-ASCII
Content-transfer-encoding: 7BIT

<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div apple-content-edited="true"> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); 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: 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="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; lette
 r-spacin
ormal; orphans: 2; 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="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><span class="Apple-style-span" style="font-size: 12px; "><div>B. R.</div><div>Tina</div><div><a href="http://tinatsou.weebly.com">http://tinatsou.weebly.com</a></div><div></div></span></div><div><br></div></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"> </div><br><div><div>On Oct 5, 2010, at 6:20 PM, Fred Baker wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br>On Oct 5, 2010, at 1:52 AM, Tina TSOU wrote:Eng<br><br><blockquote type="cite">I agree with you. Let's keep the Problem Statement I-D and
  Framewo
ng agenda. They could also aimed for informational RFCs.<br></blockquote><br>That will be between the authors of those drafts and the chairs, operating within the working group process. You're out of order attempting to subvert and direct the working group process.</div></blockquote></div>Yes, agreed. Just my personal view. I have fundamental right to express my personal opinion. I should rephrase what I meant due to English is not my mother language. My concern was that the problem statement creates a set of goals, which logically would&nbsp;be translated into WG milestones. Then there is a moral obligation&nbsp;to achieve the milestones. Since<br>an Informational document has no authority in itself. If v6ops decides to work&nbsp;on the Problem Statement document, as long as it does not block the way of the use cases and transition guides, I am more than happy to clap.<br><div><font class="Apple-style-span" face="Cambria" size="4"><span class="Apple-style-span" style="font-s
 ize: 16p
iv></body></html>

--Boundary_(ID_SpK1J01HNU4m3tYyIwqpXA)--

From tena@huawei.com  Tue Oct  5 09:12:49 2010
Return-Path: <tena@huawei.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E902F3A6F0E for <v6ops@core3.amsl.com>; Tue,  5 Oct 2010 09:12:48 -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=[AWL=-0.105,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  J_CHICKENPOX_13=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oFkBAaeGeG4P for <v6ops@core3.amsl.com>; Tue,  5 Oct 2010 09:12:47 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 95D2E3A6F3B for <v6ops@ietf.org>; Tue,  5 Oct 2010 09:12:45 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9T009O1RQKV2@szxga02-in.huawei.com> for v6ops@ietf.org; Wed, 06 Oct 2010 00:13:32 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9T005EMRQKYD@szxga02-in.huawei.com> for v6ops@ietf.org; Wed, 06 Oct 2010 00:13:32 +0800 (CST)
Received: from [192.168.5.101] ([113.116.36.142]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L9T00H6VRQJR1@szxml01-in.huawei.com>; Wed, 06 Oct 2010 00:13:32 +0800 (CST)
Date: Wed, 06 Oct 2010 00:13:23 +0800
From: Tina TSOU <tena@huawei.com>
In-reply-to: <m2lj6dueaw.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
Message-id: <C4C48CC9-EAFB-4D53-9BC7-BC24E13534EF@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <m2k4lxwtle.wl%randy@psg.com> <7A072CBD-C19D-42A0-8897-46DC09DD39A8@huawei.com> <m2lj6dueaw.wl%randy@psg.com>
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Oct 2010 16:12:49 -0000

B. R.
Tina
http://tinatsou.weebly.com




On Oct 5, 2010, at 6:25 PM, Randy Bush wrote:

>> *NOG, IETF, ITU, ETSI are all part of Internet.
>
> ROFL.  and pluto is part of earth.
ROFL. Pluto is NOT part of earth.
Our this discussion is irrelevant to the original question. The  
original question is to make sure that the documents under "IPv4 to  
IPv6 Deployment/Coexistence Discussion" in the agenda is reasonable to  
work in WG v6ops, to answer the comments why they don't go to xNOG, or  
even they go to xNOG, they still want to come to v6ops as well.
>
> randy


From joelja@bogus.com  Tue Oct  5 09:30:36 2010
Return-Path: <joelja@bogus.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E4BC23A6F79 for <v6ops@core3.amsl.com>; Tue,  5 Oct 2010 09:30:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vrz9QDLcvvHi for <v6ops@core3.amsl.com>; Tue,  5 Oct 2010 09:30:34 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id CD7083A6FBA for <v6ops@ietf.org>; Tue,  5 Oct 2010 09:30:33 -0700 (PDT)
Received: from joelja-mac.dhcp.nanog.merit.net (joelja-mac.dhcp.nanog.merit.net [192.35.165.184]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id o95GV75i031925 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 5 Oct 2010 16:31:08 GMT (envelope-from joelja@bogus.com)
Message-ID: <4CAB52CA.1020600@bogus.com>
Date: Tue, 05 Oct 2010 12:31:06 -0400
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: Tina TSOU <tena@huawei.com>
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <m2k4lxwtle.wl%randy@psg.com> <7A072CBD-C19D-42A0-8897-46DC09DD39A8@huawei.com> <m2lj6dueaw.wl%randy@psg.com> <C4C48CC9-EAFB-4D53-9BC7-BC24E13534EF@huawei.com>
In-Reply-To: <C4C48CC9-EAFB-4D53-9BC7-BC24E13534EF@huawei.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Tue, 05 Oct 2010 16:31:11 +0000 (UTC)
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Oct 2010 16:30:37 -0000

On 10/5/10 12:13 PM, Tina TSOU wrote:
> 
> B. R.
> Tina
> http://tinatsou.weebly.com
> 
> 
> 
> 
> On Oct 5, 2010, at 6:25 PM, Randy Bush wrote:
> 
>>> *NOG, IETF, ITU, ETSI are all part of Internet.
>>
>> ROFL.  and pluto is part of earth.
> ROFL. Pluto is NOT part of earth.
> Our this discussion is irrelevant to the original question. The original
> question is to make sure that the documents under "IPv4 to IPv6
> Deployment/Coexistence Discussion" in the agenda is reasonable to work
> in WG v6ops, to answer the comments why they don't go to xNOG, or even
> they go to xNOG, they still want to come to v6ops as well.

I'm at NANOG, yet I will be at IETF in bejing. If I'm a network operator
I don't go to ETSI.

If you want  to provide advice to and recive the same from network
operators you should be involved in places where network operators go.
You (tina) stated in the v6v4trans call that china has no such operator
communities, it does and we thought it relevant to encourage their
participation in this activity such that bilateral exchange of
information can occur.

Myself and Ron Bonica are here at nanog for similar reasons (as is yui lee)

>> randy
> 


From edward.jankiewicz@sri.com  Tue Oct  5 09:34:32 2010
Return-Path: <edward.jankiewicz@sri.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6CF823A6FC4 for <v6ops@core3.amsl.com>; Tue,  5 Oct 2010 09:34:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.313
X-Spam-Level: 
X-Spam-Status: No, score=-1.313 tagged_above=-999 required=5 tests=[AWL=0.133,  BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ySTj9MqPHekL for <v6ops@core3.amsl.com>; Tue,  5 Oct 2010 09:34:31 -0700 (PDT)
Received: from mail1.sri.com (newmail.SRI.COM [128.18.30.17]) by core3.amsl.com (Postfix) with ESMTP id 1CBE23A6C9D for <v6ops@ietf.org>; Tue,  5 Oct 2010 09:34:12 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Received: from [192.168.2.13] ([unknown] [72.68.71.162]) by mail.sri.com (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0L9T00NDYSQKM3J0@mail.sri.com> for v6ops@ietf.org; Tue, 05 Oct 2010 09:35:08 -0700 (PDT)
Message-id: <4CAB53BB.6090705@sri.com>
Date: Tue, 05 Oct 2010 12:35:07 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
To: v6ops@ietf.org
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <m2k4lxwtle.wl%randy@psg.com> <7A072CBD-C19D-42A0-8897-46DC09DD39A8@huawei.com> <m2lj6dueaw.wl%randy@psg.com> <C4C48CC9-EAFB-4D53-9BC7-BC24E13534EF@huawei.com>
In-reply-to: <C4C48CC9-EAFB-4D53-9BC7-BC24E13534EF@huawei.com>
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Oct 2010 16:34:32 -0000

  Perhaps a better analogy would have been that "That's like saying 
Disneyland, Stanford University, McDonalds and Greenpeace are all part 
of the Earth."

The orgs you named all share some interest in "inter-networking" and 
defining standards and procedures for it, but that does not mean they 
all share the same vision, agenda or reality about The Internet.

These discussions go on wherever they make sense to go on, until they 
naturally run their course, or in many cases long after.  It's only 
thanks to people who straddle more than one of those world-views (e.g. 
IETF and *NOG) that cooperation and coordination sometimes results.   It 
doesn't just happen, it relies on contributors to spend the time and 
energy necessary.

This was definitely off topic, but I think we need to maintain a sense 
of humor.


Meanwhile, back at the agenda, I support dedicating a block of time of 
v6ops in Beijing to the deployment/transition/coexistence drafts, and 
discussing future disposition of this work in the v6ops working group 
(or elsewhere).

On 10/5/2010 12:13 PM, Tina TSOU wrote:
>
> B. R.
> Tina
> http://tinatsou.weebly.com
>
>
>
>
> On Oct 5, 2010, at 6:25 PM, Randy Bush wrote:
>
>>> *NOG, IETF, ITU, ETSI are all part of Internet.
>>
>> ROFL.  and pluto is part of earth.
> ROFL. Pluto is NOT part of earth.
> Our this discussion is irrelevant to the original question. The 
> original question is to make sure that the documents under "IPv4 to 
> IPv6 Deployment/Coexistence Discussion" in the agenda is reasonable to 
> work in WG v6ops, to answer the comments why they don't go to xNOG, or 
> even they go to xNOG, they still want to come to v6ops as well.
>>
>> randy
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

-- 
Ed Jankiewicz - SRI International
Fort Monmouth Branch Office - IPv6 Research
Supporting DISA Standards Engineering Branch
732-389-1003 or  ed.jankiewicz@sri.com


From randy@psg.com  Tue Oct  5 16:36:29 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 299FC3A6EA9 for <v6ops@core3.amsl.com>; Tue,  5 Oct 2010 16:36:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.579
X-Spam-Level: 
X-Spam-Status: No, score=-2.579 tagged_above=-999 required=5 tests=[AWL=0.020,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N2N0d8BEgCgr for <v6ops@core3.amsl.com>; Tue,  5 Oct 2010 16:36:19 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 23CC23A6EA6 for <v6ops@ietf.org>; Tue,  5 Oct 2010 16:36:19 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1P3H4J-000EMj-Hs; Tue, 05 Oct 2010 23:37:12 +0000
Date: Wed, 06 Oct 2010 08:37:07 +0900
Message-ID: <m2r5g4tdng.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Tina TSOU <tena@huawei.com>
In-Reply-To: <C4C48CC9-EAFB-4D53-9BC7-BC24E13534EF@huawei.com>
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <m2k4lxwtle.wl%randy@psg.com> <7A072CBD-C19D-42A0-8897-46DC09DD39A8@huawei.com> <m2lj6dueaw.wl%randy@psg.com> <C4C48CC9-EAFB-4D53-9BC7-BC24E13534EF@huawei.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Oct 2010 23:36:29 -0000

>>> *NOG, IETF, ITU, ETSI are all part of Internet.
>> ROFL.  and pluto is part of earth.
> ROFL. Pluto is NOT part of earth.

and etsi and the itu have never understood the internet

randy

From randy@psg.com  Tue Oct  5 16:37:12 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D1A8C3A6EA6 for <v6ops@core3.amsl.com>; Tue,  5 Oct 2010 16:37:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.58
X-Spam-Level: 
X-Spam-Status: No, score=-2.58 tagged_above=-999 required=5 tests=[AWL=0.019,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JdT3UXE7HqlK for <v6ops@core3.amsl.com>; Tue,  5 Oct 2010 16:37:08 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 81FFD3A6EB3 for <v6ops@ietf.org>; Tue,  5 Oct 2010 16:37:07 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1P3H56-000EN2-Ru; Tue, 05 Oct 2010 23:38:01 +0000
Date: Wed, 06 Oct 2010 08:37:57 +0900
Message-ID: <m2pqvotdm2.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <4CAB52CA.1020600@bogus.com>
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <m2k4lxwtle.wl%randy@psg.com> <7A072CBD-C19D-42A0-8897-46DC09DD39A8@huawei.com> <m2lj6dueaw.wl%randy@psg.com> <C4C48CC9-EAFB-4D53-9BC7-BC24E13534EF@huawei.com> <4CAB52CA.1020600@bogus.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Oct 2010 23:37:12 -0000

> You (tina) stated in the v6v4trans call that china has no such operator
> communities

funny.  i hang out with some

randy

From bmanning@karoshi.com  Tue Oct  5 20:44:04 2010
Return-Path: <bmanning@karoshi.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7265A3A70AC for <v6ops@core3.amsl.com>; Tue,  5 Oct 2010 20:44:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.505
X-Spam-Level: 
X-Spam-Status: No, score=-6.505 tagged_above=-999 required=5 tests=[AWL=0.094,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NGltgNT34fSM for <v6ops@core3.amsl.com>; Tue,  5 Oct 2010 20:44:03 -0700 (PDT)
Received: from vacation.karoshi.com (vacation.karoshi.com [198.32.6.68]) by core3.amsl.com (Postfix) with ESMTP id 857C33A6FAF for <v6ops@ietf.org>; Tue,  5 Oct 2010 20:44:03 -0700 (PDT)
Received: from karoshi.com (localhost.localdomain [127.0.0.1]) by vacation.karoshi.com (8.12.8/8.12.8) with ESMTP id o963ibPr011418; Wed, 6 Oct 2010 03:44:37 GMT
Received: (from bmanning@localhost) by karoshi.com (8.12.8/8.12.8/Submit) id o963ibW5011417; Wed, 6 Oct 2010 03:44:37 GMT
Date: Wed, 6 Oct 2010 03:44:36 +0000
From: bmanning@vacation.karoshi.com
To: Randy Bush <randy@psg.com>
Message-ID: <20101006034436.GA11382@vacation.karoshi.com.>
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <m2k4lxwtle.wl%randy@psg.com> <7A072CBD-C19D-42A0-8897-46DC09DD39A8@huawei.com> <m2lj6dueaw.wl%randy@psg.com> <C4C48CC9-EAFB-4D53-9BC7-BC24E13534EF@huawei.com> <m2r5g4tdng.wl%randy@psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <m2r5g4tdng.wl%randy@psg.com>
User-Agent: Mutt/1.4.1i
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 03:44:04 -0000

On Wed, Oct 06, 2010 at 08:37:07AM +0900, Randy Bush wrote:
> >>> *NOG, IETF, ITU, ETSI are all part of Internet.
> >> ROFL.  and pluto is part of earth.
> > ROFL. Pluto is NOT part of earth.
> 
> and etsi and the itu have never understood the internet
> 
> randy

	and yet...  they have internet presence. both of them.
	and this is a guess, but I suspect they have some TCP/IP
	code running on nodes in their internal networks. and
	yea verily, those nodes can talk to other nodes, on other
	networks, using the TCP/IP protocol suite.

	would you consider that to be "part of Internet"?

--bill
	

From tena@huawei.com  Wed Oct  6 01:02:24 2010
Return-Path: <tena@huawei.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 27D973A6F00 for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 01:02:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.997
X-Spam-Level: 
X-Spam-Status: No, score=-99.997 tagged_above=-999 required=5 tests=[AWL=-0.102, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yJCkxHCBYj31 for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 01:02:23 -0700 (PDT)
Received: from szxga05-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id E7EAA3A6ED5 for <v6ops@ietf.org>; Wed,  6 Oct 2010 01:02:22 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9U00BD6ZPBVK@szxga05-in.huawei.com> for v6ops@ietf.org; Wed, 06 Oct 2010 16:03:11 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9U0055AZP54F@szxga05-in.huawei.com> for v6ops@ietf.org; Wed, 06 Oct 2010 16:03:11 +0800 (CST)
Received: from [192.168.1.4] ([113.116.37.175]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L9U00FKDZP7XR@szxml02-in.huawei.com>; Wed, 06 Oct 2010 16:03:07 +0800 (CST)
Date: Wed, 06 Oct 2010 16:03:07 +0800
From: Tina TSOU <tena@huawei.com>
In-reply-to: <4CAB52CA.1020600@bogus.com>
To: Joel Jaeggli <joelja@bogus.com>
Message-id: <95D04808-6642-43CF-A6CD-6BEB60F80BB5@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <m2k4lxwtle.wl%randy@psg.com> <7A072CBD-C19D-42A0-8897-46DC09DD39A8@huawei.com> <m2lj6dueaw.wl%randy@psg.com> <C4C48CC9-EAFB-4D53-9BC7-BC24E13534EF@huawei.com> <4CAB52CA.1020600@bogus.com>
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 08:02:24 -0000

B. R.
Tina
http://tinatsou.weebly.com




On Oct 6, 2010, at 12:31 AM, Joel Jaeggli wrote:

> On 10/5/10 12:13 PM, Tina TSOU wrote:
>>
>> B. R.
>> Tina
>> http://tinatsou.weebly.com
>>
>>
>>
>>
>> On Oct 5, 2010, at 6:25 PM, Randy Bush wrote:
>>
>>>> *NOG, IETF, ITU, ETSI are all part of Internet.
>>>
>>> ROFL.  and pluto is part of earth.
>> ROFL. Pluto is NOT part of earth.
>> Our this discussion is irrelevant to the original question. The  
>> original
>> question is to make sure that the documents under "IPv4 to IPv6
>> Deployment/Coexistence Discussion" in the agenda is reasonable to  
>> work
>> in WG v6ops, to answer the comments why they don't go to xNOG, or  
>> even
>> they go to xNOG, they still want to come to v6ops as well.
>
> I'm at NANOG, yet I will be at IETF in bejing. If I'm a network  
> operator
> I don't go to ETSI.
>
> If you want  to provide advice to and recive the same from network
> operators you should be involved in places where network operators go.
> You (tina)
Not me. Can-can. People asked the question in the conference call. She  
said no. She was a bit far from the telephone terminal. I conveyed her  
answer to the telephone terminal. I said "she said no". I didn't know  
either. Hope you could distinguish the different voices from two  
Chinese women.
> stated in the v6v4trans call that china has no such operator
> communities, it does and we thought it relevant to encourage their
> participation in this activity such that bilateral exchange of
> information can occur.
>
> Myself and Ron Bonica are here at nanog for similar reasons (as is  
> yui lee)
I fully agree going to xNOG. It is important. What I want to make sure  
is that no matter we go to xNOG or not, working in v6ops is still of  
much value. That's it.
>
>>> randy
>>
>


From randy@psg.com  Wed Oct  6 01:19:13 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 491B13A6ED8 for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 01:19:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.281
X-Spam-Level: 
X-Spam-Status: No, score=-2.281 tagged_above=-999 required=5 tests=[AWL=-0.282, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QFTsJdcPFvBC for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 01:19:12 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 2B0EF3A70EF for <v6ops@ietf.org>; Wed,  6 Oct 2010 01:17:58 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1P3PDE-000G6z-5L; Wed, 06 Oct 2010 08:18:56 +0000
Date: Wed, 06 Oct 2010 17:18:55 +0900
Message-ID: <m2bp77raxc.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Tina TSOU <tena@huawei.com>
In-Reply-To: <95D04808-6642-43CF-A6CD-6BEB60F80BB5@huawei.com>
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <m2k4lxwtle.wl%randy@psg.com> <7A072CBD-C19D-42A0-8897-46DC09DD39A8@huawei.com> <m2lj6dueaw.wl%randy@psg.com> <C4C48CC9-EAFB-4D53-9BC7-BC24E13534EF@huawei.com> <4CAB52CA.1020600@bogus.com> <95D04808-6642-43CF-A6CD-6BEB60F80BB5@huawei.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 08:19:13 -0000

> I fully agree going to xNOG. It is important. What I want to make sure  
> is that no matter we go to xNOG or not, working in v6ops is still of  
> much value. That's it.

which is why the operators come to ietf

randy

From tena@huawei.com  Wed Oct  6 01:21:28 2010
Return-Path: <tena@huawei.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A2ADE3A6DE2 for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 01:21:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.999
X-Spam-Level: 
X-Spam-Status: No, score=-99.999 tagged_above=-999 required=5 tests=[AWL=-0.104, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GOVNVc76BsUE for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 01:21:27 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 3C68E3A68B0 for <v6ops@ietf.org>; Wed,  6 Oct 2010 01:21:27 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9V00A300L3NG@szxga02-in.huawei.com> for v6ops@ietf.org; Wed, 06 Oct 2010 16:22:16 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9V0089S0L3C5@szxga02-in.huawei.com> for v6ops@ietf.org; Wed, 06 Oct 2010 16:22:15 +0800 (CST)
Received: from [192.168.1.4] ([113.116.37.175]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L9V0072H0L36H@szxml01-in.huawei.com>; Wed, 06 Oct 2010 16:22:15 +0800 (CST)
Date: Wed, 06 Oct 2010 16:22:14 +0800
From: Tina TSOU <tena@huawei.com>
In-reply-to: <m2pqvotdm2.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
Message-id: <E4052273-C938-477B-90BD-62E1F8F01A28@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <m2k4lxwtle.wl%randy@psg.com> <7A072CBD-C19D-42A0-8897-46DC09DD39A8@huawei.com> <m2lj6dueaw.wl%randy@psg.com> <C4C48CC9-EAFB-4D53-9BC7-BC24E13534EF@huawei.com> <4CAB52CA.1020600@bogus.com> <m2pqvotdm2.wl%randy@psg.com>
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 08:21:28 -0000

B. R.
Tina
http://tinatsou.weebly.com




On Oct 6, 2010, at 7:37 AM, Randy Bush wrote:

>> You (tina) stated in the v6v4trans call that china has no such  
>> operator
>> communities
>
> funny.  i hang out with some
Not me. Can-can. People asked the question in the conference call. She  
said no. She was a bit far from the telephone terminal. I conveyed her  
answer to the telephone terminal. I said "she said no". I didn't know  
either. Hope Joel could distinguish the different voices from two  
Chinese women.
So what? Even there is *NOG in China, Chinese operators still want to  
go to v6ops as well. As Fred said v6ops is a point of interface  
between the operational community and the IETF community; the  
operators can touch base with us anywhere they like, of course, but  
here they can explicitly get IETF involvement in their issues. That's  
the point.
>
>
> randy


From randy@psg.com  Wed Oct  6 01:23:08 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C501B3A6E0A for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 01:23:07 -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.267, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wDQQu6FXd9iv for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 01:23:06 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 323A63A6ED6 for <v6ops@ietf.org>; Wed,  6 Oct 2010 01:23:06 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1P3PIC-000G7t-RL; Wed, 06 Oct 2010 08:24:04 +0000
Date: Wed, 06 Oct 2010 17:24:03 +0900
Message-ID: <m2aamrraos.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <C165683A-1C03-415A-806F-674620AB607B@cisco.com>
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <54BED382-7B8C-4C23-826C-054B31333970@cisco.com> <641BFD35-D097-4E22-8A71-F3E75EB7CD4A@huawei.com> <C165683A-1C03-415A-806F-674620AB607B@cisco.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 08:23:08 -0000

>> I agree with you. Let's keep the Problem Statement I-D and Framework
>> I-D in the v6ops Beijing agenda. They could also aimed for
>> informational RFCs.
> 
> That will be between the authors of those drafts and the chairs,
> operating within the working group process. You're out of order
> attempting to subvert and direct the working group process.

thank you!

randy

From tena@huawei.com  Wed Oct  6 01:35:52 2010
Return-Path: <tena@huawei.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 356A93A6B2A for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 01:35:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.997
X-Spam-Level: 
X-Spam-Status: No, score=-99.997 tagged_above=-999 required=5 tests=[AWL=-0.102, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LClPpUhaByHB for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 01:35:51 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id B172B3A6ECA for <v6ops@ietf.org>; Wed,  6 Oct 2010 01:35:50 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9V00G8N193X9@szxga02-in.huawei.com> for v6ops@ietf.org; Wed, 06 Oct 2010 16:36:39 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9V00LPQ193GK@szxga02-in.huawei.com> for v6ops@ietf.org; Wed, 06 Oct 2010 16:36:39 +0800 (CST)
Received: from [192.168.1.4] ([113.116.37.175]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L9V00FK9192XR@szxml02-in.huawei.com>; Wed, 06 Oct 2010 16:36:39 +0800 (CST)
Date: Wed, 06 Oct 2010 16:36:37 +0800
From: Tina TSOU <tena@huawei.com>
In-reply-to: <m2aamrraos.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
Message-id: <56DC0013-40B8-4D3A-99E0-B2837302DD70@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <54BED382-7B8C-4C23-826C-054B31333970@cisco.com> <641BFD35-D097-4E22-8A71-F3E75EB7CD4A@huawei.com> <C165683A-1C03-415A-806F-674620AB607B@cisco.com> <m2aamrraos.wl%randy@psg.com>
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 08:35:52 -0000

B. R.
Tina
http://tinatsou.weebly.com




On Oct 6, 2010, at 4:24 PM, Randy Bush wrote:

>>> I agree with you. Let's keep the Problem Statement I-D and Framework
>>> I-D in the v6ops Beijing agenda. They could also aimed for
>>> informational RFCs.
>>
>> That will be between the authors of those drafts and the chairs,
>> operating within the working group process. You're out of order
>> attempting to subvert and direct the working group process.
>
> thank you!
Yes, agreed. Just my personal view. I have fundamental right to  
express my personal opinion. I should rephrase what I meant due to  
English is not my mother language. My concern was that the problem  
statement creates a set of goals, which logically would be translated  
into WG milestones. Then there is a moral obligation to achieve the  
milestones. Since
an Informational document has no authority in itself. If v6ops decides  
to work on the Problem Statement document, as long as it does not  
block the way of the use cases and transition guides, I am more than  
happy to clap.
>
> randy


From randy@psg.com  Wed Oct  6 01:42:10 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9353B3A6EE3 for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 01:42:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[AWL=0.047,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C3bP5I8lH-ty for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 01:42:09 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 768263A6ECA for <v6ops@ietf.org>; Wed,  6 Oct 2010 01:42:09 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1P3Pae-000GB3-4d; Wed, 06 Oct 2010 08:43:08 +0000
Date: Wed, 06 Oct 2010 17:43:07 +0900
Message-ID: <m28w2br9t0.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Tina TSOU <tena@huawei.com>
In-Reply-To: <56DC0013-40B8-4D3A-99E0-B2837302DD70@huawei.com>
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <54BED382-7B8C-4C23-826C-054B31333970@cisco.com> <641BFD35-D097-4E22-8A71-F3E75EB7CD4A@huawei.com> <C165683A-1C03-415A-806F-674620AB607B@cisco.com> <m2aamrraos.wl%randy@psg.com> <56DC0013-40B8-4D3A-99E0-B2837302DD70@huawei.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 08:42:10 -0000

> I have fundamental right to express my personal opinion.

we all do.  and one of mine is that we need to be careful that our
contribution is not exponentially proportional to layer numbers greater
than seven.

randy

From tena@huawei.com  Wed Oct  6 01:46:20 2010
Return-Path: <tena@huawei.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E39C43A6ED6 for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 01:46:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.136
X-Spam-Level: 
X-Spam-Status: No, score=-100.136 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id itQEKaIyD3Z8 for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 01:46:19 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 3A7B13A6E47 for <v6ops@ietf.org>; Wed,  6 Oct 2010 01:46:19 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9V00G811QJX9@szxga02-in.huawei.com> for v6ops@ietf.org; Wed, 06 Oct 2010 16:47:08 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9V00LQW1QJGK@szxga02-in.huawei.com> for v6ops@ietf.org; Wed, 06 Oct 2010 16:47:07 +0800 (CST)
Received: from [192.168.1.4] ([113.116.37.175]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L9V004RY1QJGM@szxml01-in.huawei.com>; Wed, 06 Oct 2010 16:47:07 +0800 (CST)
Date: Wed, 06 Oct 2010 16:47:06 +0800
From: Tina TSOU <tena@huawei.com>
In-reply-to: <20101006034436.GA11382@vacation.karoshi.com>
To: bmanning@vacation.karoshi.com
Message-id: <AE817E21-CC29-4B59-B9B2-D33BA817FFF0@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: multipart/alternative; boundary="Boundary_(ID_0MmU7m38tS3F/o67gcx8XQ)"
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <m2k4lxwtle.wl%randy@psg.com> <7A072CBD-C19D-42A0-8897-46DC09DD39A8@huawei.com> <m2lj6dueaw.wl%randy@psg.com> <C4C48CC9-EAFB-4D53-9BC7-BC24E13534EF@huawei.com> <m2r5g4tdng.wl%randy@psg.com> <20101006034436.GA11382@vacation.karoshi.com>
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 08:46:21 -0000

--Boundary_(ID_0MmU7m38tS3F/o67gcx8XQ)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT


B. R.
Tina
http://tinatsou.weebly.com




On Oct 6, 2010, at 11:44 AM, bmanning@vacation.karoshi.com wrote:

> On Wed, Oct 06, 2010 at 08:37:07AM +0900, Randy Bush wrote:
>>>>> *NOG, IETF, ITU, ETSI are all part of Internet.
>>>> ROFL.  and pluto is part of earth.
>>> ROFL. Pluto is NOT part of earth.
>>
>> and etsi and the itu have never understood the internet
>>
>> randy
>
> 	and yet...  they have internet presence. both of them.
> 	and this is a guess, but I suspect they have some TCP/IP
> 	code running on nodes in their internal networks. and
> 	yea verily, those nodes can talk to other nodes, on other
> 	networks, using the TCP/IP protocol suite.
>
> 	would you consider that to be "part of Internet"?
http://en.wikipedia.org/wiki/Internet
The Internet is a global system of interconnected computer networks  
that use the standard Internet Protocol Suite (TCP/IP) to serve  
billions of users worldwide. It is a network of networks that consists  
of millions of private, public, academic, business, and government  
networks, of local to global scope, that are linked by a broad array  
of electronic and optical networking technologies.
>
> --bill
> 	


--Boundary_(ID_0MmU7m38tS3F/o67gcx8XQ)
Content-type: text/html; charset=US-ASCII
Content-transfer-encoding: 7BIT

<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div apple-content-edited="true"> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); 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: 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="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; lette
 r-spacin
ormal; orphans: 2; 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="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><span class="Apple-style-span" style="font-size: 12px; "><div>B. R.</div><div>Tina</div><div><a href="http://tinatsou.weebly.com">http://tinatsou.weebly.com</a></div><div></div></span></div><div><br></div></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"> </div><br><div><div>On Oct 6, 2010, at 11:44 AM, <a href="mailto:bmanning@vacation.karoshi.com">bmanning@vacation.karoshi.com</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On Wed, Oct 06, 2010 at 08:37:07AM +0900, Randy Bush wrote:<br><blockq
 uote typ
="cite"><blockquote type="cite"><blockquote type="cite">*NOG, IETF, ITU, ETSI are all part of Internet.<br></blockquote></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">ROFL. &nbsp;and pluto is part of earth.<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">ROFL. Pluto is NOT part of earth.<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">and etsi and the itu have never understood the internet<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">randy<br></blockquote><br><span class="Apple-tab-span" style="white-space:pre">	</span>and yet... &nbsp;they have internet presence. both of them.<br><span class="Apple-tab-span" style="white-space:pre">	</span>and this is a guess, but I suspect they have some TCP/IP<br><span class="Apple-tab-span" style="white-space:pre">	</span>code running on nodes in their i
 nternal 
ass="Apple-tab-span" style="white-space:pre">	</span>yea verily, those nodes can talk to other nodes, on other<br><span class="Apple-tab-span" style="white-space:pre">	</span>networks, using the TCP/IP protocol suite.<br><br><span class="Apple-tab-span" style="white-space:pre">	</span>would you consider that to be "part of Internet"?<br></div></blockquote><span class="Apple-style-span" style="font-family: sans-serif; font-size: 13px; line-height: 19px; "><div><a href="http://en.wikipedia.org/wiki/Internet">http://en.wikipedia.org/wiki/Internet</a></div>The&nbsp;<b>Internet</b>&nbsp;is a global system of interconnected&nbsp;<a href="http://en.wikipedia.org/wiki/Computer_network" title="Computer network" style="text-decoration: none; color: rgb(6, 69, 173); background-image: none; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: initial; background-position: initial initial; background-repeat: initial initial; ">computer ne
 tworks</
dard&nbsp;<a href="http://en.wikipedia.org/wiki/Internet_Protocol_Suite" title="Internet Protocol Suite" style="text-decoration: none; color: rgb(6, 69, 173); background-image: none; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: initial; background-position: initial initial; background-repeat: initial initial; ">Internet Protocol Suite</a>&nbsp;(TCP/IP) to serve billions of users worldwide. It is a&nbsp;<i>network of networks</i>&nbsp;that consists of millions of private, public, academic, business, and government networks, of local to global scope, that are linked by a broad array of electronic and optical networking technologies.</span><br><blockquote type="cite"><div><br>--bill<br><span class="Apple-tab-span" style="white-space:pre">	</span><br></div></blockquote></div><br></body></html>

--Boundary_(ID_0MmU7m38tS3F/o67gcx8XQ)--

From tena@huawei.com  Wed Oct  6 01:54:21 2010
Return-Path: <tena@huawei.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AFF383A6EEF for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 01:54:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.995
X-Spam-Level: 
X-Spam-Status: No, score=-99.995 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a-uagn8d1aae for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 01:54:20 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 1F58E3A6EEA for <v6ops@ietf.org>; Wed,  6 Oct 2010 01:54:20 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9V00G9G23XEX@szxga01-in.huawei.com> for v6ops@ietf.org; Wed, 06 Oct 2010 16:55:09 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9V002VK23XBV@szxga01-in.huawei.com> for v6ops@ietf.org; Wed, 06 Oct 2010 16:55:09 +0800 (CST)
Received: from [192.168.5.101] ([113.116.37.175]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L9V005SX23VD5@szxml02-in.huawei.com>; Wed, 06 Oct 2010 16:55:09 +0800 (CST)
Date: Wed, 06 Oct 2010 16:55:05 +0800
From: Tina TSOU <tena@huawei.com>
In-reply-to: <94D16C01-3A30-4354-AD69-597AA5A7D103@cisco.com>
To: Fred Baker <fred@cisco.com>
Message-id: <4B91982C-C2DF-456D-ABF4-EE15C0617A65@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <54BED382-7B8C-4C23-826C-054B31333970@cisco.com> <641BFD35-D097-4E22-8A71-F3E75EB7CD4A@huawei.com> <94D16C01-3A30-4354-AD69-597AA5A7D103@cisco.com>
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 08:54:21 -0000

B. R.
Tina
http://tinatsou.weebly.com




On Oct 5, 2010, at 6:14 PM, Fred Baker wrote:

>
> On Oct 5, 2010, at 1:52 AM, Tina TSOU wrote:
>
>> 0)
>> "IPv4 to IPv6 Deployment/Coexistence Discussion"
>> Would it be more precise to say "IPv4 to IPv6 Transition Discussion"?
>
> That is a semantic question. Let me give you my view.
>
> In the long term, there is a transition going on. The word  
> "transition" signifies the entire change that will happen to  
> something; for example, if I am driving and change lanes, the  
> "transition" from one lane to another involves changing the  
> direction of the car relative to the road, a period of time during  
> which the car is to come extent in one lane and to some extent in  
> another, and finally a period of time in which the car is only in  
> the new lane (and presumably adjusts course to stay in it).  
> Similarly, the transition of the Internet from IPv4 to IPv6 involves  
> either deploying a new IPv6-only network (sudden change) or the  
> process of (a) turning IPv6 on in one's existing IPv4 network  
> (deployment), (b) existing with both on for a period of time  
> (coexistence), and turning IPv4 off (transition).
>
> For those who, like CERNET2, T-mobile, and Sprint, simply turn up a  
> new network or its equivalent running only IPv6, more power to them.  
> They will deal with issues of translation, and those issues will  
> have a home in v6ops.
>
> For most networks, it will be first the deployment process, which  
> draft-lee-v4v6tran-problem addresses in detail. How should prefixes  
> be allocated? If equipment cannot be readily upgraded but deployment  
> is urgent, what temporary measures can help in deploying IPv6 as a  
> service while those upgrades happen under the hood? What security  
> issues have to be addressed?
>
> With IPv6 turned on in the network, there are the questions Cancan  
> has discussed in some detail - the fact that the ISP has turned on  
> IPv6 doesn't mean that every user has upgraded their CPE or turned  
> IPv6 on in their network. Since they are using IPv4 in an IPv4+IPv6  
> network, those are coexistence issues.
>
> There will be issues such as Seiichi has alluded to, with operating  
> systems choosing their peer addresses to connect to without regard  
> to end to end connectivity issues (apple) or taking several seconds  
> per attempt ratcheting through the choices. These will be  
> operational issues in the network (can we get the neighboring  
> network to not be a walled garden when our roaming customers are  
> accessing our network's resources?), and they have a home here.
>
> And eventually it will come time to turn IPv4 off. At that point, if  
> nothing else, there will be some applications that are simply legacy  
> applications. Dealing with those will be transition issues.
>
> Yes, we will deal with transition issues. Eventually. Right now, I  
> think there are more networks figuring out how to turn IPv6 on and  
> how to get it to run they way they would like than there are  
> networks turning IPv4 off.
>
> So, yes, I don't know the timeframe, but we will be dealing with  
> transition issues. Right now, what I'm hearing from the v4v6tran  
> folks is discussion of deployment and coexistence issues.
 From an definition perspective (English - Oxford) Transition means  
"the process or a period of changing from one state or condition to  
another [Noun]".

From tena@huawei.com  Wed Oct  6 01:59:09 2010
Return-Path: <tena@huawei.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 215E13A6EEA for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 01:59:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.293
X-Spam-Level: 
X-Spam-Status: No, score=-100.293 tagged_above=-999 required=5 tests=[AWL=0.202, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nIpkoW0xCFqf for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 01:59:08 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id ECB303A6BF0 for <v6ops@ietf.org>; Wed,  6 Oct 2010 01:59:07 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9V001E72BXB0@szxga03-in.huawei.com> for v6ops@ietf.org; Wed, 06 Oct 2010 16:59:57 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9V00JFK2BWOC@szxga03-in.huawei.com> for v6ops@ietf.org; Wed, 06 Oct 2010 16:59:57 +0800 (CST)
Received: from [192.168.5.101] ([113.116.37.175]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L9V00FD42BKXR@szxml02-in.huawei.com>; Wed, 06 Oct 2010 16:59:56 +0800 (CST)
Date: Wed, 06 Oct 2010 16:59:43 +0800
From: Tina TSOU <tena@huawei.com>
In-reply-to: <m28w2br9t0.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
Message-id: <9E025610-B99C-40B3-810F-BFDCD5CAE136@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <54BED382-7B8C-4C23-826C-054B31333970@cisco.com> <641BFD35-D097-4E22-8A71-F3E75EB7CD4A@huawei.com> <C165683A-1C03-415A-806F-674620AB607B@cisco.com> <m2aamrraos.wl%randy@psg.com> <56DC0013-40B8-4D3A-99E0-B2837302DD70@huawei.com> <m28w2br9t0.wl%randy@psg.com>
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 08:59:09 -0000

B. R.
Tina
http://tinatsou.weebly.com




On Oct 6, 2010, at 4:43 PM, Randy Bush wrote:

>> I have fundamental right to express my personal opinion.
>
> we all do.  and one of mine is that we need to be careful that our
> contribution is not exponentially proportional to layer numbers  
> greater
> than seven.
What does it mean, Randy?
>
> randy


From remi.despres@free.fr  Wed Oct  6 03:38:31 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D518B3A7021 for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 03:38:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.403
X-Spam-Level: 
X-Spam-Status: No, score=-0.403 tagged_above=-999 required=5 tests=[AWL=-0.543, BAYES_05=-1.11, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BIIgjpXYGFMK for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 03:38:30 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.20]) by core3.amsl.com (Postfix) with ESMTP id E0A313A6F1E for <v6ops@ietf.org>; Wed,  6 Oct 2010 03:38:26 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2308.sfr.fr (SMTP Server) with ESMTP id 1ECFA700008A; Wed,  6 Oct 2010 12:39:26 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2308.sfr.fr (SMTP Server) with ESMTP id D21F17000094; Wed,  6 Oct 2010 12:39:24 +0200 (CEST)
X-SFR-UUID: 20101006103924860.D21F17000094@msfrf2308.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <94D16C01-3A30-4354-AD69-597AA5A7D103@cisco.com>
Date: Wed, 6 Oct 2010 12:39:22 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <811127C7-36B8-4722-8124-FC896B15C1B6@free.fr>
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <54BED382-7B8C-4C23-826C-054B31333970@cisco.com> <641BFD35-D097-4E22-8A71-F3E75EB7CD4A@huawei.com> <94D16C01-3A30-4354-AD69-597AA5A7D103@cisco.com>
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>, v6ops-ads@tools.ietf.org
Subject: Re: [v6ops] IPv6-only routing networks and IPv4 tunneling
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 10:38:32 -0000

Le 5 oct. 2010 =E0 12:14, Fred Baker a =E9crit :
> ...
>=20
> For those who, like CERNET2, T-mobile, and Sprint, simply turn up a =
new network or its equivalent running only IPv6, more power to them. =
They will deal with issues of translation, and those issues will have a =
home in v6ops.

To be complete, they will deal with issues of translation *and/or =
tunneling*.
(With 4rd, there are scenarios where routing is IPv6-only and where IPv4 =
connectivity is offered to customers without translation.)

RD



From fred@cisco.com  Wed Oct  6 05:21:23 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A12323A6EBE for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 05:21:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.396
X-Spam-Level: 
X-Spam-Status: No, score=-107.396 tagged_above=-999 required=5 tests=[AWL=-2.937, BAYES_50=0.001, HTML_IFRAME_SRC=0.043, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, J_CHICKENPOX_21=0.6, J_CHICKENPOX_44=0.6, MIME_8BIT_HEADER=0.3, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jEUyxmMsztVq for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 05:21:21 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id D55A23A6E66 for <v6ops@ietf.org>; Wed,  6 Oct 2010 05:21:20 -0700 (PDT)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.57,290,1283731200";  d="scan'208,217";a="265323756"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-5.cisco.com with ESMTP; 06 Oct 2010 12:22:20 +0000
Received: from Freds-Computer.local (sjc-vpn5-371.cisco.com [10.21.89.115]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o96CM5BQ007648; Wed, 6 Oct 2010 12:22:08 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Wed, 06 Oct 2010 08:22:14 -0400
X-PGP-Universal: processed; by Freds-Computer.local on Wed, 06 Oct 2010 08:22:14 -0400
From: Fred Baker <fred@cisco.com>
Date: Wed, 6 Oct 2010 08:21:56 -0400
Message-Id: <D40F684E-2A7B-42E6-ADC4-F4AFDE879FE3@cisco.com>
To: IPv6 Operations <v6ops@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Content-Type: multipart/alternative; boundary=Apple-Mail-2-970354582
Cc: Dave Thaler <dthaler@microsoft.com>
Subject: [v6ops] =?windows-1252?q?=93ipv6_on_windows_7=94_-_Google_Search?=
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 12:21:23 -0000

--Apple-Mail-2-970354582
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

It would be interesting to understand what the issue is here. I suspect =
it has nothing to do with the actual Windows (or Apple, Linux, etc) =
implementation, but is more related to issues as discussed in =
http://tools.ietf.org/html/draft-wing-http-new-tech. Would it make sense =
for v6ops to make a recommendation to address the concerns?



Screen reader users, click here to turn off Google Instant.
Google

=E2=80=9Cipv6 on windows 7=E2=80=9D	=C3=97

Instant is on =E2=96=BC

Web Images Videos Maps News Shopping Gmail more =E2=96=BC
FredBakerSBA@gmail.com | Web History | Settings =E2=96=BC | Sign out
Advanced search
About 2,600 results (0.19 seconds)=20
Search Results
Troubleshooting IPv6 on Windows 7 (and Why It's Worth the Bother ...
This post was mentioned on Twitter by howtoprojects: Troubleshooting =
IPv6 on Windows 7 (and Why It?s Worth the Bother) #howto =
http://bit.ly/9zJ192=E2=80=A6 ...
=
itexpertvoice.com/.../troubleshooting-ipv6-on-windows-7-and-why-its-worth =
-the-bother/ - Cached - Similar
=E2=96=BA
Windows 7 and IPv6: Useful at Last? =C2=AB IT Expert Voice
Dec 21, 2009... Troubleshooting IPv6 on Windows 7 (and Why It's Worth =
the Bother) =C2=B7 IPv6, Google, and Your Business =C2=B7 IPv6 and IPv4 =
Co-existence ...
itexpertvoice.com/home/windows-7-and-ipv6-useful-at-last/ - Cached - =
Similar
How to disable IPv6 on Windows 7 & Vista PC
Feb 9, 2010 ... Procedure to disable IPv6 feature on Windows 7 and Vista =
operating system. Use LAN connection properties option or change =
registry value to ...
www.tothepc.com/.../disable-ipv6-on-windows-7-vista-pc/ - Cached - =
Similar
serghei's blog=C2=BB Blog Archive =C2=BB IPv6 on Windows 7 is =
embarassing!
IPv6 on Windows 7 is embarassing! April 25th, 2010 at 21:51. Recently I =
moved to Windows 7 and let Windows XP behind. Yeah=E2=80=A6 I know. =
Using Windows on your ...
blog.serghei.net/it/software/ipv6-on-windows-7-is-embarassing.html - =
Cached
Set Preference for IPv4 over IPv6 on Windows 7 | Tuts4Tech
Apr 5, 2010 ... On Windows 7 by default if you have a IPv6 enabled it =
will prefer it over IPv4. In a sutiation where your IPv6 connection is =
not native this ...
tuts4tech.net/.../set-preference-for-ipv4-over-ipv6-on-windows-7/ - =
Cached
Tip: Disable IPv6 on Windows 7
Here's how to disable IPv6 on Windows 7 1. Click on the Start orb and =
select Control Panel. 2. Click the Network and Internet link. ...
www.tipstrs.com/tip/17071/Disable-IPv6-on-Windows-7 - Cached
IPV6 netsh EUI-64 store=3Dpersistent
2 posts - 1 author - Last post: Aug 26, 2009
When using IPv6 on Windows 7. If we do the following to get the IPv6 =
EUI-64 address: netsh interface ipv6 set global randomizeidentifiers=3D =
...
social.answers.microsoft.com/.../815f52c0-717a-457e-b1e7-d8ec54c7c909 - =
Cached - Similar
How do I disable IPv6 in WIndows 7 (Home Premium x64) | 1 of 1
Mar 24, 2010... How do I disable IPv6 in WIndows 7 (Home Premium x64): I =
know about http:// =
www.tothepc.com/archives/disable-ipv6-on-windows-7-vista-pc/ ...
techrepublic.com.com/5208-7343-0.html?forumID=3D101... - Cached
Thread IPv6 on Windows 7 running in Hyper-V | Microsoft TechNet ...
I have a VM running on Windows 7. My problem is with the IPv6 network, =
the VM was able to successfully lease an IP from the DHCPv6 server but =
whenever I try ...
boardreader.com/.../IPv6_on_Windows_7_running_in_Hyper_V_lxvb__ =
dd546ade-ec27-495c-bc60-4a9ff10eb15d.html - Cached
Ipv6 doesn't work after waking up from sleep mode - Windows 7 Forums
Mar 2, 2010 ... Hi All, I had a problem about ipv6 on windows 7 for a =
long time. I have a ipv6 & ipv4 dual stack network. Every time I wake up =
my computer, ...
www.sevenforums.com/.../68063-ipv6-doesnt-work-after-waking-up-sleep- =
mode.html - Cached
Everything
Images
Videos
More
Search Options
All results
Page previews
More search tools
1=09
2
3
4
5
6
7
8
9
10
Next
Search Help Give us feedback
Google HomeAdvertising ProgramsBusiness SolutionsPrivacyAbout Google


--Apple-Mail-2-970354582
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><base =
href=3D"http://www.google.com/search?client=3Dsafari&amp;rls=3Den&amp;q=3D=
%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;ie=3DUTF-8&amp;oe=3DUTF-8"><title>=
=E2=80=9Cipv6 on windows 7=E2=80=9D - Google =
Search</title><script>window.google=3D{kEI:"yGisTIDWHoO4sAOD9sj4Aw",kEXPI:=
"17259,18168,26614,26714",kCSI:{e:"17259,18168,26614,26714",ei:"yGisTIDWHo=
O4sAOD9sj4Aw",expi:"17259,18168,26614,26714"},ml:function(){},pageState:"#=
",kHL:"en",time:function(){return(new =
Date).getTime()},log:function(b,d,c){var a=3Dnew =
Image,e=3Dgoogle,g=3De.lc,f=3De.li;a.onerror=3D(a.onload=3D(a.onabort=3Dfu=
nction(){delete =
g[f]}));g[f]=3Da;c=3Dc||"/gen_204?atyp=3Di&ct=3D"+b+"&cad=3D"+d+"&zx=3D"+g=
oogle.time();a.src=3Dc;e.li=3Df+1},lc:[],li:0,j:{en:1,l:function(){google.=
fl=3Dtrue},e:function(){google.fl=3Dtrue},b:location.hash&&location.hash!=3D=
"#",bv:5,pl:[],mc:0,sc:0.5},Toolbelt:{}};(function(){for(var =
d=3D0,c;c=3D["ad","bc","p","pa","zd","ac","pc","pah","ph","sa","spf","xx",=
"zc","zz"][d++];)(function(a){google.j[a]=3Dfunction(){google.j.pl.push([a=
,arguments])}})(c)})();
window.google.sn=3D"web";window.google.timers=3D{load:{t:{start:(new =
Date).getTime()}}};try{}catch(u){}window.google.jsrt_kill=3D1;
</script><style id=3D"gstyle">body{color:#000;margin:3px =
0;overflow-y:scroll}body,#leftnav,#tbd,#atd,#tsf,#hidden_modes,#hmp{backgr=
ound:#fff}#gog{background:#fff}#gbar,#guser{font-size:13px;padding-top:1px=
 !important}#gbar{float:left;height:22px}#guser{padding-bottom:7px =
!important;text-align:right}.gbh,.gbd{border-top:1px solid =
#c9d7f1;font-size:1px}.gbh{height:0;position:absolute;top:24px;width:100%}=
#gbs,.gbm{background:#fff;left:0;position:absolute;text-align:left;visibil=
ity:hidden;z-index:1000}.gbm{border:1px solid;border-color:#c9d7f1 #36c =
#36c =
#a2bae7;z-index:1001}.gb1{margin-right:.5em}.gb1,.gb3{zoom:1}.gb2{display:=
block;padding:.2em =
.5em}.gb2,.gb3{text-decoration:none;border-bottom:none}a.gb1,a.gb2,a.gb3,a=
.gb4{color:#00c !important}a.gb2:hover{background:#36c;color:#fff =
!important}a.gb1,a.gb2,a.gb3,.link{color:#11c!important}.ts{border-collaps=
e:collapse}.ts td{padding:0}.ti,.bl,#res =
h3{display:inline}.ti{display:inline-table}#tads a.mblink,#tads a.mblink =
b,#rhs a.mblink,#rhs a.mblink b{color:#1111CC!important}a:link,.w,#prs =
a:visited,#prs =
a:active,.q:active,.q:visited{color:#11c}.mblink:visited,a:visited{color:#=
551a8b}.vst:link{color:#551a8b}.cur,.b{font-weight:bold}.j{width:42em;font=
-size:82%}.s{max-width:42em}.sl{font-size:82%}#gb{text-align:right;padding=
:1px 0 =
7px;margin:0}.hd{position:absolute;width:1px;height:1px;top:-1000em;overfl=
ow:hidden}.gl,.f,.m,.c h2,#mbEnd h2,#tads =
h2,.descbox{color:#767676}.a,cite,cite a:link,cite =
a:visited,.cite,.cite:link,#mbEnd cite b,#tads cite =
b{color:#0e774a;font-style:normal}.ng{color:#c11}h1,ol,ul,li{margin:0;padd=
ing:0}li.g,body,html,.std,.c h2,#mbEnd =
h2,h1{font-size:small;font-family:arial,sans-serif}.c h2,#mbEnd =
h2,h1{font-weight:normal}.clr{clear:both;margin:0 8px}.blk =
a{color:#000}#nav a{display:block}#nav =
.i{color:#a90a08;font-weight:bold}.csb,.ss,#logo =
span,.play_icon,.mini_play_icon,.micon,.licon,.close_btn,#tbp,.lsb,.mbi{ba=
ckground:url(/images/nav_logo16.png) =
no-repeat;overflow:hidden}.csb,.ss{background-position:0 =
0;height:40px;display:block}.ss{background-position:0 =
-41px;position:absolute;left:0;top:0}.cps{height:18px;overflow:hidden;widt=
h:114px}.mbi{background-position:-159px =
-41px;display:inline-block;float:left;height:13px;margin-right:3px;margin-=
top:1px;width:13px}#nav =
td{padding:0;text-align:center}#logo{display:block;overflow:hidden;positio=
n:relative;width:178px;height:62px;margin:3px 0 0 2px}#logo =
img{border:none;position:absolute;left:-0px;top:-145px}.ws,.wsa,.wxs,.wpb{=
background:url(/images/nav_logo16.png) =
no-repeat;border:0;cursor:pointer;display:none;margin-right:3px;height:0px=
;vertical-align:bottom;width:0px}.ws,.wsa{display:inline;height:14px;margi=
n-left:5px;vertical-align:0;width:14px}.ws{background-position:-129px =
-70px}.wsa{background-position:-114px =
-70px}.wxs{background-position:;cursor:default;display:inline;height:px;ma=
rgin-left:8px;width:px}.wpb{background-position:-159px =
-41px;display:inline;height:13px;vertical-align:-2px;width:13px}.link{curs=
or:pointer}#logo =
span,.ch{cursor:pointer}h3,.med{font-size:medium;font-weight:normal;paddin=
g:0;margin:0}.e{margin:2px 0 .75em}.slk =
div{padding-left:12px;text-indent:-10px}.fc{margin-top:.5em;padding-left:1=
6px}#mbEnd =
cite{display:block;text-align:left}#rhs_block{margin-bottom:-20px}#bsf,.bl=
k{border-top:1px solid #6b90da;background:#f0f7f9}#bsf{border-bottom:1px =
solid #6b90da}#cnt{clear:both}#res{padding-right:1em;margin:0 =
16px}.c{background:#fbf0fa;margin:0 8px}.c li{padding:0 3px 0 =
8px;margin:0}#mbEnd li{margin:1em 0;padding:0}.xsm{font-size:x-small}ol =
li{list-style:none}#ncm ul li{list-style-type:disc}.sm =
li{margin:0}.gl,#foot a,.nobr{white-space:nowrap}#mbEnd =
.med{white-space:normal}.sl,.r{display:inline;font-weight:normal;margin:0}=
.r{font-size:medium}h4.r{font-size:small}.mr{margin-top:6px}h3.tbpr{margin=
-top:.4em;margin-bottom:1.2em}img.tbpr{border:0px;width:15px;height:15px;m=
argin-right:3px}.jsb{display:block}.nojsb{display:none}.nwd{font-size:10px=
;padding:16px;text-align:center}.rt1{background:transparent =
url(/images/bubble1.png) no-repeat}.rt2{background:transparent =
url(/images/bubble2.png) repeat 0 0 =
scroll}.sb{background:url(/images/scrollbar.png) repeat scroll 0 =
0;cursor:pointer;width:14px}.rtdm:hover{text-decoration:underline}#rtr =
.g{margin:1em 0}#ss-box{background:#fff;border:1px =
solid;border-color:#c9d7f1 #36c #36c =
#a2bae7;left:0;margin-top:.1em;position:absolute;visibility:hidden;z-index=
:101}#ss-box a{display:block;padding:.2em =
.31em;text-decoration:none}#ss-box =
a:hover{background:#558be3;color:#fff!important}a.ss-selected{color:#000!i=
mportant;font-weight:bold}a.ss-unselected{color:#4273db!important}.ss-sele=
cted .mark{display:inline}.ss-unselected =
.mark{visibility:hidden}#ss-barframe{background:#fff;left:0;position:absol=
ute;visibility:hidden;z-index:100}.ri_cb{left:0;margin:6px;position:absolu=
te;top:0;z-index:1}.ri_sp{display:-moz-inline-box;display:inline-block;tex=
t-align:center;vertical-align:top;margin-bottom:6px}.ri_sp =
img{vertical-align:bottom}.mbl{margin:1em 0 =
0}em{font-weight:bold;font-style:normal}li.w0 .ws,td.w0 =
.ws{opacity:0.5}li.w0:hover .ws,td.w0:hover =
.ws{opacity:1}ol,ul,li{border:0;margin:0;padding:0}li{line-height:1.2}li.g=
{margin-top:0;margin-bottom:14px}.ibk,#productbox =
.fmg{display:-moz-inline-box;display:inline-block;*display:inline;vertical=
-align:top;zoom:1}.tsw{width:595px}#cnt{min-width:817px;max-width:1181px;m=
argin:0 =
auto;padding-top:17px;}.gbh{top:24px}#gbar{margin-left:8px;height:20px}#gu=
ser{margin-right:8px;padding-bottom:5px!important}.mbi{margin-bottom:-1px}=
.uc{margin-left:186px}#center_col,#foot{margin-left:196px;margin-right:22%=
;padding:0 8px 0 =
8px}#subform_ctrl{font-size:11px;margin-left:213px;margin-right:22%;min-he=
ight:26px;padding-top:3px;padding-right:8px;}#center_col{border-left:1px =
solid #d3e1f9;clear:both}#brs =
p{margin:0;padding-top:5px}.brs_col{display:inline-block;float:left;font-s=
ize:small;white-space:nowrap;padding-right:16px;margin-top:-1px;padding-bo=
ttom:1px}#tads,#tadsb{margin-bottom:8px!important}#tads li,#tadsb =
li{padding:1px 0}#tads li.taf,#tadsb li.taf{padding:1px 0 0}#tads =
li.tam,#tadsb li.tam{padding:14px 0 0}#tads li.tal,#tadsb =
li.tal{padding:14px 0 1px}#res{border:0;margin:0;padding:4px 8px =
0}#ires{padding-top:1px}.mbl{margin-top:5px}.play_icon{background-position=
:;height:px;margin-left:64px;margin-top:44px;width:px}#leftnav =
li{display:block}.micon,.licon,.close_btn{border:0}#leftnav =
h2{font-size:small;color:#767676;font-weight:normal;margin:8px 0 =
0;padding-left:8px;width:170px}#tbbc =
dfn{padding:4px}.close_btn{background-position:-144px =
-55px;float:right;height:14px;width:14px}.videobox{padding-bottom:3px}#lef=
tnav a{text-decoration:none}#leftnav =
a:hover{text-decoration:underline}.mitem,#showmodes{font-size:15px;line-he=
ight:24px;margin-right:4px;padding-left:8px}.mitem{margin-bottom:2px}.mite=
m =
.q{display:block}.msel{height:22px;padding-bottom:2px;margin-bottom:0;font=
-weight:bold}.micon{float:left;height:19px;margin-top:2px;margin-right:5px=
;outline:none;padding-right:1px;width:19px}#showmodes =
.micon{background-position:-160px =
-103px;height:17px;margin-left:1px;margin-right:6px;width:17px}.licon{back=
ground-position:-159px =
-70px;float:left;height:14px;margin-right:3px;width:14px}.open =
#showmodes .micon{background-position:-160px -85px}.open =
.msm,.msl{display:none}.open .msl{display:inline}.open =
#hidden_modes,.open #hmp{display:block}#swr =
li{border:0;font-size:13px;line-height:1.2;margin:0 0 =
4px;margin-right:8px;}#tbd,#atd{display:block;margin-top:8px;margin-left:2=
5px;min-height:1px}.tbt{font-size:13px;line-height:1.2}.tbou,.tbos,.tbots,=
.tbotu{margin-right:8px;padding-left:16px;padding-bottom:3px;text-indent:-=
8px}.tbos,.tbots{font-weight:bold}#leftnav .tbots =
a{color:#000!important;cursor:default;text-decoration:none}.tbfo =
.tbt,.tbpd{margin-bottom:8px}#season_{margin-top:8px}#iszlt_sel.tbcontrol_=
vis{margin-left:0}.tbpc,.tbpo,.lcsc,.lcso{font-size:13px}.tbpc,.tbo =
.tbpo,.lco .lcsc{display:inline}.tbo .tbpc,.tbpo,.lco =
.lcso,.lcsc,#set_location_section{display:none}.lco =
#set_location_section{display:block}.tbo #tbp,.lco =
.licon{background-position:-144px -70px!important}#prc_opt =
label,#prc_ttl{display:block;font-weight:normal;margin-right:2px;white-spa=
ce:nowrap}#cdr_opt,#loc_opt,#prc_opt{padding-left:8px;text-indent:0}.tbou =
#cdr_frm,.tbou #cloc_frm =
{display:none}#cdr_frm,#cdr_min,#cdr_max{width:88%}#cdr_opt =
label{display:block;font-weight:normal;margin-right:2px;white-space:nowrap=
}.bksg =
{font-size:82%;line-height:130%;padding:2px;vertical-align:top;}.bkst =
div {background-color:#f9f9f9;border:1px solid #e0e0e0;color: =
#666;font-size:small;text-align:center;}.rhss{margin:0 0 =
32px;margin-left:8px}#mbEnd{margin:0 0 32px;margin-left:8px}#mbEnd =
h2{color:#767676}#mbEnd li{margin:12px 8px 0 =
0}a:link,.w,.q:active,.q:visited,.tbotu{color:#11c;cursor:pointer}a.fl:lin=
k,.fl a,.flt,a.flt,.gl a:link,a.mblink,.mblink b{color:#4272db}.osl =
a,.gl a,#tsf a,a.mblink,a.gl,a.fl,.slk a,.bc a,.flt,a.flt u,.oslk =
a{text-decoration:none}.osl a:hover,.gl a:hover,#tsf =
a:hover,a.mblink:hover,a.gl:hover,a.fl:hover,.slk a:hover,.bc =
a:hover,.flt:hover,a.flt:hover u,.oslk =
a:hover,.tbotu:hover{text-decoration:underline}#ss-box =
a:hover{text-decoration:none}#tads .mblink,#rhs =
.mblink{text-decoration:underline}.hpn,.osl{color:#767676}div#gbi,div#gbg{=
border-color:#a2bff0 #558be3 #558be3 #a2bff0}div#gbi a.gb2:hover,div#gbg =
a.gb2:hover,.mi:hover{background-color:#558be3}#guser =
a.gb2:hover,.mi:hover,.mi:hover =
*{color:#fff!important}#guser{color:#000}#imagebox_big =
img{padding:2px!important}#productbox table.ts{color:#767676}#productbox =
table.ts a{text-decoration:underline}#productbox =
.fmg{margin-top:7px;padding-right:8px;text-align:left}#foot =
.ftl{margin-right:12px}#foot =
a.slink{text-decoration:none;color:#4272db}#fll a,#bfl =
a{color:#4272db;margin:0 12px;text-decoration:none}#foot =
a:hover{text-decoration:underline}#foot =
a.slink:visited{color:#551a8b}#blurbbox_bottom{color:#767676}.nvs =
a{text-decoration:underline}.stp{margin:7px 0 17px}.ssp{margin:.33em 0 =
17px}#gsr a:active,a.fl:active,.fl a:active,.gl =
a:active{color:#c11}</style><style>#po-bar{margin-bottom:4px;padding-top:1=
px;white-space:nowrap;z-index:98}#po-bar a,#po-bar =
a:visited{color:#4273db}#po-bar =
.flt{cursor:pointer;padding-bottom:0;text-decoration:none}#po-status{float=
:left}#po-box{background:#fff;border:1px solid;border-color:#c9d7f1 #36c =
#36c =
#a2bae7;left:0;margin-top:.1em;position:absolute;z-index:101}#po-box =
a{display:block;padding:.2em .31em;text-decoration:none}#po-box =
a:hover{background:#558be3;color:#fff!important;text-decoration: =
none!important}#po-sc-lm =
a{display:inline;white-space:nowrap;padding:0}.po-lm{color:#aaa}a.po-selec=
ted{color:#000!important;font-weight:bold}a.po-unselected{color:#4273db!im=
portant}.po-selected .mark{display:inline}.po-unselected =
.mark{visibility:hidden}.gbd{border-top:1px solid =
#c9d7f1;font-size:1px}.gb2{padding:.2em =
.5em}body{overflow-y:scroll}#logo{color:#fff;display:block;height:62px;mar=
gin:3px 0 0 2px;overflow:hidden;position:relative;width:178px}#logo =
img{border:0;left:-0px;position:absolute;top:-145px}input{-moz-box-sizing:=
content-box}.lst-b,.lst{height:26px;padding:4px 0 0}.tia =
input{border-right:none;padding-right:0px}.lst-b{border-right:none}.lst{-m=
oz-box-sizing:content-box;background:#fff;color:#000;font:17px =
arial,sans-serif;float:left;padding-left:6px;padding-right:10px;vertical-a=
lign:top;width:100%}.lst-td{background:#fff;border-bottom:1px solid =
#999}.lst-td-xbtn{border-top:1px solid =
#ccc;padding-right:16px}.ds{border-right:1px solid =
#e7e7e7;position:relative;height:32px;z-index:100}.lsbb{background:#eee;bo=
rder:1px solid =
#999;border-top-color:#ccc;border-left-color:#ccc;height:30px}.lsb{font:15=
px =
arial,sans-serif;background-position:bottom;border:none;color:#000;cursor:=
pointer;height:30px;margin:0;vertical-align:top}.lsb:active{background:#cc=
c}.lst:focus{outline:none}.lsd{font-size:11px;position:absolute;top:3px;le=
ft:16px}.gl{white-space:nowrap}#searchform{position:absolute;top:250px;wid=
th:100%;z-index:100}.tsf-p,.ctr-p > =
center{padding-left:205px;padding-right:22%}#tsf,.ctr-p{margin:0 =
auto;max-width:1181px;min-width:817px}.fade #center_col,.fade #rhs,.fade =
#leftnav{filter:alpha(opacity=3D33.3);opacity:0.333}#misspell{background:t=
ransparent;color:#fff;position:absolute;z-index:2}.misspelled{background:u=
rl('/images/experiments/wavy-underline.png') 50% 100% =
repeat-x;color:#fff;display:inline-block;line-height:1.05em;padding:0 0 =
3px =
0}form{display:inline}input[name=3D"q"]{background:transparent;position:re=
lative;z-index:3}#grey{background:#fff;border-color:transparent;color:silv=
er;overflow:hidden;position:absolute;z-index:1}#xbtn{color:#a1b9ed;cursor:=
pointer;display:none;font:28px =
Arial,sans-serif;height:20px;line-height:28px;margin:4px -8px 4px =
0;padding:0;top:2px;width:14px;z-index:4}#xbtn:hover,.flt,.flt =
u,a.fl{color:#4272db;text-decoration:none}.flt:hover,.flt:hover =
u,a.fl:hover{text-decoration:underline}.lst{border-width:0 0 0 =
1px}#sfopt a:hover{text-decoration:none}#sfopt =
a.flt:hover{text-decoration:underline}#pocs{background:#fff1a8;color:#000;=
font-size:10pt;margin:0;padding:6px =
7px}#pocs.sft{background:#fff;color:#777}#pocs a{color:#11c}#pocs.sft =
a{color:#4373db}#pocs > =
div{margin:0;padding:0}#knavm{color:#4273db;display:inline;font:11px =
arial,sans-serif!important;left:-13px;position:absolute;top:2px}#pnprev =
#knavm{bottom:1px;top:auto}#pnnext =
#knavm{bottom:1px;left:40px;top:auto}a.noline{outline:0}#searchform =
.jsb{display:none}#searchform =
.nojsb{display:block}</style><noscript></noscript><script>var =
_gjwl=3Dlocation;function _gjuc(){var =
b=3D_gjwl.href.indexOf("#");if(b>=3D0){var =
a=3D_gjwl.href.substring(b+1);if(/(^|&)q=3D/.test(a)&&a.indexOf("#")=3D=3D=
-1&&!/(^|&)cad=3Dh($|&)/.test(a)){_gjwl.replace("/search?"+a.replace(/(^|&=
)fp=3D[^&]*/g,"")+"&cad=3Dh");return 1}}return 0}function =
_gjp(){!(window._gjwl.hash&&window._gjuc())&&setTimeout(_gjp,500)};
google.y=3D{};google.x=3Dfunction(e,g){google.y[e.id]=3D[e,g];return =
false};if(!window.google)window.google=3D{};window.google.crm=3D{};window.=
google.cri=3D0;window.clk=3Dfunction(e,f,g,k,l,b,m){return true};
window.gbar=3D{qs:function(){},tg:function(e){var o=3D{id:'gbar'};for(i =
in e)o[i]=3De[i];google.x(o,function(){gbar.tg(o)})}};</script><style =
type=3D"text/css">.gac_od{background:white;margin:0;z-index:100;border-top=
:0;border-left:0;border-right:1px solid #e7e7e7;border-bottom:1px solid =
#e7e7e7;margin-top:1px;padding:0!important;position:absolute}.gac_id{backg=
round:white;margin:0;z-index:100;border-top:1px solid =
#a2bff0;border-left:1px solid #a2bff0;border-right:1px solid =
#558be3;border-bottom:1px solid =
#558be3;display:block;position:relative}.gac_m{background:white;margin:0;z=
-index:100;border:0;cursor:default;display:block;font-size:17px;line-heigh=
t:117%;padding:0;position:relative}#gac_pp{color:#a1b9ed;text-decoration:n=
one;cursor:pointer;font:22px =
Arial,sans-serif;height:20px;line-height:22px;margin:0 2px 0 =
0;padding:4px 0 0 =
0;top:4px;width:8px}#gac_pp:hover{color:#4272db;text-decoration:none}#gac_=
fd{color:#4272db;text-decoration:none}#gac_fd:hover{color:#4272db;text-dec=
oration:underline}.gac_m =
td{line-height:22px}.gac_n{padding-top:1px;padding-bottom:1px}.gac_b =
td.gac_c{background:#d5e2ff}.gac_b{background:#d5e2ff}.gac_k{display:none}=
.gac_b td.gac_k{display:block}.gac_a =
td.gac_f{background:#fff8dd}.gac_p{padding:1px 4px 2px =
3px}.gac_u{padding:0 0 1px =
0;line-height:117%;text-align:left}.gac_t{width:100%;text-align:left;font-=
size:17px}.gac_za{position:absolute;bottom:0;right:0;text-align:right;font=
-size:12px;padding-right:5px}.gac_bt{width:570px;text-align:center;padding=
:8px 0 =
7px;position:relative}.gac_sb{font-size:15px;height:28px;margin:0.2em;-web=
kit-appearance:button}.gac_z{white-space:nowrap;color:#c00}.gac_s{height:3=
px;font-size:1px}.gac_c{white-space:nowrap;overflow:hidden;text-align:left=
;padding-left:7px;padding-right:3px}.gac_e{text-align:right;padding:0 =
3px 0 =
8px;white-space:nowrap}.gac_d{font-size:13px}.gac_h{color:green}.gac_j{dis=
play:block}.gac_l{line-height:18px}.gac_x{display:block;line-height:16px}.=
gac_i{color:#666}.gac_w =
img{width:40px;height:40px}.gac_w{width:1px}.gac_r{color:red}.gac_v{paddin=
g-bottom:5px}</style><style =
type=3D"text/css">#AdContainer,#RadAd_Skyscraper,#ad-frame,#bbccom_leaderb=
oard,#center_banner,#footer_adcode,#hbBHeaderSpon,#hiddenHeaderSpon,#navba=
r_adcode,#rightAds,#rightcolumn_adcode,#top-advertising,#topMPU,#tracker_a=
dvertorial,.ad-now,.dfpad,.prWrap,[id^=3D"ad_block"],[id^=3D"adbrite"],[id=
^=3D"dclkAds"],[id^=3D"ew"][id$=3D"_bannerDiv"],[id^=3D"konaLayer"],[src*=3D=
"sixsigmatraffic.com"],a.kLink =
span[id^=3D"preLoadWrap"].preLoadWrap,a[href^=3D"http://ad."][href*=3D".do=
ubleclick.net/"],a[href^=3D"http://adserver.adpredictive.com"],div#FFN_Ban=
ner_Holder,div#FFN_imBox_Container,div#adxLeaderboard,div#p360-format-box,=
div#rm_container,div#tooltipbox[class^=3D"itxt"],div.wnDVUtilityBlock,div[=
class^=3D"dms_ad_IDS"],div[id^=3D"adKontekst_"],div[id^=3D"google_ads_div"=
],div[id^=3D"kona_"][id$=3D"_wrapper"],div[id^=3D"sponsorads"],div[id^=3D"=
y5_direct"],embed[flashvars*=3D"AdID"],iframe.chitikaAdBlock,iframe[id^=3D=
"dapIfM"],iframe[id^=3D"etarget"][id$=3D"banner"],iframe[name^=3D"AdBrite"=
],iframe[name^=3D"google_ads_"],iframe[src*=3D"clicksor.com"],img[src*=3D"=
clicksor.com"],img[src^=3D"http://cdn.adnxs.com"],ispan#ab_pointer,object#=
flashad,object#ve_threesixty_swf[name=3D"ve_threesixty_swf"],DIV#rhsa,ifra=
me[src*=3D"feedads.g.doubleclick.net"],div#dir_ads_site,div#rhs =
div#rhs_block table#mbEnd,div#tads =
table[align=3D"center"][width=3D"100%"],table[cellpadding=3D"0"][width=3D"=
100%"][style] > * > * > * > =
div#tpa1,#A9AdsMiddleBoxTop,#A9AdsOutOfStockWidgetTop,#A9AdsServicesWidget=
Top,#AD_CONTROL_22,#ADsmallWrapper,#Ad1,#Ad160x600,#Ad2,#Ad300x250,#Ad3Lef=
t,#Ad3Right,#Ad3TextAd,#AdBanner_F1,#AdBar,#AdBar1,#AdContainerTop,#AdCont=
entModule_F,#AdDetails_GoogleLinksBottom,#AdDetails_InsureWith,#AdFrame4,#=
AdHeader,#AdMiddle,#AdMobileLink,#AdRectangle,#AdSenseDiv,#AdServer,#AdSho=
wcase_F1,#AdSky23,#AdSkyscraper,#AdSponsor_SF,#AdSubsectionShowcase_F1,#Ad=
TargetControl1_iframe,#AdText,#AdTop,#Ad_Block,#Ad_Center1,#Ad_Right1,#Ad_=
Top,#Adbanner,#Adrectangle,#Ads,#AdsContent,#AdsRight,#AdsWrap,#Ads_BA_CAD=
,#Ads_BA_CAD2,#Ads_BA_CAD_box,#Ads_BA_SKY,#AdvertMPU23b,#AdvertPanel,#Adve=
rtiseFrame,#Advertisement,#Advertisements,#Advertorial,#Advertorials,#Bann=
erAdvert,#BigBoxAd,#BodyAd,#ButtonAd,#CompanyDetailsNarrowGoogleAdsPresent=
ationControl,#CompanyDetailsWideGoogleAdsPresentationControl,#ContentAd,#C=
ontentAd1,#ContentAd2,#ContentAdPlaceHolder1,#ContentAdPlaceHolder2,#Conte=
ntAdXXL,#ContentPolepositionAds_Result,#DivAdEggHeadCafeTopBanner,#FooterA=
d,#FooterAdContainer,#GoogleAd1,#GoogleAd2,#GoogleAd3,#GoogleAdsPresentati=
onControl,#GoogleAdsense,#HEADERAD,#HOME_TOP_RIGHT_BOXAD,#HeaderAdsBlock,#=
HeaderAdsBlockFront,#HeaderBannerAdSpacer,#HeaderTextAd,#HeroAd,#HomeAd1,#=
HouseAd,#ID_Ad_Sky,#Journal_Ad_125,#Journal_Ad_300,#KH-contentAd,#LeftAd,#=
LeftAdF1,#LeftAdF2,#LftAd,#LoungeAdsDiv,#LowerContentAd,#MainSponsoredLink=
s,#Nightly_adContainer,#PREFOOTER_LEFT_BOXAD,#PREFOOTER_RIGHT_BOXAD,#PageL=
eaderAd,#RelevantAds,#RgtAd1,#RightAd,#RightSponsoredAd,#SectionAd300-250,=
#SectionSponsorAd,#SidebarAdContainer,#SkyAd,#SpecialAds,#SponsoredAd,#Spo=
nsoredLinks,#TOP_ADROW,#TOP_RIGHT_BOXAD,#Tadspacehead,#TopAd,#TopAdContain=
er,#TopAdDiv,#TopAdPos,#VM-MPU-adspace,#VM-footer-adspace,#VM-header-adspa=
ce,#VM-header-adwrap,#XEadLeaderboard,#XEadSkyscraper,#_ads,#about_adsbott=
om,#ad-120x600-sidebar,#ad-120x60Div,#ad-160x600,#ad-160x600-sidebar,#ad-2=
50x300,#ad-300,#ad-300x250,#ad-300x250-sidebar,#ad-300x250Div,#ad-728,#ad-=
728x90-leaderboard-top,#ad-article,#ad-banner,#ad-bottom,#ad-bottom-wrappe=
r,#ad-boxes,#ad-bs,#ad-buttons,#ad-colB-1,#ad-column,#ad-container,#ad-con=
tent,#ad-contentad,#ad-footer,#ad-footprint-160x600,#ad-front-footer,#ad-f=
ront-sponsoredlinks,#ad-halfpage,#ad-header,#ad-inner,#ad-label,#ad-leader=
board,#ad-leaderboard-bottom,#ad-leaderboard-container,#ad-leaderboard-spo=
t,#ad-leaderboard-top,#ad-left,#ad-list-row,#ad-lrec,#ad-medium-rectangle,=
#ad-middlethree,#ad-middletwo,#ad-module,#ad-mpu,#ad-mpu1-spot,#ad-mpu2,#a=
d-mpu2-spot,#ad-north,#ad-one,#ad-placard,#ad-placeholder,#ad-rectangle,#a=
d-right,#ad-righttop,#ad-row,#ad-side-text,#ad-sky,#ad-skyscraper,#ad-slug=
-wrapper,#ad-small-banner,#ad-space,#ad-splash,#ad-spot,#ad-target,#ad-tar=
get-Leaderbord,#ad-teaser,#ad-text,#ad-top,#ad-top-banner,#ad-top-text-low=
,#ad-tower,#ad-trailerboard-spot,#ad-typ1,#ad-west,#ad-wrap,#ad-wrap-right=
,#ad-wrapper,#ad-wrapper1,#ad-yahoo-simple,#ad1,#ad125BL,#ad125BR,#ad125TL=
,#ad125TR,#ad125x125,#ad160x600,#ad160x600right,#ad1Sp,#ad2,#ad2Sp,#ad3,#a=
d300,#ad300-250,#ad300X250,#ad300_x_250,#ad300x150,#ad300x250,#ad300x250Mo=
dule,#ad300x60,#ad300x600,#ad300x600_callout,#ad336,#ad336x280,#ad375x85,#=
ad4,#ad468,#ad468x60,#ad468x60_top,#ad526x250,#ad600,#ad7,#ad728,#ad728Mid=
,#ad728Top,#ad728Wrapper,#ad728x90,#adBadges,#adBanner,#adBanner120x600,#a=
dBanner160x600,#adBanner336x280,#adBannerTable,#adBannerTop,#adBar,#adBloc=
k125,#adBlocks,#adBox,#adBox350,#adBox390,#adComponentWrapper,#adContainer=
,#adContainer_1,#adContainer_2,#adContainer_3,#adDiv,#adFps,#adFtofrs,#adG=
allery,#adGroup1,#adHeader,#adIsland,#adL,#adLB,#adLabel,#adLayer,#adLeade=
rTop,#adLeaderboard,#adMPU,#adMiddle0Frontpage,#adMiniPremiere,#adP,#adPla=
ceHolderRight,#adPlacer,#adRight,#adSenseModule,#adSenseWrapper,#adServer_=
marginal,#adSidebar,#adSidebarSq,#adSky,#adSkyscraper,#adSlider,#adSpace3,=
#adSpace300_ifrMain,#adSpace4,#adSpace5,#adSpace6,#adSpace7,#adSpace_foote=
r,#adSpace_right,#adSpace_top,#adSpacer,#adSpecial,#adSpot-Leader,#adSpot-=
banner,#adSpot-island,#adSpot-mrec1,#adSpot-sponsoredlinks,#adSpot-textbox=
1,#adSpot-widestrip,#adSpotAdvertorial,#adSpotIsland,#adSpotSponsoredLinks=
,#adSquare,#adStaticA,#adStrip,#adSuperAd,#adSuperPremiere,#adSuperbanner,=
#adTableCell,#adTag1,#adTag2,#adText,#adText_container,#adTile,#adTop,#adT=
opboxright,#adTower,#adUnit,#adWrapper,#adZoneTop,#ad_160x160,#ad_160x600,=
#ad_190x90,#ad_300,#ad_300_250,#ad_300_250_1,#ad_300x250,#ad_300x90,#ad_46=
8_60,#ad_5,#ad_728_foot,#ad_728x90,#ad_940,#ad_984,#ad_A,#ad_B,#ad_Banner,=
#ad_C,#ad_C2,#ad_D,#ad_E,#ad_F,#ad_G,#ad_H,#ad_I,#ad_J,#ad_K,#ad_L,#ad_M,#=
ad_N,#ad_O,#ad_P,#ad_YieldManager-300x250,#ad_anchor,#ad_area,#ad_banner,#=
ad_banner_top,#ad_bar,#ad_block_1,#ad_block_2,#ad_bottom,#ad_box_colspan,#=
ad_branding,#ad_bs_area,#ad_center_monster,#ad_container,#ad_container_mar=
ginal,#ad_container_side,#ad_container_top,#ad_content_top,#ad_content_wra=
p,#ad_feature,#ad_firstpost,#ad_footer,#ad_front_three,#ad_fullbanner,#ad_=
global_below_navbar,#ad_global_header,#ad_haha_1,#ad_haha_4,#ad_halfpage,#=
ad_head,#ad_header,#ad_horizontal,#ad_horseshoe_left,#ad_horseshoe_right,#=
ad_horseshoe_spacer,#ad_horseshoe_top,#ad_hotpots,#ad_in_arti,#ad_island,#=
ad_label,#ad_lastpost,#ad_layer2,#ad_leader,#ad_leaderBoard,#ad_leaderboar=
d,#ad_leaderboard_top,#ad_left,#ad_lrec,#ad_lwr_square,#ad_main,#ad_medium=
_rectangle,#ad_medium_rectangular,#ad_mediumrectangle,#ad_menu_header,#ad_=
middle,#ad_most_pop_234x60_req_wrapper,#ad_mpu,#ad_mpuav,#ad_mrcontent,#ad=
_overlay,#ad_play_300,#ad_rect,#ad_rect_body,#ad_rect_bottom,#ad_rectangle=
,#ad_rectangle_medium,#ad_related_links_div,#ad_related_links_div_program,=
#ad_replace_div_0,#ad_replace_div_1,#ad_report_leaderboard,#ad_report_rect=
angle,#ad_right,#ad_right_main,#ad_ros_tower,#ad_rr_1,#ad_sec,#ad_sec_div,=
#ad_sidebar,#ad_sidebar1,#ad_sidebar2,#ad_sidebar3,#ad_skyscraper,#ad_skys=
craper_text,#ad_slot_leaderboard,#ad_slot_livesky,#ad_slot_sky_top,#ad_spa=
ce,#ad_square,#ad_ss,#ad_table,#ad_term_bottom_place,#ad_thread_first_post=
_content,#ad_top,#ad_top_holder,#ad_tp_banner_1,#ad_tp_banner_2,#ad_unit,#=
ad_vertical,#ad_widget,#ad_window,#ad_wrapper,#adbanner,#adbig,#adbnr,#adb=
oard,#adbody,#adbottom,#adbox,#adbox1,#adbox2,#adclear,#adcode,#adcode1,#a=
dcode2,#adcode3,#adcode4,#adcolumnwrapper,#adcontainer,#adcontainerRight,#=
adcontainsm,#adcontent,#adcontrolPushSite,#add_ciao2,#addbottomleft,#addiv=
-bottom,#addiv-top,#adfooter_728x90,#adframe:not(frameset),#adhead,#adhead=
_g,#adheader,#adhome,#adiframe1_iframe,#adiframe2_iframe,#adiframe3_iframe=
,#adimg,#adition_content_ad,#adlabel,#adlabelFooter,#adlayerad,#adleaderbo=
ard,#adleft,#adlinks,#adlinkws,#adlrec,#admid,#admiddle3center,#admiddle3l=
eft,#adposition,#adposition-C,#adposition-FPMM,#adposition2,#adposition3,#=
adposition4,#adrectangle,#adrectanglea,#adrectangleb,#adrig,#adright,#adri=
ght2,#adrighthome,#ads-468,#ads-area,#ads-block,#ads-bot,#ads-bottom,#ads-=
col,#ads-dell,#ads-horizontal,#ads-indextext,#ads-leaderboard1,#ads-lrec,#=
ads-menu,#ads-middle,#ads-prices,#ads-rhs,#ads-right,#ads-top,#ads-vers7,#=
ads160left,#ads2,#ads300,#ads300Bottom,#ads300Top,#ads336x280,#ads7,#ads72=
8bottom,#ads728top,#ads790,#adsDisplay,#adsID,#ads_160,#ads_300,#ads_728,#=
ads_banner,#ads_belowforumlist,#ads_belownav,#ads_bottom_inner,#ads_bottom=
_outer,#ads_catDiv,#ads_footer,#ads_html1,#ads_html2,#ads_right,#ads_right=
_sidebar,#ads_sidebar_roadblock,#ads_top,#ads_watch_top_square,#ads_zone27=
,#adsbottom,#adsbox,#adscolumn,#adsense,#adsense-tag,#adsense-text,#adsens=
eOne,#adsenseWrap,#adsense_inline,#adsense_leaderboard,#adsense_overlay,#a=
dsense_placeholder_2,#adsenseheader,#adsensetopplay,#adsensewidget-3,#adse=
rv,#adsky,#adskyscraper,#adslot,#adsonar,#adspace,#adspace-300x250,#adspac=
e300x250,#adspaceBox,#adspaceBox300,#adspace_header,#adspot-1,#adspot-149x=
170,#adspot-1x4,#adspot-2,#adspot-295x60,#adspot-2a,#adspot-2b,#adspot-300=
x250-pos-1,#adspot-300x250-pos-2,#adspot-468x60-pos-2,#adspot-a,#adspot300=
x250,#adsright,#adstop,#adt,#adtab,#adtag_right_side,#adtech_googleslot_03=
c,#adtech_takeover,#adtop,#adtxt,#adv-masthead,#adv_google_300,#adv_google=
_728,#adv_top_banner_wrapper,#adver1,#adver2,#adver3,#adver4,#adver5,#adve=
r6,#adver7,#advert,#advert-1,#advert-120,#advert-boomer,#advert-display,#a=
dvert-header,#advert-leaderboard,#advert-links-bottom,#advert-skyscraper,#=
advert-top,#advert1,#advertBanner,#advertRight,#advert_250x250,#advert_box=
,#advert_leaderboard,#advert_lrec_format,#advert_mid,#advert_mpu,#advert_r=
ight_skyscraper,#advertbox,#advertbox2,#advertbox3,#advertbox4,#adverthome=
,#advertise,#advertise-now,#advertise1,#advertiseHere,#advertisement,#adve=
rtisement160x600,#advertisement728x90,#advertisementLigatus,#advertisement=
Prio2,#advertiser-container,#advertiserLinks,#advertising,#advertising-ban=
ner,#advertising-caption,#advertising-container,#advertising-control,#adve=
rtising-skyscraper,#advertisingModule160x600,#advertisingModule728x90,#adv=
ertisment,#advertismentElementInUniversalbox,#advertorial,#adverts,#advert=
s-top-container,#adverts-top-left,#adverts-top-middle,#adverts-top-right,#=
advertsingle,#advt,#adwhitepaperwidget,#adwin_rec,#adwith,#adwords-4-conta=
iner,#adwrapper,#adxBigAd,#adxMiddle5,#adxSponLink,#adxSponLinkA,#adxtop,#=
adzbanner,#adzerk,#adzoneBANNER,#affinityBannerAd,#agi-ad300x250,#agi-ad30=
0x250overlay,#agi-sponsored,#alert_ads,#anchorAd,#annoying_ad,#ap_adframe,=
#apiBackgroundAd,#apiTopAdWrap,#apmNADiv,#araHealthSponsorAd,#article-ad-c=
ontainer,#article-box-ad,#articleAdReplacement,#articleLeftAdColumn,#artic=
leSideAd,#article_ad,#article_box_ad,#asinglead,#atlasAdDivGame,#banner-30=
0x250,#banner-ad,#banner-ad-container,#banner-ads,#banner250x250,#banner46=
8x60,#banner728x90,#bannerAd,#bannerAdTop,#bannerAd_ctr,#banner_ad,#banner=
_ad_footer,#banner_admicro,#banner_ads,#banner_content_ad,#banner_topad,#b=
annerad,#bannerad2,#bbccom_mpu,#bbccom_storyprintsponsorship,#bbo_ad1,#bg-=
footer-ads,#bg-footer-ads2,#bg_YieldManager-300x250,#bigAd,#bigBoxAd,#biga=
d300outer,#bigadbox,#bigadspot,#billboard_ad,#block-ad_cube-1,#block-opena=
ds-1,#block-openads-3,#block-openads-4,#block-openads-5,#block-thewrap_ads=
_250x300-0,#block_advert,#blog-ad,#blog_ad_content,#blog_ad_opa,#blox-big-=
ad,#blox-big-ad-bottom,#blox-big-ad-top,#blox-halfpage-ad,#blox-tile-ad,#b=
lox-tower-ad,#book-ad,#botad,#bott_ad2,#bott_ad2_300,#bottom-ad,#bottom-ad=
-container,#bottom-ads,#bottomAd,#bottomAdCCBucket,#bottomAdContainer,#bot=
tomAdSense,#bottomAdSenseDiv,#bottomAds,#bottomRightAd,#bottomRightAdSpace=
,#bottom_ad,#bottom_ad_area,#bottom_ads,#bottom_banner_ad,#bottom_overture=
,#bottom_sponsor_ads,#bottom_sponsored_links,#bottom_text_ad,#bottomad,#bo=
ttomads,#bottomadsense,#bottomadwrapper,#bottomleaderboardad,#box-content-=
ad,#box-googleadsense-1,#box-googleadsense-r,#box1ad,#boxAd300,#boxAdConta=
iner,#box_ad,#box_mod_googleadsense,#boxad1,#boxad2,#boxad3,#boxad4,#boxad=
5,#bpAd,#bps-header-ad-container,#btr_horiz_ad,#burn_header_ad,#button-ads=
-horizontal,#button-ads-vertical,#buttonAds,#buttonAdsContainer,#button_ad=
_container,#button_ad_wrap,#buttonad,#buy-sell-ads,#c4ad-Middle1,#caAdLarg=
er,#catad,#cellAd,#channel_ad,#channel_ads,#ciHomeRHSAdslot,#circ_ad,#cnnR=
R336ad,#cnnTopAd,#colRightAd,#collapseobj_adsection,#column4-google-ads,#c=
ommercial_ads,#common_right_ad_wrapper,#common_right_lower_ad_wrapper,#com=
mon_right_lower_adspace,#common_right_lower_player_ad_wrapper,#common_righ=
t_lower_player_adspace,#common_right_player_ad_wrapper,#common_right_playe=
r_adspace,#common_right_right_adspace,#common_top_adspace,#companion-ad,#c=
ompanionAdDiv,#containerLocalAds,#containerLocalAdsInner,#containerMrecAd,=
#content-ad-header,#content-header-ad,#contentAd,#contentTopAds2,#content_=
ad,#content_ad_square,#content_ad_top,#content_ads_content,#content_box_30=
0body_sponsoredoffers,#content_box_adright300_google,#content_mpu,#content=
ad,#contentad_imtext,#contentad_right,#contentads,#contentinlineAd,#contex=
tad,#contextual-ads,#contextual-ads-block,#contextualad,#coverads,#ctl00_A=
dspace_Top_Height,#ctl00_BottomAd,#ctl00_ContentRightColumn_RightColumn_Ad=
1_BanManAd,#ctl00_ContentRightColumn_RightColumn_PremiumAd1_ucBanMan_BanMa=
nAd,#ctl00_LHTowerAd,#ctl00_LeftHandAd,#ctl00_MasterHolder_IBanner_adHolde=
r,#ctl00_TopAd,#ctl00_TowerAd,#ctl00_VBanner_adHolder,#ctl00_abot_bb,#ctl0=
0_adFooter,#ctl00_atop_bt,#ctl00_cphMain_hlAd1,#ctl00_cphMain_hlAd2,#ctl00=
_cphMain_hlAd3,#ctl00_ctl00_MainPlaceHolder_itvAdSkyscraper,#ctl00_ctl00_c=
tl00_Main_Main_PlaceHolderGoogleTopBanner_MPTopBannerAd,#ctl00_ctl00_ctl00=
_Main_Main_SideBar_MPSideAd,#ctl00_ctl00_ctl00_tableAdsTop,#ctl00_dlTilesA=
ds,#ctl00_m_skinTracker_m_adLBL,#ctl00_phCrackerMain_ucAffiliateAdvertDisp=
layMiddle_pnlAffiliateAdvert,#ctl00_phCrackerMain_ucAffiliateAdvertDisplay=
Right_pnlAffiliateAdvert,#ctrlsponsored,#cubeAd,#cube_ads,#cube_ads_inner,=
#cubead,#cubead-2,#dart_160x600,#dc-display-right-ad-1,#dcol-sponsored,#de=
fer-adright,#detail_page_vid_topads,#divAd,#divAdBox,#divMenuAds,#divWNAdH=
eader,#divWrapper_Ad,#div_video_ads,#dlads,#dni-header-ad,#dnn_ad_banner,#=
download_ads,#ds-mpu,#editorsmpu,#evotopTen_advert,#ex-ligatus,#exads,#fea=
turead,#featured-advertisements,#featuredAdContainer2,#featuredAds,#feed_l=
inks_ad_container,#first-300-ad,#first-adlayer,#first_ad_unit,#firstad,#fl=
_hdrAd,#flexiad,#footer-ad,#footer-advert,#footer-adverts,#footer-sponsore=
d,#footerAd,#footerAdDiv,#footerAds,#footerAdvertisement,#footerAdverts,#f=
ooter_ad,#footer_ad_01,#footer_ad_block,#footer_ad_container,#footer_ads,#=
footer_adspace,#footer_text_ad,#footerad,#fr_ad_center,#frame_admain,#frnA=
dSky,#frnBannerAd,#frnContentAd,#from_our_sponsors,#front_advert,#front_mp=
u,#ft-ad,#ft-ad-1,#ft-ad-container,#ft_mpu,#fusionad,#fw-advertisement,#g_=
ad,#g_adsense,#ga_300x250,#gad,#galleries-tower-ad,#gallery-ad-m0,#gallery=
_ads,#game-info-ad,#global_header_ad_area,#gmi-ResourcePageAd,#gmi-Resourc=
ePageLowerAd,#google-ad,#google-ad-art,#google-ad-table-right,#google-ad-t=
ower,#google-ads,#google-ads-bottom,#google-ads-header,#google-ads-left-si=
de,#google-adsense-mpusize,#googleAd,#googleAds,#googleAdsSml,#googleAdsen=
se,#googleAdsenseBanner,#googleAdsenseBannerBlog,#googleAdwordsModule,#goo=
gleAfcContainer,#googleSearchAds,#googleShoppingAdsRight,#googleShoppingAd=
sTop,#googleSubAds,#google_ad,#google_ad_container,#google_ad_inline,#goog=
le_ad_test,#google_ads,#google_ads_frame1,#google_ads_frame1_anchor,#googl=
e_ads_test,#google_ads_top,#google_adsense_home_468x60_1,#googlead,#google=
adbox,#googleads,#googleadsense,#googlesponsor,#grid_ad,#gsyadrectangleloa=
d,#gsyadrightload,#gsyadtop,#gsyadtopload,#gtopadvts,#half-page-ad,#halfPa=
geAd,#halfe-page-ad-box,#hdtv_ad_ss,#head-ad,#headAd,#head_advert,#headad,=
#header-ad,#header-ad-rectangle-container,#header-ads,#header-adspace,#hea=
der-advert,#header-advertisement,#header-advertising,#headerAd,#headerAdBa=
ckground,#headerAdContainer,#headerAdWrap,#headerAds,#headerAdsWrapper,#he=
aderTopAd,#header_ad,#header_ad_728_90,#header_ad_container,#header_adcode=
,#header_ads,#header_advertisement_top,#header_leaderboard_ad_container,#h=
eader_publicidad,#headerad,#headeradbox,#headerads,#headeradwrap,#headline=
_ad,#hiddenadAC,#hideads,#hl-sponsored-results,#homeTopRightAd,#home_ad,#h=
ome_bottom_ad,#home_contentad,#home_mpu,#home_spensoredlinks,#homepage-ad,=
#homepageAdsTop,#homepage_right_ad,#homepage_right_ad_container,#hometop_2=
34x60ad,#hor_ad,#horizontal-banner-ad,#horizontal_ad,#horizontal_ad_top,#h=
orizontalads,#houseAd,#hp-store-ad,#hpV2_300x250Ad,#hpV2_googAds,#icePage_=
SearchLinks_AdRightDiv,#icePage_SearchLinks_DownloadToolbarAdRightDiv,#in_=
serp_ad,#inadspace,#indexad,#inlinead,#inlinegoogleads,#inlist-ad-block,#i=
nner-advert-row,#insider_ad_wrapper,#instoryad,#int-ad,#interstitial_ad_wr=
apper,#islandAd,#j_ad,#ji_medShowAdBox,#jmp-ad-buttons,#joead,#joead2,#ka_=
adRightSkyscraperWide,#landing-adserver,#largead,#lateAd,#layerTLDADSERV,#=
lb-sponsor-left,#lb-sponsor-right,#leader-board-ad,#leader-sponsor,#leader=
AdContainer,#leader_board_ad,#leaderad,#leaderad_section,#leaderboard-ad,#=
leaderboard-bottom-ad,#leaderboard_ad,#left-ad-skin,#left-lower-adverts,#l=
eft-lower-adverts-container,#leftAdContainer,#leftAd_rdr,#leftAdvert,#left=
SectionAd300-100,#left_ad,#left_adspace,#leftad,#leftads,#lg-banner-ad,#li=
gatus,#linkAds,#linkads,#live-ad,#longAdSpace,#lowerAdvertisementImg,#lowe=
rads,#lowerthirdad,#lowertop-adverts,#lowertop-adverts-container,#lrecad,#=
mBannerAd,#main-ad,#main-ad160x600,#main-ad160x600-img,#main-ad728x90,#mai=
n-bottom-ad,#mainAd,#mainAdUnit,#mainAdvert,#main_ad,#main_rec_ad,#main_to=
p_ad_container,#marketing-promo,#mastAdvert,#mastad,#mastercardAd,#masthea=
d_ad,#masthead_topad,#medRecAd,#media_ad,#mediumAdvertisement,#medrectad,#=
menuAds,#mi_story_assets_ad,#mid-ad300x250,#mid-table-ad,#midRightTextAds,=
#mid_ad_div,#mid_ad_title,#mid_mpu,#midadd,#midadspace,#middle-ad,#middlea=
d,#middleads,#midrect_ad,#midstrip_ad,#mini-ad,#module-google_ads,#module_=
ad,#module_box_ad,#module_sky_scraper,#monsterAd,#moogleAd,#most_popular_a=
d,#mpu,#mpu-advert,#mpuAd,#mpuDiv,#mpuSlot,#mpuWrapper,#mpuWrapperAd,#mpu_=
banner,#mpu_holder,#mpu_text_ad,#mpuad,#mrecAdContainer,#ms_ad,#msad,#mult=
iLinkAdContainer,#myads_HeaderButton,#n_sponsor_ads,#namecom_ad_hosting_ma=
in,#narrow_ad_unit,#natadad300x250,#national_microlink_ads,#nationalad,#na=
vi_banner_ad_780,#nba300Ad,#nbaMidAds,#nbaVid300Ad,#new_topad,#ng_rtcol_ad=
,#noresultsads,#northad,#oanda_ads,#onespot-ads,#online_ad,#p-googleadsens=
e,#page-header-ad,#pageAds,#pageAdsDiv,#page_content_top_ad,#pagelet_adbox=
,#panelAd,#pb_report_ad,#pcworldAdBottom,#pcworldAdTop,#pinball_ad,#player=
-below-advert,#player_ad,#player_ads,#pod-ad-video-page,#portlet-advertise=
ment-left,#portlet-advertisement-right,#post-promo-ad,#post5_adbox,#post_a=
d,#priceGrabberAd,#print_ads,#printads,#product-adsense,#promo-ad,#promoAd=
s,#ps-vertical-ads,#pub468x60,#publicidad,#pushdown_ad,#qm-ad-big-box,#qm-=
ad-sky,#qm-dvdad,#r1SoftAd,#rail_ad1,#rail_ad2,#realEstateAds,#rectAd,#rec=
t_ad,#rectangle-ad,#rectangle_ad,#refine-300-ad,#region-top-ad,#rh-ad-cont=
ainer,#rh_tower_ad,#rhs_ads,#rhsadvert,#right-ad,#right-ad-skin,#right-ad-=
title,#right-ads-3,#right-box-ad,#right-featured-ad,#right-mpu-1-ad-contai=
ner,#right-uppder-adverts,#right-uppder-adverts-container,#rightAd,#rightA=
d300x250,#rightAdColumn,#rightAd_rdr,#rightColAd,#rightColumnMpuAd,#rightC=
olumnSkyAd,#right_ad,#right_ad_wrapper,#right_ads,#right_advertisement,#ri=
ght_advertising,#right_column_ads,#rightad,#rightadContainer,#rightadvertb=
ar-doubleclickads,#rightbar-ad,#rightside-ads,#rightside_ad,#righttop-adve=
rts,#righttop-adverts-container,#rm_ad_text,#ros_ad,#rotatingads,#row2AdCo=
ntainer,#rt-ad,#rt-ad-top,#rt-ad468,#rtMod_ad,#rtmod_ad,#sAdsBox,#sb-ad-sq=
,#sb_advert,#search-google-ads,#searchAdSenseBox,#searchAdSenseBoxAd,#sear=
chAdSkyscraperBox,#search_ads,#search_result_ad,#second-adlayer,#secondBox=
AdContainer,#section-container-ddc_ads,#section-sponsors,#section_advertor=
ial_feature,#servfail-ads,#sew-ad1,#shoppingads,#show-ad,#showAd,#showad,#=
side-ad,#side-ad-container,#sideAd,#sideAdSub,#sideBarAd,#side_ad,#side_ad=
_wrapper,#side_ads_by_google,#side_sky_ad,#sidead,#sideads,#sidebar-125x12=
5-ads,#sidebar-125x125-ads-below-index,#sidebar-ad,#sidebar-ad-boxes,#side=
bar-ad-space,#sidebar-ad-wrap,#sidebar-ad3,#sidebar-ads,#sidebar2ads,#side=
bar_ad_widget,#sidebar_ads,#sidebar_ads_180,#sidebar_sponsoredresult_body,=
#sidebarad,#sideline-ad,#single-mpu,#singlead,#site-leaderboard-ads,#site_=
top_ad,#sitead,#sky-ad,#skyAd,#skyAdContainer,#skyScrapperAd,#sky_ad,#sky_=
advert,#skyads,#skyscraper-ad,#skyscraperAd,#skyscraperAdContainer,#skyscr=
aper_ad,#skyscraper_advert,#skyscraperad,#sliderAdHolder,#slideshow_ad_300=
x250,#sm-banner-ad,#small_ad,#smallerAd,#specials_ads,#speeds_ads,#speeds_=
ads_fstitem,#speedtest_mrec_ad,#sphereAd,#splinks,#sponLinkDiv_1,#sponlink=
,#sponsAds,#sponsLinks,#spons_left,#sponseredlinks,#sponsor-search,#sponso=
rAd1,#sponsorAd2,#sponsorAdDiv,#sponsorLinks,#sponsorTextLink,#sponsor_ban=
derole,#sponsor_box,#sponsor_deals,#sponsor_panSponsor,#sponsor_recommenda=
tions,#sponsorbar,#sponsorbox,#sponsored,#sponsored-ads,#sponsored-feature=
s,#sponsored-links,#sponsored-resources,#sponsored1,#sponsoredBox1,#sponso=
redBox2,#sponsoredLinks,#sponsoredList,#sponsoredResults,#sponsoredSiteMai=
nline,#sponsoredSiteSidebar,#sponsored_ads_v4,#sponsored_content,#sponsore=
d_game_row_listing,#sponsored_links,#sponsored_v12,#sponsoredlinks,#sponso=
redlinks_cntr,#sponsoredresults_top,#sponsoredwellcontainerbottom,#sponsor=
edwellcontainertop,#sponsorlink,#sponsors,#sponsorshipBadge,#spotlightAds,=
#spotlightad,#sqAd,#square-sponsors,#squareAd,#squareAdSpace,#squareAds,#s=
quare_ad,#start_middle_container_advertisment,#sticky-ad,#stickyBottomAd,#=
story-ad-a,#story-ad-b,#story-leaderboard-ad,#story-sponsoredlinks,#storyA=
d,#storyAdWrap,#storyad2,#subpage-ad-right,#subpage-ad-top,#swads,#synch-a=
d,#systemad_background,#tabAdvertising,#takeoverad,#tblAd,#tbl_googlead,#t=
cwAd,#template_ad_leaderboard,#tertiary_advertising,#text-ad,#text-ads,#te=
xtAd,#textAds,#text_ad,#text_ads,#text_advert,#textad,#textad3,#the-last-a=
d-standing,#thefooterad,#themis-ads,#tile-ad,#tmglBannerAd,#top-ad,#top-ad=
-container,#top-ad-menu,#top-ads,#top-ads-tabs,#top-advertisement,#top-ban=
ner-ad,#top-search-ad-wrapper,#topAd,#topAd728x90,#topAdBanner,#topAdConta=
iner,#topAdSenseDiv,#topAds,#topAdsContainer,#topAdvert,#topBannerAd,#topN=
avLeaderboardAdHolder,#topRightBlockAdSense,#top_ad,#top_ad_area,#top_ad_g=
ame,#top_ad_wrapper,#top_ads,#top_advertise,#top_advertising,#top_right_ad=
,#top_wide_ad,#topad,#topad_left,#topad_right,#topadblock,#topaddwide,#top=
ads,#topadsense,#topadspace,#topadzone,#topcustomad,#topleaderboardad,#top=
rightAdvert,#toprightad,#topsponsored,#toptextad,#towerad,#ttp_ad_slot1,#t=
tp_ad_slot2,#twogamesAd,#txt_link_ads,#undergameAd,#upperAdvertisementImg,=
#upperMpu,#upperad,#urban_contentad_1,#urban_contentad_2,#urban_contentad_=
article,#v_ad,#vert_ad,#vert_ad_placeholder,#vertical_ad,#vertical_ads,#vi=
deoAd,#video_cnv_ad,#video_overlay_ad,#videoadlogo,#viewportAds,#walltopad=
,#weblink_ads_container,#welcomeAdsContainer,#welcome_ad_mrec,#welcome_adv=
ertisement,#wf_ContentAd,#wf_FrontSingleAd,#wf_SingleAd,#wf_bottomContentA=
d,#wgtAd,#whatsnews_top_ad,#whitepaper-ad,#whoisRightAdContainer,#wide_ad_=
unit_top,#widget_advertisement,#wrapAdRight,#wrapAdTop,#y708-ad-expedia,#y=
708-ad-lrec,#y708-ad-partners,#y708-ad-ysm,#y708-advertorial-marketplace,#=
yahoo-ads,#yahoo-sponsors,#yahooSponsored,#yahoo_ads,#yahoo_ads_2010,#yaho=
oad-tbl,#yan-sponsored,#ybf-ads,#yfi_fp_ad_mort,#yfi_fp_ad_nns,#yfi_pf_ad_=
mort,#ygrp-sponsored-links,#ymap_adbanner,#yn-gmy-ad-lrec,#yreSponsoredLin=
ks,#ysm_ad_iframe,#zoneAdserverMrec,#zoneAdserverSuper,.ADBAR,.ADPod,.AD_A=
LBUM_ITEMLIST,.AD_MOVIE_ITEM,.AD_MOVIE_ITEMLIST,.AD_MOVIE_ITEMROW,.Ad-MPU,=
.Ad120x600,.Ad160x600,.Ad160x600left,.Ad160x600right,.Ad247x90,.Ad300x250,=
.Ad300x250L,.Ad728x90,.AdBox,.AdBox7,.AdContainerBox308,.AdHeader,.AdHere,=
.AdInfo,.AdMedium,.AdPlaceHolder,.AdRingtone,.AdSense,.AdSpace,.AdTextSmal=
lFont,.AdTitle,.AdUnit,.AdUnit300,.Ad_C,.Ad_D_Wrapper,.Ad_E_Wrapper,.Ad_Ri=
ght,.Ads,.AdsBoxBottom,.AdsBoxSection,.AdsBoxTop,.AdsLinks1,.AdsLinks2,.Ad=
vert,.AdvertMidPage,.AdvertiseWithUs,.AdvertisementTextTag,.ArticleAd,.Art=
icleInlineAd,.BannerAd,.BigBoxAd,.BlockAd,.BottomAdContainer,.BottomAffili=
ate,.BoxAd,.CG_adkit_leaderboard,.CG_details_ad_dropzone,.ComAread,.Commen=
tAd,.ContentAd,.ContentAds,.DAWRadvertisement,.DeptAd,.DisplayAd,.FT_Ad,.F=
latAds,.GOOGLE_AD,.GoogleAd,.HPNewAdsBannerDiv,.HPRoundedAd,.HomeContentAd=
,.IABAdSpace,.LeftAd,.LeftTowerAd,.M2Advertisement,.MD_adZone,.MOS-ad-hack=
,.MPU,.MPUHolder,.MPUTitleWrapperClass,.MiddleAdContainer,.OpenXad,.PU_Dou=
bleClickAdsContent,.Post5ad,.RBboxAd,.RectangleAd,.RelatedAds,.RightGoogle=
AFC,.RightRailTop300x250Ad,.RightSponsoredAdTitle,.RightTowerAd,.SideAdCol=
,.SidebarAd,.SkyAdContainer,.SponsorCFrame,.SponsoredAdTitle,.SponsoredCon=
tent,.SponsoredLinks,.SponsoredLinksGrayBox,.SponsorshipText,.SquareAd,.St=
andardAdLeft,.StandardAdRight,.TextAd,.TheEagleGoogleAdSense300x250,.TopAd=
,.TopAdContainer,.TopAdL,.TopAdR,.TopBannerAd,.UIStandardFrame_SidebarAds,=
.UIWashFrame_SidebarAds,.UnderAd,.VerticalAd,.VideoAd,.WidgetAdvertiser,.a=
160x600,.a728x90,.ad-120x600,.ad-160,.ad-160x600,.ad-250,.ad-300,.ad-300-b=
lock,.ad-300-blog,.ad-300x100,.ad-300x250,.ad-300x250-right0,.ad-350,.ad-3=
55x75,.ad-600,.ad-635x40,.ad-728,.ad-728x90,.ad-728x90-1,.ad-above-header,=
.ad-adlink-bottom,.ad-adlink-side,.ad-background,.ad-banner,.ad-bigsize,.a=
d-block,.ad-blog2biz,.ad-bottom,.ad-box,.ad-break,.ad-btn,.ad-btn-heading,=
.ad-button,.ad-cell,.ad-container,.ad-disclaimer,.ad-display,.ad-div,.ad-e=
nabled,.ad-feedback,.ad-filler,.ad-footer,.ad-footer-leaderboard,.ad-googl=
e,.ad-graphic-large,.ad-gray,.ad-hdr,.ad-head,.ad-holder,.ad-homeleaderboa=
rd,.ad-img,.ad-island,.ad-label,.ad-leaderboard,.ad-links,.ad-lrec,.ad-med=
ium,.ad-medium-two,.ad-mpu,.ad-note,.ad-notice,.ad-other,.ad-permalink,.ad=
-placeholder,.ad-postText,.ad-poster,.ad-priority,.ad-rect,.ad-rectangle,.=
ad-rectangle-text,.ad-related,.ad-rh,.ad-ri,.ad-right,.ad-right-header,.ad=
-right-txt,.ad-row,.ad-section,.ad-sidebar300,.ad-sky,.ad-slot,.ad-slot-23=
4-60,.ad-slot-300-250,.ad-slot-728-90,.ad-space,.ad-space-mpu-box,.ad-spot=
,.ad-squares,.ad-statement,.ad-tabs,.ad-text,.ad-text-links,.ad-tile,.ad-t=
itle,.ad-top,.ad-top-left,.ad-unit,.ad-unit-300,.ad-unit-300-wrapper,.ad-u=
nit-anchor,.ad-vert,.ad-vtu,.ad-wrap,.ad-wrapper,.ad-zone-s-q-l,.ad.super,=
.ad0,.ad1,.ad10,.ad120,.ad120x600,.ad125,.ad160,.ad160x600,.ad18,.ad19,.ad=
2,.ad21,.ad250,.ad250c,.ad3,.ad300,.ad300250,.ad300_250,.ad300x100,.ad300x=
250,.ad300x250-hp-features,.ad300x250Top,.ad300x250_container,.ad300x250bo=
x,.ad300x600,.ad310,.ad336x280,.ad343x290,.ad4,.ad400right,.ad450,.ad468,.=
ad468_60,.ad468x60,.ad6,.ad620x70,.ad626X35,.ad7,.ad728,.ad728_90,.ad728x9=
0,.ad728x90_container,.ad8,.ad90x780,.adAgate,.adArea674x60,.adBanner,.adB=
anner300x250,.adBanner728x90,.adBannerTyp1,.adBannerTypSortableList,.adBan=
nerTypW300,.adBar,.adBgBottom,.adBgMId,.adBgTop,.adBottomboxright,.adBox,.=
adBoxBody,.adBoxBorder,.adBoxContent,.adBoxInBignews,.adBoxSidebar,.adBoxS=
ingle,.adCMRight,.adColumn,.adCont,.adContTop,.adContainer,.adContour,.adC=
reative,.adDiv,.adElement,.adFender3,.adFrame,.adFtr,.adFullWidthMiddle,.a=
dGoogle,.adHeader,.adHeadline,.adHolder,.adHome300x250,.adHorisontal,.adIn=
News,.adLabel,.adLeader,.adLeaderForum,.adLeaderboard,.adLeft,.adLoaded,.a=
dLocal,.adMastheadLeft,.adMastheadRight,.adMegaBoard,.adMkt2Colw,.adModule=
,.adNewsChannel,.adNoOutline,.adNoticeOut,.adObj,.adPageBorderL,.adPageBor=
derR,.adPanel,.adRect,.adRight,.adSelfServiceAdvertiseLink,.adServer,.adSl=
ot,.adSpBelow,.adSpace,.adSpacer,.adSponsor,.adSpot,.adSpot-searchAd,.adSp=
ot-textBox,.adSpot-twin,.adSpotIsland,.adSquare,.adSummary,.adSuperboard,.=
adSupertower,.adTD,.adTag,.adText,.adTileWrap,.adTiler,.adTitle,.adTopboxr=
ight,.adTout,.adTxt,.adUnitHorz,.adUnitVert,.adUnitVert_noImage,.adWebBoar=
d,.adWidget,.adWithTab,.adWrap,.adWrapper,.ad_0,.ad_1,.ad_120x90,.ad_125,.=
ad_130x90,.ad_160,.ad_160x600,.ad_2,.ad_200,.ad_250x250,.ad_250x250_w,.ad_=
3,.ad_300,.ad_300_250,.ad_300x250,.ad_300x250_box_right,.ad_336,.ad_336x28=
0,.ad_350x100,.ad_350x250,.ad_468,.ad_468x60,.ad_600,.ad_728,.ad_728x90,.a=
d_Left,.ad_Right,.ad_amazon,.ad_banner_border,.ad_biz,.ad_block_338,.ad_bo=
dy,.ad_border,.ad_botbanner,.ad_bottom_leaderboard,.ad_box,.ad_box2,.ad_bo=
x_ad,.ad_box_div,.ad_callout,.ad_caption,.ad_contain,.ad_container,.ad_con=
tent,.ad_content_wide,.ad_contents,.ad_descriptor,.ad_footer,.ad_framed,.a=
d_front_promo,.ad_head,.ad_header,.ad_hpm,.ad_info_block,.ad_inline,.ad_is=
land,.ad_label,.ad_launchpad,.ad_leader,.ad_leaderboard,.ad_left,.ad_links=
,.ad_linkunit,.ad_loc,.ad_lrec,.ad_main,.ad_medrec,.ad_medrect,.ad_middle,=
.ad_mpu,.ad_mr,.ad_mrec,.ad_mrec_title_article,.ad_mrect,.ad_news,.ad_noti=
ce,.ad_one,.ad_p360,.ad_partner,.ad_partners,.ad_plus,.ad_post,.ad_power,.=
ad_rectangle,.ad_right,.ad_right_col,.ad_row,.ad_sidebar,.ad_skyscraper,.a=
d_slug,.ad_slug_table,.ad_space,.ad_space_300_250,.ad_sponsor,.ad_sponsore=
dsection,.ad_spot_b,.ad_spot_c,.ad_square_r,.ad_square_top,.ad_text,.ad_te=
xt_w,.ad_title,.ad_top,.ad_top_leaderboard,.ad_topright,.ad_tower,.ad_unit=
,.ad_unit_rail,.ad_url,.ad_warning,.ad_wid300,.ad_wide,.ad_wrap,.ad_wrappe=
r,.ad_wrapper_fixed,.ad_wrapper_top,.ad_zone,.adarea,.adarea-long,.adbanne=
r,.adbannerbox,.adbannerright,.adbar,.adbg,.adborder,.adbot,.adbottom,.adb=
ottomright,.adbox,.adbox-outer,.adbox_300x600,.adbox_366x280,.adbox_468X60=
,.adbox_bottom,.adboxclass,.adbuttons,.adcode,.adcol1,.adcol2,.adcolumn,.a=
dcolumn_wrapper,.adcont,.adcontainer,.adcopy,.addiv,.adfoot,.adfootbox,.ad=
frame,.adhead,.adheader,.adheader100,.adhere,.adhered,.adhi,.adhint,.adhol=
der,.adhoriz,.adi,.adiframe,.adinfo,.adinside,.adjlink,.adkit,.adkit-adver=
t,.adkit-lb-footer,.adlabel,.adlabel-horz,.adlabel-vert,.adleft,.adleft1,.=
adline,.adlink,.adlinks,.adlist,.adlnklst,.admarker,.admedrec,.admessage,.=
admodule,.admpu,.adnation-banner,.adnotice,.adops,.adpadding,.adpane,.adpi=
c,.adprice,.adright,.adrotate_widget,.adrow,.adrow-post,.adrule,.ads-125,.=
ads-728x90-wrap,.ads-banner,.ads-below-content,.ads-categories-bsa,.ads-fa=
vicon,.ads-links-general,.ads-mpu,.ads-profile,.ads-right,.ads-section,.ad=
s-sidebar,.ads-sky,.ads-stripe,.ads-text,.ads-widget-partner-gallery,.ads2=
,.ads3,.ads300,.ads468,.ads728,.ads:not(body),.adsArea,.adsBelowHeadingNor=
mal,.adsBlock,.adsBox,.adsCont,.adsDiv,.adsFull,.adsImages,.adsRight,.adsT=
extHouse,.adsTop,.adsTower2,.adsTowerWrap,.adsWithUs,.ads_125_square,.ads_=
180,.ads_300,.ads_300x250,.ads_337x280,.ads_728x90,.ads_big,.ads_big-half,=
.ads_brace,.ads_catDiv,.ads_container,.ads_disc_anchor,.ads_disc_leader,.a=
ds_disc_lwr_square,.ads_disc_skyscraper,.ads_disc_square,.ads_div,.ads_hea=
der,.ads_leaderboard,.ads_mpu,.ads_outer,.ads_rectangle,.ads_right,.ads_sc=
_bl_i,.ads_sc_tl_i,.ads_show_if,.ads_side,.ads_sidebar,.ads_singlepost,.ad=
s_spacer,.ads_takeover,.ads_title,.ads_tr,.ads_widesky,.ads_wrapperads_top=
,.adsblockvert,.adsborder,.adsbottom,.adsbyyahoo,.adsc,.adscaleAdvert,.ads=
container,.adscreen,.adsection_a2,.adsection_c2,.adsense,.adsense-ad,.adse=
nse-category,.adsense-category-bottom,.adsense-heading,.adsense-right,.ads=
ense-title,.adsense3,.adsenseAds,.adsenseBlock,.adsenseContainer,.adsenseG=
reenBox,.adsense_bdc_v2,.adsensebig,.adsenseblock,.adsenseblock_bottom,.ad=
senseblock_top,.adsenselr,.adsensem_widget,.adsensesq,.adset,.adsforums,.a=
dside,.adsidebox,.adsider,.adsingle,.adsleft,.adslogan,.adsmalltext,.adsme=
ssage,.adspace,.adspace-MR,.adspace180,.adspace_bottom,.adspace_buysell,.a=
dspace_rotate,.adspace_skyscraper,.adspacer,.adspot,.adspot728x90,.adstop,=
.adstrip,.adtable,.adtag,.adtech,.adtext,.adtext_gray,.adtext_horizontal,.=
adtext_onwhite,.adtext_vertical,.adtile,.adtips,.adtips1,.adtop,.adtravel,=
.adtxt,.adv-mpu,.adverTag,.adver_cont_below,.advert,.advert-article-bottom=
,.advert-bannerad,.advert-box,.advert-head,.advert-horizontal,.advert-iab-=
300-250,.advert-iab-468-60,.advert-mpu,.advert-skyscraper,.advert-text,.ad=
vert4,.advert5,.advert8,.advertColumn,.advertCont,.advertContainer,.advert=
Headline,.advertRight,.advertText,.advertTitleSky,.advert_468x60,.advert_b=
ox,.advert_cont,.advert_label,.advert_leaderboard,.advert_list,.advert_not=
e,.advert_top,.advertheader-red,.advertise,.advertise-here,.advertise-home=
strip,.advertise-horz,.advertise-leaderboard,.advertise-vert,.advertiseCon=
tainer,.advertiseText,.advertise_ads,.advertise_here,.advertise_link,.adve=
rtise_link_sidebar,.advertisement,.advertisement-728x90,.advertisement-blo=
ck,.advertisement-text,.advertisement-top,.advertisement468,.advertisement=
Box,.advertisementColumnGroup,.advertisementContainer,.advertisementHeader=
,.advertisementLabel,.advertisementPanel,.advertisement_btm,.advertisement=
_caption,.advertisement_g,.advertisement_header,.advertisement_horizontal,=
.advertisement_top,.advertiser,.advertiser-links,.advertising,.advertising=
-banner,.advertising-header,.advertising-local-links,.advertising2,.advert=
isingTable,.advertising_block,.advertising_images,.advertisment,.advertism=
ent_two,.advertize,.advertorial,.advertorial-2,.advertorial-promo-box,.adv=
erts,.advt,.advt-banner-3,.advt300,.advt720,.adwordListings,.adwordsHeader=
,.adwrap,.adwrapper,.adwrapper-lrec,.adwrapper948,.affiliate,.affiliate-li=
nk,.affiliate-sidebar,.affiliateAdvertText,.affinityAdHeader,.agi-adsalesl=
inks,.alb-content-ad,.alt_ad,.anchorAd,.another_text_ad,.answer_ad_content=
,.aolSponsoredLinks,.aopsadvert,.apiAdMarkerAbove,.apiAds,.archive-ads,.ar=
t_ads,.article-ads,.articleAd,.articleAds,.articleAdsL,.articleEmbeddedAdB=
ox,.article_ad,.article_adbox,.article_mpu_box,.articleads,.aseadn,.aux-ad=
-widget-2,.b-astro-sponsored-links_horizontal,.b-astro-sponsored-links_ver=
tical,.banner-ad,.banner-ads,.banner-adverts,.banner300x100,.banner300x250=
,.banner468,.bannerAd,.bannerAdWrapper300x250,.bannerAdWrapper730x86,.bann=
erRightAd,.banner_300x250,.banner_728x90,.banner_ad,.banner_ad_footer,.ban=
ner_ad_leaderboard,.bannerad,.barkerAd,.base-ad-mpu,.base_ad,.bgnavad,.big=
-ads,.bigAd,.big_ad,.big_ads,.bigad,.bigad2,.bigbox_ad,.bigboxad,.billboar=
d_ad,.blk_advert,.block-ad,.block-ad300,.block-admanager,.block-ads-bottom=
,.block-ads-top,.block-adsense,.block-openadstream,.block-openx,.block-thi=
rdage-ads,.block_ad,.block_ad_sb_text,.block_ad_sponsored_links,.block_ad_=
sponsored_links-wrapper,.blocked-ads,.blog-ad-leader-inner,.blog-ads-conta=
iner,.blogAd,.blogAdvertisement,.blogBigAd,.blog_ad,.blogads,.blox3feature=
dAd,.body_ad,.body_sponsoredresults_bottom,.body_sponsoredresults_middle,.=
body_sponsoredresults_top,.bookseller-header-advt,.bottomAd,.bottomAds,.bo=
ttom_ad,.bottom_ad_block,.bottom_sponsor,.bottomad,.bottomadvert,.bottomri=
ghtrailAd,.bottomvidad,.box-ad,.box-ads,.box-adsense,.boxAd,.box_ad,.box_a=
ds,.box_advertising,.box_advertisment_62_border,.box_content_ad,.box_conte=
nt_ads,.boxad,.boxyads,.bps-ad-wrapper,.bps-advertisement,.bps-advertiseme=
nt-inline-ads,.br-ad,.bsa_ads,.btm_ad,.bullet-sponsored-links,.bullet-spon=
sored-links-gray,.burstContentAdIndex,.buttonAd,.buttonAds,.buttonadbox,.b=
x_ad,.bx_ad_right,.cA-adStrap,.cColumn-TextAdsBox,.care2_adspace,.catalog_=
ads,.cb-ad-container,.cb_footer_sponsor,.cb_navigation_ad,.cbstv_ad_label,=
.cbzadvert,.cdAdTitle,.cdmainlineSearchAdParent,.cdsidebarSearchAdParent,.=
centerAd,.center_ad,.centerad,.centered-ad,.cinemabotad,.clearerad,.cm_ads=
,.cms-Advert,.cnbc_badge_banner_ad_area,.cnn160AdFooter,.cnnAd,.cnnMosaic1=
60Container,.cnnSearchSponsorBox,.cnnStoreAd,.cnnStoryElementBoxAd,.cnnWCA=
dBox,.cnnWireAdLtgBox,.cnn_728adbin,.cnn_adcntr300x100,.cnn_adcntr728x90,.=
cnn_adspc336cntr,.cnn_adtitle,.column2-ad,.com-ad-server,.comment-advertis=
ement,.common_advertisement_title,.communityAd,.conTSponsored,.conductor_a=
d,.confirm_ad_left,.confirm_ad_right,.confirm_leader_ad,.consoleAd,.contai=
ner-adwords,.containerSqAd,.container_serendipity_plugin_google_adsense,.c=
ontent-ad,.contentAd,.contentAdFoot,.contentAdsWrapper,.content_ad,.conten=
t_ad_728,.content_adsq,.contentad,.contentad300x250,.contentad_right_col,.=
contentadcontainer,.contentadleft,.contenttextad,.contest_ad,.cp_ad,.cpmst=
arHeadline,.cpmstarText,.create_ad,.cs-mpu,.cscTextAd,.cse_ads,.cspAd,.ct_=
ad,.cube-ad,.cubeAd,.cube_ads,.currency_ad,.custom_ads,.darla_ad,.dartAdIm=
age,.dart_ad,.dart_tag,.dartadvert,.dartiframe,.dc-ad,.dcAdvertHeader,.dec=
kAd,.deckads,.detail-ads,.detailMpu,.detail_top_advert,.divAd,.divad1,.div=
ad2,.divad3,.divads,.divider_ad,.dmco_advert_iabrighttitle,.download_ad,.d=
ownloadad,.dynamic-ads,.dynamic_ad,.e-ad,.ec-ads,.em-ad,.embed-ad,.entry_s=
idebar_ads,.entryad,.ez-clientAd,.f_Ads,.featuredAds,.featuredadvertising,=
.flagads,.flash-advertisement,.flash_ad,.flash_advert,.flashad,.flexiad,.f=
lipbook_v2_sponsor_ad,.floatad,.footad,.footer-ad,.footerAd,.footerAdModul=
e,.footerAdslot,.footerTextAd,.footer_ad,.footer_ads,.footer_block_ad,.foo=
ter_bottomad,.footer_line_ad,.footer_text_ad,.footerad,.forumtopad,.frn_ad=
box,.frn_cont_adbox,.ft-ad,.ftdContentAd,.full_ad_box,.fullbannerad,.g3rtn=
-ad-site,.gAdvertising,.g_ggl_ad,.ga-textads-bottom,.ga-textads-top,.gaTea=
serAdsBox,.gads,.gads_cb,.gads_container,.gamesPage_ad_content,.gglAds,.go=
ogad,.googads,.google-ad,.google-ad-container,.google-ads,.google-ads-boxo=
ut,.google-ads-slim,.google-right-ad,.google-sponsored-ads,.google-sponsor=
ed-link,.google468_60,.googleAd,.googleAd-content,.googleAd-list,.googleAd=
Box,.googleAdSense,.googleAdSenseModule,.googleAd_body,.googleAds,.googleA=
ds_article_page_above_comments,.googleAdsense,.googleContentAds,.googlePro=
fileAd,.googleSearchAd_content,.googleSearchAd_sidebar,.google_ad,.google_=
add_container,.google_ads,.google_ads_bom_title,.google_ads_content,.googl=
ead,.googleaddiv,.googleaddiv2,.googleads,.googleads_300x250,.googleads_ti=
tle,.googley_ads,.gpAdBox,.gpAds,.gradientAd,.group_ad,.gsfAd,.gt_ad,.gt_a=
d_300x250,.gt_ad_728x90,.gt_adlabel,.gutter-ad-left,.gutter-ad-right,.h-ad=
-728x90-bottom,.h_Ads,.h_ad,.half-ad,.half_ad_box,.hd_advert,.hdr-ads,.hea=
der-ad,.header-advert,.headerAd,.headerAds,.headerAdvert,.header_ad,.heade=
r_ad_center,.header_advertisment,.headerad,.hi5-ad,.highlightsAd,.hm_adver=
tisment,.home-ad-links,.homeAd,.homeAdBoxA,.homeAdBoxBetweenBlocks,.homeAd=
BoxInBignews,.homeAdSection,.homeMediumAdGroup,.home_ad_bottom,.home_adver=
tisement,.home_mrec_ad,.homead,.homepage-ad,.homepage300ad,.homepageFlexAd=
Outer,.homepageMPU,.homepage_middle_right_ad,.hor_ad,.horiz_adspace,.horiz=
ontalAd,.horizontal_ad,.horizontal_ads,.horizontaltextadbox,.horizsponsore=
dlinks,.hortad,.houseAdsStyle,.housead,.hp2-adtag,.hp_ad_cont,.hp_ad_text,=
.hp_t_ad,.hp_w_ad,.ic-ads,.ico-adv,.idMultiAd,.image-advertisement,.imagea=
ds,.imgad,.in-page-ad,.in-story-text-ad,.indie-sidead,.indy_googleads,.inl=
ine-ad,.inline-mpu-left,.inlineSideAd,.inline_ad,.inline_ad_title,.inlinea=
d,.inlineadsense,.inlineadtitle,.inlist-ad,.inlistAd,.inner-advt-banner-3,=
.innerAds,.innerad,.inpostad,.insert_advertisement,.insertad,.is24-adplace=
,.islandAd,.islandAdvert,.islandad,.jimdoAdDisclaimer,.jp-advertisment-pro=
motional,.js-advert,.kw_advert,.kw_advert_pair,.l_ad_sub,.l_banner.ads_sho=
w_if,.labelads,.largeRectangleAd,.lastRowAd,.lcontentbox_ad,.leaderAdTop,.=
leaderAdvert,.leader_ad,.leaderboardAd,.leaderboardad,.leaderboardadtop,.l=
eft-ad,.leftAd,.leftAdColumn,.leftAds,.left_adlink,.left_ads,.leftad,.left=
adtag,.leftbar_ad_160_600,.leftbarads,.leftnavad,.lgRecAd,.lg_ad,.ligatus,=
.linead,.link_adslider,.link_advertise,.live-search-list-ad-container,.lja=
d,.log_ads,.longAd,.lowerAds,.m-ad-tvguide-box,.m4-adsbygoogle,.m_banner_a=
ds,.macAd,.macad,.main-ad,.main-tabs-ad-block,.main_ad,.main_adbox,.main_i=
ntro_ad,.map_media_banner_ad,.marginadsthin,.marketing-ad,.masthead_topad,=
.mdl-ad,.media-advert,.mediaAd,.mediaAdContainer,.medium-rectangle-ad,.med=
iumRectangleAdvert,.menuItemBannerAd,.messageBoardAd,.micro_ad,.mid_ad,.mi=
dad,.middleAds,.middleads,.min_navi_ad,.miniad,.mobile-sponsoring,.mod-ad-=
lrec,.mod-ad-n,.mod-adopenx,.mod_admodule,.module-ad,.module-ad-small,.mod=
ule-ads,.moduleAdvertContent,.module_ad,.module_box_ad,.modulegad,.modulet=
able-advert,.moduletable-googleads,.moduletablesquaread,.mpu,.mpu-ad,.mpu-=
advert,.mpu-footer,.mpu-fp,.mpu-title,.mpu-top-left,.mpu-top-left-banner,.=
mpu-top-right,.mpuAd,.mpuAdSlot,.mpuAdvert,.mpuArea,.mpuBox,.mpuContainer,=
.mpuHolder,.mpuTextAd,.mpu_ad,.mpu_advert,.mpu_gold,.mpu_holder,.mpu_plati=
num,.mpu_text_ad,.mpuad,.mpuholderportalpage,.mrec_advert,.ms-ads-link,.ms=
fg-shopping-mpu,.mwaads,.nSponsoredLcContent,.nSponsoredLcTopic,.nadvt300,=
.narrow_ad_unit,.narrow_ads,.navAdsBanner,.navi_ad300,.naviad,.nba300Ad,.n=
baT3Ad160,.nbaTVPodAd,.nbaTwo130Ads,.nbc_ad_carousel_wrp,.newTopAdContaine=
r,.newad,.newsviewAdBoxInNews,.nf-adbox,.nn-mpu,.noAdForLead,.normalAds,.n=
rAds,.nsAdRow,.oas-bottom-ads,.offer_sponsoredlinks,.oio-banner-zone,.oio-=
link-sidebar,.oio-zone-position,.on_single_ad_box,.onethirdadholder,.opena=
ds,.openadstext_after,.openx,.openx-ad,.osan-ads,.other_adv2,.ovAdPromo,.o=
vAdSky,.ovAdartikel,.ov_spns,.pageGoogleAd,.pageGoogleAdFlat,.pageLeaderAd=
,.page_content_right_ad,.pagead,.pagenavindexcontentad,.partnersTextLinks,=
.pencil_ad,.player_ad_box,.player_page_ad_box,.pnp_ad,.pod-ad-300,.podRela=
tedAdLinksWidget,.podSponsoredLink,.portalCenterContentAdBottom,.portalCen=
terContentAdMiddle,.portalCenterContentAdTop,.portalcontentad,.post-ad,.po=
st_ad,.post_sponsor_unit,.postbit_adbit_register,.postbit_adcode,.postgrou=
p-ads,.postgroup-ads-middle,.prebodyads,.premium_ad_container,.promoAd,.pr=
omoAds,.promo_ad,.publication-ad,.publicidad,.puff-advertorials,.qa_ad_lef=
t,.qm-ad-content,.qm-ad-content-news,.quigo-ad,.qzvAdDiv,.r_ad_box,.r_ads,=
.rad_container,.rect_ad_module,.rectad,.rectangleAd,.rectanglead,.redads_c=
ont,.regularad,.relatedAds,.related_post_google_ad,.remads,.result_ad,.res=
ults_sponsor,.results_sponsor_right,.reviewMidAdvertAlign,.rght300x250,.rh=
ads,.rhs-ad,.rhs-ads-panel,.right-ad,.right-ad-holder,.right-ad2,.right-ad=
s,.right-ads2,.rightAd,.rightRailAd,.right_ad,.right_ad_text,.right_ad_top=
,.right_ads,.right_ads_column,.right_col_ad,.right_hand_advert_column,.rig=
htad,.rightad_1,.rightad_2,.rightads,.rightadunit,.rightcol_boxad,.rightco=
ladvert,.rightcoltowerad,.rnav_ad,.rngtAd,.rt_ad1_300x90,.rt_ad_300x250,.r=
t_ad_call,.savvyad_unit,.sb-ad-sq-bg,.sbAd,.sbAdUnitContainer,.sb_adsN,.sb=
_adsNv2,.sb_adsW,.sb_adsWv2,.scanAd,.scc_advert,.sci-ad-main,.sci-ad-sub,.=
search-ad,.search-results-ad,.search-sponsor,.search-sponsored,.searchAd,.=
searchSponsoredResultsBox,.searchSponsoredResultsList,.search_column_resul=
ts_sponsored,.search_results_sponsored_top,.section-ad2,.section-sponsor,.=
section_mpu_wrapper,.section_mpu_wrapper_wrapper,.selfServeAds,.serp_spons=
ored,.servsponserLinks,.shoppingGoogleAdSense,.sidbaread,.side-ad,.side-ad=
s,.sideAd,.sideBoxAd,.side_ad,.side_ad2,.side_ad_1,.side_ad_2,.side_ad_3,.=
sidead,.sideads,.sideadsbox,.sideadvert,.sidebar-ad,.sidebar-ads,.sidebar-=
text-ad,.sidebarAd,.sidebarAdUnit,.sidebarAdvert,.sidebar_ad,.sidebar_ad_3=
00_250,.sidebar_ads,.sidebar_ads_336,.sidebar_adsense,.sidebar_box_ad,.sid=
ebarad,.sidebarad_bottom,.sidebaradbox,.sidebarboxad,.sideheadnarrowad,.si=
deheadsponsorsad,.singleAd,.singleAdsContainer,.singlead,.sitesponsor,.ski=
nAd,.skin_ad_638,.sky-ad,.skyAd,.skyAdd,.sky_ad,.sky_scraper_ad,.skyad,.sk=
yscraper-ad,.skyscraper_ad,.skyscraper_bannerAdHome,.slideshow-ad,.slpBigS=
limAdUnit,.slpSquareAdUnit,.sm_ad,.smallSkyAd1,.smallSkyAd2,.small_ad,.sma=
ll_ads,.smallad-left,.smallads,.smallsponsorad,.smart_ads_bom_title,.speci=
alAd175x90,.speedyads,.sphereAdContainer,.spl-ads,.spl_ad,.spl_ad2,.spl_ad=
_plus,.splitAd,.sponlinkbox,.spons-link,.spons_links,.sponslink,.sponsor-a=
d,.sponsor-bottom,.sponsor-link,.sponsor-links,.sponsor-right,.sponsor-ser=
vices,.sponsor-top,.sponsorArea,.sponsorBox,.sponsorPost,.sponsorPostWrap,=
.sponsorStrip,.sponsorTop,.sponsor_ad_area,.sponsor_footer,.sponsor_horizo=
ntal,.sponsor_line,.sponsor_links,.sponsor_logo,.sponsor_top,.sponsor_unit=
s,.sponsoradtitle,.sponsorbox,.sponsored,.sponsored-chunk,.sponsored-edito=
rial,.sponsored-features,.sponsored-links,.sponsored-links-alt-b,.sponsore=
d-links-holder,.sponsored-links-right,.sponsored-post,.sponsored-post_ad,.=
sponsored-results,.sponsored-right-border,.sponsored-text,.sponsoredInner,=
.sponsoredLinks,.sponsoredLinksHeader,.sponsoredProduct,.sponsoredSideInne=
r,.sponsored_ads,.sponsored_box,.sponsored_box_search,.sponsored_by,.spons=
ored_links,.sponsored_links_title_container,.sponsored_links_title_contain=
er_top,.sponsored_links_top,.sponsored_results,.sponsored_well,.sponsoredi=
bbox,.sponsoredlink,.sponsoredlinks,.sponsoredlinkscontainer,.sponsoredres=
ults,.sponsoredtextlink_container,.sponsoredtextlink_container_ovt,.sponso=
rlink,.sponsorlink2,.sponsors,.sponsors-box,.sponsorshipbox,.spotlightAd,.=
squareAd,.square_ad,.squared_ad,.ss-ad-mpu,.staticAd,.stocks-ad-tag,.store=
-ads,.story_AD,.subad,.subcontent-ad,.super-ad,.supercommentad_left,.super=
commentad_right,.supp-ads,.supportAdItem,.surveyad,.t10ad,.tab_ad,.tab_ad_=
area,.tablebordersponsor,.tadsanzeige,.tadsbanner,.tadselement,.tallad,.tb=
lTopAds,.tbl_ad,.tbox_ad,.teaser-sponsor,.teaserAdContainer,.teaser_adtile=
s,.text-ad-links,.text-g-advertisement,.text-g-group-short-rec-ad,.text-g-=
net-grp-google-ads-article-page,.textAd,.textAdBox,.textAds,.text_ad,.text=
_ads,.textad,.textadContainer,.textad_headline,.textadbox,.textads,.textad=
sfoot,.textlink-ads,.tf_page_ad_search,.thisIsAd,.thisIsAnAd,.ticket-ad,.t=
ileAds,.tips_advertisement,.title-ad,.title_adbig,.tncms-region-ads,.toola=
d,.toolbar-ad,.top-ad,.top-ad-space,.top-ads,.top-menu-ads,.top-sponsors,.=
topAd,.topAdWrap,.topAds,.topAdvertisement,.topBannerAd,.topLeaderboardAd,=
.top_Ad,.top_ad,.top_ad_728,.top_ad_728_90,.top_ad_disclaimer,.top_ad_div,=
.top_ad_wrapper,.top_ads,.top_advert,.top_advertising_lb,.top_container_ad=
,.top_sponsor,.topad,.topad-bar,.topadbox,.topads,.topadspot,.topadvertise=
mentsegment,.topcontentadvertisement,.topic_inad,.topstoriesad,.toptenAdBo=
xA,.towerAd,.towerAdLeft,.towerAds,.tower_ad,.tower_ad_disclaimer,.towerad=
,.ts-ad_unit_bigbox,.ts-banner_ad,.ttlAdsensel,.tto-sponsored-element,.two=
ColumnAd,.twoadcoll,.twoadcolr,.tx_smartadserver_pi1,.txt-ads,.txtAds,.txt=
_ads,.txtadvertise,.type_adscontainer,.type_miniad,.type_promoads,.ukAds,.=
undertimyads,.universalboxADVBOX01,.universalboxADVBOX03,.universalboxADVB=
OX04a,.usenext,.vertad,.videoAd,.videoBoxAd,.video_ad,.view-promo-mpu-righ=
t,.view_rig_ad,.virgin-mpu,.wa_adsbottom,.wide-ad,.wide-skyscraper-ad,.wid=
eAdTable,.wide_ad,.wide_ad_unit_top,.wide_ads,.wide_google_ads,.widget-ad,=
.widget-ad300x250,.widget-entry-ads-160,.widget_ad,.widget_ad_rotator,.wid=
get_island_ad,.widget_sdac_footer_ads_widget,.wikia-ad,.wikia_ad_placehold=
er,.withAds,.wnMultiAd,.wp125ad,.wp125ad_2,.wpn_ad_content,.wrap-ads,.wsSp=
onsoredLinksRight,.wsTopSposoredLinks,.x03-adunit,.x04-adunit,.xads-blk2,.=
xads-ojedn,.y-ads,.y-ads-wide,.y7-advertisement,.yahoo-sponsored,.yahoo-sp=
onsored-links,.yahooAds,.yahoo_ads,.yan-sponsored,.ygrp-ad,.yrail_ad_wrap,=
.yrail_ads,.ysmsponsor,.ysponsor,.yw-ad,[id^=3D"MarketGid"],a[href^=3D"htt=
p://ad.doubleclick.net/"],a[href^=3D"http://adserving.liveuniversenetwork.=
com/"],a[href^=3D"http://galleries.pinballpublishernetwork.com/"],a[href^=3D=
"http://galleries.securewebsiteaccess.com/"],a[href^=3D"http://install.sec=
urewebsiteaccess.com/"],a[href^=3D"http://latestdownloads.net/download.php=
?"],a[href^=3D"http://secure.signup-page.com/"],a[href^=3D"http://secure.s=
ignup-way.com/"],a[href^=3D"http://www.FriendlyDuck.com/AF_"],a[href^=3D"h=
ttp://www.adbrite.com/mb/commerce/purchase_form.php?"],a[href^=3D"http://w=
ww.friendlyduck.com/AF_"],a[href^=3D"http://www.google.com/aclk?"],a[href^=
=3D"http://www.liutilities.com/aff"],a[href^=3D"http://www.liutilities.com=
/products/campaigns/adv/"],a[href^=3D"http://www.my-dirty-hobby.com/?sub=3D=
"],a[href^=3D"http://www.ringtonematcher.com/"],div#mclip_container:first-=
child:last-child,div#tads.c,table.ra[align=3D"left"][width=3D"30%"],table.=
ra[align=3D"right"][width=3D"30%"] { visibility:hidden !important;    =
display:none !important; }</style></head><body id=3D"gsr" topmargin=3D"3" =
marginheight=3D"3" style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><base =
href=3D"http://www.google.com/search?client=3Dsafari&amp;rls=3Den&amp;q=3D=
%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;ie=3DUTF-8&amp;oe=3DUTF-8"><div =
style=3D"font-family: Helvetica; font-size: 12px; color: black; =
text-align: left; ">It would be interesting to understand what the issue =
is here. I suspect it has nothing to do with the actual Windows (or =
Apple, Linux, etc) implementation, but is more related to issues as =
discussed in <a =
href=3D"http://tools.ietf.org/html/draft-wing-http-new-tech">http://tools.=
ietf.org/html/draft-wing-http-new-tech</a>. Would it make sense for =
v6ops to make a recommendation to address the concerns?</div><div =
style=3D"font-family: Helvetica; font-size: 12px; color: black; =
text-align: left; "><br></div><div style=3D"font-family: Helvetica; =
font-size: 12px; color: black; text-align: left; "><br></div><div =
style=3D"font-family: Helvetica; font-size: 12px; color: black; =
text-align: left; =
"><br></div><script>if(google.j.b)document.body.style.display=3D'none';</s=
cript><iframe name=3D"wgjf" style=3D"display:none" src=3D"/blank.html" =
onload=3D"google.j.l()" onerror=3D"google.j.e()"></iframe><textarea =
id=3D"csi" style=3D"display:none"></textarea><textarea id=3D"wwcache" =
style=3D"display:none"></textarea><textarea id=3D"wgjc" =
style=3D"display:none"></textarea><textarea id=3D"hcache" =
style=3D"display:none"></textarea><a =
href=3D"/setprefs?sig=3D0_4WDh_gC3bEfcP6lDrLo2V9SpC94=3D&amp;suggon=3D2&am=
p;prev=3Dhttp://www.google.com/search%3Fclient%3Dsafari%26rls%3Den%26q%3D%=
25E2%2580%259Cipv6%2Bon%2Bwindows%2B7%25E2%2580%259D%26ie%3DUTF-8%26oe%3DU=
TF-8" style=3D"position:absolute;left:-1000em">Screen reader users, =
click here to turn off Google Instant.</a><div class=3D"jsrp" =
id=3D"searchform" style=3D"top:41px"><form action=3D"/search" id=3D"tsf" =
method=3D"GET" name=3D"f" onsubmit=3D"return q.value!=3D''" =
role=3D"search" style=3D"display:block;margin:0 =
auto;background:none"><input name=3D"sclient" type=3D"hidden" =
value=3D"psy"><span id=3D"tophf"><input type=3D"hidden" name=3D"hl" =
value=3D"en"><input type=3D"hidden" name=3D"client" =
value=3D"safari"><input type=3D"hidden" name=3D"rls" value=3D"en"><input =
name=3D"source" type=3D"hidden" value=3D"hp"></span><div class=3D"tsf-p" =
style=3D"position:relative"><div class=3D"nojsv" id=3D"logocont" =
style=3D"left: 0px; margin-top: -8px; padding-top: 0px; padding-right: =
12px; padding-bottom: 0px; padding-left: 12px; position: absolute; =
visibility: visible; "><h1><a id=3D"logo" =
href=3D"http://www.google.com/webhp?hl=3Den" title=3D"Go to Google =
Home">Google<img width=3D"178" height=3D"238" =
src=3D"/images/nav_logo16.png" alt=3D""></a></h1></div><div =
style=3D"padding-bottom:2px;padding-right:8px"><table border=3D"0" =
cellpadding=3D"0" cellspacing=3D"0" width=3D"100%"><tbody><tr><td =
width=3D"100%"><table border=3D"0" cellpadding=3D"0" cellspacing=3D"0" =
id=3D"sftab" style=3D"border-bottom:1px solid #e7e7e7;padding:8px 0 =
0;position:relative" width=3D"100%"><tbody><tr><td width=3D"100%"><div =
style=3D"position:relative"><table border=3D"0" cellpadding=3D"0" =
cellspacing=3D"0" width=3D"100%"><tbody><tr><td id=3D"lst-xbtn" =
class=3D"lst-td lst-td-xbtn" style=3D"border-top:1px solid #ccc" =
width=3D"100%"><div style=3D"position:relative;zoom:1"><div =
style=3D"position:relative;background:transparent"><input class=3D"lst" =
disabled=3D"" id=3D"grey" maxlength=3D"2048" type=3D"text" =
autocomplete=3D"off"><div class=3D"lst" id=3D"misspell"></div></div><div =
class=3D"lst" style=3D"position: absolute; top: -900px; left: -9000px; =
max-width: 3000px; overflow-x: hidden; overflow-y: hidden; width: auto; =
">=E2=80=9Cipv6&nbsp;on&nbsp;windows&nbsp;7=E2=80=9D</div><input =
class=3D"lst" type=3D"text" name=3D"q" maxlength=3D"2048" value=3D"=E2=80=9C=
ipv6 on windows 7=E2=80=9D" title=3D"Search" spellcheck=3D"false" =
autocomplete=3D"off"><span id=3D"tsf-oq" style=3D"display:none">=E2=80=9Ci=
pv6 on windows 7=E2=80=9D</span></div> </td><td class=3D"lst-td =
lst-td-xbtn"><a href=3D"#" id=3D"xbtn" style=3D"text-decoration: none; =
padding-top: 0px; padding-right: 5px; padding-bottom: 0px; padding-left: =
5px; display: inline; " tabindex=3D"-1" title=3D"Clear =
search">=C3=97</a></td></tr></tbody></table></div></td><td><div =
class=3D"jsb" style=3D"background-image: initial; background-attachment: =
initial; background-origin: initial; background-clip: initial; =
background-color: rgb(153, 153, 153); height: 32px; width: 1px; display: =
none; background-position: initial initial; background-repeat: initial =
initial; "></div><div class=3D"nojsb" style=3D"display: block; "><div =
class=3D"ds"><div class=3D"lsbb"><input type=3D"submit" name=3D"btnG" =
class=3D"lsb" =
value=3D"Search"></div></div></div></td></tr></tbody></table></td><td><div=
 class=3D"jsb" style=3D"font-size: 11px; position: absolute; =
padding-top: 5px; padding-left: 12px; display: none; "><a =
href=3D"/advanced_search" class=3D"fl" style=3D"color:#4373db">Advanced =
search</a><br><a href=3D"/language_tools?hl=3Den" class=3D"fl" =
style=3D"color:#4373db">Language tools</a></div><div class=3D"nojsv" =
id=3D"sfopt" style=3D"position: relative; height: 30px; visibility: =
visible; "><div class=3D"lsd"><div id=3D"po-bar"><div id=3D"po-status"><a =
href=3D"/preferences" class=3D"flt" id=3D"po-tg" onclick=3D"return =
google.x(this,function(){this.blur();google.psy.t(event)})" =
style=3D"text-decoration:none"><u id=3D"po-on-message" =
class=3D"po-l">Instant is on</u><u id=3D"po-off-message" class=3D"po-l" =
style=3D"display:none">Instant is off</u><u id=3D"po-off-sc-message" =
class=3D"po-l" style=3D"display:none">Instant is off (slow =
connection)</u> <small>=E2=96=BC</small></a><div id=3D"po-box" =
style=3D"display:none"><div id=3D"po-sc-lm" class=3D"gb2 po-lm" =
style=3D"display:none"><div style=3D"padding:2px =
5px;white-space:normal">Google Instant is off due to connection speed. =
<a =
href=3D"http://www.google.com/support/websearch/bin/answer.py?hl=3Den&amp;=
answer=3D186645" class=3D"fl">Learn more</a>.</div><div =
class=3D"gbd"></div></div><a =
href=3D"/setprefs?sig=3D0_4WDh_gC3bEfcP6lDrLo2V9SpC94=3D&amp;suggon=3D1&am=
p;prev=3Dhttp://www.google.com/search%3Fclient%3Dsafari%26rls%3Den%26q%3D%=
25E2%2580%259Cipv6%2Bon%2Bwindows%2B7%25E2%2580%259D%26ie%3DUTF-8%26oe%3DU=
TF-8" class=3D"po-link po-selected" id=3D"po-on"><span class=3D"mark">=E2=80=
=BA </span>On (type to search)</a><a =
href=3D"/setprefs?sig=3D0_4WDh_gC3bEfcP6lDrLo2V9SpC94=3D&amp;suggon=3D2&am=
p;prev=3Dhttp://www.google.com/search%3Fclient%3Dsafari%26rls%3Den%26q%3D%=
25E2%2580%259Cipv6%2Bon%2Bwindows%2B7%25E2%2580%259D%26ie%3DUTF-8%26oe%3DU=
TF-8" class=3D"po-link po-unselected" id=3D"po-off"><span =
class=3D"mark">=E2=80=BA </span>Off (press Enter to search)</a><div =
class=3D"gb2"><div class=3D"gbd"></div></div><a =
href=3D"/instant/#utm_campaign=3Dlaunch&amp;utm_medium=3Det&amp;utm_source=
=3Dtoggle" class=3D"po-link po-unselected" style=3D"padding:0 11px">More =
about Google =
Instant</a></div></div></div><br></div></div></td></tr><tr><td><div =
id=3D"pocs" style=3D"display: none; margin-top: 0px; "><div =
id=3D"pocs0">Google Instant is unavailable. Press enter to search. <a =
href=3D"/support/websearch/bin/answer.py?answer=3D186645&amp;hl=3Den&amp;f=
orm=3Dbb">Learn more</a></div><div id=3D"pocs1">Google Instant is off =
due to connection speed. Press Enter to search.</div><div =
id=3D"pocs2">Press Enter to search.</div></div><div id=3D"pets" =
style=3D"color:#767676;font-size:9pt;display:none;margin:5px 0 0 =
8px">Press Enter to search.</div></td></tr></tbody></table></div><div =
class=3D"jsb" style=3D"padding-top: 2px; display: none; "><center><span =
class=3D"ds"><span class=3D"lsbb"><input name=3D"btnG" type=3D"submit" =
value=3D"Google Search" class=3D"lsb" =
onclick=3D"this.checked=3D1"></span></span><span class=3D"ds"><span =
class=3D"lsbb"><input name=3D"btnI" type=3D"submit" value=3D"I'm Feeling =
Lucky" class=3D"lsb" onclick=3D"if(this.form.q.value)this.checked=3D1;else=
 window.location=3D'/logos/'"></span></span></center></div></div><input =
type=3D"hidden" name=3D"aq" value=3D"f"><input type=3D"hidden" =
name=3D"aqi" value=3D""><input type=3D"hidden" name=3D"aql" =
value=3D""><input type=3D"hidden" name=3D"oq" value=3D"=E2=80=9Cipv6 on =
windows 7=E2=80=9D"><input type=3D"hidden" name=3D"gs_rfai" =
value=3D""><input type=3D"hidden" name=3D"pbx" =
value=3D"1"></form></div><div id=3D"gac_scont"><div class=3D"gac_od" =
style=3D"visibility: hidden; left: 205px; top: 79px; min-width: 569px; =
"><div class=3D"gac_id"><table cellpadding=3D"0" cellspacing=3D"0" =
class=3D"gac_m"></table></div></div></div><div id=3D"main"><div =
id=3D"ghead"><div id=3D"gog"><div id=3D"gbar"><nobr><b =
class=3D"gb1">Web</b> <a =
href=3D"http://www.google.com/images?client=3Dsafari&amp;rls=3Den&amp;q=3D=
%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;oe=3DUTF-8&amp;um=3D1&amp;ie=3DUTF=
-8&amp;source=3Dog&amp;sa=3DN&amp;hl=3Den&amp;tab=3Dwi" =
onclick=3D"gbar.qs(this)" class=3D"gb1">Images</a> <a =
href=3D"http://www.google.com/search?client=3Dsafari&amp;rls=3Den&amp;q=3D=
%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;oe=3DUTF-8&amp;um=3D1&amp;ie=3DUTF=
-8&amp;tbo=3Du&amp;tbs=3Dvid:1&amp;source=3Dog&amp;sa=3DN&amp;hl=3Den&amp;=
tab=3Dwv" onclick=3D"gbar.qs(this)" class=3D"gb1">Videos</a> <a =
href=3D"http://maps.google.com/maps?client=3Dsafari&amp;rls=3Den&amp;q=3D%=
E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;oe=3DUTF-8&amp;um=3D1&amp;ie=3DUTF-=
8&amp;sa=3DN&amp;hl=3Den&amp;tab=3Dwl" onclick=3D"gbar.qs(this)" =
class=3D"gb1">Maps</a> <a =
href=3D"http://www.google.com/search?client=3Dsafari&amp;rls=3Den&amp;q=3D=
%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;oe=3DUTF-8&amp;um=3D1&amp;ie=3DUTF=
-8&amp;tbo=3Du&amp;tbs=3Dnws:1&amp;source=3Dog&amp;sa=3DN&amp;hl=3Den&amp;=
tab=3Dwn" onclick=3D"gbar.qs(this)" class=3D"gb1">News</a> <a =
href=3D"http://www.google.com/products?client=3Dsafari&amp;rls=3Den&amp;q=3D=
%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;oe=3DUTF-8&amp;um=3D1&amp;ie=3DUTF=
-8&amp;sa=3DN&amp;hl=3Den&amp;tab=3Dwf" onclick=3D"gbar.qs(this)" =
class=3D"gb1">Shopping</a> <a =
href=3D"http://mail.google.com/mail/?hl=3Den&amp;tab=3Dwm" =
class=3D"gb1">Gmail</a> <a href=3D"http://www.google.com/intl/en/options/"=
 onclick=3D"this.blur();gbar.tg(event);return !1" aria-haspopup=3D"true" =
class=3D"gb3"><u>more</u> <small>=E2=96=BC</small></a><div class=3D"gbm" =
id=3D"gbi"><a =
href=3D"http://www.google.com/search?client=3Dsafari&amp;rls=3Den&amp;q=3D=
%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;oe=3DUTF-8&amp;um=3D1&amp;ie=3DUTF=
-8&amp;tbo=3Du&amp;tbs=3Dbks:1&amp;source=3Dog&amp;sa=3DN&amp;hl=3Den&amp;=
tab=3Dwp" onclick=3D"gbar.qs(this)" class=3D"gb2">Books</a> <a =
href=3D"http://www.google.com/finance?client=3Dsafari&amp;rls=3Den&amp;q=3D=
%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;oe=3DUTF-8&amp;um=3D1&amp;ie=3DUTF=
-8&amp;sa=3DN&amp;hl=3Den&amp;tab=3Dwe" onclick=3D"gbar.qs(this)" =
class=3D"gb2">Finance</a> <a =
href=3D"http://translate.google.com/translate_t?client=3Dsafari&amp;rls=3D=
en&amp;q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;oe=3DUTF-8&amp;um=3D1&a=
mp;ie=3DUTF-8&amp;sa=3DN&amp;hl=3Den&amp;tab=3DwT" =
onclick=3D"gbar.qs(this)" class=3D"gb2">Translate</a> <a =
href=3D"http://scholar.google.com/scholar?client=3Dsafari&amp;rls=3Den&amp=
;q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;oe=3DUTF-8&amp;um=3D1&amp;ie=3D=
UTF-8&amp;sa=3DN&amp;hl=3Den&amp;tab=3Dws" onclick=3D"gbar.qs(this)" =
class=3D"gb2">Scholar</a> <a =
href=3D"http://www.google.com/search?client=3Dsafari&amp;rls=3Den&amp;q=3D=
%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;oe=3DUTF-8&amp;um=3D1&amp;ie=3DUTF=
-8&amp;tbo=3Du&amp;tbs=3Dblg:1&amp;source=3Dog&amp;sa=3DN&amp;hl=3Den&amp;=
tab=3Dwb" onclick=3D"gbar.qs(this)" class=3D"gb2">Blogs</a> <a =
href=3D"http://www.google.com/search?client=3Dsafari&amp;rls=3Den&amp;q=3D=
%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;oe=3DUTF-8&amp;um=3D1&amp;ie=3DUTF=
-8&amp;tbo=3Du&amp;tbs=3Dmbl:1&amp;source=3Dog&amp;sa=3DN&amp;hl=3Den&amp;=
tab=3DwY" onclick=3D"gbar.qs(this)" class=3D"gb2">Updates</a> <div =
class=3D"gb2"><div class=3D"gbd"></div></div><a =
href=3D"http://www.youtube.com/results?client=3Dsafari&amp;rls=3Den&amp;q=3D=
%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;oe=3DUTF-8&amp;um=3D1&amp;ie=3DUTF=
-8&amp;sa=3DN&amp;hl=3Den&amp;tab=3Dw1" onclick=3D"gbar.qs(this)" =
class=3D"gb2">YouTube</a> <a =
href=3D"http://www.google.com/calendar/render?hl=3Den&amp;tab=3Dwc" =
class=3D"gb2">Calendar</a> <a =
href=3D"http://picasaweb.google.com/lh/view?client=3Dsafari&amp;rls=3Den&a=
mp;q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;oe=3DUTF-8&amp;um=3D1&amp;i=
e=3DUTF-8&amp;sa=3DN&amp;hl=3Den&amp;tab=3Dwq" onclick=3D"gbar.qs(this)" =
class=3D"gb2">Photos</a> <a =
href=3D"http://docs.google.com/?hl=3Den&amp;tab=3Dwo&amp;authuser=3D0" =
class=3D"gb2">Documents</a> <a =
href=3D"http://www.google.com/reader/view/?hl=3Den&amp;tab=3Dwy" =
class=3D"gb2">Reader</a> <a =
href=3D"http://sites.google.com/?hl=3Den&amp;tab=3Dw3" =
class=3D"gb2">Sites</a> <a =
href=3D"http://groups.google.com/groups?client=3Dsafari&amp;rls=3Den&amp;q=
=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;oe=3DUTF-8&amp;um=3D1&amp;ie=3D=
UTF-8&amp;sa=3DN&amp;hl=3Den&amp;tab=3Dwg" onclick=3D"gbar.qs(this)" =
class=3D"gb2">Groups</a> <div class=3D"gb2"><div =
class=3D"gbd"></div></div><a =
href=3D"http://www.google.com/intl/en/options/" class=3D"gb2">even more =
=C2=BB</a> </div></nobr></div><div id=3D"guser" width=3D"100%"><nobr><span=
 id=3D"gbn" class=3D"gbi"></span><span id=3D"gbf" class=3D"gbf"></span><b =
class=3D"gb4"><a =
href=3D"mailto:FredBakerSBA@gmail.com">FredBakerSBA@gmail.com</a></b> | =
<span id=3D"gbe"></span><a href=3D"http://www.google.com/history/?hl=3Den"=
 class=3D"gb4">Web History</a> | <a href=3D"/preferences?hl=3Den" =
onclick=3D"this.blur();gbar.tg(event);return !1" aria-haspopup=3D"true" =
aria-owns=3D"gbg" class=3D"gb3"><u>Settings</u> <small>=E2=96=BC</small></=
a> | <a =
href=3D"http://www.google.com/accounts/Logout?continue=3Dhttp://www.google=
.com/search%3Fclient%3Dsafari%26rls%3Den%26q%3D%25E2%2580%259Cipv6%2Bon%2B=
windows%2B7%25E2%2580%259D%26ie%3DUTF-8%26oe%3DUTF-8" class=3D"gb4">Sign =
out</a><div class=3D"gbm" id=3D"gbg"><a href=3D"/preferences?hl=3Den" =
class=3D"gb2">Search settings</a> <a =
href=3D"https://www.google.com/accounts/ManageAccount?hl=3Den" =
class=3D"gb2">Google Account settings</a> </div></nobr></div><div =
class=3D"gbh" style=3D"left:0"></div><div class=3D"gbh" =
style=3D"right:0"></div></div></div> <div id=3D"cnt"><div =
id=3D"sfcnt"><div id=3D"sform" =
style=3D"height:43px"></div></div><style>#center_col,#footerbox{min-width:=
562px}</style><div id=3D"subform_ctrl" style=3D"margin-top: 0px; =
visibility: visible; "><div style=3D"float:right"><a =
href=3D"/advanced_search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3D=
en&amp;client=3Dsafari&amp;rls=3Den&amp;prmd=3Div" class=3D"gl nobr" =
style=3D"color:#4373db">Advanced search</a></div><div><div =
id=3D"resultStats">About 2,600 results<nobr>  (0.19 =
seconds)&nbsp;</nobr></div></div></div><div id=3D"nr_container" =
style=3D"position:relative;zoom:1" class=3D""><div id=3D"center_col" =
style=3D"visibility: visible; "><div id=3D"res" class=3D"med" =
role=3D"main"><!--a--><h2 class=3D"hd">Search Results</h2><div =
id=3D"ires"><ol><!--m--><li class=3D"g w0 knavi" style=3D"position: =
relative; "><h3 class=3D"r"><a =
href=3D"http://itexpertvoice.com/home/troubleshooting-ipv6-on-windows-7-an=
d-why-its-worth-the-bother/" class=3D"l noline" onmousedown=3D"return =
clk(this.href,'','','','1','tsf0CNsMe8XBI36xzab_0w','0CBYQFjAA')">Troubles=
hooting <em>IPv6 on  Windows 7</em> (and Why It's Worth the Bother =
<b>...</b></a></h3><button class=3D"ws" title=3D""></button><div =
class=3D"s">This post was mentioned on Twitter by howtoprojects: =
Troubleshooting <em>IPv6 on  Windows 7</em> (and Why It?s Worth the =
Bother) #howto <a =
href=3D"http://bit.ly/9zJ192">http://bit.ly/9zJ192</a>=E2=80=A6 =
<b>...</b><br><span class=3D"f"><cite><a =
href=3D"http://itexpertvoice.com/.../troubleshooting-">itexpertvoice.com/.=
../troubleshooting-</a><b>ipv6-on-windows-7</b>-and-why-its-worth =
-the-bother/</cite> - <span class=3D"gl"><a =
href=3D"http://webcache.googleusercontent.com/search?q=3Dcache:5iEZSy6D5JU=
J:itexpertvoice.com/home/troubleshooting-ipv6-on-windows-7-and-why-its-wor=
th-the-bother/+%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;cd=3D1&amp;hl=3Den&=
amp;ct=3Dclnk&amp;gl=3Dus&amp;client=3Dsafari" onmousedown=3D"return =
clk('http://webcache.googleusercontent.com/search?q=3Dcache:5iEZSy6D5JUJ:i=
texpertvoice.com/home/troubleshooting-ipv6-on-windows-7-and-why-its-worth-=
the-bother/+%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;cd=3D1&amp;hl=3Den&amp=
;ct=3Dclnk&amp;gl=3Dus&amp;client=3Dsafari','','','','1','1UZu09aoM8tF8b0Y=
KCDFBA','0CBgQIDAA')">Cached</a> - <a =
href=3D"/search?hl=3Den&amp;client=3Dsafari&amp;rls=3Den&amp;q=3Drelated:i=
texpertvoice.com/home/troubleshooting-ipv6-on-windows-7-and-why-its-worth-=
the-bother/+%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;tbo=3D1&amp;sa=3DX&amp=
;ei=3DyGisTIDWHoO4sAOD9sj4Aw&amp;ved=3D0CBkQHzAA">Similar</a></span></span=
></div><!--n--><!--m--><span id=3D"knavm" style=3D"padding-top: 0px; =
">=E2=96=BA</span></li><li class=3D"g w0 knavi" =
style=3D"margin-left:16px"><h3 class=3D"r hcw"><a =
href=3D"http://itexpertvoice.com/home/windows-7-and-ipv6-useful-at-last/" =
class=3D"l" onmousedown=3D"return =
clk(this.href,'','','','2','nnbuGC-B1iz13e4QJMq5lg','0CBsQFjAB')">Windows =
7 and IPv6: Useful at Last? =C2=AB IT Expert Voice</a></h3><button =
class=3D"ws" title=3D""></button><div class=3D"s hc">Dec 21, =
2009<b>...</b> Troubleshooting <em>IPv6 on  Windows 7</em> (and Why It's =
Worth the Bother) =C2=B7 IPv6, Google, and Your Business  =C2=B7 IPv6 =
and IPv4 Co-existence <b>...</b><br><span class=3D"f"><cite><a =
href=3D"http://itexpertvoice.com/home/windows-7-and-ipv6-useful-at-last/">=
itexpertvoice.com/home/windows-7-and-ipv6-useful-at-last/</a></cite> - =
<span class=3D"gl"><a =
href=3D"http://webcache.googleusercontent.com/search?q=3Dcache:43cTKRlEnPI=
J:itexpertvoice.com/home/windows-7-and-ipv6-useful-at-last/+%E2%80%9Cipv6+=
on+windows+7%E2%80%9D&amp;cd=3D2&amp;hl=3Den&amp;ct=3Dclnk&amp;gl=3Dus&amp=
;client=3Dsafari" onmousedown=3D"return =
clk('http://webcache.googleusercontent.com/search?q=3Dcache:43cTKRlEnPIJ:i=
texpertvoice.com/home/windows-7-and-ipv6-useful-at-last/+%E2%80%9Cipv6+on+=
windows+7%E2%80%9D&amp;cd=3D2&amp;hl=3Den&amp;ct=3Dclnk&amp;gl=3Dus&amp;cl=
ient=3Dsafari','','','','2','LxucDeonB6BRKfDN21KNZw','0CB0QIDAB')">Cached<=
/a> - <a =
href=3D"/search?hl=3Den&amp;client=3Dsafari&amp;rls=3Den&amp;q=3Drelated:i=
texpertvoice.com/home/windows-7-and-ipv6-useful-at-last/+%E2%80%9Cipv6+on+=
windows+7%E2%80%9D&amp;tbo=3D1&amp;sa=3DX&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&=
amp;ved=3D0CB4QHzAB">Similar</a></span></span></div><!--n--><!--m--></li><=
li class=3D"g w0 knavi"><h3 class=3D"r"><a =
href=3D"http://www.tothepc.com/archives/disable-ipv6-on-windows-7-vista-pc=
/" class=3D"l" onmousedown=3D"return =
clk(this.href,'','','','3','t5b4EZ70FJTr8iKLg3lT4Q','0CCAQFjAC')">How to =
disable <em>IPv6 on Windows 7</em> &amp; Vista PC</a></h3><button =
class=3D"ws" title=3D""></button><div class=3D"s">Feb 9, 2010 <b>...</b> =
Procedure to disable IPv6 feature on Windows 7 and Vista operating =
system. Use LAN  connection properties option or change registry value =
to <b>...</b><br><span class=3D"f"><cite><a =
href=3D"http://www.tothepc.com/.../disable-">www.tothepc.com/.../disable-<=
/a><b>ipv6-on-windows-7</b>-vista-pc/</cite> - <span class=3D"gl"><a =
href=3D"http://webcache.googleusercontent.com/search?q=3Dcache:mGEt0-ILcb8=
J:www.tothepc.com/archives/disable-ipv6-on-windows-7-vista-pc/+%E2%80%9Cip=
v6+on+windows+7%E2%80%9D&amp;cd=3D3&amp;hl=3Den&amp;ct=3Dclnk&amp;gl=3Dus&=
amp;client=3Dsafari" onmousedown=3D"return =
clk('http://webcache.googleusercontent.com/search?q=3Dcache:mGEt0-ILcb8J:w=
ww.tothepc.com/archives/disable-ipv6-on-windows-7-vista-pc/+%E2%80%9Cipv6+=
on+windows+7%E2%80%9D&amp;cd=3D3&amp;hl=3Den&amp;ct=3Dclnk&amp;gl=3Dus&amp=
;client=3Dsafari','','','','3','mXNhAg_FADzDA4QrEVmSZw','0CCIQIDAC')">Cach=
ed</a> - <a =
href=3D"/search?hl=3Den&amp;client=3Dsafari&amp;rls=3Den&amp;q=3Drelated:w=
ww.tothepc.com/archives/disable-ipv6-on-windows-7-vista-pc/+%E2%80%9Cipv6+=
on+windows+7%E2%80%9D&amp;tbo=3D1&amp;sa=3DX&amp;ei=3DyGisTIDWHoO4sAOD9sj4=
Aw&amp;ved=3D0CCMQHzAC">Similar</a></span></span></div><!--n--><!--m--></l=
i><li class=3D"g w0 knavi"><h3 class=3D"r"><a =
href=3D"http://blog.serghei.net/it/software/ipv6-on-windows-7-is-embarassi=
ng.html" class=3D"l" onmousedown=3D"return =
clk(this.href,'','','','4','le6kRj7z6MWobRkwVGr7bQ','0CCUQFjAD')">serghei'=
s blog=C2=BB Blog Archive =C2=BB <em>IPv6 on Windows 7</em> is =
embarassing!</a></h3><button class=3D"ws" title=3D""></button><div =
class=3D"s"><em>IPv6 on Windows 7</em> is embarassing! April  25th, 2010 =
at 21:51. Recently  I moved to Windows 7 and let Windows XP behind. =
Yeah=E2=80=A6 I know. Using Windows on your <b>...</b><br><span =
class=3D"f"><cite><a =
href=3D"http://blog.serghei.net/it/software/">blog.serghei.net/it/software=
/</a><b>ipv6-on-windows-7</b>-is-embarassing.html</cite> - <span =
class=3D"gl"><a =
href=3D"http://webcache.googleusercontent.com/search?q=3Dcache:aP8HqYw-tFQ=
J:blog.serghei.net/it/software/ipv6-on-windows-7-is-embarassing.html+%E2%8=
0%9Cipv6+on+windows+7%E2%80%9D&amp;cd=3D4&amp;hl=3Den&amp;ct=3Dclnk&amp;gl=
=3Dus&amp;client=3Dsafari" onmousedown=3D"return =
clk('http://webcache.googleusercontent.com/search?q=3Dcache:aP8HqYw-tFQJ:b=
log.serghei.net/it/software/ipv6-on-windows-7-is-embarassing.html+%E2%80%9=
Cipv6+on+windows+7%E2%80%9D&amp;cd=3D4&amp;hl=3Den&amp;ct=3Dclnk&amp;gl=3D=
us&amp;client=3Dsafari','','','','4','7x70JPtOF1IElaB2oZW_Lw','0CCcQIDAD')=
">Cached</a></span></span></div><!--n--><!--m--></li><li class=3D"g w0 =
knavi"><h3 class=3D"r"><a =
href=3D"http://tuts4tech.net/2010/04/05/set-preference-for-ipv4-over-ipv6-=
on-windows-7/" class=3D"l" onmousedown=3D"return =
clk(this.href,'','','','5','YaQdExMvApFxNV46yuoBLA','0CCkQFjAE')">Set =
Preference for IPv4 over <em>IPv6 on Windows 7</em> | =
Tuts4Tech</a></h3><button class=3D"ws" title=3D""></button><div =
class=3D"s">Apr 5, 2010 <b>...</b> On Windows 7 by default if you have a =
IPv6 enabled it will prefer it over IPv4. In a sutiation where your IPv6 =
connection is not native this <b>...</b><br><span class=3D"f"><cite><a =
href=3D"http://tuts4tech.net/.../set-preference-for-ipv4-over-">tuts4tech.=
net/.../set-preference-for-ipv4-over-</a><b>ipv6-on-windows-7</b>/</cite> =
- <span class=3D"gl"><a =
href=3D"http://webcache.googleusercontent.com/search?q=3Dcache:DHQ4mIyC-8A=
J:tuts4tech.net/2010/04/05/set-preference-for-ipv4-over-ipv6-on-windows-7/=
+%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;cd=3D5&amp;hl=3Den&amp;ct=3Dclnk&=
amp;gl=3Dus&amp;client=3Dsafari" onmousedown=3D"return =
clk('http://webcache.googleusercontent.com/search?q=3Dcache:DHQ4mIyC-8AJ:t=
uts4tech.net/2010/04/05/set-preference-for-ipv4-over-ipv6-on-windows-7/+%E=
2%80%9Cipv6+on+windows+7%E2%80%9D&amp;cd=3D5&amp;hl=3Den&amp;ct=3Dclnk&amp=
;gl=3Dus&amp;client=3Dsafari','','','','5','rpYT_Avn1BedkvkInub8wg','0CCsQ=
IDAE')">Cached</a></span></span></div><!--n--><!--m--></li><li class=3D"g =
w0 knavi"><h3 class=3D"r"><a =
href=3D"http://www.tipstrs.com/tip/17071/Disable-IPv6-on-Windows-7" =
class=3D"l" onmousedown=3D"return =
clk(this.href,'','','','6','vxXZ0wcOi_kNaxrMUhZ1lQ','0CC0QFjAF')">Tip: =
Disable <em>IPv6 on Windows 7</em></a></h3><button class=3D"ws" =
title=3D""></button><div class=3D"s">Here's how to disable <em>IPv6 on =
Windows 7</em> 1. Click on the Start orb and select Control Panel. 2. =
Click the Network and Internet link. <b>...</b><br><span =
class=3D"f"><cite><a =
href=3D"http://www.tipstrs.com/tip/17071/Disable-">www.tipstrs.com/tip/170=
71/Disable-</a><b>IPv6-on-Windows-7</b></cite> - <span class=3D"gl"><a =
href=3D"http://webcache.googleusercontent.com/search?q=3Dcache:GK2Tku6B2C8=
J:www.tipstrs.com/tip/17071/Disable-IPv6-on-Windows-7+%E2%80%9Cipv6+on+win=
dows+7%E2%80%9D&amp;cd=3D6&amp;hl=3Den&amp;ct=3Dclnk&amp;gl=3Dus&amp;clien=
t=3Dsafari" onmousedown=3D"return =
clk('http://webcache.googleusercontent.com/search?q=3Dcache:GK2Tku6B2C8J:w=
ww.tipstrs.com/tip/17071/Disable-IPv6-on-Windows-7+%E2%80%9Cipv6+on+window=
s+7%E2%80%9D&amp;cd=3D6&amp;hl=3Den&amp;ct=3Dclnk&amp;gl=3Dus&amp;client=3D=
safari','','','','6','iS0CovSfP-1wD4gSTnOApQ','0CC8QIDAF')">Cached</a></sp=
an></span></div><!--n--><!--m--></li><li class=3D"g w0 knavi"><h3 =
class=3D"r"><a =
href=3D"http://social.answers.microsoft.com/Forums/en-US/w7network/thread/=
815f52c0-717a-457e-b1e7-d8ec54c7c909" class=3D"l" onmousedown=3D"return =
clk(this.href,'','','','7','JziSSbU1tEsfT4r0YYEsGQ','0CDEQFjAG')">IPV6 =
netsh EUI-64 store=3Dpersistent</a></h3><button class=3D"ws" =
title=3D""></button><div class=3D"s"><div class=3D"f">2 =
posts&nbsp;-&nbsp;1 author&nbsp;-&nbsp;Last post:&nbsp;Aug 26, =
2009</div>When using <em>IPv6 on Windows 7</em>. If we do the following =
to get the IPv6 EUI-64 address: netsh interface ipv6 set global =
randomizeidentifiers=3D <b>...</b><br><span class=3D"f"><cite><a =
href=3D"http://social.answers.microsoft.com/.../815f52c0-717a-457e-b1e7-d8=
ec54c7c909">social.answers.microsoft.com/.../815f52c0-717a-457e-b1e7-d8ec5=
4c7c909</a></cite> - <span class=3D"gl"><a =
href=3D"http://webcache.googleusercontent.com/search?q=3Dcache:dtmYcIZYQ04=
J:social.answers.microsoft.com/Forums/en-US/w7network/thread/815f52c0-717a=
-457e-b1e7-d8ec54c7c909+%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;cd=3D7&amp=
;hl=3Den&amp;ct=3Dclnk&amp;gl=3Dus&amp;client=3Dsafari" =
onmousedown=3D"return =
clk('http://webcache.googleusercontent.com/search?q=3Dcache:dtmYcIZYQ04J:s=
ocial.answers.microsoft.com/Forums/en-US/w7network/thread/815f52c0-717a-45=
7e-b1e7-d8ec54c7c909+%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;cd=3D7&amp;hl=
=3Den&amp;ct=3Dclnk&amp;gl=3Dus&amp;client=3Dsafari','','','','7','9R3Km9g=
GTvdFED_y7E8i_Q','0CDUQIDAG')">Cached</a> - <a =
href=3D"/search?hl=3Den&amp;client=3Dsafari&amp;rls=3Den&amp;q=3Drelated:s=
ocial.answers.microsoft.com/Forums/en-US/w7network/thread/815f52c0-717a-45=
7e-b1e7-d8ec54c7c909+%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;tbo=3D1&amp;s=
a=3DX&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&amp;ved=3D0CDYQHzAG">Similar</a></sp=
an></span></div><h3 id=3D"tbpr_7" class=3D"tbpr" style=3D"display:none"><a=
 =
href=3D"/search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;tbs=3Ddsc:1&amp;tbo=3Du&amp;s=
a=3DX&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&amp;ved=3D0CDQQmAcwBg"><span =
class=3D"micon" style=3D"background-position:0 -125px"></span>Get more =
discussion results</a></h3><!--n--><!--m--></li><li class=3D"g w0 =
knavi"><h3 class=3D"r"><a =
href=3D"http://techrepublic.com.com/5208-7343-0.html?forumID=3D101&amp;thr=
eadID=3D328042" class=3D"l" onmousedown=3D"return =
clk(this.href,'','','','8','cZpHW5ut3wrz3d0mvWjOGA','0CDgQFjAH')">How do =
I disable IPv6 in WIndows 7 (Home Premium x64) | 1 of 1</a></h3><button =
class=3D"ws" title=3D""></button><div class=3D"s">Mar 24, 2010<b>...</b> =
How do I disable IPv6 in WIndows 7 (Home Premium x64): I know about =
http:// <a =
href=3D"http://www.tothepc.com/archives/disable-">www.tothepc.com/archives=
/disable-</a><em>ipv6-on-windows-7</em>-vista-pc/  <b>...</b><br><span =
class=3D"f"><cite><a =
href=3D"http://techrepublic.com.com/5208-7343-0.html?forumID=3D101">techre=
public.com.com/5208-7343-0.html?forumID=3D101</a>...</cite> - <span =
class=3D"gl"><a =
href=3D"http://webcache.googleusercontent.com/search?q=3Dcache:k6FeD26V488=
J:techrepublic.com.com/5208-7343-0.html%3FforumID%3D101%26threadID%3D32804=
2+%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;cd=3D8&amp;hl=3Den&amp;ct=3Dclnk=
&amp;gl=3Dus&amp;client=3Dsafari" onmousedown=3D"return =
clk('http://webcache.googleusercontent.com/search?q=3Dcache:k6FeD26V488J:t=
echrepublic.com.com/5208-7343-0.html%3FforumID%3D101%26threadID%3D328042+%=
E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;cd=3D8&amp;hl=3Den&amp;ct=3Dclnk&am=
p;gl=3Dus&amp;client=3Dsafari','','','','8','SkLYIC-_2XgJouJrqiN3cQ','0CDo=
QIDAH')">Cached</a></span></span></div><!--n--><!--m--></li><li class=3D"g=
 w0 knavi"><h3 class=3D"r"><a =
href=3D"http://boardreader.com/thread/IPv6_on_Windows_7_running_in_Hyper_V=
_lxvb__dd546ade-ec27-495c-bc60-4a9ff10eb15d.html" class=3D"l" =
onmousedown=3D"return =
clk(this.href,'','','','9','PBgeIRQv_l0Ub1W6XphRUg','0CDwQFjAI')">Thread =
<em>IPv6 on Windows 7</em> running in Hyper-V | Microsoft TechNet =
<b>...</b></a></h3><button class=3D"ws" title=3D""></button><div =
class=3D"s">I have a VM running on Windows 7. My problem is with the =
IPv6 network, the VM was able to successfully lease an IP from the =
DHCPv6 server but whenever I try <b>...</b><br><span class=3D"f"><cite><a =
href=3D"http://boardreader.com/.../">boardreader.com/.../</a><b>IPv6_on_Wi=
ndows_7</b>_running_in_Hyper_V_lxvb__ =
dd546ade-ec27-495c-bc60-4a9ff10eb15d.html</cite> - <span class=3D"gl"><a =
href=3D"http://webcache.googleusercontent.com/search?q=3Dcache:60cJkPAgZ-Q=
J:boardreader.com/thread/IPv6_on_Windows_7_running_in_Hyper_V_lxvb__dd546a=
de-ec27-495c-bc60-4a9ff10eb15d.html+%E2%80%9Cipv6+on+windows+7%E2%80%9D&am=
p;cd=3D9&amp;hl=3Den&amp;ct=3Dclnk&amp;gl=3Dus&amp;client=3Dsafari" =
onmousedown=3D"return =
clk('http://webcache.googleusercontent.com/search?q=3Dcache:60cJkPAgZ-QJ:b=
oardreader.com/thread/IPv6_on_Windows_7_running_in_Hyper_V_lxvb__dd546ade-=
ec27-495c-bc60-4a9ff10eb15d.html+%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;c=
d=3D9&amp;hl=3Den&amp;ct=3Dclnk&amp;gl=3Dus&amp;client=3Dsafari','','','',=
'9','CmKODkNvic6IcW0pklXOhA','0CD4QIDAI')">Cached</a></span></span></div><=
!--n--><!--m--></li><li class=3D"g w0 knavi"><h3 class=3D"r"><a =
href=3D"http://www.sevenforums.com/network-sharing/68063-ipv6-doesnt-work-=
after-waking-up-sleep-mode.html" class=3D"l" onmousedown=3D"return =
clk(this.href,'','','','10','b_o7KJRyLheLaiGbD_TV_w','0CEAQFjAJ')">Ipv6 =
doesn't work after waking up from sleep mode - Windows 7 =
Forums</a></h3><button class=3D"ws" title=3D""></button><div =
class=3D"s">Mar 2, 2010 <b>...</b> Hi All, I had a problem about =
<em>ipv6 on windows 7</em> for a long time. I have a ipv6 &amp; ipv4 =
dual stack network. Every time I wake up my computer, =
<b>...</b><br><span class=3D"f"><cite><a =
href=3D"http://www.sevenforums.com/.../68063-ipv6-doesnt-work-after-waking=
-up-sleep-">www.sevenforums.com/.../68063-ipv6-doesnt-work-after-waking-up=
-sleep-</a> mode.html</cite> - <span class=3D"gl"><a =
href=3D"http://webcache.googleusercontent.com/search?q=3Dcache:gdnEfWgrnz8=
J:www.sevenforums.com/network-sharing/68063-ipv6-doesnt-work-after-waking-=
up-sleep-mode.html+%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;cd=3D10&amp;hl=3D=
en&amp;ct=3Dclnk&amp;gl=3Dus&amp;client=3Dsafari" onmousedown=3D"return =
clk('http://webcache.googleusercontent.com/search?q=3Dcache:gdnEfWgrnz8J:w=
ww.sevenforums.com/network-sharing/68063-ipv6-doesnt-work-after-waking-up-=
sleep-mode.html+%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;cd=3D10&amp;hl=3De=
n&amp;ct=3Dclnk&amp;gl=3Dus&amp;client=3Dsafari','','','','10','M7PJRruE8s=
WmTrokshcHQg','0CEIQIDAJ')">Cached</a></span></span></div><!--n--></li><di=
v></div></ol></div><!--z--><div id=3D"wrz" class=3D"e" =
style=3D"display:none">You have removed results from this search. =
<span><button class=3D"wpb" title=3D"-" style=3D"background-position: =
-159px -55px; "></button><a href=3D"#" class=3D"fl" onclick=3D"return =
false" style=3D"font-size:small"><span>Hide =
them</span></a></span></div><div id=3D"wrm" class=3D"std" =
style=3D"display:none">Loading...</div><ol id=3D"wrg" =
style=3D"display:block;margin-left:3em"></ol></div> </div> <div =
id=3D"leftnav" role=3D"navigation" style=3D"padding-top: 3px; =
border-right-width: 1px; border-right-style: solid; border-right-color: =
rgb(211, 225, 249); padding-left: 14px; padding-right: 4px; position: =
absolute; top: 0px; width: 178px; margin-top: 0px; min-height: 0px; " =
onclick=3D"google.psy&amp;&amp;google.psy.qs(event)"><div =
id=3D"ms"><ul><li class=3D"mitem msel"><span class=3D"micon" =
style=3D"background-position:-20px -85px"></span>Everything</li><li =
class=3D"mitem"><a =
href=3D"/images?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;source=3Dlnms&amp;tbs=3Disch:=
1&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&amp;sa=3DX&amp;oi=3Dmode_link&amp;ct=3Dm=
ode&amp;ved=3D0CAsQ_AU" class=3D"q qs"><span class=3D"micon" =
style=3D"background-position:-40px -85px"></span>Images</a></li><li =
class=3D"mitem"><a =
href=3D"/search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;source=3Dlnms&amp;tbs=3Dvid:1=
&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&amp;sa=3DX&amp;oi=3Dmode_link&amp;ct=3Dmo=
de&amp;ved=3D0CAwQ_AU" class=3D"q qs"><span class=3D"micon" =
style=3D"background-position:-80px -85px"></span>Videos</a></li></ul><ul =
class=3D"nojsb" id=3D"hidden_modes"><li class=3D"mitem"><a =
href=3D"http://maps.google.com/maps?client=3Dsafari&amp;rls=3Den&amp;q=3D%=
E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;oe=3DUTF-8&amp;um=3D1&amp;ie=3DUTF-=
8&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&amp;sa=3DX&amp;oi=3Dmode_link&amp;ct=3Dm=
ode&amp;ved=3D0CA0Q_AU" class=3D"q qs"><span class=3D"micon" =
style=3D"background-position:-80px -105px"></span>Maps</a></li><li =
class=3D"mitem"><a =
href=3D"/search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;source=3Dlnms&amp;tbs=3Dnws:1=
&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&amp;sa=3DX&amp;oi=3Dmode_link&amp;ct=3Dmo=
de&amp;ved=3D0CA4Q_AU" class=3D"q qs"><span class=3D"micon" =
style=3D"background-position:-120px -85px"></span>News</a></li><li =
class=3D"mitem"><a =
href=3D"/search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;source=3Dlnms&amp;tbs=3Dshop:=
1&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&amp;sa=3DX&amp;oi=3Dmode_link&amp;ct=3Dm=
ode&amp;ved=3D0CA8Q_AU" class=3D"q qs"><span class=3D"micon" =
style=3D"background-position:-120px -105px"></span>Shopping</a></li><li =
class=3D"mitem"><a =
href=3D"/search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;source=3Dlnms&amp;tbs=3Dbks:1=
&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&amp;sa=3DX&amp;oi=3Dmode_link&amp;ct=3Dmo=
de&amp;ved=3D0CBAQ_AU" class=3D"q qs"><span class=3D"micon" =
style=3D"background-position:-40px -105px"></span>Books</a></li><li =
class=3D"mitem"><a =
href=3D"/search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;source=3Dlnms&amp;tbs=3Dblg:1=
&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&amp;sa=3DX&amp;oi=3Dmode_link&amp;ct=3Dmo=
de&amp;ved=3D0CBEQ_AU" class=3D"q qs"><span class=3D"micon" =
style=3D"background-position:0 -105px"></span>Blogs</a></li><li =
class=3D"mitem"><a =
href=3D"/search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;source=3Dlnms&amp;tbs=3Dmbl:1=
&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&amp;sa=3DX&amp;oi=3Dmode_link&amp;ct=3Dmo=
de&amp;ved=3D0CBIQ_AU" class=3D"q qs"><span class=3D"micon" =
style=3D"background-position:-40px -125px"></span>Updates</a></li><li =
class=3D"mitem"><a =
href=3D"/search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;source=3Dlnms&amp;tbs=3Ddsc:1=
&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&amp;sa=3DX&amp;oi=3Dmode_link&amp;ct=3Dmo=
de&amp;ved=3D0CBMQ_AU" class=3D"q qs"><span class=3D"micon" =
style=3D"background-position:0 =
-125px"></span>Discussions</a></li></ul><a id=3D"showmodes" class=3D"jsb =
q nj" href=3D"#" =
onclick=3D"google.x(this.id,google.srp.toggleModes);return false" =
style=3D"border-bottom:1px solid #c9d7f1;padding-bottom:9px"><span =
class=3D"micon"></span><span class=3D"msm">More</span><span =
class=3D"msl">Fewer</span></a></div><div =
style=3D"clear:both;overflow:hidden"><h2 class=3D"hd">Search =
Options</h2><ul id=3D"tbd" class=3D"med"><li class=3D"jsb"><ul =
class=3D"tbt"><li class=3D"tbos" id=3D"frim_" onclick=3D"return =
google.Toolbelt.tbosClk(event)">All results</li></ul></li><li><ul =
class=3D"tbt"><li class=3D"tbou" id=3D"prv_1"><a =
href=3D"/search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;source=3Dlnt&amp;tbs=3Dprv:1&=
amp;sa=3DX&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&amp;ved=3D0CAgQpwU" class=3D"q =
qs">Page previews</a></li></ul></li></ul><a =
href=3D"/search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;tbo=3D1" class=3D"nj q" =
id=3D"tbpi" onclick=3D"return google.x(this,function(){return =
google.Toolbelt.togglePromotedTools(this, event)})" =
style=3D"clear:both;display:block;margin:8px;margin-left:16px"><span =
id=3D"tbp" style=3D"background-position:-159px =
-70px;border:0;display:block;float:left;height:14px;margin-right:3px;width=
:14px"></span><nobr class=3D"tbpo">Fewer search tools</nobr><nobr =
class=3D"tbpc">More search tools</nobr></a></div></div></div> <div =
id=3D"foot" class=3D"tsf-p" role=3D"contentinfo"><div id=3D"navcnt"><table=
 id=3D"nav" =
style=3D"border-collapse:collapse;text-align:left;direction:ltr;margin:17p=
x auto 0"><tbody><tr valign=3D"top"><td class=3D"b"><span class=3D"csb" =
style=3D"background-position:-24px 0;width:28px"></span></td><td =
class=3D"cur"><span class=3D"csb" style=3D"background-position:-53px =
0;width:20px"></span>1</td><td><a =
href=3D"/search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&a=
mp;start=3D10&amp;sa=3DN" class=3D"fl"><span class=3D"csb ch" =
style=3D"background-position:-74px 0;width:20px"></span>2</a></td><td><a =
href=3D"/search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&a=
mp;start=3D20&amp;sa=3DN" class=3D"fl"><span class=3D"csb ch" =
style=3D"background-position:-74px 0;width:20px"></span>3</a></td><td><a =
href=3D"/search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&a=
mp;start=3D30&amp;sa=3DN" class=3D"fl"><span class=3D"csb ch" =
style=3D"background-position:-74px 0;width:20px"></span>4</a></td><td><a =
href=3D"/search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&a=
mp;start=3D40&amp;sa=3DN" class=3D"fl"><span class=3D"csb ch" =
style=3D"background-position:-74px 0;width:20px"></span>5</a></td><td><a =
href=3D"/search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&a=
mp;start=3D50&amp;sa=3DN" class=3D"fl"><span class=3D"csb ch" =
style=3D"background-position:-74px 0;width:20px"></span>6</a></td><td><a =
href=3D"/search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&a=
mp;start=3D60&amp;sa=3DN" class=3D"fl"><span class=3D"csb ch" =
style=3D"background-position:-74px 0;width:20px"></span>7</a></td><td><a =
href=3D"/search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&a=
mp;start=3D70&amp;sa=3DN" class=3D"fl"><span class=3D"csb ch" =
style=3D"background-position:-74px 0;width:20px"></span>8</a></td><td><a =
href=3D"/search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&a=
mp;start=3D80&amp;sa=3DN" class=3D"fl"><span class=3D"csb ch" =
style=3D"background-position:-74px 0;width:20px"></span>9</a></td><td><a =
href=3D"/search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&a=
mp;start=3D90&amp;sa=3DN" class=3D"fl"><span class=3D"csb ch" =
style=3D"background-position:-74px 0;width:20px"></span>10</a></td><td =
class=3D"b"><a =
href=3D"/search?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&amp;cl=
ient=3Dsafari&amp;rls=3Den&amp;prmd=3Div&amp;ei=3DyGisTIDWHoO4sAOD9sj4Aw&a=
mp;start=3D10&amp;sa=3DN" class=3D"pn knavi" id=3D"pnnext" =
style=3D"text-align:left;text-decoration:none"><span class=3D"csb ch" =
style=3D"background-position:-96px 0;width:71px"></span><span =
style=3D"display:block;margin-left:53px;text-decoration:underline">Next</s=
pan></a></td></tr></tbody></table></div><div =
style=3D"height:13px;line-height:0"></div><div><p id=3D"bfl" =
style=3D"margin:6px 0 0;text-align:center"><a =
href=3D"/support/websearch/bin/answer.py?answer=3D134479&amp;hl=3Den" =
class=3D"fl">Search Help</a> <a =
href=3D"/quality_form?q=3D%E2%80%9Cipv6+on+windows+7%E2%80%9D&amp;hl=3Den&=
amp;client=3Dsafari&amp;rls=3Den&amp;prmd=3Div" target=3D"_blank" =
class=3D"fl">Give us feedback</a> </p></div><div id=3D"fll" =
style=3D"margin:19px auto 19px auto;text-align:center"><a =
href=3D"/">Google&nbsp;Home</a><a =
href=3D"/intl/en/ads/">Advertising&nbsp;Programs</a><a =
href=3D"/services/">Business Solutions</a><a =
href=3D"/intl/en/privacy.html">Privacy</a><a =
href=3D"/intl/en/about.html">About Google</a></div></div><script =
type=3D"text/javascript">(new Image()).src=3D"<a =
href=3D"http://id.google.com/verify/EAAAAHDBvJ1dM1tVSi6Q3rm5Ni8.gif">http:=
//id.google.com/verify/EAAAAHDBvJ1dM1tVSi6Q3rm5Ni8.gif</a>";</script><nosc=
ript></noscript></div>  </div> <script>function _gjp() {!(location.hash =
&& _gjuc()) && setTimeout(_gjp, =
500);}google.j[1]=3D{cc:[],co:['ghead','cnt','xjsi'],css:document.getEleme=
ntById('gstyle').innerHTML,main:'<div id=3Dghead></div><div =
id=3Dcnt></div><div is=3Dxjsi></div>'};function wgjp(){var =
xjs=3Ddocument.createElement('script');xjs.src=3D'/extern_chrome/7c8f32f65=
b860aba.js?ie=3DUTF-8&oe=3DUTF-8';(document.getElementById('xjsd') || =
document.body).appendChild(xjs)};</script><div id=3D"xjsd"><script =
src=3D"/extern_js/f/CgJlbhICdXMrMEU4ASwrMFo4ACwrMA44ACwrMBc4ACwrMCc4ACwrMD=
w4ACwrMFE4ACwrMFk4EiwrMAo4gwFALywrMBY4ACwrMBk4ACwrMCE4AEABLCswJTjPiAEsKzAq=
OAssKzArOBEsKzA1OAQsKzBAOAAsKzBBOAAsKzBOOAYsKzBTOAAsKzBUOAAsKzBjOAAsKzAdOF=
0sKzBcOCAsKzAYOAAsKzAmOAAsgAIZkAIe/_RTxjFVIpsY.js"></script><script =
src=3D"/extern_chrome/7c8f32f65b860aba.js?ie=3DUTF-8&amp;oe=3DUTF-8"></scr=
ipt></div><div =
id=3D"xjsi"><script>if(google.y)google.y.first=3D[];if(google.y)google.y.f=
irst=3D[];if(!google.xjs){google.dstr=3D[];google.rein=3D[];window.setTime=
out(function(){var =
a=3Ddocument.createElement("script");a.src=3D"/extern_js/f/CgJlbhICdXMrMEU=
4ASwrMFo4ACwrMA44ACwrMBc4ACwrMCc4ACwrMDw4ACwrMFE4ACwrMFk4EiwrMAo4gwFALywrM=
BY4ACwrMBk4ACwrMCE4AEABLCswJTjPiAEsKzAqOAssKzArOBEsKzA1OAQsKzBAOAAsKzBBOAA=
sKzBOOAYsKzBTOAAsKzBUOAAsKzBjOAAsKzAdOF0sKzBcOCAsKzAYOAAsKzAmOAAsgAIZkAIe/=
_RTxjFVIpsY.js";(document.getElementById("xjsd")||document.body).appendChi=
ld(a);if(google.timers&&google.timers.load.t)google.timers.load.t.xjsls=3D=
(new Date).getTime();},0);
=
google.xjs=3D1}window.mbtb1=3D{tbs:"",docid:"15117440554053306690",usg:"6f=
bc",obd:false};google.base_href=3D'/search?q\x3d%E2%80%9Cipv6+on+windows+7=
%E2%80%9D\x26hl\x3den\x26client\x3dsafari\x26rls\x3den\x26prmd\x3div';goog=
le.sn=3D'web';google.Toolbelt.atg=3D[7,3,3,4,1];google.Toolbelt.pbt=3D[[1,=
0],[4,4]];google.Toolbelt.pti=3D{7:1,22:1};google.drhs=3D1;var =
oldElement=3Ddocument.getElementById('tbt3');if(oldElement){oldElement.par=
entNode.removeChild(oldElement);}delete google.ww;(function(){var r =3D =
(function() {google.y.first.push(function(){google.Tbpr && =
google.Tbpr.init();google.tbpr && =
google.tbpr.init();google.Toolbelt.initializeToolElements =
&&google.Toolbelt.initializeToolElements();;google.sw({q:'=E2=80=9Cipv6 =
on windows 7=E2=80=9D',nn:'Fred =
B',lb:1,ls:'__h9U6U8wOlrvc2X5XY_fC_OdQqRo\x3d',ls2:'__ijwM-hyOn5ilVhDloJ0j=
6WpODM4\x3d'});var =
form=3Ddocument.gs||document.f||document.gs;google.ac.i(form,form.q,'','=E2=
=80=9Cipv6 on windows =
7=E2=80=9D','oJj3KdmJjUiSCsLBvd8YGw',{o:1,sw:1,l:1,r:0});google.riu=3D{ren=
der:function(){window.setTimeout(function(){var =
a=3Ddocument.createElement("script");a.src=3D"/extern_js/f/CgJlbhICdXMrMD8=
4AyyAAhmQAh4/fpJ2E8bIc2s.js";(document.getElementById("xjsd")||document.bo=
dy).appendChild(a);},0);
}};;google.mc =3D [[14,{}],[99,{}],[84,{}],[22,{"m_error":"\u003Cfont =
color=3Dred\u003EError:\u003C/font\u003E The server could not complete =
your request.  Try again in 30 seconds.","m_tip":"Click for more =
information"}],[64,{}],[92,{"avgTtfc":1000,"focus":true,"hpt":250,"p_dym":=
"Did you mean:","p_gs":"Google Search","p_sif":"Search instead =
for","p_srf":"Showing results =
for","rpt":41,"tdur":50}]];google.med('init');google.History&&google.Histo=
ry.initialize('/search?client\x3dsafari\x26amp;rls\x3den\x26amp;q\x3d%E2%8=
0%9Cipv6+on+windows+7%E2%80%9D\x26amp;ie\x3dUTF-8\x26amp;oe\x3dUTF-8')});}=
);r();var loc=3Dwindow.location.hash =
?window.location.href.substr(window.location.href.indexOf('#')):'#';if =
(loc=3D=3D'#'&&google.defre) =
{google.defre=3D1;google.y.first.push(function(){if =
(google.j&&google.j.init) =
{google.rein&&google.rein.push(r);}});}})();if(google.j&&google.j.en&&goog=
le.j.xi){window.setTimeout(google.j.xi,0);google.fade=3Dnull;}</script></d=
iv><script>(function(){
var b,d,e,f;function =
g(a,c){if(a.removeEventListener){a.removeEventListener("load",c,false);a.r=
emoveEventListener("error",c,false)}else{a.detachEvent("onload",c);a.detac=
hEvent("onerror",c)}}function h(a){f=3D(new =
Date).getTime();++d;a=3Da||window.event;var =
c=3Da.target||a.srcElement;g(c,h)}var =
i=3Ddocument.getElementsByTagName("img");b=3Di.length;d=3D0;for(var =
j=3D0,k;j<b;++j){k=3Di[j];if(k.complete||typeof =
k.src!=3D"string"||!k.src)++d;else =
if(k.addEventListener){k.addEventListener("load",h,false);k.addEventListen=
er("error",
=
h,false)}else{k.attachEvent("onload",h);k.attachEvent("onerror",h)}}e=3Db-=
d;function =
l(){if(!google.timers.load.t)return;google.timers.load.t.ol=3D(new =
Date).getTime();google.timers.load.t.iml=3Df;google.kCSI.imc=3Dd;google.kC=
SI.imn=3Db;google.kCSI.imp=3De;google.timers.load.t.xjs&&google.report&&go=
ogle.report(google.timers.load,google.kCSI)}if(window.addEventListener)win=
dow.addEventListener("load",l,false);else =
if(window.attachEvent)window.attachEvent("onload",l);google.timers.load.t.=
prt=3D(f=3D(new Date).getTime());
})();
</script><div style=3D"font-family: Helvetica; font-size: 12px; color: =
black; text-align: left; "><br =
class=3D"webkit-block-placeholder"></div></body></html>=

--Apple-Mail-2-970354582--

From fred@cisco.com  Wed Oct  6 06:13:44 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D27A63A6E67 for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 06:13:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.029
X-Spam-Level: 
X-Spam-Status: No, score=-110.029 tagged_above=-999 required=5 tests=[AWL=-0.330, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OlIHgo8m00-Y for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 06:13:43 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id D271B3A6E46 for <v6ops@ietf.org>; Wed,  6 Oct 2010 06:13:42 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAAETrExAZnwN/2dsb2JhbACiQ3GlVZwlhUcEikCDAg
X-IronPort-AV: E=Sophos;i="4.57,290,1283731200"; d="scan'208";a="167416510"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 06 Oct 2010 13:14:42 +0000
Received: from Freds-Computer.local (rtp-vpn5-459.cisco.com [10.82.233.204]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o96DEYDg029896; Wed, 6 Oct 2010 13:14:37 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Wed, 06 Oct 2010 09:14:42 -0400
X-PGP-Universal: processed; by Freds-Computer.local on Wed, 06 Oct 2010 09:14:42 -0400
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <D40F684E-2A7B-42E6-ADC4-F4AFDE879FE3@cisco.com>
Date: Wed, 6 Oct 2010 09:14:28 -0400
Message-Id: <DC5EA05D-3758-4351-9DB0-A46218482815@cisco.com>
References: <D40F684E-2A7B-42E6-ADC4-F4AFDE879FE3@cisco.com>
To: IPv6 Operations <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: Dave Thaler <dthaler@microsoft.com>
Subject: Re: [v6ops] =?windows-1252?q?=93ipv6_on_windows_7=94_-_Google_Search?=
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 13:13:45 -0000

> It would be interesting to understand what the issue is here. I =
suspect it has nothing to do with the actual Windows (or Apple, Linux, =
etc) implementation, but is more related to issues as discussed in =
http://tools.ietf.org/html/draft-wing-http-new-tech. Would it make sense =
for v6ops to make a recommendation to address the concerns?

Reading over my own email, my comment can be confusing - the =
getaddrinfo() stuff is in the implementations in question, so it does =
indeed "have something to do with the implementation". I guess my =
question is -=20

I get questions about operational IPv6 deployment due to issues of =
implementation. One ISP recently told me that they can't deploy AAAA =
records for certain services because when their customers are in the =
region of a neighboring ISP that runs IPv6 as a walled garden and btw =
respond to connection attempts with a TCP RST, their user's laptops =
don't correctly fall back to IPv4. I can imagine several possible =
recommendations, and might actually recommend two of them: "happy =
eyeballs" as Dan Wing describes (open TCP sessions at some rate trying =
all IPv4 and IPv6 combinations until one of them opens a session, with =
the objective of achieving an open session within a stated interval such =
as 1 second or less), and an operational recommendation that if you're =
going to run IPv6 as a walled garden, that you configure your first hop =
routers to respond "host unreachable" or "network unreachable" to any =
packet that you have decided to not deliver.

Would it be appropriate, and would the working group like to discuss, =
such recommendations?=

From martin@millnert.se  Wed Oct  6 06:27:01 2010
Return-Path: <martin@millnert.se>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0FC7A3A6D93 for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 06:27:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.147
X-Spam-Level: 
X-Spam-Status: No, score=-2.147 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, SARE_SUB_ENC_UTF8=0.152]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j+rHLI-e3wxF for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 06:27:00 -0700 (PDT)
Received: from ncis.csbnet.se (ncis.csbnet.se [IPv6:2a02:9a0:4:104:a00:2bff:fec5:95ea]) by core3.amsl.com (Postfix) with ESMTP id D41453A6CDD for <v6ops@ietf.org>; Wed,  6 Oct 2010 06:26:59 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by ncis.csbnet.se (Postfix) with ESMTP id EECEB1BD509; Wed,  6 Oct 2010 15:27:58 +0200 (CEST)
Received: from ncis.csbnet.se ([127.0.0.1]) by localhost (ncis.vpn.anti [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6A-Wn24BKJhX; Wed,  6 Oct 2010 15:27:46 +0200 (CEST)
Received: from [IPv6:2a02:9a0:4:104:21a:4dff:fe48:f17] (hsa.csbnet.se [IPv6:2a02:9a0:4:104:21a:4dff:fe48:f17]) by ncis.csbnet.se (Postfix) with ESMTPSA id D2D7113904; Wed,  6 Oct 2010 15:27:44 +0200 (CEST)
From: Martin Millnert <martin@millnert.se>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <DC5EA05D-3758-4351-9DB0-A46218482815@cisco.com>
References: <D40F684E-2A7B-42E6-ADC4-F4AFDE879FE3@cisco.com> <DC5EA05D-3758-4351-9DB0-A46218482815@cisco.com>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-cRb8vFXJnXasxj8OMwD4"
Date: Wed, 06 Oct 2010 15:27:43 +0200
Message-ID: <1286371663.3459.3.camel@hsa.csbnet.se>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.2 
Cc: IPv6 Operations <v6ops@ietf.org>, Dave Thaler <dthaler@microsoft.com>
Subject: Re: [v6ops] =?utf-8?q?=E2=80=9Cipv6_on_windows_7=E2=80=9D_-_Google_Se?= =?utf-8?q?arch?=
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 13:27:01 -0000

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

On Wed, 2010-10-06 at 09:14 -0400, Fred Baker wrote:
> Would it be appropriate, and would the working group like to discuss, suc=
h recommendations?

Yes, I believe this can be very valuable recommendations for both ISPs
and OS vendors, to make eyeballs... more happy.

Cheers,
--=20
Martin Millnert <martin@millnert.se>

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

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

iEYEABECAAYFAkyseUsACgkQatANZBhP8gOJLgCaAisHa1wo+ri3w5w0vqpgaWTb
FZUAni9SJIPlq+17x8LhmMyTC3CWv+jg
=CfCy
-----END PGP SIGNATURE-----

--=-cRb8vFXJnXasxj8OMwD4--


From randy@psg.com  Wed Oct  6 07:02:54 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 483503A6F48 for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 07:02:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.554
X-Spam-Level: 
X-Spam-Status: No, score=-2.554 tagged_above=-999 required=5 tests=[AWL=0.045,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MHnVdQ5z3Rb0 for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 07:02:53 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 0D0DC3A6CDD for <v6ops@ietf.org>; Wed,  6 Oct 2010 07:02:53 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1P3Ub1-000Gqg-LL; Wed, 06 Oct 2010 14:03:52 +0000
Date: Wed, 06 Oct 2010 23:03:50 +0900
Message-ID: <m21v83quyh.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Tina TSOU <tena@huawei.com>
In-Reply-To: <9E025610-B99C-40B3-810F-BFDCD5CAE136@huawei.com>
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <54BED382-7B8C-4C23-826C-054B31333970@cisco.com> <641BFD35-D097-4E22-8A71-F3E75EB7CD4A@huawei.com> <C165683A-1C03-415A-806F-674620AB607B@cisco.com> <m2aamrraos.wl%randy@psg.com> <56DC0013-40B8-4D3A-99E0-B2837302DD70@huawei.com> <m28w2br9t0.wl%randy@psg.com> <9E025610-B99C-40B3-810F-BFDCD5CAE136@huawei.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 14:02:54 -0000

>> we all do.  and one of mine is that we need to be careful that our
>> contribution is not exponentially proportional to layer numbers
>> greater than seven.
> What does it mean, Randy?

avoid political bs, produce technical content

From tena@huawei.com  Wed Oct  6 07:21:04 2010
Return-Path: <tena@huawei.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 120693A6F63 for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 07:21:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.298
X-Spam-Level: 
X-Spam-Status: No, score=-100.298 tagged_above=-999 required=5 tests=[AWL=0.197, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nSRxtK9q1ADx for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 07:21:03 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id F1D5C3A6F83 for <v6ops@ietf.org>; Wed,  6 Oct 2010 07:20:52 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9V00F7OH7VMZ@szxga04-in.huawei.com> for v6ops@ietf.org; Wed, 06 Oct 2010 22:21:31 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9V00819H7V07@szxga04-in.huawei.com> for v6ops@ietf.org; Wed, 06 Oct 2010 22:21:31 +0800 (CST)
Received: from [192.168.1.4] ([113.116.37.175]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L9V00H3HH7UHY@szxml02-in.huawei.com>; Wed, 06 Oct 2010 22:21:31 +0800 (CST)
Date: Wed, 06 Oct 2010 22:21:29 +0800
From: Tina TSOU <tena@huawei.com>
In-reply-to: <m21v83quyh.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
Message-id: <96308D61-00CE-4D93-880E-3B1612F4F4D0@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <54BED382-7B8C-4C23-826C-054B31333970@cisco.com> <641BFD35-D097-4E22-8A71-F3E75EB7CD4A@huawei.com> <C165683A-1C03-415A-806F-674620AB607B@cisco.com> <m2aamrraos.wl%randy@psg.com> <56DC0013-40B8-4D3A-99E0-B2837302DD70@huawei.com> <m28w2br9t0.wl%randy@psg.com> <9E025610-B99C-40B3-810F-BFDCD5CAE136@huawei.com> <m21v83quyh.wl%randy@psg.com>
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 14:21:04 -0000

B. R.
Tina
http://tinatsou.weebly.com




On Oct 6, 2010, at 10:03 PM, Randy Bush wrote:

>>> we all do.  and one of mine is that we need to be careful that our
>>> contribution is not exponentially proportional to layer numbers
>>> greater than seven.
>> What does it mean, Randy?
>
> avoid political bs, produce technical content
This is what I tried to avoid, if the problem statement I-D and the  
use cases I-D and transition guides I-D are technically fine, the  
problem statement I-D should not block the way of the latter. Perhaps  
I worry too much. It may not happen.


From fernando.gont.netbook.win@gmail.com  Wed Oct  6 07:32:27 2010
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A700B3A6E6A for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 07:32:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.343
X-Spam-Level: 
X-Spam-Status: No, score=-2.343 tagged_above=-999 required=5 tests=[AWL=-0.044, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KAAnuBK2cvWe for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 07:32:26 -0700 (PDT)
Received: from mail-gw0-f66.google.com (mail-gw0-f66.google.com [74.125.83.66]) by core3.amsl.com (Postfix) with ESMTP id ED02A3A6CDD for <v6ops@ietf.org>; Wed,  6 Oct 2010 07:32:25 -0700 (PDT)
Received: by gwb11 with SMTP id 11so2076608gwb.1 for <v6ops@ietf.org>; Wed, 06 Oct 2010 07:33:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=6g/Gli5/trMIcRl6tZ/kBoQnYJBB0sqWRqrl3uKEwNA=; b=xUXmSWu/KIm7BGFkH73JPAyYi9CvcS4aXUQSyQ8AH2AaETurOKR22TQWXmSJ1kMv+S ikm6JNy5L7xkv5wQWyzObBUKZAIqTeFjHhQRH2XEo6eEunge62o+hw+BM1SsKcXjsGE1 ijNy/Nb5su5mfWTL4ymgsV4GUmfw+lWhFlZ7c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=hjQlvE0LdpHgltKbUHywXKAcUFJC7Hc3wMpQUz63FYUm2mnp9XrE8JM9pAgYk2R9CS xaT79btlXUTkvxsYfLkDM9kGpLXf0tWngZn7fnlWvU0Wmg0muaIVfhNiNP6cHnFhgXCE p2gpQKKzKKHrKQp1Ib/oL3Xr43Wa5zqopzJvo=
Received: by 10.150.49.15 with SMTP id w15mr2011776ybw.245.1286375605927; Wed, 06 Oct 2010 07:33:25 -0700 (PDT)
Received: from [192.168.0.122] (61-128-17-190.fibertel.com.ar [190.17.128.61]) by mx.google.com with ESMTPS id r36sm1301592yba.0.2010.10.06.07.33.22 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 06 Oct 2010 07:33:25 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4CAC88AD.3010901@gont.com.ar>
Date: Wed, 06 Oct 2010 11:33:17 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <D40F684E-2A7B-42E6-ADC4-F4AFDE879FE3@cisco.com> <DC5EA05D-3758-4351-9DB0-A46218482815@cisco.com>
In-Reply-To: <DC5EA05D-3758-4351-9DB0-A46218482815@cisco.com>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, Dave Thaler <dthaler@microsoft.com>
Subject: Re: [v6ops] =?windows-1252?q?=93ipv6_on_windows_7=94_-_Google_Search?=
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 14:32:27 -0000

Hi, Fred,

> Reading over my own email, my comment can be confusing - the
> getaddrinfo() stuff is in the implementations in question, so it does
> indeed "have something to do with the implementation". I guess my
> question is -
> 
> I get questions about operational IPv6 deployment due to issues of
> implementation. One ISP recently told me that they can't deploy AAAA
> records for certain services because when their customers are in the
> region of a neighboring ISP that runs IPv6 as a walled garden and btw
> respond to connection attempts with a TCP RST, their user's laptops
> don't correctly fall back to IPv4. 

Note: I do recall checking, years ago, that Windows systems used to
respond with RST when e.g. the queue of incoming connections was full
(e.g., the server was under s SYN-flood attack). As a result, RSTs had
the semantics of "soft errors", rather than "hard errors", and hence
Windows was being coherent with their own implementation. -- Although
IMO their behavior was coherent but wrong: RSTs are ment to signal hard
errors... so they shouldn't have been sending RSTs when under a
SYN-flood attack, and would be aborting connections upon receipt of an RST.



> I can imagine several possible
> recommendations, and might actually recommend two of them: "happy
> eyeballs" as Dan Wing describes (open TCP sessions at some rate
> trying all IPv4 and IPv6 combinations until one of them opens a
> session, with the objective of achieving an open session within a
> stated interval such as 1 second or less), 

FWIW, this approach of "parallel connections" was mentioned in at least
some of the I-D versions that led to RFC 5461.

However, keep in mind that this approach of "try all possible addresses"
may put a bit of stress on the servers - particularly those that are
popular and also have multiple addresses.


> and an operational
> recommendation that if you're going to run IPv6 as a walled garden,
> that you configure your first hop routers to respond "host
> unreachable" or "network unreachable" to any packet that you have
> decided to not deliver.

Specs-wise that wouldn't help. We (other folks and myself) tried to
pursue RFC5461 as std track... but there was an endless debate on tcpm,
and the I-D ended up targeting the Informational track. Specs-wise,
these "destination unreachables" indicate soft errors, and thus should
not cause the connection to be aborted.

That said, RFC5461 *has* been implemented in the real world, despite
tcpm's concerns.

Some folks at a japanese telco had mentioned that they had asked a
(large :-) ) vendor to implement RFC 5461, but they argued that they
wouldn't, because RFC5461 was not std track.


> Would it be appropriate, and would the working group like to discuss,
> such recommendations? 

The "problem" here is that, in order for such a recommendation to make
sense, you need to have clients react to those ICMPs by aborting the
corresponding connection.... and that basically means re-hashing RFC 5461.

I guess that if the proposal aims at requiring this behavior *only* for
ICMPv6 (and *not* for ICMPv4), it may have more chances to fly, but...

Thoughts?

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





From gvandeve@cisco.com  Wed Oct  6 07:44:21 2010
Return-Path: <gvandeve@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9BE8B3A6F10 for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 07:44:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.23
X-Spam-Level: 
X-Spam-Status: No, score=-10.23 tagged_above=-999 required=5 tests=[AWL=-0.231, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tQ3Wz3lmNdpq for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 07:44:20 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id A8DD13A6C4C for <v6ops@ietf.org>; Wed,  6 Oct 2010 07:44:16 -0700 (PDT)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtYDAA8orEyQ/khLgWdsb2JhbACiRBUBARYiIqdbnC+FRwSNSA
X-IronPort-AV: E=Sophos;i="4.57,290,1283731200"; d="scan'208";a="65968999"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 06 Oct 2010 14:45:16 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id o96EjGLk015400; Wed, 6 Oct 2010 14:45:16 GMT
Received: from xmb-ams-101.cisco.com ([144.254.74.76]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 6 Oct 2010 16:45:16 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 6 Oct 2010 16:45:14 +0200
Message-ID: <4269EA985EACD24987D82DAE2FEC62E50254C801@XMB-AMS-101.cisco.com>
In-Reply-To: <96308D61-00CE-4D93-880E-3B1612F4F4D0@huawei.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops] Agenda scheduling for IETF 79
Thread-Index: ActlYekAz1ycikaKSlCWOOmDKjLQsAAAuZdg
References: <20101001161955.7BE263A6CEF@core3.amsl.com><47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com><1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com><8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com><CB2FC880-934B-4241-905E-D221862EE13F@huawei.com><54BED382-7B8C-4C23-826C-054B31333970@cisco.com><641BFD35-D097-4E22-8A71-F3E75EB7CD4A@huawei.com><C165683A-1C03-415A-806F-674620AB607B@cisco.com><m2aamrraos.wl%randy@psg.com><56DC0013-40B8-4D3A-99E0-B2837302DD70@huawei.com><m28w2br9t0.wl%randy@psg.com><9E025610-B99C-40B3-810F-BFDCD5CAE136@huawei.com><m21v83quyh.wl%randy@psg.com> <96308D61-00CE-4D93-880E-3B1612F4F4D0@huawei.com>
From: "Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com>
To: "Tina TSOU" <tena@huawei.com>
X-OriginalArrivalTime: 06 Oct 2010 14:45:16.0245 (UTC) FILETIME=[17044850:01CB6565]
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 14:44:21 -0000

Deliverables should be technical, concrete and absolute of nature.

Btw, this discussion is not anymore on agenda items. Please change the
title of the tread

G/

-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
Of Tina TSOU
Sent: Wednesday, October 06, 2010 4:21 PM
To: Randy Bush
Cc: IPv6 Operations
Subject: Re: [v6ops] Agenda scheduling for IETF 79


B. R.
Tina
http://tinatsou.weebly.com




On Oct 6, 2010, at 10:03 PM, Randy Bush wrote:

>>> we all do.  and one of mine is that we need to be careful that our
>>> contribution is not exponentially proportional to layer numbers
>>> greater than seven.
>> What does it mean, Randy?
>
> avoid political bs, produce technical content
This is what I tried to avoid, if the problem statement I-D and the =20
use cases I-D and transition guides I-D are technically fine, the =20
problem statement I-D should not block the way of the latter. Perhaps =20
I worry too much. It may not happen.

_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

From fred@cisco.com  Wed Oct  6 08:17:15 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 08DA03A7087 for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 08:17:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.974
X-Spam-Level: 
X-Spam-Status: No, score=-109.974 tagged_above=-999 required=5 tests=[AWL=-0.275, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k8tV3sFEiUaN for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 08:17:12 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 04FE93A7115 for <v6ops@ietf.org>; Wed,  6 Oct 2010 08:17:11 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAI8vrExAZnwM/2dsb2JhbACiRnGoGpwzhUcEhXqDfkiDAg
X-IronPort-AV: E=Sophos;i="4.57,290,1283731200"; d="scan'208";a="167672322"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 06 Oct 2010 15:18:11 +0000
Received: from Freds-Computer.local (rtp-vpn3-1782.cisco.com [10.82.222.253]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o96FI3ew001289; Wed, 6 Oct 2010 15:18:05 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Wed, 06 Oct 2010 11:18:11 -0400
X-PGP-Universal: processed; by Freds-Computer.local on Wed, 06 Oct 2010 11:18:11 -0400
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4CAC88AD.3010901@gont.com.ar>
Date: Wed, 6 Oct 2010 11:17:56 -0400
Message-Id: <8C1CBF9B-3593-4C68-94E3-8B3F2124646A@cisco.com>
References: <D40F684E-2A7B-42E6-ADC4-F4AFDE879FE3@cisco.com> <DC5EA05D-3758-4351-9DB0-A46218482815@cisco.com> <4CAC88AD.3010901@gont.com.ar>
To: Fernando Gont <fernando@gont.com.ar>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>, Dave Thaler <dthaler@microsoft.com>
Subject: Re: [v6ops] =?windows-1252?q?=93ipv6_on_windows_7=94_-_Google_Search?=
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 15:17:15 -0000

On Oct 6, 2010, at 10:33 AM, Fernando Gont wrote:

> Hi, Fred,
>=20
>> Reading over my own email, my comment can be confusing - the
>> getaddrinfo() stuff is in the implementations in question, so it does
>> indeed "have something to do with the implementation". I guess my
>> question is -
>>=20
>> I get questions about operational IPv6 deployment due to issues of
>> implementation. One ISP recently told me that they can't deploy AAAA
>> records for certain services because when their customers are in the
>> region of a neighboring ISP that runs IPv6 as a walled garden and btw
>> respond to connection attempts with a TCP RST, their user's laptops
>> don't correctly fall back to IPv4.=20
>=20
> Note: I do recall checking, years ago, that Windows systems used to
> respond with RST when e.g. the queue of incoming connections was full
> (e.g., the server was under s SYN-flood attack). As a result, RSTs had
> the semantics of "soft errors", rather than "hard errors", and hence
> Windows was being coherent with their own implementation. -- Although
> IMO their behavior was coherent but wrong: RSTs are ment to signal =
hard
> errors... so they shouldn't have been sending RSTs when under a
> SYN-flood attack, and would be aborting connections upon receipt of an =
RST.

Without naming names, the situation is (I'm told) that a certain ISP =
operates its IPv6 network as a walled garden, and replies TCP RST to any =
TCP session that tries to leave the walled garden. One would hope that =
the way they would do that would instead be to have no default route =
within their backbone, but only prefix routes, and configure their =
routers to respond ICMP "you can't get there from here" instead.

>> I can imagine several possible
>> recommendations, and might actually recommend two of them: "happy
>> eyeballs" as Dan Wing describes (open TCP sessions at some rate
>> trying all IPv4 and IPv6 combinations until one of them opens a
>> session, with the objective of achieving an open session within a
>> stated interval such as 1 second or less),=20
>=20
> FWIW, this approach of "parallel connections" was mentioned in at =
least
> some of the I-D versions that led to RFC 5461.

Well, yes, but

   It is worth noting that while most applications try the addresses
   returned by the name-to-address function in serial, this is certainly
   not the only possible approach.  For example, applications could try
   multiple addresses in parallel until one succeeds, possibly avoiding
   the problem of long delays between connection-establishment attempts
   described in this document [Gont].

doesn't have the ring of "getting the connection open within my lifetime =
is important" :-)

> However, keep in mind that this approach of "try all possible =
addresses"
> may put a bit of stress on the servers - particularly those that are
> popular and also have multiple addresses.

Well, yes. And when Netscape started opening four TCP sessions at a =
crack instead of one, people worried about server load then as well. In =
this case, there are a couple of differences. One, the client has the =
option of remembering which address it found useful last time and trying =
it first. Two, while these "bogus" sessions might occupy a TCB for a =
couple of RTTs, it will likely be RST quickly.=20

>> and an operational
>> recommendation that if you're going to run IPv6 as a walled garden,
>> that you configure your first hop routers to respond "host
>> unreachable" or "network unreachable" to any packet that you have
>> decided to not deliver.
>=20
> Specs-wise that wouldn't help. We (other folks and myself) tried to
> pursue RFC5461 as std track... but there was an endless debate on =
tcpm,
> and the I-D ended up targeting the Informational track. Specs-wise,
> these "destination unreachables" indicate soft errors, and thus should
> not cause the connection to be aborted.
>=20
> That said, RFC5461 *has* been implemented in the real world, despite
> tcpm's concerns.
>=20
> Some folks at a japanese telco had mentioned that they had asked a
> (large :-) ) vendor to implement RFC 5461, but they argued that they
> wouldn't, because RFC5461 was not std track.

That may be the point of v6ops making a statement that this is =
important. I won't say "tcpm is a bunch of academics", because that is =
overstating the case, but it's not clear that they have very much =
operational understanding.

>> Would it be appropriate, and would the working group like to discuss,
>> such recommendations?=20
>=20
> The "problem" here is that, in order for such a recommendation to make
> sense, you need to have clients react to those ICMPs by aborting the
> corresponding connection.... and that basically means re-hashing RFC =
5461.

Maybe we need to get them to explain how to open a TCP session in less =
than a minute.

> I guess that if the proposal aims at requiring this behavior *only* =
for
> ICMPv6 (and *not* for ICMPv4), it may have more chances to fly, but...
>=20
> Thoughts?
>=20
> Kind regards,
> --=20
> Fernando Gont
> e-mail: fernando@gont.com.ar || fgont@acm.org
> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
>=20
>=20
>=20
>=20


From tena@huawei.com  Wed Oct  6 08:20:52 2010
Return-Path: <tena@huawei.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3F6E43A6FA9 for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 08:20:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.002
X-Spam-Level: 
X-Spam-Status: No, score=-100.002 tagged_above=-999 required=5 tests=[AWL=-0.107, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UpNdIbFV4eEU for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 08:20:51 -0700 (PDT)
Received: from szxga05-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 0953C3A6F93 for <v6ops@ietf.org>; Wed,  6 Oct 2010 08:20:51 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9V00BPJK04VK@szxga05-in.huawei.com> for v6ops@ietf.org; Wed, 06 Oct 2010 23:21:40 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L9V00IKCK03UQ@szxga05-in.huawei.com> for v6ops@ietf.org; Wed, 06 Oct 2010 23:21:40 +0800 (CST)
Received: from [192.168.5.101] ([113.116.37.175]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L9V00HRXJZUHY@szxml02-in.huawei.com>; Wed, 06 Oct 2010 23:21:39 +0800 (CST)
Date: Wed, 06 Oct 2010 23:21:21 +0800
From: Tina TSOU <tena@huawei.com>
In-reply-to: <4269EA985EACD24987D82DAE2FEC62E50254C801@XMB-AMS-101.cisco.com>
To: "Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com>
Message-id: <B5BA80D4-4E7F-4F53-AD65-404E7692DA6B@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: text/plain; charset=US-ASCII; format=flowed
Content-transfer-encoding: 7BIT
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <54BED382-7B8C-4C23-826C-054B31333970@cisco.com> <641BFD35-D097-4E22-8A71-F3E75EB7CD4A@huawei.com> <C165683A-1C03-415A-806F-674620AB607B@cisco.com> <m2aamrraos.wl%randy@psg.com> <56DC0013-40B8-4D3A-99E0-B2837302DD70@huawei.com> <m28w2br9t0.wl%randy@psg.com> <9E025610-B99C-40B3-810F-BFDCD5CAE136@huawei.com> <m21v83quyh.wl%randy@psg.com> <96308D61-00CE-4D93-880E-3B1612F4F4D0@huawei.com> <4269EA985EACD24987D82DAE2FEC62E50254C801@XMB-AMS-101.cisco.com>
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: [v6ops] v4v6tran was Re:  Agenda scheduling for IETF 79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 15:20:52 -0000

	
B. R.
Tina
http://tinatsou.weebly.com




On Oct 6, 2010, at 10:45 PM, Gunter Van de Velde (gvandeve) wrote:

> Deliverables should be technical, concrete and absolute of nature.
Agreed:)
>
> Btw, this discussion is not anymore on agenda items. Please change the
> title of the tread
Why didn't you change the title? :)
>
> G/
>
> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
> Of Tina TSOU
> Sent: Wednesday, October 06, 2010 4:21 PM
> To: Randy Bush
> Cc: IPv6 Operations
> Subject: Re: [v6ops] Agenda scheduling for IETF 79
>
>
> B. R.
> Tina
> http://tinatsou.weebly.com
>
>
>
>
> On Oct 6, 2010, at 10:03 PM, Randy Bush wrote:
>
>>>> we all do.  and one of mine is that we need to be careful that our
>>>> contribution is not exponentially proportional to layer numbers
>>>> greater than seven.
>>> What does it mean, Randy?
>>
>> avoid political bs, produce technical content
> This is what I tried to avoid, if the problem statement I-D and the
> use cases I-D and transition guides I-D are technically fine, the
> problem statement I-D should not block the way of the latter. Perhaps
> I worry too much. It may not happen.
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From fernando.gont.netbook.win@gmail.com  Wed Oct  6 08:50:09 2010
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0EF463A70E8 for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 08:50:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.089
X-Spam-Level: 
X-Spam-Status: No, score=-2.089 tagged_above=-999 required=5 tests=[AWL=-0.390, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pMKqufNvlgNs for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 08:50:08 -0700 (PDT)
Received: from mail-yx0-f194.google.com (mail-yx0-f194.google.com [209.85.213.194]) by core3.amsl.com (Postfix) with ESMTP id A69533A6FB9 for <v6ops@ietf.org>; Wed,  6 Oct 2010 08:50:07 -0700 (PDT)
Received: by yxj4 with SMTP id 4so2075768yxj.1 for <v6ops@ietf.org>; Wed, 06 Oct 2010 08:51:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=4V8MepVhpO8RI9nDEHqDm4li9r7o6TSSINKFmLFL9Q4=; b=PB47f9W9J4EtbNagVPltClYv3jOhOFiMxYEiaq59XVvDB0qrYP92j2gJ2OiDctxgaw L+22TRfWrDizPfNLZ5G89t7ky36e1HYYzZwHD5Mo6RfDYZfBVwPXk28Zbnoggt3l3mXN sDb7994mMUB2mD5XiZE3RhZtNyBobcl039AqQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=hd/wOR7xjZEWkaKY4PboNjUBSaZV0CD6w/QE0/0uqbOWGuzrAxqPShccmXtEoWVld0 h0babWBJstpK5jTzX6OsDZmXDQlv2PD9KS3JayqwB8HHGTvLNWoSkK2/iGBMTiRlCqW1 EFdmgCdUS7xJGzCTWSFrjC9kXgEQuhjbcP2mU=
Received: by 10.151.28.10 with SMTP id f10mr2144870ybj.94.1286380267356; Wed, 06 Oct 2010 08:51:07 -0700 (PDT)
Received: from [192.168.2.5] ([186.137.79.118]) by mx.google.com with ESMTPS id v34sm1356820yba.7.2010.10.06.08.51.04 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 06 Oct 2010 08:51:06 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4CAC9AE3.1070202@gont.com.ar>
Date: Wed, 06 Oct 2010 12:50:59 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <D40F684E-2A7B-42E6-ADC4-F4AFDE879FE3@cisco.com> <DC5EA05D-3758-4351-9DB0-A46218482815@cisco.com> <4CAC88AD.3010901@gont.com.ar> <8C1CBF9B-3593-4C68-94E3-8B3F2124646A@cisco.com>
In-Reply-To: <8C1CBF9B-3593-4C68-94E3-8B3F2124646A@cisco.com>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, Dave Thaler <dthaler@microsoft.com>
Subject: Re: [v6ops] =?windows-1252?q?=93ipv6_on_windows_7=94_-_Google_Search?=
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 15:50:09 -0000

Hi, Fred,

> Without naming names, the situation is (I'm told) that a certain ISP
> operates its IPv6 network as a walled garden, and replies TCP RST to
> any TCP session that tries to leave the walled garden. One would hope
> that the way they would do that would instead be to have no default
> route within their backbone, but only prefix routes, and configure
> their routers to respond ICMP "you can't get there from here"
> instead.

As noted in my previous e-mail, specs-wise those ICMPs wouldn't help
(they are supposed to indicate soft errors). I would argue that if they
do respond with RSTs, the client should be aborting those connections!



>> FWIW, this approach of "parallel connections" was mentioned in at
>> least some of the I-D versions that led to RFC 5461.
> 
> Well, yes, but
> 
> It is worth noting that while most applications try the addresses 
> returned by the name-to-address function in serial, this is
> certainly not the only possible approach.  For example, applications
> could try multiple addresses in parallel until one succeeds, possibly
> avoiding the problem of long delays between connection-establishment
> attempts described in this document [Gont].
> 
> doesn't have the ring of "getting the connection open within my
> lifetime is important" :-)

Agreed. Although the studies referenced on the responsiveness impact on
users' happiness should be a hint ;-)



>>> Would it be appropriate, and would the working group like to
>>> discuss, such recommendations?
>> 
>> The "problem" here is that, in order for such a recommendation to
>> make sense, you need to have clients react to those ICMPs by
>> aborting the corresponding connection.... and that basically means
>> re-hashing RFC 5461.
> 
> Maybe we need to get them to explain how to open a TCP session in
> less than a minute.

I will tell you the answer that you'll most likely get:

"TCP is not designed with such performance considerations in mind"

-- skim through the discussions related to "ICMP attacks against TCP",
and you'll see that this could be actually worse (see e.g.:
http://www.ietf.org/mail-archive/web/tcpm/current/msg04884.html)

All the above said, it's clear that there is a real problem to solve,
and I do think that it would be a good idea that v6ops does something
about this.

So, being pragmatic: what (specifically) do you have in mind, other than
describing the problem in an I-D? -- i.e., I guess that they'll argue
that it's not v6ops that should make recommendations as to how a TCP
implementation should respond to icmp error messages...

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





From fred@cisco.com  Wed Oct  6 09:12:06 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF41E3A7147 for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 09:12:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.962
X-Spam-Level: 
X-Spam-Status: No, score=-109.962 tagged_above=-999 required=5 tests=[AWL=-0.263, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1PuzFbgRnecY for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 09:12:04 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 970103A719A for <v6ops@ietf.org>; Wed,  6 Oct 2010 09:11:33 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.57,290,1283731200"; d="scan'208";a="167690603"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 06 Oct 2010 16:12:27 +0000
Received: from Freds-Computer.local (rtp-vpn3-1782.cisco.com [10.82.222.253]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o96GCJMk022034; Wed, 6 Oct 2010 16:12:22 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Wed, 06 Oct 2010 12:12:27 -0400
X-PGP-Universal: processed; by Freds-Computer.local on Wed, 06 Oct 2010 12:12:27 -0400
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4CAC9AE3.1070202@gont.com.ar>
Date: Wed, 6 Oct 2010 12:12:12 -0400
Message-Id: <E977F4D3-FAE1-4007-93ED-2ABD10F408F0@cisco.com>
References: <D40F684E-2A7B-42E6-ADC4-F4AFDE879FE3@cisco.com> <DC5EA05D-3758-4351-9DB0-A46218482815@cisco.com> <4CAC88AD.3010901@gont.com.ar> <8C1CBF9B-3593-4C68-94E3-8B3F2124646A@cisco.com> <4CAC9AE3.1070202@gont.com.ar>
To: Fernando Gont <fernando@gont.com.ar>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>, Dave Thaler <dthaler@microsoft.com>
Subject: Re: [v6ops] =?windows-1252?q?=93ipv6_on_windows_7=94_-_Google_Search?=
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 16:12:06 -0000

On Oct 6, 2010, at 11:50 AM, Fernando Gont wrote:

> All the above said, it's clear that there is a real problem to solve,
> and I do think that it would be a good idea that v6ops does something
> about this.
>=20
> So, being pragmatic: what (specifically) do you have in mind, other =
than
> describing the problem in an I-D? -- i.e., I guess that they'll argue
> that it's not v6ops that should make recommendations as to how a TCP
> implementation should respond to icmp error messages...

Per our charter, we can produce operational solutions, and we can =
deliver requirements to other working groups. I personally think that a =
statement by v6ops that your RFC and the Happy Eyeballs draft are both =
things the operators would like to see widely deployed would be a good =
thing.

If tcpm is going to dismiss the two as "we don't design TCP to be used =
in the operational Internet", then having an operational group say =
"here's how to use TCP in an operational internet" is not out of bounds. =
tcmp has vacated the field in favor of its ivory tower.=

From fred@cisco.com  Wed Oct  6 12:32:35 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 781C73A70C3; Wed,  6 Oct 2010 12:32:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.999
X-Spam-Level: 
X-Spam-Status: No, score=-109.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h7y5-Tph9em6; Wed,  6 Oct 2010 12:32:34 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id DE96B3A71F8; Wed,  6 Oct 2010 12:32:33 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAAdsrExAZnwM/2dsb2JhbACiTXGqE5xAhUcEikCDAg
X-IronPort-AV: E=Sophos;i="4.57,292,1283731200"; d="scan'208";a="167556171"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 06 Oct 2010 19:33:34 +0000
Received: from dhcp-64-100-223-31.cisco.com (dhcp-64-100-223-31.cisco.com [64.100.223.31]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o96JXQwU004020; Wed, 6 Oct 2010 19:33:29 GMT
Received: from [127.0.0.1] by dhcp-64-100-223-31.cisco.com (PGP Universal service); Wed, 06 Oct 2010 15:33:34 -0400
X-PGP-Universal: processed; by dhcp-64-100-223-31.cisco.com on Wed, 06 Oct 2010 15:33:34 -0400
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
Date: Wed, 6 Oct 2010 15:33:20 -0400
Message-Id: <FE7805F0-B3FB-49BF-8C28-CED2CFEA3F0E@cisco.com>
References: <20101006191804.9D1853A71C0@core3.amsl.com>
To: IPv6 Operations <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: ops-dir@ietf.org
Subject: [v6ops] Fwd: New Version Notification for draft-baker-v6ops-session-start-time-00
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 19:32:35 -0000

If I get enough people telling me they agree with this, I'll send it off =
to random ADs and WG Chairs as an internet draft and ask for time to =
discuss it in their working groups in Beijing, and not occupy v6ops time =
with it. If you don't comment, I'll bore you to tears with it in the =
meeting :-)

It's short. The important bits fit on a bit over a page. The important =
references are:
  =20
http://www.ietf.org/rfc/rfc5461.txt
5461 TCP's Reaction to Soft Errors. F. Gont. February 2009.=20
     (Format: TXT=3D31749 bytes) (Status: INFORMATIONAL)

and

http://tools.ietf.org/id/draft-wing-http-new-tech
     Wing, D., Yourtchenko, A., and P. Natarajan, "Happy
     Eyeballs: Trending Towards Success (IPv6 and SCTP)",
     August 2010.

Begin forwarded message:

> From: IETF I-D Submission Tool <idsubmission@ietf.org>
> Date: October 6, 2010 3:18:04 PM EDT
> To: fred@cisco.com
> Subject: New Version Notification for =
draft-baker-v6ops-session-start-time-00=20
>=20
>=20
> A new version of I-D, draft-baker-v6ops-session-start-time-00.txt has =
been successfully submitted by Fred Baker and posted to the IETF =
repository.
>=20
> Filename:	 draft-baker-v6ops-session-start-time
> Revision:	 00
> Title:		 Opening TCP Sessions in Complex Environments
> Creation_date:	 2010-10-06
> WG ID:		 Independent Submission
> Number_of_pages: 5
>=20
> Abstract:
> A barrier to the deployment of IPv6 is the amount of time it takes to
> open a session using common transport APIs.  This note addresses
> issues and requests solutions that may respond to them.
>=20
>=20
>=20
> The IETF Secretariat.
>=20
>=20


From scott.brim@gmail.com  Wed Oct  6 13:24:25 2010
Return-Path: <scott.brim@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2B21D3A7117; Wed,  6 Oct 2010 13:24:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.557
X-Spam-Level: 
X-Spam-Status: No, score=-102.557 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rsqi+vsy-tMC; Wed,  6 Oct 2010 13:24:24 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 326BD3A700E; Wed,  6 Oct 2010 13:24:24 -0700 (PDT)
Received: by vws10 with SMTP id 10so173969vws.31 for <multiple recipients>; Wed, 06 Oct 2010 13:25:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=1y4AL92bXgq4rRXy6y+yXIMwtXfxBgxuVcQJO6sztwA=; b=cciDujPGfHU22Xf+a1mYD8WYAxtndoeimger+juRljSaLEOSL3++aeS1g7MVOb1pXc EwmBSZGp2XK4vDjwjkUv7SNEgXwl+gAORN/Mt99RiZzMQ5MRcocN+4TGDsivuP7QYvt1 XfjCq/+qDZ1AZ4y4UJAknglV6wV8ZCATuCypY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=GmEsOUI46uTO5+QF/JA0WgYxVy3TmHMs7tw5Sqp8nGJiWKcNKRaPoAgHFoDEi6zMI0 HavlntYxl14Az86c3gkdufVgtSRMX1/3vd1B5hvciBiD/iNi3I+8Ajwp4fpr54aZceZ0 7e6Xb7BGHpOPYM1bj32qctxxk7IwAxHQEDGnM=
Received: by 10.220.199.193 with SMTP id et1mr919046vcb.56.1286396724748; Wed, 06 Oct 2010 13:25:24 -0700 (PDT)
Received: from sbrim-mbp.local (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id w1sm1529995vbl.18.2010.10.06.13.25.22 (version=SSLv3 cipher=RC4-MD5); Wed, 06 Oct 2010 13:25:23 -0700 (PDT)
Message-ID: <4CACDB32.8010900@gmail.com>
Date: Wed, 06 Oct 2010 16:25:22 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <20101006191804.9D1853A71C0@core3.amsl.com> <FE7805F0-B3FB-49BF-8C28-CED2CFEA3F0E@cisco.com>
In-Reply-To: <FE7805F0-B3FB-49BF-8C28-CED2CFEA3F0E@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, ops-dir@ietf.org
Subject: Re: [v6ops] Fwd: New Version Notification for draft-baker-v6ops-session-start-time-00
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 20:24:25 -0000

IMHO -> TSVAREA.  It's not about IPv6 or even IP, it's about
establishing transport connections.

From ipng@69706e6720323030352d30312d31340a.nosense.org  Wed Oct  6 13:55:29 2010
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2D8FD3A7264 for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 13:55:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.68
X-Spam-Level: 
X-Spam-Status: No, score=-0.68 tagged_above=-999 required=5 tests=[AWL=-0.808,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_SORBS_DUL=0.877, SARE_SUB_ENC_UTF8x2=0.246]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YVBy++n26UNf for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 13:55:28 -0700 (PDT)
Received: from smtp2.adam.net.au (smtp2.adam.net.au [202.136.110.251]) by core3.amsl.com (Postfix) with ESMTP id D81953A7263 for <v6ops@ietf.org>; Wed,  6 Oct 2010 13:55:27 -0700 (PDT)
Received: from 219-90-235-115.ip.adam.com.au ([219.90.235.115] helo=opy.nosense.org) by smtp2.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1P3b2H-0003bD-Ei; Thu, 07 Oct 2010 07:26:25 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id DE0F03B31E; Thu,  7 Oct 2010 07:26:24 +1030 (CST)
Date: Thu, 7 Oct 2010 07:26:23 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Fred Baker <fred@cisco.com>
Message-ID: <20101007072623.7be3507e@opy.nosense.org>
In-Reply-To: <DC5EA05D-3758-4351-9DB0-A46218482815@cisco.com>
References: <D40F684E-2A7B-42E6-ADC4-F4AFDE879FE3@cisco.com> <DC5EA05D-3758-4351-9DB0-A46218482815@cisco.com>
X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, Dave Thaler <dthaler@microsoft.com>
Subject: Re: [v6ops] =?utf-8?q?=E2=80=9Cipv6_on_windows_7=E2=80=9D_-_Google_Se?= =?utf-8?q?arch?=
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 20:55:29 -0000

Hi Fred,

On Wed, 6 Oct 2010 09:14:28 -0400
Fred Baker <fred@cisco.com> wrote:

> > It would be interesting to understand what the issue is here. I suspect it has nothing to do with the actual Windows (or Apple, Linux, etc) implementation, but is more related to issues as discussed in http://tools.ietf.org/html/draft-wing-http-new-tech. Would it make sense for v6ops to make a recommendation to address the concerns?
> 
> Reading over my own email, my comment can be confusing - the getaddrinfo() stuff is in the implementations in question, so it does indeed "have something to do with the implementation". I guess my question is - 
> 
> I get questions about operational IPv6 deployment due to issues of implementation. One ISP recently told me that they can't deploy AAAA records for certain services because when their customers are in the region of a neighboring ISP that runs IPv6 as a walled garden and btw respond to connection attempts with a TCP RST, their user's laptops don't correctly fall back to IPv4. I can imagine several possible recommendations, and might actually recommend two of them: "happy eyeballs" as Dan Wing describes (open TCP sessions at some rate trying all IPv4 and IPv6 combinations until one of them opens a session, with the objective of achieving an open session within a stated interval such as 1 second or less), and an operational recommendation that if you're going to run IPv6 as a walled garden, that you configure your first hop routers to respond "host unreachable" or "network unreachable" to any packet that you have decided to not deliver.
 
A while back I converted an application to use getaddrinfo(), and
the advice in the manual page, when there were multiple A/AAAA
responses, was to walk through them all, in order and in turn,
attempting to connect(). If connect() failed, regardless of the
cause e.g. timeout or connect refused, move on to the next result of
the getaddrinfo() call.

Some advice in regards to how getaddrinfo() should be used might be
useful, although I wonder if it would be better placed in an update to
one of the IPv6 socket API RFCs. Some text relating to the use of
getaddrinfo() (an an appendix possibly) in an update to the source
address selection RFC probably wouldn't hurt though.

I can't really see why this 'walled garden' ISP is responding with TCP
resets though. I'd have thought it would be more customer friendly
(more "garden like") to send an connection attempts to
unknown/unavailable destinations towards something like a wildcarding
web server.

Regards,
Mark.

From edward.jankiewicz@sri.com  Wed Oct  6 14:53:34 2010
Return-Path: <edward.jankiewicz@sri.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A9683A705D for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 14:53:34 -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=0.214,  BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ogG5t2-giQjD for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 14:53:33 -0700 (PDT)
Received: from mail1.sri.com (mail1.SRI.COM [128.18.30.17]) by core3.amsl.com (Postfix) with ESMTP id 6A61E3A6FA2 for <v6ops@ietf.org>; Wed,  6 Oct 2010 14:53:33 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Received: from [192.168.1.144] ([unknown] [68.81.23.3]) by mail.sri.com (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0L9W00NZY26WRKC0@mail.sri.com> for v6ops@ietf.org; Wed, 06 Oct 2010 14:54:32 -0700 (PDT)
Message-id: <4CACF016.8030706@sri.com>
Date: Wed, 06 Oct 2010 17:54:30 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
To: v6ops@ietf.org
References: <20101006191804.9D1853A71C0@core3.amsl.com> <FE7805F0-B3FB-49BF-8C28-CED2CFEA3F0E@cisco.com>
In-reply-to: <FE7805F0-B3FB-49BF-8C28-CED2CFEA3F0E@cisco.com>
Subject: Re: [v6ops] Fwd: New Version Notification for	draft-baker-v6ops-session-start-time-00
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 21:53:34 -0000

  It seems prudent to post this draft as a question to intarea and 
tsvarea as suggested, and see what area would take it up.  Also apparea 
where Happy Eyeballs is under discussion.  Seems that tsvarea (tcpm) 
would be appropriate forum to discuss taking RFC 5461 approach to standard.


On 10/6/2010 3:33 PM, Fred Baker wrote:
> If I get enough people telling me they agree with this, I'll send it off to random ADs and WG Chairs as an internet draft and ask for time to discuss it in their working groups in Beijing, and not occupy v6ops time with it. If you don't comment, I'll bore you to tears with it in the meeting :-)
>
> It's short. The important bits fit on a bit over a page. The important references are:
>
> http://www.ietf.org/rfc/rfc5461.txt
> 5461 TCP's Reaction to Soft Errors. F. Gont. February 2009.
>       (Format: TXT=31749 bytes) (Status: INFORMATIONAL)
>
> and
>
> http://tools.ietf.org/id/draft-wing-http-new-tech
>       Wing, D., Yourtchenko, A., and P. Natarajan, "Happy
>       Eyeballs: Trending Towards Success (IPv6 and SCTP)",
>       August 2010.
>
> Begin forwarded message:
>
>> From: IETF I-D Submission Tool<idsubmission@ietf.org>
>> Date: October 6, 2010 3:18:04 PM EDT
>> To: fred@cisco.com
>> Subject: New Version Notification for draft-baker-v6ops-session-start-time-00
>>
>>
>> A new version of I-D, draft-baker-v6ops-session-start-time-00.txt has been successfully submitted by Fred Baker and posted to the IETF repository.
>>
>> Filename:	 draft-baker-v6ops-session-start-time
>> Revision:	 00
>> Title:		 Opening TCP Sessions in Complex Environments
>> Creation_date:	 2010-10-06
>> WG ID:		 Independent Submission
>> Number_of_pages: 5
>>
>> Abstract:
>> A barrier to the deployment of IPv6 is the amount of time it takes to
>> open a session using common transport APIs.  This note addresses
>> issues and requests solutions that may respond to them.
>>
>>
>>
>> The IETF Secretariat.
>>
>>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

-- 
Ed Jankiewicz - SRI International
Fort Monmouth Branch Office - IPv6 Research
Supporting DISA Standards Engineering Branch
732-389-1003 or  ed.jankiewicz@sri.com


From brian.e.carpenter@gmail.com  Wed Oct  6 15:30:55 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E266E3A71D7; Wed,  6 Oct 2010 15:30:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.295
X-Spam-Level: 
X-Spam-Status: No, score=-102.295 tagged_above=-999 required=5 tests=[AWL=-0.296, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QYaui9zl3olh; Wed,  6 Oct 2010 15:30:54 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 499703A7059; Wed,  6 Oct 2010 15:30:51 -0700 (PDT)
Received: by vws10 with SMTP id 10so65983vws.31 for <multiple recipients>; Wed, 06 Oct 2010 15:31:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=s6aW/jnqZiIYkD+Ndokml++cQgHI9YWDt412FxmZIdw=; b=Z7iJJBLvE5A5uAmxMAZaOJpEMZ6tXsdCGyMYAzPxvJL2CQvjKWl25xphjbLaTXK+jG vPDnat4jVOeFzH0RUbk/ckErttB93djlvkuwMHvBbKnsbCtv43/9VXyo+QVZvygELTim U82Q9E2FNgxK/U4l34+Gcw0B8BgKaNNbPR6jE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=e32NxGGL8Y/ok8/rJqyxT/u2vMKCFdVMTVkMZulEtxuo+P5ihpUJqTc5kIBvsF4j9c mGWTYni1HFM71M0z04pqKBSiLFIWgPA1tqxiYqOXvnz3x3AZbdAtrocdLkdsGa7BJGvQ fqXiqEVOyeC5IlK/DskRuwluaqhaymURmZJ1A=
Received: by 10.220.176.130 with SMTP id be2mr956110vcb.205.1286404304778; Wed, 06 Oct 2010 15:31:44 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id l9sm1610954vbp.11.2010.10.06.15.31.41 (version=SSLv3 cipher=RC4-MD5); Wed, 06 Oct 2010 15:31:43 -0700 (PDT)
Message-ID: <4CACF8CB.9080106@gmail.com>
Date: Thu, 07 Oct 2010 11:31:39 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <20101006191804.9D1853A71C0@core3.amsl.com> <FE7805F0-B3FB-49BF-8C28-CED2CFEA3F0E@cisco.com>
In-Reply-To: <FE7805F0-B3FB-49BF-8C28-CED2CFEA3F0E@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, ops-dir@ietf.org
Subject: Re: [v6ops] Fwd: New Version Notification for draft-baker-v6ops-session-start-time-00
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2010 22:30:56 -0000

I need to point out that there is closely related standards text,
code, and experience in REAP (RFC5534). Although REAP was designed
as part of shim6, it's relatively separable if need be.

It also scales quite well, and tells us something about how long
trying out alternate paths will take in practice. The following
paper covers this, as well as how much is to be gained by
trying out alternate paths in parallel (see the section on
sending initial probes concurrently).
http://www.cs.auckland.ac.nz/~brian/iccnt2010_reap.pdf
(from ICCNT 2010 conference).

Regards
   Brian Carpenter

On 2010-10-07 08:33, Fred Baker wrote:
> If I get enough people telling me they agree with this, I'll send it off to random ADs and WG Chairs as an internet draft and ask for time to discuss it in their working groups in Beijing, and not occupy v6ops time with it. If you don't comment, I'll bore you to tears with it in the meeting :-)
> 
> It's short. The important bits fit on a bit over a page. The important references are:
>    
> http://www.ietf.org/rfc/rfc5461.txt
> 5461 TCP's Reaction to Soft Errors. F. Gont. February 2009. 
>      (Format: TXT=31749 bytes) (Status: INFORMATIONAL)
> 
> and
> 
> http://tools.ietf.org/id/draft-wing-http-new-tech
>      Wing, D., Yourtchenko, A., and P. Natarajan, "Happy
>      Eyeballs: Trending Towards Success (IPv6 and SCTP)",
>      August 2010.
> 
> Begin forwarded message:
> 
>> From: IETF I-D Submission Tool <idsubmission@ietf.org>
>> Date: October 6, 2010 3:18:04 PM EDT
>> To: fred@cisco.com
>> Subject: New Version Notification for draft-baker-v6ops-session-start-time-00 
>>
>>
>> A new version of I-D, draft-baker-v6ops-session-start-time-00.txt has been successfully submitted by Fred Baker and posted to the IETF repository.
>>
>> Filename:	 draft-baker-v6ops-session-start-time
>> Revision:	 00
>> Title:		 Opening TCP Sessions in Complex Environments
>> Creation_date:	 2010-10-06
>> WG ID:		 Independent Submission
>> Number_of_pages: 5
>>
>> Abstract:
>> A barrier to the deployment of IPv6 is the amount of time it takes to
>> open a session using common transport APIs.  This note addresses
>> issues and requests solutions that may respond to them.
>>
>>
>>
>> The IETF Secretariat.
>>
>>
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> 

From fernando.gont.netbook.win@gmail.com  Wed Oct  6 17:12:58 2010
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D84923A6EAC; Wed,  6 Oct 2010 17:12:58 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kH2YjyUTOdy4; Wed,  6 Oct 2010 17:12:57 -0700 (PDT)
Received: from mail-gy0-f194.google.com (mail-gy0-f194.google.com [209.85.160.194]) by core3.amsl.com (Postfix) with ESMTP id 43B753A6D97; Wed,  6 Oct 2010 17:12:57 -0700 (PDT)
Received: by gyg13 with SMTP id 13so18018gyg.1 for <multiple recipients>; Wed, 06 Oct 2010 17:13:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=WtR5ZMnq5sxeUOTxw//exDu6C19tOovwQkBj9IEQpgQ=; b=GgdGa33M+VLgs5DRSr0WveoDWjjqQfwSFIPDkvNZMk9q0RbKvSwnem2RmhmYXMfwYY FFvZCz0Let+eqYQlFBbmo99QDqfYaklwGXv9Fj2Dd3m2AkDrppJkS4A2X3htqHj0D4os ORB1tjqxytj6DkOgggidAe5bwxRjssS/U6Bfk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=oPuI0SPANA7dDXXcT/8VbPQKFNiIZWAh0lVIJ+ghs1rZD4bGs/jyZ0Zgjj13LUT+da IiJ/CMtqlm0mQraFjZjRQk9qm35BS3LLnKAXbVyKsbTDXSk6Q/LRSBbGAy9ypD/IoAK/ GzLhn2IuGO/SKevf3OBjKyBI5rbgtFszxqIQ0=
Received: by 10.236.103.17 with SMTP id e17mr14412015yhg.89.1286410436958; Wed, 06 Oct 2010 17:13:56 -0700 (PDT)
Received: from [192.168.0.122] (61-128-17-190.fibertel.com.ar [190.17.128.61]) by mx.google.com with ESMTPS id y64sm708792yhc.14.2010.10.06.17.13.54 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 06 Oct 2010 17:13:56 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4CACEFDD.5030608@gont.com.ar>
Date: Wed, 06 Oct 2010 18:53:33 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <20101006191804.9D1853A71C0@core3.amsl.com> <FE7805F0-B3FB-49BF-8C28-CED2CFEA3F0E@cisco.com>
In-Reply-To: <FE7805F0-B3FB-49BF-8C28-CED2CFEA3F0E@cisco.com>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, ops-dir@ietf.org
Subject: Re: [v6ops] Fwd: New Version Notification for	draft-baker-v6ops-session-start-time-00
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2010 00:12:59 -0000

Hi, Fred,

FWIW, I agree with this.

Thanks,
Fernando




On 06/10/2010 04:33 p.m., Fred Baker wrote:
> If I get enough people telling me they agree with this, I'll send it off to random ADs and WG Chairs as an internet draft and ask for time to discuss it in their working groups in Beijing, and not occupy v6ops time with it. If you don't comment, I'll bore you to tears with it in the meeting :-)
> 
> It's short. The important bits fit on a bit over a page. The important references are:
>    
> http://www.ietf.org/rfc/rfc5461.txt
> 5461 TCP's Reaction to Soft Errors. F. Gont. February 2009. 
>      (Format: TXT=31749 bytes) (Status: INFORMATIONAL)
> 
> and
> 
> http://tools.ietf.org/id/draft-wing-http-new-tech
>      Wing, D., Yourtchenko, A., and P. Natarajan, "Happy
>      Eyeballs: Trending Towards Success (IPv6 and SCTP)",
>      August 2010.
> 
> Begin forwarded message:
> 
>> From: IETF I-D Submission Tool <idsubmission@ietf.org>
>> Date: October 6, 2010 3:18:04 PM EDT
>> To: fred@cisco.com
>> Subject: New Version Notification for draft-baker-v6ops-session-start-time-00 
>>
>>
>> A new version of I-D, draft-baker-v6ops-session-start-time-00.txt has been successfully submitted by Fred Baker and posted to the IETF repository.
>>
>> Filename:	 draft-baker-v6ops-session-start-time
>> Revision:	 00
>> Title:		 Opening TCP Sessions in Complex Environments
>> Creation_date:	 2010-10-06
>> WG ID:		 Independent Submission
>> Number_of_pages: 5
>>
>> Abstract:
>> A barrier to the deployment of IPv6 is the amount of time it takes to
>> open a session using common transport APIs.  This note addresses
>> issues and requests solutions that may respond to them.
>>
>>
>>
>> The IETF Secretariat.
>>
>>
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> 

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





From fred@cisco.com  Wed Oct  6 17:35:53 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 64AEB3A6F40; Wed,  6 Oct 2010 17:35:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.082
X-Spam-Level: 
X-Spam-Status: No, score=-110.082 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W494rS1lCDrK; Wed,  6 Oct 2010 17:35:49 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 802593A6ECF; Wed,  6 Oct 2010 17:35:48 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAFeyrExAZnwM/2dsb2JhbACiUXGpeZwuhUcEikCDAg
X-IronPort-AV: E=Sophos;i="4.57,294,1283731200"; d="scan'208";a="167639300"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 07 Oct 2010 00:36:46 +0000
Received: from Freds-Computer.local (rtp-vpn2-1802.cisco.com [10.82.247.13]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o970acBp003981; Thu, 7 Oct 2010 00:36:41 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Wed, 06 Oct 2010 20:36:46 -0400
X-PGP-Universal: processed; by Freds-Computer.local on Wed, 06 Oct 2010 20:36:46 -0400
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4CACF8CB.9080106@gmail.com>
Date: Wed, 6 Oct 2010 20:36:32 -0400
Message-Id: <FE29EAB9-E059-4057-AE93-1BF6307C9AA9@cisco.com>
References: <20101006191804.9D1853A71C0@core3.amsl.com> <FE7805F0-B3FB-49BF-8C28-CED2CFEA3F0E@cisco.com> <4CACF8CB.9080106@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>, ops-dir@ietf.org
Subject: Re: [v6ops] Fwd: New Version Notification for draft-baker-v6ops-session-start-time-00
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2010 00:35:53 -0000

Thanks.

On Oct 6, 2010, at 6:31 PM, Brian E Carpenter wrote:

> I need to point out that there is closely related standards text,
> code, and experience in REAP (RFC5534). Although REAP was designed
> as part of shim6, it's relatively separable if need be.
>=20
> It also scales quite well, and tells us something about how long
> trying out alternate paths will take in practice. The following
> paper covers this, as well as how much is to be gained by
> trying out alternate paths in parallel (see the section on
> sending initial probes concurrently).
> http://www.cs.auckland.ac.nz/~brian/iccnt2010_reap.pdf
> (from ICCNT 2010 conference).
>=20
> Regards
>   Brian Carpenter
>=20
> On 2010-10-07 08:33, Fred Baker wrote:
>> If I get enough people telling me they agree with this, I'll send it =
off to random ADs and WG Chairs as an internet draft and ask for time to =
discuss it in their working groups in Beijing, and not occupy v6ops time =
with it. If you don't comment, I'll bore you to tears with it in the =
meeting :-)
>>=20
>> It's short. The important bits fit on a bit over a page. The =
important references are:
>>=20
>> http://www.ietf.org/rfc/rfc5461.txt
>> 5461 TCP's Reaction to Soft Errors. F. Gont. February 2009.=20
>>     (Format: TXT=3D31749 bytes) (Status: INFORMATIONAL)
>>=20
>> and
>>=20
>> http://tools.ietf.org/id/draft-wing-http-new-tech
>>     Wing, D., Yourtchenko, A., and P. Natarajan, "Happy
>>     Eyeballs: Trending Towards Success (IPv6 and SCTP)",
>>     August 2010.
>>=20
>> Begin forwarded message:
>>=20
>>> From: IETF I-D Submission Tool <idsubmission@ietf.org>
>>> Date: October 6, 2010 3:18:04 PM EDT
>>> To: fred@cisco.com
>>> Subject: New Version Notification for =
draft-baker-v6ops-session-start-time-00=20
>>>=20
>>>=20
>>> A new version of I-D, draft-baker-v6ops-session-start-time-00.txt =
has been successfully submitted by Fred Baker and posted to the IETF =
repository.
>>>=20
>>> Filename:	 draft-baker-v6ops-session-start-time
>>> Revision:	 00
>>> Title:		 Opening TCP Sessions in Complex Environments
>>> Creation_date:	 2010-10-06
>>> WG ID:		 Independent Submission
>>> Number_of_pages: 5
>>>=20
>>> Abstract:
>>> A barrier to the deployment of IPv6 is the amount of time it takes =
to
>>> open a session using common transport APIs.  This note addresses
>>> issues and requests solutions that may respond to them.
>>>=20
>>>=20
>>>=20
>>> The IETF Secretariat.
>>>=20
>>>=20
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>>=20


From scott.brim@gmail.com  Wed Oct  6 19:22:54 2010
Return-Path: <scott.brim@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC3C73A6D54; Wed,  6 Oct 2010 19:22:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.258
X-Spam-Level: 
X-Spam-Status: No, score=-102.258 tagged_above=-999 required=5 tests=[AWL=-0.259, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TNMu75dIhoGT; Wed,  6 Oct 2010 19:22:53 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 941673A6CDC; Wed,  6 Oct 2010 19:22:53 -0700 (PDT)
Received: by vws10 with SMTP id 10so167640vws.31 for <multiple recipients>; Wed, 06 Oct 2010 19:23:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=KsvkjZ/j7ElBm8OFQq5icxpV4JIkOXIb+pz0Hr5sPrs=; b=q4kpBLlrNMrpJubp/+eu+7lYCgu8kL2h3RSHwN7+3+GbJ875gwPqFjOSkveZ2mbvjI Se7fHlLlppa2WjYcjaS3uKQGz3Gaf8nU7+BzgTy6s1GpqkvexhOlOXnEGQUEEZzDzRnM l9rHhaOToIlUrOhu1TowHg8ZQKnILdwdtaiJQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=v795Assm35PSJ2ua5oPFnRBMVoFu7LyPu4idcNkRPDkxqgO51AukDS6YawlBPCTEoy FGj1ZAUPl6aaeQBg6i0DznCcmoMm6Z/fHnRsh+tHioK2zNv5rhZBhaxpncGixRU4wU07 UVeOpt8NhzhMwlK/KVFJLPhF1ATn6xUV4yblw=
Received: by 10.220.167.194 with SMTP id r2mr52117vcy.247.1286418234572; Wed, 06 Oct 2010 19:23:54 -0700 (PDT)
Received: from sbrim-mbp0.local (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id r15sm1694815vbp.0.2010.10.06.19.23.52 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 06 Oct 2010 19:23:53 -0700 (PDT)
Message-ID: <4CAD2F36.4060409@gmail.com>
Date: Wed, 06 Oct 2010 22:23:50 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <20101006191804.9D1853A71C0@core3.amsl.com>	<FE7805F0-B3FB-49BF-8C28-CED2CFEA3F0E@cisco.com> <4CACF8CB.9080106@gmail.com>
In-Reply-To: <4CACF8CB.9080106@gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, ops-dir@ietf.org
Subject: Re: [v6ops] Fwd: New Version Notification for draft-baker-v6ops-session-start-time-00
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2010 02:22:54 -0000

Brian E Carpenter allegedly wrote on 10/06/2010 18:31 EDT:
> I need to point out that there is closely related standards text,
> code, and experience in REAP (RFC5534). 

(getting out of scope for v6ops but since we're here ...)

REAP is focused on failure recovery and parsimonious probing, while the
happy eyeballs issue is configuring and caching connectivity results at
multiple layers (v4, v6, different transport protocols) so the endpoints
can quickly establish a connection that is likely to be useful.

> Although REAP was designed
> as part of shim6, it's relatively separable if need be.

Good because Shim6 doesn't look like it's taking over the Internet :-p

> It also scales quite well, and tells us something about how long
> trying out alternate paths will take in practice.

I don't recall if you saw my slides from Dagstuhl in early 2009, but
everything you can accomplish with REAP and alternate paths you can do
at least as well with concurrent multipath transport (SCTP, MPTCP).

See you soon ... Scott

From brian.e.carpenter@gmail.com  Wed Oct  6 19:34:22 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AB4333A6D54; Wed,  6 Oct 2010 19:34:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.293
X-Spam-Level: 
X-Spam-Status: No, score=-102.293 tagged_above=-999 required=5 tests=[AWL=-0.294, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sCELGo5UIpav; Wed,  6 Oct 2010 19:34:21 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id 3B35C3A6FFA; Wed,  6 Oct 2010 19:34:21 -0700 (PDT)
Received: by yxl31 with SMTP id 31so119035yxl.31 for <multiple recipients>; Wed, 06 Oct 2010 19:35:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=wvnrulLj2m6e6lSt0TTs9N6wAhkf29EKgj5M/6LYVao=; b=l64ZpPl2xE3JgyGMa1oJMxUt/gBCoKiyffmfa6lrphTWFZl8UlTLF+TOie6egyuI6M sMGysfxX9NDh4UO97tXk+Gu439uaPBCeOKoVPkbL4X07VIoBZM05JL4K/I2uTEKbvcwh buvoKve12R8KdPHA4GSg2ZGtyNxLp9fRWZvH8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=u5JWvA6qzrj3fBsza1IhaJTJlTjTyGZ2D1aDGm1it18RFzxD87kkXq2y0U3947Czcj hgpmjWLFtITVCLeIKDFdG6uwQ5foefAm3rRlvR+oH+cmu3AthwRLkJL/iU5Ldzfsic69 +TqRtnCuAUzrm3nrwQ0n+quO0dpsKZEdbiv+U=
Received: by 10.150.178.13 with SMTP id a13mr223143ybf.253.1286418922331; Wed, 06 Oct 2010 19:35:22 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id q14sm1506521ybk.7.2010.10.06.19.35.19 (version=SSLv3 cipher=RC4-MD5); Wed, 06 Oct 2010 19:35:21 -0700 (PDT)
Message-ID: <4CAD31D5.3050707@gmail.com>
Date: Thu, 07 Oct 2010 15:35:01 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
References: <20101006191804.9D1853A71C0@core3.amsl.com>	<FE7805F0-B3FB-49BF-8C28-CED2CFEA3F0E@cisco.com> <4CACF8CB.9080106@gmail.com> <4CAD2F36.4060409@gmail.com>
In-Reply-To: <4CAD2F36.4060409@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, ops-dir@ietf.org
Subject: Re: [v6ops] Fwd: New Version Notification for draft-baker-v6ops-session-start-time-00
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2010 02:34:23 -0000

On 2010-10-07 15:23, Scott Brim wrote:
> Brian E Carpenter allegedly wrote on 10/06/2010 18:31 EDT:
>> I need to point out that there is closely related standards text,
>> code, and experience in REAP (RFC5534). 
> 
> (getting out of scope for v6ops but since we're here ...)
> 
> REAP is focused on failure recovery and parsimonious probing, while the
> happy eyeballs issue is configuring and caching connectivity results at
> multiple layers (v4, v6, different transport protocols) so the endpoints
> can quickly establish a connection that is likely to be useful.

I understand. But it is entirely possible that a REAP-like process spanning
v4 and v6 would be a method of achieving happy eyeballs for all applications
in one go, without any API impact or needing to touch the transport layer.

As the simulation shows, moving from sequential probing to simultaneous
probing does improve (re)connect time, but not so much as you might
expect.

> 
>> Although REAP was designed
>> as part of shim6, it's relatively separable if need be.
> 
> Good because Shim6 doesn't look like it's taking over the Internet :-p
> 
>> It also scales quite well, and tells us something about how long
>> trying out alternate paths will take in practice.
> 
> I don't recall if you saw my slides from Dagstuhl in early 2009, but
> everything you can accomplish with REAP and alternate paths you can do
> at least as well with concurrent multipath transport (SCTP, MPTCP).

Yes, of course these things are equivalent at some level. shim6 was
invented specifically to be invisible to widely used transport layers
such as TCP and UDP. It is an exercise for the reader to decide whether
shim6, SCTP or MPTCP has the best chance of taking over the Internet.

From randy@psg.com  Wed Oct  6 19:41:28 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ADA863A6FFA for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 19:41:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.604
X-Spam-Level: 
X-Spam-Status: No, score=-2.604 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h-88VdrGoQJB for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 19:41:27 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id CD09D3A6EBA for <v6ops@ietf.org>; Wed,  6 Oct 2010 19:41:26 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1P3gR7-000JJ2-6i; Thu, 07 Oct 2010 02:42:25 +0000
Date: Thu, 07 Oct 2010 11:42:19 +0900
Message-ID: <m2r5g2oh9w.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Tina TSOU <tena@huawei.com>
In-Reply-To: <B5BA80D4-4E7F-4F53-AD65-404E7692DA6B@huawei.com>
References: <20101001161955.7BE263A6CEF@core3.amsl.com> <47DA25FF-863C-4173-A038-93B2F30BA097@cisco.com> <1E6E380B-D0A3-41E1-BC62-8B1A2C97C657@huawei.com> <8C84858E-038D-4F2F-9C69-8D2A443CF2D1@cisco.com> <CB2FC880-934B-4241-905E-D221862EE13F@huawei.com> <54BED382-7B8C-4C23-826C-054B31333970@cisco.com> <641BFD35-D097-4E22-8A71-F3E75EB7CD4A@huawei.com> <C165683A-1C03-415A-806F-674620AB607B@cisco.com> <m2aamrraos.wl%randy@psg.com> <56DC0013-40B8-4D3A-99E0-B2837302DD70@huawei.com> <m28w2br9t0.wl%randy@psg.com> <9E025610-B99C-40B3-810F-BFDCD5CAE136@huawei.com> <m21v83quyh.wl%randy@psg.com> <96308D61-00CE-4D93-880E-3B1612F4F4D0@huawei.com> <4269EA985EACD24987D82DAE2FEC62E50254C801@XMB-AMS-101.cisco.com> <B5BA80D4-4E7F-4F53-AD65-404E7692DA6B@huawei.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: [v6ops] stupid discussion of power-driven bs with no technical content
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2010 02:41:28 -0000

>> Btw, this discussion is not anymore on agenda items. Please change the
>> title of the tread
> Why didn't you change the title? :)

i have

randy

From fred@cisco.com  Wed Oct  6 19:59:20 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 066ED3A70B3; Wed,  6 Oct 2010 19:59:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.374
X-Spam-Level: 
X-Spam-Status: No, score=-110.374 tagged_above=-999 required=5 tests=[AWL=0.225, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dze5Ga8t7-0L; Wed,  6 Oct 2010 19:59:11 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 3F15D3A6C0A; Wed,  6 Oct 2010 19:59:11 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAMvUrExAZnwM/2dsb2JhbACiU3GpB5wzhUcEikCDAg
X-IronPort-AV: E=Sophos;i="4.57,295,1283731200"; d="scan'208";a="167904440"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 07 Oct 2010 03:00:12 +0000
Received: from Freds-Computer.local (rtp-vpn2-1802.cisco.com [10.82.247.13]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o97304FC024685; Thu, 7 Oct 2010 03:00:04 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Wed, 06 Oct 2010 23:00:12 -0400
X-PGP-Universal: processed; by Freds-Computer.local on Wed, 06 Oct 2010 23:00:12 -0400
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4CAD31D5.3050707@gmail.com>
Date: Wed, 6 Oct 2010 22:59:54 -0400
Message-Id: <B5D2DBE5-196B-47DB-9AFC-EC475B3F5CC2@cisco.com>
References: <20101006191804.9D1853A71C0@core3.amsl.com>	<FE7805F0-B3FB-49BF-8C28-CED2CFEA3F0E@cisco.com> <4CACF8CB.9080106@gmail.com> <4CAD2F36.4060409@gmail.com> <4CAD31D5.3050707@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>, Scott Brim <scott.brim@gmail.com>, ops-dir@ietf.org
Subject: Re: [v6ops] Fwd: New Version Notification for draft-baker-v6ops-session-start-time-00
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2010 02:59:21 -0000

On Oct 6, 2010, at 10:35 PM, Brian E Carpenter wrote:

> As the simulation shows, moving from sequential probing to =
simultaneous
> probing does improve (re)connect time, but not so much as you might
> expect.

As I said in private email, I think they are looking at different =
problems.=20

If I have N*M address pairs (if I am connecting to some other system, I =
have N addresses and it has M), I can write a relatively simple equation =
for the amount of time it will take to set up a connection. Let's =
imagine I know the ping RTT for each pair, and let's call that value =
RTTij for i in 1..N and j in 1..M. If I send all SYNs simultaneously =
(and ignore queuing effects), the amount of time it will take to open =
one of the sessions is the least value in {RTTij | i in 1..N, j in =
1..M}. If I start them sequentially and the inter-start time is P, then =
in the worst case the time to open a session is (N*M-1)*P + RTTnm; the =
average is probably (N*M-1)*P/2 + RTT[N/2][M/2], and the least is =
RTT[1][1].

Now, consider the value of P. In most present applications' use of the =
Socket API, it opens a socket, attempts to connect, waits until the =
connect fails, and then tries the next. That puts P in the ballpark of =
2-3 seconds. What Happy Eyeballs suggests is to arbitrarily limit P to a =
magic number - 50 ms being recommended - and start new sessions in =
parallel.

For any positive value of N and M, (N*M-1)*3 seconds + a constant is =
greater than (N*M-1)*0.050 seconds + a constant, roughly 60 times as =
large.

I think what your simulation is measuring is the interference of the =
REAP protocol, which if there are more than 10 address pairs your =
article says measurably impedes the traffic it is protecting, with the =
traffic it is protecting.=20=

From brian.e.carpenter@gmail.com  Wed Oct  6 20:57:37 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 137B43A6D84; Wed,  6 Oct 2010 20:57:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.591
X-Spam-Level: 
X-Spam-Status: No, score=-102.591 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 113nYhoCwc5g; Wed,  6 Oct 2010 20:57:36 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id C80413A6D2D; Wed,  6 Oct 2010 20:57:35 -0700 (PDT)
Received: by gxk20 with SMTP id 20so140321gxk.31 for <multiple recipients>; Wed, 06 Oct 2010 20:58:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=TxqevHMxQ8Xqg7oFMVF8swMYlkm+ul/dGW6KanpXyls=; b=td05EDvfT6e5UCtobyCbM0iG5RTBaZLEW6y2nLo3aFRKB7nbRKaGDITEwhiF2mxBh9 DM4OmQkIqqPZZYVEsi4i/MkN6js+A9rgOOpbP456HMDrjL+Y1oaxx1ZPtu7caRvF3/vi DrbIHHVTgUumFhgWQPI39CL+z9ooqZGlJlYhc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=SpkNM7ypjZW9WOWBLG+p6oLYkQWKBRcxIG824Z52mnxvHBV5XEjDKEk3MT2hxBF6EN k0WC2WmrBYEoFymGYk7V92GbUAmqWJnxyBoUZ8rhsWbm1Z2WIf10kEXhOOUtnSXjoVlZ O5+nvhB1niFkx8ecQza6WQmPyTrP8vFIN5xWM=
Received: by 10.151.109.21 with SMTP id l21mr278103ybm.361.1286423916680; Wed, 06 Oct 2010 20:58:36 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id p30sm1581699ybk.8.2010.10.06.20.58.34 (version=SSLv3 cipher=RC4-MD5); Wed, 06 Oct 2010 20:58:36 -0700 (PDT)
Message-ID: <4CAD454A.8050209@gmail.com>
Date: Thu, 07 Oct 2010 16:58:02 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <20101006191804.9D1853A71C0@core3.amsl.com>	<FE7805F0-B3FB-49BF-8C28-CED2CFEA3F0E@cisco.com> <4CACF8CB.9080106@gmail.com> <4CAD2F36.4060409@gmail.com> <4CAD31D5.3050707@gmail.com> <B5D2DBE5-196B-47DB-9AFC-EC475B3F5CC2@cisco.com>
In-Reply-To: <B5D2DBE5-196B-47DB-9AFC-EC475B3F5CC2@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, Scott Brim <scott.brim@gmail.com>, ops-dir@ietf.org
Subject: Re: [v6ops] Fwd: New Version Notification for draft-baker-v6ops-session-start-time-00
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2010 03:57:37 -0000

On 2010-10-07 15:59, Fred Baker wrote:
> On Oct 6, 2010, at 10:35 PM, Brian E Carpenter wrote:
> 
>> As the simulation shows, moving from sequential probing to simultaneous
>> probing does improve (re)connect time, but not so much as you might
>> expect.
> 
> As I said in private email, I think they are looking at different problems. 
> 
> If I have N*M address pairs (if I am connecting to some other system, I have N addresses and it has M), I can write a relatively simple equation for the amount of time it will take to set up a connection. Let's imagine I know the ping RTT for each pair, and let's call that value RTTij for i in 1..N and j in 1..M. If I send all SYNs simultaneously (and ignore queuing effects), the amount of time it will take to open one of the sessions is the least value in {RTTij | i in 1..N, j in 1..M}. If I start them sequentially and the inter-start time is P, then in the worst case the time to open a session is (N*M-1)*P + RTTnm; the average is probably (N*M-1)*P/2 + RTT[N/2][M/2], and the least is RTT[1][1].
> 
> Now, consider the value of P. In most present applications' use of the Socket API, it opens a socket, attempts to connect, waits until the connect fails, and then tries the next. That puts P in the ballpark of 2-3 seconds. What Happy Eyeballs suggests is to arbitrarily limit P to a magic number - 50 ms being recommended - and start new sessions in parallel.

Yes, and that would in effect cut the tail off a long tail distribution. Of course,
the value of 50ms could be tuned experimentally.

> For any positive value of N and M, (N*M-1)*3 seconds + a constant is greater than (N*M-1)*0.050 seconds + a constant, roughly 60 times as large.
> 
> I think what your simulation is measuring is the interference of the REAP protocol, which if there are more than 10 address pairs your article says measurably impedes the traffic it is protecting, with the traffic it is protecting. 

Correct. Well, in theory, we can simulate anything, I suppose.

   Brian

From fred@cisco.com  Wed Oct  6 21:28:43 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7269B3A6D35; Wed,  6 Oct 2010 21:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.394
X-Spam-Level: 
X-Spam-Status: No, score=-110.394 tagged_above=-999 required=5 tests=[AWL=0.205, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QDn+koecgskS; Wed,  6 Oct 2010 21:28:42 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 595DE3A6D2D; Wed,  6 Oct 2010 21:28:42 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAGrprExAZnwN/2dsb2JhbACiU3GoKJw8hUcEikCDAg
X-IronPort-AV: E=Sophos;i="4.57,295,1283731200"; d="scan'208";a="167714548"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 07 Oct 2010 04:29:42 +0000
Received: from Freds-Computer.local (rtp-vpn2-1802.cisco.com [10.82.247.13]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o974TYV5025591; Thu, 7 Oct 2010 04:29:37 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Thu, 07 Oct 2010 00:29:42 -0400
X-PGP-Universal: processed; by Freds-Computer.local on Thu, 07 Oct 2010 00:29:42 -0400
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4CAD454A.8050209@gmail.com>
Date: Thu, 7 Oct 2010 00:29:27 -0400
Message-Id: <D4B66D23-D777-400C-941B-32921D59ADA4@cisco.com>
References: <20101006191804.9D1853A71C0@core3.amsl.com>	<FE7805F0-B3FB-49BF-8C28-CED2CFEA3F0E@cisco.com> <4CACF8CB.9080106@gmail.com> <4CAD2F36.4060409@gmail.com> <4CAD31D5.3050707@gmail.com> <B5D2DBE5-196B-47DB-9AFC-EC475B3F5CC2@cisco.com> <4CAD454A.8050209@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>, Scott Brim <scott.brim@gmail.com>, ops-dir@ietf.org
Subject: Re: [v6ops] Fwd: New Version Notification for draft-baker-v6ops-session-start-time-00
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2010 04:28:43 -0000

On Oct 6, 2010, at 11:58 PM, Brian E Carpenter wrote:

>> Now, consider the value of P. In most present applications' use of =
the Socket API, it opens a socket, attempts to connect, waits until the =
connect fails, and then tries the next. That puts P in the ballpark of =
2-3 seconds. What Happy Eyeballs suggests is to arbitrarily limit P to a =
magic number - 50 ms being recommended - and start new sessions in =
parallel.
>=20
> Yes, and that would in effect cut the tail off a long tail =
distribution. Of course,
> the value of 50ms could be tuned experimentally.

IMHO, Happy Eyeballs' 50 ms is a SWAG - a Silly Wild-A$$ed Guess. If I =
were to make it, I'd make it 10 ms. And someone else would pick pi^3. I =
think some serious experimentation is in order on that aspect.=

From ek@google.com  Wed Oct  6 21:41:18 2010
Return-Path: <ek@google.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC3C73A6DFD for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 21:41:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.677
X-Spam-Level: 
X-Spam-Status: No, score=-105.677 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DroZt+krUvUZ for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 21:41:18 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id AACE73A6D35 for <v6ops@ietf.org>; Wed,  6 Oct 2010 21:41:18 -0700 (PDT)
Received: from hpaq13.eem.corp.google.com (hpaq13.eem.corp.google.com [172.25.149.13]) by smtp-out.google.com with ESMTP id o974gJk5006622 for <v6ops@ietf.org>; Wed, 6 Oct 2010 21:42:19 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1286426540; bh=E8Id/9Hdn+YfC7qxZkRIEprfvmY=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=sBPH8lZW51HXEyhJpDjUJdawbTtPMaSHSi3VKtmPKdbGT9j7dXVl5NY8E9hq9sNwe JG3I134P+BpuoFybDD1HQ==
Received: from qwk3 (qwk3.prod.google.com [10.241.195.131]) by hpaq13.eem.corp.google.com with ESMTP id o974fD2D026971 for <v6ops@ietf.org>; Wed, 6 Oct 2010 21:42:18 -0700
Received: by qwk3 with SMTP id 3so140461qwk.7 for <v6ops@ietf.org>; Wed, 06 Oct 2010 21:42:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=V1spcGawoTK71BabrVA/L37IEfG9k4vjTzq79xS3vcE=; b=K5CPlF9r+lmsrkcrcnApUzQsHbj1IxI6S92q3zShgnPj9o3Y6r43b7+5SKYc8GSGFI 1ea1TmH2SNfPBjRE2mXw==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=qAZvNLSmfC9cCoKoMMcHlbAoTWn25lQ1OKROx8nKkZmLcFRogsEJpGKYpdE9XL6hlz TqLTshSNzWXHnDC404sw==
MIME-Version: 1.0
Received: by 10.229.240.145 with SMTP id la17mr266013qcb.75.1286426527812; Wed, 06 Oct 2010 21:42:07 -0700 (PDT)
Received: by 10.229.13.140 with HTTP; Wed, 6 Oct 2010 21:42:07 -0700 (PDT)
In-Reply-To: <D4B66D23-D777-400C-941B-32921D59ADA4@cisco.com>
References: <20101006191804.9D1853A71C0@core3.amsl.com> <FE7805F0-B3FB-49BF-8C28-CED2CFEA3F0E@cisco.com> <4CACF8CB.9080106@gmail.com> <4CAD2F36.4060409@gmail.com> <4CAD31D5.3050707@gmail.com> <B5D2DBE5-196B-47DB-9AFC-EC475B3F5CC2@cisco.com> <4CAD454A.8050209@gmail.com> <D4B66D23-D777-400C-941B-32921D59ADA4@cisco.com>
Date: Wed, 6 Oct 2010 21:42:07 -0700
Message-ID: <AANLkTi=2VguBz=epi_vWYyT3KXPDkiJp6uGP-N5VG5WT@mail.gmail.com>
From: Erik Kline <ek@google.com>
To: Fred Baker <fred@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: IPv6 Operations <v6ops@ietf.org>, Scott Brim <scott.brim@gmail.com>, ops-dir@ietf.org
Subject: Re: [v6ops] Fwd: New Version Notification for draft-baker-v6ops-session-start-time-00
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2010 04:41:19 -0000

On 6 October 2010 21:29, Fred Baker <fred@cisco.com> wrote:
>
> On Oct 6, 2010, at 11:58 PM, Brian E Carpenter wrote:
>
>>> Now, consider the value of P. In most present applications' use of the =
Socket API, it opens a socket, attempts to connect, waits until the connect=
 fails, and then tries the next. That puts P in the ballpark of 2-3 seconds=
. What Happy Eyeballs suggests is to arbitrarily limit P to a magic number =
- 50 ms being recommended - and start new sessions in parallel.
>>
>> Yes, and that would in effect cut the tail off a long tail distribution.=
 Of course,
>> the value of 50ms could be tuned experimentally.
>
> IMHO, Happy Eyeballs' 50 ms is a SWAG - a Silly Wild-A$$ed Guess. If I we=
re to make it, I'd make it 10 ms. And someone else would pick pi^3. I think=
 some serious experimentation is in order on that aspect.

Indeed.

FWIW, I'd choose something on the order of magnitude of 2 or 3 times
the mean or median RTT on the Internet, as measured by CAIDA or
something.

Also, timers on the connect() are one thing, but additional steps need
to be taken by applications in the face of possible pMTUd failures.
I've definitely seen instances where an IPv6 TCP connect happens
plenty fast, but forward progress on, say, an HTTP GET where the
returned page is "large" just hangs.  But that's a slightly different
discussion.

From dwing@cisco.com  Wed Oct  6 23:24:08 2010
Return-Path: <dwing@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 445373A6BAD; Wed,  6 Oct 2010 23:24:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.396
X-Spam-Level: 
X-Spam-Status: No, score=-110.396 tagged_above=-999 required=5 tests=[AWL=0.203, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CI2nUQ7gPO4i; Wed,  6 Oct 2010 23:24:07 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 4B5C23A6BDF; Wed,  6 Oct 2010 23:24:07 -0700 (PDT)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.57,296,1283731200"; d="scan'208";a="265775034"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-5.cisco.com with ESMTP; 07 Oct 2010 06:24:52 +0000
Received: from dwingWS ([10.32.240.197]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o976OqwM005956; Thu, 7 Oct 2010 06:24:52 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Erik Kline'" <ek@google.com>, "'Fred Baker'" <fred@cisco.com>
References: <20101006191804.9D1853A71C0@core3.amsl.com>	<FE7805F0-B3FB-49BF-8C28-CED2CFEA3F0E@cisco.com>	<4CACF8CB.9080106@gmail.com> <4CAD2F36.4060409@gmail.com>	<4CAD31D5.3050707@gmail.com>	<B5D2DBE5-196B-47DB-9AFC-EC475B3F5CC2@cisco.com>	<4CAD454A.8050209@gmail.com>	<D4B66D23-D777-400C-941B-32921D59ADA4@cisco.com> <AANLkTi=2VguBz=epi_vWYyT3KXPDkiJp6uGP-N5VG5WT@mail.gmail.com>
In-Reply-To: <AANLkTi=2VguBz=epi_vWYyT3KXPDkiJp6uGP-N5VG5WT@mail.gmail.com>
Date: Wed, 6 Oct 2010 23:24:52 -0700
Message-ID: <035701cb65e8$5a345bf0$0e9d13d0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Actl2gyqh2ylOPfvRoGzI98VJfO0swADc3qA
Content-Language: en-us
Cc: 'IPv6 Operations' <v6ops@ietf.org>, 'Scott Brim' <scott.brim@gmail.com>, ops-dir@ietf.org
Subject: Re: [v6ops] Fwd: New Version Notification for	draft-baker-v6ops-session-start-time-00
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2010 06:24:08 -0000

> Also, timers on the connect() are one thing, but additional steps need
> to be taken by applications in the face of possible pMTUd failures.
> I've definitely seen instances where an IPv6 TCP connect happens
> plenty fast, but forward progress on, say, an HTTP GET where the
> returned page is "large" just hangs.  But that's a slightly different
> discussion.

Significantly different discussion. 

Instead of talking about GETs which can be dismissed ("nyeah, it was
slow, do it again over IPv4 after awhile"), I worry about POSTs hitting
these PMTUD problems, because they could change the state on the server
(partially updating a file, selling stock, ...  who knows what else).

-d



From dwing@cisco.com  Wed Oct  6 23:34:46 2010
Return-Path: <dwing@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B50403A6F95 for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 23:34:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.099
X-Spam-Level: 
X-Spam-Status: No, score=-110.099 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6v9A6DqOih4s for <v6ops@core3.amsl.com>; Wed,  6 Oct 2010 23:34:43 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 367F63A6FAF for <v6ops@ietf.org>; Wed,  6 Oct 2010 23:34:43 -0700 (PDT)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.57,296,1283731200"; d="scan'208";a="265780403"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-5.cisco.com with ESMTP; 07 Oct 2010 06:35:45 +0000
Received: from dwingWS ([10.32.240.197]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o976ZiUx025274; Thu, 7 Oct 2010 06:35:45 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'Fernando Gont'" <fernando@gont.com.ar>, "'Fred Baker'" <fred@cisco.com>
References: <D40F684E-2A7B-42E6-ADC4-F4AFDE879FE3@cisco.com>	<DC5EA05D-3758-4351-9DB0-A46218482815@cisco.com> <4CAC88AD.3010901@gont.com.ar>
In-Reply-To: <4CAC88AD.3010901@gont.com.ar>
Date: Wed, 6 Oct 2010 23:35:45 -0700
Message-ID: <036301cb65e9$df221810$9d664830$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: ActlY3dt+hwARaeHQX6lumzqTbAdBAAhcE5Q
Content-Language: en-us
Cc: 'IPv6 Operations' <v6ops@ietf.org>, 'Dave Thaler' <dthaler@microsoft.com>
Subject: Re: [v6ops] "ipv6 on windows 7" - Google Search
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2010 06:34:47 -0000

> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
> Of Fernando Gont
> Sent: Wednesday, October 06, 2010 7:33 AM
> To: Fred Baker
> Cc: IPv6 Operations; Dave Thaler
> Subject: Re: [v6ops] "ipv6 on windows 7" - Google Search
> 
> Hi, Fred,
> 
> > Reading over my own email, my comment can be confusing - the
> > getaddrinfo() stuff is in the implementations in question, so it does
> > indeed "have something to do with the implementation". I guess my
> > question is -
> >
> > I get questions about operational IPv6 deployment due to issues of
> > implementation. One ISP recently told me that they can't deploy AAAA
> > records for certain services because when their customers are in the
> > region of a neighboring ISP that runs IPv6 as a walled garden and btw
> > respond to connection attempts with a TCP RST, their user's laptops
> > don't correctly fall back to IPv4.
> 
> Note: I do recall checking, years ago, that Windows systems used to
> respond with RST when e.g. the queue of incoming connections was full
> (e.g., the server was under s SYN-flood attack). As a result, RSTs had
> the semantics of "soft errors", rather than "hard errors", and hence
> Windows was being coherent with their own implementation. -- Although
> IMO their behavior was coherent but wrong: RSTs are ment to signal hard
> errors... so they shouldn't have been sending RSTs when under a
> SYN-flood attack, and would be aborting connections upon receipt of an
> RST.
> 
> 
> 
> > I can imagine several possible
> > recommendations, and might actually recommend two of them: "happy
> > eyeballs" as Dan Wing describes (open TCP sessions at some rate
> > trying all IPv4 and IPv6 combinations until one of them opens a
> > session, with the objective of achieving an open session within a
> > stated interval such as 1 second or less),
> 
> FWIW, this approach of "parallel connections" was mentioned in at least
> some of the I-D versions that led to RFC 5461.
> 
> However, keep in mind that this approach of "try all possible
> addresses"
> may put a bit of stress on the servers - particularly those that are
> popular and also have multiple addresses.
> 
> 
> > and an operational
> > recommendation that if you're going to run IPv6 as a walled garden,
> > that you configure your first hop routers to respond "host
> > unreachable" or "network unreachable" to any packet that you have
> > decided to not deliver.
> 
> Specs-wise that wouldn't help. We (other folks and myself) tried to
> pursue RFC5461 as std track... but there was an endless debate on tcpm,
> and the I-D ended up targeting the Informational track. Specs-wise,
> these "destination unreachables" indicate soft errors, and thus should
> not cause the connection to be aborted.

My read of RFC5927 and RFC5461 is that destination
unreachable/administratively 
prohibited should have the desired effect.  That is what these walled 
gardens are trying to say, anyway -- "I don't want that traffic".

-d

> That said, RFC5461 *has* been implemented in the real world, despite
> tcpm's concerns.
> 
> Some folks at a japanese telco had mentioned that they had asked a
> (large :-) ) vendor to implement RFC 5461, but they argued that they
> wouldn't, because RFC5461 was not std track.
> 
> 
> > Would it be appropriate, and would the working group like to discuss,
> > such recommendations?
> 
> The "problem" here is that, in order for such a recommendation to make
> sense, you need to have clients react to those ICMPs by aborting the
> corresponding connection.... and that basically means re-hashing RFC
> 5461.
> 
> I guess that if the proposal aims at requiring this behavior *only* for
> ICMPv6 (and *not* for ICMPv4), it may have more chances to fly, but...
> 
> Thoughts?
> 
> Kind regards,
> --
> Fernando Gont
> e-mail: fernando@gont.com.ar || fgont@acm.org
> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
> 
> 
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From gert@space.net  Thu Oct  7 01:02:52 2010
Return-Path: <gert@space.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C2CCE3A6DFA for <v6ops@core3.amsl.com>; Thu,  7 Oct 2010 01:02:52 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hhYOipAxsqWA for <v6ops@core3.amsl.com>; Thu,  7 Oct 2010 01:02:48 -0700 (PDT)
Received: from mobil.space.net (mobil.Space.Net [IPv6:2001:608:2:81::2]) by core3.amsl.com (Postfix) with ESMTP id 51DF73A6D18 for <v6ops@ietf.org>; Thu,  7 Oct 2010 01:02:47 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id 9C14FF83EE for <v6ops@ietf.org>; Thu,  7 Oct 2010 10:03:47 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 819F2F81F9 for <v6ops@ietf.org>; Thu,  7 Oct 2010 10:03:47 +0200 (CEST)
Received: (qmail 28996 invoked by uid 1007); 7 Oct 2010 10:03:47 +0200
Date: Thu, 7 Oct 2010 10:03:47 +0200
From: Gert Doering <gert@space.net>
To: Fred Baker <fred@cisco.com>
Message-ID: <20101007080347.GT32268@Space.Net>
References: <20101006191804.9D1853A71C0@core3.amsl.com> <FE7805F0-B3FB-49BF-8C28-CED2CFEA3F0E@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FE7805F0-B3FB-49BF-8C28-CED2CFEA3F0E@cisco.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: IPv6 Operations <v6ops@ietf.org>, ops-dir@ietf.org
Subject: Re: [v6ops] Fwd: New Version Notification for draft-baker-v6ops-session-start-time-00
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2010 08:02:52 -0000

Hi,

On Wed, Oct 06, 2010 at 03:33:20PM -0400, Fred Baker wrote:
> If I get enough people telling me they agree with this, 

*agree*

Gert Doering
-- 
did you enable IPv6 on something today...?

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

From behcetsarikaya@yahoo.com  Thu Oct  7 09:39:08 2010
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B94F3A6C24 for <v6ops@core3.amsl.com>; Thu,  7 Oct 2010 09:39:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.188
X-Spam-Level: 
X-Spam-Status: No, score=-2.188 tagged_above=-999 required=5 tests=[AWL=0.411,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OkqtNHGhFwO9 for <v6ops@core3.amsl.com>; Thu,  7 Oct 2010 09:39:06 -0700 (PDT)
Received: from nm27-vm0.bullet.mail.sp2.yahoo.com (nm27-vm0.bullet.mail.sp2.yahoo.com [98.139.91.232]) by core3.amsl.com (Postfix) with SMTP id C1C753A7153 for <v6ops@ietf.org>; Thu,  7 Oct 2010 09:39:05 -0700 (PDT)
Received: from [98.139.91.69] by nm27.bullet.mail.sp2.yahoo.com with NNFMP; 07 Oct 2010 16:40:05 -0000
Received: from [98.139.91.24] by tm9.bullet.mail.sp2.yahoo.com with NNFMP; 07 Oct 2010 16:40:05 -0000
Received: from [127.0.0.1] by omp1024.mail.sp2.yahoo.com with NNFMP; 07 Oct 2010 16:40:05 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 457999.28262.bm@omp1024.mail.sp2.yahoo.com
Received: (qmail 39420 invoked by uid 60001); 7 Oct 2010 16:40:04 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1286469604; bh=mSLlFR12ch6shnK0p3H4QP/4zS6DX7zwwzEQ6OD+aWE=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=3OiMRDojrKndFq+Yh+jeriOTdLl1G6aaZxo3pOjnY15jHh8RZVMYsUwfve6rXnyJ5xX8YQdHnMuZVyF45+5F340+l8fYtzjTsbVIRw9qAH+3jSQr/rBFP0o9gyzSjP9R94Y4mr/sZeuPvEgMswF7cVI4wgalJPv13rJSeZFCYMQ=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=n2NrNJfwG49iL3WOj1ESxOuwo0gu5q68RyCm04s+Y20WRbiGAX8ri3hlHU92Jb0GyApjXlRpPHUxUF1aKTTU7ZPClyT7jmngwVHLquuT7h1K+HmbyAp7XUGYxv1AMqhFEKgFtn92hogc8tXVGHSY69zHS392MDdLsXaQC5ASQ4Q=;
Message-ID: <744414.39065.qm@web111406.mail.gq1.yahoo.com>
X-YMail-OSG: BctqWUMVM1lxV1IM6fZTue3zd7hOvryPFiEltezn6v1Kz1e v1ONptqQ8KULtfyGe5NTL4syeATacHcjt8BP_8Z68pFC8u3xbjNKCyrf7Jpn YLWt.YKa22cug6XvUHtfLRYDhNrDbjTzk8kY8213fDpPrR7gF0yTVfIn0dc0 mPPxTRmNrgJmNkTsTqcdl3lp6AcaxzyJ_UWBXtO7tbV5pdZt6mKUSyOXmT7Y vqKKUkSIaab7sH6219duWjYc9cAutyt3TYnCq4ksCmON5TIuBwqqnd1p3FOc iNzIM6TWhwk7bWSW4gHyHZi0c3E07K7d8DtRoCbNbA4DRFksQ_w4YVPYXIwP 9p4bYReDB1cbhy3O_dEi.82CcC3C3GQ4-
Received: from [206.16.17.212] by web111406.mail.gq1.yahoo.com via HTTP; Thu, 07 Oct 2010 09:40:03 PDT
X-Mailer: YahooMailRC/504.5 YahooMailWebService/0.8.106.282862
References: <4CAAA2B5.1070901@ericsson.com>
Date: Thu, 7 Oct 2010 09:40:03 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, v6ops@ietf.org
In-Reply-To: <4CAAA2B5.1070901@ericsson.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [v6ops] Review of draft-sarikaya-v6ops-prefix-delegation-01.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2010 16:39:08 -0000

Hi Suresh,
  Thank you for your review.
Please see inline.




----- Original Message ----
> From: Suresh Krishnan <suresh.krishnan@ericsson.com>
> To: v6ops@ietf.org
> Sent: Mon, October 4, 2010 10:59:49 PM
> Subject: [v6ops] Review of draft-sarikaya-v6ops-prefix-delegation-01.txt
> 
> Hi,
>   I have read the draft  draft-sarikaya-v6ops-prefix-delegation-01.txt and I 
>have a few  comments.
> 
> Meta-comment
> ============
> 
> It is unclear what the goal  of this draft is
> 
> a) Is it expected to be a recommendation from the IETF  to 3GPP, WiMAX forum 
>etc. on how to perform DHCPv6-PD in their  networks?
> 
> (or)
> 
> b) Is it an Informational document expected to  document how DHCPv6-PD is being 
>used in these networks?
> 
> There is more  clarity required here.

It is more a) than b) I think. That's why the intended status is BCP. What do 
you think?

> 
> Section 3.1
> ===========
> 
> * First  paragraph: The text about the relay function is completely wrong. If 
>the AR and  the >DHCPv6 server are not directly connected, there needs to be at 
>least one  relay between >them but the relay is certainly not the AR. Can you 
>please rewrite  this?

This is an important point that we need to clarify.

What we have in 3.1 is SLAAC scenario. AR gets the attach trigger and starts the 
Requesting Router operation of 3633 with DHCP Solicit which is internally 
generated. Then another part in AR which is DHCP Relay takes this and sends out 
Relay-Forward message. Pictorially we showed these and following message 
exchanges as in Fig. 2.

Do you think we should make DHCP Client- Relay agent communication more explicit 
in the figure?


> 
> * Same comment about the relay behavior for the sequence diagram.  The AR  
>either sends Solicit messages (or) relays Solicit messages from  somebody else. 
>It does not relay-forward its own Solicit messages.
> 
> * Step  2: Need to refer to RFC3633 for describing how to create the IA_PD.
> 
> *  Step 7: How is the prefix for the RA derived from the delegated  prefix?
> 
> Section 3.2
> ===========
> 
> * Requires a different sequence  diagram showing DHCPv6 messages originating 
>from the MN and relay messages from  the AR. This cannot be shared with Section 
>3.1
> 

What we have in Sec. 3.2 is DHCP scenario. AR first gets a prefix using Sec. 
3.1.
Yes you are right, the next part is different, we can have a different diagram 
there.

We will fix the draft based on your other comments, no problem.


      

From brian.e.carpenter@gmail.com  Thu Oct  7 15:38:39 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EBC173A6F8B; Thu,  7 Oct 2010 15:38:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.363
X-Spam-Level: 
X-Spam-Status: No, score=-102.363 tagged_above=-999 required=5 tests=[AWL=0.236, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t4l16UMKYer5; Thu,  7 Oct 2010 15:38:37 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id A21173A6FD8; Thu,  7 Oct 2010 15:38:03 -0700 (PDT)
Received: by vws10 with SMTP id 10so141546vws.31 for <multiple recipients>; Thu, 07 Oct 2010 15:39:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=GxzH5qnmm0KWTzqW0erZisM88u942afcs3vQKo0+8ic=; b=rBJxp+CIeuZsGRNhQ37x8heGUCXXnRiQRFSEttfFBh9zvOeLjL9nf1FeIVF2Uc4J84 GYEPTOEHx2/tHJiaqhhMXHIIRDVM5GsxLujz5k36FFmjx6VGkwFnUetE8eNneLwu149n 4MA3zJvq4EgtWBBm9RB2NFSxg2VU//CQRF9mU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=itrwEBNaP3JsHYQOV1r2jvFJHyVHZkWqfFBQKZ9rd5Q7NpLsYv5IO+X/ksb/PO+FUq BZK87rL3/etG3IuyC0C2zCEskWt5yeyqjakvLGNnEUBEl6eYfgQDO7OLDt2WUeutNPIp gnrTLPh4YDtI9aPdS/SerFzI7q2yGxpeTgS/0=
Received: by 10.220.164.13 with SMTP id c13mr442409vcy.110.1286491146688; Thu, 07 Oct 2010 15:39:06 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.142.15]) by mx.google.com with ESMTPS id i2sm1222992vcs.9.2010.10.07.15.39.03 (version=SSLv3 cipher=RC4-MD5); Thu, 07 Oct 2010 15:39:05 -0700 (PDT)
Message-ID: <4CAE4C02.2000203@gmail.com>
Date: Fri, 08 Oct 2010 11:38:58 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IPv6 Operations <v6ops@ietf.org>
References: <20101006191804.9D1853A71C0@core3.amsl.com>	<FE7805F0-B3FB-49BF-8C28-CED2CFEA3F0E@cisco.com>	<4CACF8CB.9080106@gmail.com>	<4CAD2F36.4060409@gmail.com>	<4CAD31D5.3050707@gmail.com>	<B5D2DBE5-196B-47DB-9AFC-EC475B3F5CC2@cisco.com>	<4CAD454A.8050209@gmail.com>	<D4B66D23-D777-400C-941B-32921D59ADA4@cisco.com>	<AANLkTi=2VguBz=epi_vWYyT3KXPDkiJp6uGP-N5VG5WT@mail.gmail.com>	<035701cb65e8$5a345bf0$0e9d13d0$@com> <AANLkTinn7MEcKjz=KjoVrAr9y7BX64PMOoTWKcKpVqcW@mail.gmail.com>
In-Reply-To: <AANLkTinn7MEcKjz=KjoVrAr9y7BX64PMOoTWKcKpVqcW@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ops-dir@ietf.org
Subject: [v6ops] POSTs [was: New Version Notification for draft-baker-v6ops-session-start-time-00]
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Oct 2010 22:38:39 -0000

Dan,

> From: Dan Wing <dwing@cisco.com>
> Date: Thu, Oct 7, 2010 at 7:24 PM
> Subject: Re: [v6ops] Fwd: New Version Notification
> for	draft-baker-v6ops-session-start-time-00
> To: Erik Kline <ek@google.com>, Fred Baker <fred@cisco.com>
> Cc: IPv6 Operations <v6ops@ietf.org>, Scott Brim
> <scott.brim@gmail.com>, ops-dir@ietf.org
> 
> 
>> Also, timers on the connect() are one thing, but additional steps need
>> to be taken by applications in the face of possible pMTUd failures.
>> I've definitely seen instances where an IPv6 TCP connect happens
>> plenty fast, but forward progress on, say, an HTTP GET where the
>> returned page is "large" just hangs.  But that's a slightly different
>> discussion.
> 
> Significantly different discussion.
> 
> Instead of talking about GETs which can be dismissed ("nyeah, it was
> slow, do it again over IPv4 after awhile"), I worry about POSTs hitting
> these PMTUD problems, because they could change the state on the server
> (partially updating a file, selling stock, ...  who knows what else).

And I'm not sure it's relevant to the happy eyeballs model. POST failures,
by definition, arise after you've already made a TCP connection to
the server. A failure to discover a too-small PMTU (or NATs losing state),
may explain them, but those are entirely different problems. The fact
that POST is a broken transaction protocol is unfixable.

    Brian

From joelja@bogus.com  Thu Oct  7 21:21:33 2010
Return-Path: <joelja@bogus.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CAC1F3A67EE for <v6ops@core3.amsl.com>; Thu,  7 Oct 2010 21:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.535
X-Spam-Level: 
X-Spam-Status: No, score=-101.535 tagged_above=-999 required=5 tests=[AWL=-0.828, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MISSING_HEADERS=1.292, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pqunNIEucfvM for <v6ops@core3.amsl.com>; Thu,  7 Oct 2010 21:21:32 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 379033A67EA for <v6ops@ietf.org>; Thu,  7 Oct 2010 21:21:32 -0700 (PDT)
Received: from [192.168.2.103] (m4d5536d0.tmodns.net [208.54.85.77]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id o984MSAY028757 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT) for <v6ops@ietf.org>; Fri, 8 Oct 2010 04:22:35 GMT (envelope-from joelja@bogus.com)
Message-ID: <4CAE9C7F.8020309@bogus.com>
Date: Fri, 08 Oct 2010 00:22:23 -0400
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
CC: IPv6 Operations <v6ops@ietf.org>
References: <8FEB0766-BF81-4B83-ADCA-055AF1CAF239@cisco.com>
In-Reply-To: <8FEB0766-BF81-4B83-ADCA-055AF1CAF239@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Fri, 08 Oct 2010 04:22:35 +0000 (UTC)
Subject: [v6ops] Reminder: draft-ietf-v6ops-tunnel-loops WGLC ends at the close of 10/10/10
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Oct 2010 04:21:33 -0000

Just to remind the list, deadline for last call on
draft-ietf-v6ops-tunnel-loops is the end of the day on 10/10/10. please
submit your comments by then.

http://tools.ietf.org/html/draft-ietf-v6ops-tunnel-loops-00

thanks
joel

On 9/26/10 2:00 PM, Fred Baker wrote:
> This is to initiate a two week working group last call of
> draft-ietf-v6ops-tunnel-loops. Please read it now. If you find nits
> (spelling errors, minor suggested wording changes, etc), comment to the
> authors; if you find greater issues, such as disagreeing with a
> statement or finding additional issues that need to be addressed, please
> post your comments to the list.
> 
> We are looking specifically for comments on the importance of the
> document as well as its content. If you have read the document and
> believe it to be of operational utility, that is also an important
> comment to make.
> 
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From vbhanu@microsoft.com  Fri Oct  8 20:12:26 2010
Return-Path: <vbhanu@microsoft.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D8963A677C for <v6ops@core3.amsl.com>; Fri,  8 Oct 2010 20:12:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RdoDP7AIrEDO for <v6ops@core3.amsl.com>; Fri,  8 Oct 2010 20:12:24 -0700 (PDT)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by core3.amsl.com (Postfix) with ESMTP id 8EECF3A6767 for <v6ops@ietf.org>; Fri,  8 Oct 2010 20:12:24 -0700 (PDT)
Received: from TK5EX14MLTC103.redmond.corp.microsoft.com (157.54.79.174) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 8 Oct 2010 20:13:24 -0700
Received: from TK5EX14MBXC129.redmond.corp.microsoft.com ([169.254.8.77]) by TK5EX14MLTC103.redmond.corp.microsoft.com ([157.54.79.174]) with mapi id 14.01.0218.012; Fri, 8 Oct 2010 20:13:24 -0700
From: Vivek Bhanu <vbhanu@microsoft.com>
To: "'v6ops@ietf.org'" <v6ops@ietf.org>
Thread-Topic: RE: [v6ops] "ipv6 on windows 7" - Google Search
Thread-Index: ActnVwxpl/FmNxX9Sn6QVmgVJ+gKFw==
Date: Sat, 9 Oct 2010 03:13:24 +0000
Message-ID: <2E8405BF2C0C874BB2A91035BE3AB32113C28EC3@TK5EX14MBXC129.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.70]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [v6ops] "ipv6 on windows 7" - Google Search
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Oct 2010 03:12:26 -0000

Hi Fernando:

> Note: I do recall checking, years ago, that Windows systems used to
> respond with RST when e.g. the queue of incoming connections was full
> (e.g., the server was under s SYN-flood attack). As a result, RSTs had
> the semantics of "soft errors", rather than "hard errors", and hence
> Windows was being coherent with their own implementation. -- Although
> IMO their behavior was coherent but wrong: RSTs are ment to signal hard
> errors... so they shouldn't have been sending RSTs when under a
> SYN-flood attack, and would be aborting connections upon receipt of an RS=
T.

The Windows implementation generates a RST to inform the sender that the
receiver side has deliberately rejected its request. The RST is hard from t=
he=20
point of view that the connection in question isn't allowed to transfer dat=
a
and is in the CLOSED state.

The sender is free to negotiate a second time subsequently. A Windows=20
sender retransmits its SYN to work around the queue limits when it receives
a RST in response to the original SYN and gives up after all retransmission=
s
(3) are exhausted. So if the receiver is overwhelmed for any reason, the
sender still ends up with a hard error after 3 RTTs elapse.=20

So when the application observes that its connection request failed, it is=
=20
free to negotiate once again using a different address. The winsock API,=20
WSAConnectByName helps applications in this regard.

Thanks
Vivek



From tena@huawei.com  Fri Oct  8 23:03:29 2010
Return-Path: <tena@huawei.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E2AEE3A67E4; Fri,  8 Oct 2010 23:03:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -92.981
X-Spam-Level: 
X-Spam-Status: No, score=-92.981 tagged_above=-999 required=5 tests=[AWL=7.513, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EqIgtfBQ6qHC; Fri,  8 Oct 2010 23:03:27 -0700 (PDT)
Received: from szxga05-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id E5E7C3A67FA; Fri,  8 Oct 2010 23:03:26 -0700 (PDT)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LA00000ZE7A7V@szxga05-in.huawei.com>; Sat, 09 Oct 2010 14:04:22 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LA0002CBE79N6@szxga05-in.huawei.com>; Sat, 09 Oct 2010 14:04:22 +0800 (CST)
Received: from [192.168.1.7] (c-24-7-50-101.hsd1.ca.comcast.net [24.7.50.101]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LA000JBWE749V@szxml02-in.huawei.com>; Sat, 09 Oct 2010 14:04:21 +0800 (CST)
Date: Sat, 09 Oct 2010 14:04:15 +0800
From: Tina TSOU <tena@huawei.com>
In-reply-to: <E1D6BFB4BE1043838F808F490589DD61@china.huawei.com>
To: IPv6 Operations <v6ops@ietf.org>, ops-dir@ietf.org
Message-id: <1317BCCD-CB91-4924-9DCC-DB9B345CA2A3@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.936)
Content-type: multipart/alternative; boundary="Boundary_(ID_7A8o7QUXIi2VKm218RcQUA)"
References: <E1D6BFB4BE1043838F808F490589DD61@china.huawei.com>
Subject: Re: [v6ops] [OPS-DIR] Fwd: New Version Notification fordraft-baker-v6ops-session-start-time-00
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Oct 2010 06:03:29 -0000

--Boundary_(ID_7A8o7QUXIi2VKm218RcQUA)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT

Hi,

Since draft-baker-v6ops-session-start-time-00 recommends RFC5461 and  
draft-wing-http-new-tech-00, I have some comments on draft-wing-http- 
new-tech-00.

Section 4.1

The HTTP client is configured with one value, P. A positive value

    indicates a preference for IPv6 and a negative value indicates a

    preference for IPv4.  A value of 0 indicates equal weight, which

    means the A and AAAA queries and associated connection attempts will

    be sent as quickly as possible.  The absolute value of P is the

    measure of a delay before initiating a connection attempt on the

    other address family.  There are two P values maintained:  one is

    application-wide and the other is specific per each destination

    (hostname and port).

  [snipped]

    The HTTP client starts two threads in order to minimize the user-

    noticeable delay ("dead time") during the connection attempts:



Comments are below.

1) One P per client or one P per application?

2) How would the application-wide P and the per-destination P work  
together? What if application-wide P is greater than 0 and per- 
destination P smaller than 0, and vise versa, which would take priority?

3. How about more threads, e.g. 3 or 4, try multiple IPv4 and IPv6  
addresses simultaneously (maybe I miss something)? Of course this  
might cause some problem if the number of threads is too big.



B. R.
Tina
http://tinatsou.weebly.com



--Boundary_(ID_7A8o7QUXIi2VKm218RcQUA)
Content-type: text/html; charset=GB2312
Content-transfer-encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><!--StartFragment--><p =
class=3D"MsoNormal">Hi,</p><p class=3D"MsoNormal">Since =
draft-baker-v6ops-session-start-time-00 recommends RFC5461<span =
style=3D"font-family:&quot;Apple =
Symbols&quot;;mso-bidi-font-family:&quot;Apple Symbols&quot;"> =
</span><font class=3D"Apple-style-span" face=3D"Arial">and</font>
draft-wing-http-new-tech-00, I have some comments on =
draft-wing-http-new-tech-00.</p><p class=3D"MsoNormal"><span =
style=3D"font-family:=CB=CE=CC=E5;mso-bidi-font-family:=CB=CE=CC=E5">Secti=
on
4.1<o:p></o:p></span></p><p class=3D"MsoNormal"><span =
style=3D"font-family:=CB=CE=CC=E5;mso-bidi-font-family:=CB=CE=CC=E5"><font=
 class=3D"Apple-style-span" color=3D"#FF0000">The
HTTP client is configured with one value, P.</font> A positive =
value<o:p></o:p></span></p><p class=3D"MsoNormal"><span =
style=3D"font-family:=CB=CE=CC=E5;mso-bidi-font-family:=CB=CE=CC=E5"><span=
 style=3D"mso-spacerun: yes">&nbsp;&nbsp; </span>indicates a preference =
for IPv6
and a negative value indicates a<o:p></o:p></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-family:=CB=CE=CC=E5;mso-bidi-font-family:=CB=CE=CC=E5"><span=
 style=3D"mso-spacerun: yes">&nbsp;&nbsp; </span>preference for =
IPv4.<span style=3D"mso-spacerun: yes">&nbsp; </span>A value of 0 =
indicates equal weight,
which<o:p></o:p></span></p><p class=3D"MsoNormal"><span =
style=3D"font-family:=CB=CE=CC=E5;mso-bidi-font-family:=CB=CE=CC=E5"><span=
 style=3D"mso-spacerun: yes">&nbsp;&nbsp; </span>means the A and AAAA =
queries and
associated connection attempts will<o:p></o:p></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-family:=CB=CE=CC=E5;mso-bidi-font-family:=CB=CE=CC=E5"><span=
 style=3D"mso-spacerun: yes">&nbsp;&nbsp; </span>be sent as quickly as
possible.<span style=3D"mso-spacerun: yes">&nbsp; </span>The absolute =
value of P
is the<o:p></o:p></span></p><p class=3D"MsoNormal"><span =
style=3D"font-family:=CB=CE=CC=E5;mso-bidi-font-family:=CB=CE=CC=E5"><span=
 style=3D"mso-spacerun: yes">&nbsp;&nbsp; </span>measure of a delay =
before
initiating a connection attempt on the<o:p></o:p></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-family:=CB=CE=CC=E5;mso-bidi-font-family:=CB=CE=CC=E5"><span=
 style=3D"mso-spacerun: yes">&nbsp;&nbsp; </span>other address =
family.<span style=3D"mso-spacerun: yes">&nbsp; </span><font =
class=3D"Apple-style-span" color=3D"#FF0000">There are two P values =
maintained</font>:<span style=3D"mso-spacerun: yes">&nbsp; </span>one =
is<o:p></o:p></span></p><p class=3D"MsoNormal"><span =
style=3D"font-family:=CB=CE=CC=E5;mso-bidi-font-family:=CB=CE=CC=E5"><span=
 style=3D"mso-spacerun: yes">&nbsp;&nbsp; </span>application-wide and =
the other is
specific per each destination<o:p></o:p></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-family:=CB=CE=CC=E5;mso-bidi-font-family:=CB=CE=CC=E5"><span=
 style=3D"mso-spacerun: yes">&nbsp;&nbsp; </span>(hostname and =
port).<o:p></o:p></span></p><p class=3D"MsoNormal"><span =
style=3D"font-family:=CB=CE=CC=E5;mso-bidi-font-family:=CB=CE=CC=E5"><span=
 style=3D"mso-spacerun: =
yes">&nbsp;</span>[snipped]<o:p></o:p></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-family:=CB=CE=CC=E5;mso-bidi-font-family:=CB=CE=CC=E5"><span=
 style=3D"mso-spacerun: yes">&nbsp;&nbsp; </span>The HTTP client starts =
<font class=3D"Apple-style-span" color=3D"#FF0000">two
threads </font>in order to minimize the user-<o:p></o:p></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-family:=CB=CE=CC=E5;mso-bidi-font-family:=CB=CE=CC=E5"><span=
 style=3D"mso-spacerun: yes">&nbsp;&nbsp; </span>noticeable delay ("dead
time") during the connection attempts:<o:p></o:p></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-family:=CB=CE=CC=E5;mso-bidi-font-family:=CB=CE=CC=E5"><span=
 style=3D"mso-spacerun: yes">&nbsp;</span><o:p></o:p></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-family:=CB=CE=CC=E5;mso-bidi-font-family:=CB=CE=CC=E5">Comme=
nts
are below.<o:p></o:p></span></p><p class=3D"MsoNormal"><span =
style=3D"font-family:=CB=CE=CC=E5;mso-bidi-font-family:=CB=CE=CC=E5">1) =
One
P per client or one P per application?<o:p></o:p></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-family:=CB=CE=CC=E5;mso-bidi-font-family:=CB=CE=CC=E5">2) =
How
would the application-wide P and the per-destination P work together? =
What if
application-wide P is greater than 0 and per-destination P smaller than =
0, and
vise versa, which would take priority?<o:p></o:p></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-family:=CB=CE=CC=E5;mso-bidi-font-family:=CB=CE=CC=E5">3. =
How
about more threads, e.g. 3 or 4, try multiple IPv4 and IPv6 addresses
simultaneously (maybe I miss something)? Of course this might cause some
problem if the number of threads is too big.<o:p></o:p></span></p><p =
class=3D"MsoNormal"><span =
style=3D"font-family:=CB=CE=CC=E5;mso-bidi-font-family:=CB=CE=CC=E5"><br><=
/span></p>

<!--EndFragment-->


<div apple-content-edited=3D"true"> <div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; 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; "><div><span class=3D"Apple-style-span" =
style=3D"font-size: 12px; "><div>B. R.</div><div>Tina</div><div><a =
href=3D"http://tinatsou.weebly.com">http://tinatsou.weebly.com</a></div><d=
iv></div></span></div><div><br></div></div></span></div></div><br></body><=
/html>=

--Boundary_(ID_7A8o7QUXIi2VKm218RcQUA)--

From fred@cisco.com  Sun Oct 10 10:59:18 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B8A263A6826 for <v6ops@core3.amsl.com>; Sun, 10 Oct 2010 10:59:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.264
X-Spam-Level: 
X-Spam-Status: No, score=-110.264 tagged_above=-999 required=5 tests=[AWL=0.334, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hnsKbWktdVaA for <v6ops@core3.amsl.com>; Sun, 10 Oct 2010 10:59:17 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id E6D403A6820 for <v6ops@ietf.org>; Sun, 10 Oct 2010 10:59:17 -0700 (PDT)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApgFAM2bsUyrR7Hu/2dsb2JhbACBRKBKcaA7m3WFSASEUoVvgwM
X-IronPort-AV: E=Sophos;i="4.57,309,1283731200";  d="scan'208,217";a="601876737"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-6.cisco.com with ESMTP; 10 Oct 2010 18:00:28 +0000
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o9AI0Dwc020368; Sun, 10 Oct 2010 18:00:21 GMT
Received: from [127.0.0.1] by stealth-10-32-244-219.cisco.com (PGP Universal service); Sun, 10 Oct 2010 11:00:27 -0700
X-PGP-Universal: processed; by stealth-10-32-244-219.cisco.com on Sun, 10 Oct 2010 11:00:27 -0700
From: Fred Baker <fred@cisco.com>
Date: Sun, 10 Oct 2010 11:00:08 -0700
Message-Id: <C05BE420-A613-4AD4-8A94-73645C4947CB@cisco.com>
To: IPv6 Operations <v6ops@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Content-Type: multipart/alternative; boundary=Apple-Mail-14--811237059
Cc: v6ops-chairs@tools.ietf.org, Ron Bonica <ron@bonica.org>
Subject: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Oct 2010 17:59:18 -0000

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

This is to initiate a two week working group last call of =
draft-ietf-v6ops-v6-in-mobile-networks. Please read it now. If you find =
nits (spelling errors, minor suggested wording changes, etc), comment to =
the authors; if you find greater issues, such as disagreeing with a =
statement or finding additional issues that need to be addressed, please =
post your comments to the list.

We are looking specifically for comments on the importance of the =
document as well as its content. If you have read the document and =
believe it to be of operational utility, that is also an important =
comment to make.=

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

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><font face=3D"Helvetica" size=3D"3" =
style=3D"font: 12.0px Helvetica">This is to initiate a two week working =
group last call of draft-ietf-v6ops-v6-in-mobile-networks. Please read =
it now. If&nbsp;you find nits (spelling errors, minor suggested wording =
changes, etc), comment to the authors; if you find greater&nbsp;issues, =
such as disagreeing with a statement or finding additional issues that =
need to be addressed, please post your&nbsp;comments to the =
list.</font></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
12px/normal Helvetica; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"3" style=3D"font: =
12.0px Helvetica">We are looking specifically for comments on the =
importance of the document as well as its content. If you have read =
the&nbsp;document and believe it to be of operational utility, that is =
also an important comment to make.</font></div> </div></body></html>=

--Apple-Mail-14--811237059--

From cb.list6@gmail.com  Sun Oct 10 11:36:15 2010
Return-Path: <cb.list6@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C87EB3A6820 for <v6ops@core3.amsl.com>; Sun, 10 Oct 2010 11:36:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.117
X-Spam-Level: 
X-Spam-Status: No, score=-2.117 tagged_above=-999 required=5 tests=[AWL=0.482,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z2OVRUwG4dBR for <v6ops@core3.amsl.com>; Sun, 10 Oct 2010 11:36:12 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id 9AEB63A67FB for <v6ops@ietf.org>; Sun, 10 Oct 2010 11:36:12 -0700 (PDT)
Received: by qyk7 with SMTP id 7so2831319qyk.10 for <v6ops@ietf.org>; Sun, 10 Oct 2010 11:37:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=SNTK4E2c5ZOxQ0Twir44EML5cYUF61OdWGy4vwRwUMQ=; b=AK3oDOy39XtuRDsBiBV1EEJRl5A46zV9NQA8ODVhnn5IFyNsPdD9ONFW+OrQImnFm6 R1QhEv5FJnyoVWdYy6/ZhV1+yqgXAssEmO9xw7JpUQdfQad5CGyK/y9rbKVCz1zS60mn YIFfUNuqBbLlhg7hnExB/rlng87PztvqZrLdE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=fVDC7lqEP7llMPjo4QVmdqlz++N8srVcKwb6rj6PjJNA7QVHDk4eshsrl/3mDlGxtV AmLvGFyw8EX/Tp9ZU3qQhYE7UCE4vkDYna1mTSORrU6foV6SG8Wwyf4WV9koyUVeIYJQ m5my2lCy6svWg41aAS5EFVgFMzI9Q5HK5vP+8=
MIME-Version: 1.0
Received: by 10.224.213.9 with SMTP id gu9mr3772678qab.271.1286735842353; Sun, 10 Oct 2010 11:37:22 -0700 (PDT)
Received: by 10.229.245.201 with HTTP; Sun, 10 Oct 2010 11:37:22 -0700 (PDT)
In-Reply-To: <C05BE420-A613-4AD4-8A94-73645C4947CB@cisco.com>
References: <C05BE420-A613-4AD4-8A94-73645C4947CB@cisco.com>
Date: Sun, 10 Oct 2010 11:37:22 -0700
Message-ID: <AANLkTik9X27b80RdKW6+wDFNGREbYTV4Dro6eXJaWqyP@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: Fred Baker <fred@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>, v6ops-chairs@tools.ietf.org, Ron Bonica <ron@bonica.org>
Subject: Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Oct 2010 18:36:16 -0000

On Sun, Oct 10, 2010 at 11:00 AM, Fred Baker <fred@cisco.com> wrote:
> This is to initiate a two week working group last call of
> draft-ietf-v6ops-v6-in-mobile-networks. Please read it now. If=A0you find=
 nits
> (spelling errors, minor suggested wording changes, etc), comment to the
> authors; if you find greater=A0issues, such as disagreeing with a stateme=
nt or
> finding additional issues that need to be addressed, please post
> your=A0comments to the list.
> We are looking specifically for comments on the importance of the documen=
t
> as well as its content. If you have read the=A0document and believe it to=
 be
> of operational utility, that is also an important comment to make.

FYI, some of my comments that have not made it into a new rev yet

http://www.ietf.org/mail-archive/web/v6ops/current/msg05426.html

Cameron
=3D=3D=3D=3D=3D=3D
http://groups.google.com/group/tmoipv6beta
=3D=3D=3D=3D=3D=3D

From rkoodli@cisco.com  Sun Oct 10 13:13:03 2010
Return-Path: <rkoodli@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B421D3A6855 for <v6ops@core3.amsl.com>; Sun, 10 Oct 2010 13:13:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.452
X-Spam-Level: 
X-Spam-Status: No, score=-108.452 tagged_above=-999 required=5 tests=[AWL=0.151, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OFcvXfrUJ+gI for <v6ops@core3.amsl.com>; Sun, 10 Oct 2010 13:13:02 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id E78163A6856 for <v6ops@ietf.org>; Sun, 10 Oct 2010 13:13:01 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai0FAKO7sUytJV2Z/2dsb2JhbAChPFNxoTubcIIXgzEEhFKFb4MJgmA
X-IronPort-AV: E=Sophos;i="4.57,310,1283731200"; d="scan'208";a="168897973"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rtp-iport-1.cisco.com with ESMTP; 10 Oct 2010 20:14:11 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id o9AKEBBA011045;  Sun, 10 Oct 2010 20:14:11 GMT
Received: from xmb-rcd-111.cisco.com ([72.163.62.153]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 10 Oct 2010 15:14:06 -0500
Received: from 10.21.89.80 ([10.21.89.80]) by XMB-RCD-111.cisco.com ([72.163.62.153]) with Microsoft Exchange Server HTTP-DAV ;  Sun, 10 Oct 2010 20:14:02 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Sun, 10 Oct 2010 13:25:45 -0700
From: Rajeev Koodli <rkoodli@cisco.com>
To: Cameron Byrne <cb.list6@gmail.com>, Fred Baker <fred@cisco.com>
Message-ID: <C8D76F59.9B44%rkoodli@cisco.com>
Thread-Topic: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
Thread-Index: ActouVEnnNtr4+oBLE2GxsbcCEBvDw==
In-Reply-To: <AANLkTik9X27b80RdKW6+wDFNGREbYTV4Dro6eXJaWqyP@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-OriginalArrivalTime: 10 Oct 2010 20:14:06.0189 (UTC) FILETIME=[B0A1D1D0:01CB68B7]
Cc: IPv6 Operations <v6ops@ietf.org>, v6ops-chairs@tools.ietf.org, Ron Bonica <ron@bonica.org>
Subject: Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Oct 2010 20:13:04 -0000

Hi Cameron,

Yes, I intend to incorporate the outcome of the ML discussion we had in the
next version.
In the meanwhile, folks may provide input as well, as part of this.

Thanks,

-Rajeev



On 10/10/10 11:37 AM, "Cameron Byrne" <cb.list6@gmail.com> wrote:

> On Sun, Oct 10, 2010 at 11:00 AM, Fred Baker <fred@cisco.com> wrote:
>> This is to initiate a two week working group last call of
>> draft-ietf-v6ops-v6-in-mobile-networks. Please read it now. If=A0you find =
nits
>> (spelling errors, minor suggested wording changes, etc), comment to the
>> authors; if you find greater=A0issues, such as disagreeing with a statemen=
t or
>> finding additional issues that need to be addressed, please post
>> your=A0comments to the list.
>> We are looking specifically for comments on the importance of the docume=
nt
>> as well as its content. If you have read the=A0document and believe it to =
be
>> of operational utility, that is also an important comment to make.
>=20
> FYI, some of my comments that have not made it into a new rev yet
>=20
> http://www.ietf.org/mail-archive/web/v6ops/current/msg05426.html
>=20
> Cameron
> =3D=3D=3D=3D=3D=3D
> http://groups.google.com/group/tmoipv6beta
> =3D=3D=3D=3D=3D=3D
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From root@core3.amsl.com  Sun Oct 10 19:15:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: v6ops@ietf.org
Delivered-To: v6ops@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 4288A3A68B2; Sun, 10 Oct 2010 19:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20101011021502.4288A3A68B2@core3.amsl.com>
Date: Sun, 10 Oct 2010 19:15:02 -0700 (PDT)
Cc: v6ops@ietf.org
Subject: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Oct 2010 02:15:02 -0000

--NextPart

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


	Title           : An Incremental Carrier-Grade NAT (CGN) for IPv6 Transition
	Author(s)       : S. Jiang, D. Guo
	Filename        : draft-ietf-v6ops-incremental-cgn-02.txt
	Pages           : 13
	Date            : 2010-10-10

Global IPv6 deployment was slower than originally expected. As IPv4 
address exhaustion approaches, the IPv4 to IPv6 transition issues 
become more critical and less tractable. Host-based transition 
 
 
 mechanisms used in dual stack environments are not able to meet the 
transition requirements. Most end users are not sufficiently expert 
to configure or maintain host-based transition mechanisms. Carrier-
Grade NAT (CGN) devices with integrated transition mechanisms can 
reduce the operational change required during the IPv4 to IPv6 
migration or coexistence period. 

This document proposes an incremental CGN approach for IPv6 
transition. It can provide IPv6 access services for IPv6-enabled 
hosts and IPv4 access services for IPv4 hosts while leaving much of a 
legacy IPv4 ISP network unchanged. It is suitable for the initial 
stage of IPv4 to IPv6 migration. Unlike NAT444 based CGN alone, 
Incremental CGN also supports and encourages transition towards dual-
stack or IPv6-only ISP networks. A smooth transition to IPv6 
deployment is also described in this document. 

An integrated configurable CGN device and an adaptive Home Gateway 
(HG) device are introduced. Both HG and CGN are re-usable devices 
during different transition periods. It avoids potential multiple 
upgrades. It enables IPv6 migration to be incrementally achieved 
according to the real user requirements.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-incremental-cgn-02.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-v6ops-incremental-cgn-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-10-10190930.I-D@ietf.org>


--NextPart--

From remi.despres@free.fr  Mon Oct 11 00:41:04 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B599F3A68C3 for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 00:41:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.163
X-Spam-Level: 
X-Spam-Status: No, score=-1.163 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a5xs0ZeaGfrg for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 00:40:57 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.21]) by core3.amsl.com (Postfix) with ESMTP id A35B83A67A7 for <v6ops@ietf.org>; Mon, 11 Oct 2010 00:40:53 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2311.sfr.fr (SMTP Server) with ESMTP id 3D32B700008C; Mon, 11 Oct 2010 09:42:04 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2311.sfr.fr (SMTP Server) with ESMTP id BAD3B7000085; Mon, 11 Oct 2010 09:42:03 +0200 (CEST)
X-SFR-UUID: 20101011074203765.BAD3B7000085@msfrf2311.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <20101011021502.4288A3A68B2@core3.amsl.com>
Date: Mon, 11 Oct 2010 09:42:02 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B91ECF5-B59D-464B-B5B0-1DAF69303ED4@free.fr>
References: <20101011021502.4288A3A68B2@core3.amsl.com>
To: Sheng Jiang <shengjiang@huawei.com>, Diang Guo <guoseu@huawei.com>, Brian Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1081)
Cc: v6ops v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Oct 2010 07:41:04 -0000

Hi Sheng, Diang, Brian,

The draft says=20
"[ISPs]... currently face two urgent pressures - to compensate for an =
immediate shortage of IPv4 addresses by deploying some method of address =
sharing, and to prepare actively for the use of deployment of IPv6 =
address space and services. ISPs facing only one pressure out of   two =
could adopt either CGN (for shortage of IPv6 addresses) or 6rd."

This misses the point that 6rd can also be used by ISPs that, to face =
the IPv4 address shortage, operate CGN44s and assign private IPv4 =
addresses to their customers.
This is illustrated in particular in section 4 of RFC 5569:
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
              ______________________________
             |                              |
             | 10.x.x.x/8 private addresses |
             |  <=3D=3D                         |
       <-----|         IPv4 anycast address |----->
             |            of 6rd relays     |
    6rd-CPEs |                      =3D=3D>     |  6rd-relays
             |                              |
       <-----|          0.0.0.0/0           |----->
             |              :               |
             |______________V_______________|
                          __|__
    ISP-supported NAT(s) |     |
                         |_____|
                            |
                            V
                 IPv4 public addresses
          Figure 3: 6rd Applicability to ISPs That Assign
                    IPv4 Private Addresses
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
If a home gateway supports 6rd with the DHCPv4 option introduced in RFC =
5969, the goal of incremental CGN seems to be reached with already =
specified mechanisms.

Thoughts?

Regards,
RD=20



> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the IPv6 Operations Working Group of the =
IETF.
>=20
>=20
> 	Title           : An Incremental Carrier-Grade NAT (CGN) for =
IPv6 Transition
> 	Author(s)       : S. Jiang, D. Guo
> 	Filename        : draft-ietf-v6ops-incremental-cgn-02.txt
> 	Pages           : 13
> 	Date            : 2010-10-10
>=20
> Global IPv6 deployment was slower than originally expected. As IPv4=20
> address exhaustion approaches, the IPv4 to IPv6 transition issues=20
> become more critical and less tractable. Host-based transition=20
>=20
>=20
> mechanisms used in dual stack environments are not able to meet the=20
> transition requirements. Most end users are not sufficiently expert=20
> to configure or maintain host-based transition mechanisms. Carrier-
> Grade NAT (CGN) devices with integrated transition mechanisms can=20
> reduce the operational change required during the IPv4 to IPv6=20
> migration or coexistence period.=20
>=20
> This document proposes an incremental CGN approach for IPv6=20
> transition. It can provide IPv6 access services for IPv6-enabled=20
> hosts and IPv4 access services for IPv4 hosts while leaving much of a=20=

> legacy IPv4 ISP network unchanged. It is suitable for the initial=20
> stage of IPv4 to IPv6 migration. Unlike NAT444 based CGN alone,=20
> Incremental CGN also supports and encourages transition towards dual-
> stack or IPv6-only ISP networks. A smooth transition to IPv6=20
> deployment is also described in this document.=20
>=20
> An integrated configurable CGN device and an adaptive Home Gateway=20
> (HG) device are introduced. Both HG and CGN are re-usable devices=20
> during different transition periods. It avoids potential multiple=20
> upgrades. It enables IPv6 migration to be incrementally achieved=20
> according to the real user requirements.
>=20
> A URL for this Internet-Draft is:
> =
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-incremental-cgn-02.tx=
t
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> <Pi=E8ce jointe Mail>_______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops



From shengjiang@huawei.com  Mon Oct 11 00:58:42 2010
Return-Path: <shengjiang@huawei.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6EC933A6783 for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 00:58:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.15
X-Spam-Level: 
X-Spam-Status: No, score=-0.15 tagged_above=-999 required=5 tests=[AWL=-0.555,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uH88B-vEe6W8 for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 00:58:41 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id CFB493A67A7 for <v6ops@ietf.org>; Mon, 11 Oct 2010 00:58:40 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LA4005KN8TF4S@szxga03-in.huawei.com> for v6ops@ietf.org; Mon, 11 Oct 2010 15:58:30 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LA400AJI8TC5T@szxga03-in.huawei.com> for v6ops@ietf.org; Mon, 11 Oct 2010 15:58:25 +0800 (CST)
Received: from j66104a ([10.110.98.46]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LA400LPN8TB5M@szxml06-in.huawei.com> for v6ops@ietf.org; Mon, 11 Oct 2010 15:58:24 +0800 (CST)
Date: Mon, 11 Oct 2010 15:58:22 +0800
From: Sheng Jiang <shengjiang@huawei.com>
In-reply-to: <3B91ECF5-B59D-464B-B5B0-1DAF69303ED4@free.fr>
To: =?ISO-8859-1?Q?'R=E9mi_Despr=E9s'?= <remi.despres@free.fr>, 'Diang Guo' <guoseu@huawei.com>, 'Brian Carpenter' <brian.e.carpenter@gmail.com>
Message-id: <004401cb691a$13f6d200$2e626e0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
Thread-index: ActpF91oellywieWT42/pXMbekmXSgAAG6cA
Cc: 'v6ops v6ops' <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Oct 2010 07:58:42 -0000

Hi, Remi,

You are right here. You may notice, incremental cgn is an information =
document, which does not
define any concrete mechanisms. It gives guidelines and discuss time =
sequence and steps during
transitioning. 6rd with private Ipv4 addresses is one of concrete =
instance of the certain phase of
incremental cgn. We have already indicated this. Both RFC5569, RFC5969 =
are quoted in the document.

Best regards,

Sheng

> -----Original Message-----
> From: R=E9mi Despr=E9s [mailto:remi.despres@free.fr]=20
> Sent: Monday, October 11, 2010 3:42 PM
> To: Sheng Jiang; Diang Guo; Brian Carpenter
> Cc: v6ops v6ops
> Subject: Re: [v6ops] I-D=20
> Action:draft-ietf-v6ops-incremental-cgn-02.txt
>=20
> Hi Sheng, Diang, Brian,
>=20
> The draft says=20
> "[ISPs]... currently face two urgent pressures - to=20
> compensate for an immediate shortage of IPv4 addresses by=20
> deploying some method of address sharing, and to prepare=20
> actively for the use of deployment of IPv6 address space and=20
> services. ISPs facing only one pressure out of   two could=20
> adopt either CGN (for shortage of IPv6 addresses) or 6rd."
>=20
> This misses the point that 6rd can also be used by ISPs that,=20
> to face the IPv4 address shortage, operate CGN44s and assign=20
> private IPv4 addresses to their customers.
> This is illustrated in particular in section 4 of RFC 5569:
> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>               ______________________________
>              |                              |
>              | 10.x.x.x/8 private addresses |
>              |  <=3D=3D                         |
>        <-----|         IPv4 anycast address |----->
>              |            of 6rd relays     |
>     6rd-CPEs |                      =3D=3D>     |  6rd-relays
>              |                              |
>        <-----|          0.0.0.0/0           |----->
>              |              :               |
>              |______________V_______________|
>                           __|__
>     ISP-supported NAT(s) |     |
>                          |_____|
>                             |
>                             V
>                  IPv4 public addresses
>           Figure 3: 6rd Applicability to ISPs That Assign
>                     IPv4 Private Addresses
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> If a home gateway supports 6rd with the DHCPv4 option=20
> introduced in RFC 5969, the goal of incremental CGN seems to=20
> be reached with already specified mechanisms.
>=20
> Thoughts?
>=20
> Regards,
> RD=20
>=20
>=20
>=20
> > A New Internet-Draft is available from the on-line=20
> Internet-Drafts directories.
> > This draft is a work item of the IPv6 Operations Working=20
> Group of the IETF.
> >=20
> >=20
> > 	Title           : An Incremental Carrier-Grade NAT=20
> (CGN) for IPv6 Transition
> > 	Author(s)       : S. Jiang, D. Guo
> > 	Filename        : draft-ietf-v6ops-incremental-cgn-02.txt
> > 	Pages           : 13
> > 	Date            : 2010-10-10
> >=20
> > Global IPv6 deployment was slower than originally expected. As IPv4=20
> > address exhaustion approaches, the IPv4 to IPv6 transition issues=20
> > become more critical and less tractable. Host-based transition
> >=20
> >=20
> > mechanisms used in dual stack environments are not able to meet the=20
> > transition requirements. Most end users are not=20
> sufficiently expert to=20
> > configure or maintain host-based transition mechanisms.=20
> Carrier- Grade=20
> > NAT (CGN) devices with integrated transition mechanisms can=20
> reduce the=20
> > operational change required during the IPv4 to IPv6 migration or=20
> > coexistence period.
> >=20
> > This document proposes an incremental CGN approach for IPv6=20
> > transition. It can provide IPv6 access services for=20
> IPv6-enabled hosts=20
> > and IPv4 access services for IPv4 hosts while leaving much=20
> of a legacy=20
> > IPv4 ISP network unchanged. It is suitable for the initial stage of=20
> > IPv4 to IPv6 migration. Unlike NAT444 based CGN alone,=20
> Incremental CGN=20
> > also supports and encourages transition towards dual- stack or=20
> > IPv6-only ISP networks. A smooth transition to IPv6=20
> deployment is also=20
> > described in this document.
> >=20
> > An integrated configurable CGN device and an adaptive Home Gateway
> > (HG) device are introduced. Both HG and CGN are re-usable devices=20
> > during different transition periods. It avoids potential multiple=20
> > upgrades. It enables IPv6 migration to be incrementally achieved=20
> > according to the real user requirements.
> >=20
> > A URL for this Internet-Draft is:
> >=20
> http://www.ietf.org/internet-drafts/draft-ietf-v6ops-incremental-cgn-0
> > 2.txt
> >=20
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >=20
> > Below is the data which will enable a MIME compliant mail reader=20
> > implementation to automatically retrieve the ASCII version of the=20
> > Internet-Draft.
> > <Pi=E8ce jointe Mail>_______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
>=20
>=20


From remi.despres@free.fr  Mon Oct 11 01:37:55 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 26D933A6941 for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 01:37:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.165
X-Spam-Level: 
X-Spam-Status: No, score=-1.165 tagged_above=-999 required=5 tests=[AWL=0.184,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d-JG5kMjKOWt for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 01:37:54 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.19]) by core3.amsl.com (Postfix) with ESMTP id 8AC913A6942 for <v6ops@ietf.org>; Mon, 11 Oct 2010 01:37:53 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2302.sfr.fr (SMTP Server) with ESMTP id B11EC7000098; Mon, 11 Oct 2010 10:39:04 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2302.sfr.fr (SMTP Server) with ESMTP id 31BA57000094; Mon, 11 Oct 2010 10:39:01 +0200 (CEST)
X-SFR-UUID: 20101011083904203.31BA57000094@msfrf2302.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <004401cb691a$13f6d200$2e626e0a@china.huawei.com>
Date: Mon, 11 Oct 2010 10:38:59 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr>
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com>
To: Sheng Jiang <shengjiang@huawei.com>
X-Mailer: Apple Mail (2.1081)
Cc: 'v6ops v6ops' <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Oct 2010 08:37:55 -0000

Thanks Sheng for the quick answer.

Yet, in the sentence I quoted, the draft suggests that 6rd is not a =
solution to face both pressures (1. to compensate for an immediate =
shortage of IPv4 addresses by deploying some method of address sharing; =
2.  to prepare actively for the use of deployment of IPv6 address space =
and services).=20

It can be confusing, I believe, for network operators, mobiles operators =
in particular, that have already deployed CGN44s.
For them, 6rd can be the only additional solution they need to address =
both pressures.=20

If the draft can clarify how 6rd and CGN44s can be used jointly to =
address both pressures, without needing any new design, it will IMHO =
serve a very useful purpose in v6ops.=20

But, then, the term "Incremental CGN" remains confusing IMHO=20
CGN44+6rd, or something similar, could be an intuitive name for the =
solution.

Regards,
RD
  =20

Le 11 oct. 2010 =E0 09:58, Sheng Jiang a =E9crit :

> Hi, Remi,
>=20
> You are right here. You may notice, incremental cgn is an information =
document, which does not
> define any concrete mechanisms. It gives guidelines and discuss time =
sequence and steps during
> transitioning. 6rd with private Ipv4 addresses is one of concrete =
instance of the certain phase of
> incremental cgn. We have already indicated this. Both RFC5569, RFC5969 =
are quoted in the document.
>=20
> Best regards,
>=20
> Sheng
>=20
>> -----Original Message-----
>> From: R=E9mi Despr=E9s [mailto:remi.despres@free.fr]=20
>> Sent: Monday, October 11, 2010 3:42 PM
>> To: Sheng Jiang; Diang Guo; Brian Carpenter
>> Cc: v6ops v6ops
>> Subject: Re: [v6ops] I-D=20
>> Action:draft-ietf-v6ops-incremental-cgn-02.txt
>>=20
>> Hi Sheng, Diang, Brian,
>>=20
>> The draft says=20
>> "[ISPs]... currently face two urgent pressures - to=20
>> compensate for an immediate shortage of IPv4 addresses by=20
>> deploying some method of address sharing, and to prepare=20
>> actively for the use of deployment of IPv6 address space and=20
>> services. ISPs facing only one pressure out of   two could=20
>> adopt either CGN (for shortage of IPv6 addresses) or 6rd."
>>=20
>> This misses the point that 6rd can also be used by ISPs that,=20
>> to face the IPv4 address shortage, operate CGN44s and assign=20
>> private IPv4 addresses to their customers.
>> This is illustrated in particular in section 4 of RFC 5569:
>> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>>              ______________________________
>>             |                              |
>>             | 10.x.x.x/8 private addresses |
>>             |  <=3D=3D                         |
>>       <-----|         IPv4 anycast address |----->
>>             |            of 6rd relays     |
>>    6rd-CPEs |                      =3D=3D>     |  6rd-relays
>>             |                              |
>>       <-----|          0.0.0.0/0           |----->
>>             |              :               |
>>             |______________V_______________|
>>                          __|__
>>    ISP-supported NAT(s) |     |
>>                         |_____|
>>                            |
>>                            V
>>                 IPv4 public addresses
>>          Figure 3: 6rd Applicability to ISPs That Assign
>>                    IPv4 Private Addresses
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>=20
>> If a home gateway supports 6rd with the DHCPv4 option=20
>> introduced in RFC 5969, the goal of incremental CGN seems to=20
>> be reached with already specified mechanisms.
>>=20
>> Thoughts?
>>=20
>> Regards,
>> RD=20
>>=20
>>=20
>>=20
>>> A New Internet-Draft is available from the on-line=20
>> Internet-Drafts directories.
>>> This draft is a work item of the IPv6 Operations Working=20
>> Group of the IETF.
>>>=20
>>>=20
>>> 	Title           : An Incremental Carrier-Grade NAT=20
>> (CGN) for IPv6 Transition
>>> 	Author(s)       : S. Jiang, D. Guo
>>> 	Filename        : draft-ietf-v6ops-incremental-cgn-02.txt
>>> 	Pages           : 13
>>> 	Date            : 2010-10-10
>>>=20
>>> Global IPv6 deployment was slower than originally expected. As IPv4=20=

>>> address exhaustion approaches, the IPv4 to IPv6 transition issues=20
>>> become more critical and less tractable. Host-based transition
>>>=20
>>>=20
>>> mechanisms used in dual stack environments are not able to meet the=20=

>>> transition requirements. Most end users are not=20
>> sufficiently expert to=20
>>> configure or maintain host-based transition mechanisms.=20
>> Carrier- Grade=20
>>> NAT (CGN) devices with integrated transition mechanisms can=20
>> reduce the=20
>>> operational change required during the IPv4 to IPv6 migration or=20
>>> coexistence period.
>>>=20
>>> This document proposes an incremental CGN approach for IPv6=20
>>> transition. It can provide IPv6 access services for=20
>> IPv6-enabled hosts=20
>>> and IPv4 access services for IPv4 hosts while leaving much=20
>> of a legacy=20
>>> IPv4 ISP network unchanged. It is suitable for the initial stage of=20=

>>> IPv4 to IPv6 migration. Unlike NAT444 based CGN alone,=20
>> Incremental CGN=20
>>> also supports and encourages transition towards dual- stack or=20
>>> IPv6-only ISP networks. A smooth transition to IPv6=20
>> deployment is also=20
>>> described in this document.
>>>=20
>>> An integrated configurable CGN device and an adaptive Home Gateway
>>> (HG) device are introduced. Both HG and CGN are re-usable devices=20
>>> during different transition periods. It avoids potential multiple=20
>>> upgrades. It enables IPv6 migration to be incrementally achieved=20
>>> according to the real user requirements.
>>>=20
>>> A URL for this Internet-Draft is:
>>>=20
>> =
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-incremental-cgn-0
>>> 2.txt
>>>=20
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>=20
>>> Below is the data which will enable a MIME compliant mail reader=20
>>> implementation to automatically retrieve the ASCII version of the=20
>>> Internet-Draft.
>>> <Pi=E8ce jointe Mail>_______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>=20
>>=20
>=20



From mohamed.boucadair@orange-ftgroup.com  Mon Oct 11 05:03:11 2010
Return-Path: <mohamed.boucadair@orange-ftgroup.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4A1383A69DD for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 05:03:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.557
X-Spam-Level: 
X-Spam-Status: No, score=-2.557 tagged_above=-999 required=5 tests=[AWL=-0.209, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FBiKGyV-nS+j for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 05:03:09 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by core3.amsl.com (Postfix) with ESMTP id 043D73A67EA for <v6ops@ietf.org>; Mon, 11 Oct 2010 05:03:09 -0700 (PDT)
Received: from omfedm05.si.francetelecom.fr (unknown [xx.xx.xx.1]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id A10D022C4A9; Mon, 11 Oct 2010 14:04:19 +0200 (CEST)
Received: from puexch31.nanterre.francetelecom.fr (unknown [10.101.44.29]) by omfedm05.si.francetelecom.fr (ESMTP service) with ESMTP id 5272C35C055; Mon, 11 Oct 2010 14:04:19 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.7]) by puexch31.nanterre.francetelecom.fr ([10.101.44.29]) with mapi; Mon, 11 Oct 2010 14:04:17 +0200
From: <mohamed.boucadair@orange-ftgroup.com>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>, Sheng Jiang <shengjiang@huawei.com>
Date: Mon, 11 Oct 2010 14:04:16 +0200
Thread-Topic: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
Thread-Index: ActpH8t0WJqC4QnFR6mLUj/zKrgNqAACMIBw
Message-ID: <32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr>
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com> <A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr>
In-Reply-To: <A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.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.5.9.395186, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.10.11.113314
Cc: BINET David NCPI/NAD/TIP <david.binet@orange-ftgroup.com>, 'v6ops v6ops' <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Oct 2010 12:03:11 -0000

Dear R=E9mi;

I don't understand well here the underlying rationale to offer v6 over v4 b=
ehind a CGN and then to claim this is to "prepare actively for the use of d=
eployment of IPv6".

If you share the public IP address, you loose one the important aspects of =
6rd: having a global (IPv6) address and therefore to ease inbound connectio=
ns.

IMHO, if we want to encourage the deployment of IPv6, we need to focus on n=
ative deployment and stop with these v6 in v4 tunnelling proposals.=20

Having these proposals about tunnelling over IPv4 is another hurdle we have=
 within our organisation to promote native IPv6 deployment.

Cheers,
Med=20

-----Message d'origine-----
De : v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] De la part de R=
=E9mi Despr=E9s
Envoy=E9 : lundi 11 octobre 2010 10:39
=C0 : Sheng Jiang
Cc : 'v6ops v6ops'
Objet : Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt

Thanks Sheng for the quick answer.

Yet, in the sentence I quoted, the draft suggests that 6rd is not a solutio=
n to face both pressures (1. to compensate for an immediate shortage of IPv=
4 addresses by deploying some method of address sharing; 2.  to prepare act=
ively for the use of deployment of IPv6 address space and services).=20

It can be confusing, I believe, for network operators, mobiles operators in=
 particular, that have already deployed CGN44s.
For them, 6rd can be the only additional solution they need to address both=
 pressures.=20

If the draft can clarify how 6rd and CGN44s can be used jointly to address =
both pressures, without needing any new design, it will IMHO serve a very u=
seful purpose in v6ops.=20

But, then, the term "Incremental CGN" remains confusing IMHO=20
CGN44+6rd, or something similar, could be an intuitive name for the solutio=
n.

Regards,
RD
=20=20=20

Le 11 oct. 2010 =E0 09:58, Sheng Jiang a =E9crit :

> Hi, Remi,
>=20
> You are right here. You may notice, incremental cgn is an information doc=
ument, which does not
> define any concrete mechanisms. It gives guidelines and discuss time sequ=
ence and steps during
> transitioning. 6rd with private Ipv4 addresses is one of concrete instanc=
e of the certain phase of
> incremental cgn. We have already indicated this. Both RFC5569, RFC5969 ar=
e quoted in the document.
>=20
> Best regards,
>=20
> Sheng
>=20
>> -----Original Message-----
>> From: R=E9mi Despr=E9s [mailto:remi.despres@free.fr]=20
>> Sent: Monday, October 11, 2010 3:42 PM
>> To: Sheng Jiang; Diang Guo; Brian Carpenter
>> Cc: v6ops v6ops
>> Subject: Re: [v6ops] I-D=20
>> Action:draft-ietf-v6ops-incremental-cgn-02.txt
>>=20
>> Hi Sheng, Diang, Brian,
>>=20
>> The draft says=20
>> "[ISPs]... currently face two urgent pressures - to=20
>> compensate for an immediate shortage of IPv4 addresses by=20
>> deploying some method of address sharing, and to prepare=20
>> actively for the use of deployment of IPv6 address space and=20
>> services. ISPs facing only one pressure out of   two could=20
>> adopt either CGN (for shortage of IPv6 addresses) or 6rd."
>>=20
>> This misses the point that 6rd can also be used by ISPs that,=20
>> to face the IPv4 address shortage, operate CGN44s and assign=20
>> private IPv4 addresses to their customers.
>> This is illustrated in particular in section 4 of RFC 5569:
>> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>>              ______________________________
>>             |                              |
>>             | 10.x.x.x/8 private addresses |
>>             |  <=3D=3D                         |
>>       <-----|         IPv4 anycast address |----->
>>             |            of 6rd relays     |
>>    6rd-CPEs |                      =3D=3D>     |  6rd-relays
>>             |                              |
>>       <-----|          0.0.0.0/0           |----->
>>             |              :               |
>>             |______________V_______________|
>>                          __|__
>>    ISP-supported NAT(s) |     |
>>                         |_____|
>>                            |
>>                            V
>>                 IPv4 public addresses
>>          Figure 3: 6rd Applicability to ISPs That Assign
>>                    IPv4 Private Addresses
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>=20
>> If a home gateway supports 6rd with the DHCPv4 option=20
>> introduced in RFC 5969, the goal of incremental CGN seems to=20
>> be reached with already specified mechanisms.
>>=20
>> Thoughts?
>>=20
>> Regards,
>> RD=20
>>=20
>>=20
>>=20
>>> A New Internet-Draft is available from the on-line=20
>> Internet-Drafts directories.
>>> This draft is a work item of the IPv6 Operations Working=20
>> Group of the IETF.
>>>=20
>>>=20
>>> 	Title           : An Incremental Carrier-Grade NAT=20
>> (CGN) for IPv6 Transition
>>> 	Author(s)       : S. Jiang, D. Guo
>>> 	Filename        : draft-ietf-v6ops-incremental-cgn-02.txt
>>> 	Pages           : 13
>>> 	Date            : 2010-10-10
>>>=20
>>> Global IPv6 deployment was slower than originally expected. As IPv4=20
>>> address exhaustion approaches, the IPv4 to IPv6 transition issues=20
>>> become more critical and less tractable. Host-based transition
>>>=20
>>>=20
>>> mechanisms used in dual stack environments are not able to meet the=20
>>> transition requirements. Most end users are not=20
>> sufficiently expert to=20
>>> configure or maintain host-based transition mechanisms.=20
>> Carrier- Grade=20
>>> NAT (CGN) devices with integrated transition mechanisms can=20
>> reduce the=20
>>> operational change required during the IPv4 to IPv6 migration or=20
>>> coexistence period.
>>>=20
>>> This document proposes an incremental CGN approach for IPv6=20
>>> transition. It can provide IPv6 access services for=20
>> IPv6-enabled hosts=20
>>> and IPv4 access services for IPv4 hosts while leaving much=20
>> of a legacy=20
>>> IPv4 ISP network unchanged. It is suitable for the initial stage of=20
>>> IPv4 to IPv6 migration. Unlike NAT444 based CGN alone,=20
>> Incremental CGN=20
>>> also supports and encourages transition towards dual- stack or=20
>>> IPv6-only ISP networks. A smooth transition to IPv6=20
>> deployment is also=20
>>> described in this document.
>>>=20
>>> An integrated configurable CGN device and an adaptive Home Gateway
>>> (HG) device are introduced. Both HG and CGN are re-usable devices=20
>>> during different transition periods. It avoids potential multiple=20
>>> upgrades. It enables IPv6 migration to be incrementally achieved=20
>>> according to the real user requirements.
>>>=20
>>> A URL for this Internet-Draft is:
>>>=20
>> http://www.ietf.org/internet-drafts/draft-ietf-v6ops-incremental-cgn-0
>>> 2.txt
>>>=20
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>=20
>>> Below is the data which will enable a MIME compliant mail reader=20
>>> implementation to automatically retrieve the ASCII version of the=20
>>> Internet-Draft.
>>> <Pi=E8ce jointe Mail>_______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>=20
>>=20
>=20


_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

*********************************
This message and any attachments (the "message") are confidential and inten=
ded solely for the addressees.=20
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.=20
France Telecom Group shall not be liable for the message if altered, change=
d or falsified.
If you are not the intended addressee of this message, please cancel it imm=
ediately and inform the sender.
********************************


From remi.despres@free.fr  Mon Oct 11 05:46:38 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3A15D3A69E3 for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 05:46:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.383
X-Spam-Level: 
X-Spam-Status: No, score=0.383 tagged_above=-999 required=5 tests=[AWL=-1.367,  BAYES_20=-0.74, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vOCU6FWayH4w for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 05:46:36 -0700 (PDT)
Received: from smtp22.services.sfr.fr (smtp22.services.sfr.fr [93.17.128.10]) by core3.amsl.com (Postfix) with ESMTP id 7304C3A6A07 for <v6ops@ietf.org>; Mon, 11 Oct 2010 05:46:36 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2204.sfr.fr (SMTP Server) with ESMTP id AC7227000094; Mon, 11 Oct 2010 14:47:47 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2204.sfr.fr (SMTP Server) with ESMTP id CB89F7000092; Mon, 11 Oct 2010 14:47:46 +0200 (CEST)
X-SFR-UUID: 20101011124746833.CB89F7000092@msfrf2204.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr>
Date: Mon, 11 Oct 2010 14:47:46 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <10D0DC0C-33A2-413C-91F5-EA2186A74AE3@free.fr>
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com> <A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr> <32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr>
To: <mohamed.boucadair@orange-ftgroup.com> <mohamed.boucadair@orange-ftgroup.com>
X-Mailer: Apple Mail (2.1081)
Cc: BINET David NCPI/NAD/TIP <david.binet@orange-ftgroup.com>, 'v6ops v6ops' <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Oct 2010 12:46:38 -0000

Hi Med,

Le 11 oct. 2010 =E0 14:04, <mohamed.boucadair@orange-ftgroup.com> =
<mohamed.boucadair@orange-ftgroup.com> a =E9crit :

> Dear R=E9mi;
>=20
> I don't understand well here the underlying rationale to offer v6 over =
v4 behind a CGN and then to claim this is to "prepare actively for the =
use of deployment of IPv6".

In my understanding, rapidly providing native IPv6 addresses to hosts =
leads them to use more and more IPv6, and less and less IPv4.
It does increases IPv6 use AND deployment (not sure about use OF =
deployment).
What is important IMHO is services users get, not underlying mechanics =
used to provide them.


> If you share the public IP address, you loose one the important =
aspects of 6rd: having a global (IPv6) address and therefore to ease =
inbound connections.

There must be a confusion here.
In the CGN44+6rd solution:=20
- IPv6 addresses aren't shared
- Private IPv4 addresses from which they are derived aren't shared =
either (at least where they apply, i.e. in networks behind CGNs).


> IMHO, if we want to encourage the deployment of IPv6, we need to focus =
on native deployment and stop with these v6 in v4 tunnelling proposals.=20=


Note that I am not making any new tunneling proposal here.
I just point out that 6rd is a solution that, combined with CGN44s, =
permits ISPs that have to share IPv4 addresses and want to offer IPv6 =
service to do it without having to switch to dual-stack routing or =
Ipv6-only routing now.


> Having these proposals about tunnelling over IPv4 is another hurdle we =
have within our organisation to promote native IPv6 deployment.

Your organization is obliged in any way to adopt choices that, in view =
of their own constraints, some others find good for them.

Now, if you implicitly talk about 6a44, which is indeed a new tunneling =
mechanism, this isn't a discussion for this thread.
(It has no relationship with incremental CGN or  CGN44+6rd.)
Its purpose is easy deployment of native IPv6 across legacy IPv4-only =
CPEs, a need of many users that want reliable IPv6 connectivity where =
CPEs can't be changed in the short term.

Regards,
RD=20
=20
>=20
> Cheers,
> Med=20
>=20
> -----Message d'origine-----
> De : v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] De la part =
de R=E9mi Despr=E9s
> Envoy=E9 : lundi 11 octobre 2010 10:39
> =C0 : Sheng Jiang
> Cc : 'v6ops v6ops'
> Objet : Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
>=20
> Thanks Sheng for the quick answer.
>=20
> Yet, in the sentence I quoted, the draft suggests that 6rd is not a =
solution to face both pressures (1. to compensate for an immediate =
shortage of IPv4 addresses by deploying some method of address sharing; =
2.  to prepare actively for the use of deployment of IPv6 address space =
and services).=20
>=20
> It can be confusing, I believe, for network operators, mobiles =
operators in particular, that have already deployed CGN44s.
> For them, 6rd can be the only additional solution they need to address =
both pressures.=20
>=20
> If the draft can clarify how 6rd and CGN44s can be used jointly to =
address both pressures, without needing any new design, it will IMHO =
serve a very useful purpose in v6ops.=20
>=20
> But, then, the term "Incremental CGN" remains confusing IMHO=20
> CGN44+6rd, or something similar, could be an intuitive name for the =
solution.
>=20
> Regards,
> RD
>=20
>=20
> Le 11 oct. 2010 =E0 09:58, Sheng Jiang a =E9crit :
>=20
>> Hi, Remi,
>>=20
>> You are right here. You may notice, incremental cgn is an information =
document, which does not
>> define any concrete mechanisms. It gives guidelines and discuss time =
sequence and steps during
>> transitioning. 6rd with private Ipv4 addresses is one of concrete =
instance of the certain phase of
>> incremental cgn. We have already indicated this. Both RFC5569, =
RFC5969 are quoted in the document.
>>=20
>> Best regards,
>>=20
>> Sheng
>>=20
>>> -----Original Message-----
>>> From: R=E9mi Despr=E9s [mailto:remi.despres@free.fr]=20
>>> Sent: Monday, October 11, 2010 3:42 PM
>>> To: Sheng Jiang; Diang Guo; Brian Carpenter
>>> Cc: v6ops v6ops
>>> Subject: Re: [v6ops] I-D=20
>>> Action:draft-ietf-v6ops-incremental-cgn-02.txt
>>>=20
>>> Hi Sheng, Diang, Brian,
>>>=20
>>> The draft says=20
>>> "[ISPs]... currently face two urgent pressures - to=20
>>> compensate for an immediate shortage of IPv4 addresses by=20
>>> deploying some method of address sharing, and to prepare=20
>>> actively for the use of deployment of IPv6 address space and=20
>>> services. ISPs facing only one pressure out of   two could=20
>>> adopt either CGN (for shortage of IPv6 addresses) or 6rd."
>>>=20
>>> This misses the point that 6rd can also be used by ISPs that,=20
>>> to face the IPv4 address shortage, operate CGN44s and assign=20
>>> private IPv4 addresses to their customers.
>>> This is illustrated in particular in section 4 of RFC 5569:
>>> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>>>             ______________________________
>>>            |                              |
>>>            | 10.x.x.x/8 private addresses |
>>>            |  <=3D=3D                         |
>>>      <-----|         IPv4 anycast address |----->
>>>            |            of 6rd relays     |
>>>   6rd-CPEs |                      =3D=3D>     |  6rd-relays
>>>            |                              |
>>>      <-----|          0.0.0.0/0           |----->
>>>            |              :               |
>>>            |______________V_______________|
>>>                         __|__
>>>   ISP-supported NAT(s) |     |
>>>                        |_____|
>>>                           |
>>>                           V
>>>                IPv4 public addresses
>>>         Figure 3: 6rd Applicability to ISPs That Assign
>>>                   IPv4 Private Addresses
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>=20
>>> If a home gateway supports 6rd with the DHCPv4 option=20
>>> introduced in RFC 5969, the goal of incremental CGN seems to=20
>>> be reached with already specified mechanisms.
>>>=20
>>> Thoughts?
>>>=20
>>> Regards,
>>> RD=20
>>>=20
>>>=20
>>>=20
>>>> A New Internet-Draft is available from the on-line=20
>>> Internet-Drafts directories.
>>>> This draft is a work item of the IPv6 Operations Working=20
>>> Group of the IETF.
>>>>=20
>>>>=20
>>>> 	Title           : An Incremental Carrier-Grade NAT=20
>>> (CGN) for IPv6 Transition
>>>> 	Author(s)       : S. Jiang, D. Guo
>>>> 	Filename        : draft-ietf-v6ops-incremental-cgn-02.txt
>>>> 	Pages           : 13
>>>> 	Date            : 2010-10-10
>>>>=20
>>>> Global IPv6 deployment was slower than originally expected. As IPv4=20=

>>>> address exhaustion approaches, the IPv4 to IPv6 transition issues=20=

>>>> become more critical and less tractable. Host-based transition
>>>>=20
>>>>=20
>>>> mechanisms used in dual stack environments are not able to meet the=20=

>>>> transition requirements. Most end users are not=20
>>> sufficiently expert to=20
>>>> configure or maintain host-based transition mechanisms.=20
>>> Carrier- Grade=20
>>>> NAT (CGN) devices with integrated transition mechanisms can=20
>>> reduce the=20
>>>> operational change required during the IPv4 to IPv6 migration or=20
>>>> coexistence period.
>>>>=20
>>>> This document proposes an incremental CGN approach for IPv6=20
>>>> transition. It can provide IPv6 access services for=20
>>> IPv6-enabled hosts=20
>>>> and IPv4 access services for IPv4 hosts while leaving much=20
>>> of a legacy=20
>>>> IPv4 ISP network unchanged. It is suitable for the initial stage of=20=

>>>> IPv4 to IPv6 migration. Unlike NAT444 based CGN alone,=20
>>> Incremental CGN=20
>>>> also supports and encourages transition towards dual- stack or=20
>>>> IPv6-only ISP networks. A smooth transition to IPv6=20
>>> deployment is also=20
>>>> described in this document.
>>>>=20
>>>> An integrated configurable CGN device and an adaptive Home Gateway
>>>> (HG) device are introduced. Both HG and CGN are re-usable devices=20=

>>>> during different transition periods. It avoids potential multiple=20=

>>>> upgrades. It enables IPv6 migration to be incrementally achieved=20
>>>> according to the real user requirements.
>>>>=20
>>>> A URL for this Internet-Draft is:
>>>>=20
>>> =
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-incremental-cgn-0
>>>> 2.txt
>>>>=20
>>>> Internet-Drafts are also available by anonymous FTP at:
>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>=20
>>>> Below is the data which will enable a MIME compliant mail reader=20
>>>> implementation to automatically retrieve the ASCII version of the=20=

>>>> Internet-Draft.
>>>> <Pi=E8ce jointe =
Mail>_______________________________________________
>>>> v6ops mailing list
>>>> v6ops@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>=20
>>>=20
>>=20
>=20
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>=20
> *********************************
> This message and any attachments (the "message") are confidential and =
intended solely for the addressees.=20
> Any unauthorised use or dissemination is prohibited.
> Messages are susceptible to alteration.=20
> France Telecom Group shall not be liable for the message if altered, =
changed or falsified.
> If you are not the intended addressee of this message, please cancel =
it immediately and inform the sender.
> ********************************
>=20



From randy@psg.com  Mon Oct 11 05:54:10 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 324F73A6A22 for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 05:54:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level: 
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.037,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tx09YezIozWW for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 05:54:09 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 4A6473A69F4 for <v6ops@ietf.org>; Mon, 11 Oct 2010 05:54:09 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1P5HuQ-0009xr-LK; Mon, 11 Oct 2010 12:55:19 +0000
Date: Mon, 11 Oct 2010 21:55:17 +0900
Message-ID: <m2ocb0nb2i.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Mohamed Boucadair <mohamed.boucadair@orange-ftgroup.com>
In-Reply-To: <32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr>
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com> <A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr> <32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Oct 2010 12:54:10 -0000

> I don't understand well here the underlying rationale to offer v6 over
> v4 behind a CGN and then to claim this is to "prepare actively for the
> use of deployment of IPv6".

maybe if you dring another 500ml of the cgn koolaid the visions will
come to you.

randy

From brian.e.carpenter@gmail.com  Mon Oct 11 14:29:44 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8694A3A6B86 for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 14:29:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.382
X-Spam-Level: 
X-Spam-Status: No, score=-102.382 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oDhFc-gHZ577 for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 14:29:43 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 572293A6832 for <v6ops@ietf.org>; Mon, 11 Oct 2010 14:29:43 -0700 (PDT)
Received: by vws12 with SMTP id 12so955137vws.31 for <v6ops@ietf.org>; Mon, 11 Oct 2010 14:30:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=C7CR6pnuybjvaX9OTGnTWNIJPzBWW9sfQ+B20m13Vr0=; b=N9PtYeWSNfKm51hv9iy6wwSQDk+yXD+Ch63G8CtO2jMAqo+HZn8hBQS57AiCASWgie VvAEQM/VFOjg1yn0uNTH404XA0lmxO2+Sdpnjw+rbiEgNcOEMvrBjxbUDZz2Ip2iYyc7 WXjOfTjYZHYZwfagpqGVMuupcH1xh2RSRV1ZQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=Vyzql64v97zGrc7chMkGk9dhVWp5urMO+5i3pIuE8J5oW+jhiGNmgdMjD42ylyK4ba fGGQHz8qLmucsVWfwRPq6ekBnLqnzQrC/9GPX2u7o8RrsknTGZd0PnwIIonav+D1saGx WTGgBK0Kfaptd/cnOzOgLsNCu2TIEUPz/kuKE=
Received: by 10.220.200.199 with SMTP id ex7mr2050766vcb.263.1286832655501; Mon, 11 Oct 2010 14:30:55 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.142.15]) by mx.google.com with ESMTPS id x26sm2514453vbw.8.2010.10.11.14.30.52 (version=SSLv3 cipher=RC4-MD5); Mon, 11 Oct 2010 14:30:54 -0700 (PDT)
Message-ID: <4CB38205.1050301@gmail.com>
Date: Tue, 12 Oct 2010 10:30:45 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: mohamed.boucadair@orange-ftgroup.com
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com>	<A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr> <32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 'v6ops v6ops' <v6ops@ietf.org>, BINET David NCPI/NAD/TIP <david.binet@orange-ftgroup.com>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Oct 2010 21:29:44 -0000

Med,

On 2010-10-12 01:04, mohamed.boucadair@orange-ftgroup.com wrote:
...
> IMHO, if we want to encourage the deployment of IPv6, we need to focus on native deployment and stop with these v6 in v4 tunnelling proposals. 

Personally, I agree with you (and Randy). But some operators don't agree
with you, are firmly engaged in the CGN direction, and want guidance on how
to proceed. Just saying "don't" will not help anybody.

    Brian


From randy@psg.com  Mon Oct 11 15:40:25 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8DA223A685B for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 15:40:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.263
X-Spam-Level: 
X-Spam-Status: No, score=-2.263 tagged_above=-999 required=5 tests=[AWL=-0.264, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gzB0XpvWQ0WM for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 15:40:24 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 8CB183A6857 for <v6ops@ietf.org>; Mon, 11 Oct 2010 15:40:24 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1P5R3n-000BLS-Ez; Mon, 11 Oct 2010 22:41:35 +0000
Date: Tue, 12 Oct 2010 07:41:34 +0900
Message-ID: <m2zkukl5cx.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <4CB38205.1050301@gmail.com>
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com> <A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr> <32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr> <4CB38205.1050301@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Oct 2010 22:40:25 -0000

>> IMHO, if we want to encourage the deployment of IPv6, we need to
>> focus on native deployment and stop with these v6 in v4 tunnelling
>> proposals.
> Personally, I agree with you (and Randy). But some operators don't
> agree with you, are firmly engaged in the CGN direction, and want
> guidance on how to proceed. Just saying "don't" will not help anybody.

yes.  i love when my competition is foolish.

but the question is why should we, as the v6ops wg, consider the cgn
part to be v6 deployment?  it is actually tortured v4 deployment.

does it require different tools than punching v6 through any other
entrenched v4 network?  for example, as med pointed out, 6rd and the
other hacks will work.

randy

From yiu_lee@cable.comcast.com  Mon Oct 11 18:15:27 2010
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D65E3A6BC2 for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 18:15:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.228
X-Spam-Level: 
X-Spam-Status: No, score=-104.228 tagged_above=-999 required=5 tests=[AWL=1.868, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CWdqfG9rzv3o for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 18:15:26 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id E56DF3A6BC5 for <v6ops@ietf.org>; Mon, 11 Oct 2010 18:15:25 -0700 (PDT)
Received: from ([24.40.55.42]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.98010032; Mon, 11 Oct 2010 21:16:34 -0400
Received: from PACDCEXCMB04.cable.comcast.com (24.40.15.86) by PACDCEXHUB01.cable.comcast.com (24.40.55.42) with Microsoft SMTP Server id 14.1.218.12; Mon, 11 Oct 2010 21:16:34 -0400
Received: from 68.81.70.196 ([68.81.70.196]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) via Exchange Front-End Server legacywebmail.comcast.com ([24.40.8.152]) with Microsoft Exchange Server HTTP-DAV ; Tue, 12 Oct 2010 01:16:32 +0000
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Mon, 11 Oct 2010 21:16:31 -0400
From: "Yiu L. Lee" <yiu_lee@cable.comcast.com>
To: =?ISO-8859-1?B?UultaQ==?= =?ISO-8859-1?B?IERlc3By6XM=?= <remi.despres@free.fr>, <mohamed.boucadair@orange-ftgroup.com>
Message-ID: <C8D92F2F.3EFC8%yiu_lee@cable.comcast.com>
Thread-Topic: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
Thread-Index: ActpqxoyAPQe0eKgf0mVbO69HhZuKw==
In-Reply-To: <10D0DC0C-33A2-413C-91F5-EA2186A74AE3@free.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Cc: BINET David NCPI/NAD/TIP <david.binet@orange-ftgroup.com>, 'v6ops v6ops' <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2010 01:15:27 -0000

Hi Remi,

> There must be a confusion here.
> In the CGN44+6rd solution:
> - IPv6 addresses aren't shared
> - Private IPv4 addresses from which they are derived aren't shared either (at
> least where they apply, i.e. in networks behind CGNs).
> 
This is true only if there is no overlapped private space. If an overlapped
space is used, a different 6rd domain should be used.

Cheers,
Yiu


From shengjiang@huawei.com  Mon Oct 11 18:32:27 2010
Return-Path: <shengjiang@huawei.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8E5833A67B8 for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 18:32:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[AWL=-0.505,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BRjsG1FV9wBj for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 18:32:26 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id EFAE03A6863 for <v6ops@ietf.org>; Mon, 11 Oct 2010 18:32:25 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LA500FQOLNSUL@szxga04-in.huawei.com> for v6ops@ietf.org; Tue, 12 Oct 2010 09:33:28 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LA500BCZLNSJX@szxga04-in.huawei.com> for v6ops@ietf.org; Tue, 12 Oct 2010 09:33:28 +0800 (CST)
Received: from j66104a ([10.110.98.46]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LA5009KZLNRUD@szxml06-in.huawei.com> for v6ops@ietf.org; Tue, 12 Oct 2010 09:33:28 +0800 (CST)
Date: Tue, 12 Oct 2010 09:33:27 +0800
From: Sheng Jiang <shengjiang@huawei.com>
In-reply-to: <A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr>
To: =?iso-8859-1?Q?'R=E9mi_Despr=E9s'?= <remi.despres@free.fr>
Message-id: <002001cb69ad$789fac20$2e626e0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3664
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable
Thread-index: ActpH/SriHtBh9QATAGLP9ZUbKZF8AAjLuMg
Cc: 'v6ops v6ops' <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2010 01:32:27 -0000

Hi, Remi,

The WGLC on this draft was just ended Sep 23. The 02 version was =
produced to integrate all the
comments we received during the WGLC. It is now submitted for IESG =
evaluation. We are now waiting
for AD comments, and when we get those we can consider additional =
changes. We think our draft
already does explain how CGN and 6rd are complementary.

Regards,

Sheng

> -----Original Message-----
> From: R=E9mi Despr=E9s [mailto:remi.despres@free.fr]=20
> Sent: Monday, October 11, 2010 4:39 PM
> To: Sheng Jiang
> Cc: 'Diang Guo'; 'Brian Carpenter'; 'v6ops v6ops'
> Subject: Re: [v6ops] I-D=20
> Action:draft-ietf-v6ops-incremental-cgn-02.txt
>=20
> Thanks Sheng for the quick answer.
>=20
> Yet, in the sentence I quoted, the draft suggests that 6rd is=20
> not a solution to face both pressures (1. to compensate for=20
> an immediate shortage of IPv4 addresses by deploying some=20
> method of address sharing; 2.  to prepare actively for the=20
> use of deployment of IPv6 address space and services).=20
>=20
> It can be confusing, I believe, for network operators,=20
> mobiles operators in particular, that have already deployed CGN44s.
> For them, 6rd can be the only additional solution they need=20
> to address both pressures.=20
>=20
> If the draft can clarify how 6rd and CGN44s can be used=20
> jointly to address both pressures, without needing any new=20
> design, it will IMHO serve a very useful purpose in v6ops.=20
>=20
> But, then, the term "Incremental CGN" remains confusing IMHO=20
> CGN44+6rd, or something similar, could be an intuitive name=20
> for the solution.
>=20
> Regards,
> RD
>   =20
>=20
> Le 11 oct. 2010 =E0 09:58, Sheng Jiang a =E9crit :
>=20
> > Hi, Remi,
> >=20
> > You are right here. You may notice, incremental cgn is an=20
> information=20
> > document, which does not define any concrete mechanisms. It gives=20
> > guidelines and discuss time sequence and steps during=20
> transitioning.=20
> > 6rd with private Ipv4 addresses is one of concrete instance=20
> of the certain phase of incremental cgn. We have already=20
> indicated this. Both RFC5569, RFC5969 are quoted in the document.
> >=20
> > Best regards,
> >=20
> > Sheng
> >=20
> >> -----Original Message-----
> >> From: R=E9mi Despr=E9s [mailto:remi.despres@free.fr]
> >> Sent: Monday, October 11, 2010 3:42 PM
> >> To: Sheng Jiang; Diang Guo; Brian Carpenter
> >> Cc: v6ops v6ops
> >> Subject: Re: [v6ops] I-D
> >> Action:draft-ietf-v6ops-incremental-cgn-02.txt
> >>=20
> >> Hi Sheng, Diang, Brian,
> >>=20
> >> The draft says
> >> "[ISPs]... currently face two urgent pressures - to=20
> compensate for an=20
> >> immediate shortage of IPv4 addresses by deploying some method of=20
> >> address sharing, and to prepare actively for the use of=20
> deployment of=20
> >> IPv6 address space and
> >> services. ISPs facing only one pressure out of   two could=20
> >> adopt either CGN (for shortage of IPv6 addresses) or 6rd."
> >>=20
> >> This misses the point that 6rd can also be used by ISPs=20
> that, to face=20
> >> the IPv4 address shortage, operate CGN44s and assign private IPv4=20
> >> addresses to their customers.
> >> This is illustrated in particular in section 4 of RFC 5569:
> >> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> >>              ______________________________
> >>             |                              |
> >>             | 10.x.x.x/8 private addresses |
> >>             |  <=3D=3D                         |
> >>       <-----|         IPv4 anycast address |----->
> >>             |            of 6rd relays     |
> >>    6rd-CPEs |                      =3D=3D>     |  6rd-relays
> >>             |                              |
> >>       <-----|          0.0.0.0/0           |----->
> >>             |              :               |
> >>             |______________V_______________|
> >>                          __|__
> >>    ISP-supported NAT(s) |     |
> >>                         |_____|
> >>                            |
> >>                            V
> >>                 IPv4 public addresses
> >>          Figure 3: 6rd Applicability to ISPs That Assign
> >>                    IPv4 Private Addresses
> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>=20
> >> If a home gateway supports 6rd with the DHCPv4 option=20
> introduced in=20
> >> RFC 5969, the goal of incremental CGN seems to be reached with=20
> >> already specified mechanisms.
> >>=20
> >> Thoughts?
> >>=20
> >> Regards,
> >> RD
> >>=20
> >>=20
> >>=20
> >>> A New Internet-Draft is available from the on-line
> >> Internet-Drafts directories.
> >>> This draft is a work item of the IPv6 Operations Working
> >> Group of the IETF.
> >>>=20
> >>>=20
> >>> 	Title           : An Incremental Carrier-Grade NAT=20
> >> (CGN) for IPv6 Transition
> >>> 	Author(s)       : S. Jiang, D. Guo
> >>> 	Filename        : draft-ietf-v6ops-incremental-cgn-02.txt
> >>> 	Pages           : 13
> >>> 	Date            : 2010-10-10
> >>>=20
> >>> Global IPv6 deployment was slower than originally=20
> expected. As IPv4=20
> >>> address exhaustion approaches, the IPv4 to IPv6 transition issues=20
> >>> become more critical and less tractable. Host-based transition
> >>>=20
> >>>=20
> >>> mechanisms used in dual stack environments are not able=20
> to meet the=20
> >>> transition requirements. Most end users are not
> >> sufficiently expert to
> >>> configure or maintain host-based transition mechanisms.=20
> >> Carrier- Grade
> >>> NAT (CGN) devices with integrated transition mechanisms can
> >> reduce the
> >>> operational change required during the IPv4 to IPv6 migration or=20
> >>> coexistence period.
> >>>=20
> >>> This document proposes an incremental CGN approach for IPv6=20
> >>> transition. It can provide IPv6 access services for
> >> IPv6-enabled hosts
> >>> and IPv4 access services for IPv4 hosts while leaving much
> >> of a legacy
> >>> IPv4 ISP network unchanged. It is suitable for the=20
> initial stage of
> >>> IPv4 to IPv6 migration. Unlike NAT444 based CGN alone,
> >> Incremental CGN
> >>> also supports and encourages transition towards dual- stack or=20
> >>> IPv6-only ISP networks. A smooth transition to IPv6
> >> deployment is also
> >>> described in this document.
> >>>=20
> >>> An integrated configurable CGN device and an adaptive Home Gateway
> >>> (HG) device are introduced. Both HG and CGN are re-usable devices=20
> >>> during different transition periods. It avoids potential multiple=20
> >>> upgrades. It enables IPv6 migration to be incrementally achieved=20
> >>> according to the real user requirements.
> >>>=20
> >>> A URL for this Internet-Draft is:
> >>>=20
> >>=20
> http://www.ietf.org/internet-drafts/draft-ietf-v6ops-incremental-cgn-
> >> 0
> >>> 2.txt
> >>>=20
> >>> Internet-Drafts are also available by anonymous FTP at:
> >>> ftp://ftp.ietf.org/internet-drafts/
> >>>=20
> >>> Below is the data which will enable a MIME compliant mail reader=20
> >>> implementation to automatically retrieve the ASCII version of the=20
> >>> Internet-Draft.
> >>> <Pi=E8ce jointe =
Mail>_______________________________________________
> >>> v6ops mailing list
> >>> v6ops@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/v6ops
> >>=20
> >>=20
> >=20
>=20
>=20


From remi.despres@free.fr  Mon Oct 11 23:07:33 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 499DA3A6778 for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 23:07:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.136
X-Spam-Level: 
X-Spam-Status: No, score=-0.136 tagged_above=-999 required=5 tests=[AWL=-0.787, BAYES_50=0.001, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cPRqpkpoOHWQ for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 23:07:32 -0700 (PDT)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.83]) by core3.amsl.com (Postfix) with ESMTP id 3377A3A6407 for <v6ops@ietf.org>; Mon, 11 Oct 2010 23:07:32 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2412.sfr.fr (SMTP Server) with ESMTP id 219097000088; Tue, 12 Oct 2010 08:08:45 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2412.sfr.fr (SMTP Server) with ESMTP id B6F5A7000087; Tue, 12 Oct 2010 08:08:44 +0200 (CEST)
X-SFR-UUID: 20101012060844749.B6F5A7000087@msfrf2412.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <C8D92F2F.3EFC8%yiu_lee@cable.comcast.com>
Date: Tue, 12 Oct 2010 08:08:42 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <90C0E5B3-981D-49C8-958E-E9785C646482@free.fr>
References: <C8D92F2F.3EFC8%yiu_lee@cable.comcast.com>
To: "Yiu L. Lee" <yiu_lee@cable.comcast.com>
X-Mailer: Apple Mail (2.1081)
Cc: BINET David NCPI/NAD/TIP <david.binet@orange-ftgroup.com>, 'v6ops v6ops' <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2010 06:07:33 -0000

Le 12 oct. 2010 =E0 03:16, Yiu L. Lee a =E9crit :

> Hi Remi,
>=20
>> There must be a confusion here.
>> In the CGN44+6rd solution:
>> - IPv6 addresses aren't shared
>> - Private IPv4 addresses from which they are derived aren't shared =
either (at
>> least where they apply, i.e. in networks behind CGNs).
>>=20
> This is true only if there is no overlapped private space. If an =
overlapped
> space is used, a different 6rd domain should be used.

Agreed.
That's what I meant.

Cheers,
RD



From mohamed.boucadair@orange-ftgroup.com  Mon Oct 11 23:26:45 2010
Return-Path: <mohamed.boucadair@orange-ftgroup.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A2D7E3A67B6 for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 23:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[AWL=-0.928, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3, SARE_LWSHORTT=1.24, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6tJFtZmIemTc for <v6ops@core3.amsl.com>; Mon, 11 Oct 2010 23:26:44 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) by core3.amsl.com (Postfix) with ESMTP id CEB5C3A6782 for <v6ops@ietf.org>; Mon, 11 Oct 2010 23:26:43 -0700 (PDT)
Received: from omfeda07.si.francetelecom.fr (unknown [xx.xx.xx.200]) by omfeda12.si.francetelecom.fr (ESMTP service) with ESMTP id 687B33B46AC; Tue, 12 Oct 2010 08:27:56 +0200 (CEST)
Received: from PUEXCH41.nanterre.francetelecom.fr (unknown [10.101.44.30]) by omfeda07.si.francetelecom.fr (ESMTP service) with ESMTP id 3FC0715805B; Tue, 12 Oct 2010 08:27:56 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.7]) by PUEXCH41.nanterre.francetelecom.fr ([10.101.44.30]) with mapi; Tue, 12 Oct 2010 08:27:51 +0200
From: <mohamed.boucadair@orange-ftgroup.com>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Date: Tue, 12 Oct 2010 08:27:50 +0200
Thread-Topic: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
Thread-Index: ActpQoKpUVVqTFm4T+alw21KMgK04gAk5eOw
Message-ID: <28013_1286864876_4CB3FFEC_28013_139102_1_94C682931C08B048B7A8645303FDC9F327C1008C64@PUEXCB1B.nanterre.francetelecom.fr>
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com> <A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr> <32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr> <10D0DC0C-33A2-413C-91F5-EA2186A74AE3@free.fr>
In-Reply-To: <10D0DC0C-33A2-413C-91F5-EA2186A74AE3@free.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.5.9.395186, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.10.12.53315
Cc: David NCPI/NAD/TIP <david.binet@orange-ftgroup.com>, 'v6ops v6ops' <v6ops@ietf.org>, BINET
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2010 06:26:45 -0000

Dear R=E9mi,

I'm not referring to 6a44 but to the IPv6 over IPv4 in a NAT444 model you a=
re proposing.=20

Cheers,
Med=20

-----Message d'origine-----
De : R=E9mi Despr=E9s [mailto:remi.despres@free.fr]=20
Envoy=E9 : lundi 11 octobre 2010 14:48
=C0 : BOUCADAIR Mohamed NCPI/NAD/TIP
Cc : Sheng Jiang; 'v6ops v6ops'; BINET David NCPI/NAD/TIP
Objet : Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt

Hi Med,

Le 11 oct. 2010 =E0 14:04, <mohamed.boucadair@orange-ftgroup.com> <mohamed.=
boucadair@orange-ftgroup.com> a =E9crit :

> Dear R=E9mi;
>=20
> I don't understand well here the underlying rationale to offer v6 over v4=
 behind a CGN and then to claim this is to "prepare actively for the use of=
 deployment of IPv6".

In my understanding, rapidly providing native IPv6 addresses to hosts leads=
 them to use more and more IPv6, and less and less IPv4.
It does increases IPv6 use AND deployment (not sure about use OF deployment=
).
What is important IMHO is services users get, not underlying mechanics used=
 to provide them.


> If you share the public IP address, you loose one the important aspects o=
f 6rd: having a global (IPv6) address and therefore to ease inbound connect=
ions.

There must be a confusion here.
In the CGN44+6rd solution:=20
- IPv6 addresses aren't shared
- Private IPv4 addresses from which they are derived aren't shared either (=
at least where they apply, i.e. in networks behind CGNs).


> IMHO, if we want to encourage the deployment of IPv6, we need to focus on=
 native deployment and stop with these v6 in v4 tunnelling proposals.=20

Note that I am not making any new tunneling proposal here.
I just point out that 6rd is a solution that, combined with CGN44s, permits=
 ISPs that have to share IPv4 addresses and want to offer IPv6 service to d=
o it without having to switch to dual-stack routing or Ipv6-only routing no=
w.


> Having these proposals about tunnelling over IPv4 is another hurdle we ha=
ve within our organisation to promote native IPv6 deployment.

Your organization is obliged in any way to adopt choices that, in view of t=
heir own constraints, some others find good for them.

Now, if you implicitly talk about 6a44, which is indeed a new tunneling mec=
hanism, this isn't a discussion for this thread.
(It has no relationship with incremental CGN or  CGN44+6rd.)
Its purpose is easy deployment of native IPv6 across legacy IPv4-only CPEs,=
 a need of many users that want reliable IPv6 connectivity where CPEs can't=
 be changed in the short term.

Regards,
RD=20
=20
>=20
> Cheers,
> Med=20
>=20
> -----Message d'origine-----
> De : v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] De la part de=
 R=E9mi Despr=E9s
> Envoy=E9 : lundi 11 octobre 2010 10:39
> =C0 : Sheng Jiang
> Cc : 'v6ops v6ops'
> Objet : Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
>=20
> Thanks Sheng for the quick answer.
>=20
> Yet, in the sentence I quoted, the draft suggests that 6rd is not a solut=
ion to face both pressures (1. to compensate for an immediate shortage of I=
Pv4 addresses by deploying some method of address sharing; 2.  to prepare a=
ctively for the use of deployment of IPv6 address space and services).=20
>=20
> It can be confusing, I believe, for network operators, mobiles operators =
in particular, that have already deployed CGN44s.
> For them, 6rd can be the only additional solution they need to address bo=
th pressures.=20
>=20
> If the draft can clarify how 6rd and CGN44s can be used jointly to addres=
s both pressures, without needing any new design, it will IMHO serve a very=
 useful purpose in v6ops.=20
>=20
> But, then, the term "Incremental CGN" remains confusing IMHO=20
> CGN44+6rd, or something similar, could be an intuitive name for the solut=
ion.
>=20
> Regards,
> RD
>=20
>=20
> Le 11 oct. 2010 =E0 09:58, Sheng Jiang a =E9crit :
>=20
>> Hi, Remi,
>>=20
>> You are right here. You may notice, incremental cgn is an information do=
cument, which does not
>> define any concrete mechanisms. It gives guidelines and discuss time seq=
uence and steps during
>> transitioning. 6rd with private Ipv4 addresses is one of concrete instan=
ce of the certain phase of
>> incremental cgn. We have already indicated this. Both RFC5569, RFC5969 a=
re quoted in the document.
>>=20
>> Best regards,
>>=20
>> Sheng
>>=20
>>> -----Original Message-----
>>> From: R=E9mi Despr=E9s [mailto:remi.despres@free.fr]=20
>>> Sent: Monday, October 11, 2010 3:42 PM
>>> To: Sheng Jiang; Diang Guo; Brian Carpenter
>>> Cc: v6ops v6ops
>>> Subject: Re: [v6ops] I-D=20
>>> Action:draft-ietf-v6ops-incremental-cgn-02.txt
>>>=20
>>> Hi Sheng, Diang, Brian,
>>>=20
>>> The draft says=20
>>> "[ISPs]... currently face two urgent pressures - to=20
>>> compensate for an immediate shortage of IPv4 addresses by=20
>>> deploying some method of address sharing, and to prepare=20
>>> actively for the use of deployment of IPv6 address space and=20
>>> services. ISPs facing only one pressure out of   two could=20
>>> adopt either CGN (for shortage of IPv6 addresses) or 6rd."
>>>=20
>>> This misses the point that 6rd can also be used by ISPs that,=20
>>> to face the IPv4 address shortage, operate CGN44s and assign=20
>>> private IPv4 addresses to their customers.
>>> This is illustrated in particular in section 4 of RFC 5569:
>>> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
>>>             ______________________________
>>>            |                              |
>>>            | 10.x.x.x/8 private addresses |
>>>            |  <=3D=3D                         |
>>>      <-----|         IPv4 anycast address |----->
>>>            |            of 6rd relays     |
>>>   6rd-CPEs |                      =3D=3D>     |  6rd-relays
>>>            |                              |
>>>      <-----|          0.0.0.0/0           |----->
>>>            |              :               |
>>>            |______________V_______________|
>>>                         __|__
>>>   ISP-supported NAT(s) |     |
>>>                        |_____|
>>>                           |
>>>                           V
>>>                IPv4 public addresses
>>>         Figure 3: 6rd Applicability to ISPs That Assign
>>>                   IPv4 Private Addresses
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>=20
>>> If a home gateway supports 6rd with the DHCPv4 option=20
>>> introduced in RFC 5969, the goal of incremental CGN seems to=20
>>> be reached with already specified mechanisms.
>>>=20
>>> Thoughts?
>>>=20
>>> Regards,
>>> RD=20
>>>=20
>>>=20
>>>=20
>>>> A New Internet-Draft is available from the on-line=20
>>> Internet-Drafts directories.
>>>> This draft is a work item of the IPv6 Operations Working=20
>>> Group of the IETF.
>>>>=20
>>>>=20
>>>> 	Title           : An Incremental Carrier-Grade NAT=20
>>> (CGN) for IPv6 Transition
>>>> 	Author(s)       : S. Jiang, D. Guo
>>>> 	Filename        : draft-ietf-v6ops-incremental-cgn-02.txt
>>>> 	Pages           : 13
>>>> 	Date            : 2010-10-10
>>>>=20
>>>> Global IPv6 deployment was slower than originally expected. As IPv4=20
>>>> address exhaustion approaches, the IPv4 to IPv6 transition issues=20
>>>> become more critical and less tractable. Host-based transition
>>>>=20
>>>>=20
>>>> mechanisms used in dual stack environments are not able to meet the=20
>>>> transition requirements. Most end users are not=20
>>> sufficiently expert to=20
>>>> configure or maintain host-based transition mechanisms.=20
>>> Carrier- Grade=20
>>>> NAT (CGN) devices with integrated transition mechanisms can=20
>>> reduce the=20
>>>> operational change required during the IPv4 to IPv6 migration or=20
>>>> coexistence period.
>>>>=20
>>>> This document proposes an incremental CGN approach for IPv6=20
>>>> transition. It can provide IPv6 access services for=20
>>> IPv6-enabled hosts=20
>>>> and IPv4 access services for IPv4 hosts while leaving much=20
>>> of a legacy=20
>>>> IPv4 ISP network unchanged. It is suitable for the initial stage of=20
>>>> IPv4 to IPv6 migration. Unlike NAT444 based CGN alone,=20
>>> Incremental CGN=20
>>>> also supports and encourages transition towards dual- stack or=20
>>>> IPv6-only ISP networks. A smooth transition to IPv6=20
>>> deployment is also=20
>>>> described in this document.
>>>>=20
>>>> An integrated configurable CGN device and an adaptive Home Gateway
>>>> (HG) device are introduced. Both HG and CGN are re-usable devices=20
>>>> during different transition periods. It avoids potential multiple=20
>>>> upgrades. It enables IPv6 migration to be incrementally achieved=20
>>>> according to the real user requirements.
>>>>=20
>>>> A URL for this Internet-Draft is:
>>>>=20
>>> http://www.ietf.org/internet-drafts/draft-ietf-v6ops-incremental-cgn-0
>>>> 2.txt
>>>>=20
>>>> Internet-Drafts are also available by anonymous FTP at:
>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>=20
>>>> Below is the data which will enable a MIME compliant mail reader=20
>>>> implementation to automatically retrieve the ASCII version of the=20
>>>> Internet-Draft.
>>>> <Pi=E8ce jointe Mail>_______________________________________________
>>>> v6ops mailing list
>>>> v6ops@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>=20
>>>=20
>>=20
>=20
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>=20
> *********************************
> This message and any attachments (the "message") are confidential and int=
ended solely for the addressees.=20
> Any unauthorised use or dissemination is prohibited.
> Messages are susceptible to alteration.=20
> France Telecom Group shall not be liable for the message if altered, chan=
ged or falsified.
> If you are not the intended addressee of this message, please cancel it i=
mmediately and inform the sender.
> ********************************
>=20



*********************************
This message and any attachments (the "message") are confidential and inten=
ded solely for the addressees.=20
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.=20
France Telecom Group shall not be liable for the message if altered, change=
d or falsified.
If you are not the intended addressee of this message, please cancel it imm=
ediately and inform the sender.
********************************


From fred@cisco.com  Tue Oct 12 06:12:47 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2A6EB3A696E for <v6ops@core3.amsl.com>; Tue, 12 Oct 2010 06:12:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.28
X-Spam-Level: 
X-Spam-Status: No, score=-110.28 tagged_above=-999 required=5 tests=[AWL=0.319, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KQtkknvbSxCe for <v6ops@core3.amsl.com>; Tue, 12 Oct 2010 06:12:45 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 0827E3A67AE for <v6ops@ietf.org>; Tue, 12 Oct 2010 06:12:45 -0700 (PDT)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAPb7s0yrR7Hu/2dsb2JhbAChUXGgTZxqhUgEhFKFb4MD
X-IronPort-AV: E=Sophos;i="4.57,320,1283731200"; d="scan'208";a="370159699"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-1.cisco.com with ESMTP; 12 Oct 2010 13:13:59 +0000
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o9CDDpgu010011 for <v6ops@ietf.org>; Tue, 12 Oct 2010 13:13:54 GMT
Received: from [127.0.0.1] by stealth-10-32-244-219.cisco.com (PGP Universal service); Tue, 12 Oct 2010 06:13:59 -0700
X-PGP-Universal: processed; by stealth-10-32-244-219.cisco.com on Tue, 12 Oct 2010 06:13:59 -0700
From: Fred Baker <fred@cisco.com>
Date: Tue, 12 Oct 2010 06:13:44 -0700
References: <EDC652A26FB23C4EB6384A4584434A040260F225@307622ANEX5.global.avaya.com>
To: IPv6 Operations <v6ops@ietf.org>
Message-Id: <0166838C-6436-4881-8A43-8CE944D92975@cisco.com>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [v6ops] Fwd: [OPS-AREA] reminder: I-D cutoff dates for IETF-79
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2010 13:12:47 -0000

Begin forwarded message:

> From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> Date: October 12, 2010 5:36:31 AM PDT
> To: <ops-chairs@ietf.org>, <ops-area@ietf.org>
> Subject: [OPS-AREA] reminder: I-D cutoff dates for IETF-79
> 
> 
> 
> 
> 
> Just a reminder that the cutoff date for -00 drafts is this Monday,
> October 18, at 24:00 UTC. The date for drafts with higher version
> numbers is the following Monday, October 25, also at 24:00 UTC. Yes,
> IETF 79 is fast approaching!
> 
> Dan
> _______________________________________________
> OPS-AREA mailing list
> OPS-AREA@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-area


From root@core3.amsl.com  Tue Oct 12 11:00:01 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: v6ops@ietf.org
Delivered-To: v6ops@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id D0C3C3A69CE; Tue, 12 Oct 2010 11:00:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20101012180001.D0C3C3A69CE@core3.amsl.com>
Date: Tue, 12 Oct 2010 11:00:01 -0700 (PDT)
Cc: v6ops@ietf.org
Subject: [v6ops] I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2010 18:00:02 -0000

--NextPart

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


	Title           : Recommended Simple Security Capabilities in Customer Premises Equipment for Providing Residential IPv6 Internet Service
	Author(s)       : J. Woodyatt
	Filename        : draft-ietf-v6ops-cpe-simple-security-15.txt
	Pages           : 35
	Date            : 2010-10-12

This document identifies a set of recommendations for the makers of
devices describing how to provide for "simple security" capabilities
at the perimeter of local-area IPv6 networks in Internet-enabled
homes and small offices.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-cpe-simple-security-15.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-v6ops-cpe-simple-security-15.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-10-12105527.I-D@ietf.org>


--NextPart--

From suresh.krishnan@ericsson.com  Tue Oct 12 11:08:29 2010
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7AFED3A6A06 for <v6ops@core3.amsl.com>; Tue, 12 Oct 2010 11:08:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.517
X-Spam-Level: 
X-Spam-Status: No, score=-102.517 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LsHdVpZHR8L8 for <v6ops@core3.amsl.com>; Tue, 12 Oct 2010 11:08:28 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.8]) by core3.amsl.com (Postfix) with ESMTP id 4F7E43A6910 for <v6ops@ietf.org>; Tue, 12 Oct 2010 11:08:28 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id o9CIPfab025294; Tue, 12 Oct 2010 13:26:32 -0500
Received: from [142.133.10.113] (147.117.20.213) by eusaamw0711.eamcs.ericsson.se (147.117.20.179) with Microsoft SMTP Server id 8.2.234.1; Tue, 12 Oct 2010 14:09:26 -0400
Message-ID: <4CB4A413.8060705@ericsson.com>
Date: Tue, 12 Oct 2010 14:08:19 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: Behcet Sarikaya <sarikaya@ieee.org>
References: <4CAAA2B5.1070901@ericsson.com> <744414.39065.qm@web111406.mail.gq1.yahoo.com>
In-Reply-To: <744414.39065.qm@web111406.mail.gq1.yahoo.com>
Content-Type: text/plain; charset="us-ascii"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] Review of draft-sarikaya-v6ops-prefix-delegation-01.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2010 18:08:29 -0000

Hi Behcet,

On 10-10-07 12:40 PM, Behcet Sarikaya wrote:
> Hi Suresh,
>   Thank you for your review.
> Please see inline.
> 
> 
> 
> 
> ----- Original Message ----
>> From: Suresh Krishnan <suresh.krishnan@ericsson.com>
>> To: v6ops@ietf.org
>> Sent: Mon, October 4, 2010 10:59:49 PM
>> Subject: [v6ops] Review of draft-sarikaya-v6ops-prefix-delegation-01.txt
>>
>> Hi,
>>   I have read the draft  draft-sarikaya-v6ops-prefix-delegation-01.txt and I 
>> have a few  comments.
>>
>> Meta-comment
>> ============
>>
>> It is unclear what the goal  of this draft is
>>
>> a) Is it expected to be a recommendation from the IETF  to 3GPP, WiMAX forum 
>> etc. on how to perform DHCPv6-PD in their  networks?
>>
>> (or)
>>
>> b) Is it an Informational document expected to  document how DHCPv6-PD is being 
>> used in these networks?
>>
>> There is more  clarity required here.
> 
> It is more a) than b) I think. That's why the intended status is BCP. What do 
> you think?

It is fine either way, but clarify this in the abstract and/or the 
introduction.

> 
>> Section 3.1
>> ===========
>>
>> * First  paragraph: The text about the relay function is completely wrong. If 
>> the AR and  the >DHCPv6 server are not directly connected, there needs to be at 
>> least one  relay between >them but the relay is certainly not the AR. Can you 
>> please rewrite  this?
> 
> This is an important point that we need to clarify.

Please do so.

> 
> What we have in 3.1 is SLAAC scenario. AR gets the attach trigger and starts the 
> Requesting Router operation of 3633 with DHCP Solicit which is internally 
> generated. Then another part in AR which is DHCP Relay takes this and sends out 
> Relay-Forward message. Pictorially we showed these and following message 
> exchanges as in Fig. 2.
> 
> Do you think we should make DHCP Client- Relay agent communication more explicit 
> in the figure?

Yes.

> 
> 
>> * Same comment about the relay behavior for the sequence diagram.  The AR  
>> either sends Solicit messages (or) relays Solicit messages from  somebody else. 
>> It does not relay-forward its own Solicit messages.
>>
>> * Step  2: Need to refer to RFC3633 for describing how to create the IA_PD.
>>
>> *  Step 7: How is the prefix for the RA derived from the delegated  prefix?
>>
>> Section 3.2
>> ===========
>>
>> * Requires a different sequence  diagram showing DHCPv6 messages originating 
>>from the MN and relay messages from  the AR. This cannot be shared with Section 
>> 3.1
>>
> 
> What we have in Sec. 3.2 is DHCP scenario. AR first gets a prefix using Sec. 
> 3.1.
> Yes you are right, the next part is different, we can have a different diagram 
> there.

OK.

> 
> We will fix the draft based on your other comments, no problem.

I will review the next version when it is available.

Thanks
Suresh


From fred@cisco.com  Tue Oct 12 11:35:22 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF2EB3A6A01; Tue, 12 Oct 2010 11:35:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.994
X-Spam-Level: 
X-Spam-Status: No, score=-109.994 tagged_above=-999 required=5 tests=[AWL=0.005, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W6W7EZo3A6BO; Tue, 12 Oct 2010 11:35:20 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 1AB9C3A6A08; Tue, 12 Oct 2010 11:35:18 -0700 (PDT)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-Files: None : None
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAPdGtEyrR7Ht/2dsb2JhbAChXXGiXZx4hUgEhFKFb4MD
X-IronPort-AV: E=Sophos;i="4.57,321,1283731200"; d="scan'208";a="602892494"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-6.cisco.com with ESMTP; 12 Oct 2010 18:36:24 +0000
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o9CIaHt1014501; Tue, 12 Oct 2010 18:36:19 GMT
Received: from [127.0.0.1] by stealth-10-32-244-219.cisco.com (PGP Universal service); Tue, 12 Oct 2010 11:36:24 -0700
X-PGP-Universal: processed; by stealth-10-32-244-219.cisco.com on Tue, 12 Oct 2010 11:36:24 -0700
From: Fred Baker <fred@cisco.com>
Mime-Version: 1.0 (Apple Message framework v1081)
Date: Tue, 12 Oct 2010 11:36:09 -0700
References: <20101012180001.D0C3C3A69CE@core3.amsl.com>
To: IPv6 Operations <v6ops@ietf.org>
Message-Id: <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com>
X-Mailer: Apple Mail (2.1081)
Content-Type: multipart/mixed; boundary=Apple-Mail-361--636275217
Cc: IESG IESG <iesg@ietf.org>
Subject: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2010 18:35:22 -0000

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

This is a quick consensus check. The CPE Simple Security document is =
about to complete IESG review, and has gone through four revisions in =
the process of IETF Last Call and IESG review. I'd like to the working =
group to quickly ratify (or not) the changes that have been made and the =
current text.

    =
ftp://ftpeng.cisco.com/fred/v6ops/draft-ietf-v6ops-cpe-simple-security-11-=
15.html
    =
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-cpe-simple-security-1=
5.txt
    http://datatracker.ietf.org/doc/draft-ietf-v6ops-cpe-simple-security

If you have any comments, please make them by the weekend. Silence will =
be presumed to be consent.

Begin forwarded message:

> From: Internet-Drafts@ietf.org
> Date: October 12, 2010 11:00:01 AM PDT
> To: i-d-announce@ietf.org
> Cc: v6ops@ietf.org
> Subject: [v6ops] I-D =
Action:draft-ietf-v6ops-cpe-simple-security-15.txt
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the IPv6 Operations Working Group of the =
IETF.
>=20
>=20
> 	Title           : Recommended Simple Security Capabilities in =
Customer Premises Equipment for Providing Residential IPv6 Internet =
Service
> 	Author(s)       : J. Woodyatt
> 	Filename        : draft-ietf-v6ops-cpe-simple-security-15.txt
> 	Pages           : 35
> 	Date            : 2010-10-12
>=20
> This document identifies a set of recommendations for the makers of
> devices describing how to provide for "simple security" capabilities
> at the perimeter of local-area IPv6 networks in Internet-enabled
> homes and small offices.
>=20
> A URL for this Internet-Draft is:
> =
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-cpe-simple-security-1=
5.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.

--Apple-Mail-361--636275217
Content-Disposition: attachment;
	filename="Mail Attachment"
Content-Type: message/external-body;
	name="Mail Attachment"
Content-Transfer-Encoding: 7bit

Content-Type: text/plain<BR>Content-ID: &lt;2010-10-12105527.I-D@ietf.org&gt;<BR><BR>


--Apple-Mail-361--636275217
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


--Apple-Mail-361--636275217--

From brian.e.carpenter@gmail.com  Tue Oct 12 14:58:11 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 640F03A6AA2 for <v6ops@core3.amsl.com>; Tue, 12 Oct 2010 14:58:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.291
X-Spam-Level: 
X-Spam-Status: No, score=-102.291 tagged_above=-999 required=5 tests=[AWL=-0.292, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 87xHkuLlAODC for <v6ops@core3.amsl.com>; Tue, 12 Oct 2010 14:58:08 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 26C9C3A6A9D for <v6ops@ietf.org>; Tue, 12 Oct 2010 14:58:05 -0700 (PDT)
Received: by ewy6 with SMTP id 6so2065056ewy.31 for <v6ops@ietf.org>; Tue, 12 Oct 2010 14:59:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=G7H8uCVwVWRILdw/nWUEDwJPUvvmuzoaqxPnDUiqx58=; b=TTFoAzEEPjnVqZqE3IMo34logySGaa8B886aYwIXzUnNv4PMfAoDeVmHRKQUXoZj03 laYTCc9zhDgNqoOzn/nh64yKTMwece8pPi8BanenxEyAMYa6Vf90zW1EcFe1A82TOKOO ji07uf+F+FvY5RzVYdPJWgMV69lsVc5TBA2/w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=P0fKmlUxhyfZ3VduTVpuy5Tj32V47V/jau1deF5OWX2FmIGmg34R2DUvBHJl44NSSO X/rZ3XpGML9qdjfmVq8BacF8QgNU41zhKdZdmX6PC2MgI9yeYe01+EUJ7v56MowWIXnX 559pbUG4igSqeJ0Ivtnl5cy8VxkLubCjkkTxM=
Received: by 10.213.105.148 with SMTP id t20mr3163450ebo.30.1286920759704; Tue, 12 Oct 2010 14:59:19 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id x54sm3622845eeh.11.2010.10.12.14.59.16 (version=SSLv3 cipher=RC4-MD5); Tue, 12 Oct 2010 14:59:18 -0700 (PDT)
Message-ID: <4CB4DA32.3030507@gmail.com>
Date: Wed, 13 Oct 2010 10:59:14 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com>	<A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr>	<32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr>	<4CB38205.1050301@gmail.com> <m2zkukl5cx.wl%randy@psg.com>
In-Reply-To: <m2zkukl5cx.wl%randy@psg.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2010 21:58:11 -0000

On 2010-10-12 11:41, Randy Bush wrote:
>>> IMHO, if we want to encourage the deployment of IPv6, we need to
>>> focus on native deployment and stop with these v6 in v4 tunnelling
>>> proposals.
>> Personally, I agree with you (and Randy). But some operators don't
>> agree with you, are firmly engaged in the CGN direction, and want
>> guidance on how to proceed. Just saying "don't" will not help anybody.
> 
> yes.  i love when my competition is foolish.
> 
> but the question is why should we, as the v6ops wg, consider the cgn
> part to be v6 deployment?  it is actually tortured v4 deployment.

Well, this gets back to whether coexistence techniques are part of
the v6ops charter, and I understood the conclusion to be yes.
That still doesn't mean that we have to like the technique.

> does it require different tools than punching v6 through any other
> entrenched v4 network?  for example, as med pointed out, 6rd and the
> other hacks will work.

Yes. Various tunneling techniques would work. The document lists
several of them in section 2.2.

   Brian

From randy@psg.com  Tue Oct 12 21:02:19 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 015BD3A6B4C for <v6ops@core3.amsl.com>; Tue, 12 Oct 2010 21:02:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.254
X-Spam-Level: 
X-Spam-Status: No, score=-2.254 tagged_above=-999 required=5 tests=[AWL=-0.255, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a+IiP7Xp5S8f for <v6ops@core3.amsl.com>; Tue, 12 Oct 2010 21:02:18 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 2B8F43A6B4B for <v6ops@ietf.org>; Tue, 12 Oct 2010 21:02:18 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1P5sYu-000Gjq-FA; Wed, 13 Oct 2010 04:03:32 +0000
Date: Wed, 13 Oct 2010 07:03:30 +0300
Message-ID: <m2wrpmivsd.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <4CB4DA32.3030507@gmail.com>
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com> <A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr> <32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr> <4CB38205.1050301@gmail.com> <m2zkukl5cx.wl%randy@psg.com> <4CB4DA32.3030507@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2010 04:02:19 -0000

>> but the question is why should we, as the v6ops wg, consider the cgn
>> part to be v6 deployment?  it is actually tortured v4 deployment.
> Well, this gets back to whether coexistence techniques are part of
> the v6ops charter, and I understood the conclusion to be yes.

ships in the night != coexistence

randy

From fred@cisco.com  Tue Oct 12 22:13:23 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C4D1D3A6B8A for <v6ops@core3.amsl.com>; Tue, 12 Oct 2010 22:13:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.006
X-Spam-Level: 
X-Spam-Status: No, score=-110.006 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gEux6-bQ71tz for <v6ops@core3.amsl.com>; Tue, 12 Oct 2010 22:13:18 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 4AD5F3A6B77 for <v6ops@ietf.org>; Tue, 12 Oct 2010 22:13:18 -0700 (PDT)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAAHdtEyrR7Ht/2dsb2JhbAChU3GhZJxwhUgEhFKFb4MD
X-IronPort-AV: E=Sophos;i="4.57,323,1283731200"; d="scan'208";a="370452064"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-1.cisco.com with ESMTP; 13 Oct 2010 05:14:34 +0000
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o9D5EPXK027214; Wed, 13 Oct 2010 05:14:27 GMT
Received: from [127.0.0.1] by stealth-10-32-244-219.cisco.com (PGP Universal service); Tue, 12 Oct 2010 22:14:34 -0700
X-PGP-Universal: processed; by stealth-10-32-244-219.cisco.com on Tue, 12 Oct 2010 22:14:34 -0700
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <m2wrpmivsd.wl%randy@psg.com>
Date: Tue, 12 Oct 2010 21:30:57 -0700
Message-Id: <C162B318-0BE3-44F6-8485-D65588CF9B7F@cisco.com>
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com> <A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr> <32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr> <4CB38205.1050301@gmail.com> <m2zkukl5cx.wl%randy@psg.com> <4CB4DA32.3030507@gmail.com> <m2wrpmivsd.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2010 05:13:24 -0000

On Oct 12, 2010, at 9:03 PM, Randy Bush wrote:

>>> but the question is why should we, as the v6ops wg, consider the cgn
>>> part to be v6 deployment?  it is actually tortured v4 deployment.
>> Well, this gets back to whether coexistence techniques are part of
>> the v6ops charter, and I understood the conclusion to be yes.
>=20
> ships in the night !=3D coexistence

If everyone does a dual stack deployment, you have ships in the night. =
Is everyone doing a dual stack deployment? Sounds like not necessarily.=

From randy@psg.com  Tue Oct 12 22:18:55 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B367D3A6B71 for <v6ops@core3.amsl.com>; Tue, 12 Oct 2010 22:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.545
X-Spam-Level: 
X-Spam-Status: No, score=-2.545 tagged_above=-999 required=5 tests=[AWL=0.054,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RoErk--QkGUK for <v6ops@core3.amsl.com>; Tue, 12 Oct 2010 22:18:53 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 2D1703A68B3 for <v6ops@ietf.org>; Tue, 12 Oct 2010 22:18:53 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1P5tl1-000Gxy-4g; Wed, 13 Oct 2010 05:20:07 +0000
Date: Wed, 13 Oct 2010 08:20:04 +0300
Message-ID: <m239sais8r.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <C162B318-0BE3-44F6-8485-D65588CF9B7F@cisco.com>
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com> <A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr> <32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr> <4CB38205.1050301@gmail.com> <m2zkukl5cx.wl%randy@psg.com> <4CB4DA32.3030507@gmail.com> <m2wrpmivsd.wl%randy@psg.com> <C162B318-0BE3-44F6-8485-D65588CF9B7F@cisco.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2010 05:18:55 -0000

> If everyone does a dual stack deployment, you have ships in the night.

and we don't need a wg document for it, do we?

> Is everyone doing a dual stack deployment? Sounds like not
> necessarily.

no.  cernet2, for example, does v6 only.  others do v4 only.  neither
needs a major wg effort, documents, ...

some do v4 only but provide v6 tunneling crutches (6rd).  6rd documents
how to do that.  same for the other tunnels.

randy

From joelja@bogus.com  Tue Oct 12 23:09:33 2010
Return-Path: <joelja@bogus.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 943243A6868 for <v6ops@core3.amsl.com>; Tue, 12 Oct 2010 23:09:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.744
X-Spam-Level: 
X-Spam-Status: No, score=-101.744 tagged_above=-999 required=5 tests=[AWL=-0.345, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_37=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o0+KpLPCgyIs for <v6ops@core3.amsl.com>; Tue, 12 Oct 2010 23:09:32 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 5189E3A68C0 for <v6ops@ietf.org>; Tue, 12 Oct 2010 23:09:31 -0700 (PDT)
Received: from joelja-mac.lan (c-98-234-104-156.hsd1.ca.comcast.net [98.234.104.156]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id o9D6AgoD017546 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 13 Oct 2010 06:10:45 GMT (envelope-from joelja@bogus.com)
Message-ID: <4CB54D62.3070308@bogus.com>
Date: Tue, 12 Oct 2010 23:10:42 -0700
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com>	<A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr>	<32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr>	<4CB38205.1050301@gmail.com> <m2zkukl5cx.wl%randy@psg.com>	<4CB4DA32.3030507@gmail.com> <m2wrpmivsd.wl%randy@psg.com>	<C162B318-0BE3-44F6-8485-D65588CF9B7F@cisco.com> <m239sais8r.wl%randy@psg.com>
In-Reply-To: <m239sais8r.wl%randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Wed, 13 Oct 2010 06:10:45 +0000 (UTC)
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2010 06:09:33 -0000

On 10/12/10 10:20 PM, Randy Bush wrote:
>> If everyone does a dual stack deployment, you have ships in the
>> night.
> 
> and we don't need a wg document for it, do we?

nope, but ops people may find a reason to milk along or hop over their
broken v4 access network for the time being. doing it long term seems
like a fools errand. It doesn't seem especially onerous to document what
that might look like if if some of the participants have to hold their
noses.

Ultimately, I belive that mucking about with v4cgn, or indeed v4 a+p is
going to leave one at a competitive disadvantage those those that either
choose not to, or don't have to. That's a problem that will probably
sort itself out,because you can quite easily make your service both
crappier and more expensive by heading in that direction...

>> Is everyone doing a dual stack deployment? Sounds like not 
>> necessarily.
> 
> no.  cernet2, for example, does v6 only.  others do v4 only.
> neither needs a major wg effort, documents, ...
> 
> some do v4 only but provide v6 tunneling crutches (6rd).  6rd
> documents how to do that.  same for the other tunnels.
> 
> randy _______________________________________________ v6ops mailing
> list v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
> 


From randy@psg.com  Tue Oct 12 23:20:07 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C08AB3A6778 for <v6ops@core3.amsl.com>; Tue, 12 Oct 2010 23:20:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.547
X-Spam-Level: 
X-Spam-Status: No, score=-2.547 tagged_above=-999 required=5 tests=[AWL=0.052,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DVmA+91NFFop for <v6ops@core3.amsl.com>; Tue, 12 Oct 2010 23:20:06 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 863813A63EC for <v6ops@ietf.org>; Tue, 12 Oct 2010 23:20:05 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1P5uiE-000HAX-M6; Wed, 13 Oct 2010 06:21:19 +0000
Date: Wed, 13 Oct 2010 09:21:15 +0300
Message-ID: <m2ocayhauc.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <4CB54D62.3070308@bogus.com>
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com> <A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr> <32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr> <4CB38205.1050301@gmail.com> <m2zkukl5cx.wl%randy@psg.com> <4CB4DA32.3030507@gmail.com> <m2wrpmivsd.wl%randy@psg.com> <C162B318-0BE3-44F6-8485-D65588CF9B7F@cisco.com> <m239sais8r.wl%randy@psg.com> <4CB54D62.3070308@bogus.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2010 06:20:07 -0000

> nope, but ops people may find a reason to milk along or hop over their
> broken v4 access network for the time being. doing it long term seems
> like a fools errand. It doesn't seem especially onerous to document what
> that might look like if if some of the participants have to hold their
> noses.

and i said

>> some do v4 only but provide v6 tunneling crutches (6rd).  6rd
>> documents how to do that.  same for the other tunnels.

i.e. the hopping mechanism document how to deal with ipv4 or broken ipv4
networks.

randy

From joelja@bogus.com  Tue Oct 12 23:38:37 2010
Return-Path: <joelja@bogus.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9910E3A6805 for <v6ops@core3.amsl.com>; Tue, 12 Oct 2010 23:38:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.336
X-Spam-Level: 
X-Spam-Status: No, score=-102.336 tagged_above=-999 required=5 tests=[AWL=0.263, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XtPrE0I8SVKs for <v6ops@core3.amsl.com>; Tue, 12 Oct 2010 23:38:36 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 42FC73A63EC for <v6ops@ietf.org>; Tue, 12 Oct 2010 23:38:36 -0700 (PDT)
Received: from [192.168.1.240] (c-98-234-104-156.hsd1.ca.comcast.net [98.234.104.156]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id o9D6djQ0018927 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 13 Oct 2010 06:39:49 GMT (envelope-from joelja@bogus.com)
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com> <A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr> <32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr> <4CB38205.1050301@gmail.com> <m2zkukl5cx.wl%randy@psg.com> <4CB4DA32.3030507@gmail.com> <m2wrpmivsd.wl%randy@psg.com> <C162B318-0BE3-44F6-8485-D65588CF9B7F@cisco.com> <m239sais8r.wl%randy@psg.com> <4CB54D62.3070308@bogus.com> <m2ocayhauc.wl%randy@psg.com>
Message-Id: <5EFCAC5D-3459-45C4-AC33-7EBFC12D3408@bogus.com>
From: Joel Jaeggli <joelja@bogus.com>
To: Randy Bush <randy@psg.com>
In-Reply-To: <m2ocayhauc.wl%randy@psg.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPad Mail (7B405)
Mime-Version: 1.0 (iPad Mail 7B405)
Date: Tue, 12 Oct 2010 23:39:53 -0700
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Wed, 13 Oct 2010 06:39:50 +0000 (UTC)
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2010 06:38:37 -0000

Joel's widget number 2

On Oct 12, 2010, at 23:21, Randy Bush <randy@psg.com> wrote:

>> nope, but ops people may find a reason to milk along or hop over =
their
>> broken v4 access network for the time being. doing it long term seems
>> like a fools errand. It doesn't seem especially onerous to document =
what
>> that might look like if if some of the participants have to hold =
their
>> noses.
>=20
> and i said
>=20
>>> some do v4 only but provide v6 tunneling crutches (6rd).  6rd
>>> documents how to do that.  same for the other tunnels.
>=20
> i.e. the hopping mechanism document how to deal with ipv4 or broken =
ipv4
> networks.

I'm inclined to conclude that 6rd is a tool not the tool. The broken v4 =
network is still there in your 6rd deployment, in fact it's a =
precondition.=20

> randy
>=20

From randy@psg.com  Tue Oct 12 23:41:14 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D8A33A68C5 for <v6ops@core3.amsl.com>; Tue, 12 Oct 2010 23:41: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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rh7cR6upo78R for <v6ops@core3.amsl.com>; Tue, 12 Oct 2010 23:41:13 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 4AAC83A68B1 for <v6ops@ietf.org>; Tue, 12 Oct 2010 23:41:13 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1P5v2i-000HGW-Cc; Wed, 13 Oct 2010 06:42:28 +0000
Date: Wed, 13 Oct 2010 09:42:25 +0300
Message-ID: <m2eibuh9v2.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <5EFCAC5D-3459-45C4-AC33-7EBFC12D3408@bogus.com>
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com> <A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr> <32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr> <4CB38205.1050301@gmail.com> <m2zkukl5cx.wl%randy@psg.com> <4CB4DA32.3030507@gmail.com> <m2wrpmivsd.wl%randy@psg.com> <C162B318-0BE3-44F6-8485-D65588CF9B7F@cisco.com> <m239sais8r.wl%randy@psg.com> <4CB54D62.3070308@bogus.com> <m2ocayhauc.wl%randy@psg.com> <5EFCAC5D-3459-45C4-AC33-7EBFC12D3408@bogus.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2010 06:41:14 -0000

>>>> some do v4 only but provide v6 tunneling crutches (6rd).  6rd
>>>> documents how to do that.  same for the other tunnels.
>> i.e. the hopping mechanism document how to deal with ipv4 or broken
>> ipv4 networks.
> I'm inclined to conclude that 6rd is a tool not the tool. The broken
> v4 network is still there in your 6rd deployment, in fact it's a
> precondition.

yes.  and each tool documents how it punches through v4.

are you advocating that the nat docs should each tell how each and every
tool should be configured to punch it?

randy

From remi.despres@free.fr  Wed Oct 13 00:07:13 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 99CA23A68C5 for <v6ops@core3.amsl.com>; Wed, 13 Oct 2010 00:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.13
X-Spam-Level: 
X-Spam-Status: No, score=-0.13 tagged_above=-999 required=5 tests=[AWL=-0.781,  BAYES_50=0.001, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B8qLsEfp5cV9 for <v6ops@core3.amsl.com>; Wed, 13 Oct 2010 00:07:12 -0700 (PDT)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.82]) by core3.amsl.com (Postfix) with ESMTP id B1E5D3A6877 for <v6ops@ietf.org>; Wed, 13 Oct 2010 00:07:12 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2409.sfr.fr (SMTP Server) with ESMTP id C8F987000088; Wed, 13 Oct 2010 09:08:27 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2409.sfr.fr (SMTP Server) with ESMTP id 327087000082; Wed, 13 Oct 2010 09:08:27 +0200 (CEST)
X-SFR-UUID: 20101013070827206.327087000082@msfrf2409.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <m2eibuh9v2.wl%randy@psg.com>
Date: Wed, 13 Oct 2010 09:08:26 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <322B3197-8153-470F-A516-B473E98C01A9@free.fr>
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com> <A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr> <32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr> <4CB38205.1050301@gmail.com> <m2zkukl5cx.wl%randy@psg.com> <4CB4DA32.3030507@gmail.com> <m2wrpmivsd.wl%randy@psg.com> <C162B318-0BE3-44F6-8485-D65588CF9B7F@cisco.com> <m239sais8r.wl%randy@psg.com> <4CB54D62.3070308@bogus.com> <m2ocayhauc.wl%randy@psg.com> <5EFCAC5D-3459-45C4-AC33-7EBFC12D3408@bogus.com> <m2eibuh9v2.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2010 07:07:13 -0000

Le 13 oct. 2010 =E0 08:42, Randy Bush a =E9crit :

>> I'm inclined to conclude that 6rd is a tool not the tool. The broken
>> v4 network is still there in your 6rd deployment, in fact it's a
>> precondition.
>=20
> yes.  and each tool documents how it punches through v4.
>=20
> are you advocating that the nat docs should each tell how each and =
every
> tool should be configured to punch it?

Just to make sure no readers are confused: 6rd is NOT a NAT punching =
tool.
NAT docs need not to be concerned.

6rd is just a tool to rapidly offer native IPv6 service to some users.
With it, hosts cannot know that part of the traversed network wasn't =
directly routing IPv6.

RD=20



From joelja@bogus.com  Wed Oct 13 00:17:05 2010
Return-Path: <joelja@bogus.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4161A3A6917 for <v6ops@core3.amsl.com>; Wed, 13 Oct 2010 00:17:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.348
X-Spam-Level: 
X-Spam-Status: No, score=-102.348 tagged_above=-999 required=5 tests=[AWL=0.251, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ftgovc1526lI for <v6ops@core3.amsl.com>; Wed, 13 Oct 2010 00:17:03 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 894903A692B for <v6ops@ietf.org>; Wed, 13 Oct 2010 00:17:01 -0700 (PDT)
Received: from [192.168.1.240] (c-98-234-104-156.hsd1.ca.comcast.net [98.234.104.156]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id o9D7IEPn021132 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 13 Oct 2010 07:18:15 GMT (envelope-from joelja@bogus.com)
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com> <A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr> <32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr> <4CB38205.1050301@gmail.com> <m2zkukl5cx.wl%randy@psg.com> <4CB4DA32.3030507@gmail.com> <m2wrpmivsd.wl%randy@psg.com> <C162B318-0BE3-44F6-8485-D65588CF9B7F@cisco.com> <m239sais8r.wl%randy@psg.com> <4CB54D62.3070308@bogus.com> <m2ocayhauc.wl%randy@psg.com> <5EFCAC5D-3459-45C4-AC33-7EBFC12D3408@bogus.com> <m2eibuh9v2.wl%randy@psg.com>
Message-Id: <30BC796F-266F-4686-8ED1-4358229033EB@bogus.com>
From: Joel Jaeggli <joelja@bogus.com>
To: Randy Bush <randy@psg.com>
In-Reply-To: <m2eibuh9v2.wl%randy@psg.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPad Mail (7B405)
Mime-Version: 1.0 (iPad Mail 7B405)
Date: Wed, 13 Oct 2010 00:18:23 -0700
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Wed, 13 Oct 2010 07:18:16 +0000 (UTC)
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2010 07:17:05 -0000

Joel's widget number 2

On Oct 12, 2010, at 23:42, Randy Bush <randy@psg.com> wrote:

>>>>> some do v4 only but provide v6 tunneling crutches (6rd).  6rd
>>>>> documents how to do that.  same for the other tunnels.
>>> i.e. the hopping mechanism document how to deal with ipv4 or broken
>>> ipv4 networks.
>> I'm inclined to conclude that 6rd is a tool not the tool. The broken
>> v4 network is still there in your 6rd deployment, in fact it's a
>> precondition.
>=20
> yes.  and each tool documents how it punches through v4.
>=20
> are you advocating that the nat docs should each tell how each and =
every
> tool should be configured to punch it?

No, I would be satisfied with characterizing the level of harm a =
particular approach inflicts.=20

> randy
>=20

From randy@psg.com  Wed Oct 13 00:23:19 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D8E93A6916 for <v6ops@core3.amsl.com>; Wed, 13 Oct 2010 00:23:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.55
X-Spam-Level: 
X-Spam-Status: No, score=-2.55 tagged_above=-999 required=5 tests=[AWL=0.049,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gU7VH57REta5 for <v6ops@core3.amsl.com>; Wed, 13 Oct 2010 00:23:18 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id AD1FE3A6877 for <v6ops@ietf.org>; Wed, 13 Oct 2010 00:23:18 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1P5vhQ-000HNQ-K5; Wed, 13 Oct 2010 07:24:33 +0000
Date: Wed, 13 Oct 2010 10:24:29 +0300
Message-ID: <m28w22h7wy.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Joel Jaeggli <joelja@bogus.com>
In-Reply-To: <30BC796F-266F-4686-8ED1-4358229033EB@bogus.com>
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com> <A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr> <32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr> <4CB38205.1050301@gmail.com> <m2zkukl5cx.wl%randy@psg.com> <4CB4DA32.3030507@gmail.com> <m2wrpmivsd.wl%randy@psg.com> <C162B318-0BE3-44F6-8485-D65588CF9B7F@cisco.com> <m239sais8r.wl%randy@psg.com> <4CB54D62.3070308@bogus.com> <m2ocayhauc.wl%randy@psg.com> <5EFCAC5D-3459-45C4-AC33-7EBFC12D3408@bogus.com> <m2eibuh9v2.wl%randy@psg.com> <30BC796F-266F-4686-8ED1-4358229033EB@bogus.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2010 07:23:19 -0000

>>>>>> some do v4 only but provide v6 tunneling crutches (6rd).  6rd
>>>>>> documents how to do that.  same for the other tunnels.
>>>> i.e. the hopping mechanism document how to deal with ipv4 or broken
>>>> ipv4 networks.
>>> I'm inclined to conclude that 6rd is a tool not the tool. The broken
>>> v4 network is still there in your 6rd deployment, in fact it's a
>>> precondition.
>> yes.  and each tool documents how it punches through v4.
>> are you advocating that the nat docs should each tell how each and every
>> tool should be configured to punch it?
> No, I would be satisfied with characterizing the level of harm a
> particular approach inflicts.

then we're on the same page.  a cgn doc should warn of any issues it
creates in both v4 and v6.  and this is what i thought behave was
supposed to be doing.

randy

From tjc@ecs.soton.ac.uk  Wed Oct 13 02:40:34 2010
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B4D853A6A05 for <v6ops@core3.amsl.com>; Wed, 13 Oct 2010 02:40:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.226
X-Spam-Level: 
X-Spam-Status: No, score=-2.226 tagged_above=-999 required=5 tests=[AWL=-0.227, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZfUrQw5kSR-r for <v6ops@core3.amsl.com>; Wed, 13 Oct 2010 02:40:25 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [152.78.68.146]) by core3.amsl.com (Postfix) with ESMTP id F3C383A69CE for <v6ops@ietf.org>; Wed, 13 Oct 2010 02:40: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 o9D9eM36032490 for <v6ops@ietf.org>; Wed, 13 Oct 2010 10:40:22 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk o9D9eM36032490
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1286962823; bh=+uF7le92OfTFUpnZu8in1X3/QsA=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=FZFLIGquzoEqpxdVSKQL9LZcl1Fpd2TTUHKQA4u6oBs83crni7ee8ACHFDOaM8DtZ e76JRBVmslDYC5PqLNyISyA5al1UbKLXQ9Pduklt65d25xvMoeSVFXfSW9vUi+MEcb HDjwnsDRc8zkw23ohCBvj38hAzbagYehiUOJOWt8=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id m9CAeM2308237453G8 ret-id none; Wed, 13 Oct 2010 10:40:23 +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 o9D9eFHT012868 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <v6ops@ietf.org>; Wed, 13 Oct 2010 10:40:16 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <C162B318-0BE3-44F6-8485-D65588CF9B7F@cisco.com>
Date: Wed, 13 Oct 2010 10:40:15 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|76d1da44b7879b5f1b5877a5f1e8cbf0m9CAeM03tjc|ecs.soton.ac.uk|7C6CD044-B91D-45E7-B3ED-01B7595423B0@ecs.soton.ac.uk>
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com> <A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr> <32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr> <4CB38205.1050301@gmail.com> <m2zkukl5cx.wl%randy@psg.com> <4CB4DA32.3030507@gmail.com> <m2wrpmivsd.wl%randy@psg.com> <C162B318-0BE3-44F6-8485-D65588CF9B7F@cisco.com> <7C6CD044-B91D-45E7-B3ED-01B7595423B0@ecs.soton.ac.uk>
To: IPv6 Ops WG <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1081)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=m9CAeM230823745300; tid=m9CAeM2308237453G8; 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: o9D9eM36032490
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2010 09:40:34 -0000

On 13 Oct 2010, at 05:30, Fred Baker wrote:

>=20
> On Oct 12, 2010, at 9:03 PM, Randy Bush wrote:
>=20
>>>> but the question is why should we, as the v6ops wg, consider the =
cgn
>>>> part to be v6 deployment?  it is actually tortured v4 deployment.
>>> Well, this gets back to whether coexistence techniques are part of
>>> the v6ops charter, and I understood the conclusion to be yes.
>>=20
>> ships in the night !=3D coexistence
>=20
> If everyone does a dual stack deployment, you have ships in the night. =
Is everyone doing a dual stack deployment? Sounds like not necessarily.

Having run a dual-stack site for a few years, yes the network =
perspective may be ships in the night, but really I don't want to manage =
two networks, I want to manage one.   Finding the tools that are aware =
of both protocols, and let you manage them in a consistent manner is, in =
my view, very important.    You might have separate IPv4 and IPv6 =
firewall appliances for example, but being able to apply a common =
implementation on policy across both, through a single =
interface/toolset, is highly desirable.

We're watching NAT64-style developments closely to determine when =
IPv6-only internally might be realistic.   At the moment dual-stack =
works for us, but I would imagine many greenfield networks will be =
pushing the NAT64 approach and we hope to learn from them.

Tim


From remi.despres@free.fr  Wed Oct 13 05:43:34 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C3883A6A3F for <v6ops@core3.amsl.com>; Wed, 13 Oct 2010 05:43:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.423
X-Spam-Level: 
X-Spam-Status: No, score=-1.423 tagged_above=-999 required=5 tests=[AWL=0.526,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K3oUaD2z464P for <v6ops@core3.amsl.com>; Wed, 13 Oct 2010 05:43:33 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.22]) by core3.amsl.com (Postfix) with ESMTP id 546603A68ED for <v6ops@ietf.org>; Wed, 13 Oct 2010 05:43:33 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2317.sfr.fr (SMTP Server) with ESMTP id 4C6697000088; Wed, 13 Oct 2010 14:44:49 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2317.sfr.fr (SMTP Server) with ESMTP id DBE537000096; Wed, 13 Oct 2010 14:44:48 +0200 (CEST)
X-SFR-UUID: 20101013124448900.DBE537000096@msfrf2317.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <EMEW3|76d1da44b7879b5f1b5877a5f1e8cbf0m9CAeM03tjc|ecs.soton.ac.uk|7C6CD044-B91D-45E7-B3ED-01B7595423B0@ecs.soton.ac.uk>
Date: Wed, 13 Oct 2010 14:44:45 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <4621C4CA-7914-46DC-B05C-A5F1260FF50D@free.fr>
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com> <A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr> <32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr> <4CB38205.1050301@gmail.com> <m2zkukl5cx.wl%randy@psg.com> <4CB4DA32.3030507@gmail.com> <m2wrpmivsd.wl%randy@psg.com> <C162B318-0BE3-44F6-8485-D65588CF9B7F@cisco.com> <7C6CD044-B91D-45E7-B3ED-01B7595423B0@ecs.soton.ac.uk> <EMEW3|76d1da44b7879b5f1b5877a5f1e8cbf0m9CAeM03tjc|ecs.soton.ac.uk|7C6CD044-B91D-45E7-B3ED-01B7595423B0@ecs.soton.ac.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] Determining "when IPv6-only internally might be realistic"
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2010 12:43:34 -0000

Hi Tim,

On 13 oct. 2010 at 11:40, Tim Chown wrote:
> ...
> We're watching NAT64-style developments closely to determine when =
IPv6-only internally might be realistic.

You may also be interested in closely watching SAM/4rd.
It is a simplified alternative to NAT64, and to DS-lite, to maintain =
IPv4 connectivity across IPv6-only routing networks (including when  =
IPv4 addresses have to be shared among customer sites).
It can coexist with NAT64 and/or DS-lite if these solutions are =
previously deployed.

The current specification is =
tools.ietf.org/html/draft-despres-softwire-sam-01 - section 3.2.
I plan to have by Monday an updated draft whos title is "Global IPv4 =
Residual Deployment across IPv6 Networks (4rd) - a Stateless Solution";

Regards,
RD
 =20



From brian.e.carpenter@gmail.com  Wed Oct 13 14:06:39 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF2373A69C1 for <v6ops@core3.amsl.com>; Wed, 13 Oct 2010 14:06:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.589
X-Spam-Level: 
X-Spam-Status: No, score=-102.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4e15TImdAnKG for <v6ops@core3.amsl.com>; Wed, 13 Oct 2010 14:06:38 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 8CFA33A696C for <v6ops@ietf.org>; Wed, 13 Oct 2010 14:06:38 -0700 (PDT)
Received: by wwj40 with SMTP id 40so4712022wwj.13 for <v6ops@ietf.org>; Wed, 13 Oct 2010 14:07:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=pQtZW5ZFpUtkazcIjO2m02xpvmoFm7dtZhY9/ADGT4g=; b=QH41tkktjwEdbl3GULOXHGdnllkPmbArT3cLi7YRLdjwZtDGzVDqeL9ijRedlK4wjV OKLiNAnCYfDa+kEl2SKCOdfHcfU1WANtIMd7x+hXmILMAsfrK+S5VkQVBYjNTzS19omO R4Disz4Uzu745Vle/6koIDkUqTvz9wwUDCQT0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=JiGlBRhgVfCK2/QexGtqlpz+T//RfQjhz6B+wEw6TcA5i3GLm95oRJLbopRCJPKrKH 9L/P2VYrdVMzoL1t8w8X/B8Lje+iyxW13Hm6jBp0AgJ+EEAVgIGDl7FuLU9OvsMvJAiQ WuuT/q4/5X8bcXKgQnQSqDblU527BM+gK2Mm0=
Received: by 10.227.135.15 with SMTP id l15mr8984054wbt.203.1287004075385; Wed, 13 Oct 2010 14:07:55 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id g9sm8710779wbh.7.2010.10.13.14.07.51 (version=SSLv3 cipher=RC4-MD5); Wed, 13 Oct 2010 14:07:54 -0700 (PDT)
Message-ID: <4CB61FA5.8000409@gmail.com>
Date: Thu, 14 Oct 2010 10:07:49 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
References: <004401cb691a$13f6d200$2e626e0a@china.huawei.com>	<A71390EF-1CB2-4D8C-8F8E-A8A4E38A6AB0@free.fr>	<32260_1286798659_4CB2FD43_32260_11327_1_94C682931C08B048B7A8645303FDC9F327C100899E@PUEXCB1B.nanterre.francetelecom.fr>	<4CB38205.1050301@gmail.com> <m2zkukl5cx.wl%randy@psg.com>	<4CB4DA32.3030507@gmail.com> <m2wrpmivsd.wl%randy@psg.com>	<C162B318-0BE3-44F6-8485-D65588CF9B7F@cisco.com>	<m239sais8r.wl%randy@psg.com> <4CB54D62.3070308@bogus.com>	<m2ocayhauc.wl%randy@psg.com>	<5EFCAC5D-3459-45C4-AC33-7EBFC12D3408@bogus.com>	<m2eibuh9v2.wl%randy@psg.com>	<30BC796F-266F-4686-8ED1-4358229033EB@bogus.com> <m28w22h7wy.wl%randy@psg.com>
In-Reply-To: <m28w22h7wy.wl%randy@psg.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-incremental-cgn-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2010 21:06:39 -0000

On 2010-10-13 20:24, Randy Bush wrote:
>>>>>>> some do v4 only but provide v6 tunneling crutches (6rd).  6rd
>>>>>>> documents how to do that.  same for the other tunnels.
>>>>> i.e. the hopping mechanism document how to deal with ipv4 or broken
>>>>> ipv4 networks.
>>>> I'm inclined to conclude that 6rd is a tool not the tool. The broken
>>>> v4 network is still there in your 6rd deployment, in fact it's a
>>>> precondition.
>>> yes.  and each tool documents how it punches through v4.
>>> are you advocating that the nat docs should each tell how each and every
>>> tool should be configured to punch it?
>> No, I would be satisfied with characterizing the level of harm a
>> particular approach inflicts.
> 
> then we're on the same page.  a cgn doc should warn of any issues it
> creates in both v4 and v6.  and this is what i thought behave was
> supposed to be doing.

Our draft says:

"2.7. Discussion

   For IPv4 traffic, the incremental CGN approach inherits all the
   problems of CGN address sharing techniques
   [I-D.ietf-intarea-shared-addressing-issues] (e.g., scaling, and the
   difficulty of supporting well-known ports for inbound traffic).
   Application layer problems created by double NAT are for further
   study."

I tend to agree that expansion on this point belongs in BEHAVE.

     Brian

From ipng@69706e6720323030352d30312d31340a.nosense.org  Thu Oct 14 03:20:00 2010
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B90793A69BC; Thu, 14 Oct 2010 03:19:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.665
X-Spam-Level: 
X-Spam-Status: No, score=-1.665 tagged_above=-999 required=5 tests=[AWL=0.230,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SoUMbqb8bsr6; Thu, 14 Oct 2010 03:19:58 -0700 (PDT)
Received: from smtp1.adam.net.au (smtp1.adam.net.au [202.136.110.253]) by core3.amsl.com (Postfix) with ESMTP id EEE7C3A67A7; Thu, 14 Oct 2010 03:19:57 -0700 (PDT)
Received: from 219-90-190-11.ip.adam.com.au ([219.90.190.11] helo=opy.nosense.org) by smtp1.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1P6Kvv-0001xw-NB; Thu, 14 Oct 2010 20:51:11 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id DB15D3B325; Thu, 14 Oct 2010 20:51:10 +1030 (CST)
Date: Thu, 14 Oct 2010 20:51:09 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Fred Baker <fred@cisco.com>
Message-ID: <20101014205109.75a23d68@opy.nosense.org>
In-Reply-To: <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com> <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com>
X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, IESG IESG <iesg@ietf.org>
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 10:20:01 -0000

Hi Fred,

I'm really quite concerned about this new text,

REC-13: By DEFAULT, Internet gateways SHOULD, automatically download
   and install software updates for extending IPv6 simple security for
   support of future standard upper layer transports and extension
   headers.

in particular the automatic install, as I don't think the
consequences of automatically updating the firmware "behind the
customers back" have been fully considered. 

If there are any failures with this mechanism at all, the customer
will most likely be calling the ISP, not the product vendor, despite the
vendor being in control of and responsible for when this new firmware is
deployed. It will appear to the customer that the ISP's service has
failed. As an update is likely to be pushed out to many CPE at once,
that could result in floods of 100s, 1000s etc. of unexpected calls to
the ISP's helpdesk moments after the update occurs. It could also mean
that updates occur in the middle of when the ISP's services are most
used due to differing time zones between when the vendor pushes new
firmware out verses and when customers are most commonly using the
Internet services.  In this scenario the ISP should be in control of
when these updates are made available.

Following the model used by vendors of desktop OSes these days, it
would be better if when updates were pushed out, the customer was
alerted to an update being available, and the customer had to somehow
manually trigger the update, to avoid disrupting services. 

I think it'd probably be better to make only a passing comment about
keeping the firmware up to date, avoiding it being a specific SHOULD
recommendation, without details, in this document. The Broadband Forum,
with mechanisms such as TR-69, seem to be more thoroughly considering
these issues.

Regards,
Mark.



On Tue, 12 Oct 2010 11:36:09 -0700
Fred Baker <fred@cisco.com> wrote:

> This is a quick consensus check. The CPE Simple Security document is about to complete IESG review, and has gone through four revisions in the process of IETF Last Call and IESG review. I'd like to the working group to quickly ratify (or not) the changes that have been made and the current text.
> 
>     ftp://ftpeng.cisco.com/fred/v6ops/draft-ietf-v6ops-cpe-simple-security-11-15.html
>     http://www.ietf.org/internet-drafts/draft-ietf-v6ops-cpe-simple-security-15.txt
>     http://datatracker.ietf.org/doc/draft-ietf-v6ops-cpe-simple-security
> 
> If you have any comments, please make them by the weekend. Silence will be presumed to be consent.
> 
> Begin forwarded message:
> 
> > From: Internet-Drafts@ietf.org
> > Date: October 12, 2010 11:00:01 AM PDT
> > To: i-d-announce@ietf.org
> > Cc: v6ops@ietf.org
> > Subject: [v6ops] I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
> > 
> > A New Internet-Draft is available from the on-line Internet-Drafts directories.
> > This draft is a work item of the IPv6 Operations Working Group of the IETF.
> > 
> > 
> > 	Title           : Recommended Simple Security Capabilities in Customer Premises Equipment for Providing Residential IPv6 Internet Service
> > 	Author(s)       : J. Woodyatt
> > 	Filename        : draft-ietf-v6ops-cpe-simple-security-15.txt
> > 	Pages           : 35
> > 	Date            : 2010-10-12
> > 
> > This document identifies a set of recommendations for the makers of
> > devices describing how to provide for "simple security" capabilities
> > at the perimeter of local-area IPv6 networks in Internet-enabled
> > homes and small offices.
> > 
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-v6ops-cpe-simple-security-15.txt
> > 
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> > 
> > Below is the data which will enable a MIME compliant mail reader
> > implementation to automatically retrieve the ASCII version of the
> > Internet-Draft.

From behcetsarikaya@yahoo.com  Thu Oct 14 07:36:06 2010
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3A7773A69DC for <v6ops@core3.amsl.com>; Thu, 14 Oct 2010 07:36:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.92
X-Spam-Level: 
X-Spam-Status: No, score=-0.92 tagged_above=-999 required=5 tests=[AWL=-0.921,  BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fDAa9WZ6B4qi for <v6ops@core3.amsl.com>; Thu, 14 Oct 2010 07:36:04 -0700 (PDT)
Received: from nm17-vm0.bullet.mail.sp2.yahoo.com (nm17-vm0.bullet.mail.sp2.yahoo.com [98.139.91.212]) by core3.amsl.com (Postfix) with SMTP id 9DBC03A67AE for <v6ops@ietf.org>; Thu, 14 Oct 2010 07:36:03 -0700 (PDT)
Received: from [98.139.91.69] by nm17.bullet.mail.sp2.yahoo.com with NNFMP; 14 Oct 2010 14:37:20 -0000
Received: from [98.139.91.60] by tm9.bullet.mail.sp2.yahoo.com with NNFMP; 14 Oct 2010 14:37:20 -0000
Received: from [127.0.0.1] by omp1060.mail.sp2.yahoo.com with NNFMP; 14 Oct 2010 14:37:20 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 114141.74754.bm@omp1060.mail.sp2.yahoo.com
Received: (qmail 83231 invoked by uid 60001); 14 Oct 2010 14:37:19 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1287067039; bh=NN/k5Uamdd5R3yicGiu+2aIFVlO+KFHjPiKzGXsIgow=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=a8E8CdKS6xhL3j4x8ayRVngDh5re7yEFI39PyqbQ1MZAUv1iLm7rh+zETh3dcPRXLBA2wNy4nC811xYSo4p7BZfyWB/Mm1exuRZRJzjaA4uLx53+haoKiIg04vQE4s7kx1Z+V7VdKq7GMge0VNsCuJat1zdLhryb5RUBfZ0HN8w=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=M4o+DNnB4jEHF1D3ZcZT6VQBI4ec80h/SWcqiyD7BVWlX29Xky/m61odulTtrKWvSAc6lEz5IdJGNyDIC0awi5Ij+Ysib4Qp0fqDyCzsXj4pCtyi+Igf+gmjlufaY7a12zdmh8kQeRbhoB7igVTWlS8lcCAiERKqxCkaUbfMpkI=;
Message-ID: <602694.83221.qm@web111409.mail.gq1.yahoo.com>
X-YMail-OSG: UTIk8aIVM1nJobe.Lrv2MWIh0hx91BgxcH35YjSaiYwppfX gQqet3o6lzR0wbtIav3403rGuIhCaSn3iDj7AOBViUIhqtZpiXnXek6md_Mm hAIcLPINNRbpetyTHzA.UzFzMFmwf2DIg7Hcfmfjsmraav2RMfr_WG6suNVC u0MIMl3Um5rA0TrFMbcMnfyvuxNksAAv5ZapbQ4BmfTahM2KkLZzHMOPh8FV b23JUdrqa6qi8qTTgK7O.VVTR1Qt0QAPnpGC2KBKsDrocnG9_MN6qovzebe2 k2xOecxGUvLS3UWUoI2xHT4kIovsc_XkfLt0PDEBVhQUd0AIbkudv2ob1qFN GhtzJbXGzKWjf5SN8cfl54hFp
Received: from [206.16.17.212] by web111409.mail.gq1.yahoo.com via HTTP; Thu, 14 Oct 2010 07:37:19 PDT
X-Mailer: YahooMailRC/504.5 YahooMailWebService/0.8.106.282862
Date: Thu, 14 Oct 2010 07:37:19 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: IPv6 Operations <v6ops@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [v6ops] draft-sarikaya-v6ops-prefix-delegation revised
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 14:36:06 -0000

Hi all,
  We submitted draft-sarikaya-v6ops-prefix-delegation-02.txt it is at:
http://tools.ietf.org/html/draft-sarikaya-v6ops-prefix-delegation-02

based on the comments received. We believe that we resolved all the comments. If 
not, please speak up.

Regards,

Behcet



      

From fred@cisco.com  Thu Oct 14 08:33:51 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 51D1C3A6997; Thu, 14 Oct 2010 08:33:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.315
X-Spam-Level: 
X-Spam-Status: No, score=-110.315 tagged_above=-999 required=5 tests=[AWL=0.284, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xlEq4QPfQB2N; Thu, 14 Oct 2010 08:33:49 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id DC0173A63D2; Thu, 14 Oct 2010 08:33:49 -0700 (PDT)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAD/AtkyrR7Hu/2dsb2JhbAChKXGjHZx5hUgEhFOFc4MD
X-IronPort-AV: E=Sophos;i="4.57,330,1283731200"; d="scan'208";a="603976329"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-6.cisco.com with ESMTP; 14 Oct 2010 15:35:09 +0000
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o9EFZ0mm001772; Thu, 14 Oct 2010 15:35:02 GMT
Received: from [127.0.0.1] by stealth-10-32-244-219.cisco.com (PGP Universal service); Thu, 14 Oct 2010 08:35:09 -0700
X-PGP-Universal: processed; by stealth-10-32-244-219.cisco.com on Thu, 14 Oct 2010 08:35:09 -0700
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <20101014205109.75a23d68@opy.nosense.org>
Date: Thu, 14 Oct 2010 08:34:53 -0700
Message-Id: <884ABB3B-77D5-4660-8914-92BEE228998F@cisco.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com> <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com> <20101014205109.75a23d68@opy.nosense.org>
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>, IESG IESG <iesg@ietf.org>
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 15:33:51 -0000

If the comment is not in this draft, then the work being done in the =
Broadband Forum on this topic should be replicated at Cable Labs for =
that class of networks. Question to their respective representatives: =
are you sufficiently on the same page that you can suggest a statement =
to go here, or would you prefer separate approaches from the Fora?

Mark: How would you suggest wording the "passing comment" regarding =
updates? It sounds like you would prefer something along the lines of:

REC-13:
Residential Internet Gateways SHOULD provide a means for their owners to =
securely update their firmware, for the installation of security patches =
and other manufacturer-recommended changes. Owners are responsible to =
install the firmware, and encouraged to do so promptly, but the means of =
informing them of the availability of the update is beyond the scope of =
this document.

</chair>
I can see both sides of this. I configure my laptop (OS and =
applications) to automatically download patches and notify me of their =
availability, and I decide to install them. I like that on two counts: =
*I* maintain my patches, and I *maintain* my patches. The model makes =
sense with other software and firmware relevant to me as a consumer. On =
the other hand, patches get applied to my wife's and my daughter's =
laptops when I notice that they need to be applied (in my daughter's =
case, that means that I'm visiting her) and make it happen. If I were =
the manufacturer of the residential gateway in question, the only way I =
see to maintain the software would be to maintain an email list as =
people register their products and send them an email, as people can't =
be depended on to log into a manufacturer or ISP site periodically to =
get the news, and the residential gateway doesn't generally have a =
screen that the owner periodically looks at to announce the need for an =
update. We all know how emails tend to get lost in the noise...
<chair>

All: opinions?

On Oct 14, 2010, at 3:21 AM, Mark Smith wrote:

> Hi Fred,
>=20
> I'm really quite concerned about this new text,
>=20
> REC-13: By DEFAULT, Internet gateways SHOULD, automatically download
>   and install software updates for extending IPv6 simple security for
>   support of future standard upper layer transports and extension
>   headers.
>=20
> in particular the automatic install, as I don't think the
> consequences of automatically updating the firmware "behind the
> customers back" have been fully considered.=20
>=20
> If there are any failures with this mechanism at all, the customer
> will most likely be calling the ISP, not the product vendor, despite =
the
> vendor being in control of and responsible for when this new firmware =
is
> deployed. It will appear to the customer that the ISP's service has
> failed. As an update is likely to be pushed out to many CPE at once,
> that could result in floods of 100s, 1000s etc. of unexpected calls to
> the ISP's helpdesk moments after the update occurs. It could also mean
> that updates occur in the middle of when the ISP's services are most
> used due to differing time zones between when the vendor pushes new
> firmware out verses and when customers are most commonly using the
> Internet services.  In this scenario the ISP should be in control of
> when these updates are made available.
>=20
> Following the model used by vendors of desktop OSes these days, it
> would be better if when updates were pushed out, the customer was
> alerted to an update being available, and the customer had to somehow
> manually trigger the update, to avoid disrupting services.=20
>=20
> I think it'd probably be better to make only a passing comment about
> keeping the firmware up to date, avoiding it being a specific SHOULD
> recommendation, without details, in this document. The Broadband =
Forum,
> with mechanisms such as TR-69, seem to be more thoroughly considering
> these issues.
>=20
> Regards,
> Mark.
>=20
>=20
>=20
> On Tue, 12 Oct 2010 11:36:09 -0700
> Fred Baker <fred@cisco.com> wrote:
>=20
>> This is a quick consensus check. The CPE Simple Security document is =
about to complete IESG review, and has gone through four revisions in =
the process of IETF Last Call and IESG review. I'd like to the working =
group to quickly ratify (or not) the changes that have been made and the =
current text.
>>=20
>>    =
ftp://ftpeng.cisco.com/fred/v6ops/draft-ietf-v6ops-cpe-simple-security-11-=
15.html
>>    =
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-cpe-simple-security-1=
5.txt
>>    =
http://datatracker.ietf.org/doc/draft-ietf-v6ops-cpe-simple-security
>>=20
>> If you have any comments, please make them by the weekend. Silence =
will be presumed to be consent.
>>=20
>> Begin forwarded message:
>>=20
>>> From: Internet-Drafts@ietf.org
>>> Date: October 12, 2010 11:00:01 AM PDT
>>> To: i-d-announce@ietf.org
>>> Cc: v6ops@ietf.org
>>> Subject: [v6ops] I-D =
Action:draft-ietf-v6ops-cpe-simple-security-15.txt
>>>=20
>>> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
>>> This draft is a work item of the IPv6 Operations Working Group of =
the IETF.
>>>=20
>>>=20
>>> 	Title           : Recommended Simple Security Capabilities in =
Customer Premises Equipment for Providing Residential IPv6 Internet =
Service
>>> 	Author(s)       : J. Woodyatt
>>> 	Filename        : draft-ietf-v6ops-cpe-simple-security-15.txt
>>> 	Pages           : 35
>>> 	Date            : 2010-10-12
>>>=20
>>> This document identifies a set of recommendations for the makers of
>>> devices describing how to provide for "simple security" capabilities
>>> at the perimeter of local-area IPv6 networks in Internet-enabled
>>> homes and small offices.
>>>=20
>>> A URL for this Internet-Draft is:
>>> =
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-cpe-simple-security-1=
5.txt
>>>=20
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>=20
>>> Below is the data which will enable a MIME compliant mail reader
>>> implementation to automatically retrieve the ASCII version of the
>>> Internet-Draft.


From jhw@apple.com  Thu Oct 14 12:44:47 2010
Return-Path: <jhw@apple.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 09A053A6916; Thu, 14 Oct 2010 12:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.056
X-Spam-Level: 
X-Spam-Status: No, score=-106.056 tagged_above=-999 required=5 tests=[AWL=-0.057, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bNnI83EXG3DD; Thu, 14 Oct 2010 12:44:46 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id 020633A63D2; Thu, 14 Oct 2010 12:44:45 -0700 (PDT)
Received: from relay11.apple.com (relay11.apple.com [17.128.113.48]) by mail-out4.apple.com (Postfix) with ESMTP id 82AC5B5E3FCD; Thu, 14 Oct 2010 12:46:05 -0700 (PDT)
X-AuditID: 11807130-b7b53ae0000049b6-17-4cb75dfd6c48
Received: from [17.151.78.233] (Unknown_Domain [17.151.78.233]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay11.apple.com (Apple SCV relay) with SMTP id BC.B8.18870.DFD57BC4; Thu, 14 Oct 2010 12:46:05 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: james woodyatt <jhw@apple.com>
In-Reply-To: <20101014205109.75a23d68@opy.nosense.org>
Date: Thu, 14 Oct 2010 12:46:04 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com> <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com> <20101014205109.75a23d68@opy.nosense.org>
To: IPv6 Operations <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Cc: iesg@ietf.org
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 19:44:47 -0000

On Oct 14, 2010, at 03:21 , Mark Smith wrote:
>=20
> I'm really quite concerned about this new text,
>=20
> REC-13: By DEFAULT, Internet gateways SHOULD, automatically download
>  and install software updates for extending IPv6 simple security for
>  support of future standard upper layer transports and extension
>  headers.
>=20
> in particular the automatic install, as I don't think the
> consequences of automatically updating the firmware "behind the
> customers back" have been fully considered.=20

This new text is the result of IESG ballot discussion on the -14 =
revision, submitted by Jari Arkko on 2010-10-07.  Here is the text I =
just pulled out of the I-D datatracker.

>> Also, the only mention of new protocols and unrecognized protocols =
and what to
>> do with them is here:
>>=20
>>  Conversely, simple Internet gateways are not expected to prohibit =
the
>>  development of new applications.  In particular, packets with =
end-to-
>>  end network security and routing extension headers for mobility are
>>  expected to pass Internet gateways freely.
>>=20
>> In other words, if you package your traffic in IPsec (or Mobile IPv6) =
it will
>> work, otherwise not. I think the document should be more explicit =
about this
>> limitation, and that new extension headers, new transport protocols, =
etc. would
>> not work through the simple gateway. I would suggest that the =
document say
>> something about recommending automatic software updates for any =
device that
>> supports this type of a functionality so that newly allocated =
protocol numbers
>> could become supported in an easy manner.

After reviewing the current revision, Mr. Arkko cleared his objection =
and sent another comment about this topic to the v6ops chairs, the IESG =
and me.

>> The justification before REQ-13 seems a bit out of balance. It is =
only arguing about new attacks, not the development of new protocols. In =
my mind that is an equally good reason to have software updates. Then =
the requirement itself only argues about new protocols, and does not =
refer to the new attacks at all. I would edit this slightly differently, =
just have the requirement stand on its own, and the preceding paragraph =
about the motivation should include both aspects.

It seems like Mr. Smith and Mr. Arkko are in disagreement about whether =
software updates should be downloaded and applied automatically, and I =
don't know how to proceed from here.

I'm not sure Mr. Arkko's original comment about "new extension header, =
new transport protocols, etc. would not work through [IPv6 simple =
security]" is strictly correct.  We can expect that new transport =
protocols will be tracked with generic state records comprising source =
address and next header value.  Assuming I-D.ietf-6man-exthdr proceeds =
to standard, we can also expect the same for all new standard extension =
headers.

I have no opinion one way or another.  My principle interest is to be =
finished with editing this draft sooner rather than later.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering


From fred@cisco.com  Thu Oct 14 13:08:33 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC8193A6A67; Thu, 14 Oct 2010 13:08:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.333
X-Spam-Level: 
X-Spam-Status: No, score=-110.333 tagged_above=-999 required=5 tests=[AWL=0.266, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ruwnrFSw68dl; Thu, 14 Oct 2010 13:08:32 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id D07E63A6956; Thu, 14 Oct 2010 13:08:32 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEADwAt0yrR7H+/2dsb2JhbAChLXGlIZx/hUgEhFOFc4MD
X-IronPort-AV: E=Sophos;i="4.57,332,1283731200"; d="scan'208";a="200995491"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-4.cisco.com with ESMTP; 14 Oct 2010 20:09:52 +0000
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o9EK9iLi027735; Thu, 14 Oct 2010 20:09:47 GMT
Received: from [127.0.0.1] by stealth-10-32-244-219.cisco.com (PGP Universal service); Thu, 14 Oct 2010 13:09:52 -0700
X-PGP-Universal: processed; by stealth-10-32-244-219.cisco.com on Thu, 14 Oct 2010 13:09:52 -0700
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com>
Date: Thu, 14 Oct 2010 13:09:37 -0700
Message-Id: <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com> <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com> <20101014205109.75a23d68@opy.nosense.org> <DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>, iesg@ietf.org
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 20:08:33 -0000

On Oct 14, 2010, at 12:46 PM, james woodyatt wrote:

> It seems like Mr. Smith and Mr. Arkko are in disagreement about =
whether software updates should be downloaded and applied automatically, =
and I don't know how to proceed from here.

Jari, being on the IESG, is copied in this. I would suggest that he, =
Mark, and Barbara argue their relative cases. At the end of the day, the =
reason that I asked for a final discussion is that there have been =
several changes, and the document has to satisfy not only it's last =
reviewer, but the operational community that is recommending it.

the status as I see it is:

 - Jari wants the patches applied automatically, which assures patch =
updates but removes a level of control from the owner/operator of the =
device

 - Mark wants the patches pushed out but applied with the =
owner/operator's consent

 - Barbara wants the owner/operator to have an interface that can apply =
a patch, but leave anything else undefined; this basically preserves the =
status quo, which means that residential gateways are likely to =
generally *not* track patches and as a result have security =
vulnerabilities, which is also the status quo.

A middle ground, perhaps, would be to recommend that the manufacturer =
provide an option that the user can select; the present language's "by =
default" suggests this as well. The options would be for the device to =
periodically access a manufacturer web site and download updated =
firmware or for the manufacturer to somehow (blast email?) advise the =
registered owner to do so at their convenience. The issue for this draft =
would be "what is the default", as that will be the most common actual =
behavior.=

From brian.e.carpenter@gmail.com  Thu Oct 14 13:21:17 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CDADF3A6A0A; Thu, 14 Oct 2010 13:21:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.289
X-Spam-Level: 
X-Spam-Status: No, score=-102.289 tagged_above=-999 required=5 tests=[AWL=-0.290, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VMoRAVPzywaR; Thu, 14 Oct 2010 13:21:17 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id 805E73A6956; Thu, 14 Oct 2010 13:21:16 -0700 (PDT)
Received: by wwj40 with SMTP id 40so51444wwj.13 for <multiple recipients>; Thu, 14 Oct 2010 13:22:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=3C8rJlT8Op3EHk5s4pL5XiLXHY/7z/DQi8HmQatclmI=; b=kT+7jGBSyrpd1mmd37LXItC6YKPeSxSMN/y2+L8yfFEVVXxjMF5WTwl+MhSHWfuSuV DxZVtfByCbjeIACaf6njYZIPimZ2+EJvcL9iYnA1IHMcPvELBwUs7xKH3Juu4/CEhjtb g8OVfwpEUvLDY9xLBe+zTClq+IDXX2IPMYctk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=nkrEinWMe3d5rSnWDG1Lfmmf5D4ljzXysozM0FJtc6FxZFcD3YJY45jj/p1wgs3DCw YP35oyFd5637raE+EA7VSc4bYrPZuP4dZLNTXiRYPEf2ItTEg7ekd/fwl2x3NIQsHW/L 3hoAEKs0kH3lfAa/C9lp3dPRQ5cHimmeGWUcU=
Received: by 10.216.28.77 with SMTP id f55mr503610wea.91.1287087755346; Thu, 14 Oct 2010 13:22:35 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id x62sm7403993weq.15.2010.10.14.13.22.31 (version=SSLv3 cipher=RC4-MD5); Thu, 14 Oct 2010 13:22:34 -0700 (PDT)
Message-ID: <4CB76693.8@gmail.com>
Date: Fri, 15 Oct 2010 09:22:43 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com>	<ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com>	<20101014205109.75a23d68@opy.nosense.org>	<DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com> <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com>
In-Reply-To: <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, iesg@ietf.org
Subject: Re: [v6ops] Fwd: I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 20:21:17 -0000

On 2010-10-15 09:09, Fred Baker wrote:
> On Oct 14, 2010, at 12:46 PM, james woodyatt wrote:
> 
>> It seems like Mr. Smith and Mr. Arkko are in disagreement about whether software updates should be downloaded and applied automatically, and I don't know how to proceed from here.
> 
> Jari, being on the IESG, is copied in this. I would suggest that he, Mark, and Barbara argue their relative cases. At the end of the day, the reason that I asked for a final discussion is that there have been several changes, and the document has to satisfy not only it's last reviewer, but the operational community that is recommending it.
> 
> the status as I see it is:
> 
>  - Jari wants the patches applied automatically, which assures patch updates but removes a level of control from the owner/operator of the device

Speaking as a user, I deeply hate systems that install patches by default
without asking me. I don't think the IETF should be taking a position on
that one way or the other. On the other, leaving patching up to the user's
initiative has been thoroughly proved to fail. So I think Mark's
position is best, but I'd still prefer us to be neutral: recommend that
the implementor/vendor provides a patch mechanism, but not saying anything
about automatic vs consent vs voluntary.

    Brian

>  - Mark wants the patches pushed out but applied with the owner/operator's consent
> 
>  - Barbara wants the owner/operator to have an interface that can apply a patch, but leave anything else undefined; this basically preserves the status quo, which means that residential gateways are likely to generally *not* track patches and as a result have security vulnerabilities, which is also the status quo.
> 
> A middle ground, perhaps, would be to recommend that the manufacturer provide an option that the user can select; the present language's "by default" suggests this as well. The options would be for the device to periodically access a manufacturer web site and download updated firmware or for the manufacturer to somehow (blast email?) advise the registered owner to do so at their convenience. The issue for this draft would be "what is the default", as that will be the most common actual behavior.
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> 

From fred@cisco.com  Thu Oct 14 13:28:24 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8373A3A6956; Thu, 14 Oct 2010 13:28:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.042
X-Spam-Level: 
X-Spam-Status: No, score=-110.042 tagged_above=-999 required=5 tests=[AWL=-0.043, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r0BPTSoUk7YF; Thu, 14 Oct 2010 13:28:23 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id B93FE3A6A01; Thu, 14 Oct 2010 13:28:22 -0700 (PDT)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAH0Et0yrR7Ht/2dsb2JhbAChInGlOZ0BhUgEhFOFc4MD
X-IronPort-AV: E=Sophos;i="4.57,332,1283731200"; d="scan'208";a="269719609"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-5.cisco.com with ESMTP; 14 Oct 2010 20:29:42 +0000
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o9EKTYn6021406; Thu, 14 Oct 2010 20:29:37 GMT
Received: from [127.0.0.1] by stealth-10-32-244-219.cisco.com (PGP Universal service); Thu, 14 Oct 2010 13:29:42 -0700
X-PGP-Universal: processed; by stealth-10-32-244-219.cisco.com on Thu, 14 Oct 2010 13:29:42 -0700
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4CB76693.8@gmail.com>
Date: Thu, 14 Oct 2010 13:29:28 -0700
Message-Id: <2AC2EA34-9607-436E-A5C8-DDA745F0997D@cisco.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com>	<ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com>	<20101014205109.75a23d68@opy.nosense.org>	<DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com> <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com> <4CB76693.8@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>, iesg@ietf.org
Subject: Re: [v6ops] Fwd: I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 20:28:24 -0000

On Oct 14, 2010, at 1:22 PM, Brian E Carpenter wrote:

> On 2010-10-15 09:09, Fred Baker wrote:
>> On Oct 14, 2010, at 12:46 PM, james woodyatt wrote:
>>=20
>>> It seems like Mr. Smith and Mr. Arkko are in disagreement about =
whether software updates should be downloaded and applied automatically, =
and I don't know how to proceed from here.
>>=20
>> Jari, being on the IESG, is copied in this. I would suggest that he, =
Mark, and Barbara argue their relative cases. At the end of the day, the =
reason that I asked for a final discussion is that there have been =
several changes, and the document has to satisfy not only it's last =
reviewer, but the operational community that is recommending it.
>>=20
>> the status as I see it is:
>>=20
>> - Jari wants the patches applied automatically, which assures patch =
updates but removes a level of control from the owner/operator of the =
device
>=20
> Speaking as a user, I deeply hate systems that install patches by =
default
> without asking me. I don't think the IETF should be taking a position =
on
> that one way or the other. On the other, leaving patching up to the =
user's
> initiative has been thoroughly proved to fail. So I think Mark's
> position is best, but I'd still prefer us to be neutral: recommend =
that
> the implementor/vendor provides a patch mechanism, but not saying =
anything
> about automatic vs consent vs voluntary.

So you in essence support Barbara's proposed language.

>    Brian
>=20
>> - Mark wants the patches pushed out but applied with the =
owner/operator's consent
>>=20
>> - Barbara wants the owner/operator to have an interface that can =
apply a patch, but leave anything else undefined; this basically =
preserves the status quo, which means that residential gateways are =
likely to generally *not* track patches and as a result have security =
vulnerabilities, which is also the status quo.
>>=20
>> A middle ground, perhaps, would be to recommend that the manufacturer =
provide an option that the user can select; the present language's "by =
default" suggests this as well. The options would be for the device to =
periodically access a manufacturer web site and download updated =
firmware or for the manufacturer to somehow (blast email?) advise the =
registered owner to do so at their convenience. The issue for this draft =
would be "what is the default", as that will be the most common actual =
behavior.
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>>=20


From jhw@apple.com  Thu Oct 14 13:29:41 2010
Return-Path: <jhw@apple.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C0A523A6BAD; Thu, 14 Oct 2010 13:29:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.352
X-Spam-Level: 
X-Spam-Status: No, score=-106.352 tagged_above=-999 required=5 tests=[AWL=0.247, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gTLWz7S9sSSB; Thu, 14 Oct 2010 13:29:35 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 445173A6BB3; Thu, 14 Oct 2010 13:29:31 -0700 (PDT)
Received: from relay13.apple.com (relay13.apple.com [17.128.113.29]) by mail-out3.apple.com (Postfix) with ESMTP id D1DA1AF623E3; Thu, 14 Oct 2010 13:30:50 -0700 (PDT)
X-AuditID: 1180711d-b7c86ae000000247-ae-4cb7687a68e2
Received: from [17.151.78.233] (Unknown_Domain [17.151.78.233]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay13.apple.com (Apple SCV relay) with SMTP id 58.87.00583.A7867BC4; Thu, 14 Oct 2010 13:30:50 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: james woodyatt <jhw@apple.com>
In-Reply-To: <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com>
Date: Thu, 14 Oct 2010 13:30:50 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3277F900-7DE4-4FFB-B469-D7360ACD04AD@apple.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com> <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com> <20101014205109.75a23d68@opy.nosense.org> <DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com> <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com>
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Cc: IPv6 Operations <v6ops@ietf.org>, iesg@ietf.org
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 20:29:42 -0000

On Oct 14, 2010, at 13:09 , Fred Baker wrote:
>=20
> The issue for this draft would be "what is the default", as that will =
be the most common actual behavior.

As long as software updates require user interaction to apply, we will =
continue to have the status quo ante, i.e. most gateways will never be =
updated from their factory software load.  I don't see much practical =
benefit in making recommendations about staging of firmware updates =
prior to sending an attention signal to a human.

I suggest tweaking the recommendation to say that an "easily configured =
administrative option" to download and apply updates automatically =
SHOULD be offered.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



From ipng@69706e6720323030352d30312d31340a.nosense.org  Thu Oct 14 13:54:47 2010
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF6153A6B17; Thu, 14 Oct 2010 13:54:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.672
X-Spam-Level: 
X-Spam-Status: No, score=-1.672 tagged_above=-999 required=5 tests=[AWL=0.223,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hJU-aEUSNZ8e; Thu, 14 Oct 2010 13:54:45 -0700 (PDT)
Received: from smtp1.adam.net.au (smtp1.adam.net.au [202.136.110.253]) by core3.amsl.com (Postfix) with ESMTP id 6B02C3A6AC4; Thu, 14 Oct 2010 13:54:43 -0700 (PDT)
Received: from 219-90-190-11.ip.adam.com.au ([219.90.190.11] helo=opy.nosense.org) by smtp1.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1P6UqB-0001aN-ND; Fri, 15 Oct 2010 07:25:55 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id C8B273B31E; Fri, 15 Oct 2010 07:25:54 +1030 (CST)
Date: Fri, 15 Oct 2010 07:25:49 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Fred Baker <fred@cisco.com>
Message-ID: <20101015072549.4b1061b3@opy.nosense.org>
In-Reply-To: <884ABB3B-77D5-4660-8914-92BEE228998F@cisco.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com> <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com> <20101014205109.75a23d68@opy.nosense.org> <884ABB3B-77D5-4660-8914-92BEE228998F@cisco.com>
X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, IESG IESG <iesg@ietf.org>
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 20:54:47 -0000

Hi Fred,

On Thu, 14 Oct 2010 08:34:53 -0700
Fred Baker <fred@cisco.com> wrote:

> If the comment is not in this draft, then the work being done in the Broadband Forum on this topic should be replicated at Cable Labs for that class of networks. Question to their respective representatives: are you sufficiently on the same page that you can suggest a statement to go here, or would you prefer separate approaches from the Fora?
> 
> Mark: How would you suggest wording the "passing comment" regarding updates? It sounds like you would prefer something along the lines of:
> 
> REC-13:
> Residential Internet Gateways SHOULD provide a means for their owners to securely update their firmware, for the installation of security patches and other manufacturer-recommended changes. Owners are responsible to install the firmware, and encouraged to do so promptly, but the means of informing them of the availability of the update is beyond the scope of this document.
> 

Yes, I'd be happier with that. 

> </chair>
> I can see both sides of this. I configure my laptop (OS and applications) to automatically download patches and notify me of their availability, and I decide to install them. I like that on two counts: *I* maintain my patches, and I *maintain* my patches. The model makes sense with other software and firmware relevant to me as a consumer. On the other hand, patches get applied to my wife's and my daughter's laptops when I notice that they need to be applied (in my daughter's case, that means that I'm visiting her) and make it happen. If I were the manufacturer of the residential gateway in question, the only way I see to maintain the software would be to maintain an email list as people register their products and send them an email, as people can't be depended on to log into a manufacturer or ISP site periodically to get the news, and the residential gateway doesn't generally have a screen that the owner periodically looks at to announce the need for an update. We all know
  how emails tend to get lost in the noise...
> <chair>
> 

My issue isn't so much the automated downloading, it's the automated
installation. CPE typically needs to be rebooted to perform that task,
so automated installation means an unexpected service outage. So in the
middle of making a VoIP phone call to the boss (or to emergency
services!), accessing the corporate VPN, watching a streaming video
etc., there'd all of a sudden be an unexplained outage of typically a
few minutes, as well as typically would would be alarming flashing of
lights on the device. Very un-user friendly behaviour, and worse
because the ISP is likely to be the first to be blamed for it, and have
wear the consequences of dealing with unhappy customers. Unfortunately
I've recently had to deal with a situation where vendor faults on large
numbers of CPE devices were seen to be my (ISP) employer's
responsibility and it was very unpleasant to say the least.

As for mechanism for applying an update (which I do agree is out of
scope), one thought I had would be possibly an "Firmware Upgrade
Available" flashing LED on the CPE, and a specific button to be held
down for say 5 seconds to load it would be a fairly simple way to both
notify the end-user and allow them to control when it is applied.

Thanks,
Mark.



> All: opinions?
> 
> On Oct 14, 2010, at 3:21 AM, Mark Smith wrote:
> 
> > Hi Fred,
> > 
> > I'm really quite concerned about this new text,
> > 
> > REC-13: By DEFAULT, Internet gateways SHOULD, automatically download
> >   and install software updates for extending IPv6 simple security for
> >   support of future standard upper layer transports and extension
> >   headers.
> > 
> > in particular the automatic install, as I don't think the
> > consequences of automatically updating the firmware "behind the
> > customers back" have been fully considered. 
> > 
> > If there are any failures with this mechanism at all, the customer
> > will most likely be calling the ISP, not the product vendor, despite the
> > vendor being in control of and responsible for when this new firmware is
> > deployed. It will appear to the customer that the ISP's service has
> > failed. As an update is likely to be pushed out to many CPE at once,
> > that could result in floods of 100s, 1000s etc. of unexpected calls to
> > the ISP's helpdesk moments after the update occurs. It could also mean
> > that updates occur in the middle of when the ISP's services are most
> > used due to differing time zones between when the vendor pushes new
> > firmware out verses and when customers are most commonly using the
> > Internet services.  In this scenario the ISP should be in control of
> > when these updates are made available.
> > 
> > Following the model used by vendors of desktop OSes these days, it
> > would be better if when updates were pushed out, the customer was
> > alerted to an update being available, and the customer had to somehow
> > manually trigger the update, to avoid disrupting services. 
> > 
> > I think it'd probably be better to make only a passing comment about
> > keeping the firmware up to date, avoiding it being a specific SHOULD
> > recommendation, without details, in this document. The Broadband Forum,
> > with mechanisms such as TR-69, seem to be more thoroughly considering
> > these issues.
> > 
> > Regards,
> > Mark.
> > 
> > 
> > 
> > On Tue, 12 Oct 2010 11:36:09 -0700
> > Fred Baker <fred@cisco.com> wrote:
> > 
> >> This is a quick consensus check. The CPE Simple Security document is about to complete IESG review, and has gone through four revisions in the process of IETF Last Call and IESG review. I'd like to the working group to quickly ratify (or not) the changes that have been made and the current text.
> >> 
> >>    ftp://ftpeng.cisco.com/fred/v6ops/draft-ietf-v6ops-cpe-simple-security-11-15.html
> >>    http://www.ietf.org/internet-drafts/draft-ietf-v6ops-cpe-simple-security-15.txt
> >>    http://datatracker.ietf.org/doc/draft-ietf-v6ops-cpe-simple-security
> >> 
> >> If you have any comments, please make them by the weekend. Silence will be presumed to be consent.
> >> 
> >> Begin forwarded message:
> >> 
> >>> From: Internet-Drafts@ietf.org
> >>> Date: October 12, 2010 11:00:01 AM PDT
> >>> To: i-d-announce@ietf.org
> >>> Cc: v6ops@ietf.org
> >>> Subject: [v6ops] I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
> >>> 
> >>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> >>> This draft is a work item of the IPv6 Operations Working Group of the IETF.
> >>> 
> >>> 
> >>> 	Title           : Recommended Simple Security Capabilities in Customer Premises Equipment for Providing Residential IPv6 Internet Service
> >>> 	Author(s)       : J. Woodyatt
> >>> 	Filename        : draft-ietf-v6ops-cpe-simple-security-15.txt
> >>> 	Pages           : 35
> >>> 	Date            : 2010-10-12
> >>> 
> >>> This document identifies a set of recommendations for the makers of
> >>> devices describing how to provide for "simple security" capabilities
> >>> at the perimeter of local-area IPv6 networks in Internet-enabled
> >>> homes and small offices.
> >>> 
> >>> A URL for this Internet-Draft is:
> >>> http://www.ietf.org/internet-drafts/draft-ietf-v6ops-cpe-simple-security-15.txt
> >>> 
> >>> Internet-Drafts are also available by anonymous FTP at:
> >>> ftp://ftp.ietf.org/internet-drafts/
> >>> 
> >>> Below is the data which will enable a MIME compliant mail reader
> >>> implementation to automatically retrieve the ASCII version of the
> >>> Internet-Draft.
> 

From bs7652@att.com  Thu Oct 14 14:01:38 2010
Return-Path: <bs7652@att.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9FAC23A6B8E; Thu, 14 Oct 2010 14:01:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.169
X-Spam-Level: 
X-Spam-Status: No, score=-106.169 tagged_above=-999 required=5 tests=[AWL=-0.170, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8V9OUKg+DGq5; Thu, 14 Oct 2010 14:01:37 -0700 (PDT)
Received: from mail121.messagelabs.com (mail121.messagelabs.com [216.82.242.3]) by core3.amsl.com (Postfix) with ESMTP id 87F4B3A6AC2; Thu, 14 Oct 2010 14:01:36 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: bs7652@att.com
X-Msg-Ref: server-7.tower-121.messagelabs.com!1287090174!34044357!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 15177 invoked from network); 14 Oct 2010 21:02:55 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-7.tower-121.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Oct 2010 21:02:55 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o9EL2IKY026251; Thu, 14 Oct 2010 17:02:18 -0400
Received: from 01GAF5142010625.AD.BLS.COM (01GAF5142010625.ad.bls.com [139.76.131.31]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with SMTP id o9EL2Gjl026237; Thu, 14 Oct 2010 17:02:16 -0400
Received: from 01NC27689010627.AD.BLS.COM ([90.144.44.202]) by 01GAF5142010625.AD.BLS.COM with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 14 Oct 2010 17:02:52 -0400
Received: from 01NC27689010650.AD.BLS.COM ([90.144.44.120]) by 01NC27689010627.AD.BLS.COM with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 14 Oct 2010 17:02:52 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 14 Oct 2010 17:02:48 -0400
Message-ID: <750BF7861EBBE048B3E648B4BB6E8F4F16EF49F0@crexc50p>
In-Reply-To: <884ABB3B-77D5-4660-8914-92BEE228998F@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops] Fwd: I-DAction:draft-ietf-v6ops-cpe-simple-security-15.txt
Thread-Index: ActrtWs2mcZrqBKVSimuduFnzIET7QALaqRg
References: <20101012180001.D0C3C3A69CE@core3.amsl.com><ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com><20101014205109.75a23d68@opy.nosense.org> <884ABB3B-77D5-4660-8914-92BEE228998F@cisco.com>
From: "STARK, BARBARA H (ATTLABS)" <bs7652@att.com>
To: "Fred Baker" <fred@cisco.com>, "Mark Smith" <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-OriginalArrivalTime: 14 Oct 2010 21:02:52.0054 (UTC) FILETIME=[2A3C6360:01CB6BE3]
Cc: IPv6 Operations <v6ops@ietf.org>, IESG IESG <iesg@ietf.org>
Subject: Re: [v6ops] Fwd: I-DAction:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 21:01:38 -0000

BBF has defined a model for doing firmware upgrades via TR-069. But
support for this mechanism is not mandated, and not all SPs choose to
use it (though some do). Other methods I've seen are (1) the device has
an "update" web page that can be manually invoked by the user, (2)
during initial device configuration the user is prompted to set up a
periodic time for the device to go out and look for updates (e.g., the
4th of every month at 2:41am local time), (3) similar to (1) but in
addition to that the device periodically checks for updates and makes it
known on the main device web page that an update is available and the
user needs to manually invoke it, etc. These methods are also usable by
retail CE routers, and none of them have the effect of causing too many
routers to upgrade at the same time.

I wouldn't recommend that CE routers use a mechanism that causes en
masse upgrades. But since I've never seen a CE router manufacturer do
something like that (and most don't have the capability, since CE
routers are almost never manageable through a "push" management model),
I don't really think we need language in the simple-security draft
recommending against that.

I think that if you take the first sentence of the text Fred suggested,
that should be sufficient:

REC-13:
Residential Internet Gateways SHOULD provide a means for their owners to
securely update their firmware, for the installation of security patches
and other manufacturer-recommended changes.

Barbara

> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
> Of Fred Baker
>
> If the comment is not in this draft, then the work being done in the
> Broadband Forum on this topic should be replicated at Cable Labs for
> that class of networks. Question to their respective representatives:
> are you sufficiently on the same page that you can suggest a statement
> to go here, or would you prefer separate approaches from the Fora?
>=20
> Mark: How would you suggest wording the "passing comment" regarding
> updates? It sounds like you would prefer something along the lines of:
>=20
> REC-13:
> Residential Internet Gateways SHOULD provide a means for their owners
> to securely update their firmware, for the installation of security
> patches and other manufacturer-recommended changes. Owners are
> responsible to install the firmware, and encouraged to do so promptly,
> but the means of informing them of the availability of the update is
> beyond the scope of this document.
>=20
> </chair>
> I can see both sides of this. I configure my laptop (OS and
> applications) to automatically download patches and notify me of their
> availability, and I decide to install them. I like that on two counts:
> *I* maintain my patches, and I *maintain* my patches. The model makes
> sense with other software and firmware relevant to me as a consumer.
On
> the other hand, patches get applied to my wife's and my daughter's
> laptops when I notice that they need to be applied (in my daughter's
> case, that means that I'm visiting her) and make it happen. If I were
> the manufacturer of the residential gateway in question, the only way
I
> see to maintain the software would be to maintain an email list as
> people register their products and send them an email, as people can't
> be depended on to log into a manufacturer or ISP site periodically to
> get the news, and the residential gateway doesn't generally have a
> screen that the owner periodically looks at to announce the need for
an
> update. We all know h
>  ow emails tend to get lost in the noise...
> <chair>
>=20
> All: opinions?
>=20
> On Oct 14, 2010, at 3:21 AM, Mark Smith wrote:
>=20
> > Hi Fred,
> >
> > I'm really quite concerned about this new text,
> >
> > REC-13: By DEFAULT, Internet gateways SHOULD, automatically download
> >   and install software updates for extending IPv6 simple security
for
> >   support of future standard upper layer transports and extension
> >   headers.
> >
> > in particular the automatic install, as I don't think the
> > consequences of automatically updating the firmware "behind the
> > customers back" have been fully considered.
> >
> > If there are any failures with this mechanism at all, the customer
> > will most likely be calling the ISP, not the product vendor, despite
> the
> > vendor being in control of and responsible for when this new
firmware
> is
> > deployed. It will appear to the customer that the ISP's service has
> > failed. As an update is likely to be pushed out to many CPE at once,
> > that could result in floods of 100s, 1000s etc. of unexpected calls
> to
> > the ISP's helpdesk moments after the update occurs. It could also
> mean
> > that updates occur in the middle of when the ISP's services are most
> > used due to differing time zones between when the vendor pushes new
> > firmware out verses and when customers are most commonly using the
> > Internet services.  In this scenario the ISP should be in control of
> > when these updates are made available.
> >
> > Following the model used by vendors of desktop OSes these days, it
> > would be better if when updates were pushed out, the customer was
> > alerted to an update being available, and the customer had to
somehow
> > manually trigger the update, to avoid disrupting services.
> >
> > I think it'd probably be better to make only a passing comment about
> > keeping the firmware up to date, avoiding it being a specific SHOULD
> > recommendation, without details, in this document. The Broadband
> Forum,
> > with mechanisms such as TR-69, seem to be more thoroughly
considering
> > these issues.
> >
> > Regards,
> > Mark.
> >
> >
> >
> > On Tue, 12 Oct 2010 11:36:09 -0700
> > Fred Baker <fred@cisco.com> wrote:
> >
> >> This is a quick consensus check. The CPE Simple Security document
is
> about to complete IESG review, and has gone through four revisions in
> the process of IETF Last Call and IESG review. I'd like to the working
> group to quickly ratify (or not) the changes that have been made and
> the current text.
> >>
> >>    ftp://ftpeng.cisco.com/fred/v6ops/draft-ietf-v6ops-cpe-simple-
> security-11-15.html
> >>    http://www.ietf.org/internet-drafts/draft-ietf-v6ops-cpe-simple-
> security-15.txt
> >>    http://datatracker.ietf.org/doc/draft-ietf-v6ops-cpe-simple-
> security
> >>
> >> If you have any comments, please make them by the weekend. Silence
> will be presumed to be consent.
> >>
> >> Begin forwarded message:
> >>
> >>> From: Internet-Drafts@ietf.org
> >>> Date: October 12, 2010 11:00:01 AM PDT
> >>> To: i-d-announce@ietf.org
> >>> Cc: v6ops@ietf.org
> >>> Subject: [v6ops] I-D Action:draft-ietf-v6ops-cpe-simple-security-
> 15.txt
> >>>
> >>> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >>> This draft is a work item of the IPv6 Operations Working Group of
> the IETF.
> >>>
> >>>
> >>> 	Title           : Recommended Simple Security Capabilities in
> Customer Premises Equipment for Providing Residential IPv6 Internet
> Service
> >>> 	Author(s)       : J. Woodyatt
> >>> 	Filename        : draft-ietf-v6ops-cpe-simple-security-15.txt
> >>> 	Pages           : 35
> >>> 	Date            : 2010-10-12
> >>>
> >>> This document identifies a set of recommendations for the makers
of
> >>> devices describing how to provide for "simple security"
> capabilities
> >>> at the perimeter of local-area IPv6 networks in Internet-enabled
> >>> homes and small offices.
> >>>
> >>> A URL for this Internet-Draft is:
> >>> http://www.ietf.org/internet-drafts/draft-ietf-v6ops-cpe-simple-
> security-15.txt
> >>>
> >>> Internet-Drafts are also available by anonymous FTP at:
> >>> ftp://ftp.ietf.org/internet-drafts/
> >>>
> >>> Below is the data which will enable a MIME compliant mail reader
> >>> implementation to automatically retrieve the ASCII version of the
> >>> Internet-Draft.
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

From jhw@apple.com  Thu Oct 14 14:02:24 2010
Return-Path: <jhw@apple.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7FA5E3A6AC2 for <v6ops@core3.amsl.com>; Thu, 14 Oct 2010 14:02:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.369
X-Spam-Level: 
X-Spam-Status: No, score=-106.369 tagged_above=-999 required=5 tests=[AWL=0.230, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hnUoukWj8SKX for <v6ops@core3.amsl.com>; Thu, 14 Oct 2010 14:02:23 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id BA0A03A6A3E for <v6ops@ietf.org>; Thu, 14 Oct 2010 14:02:23 -0700 (PDT)
Received: from relay13.apple.com (relay13.apple.com [17.128.113.29]) by mail-out3.apple.com (Postfix) with ESMTP id 863C3AF6476F; Thu, 14 Oct 2010 14:03:43 -0700 (PDT)
X-AuditID: 1180711d-b7c86ae000000247-5f-4cb7702e66ca
Received: from [17.151.110.125] (Unknown_Domain [17.151.110.125]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay13.apple.com (Apple SCV relay) with SMTP id 9D.11.00583.F2077BC4; Thu, 14 Oct 2010 14:03:43 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: james woodyatt <jhw@apple.com>
In-Reply-To: <20101015072549.4b1061b3@opy.nosense.org>
Date: Thu, 14 Oct 2010 14:03:42 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <48E6EFD1-AB41-451A-91A8-291D427102F3@apple.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com> <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com> <20101014205109.75a23d68@opy.nosense.org> <884ABB3B-77D5-4660-8914-92BEE228998F@cisco.com> <20101015072549.4b1061b3@opy.nosense.org>
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 21:02:24 -0000

On Oct 14, 2010, at 13:55 , Mark Smith wrote:
>=20
> ...so automated installation means an unexpected service outage...

Because that, as we all know, never happens.  (I'm about *this* close to =
recommending that IANA set aside 192.168.100.1 as a reserved IPv4 =
address for use only by DOCSIS management interfaces.)

Still, your point seems compelling to me.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



From brian.e.carpenter@gmail.com  Thu Oct 14 14:21:40 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4E5873A6A6E; Thu, 14 Oct 2010 14:21:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.287
X-Spam-Level: 
X-Spam-Status: No, score=-102.287 tagged_above=-999 required=5 tests=[AWL=-0.288, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JTYAHsrkiwpk; Thu, 14 Oct 2010 14:21:39 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id DF1CA3A6A3E; Thu, 14 Oct 2010 14:21:38 -0700 (PDT)
Received: by wwj40 with SMTP id 40so101784wwj.13 for <multiple recipients>; Thu, 14 Oct 2010 14:22:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=aSMWHiU4rRnQn5f0sx0I02u1i9HLMCLNdajOxoGL0K4=; b=IgivA7pcVw+5auCi1xdwkHjoRuTEuoJFSIPbqw7fVfHACh8KJrx8x7hpDZoMuhLDtl ZoPXObKxKriX5GcXG76E04g/mZABp42YYySJKtqwajKQe/NqQeHHimjipHsPi1vouJW2 MVnbrxEjcSqWdzq02hmkb+pRJx/onOrMMU/0Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=J56pSEsz28kpvHPlWxwu/vSKe0MBLVN2FByoXj/GsiBHkIxVY3AkcQjLgUO0UF3yoA gPHzTvaoR7DD3vLD3Hu8mRoAkT1x9MrHpUivITMMtinh1HNmUBWmAOvNek2PTRnxIinB z2zy26LsFY8rSUDXCdFxlEs6zeYHYV9DRC3dQ=
Received: by 10.216.4.19 with SMTP id 19mr10509389wei.110.1287091376150; Thu, 14 Oct 2010 14:22:56 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id x3sm5546710weq.8.2010.10.14.14.22.52 (version=SSLv3 cipher=RC4-MD5); Thu, 14 Oct 2010 14:22:55 -0700 (PDT)
Message-ID: <4CB774A7.3070301@gmail.com>
Date: Fri, 15 Oct 2010 10:22:47 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com>	<ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com>	<20101014205109.75a23d68@opy.nosense.org>	<DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com> <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com> <4CB76693.8@gmail.com> <2AC2EA34-9607-436E-A5C8-DDA745F0997D@cisco.com>
In-Reply-To: <2AC2EA34-9607-436E-A5C8-DDA745F0997D@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, iesg@ietf.org
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 21:21:40 -0000

I think we should keep our noses out of default patching
policies. These may vary a lot according to the context.
I would certainly expect DOCSIS boxes to be upgraded without
involving the user, for example, but the same won't be true
for the proverbial $50 box from the local electronics supermarket.
One size of policy won't fit all. So don't say who does the patching:

REC-13:
Residential Internet Gateways SHOULD provide a convenient means to
securely update their firmware, for the installation of security patches
and other manufacturer-recommended changes.

Regards
   Brian Carpenter


On 2010-10-15 09:29, Fred Baker wrote:
> On Oct 14, 2010, at 1:22 PM, Brian E Carpenter wrote:
> 
>> On 2010-10-15 09:09, Fred Baker wrote:
>>> On Oct 14, 2010, at 12:46 PM, james woodyatt wrote:
>>>
>>>> It seems like Mr. Smith and Mr. Arkko are in disagreement about whether software updates should be downloaded and applied automatically, and I don't know how to proceed from here.
>>> Jari, being on the IESG, is copied in this. I would suggest that he, Mark, and Barbara argue their relative cases. At the end of the day, the reason that I asked for a final discussion is that there have been several changes, and the document has to satisfy not only it's last reviewer, but the operational community that is recommending it.
>>>
>>> the status as I see it is:
>>>
>>> - Jari wants the patches applied automatically, which assures patch updates but removes a level of control from the owner/operator of the device
>> Speaking as a user, I deeply hate systems that install patches by default
>> without asking me. I don't think the IETF should be taking a position on
>> that one way or the other. On the other, leaving patching up to the user's
>> initiative has been thoroughly proved to fail. So I think Mark's
>> position is best, but I'd still prefer us to be neutral: recommend that
>> the implementor/vendor provides a patch mechanism, but not saying anything
>> about automatic vs consent vs voluntary.
> 
> So you in essence support Barbara's proposed language.
> 
>>    Brian
>>
>>> - Mark wants the patches pushed out but applied with the owner/operator's consent
>>>
>>> - Barbara wants the owner/operator to have an interface that can apply a patch, but leave anything else undefined; this basically preserves the status quo, which means that residential gateways are likely to generally *not* track patches and as a result have security vulnerabilities, which is also the status quo.
>>>
>>> A middle ground, perhaps, would be to recommend that the manufacturer provide an option that the user can select; the present language's "by default" suggests this as well. The options would be for the device to periodically access a manufacturer web site and download updated firmware or for the manufacturer to somehow (blast email?) advise the registered owner to do so at their convenience. The issue for this draft would be "what is the default", as that will be the most common actual behavior.
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>
> 
> 

From rja.lists@gmail.com  Thu Oct 14 15:09:47 2010
Return-Path: <rja.lists@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7B4593A6C1A for <v6ops@core3.amsl.com>; Thu, 14 Oct 2010 15:09: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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OzvBi9HQhUCO for <v6ops@core3.amsl.com>; Thu, 14 Oct 2010 15:09:46 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id 5DB913A6C0F for <v6ops@ietf.org>; Thu, 14 Oct 2010 15:09:46 -0700 (PDT)
Received: by yxk30 with SMTP id 30so72756yxk.31 for <v6ops@ietf.org>; Thu, 14 Oct 2010 15:11:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:content-type :content-transfer-encoding:subject:date:message-id:to:mime-version :x-mailer; bh=mTOl2bQWgJ5EAjjP6oBGw7C962kEUv1oMKwJCBgYiQU=; b=Q44z4wIQ2QTyE887mopJEJakqsiudUG7VUd2cEI7hlVNuNJkpJuSxwEAKWLSIVxKb3 1E4Q1HwL3NgWoXa05hgG6S67+QUCat0oo0CbTFyo9sLqQRTmnMChTfIeVrV+/0YxtL8M 2a72pi7QYSewjijSxsGgtYje4W+ZUllm7/OR4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=CEYGKxdsMvJfOaqpzq5rzhGlea5rfJG1M0TpXASOBr+t8qZiYrkNgWzgf8llFqwbhu MVF9ldeWX5fDcFpH7YzN3nNB5vcPH7PoplO2Ti69R+q5XExa5y93jjSxRGIlAicHWhsw 8hOWB+XIZUL3UOkFERwuxydd8E1y/Ls5mdq9g=
Received: by 10.150.208.8 with SMTP id f8mr157835ybg.294.1287094265712; Thu, 14 Oct 2010 15:11:05 -0700 (PDT)
Received: from [172.16.1.28] (h-66-134-38-70.mclnva23.static.covad.net [66.134.38.70]) by mx.google.com with ESMTPS id q23sm392712yba.5.2010.10.14.15.11.04 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 14 Oct 2010 15:11:05 -0700 (PDT)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 14 Oct 2010 18:11:03 -0400
Message-Id: <C7FCC31E-AC1C-456E-B1DA-A6C524B09099@gmail.com>
To: v6ops@ietf.org
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 22:09:47 -0000

Earlier today, James Woodyatt wrote:
> I'm not sure Mr. Arkko's original comment about 
> "new extension header, new transport protocols, etc. 
> would not work through [IPv6 simple security]" is 
> strictly correct.  

I certainly hope it isn't entirely correct.

I can think of 2 relevant examples of new IPv6 options:
	RFC-5570
	draft-rja-ilnp-nonce-06.txt

One would hope packets with either or both of those options
would be handled properly -- i.e. as per RFC-2460, Section 
4.2.  

If someone really thinks that the quoted claim at top is true, 
I'd love to be educated why/how/when it is true ?


> We can expect that new transport protocols will be tracked 
> with generic state records comprising source address and 
> next header value.  Assuming I-D.ietf-6man-exthdr proceeds 
> to standard, we can also expect the same for all new standard 
> extension headers.

It has never been clear to me what extension header might
exist in future that is neither a hop-by-hop option nor
a Destination Option.  Formats for defining new options for
either of those seem quite clearly defined in RFC-2460.

So I've been a bit confused what actual problem I-D.ietf-6man-exthdr
is trying to solve; perhaps it is merely cluelessness
on my part that the problem/issue isn't obvious to me, 
but education on what problem that I-D solves also 
would be welcome.

Yours,

Ran






From joelja@bogus.com  Thu Oct 14 19:33:39 2010
Return-Path: <joelja@bogus.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 884033A6A73; Thu, 14 Oct 2010 19:33:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.056
X-Spam-Level: 
X-Spam-Status: No, score=-102.056 tagged_above=-999 required=5 tests=[AWL=-0.057, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SU9BllSAS7a2; Thu, 14 Oct 2010 19:33:37 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 17AA13A686B; Thu, 14 Oct 2010 19:33:36 -0700 (PDT)
Received: from joelja-mac.lan (c-98-234-104-156.hsd1.ca.comcast.net [98.234.104.156]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id o9F2Yrug062635 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 15 Oct 2010 02:34:54 GMT (envelope-from joelja@bogus.com)
Message-ID: <4CB7BDCD.4000207@bogus.com>
Date: Thu, 14 Oct 2010 19:34:53 -0700
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com>	<ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com>	<20101014205109.75a23d68@opy.nosense.org>	<DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com> <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com>
In-Reply-To: <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Fri, 15 Oct 2010 02:34:55 +0000 (UTC)
Cc: IPv6 Operations <v6ops@ietf.org>, iesg@ietf.org
Subject: Re: [v6ops] Fwd: I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 02:33:39 -0000

On 10/14/10 1:09 PM, Fred Baker wrote:
> 
> On Oct 14, 2010, at 12:46 PM, james woodyatt wrote:
> 
>> It seems like Mr. Smith and Mr. Arkko are in disagreement about
>> whether software updates should be downloaded and applied
>> automatically, and I don't know how to proceed from here.
> 
> Jari, being on the IESG, is copied in this. I would suggest that he,
> Mark, and Barbara argue their relative cases. At the end of the day,
> the reason that I asked for a final discussion is that there have
> been several changes, and the document has to satisfy not only it's
> last reviewer, but the operational community that is recommending
> it.
> 
> the status as I see it is:
> 
> - Jari wants the patches applied automatically, which assures patch
> updates but removes a level of control from the owner/operator of the
> device
> 
> - Mark wants the patches pushed out but applied with the
> owner/operator's consent
> 
> - Barbara wants the owner/operator to have an interface that can
> apply a patch, but leave anything else undefined; this basically
> preserves the status quo, which means that residential gateways are
> likely to generally *not* track patches and as a result have security
> vulnerabilities, which is also the status quo.
> 
> A middle ground, perhaps, would be to recommend that the manufacturer
> provide an option that the user can select; the present language's
> "by default" suggests this as well. The options would be for the
> device to periodically access a manufacturer web site and download
> updated firmware or for the manufacturer to somehow (blast email?)
> advise the registered owner to do so at their convenience. The issue
> for this draft would be "what is the default", as that will be the
> most common actual behavior. 

This seems a lot alike an implementation detail, if a device does not
update itself automatically then the acceptance of updates by end users
is going to be terribly low, if it does, they might approach 100%. I can
observe in another business that voluntary software updates on mobile
phones (speaking my own employer) have a rather low uptake rate (like
under 10%) ota updates for carrier supported devices on the the other
hand may approach 100%.

so if you actually want the devices to be up-datable in order to address
problems in the field they really do need to do so autonomously, there
no way around that.

Still for a device procured by a consumer it should be between them and
their vendor as to whether this happens.

For the record I think the text for rec-13 is sufficiently strong that
people with a good reason to do so will ignore it and as a general case
recommendation it is fine.

> _______________________________________________ v6ops mailing list 
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
> 


From fernando.gont.netbook.win@gmail.com  Thu Oct 14 23:33:36 2010
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 00B823A6A9B; Thu, 14 Oct 2010 23:33: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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JbNbOUu45Whm; Thu, 14 Oct 2010 23:33:35 -0700 (PDT)
Received: from mail-gy0-f194.google.com (mail-gy0-f194.google.com [209.85.160.194]) by core3.amsl.com (Postfix) with ESMTP id CC5503A6857; Thu, 14 Oct 2010 23:33:34 -0700 (PDT)
Received: by gyd12 with SMTP id 12so112915gyd.1 for <multiple recipients>; Thu, 14 Oct 2010 23:34:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=p20iSlxS5wlqnAJ/Kmu9EvbuQO8M363KULPy0T7mVqo=; b=fYLhDeCt69GBJ2RxhY+VqbufWvMbMKVJMuGZEYoYH4NRr+J11I0BiFndRKSXBQ67Y7 QQwL5WXGVHklXUv2YO5mw0fklrGTftjAxQWOskNG3bDBIxtzYBwCJWWmPW/ERh0VXyFX txlk0orDUc6JP0glClxzD3Z3FE+OZ39Pkxscc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=TZKfFdfudHx6VAVdkIw/gmVlMXMqYV0sIgndZVr1AK+w0HwCNRpbt8XaYRh5fGrQ8R 7AuRyddOTUvXd6ow5ZcUkwdA3HHRzk7miBCzcpLAtU4Yb+rzH6DzgDiPz+9daOChjD0Z 1NWctYkC5gqvMmz269UG/FBDEyg5G6wrCLi7M=
Received: by 10.150.216.5 with SMTP id o5mr1040436ybg.37.1287124495245; Thu, 14 Oct 2010 23:34:55 -0700 (PDT)
Received: from [192.168.2.4] ([186.137.76.195]) by mx.google.com with ESMTPS id q36sm1692194ybk.6.2010.10.14.23.34.49 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 14 Oct 2010 23:34:54 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4CB7F603.6000807@gont.com.ar>
Date: Fri, 15 Oct 2010 03:34:43 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Joel Jaeggli <joelja@bogus.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com>	<ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com>	<20101014205109.75a23d68@opy.nosense.org>	<DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com>	<BE0267C0-302D-48CB-A167-F300B0170922@cisco.com> <4CB7BDCD.4000207@bogus.com>
In-Reply-To: <4CB7BDCD.4000207@bogus.com>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, iesg@ietf.org
Subject: Re: [v6ops] Fwd:	I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 06:33:36 -0000

On 14/10/2010 11:34 p.m., Joel Jaeggli wrote:

>> - Barbara wants the owner/operator to have an interface that can
>> apply a patch, but leave anything else undefined; this basically
>> preserves the status quo, which means that residential gateways are
>> likely to generally *not* track patches and as a result have security
>> vulnerabilities, which is also the status quo.

Not to add more noise to this issue, but.... have you guys considered
Evilgrade? (see
<https://www.defcon.org/images/defcon-18/dc-18-presentations/Amato-Kirschabum/DEFCON-18-Amato-Kirschabum-Evilgrade.pdf>
and others...)

Bottom-line: beware with what you recommend, because you might get it ;-)

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





From joelja@bogus.com  Fri Oct 15 00:17:54 2010
Return-Path: <joelja@bogus.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 812DF3A6C64; Fri, 15 Oct 2010 00:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.354
X-Spam-Level: 
X-Spam-Status: No, score=-102.354 tagged_above=-999 required=5 tests=[AWL=0.245, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JFqVjfJgOmq5; Fri, 15 Oct 2010 00:17:53 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 90D793A6C07; Fri, 15 Oct 2010 00:17:52 -0700 (PDT)
Received: from [192.168.1.240] (c-98-234-104-156.hsd1.ca.comcast.net [98.234.104.156]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id o9F7J8mN078987 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 15 Oct 2010 07:19:08 GMT (envelope-from joelja@bogus.com)
References: <20101012180001.D0C3C3A69CE@core3.amsl.com>	<ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com>	<20101014205109.75a23d68@opy.nosense.org>	<DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com>	<BE0267C0-302D-48CB-A167-F300B0170922@cisco.com> <4CB7BDCD.4000207@bogus.com> <4CB7F603.6000807@gont.com.ar>
Message-Id: <B780B1AC-332E-4A9A-BD39-BD16903B31A2@bogus.com>
From: Joel Jaeggli <joelja@bogus.com>
To: Fernando Gont <fernando@gont.com.ar>
In-Reply-To: <4CB7F603.6000807@gont.com.ar>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPad Mail (7B405)
Mime-Version: 1.0 (iPad Mail 7B405)
Date: Fri, 15 Oct 2010 00:19:25 -0700
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Fri, 15 Oct 2010 07:19:09 +0000 (UTC)
Cc: IPv6 Operations <v6ops@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [v6ops] Fwd:	I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 07:17:54 -0000

Joel's widget number 2

On Oct 14, 2010, at 23:34, Fernando Gont <fernando@gont.com.ar> wrote:

> On 14/10/2010 11:34 p.m., Joel Jaeggli wrote:
>=20
>>> Yhy- Barbara wants the owner/operator to have an interface that can
>>> apply a patch, but leave anything else undefined; this basically
>>> preserves the status quo, which means that residential gateways are
>>> likely to generally *not* track patches and as a result have =
security
>>> vulnerabilities, which is also the status quo.
>=20
> Not to add more noise to this issue, but.... have you guys considered
> Evilgrade? (see
> =
<https://www.defcon.org/images/defcon-18/dc-18-presentations/Amato-Kirscha=
bum/DEFCON-18-Amato-Kirschabum-Evilgrade.pdf>
> and others...)
>=20
> Bottom-line: beware with what you recommend, because you might get it =
;-)

There are abundant examples of how to build a trustworthy update system. =
The fact that a bad one can also be built is not reason to avoid using =
one.

> Thanks,
> --=20
> Fernando Gont
> e-mail: fernando@gont.com.ar || fgont@acm.org
> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
>=20
>=20
>=20
>=20

From fernando.gont.netbook.win@gmail.com  Fri Oct 15 00:41:16 2010
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 73DCD3A6778; Fri, 15 Oct 2010 00:41:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.321
X-Spam-Level: 
X-Spam-Status: No, score=-2.321 tagged_above=-999 required=5 tests=[AWL=0.278,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dd8eezWdlcRk; Fri, 15 Oct 2010 00:41:15 -0700 (PDT)
Received: from mail-gx0-f194.google.com (mail-gx0-f194.google.com [209.85.161.194]) by core3.amsl.com (Postfix) with ESMTP id 2D3A53A6774; Fri, 15 Oct 2010 00:41:15 -0700 (PDT)
Received: by gxk23 with SMTP id 23so137010gxk.1 for <multiple recipients>; Fri, 15 Oct 2010 00:42:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=2Dm+sq6sUqXPoyEiMg1OVKO7ZJSMqd8Iq+hzat3YPww=; b=tVBGs3GCyNpOHwR7pARlOgU6Ztv2JrsuP+R93fHSxp/yMGd1EfIKXjy7rzGksWdrmm nSZ2ZVrfhSSIEIfHajlLBJ4LwrER1V/oJWJVh6CkpYcWGSkkWH/zlnfms3TUXi39hQ8/ CXr9ICPNEaP4VresNDYyyedTc3Jppf803UOuk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=t7oDGomuSkvmpuBQJ+g8VaFiuVZOOe7Epan3yQy877xeOTayI83IOojsIsKzSlVwGt ft634wI8DuYUgE+z2MshamaNvOALX1JAVvsNowoFtjes2hWhuB2fxoneH9PR3Ybo3bPn ZMYRtvz9vjhJ0d/M4uvwEAv9oIQzab1kapVlM=
Received: by 10.151.155.2 with SMTP id h2mr1030288ybo.216.1287128554190; Fri, 15 Oct 2010 00:42:34 -0700 (PDT)
Received: from [192.168.0.124] (61-128-17-190.fibertel.com.ar [190.17.128.61]) by mx.google.com with ESMTPS id v3sm10238104yba.2.2010.10.15.00.42.30 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 15 Oct 2010 00:42:33 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4CB805E3.6020503@gont.com.ar>
Date: Fri, 15 Oct 2010 04:42:27 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Joel Jaeggli <joelja@bogus.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com>	<ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com>	<20101014205109.75a23d68@opy.nosense.org>	<DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com>	<BE0267C0-302D-48CB-A167-F300B0170922@cisco.com> <4CB7BDCD.4000207@bogus.com> <4CB7F603.6000807@gont.com.ar> <B780B1AC-332E-4A9A-BD39-BD16903B31A2@bogus.com>
In-Reply-To: <B780B1AC-332E-4A9A-BD39-BD16903B31A2@bogus.com>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [v6ops] Fwd:	I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 07:41:16 -0000

On 15/10/2010 04:19 a.m., Joel Jaeggli wrote:

>> Not to add more noise to this issue, but.... have you guys
>> considered Evilgrade? (see 
>> <https://www.defcon.org/images/defcon-18/dc-18-presentations/Amato-Kirschabum/DEFCON-18-Amato-Kirschabum-Evilgrade.pdf>
>>
> There are abundant examples of how to build a trustworthy update
> system. The fact that a bad one can also be built is not reason to
> avoid using one.

If "automatic updates" are mentioned, a note about these issues should
probably be included, too. (a pointer, at the very least... not
necessarily to this specific tool/presentation).

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





From fernando.gont.netbook.win@gmail.com  Fri Oct 15 09:49:22 2010
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F3CD13A6AA8 for <v6ops@core3.amsl.com>; Fri, 15 Oct 2010 09:49:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[AWL=-0.368, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mMXhScD-hGz5 for <v6ops@core3.amsl.com>; Fri, 15 Oct 2010 09:49:19 -0700 (PDT)
Received: from mail-iw0-f194.google.com (mail-iw0-f194.google.com [209.85.214.194]) by core3.amsl.com (Postfix) with ESMTP id 031DA3A6A85 for <v6ops@ietf.org>; Fri, 15 Oct 2010 09:49:18 -0700 (PDT)
Received: by iwn9 with SMTP id 9so390934iwn.1 for <v6ops@ietf.org>; Fri, 15 Oct 2010 09:50:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=Q1nNnNhEZO51+luxharirYDKK+PwFqvaLCiAT7lZVBU=; b=yCdm8+THlAOMYgJXjCrGaUked8zbzG+uHoiwrh3TxLf0JmWgxqjg2LjV8TbTuThvNv NHhSRAKX1yc21Gf7cCX4fAdlB3jPpJw5bvzCJNXinqBYHfKKg+PLsXmW52m39x1UdCod h0AmEJzdGu8LjbLeThIYcRKwBTjsD4vPEHb6E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=DguIzrYkJhtkCJKNPvIdw0BaQQ/zlIr2ClpM4aldIgdIRITCeZFGGpZGMbYPV1fnhg NzQ3FGXQc1eOn4iST8fPUDTezvBUo/JEU3diNzh4mRsm5mVlrNeMonSo+iAyYrDDdqTr FS0f2LdFqr8VT+EcmR9YRH1CRXxad0hwf5fso=
Received: by 10.42.142.1 with SMTP id q1mr931082icu.119.1287161440420; Fri, 15 Oct 2010 09:50:40 -0700 (PDT)
Received: from [192.168.0.124] (61-128-17-190.fibertel.com.ar [190.17.128.61]) by mx.google.com with ESMTPS id l66sm2390232yhd.20.2010.10.15.09.50.37 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 15 Oct 2010 09:50:38 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4CB7F4B2.3030007@gont.com.ar>
Date: Fri, 15 Oct 2010 03:29:06 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: RJ Atkinson <rja.lists@gmail.com>
References: <C7FCC31E-AC1C-456E-B1DA-A6C524B09099@gmail.com>
In-Reply-To: <C7FCC31E-AC1C-456E-B1DA-A6C524B09099@gmail.com>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Fwd: I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 16:49:22 -0000

On 14/10/2010 07:11 p.m., RJ Atkinson wrote:

> So I've been a bit confused what actual problem I-D.ietf-6man-exthdr
> is trying to solve; perhaps it is merely cluelessness
> on my part that the problem/issue isn't obvious to me, 
> but education on what problem that I-D solves also 
> would be welcome.

Without having read the aforementioned I-D, my take/guess is that it
aims at defining a common syntax for new extension headers.

The "current problem" is that extension headers do not have a common
syntax (TLV-like), and hence a middlebox could possibly *not* be able to
parse the whole header chain to e.g. be able to do deep packet inspection.

That said, I agree with you that one would expect that we already have
enough extension headers such that, in the event you need to define a
new option, there's no need to define a new extension header to include
that option. -- i.e., this issues shouldn't be a problem in practice.

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





From jhw@apple.com  Fri Oct 15 10:54:58 2010
Return-Path: <jhw@apple.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D1FE13A6BD0 for <v6ops@core3.amsl.com>; Fri, 15 Oct 2010 10:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.383
X-Spam-Level: 
X-Spam-Status: No, score=-106.383 tagged_above=-999 required=5 tests=[AWL=0.216, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZAOWtlTArcXi for <v6ops@core3.amsl.com>; Fri, 15 Oct 2010 10:54:58 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 100493A6B9B for <v6ops@ietf.org>; Fri, 15 Oct 2010 10:54:58 -0700 (PDT)
Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out3.apple.com (Postfix) with ESMTP id 1787AAF9EA02; Fri, 15 Oct 2010 10:56:20 -0700 (PDT)
X-AuditID: 11807134-b7c05ae000002d5d-77-4cb895c39c40
Received: from [17.151.110.65] (Unknown_Domain [17.151.110.65]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay14.apple.com (Apple SCV relay) with SMTP id AB.BC.11613.3C598BC4; Fri, 15 Oct 2010 10:56:20 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Fri, 15 Oct 2010 10:56:18 -0700
Message-Id: <54E3BDFE-9FB3-41AE-833B-92FCCA234037@apple.com>
To: IETF V6OPS WG <v6ops@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Subject: [v6ops] draft-ietf-v6ops-cpe-simple-security
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 17:54:59 -0000

everyone--

I'm out of the office today and dealing with family issues this weekend. =
 I'll be checking email periodically, and I'm looking for clear =
direction to revise REC-13 and its surrounding text.  I'm pretty sure =
the boundaries of acceptable opinion on this topic, within both IESG and =
the working group, are narrower than my own, so I don't think I have =
anything to add to the discussion.  I just need to know what to write =
and I'll post an update.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



From rbonica@juniper.net  Fri Oct 15 11:56:35 2010
Return-Path: <rbonica@juniper.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D1453A6B95; Fri, 15 Oct 2010 11:56:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.192
X-Spam-Level: 
X-Spam-Status: No, score=-106.192 tagged_above=-999 required=5 tests=[AWL=-0.193, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G9FQhl9Iooe4; Fri, 15 Oct 2010 11:56:33 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by core3.amsl.com (Postfix) with ESMTP id A9E663A6A2B; Fri, 15 Oct 2010 11:56:31 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKTLikMbkmHLvQ6ZV7NE+huuTd3GCd28hh@postini.com; Fri, 15 Oct 2010 11:57:55 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 15 Oct 2010 11:56:47 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Fri, 15 Oct 2010 14:56:46 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Joel Jaeggli <joelja@bogus.com>, Fred Baker <fred@cisco.com>
Date: Fri, 15 Oct 2010 14:56:45 -0400
Thread-Topic: [v6ops] Fwd:	I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
Thread-Index: ActsEZVUmCv+41ApSaC4TcCgZY/oGAAhIPBg
Message-ID: <13205C286662DE4387D9AF3AC30EF456B020F14DDF@EMBX01-WF.jnpr.net>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com> <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com> <20101014205109.75a23d68@opy.nosense.org> <DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com> <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com> <4CB7BDCD.4000207@bogus.com>
In-Reply-To: <4CB7BDCD.4000207@bogus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPv6 Operations <v6ops@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [v6ops] Fwd:	I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 18:56:35 -0000

Folks,

I think that the business model is important, here.=20

Assume that I have purchased an "managed service" from my friendly, local I=
SP. They provide IPv6 connectivity and drop off a router in my kitchen. I p=
lug my computer into the router and never think about it again. If the ISP =
discovers a bug in the router software, they update it automatically and I =
am none the wiser. (This is the model that Jari suggests. It is also my ISP=
's service model.)

Now, assume that I purchase an "unmanaged service". The ISP provides IPv6 c=
onnectivity and I go to Crazy Eddy's Electronics World to purchase an Acme-=
100 router, running ACME-OS Version 1.1. A few months later, the Acme corpo=
ration discovers a bug in their implementation of feature X. So they releas=
e ACME-OS Version 1.2. While version 1.2 corrects the bug in feature X, it =
introduces another bug in feature Y.

In this case, the user knows best whether he wants to upgrade to version 1.=
2. Users who rely on feature X will want to upgrade, while users who do not=
 rely on feature X will not be so motivated. In this case, the model that M=
ark suggests makes most sense.

Acme corporation wants to sell their gear into both managed and unmanaged e=
nvironments. So, we need to find some middle ground. I would suggest a conf=
iguration switch between the two modes proposed above. Since the vast major=
ity of residential users have no idea what their routers are doing, I would=
 suggest Jari's mode as default.

                                                                     Ron





> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
> Of Joel Jaeggli
> Sent: Thursday, October 14, 2010 10:35 PM
> To: Fred Baker
> Cc: IPv6 Operations; iesg@ietf.org
> Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-
> security-15.txt
>=20
> On 10/14/10 1:09 PM, Fred Baker wrote:
> >
> > On Oct 14, 2010, at 12:46 PM, james woodyatt wrote:
> >
> >> It seems like Mr. Smith and Mr. Arkko are in disagreement about
> >> whether software updates should be downloaded and applied
> >> automatically, and I don't know how to proceed from here.
> >
> > Jari, being on the IESG, is copied in this. I would suggest that he,
> > Mark, and Barbara argue their relative cases. At the end of the day,
> > the reason that I asked for a final discussion is that there have
> > been several changes, and the document has to satisfy not only it's
> > last reviewer, but the operational community that is recommending
> > it.
> >
> > the status as I see it is:
> >
> > - Jari wants the patches applied automatically, which assures patch
> > updates but removes a level of control from the owner/operator of the
> > device
> >
> > - Mark wants the patches pushed out but applied with the
> > owner/operator's consent
> >
> > - Barbara wants the owner/operator to have an interface that can
> > apply a patch, but leave anything else undefined; this basically
> > preserves the status quo, which means that residential gateways are
> > likely to generally *not* track patches and as a result have security
> > vulnerabilities, which is also the status quo.
> >
> > A middle ground, perhaps, would be to recommend that the manufacturer
> > provide an option that the user can select; the present language's
> > "by default" suggests this as well. The options would be for the
> > device to periodically access a manufacturer web site and download
> > updated firmware or for the manufacturer to somehow (blast email?)
> > advise the registered owner to do so at their convenience. The issue
> > for this draft would be "what is the default", as that will be the
> > most common actual behavior.
>=20
> This seems a lot alike an implementation detail, if a device does not
> update itself automatically then the acceptance of updates by end users
> is going to be terribly low, if it does, they might approach 100%. I
> can
> observe in another business that voluntary software updates on mobile
> phones (speaking my own employer) have a rather low uptake rate (like
> under 10%) ota updates for carrier supported devices on the the other
> hand may approach 100%.
>=20
> so if you actually want the devices to be up-datable in order to
> address
> problems in the field they really do need to do so autonomously, there
> no way around that.
>=20
> Still for a device procured by a consumer it should be between them and
> their vendor as to whether this happens.
>=20
> For the record I think the text for rec-13 is sufficiently strong that
> people with a good reason to do so will ignore it and as a general case
> recommendation it is fine.
>=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 yiu_lee@cable.comcast.com  Fri Oct 15 13:36:50 2010
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1F58A3A6CED; Fri, 15 Oct 2010 13:36:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.297
X-Spam-Level: 
X-Spam-Status: No, score=-104.297 tagged_above=-999 required=5 tests=[AWL=1.499, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SJ9y-zIltWWz; Fri, 15 Oct 2010 13:36:47 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id D5F043A6CD4; Fri, 15 Oct 2010 13:36:46 -0700 (PDT)
Received: from ([24.40.55.42]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.99299556; Fri, 15 Oct 2010 16:38:06 -0400
Received: from PACDCEXCMB04.cable.comcast.com (24.40.15.86) by PACDCEXHUB01.cable.comcast.com (24.40.55.42) with Microsoft SMTP Server id 14.1.218.12; Fri, 15 Oct 2010 16:38:05 -0400
Received: from 68.81.91.8 ([68.81.91.8]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) via Exchange Front-End Server legacywebmail.comcast.com ([24.40.8.154]) with Microsoft Exchange Server HTTP-DAV ; Fri, 15 Oct 2010 20:38:05 +0000
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Fri, 15 Oct 2010 16:38:03 -0400
From: "Yiu L. Lee" <yiu_lee@cable.comcast.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Fred Baker <fred@cisco.com>
Message-ID: <C8DE33EB.3F293%yiu_lee@cable.comcast.com>
Thread-Topic: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
Thread-Index: ActsqN0alwMPFehaNUmV/vFIP+qsxg==
In-Reply-To: <4CB76693.8@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, iesg@ietf.org
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 20:36:50 -0000

As a user, I also don't like automatic update w/o my consent.


On 10/14/10 4:22 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
wrote:

> On 2010-10-15 09:09, Fred Baker wrote:
>> On Oct 14, 2010, at 12:46 PM, james woodyatt wrote:
>> 
>>> It seems like Mr. Smith and Mr. Arkko are in disagreement about whether
>>> software updates should be downloaded and applied automatically, and I don't
>>> know how to proceed from here.
>> 
>> Jari, being on the IESG, is copied in this. I would suggest that he, Mark,
>> and Barbara argue their relative cases. At the end of the day, the reason
>> that I asked for a final discussion is that there have been several changes,
>> and the document has to satisfy not only it's last reviewer, but the
>> operational community that is recommending it.
>> 
>> the status as I see it is:
>> 
>>  - Jari wants the patches applied automatically, which assures patch updates
>> but removes a level of control from the owner/operator of the device
> 
> Speaking as a user, I deeply hate systems that install patches by default
> without asking me. I don't think the IETF should be taking a position on
> that one way or the other. On the other, leaving patching up to the user's
> initiative has been thoroughly proved to fail. So I think Mark's
> position is best, but I'd still prefer us to be neutral: recommend that
> the implementor/vendor provides a patch mechanism, but not saying anything
> about automatic vs consent vs voluntary.
> 
>     Brian
> 
>>  - Mark wants the patches pushed out but applied with the owner/operator's
>> consent
>> 
>>  - Barbara wants the owner/operator to have an interface that can apply a
>> patch, but leave anything else undefined; this basically preserves the status
>> quo, which means that residential gateways are likely to generally *not*
>> track patches and as a result have security vulnerabilities, which is also
>> the status quo.
>> 
>> A middle ground, perhaps, would be to recommend that the manufacturer provide
>> an option that the user can select; the present language's "by default"
>> suggests this as well. The options would be for the device to periodically
>> access a manufacturer web site and download updated firmware or for the
>> manufacturer to somehow (blast email?) advise the registered owner to do so
>> at their convenience. The issue for this draft would be "what is the
>> default", as that will be the most common actual behavior.
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From therbst@silverspringnet.com  Fri Oct 15 13:40:00 2010
Return-Path: <therbst@silverspringnet.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 03A993A6CE8; Fri, 15 Oct 2010 13:40:00 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GaxigYNPqx5c; Fri, 15 Oct 2010 13:39:59 -0700 (PDT)
Received: from it-ipcorp-01.silverspringnet.com (it-ipcorp-01.silverspringnet.com [74.121.22.25]) by core3.amsl.com (Postfix) with ESMTP id 19A3B3A6CE2; Fri, 15 Oct 2010 13:39:59 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApsEAABZuEwKyAE+/2dsb2JhbACiFcEVhUkEhFSJEIJQ
X-IronPort-AV: E=Sophos;i="4.57,338,1283756400";  d="scan'208";a="1533308"
Received: from unknown (HELO IT-EXCA-02.silverspringnet.com) ([10.200.1.62]) by it-ipcorp-01.silverspringnet.com with ESMTP; 15 Oct 2010 13:41:20 -0700
Received: from IT-EXMB-01.silverspringnet.com ([fe80::b81e:2d5b:d263:6c44]) by IT-EXCA-02.silverspringnet.com ([::1]) with mapi; Fri, 15 Oct 2010 13:41:20 -0700
From: Thomas Herbst <therbst@silverspringnet.com>
To: "Yiu L. Lee" <yiu_lee@cable.comcast.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Fred Baker <fred@cisco.com>
Date: Fri, 15 Oct 2010 13:41:20 -0700
Thread-Topic: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
Thread-Index: ActsqN0alwMPFehaNUmV/vFIP+qsxgAABlbw
Message-ID: <0C81AF1155244B419CCE672396E82FDF2F3CD5F2@IT-EXMB-01.silverspringnet.com>
References: <4CB76693.8@gmail.com> <C8DE33EB.3F293%yiu_lee@cable.comcast.com>
In-Reply-To: <C8DE33EB.3F293%yiu_lee@cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPv6 Operations <v6ops@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 20:40:00 -0000

Based on past work in a consumer networking company, my understanding is th=
at there are places in Europe where=20
automatic updates are not legal if the device is consumer owned.

-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of Y=
iu L. Lee
Sent: Friday, October 15, 2010 1:38 PM
To: Brian E Carpenter; Fred Baker
Cc: IPv6 Operations; iesg@ietf.org
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-1=
5.txt

As a user, I also don't like automatic update w/o my consent.


On 10/14/10 4:22 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
wrote:

> On 2010-10-15 09:09, Fred Baker wrote:
>> On Oct 14, 2010, at 12:46 PM, james woodyatt wrote:
>>=20
>>> It seems like Mr. Smith and Mr. Arkko are in disagreement about whether
>>> software updates should be downloaded and applied automatically, and I =
don't
>>> know how to proceed from here.
>>=20
>> Jari, being on the IESG, is copied in this. I would suggest that he, Mar=
k,
>> and Barbara argue their relative cases. At the end of the day, the reaso=
n
>> that I asked for a final discussion is that there have been several chan=
ges,
>> and the document has to satisfy not only it's last reviewer, but the
>> operational community that is recommending it.
>>=20
>> the status as I see it is:
>>=20
>>  - Jari wants the patches applied automatically, which assures patch upd=
ates
>> but removes a level of control from the owner/operator of the device
>=20
> Speaking as a user, I deeply hate systems that install patches by default
> without asking me. I don't think the IETF should be taking a position on
> that one way or the other. On the other, leaving patching up to the user'=
s
> initiative has been thoroughly proved to fail. So I think Mark's
> position is best, but I'd still prefer us to be neutral: recommend that
> the implementor/vendor provides a patch mechanism, but not saying anythin=
g
> about automatic vs consent vs voluntary.
>=20
>     Brian
>=20
>>  - Mark wants the patches pushed out but applied with the owner/operator=
's
>> consent
>> =09
>>  - Barbara wants the owner/operator to have an interface that can apply =
a
>> patch, but leave anything else undefined; this basically preserves the s=
tatus
>> quo, which means that residential gateways are likely to generally *not*
>> track patches and as a result have security vulnerabilities, which is al=
so
>> the status quo.
>>=20
>> A middle ground, perhaps, would be to recommend that the manufacturer pr=
ovide
>> an option that the user can select; the present language's "by default"
>> suggests this as well. The options would be for the device to periodical=
ly
>> access a manufacturer web site and download updated firmware or for the
>> manufacturer to somehow (blast email?) advise the registered owner to do=
 so
>> at their convenience. The issue for this draft would be "what is the
>> default", as that will be the most common actual behavior.
>> _______________________________________________
>> 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

_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

From drc@virtualized.org  Fri Oct 15 13:59:25 2010
Return-Path: <drc@virtualized.org>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D52F93A6BCC; Fri, 15 Oct 2010 13:59:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.821
X-Spam-Level: 
X-Spam-Status: No, score=-2.821 tagged_above=-999 required=5 tests=[AWL=-0.222, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 81nUwV3x4m5W; Fri, 15 Oct 2010 13:59:24 -0700 (PDT)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190]) by core3.amsl.com (Postfix) with ESMTP id E0A953A6B3D; Fri, 15 Oct 2010 13:59:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by virtualized.org (Postfix) with ESMTP id ECE0EEB755E; Fri, 15 Oct 2010 14:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at virtualized.org
Received: from virtualized.org ([127.0.0.1]) by localhost (trantor.virtualized.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J5hvuUlt+hjl; Fri, 15 Oct 2010 14:00:44 -0700 (PDT)
Received: from [10.0.1.7] (cpe-70-95-123-210.hawaii.res.rr.com [70.95.123.210]) by virtualized.org (Postfix) with ESMTP id CDCE3EB754D; Fri, 15 Oct 2010 14:00:43 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: David Conrad <drc@virtualized.org>
In-Reply-To: <C8DE33EB.3F293%yiu_lee@cable.comcast.com>
Date: Fri, 15 Oct 2010 11:00:42 -1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <65A20F28-24CD-48FF-8852-97DCDD2AFCF7@virtualized.org>
References: <C8DE33EB.3F293%yiu_lee@cable.comcast.com>
To: "Yiu L. Lee" <yiu_lee@cable.comcast.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>, iesg@ietf.org
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 20:59:26 -0000

On Oct 15, 2010, at 10:38 AM, Yiu L. Lee wrote:
> As a user, I also don't like automatic update w/o my consent.

If you have a TiVo, does it bother you that it updates itself without =
consent?

I might observe that anyone on this mailing list is not the target =
audience of automatic update. =20

I suspect it would be more useful to view this from a risk =
mitigation/"least harm" perspective.  The reality is that the vast =
majority of users are unlikely to even know how to log into their CPE, =
much less be able to log in, determine whether or not installing an =
update is a good idea, and install that update.  Given the types of =
attacks we're seeing today (e.g., Drive-by Pharming), it seems to me =
that there are more risks to the Internet as a whole to requiring manual =
intervention than not.

With that in mind, I'd prefer that there be a recommendation that =
automatic updates be enabled by default with a mechanism to allow users =
to disable those updates if they so desire.

Regards,
-drc


From joelja@bogus.com  Fri Oct 15 14:18:35 2010
Return-Path: <joelja@bogus.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F248D3A6D3B; Fri, 15 Oct 2010 14:18:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.316
X-Spam-Level: 
X-Spam-Status: No, score=-102.316 tagged_above=-999 required=5 tests=[AWL=-0.317, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QH7vXFNWguih; Fri, 15 Oct 2010 14:18:34 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 795263A6D39; Fri, 15 Oct 2010 14:18:33 -0700 (PDT)
Received: from dhcp-176.nokia.net (dhcp-176.nokia.net [192.103.16.176] (may be forged)) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id o9FLJo6G039961 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 15 Oct 2010 21:19:51 GMT (envelope-from joelja@bogus.com)
Message-ID: <4CB8C576.40804@bogus.com>
Date: Fri, 15 Oct 2010 14:19:50 -0700
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: "Yiu L. Lee" <yiu_lee@cable.comcast.com>
References: <C8DE33EB.3F293%yiu_lee@cable.comcast.com>
In-Reply-To: <C8DE33EB.3F293%yiu_lee@cable.comcast.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Fri, 15 Oct 2010 21:19:51 +0000 (UTC)
Cc: iesg@ietf.org, IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 21:18:35 -0000

On 10/15/10 1:38 PM, Yiu L. Lee wrote:
> As a user, I also don't like automatic update w/o my consent.

however comcast automatically updates your STB's and the docsis modems
with some degree of frequency...

Who owns and or manages devices that constitute the cpe varies by device
type business model and so on.

Your virus and potentially IDS and firewall definitions probably update
themselves automatically and without your consent, you can in all
likelihood turn that off.

Saying generically,  "I don't like automatically applying updates" is
fine, stating that consumer oriented devices SHOULD NOT update
themselves without a users' consent dooms them to running only the
software that they came with by in large.

> 
> On 10/14/10 4:22 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> wrote:
> 
>> On 2010-10-15 09:09, Fred Baker wrote:
>>> On Oct 14, 2010, at 12:46 PM, james woodyatt wrote:
>>>
>>>> It seems like Mr. Smith and Mr. Arkko are in disagreement about whether
>>>> software updates should be downloaded and applied automatically, and I don't
>>>> know how to proceed from here.
>>>
>>> Jari, being on the IESG, is copied in this. I would suggest that he, Mark,
>>> and Barbara argue their relative cases. At the end of the day, the reason
>>> that I asked for a final discussion is that there have been several changes,
>>> and the document has to satisfy not only it's last reviewer, but the
>>> operational community that is recommending it.
>>>
>>> the status as I see it is:
>>>
>>>  - Jari wants the patches applied automatically, which assures patch updates
>>> but removes a level of control from the owner/operator of the device
>>
>> Speaking as a user, I deeply hate systems that install patches by default
>> without asking me. I don't think the IETF should be taking a position on
>> that one way or the other. On the other, leaving patching up to the user's
>> initiative has been thoroughly proved to fail. So I think Mark's
>> position is best, but I'd still prefer us to be neutral: recommend that
>> the implementor/vendor provides a patch mechanism, but not saying anything
>> about automatic vs consent vs voluntary.
>>
>>     Brian
>>
>>>  - Mark wants the patches pushed out but applied with the owner/operator's
>>> consent
>>>
>>>  - Barbara wants the owner/operator to have an interface that can apply a
>>> patch, but leave anything else undefined; this basically preserves the status
>>> quo, which means that residential gateways are likely to generally *not*
>>> track patches and as a result have security vulnerabilities, which is also
>>> the status quo.
>>>
>>> A middle ground, perhaps, would be to recommend that the manufacturer provide
>>> an option that the user can select; the present language's "by default"
>>> suggests this as well. The options would be for the device to periodically
>>> access a manufacturer web site and download updated firmware or for the
>>> manufacturer to somehow (blast email?) advise the registered owner to do so
>>> at their convenience. The issue for this draft would be "what is the
>>> default", as that will be the most common actual behavior.
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> 


From yiu_lee@cable.comcast.com  Fri Oct 15 14:24:33 2010
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 25EC73A6BB3; Fri, 15 Oct 2010 14:24:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.35
X-Spam-Level: 
X-Spam-Status: No, score=-104.35 tagged_above=-999 required=5 tests=[AWL=1.446, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JMJW6fKkxk79; Fri, 15 Oct 2010 14:24:32 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 9E2C23A6B94; Fri, 15 Oct 2010 14:24:31 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.99315834; Fri, 15 Oct 2010 17:25:47 -0400
Received: from PACDCEXCMB04.cable.comcast.com (24.40.15.86) by PACDCEXHUB02.cable.comcast.com (24.40.55.41) with Microsoft SMTP Server id 14.1.218.12; Fri, 15 Oct 2010 17:25:47 -0400
Received: from 68.81.91.8 ([68.81.91.8]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) via Exchange Front-End Server legacywebmail.comcast.com ([24.40.8.154]) with Microsoft Exchange Server HTTP-DAV ; Fri, 15 Oct 2010 21:25:46 +0000
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Fri, 15 Oct 2010 17:25:45 -0400
From: "Yiu L. Lee" <yiu_lee@cable.comcast.com>
To: Joel Jaeggli <joelja@bogus.com>
Message-ID: <C8DE3F19.3F2A3%yiu_lee@cable.comcast.com>
Thread-Topic: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
Thread-Index: Actsr4b9jDYCGBkGj0WUAA9ujcj0GA==
In-Reply-To: <4CB8C576.40804@bogus.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Cc: iesg@ietf.org, IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 21:24:33 -0000

I give this comment as a user.

If this is a managed device (STB and CM), I don't mind they will do the
update for me. I know that if bad things happened, I could ask for a new
one. However, if this is an unmanaged device, I would like to be informed.
Any update has risk, I just want to make sure the users will understand the
risk.


On 10/15/10 5:19 PM, "Joel Jaeggli" <joelja@bogus.com> wrote:

> On 10/15/10 1:38 PM, Yiu L. Lee wrote:
>> As a user, I also don't like automatic update w/o my consent.
> 
> however comcast automatically updates your STB's and the docsis modems
> with some degree of frequency...
> 
> Who owns and or manages devices that constitute the cpe varies by device
> type business model and so on.
> 
> Your virus and potentially IDS and firewall definitions probably update
> themselves automatically and without your consent, you can in all
> likelihood turn that off.
> 
> Saying generically,  "I don't like automatically applying updates" is
> fine, stating that consumer oriented devices SHOULD NOT update
> themselves without a users' consent dooms them to running only the
> software that they came with by in large.
> 
>> 
>> On 10/14/10 4:22 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
>> wrote:
>> 
>>> On 2010-10-15 09:09, Fred Baker wrote:
>>>> On Oct 14, 2010, at 12:46 PM, james woodyatt wrote:
>>>> 
>>>>> It seems like Mr. Smith and Mr. Arkko are in disagreement about whether
>>>>> software updates should be downloaded and applied automatically, and I
>>>>> don't
>>>>> know how to proceed from here.
>>>> 
>>>> Jari, being on the IESG, is copied in this. I would suggest that he, Mark,
>>>> and Barbara argue their relative cases. At the end of the day, the reason
>>>> that I asked for a final discussion is that there have been several
>>>> changes,
>>>> and the document has to satisfy not only it's last reviewer, but the
>>>> operational community that is recommending it.
>>>> 
>>>> the status as I see it is:
>>>> 
>>>>  - Jari wants the patches applied automatically, which assures patch
>>>> updates
>>>> but removes a level of control from the owner/operator of the device
>>> 
>>> Speaking as a user, I deeply hate systems that install patches by default
>>> without asking me. I don't think the IETF should be taking a position on
>>> that one way or the other. On the other, leaving patching up to the user's
>>> initiative has been thoroughly proved to fail. So I think Mark's
>>> position is best, but I'd still prefer us to be neutral: recommend that
>>> the implementor/vendor provides a patch mechanism, but not saying anything
>>> about automatic vs consent vs voluntary.
>>> 
>>>     Brian
>>> 
>>>>  - Mark wants the patches pushed out but applied with the owner/operator's
>>>> consent
>>>> 
>>>>  - Barbara wants the owner/operator to have an interface that can apply a
>>>> patch, but leave anything else undefined; this basically preserves the
>>>> status
>>>> quo, which means that residential gateways are likely to generally *not*
>>>> track patches and as a result have security vulnerabilities, which is also
>>>> the status quo.
>>>> 
>>>> A middle ground, perhaps, would be to recommend that the manufacturer
>>>> provide
>>>> an option that the user can select; the present language's "by default"
>>>> suggests this as well. The options would be for the device to periodically
>>>> access a manufacturer web site and download updated firmware or for the
>>>> manufacturer to somehow (blast email?) advise the registered owner to do so
>>>> at their convenience. The issue for this draft would be "what is the
>>>> default", as that will be the most common actual behavior.
>>>> _______________________________________________
>>>> v6ops mailing list
>>>> v6ops@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>> 
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>> 
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>> 
> 


From nick@inex.ie  Fri Oct 15 14:26:29 2010
Return-Path: <nick@inex.ie>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 021403A6D29 for <v6ops@core3.amsl.com>; Fri, 15 Oct 2010 14:26:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ehywX1h7nRHh for <v6ops@core3.amsl.com>; Fri, 15 Oct 2010 14:26:27 -0700 (PDT)
Received: from mail.acquirer.com (unknown [IPv6:2001:1bb8:2004:150::2]) by core3.amsl.com (Postfix) with ESMTP id CE9CB3A69A8 for <v6ops@ietf.org>; Fri, 15 Oct 2010 14:26:26 -0700 (PDT)
X-Envelope-To: <v6ops@ietf.org>
Received: from crumpet.foobar.org (crumpet.foobar.org [10.230.100.249]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.3) with ESMTP id o9FLRcjR027402 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <v6ops@ietf.org>; Fri, 15 Oct 2010 22:27:44 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <4CB8C74A.2060007@inex.ie>
Date: Fri, 15 Oct 2010 22:27:38 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.1.12) Gecko/20100914 Thunderbird/3.0.8
MIME-Version: 1.0
To: v6ops@ietf.org
References: <20101012180001.D0C3C3A69CE@core3.amsl.com>	<ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com>	<20101014205109.75a23d68@opy.nosense.org>	<DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com>	<BE0267C0-302D-48CB-A167-F300B0170922@cisco.com> <4CB76693.8@gmail.com>
In-Reply-To: <4CB76693.8@gmail.com>
X-Enigmail-Version: 1.0.1
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [v6ops] Fwd:	I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 21:26:29 -0000

On 14/10/2010 21:22, Brian E Carpenter wrote:
> Speaking as a user, I deeply hate systems that install patches by default
> without asking me. I don't think the IETF should be taking a position on
> that one way or the other. On the other, leaving patching up to the user's
> initiative has been thoroughly proved to fail. So I think Mark's
> position is best, but I'd still prefer us to be neutral: recommend that
> the implementor/vendor provides a patch mechanism, but not saying anything
> about automatic vs consent vs voluntary.

Speaking as an end user, I don't have a major problem with CPEs updating
themselves automatically.  Other than that, I agree with Brian completely.

Nick

From nick@inex.ie  Fri Oct 15 14:28:44 2010
Return-Path: <nick@inex.ie>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4CE353A6D31 for <v6ops@core3.amsl.com>; Fri, 15 Oct 2010 14:28:44 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YFmS6lROsmZ2 for <v6ops@core3.amsl.com>; Fri, 15 Oct 2010 14:28:43 -0700 (PDT)
Received: from mail.acquirer.com (unknown [IPv6:2001:1bb8:2004:150::2]) by core3.amsl.com (Postfix) with ESMTP id 9A9E33A69A8 for <v6ops@ietf.org>; Fri, 15 Oct 2010 14:28:42 -0700 (PDT)
X-Envelope-To: <v6ops@ietf.org>
Received: from crumpet.foobar.org (crumpet.foobar.org [10.230.100.249]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.3) with ESMTP id o9FLTuo0048645 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <v6ops@ietf.org>; Fri, 15 Oct 2010 22:30:01 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <4CB8C7D4.3090903@inex.ie>
Date: Fri, 15 Oct 2010 22:29:56 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.1.12) Gecko/20100914 Thunderbird/3.0.8
MIME-Version: 1.0
To: v6ops@ietf.org
References: <C8DE3F19.3F2A3%yiu_lee@cable.comcast.com>
In-Reply-To: <C8DE3F19.3F2A3%yiu_lee@cable.comcast.com>
X-Enigmail-Version: 1.0.1
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 21:28:44 -0000

On 15/10/2010 22:25, Yiu L. Lee wrote:
> Any update has risk, I just want to make sure the users will understand the
> risk.

Most users generally don't understand and aren't interested in knowing
about the risk associated with automatic updates.  You are the exception.

Oh dear.  This is becoming a bikeshed issue.

Nick

From yiu_lee@cable.comcast.com  Fri Oct 15 14:33:49 2010
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB1453A69A8; Fri, 15 Oct 2010 14:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.7
X-Spam-Level: 
X-Spam-Status: No, score=-104.7 tagged_above=-999 required=5 tests=[AWL=1.696,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368,  RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TigoxRK79VDw; Fri, 15 Oct 2010 14:33:48 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 410D73A6B9D; Fri, 15 Oct 2010 14:33:48 -0700 (PDT)
Received: from ([24.40.55.40]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.99318387; Fri, 15 Oct 2010 17:35:06 -0400
Received: from PACDCEXCMB04.cable.comcast.com (24.40.15.86) by pacdcexhub03.cable.comcast.com (24.40.55.40) with Microsoft SMTP Server id 14.1.218.12; Fri, 15 Oct 2010 17:35:06 -0400
Received: from 68.81.91.8 ([68.81.91.8]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) via Exchange Front-End Server legacywebmail.comcast.com ([24.40.8.154]) with Microsoft Exchange Server HTTP-DAV ; Fri, 15 Oct 2010 21:35:03 +0000
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Fri, 15 Oct 2010 17:35:02 -0400
From: "Yiu L. Lee" <yiu_lee@cable.comcast.com>
To: David Conrad <drc@virtualized.org>
Message-ID: <C8DE4146.3F2AA%yiu_lee@cable.comcast.com>
Thread-Topic: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
Thread-Index: ActssNL8yV8XgZ2ymEW8L6IkBg8SoA==
In-Reply-To: <65A20F28-24CD-48FF-8852-97DCDD2AFCF7@virtualized.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, iesg@ietf.org
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 21:33:49 -0000

Hi Dave,

> If you have a TiVo, does it bother you that it updates itself without consent?
> 
I don't own a TiVo, so I can't comment.

> I might observe that anyone on this mailing list is not the target audience of
> automatic update.
>
> I suspect it would be more useful to view this from a risk mitigation/"least
> harm" perspective.  The reality is that the vast majority of users are
> unlikely to even know how to log into their CPE, much less be able to log in,
> determine whether or not installing an update is a good idea, and install that
> update.  Given the types of attacks we're seeing today (e.g., Drive-by
> Pharming), it seems to me that there are more risks to the Internet as a whole
> to requiring manual intervention than not.
> 
Agreed

> With that in mind, I'd prefer that there be a recommendation that automatic
> updates be enabled by default with a mechanism to allow users to disable those
> updates if they so desire.
> 
I think this is the linux, Windows and MacOSX approach. I think this is
acceptable to turn on the automatic update by default and let users to
disable it if they decide to.

Regards,
Yiu




From mbaugher@cisco.com  Fri Oct 15 14:38:52 2010
Return-Path: <mbaugher@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C79FA3A69A8; Fri, 15 Oct 2010 14:38:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.128
X-Spam-Level: 
X-Spam-Status: No, score=-10.128 tagged_above=-999 required=5 tests=[AWL=-0.129, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AU6b4uW8kfI5; Fri, 15 Oct 2010 14:38:31 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 67AB03A6BA7; Fri, 15 Oct 2010 14:38:24 -0700 (PDT)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.57,338,1283731200"; d="scan'208";a="604747964"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-6.cisco.com with ESMTP; 15 Oct 2010 21:39:40 +0000
Received: from [192.168.1.127] ([10.21.86.224]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o9FLddmI000124; Fri, 15 Oct 2010 21:39:39 GMT
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Mark Baugher <mbaugher@cisco.com>
In-Reply-To: <0C81AF1155244B419CCE672396E82FDF2F3CD5F2@IT-EXMB-01.silverspringnet.com>
Date: Fri, 15 Oct 2010 14:39:38 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <59A96C7A-EB87-4A28-AB2C-16C723A75F34@cisco.com>
References: <4CB76693.8@gmail.com> <C8DE33EB.3F293%yiu_lee@cable.comcast.com> <0C81AF1155244B419CCE672396E82FDF2F3CD5F2@IT-EXMB-01.silverspringnet.com>
To: Thomas Herbst <therbst@silverspringnet.com>
X-Mailer: Apple Mail (2.1081)
Cc: "iesg@ietf.org" <iesg@ietf.org>, IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 21:38:53 -0000

Right, what we have is a policy knob where some vendors will choose to =
one thing, others may choose to do another, and some countries have laws =
dictating what must be done.  I would think that we can motivate a =
SHOULD based on what the WG/IESG thinks is the best practice.  But that =
will vary by vendor, customer agreement, local laws and other matters.

Mark
On Oct 15, 2010, at 1:41 PM, Thomas Herbst wrote:

> Based on past work in a consumer networking company, my understanding =
is that there are places in Europe where=20
> automatic updates are not legal if the device is consumer owned.
>=20
> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf =
Of Yiu L. Lee
> Sent: Friday, October 15, 2010 1:38 PM
> To: Brian E Carpenter; Fred Baker
> Cc: IPv6 Operations; iesg@ietf.org
> Subject: Re: [v6ops] Fwd: I-D =
Action:draft-ietf-v6ops-cpe-simple-security-15.txt
>=20
> As a user, I also don't like automatic update w/o my consent.
>=20
>=20
> On 10/14/10 4:22 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> wrote:
>=20
>> On 2010-10-15 09:09, Fred Baker wrote:
>>> On Oct 14, 2010, at 12:46 PM, james woodyatt wrote:
>>>=20
>>>> It seems like Mr. Smith and Mr. Arkko are in disagreement about =
whether
>>>> software updates should be downloaded and applied automatically, =
and I don't
>>>> know how to proceed from here.
>>>=20
>>> Jari, being on the IESG, is copied in this. I would suggest that he, =
Mark,
>>> and Barbara argue their relative cases. At the end of the day, the =
reason
>>> that I asked for a final discussion is that there have been several =
changes,
>>> and the document has to satisfy not only it's last reviewer, but the
>>> operational community that is recommending it.
>>>=20
>>> the status as I see it is:
>>>=20
>>> - Jari wants the patches applied automatically, which assures patch =
updates
>>> but removes a level of control from the owner/operator of the device
>>=20
>> Speaking as a user, I deeply hate systems that install patches by =
default
>> without asking me. I don't think the IETF should be taking a position =
on
>> that one way or the other. On the other, leaving patching up to the =
user's
>> initiative has been thoroughly proved to fail. So I think Mark's
>> position is best, but I'd still prefer us to be neutral: recommend =
that
>> the implementor/vendor provides a patch mechanism, but not saying =
anything
>> about automatic vs consent vs voluntary.
>>=20
>>    Brian
>>=20
>>> - Mark wants the patches pushed out but applied with the =
owner/operator's
>>> consent
>>> =09
>>> - Barbara wants the owner/operator to have an interface that can =
apply a
>>> patch, but leave anything else undefined; this basically preserves =
the status
>>> quo, which means that residential gateways are likely to generally =
*not*
>>> track patches and as a result have security vulnerabilities, which =
is also
>>> the status quo.
>>>=20
>>> A middle ground, perhaps, would be to recommend that the =
manufacturer provide
>>> an option that the user can select; the present language's "by =
default"
>>> suggests this as well. The options would be for the device to =
periodically
>>> access a manufacturer web site and download updated firmware or for =
the
>>> manufacturer to somehow (blast email?) advise the registered owner =
to do so
>>> at their convenience. The issue for this draft would be "what is the
>>> default", as that will be the most common actual behavior.
>>> _______________________________________________
>>> 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
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From yiu_lee@cable.comcast.com  Fri Oct 15 14:41:32 2010
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 63DF03A6D01 for <v6ops@core3.amsl.com>; Fri, 15 Oct 2010 14:41:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.457
X-Spam-Level: 
X-Spam-Status: No, score=-104.457 tagged_above=-999 required=5 tests=[AWL=1.339, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22y7XNTZ1g6W for <v6ops@core3.amsl.com>; Fri, 15 Oct 2010 14:41:31 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id A6DDD3A6BCC for <v6ops@ietf.org>; Fri, 15 Oct 2010 14:41:27 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.99320026; Fri, 15 Oct 2010 17:42:48 -0400
Received: from PACDCEXCMB04.cable.comcast.com (24.40.15.86) by PACDCEXHUB02.cable.comcast.com (24.40.55.41) with Microsoft SMTP Server id 14.1.218.12; Fri, 15 Oct 2010 17:42:48 -0400
Received: from 68.81.91.8 ([68.81.91.8]) by PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) via Exchange Front-End Server legacywebmail.comcast.com ([24.40.8.154]) with Microsoft Exchange Server HTTP-DAV ; Fri, 15 Oct 2010 21:42:45 +0000
User-Agent: Microsoft-Entourage/12.26.0.100708
Date: Fri, 15 Oct 2010 17:42:45 -0400
From: "Yiu L. Lee" <yiu_lee@cable.comcast.com>
To: Nick Hilliard <nick@inex.ie>, <v6ops@ietf.org>
Message-ID: <C8DE4315.3F2AE%yiu_lee@cable.comcast.com>
Thread-Topic: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
Thread-Index: Actsseb0c2GhReuRxUyxZos18lz75g==
In-Reply-To: <4CB8C7D4.3090903@inex.ie>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 21:41:32 -0000

Well, I learned it in a hard way. One time I updated the firmeware (use the
automatic update feature) of a CPE and it bricked. I can't recover it and of
course I can't get an exchange since the router was older than one year. If
the update procedure is clean every time (like Windows and MacOSX update), I
will not be so careful of the automatic update.

Anyhow, I also agree Brian's email, IETF should recommend patch mechanism
but stay neutral about voluntary vs consent.


On 10/15/10 5:29 PM, "Nick Hilliard" <nick@inex.ie> wrote:

> On 15/10/2010 22:25, Yiu L. Lee wrote:
>> Any update has risk, I just want to make sure the users will understand the
>> risk.
> 
> Most users generally don't understand and aren't interested in knowing
> about the risk associated with automatic updates.  You are the exception.
> 
> Oh dear.  This is becoming a bikeshed issue.
> 
> Nick
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From ipng@69706e6720323030352d30312d31340a.nosense.org  Fri Oct 15 14:47:03 2010
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7EC133A6BBF; Fri, 15 Oct 2010 14:47:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level: 
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[AWL=-0.084, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oA3O0YQRx+Vx; Fri, 15 Oct 2010 14:47:02 -0700 (PDT)
Received: from smtp1.adam.net.au (smtp1.adam.net.au [202.136.110.253]) by core3.amsl.com (Postfix) with ESMTP id 9E3A53A68E0; Fri, 15 Oct 2010 14:47:01 -0700 (PDT)
Received: from 219-90-190-11.ip.adam.com.au ([219.90.190.11] helo=opy.nosense.org) by smtp1.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1P6s8M-0002Ld-6g; Sat, 16 Oct 2010 08:18:14 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 4961A3B31E; Sat, 16 Oct 2010 08:18:13 +1030 (CST)
Date: Sat, 16 Oct 2010 08:18:11 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Ronald Bonica <rbonica@juniper.net>
Message-ID: <20101016081811.1fcb82e5@opy.nosense.org>
In-Reply-To: <13205C286662DE4387D9AF3AC30EF456B020F14DDF@EMBX01-WF.jnpr.net>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com> <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com> <20101014205109.75a23d68@opy.nosense.org> <DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com> <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com> <4CB7BDCD.4000207@bogus.com> <13205C286662DE4387D9AF3AC30EF456B020F14DDF@EMBX01-WF.jnpr.net>
X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: Operations <v6ops@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, IPv6
Subject: Re: [v6ops] Fwd:	I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 21:47:03 -0000

Hi Ron,


On Fri, 15 Oct 2010 14:56:45 -0400
Ronald Bonica <rbonica@juniper.net> wrote:

> Folks,
> 
> I think that the business model is important, here. 
> 
> Assume that I have purchased an "managed service" from my friendly, local ISP. They provide IPv6 connectivity and drop off a router in my kitchen. I plug my computer into the router and never think about it again. If the ISP discovers a bug in the router software, they update it automatically and I am none the wiser. (This is the model that Jari suggests. It is also my ISP's service model.)
> 

The fundamental problem is that this draft is aimed at vendors. With
this clause the vendor chooses when and where to provide firmware
updates to the CPE users. So it won't be possible for the ISP to provide a
managed CPE service, because they don't control and can't be in control
of when the firmware is released to the CPE customers. They may not
even be aware of a new firmware release until they get a flood of
support calls about the Internet breaking.

If the draft is going to persist with specifying that firmware is
automatically distributed and installed, then it is also going to have
to specify mechanisms as to how ISPs are going to put inline with this
process, between the vendor and the CPE, so they're going to be able to
prevent automatic upgrades occurring at times when it is inconvenient to
customers. Of course, that will only be successful if all CPE vendors
comply with this "ISP controlled" mechanism. That'll also create an
additonal burden on the ISPs because they'll end up being responsible
for software maintenance for their customer's CPE, even in markets
where customers can purchase CPE independently of ISPs.

Think about applying this model to other devices and I hope you'll see
the fundamental problem -

o  would you be happy that your Internet attached TV's firmware is
automatically updated and installed when the vendor makes firmware
available, right in the middle of a movie?

o  would you be happy that your (eventual) Internet attached ECU's
firmware is automatically updated and installed when the car vendor
makes firmware available, right at the moment when you're travelling at
100Kph/60Mph?

o  would you be happy that your Internet attached plane's firmware is
automatically updated and installed when the plane vendor makes
firmware available, right at the moment you're a passenger in it at it,
and it is in the middle of taking off?

In each of these cases, the operator of the device has to be in control
of when these firmware upgrades occur as they can make the best
operational choice as to when they should occur. Device vendors
usually aren't also operators. For ISP managed CPE, the ISP is
the operator. For privately purchased CPE, the customer has chosen to
take on the responsibility of being the device's operator and is
therefore responsible for it's maintenance - if they don't want to be an
operator, they need to be prepared to engage somebody else to
perform that function. 

I certainly understand the issue of CPE firmware not being upgraded
regularly. However I think that may be more of a human-computer
interface issue. It isn't easy enough for non-technical people to do -
methods such as a flashing LED, persistent beeper and a upgrade
firmware button might be far more successful. But automated updates that
are distributed and installed without notice or control by ISPs or the
end-CPE owners won't solve the problem without causing possibly bigger
ones.

Regards,
Mark.

> Now, assume that I purchase an "unmanaged service". The ISP provides IPv6 connectivity and I go to Crazy Eddy's Electronics World to purchase an Acme-100 router, running ACME-OS Version 1.1. A few months later, the Acme corporation discovers a bug in their implementation of feature X. So they release ACME-OS Version 1.2. While version 1.2 corrects the bug in feature X, it introduces another bug in feature Y.
> 
> In this case, the user knows best whether he wants to upgrade to version 1.2. Users who rely on feature X will want to upgrade, while users who do not rely on feature X will not be so motivated. In this case, the model that Mark suggests makes most sense.
> 
> Acme corporation wants to sell their gear into both managed and unmanaged environments. So, we need to find some middle ground. I would suggest a configuration switch between the two modes proposed above. Since the vast majority of residential users have no idea what their routers are doing, I would suggest Jari's mode as default.
> 
>                                                                      Ron
> 
> 
> 
> 
> 
> > -----Original Message-----
> > From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
> > Of Joel Jaeggli
> > Sent: Thursday, October 14, 2010 10:35 PM
> > To: Fred Baker
> > Cc: IPv6 Operations; iesg@ietf.org
> > Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-
> > security-15.txt
> > 
> > On 10/14/10 1:09 PM, Fred Baker wrote:
> > >
> > > On Oct 14, 2010, at 12:46 PM, james woodyatt wrote:
> > >
> > >> It seems like Mr. Smith and Mr. Arkko are in disagreement about
> > >> whether software updates should be downloaded and applied
> > >> automatically, and I don't know how to proceed from here.
> > >
> > > Jari, being on the IESG, is copied in this. I would suggest that he,
> > > Mark, and Barbara argue their relative cases. At the end of the day,
> > > the reason that I asked for a final discussion is that there have
> > > been several changes, and the document has to satisfy not only it's
> > > last reviewer, but the operational community that is recommending
> > > it.
> > >
> > > the status as I see it is:
> > >
> > > - Jari wants the patches applied automatically, which assures patch
> > > updates but removes a level of control from the owner/operator of the
> > > device
> > >
> > > - Mark wants the patches pushed out but applied with the
> > > owner/operator's consent
> > >
> > > - Barbara wants the owner/operator to have an interface that can
> > > apply a patch, but leave anything else undefined; this basically
> > > preserves the status quo, which means that residential gateways are
> > > likely to generally *not* track patches and as a result have security
> > > vulnerabilities, which is also the status quo.
> > >
> > > A middle ground, perhaps, would be to recommend that the manufacturer
> > > provide an option that the user can select; the present language's
> > > "by default" suggests this as well. The options would be for the
> > > device to periodically access a manufacturer web site and download
> > > updated firmware or for the manufacturer to somehow (blast email?)
> > > advise the registered owner to do so at their convenience. The issue
> > > for this draft would be "what is the default", as that will be the
> > > most common actual behavior.
> > 
> > This seems a lot alike an implementation detail, if a device does not
> > update itself automatically then the acceptance of updates by end users
> > is going to be terribly low, if it does, they might approach 100%. I
> > can
> > observe in another business that voluntary software updates on mobile
> > phones (speaking my own employer) have a rather low uptake rate (like
> > under 10%) ota updates for carrier supported devices on the the other
> > hand may approach 100%.
> > 
> > so if you actually want the devices to be up-datable in order to
> > address
> > problems in the field they really do need to do so autonomously, there
> > no way around that.
> > 
> > Still for a device procured by a consumer it should be between them and
> > their vendor as to whether this happens.
> > 
> > For the record I think the text for rec-13 is sufficiently strong that
> > people with a good reason to do so will ignore it and as a general case
> > recommendation it is fine.
> > 
> > > _______________________________________________ v6ops mailing list
> > > v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
> > >
> > 
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

From drc@virtualized.org  Fri Oct 15 14:48:23 2010
Return-Path: <drc@virtualized.org>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CBC423A6BC7; Fri, 15 Oct 2010 14:48:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level: 
X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lUOwPHDugoEz; Fri, 15 Oct 2010 14:48:23 -0700 (PDT)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190]) by core3.amsl.com (Postfix) with ESMTP id ECD963A6BC6; Fri, 15 Oct 2010 14:48:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by virtualized.org (Postfix) with ESMTP id 4DD39EB7896; Fri, 15 Oct 2010 14:49:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at virtualized.org
Received: from virtualized.org ([127.0.0.1]) by localhost (trantor.virtualized.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mqml2gFqTq0B; Fri, 15 Oct 2010 14:49:43 -0700 (PDT)
Received: from [10.0.1.7] (cpe-70-95-123-210.hawaii.res.rr.com [70.95.123.210]) by virtualized.org (Postfix) with ESMTP id 29BDDEB7885; Fri, 15 Oct 2010 14:49:43 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: David Conrad <drc@virtualized.org>
In-Reply-To: <C8DE4146.3F2AA%yiu_lee@cable.comcast.com>
Date: Fri, 15 Oct 2010 11:49:41 -1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <A5625C1A-1A3E-4507-ADFC-09174346DFE1@virtualized.org>
References: <C8DE4146.3F2AA%yiu_lee@cable.comcast.com>
To: "Yiu L. Lee" <yiu_lee@cable.comcast.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>, iesg@ietf.org
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 21:48:23 -0000

On Oct 15, 2010, at 11:35 AM, Yiu L. Lee wrote:
>> With that in mind, I'd prefer that there be a recommendation that =
automatic
>> updates be enabled by default with a mechanism to allow users to =
disable those
>> updates if they so desire.
> I think this is the linux, Windows and MacOSX approach.

Just to be clear, I believe all of these require manual intervention. =
I'm arguing against this. If a device requires manual intervention, I'd =
argue that people won't bother and we'll end up with broken, vulnerable =
CPEs as we do today, just a whole lot more of them.

(Note that this assumes vendors will actually update their boxes instead =
of through inaction  encouraging people to go out and buy new ones)

> I think this is
> acceptable to turn on the automatic update by default and let users to
> disable it if they decide to.

Ideally, during installation/initial configuration the user could be =
presented with the option of disabling unattended automatic update =
(since I figure installation/initial configuration is typically the only =
time most users log into the box).

Regards,
-drc


From shemant@cisco.com  Fri Oct 15 14:51:11 2010
Return-Path: <shemant@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E0D313A6BC4; Fri, 15 Oct 2010 14:51:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.458
X-Spam-Level: 
X-Spam-Status: No, score=-10.458 tagged_above=-999 required=5 tests=[AWL=0.141, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ySY18gdHIarg; Fri, 15 Oct 2010 14:51:10 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 3C0D03A68E0; Fri, 15 Oct 2010 14:51:10 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAOFpuEytJV2Z/2dsb2JhbAChMHGkY5xHhUkEhFSJAA
X-IronPort-AV: E=Sophos;i="4.57,338,1283731200"; d="scan'208";a="171261924"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rtp-iport-2.cisco.com with ESMTP; 15 Oct 2010 21:52:31 +0000
Received: from xbh-rcd-302.cisco.com (xbh-rcd-302.cisco.com [72.163.63.9]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id o9FLqUxo015669;  Fri, 15 Oct 2010 21:52:30 GMT
Received: from xmb-rcd-114.cisco.com ([72.163.62.156]) by xbh-rcd-302.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 15 Oct 2010 16:52:31 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 15 Oct 2010 16:52:30 -0500
Message-ID: <AF742F21C1FCEE4DAB7F4842ABDC511C02F72EFE@XMB-RCD-114.cisco.com>
In-Reply-To: <C8DE4146.3F2AA%yiu_lee@cable.comcast.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
Thread-Index: ActssNL8yV8XgZ2ymEW8L6IkBg8SoAAAbniw
References: <65A20F28-24CD-48FF-8852-97DCDD2AFCF7@virtualized.org> <C8DE4146.3F2AA%yiu_lee@cable.comcast.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Yiu L. Lee" <yiu_lee@cable.comcast.com>, "David Conrad" <drc@virtualized.org>
X-OriginalArrivalTime: 15 Oct 2010 21:52:31.0216 (UTC) FILETIME=[445E2F00:01CB6CB3]
Cc: IPv6 Operations <v6ops@ietf.org>, iesg@ietf.org
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 21:51:12 -0000

-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
Of Yiu L. Lee
Sent: Friday, October 15, 2010 5:35 PM
To: David Conrad
Cc: IPv6 Operations; iesg@ietf.org
Subject: Re: [v6ops] Fwd: I-D
Action:draft-ietf-v6ops-cpe-simple-security-15.txt


>> With that in mind, I'd prefer that there be a recommendation that
automatic
>> updates be enabled by default with a mechanism to allow users to
disable those
>> updates if they so desire.
>>=20
>I think this is the linux, Windows and MacOSX approach. I think this is
>acceptable to turn on the automatic update by default and let users to
>disable it if they decide to.

Users of machines that run Windows, Linux, or MaxOS are generally more
aware of the security updates because the machines tell them so - these
are PCs used by folks with a nice GUI etc.  The home gateway is a
consumer device that a customer is not logged on for several hours a day
like working on their PCs.  Thus auto upgrade default of On for the home
router is debatable.

Hemant

From drc@virtualized.org  Fri Oct 15 15:15:11 2010
Return-Path: <drc@virtualized.org>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A6D163A6ADF; Fri, 15 Oct 2010 15:15:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.781
X-Spam-Level: 
X-Spam-Status: No, score=-2.781 tagged_above=-999 required=5 tests=[AWL=-0.182, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AZqIOgJHxaY7; Fri, 15 Oct 2010 15:15:10 -0700 (PDT)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190]) by core3.amsl.com (Postfix) with ESMTP id A00793A6AC4; Fri, 15 Oct 2010 15:15:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by virtualized.org (Postfix) with ESMTP id DAE85EB7BD5; Fri, 15 Oct 2010 15:16:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at virtualized.org
Received: from virtualized.org ([127.0.0.1]) by localhost (trantor.virtualized.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J-RCWEbgrcTN; Fri, 15 Oct 2010 15:16:29 -0700 (PDT)
Received: from [10.0.1.7] (cpe-70-95-123-210.hawaii.res.rr.com [70.95.123.210]) by virtualized.org (Postfix) with ESMTP id 2A869EB7BC6; Fri, 15 Oct 2010 15:16:29 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: David Conrad <drc@virtualized.org>
In-Reply-To: <20101016081811.1fcb82e5@opy.nosense.org>
Date: Fri, 15 Oct 2010 12:16:26 -1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <1055404F-D06A-4E8F-AA8D-3E62119F996C@virtualized.org>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com> <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com> <20101014205109.75a23d68@opy.nosense.org> <DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com> <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com> <4CB7BDCD.4000207@bogus.com> <13205C286662DE4387D9AF3AC30EF456B020F14DDF@EMBX01-WF.jnpr.net> <20101016081811.1fcb82e5@opy.nosense.org>
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Mailer: Apple Mail (2.1081)
Cc: Operations <v6ops@ietf.org>, iesg@ietf.org, IPv6@core3.amsl.com
Subject: Re: [v6ops] Fwd:	I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 22:15:11 -0000

Mark,

On Oct 15, 2010, at 11:48 AM, Mark Smith wrote:
> So it won't be possible for the ISP to provide a
> managed CPE service, because they don't control and can't be in =
control
> of when the firmware is released to the CPE customers.

I'd think that recommending having an option that disables unattended =
automatic update would address this concern.  Managed service providers, =
since they'd be controlling the CPE, could go in and disable unattended =
automatic updates (if they so desire).

> If the draft is going to persist with specifying that firmware is
> automatically distributed and installed, then it is also going to have
> to specify mechanisms as to how ISPs are going to put inline with this
> process, between the vendor and the CPE, so they're going to be able =
to
> prevent automatic upgrades occurring at times when it is inconvenient =
to
> customers.

Not really.

> o  would you be happy that your Internet attached TV's firmware is

Sort of like my TiVo updating itself?

> o  would you be happy that your (eventual) Internet attached ECU's
[...]
> o  would you be happy that your Internet attached plane's firmware is

Presumably, vendors would figure out how to do upgrades with minimal =
risk if the decided to follow the IETF recommendations, e.g., the ECU =
can easily tell when the car isn't running (or even occupied) and a =
plane's systems can easily determine whether the engines are running (or =
whatever). Posing reductio ad absurdum scenarios probably isn't really =
helping the discussion.

> I certainly understand the issue of CPE firmware not being upgraded
> regularly.

According to recent data out of DNS-OARC, there are between 160,000 and =
320,000 name servers on the Internet still running BIND version 4 -- a =
name server that has been deprecated by ISC now for almost a decade.

People generally do not interact with CPE devices outside of perhaps =
initial installation/configuration.  They might cycle the power once in =
a while, but otherwise it is a black box.  These unattended devices have =
proven to be a target for various forms of attacks. I believe we should =
learn from past (and current) experiences and make recommendations that =
address those experiences.  Assuming that folks are going to become more =
conscientious about installing updates hasn't really worked in the past, =
I'm unsure why it will work in the future.

Regards,
-drc


From brian.e.carpenter@gmail.com  Fri Oct 15 15:39:31 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5368E3A6B0A; Fri, 15 Oct 2010 15:39:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.095
X-Spam-Level: 
X-Spam-Status: No, score=-102.095 tagged_above=-999 required=5 tests=[AWL=-0.096, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MT64yT7yf-A5; Fri, 15 Oct 2010 15:39:31 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id E3B963A6AD7; Fri, 15 Oct 2010 15:39:26 -0700 (PDT)
Received: by qyk36 with SMTP id 36so1424594qyk.10 for <multiple recipients>; Fri, 15 Oct 2010 15:40:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=KROMz18wfEut8Yc9Q+xtRGyspZmCOwPqge0RL+4HHtQ=; b=VPkFZ9BIeMMmxQASvJn7CrCO4dATM4+IaUuCFR9cUn5PQhZXiB1xkPL3LkwWQR7omi aQ0TFv7fu+lhmT6x2/pv4hr8nmKw4PlTYkUHc0c973VtVR0vScwJHuWZtSCBC7eguutA cABaX3vMqdRbsj3Se7Ngu7FfoA/YXSeUpXhiw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=mhZq1YkTIX1zt9A2+BDFXpLbhpZ3/h5Ps23Wjx1DR7DADWPU19o+Ns8mjfX6Fl1X+P BUp/U1A7+ptPfFvCx9M3pHipG4bMW6yuL7KP8ONy6VmQpjkLu4vV0B+7IUROmqPWysRG OzqiyRqprJtjL1sUE4I5ZslkwspkDbaNiuMck=
Received: by 10.229.233.195 with SMTP id jz3mr1236603qcb.207.1287182436727; Fri, 15 Oct 2010 15:40:36 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.142.15]) by mx.google.com with ESMTPS id l13sm11362142qck.19.2010.10.15.15.40.32 (version=SSLv3 cipher=RC4-MD5); Fri, 15 Oct 2010 15:40:35 -0700 (PDT)
Message-ID: <4CB8D855.4080902@gmail.com>
Date: Sat, 16 Oct 2010 11:40:21 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: David Conrad <drc@virtualized.org>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com>	<ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com>	<20101014205109.75a23d68@opy.nosense.org>	<DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com>	<BE0267C0-302D-48CB-A167-F300B0170922@cisco.com>	<4CB7BDCD.4000207@bogus.com>	<13205C286662DE4387D9AF3AC30EF456B020F14DDF@EMBX01-WF.jnpr.net>	<20101016081811.1fcb82e5@opy.nosense.org> <1055404F-D06A-4E8F-AA8D-3E62119F996C@virtualized.org>
In-Reply-To: <1055404F-D06A-4E8F-AA8D-3E62119F996C@virtualized.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Operations <v6ops@ietf.org>, iesg@ietf.org, IPv6@core3.amsl.com
Subject: Re: [v6ops] Fwd:	I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 22:39:31 -0000

On 2010-10-16 11:16, David Conrad wrote:
> Mark,
> 
> On Oct 15, 2010, at 11:48 AM, Mark Smith wrote:
>> So it won't be possible for the ISP to provide a
>> managed CPE service, because they don't control and can't be in control
>> of when the firmware is released to the CPE customers.
> 
> I'd think that recommending having an option that disables unattended automatic update would address this concern.  Managed service providers, since they'd be controlling the CPE, could go in and disable unattended automatic updates (if they so desire).

I think the discussion has shown that we (the IETF) don't have consensus
and that legal and commercial requirements will vary enormously in the
real world. To me there's only one possible conclusion: the IETF can't
"legislate" on this. So again here is my suggestion:

REC-13:
Residential Internet Gateways SHOULD provide a convenient means to
securely update their firmware, for the installation of security patches
and other manufacturer-recommended changes.

    Brian

>> If the draft is going to persist with specifying that firmware is
>> automatically distributed and installed, then it is also going to have
>> to specify mechanisms as to how ISPs are going to put inline with this
>> process, between the vendor and the CPE, so they're going to be able to
>> prevent automatic upgrades occurring at times when it is inconvenient to
>> customers.
> 
> Not really.
> 
>> o  would you be happy that your Internet attached TV's firmware is
> 
> Sort of like my TiVo updating itself?
> 
>> o  would you be happy that your (eventual) Internet attached ECU's
> [...]
>> o  would you be happy that your Internet attached plane's firmware is
> 
> Presumably, vendors would figure out how to do upgrades with minimal risk if the decided to follow the IETF recommendations, e.g., the ECU can easily tell when the car isn't running (or even occupied) and a plane's systems can easily determine whether the engines are running (or whatever). Posing reductio ad absurdum scenarios probably isn't really helping the discussion.
> 
>> I certainly understand the issue of CPE firmware not being upgraded
>> regularly.
> 
> According to recent data out of DNS-OARC, there are between 160,000 and 320,000 name servers on the Internet still running BIND version 4 -- a name server that has been deprecated by ISC now for almost a decade.
> 
> People generally do not interact with CPE devices outside of perhaps initial installation/configuration.  They might cycle the power once in a while, but otherwise it is a black box.  These unattended devices have proven to be a target for various forms of attacks. I believe we should learn from past (and current) experiences and make recommendations that address those experiences.  Assuming that folks are going to become more conscientious about installing updates hasn't really worked in the past, I'm unsure why it will work in the future.
> 
> Regards,
> -drc
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> 

From jhw@apple.com  Sat Oct 16 12:31:11 2010
Return-Path: <jhw@apple.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4FD5C3A69C4 for <v6ops@core3.amsl.com>; Sat, 16 Oct 2010 12:31:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.396
X-Spam-Level: 
X-Spam-Status: No, score=-106.396 tagged_above=-999 required=5 tests=[AWL=0.203, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id whFFODNDAoDm for <v6ops@core3.amsl.com>; Sat, 16 Oct 2010 12:31:10 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id 565E93A6A82 for <v6ops@ietf.org>; Sat, 16 Oct 2010 12:31:10 -0700 (PDT)
Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out4.apple.com (Postfix) with ESMTP id A1BDDB63FD98; Sat, 16 Oct 2010 12:32:34 -0700 (PDT)
X-AuditID: 11807137-b7bf7ae000000f05-d8-4cb9fdd1e24b
Received: from [17.151.102.89] (Unknown_Domain [17.151.102.89]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay16.apple.com (Apple SCV relay) with SMTP id 0E.91.03845.2DDF9BC4; Sat, 16 Oct 2010 12:32:34 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: james woodyatt <jhw@apple.com>
In-Reply-To: <4CB8C7D4.3090903@inex.ie>
Date: Sat, 16 Oct 2010 12:32:33 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <03D21E82-F62C-4731-9C08-83F93CD547C6@apple.com>
References: <C8DE3F19.3F2A3%yiu_lee@cable.comcast.com> <4CB8C7D4.3090903@inex.ie>
To: Nick Hilliard <nick@inex.ie>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Fwd: I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Oct 2010 19:31:11 -0000

On Oct 15, 2010, at 14:29, Nick Hilliard wrote:
> 
> This is becoming a bikeshed issue.

"What color is the bikeshed at Hereford?"

Wait.  I didn't get that movie reference at all right, did I?


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



From nick@inex.ie  Sat Oct 16 12:53:06 2010
Return-Path: <nick@inex.ie>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 461093A6A0E for <v6ops@core3.amsl.com>; Sat, 16 Oct 2010 12:53:06 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TIPjwY4ggUt0 for <v6ops@core3.amsl.com>; Sat, 16 Oct 2010 12:53:05 -0700 (PDT)
Received: from mail.acquirer.com (unknown [IPv6:2001:1bb8:2004:150::2]) by core3.amsl.com (Postfix) with ESMTP id 04D993A69A1 for <v6ops@ietf.org>; Sat, 16 Oct 2010 12:53:04 -0700 (PDT)
X-Envelope-To: v6ops@ietf.org
Received: from crumpet.foobar.org (crumpet.foobar.org [10.230.100.249]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.3) with ESMTP id o9GJsD8P070309 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 16 Oct 2010 20:54:19 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <4CBA02E5.4000308@inex.ie>
Date: Sat, 16 Oct 2010 20:54:13 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.1.12) Gecko/20100914 Thunderbird/3.0.8
MIME-Version: 1.0
To: james woodyatt <jhw@apple.com>
References: <C8DE3F19.3F2A3%yiu_lee@cable.comcast.com> <4CB8C7D4.3090903@inex.ie> <03D21E82-F62C-4731-9C08-83F93CD547C6@apple.com>
In-Reply-To: <03D21E82-F62C-4731-9C08-83F93CD547C6@apple.com>
X-Enigmail-Version: 1.0.1
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Fwd: I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Oct 2010 19:53:06 -0000

On 16/10/2010 20:32, james woodyatt wrote:
> On Oct 15, 2010, at 14:29, Nick Hilliard wrote:
>>
>> This is becoming a bikeshed issue.
> 
> "What color is the bikeshed at Hereford?"
> 
> Wait.  I didn't get that movie reference at all right, did I?

http://www.bikeshed.com/

Just in case there's any doubt, the only acceptable version of this web
site is http://mediumaquamarine.bikeshed.com/.  All other colours are
objectively wrong and choosing them would display very bad judgement.

In my humble opinion, that is.

Nick

From scott.brim@gmail.com  Sat Oct 16 13:49:00 2010
Return-Path: <scott.brim@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E78AD3A6ADA for <v6ops@core3.amsl.com>; Sat, 16 Oct 2010 13:49:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level: 
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2fy+3PkzR2KX for <v6ops@core3.amsl.com>; Sat, 16 Oct 2010 13:49:00 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id D70143A69A1 for <v6ops@ietf.org>; Sat, 16 Oct 2010 13:48:59 -0700 (PDT)
Received: by qwc9 with SMTP id 9so1186468qwc.31 for <v6ops@ietf.org>; Sat, 16 Oct 2010 13:50:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=al3e4d1KbnBAC7W/vNnx+eBZ8YA8p4vVGSt8uUm3kmk=; b=qu5KiLBrrIZGOO17JiCJjNdo/tESLEdNb68sFlZJ3JeXJsVm0ouXhGgBLBPIvefM4B 0ou+DpqzCBZK0maoRBh97Mv7Xs6osymv7c5pP6EMamKtu0OOJgs7VYnhn1VY95k1stJ0 WwiPA4xGhQ1RWwZvcZq68UOFSp0pnUHKkKQDM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=ev/ejruk0YD2iKrqL4VnNsJ7rTy03+AJ/8zSsxOfz71aZPrYhR51wbDwdTe+juchYp EzcuV/xiJYuSR69kFE5PvTJ+6iZ5cJVMfWWCCjK4UqenhJU8Ui1thPPloVxcX+/7wdNT qllrPI2rwhuv7rBLo2YtdLjO29fsN5PAMVMfk=
Received: by 10.229.231.7 with SMTP id jo7mr2149741qcb.254.1287262222313; Sat, 16 Oct 2010 13:50:22 -0700 (PDT)
Received: from sbrim-mbp.local (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id mz11sm9967622qcb.15.2010.10.16.13.50.20 (version=SSLv3 cipher=RC4-MD5); Sat, 16 Oct 2010 13:50:20 -0700 (PDT)
Message-ID: <4CBA100A.9080801@gmail.com>
Date: Sat, 16 Oct 2010 16:50:18 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: Nick Hilliard <nick@inex.ie>
References: <C8DE3F19.3F2A3%yiu_lee@cable.comcast.com>	<4CB8C7D4.3090903@inex.ie>	<03D21E82-F62C-4731-9C08-83F93CD547C6@apple.com> <4CBA02E5.4000308@inex.ie>
In-Reply-To: <4CBA02E5.4000308@inex.ie>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Fwd: I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Oct 2010 20:49:01 -0000

On 10/16/2010 15:54 EDT, Nick Hilliard wrote:
> On 16/10/2010 20:32, james woodyatt wrote:
>> On Oct 15, 2010, at 14:29, Nick Hilliard wrote:
>>>
>>> This is becoming a bikeshed issue.
>>
>> "What color is the bikeshed at Hereford?"
>>
>> Wait.  I didn't get that movie reference at all right, did I?
> 
> http://www.bikeshed.com/
> 
> Just in case there's any doubt, the only acceptable version of this web
> site is http://mediumaquamarine.bikeshed.com/.  All other colours are
> objectively wrong and choosing them would display very bad judgement.
> 
> In my humble opinion, that is.
> 
> Nick

http://en.wikipedia.org/wiki/Parkinson%27s_Law_of_Triviality

Also, allegedly, Henry Kissinger said about Harvard faculty meetings
that "the fighting is so bitter because the stakes are so small."


From fred@cisco.com  Sat Oct 16 22:15:43 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA9BD3A6956 for <v6ops@core3.amsl.com>; Sat, 16 Oct 2010 22:15:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.153
X-Spam-Level: 
X-Spam-Status: No, score=-110.153 tagged_above=-999 required=5 tests=[AWL=0.446, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4UDZ-qxxagsb for <v6ops@core3.amsl.com>; Sat, 16 Oct 2010 22:15:24 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id E63393A6A8E for <v6ops@ietf.org>; Sat, 16 Oct 2010 22:15:14 -0700 (PDT)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAG8jukyrRN+K/2dsb2JhbAChK3GnHJs1hUkEhFSFdoMF
X-IronPort-AV: E=Sophos;i="4.57,342,1283731200"; d="scan'208";a="605212304"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-6.cisco.com with ESMTP; 17 Oct 2010 05:16:32 +0000
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o9H5GP0A005314 for <v6ops@ietf.org>; Sun, 17 Oct 2010 05:16:27 GMT
Received: from [127.0.0.1] by stealth-10-32-244-219.cisco.com (PGP Universal service); Sat, 16 Oct 2010 22:16:32 -0700
X-PGP-Universal: processed; by stealth-10-32-244-219.cisco.com on Sat, 16 Oct 2010 22:16:32 -0700
From: Fred Baker <fred@cisco.com>
Date: Sat, 16 Oct 2010 22:16:18 -0700
Message-Id: <10696153-0E3C-45D5-B531-8C5DD7930E91@cisco.com>
To: IPv6 Operations <v6ops@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: [v6ops] IETF 79 Agenda
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: V6ops Chairs <v6ops-chairs@tools.ietf.org>
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Oct 2010 05:15:44 -0000

The meeting agenda is posted at =
http://www.ietf.org/proceedings/79/agenda/v6ops.html

If I have missed anything or folks want to agenda-bash, please let us =
know.=

From fred@cisco.com  Sun Oct 17 11:01:57 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 43D413A6A9F for <v6ops@core3.amsl.com>; Sun, 17 Oct 2010 11:01:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.27
X-Spam-Level: 
X-Spam-Status: No, score=-110.27 tagged_above=-999 required=5 tests=[AWL=0.328, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5K68lWgHRlHc for <v6ops@core3.amsl.com>; Sun, 17 Oct 2010 11:01:56 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 06F2D3A6BA7 for <v6ops@ietf.org>; Sun, 17 Oct 2010 11:01:56 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjIHAG/XukyrR7Hu/2dsb2JhbACBRZFshWoBiA9xp0ybS4VJBIRUhXaDBQ
X-IronPort-AV: E=Sophos;i="4.57,342,1283731200";  d="scan'208,217";a="202114607"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 17 Oct 2010 18:00:24 +0000
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o9HI09RX012473 for <v6ops@ietf.org>; Sun, 17 Oct 2010 18:00:17 GMT
Received: from [127.0.0.1] by stealth-10-32-244-219.cisco.com (PGP Universal service); Sun, 17 Oct 2010 11:00:24 -0700
X-PGP-Universal: processed; by stealth-10-32-244-219.cisco.com on Sun, 17 Oct 2010 11:00:24 -0700
From: Fred Baker <fred@cisco.com>
Date: Sun, 17 Oct 2010 11:00:04 -0700
Message-Id: <F0A138C4-70DB-4D32-9B95-EC3193406B9C@cisco.com>
To: IPv6 Operations <v6ops@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Content-Type: multipart/alternative; boundary=Apple-Mail-18--206441160
Subject: [v6ops] Fwd: draft-ietf-v6ops-v6-in-mobile-networks WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Oct 2010 18:01:57 -0000

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



Begin forwarded message:

From: Fred Baker <fred@cisco.com>
Date: October 10, 2010 11:00:08 AM PDT
To: IPv6 Operations <v6ops@ietf.org>
Cc: v6ops-chairs@tools.ietf.org, Ron Bonica <ron@bonica.org>
Subject: draft-ietf-v6ops-v6-in-mobile-networks WGLC

This is to initiate a two week working group last call of =
draft-ietf-v6ops-v6-in-mobile-networks. Please read it now. If you find =
nits (spelling errors, minor suggested wording changes, etc), comment to =
the authors; if you find greater issues, such as disagreeing with a =
statement or finding additional issues that need to be addressed, please =
post your comments to the list.

We are looking specifically for comments on the importance of the =
document as well as its content. If you have read the document and =
believe it to be of operational utility, that is also an important =
comment to make.


We have had a number of topics on the list recently, and I want to make =
sure that this one is not lost in the noise. The WGLC on this document =
will continue for the coming week, and we invite your comments.

http://datatracker.ietf.org/doc/draft-ietf-v6ops-v6-in-mobile-networks
http://tools.ietf.org/html/draft-ietf-v6ops-v6-in-mobile-networks
  "Mobile Networks Considerations for IPv6 Deployment", Rajeev Koodli,
  12-Jul-10=

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

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal =
normal normal 12px/normal Helvetica; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"3" style=3D"font: =
12.0px Helvetica">Begin forwarded message:</font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font =
face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px =
Helvetica">From:&nbsp;Fred Baker &lt;<a =
href=3D"mailto:fred@cisco.com">fred@cisco.com</a>&gt;</font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"3" style=3D"font: =
12.0px Helvetica">Date:&nbsp;October 10, 2010 11:00:08 AM =
PDT</font></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><font face=3D"Helvetica" =
size=3D"3" style=3D"font: 12.0px Helvetica">To:&nbsp;IPv6 Operations =
&lt;<a =
href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a>&gt;</font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"3" style=3D"font: =
12.0px Helvetica">Cc:&nbsp;<a =
href=3D"mailto:v6ops-chairs@tools.ietf.org">v6ops-chairs@tools.ietf.org</a=
>, Ron Bonica &lt;<a =
href=3D"mailto:ron@bonica.org">ron@bonica.org</a>&gt;</font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"3" style=3D"font: =
12.0px Helvetica">Subject:&nbsp;draft-ietf-v6ops-v6-in-mobile-networks =
WGLC</font></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
12px/normal Helvetica; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"3" style=3D"font: =
12.0px Helvetica">This is to initiate a two week working group last call =
of draft-ietf-v6ops-v6-in-mobile-networks. Please read it now. If you =
find nits (spelling errors, minor suggested wording changes, etc), =
comment to&nbsp;the authors; if you find greater issues, such as =
disagreeing with a statement or finding additional issues that need to =
be addressed, please post your comments to the list.</font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font =
face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px Helvetica">We are =
looking specifically for comments on the importance of the document as =
well as its content. If you have read the document and believe it to be =
of operational utility, that is also an important&nbsp;comment to =
make.</font></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
12px/normal Helvetica; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; font: normal normal normal 12px/normal Helvetica; =
min-height: 14px; "><br></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font =
face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px Helvetica">We have =
had a number of topics on the list recently, and I want to make sure =
that this one is not lost in the noise. The WGLC on this document will =
continue for the coming week, and we invite your =
comments.</font></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; font: normal normal normal =
12px/normal Helvetica; min-height: 14px; "><br></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"3" style=3D"font: =
12.0px Helvetica"><a =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-v6ops-v6-in-mobile-netw=
orks">http://datatracker.ietf.org/doc/draft-ietf-v6ops-v6-in-mobile-networ=
ks</a></font></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><font face=3D"Helvetica" =
size=3D"3" style=3D"font: 12.0px Helvetica"><a =
href=3D"http://tools.ietf.org/html/draft-ietf-v6ops-v6-in-mobile-networks"=
>http://tools.ietf.org/html/draft-ietf-v6ops-v6-in-mobile-networks</a></fo=
nt></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><font face=3D"Helvetica" =
size=3D"3" style=3D"font: 12.0px Helvetica">&nbsp;&nbsp;"Mobile Networks =
Considerations for IPv6 Deployment", Rajeev Koodli,</font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"3" style=3D"font: =
12.0px Helvetica">&nbsp;&nbsp;12-Jul-10</font></div> =
</div></body></html>=

--Apple-Mail-18--206441160--

From sam.silvester@gmail.com  Sun Oct 17 18:16:06 2010
Return-Path: <sam.silvester@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AEC1A3A6C49; Sun, 17 Oct 2010 18:16:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oO3NA4m1xN+0; Sun, 17 Oct 2010 18:16:03 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id 84B693A6C48; Sun, 17 Oct 2010 18:16:03 -0700 (PDT)
Received: by qyk8 with SMTP id 8so3649395qyk.10 for <multiple recipients>; Sun, 17 Oct 2010 18:17:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=1nEu4pJJB03rEbsrbPqKSEXXu0d3WwkF2MPYC/fHwI0=; b=XGVPtMTu8wM5FFLrr6PUzJ8hIG3JHpwmlPSeLcPVMRHSvU67E9JYZFu4s7pOBIXd/G YM0mkXrTMTMhlqXjEZHmKrkL7S2+xoWe1hd2agSm9hMHuGL9w6yShYNWk5CXsWm/pnXn yxvqQK4KzG4ZBgk/NhmgOXKknsgOm5Zf2FGGA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=I4eke3ZaTEqMSQGtvYphRmju4Mg5++d/QB4TWvjB8/qwZg5nI+P5WWAcEVTwKoxMpn DtqOeHHgtGQe4VnstXVuMgzMH9iS3oWAFDTYpLQoB0x4urGuC1bYj2LFOX+kOJRDu3R/ 4YPVLJkYLrSEiVyeqH4bj6lkOfWyF4KVJMcNk=
MIME-Version: 1.0
Received: by 10.229.217.83 with SMTP id hl19mr3295413qcb.15.1287364650522; Sun, 17 Oct 2010 18:17:30 -0700 (PDT)
Received: by 10.229.27.18 with HTTP; Sun, 17 Oct 2010 18:17:30 -0700 (PDT)
In-Reply-To: <3277F900-7DE4-4FFB-B469-D7360ACD04AD@apple.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com> <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com> <20101014205109.75a23d68@opy.nosense.org> <DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com> <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com> <3277F900-7DE4-4FFB-B469-D7360ACD04AD@apple.com>
Date: Mon, 18 Oct 2010 11:47:30 +1030
Message-ID: <AANLkTinJ55=Yp2KmS92g4maxn2eocgUSw9FutpQ+3F_M@mail.gmail.com>
From: Sam Silvester <sam.silvester@gmail.com>
To: IPv6 Operations <v6ops@ietf.org>, iesg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Oct 2010 01:16:06 -0000

On Fri, Oct 15, 2010 at 7:00 AM, james woodyatt <jhw@apple.com> wrote:
> On Oct 14, 2010, at 13:09 , Fred Baker wrote:
>>
>> The issue for this draft would be "what is the default", as that will be the most common actual behavior.

As an operator, I'd like to avoid vendor patches to be automatically
installed for the reasons noted here (mass rebooting, helpdesk calls,
potential for nasty bugs to be "mass installed by default" etc).

I don't mind the idea of mechanisms being switchable to do automatic
install or an appropriate interface provided to the operator to allow
for this to be enabled for managed services.

>
> I suggest tweaking the recommendation to say that an "easily configured administrative option" to download and apply updates automatically SHOULD be offered.

Whilst I don't offer a suggestion on the exact wording, I think it
would be good to recommend that devices have a mechanism for automatic
download - at least that way people are 'encouraged' or at least aware
without having to know to hunt around on the vendor's website for
updates.

I do wonder about the UI in terms of notifying users that some action
is required on their part when a new update is available for install.
It's probably an implementation detail however.

From joelja@bogus.com  Sun Oct 17 23:28:41 2010
Return-Path: <joelja@bogus.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CBD8B3A6874; Sun, 17 Oct 2010 23:28:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.068
X-Spam-Level: 
X-Spam-Status: No, score=-102.068 tagged_above=-999 required=5 tests=[AWL=-0.069, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cebt5TIL+COm; Sun, 17 Oct 2010 23:28:41 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 977B13A6A63; Sun, 17 Oct 2010 23:28:40 -0700 (PDT)
Received: from joelja-mac.lan (c-98-234-104-156.hsd1.ca.comcast.net [98.234.104.156]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id o9I6U58I089793 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 18 Oct 2010 06:30:05 GMT (envelope-from joelja@bogus.com)
Message-ID: <4CBBE96D.2010605@bogus.com>
Date: Sun, 17 Oct 2010 23:30:05 -0700
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: Sam Silvester <sam.silvester@gmail.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com>	<ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com>	<20101014205109.75a23d68@opy.nosense.org>	<DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com>	<BE0267C0-302D-48CB-A167-F300B0170922@cisco.com>	<3277F900-7DE4-4FFB-B469-D7360ACD04AD@apple.com> <AANLkTinJ55=Yp2KmS92g4maxn2eocgUSw9FutpQ+3F_M@mail.gmail.com>
In-Reply-To: <AANLkTinJ55=Yp2KmS92g4maxn2eocgUSw9FutpQ+3F_M@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Mon, 18 Oct 2010 06:30:06 +0000 (UTC)
Cc: IPv6 Operations <v6ops@ietf.org>, iesg@ietf.org
Subject: Re: [v6ops] Fwd: I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Oct 2010 06:28:41 -0000

On 10/17/10 6:17 PM, Sam Silvester wrote:
> On Fri, Oct 15, 2010 at 7:00 AM, james woodyatt <jhw@apple.com> wrote:
>> On Oct 14, 2010, at 13:09 , Fred Baker wrote:
>>>
>>> The issue for this draft would be "what is the default", as that will be the most common actual behavior.
> 
> As an operator, I'd like to avoid vendor patches to be automatically
> installed for the reasons noted here (mass rebooting, helpdesk calls,
> potential for nasty bugs to be "mass installed by default" etc).

An "automatic" process has some instigating condition, I imagine in for
example the docsis context this would be instigated by the operator, in
a cellular OMA/DM/FOTA context it's certainly instigated by the operator...

It strikes me as unlikely that we'll be able produce language that is
appropriate for every context, The general sense that a mechanism by
which automatic software updates can be applied should be provided
leaves leeway for application specific methods to be applied.

> I don't mind the idea of mechanisms being switchable to do automatic
> install or an appropriate interface provided to the operator to allow
> for this to be enabled for managed services.
> 
>>
>> I suggest tweaking the recommendation to say that an "easily configured administrative option" to download and apply updates automatically SHOULD be offered.
> 
> Whilst I don't offer a suggestion on the exact wording, I think it
> would be good to recommend that devices have a mechanism for automatic
> download - at least that way people are 'encouraged' or at least aware
> without having to know to hunt around on the vendor's website for
> updates.
> 
> I do wonder about the UI in terms of notifying users that some action
> is required on their part when a new update is available for install.
> It's probably an implementation detail however.
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> 


From remi.despres@free.fr  Mon Oct 18 01:08:08 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 962EA3A6CD3 for <v6ops@core3.amsl.com>; Mon, 18 Oct 2010 01:08:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.115
X-Spam-Level: 
X-Spam-Status: No, score=-0.115 tagged_above=-999 required=5 tests=[AWL=-0.766, BAYES_50=0.001, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Mx8U03fWpf7 for <v6ops@core3.amsl.com>; Mon, 18 Oct 2010 01:07:32 -0700 (PDT)
Received: from smtp22.services.sfr.fr (smtp22.services.sfr.fr [93.17.128.10]) by core3.amsl.com (Postfix) with ESMTP id 063453A6CDB for <v6ops@ietf.org>; Mon, 18 Oct 2010 01:07:07 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2204.sfr.fr (SMTP Server) with ESMTP id DC086700009B for <v6ops@ietf.org>; Mon, 18 Oct 2010 10:08:33 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2204.sfr.fr (SMTP Server) with ESMTP id A80427000090 for <v6ops@ietf.org>; Mon, 18 Oct 2010 10:08:33 +0200 (CEST)
X-SFR-UUID: 20101018080833688.A80427000090@msfrf2204.sfr.fr
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 18 Oct 2010 10:08:31 +0200
Message-Id: <EB11768B-0A00-4F25-B58F-84AC079EC419@free.fr>
To: v6ops v6ops <v6ops@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Subject: [v6ops] CPE simple security - Soft updates of unmanaged CPEs.
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Oct 2010 08:08:08 -0000

Hi, all,

1.
For information, in relation to the current discussion about =
draft-ietf-v6ops-cpe-simple-security-15, here is what Free.fr, of which =
I am a happy customer, has been doing for years:

By default, no software update is received.
The short user manual indicates that the last update can be received, at =
any time, by means of a "hard reboot".
A hard reboot consists in 4 consecutive power-off/power-on.=20
Some announcements by Free of new features come with the advice to do =
hard reboots to get them.

It would be wise IMHO that the draft would at least clearly permit this =
kind of behavior.

(This isn't the case with the current REC-13 "By DEFAULT, Internet =
gateways SHOULD, automatically download and install software updates for =
extending IPv6 simple security for support of future standard upper =
layer transports and extension headers.")=20

2.
The requirement that new protections for upper layers can be downloaded =
from time to time seems to me opposite to the notion of an IETF =
specified "simple security".

3.
Wouldn't the best approach be to just delete REC-13 and the preceding =
paragraph that (tentatively) justifies it?


Regards,
RD



From phdgang@gmail.com  Mon Oct 18 08:24:01 2010
Return-Path: <phdgang@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A5753A6CD2 for <v6ops@core3.amsl.com>; Mon, 18 Oct 2010 08:24: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=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QfeH-8dZnWDZ for <v6ops@core3.amsl.com>; Mon, 18 Oct 2010 08:24:00 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id AD2753A69F0 for <v6ops@ietf.org>; Mon, 18 Oct 2010 08:24:00 -0700 (PDT)
Received: by gxk8 with SMTP id 8so540673gxk.31 for <v6ops@ietf.org>; Mon, 18 Oct 2010 08:25:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=9JOpQ9qU5zBe/M6A1WnP65YRtEQ3d8UbjysTEOewe54=; b=nfQEHrqK33Qa8YzLU7GcWc9GEn1/CMOkbrA1m3EYRM97Klvd1bdC3sSUJbzlrJ++xo bN2qP8teT8fuXbtoaTT0HT2yxH0Q1x8N9y14mjykTsST5Cl4soW66YnB1iXJe4QjqZz3 abXIonUFzDnqRIYB0wvD06ETJz7qhjOaSM6Eg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=KViYtdpJQPu1aSRPZzuKZbmyDi30Nq5J0DvG0q1qTlRC3iUjnozkVOOQoj3D/E8L1f uKgwi3SJAeWgjP4kmj+5OFCnvwb8SFnYHz8S4ZtSh3lEfouZxA54hG86Ig9Rcw1Kis0d W7v2EGW2HrG5BZY3DF+faYZTjD6OnqhXiGzsc=
MIME-Version: 1.0
Received: by 10.90.84.16 with SMTP id h16mr2119185agb.82.1287415528844; Mon, 18 Oct 2010 08:25:28 -0700 (PDT)
Received: by 10.91.158.3 with HTTP; Mon, 18 Oct 2010 08:25:28 -0700 (PDT)
In-Reply-To: <20101018151033.1112B3A6DF8@core3.amsl.com>
References: <20101018151033.1112B3A6DF8@core3.amsl.com>
Date: Mon, 18 Oct 2010 23:25:28 +0800
Message-ID: <AANLkTinqgzz60Jjz35Y-evzQq5AiU553r4W67W4YA6r8@mail.gmail.com>
From: GangChen <phdgang@gmail.com>
To: v6ops@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [v6ops] [V6ops] New Version Notification for draft-chen-v6ops-nat64-cpe-00
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Oct 2010 15:24:01 -0000

Dear all,

Please kindly to check new proposed draft.
Comments are welcome.

Gang Chen


---------- Forwarded message ----------
From: IETF I-D Submission Tool <idsubmission@ietf.org>
Date: Mon, 18 Oct 2010 08:10:33 -0700 (PDT)
Subject: New Version Notification for draft-chen-v6ops-nat64-cpe-00
To: phdgang@gmail.com
Cc: denghui02@gmail.com


A new version of I-D, draft-chen-v6ops-nat64-cpe-00.txt has been
successfully submitted by Gang Chen and posted to the IETF repository.

Filename:	 draft-chen-v6ops-nat64-cpe
Revision:	 00
Title:		 NAT64-CPE Mode Operation for Opening Residential Service
Creation_date:	 2010-10-18
WG ID:		 Independent Submission
Number_of_pages: 7

Abstract:
The document has proposed an approach of NAT64-CPE mode, which would
give residential service opportunities to be accessed by remote
subscribers going through IPv6 networks.  The document captures the
fundamental NAT64 functionalities with special cares to fit into CPE
scenarios and don't need cooperate with DNS64 any more.  It will
compatible with legacy residential servers and no further updates
requirements to DNS.



The IETF Secretariat.

From sam.silvester@gmail.com  Tue Oct 19 03:02:03 2010
Return-Path: <sam.silvester@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 418073A6783; Tue, 19 Oct 2010 03:02:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ldkgm4THJLjn; Tue, 19 Oct 2010 03:02:02 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 286F93A6782; Tue, 19 Oct 2010 03:02:02 -0700 (PDT)
Received: by qwc9 with SMTP id 9so1562134qwc.31 for <multiple recipients>; Tue, 19 Oct 2010 03:03:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=8qj3Ofz7Prde04Ocvu+zw8p/2RQgSgmBQA9s7vbMGYg=; b=RUABQnRMTXPOcZWutOJDXqDXyVS4tXmD8l2VFK2wBdTMxes1VaJxqB4IooRT+AC75f cOTZMPxmdn0j4LpikW01ZNwiyAWqsBD81MFljiuvPR5t0Lxe4L2UAgEMXgcFSiVRrlGI KfO7hfagGq3tTBm66LxGlziuTH40RbRRz1H6A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=WotAQeeNCwG/xgZpGCkp25nIJg769EqRA4fzlmnDrtDiMTgOXwbdhmYOy4kMNmdOzx Qy9MPGrB0YvjX5Qfqyw4xzZ3cjJp2z/W8gVbTpF92wH3qjOBGONH5G51NCLYaM7OCfMo JP/3LwfEHn1gr9L9tMDVqt9pjPQxS50pigBIY=
MIME-Version: 1.0
Received: by 10.229.248.135 with SMTP id mg7mr4965079qcb.160.1287482612320; Tue, 19 Oct 2010 03:03:32 -0700 (PDT)
Received: by 10.229.27.18 with HTTP; Tue, 19 Oct 2010 03:03:31 -0700 (PDT)
In-Reply-To: <4CBBE96D.2010605@bogus.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com> <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com> <20101014205109.75a23d68@opy.nosense.org> <DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com> <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com> <3277F900-7DE4-4FFB-B469-D7360ACD04AD@apple.com> <AANLkTinJ55=Yp2KmS92g4maxn2eocgUSw9FutpQ+3F_M@mail.gmail.com> <4CBBE96D.2010605@bogus.com>
Date: Tue, 19 Oct 2010 20:33:31 +1030
Message-ID: <AANLkTinshKeG6fjRDtM_zeVJ2bk21x=Jm7pyYEdYcztd@mail.gmail.com>
From: Sam Silvester <sam.silvester@gmail.com>
To: iesg@ietf.org, IPv6 Operations <v6ops@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2010 10:02:03 -0000

On Mon, Oct 18, 2010 at 5:00 PM, Joel Jaeggli <joelja@bogus.com> wrote:
> On 10/17/10 6:17 PM, Sam Silvester wrote:
>> As an operator, I'd like to avoid vendor patches to be automatically
>> installed for the reasons noted here (mass rebooting, helpdesk calls,
>> potential for nasty bugs to be "mass installed by default" etc).
>
> An "automatic" process has some instigating condition, I imagine in for
> example the docsis context this would be instigated by the operator, in
> a cellular OMA/DM/FOTA context it's certainly instigated by the operator...

I'm rather ok with the operator case (the company I work for has a mix
of products including some of which we manage CPE software upgrades
centrally). The one that I'm a little more concerned about is if the
CPE vendor themselves can instigate the upgrade - especially in the
case of residential CPE, there isn't much in the way of testing or
quality control often.

> It strikes me as unlikely that we'll be able produce language that is
> appropriate for every context, The general sense that a mechanism by
> which automatic software updates can be applied should be provided
> leaves leeway for application specific methods to be applied.

I agree broadly, although I do wonder a little if something can or
should to be said toward the previously mentioned "vendor instigated"
upgrade scenario.

Sam

From fred@cisco.com  Tue Oct 19 11:43:27 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 80AF23A68AC; Tue, 19 Oct 2010 11:43:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.296
X-Spam-Level: 
X-Spam-Status: No, score=-110.296 tagged_above=-999 required=5 tests=[AWL=0.303, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bGAdka2UxmRr; Tue, 19 Oct 2010 11:43:25 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 441DC3A68E1; Tue, 19 Oct 2010 11:43:25 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAAqEvUyrR7Ht/2dsb2JhbAChanGneJxFhUoEhFWFdoME
X-IronPort-AV: E=Sophos;i="4.57,351,1283731200"; d="scan'208";a="203273079"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-4.cisco.com with ESMTP; 19 Oct 2010 18:40:22 +0000
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o9JIeEpW013272; Tue, 19 Oct 2010 18:40:16 GMT
Received: from [127.0.0.1] by stealth-10-32-244-219.cisco.com (PGP Universal service); Tue, 19 Oct 2010 11:40:22 -0700
X-PGP-Universal: processed; by stealth-10-32-244-219.cisco.com on Tue, 19 Oct 2010 11:40:22 -0700
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4CB8D855.4080902@gmail.com>
Date: Tue, 19 Oct 2010 11:40:07 -0700
Message-Id: <FEF7DFB0-AA2B-47F6-9757-24D88C6FC39A@cisco.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com>	<ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com>	<20101014205109.75a23d68@opy.nosense.org>	<DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com>	<BE0267C0-302D-48CB-A167-F300B0170922@cisco.com>	<4CB7BDCD.4000207@bogus.com>	<13205C286662DE4387D9AF3AC30EF456B020F14DDF@EMBX01-WF.jnpr.net>	<20101016081811.1fcb82e5@opy.nosense.org> <1055404F-D06A-4E8F-AA8D-3E62119F996C@virtualized.org> <4CB8D855.4080902@gmail.com>
To: Operations <v6ops@ietf.org>, IESG IESG <iesg@ietf.org>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IPv6@core3.amsl.com
Subject: Re: [v6ops] Fwd:	I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2010 18:43:27 -0000

On Oct 15, 2010, at 3:40 PM, Brian E Carpenter wrote:

>> I'd think that recommending having an option that disables unattended =
automatic update would address this concern.  Managed service providers, =
since they'd be controlling the CPE, could go in and disable unattended =
automatic updates (if they so desire).
>=20
> I think the discussion has shown that we (the IETF) don't have =
consensus
> and that legal and commercial requirements will vary enormously in the
> real world. To me there's only one possible conclusion: the IETF can't
> "legislate" on this. So again here is my suggestion:
>=20
> REC-13:
> Residential Internet Gateways SHOULD provide a convenient means to
> securely update their firmware, for the installation of security =
patches
> and other manufacturer-recommended changes.

I have been following this discussion with a view to figuring out what =
recommendations SHOULD be made :-) A key concern I have here, as I said =
last week, is the difference between a residential gateway and a laptop; =
A laptop's owner at least knows whether an irritating icon is jumping up =
and down or has the opportunity to see a dialog box; I don't see that =
happening with the router in my equipment closet under the stairs.

It seems that we agree that there are at least two options that need =
support:
   - automated software update
   - manually initiated software update

One could go into other mechanisms such as having the user download the =
new image to a laptop and then TFTP it to a router. Some things are best =
left unsuggested, for fear that the vendor might say "hey, that's a =
great idea!".

In both cases, the update has to be initiated by the residential CPE, =
for scale and reliability, and if automated should be randomized in time =
for reasons discussed in RFC 3439. Having the ISP or the vendor manage a =
list of the IP addresses of deployed routers is (ahem) problematic.

In both cases, we need a way to specify the URL and certificate of the =
download site. I should imagine the vendor would preconfigure them, and =
an ISP running managed services could configure a different =
URL+certificate in routers it deploys. There is of course the question =
of what happens should the parameter memory get zapped; I would leave =
that to the vendor. There is also the question of how the device knows =
whether it has already downloaded the image; I for one would do that by =
having the URL change itself, so that the client system ca always get =
access to an older image as a recovery path and so it can tell whether =
the image it is requesting is in fact new.

In preceding recommendations, the format of the document is to state a =
recommendation and follow it with an explanatory note.=20

Which brings me to this suggestion:

/*
 * suggestion
 */
REC-13:
Residential Internet Gateways SHOULD provide a convenient means to =
securely update their firmware, for the installation of security patches =
and other manufacturer-recommended changes.

Vendors can expect users and operators to have differing viewpoints on =
the maintenance of patches, with some preferring automated update and =
some preferring manual initiation, and those preferring automated update =
wanting to download from a vendor site or one managed by the network =
operator. To handle the disparity, vendors are well advised if they =
provide manual and automated options. In the automated case, they would =
do well to facilitate pre-configuration of the download URL and a means =
of validating the software image such as a certificate.
/*
 * end of suggestion
 */

Opinions?=

From jhw@apple.com  Tue Oct 19 12:03:59 2010
Return-Path: <jhw@apple.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A51433A68EA for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 12:03:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.145
X-Spam-Level: 
X-Spam-Status: No, score=-106.145 tagged_above=-999 required=5 tests=[AWL=0.454, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gYIy-p2s9Bd2 for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 12:03:58 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id C8E1D3A68C7 for <v6ops@ietf.org>; Tue, 19 Oct 2010 12:03:58 -0700 (PDT)
Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out3.apple.com (Postfix) with ESMTP id 681D7B087015 for <v6ops@ietf.org>; Tue, 19 Oct 2010 12:05:30 -0700 (PDT)
X-AuditID: 11807134-b7c05ae000002d5d-8b-4cbdebfa1d95
Received: from elliott.apple.com (elliott.apple.com [17.151.62.13]) by relay14.apple.com (Apple SCV relay) with SMTP id DD.78.11613.AFBEDBC4; Tue, 19 Oct 2010 12:05:30 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from il0602f-dhcp196.apple.com (il0602f-dhcp196.apple.com [17.206.50.196]) by elliott.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LAJ00J16X15GU60@elliott.apple.com> for v6ops@ietf.org; Tue, 19 Oct 2010 12:05:30 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <FEF7DFB0-AA2B-47F6-9757-24D88C6FC39A@cisco.com>
Date: Tue, 19 Oct 2010 12:05:26 -0700
Message-id: <F9E4D0F4-2B80-423B-9272-D3CB55349CCC@apple.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com> <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com> <20101014205109.75a23d68@opy.nosense.org> <DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com> <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com> <4CB7BDCD.4000207@bogus.com> <13205C286662DE4387D9AF3AC30EF456B020F14DDF@EMBX01-WF.jnpr.net> <20101016081811.1fcb82e5@opy.nosense.org> <1055404F-D06A-4E8F-AA8D-3E62119F996C@virtualized.org> <4CB8D855.4080902@gmail.com> <FEF7DFB0-AA2B-47F6-9757-24D88C6FC39A@cisco.com>
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] Fwd:	I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2010 19:03:59 -0000

On Oct 19, 2010, at 11:40, Fred Baker wrote:
> 
> In preceding recommendations, the format of the document is to state a recommendation and follow it with an explanatory note. 

Actually, there's a lot of conceptual introduction followed by recommendation.  The current version of REC-13 is an example of this form.

> Which brings me to this suggestion:
> 
> /*
> * suggestion
> */
> REC-13:
> Residential Internet Gateways SHOULD provide a convenient means to securely update their firmware, for the installation of security patches and other manufacturer-recommended changes.
> 
> Vendors can expect users and operators to have differing viewpoints on the maintenance of patches, with some preferring automated update and some preferring manual initiation, and those preferring automated update wanting to download from a vendor site or one managed by the network operator. To handle the disparity, vendors are well advised if they provide manual and automated options. In the automated case, they would do well to facilitate pre-configuration of the download URL and a means of validating the software image such as a certificate.
> /*
> * end of suggestion
> */
> 
> Opinions?

I like this color.  Can I paint the bikeshed now?

p.s. I'd be inclined to leave alone the current paragraph preceding REC-13, then replace REC-13 with all of your suggested text above.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



From gert@space.net  Tue Oct 19 12:16:03 2010
Return-Path: <gert@space.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ECF2F3A693F for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 12:16:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id itjD4NMR8hpV for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 12:15:31 -0700 (PDT)
Received: from mobil.space.net (mobil.Space.Net [IPv6:2001:608:2:81::2]) by core3.amsl.com (Postfix) with ESMTP id 68F083A6930 for <v6ops@ietf.org>; Tue, 19 Oct 2010 12:15:29 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id 05685F81AE for <v6ops@ietf.org>; Tue, 19 Oct 2010 21:17:00 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id DA8EEF8179 for <v6ops@ietf.org>; Tue, 19 Oct 2010 21:16:59 +0200 (CEST)
Received: (qmail 73553 invoked by uid 1007); 19 Oct 2010 21:16:59 +0200
Date: Tue, 19 Oct 2010 21:16:59 +0200
From: Gert Doering <gert@space.net>
To: Fred Baker <fred@cisco.com>
Message-ID: <20101019191659.GG32268@Space.Net>
References: <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com> <20101014205109.75a23d68@opy.nosense.org> <DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com> <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com> <4CB7BDCD.4000207@bogus.com> <13205C286662DE4387D9AF3AC30EF456B020F14DDF@EMBX01-WF.jnpr.net> <20101016081811.1fcb82e5@opy.nosense.org> <1055404F-D06A-4E8F-AA8D-3E62119F996C@virtualized.org> <4CB8D855.4080902@gmail.com> <FEF7DFB0-AA2B-47F6-9757-24D88C6FC39A@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <FEF7DFB0-AA2B-47F6-9757-24D88C6FC39A@cisco.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: Operations <v6ops@ietf.org>, IESG IESG <iesg@ietf.org>, IPv6@core3.amsl.com
Subject: Re: [v6ops] Fwd:	I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2010 19:16:03 -0000

Hi,

On Tue, Oct 19, 2010 at 11:40:07AM -0700, Fred Baker wrote:
> /*
>  * suggestion
>  */
> REC-13:
> Residential Internet Gateways SHOULD provide a convenient means to securely update their firmware, for the installation of security patches and other manufacturer-recommended changes.
> 
> Vendors can expect users and operators to have differing viewpoints on the maintenance of patches, with some preferring automated update and some preferring manual initiation, and those preferring automated update wanting to download from a vendor site or one managed by the network operator. To handle the disparity, vendors are well advised if they provide manual and automated options. In the automated case, they would do well to facilitate pre-configuration of the download URL and a means of validating the software image such as a certificate.
> /*
>  * end of suggestion
>  */

Works for me.  Both from the ISP side and from the end user side.

Gert Doering
-- 
did you enable IPv6 on something today...?

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

From rbonica@juniper.net  Tue Oct 19 12:21:35 2010
Return-Path: <rbonica@juniper.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 01F613A6926; Tue, 19 Oct 2010 12:21:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.192
X-Spam-Level: 
X-Spam-Status: No, score=-106.192 tagged_above=-999 required=5 tests=[AWL=-0.193, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lHfYtqNUDG3V; Tue, 19 Oct 2010 12:21:34 -0700 (PDT)
Received: from exprod7og127.obsmtp.com (exprod7og127.obsmtp.com [64.18.2.210]) by core3.amsl.com (Postfix) with ESMTP id C21B83A67AB; Tue, 19 Oct 2010 12:21:30 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob127.postini.com ([64.18.6.12]) with SMTP ID DSNKTL3wFvLI2cShfOYdEqytYblG/xLZZCKZ@postini.com; Tue, 19 Oct 2010 12:23:05 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.2.254.0; Tue, 19 Oct 2010 12:19:08 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Tue, 19 Oct 2010 15:19:07 -0400
From: Ronald Bonica <rbonica@juniper.net>
To: Gert Doering <gert@space.net>, Fred Baker <fred@cisco.com>
Date: Tue, 19 Oct 2010 15:19:06 -0400
Thread-Topic: [v6ops]	Fwd:	I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
Thread-Index: Actvwk3R9lKHuU0eQXOIkyAqjTgQKQAACnBg
Message-ID: <13205C286662DE4387D9AF3AC30EF456B021143BA1@EMBX01-WF.jnpr.net>
References: <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com> <20101014205109.75a23d68@opy.nosense.org> <DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com> <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com> <4CB7BDCD.4000207@bogus.com> <13205C286662DE4387D9AF3AC30EF456B020F14DDF@EMBX01-WF.jnpr.net> <20101016081811.1fcb82e5@opy.nosense.org> <1055404F-D06A-4E8F-AA8D-3E62119F996C@virtualized.org> <4CB8D855.4080902@gmail.com> <FEF7DFB0-AA2B-47F6-9757-24D88C6FC39A@cisco.com> <20101019191659.GG32268@Space.Net>
In-Reply-To: <20101019191659.GG32268@Space.Net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Operations <v6ops@ietf.org>, IESG IESG <iesg@ietf.org>, "IPv6@core3.amsl.com" <IPv6@core3.amsl.com>
Subject: Re: [v6ops] Fwd:	I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2010 19:21:35 -0000

Me too

> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
> Of Gert Doering
> Sent: Tuesday, October 19, 2010 3:17 PM
> To: Fred Baker
> Cc: Operations; IESG IESG; IPv6@core3.amsl.com
> Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-
> security-15.txt
>=20
> Hi,
>=20
> On Tue, Oct 19, 2010 at 11:40:07AM -0700, Fred Baker wrote:
> > /*
> >  * suggestion
> >  */
> > REC-13:
> > Residential Internet Gateways SHOULD provide a convenient means to
> securely update their firmware, for the installation of security
> patches and other manufacturer-recommended changes.
> >
> > Vendors can expect users and operators to have differing viewpoints
> on the maintenance of patches, with some preferring automated update
> and some preferring manual initiation, and those preferring automated
> update wanting to download from a vendor site or one managed by the
> network operator. To handle the disparity, vendors are well advised if
> they provide manual and automated options. In the automated case, they
> would do well to facilitate pre-configuration of the download URL and a
> means of validating the software image such as a certificate.
> > /*
> >  * end of suggestion
> >  */
>=20
> Works for me.  Both from the ISP side and from the end user side.
>=20
> Gert Doering
> --
> did you enable IPv6 on something today...?
>=20
> SpaceNet AG                        Vorstand: Sebastian v. Bomhard
> Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-
> Culemann
> D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
> Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

From steve.dotson@cox.com  Tue Oct 19 12:59:25 2010
Return-Path: <steve.dotson@cox.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 57B943A6936; Tue, 19 Oct 2010 12:59:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.149
X-Spam-Level: 
X-Spam-Status: No, score=-3.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zJubCVldxoaL; Tue, 19 Oct 2010 12:59:24 -0700 (PDT)
Received: from post5.cox.com (post5.cox.com [24.248.74.41]) by core3.amsl.com (Postfix) with ESMTP id 1EA2E3A6949; Tue, 19 Oct 2010 12:59:24 -0700 (PDT)
Received: from ([192.168.74.254]) by post5.cox.com with ESMTP with TLS id 5503601.350155074; Tue, 19 Oct 2010 16:02:47 -0400
Received: from CATL0MS108.corp.cox.com ([fe80::9595:ca9f:7e29:b9b7]) by CATL0MS403.corp.cox.com ([10.62.236.91]) with mapi; Tue, 19 Oct 2010 16:00:48 -0400
From: <Steve.Dotson@cox.com>
To: <fred@cisco.com>, <v6ops@ietf.org>, <iesg@ietf.org>
Date: Tue, 19 Oct 2010 16:00:48 -0400
Thread-Topic: [v6ops]	Fwd:	I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
Thread-Index: ActvvckTHu+0B2ujT0+uJOJLxtWR/AACiDpg
Message-ID: <CF4030F9C0B29D4E8B86294E4760E2E5033A0D5D44@CATL0MS108.corp.cox.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com> <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com> <20101014205109.75a23d68@opy.nosense.org> <DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com> <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com> <4CB7BDCD.4000207@bogus.com> <13205C286662DE4387D9AF3AC30EF456B020F14DDF@EMBX01-WF.jnpr.net> <20101016081811.1fcb82e5@opy.nosense.org> <1055404F-D06A-4E8F-AA8D-3E62119F996C@virtualized.org> <4CB8D855.4080902@gmail.com> <FEF7DFB0-AA2B-47F6-9757-24D88C6FC39A@cisco.com>
In-Reply-To: <FEF7DFB0-AA2B-47F6-9757-24D88C6FC39A@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPv6@core3.amsl.com
Subject: Re: [v6ops] Fwd:	I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2010 19:59:25 -0000

I like it. As Gert already said, it speaks to both views.

-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of F=
red Baker
Sent: Tuesday, October 19, 2010 2:40 PM
To: Operations; IESG IESG
Cc: IPv6@core3.amsl.com
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-1=
5.txt


On Oct 15, 2010, at 3:40 PM, Brian E Carpenter wrote:

>> I'd think that recommending having an option that disables unattended au=
tomatic update would address this concern.  Managed service providers, sinc=
e they'd be controlling the CPE, could go in and disable unattended automat=
ic updates (if they so desire).
>=20
> I think the discussion has shown that we (the IETF) don't have consensus
> and that legal and commercial requirements will vary enormously in the
> real world. To me there's only one possible conclusion: the IETF can't
> "legislate" on this. So again here is my suggestion:
>=20
> REC-13:
> Residential Internet Gateways SHOULD provide a convenient means to
> securely update their firmware, for the installation of security patches
> and other manufacturer-recommended changes.

I have been following this discussion with a view to figuring out what reco=
mmendations SHOULD be made :-) A key concern I have here, as I said last we=
ek, is the difference between a residential gateway and a laptop; A laptop'=
s owner at least knows whether an irritating icon is jumping up and down or=
 has the opportunity to see a dialog box; I don't see that happening with t=
he router in my equipment closet under the stairs.

It seems that we agree that there are at least two options that need suppor=
t:
   - automated software update
   - manually initiated software update

One could go into other mechanisms such as having the user download the new=
 image to a laptop and then TFTP it to a router. Some things are best left =
unsuggested, for fear that the vendor might say "hey, that's a great idea!"=
.

In both cases, the update has to be initiated by the residential CPE, for s=
cale and reliability, and if automated should be randomized in time for rea=
sons discussed in RFC 3439. Having the ISP or the vendor manage a list of t=
he IP addresses of deployed routers is (ahem) problematic.

In both cases, we need a way to specify the URL and certificate of the down=
load site. I should imagine the vendor would preconfigure them, and an ISP =
running managed services could configure a different URL+certificate in rou=
ters it deploys. There is of course the question of what happens should the=
 parameter memory get zapped; I would leave that to the vendor. There is al=
so the question of how the device knows whether it has already downloaded t=
he image; I for one would do that by having the URL change itself, so that =
the client system ca always get access to an older image as a recovery path=
 and so it can tell whether the image it is requesting is in fact new.

In preceding recommendations, the format of the document is to state a reco=
mmendation and follow it with an explanatory note.=20

Which brings me to this suggestion:

/*
 * suggestion
 */
REC-13:
Residential Internet Gateways SHOULD provide a convenient means to securely=
 update their firmware, for the installation of security patches and other =
manufacturer-recommended changes.

Vendors can expect users and operators to have differing viewpoints on the =
maintenance of patches, with some preferring automated update and some pref=
erring manual initiation, and those preferring automated update wanting to =
download from a vendor site or one managed by the network operator. To hand=
le the disparity, vendors are well advised if they provide manual and autom=
ated options. In the automated case, they would do well to facilitate pre-c=
onfiguration of the download URL and a means of validating the software ima=
ge such as a certificate.
/*
 * end of suggestion
 */

Opinions?
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

From bs7652@att.com  Tue Oct 19 13:09:54 2010
Return-Path: <bs7652@att.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C0D513A695E; Tue, 19 Oct 2010 13:09:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.153
X-Spam-Level: 
X-Spam-Status: No, score=-106.153 tagged_above=-999 required=5 tests=[AWL=-0.154, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zeJufahFAjrt; Tue, 19 Oct 2010 13:09:51 -0700 (PDT)
Received: from mail167.messagelabs.com (mail167.messagelabs.com [216.82.253.179]) by core3.amsl.com (Postfix) with ESMTP id 870423A695B; Tue, 19 Oct 2010 13:09:51 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: bs7652@att.com
X-Msg-Ref: server-12.tower-167.messagelabs.com!1287519081!40496664!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 16098 invoked from network); 19 Oct 2010 20:11:22 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-12.tower-167.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 19 Oct 2010 20:11:22 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o9JKAiwp005485; Tue, 19 Oct 2010 16:10:44 -0400
Received: from 01GAF5142010621.AD.BLS.COM (01GAF5142010621.ad.bls.com [139.76.131.79]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with SMTP id o9JKAevf005416; Tue, 19 Oct 2010 16:10:40 -0400
Received: from 01NC27689010626.AD.BLS.COM ([90.144.44.201]) by 01GAF5142010621.AD.BLS.COM with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 19 Oct 2010 16:11:16 -0400
Received: from 01NC27689010650.AD.BLS.COM ([90.144.44.120]) by 01NC27689010626.AD.BLS.COM with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 19 Oct 2010 16:11:16 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 19 Oct 2010 16:11:15 -0400
Message-ID: <750BF7861EBBE048B3E648B4BB6E8F4F170B049A@crexc50p>
In-Reply-To: <CF4030F9C0B29D4E8B86294E4760E2E5033A0D5D44@CATL0MS108.corp.cox.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops]Fwd:	I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
Thread-Index: ActvvckTHu+0B2ujT0+uJOJLxtWR/AACiDpgAABugwA=
References: <20101012180001.D0C3C3A69CE@core3.amsl.com><ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com><20101014205109.75a23d68@opy.nosense.org><DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com><BE0267C0-302D-48CB-A167-F300B0170922@cisco.com><4CB7BDCD.4000207@bogus.com><13205C286662DE4387D9AF3AC30EF456B020F14DDF@EMBX01-WF.jnpr.net><20101016081811.1fcb82e5@opy.nosense.org><1055404F-D06A-4E8F-AA8D-3E62119F996C@virtualized.org><4CB8D855.4080902@gmail.com><FEF7DFB0-AA2B-47F6-9757-24D88C6FC39A@cisco.com> <CF4030F9C0B29D4E8B86294E4760E2E5033A0D5D44@CATL0MS108.corp.cox.com>
From: "STARK, BARBARA H (ATTLABS)" <bs7652@att.com>
To: <Steve.Dotson@cox.com>, <fred@cisco.com>, <v6ops@ietf.org>, <iesg@ietf.org>
X-OriginalArrivalTime: 19 Oct 2010 20:11:16.0265 (UTC) FILETIME=[C9113990:01CB6FC9]
Cc: IPv6@core3.amsl.com
Subject: Re: [v6ops] Fwd:	I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2010 20:09:55 -0000

It's fine.
Barbara

> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
> Of Steve.Dotson@cox.com
> Sent: Tuesday, October 19, 2010 4:01 PM
> To: fred@cisco.com; v6ops@ietf.org; iesg@ietf.org
> Cc: IPv6@core3.amsl.com
> Subject: Re: [v6ops]Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-
> security-15.txt
>=20
> I like it. As Gert already said, it speaks to both views.
>=20
> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
> Of Fred Baker
> Sent: Tuesday, October 19, 2010 2:40 PM
> To: Operations; IESG IESG
> Cc: IPv6@core3.amsl.com
> Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-
> security-15.txt
>=20
>=20
> On Oct 15, 2010, at 3:40 PM, Brian E Carpenter wrote:
>=20
> >> I'd think that recommending having an option that disables
> unattended automatic update would address this concern.  Managed
> service providers, since they'd be controlling the CPE, could go in
and
> disable unattended automatic updates (if they so desire).
> >
> > I think the discussion has shown that we (the IETF) don't have
> consensus
> > and that legal and commercial requirements will vary enormously in
> the
> > real world. To me there's only one possible conclusion: the IETF
> can't
> > "legislate" on this. So again here is my suggestion:
> >
> > REC-13:
> > Residential Internet Gateways SHOULD provide a convenient means to
> > securely update their firmware, for the installation of security
> patches
> > and other manufacturer-recommended changes.
>=20
> I have been following this discussion with a view to figuring out what
> recommendations SHOULD be made :-) A key concern I have here, as I
said
> last week, is the difference between a residential gateway and a
> laptop; A laptop's owner at least knows whether an irritating icon is
> jumping up and down or has the opportunity to see a dialog box; I
don't
> see that happening with the router in my equipment closet under the
> stairs.
>=20
> It seems that we agree that there are at least two options that need
> support:
>    - automated software update
>    - manually initiated software update
>=20
> One could go into other mechanisms such as having the user download
the
> new image to a laptop and then TFTP it to a router. Some things are
> best left unsuggested, for fear that the vendor might say "hey, that's
> a great idea!".
>=20
> In both cases, the update has to be initiated by the residential CPE,
> for scale and reliability, and if automated should be randomized in
> time for reasons discussed in RFC 3439. Having the ISP or the vendor
> manage a list of the IP addresses of deployed routers is (ahem)
> problematic.
>=20
> In both cases, we need a way to specify the URL and certificate of the
> download site. I should imagine the vendor would preconfigure them,
and
> an ISP running managed services could configure a different
> URL+certificate in routers it deploys. There is of course the question
> of what happens should the parameter memory get zapped; I would leave
> that to the vendor. There is also the question of how the device knows
> whether it has already downloaded the image; I for one would do that
by
> having the URL change itself, so that the client system ca always get
> access to an older image as a recovery path and so it can tell whether
> the image it is requesting is in fact new.
>=20
> In preceding recommendations, the format of the document is to state a
> recommendation and follow it with an explanatory note.
>=20
> Which brings me to this suggestion:
>=20
> /*
>  * suggestion
>  */
> REC-13:
> Residential Internet Gateways SHOULD provide a convenient means to
> securely update their firmware, for the installation of security
> patches and other manufacturer-recommended changes.
>=20
> Vendors can expect users and operators to have differing viewpoints on
> the maintenance of patches, with some preferring automated update and
> some preferring manual initiation, and those preferring automated
> update wanting to download from a vendor site or one managed by the
> network operator. To handle the disparity, vendors are well advised if
> they provide manual and automated options. In the automated case, they
> would do well to facilitate pre-configuration of the download URL and
a
> means of validating the software image such as a certificate.
> /*
>  * end of suggestion
>  */
>=20
> Opinions?
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

From brian.e.carpenter@gmail.com  Tue Oct 19 13:28:01 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 56A9A3A6969; Tue, 19 Oct 2010 13:28:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.284
X-Spam-Level: 
X-Spam-Status: No, score=-102.284 tagged_above=-999 required=5 tests=[AWL=-0.285, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kYG0EN0tYQUE; Tue, 19 Oct 2010 13:27:59 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 877083A695B; Tue, 19 Oct 2010 13:27:58 -0700 (PDT)
Received: by fxm17 with SMTP id 17so2171592fxm.31 for <multiple recipients>; Tue, 19 Oct 2010 13:29:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=vTQVKuC3o2mkuP7p6ECKv0SnIJD4z/KInwjDmcidm0A=; b=At2XObjblLfyaLbO2Xy6ZaWd5pCXCHbFGhPPEXl1tgtP2YiufSCg/x/CTuHnCzfRPN w5p9LBuQfQdrIFAuVR66j3D1QbGcGvOdGdfDvnbFgwgpu3KXZqk6KSc4Oouyxcwo7KA7 VOLc69NNAVR/L6LeggOI56nt+jSmhON7I827A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=Be8pJi1MZCOjXSXL+C3cH101Awpq2eYsOB4tBrpda911MTMT+cigpKMKJNfbFKMCJf Y0dtnDimKaLUxxSC/Vep3ELRdE2ejgUzZF2TIBprUsWAHXKgwBNr/sGatmQCvrULq1tE kBoMqIdIwH9jURTnMSxuXBJ3HgIvsW619wo1M=
Received: by 10.103.2.6 with SMTP id e6mr5460243mui.83.1287520168293; Tue, 19 Oct 2010 13:29:28 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id k4sm4174883faa.8.2010.10.19.13.29.24 (version=SSLv3 cipher=RC4-MD5); Tue, 19 Oct 2010 13:29:27 -0700 (PDT)
Message-ID: <4CBDFFA1.5080209@gmail.com>
Date: Wed, 20 Oct 2010 09:29:21 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com>	<ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com>	<20101014205109.75a23d68@opy.nosense.org>	<DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com>	<BE0267C0-302D-48CB-A167-F300B0170922@cisco.com>	<4CB7BDCD.4000207@bogus.com>	<13205C286662DE4387D9AF3AC30EF456B020F14DDF@EMBX01-WF.jnpr.net>	<20101016081811.1fcb82e5@opy.nosense.org>	<1055404F-D06A-4E8F-AA8D-3E62119F996C@virtualized.org>	<4CB8D855.4080902@gmail.com> <FEF7DFB0-AA2B-47F6-9757-24D88C6FC39A@cisco.com>
In-Reply-To: <FEF7DFB0-AA2B-47F6-9757-24D88C6FC39A@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Operations <v6ops@ietf.org>, IESG IESG <iesg@ietf.org>, IPv6@core3.amsl.com
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2010 20:28:01 -0000

Works for me too.

Regards
   Brian Carpenter

On 2010-10-20 07:40, Fred Baker wrote:
> On Oct 15, 2010, at 3:40 PM, Brian E Carpenter wrote:
> 
>>> I'd think that recommending having an option that disables unattended automatic update would address this concern.  Managed service providers, since they'd be controlling the CPE, could go in and disable unattended automatic updates (if they so desire).
>> I think the discussion has shown that we (the IETF) don't have consensus
>> and that legal and commercial requirements will vary enormously in the
>> real world. To me there's only one possible conclusion: the IETF can't
>> "legislate" on this. So again here is my suggestion:
>>
>> REC-13:
>> Residential Internet Gateways SHOULD provide a convenient means to
>> securely update their firmware, for the installation of security patches
>> and other manufacturer-recommended changes.
> 
> I have been following this discussion with a view to figuring out what recommendations SHOULD be made :-) A key concern I have here, as I said last week, is the difference between a residential gateway and a laptop; A laptop's owner at least knows whether an irritating icon is jumping up and down or has the opportunity to see a dialog box; I don't see that happening with the router in my equipment closet under the stairs.
> 
> It seems that we agree that there are at least two options that need support:
>    - automated software update
>    - manually initiated software update
> 
> One could go into other mechanisms such as having the user download the new image to a laptop and then TFTP it to a router. Some things are best left unsuggested, for fear that the vendor might say "hey, that's a great idea!".
> 
> In both cases, the update has to be initiated by the residential CPE, for scale and reliability, and if automated should be randomized in time for reasons discussed in RFC 3439. Having the ISP or the vendor manage a list of the IP addresses of deployed routers is (ahem) problematic.
> 
> In both cases, we need a way to specify the URL and certificate of the download site. I should imagine the vendor would preconfigure them, and an ISP running managed services could configure a different URL+certificate in routers it deploys. There is of course the question of what happens should the parameter memory get zapped; I would leave that to the vendor. There is also the question of how the device knows whether it has already downloaded the image; I for one would do that by having the URL change itself, so that the client system ca always get access to an older image as a recovery path and so it can tell whether the image it is requesting is in fact new.
> 
> In preceding recommendations, the format of the document is to state a recommendation and follow it with an explanatory note. 
> 
> Which brings me to this suggestion:
> 
> /*
>  * suggestion
>  */
> REC-13:
> Residential Internet Gateways SHOULD provide a convenient means to securely update their firmware, for the installation of security patches and other manufacturer-recommended changes.
> 
> Vendors can expect users and operators to have differing viewpoints on the maintenance of patches, with some preferring automated update and some preferring manual initiation, and those preferring automated update wanting to download from a vendor site or one managed by the network operator. To handle the disparity, vendors are well advised if they provide manual and automated options. In the automated case, they would do well to facilitate pre-configuration of the download URL and a means of validating the software image such as a certificate.
> /*
>  * end of suggestion
>  */
> 
> Opinions?
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> 

From ipng@69706e6720323030352d30312d31340a.nosense.org  Tue Oct 19 13:51:43 2010
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 68E2F3A6860; Tue, 19 Oct 2010 13:51:43 -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=[AWL=-0.082, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zAOC3ATAn1Ce; Tue, 19 Oct 2010 13:51:43 -0700 (PDT)
Received: from smtp1.adam.net.au (smtp1.adam.net.au [202.136.110.253]) by core3.amsl.com (Postfix) with ESMTP id E905A3A6863; Tue, 19 Oct 2010 13:51:42 -0700 (PDT)
Received: from 219-90-180-167.ip.adam.com.au ([219.90.180.167] helo=opy.nosense.org) by smtp1.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1P8JBC-0001nf-Or; Wed, 20 Oct 2010 07:23:06 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 087C33B31E; Wed, 20 Oct 2010 07:23:06 +1030 (CST)
Date: Wed, 20 Oct 2010 07:23:04 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Fred Baker <fred@cisco.com>
Message-ID: <20101020072304.01450c3a@opy.nosense.org>
In-Reply-To: <FEF7DFB0-AA2B-47F6-9757-24D88C6FC39A@cisco.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com> <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com> <20101014205109.75a23d68@opy.nosense.org> <DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com> <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com> <4CB7BDCD.4000207@bogus.com> <13205C286662DE4387D9AF3AC30EF456B020F14DDF@EMBX01-WF.jnpr.net> <20101016081811.1fcb82e5@opy.nosense.org> <1055404F-D06A-4E8F-AA8D-3E62119F996C@virtualized.org> <4CB8D855.4080902@gmail.com> <FEF7DFB0-AA2B-47F6-9757-24D88C6FC39A@cisco.com>
X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: Operations <v6ops@ietf.org>, IESG IESG <iesg@ietf.org>, IPv6@core3.amsl.com
Subject: Re: [v6ops] Fwd:	I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2010 20:51:43 -0000

Hi Fred,

I'm ok with it.

Regards,
Mark.


On Tue, 19 Oct 2010 11:40:07 -0700
Fred Baker <fred@cisco.com> wrote:

> 
> On Oct 15, 2010, at 3:40 PM, Brian E Carpenter wrote:
> 
> >> I'd think that recommending having an option that disables unattended automatic update would address this concern.  Managed service providers, since they'd be controlling the CPE, could go in and disable unattended automatic updates (if they so desire).
> > 
> > I think the discussion has shown that we (the IETF) don't have consensus
> > and that legal and commercial requirements will vary enormously in the
> > real world. To me there's only one possible conclusion: the IETF can't
> > "legislate" on this. So again here is my suggestion:
> > 
> > REC-13:
> > Residential Internet Gateways SHOULD provide a convenient means to
> > securely update their firmware, for the installation of security patches
> > and other manufacturer-recommended changes.
> 
> I have been following this discussion with a view to figuring out what recommendations SHOULD be made :-) A key concern I have here, as I said last week, is the difference between a residential gateway and a laptop; A laptop's owner at least knows whether an irritating icon is jumping up and down or has the opportunity to see a dialog box; I don't see that happening with the router in my equipment closet under the stairs.
> 
> It seems that we agree that there are at least two options that need support:
>    - automated software update
>    - manually initiated software update
> 
> One could go into other mechanisms such as having the user download the new image to a laptop and then TFTP it to a router. Some things are best left unsuggested, for fear that the vendor might say "hey, that's a great idea!".
> 
> In both cases, the update has to be initiated by the residential CPE, for scale and reliability, and if automated should be randomized in time for reasons discussed in RFC 3439. Having the ISP or the vendor manage a list of the IP addresses of deployed routers is (ahem) problematic.
> 
> In both cases, we need a way to specify the URL and certificate of the download site. I should imagine the vendor would preconfigure them, and an ISP running managed services could configure a different URL+certificate in routers it deploys. There is of course the question of what happens should the parameter memory get zapped; I would leave that to the vendor. There is also the question of how the device knows whether it has already downloaded the image; I for one would do that by having the URL change itself, so that the client system ca always get access to an older image as a recovery path and so it can tell whether the image it is requesting is in fact new.
> 
> In preceding recommendations, the format of the document is to state a recommendation and follow it with an explanatory note. 
> 
> Which brings me to this suggestion:
> 
> /*
>  * suggestion
>  */
> REC-13:
> Residential Internet Gateways SHOULD provide a convenient means to securely update their firmware, for the installation of security patches and other manufacturer-recommended changes.
> 
> Vendors can expect users and operators to have differing viewpoints on the maintenance of patches, with some preferring automated update and some preferring manual initiation, and those preferring automated update wanting to download from a vendor site or one managed by the network operator. To handle the disparity, vendors are well advised if they provide manual and automated options. In the automated case, they would do well to facilitate pre-configuration of the download URL and a means of validating the software image such as a certificate.
> /*
>  * end of suggestion
>  */
> 
> Opinions?
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

From brian.e.carpenter@gmail.com  Tue Oct 19 14:34:24 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE22F3A6897 for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 14:34:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q2h72gEKSCm1 for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 14:34:22 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id A249C3A6860 for <v6ops@ietf.org>; Tue, 19 Oct 2010 14:34:21 -0700 (PDT)
Received: by ewy6 with SMTP id 6so2097014ewy.31 for <v6ops@ietf.org>; Tue, 19 Oct 2010 14:35:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=aGRXwFfjS2aA3HP2Q3VXuz0UZ4IH/7S/eTHC9M1+xdY=; b=wdPktNPytt4n1YEoyYz4yn1+AuHR/dt8WgTEFnIPFRNaZruzuuBsHaIu481BU0B191 2uPzaDFb4Smbw8Vhpj3+zJIbGajhhrT0v3MFpPevvxa3nC9hqdEHBrE/7UTKJdUl1Qb4 KpAtE9j4WtfCJ8MpVEifEFCDmFi+1/g0gJrCc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; b=jWW8hnEoCFU728S0IduUNGNRs/a5zylCSbKxGfOeWQhyTw+f7YLWdwDHKhhzGa6Ggz TlGWj/DQPjIvOkDPK81/8L+xGpiBoMyuT4zUfw7Eel8lJUMRDpmJFVWnLTsFn1S9JwPT e9iBwWh5JOp0xUgorjgYrizu3GRUIyyZxvOS4=
Received: by 10.216.173.79 with SMTP id u57mr6057567wel.40.1287524152382; Tue, 19 Oct 2010 14:35:52 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id l14sm6297501weq.35.2010.10.19.14.35.48 (version=SSLv3 cipher=RC4-MD5); Tue, 19 Oct 2010 14:35:50 -0700 (PDT)
Message-ID: <4CBE0F32.8000504@gmail.com>
Date: Wed, 20 Oct 2010 10:35:46 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org,  IPv6 Operations <v6ops@ietf.org>
References: <20100922151502.E21FF3A6952@core3.amsl.com>
In-Reply-To: <20100922151502.E21FF3A6952@core3.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2010 21:34:24 -0000

Not to beat about the bush, I think this is a horrible idea.

6to4 is a temporary transition tool, which was actually designed
specifically to bypass ISPs that were not providing any form of
IPv6 service. I fully agree that ISPs should be managing transition,
but doing that by adding a NAT kludge to a temporary transition
tool is truly not the way to do this.

What would be good would be to detail carefully the failure scenarios
for 6to4 (and Teredo) and then recommend mitigations, for both ISPs
and content providers. At this point, it's clearly in the interests
of ISPs and content providers to do so.

Regards
   Brian Carpenter

From Bill.Armstrong@chartercom.com  Tue Oct 19 16:02:53 2010
Return-Path: <Bill.Armstrong@chartercom.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B1953A6888 for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 16:02:53 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 477jCPGCr8Kz for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 16:02:51 -0700 (PDT)
Received: from mail.chartercom.com (mail.chartercom.com [24.217.29.16]) by core3.amsl.com (Postfix) with ESMTP id C93C03A6804 for <v6ops@ietf.org>; Tue, 19 Oct 2010 16:02:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.57,352,1283749200"; d="scan'208";a="122701278"
Received: from unknown (HELO KSTLMEXHTP03.CORP.CHARTERCOM.COM) ([192.168.31.174]) by mail.chartercom.com with ESMTP; 19 Oct 2010 18:04:23 -0500
Received: from KSTLMEXCP02MBX.CORP.CHARTERCOM.COM ([192.168.31.12]) by KSTLMEXHTP03.CORP.CHARTERCOM.COM ([192.168.31.174]) with mapi; Tue, 19 Oct 2010 18:04:23 -0500
From: "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org" <draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org>, IPv6 Operations <v6ops@ietf.org>
Date: Tue, 19 Oct 2010 18:04:21 -0500
Thread-Topic: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: Actv1Z/KW2yf6cW1QP2oDFOx4DpKfAABcgcQ
Message-ID: <E71300B9B9041340B238540990BF04530914BB4CCF@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM>
References: <20100922151502.E21FF3A6952@core3.amsl.com> <4CBE0F32.8000504@gmail.com>
In-Reply-To: <4CBE0F32.8000504@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: Re: [v6ops] I-D	Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2010 23:02:53 -0000

So now we are forced to either pine for yet another non-existent bigger-and=
-better transition technology that's based on a world view where market fac=
tors don't drive the adoption of new technologies or write yet another list=
 of things we know are broken (or will be) with the existing technologies(p=
erhaps such and exercise was the impetus for this draft?)?=20

6to4 is one of the few transition technologies that, due to its prevalence =
in a good deal of EXISTING devices could allow for a more seamless transiti=
on to the IPv6 internet as well as act as a signal to both Internet and Con=
tent providers that PEOPLE are using the v6 internet. However due to the co=
mplete lack of any traffic engineering capabilities the user experience is =
FAR from ideal. All the while the addition of Stateless NAT on the provider=
 network (+1 for no consumer side changes\purchases) could allow for wider =
adoption of potentially LESS-broken IPv6 overnight(literally a maintenance =
window to enable the NAT in front of a given 6to4 relay).



-Bill


-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of B=
rian E Carpenter
Sent: Tuesday, October 19, 2010 4:36 PM
To: draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org; IPv6=
 Operations
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed=
-tunnel-00.txt

Not to beat about the bush, I think this is a horrible idea.

6to4 is a temporary transition tool, which was actually designed
specifically to bypass ISPs that were not providing any form of
IPv6 service. I fully agree that ISPs should be managing transition,
but doing that by adding a NAT kludge to a temporary transition
tool is truly not the way to do this.

What would be good would be to detail carefully the failure scenarios
for 6to4 (and Teredo) and then recommend mitigations, for both ISPs
and content providers. At this point, it's clearly in the interests
of ISPs and content providers to do so.

Regards
   Brian Carpenter
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

E-MAIL CONFIDENTIALITY NOTICE:=20

=20

=20

=20

The contents of this e-mail message and=20
any attachments are intended solely for the=20
addressee(s) and may contain confidential=20
and/or legally privileged information. If you=20
are not the intended recipient of this message=20
or if this message has been addressed to you=20
in error, please immediately alert the sender
 by reply e-mail and then delete this message=20
and any attachments. If you are not the=20
intended recipient, you are notified that=20
any use, dissemination, distribution, copying,=20
or storage of this message or any attachment=20
is strictly prohibited.









From fred@cisco.com  Tue Oct 19 16:18:29 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B7A0B3A6804 for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 16:18:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.004
X-Spam-Level: 
X-Spam-Status: No, score=-110.004 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OlahuKQ8NvJQ for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 16:18:28 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id D0FF83A6899 for <v6ops@ietf.org>; Tue, 19 Oct 2010 16:18:28 -0700 (PDT)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEALvEvUyrR7Hu/2dsb2JhbAChUXGnV5xGhUoEhFWFdoME
X-IronPort-AV: E=Sophos;i="4.57,353,1283731200"; d="scan'208";a="606600841"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-6.cisco.com with ESMTP; 19 Oct 2010 23:20:00 +0000
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o9JNJqcm019825; Tue, 19 Oct 2010 23:19:54 GMT
Received: from [127.0.0.1] by stealth-10-32-244-219.cisco.com (PGP Universal service); Tue, 19 Oct 2010 16:20:00 -0700
X-PGP-Universal: processed; by stealth-10-32-244-219.cisco.com on Tue, 19 Oct 2010 16:20:00 -0700
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <E71300B9B9041340B238540990BF04530914BB4CCF@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM>
Date: Tue, 19 Oct 2010 16:19:42 -0700
Message-Id: <ECD91250-8817-4746-ABC2-ED9CDFDFF82D@cisco.com>
References: <20100922151502.E21FF3A6952@core3.amsl.com> <4CBE0F32.8000504@gmail.com> <E71300B9B9041340B238540990BF04530914BB4CCF@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM>
To: "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>, "draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org" <draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org>
Subject: Re: [v6ops] I-D	Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2010 23:18:29 -0000

On Oct 19, 2010, at 4:04 PM, Armstrong, Bill R wrote:

> So now we are forced to either pine for yet another non-existent =
bigger-and-better transition technology that's based on a world view =
where market factors don't drive the adoption of new technologies or =
write yet another list of things we know are broken (or will be) with =
the existing technologies(perhaps such and exercise was the impetus for =
this draft?)?=20
>=20
> 6to4 is one of the few transition technologies that, due to its =
prevalence in a good deal of EXISTING devices could allow for a more =
seamless transition to the IPv6 internet as well as act as a signal to =
both Internet and Content providers that PEOPLE are using the v6 =
internet. However due to the complete lack of any traffic engineering =
capabilities the user experience is FAR from ideal. All the while the =
addition of Stateless NAT on the provider network (+1 for no consumer =
side changes\purchases) could allow for wider adoption of potentially =
LESS-broken IPv6 overnight(literally a maintenance window to enable the =
NAT in front of a given 6to4 relay).

</chair>
Personally, I think the issues that make 6to4 service less than =
wonderful are far more related to draft-ietf-v6ops-tunnel-loops and  =
than they are to traffic engineering capabilities. 6to4 encapsulates =
IPv6 in IPv4, which means that in today's predominantly IPv4 network =
6to4 enjoys the same traffic engineering that IPv4 traffic encounters.

> -Bill
>=20
>=20
> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf =
Of Brian E Carpenter
> Sent: Tuesday, October 19, 2010 4:36 PM
> To: draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org; =
IPv6 Operations
> Subject: Re: [v6ops] I-D =
Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
>=20
> Not to beat about the bush, I think this is a horrible idea.
>=20
> 6to4 is a temporary transition tool, which was actually designed
> specifically to bypass ISPs that were not providing any form of
> IPv6 service. I fully agree that ISPs should be managing transition,
> but doing that by adding a NAT kludge to a temporary transition
> tool is truly not the way to do this.
>=20
> What would be good would be to detail carefully the failure scenarios
> for 6to4 (and Teredo) and then recommend mitigations, for both ISPs
> and content providers. At this point, it's clearly in the interests
> of ISPs and content providers to do so.
>=20
> Regards
>   Brian Carpenter
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>=20
> E-MAIL CONFIDENTIALITY NOTICE:=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> The contents of this e-mail message and=20
> any attachments are intended solely for the=20
> addressee(s) and may contain confidential=20
> and/or legally privileged information. If you=20
> are not the intended recipient of this message=20
> or if this message has been addressed to you=20
> in error, please immediately alert the sender
> by reply e-mail and then delete this message=20
> and any attachments. If you are not the=20
> intended recipient, you are notified that=20
> any use, dissemination, distribution, copying,=20
> or storage of this message or any attachment=20
> is strictly prohibited.
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From ek@google.com  Tue Oct 19 16:30:32 2010
Return-Path: <ek@google.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C31543A6982 for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 16:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.827
X-Spam-Level: 
X-Spam-Status: No, score=-105.827 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KLAu4-tzq5sz for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 16:30:29 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id AF6763A681A for <v6ops@ietf.org>; Tue, 19 Oct 2010 16:30:06 -0700 (PDT)
Received: from wpaz29.hot.corp.google.com (wpaz29.hot.corp.google.com [172.24.198.93]) by smtp-out.google.com with ESMTP id o9JNVb9C022883 for <v6ops@ietf.org>; Tue, 19 Oct 2010 16:31:37 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1287531097; bh=MtCkkXkDFNW5ldOMDDlN/YgxICo=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=VZVlGhyvu5BXx1JLVXK2g87EJbwe7Tl9jUvDkdC0Hn8/ezbB1Jzc/Vj1bDS1VDbrD ELcTtc2nqvXb2geoYy4Vg==
Received: from qwd6 (qwd6.prod.google.com [10.241.193.198]) by wpaz29.hot.corp.google.com with ESMTP id o9JNV47t023348 for <v6ops@ietf.org>; Tue, 19 Oct 2010 16:31:36 -0700
Received: by qwd6 with SMTP id 6so591172qwd.14 for <v6ops@ietf.org>; Tue, 19 Oct 2010 16:31:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=XZzEW5NMXY5eFKk2DOS4bwfPsT6EAWHQtmOWeHvFwCo=; b=ugjzw8mYyd9LTpZjuwY+acAaM4r9gtMi64PqYTnwgnQCt/qUt1BSb74EnT94FQzIOu PB2e1zKOIPgLrorNHwtA==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=UFz3WA4LagX2dt7lE9rVGI5IRS//mHMYextFT0jxNFEx94UsFKHZBhHg8rd9sJ+dGX NbhylXj62NoDv6mD4nsg==
MIME-Version: 1.0
Received: by 10.224.11.20 with SMTP id r20mr1244464qar.395.1287531095912; Tue, 19 Oct 2010 16:31:35 -0700 (PDT)
Received: by 10.229.78.228 with HTTP; Tue, 19 Oct 2010 16:31:35 -0700 (PDT)
In-Reply-To: <ECD91250-8817-4746-ABC2-ED9CDFDFF82D@cisco.com>
References: <20100922151502.E21FF3A6952@core3.amsl.com> <4CBE0F32.8000504@gmail.com> <E71300B9B9041340B238540990BF04530914BB4CCF@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <ECD91250-8817-4746-ABC2-ED9CDFDFF82D@cisco.com>
Date: Tue, 19 Oct 2010 16:31:35 -0700
Message-ID: <AANLkTikiPjmhhzgTaiiOMuH8v4t=5PPOCnQH40hOQYcp@mail.gmail.com>
From: Erik Kline <ek@google.com>
To: Fred Baker <fred@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: IPv6 Operations <v6ops@ietf.org>, "draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org" <draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org>, "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2010 23:30:32 -0000
X-List-Received-Date: Tue, 19 Oct 2010 23:30:32 -0000

On 19 October 2010 16:19, Fred Baker <fred@cisco.com> wrote:
>
> On Oct 19, 2010, at 4:04 PM, Armstrong, Bill R wrote:
>
>> So now we are forced to either pine for yet another non-existent bigger-=
and-better transition technology that's based on a world view where market =
factors don't drive the adoption of new technologies or write yet another l=
ist of things we know are broken (or will be) with the existing technologie=
s(perhaps such and exercise was the impetus for this draft?)?
>>
>> 6to4 is one of the few transition technologies that, due to its prevalen=
ce in a good deal of EXISTING devices could allow for a more seamless trans=
ition to the IPv6 internet as well as act as a signal to both Internet and =
Content providers that PEOPLE are using the v6 internet. However due to the=
 complete lack of any traffic engineering capabilities the user experience =
is FAR from ideal. All the while the addition of Stateless NAT on the provi=
der network (+1 for no consumer side changes\purchases) could allow for wid=
er adoption of potentially LESS-broken IPv6 overnight(literally a maintenan=
ce window to enable the NAT in front of a given 6to4 relay).
>
> </chair>
> Personally, I think the issues that make 6to4 service less than wonderful=
 are far more related to draft-ietf-v6ops-tunnel-loops and =C2=A0than they =
are to traffic engineering capabilities. 6to4 encapsulates IPv6 in IPv4, wh=
ich means that in today's predominantly IPv4 network 6to4 enjoys the same t=
raffic engineering that IPv4 traffic encounters.

Also, this may basically be too late.  Some operating systems already
de-pref 6to4 when rfc1918 is available, and as other OSes pick this up
apps won't use 6to4 (yay) except to reach an IPv6-only destination
(fair enough).

From fred@cisco.com  Tue Oct 19 16:43:54 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 919CE3A6925 for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 16:43:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.304
X-Spam-Level: 
X-Spam-Status: No, score=-110.304 tagged_above=-999 required=5 tests=[AWL=0.295, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W0S0bc6njEES for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 16:43:53 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 1F4F73A690F for <v6ops@ietf.org>; Tue, 19 Oct 2010 16:43:53 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAFrKvUyrR7H+/2dsb2JhbAChUXGnRJxAhUoEhFWFdoME
X-IronPort-AV: E=Sophos;i="4.57,353,1283731200"; d="scan'208";a="203468550"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-4.cisco.com with ESMTP; 19 Oct 2010 23:45:25 +0000
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o9JNjEEm001106; Tue, 19 Oct 2010 23:45:17 GMT
Received: from [127.0.0.1] by stealth-10-32-244-219.cisco.com (PGP Universal service); Tue, 19 Oct 2010 16:45:24 -0700
X-PGP-Universal: processed; by stealth-10-32-244-219.cisco.com on Tue, 19 Oct 2010 16:45:24 -0700
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <12A4FA46AA7DA94A8FDBE2C945E1BF62016D414D@CL08MBC.rci.rogers.ca>
Date: Tue, 19 Oct 2010 16:45:07 -0700
Message-Id: <56EBC452-7E33-4BC9-AD27-AEF4806F8886@cisco.com>
References: <20100922151502.E21FF3A6952@core3.amsl.com> <4CBE0F32.8000504@gmail.com> <E71300B9B9041340B238540990BF04530914BB4CCF@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <ECD91250-8817-4746-ABC2-ED9CDFDFF82D@cisco.com> <12A4FA46AA7DA94A8FDBE2C945E1BF62016D414D@CL08MBC.rci.rogers.ca>
To: Victor Kuarsingh <Victor.Kuarsingh@rci.rogers.com>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>, draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org, "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>
Subject: Re: [v6ops] I-D	Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2010 23:43:54 -0000

On Oct 19, 2010, at 4:31 PM, Victor Kuarsingh wrote:

> I cannot stop 6to4, but can try and make it better as experienced by a =
customer (who has no knowledge, of IP and is just trying to "do" =
something on the web). =20

No doubt.

</chair>
My humble perspective, speaking strictly for myself here, is that any =
ISP (not just your employer, but any ISP) that is really concerned about =
consumer experience of IPv6 would do better to deploy IPv6 and manage it =
the same way it manages IPv4 traffic than to try to manage the way its =
customers work around the lack of native support.=

From prvs=901458893=Victor.Kuarsingh@rci.rogers.com  Tue Oct 19 14:48:23 2010
Return-Path: <prvs=901458893=Victor.Kuarsingh@rci.rogers.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 42C3C3A6860 for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 14:48:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.267
X-Spam-Level: 
X-Spam-Status: No, score=-1.267 tagged_above=-999 required=5 tests=[AWL=1.332,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D-sjvMMhar2L for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 14:48:20 -0700 (PDT)
Received: from mail.mail.rss.rogers.com (mail.tvrogers.com [142.146.31.23]) by core3.amsl.com (Postfix) with ESMTP id 494C33A68AE for <v6ops@ietf.org>; Tue, 19 Oct 2010 14:48:20 -0700 (PDT)
Content-Type: multipart/mixed; boundary="===============0785195694=="
MIME-Version: 1.0
Received: from unknown (HELO RSOESNEXIGWC.rci.rogers.ca) ([142.146.14.123]) by mail.mail.rss.rogers.com with ESMTP; 19 Oct 2010 17:49:51 -0400
Received: from RSOESNGTABHA.rci.rogers.ca ([10.3.37.22]) by RSOESNEXIGWC.rci.rogers.ca with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 19 Oct 2010 17:49:51 -0400
Received: from CL08MBC.rci.rogers.ca ([10.3.45.52]) by RSOESNGTABHA.rci.rogers.ca with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 19 Oct 2010 17:49:51 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
MIME-Version: 1.0
Date: Tue, 19 Oct 2010 17:48:51 -0400
Message-ID: <12A4FA46AA7DA94A8FDBE2C945E1BF62016D4147@CL08MBC.rci.rogers.ca>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: Actv1aDhoKewDnAIRUWV4OHcxGzJsgAAPZtz
References: <20100922151502.E21FF3A6952@core3.amsl.com> <4CBE0F32.8000504@gmail.com>
From: "Victor Kuarsingh" <Victor.Kuarsingh@rci.rogers.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>, <draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org>, "IPv6 Operations" <v6ops@ietf.org>
X-OriginalArrivalTime: 19 Oct 2010 21:49:51.0366 (UTC) FILETIME=[8EBE0260:01CB6FD7]
X-Mailman-Approved-At: Tue, 19 Oct 2010 16:53:00 -0700
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2010 21:48:23 -0000

--===============0785195694==
MIME-Version: 1.0
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Brian,

Valid input.

On a side note then, I am happy to entertain additional input as to what =
an "operator" can do for the following use case.

- Post IPv6 ramp up / IPv4 runout
- consumer is on IPv4-only (based on access network, home CPE etc)
- IPv6 only (AAAA) is now a possibility

This idea was not intended as a "transition tool" but more of a catch =
all.  It works with what's 'out there'.  I agree other mechanisms are =
better (i.e. Native, 6RD, 6a44 etc), but that all assumes an upgraded =
CPE/host.  this intended to be used as part of the tool kit, not a sole =
option.

Was trying to solve an issue we have in provider environments where we =
cannot get equipment changed out for so many reasons=20

regards,

Victor



-----Original Message-----
From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
Sent: Tue 10/19/2010 5:35 PM
To: draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org; =
IPv6 Operations
Subject: Re: I-D =
Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
=20
Not to beat about the bush, I think this is a horrible idea.

6to4 is a temporary transition tool, which was actually designed
specifically to bypass ISPs that were not providing any form of
IPv6 service. I fully agree that ISPs should be managing transition,
but doing that by adding a NAT kludge to a temporary transition
tool is truly not the way to do this.

What would be good would be to detail carefully the failure scenarios
for 6to4 (and Teredo) and then recommend mitigations, for both ISPs
and content providers. At this point, it's clearly in the interests
of ISPs and content providers to do so.

Regards
   Brian Carpenter


--===============0785195694==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline


This e-mail (and attachment(s)) is confidential, proprietary, may be subjec=
t to copyright and legal privilege and no related rights are waived. If you=
 are not the intended recipient or its agent, any review, dissemination, di=
stribution or copying of this e-mail or any of its content is strictly proh=
ibited and may be unlawful. All messages may be monitored as permitted by a=
pplicable law and regulations and our policies to protect our business. E-m=
ails are not secure and you are deemed to have accepted any risk if you com=
municate with us by e-mail. If received in error, please notify us immediat=
ely and delete the e-mail (and any attachments) from any computer or any st=
orage medium without printing a copy.

Ce courriel (ainsi que ses pi=C3=A8ces jointes) est confidentiel, exclusif,=
 et peut faire l=E2=80=99objet de droit d=E2=80=99auteur et de privil=C3=A8=
ge juridique; aucun droit connexe n=E2=80=99est exclu. Si vous n=E2=80=99=
=C3=AAtes pas le destinataire vis=C3=A9 ou son repr=C3=A9sentant, toute =C3=
=A9tude, diffusion, transmission ou copie de ce courriel en tout ou en part=
ie, est strictement interdite et peut =C3=AAtre ill=C3=A9gale. Tous les mes=
sages peuvent =C3=AAtre surveill=C3=A9s, selon les lois et r=C3=A8glements =
applicables et les politiques de protection de notre entreprise. Les courri=
els ne sont pas s=C3=A9curis=C3=A9s et vous =C3=AAtes r=C3=A9put=C3=A9s avo=
ir accept=C3=A9 tous les risques qui y sont li=C3=A9s si vous choisissez de=
 communiquer avec nous par ce moyen. Si vous avez re=C3=A7u ce message par =
erreur, veuillez nous en aviser imm=C3=A9diatement et supprimer ce courriel=
 (ainsi que toutes ses pi=C3=A8ces jointes) de tout ordinateur ou support d=
e donn=C3=A9es sans en imprimer une copie.=20

--===============0785195694==--

From prvs=901458893=Victor.Kuarsingh@rci.rogers.com  Tue Oct 19 16:32:45 2010
Return-Path: <prvs=901458893=Victor.Kuarsingh@rci.rogers.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AEC713A699D for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 16:32:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.133
X-Spam-Level: 
X-Spam-Status: No, score=-1.133 tagged_above=-999 required=5 tests=[AWL=0.866,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bbbXzQ6akaOj for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 16:31:43 -0700 (PDT)
Received: from mail.mail.rss.rogers.com (mail.mail.rss.rogers.com [142.146.31.23]) by core3.amsl.com (Postfix) with ESMTP id A9D003A6993 for <v6ops@ietf.org>; Tue, 19 Oct 2010 16:31:34 -0700 (PDT)
Content-Type: multipart/mixed; boundary="===============1835864390=="
MIME-Version: 1.0
Received: from unknown (HELO RSOESNEXIGWC.rci.rogers.ca) ([142.146.14.123]) by mail.mail.rss.rogers.com with ESMTP; 19 Oct 2010 19:32:47 -0400
Received: from RSOESNGTABHC.rci.rogers.ca ([10.3.37.54]) by RSOESNEXIGWC.rci.rogers.ca with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 19 Oct 2010 19:32:46 -0400
Received: from CL08MBC.rci.rogers.ca ([10.3.45.52]) by RSOESNGTABHC.rci.rogers.ca with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 19 Oct 2010 19:32:46 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
MIME-Version: 1.0
Date: Tue, 19 Oct 2010 19:31:56 -0400
Message-ID: <12A4FA46AA7DA94A8FDBE2C945E1BF62016D414D@CL08MBC.rci.rogers.ca>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops] I-D	Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: Actv5C74kVpgazpAR9eEAJw5dMI/QwAACqmk
References: <20100922151502.E21FF3A6952@core3.amsl.com> <4CBE0F32.8000504@gmail.com> <E71300B9B9041340B238540990BF04530914BB4CCF@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <ECD91250-8817-4746-ABC2-ED9CDFDFF82D@cisco.com>
From: "Victor Kuarsingh" <Victor.Kuarsingh@rci.rogers.com>
To: "Fred Baker" <fred@cisco.com>, "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>
X-OriginalArrivalTime: 19 Oct 2010 23:32:46.0384 (UTC) FILETIME=[EF56FB00:01CB6FE5]
X-Mailman-Approved-At: Tue, 19 Oct 2010 16:53:01 -0700
Cc: IPv6 Operations <v6ops@ietf.org>, draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org
Subject: Re: [v6ops] I-D	Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2010 23:32:46 -0000

--===============1835864390==
MIME-Version: 1.0
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Fred/others,

I think Bill was eluding to the issue of 6to4 return path (my guess).  =
When we (operators) put in BRs for 6to4 to help create a "better" 6to4 =
service, we cannot control the return path.  I know this was not the =
original intent of 6to4, but if the return path was not subject to less =
then optimal (sometime long) return paths, it is not bad as a catch all =
(it's widely deployed in OSs and equipment).

Our IPv4 environment follows (for the most part) our IPv4 route =
advertisement policy (i.e traffic comes back in a manner related to how =
we announce routes).  As for 6to4, the IPv6 return (which is vetted by =
relay on IPv6 side) it does not share our route "policy" attributes.

I cannot stop 6to4, but can try and make it better as experienced by a =
customer (who has no knowledge, of IP and is just trying to "do" =
something on the web). =20


Victor



-----Original Message-----
From: Fred Baker [mailto:fred@cisco.com]
Sent: Tue 10/19/2010 7:19 PM
To: Armstrong, Bill R
Cc: Brian E Carpenter; =
draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org; IPv6 =
Operations
Subject: Re: [v6ops] I-D	=
Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
=20

On Oct 19, 2010, at 4:04 PM, Armstrong, Bill R wrote:

> So now we are forced to either pine for yet another non-existent =
bigger-and-better transition technology that's based on a world view =
where market factors don't drive the adoption of new technologies or =
write yet another list of things we know are broken (or will be) with =
the existing technologies(perhaps such and exercise was the impetus for =
this draft?)?=20
>=20
> 6to4 is one of the few transition technologies that, due to its =
prevalence in a good deal of EXISTING devices could allow for a more =
seamless transition to the IPv6 internet as well as act as a signal to =
both Internet and Content providers that PEOPLE are using the v6 =
internet. However due to the complete lack of any traffic engineering =
capabilities the user experience is FAR from ideal. All the while the =
addition of Stateless NAT on the provider network (+1 for no consumer =
side changes\purchases) could allow for wider adoption of potentially =
LESS-broken IPv6 overnight(literally a maintenance window to enable the =
NAT in front of a given 6to4 relay).

</chair>
Personally, I think the issues that make 6to4 service less than =
wonderful are far more related to draft-ietf-v6ops-tunnel-loops and  =
than they are to traffic engineering capabilities. 6to4 encapsulates =
IPv6 in IPv4, which means that in today's predominantly IPv4 network =
6to4 enjoys the same traffic engineering that IPv4 traffic encounters.

> -Bill
>=20
>=20
> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf =
Of Brian E Carpenter
> Sent: Tuesday, October 19, 2010 4:36 PM
> To: draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org; =
IPv6 Operations
> Subject: Re: [v6ops] I-D =
Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
>=20
> Not to beat about the bush, I think this is a horrible idea.
>=20
> 6to4 is a temporary transition tool, which was actually designed
> specifically to bypass ISPs that were not providing any form of
> IPv6 service. I fully agree that ISPs should be managing transition,
> but doing that by adding a NAT kludge to a temporary transition
> tool is truly not the way to do this.
>=20
> What would be good would be to detail carefully the failure scenarios
> for 6to4 (and Teredo) and then recommend mitigations, for both ISPs
> and content providers. At this point, it's clearly in the interests
> of ISPs and content providers to do so.
>=20
> Regards
>   Brian Carpenter
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>=20
> E-MAIL CONFIDENTIALITY NOTICE:=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> The contents of this e-mail message and=20
> any attachments are intended solely for the=20
> addressee(s) and may contain confidential=20
> and/or legally privileged information. If you=20
> are not the intended recipient of this message=20
> or if this message has been addressed to you=20
> in error, please immediately alert the sender
> by reply e-mail and then delete this message=20
> and any attachments. If you are not the=20
> intended recipient, you are notified that=20
> any use, dissemination, distribution, copying,=20
> or storage of this message or any attachment=20
> is strictly prohibited.
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops



--===============1835864390==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline


This e-mail (and attachment(s)) is confidential, proprietary, may be subjec=
t to copyright and legal privilege and no related rights are waived. If you=
 are not the intended recipient or its agent, any review, dissemination, di=
stribution or copying of this e-mail or any of its content is strictly proh=
ibited and may be unlawful. All messages may be monitored as permitted by a=
pplicable law and regulations and our policies to protect our business. E-m=
ails are not secure and you are deemed to have accepted any risk if you com=
municate with us by e-mail. If received in error, please notify us immediat=
ely and delete the e-mail (and any attachments) from any computer or any st=
orage medium without printing a copy.

Ce courriel (ainsi que ses pi=C3=A8ces jointes) est confidentiel, exclusif,=
 et peut faire l=E2=80=99objet de droit d=E2=80=99auteur et de privil=C3=A8=
ge juridique; aucun droit connexe n=E2=80=99est exclu. Si vous n=E2=80=99=
=C3=AAtes pas le destinataire vis=C3=A9 ou son repr=C3=A9sentant, toute =C3=
=A9tude, diffusion, transmission ou copie de ce courriel en tout ou en part=
ie, est strictement interdite et peut =C3=AAtre ill=C3=A9gale. Tous les mes=
sages peuvent =C3=AAtre surveill=C3=A9s, selon les lois et r=C3=A8glements =
applicables et les politiques de protection de notre entreprise. Les courri=
els ne sont pas s=C3=A9curis=C3=A9s et vous =C3=AAtes r=C3=A9put=C3=A9s avo=
ir accept=C3=A9 tous les risques qui y sont li=C3=A9s si vous choisissez de=
 communiquer avec nous par ce moyen. Si vous avez re=C3=A7u ce message par =
erreur, veuillez nous en aviser imm=C3=A9diatement et supprimer ce courriel=
 (ainsi que toutes ses pi=C3=A8ces jointes) de tout ordinateur ou support d=
e donn=C3=A9es sans en imprimer une copie.=20

--===============1835864390==--

From xing@cernet.edu.cn  Tue Oct 19 17:34:57 2010
Return-Path: <xing@cernet.edu.cn>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A0F5F3A6910 for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 17:34:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.303
X-Spam-Level: 
X-Spam-Status: No, score=-99.303 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HAS_XAIMC=2.696, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5-b6qq+YekjQ for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 17:34:56 -0700 (PDT)
Received: from cernet.edu.cn (sea.net.edu.cn [202.112.39.2]) by core3.amsl.com (Postfix) with SMTP id 50B113A68E3 for <v6ops@ietf.org>; Tue, 19 Oct 2010 17:34:54 -0700 (PDT)
Received: from [IPv6:2001:252:ffca:2669:600::]([202.38.105.6]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm54cbe3cd6; Wed, 20 Oct 2010 08:36:10 +0800
Message-ID: <4CBE3974.5020806@cernet.edu.cn>
Date: Wed, 20 Oct 2010 08:36:04 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; zh-CN; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <20100922151502.E21FF3A6952@core3.amsl.com>	<4CBE0F32.8000504@gmail.com>	<E71300B9B9041340B238540990BF04530914BB4CCF@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM>	<ECD91250-8817-4746-ABC2-ED9CDFDFF82D@cisco.com>	<12A4FA46AA7DA94A8FDBE2C945E1BF62016D414D@CL08MBC.rci.rogers.ca> <56EBC452-7E33-4BC9-AD27-AEF4806F8886@cisco.com>
In-Reply-To: <56EBC452-7E33-4BC9-AD27-AEF4806F8886@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-AIMC-AUTH: xing
X-AIMC-MAILFROM: xing@cernet.edu.cn
X-AIMC-Msg-ID: swEfWIZB
Cc: IPv6 Operations <v6ops@ietf.org>, draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org, "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>, Victor Kuarsingh <Victor.Kuarsingh@rci.rogers.com>
Subject: Re: [v6ops] I-D	Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 00:34:57 -0000

  äºŽ 2010-10-20 7:45, Fred Baker å†™é�“:
> On Oct 19, 2010, at 4:31 PM, Victor Kuarsingh wrote:
>
>> I cannot stop 6to4, but can try and make it better as experienced by a customer (who has no knowledge, of IP and is just trying to "do" something on the web).
> No doubt.
>
> </chair>
> My humble perspective, speaking strictly for myself here, is that any ISP (not just your employer, but any ISP) that is really concerned about consumer experience of IPv6 would do better to deploy IPv6 and manage it the same way it manages IPv4 traffic than to try to manage the way its customers work around the lack of native support.

Fully agree with Fred.

xing

> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>
>


From brian.e.carpenter@gmail.com  Tue Oct 19 18:16:04 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BD6E63A6986 for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 18:16:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.281
X-Spam-Level: 
X-Spam-Status: No, score=-102.281 tagged_above=-999 required=5 tests=[AWL=-0.282, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GjOTykFYA9Cv for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 18:16:02 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 3375F3A6991 for <v6ops@ietf.org>; Tue, 19 Oct 2010 18:16:02 -0700 (PDT)
Received: by qwc9 with SMTP id 9so1929391qwc.31 for <v6ops@ietf.org>; Tue, 19 Oct 2010 18:17:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=f3mtsZ1Jt3tmVfd4rvKVIQRTcYvRXz1dE1jgUX3hl6Q=; b=M2+uT7Zn7Fsh5ijnV8Alp+6UQmnPPbzv3lGhzW1mwIFQKlU2kEX+SOmqxwkbEO35VL Xhbaa0gy7BrI63XA0hLLN3g+hAuGvRjyBiuJquyPtKFlVjTAHVCLgIxdOE/gKzxkmgsc sO8Gd7Qa7ZK4OH1Y8rgSP0NGVvccn4LdmhTrU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=UseYjg7pL+ptn82tmk2BPmxDJ4FpJ7l59RKIVWqkTsJIimmZVGUfMztpYqEB88wlda a4fr58LXvsiJ3/VLxN2qikmqoF8d4lTQ3xcX7QKI1RjZBTbCuNmri4oTPnSxUWB0Yrcw 9S9qn3AXx9b+qgwe1AJw7Ngx2sW/vbMnUtWao=
Received: by 10.224.186.66 with SMTP id cr2mr4150588qab.252.1287537453915; Tue, 19 Oct 2010 18:17:33 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id e18sm5374439vcf.36.2010.10.19.18.17.30 (version=SSLv3 cipher=RC4-MD5); Tue, 19 Oct 2010 18:17:33 -0700 (PDT)
Message-ID: <4CBE4333.9040600@gmail.com>
Date: Wed, 20 Oct 2010 14:17:39 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Victor Kuarsingh <Victor.Kuarsingh@rci.rogers.com>
References: <20100922151502.E21FF3A6952@core3.amsl.com> <4CBE0F32.8000504@gmail.com> <E71300B9B9041340B238540990BF04530914BB4CCF@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <ECD91250-8817-4746-ABC2-ED9CDFDFF82D@cisco.com> <12A4FA46AA7DA94A8FDBE2C945E1BF62016D414D@CL08MBC.rci.rogers.ca>
In-Reply-To: <12A4FA46AA7DA94A8FDBE2C945E1BF62016D414D@CL08MBC.rci.rogers.ca>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>, draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org, "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>
Subject: Re: [v6ops] I-D	Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 01:16:04 -0000

On 2010-10-20 12:31, Victor Kuarsingh wrote:
> Fred/others,
>=20
> I think Bill was eluding to the issue of 6to4 return path (my guess).  =
When we (operators) put in BRs for 6to4 to help create a "better" 6to4 se=
rvice, we cannot control the return path.  I know this was not the origin=
al intent of 6to4, but if the return path was not subject to less then op=
timal (sometime long) return paths, it is not bad as a catch all (it's wi=
dely deployed in OSs and equipment).

Sure. So if every ISP that has customers operating servers with IPv6 conn=
ectivity
provided a 6to4 relay and a route for 2002::/16, the return path for 6to4=

would end up being the same as the return path for IPv4. That was the des=
ign
point, and it seem to me that there is a strong incentive for those ISPs
to make it happen. Maybe this needs to be publicised.

   Brian

> Our IPv4 environment follows (for the most part) our IPv4 route adverti=
sement policy (i.e traffic comes back in a manner related to how we annou=
nce routes).  As for 6to4, the IPv6 return (which is vetted by relay on I=
Pv6 side) it does not share our route "policy" attributes.
>=20
> I cannot stop 6to4, but can try and make it better as experienced by a =
customer (who has no knowledge, of IP and is just trying to "do" somethin=
g on the web). =20
>=20
>=20
> Victor
>=20
>=20
>=20
> -----Original Message-----
> From: Fred Baker [mailto:fred@cisco.com]
> Sent: Tue 10/19/2010 7:19 PM
> To: Armstrong, Bill R
> Cc: Brian E Carpenter; draft-kuarsingh-v6ops-6to4-provider-managed-tunn=
el@tools.ietf.org; IPv6 Operations
> Subject: Re: [v6ops] I-D	Action:draft-kuarsingh-v6ops-6to4-provider-man=
aged-tunnel-00.txt
> =20
>=20
> On Oct 19, 2010, at 4:04 PM, Armstrong, Bill R wrote:
>=20
>> So now we are forced to either pine for yet another non-existent bigge=
r-and-better transition technology that's based on a world view where mar=
ket factors don't drive the adoption of new technologies or write yet ano=
ther list of things we know are broken (or will be) with the existing tec=
hnologies(perhaps such and exercise was the impetus for this draft?)?=20
>>
>> 6to4 is one of the few transition technologies that, due to its preval=
ence in a good deal of EXISTING devices could allow for a more seamless t=
ransition to the IPv6 internet as well as act as a signal to both Interne=
t and Content providers that PEOPLE are using the v6 internet. However du=
e to the complete lack of any traffic engineering capabilities the user e=
xperience is FAR from ideal. All the while the addition of Stateless NAT =
on the provider network (+1 for no consumer side changes\purchases) could=
 allow for wider adoption of potentially LESS-broken IPv6 overnight(liter=
ally a maintenance window to enable the NAT in front of a given 6to4 rela=
y).
>=20
> </chair>
> Personally, I think the issues that make 6to4 service less than wonderf=
ul are far more related to draft-ietf-v6ops-tunnel-loops and  than they a=
re to traffic engineering capabilities. 6to4 encapsulates IPv6 in IPv4, w=
hich means that in today's predominantly IPv4 network 6to4 enjoys the sam=
e traffic engineering that IPv4 traffic encounters.
>=20
>> -Bill
>>
>>
>> -----Original Message-----
>> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf=
 Of Brian E Carpenter
>> Sent: Tuesday, October 19, 2010 4:36 PM
>> To: draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org;=
 IPv6 Operations
>> Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-ma=
naged-tunnel-00.txt
>>
>> Not to beat about the bush, I think this is a horrible idea.
>>
>> 6to4 is a temporary transition tool, which was actually designed
>> specifically to bypass ISPs that were not providing any form of
>> IPv6 service. I fully agree that ISPs should be managing transition,
>> but doing that by adding a NAT kludge to a temporary transition
>> tool is truly not the way to do this.
>>
>> What would be good would be to detail carefully the failure scenarios
>> for 6to4 (and Teredo) and then recommend mitigations, for both ISPs
>> and content providers. At this point, it's clearly in the interests
>> of ISPs and content providers to do so.
>>
>> Regards
>>   Brian Carpenter
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>>
>> E-MAIL CONFIDENTIALITY NOTICE:=20
>>
>>
>>
>>
>>
>>
>>
>> The contents of this e-mail message and=20
>> any attachments are intended solely for the=20
>> addressee(s) and may contain confidential=20
>> and/or legally privileged information. If you=20
>> are not the intended recipient of this message=20
>> or if this message has been addressed to you=20
>> in error, please immediately alert the sender
>> by reply e-mail and then delete this message=20
>> and any attachments. If you are not the=20
>> intended recipient, you are notified that=20
>> any use, dissemination, distribution, copying,=20
>> or storage of this message or any attachment=20
>> is strictly prohibited.
>>
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>=20
>=20
>=20
> -----------------------------------------------------------------------=
-
>=20
>=20
> This e-mail (and attachment(s)) is confidential, proprietary, may be su=
bject to copyright and legal privilege and no related rights are waived. =
If you are not the intended recipient or its agent, any review, dissemina=
tion, distribution or copying of this e-mail or any of its content is str=
ictly prohibited and may be unlawful. All messages may be monitored as pe=
rmitted by applicable law and regulations and our policies to protect our=
 business. E-mails are not secure and you are deemed to have accepted any=
 risk if you communicate with us by e-mail. If received in error, please =
notify us immediately and delete the e-mail (and any attachments) from an=
y computer or any storage medium without printing a copy.
>=20
> Ce courriel (ainsi que ses pi=C3=A8ces jointes) est confidentiel, exclu=
sif, et peut faire l=E2=80=99objet de droit d=E2=80=99auteur et de privil=
=C3=A8ge juridique; aucun droit connexe n=E2=80=99est exclu. Si vous n=E2=
=80=99=C3=AAtes pas le destinataire vis=C3=A9 ou son repr=C3=A9sentant, t=
oute =C3=A9tude, diffusion, transmission ou copie de ce courriel en tout =
ou en partie, est strictement interdite et peut =C3=AAtre ill=C3=A9gale. =
Tous les messages peuvent =C3=AAtre surveill=C3=A9s, selon les lois et r=C3=
=A8glements applicables et les politiques de protection de notre entrepri=
se. Les courriels ne sont pas s=C3=A9curis=C3=A9s et vous =C3=AAtes r=C3=A9=
put=C3=A9s avoir accept=C3=A9 tous les risques qui y sont li=C3=A9s si vo=
us choisissez de communiquer avec nous par ce moyen. Si vous avez re=C3=A7=
u ce message par erreur, veuillez nous en aviser imm=C3=A9diatement et su=
pprimer ce courriel (ainsi que toutes ses pi=C3=A8ces jointes) de tout or=
dinateur ou support de donn=C3=A9es sans en imprimer une copie.=20


From bingxuere@gmail.com  Tue Oct 19 19:32:21 2010
Return-Path: <bingxuere@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 637933A6991 for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 19:32:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qBt0uQuOcvC3 for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 19:32:18 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id 1EEA33A6984 for <v6ops@ietf.org>; Tue, 19 Oct 2010 19:32:18 -0700 (PDT)
Received: by qyk36 with SMTP id 36so1139639qyk.10 for <v6ops@ietf.org>; Tue, 19 Oct 2010 19:33:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=ImVyh5hwduMyx08VPFpLOo2RpOWqEUpNL45n30WfgJ0=; b=oTYrJYbnSw02zcYQvZDWLOHXZk9/cyvl8xNnGF70SNJvwJu/WxHovFEKiUcmudbxXN mjHlEjFVQ59bnAhbzfPZH1OFtuuLsG3vwy5ZCoRtrLAwiDPk+kkeSJ3ol7/EPBH7QIF9 FS2JAWhD550JuWRPRKuqkD7fYxCpduP0NCJ54=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=kHc8SJy9eX81JTty+bPjpdhmnIOBwtMrNFhkmC73uaqViwX2cLg7ggKMk7dfGSaNk5 Mb3I/o9zL46VbYmrsqXdZFn87jjW/JCrYJgHMPUt8D86ZnWFGy7zL1ZJXRL/vOPFtAgi irdxYaRunNqfr83GGd2WQ4YDK0OgbPXpxr7zQ=
MIME-Version: 1.0
Received: by 10.229.222.200 with SMTP id ih8mr2407333qcb.266.1287542028880; Tue, 19 Oct 2010 19:33:48 -0700 (PDT)
Received: by 10.229.69.132 with HTTP; Tue, 19 Oct 2010 19:33:48 -0700 (PDT)
Date: Wed, 20 Oct 2010 10:33:48 +0800
Message-ID: <AANLkTikvoQJ+_=-Sb0CGemC6zC_LkQ4cwQtRQT+nkZ_B@mail.gmail.com>
From: =?UTF-8?B?5a2Z55C8?= <bingxuere@gmail.com>
To: v6ops@ietf.org
Content-Type: multipart/alternative; boundary=0016361e830243d01a0493033db9
Subject: [v6ops] Fw: New Version Notification for draft-sunq-v6ops-ivi-sp-00
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 02:39:10 -0000

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

Dear All,

We have submitted a new draft draft-sunq-v6ops-ivi-sp-00.txt.
Comments are welcome.

Best regards

  Qiong Sun
China Telecom Beijing Research Institute
Network Technology Department
------------------------------
Tel=EF=BC=9A18901332882
E-mail=EF=BC=9Asunqiong@ctbri.com.cn
------------------------------

 ------------------------------
*From=EF=BC=9A* IETF I-D Submission Tool
*Date=EF=BC=9A* 2010-10-18 21:27:10
*To=EF=BC=9A* sunqiong
*CC=EF=BC=9A* fengm; congxiao; xing; wanghy
*Subject=EF=BC=9A* New Version Notification for draft-sunq-v6ops-ivi-sp-00


A new version of I-D, draft-sunq-v6ops-ivi-sp-00.txt has been
successfully submitted by Qiong Sun and posted to the IETF repository.
Filename:  draft-sunq-v6ops-ivi-sp
Revision:  00
Title:
 Considerations for Stateless Translation (IVI/dIVI) in Large SP Network
Creation_date:  2010-10-18
WG ID:  Independent Submission
Number_of_pages: 17
Abstract:
With the approaching exhaustion of IPv4 address space, large-scale
SPs are now faced with the only real option to deploy IPv6 in a
timely manner. In order to achieve smooth transition to IPv6,
migration tools should be introduced for different deployment models.
Among different IPv6 transition mechanisms, dIVI is a prefix-specific
and stateless address mapping method which can directly translate
IPv4 packet to IPv6 packet. This document describes the challenges
and requirements for large SP to deploy IPv6 in operational network,
the experimental results of dIVI in our laboratory and the
considerations for dIVI deployment in large SP operational network.

The IETF Secretariat.

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

<div>Dear=C2=A0All,</div>
<div>=C2=A0</div>
<div>We have submitted=C2=A0a new draft draft-sunq-v6ops-ivi-sp-00.txt. <br=
></div>
<div>Comments are welcome.</div>
<div>=C2=A0</div>
<div>Best regards</div>
<div>=C2=A0</div><font color=3D"#000000">
<div>
<div>
<div>
<div>
<div>Qiong Sun</div>
<div>China Telecom Beijing Research Institute</div>
<div>Network Technology Department</div>
<div>------------------------------</div>
<div>Tel=EF=BC=9A18901332882</div>
<div>E-mail=EF=BC=9A<a href=3D"mailto:sunqiong@ctbri.com.cn">sunqiong@ctbri=
.com.cn</a></div>
<div>------------------------------=C2=A0</div></div></div></div>
<div>=C2=A0</div>
<div>
<hr color=3D"#b5c4df" size=3D"1">

<div><strong>From=EF=BC=9A</strong> IETF I-D Submission Tool</div>
<div><strong>Date=EF=BC=9A</strong> 2010-10-18=C2=A021:27:10</div>
<div><strong>To=EF=BC=9A</strong> sunqiong</div>
<div><strong>CC=EF=BC=9A</strong> fengm; congxiao; xing; wanghy</div>
<div><strong>Subject=EF=BC=9A</strong> New Version Notification for=20
draft-sunq-v6ops-ivi-sp-00</div>
<div>=C2=A0</div></div>
<div>

<div>A=C2=A0new=C2=A0version=C2=A0of=C2=A0I-D,=C2=A0draft-sunq-v6ops-ivi-sp=
-00.txt=C2=A0has=C2=A0been=C2=A0successfully=C2=A0submitted=C2=A0by=C2=A0Qi=
ong=C2=A0Sun=C2=A0and=C2=A0posted=C2=A0to=C2=A0the=C2=A0IETF=C2=A0repositor=
y.</div>

<div>Filename: =C2=A0draft-sunq-v6ops-ivi-sp</div>
<div>Revision: =C2=A000</div>
<div>Title:=20
=C2=A0Considerations=C2=A0for=C2=A0Stateless=C2=A0Translation=C2=A0(IVI/dIV=
I)=C2=A0in=C2=A0Large=C2=A0SP=C2=A0Network</div>
<div>Creation_date: =C2=A02010-10-18</div>
<div>WG=C2=A0ID: =C2=A0Independent=C2=A0Submission</div>
<div>Number_of_pages:=C2=A017</div>

<div>Abstract:</div>
<div>With=C2=A0the=C2=A0approaching=C2=A0exhaustion=C2=A0of=C2=A0IPv4=C2=A0=
address=C2=A0space,=C2=A0large-scale</div>
<div>SPs=C2=A0are=C2=A0now=C2=A0faced=C2=A0with=C2=A0the=C2=A0only=C2=A0rea=
l=C2=A0option=C2=A0to=C2=A0deploy=C2=A0IPv6=C2=A0in=C2=A0a</div>
<div>timely=C2=A0manner.=C2=A0In=C2=A0order=C2=A0to=C2=A0achieve=C2=A0smoot=
h=C2=A0transition=C2=A0to=C2=A0IPv6,</div>
<div>migration=C2=A0tools=C2=A0should=C2=A0be=C2=A0introduced=C2=A0for=C2=
=A0different=C2=A0deployment=C2=A0models.</div>
<div>Among=C2=A0different=C2=A0IPv6=C2=A0transition=C2=A0mechanisms,=C2=A0d=
IVI=C2=A0is=C2=A0a=C2=A0prefix-specific</div>
<div>and=C2=A0stateless=C2=A0address=C2=A0mapping=C2=A0method=C2=A0which=C2=
=A0can=C2=A0directly=C2=A0translate</div>
<div>IPv4=C2=A0packet=C2=A0to=C2=A0IPv6=C2=A0packet.=C2=A0This=C2=A0documen=
t=C2=A0describes=C2=A0the=C2=A0challenges</div>
<div>and=C2=A0requirements=C2=A0for=C2=A0large=C2=A0SP=C2=A0to=C2=A0deploy=
=C2=A0IPv6=C2=A0in=C2=A0operational=C2=A0network,</div>
<div>the=C2=A0experimental=C2=A0results=C2=A0of=C2=A0dIVI=C2=A0in=C2=A0our=
=C2=A0laboratory=C2=A0and=C2=A0the</div>
<div>considerations=C2=A0for=C2=A0dIVI=C2=A0deployment=C2=A0in=C2=A0large=
=C2=A0SP=C2=A0operational=C2=A0network.</div>
<div>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0</div>


<div>The=C2=A0IETF=C2=A0Secretariat.</div>

</div></div>
<div><font color=3D"#c0c0c0"><span>
<div>
<div>
<div>=C2=A0</div></div></div></span></font></div></font>

--0016361e830243d01a0493033db9--

From frnkblk@iname.com  Tue Oct 19 20:11:18 2010
Return-Path: <frnkblk@iname.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC0AE3A699F; Tue, 19 Oct 2010 20:11:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.65
X-Spam-Level: 
X-Spam-Status: No, score=0.65 tagged_above=-999 required=5 tests=[AWL=2.149, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YC6X-WH2tcvl; Tue, 19 Oct 2010 20:11:09 -0700 (PDT)
Received: from premieronline.net (smtp1-5.premieronline.net [96.31.0.25]) by core3.amsl.com (Postfix) with ESMTP id 5EAA63A699A; Tue, 19 Oct 2010 20:11:08 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=199.120.69.26; 
Received: from FrankBulkLapto (unverified [199.120.69.26])  by premieronline.net (SurgeMail 4.3k) with ESMTP id 17865103-1729245  for multiple; Tue, 19 Oct 2010 22:12:31 -0500
From: "Frank Bulk" <frnkblk@iname.com>
To: "'David Conrad'" <drc@virtualized.org>, "Yiu L. Lee" <yiu_lee@cable.comcast.com>
References: <C8DE33EB.3F293%yiu_lee@cable.comcast.com> <65A20F28-24CD-48FF-8852-97DCDD2AFCF7@virtualized.org>
In-Reply-To: <65A20F28-24CD-48FF-8852-97DCDD2AFCF7@virtualized.org>
Date: Tue, 19 Oct 2010 22:12:26 -0500
Message-ID: <!&!AAAAAAAAAAAuAAAAAAAAAKTyXRN5/+lGvU59a+P7CFMBAN6gY+ZG84BMpVQcAbDh1IQAAAATbSgAABAAAAAlaiBNusbDQJD0Y0S+If9/AQAAAAA=@iname.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: ActsrBjEeFXeMf/yQCSub9AFEyuOrwDWEefA
Content-Language: en-us
X-Authenticated-User: fbulk@premieronline.net 
X-SpamDetect: : 0.000000 
X-Info: aspam skipped due to (useraccess)
X-MyRbl: Color=Yellow Age=0 Spam=0 Notspam=0 Stars=2 Good=11 Friend=102 Surbl=0 Catch=0 r=6.4e-05 ip=199.120.69.26
X-IP-stats: Incoming Outgoing Last 0, First 591, in=8445681, out=42666, spam=0 Known=true ip=199.120.69.26
Cc: IPv6 Operations <v6ops@ietf.org>, iesg@ietf.org
Subject: Re: [v6ops] Fwd: I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: frnkblk@iname.com
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 03:11:18 -0000

I second David's idea.  It has the proper balance that allows the general
user to keep a properly-updated CPE, while allowing power users, who might
be annoyed by service interruptions, to disable it.

All this discussion doesn't preclude a CPE vendor from implementing a system
that only patches and reboots during the wee hours of the morning or upon a
power-cycle.

Frank

-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of
David Conrad
Sent: Friday, October 15, 2010 4:01 PM
To: Yiu L. Lee
Cc: IPv6 Operations; iesg@ietf.org
Subject: Re: [v6ops] Fwd: I-D
Action:draft-ietf-v6ops-cpe-simple-security-15.txt

On Oct 15, 2010, at 10:38 AM, Yiu L. Lee wrote:
> As a user, I also don't like automatic update w/o my consent.

If you have a TiVo, does it bother you that it updates itself without
consent?

I might observe that anyone on this mailing list is not the target audience
of automatic update.  

I suspect it would be more useful to view this from a risk mitigation/"least
harm" perspective.  The reality is that the vast majority of users are
unlikely to even know how to log into their CPE, much less be able to log
in, determine whether or not installing an update is a good idea, and
install that update.  Given the types of attacks we're seeing today (e.g.,
Drive-by Pharming), it seems to me that there are more risks to the Internet
as a whole to requiring manual intervention than not.

With that in mind, I'd prefer that there be a recommendation that automatic
updates be enabled by default with a mechanism to allow users to disable
those updates if they so desire.

Regards,
-drc

_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops


From frnkblk@iname.com  Tue Oct 19 20:18:49 2010
Return-Path: <frnkblk@iname.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6589D3A69A6; Tue, 19 Oct 2010 20:18:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.066
X-Spam-Level: 
X-Spam-Status: No, score=-0.066 tagged_above=-999 required=5 tests=[AWL=1.433,  BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D-ifIocUXjPH; Tue, 19 Oct 2010 20:18:48 -0700 (PDT)
Received: from premieronline.net (mail.premieronline.net [96.31.0.20]) by core3.amsl.com (Postfix) with ESMTP id B52AA3A69A4; Tue, 19 Oct 2010 20:18:47 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=199.120.69.26; 
Received: from FrankBulkLapto (unverified [199.120.69.26])  by premieronline.net (SurgeMail 4.3k) with ESMTP id 17796256-1729245  for multiple; Tue, 19 Oct 2010 22:20:13 -0500
From: "Frank Bulk" <frnkblk@iname.com>
To: "'Fred Baker'" <fred@cisco.com>, "Operations" <v6ops@ietf.org>, "IESG IESG" <iesg@ietf.org>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com>	<ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com>	<20101014205109.75a23d68@opy.nosense.org>	<DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com>	<BE0267C0-302D-48CB-A167-F300B0170922@cisco.com>	<4CB7BDCD.4000207@bogus.com>	<13205C286662DE4387D9AF3AC30EF456B020F14DDF@EMBX01-WF.jnpr.net>	<20101016081811.1fcb82e5@opy.nosense.org>	<1055404F-D06A-4E8F-AA8D-3E62119F996C@virtualized.org>	<4CB8D855.4080902@gmail.com> <FEF7DFB0-AA2B-47F6-9757-24D88C6FC39A@cisco.com>
In-Reply-To: <FEF7DFB0-AA2B-47F6-9757-24D88C6FC39A@cisco.com>
Date: Tue, 19 Oct 2010 22:20:06 -0500
Message-ID: <!&!AAAAAAAAAAAuAAAAAAAAAKTyXRN5/+lGvU59a+P7CFMBAN6gY+ZG84BMpVQcAbDh1IQAAAATbSgAABAAAABosHYZmm/URKRcq9yYp3GwAQAAAAA=@iname.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: ActvvdL2XMfUI1OoQIOjMExHZzrRRQAR7JCA
Content-Language: en-us
X-Authenticated-User: fbulk@premieronline.net 
X-SpamDetect: : 0.000000 
X-Info: aspam skipped due to (useraccess)
X-MyRbl: Color=Yellow Age=0 Spam=0 Notspam=0 Stars=1 Good=13 Friend=70 Surbl=0 Catch=0 r=3.6e-05 ip=199.120.69.26
X-IP-stats: Incoming Outgoing Last 0, First 588, in=8442960, out=31867, spam=0 Known=true ip=199.120.69.26
Cc: IPv6@core3.amsl.com
Subject: Re: [v6ops] Fwd:	I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: frnkblk@iname.com
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 03:18:49 -0000

I'm afraid if we use "SHOULD", CPE vendors will follow the path so far
followed, which is not building that option into their product.

I'd rather see a "MUST" to the automatic update functionality, but a
"SHOULD" in regards whether it's turned on by default or not.

Frank

-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of
Fred Baker
Sent: Tuesday, October 19, 2010 1:40 PM
To: Operations; IESG IESG
Cc: IPv6@core3.amsl.com
Subject: Re: [v6ops] Fwd: I-D
Action:draft-ietf-v6ops-cpe-simple-security-15.txt


On Oct 15, 2010, at 3:40 PM, Brian E Carpenter wrote:

>> I'd think that recommending having an option that disables unattended
automatic update would address this concern.  Managed service providers,
since they'd be controlling the CPE, could go in and disable unattended
automatic updates (if they so desire).
> 
> I think the discussion has shown that we (the IETF) don't have consensus
> and that legal and commercial requirements will vary enormously in the
> real world. To me there's only one possible conclusion: the IETF can't
> "legislate" on this. So again here is my suggestion:
> 
> REC-13:
> Residential Internet Gateways SHOULD provide a convenient means to
> securely update their firmware, for the installation of security patches
> and other manufacturer-recommended changes.

I have been following this discussion with a view to figuring out what
recommendations SHOULD be made :-) A key concern I have here, as I said last
week, is the difference between a residential gateway and a laptop; A
laptop's owner at least knows whether an irritating icon is jumping up and
down or has the opportunity to see a dialog box; I don't see that happening
with the router in my equipment closet under the stairs.

It seems that we agree that there are at least two options that need
support:
   - automated software update
   - manually initiated software update

One could go into other mechanisms such as having the user download the new
image to a laptop and then TFTP it to a router. Some things are best left
unsuggested, for fear that the vendor might say "hey, that's a great idea!".

In both cases, the update has to be initiated by the residential CPE, for
scale and reliability, and if automated should be randomized in time for
reasons discussed in RFC 3439. Having the ISP or the vendor manage a list of
the IP addresses of deployed routers is (ahem) problematic.

In both cases, we need a way to specify the URL and certificate of the
download site. I should imagine the vendor would preconfigure them, and an
ISP running managed services could configure a different URL+certificate in
routers it deploys. There is of course the question of what happens should
the parameter memory get zapped; I would leave that to the vendor. There is
also the question of how the device knows whether it has already downloaded
the image; I for one would do that by having the URL change itself, so that
the client system ca always get access to an older image as a recovery path
and so it can tell whether the image it is requesting is in fact new.

In preceding recommendations, the format of the document is to state a
recommendation and follow it with an explanatory note. 

Which brings me to this suggestion:

/*
 * suggestion
 */
REC-13:
Residential Internet Gateways SHOULD provide a convenient means to securely
update their firmware, for the installation of security patches and other
manufacturer-recommended changes.

Vendors can expect users and operators to have differing viewpoints on the
maintenance of patches, with some preferring automated update and some
preferring manual initiation, and those preferring automated update wanting
to download from a vendor site or one managed by the network operator. To
handle the disparity, vendors are well advised if they provide manual and
automated options. In the automated case, they would do well to facilitate
pre-configuration of the download URL and a means of validating the software
image such as a certificate.
/*
 * end of suggestion
 */

Opinions?
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops


From yiu_lee@cable.comcast.com  Tue Oct 19 20:21:59 2010
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A0B263A6997 for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 20:21:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.466
X-Spam-Level: 
X-Spam-Status: No, score=-104.466 tagged_above=-999 required=5 tests=[AWL=3.397, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dSNLQWEkDMxa for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 20:21:58 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 19AB93A699D for <v6ops@ietf.org>; Tue, 19 Oct 2010 20:21:58 -0700 (PDT)
Received: from ([24.40.55.40]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.100348964; Tue, 19 Oct 2010 23:23:27 -0400
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by pacdcexhub03.cable.comcast.com ([fe80::d1dd:b302:b617:3755%12]) with mapi id 14.01.0218.012; Tue, 19 Oct 2010 23:23:27 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [v6ops]	I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: AQHLb/SaKYlqleHzJE6S42Tu7kRkSpNJb2+A
Date: Wed, 20 Oct 2010 03:23:25 +0000
Message-ID: <C1271EB5-E81B-4D45-9BBF-C329EAFF9DED@Cable.Comcast.com>
References: <20100922151502.E21FF3A6952@core3.amsl.com> <4CBE0F32.8000504@gmail.com> <E71300B9B9041340B238540990BF04530914BB4CCF@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <ECD91250-8817-4746-ABC2-ED9CDFDFF82D@cisco.com> <12A4FA46AA7DA94A8FDBE2C945E1BF62016D414D@CL08MBC.rci.rogers.ca> <4CBE4333.9040600@gmail.com>
In-Reply-To: <4CBE4333.9040600@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="utf-8"
Content-ID: <2394256B1FEA3B4F9E5AF8802CB1E6EC@cable.comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: IPv6 Operations <v6ops@ietf.org>, "draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org" <draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org>, "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>, Victor Kuarsingh <Victor.Kuarsingh@rci.rogers.com>
Subject: Re: [v6ops] I-D	Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 03:21:59 -0000

SGkgQnJpYW4sDQoNCkZ1bGx5IGFncmVlLiBJbiBwcmFjdGljZSwgaG93IHRvIGNvb3JkaW5hdGUg
YWxsIHRoZSBJU1BzIHRvIGRlcGxveSA2dG80IFJlbGF5IGlzIGEgcmVhbCBjaGFsbGVuZ2UuIEhv
d2V2ZXIsIHVzaW5nIHRoaXMgdGVjaG5pcXVlIGNhbiBpbXByb3ZlIHRoZSBjdXN0b21lciBleHBl
cmllbmNlIGRheSBvbmUuIEFzIFZpY3RvciBwb2ludGVkIG91dCwgdGhpcyBpc24ndCBhIHRyYW5z
aXRpb24gdGVjaC4gV2UgbWVyZWx5IHdhbnQgdG8gcHJvdmlkZSBhIGJldHRlciBleHBlcmllbmNl
IHRvIHRoZSBleGlzdGluZyA2dG80IHVzZXJzIHdpdGhvdXQgY2hhbmdpbmcgYW55dGhpbmcuIE5v
IG5ldyBDUEUgb3IgaG9zdCB1cGdyYWRlLiBUaGUgcmVsYXkgd2lsbCBzdW5zZXQgYXMgc29vbiBh
cyBwZW9wbGUgY2hhbmdlIHRoZWlyIENQRSB0byBuYXRpdmUgdjYgb3IgNnJkLg0KDQpSZWdhcmRz
LA0KWWl1DQoNCg0KT24gT2N0IDE5LCAyMDEwLCBhdCA5OjE3IFBNLCAiQnJpYW4gRSBDYXJwZW50
ZXIiIDxicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb20+IHdyb3RlOg0KDQo+IE9uIDIwMTAtMTAt
MjAgMTI6MzEsIFZpY3RvciBLdWFyc2luZ2ggd3JvdGU6DQo+PiBGcmVkL290aGVycywNCj4+IA0K
Pj4gSSB0aGluayBCaWxsIHdhcyBlbHVkaW5nIHRvIHRoZSBpc3N1ZSBvZiA2dG80IHJldHVybiBw
YXRoIChteSBndWVzcykuICBXaGVuIHdlIChvcGVyYXRvcnMpIHB1dCBpbiBCUnMgZm9yIDZ0bzQg
dG8gaGVscCBjcmVhdGUgYSAiYmV0dGVyIiA2dG80IHNlcnZpY2UsIHdlIGNhbm5vdCBjb250cm9s
IHRoZSByZXR1cm4gcGF0aC4gIEkga25vdyB0aGlzIHdhcyBub3QgdGhlIG9yaWdpbmFsIGludGVu
dCBvZiA2dG80LCBidXQgaWYgdGhlIHJldHVybiBwYXRoIHdhcyBub3Qgc3ViamVjdCB0byBsZXNz
IHRoZW4gb3B0aW1hbCAoc29tZXRpbWUgbG9uZykgcmV0dXJuIHBhdGhzLCBpdCBpcyBub3QgYmFk
IGFzIGEgY2F0Y2ggYWxsIChpdCdzIHdpZGVseSBkZXBsb3llZCBpbiBPU3MgYW5kIGVxdWlwbWVu
dCkuDQo+IA0KPiBTdXJlLiBTbyBpZiBldmVyeSBJU1AgdGhhdCBoYXMgY3VzdG9tZXJzIG9wZXJh
dGluZyBzZXJ2ZXJzIHdpdGggSVB2NiBjb25uZWN0aXZpdHkNCj4gcHJvdmlkZWQgYSA2dG80IHJl
bGF5IGFuZCBhIHJvdXRlIGZvciAyMDAyOjovMTYsIHRoZSByZXR1cm4gcGF0aCBmb3IgNnRvNA0K
PiB3b3VsZCBlbmQgdXAgYmVpbmcgdGhlIHNhbWUgYXMgdGhlIHJldHVybiBwYXRoIGZvciBJUHY0
LiBUaGF0IHdhcyB0aGUgZGVzaWduDQo+IHBvaW50LCBhbmQgaXQgc2VlbSB0byBtZSB0aGF0IHRo
ZXJlIGlzIGEgc3Ryb25nIGluY2VudGl2ZSBmb3IgdGhvc2UgSVNQcw0KPiB0byBtYWtlIGl0IGhh
cHBlbi4gTWF5YmUgdGhpcyBuZWVkcyB0byBiZSBwdWJsaWNpc2VkLg0KPiANCj4gICBCcmlhbg0K
PiANCj4+IE91ciBJUHY0IGVudmlyb25tZW50IGZvbGxvd3MgKGZvciB0aGUgbW9zdCBwYXJ0KSBv
dXIgSVB2NCByb3V0ZSBhZHZlcnRpc2VtZW50IHBvbGljeSAoaS5lIHRyYWZmaWMgY29tZXMgYmFj
ayBpbiBhIG1hbm5lciByZWxhdGVkIHRvIGhvdyB3ZSBhbm5vdW5jZSByb3V0ZXMpLiAgQXMgZm9y
IDZ0bzQsIHRoZSBJUHY2IHJldHVybiAod2hpY2ggaXMgdmV0dGVkIGJ5IHJlbGF5IG9uIElQdjYg
c2lkZSkgaXQgZG9lcyBub3Qgc2hhcmUgb3VyIHJvdXRlICJwb2xpY3kiIGF0dHJpYnV0ZXMuDQo+
PiANCj4+IEkgY2Fubm90IHN0b3AgNnRvNCwgYnV0IGNhbiB0cnkgYW5kIG1ha2UgaXQgYmV0dGVy
IGFzIGV4cGVyaWVuY2VkIGJ5IGEgY3VzdG9tZXIgKHdobyBoYXMgbm8ga25vd2xlZGdlLCBvZiBJ
UCBhbmQgaXMganVzdCB0cnlpbmcgdG8gImRvIiBzb21ldGhpbmcgb24gdGhlIHdlYikuICANCj4+
IA0KPj4gDQo+PiBWaWN0b3INCj4+IA0KPj4gDQo+PiANCj4+IC0tLS0tT3JpZ2luYWwgTWVzc2Fn
ZS0tLS0tDQo+PiBGcm9tOiBGcmVkIEJha2VyIFttYWlsdG86ZnJlZEBjaXNjby5jb21dDQo+PiBT
ZW50OiBUdWUgMTAvMTkvMjAxMCA3OjE5IFBNDQo+PiBUbzogQXJtc3Ryb25nLCBCaWxsIFINCj4+
IENjOiBCcmlhbiBFIENhcnBlbnRlcjsgZHJhZnQta3VhcnNpbmdoLXY2b3BzLTZ0bzQtcHJvdmlk
ZXItbWFuYWdlZC10dW5uZWxAdG9vbHMuaWV0Zi5vcmc7IElQdjYgT3BlcmF0aW9ucw0KPj4gU3Vi
amVjdDogUmU6IFt2Nm9wc10gSS1ECUFjdGlvbjpkcmFmdC1rdWFyc2luZ2gtdjZvcHMtNnRvNC1w
cm92aWRlci1tYW5hZ2VkLXR1bm5lbC0wMC50eHQNCj4+IA0KPj4gDQo+PiBPbiBPY3QgMTksIDIw
MTAsIGF0IDQ6MDQgUE0sIEFybXN0cm9uZywgQmlsbCBSIHdyb3RlOg0KPj4gDQo+Pj4gU28gbm93
IHdlIGFyZSBmb3JjZWQgdG8gZWl0aGVyIHBpbmUgZm9yIHlldCBhbm90aGVyIG5vbi1leGlzdGVu
dCBiaWdnZXItYW5kLWJldHRlciB0cmFuc2l0aW9uIHRlY2hub2xvZ3kgdGhhdCdzIGJhc2VkIG9u
IGEgd29ybGQgdmlldyB3aGVyZSBtYXJrZXQgZmFjdG9ycyBkb24ndCBkcml2ZSB0aGUgYWRvcHRp
b24gb2YgbmV3IHRlY2hub2xvZ2llcyBvciB3cml0ZSB5ZXQgYW5vdGhlciBsaXN0IG9mIHRoaW5n
cyB3ZSBrbm93IGFyZSBicm9rZW4gKG9yIHdpbGwgYmUpIHdpdGggdGhlIGV4aXN0aW5nIHRlY2hu
b2xvZ2llcyhwZXJoYXBzIHN1Y2ggYW5kIGV4ZXJjaXNlIHdhcyB0aGUgaW1wZXR1cyBmb3IgdGhp
cyBkcmFmdD8pPyANCj4+PiANCj4+PiA2dG80IGlzIG9uZSBvZiB0aGUgZmV3IHRyYW5zaXRpb24g
dGVjaG5vbG9naWVzIHRoYXQsIGR1ZSB0byBpdHMgcHJldmFsZW5jZSBpbiBhIGdvb2QgZGVhbCBv
ZiBFWElTVElORyBkZXZpY2VzIGNvdWxkIGFsbG93IGZvciBhIG1vcmUgc2VhbWxlc3MgdHJhbnNp
dGlvbiB0byB0aGUgSVB2NiBpbnRlcm5ldCBhcyB3ZWxsIGFzIGFjdCBhcyBhIHNpZ25hbCB0byBi
b3RoIEludGVybmV0IGFuZCBDb250ZW50IHByb3ZpZGVycyB0aGF0IFBFT1BMRSBhcmUgdXNpbmcg
dGhlIHY2IGludGVybmV0LiBIb3dldmVyIGR1ZSB0byB0aGUgY29tcGxldGUgbGFjayBvZiBhbnkg
dHJhZmZpYyBlbmdpbmVlcmluZyBjYXBhYmlsaXRpZXMgdGhlIHVzZXIgZXhwZXJpZW5jZSBpcyBG
QVIgZnJvbSBpZGVhbC4gQWxsIHRoZSB3aGlsZSB0aGUgYWRkaXRpb24gb2YgU3RhdGVsZXNzIE5B
VCBvbiB0aGUgcHJvdmlkZXIgbmV0d29yayAoKzEgZm9yIG5vIGNvbnN1bWVyIHNpZGUgY2hhbmdl
c1xwdXJjaGFzZXMpIGNvdWxkIGFsbG93IGZvciB3aWRlciBhZG9wdGlvbiBvZiBwb3RlbnRpYWxs
eSBMRVNTLWJyb2tlbiBJUHY2IG92ZXJuaWdodChsaXRlcmFsbHkgYSBtYWludGVuYW5jZSB3aW5k
b3cgdG8gZW5hYmxlIHRoZSBOQVQgaW4gZnJvbnQgb2YgYSBnaXZlbiA2dG80IHJlbGF5KS4NCj4+
IA0KPj4gPC9jaGFpcj4NCj4+IFBlcnNvbmFsbHksIEkgdGhpbmsgdGhlIGlzc3VlcyB0aGF0IG1h
a2UgNnRvNCBzZXJ2aWNlIGxlc3MgdGhhbiB3b25kZXJmdWwgYXJlIGZhciBtb3JlIHJlbGF0ZWQg
dG8gZHJhZnQtaWV0Zi12Nm9wcy10dW5uZWwtbG9vcHMgYW5kICB0aGFuIHRoZXkgYXJlIHRvIHRy
YWZmaWMgZW5naW5lZXJpbmcgY2FwYWJpbGl0aWVzLiA2dG80IGVuY2Fwc3VsYXRlcyBJUHY2IGlu
IElQdjQsIHdoaWNoIG1lYW5zIHRoYXQgaW4gdG9kYXkncyBwcmVkb21pbmFudGx5IElQdjQgbmV0
d29yayA2dG80IGVuam95cyB0aGUgc2FtZSB0cmFmZmljIGVuZ2luZWVyaW5nIHRoYXQgSVB2NCB0
cmFmZmljIGVuY291bnRlcnMuDQo+PiANCj4+PiAtQmlsbA0KPj4+IA0KPj4+IA0KPj4+IC0tLS0t
T3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+Pj4gRnJvbTogdjZvcHMtYm91bmNlc0BpZXRmLm9yZyBb
bWFpbHRvOnY2b3BzLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBCcmlhbiBFIENhcnBl
bnRlcg0KPj4+IFNlbnQ6IFR1ZXNkYXksIE9jdG9iZXIgMTksIDIwMTAgNDozNiBQTQ0KPj4+IFRv
OiBkcmFmdC1rdWFyc2luZ2gtdjZvcHMtNnRvNC1wcm92aWRlci1tYW5hZ2VkLXR1bm5lbEB0b29s
cy5pZXRmLm9yZzsgSVB2NiBPcGVyYXRpb25zDQo+Pj4gU3ViamVjdDogUmU6IFt2Nm9wc10gSS1E
IEFjdGlvbjpkcmFmdC1rdWFyc2luZ2gtdjZvcHMtNnRvNC1wcm92aWRlci1tYW5hZ2VkLXR1bm5l
bC0wMC50eHQNCj4+PiANCj4+PiBOb3QgdG8gYmVhdCBhYm91dCB0aGUgYnVzaCwgSSB0aGluayB0
aGlzIGlzIGEgaG9ycmlibGUgaWRlYS4NCj4+PiANCj4+PiA2dG80IGlzIGEgdGVtcG9yYXJ5IHRy
YW5zaXRpb24gdG9vbCwgd2hpY2ggd2FzIGFjdHVhbGx5IGRlc2lnbmVkDQo+Pj4gc3BlY2lmaWNh
bGx5IHRvIGJ5cGFzcyBJU1BzIHRoYXQgd2VyZSBub3QgcHJvdmlkaW5nIGFueSBmb3JtIG9mDQo+
Pj4gSVB2NiBzZXJ2aWNlLiBJIGZ1bGx5IGFncmVlIHRoYXQgSVNQcyBzaG91bGQgYmUgbWFuYWdp
bmcgdHJhbnNpdGlvbiwNCj4+PiBidXQgZG9pbmcgdGhhdCBieSBhZGRpbmcgYSBOQVQga2x1ZGdl
IHRvIGEgdGVtcG9yYXJ5IHRyYW5zaXRpb24NCj4+PiB0b29sIGlzIHRydWx5IG5vdCB0aGUgd2F5
IHRvIGRvIHRoaXMuDQo+Pj4gDQo+Pj4gV2hhdCB3b3VsZCBiZSBnb29kIHdvdWxkIGJlIHRvIGRl
dGFpbCBjYXJlZnVsbHkgdGhlIGZhaWx1cmUgc2NlbmFyaW9zDQo+Pj4gZm9yIDZ0bzQgKGFuZCBU
ZXJlZG8pIGFuZCB0aGVuIHJlY29tbWVuZCBtaXRpZ2F0aW9ucywgZm9yIGJvdGggSVNQcw0KPj4+
IGFuZCBjb250ZW50IHByb3ZpZGVycy4gQXQgdGhpcyBwb2ludCwgaXQncyBjbGVhcmx5IGluIHRo
ZSBpbnRlcmVzdHMNCj4+PiBvZiBJU1BzIGFuZCBjb250ZW50IHByb3ZpZGVycyB0byBkbyBzby4N
Cj4+PiANCj4+PiBSZWdhcmRzDQo+Pj4gIEJyaWFuIENhcnBlbnRlcg0KPj4+IF9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+Pj4gdjZvcHMgbWFpbGluZyBs
aXN0DQo+Pj4gdjZvcHNAaWV0Zi5vcmcNCj4+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL3Y2b3BzDQo+Pj4gDQo+Pj4gRS1NQUlMIENPTkZJREVOVElBTElUWSBOT1RJQ0U6
IA0KPj4+IA0KPj4+IA0KPj4+IA0KPj4+IA0KPj4+IA0KPj4+IA0KPj4+IA0KPj4+IFRoZSBjb250
ZW50cyBvZiB0aGlzIGUtbWFpbCBtZXNzYWdlIGFuZCANCj4+PiBhbnkgYXR0YWNobWVudHMgYXJl
IGludGVuZGVkIHNvbGVseSBmb3IgdGhlIA0KPj4+IGFkZHJlc3NlZShzKSBhbmQgbWF5IGNvbnRh
aW4gY29uZmlkZW50aWFsIA0KPj4+IGFuZC9vciBsZWdhbGx5IHByaXZpbGVnZWQgaW5mb3JtYXRp
b24uIElmIHlvdSANCj4+PiBhcmUgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQgb2YgdGhpcyBt
ZXNzYWdlIA0KPj4+IG9yIGlmIHRoaXMgbWVzc2FnZSBoYXMgYmVlbiBhZGRyZXNzZWQgdG8geW91
IA0KPj4+IGluIGVycm9yLCBwbGVhc2UgaW1tZWRpYXRlbHkgYWxlcnQgdGhlIHNlbmRlcg0KPj4+
IGJ5IHJlcGx5IGUtbWFpbCBhbmQgdGhlbiBkZWxldGUgdGhpcyBtZXNzYWdlIA0KPj4+IGFuZCBh
bnkgYXR0YWNobWVudHMuIElmIHlvdSBhcmUgbm90IHRoZSANCj4+PiBpbnRlbmRlZCByZWNpcGll
bnQsIHlvdSBhcmUgbm90aWZpZWQgdGhhdCANCj4+PiBhbnkgdXNlLCBkaXNzZW1pbmF0aW9uLCBk
aXN0cmlidXRpb24sIGNvcHlpbmcsIA0KPj4+IG9yIHN0b3JhZ2Ugb2YgdGhpcyBtZXNzYWdlIG9y
IGFueSBhdHRhY2htZW50IA0KPj4+IGlzIHN0cmljdGx5IHByb2hpYml0ZWQuDQo+Pj4gDQo+Pj4g
DQo+Pj4gDQo+Pj4gDQo+Pj4gDQo+Pj4gDQo+Pj4gDQo+Pj4gDQo+Pj4gX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+PiB2Nm9wcyBtYWlsaW5nIGxpc3QN
Cj4+PiB2Nm9wc0BpZXRmLm9yZw0KPj4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vdjZvcHMNCj4+IA0KPj4gDQo+PiANCj4+IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPj4gDQo+PiAN
Cj4+IFRoaXMgZS1tYWlsIChhbmQgYXR0YWNobWVudChzKSkgaXMgY29uZmlkZW50aWFsLCBwcm9w
cmlldGFyeSwgbWF5IGJlIHN1YmplY3QgdG8gY29weXJpZ2h0IGFuZCBsZWdhbCBwcml2aWxlZ2Ug
YW5kIG5vIHJlbGF0ZWQgcmlnaHRzIGFyZSB3YWl2ZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRl
bmRlZCByZWNpcGllbnQgb3IgaXRzIGFnZW50LCBhbnkgcmV2aWV3LCBkaXNzZW1pbmF0aW9uLCBk
aXN0cmlidXRpb24gb3IgY29weWluZyBvZiB0aGlzIGUtbWFpbCBvciBhbnkgb2YgaXRzIGNvbnRl
bnQgaXMgc3RyaWN0bHkgcHJvaGliaXRlZCBhbmQgbWF5IGJlIHVubGF3ZnVsLiBBbGwgbWVzc2Fn
ZXMgbWF5IGJlIG1vbml0b3JlZCBhcyBwZXJtaXR0ZWQgYnkgYXBwbGljYWJsZSBsYXcgYW5kIHJl
Z3VsYXRpb25zIGFuZCBvdXIgcG9saWNpZXMgdG8gcHJvdGVjdCBvdXIgYnVzaW5lc3MuIEUtbWFp
bHMgYXJlIG5vdCBzZWN1cmUgYW5kIHlvdSBhcmUgZGVlbWVkIHRvIGhhdmUgYWNjZXB0ZWQgYW55
IHJpc2sgaWYgeW91IGNvbW11bmljYXRlIHdpdGggdXMgYnkgZS1tYWlsLiBJZiByZWNlaXZlZCBp
biBlcnJvciwgcGxlYXNlIG5vdGlmeSB1cyBpbW1lZGlhdGVseSBhbmQgZGVsZXRlIHRoZSBlLW1h
aWwgKGFuZCBhbnkgYXR0YWNobWVudHMpIGZyb20gYW55IGNvbXB1dGVyIG9yIGFueSBzdG9yYWdl
IG1lZGl1bSB3aXRob3V0IHByaW50aW5nIGEgY29weS4NCj4+IA0KPj4gQ2UgY291cnJpZWwgKGFp
bnNpIHF1ZSBzZXMgcGnDqGNlcyBqb2ludGVzKSBlc3QgY29uZmlkZW50aWVsLCBleGNsdXNpZiwg
ZXQgcGV1dCBmYWlyZSBs4oCZb2JqZXQgZGUgZHJvaXQgZOKAmWF1dGV1ciBldCBkZSBwcml2aWzD
qGdlIGp1cmlkaXF1ZTsgYXVjdW4gZHJvaXQgY29ubmV4ZSBu4oCZZXN0IGV4Y2x1LiBTaSB2b3Vz
IG7igJnDqnRlcyBwYXMgbGUgZGVzdGluYXRhaXJlIHZpc8OpIG91IHNvbiByZXByw6lzZW50YW50
LCB0b3V0ZSDDqXR1ZGUsIGRpZmZ1c2lvbiwgdHJhbnNtaXNzaW9uIG91IGNvcGllIGRlIGNlIGNv
dXJyaWVsIGVuIHRvdXQgb3UgZW4gcGFydGllLCBlc3Qgc3RyaWN0ZW1lbnQgaW50ZXJkaXRlIGV0
IHBldXQgw6p0cmUgaWxsw6lnYWxlLiBUb3VzIGxlcyBtZXNzYWdlcyBwZXV2ZW50IMOqdHJlIHN1
cnZlaWxsw6lzLCBzZWxvbiBsZXMgbG9pcyBldCByw6hnbGVtZW50cyBhcHBsaWNhYmxlcyBldCBs
ZXMgcG9saXRpcXVlcyBkZSBwcm90ZWN0aW9uIGRlIG5vdHJlIGVudHJlcHJpc2UuIExlcyBjb3Vy
cmllbHMgbmUgc29udCBwYXMgc8OpY3VyaXPDqXMgZXQgdm91cyDDqnRlcyByw6lwdXTDqXMgYXZv
aXIgYWNjZXB0w6kgdG91cyBsZXMgcmlzcXVlcyBxdWkgeSBzb250IGxpw6lzIHNpIHZvdXMgY2hv
aXNpc3NleiBkZSBjb21tdW5pcXVlciBhdmVjIG5vdXMgcGFyIGNlIG1veWVuLiBTaSB2b3VzIGF2
ZXogcmXDp3UgY2UgbWVzc2FnZSBwYXIgZXJyZXVyLCB2ZXVpbGxleiBub3VzIGVuIGF2aXNlciBp
bW3DqWRpYXRlbWVudCBldCBzdXBwcmltZXIgY2UgY291cnJpZWwgKGFpbnNpIHF1ZSB0b3V0ZXMg
c2VzIHBpw6hjZXMgam9pbnRlcykgZGUgdG91dCBvcmRpbmF0ZXVyIG91IHN1cHBvcnQgZGUgZG9u
bsOpZXMgc2FucyBlbiBpbXByaW1lciB1bmUgY29waWUuIA0KPiANCj4gX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gdjZvcHMgbWFpbGluZyBsaXN0DQo+
IHY2b3BzQGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
djZvcHMNCg==

From yiu_lee@cable.comcast.com  Tue Oct 19 20:41:47 2010
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5D0403A6984; Tue, 19 Oct 2010 20:41:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.952
X-Spam-Level: 
X-Spam-Status: No, score=-104.952 tagged_above=-999 required=5 tests=[AWL=2.912, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id scrbQlT5ZInW; Tue, 19 Oct 2010 20:41:47 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 5696F3A69AF; Tue, 19 Oct 2010 20:34:12 -0700 (PDT)
Received: from ([24.40.55.40]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.100350264; Tue, 19 Oct 2010 23:35:20 -0400
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by pacdcexhub03.cable.comcast.com ([fe80::d1dd:b302:b617:3755%12]) with mapi id 14.01.0218.012; Tue, 19 Oct 2010 23:35:21 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: Fred Baker <fred@cisco.com>
Thread-Topic: [v6ops]	Fwd:	I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
Thread-Index: AQHLb73H81JVgX7DzEWP05Et4brJ9JNJczQA
Date: Wed, 20 Oct 2010 03:35:20 +0000
Message-ID: <DB81914A-D8FF-4713-9785-1C94E47D714B@Cable.Comcast.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com> <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com> <20101014205109.75a23d68@opy.nosense.org> <DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com> <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com> <4CB7BDCD.4000207@bogus.com> <13205C286662DE4387D9AF3AC30EF456B020F14DDF@EMBX01-WF.jnpr.net> <20101016081811.1fcb82e5@opy.nosense.org> <1055404F-D06A-4E8F-AA8D-3E62119F996C@virtualized.org> <4CB8D855.4080902@gmail.com> <FEF7DFB0-AA2B-47F6-9757-24D88C6FC39A@cisco.com>
In-Reply-To: <FEF7DFB0-AA2B-47F6-9757-24D88C6FC39A@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1BC31AEAF900344281BB709AB1241546@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Operations <v6ops@ietf.org>, IESG IESG <iesg@ietf.org>
Subject: Re: [v6ops] Fwd:	I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 03:41:48 -0000

+1

On Oct 19, 2010, at 2:45 PM, "Fred Baker" <fred@cisco.com> wrote:

>=20
> On Oct 15, 2010, at 3:40 PM, Brian E Carpenter wrote:
>=20
>>> I'd think that recommending having an option that disables unattended a=
utomatic update would address this concern.  Managed service providers, sin=
ce they'd be controlling the CPE, could go in and disable unattended automa=
tic updates (if they so desire).
>>=20
>> I think the discussion has shown that we (the IETF) don't have consensus
>> and that legal and commercial requirements will vary enormously in the
>> real world. To me there's only one possible conclusion: the IETF can't
>> "legislate" on this. So again here is my suggestion:
>>=20
>> REC-13:
>> Residential Internet Gateways SHOULD provide a convenient means to
>> securely update their firmware, for the installation of security patches
>> and other manufacturer-recommended changes.
>=20
> I have been following this discussion with a view to figuring out what re=
commendations SHOULD be made :-) A key concern I have here, as I said last =
week, is the difference between a residential gateway and a laptop; A lapto=
p's owner at least knows whether an irritating icon is jumping up and down =
or has the opportunity to see a dialog box; I don't see that happening with=
 the router in my equipment closet under the stairs.
>=20
> It seems that we agree that there are at least two options that need supp=
ort:
>   - automated software update
>   - manually initiated software update
>=20
> One could go into other mechanisms such as having the user download the n=
ew image to a laptop and then TFTP it to a router. Some things are best lef=
t unsuggested, for fear that the vendor might say "hey, that's a great idea=
!".
>=20
> In both cases, the update has to be initiated by the residential CPE, for=
 scale and reliability, and if automated should be randomized in time for r=
easons discussed in RFC 3439. Having the ISP or the vendor manage a list of=
 the IP addresses of deployed routers is (ahem) problematic.
>=20
> In both cases, we need a way to specify the URL and certificate of the do=
wnload site. I should imagine the vendor would preconfigure them, and an IS=
P running managed services could configure a different URL+certificate in r=
outers it deploys. There is of course the question of what happens should t=
he parameter memory get zapped; I would leave that to the vendor. There is =
also the question of how the device knows whether it has already downloaded=
 the image; I for one would do that by having the URL change itself, so tha=
t the client system ca always get access to an older image as a recovery pa=
th and so it can tell whether the image it is requesting is in fact new.
>=20
> In preceding recommendations, the format of the document is to state a re=
commendation and follow it with an explanatory note.=20
>=20
> Which brings me to this suggestion:
>=20
> /*
> * suggestion
> */
> REC-13:
> Residential Internet Gateways SHOULD provide a convenient means to secure=
ly update their firmware, for the installation of security patches and othe=
r manufacturer-recommended changes.
>=20
> Vendors can expect users and operators to have differing viewpoints on th=
e maintenance of patches, with some preferring automated update and some pr=
eferring manual initiation, and those preferring automated update wanting t=
o download from a vendor site or one managed by the network operator. To ha=
ndle the disparity, vendors are well advised if they provide manual and aut=
omated options. In the automated case, they would do well to facilitate pre=
-configuration of the download URL and a means of validating the software i=
mage such as a certificate.
> /*
> * end of suggestion
> */
>=20
> Opinions?
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

From randy@psg.com  Tue Oct 19 22:40:55 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4ECDC3A69D0 for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 22:40:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[AWL=0.047,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r7fFD9VxysoC for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 22:40:53 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 783033A69CF for <v6ops@ietf.org>; Tue, 19 Oct 2010 22:40:07 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1P8RQD-000NX4-C3; Wed, 20 Oct 2010 05:41:09 +0000
Date: Tue, 19 Oct 2010 22:41:08 -0700
Message-ID: <m24ochl8uj.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <56EBC452-7E33-4BC9-AD27-AEF4806F8886@cisco.com>
References: <20100922151502.E21FF3A6952@core3.amsl.com> <4CBE0F32.8000504@gmail.com> <E71300B9B9041340B238540990BF04530914BB4CCF@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <ECD91250-8817-4746-ABC2-ED9CDFDFF82D@cisco.com> <12A4FA46AA7DA94A8FDBE2C945E1BF62016D414D@CL08MBC.rci.rogers.ca> <56EBC452-7E33-4BC9-AD27-AEF4806F8886@cisco.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 05:40:55 -0000

> My humble perspective, speaking strictly for myself here, is that any
> ISP (not just your employer, but any ISP) that is really concerned
> about consumer experience of IPv6 would do better to deploy IPv6 and
> manage it the same way it manages IPv4 traffic than to try to manage
> the way its customers work around the lack of native support.

yesssssssssss!  

bleeping brilliantly said.  thank you.

randy

From victor.kuarsingh@gmail.com  Tue Oct 19 23:50:46 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 973A73A6403 for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 23:50:46 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZhGlQe+UKPDU for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 23:50:45 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id 941203A63CA for <v6ops@ietf.org>; Tue, 19 Oct 2010 23:50:45 -0700 (PDT)
Received: by yxk30 with SMTP id 30so1585873yxk.31 for <v6ops@ietf.org>; Tue, 19 Oct 2010 23:52:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=8WM+a8hx7moyAhEuLSVqzIp5OQLm1Qk8RCRBxF4hNWA=; b=LntPPJTEJTTq8U32gUJdKKtyKnb2rCEZQkVDVXfGtBXLQ/GlTLcYBJn729S3qMVpGB Q5LvwjZRrkJGwLSuj2r9aVehXzGLw1n9CWJE20Ambi5Cg0cCa94W33jesSjUMxQGhRM0 eYZpJGr2C2l3EnQ4c/I/Wm4cBa0pwxXOu3WYc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=n37UtkFlz2TCD9PzkQqURAb7Oo/4eLIR3nc4S2BWK6ok6zKsjVOZo0uSQ0PsMWRWE+ PhYbC4TTIJE0gnv/d/Pzagg1RYTTSqdIIKCkVg37yDWLPX6HahjkvzjFHu2l04FbyHiC R/RwX+yIr06N17N6+gqatrMzE9+bGNbdgH6ng=
Received: by 10.101.162.10 with SMTP id p10mr4885773ano.241.1287557536306; Tue, 19 Oct 2010 23:52:16 -0700 (PDT)
Received: from [172.28.172.161] ([65.91.54.2]) by mx.google.com with ESMTPS id w15sm22967943anw.33.2010.10.19.23.52.12 (version=SSLv3 cipher=RC4-MD5); Tue, 19 Oct 2010 23:52:15 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Tue, 19 Oct 2010 23:52:09 -0700
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: Randy Bush <randy@psg.com>, Fred Baker <fred@cisco.com>
Message-ID: <C8E3DFA9.1025F%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: ActwI1CuD1+eEkpJNEiw+X1tcdSHxA==
In-Reply-To: <m24ochl8uj.wl%randy@psg.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 06:50:46 -0000

Fred,

I do agree with your position, but that is predicated on the ISP "managing"
the CPE.  In many cases, the ISP just provides "access" to IP which means
the customer equipment and it's capabilities are what determines what is
feasible at that site.

All the IPv6 enablement I do cannot change that (again, short of changing an
entire business model for a company, this is running state for many ISPs).
IPv4 service worked well since the equipment acquired by customers had a
baseline of functionality which for the most part worked with the provider
upstream systems.  IPv6 poses new challenges since the existing and deployed
gear in many cases dose not support IPv6. ISPs will try to get this
corrected but cannot control the entire deployment base.

But I do find that many see this transition challenge as an "either/or"
where we (many ISPs) see it as a combination of strategies.  I can work to
provide IPv6 native connectivity, while providing a better service for
endpoints that cannot support IPv6 day 1.  This was targeted as a part of
the "mix" to keep things going while the real work of IPv6 deployment is
carried out (again, not either/or, but parallel streams where this is not
compromising the IPv6 deployment).

This option is very easy to put in place (like 6to4 relays) and is low
touch.  I would not consume many resources and engineering effort.

I do see the argument if this was the sole strategy for a provider (which
makes little sense), but do not fully see everyone's position if it's part
of a bigger mix of technologies (of which IPv6 native is one) that supply
services to the large cross-section of customers with varying degrees of
functionality.  I can push for IPv6 and have this running on the side.

Regards,

Victor



On 19/10/10 10:41 PM, "Randy Bush" <randy@psg.com> wrote:

>> My humble perspective, speaking strictly for myself here, is that any
>> ISP (not just your employer, but any ISP) that is really concerned
>> about consumer experience of IPv6 would do better to deploy IPv6 and
>> manage it the same way it manages IPv4 traffic than to try to manage
>> the way its customers work around the lack of native support.
> 
> yesssssssssss!  
> 
> bleeping brilliantly said.  thank you.
> 
> randy
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops



From Bill.Armstrong@chartercom.com  Tue Oct 19 23:52:19 2010
Return-Path: <Bill.Armstrong@chartercom.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CDC713A63CA for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 23:52:19 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a3q5qLBPohrF for <v6ops@core3.amsl.com>; Tue, 19 Oct 2010 23:52:18 -0700 (PDT)
Received: from mail.chartercom.com (mail.chartercom.com [24.217.29.16]) by core3.amsl.com (Postfix) with ESMTP id A88743A69CA for <v6ops@ietf.org>; Tue, 19 Oct 2010 23:52:18 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.57,354,1283749200"; d="scan'208";a="122723775"
Received: from unknown (HELO KSTLMEXHTP02.CORP.CHARTERCOM.COM) ([192.168.31.32]) by mail.chartercom.com with ESMTP; 20 Oct 2010 01:53:51 -0500
Received: from KSTLMEXCP02MBX.CORP.CHARTERCOM.COM ([192.168.31.12]) by KSTLMEXHTP02.CORP.CHARTERCOM.COM ([192.168.31.32]) with mapi; Wed, 20 Oct 2010 01:53:50 -0500
From: "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>
To: Xing Li <xing@cernet.edu.cn>, Fred Baker <fred@cisco.com>, "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Date: Wed, 20 Oct 2010 01:53:47 -0500
Thread-Topic: [v6ops]	I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: Actv7szmMKtuioCBRh2TVR47gANzgAAGpNtQ
Message-ID: <E71300B9B9041340B238540990BF04530914BB4D8E@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM>
References: <20100922151502.E21FF3A6952@core3.amsl.com> <4CBE0F32.8000504@gmail.com> <E71300B9B9041340B238540990BF04530914BB4CCF@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <ECD91250-8817-4746-ABC2-ED9CDFDFF82D@cisco.com> <12A4FA46AA7DA94A8FDBE2C945E1BF62016D414D@CL08MBC.rci.rogers.ca> <56EBC452-7E33-4BC9-AD27-AEF4806F8886@cisco.com> <4CBE3974.5020806@cernet.edu.cn>
In-Reply-To: <4CBE3974.5020806@cernet.edu.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Cc: IPv6 Operations <v6ops@ietf.org>, "draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org" <draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org>
Subject: Re: [v6ops] I-D	Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 06:52:20 -0000

SSBhbHNvIGFncmVlIHdpdGggRnJlZCwgTmF0aXZlIGlzIHRoZSB3aW4gYW5kIGlzIHVuZG91YnRl
ZGx5IHRoZSBnb2FsLiBTb3JyeSBpZiBJIHdhcyBiaXQgY29uZnJvbnRhdGlvbmFsIGVhcmxpZXIs
IGJ1dCBsZXQncyBiZSBob25lc3QgYXQgcHJlc2VudCB0aGVyZSBhcmUgdmVyeSBmZXcgY3VzdG9t
ZXJzIGFza2luZyBmb3IgSVB2NiwgdGhlIHZhc3QgbWFqb3JpdHkgb2YgSVAgZW5hYmxlZCBjb25z
dW1lciBlbGVjdHJvbmljcyAobm9uLVBDcykgYXJlIElQdjQgb25seSwgYW5kIHRoZSBsYWNrIG9m
IFVTLWJhc2VkIElQdjYgY29udGVudCBkb2Vzbid0IGV4YWN0bHkgZm9zdGVyIHRoZSBraW5kIG9m
ICJyYWgtcmFoLWxldHMtZ28tc3BlbmQtYS1mb3J0dW5lLXRvLXJlcGxhY2UtTi1taWxsaW9uLUlQ
djQtb25seS1DUEUiIGF0dGl0dWRlLCBlbmdpbmVlciB0eXBlcyB3b3VsZCBob3BlIHRvIHNlZSBm
cm9tIHRoZSBidXNpbmVzcy4gU28gaWYgdGhlcmUgaXMgYSByZWxhdGl2ZWx5IHF1aWNrIGFuZCBj
b3N0IGVmZmVjdGl2ZSB3YXkgZm9yIGFuIElTUCB0byBwcm92aWRlIGFuIGltcHJvdmVkIElQdjYg
ZXhwZXJpZW5jZSByaWdodCBvdXQgb2YgdGhlIGdhdGUsIGRlc3BpdGUgaXQgbm90IGJlaW5nIE5h
dGl2ZSwgc2hvdWxkbid0IGl0LCBhdCB0aGUgdmVyeSBsZWFzdCBiZSBjb25zaWRlcmVkPyBQYXJ0
aWN1bGFybHkgd2hlbiB0aGUgYWx0ZXJuYXRpdmUgaXMgc2ltcGx5IHdhaXRpbmcgZm9yIDZyZFxE
Uy1saXRlXE5hdGl2ZSBjYXBhYmxlIENQRSBvciB0YWtpbmcgbm8gYWN0aW9uIHdoYXRzb2V2ZXIo
dGltZSBpcyBvZiB0aGUgZXNzZW5jZSwgbm8/KS4gDQoNCkFub3RoZXIgdGhpbmcgdGhhdCBJIHRo
aW5rIG5lZWRzIHRvIGJlIGNvbnNpZGVyZWQgaXMgdGhhdCBldmVyeSBkYXkgZm9yIGEgc3Vic2V0
IG9mIElQdjYgaW50ZXJuZXQgdXNlcnMsIGxlZ2l0aW1hdGVseSBpbXBhaXJlZCBJUHY2IHNlcnZp
Y2UgZXhpc3RzLCBhbmQgc29tZSBmcmFjdGlvbiBvZiB0aG9zZSB1c2VycyBoYXMgdGhlaXIgY3J1
bW15IElQdjYgZXhwZXJpZW5jZSByZWNvcmRlZCBhbmQgcmVwb3J0ZWQgb24uIFRoZXNlIG1ldHJp
Y3MgYW5kIG90aGVycyBsaWtlIHRoZW0gYXJlIHRoZSBzYW1lIG1ldHJpY3MgdGhhdCB3aWxsIGlu
Zmx1ZW5jZSB0aGUgZGF0YSB1c2VkIGluIHRoZSBkZWNpc2lvbiBtYWtpbmcgcHJvY2VzcyBieSBj
b3VudGxlc3Mgb3JnYW5pemF0aW9ucywgYmUgdGhleSBFbnRlcnByaXNlcywgSVNQcyBvciBDb250
ZW50IFByb3ZpZGVycyB0byBoZWxwIGRldGVybWluZSB3aGVuIHRoZXkgZmVlbCB0aGV5IHNob3Vs
ZCB0YWtlIHRoZSBJUHY2IHBsdW5nZS4gQW5kIGZvciB0aG9zZSBvcmdhbml6YXRpb24gdGhhdCBh
cmUgcGVyZmVjdGx5IGhhcHB5IHdpdGggdGhlaXIgc2luZ2xlIC8yNCBhbmQgZ29icyBvZiBOQVQg
d2hhdCByZWFzb24sIGJhc2VkIG9uIHRob3NlIHVuZGVycGVyZm9ybWluZyBJUHY2IG1ldHJpY3Ms
IHdvdWxkIHRoZXkgaGF2ZSB0byBldmVuIHJlcXVlc3RcZW5hYmxlIER1YWwtU3RhY2tlZCBvciBO
YXRpdmUgc2VydmljZSBmcm9tIHRoZWlyIHByb3ZpZGVyPyBJJ20gbm90IHRyeWluZyB0byBzYXkg
dGhhdCA2dG80IHJlbGF5IHVzZXJzIGluZmx1ZW5jZSB0aGUgbGlvbnMtc2hhcmUgb2YgdGhlIElQ
djYgaW50ZXJuZXQgdXNlIHN0YXRpc3RpY3MsIEknbSBzdXJlIHRoZWlyIGZhciBmcm9tIGl0LCB3
aGF0IEkgYW0gc2F5aW5nIGlzIHRoYXQgZnJvbSBhIHB1cmVseSBhbHRydWlzdGljLWdlZWsgcGVy
c3BlY3RpdmUsIGlzbid0IGFueXRoaW5nIHRoYXQgd2lsbCBoZWxwIHNpZ25hbCBhbmQgYWxsb3cg
Zm9yIHRoZSBhZG9wdGlvbiBvZiB2NiBvbiBhIGJyb2FkZXIgc2NhbGUgYXMgd2VsbCBhcyBoZWxw
IHRvIHByb3ZpZGUgaW1wcm92ZWQgaW50ZXJuZXQgcGVyZm9ybWFuY2Ugd2hhdCB3ZSdyZSBhbGwg
YWZ0ZXI/DQoNCg0KDQotQmlsbA0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9t
OiBYaW5nIExpIFttYWlsdG86eGluZ0BjZXJuZXQuZWR1LmNuXSANClNlbnQ6IFR1ZXNkYXksIE9j
dG9iZXIgMTksIDIwMTAgNzozNiBQTQ0KVG86IEZyZWQgQmFrZXINCkNjOiBWaWN0b3IgS3VhcnNp
bmdoOyBJUHY2IE9wZXJhdGlvbnM7IGRyYWZ0LWt1YXJzaW5naC12Nm9wcy02dG80LXByb3ZpZGVy
LW1hbmFnZWQtdHVubmVsQHRvb2xzLmlldGYub3JnOyBBcm1zdHJvbmcsIEJpbGwgUg0KU3ViamVj
dDogUmU6IFt2Nm9wc10gSS1EIEFjdGlvbjpkcmFmdC1rdWFyc2luZ2gtdjZvcHMtNnRvNC1wcm92
aWRlci1tYW5hZ2VkLXR1bm5lbC0wMC50eHQNCg0KICDkuo4gMjAxMC0xMC0yMCA3OjQ1LCBGcmVk
IEJha2VyIOWGmemBkzoNCj4gT24gT2N0IDE5LCAyMDEwLCBhdCA0OjMxIFBNLCBWaWN0b3IgS3Vh
cnNpbmdoIHdyb3RlOg0KPg0KPj4gSSBjYW5ub3Qgc3RvcCA2dG80LCBidXQgY2FuIHRyeSBhbmQg
bWFrZSBpdCBiZXR0ZXIgYXMgZXhwZXJpZW5jZWQgYnkgYSBjdXN0b21lciAod2hvIGhhcyBubyBr
bm93bGVkZ2UsIG9mIElQIGFuZCBpcyBqdXN0IHRyeWluZyB0byAiZG8iIHNvbWV0aGluZyBvbiB0
aGUgd2ViKS4NCj4gTm8gZG91YnQuDQo+DQo+IDwvY2hhaXI+DQo+IE15IGh1bWJsZSBwZXJzcGVj
dGl2ZSwgc3BlYWtpbmcgc3RyaWN0bHkgZm9yIG15c2VsZiBoZXJlLCBpcyB0aGF0IGFueSBJU1Ag
KG5vdCBqdXN0IHlvdXIgZW1wbG95ZXIsIGJ1dCBhbnkgSVNQKSB0aGF0IGlzIHJlYWxseSBjb25j
ZXJuZWQgYWJvdXQgY29uc3VtZXIgZXhwZXJpZW5jZSBvZiBJUHY2IHdvdWxkIGRvIGJldHRlciB0
byBkZXBsb3kgSVB2NiBhbmQgbWFuYWdlIGl0IHRoZSBzYW1lIHdheSBpdCBtYW5hZ2VzIElQdjQg
dHJhZmZpYyB0aGFuIHRvIHRyeSB0byBtYW5hZ2UgdGhlIHdheSBpdHMgY3VzdG9tZXJzIHdvcmsg
YXJvdW5kIHRoZSBsYWNrIG9mIG5hdGl2ZSBzdXBwb3J0Lg0KDQpGdWxseSBhZ3JlZSB3aXRoIEZy
ZWQuDQoNCnhpbmcNCg0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KPiB2Nm9wcyBtYWlsaW5nIGxpc3QNCj4gdjZvcHNAaWV0Zi5vcmcNCj4gaHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby92Nm9wcw0KPg0KPg0KDQoKRS1NQUlMIENP
TkZJREVOVElBTElUWSBOT1RJQ0U6IAoKIAoKIAoKIAoKVGhlIGNvbnRlbnRzIG9mIHRoaXMgZS1t
YWlsIG1lc3NhZ2UgYW5kIAphbnkgYXR0YWNobWVudHMgYXJlIGludGVuZGVkIHNvbGVseSBmb3Ig
dGhlIAphZGRyZXNzZWUocykgYW5kIG1heSBjb250YWluIGNvbmZpZGVudGlhbCAKYW5kL29yIGxl
Z2FsbHkgcHJpdmlsZWdlZCBpbmZvcm1hdGlvbi4gSWYgeW91IAphcmUgbm90IHRoZSBpbnRlbmRl
ZCByZWNpcGllbnQgb2YgdGhpcyBtZXNzYWdlIApvciBpZiB0aGlzIG1lc3NhZ2UgaGFzIGJlZW4g
YWRkcmVzc2VkIHRvIHlvdSAKaW4gZXJyb3IsIHBsZWFzZSBpbW1lZGlhdGVseSBhbGVydCB0aGUg
c2VuZGVyCiBieSByZXBseSBlLW1haWwgYW5kIHRoZW4gZGVsZXRlIHRoaXMgbWVzc2FnZSAKYW5k
IGFueSBhdHRhY2htZW50cy4gSWYgeW91IGFyZSBub3QgdGhlIAppbnRlbmRlZCByZWNpcGllbnQs
IHlvdSBhcmUgbm90aWZpZWQgdGhhdCAKYW55IHVzZSwgZGlzc2VtaW5hdGlvbiwgZGlzdHJpYnV0
aW9uLCBjb3B5aW5nLCAKb3Igc3RvcmFnZSBvZiB0aGlzIG1lc3NhZ2Ugb3IgYW55IGF0dGFjaG1l
bnQgCmlzIHN0cmljdGx5IHByb2hpYml0ZWQuCgoKCgoKCgo=


From remi.despres@free.fr  Wed Oct 20 00:09:23 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BCFA93A63CA for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 00:09:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.13
X-Spam-Level: 
X-Spam-Status: No, score=-1.13 tagged_above=-999 required=5 tests=[AWL=0.219,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eMvhUdOYU+G7 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 00:09:23 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.2]) by core3.amsl.com (Postfix) with ESMTP id A81943A69CA for <v6ops@ietf.org>; Wed, 20 Oct 2010 00:09:22 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2108.sfr.fr (SMTP Server) with ESMTP id 66E4C7000085; Wed, 20 Oct 2010 09:10:54 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2108.sfr.fr (SMTP Server) with ESMTP id D6E27700008B; Wed, 20 Oct 2010 09:10:53 +0200 (CEST)
X-SFR-UUID: 20101020071053880.D6E27700008B@msfrf2108.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <F9E4D0F4-2B80-423B-9272-D3CB55349CCC@apple.com>
Date: Wed, 20 Oct 2010 09:10:53 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0CE2DF18-8108-498F-A069-CF808CCB67D2@free.fr>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com> <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com> <20101014205109.75a23d68@opy.nosense.org> <DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com> <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com> <4CB7BDCD.4000207@bogus.com> <13205C286662DE4387D9AF3AC30EF456B020F14DDF@EMBX01-WF.jnpr.net> <20101016081811.1fcb82e5@opy.nosense.org> <1055404F-D06A-4E8F-AA8D-3E62119F996C@virtualized.org> <4CB8D855.4080902@gmail.com> <FEF7DFB0-AA2B-47F6-9757-24D88C6FC39A@cisco.com> <F9E4D0F4-2B80-423B-9272-D3CB55349CCC@apple.com>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1081)
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] Fwd:	I-D	Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 07:09:23 -0000

Le 19 oct. 2010 =E0 21:05, james woodyatt a =E9crit :

> On Oct 19, 2010, at 11:40, Fred Baker wrote:
>>=20
>> In preceding recommendations, the format of the document is to state =
a recommendation and follow it with an explanatory note.=20
>=20
> Actually, there's a lot of conceptual introduction followed by =
recommendation.  The current version of REC-13 is an example of this =
form.
>=20
>> Which brings me to this suggestion:
>>=20
>> /*
>> * suggestion
>> */
>> REC-13:
>> Residential Internet Gateways SHOULD provide a convenient means to =
securely update their firmware, for the installation of security patches =
and other manufacturer-recommended changes.
>>=20
>> Vendors can expect users and operators to have differing viewpoints =
on the maintenance of patches, with some preferring automated update and =
some preferring manual initiation, and those preferring automated update =
wanting to download from a vendor site or one managed by the network =
operator. To handle the disparity, vendors are well advised if they =
provide manual and automated options. In the automated case, they would =
do well to facilitate pre-configuration of the download URL and a means =
of validating the software image such as a certificate.
>> /*
>> * end of suggestion
>> */
>>=20
>> Opinions?
>=20
> I like this color.  Can I paint the bikeshed now?

Yes IMHO
I find this a good compromise. =20

> p.s. I'd be inclined to leave alone the current paragraph preceding =
REC-13, then replace REC-13 with all of your suggested text above.

My support holds with or without the sentence, or also with Fred's =
paragraph before REC-13 in place of the current sentence.

Regards,
RD

>=20
>=20
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, communications engineering
>=20
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops



From remi.despres@free.fr  Wed Oct 20 01:18:58 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D5E333A6857 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 01:18:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.432
X-Spam-Level: 
X-Spam-Status: No, score=-1.432 tagged_above=-999 required=5 tests=[AWL=0.517,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hpPDlUQS85F9 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 01:18:58 -0700 (PDT)
Received: from smtp22.services.sfr.fr (smtp22.services.sfr.fr [93.17.128.11]) by core3.amsl.com (Postfix) with ESMTP id 1313D3A681A for <v6ops@ietf.org>; Wed, 20 Oct 2010 01:18:58 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2206.sfr.fr (SMTP Server) with ESMTP id F3F21700009B; Wed, 20 Oct 2010 10:20:29 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2206.sfr.fr (SMTP Server) with ESMTP id 3CD1B7000099; Wed, 20 Oct 2010 10:20:27 +0200 (CEST)
X-SFR-UUID: 20101020082027249.3CD1B7000099@msfrf2206.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <C1271EB5-E81B-4D45-9BBF-C329EAFF9DED@Cable.Comcast.com>
Date: Wed, 20 Oct 2010 10:20:27 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <77479F2A-0939-4BD1-8DB7-7D62B20E4159@free.fr>
References: <20100922151502.E21FF3A6952@core3.amsl.com> <4CBE0F32.8000504@gmail.com> <E71300B9B9041340B238540990BF04530914BB4CCF@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <ECD91250-8817-4746-ABC2-ED9CDFDFF82D@cisco.com> <12A4FA46AA7DA94A8FDBE2C945E1BF62016D414D@CL08MBC.rci.rogers.ca> <4CBE4333.9040600@gmail.com> <C1271EB5-E81B-4D45-9BBF-C329EAFF9DED@Cable.Comcast.com>
To: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>, "draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org" <draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org>, "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>, Victor Kuarsingh <Victor.Kuarsingh@rci.rogers.com>
Subject: Re: [v6ops] I-D	Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 08:18:58 -0000

=20
Le 20 oct. 2010 =E0 05:23, Lee, Yiu a =E9crit :


> ... However, using this technique can improve the customer experience =
day one.

To some extent, it might (and, from a strictly technical point of view, =
the idea is neat), but:
- Providers that would support it would, for their customers, BREAK the =
e2e transparency (that IPv6 has so far restored in the Internet, and =
that is IMHO a great progress not to be lost).
- Unless I misunderstand, the draft doesn't completely describe what =
happens to 6to4 addresses that have non 0 SLA-ID after their embedded =
IPv4 addresses.=20
- The requirement of a Customer opt-out introduces significant =
complexity.=20

Regards,
RD





From randy@psg.com  Wed Oct 20 04:05:58 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D5DB3A659A for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 04:05:58 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ephlib6o8+hf for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 04:05:57 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 40EC83A63CB for <v6ops@ietf.org>; Wed, 20 Oct 2010 04:05:57 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1P8WW0-000OPy-NX; Wed, 20 Oct 2010 11:07:28 +0000
Date: Wed, 20 Oct 2010 04:07:28 -0700
Message-ID: <m2mxq9jf67.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Bill R Armstrong <Bill.Armstrong@chartercom.com>
In-Reply-To: <E71300B9B9041340B238540990BF04530914BB4D8E@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM>
References: <20100922151502.E21FF3A6952@core3.amsl.com> <4CBE0F32.8000504@gmail.com> <E71300B9B9041340B238540990BF04530914BB4CCF@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <ECD91250-8817-4746-ABC2-ED9CDFDFF82D@cisco.com> <12A4FA46AA7DA94A8FDBE2C945E1BF62016D414D@CL08MBC.rci.rogers.ca> <56EBC452-7E33-4BC9-AD27-AEF4806F8886@cisco.com> <4CBE3974.5020806@cernet.edu.cn> <E71300B9B9041340B238540990BF04530914BB4D8E@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 11:05:58 -0000

> there are very few customers asking for IPv6

and there are very few customers asking for ipv4.  they just want their
mtv.

very few customers walk into the car sales showroom and ask about the
wheel bearings.

randy

From sam.silvester@gmail.com  Wed Oct 20 04:54:23 2010
Return-Path: <sam.silvester@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EDB913A67D1; Wed, 20 Oct 2010 04:54: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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rpiXMZpuVo7X; Wed, 20 Oct 2010 04:54:22 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id D86373A67AC; Wed, 20 Oct 2010 04:54:21 -0700 (PDT)
Received: by qwc9 with SMTP id 9so2340463qwc.31 for <multiple recipients>; Wed, 20 Oct 2010 04:55:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=mI4nJz9eAxKAo5idKZRgm1XVZl6c4Co1fJ0URFW1BE8=; b=BZSLmog/yfSvQsIGW9Kcg12d21tvtIlTbBton5sMhu7iaPlzikxY/pQLW/8DKb0Ecx Qadkgl6pArgWiKYAcBHIDjgpAIcfjrhIEGP5JKF2/euB3sMFGFk68DPtUNfFKT/0ZZNH tH9r4HXDiiBr1i55RWQb+4UHg5+lSnzQ1XCO4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=JLLmFeoO5RFXBEqqDQQOkKjBFfp2arqeJ7GqLPuHackfjjMyNbzYigtAmTDgcLeZVk Ai/UggZK7Ueq43jpVskDoL8X07dxZDEEVVkKT2vFiyA3qwGBh5IfdcdSf85PuEyrl9fJ gG7Lv6SH/Nq7LCtFxE3NgyGlC8fxgyErh/cE0=
MIME-Version: 1.0
Received: by 10.229.239.129 with SMTP id kw1mr6374211qcb.90.1287575754472; Wed, 20 Oct 2010 04:55:54 -0700 (PDT)
Received: by 10.229.27.18 with HTTP; Wed, 20 Oct 2010 04:55:53 -0700 (PDT)
In-Reply-To: <FEF7DFB0-AA2B-47F6-9757-24D88C6FC39A@cisco.com>
References: <20101012180001.D0C3C3A69CE@core3.amsl.com> <ED22EE5B-641A-4DB7-857A-361AE388E989@cisco.com> <20101014205109.75a23d68@opy.nosense.org> <DAB0B79E-3354-48A4-87F0-D4C61B954C63@apple.com> <BE0267C0-302D-48CB-A167-F300B0170922@cisco.com> <4CB7BDCD.4000207@bogus.com> <13205C286662DE4387D9AF3AC30EF456B020F14DDF@EMBX01-WF.jnpr.net> <20101016081811.1fcb82e5@opy.nosense.org> <1055404F-D06A-4E8F-AA8D-3E62119F996C@virtualized.org> <4CB8D855.4080902@gmail.com> <FEF7DFB0-AA2B-47F6-9757-24D88C6FC39A@cisco.com>
Date: Wed, 20 Oct 2010 22:25:53 +1030
Message-ID: <AANLkTi=e9aNG4OCQztda_dTBSf8Ob-E49-2RGo7zkfQy@mail.gmail.com>
From: Sam Silvester <sam.silvester@gmail.com>
To: Fred Baker <fred@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Operations <v6ops@ietf.org>, IESG IESG <iesg@ietf.org>, IPv6@core3.amsl.com
Subject: Re: [v6ops] Fwd: I-D Action:draft-ietf-v6ops-cpe-simple-security-15.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 11:54:23 -0000

On Wed, Oct 20, 2010 at 5:10 AM, Fred Baker <fred@cisco.com> wrote:
>
> In preceding recommendations, the format of the document is to state a re=
commendation and follow it with an explanatory note.
>
> Which brings me to this suggestion:
>
> /*
> =A0* suggestion
> =A0*/
> REC-13:
> Residential Internet Gateways SHOULD provide a convenient means to secure=
ly update their firmware, for the installation of security patches and othe=
r manufacturer-recommended changes.
>
> Vendors can expect users and operators to have differing viewpoints on th=
e maintenance of patches, with some preferring automated update and some pr=
eferring manual initiation, and those preferring automated update wanting t=
o download from a vendor site or one managed by the network operator. To ha=
ndle the disparity, vendors are well advised if they provide manual and aut=
omated options. In the automated case, they would do well to facilitate pre=
-configuration of the download URL and a means of validating the software i=
mage such as a certificate.
> /*
> =A0* end of suggestion
> =A0*/
>
> Opinions?

Covers both cases and explains the situation well. Looks good.

Sam

From Jean-Francois.TremblayING@videotron.com  Wed Oct 20 06:42:06 2010
Return-Path: <Jean-Francois.TremblayING@videotron.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A56F3A67FE; Wed, 20 Oct 2010 06:42:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.109
X-Spam-Level: 
X-Spam-Status: No, score=0.109 tagged_above=-999 required=5 tests=[AWL=-0.293,  BAYES_00=-2.599, GB_I_LETTER=-2, GB_SUMOF=5, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v2tPhDRgUd2X; Wed, 20 Oct 2010 06:42:00 -0700 (PDT)
Received: from mx02.videotron.com (mx02.videotron.com [24.201.243.151]) by core3.amsl.com (Postfix) with ESMTP id F378D3A67EF; Wed, 20 Oct 2010 06:41:58 -0700 (PDT)
In-Reply-To: <77479F2A-0939-4BD1-8DB7-7D62B20E4159@free.fr>
To: remi.despres@free.fr
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006
Message-ID: <OFDA1BD473.DC458FF7-ON852577C2.004AFFF0-852577C2.004B6169@videotron.com>
From: Jean-Francois.TremblayING@videotron.com
Date: Wed, 20 Oct 2010 09:43:20 -0400
X-MIMETrack: Serialize by Router on DOMMTL11/SRV/GVL(Release 7.0.2FP1|January 10, 2007) at 2010-10-20 09:43:21
Content-Type: multipart/mixed; boundary="=_mixed 004B6168852577C2_="
Cc: IPv6 Operations <v6ops@ietf.org>, "draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org" <draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org>, "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>, v6ops-bounces@ietf.org, "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>, Victor Kuarsingh <Victor.Kuarsingh@rci.rogers.com>
Subject: Re: [v6ops] I-D	Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 13:42:06 -0000

--=_mixed 004B6168852577C2_=
Content-Type: multipart/alternative; boundary="=_alternative 004B6168852577C2_="


--=_alternative 004B6168852577C2_=
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

 >> Le 20 oct. 2010 =E0 05:23, Lee, Yiu a =E9crit :
>> ... However, using this technique can improve the customer experience=20
day one.

> To some extent, it might (and, from a strictly technical point of view,=20
> the idea is neat), but:
> - Providers that would support it would, for their customers, BREAK the=20
> e2e transparency (that IPv6 has so far restored in the Internet, and=20
that=20
> is IMHO a great progress not to be lost).
> - Unless I misunderstand, the draft doesn't completely describe what=20
happens=20
> to 6to4 addresses that have non 0 SLA-ID after their embedded IPv4=20
addresses.=20

Remi,=20
On this regards, please have a look at the following draft, it describes=20
in=20
more details how the addressing is affected (this draft is not available=20
as
an ID, we're sorry but we missed the submission deadline):




> - The requirement of a Customer opt-out introduces significant=20
complexity.=20
> Regards,
> RD

JFT
--=_alternative 004B6168852577C2_=
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable


<br>
<br><tt><font size=3D2>&nbsp;<br>
&gt;&gt; Le 20 oct. 2010 =E0 05:23, Lee, Yiu a =E9crit :<br>
&gt;&gt; ... However, using this technique can improve the customer experie=
nce
day one.<br>
<br>
&gt; To some extent, it might (and, from a strictly technical point of
view, </font></tt>
<br><tt><font size=3D2>&gt; the idea is neat), but:<br>
&gt; - Providers that would support it would, for their customers, BREAK
the </font></tt>
<br><tt><font size=3D2>&gt; e2e transparency (that IPv6 has so far restored
in the Internet, and that </font></tt>
<br><tt><font size=3D2>&gt; is IMHO a great progress not to be lost).<br>
&gt; - Unless I misunderstand, the draft doesn't completely describe what
happens </font></tt>
<br><tt><font size=3D2>&gt; to 6to4 addresses that have non 0 SLA-ID after
their embedded IPv4 addresses. <br>
</font></tt>
<br><tt><font size=3D2>Remi, </font></tt>
<br><tt><font size=3D2>On this regards, please have a look at the following
draft, it describes in &nbsp;</font></tt>
<br><tt><font size=3D2>more details how the addressing is affected (this
draft is not available as</font></tt>
<br><tt><font size=3D2>an ID, we're sorry but we missed the submission dead=
line):</font></tt>
<br>
<br>
<br>
<br>
<br><tt><font size=3D2>&gt; - The requirement of a Customer opt-out introdu=
ces
significant complexity. <br>
&gt; Regards,<br>
&gt; RD<br>
</font></tt>
<br><font size=3D2 face=3D"sans-serif">JFT</font>
--=_alternative 004B6168852577C2_=--
--=_mixed 004B6168852577C2_=
Content-Type: text/plain; name="draft-tremblay-pt66ac-00.txt"
Content-Disposition: attachment; filename="draft-tremblay-pt66ac-00.txt"
Content-Transfer-Encoding: quoted-printable




Behavior Engineering for Hindrance                           J. Tremblay
Avoidance                                                      Videotron
Internet-Draft                                                 S. Beuker
Intended status: Standards Track                     Shaw Communications
Expires: April 21, 2011                                 October 18, 2010


    Addressing bit compression for stateless IPv6 prefix translation
                        draft-tremblay-pt66ac-00

Abstract

   This document describes a method to extend IPv6 prefix translation
   [NAT66] to statelessly translate between IPv6 prefixes of differing
   lengths.  This technique, called PT66 addressing bit compression
   (PT66-AC), provides a way to map a shorter prefix (such as the fixed
   [6to4] prefix) to a longer global unicast prefix, while avoiding
   stateful translation.  The difference between the prefix lengths is
   compensated for by removing an unused string of subnetting bits, as
   specified, from the addresses within the shorter prefix.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 21, 2011.

Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the
   document authors.  All rights reserved.



Tremblay & Beuker        Expires April 21, 2011                 [Page 1]
=0C
Internet-Draft                   PT66-AC                    October 2010


   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  IPv6 Translator Model  . . . . . . . . . . . . . . . . . . . .  3
   3.  IPv6 Prefix Translation with Addressing Compression  . . . . .  5
     3.1.  Configuration Elements . . . . . . . . . . . . . . . . . .  6
     3.2.  Egress Translation Behavior for Compressed Bits  . . . . .  7
     3.3.  Ingress Translation Behavior for Compressed Bits . . . . .  7
     3.4.  Translator Operation . . . . . . . . . . . . . . . . . . .  7
       3.4.1.  Egress Traffic Operation . . . . . . . . . . . . . . .  7
       3.4.2.  Ingress Traffic Operation  . . . . . . . . . . . . . .  8
   4.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . . .  8
     4.1.  6to4 Subnet Compression  . . . . . . . . . . . . . . . . .  8
     4.2.  6to4 IPv4 and Subnet Compression . . . . . . . . . . . . .  9
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 11
   7.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12
   8.  Informative References . . . . . . . . . . . . . . . . . . . . 12
   Appendix A.  An Appendix . . . . . . . . . . . . . . . . . . . . . 12
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12




















Tremblay & Beuker        Expires April 21, 2011                 [Page 2]
=0C
Internet-Draft                   PT66-AC                    October 2010


1.  Introduction

   Since IPv6 has become a standard, multiple transition mechanisms have
   been proposed to stimulate the rate of IPv6 adoption.  Some of these
   mechanisms use specific addressing space and fixed lengths for
   different types of prefixes.  There is sometimes a need to translate
   a protocol-specific addressing space into global unicast space to
   improve the routing behavior.  Of course, this improvement to routing
   comes at the cost of lowered interoperability for some applications.

   One issue with translating these prefixes is the challenge of
   obtaining a globally unique prefix of appropriate size.  However,
   there are often a number of bits rarely used within the transition
   protocol specific prefixes.  Using an address translator with
   addressing bit compression allows a deployment to drop these unused
   bits and make more efficient usage of the public addressing space.

   For example, the IPv6 transition protocol [6to4] statelessly maps 32
   bit IPv4 addresses into the 2002::/16 prefix, to create a /48 IPv6
   prefix for every IPv4 address.  Normally, return traffic destined to
   this prefix will be routed to the nearest 6to4 relay router.  An ISP
   may wish to gain control over return routing of the 6to4 traffic by
   mapping their 6to4 address space into a globally unique IPv6 prefix.

   Implementing this without addressing bit compression would require an
   IPv6 /32 for every /16 of IPv4 global space assigned to an ISP.
   Acquiring the required IPv6 space from a Regional Internet Registry
   is therefore unrealistic in most cases.  Using addressing bit
   compression, an ISP can make better use of the globally unique IPv6
   space by reducing the size of the 6to4 subnet available to each user.


2.  IPv6 Translator Model

   The current stateless IPv6 prefix translation model is described in
   [NAT66].  In that model, IPv6 traffic is translated between an
   internal network and an external network.














Tremblay & Beuker        Expires April 21, 2011                 [Page 3]
=0C
Internet-Draft                   PT66-AC                    October 2010


   An IPv6 translator model described in [NAT66]:

           External Network:  Prefix =3D 2001:0DB8:0001:/48
               --------------------------------------
                                 |
                                 |
                            +---------+
                            |  PT66   |
                            |  Device |
                            +---------+
                                 |
                                 |
               --------------------------------------
           Internal Network:  Prefix =3D FD01:0203:0405:/48


   This translation model may be represented in a generic fashion by
   replacing the address characters with letters denoting the function
   of those address bits.  The representation below describes a single
   translation mapping in a device that may implement several.

      L - Internal (or "Local") network IPv6 prefix

      E - External network IPv6 prefix

      N - Subnet bits

      I - Interface Identifier (IID) bits

   A generic IPv6 translator model

   External Network Prefix =3D EEEE:EEEE:EEEE:NNNN:IIII:IIII:IIII:IIII
               --------------------------------------
                                 |
                                 |
                            +---------+
                            |  PT66   |
                            |  Device |
                            +---------+
                                 |
                                 |
               --------------------------------------
   Internal Network Prefix =3D LLLL:LLLL:LLLL:NNNN:IIII:IIII:IIII:IIII


   In this figure, L represents the Internal or Local prefix to be
   translated to the External prefix bits E. The number of L bits is
   equal to the number of E bits.  Subnet bits N and Interface-ID bits I



Tremblay & Beuker        Expires April 21, 2011                 [Page 4]
=0C
Internet-Draft                   PT66-AC                    October 2010


   are not changed by the translator.


3.  IPv6 Prefix Translation with Addressing Compression

   It is implicit that any basic [NAT66] mapping must be between
   prefixes of the same size, as each prefix of is overwritten by the
   other as traffic passes through.  The section below gives a
   description of how to map internal and external networks of different
   lengths.  In this example, the internal prefix used is a larger /28,
   while the external prefix used is a smaller /40.

      L - Local or Internal network IPv6 prefix

      E - External network IPv6 prefix

      S - Shifted subnet bits

      N - Unmodified subnet bits

      C - Compressed (removed) bits

      I - Interface Identifier (IID) bits

   Generic Prefix Translator Model with Addressing Compression

   External Network Prefix =3D EEEE:EEEE:EESS:SSSN:IIII:IIII:IIII:IIII
               --------------------------------------
                                 |
                                 |
                            +----------+
                            |  PT66-AC |
                            |  Device  |
                            +----------+
                                 |
                                 |
               --------------------------------------
   Internal Network Prefix =3D LLLL:LLLS:SSSS:CCCN:IIII:IIII:IIII:IIII


   In this translation model, the N bits (4 bits represented) from the
   internal subnet are left untouched.  The C bits (12 bits represented)
   are the compressed bits, not present in the external network prefix.
   The S bits (20 bits represented) are bitwise shifted to the right by
   the length of the C bits when translating from the internal network
   to the external network.  This compression of the subnet allows for
   the adaptation from the larger prefix to the smaller prefix to be
   made.  The L bits (28 bits represented) are replaced by the E bits



Tremblay & Beuker        Expires April 21, 2011                 [Page 5]
=0C
Internet-Draft                   PT66-AC                    October 2010


   (40 bits represented) when translating from the internal network to
   the external network.

   In this document, traffic received on the internal network interface
   and forwarded by the external traffic interface is called egress
   traffic.  Inversely, any traffic received on the external network
   interface and forwarded to the internal network interface is called
   ingress traffic.

3.1.  Configuration Elements

   The IPv6 prefix translation with addressing compression model
   (PT66-AC) makes use of the following variables:

      L Length of the internal network prefix

      E Length of the external network prefix

      S Number of shifted bits

      C Number of compressed bits

      N Number of unchanged subnet bits

   In order to avoid confusion and increase readability, both the full
   name and variable notation of the above parameters are used
   throughout this document.

   In this translation model, the sum of the length of the internal
   network prefix (L), of the number of shifted bits (S), of the number
   of compressed bits (C) and of the number of unchanged bits (N) always
   equals 64 (L + S + C + N =3D 64).  As well, the sum of the length of
   the external network (E), of the number of shifted bits (S) and of
   the number of unchanged bits (N) always equals 64 (E + S + N =3D 64).

   Hence the number of compressed bits (C) is always equal to the length
   of the external prefix minus the length of the local prefix (C =3D E -
   L).  Only the length of each prefix need be defined, and the length
   of the compressed bits (C) can be derived from those values.
   Similarly, in order to know the number of shifted bits (S) and
   unchanged bits (N), one of these two must be defined in the
   configuration of the translation mapping.  Therefore, the elements
   that must be defined in a translation mapping with compression are
   the internal network prefix and its length (L), the external network
   prefix and its length (E) and either the number of shifted bits (S)
   or unchanged bits (N).

   With these configuration elements defined for each translation



Tremblay & Beuker        Expires April 21, 2011                 [Page 6]
=0C
Internet-Draft                   PT66-AC                    October 2010


   mapping, an IPv6 translator can statelessly translate ingress and
   egress traffic between prefixes of differing length.

3.2.  Egress Translation Behavior for Compressed Bits

   The value of the bits compressed is hereto referred to as the
   'compressed bit pattern'.  By default, any egress traffic MUST be
   dropped if the compressed bit pattern is not equal to zero.
   Optionally, a compressed bit pattern different from all zeros may be
   defined by configuration and used to filter incoming traffic.  The
   compressed bit pattern length MUST be equal to the difference between
   the length of the external prefix and the length of the internal
   prefix (C must equal E - L).

   The translation device SHOULD issue an ICMP type 1 (Destination
   Unreachable) message with code 5 (Source address failed ingress/
   egress policy) to the source address when dropping traffic for the
   first time for each source address/destination address pair.

3.3.  Ingress Translation Behavior for Compressed Bits

   For traffic entering the external network interface of the
   translator, the compressed bits MUST be restored with zeros by
   default, unless a different compressed bit pattern has been
   configured for the mapping.  In such a case, the user-defined
   compressed bit pattern MUST be used to restore the compressed bits.

3.4.  Translator Operation

   For traffic entering the external network interface of the
   translator, the compressed bits MUST be restored with zeros by
   default, unless a different compressed bit pattern has been
   configured for the mapping.  In such a case, the user-defined
   compressed bit pattern MUST be used to restore the compressed bits.

3.4.1.  Egress Traffic Operation

   For each egress packet, the prefix translator MUST use the
   appropriate translation mapping with the longest matching internal
   prefix.  The S bits of the IPv6 source address are shifted bitwise to
   the right by the number of compressed bits (C).  The leftmost bits of
   the source address (L) are replaced by the bits of the external
   network prefix (E).  Unchanged bits (N) of the source address MUST
   NOT be modified.







Tremblay & Beuker        Expires April 21, 2011                 [Page 7]
=0C
Internet-Draft                   PT66-AC                    October 2010


3.4.2.  Ingress Traffic Operation

   For each ingress packet, the prefix translator MUST use the
   appropriate translation mapping.  Selection of the appropriate
   mapping is outside of the scope of this document.  The behavior of
   the translator when no mapping is matched is also out of scope for
   this document.  Asynchronous mappings between internal and external
   prefixes, where an ingress source address translated does not in turn
   translate back to the same destination address on egress traffic,
   SHOULD be prevented.

   Once a suitable mapping is found, the leftmost bits of the
   destination address are replaced by the corresponding bits from the
   local network prefix (L).  Starting at the bit position equal to the
   length of the external prefix (E), the Shifted bits are bitwise
   shifted to the left by the number of compressed bits (C).  The C bits
   are restored with zeros, or the compressed bit pattern if set in the
   mapping configuration.  Unchanged bits (N) of the destination address
   MUST NOT be modified.


4.  Examples

4.1.  6to4 Subnet Compression

   When an IPv6 prefix translator is used with a 6to4 prefix as the
   internal network, it is possible to compress seldom-used subnet bits
   in order to reduce the size of the external global unicast prefix.
   As specified in [6to4], a 6to4 router will define a /48 for each IPv4
   global unicast address.  This provides 16 bits of subnet addressing
   available to the user.  The 6to4 protocol being often implemented by
   residential gateways, only one LAN subnet (/64) is utilized in most
   implementations.  It is therefore possible to reduce the number of
   available /64 subnets available from 65536 (16 bits) to 16 (4 bits)
   or even a single one (0 subnet bits).  The following example
   compresses the 16 subnet bits to 4 bits, leaving room for 16 /64
   subnets.

   The prefix translation model for 6to4 is similar to the generic
   model, with the internal network bits (L) being defined as 2002::/16.
   The 32 bits of the 6to4 router IPv4 address are the shifted bits (S).

   This example uses 192.0.2.1 as the 6to4 router IPv4 address and 2001:
   DB0::/28 as the provider global unicast prefix.  A single subnet
   number 0001 is used.  A single host exchanges traffic from Interface
   ID ::A.





Tremblay & Beuker        Expires April 21, 2011                 [Page 8]
=0C
Internet-Draft                   PT66-AC                    October 2010


   External Network Prefix =3D EEEE:EEES:SSSS:SSSN:IIII:IIII:IIII:IIII
                             2001:0DBC:0000:2011:0000:0000:0000:000A
               --------------------------------------
                                 |
                                 |
                            +----------+
                            |  PT66-AC |
                            |  Device  |
                            +----------+
                                 |
                                 |
               --------------------------------------
   Internal 6to4 Prefix =3D LLLL:SSSS:SSSS:CCCN:IIII:IIII:IIII:IIII
                          2002:C000:0201:0001:0000:0000:0000:000A


   In this example, the ISP configures the PT66-AC with the following
   mapping: 2002::/16, 2001:DB0::/28, C=3D12 (or N=3D4)

   During operation, egress traffic from address 2002:C000:0201:1::A is
   translated as follow:

   2002:C000:0201:0001::A  Egress packets source address
   2002:C00C:0000:2011::A  Shift S bits (32 bits) to the right
                           by C bits (12 bits)
   2001:0DBC:0000:2011::A  Replace L bits by E bits. This is the new
                           egress source address.

   The inverse operations takes place for ingress traffic with
   destinations within 2001:db0::/28:

   2001:0DBC:0000:2011::A  Incoming destination address
   2002:0DBC:0000:2011::A  Leftmost bits are replaced by the L bits
                           (16 bits)
   2002:C000:0201:2011::A  The 32 S bits are shifted to the left
                           by C bits (12 bits)
   2002:C000:0201:0001::A  The C bits are restored. This is the new
                           destination address on the local network

   This example demonstrated how to compress the 12 first bits of the
   6to4 subnet bits in order for an ISP to use a longer global unicast
   prefix for the external network.

4.2.  6to4 IPv4 and Subnet Compression

   As an improvement over the previous example, the ISP also has the
   opportunity to compress the IPv4 prefix part of the IPv4 address in
   the 6to4 prefix.  That information is redundant, because it can be



Tremblay & Beuker        Expires April 21, 2011                 [Page 9]
=0C
Internet-Draft                   PT66-AC                    October 2010


   recovered from the mapping when translating ingress traffic.
   Omitting this allows the ISP to use an even smaller prefix on the
   external interface.

   This example is similar the previous one, with the addition that the
   IPv4 prefix 192.0.2.0/24 will also be compressed.  The external
   prefix used by the ISP is now 2001:db8:FFFF:F000::/52.  The 6to4
   subnet remains compressed from 16 to 4 bits.

   A translation mapping is configured as follow: 2002:C000:0200::/40,
   2001:0DB8:FFFF:F000::/52, C=3D12 (or N=3D4)

   External Network Prefix =3D EEEE:EEEE:EEEE:ESSN:IIII:IIII:IIII:IIII
                             2001:0DB8:FFFF:F011:0000:0000:0000:000A
               --------------------------------------
                                 |
                                 |
                            +----------+
                            |  PT66-AC |
                            |  Device  |
                            +----------+
                                 |
                                 |
               --------------------------------------
   Internal 6to4 Prefix =3D LLLL:LLLL:LLSS:CCCN:IIII:IIII:IIII:IIII
                          2002:C000:0201:0001:0000:0000:0000:000A



   Egress operation:

   2002:C000:0201:0001::A  Egress packets source address
   2002:C000:0201:0011::A  Shift S bits (8 bits) to the
                           right by C bits (12 bits)
   2001:0DB8:FFFF:F011::A  Replace L bits by E bits. This
                           is the new egress source address.















Tremblay & Beuker        Expires April 21, 2011                [Page 10]
=0C
Internet-Draft                   PT66-AC                    October 2010


   Ingress operation for destinations within 2001:db8:FFFF:F000::/52:

   2001:0DB8:FFFF:F011::A  Incoming destination address
   2002:C000:02FF:F011::A  Leftmost bits are replaced
                           by the L bits (40 bits)
   2002:C000:0201:F011::A  The S bits (8 bits) are shifted to
                           the left by C bits (12 bits)
   2002:C000:0201:0001::A  The C bits are restored. This is the
                           new destination address on local network

   This example demonstrates that both the IPv4 addressing and the
   subnet parts of a 6to4 prefix can be compressed.  It is therefore
   possible to translate a provider's own 6to4 addressing subset (from
   its own global IPv4 unicast space) to a set of global IPv6 unicast
   prefixes that are small enough not to require an extremely large IPv6
   global unicast assignment.

   The resulting IPv6 unicast prefixes are also completely decoupled
   from IPv4 and avoid the need for injection of IPv4 routing
   information in the IPv6 routing table in order to achieve better
   routing.


5.  IANA Considerations

   This document makes no request of IANA.

   Note to RFC Editor: this section may be removed on publication as an
   RFC.


6.  Security Considerations

   All of the security considerations of [NAT66] are still applicable
   when address bit compression is applied.  The stateless address
   mapping of NAT66 allows for direct inbound connections to internal
   nodes, something not present in NAT44.

   In addition, an implementation of NAT66 with addressing bit
   compression must be aware of the potential for a DOS attack against
   the device by an internal node intentionally sending packets that do
   not match the compressed bit pattern.  This would force the
   generation of ICMP unreachable messages to the source address, which
   could be spoofed, and could potentially impact the operation of both
   the NAT66 device and the legitimate user of the spoofed source
   address.  For this reason, it is recommended that the rate of ICMP
   unreachable messages generated is limited.




Tremblay & Beuker        Expires April 21, 2011                [Page 11]
=0C
Internet-Draft                   PT66-AC                    October 2010


   Another possibility of resource exhaustion is to receive packets on
   an interface that doesn't have any mapping for the source or
   destination.  For example, traffic with an internal destination
   coming on the outside interface.  Such traffic SHOULD be silently
   dropped.


7.  Acknowledgements

   Thanks to the following people (in alphabetical order) for their
   participation and review:

      Victor Kuarsingh, Rogers Communications

      Yiu Lee, Comcast


8.  Informative References

   [NAT66]  Wasserman, M. and F. Baker, "IPv6-to-IPv6 Network Address
            Translation (NAT66)", November 2008.


Appendix A.  An Appendix


Authors' Addresses

   Jean-Francois Tremblay
   Videotron
   150 Beaubien Ouest
   Montreal, Quebec  H2V 1C4
   Canada

   Email: jf@jftremblay.com


   Scott Beuker
   Shaw Communications
   200 - 3636 23rd St NE
   Calgary, Alberta  T2E 8Z5
   Canada

   Email: Scott.Beuker@sjrb.ca







Tremblay & Beuker        Expires April 21, 2011                [Page 12]
=0C
--=_mixed 004B6168852577C2_=--

From Jean-Francois.TremblayING@videotron.com  Wed Oct 20 07:12:18 2010
Return-Path: <Jean-Francois.TremblayING@videotron.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C0E563A682D; Wed, 20 Oct 2010 07:12:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.245
X-Spam-Level: 
X-Spam-Status: No, score=-1.245 tagged_above=-999 required=5 tests=[AWL=1.353,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zdX1sEVb6--p; Wed, 20 Oct 2010 07:12:14 -0700 (PDT)
Received: from mx02.videotron.com (mx02.videotron.com [24.201.243.151]) by core3.amsl.com (Postfix) with ESMTP id 86F233A680F; Wed, 20 Oct 2010 07:12:14 -0700 (PDT)
In-Reply-To: <m24ochl8uj.wl%randy@psg.com>
To: IPv6 Operations <v6ops@ietf.org>, v6ops-bounces@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006
Message-ID: <OF9DF5D797.F506E6B7-ON852577C2.004B643C-852577C2.004E26A7@videotron.com>
From: Jean-Francois.TremblayING@videotron.com
Date: Wed, 20 Oct 2010 10:13:33 -0400
X-MIMETrack: Serialize by Router on DOMMTL11/SRV/GVL(Release 7.0.2FP1|January 10, 2007) at 2010-10-20 10:13:37, Serialize complete at 2010-10-20 10:13:37
Content-Type: multipart/alternative; boundary="=_alternative 004E26A5852577C2_="
Subject: Re: [v6ops] I-D	Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 14:12:19 -0000

Message en plusieurs parties au format MIME
--=_alternative 004E26A5852577C2_=
Content-Type: text/plain; charset="US-ASCII"

>> My humble perspective, speaking strictly for myself here, is that any
>> ISP (not just your employer, but any ISP) that is really concerned
>> about consumer experience of IPv6 would do better to deploy IPv6 and
>> manage it the same way it manages IPv4 traffic than to try to manage
>> the way its customers work around the lack of native support.

> yesssssssssss! 
> bleeping brilliantly said.  thank you.
> randy

Right, we are all in violent agreement that native IPv6 is the way to go. 

All the ISPs who support 6to4-PMT also strive to deploy native 
IPv6 in their network in a timely fashion. However, the hard reality 
is that vendor support is often lacking and/or prohibitivly 
expensive (like replacing the equipment with the latest one). 

So let me return the question to my favorite vendor (first poster in
this mail). When can I get the IPv6 features I need to deploy 
IPv6 natively? Oh, and btw, I need that to be cheap, no hardware 
upgrades please. 
The bottom line is that most vendors support for real-life deployment 
is late and we have to live with 6to4 being deployed now with 
a sub-optimal number of relays. Even if 6to4-PMT breaks e2e, it 
still provides IMHO for a better user experience in many cases, 
until native is available at every doorstep. (or 6RD as a temporary 
step toward native). 

We've all heard several times complaints about the lack of 
operator participation at the the IETF. Well, the last posts 
from Victor, Lee and Bill were real feedback from operators
feeling the pain of pushing IPv6 deployement on a daily basis
and trying to come up with actual implementable solutions. 

/JFT
--=_alternative 004E26A5852577C2_=
Content-Type: text/html; charset="US-ASCII"


<br>
<br>
<br><tt><font size=2>&gt;&gt; My humble perspective, speaking strictly
for myself here, is that any<br>
&gt;&gt; ISP (not just your employer, but any ISP) that is really concerned<br>
&gt;&gt; about consumer experience of IPv6 would do better to deploy IPv6
and<br>
&gt;&gt; manage it the same way it manages IPv4 traffic than to try to
manage<br>
&gt;&gt; the way its customers work around the lack of native support.<br>
<br>
&gt; yesssssssssss! &nbsp;<br>
&gt; bleeping brilliantly said. &nbsp;thank you.<br>
&gt; randy</font></tt>
<br>
<br><tt><font size=2>Right, we are all in violent agreement that native
IPv6 is the way to go. </font></tt>
<br>
<br><tt><font size=2>All the ISPs who support 6to4-PMT also strive to deploy
native </font></tt>
<br><tt><font size=2>IPv6 in their network in a timely fashion. However,
the hard reality </font></tt>
<br><tt><font size=2>is that vendor support is often lacking and/or prohibitivly
</font></tt>
<br><tt><font size=2>expensive (like replacing the equipment with the latest
one). </font></tt>
<br>
<br><tt><font size=2>So let me return the question to my favorite vendor
(first poster in</font></tt>
<br><tt><font size=2>this mail). When can I get the IPv6 features I need
to deploy </font></tt>
<br><tt><font size=2>IPv6 natively? Oh, and btw, I need that to be cheap,
no hardware </font></tt>
<br><tt><font size=2>upgrades please. &nbsp;</font></tt>
<br><tt><font size=2>The bottom line is that most vendors support for real-life
deployment </font></tt>
<br><tt><font size=2>is late and we have to live with 6to4 being deployed
now with </font></tt>
<br><tt><font size=2>a sub-optimal number of relays. Even if 6to4-PMT breaks
e2e, it </font></tt>
<br><tt><font size=2>still provides IMHO for a better user experience in
many cases, </font></tt>
<br><tt><font size=2>until native is available at every doorstep. (or 6RD
as a temporary </font></tt>
<br><tt><font size=2>step toward native). </font></tt>
<br>
<br><tt><font size=2>We've all heard several times complaints about the
lack of </font></tt>
<br><tt><font size=2>operator participation at the the IETF. Well, the
last posts </font></tt>
<br><tt><font size=2>from Victor, Lee and Bill were real feedback from
operators</font></tt>
<br><tt><font size=2>feeling the pain of pushing IPv6 deployement on a
daily basis</font></tt>
<br><tt><font size=2>and trying to come up with actual implementable solutions.
</font></tt>
<br>
<br><font size=2 face="sans-serif">/JFT</font>
--=_alternative 004E26A5852577C2_=--

From cb.list6@gmail.com  Wed Oct 20 07:22:43 2010
Return-Path: <cb.list6@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BD2C83A69C3 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 07:22:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=0.450,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fyA2tj3Zkec5 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 07:22:42 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id 67D603A683E for <v6ops@ietf.org>; Wed, 20 Oct 2010 07:22:42 -0700 (PDT)
Received: by qyk27 with SMTP id 27so1478643qyk.10 for <v6ops@ietf.org>; Wed, 20 Oct 2010 07:24:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=day+vG5gllHHkFgDKwYm2vtm+BU/lHjjc9sv3JbqNvI=; b=BwVGtKD3U5xrDZOPXjJaUQnE5q6kqJ/T99wqi/eND9w0Ynk0if7tAhEplJs99xyVKk N76Bz6kMcPD7wYAn9OruptSBXWmJRwetzjaTa0FRgDjBIlLNuNiWI7WWgBbAKjmESlEK zJUnuUf3/uJcgpc4tNUnkLSmNRhYJTJU+Bfsw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=VR8nuC36qA1+u4B3qfcOrHw8g4SeInxYKuz6PGlC35A5lDK4A2vHIOPAMKJ7DTc/EK o3ZLbWOzSrP+9LXj4GDg5MpAAlh8viDlZB7Cc/jhTLDU29Yy6kXMgO0dKyGwDf7DIdHS wLGY1G/jT4Jz8U4TgB/rcMQ4suV3OhDQLDmZ4=
MIME-Version: 1.0
Received: by 10.229.245.4 with SMTP id ls4mr774724qcb.32.1287584655350; Wed, 20 Oct 2010 07:24:15 -0700 (PDT)
Received: by 10.229.245.201 with HTTP; Wed, 20 Oct 2010 07:24:14 -0700 (PDT)
In-Reply-To: <E71300B9B9041340B238540990BF04530914BB4D8E@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM>
References: <20100922151502.E21FF3A6952@core3.amsl.com> <4CBE0F32.8000504@gmail.com> <E71300B9B9041340B238540990BF04530914BB4CCF@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <ECD91250-8817-4746-ABC2-ED9CDFDFF82D@cisco.com> <12A4FA46AA7DA94A8FDBE2C945E1BF62016D414D@CL08MBC.rci.rogers.ca> <56EBC452-7E33-4BC9-AD27-AEF4806F8886@cisco.com> <4CBE3974.5020806@cernet.edu.cn> <E71300B9B9041340B238540990BF04530914BB4D8E@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM>
Date: Wed, 20 Oct 2010 07:24:14 -0700
Message-ID: <AANLkTinAoKowKO9AZjKuWn9ixZv5LRk0xkDOFdv+Wboh@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>, "draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org" <draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org>, "Lee, Yiu" <Yiu_Lee@cable.comcast.com>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 14:22:43 -0000

On Tue, Oct 19, 2010 at 11:53 PM, Armstrong, Bill R
<Bill.Armstrong@chartercom.com> wrote:
> I also agree with Fred, Native is the win and is undoubtedly the goal. So=
rry if I was bit confrontational earlier, but let's be honest at present th=
ere are very few customers asking for IPv6, the vast majority of IP enabled=
 consumer electronics (non-PCs) are IPv4 only, and the lack of US-based IPv=
6 content doesn't exactly foster the kind of "rah-rah-lets-go-spend-a-fortu=
ne-to-replace-N-million-IPv4-only-CPE" attitude, engineer types would hope =
to see from the business.

 -> I have said it several times on this list, but it keeps coming up.
 There is a lot of "potential" IPv6 traffic on your network.  Take all
the Google, Youtube, Facebook, Netflix traffic.  Add those all
together and tell me what percent bandwidth they are on your network.
That is IPv6 content available today.  Now add in the IPv6 "saber
rattlers" like Yahoo and the US Gov't.  Reach a tipping point yet?  I
have.


So if there is a relatively quick and cost effective way for an ISP to
provide an improved IPv6 experience right out of the gate, despite it
not being Native, shouldn't it, at the very least be considered?
Particularly when the alternative is simply waiting for
6rd\DS-lite\Native capable CPE or taking no action whatsoever(time is
of the essence, no?).
>
> Another thing that I think needs to be considered is that every day for a=
 subset of IPv6 internet users, legitimately impaired IPv6 service exists, =
and some fraction of those users has their crummy IPv6 experience recorded =
and reported on. These metrics and others

->FUD.  I have 6RD at home (thanks Comcast), ISATAP at work (thanks
MSFT for making this easy) and IPv6-only 3G + NAT64 on my mobile
(thanks T-Mobile USA).  I have IPv6 everywhere, and i have NEVER had
an IPv6 related network issue.  NEVER.  I hear people on Macs
sometimes have issues, i don't have a Mac.  Most people don't have
Macs.

 like them are the same metrics that will influence the data used in
the decision making process by countless organizations, be they
Enterprises, ISPs or Content Providers to help determine when they
feel they should take the IPv6 plunge. And for those organization that
are perfectly happy with their single /24 and gobs of NAT what reason,
based on those underperforming IPv6 metrics, would they have to even
request\enable Dual-Stacked or Native service from their provider? I'm
not trying to say that 6to4 relay users influence the lions-share of
the IPv6 internet use statistics, I'm sure their far from it, what I
am saying is that from a purely altruistic-geek perspective, isn't
anything that will help signal and allow for the adoption of v6 on a
broader scale as well as help to provide improved internet performance
what we're all after?
>
>
>

We all agree that customers dont care about ipv4 or ipv6, right?  So
why bother with these hacks that don't actually help you grow your
edge or deploy real IPv6?  It all seems like just a distraction to me.
 Is it just trying to be a good citizen to help get the community some
more short-term mileage out of the (too little, too late) dual-stack
transition strategy for the Internet?

If you have business case for user experience with IPv6 ... then you
should be doing dual-stack.  If you are running out of addersses, you
should do DS-lite. If you don't have a business case ....

Cameron

From victor.kuarsingh@gmail.com  Wed Oct 20 08:06:40 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E6CD23A6847 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 08:06:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.849
X-Spam-Level: 
X-Spam-Status: No, score=-1.849 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J6pdl3+40xDx for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 08:06:39 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 80B843A69C3 for <v6ops@ietf.org>; Wed, 20 Oct 2010 08:06:39 -0700 (PDT)
Received: by vws12 with SMTP id 12so2192291vws.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 08:08:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=Zc53kfbVRALDDsiJZh9xNuaRjU1sWjsa2Xx4oTwcihE=; b=qxpoegqnEZ0aQDfrEQsYw08KeHtxivn3uwPpABiUdCPMhNwyIBk5CynmPJo1eBJu7m oc63IzqTKPmZArRI1zB/ItiWQnsH5M12yzI0Uc2PO66+CRlnV8l61Nzo73IEIyW61/7q urQaQBHFfMbqPQnaA+TRMyMtLqvga66omr+tg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=gjtubKpZobD0dVgxgU0uuz7wmJwYHGX5RSva1XjzFyxZTqjTAPC3IAHqiOXpd0Rh7m EMIncBXffmLaJJ9/fpXlLt2c69LkANv+xAnxTKqjE+Lc2Vp9JGeJT1TFsLCcwnrJnqYf I5IJkWpa4pTL1snG2WJQI3mDeOBOBQJFgb+fo=
Received: by 10.220.85.19 with SMTP id m19mr2180047vcl.77.1287587292377; Wed, 20 Oct 2010 08:08:12 -0700 (PDT)
Received: from [172.28.172.161] ([65.91.54.2]) by mx.google.com with ESMTPS id o17sm146399vbi.12.2010.10.20.08.08.09 (version=SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 08:08:11 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Wed, 20 Oct 2010 08:08:04 -0700
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: =?ISO-8859-1?B?UultaQ==?= =?ISO-8859-1?B?IERlc3By6XM=?= <remi.despres@free.fr>, "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
Message-ID: <C8E453E4.10274%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: ActwaJgLU8R3McuUo0+R6CG3aNqg9w==
In-Reply-To: <77479F2A-0939-4BD1-8DB7-7D62B20E4159@free.fr>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>, "draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org" <draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org>, "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>, Victor Kuarsingh <victor.kuarsingh@rci.rogers.com>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 15:06:41 -0000

Remi,

Yes, the e2e transparency loss is of consideration (subject to further test
on impact).

In our testing we found that most in the wild equipment which turns on 6to4
sets the SLA-ID to "0".  Therefore the opt-in is not doing anything (6to4
has just turned itself on automatically).

The opt-out would be setting the SLA-ID to anything by "0" or perhaps "1"
(since 1 is found as the SLA-ID on a few other defaults).

This is only targeted at people of have default settings on their equipment
and no knowledge of IPv4, IPv6 etc.

In the use case where a provider may have turned on NAT44/LSN (NAT444) and
used public IP space (which now breaks auto 6to4), the loss of e2e may not
be as bad as broken 6to4.

Again, I would like to stress, this is just an option to complete the whole
strategy (which is put out IPv6).

Victor


On 20/10/10 1:20 AM, "R=E9mi Despr=E9s" <remi.despres@free.fr> wrote:

> =20
> Le 20 oct. 2010 =E0 05:23, Lee, Yiu a =E9crit :
>=20
>=20
>> ... However, using this technique can improve the customer experience da=
y
>> one.
>=20
> To some extent, it might (and, from a strictly technical point of view, t=
he
> idea is neat), but:
> - Providers that would support it would, for their customers, BREAK the e=
2e
> transparency (that IPv6 has so far restored in the Internet, and that is =
IMHO
> a great progress not to be lost).
> - Unless I misunderstand, the draft doesn't completely describe what happ=
ens
> to 6to4 addresses that have non 0 SLA-ID after their embedded IPv4 addres=
ses.
> - The requirement of a Customer opt-out introduces significant complexity=
.
>=20
> Regards,
> RD
>=20
>=20
>=20
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops



From victor.kuarsingh@gmail.com  Wed Oct 20 08:13:36 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A4F03A681F for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 08:13:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.924
X-Spam-Level: 
X-Spam-Status: No, score=-1.924 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42fIJSywNLoA for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 08:13:32 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by core3.amsl.com (Postfix) with ESMTP id C3AF13A681E for <v6ops@ietf.org>; Wed, 20 Oct 2010 08:13:28 -0700 (PDT)
Received: by pzk30 with SMTP id 30so259331pzk.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 08:15:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=yWw0+KRFGAQY5M2TYinq9itooU1RhFIWFjy8ggaN2X4=; b=D2jxNddn3IyhtVCcOSHbdm7sVAIaGP41hN02hRoaZxZ/yk72XLlfcW3II2yKDzNLgs N16tuUg1a89cjpkHqrFiXFqydqySGS7/Cl2bjSbBrMs4c87Zl8jtgvkkepPJLRHPGXIT /+CaTMLE5Xddbo6yHp+kaQ9SdGaz3C0oxytxQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=agffDmblWzTCG6q7u5CXeVh8NpHYKWPzIzGlUXq6b6T6YHBqEP31YAuuRhUVDU4N2i Y8Ei82sVJB1BCAVnU/szMrXQjkjan4petT4ANXBmgmvZE1xqJUF3DQAkz+k83PFoVli/ RTNzkj9rslC2+XA7uvgr4cTmfZZS6wD/zQG+M=
Received: by 10.142.186.13 with SMTP id j13mr5966549wff.76.1287587697308; Wed, 20 Oct 2010 08:14:57 -0700 (PDT)
Received: from [172.28.172.161] ([65.91.54.2]) by mx.google.com with ESMTPS id y8sm109594vch.5.2010.10.20.08.14.55 (version=SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 08:14:56 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Wed, 20 Oct 2010 08:14:52 -0700
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: Cameron Byrne <cb.list6@gmail.com>, "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>
Message-ID: <C8E4557C.10277%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: ActwaYs7kVYAGws/XUSRO+OWWq78+Q==
In-Reply-To: <AANLkTinAoKowKO9AZjKuWn9ixZv5LRk0xkDOFdv+Wboh@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, "draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org" <draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org>, "Lee, Yiu" <Yiu_Lee@cable.comcast.com>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 15:13:37 -0000

Cameron,

I agree, we will push out IPv6 native... But the ability to push it out
depends on the access network type, business model etc.  In our mobile
network, it's much easier since we influence (to some extent) what
phones/devices go out there.  The work you have done in this area is great
and we like the path that has been set forth.  I would however argue that
most of the phones in my network do not currently support IPv6 (so that a
bit challenge for us.. But a separate topic)

On the other hand, Wireline access is a different kettle of fish.  Not all
endpoints are managed (which means we don't control what on it and what
functions it has).  I am playing poker with the cards I am delta.  I can't
play for a full house with three different suits.

Yes, this is stop gap measure, which is easy to put in, and very low touch.
I can put it out there fast, cheap and without changing much in the network
(some routes).  We continue to dedicate the lion share of our resources to
IPv6 deployment.  This again is not an either or situation.. It's a part of
the big mix.

Regards,




On 20/10/10 7:24 AM, "Cameron Byrne" <cb.list6@gmail.com> wrote:

> On Tue, Oct 19, 2010 at 11:53 PM, Armstrong, Bill R
> <Bill.Armstrong@chartercom.com> wrote:
>> I also agree with Fred, Native is the win and is undoubtedly the goal. Sorry
>> if I was bit confrontational earlier, but let's be honest at present there
>> are very few customers asking for IPv6, the vast majority of IP enabled
>> consumer electronics (non-PCs) are IPv4 only, and the lack of US-based IPv6
>> content doesn't exactly foster the kind of
>> "rah-rah-lets-go-spend-a-fortune-to-replace-N-million-IPv4-only-CPE"
>> attitude, engineer types would hope to see from the business.
> 
>  -> I have said it several times on this list, but it keeps coming up.
>  There is a lot of "potential" IPv6 traffic on your network.  Take all
> the Google, Youtube, Facebook, Netflix traffic.  Add those all
> together and tell me what percent bandwidth they are on your network.
> That is IPv6 content available today.  Now add in the IPv6 "saber
> rattlers" like Yahoo and the US Gov't.  Reach a tipping point yet?  I
> have.
> 
> 
> So if there is a relatively quick and cost effective way for an ISP to
> provide an improved IPv6 experience right out of the gate, despite it
> not being Native, shouldn't it, at the very least be considered?
> Particularly when the alternative is simply waiting for
> 6rd\DS-lite\Native capable CPE or taking no action whatsoever(time is
> of the essence, no?).
>> 
>> Another thing that I think needs to be considered is that every day for a
>> subset of IPv6 internet users, legitimately impaired IPv6 service exists, and
>> some fraction of those users has their crummy IPv6 experience recorded and
>> reported on. These metrics and others
> 
> ->FUD.  I have 6RD at home (thanks Comcast), ISATAP at work (thanks
> MSFT for making this easy) and IPv6-only 3G + NAT64 on my mobile
> (thanks T-Mobile USA).  I have IPv6 everywhere, and i have NEVER had
> an IPv6 related network issue.  NEVER.  I hear people on Macs
> sometimes have issues, i don't have a Mac.  Most people don't have
> Macs.
> 
>  like them are the same metrics that will influence the data used in
> the decision making process by countless organizations, be they
> Enterprises, ISPs or Content Providers to help determine when they
> feel they should take the IPv6 plunge. And for those organization that
> are perfectly happy with their single /24 and gobs of NAT what reason,
> based on those underperforming IPv6 metrics, would they have to even
> request\enable Dual-Stacked or Native service from their provider? I'm
> not trying to say that 6to4 relay users influence the lions-share of
> the IPv6 internet use statistics, I'm sure their far from it, what I
> am saying is that from a purely altruistic-geek perspective, isn't
> anything that will help signal and allow for the adoption of v6 on a
> broader scale as well as help to provide improved internet performance
> what we're all after?
>> 
>> 
>> 
> 
> We all agree that customers dont care about ipv4 or ipv6, right?  So
> why bother with these hacks that don't actually help you grow your
> edge or deploy real IPv6?  It all seems like just a distraction to me.
>  Is it just trying to be a good citizen to help get the community some
> more short-term mileage out of the (too little, too late) dual-stack
> transition strategy for the Internet?
> 
> If you have business case for user experience with IPv6 ... then you
> should be doing dual-stack.  If you are running out of addersses, you
> should do DS-lite. If you don't have a business case ....
> 
> Cameron
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops



From cb.list6@gmail.com  Wed Oct 20 08:16:53 2010
Return-Path: <cb.list6@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 75F903A68D5; Wed, 20 Oct 2010 08:16:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.858
X-Spam-Level: 
X-Spam-Status: No, score=-1.858 tagged_above=-999 required=5 tests=[AWL=0.141,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aTxtBTFgzFXW; Wed, 20 Oct 2010 08:16:52 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id B81873A696D; Wed, 20 Oct 2010 08:16:51 -0700 (PDT)
Received: by qyk27 with SMTP id 27so1533275qyk.10 for <multiple recipients>; Wed, 20 Oct 2010 08:18:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=G7xjFn+xqn3NbvwjBetEUW7FGZDPtMjjj/5Gzd8e0pw=; b=syErDTzs71l4cwOTqz1UKZsnhbiMVYN8sImRwDlCuOmv7EgsxbJmJXjgJFIa8iK9nS ZXBpq7MU5Le1k2UAl9qXIcZlvPDQ7hyt/ON+2JPT/M4dxSR8t+cNBzUx+cNF1A5+iMlX H9P4Y6oIzT6qFgKFqQAfvvAKgZLjf8UY68jiI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=WwtgWX7E8fyh7xiLqVfWpvJT9x5uypkxfSl+oomoxdGrFMKjSWbjNi4kUWugeYd61K 6iNtdk46HRlPqmRG0+BcH1GzLjYWn3K9HoOsQLeIXeoX//ZyNT1Eqf2tDCwvZYMaaSuy T4ilxrh8PhhpecTO/aIiORrGLtg5L7hVP2RtM=
MIME-Version: 1.0
Received: by 10.224.210.2 with SMTP id gi2mr5546238qab.108.1287587904799; Wed, 20 Oct 2010 08:18:24 -0700 (PDT)
Received: by 10.229.245.201 with HTTP; Wed, 20 Oct 2010 08:18:24 -0700 (PDT)
In-Reply-To: <OF9DF5D797.F506E6B7-ON852577C2.004B643C-852577C2.004E26A7@videotron.com>
References: <m24ochl8uj.wl%randy@psg.com> <OF9DF5D797.F506E6B7-ON852577C2.004B643C-852577C2.004E26A7@videotron.com>
Date: Wed, 20 Oct 2010 08:18:24 -0700
Message-ID: <AANLkTi=s8TFw8S3JYzZdRiboNHFmNV0aLQVyzuN_PP=A@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: Jean-Francois.TremblayING@videotron.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>, v6ops-bounces@ietf.org
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 15:16:53 -0000

On Wed, Oct 20, 2010 at 7:13 AM,
<Jean-Francois.TremblayING@videotron.com> wrote:
>
>
>
>>> My humble perspective, speaking strictly for myself here, is that any
>>> ISP (not just your employer, but any ISP) that is really concerned
>>> about consumer experience of IPv6 would do better to deploy IPv6 and
>>> manage it the same way it manages IPv4 traffic than to try to manage
>>> the way its customers work around the lack of native support.
>
>> yesssssssssss!
>> bleeping brilliantly said. =A0thank you.
>> randy
>
> Right, we are all in violent agreement that native IPv6 is the way to go.
>
> All the ISPs who support 6to4-PMT also strive to deploy native
> IPv6 in their network in a timely fashion. However, the hard reality
> is that vendor support is often lacking and/or prohibitivly
> expensive (like replacing the equipment with the latest one).
>
> So let me return the question to my favorite vendor (first poster in
> this mail). When can I get the IPv6 features I need to deploy
> IPv6 natively? Oh, and btw, I need that to be cheap, no hardware
> upgrades please.


Maybe your favorite vendor is my favorite vendor

http://www.ietf.org/mail-archive/web/v4tov6transition/current/msg00319.html

Nothing back in 2 weeks ....

Cameron


> The bottom line is that most vendors support for real-life deployment
> is late and we have to live with 6to4 being deployed now with
> a sub-optimal number of relays. Even if 6to4-PMT breaks e2e, it
> still provides IMHO for a better user experience in many cases,
> until native is available at every doorstep. (or 6RD as a temporary
> step toward native).
>
> We've all heard several times complaints about the lack of
> operator participation at the the IETF. Well, the last posts
> from Victor, Lee and Bill were real feedback from operators
> feeling the pain of pushing IPv6 deployement on a daily basis
> and trying to come up with actual implementable solutions.
>
> /JFT
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>
>

From edward.jankiewicz@sri.com  Wed Oct 20 08:23:30 2010
Return-Path: <edward.jankiewicz@sri.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 516A33A67FE for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 08:23:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.341
X-Spam-Level: 
X-Spam-Status: No, score=-1.341 tagged_above=-999 required=5 tests=[AWL=0.105,  BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Eq4Kkh5juzWm for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 08:23:29 -0700 (PDT)
Received: from mail1.sri.com (mail1.SRI.COM [128.18.30.17]) by core3.amsl.com (Postfix) with ESMTP id 135ED3A67D3 for <v6ops@ietf.org>; Wed, 20 Oct 2010 08:23:29 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; format=flowed
Received: from [192.168.1.144] ([unknown] [68.81.23.3]) by mail.sri.com (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0LAL00HDZHHNX350@mail.sri.com> for v6ops@ietf.org; Wed, 20 Oct 2010 08:25:00 -0700 (PDT)
Message-id: <4CBF09CC.4090406@sri.com>
Date: Wed, 20 Oct 2010 11:25:00 -0400
From: Ed Jankiewicz <edward.jankiewicz@sri.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>
References: <C8E3DFA9.1025F%victor.kuarsingh@gmail.com>
In-reply-to: <C8E3DFA9.1025F%victor.kuarsingh@gmail.com>
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 15:23:30 -0000

  Is it impossible to agree with both opinions?

Fred/Randy:  Operators should devote scarce resources to deploying 
native IPv6 and managing it well, rather than spinning more complicated 
webs of IPv4 accommodation.

Victor:  The ISP cannot dictate all updates to CPE, must provide access 
to all legacy customers, not just eager IPv6 adopters, so an interim 
mechanism that minimizes their inconvenience is needed.

There are around 100 RFCs and drafts about aspects of coexistence and 
transition flying around*, I sure hope they are not all going to be 
"standardized" because 100 standards for the same thing is about as good 
as none (IMHO).   Some of these are being generated by folks in the 
operator community, not just ivory tower solutions, so they should be 
motivated by real problems that need to be solved.  One size will never 
fit all, so some solutions may be a good fit for one ISP, and not for 
others.  Our job here is to provide engineering opinions on all these 
alternatives, to permit things that will help, and prevent things that 
will harm.

There should be something like "The laws of robotics" for 
transition/coexistence mechanisms:

1.  First, do no harm (to your legacy IPv4 customers, to your eager IPv6 
customers, to the larger community)
2.  Keep it simple (solve particular problems with targeted mechanisms) 
but no simpler than necessary to avoid harm
3.  Design and deploy your interim solution(s) with a clear path to 
eventually render them redundant:  enable, promote and encourage 
transition to native IPv6 (do not install any new equipment that does 
not support IPv6; sunset IPv4 access - without harming legacy customers)

I think these allow an operator complete freedom to manage their own 
network and to chose and operate any coexistence mechanism as long as 
they need to for supporting their customers, except where those choices 
cause harm to someone else.  Of course, there is no universal definition 
of "harm" so reasonable people can disagree, e.g. if a mechanism in use 
on the access side causes additional delay, content providers may see 
that as "harming" their users' experience.  That's why mailing lists and 
WG meetings are just so much fun.

On reflection, these are just corollary to the Robustness Principle or 
Postel's Law [RFC 793] .  "Be conservative in what you do, be liberal in 
what you accept from others."

Ed J


*shameless self-promotion:  take a look at 
http://tools.ietf.org/html/draft-jankiewicz-v6ops-v4v6biblio-02 
something I started to organize my own reading, but posted in case it 
helps anyone.  It tries to take a snapshot of the current work, so if I 
missed or mischaracterized anything, happy to take comments off-list to 
correct before Oct 25 update deadline.

On 10/20/2010 2:52 AM, Victor Kuarsingh wrote:
> Fred,
>
> I do agree with your position, but that is predicated on the ISP "managing"
> the CPE.  In many cases, the ISP just provides "access" to IP which means
> the customer equipment and it's capabilities are what determines what is
> feasible at that site.
>
> All the IPv6 enablement I do cannot change that (again, short of changing an
> entire business model for a company, this is running state for many ISPs).
> IPv4 service worked well since the equipment acquired by customers had a
> baseline of functionality which for the most part worked with the provider
> upstream systems.  IPv6 poses new challenges since the existing and deployed
> gear in many cases dose not support IPv6. ISPs will try to get this
> corrected but cannot control the entire deployment base.
>
> But I do find that many see this transition challenge as an "either/or"
> where we (many ISPs) see it as a combination of strategies.  I can work to
> provide IPv6 native connectivity, while providing a better service for
> endpoints that cannot support IPv6 day 1.  This was targeted as a part of
> the "mix" to keep things going while the real work of IPv6 deployment is
> carried out (again, not either/or, but parallel streams where this is not
> compromising the IPv6 deployment).
>
> This option is very easy to put in place (like 6to4 relays) and is low
> touch.  I would not consume many resources and engineering effort.
>
> I do see the argument if this was the sole strategy for a provider (which
> makes little sense), but do not fully see everyone's position if it's part
> of a bigger mix of technologies (of which IPv6 native is one) that supply
> services to the large cross-section of customers with varying degrees of
> functionality.  I can push for IPv6 and have this running on the side.
>
> Regards,
>
> Victor
>
>
>
> On 19/10/10 10:41 PM, "Randy Bush"<randy@psg.com>  wrote:
>
>>> My humble perspective, speaking strictly for myself here, is that any
>>> ISP (not just your employer, but any ISP) that is really concerned
>>> about consumer experience of IPv6 would do better to deploy IPv6 and
>>> manage it the same way it manages IPv4 traffic than to try to manage
>>> the way its customers work around the lack of native support.
>> yesssssssssss!
>>
>> bleeping brilliantly said.  thank you.
>>
>> randy
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From remi.despres@free.fr  Wed Oct 20 08:28:49 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 298183A67AD for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 08:28:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.437
X-Spam-Level: 
X-Spam-Status: No, score=-1.437 tagged_above=-999 required=5 tests=[AWL=0.512,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rqj4osk7wFi0 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 08:28:48 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.2]) by core3.amsl.com (Postfix) with ESMTP id A25E53A684D for <v6ops@ietf.org>; Wed, 20 Oct 2010 08:28:47 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2108.sfr.fr (SMTP Server) with ESMTP id 5B415700009F; Wed, 20 Oct 2010 17:30:20 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2108.sfr.fr (SMTP Server) with ESMTP id 690317000085; Wed, 20 Oct 2010 17:30:19 +0200 (CEST)
X-SFR-UUID: 20101020153019430.690317000085@msfrf2108.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <AANLkTinAoKowKO9AZjKuWn9ixZv5LRk0xkDOFdv+Wboh@mail.gmail.com>
Date: Wed, 20 Oct 2010 17:30:19 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <2ACE6EE9-AB72-4BDD-B048-B1C73DAF8608@free.fr>
References: <20100922151502.E21FF3A6952@core3.amsl.com> <4CBE0F32.8000504@gmail.com> <E71300B9B9041340B238540990BF04530914BB4CCF@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <ECD91250-8817-4746-ABC2-ED9CDFDFF82D@cisco.com> <12A4FA46AA7DA94A8FDBE2C945E1BF62016D414D@CL08MBC.rci.rogers.ca> <56EBC452-7E33-4BC9-AD27-AEF4806F8886@cisco.com> <4CBE3974.5020806@cernet.edu.cn> <E71300B9B9041340B238540990BF04530914BB4D8E@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <AANLkTinAoKowKO9AZjKuWn9ixZv5LRk0xkDOFdv+Wboh@mail.gmail.com>
To: Fred Baker <fred@cisco.com>, Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 15:28:49 -0000

Le 20 oct. 2010 =E0 16:24, Cameron Byrne a =E9crit :

> ...
> ->FUD.  I have 6RD at home (thanks Comcast), ISATAP at work (thanks
> MSFT for making this easy) and IPv6-only 3G + NAT64 on my mobile
> (thanks T-Mobile USA).  I have IPv6 everywhere, and i have NEVER had
> an IPv6 related network issue.  NEVER.  I hear people on Macs
> sometimes have issues, i don't have a Mac.  Most people don't have
> Macs.

I have a MAC and I have happily used IPv6 since 2008, with Google and =
IETF servers in particular.

In my understanding, IETF has been so far mistaken in its way to promote =
IPv6.
By insisting that, to offer IPv6 SERVICE, ISP should first upgrade their =
networks to DUAL-SATCK ROUTING, it has blocked the process.

One should not ignore that some ISP networks need hardware changes to =
support dual-stack routing (i.e. time and money).

But, fortunately, what is needed ASAP is the IPv6 SERVICE (real service, =
i.e. with native addresses, not 6to4 or Teredo addresses which have =
connectivity problems).

If the IPV6 SERVICE is offered with DUAL-SATCK ROUTING, very fine, but =
if it is done with 6rd to save time and money, very fine too.=20

Regards,
RD=20





From yiu_lee@cable.comcast.com  Wed Oct 20 08:34:07 2010
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 26F7C3A681F for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 08:34:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.165
X-Spam-Level: 
X-Spam-Status: No, score=-105.165 tagged_above=-999 required=5 tests=[AWL=2.398, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xsu88+ltjaCY for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 08:33:17 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 8F5483A67D3 for <v6ops@ietf.org>; Wed, 20 Oct 2010 08:33:12 -0700 (PDT)
Received: from ([24.40.55.40]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.100456544; Wed, 20 Oct 2010 11:34:39 -0400
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by pacdcexhub03.cable.comcast.com ([fe80::d1dd:b302:b617:3755%12]) with mapi id 14.01.0255.000; Wed, 20 Oct 2010 11:34:39 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>, =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Thread-Topic: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: AQHLcGifOd2pAnNd3EuQkp9ae9GlRZNJ98mA
Date: Wed, 20 Oct 2010 15:34:39 +0000
Message-ID: <C8E47F9D.1C72%yiu_lee@cable.comcast.com>
In-Reply-To: <C8E453E4.10274%victor.kuarsingh@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.0.0.100825
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <CA9BD0EA760C2B4BA2B18B5FD06DD7AF@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPv6 Operations <v6ops@ietf.org>, "draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org" <draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org>, "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>, Victor Kuarsingh <victor.kuarsingh@rci.rogers.com>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 15:34:07 -0000

Hi Remi,

Three points:=20

(1) This is a 00 draft. We would like to hear more from the group and put
the updates in 01.

(2) For the e2e transparency, this only affects those who rely on the
external initiated connections (like web-server, ssh-server, etc). We
assume most 6to4 users don't rely on e2e transparency.

(3) Some small population will like to have e2e transparency on 6to4. We
want to find a more automatic way to enable them to bypass the 6to4-PMT.
Worst case it may require manual opt-out. This is still under discussion.

Thanks,
Yiu


On 10/20/10 11:08 AM, "Victor Kuarsingh" <victor.kuarsingh@gmail.com>
wrote:

>Remi,
>
>Yes, the e2e transparency loss is of consideration (subject to further
>test
>on impact).
>
>In our testing we found that most in the wild equipment which turns on
>6to4
>sets the SLA-ID to "0".  Therefore the opt-in is not doing anything (6to4
>has just turned itself on automatically).
>
>The opt-out would be setting the SLA-ID to anything by "0" or perhaps "1"
>(since 1 is found as the SLA-ID on a few other defaults).
>
>This is only targeted at people of have default settings on their
>equipment
>and no knowledge of IPv4, IPv6 etc.
>
>In the use case where a provider may have turned on NAT44/LSN (NAT444) and
>used public IP space (which now breaks auto 6to4), the loss of e2e may not
>be as bad as broken 6to4.
>
>Again, I would like to stress, this is just an option to complete the
>whole
>strategy (which is put out IPv6).
>
>Victor
>
>
>On 20/10/10 1:20 AM, "R=E9mi Despr=E9s" <remi.despres@free.fr> wrote:
>
>> =20
>> Le 20 oct. 2010 =E0 05:23, Lee, Yiu a =E9crit :
>>=20
>>=20
>>> ... However, using this technique can improve the customer experience
>>>day
>>> one.
>>=20
>> To some extent, it might (and, from a strictly technical point of view,
>>the
>> idea is neat), but:
>> - Providers that would support it would, for their customers, BREAK the
>>e2e
>> transparency (that IPv6 has so far restored in the Internet, and that
>>is IMHO
>> a great progress not to be lost).
>> - Unless I misunderstand, the draft doesn't completely describe what
>>happens
>> to 6to4 addresses that have non 0 SLA-ID after their embedded IPv4
>>addresses.
>> - The requirement of a Customer opt-out introduces significant
>>complexity.
>>=20
>> Regards,
>> RD
>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>
>


From remi.despres@free.fr  Wed Oct 20 08:39:09 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6AF663A680A for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 08:39:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.441
X-Spam-Level: 
X-Spam-Status: No, score=-1.441 tagged_above=-999 required=5 tests=[AWL=0.508,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BF7kMq712IZ3 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 08:39:07 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.2]) by core3.amsl.com (Postfix) with ESMTP id 47D993A681F for <v6ops@ietf.org>; Wed, 20 Oct 2010 08:39:07 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2108.sfr.fr (SMTP Server) with ESMTP id 5F1AE70000A4; Wed, 20 Oct 2010 17:40:40 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2108.sfr.fr (SMTP Server) with ESMTP id 92E1370000A5; Wed, 20 Oct 2010 17:40:35 +0200 (CEST)
X-SFR-UUID: 20101020154035601.92E1370000A5@msfrf2108.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <C8E453E4.10274%victor.kuarsingh@gmail.com>
Date: Wed, 20 Oct 2010 17:40:35 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9CFBA48C-15DF-4D06-B7B5-D7DD5DDA28C9@free.fr>
References: <C8E453E4.10274%victor.kuarsingh@gmail.com>
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>, Victor Kuarsingh <victor.kuarsingh@rci.rogers.com>, "draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org" <draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org>, "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>, "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 15:39:09 -0000

Le 20 oct. 2010 =E0 17:08, Victor Kuarsingh a =E9crit :

> Remi,
>=20
> Yes, the e2e transparency loss is of consideration (subject to further =
test
> on impact).

A short time test cannot show which potentialities of e2e transparence =
restoration will be lost if, before really restoring e2e transparency we =
kill it.


> In our testing we found that most in the wild equipment which turns on =
6to4
> sets the SLA-ID to "0".  Therefore the opt-in is not doing anything =
(6to4
> has just turned itself on automatically).

We need IMHO solutions that work in ALL cases of their scope, not only =
MOST cases.


> ...
> Again, I would like to stress, this is just an option to complete the =
whole
> strategy (which is put out IPv6).

Deploy IPv6, indeed, but no by destroying part of its value from the =
outset.


Regards,
RD




From yiu_lee@cable.comcast.com  Wed Oct 20 08:40:54 2010
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A2BE03A6828 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 08:40:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.574
X-Spam-Level: 
X-Spam-Status: No, score=-105.574 tagged_above=-999 required=5 tests=[AWL=2.274, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Sjkb0RNE-am for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 08:40:51 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 85A723A6975 for <v6ops@ietf.org>; Wed, 20 Oct 2010 08:40:43 -0700 (PDT)
Received: from ([24.40.55.40]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.100459678; Wed, 20 Oct 2010 11:41:29 -0400
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by pacdcexhub03.cable.comcast.com ([fe80::d1dd:b302:b617:3755%12]) with mapi id 14.01.0255.000; Wed, 20 Oct 2010 11:41:29 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>, Fred Baker <fred@cisco.com>, Randy Bush <randy@psg.com>
Thread-Topic: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: AQHLcG1ClpAXfUpxlUeK3NTYgRrurg==
Date: Wed, 20 Oct 2010 15:41:28 +0000
Message-ID: <C8E4858D.1C80%yiu_lee@cable.comcast.com>
In-Reply-To: <2ACE6EE9-AB72-4BDD-B048-B1C73DAF8608@free.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.0.0.100825
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <809751D1B7EC2E44985F024E855A7033@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 15:40:54 -0000

Hi Remi,

I agree that 6rd is a very nice solution. The catch for 6rd is CPE
upgrade. This isn't easy for some operators which millions of unmanaged
CPEs.

Regards,
Yiu


On 10/20/10 11:30 AM, "R=E9mi Despr=E9s" <remi.despres@free.fr> wrote:

>Le 20 oct. 2010 =E0 16:24, Cameron Byrne a =E9crit :
>
>> ...
>> ->FUD.  I have 6RD at home (thanks Comcast), ISATAP at work (thanks
>> MSFT for making this easy) and IPv6-only 3G + NAT64 on my mobile
>> (thanks T-Mobile USA).  I have IPv6 everywhere, and i have NEVER had
>> an IPv6 related network issue.  NEVER.  I hear people on Macs
>> sometimes have issues, i don't have a Mac.  Most people don't have
>> Macs.
>
>I have a MAC and I have happily used IPv6 since 2008, with Google and
>IETF servers in particular.
>
>In my understanding, IETF has been so far mistaken in its way to promote
>IPv6.
>By insisting that, to offer IPv6 SERVICE, ISP should first upgrade their
>networks to DUAL-SATCK ROUTING, it has blocked the process.
>
>One should not ignore that some ISP networks need hardware changes to
>support dual-stack routing (i.e. time and money).
>
>But, fortunately, what is needed ASAP is the IPv6 SERVICE (real service,
>i.e. with native addresses, not 6to4 or Teredo addresses which have
>connectivity problems).
>
>If the IPV6 SERVICE is offered with DUAL-SATCK ROUTING, very fine, but if
>it is done with 6rd to save time and money, very fine too.
>
>Regards,
>RD=20
>
>
>
>
>_______________________________________________
>v6ops mailing list
>v6ops@ietf.org
>https://www.ietf.org/mailman/listinfo/v6ops


From gert@space.net  Wed Oct 20 08:50:32 2010
Return-Path: <gert@space.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2ABA93A68D5 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 08:50: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=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XMpWt-1+c6Na for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 08:50:31 -0700 (PDT)
Received: from mobil.space.net (mobil.Space.Net [IPv6:2001:608:2:81::2]) by core3.amsl.com (Postfix) with ESMTP id 6D6B43A6914 for <v6ops@ietf.org>; Wed, 20 Oct 2010 08:50:23 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id D4E17F8111 for <v6ops@ietf.org>; Wed, 20 Oct 2010 17:51:54 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id B6DF3F8146 for <v6ops@ietf.org>; Wed, 20 Oct 2010 17:51:54 +0200 (CEST)
Received: (qmail 29937 invoked by uid 1007); 20 Oct 2010 17:51:54 +0200
Date: Wed, 20 Oct 2010 17:51:54 +0200
From: Gert Doering <gert@space.net>
To: Victor Kuarsingh <Victor.Kuarsingh@rci.rogers.com>
Message-ID: <20101020155154.GP32268@Space.Net>
References: <20100922151502.E21FF3A6952@core3.amsl.com> <4CBE0F32.8000504@gmail.com> <12A4FA46AA7DA94A8FDBE2C945E1BF62016D4147@CL08MBC.rci.rogers.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <12A4FA46AA7DA94A8FDBE2C945E1BF62016D4147@CL08MBC.rci.rogers.ca>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: IPv6 Operations <v6ops@ietf.org>, draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 15:50:32 -0000

Hi,

On Tue, Oct 19, 2010 at 05:48:51PM -0400, Victor Kuarsingh wrote:
> On a side note then, I am happy to entertain additional input as to what an "operator" can do for the following use case.
> 
> - Post IPv6 ramp up / IPv4 runout
> - consumer is on IPv4-only (based on access network, home CPE etc)

"enable IPv6 there"

If that's not viable, offer 6rd or configured tunnels.

Gert Doering
        -- NetMaster
-- 
did you enable IPv6 on something today...?

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

From victor.kuarsingh@gmail.com  Wed Oct 20 09:18:17 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3E4423A68E8 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 09:18:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HqA0rsrtGkZ8 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 09:18:17 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by core3.amsl.com (Postfix) with ESMTP id 9D8203A69E7 for <v6ops@ietf.org>; Wed, 20 Oct 2010 09:17:56 -0700 (PDT)
Received: by pzk30 with SMTP id 30so292523pzk.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 09:19:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=QCQOp8pI/nfisSOBWKR85qA0bMGXYSKnIKQ21LMV/oo=; b=tf1+C199YjuA9pPX0aWBKwf/7tFOmZUN/PAi1xxS0BIxHxFmSWFwxeXXpOKPKlekzm mOB9fdLm10BW/o9TjZrP43ZdmOkwTgu/I44OAmTknfPfKeo8j/xqL5JG6NueQhx8ereS 44YVsOc/hwAN5OL5Vn4JgUoMteVeFaAnmWSKE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=q7989TpUANIiMec6bZeY6bJ9AF/V+k69i0fisHr0rhNV7p3ra/b8Asj4xbqYMHuqUy 1eH7HOk1Ln72tX+BoDCBpmrXCoetIaSe8aetPwlXr4MNSllAWB6Cm3odQg7f1SP8sAyL w4VpPM+9WwixK3rHLEAYyBqTEdpRAEMHSFlEo=
Received: by 10.142.165.18 with SMTP id n18mr6070241wfe.175.1287591560486; Wed, 20 Oct 2010 09:19:20 -0700 (PDT)
Received: from [172.28.172.161] ([65.91.54.2]) by mx.google.com with ESMTPS id y8sm138712vch.5.2010.10.20.09.19.16 (version=SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 09:19:19 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Wed, 20 Oct 2010 09:19:10 -0700
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: Gert Doering <gert@space.net>, Victor Kuarsingh <victor.kuarsingh@rci.rogers.com>
Message-ID: <C8E4648E.10286%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: ActwcobHzbjcWorH1kSfUukHsedw4g==
In-Reply-To: <20101020155154.GP32268@Space.Net>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 16:18:17 -0000

Gert,

IPv6 is not possible everywhere immediately (vendors have been selling us
IPv4-only upto this day).  I can go to the local store and maybe find one or
two boxes that do native IPv6 (the world we live in).

6RD is good, but again, I cannot force an unmanaged device to support
something.  Where I can, I would do this...  For all others, IPv4 (based on
what was sold and what people picked up at their local best buy) with
existing capabilities IS what we have in the near future.

On a side point:

Having customers configure something themselves... we are talking about a
customer base with varying degrees of capabilities (some have trouble
logging on).  I do not think comparing "our" (IETFers and like technical
folks) capabilities to make something work as a template to what can be done
in a production network.. I assume (based on experience) that most customers
will do nothing other the plug it in and turn it on.

Victor


On 20/10/10 8:51 AM, "Gert Doering" <gert@space.net> wrote:

> Hi,
> 
> On Tue, Oct 19, 2010 at 05:48:51PM -0400, Victor Kuarsingh wrote:
>> On a side note then, I am happy to entertain additional input as to what an
>> "operator" can do for the following use case.
>> 
>> - Post IPv6 ramp up / IPv4 runout
>> - consumer is on IPv4-only (based on access network, home CPE etc)
> 
> "enable IPv6 there"
> 
> If that's not viable, offer 6rd or configured tunnels.
> 
> Gert Doering
>         -- NetMaster



From gert@space.net  Wed Oct 20 09:21:29 2010
Return-Path: <gert@space.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2A473A6879 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 09:21:29 -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_53=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XyrOaYZMATdh for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 09:21:28 -0700 (PDT)
Received: from mobil.space.net (mobil.Space.Net [IPv6:2001:608:2:81::2]) by core3.amsl.com (Postfix) with ESMTP id 0D58F3A68EC for <v6ops@ietf.org>; Wed, 20 Oct 2010 09:21:27 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id 93E9EF8191 for <v6ops@ietf.org>; Wed, 20 Oct 2010 18:22:58 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 77700F81A2 for <v6ops@ietf.org>; Wed, 20 Oct 2010 18:22:58 +0200 (CEST)
Received: (qmail 11304 invoked by uid 1007); 20 Oct 2010 18:22:58 +0200
Date: Wed, 20 Oct 2010 18:22:58 +0200
From: Gert Doering <gert@space.net>
To: Victor Kuarsingh <vicmank@rogers.com>
Message-ID: <20101020162258.GS32268@Space.Net>
References: <20101020155154.GP32268@Space.Net> <C8E463CE.10282%vicmank@rogers.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="U9GRvG5UtPp9PlSk"
Content-Disposition: inline
In-Reply-To: <C8E463CE.10282%vicmank@rogers.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: IPv6 Operations <v6ops@ietf.org>, draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org, Victor Kuarsingh <victor.kuarsingh@rci.rogers.com>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 16:21:29 -0000

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

Hi,

On Wed, Oct 20, 2010 at 09:15:58AM -0700, Victor Kuarsingh wrote:
> IPv6 is not possible everywhere immediately (vendors have been selling us
> IPv4-only upto this day). =20

Why are you buying IPv4-only products?

> I can go to the local store and maybe find one or
> two boxes that do native IPv6 (the world we live in).

CPEs are a somewhat tricky matter, but even there, things are changing
(see Marco's work on labs.ripe.net).

As an ISP, you always have the option to use some generic and cheap
CPE hardware, and install your own custom firmware.  Or even get someone
to build specific CPEs for you (which is what free.fr did, if I understand
that right - and so they built in 6rd from the start).

> I do not think comparing "our" (IETFers and like technical
> folks) capabilities to make something work as a template to what can be d=
one
> in a production network.. I assume (based on experience) that most custom=
ers
> will do nothing other the plug it in and turn it on.

Over here, most times end users change to a new DSL provider, they get a
router with the offering for a very good price - and most of the time,=20
they just take it, because it offers additional functionality to what
they have, or because they want to have something that is known to work.

Sending out IPv6-capable CPEs at that point will give customers working
IPv6 without having to do anything but "plug it in and turn it on".

If you use an AVM Fritz!Box with some of the (smaller) german DSL networks=
=20
today, this is exactly what happens: SLAAC + DHCP-PD, ISP delegates a /56=
=20
to the CPE, CPE assigns /64 onto its LAN, voila, automatic IPv6.

Gert Doering
        -- NetMaster
--=20
did you enable IPv6 on something today...?

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

--U9GRvG5UtPp9PlSk
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)

iQCVAwUBTL8XYqkuBuNlUUl1AQK8qgQAh0KPjq+ghIL3RImXzXwRxL8hZUbz+iF7
+ndTiQeX/vENDj+q/v+iRBVjvofmp2+vg4WgXGj5I18H1xFudnp4WL7ueZeqn+R5
KdEofyuUiqtAQYSDz6cB/4LMHj7kYFamp+iNvgrINmNO9sIdZOl16uzQqP89Iqm9
MIcXPOEQ3Ys=
=T146
-----END PGP SIGNATURE-----

--U9GRvG5UtPp9PlSk--

From vicmank@rogers.com  Wed Oct 20 09:15:45 2010
Return-Path: <vicmank@rogers.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0CD723A699D for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 09:15: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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3oxSmXu9qVfX for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 09:15:33 -0700 (PDT)
Received: from hiltonsmtp.worldspice.net (hiltonsmtp.worldspice.net [216.37.94.58]) by core3.amsl.com (Postfix) with ESMTP id C96373A6921 for <v6ops@ietf.org>; Wed, 20 Oct 2010 09:14:48 -0700 (PDT)
Received: (qmail 13999 invoked by uid 0); 20 Oct 2010 16:16:16 -0000
Received: by simscan 1.4.0 ppid: 13560, pid: 13947, t: 1.0498s scanners: clamav: 0.94.1/m:50/d:9101 spam: 3.2.5
Received: from unknown (HELO ?172.28.172.161?) (vicmank@rogers.com@65.91.54.2) by hiltoncluster01.worldspice.net with ESMTPA; 20 Oct 2010 16:16:15 -0000
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Wed, 20 Oct 2010 09:15:58 -0700
From: Victor Kuarsingh <vicmank@rogers.com>
To: Gert Doering <gert@space.net>, Victor Kuarsingh <victor.kuarsingh@rci.rogers.com>
Message-ID: <C8E463CE.10282%vicmank@rogers.com>
Thread-Topic: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: ActwchRWp6LHzAJonk6asl48t4owkw==
In-Reply-To: <20101020155154.GP32268@Space.Net>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Mailman-Approved-At: Wed, 20 Oct 2010 09:30:40 -0700
Cc: IPv6 Operations <v6ops@ietf.org>, draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 16:15:45 -0000

Gert,

IPv6 is not possible everywhere immediately (vendors have been selling us
IPv4-only upto this day).  I can go to the local store and maybe find one or
two boxes that do native IPv6 (the world we live in).

6RD is good, but again, I cannot force an unmanaged device to support
something.  Where I can, I would do this...  For all others, IPv4 (based on
what was sold and what people picked up at their local best buy) with
existing capabilities IS what we have in the near future.

On a side point:

Having customers configure something themselves... we are talking about a
customer base with varying degrees of capabilities (some have trouble
logging on).  I do not think comparing "our" (IETFers and like technical
folks) capabilities to make something work as a template to what can be done
in a production network.. I assume (based on experience) that most customers
will do nothing other the plug it in and turn it on.

Victor


On 20/10/10 8:51 AM, "Gert Doering" <gert@space.net> wrote:

> Hi,
> 
> On Tue, Oct 19, 2010 at 05:48:51PM -0400, Victor Kuarsingh wrote:
>> On a side note then, I am happy to entertain additional input as to what an
>> "operator" can do for the following use case.
>> 
>> - Post IPv6 ramp up / IPv4 runout
>> - consumer is on IPv4-only (based on access network, home CPE etc)
> 
> "enable IPv6 there"
> 
> If that's not viable, offer 6rd or configured tunnels.
> 
> Gert Doering
>         -- NetMaster



From jhw@apple.com  Wed Oct 20 09:43:19 2010
Return-Path: <jhw@apple.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A420F3A69F7 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 09:43:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.299
X-Spam-Level: 
X-Spam-Status: No, score=-106.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KjXlW4sI5dm0 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 09:42:48 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 12DA53A6A03 for <v6ops@ietf.org>; Wed, 20 Oct 2010 09:39:31 -0700 (PDT)
Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out3.apple.com (Postfix) with ESMTP id 7B289B0BCCC1 for <v6ops@ietf.org>; Wed, 20 Oct 2010 09:41:04 -0700 (PDT)
X-AuditID: 11807134-b7c05ae000002d5d-f1-4cbf1ba0ce0b
Received: from elliott.apple.com (elliott.apple.com [17.151.62.13]) by relay14.apple.com (Apple SCV relay) with SMTP id BB.89.11613.0AB1FBC4; Wed, 20 Oct 2010 09:41:04 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from [172.16.1.7] (adit.conjury.org [75.101.54.88]) by elliott.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LAL00DUAL0FVR70@elliott.apple.com> for v6ops@ietf.org; Wed, 20 Oct 2010 09:41:04 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <4CBE4333.9040600@gmail.com>
Date: Wed, 20 Oct 2010 09:41:03 -0700
Message-id: <41B735BE-B7DA-4008-8A7E-8345B01F0D0D@apple.com>
References: <20100922151502.E21FF3A6952@core3.amsl.com> <4CBE0F32.8000504@gmail.com> <E71300B9B9041340B238540990BF04530914BB4CCF@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <ECD91250-8817-4746-ABC2-ED9CDFDFF82D@cisco.com> <12A4FA46AA7DA94A8FDBE2C945E1BF62016D414D@CL08MBC.rci.rogers.ca> <4CBE4333.9040600@gmail.com>
To: IETF V6OPS WG <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 16:43:19 -0000

On Oct 19, 2010, at 14:35, Brian E Carpenter wrote:

> Not to beat about the bush, I think [I-D.kuarsingh-v6ops-6to4-provider-managed-tunnel] is a horrible idea.

I'm horrified too.

On Oct 19, 2010, at 18:17, Brian E Carpenter wrote:

> Sure. So if every ISP that has customers operating servers with IPv6 connectivity
> provided a 6to4 relay and a route for 2002::/16, the return path for 6to4
> would end up being the same as the return path for IPv4. That was the design
> point, and it seem to me that there is a strong incentive for those ISPs
> to make it happen. Maybe this needs to be publicised.

This is the only other sensible comment I've seen in this thread.  I predict as the v6ops community grows, the blight caused by the presence of unmanaged 6to4 subscriber gateways will only grow more vexing over time.  Content delivery networks are another place where 6to4 is sure to cause headaches.

Not sure IETF is the correct organ to publicizing the problem.  Maybe somebody should bend the ear of a trade magazine reporter.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



From Jean-Francois.TremblayING@videotron.com  Wed Oct 20 09:44:37 2010
Return-Path: <Jean-Francois.TremblayING@videotron.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E59DE3A68CE; Wed, 20 Oct 2010 09:44:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.696
X-Spam-Level: 
X-Spam-Status: No, score=-1.696 tagged_above=-999 required=5 tests=[AWL=0.902,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qLdw+GWnvo67; Wed, 20 Oct 2010 09:44:34 -0700 (PDT)
Received: from mx02.videotron.com (mx02.videotron.com [24.201.243.151]) by core3.amsl.com (Postfix) with ESMTP id 8E83F3A69F1; Wed, 20 Oct 2010 09:42:48 -0700 (PDT)
In-Reply-To: <20101020162258.GS32268@Space.Net>
To: gert@space.net
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006
Message-ID: <OFE722104B.2896677B-ON852577C2.005A29A1-852577C2.005BEFE5@videotron.com>
From: Jean-Francois.TremblayING@videotron.com
Date: Wed, 20 Oct 2010 12:44:08 -0400
X-MIMETrack: Serialize by Router on DOMMTL11/SRV/GVL(Release 7.0.2FP1|January 10, 2007) at 2010-10-20 12:44:11, Serialize complete at 2010-10-20 12:44:11
Content-Type: multipart/alternative; boundary="=_alternative 005BEFE3852577C2_="
Cc: Victor Kuarsingh <vicmank@rogers.com>, IPv6 Operations <v6ops@ietf.org>, draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org, v6ops-bounces@ietf.org, Victor Kuarsingh <victor.kuarsingh@rci.rogers.com>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 16:44:37 -0000

Message en plusieurs parties au format MIME
--=_alternative 005BEFE3852577C2_=
Content-Type: text/plain; charset="US-ASCII"

> On Wed, Oct 20, 2010 at 09:15:58AM -0700, Victor Kuarsingh wrote:
>> IPv6 is not possible everywhere immediately (vendors have been selling 
us
>> IPv4-only upto this day). 
> 
> Why are you buying IPv4-only products?

Gert, 
I have to concur with Victor here, not on buying IPv4-only products, 
but on the fact that IPv6 feature-parity with IPv4 or near feature-
parity is rarely if not ever seen in vendors, even for those touting
IPv6 support. The lack of IPv6 features really hinders production 
deployments. 


>> I can go to the local store and maybe find one or
>> two boxes that do native IPv6 (the world we live in).
>CPEs are a somewhat tricky matter, but even there, things are changing
>(see Marco's work on labs.ripe.net).

If off-the-shelf IPv6 CPEs become the standard offering as early as
2012, it still leaves years to deal with IPv4-only customers CPEs. 
That's far from the 'instant IPv6' turn-on some posts on this list
seem to be suggesting. Something that works with current CPEs is
required, at least for a few years. That means NAT444 is unavoidable
for many providers. 


> As an ISP, you always have the option to use some generic and cheap
> CPE hardware, and install your own custom firmware.  Or even get someone
> to build specific CPEs for you (which is what free.fr did, if I 
understand
> that right - and so they built in 6rd from the start).

For those who provide a CPE maybe. Otherwise you're stuck with whatever 
your clients purchased at the local store. And you can bet that doesn't
support IPv6 yet. 


> Over here, most times end users change to a new DSL provider, they get a
> router with the offering for a very good price - and most of the time, 
> they just take it, because it offers additional functionality to what
> they have, or because they want to have something that is known to work.
> 
> Sending out IPv6-capable CPEs at that point will give customers working
> IPv6 without having to do anything but "plug it in and turn it on".

Unfortunately, this is rarely the case for cable providers, at least in 
North-America. Most users get their own CPE device and will hold it 
for several years until a major technology change (perceived or real)
will force them to go get another one (for example 802.11n). 
JFT


--=_alternative 005BEFE3852577C2_=
Content-Type: text/html; charset="US-ASCII"


<br>
<br>
<br>
<br><tt><font size=2>&gt; On Wed, Oct 20, 2010 at 09:15:58AM -0700, Victor
Kuarsingh wrote:<br>
&gt;&gt; IPv6 is not possible everywhere immediately (vendors have been
selling us<br>
&gt;&gt; IPv4-only upto this day). &nbsp;<br>
&gt; <br>
&gt; Why are you buying IPv4-only products?<br>
</font></tt>
<br><tt><font size=2>Gert, </font></tt>
<br><tt><font size=2>I have to concur with Victor here, not on buying IPv4-only
products, </font></tt>
<br><tt><font size=2>but on the fact that IPv6 feature-parity with IPv4
or near feature-</font></tt>
<br><tt><font size=2>parity is rarely if not ever seen in vendors, even
for those touting</font></tt>
<br><tt><font size=2>IPv6 support. The lack of IPv6 features really hinders
production </font></tt>
<br><tt><font size=2>deployments. </font></tt>
<br>
<br><tt><font size=2><br>
&gt;&gt; I can go to the local store and maybe find one or<br>
&gt;&gt; two boxes that do native IPv6 (the world we live in).<br>
&gt;CPEs are a somewhat tricky matter, but even there, things are changing<br>
&gt;(see Marco's work on labs.ripe.net).<br>
</font></tt>
<br><tt><font size=2>If off-the-shelf IPv6 CPEs become the standard offering
as early as</font></tt>
<br><tt><font size=2>2012, it still leaves years to deal with IPv4-only
customers CPEs. </font></tt>
<br><tt><font size=2>That's far from the 'instant IPv6' turn-on some posts
on this list</font></tt>
<br><tt><font size=2>seem to be suggesting. Something that works with current
CPEs is</font></tt>
<br><tt><font size=2>required, at least for a few years. That means NAT444
is unavoidable</font></tt>
<br><tt><font size=2>for many providers. </font></tt>
<br>
<br><tt><font size=2><br>
&gt; As an ISP, you always have the option to use some generic and cheap<br>
&gt; CPE hardware, and install your own custom firmware. &nbsp;Or even
get someone<br>
&gt; to build specific CPEs for you (which is what free.fr did, if I understand<br>
&gt; that right - and so they built in 6rd from the start).<br>
</font></tt>
<br><tt><font size=2>For those who provide a CPE maybe. Otherwise you're
stuck with whatever </font></tt>
<br><tt><font size=2>your clients purchased at the local store. And you
can bet that doesn't</font></tt>
<br><tt><font size=2>support IPv6 yet. </font></tt>
<br>
<br><tt><font size=2><br>
&gt; Over here, most times end users change to a new DSL provider, they
get a<br>
&gt; router with the offering for a very good price - and most of the time,
<br>
&gt; they just take it, because it offers additional functionality to what<br>
&gt; they have, or because they want to have something that is known to
work.<br>
&gt; <br>
&gt; Sending out IPv6-capable CPEs at that point will give customers working<br>
&gt; IPv6 without having to do anything but &quot;plug it in and turn it
on&quot;.</font></tt>
<br>
<br><tt><font size=2>Unfortunately, this is rarely the case for cable providers,
at least in </font></tt>
<br><tt><font size=2>North-America. Most users get their own CPE device
and will hold it </font></tt>
<br><tt><font size=2>for several years until a major technology change
(perceived or real)</font></tt>
<br><tt><font size=2>will force them to go get another one (for example
802.11n). </font></tt>
<br><font size=2 face="sans-serif">JFT</font>
<br>
<br>
--=_alternative 005BEFE3852577C2_=--

From victor.kuarsingh@gmail.com  Wed Oct 20 10:19:44 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F0353A68FB for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 10:19:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ejSUKgld0opO for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 10:19:43 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 43F403A6897 for <v6ops@ietf.org>; Wed, 20 Oct 2010 10:19:42 -0700 (PDT)
Received: by ewy6 with SMTP id 6so2608173ewy.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 10:21:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=LbLDT5YsEJotl4zzpJ5cMLYmag0BP3w33PdiQ/G/Yow=; b=Y2AbQnVC2VZ0MvekvFbVaFu4Pl4S3d5uMz7TrqGWj+SsEibVgyr/SkFM+d+jSPymqk EdYLucVVZOMY3AwxZfdU4f5rJ7XbXdCAoEAsNI56tEvw6C0CJKJ+DjlHRswqduBYsm8r yddeG0l6VKVB+wKGdT/TgbSH2cabc/U2Z6Q3c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=YngNHQZDBx/W3ZPkhTrHZPKrZ7U6GyjnqKE+5I4PnpJ7SUUdz2OJJWw+365Lh4c1lk RhNiAakS4vv1E2+u5IgHjJrjwV/7sOkpTrGCHh1X3C6toy8KpSEx3gQye28F+jthiJc3 3AanMouBian1No/dWtGvkcC8IqeR46dWdx3cM=
Received: by 10.213.35.2 with SMTP id n2mr3204282ebd.38.1287595275604; Wed, 20 Oct 2010 10:21:15 -0700 (PDT)
Received: from [172.28.172.161] ([65.91.54.2]) by mx.google.com with ESMTPS id j7sm166538vcr.39.2010.10.20.10.21.00 (version=SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 10:21:02 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Wed, 20 Oct 2010 10:20:56 -0700
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: james woodyatt <jhw@apple.com>, IETF V6OPS WG <v6ops@ietf.org>
Message-ID: <C8E47308.10299%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: Actweye6/rQbBW6zHUmqiDt3d3kQYw==
In-Reply-To: <41B735BE-B7DA-4008-8A7E-8345B01F0D0D@apple.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 17:19:44 -0000

James,

I agree, if we can get 6to4 relays out there in mass, then the challenges go
away or are subsided.  Unfortunately this is a theoretical position at this
point (having everyone do something for the good of all), and one cannot
build a real network on the notion that "I hope everyone does this".

Also, we are concerned about how long it would take to document, communicate
this concept and have ISPs and content providers implement it.  I have
offered to help Brian document this position as an effort to make it right.

Based on our track record on IPv6 communication and implementation, I would
suggest that it may take a long time to effect this change.. But it's worth
a try.

Regards,

Victor


On 20/10/10 9:41 AM, "james woodyatt" <jhw@apple.com> wrote:

> On Oct 19, 2010, at 14:35, Brian E Carpenter wrote:
> 
>> Not to beat about the bush, I think
>> [I-D.kuarsingh-v6ops-6to4-provider-managed-tunnel] is a horrible idea.
> 
> I'm horrified too.
> 
> On Oct 19, 2010, at 18:17, Brian E Carpenter wrote:
> 
>> Sure. So if every ISP that has customers operating servers with IPv6
>> connectivity
>> provided a 6to4 relay and a route for 2002::/16, the return path for 6to4
>> would end up being the same as the return path for IPv4. That was the design
>> point, and it seem to me that there is a strong incentive for those ISPs
>> to make it happen. Maybe this needs to be publicised.
> 
> This is the only other sensible comment I've seen in this thread.  I predict
> as the v6ops community grows, the blight caused by the presence of unmanaged
> 6to4 subscriber gateways will only grow more vexing over time.  Content
> delivery networks are another place where 6to4 is sure to cause headaches.
> 
> Not sure IETF is the correct organ to publicizing the problem.  Maybe somebody
> should bend the ear of a trade magazine reporter.
> 
> 
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, communications engineering
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops



From remi.despres@free.fr  Wed Oct 20 10:45:34 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 936CA3A69F3 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 10:45:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.144
X-Spam-Level: 
X-Spam-Status: No, score=-1.144 tagged_above=-999 required=5 tests=[AWL=0.205,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L3yIPhpCUgGt for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 10:45:33 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.2]) by core3.amsl.com (Postfix) with ESMTP id 71CCE3A69EE for <v6ops@ietf.org>; Wed, 20 Oct 2010 10:45:33 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2106.sfr.fr (SMTP Server) with ESMTP id 719AB700008C; Wed, 20 Oct 2010 19:47:06 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2106.sfr.fr (SMTP Server) with ESMTP id 0CD277000091; Wed, 20 Oct 2010 19:47:04 +0200 (CEST)
X-SFR-UUID: 20101020174704526.0CD277000091@msfrf2106.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <41B735BE-B7DA-4008-8A7E-8345B01F0D0D@apple.com>
Date: Wed, 20 Oct 2010 19:47:02 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <22DF0C13-8810-4484-86AD-0F92BB5AED5E@free.fr>
References: <20100922151502.E21FF3A6952@core3.amsl.com> <4CBE0F32.8000504@gmail.com> <E71300B9B9041340B238540990BF04530914BB4CCF@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <ECD91250-8817-4746-ABC2-ED9CDFDFF82D@cisco.com> <12A4FA46AA7DA94A8FDBE2C945E1BF62016D414D@CL08MBC.rci.rogers.ca> <4CBE4333.9040600@gmail.com> <41B735BE-B7DA-4008-8A7E-8345B01F0D0D@apple.com>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1081)
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 17:45:34 -0000

Le 20 oct. 2010 =E0 18:41, james woodyatt a =E9crit :

> On Oct 19, 2010, at 14:35, Brian E Carpenter wrote:
>=20
>> Not to beat about the bush, I think =
[I-D.kuarsingh-v6ops-6to4-provider-managed-tunnel] is a horrible idea.
>=20
> I'm horrified too.

Breaking e2e transparency in IPv6 should indeed be loudly dissuaded.


> On Oct 19, 2010, at 18:17, Brian E Carpenter wrote:
>=20
>> Sure. So if every ISP that has customers operating servers with IPv6 =
connectivity
>> provided a 6to4 relay and a route for 2002::/16, the return path for =
6to4
>> would end up being the same as the return path for IPv4. That was the =
design
>> point, and it seem to me that there is a strong incentive for those =
ISPs
>> to make it happen. Maybe this needs to be publicised.
>=20
> This is the only other sensible comment I've seen in this thread.  I =
predict as the v6ops community grows, the blight caused by the presence =
of unmanaged 6to4 subscriber gateways will only grow more vexing over =
time.  Content delivery networks are another place where 6to4 is sure to =
cause headaches.

The point that if each ISP would operate its own 6to4 relay there would =
be no IPv4 connectivity problem is right, but this is unlikely to =
happen.

Consequently, an incentive to spend money to just reduce adverse effects =
of 6to4 intrinsic limitations, is IMHO a bad advice.
What is needed is good quality IPv6 asap (be it with dual-stack routing =
and CPEs, with 6rd BRs and CPEs, 6a44 BRs for hosts that eventually =
support it, or whatever easily operated solution.=20

BTW, 6to4 is precisely something that will become impossible as ISPs =
start assigning RFC1918 addresses to customers (a problem that neither =
6rd nor 6a44 have).

Regards,
RD=20

=20

>=20
> Not sure IETF is the correct organ to publicizing the problem.  Maybe =
somebody should bend the ear of a trade magazine reporter.
>=20
>=20
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, communications engineering
>=20
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops



From pch-b6B5344D9@u-1.phicoh.com  Wed Oct 20 11:26:15 2010
Return-Path: <pch-b6B5344D9@u-1.phicoh.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 625AC3A67D9 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 11:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.059
X-Spam-Level: 
X-Spam-Status: No, score=-4.059 tagged_above=-999 required=5 tests=[AWL=0.541,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OPW7hvgzqsAA for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 11:26:14 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by core3.amsl.com (Postfix) with ESMTP id 3243D3A6824 for <v6ops@ietf.org>; Wed, 20 Oct 2010 11:26:13 -0700 (PDT)
Received: from stereo.hq.phicoh.net ([127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #2) id m1P8dO1-0001gNC; Wed, 20 Oct 2010 20:27 +0200
Message-Id: <m1P8dO1-0001gNC@stereo.hq.phicoh.net>
To: james woodyatt <jhw@apple.com>
From: Philip Homburg <pch-v6ops@u-1.phicoh.com>
Sender: pch-b6B5344D9@u-1.phicoh.com
References: <20100922151502.E21FF3A6952@core3.amsl.com> <4CBE0F32.8000504@gmail.com> <E71300B9B9041340B238540990BF04530914BB4CCF@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <ECD91250-8817-4746-ABC2-ED9CDFDFF82D@cisco.com> <12A4FA46AA7DA94A8FDBE2C945E1BF62016D414D@CL08MBC.rci.rogers.ca> <4CBE4333.9040600@gmail.com> <41B735BE-B7DA-4008-8A7E-8345B01F0D0D@apple.com> 
In-reply-to: Your message of "Wed, 20 Oct 2010 09:41:03 -0700 ." <41B735BE-B7DA-4008-8A7E-8345B01F0D0D@apple.com> 
Date: Wed, 20 Oct 2010 20:27:34 +0200
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 18:26:15 -0000

In your letter dated Wed, 20 Oct 2010 09:41:03 -0700 you wrote:
>Content delivery
> networks are another place where 6to4 is sure to cause headaches.

Why is that? If a content provider interally just routes 2002::/16 traffic
to a relay box, then it becomes just IPv4 traffic that can be routed to its
destination.

In fact, every content provider can serve 6to4 users better by doing this
themselves instead of relying on the 2002::/16 BGP routes.



From pch-b6B5344D9@u-1.phicoh.com  Wed Oct 20 11:29:59 2010
Return-Path: <pch-b6B5344D9@u-1.phicoh.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B5D433A681B for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 11:29:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.239
X-Spam-Level: 
X-Spam-Status: No, score=-4.239 tagged_above=-999 required=5 tests=[AWL=0.360,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4O+YQN-9S5oC for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 11:29:56 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by core3.amsl.com (Postfix) with ESMTP id 577BF3A680D for <v6ops@ietf.org>; Wed, 20 Oct 2010 11:29:53 -0700 (PDT)
Received: from stereo.hq.phicoh.net ([127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #2) id m1P8dRc-0001gOC; Wed, 20 Oct 2010 20:31 +0200
Message-Id: <m1P8dRc-0001gOC@stereo.hq.phicoh.net>
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>
From: Philip Homburg <pch-v6ops@u-1.phicoh.com>
Sender: pch-b6B5344D9@u-1.phicoh.com
In-reply-to: Your message of "Wed, 20 Oct 2010 10:20:56 -0700 ." <C8E47308.10299%victor.kuarsingh@gmail.com> 
Date: Wed, 20 Oct 2010 20:31:23 +0200
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 18:29:59 -0000
X-List-Received-Date: Wed, 20 Oct 2010 18:29:59 -0000

In your letter dated Wed, 20 Oct 2010 10:20:56 -0700 you wrote:
>I agree, if we can get 6to4 relays out there in mass, then the challenges go
>away or are subsided.  Unfortunately this is a theoretical position at this
>point (having everyone do something for the good of all), and one cannot
>build a real network on the notion that "I hope everyone does this".

A simple hack to get the return traffic is for an ISP that has for example an
IPv4 /16, to put 2002:xxyy::/32 in the IPv6 routing table. This causes all of
the return traffic for that ISP's 6to4 customers to take the right route
back over the IPv6 backbone.

Of course, everybody will officially hate you for doing that because it causes
more entries in the IPv6 routing table. But is a purely local solution that
you can use to get your customers IPv6 connected.



From victor.kuarsingh@gmail.com  Wed Oct 20 11:41:07 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 23CEA3A681F for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 11:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.261
X-Spam-Level: 
X-Spam-Status: No, score=-3.261 tagged_above=-999 required=5 tests=[AWL=1.338,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x9EflwKERWuu for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 11:41:04 -0700 (PDT)
Received: from mail-px0-f172.google.com (mail-px0-f172.google.com [209.85.212.172]) by core3.amsl.com (Postfix) with ESMTP id 886E63A67EF for <v6ops@ietf.org>; Wed, 20 Oct 2010 11:41:04 -0700 (PDT)
Received: by pxi9 with SMTP id 9so849511pxi.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 11:42:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=BL23VoxxDvkRkkaltGvmi0NxhvWtMD3RMOyKpAlm5AM=; b=ND4ALPgOVKvA/mBodhE8o7iV8JdadwKJfLQ3dtB4iQ3kAe07O5hVDI6keVKHEJfazE m1L0gxQO55LJHi+3IVGxGc3imtZVaKQPw9EW1+RKacq3BI0cFPnLvdwts0pY8HMuStOJ DGvnPCilNwSSMmkWMoY+BihoaYvNxVwtQ0i90=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=T0Tn/Rk+ZbC+P0NRwPHCS+qd2yooKYrW+nJg9I2B98LBFw1ZTBPLFPCkag7jNpot5J 4gU5FVtuMxyJgsTPUfJXSzqLx5Af5XlWCnO03m7s1Wgd5yUBIjT+l8YaVR3eZSpMu1BR Nbl5K4gxVaPvVs8LoJ6Hf2xQBLzWjGPtyoZCc=
Received: by 10.142.211.4 with SMTP id j4mr6257657wfg.308.1287600158019; Wed, 20 Oct 2010 11:42:38 -0700 (PDT)
Received: from [172.28.172.161] ([65.91.54.2]) by mx.google.com with ESMTPS id f18sm204128vcm.35.2010.10.20.11.42.35 (version=SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 11:42:37 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Wed, 20 Oct 2010 11:42:24 -0700
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: Philip Homburg <pch-v6ops@u-1.phicoh.com>
Message-ID: <C8E48620.102A7%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: ActwhokzkclFKSbG8U+/jpnc1PVB5w==
In-Reply-To: <m1P8dRc-0001gOC@stereo.hq.phicoh.net>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 18:41:08 -0000

Phillip,

Correct, but if people filter the routes, then it would not work.  To be
clear, this was something that was talked about before PMT and it was
suggested that poisoning the IPv6 table with IPv4 routes was a non-starter.

Regards,

Victor


On 20/10/10 11:31 AM, "Philip Homburg" <pch-v6ops@u-1.phicoh.com> wrote:

> In your letter dated Wed, 20 Oct 2010 10:20:56 -0700 you wrote:
>> I agree, if we can get 6to4 relays out there in mass, then the challenges go
>> away or are subsided.  Unfortunately this is a theoretical position at this
>> point (having everyone do something for the good of all), and one cannot
>> build a real network on the notion that "I hope everyone does this".
> 
> A simple hack to get the return traffic is for an ISP that has for example an
> IPv4 /16, to put 2002:xxyy::/32 in the IPv6 routing table. This causes all of
> the return traffic for that ISP's 6to4 customers to take the right route
> back over the IPv6 backbone.
> 
> Of course, everybody will officially hate you for doing that because it causes
> more entries in the IPv6 routing table. But is a purely local solution that
> you can use to get your customers IPv6 connected.
> 
> 



From pch-b6B5344D9@u-1.phicoh.com  Wed Oct 20 11:46:42 2010
Return-Path: <pch-b6B5344D9@u-1.phicoh.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DA99C3A68B8 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 11:46:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.329
X-Spam-Level: 
X-Spam-Status: No, score=-4.329 tagged_above=-999 required=5 tests=[AWL=0.270,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VxrrWZ43o7ld for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 11:46:33 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by core3.amsl.com (Postfix) with ESMTP id EA8D93A68D5 for <v6ops@ietf.org>; Wed, 20 Oct 2010 11:46:12 -0700 (PDT)
Received: from stereo.hq.phicoh.net ([127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #2) id m1P8dhC-0001j2C; Wed, 20 Oct 2010 20:47 +0200
Message-Id: <m1P8dhC-0001j2C@stereo.hq.phicoh.net>
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>
From: Philip Homburg <pch-v6ops@u-1.phicoh.com>
Sender: pch-b6B5344D9@u-1.phicoh.com
In-reply-to: Your message of "Wed, 20 Oct 2010 11:42:24 -0700 ." <C8E48620.102A7%victor.kuarsingh@gmail.com> 
Date: Wed, 20 Oct 2010 20:47:29 +0200
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 18:46:42 -0000

In your letter dated Wed, 20 Oct 2010 11:42:24 -0700 you wrote:
>Correct, but if people filter the routes, then it would not work.  To be
>clear, this was something that was talked about before PMT and it was
>suggested that poisoning the IPv6 table with IPv4 routes was a non-starter.

Given the amount of junk in the IPv4 routing table, does it really make sense
to break a relatively clean transition technique by being overly conservative
when it comes to the routing table?

Fortunately, it is not my call.

But it does suggest that the idea that IPv4 space is running out and that we
have to act now is not universally accepted, not even by people running
IPv6.



From jhw@apple.com  Wed Oct 20 11:56:35 2010
Return-Path: <jhw@apple.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3548C3A683A for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 11:56:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.407
X-Spam-Level: 
X-Spam-Status: No, score=-107.407 tagged_above=-999 required=5 tests=[AWL=1.192, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0zt2GA8k2euD for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 11:56:34 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id 085A93A681B for <v6ops@ietf.org>; Wed, 20 Oct 2010 11:56:34 -0700 (PDT)
Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out4.apple.com (Postfix) with ESMTP id 03EDBB7016E3 for <v6ops@ietf.org>; Wed, 20 Oct 2010 11:58:08 -0700 (PDT)
X-AuditID: 11807134-b7c05ae000002d5d-78-4cbf3bbf1101
Received: from elliott.apple.com (elliott.apple.com [17.151.62.13]) by relay14.apple.com (Apple SCV relay) with SMTP id 60.C1.11613.FBB3FBC4; Wed, 20 Oct 2010 11:58:07 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from [17.151.110.50] by elliott.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LAL00D4SRCVVRB0@elliott.apple.com> for v6ops@ietf.org; Wed, 20 Oct 2010 11:58:07 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <m1P8dO1-0001gNC@stereo.hq.phicoh.net>
Date: Wed, 20 Oct 2010 11:58:07 -0700
Message-id: <FFD59518-2527-4E30-AC81-96ABFA5B4AC0@apple.com>
References: <20100922151502.E21FF3A6952@core3.amsl.com> <4CBE0F32.8000504@gmail.com> <E71300B9B9041340B238540990BF04530914BB4CCF@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <ECD91250-8817-4746-ABC2-ED9CDFDFF82D@cisco.com> <12A4FA46AA7DA94A8FDBE2C945E1BF62016D414D@CL08MBC.rci.rogers.ca> <4CBE4333.9040600@gmail.com> <41B735BE-B7DA-4008-8A7E-8345B01F0D0D@apple.com> <m1P8dO1-0001gNC@stereo.hq.phicoh.net>
To: Philip Homburg <pch-v6ops@u-1.phicoh.com>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 18:56:35 -0000

On Oct 20, 2010, at 11:27, Philip Homburg wrote:
> In your letter dated Wed, 20 Oct 2010 09:41:03 -0700 you wrote:
>> 
>> Content delivery networks are another place where 6to4 is sure to cause headaches.
> 
> Why is that? If a content provider interally just routes 2002::/16 traffic to a relay box, then it becomes just IPv4 traffic that can be routed to its destination.

A 6to4 relay router needs to be inserted into the optimized paths between every IPv6 content distribution server and its potentially 6to4-located clients.  That's a headache all by itself.

Then there's the more terrifying problem of how your CDN chooses the optimal content server for the client [based on $MAGICK_FAERIE_DUST, which I'm going to leave for other-- more polite-- participants to describe, but trust me: 6to4 can throw any of *several* different giant spanners into those works, depending on how their particular tribe of faeries are organized].

> In fact, every content provider can serve 6to4 users better by doing this themselves instead of relying on the 2002::/16 BGP routes.

What they *can* do, and what they will judge *worth* doing, might be pretty far apart.

p.s. All of the above applies just as well to Teredo, but Teredo has better sunsetting than 6to4.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



From victor.kuarsingh@gmail.com  Wed Oct 20 11:58:46 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A44673A682D for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 11:58:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.529
X-Spam-Level: 
X-Spam-Status: No, score=-3.529 tagged_above=-999 required=5 tests=[AWL=1.070,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dpqUQVbMyMIE for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 11:58:45 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 578C03A67EF for <v6ops@ietf.org>; Wed, 20 Oct 2010 11:58:45 -0700 (PDT)
Received: by ewy6 with SMTP id 6so2696183ewy.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 12:00:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=iRlWnBT7zB+yDrN0jK+X2g+H1BJndmLJNDQHEDj6wEM=; b=kaJoUR1Ufgc5eWoium6+EX9ba+9LehYtD0R2aGcPmtANPi2CavzNcyCVZs+72oKmns /O8aEpaWuST5zRwP5zaCo/n/AkF3ptDgH8Guil8iW9B81zxrStozSUqy/ma0FXePpj8U mfdvgwUTul1UPbtmdthpUEe9XSxm05sqmhJA4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=VmkiV5cRhLt2qMhT9mAtX9O59pML3wVAgW+8d4p+Lbva9X021MLOKsEr5GtBAHLi61 22gfhiDzrT2PsmTET/RiStADKmO9ZE+O+L5QDWiWk5EwrrdmiqVb14yR02esLZAyQ6TA 7UYEelIa1ghOrP5Yc4TsKQHau5CmjDDOzkMGM=
Received: by 10.213.26.14 with SMTP id b14mr7096230ebc.15.1287601218417; Wed, 20 Oct 2010 12:00:18 -0700 (PDT)
Received: from [172.28.172.161] ([65.91.54.2]) by mx.google.com with ESMTPS id b52sm633073eei.1.2010.10.20.12.00.17 (version=SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 12:00:17 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Wed, 20 Oct 2010 12:00:07 -0700
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: Philip Homburg <pch-v6ops@u-1.phicoh.com>
Message-ID: <C8E48A47.102AB%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: ActwiQLMUVdkFcANC0yHvSPXVInbEQ==
In-Reply-To: <m1P8dhC-0001j2C@stereo.hq.phicoh.net>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 18:58:46 -0000

Phillip,

Perhaps the community would accept a "time limited" acceptance of longer
then 2002::/16 set of routes would work.

We would need to get people to agree to not drop them.  And of course, how
would we deal with the "removal" process?  How would we twilight this? This
may be another challenging item which requires a bunch of providers agreeing
to something to do globally.

I am not as concerned about longer then /16s as others.

Regards,

Victor


On 20/10/10 11:47 AM, "Philip Homburg" <pch-v6ops@u-1.phicoh.com> wrote:

> In your letter dated Wed, 20 Oct 2010 11:42:24 -0700 you wrote:
>> Correct, but if people filter the routes, then it would not work.  To be
>> clear, this was something that was talked about before PMT and it was
>> suggested that poisoning the IPv6 table with IPv4 routes was a non-starter.
> 
> Given the amount of junk in the IPv4 routing table, does it really make sense
> to break a relatively clean transition technique by being overly conservative
> when it comes to the routing table?
> 
> Fortunately, it is not my call.
> 
> But it does suggest that the idea that IPv4 space is running out and that we
> have to act now is not universally accepted, not even by people running
> IPv6.
> 
> 



From ichiroumakino@gmail.com  Wed Oct 20 12:09:28 2010
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 59C1F3A67D9 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 12:09:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.571
X-Spam-Level: 
X-Spam-Status: No, score=-2.571 tagged_above=-999 required=5 tests=[AWL=0.028,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TjzCbprfeDdO for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 12:09:27 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id E05243A67DF for <v6ops@ietf.org>; Wed, 20 Oct 2010 12:09:23 -0700 (PDT)
Received: by eyf6 with SMTP id 6so916532eyf.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 12:10:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=YS+nv+2fYaoE1mnpQANRa/Zj2W1z+aWozQFT/NrzQjQ=; b=STGErUp9806/byhBF91dgBbt6XoqLRa8Bae03d+mw4XJlX1C8Ht+nuEJRrXBh7lKNv mShOKVS97wLILFkbkNDdkvDmxYpmKOzKW8TRUuQUOOXl3XGIdaSV7pFfs++rcA74abBd VBnnt2c8k2m5Q/I+wVKX7U1qH9L8o4cNVzyO4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=qCi4Wy+f0/KxcfbEcc/doLFXnmmp5OkXm/KffTx7hWlQgTUkZxY0QZe13hz4fpiVHR 7E77Tak4bnG0MYlBATcrEfsR0DG7j1eQ21tUclKtNaKBJYBdih/ZeB72CuYiaZLKsSvD 3OFAKU++8sq6EbXs7iJXpsrNIhvY6m5ijp7BE=
Received: by 10.14.47.78 with SMTP id s54mr5429506eeb.21.1287601856711; Wed, 20 Oct 2010 12:10:56 -0700 (PDT)
Received: from ams3-vpn-dhcp6363.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) by mx.google.com with ESMTPS id b52sm643064eei.7.2010.10.20.12.10.50 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 12:10:51 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <C8E48A47.102AB%victor.kuarsingh@gmail.com>
Date: Wed, 20 Oct 2010 21:10:48 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <81414319-C5A7-430E-9EE8-B9F105401D76@employees.org>
References: <C8E48A47.102AB%victor.kuarsingh@gmail.com>
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>
X-Mailer: Apple Mail (2.1081)
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 19:09:28 -0000

> Perhaps the community would accept a "time limited" acceptance of =
longer
> then 2002::/16 set of routes would work.
>=20
> We would need to get people to agree to not drop them.  And of course, =
how
> would we deal with the "removal" process?  How would we twilight this? =
This
> may be another challenging item which requires a bunch of providers =
agreeing
> to something to do globally.
>=20
> I am not as concerned about longer then /16s as others.

or would the community accept:
ip route 192.88.99.1/32 Null0

alternatively and slightly more friendly redirect http 6to4 traffic to a =
local web server giving instructions for how to disable 6to4 (and use =
the ISP's native IPv6 service.)

cheers,
Ole=

From victor.kuarsingh@gmail.com  Wed Oct 20 12:17:24 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B4AEC3A6824 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 12:17:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.707
X-Spam-Level: 
X-Spam-Status: No, score=-2.707 tagged_above=-999 required=5 tests=[AWL=-0.108, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 62J3h+h0COhP for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 12:17:11 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 8E23A3A67DF for <v6ops@ietf.org>; Wed, 20 Oct 2010 12:17:09 -0700 (PDT)
Received: by gwaa18 with SMTP id a18so1319747gwa.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 12:18:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=1tjo39zKDWSeupow1jt+bM5WVJ7OcWim4AUu/znIGaY=; b=yET444wV00oSF6SqwsSVF4C+/OBSSm+jBPdR5/biBX8+vWxa22Q3+pKiihr8ncA0kg NmDOFoD72YF9CoAYCJr9Ni0r11N67J3Wv8UJNcGmYR5LPc2wmjIksUjKkIHOrmmMHy2R q9dFrfM8U0fcWWfQD5jyBFmOOavnqWHKk2tss=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=dPJkYsjxHLef7a6roUg6WTwbO4tR+AoWM9jc825hsZ9kZPSNV6bap5wVpw70eDTb/2 U1IIiUHGzOfTrDh/u367bOyTDPOhRURimzEAlqPaGFnEF8qn+5v+S7ByPSt1e71SGznV XZmnhMfMc2aIZXBqmTzkam1LTqnO81Xn9RxEM=
Received: by 10.42.106.208 with SMTP id a16mr5456423icp.380.1287602322820; Wed, 20 Oct 2010 12:18:42 -0700 (PDT)
Received: from [172.28.172.161] ([65.91.54.2]) by mx.google.com with ESMTPS id e16sm220452vcm.8.2010.10.20.12.18.40 (version=SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 12:18:41 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Wed, 20 Oct 2010 12:18:31 -0700
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: Ole Troan <otroan@employees.org>
Message-ID: <C8E48E97.102AF%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: Actwi5TVggCgOkMPLU27UQoNob+pfg==
In-Reply-To: <81414319-C5A7-430E-9EE8-B9F105401D76@employees.org>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 19:17:28 -0000

Ole, 

Just as point of reference, there are some "boxes" out there that have auto
6to4 (CPE/Gateways) which cannot be turned off (no option in config).  And
filtering the anycast IPv4 address does not turn it off either (so broken
IPv6).

Regards,

Victor


On 20/10/10 12:10 PM, "Ole Troan" <otroan@employees.org> wrote:

>> Perhaps the community would accept a "time limited" acceptance of longer
>> then 2002::/16 set of routes would work.
>> 
>> We would need to get people to agree to not drop them.  And of course, how
>> would we deal with the "removal" process?  How would we twilight this? This
>> may be another challenging item which requires a bunch of providers agreeing
>> to something to do globally.
>> 
>> I am not as concerned about longer then /16s as others.
> 
> or would the community accept:
> ip route 192.88.99.1/32 Null0
> 
> alternatively and slightly more friendly redirect http 6to4 traffic to a local
> web server giving instructions for how to disable 6to4 (and use the ISP's
> native IPv6 service.)
> 
> cheers,
> Ole



From ek@google.com  Wed Oct 20 12:21:30 2010
Return-Path: <ek@google.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 79CE23A6847 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 12:21:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.877
X-Spam-Level: 
X-Spam-Status: No, score=-105.877 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GO2DqfGeOgga for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 12:21:29 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 4889C3A67DF for <v6ops@ietf.org>; Wed, 20 Oct 2010 12:21:28 -0700 (PDT)
Received: from kpbe14.cbf.corp.google.com (kpbe14.cbf.corp.google.com [172.25.105.78]) by smtp-out.google.com with ESMTP id o9KJN1QE017634 for <v6ops@ietf.org>; Wed, 20 Oct 2010 12:23:02 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1287602582; bh=9vkF9Ym0PcFQQ1NIvUrktKh/wx4=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=H/Z6YGKQBM8OYsF4tPLNWMkoT9MhPzUD/i1GNlcjVoR0QtOIGtIOT4VVFEisohecc RjLKukzbUMaipiAgdRU2g==
Received: from vws14 (vws14.prod.google.com [10.241.21.142]) by kpbe14.cbf.corp.google.com with ESMTP id o9KJN0Sw017566 for <v6ops@ietf.org>; Wed, 20 Oct 2010 12:23:00 -0700
Received: by vws14 with SMTP id 14so2467419vws.23 for <v6ops@ietf.org>; Wed, 20 Oct 2010 12:23:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=oq1nyYxiHBuNYj3QJjDtZcBVRBYn3KjmYbM82lcf1KU=; b=quRdprgD5oJCvt1nwcVq71isW1EZe3fyluVhWa8m8Jq/DqMtkVx/nTg4ZHM4X+eKbi M8Yw2pLYHNX8AQ3kmQEQ==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=qeaPF4P+WjCDbp+LgbSMlhREgiAYXhv8p+IZm2DGLxEDxiqNGhWhmMIKFNZDvenxZl gvakDfL59eAZKXMZ5yDg==
MIME-Version: 1.0
Received: by 10.229.240.78 with SMTP id kz14mr6798114qcb.230.1287602579594; Wed, 20 Oct 2010 12:22:59 -0700 (PDT)
Received: by 10.229.78.228 with HTTP; Wed, 20 Oct 2010 12:22:59 -0700 (PDT)
In-Reply-To: <81414319-C5A7-430E-9EE8-B9F105401D76@employees.org>
References: <C8E48A47.102AB%victor.kuarsingh@gmail.com> <81414319-C5A7-430E-9EE8-B9F105401D76@employees.org>
Date: Wed, 20 Oct 2010 12:22:59 -0700
Message-ID: <AANLkTimrMHoyDH2cPoA3==U3Sp4DPxdMjG3n3bE96_5p@mail.gmail.com>
From: Erik Kline <ek@google.com>
To: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 19:21:30 -0000

On 20 October 2010 12:10, Ole Troan <otroan@employees.org> wrote:
>> Perhaps the community would accept a "time limited" acceptance of longer
>> then 2002::/16 set of routes would work.
>>
>> We would need to get people to agree to not drop them. =C2=A0And of cour=
se, how
>> would we deal with the "removal" process? =C2=A0How would we twilight th=
is? This
>> may be another challenging item which requires a bunch of providers agre=
eing
>> to something to do globally.
>>
>> I am not as concerned about longer then /16s as others.
>
> or would the community accept:
> ip route 192.88.99.1/32 Null0
>
> alternatively and slightly more friendly redirect http 6to4 traffic to a =
local web server giving instructions for how to disable 6to4 (and use the I=
SP's native IPv6 service.)

Again, if the client elevates RFC1918 local addresses to global scope
for 3484 purposes, thereby de-prefing 6to4 when doing addr selection
for dualstack destinations, doesn't this whole thing just become
irrelevant as far as /transition/ is concerned?  You'd only be
concerning yourself with traffic to IPv6-only destinations.

From ichiroumakino@gmail.com  Wed Oct 20 12:27:09 2010
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 68B633A6843 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 12:27:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.572
X-Spam-Level: 
X-Spam-Status: No, score=-2.572 tagged_above=-999 required=5 tests=[AWL=0.027,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8CvYW0Aqbc5r for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 12:27:08 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 43A943A67DF for <v6ops@ietf.org>; Wed, 20 Oct 2010 12:27:08 -0700 (PDT)
Received: by eyf6 with SMTP id 6so936888eyf.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 12:28:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=D/xK+wqwcRfT+zR5rEEejSfL0VPuznAWAIaKu0OuS8E=; b=DwadcMDpsC5ElImG5mDnJ0LB1azpdzjle8Dv5mxCrzX9pEsCu5XAg/p7QYC6ZacpqN LwyAyDRg7KV2IXKzcvq56QHHwb01ZLjOkObAPLQZVhFS2ypeiJXdvKzhuZPxift+J8OK Sqpn8s84O6stFg39dWAmLMrSfyzXKPzBPwmLg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=TJWlbvkYIx76zS1O1AEIAW6zBSO/x0asRXvxf78Euvl9UyESn0FJSfgDnMhz+qsy1T VShucnpsjmbLJmqAmp/1rMRMvT5T+SDbRxkSGW8wqAbMcvGfgu6PvPpkn5ukZmaSp/CE NfthY9vflaPBeXLTsrRQo9MSCKnTrVX8XBqzY=
Received: by 10.213.17.139 with SMTP id s11mr932797eba.51.1287602921359; Wed, 20 Oct 2010 12:28:41 -0700 (PDT)
Received: from ams3-vpn-dhcp6363.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) by mx.google.com with ESMTPS id b52sm666488eei.1.2010.10.20.12.28.37 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 12:28:40 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <C8E48E97.102AF%victor.kuarsingh@gmail.com>
Date: Wed, 20 Oct 2010 21:28:25 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5D783F8-3ECF-4548-B620-F1648A9B6FA6@employees.org>
References: <C8E48E97.102AF%victor.kuarsingh@gmail.com>
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>
X-Mailer: Apple Mail (2.1081)
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 19:27:09 -0000

Victor,

> Just as point of reference, there are some "boxes" out there that have =
auto
> 6to4 (CPE/Gateways) which cannot be turned off (no option in config).  =
And
> filtering the anycast IPv4 address does not turn it off either (so =
broken
> IPv6).

interesting. would you be able to share with the list (or privately) =
which CPEs do this?

cheers,
Ole


>>> Perhaps the community would accept a "time limited" acceptance of =
longer
>>> then 2002::/16 set of routes would work.
>>>=20
>>> We would need to get people to agree to not drop them.  And of =
course, how
>>> would we deal with the "removal" process?  How would we twilight =
this? This
>>> may be another challenging item which requires a bunch of providers =
agreeing
>>> to something to do globally.
>>>=20
>>> I am not as concerned about longer then /16s as others.
>>=20
>> or would the community accept:
>> ip route 192.88.99.1/32 Null0
>>=20
>> alternatively and slightly more friendly redirect http 6to4 traffic =
to a local
>> web server giving instructions for how to disable 6to4 (and use the =
ISP's
>> native IPv6 service.)
>>=20
>> cheers,
>> Ole
>=20
>=20


From ichiroumakino@gmail.com  Wed Oct 20 12:27:19 2010
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 07BA23A6847 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 12:27:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.572
X-Spam-Level: 
X-Spam-Status: No, score=-2.572 tagged_above=-999 required=5 tests=[AWL=0.027,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JX3v56LmCPSw for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 12:27:18 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id C8E4B3A681E for <v6ops@ietf.org>; Wed, 20 Oct 2010 12:27:17 -0700 (PDT)
Received: by ewy6 with SMTP id 6so2722504ewy.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 12:28:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=Mx7WIoy2gPuMC9E/ezFqyWQvRdc+FD8m/jj85fUyTPg=; b=IBEwYynqA6wY3/4zQbJOv/+87TOeCu8eEe2qyxFfzYC2WEkdaX4u0JfgYYetpPEY9/ JAeBSc1jNuwcPOg4crM+jqYPzSpMO5XhJ3cEQg0v/bttneMDZJlgoiJMqC62ilzPbotI 43LrB26kqCkhX5Ly/+sWKyy3i4232mZlSYXWU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=iCZ2by45i4Hw/r0Z5++4VZV1o6FdnLW8SdVlbJDzspzFYxzSu/erJSbJSEWBxnr1G2 Rzk0Pm0s7V984xD4FtkEZilLKi8mS7vodsZJJcCmAtarmOYbB6WkCHhY5er318nzzGry /aVoJIvBXB3E8AKRPIxj46LcLpZ+dv2HeVhOc=
Received: by 10.213.34.129 with SMTP id l1mr915356ebd.94.1287602931009; Wed, 20 Oct 2010 12:28:51 -0700 (PDT)
Received: from ams3-vpn-dhcp6363.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) by mx.google.com with ESMTPS id b52sm666488eei.1.2010.10.20.12.28.49 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 12:28:50 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <AANLkTimrMHoyDH2cPoA3==U3Sp4DPxdMjG3n3bE96_5p@mail.gmail.com>
Date: Wed, 20 Oct 2010 21:28:49 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <07ABC58E-B177-4DB4-9746-8D6AE3A2C086@employees.org>
References: <C8E48A47.102AB%victor.kuarsingh@gmail.com> <81414319-C5A7-430E-9EE8-B9F105401D76@employees.org> <AANLkTimrMHoyDH2cPoA3==U3Sp4DPxdMjG3n3bE96_5p@mail.gmail.com>
To: Erik Kline <ek@google.com>
X-Mailer: Apple Mail (2.1081)
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 19:27:19 -0000

Erik,

>>> Perhaps the community would accept a "time limited" acceptance of =
longer
>>> then 2002::/16 set of routes would work.
>>>=20
>>> We would need to get people to agree to not drop them.  And of =
course, how
>>> would we deal with the "removal" process?  How would we twilight =
this? This
>>> may be another challenging item which requires a bunch of providers =
agreeing
>>> to something to do globally.
>>>=20
>>> I am not as concerned about longer then /16s as others.
>>=20
>> or would the community accept:
>> ip route 192.88.99.1/32 Null0
>>=20
>> alternatively and slightly more friendly redirect http 6to4 traffic =
to a local web server giving instructions for how to disable 6to4 (and =
use the ISP's native IPv6 service.)
>=20
> Again, if the client elevates RFC1918 local addresses to global scope
> for 3484 purposes, thereby de-prefing 6to4 when doing addr selection
> for dualstack destinations, doesn't this whole thing just become
> irrelevant as far as /transition/ is concerned?  You'd only be
> concerning yourself with traffic to IPv6-only destinations.

agree, but I think for a complete host based solutions we need happy =
eyeballs.

cheers,
Ole



From victor.kuarsingh@gmail.com  Wed Oct 20 12:44:52 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE3773A68A0 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 12:44:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.994
X-Spam-Level: 
X-Spam-Status: No, score=-1.994 tagged_above=-999 required=5 tests=[AWL=-0.791, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xoo4BDZSFRHR for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 12:44:51 -0700 (PDT)
Received: from mail-pv0-f172.google.com (mail-pv0-f172.google.com [74.125.83.172]) by core3.amsl.com (Postfix) with ESMTP id E21D73A68EA for <v6ops@ietf.org>; Wed, 20 Oct 2010 12:44:50 -0700 (PDT)
Received: by pvg4 with SMTP id 4so611827pvg.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 12:46:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=4Ij5XiokuBQh7B5FI0pTDXeORRr5X2otwRaJzMy7cTE=; b=tDLV6Kz3qsf9Ao26uKrCmiH8zyqo4piVcdBqeeQIi1qX67IJZvZXlYgmioDCe2FNDf ybqJ1GuQr1ziv2Se0Votf6NsmbVSRqq8kFDS2DNUsud6sJfNCbBKPNqDNnUnV9vHcGGs TMJzdzNhcXu00SePO7hqReRMCC40L7gz8IN40=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=NW6zbVScIPjmgPZ9WkLa8EVQPVSKFgR/BUqL+NqgFQB9dahi5GM0+5uTlDxUfLz5Ju SAfCC3xjpasZVhG0p07HWd6/jt4uUHREu9H2fknxj5R0Y/fTU8eGpxqD7i6xnqaEMzL7 soBixUf49ZzIPKOMOODZcYT0s8G3CcTuxZ54M=
Received: by 10.142.116.13 with SMTP id o13mr6327594wfc.178.1287603984629; Wed, 20 Oct 2010 12:46:24 -0700 (PDT)
Received: from [172.28.172.161] ([65.91.54.2]) by mx.google.com with ESMTPS id p28sm233656vcr.46.2010.10.20.12.46.21 (version=SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 12:46:23 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Wed, 20 Oct 2010 12:46:10 -0700
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: Erik Kline <ek@google.com>, Ole Troan <otroan@employees.org>
Message-ID: <C8E49512.102B8%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: Actwj3GtsEL4cYPQOU+vjDlwP+39SQ==
In-Reply-To: <AANLkTimrMHoyDH2cPoA3==U3Sp4DPxdMjG3n3bE96_5p@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 19:44:52 -0000

Erik,

I do appreciate everyone's input on this, but I think I still have not been
clear as to how we see this fit into the big picture.

PMT is not "the" option, it only addresses part of a bigger issue.  For the
specific use case we are talking about, yes, we are concerning ourselves
with IPv6 only if IPv4-only access with unmanaged CPEs are used.

Here is example of what some ISPs may see.

1. IPv6 Native (stuff we can get to native IPv6 based on available
hardware/software in the access network and CPE supports IPv6)
2. IPv6 over Managed Tunneled/CPE.  (we can control the CPE and get it IPv6
via technologies like 6RD).
3. (*KEY ISSUE FOR PMT*) IPv4 only access (i.e. DOCSIS 2.0 which cannot be
upgraded to IPv6) with unmanaged CPEs.

It is the third use case we are concerned with if IPv6 only is out there
(again, we are all guessing as to if this may happened in any specific
timeframe).

I need to deal with all three situations.  I will need a mix of
technologies, there is no one-size-fits-all for IPv6 transition (not matter
how much I want it).

Again, vendors have been pumping our customer base with IPv4 only, non-IPv6
CPEs for years and continue to do so.  I am not buying them.. Customers are=
,
who pay for the entire system which pays all of us (through various channel=
s
and business models)

Regards,

Victor




On 20/10/10 12:22 PM, "Erik Kline" <ek@google.com> wrote:

> On 20 October 2010 12:10, Ole Troan <otroan@employees.org> wrote:
>>> Perhaps the community would accept a "time limited" acceptance of longe=
r
>>> then 2002::/16 set of routes would work.
>>>=20
>>> We would need to get people to agree to not drop them. =A0And of course, =
how
>>> would we deal with the "removal" process? =A0How would we twilight this? =
This
>>> may be another challenging item which requires a bunch of providers agr=
eeing
>>> to something to do globally.
>>>=20
>>> I am not as concerned about longer then /16s as others.
>>=20
>> or would the community accept:
>> ip route 192.88.99.1/32 Null0
>>=20
>> alternatively and slightly more friendly redirect http 6to4 traffic to a
>> local web server giving instructions for how to disable 6to4 (and use th=
e
>> ISP's native IPv6 service.)
>=20
> Again, if the client elevates RFC1918 local addresses to global scope
> for 3484 purposes, thereby de-prefing 6to4 when doing addr selection
> for dualstack destinations, doesn't this whole thing just become
> irrelevant as far as /transition/ is concerned?  You'd only be
> concerning yourself with traffic to IPv6-only destinations.



From prvs=902b287ac=Scott.Beuker@sjrb.ca  Wed Oct 20 12:51:12 2010
Return-Path: <prvs=902b287ac=Scott.Beuker@sjrb.ca>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC6943A68EC for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 12:51: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=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K2lCSrSwqaaS for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 12:51:11 -0700 (PDT)
Received: from prdcg4ipta02x-ext.shaw.ca (prdcg4ipta02x-ext.shaw.ca [204.209.208.147]) by core3.amsl.com (Postfix) with ESMTP id B09993A68E8 for <v6ops@ietf.org>; Wed, 20 Oct 2010 12:51:11 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.57,356,1283752800"; d="scan'208";a="154930157"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 20 Oct 2010 13:52:25 -0600
Message-ID: <1EA76BAD7F050648910C041BDDED8CD5013FDBAE@PRDCG4EXVW01-5.OSS.PRD>
In-Reply-To: <81414319-C5A7-430E-9EE8-B9F105401D76@employees.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: Actwin9DEI0Wg/wFSdmT7nnH3aG/cgAAb2cA
References: <C8E48A47.102AB%victor.kuarsingh@gmail.com> <81414319-C5A7-430E-9EE8-B9F105401D76@employees.org>
From: "Scott Beuker" <Scott.Beuker@sjrb.ca>
To: "Ole Troan" <otroan@employees.org>, "IETF V6OPS WG" <v6ops@ietf.org>
X-OriginalArrivalTime: 20 Oct 2010 19:52:26.0457 (UTC) FILETIME=[520FF490:01CB7090]
X-TM-AS-Product-Ver: SMEX-8.0.0.1285-6.500.1024-17716.001
X-TM-AS-Result: No--8.235900-0.000000-31
X-TM-AS-User-Approved-Sender: Yes
X-TM-AS-User-Blocked-Sender: No
Subject: Re: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 19:51:13 -0000

> or would the community accept:
> ip route 192.88.99.1/32 Null0
>=20
> alternatively and slightly more friendly redirect http 6to4 traffic to
a
> local web server giving instructions for how to disable 6to4 (and use
> the ISP's native IPv6 service.)
>=20
> cheers,
> Ole


Ole,

6to4 is not a transition mechanism. It's a band aid to provide users
stuck on an IPv4-only network access to IPv6-only content. Therefore,
bringing up native IPv6 service as a better alternative using 6to4 is
like saying that brushing your teeth twice a day is better than having
to get a brain tumor removed; while the statement is true, the
comparison is totally irrelevant.

The use of 6to4 implies that, for whatever reason, native IPv6 is
unavailable for that user. IPv4 will be preferred over IPv6 on a host
running native IPv4 and IPv6 over 6to4, so 6to4 is only there as a last
resort for IPv6 only content for a user temporarily waiting for native
IPv6 service.

6to4-PMT is a good idea, as are more specific 2002::/16 routes, because
both improve upon a solution with flaws (6to4) which will be utilized no
matter what you say or do. You can either have the better version, or
the existing inferior version, your pick.

You were lucky enough not to have issues with vendors and hardware life
cycles that prevented you from getting native 6to4 deployed in time?
Great! Congratulations! I'm happy for you! Unfortunately, not all of us
are that lucky and we have to deal with vendors dragging their feet on
complete and stable implementations, despite our incessant hounding the
past 2+ years. This is sometimes how things go in the real world, and
that's why we have "Plan C" type measures like 6to4 to temporarily plug
holes and, as such, smooth the transition to IPv6.

Blocking these improvements via this draft will not make 6to4 go away. I
guarantee it.

- Scott




From ichiroumakino@gmail.com  Wed Oct 20 13:06:07 2010
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A61763A68D3 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:06:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.572
X-Spam-Level: 
X-Spam-Status: No, score=-2.572 tagged_above=-999 required=5 tests=[AWL=0.027,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5MHwX8O6T1NL for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:06:06 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id E36283A68E8 for <v6ops@ietf.org>; Wed, 20 Oct 2010 13:06:05 -0700 (PDT)
Received: by eyf6 with SMTP id 6so984875eyf.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 13:07:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=aMxqc0W4J1BtcHxLsa04Fg3UgqkvU7VPi2VliiT8wrs=; b=V67awnMmo5hLlBjn866sbS6cQIq0fLw+leT9GUN9B80VIg51YWmm163aFgWSjM3n5F qGtGjlHsAbESiY7Zt0Cy5q/7TEPHLJo5b9PwcrK0rZl10ue++hZu6RDk2CjTkPWkgzRx EgJ5nMHJ/tUoVLp+fbgqpL2G5VtPHQNHY+zEM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=reGaPC3ifECe/EGn8GtfGD0n979gNSigcpEipEoA8VXU0Sd54w32GJ4HzF418z3NRh 9ifPVd20Etra29KQ+jGnkwKPqOg02ycMG+5ONzbOiZ8uDplH2ySN4ABBakjW8iUTt/jy VxXEPojz4dVgCmh2wnwf+k23OEOYDDTXk9i+E=
Received: by 10.14.127.200 with SMTP id d48mr2219310eei.10.1287605259039; Wed, 20 Oct 2010 13:07:39 -0700 (PDT)
Received: from ams3-vpn-dhcp6363.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) by mx.google.com with ESMTPS id b52sm709470eei.1.2010.10.20.13.07.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 13:07:37 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <1EA76BAD7F050648910C041BDDED8CD5013FDBAE@PRDCG4EXVW01-5.OSS.PRD>
Date: Wed, 20 Oct 2010 22:07:28 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B95D067E-BA26-4EFF-9659-C75BD084D603@employees.org>
References: <C8E48A47.102AB%victor.kuarsingh@gmail.com> <81414319-C5A7-430E-9EE8-B9F105401D76@employees.org> <1EA76BAD7F050648910C041BDDED8CD5013FDBAE@PRDCG4EXVW01-5.OSS.PRD>
To: "Scott Beuker" <Scott.Beuker@sjrb.ca>
X-Mailer: Apple Mail (2.1081)
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 20:06:07 -0000

Scott,

> 6to4 is not a transition mechanism. It's a band aid to provide users
> stuck on an IPv4-only network access to IPv6-only content. Therefore,
> bringing up native IPv6 service as a better alternative using 6to4 is
> like saying that brushing your teeth twice a day is better than having
> to get a brain tumor removed; while the statement is true, the
> comparison is totally irrelevant.

6to4 is a mechanism created to bypass your local non IPv6 supporting =
ISP.
that's not the case here and I don't quite see why 6to4 should be the =
first choice of tool to use.

cheers,
Ole


From victor.kuarsingh@gmail.com  Wed Oct 20 13:14:09 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 697AB3A68C7 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:14:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.293
X-Spam-Level: 
X-Spam-Status: No, score=-2.293 tagged_above=-999 required=5 tests=[AWL=-0.294, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QWjCI3xDnrtb for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:14:08 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 296F03A67D9 for <v6ops@ietf.org>; Wed, 20 Oct 2010 13:14:08 -0700 (PDT)
Received: by gwaa18 with SMTP id a18so1371593gwa.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 13:15:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=0mWusPG/U+47l8Fn02EiI7qVAx8+7QJNVUP7J3ht0uM=; b=A6s8HFjazwuGvo+nf6v13YmQkjJQKRFv3RwWQ1r/yZTvztHoXjyt0CnxFotGhI9yj4 DPgIGbc8Us+lDfIeSapO1uLDL34ZdfyytoToq6mCj1wd2SoeopqLhy5JHPH/7X2zueN7 HT3Xb+KUlRGi+QdGjJgJveLhDGDgUXjWPf4jY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=Lt4ogTo2x7F9DJxI/K2K7VXxV/bZ336qR/CYoWj8Jhu1EQAJ78cxF0M5dWXVBNdeBj 7DEztNww12m5cAe5H7YiKv4kO++v1NKpGl7piAT01xFXOXzN557z1xb5lMMgJYcDJ4a8 lyqM68fEOUkM00Z+fwz7jMyF2Bln3D89Nxg10=
Received: by 10.42.178.65 with SMTP id bl1mr2637565icb.478.1287605741545; Wed, 20 Oct 2010 13:15:41 -0700 (PDT)
Received: from [172.28.172.161] ([65.91.54.2]) by mx.google.com with ESMTPS id y14sm247338vch.4.2010.10.20.13.15.37 (version=SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 13:15:40 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Wed, 20 Oct 2010 13:15:26 -0700
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: Ole Troan <otroan@employees.org>, Scott Beuker <Scott.Beuker@sjrb.ca>
Message-ID: <C8E49BEE.102CE%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: Actwk4hVl/N5W1GfuU+bZjrYb7txKg==
In-Reply-To: <B95D067E-BA26-4EFF-9659-C75BD084D603@employees.org>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 20:14:09 -0000

Ole,

The suggestion was based on the fact that it's out there.  We take what we
have and try and use it for good.  Again, we were given lemons... So we are
making lemonade.

I know that 6to4 was not created for this purpose, but I think as in the
past with other technologies, we can re-purpose or leverage something if it
fits the bill and can help solve a problem.

Regards,

Victor



On 20/10/10 1:07 PM, "Ole Troan" <otroan@employees.org> wrote:

> Scott,
> 
>> 6to4 is not a transition mechanism. It's a band aid to provide users
>> stuck on an IPv4-only network access to IPv6-only content. Therefore,
>> bringing up native IPv6 service as a better alternative using 6to4 is
>> like saying that brushing your teeth twice a day is better than having
>> to get a brain tumor removed; while the statement is true, the
>> comparison is totally irrelevant.
> 
> 6to4 is a mechanism created to bypass your local non IPv6 supporting ISP.
> that's not the case here and I don't quite see why 6to4 should be the first
> choice of tool to use.
> 
> cheers,
> Ole
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops



From swmike@swm.pp.se  Wed Oct 20 13:24:06 2010
Return-Path: <swmike@swm.pp.se>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8CF3D3A67A7 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:24:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.538
X-Spam-Level: 
X-Spam-Status: No, score=-2.538 tagged_above=-999 required=5 tests=[AWL=0.061,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KbkNFgamaUrC for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:24:05 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id 885FD3A63CB for <v6ops@ietf.org>; Wed, 20 Oct 2010 13:24:00 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 666029E; Wed, 20 Oct 2010 22:25:32 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 65BE79A; Wed, 20 Oct 2010 22:25:32 +0200 (CEST)
Date: Wed, 20 Oct 2010 22:25:32 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>
In-Reply-To: <C8E48A47.102AB%victor.kuarsingh@gmail.com>
Message-ID: <alpine.DEB.1.10.1010202224180.29868@uplift.swm.pp.se>
References: <C8E48A47.102AB%victor.kuarsingh@gmail.com>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 20:24:06 -0000

On Wed, 20 Oct 2010, Victor Kuarsingh wrote:

> Perhaps the community would accept a "time limited" acceptance of longer 
> then 2002::/16 set of routes would work.

Let's NOT open that can of worms, mmmkay?

Let people do 6RD or something else instead of trying to do more work on 
6to4. 6to4 in its present state is what it is, if people want to deploy 
more relays, fine, but let's not change it, it won't help.

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

From prvs=902b287ac=Scott.Beuker@sjrb.ca  Wed Oct 20 13:24:23 2010
Return-Path: <prvs=902b287ac=Scott.Beuker@sjrb.ca>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF8053A63CB for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:24: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=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WLCQ4OAnIhYA for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:24:23 -0700 (PDT)
Received: from prdcg4ipta02x-ext.shaw.ca (prdcg4ipta02x-ext.shaw.ca [204.209.208.147]) by core3.amsl.com (Postfix) with ESMTP id 11ADB3A68F8 for <v6ops@ietf.org>; Wed, 20 Oct 2010 13:24:23 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.57,356,1283752800"; d="scan'208";a="154933095"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 20 Oct 2010 14:25:37 -0600
Message-ID: <1EA76BAD7F050648910C041BDDED8CD5013FDBAF@PRDCG4EXVW01-5.OSS.PRD>
In-Reply-To: <B95D067E-BA26-4EFF-9659-C75BD084D603@employees.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: ActwkmiPDusmp101SMCj7EstMzDZOgAAK/lw
References: <C8E48A47.102AB%victor.kuarsingh@gmail.com> <81414319-C5A7-430E-9EE8-B9F105401D76@employees.org> <1EA76BAD7F050648910C041BDDED8CD5013FDBAE@PRDCG4EXVW01-5.OSS.PRD> <B95D067E-BA26-4EFF-9659-C75BD084D603@employees.org>
From: "Scott Beuker" <Scott.Beuker@sjrb.ca>
To: "Ole Troan" <otroan@employees.org>
X-OriginalArrivalTime: 20 Oct 2010 20:25:56.0934 (UTC) FILETIME=[00666660:01CB7095]
X-TM-AS-Product-Ver: SMEX-8.0.0.1285-6.500.1024-17716.001
X-TM-AS-Result: No--12.865200-0.000000-31
X-TM-AS-User-Approved-Sender: Yes
X-TM-AS-User-Blocked-Sender: No
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 20:24:24 -0000

Ole,

> 6to4 is a mechanism created to bypass your local non IPv6 supporting
> ISP.
> that's not the case here and I don't quite see why 6to4 should be the
> first choice of tool to use.

You're getting distracted by things which are moot.

The bottom line is that 6to4 only comes into play when IPv4 is not
available. It's not lifting eyeballs away from IPv4 and towards IPv6. It
is NOT the "first choice of tool to use", it's in fact by definition the
last choice. It's there to provide the consumer a seamless Internet
experience while the Internet is in its transition state.

I'll reiterate what I said prior: trying to blockade improvements to
6to4 will NOT speed the deployment of native IPv6. ISPs that recognize
they may end up utilizing 6to4-PMT *briefly* are already doing
everything they can to deploy native IPv6, but want to improve the
customer experience in the interim for those using 6to4, in the scenario
where IPv6-only content comes faster than we are ready for it.

Attempting to improve upon "Plan C" (6to4) does not imply anything about
a lack of commitment on our part to "Plan A" (native IPv6) or "Plan B"
(better tunnels like 6RD).

I hope for the best, but I plan for the worst.

Thanks,
Scott

From Bill.Armstrong@chartercom.com  Wed Oct 20 13:29:09 2010
Return-Path: <Bill.Armstrong@chartercom.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5FA6C3A6914 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:29:09 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4JIJHX66T4qc for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:29:06 -0700 (PDT)
Received: from mail.chartercom.com (mail.chartercom.com [24.217.29.16]) by core3.amsl.com (Postfix) with ESMTP id 14FB53A6911 for <v6ops@ietf.org>; Wed, 20 Oct 2010 13:29:06 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.57,356,1283749200"; d="scan'208";a="122870082"
Received: from unknown (HELO KSTLMEXHTP03.CORP.CHARTERCOM.COM) ([192.168.31.174]) by mail.chartercom.com with ESMTP; 20 Oct 2010 15:30:38 -0500
Received: from KSTLMEXCP02MBX.CORP.CHARTERCOM.COM ([192.168.31.12]) by KSTLMEXHTP03.CORP.CHARTERCOM.COM ([192.168.31.174]) with mapi; Wed, 20 Oct 2010 15:30:38 -0500
From: "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>
To: Scott Beuker <Scott.Beuker@sjrb.ca>, Ole Troan <otroan@employees.org>, IETF V6OPS WG <v6ops@ietf.org>
Date: Wed, 20 Oct 2010 15:30:36 -0500
Thread-Topic: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: Actwin9DEI0Wg/wFSdmT7nnH3aG/cgAAb2cAAAIJZLA=
Message-ID: <E71300B9B9041340B238540990BF04530914C27968@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM>
References: <C8E48A47.102AB%victor.kuarsingh@gmail.com> <81414319-C5A7-430E-9EE8-B9F105401D76@employees.org> <1EA76BAD7F050648910C041BDDED8CD5013FDBAE@PRDCG4EXVW01-5.OSS.PRD>
In-Reply-To: <1EA76BAD7F050648910C041BDDED8CD5013FDBAE@PRDCG4EXVW01-5.OSS.PRD>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: Re: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 20:29:09 -0000

Scott hit the nail on the head.=20


-Bill


-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of S=
cott Beuker
Sent: Wednesday, October 20, 2010 2:52 PM
To: Ole Troan; IETF V6OPS WG
Subject: Re: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-=
tunnel-00.txt

> or would the community accept:
> ip route 192.88.99.1/32 Null0
>=20
> alternatively and slightly more friendly redirect http 6to4 traffic to
a
> local web server giving instructions for how to disable 6to4 (and use
> the ISP's native IPv6 service.)
>=20
> cheers,
> Ole


Ole,

6to4 is not a transition mechanism. It's a band aid to provide users
stuck on an IPv4-only network access to IPv6-only content. Therefore,
bringing up native IPv6 service as a better alternative using 6to4 is
like saying that brushing your teeth twice a day is better than having
to get a brain tumor removed; while the statement is true, the
comparison is totally irrelevant.

The use of 6to4 implies that, for whatever reason, native IPv6 is
unavailable for that user. IPv4 will be preferred over IPv6 on a host
running native IPv4 and IPv6 over 6to4, so 6to4 is only there as a last
resort for IPv6 only content for a user temporarily waiting for native
IPv6 service.

6to4-PMT is a good idea, as are more specific 2002::/16 routes, because
both improve upon a solution with flaws (6to4) which will be utilized no
matter what you say or do. You can either have the better version, or
the existing inferior version, your pick.

You were lucky enough not to have issues with vendors and hardware life
cycles that prevented you from getting native 6to4 deployed in time?
Great! Congratulations! I'm happy for you! Unfortunately, not all of us
are that lucky and we have to deal with vendors dragging their feet on
complete and stable implementations, despite our incessant hounding the
past 2+ years. This is sometimes how things go in the real world, and
that's why we have "Plan C" type measures like 6to4 to temporarily plug
holes and, as such, smooth the transition to IPv6.

Blocking these improvements via this draft will not make 6to4 go away. I
guarantee it.

- Scott



_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

E-MAIL CONFIDENTIALITY NOTICE:=20

=20

=20

=20

The contents of this e-mail message and=20
any attachments are intended solely for the=20
addressee(s) and may contain confidential=20
and/or legally privileged information. If you=20
are not the intended recipient of this message=20
or if this message has been addressed to you=20
in error, please immediately alert the sender
 by reply e-mail and then delete this message=20
and any attachments. If you are not the=20
intended recipient, you are notified that=20
any use, dissemination, distribution, copying,=20
or storage of this message or any attachment=20
is strictly prohibited.









From victor.kuarsingh@gmail.com  Wed Oct 20 13:29:31 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 19E623A6940 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:29:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.56
X-Spam-Level: 
X-Spam-Status: No, score=-2.56 tagged_above=-999 required=5 tests=[AWL=0.039,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pRp2ujRBxBAs for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:29:29 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 4FC9F3A6948 for <v6ops@ietf.org>; Wed, 20 Oct 2010 13:29:24 -0700 (PDT)
Received: by vws12 with SMTP id 12so2488170vws.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 13:30:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=L+yKRb5wwV3jppl3g2ge8RTJKIDOT9Ic+R6S4tMxGV8=; b=gvS/wd4pprk8/JYCUqgLNH0A6ATzhvRo5urUSrCXJYqVoG4k0rwNJ//v3pqhVTL4Uz ver73rzgtBQYeDYzsoBvNvSGXFciX6XucDdnxp7IPOh9/Qwn7DKW/aCWp3bd8JCBalmK qEWb/TspBIR4h81RtmAzmIUZxelBpZAkvJ+o8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=IL9wMy775VwGxtqRZjcUvSZBEKtu77EuvAQClg1H3crJRlfozvOu6UD09mN1sPBbP8 YzBefzM07c5WkwMiTdSTcUySm2/UVTiZPEQcA3t3lCXFGX4YwXLTNSrKjpSU1k0kivjV HniNFPoH3FQQdm9zqZOkkf/IyGShvAnDd4aRs=
Received: by 10.220.198.136 with SMTP id eo8mr935093vcb.104.1287606657372; Wed, 20 Oct 2010 13:30:57 -0700 (PDT)
Received: from [172.28.172.161] ([65.91.54.2]) by mx.google.com with ESMTPS id h28sm254337vcr.43.2010.10.20.13.30.55 (version=SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 13:30:56 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Wed, 20 Oct 2010 13:30:44 -0700
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Message-ID: <C8E49F84.102D3%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: ActwlauBxjI0/3V+DEK+npeStb69kw==
In-Reply-To: <alpine.DEB.1.10.1010202224180.29868@uplift.swm.pp.se>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 20:29:31 -0000

Mikael,

We are not changing 6to4... It's status quo.. We are just adding an new
layer to improve created a deterministic path (with loss of e2e).

The longer then /16 route is not a mod either, it's a global agreement issue
(will we accept longer then /16 for 2002::).

Regards,

Victor


On 20/10/10 1:25 PM, "Mikael Abrahamsson" <swmike@swm.pp.se> wrote:

> On Wed, 20 Oct 2010, Victor Kuarsingh wrote:
> 
>> Perhaps the community would accept a "time limited" acceptance of longer
>> then 2002::/16 set of routes would work.
> 
> Let's NOT open that can of worms, mmmkay?
> 
> Let people do 6RD or something else instead of trying to do more work on
> 6to4. 6to4 in its present state is what it is, if people want to deploy
> more relays, fine, but let's not change it, it won't help.



From ichiroumakino@gmail.com  Wed Oct 20 13:34:09 2010
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CF5DC3A6905 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:34:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.573
X-Spam-Level: 
X-Spam-Status: No, score=-2.573 tagged_above=-999 required=5 tests=[AWL=0.026,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4HO6e2ezEy8v for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:34:06 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 6B7B13A6904 for <v6ops@ietf.org>; Wed, 20 Oct 2010 13:34:04 -0700 (PDT)
Received: by ewy6 with SMTP id 6so2781008ewy.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 13:35:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=yFalSzHNvGWBU4X0u733UFAjM8l+9zBZZ+2y5FJfLWc=; b=YY/rNpzkheUbvLJ4UfqXaVN1VlyxQD7zeFTSTPUAbZToXoWCBeDwlrvu17BVLL+Gi0 XEojqkasl4BMFNdCyst21I8NXX+Taq2V46VL3tYQwA+YSebIu8AN/NpWVYVfDDjcGjM1 YSGEwhzOAKs8sRzMKcdzT2Dja3IeFTq/A5BRc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=SmqTWQHmREkJpC0JBreGOvreWw0wsAbqsTgYqR/oTVkcAJ/Ux7Xkzoa96vYlcQTuqP +fE4DBjmolLu51qsdJP2SURValDGPFMx1qV4g0YsNThc9OPz5+gVgfes2beIbKOEfX2G 7HAPRb/GKYJpz/8wlticEb895ZDlzOuTd/Qa0=
Received: by 10.14.127.66 with SMTP id c42mr4822054eei.28.1287606937664; Wed, 20 Oct 2010 13:35:37 -0700 (PDT)
Received: from ams3-vpn-dhcp6363.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) by mx.google.com with ESMTPS id q58sm736452eeh.15.2010.10.20.13.35.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 13:35:36 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <1EA76BAD7F050648910C041BDDED8CD5013FDBAF@PRDCG4EXVW01-5.OSS.PRD>
Date: Wed, 20 Oct 2010 22:35:29 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D9571054-81AA-4439-A4AC-B9D9711BC673@employees.org>
References: <C8E48A47.102AB%victor.kuarsingh@gmail.com> <81414319-C5A7-430E-9EE8-B9F105401D76@employees.org> <1EA76BAD7F050648910C041BDDED8CD5013FDBAE@PRDCG4EXVW01-5.OSS.PRD> <B95D067E-BA26-4EFF-9659-C75BD084D603@employees.org> <1EA76BAD7F050648910C041BDDED8CD5013FDBAF@PRDCG4EXVW01-5.OSS.PRD>
To: "Scott Beuker" <Scott.Beuker@sjrb.ca>
X-Mailer: Apple Mail (2.1081)
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 20:34:10 -0000

Scott,

>> 6to4 is a mechanism created to bypass your local non IPv6 supporting
>> ISP.
>> that's not the case here and I don't quite see why 6to4 should be the
>> first choice of tool to use.
>=20
> You're getting distracted by things which are moot.
>=20
> The bottom line is that 6to4 only comes into play when IPv4 is not
> available. It's not lifting eyeballs away from IPv4 and towards IPv6. =
It
> is NOT the "first choice of tool to use", it's in fact by definition =
the
> last choice. It's there to provide the consumer a seamless Internet
> experience while the Internet is in its transition state.
>=20
> I'll reiterate what I said prior: trying to blockade improvements to
> 6to4 will NOT speed the deployment of native IPv6. ISPs that recognize
> they may end up utilizing 6to4-PMT *briefly* are already doing
> everything they can to deploy native IPv6, but want to improve the
> customer experience in the interim for those using 6to4, in the =
scenario
> where IPv6-only content comes faster than we are ready for it.
>=20
> Attempting to improve upon "Plan C" (6to4) does not imply anything =
about
> a lack of commitment on our part to "Plan A" (native IPv6) or "Plan B"
> (better tunnels like 6RD).
>=20
> I hope for the best, but I plan for the worst.

I'm sure you can provide some better numbers, but am I correct in =
assuming that:
 - you have an huge set of CPEs that are IPv4 only
 - you have a small set of CPEs supporting 6to4
 - you have a tiny set of those CPEs doing 6to4 by default
 - you have a small set of CPEs supporting 6rd and native IPv6

what I don't quite understand is why the focus on plan C for a =
presumably tiny set of customers. when the big elephant in the room is =
the IPv4 only CPEs.

offer a patch for the 6to4 by default CPEs, encourage the users to =
upgrade to 6rd/native IPv6 CPEs, which is something I would think has to =
happen anyway...

cheers,
Ole

=20


From gert@space.net  Wed Oct 20 13:46:01 2010
Return-Path: <gert@space.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B2863A6905 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:46:01 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WR-lfpmEiX8d for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:46:00 -0700 (PDT)
Received: from mobil.space.net (mobil.Space.Net [IPv6:2001:608:2:81::2]) by core3.amsl.com (Postfix) with ESMTP id ECE1C3A68C2 for <v6ops@ietf.org>; Wed, 20 Oct 2010 13:45:59 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id 9DD84F8160 for <v6ops@ietf.org>; Wed, 20 Oct 2010 22:47:31 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 7991FF8166 for <v6ops@ietf.org>; Wed, 20 Oct 2010 22:47:31 +0200 (CEST)
Received: (qmail 11546 invoked by uid 1007); 20 Oct 2010 22:47:31 +0200
Date: Wed, 20 Oct 2010 22:47:31 +0200
From: Gert Doering <gert@space.net>
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>
Message-ID: <20101020204731.GT32268@Space.Net>
References: <alpine.DEB.1.10.1010202224180.29868@uplift.swm.pp.se> <C8E49F84.102D3%victor.kuarsingh@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C8E49F84.102D3%victor.kuarsingh@gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 20:46:01 -0000

Hi,

On Wed, Oct 20, 2010 at 01:30:44PM -0700, Victor Kuarsingh wrote:
> The longer then /16 route is not a mod either, it's a global agreement issue
> (will we accept longer then /16 for 2002::).

We're not going to accept 300.000 IPv4 routes coming back as 2002:<ipv4>
spill.  Don't go there.

Gert Doering
        -- NetMaster
-- 
did you enable IPv6 on something today...?

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

From swmike@swm.pp.se  Wed Oct 20 13:50:37 2010
Return-Path: <swmike@swm.pp.se>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A12B63A694F for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:50:37 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ychDSJjMWSJU for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:50:36 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id 86C093A694E for <v6ops@ietf.org>; Wed, 20 Oct 2010 13:50:36 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 08187A0; Wed, 20 Oct 2010 22:52:10 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 060A29A; Wed, 20 Oct 2010 22:52:10 +0200 (CEST)
Date: Wed, 20 Oct 2010 22:52:10 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>
In-Reply-To: <C8E49F84.102D3%victor.kuarsingh@gmail.com>
Message-ID: <alpine.DEB.1.10.1010202249170.29868@uplift.swm.pp.se>
References: <C8E49F84.102D3%victor.kuarsingh@gmail.com>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 20:50:37 -0000

On Wed, 20 Oct 2010, Victor Kuarsingh wrote:

> We are not changing 6to4... It's status quo.. We are just adding an new 
> layer to improve created a deterministic path (with loss of e2e).

No, 6to4 specifically prohibits more specifics in 2002::/16, to quote 
RFC3056:

"6to4 prefixes more specific than 2002::/16 must not be propagated in
    native IPv6 routing, to prevent pollution of the IPv6 routing table
    by elements of the IPv4 routing table. "

> The longer then /16 route is not a mod either, it's a global agreement issue
> (will we accept longer then /16 for 2002::).

The RFC prohibits this, so what you're asking for is a change of the RFC.

We're not going there, period.

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

From victor.kuarsingh@gmail.com  Wed Oct 20 13:52:39 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B273B3A6933 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:52:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.564
X-Spam-Level: 
X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.035,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fH0DxBEwbx9s for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:52:38 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id BF0BF3A68D2 for <v6ops@ietf.org>; Wed, 20 Oct 2010 13:52:38 -0700 (PDT)
Received: by mail-vw0-f44.google.com with SMTP id 12so2510340vws.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 13:54:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=j+x9V9YrxnqliYuegZHqbqEHbZAwGh+5J1JdDwLf3Lw=; b=LlS6f9nFdLil3YnqNmOdzDNcM6tdRoNQDs7FuTYGx+GljbJlsKxpLdPPwlvM+g9SBh 1BtSF9O8/mSQLibk6ZYwYPkwct3roKQ8HjhV5QuYnTCA55ZmuNaK5VHM8zpPFXCf/px2 itBXFjKx0CBGtXqNEgX5Gg9vFJhxMma6G6GDw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=HFzRCVHNeCq9x1h3r+zp+FGBhU9vtGOh9n6Dg3EoVXjD2Q+tTwImrgMDnh8niuxKf6 r3Sdn1QCmuPIC3uq5AL/2OIkuG5TOdk4s1KHQTJFWuwXYulkTv6LO5Rr5Fnut1as+PXW 0cGE5mC0Gb5QD/Hm3IGha4kxff9i3qvAr0myw=
Received: by 10.220.202.7 with SMTP id fc7mr2323533vcb.138.1287608052639; Wed, 20 Oct 2010 13:54:12 -0700 (PDT)
Received: from [172.28.172.161] ([65.91.54.2]) by mx.google.com with ESMTPS id l14sm265296vcr.42.2010.10.20.13.54.10 (version=SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 13:54:11 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Wed, 20 Oct 2010 13:53:58 -0700
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: Gert Doering <gert@space.net>
Message-ID: <C8E4A4F6.102E1%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: ActwmOpkY/jkPowA/kSRTx6zCT1iHQ==
In-Reply-To: <20101020204731.GT32268@Space.Net>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 20:52:39 -0000

Gert,

That way it was off the table... Based on this position. I agree, it's a
non-starter for many.

Regards,

Victor


On 20/10/10 1:47 PM, "Gert Doering" <gert@space.net> wrote:

> Hi,
> 
> On Wed, Oct 20, 2010 at 01:30:44PM -0700, Victor Kuarsingh wrote:
>> The longer then /16 route is not a mod either, it's a global agreement issue
>> (will we accept longer then /16 for 2002::).
> 
> We're not going to accept 300.000 IPv4 routes coming back as 2002:<ipv4>
> spill.  Don't go there.
> 
> Gert Doering
>         -- NetMaster



From victor.kuarsingh@gmail.com  Wed Oct 20 13:55:57 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0347A3A681E for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:55:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level: 
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.032,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GZYn3y0oRsvH for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 13:55:55 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id 7E5593A67A7 for <v6ops@ietf.org>; Wed, 20 Oct 2010 13:55:54 -0700 (PDT)
Received: by yxk30 with SMTP id 30so2186228yxk.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 13:57:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=k1PudpcFgNN2YVi71y17IDxz4YwA0QIJiKeeYVqbFJM=; b=wUKriACujoBv44vuZStfxs7LYLFO8jrWOjLkYh2e8K4TfjImKxSRV26SXWcoPlTNID /biBE9ExLuRWLmJrKT9eKIIt03u1JIxSZbrL73XmBFB91d92lrQLkbHy5hvrNouD1m0X 98NRcfTneDrNvZy0+q7m59bjtglegDtfb2KK4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=IDr3URwOMe/BeanCmWDVxepFYwxszzzmrF76e62sjf16WfgLIO8jUT4xqzS4l4dzWf dH1GeqCsn7VsQylc6jP0RXR5HNTUDw0TT7NizXRivo4f4aHAYTLkjjUEsLv9LFIuNAZY jQHEgfF5/sCscvd9KXuy6jna/MG+ZPuSOk+WA=
Received: by 10.42.41.7 with SMTP id n7mr5655390ice.381.1287608248004; Wed, 20 Oct 2010 13:57:28 -0700 (PDT)
Received: from [172.28.172.161] ([65.91.54.2]) by mx.google.com with ESMTPS id f18sm266962vcm.35.2010.10.20.13.57.25 (version=SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 13:57:27 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Wed, 20 Oct 2010 13:57:21 -0700
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Message-ID: <C8E4A5C1.102E3%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: ActwmWNkOtREesKARE678FrnFi7UBA==
In-Reply-To: <alpine.DEB.1.10.1010202249170.29868@uplift.swm.pp.se>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 20:55:57 -0000

Mikael,

Fair enough.. As noted to Gert, it was "an" idea, and it's already off the
table.. It was just a discussion point.

I agree, I don't think anyone is going there (it seems to be a well
understood principle).  But as you said, since the RFC comments on it, it
would in fact be an RFC update.

Regards,

Victor


On 20/10/10 1:52 PM, "Mikael Abrahamsson" <swmike@swm.pp.se> wrote:

> On Wed, 20 Oct 2010, Victor Kuarsingh wrote:
> 
>> We are not changing 6to4... It's status quo.. We are just adding an new
>> layer to improve created a deterministic path (with loss of e2e).
> 
> No, 6to4 specifically prohibits more specifics in 2002::/16, to quote
> RFC3056:
> 
> "6to4 prefixes more specific than 2002::/16 must not be propagated in
>     native IPv6 routing, to prevent pollution of the IPv6 routing table
>     by elements of the IPv4 routing table. "
> 
>> The longer then /16 route is not a mod either, it's a global agreement issue
>> (will we accept longer then /16 for 2002::).
> 
> The RFC prohibits this, so what you're asking for is a change of the RFC.
> 
> We're not going there, period.



From prvs=902b287ac=Scott.Beuker@sjrb.ca  Wed Oct 20 14:08:43 2010
Return-Path: <prvs=902b287ac=Scott.Beuker@sjrb.ca>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A2A8A3A67FB for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 14:08: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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QR1mcAlnXp+U for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 14:08:41 -0700 (PDT)
Received: from prdcg4ipta02x-ext.shaw.ca (prdcg4ipta02x-ext.shaw.ca [204.209.208.147]) by core3.amsl.com (Postfix) with ESMTP id B193C3A6933 for <v6ops@ietf.org>; Wed, 20 Oct 2010 14:08:41 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.57,357,1283752800"; d="scan'208";a="154937167"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 20 Oct 2010 15:09:56 -0600
Message-ID: <1EA76BAD7F050648910C041BDDED8CD5013FDBB1@PRDCG4EXVW01-5.OSS.PRD>
In-Reply-To: <D9571054-81AA-4439-A4AC-B9D9711BC673@employees.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops]I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: ActwllgmMTsof+nGRcCpdgvDN+oHIwAAZd2A
References: <C8E48A47.102AB%victor.kuarsingh@gmail.com><81414319-C5A7-430E-9EE8-B9F105401D76@employees.org><1EA76BAD7F050648910C041BDDED8CD5013FDBAE@PRDCG4EXVW01-5.OSS.PRD><B95D067E-BA26-4EFF-9659-C75BD084D603@employees.org><1EA76BAD7F050648910C041BDDED8CD5013FDBAF@PRDCG4EXVW01-5.OSS.PRD> <D9571054-81AA-4439-A4AC-B9D9711BC673@employees.org>
From: "Scott Beuker" <Scott.Beuker@sjrb.ca>
To: "Ole Troan" <otroan@employees.org>
X-OriginalArrivalTime: 20 Oct 2010 21:09:56.0844 (UTC) FILETIME=[25E8B2C0:01CB709B]
X-TM-AS-Product-Ver: SMEX-8.0.0.1285-6.500.1024-17716.001
X-TM-AS-Result: No--23.111200-0.000000-31
X-TM-AS-User-Approved-Sender: Yes
X-TM-AS-User-Blocked-Sender: No
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 21:08:43 -0000

> I'm sure you can provide some better numbers, but am I correct in
> assuming that:
>  - you have an huge set of CPEs that are IPv4 only

Correct.

>  - you have a small set of CPEs supporting 6to4

Correct, and this number continues to grow.

>  - you have a tiny set of those CPEs doing 6to4 by default

I'm not sure "tiny" is accurate; we're not entirely sure yet. We know
there's "some", and this number continues to grow.

>  - you have a small set of CPEs supporting 6rd and native IPv6

Incorrect.

By my estimation, we have approximately 0 CPEs support 6RD. Of course,
this number will grow, which is why we plan to support 6RD and would
prefer it over any form of 6to4. But that doesn't mean we don't have a
use case for 6to4.

I could guess and hope that this wouldn't happen, because we'd get
native IPv6 out to 100% of our customers before any of them want/need
it, but doing so and being wrong could get me fired. And when we are
able to get native IPv6 to our customers is indeed beyond my control,
and beyond the company I work for's control too.

I'm truly unsure of where we're at with native IPv6 support in CPE
gateways, but I hope we can agree it's worryingly low today, and it's
not something consumers are apt to replace every 12 months.


>=20
> what I don't quite understand is why the focus on plan C for a
> presumably tiny set of customers. when the big elephant in the room is
> the IPv4 only CPEs.

Because where I work we worry about 100% of our customers. Trying to
improve upon 6to4 does not impede in any way my work towards deploying
native IPv6 nor 6RD. Not even slightly. As Victor has pointed out,
though this solution is applicable for a small subset of customers, it
also requires a small amount of work to get up and running, very small
in fact. So it's worthwhile.

On the other hand, who knows how many 6to4 CPEs will be out there a year
from now? We know this number is growing, because we know 6to4 enabled
CPE devices continue to sit on store shelves. Until they're gone, a
reasonable person expects this number to grow as consumers continue to
replace their CPEs through the natural life cycle (aka power surges and
dust).


>=20
> offer a patch for the 6to4 by default CPEs, encourage the users to
> upgrade to 6rd/native IPv6 CPEs, which is something I would think has
to
> happen anyway...

I'm just going to assume this paragraph was written tongue-in-cheek.

Thanks,
Scott



From tena@huawei.com  Wed Oct 20 14:39:17 2010
Return-Path: <tena@huawei.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 647323A68D2 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 14:39:03 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U010QtMRbMKS for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 14:38:56 -0700 (PDT)
Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180]) by core3.amsl.com (Postfix) with ESMTP id 0AA943A6916 for <v6ops@ietf.org>; Wed, 20 Oct 2010 14:38:47 -0700 (PDT)
Received: from huawei.com (usaga04-in [172.18.4.101]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LAL00LHUYV6TJ@usaga04-in.huawei.com> for v6ops@ietf.org; Wed, 20 Oct 2010 16:40:18 -0500 (CDT)
Received: from TingZousc1 ([10.193.34.160]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LAL006ZHYV1J2@usaga04-in.huawei.com> for v6ops@ietf.org; Wed, 20 Oct 2010 16:40:18 -0500 (CDT)
Date: Wed, 20 Oct 2010 14:40:12 -0700
From: Tina Tsou <tena@huawei.com>
In-reply-to: <C8E463CE.10282%vicmank@rogers.com>
To: 'Victor Kuarsingh' <vicmank@rogers.com>, 'Gert Doering' <gert@space.net>,  'Victor Kuarsingh' <victor.kuarsingh@rci.rogers.com>
Message-id: <01ac01cb709f$632940b0$297bc210$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: ActwchRWp6LHzAJonk6asl48t4owkwALMz9Q
References: <20101020155154.GP32268@Space.Net> <C8E463CE.10282%vicmank@rogers.com>
Cc: 'IPv6 Operations' <v6ops@ietf.org>, draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 21:39:17 -0000
X-List-Received-Date: Wed, 20 Oct 2010 21:39:17 -0000

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


-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of
Victor Kuarsingh
Sent: Wednesday, October 20, 2010 9:16 AM
To: Gert Doering; Victor Kuarsingh
Cc: IPv6 Operations;
draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org
Subject: Re: [v6ops] I-D
Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt

Gert,

IPv6 is not possible everywhere immediately (vendors have been selling us
IPv4-only upto this day).  I can go to the local store and maybe find one or
two boxes that do native IPv6 (the world we live in).

6RD is good, but again, I cannot force an unmanaged device to support
something.  
[Then you may consider using this 
draft-tsou-softwire-gwinit-6rd-00  "Gateway-Initiated" 6rd]

Where I can, I would do this...  For all others, IPv4 (based on
what was sold and what people picked up at their local best buy) with
existing capabilities IS what we have in the near future.

On a side point:

Having customers configure something themselves... we are talking about a
customer base with varying degrees of capabilities (some have trouble
logging on).  I do not think comparing "our" (IETFers and like technical
folks) capabilities to make something work as a template to what can be done
in a production network.. I assume (based on experience) that most customers
will do nothing other the plug it in and turn it on.

Victor


On 20/10/10 8:51 AM, "Gert Doering" <gert@space.net> wrote:

> Hi,
> 
> On Tue, Oct 19, 2010 at 05:48:51PM -0400, Victor Kuarsingh wrote:
>> On a side note then, I am happy to entertain additional input as to what
an
>> "operator" can do for the following use case.
>> 
>> - Post IPv6 ramp up / IPv4 runout
>> - consumer is on IPv4-only (based on access network, home CPE etc)
> 
> "enable IPv6 there"
> 
> If that's not viable, offer 6rd or configured tunnels.
> 
> Gert Doering
>         -- NetMaster


_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops


From brian.e.carpenter@gmail.com  Wed Oct 20 15:53:01 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B4CD3A682F for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 15:53:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fwVTnlSnuCjC for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 15:53:00 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id 46A8D3A680D for <v6ops@ietf.org>; Wed, 20 Oct 2010 15:53:00 -0700 (PDT)
Received: by qyk36 with SMTP id 36so1778108qyk.10 for <v6ops@ietf.org>; Wed, 20 Oct 2010 15:54:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=1J/wy2CB2IlPRuETd9DQKDZsXDGH0PRZkfAWc44KgSk=; b=aRiwPX1nhyiixN6fmOlqEBCLqtgQpnYB/JkguUEQE0EJFyaVc1Ql/Xq3+2jX754vK/ I08R77hahwnGIgq6TjH1HOxnuZpG066Sp0ldiDacmC3365EIbLkVLDesevhB/6Um97Z5 thlyz2+aPjXkKmLfoeUb+Cp2VTVWuzojtcC3M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=Y6qCYgrC7ClVvJv27FbuhzMuX6E6+20HiWdGf6U0Wtgd/GTPLAh+fz+sJe8cRpGrvv B0HLrJmXzB6P0FHufiriwzA1FfnmFyg0cJb0HqdnPj47fGKemxZvHwA41LjCWYRmMUre Q9QVnv/i/2VeUGzj5+Imaw7+KCs5NwZCTy0rc=
Received: by 10.224.196.131 with SMTP id eg3mr2723qab.183.1287615274221; Wed, 20 Oct 2010 15:54:34 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id m10sm335133vcf.21.2010.10.20.15.54.31 (version=SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 15:54:33 -0700 (PDT)
Message-ID: <4CBF7326.5080607@gmail.com>
Date: Thu, 21 Oct 2010 11:54:30 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>
References: <C8E47308.10299%victor.kuarsingh@gmail.com>
In-Reply-To: <C8E47308.10299%victor.kuarsingh@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: [v6ops] Economic incentive for 2002::/16 [was draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt]
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 22:53:01 -0000

On 2010-10-21 06:20, Victor Kuarsingh wrote:
> James,
> 
> I agree, if we can get 6to4 relays out there in mass, then the challenges go
> away or are subsided.  Unfortunately this is a theoretical position at this
> point (having everyone do something for the good of all),

No. An ISP operating a 6to4 relay and advertising a 2002::/16 route to it
is acting entirely in the interests of that ISP's native IPv6 customers,
especially if they are content providers. The economic incentive in this
case is not misplaced.

Our confusion comes from thinking of the placement of the IPv4 side of the
relays as important. It isn't; it's the placement of the IPv6 side of
the relays that affects the return path from servers to 6to4 clients.

The paradoxical moral is that all ISPs operating IPv6 services have an
incentive to operate a 6to4 relay, even though they have no 6to4 customers.
This is the message we have failed to convey.

   Brian

From brian.e.carpenter@gmail.com  Wed Oct 20 15:56:36 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2556B3A68B2 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 15:56:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.512
X-Spam-Level: 
X-Spam-Status: No, score=-103.512 tagged_above=-999 required=5 tests=[AWL=0.952, BAYES_00=-2.599, GB_I_LETTER=-2, SARE_SUB_OBFU_OTHER=0.135, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qxkNGGHXGTzJ for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 15:56:30 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id A05663A682F for <v6ops@ietf.org>; Wed, 20 Oct 2010 15:56:27 -0700 (PDT)
Received: by qwc9 with SMTP id 9so2983974qwc.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 15:58:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=kFH7NSlQ2c8UFeMp4SNJZPMPoVTowmdNAKR8hrZDq+c=; b=Eod62N5oxO6vtHF+iffKM7jU0XyiPyKx7jdLxBsC6xxPOxJz6pSIe7ee6tZTJukQqS ho8a9bU6h+88dmrUzb2737EFtzSQo0UFw/96qHC/F0i81u4kjchlSJ+lbBQJkUf1m7Km Vg1gFa3N/jcwshFPmMBzePXWNY3v8AM+TSvuI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=OmYyTaKo2dJj25hhwrzLEZjixKsxdXSFNgfKYzx7OFqXbRFatHllAfaj374bFwl0Oz Gwtw681FVLOD9t+BxUGm1mhDno1Si1tVPDcDZ0vnhmXpDe/DUtWrY2UIcWkX6pAs9Xtp 6QUBsKEJfm1/zUxKG3Og2Mmv8D9kDy4GC0igs=
Received: by 10.224.137.130 with SMTP id w2mr14169qat.112.1287615481434; Wed, 20 Oct 2010 15:58:01 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id l14sm337631vcr.42.2010.10.20.15.57.58 (version=SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 15:58:01 -0700 (PDT)
Message-ID: <4CBF73F5.2050502@gmail.com>
Date: Thu, 21 Oct 2010 11:57:57 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Philip Homburg <pch-v6ops@u-1.phicoh.com>
References: <m1P8dRc-0001gOC@stereo.hq.phicoh.net>
In-Reply-To: <m1P8dRc-0001gOC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: [v6ops] 2002:xxyy::/32 [was draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt]
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 22:56:37 -0000

On 2010-10-21 07:31, Philip Homburg wrote:
> In your letter dated Wed, 20 Oct 2010 10:20:56 -0700 you wrote:
>> I agree, if we can get 6to4 relays out there in mass, then the challenges go
>> away or are subsided.  Unfortunately this is a theoretical position at this
>> point (having everyone do something for the good of all), and one cannot
>> build a real network on the notion that "I hope everyone does this".
> 
> A simple hack to get the return traffic is for an ISP that has for example an
> IPv4 /16, to put 2002:xxyy::/32 in the IPv6 routing table. This causes all of
> the return traffic for that ISP's 6to4 customers to take the right route
> back over the IPv6 backbone.
> 
> Of course, everybody will officially hate you for doing that because it causes
> more entries in the IPv6 routing table. But is a purely local solution that
> you can use to get your customers IPv6 connected.

I remember the authors of 6to4 being severely roasted by an Ops Area
Director (a certain Mr R. Bush) to ensure that RFC 3056 declared this
illegal, immoral and fattening. But I guess it could be used locally,
as long as it never appears in BGP4.

Regards
   Brian Carpenter

From john_brzozowski@cable.comcast.com  Wed Oct 20 15:59:48 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 834E53A680D for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 15:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.262
X-Spam-Level: 
X-Spam-Status: No, score=-107.262 tagged_above=-999 required=5 tests=[AWL=0.601, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FQojVpjFwfj1 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 15:59:45 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 79F253A657C for <v6ops@ietf.org>; Wed, 20 Oct 2010 15:59:45 -0700 (PDT)
Received: from ([24.40.55.40]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.100627561; Wed, 20 Oct 2010 19:01:16 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by pacdcexhub03.cable.comcast.com ([fe80::d1dd:b302:b617:3755%12]) with mapi id 14.01.0255.000; Wed, 20 Oct 2010 19:01:16 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: "Brian E. Carpenter" <brian.e.carpenter@gmail.com>, Victor Kuarsingh <victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] Economic incentive for 2002::/16 [was draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt]
Thread-Index: AQHLcKqzNv6Mb40H0UmCJShm1ulung==
Date: Wed, 20 Oct 2010 23:01:15 +0000
Message-ID: <C8E4ECF9.2A6CE%john_brzozowski@cable.comcast.com>
In-Reply-To: <4CBF7326.5080607@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <13609593D0B9514F85E122960B6A9B06@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] Economic incentive for 2002::/16 [was draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt]
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 22:59:48 -0000

+1 except for the IPv4 comments.  From what we are seeing, operators should
not announce their relays publicly over IPv4.  Open 6to4 relays seem to
yield undesirable behavior.  I agree, from experience, that operators shoul=
d
offer 6to4 relays especially if they have users attempting to use the same.

John

On 10/20/10 6:54 PM, "Brian E. Carpenter" <brian.e.carpenter@gmail.com>
wrote:

> On 2010-10-21 06:20, Victor Kuarsingh wrote:
>> James,
>>=20
>> I agree, if we can get 6to4 relays out there in mass, then the challenge=
s go
>> away or are subsided.  Unfortunately this is a theoretical position at t=
his
>> point (having everyone do something for the good of all),
>=20
> No. An ISP operating a 6to4 relay and advertising a 2002::/16 route to it
> is acting entirely in the interests of that ISP's native IPv6 customers,
> especially if they are content providers. The economic incentive in this
> case is not misplaced.
>=20
> Our confusion comes from thinking of the placement of the IPv4 side of th=
e
> relays as important. It isn't; it's the placement of the IPv6 side of
> the relays that affects the return path from servers to 6to4 clients.
>=20
> The paradoxical moral is that all ISPs operating IPv6 services have an
> incentive to operate a 6to4 relay, even though they have no 6to4 customer=
s.
> This is the message we have failed to convey.
>=20
>    Brian
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

=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
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From victor.kuarsingh@gmail.com  Wed Oct 20 16:27:39 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E44E93A68EC for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 16:27:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.503
X-Spam-Level: 
X-Spam-Status: No, score=-3.503 tagged_above=-999 required=5 tests=[AWL=0.962,  BAYES_00=-2.599, GB_I_LETTER=-2, SARE_SUB_OBFU_OTHER=0.135]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MRkbT9jTVr5i for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 16:27:39 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id DF9543A68EB for <v6ops@ietf.org>; Wed, 20 Oct 2010 16:27:38 -0700 (PDT)
Received: by ywa6 with SMTP id 6so2651826ywa.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 16:29:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=EF5YC2iAvwJ9IqFdcFWf0muEJkLALOBVqlxW25ifgOo=; b=e5W0ulDnwOwqkj9yoojuvcMfVklXnPFAA/5Fers847d0uVz203fnEToyag8Y/GGuve s84Qo+lve/nj80UPPigH7Htr+6n9EEOsNXWPPrGV2bEUe71m1J/PP2B/GQVc0MNa0Nwr qU+plOy1Ol6TVqsj2e4BtqCciTs3EVLXy4OhU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=X9JMfP3xLEsRDL2MqxfvNHeA4IwDX4GfainhuaE5Y512l7hseoLSaXn1IhvHe7WH1C bEZMl9Zq8Adxk1AUvSG32sBR5TLvoQP+5ci2xqzlVDecT06BKenHcvV9wx2BDIb1DMd0 wnijizMdiznMrL9KuYabhRWNhFyD9FjXYewOc=
Received: by 10.150.159.19 with SMTP id h19mr2268595ybe.340.1287617352744; Wed, 20 Oct 2010 16:29:12 -0700 (PDT)
Received: from [172.28.172.161] ([65.91.54.2]) by mx.google.com with ESMTPS id n48sm636903yha.7.2010.10.20.16.29.11 (version=SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 16:29:12 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Wed, 20 Oct 2010 16:29:07 -0700
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Philip Homburg <pch-v6ops@u-1.phicoh.com>
Message-ID: <C8E4C953.102F5%victor.kuarsingh@gmail.com>
Thread-Topic: 2002:xxyy::/32 [was draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt]
Thread-Index: Actwrpb9ISV+S54A1kiw2+gPi/hPEA==
In-Reply-To: <4CBF73F5.2050502@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] 2002:xxyy::/32 [was draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt]
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 23:27:40 -0000

Brian,

Thanks for the background.  Now that was a long time ago (in IP years) and
since times have changed and we are looking at solving problems of today, do
you think this position may open to further debate?  As noted in your
example, an ISP can guide traffic for blocks upto a [IPv4]/16 or shorter
with routes in the IPv6 space which are upto [IPv6]/32s. (although this does
not help those who have blocks smaller then /16s - say a small ISP with a
/19, /20 etc)

Just asking.. I think this tangent conversation is very contentious.. But
new problems (i.e. IPv4 run out, lagging CPE capabilities, IPv6 only
endpoint threat) require new idea...

Don't shoot me.. just a question.. I will go hide now..

Regards,

Victor


On 20/10/10 3:57 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
wrote:

> 
> On 2010-10-21 07:31, Philip Homburg wrote:
>> In your letter dated Wed, 20 Oct 2010 10:20:56 -0700 you wrote:
>>> I agree, if we can get 6to4 relays out there in mass, then the challenges go
>>> away or are subsided.  Unfortunately this is a theoretical position at this
>>> point (having everyone do something for the good of all), and one cannot
>>> build a real network on the notion that "I hope everyone does this".
>> 
>> A simple hack to get the return traffic is for an ISP that has for example an
>> IPv4 /16, to put 2002:xxyy::/32 in the IPv6 routing table. This causes all of
>> the return traffic for that ISP's 6to4 customers to take the right route
>> back over the IPv6 backbone.
>> 
>> Of course, everybody will officially hate you for doing that because it
>> causes
>> more entries in the IPv6 routing table. But is a purely local solution that
>> you can use to get your customers IPv6 connected.
> 
> I remember the authors of 6to4 being severely roasted by an Ops Area
> Director (a certain Mr R. Bush) to ensure that RFC 3056 declared this
> illegal, immoral and fattening. But I guess it could be used locally,
> as long as it never appears in BGP4.
> 
> Regards
>    Brian Carpenter



From Jean-Francois.TremblayING@videotron.com  Wed Oct 20 17:08:34 2010
Return-Path: <Jean-Francois.TremblayING@videotron.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DED443A6821; Wed, 20 Oct 2010 17:08:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[AWL=0.677,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ATZJ2CN-dIEO; Wed, 20 Oct 2010 17:08:33 -0700 (PDT)
Received: from mx01.videotron.com (mx01.videotron.com [24.201.243.152]) by core3.amsl.com (Postfix) with ESMTP id D4F7B3A657C; Wed, 20 Oct 2010 17:08:33 -0700 (PDT)
In-Reply-To: <4CBF7326.5080607@gmail.com>
To: brian.e.carpenter@gmail.com
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006
Message-ID: <OF41D1A9C1.6ED93732-ON852577C2.00837F4F-852577C3.0000E8F9@videotron.com>
From: Jean-Francois.TremblayING@videotron.com
Date: Wed, 20 Oct 2010 20:09:53 -0400
X-MIMETrack: Serialize by Router on DOMMTL11/SRV/GVL(Release 7.0.2FP1|January 10, 2007) at 2010-10-20 20:09:56, Serialize complete at 2010-10-20 20:09:56
Content-Type: multipart/alternative; boundary="=_alternative 0000E8F8852577C3_="
Cc: IETF V6OPS WG <v6ops@ietf.org>, v6ops-bounces@ietf.org
Subject: [v6ops] RE  Economic incentive for 2002::/16
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 00:08:35 -0000

Message en plusieurs parties au format MIME
--=_alternative 0000E8F8852577C3_=
Content-Type: text/plain; charset="US-ASCII"

> No. An ISP operating a 6to4 relay and advertising a 2002::/16 route to 
it
> is acting entirely in the interests of that ISP's native IPv6 customers,
> especially if they are content providers. The economic incentive in this
> case is not misplaced.

Brian, I am not sure I fully agree with you here. It might be true if 
2002::/16 is densely advertised, but if it is sparsely like it is now, 
announcing 2002::/16 will attrack return traffic from neighboring ASes. 

The resulting IPv4 traffic is very likely not destined to my own AS. If 
that traffic is through transit (paying) rather than peering (as in free), 

it means I'm actually paying *twice* to send it over my transit links, 
not counting the impact of the additional bandwitdth usage. 

Arguably, 6to4 traffic is not large enough to affect any large ISP's 
bottom line. But I'll have a hard time convincing my management to 
advertise a relay that cost us twice the usual transit fee. The 
"for the better good of the Internet" argument will probably not fly 
here. On the other side, local advertisement is easily justifiable. 

-> Flames here if I got my BGP-fu wrong... 

JF

--=_alternative 0000E8F8852577C3_=
Content-Type: text/html; charset="US-ASCII"


<br>
<br><tt><font size=2>&gt; No. An ISP operating a 6to4 relay and advertising
a 2002::/16 route to it<br>
&gt; is acting entirely in the interests of that ISP's native IPv6 customers,<br>
&gt; especially if they are content providers. The economic incentive in
this<br>
&gt; case is not misplaced.<br>
<br>
Brian, I am not sure I fully agree with you here. It might be true if </font></tt>
<br><tt><font size=2>2002::/16 is densely advertised, but if it is sparsely
like it is now, </font></tt>
<br><tt><font size=2>announcing 2002::/16 will attrack return traffic from
neighboring ASes. </font></tt>
<br>
<br><tt><font size=2>The resulting IPv4 traffic is very likely not destined
to my own AS. If </font></tt>
<br><tt><font size=2>that traffic is through transit (paying) rather than
peering (as in free), </font></tt>
<br><tt><font size=2>it means I'm actually paying *twice* to send it over
my transit links, </font></tt>
<br><tt><font size=2>not counting the impact of the additional bandwitdth
usage. </font></tt>
<br>
<br><tt><font size=2>Arguably, 6to4 traffic is not large enough to affect
any large ISP's </font></tt>
<br><tt><font size=2>bottom line. But I'll have a hard time convincing
my management to </font></tt>
<br><tt><font size=2>advertise a relay that cost us twice the usual transit
fee. The </font></tt>
<br><tt><font size=2>&quot;for the better good of the Internet&quot; argument
will probably not fly </font></tt>
<br><tt><font size=2>here. On the other side, local advertisement is easily
justifiable. </font></tt>
<br>
<br><tt><font size=2>-&gt; Flames here if I got my BGP-fu wrong... </font></tt>
<br>
<br><tt><font size=2>JF</font></tt>
<br>
--=_alternative 0000E8F8852577C3_=--

From brian.e.carpenter@gmail.com  Wed Oct 20 17:26:16 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 426113A6919; Wed, 20 Oct 2010 17:26:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.585
X-Spam-Level: 
X-Spam-Status: No, score=-102.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tc6ZX0BcOjmm; Wed, 20 Oct 2010 17:26:15 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 0923E3A68FB; Wed, 20 Oct 2010 17:26:14 -0700 (PDT)
Received: by vws12 with SMTP id 12so2635333vws.31 for <multiple recipients>; Wed, 20 Oct 2010 17:27:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=f25ZWJoN3Fv8/bQjQ3EcOtaiitB4xm54nB3mnsg+K6A=; b=pQ7Jp0lo65294bHcWdop79nZQTBTAse8GzBm451JVqtDJ35lqwKuf43L+dK8CW7jDC jxbE58jKssFf9x98zr94YeQ5XYeU7trjFF6QK7VCPmm7oAnJ9Ow+Y60mS6NqFjkVyV8Y YEDTdZIw3Zlj8fjNUKgTI/+sJdp/UmAGjqfgc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=nwIAtQ1HVF7cTTSFqHztMIGzyYVQFYUAfZH5atZ31JgVhnvCR/mlNP44lg65ym2tE5 Bn52Ied+NmS7U1lpASESUQrwLbsKmsj+B/AUcHZ3WAnc3J0kEcFndQKHvwabdphhftD9 dD9XNYBNS2CHOkviK87cXPVc9EHiyiejyHuyo=
Received: by 10.220.159.196 with SMTP id k4mr24644vcx.196.1287620868979; Wed, 20 Oct 2010 17:27:48 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id y21sm482702vbx.6.2010.10.20.17.27.46 (version=SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 17:27:48 -0700 (PDT)
Message-ID: <4CBF890B.6030300@gmail.com>
Date: Thu, 21 Oct 2010 13:27:55 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Jean-Francois.TremblayING@videotron.com
References: <OF41D1A9C1.6ED93732-ON852577C2.00837F4F-852577C3.0000E8F9@videotron.com>
In-Reply-To: <OF41D1A9C1.6ED93732-ON852577C2.00837F4F-852577C3.0000E8F9@videotron.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF V6OPS WG <v6ops@ietf.org>, v6ops-bounces@ietf.org
Subject: Re: [v6ops] RE  Economic incentive for 2002::/16
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 00:26:16 -0000

On 2010-10-21 13:09, Jean-Francois.TremblayING@videotron.com wrote:
>> No. An ISP operating a 6to4 relay and advertising a 2002::/16 route to 
> it
>> is acting entirely in the interests of that ISP's native IPv6 customers,
>> especially if they are content providers. The economic incentive in this
>> case is not misplaced.
> 
> Brian, I am not sure I fully agree with you here. It might be true if 
> 2002::/16 is densely advertised, but if it is sparsely like it is now, 
> announcing 2002::/16 will attrack return traffic from neighboring ASes. 

I wouldn't advocate announcing it in BGP4, for that reason. Just announce
it in the ISP's IGP, for its own customers.

OK, this needs a draft, but that won't happen until after Beijing.

   Brian
> 
> The resulting IPv4 traffic is very likely not destined to my own AS. If 
> that traffic is through transit (paying) rather than peering (as in free), 
> 
> it means I'm actually paying *twice* to send it over my transit links, 
> not counting the impact of the additional bandwitdth usage. 
> 
> Arguably, 6to4 traffic is not large enough to affect any large ISP's 
> bottom line. But I'll have a hard time convincing my management to 
> advertise a relay that cost us twice the usual transit fee. The 
> "for the better good of the Internet" argument will probably not fly 
> here. On the other side, local advertisement is easily justifiable. 
> 
> -> Flames here if I got my BGP-fu wrong... 
> 
> JF
> 

From brian.e.carpenter@gmail.com  Wed Oct 20 17:29:44 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 072CB3A6930 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 17:29:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.285
X-Spam-Level: 
X-Spam-Status: No, score=-102.285 tagged_above=-999 required=5 tests=[AWL=-0.286, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k-+uFZbO1EP8 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 17:29:42 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id A372D3A657C for <v6ops@ietf.org>; Wed, 20 Oct 2010 17:29:42 -0700 (PDT)
Received: by vws12 with SMTP id 12so2636476vws.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 17:31:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=XjeNC0Tn9KCfGl70mmYYaFGa4WD1Jd1xyG/pr2xlj9w=; b=IVXBEnVtg66548NnUrzCFOlXNkBrVM3yGHvryJjzCwEKwNgZE6lifflDIMgs6N/lEi hDuXp0WxEqL0SP2HK0TlV2fCPBsB7VKKQ/Aeu6wzM3o6Y8kcKOICacsec3cZNYMOCMQv Rgew8IFyfGc3ly4wTS1JWkstIqVrCk3kvsHGc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=S7zOBKk7S0nmLpsBVzxqoD5m7nKtcjtM+6NEkJxf9qvCsTeT1zRPfPTf0dABeG02to iTznFGWoA07YnfVXCLAMeKFL+R5PCm51SHFYa4Mch/EBepEKtdVfeuhnJQzSthfR5b9G zE9C/SktoPE8hwcQniAhp/VIc4V0AYSP2isz8=
Received: by 10.220.189.11 with SMTP id dc11mr35659vcb.39.1287621075308; Wed, 20 Oct 2010 17:31:15 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id f18sm392384vcm.11.2010.10.20.17.31.13 (version=SSLv3 cipher=RC4-MD5); Wed, 20 Oct 2010 17:31:14 -0700 (PDT)
Message-ID: <4CBF89DA.2070007@gmail.com>
Date: Thu, 21 Oct 2010 13:31:22 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
References: <C8E4ECF9.2A6CE%john_brzozowski@cable.comcast.com>
In-Reply-To: <C8E4ECF9.2A6CE%john_brzozowski@cable.comcast.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] Economic incentive for 2002::/16 [was draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt]
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 00:29:44 -0000

John,

I agree. The 6to4 client will try to find a benevolent relay as close
as possible; if they fail to find one, they will never show up
as 6to4 users anyway. "Destination unreachable" for 192.88.99.1
would kill the problem at source.

Regards
   Brian Carpenter

On 2010-10-21 12:01, Brzozowski, John wrote:
> +1 except for the IPv4 comments.  From what we are seeing, operators should
> not announce their relays publicly over IPv4.  Open 6to4 relays seem to
> yield undesirable behavior.  I agree, from experience, that operators should
> offer 6to4 relays especially if they have users attempting to use the same.
> 
> John
> 
> On 10/20/10 6:54 PM, "Brian E. Carpenter" <brian.e.carpenter@gmail.com>
> wrote:
> 
>> On 2010-10-21 06:20, Victor Kuarsingh wrote:
>>> James,
>>>
>>> I agree, if we can get 6to4 relays out there in mass, then the challenges go
>>> away or are subsided.  Unfortunately this is a theoretical position at this
>>> point (having everyone do something for the good of all),
>> No. An ISP operating a 6to4 relay and advertising a 2002::/16 route to it
>> is acting entirely in the interests of that ISP's native IPv6 customers,
>> especially if they are content providers. The economic incentive in this
>> case is not misplaced.
>>
>> Our confusion comes from thinking of the placement of the IPv4 side of the
>> relays as important. It isn't; it's the placement of the IPv6 side of
>> the relays that affects the return path from servers to 6to4 clients.
>>
>> The paradoxical moral is that all ISPs operating IPv6 services have an
>> incentive to operate a 6to4 relay, even though they have no 6to4 customers.
>> This is the message we have failed to convey.
>>
>>    Brian
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
> 
> =========================================
> John Jason Brzozowski
> Comcast Cable
> e) mailto:john_brzozowski@cable.comcast.com
> o) 609-377-6594
> m) 484-962-0060
> w) http://www.comcast6.net
> =========================================
> 
> 

From cancanhuang110@gmail.com  Wed Oct 20 17:55:19 2010
Return-Path: <cancanhuang110@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4219E3A68A2 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 17:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.642
X-Spam-Level: 
X-Spam-Status: No, score=-1.642 tagged_above=-999 required=5 tests=[AWL=0.356,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_34=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3XCRyF5aoL2N for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 17:55:18 -0700 (PDT)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by core3.amsl.com (Postfix) with ESMTP id 3670F3A657C for <v6ops@ietf.org>; Wed, 20 Oct 2010 17:55:07 -0700 (PDT)
Received: by bwz12 with SMTP id 12so8504bwz.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 17:56:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=hsOFUFvRxkm5UyjlxX4mSH2vMeWWBt8HU6Y6JSLYkCA=; b=h8NCFG/MxOwpdO1Vc/cM7dn1/vPIv+v7Uz8pd0kEdw+ztqDVDF6BCTNiYEAAaNtT8V 5Nes7R/MD3BfM4r9MVxWv1IlkZTKDpfqzwye7lUzqiDKjK20coFj9uDkhOjUi1k5ECpv DrfK7orI6D+zTSPgcIEOgDKhoAzg/79SrguVM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=YHD2eltV/q0IAbyJP4/22YpAMrm4kFbmN2KPwi0WjzhPwyRrXYbWwmXxilCkFZd+4x 9/pgteg7pKktzdTkRPrL1i1vSzheqf43DZ+5f76NTbyRSw0Rcx4EcYbK7djaBwVzr5KZ za7GwsTWr6DFyZwDA83sD81JeBYt29jtlZ/Is=
MIME-Version: 1.0
Received: by 10.204.84.156 with SMTP id j28mr93525bkl.101.1287622598576; Wed, 20 Oct 2010 17:56:38 -0700 (PDT)
Received: by 10.204.176.140 with HTTP; Wed, 20 Oct 2010 17:56:38 -0700 (PDT)
In-Reply-To: <AANLkTikajZTFOZRJ-cBUtmcQMOsSpoHenqXn6t7nugx4@mail.gmail.com>
References: <AANLkTikajZTFOZRJ-cBUtmcQMOsSpoHenqXn6t7nugx4@mail.gmail.com>
Date: Thu, 21 Oct 2010 08:56:38 +0800
Message-ID: <AANLkTi=7YNPC-fm6eawBYKS2=4wHb1+DFAYUiSBpc2yg@mail.gmail.com>
From: huang cancan <cancanhuang110@gmail.com>
To: v6ops@ietf.org
Content-Type: multipart/alternative; boundary=001636c9236297cb4e049315ffc7
Subject: [v6ops] Updated draft notification: draft-huang-v6ops-v4v6tran-bb-usecase-01
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 00:55:19 -0000

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

Dear all:

  draft-huang-v6ops-v4v6tran-bb-usecase-01 was successfully submitted.

  This draft describes a use case for the migration from IPv4 to IPv6 for
one of the typical broadband network. The content is orgnized by various
scenarios we can foresee during the migration.

   Thank for all the previous comments from you: Guoliang, Fred, Remmi,
Yiu,Tina , Cathy, Tom Taylor,Jason......

   I am still looking forward the kindly check and comments from all of you.

   Thank you very much!

Cancan Huang
China Telecom

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

<div class=3D"gmail_quote"><br>
<div>Dear all:</div>
<div>=A0 </div>
<div>=A0 draft-huang-v6ops-v4v6tran-bb-usecase-01 was successfully submitte=
d.=A0=A0=A0</div>
<div>=A0 </div>
<div>=A0 This draft describes a use case for the migration from IPv4 to IPv=
6 for one of the typical broadband network. The content is orgnized by vari=
ous scenarios we can foresee during the migration.</div>
<div>=A0 </div>
<div>=A0=A0 Thank for all the previous comments from you: Guoliang, Fred, R=
emmi, Yiu,Tina , Cathy, Tom Taylor,Jason......</div>
<div>=A0 </div>
<div>=A0=A0 I am still looking forward the kindly check and comments from a=
ll of you.</div>
<div>=A0</div>
<div>=A0=A0 Thank you very much!</div>
<div>=A0</div><font color=3D"#888888">
<div>Cancan Huang</div>
<div>China Telecom</div>
<div>=A0</div>
<div>=A0</div></font></div><br>

--001636c9236297cb4e049315ffc7--

From Jean-Francois.TremblayING@videotron.com  Wed Oct 20 17:56:09 2010
Return-Path: <Jean-Francois.TremblayING@videotron.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BBBB13A6934; Wed, 20 Oct 2010 17:56:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.057
X-Spam-Level: 
X-Spam-Status: No, score=-2.057 tagged_above=-999 required=5 tests=[AWL=0.541,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UVyR8I4C26dk; Wed, 20 Oct 2010 17:56:07 -0700 (PDT)
Received: from mx01.videotron.com (mx01.videotron.com [24.201.243.152]) by core3.amsl.com (Postfix) with ESMTP id DFF8F3A657C; Wed, 20 Oct 2010 17:56:06 -0700 (PDT)
In-Reply-To: <D9571054-81AA-4439-A4AC-B9D9711BC673@employees.org>
To: otroan@employees.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006
Message-ID: <OF2AB7BBCF.1DF4A3EC-ON852577C3.0001FC71-852577C3.000543D9@videotron.com>
From: Jean-Francois.TremblayING@videotron.com
Date: Wed, 20 Oct 2010 20:57:27 -0400
X-MIMETrack: Serialize by Router on DOMMTL11/SRV/GVL(Release 7.0.2FP1|January 10, 2007) at 2010-10-20 20:57:31, Serialize complete at 2010-10-20 20:57:31
Content-Type: multipart/alternative; boundary="=_alternative 000543D7852577C3_="
Cc: Scott Beuker <Scott.Beuker@sjrb.ca>, IETF V6OPS WG <v6ops@ietf.org>, v6ops-bounces@ietf.org
Subject: Re: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 00:56:09 -0000

Message en plusieurs parties au format MIME
--=_alternative 000543D7852577C3_=
Content-Type: text/plain; charset="US-ASCII"

> I'm sure you can provide some better numbers, but am I correct in 
assuming that:
>  - you have an huge set of CPEs that are IPv4 only
>  - you have a small set of CPEs supporting 6to4
>  - you have a tiny set of those CPEs doing 6to4 by default
>  - you have a small set of CPEs supporting 6rd and native IPv6
>
> what I don't quite understand is why the focus on plan C for a 
presumably tiny 
> set of customers. when the big elephant in the room is the IPv4 only 
CPEs.

Ole, 

The larger elephant in the room might be the set of Windows 7 and 
Vista hosts connected to their provider directly behing a modem. Given 
a public IPv4 address and no v6, I understand these will do 6to4 by 
default 
(somebody correct me if this is no longer true). 

According to statistics heard at some point (can't find a reference now), 
directly connected users account for about 15 to 19% of users. Out of that 

percentage, roughly 30% are Win7 or Vista users 
(http://www.netmarketshare.com/os-market-share.aspx?qprid=11). 

Even if this is less than 5% of a provider's users, these hosts probably 
represent a much larger set than item 3 above. I know no sane ISP who 
would take the risk of having 5% of their clients call support because 
"Internet is slow" on the day google.com turns on AAAAs at large. This 
is why fixing 6to4 return path makes operational sense. 

<flame-suit-on>

JF

On a side note, I like your idea of redirecting HTTP 6to4 traffic to 
a page explaining how to disable it and to null-route the rest. 


--=_alternative 000543D7852577C3_=
Content-Type: text/html; charset="US-ASCII"


<br>
<br><tt><font size=2><br>
&gt; I'm sure you can provide some better numbers, but am I correct in
assuming that:<br>
&gt; &nbsp;- you have an huge set of CPEs that are IPv4 only<br>
&gt; &nbsp;- you have a small set of CPEs supporting 6to4<br>
&gt; &nbsp;- you have a tiny set of those CPEs doing 6to4 by default<br>
&gt; &nbsp;- you have a small set of CPEs supporting 6rd and native IPv6<br>
&gt;</font></tt>
<br><tt><font size=2>&gt; what I don't quite understand is why the focus
on plan C for a presumably tiny </font></tt>
<br><tt><font size=2>&gt; set of customers. when the big elephant in the
room is the IPv4 only CPEs.<br>
</font></tt>
<br><tt><font size=2>Ole, </font></tt>
<br><tt><font size=2><br>
The larger elephant in the room might be the set of Windows 7 and </font></tt>
<br><tt><font size=2>Vista hosts connected to their provider directly behing
a modem. Given </font></tt>
<br><tt><font size=2>a public IPv4 address and no v6, I understand these
will do 6to4 by default </font></tt>
<br><tt><font size=2>(somebody correct me if this is no longer true). </font></tt>
<br>
<br><tt><font size=2>According to statistics heard at some point (can't
find a reference now), </font></tt>
<br><tt><font size=2>directly connected users account for about 15 to 19%
of users. Out of that </font></tt>
<br><tt><font size=2>percentage, roughly 30% are Win7 or Vista users </font></tt>
<br><tt><font size=2>(http://www.netmarketshare.com/os-market-share.aspx?qprid=11).
</font></tt>
<br>
<br><tt><font size=2>Even if this is less than 5% of a provider's users,
these hosts probably </font></tt>
<br><tt><font size=2>represent a much larger set than item 3 above. I know
no sane ISP who </font></tt>
<br><tt><font size=2>would take the risk of having 5% of their clients
call support because </font></tt>
<br><tt><font size=2>&quot;Internet is slow&quot; on the day google.com
turns on AAAAs at large. This </font></tt>
<br><tt><font size=2>is why fixing 6to4 return path makes operational sense.
</font></tt>
<br>
<br><tt><font size=2>&lt;flame-suit-on&gt;</font></tt>
<br>
<br><tt><font size=2>JF</font></tt>
<br>
<br><tt><font size=2>On a side note, I like your idea of redirecting HTTP
6to4 traffic to </font></tt>
<br><tt><font size=2>a page explaining how to disable it and to null-route
the rest. </font></tt>
<br>
<br>
--=_alternative 000543D7852577C3_=--

From jasonlin.gz@gmail.com  Wed Oct 20 18:00:37 2010
Return-Path: <jasonlin.gz@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2DB603A6965 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 18:00:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.019
X-Spam-Level: 
X-Spam-Status: No, score=-2.019 tagged_above=-999 required=5 tests=[AWL=0.579,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CVQxZjs84lC9 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 18:00:36 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id E60963A695F for <v6ops@ietf.org>; Wed, 20 Oct 2010 18:00:35 -0700 (PDT)
Received: by gyc15 with SMTP id 15so2722649gyc.31 for <v6ops@ietf.org>; Wed, 20 Oct 2010 18:02:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=R3KSOcVsPLDiM8Q/Id1twGs7dw/v08aVHazCcG4UJw0=; b=M25QseJehrMoNKrTx1W6KScN+vCgEK1Z8WW+g0wXvfI+jActFlkpaXb8qzlMZ1+V5/ g4e4pTzzitDkh7RSNO745epmTsfkokEm7Zywo7mxdaPOVtM2n1pJEf/OzI1PE5XlIjr0 utfkFH1y4pH6fpF86Q0iUsguV74G58jouKW28=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=jpjOU14FmMtop/h+bTHpIxirzQNqTN85AhIcrngeI/7kph883kb/jRjhN0TD/FpJd9 lZaMju8RFOYzVAIx1m2DRsYGOHmvHglblODqvAXSEs08a3yE3rnCSA9z8mE34J7x2SWP aWTU50/hNSTO8C++aURd9MpzTDA3h0FsyWhoM=
MIME-Version: 1.0
Received: by 10.42.136.9 with SMTP id r9mr76334ict.107.1287622929708; Wed, 20 Oct 2010 18:02:09 -0700 (PDT)
Received: by 10.231.149.81 with HTTP; Wed, 20 Oct 2010 18:02:09 -0700 (PDT)
In-Reply-To: <AANLkTikqC4sKqDcDbcBCrRLXog=Y2gmMiwokKovHMjbx@mail.gmail.com>
References: <20101020025547.BE9C13A6984@core3.amsl.com> <AANLkTi=QbzoSrcYX7q4scn30gjU30UMmgpPnu84f7VLF@mail.gmail.com> <AANLkTikqC4sKqDcDbcBCrRLXog=Y2gmMiwokKovHMjbx@mail.gmail.com>
Date: Thu, 21 Oct 2010 09:02:09 +0800
Message-ID: <AANLkTiktS_M0BJKh=HViUuyzUGtHP=Czrckj+Jyp66bh@mail.gmail.com>
From: Jason Lin <jasonlin.gz@gmail.com>
To: v6ops@ietf.org
Content-Type: multipart/alternative; boundary=90e6ba6e8d5054783d0493161375
Subject: [v6ops] [v4v6tran] New Version Notification for draft-yang-v6ops-v4v6tran-bb-transition-guide-01
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 01:00:37 -0000

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

sorry guys, I've sent this notification to a wrong address, so I resent it.

---------- Forwarded message ----------
From: Jason Lin <jasonlin.gz@gmail.com>
Date: Wed, Oct 20, 2010 at 11:08 AM
Subject: [v6ops][v4v6tran] New Version Notification for
draft-yang-v6ops-v4v6tran-bb-transition-guide-01
To: v6ops@ops.ietf.org, v4tov6transition@ietf.org


Dear all,

Please kindly to check the new version draft.
Comments are warmly welcome!

Many thanks for the comments from Dave Thaler, Denis Alexeitsev, Jari Arkko=
,
Remi Despres, Tina
   TSOU, Tom Taylor and Tony Li. =EF=BC=88list in alphabetical order=EF=BC=
=89

Best Regards,

Jason Lin
China Telecom
109, Zhongshan Ave. West,
Guangzhou, Tianhe District  510630
P.R. China

---------- Forwarded message ----------
From: IETF I-D Submission Tool <idsubmission@ietf.org>
Date: Wed, Oct 20, 2010 at 10:55 AM
Subject: New Version Notification for
draft-yang-v6ops-v4v6tran-bb-transition-guide-01
To: jasonlin.gz@gmail.com
Cc: yanggl@gsta.com, hulm@gsta.com



A new version of I-D, draft-yang-v6ops-v4v6tran-bb-transition-guide-01.txt
has been successfully submitted by JinYan Lin and posted to the IETF
repository.

Filename:        draft-yang-v6ops-v4v6tran-bb-transition-guide
Revision:        01
Title:           IPv6 Transition Guide For A Large-scale Broadband Network
Creation_date:   2010-10-20
WG ID:           Independent Submission
Number_of_pages: 27

Abstract:
This document discusses about different IPv6 migrating solutions for
each part of the Large-scale broadband network with layer 2 access
infrastructure.  They are based on the requirements of providing
existing broadband services in v4v6-coexisting or IPv6-only
scenarios.  The document provides analysis of different solutions and
also describes the suitable scenarios that each solution may be
deployed in.



The IETF Secretariat.

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

<div class=3D"gmail_quote">sorry guys, I&#39;ve sent this notification to a=
 wrong address, so I resent it.</div><div class=3D"gmail_quote"><br></div><=
div class=3D"gmail_quote">---------- Forwarded message ----------<br>From: =
<b class=3D"gmail_sendername">Jason Lin</b> <span dir=3D"ltr">&lt;<a href=
=3D"mailto:jasonlin.gz@gmail.com">jasonlin.gz@gmail.com</a>&gt;</span><br>
Date: Wed, Oct 20, 2010 at 11:08 AM<br>Subject: [v6ops][v4v6tran] New Versi=
on Notification for draft-yang-v6ops-v4v6tran-bb-transition-guide-01<br>To:=
 <a href=3D"mailto:v6ops@ops.ietf.org">v6ops@ops.ietf.org</a>, <a href=3D"m=
ailto:v4tov6transition@ietf.org">v4tov6transition@ietf.org</a><br>
<br><br><div class=3D"im"><div class=3D"gmail_quote"><span style=3D"font-fa=
mily:arial, sans-serif;border-collapse:collapse"><font color=3D"#333333">De=
ar all,<br><br>Please kindly to check the new version draft.<br>Comments ar=
e warmly welcome!</font></span></div>

<div class=3D"gmail_quote">
<font face=3D"arial, sans-serif"><span style=3D"border-collapse:collapse"><=
font color=3D"#333333"><br></font></span></font></div></div><div class=3D"g=
mail_quote"><font face=3D"arial, sans-serif"><span style=3D"border-collapse=
:collapse"><font color=3D"#333333">Many thanks for the comments from Dave T=
haler, Denis Alexeitsev, Jari Arkko, Remi D</font><span><font color=3D"#333=
333">espres</font></span><font color=3D"#333333">, Tina</font></span></font=
></div>


<div class=3D"gmail_quote"><font face=3D"arial, sans-serif"><span style=3D"=
border-collapse:collapse"><font color=3D"#333333">=C2=A0=C2=A0 TSOU, Tom Ta=
ylor and Tony Li. =EF=BC=88</font></span></font><span style=3D"font-family:=
arial, sans-serif;line-height:18px"><font color=3D"#333333">list in alphabe=
tical order</font></span><span style=3D"font-family:arial, sans-serif;borde=
r-collapse:collapse"><font color=3D"#333333">=EF=BC=89</font></span></div>
<div><div></div><div class=3D"h5">
<div class=3D"gmail_quote">
<span style=3D"font-family:arial, sans-serif;border-collapse:collapse"><br>=
</span><div><span style=3D"font-family:arial, sans-serif;border-collapse:co=
llapse">Best Regards,<br>
</span><div><span style=3D"font-family:arial, sans-serif;font-size:12.5px;b=
order-collapse:collapse"><font size=3D"5"><span style=3D"font-size:18px"><f=
ont size=3D"4"><span style=3D"font-size:15px"><br>
</span></font></span></font></span><div><span style=3D"font-family:arial, s=
ans-serif;font-size:12.5px;border-collapse:collapse">Jason Lin</span><br><d=
iv>China Telecom</div><div>109, Zhongshan Ave. West,</div>
<div>Guangzhou, Tianhe District =C2=A0510630</div><div>P.R. China</div></di=
v><div><div></div><div><div><br></div><div><div class=3D"gmail_quote">-----=
----- Forwarded message ----------<br>From: <b class=3D"gmail_sendername">I=
ETF I-D Submission Tool</b> <span dir=3D"ltr">&lt;<a href=3D"mailto:idsubmi=
ssion@ietf.org" target=3D"_blank">idsubmission@ietf.org</a>&gt;</span><br>




Date: Wed, Oct 20, 2010 at 10:55 AM<br>Subject: New Version Notification fo=
r          draft-yang-v6ops-v4v6tran-bb-transition-guide-01<br>To: <a href=
=3D"mailto:jasonlin.gz@gmail.com" target=3D"_blank">jasonlin.gz@gmail.com</=
a><br>



Cc: <a href=3D"mailto:yanggl@gsta.com" target=3D"_blank">yanggl@gsta.com</a=
>, <a href=3D"mailto:hulm@gsta.com" target=3D"_blank">hulm@gsta.com</a><br>
<br><br><br>
A new version of I-D, draft-yang-v6ops-v4v6tran-bb-transition-guide-01.txt =
has been successfully submitted by JinYan Lin and posted to the IETF reposi=
tory.<br>
<br>
Filename: =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-yang-v6ops-v4v6tran-bb-transitio=
n-guide<br>
Revision: =C2=A0 =C2=A0 =C2=A0 =C2=A001<br>
Title: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 IPv6 Transition Guide For A Large=
-scale Broadband Network<br>
Creation_date: =C2=A0 2010-10-20<br>
WG ID: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Independent Submission<br>
Number_of_pages: 27<br>
<br>
Abstract:<br>
This document discusses about different IPv6 migrating solutions for<br>
each part of the Large-scale broadband network with layer 2 access<br>
infrastructure. =C2=A0They are based on the requirements of providing<br>
existing broadband services in v4v6-coexisting or IPv6-only<br>
scenarios. =C2=A0The document provides analysis of different solutions and<=
br>
also describes the suitable scenarios that each solution may be<br>
deployed in.<br>
<br>
<br>
<br>
The IETF Secretariat.<br>
<br>
<br>
</div><br>
</div></div></div></div></div>
</div><br>
</div></div></div><br>

--90e6ba6e8d5054783d0493161375--

From ek@google.com  Wed Oct 20 18:13:37 2010
Return-Path: <ek@google.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E08403A691B for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 18:13:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.377
X-Spam-Level: 
X-Spam-Status: No, score=-105.377 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yK7x3SKPKsMU for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 18:13:36 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 946D83A68AC for <v6ops@ietf.org>; Wed, 20 Oct 2010 18:13:36 -0700 (PDT)
Received: from hpaq1.eem.corp.google.com (hpaq1.eem.corp.google.com [172.25.149.1]) by smtp-out.google.com with ESMTP id o9L1FAFw005439 for <v6ops@ietf.org>; Wed, 20 Oct 2010 18:15:10 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1287623710; bh=mixi6NanLxPsZsrSCHrsgkbHgvM=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type:Content-Transfer-Encoding; b=PxITXhnRTROz6t8aepH7wXXLwbkpNK1hC8+mA3AIXKZjTGPcqHjdqIT/N2G+X6n5r 3FvbRz8ihgtSnQwSA1srw==
Received: from qyk38 (qyk38.prod.google.com [10.241.83.166]) by hpaq1.eem.corp.google.com with ESMTP id o9L1F2YA017564 for <v6ops@ietf.org>; Wed, 20 Oct 2010 18:15:03 -0700
Received: by qyk38 with SMTP id 38so1639989qyk.9 for <v6ops@ietf.org>; Wed, 20 Oct 2010 18:15:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=4FXPbg6fHRaLZuWtekaHE0r/vZORIGRTHnd7c6s2bNQ=; b=UnnID/tMUSB2vjACLq2iuMLtks2C6wn0YWc0yt0QqfaCuZH9fxgGR+JRo4hX2GDvaC /wuFLbr1mBcFqQn8caKg==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=aAkkVdH3aCgmiW9LHO+PLdvzPJpkeJLcrgO6ZOaFx4M30p4849WCIiSL3Ddk/cTuKD Wef5aJJiiz/lkXe2hkCw==
MIME-Version: 1.0
Received: by 10.229.219.74 with SMTP id ht10mr68638qcb.270.1287623702407; Wed, 20 Oct 2010 18:15:02 -0700 (PDT)
Received: by 10.229.78.228 with HTTP; Wed, 20 Oct 2010 18:15:02 -0700 (PDT)
In-Reply-To: <OF2AB7BBCF.1DF4A3EC-ON852577C3.0001FC71-852577C3.000543D9@videotron.com>
References: <D9571054-81AA-4439-A4AC-B9D9711BC673@employees.org> <OF2AB7BBCF.1DF4A3EC-ON852577C3.0001FC71-852577C3.000543D9@videotron.com>
Date: Wed, 20 Oct 2010 18:15:02 -0700
Message-ID: <AANLkTinJm-_r4cYncvZZa7fGHkVJgOuX9UgEa4tdx_AT@mail.gmail.com>
From: Erik Kline <ek@google.com>
To: Jean-Francois.TremblayING@videotron.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
Cc: Scott Beuker <Scott.Beuker@sjrb.ca>, IETF V6OPS WG <v6ops@ietf.org>, v6ops-bounces@ietf.org
Subject: Re: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 01:13:37 -0000

On 20 October 2010 17:57,  <Jean-Francois.TremblayING@videotron.com> wrote:
>
>
>
>> I'm sure you can provide some better numbers, but am I correct in assumi=
ng
>> that:
>> =C2=A0- you have an huge set of CPEs that are IPv4 only
>> =C2=A0- you have a small set of CPEs supporting 6to4
>> =C2=A0- you have a tiny set of those CPEs doing 6to4 by default
>> =C2=A0- you have a small set of CPEs supporting 6rd and native IPv6
>>
>> what I don't quite understand is why the focus on plan C for a presumabl=
y
>> tiny
>> set of customers. when the big elephant in the room is the IPv4 only CPE=
s.
>
> Ole,
>
> The larger elephant in the room might be the set of Windows 7 and
> Vista hosts connected to their provider directly behing a modem. Given
> a public IPv4 address and no v6, I understand these will do 6to4 by defau=
lt
> (somebody correct me if this is no longer true).
>
> According to statistics heard at some point (can't find a reference now),
> directly connected users account for about 15 to 19% of users. Out of tha=
t
> percentage, roughly 30% are Win7 or Vista users
> (http://www.netmarketshare.com/os-market-share.aspx?qprid=3D11).
>
> Even if this is less than 5% of a provider's users, these hosts probably
> represent a much larger set than item 3 above. I know no sane ISP who
> would take the risk of having 5% of their clients call support because
> "Internet is slow" on the day google.com turns on AAAAs at large. This
> is why fixing 6to4 return path makes operational sense.
>
> <flame-suit-on>
>
> JF
>
> On a side note, I like your idea of redirecting HTTP 6to4 traffic to
> a page explaining how to disable it and to null-route the rest.
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>
>

I don't know if these numbers are relevant to anybody but me, but
here's the latest:

    - of the clients in one of our experiments that connect to a
dualstack hostname, 0.2% (up from 0.04% 2 years ago!) connect with
native (or apparently native) IPv6, and an additional 0.1% connect
with 6to4.

Also, the extra contribution from 6to4 has been steadily dwindling:

    - 2 years ago 6to4 users were 3x as numerous as native.  Now
they're only half as numerous.

>From this I would conclude that 6to4 is steadily dwindling as a factor
(for dualstack HTTP destinations, etc etc, caveat caveat).  Of course,
someone else might drawn some other conclusion.

From jhw@apple.com  Wed Oct 20 20:15:35 2010
Return-Path: <jhw@apple.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 62E9A3A698D for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 20:15:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RoRi6Y-ybpAL for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 20:14:59 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id CEE033A69FA for <v6ops@ietf.org>; Wed, 20 Oct 2010 20:13:18 -0700 (PDT)
Received: from relay11.apple.com (relay11.apple.com [17.128.113.48]) by mail-out4.apple.com (Postfix) with ESMTP id 51317B718BC7 for <v6ops@ietf.org>; Wed, 20 Oct 2010 20:14:53 -0700 (PDT)
X-AuditID: 11807130-b7b53ae0000049b6-41-4cbfb02dfbf1
Received: from elliott.apple.com (elliott.apple.com [17.151.62.13]) by relay11.apple.com (Apple SCV relay) with SMTP id 2A.BE.18870.D20BFBC4; Wed, 20 Oct 2010 20:14:53 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from [172.16.1.250] (adit.conjury.org [75.101.54.88]) by elliott.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LAM001A3ECMUSA0@elliott.apple.com> for v6ops@ietf.org; Wed, 20 Oct 2010 20:14:53 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <C8E515F5.1D27%yiu_lee@cable.comcast.com>
Date: Wed, 20 Oct 2010 20:14:46 -0700
Message-id: <61A9CE89-B721-4E78-AAC5-9B3809FDC49F@apple.com>
References: <C8E515F5.1D27%yiu_lee@cable.comcast.com>
To: IPv6 Operations <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 03:15:36 -0000

On Oct 20, 2010, at 18:57 , Lee, Yiu wrote:
> 
> Thanks for the information. I also assume it will support IA_PD. If the
> AirPort and Time Capsule receive a PD shorter than /64, what is the
> behavior?

Again, assuming you are using AirPort Extreme or Time Capsule (not AirPort Express) made after about October 2009, then there is an "Advanced" mode available that supports DHCPv6 client, including with IA_PD in its "native router" configuration.

Its behavior is far from ideal, but better than nothing: the first prefix in the IA_PD option is zero-extended to produce a 64-bit network identifier.   That single /64 is advertised on the LAN bridge and the unit's integrated DNS server is advertised with RDNSS options and stateless DHCPv6.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



From joelja@bogus.com  Wed Oct 20 22:41:09 2010
Return-Path: <joelja@bogus.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A1E03A69F9 for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 22:41:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.082
X-Spam-Level: 
X-Spam-Status: No, score=-102.082 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NL+eG+76Vkgh for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 22:41:07 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [147.28.0.81]) by core3.amsl.com (Postfix) with ESMTP id 803AD3A69CF for <v6ops@ietf.org>; Wed, 20 Oct 2010 22:40:59 -0700 (PDT)
Received: from joelja-mac.lan (c-98-234-104-156.hsd1.ca.comcast.net [98.234.104.156]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id o9L5fGu4035465 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 21 Oct 2010 05:41:17 GMT (envelope-from joelja@bogus.com)
Message-ID: <4CBFD27C.5050105@bogus.com>
Date: Wed, 20 Oct 2010 22:41:16 -0700
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>
References: <C8E49512.102B8%victor.kuarsingh@gmail.com>
In-Reply-To: <C8E49512.102B8%victor.kuarsingh@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Thu, 21 Oct 2010 05:41:18 +0000 (UTC)
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 05:41:09 -0000

On 10/20/10 12:46 PM, Victor Kuarsingh wrote:
> Erik,
> 
> I do appreciate everyone's input on this, but I think I still have not been
> clear as to how we see this fit into the big picture.
> 
> PMT is not "the" option, it only addresses part of a bigger issue.  For the
> specific use case we are talking about, yes, we are concerning ourselves
> with IPv6 only if IPv4-only access with unmanaged CPEs are used.

ipv4 unmanaged cpe which support 6to4 which it should be noted is a more
limited set of the total devices.

> Here is example of what some ISPs may see.
> 
> 1. IPv6 Native (stuff we can get to native IPv6 based on available
> hardware/software in the access network and CPE supports IPv6)
> 2. IPv6 over Managed Tunneled/CPE.  (we can control the CPE and get it IPv6
> via technologies like 6RD).
> 3. (*KEY ISSUE FOR PMT*) IPv4 only access (i.e. DOCSIS 2.0 which cannot be
> upgraded to IPv6) with unmanaged CPEs.
> 
> It is the third use case we are concerned with if IPv6 only is out there
> (again, we are all guessing as to if this may happened in any specific
> timeframe).
> 
> I need to deal with all three situations.  I will need a mix of
> technologies, there is no one-size-fits-all for IPv6 transition (not matter
> how much I want it).
> 
> Again, vendors have been pumping our customer base with IPv4 only, non-IPv6
> CPEs for years and continue to do so. 

and they don't likely recently do 6to4 either.

> I am not buying them.. Customers are,
> who pay for the entire system which pays all of us (through various channels
> and business models)
> 
> Regards,
> 
> Victor
> 
> 
> 
> 
> On 20/10/10 12:22 PM, "Erik Kline" <ek@google.com> wrote:
> 
>> On 20 October 2010 12:10, Ole Troan <otroan@employees.org> wrote:
>>>> Perhaps the community would accept a "time limited" acceptance of longer
>>>> then 2002::/16 set of routes would work.
>>>>
>>>> We would need to get people to agree to not drop them.  And of course, how
>>>> would we deal with the "removal" process?  How would we twilight this? This
>>>> may be another challenging item which requires a bunch of providers agreeing
>>>> to something to do globally.
>>>>
>>>> I am not as concerned about longer then /16s as others.
>>>
>>> or would the community accept:
>>> ip route 192.88.99.1/32 Null0
>>>
>>> alternatively and slightly more friendly redirect http 6to4 traffic to a
>>> local web server giving instructions for how to disable 6to4 (and use the
>>> ISP's native IPv6 service.)
>>
>> Again, if the client elevates RFC1918 local addresses to global scope
>> for 3484 purposes, thereby de-prefing 6to4 when doing addr selection
>> for dualstack destinations, doesn't this whole thing just become
>> irrelevant as far as /transition/ is concerned?  You'd only be
>> concerning yourself with traffic to IPv6-only destinations.
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> 


From john_brzozowski@cable.comcast.com  Wed Oct 20 23:36:27 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 755193A69AB for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 23:36:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.348
X-Spam-Level: 
X-Spam-Status: No, score=-107.348 tagged_above=-999 required=5 tests=[AWL=0.515, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ICH02rTxE17h for <v6ops@core3.amsl.com>; Wed, 20 Oct 2010 23:36:26 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 2823F3A69A9 for <v6ops@ietf.org>; Wed, 20 Oct 2010 23:36:26 -0700 (PDT)
Received: from ([24.40.55.42]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.100693237; Thu, 21 Oct 2010 02:37:57 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by PACDCEXHUB01.cable.comcast.com ([fe80::d1e7:20b5:9b63:21a6%12]) with mapi id 14.01.0255.000; Thu, 21 Oct 2010 02:37:57 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: IPv6 Operations <v6ops@ietf.org>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
Thread-Index: AQHLb7qA2T6t3TrIl0mUPJfZCE79dZNKB0SAgAA+QwCAAKTAgIAAFYsA///1tYA=
Date: Thu, 21 Oct 2010 06:37:55 +0000
Message-ID: <C8E55803.2A7F5%john_brzozowski@cable.comcast.com>
In-Reply-To: <61A9CE89-B721-4E78-AAC5-9B3809FDC49F@apple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <ABDFCD1389A9B14BB7296C57EC33D2B5@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 06:36:27 -0000

James,

What you describe seems reasonable and functional.  The simple fact that a
functional implementation exists is very positive.

The only other comment I would offer is why would a shorter prefix be
offered to an IGD if the device cannot support it?  This leads to a point
that I think is worth noting related to RFC3633.  It is important that IGD
hint to the size of IPv6 prefix desired/supported in its DHCPv6 SOLICIT.
>From what I have seen very few, if any, IGDs provide a hint in the IA_PD.

Providing the hint does not guarantee that the operator will always honor
the hint.  This, however, is a step in the right direction to ensure the IG=
D
is offered an appropriately sized IPv6 prefix.

John

On 10/20/10 11:14 PM, "james woodyatt" <jhw@apple.com> wrote:

> On Oct 20, 2010, at 18:57 , Lee, Yiu wrote:
>>=20
>> Thanks for the information. I also assume it will support IA_PD. If the
>> AirPort and Time Capsule receive a PD shorter than /64, what is the
>> behavior?
>=20
> Again, assuming you are using AirPort Extreme or Time Capsule (not AirPor=
t
> Express) made after about October 2009, then there is an "Advanced" mode
> available that supports DHCPv6 client, including with IA_PD in its "nativ=
e
> router" configuration.
>=20
> Its behavior is far from ideal, but better than nothing: the first prefix=
 in
> the IA_PD option is zero-extended to produce a 64-bit network identifier.
> That single /64 is advertised on the LAN bridge and the unit's integrated=
 DNS
> server is advertised with RDNSS options and stateless DHCPv6.
>=20
>=20
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, communications engineering
>=20
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

=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
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From ichiroumakino@gmail.com  Thu Oct 21 00:07:31 2010
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 296853A69BD for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 00:07:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.573
X-Spam-Level: 
X-Spam-Status: No, score=-2.573 tagged_above=-999 required=5 tests=[AWL=0.026,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fiX3mG9qChke for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 00:07:26 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 6A9F03A6959 for <v6ops@ietf.org>; Thu, 21 Oct 2010 00:07:26 -0700 (PDT)
Received: by ewy6 with SMTP id 6so2974945ewy.31 for <v6ops@ietf.org>; Thu, 21 Oct 2010 00:09:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=SI7JLfCdXHYEoOT0FhyteV0jzTuHAEpMOXKlGjghsBg=; b=qjEL5jjxBFzncl3aYz4LXbdEaJ0yw/dKfviWbLFVeRGaj5vNCO1SR/N6NpPE3B+Phh LCC6HrznJnbJi+MoTXvX2I5SrYB0ZNq61Rd1hvG0z4YHGyO4xMkEXz3EgCoMrSxMqYcE cFs5VEimQxHV/P76L3MEthegTxo3LW+Xs73/Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=L6QtgpxlifBXVzbldSWGjIeMJKV1PLcp3jSO3jR3ftIjqNwnW806i7e894JYYgktqA stLkNOMbNbfhSlLrqJEoOZFPDsmfUVASEl0wQaEgW55sdTPc47elKkWwCTSGWjIjnP6U rKqQuAPn1RhYcTDNKLp8DqtLAUI5IZeHmepHA=
Received: by 10.213.11.16 with SMTP id r16mr3917847ebr.56.1287644940393; Thu, 21 Oct 2010 00:09:00 -0700 (PDT)
Received: from ams3-vpn-dhcp6363.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) by mx.google.com with ESMTPS id v56sm1368915eeh.20.2010.10.21.00.08.57 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 21 Oct 2010 00:08:59 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <C8E55803.2A7F5%john_brzozowski@cable.comcast.com>
Date: Thu, 21 Oct 2010 09:08:52 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <49C6C36B-E028-40F3-B2FF-ECCF5E452AB9@employees.org>
References: <C8E55803.2A7F5%john_brzozowski@cable.comcast.com>
To: "Brzozowski, John" <John_Brzozowski@cable.comcast.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 07:07:31 -0000

John,

> What you describe seems reasonable and functional.  The simple fact =
that a
> functional implementation exists is very positive.
>=20
> The only other comment I would offer is why would a shorter prefix be
> offered to an IGD if the device cannot support it?  This leads to a =
point
> that I think is worth noting related to RFC3633.  It is important that =
IGD
> hint to the size of IPv6 prefix desired/supported in its DHCPv6 =
SOLICIT.
> =46rom what I have seen very few, if any, IGDs provide a hint in the =
IA_PD.
>=20
> Providing the hint does not guarantee that the operator will always =
honor
> the hint.  This, however, is a step in the right direction to ensure =
the IGD
> is offered an appropriately sized IPv6 prefix.

my assumption is that residential customers get the same address block =
size independent of what their actual need is.

if you give every customer a /56, isn't that a simple deployment model, =
where you can do simple aggregation and you don't have to "negotiate" =
with each customer for their most suitable address block size, which =
might even change over time...?

as more advanced home networks evolve, it is going to be difficult for =
the border router to know the number of links that exists or may appear =
in the future. the intention with PD was always that the prefix size was =
a contractual matter, not one which is negotiated 'real time'.

mind you, I'm not an operator and I would surely like to understand the =
reasons why doing more negotiation would be useful? of course, one has =
to expect that every CPE supports a delegation of <=3D/64. are there =
really implementations which only supports a single /64? if so, I'd =
claim that's a bug and not in line with 3633 nor the basic ipv6 ce =
router requirements specification.

cheers,
Ole=

From gert@space.net  Thu Oct 21 00:32:06 2010
Return-Path: <gert@space.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9F96B3A69F4 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 00:32:06 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lci3+KpTAGPk for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 00:32:05 -0700 (PDT)
Received: from mobil.space.net (mobil.Space.Net [IPv6:2001:608:2:81::2]) by core3.amsl.com (Postfix) with ESMTP id 48D193A6944 for <v6ops@ietf.org>; Thu, 21 Oct 2010 00:32:04 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id 8AD44F81AE for <v6ops@ietf.org>; Thu, 21 Oct 2010 09:33:38 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 67DAAF81B3 for <v6ops@ietf.org>; Thu, 21 Oct 2010 09:33:38 +0200 (CEST)
Received: (qmail 97005 invoked by uid 1007); 21 Oct 2010 09:33:38 +0200
Date: Thu, 21 Oct 2010 09:33:38 +0200
From: Gert Doering <gert@space.net>
To: Jean-Francois.TremblayING@videotron.com
Message-ID: <20101021073338.GV32268@Space.Net>
References: <D9571054-81AA-4439-A4AC-B9D9711BC673@employees.org> <OF2AB7BBCF.1DF4A3EC-ON852577C3.0001FC71-852577C3.000543D9@videotron.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <OF2AB7BBCF.1DF4A3EC-ON852577C3.0001FC71-852577C3.000543D9@videotron.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: Scott Beuker <Scott.Beuker@sjrb.ca>, IETF V6OPS WG <v6ops@ietf.org>, v6ops-bounces@ietf.org
Subject: Re: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 07:32:06 -0000

Hi,

On Wed, Oct 20, 2010 at 08:57:27PM -0400, Jean-Francois.TremblayING@videotron.com wrote:
> The larger elephant in the room might be the set of Windows 7 and 
> Vista hosts connected to their provider directly behing a modem. Given 
> a public IPv4 address and no v6, I understand these will do 6to4 by 
> default (somebody correct me if this is no longer true). 

True, but...

> Even if this is less than 5% of a provider's users, these hosts probably 
> represent a much larger set than item 3 above. I know no sane ISP who 
> would take the risk of having 5% of their clients call support because 
> "Internet is slow" on the day google.com turns on AAAAs at large. This 
> is why fixing 6to4 return path makes operational sense. 

... Vista and Win7 will prefer IPv4 to 6to4.  So when connecting to 
dual-stacked hosts, they will not use IPv6.  No problem here.

6to4 will only be used connecting to IPv6-only hosts.

Gert Doering
        -- NetMaster
-- 
did you enable IPv6 on something today...?

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

From john_brzozowski@cable.comcast.com  Thu Oct 21 00:41:52 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9B8D33A6985 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 00:41:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.562
X-Spam-Level: 
X-Spam-Status: No, score=-107.562 tagged_above=-999 required=5 tests=[AWL=0.601, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DPl6mJBU2+C0 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 00:41:51 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id D96543A63CA for <v6ops@ietf.org>; Thu, 21 Oct 2010 00:41:50 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.100698189; Thu, 21 Oct 2010 03:43:21 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by PACDCEXHUB02.cable.comcast.com ([fe80::11d4:f530:37a0:9f4e%12]) with mapi id 14.01.0255.000; Thu, 21 Oct 2010 03:43:21 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: =?iso-8859-1?Q?Ole_Tr=F8an?= <otroan@employees.org>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
Thread-Index: Actw86D12T6t3TrIl0mUPJfZCE79dQ==
Date: Thu, 21 Oct 2010 07:43:20 +0000
Message-ID: <C8E56757.2A817%john_brzozowski@cable.comcast.com>
In-Reply-To: <49C6C36B-E028-40F3-B2FF-ECCF5E452AB9@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <645155C79017A944AB3986DC0F5B88F6@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 07:41:52 -0000

On 10/21/10 3:08 AM, "Ole Tr=F8an" <otroan@employees.org> wrote:

> John,
>=20
>> What you describe seems reasonable and functional.  The simple fact that=
 a
>> functional implementation exists is very positive.
>>=20
>> The only other comment I would offer is why would a shorter prefix be
>> offered to an IGD if the device cannot support it?  This leads to a poin=
t
>> that I think is worth noting related to RFC3633.  It is important that I=
GD
>> hint to the size of IPv6 prefix desired/supported in its DHCPv6 SOLICIT.
>> From what I have seen very few, if any, IGDs provide a hint in the IA_PD=
.
>>=20
>> Providing the hint does not guarantee that the operator will always hono=
r
>> the hint.  This, however, is a step in the right direction to ensure the=
 IGD
>> is offered an appropriately sized IPv6 prefix.
>=20
> my assumption is that residential customers get the same address block si=
ze
> independent of what their actual need is.
[jjmb] at this time I do not share this assumption, I may over time.  I als=
o
not sure if this a universally accepted assumption.
>=20
> if you give every customer a /56, isn't that a simple deployment model, w=
here
> you can do simple aggregation and you don't have to "negotiate" with each
> customer for their most suitable address block size, which might even cha=
nge
> over time...?
[jjmb] a fixed prefix does not necessarily make for a simpler deployment
model.  For a given prefix length range the simplicity or complexity of
aggregation will not necessarily change.  In a cable environment, for
example, the aggregation could occur at the CMTS regardless of prefix
length.  Fortunately DHCPv6 facilitates negotiation even if needs change
over time.  If additional space is needed over time IGDs can request a
shorter prefix.
>=20
> as more advanced home networks evolve, it is going to be difficult for th=
e
> border router to know the number of links that exists or may appear in th=
e
> future. the intention with PD was always that the prefix size was a
> contractual matter, not one which is negotiated 'real time'.
[jjmb] Hmmm...RFC3633 is a contract?
>=20
> mind you, I'm not an operator and I would surely like to understand the
> reasons why doing more negotiation would be useful? of course, one has to
> expect that every CPE supports a delegation of <=3D/64. are there really
> implementations which only supports a single /64? if so, I'd claim that's=
 a
> bug and not in line with 3633 nor the basic ipv6 ce router requirements
> specification.
[jjmb] having flexibility is a must, making substantial fixed decisions thi=
s
early can result in complications or even limitations.  I absolutely agree
with one of your comments above, home networks will evolve.  As such we nee=
d
to ensure we have the ability to accommodate the same over time.  An
incremental approach supports this goal.  Yes there are implementations tha=
t
only support a /64, nothing shorter largely because they physically do not
have the need and/or ability to support anything else.  If a device has onl=
y
one IPv4 LAN and cannot be upgraded to support more (including hierarchical
PD) why would this be a bug?  I think we will have to agree to disagree, I
do not view this as a bug.  I do think this is inline with RFC3633 and the
IPv6 CPE router requirements.  A lot of work has been done over the past
couple of years to get some existing routers to be software upgradable to
support native IPv6 as such there may be some devices with lesser
capabilities.  Having a minimal level of support for IPv6 is better than
none, right?  Finally, there may be a wide range of routers built over time
that range in caliber and features.
>=20
> cheers,
> Ole

=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
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From gert@space.net  Thu Oct 21 01:43:22 2010
Return-Path: <gert@space.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 454173A69F1 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 01:43:22 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xZc2eIn7-eBy for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 01:43:21 -0700 (PDT)
Received: from mobil.space.net (mobil.Space.Net [IPv6:2001:608:2:81::2]) by core3.amsl.com (Postfix) with ESMTP id 001713A69DD for <v6ops@ietf.org>; Thu, 21 Oct 2010 01:43:19 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id 07733F81DE for <v6ops@ietf.org>; Thu, 21 Oct 2010 10:44:54 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id DB02FF81AE for <v6ops@ietf.org>; Thu, 21 Oct 2010 10:44:53 +0200 (CEST)
Received: (qmail 64470 invoked by uid 1007); 21 Oct 2010 10:44:53 +0200
Date: Thu, 21 Oct 2010 10:44:53 +0200
From: Gert Doering <gert@space.net>
To: Jean-Francois.TremblayING@videotron.com
Message-ID: <20101021084453.GX32268@Space.Net>
References: <4CBF7326.5080607@gmail.com> <OF41D1A9C1.6ED93732-ON852577C2.00837F4F-852577C3.0000E8F9@videotron.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <OF41D1A9C1.6ED93732-ON852577C2.00837F4F-852577C3.0000E8F9@videotron.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: IETF V6OPS WG <v6ops@ietf.org>, v6ops-bounces@ietf.org
Subject: Re: [v6ops] RE  Economic incentive for 2002::/16
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 08:43:22 -0000

Hi,

On Wed, Oct 20, 2010 at 08:09:53PM -0400, Jean-Francois.TremblayING@videotron.com wrote:
> > No. An ISP operating a 6to4 relay and advertising a 2002::/16 route to 
> it
> > is acting entirely in the interests of that ISP's native IPv6 customers,
> > especially if they are content providers. The economic incentive in this
> > case is not misplaced.
> 
> Brian, I am not sure I fully agree with you here. It might be true if 
> 2002::/16 is densely advertised, but if it is sparsely like it is now, 
> announcing 2002::/16 will attrack return traffic from neighboring ASes. 

So don't announce it to anyone but your paying customers.  Good return
connectivity for your native IPv6 servers --> 6to4 clients, no extra
cost.

Gert Doering
        -- NetMaster
-- 
did you enable IPv6 on something today...?

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

From tore.anderson@redpill-linpro.com  Thu Oct 21 01:49:55 2010
Return-Path: <tore.anderson@redpill-linpro.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A9EB3A69F2 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 01:49:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UfK3eRpVpwGW for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 01:49:53 -0700 (PDT)
Received: from mailhub.linpro.no (mailhub.linpro.no [87.238.49.141]) by core3.amsl.com (Postfix) with ESMTP id 734003A690E for <v6ops@ietf.org>; Thu, 21 Oct 2010 01:49:53 -0700 (PDT)
Received: from localhost (mailhub.linpro.no [87.238.49.141]) by mailhub.linpro.no (Postfix) with ESMTP id BEF9E1DD1BC; Thu, 21 Oct 2010 10:51:27 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mailhub.linpro.no
Received: from mailhub.linpro.no ([87.238.49.141]) by localhost (mailhub.linpro.no [87.238.49.141]) (amavisd-new, port 10024) with ESMTP id pgav-H4MV4bl; Thu, 21 Oct 2010 10:51:20 +0200 (CEST)
Received: from zimbra.redpill-linpro.com (claudius.linpro.no [87.238.49.234]) by mailhub.linpro.no (Postfix) with ESMTP; Thu, 21 Oct 2010 10:51:19 +0200 (CEST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.redpill-linpro.com (Postfix) with ESMTP id C209F170C002; Thu, 21 Oct 2010 10:51:19 +0200 (CEST)
X-Virus-Scanned: amavisd-new at claudius.linpro.no
Received: from zimbra.redpill-linpro.com ([127.0.0.1]) by localhost (zimbra.redpill-linpro.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AbQol3YHryP4; Thu, 21 Oct 2010 10:51:19 +0200 (CEST)
Received: from echo.linpro.no (echo.linpro.no [87.238.42.42]) by zimbra.redpill-linpro.com (Postfix) with ESMTPSA id 57A20170C001; Thu, 21 Oct 2010 10:51:19 +0200 (CEST)
Message-ID: <4CBFFF07.1070302@redpill-linpro.com>
Date: Thu, 21 Oct 2010 10:51:19 +0200
From: Tore Anderson <tore.anderson@redpill-linpro.com>
Organization: Redpill Linpro AS
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100921 Fedora/3.1.4-1.fc13 Thunderbird/3.1.4
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <C8E4ECF9.2A6CE%john_brzozowski@cable.comcast.com> <4CBF89DA.2070007@gmail.com>
In-Reply-To: <4CBF89DA.2070007@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: IETF V6OPS WG <v6ops@ietf.org>, "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
Subject: Re: [v6ops] Economic incentive for 2002::/16 [was	draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt]
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 08:49:55 -0000

Brian, John,

* Brian E Carpenter

> The 6to4 client will try to find a benevolent relay as close as 
> possible; if they fail to find one, they will never show up as 6to4 
> users anyway. "Destination unreachable" for 192.88.99.1 would kill 
> the problem at source.

Null-routing the anycast address is counter-productive as it will not
prevent 6to4 implementations from setting up the tunnel interface, even
if the null-route produces ICMPv4 unreachables.  So you end up ensuring
that any application that attempts to use the 6to4 tunnel for
connectivity is blackholed.

This is true for Windows 7's default-on 6to4 adapter, at least.  Couple
this with software that prefers 6to4 to IPv4, such as Opera <10.50 or
Mac OS X (if Windows Internet Connection Sharing is active), and you've
just created another «broken user» and made it even more difficult than
it already is for content providers out there to get approval for
publishing quad As.  We _really_ don't need that...

It's much better, then, to let the user have a decent shot at using 6to4
successfully, even if that means the outbound traffic has to trampoline
off a third party relay somewhere.  The best would be if the SP has
relays on-net (like Comcast has), but if they don't it's actually much
better for the end users if there's as many open relays as possible
available.  That would improve the chances that the closest relay is
actually fairly close and won't cause the latencies to suffer too badly.

* John Brzozowksi

> From what we are seeing, operators should not announce their relays 
> publicly over IPv4.  Open 6to4 relays seem to yield undesirable 
> behavior.

The undesirable behaviour is really that 6to4 is being used as much as
it is and in preference to IPv4.  Unfortunately, that cat is out of the
bag.  Shutting down the open relays won't help, it will just worsen the
whole ordeal.

Best regards,
-- 
Tore Anderson
Redpill Linpro AS - http://www.redpill-linpro.com/
Tel: +47 21 54 41 27

From ichiroumakino@gmail.com  Thu Oct 21 02:02:09 2010
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C35B3A6A0F for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 02:02:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.573
X-Spam-Level: 
X-Spam-Status: No, score=-2.573 tagged_above=-999 required=5 tests=[AWL=0.026,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4SERniBBUyTd for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 02:02:07 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 0F9123A681A for <v6ops@ietf.org>; Thu, 21 Oct 2010 02:02:05 -0700 (PDT)
Received: by ewy6 with SMTP id 6so3003314ewy.31 for <v6ops@ietf.org>; Thu, 21 Oct 2010 02:03:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=H/iAaFIiYOZrl2AzXKaEyMNVqb0WTGayNZF9Nw4Pm34=; b=e/iHOzmGet9/Ob07roiAnNJBYIaBsogcwOr3VucWvTCM4Y99RnlwjcqzKAMtNpJYXV wwmmV6Cx7FHkT7EHHJSUtTy79P0Hl3gMto7hN6kUR03vFaHK+1iPODl/oD7NAtzsYpom JVHDqHkNAoPGvI2UoSqI5XohLsofYbpIm0ux0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=v5wy3ZKNz/ACTu9rB5mcj286rVxH8Bf/HqFzE8/mqSKsqrTt0sGW9rLEPQO+uzLS7d tIt8Ehz/3RqxX+rSA1uoeyiuGt2V8fnxCSiFNPasPwbqAtnRDu65YuJUxTSZvriOvw19 Uv0HehbsZiXRnjFqoBu05w0LuvHAv9lEt/Duw=
Received: by 10.14.47.78 with SMTP id s54mr376236eeb.2.1287651820531; Thu, 21 Oct 2010 02:03:40 -0700 (PDT)
Received: from dhcp-osl-vl300-64-103-53-105.cisco.com (dhcp-osl-vl300-64-103-53-105.cisco.com [64.103.53.105]) by mx.google.com with ESMTPS id w20sm1505028eeh.0.2010.10.21.02.03.38 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 21 Oct 2010 02:03:39 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <C8E56757.2A817%john_brzozowski@cable.comcast.com>
Date: Thu, 21 Oct 2010 11:03:36 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D926804D-A16F-40FC-AFF1-C15469D8B319@employees.org>
References: <C8E56757.2A817%john_brzozowski@cable.comcast.com>
To: "Brzozowski, John" <John_Brzozowski@cable.comcast.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 09:02:09 -0000

John,

[...]

>> as more advanced home networks evolve, it is going to be difficult =
for the
>> border router to know the number of links that exists or may appear =
in the
>> future. the intention with PD was always that the prefix size was a
>> contractual matter, not one which is negotiated 'real time'.
> [jjmb] Hmmm...RFC3633 is a contract?

a fax replacement. I'd expect when I buy service from an ISP the =
contract between me and the ISP also includes the size of the prefix I =
will be assigned as well as guarantees about its lifetime.

currently the hint in 3633 is just a MAY and even then there is only =
text suggesting that the requesting router should include a prefix, to =
hint to the server that it would like to receive the same prefix that =
was presumably previously delegated. WPD-2 in =
draft-ietf-v6ops-ipv6-cpe-router-07 includes a MAY hint to the =
delegating router about the size it would require and WPD-3 states it =
MUST accept a different prefix size.

DHCPv6 PD is a mechanism where the control and policy is at the DHCPv6 =
PD server.

you could write a proposal to strengthen this language, but I would =
posit that the IPv6 CE is in no position to know a priori what size to =
ask for.

>> mind you, I'm not an operator and I would surely like to understand =
the
>> reasons why doing more negotiation would be useful? of course, one =
has to
>> expect that every CPE supports a delegation of <=3D/64. are there =
really
>> implementations which only supports a single /64? if so, I'd claim =
that's a
>> bug and not in line with 3633 nor the basic ipv6 ce router =
requirements
>> specification.
> [jjmb] having flexibility is a must, making substantial fixed =
decisions this
> early can result in complications or even limitations.  I absolutely =
agree
> with one of your comments above, home networks will evolve.  As such =
we need
> to ensure we have the ability to accommodate the same over time.  An
> incremental approach supports this goal.  Yes there are =
implementations that
> only support a /64, nothing shorter largely because they physically do =
not
> have the need and/or ability to support anything else.  If a device =
has only
> one IPv4 LAN and cannot be upgraded to support more (including =
hierarchical
> PD) why would this be a bug?  I think we will have to agree to =
disagree, I
> do not view this as a bug.  I do think this is inline with RFC3633 and =
the
> IPv6 CPE router requirements.  A lot of work has been done over the =
past
> couple of years to get some existing routers to be software upgradable =
to
> support native IPv6 as such there may be some devices with lesser
> capabilities.  Having a minimal level of support for IPv6 is better =
than
> none, right?  Finally, there may be a wide range of routers built over =
time
> that range in caliber and features.

I think we are in agreement. I'm certainly not suggesting that e.g. a =
/56 is the only way it can be done. nor that delegations have to be =
rigid. every implementation must support any prefix length thrown at it, =
with the exception of getting a so small address block that it doesn't =
get a single /64 per link.

I'm just saying that the rfc3633 "hint" may not be very useful; and that =
delegating the absolute minimum address block required may be =
problematic. for example if the CE after a delegation is done determines =
that it needs a larger block, the home network may have to be =
renumbered.

thinking of DHCP PD as a fax replacement, lets you not have to think =
about all the hard corner cases. ;-)

cheers,
Ole=

From remi.despres@free.fr  Thu Oct 21 03:16:26 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 10A7B3A6947 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 03:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.446
X-Spam-Level: 
X-Spam-Status: No, score=-1.446 tagged_above=-999 required=5 tests=[AWL=0.503,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TwXpn-mtQMRa for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 03:16:24 -0700 (PDT)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.81]) by core3.amsl.com (Postfix) with ESMTP id DE5C13A6934 for <v6ops@ietf.org>; Thu, 21 Oct 2010 03:16:23 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2404.sfr.fr (SMTP Server) with ESMTP id EA31B7000090 for <v6ops@ietf.org>; Thu, 21 Oct 2010 12:17:57 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2404.sfr.fr (SMTP Server) with ESMTP id B698B7000088 for <v6ops@ietf.org>; Thu, 21 Oct 2010 12:17:57 +0200 (CEST)
X-SFR-UUID: 20101021101757748.B698B7000088@msfrf2404.sfr.fr
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Date: Thu, 21 Oct 2010 12:17:57 +0200
Message-Id: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr>
To: v6ops <v6ops@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Subject: [v6ops] Reasons not to endorse NAT66/6to4 (ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 10:16:26 -0000

Le 20 oct. 2010 =E0 22:15, Victor Kuarsingh a =E9crit :

> The suggestion [to adopt PMT, i.e. an combination of NAT66 with 6to4 =
relays] was based on the fact that [6to4 is] out there.  We take what we =
have and try and use it for good.

There is in my understanding a far better approach:
"Rather than spending energy to partially fix some 6to4 problems, while =
creating new ones, deploy the "real IPv6 service" asap, and suggest to =
turn 6to4 off while it's not too difficult.

The "Real IPv6 service" is as follows:
- It offers reliable connectivity to all native IPv6 addresses (unlike =
6to4).
- It gives ISPs control of the QoS they offer to their customers (unlike =
6to4).
- It guarantees e2e network transparency between any pair of native IPv6 =
addresses (unlike NAT66).
- This being achieved, one doesn't care whether e2e paths are totally =
dual-stack, partially 6rd, partially 6a44, or whatever, provided the =
service is available.

A serious concern with 6to4 is that, without strict precautions that =
aren't taken today, it becomes an evil: it tends to disgust users from =
IPv6 in general (it has connectivity and QoS problems that are far =
beyond Grandma's understanding capability). On the other hand, the real =
IPv6 service keeps people satisfied.

Please, don't get me wrong:
- 6to4 has been great for early IPv6 between IPv4 clouds, and can still =
work perfectly between two 6to4 IPv6 addresses.
- The idea of combining 6to4 relays with NAT66's (be they stateless or =
stateful), is worth discussing it, and thanks for clearly raising the =
issue.

But the point is that, to facilitate real IPv6 deployment and willful =
user acceptance, NAT66/6to4 would be counterproductive.


Regards,
RD=


From nick@inex.ie  Thu Oct 21 03:49:26 2010
Return-Path: <nick@inex.ie>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 469163A694F for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 03:49:26 -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.100, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p18Idm3O4qN5 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 03:49:25 -0700 (PDT)
Received: from mail.acquirer.com (unknown [IPv6:2001:1bb8:2004:150::2]) by core3.amsl.com (Postfix) with ESMTP id 1C4C13A694A for <v6ops@ietf.org>; Thu, 21 Oct 2010 03:49:24 -0700 (PDT)
X-Envelope-To: v6ops@ietf.org
Received: from cupcake.local ([10.228.100.105]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.3) with ESMTP id o9LAoq7i063739 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 21 Oct 2010 11:50:52 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <4CC01B0C.5020406@inex.ie>
Date: Thu, 21 Oct 2010 11:50:52 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b8pre) Gecko/20101013 Thunderbird/3.3a1pre
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr>
In-Reply-To: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr>
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 10:49:26 -0000

On 21/10/2010 11:17, Rémi Després wrote:
> But the point is that, to facilitate real IPv6 deployment and willful
> user acceptance, NAT66/6to4 would be counterproductive.

I agree with all of these points.  They're all good and valid.

However, the reality is that the CPE market is shockingly badly equipped as 
regards ipv6 support, and in many situations the provider side edge 
equipment isn't much better.  Remember, much of this equipment operates on 
a 5y lifetime basis, and even today, lots of vendors are telling people 
that their ipv6 deployment plans are only really beginning (both for CPE 
and provider edge kit).  For this reason, lack of functional ipv6 support 
on the last-mile will continue to be a problem for many years to come.

It kills me to say it - it really, really does - but in this instance, the 
overwhelming cretinousness introduced by 
draft-kuarsingh-v6ops-provider-managed-tunnel is very slightly surpassed by 
the even more overwhelmingly cretinous attitude of the cheap-as-chips 
vendors which are _still_ today designing kit which will never be ipv6 capable.

So, despite loathing this draft and every crap engineering principal it 
stands for, I am forced to admit that at this stage, we need it.

In case there's any doubt, I feel dirty to have to say this.

Nick

From nick@inex.ie  Thu Oct 21 04:05:52 2010
Return-Path: <nick@inex.ie>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF87A3A69E8 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 04:05:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.385
X-Spam-Level: 
X-Spam-Status: No, score=-2.385 tagged_above=-999 required=5 tests=[AWL=-0.086, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rFmzdIngYv3z for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 04:05:50 -0700 (PDT)
Received: from mail.acquirer.com (unknown [IPv6:2001:1bb8:2004:150::2]) by core3.amsl.com (Postfix) with ESMTP id 24ABA3A69FB for <v6ops@ietf.org>; Thu, 21 Oct 2010 04:05:23 -0700 (PDT)
X-Envelope-To: v6ops@ietf.org
Received: from cupcake.local ([10.228.100.105]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.3) with ESMTP id o9LB6r9w077163 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 21 Oct 2010 12:06:53 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <4CC01ECD.9040102@inex.ie>
Date: Thu, 21 Oct 2010 12:06:53 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b8pre) Gecko/20101013 Thunderbird/3.3a1pre
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr> <4CC01B0C.5020406@inex.ie>
In-Reply-To: <4CC01B0C.5020406@inex.ie>
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 11:05:52 -0000

On 21/10/2010 11:50, Nick Hilliard wrote:
> So, despite loathing this draft and every crap engineering principal it
> stands for, I am forced to admit that at this stage, we need it.

I should add that the proposal's only mitigating virtue is that it's 
relatively easy to undo.

Nick

From teemu.savolainen@nokia.com  Thu Oct 21 05:00:17 2010
Return-Path: <teemu.savolainen@nokia.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BD1673A6767 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 05:00:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.587
X-Spam-Level: 
X-Spam-Status: No, score=-6.587 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V-xuQMJ6ZjBm for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 05:00:12 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id 2FB1E3A68F5 for <v6ops@ietf.org>; Thu, 21 Oct 2010 05:00:12 -0700 (PDT)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-mx09.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o9LC1OZd029280; Thu, 21 Oct 2010 07:01:36 -0500
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by vaebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 21 Oct 2010 15:01:27 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.5]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 21 Oct 2010 15:01:27 +0300
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-01.mgdnok.nokia.com ([65.54.30.5]) with mapi; Thu, 21 Oct 2010 14:01:26 +0200
From: <teemu.savolainen@nokia.com>
To: <fred@cisco.com>, <v6ops@ietf.org>
Date: Thu, 21 Oct 2010 14:01:23 +0200
Thread-Topic: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
Thread-Index: ActopRH/JoCme+MzQXiyJfFN4kSgHQIcAP9g
Message-ID: <18034D4D7FE9AE48BF19AB1B0EF2729F5F0418A89E@NOK-EUMSG-01.mgdnok.nokia.com>
References: <C05BE420-A613-4AD4-8A94-73645C4947CB@cisco.com>
In-Reply-To: <C05BE420-A613-4AD4-8A94-73645C4947CB@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_18034D4D7FE9AE48BF19AB1B0EF2729F5F0418A89ENOKEUMSG01mgd_"
MIME-Version: 1.0
X-OriginalArrivalTime: 21 Oct 2010 12:01:27.0117 (UTC) FILETIME=[B0989FD0:01CB7117]
X-Nokia-AV: Clean
Cc: v6ops-chairs@tools.ietf.org, ron@bonica.org
Subject: Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 12:00:17 -0000

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

Hi,

Section 3.1: it is true that IPv4 PDN on-demand and deferred IPv4 address a=
llocations are "approaches" in theory, but I do not believe their applicabi=
lity in practice. E.g. what is the likelyhood that popular desktop OSes wou=
ld suddenly implement that kind of features (isn't the style usually ask DH=
CPv4 right at interface up and then renew forever)?

Section 3.1: I do not believe cellular handsets will implement DHCPv4 for c=
ellular interfaces. Hence I disagree with:"this may very well change in the=
 future release". Cellular handsets have managed without DHCPv4 since the d=
awn of packet switched cellular networks. Why on earth they would now start=
 to use DHCPv4 on cellular access at the very twilight of IPv4?

The "additional considerations" is huge, like there is no benefit whatsoeve=
r for hosts to do IPv4 on-demand or deferred IPv4 address allocation. Also =
it is non-trivial, like whether DHCPv4 should be triggered if application b=
inds socket to 127.0.0.1..

I also slightly disagree with this:" On the other hand, in the existing 3G =
UMTS networks, there is no requirement for an always-on connection". While =
there is no such requirement from standards bodies, essentially for many de=
vices there is from the end user direction: users want to have IM/Skype/ema=
il always on. Should be clarified.

I seem to agree with the conclusions document draws at the end of section 3=
.1 (there is nothing wrong in doing investigations of on-demand PDN..:)

Best regards,

Teemu

From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of e=
xt Fred Baker
Sent: 10. lokakuuta 2010 21:00
To: IPv6 Operations
Cc: v6ops-chairs@tools.ietf.org; Ron Bonica
Subject: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC

This is to initiate a two week working group last call of draft-ietf-v6ops-=
v6-in-mobile-networks. Please read it now. If you find nits (spelling error=
s, minor suggested wording changes, etc), comment to the authors; if you fi=
nd greater issues, such as disagreeing with a statement or finding addition=
al issues that need to be addressed, please post your comments to the list.

We are looking specifically for comments on the importance of the document =
as well as its content. If you have read the document and believe it to be =
of operational utility, that is also an important comment to make.

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
-->
</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 style=3D'word-wrap: break-wor=
d;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space'>

<div class=3DWordSection1>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Hi,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Section 3.1: it is true that IPv4 PDN on-demand and deferred
IPv4 address allocations are &#8220;approaches&#8221; in theory, but I do n=
ot
believe their applicability in practice. E.g. what is the likelyhood that
popular desktop OSes would suddenly implement that kind of features (isn&#8=
217;t
the style usually ask DHCPv4 right at interface up and then renew forever)?=
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Section 3.1: I do not believe cellular handsets will impleme=
nt
DHCPv4 for cellular interfaces. Hence I disagree with:&#8221;this may very =
well
change in the future release&#8221;. Cellular handsets have managed without=
 DHCPv4
since the dawn of packet switched cellular networks. Why on earth they woul=
d now
start to use DHCPv4 on cellular access at the very twilight of IPv4? <o:p><=
/o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>The &#8220;additional considerations&#8221; is huge, like th=
ere
is no benefit whatsoever for hosts to do IPv4 on-demand or deferred IPv4
address allocation. Also it is non-trivial, like whether DHCPv4 should be
triggered if application binds socket to 127.0.0.1..<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>I also slightly disagree with this:&#8221; On the other hand=
, in
the existing 3G UMTS networks, there is no requirement for an always-on
connection&#8221;. While there is no such requirement from standards bodies=
,
essentially for many devices there is from the end user direction: users wa=
nt
to have IM/Skype/email always on. Should be clarified.<o:p></o:p></span></p=
>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>I seem to agree with the conclusions document draws at the e=
nd
of section 3.1 (there is nothing wrong in doing investigations of on-demand
PDN..</span><span style=3D'font-size:11.0pt;font-family:Wingdings;color:#1F=
497D'>J</span><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'=
><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Best regards,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Teemu<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] <b>On Behalf Of </b>=
ext
Fred Baker<br>
<b>Sent:</b> 10. lokakuuta 2010 21:00<br>
<b>To:</b> IPv6 Operations<br>
<b>Cc:</b> v6ops-chairs@tools.ietf.org; Ron Bonica<br>
<b>Subject:</b> [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC<o:p></o=
:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;font-family:"Helvetica"=
,"sans-serif"'>This
is to initiate a two week working group last call of draft-ietf-v6ops-v6-in=
-mobile-networks.
Please read it now. If&nbsp;you find nits (spelling errors, minor suggested
wording changes, etc), comment to the authors; if you find greater&nbsp;iss=
ues,
such as disagreeing with a statement or finding additional issues that need=
 to
be addressed, please post your&nbsp;comments to the list.</span><o:p></o:p>=
</p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;font-family:"Helvetica"=
,"sans-serif"'><o:p>&nbsp;</o:p></span></p>

</div>

<div>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;font-family:"Helvetica"=
,"sans-serif"'>We
are looking specifically for comments on the importance of the document as =
well
as its content. If you have read the&nbsp;document and believe it to be of
operational utility, that is also an important comment to make.</span><o:p>=
</o:p></p>

</div>

</div>

</div>

</div>

</body>

</html>

--_000_18034D4D7FE9AE48BF19AB1B0EF2729F5F0418A89ENOKEUMSG01mgd_--

From yiu_lee@cable.comcast.com  Thu Oct 21 05:15:19 2010
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C04A53A67AC for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 05:15:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.173
X-Spam-Level: 
X-Spam-Status: No, score=-106.173 tagged_above=-999 required=5 tests=[AWL=1.990, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tF2XEWt1QAvq for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 05:15:18 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 9CC813A67B1 for <v6ops@ietf.org>; Thu, 21 Oct 2010 05:15:17 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.100732061; Thu, 21 Oct 2010 08:16:48 -0400
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by PACDCEXHUB02.cable.comcast.com ([fe80::11d4:f530:37a0:9f4e%12]) with mapi id 14.01.0255.000; Thu, 21 Oct 2010 08:16:48 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>, v6ops <v6ops@ietf.org>
Thread-Topic: [v6ops] Reasons not to endorse NAT66/6to4 (ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
Thread-Index: AQHLcRnVaYB7ehU/DkykGG5EBND1fA==
Date: Thu, 21 Oct 2010 12:16:47 +0000
Message-ID: <C8E5A527.1D52%yiu_lee@cable.comcast.com>
In-Reply-To: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.0.0.100825
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <19AF7E80F0F30B42859098D275FE85F6@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 12:15:19 -0000

Hi Remi,

I think you miss the point. Nobody here argues 6to4 was a better service
or offered this service as a primary IPv6 service. Every one agrees that
native, 6rd, etc. are far better choices. All we are saying it there are
few people (decreasing in number according to Eric) are still using 6to4
(consciously or unconsciously). To make them happier until they move to
"true" IPv6 service, an operator could offer a simple way to control the
return path. Nothing more, nothing less.

As far as I know, most operators are spending their energy to deploy IPv6.
This effort is small but does benefit a few individual and the cost is
low.=20

Cheers,
Yiu


On 10/21/10 6:17 AM, "R=E9mi Despr=E9s" <remi.despres@free.fr> wrote:

>
>Le 20 oct. 2010 =E0 22:15, Victor Kuarsingh a =E9crit :
>
>> The suggestion [to adopt PMT, i.e. an combination of NAT66 with 6to4
>>relays] was based on the fact that [6to4 is] out there.  We take what we
>>have and try and use it for good.
>
>There is in my understanding a far better approach:
>"Rather than spending energy to partially fix some 6to4 problems, while
>creating new ones, deploy the "real IPv6 service" asap, and suggest to
>turn 6to4 off while it's not too difficult.
>
>The "Real IPv6 service" is as follows:
>- It offers reliable connectivity to all native IPv6 addresses (unlike
>6to4).
>- It gives ISPs control of the QoS they offer to their customers (unlike
>6to4).
>- It guarantees e2e network transparency between any pair of native IPv6
>addresses (unlike NAT66).
>- This being achieved, one doesn't care whether e2e paths are totally
>dual-stack, partially 6rd, partially 6a44, or whatever, provided the
>service is available.
>
>A serious concern with 6to4 is that, without strict precautions that
>aren't taken today, it becomes an evil: it tends to disgust users from
>IPv6 in general (it has connectivity and QoS problems that are far beyond
>Grandma's understanding capability). On the other hand, the real IPv6
>service keeps people satisfied.
>
>Please, don't get me wrong:
>- 6to4 has been great for early IPv6 between IPv4 clouds, and can still
>work perfectly between two 6to4 IPv6 addresses.
>- The idea of combining 6to4 relays with NAT66's (be they stateless or
>stateful), is worth discussing it, and thanks for clearly raising the
>issue.
>
>But the point is that, to facilitate real IPv6 deployment and willful
>user acceptance, NAT66/6to4 would be counterproductive.
>
>
>Regards,
>RD
>_______________________________________________
>v6ops mailing list
>v6ops@ietf.org
>https://www.ietf.org/mailman/listinfo/v6ops


From remi.despres@free.fr  Thu Oct 21 05:45:29 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 790BA3A699A for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 05:45:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.453
X-Spam-Level: 
X-Spam-Status: No, score=-1.453 tagged_above=-999 required=5 tests=[AWL=0.496,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Epwni4hYkcft for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 05:44:58 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.2]) by core3.amsl.com (Postfix) with ESMTP id 2B0D33A68F5 for <v6ops@ietf.org>; Thu, 21 Oct 2010 05:44:21 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2106.sfr.fr (SMTP Server) with ESMTP id D1FF8700009C; Thu, 21 Oct 2010 14:45:55 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2106.sfr.fr (SMTP Server) with ESMTP id 6973B700009E; Thu, 21 Oct 2010 14:45:55 +0200 (CEST)
X-SFR-UUID: 20101021124555432.6973B700009E@msfrf2106.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <4CC01B0C.5020406@inex.ie>
Date: Thu, 21 Oct 2010 14:45:54 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FE1F03BC-EB55-4117-9EF6-A73B38AFD5B4@free.fr>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr> <4CC01B0C.5020406@inex.ie>
To: Nick Hilliard <nick@inex.ie>
X-Mailer: Apple Mail (2.1081)
Cc: v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 12:45:29 -0000

Le 21 oct. 2010 =E0 12:50, Nick Hilliard a =E9crit :

> On 21/10/2010 11:17, R=E9mi Despr=E9s wrote:
>> But the point is that, to facilitate real IPv6 deployment and willful
>> user acceptance, NAT66/6to4 would be counterproductive.
>=20
> I agree with all of these points.  They're all good and valid.

Good, but reading what you say next, it seems you have significant =
doubts!

> However, the reality is that the CPE market is shockingly badly =
equipped as regards ipv6 support, and in many situations the provider =
side edge equipment isn't much better.

That is the point of adding clean solutions that are still missing.
(6a44, which Brian Carpenter, Sheng Jiang, and myself, are proposing is =
precisely that. It provides a solution for hosts behind legacy CPEs, at =
a cost of simple code to be added in host-OS's, and a simple add-on in =
one or a few ISP border devices.) =20

>  Remember, much of this equipment operates on a 5y lifetime basis, and =
even today, lots of vendors are telling people that their ipv6 =
deployment plans are only really beginning (both for CPE and provider =
edge kit).

6rd concerns customer sites where CPEs can be updated, yes, but doesn't =
need PE modifications (RFC 5569 and 5969))
6a44 concerns hosts behind legacy CPEs, provided they can be upgraded, =
but doesn't need PE modification either.
=20
>  For this reason, lack of functional ipv6 support on the last-mile =
will continue to be a problem for many years to come.

Not necessarily if taken with the appropriate tools (remember that it =
took Free.fr only 5 weeks from "no intention to support IPv6" to "It's =
deployed, our customers can turn it on").

> It kills me to say it - it really, really does - but in this instance, =
the overwhelming cretinousness introduced by =
draft-kuarsingh-v6ops-provider-managed-tunnel is very slightly surpassed =
by the even more overwhelmingly cretinous attitude of the cheap-as-chips =
vendors which are _still_ today designing kit which will never be ipv6 =
capable.
>=20
> So, despite loathing this draft and every crap engineering principal =
it stands for,


> I am forced to admit that at this stage, we need it.

I hope you will understand you are not forced at all.

> In case there's any doubt, I feel dirty to have to say this.

You will feel a lot cleaner when you avoid to say it ;-).

Regards,
RD




From john_brzozowski@cable.comcast.com  Thu Oct 21 05:51:44 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 760E73A6934 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 05:51:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.779
X-Spam-Level: 
X-Spam-Status: No, score=-107.779 tagged_above=-999 required=5 tests=[AWL=0.684, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id irlJuvIYfrrU for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 05:51:42 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 2290D3A67B1 for <v6ops@ietf.org>; Thu, 21 Oct 2010 05:51:42 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.100740506; Thu, 21 Oct 2010 08:53:13 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by PACDCEXHUB02.cable.comcast.com ([fe80::11d4:f530:37a0:9f4e%12]) with mapi id 14.01.0255.000; Thu, 21 Oct 2010 08:53:13 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: Tore Anderson <tore.anderson@redpill-linpro.com>, "Brian E. Carpenter" <brian.e.carpenter@gmail.com>
Thread-Topic: [v6ops] Economic incentive for 2002::/16 [was draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt]
Thread-Index: AQHLcR7rM4g8rKhNUUO5ua1UW6mO9A==
Date: Thu, 21 Oct 2010 12:53:12 +0000
Message-ID: <C8E5AFFA.2A8E0%john_brzozowski@cable.comcast.com>
In-Reply-To: <4CBFFF07.1070302@redpill-linpro.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <C674F0855B08024C83DFC21C1FA9B87F@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] Economic incentive for 2002::/16 [was draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt]
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 12:51:44 -0000

On 10/21/10 4:51 AM, "Tore Anderson" <tore.anderson@redpill-linpro.com>
wrote:

> Brian, John,
>=20
> * Brian E Carpenter
>=20
>> The 6to4 client will try to find a benevolent relay as close as
>> possible; if they fail to find one, they will never show up as 6to4
>> users anyway. "Destination unreachable" for 192.88.99.1 would kill
>> the problem at source.
>=20
> Null-routing the anycast address is counter-productive as it will not
> prevent 6to4 implementations from setting up the tunnel interface, even
> if the null-route produces ICMPv4 unreachables.  So you end up ensuring
> that any application that attempts to use the 6to4 tunnel for
> connectivity is blackholed.
>=20
> This is true for Windows 7's default-on 6to4 adapter, at least.  Couple
> this with software that prefers 6to4 to IPv4, such as Opera <10.50 or
> Mac OS X (if Windows Internet Connection Sharing is active), and you've
> just created another =ABbroken user=BB and made it even more difficult th=
an
> it already is for content providers out there to get approval for
> publishing quad As.  We _really_ don't need that...
[jjmb] I concur with your points above.  Black-holing the 6to4 IPv4 anycast
is not recommended and will make matters worse.
>=20
> It's much better, then, to let the user have a decent shot at using 6to4
> successfully, even if that means the outbound traffic has to trampoline
> off a third party relay somewhere.  The best would be if the SP has
> relays on-net (like Comcast has), but if they don't it's actually much
> better for the end users if there's as many open relays as possible
> available.  That would improve the chances that the closest relay is
> actually fairly close and won't cause the latencies to suffer too badly.
[jjmb] The point I would like to reinforce is that operators really should
seriously consider deploying their own 6to4 relays.
>=20
> * John Brzozowksi
>=20
>> From what we are seeing, operators should not announce their relays
>> publicly over IPv4.  Open 6to4 relays seem to yield undesirable
>> behavior.
>=20
> The undesirable behaviour is really that 6to4 is being used as much as
> it is and in preference to IPv4.  Unfortunately, that cat is out of the
> bag.  Shutting down the open relays won't help, it will just worsen the
> whole ordeal.
[jjmb] indeed, my main point here was to ensure that moving forward
operators deploy relays for use by their subscriber base and not announced
them openly.
>=20
> Best regards,

=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
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From remi.despres@free.fr  Thu Oct 21 06:37:28 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 931F93A68AD for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 06:37:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.153
X-Spam-Level: 
X-Spam-Status: No, score=-1.153 tagged_above=-999 required=5 tests=[AWL=0.196,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id olafsFX+O698 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 06:37:27 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.2]) by core3.amsl.com (Postfix) with ESMTP id 0F9113A67E6 for <v6ops@ietf.org>; Thu, 21 Oct 2010 06:37:27 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2106.sfr.fr (SMTP Server) with ESMTP id 51946700008F; Thu, 21 Oct 2010 15:39:02 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2106.sfr.fr (SMTP Server) with ESMTP id BB4FA700008A; Thu, 21 Oct 2010 15:39:01 +0200 (CEST)
X-SFR-UUID: 20101021133901767.BB4FA700008A@msfrf2106.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <C8E5A527.1D52%yiu_lee@cable.comcast.com>
Date: Thu, 21 Oct 2010 15:39:00 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A2FC1ABA-62B1-4517-A633-22316AC11605@free.fr>
References: <C8E5A527.1D52%yiu_lee@cable.comcast.com>
To: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
X-Mailer: Apple Mail (2.1081)
Cc: v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 13:37:28 -0000

Le 21 oct. 2010 =E0 14:16, Lee, Yiu a =E9crit :

> Hi Remi,
>=20
> I think you miss the point.

> Nobody here argues 6to4 was a better service
> or offered this service as a primary IPv6 service.


I never suggested that anyone expressed preference for 6to4 over native =
IPv6!!!
(Please don't let people believe I misunderstand so much what people =
say.)=20
 =20
> Every one agrees that
> native, 6rd, etc. are far better choices.

> All we are saying it there are
> few people (decreasing in number according to Eric) are still using =
6to4
> (consciously or unconsciously).

True, but if real IPv6 service is added where these people are, they =
will, without doing anything, stop using 6to4.
This will improve their user experience without damaging that of those =
that already use native IPv6.

Leaving 6to4 as is, without new investments to improve it, will damage =
user experiences of NEITHER 6to4 users NOR that of native IPv6 users.

> To make them happier until they move to
> "true" IPv6 service, an operator could offer a simple way to control =
the
> return path. Nothing more, nothing less.

Let me insist that it breaks e2e transparency for native IPv6 addresses.
In particular, it doesn't open incoming connectivity in IPv6 (the IPv6 =
address a host sees is NOT the address to be used to reach it. IPv6 =
referrals become impossible!)
This is IMHO a very messy approach.

Please remember that, as it is, 6to4  AT LEAST doesn't break IPv6 e2e =
transparency.
IPv6 referrals and DNS AAAA's are possible today with 6to4 addresses.=20
=20

> As far as I know, most operators are spending their energy to deploy =
IPv6.
> This effort is small but does benefit a few individual and the cost is
> low.=20

Not sure what you mean.
If routing is IPv6-only, 6to4 isn't concerned.
If routing is duals-stack, adding 6a44 support (and encouraging host =
vendors to support 6a44) will expand real IPv6 availability WITHOUT =
BREAKING e2e transparency (i.e. IPv6 referrals and DNS AAAA's in =
particular).

In my understanding, hosts should better remain with only IPv4 turned on =
until their ISP does offer IPv6 to them, one way or another.
Any view to the contrary should IMHO be solidly argued for.

Any ISP would solve very little by supporting NAT66/6to4 combinations, =
and will, for sure, create significant problems.


Cheers,
RD

> Cheers,
> Yiu
>=20
>=20
> On 10/21/10 6:17 AM, "R=E9mi Despr=E9s" <remi.despres@free.fr> wrote:
>=20
>>=20
>> Le 20 oct. 2010 =E0 22:15, Victor Kuarsingh a =E9crit :
>>=20
>>> The suggestion [to adopt PMT, i.e. an combination of NAT66 with 6to4
>>> relays] was based on the fact that [6to4 is] out there.  We take =
what we
>>> have and try and use it for good.
>>=20
>> There is in my understanding a far better approach:
>> "Rather than spending energy to partially fix some 6to4 problems, =
while
>> creating new ones, deploy the "real IPv6 service" asap, and suggest =
to
>> turn 6to4 off while it's not too difficult.
>>=20
>> The "Real IPv6 service" is as follows:
>> - It offers reliable connectivity to all native IPv6 addresses =
(unlike
>> 6to4).
>> - It gives ISPs control of the QoS they offer to their customers =
(unlike
>> 6to4).
>> - It guarantees e2e network transparency between any pair of native =
IPv6
>> addresses (unlike NAT66).
>> - This being achieved, one doesn't care whether e2e paths are totally
>> dual-stack, partially 6rd, partially 6a44, or whatever, provided the
>> service is available.
>>=20
>> A serious concern with 6to4 is that, without strict precautions that
>> aren't taken today, it becomes an evil: it tends to disgust users =
from
>> IPv6 in general (it has connectivity and QoS problems that are far =
beyond
>> Grandma's understanding capability). On the other hand, the real IPv6
>> service keeps people satisfied.
>>=20
>> Please, don't get me wrong:
>> - 6to4 has been great for early IPv6 between IPv4 clouds, and can =
still
>> work perfectly between two 6to4 IPv6 addresses.
>> - The idea of combining 6to4 relays with NAT66's (be they stateless =
or
>> stateful), is worth discussing it, and thanks for clearly raising the
>> issue.
>>=20
>> But the point is that, to facilitate real IPv6 deployment and willful
>> user acceptance, NAT66/6to4 would be counterproductive.
>>=20
>>=20
>> Regards,
>> RD
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>=20



From yiu_lee@cable.comcast.com  Thu Oct 21 07:02:37 2010
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 449FF3A68B9 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 07:02:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.339
X-Spam-Level: 
X-Spam-Status: No, score=-106.339 tagged_above=-999 required=5 tests=[AWL=1.824, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pMLhxXwz9+1J for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 07:02:36 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 6E6C43A68AD for <v6ops@ietf.org>; Thu, 21 Oct 2010 07:02:33 -0700 (PDT)
Received: from ([24.40.55.42]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.100762825; Thu, 21 Oct 2010 10:04:03 -0400
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by PACDCEXHUB01.cable.comcast.com ([fe80::d1e7:20b5:9b63:21a6%12]) with mapi id 14.01.0255.000; Thu, 21 Oct 2010 10:04:03 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Thread-Topic: [v6ops] Reasons not to endorse NAT66/6to4 (ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
Thread-Index: AQHLcRnVaYB7ehU/DkykGG5EBND1fJNLq3wA///D8IA=
Date: Thu, 21 Oct 2010 14:04:02 +0000
Message-ID: <C8E5BF08.1D6E%yiu_lee@cable.comcast.com>
In-Reply-To: <A2FC1ABA-62B1-4517-A633-22316AC11605@free.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.0.0.100825
x-originating-ip: [147.191.125.11]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <57BC4767FA8A7A46ADD306D40E41DDE2@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 14:02:37 -0000

Hi Remi,

>
>Any ISP would solve very little by supporting NAT66/6to4 combinations,
>and will, for sure, create significant problems.

>I still try to understand what significant problems we refer to here. I
>do agree that this only helps a small subset of users. However the cost
>to implement this is minimal. It is "almost" transparent to the users
>except those relying on 6to4 for incoming connectivity. I don't have a
>number how many people using 6to4 for incoming connections, but I guess
>the number would be small. And we will let them to opt-out. This
>methodology targets only for those who didn't even know 6to4 is on by
>default and may experience some bad experience.

Cheers,
Yiu


From yiu_lee@cable.comcast.com  Thu Oct 21 07:06:34 2010
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 96DFD3A6A00 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 07:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.479
X-Spam-Level: 
X-Spam-Status: No, score=-106.479 tagged_above=-999 required=5 tests=[AWL=1.684, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lAwlkbtqlAHM for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 07:06:33 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 4C7BD3A68AD for <v6ops@ietf.org>; Thu, 21 Oct 2010 07:06:33 -0700 (PDT)
Received: from ([24.40.55.42]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.100764227; Thu, 21 Oct 2010 10:08:03 -0400
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by PACDCEXHUB01.cable.comcast.com ([fe80::d1e7:20b5:9b63:21a6%12]) with mapi id 14.01.0255.000; Thu, 21 Oct 2010 10:08:03 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Thread-Topic: [v6ops] Reasons not to endorse NAT66/6to4 (ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
Thread-Index: AQHLcRnVaYB7ehU/DkykGG5EBND1fJNLq3wA///E/YA=
Date: Thu, 21 Oct 2010 14:08:02 +0000
Message-ID: <C8E5C0B1.1D70%yiu_lee@cable.comcast.com>
In-Reply-To: <A2FC1ABA-62B1-4517-A633-22316AC11605@free.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.0.0.100825
x-originating-ip: [147.191.125.11]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B4E3D7FB56C54E4985D413A637DD126E@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 14:06:34 -0000

Hi Remi,

>
>I never suggested that anyone expressed preference for 6to4 over native
>IPv6!!!
>(Please don't let people believe I misunderstand so much what people
>say.)=20
> =20
>>I apologize if I mis-understood you. I saw you wrote a long paragraph to
>>explain what is "The Real IPv6 Service". I thought you tried to compare
>>this to other IPv6 technologies. Again, my apology.
>>=20
>>=20
>


From prvs=9032ec11e=Scott.Beuker@sjrb.ca  Thu Oct 21 07:22:48 2010
Return-Path: <prvs=9032ec11e=Scott.Beuker@sjrb.ca>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB8713A68A9 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 07:22:48 -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, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A7G7U4384kjV for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 07:22:47 -0700 (PDT)
Received: from prdcg4ipta01x-ext.shaw.ca (prdcg4ipta01x-ext.shaw.ca [204.209.208.146]) by core3.amsl.com (Postfix) with ESMTP id 88F743A66B4 for <v6ops@ietf.org>; Thu, 21 Oct 2010 07:22:47 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.58,217,1286172000"; d="scan'208";a="45102766"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 21 Oct 2010 08:24:02 -0600
Message-ID: <1EA76BAD7F050648910C041BDDED8CD5013FDBB5@PRDCG4EXVW01-5.OSS.PRD>
In-Reply-To: <FE1F03BC-EB55-4117-9EF6-A73B38AFD5B4@free.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops] Reasons not to endorse NAT66/6to4 (refdraft-kuarsingh-v6ops-provider-managed-tunnel-00)
Thread-Index: ActxHhA178K90KcESIG8CwEjkzEyJAACdTsw
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr><4CC01B0C.5020406@inex.ie> <FE1F03BC-EB55-4117-9EF6-A73B38AFD5B4@free.fr>
From: "Scott Beuker" <Scott.Beuker@sjrb.ca>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>, "v6ops" <v6ops@ietf.org>
X-OriginalArrivalTime: 21 Oct 2010 14:24:03.0338 (UTC) FILETIME=[9C8056A0:01CB712B]
X-TM-AS-Product-Ver: SMEX-8.0.0.1285-6.500.1024-17716.007
X-TM-AS-Result: No--29.976900-0.000000-31
X-TM-AS-User-Approved-Sender: Yes
X-TM-AS-User-Blocked-Sender: No
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (refdraft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 14:22:48 -0000

Remi,

> That is the point of adding clean solutions that are still missing.
> (6a44, which Brian Carpenter, Sheng Jiang, and myself, are proposing =
is
> precisely that. It provides a solution for hosts behind legacy CPEs, =
at
> a cost of simple code to be added in host-OS's, and a simple add-on in
> one or a few ISP border devices.)

Code to be added to host operating systems? So in other words, a totally =
unrealistic and still-born idea. You're at least 5 years too late my =
friend.

The time for idealism has come and gone. Drastic changes to the IPv6 =
transition landscape are no longer possible in a world where the =
customer purchases their own CPE devices and expects a decent few years =
use from them.

Here are the current realities:

1) 6to4 is out there
2) 6to4 provides a safety net to IPv6-only content for an IPv4-only user
3) 6to4 doesn't impede native IPv6 deployment, nor is it a substitute =
for it

Deal with that and move forward; or at least, please stay out of the way =
of those of us who are trying to.=20

Promotion of your own draft is not a reason to try to impede someone =
else's.



> 6rd concerns customer sites where CPEs can be updated, yes, but =
doesn't
> need PE modifications (RFC 5569 and 5969))
> 6a44 concerns hosts behind legacy CPEs, provided they can be upgraded,
> but doesn't need PE modification either.

So in other words, both are totally irrelevant to this discussion. =
Neither addresses the use case that 6to4-PMT does. Please read the draft =
to better understand this.



> Not necessarily if taken with the appropriate tools (remember that it
> took Free.fr only 5 weeks from "no intention to support IPv6" to "It's
> deployed, our customers can turn it on").

Free.fr has control of the customer CPE. 6to4-PMT comes to relevance in =
a totally different situation.



> > I am forced to admit that at this stage, we need it.
>=20
> I hope you will understand you are not forced at all.

Though it's always nice to have people ready and willing to tell other =
network operators, in totally different markets, cultures, and technical =
environments, what they must and must not do... at some point you have =
to step back and realize that your experiences are not necessarily =
universally applicable.

Thanks,
Scott

From remi.despres@free.fr  Thu Oct 21 07:33:11 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0BB983A6A18 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 07:33:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.454
X-Spam-Level: 
X-Spam-Status: No, score=-1.454 tagged_above=-999 required=5 tests=[AWL=0.495,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RRwBIo-ZynzH for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 07:33:10 -0700 (PDT)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.81]) by core3.amsl.com (Postfix) with ESMTP id C92F83A6A12 for <v6ops@ietf.org>; Thu, 21 Oct 2010 07:33:08 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2404.sfr.fr (SMTP Server) with ESMTP id 2B3F7700008D; Thu, 21 Oct 2010 16:34:42 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2404.sfr.fr (SMTP Server) with ESMTP id B8ECC700008F; Thu, 21 Oct 2010 16:34:41 +0200 (CEST)
X-SFR-UUID: 20101021143441757.B8ECC700008F@msfrf2404.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <C8E5BF08.1D6E%yiu_lee@cable.comcast.com>
Date: Thu, 21 Oct 2010 16:34:40 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B28A491B-D1A4-47DD-B886-19143FF84DD4@free.fr>
References: <C8E5BF08.1D6E%yiu_lee@cable.comcast.com>
To: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
X-Mailer: Apple Mail (2.1081)
Cc: v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 14:33:11 -0000

Le 21 oct. 2010 =E0 16:04, Lee, Yiu a =E9crit :
>> ...
>> Any ISP would solve very little by supporting NAT66/6to4 =
combinations,
>> and will, for sure, create significant problems.
>=20
>> I still try to understand what significant problems we refer to here. =
I
>> do agree that this only helps a small subset of users. However the =
cost
>> to implement this is minimal. It is "almost" transparent to the users
>> except those relying on 6to4 for incoming connectivity.

>> I don't have a
>> number how many people using 6to4 for incoming connections, but I =
guess
>> the number would be small.

Maybe, but breaking what works is IMHO a bad approach to good service.
Preserving backward compatibility is in general a must, (especially if =
the lack of it may hurt an unknown number of users, for the sake of =
moderately improving service for another unknown number of users.)=20


>> And we will let them to opt-out.

=CC see.
It looks like you would have made your decision in view of the low cost.
I hope you only talk about the experimental phase.

Le me make the point that changing this decision for the future won't =
cost much either.
And I hope you marketing guys will know about this discussion.

>> This
>> methodology targets only for those who didn't even know 6to4 is on by
>> default and may experience some bad experience.

Again, these users should be advised not to activate IPv6 (or to =
deactivate IPv6 as the case may be), until you offer native IPv6 to =
them, one way or another.=20
On the other hand, hosts that take advantage of their global IPv6 =
address for incoming connectivity will see their service broken when you =
impose NAT66 to all your 6to4 users.=20
(And, if it isn't for incoming connectivity that IPv6 is used, IPv6 can =
be still dispensed with for still some time. No FUD to be had about any =
deterioration of user experience.)=20

Cheers,
RD


>=20
> Cheers,
> Yiu
>=20



From jhw@apple.com  Thu Oct 21 07:54:15 2010
Return-Path: <jhw@apple.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CF26A3A6818 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 07:54:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cfkeEHQTzvjo for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 07:54:15 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id BDE583A67B7 for <v6ops@ietf.org>; Thu, 21 Oct 2010 07:54:14 -0700 (PDT)
Received: from relay15.apple.com (relay15.apple.com [17.128.113.54]) by mail-out3.apple.com (Postfix) with ESMTP id 53C49B0F7AD3 for <v6ops@ietf.org>; Thu, 21 Oct 2010 07:55:50 -0700 (PDT)
X-AuditID: 11807136-b7b3aae0000033cc-56-4cc054761564
Received: from elliott.apple.com (elliott.apple.com [17.151.62.13]) by relay15.apple.com (Apple SCV relay) with SMTP id F7.40.13260.67450CC4; Thu, 21 Oct 2010 07:55:50 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from [172.16.1.7] (adit.conjury.org [75.101.54.88]) by elliott.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LAN00ATFAT14A60@elliott.apple.com> for v6ops@ietf.org; Thu, 21 Oct 2010 07:55:50 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <C8E55803.2A7F5%john_brzozowski@cable.comcast.com>
Date: Thu, 21 Oct 2010 07:55:49 -0700
Message-id: <82D3A362-1B89-4C22-AB78-E16A036C6A57@apple.com>
References: <C8E55803.2A7F5%john_brzozowski@cable.comcast.com>
To: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 14:54:15 -0000

On Oct 20, 2010, at 23:37, Brzozowski, John wrote:

> The only other comment I would offer is why would a shorter prefix be offered to an IGD if the device cannot support it?

An IGD could be upgraded in the field to support it.

Some people consider it a software error (rather than a product development mistake) that AirPort doesn't currently offer IPv6 service on its guest network.  If it did, then it would choose a second subnet identifier.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



From remi.despres@free.fr  Thu Oct 21 08:38:35 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8900A3A684C for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 08:38:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.457
X-Spam-Level: 
X-Spam-Status: No, score=-1.457 tagged_above=-999 required=5 tests=[AWL=0.492,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tmc9GDP9wDyu for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 08:38:34 -0700 (PDT)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.81]) by core3.amsl.com (Postfix) with ESMTP id 17D9B3A67B7 for <v6ops@ietf.org>; Thu, 21 Oct 2010 08:38:34 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2404.sfr.fr (SMTP Server) with ESMTP id 3D2467000089; Thu, 21 Oct 2010 17:40:09 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2404.sfr.fr (SMTP Server) with ESMTP id B79E8700008F; Thu, 21 Oct 2010 17:40:08 +0200 (CEST)
X-SFR-UUID: 20101021154008752.B79E8700008F@msfrf2404.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <1EA76BAD7F050648910C041BDDED8CD5013FDBB5@PRDCG4EXVW01-5.OSS.PRD>
Date: Thu, 21 Oct 2010 17:40:07 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <51CDFEA8-3EA5-4D85-833C-75E2FAC2BC87@free.fr>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr><4CC01B0C.5020406@inex.ie> <FE1F03BC-EB55-4117-9EF6-A73B38AFD5B4@free.fr> <1EA76BAD7F050648910C041BDDED8CD5013FDBB5@PRDCG4EXVW01-5.OSS.PRD>
To: "Scott Beuker" <Scott.Beuker@sjrb.ca>
X-Mailer: Apple Mail (2.1081)
Cc: v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (refdraft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 15:38:35 -0000

Le 21 oct. 2010 =E0 16:24, Scott Beuker a =E9crit :

> Remi,
>=20
>> That is the point of adding clean solutions that are still missing.
>> (6a44, which Brian Carpenter, Sheng Jiang, and myself, are proposing =
is
>> precisely that. It provides a solution for hosts behind legacy CPEs, =
at
>> a cost of simple code to be added in host-OS's, and a simple add-on =
in
>> one or a few ISP border devices.)
>=20
> Code to be added to host operating systems? So in other words, a =
totally unrealistic and still-born idea. You're at least 5 years too =
late my friend.

Well, my friend, I have seen many updates of host software in the last 5 =
year. Some of them made necessary because complex softwares badly needed =
fixes.

The question is, how much a particular add-on will improve user =
experience, in face of how expensive is it to have it.=20

> The time for idealism has come and gone.

I never saw myself as an idealist.
(As a matter of fact, I believe that having invented 6rd, and convinced =
Free.fr that they could (in their case) deploy it rapidly, pleads for a =
reasonable level of pragmatism.)


> Drastic changes to the IPv6 transition landscape are no longer =
possible in a world where the customer purchases their own CPE devices =
and expects a decent few years use from them.

Please read the 6a44 draft to see that, contrary to what you seem to =
believe, I don't forget them.

> Here are the current realities:
>=20
> 1) 6to4 is out there
> 2) 6to4 provides a safety net to IPv6-only content for an IPv4-only =
user

How many such contents do you know?
Are there vendors unwise enough to offer in IPv6-only a service destined =
to some IPv4-only users?

In any case, relying on a good quality safety (native IPv6) is safer =
than relying on one that has holes in it (6to4).
And this is even truer if some people envisage to make new holes in it =
(loss of e2e transparency, due to NAT66, while 6to4 still ejoys it =
today.)


> 3) 6to4 doesn't impede native IPv6 deployment, nor is it a substitute =
for it

It doesn't impede native IPv6 deployment, that's clear, but it may =
impede motivation to request it, people believing that it offers =
good-enough service.

If spoiled with NAT66 (which is the subject at hand):
- it will deteriorate 6to4 itself (IPv6 referrals impossible with 6to4 =
addresses)
- it will deteriorate native IPv6 (no more guarantee of e2e transparency =
between two native addresses (one may be an avatar of a 6to4 address, =
with a NAT66 in the way.  =20

 =20
> Deal with that and move forward;


> or at least, please stay out of the way of those of us who are trying =
to.=20

Please feel free not to read what I write, and go your own way
Being asked to react to the new NAT66/6to4 proposal, I found it my duty =
to tell what I believe is important.


> Promotion of your own draft is not a reason to try to impede someone =
else's.

I refer to existing or proposed or solutions, even if some of them come =
from myself, when it is relevant to the discussion at hand.
Here again, I find it my duty. =20

>=20
>> 6rd concerns customer sites where CPEs can be updated, yes, but =
doesn't
>> need PE modifications (RFC 5569 and 5969))
>> 6a44 concerns hosts behind legacy CPEs, provided they can be =
upgraded,
>> but doesn't need PE modification either.
>=20
> So in other words, both are totally irrelevant to this discussion.

> Neither addresses the use case that 6to4-PMT does.

This was to clarify that dual-stack routing is NOT the only way to offer =
native IPv6 SERVICE, the best alternative to a broken 6to4.
I still believe it fits here.=20
=20
> Please read the draft to better understand this.

I did read the draft, and believe I do understand its implications =
reasonably well.
If you feel I misunderstood something, please let me know.

>> Not necessarily if taken with the appropriate tools (remember that it
>> took Free.fr only 5 weeks from "no intention to support IPv6" to =
"It's
>> deployed, our customers can turn it on").
>=20
> Free.fr has control of the customer CPE. 6to4-PMT comes to relevance =
in a totally different situation.

This sentence of mine you quote was an answer to "lack of functional =
ipv6 support on the last-mile will continue to be a problem for many =
years to come.".
I still believe it is relevant.

>>> I am forced to admit that at this stage, we need it.
>>=20
>> I hope you will understand you are not forced at all.

This sentence of mine is more understandable if you also quote what Nick =
Hilliard was writing just after, namely:=20
"In case there's any doubt, I feel dirty to have to say this."
I was in fact hoping that he would be relieved from "feeling dirty".
>=20
> Though it's always nice to have people ready and willing to tell other =
network operators, in totally different markets, cultures, and technical =
environments, what they must and must not do... at some point you have =
to step back and realize that your experiences are not necessarily =
universally applicable.

I certainly have no intention to tell you what you must do.

RD



>=20
> Thanks,
> Scott



From Bill.Armstrong@chartercom.com  Thu Oct 21 08:39:23 2010
Return-Path: <Bill.Armstrong@chartercom.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7EBA43A6A1E for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 08:39:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.549
X-Spam-Level: 
X-Spam-Status: No, score=-1.549 tagged_above=-999 required=5 tests=[AWL=-0.450, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_93=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OxTiwAi0dC+D for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 08:38:57 -0700 (PDT)
Received: from mail.chartercom.com (mail.chartercom.com [24.217.29.16]) by core3.amsl.com (Postfix) with ESMTP id 002583A6A12 for <v6ops@ietf.org>; Thu, 21 Oct 2010 08:38:52 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.58,217,1286168400"; d="scan'208";a="123307016"
Received: from unknown (HELO KSTLMEXHTP01.CORP.CHARTERCOM.COM) ([192.168.31.33]) by mail.chartercom.com with ESMTP; 21 Oct 2010 10:40:28 -0500
Received: from KSTLMEXCP02MBX.CORP.CHARTERCOM.COM ([192.168.31.13]) by KSTLMEXHTP01.CORP.CHARTERCOM.COM ([192.168.31.33]) with mapi; Thu, 21 Oct 2010 10:40:28 -0500
From: "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>
To: Scott Beuker <Scott.Beuker@sjrb.ca>, =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>, v6ops <v6ops@ietf.org>
Date: Thu, 21 Oct 2010 10:40:26 -0500
Thread-Topic: [v6ops] Reasons not to endorse NAT66/6to4 (refdraft-kuarsingh-v6ops-provider-managed-tunnel-00)
Thread-Index: ActxHhA178K90KcESIG8CwEjkzEyJAACdTswAAFDtVA=
Message-ID: <E71300B9B9041340B238540990BF04530915AAD92B@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr><4CC01B0C.5020406@inex.ie> <FE1F03BC-EB55-4117-9EF6-A73B38AFD5B4@free.fr> <1EA76BAD7F050648910C041BDDED8CD5013FDBB5@PRDCG4EXVW01-5.OSS.PRD>
In-Reply-To: <1EA76BAD7F050648910C041BDDED8CD5013FDBB5@PRDCG4EXVW01-5.OSS.PRD>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4	(refdraft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 15:39:23 -0000

This is it.=20

I keep hearing "just offer Native" or "deploy -[insert unreleased\un-deploy=
ed transition technology here]-" as the way to side step this proposal\prob=
lem. But I think the fundamental fact being *consistently* overlooked by th=
e opponents to the draft is that the hands of a good deal of the operators =
are tied by the currently deployed(+100K's) unmanaged(not the ISPs to touch=
) CPE.

If the fix offered up to "just enable Native" is "simply" replace ALL the C=
PE that are IPv6 incapable and\or offer firmware patches for the remaining =
gear then we may need to have larger discussion on economic realities. Stuf=
f costs money, new stuff doubly so.=20

We need to stop looking at this as an OR to SOLVE the IPv6 problem but rath=
er view it as an AND (as seen in bANDaid) which can help foster the adoptio=
n of IPv6.

=09

-Bill


-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of S=
cott Beuker
Sent: Thursday, October 21, 2010 9:24 AM
To: R=E9mi Despr=E9s; v6ops
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (refdraft-kuarsingh-=
v6ops-provider-managed-tunnel-00)

Remi,

> That is the point of adding clean solutions that are still missing.
> (6a44, which Brian Carpenter, Sheng Jiang, and myself, are proposing is
> precisely that. It provides a solution for hosts behind legacy CPEs, at
> a cost of simple code to be added in host-OS's, and a simple add-on in
> one or a few ISP border devices.)

Code to be added to host operating systems? So in other words, a totally un=
realistic and still-born idea. You're at least 5 years too late my friend.

The time for idealism has come and gone. Drastic changes to the IPv6 transi=
tion landscape are no longer possible in a world where the customer purchas=
es their own CPE devices and expects a decent few years use from them.

Here are the current realities:

1) 6to4 is out there
2) 6to4 provides a safety net to IPv6-only content for an IPv4-only user
3) 6to4 doesn't impede native IPv6 deployment, nor is it a substitute for it

Deal with that and move forward; or at least, please stay out of the way of=
 those of us who are trying to.=20

Promotion of your own draft is not a reason to try to impede someone else's.



> 6rd concerns customer sites where CPEs can be updated, yes, but doesn't
> need PE modifications (RFC 5569 and 5969))
> 6a44 concerns hosts behind legacy CPEs, provided they can be upgraded,
> but doesn't need PE modification either.

So in other words, both are totally irrelevant to this discussion. Neither =
addresses the use case that 6to4-PMT does. Please read the draft to better =
understand this.



> Not necessarily if taken with the appropriate tools (remember that it
> took Free.fr only 5 weeks from "no intention to support IPv6" to "It's
> deployed, our customers can turn it on").

Free.fr has control of the customer CPE. 6to4-PMT comes to relevance in a t=
otally different situation.



> > I am forced to admit that at this stage, we need it.
>=20
> I hope you will understand you are not forced at all.

Though it's always nice to have people ready and willing to tell other netw=
ork operators, in totally different markets, cultures, and technical enviro=
nments, what they must and must not do... at some point you have to step ba=
ck and realize that your experiences are not necessarily universally applic=
able.

Thanks,
Scott
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

E-MAIL CONFIDENTIALITY NOTICE:=20

=20

=20

=20

The contents of this e-mail message and=20
any attachments are intended solely for the=20
addressee(s) and may contain confidential=20
and/or legally privileged information. If you=20
are not the intended recipient of this message=20
or if this message has been addressed to you=20
in error, please immediately alert the sender
 by reply e-mail and then delete this message=20
and any attachments. If you are not the=20
intended recipient, you are notified that=20
any use, dissemination, distribution, copying,=20
or storage of this message or any attachment=20
is strictly prohibited.









From pch-b6B5344D9@u-1.phicoh.com  Thu Oct 21 08:52:34 2010
Return-Path: <pch-b6B5344D9@u-1.phicoh.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B4EA63A680E for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 08:52:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.233
X-Spam-Level: 
X-Spam-Status: No, score=-4.233 tagged_above=-999 required=5 tests=[AWL=0.066,  BAYES_00=-2.599, GB_I_LETTER=-2, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vRQAEjLx4Z18 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 08:52:33 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by core3.amsl.com (Postfix) with ESMTP id 5AD383A6844 for <v6ops@ietf.org>; Thu, 21 Oct 2010 08:52:32 -0700 (PDT)
Received: from stereo.hq.phicoh.net ([127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #2) id m1P8xSv-0001gOC; Thu, 21 Oct 2010 17:54 +0200
Message-Id: <m1P8xSv-0001gOC@stereo.hq.phicoh.net>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
From: Philip Homburg <pch-v6ops@u-1.phicoh.com>
Sender: pch-b6B5344D9@u-1.phicoh.com
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr><4CC01B0C.5020406@inex.ie> <FE1F03BC-EB55-4117-9EF6-A73B38AFD5B4@free.fr> <1EA76BAD7F050648910C041BDDED8CD5013FDBB5@PRDCG4EXVW01-5.OSS.PRD> <51CDFEA8-3EA5-4D85-833C-75E2FAC2BC87@free.fr> 
In-reply-to: Your message of "Thu, 21 Oct 2010 17:40:07 +0200 ." <51CDFEA8-3EA5-4D85-833C-75E2FAC2BC87@free.fr> 
Date: Thu, 21 Oct 2010 17:53:52 +0200
Cc: Scott Beuker <Scott.Beuker@sjrb.ca>, v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (refdraft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 15:52:34 -0000

In your letter dated Thu, 21 Oct 2010 17:40:07 +0200 you wrote:
>> 2) 6to4 provides a safety net to IPv6-only content for an IPv4-only user
>
>How many such contents do you know?
>Are there vendors unwise enough to offer in IPv6-only a service destined to=
> some IPv4-only users?

IPv6-only service is expected to be any host that is IPv6 connected and behind
a carrier-grade NAT box.

So, after IPv4 addresses run out that will be any consumer or small business
that wants to run a web server, ssh, etc. 

But the most likely source of IPv6-only will be all kinds of peer to peer
protocols that many consumers want to run, and that are quite incompatible
with carrier-grade NAT.



From jhw@apple.com  Thu Oct 21 09:18:45 2010
Return-Path: <jhw@apple.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 595B73A6A18 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 09:18:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q1t6y0CvSXi2 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 09:18:44 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id 650113A69F4 for <v6ops@ietf.org>; Thu, 21 Oct 2010 09:18:44 -0700 (PDT)
Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out4.apple.com (Postfix) with ESMTP id 52D10B7379F9 for <v6ops@ietf.org>; Thu, 21 Oct 2010 09:20:20 -0700 (PDT)
X-AuditID: 11807137-b7bf7ae000000f05-2a-4cc06844e8f0
Received: from gertie.apple.com (gertie.apple.com [17.151.62.15]) by relay16.apple.com (Apple SCV relay) with SMTP id 78.4B.03845.44860CC4; Thu, 21 Oct 2010 09:20:20 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from [66.109.106.185] by gertie.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LAN005UFEPRUR80@gertie.apple.com> for v6ops@ietf.org; Thu, 21 Oct 2010 09:20:20 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <E71300B9B9041340B238540990BF04530915AAD92B@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM>
Date: Thu, 21 Oct 2010 09:20:15 -0700
Message-id: <75632460-4C3A-428A-9601-22E113012786@apple.com>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr> <4CC01B0C.5020406@inex.ie> <FE1F03BC-EB55-4117-9EF6-A73B38AFD5B4@free.fr> <1EA76BAD7F050648910C041BDDED8CD5013FDBB5@PRDCG4EXVW01-5.OSS.PRD> <E71300B9B9041340B238540990BF04530915AAD92B@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM>
To: v6ops <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [v6ops] Reasons not to endorse	NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 16:18:45 -0000

On Oct 21, 2010, at 08:40, Armstrong, Bill R wrote:
> 
> We need to stop looking at this as an OR to SOLVE the IPv6 problem but rather view it as an AND (as seen in bANDaid) which can help foster the adoption of IPv6.

I remain unpersuaded.  I think that operators who can't bring themselves to deploy IPv6 without breaking end-to-end transparency for their subscribers should leave the business of providing IPv6 service to others.

There will still be plenty of demand for IPv4-only service for a long time to come.  It's going to be a long long time before content providers start turning off their IPv4 servers.  In other words, I see no reason to believe the statement in section 2 quoted below:

>> After IPv4 run out, IPv6 content may grow rapidly and in some cases, IPv4 may not be a connection option for some web based content providers or the remote host (IPv6 Only).

Operators still have plenty of time before they have to worry about providing subscribers with access to IPv6-only hosts on the public Internet.  I-D.ietf-behave-v6v4-framework section 2.4, "Scenario 4: an IPv4 network to the IPv6 Internet," speaks to this.

>> [...] From the transition phase discussion in Section 1.4, this scenario will probably only occur when we are well past the early stage of the "S" curve and the IPv4/IPv6 transition has already moved to the right direction. [...]

If operators have good reason to believe there is a pressing need to serve to the public IPv6 Internet to subscribers on IPv4-only first-mile links without waiting for an upgrade cycle on either residential gateways or host operating systems, then it's well past time they should have brought their concerns to the BEHAVE working group.

Maybe they should have spoke up when RFC 4966 was under discussion.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



From remi.despres@free.fr  Thu Oct 21 09:19:52 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 16D013A69F2 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 09:19:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.861
X-Spam-Level: 
X-Spam-Status: No, score=-0.861 tagged_above=-999 required=5 tests=[AWL=-0.112, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, J_CHICKENPOX_93=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2EFigWP5+Q8I for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 09:19:50 -0700 (PDT)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.81]) by core3.amsl.com (Postfix) with ESMTP id A63613A68AD for <v6ops@ietf.org>; Thu, 21 Oct 2010 09:19:49 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2404.sfr.fr (SMTP Server) with ESMTP id 3D6337000095; Thu, 21 Oct 2010 18:21:25 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2404.sfr.fr (SMTP Server) with ESMTP id 867B47000098; Thu, 21 Oct 2010 18:21:24 +0200 (CEST)
X-SFR-UUID: 20101021162124550.867B47000098@msfrf2404.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <E71300B9B9041340B238540990BF04530915AAD92B@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM>
Date: Thu, 21 Oct 2010 18:21:23 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C4E55787-A0DE-4435-9663-3591D6F5B978@free.fr>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr><4CC01B0C.5020406@inex.ie> <FE1F03BC-EB55-4117-9EF6-A73B38AFD5B4@free.fr> <1EA76BAD7F050648910C041BDDED8CD5013FDBB5@PRDCG4EXVW01-5.OSS.PRD> <E71300B9B9041340B238540990BF04530915AAD92B@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM>
To: "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>
X-Mailer: Apple Mail (2.1081)
Cc: Scott Beuker <Scott.Beuker@sjrb.ca>, v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (refdraft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 16:19:52 -0000

Le 21 oct. 2010 =E0 17:40, Armstrong, Bill R a =E9crit :

> This is it.=20
>=20
> I keep hearing "just offer Native" or "deploy -[insert =
unreleased\un-deployed transition technology here]-" as the way to side =
step this proposal\problem. But I think the fundamental fact being =
*consistently* overlooked by the opponents to the draft is that the =
hands of a good deal of the operators are tied by the currently =
deployed(+100K's) unmanaged(not the ISPs to touch) CPE.
>=20
> If the fix offered up to "just enable Native" is "simply" replace ALL =
the CPE that are IPv6 incapable and\or offer firmware patches for the =
remaining gear then we may need to have larger discussion on economic =
realities. Stuff costs money, new stuff doubly so.

It is NOT "simply replace ALL the CPE that are IPv6 incapable".
Brian Carpenter, Sheng Jiang, and myself, propose a simple solution for =
native IPv6 across NAT44 CPEs i(draft-despres-softwire-6a44-00). =20
Its limitation (strong at this point, but which may evolve as the =
specification gets well understood) is that it depends on an update in =
host software.
Host software upgrades appear to be unavoidable to achieve simple, =
efficient, and reliable, native IPv6 across legacy CPEs.


> We need to stop looking at this as an OR to SOLVE the IPv6 problem but =
rather view it as an AND (as seen in bANDaid) which can help foster the =
adoption of IPv6.

We all agree, I believe, that one size doesn't fit all.

The specific danger of NAT66/6to4 is that, being easy to implement and =
to operate, there is a temptation to deploy it.
But, if deployed, it breaks things that worked before.
In particular it breaks the possibility to advertise one's own 6to4 =
address and to be reachable at this address by IPv6 hosts that have =
access to a 6to4 relay.
(Besides, but this is less important, the amount of user experience that =
could be improved by a NAT66/6to4 deployment is unclear.)=20


Regards,=20
RD


>=20
> =09
>=20
> -Bill
>=20
>=20
> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf =
Of Scott Beuker
> Sent: Thursday, October 21, 2010 9:24 AM
> To: R=E9mi Despr=E9s; v6ops
> Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 =
(refdraft-kuarsingh-v6ops-provider-managed-tunnel-00)
>=20
> Remi,
>=20
>> That is the point of adding clean solutions that are still missing.
>> (6a44, which Brian Carpenter, Sheng Jiang, and myself, are proposing =
is
>> precisely that. It provides a solution for hosts behind legacy CPEs, =
at
>> a cost of simple code to be added in host-OS's, and a simple add-on =
in
>> one or a few ISP border devices.)
>=20
> Code to be added to host operating systems? So in other words, a =
totally unrealistic and still-born idea. You're at least 5 years too =
late my friend.
>=20
> The time for idealism has come and gone. Drastic changes to the IPv6 =
transition landscape are no longer possible in a world where the =
customer purchases their own CPE devices and expects a decent few years =
use from them.
>=20
> Here are the current realities:
>=20
> 1) 6to4 is out there
> 2) 6to4 provides a safety net to IPv6-only content for an IPv4-only =
user
> 3) 6to4 doesn't impede native IPv6 deployment, nor is it a substitute =
for it
>=20
> Deal with that and move forward; or at least, please stay out of the =
way of those of us who are trying to.=20
>=20
> Promotion of your own draft is not a reason to try to impede someone =
else's.
>=20
>=20
>=20
>> 6rd concerns customer sites where CPEs can be updated, yes, but =
doesn't
>> need PE modifications (RFC 5569 and 5969))
>> 6a44 concerns hosts behind legacy CPEs, provided they can be =
upgraded,
>> but doesn't need PE modification either.
>=20
> So in other words, both are totally irrelevant to this discussion. =
Neither addresses the use case that 6to4-PMT does. Please read the draft =
to better understand this.
>=20
>=20
>=20
>> Not necessarily if taken with the appropriate tools (remember that it
>> took Free.fr only 5 weeks from "no intention to support IPv6" to =
"It's
>> deployed, our customers can turn it on").
>=20
> Free.fr has control of the customer CPE. 6to4-PMT comes to relevance =
in a totally different situation.
>=20
>=20
>=20
>>> I am forced to admit that at this stage, we need it.
>>=20
>> I hope you will understand you are not forced at all.
>=20
> Though it's always nice to have people ready and willing to tell other =
network operators, in totally different markets, cultures, and technical =
environments, what they must and must not do... at some point you have =
to step back and realize that your experiences are not necessarily =
universally applicable.
>=20
> Thanks,
> Scott
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>=20
> E-MAIL CONFIDENTIALITY NOTICE:=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> The contents of this e-mail message and=20
> any attachments are intended solely for the=20
> addressee(s) and may contain confidential=20
> and/or legally privileged information. If you=20
> are not the intended recipient of this message=20
> or if this message has been addressed to you=20
> in error, please immediately alert the sender
> by reply e-mail and then delete this message=20
> and any attachments. If you are not the=20
> intended recipient, you are notified that=20
> any use, dissemination, distribution, copying,=20
> or storage of this message or any attachment=20
> is strictly prohibited.
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20



From fernando.gont.netbook.win@gmail.com  Thu Oct 21 10:02:57 2010
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C7E13A6A4C for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 10:02:57 -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=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FXGqCJrcTGc1 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 10:02:56 -0700 (PDT)
Received: from mail-iw0-f194.google.com (mail-iw0-f194.google.com [209.85.214.194]) by core3.amsl.com (Postfix) with ESMTP id 4C8293A69F2 for <v6ops@ietf.org>; Thu, 21 Oct 2010 10:02:56 -0700 (PDT)
Received: by iwn33 with SMTP id 33so555323iwn.1 for <v6ops@ietf.org>; Thu, 21 Oct 2010 10:04:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=8CcdB33j6Sj0FrKHu9wO7QBLGuuxU0FrKU02Apap0kU=; b=O5HxV2hmMeqa9Aia4JIoLG6pQeTka1AmRJiDvm9U7Htj4UdsVaSCwnmgaWpIZqqJF1 6Pu6gN5/AByxABwmnchcKdwz9VAMJLeG/cSAwOLtSWJ59Enh6cuIY4wg0/vaLNY+k9HC 3KJK9ixaEaTDtTt8nNyf/+ALsxt0Ssn7dKYKY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=RR2OSXrgkGFOQ6UJemhQFZ32COq1Y8fKYrp6sqSKVPbU1hfTGu5DH9p9Fb/XuH2TXe 8eGFvHfo+6ot0vKvjzmB9hl29ywseIj1FON+Pg8VILAiIMt4M0kh6JnQzCt3jT5rFdLu mi4T/jZ0kjxFEMSLq44d1/jvp4+6lleMRSId0=
Received: by 10.42.13.75 with SMTP id c11mr764892ica.481.1287680668499; Thu, 21 Oct 2010 10:04:28 -0700 (PDT)
Received: from [200.160.9.194] ([200.160.9.194]) by mx.google.com with ESMTPS id y41sm1427147yhc.4.2010.10.21.10.04.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 21 Oct 2010 10:04:27 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4CC07295.8000603@gont.com.ar>
Date: Thu, 21 Oct 2010 14:04:21 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr>
In-Reply-To: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (ref	draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 17:02:57 -0000

On 21/10/2010 07:17 a.m., Rémi Després wrote:

> A serious concern with 6to4 is that, without strict precautions that
> aren't taken today, it becomes an evil: it tends to disgust users
> from IPv6 in general (it has connectivity and QoS problems that are
> far beyond Grandma's understanding capability). On the other hand,
> the real IPv6 service keeps people satisfied.

I don't think people care about which version of IP is servicing them.
If Grandma cannot understand the problems you're referring to, the
distinction between IPv4 and IPv6 is probably out of her scope, too.

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





From cb.list6@gmail.com  Thu Oct 21 10:09:24 2010
Return-Path: <cb.list6@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5F3283A6A22 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 10:09:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.861
X-Spam-Level: 
X-Spam-Status: No, score=-1.861 tagged_above=-999 required=5 tests=[AWL=0.138,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vRakHxuNmRun for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 10:09:23 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id F337A3A6A1C for <v6ops@ietf.org>; Thu, 21 Oct 2010 10:09:22 -0700 (PDT)
Received: by qwc9 with SMTP id 9so3828636qwc.31 for <v6ops@ietf.org>; Thu, 21 Oct 2010 10:10:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=W46weHX+rgZuNxjb0ddJbDPXZre3Twau/JKqUsqKhGw=; b=O/QK1MhXz9aNiQzeMJXY/A333GNAztrGQQpgS43qtZm1PkLfnxZeNhaIfOLWaYJ4KT yr/sDakY4wTSJv+dD69jm2wWjPD2PjVIXAjEWZFONNhEwf8+0P8x+dMESn6an5x2G1Ig lb7DoUKUHJ7sW5YAzmPh/Dp5/swDRtVKsgtGw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=NBHVTh2nxZxDh6TVKhf6fMPsWt0mcoc2d/GN8DQJci4KCgfxNpr6cdfM6vZUamqR49 AtPmRjXoUoClIG9BIyRwWEGqmHPKB9s3JOQiebZE7AdOrdJPMvr/rN3wjm6eQyWeN7e5 9EtZZLjmS78AMVeklaayjePI72DrMjtzQbBtg=
MIME-Version: 1.0
Received: by 10.229.181.206 with SMTP id bz14mr1005960qcb.245.1287681058393; Thu, 21 Oct 2010 10:10:58 -0700 (PDT)
Received: by 10.229.245.201 with HTTP; Thu, 21 Oct 2010 10:10:58 -0700 (PDT)
In-Reply-To: <75632460-4C3A-428A-9601-22E113012786@apple.com>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr> <4CC01B0C.5020406@inex.ie> <FE1F03BC-EB55-4117-9EF6-A73B38AFD5B4@free.fr> <1EA76BAD7F050648910C041BDDED8CD5013FDBB5@PRDCG4EXVW01-5.OSS.PRD> <E71300B9B9041340B238540990BF04530915AAD92B@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <75632460-4C3A-428A-9601-22E113012786@apple.com>
Date: Thu, 21 Oct 2010 10:10:58 -0700
Message-ID: <AANLkTinMC81DScKi3YQ3jnWKe9ufr=6bqG_RGTp0yP28@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: james woodyatt <jhw@apple.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 17:09:24 -0000

On Thu, Oct 21, 2010 at 9:20 AM, james woodyatt <jhw@apple.com> wrote:
> On Oct 21, 2010, at 08:40, Armstrong, Bill R wrote:
>>
>> We need to stop looking at this as an OR to SOLVE the IPv6 problem but r=
ather view it as an AND (as seen in bANDaid) which can help foster the adop=
tion of IPv6.
>
> I remain unpersuaded. =A0I think that operators who can't bring themselve=
s to deploy IPv6 without breaking end-to-end transparency for their subscri=
bers should leave the business of providing IPv6 service to others.
>
> There will still be plenty of demand for IPv4-only service for a long tim=
e to come. =A0It's going to be a long long time before content providers st=
art turning off their IPv4 servers. =A0In other words, I see no reason to b=
elieve the statement in section 2 quoted below:
>
>>> After IPv4 run out, IPv6 content may grow rapidly and in some cases, IP=
v4 may not be a connection option for some web based content providers or t=
he remote host (IPv6 Only).
>
> Operators still have plenty of time before they have to worry about provi=
ding subscribers with access to IPv6-only hosts on the public Internet. =A0=
I-D.ietf-behave-v6v4-framework section 2.4, "Scenario 4: an IPv4 network to=
 the IPv6 Internet," speaks to this.
>

I strongly disagree with this, especially since i have firm plans of
launching IPv6-only handsets + NAT64 next year (2011). In fact i have
it running in beta today with ~200 paying subscribers.  This is the
reality of smartly not investing more in IPv4, having been reject for
IPv4 space, and running on empty (aka bogons) for several years now.
And, the mobile and cloud network edge keeps growing quickly.

The moral of the story is that access networks will be IPv4-only,
IPv6-only, or dual stack. Content providers need to choose who they
want to see their content, this is usually results in when they go
dual-stack, not if.  I don't believe that my customers care about the
difference on many types of handsets between IPv4 + NAT44 and IPv6 +
NAT64, just like they don't care that i give them bogons today.
Content providers may tell the difference between IPv6 and IPv4 on the
UE, and many have made it clear they prefer IPv6 since it takes the
CGN out of the path when they (content) do offer IPv6 services.

Side note, it is also cheaper and more robust to run IPv6, since major
content players like Google and Facebook will no longer need NAT44 in
my network, their native IPv6 by-passes the NAT64.

Cameron

>>> [...] From the transition phase discussion in Section 1.4, this scenari=
o will probably only occur when we are well past the early stage of the "S"=
 curve and the IPv4/IPv6 transition has already moved to the right directio=
n. [...]
>
> If operators have good reason to believe there is a pressing need to serv=
e to the public IPv6 Internet to subscribers on IPv4-only first-mile links =
without waiting for an upgrade cycle on either residential gateways or host=
 operating systems, then it's well past time they should have brought their=
 concerns to the BEHAVE working group.
>
> Maybe they should have spoke up when RFC 4966 was under discussion.
>
>
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, communications engineering
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

From Bill.Armstrong@chartercom.com  Thu Oct 21 10:19:21 2010
Return-Path: <Bill.Armstrong@chartercom.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 674163A69AF for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 10:19:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.437
X-Spam-Level: 
X-Spam-Status: No, score=-1.437 tagged_above=-999 required=5 tests=[AWL=-0.338, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_93=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28aljnsjznCB for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 10:19:19 -0700 (PDT)
Received: from mail.chartercom.com (mail.chartercom.com [24.217.29.16]) by core3.amsl.com (Postfix) with ESMTP id 23E153A6A7B for <v6ops@ietf.org>; Thu, 21 Oct 2010 10:19:04 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.58,218,1286168400"; d="scan'208";a="123330480"
Received: from unknown (HELO KSTLMEXHTP02.CORP.CHARTERCOM.COM) ([192.168.31.32]) by mail.chartercom.com with ESMTP; 21 Oct 2010 12:20:39 -0500
Received: from KSTLMEXCP02MBX.CORP.CHARTERCOM.COM ([192.168.31.13]) by KSTLMEXHTP02.CORP.CHARTERCOM.COM ([192.168.31.32]) with mapi; Thu, 21 Oct 2010 12:20:39 -0500
From: "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Date: Thu, 21 Oct 2010 12:20:36 -0500
Thread-Topic: [v6ops] Reasons not to endorse NAT66/6to4 (refdraft-kuarsingh-v6ops-provider-managed-tunnel-00)
Thread-Index: ActxPAMKH9ILHYfXR1WbpeyD6f8aUQAA4jHg
Message-ID: <E71300B9B9041340B238540990BF04530915AADB66@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr><4CC01B0C.5020406@inex.ie> <FE1F03BC-EB55-4117-9EF6-A73B38AFD5B4@free.fr> <1EA76BAD7F050648910C041BDDED8CD5013FDBB5@PRDCG4EXVW01-5.OSS.PRD> <E71300B9B9041340B238540990BF04530915AAD92B@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <C4E55787-A0DE-4435-9663-3591D6F5B978@free.fr>
In-Reply-To: <C4E55787-A0DE-4435-9663-3591D6F5B978@free.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: Scott Beuker <Scott.Beuker@sjrb.ca>, v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (refdraft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 17:19:21 -0000

So we all agree that software upgrades are the key. I'm not NOT going to su=
pport\deploy 6rd 6a44 or DS-lite because of PMT rather due to the fact that=
 they don't exist yet, its new stuff, once software has been written and ha=
s been folded into the dev cycles of all the major hardware\software vendor=
s then we have yet another tool that can be used to work toward ubiquitous =
IPv6. So while we wait, 6to4 is there NOW and what PMT adds from a function=
ality perspective(I think) outweighs the potential breakage concerns.=20


-Bill


-----Original Message-----
From: R=E9mi Despr=E9s [mailto:remi.despres@free.fr]=20
Sent: Thursday, October 21, 2010 11:21 AM
To: Armstrong, Bill R
Cc: Scott Beuker; v6ops
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (refdraft-kuarsingh-=
v6ops-provider-managed-tunnel-00)


Le 21 oct. 2010 =E0 17:40, Armstrong, Bill R a =E9crit :

> This is it.=20
>=20
> I keep hearing "just offer Native" or "deploy -[insert unreleased\un-depl=
oyed transition technology here]-" as the way to side step this proposal\pr=
oblem. But I think the fundamental fact being *consistently* overlooked by =
the opponents to the draft is that the hands of a good deal of the operator=
s are tied by the currently deployed(+100K's) unmanaged(not the ISPs to tou=
ch) CPE.
>=20
> If the fix offered up to "just enable Native" is "simply" replace ALL the=
 CPE that are IPv6 incapable and\or offer firmware patches for the remainin=
g gear then we may need to have larger discussion on economic realities. St=
uff costs money, new stuff doubly so.

It is NOT "simply replace ALL the CPE that are IPv6 incapable".
Brian Carpenter, Sheng Jiang, and myself, propose a simple solution for nat=
ive IPv6 across NAT44 CPEs i(draft-despres-softwire-6a44-00). =20
Its limitation (strong at this point, but which may evolve as the specifica=
tion gets well understood) is that it depends on an update in host software.
Host software upgrades appear to be unavoidable to achieve simple, efficien=
t, and reliable, native IPv6 across legacy CPEs.


> We need to stop looking at this as an OR to SOLVE the IPv6 problem but ra=
ther view it as an AND (as seen in bANDaid) which can help foster the adopt=
ion of IPv6.

We all agree, I believe, that one size doesn't fit all.

The specific danger of NAT66/6to4 is that, being easy to implement and to o=
perate, there is a temptation to deploy it.
But, if deployed, it breaks things that worked before.
In particular it breaks the possibility to advertise one's own 6to4 address=
 and to be reachable at this address by IPv6 hosts that have access to a 6t=
o4 relay.
(Besides, but this is less important, the amount of user experience that co=
uld be improved by a NAT66/6to4 deployment is unclear.)=20


Regards,=20
RD


>=20
> =09
>=20
> -Bill
>=20
>=20
> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of=
 Scott Beuker
> Sent: Thursday, October 21, 2010 9:24 AM
> To: R=E9mi Despr=E9s; v6ops
> Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (refdraft-kuarsing=
h-v6ops-provider-managed-tunnel-00)
>=20
> Remi,
>=20
>> That is the point of adding clean solutions that are still missing.
>> (6a44, which Brian Carpenter, Sheng Jiang, and myself, are proposing is
>> precisely that. It provides a solution for hosts behind legacy CPEs, at
>> a cost of simple code to be added in host-OS's, and a simple add-on in
>> one or a few ISP border devices.)
>=20
> Code to be added to host operating systems? So in other words, a totally =
unrealistic and still-born idea. You're at least 5 years too late my friend.
>=20
> The time for idealism has come and gone. Drastic changes to the IPv6 tran=
sition landscape are no longer possible in a world where the customer purch=
ases their own CPE devices and expects a decent few years use from them.
>=20
> Here are the current realities:
>=20
> 1) 6to4 is out there
> 2) 6to4 provides a safety net to IPv6-only content for an IPv4-only user
> 3) 6to4 doesn't impede native IPv6 deployment, nor is it a substitute for=
 it
>=20
> Deal with that and move forward; or at least, please stay out of the way =
of those of us who are trying to.=20
>=20
> Promotion of your own draft is not a reason to try to impede someone else=
's.
>=20
>=20
>=20
>> 6rd concerns customer sites where CPEs can be updated, yes, but doesn't
>> need PE modifications (RFC 5569 and 5969))
>> 6a44 concerns hosts behind legacy CPEs, provided they can be upgraded,
>> but doesn't need PE modification either.
>=20
> So in other words, both are totally irrelevant to this discussion. Neithe=
r addresses the use case that 6to4-PMT does. Please read the draft to bette=
r understand this.
>=20
>=20
>=20
>> Not necessarily if taken with the appropriate tools (remember that it
>> took Free.fr only 5 weeks from "no intention to support IPv6" to "It's
>> deployed, our customers can turn it on").
>=20
> Free.fr has control of the customer CPE. 6to4-PMT comes to relevance in a=
 totally different situation.
>=20
>=20
>=20
>>> I am forced to admit that at this stage, we need it.
>>=20
>> I hope you will understand you are not forced at all.
>=20
> Though it's always nice to have people ready and willing to tell other ne=
twork operators, in totally different markets, cultures, and technical envi=
ronments, what they must and must not do... at some point you have to step =
back and realize that your experiences are not necessarily universally appl=
icable.
>=20
> Thanks,
> Scott
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>=20
> E-MAIL CONFIDENTIALITY NOTICE:=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> The contents of this e-mail message and=20
> any attachments are intended solely for the=20
> addressee(s) and may contain confidential=20
> and/or legally privileged information. If you=20
> are not the intended recipient of this message=20
> or if this message has been addressed to you=20
> in error, please immediately alert the sender
> by reply e-mail and then delete this message=20
> and any attachments. If you are not the=20
> intended recipient, you are notified that=20
> any use, dissemination, distribution, copying,=20
> or storage of this message or any attachment=20
> is strictly prohibited.
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20



E-MAIL CONFIDENTIALITY NOTICE:=20

=20

=20

=20

The contents of this e-mail message and=20
any attachments are intended solely for the=20
addressee(s) and may contain confidential=20
and/or legally privileged information. If you=20
are not the intended recipient of this message=20
or if this message has been addressed to you=20
in error, please immediately alert the sender
 by reply e-mail and then delete this message=20
and any attachments. If you are not the=20
intended recipient, you are notified that=20
any use, dissemination, distribution, copying,=20
or storage of this message or any attachment=20
is strictly prohibited.









From remi.despres@free.fr  Thu Oct 21 10:27:50 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24D5D3A6866 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 10:27:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.46
X-Spam-Level: 
X-Spam-Status: No, score=-1.46 tagged_above=-999 required=5 tests=[AWL=0.489,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ZkQItz7fmCo for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 10:27:49 -0700 (PDT)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.81]) by core3.amsl.com (Postfix) with ESMTP id 10DC83A69FB for <v6ops@ietf.org>; Thu, 21 Oct 2010 10:27:49 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2404.sfr.fr (SMTP Server) with ESMTP id 4B7CA7000096; Thu, 21 Oct 2010 19:29:24 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2404.sfr.fr (SMTP Server) with ESMTP id DCF927000089; Thu, 21 Oct 2010 19:29:23 +0200 (CEST)
X-SFR-UUID: 20101021172923905.DCF927000089@msfrf2404.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <4CC07295.8000603@gont.com.ar>
Date: Thu, 21 Oct 2010 19:29:22 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <28A6DE3B-3D4D-45DF-98D3-4B7AFE0E6CF1@free.fr>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr> <4CC07295.8000603@gont.com.ar>
To: Fernando Gont <fernando@gont.com.ar>
X-Mailer: Apple Mail (2.1081)
Cc: v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (ref	draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 17:27:50 -0000

Le 21 oct. 2010 =E0 19:04, Fernando Gont a =E9crit :

> On 21/10/2010 07:17 a.m., R=E9mi Despr=E9s wrote:
>=20
>> A serious concern with 6to4 is that, without strict precautions that
>> aren't taken today, it becomes an evil: it tends to disgust users
>> from IPv6 in general (it has connectivity and QoS problems that are
>> far beyond Grandma's understanding capability). On the other hand,
>> the real IPv6 service keeps people satisfied.
>=20
> I don't think people care about which version of IP is servicing them.

Absolutely right.
Robustness and plug-and-play are a must for ordinary people.
Solutions that work only in 95% of cases, and that you have to configure =
are the worse of all.=20


> If Grandma cannot understand the problems you're referring to, the
> distinction between IPv4 and IPv6 is probably out of her scope, too.

Absolutely.
Her host, should by default work in IPv6  only if it a native IPv6 =
address.
A host that accepts by default to work with 6to4 or Teredo isn't a good =
approach for Grandma.

Regards,
RD



From root@core3.amsl.com  Thu Oct 21 10:30:03 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: v6ops@ietf.org
Delivered-To: v6ops@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id A1A2B3A6A3B; Thu, 21 Oct 2010 10:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20101021173003.A1A2B3A6A3B@core3.amsl.com>
Date: Thu, 21 Oct 2010 10:30:01 -0700 (PDT)
Cc: v6ops@ietf.org
Subject: [v6ops] I-D Action:draft-ietf-v6ops-tunnel-security-concerns-03.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 17:30:03 -0000

--NextPart

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


	Title           : Security Concerns With IP Tunneling
	Author(s)       : S. Krishnan, et al.
	Filename        : draft-ietf-v6ops-tunnel-security-concerns-03.txt
	Pages           : 19
	Date            : 2010-10-21

A number of security concerns with IP tunnels are documented in this
memo.  The intended audience of this document includes network
administrators and future protocol developers.  The primary intent of
this document is to raise the awareness level regarding the security
issues with IP tunnels as deployed today.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-tunnel-security-concerns-03.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-v6ops-tunnel-security-concerns-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-10-21101904.I-D@ietf.org>


--NextPart--

From remi.despres@free.fr  Thu Oct 21 10:33:17 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B87563A6A22 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 10:33:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.863
X-Spam-Level: 
X-Spam-Status: No, score=-0.863 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, J_CHICKENPOX_93=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J1hR1grF9Pya for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 10:33:16 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.21]) by core3.amsl.com (Postfix) with ESMTP id 179B43A6A1B for <v6ops@ietf.org>; Thu, 21 Oct 2010 10:33:14 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2313.sfr.fr (SMTP Server) with ESMTP id D21267000094; Thu, 21 Oct 2010 19:34:49 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2313.sfr.fr (SMTP Server) with ESMTP id 1F04E7000091; Thu, 21 Oct 2010 19:34:48 +0200 (CEST)
X-SFR-UUID: 20101021173449127.1F04E7000091@msfrf2313.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <E71300B9B9041340B238540990BF04530915AADB66@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM>
Date: Thu, 21 Oct 2010 19:34:48 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DAA74363-9A86-4104-8A90-82614497BFB7@free.fr>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr><4CC01B0C.5020406@inex.ie> <FE1F03BC-EB55-4117-9EF6-A73B38AFD5B4@free.fr> <1EA76BAD7F050648910C041BDDED8CD5013FDBB5@PRDCG4EXVW01-5.OSS.PRD> <E71300B9B9041340B238540990BF04530915AAD92B@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <C4E55787-A0DE-4435-9663-3591D6F5B978@free.fr> <E71300B9B9041340B238540990BF04530915AADB66@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM>
To: "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>
X-Mailer: Apple Mail (2.1081)
Cc: Scott Beuker <Scott.Beuker@sjrb.ca>, v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (refdraft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 17:33:17 -0000

Le 21 oct. 2010 =E0 19:20, Armstrong, Bill R a =E9crit :

> So we all agree that software upgrades are the key. I'm not NOT going =
to support\deploy 6rd 6a44 or DS-lite because of PMT rather due to the =
fact that they don't exist yet, its new stuff, once software has been =
written and has been folded into the dev cycles of all the major =
hardware\software vendors then we have yet another tool that can be used =
to work toward ubiquitous IPv6.

> So while we wait, 6to4 is there NOW

Yes, some people use it 6to4 its limits.=20
Breaking 6to4's e2e transparency is likely to create more problems than =
it is expected to solve.
=20
> and what PMT adds from a functionality perspective(I think) outweighs =
the potential breakage concerns.

Very different view here.
At least people won't be able to say they weren't informed.

RD






>=20
>=20
>=20
> -Bill
>=20
>=20
> -----Original Message-----
> From: R=E9mi Despr=E9s [mailto:remi.despres@free.fr]=20
> Sent: Thursday, October 21, 2010 11:21 AM
> To: Armstrong, Bill R
> Cc: Scott Beuker; v6ops
> Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 =
(refdraft-kuarsingh-v6ops-provider-managed-tunnel-00)
>=20
>=20
> Le 21 oct. 2010 =E0 17:40, Armstrong, Bill R a =E9crit :
>=20
>> This is it.=20
>>=20
>> I keep hearing "just offer Native" or "deploy -[insert =
unreleased\un-deployed transition technology here]-" as the way to side =
step this proposal\problem. But I think the fundamental fact being =
*consistently* overlooked by the opponents to the draft is that the =
hands of a good deal of the operators are tied by the currently =
deployed(+100K's) unmanaged(not the ISPs to touch) CPE.
>>=20
>> If the fix offered up to "just enable Native" is "simply" replace ALL =
the CPE that are IPv6 incapable and\or offer firmware patches for the =
remaining gear then we may need to have larger discussion on economic =
realities. Stuff costs money, new stuff doubly so.
>=20
> It is NOT "simply replace ALL the CPE that are IPv6 incapable".
> Brian Carpenter, Sheng Jiang, and myself, propose a simple solution =
for native IPv6 across NAT44 CPEs i(draft-despres-softwire-6a44-00). =20
> Its limitation (strong at this point, but which may evolve as the =
specification gets well understood) is that it depends on an update in =
host software.
> Host software upgrades appear to be unavoidable to achieve simple, =
efficient, and reliable, native IPv6 across legacy CPEs.
>=20
>=20
>> We need to stop looking at this as an OR to SOLVE the IPv6 problem =
but rather view it as an AND (as seen in bANDaid) which can help foster =
the adoption of IPv6.
>=20
> We all agree, I believe, that one size doesn't fit all.
>=20
> The specific danger of NAT66/6to4 is that, being easy to implement and =
to operate, there is a temptation to deploy it.
> But, if deployed, it breaks things that worked before.
> In particular it breaks the possibility to advertise one's own 6to4 =
address and to be reachable at this address by IPv6 hosts that have =
access to a 6to4 relay.
> (Besides, but this is less important, the amount of user experience =
that could be improved by a NAT66/6to4 deployment is unclear.)=20
>=20
>=20
> Regards,=20
> RD
>=20
>=20
>>=20
>> =09
>>=20
>> -Bill
>>=20
>>=20
>> -----Original Message-----
>> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On =
Behalf Of Scott Beuker
>> Sent: Thursday, October 21, 2010 9:24 AM
>> To: R=E9mi Despr=E9s; v6ops
>> Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 =
(refdraft-kuarsingh-v6ops-provider-managed-tunnel-00)
>>=20
>> Remi,
>>=20
>>> That is the point of adding clean solutions that are still missing.
>>> (6a44, which Brian Carpenter, Sheng Jiang, and myself, are proposing =
is
>>> precisely that. It provides a solution for hosts behind legacy CPEs, =
at
>>> a cost of simple code to be added in host-OS's, and a simple add-on =
in
>>> one or a few ISP border devices.)
>>=20
>> Code to be added to host operating systems? So in other words, a =
totally unrealistic and still-born idea. You're at least 5 years too =
late my friend.
>>=20
>> The time for idealism has come and gone. Drastic changes to the IPv6 =
transition landscape are no longer possible in a world where the =
customer purchases their own CPE devices and expects a decent few years =
use from them.
>>=20
>> Here are the current realities:
>>=20
>> 1) 6to4 is out there
>> 2) 6to4 provides a safety net to IPv6-only content for an IPv4-only =
user
>> 3) 6to4 doesn't impede native IPv6 deployment, nor is it a substitute =
for it
>>=20
>> Deal with that and move forward; or at least, please stay out of the =
way of those of us who are trying to.=20
>>=20
>> Promotion of your own draft is not a reason to try to impede someone =
else's.
>>=20
>>=20
>>=20
>>> 6rd concerns customer sites where CPEs can be updated, yes, but =
doesn't
>>> need PE modifications (RFC 5569 and 5969))
>>> 6a44 concerns hosts behind legacy CPEs, provided they can be =
upgraded,
>>> but doesn't need PE modification either.
>>=20
>> So in other words, both are totally irrelevant to this discussion. =
Neither addresses the use case that 6to4-PMT does. Please read the draft =
to better understand this.
>>=20
>>=20
>>=20
>>> Not necessarily if taken with the appropriate tools (remember that =
it
>>> took Free.fr only 5 weeks from "no intention to support IPv6" to =
"It's
>>> deployed, our customers can turn it on").
>>=20
>> Free.fr has control of the customer CPE. 6to4-PMT comes to relevance =
in a totally different situation.
>>=20
>>=20
>>=20
>>>> I am forced to admit that at this stage, we need it.
>>>=20
>>> I hope you will understand you are not forced at all.
>>=20
>> Though it's always nice to have people ready and willing to tell =
other network operators, in totally different markets, cultures, and =
technical environments, what they must and must not do... at some point =
you have to step back and realize that your experiences are not =
necessarily universally applicable.
>>=20
>> Thanks,
>> Scott
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>>=20
>> E-MAIL CONFIDENTIALITY NOTICE:=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>> The contents of this e-mail message and=20
>> any attachments are intended solely for the=20
>> addressee(s) and may contain confidential=20
>> and/or legally privileged information. If you=20
>> are not the intended recipient of this message=20
>> or if this message has been addressed to you=20
>> in error, please immediately alert the sender
>> by reply e-mail and then delete this message=20
>> and any attachments. If you are not the=20
>> intended recipient, you are notified that=20
>> any use, dissemination, distribution, copying,=20
>> or storage of this message or any attachment=20
>> is strictly prohibited.
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>=20
>=20
>=20
> E-MAIL CONFIDENTIALITY NOTICE:=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> The contents of this e-mail message and=20
> any attachments are intended solely for the=20
> addressee(s) and may contain confidential=20
> and/or legally privileged information. If you=20
> are not the intended recipient of this message=20
> or if this message has been addressed to you=20
> in error, please immediately alert the sender
> by reply e-mail and then delete this message=20
> and any attachments. If you are not the=20
> intended recipient, you are notified that=20
> any use, dissemination, distribution, copying,=20
> or storage of this message or any attachment=20
> is strictly prohibited.
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20



From fernando.gont.netbook.win@gmail.com  Thu Oct 21 10:55:28 2010
Return-Path: <fernando.gont.netbook.win@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 470423A699A for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 10:55:28 -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=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NRpY+sfnvTXZ for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 10:55:26 -0700 (PDT)
Received: from mail-iw0-f194.google.com (mail-iw0-f194.google.com [209.85.214.194]) by core3.amsl.com (Postfix) with ESMTP id 93F2F3A68F3 for <v6ops@ietf.org>; Thu, 21 Oct 2010 10:55:26 -0700 (PDT)
Received: by iwn35 with SMTP id 35so6953iwn.1 for <v6ops@ietf.org>; Thu, 21 Oct 2010 10:57:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=eft99y1VrLggNb/3Z/hbrtsGKlkAoIirv3y6mL1F9t4=; b=PtYrLMikR46AQSNIJ6+YpsT+Oxf8Q6LITZ7dShw2ZfSLlxWrAOHbvBoDPx44IP8qkM kLlMTpH9P8oq2Et+uboWRIho9++Kv4LQKkzWIGMbhsUIysh70t9Y6cFGplqZOzmPsxVn KRJgNwalM743keDln7lh3G+Uf6KVpFrr8LVic=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=Kr/0VE+URimxBRBJT8GFberW7wabkJsJqDGcfrGhJiAFu9IM87f7bTeStHGSxTUsMQ VkfwufOgz+40talYW3MnQe0vI1pWPWkb+U+C69cUWZeiv8JKeJcM/EWCqeH+Vp7tZ9xQ hNUdmqBr4lxOkVfzr4wHsI/YjoFW6fIs9NHQE=
Received: by 10.42.170.10 with SMTP id d10mr1044763icz.105.1287683822439; Thu, 21 Oct 2010 10:57:02 -0700 (PDT)
Received: from [200.160.9.194] ([200.160.9.194]) by mx.google.com with ESMTPS id j27sm1464681yha.30.2010.10.21.10.57.00 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 21 Oct 2010 10:57:01 -0700 (PDT)
Sender: Fernando Gont <fernando.gont.netbook.win@gmail.com>
Message-ID: <4CC07EEA.6000306@gont.com.ar>
Date: Thu, 21 Oct 2010 14:56:58 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr> <4CC07295.8000603@gont.com.ar> <28A6DE3B-3D4D-45DF-98D3-4B7AFE0E6CF1@free.fr>
In-Reply-To: <28A6DE3B-3D4D-45DF-98D3-4B7AFE0E6CF1@free.fr>
X-Enigmail-Version: 1.1.1
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (ref	draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 17:55:28 -0000

Hi, Remi,

>> If Grandma cannot understand the problems you're referring to, the
>> distinction between IPv4 and IPv6 is probably out of her scope, too.
> 
> Absolutely.
> Her host, should by default work in IPv6  only if it a native IPv6 address.
> A host that accepts by default to work with 6to4 or Teredo isn't a good approach for Grandma.

Are you arguing that e.g. Teredo and 6to4 should be disabled by default,
or rather that IPv4 should be preferred over IPv6 when the IPv6
connectivity is provided by Teredo/6to4?

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





From jhw@apple.com  Thu Oct 21 11:09:39 2010
Return-Path: <jhw@apple.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DDEEB3A6923 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 11:09:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.19
X-Spam-Level: 
X-Spam-Status: No, score=-106.19 tagged_above=-999 required=5 tests=[AWL=0.409, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TJqc7KkcTv-r for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 11:09:39 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id 168013A68FC for <v6ops@ietf.org>; Thu, 21 Oct 2010 11:09:39 -0700 (PDT)
Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out4.apple.com (Postfix) with ESMTP id 077FEB73D89C for <v6ops@ietf.org>; Thu, 21 Oct 2010 11:11:15 -0700 (PDT)
X-AuditID: 11807137-b7bf7ae000000f05-38-4cc0824249a6
Received: from et.apple.com (et.apple.com [17.151.62.12]) by relay16.apple.com (Apple SCV relay) with SMTP id 4D.9B.03845.24280CC4; Thu, 21 Oct 2010 11:11:15 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from il0602f-dhcp196.apple.com (il0602f-dhcp196.apple.com [17.206.50.196]) by et.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LAN00B5GJUQZC30@et.apple.com> for v6ops@ietf.org; Thu, 21 Oct 2010 11:11:14 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <AANLkTinMC81DScKi3YQ3jnWKe9ufr=6bqG_RGTp0yP28@mail.gmail.com>
Date: Thu, 21 Oct 2010 11:11:14 -0700
Message-id: <4C39DDAC-1D14-47B4-88D3-042B4595E58D@apple.com>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr> <4CC01B0C.5020406@inex.ie> <FE1F03BC-EB55-4117-9EF6-A73B38AFD5B4@free.fr> <1EA76BAD7F050648910C041BDDED8CD5013FDBB5@PRDCG4EXVW01-5.OSS.PRD> <E71300B9B9041340B238540990BF04530915AAD92B@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <75632460-4C3A-428A-9601-22E113012786@apple.com> <AANLkTinMC81DScKi3YQ3jnWKe9ufr=6bqG_RGTp0yP28@mail.gmail.com>
To: v6ops WG <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 18:09:40 -0000

everyone--

I'm about to start advocating seriously that the Darwin IPv6 stop autoconfiguring interface addresses with the 2002::/16 prefix even when the Prefix Information Option has the A=1 bit set.  If this draft progresses or operators start seriously looking like they're going to deploy 6to4-PMT, then I'm pretty sure there won't be any alternative.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



From Fred.L.Templin@boeing.com  Thu Oct 21 11:32:23 2010
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 78B223A67C2 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 11:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.223
X-Spam-Level: 
X-Spam-Status: No, score=-6.223 tagged_above=-999 required=5 tests=[AWL=0.376,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dUDFN2blE1YM for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 11:32:22 -0700 (PDT)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 804663A6452 for <v6ops@ietf.org>; Thu, 21 Oct 2010 11:32:21 -0700 (PDT)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by slb-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id o9LIXtGJ008515 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <v6ops@ietf.org>; Thu, 21 Oct 2010 11:33:55 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id o9LIXsdP019158 for <v6ops@ietf.org>; Thu, 21 Oct 2010 11:33:54 -0700 (PDT)
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id o9LIXsiV019153 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK) for <v6ops@ietf.org>; Thu, 21 Oct 2010 11:33:54 -0700 (PDT)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.97]) by XCH-NWHT-11.nw.nos.boeing.com ([130.247.25.114]) with mapi; Thu, 21 Oct 2010 11:33:54 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: v6ops WG <v6ops@ietf.org>
Date: Thu, 21 Oct 2010 11:33:53 -0700
Thread-Topic: [v6ops] Reasons not to endorse NAT66/6to4
Thread-Index: ActxS2FS/UGgIOAtRM6j0q4ZhG8iswAAkOsw
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A65C59C52BC9@XCH-NW-01V.nw.nos.boeing.com>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr><4CC01B0C.5020406@ inex.ie><FE1F03BC-EB55-4117-9EF6-A73B38AFD5B4@free.fr><1EA76BAD7F050648910C 041BDDED8CD5013FDBB5@PRDCG4EXVW01-5.OSS.PRD><E71300B9B9041340B238540990BF04 530915AAD92B@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM><75632460-4C3A-428A-9601-22 E113012786@apple.com><AANLkTinMC81DScKi3YQ3jnWKe9ufr=6bqG_RGTp0yP28@mail.gmail.com> <4C39DDAC-1D14-47B4-88D3-042B4595E58D@apple.com>
In-Reply-To: <4C39DDAC-1D14-47B4-88D3-042B4595E58D@apple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 18:32:23 -0000

Some other limiting factors to consider wrt the proposal:

- strict provider-aggregated instead of provider-independent
- mobility, multihoming, traffic engineering not well supported
- only addresses IPv6-in-IPv4 (not other protocol combinations)
- tunnel MTU uncertainties

Fred
fred.l.templin@boeing.com

From fred@cisco.com  Thu Oct 21 12:14:54 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A6B93A67F6 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 12:14:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.361
X-Spam-Level: 
X-Spam-Status: No, score=-110.361 tagged_above=-999 required=5 tests=[AWL=0.238, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wY7uCkHdXq5v for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 12:14:53 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 267F43A6A56 for <v6ops@ietf.org>; Thu, 21 Oct 2010 12:14:53 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEANQuwExAZnwN/2dsb2JhbAChXnGlFZwyhUoEik2DBA
X-IronPort-AV: E=Sophos;i="4.58,218,1286150400"; d="scan'208";a="173504710"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 21 Oct 2010 19:16:29 +0000
Received: from Freds-Computer.local (rtp-vpn2-1100.cisco.com [10.82.244.76]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o9LJGCs8011795 for <v6ops@ietf.org>; Thu, 21 Oct 2010 19:16:22 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Thu, 21 Oct 2010 15:16:28 -0400
X-PGP-Universal: processed; by Freds-Computer.local on Thu, 21 Oct 2010 15:16:28 -0400
From: Fred Baker <fred@cisco.com>
Date: Thu, 21 Oct 2010 15:16:17 -0400
Message-Id: <52E02B43-ECEA-434C-85FE-4C244A812EBB@cisco.com>
To: IPv6 Operations <v6ops@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: [v6ops] Etiquette
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 19:14:54 -0000

The chairs just received a note concerned about decorum on the list. In =
general, this list should be about items mentioned in the charter. If we =
have comments about companies, their products, or their deployments, it =
would be best if we took those up directly with the networks or vendors =
in question rather than using this forum.=

From brian.e.carpenter@gmail.com  Thu Oct 21 13:23:56 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 427793A6A4E for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 13:23:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.283
X-Spam-Level: 
X-Spam-Status: No, score=-102.283 tagged_above=-999 required=5 tests=[AWL=-0.284, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AbOQKmE4Bl1Z for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 13:23:54 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 16E003A68EE for <v6ops@ietf.org>; Thu, 21 Oct 2010 13:23:53 -0700 (PDT)
Received: by fxm8 with SMTP id 8so18083fxm.31 for <v6ops@ietf.org>; Thu, 21 Oct 2010 13:25:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=uqzkgg6XL5Qf9DPhWCgq+l/3SliAZj8pzTheTRKkp+U=; b=KIWdGnBfz7VxzFI/X5Oy4ArGwvH6V7fguqEdbM9G+TkMQFYhb08Gv/58XzawyomcTv lMRqFo94Tr7HxE0wpjDwMmVSRllcb6r6NG8yJxlOWbQ+/NKHFC7drZdm2N4UszZIVSgm 5lvJm7mZnZVm/GrXpTUPuQydNVviKkb0wjK4w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=Be1x7w61uxlIgOg+4kzPVgpi6lVjySIVPXqZz2UAXiy0KnsRzsPaG4MxvD62j54ydN fk6vXhLCg3BWUEPFzSBLz0ts7EfmPWJ93jgklMShVBYarUhUPWVzCHw9cd/Pm38E/Jh6 2r5pcvWQm1hbKKjF/9goYVcyyGzAxgj6W8yho=
Received: by 10.223.1.144 with SMTP id 16mr27894faf.32.1287692715425; Thu, 21 Oct 2010 13:25:15 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id p2sm1072989fak.46.2010.10.21.13.25.11 (version=SSLv3 cipher=RC4-MD5); Thu, 21 Oct 2010 13:25:14 -0700 (PDT)
Message-ID: <4CC0A1A2.3060003@gmail.com>
Date: Fri, 22 Oct 2010 09:25:06 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
References: <C8E56757.2A817%john_brzozowski@cable.comcast.com>
In-Reply-To: <C8E56757.2A817%john_brzozowski@cable.comcast.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 20:23:56 -0000

On 2010-10-21 20:43, Brzozowski, John wrote:
> On 10/21/10 3:08 AM, "Ole Tr=C3=B8an" <otroan@employees.org> wrote:
>=20
>> John,
>>
>>> What you describe seems reasonable and functional.  The simple fact t=
hat a
>>> functional implementation exists is very positive.
>>>
>>> The only other comment I would offer is why would a shorter prefix be=

>>> offered to an IGD if the device cannot support it?  This leads to a p=
oint
>>> that I think is worth noting related to RFC3633.  It is important tha=
t IGD
>>> hint to the size of IPv6 prefix desired/supported in its DHCPv6 SOLIC=
IT.
>>> From what I have seen very few, if any, IGDs provide a hint in the IA=
_PD.
>>>
>>> Providing the hint does not guarantee that the operator will always h=
onor
>>> the hint.  This, however, is a step in the right direction to ensure =
the IGD
>>> is offered an appropriately sized IPv6 prefix.
>> my assumption is that residential customers get the same address block=
 size
>> independent of what their actual need is.
> [jjmb] at this time I do not share this assumption, I may over time.  I=
 also
> not sure if this a universally accepted assumption.

Absolutely not. It's entirely a matter between the customer and the ISP.
The ISP might choose to offer a one-size-fits-all model or a user-chooses=

(and pays) model. This is emphatically not the IETF's business, beyond
what is said in draft-ietf-v6ops-3177bis-end-sites.

In our protocols, prefix length clearly needs to be a parameter
(as it is in draft-hu-pppext-ipv6cp-extensions, for example).

    Brian

>> if you give every customer a /56, isn't that a simple deployment model=
, where
>> you can do simple aggregation and you don't have to "negotiate" with e=
ach
>> customer for their most suitable address block size, which might even =
change
>> over time...?
> [jjmb] a fixed prefix does not necessarily make for a simpler deploymen=
t
> model.  For a given prefix length range the simplicity or complexity of=

> aggregation will not necessarily change.  In a cable environment, for
> example, the aggregation could occur at the CMTS regardless of prefix
> length.  Fortunately DHCPv6 facilitates negotiation even if needs chang=
e
> over time.  If additional space is needed over time IGDs can request a
> shorter prefix.
>> as more advanced home networks evolve, it is going to be difficult for=
 the
>> border router to know the number of links that exists or may appear in=
 the
>> future. the intention with PD was always that the prefix size was a
>> contractual matter, not one which is negotiated 'real time'.
> [jjmb] Hmmm...RFC3633 is a contract?
>> mind you, I'm not an operator and I would surely like to understand th=
e
>> reasons why doing more negotiation would be useful? of course, one has=
 to
>> expect that every CPE supports a delegation of <=3D/64. are there real=
ly
>> implementations which only supports a single /64? if so, I'd claim tha=
t's a
>> bug and not in line with 3633 nor the basic ipv6 ce router requirement=
s
>> specification.
> [jjmb] having flexibility is a must, making substantial fixed decisions=
 this
> early can result in complications or even limitations.  I absolutely ag=
ree
> with one of your comments above, home networks will evolve.  As such we=
 need
> to ensure we have the ability to accommodate the same over time.  An
> incremental approach supports this goal.  Yes there are implementations=
 that
> only support a /64, nothing shorter largely because they physically do =
not
> have the need and/or ability to support anything else.  If a device has=
 only
> one IPv4 LAN and cannot be upgraded to support more (including hierarch=
ical
> PD) why would this be a bug?  I think we will have to agree to disagree=
, I
> do not view this as a bug.  I do think this is inline with RFC3633 and =
the
> IPv6 CPE router requirements.  A lot of work has been done over the pas=
t
> couple of years to get some existing routers to be software upgradable =
to
> support native IPv6 as such there may be some devices with lesser
> capabilities.  Having a minimal level of support for IPv6 is better tha=
n
> none, right?  Finally, there may be a wide range of routers built over =
time
> that range in caliber and features.
>> cheers,
>> Ole
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> John Jason Brzozowski
> Comcast Cable
> e) mailto:john_brzozowski@cable.comcast.com
> o) 609-377-6594
> m) 484-962-0060
> w) http://www.comcast6.net
> =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
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>=20


From ek@google.com  Thu Oct 21 13:34:54 2010
Return-Path: <ek@google.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A09F3A6838 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 13:34:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.677
X-Spam-Level: 
X-Spam-Status: No, score=-105.677 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KjlEykJHE+d7 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 13:34:51 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by core3.amsl.com (Postfix) with ESMTP id 9E6913A67E1 for <v6ops@ietf.org>; Thu, 21 Oct 2010 13:34:50 -0700 (PDT)
Received: from wpaz13.hot.corp.google.com (wpaz13.hot.corp.google.com [172.24.198.77]) by smtp-out.google.com with ESMTP id o9LKaQHZ005611 for <v6ops@ietf.org>; Thu, 21 Oct 2010 13:36:26 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1287693386; bh=QqVvnCcAYs81LViFjzamUtP+Zd0=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=pZCHnNZlZV297FSe6cyzvs/vy4HX3yflI3mE0fnTkI7YPrVUoUXnlMFGV/lutQ0NU TctLshsmEe3u1DS/zQ1yQ==
Received: from qwi2 (qwi2.prod.google.com [10.241.195.2]) by wpaz13.hot.corp.google.com with ESMTP id o9LKaPPO008242 for <v6ops@ietf.org>; Thu, 21 Oct 2010 13:36:25 -0700
Received: by qwi2 with SMTP id 2so49680qwi.14 for <v6ops@ietf.org>; Thu, 21 Oct 2010 13:36:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=QA07ihw3o4ereKRI7zr/OJ8TQBAAQfDOYrnssPYHe1g=; b=RbiUc/bDLGPeoU4Ibe6cbrS899N6pi0Rg03K7iUwqFWd9OI+gGySPt5TuCEtABMhyb VnRANLmJH1BLi5SfYdrg==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=pPVJT4h2YHXIOjyJqECp5yskLktdl69lG9mY1b1v/MkxmZLhcoWZOF8a8776w6Wthq T1VXfQIltLA5gyVSvTvw==
MIME-Version: 1.0
Received: by 10.229.96.12 with SMTP id f12mr1200531qcn.274.1287693385144; Thu, 21 Oct 2010 13:36:25 -0700 (PDT)
Received: by 10.229.78.228 with HTTP; Thu, 21 Oct 2010 13:36:25 -0700 (PDT)
In-Reply-To: <4C39DDAC-1D14-47B4-88D3-042B4595E58D@apple.com>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr> <4CC01B0C.5020406@inex.ie> <FE1F03BC-EB55-4117-9EF6-A73B38AFD5B4@free.fr> <1EA76BAD7F050648910C041BDDED8CD5013FDBB5@PRDCG4EXVW01-5.OSS.PRD> <E71300B9B9041340B238540990BF04530915AAD92B@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <75632460-4C3A-428A-9601-22E113012786@apple.com> <AANLkTinMC81DScKi3YQ3jnWKe9ufr=6bqG_RGTp0yP28@mail.gmail.com> <4C39DDAC-1D14-47B4-88D3-042B4595E58D@apple.com>
Date: Thu, 21 Oct 2010 13:36:25 -0700
Message-ID: <AANLkTimVFsaNkAGFXwVQWhZUz+NwL-67QYdLvRkFkf1S@mail.gmail.com>
From: Erik Kline <ek@google.com>
To: james woodyatt <jhw@apple.com>
Content-Type: multipart/alternative; boundary=001636832064cd18b60493267ace
X-System-Of-Record: true
Cc: v6ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 20:34:54 -0000

--001636832064cd18b60493267ace
Content-Type: text/plain; charset=UTF-8

On 21 October 2010 11:11, james woodyatt <jhw@apple.com> wrote:

> everyone--
>
> I'm about to start advocating seriously that the Darwin IPv6 stop
> autoconfiguring interface addresses with the 2002::/16 prefix even when the
> Prefix Information Option has the A=1 bit set.  If this draft progresses or
> operators start seriously looking like they're going to deploy 6to4-PMT,
> then I'm pretty sure there won't be any alternative.


At first blush, this sounds like a reasonable idea to me regardless.  Or at
least that may be reasonable default behavior and those who want the feature
can check the "take my life into my own hands" check box.  =)

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

On 21 October 2010 11:11, james woodyatt <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:jhw@apple.com">jhw@apple.com</a>&gt;</span> wrote:<br><div class=3D"g=
mail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex;">
everyone--<br>
<br>
I&#39;m about to start advocating seriously that the Darwin IPv6 stop autoc=
onfiguring interface addresses with the 2002::/16 prefix even when the Pref=
ix Information Option has the A=3D1 bit set. =C2=A0If this draft progresses=
 or operators start seriously looking like they&#39;re going to deploy 6to4=
-PMT, then I&#39;m pretty sure there won&#39;t be any alternative.</blockqu=
ote>
<div><br></div><div>At first blush, this sounds like a reasonable idea to m=
e regardless. =C2=A0Or at least that may be reasonable default behavior and=
 those who want the feature can check the &quot;take my life into my own ha=
nds&quot; check box. =C2=A0=3D)</div>
</div>

--001636832064cd18b60493267ace--

From ot@cisco.com  Thu Oct 21 13:37:14 2010
Return-Path: <ot@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EDD523A686A for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 13:37:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.793
X-Spam-Level: 
X-Spam-Status: No, score=-4.793 tagged_above=-999 required=5 tests=[AWL=-2.794, BAYES_00=-2.599, J_CHICKENPOX_32=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DSd5goAf5LJo for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 13:37:13 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id D68CC3A6845 for <v6ops@ietf.org>; Thu, 21 Oct 2010 13:37:12 -0700 (PDT)
Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYEAMNBwEyQ/khNgWdsb2JhbAChXhUBARYiIqRUnEGFSgSKTQ
X-IronPort-AV: E=Sophos;i="4.58,219,1286150400"; d="scan'208";a="11774840"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 21 Oct 2010 20:38:48 +0000
Received: from ams3-vpn-dhcp6406.cisco.com (ams3-vpn-dhcp6406.cisco.com [10.61.89.5]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id o9LKcmQd023037; Thu, 21 Oct 2010 20:38:48 GMT
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <ot@cisco.com>
In-Reply-To: <4CC0A1A2.3060003@gmail.com>
Date: Thu, 21 Oct 2010 22:38:47 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <11EA1C19-01B2-46B6-A0EE-6CB760F3482E@cisco.com>
References: <C8E56757.2A817%john_brzozowski@cable.comcast.com> <4CC0A1A2.3060003@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>, "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 20:37:14 -0000

Brian,

>>>> Providing the hint does not guarantee that the operator will always =
honor
>>>> the hint.  This, however, is a step in the right direction to =
ensure the IGD
>>>> is offered an appropriately sized IPv6 prefix.
>>> my assumption is that residential customers get the same address =
block size
>>> independent of what their actual need is.
>> [jjmb] at this time I do not share this assumption, I may over time.  =
I also
>> not sure if this a universally accepted assumption.
>=20
> Absolutely not. It's entirely a matter between the customer and the =
ISP.
> The ISP might choose to offer a one-size-fits-all model or a =
user-chooses
> (and pays) model. This is emphatically not the IETF's business, beyond
> what is said in draft-ietf-v6ops-3177bis-end-sites.

certainly, and I didn't imply anything else.
DHCP PD does indeed contain a prefix length, but it is not suitable as a =
protocol to negotiate the size of an address block.

what do you gain from doing dynamic address block size negotiations =
between RR and DR?
as opposed to the customer getting whatever address block size he =
desires when buying the service?

> In our protocols, prefix length clearly needs to be a parameter
> (as it is in draft-hu-pppext-ipv6cp-extensions, for example).

so now we are not only going to replicate all functions between DHCPv6 =
and RA options, but also for IPv6CP? that appears to be a bad idea.

cheers,
Ole=

From brian.e.carpenter@gmail.com  Thu Oct 21 14:02:32 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CFDD23A67F6 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 14:02:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.282
X-Spam-Level: 
X-Spam-Status: No, score=-102.282 tagged_above=-999 required=5 tests=[AWL=-0.283, BAYES_00=-2.599, J_CHICKENPOX_32=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LvlDt2gLqF5B for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 14:02:32 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id D402D3A6847 for <v6ops@ietf.org>; Thu, 21 Oct 2010 14:02:31 -0700 (PDT)
Received: by wwe15 with SMTP id 15so37639wwe.13 for <v6ops@ietf.org>; Thu, 21 Oct 2010 14:04:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=AhV79rwk5N8Sb9q9/AH8KpSZTr9Y7dJE1I25v32m8HA=; b=o0jwaODulyVN+Tp4AJBpwf7ve0hG/OmEg6wPE5QQKayQXzKKBN6fo0sCOOHOXRrut1 4oSr7ks4tYuvifNj8/AMYONxsT4jkyy1ybE763ZWTlMyxj/bfjEQjlrdMyQJFtf34xgr WJHc/tog+hRIkQARckI0koCnqUZYNM06A7puc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=Grh/GljK9Ju6fDvfRv1+0yaSCL1TQRX16GtTJt6XSnRk9oBjIFS3YxQub8UT0ZxcHW G7lBlGXKnmJYT1/ypV44REJB3rJQtCI3xO8rnDs1k62Z1hFmCj/0/peftL3G7w3GHEZZ 1jYwOdVRAzOhpBmqgnw1Tg8h2BBvzgj4Nss2A=
Received: by 10.227.128.201 with SMTP id l9mr1828569wbs.22.1287695047525; Thu, 21 Oct 2010 14:04:07 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id h29sm1733551wbc.9.2010.10.21.14.04.04 (version=SSLv3 cipher=RC4-MD5); Thu, 21 Oct 2010 14:04:06 -0700 (PDT)
Message-ID: <4CC0AABD.6060207@gmail.com>
Date: Fri, 22 Oct 2010 10:03:57 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ole Troan <ot@cisco.com>
References: <C8E56757.2A817%john_brzozowski@cable.comcast.com> <4CC0A1A2.3060003@gmail.com> <11EA1C19-01B2-46B6-A0EE-6CB760F3482E@cisco.com>
In-Reply-To: <11EA1C19-01B2-46B6-A0EE-6CB760F3482E@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 21:02:32 -0000

On 2010-10-22 09:38, Ole Troan wrote:
> Brian,
> 
>>>>> Providing the hint does not guarantee that the operator will always honor
>>>>> the hint.  This, however, is a step in the right direction to ensure the IGD
>>>>> is offered an appropriately sized IPv6 prefix.
>>>> my assumption is that residential customers get the same address block size
>>>> independent of what their actual need is.
>>> [jjmb] at this time I do not share this assumption, I may over time.  I also
>>> not sure if this a universally accepted assumption.
>> Absolutely not. It's entirely a matter between the customer and the ISP.
>> The ISP might choose to offer a one-size-fits-all model or a user-chooses
>> (and pays) model. This is emphatically not the IETF's business, beyond
>> what is said in draft-ietf-v6ops-3177bis-end-sites.
> 
> certainly, and I didn't imply anything else.
> DHCP PD does indeed contain a prefix length, but it is not suitable as a protocol to negotiate the size of an address block.
> 
> what do you gain from doing dynamic address block size negotiations between RR and DR?
> as opposed to the customer getting whatever address block size he desires when buying the service?

I tend to agree, but again, that's not IETF business.

>> In our protocols, prefix length clearly needs to be a parameter
>> (as it is in draft-hu-pppext-ipv6cp-extensions, for example).
> 
> so now we are not only going to replicate all functions between DHCPv6 and RA options, but also for IPv6CP? that appears to be a bad idea.

Well, there are arguments about why this is needed from an operational viewpoint
in draft-hu-pppext-ipv6cp-requirements. I guess they should be discussed
on the pppext list.

     Brian

From root@core3.amsl.com  Thu Oct 21 14:15:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: v6ops@ietf.org
Delivered-To: v6ops@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 1E2243A68F5; Thu, 21 Oct 2010 14:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20101021211502.1E2243A68F5@core3.amsl.com>
Date: Thu, 21 Oct 2010 14:15:02 -0700 (PDT)
Cc: v6ops@ietf.org
Subject: [v6ops] I-D Action:draft-ietf-v6ops-cpe-simple-security-16.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 21:15:02 -0000

--NextPart

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


	Title           : Recommended Simple Security Capabilities in Customer Premises Equipment for Providing Residential IPv6 Internet Service
	Author(s)       : J. Woodyatt
	Filename        : draft-ietf-v6ops-cpe-simple-security-16.txt
	Pages           : 35
	Date            : 2010-10-21

This document identifies a set of recommendations for the makers of
devices describing how to provide for "simple security" capabilities
at the perimeter of local-area IPv6 networks in Internet-enabled
homes and small offices.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-cpe-simple-security-16.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-v6ops-cpe-simple-security-16.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-10-21141304.I-D@ietf.org>


--NextPart--

From john_brzozowski@cable.comcast.com  Thu Oct 21 15:32:33 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 90FD53A6405 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 15:32:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.848
X-Spam-Level: 
X-Spam-Status: No, score=-107.848 tagged_above=-999 required=5 tests=[AWL=0.615, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MAEd10SkjZhL for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 15:32:28 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id A16253A63EC for <v6ops@ietf.org>; Thu, 21 Oct 2010 15:32:27 -0700 (PDT)
Received: from ([24.40.55.42]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.100959660; Thu, 21 Oct 2010 18:34:01 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by PACDCEXHUB01.cable.comcast.com ([fe80::d1e7:20b5:9b63:21a6%12]) with mapi id 14.01.0255.000; Thu, 21 Oct 2010 18:34:01 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: james woodyatt <jhw@apple.com>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
Thread-Index: AQHLb7qA2T6t3TrIl0mUPJfZCE79dZNKB0SAgAA+QwCAAKTAgIAAFYsA///1tYCAAM4qgIAAPPyA
Date: Thu, 21 Oct 2010 22:34:00 +0000
Message-ID: <C8E6381D.2ABE8%john_brzozowski@cable.comcast.com>
In-Reply-To: <82D3A362-1B89-4C22-AB78-E16A036C6A57@apple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F17C89281DF3C14B9B3F6479C23F03FE@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 22:32:33 -0000

On 10/21/10 10:55 AM, "james woodyatt" <jhw@apple.com> wrote:

> On Oct 20, 2010, at 23:37, Brzozowski, John wrote:
>=20
>> The only other comment I would offer is why would a shorter prefix be of=
fered
>> to an IGD if the device cannot support it?
>=20
> An IGD could be upgraded in the field to support it.
[jjmb] this is an important point to note, thanks.
>=20
> Some people consider it a software error (rather than a product developme=
nt
> mistake) that AirPort doesn't currently offer IPv6 service on its guest
> network.  If it did, then it would choose a second subnet identifier.
[jjmb] I consider it a stepping stone.  It is clearly something that is
resolvable.  In the case where a second identifier is used are you thinking
a second independent DHCPv6 request for another IA_PD or a revised DHCPv6
request for a shorter IA_PD?
>=20
>=20
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, communications engineering
>=20
>=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From john_brzozowski@cable.comcast.com  Thu Oct 21 15:39:00 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 37DB23A672E for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 15:39:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.904
X-Spam-Level: 
X-Spam-Status: No, score=-107.904 tagged_above=-999 required=5 tests=[AWL=0.559, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pl14Q5DWRWSF for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 15:38:59 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id E38E33A63EC for <v6ops@ietf.org>; Thu, 21 Oct 2010 15:38:58 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.100961159; Thu, 21 Oct 2010 18:40:32 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by PACDCEXHUB02.cable.comcast.com ([fe80::11d4:f530:37a0:9f4e%12]) with mapi id 14.01.0255.000; Thu, 21 Oct 2010 18:40:32 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: "Brian E. Carpenter" <brian.e.carpenter@gmail.com>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again
Thread-Index: AQHLcV4d775YCTTaj0KZPXL4p8GjopNL/zYA
Date: Thu, 21 Oct 2010 22:40:31 +0000
Message-ID: <C8E639A2.2ABF9%john_brzozowski@cable.comcast.com>
In-Reply-To: <4CC0A1A2.3060003@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <84B0D298EB42DC4FBC2946101CADFABB@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 22:39:00 -0000

Brian,

I agree with you your statements below, we at the IETF deal with protocols
not contracts.

John


On 10/21/10 4:25 PM, "Brian E. Carpenter" <brian.e.carpenter@gmail.com>
wrote:

> Absolutely not. It's entirely a matter between the customer and the ISP.
> The ISP might choose to offer a one-size-fits-all model or a user-chooses
> (and pays) model. This is emphatically not the IETF's business, beyond
> what is said in draft-ietf-v6ops-3177bis-end-sites.
>=20
> In our protocols, prefix length clearly needs to be a parameter
> (as it is in draft-hu-pppext-ipv6cp-extensions, for example).

=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
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From john_brzozowski@cable.comcast.com  Thu Oct 21 15:43:13 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A0C333A6784 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 15:43:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.65
X-Spam-Level: 
X-Spam-Status: No, score=-107.65 tagged_above=-999 required=5 tests=[AWL=0.213, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r80tBv81nR0j for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 15:43:12 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 368DE3A63CA for <v6ops@ietf.org>; Thu, 21 Oct 2010 15:43:12 -0700 (PDT)
Received: from ([24.40.55.42]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.100962167; Thu, 21 Oct 2010 18:44:24 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by PACDCEXHUB01.cable.comcast.com ([fe80::d1e7:20b5:9b63:21a6%12]) with mapi id 14.01.0255.000; Thu, 21 Oct 2010 18:44:24 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: Ole Troan <ot@cisco.com>, "Brian E. Carpenter" <brian.e.carpenter@gmail.com>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again
Thread-Index: ActxcYP/775YCTTaj0KZPXL4p8Gjog==
Date: Thu, 21 Oct 2010 22:44:24 +0000
Message-ID: <C8E63A8B.2AC06%john_brzozowski@cable.comcast.com>
In-Reply-To: <11EA1C19-01B2-46B6-A0EE-6CB760F3482E@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <E78F95AE32D2784483BA4FA31FAA46DB@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 22:43:13 -0000

On 10/21/10 4:38 PM, "Ole Troan" <ot@cisco.com> wrote:

> Brian,
>=20
>>>>> Providing the hint does not guarantee that the operator will always h=
onor
>>>>> the hint.  This, however, is a step in the right direction to ensure =
the
>>>>> IGD
>>>>> is offered an appropriately sized IPv6 prefix.
>>>> my assumption is that residential customers get the same address block=
 size
>>>> independent of what their actual need is.
>>> [jjmb] at this time I do not share this assumption, I may over time.  I=
 also
>>> not sure if this a universally accepted assumption.
>>=20
>> Absolutely not. It's entirely a matter between the customer and the ISP.
>> The ISP might choose to offer a one-size-fits-all model or a user-choose=
s
>> (and pays) model. This is emphatically not the IETF's business, beyond
>> what is said in draft-ietf-v6ops-3177bis-end-sites.
>=20
> certainly, and I didn't imply anything else.
[jjmb] I understood your points differently but must have misunderstood.  I=
t
seemed like there were other implications.
> DHCP PD does indeed contain a prefix length, but it is not suitable as a
> protocol to negotiate the size of an address block.
[jjmb] this is not how I read RFC3633.
>=20
> what do you gain from doing dynamic address block size negotiations betwe=
en RR
> and DR?
[jjmb] not to sound clich=E9, right sizing is achieved.
> as opposed to the customer getting whatever address block size he desires=
 when
> buying the service?
>=20
>> In our protocols, prefix length clearly needs to be a parameter
>> (as it is in draft-hu-pppext-ipv6cp-extensions, for example).
>=20
> so now we are not only going to replicate all functions between DHCPv6 an=
d RA
> options, but also for IPv6CP? that appears to be a bad idea.
[jjmb] what badness are we replicating?  It seems we are ensuring
flexibility instead of fixed constructs.
>=20
> cheers,
> Ole

=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
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From john_brzozowski@cable.comcast.com  Thu Oct 21 15:45:36 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6194F3A63CA for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 15:45:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.667
X-Spam-Level: 
X-Spam-Status: No, score=-107.667 tagged_above=-999 required=5 tests=[AWL=0.197, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vszjOZMgpVuO for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 15:45:35 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 1C7313A67A4 for <v6ops@ietf.org>; Thu, 21 Oct 2010 15:45:35 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.100962936; Thu, 21 Oct 2010 18:46:57 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by PACDCEXHUB02.cable.comcast.com ([fe80::11d4:f530:37a0:9f4e%12]) with mapi id 14.01.0255.000; Thu, 21 Oct 2010 18:46:56 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: "Brian E. Carpenter" <brian.e.carpenter@gmail.com>, Ole Troan <ot@cisco.com>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again
Thread-Index: AQHLcV4d775YCTTaj0KZPXL4p8GjopNMID2AgAAHCID//9m0gA==
Date: Thu, 21 Oct 2010 22:46:55 +0000
Message-ID: <C8E63B1D.2AC11%john_brzozowski@cable.comcast.com>
In-Reply-To: <4CC0AABD.6060207@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <DF2525C9EF3D2F43911A787407E7FF69@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 22:45:36 -0000

On 10/21/10 5:03 PM, "Brian E. Carpenter" <brian.e.carpenter@gmail.com>
wrote:

> On 2010-10-22 09:38, Ole Troan wrote:
>> Brian,
>>=20
>>>>>> Providing the hint does not guarantee that the operator will always =
honor
>>>>>> the hint.  This, however, is a step in the right direction to ensure=
 the
>>>>>> IGD
>>>>>> is offered an appropriately sized IPv6 prefix.
>>>>> my assumption is that residential customers get the same address bloc=
k
>>>>> size
>>>>> independent of what their actual need is.
>>>> [jjmb] at this time I do not share this assumption, I may over time.  =
I
>>>> also
>>>> not sure if this a universally accepted assumption.
>>> Absolutely not. It's entirely a matter between the customer and the ISP=
.
>>> The ISP might choose to offer a one-size-fits-all model or a user-choos=
es
>>> (and pays) model. This is emphatically not the IETF's business, beyond
>>> what is said in draft-ietf-v6ops-3177bis-end-sites.
>>=20
>> certainly, and I didn't imply anything else.
>> DHCP PD does indeed contain a prefix length, but it is not suitable as a
>> protocol to negotiate the size of an address block.
>>=20
>> what do you gain from doing dynamic address block size negotiations betw=
een
>> RR and DR?
>> as opposed to the customer getting whatever address block size he desire=
s
>> when buying the service?
>=20
> I tend to agree, but again, that's not IETF business.
[jjmb] +1
>=20
>>> In our protocols, prefix length clearly needs to be a parameter
>>> (as it is in draft-hu-pppext-ipv6cp-extensions, for example).
>>=20
>> so now we are not only going to replicate all functions between DHCPv6 a=
nd RA
>> options, but also for IPv6CP? that appears to be a bad idea.
>=20
> Well, there are arguments about why this is needed from an operational
> viewpoint
> in draft-hu-pppext-ipv6cp-requirements. I guess they should be discussed
> on the pppext list.
>=20
>      Brian

=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
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From jhw@apple.com  Thu Oct 21 16:59:17 2010
Return-Path: <jhw@apple.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4FB283A67EF for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 16:59:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.228
X-Spam-Level: 
X-Spam-Status: No, score=-106.228 tagged_above=-999 required=5 tests=[AWL=0.371, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MvOqY1Yy1INh for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 16:59:16 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 2AA8A3A659A for <v6ops@ietf.org>; Thu, 21 Oct 2010 16:59:16 -0700 (PDT)
Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out3.apple.com (Postfix) with ESMTP id DC83DB115908 for <v6ops@ietf.org>; Thu, 21 Oct 2010 17:00:52 -0700 (PDT)
X-AuditID: 11807134-b7c05ae000002d5d-c1-4cc0d434ae28
Received: from et.apple.com (et.apple.com [17.151.62.12]) by relay14.apple.com (Apple SCV relay) with SMTP id B2.48.11613.434D0CC4; Thu, 21 Oct 2010 17:00:52 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from il0602f-dhcp196.apple.com (il0602f-dhcp196.apple.com [17.206.50.196]) by et.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LAO00BXK01GZCA0@et.apple.com> for v6ops@ietf.org; Thu, 21 Oct 2010 17:00:52 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <C8E6381D.2ABE8%john_brzozowski@cable.comcast.com>
Date: Thu, 21 Oct 2010 17:00:52 -0700
Message-id: <08DEEF72-2BA4-44AF-B625-5444F52F5CF5@apple.com>
References: <C8E6381D.2ABE8%john_brzozowski@cable.comcast.com>
To: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Oct 2010 23:59:17 -0000

On Oct 21, 2010, at 15:34, Brzozowski, John wrote:
> 
> [jjmb] I consider it a stepping stone.  It is clearly something that is
> resolvable.  In the case where a second identifier is used are you thinking
> a second independent DHCPv6 request for another IA_PD or a revised DHCPv6
> request for a shorter IA_PD?

Whatever is the most expedient way to get enough space for the two separate subnets.  My preference would be that the DHCPv6 client could request one prefix with no length hint and generally expect to get back enough space, i.e. a single prefix with length <= 63.  If the server only gives back a /64, then I'd refuse to turn up IPv6 on the guest network.

If it turns out that I need to request two prefixes to get two /64 delegations, then I suppose I'll have to change the firmware to make it always request two prefixes when the guest network is enabled.

Perhaps, it would be a good idea to do that anyway.  I could request a /48 for the primary local network and a /64 for the guest network.  What do you think?


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



From yiu_lee@cable.comcast.com  Thu Oct 21 17:21:48 2010
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5B51E3A67D0 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 17:21:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.864
X-Spam-Level: 
X-Spam-Status: No, score=-106.864 tagged_above=-999 required=5 tests=[AWL=1.599, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LEV2j2IjWAb7 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 17:21:47 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 542BB3A67E4 for <v6ops@ietf.org>; Thu, 21 Oct 2010 17:21:47 -0700 (PDT)
Received: from ([24.40.55.42]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.100983748; Thu, 21 Oct 2010 20:23:22 -0400
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by PACDCEXHUB01.cable.comcast.com ([fe80::d1e7:20b5:9b63:21a6%12]) with mapi id 14.01.0255.000; Thu, 21 Oct 2010 20:23:22 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: IETF V6OPS WG <v6ops@ietf.org>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
Thread-Index: AQHLb7qAIT/HxWXPnUW6tpRGzzvHc5NKB0SAgAA+QwCAAGGvgIAAWJwAgAA4w4CAAIscgIAAgAQAgAAYRQD//8M4gA==
Date: Fri, 22 Oct 2010 00:23:20 +0000
Message-ID: <C8E65094.1DEF%yiu_lee@cable.comcast.com>
In-Reply-To: <08DEEF72-2BA4-44AF-B625-5444F52F5CF5@apple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.0.0.100825
x-originating-ip: [147.191.125.14]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <46768EFC58A63B419C0232A537C3DF66@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 00:21:48 -0000

>
>Whatever is the most expedient way to get enough space for the two
>separate subnets.  My preference would be that the DHCPv6 client could
>request one prefix with no length hint and generally expect to get back
>enough space, i.e. a single prefix with length <=3D 63.  If the server onl=
y
>gives back a /64, then I'd refuse to turn up IPv6 on the guest network.

[YL] Make sense. =20

>
>If it turns out that I need to request two prefixes to get two /64
>delegations, then I suppose I'll have to change the firmware to make it
>always request two prefixes when the guest network is enabled.
>
>Perhaps, it would be a good idea to do that anyway.  I could request a
>/48 for the primary local network and a /64 for the guest network.  What
>do you think?

>[YL] I don't think why an operator will do that because it will require
>the dhcp server to maintain two different leases. If the 1st IA_PD
>contains a /64, I suspect the server may give the same /64 in the 2nd
>request.


From john_brzozowski@cable.comcast.com  Thu Oct 21 17:31:00 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 11F3A3A67EE for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 17:31:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.981
X-Spam-Level: 
X-Spam-Status: No, score=-107.981 tagged_above=-999 required=5 tests=[AWL=0.482, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TT6FjkBsZ7Qt for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 17:30:56 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 5ACD23A67D9 for <v6ops@ietf.org>; Thu, 21 Oct 2010 17:30:56 -0700 (PDT)
Received: from ([24.40.55.40]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.100985554; Thu, 21 Oct 2010 20:32:29 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by pacdcexhub03.cable.comcast.com ([fe80::d1dd:b302:b617:3755%12]) with mapi id 14.01.0255.000; Thu, 21 Oct 2010 20:32:29 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: james woodyatt <jhw@apple.com>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
Thread-Index: ActxgJ6N2T6t3TrIl0mUPJfZCE79dQ==
Date: Fri, 22 Oct 2010 00:32:28 +0000
Message-ID: <C8E653E2.2AC8E%john_brzozowski@cable.comcast.com>
In-Reply-To: <08DEEF72-2BA4-44AF-B625-5444F52F5CF5@apple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BBC460781EA0A44C86A50316D30EA22A@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 00:31:00 -0000

On 10/21/10 8:00 PM, "james woodyatt" <jhw@apple.com> wrote:

> On Oct 21, 2010, at 15:34, Brzozowski, John wrote:
>>=20
>> [jjmb] I consider it a stepping stone.  It is clearly something that is
>> resolvable.  In the case where a second identifier is used are you think=
ing
>> a second independent DHCPv6 request for another IA_PD or a revised DHCPv=
6
>> request for a shorter IA_PD?
>=20
> Whatever is the most expedient way to get enough space for the two separa=
te
> subnets.  My preference would be that the DHCPv6 client could request one
> prefix with no length hint and generally expect to get back enough space,=
 i.e.
> a single prefix with length <=3D 63.  If the server only gives back a /64=
, then
> I'd refuse to turn up IPv6 on the guest network.
[jjmb] I would recommend using the hint to request a single prefix of
adequate length.  For example an IGD that supports two IPv6 LANs might
request a /63.  I think two independent requests would work however a singl=
e
request would most likely yield a single prefix that can be allocated
accordingly by the IGD instead of two discontiguous prefixes.  I agree that
if the server only gives back a /64 the primary LAN should take precedence.
>=20
> If it turns out that I need to request two prefixes to get two /64
> delegations, then I suppose I'll have to change the firmware to make it a=
lways
> request two prefixes when the guest network is enabled.
[jjmb] this is one option versus what I mention above.
>=20
> Perhaps, it would be a good idea to do that anyway.  I could request a /4=
8 for
> the primary local network and a /64 for the guest network.  What do you t=
hink?
[jjmb] I think an IGD should request what it can support.  I am generally
not an advocate of an IGD requesting space it cannot possibly use.  For an
IGD that support two LANs I am thinking a /63 would minimally be required.
>=20
>=20
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, communications engineering
>=20
>=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From rkoodli@cisco.com  Thu Oct 21 21:03:57 2010
Return-Path: <rkoodli@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E72733A672E for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 21:03:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.677
X-Spam-Level: 
X-Spam-Status: No, score=-108.677 tagged_above=-999 required=5 tests=[AWL=-0.074, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YX27f19gMrA1 for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 21:03:51 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 084333A67FA for <v6ops@ietf.org>; Thu, 21 Oct 2010 21:03:50 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmYFANSpwEytJV2Y/2dsb2JhbACBRJ9KUnGhOJwpgneCUwSEVoV3gwo
X-IronPort-AV: E=Sophos;i="4.58,221,1286150400";  d="scan'208,217";a="173653167"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rtp-iport-2.cisco.com with ESMTP; 22 Oct 2010 04:05:27 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id o9M45Ra0013391;  Fri, 22 Oct 2010 04:05:27 GMT
Received: from xmb-rcd-111.cisco.com ([72.163.62.153]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 21 Oct 2010 23:05:27 -0500
Received: from 10.21.87.199 ([10.21.87.199]) by XMB-RCD-111.cisco.com ([72.163.62.153]) with Microsoft Exchange Server HTTP-DAV ;  Fri, 22 Oct 2010 04:05:26 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Thu, 21 Oct 2010 21:17:48 -0700
From: Rajeev Koodli <rkoodli@cisco.com>
To: <teemu.savolainen@nokia.com>, Fred Baker <fred@cisco.com>, <v6ops@ietf.org>
Message-ID: <C8E65E7C.A1E3%rkoodli@cisco.com>
Thread-Topic: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
Thread-Index: ActopRH/JoCme+MzQXiyJfFN4kSgHQIcAP9gACK/4tk=
In-Reply-To: <18034D4D7FE9AE48BF19AB1B0EF2729F5F0418A89E@NOK-EUMSG-01.mgdnok.nokia.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3370540669_8524549"
X-OriginalArrivalTime: 22 Oct 2010 04:05:27.0015 (UTC) FILETIME=[5BDCA770:01CB719E]
Cc: v6ops-chairs@tools.ietf.org, ron@bonica.org
Subject: Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 04:03:58 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3370540669_8524549
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable


Hi Teemu,

Thanks for your feedback.

On-demand approaches: we had a good discussion already on the matter, and I
have revised the ID based on that discussion. Yes, there are no handsets
doing this, but we left it open for laptops which may do this. If this is
not a possibility at all, it would remain as an option; at this stage, I am
not sure if we should say it is Not an option at all..

DHCPv4 on cellular handsets: again, the statement is not implying that they
will surely implement DHCPv4. May be you can see what=B9s coming in the futur=
e
better than I do, but I am going with the option that already exists in 3GP=
P
standards =AD PCO to defer address allocation and then using DHCPv4. Again,
this may never be done, but it=B9s premature to say it will never be done.
Besides, consider the handsets accessing the EPC via WiFi interface, and no=
t
the cellular interface. Would you say that handsets will not do DHCPv4 over
WiFi as well?

Yes, there are additional considerations, and the ID is not making any
recommendations to use on-demand/DHCPv4.As you point out, the ID is only
pointing out that carriers may consider investigating the on-demand
addressing.
(BTW, on-demand PDN is subject to session inactivity timers, and is not the
same as on-demand IPv4 addressing).

3G always-on: okay, I will add some clarifying text.

Regards,

-Rajeev


On 10/21/10 5:01 AM, "teemu.savolainen@nokia.com"
<teemu.savolainen@nokia.com> wrote:

> Hi,
> =20
> Section 3.1: it is true that IPv4 PDN on-demand and deferred IPv4 address
> allocations are =B3approaches=B2 in theory, but I do not believe their
> applicability in practice. E.g. what is the likelyhood that popular deskt=
op
> OSes would suddenly implement that kind of features (isn=B9t the style usua=
lly
> ask DHCPv4 right at interface up and then renew forever)?
> =20
> Section 3.1: I do not believe cellular handsets will implement DHCPv4 for
> cellular interfaces. Hence I disagree with:=B2this may very well change in =
the
> future release=B2. Cellular handsets have managed without DHCPv4 since the =
dawn
> of packet switched cellular networks. Why on earth they would now start t=
o use
> DHCPv4 on cellular access at the very twilight of IPv4?
> =20
> The =B3additional considerations=B2 is huge, like there is no benefit whatsoe=
ver
> for hosts to do IPv4 on-demand or deferred IPv4 address allocation. Also =
it is
> non-trivial, like whether DHCPv4 should be triggered if application binds
> socket to 127.0.0.1..
> =20
> I also slightly disagree with this:=B2 On the other hand, in the existing 3=
G
> UMTS networks, there is no requirement for an always-on connection=B2. Whil=
e
> there is no such requirement from standards bodies, essentially for many
> devices there is from the end user direction: users want to have
> IM/Skype/email always on. Should be clarified.
> =20
> I seem to agree with the conclusions document draws at the end of section=
 3.1
> (there is nothing wrong in doing investigations of on-demand PDN..J
> =20
> Best regards,
> =20
> Teemu
> =20
>=20
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of=
 ext
> Fred Baker
> Sent: 10. lokakuuta 2010 21:00
> To: IPv6 Operations
> Cc: v6ops-chairs@tools.ietf.org; Ron Bonica
> Subject: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
> =20
>=20
> This is to initiate a two week working group last call of
> draft-ietf-v6ops-v6-in-mobile-networks. Please read it now. If you find n=
its
> (spelling errors, minor suggested wording changes, etc), comment to the
> authors; if you find greater issues, such as disagreeing with a statement=
 or
> finding additional issues that need to be addressed, please post your com=
ments
> to the list.
>=20
> =20
>=20
> We are looking specifically for comments on the importance of the documen=
t as
> well as its content. If you have read the document and believe it to be o=
f
> operational utility, that is also an important comment to make.
>=20
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


--B_3370540669_8524549
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:11pt=
'><BR>
Hi Teemu,<BR>
<BR>
Thanks for your feedback.<BR>
<BR>
On-demand approaches: we had a good discussion already on the matter, and I=
 have revised the ID based on that discussion. Yes, there are no handsets do=
ing this, but we left it open for laptops which may do this. If this is not =
a possibility at all, it would remain as an option; at this stage, I am not =
sure if we should say it is Not an option at all..<BR>
<BR>
DHCPv4 on cellular handsets: again, the statement is not implying that they=
 will surely implement DHCPv4. May be you can see what&#8217;s coming in the=
 future better than I do, but I am going with the option that already exists=
 in 3GPP standards &#8211; PCO to defer address allocation and then using DH=
CPv4. Again, this may never be done, but it&#8217;s premature to say it <I>w=
ill</I> never be done. Besides, consider the handsets accessing the EPC via =
WiFi interface, and not the cellular interface. Would you say that handsets =
will not do DHCPv4 over WiFi as well?<BR>
<BR>
Yes, there are additional considerations, and the ID is not making any reco=
mmendations to use on-demand/DHCPv4.As you point out, the ID is only pointin=
g out that carriers may consider investigating the on-demand addressing.<BR>
(BTW, on-demand PDN is subject to session inactivity timers, and is not the=
 same as on-demand IPv4 addressing).<BR>
<BR>
3G always-on: okay, I will add some clarifying text.<BR>
<BR>
Regards,<BR>
<BR>
-Rajeev<BR>
<BR>
<BR>
On 10/21/10 5:01 AM, &quot;<a href=3D"teemu.savolainen@nokia.com">teemu.savol=
ainen@nokia.com</a>&quot; &lt;<a href=3D"teemu.savolainen@nokia.com">teemu.sav=
olainen@nokia.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><=
SPAN STYLE=3D'font-size:11pt'><FONT COLOR=3D"#1F497D">Hi,<BR>
&nbsp;<BR>
Section 3.1: it is true that IPv4 PDN on-demand and deferred IPv4 address a=
llocations are &#8220;approaches&#8221; in theory, but I do not believe thei=
r applicability in practice. E.g. what is the likelyhood that popular deskto=
p OSes would suddenly implement that kind of features (isn&#8217;t the style=
 usually ask DHCPv4 right at interface up and then renew forever)?<BR>
&nbsp;<BR>
Section 3.1: I do not believe cellular handsets will implement DHCPv4 for c=
ellular interfaces. Hence I disagree with:&#8221;this may very well change i=
n the future release&#8221;. Cellular handsets have managed without DHCPv4 s=
ince the dawn of packet switched cellular networks. Why on earth they would =
now start to use DHCPv4 on cellular access at the very twilight of IPv4? <BR=
>
&nbsp;<BR>
The &#8220;additional considerations&#8221; is huge, like there is no benef=
it whatsoever for hosts to do IPv4 on-demand or deferred IPv4 address alloca=
tion. Also it is non-trivial, like whether DHCPv4 should be triggered if app=
lication binds socket to 127.0.0.1..<BR>
&nbsp;<BR>
I also slightly disagree with this:&#8221; On the other hand, in the existi=
ng 3G UMTS networks, there is no requirement for an always-on connection&#82=
21;. While there is no such requirement from standards bodies, essentially f=
or many devices there is from the end user direction: users want to have IM/=
Skype/email always on. Should be clarified.<BR>
&nbsp;<BR>
I seem to agree with the conclusions document draws at the end of section 3=
.1 (there is nothing wrong in doing investigations of on-demand PDN..</FONT>=
</SPAN></FONT><SPAN STYLE=3D'font-size:11pt'><FONT COLOR=3D"#1F497D"><FONT FACE=3D=
"Wingdings">J<BR>
</FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> <BR>
Best regards,<BR>
&nbsp;<BR>
Teemu<BR>
&nbsp;<BR>
</FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><BR>
</FONT></SPAN><FONT SIZE=3D"2"><FONT FACE=3D"Tahoma, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:10pt'><B>From:</B> <a href=3D"v6ops-bounces@ietf.org">=
v6ops-bounces@ietf.org</a> [<a href=3D"mailto:v6ops-bounces@ietf.org">mailto:v=
6ops-bounces@ietf.org</a>] <B>On Behalf Of </B>ext Fred Baker<BR>
<B>Sent:</B> 10. lokakuuta 2010 21:00<BR>
<B>To:</B> IPv6 Operations<BR>
<B>Cc:</B> <a href=3D"v6ops-chairs@tools.ietf.org">v6ops-chairs@tools.ietf.or=
g</a>; Ron Bonica<BR>
<B>Subject:</B> [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Times New Roman"><SPAN STYLE=3D'font-size:12=
pt'> <BR>
</SPAN></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'=
font-size:11pt'><BR>
</SPAN></FONT><FONT SIZE=3D"1"><FONT FACE=3D"Helvetica, Verdana, Arial"><SPAN S=
TYLE=3D'font-size:9pt'>This is to initiate a two week working group last call =
of draft-ietf-v6ops-v6-in-mobile-networks. Please read it now. If you find n=
its (spelling errors, minor suggested wording changes, etc), comment to the =
authors; if you find greater issues, such as disagreeing with a statement or=
 finding additional issues that need to be addressed, please post your comme=
nts to the list.<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN =
STYLE=3D'font-size:11pt'><BR>
</SPAN></FONT><FONT SIZE=3D"1"><FONT FACE=3D"Helvetica, Verdana, Arial"><SPAN S=
TYLE=3D'font-size:9pt'> <BR>
</SPAN></FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN =
STYLE=3D'font-size:11pt'><BR>
</SPAN></FONT><FONT SIZE=3D"1"><FONT FACE=3D"Helvetica, Verdana, Arial"><SPAN S=
TYLE=3D'font-size:9pt'>We are looking specifically for comments on the importa=
nce of the document as well as its content. If you have read the document an=
d believe it to be of operational utility, that is also an important comment=
 to make.<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN =
STYLE=3D'font-size:11pt'><BR>
<HR ALIGN=3DCENTER SIZE=3D"3" WIDTH=3D"95%"></SPAN></FONT><FONT SIZE=3D"2"><FONT FA=
CE=3D"Consolas, Courier New, Courier"><SPAN STYLE=3D'font-size:10pt'>___________=
____________________________________<BR>
v6ops mailing list<BR>
<a href=3D"v6ops@ietf.org">v6ops@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops">https://www.ietf.org/=
mailman/listinfo/v6ops</a><BR>
</SPAN></FONT></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--B_3370540669_8524549--


From ot@cisco.com  Thu Oct 21 21:31:18 2010
Return-Path: <ot@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1031C3A67EA for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 21:31:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.394
X-Spam-Level: 
X-Spam-Status: No, score=-8.394 tagged_above=-999 required=5 tests=[AWL=1.605,  BAYES_00=-2.599, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3l5IdWDE9twj for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 21:31:15 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 366A93A67FA for <v6ops@ietf.org>; Thu, 21 Oct 2010 21:31:15 -0700 (PDT)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYEAGKwwEyQ/khLgWdsb2JhbAChYBUBARYiIqFEnCKFSgSKTQ
X-IronPort-AV: E=Sophos;i="4.58,221,1286150400"; d="scan'208";a="67257867"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 22 Oct 2010 04:32:51 +0000
Received: from ams3-vpn-dhcp1711.cisco.com (ams3-vpn-dhcp1711.cisco.com [10.61.70.175]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id o9M4WpxJ027804; Fri, 22 Oct 2010 04:32:51 GMT
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <ot@cisco.com>
In-Reply-To: <4CC0AABD.6060207@gmail.com>
Date: Fri, 22 Oct 2010 06:32:50 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <BF19AF42-62D0-4C9E-BDB2-1AC759881879@cisco.com>
References: <C8E56757.2A817%john_brzozowski@cable.comcast.com> <4CC0A1A2.3060003@gmail.com> <11EA1C19-01B2-46B6-A0EE-6CB760F3482E@cisco.com> <4CC0AABD.6060207@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>, "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 04:31:18 -0000

Brian,

>>>>>> Providing the hint does not guarantee that the operator will =
always honor
>>>>>> the hint.  This, however, is a step in the right direction to =
ensure the IGD
>>>>>> is offered an appropriately sized IPv6 prefix.
>>>>> my assumption is that residential customers get the same address =
block size
>>>>> independent of what their actual need is.
>>>> [jjmb] at this time I do not share this assumption, I may over =
time.  I also
>>>> not sure if this a universally accepted assumption.
>>> Absolutely not. It's entirely a matter between the customer and the =
ISP.
>>> The ISP might choose to offer a one-size-fits-all model or a =
user-chooses
>>> (and pays) model. This is emphatically not the IETF's business, =
beyond
>>> what is said in draft-ietf-v6ops-3177bis-end-sites.
>>=20
>> certainly, and I didn't imply anything else.
>> DHCP PD does indeed contain a prefix length, but it is not suitable =
as a protocol to negotiate the size of an address block.
>>=20
>> what do you gain from doing dynamic address block size negotiations =
between RR and DR?
>> as opposed to the customer getting whatever address block size he =
desires when buying the service?
>=20
> I tend to agree, but again, that's not IETF business.

but it is the IETF business how our protocols work.
where in rfc3633 is this behaviour specified?

>>> In our protocols, prefix length clearly needs to be a parameter
>>> (as it is in draft-hu-pppext-ipv6cp-extensions, for example).
>>=20
>> so now we are not only going to replicate all functions between =
DHCPv6 and RA options, but also for IPv6CP? that appears to be a bad =
idea.
>=20
> Well, there are arguments about why this is needed from an operational =
viewpoint
> in draft-hu-pppext-ipv6cp-requirements. I guess they should be =
discussed
> on the pppext list.

so creating two protocols doing exactly the same thing is a good thing?

cheers,
Ole


From remi.despres@free.fr  Thu Oct 21 23:18:22 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 33AD53A685E for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 23:18:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.005
X-Spam-Level: 
X-Spam-Status: No, score=-1.005 tagged_above=-999 required=5 tests=[AWL=0.029,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zE-SAhi4f3nu for <v6ops@core3.amsl.com>; Thu, 21 Oct 2010 23:18:15 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.1]) by core3.amsl.com (Postfix) with ESMTP id 33C6E3A6866 for <v6ops@ietf.org>; Thu, 21 Oct 2010 23:18:03 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2103.sfr.fr (SMTP Server) with ESMTP id B035A7000087; Fri, 22 Oct 2010 08:19:38 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2103.sfr.fr (SMTP Server) with ESMTP id D63BC7000083; Fri, 22 Oct 2010 08:19:37 +0200 (CEST)
X-SFR-UUID: 20101022061937877.D63BC7000083@msfrf2103.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <C8E4858D.1C80%yiu_lee@cable.comcast.com>
Date: Fri, 22 Oct 2010 08:19:36 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0454B2CB-EC15-4612-B152-77BFC50D7C6E@free.fr>
References: <C8E4858D.1C80%yiu_lee@cable.comcast.com>
To: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 06:18:22 -0000

Le 20 oct. 2010 =E0 17:41, Lee, Yiu a =E9crit :

> Hi Remi,
>=20
> I agree that 6rd is a very nice solution. The catch for 6rd is CPE
> upgrade. This isn't easy for some operators which millions of =
unmanaged
> CPEs.

It has always been very clear.
We all agree that one size doesn't fit all!

As you know, that' why some 6a44 should also be useful: to deal with CPE =
cannot be modified (without ignoring that it still needs OS-vendor =
support, and without pretending that it solves ALL problems ;-)).

Note also that I do agree that dual-sack routing with dual-stack CPEs, =
where it can be deployed quickly and at low cost, is the most obvious =
solution.

Regards,
RD
  =20

> Regards,
> Yiu
>=20
>=20
> On 10/20/10 11:30 AM, "R=E9mi Despr=E9s" <remi.despres@free.fr> wrote:
>=20
>> Le 20 oct. 2010 =E0 16:24, Cameron Byrne a =E9crit :
>>=20
>>> ...
>>> ->FUD.  I have 6RD at home (thanks Comcast), ISATAP at work (thanks
>>> MSFT for making this easy) and IPv6-only 3G + NAT64 on my mobile
>>> (thanks T-Mobile USA).  I have IPv6 everywhere, and i have NEVER had
>>> an IPv6 related network issue.  NEVER.  I hear people on Macs
>>> sometimes have issues, i don't have a Mac.  Most people don't have
>>> Macs.
>>=20
>> I have a MAC and I have happily used IPv6 since 2008, with Google and
>> IETF servers in particular.
>>=20
>> In my understanding, IETF has been so far mistaken in its way to =
promote
>> IPv6.
>> By insisting that, to offer IPv6 SERVICE, ISP should first upgrade =
their
>> networks to DUAL-SATCK ROUTING, it has blocked the process.
>>=20
>> One should not ignore that some ISP networks need hardware changes to
>> support dual-stack routing (i.e. time and money).
>>=20
>> But, fortunately, what is needed ASAP is the IPv6 SERVICE (real =
service,
>> i.e. with native addresses, not 6to4 or Teredo addresses which have
>> connectivity problems).
>>=20
>> If the IPV6 SERVICE is offered with DUAL-SATCK ROUTING, very fine, =
but if
>> it is done with 6rd to save time and money, very fine too.
>>=20
>> Regards,
>> RD=20
>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>=20



From remi.despres@free.fr  Fri Oct 22 00:20:08 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6914B3A67DF for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 00:20:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.463
X-Spam-Level: 
X-Spam-Status: No, score=-1.463 tagged_above=-999 required=5 tests=[AWL=0.486,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VmURmiUTRp1H for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 00:20:07 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.3]) by core3.amsl.com (Postfix) with ESMTP id 4E5A03A67A1 for <v6ops@ietf.org>; Fri, 22 Oct 2010 00:20:07 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2112.sfr.fr (SMTP Server) with ESMTP id CE5617000088; Fri, 22 Oct 2010 09:21:43 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2112.sfr.fr (SMTP Server) with ESMTP id 660BF700008B; Fri, 22 Oct 2010 09:21:43 +0200 (CEST)
X-SFR-UUID: 20101022072143418.660BF700008B@msfrf2112.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <4CC07EEA.6000306@gont.com.ar>
Date: Fri, 22 Oct 2010 09:21:41 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <44C27CB3-0633-46E4-A919-6351526D0DFA@free.fr>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr> <4CC07295.8000603@gont.com.ar> <28A6DE3B-3D4D-45DF-98D3-4B7AFE0E6CF1@free.fr> <4CC07EEA.6000306@gont.com.ar>
To: Fernando Gont <fernando@gont.com.ar>
X-Mailer: Apple Mail (2.1081)
Cc: v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4 (ref	draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 07:20:08 -0000

Le 21 oct. 2010 =E0 19:56, Fernando Gont a =E9crit :

> Hi, Remi,
>=20
>>> If Grandma cannot understand the problems you're referring to, the
>>> distinction between IPv4 and IPv6 is probably out of her scope, too.
>>=20
>> Absolutely.
>> Her host, should by default work in IPv6  only if it a native IPv6 =
address.
>> A host that accepts by default to work with 6to4 or Teredo isn't a =
good approach for Grandma.
>=20
> Are you arguing that e.g. Teredo and 6to4 should be disabled by =
default,

Yes.

> or rather that IPv4 should be preferred over IPv6 when the IPv6
> connectivity is provided by Teredo/6to4?

No.

The idea is that Teredo and 6to4, which are useful in some identified =
scenarios but have some lose ends in some others, should be reserved to =
users that know what they do.

Typically, users that don't know how to configure port forwarding in =
their CPEs, only use applications that do work across NAT444.
Avoiding to enable non-native IPv6 (6to4 or Teredo) can protect against =
some connectivity hazards while maintaining their normal user =
experience. =20
Now, when native IPv6 addresses are made available (whatever the tool =
used), they should, without even noticing it, use IPv6 instead of IPv4 =
to reach dual-stack servers. As a result, their consumption of shared =
IPv4 addresses CGNs will automatically decrease, for the good of all.

Regards,
RD=20





>=20
> Thanks,
> --=20
> Fernando Gont
> e-mail: fernando@gont.com.ar || fgont@acm.org
> PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1
>=20
>=20
>=20
>=20



From remi.despres@free.fr  Fri Oct 22 01:20:27 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B0383A67F4 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 01:20:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.166
X-Spam-Level: 
X-Spam-Status: No, score=-1.166 tagged_above=-999 required=5 tests=[AWL=0.183,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t4JQIYP6ALTl for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 01:20:26 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.3]) by core3.amsl.com (Postfix) with ESMTP id 784D93A686C for <v6ops@ietf.org>; Fri, 22 Oct 2010 01:20:25 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2112.sfr.fr (SMTP Server) with ESMTP id 47060700008B; Fri, 22 Oct 2010 10:22:02 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2112.sfr.fr (SMTP Server) with ESMTP id 99875700008C; Fri, 22 Oct 2010 10:22:01 +0200 (CEST)
X-SFR-UUID: 20101022082201628.99875700008C@msfrf2112.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <1EA76BAD7F050648910C041BDDED8CD5013FDBAE@PRDCG4EXVW01-5.OSS.PRD>
Date: Fri, 22 Oct 2010 10:21:59 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <99D2E42C-315C-4916-89DD-943A0AFBB5EA@free.fr>
References: <C8E48A47.102AB%victor.kuarsingh@gmail.com> <81414319-C5A7-430E-9EE8-B9F105401D76@employees.org> <1EA76BAD7F050648910C041BDDED8CD5013FDBAE@PRDCG4EXVW01-5.OSS.PRD>
To: Scott Beuker <Scott.Beuker@sjrb.ca>
X-Mailer: Apple Mail (2.1081)
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 08:20:27 -0000

Hi, Scott,


Le 20 oct. 2010 =E0 21:52, Scott Beuker a =E9crit :

> 6to4-PMT is a good idea, as are more specific 2002::/16 routes, =
because
> both improve upon a solution with flaws (6to4)

The problem I discuss is that it introduces in exchange a new flaw.
And unless I misunderstand, the cure is worse than the disease.

With 6to4-PMT (i.e. NAT66 added to 6to4), peer-to-peer applications will =
NO LONGER work.=20
(They do work today between two 6to4 addresses  that have both good 6to4 =
relays on their way.)


> which will be utilized no
> matter what you say or do.

Each organization obviously makes its own decisions.
Yet, documenting that there is a problem can help to make the best =
decisions.
What I say is only said in view to enlighten the community.


> You can either have the better version, or
> the existing inferior version, your pick.

Exactly.
It's why breaking an "existing interior version" (6to4 in the present =
case) can create bad problems .


> You were lucky enough not to have issues with vendors and hardware =
life
> cycles that prevented you from getting native 6to4 deployed in time?
> Great! Congratulations! I'm happy for you! Unfortunately, not all of =
us
> are that lucky and we have to deal with vendors dragging their feet on
> complete and stable implementations, despite our incessant hounding =
the
> past 2+ years.

Should I make the point again that 6rd and 6a44 are precisely designed =
for native IPv6 address deployments without hardware changes.


> This is sometimes how things go in the real world, and
> that's why we have "Plan C" type measures like 6to4 to temporarily =
plug
> holes and, as such, smooth the transition to IPv6.
>=20
> Blocking these improvements via this draft will not make 6to4 go away.
> I guarantee it.

If you are responsible for choosing deployed solutions somewhere, and if =
you have made your decision, no one, and certainly not me, will block =
you.=20

But if you pollute 6to4 with NAT66, users should know it, and should =
probably prefer Teredo despite its limitations because, at least, it =
doesn't break IPv6 for P2P applications.

Note that it's clear to me that:
- 6to4 between TWO 6to4 addresses (its original purpose) does work =
without problem.
- This will remain true for your customers even after you have added =
NAT66 to your 6to4.=20


To concluse:
- do you claim that 6to4 with NAT66 still permits P2P applications =
between 6to4 and native IPv6 addresses?
(If yes, and if you are right, I will acknowledge my mistake and present =
my apologies.)
- If P2P applications do become impossible between 6to4 and native IPv6, =
do you consider it a minor effect on future user experience?

RD

=20

>=20
> - Scott
>=20
>=20
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops



From remi.despres@free.fr  Fri Oct 22 01:36:58 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1138A3A685B for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 01:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.167
X-Spam-Level: 
X-Spam-Status: No, score=-1.167 tagged_above=-999 required=5 tests=[AWL=0.182,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RBJfvs2qkz1j for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 01:36:48 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.3]) by core3.amsl.com (Postfix) with ESMTP id 5CBE83A6887 for <v6ops@ietf.org>; Fri, 22 Oct 2010 01:36:46 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2112.sfr.fr (SMTP Server) with ESMTP id 7F01D7000091; Fri, 22 Oct 2010 10:38:23 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2112.sfr.fr (SMTP Server) with ESMTP id 4BA6D7000084; Fri, 22 Oct 2010 10:38:23 +0200 (CEST)
X-SFR-UUID: 20101022083823309.4BA6D7000084@msfrf2112.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <4C39DDAC-1D14-47B4-88D3-042B4595E58D@apple.com>
Date: Fri, 22 Oct 2010 10:38:21 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <4F1F8A74-3CB1-483D-BB1B-611E586FA69F@free.fr>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr> <4CC01B0C.5020406@inex.ie> <FE1F03BC-EB55-4117-9EF6-A73B38AFD5B4@free.fr> <1EA76BAD7F050648910C041BDDED8CD5013FDBB5@PRDCG4EXVW01-5.OSS.PRD> <E71300B9B9041340B238540990BF04530915AAD92B@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <75632460-4C3A-428A-9601-22E113012786@apple.com> <AANLkTinMC81DScKi3YQ3jnWKe9ufr=6bqG_RGTp0yP28@mail.gmail.com> <4C39DDAC-1D14-47B4-88D3-042B4595E58D@apple.com>
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.1081)
Cc: v6ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 08:36:58 -0000

Le 21 oct. 2010 =E0 20:11, james woodyatt a =E9crit :

> everyone--
>=20
> I'm about to start advocating seriously that the Darwin IPv6 stop =
autoconfiguring interface addresses with the 2002::/16 prefix even when =
the Prefix Information Option has the A=3D1 bit set.  If this draft =
progresses or operators start seriously looking like they're going to =
deploy 6to4-PMT, then I'm pretty sure there won't be any alternative.

Full agreement.
By adding NAT66 to 6to4, those who believe that they will improve 6to4 =
By adding NAT66 to it, may very well just kill it.

RD
>=20
>=20
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, communications engineering
>=20
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops



From remi.despres@free.fr  Fri Oct 22 01:43:41 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 312EB3A6891 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 01:43:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.168
X-Spam-Level: 
X-Spam-Status: No, score=-1.168 tagged_above=-999 required=5 tests=[AWL=0.181,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iym9KP+3v4+J for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 01:43:40 -0700 (PDT)
Received: from smtp21.services.sfr.fr (smtp21.services.sfr.fr [93.17.128.3]) by core3.amsl.com (Postfix) with ESMTP id 4753B3A6800 for <v6ops@ietf.org>; Fri, 22 Oct 2010 01:43:40 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2112.sfr.fr (SMTP Server) with ESMTP id 6B9E5700009E; Fri, 22 Oct 2010 10:45:17 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2112.sfr.fr (SMTP Server) with ESMTP id 23B6E700009F; Fri, 22 Oct 2010 10:45:17 +0200 (CEST)
X-SFR-UUID: 20101022084517146.23B6E700009F@msfrf2112.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <AANLkTimVFsaNkAGFXwVQWhZUz+NwL-67QYdLvRkFkf1S@mail.gmail.com>
Date: Fri, 22 Oct 2010 10:45:15 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <5393786A-C348-4B67-8F6D-E1979761AD43@free.fr>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr> <4CC01B0C.5020406@inex.ie> <FE1F03BC-EB55-4117-9EF6-A73B38AFD5B4@free.fr> <1EA76BAD7F050648910C041BDDED8CD5013FDBB5@PRDCG4EXVW01-5.OSS.PRD> <E71300B9B9041340B238540990BF04530915AAD92B@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM> <75632460-4C3A-428A-9601-22E113012786@apple.com> <AANLkTinMC81DScKi3YQ3jnWKe9ufr=6bqG_RGTp0yP28@mail.gmail.com> <4C39DDAC-1D14-47B4-88D3-042B4595E58D@apple.com> <AANLkTimVFsaNkAGFXwVQWhZUz+NwL-67QYdLvRkFkf1S@mail.gmail.com>
To: Erik Kline <ek@google.com>
X-Mailer: Apple Mail (2.1081)
Cc: v6ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 08:43:41 -0000

Le 21 oct. 2010 =E0 22:36, Erik Kline a =E9crit :

> On 21 October 2010 11:11, james woodyatt <jhw@apple.com> wrote:
> everyone--
>=20
> I'm about to start advocating seriously that the Darwin IPv6 stop =
autoconfiguring interface addresses with the 2002::/16 prefix even when =
the Prefix Information Option has the A=3D1 bit set.  If this draft =
progresses or operators start seriously looking like they're going to =
deploy 6to4-PMT, then I'm pretty sure there won't be any alternative.
>=20
> At first blush, this sounds like a reasonable idea to me regardless.  =
Or at least that may be reasonable default behavior and those who want =
the feature can check the "take my life into my own hands" check box.

An intermediate stand (as long as 6to4-PMT doesn't come to break 6to4), =
is that router CPEs do propagate 6to4 prefixes, but that, *by default* =
hosts have IPv6 enabled ONLY IF they have native IPv6 addresses.
=20

>  =3D)
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops



From gert@space.net  Fri Oct 22 01:49:50 2010
Return-Path: <gert@space.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F2A563A689E for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 01:49:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.256
X-Spam-Level: 
X-Spam-Status: No, score=-2.256 tagged_above=-999 required=5 tests=[AWL=-0.257, BAYES_00=-2.599, J_CHICKENPOX_37=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U+wpCWT8h8l5 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 01:49:49 -0700 (PDT)
Received: from mobil.space.net (mobil.Space.Net [IPv6:2001:608:2:81::2]) by core3.amsl.com (Postfix) with ESMTP id 096AF3A6840 for <v6ops@ietf.org>; Fri, 22 Oct 2010 01:49:47 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id 030E1F84AB for <v6ops@ietf.org>; Fri, 22 Oct 2010 10:51:23 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 8D724F84D0 for <v6ops@ietf.org>; Fri, 22 Oct 2010 10:50:25 +0200 (CEST)
Received: (qmail 62606 invoked by uid 1007); 22 Oct 2010 10:50:25 +0200
Date: Fri, 22 Oct 2010 10:50:25 +0200
From: Gert Doering <gert@space.net>
To: james woodyatt <jhw@apple.com>
Message-ID: <20101022085025.GM32268@Space.Net>
References: <C8E6381D.2ABE8%john_brzozowski@cable.comcast.com> <08DEEF72-2BA4-44AF-B625-5444F52F5CF5@apple.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <08DEEF72-2BA4-44AF-B625-5444F52F5CF5@apple.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: IETF V6OPS WG <v6ops@ietf.org>, "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 08:49:50 -0000

Hi,

On Thu, Oct 21, 2010 at 05:00:52PM -0700, james woodyatt wrote:
> Perhaps, it would be a good idea to do that anyway.  I could request 
> a /48 for the primary local network and a /64 for the guest network.  
> What do you think?

It would break the deployment model we're envisioning for our DSL customers
- they get *one* prefix of sufficient size, and the prefix is statically 
provisioned in the radius server.

So you'd get the /48 (or /56), and nothing for the second request.

Also, even if it would be all allocate dynamically, it would double the
internal routes on the provider side, which might or might not cause 
extra problems...

So if I'm asked, I'd say "try to get a reasonably-sized prefix, use one
/64 from it for LAN+private network and another /64 for the guest network"

(btw, I'm quite happy to see this functionality emerge - and hope my older
Airport Extreme will eventually get a firmware upgrade to make use of 
it :) )

Gert Doering
        -- NetMaster
-- 
did you enable IPv6 on something today...?

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

From wwwrun@core3.amsl.com  Fri Oct 22 06:54:09 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: v6ops@ietf.org
Delivered-To: v6ops@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 11E1328C0E8; Fri, 22 Oct 2010 06:54:08 -0700 (PDT)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20101022135409.11E1328C0E8@core3.amsl.com>
Date: Fri, 22 Oct 2010 06:54:09 -0700 (PDT)
Cc: v6ops mailing list <v6ops@ietf.org>, Internet Architecture Board <iab@iab.org>, v6ops chair <v6ops-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [v6ops] Document Action: 'Recommended Simple Security Capabilities in Customer Premises Equipment for Providing Residential IPv6 Internet Service' to Informational RFC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 13:54:09 -0000

The IESG has approved the following document:

- 'Recommended Simple Security Capabilities in Customer Premises 
   Equipment for Providing Residential IPv6 Internet Service '
   <draft-ietf-v6ops-cpe-simple-security-16.txt> as an Informational RFC


This document is the product of the IPv6 Operations Working Group. 

The IESG contact persons are Ron Bonica and Dan Romascanu.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-cpe-simple-security-16.txt

Technical Summary
 
This document identifies a set of recommendations for the makers of
devices describing how to provide for "simple security" capabilities
at the perimeter of local-area IPv6 networks in Internet-enabled
homes and small offices.
 
Working Group Summary
 
The working group was divided on the concept of defining or recommending
the use of firewalls; as a result, this document is very explicitly a set
of recommendations for those that would choose to build or deploy a
firewall without making any recommendation on whether anyone should do
either. It describes a simple stateful firewall, permeable to traffic that
is secured using IPsec.
 
Document Quality
 
There is at least one deployed implementation of this firewall, and
expected to be others. The document clearly specifies a consensus set of
recommendations for such firewalls.

Personel

Fred Baker is shepherd.

RFC Editor Note

OLD TEXT:

REC-13: 

By DEFAULT, Internet gateways SHOULD, automatically download
and install software updates for extending IPv6 simple security for
support of future standard upper layer transports and extension
headers.

NEW TEXT:

REC-13:
Residential Internet Gateways SHOULD provide a convenient means to 
securely update their firmware, for the installation of security 
patches and other manufacturer-recommended changes.
 
Vendors can expect users and operators to have differing viewpoints 
on the maintenance of patches, with some preferring automated update 
and some preferring manual initiation, and those preferring automated 
update wanting to download from a vendor site or one managed by the 
network operator. To handle the disparity, vendors are well advised 
if they provide manual and automated options. In the automated case, 
they would do well to facilitate pre-configuration of the download 
URL and a means of validating the software image such as a certificate.


From prvs=904190e80=Scott.Beuker@sjrb.ca  Fri Oct 22 07:07:24 2010
Return-Path: <prvs=904190e80=Scott.Beuker@sjrb.ca>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 01BEA3A692C for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 07:07:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.412
X-Spam-Level: 
X-Spam-Status: No, score=-2.412 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QKLGc9gKEvA5 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 07:07:23 -0700 (PDT)
Received: from prdcg4ipta01x-ext.shaw.ca (prdcg4ipta01x-ext.shaw.ca [204.209.208.146]) by core3.amsl.com (Postfix) with ESMTP id 042FD3A692A for <v6ops@ietf.org>; Fri, 22 Oct 2010 07:07:22 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.58,223,1286172000"; d="scan'208";a="45186652"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 22 Oct 2010 08:08:38 -0600
Message-ID: <1EA76BAD7F050648910C041BDDED8CD5013FDBD0@PRDCG4EXVW01-5.OSS.PRD>
In-Reply-To: <99D2E42C-315C-4916-89DD-943A0AFBB5EA@free.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: Actxwimq6J/FqyeiTk2106/WYH9FFgALaavQ
References: <C8E48A47.102AB%victor.kuarsingh@gmail.com> <81414319-C5A7-430E-9EE8-B9F105401D76@employees.org> <1EA76BAD7F050648910C041BDDED8CD5013FDBAE@PRDCG4EXVW01-5.OSS.PRD> <99D2E42C-315C-4916-89DD-943A0AFBB5EA@free.fr>
From: "Scott Beuker" <Scott.Beuker@sjrb.ca>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
X-OriginalArrivalTime: 22 Oct 2010 14:09:00.0203 (UTC) FILETIME=[AC9A9FB0:01CB71F2]
X-TM-AS-Product-Ver: SMEX-8.0.0.1285-6.500.1024-17718.006
X-TM-AS-Result: No--11.404800-0.000000-31
X-TM-AS-User-Approved-Sender: Yes
X-TM-AS-User-Blocked-Sender: No
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 14:07:24 -0000

Remi,

I'm taking the liberty of just skipping to the key points as I have =
limited time:

> To concluse:
> - do you claim that 6to4 with NAT66 still permits P2P applications
> between 6to4 and native IPv6 addresses?
> (If yes, and if you are right, I will acknowledge my mistake and =
present
> my apologies.)

No, you are correct, but the trade off is thus: with 6to4-PMT a network =
operator can "guarantee" (as best is possible on the Internet) =
reachability to IPv6-only web sites. With regular 6to4, return traffic =
may have to pass through a third party network and service, who may be =
doing anything up to and including dropping it.

Now, comparing those two things to determine which is more desirable is =
debatable, but I want the network operator to be able to make that =
decision for themselves.

> - If P2P applications do become impossible between 6to4 and native =
IPv6,
> do you consider it a minor effect on future user experience?

Personally, looking at the user who will be utilizing 6to4, I see =
someone for whom ensuring basic IPv6-only content accessibility is more =
important. This user is likely unaware they're using 6to4, and simply =
want to be able to look up recipes for cookies or check their email. =
Even if they do dabble in P2P, i.e. torrents, they won't notice the =
missing IPv6 peers.

On the other hand, anyone savvy enough to notice will be more willing to =
buy a home gateway device that supports 6RD or native IPv6, depending on =
where we're at with deployment in their area. In fact this can be =
leveraged to motivate them to toss the old gateway and get one with =
proper IPv6 support.

The bottom line is that it's a tool in the toolbox I would like to have. =
The fact is, while I defend it as a viable option in certain =
circumstances, that doesn't necessarily mean I would end up deploying =
it. If all goes well, we'll never have to, and I continue to strive for =
that.

Thanks,
Scott=20


From victor.kuarsingh@gmail.com  Fri Oct 22 07:11:57 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 705D828C111 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 07:11:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.857
X-Spam-Level: 
X-Spam-Status: No, score=-0.857 tagged_above=-999 required=5 tests=[AWL=0.843,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24qu4t9Qm68p for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 07:11:53 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id C8CA528C102 for <v6ops@ietf.org>; Fri, 22 Oct 2010 07:11:52 -0700 (PDT)
Received: by eyd10 with SMTP id 10so394356eyd.31 for <v6ops@ietf.org>; Fri, 22 Oct 2010 07:13:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=RTJ6D0mJdVUAJRZU8frX0vf7qgsCNKa2tngt9HwWFIU=; b=ZDfge+zWU82yzB5MdZi8wYFKwhxdPJPKf8iLvjhfi3yjbZfp3cI8mCpS0Is6TVnkNd k49jO6p+0pW1eRkw0NQzUDMQbiWm5Tyay+k49gvmQ7KkSVJsXUHHykU+k66c4uo0+6eE /BAi3LbR77UcxcG1OmX6KkaJTvhS5jMswvAis=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=CyM1Uk6LYvGn9dUqTpg1pCvyaxtie9mPIYvvR2DMbY+5q9sv1bptPx74rM7vZvPKop 7voDZWAAQboPTVxwwY78aS3gJPHkYpKbGMezrUi+tjnzunTdkaM0rODAObMrpNPDXMa/ vCA9rfr8N39vNj2xvfsDs3IgiXFUmRGb8vwMI=
Received: by 10.216.70.200 with SMTP id p50mr2618190wed.54.1287756809802; Fri, 22 Oct 2010 07:13:29 -0700 (PDT)
Received: from [10.16.56.120] (surf99.net.rss.rogers.com [24.114.255.99]) by mx.google.com with ESMTPS id e12sm1941827wer.36.2010.10.22.07.13.26 (version=SSLv3 cipher=RC4-MD5); Fri, 22 Oct 2010 07:13:29 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Fri, 22 Oct 2010 10:13:17 -0400
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: Scott Beuker <Scott.Beuker@sjrb.ca>, =?ISO-8859-1?B?UultaQ==?= =?ISO-8859-1?B?IERlc3By6XM=?= <remi.despres@free.fr>
Message-ID: <C8E7143D.1051F%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: Actxwimq6J/FqyeiTk2106/WYH9FFgALaavQAADdVQY=
In-Reply-To: <1EA76BAD7F050648910C041BDDED8CD5013FDBD0@PRDCG4EXVW01-5.OSS.PRD>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 14:11:57 -0000

Group,

May I propose an option here to help us understand the benefits and/or
confirmed drawbacks of PMT operation.

I can conduct a test within a live production network (limited scope/time)
and we can understand and verify how this would perform.

Would the group be open to this approach?  WE can have this coded on single
Linux platform (with 6to4) using the PF functions supporting IPv6 (as I have
been informed).

This is just a thought.

Regards,

Victor


On 22/10/10 10:08 AM, "Scott Beuker" <Scott.Beuker@sjrb.ca> wrote:

> Remi,
> 
> I'm taking the liberty of just skipping to the key points as I have limited
> time:
> 
>> To concluse:
>> - do you claim that 6to4 with NAT66 still permits P2P applications
>> between 6to4 and native IPv6 addresses?
>> (If yes, and if you are right, I will acknowledge my mistake and present
>> my apologies.)
> 
> No, you are correct, but the trade off is thus: with 6to4-PMT a network
> operator can "guarantee" (as best is possible on the Internet) reachability to
> IPv6-only web sites. With regular 6to4, return traffic may have to pass
> through a third party network and service, who may be doing anything up to and
> including dropping it.
> 
> Now, comparing those two things to determine which is more desirable is
> debatable, but I want the network operator to be able to make that decision
> for themselves.
> 
>> - If P2P applications do become impossible between 6to4 and native IPv6,
>> do you consider it a minor effect on future user experience?
> 
> Personally, looking at the user who will be utilizing 6to4, I see someone for
> whom ensuring basic IPv6-only content accessibility is more important. This
> user is likely unaware they're using 6to4, and simply want to be able to look
> up recipes for cookies or check their email. Even if they do dabble in P2P,
> i.e. torrents, they won't notice the missing IPv6 peers.
> 
> On the other hand, anyone savvy enough to notice will be more willing to buy a
> home gateway device that supports 6RD or native IPv6, depending on where we're
> at with deployment in their area. In fact this can be leveraged to motivate
> them to toss the old gateway and get one with proper IPv6 support.
> 
> The bottom line is that it's a tool in the toolbox I would like to have. The
> fact is, while I defend it as a viable option in certain circumstances, that
> doesn't necessarily mean I would end up deploying it. If all goes well, we'll
> never have to, and I continue to strive for that.
> 
> Thanks,
> Scott 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops



From prvs=904190e80=Scott.Beuker@sjrb.ca  Fri Oct 22 07:34:37 2010
Return-Path: <prvs=904190e80=Scott.Beuker@sjrb.ca>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8363528C0DD for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 07:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.389
X-Spam-Level: 
X-Spam-Status: No, score=-2.389 tagged_above=-999 required=5 tests=[AWL=-0.090, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bY+I6djuP89Y for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 07:34:36 -0700 (PDT)
Received: from prdcg4ipta02x-ext.shaw.ca (prdcg4ipta02x-ext.shaw.ca [204.209.208.147]) by core3.amsl.com (Postfix) with ESMTP id 12E2628C102 for <v6ops@ietf.org>; Fri, 22 Oct 2010 07:34:26 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.58,223,1286172000"; d="scan'208";a="155269736"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 22 Oct 2010 08:35:37 -0600
Message-ID: <1EA76BAD7F050648910C041BDDED8CD5013FDBD1@PRDCG4EXVW01-5.OSS.PRD>
In-Reply-To: <44C27CB3-0633-46E4-A919-6351526D0DFA@free.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops] Reasons not to endorse NAT66/6to4(ref	draft-kuarsingh-v6ops-provider-managed-tunnel-00)
Thread-Index: Actxub4JKfZKImL8SgKUA9RUQE1BpQAO09PQ
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr><4CC07295.8000603@gont.com.ar><28A6DE3B-3D4D-45DF-98D3-4B7AFE0E6CF1@free.fr><4CC07EEA.6000306@gont.com.ar> <44C27CB3-0633-46E4-A919-6351526D0DFA@free.fr>
From: "Scott Beuker" <Scott.Beuker@sjrb.ca>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
X-OriginalArrivalTime: 22 Oct 2010 14:35:38.0280 (UTC) FILETIME=[6521D280:01CB71F6]
X-TM-AS-Product-Ver: SMEX-8.0.0.1285-6.500.1024-17718.007
X-TM-AS-Result: No--5.613400-0.000000-31
X-TM-AS-User-Approved-Sender: Yes
X-TM-AS-User-Blocked-Sender: No
Cc: v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref	draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 14:34:37 -0000

> The idea is that Teredo and 6to4, which are useful in some identified
> scenarios but have some lose ends in some others, should be reserved =
to
> users that know what they do.


Exactly the opposite, in my opinion. If you ask the creators of Teredo =
and 6to4, I think they'll tell you it's intended to catch the users who =
know nothing of IPv6, and allow the rest of us who do to proceed with =
the transition to IPv6, without having them hold us back.

Regardless, as it is this is how it can be leveraged, and it will be for =
the best of the IPv6 transition effort if it is.

- Scott

From remi.despres@free.fr  Fri Oct 22 07:47:43 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 759843A67DF for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 07:47:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.169
X-Spam-Level: 
X-Spam-Status: No, score=-1.169 tagged_above=-999 required=5 tests=[AWL=0.180,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nhFAkph-quDg for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 07:47:42 -0700 (PDT)
Received: from smtp22.services.sfr.fr (smtp22.services.sfr.fr [93.17.128.13]) by core3.amsl.com (Postfix) with ESMTP id 0DA4B3A6888 for <v6ops@ietf.org>; Fri, 22 Oct 2010 07:47:42 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2217.sfr.fr (SMTP Server) with ESMTP id E730F7000081; Fri, 22 Oct 2010 16:49:18 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2217.sfr.fr (SMTP Server) with ESMTP id A34617000087; Fri, 22 Oct 2010 16:49:17 +0200 (CEST)
X-SFR-UUID: 20101022144917668.A34617000087@msfrf2217.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <C8E47F9D.1C72%yiu_lee@cable.comcast.com>
Date: Fri, 22 Oct 2010 16:49:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D8420EFB-E8F1-490E-8419-C6829B8A5E26@free.fr>
References: <C8E47F9D.1C72%yiu_lee@cable.comcast.com>
To: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>, "draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org" <draft-kuarsingh-v6ops-6to4-provider-managed-tunnel@tools.ietf.org>, "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>, Victor Kuarsingh <victor.kuarsingh@rci.rogers.com>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 14:47:43 -0000

Le 20 oct. 2010 =E0 17:34, Lee, Yiu a =E9crit :

> Hi Remi,
>=20
> Three points:=20
>=20
> (1) This is a 00 draft. We would like to hear more from the group and =
put
> the updates in 01.
>=20
> (2) For the e2e transparency, this only affects those who rely on the
> external initiated connections (like web-server, ssh-server, etc). We
> assume most 6to4 users don't rely on e2e transparency.

How would SIP, Skype, games, etc., work in IPv6 with 6to4-PMT isn't =
clear to me.
Don't they require referrals?=20

> (3) Some small population will like to have e2e transparency on 6to4. =
We
> want to find a more automatic way to enable them to bypass the =
6to4-PMT.
> Worst case it may require manual opt-out. This is still under =
discussion.

Opt in would be better IMHO, so that referrals still work by default.

Cheers,
RD



>=20
> Thanks,
> Yiu
>=20
>=20
> On 10/20/10 11:08 AM, "Victor Kuarsingh" <victor.kuarsingh@gmail.com>
> wrote:
>=20
>> Remi,
>>=20
>> Yes, the e2e transparency loss is of consideration (subject to =
further
>> test
>> on impact).
>>=20
>> In our testing we found that most in the wild equipment which turns =
on
>> 6to4
>> sets the SLA-ID to "0".  Therefore the opt-in is not doing anything =
(6to4
>> has just turned itself on automatically).
>>=20
>> The opt-out would be setting the SLA-ID to anything by "0" or perhaps =
"1"
>> (since 1 is found as the SLA-ID on a few other defaults).
>>=20
>> This is only targeted at people of have default settings on their
>> equipment
>> and no knowledge of IPv4, IPv6 etc.
>>=20
>> In the use case where a provider may have turned on NAT44/LSN =
(NAT444) and
>> used public IP space (which now breaks auto 6to4), the loss of e2e =
may not
>> be as bad as broken 6to4.
>>=20
>> Again, I would like to stress, this is just an option to complete the
>> whole
>> strategy (which is put out IPv6).
>>=20
>> Victor
>>=20
>>=20
>> On 20/10/10 1:20 AM, "R=E9mi Despr=E9s" <remi.despres@free.fr> wrote:
>>=20
>>>=20
>>> Le 20 oct. 2010 =E0 05:23, Lee, Yiu a =E9crit :
>>>=20
>>>=20
>>>> ... However, using this technique can improve the customer =
experience
>>>> day
>>>> one.
>>>=20
>>> To some extent, it might (and, from a strictly technical point of =
view,
>>> the
>>> idea is neat), but:
>>> - Providers that would support it would, for their customers, BREAK =
the
>>> e2e
>>> transparency (that IPv6 has so far restored in the Internet, and =
that
>>> is IMHO
>>> a great progress not to be lost).
>>> - Unless I misunderstand, the draft doesn't completely describe what
>>> happens
>>> to 6to4 addresses that have non 0 SLA-ID after their embedded IPv4
>>> addresses.
>>> - The requirement of a Customer opt-out introduces significant
>>> complexity.
>>>=20
>>> Regards,
>>> RD
>>>=20
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>=20
>>=20
>=20



From nick@inex.ie  Fri Oct 22 08:56:35 2010
Return-Path: <nick@inex.ie>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C42843A6814 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 08:56:35 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CVpeAP8v0CVM for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 08:56:34 -0700 (PDT)
Received: from mail.acquirer.com (unknown [IPv6:2001:1bb8:2004:150::2]) by core3.amsl.com (Postfix) with ESMTP id 3C8853A67B1 for <v6ops@ietf.org>; Fri, 22 Oct 2010 08:56:33 -0700 (PDT)
X-Envelope-To: <v6ops@ietf.org>
Received: from crumpet.foobar.org (crumpet.foobar.org [10.230.100.249]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.3) with ESMTP id o9MFvxdP046123 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <v6ops@ietf.org>; Fri, 22 Oct 2010 16:58:05 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <4CC1B487.7090702@inex.ie>
Date: Fri, 22 Oct 2010 16:57:59 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.1.14) Gecko/20101005 Thunderbird/3.0.9
MIME-Version: 1.0
To: v6ops@ietf.org
References: <C8E7143D.1051F%victor.kuarsingh@gmail.com>
In-Reply-To: <C8E7143D.1051F%victor.kuarsingh@gmail.com>
X-Enigmail-Version: 1.0.1
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [v6ops] I-DAction:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 15:56:36 -0000

On 22/10/2010 15:13, Victor Kuarsingh wrote:
> I can conduct a test within a live production network (limited scope/time)
> and we can understand and verify how this would perform.
> 
> Would the group be open to this approach?  WE can have this coded on single
> Linux platform (with 6to4) using the PF functions supporting IPv6 (as I have
> been informed).

I think this is a first class idea.  Even if we don't have rough consensus,
running code would be a great start.

Nick

From remi.despres@free.fr  Fri Oct 22 08:59:54 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF8D43A68D1 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 08:59:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.471
X-Spam-Level: 
X-Spam-Status: No, score=-1.471 tagged_above=-999 required=5 tests=[AWL=0.478,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rZBnM6lrTDc4 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 08:59:53 -0700 (PDT)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.81]) by core3.amsl.com (Postfix) with ESMTP id 668363A67B1 for <v6ops@ietf.org>; Fri, 22 Oct 2010 08:59:53 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2421.sfr.fr (SMTP Server) with ESMTP id C5F3B700008D; Fri, 22 Oct 2010 18:01:30 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2421.sfr.fr (SMTP Server) with ESMTP id 57EDF700008C; Fri, 22 Oct 2010 18:01:30 +0200 (CEST)
X-SFR-UUID: 20101022160130360.57EDF700008C@msfrf2421.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <1EA76BAD7F050648910C041BDDED8CD5013FDBD1@PRDCG4EXVW01-5.OSS.PRD>
Date: Fri, 22 Oct 2010 18:01:30 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D0FD94C-892C-47C9-BAFC-BD8DA6B48C9E@free.fr>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr><4CC07295.8000603@gont.com.ar><28A6DE3B-3D4D-45DF-98D3-4B7AFE0E6CF1@free.fr><4CC07EEA.6000306@gont.com.ar> <44C27CB3-0633-46E4-A919-6351526D0DFA@free.fr> <1EA76BAD7F050648910C041BDDED8CD5013FDBD1@PRDCG4EXVW01-5.OSS.PRD>
To: "Scott Beuker" <Scott.Beuker@sjrb.ca>
X-Mailer: Apple Mail (2.1081)
Cc: v6ops v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref	draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 15:59:54 -0000

Le 22 oct. 2010 =E0 16:35, Scott Beuker a =E9crit :

>> The idea is that Teredo and 6to4, which are useful in some identified
>> scenarios but have some lose ends in some others, should be reserved =
to
>> users that know what they do.
>=20
>=20
> Exactly the opposite, in my opinion.

Note that the RFC on Teredo (RFC 4380) says "Teredo is designed to =
provide an "IPv6 access of last resort" to  nodes that need IPv6 =
connectivity but cannot use any of the other IPv6 transition schemes."
Today, the ordinary user doesn't NEED IPv6 connectivity.=20
In my understanding, Teredo is appropriate for those who know enough =
about IPv6 to determine that they NEED it, but oNLY for these.


> If you ask the creators of Teredo and 6to4, I think they'll tell you =
it's intended to catch the users who know nothing of IPv6, and allow the =
rest of us who do to proceed with the transition to IPv6, without having =
them hold us back.

I add a Direct copy to Brian Carpenter, the creator of 6to4.


It's also worth taking in consideration what James Woodyatt, a major =
promoter of 6to4 in Apple products, has written about 6to4-PMT:=20
"I'm about to start advocating seriously that the Darwin IPv6 stop =
autoconfiguring interface addresses with the 2002::/16 prefix even when =
the Prefix Information Option has the A=3D1 bit set.  If this draft =
progresses or operators start seriously looking like they're going to =
deploy 6to4-PMT, then I'm pretty sure there won't be any alternative."



Regards,
RD


>=20
> Regardless, as it is this is how it can be leveraged, and it will be =
for the best of the IPv6 transition effort if it is.
>=20
> - Scott



From ipng@69706e6720323030352d30312d31340a.nosense.org  Fri Oct 22 10:09:33 2010
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 472BE3A68F9 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 10:09:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.527
X-Spam-Level: 
X-Spam-Status: No, score=-0.527 tagged_above=-999 required=5 tests=[AWL=-0.524, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_13=0.6, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zq7ReEQPTPm0 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 10:09:32 -0700 (PDT)
Received: from smtp1.adam.net.au (smtp1.adam.net.au [202.136.110.253]) by core3.amsl.com (Postfix) with ESMTP id F02AD3A67AD for <v6ops@ietf.org>; Fri, 22 Oct 2010 10:09:31 -0700 (PDT)
Received: from 182-239-171-173.ip.adam.com.au ([182.239.171.173] helo=opy.nosense.org) by smtp1.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1P9L92-0004UL-QX for v6ops@ietf.org; Sat, 23 Oct 2010 03:41:08 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id D1D2A3B32F for <v6ops@ietf.org>; Sat, 23 Oct 2010 03:41:07 +1030 (CST)
Date: Sat, 23 Oct 2010 03:41:07 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
Cc: v6ops mailing list <v6ops@ietf.org>
Message-ID: <20101023034107.2e049007@opy.nosense.org>
In-Reply-To: <20101022135409.11E1328C0E8@core3.amsl.com>
References: <20101022135409.11E1328C0E8@core3.amsl.com>
X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [v6ops] Document Action: 'Recommended Simple Security Capabilities in Customer Premises Equipment for Providing Residential IPv6 Internet Service' to Informational RFC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 17:09:33 -0000

On Fri, 22 Oct 2010 06:54:09 -0700 (PDT)
The IESG <iesg-secretary@ietf.org> wrote:

> The IESG has approved the following document:
> 
> - 'Recommended Simple Security Capabilities in Customer Premises 
>    Equipment for Providing Residential IPv6 Internet Service '
>    <draft-ietf-v6ops-cpe-simple-security-16.txt> as an Informational RFC
> 

Well done everybody, especially James. I think I've read somewhere that
the DHCPv6 spec had set a record at 15 revisions ... it's just been
beaten :-)

> 
> This document is the product of the IPv6 Operations Working Group. 
> 
> The IESG contact persons are Ron Bonica and Dan Romascanu.
> 
> A URL of this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-v6ops-cpe-simple-security-16.txt
> 
> Technical Summary
>  
> This document identifies a set of recommendations for the makers of
> devices describing how to provide for "simple security" capabilities
> at the perimeter of local-area IPv6 networks in Internet-enabled
> homes and small offices.
>  
> Working Group Summary
>  
> The working group was divided on the concept of defining or recommending
> the use of firewalls; as a result, this document is very explicitly a set
> of recommendations for those that would choose to build or deploy a
> firewall without making any recommendation on whether anyone should do
> either. It describes a simple stateful firewall, permeable to traffic that
> is secured using IPsec.
>  
> Document Quality
>  
> There is at least one deployed implementation of this firewall, and
> expected to be others. The document clearly specifies a consensus set of
> recommendations for such firewalls.
> 
> Personel
> 
> Fred Baker is shepherd.
> 
> RFC Editor Note
> 
> OLD TEXT:
> 
> REC-13: 
> 
> By DEFAULT, Internet gateways SHOULD, automatically download
> and install software updates for extending IPv6 simple security for
> support of future standard upper layer transports and extension
> headers.
> 
> NEW TEXT:
> 
> REC-13:
> Residential Internet Gateways SHOULD provide a convenient means to 
> securely update their firmware, for the installation of security 
> patches and other manufacturer-recommended changes.
>  
> Vendors can expect users and operators to have differing viewpoints 
> on the maintenance of patches, with some preferring automated update 
> and some preferring manual initiation, and those preferring automated 
> update wanting to download from a vendor site or one managed by the 
> network operator. To handle the disparity, vendors are well advised 
> if they provide manual and automated options. In the automated case, 
> they would do well to facilitate pre-configuration of the download 
> URL and a means of validating the software image such as a certificate.
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

From alh-ietf@tndh.net  Fri Oct 22 10:43:46 2010
Return-Path: <alh-ietf@tndh.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1FE2F3A6948 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 10:43:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.638
X-Spam-Level: **
X-Spam-Status: No, score=2.638 tagged_above=-999 required=5 tests=[AWL=-0.222,  BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, FH_HOST_EQ_D_D_D_D=0.765,  HOST_EQ_STATICB=1.372, J_CHICKENPOX_13=0.6, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3xhBIr0WrxaR for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 10:43:45 -0700 (PDT)
Received: from tndh.net (static-66-15-163-216.bdsl.verizon.net [66.15.163.216]) by core3.amsl.com (Postfix) with ESMTP id 8B78F3A6951 for <v6ops@ietf.org>; Fri, 22 Oct 2010 10:43:43 -0700 (PDT)
X-AuthUser: alh-ietf@tndh.net
Received: from ahainW7 ([192.168.123.15]:60914) by tndh.net with [XMail 1.27 ESMTP Server] id <S18BFAB7> for <v6ops@ietf.org> from <alh-ietf@tndh.net>; Fri, 22 Oct 2010 10:44:42 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Victor Kuarsingh'" <victor.kuarsingh@gmail.com>, "'Mikael Abrahamsson'" <swmike@swm.pp.se>
References: <alpine.DEB.1.10.1010202249170.29868@uplift.swm.pp.se> <C8E4A5C1.102E3%victor.kuarsingh@gmail.com>
In-Reply-To: <C8E4A5C1.102E3%victor.kuarsingh@gmail.com>
Date: Fri, 22 Oct 2010 10:44:30 -0700
Message-ID: <043801cb7210$c99d17f0$5cd747d0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: ActwmWNkOtREesKARE678FrnFi7UBABdXWDw
Content-Language: en-us
Cc: 'IETF V6OPS WG' <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 17:43:46 -0000

The impact on the routing table for longer than /16 is complete FUD. The
reality is that the RIRs are most likely to put 6rd into a separate prefix
from the normal provider allocation, so there will be an impact on routing
in any case. Yes there will be more prefixes for a longer than /16 approach
than for a parallel 6rd prefix block, but if you remove TE from the picture
the actual number is more like 3x the number of provider AS's to ignore the
broken one-liner in 3056. 

Everyone needs to stop finding reasons to inhibit progress, do what is
necessary, and move on. There will be systems that need to operate in
unmanaged environments, and their needs are completely different from those
that are managed. Stop trying to force everything into the managed bucket.
Fix 3056 to say that longer prefixes in 2002:: are an appropriate way for a
provider to start managing those unmanaged systems while they wean those
customers off the unmanaged technology. 

FWIW: I believe kuarsingh-v6ops-6to4-provider-managed-tunnel is a bad idea
because it is fundamentally a 66nat. The right thing to do is ignore 3056
and advertise the appropriate longer than /16 prefix to cause symmetric
traffic. This is not a long term solution, so a short term hit to the IPv6
routing table is not an issue.

Tony


> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
> Of Victor Kuarsingh
> Sent: Wednesday, October 20, 2010 1:57 PM
> To: Mikael Abrahamsson
> Cc: IETF V6OPS WG
> Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-
> managed-tunnel-00.txt
> 
> Mikael,
> 
> Fair enough.. As noted to Gert, it was "an" idea, and it's already off
> the
> table.. It was just a discussion point.
> 
> I agree, I don't think anyone is going there (it seems to be a well
> understood principle).  But as you said, since the RFC comments on it,
> it
> would in fact be an RFC update.
> 
> Regards,
> 
> Victor
> 
> 
> On 20/10/10 1:52 PM, "Mikael Abrahamsson" <swmike@swm.pp.se> wrote:
> 
> > On Wed, 20 Oct 2010, Victor Kuarsingh wrote:
> >
> >> We are not changing 6to4... It's status quo.. We are just adding an
> new
> >> layer to improve created a deterministic path (with loss of e2e).
> >
> > No, 6to4 specifically prohibits more specifics in 2002::/16, to quote
> > RFC3056:
> >
> > "6to4 prefixes more specific than 2002::/16 must not be propagated in
> >     native IPv6 routing, to prevent pollution of the IPv6 routing
> table
> >     by elements of the IPv4 routing table. "
> >
> >> The longer then /16 route is not a mod either, it's a global
> agreement issue
> >> (will we accept longer then /16 for 2002::).
> >
> > The RFC prohibits this, so what you're asking for is a change of the
> RFC.
> >
> > We're not going there, period.
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From alh-ietf@tndh.net  Fri Oct 22 10:55:56 2010
Return-Path: <alh-ietf@tndh.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C692D3A6826 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 10:55:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.746
X-Spam-Level: *
X-Spam-Status: No, score=1.746 tagged_above=-999 required=5 tests=[AWL=0.726,  BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, FH_HOST_EQ_D_D_D_D=0.765, HOST_EQ_STATICB=1.372]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GF4Fsd55YUrY for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 10:55:53 -0700 (PDT)
Received: from tndh.net (static-66-15-163-216.bdsl.verizon.net [66.15.163.216]) by core3.amsl.com (Postfix) with ESMTP id CDEC13A682B for <v6ops@ietf.org>; Fri, 22 Oct 2010 10:55:53 -0700 (PDT)
X-AuthUser: alh-ietf@tndh.net
Received: from ahainW7 ([192.168.123.15]:50248) by tndh.net with [XMail 1.27 ESMTP Server] id <S18BFACC> for <v6ops@ietf.org> from <alh-ietf@tndh.net>; Fri, 22 Oct 2010 10:57:39 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Ole Troan'" <ot@cisco.com>, "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>
References: <C8E56757.2A817%john_brzozowski@cable.comcast.com>	<4CC0A1A2.3060003@gmail.com>	<11EA1C19-01B2-46B6-A0EE-6CB760F3482E@cisco.com>	<4CC0AABD.6060207@gmail.com> <BF19AF42-62D0-4C9E-BDB2-1AC759881879@cisco.com>
In-Reply-To: <BF19AF42-62D0-4C9E-BDB2-1AC759881879@cisco.com>
Date: Fri, 22 Oct 2010 10:57:28 -0700
Message-ID: <043d01cb7212$98f17590$cad460b0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: ActxolQcd0RwiarNQCuzpf0n8d30DgAb8pWA
Content-Language: en-us
Cc: 'IPv6 Operations' <v6ops@ietf.org>, "'Brzozowski, John'" <John_Brzozowski@Cable.Comcast.com>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 17:55:56 -0000

Ole Troan wrote:
> ...
> so creating two protocols doing exactly the same thing is a good thing?

When the target environments are different -- YES.  Having different
solutions for managed vs. unmanaged environments that actually are
completely self-contained is required. The failure to date is that too many
people want to assert their view of how to manage a network onto other
people's environments. Both operational models are valid, so independent and
fully functional tools need to exist for each. 

Tony




From victor.kuarsingh@gmail.com  Fri Oct 22 10:58:07 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6D2CC3A6826 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 10:58:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.597
X-Spam-Level: 
X-Spam-Status: No, score=-0.597 tagged_above=-999 required=5 tests=[AWL=0.162,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b0Q3ZcN+bw+W for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 10:58:06 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id E70903A6899 for <v6ops@ietf.org>; Fri, 22 Oct 2010 10:58:05 -0700 (PDT)
Received: by wwe15 with SMTP id 15so1110565wwe.13 for <v6ops@ietf.org>; Fri, 22 Oct 2010 10:59:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=OT6ZXa6faFzhEL5hQTVcfXDoVMZ1wL39DFr+ZopkHQk=; b=oOebIgxYRxhsKzxok3U0cMBaSbVv0jw56ZS8hmWAB04NqBV08TCoj58vJVvpPwy9Xi 0Y8bNtpDHCEU7n/zxjVzzQ/ZRBjCJWfgvAG/ea/A5CvYck2hP07aWlw40UFDoEkbwmnP nHuYYpYlSgCloB6TcEo7ThModxVnct4swfzMA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=pap6DYuEQeDIjUEbJsatYYYQSUrA3PM+3sAu4VjHjmKQ7IoBcjn+qBXtdf9M7Hs9cX bVTQIE8b8xS/92rH2smHXiYAwsx4bK/GL0duLFb1bbGurOQazqspIYCo3QK/XY6F4+Op DG50JMst1HogSiO0ykB72G8j/VHbMKfKaYiX0=
Received: by 10.227.146.142 with SMTP id h14mr3261151wbv.25.1287770382816; Fri, 22 Oct 2010 10:59:42 -0700 (PDT)
Received: from [10.16.150.59] (surf99.net.rss.rogers.com [24.114.255.99]) by mx.google.com with ESMTPS id a17sm2729254wbe.0.2010.10.22.10.59.40 (version=SSLv3 cipher=RC4-MD5); Fri, 22 Oct 2010 10:59:42 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Fri, 22 Oct 2010 13:59:35 -0400
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: Tony Hain <alh-ietf@tndh.net>, 'Mikael Abrahamsson' <swmike@swm.pp.se>
Message-ID: <C8E74947.1055B%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
Thread-Index: ActwmWNkOtREesKARE678FrnFi7UBABdXWDwAAECeXo=
In-Reply-To: <043801cb7210$c99d17f0$5cd747d0$@net>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: 'IETF V6OPS WG' <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 17:58:07 -0000

Tony,

If there would be consensus on longer then /16s on 2002:: then the PMT model
operation is not needed.  It would provide the same level of "control"
without the need for PT66.

But, we (operators) need something that works with "deployed" software
features in deployed hardware (of which 6to4 is one of them - I like 6RD and
other technologies, but they are just not currently in many/most of the
equipment in production networks).

We (operators) just had the distinct impression that the rules set in 3056
(as I was informed the other day) were "firm" and not likely to be broken.
Brian noted the other day that 3056 was fitted with that text based on
"feedback" at that time.  Do you think this can be reversed / modified?  I
got the impression there is considerable negative support on this.

Regards,

Victor


On 22/10/10 1:44 PM, "Tony Hain" <alh-ietf@tndh.net> wrote:

> The impact on the routing table for longer than /16 is complete FUD. The
> reality is that the RIRs are most likely to put 6rd into a separate prefix
> from the normal provider allocation, so there will be an impact on routing
> in any case. Yes there will be more prefixes for a longer than /16 approach
> than for a parallel 6rd prefix block, but if you remove TE from the picture
> the actual number is more like 3x the number of provider AS's to ignore the
> broken one-liner in 3056.
> 
> Everyone needs to stop finding reasons to inhibit progress, do what is
> necessary, and move on. There will be systems that need to operate in
> unmanaged environments, and their needs are completely different from those
> that are managed. Stop trying to force everything into the managed bucket.
> Fix 3056 to say that longer prefixes in 2002:: are an appropriate way for a
> provider to start managing those unmanaged systems while they wean those
> customers off the unmanaged technology.
> 
> FWIW: I believe kuarsingh-v6ops-6to4-provider-managed-tunnel is a bad idea
> because it is fundamentally a 66nat. The right thing to do is ignore 3056
> and advertise the appropriate longer than /16 prefix to cause symmetric
> traffic. This is not a long term solution, so a short term hit to the IPv6
> routing table is not an issue.
> 
> Tony
> 
> 
>> -----Original Message-----
>> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
>> Of Victor Kuarsingh
>> Sent: Wednesday, October 20, 2010 1:57 PM
>> To: Mikael Abrahamsson
>> Cc: IETF V6OPS WG
>> Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-
>> managed-tunnel-00.txt
>> 
>> Mikael,
>> 
>> Fair enough.. As noted to Gert, it was "an" idea, and it's already off
>> the
>> table.. It was just a discussion point.
>> 
>> I agree, I don't think anyone is going there (it seems to be a well
>> understood principle).  But as you said, since the RFC comments on it,
>> it
>> would in fact be an RFC update.
>> 
>> Regards,
>> 
>> Victor
>> 
>> 
>> On 20/10/10 1:52 PM, "Mikael Abrahamsson" <swmike@swm.pp.se> wrote:
>> 
>>> On Wed, 20 Oct 2010, Victor Kuarsingh wrote:
>>> 
>>>> We are not changing 6to4... It's status quo.. We are just adding an
>> new
>>>> layer to improve created a deterministic path (with loss of e2e).
>>> 
>>> No, 6to4 specifically prohibits more specifics in 2002::/16, to quote
>>> RFC3056:
>>> 
>>> "6to4 prefixes more specific than 2002::/16 must not be propagated in
>>>     native IPv6 routing, to prevent pollution of the IPv6 routing
>> table
>>>     by elements of the IPv4 routing table. "
>>> 
>>>> The longer then /16 route is not a mod either, it's a global
>> agreement issue
>>>> (will we accept longer then /16 for 2002::).
>>> 
>>> The RFC prohibits this, so what you're asking for is a change of the
>> RFC.
>>> 
>>> We're not going there, period.
>> 
>> 
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
> 



From john_brzozowski@cable.comcast.com  Fri Oct 22 11:04:14 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 09D3E3A6936 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 11:04:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.713
X-Spam-Level: 
X-Spam-Status: No, score=-107.713 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G0L19TsoeGIB for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 11:04:12 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 692BB3A68A4 for <v6ops@ietf.org>; Fri, 22 Oct 2010 11:04:12 -0700 (PDT)
Received: from ([24.40.55.40]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.101185069; Fri, 22 Oct 2010 14:05:45 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by pacdcexhub03.cable.comcast.com ([fe80::d1dd:b302:b617:3755%12]) with mapi id 14.01.0255.000; Fri, 22 Oct 2010 14:05:45 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: Ole Troan <ot@cisco.com>, "Brian E. Carpenter" <brian.e.carpenter@gmail.com>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again
Thread-Index: AQHLcaIzGAgvL+p1b0efThcxErp8n5NNREiA
Date: Fri, 22 Oct 2010 18:05:45 +0000
Message-ID: <C8E74AC5.2AF55%john_brzozowski@cable.comcast.com>
In-Reply-To: <BF19AF42-62D0-4C9E-BDB2-1AC759881879@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <AA945616491DC548AA879B13370A0576@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 18:04:14 -0000

On 10/22/10 12:32 AM, "Ole Troan" <ot@cisco.com> wrote:

> Brian,
>=20
>>>>>>> Providing the hint does not guarantee that the operator will always
>>>>>>> honor
>>>>>>> the hint.  This, however, is a step in the right direction to ensur=
e the
>>>>>>> IGD
>>>>>>> is offered an appropriately sized IPv6 prefix.
>>>>>> my assumption is that residential customers get the same address blo=
ck
>>>>>> size
>>>>>> independent of what their actual need is.
>>>>> [jjmb] at this time I do not share this assumption, I may over time. =
 I
>>>>> also
>>>>> not sure if this a universally accepted assumption.
>>>> Absolutely not. It's entirely a matter between the customer and the IS=
P.
>>>> The ISP might choose to offer a one-size-fits-all model or a user-choo=
ses
>>>> (and pays) model. This is emphatically not the IETF's business, beyond
>>>> what is said in draft-ietf-v6ops-3177bis-end-sites.
>>>=20
>>> certainly, and I didn't imply anything else.
>>> DHCP PD does indeed contain a prefix length, but it is not suitable as =
a
>>> protocol to negotiate the size of an address block.
>>>=20
>>> what do you gain from doing dynamic address block size negotiations bet=
ween
>>> RR and DR?
>>> as opposed to the customer getting whatever address block size he desir=
es
>>> when buying the service?
>>=20
>> I tend to agree, but again, that's not IETF business.
>=20
> but it is the IETF business how our protocols work.
> where in rfc3633 is this behaviour specified?
[jjmb] what do you mean?  You yourself cited the text in RFC3633 where the
prefix size hints can be used?
>=20
>>>> In our protocols, prefix length clearly needs to be a parameter
>>>> (as it is in draft-hu-pppext-ipv6cp-extensions, for example).
>>>=20
>>> so now we are not only going to replicate all functions between DHCPv6 =
and
>>> RA options, but also for IPv6CP? that appears to be a bad idea.
>>=20
>> Well, there are arguments about why this is needed from an operational
>> viewpoint
>> in draft-hu-pppext-ipv6cp-requirements. I guess they should be discussed
>> on the pppext list.
>=20
> so creating two protocols doing exactly the same thing is a good thing?
[jjmb] are you saying that draft-hu-pppext-ipv6cp-requirements =3D=3D RFC36=
33?
>=20
> cheers,
> Ole
>=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From gert@space.net  Fri Oct 22 12:02:59 2010
Return-Path: <gert@space.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E3F33A68C0 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 12:02:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.024
X-Spam-Level: 
X-Spam-Status: No, score=-2.024 tagged_above=-999 required=5 tests=[AWL=-0.425, BAYES_00=-2.599, J_BACKHAIR_44=1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Rby3bez91fs for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 12:02:58 -0700 (PDT)
Received: from mobil.space.net (mobil.Space.Net [IPv6:2001:608:2:81::2]) by core3.amsl.com (Postfix) with ESMTP id 1503A3A6918 for <v6ops@ietf.org>; Fri, 22 Oct 2010 12:02:57 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id 85AD0F80E1 for <v6ops@ietf.org>; Fri, 22 Oct 2010 21:04:34 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 44CA4F8281 for <v6ops@ietf.org>; Fri, 22 Oct 2010 21:04:34 +0200 (CEST)
Received: (qmail 8718 invoked by uid 1007); 22 Oct 2010 21:04:34 +0200
Date: Fri, 22 Oct 2010 21:04:34 +0200
From: Gert Doering <gert@space.net>
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>
Message-ID: <20101022190434.GT32268@Space.Net>
References: <043801cb7210$c99d17f0$5cd747d0$@net> <C8E74947.1055B%victor.kuarsingh@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C8E74947.1055B%victor.kuarsingh@gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: 'IETF V6OPS WG' <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 19:02:59 -0000

Hi,

On Fri, Oct 22, 2010 at 01:59:35PM -0400, Victor Kuarsingh wrote:
> We (operators) just had the distinct impression that the rules set in 3056
> (as I was informed the other day) were "firm" and not likely to be broken.
> Brian noted the other day that 3056 was fitted with that text based on
> "feedback" at that time.  Do you think this can be reversed / modified?  I
> got the impression there is considerable negative support on this.

One approach to rework 3056 would be to completely deprecate the 
6to4-with-anycast model.  Get the vendors to drop it from their
operating systems (at least as "default-on") - possibly adding new
rules that only 6to4<->6to4 traffic is allowed to use the 6to4 tunnels,
and that traffic destined to other IPv6 addresses MUST NOT be sent
with a source address of 2002::

So, yes, unreachability for "IPv4-only clients" to "IPv6-only servers".

If there's real interest to reach those servers, the clients will find
a way to get IPv6 - but it's unlikely that we'll see IPv6-only servers
any time soon.

Gert Doering
        -- NetMaster
-- 
did you enable IPv6 on something today...?

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

From rdroms@cisco.com  Fri Oct 22 12:26:42 2010
Return-Path: <rdroms@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D3B2D3A6822 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 12:26:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.267
X-Spam-Level: 
X-Spam-Status: No, score=-10.267 tagged_above=-999 required=5 tests=[AWL=-0.268, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TfarbRCrMBG3 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 12:26:37 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id E89963A680C for <v6ops@ietf.org>; Fri, 22 Oct 2010 12:26:36 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEACeCwUxAZnwN/2dsb2JhbAChaHGieJwRhUoEik0
X-IronPort-AV: E=Sophos;i="4.58,224,1286150400"; d="scan'208";a="173748823"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 22 Oct 2010 19:28:14 +0000
Received: from bxb-rdroms-8712.cisco.com (bxb-rdroms-8712.cisco.com [10.98.10.83]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o9MJSD01024794; Fri, 22 Oct 2010 19:28:13 GMT
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms@cisco.com>
In-Reply-To: <20101023034107.2e049007@opy.nosense.org>
Date: Fri, 22 Oct 2010 15:28:13 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <804E93BB-B90E-427B-8A83-98E1D36DDC3F@cisco.com>
References: <20101022135409.11E1328C0E8@core3.amsl.com> <20101023034107.2e049007@opy.nosense.org>
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Mailer: Apple Mail (2.1081)
Cc: v6ops mailing list <v6ops@ietf.org>
Subject: Re: [v6ops] Document Action: 'Recommended Simple Security Capabilities in Customer Premises Equipment for Providing Residential IPv6 Internet Service' to Informational RFC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 19:26:42 -0000

With a little research - regrettably, we didn't record the actual rev =
number in RFC 3315 - the highest numbered rev of the DHCPv6 spec I could =
find was draft-ietf-dhc-dhcpv6-28.

=46rom the Acknowledgments in RFC 3315:

   And, thanks to Steve Deering for pointing out at IETF 51 in London
   that the DHCPv6 specification has the highest revision number of any
   Internet Draft.

In any event, that record has been significantly exceeded by more recent =
drafts: draft-hixie-thewebsocketprotocol-77.txt=20

- Ralph

On Oct 22, 2010, at 1:11 PM 10/22/10, Mark Smith wrote:

> On Fri, 22 Oct 2010 06:54:09 -0700 (PDT)
> The IESG <iesg-secretary@ietf.org> wrote:
>=20
>> The IESG has approved the following document:
>>=20
>> - 'Recommended Simple Security Capabilities in Customer Premises=20
>>   Equipment for Providing Residential IPv6 Internet Service '
>>   <draft-ietf-v6ops-cpe-simple-security-16.txt> as an Informational =
RFC
>>=20
>=20
> Well done everybody, especially James. I think I've read somewhere =
that
> the DHCPv6 spec had set a record at 15 revisions ... it's just been
> beaten :-)
>=20
>>=20
>> This document is the product of the IPv6 Operations Working Group.=20
>>=20
>> The IESG contact persons are Ron Bonica and Dan Romascanu.
>>=20
>> A URL of this Internet-Draft is:
>> =
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-cpe-simple-security-1=
6.txt
>>=20
>> Technical Summary
>>=20
>> This document identifies a set of recommendations for the makers of
>> devices describing how to provide for "simple security" capabilities
>> at the perimeter of local-area IPv6 networks in Internet-enabled
>> homes and small offices.
>>=20
>> Working Group Summary
>>=20
>> The working group was divided on the concept of defining or =
recommending
>> the use of firewalls; as a result, this document is very explicitly a =
set
>> of recommendations for those that would choose to build or deploy a
>> firewall without making any recommendation on whether anyone should =
do
>> either. It describes a simple stateful firewall, permeable to traffic =
that
>> is secured using IPsec.
>>=20
>> Document Quality
>>=20
>> There is at least one deployed implementation of this firewall, and
>> expected to be others. The document clearly specifies a consensus set =
of
>> recommendations for such firewalls.
>>=20
>> Personel
>>=20
>> Fred Baker is shepherd.
>>=20
>> RFC Editor Note
>>=20
>> OLD TEXT:
>>=20
>> REC-13:=20
>>=20
>> By DEFAULT, Internet gateways SHOULD, automatically download
>> and install software updates for extending IPv6 simple security for
>> support of future standard upper layer transports and extension
>> headers.
>>=20
>> NEW TEXT:
>>=20
>> REC-13:
>> Residential Internet Gateways SHOULD provide a convenient means to=20
>> securely update their firmware, for the installation of security=20
>> patches and other manufacturer-recommended changes.
>>=20
>> Vendors can expect users and operators to have differing viewpoints=20=

>> on the maintenance of patches, with some preferring automated update=20=

>> and some preferring manual initiation, and those preferring automated=20=

>> update wanting to download from a vendor site or one managed by the=20=

>> network operator. To handle the disparity, vendors are well advised=20=

>> if they provide manual and automated options. In the automated case,=20=

>> they would do well to facilitate pre-configuration of the download=20
>> URL and a means of validating the software image such as a =
certificate.
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From volz@cisco.com  Fri Oct 22 12:38:32 2010
Return-Path: <volz@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E5393A695D for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 12:38:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.053
X-Spam-Level: 
X-Spam-Status: No, score=-10.053 tagged_above=-999 required=5 tests=[AWL=-0.054, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4hVLbsNcLuST for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 12:38:31 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 451983A696D for <v6ops@ietf.org>; Fri, 22 Oct 2010 12:38:13 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAPiEwUytJV2Z/2dsb2JhbAChaHGiW5wThUoEhFaJAQ
X-IronPort-AV: E=Sophos;i="4.58,224,1286150400"; d="scan'208";a="173962210"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rtp-iport-2.cisco.com with ESMTP; 22 Oct 2010 19:38:30 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id o9MJcRiO025754;  Fri, 22 Oct 2010 19:38:27 GMT
Received: from xmb-rcd-101.cisco.com ([72.163.62.143]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 22 Oct 2010 14:38:28 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 22 Oct 2010 14:38:23 -0500
Message-ID: <D9B5773329187548A0189ED65036678904932107@XMB-RCD-101.cisco.com>
In-Reply-To: <804E93BB-B90E-427B-8A83-98E1D36DDC3F@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops] Document Action: 'Recommended Simple SecurityCapabilities in Customer Premises Equipment for ProvidingResidential IPv6 Internet Service' to Informational RFC
Thread-Index: ActyH11ERiDU9DweRYa7HAWj5UAhKgAAMc6A
References: <20101022135409.11E1328C0E8@core3.amsl.com><20101023034107.2e049007@opy.nosense.org> <804E93BB-B90E-427B-8A83-98E1D36DDC3F@cisco.com>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Ralph Droms (rdroms)" <rdroms@cisco.com>, "Mark Smith" <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-OriginalArrivalTime: 22 Oct 2010 19:38:28.0056 (UTC) FILETIME=[B3299D80:01CB7220]
Cc: v6ops mailing list <v6ops@ietf.org>
Subject: Re: [v6ops] Document Action: 'Recommended Simple SecurityCapabilities in Customer Premises Equipment for ProvidingResidential IPv6 Internet Service' to Informational RFC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 19:38:32 -0000

Just so the record is correct, technically they only got to 76:

http://www.ietf.org/id/draft-hixie-thewebsocketprotocol-77.txt:

---
This Internet-Draft, draft-hixie-thewebsocketprotocol-76.txt, has been
replaced by another
document, draft-ietf-hybi-thewebsocketprotocol-01.txt, and has been
deleted from the=20
Internet-Drafts directory.

Internet-Drafts are not archival documents, and copies of
Internet-Drafts
that have been deleted from the directory are not available.  The
Secretariat does not have any information regarding the future plans of
the author(s) or working group, if applicable, with respect to this
deleted Internet-Draft.  For more information, or to request a copy of
the document, please contact the author(s) directly.=20

Draft Author(s):

 I. Hickson <ian@hixie.ch>
---

Kind of sad they didn't keep going, but 76 is a going to be a tough
record to beat -- I would have long given up?

- Bernie

-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
Of Ralph Droms (rdroms)
Sent: Friday, October 22, 2010 3:28 PM
To: Mark Smith
Cc: v6ops mailing list
Subject: Re: [v6ops] Document Action: 'Recommended Simple
SecurityCapabilities in Customer Premises Equipment for
ProvidingResidential IPv6 Internet Service' to Informational RFC

With a little research - regrettably, we didn't record the actual rev
number in RFC 3315 - the highest numbered rev of the DHCPv6 spec I could
find was draft-ietf-dhc-dhcpv6-28.

>From the Acknowledgments in RFC 3315:

   And, thanks to Steve Deering for pointing out at IETF 51 in London
   that the DHCPv6 specification has the highest revision number of any
   Internet Draft.

In any event, that record has been significantly exceeded by more recent
drafts: draft-hixie-thewebsocketprotocol-77.txt=20

- Ralph

On Oct 22, 2010, at 1:11 PM 10/22/10, Mark Smith wrote:

> On Fri, 22 Oct 2010 06:54:09 -0700 (PDT)
> The IESG <iesg-secretary@ietf.org> wrote:
>=20
>> The IESG has approved the following document:
>>=20
>> - 'Recommended Simple Security Capabilities in Customer Premises=20
>>   Equipment for Providing Residential IPv6 Internet Service '
>>   <draft-ietf-v6ops-cpe-simple-security-16.txt> as an Informational
RFC
>>=20
>=20
> Well done everybody, especially James. I think I've read somewhere
that
> the DHCPv6 spec had set a record at 15 revisions ... it's just been
> beaten :-)
>=20
>>=20
>> This document is the product of the IPv6 Operations Working Group.=20
>>=20
>> The IESG contact persons are Ron Bonica and Dan Romascanu.
>>=20
>> A URL of this Internet-Draft is:
>>
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-cpe-simple-security
-16.txt
>>=20
>> Technical Summary
>>=20
>> This document identifies a set of recommendations for the makers of
>> devices describing how to provide for "simple security" capabilities
>> at the perimeter of local-area IPv6 networks in Internet-enabled
>> homes and small offices.
>>=20
>> Working Group Summary
>>=20
>> The working group was divided on the concept of defining or
recommending
>> the use of firewalls; as a result, this document is very explicitly a
set
>> of recommendations for those that would choose to build or deploy a
>> firewall without making any recommendation on whether anyone should
do
>> either. It describes a simple stateful firewall, permeable to traffic
that
>> is secured using IPsec.
>>=20
>> Document Quality
>>=20
>> There is at least one deployed implementation of this firewall, and
>> expected to be others. The document clearly specifies a consensus set
of
>> recommendations for such firewalls.
>>=20
>> Personel
>>=20
>> Fred Baker is shepherd.
>>=20
>> RFC Editor Note
>>=20
>> OLD TEXT:
>>=20
>> REC-13:=20
>>=20
>> By DEFAULT, Internet gateways SHOULD, automatically download
>> and install software updates for extending IPv6 simple security for
>> support of future standard upper layer transports and extension
>> headers.
>>=20
>> NEW TEXT:
>>=20
>> REC-13:
>> Residential Internet Gateways SHOULD provide a convenient means to=20
>> securely update their firmware, for the installation of security=20
>> patches and other manufacturer-recommended changes.
>>=20
>> Vendors can expect users and operators to have differing viewpoints=20
>> on the maintenance of patches, with some preferring automated update=20
>> and some preferring manual initiation, and those preferring automated

>> update wanting to download from a vendor site or one managed by the=20
>> network operator. To handle the disparity, vendors are well advised=20
>> if they provide manual and automated options. In the automated case,=20
>> they would do well to facilitate pre-configuration of the download=20
>> URL and a means of validating the software image such as a
certificate.
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

From john_brzozowski@cable.comcast.com  Fri Oct 22 12:38:37 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 034643A6916 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 12:38:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.022
X-Spam-Level: 
X-Spam-Status: No, score=-108.022 tagged_above=-999 required=5 tests=[AWL=0.441, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qJZ464iSDJBP for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 12:38:34 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 78B9228C129 for <v6ops@ietf.org>; Fri, 22 Oct 2010 12:38:15 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.101218495; Fri, 22 Oct 2010 15:38:52 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by PACDCEXHUB02.cable.comcast.com ([fe80::11d4:f530:37a0:9f4e%12]) with mapi id 14.01.0255.000; Fri, 22 Oct 2010 15:38:52 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: Tony Hain <alh-ietf@tndh.net>, Ole Troan <ot@cisco.com>, "Brian E. Carpenter" <brian.e.carpenter@gmail.com>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again
Thread-Index: ActyIMiWGAgvL+p1b0efThcxErp8nw==
Date: Fri, 22 Oct 2010 19:38:51 +0000
Message-ID: <C8E76098.2AFB6%john_brzozowski@cable.comcast.com>
In-Reply-To: <043d01cb7212$98f17590$cad460b0$@net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2D459BA1415DFC4DA422F652238A0C0E@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 'IPv6 Operations' <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 19:38:37 -0000

To add to Tony's point, I have to agree that there are folks that do not
have experience operating networks, specifically deploying IPv6, that seem
to enjoy asserting their assumptions and views.  Instead of doing this it
might be useful (and more productive) if folks first tried to understand ho=
w
various types of networks work before making recommendations, etc.

John


On 10/22/10 1:57 PM, "Tony Hain" <alh-ietf@tndh.net> wrote:

> Ole Troan wrote:
>> ...
>> so creating two protocols doing exactly the same thing is a good thing?
>=20
> When the target environments are different -- YES.  Having different
> solutions for managed vs. unmanaged environments that actually are
> completely self-contained is required. The failure to date is that too ma=
ny
> people want to assert their view of how to manage a network onto other
> people's environments. Both operational models are valid, so independent =
and
> fully functional tools need to exist for each.
>=20
> Tony
>=20
>=20
>=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From swmike@swm.pp.se  Fri Oct 22 12:41:26 2010
Return-Path: <swmike@swm.pp.se>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8BC1528C128 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 12:41:24 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F5tFu3vgtE6Q for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 12:41:22 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id 281AB28C150 for <v6ops@ietf.org>; Fri, 22 Oct 2010 12:38:40 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 777249E; Fri, 22 Oct 2010 21:40:18 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 760E29A for <v6ops@ietf.org>; Fri, 22 Oct 2010 21:40:18 +0200 (CEST)
Date: Fri, 22 Oct 2010 21:40:18 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: 'IETF V6OPS WG' <v6ops@ietf.org>
In-Reply-To: <C8E74947.1055B%victor.kuarsingh@gmail.com>
Message-ID: <alpine.DEB.1.10.1010222138140.29868@uplift.swm.pp.se>
References: <C8E74947.1055B%victor.kuarsingh@gmail.com>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 19:41:26 -0000

On Fri, 22 Oct 2010, Victor Kuarsingh wrote:

> We (operators) just had the distinct impression that the rules set in 
> 3056 (as I was informed the other day) were "firm" and not likely to be 
> broken. Brian noted the other day that 3056 was fitted with that text 
> based on "feedback" at that time.  Do you think this can be reversed / 
> modified?  I got the impression there is considerable negative support 
> on this.

I don't really know what you mean by "considerable negative support" in 
this context, but I don't know many people who seriously think importing 
the IPv4 table into IPv6 under 2002::/16 is a good idea.

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

From john_brzozowski@cable.comcast.com  Fri Oct 22 12:43:53 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B59F13A6807 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 12:43:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.898
X-Spam-Level: 
X-Spam-Status: No, score=-107.898 tagged_above=-999 required=5 tests=[AWL=0.265, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PP-bvI3OCDMn for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 12:43:49 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 29ACB3A67FD for <v6ops@ietf.org>; Fri, 22 Oct 2010 12:43:49 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.101220680; Fri, 22 Oct 2010 15:45:23 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by PACDCEXHUB02.cable.comcast.com ([fe80::11d4:f530:37a0:9f4e%12]) with mapi id 14.01.0255.000; Fri, 22 Oct 2010 15:45:23 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: =?iso-8859-1?Q?Ole_Tr=F8an?= <otroan@employees.org>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
Thread-Index: ActyIazf2T6t3TrIl0mUPJfZCE79dQ==
Date: Fri, 22 Oct 2010 19:45:22 +0000
Message-ID: <C8E76217.2AFBD%john_brzozowski@cable.comcast.com>
In-Reply-To: <D926804D-A16F-40FC-AFF1-C15469D8B319@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <8FED4B479B07DA49B97AE4BAE3CB63C3@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 19:43:53 -0000

On 10/21/10 5:03 AM, "Ole Tr=F8an" <otroan@employees.org> wrote:

> John,
>=20
> [...]
>=20
>>> as more advanced home networks evolve, it is going to be difficult for =
the
>>> border router to know the number of links that exists or may appear in =
the
>>> future. the intention with PD was always that the prefix size was a
>>> contractual matter, not one which is negotiated 'real time'.
>> [jjmb] Hmmm...RFC3633 is a contract?
>=20
> a fax replacement. I'd expect when I buy service from an ISP the contract
> between me and the ISP also includes the size of the prefix I will be ass=
igned
> as well as guarantees about its lifetime.
[jjmb] as stated in other emails we are dealing with protocols not
contracts.  Brian stated it well, this is between the subscriber and
operators, not the IETF.
>=20
> currently the hint in 3633 is just a MAY and even then there is only text
> suggesting that the requesting router should include a prefix, to hint to=
 the
> server that it would like to receive the same prefix that was presumably
> previously delegated. WPD-2 in draft-ietf-v6ops-ipv6-cpe-router-07 includ=
es a
> MAY hint to the delegating router about the size it would require and WPD=
-3
> states it MUST accept a different prefix size.
[jjmb] operators also have there own requirements, which may vary.  I for
one will be requiring the hint.
>=20
> DHCPv6 PD is a mechanism where the control and policy is at the DHCPv6 PD
> server.
>=20
> you could write a proposal to strengthen this language, but I would posit=
 that
> the IPv6 CE is in no position to know a priori what size to ask for.
[jjmb] really?  An IPv6 CPE has no way to determine how many and what sort
of interfaces it is built to support or configure with?  It is not aware of
its configuration which in turn would drive its provisioning request?  IMO
this is most certainly something an IGD can and should be programmatically
aware of specifically when initializing.
>=20
>>> mind you, I'm not an operator and I would surely like to understand the
>>> reasons why doing more negotiation would be useful? of course, one has =
to
>>> expect that every CPE supports a delegation of <=3D/64. are there reall=
y
>>> implementations which only supports a single /64? if so, I'd claim that=
's a
>>> bug and not in line with 3633 nor the basic ipv6 ce router requirements
>>> specification.
>> [jjmb] having flexibility is a must, making substantial fixed decisions =
this
>> early can result in complications or even limitations.  I absolutely agr=
ee
>> with one of your comments above, home networks will evolve.  As such we =
need
>> to ensure we have the ability to accommodate the same over time.  An
>> incremental approach supports this goal.  Yes there are implementations =
that
>> only support a /64, nothing shorter largely because they physically do n=
ot
>> have the need and/or ability to support anything else.  If a device has =
only
>> one IPv4 LAN and cannot be upgraded to support more (including hierarchi=
cal
>> PD) why would this be a bug?  I think we will have to agree to disagree,=
 I
>> do not view this as a bug.  I do think this is inline with RFC3633 and t=
he
>> IPv6 CPE router requirements.  A lot of work has been done over the past
>> couple of years to get some existing routers to be software upgradable t=
o
>> support native IPv6 as such there may be some devices with lesser
>> capabilities.  Having a minimal level of support for IPv6 is better than
>> none, right?  Finally, there may be a wide range of routers built over t=
ime
>> that range in caliber and features.
>=20
> I think we are in agreement. I'm certainly not suggesting that e.g. a /56=
 is
> the only way it can be done. nor that delegations have to be rigid. every
> implementation must support any prefix length thrown at it, with the exce=
ption
> of getting a so small address block that it doesn't get a single /64 per =
link.
>=20
> I'm just saying that the rfc3633 "hint" may not be very useful; and that
> delegating the absolute minimum address block required may be problematic=
. for
> example if the CE after a delegation is done determines that it needs a l=
arger
> block, the home network may have to be renumbered.
[jjmb] if a CE can only support the minimum why is it a problem for it to b=
e
provisioning with the minimum?  If a CE after its initial provisioning is
reconfigured to support additional VLANs renumbering will have to occur
anyway no?
>=20
> thinking of DHCP PD as a fax replacement, lets you not have to think abou=
t all
> the hard corner cases. ;-)
[jjmb] I still am not clear to the reference to fax replacement, sorry.
>=20
> cheers,
> Ole

=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
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From rdroms@cisco.com  Fri Oct 22 12:47:41 2010
Return-Path: <rdroms@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 79AE03A680C for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 12:47:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.254
X-Spam-Level: 
X-Spam-Status: No, score=-10.254 tagged_above=-999 required=5 tests=[AWL=-0.255, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X41WbyhvAXZe for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 12:47:39 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 4B1783A6805 for <v6ops@ietf.org>; Fri, 22 Oct 2010 12:47:39 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.58,224,1286150400"; d="scan'208";a="173966193"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 22 Oct 2010 19:49:17 +0000
Received: from bxb-rdroms-8712.cisco.com (bxb-rdroms-8712.cisco.com [10.98.10.83]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o9MJnHHS019970; Fri, 22 Oct 2010 19:49:17 GMT
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: Ralph Droms <rdroms@cisco.com>
In-Reply-To: <C8E76217.2AFBD%john_brzozowski@cable.comcast.com>
Date: Fri, 22 Oct 2010 15:49:17 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <78A3A6A4-3718-4468-B198-FDBCDA10CCD3@cisco.com>
References: <C8E76217.2AFBD%john_brzozowski@cable.comcast.com>
To: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 19:47:41 -0000

John - regarding the size of the prefix to request, here is a simple =
example.  We expect Zigbee IP sensor network to connect through a =
dual-interface gateway to the home network and then to the IGD.  The =
sensor network needs a prefix for the 802.15.4 network, but the IGD only =
has a single interface.  How does the IGD know to ask for a prefix =
shorter than /64?  In general, how does the IGD know, a priori, the =
architecture of the residential network so it can ask for an =
appropriately sized prefix?

- Ralph

On Oct 22, 2010, at 3:45 PM 10/22/10, Brzozowski, John wrote:

> On 10/21/10 5:03 AM, "Ole Tr=F8an" <otroan@employees.org> wrote:
>=20
>> John,
>>=20
>> [...]
>>=20
>>>> as more advanced home networks evolve, it is going to be difficult =
for the
>>>> border router to know the number of links that exists or may appear =
in the
>>>> future. the intention with PD was always that the prefix size was a
>>>> contractual matter, not one which is negotiated 'real time'.
>>> [jjmb] Hmmm...RFC3633 is a contract?
>>=20
>> a fax replacement. I'd expect when I buy service from an ISP the =
contract
>> between me and the ISP also includes the size of the prefix I will be =
assigned
>> as well as guarantees about its lifetime.
> [jjmb] as stated in other emails we are dealing with protocols not
> contracts.  Brian stated it well, this is between the subscriber and
> operators, not the IETF.
>>=20
>> currently the hint in 3633 is just a MAY and even then there is only =
text
>> suggesting that the requesting router should include a prefix, to =
hint to the
>> server that it would like to receive the same prefix that was =
presumably
>> previously delegated. WPD-2 in draft-ietf-v6ops-ipv6-cpe-router-07 =
includes a
>> MAY hint to the delegating router about the size it would require and =
WPD-3
>> states it MUST accept a different prefix size.
> [jjmb] operators also have there own requirements, which may vary.  I =
for
> one will be requiring the hint.
>>=20
>> DHCPv6 PD is a mechanism where the control and policy is at the =
DHCPv6 PD
>> server.
>>=20
>> you could write a proposal to strengthen this language, but I would =
posit that
>> the IPv6 CE is in no position to know a priori what size to ask for.
> [jjmb] really?  An IPv6 CPE has no way to determine how many and what =
sort
> of interfaces it is built to support or configure with?  It is not =
aware of
> its configuration which in turn would drive its provisioning request?  =
IMO
> this is most certainly something an IGD can and should be =
programmatically
> aware of specifically when initializing.
>>=20
>>>> mind you, I'm not an operator and I would surely like to understand =
the
>>>> reasons why doing more negotiation would be useful? of course, one =
has to
>>>> expect that every CPE supports a delegation of <=3D/64. are there =
really
>>>> implementations which only supports a single /64? if so, I'd claim =
that's a
>>>> bug and not in line with 3633 nor the basic ipv6 ce router =
requirements
>>>> specification.
>>> [jjmb] having flexibility is a must, making substantial fixed =
decisions this
>>> early can result in complications or even limitations.  I absolutely =
agree
>>> with one of your comments above, home networks will evolve.  As such =
we need
>>> to ensure we have the ability to accommodate the same over time.  An
>>> incremental approach supports this goal.  Yes there are =
implementations that
>>> only support a /64, nothing shorter largely because they physically =
do not
>>> have the need and/or ability to support anything else.  If a device =
has only
>>> one IPv4 LAN and cannot be upgraded to support more (including =
hierarchical
>>> PD) why would this be a bug?  I think we will have to agree to =
disagree, I
>>> do not view this as a bug.  I do think this is inline with RFC3633 =
and the
>>> IPv6 CPE router requirements.  A lot of work has been done over the =
past
>>> couple of years to get some existing routers to be software =
upgradable to
>>> support native IPv6 as such there may be some devices with lesser
>>> capabilities.  Having a minimal level of support for IPv6 is better =
than
>>> none, right?  Finally, there may be a wide range of routers built =
over time
>>> that range in caliber and features.
>>=20
>> I think we are in agreement. I'm certainly not suggesting that e.g. a =
/56 is
>> the only way it can be done. nor that delegations have to be rigid. =
every
>> implementation must support any prefix length thrown at it, with the =
exception
>> of getting a so small address block that it doesn't get a single /64 =
per link.
>>=20
>> I'm just saying that the rfc3633 "hint" may not be very useful; and =
that
>> delegating the absolute minimum address block required may be =
problematic. for
>> example if the CE after a delegation is done determines that it needs =
a larger
>> block, the home network may have to be renumbered.
> [jjmb] if a CE can only support the minimum why is it a problem for it =
to be
> provisioning with the minimum?  If a CE after its initial provisioning =
is
> reconfigured to support additional VLANs renumbering will have to =
occur
> anyway no?
>>=20
>> thinking of DHCP PD as a fax replacement, lets you not have to think =
about all
>> the hard corner cases. ;-)
> [jjmb] I still am not clear to the reference to fax replacement, =
sorry.
>>=20
>> cheers,
>> Ole
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> John Jason Brzozowski
> Comcast Cable
> e) mailto:john_brzozowski@cable.comcast.com
> o) 609-377-6594
> m) 484-962-0060
> w) http://www.comcast6.net
> =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
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From john_brzozowski@cable.comcast.com  Fri Oct 22 12:53:17 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 253303A67B1 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 12:53:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.763
X-Spam-Level: 
X-Spam-Status: No, score=-107.763 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_37=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6j24W43TLoyK for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 12:53:15 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id BE8153A679C for <v6ops@ietf.org>; Fri, 22 Oct 2010 12:53:14 -0700 (PDT)
Received: from ([24.40.55.42]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.101223710; Fri, 22 Oct 2010 15:54:50 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by PACDCEXHUB01.cable.comcast.com ([fe80::d1e7:20b5:9b63:21a6%12]) with mapi id 14.01.0255.000; Fri, 22 Oct 2010 15:54:49 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: Gert Doering <gert@space.net>, james woodyatt <jhw@apple.com>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
Thread-Index: AQHLb7qA2T6t3TrIl0mUPJfZCE79dZNKB0SAgAA+QwCAAKTAgIAAFYsA///1tYCAAM4qgIAAPPyAgACsfomAALlnAA==
Date: Fri, 22 Oct 2010 19:54:48 +0000
Message-ID: <C8E76456.2AFD8%john_brzozowski@cable.comcast.com>
In-Reply-To: <20101022085025.GM32268@Space.Net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <EC5D94194A805F4796AF03F180FB6C50@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 19:53:17 -0000

Gert,

Are you saying you prefer two independent requests?  If I am reading your
mail correctly, it sounds like a right-sized IA_PD that is shorter than a
/64 would still work for you right?  The IGD would have to split the prefix
up and allocate it to the various LAN segments, etc. right?

John

On 10/22/10 4:50 AM, "Gert Doering" <gert@space.net> wrote:

> Hi,
>=20
> On Thu, Oct 21, 2010 at 05:00:52PM -0700, james woodyatt wrote:
>> Perhaps, it would be a good idea to do that anyway.  I could request
>> a /48 for the primary local network and a /64 for the guest network.
>> What do you think?
>=20
> It would break the deployment model we're envisioning for our DSL custome=
rs
> - they get *one* prefix of sufficient size, and the prefix is statically
> provisioned in the radius server.
>=20
> So you'd get the /48 (or /56), and nothing for the second request.
>=20
> Also, even if it would be all allocate dynamically, it would double the
> internal routes on the provider side, which might or might not cause
> extra problems...
>=20
> So if I'm asked, I'd say "try to get a reasonably-sized prefix, use one
> /64 from it for LAN+private network and another /64 for the guest network=
"
>=20
> (btw, I'm quite happy to see this functionality emerge - and hope my olde=
r
> Airport Extreme will eventually get a firmware upgrade to make use of
> it :) )
>=20
> Gert Doering
>         -- NetMaster

=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
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From john_brzozowski@cable.comcast.com  Fri Oct 22 12:56:10 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 344113A6818 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 12:56:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.768
X-Spam-Level: 
X-Spam-Status: No, score=-107.768 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9M1AOeuvJQnl for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 12:56:08 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 4F9303A679C for <v6ops@ietf.org>; Fri, 22 Oct 2010 12:56:08 -0700 (PDT)
Received: from ([24.40.55.40]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.101224555; Fri, 22 Oct 2010 15:57:42 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by pacdcexhub03.cable.comcast.com ([fe80::d1dd:b302:b617:3755%12]) with mapi id 14.01.0255.000; Fri, 22 Oct 2010 15:57:42 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: Ralph Droms <rdroms@cisco.com>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
Thread-Index: ActyIazf2T6t3TrIl0mUPJfZCE79dQAIhAqA//+/WgA=
Date: Fri, 22 Oct 2010 19:57:41 +0000
Message-ID: <C8E76502.2AFDF%john_brzozowski@cable.comcast.com>
In-Reply-To: <78A3A6A4-3718-4468-B198-FDBCDA10CCD3@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <DB8B4674966EBE46A69BDF7C2F0894AB@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 19:56:10 -0000

Ralph,

The IGD in this would have to know about the sensor network to ensure
traffic to it can be routed right?  The IGD at the edge of the customer
premise needs to have some awareness some where no?  Even if the IGD was
issue a /56, it would still have to support some form of hierarchical PD to
provision and enable the sensor network right?

John


On 10/22/10 3:49 PM, "Ralph Droms" <rdroms@cisco.com> wrote:

> John - regarding the size of the prefix to request, here is a simple exam=
ple.
> We expect Zigbee IP sensor network to connect through a dual-interface ga=
teway
> to the home network and then to the IGD.  The sensor network needs a pref=
ix
> for the 802.15.4 network, but the IGD only has a single interface.  How d=
oes
> the IGD know to ask for a prefix shorter than /64?  In general, how does =
the
> IGD know, a priori, the architecture of the residential network so it can=
 ask
> for an appropriately sized prefix?
>=20
> - Ralph
>=20
> On Oct 22, 2010, at 3:45 PM 10/22/10, Brzozowski, John wrote:
>=20
>> On 10/21/10 5:03 AM, "Ole Tr=F8an" <otroan@employees.org> wrote:
>>=20
>>> John,
>>>=20
>>> [...]
>>>=20
>>>>> as more advanced home networks evolve, it is going to be difficult fo=
r the
>>>>> border router to know the number of links that exists or may appear i=
n the
>>>>> future. the intention with PD was always that the prefix size was a
>>>>> contractual matter, not one which is negotiated 'real time'.
>>>> [jjmb] Hmmm...RFC3633 is a contract?
>>>=20
>>> a fax replacement. I'd expect when I buy service from an ISP the contra=
ct
>>> between me and the ISP also includes the size of the prefix I will be
>>> assigned
>>> as well as guarantees about its lifetime.
>> [jjmb] as stated in other emails we are dealing with protocols not
>> contracts.  Brian stated it well, this is between the subscriber and
>> operators, not the IETF.
>>>=20
>>> currently the hint in 3633 is just a MAY and even then there is only te=
xt
>>> suggesting that the requesting router should include a prefix, to hint =
to
>>> the
>>> server that it would like to receive the same prefix that was presumabl=
y
>>> previously delegated. WPD-2 in draft-ietf-v6ops-ipv6-cpe-router-07 incl=
udes
>>> a
>>> MAY hint to the delegating router about the size it would require and W=
PD-3
>>> states it MUST accept a different prefix size.
>> [jjmb] operators also have there own requirements, which may vary.  I fo=
r
>> one will be requiring the hint.
>>>=20
>>> DHCPv6 PD is a mechanism where the control and policy is at the DHCPv6 =
PD
>>> server.
>>>=20
>>> you could write a proposal to strengthen this language, but I would pos=
it
>>> that
>>> the IPv6 CE is in no position to know a priori what size to ask for.
>> [jjmb] really?  An IPv6 CPE has no way to determine how many and what so=
rt
>> of interfaces it is built to support or configure with?  It is not aware=
 of
>> its configuration which in turn would drive its provisioning request?  I=
MO
>> this is most certainly something an IGD can and should be programmatical=
ly
>> aware of specifically when initializing.
>>>=20
>>>>> mind you, I'm not an operator and I would surely like to understand t=
he
>>>>> reasons why doing more negotiation would be useful? of course, one ha=
s to
>>>>> expect that every CPE supports a delegation of <=3D/64. are there rea=
lly
>>>>> implementations which only supports a single /64? if so, I'd claim th=
at's
>>>>> a
>>>>> bug and not in line with 3633 nor the basic ipv6 ce router requiremen=
ts
>>>>> specification.
>>>> [jjmb] having flexibility is a must, making substantial fixed decision=
s
>>>> this
>>>> early can result in complications or even limitations.  I absolutely a=
gree
>>>> with one of your comments above, home networks will evolve.  As such w=
e
>>>> need
>>>> to ensure we have the ability to accommodate the same over time.  An
>>>> incremental approach supports this goal.  Yes there are implementation=
s
>>>> that
>>>> only support a /64, nothing shorter largely because they physically do=
 not
>>>> have the need and/or ability to support anything else.  If a device ha=
s
>>>> only
>>>> one IPv4 LAN and cannot be upgraded to support more (including hierarc=
hical
>>>> PD) why would this be a bug?  I think we will have to agree to disagre=
e, I
>>>> do not view this as a bug.  I do think this is inline with RFC3633 and=
 the
>>>> IPv6 CPE router requirements.  A lot of work has been done over the pa=
st
>>>> couple of years to get some existing routers to be software upgradable=
 to
>>>> support native IPv6 as such there may be some devices with lesser
>>>> capabilities.  Having a minimal level of support for IPv6 is better th=
an
>>>> none, right?  Finally, there may be a wide range of routers built over=
 time
>>>> that range in caliber and features.
>>>=20
>>> I think we are in agreement. I'm certainly not suggesting that e.g. a /=
56 is
>>> the only way it can be done. nor that delegations have to be rigid. eve=
ry
>>> implementation must support any prefix length thrown at it, with the
>>> exception
>>> of getting a so small address block that it doesn't get a single /64 pe=
r
>>> link.
>>>=20
>>> I'm just saying that the rfc3633 "hint" may not be very useful; and tha=
t
>>> delegating the absolute minimum address block required may be problemat=
ic.
>>> for
>>> example if the CE after a delegation is done determines that it needs a
>>> larger
>>> block, the home network may have to be renumbered.
>> [jjmb] if a CE can only support the minimum why is it a problem for it t=
o be
>> provisioning with the minimum?  If a CE after its initial provisioning i=
s
>> reconfigured to support additional VLANs renumbering will have to occur
>> anyway no?
>>>=20
>>> thinking of DHCP PD as a fax replacement, lets you not have to think ab=
out
>>> all
>>> the hard corner cases. ;-)
>> [jjmb] I still am not clear to the reference to fax replacement, sorry.
>>>=20
>>> cheers,
>>> Ole
>>=20
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> John Jason Brzozowski
>> Comcast Cable
>> e) mailto:john_brzozowski@cable.comcast.com
>> o) 609-377-6594
>> m) 484-962-0060
>> w) http://www.comcast6.net
>> =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
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From brian.e.carpenter@gmail.com  Fri Oct 22 13:02:14 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9EF443A6818 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:02:14 -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.265, BAYES_00=-2.599, J_CHICKENPOX_32=0.6, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yb3GmO7nvioV for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:02:14 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id A12F33A679C for <v6ops@ietf.org>; Fri, 22 Oct 2010 13:02:13 -0700 (PDT)
Received: by wyb28 with SMTP id 28so1238241wyb.31 for <v6ops@ietf.org>; Fri, 22 Oct 2010 13:03:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=WDf5u0HHt4VH7elCsohvp+6+Ls0dhAaiEPqUOp+mH/0=; b=H+NWDwouQTq0twDYd522rfjKH5SnqZ4TKn590h57sVw07cqF9GuwY1uDes3A3tDQng NMI+UFr/IwXh8gA3cWgDJjIBMTay+HHZGWDP6dCw3j7/ru7sTVlY/gi3Bzm4iM83SmKP BMG7oS45Xsqwnd3BNsM3nKeqVLSmHMGhqY6og=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=RTidA2LcEBI1cJmvNL+8pE2Fnjj4K6Dp7AfEiPYxcs6bDbIfDOq8W1bO40Gwb+svrQ mRUvWUNpl36nAbDjEfhhe0+uLp/kD9ntL58xcKA1IEvR7pSGtjh0ifjRnJ43PqHD9j2y ef4cjsgEelOrkE1tBntEIKlE2JZ4AKWdP+Brk=
Received: by 10.216.153.140 with SMTP id f12mr11645308wek.111.1287777830788; Fri, 22 Oct 2010 13:03:50 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.142.15]) by mx.google.com with ESMTPS id e56sm2225100wer.46.2010.10.22.13.03.47 (version=SSLv3 cipher=RC4-MD5); Fri, 22 Oct 2010 13:03:50 -0700 (PDT)
Message-ID: <4CC1EE1D.7090703@gmail.com>
Date: Sat, 23 Oct 2010 09:03:41 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ole Troan <ot@cisco.com>
References: <C8E56757.2A817%john_brzozowski@cable.comcast.com> <4CC0A1A2.3060003@gmail.com> <11EA1C19-01B2-46B6-A0EE-6CB760F3482E@cisco.com> <4CC0AABD.6060207@gmail.com> <BF19AF42-62D0-4C9E-BDB2-1AC759881879@cisco.com>
In-Reply-To: <BF19AF42-62D0-4C9E-BDB2-1AC759881879@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 20:02:14 -0000

Ole,

On 2010-10-22 17:32, Ole Troan wrote:
...

>>>> In our protocols, prefix length clearly needs to be a parameter
>>>> (as it is in draft-hu-pppext-ipv6cp-extensions, for example).
>>> so now we are not only going to replicate all functions between DHCPv6 and RA options, but also for IPv6CP? that appears to be a bad idea.
>> Well, there are arguments about why this is needed from an operational viewpoint
>> in draft-hu-pppext-ipv6cp-requirements. I guess they should be discussed
>> on the pppext list.
> 
> so creating two protocols doing exactly the same thing is a good thing?

In general, not. But if an operator is using PPP to establish sessions
with thousand or millions of subscribers, I can well understand that they
don't want to run either SLAAC or DHCPv6 as well as IPV6CP/PPP.
Anyway, as I said, that point needs to be argued in PPPEXT, not here.

    Brian

From rdroms@cisco.com  Fri Oct 22 13:04:40 2010
Return-Path: <rdroms@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 590AE3A679C for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:04:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.544
X-Spam-Level: 
X-Spam-Status: No, score=-9.544 tagged_above=-999 required=5 tests=[AWL=-0.941, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g27hY0n72FV1 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:04:38 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 4AA163A68E2 for <v6ops@ietf.org>; Fri, 22 Oct 2010 13:04:38 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAP+LwUxAZnwN/2dsb2JhbAChFlJxolKcFIMPgjsEik0
X-IronPort-AV: E=Sophos;i="4.58,224,1286150400"; d="scan'208";a="173970923"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 22 Oct 2010 20:06:16 +0000
Received: from bxb-rdroms-8712.cisco.com (bxb-rdroms-8712.cisco.com [10.98.10.83]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o9MK6GCW009630; Fri, 22 Oct 2010 20:06:16 GMT
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: Ralph Droms <rdroms@cisco.com>
In-Reply-To: <C8E76502.2AFDF%john_brzozowski@cable.comcast.com>
Date: Fri, 22 Oct 2010 16:06:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <16D42229-E6D7-4CAA-A35B-743991BDC798@cisco.com>
References: <C8E76502.2AFDF%john_brzozowski@cable.comcast.com>
To: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 20:04:40 -0000

On Oct 22, 2010, at 3:57 PM 10/22/10, Brzozowski, John wrote:

> Ralph,
>=20
> The IGD in this would have to know about the sensor network to ensure
> traffic to it can be routed right?  The IGD at the edge of the =
customer
> premise needs to have some awareness some where no?  Even if the IGD =
was
> issue a /56, it would still have to support some form of hierarchical =
PD to
> provision and enable the sensor network right?
>=20
> John

Yes.

- Ralph

>=20
>=20
> On 10/22/10 3:49 PM, "Ralph Droms" <rdroms@cisco.com> wrote:
>=20
>> John - regarding the size of the prefix to request, here is a simple =
example.
>> We expect Zigbee IP sensor network to connect through a =
dual-interface gateway
>> to the home network and then to the IGD.  The sensor network needs a =
prefix
>> for the 802.15.4 network, but the IGD only has a single interface.  =
How does
>> the IGD know to ask for a prefix shorter than /64?  In general, how =
does the
>> IGD know, a priori, the architecture of the residential network so it =
can ask
>> for an appropriately sized prefix?
>>=20
>> - Ralph
>>=20
>> On Oct 22, 2010, at 3:45 PM 10/22/10, Brzozowski, John wrote:
>>=20
>>> On 10/21/10 5:03 AM, "Ole Tr=F8an" <otroan@employees.org> wrote:
>>>=20
>>>> John,
>>>>=20
>>>> [...]
>>>>=20
>>>>>> as more advanced home networks evolve, it is going to be =
difficult for the
>>>>>> border router to know the number of links that exists or may =
appear in the
>>>>>> future. the intention with PD was always that the prefix size was =
a
>>>>>> contractual matter, not one which is negotiated 'real time'.
>>>>> [jjmb] Hmmm...RFC3633 is a contract?
>>>>=20
>>>> a fax replacement. I'd expect when I buy service from an ISP the =
contract
>>>> between me and the ISP also includes the size of the prefix I will =
be
>>>> assigned
>>>> as well as guarantees about its lifetime.
>>> [jjmb] as stated in other emails we are dealing with protocols not
>>> contracts.  Brian stated it well, this is between the subscriber and
>>> operators, not the IETF.
>>>>=20
>>>> currently the hint in 3633 is just a MAY and even then there is =
only text
>>>> suggesting that the requesting router should include a prefix, to =
hint to
>>>> the
>>>> server that it would like to receive the same prefix that was =
presumably
>>>> previously delegated. WPD-2 in draft-ietf-v6ops-ipv6-cpe-router-07 =
includes
>>>> a
>>>> MAY hint to the delegating router about the size it would require =
and WPD-3
>>>> states it MUST accept a different prefix size.
>>> [jjmb] operators also have there own requirements, which may vary.  =
I for
>>> one will be requiring the hint.
>>>>=20
>>>> DHCPv6 PD is a mechanism where the control and policy is at the =
DHCPv6 PD
>>>> server.
>>>>=20
>>>> you could write a proposal to strengthen this language, but I would =
posit
>>>> that
>>>> the IPv6 CE is in no position to know a priori what size to ask =
for.
>>> [jjmb] really?  An IPv6 CPE has no way to determine how many and =
what sort
>>> of interfaces it is built to support or configure with?  It is not =
aware of
>>> its configuration which in turn would drive its provisioning =
request?  IMO
>>> this is most certainly something an IGD can and should be =
programmatically
>>> aware of specifically when initializing.
>>>>=20
>>>>>> mind you, I'm not an operator and I would surely like to =
understand the
>>>>>> reasons why doing more negotiation would be useful? of course, =
one has to
>>>>>> expect that every CPE supports a delegation of <=3D/64. are there =
really
>>>>>> implementations which only supports a single /64? if so, I'd =
claim that's
>>>>>> a
>>>>>> bug and not in line with 3633 nor the basic ipv6 ce router =
requirements
>>>>>> specification.
>>>>> [jjmb] having flexibility is a must, making substantial fixed =
decisions
>>>>> this
>>>>> early can result in complications or even limitations.  I =
absolutely agree
>>>>> with one of your comments above, home networks will evolve.  As =
such we
>>>>> need
>>>>> to ensure we have the ability to accommodate the same over time.  =
An
>>>>> incremental approach supports this goal.  Yes there are =
implementations
>>>>> that
>>>>> only support a /64, nothing shorter largely because they =
physically do not
>>>>> have the need and/or ability to support anything else.  If a =
device has
>>>>> only
>>>>> one IPv4 LAN and cannot be upgraded to support more (including =
hierarchical
>>>>> PD) why would this be a bug?  I think we will have to agree to =
disagree, I
>>>>> do not view this as a bug.  I do think this is inline with RFC3633 =
and the
>>>>> IPv6 CPE router requirements.  A lot of work has been done over =
the past
>>>>> couple of years to get some existing routers to be software =
upgradable to
>>>>> support native IPv6 as such there may be some devices with lesser
>>>>> capabilities.  Having a minimal level of support for IPv6 is =
better than
>>>>> none, right?  Finally, there may be a wide range of routers built =
over time
>>>>> that range in caliber and features.
>>>>=20
>>>> I think we are in agreement. I'm certainly not suggesting that e.g. =
a /56 is
>>>> the only way it can be done. nor that delegations have to be rigid. =
every
>>>> implementation must support any prefix length thrown at it, with =
the
>>>> exception
>>>> of getting a so small address block that it doesn't get a single =
/64 per
>>>> link.
>>>>=20
>>>> I'm just saying that the rfc3633 "hint" may not be very useful; and =
that
>>>> delegating the absolute minimum address block required may be =
problematic.
>>>> for
>>>> example if the CE after a delegation is done determines that it =
needs a
>>>> larger
>>>> block, the home network may have to be renumbered.
>>> [jjmb] if a CE can only support the minimum why is it a problem for =
it to be
>>> provisioning with the minimum?  If a CE after its initial =
provisioning is
>>> reconfigured to support additional VLANs renumbering will have to =
occur
>>> anyway no?
>>>>=20
>>>> thinking of DHCP PD as a fax replacement, lets you not have to =
think about
>>>> all
>>>> the hard corner cases. ;-)
>>> [jjmb] I still am not clear to the reference to fax replacement, =
sorry.
>>>>=20
>>>> cheers,
>>>> Ole
>>>=20
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>> John Jason Brzozowski
>>> Comcast Cable
>>> e) mailto:john_brzozowski@cable.comcast.com
>>> o) 609-377-6594
>>> m) 484-962-0060
>>> w) http://www.comcast6.net
>>> =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
>>>=20
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>=20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> John Jason Brzozowski
> Comcast Cable
> e) mailto:john_brzozowski@cable.comcast.com
> o) 609-377-6594
> m) 484-962-0060
> w) http://www.comcast6.net
> =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
>=20


From brian.e.carpenter@gmail.com  Fri Oct 22 13:16:47 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 521443A695C for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:16:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.404
X-Spam-Level: 
X-Spam-Status: No, score=-102.404 tagged_above=-999 required=5 tests=[AWL=0.195, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fg6JuQV12lQJ for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:16:30 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 184B33A6979 for <v6ops@ietf.org>; Fri, 22 Oct 2010 13:14:09 -0700 (PDT)
Received: by ewy27 with SMTP id 27so802899ewy.31 for <v6ops@ietf.org>; Fri, 22 Oct 2010 13:15:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=MNTJFgIQ/q9zLFv22qKLIsFAXAONLs39owwcVy6V6rk=; b=efAOcsKkUdurjfcHqSaSOCN4Bwau4+5/9W0rPKqQLeTrTWJDOUXTqpqlvImzd70WwS 92Jc8O5s00BW5HlfrNaL4QHorwSO9FgekkMEM9TI6QJABlw+LSw2usTWreD+5CkWRUvg GjPhgsIkWG/AuhEgXtOifjmv0vb0yl7CVGLlM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=uS8JizQPj6X8ADoIv3X27dIgchsbtu6PvWHK9qSYP7MVhqPhKtTFVi8NNsHOAECqlm ma86NS+19FXkQ6fe54/2HRAJjGV0xL0xEXurUQp8N9yfbF3/2d+ch7LcoCovaBRLyzyC XLZKdpPF1eXLgDos9OpYsPRsZWesgYTJDHTRQ=
Received: by 10.14.48.78 with SMTP id u54mr2685921eeb.27.1287778547900; Fri, 22 Oct 2010 13:15:47 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.142.15]) by mx.google.com with ESMTPS id v56sm3760422eeh.8.2010.10.22.13.15.44 (version=SSLv3 cipher=RC4-MD5); Fri, 22 Oct 2010 13:15:46 -0700 (PDT)
Message-ID: <4CC1F0EA.8090304@gmail.com>
Date: Sat, 23 Oct 2010 09:15:38 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Scott Beuker <Scott.Beuker@sjrb.ca>, Gert Doering <gert@space.net>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr><4CC07295.8000603@gont.com.ar><28A6DE3B-3D4D-45DF-98D3-4B7AFE0E6CF1@free.fr><4CC07EEA.6000306@gont.com.ar>	<44C27CB3-0633-46E4-A919-6351526D0DFA@free.fr> <1EA76BAD7F050648910C041BDDED8CD5013FDBD1@PRDCG4EXVW01-5.OSS.PRD>
In-Reply-To: <1EA76BAD7F050648910C041BDDED8CD5013FDBD1@PRDCG4EXVW01-5.OSS.PRD>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 20:16:47 -0000

On 2010-10-23 03:35, Scott Beuker wrote:
>> The idea is that Teredo and 6to4, which are useful in some identified
>> scenarios but have some lose ends in some others, should be reserved to
>> users that know what they do.
> 
> 
> Exactly the opposite, in my opinion. If you ask the creators of Teredo and 6to4, I think they'll tell you it's intended to catch the users who know nothing of IPv6, and allow the rest of us who do to proceed with the transition to IPv6, without having them hold us back.

I don't know what Christian would say about Teredo, but 6to4 as defined
in RFC 3056 was entirely aimed at consenting adults: a site that wanted
IPv6 access but whose ISP did not provide it, and a remote ISP
that provided IPv6 access and was willing to operate a unicast 6to4
relay.

Unfortunately, RFC 3068 subverted this by endorsing host-based
instead of router-based 6to4, and defining an anycast address for
6to4 relays. That has seen a lot of usage, but does create the
return path problem.

On 2010-10-23 08:04, Gert Doering wrote:

> One approach to rework 3056 would be to completely deprecate the 
> 6to4-with-anycast model.  

That is to say, deprecate RFC 3068 and revert to the pure RFC 3056 model.

Good idea. Could you push my toothpaste back into the tube, too, please ;-)

     Brian

From john_brzozowski@cable.comcast.com  Fri Oct 22 13:17:53 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E85943A6916 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:17:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.773
X-Spam-Level: 
X-Spam-Status: No, score=-107.773 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p0w5VQteLFWT for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:17:50 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 478123A695C for <v6ops@ietf.org>; Fri, 22 Oct 2010 13:16:52 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.101234854; Fri, 22 Oct 2010 16:18:27 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by PACDCEXHUB02.cable.comcast.com ([fe80::11d4:f530:37a0:9f4e%12]) with mapi id 14.01.0255.000; Fri, 22 Oct 2010 16:18:27 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: Ralph Droms <rdroms@cisco.com>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
Thread-Index: ActyIazf2T6t3TrIl0mUPJfZCE79dQAIhAqA//+/WgCAAEVkAP//wGkA
Date: Fri, 22 Oct 2010 20:18:26 +0000
Message-ID: <C8E769E0.2B00C%john_brzozowski@cable.comcast.com>
In-Reply-To: <16D42229-E6D7-4CAA-A35B-743991BDC798@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <E8C0BB03E6D4BF4980ABFA4E19724E89@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 20:17:53 -0000

The IGD has to some degree of awareness to ensure it gets provisioned
appropriately and can in turn support whatever is connected to it within th=
e
premise.


On 10/22/10 4:06 PM, "Ralph Droms" <rdroms@cisco.com> wrote:

>=20
> On Oct 22, 2010, at 3:57 PM 10/22/10, Brzozowski, John wrote:
>=20
>> Ralph,
>>=20
>> The IGD in this would have to know about the sensor network to ensure
>> traffic to it can be routed right?  The IGD at the edge of the customer
>> premise needs to have some awareness some where no?  Even if the IGD was
>> issue a /56, it would still have to support some form of hierarchical PD=
 to
>> provision and enable the sensor network right?
>>=20
>> John
>=20
> Yes.
>=20
> - Ralph
>=20
>>=20
>>=20
>> On 10/22/10 3:49 PM, "Ralph Droms" <rdroms@cisco.com> wrote:
>>=20
>>> John - regarding the size of the prefix to request, here is a simple
>>> example.
>>> We expect Zigbee IP sensor network to connect through a dual-interface
>>> gateway
>>> to the home network and then to the IGD.  The sensor network needs a pr=
efix
>>> for the 802.15.4 network, but the IGD only has a single interface.  How=
 does
>>> the IGD know to ask for a prefix shorter than /64?  In general, how doe=
s the
>>> IGD know, a priori, the architecture of the residential network so it c=
an
>>> ask
>>> for an appropriately sized prefix?
>>>=20
>>> - Ralph
>>>=20
>>> On Oct 22, 2010, at 3:45 PM 10/22/10, Brzozowski, John wrote:
>>>=20
>>>> On 10/21/10 5:03 AM, "Ole Tr=F8an" <otroan@employees.org> wrote:
>>>>=20
>>>>> John,
>>>>>=20
>>>>> [...]
>>>>>=20
>>>>>>> as more advanced home networks evolve, it is going to be difficult =
for
>>>>>>> the
>>>>>>> border router to know the number of links that exists or may appear=
 in
>>>>>>> the
>>>>>>> future. the intention with PD was always that the prefix size was a
>>>>>>> contractual matter, not one which is negotiated 'real time'.
>>>>>> [jjmb] Hmmm...RFC3633 is a contract?
>>>>>=20
>>>>> a fax replacement. I'd expect when I buy service from an ISP the cont=
ract
>>>>> between me and the ISP also includes the size of the prefix I will be
>>>>> assigned
>>>>> as well as guarantees about its lifetime.
>>>> [jjmb] as stated in other emails we are dealing with protocols not
>>>> contracts.  Brian stated it well, this is between the subscriber and
>>>> operators, not the IETF.
>>>>>=20
>>>>> currently the hint in 3633 is just a MAY and even then there is only =
text
>>>>> suggesting that the requesting router should include a prefix, to hin=
t to
>>>>> the
>>>>> server that it would like to receive the same prefix that was presuma=
bly
>>>>> previously delegated. WPD-2 in draft-ietf-v6ops-ipv6-cpe-router-07
>>>>> includes
>>>>> a
>>>>> MAY hint to the delegating router about the size it would require and
>>>>> WPD-3
>>>>> states it MUST accept a different prefix size.
>>>> [jjmb] operators also have there own requirements, which may vary.  I =
for
>>>> one will be requiring the hint.
>>>>>=20
>>>>> DHCPv6 PD is a mechanism where the control and policy is at the DHCPv=
6 PD
>>>>> server.
>>>>>=20
>>>>> you could write a proposal to strengthen this language, but I would p=
osit
>>>>> that
>>>>> the IPv6 CE is in no position to know a priori what size to ask for.
>>>> [jjmb] really?  An IPv6 CPE has no way to determine how many and what =
sort
>>>> of interfaces it is built to support or configure with?  It is not awa=
re of
>>>> its configuration which in turn would drive its provisioning request? =
 IMO
>>>> this is most certainly something an IGD can and should be programmatic=
ally
>>>> aware of specifically when initializing.
>>>>>=20
>>>>>>> mind you, I'm not an operator and I would surely like to understand=
 the
>>>>>>> reasons why doing more negotiation would be useful? of course, one =
has
>>>>>>> to
>>>>>>> expect that every CPE supports a delegation of <=3D/64. are there r=
eally
>>>>>>> implementations which only supports a single /64? if so, I'd claim
>>>>>>> that's
>>>>>>> a
>>>>>>> bug and not in line with 3633 nor the basic ipv6 ce router requirem=
ents
>>>>>>> specification.
>>>>>> [jjmb] having flexibility is a must, making substantial fixed decisi=
ons
>>>>>> this
>>>>>> early can result in complications or even limitations.  I absolutely
>>>>>> agree
>>>>>> with one of your comments above, home networks will evolve.  As such=
 we
>>>>>> need
>>>>>> to ensure we have the ability to accommodate the same over time.  An
>>>>>> incremental approach supports this goal.  Yes there are implementati=
ons
>>>>>> that
>>>>>> only support a /64, nothing shorter largely because they physically =
do
>>>>>> not
>>>>>> have the need and/or ability to support anything else.  If a device =
has
>>>>>> only
>>>>>> one IPv4 LAN and cannot be upgraded to support more (including
>>>>>> hierarchical
>>>>>> PD) why would this be a bug?  I think we will have to agree to disag=
ree,
>>>>>> I
>>>>>> do not view this as a bug.  I do think this is inline with RFC3633 a=
nd
>>>>>> the
>>>>>> IPv6 CPE router requirements.  A lot of work has been done over the =
past
>>>>>> couple of years to get some existing routers to be software upgradab=
le to
>>>>>> support native IPv6 as such there may be some devices with lesser
>>>>>> capabilities.  Having a minimal level of support for IPv6 is better =
than
>>>>>> none, right?  Finally, there may be a wide range of routers built ov=
er
>>>>>> time
>>>>>> that range in caliber and features.
>>>>>=20
>>>>> I think we are in agreement. I'm certainly not suggesting that e.g. a=
 /56
>>>>> is
>>>>> the only way it can be done. nor that delegations have to be rigid. e=
very
>>>>> implementation must support any prefix length thrown at it, with the
>>>>> exception
>>>>> of getting a so small address block that it doesn't get a single /64 =
per
>>>>> link.
>>>>>=20
>>>>> I'm just saying that the rfc3633 "hint" may not be very useful; and t=
hat
>>>>> delegating the absolute minimum address block required may be problem=
atic.
>>>>> for
>>>>> example if the CE after a delegation is done determines that it needs=
 a
>>>>> larger
>>>>> block, the home network may have to be renumbered.
>>>> [jjmb] if a CE can only support the minimum why is it a problem for it=
 to
>>>> be
>>>> provisioning with the minimum?  If a CE after its initial provisioning=
 is
>>>> reconfigured to support additional VLANs renumbering will have to occu=
r
>>>> anyway no?
>>>>>=20
>>>>> thinking of DHCP PD as a fax replacement, lets you not have to think =
about
>>>>> all
>>>>> the hard corner cases. ;-)
>>>> [jjmb] I still am not clear to the reference to fax replacement, sorry=
.
>>>>>=20
>>>>> cheers,
>>>>> Ole
>>>>=20
>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>> John Jason Brzozowski
>>>> Comcast Cable
>>>> e) mailto:john_brzozowski@cable.comcast.com
>>>> o) 609-377-6594
>>>> m) 484-962-0060
>>>> w) http://www.comcast6.net
>>>> =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
>>>>=20
>>>> _______________________________________________
>>>> v6ops mailing list
>>>> v6ops@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>=20
>>=20
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> John Jason Brzozowski
>> Comcast Cable
>> e) mailto:john_brzozowski@cable.comcast.com
>> o) 609-377-6594
>> m) 484-962-0060
>> w) http://www.comcast6.net
>> =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
>>=20
>=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From rdroms@cisco.com  Fri Oct 22 13:19:06 2010
Return-Path: <rdroms@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 57C583A67E4 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:19:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.501
X-Spam-Level: 
X-Spam-Status: No, score=-9.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, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kb3bMtmhk0qf for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:19:04 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 6B40E3A679C for <v6ops@ietf.org>; Fri, 22 Oct 2010 13:19:04 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.58,225,1286150400"; d="scan'208";a="173766905"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 22 Oct 2010 20:20:42 +0000
Received: from bxb-rdroms-8712.cisco.com (bxb-rdroms-8712.cisco.com [10.98.10.83]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o9MKKgYs029625; Fri, 22 Oct 2010 20:20:42 GMT
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: Ralph Droms <rdroms@cisco.com>
In-Reply-To: <C8E769E0.2B00C%john_brzozowski@cable.comcast.com>
Date: Fri, 22 Oct 2010 16:20:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DE7AE48C-76C8-4D1E-946B-43CD520FD86C@cisco.com>
References: <C8E769E0.2B00C%john_brzozowski@cable.comcast.com>
To: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 20:19:06 -0000

Just because the IGD has the capability to do hierarchical PD doesn't =
mean it knows how many prefixes to ask for.

- Ralph

On Oct 22, 2010, at 4:18 PM 10/22/10, Brzozowski, John wrote:

> The IGD has to some degree of awareness to ensure it gets provisioned
> appropriately and can in turn support whatever is connected to it =
within the
> premise.
>=20
>=20
> On 10/22/10 4:06 PM, "Ralph Droms" <rdroms@cisco.com> wrote:
>=20
>>=20
>> On Oct 22, 2010, at 3:57 PM 10/22/10, Brzozowski, John wrote:
>>=20
>>> Ralph,
>>>=20
>>> The IGD in this would have to know about the sensor network to =
ensure
>>> traffic to it can be routed right?  The IGD at the edge of the =
customer
>>> premise needs to have some awareness some where no?  Even if the IGD =
was
>>> issue a /56, it would still have to support some form of =
hierarchical PD to
>>> provision and enable the sensor network right?
>>>=20
>>> John
>>=20
>> Yes.
>>=20
>> - Ralph
>>=20
>>>=20
>>>=20
>>> On 10/22/10 3:49 PM, "Ralph Droms" <rdroms@cisco.com> wrote:
>>>=20
>>>> John - regarding the size of the prefix to request, here is a =
simple
>>>> example.
>>>> We expect Zigbee IP sensor network to connect through a =
dual-interface
>>>> gateway
>>>> to the home network and then to the IGD.  The sensor network needs =
a prefix
>>>> for the 802.15.4 network, but the IGD only has a single interface.  =
How does
>>>> the IGD know to ask for a prefix shorter than /64?  In general, how =
does the
>>>> IGD know, a priori, the architecture of the residential network so =
it can
>>>> ask
>>>> for an appropriately sized prefix?
>>>>=20
>>>> - Ralph
>>>>=20
>>>> On Oct 22, 2010, at 3:45 PM 10/22/10, Brzozowski, John wrote:
>>>>=20
>>>>> On 10/21/10 5:03 AM, "Ole Tr=F8an" <otroan@employees.org> wrote:
>>>>>=20
>>>>>> John,
>>>>>>=20
>>>>>> [...]
>>>>>>=20
>>>>>>>> as more advanced home networks evolve, it is going to be =
difficult for
>>>>>>>> the
>>>>>>>> border router to know the number of links that exists or may =
appear in
>>>>>>>> the
>>>>>>>> future. the intention with PD was always that the prefix size =
was a
>>>>>>>> contractual matter, not one which is negotiated 'real time'.
>>>>>>> [jjmb] Hmmm...RFC3633 is a contract?
>>>>>>=20
>>>>>> a fax replacement. I'd expect when I buy service from an ISP the =
contract
>>>>>> between me and the ISP also includes the size of the prefix I =
will be
>>>>>> assigned
>>>>>> as well as guarantees about its lifetime.
>>>>> [jjmb] as stated in other emails we are dealing with protocols not
>>>>> contracts.  Brian stated it well, this is between the subscriber =
and
>>>>> operators, not the IETF.
>>>>>>=20
>>>>>> currently the hint in 3633 is just a MAY and even then there is =
only text
>>>>>> suggesting that the requesting router should include a prefix, to =
hint to
>>>>>> the
>>>>>> server that it would like to receive the same prefix that was =
presumably
>>>>>> previously delegated. WPD-2 in =
draft-ietf-v6ops-ipv6-cpe-router-07
>>>>>> includes
>>>>>> a
>>>>>> MAY hint to the delegating router about the size it would require =
and
>>>>>> WPD-3
>>>>>> states it MUST accept a different prefix size.
>>>>> [jjmb] operators also have there own requirements, which may vary. =
 I for
>>>>> one will be requiring the hint.
>>>>>>=20
>>>>>> DHCPv6 PD is a mechanism where the control and policy is at the =
DHCPv6 PD
>>>>>> server.
>>>>>>=20
>>>>>> you could write a proposal to strengthen this language, but I =
would posit
>>>>>> that
>>>>>> the IPv6 CE is in no position to know a priori what size to ask =
for.
>>>>> [jjmb] really?  An IPv6 CPE has no way to determine how many and =
what sort
>>>>> of interfaces it is built to support or configure with?  It is not =
aware of
>>>>> its configuration which in turn would drive its provisioning =
request?  IMO
>>>>> this is most certainly something an IGD can and should be =
programmatically
>>>>> aware of specifically when initializing.
>>>>>>=20
>>>>>>>> mind you, I'm not an operator and I would surely like to =
understand the
>>>>>>>> reasons why doing more negotiation would be useful? of course, =
one has
>>>>>>>> to
>>>>>>>> expect that every CPE supports a delegation of <=3D/64. are =
there really
>>>>>>>> implementations which only supports a single /64? if so, I'd =
claim
>>>>>>>> that's
>>>>>>>> a
>>>>>>>> bug and not in line with 3633 nor the basic ipv6 ce router =
requirements
>>>>>>>> specification.
>>>>>>> [jjmb] having flexibility is a must, making substantial fixed =
decisions
>>>>>>> this
>>>>>>> early can result in complications or even limitations.  I =
absolutely
>>>>>>> agree
>>>>>>> with one of your comments above, home networks will evolve.  As =
such we
>>>>>>> need
>>>>>>> to ensure we have the ability to accommodate the same over time. =
 An
>>>>>>> incremental approach supports this goal.  Yes there are =
implementations
>>>>>>> that
>>>>>>> only support a /64, nothing shorter largely because they =
physically do
>>>>>>> not
>>>>>>> have the need and/or ability to support anything else.  If a =
device has
>>>>>>> only
>>>>>>> one IPv4 LAN and cannot be upgraded to support more (including
>>>>>>> hierarchical
>>>>>>> PD) why would this be a bug?  I think we will have to agree to =
disagree,
>>>>>>> I
>>>>>>> do not view this as a bug.  I do think this is inline with =
RFC3633 and
>>>>>>> the
>>>>>>> IPv6 CPE router requirements.  A lot of work has been done over =
the past
>>>>>>> couple of years to get some existing routers to be software =
upgradable to
>>>>>>> support native IPv6 as such there may be some devices with =
lesser
>>>>>>> capabilities.  Having a minimal level of support for IPv6 is =
better than
>>>>>>> none, right?  Finally, there may be a wide range of routers =
built over
>>>>>>> time
>>>>>>> that range in caliber and features.
>>>>>>=20
>>>>>> I think we are in agreement. I'm certainly not suggesting that =
e.g. a /56
>>>>>> is
>>>>>> the only way it can be done. nor that delegations have to be =
rigid. every
>>>>>> implementation must support any prefix length thrown at it, with =
the
>>>>>> exception
>>>>>> of getting a so small address block that it doesn't get a single =
/64 per
>>>>>> link.
>>>>>>=20
>>>>>> I'm just saying that the rfc3633 "hint" may not be very useful; =
and that
>>>>>> delegating the absolute minimum address block required may be =
problematic.
>>>>>> for
>>>>>> example if the CE after a delegation is done determines that it =
needs a
>>>>>> larger
>>>>>> block, the home network may have to be renumbered.
>>>>> [jjmb] if a CE can only support the minimum why is it a problem =
for it to
>>>>> be
>>>>> provisioning with the minimum?  If a CE after its initial =
provisioning is
>>>>> reconfigured to support additional VLANs renumbering will have to =
occur
>>>>> anyway no?
>>>>>>=20
>>>>>> thinking of DHCP PD as a fax replacement, lets you not have to =
think about
>>>>>> all
>>>>>> the hard corner cases. ;-)
>>>>> [jjmb] I still am not clear to the reference to fax replacement, =
sorry.
>>>>>>=20
>>>>>> cheers,
>>>>>> Ole
>>>>>=20
>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>>> John Jason Brzozowski
>>>>> Comcast Cable
>>>>> e) mailto:john_brzozowski@cable.comcast.com
>>>>> o) 609-377-6594
>>>>> m) 484-962-0060
>>>>> w) http://www.comcast6.net
>>>>> =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
>>>>>=20
>>>>> _______________________________________________
>>>>> v6ops mailing list
>>>>> v6ops@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>>=20
>>>=20
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>> John Jason Brzozowski
>>> Comcast Cable
>>> e) mailto:john_brzozowski@cable.comcast.com
>>> o) 609-377-6594
>>> m) 484-962-0060
>>> w) http://www.comcast6.net
>>> =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
>>>=20
>>=20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> John Jason Brzozowski
> Comcast Cable
> e) mailto:john_brzozowski@cable.comcast.com
> o) 609-377-6594
> m) 484-962-0060
> w) http://www.comcast6.net
> =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
>=20


From john_brzozowski@cable.comcast.com  Fri Oct 22 13:24:51 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 90DD53A6888 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:24:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.777
X-Spam-Level: 
X-Spam-Status: No, score=-107.777 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r72pgqyubz9Z for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:24:50 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id B4B5D3A679C for <v6ops@ietf.org>; Fri, 22 Oct 2010 13:24:49 -0700 (PDT)
Received: from ([24.40.55.42]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.101237438; Fri, 22 Oct 2010 16:26:23 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by PACDCEXHUB01.cable.comcast.com ([fe80::d1e7:20b5:9b63:21a6%12]) with mapi id 14.01.0255.000; Fri, 22 Oct 2010 16:26:17 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: Ralph Droms <rdroms@cisco.com>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
Thread-Index: ActyIazf2T6t3TrIl0mUPJfZCE79dQAIhAqA//+/WgCAAEVkAP//wGkAgABDoAD//76MAA==
Date: Fri, 22 Oct 2010 20:26:15 +0000
Message-ID: <C8E76BB2.2B026%john_brzozowski@cable.comcast.com>
In-Reply-To: <DE7AE48C-76C8-4D1E-946B-43CD520FD86C@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <CDB97D57F809734BA17F0DF2FC84C59F@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 20:24:51 -0000

Provisioning large blocks across the board may not reliably work either.

Perhaps the IGD should simply relay downstream IA_PD requests from within
the premise and let the other RRs negotiate their own prefix requests with
the operator DHCPv6 servers?

John

On 10/22/10 4:20 PM, "Ralph Droms" <rdroms@cisco.com> wrote:

> Just because the IGD has the capability to do hierarchical PD doesn't mea=
n it
> knows how many prefixes to ask for.
>=20
> - Ralph
>=20
> On Oct 22, 2010, at 4:18 PM 10/22/10, Brzozowski, John wrote:
>=20
>> The IGD has to some degree of awareness to ensure it gets provisioned
>> appropriately and can in turn support whatever is connected to it within=
 the
>> premise.
>>=20
>>=20
>> On 10/22/10 4:06 PM, "Ralph Droms" <rdroms@cisco.com> wrote:
>>=20
>>>=20
>>> On Oct 22, 2010, at 3:57 PM 10/22/10, Brzozowski, John wrote:
>>>=20
>>>> Ralph,
>>>>=20
>>>> The IGD in this would have to know about the sensor network to ensure
>>>> traffic to it can be routed right?  The IGD at the edge of the custome=
r
>>>> premise needs to have some awareness some where no?  Even if the IGD w=
as
>>>> issue a /56, it would still have to support some form of hierarchical =
PD to
>>>> provision and enable the sensor network right?
>>>>=20
>>>> John
>>>=20
>>> Yes.
>>>=20
>>> - Ralph
>>>=20
>>>>=20
>>>>=20
>>>> On 10/22/10 3:49 PM, "Ralph Droms" <rdroms@cisco.com> wrote:
>>>>=20
>>>>> John - regarding the size of the prefix to request, here is a simple
>>>>> example.
>>>>> We expect Zigbee IP sensor network to connect through a dual-interfac=
e
>>>>> gateway
>>>>> to the home network and then to the IGD.  The sensor network needs a
>>>>> prefix
>>>>> for the 802.15.4 network, but the IGD only has a single interface.  H=
ow
>>>>> does
>>>>> the IGD know to ask for a prefix shorter than /64?  In general, how d=
oes
>>>>> the
>>>>> IGD know, a priori, the architecture of the residential network so it=
 can
>>>>> ask
>>>>> for an appropriately sized prefix?
>>>>>=20
>>>>> - Ralph
>>>>>=20
>>>>> On Oct 22, 2010, at 3:45 PM 10/22/10, Brzozowski, John wrote:
>>>>>=20
>>>>>> On 10/21/10 5:03 AM, "Ole Tr=F8an" <otroan@employees.org> wrote:
>>>>>>=20
>>>>>>> John,
>>>>>>>=20
>>>>>>> [...]
>>>>>>>=20
>>>>>>>>> as more advanced home networks evolve, it is going to be difficul=
t for
>>>>>>>>> the
>>>>>>>>> border router to know the number of links that exists or may appe=
ar in
>>>>>>>>> the
>>>>>>>>> future. the intention with PD was always that the prefix size was=
 a
>>>>>>>>> contractual matter, not one which is negotiated 'real time'.
>>>>>>>> [jjmb] Hmmm...RFC3633 is a contract?
>>>>>>>=20
>>>>>>> a fax replacement. I'd expect when I buy service from an ISP the
>>>>>>> contract
>>>>>>> between me and the ISP also includes the size of the prefix I will =
be
>>>>>>> assigned
>>>>>>> as well as guarantees about its lifetime.
>>>>>> [jjmb] as stated in other emails we are dealing with protocols not
>>>>>> contracts.  Brian stated it well, this is between the subscriber and
>>>>>> operators, not the IETF.
>>>>>>>=20
>>>>>>> currently the hint in 3633 is just a MAY and even then there is onl=
y
>>>>>>> text
>>>>>>> suggesting that the requesting router should include a prefix, to h=
int
>>>>>>> to
>>>>>>> the
>>>>>>> server that it would like to receive the same prefix that was presu=
mably
>>>>>>> previously delegated. WPD-2 in draft-ietf-v6ops-ipv6-cpe-router-07
>>>>>>> includes
>>>>>>> a
>>>>>>> MAY hint to the delegating router about the size it would require a=
nd
>>>>>>> WPD-3
>>>>>>> states it MUST accept a different prefix size.
>>>>>> [jjmb] operators also have there own requirements, which may vary.  =
I for
>>>>>> one will be requiring the hint.
>>>>>>>=20
>>>>>>> DHCPv6 PD is a mechanism where the control and policy is at the DHC=
Pv6
>>>>>>> PD
>>>>>>> server.
>>>>>>>=20
>>>>>>> you could write a proposal to strengthen this language, but I would
>>>>>>> posit
>>>>>>> that
>>>>>>> the IPv6 CE is in no position to know a priori what size to ask for=
.
>>>>>> [jjmb] really?  An IPv6 CPE has no way to determine how many and wha=
t
>>>>>> sort
>>>>>> of interfaces it is built to support or configure with?  It is not a=
ware
>>>>>> of
>>>>>> its configuration which in turn would drive its provisioning request=
?
>>>>>> IMO
>>>>>> this is most certainly something an IGD can and should be
>>>>>> programmatically
>>>>>> aware of specifically when initializing.
>>>>>>>=20
>>>>>>>>> mind you, I'm not an operator and I would surely like to understa=
nd
>>>>>>>>> the
>>>>>>>>> reasons why doing more negotiation would be useful? of course, on=
e has
>>>>>>>>> to
>>>>>>>>> expect that every CPE supports a delegation of <=3D/64. are there=
 really
>>>>>>>>> implementations which only supports a single /64? if so, I'd clai=
m
>>>>>>>>> that's
>>>>>>>>> a
>>>>>>>>> bug and not in line with 3633 nor the basic ipv6 ce router
>>>>>>>>> requirements
>>>>>>>>> specification.
>>>>>>>> [jjmb] having flexibility is a must, making substantial fixed deci=
sions
>>>>>>>> this
>>>>>>>> early can result in complications or even limitations.  I absolute=
ly
>>>>>>>> agree
>>>>>>>> with one of your comments above, home networks will evolve.  As su=
ch we
>>>>>>>> need
>>>>>>>> to ensure we have the ability to accommodate the same over time.  =
An
>>>>>>>> incremental approach supports this goal.  Yes there are implementa=
tions
>>>>>>>> that
>>>>>>>> only support a /64, nothing shorter largely because they physicall=
y do
>>>>>>>> not
>>>>>>>> have the need and/or ability to support anything else.  If a devic=
e has
>>>>>>>> only
>>>>>>>> one IPv4 LAN and cannot be upgraded to support more (including
>>>>>>>> hierarchical
>>>>>>>> PD) why would this be a bug?  I think we will have to agree to
>>>>>>>> disagree,
>>>>>>>> I
>>>>>>>> do not view this as a bug.  I do think this is inline with RFC3633=
 and
>>>>>>>> the
>>>>>>>> IPv6 CPE router requirements.  A lot of work has been done over th=
e
>>>>>>>> past
>>>>>>>> couple of years to get some existing routers to be software upgrad=
able
>>>>>>>> to
>>>>>>>> support native IPv6 as such there may be some devices with lesser
>>>>>>>> capabilities.  Having a minimal level of support for IPv6 is bette=
r
>>>>>>>> than
>>>>>>>> none, right?  Finally, there may be a wide range of routers built =
over
>>>>>>>> time
>>>>>>>> that range in caliber and features.
>>>>>>>=20
>>>>>>> I think we are in agreement. I'm certainly not suggesting that e.g.=
 a
>>>>>>> /56
>>>>>>> is
>>>>>>> the only way it can be done. nor that delegations have to be rigid.
>>>>>>> every
>>>>>>> implementation must support any prefix length thrown at it, with th=
e
>>>>>>> exception
>>>>>>> of getting a so small address block that it doesn't get a single /6=
4 per
>>>>>>> link.
>>>>>>>=20
>>>>>>> I'm just saying that the rfc3633 "hint" may not be very useful; and=
 that
>>>>>>> delegating the absolute minimum address block required may be
>>>>>>> problematic.
>>>>>>> for
>>>>>>> example if the CE after a delegation is done determines that it nee=
ds a
>>>>>>> larger
>>>>>>> block, the home network may have to be renumbered.
>>>>>> [jjmb] if a CE can only support the minimum why is it a problem for =
it to
>>>>>> be
>>>>>> provisioning with the minimum?  If a CE after its initial provisioni=
ng is
>>>>>> reconfigured to support additional VLANs renumbering will have to oc=
cur
>>>>>> anyway no?
>>>>>>>=20
>>>>>>> thinking of DHCP PD as a fax replacement, lets you not have to thin=
k
>>>>>>> about
>>>>>>> all
>>>>>>> the hard corner cases. ;-)
>>>>>> [jjmb] I still am not clear to the reference to fax replacement, sor=
ry.
>>>>>>>=20
>>>>>>> cheers,
>>>>>>> Ole
>>>>>>=20
>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>>>> John Jason Brzozowski
>>>>>> Comcast Cable
>>>>>> e) mailto:john_brzozowski@cable.comcast.com
>>>>>> o) 609-377-6594
>>>>>> m) 484-962-0060
>>>>>> w) http://www.comcast6.net
>>>>>> =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
>>>>>>=20
>>>>>> _______________________________________________
>>>>>> v6ops mailing list
>>>>>> v6ops@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>>>=20
>>>>=20
>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>> John Jason Brzozowski
>>>> Comcast Cable
>>>> e) mailto:john_brzozowski@cable.comcast.com
>>>> o) 609-377-6594
>>>> m) 484-962-0060
>>>> w) http://www.comcast6.net
>>>> =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
>>>>=20
>>>=20
>>=20
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> John Jason Brzozowski
>> Comcast Cable
>> e) mailto:john_brzozowski@cable.comcast.com
>> o) 609-377-6594
>> m) 484-962-0060
>> w) http://www.comcast6.net
>> =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
>>=20
>=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From rdroms@cisco.com  Fri Oct 22 13:26:26 2010
Return-Path: <rdroms@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB3B83A6900 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:26:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.462
X-Spam-Level: 
X-Spam-Status: No, score=-9.462 tagged_above=-999 required=5 tests=[AWL=-0.859, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kz0TOUf3z1I0 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:26:22 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 389163A68C5 for <v6ops@ietf.org>; Fri, 22 Oct 2010 13:26:22 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.58,225,1286150400"; d="scan'208";a="173768655"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 22 Oct 2010 20:28:00 +0000
Received: from bxb-rdroms-8712.cisco.com (bxb-rdroms-8712.cisco.com [10.98.10.83]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o9MKS0Z0015557; Fri, 22 Oct 2010 20:28:00 GMT
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: Ralph Droms <rdroms@cisco.com>
In-Reply-To: <C8E76BB2.2B026%john_brzozowski@cable.comcast.com>
Date: Fri, 22 Oct 2010 16:28:00 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2BEBDF09-12FD-410F-A292-D54712F9CAA2@cisco.com>
References: <C8E76BB2.2B026%john_brzozowski@cable.comcast.com>
To: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 20:26:26 -0000

Doesn't seem like that will scale very well if there are more than a =
couple of routers in the home network.

But what do I know?  I'm not an SP network operator.

- Ralph


On Oct 22, 2010, at 4:26 PM 10/22/10, Brzozowski, John wrote:

> Provisioning large blocks across the board may not reliably work =
either.
>=20
> Perhaps the IGD should simply relay downstream IA_PD requests from =
within
> the premise and let the other RRs negotiate their own prefix requests =
with
> the operator DHCPv6 servers?
>=20
> John
>=20
> On 10/22/10 4:20 PM, "Ralph Droms" <rdroms@cisco.com> wrote:
>=20
>> Just because the IGD has the capability to do hierarchical PD doesn't =
mean it
>> knows how many prefixes to ask for.
>>=20
>> - Ralph
>>=20
>> On Oct 22, 2010, at 4:18 PM 10/22/10, Brzozowski, John wrote:
>>=20
>>> The IGD has to some degree of awareness to ensure it gets =
provisioned
>>> appropriately and can in turn support whatever is connected to it =
within the
>>> premise.
>>>=20
>>>=20
>>> On 10/22/10 4:06 PM, "Ralph Droms" <rdroms@cisco.com> wrote:
>>>=20
>>>>=20
>>>> On Oct 22, 2010, at 3:57 PM 10/22/10, Brzozowski, John wrote:
>>>>=20
>>>>> Ralph,
>>>>>=20
>>>>> The IGD in this would have to know about the sensor network to =
ensure
>>>>> traffic to it can be routed right?  The IGD at the edge of the =
customer
>>>>> premise needs to have some awareness some where no?  Even if the =
IGD was
>>>>> issue a /56, it would still have to support some form of =
hierarchical PD to
>>>>> provision and enable the sensor network right?
>>>>>=20
>>>>> John
>>>>=20
>>>> Yes.
>>>>=20
>>>> - Ralph
>>>>=20
>>>>>=20
>>>>>=20
>>>>> On 10/22/10 3:49 PM, "Ralph Droms" <rdroms@cisco.com> wrote:
>>>>>=20
>>>>>> John - regarding the size of the prefix to request, here is a =
simple
>>>>>> example.
>>>>>> We expect Zigbee IP sensor network to connect through a =
dual-interface
>>>>>> gateway
>>>>>> to the home network and then to the IGD.  The sensor network =
needs a
>>>>>> prefix
>>>>>> for the 802.15.4 network, but the IGD only has a single =
interface.  How
>>>>>> does
>>>>>> the IGD know to ask for a prefix shorter than /64?  In general, =
how does
>>>>>> the
>>>>>> IGD know, a priori, the architecture of the residential network =
so it can
>>>>>> ask
>>>>>> for an appropriately sized prefix?
>>>>>>=20
>>>>>> - Ralph
>>>>>>=20
>>>>>> On Oct 22, 2010, at 3:45 PM 10/22/10, Brzozowski, John wrote:
>>>>>>=20
>>>>>>> On 10/21/10 5:03 AM, "Ole Tr=F8an" <otroan@employees.org> wrote:
>>>>>>>=20
>>>>>>>> John,
>>>>>>>>=20
>>>>>>>> [...]
>>>>>>>>=20
>>>>>>>>>> as more advanced home networks evolve, it is going to be =
difficult for
>>>>>>>>>> the
>>>>>>>>>> border router to know the number of links that exists or may =
appear in
>>>>>>>>>> the
>>>>>>>>>> future. the intention with PD was always that the prefix size =
was a
>>>>>>>>>> contractual matter, not one which is negotiated 'real time'.
>>>>>>>>> [jjmb] Hmmm...RFC3633 is a contract?
>>>>>>>>=20
>>>>>>>> a fax replacement. I'd expect when I buy service from an ISP =
the
>>>>>>>> contract
>>>>>>>> between me and the ISP also includes the size of the prefix I =
will be
>>>>>>>> assigned
>>>>>>>> as well as guarantees about its lifetime.
>>>>>>> [jjmb] as stated in other emails we are dealing with protocols =
not
>>>>>>> contracts.  Brian stated it well, this is between the subscriber =
and
>>>>>>> operators, not the IETF.
>>>>>>>>=20
>>>>>>>> currently the hint in 3633 is just a MAY and even then there is =
only
>>>>>>>> text
>>>>>>>> suggesting that the requesting router should include a prefix, =
to hint
>>>>>>>> to
>>>>>>>> the
>>>>>>>> server that it would like to receive the same prefix that was =
presumably
>>>>>>>> previously delegated. WPD-2 in =
draft-ietf-v6ops-ipv6-cpe-router-07
>>>>>>>> includes
>>>>>>>> a
>>>>>>>> MAY hint to the delegating router about the size it would =
require and
>>>>>>>> WPD-3
>>>>>>>> states it MUST accept a different prefix size.
>>>>>>> [jjmb] operators also have there own requirements, which may =
vary.  I for
>>>>>>> one will be requiring the hint.
>>>>>>>>=20
>>>>>>>> DHCPv6 PD is a mechanism where the control and policy is at the =
DHCPv6
>>>>>>>> PD
>>>>>>>> server.
>>>>>>>>=20
>>>>>>>> you could write a proposal to strengthen this language, but I =
would
>>>>>>>> posit
>>>>>>>> that
>>>>>>>> the IPv6 CE is in no position to know a priori what size to ask =
for.
>>>>>>> [jjmb] really?  An IPv6 CPE has no way to determine how many and =
what
>>>>>>> sort
>>>>>>> of interfaces it is built to support or configure with?  It is =
not aware
>>>>>>> of
>>>>>>> its configuration which in turn would drive its provisioning =
request?
>>>>>>> IMO
>>>>>>> this is most certainly something an IGD can and should be
>>>>>>> programmatically
>>>>>>> aware of specifically when initializing.
>>>>>>>>=20
>>>>>>>>>> mind you, I'm not an operator and I would surely like to =
understand
>>>>>>>>>> the
>>>>>>>>>> reasons why doing more negotiation would be useful? of =
course, one has
>>>>>>>>>> to
>>>>>>>>>> expect that every CPE supports a delegation of <=3D/64. are =
there really
>>>>>>>>>> implementations which only supports a single /64? if so, I'd =
claim
>>>>>>>>>> that's
>>>>>>>>>> a
>>>>>>>>>> bug and not in line with 3633 nor the basic ipv6 ce router
>>>>>>>>>> requirements
>>>>>>>>>> specification.
>>>>>>>>> [jjmb] having flexibility is a must, making substantial fixed =
decisions
>>>>>>>>> this
>>>>>>>>> early can result in complications or even limitations.  I =
absolutely
>>>>>>>>> agree
>>>>>>>>> with one of your comments above, home networks will evolve.  =
As such we
>>>>>>>>> need
>>>>>>>>> to ensure we have the ability to accommodate the same over =
time.  An
>>>>>>>>> incremental approach supports this goal.  Yes there are =
implementations
>>>>>>>>> that
>>>>>>>>> only support a /64, nothing shorter largely because they =
physically do
>>>>>>>>> not
>>>>>>>>> have the need and/or ability to support anything else.  If a =
device has
>>>>>>>>> only
>>>>>>>>> one IPv4 LAN and cannot be upgraded to support more (including
>>>>>>>>> hierarchical
>>>>>>>>> PD) why would this be a bug?  I think we will have to agree to
>>>>>>>>> disagree,
>>>>>>>>> I
>>>>>>>>> do not view this as a bug.  I do think this is inline with =
RFC3633 and
>>>>>>>>> the
>>>>>>>>> IPv6 CPE router requirements.  A lot of work has been done =
over the
>>>>>>>>> past
>>>>>>>>> couple of years to get some existing routers to be software =
upgradable
>>>>>>>>> to
>>>>>>>>> support native IPv6 as such there may be some devices with =
lesser
>>>>>>>>> capabilities.  Having a minimal level of support for IPv6 is =
better
>>>>>>>>> than
>>>>>>>>> none, right?  Finally, there may be a wide range of routers =
built over
>>>>>>>>> time
>>>>>>>>> that range in caliber and features.
>>>>>>>>=20
>>>>>>>> I think we are in agreement. I'm certainly not suggesting that =
e.g. a
>>>>>>>> /56
>>>>>>>> is
>>>>>>>> the only way it can be done. nor that delegations have to be =
rigid.
>>>>>>>> every
>>>>>>>> implementation must support any prefix length thrown at it, =
with the
>>>>>>>> exception
>>>>>>>> of getting a so small address block that it doesn't get a =
single /64 per
>>>>>>>> link.
>>>>>>>>=20
>>>>>>>> I'm just saying that the rfc3633 "hint" may not be very useful; =
and that
>>>>>>>> delegating the absolute minimum address block required may be
>>>>>>>> problematic.
>>>>>>>> for
>>>>>>>> example if the CE after a delegation is done determines that it =
needs a
>>>>>>>> larger
>>>>>>>> block, the home network may have to be renumbered.
>>>>>>> [jjmb] if a CE can only support the minimum why is it a problem =
for it to
>>>>>>> be
>>>>>>> provisioning with the minimum?  If a CE after its initial =
provisioning is
>>>>>>> reconfigured to support additional VLANs renumbering will have =
to occur
>>>>>>> anyway no?
>>>>>>>>=20
>>>>>>>> thinking of DHCP PD as a fax replacement, lets you not have to =
think
>>>>>>>> about
>>>>>>>> all
>>>>>>>> the hard corner cases. ;-)
>>>>>>> [jjmb] I still am not clear to the reference to fax replacement, =
sorry.
>>>>>>>>=20
>>>>>>>> cheers,
>>>>>>>> Ole
>>>>>>>=20
>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>>>>> John Jason Brzozowski
>>>>>>> Comcast Cable
>>>>>>> e) mailto:john_brzozowski@cable.comcast.com
>>>>>>> o) 609-377-6594
>>>>>>> m) 484-962-0060
>>>>>>> w) http://www.comcast6.net
>>>>>>> =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
>>>>>>>=20
>>>>>>> _______________________________________________
>>>>>>> v6ops mailing list
>>>>>>> v6ops@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>>>>=20
>>>>>=20
>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>>> John Jason Brzozowski
>>>>> Comcast Cable
>>>>> e) mailto:john_brzozowski@cable.comcast.com
>>>>> o) 609-377-6594
>>>>> m) 484-962-0060
>>>>> w) http://www.comcast6.net
>>>>> =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
>>>>>=20
>>>>=20
>>>=20
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>> John Jason Brzozowski
>>> Comcast Cable
>>> e) mailto:john_brzozowski@cable.comcast.com
>>> o) 609-377-6594
>>> m) 484-962-0060
>>> w) http://www.comcast6.net
>>> =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
>>>=20
>>=20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> John Jason Brzozowski
> Comcast Cable
> e) mailto:john_brzozowski@cable.comcast.com
> o) 609-377-6594
> m) 484-962-0060
> w) http://www.comcast6.net
> =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
>=20


From ot@cisco.com  Fri Oct 22 13:28:53 2010
Return-Path: <ot@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD8023A6900 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:28:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.895
X-Spam-Level: 
X-Spam-Status: No, score=-8.895 tagged_above=-999 required=5 tests=[AWL=1.704,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vSBl4zRVETmp for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:28:52 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 5F5993A68C5 for <v6ops@ietf.org>; Fri, 22 Oct 2010 13:28:52 -0700 (PDT)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYEAGORwUyQ/khMgWdsb2JhbAChaBUBARYiIqJNjSiOc4MPgjsEik0
X-IronPort-AV: E=Sophos;i="4.58,225,1286150400"; d="scan'208";a="67329878"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 22 Oct 2010 20:30:30 +0000
Received: from dhcp-10-61-107-73.cisco.com (dhcp-10-61-107-73.cisco.com [10.61.107.73]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id o9MKUSSm000652; Fri, 22 Oct 2010 20:30:28 GMT
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <ot@cisco.com>
In-Reply-To: <C8E76098.2AFB6%john_brzozowski@cable.comcast.com>
Date: Fri, 22 Oct 2010 22:30:28 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D313496-536D-4952-8599-F4B5D8386168@cisco.com>
References: <C8E76098.2AFB6%john_brzozowski@cable.comcast.com>
To: "Brzozowski, John" <John_Brzozowski@cable.comcast.com>
X-Mailer: Apple Mail (2.1081)
Cc: 'IPv6 Operations' <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 20:28:53 -0000

> To add to Tony's point, I have to agree that there are folks that do =
not
> have experience operating networks, specifically deploying IPv6, that =
seem
> to enjoy asserting their assumptions and views.  Instead of doing this =
it
> might be useful (and more productive) if folks first tried to =
understand how
> various types of networks work before making recommendations, etc.

perhaps it would be equally productive if the operators tried to =
understand how end-users would want to build their networks?

I base my previous assumption on RFC3177. as we're on an IETF list, is =
there any other IETF recommendation for a different allocation model?

cheers,
Ole



>> Ole Troan wrote:
>>> ...
>>> so creating two protocols doing exactly the same thing is a good =
thing?
>>=20
>> When the target environments are different -- YES.  Having different
>> solutions for managed vs. unmanaged environments that actually are
>> completely self-contained is required. The failure to date is that =
too many
>> people want to assert their view of how to manage a network onto =
other
>> people's environments. Both operational models are valid, so =
independent and
>> fully functional tools need to exist for each.
>>=20
>> Tony
>>=20
>>=20
>>=20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> John Jason Brzozowski
> Comcast Cable
> e) mailto:john_brzozowski@cable.comcast.com
> o) 609-377-6594
> m) 484-962-0060
> w) http://www.comcast6.net
> =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
>=20


From ichiroumakino@gmail.com  Fri Oct 22 13:30:05 2010
Return-Path: <ichiroumakino@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 97D113A693E for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:30:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.576
X-Spam-Level: 
X-Spam-Status: No, score=-1.576 tagged_above=-999 required=5 tests=[AWL=-0.973, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XnbJIiO3W3y4 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:30:04 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id F12AB3A6930 for <v6ops@ietf.org>; Fri, 22 Oct 2010 13:30:03 -0700 (PDT)
Received: by ewy27 with SMTP id 27so811764ewy.31 for <v6ops@ietf.org>; Fri, 22 Oct 2010 13:31:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=z0KWPm5mKZIbprAvd+on8HA0i9C+kKC249+VZnU/uII=; b=bLIKgtwIvzOyaUyfKL0yuag8+TdWv1NhEKVtXw2PnjbrS2aX8SujxNVszQZoWuaf8N SCu5h6TE62Yb1OHZmkMUG43V+u7Y7PowI1Fj2SuiC1s0+up+JTs600en2ndlHZF7vbyA f91F/dHyl/ffY2wmeth5Y1RGP3rTk7v/F6pJ8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=wTjg6LoN2AfSkVj3wsmt/bdi805Z2GyKt5oxjOlxJv8nNlbaFgChdxCbprfsOryVyw SsvJ5Ua90nD8jTtieNMfOnjMR8OnzNCj2RMhRmD6Wn3ovFkyKDfefy1yULEVuWmjGGXe KlxcPcknMk2vbgJCfaxivRkdj5Sq4oxgTdNJU=
Received: by 10.213.28.139 with SMTP id m11mr3743429ebc.68.1287779501615; Fri, 22 Oct 2010 13:31:41 -0700 (PDT)
Received: from dhcp-10-61-107-73.cisco.com (64-103-25-233.cisco.com [64.103.25.233]) by mx.google.com with ESMTPS id q58sm3785036eeh.15.2010.10.22.13.31.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 22 Oct 2010 13:31:40 -0700 (PDT)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: Ole Troan <otroan@employees.org>
In-Reply-To: <C8E76502.2AFDF%john_brzozowski@cable.comcast.com>
Date: Fri, 22 Oct 2010 22:31:38 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3C8235FC-FB34-483E-B0E3-613409A04457@employees.org>
References: <C8E76502.2AFDF%john_brzozowski@cable.comcast.com>
To: "Brzozowski, John" <John_Brzozowski@cable.comcast.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 20:30:05 -0000

John,

> The IGD in this would have to know about the sensor network to ensure
> traffic to it can be routed right?  The IGD at the edge of the =
customer
> premise needs to have some awareness some where no?  Even if the IGD =
was
> issue a /56, it would still have to support some form of hierarchical =
PD to
> provision and enable the sensor network right?

are you suggesting that one shouldn't be able to build IPv6 home =
networks using manual configuration?

cheers,
Ole


>> John - regarding the size of the prefix to request, here is a simple =
example.
>> We expect Zigbee IP sensor network to connect through a =
dual-interface gateway
>> to the home network and then to the IGD.  The sensor network needs a =
prefix
>> for the 802.15.4 network, but the IGD only has a single interface.  =
How does
>> the IGD know to ask for a prefix shorter than /64?  In general, how =
does the
>> IGD know, a priori, the architecture of the residential network so it =
can ask
>> for an appropriately sized prefix?
>>=20
>> - Ralph
>>=20
>> On Oct 22, 2010, at 3:45 PM 10/22/10, Brzozowski, John wrote:
>>=20
>>> On 10/21/10 5:03 AM, "Ole Tr=F8an" <otroan@employees.org> wrote:
>>>=20
>>>> John,
>>>>=20
>>>> [...]
>>>>=20
>>>>>> as more advanced home networks evolve, it is going to be =
difficult for the
>>>>>> border router to know the number of links that exists or may =
appear in the
>>>>>> future. the intention with PD was always that the prefix size was =
a
>>>>>> contractual matter, not one which is negotiated 'real time'.
>>>>> [jjmb] Hmmm...RFC3633 is a contract?
>>>>=20
>>>> a fax replacement. I'd expect when I buy service from an ISP the =
contract
>>>> between me and the ISP also includes the size of the prefix I will =
be
>>>> assigned
>>>> as well as guarantees about its lifetime.
>>> [jjmb] as stated in other emails we are dealing with protocols not
>>> contracts.  Brian stated it well, this is between the subscriber and
>>> operators, not the IETF.
>>>>=20
>>>> currently the hint in 3633 is just a MAY and even then there is =
only text
>>>> suggesting that the requesting router should include a prefix, to =
hint to
>>>> the
>>>> server that it would like to receive the same prefix that was =
presumably
>>>> previously delegated. WPD-2 in draft-ietf-v6ops-ipv6-cpe-router-07 =
includes
>>>> a
>>>> MAY hint to the delegating router about the size it would require =
and WPD-3
>>>> states it MUST accept a different prefix size.
>>> [jjmb] operators also have there own requirements, which may vary.  =
I for
>>> one will be requiring the hint.
>>>>=20
>>>> DHCPv6 PD is a mechanism where the control and policy is at the =
DHCPv6 PD
>>>> server.
>>>>=20
>>>> you could write a proposal to strengthen this language, but I would =
posit
>>>> that
>>>> the IPv6 CE is in no position to know a priori what size to ask =
for.
>>> [jjmb] really?  An IPv6 CPE has no way to determine how many and =
what sort
>>> of interfaces it is built to support or configure with?  It is not =
aware of
>>> its configuration which in turn would drive its provisioning =
request?  IMO
>>> this is most certainly something an IGD can and should be =
programmatically
>>> aware of specifically when initializing.
>>>>=20
>>>>>> mind you, I'm not an operator and I would surely like to =
understand the
>>>>>> reasons why doing more negotiation would be useful? of course, =
one has to
>>>>>> expect that every CPE supports a delegation of <=3D/64. are there =
really
>>>>>> implementations which only supports a single /64? if so, I'd =
claim that's
>>>>>> a
>>>>>> bug and not in line with 3633 nor the basic ipv6 ce router =
requirements
>>>>>> specification.
>>>>> [jjmb] having flexibility is a must, making substantial fixed =
decisions
>>>>> this
>>>>> early can result in complications or even limitations.  I =
absolutely agree
>>>>> with one of your comments above, home networks will evolve.  As =
such we
>>>>> need
>>>>> to ensure we have the ability to accommodate the same over time.  =
An
>>>>> incremental approach supports this goal.  Yes there are =
implementations
>>>>> that
>>>>> only support a /64, nothing shorter largely because they =
physically do not
>>>>> have the need and/or ability to support anything else.  If a =
device has
>>>>> only
>>>>> one IPv4 LAN and cannot be upgraded to support more (including =
hierarchical
>>>>> PD) why would this be a bug?  I think we will have to agree to =
disagree, I
>>>>> do not view this as a bug.  I do think this is inline with RFC3633 =
and the
>>>>> IPv6 CPE router requirements.  A lot of work has been done over =
the past
>>>>> couple of years to get some existing routers to be software =
upgradable to
>>>>> support native IPv6 as such there may be some devices with lesser
>>>>> capabilities.  Having a minimal level of support for IPv6 is =
better than
>>>>> none, right?  Finally, there may be a wide range of routers built =
over time
>>>>> that range in caliber and features.
>>>>=20
>>>> I think we are in agreement. I'm certainly not suggesting that e.g. =
a /56 is
>>>> the only way it can be done. nor that delegations have to be rigid. =
every
>>>> implementation must support any prefix length thrown at it, with =
the
>>>> exception
>>>> of getting a so small address block that it doesn't get a single =
/64 per
>>>> link.
>>>>=20
>>>> I'm just saying that the rfc3633 "hint" may not be very useful; and =
that
>>>> delegating the absolute minimum address block required may be =
problematic.
>>>> for
>>>> example if the CE after a delegation is done determines that it =
needs a
>>>> larger
>>>> block, the home network may have to be renumbered.
>>> [jjmb] if a CE can only support the minimum why is it a problem for =
it to be
>>> provisioning with the minimum?  If a CE after its initial =
provisioning is
>>> reconfigured to support additional VLANs renumbering will have to =
occur
>>> anyway no?
>>>>=20
>>>> thinking of DHCP PD as a fax replacement, lets you not have to =
think about
>>>> all
>>>> the hard corner cases. ;-)
>>> [jjmb] I still am not clear to the reference to fax replacement, =
sorry.
>>>>=20
>>>> cheers,
>>>> Ole
>>>=20
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>> John Jason Brzozowski
>>> Comcast Cable
>>> e) mailto:john_brzozowski@cable.comcast.com
>>> o) 609-377-6594
>>> m) 484-962-0060
>>> w) http://www.comcast6.net
>>> =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
>>>=20
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>=20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> John Jason Brzozowski
> Comcast Cable
> e) mailto:john_brzozowski@cable.comcast.com
> o) 609-377-6594
> m) 484-962-0060
> w) http://www.comcast6.net
> =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
>=20


From john_brzozowski@cable.comcast.com  Fri Oct 22 13:30:41 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 195E23A693E for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:30:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.781
X-Spam-Level: 
X-Spam-Status: No, score=-107.781 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7vEVLJ-fuFjB for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:30:38 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id AC4593A6900 for <v6ops@ietf.org>; Fri, 22 Oct 2010 13:30:37 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.101239761; Fri, 22 Oct 2010 16:32:11 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by PACDCEXHUB02.cable.comcast.com ([fe80::11d4:f530:37a0:9f4e%12]) with mapi id 14.01.0255.000; Fri, 22 Oct 2010 16:32:06 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: Ralph Droms <rdroms@cisco.com>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
Thread-Index: ActyKDTI2T6t3TrIl0mUPJfZCE79dQ==
Date: Fri, 22 Oct 2010 20:32:06 +0000
Message-ID: <C8E76D0C.2B042%john_brzozowski@cable.comcast.com>
In-Reply-To: <2BEBDF09-12FD-410F-A292-D54712F9CAA2@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B76D64D61EA76C468CBA395B29C922A7@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 20:30:41 -0000

To be clear, either approach has scale and/or operational challenges.

So I am back to how does an IGD ensure that what it requests a prefix of
sufficient size from the operator?  RFC3633 loosely provides a mechanism,
why not use it?


On 10/22/10 4:28 PM, "Ralph Droms" <rdroms@cisco.com> wrote:

> Doesn't seem like that will scale very well if there are more than a coup=
le of
> routers in the home network.
>=20
> But what do I know?  I'm not an SP network operator.
>=20
> - Ralph
>=20
>=20
> On Oct 22, 2010, at 4:26 PM 10/22/10, Brzozowski, John wrote:
>=20
>> Provisioning large blocks across the board may not reliably work either.
>>=20
>> Perhaps the IGD should simply relay downstream IA_PD requests from withi=
n
>> the premise and let the other RRs negotiate their own prefix requests wi=
th
>> the operator DHCPv6 servers?
>>=20
>> John
>>=20
>> On 10/22/10 4:20 PM, "Ralph Droms" <rdroms@cisco.com> wrote:
>>=20
>>> Just because the IGD has the capability to do hierarchical PD doesn't m=
ean
>>> it
>>> knows how many prefixes to ask for.
>>>=20
>>> - Ralph
>>>=20
>>> On Oct 22, 2010, at 4:18 PM 10/22/10, Brzozowski, John wrote:
>>>=20
>>>> The IGD has to some degree of awareness to ensure it gets provisioned
>>>> appropriately and can in turn support whatever is connected to it with=
in
>>>> the
>>>> premise.
>>>>=20
>>>>=20
>>>> On 10/22/10 4:06 PM, "Ralph Droms" <rdroms@cisco.com> wrote:
>>>>=20
>>>>>=20
>>>>> On Oct 22, 2010, at 3:57 PM 10/22/10, Brzozowski, John wrote:
>>>>>=20
>>>>>> Ralph,
>>>>>>=20
>>>>>> The IGD in this would have to know about the sensor network to ensur=
e
>>>>>> traffic to it can be routed right?  The IGD at the edge of the custo=
mer
>>>>>> premise needs to have some awareness some where no?  Even if the IGD=
 was
>>>>>> issue a /56, it would still have to support some form of hierarchica=
l PD
>>>>>> to
>>>>>> provision and enable the sensor network right?
>>>>>>=20
>>>>>> John
>>>>>=20
>>>>> Yes.
>>>>>=20
>>>>> - Ralph
>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> On 10/22/10 3:49 PM, "Ralph Droms" <rdroms@cisco.com> wrote:
>>>>>>=20
>>>>>>> John - regarding the size of the prefix to request, here is a simpl=
e
>>>>>>> example.
>>>>>>> We expect Zigbee IP sensor network to connect through a dual-interf=
ace
>>>>>>> gateway
>>>>>>> to the home network and then to the IGD.  The sensor network needs =
a
>>>>>>> prefix
>>>>>>> for the 802.15.4 network, but the IGD only has a single interface. =
 How
>>>>>>> does
>>>>>>> the IGD know to ask for a prefix shorter than /64?  In general, how=
 does
>>>>>>> the
>>>>>>> IGD know, a priori, the architecture of the residential network so =
it
>>>>>>> can
>>>>>>> ask
>>>>>>> for an appropriately sized prefix?
>>>>>>>=20
>>>>>>> - Ralph
>>>>>>>=20
>>>>>>> On Oct 22, 2010, at 3:45 PM 10/22/10, Brzozowski, John wrote:
>>>>>>>=20
>>>>>>>> On 10/21/10 5:03 AM, "Ole Tr=F8an" <otroan@employees.org> wrote:
>>>>>>>>=20
>>>>>>>>> John,
>>>>>>>>>=20
>>>>>>>>> [...]
>>>>>>>>>=20
>>>>>>>>>>> as more advanced home networks evolve, it is going to be diffic=
ult
>>>>>>>>>>> for
>>>>>>>>>>> the
>>>>>>>>>>> border router to know the number of links that exists or may ap=
pear
>>>>>>>>>>> in
>>>>>>>>>>> the
>>>>>>>>>>> future. the intention with PD was always that the prefix size w=
as a
>>>>>>>>>>> contractual matter, not one which is negotiated 'real time'.
>>>>>>>>>> [jjmb] Hmmm...RFC3633 is a contract?
>>>>>>>>>=20
>>>>>>>>> a fax replacement. I'd expect when I buy service from an ISP the
>>>>>>>>> contract
>>>>>>>>> between me and the ISP also includes the size of the prefix I wil=
l be
>>>>>>>>> assigned
>>>>>>>>> as well as guarantees about its lifetime.
>>>>>>>> [jjmb] as stated in other emails we are dealing with protocols not
>>>>>>>> contracts.  Brian stated it well, this is between the subscriber a=
nd
>>>>>>>> operators, not the IETF.
>>>>>>>>>=20
>>>>>>>>> currently the hint in 3633 is just a MAY and even then there is o=
nly
>>>>>>>>> text
>>>>>>>>> suggesting that the requesting router should include a prefix, to=
 hint
>>>>>>>>> to
>>>>>>>>> the
>>>>>>>>> server that it would like to receive the same prefix that was
>>>>>>>>> presumably
>>>>>>>>> previously delegated. WPD-2 in draft-ietf-v6ops-ipv6-cpe-router-0=
7
>>>>>>>>> includes
>>>>>>>>> a
>>>>>>>>> MAY hint to the delegating router about the size it would require=
 and
>>>>>>>>> WPD-3
>>>>>>>>> states it MUST accept a different prefix size.
>>>>>>>> [jjmb] operators also have there own requirements, which may vary.=
  I
>>>>>>>> for
>>>>>>>> one will be requiring the hint.
>>>>>>>>>=20
>>>>>>>>> DHCPv6 PD is a mechanism where the control and policy is at the D=
HCPv6
>>>>>>>>> PD
>>>>>>>>> server.
>>>>>>>>>=20
>>>>>>>>> you could write a proposal to strengthen this language, but I wou=
ld
>>>>>>>>> posit
>>>>>>>>> that
>>>>>>>>> the IPv6 CE is in no position to know a priori what size to ask f=
or.
>>>>>>>> [jjmb] really?  An IPv6 CPE has no way to determine how many and w=
hat
>>>>>>>> sort
>>>>>>>> of interfaces it is built to support or configure with?  It is not
>>>>>>>> aware
>>>>>>>> of
>>>>>>>> its configuration which in turn would drive its provisioning reque=
st?
>>>>>>>> IMO
>>>>>>>> this is most certainly something an IGD can and should be
>>>>>>>> programmatically
>>>>>>>> aware of specifically when initializing.
>>>>>>>>>=20
>>>>>>>>>>> mind you, I'm not an operator and I would surely like to unders=
tand
>>>>>>>>>>> the
>>>>>>>>>>> reasons why doing more negotiation would be useful? of course, =
one
>>>>>>>>>>> has
>>>>>>>>>>> to
>>>>>>>>>>> expect that every CPE supports a delegation of <=3D/64. are the=
re
>>>>>>>>>>> really
>>>>>>>>>>> implementations which only supports a single /64? if so, I'd cl=
aim
>>>>>>>>>>> that's
>>>>>>>>>>> a
>>>>>>>>>>> bug and not in line with 3633 nor the basic ipv6 ce router
>>>>>>>>>>> requirements
>>>>>>>>>>> specification.
>>>>>>>>>> [jjmb] having flexibility is a must, making substantial fixed
>>>>>>>>>> decisions
>>>>>>>>>> this
>>>>>>>>>> early can result in complications or even limitations.  I absolu=
tely
>>>>>>>>>> agree
>>>>>>>>>> with one of your comments above, home networks will evolve.  As =
such
>>>>>>>>>> we
>>>>>>>>>> need
>>>>>>>>>> to ensure we have the ability to accommodate the same over time.=
  An
>>>>>>>>>> incremental approach supports this goal.  Yes there are
>>>>>>>>>> implementations
>>>>>>>>>> that
>>>>>>>>>> only support a /64, nothing shorter largely because they physica=
lly
>>>>>>>>>> do
>>>>>>>>>> not
>>>>>>>>>> have the need and/or ability to support anything else.  If a dev=
ice
>>>>>>>>>> has
>>>>>>>>>> only
>>>>>>>>>> one IPv4 LAN and cannot be upgraded to support more (including
>>>>>>>>>> hierarchical
>>>>>>>>>> PD) why would this be a bug?  I think we will have to agree to
>>>>>>>>>> disagree,
>>>>>>>>>> I
>>>>>>>>>> do not view this as a bug.  I do think this is inline with RFC36=
33
>>>>>>>>>> and
>>>>>>>>>> the
>>>>>>>>>> IPv6 CPE router requirements.  A lot of work has been done over =
the
>>>>>>>>>> past
>>>>>>>>>> couple of years to get some existing routers to be software
>>>>>>>>>> upgradable
>>>>>>>>>> to
>>>>>>>>>> support native IPv6 as such there may be some devices with lesse=
r
>>>>>>>>>> capabilities.  Having a minimal level of support for IPv6 is bet=
ter
>>>>>>>>>> than
>>>>>>>>>> none, right?  Finally, there may be a wide range of routers buil=
t
>>>>>>>>>> over
>>>>>>>>>> time
>>>>>>>>>> that range in caliber and features.
>>>>>>>>>=20
>>>>>>>>> I think we are in agreement. I'm certainly not suggesting that e.=
g. a
>>>>>>>>> /56
>>>>>>>>> is
>>>>>>>>> the only way it can be done. nor that delegations have to be rigi=
d.
>>>>>>>>> every
>>>>>>>>> implementation must support any prefix length thrown at it, with =
the
>>>>>>>>> exception
>>>>>>>>> of getting a so small address block that it doesn't get a single =
/64
>>>>>>>>> per
>>>>>>>>> link.
>>>>>>>>>=20
>>>>>>>>> I'm just saying that the rfc3633 "hint" may not be very useful; a=
nd
>>>>>>>>> that
>>>>>>>>> delegating the absolute minimum address block required may be
>>>>>>>>> problematic.
>>>>>>>>> for
>>>>>>>>> example if the CE after a delegation is done determines that it n=
eeds
>>>>>>>>> a
>>>>>>>>> larger
>>>>>>>>> block, the home network may have to be renumbered.
>>>>>>>> [jjmb] if a CE can only support the minimum why is it a problem fo=
r it
>>>>>>>> to
>>>>>>>> be
>>>>>>>> provisioning with the minimum?  If a CE after its initial provisio=
ning
>>>>>>>> is
>>>>>>>> reconfigured to support additional VLANs renumbering will have to =
occur
>>>>>>>> anyway no?
>>>>>>>>>=20
>>>>>>>>> thinking of DHCP PD as a fax replacement, lets you not have to th=
ink
>>>>>>>>> about
>>>>>>>>> all
>>>>>>>>> the hard corner cases. ;-)
>>>>>>>> [jjmb] I still am not clear to the reference to fax replacement, s=
orry.
>>>>>>>>>=20
>>>>>>>>> cheers,
>>>>>>>>> Ole
>>>>>>>>=20
>>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>>>>>> John Jason Brzozowski
>>>>>>>> Comcast Cable
>>>>>>>> e) mailto:john_brzozowski@cable.comcast.com
>>>>>>>> o) 609-377-6594
>>>>>>>> m) 484-962-0060
>>>>>>>> w) http://www.comcast6.net
>>>>>>>> =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
>>>>>>>>=20
>>>>>>>> _______________________________________________
>>>>>>>> v6ops mailing list
>>>>>>>> v6ops@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>>>>>=20
>>>>>>=20
>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>>>> John Jason Brzozowski
>>>>>> Comcast Cable
>>>>>> e) mailto:john_brzozowski@cable.comcast.com
>>>>>> o) 609-377-6594
>>>>>> m) 484-962-0060
>>>>>> w) http://www.comcast6.net
>>>>>> =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
>>>>>>=20
>>>>>=20
>>>>=20
>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>> John Jason Brzozowski
>>>> Comcast Cable
>>>> e) mailto:john_brzozowski@cable.comcast.com
>>>> o) 609-377-6594
>>>> m) 484-962-0060
>>>> w) http://www.comcast6.net
>>>> =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
>>>>=20
>>>=20
>>=20
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> John Jason Brzozowski
>> Comcast Cable
>> e) mailto:john_brzozowski@cable.comcast.com
>> o) 609-377-6594
>> m) 484-962-0060
>> w) http://www.comcast6.net
>> =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
>>=20
>=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From rdroms@cisco.com  Fri Oct 22 13:34:20 2010
Return-Path: <rdroms@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A5BB53A693E for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.426
X-Spam-Level: 
X-Spam-Status: No, score=-9.426 tagged_above=-999 required=5 tests=[AWL=-0.823, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OlEWZybfeuhk for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:34:18 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 7B8523A695A for <v6ops@ietf.org>; Fri, 22 Oct 2010 13:34:18 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.58,225,1286150400"; d="scan'208";a="173978757"
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 22 Oct 2010 20:35:56 +0000
Received: from bxb-rdroms-8712.cisco.com (bxb-rdroms-8712.cisco.com [10.98.10.83]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o9MKZuaP003729; Fri, 22 Oct 2010 20:35:56 GMT
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: Ralph Droms <rdroms@cisco.com>
In-Reply-To: <C8E76D0C.2B042%john_brzozowski@cable.comcast.com>
Date: Fri, 22 Oct 2010 16:35:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <618B7A4B-FDAE-4F06-8580-519FF56C4F52@cisco.com>
References: <C8E76D0C.2B042%john_brzozowski@cable.comcast.com>
To: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 20:34:20 -0000

Although RFC 3633 might provide a hinting mechanism, there's no good =
automated way for the IGD to know what information to put into that =
hint.  So there is no way for the IGD to ensure it requests a sufficient =
prefix.

- Ralph

On Oct 22, 2010, at 4:32 PM 10/22/10, Brzozowski, John wrote:

> To be clear, either approach has scale and/or operational challenges.
>=20
> So I am back to how does an IGD ensure that what it requests a prefix =
of
> sufficient size from the operator?  RFC3633 loosely provides a =
mechanism,
> why not use it?
>=20
>=20
> On 10/22/10 4:28 PM, "Ralph Droms" <rdroms@cisco.com> wrote:
>=20
>> Doesn't seem like that will scale very well if there are more than a =
couple of
>> routers in the home network.
>>=20
>> But what do I know?  I'm not an SP network operator.
>>=20
>> - Ralph
>>=20
>>=20
>> On Oct 22, 2010, at 4:26 PM 10/22/10, Brzozowski, John wrote:
>>=20
>>> Provisioning large blocks across the board may not reliably work =
either.
>>>=20
>>> Perhaps the IGD should simply relay downstream IA_PD requests from =
within
>>> the premise and let the other RRs negotiate their own prefix =
requests with
>>> the operator DHCPv6 servers?
>>>=20
>>> John
>>>=20
>>> On 10/22/10 4:20 PM, "Ralph Droms" <rdroms@cisco.com> wrote:
>>>=20
>>>> Just because the IGD has the capability to do hierarchical PD =
doesn't mean
>>>> it
>>>> knows how many prefixes to ask for.
>>>>=20
>>>> - Ralph
>>>>=20
>>>> On Oct 22, 2010, at 4:18 PM 10/22/10, Brzozowski, John wrote:
>>>>=20
>>>>> The IGD has to some degree of awareness to ensure it gets =
provisioned
>>>>> appropriately and can in turn support whatever is connected to it =
within
>>>>> the
>>>>> premise.
>>>>>=20
>>>>>=20
>>>>> On 10/22/10 4:06 PM, "Ralph Droms" <rdroms@cisco.com> wrote:
>>>>>=20
>>>>>>=20
>>>>>> On Oct 22, 2010, at 3:57 PM 10/22/10, Brzozowski, John wrote:
>>>>>>=20
>>>>>>> Ralph,
>>>>>>>=20
>>>>>>> The IGD in this would have to know about the sensor network to =
ensure
>>>>>>> traffic to it can be routed right?  The IGD at the edge of the =
customer
>>>>>>> premise needs to have some awareness some where no?  Even if the =
IGD was
>>>>>>> issue a /56, it would still have to support some form of =
hierarchical PD
>>>>>>> to
>>>>>>> provision and enable the sensor network right?
>>>>>>>=20
>>>>>>> John
>>>>>>=20
>>>>>> Yes.
>>>>>>=20
>>>>>> - Ralph
>>>>>>=20
>>>>>>>=20
>>>>>>>=20
>>>>>>> On 10/22/10 3:49 PM, "Ralph Droms" <rdroms@cisco.com> wrote:
>>>>>>>=20
>>>>>>>> John - regarding the size of the prefix to request, here is a =
simple
>>>>>>>> example.
>>>>>>>> We expect Zigbee IP sensor network to connect through a =
dual-interface
>>>>>>>> gateway
>>>>>>>> to the home network and then to the IGD.  The sensor network =
needs a
>>>>>>>> prefix
>>>>>>>> for the 802.15.4 network, but the IGD only has a single =
interface.  How
>>>>>>>> does
>>>>>>>> the IGD know to ask for a prefix shorter than /64?  In general, =
how does
>>>>>>>> the
>>>>>>>> IGD know, a priori, the architecture of the residential network =
so it
>>>>>>>> can
>>>>>>>> ask
>>>>>>>> for an appropriately sized prefix?
>>>>>>>>=20
>>>>>>>> - Ralph
>>>>>>>>=20
>>>>>>>> On Oct 22, 2010, at 3:45 PM 10/22/10, Brzozowski, John wrote:
>>>>>>>>=20
>>>>>>>>> On 10/21/10 5:03 AM, "Ole Tr=F8an" <otroan@employees.org> =
wrote:
>>>>>>>>>=20
>>>>>>>>>> John,
>>>>>>>>>>=20
>>>>>>>>>> [...]
>>>>>>>>>>=20
>>>>>>>>>>>> as more advanced home networks evolve, it is going to be =
difficult
>>>>>>>>>>>> for
>>>>>>>>>>>> the
>>>>>>>>>>>> border router to know the number of links that exists or =
may appear
>>>>>>>>>>>> in
>>>>>>>>>>>> the
>>>>>>>>>>>> future. the intention with PD was always that the prefix =
size was a
>>>>>>>>>>>> contractual matter, not one which is negotiated 'real =
time'.
>>>>>>>>>>> [jjmb] Hmmm...RFC3633 is a contract?
>>>>>>>>>>=20
>>>>>>>>>> a fax replacement. I'd expect when I buy service from an ISP =
the
>>>>>>>>>> contract
>>>>>>>>>> between me and the ISP also includes the size of the prefix I =
will be
>>>>>>>>>> assigned
>>>>>>>>>> as well as guarantees about its lifetime.
>>>>>>>>> [jjmb] as stated in other emails we are dealing with protocols =
not
>>>>>>>>> contracts.  Brian stated it well, this is between the =
subscriber and
>>>>>>>>> operators, not the IETF.
>>>>>>>>>>=20
>>>>>>>>>> currently the hint in 3633 is just a MAY and even then there =
is only
>>>>>>>>>> text
>>>>>>>>>> suggesting that the requesting router should include a =
prefix, to hint
>>>>>>>>>> to
>>>>>>>>>> the
>>>>>>>>>> server that it would like to receive the same prefix that was
>>>>>>>>>> presumably
>>>>>>>>>> previously delegated. WPD-2 in =
draft-ietf-v6ops-ipv6-cpe-router-07
>>>>>>>>>> includes
>>>>>>>>>> a
>>>>>>>>>> MAY hint to the delegating router about the size it would =
require and
>>>>>>>>>> WPD-3
>>>>>>>>>> states it MUST accept a different prefix size.
>>>>>>>>> [jjmb] operators also have there own requirements, which may =
vary.  I
>>>>>>>>> for
>>>>>>>>> one will be requiring the hint.
>>>>>>>>>>=20
>>>>>>>>>> DHCPv6 PD is a mechanism where the control and policy is at =
the DHCPv6
>>>>>>>>>> PD
>>>>>>>>>> server.
>>>>>>>>>>=20
>>>>>>>>>> you could write a proposal to strengthen this language, but I =
would
>>>>>>>>>> posit
>>>>>>>>>> that
>>>>>>>>>> the IPv6 CE is in no position to know a priori what size to =
ask for.
>>>>>>>>> [jjmb] really?  An IPv6 CPE has no way to determine how many =
and what
>>>>>>>>> sort
>>>>>>>>> of interfaces it is built to support or configure with?  It is =
not
>>>>>>>>> aware
>>>>>>>>> of
>>>>>>>>> its configuration which in turn would drive its provisioning =
request?
>>>>>>>>> IMO
>>>>>>>>> this is most certainly something an IGD can and should be
>>>>>>>>> programmatically
>>>>>>>>> aware of specifically when initializing.
>>>>>>>>>>=20
>>>>>>>>>>>> mind you, I'm not an operator and I would surely like to =
understand
>>>>>>>>>>>> the
>>>>>>>>>>>> reasons why doing more negotiation would be useful? of =
course, one
>>>>>>>>>>>> has
>>>>>>>>>>>> to
>>>>>>>>>>>> expect that every CPE supports a delegation of <=3D/64. are =
there
>>>>>>>>>>>> really
>>>>>>>>>>>> implementations which only supports a single /64? if so, =
I'd claim
>>>>>>>>>>>> that's
>>>>>>>>>>>> a
>>>>>>>>>>>> bug and not in line with 3633 nor the basic ipv6 ce router
>>>>>>>>>>>> requirements
>>>>>>>>>>>> specification.
>>>>>>>>>>> [jjmb] having flexibility is a must, making substantial =
fixed
>>>>>>>>>>> decisions
>>>>>>>>>>> this
>>>>>>>>>>> early can result in complications or even limitations.  I =
absolutely
>>>>>>>>>>> agree
>>>>>>>>>>> with one of your comments above, home networks will evolve.  =
As such
>>>>>>>>>>> we
>>>>>>>>>>> need
>>>>>>>>>>> to ensure we have the ability to accommodate the same over =
time.  An
>>>>>>>>>>> incremental approach supports this goal.  Yes there are
>>>>>>>>>>> implementations
>>>>>>>>>>> that
>>>>>>>>>>> only support a /64, nothing shorter largely because they =
physically
>>>>>>>>>>> do
>>>>>>>>>>> not
>>>>>>>>>>> have the need and/or ability to support anything else.  If a =
device
>>>>>>>>>>> has
>>>>>>>>>>> only
>>>>>>>>>>> one IPv4 LAN and cannot be upgraded to support more =
(including
>>>>>>>>>>> hierarchical
>>>>>>>>>>> PD) why would this be a bug?  I think we will have to agree =
to
>>>>>>>>>>> disagree,
>>>>>>>>>>> I
>>>>>>>>>>> do not view this as a bug.  I do think this is inline with =
RFC3633
>>>>>>>>>>> and
>>>>>>>>>>> the
>>>>>>>>>>> IPv6 CPE router requirements.  A lot of work has been done =
over the
>>>>>>>>>>> past
>>>>>>>>>>> couple of years to get some existing routers to be software
>>>>>>>>>>> upgradable
>>>>>>>>>>> to
>>>>>>>>>>> support native IPv6 as such there may be some devices with =
lesser
>>>>>>>>>>> capabilities.  Having a minimal level of support for IPv6 is =
better
>>>>>>>>>>> than
>>>>>>>>>>> none, right?  Finally, there may be a wide range of routers =
built
>>>>>>>>>>> over
>>>>>>>>>>> time
>>>>>>>>>>> that range in caliber and features.
>>>>>>>>>>=20
>>>>>>>>>> I think we are in agreement. I'm certainly not suggesting =
that e.g. a
>>>>>>>>>> /56
>>>>>>>>>> is
>>>>>>>>>> the only way it can be done. nor that delegations have to be =
rigid.
>>>>>>>>>> every
>>>>>>>>>> implementation must support any prefix length thrown at it, =
with the
>>>>>>>>>> exception
>>>>>>>>>> of getting a so small address block that it doesn't get a =
single /64
>>>>>>>>>> per
>>>>>>>>>> link.
>>>>>>>>>>=20
>>>>>>>>>> I'm just saying that the rfc3633 "hint" may not be very =
useful; and
>>>>>>>>>> that
>>>>>>>>>> delegating the absolute minimum address block required may be
>>>>>>>>>> problematic.
>>>>>>>>>> for
>>>>>>>>>> example if the CE after a delegation is done determines that =
it needs
>>>>>>>>>> a
>>>>>>>>>> larger
>>>>>>>>>> block, the home network may have to be renumbered.
>>>>>>>>> [jjmb] if a CE can only support the minimum why is it a =
problem for it
>>>>>>>>> to
>>>>>>>>> be
>>>>>>>>> provisioning with the minimum?  If a CE after its initial =
provisioning
>>>>>>>>> is
>>>>>>>>> reconfigured to support additional VLANs renumbering will have =
to occur
>>>>>>>>> anyway no?
>>>>>>>>>>=20
>>>>>>>>>> thinking of DHCP PD as a fax replacement, lets you not have =
to think
>>>>>>>>>> about
>>>>>>>>>> all
>>>>>>>>>> the hard corner cases. ;-)
>>>>>>>>> [jjmb] I still am not clear to the reference to fax =
replacement, sorry.
>>>>>>>>>>=20
>>>>>>>>>> cheers,
>>>>>>>>>> Ole
>>>>>>>>>=20
>>>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>>>>>>> John Jason Brzozowski
>>>>>>>>> Comcast Cable
>>>>>>>>> e) mailto:john_brzozowski@cable.comcast.com
>>>>>>>>> o) 609-377-6594
>>>>>>>>> m) 484-962-0060
>>>>>>>>> w) http://www.comcast6.net
>>>>>>>>> =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
>>>>>>>>>=20
>>>>>>>>> _______________________________________________
>>>>>>>>> v6ops mailing list
>>>>>>>>> v6ops@ietf.org
>>>>>>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>>>>>>=20
>>>>>>>=20
>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>>>>> John Jason Brzozowski
>>>>>>> Comcast Cable
>>>>>>> e) mailto:john_brzozowski@cable.comcast.com
>>>>>>> o) 609-377-6594
>>>>>>> m) 484-962-0060
>>>>>>> w) http://www.comcast6.net
>>>>>>> =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
>>>>>>>=20
>>>>>>=20
>>>>>=20
>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>>> John Jason Brzozowski
>>>>> Comcast Cable
>>>>> e) mailto:john_brzozowski@cable.comcast.com
>>>>> o) 609-377-6594
>>>>> m) 484-962-0060
>>>>> w) http://www.comcast6.net
>>>>> =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
>>>>>=20
>>>>=20
>>>=20
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>> John Jason Brzozowski
>>> Comcast Cable
>>> e) mailto:john_brzozowski@cable.comcast.com
>>> o) 609-377-6594
>>> m) 484-962-0060
>>> w) http://www.comcast6.net
>>> =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
>>>=20
>>=20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> John Jason Brzozowski
> Comcast Cable
> e) mailto:john_brzozowski@cable.comcast.com
> o) 609-377-6594
> m) 484-962-0060
> w) http://www.comcast6.net
> =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
>=20


From prvs=904190e80=Scott.Beuker@sjrb.ca  Fri Oct 22 13:38:51 2010
Return-Path: <prvs=904190e80=Scott.Beuker@sjrb.ca>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B990F3A6956 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:38:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.374
X-Spam-Level: 
X-Spam-Status: No, score=-2.374 tagged_above=-999 required=5 tests=[AWL=-0.075, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ciYWl6VHo958 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:38:50 -0700 (PDT)
Received: from prdcg4ipta02x-ext.shaw.ca (prdcg4ipta02x-ext.shaw.ca [204.209.208.147]) by core3.amsl.com (Postfix) with ESMTP id 512043A693E for <v6ops@ietf.org>; Fri, 22 Oct 2010 13:38:50 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.58,225,1286172000"; d="scan'208";a="155294284"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 22 Oct 2010 14:40:07 -0600
Message-ID: <1EA76BAD7F050648910C041BDDED8CD5013FDBD5@PRDCG4EXVW01-5.OSS.PRD>
In-Reply-To: <6D0FD94C-892C-47C9-BAFC-BD8DA6B48C9E@free.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops] Reasons not to endorse NAT66/6to4(ref	draft-kuarsingh-v6ops-provider-managed-tunnel-00)
Thread-Index: ActyAlqAfg2wc7LfSjWu5D9Souk9TwAIJ2hQ
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr><4CC07295.8000603@gont.com.ar><28A6DE3B-3D4D-45DF-98D3-4B7AFE0E6CF1@free.fr><4CC07EEA.6000306@gont.com.ar> <44C27CB3-0633-46E4-A919-6351526D0DFA@free.fr> <1EA76BAD7F050648910C041BDDED8CD5013FDBD1@PRDCG4EXVW01-5.OSS.PRD> <6D0FD94C-892C-47C9-BAFC-BD8DA6B48C9E@free.fr>
From: "Scott Beuker" <Scott.Beuker@sjrb.ca>
To: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
X-OriginalArrivalTime: 22 Oct 2010 20:40:07.0382 (UTC) FILETIME=[5021F760:01CB7229]
X-TM-AS-Product-Ver: SMEX-8.0.0.1285-6.500.1024-17720.000
X-TM-AS-Result: No--11.288900-0.000000-31
X-TM-AS-User-Approved-Sender: Yes
X-TM-AS-User-Blocked-Sender: No
Cc: v6ops v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref	draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 20:38:51 -0000

> Note that the RFC on Teredo (RFC 4380) says "Teredo is designed to
> provide an "IPv6 access of last resort" to  nodes that need IPv6
> connectivity but cannot use any of the other IPv6 transition schemes."
> Today, the ordinary user doesn't NEED IPv6 connectivity.
> In my understanding, Teredo is appropriate for those who know enough
> about IPv6 to determine that they NEED it, but oNLY for these.

Yes, *today* that is true. But by that same logic, IPv6 isn't necessary =
at all *today*. This isn't about today. This is about a year or two from =
now. This is about the point in time when IPv6 is necessary, and yet =
some people don't have it.

- Scott


From Wesley.E.George@sprint.com  Fri Oct 22 13:51:08 2010
Return-Path: <Wesley.E.George@sprint.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 073FB3A6969 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:51:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.383
X-Spam-Level: 
X-Spam-Status: No, score=-3.383 tagged_above=-999 required=5 tests=[AWL=-0.384, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jA4-JdE+9IwD for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:51:05 -0700 (PDT)
Received: from AM1EHSOBE003.bigfish.com (am1ehsobe003.messaging.microsoft.com [213.199.154.206]) by core3.amsl.com (Postfix) with ESMTP id B47F13A68E7 for <v6ops@ietf.org>; Fri, 22 Oct 2010 13:51:04 -0700 (PDT)
Received: from mail24-am1-R.bigfish.com (10.3.201.250) by AM1EHSOBE003.bigfish.com (10.3.204.23) with Microsoft SMTP Server id 14.1.225.8; Fri, 22 Oct 2010 20:52:42 +0000
Received: from mail24-am1 (localhost.localdomain [127.0.0.1])	by mail24-am1-R.bigfish.com (Postfix) with ESMTP id 0AA2311C0628; Fri, 22 Oct 2010 20:52:42 +0000 (UTC)
X-SpamScore: -49
X-BigFish: VS-49(zz542N1418M1432N4015L9371Pzz1202hzz8275dh1033ILz2fh87h2a8h61h)
X-Spam-TCS-SCL: 0:0
X-FB-DOMAIN-IP-MATCH: fail
Received: from mail24-am1 (localhost.localdomain [127.0.0.1]) by mail24-am1 (MessageSwitch) id 1287780760795245_3194; Fri, 22 Oct 2010 20:52:40 +0000 (UTC)
Received: from AM1EHSMHS003.bigfish.com (unknown [10.3.201.251])	by mail24-am1.bigfish.com (Postfix) with ESMTP id BF0407D004C; Fri, 22 Oct 2010 20:52:40 +0000 (UTC)
Received: from plsasdm1.corp.sprint.com (144.230.168.25) by AM1EHSMHS003.bigfish.com (10.3.207.103) with Microsoft SMTP Server (TLS) id 14.1.225.8; Fri, 22 Oct 2010 20:52:37 +0000
Received: from PDAWEH01.ad.sprint.com (PDAWEH01.corp.sprint.com [144.226.110.69])	by plsasdm1.corp.sprint.com (Sentrion-MTA-4.0.5/Sentrion-MTA-4.0.5) with ESMTP id o9MKqZEq029625 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 22 Oct 2010 15:52:35 -0500
Received: from PDAWEH04.ad.sprint.com (144.226.111.59) by PDAWEH01.ad.sprint.com (144.226.110.69) with Microsoft SMTP Server (TLS) id 14.1.255.0; Fri, 22 Oct 2010 15:52:35 -0500
Received: from PLSWM12A.ad.sprint.com ([fe80::dd81:e8a1:cd6b:78f]) by PDAWEH04.ad.sprint.com ([2002:90e2:6f3b::90e2:6f3b]) with mapi id 14.01.0255.000; Fri, 22 Oct 2010 15:52:34 -0500
From: "George, Wes E IV [NTK]" <Wesley.E.George@sprint.com>
To: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: Soliciting feedback on draft-livingood-dns-whitelisting-implications
Thread-Index: AQHLYZZsVCE0+zqIz0+l2xjka9peKJNNW4lQ
Date: Fri, 22 Oct 2010 20:52:34 +0000
Message-ID: <54E900DC635DAB4DB7A6D799B3C4CD8E016867@PLSWM12A.ad.sprint.com>
References: <C8BFD127.F082%victor.kuarsingh@gmail.com> <C8CB9E88.5599%jason_livingood@cable.comcast.com>
In-Reply-To: <C8CB9E88.5599%jason_livingood@cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.153.203.27]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: sprint.com
Subject: Re: [v6ops] Soliciting feedback on	draft-livingood-dns-whitelisting-implications
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 20:51:08 -0000

I have reviewed this draft (-01 version), and have some comments. I think t=
hat there's value in having a draft like this, so keep up the good work!

First, I might recommend taking your introduction and splitting it into a b=
asic explanation of what whitelisting is, and then move the section where y=
ou discuss *why* people are doing this into its own section. Since you have=
 a specific section on concerns, it would make sense to have a complimentar=
y section on justification/pros for using whitelisting.

Second, in your concerns section (3), you refer to "these [concerned] parti=
es" multiple times. I think it would be cleaner to simply start the section=
 as you have (concerns in parts of the internet community), and then just d=
iscuss the issue. Rather than trying to distance yourself in your language =
from the concept being expressed, with "some people say..." just state it a=
s fact. While not everyone may agree with the opinion being discussed, you =
are still stating a factual representation of the opinions of a group of fo=
lks, so I don't think that it's necessary to qualify it so much. I think th=
at would be clearer and cleaner than the current language.

You talk in the concerns section about the fact that whitelisting requires =
new IPv6 networks to seek out and contact all of the whitelisters to get th=
eir DNS resolvers approved, and how that is difficult and time-consuming, b=
ut I think that you could clarify why this is a bad thing, independent of t=
he effort required to manage it. You mention barriers to IPv6 deployment, b=
ut I can think of a specific example that may help to clarify what you mean=
: When you deploy IPv6 in any form on an eyeball network, it is often at le=
ast partially as a way to reduce the pressure on IPv4 exhaustion within tha=
t network, as well as to reduce the load on any IPv4 extension technologies=
 that you may have implemented (NATs of various flavors, DSLite, etc). Anyt=
hing that can go native IPv6 can likely bypass that infrastructure, dependi=
ng on implementation. Whitelists dramatically reduce this benefit by maskin=
g what would otherwise be IPv6-reachable content and keeping it on the IPv4=
 infrastructure. It's not really a question of preventing IPv6 deployment, =
as that really shouldn't still be a question. Really, it is preventing prov=
iders from being able to leverage what they have deployed. While you could =
argue that even a partial whitelist (based on your top 10 customer destinat=
ions) would help, the other several thousand that are missing have a combin=
ed negative effect that should be noted here.

You touch on this a bit in your section on de-listing and in 7.4 but whitel=
isting can also provide a false sense of security to the content network, a=
nd it is highly reliant on the vetting process and the individual network i=
mplementation in order for it to actually provide the benefit being sought.
What I mean by this is, even on a network with ubiquitous IPv6 support, if =
it is opt-in, or reliant on compatible customer-owned CPE, I can still have=
 a "broken" host behind legacy equipment and have a bad user experience.
Unless the network in question is very homogenous, and IPv6 is deployed in =
the same way (and possibly the same time) network-wide, there is a question=
 as to whether the whitelister can trust the requestor (whitelistee?) that =
their entire network will provide the expected level of IPv6 service everyw=
here. If the requestor happens to provide publicly reachable DNS cache serv=
ers, there is no guarantee that all hosts using those servers are not "brok=
en" and may well defeat the purpose of the whitelist.
So the alternative is to either deny those networks whitelist until they ar=
e nearly finished with what may be a multiyear IPv6 deployment, or take wha=
t are essentially the same risks of poor end user experience, and hope that=
 they'll be resolved before they're overly detrimental to your business. Ot=
herwise, it may require the end network to make architectural changes to th=
eir DNS infrastructure to ensure that they can segregate the IPv6-capable p=
arts of the network onto one set of resolvers that are separate from the IP=
v4-only sections, or make their whitelisted resolvers no longer publicly av=
ailable, etc.

This problem can be even worse in SPs that serve primarily commercial/enter=
prise networks. Residential network SPs can make a reasonable assumption th=
at the majority of their customers will be using the in-network resolvers. =
Large ISPs with large business customers cannot assume this. In fact, the m=
ajority of their customers may be rolling their own DNS caches locally. Som=
e may ultimately point back to the ISP's cache servers, but an equal amount=
 will do their own recursion from the root, or point to someone else's DNS =
resolvers. This now dramatically increases the scope of folks that must be =
whitelisted to see any benefit from an IPv6 deployment, and as an ISP, I ha=
ve almost no control over whether my customer expends the energy (or even k=
nows how) to get their servers whitelisted.

Regarding section 5 - I'm not sure I agree with the assertion that whitelis=
ting would need to be built into all auth server software for universal imp=
lementation. The proposal I saw for making this a little less manual (I wou=
ld cite a draft, but I'm not aware of one - Erik Kline from Google presente=
d the idea at a conference) used in-addr.arpa TXT records, combined with so=
me external scripting to collect and verify IP addresses of resolvers to fe=
ed into whitelists. I would think that this could be implemented without sp=
ecial software in the auth server itself, but I'm by no means an expert on =
existing implementations of DNS auth/whitelist as to where the magic actual=
ly happens. I just bring it up as a point to verify.
I think that there is also a subset that is sort of both of your two catego=
ries - ad-hoc deployment, but universal (if still mostly ad-hoc) coordinati=
on. Think in terms of a well-known email distro (whitelist@listdomain.com) =
or website (like peeringdb) that anyone who is whitelisting their auth serv=
ers can join, and when new people want to qualify their networks for whitel=
isting, they send mail to that address. This at least removes the barrier a=
ssociated with having to find and reach all of the folks who are doing the =
whitelisting.

Also, you should point out a potential timing issue with universal implemen=
tation - if we go the route of standardizing a whitelisting implementation =
(pushing through IETF, multiple vendors implementing, multiple networks usi=
ng), we're likely to miss the window where this actually matters. Ultimatel=
y, I have always understood whitelisting to be a set of "training wheels" u=
ntil big content providers were more confident that IPv6 would work for eno=
ugh of their users that there was no risk in mainstreaming their AAAA recor=
ds. In most cases, this translates into an increase in the amount of good I=
Pv6 deployments so that the amount of broken deployments both is reduced an=
d made statistically insignificant. If we still have major problems with IP=
v6 working on the other end of a standards and deployment cycle, especially=
 since it would likely take us post IPv4 exhaustion, I'd say we have a larg=
er problem.

Section 8 - Another alternative would be DNS shared fate - only responding =
with AAAA queries to IPv6 source addresses, either at the auth or recursive=
 server as a coarse way to verify that IPv6 is functioning properly before =
sending a client to use it. I am aware of two main concerns with this - tha=
t it doesn't actually prove functional IPv6, because it doesn't necessarily=
 verify MTU and routing all work correctly, and that it would shut out any =
hosts that cannot do DNS via IPv6, either because they don't support it (li=
ke Windows XP), or because they have not been configured with an IPv6 DNS s=
erver. There are likely others, but that's all I can think of right now.

Lastly, I think you probably need either an informative reference or a comp=
anion draft explaining what "broken IPv6" whitelisting is attempting to pro=
tect against. I agree with what you say in section 6 that it's not in scope=
 of this document, but since the real solution is to fix what's broken, a r=
eference can't hurt, especially in 8.3.1.

Thanks,
Wes George

> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
> Of Livingood, Jason
> Sent: Friday, October 01, 2010 2:28 PM
> To: v6ops@ietf.org
> Subject: [v6ops] Soliciting feedback on draft-livingood-dns-
> whitelisting-implications
>
> Hi -
>
> I am soliciting feeback on this new draft, available at
> http://tools.ietf.org/html/draft-livingood-dns-whitelisting-
> implications. In particular, I am looking for more text to add in the
> justifications / rationale for this practice in an attempt to
> objectively examine the issue from many sides.  This is only a first
> draft of course.
>
> Regards
> Jason Livingood
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


________________________________

This e-mail may contain Sprint Nextel proprietary information intended for =
the sole use of the recipient(s). Any use by others is prohibited. If you a=
re not the intended recipient, please contact the sender and delete all cop=
ies of the message.


From jhw@apple.com  Fri Oct 22 13:56:44 2010
Return-Path: <jhw@apple.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B06EE3A695A for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.259
X-Spam-Level: 
X-Spam-Status: No, score=-106.259 tagged_above=-999 required=5 tests=[AWL=0.340, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yvFizOUaVQq0 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 13:56:43 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id E253A3A68BA for <v6ops@ietf.org>; Fri, 22 Oct 2010 13:56:43 -0700 (PDT)
Received: from relay15.apple.com (relay15.apple.com [17.128.113.54]) by mail-out4.apple.com (Postfix) with ESMTP id B6563B77E0B0 for <v6ops@ietf.org>; Fri, 22 Oct 2010 13:58:22 -0700 (PDT)
X-AuditID: 11807136-b7b3aae0000033cc-60-4cc1faeed7cc
Received: from gertie.apple.com (gertie.apple.com [17.151.62.15]) by relay15.apple.com (Apple SCV relay) with SMTP id A7.91.13260.EEAF1CC4; Fri, 22 Oct 2010 13:58:22 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from il0602f-dhcp196.apple.com (il0602f-dhcp196.apple.com [17.206.50.196]) by gertie.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LAP00EN4M9AUZ20@gertie.apple.com> for v6ops@ietf.org; Fri, 22 Oct 2010 13:58:22 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <618B7A4B-FDAE-4F06-8580-519FF56C4F52@cisco.com>
Date: Fri, 22 Oct 2010 13:58:21 -0700
Message-id: <74E6F793-2C81-4CB7-A571-C658146F9F75@apple.com>
References: <C8E76D0C.2B042%john_brzozowski@cable.comcast.com> <618B7A4B-FDAE-4F06-8580-519FF56C4F52@cisco.com>
To: IPv6 Operations <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 20:56:44 -0000

On Oct 22, 2010, at 13:35, Ralph Droms wrote:

> Although RFC 3633 might provide a hinting mechanism, there's no good automated way for the IGD to know what information to put into that hint.  So there is no way for the IGD to ensure it requests a sufficient prefix.

What he said, with a caveat: a gateway device that can never be field upgraded to support interior routing on the subscriber local network can probably safely send a hint for enough subnet identifier space to cover all its local interfaces.

The sticky part here is knowing whether a gateway device really cannot ever be field-upgraded.  Consider that device configurations can often be migrated in the process of replacing a hardware unit with a newer model with more capabilities.  For example, it's certainly the case that existing AirPort base stations can only support one local /64 prefix, because today they don't support IPv6 on their guest network.  But what happens when a customer replaces their current unit with a hypothetical future product that *does* support IPv6 on its guest network with a separate /64 prefix?

If changing the size of the prefix hint from /64 to /63 means the subscriber will get a new prefix delegation, despite continuing to use the same DUID as the previous unit did, then the customer is now forced to renumber.  On the other hand, if AirPort simply requests a prefix and uses whatever it can get, then a renumber may not be necessary.  Therefore, a clear disincentive to sending a prefix length hint exists.

We obviously wouldn't want to send a hint unless the network refused to delegate a prefix without one.  If that were the case, then we would want to always send a hint for /48 prefix.  I'm not sure this dance can end well for anybody.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



From brian.e.carpenter@gmail.com  Fri Oct 22 15:00:34 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24A5328C0FA for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 15:00:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.408
X-Spam-Level: 
X-Spam-Status: No, score=-102.408 tagged_above=-999 required=5 tests=[AWL=0.191, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0pYLD-Vq1HkZ for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 15:00:33 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by core3.amsl.com (Postfix) with ESMTP id 454F628C0E9 for <v6ops@ietf.org>; Fri, 22 Oct 2010 15:00:33 -0700 (PDT)
Received: by gxk3 with SMTP id 3so515109gxk.31 for <v6ops@ietf.org>; Fri, 22 Oct 2010 15:02:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=+I31M5J2paMjKOsN+gFTjUcc6KF/cI9iiH0u6q704jw=; b=UTXRKZWcvpH2ZBrs3cHwnuUwQw/dgOnfofOrk8PJtgwxrnSCDovvWbjiKxVKIFmAMN fMQ4/GoMK9FC2wSu0GfVaoW//1Oa80ggRaTF7rK0wymHVZ0WR9Dn+ZGKRJ2Y/qpQWzDS XZGMPlmhfRn17mQXJ8rGHf4W25ldsPfXXJeVc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=RWpTIwu1K2pRExDfNwgKE1vd/Sg9wfFW4eVdFnC519dVuquv+1QQaGiUyfRHhqbLQ7 n5OoJfeMcZyhT8wbkXRLOWw17bx7w54vEoJHqA+WfQEgU9i1n9L+eaSqigRjAtJSqcL6 4JVabSL3DhxY+k8sLtNFygbhBnQURuHng3S/0=
Received: by 10.229.224.201 with SMTP id ip9mr2827309qcb.16.1287784931717; Fri, 22 Oct 2010 15:02:11 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.142.15]) by mx.google.com with ESMTPS id u2sm3088981qcq.43.2010.10.22.15.02.09 (version=SSLv3 cipher=RC4-MD5); Fri, 22 Oct 2010 15:02:11 -0700 (PDT)
Message-ID: <4CC209DD.6020801@gmail.com>
Date: Sat, 23 Oct 2010 11:02:05 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ole Troan <ot@cisco.com>
References: <C8E76098.2AFB6%john_brzozowski@cable.comcast.com> <6D313496-536D-4952-8599-F4B5D8386168@cisco.com>
In-Reply-To: <6D313496-536D-4952-8599-F4B5D8386168@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 'IPv6 Operations' <v6ops@ietf.org>, "Brzozowski, John" <John_Brzozowski@cable.comcast.com>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 22:00:34 -0000

On 2010-10-23 09:30, Ole Troan wrote:
>> To add to Tony's point, I have to agree that there are folks that do not
>> have experience operating networks, specifically deploying IPv6, that seem
>> to enjoy asserting their assumptions and views.  Instead of doing this it
>> might be useful (and more productive) if folks first tried to understand how
>> various types of networks work before making recommendations, etc.
> 
> perhaps it would be equally productive if the operators tried to understand how end-users would want to build their networks?
> 
> I base my previous assumption on RFC3177. as we're on an IETF list, is there any other IETF recommendation for a different allocation model?

On 2010-10-18 07:00, Fred Baker wrote:

>> > Next week (I'm giving you an extra week's notice as I know you are busy), the IETF IPv6 Operations Working Group is initiating a two week working group last call of 
>> > 
>> > http://tools.ietf.org/html/draft-ietf-v6ops-3177bis-end-sites
>> >   "IPv6 Address Assignment to End Sites", Thomas Narten, Geoff Huston,
>> >   Rosalea Roberts

   Brian

From ot@cisco.com  Fri Oct 22 15:24:24 2010
Return-Path: <ot@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4D0A13A6987 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 15:24:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.084
X-Spam-Level: 
X-Spam-Status: No, score=-5.084 tagged_above=-999 required=5 tests=[AWL=-2.485, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7YgW2fWB+0cP for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 15:24:23 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id DA5D83A694D for <v6ops@ietf.org>; Fri, 22 Oct 2010 15:24:22 -0700 (PDT)
Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYEAOurwUyQ/khMgWdsb2JhbAChbhUBARYiIqIfnDWFSgSKTQ
X-IronPort-AV: E=Sophos;i="4.58,225,1286150400"; d="scan'208";a="11849301"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 22 Oct 2010 22:26:01 +0000
Received: from dhcp-10-61-101-160.cisco.com (dhcp-10-61-101-160.cisco.com [10.61.101.160]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id o9MMQ0Wv017285; Fri, 22 Oct 2010 22:26:00 GMT
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <ot@cisco.com>
In-Reply-To: <4CC209DD.6020801@gmail.com>
Date: Sat, 23 Oct 2010 00:26:00 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <69BB450D-B503-4F3D-8B70-7AAF17F0E95C@cisco.com>
References: <C8E76098.2AFB6%john_brzozowski@cable.comcast.com> <6D313496-536D-4952-8599-F4B5D8386168@cisco.com> <4CC209DD.6020801@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1081)
Cc: 'IPv6 Operations' <v6ops@ietf.org>, "Brzozowski, John" <John_Brzozowski@cable.comcast.com>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 22:24:24 -0000

Brian,

>>> To add to Tony's point, I have to agree that there are folks that do =
not
>>> have experience operating networks, specifically deploying IPv6, =
that seem
>>> to enjoy asserting their assumptions and views.  Instead of doing =
this it
>>> might be useful (and more productive) if folks first tried to =
understand how
>>> various types of networks work before making recommendations, etc.
>>=20
>> perhaps it would be equally productive if the operators tried to =
understand how end-users would want to build their networks?
>>=20
>> I base my previous assumption on RFC3177. as we're on an IETF list, =
is there any other IETF recommendation for a different allocation model?
>=20
> On 2010-10-18 07:00, Fred Baker wrote:
>=20
>>>> Next week (I'm giving you an extra week's notice as I know you are =
busy), the IETF IPv6 Operations Working Group is initiating a two week =
working group last call of=20
>>>>=20
>>>> http://tools.ietf.org/html/draft-ietf-v6ops-3177bis-end-sites
>>>>  "IPv6 Address Assignment to End Sites", Thomas Narten, Geoff =
Huston,
>>>>  Rosalea Roberts

do you think rfc3177bis changes this?
i.e. does it no longer advocate that "sites should get sufficient =
address space without jumping through hoops"? and that this should be a =
long lived address block assignment, not one which is subject to =
dynamically change as the end user network grows or shrinks?

I have no issue with delegation of address space of arbitrary length.
I have an issue with:
 - the expectation that an RR will know what to ask for
 - that RFC3633 provides a suitable mechanism for negotiating address =
space size

as one of the authors of RFC3633, I think it is fair that I declare what =
assumptions that document was written under. my assumption was one of =
delegation of long-lived prefixes without any negotiation, i.e. with =
assignment size set by the delegating routers. and that is in the spirit =
the document is written. if operators want to delegate prefixes in a =
different fashion, they have to be aware that the tool (3633) may not be =
up for the task.

cheers,
Ole=

From ot@cisco.com  Fri Oct 22 15:33:10 2010
Return-Path: <ot@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4964B3A68F6 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 15:33:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.378
X-Spam-Level: 
X-Spam-Status: No, score=-4.378 tagged_above=-999 required=5 tests=[AWL=-2.694, BAYES_00=-2.599, J_CHICKENPOX_32=0.6, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4qf1jX9XlpfK for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 15:33:08 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 89C933A698C for <v6ops@ietf.org>; Fri, 22 Oct 2010 15:33:04 -0700 (PDT)
Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYEADauwUyQ/khLgWdsb2JhbAChbxUBARYiIqIhnDKFSgSKTQ
X-IronPort-AV: E=Sophos;i="4.58,225,1286150400"; d="scan'208";a="11849450"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 22 Oct 2010 22:34:42 +0000
Received: from dhcp-10-61-101-160.cisco.com (dhcp-10-61-101-160.cisco.com [10.61.101.160]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id o9MMYgAJ005451; Fri, 22 Oct 2010 22:34:42 GMT
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <ot@cisco.com>
In-Reply-To: <4CC1EE1D.7090703@gmail.com>
Date: Sat, 23 Oct 2010 00:34:41 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DA25B1E4-BABB-47DB-A3E3-473C31F57017@cisco.com>
References: <C8E56757.2A817%john_brzozowski@cable.comcast.com> <4CC0A1A2.3060003@gmail.com> <11EA1C19-01B2-46B6-A0EE-6CB760F3482E@cisco.com> <4CC0AABD.6060207@gmail.com> <BF19AF42-62D0-4C9E-BDB2-1AC759881879@cisco.com> <4CC1EE1D.7090703@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>, "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2010 22:33:10 -0000

>>>>> In our protocols, prefix length clearly needs to be a parameter
>>>>> (as it is in draft-hu-pppext-ipv6cp-extensions, for example).
>>>> so now we are not only going to replicate all functions between =
DHCPv6 and RA options, but also for IPv6CP? that appears to be a bad =
idea.
>>> Well, there are arguments about why this is needed from an =
operational viewpoint
>>> in draft-hu-pppext-ipv6cp-requirements. I guess they should be =
discussed
>>> on the pppext list.
>>=20
>> so creating two protocols doing exactly the same thing is a good =
thing?
>=20
> In general, not. But if an operator is using PPP to establish sessions
> with thousand or millions of subscribers, I can well understand that =
they
> don't want to run either SLAAC or DHCPv6 as well as IPV6CP/PPP.

ND is running there anyway. and you are saying that wrapping the bits on =
the wire between two IPv6 nodes makes a big difference to the operator? =
I don't understand that argument. if you send an IPv6 prefix on the wire =
with a DHCP header wrapping or an IPv6CP control header wrapping what =
difference does that make?
neither protocol forces any different infrastructure in the backend, =
e.g. you can very well run DHCP PD on the wire, and use Radius in the =
backend.

> Anyway, as I said, that point needs to be argued in PPPEXT, not here.

as this discussion has been held on the ipng/ipv6 list for as long as I =
can remember, I think it belongs here rather than in pppext.

couldn't find the first occurrence of this debate, here is one pointer:
http://www.mail-archive.com/ipng@sunroof.eng.sun.com/msg03545.html

consensus has been many times over to make provisioning and =
configuration media independent for IPv6, and that we should not create =
L2 specific configuration mechanisms. I see this draft's proposal is to =
overturn that consensus.

cheers,
Ole=

From ek@google.com  Fri Oct 22 17:38:04 2010
Return-Path: <ek@google.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E99423A69AD for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 17:38:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.901
X-Spam-Level: 
X-Spam-Status: No, score=-105.901 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xTZT8Bqq9T9m for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 17:38:02 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 5E8C63A69AB for <v6ops@ietf.org>; Fri, 22 Oct 2010 17:38:00 -0700 (PDT)
Received: from kpbe19.cbf.corp.google.com (kpbe19.cbf.corp.google.com [172.25.105.83]) by smtp-out.google.com with ESMTP id o9N0db03004153 for <v6ops@ietf.org>; Fri, 22 Oct 2010 17:39:38 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1287794378; bh=6pWHPBpZKPxGNENtApo+CXBMVVU=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=XJWcScaVReAo7qxzAG3zyDSHi788NXxUpJtPklubWjjVk9a5RHljOukV3lJcUhGLU 4RRVu5AXh+Rl1D/ebZ6GA==
Received: from qyk1 (qyk1.prod.google.com [10.241.83.129]) by kpbe19.cbf.corp.google.com with ESMTP id o9N0dALK024979 for <v6ops@ietf.org>; Fri, 22 Oct 2010 17:39:23 -0700
Received: by qyk1 with SMTP id 1so22300qyk.10 for <v6ops@ietf.org>; Fri, 22 Oct 2010 17:39:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=7Hk3qgt7sPx9p/8jVc7MxdAb9F73SqlThkgzc2GiXGE=; b=Wb3RaQMM+jBoVpxaqXK4rZtkpxIULC8udn21/+rwRzv4F6UdctJX4JmyqmV6Y1oNP4 WwXdm8bn/hQHPSfxOObw==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=tw6pXUR4pBDiLNhaJvDtvZNwis4uzeF2bOhSTC3HXymHhveY//OKJG0KRtPHvNygq9 6ZhIaFsDyjgXChi1dMBw==
MIME-Version: 1.0
Received: by 10.229.75.1 with SMTP id w1mr2943838qcj.100.1287794349513; Fri, 22 Oct 2010 17:39:09 -0700 (PDT)
Received: by 10.229.78.228 with HTTP; Fri, 22 Oct 2010 17:39:09 -0700 (PDT)
In-Reply-To: <54E900DC635DAB4DB7A6D799B3C4CD8E016867@PLSWM12A.ad.sprint.com>
References: <C8BFD127.F082%victor.kuarsingh@gmail.com> <C8CB9E88.5599%jason_livingood@cable.comcast.com> <54E900DC635DAB4DB7A6D799B3C4CD8E016867@PLSWM12A.ad.sprint.com>
Date: Fri, 22 Oct 2010 17:39:09 -0700
Message-ID: <AANLkTi=y7hYYPBGcHr+FCXXAPsPWHEMVnEbF_7m+DSGS@mail.gmail.com>
From: Erik Kline <ek@google.com>
To: "George, Wes E IV [NTK]" <Wesley.E.George@sprint.com>
Content-Type: multipart/alternative; boundary=00163646c10abf1ca004933dfc85
X-System-Of-Record: true
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
Subject: Re: [v6ops] Soliciting feedback on draft-livingood-dns-whitelisting-implications
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Oct 2010 00:38:05 -0000

--00163646c10abf1ca004933dfc85
Content-Type: text/plain; charset=UTF-8

>
> Regarding section 5 - I'm not sure I agree with the assertion that
> whitelisting would need to be built into all auth server software for
> universal implementation. The proposal I saw for making this a little less
> manual (I would cite a draft, but I'm not aware of one - Erik Kline from
> Google presented the idea at a conference) used in-addr.arpa TXT records,
> combined with some external scripting to collect and verify IP addresses of
> resolvers to feed into whitelists. I would think that this could be
> implemented without special software in the auth server itself, but I'm by
> no means an expert on existing implementations of DNS auth/whitelist as to
> where the magic actually happens. I just bring it up as a point to verify.
> I think that there is also a subset that is sort of both of your two
> categories - ad-hoc deployment, but universal (if still mostly ad-hoc)
> coordination. Think in terms of a well-known email distro (
> whitelist@listdomain.com) or website (like peeringdb) that anyone who is
> whitelisting their auth servers can join, and when new people want to
> qualify their networks for whitelisting, they send mail to that address.
> This at least removes the barrier associated with having to find and reach
> all of the folks who are doing the whitelisting.
>

The thing you describe is here:
http://ipv6whitelist.googlecode.com/hg/spec.txt


> Section 8 - Another alternative would be DNS shared fate - only responding
> with AAAA queries to IPv6 source addresses, either at the auth or recursive
> server as a coarse way to verify that IPv6 is functioning properly before
> sending a client to use it. I am aware of two main concerns with this - that
> it doesn't actually prove functional IPv6, because it doesn't necessarily
> verify MTU and routing all work correctly, and that it would shut out any
> hosts that cannot do DNS via IPv6, either because they don't support it
> (like Windows XP), or because they have not been configured with an IPv6 DNS
> server. There are likely others, but that's all I can think of right now.


Actually, [a variant of] this is another idea on which I've recently begun
some implementation work, to see just how feasible it might be.  =)

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

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Regarding sectio=
n 5 - I&#39;m not sure I agree with the assertion that whitelisting would n=
eed to be built into all auth server software for universal implementation.=
 The proposal I saw for making this a little less manual (I would cite a dr=
aft, but I&#39;m not aware of one - Erik Kline from Google presented the id=
ea at a conference) used in-addr.arpa TXT records, combined with some exter=
nal scripting to collect and verify IP addresses of resolvers to feed into =
whitelists. I would think that this could be implemented without special so=
ftware in the auth server itself, but I&#39;m by no means an expert on exis=
ting implementations of DNS auth/whitelist as to where the magic actually h=
appens. I just bring it up as a point to verify.<br>

I think that there is also a subset that is sort of both of your two catego=
ries - ad-hoc deployment, but universal (if still mostly ad-hoc) coordinati=
on. Think in terms of a well-known email distro (<a href=3D"mailto:whitelis=
t@listdomain.com">whitelist@listdomain.com</a>) or website (like peeringdb)=
 that anyone who is whitelisting their auth servers can join, and when new =
people want to qualify their networks for whitelisting, they send mail to t=
hat address. This at least removes the barrier associated with having to fi=
nd and reach all of the folks who are doing the whitelisting.<br>
</blockquote><div><br></div><div>The thing you describe is here: =C2=A0<a h=
ref=3D"http://ipv6whitelist.googlecode.com/hg/spec.txt">http://ipv6whitelis=
t.googlecode.com/hg/spec.txt</a></div><meta http-equiv=3D"content-type" con=
tent=3D"text/html; charset=3Dutf-8"><div>
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex;">
Section 8 - Another alternative would be DNS shared fate - only responding =
with AAAA queries to IPv6 source addresses, either at the auth or recursive=
 server as a coarse way to verify that IPv6 is functioning properly before =
sending a client to use it. I am aware of two main concerns with this - tha=
t it doesn&#39;t actually prove functional IPv6, because it doesn&#39;t nec=
essarily verify MTU and routing all work correctly, and that it would shut =
out any hosts that cannot do DNS via IPv6, either because they don&#39;t su=
pport it (like Windows XP), or because they have not been configured with a=
n IPv6 DNS server. There are likely others, but that&#39;s all I can think =
of right now.</blockquote>
<div><br></div><div>Actually, [a variant of] this is another idea on which =
I&#39;ve recently begun some implementation work, to see just how feasible =
it might be. =C2=A0=3D)</div></div>

--00163646c10abf1ca004933dfc85--

From john_brzozowski@cable.comcast.com  Fri Oct 22 18:09:35 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A87603A695D for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 18:09:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.085
X-Spam-Level: 
X-Spam-Status: No, score=-108.085 tagged_above=-999 required=5 tests=[AWL=0.378, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 66cf2F2IqkKG for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 18:09:34 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id E40CE3A6955 for <v6ops@ietf.org>; Fri, 22 Oct 2010 18:09:33 -0700 (PDT)
Received: from ([24.40.55.42]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.101303052; Fri, 22 Oct 2010 21:10:48 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by PACDCEXHUB01.cable.comcast.com ([fe80::d1e7:20b5:9b63:21a6%12]) with mapi id 14.01.0255.000; Fri, 22 Oct 2010 21:10:48 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: Ole Troan <ot@cisco.com>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again
Thread-Index: ActyIMiWGAgvL+p1b0efThcxErp8nwAKLVEAAAFqsgA=
Date: Sat, 23 Oct 2010 01:10:47 +0000
Message-ID: <C8E7AE66.2B0CB%john_brzozowski@cable.comcast.com>
In-Reply-To: <6D313496-536D-4952-8599-F4B5D8386168@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <01B5BB0CE92FBE41865FAC27C71FDA8F@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 'IPv6 Operations' <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Oct 2010 01:09:35 -0000

On 10/22/10 4:30 PM, "Ole Troan" <ot@cisco.com> wrote:

>> To add to Tony's point, I have to agree that there are folks that do not
>> have experience operating networks, specifically deploying IPv6, that se=
em
>> to enjoy asserting their assumptions and views.  Instead of doing this i=
t
>> might be useful (and more productive) if folks first tried to understand=
 how
>> various types of networks work before making recommendations, etc.
>=20
> perhaps it would be equally productive if the operators tried to understa=
nd
> how end-users would want to build their networks?
[jjmb] 100% agree, this is a fair a statement.
>=20
> I base my previous assumption on RFC3177. as we're on an IETF list, is th=
ere
> any other IETF recommendation for a different allocation model?
[jjmb] I am basing my statements on trial experience at this time, which do
not necessarily align with RFC3177.  I will see about offering some feedbac=
k
on updates to RFC3177, seems like a good idea.
>=20
> cheers,
> Ole
>=20
>=20
>=20
>>> Ole Troan wrote:
>>>> ...
>>>> so creating two protocols doing exactly the same thing is a good thing=
?
>>>=20
>>> When the target environments are different -- YES.  Having different
>>> solutions for managed vs. unmanaged environments that actually are
>>> completely self-contained is required. The failure to date is that too =
many
>>> people want to assert their view of how to manage a network onto other
>>> people's environments. Both operational models are valid, so independen=
t and
>>> fully functional tools need to exist for each.
>>>=20
>>> Tony
>>>=20
>>>=20
>>>=20
>>=20
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> John Jason Brzozowski
>> Comcast Cable
>> e) mailto:john_brzozowski@cable.comcast.com
>> o) 609-377-6594
>> m) 484-962-0060
>> w) http://www.comcast6.net
>> =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
>>=20
>=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From john_brzozowski@cable.comcast.com  Fri Oct 22 18:10:23 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0EE5C3A6819 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 18:10:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.1
X-Spam-Level: 
X-Spam-Status: No, score=-108.1 tagged_above=-999 required=5 tests=[AWL=0.363,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368,  RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31b4aTCvEMLb for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 18:10:12 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 04B4728C0F7 for <v6ops@ietf.org>; Fri, 22 Oct 2010 18:10:04 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.101303123; Fri, 22 Oct 2010 21:11:40 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by PACDCEXHUB02.cable.comcast.com ([fe80::11d4:f530:37a0:9f4e%12]) with mapi id 14.01.0255.000; Fri, 22 Oct 2010 21:11:40 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: "Brian E. Carpenter" <brian.e.carpenter@gmail.com>, Ole Troan <ot@cisco.com>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again
Thread-Index: ActyIMiWGAgvL+p1b0efThcxErp8nwAKLVEAAAMzHoD///H6AA==
Date: Sat, 23 Oct 2010 01:11:38 +0000
Message-ID: <C8E7AE9A.2B0CE%john_brzozowski@cable.comcast.com>
In-Reply-To: <4CC209DD.6020801@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F414C39E68C266479EC9B01754DF144A@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 'IPv6 Operations' <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Oct 2010 01:10:23 -0000

Perfect timing...thanks Brian.


On 10/22/10 6:02 PM, "Brian E. Carpenter" <brian.e.carpenter@gmail.com>
wrote:

> On 2010-10-23 09:30, Ole Troan wrote:
>>> To add to Tony's point, I have to agree that there are folks that do no=
t
>>> have experience operating networks, specifically deploying IPv6, that s=
eem
>>> to enjoy asserting their assumptions and views.  Instead of doing this =
it
>>> might be useful (and more productive) if folks first tried to understan=
d how
>>> various types of networks work before making recommendations, etc.
>>=20
>> perhaps it would be equally productive if the operators tried to underst=
and
>> how end-users would want to build their networks?
>>=20
>> I base my previous assumption on RFC3177. as we're on an IETF list, is t=
here
>> any other IETF recommendation for a different allocation model?
>=20
> On 2010-10-18 07:00, Fred Baker wrote:
>=20
>>>> Next week (I'm giving you an extra week's notice as I know you are bus=
y),
>>>> the IETF IPv6 Operations Working Group is initiating a two week workin=
g
>>>> group last call of
>>>>=20
>>>> http://tools.ietf.org/html/draft-ietf-v6ops-3177bis-end-sites
>>>>   "IPv6 Address Assignment to End Sites", Thomas Narten, Geoff Huston,
>>>>   Rosalea Roberts
>=20
>    Brian

=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
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From john_brzozowski@cable.comcast.com  Fri Oct 22 18:18:04 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1CCF03A69AB for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 18:18:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.115
X-Spam-Level: 
X-Spam-Status: No, score=-108.115 tagged_above=-999 required=5 tests=[AWL=0.348, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0gnVecqFC1gn for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 18:18:02 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id AF6AE3A689D for <v6ops@ietf.org>; Fri, 22 Oct 2010 18:18:02 -0700 (PDT)
Received: from ([24.40.55.40]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.101304267; Fri, 22 Oct 2010 21:19:37 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by pacdcexhub03.cable.comcast.com ([fe80::d1dd:b302:b617:3755%12]) with mapi id 14.01.0255.000; Fri, 22 Oct 2010 21:19:36 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: Ole Troan <ot@cisco.com>, "Brian E. Carpenter" <brian.e.carpenter@gmail.com>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again
Thread-Index: ActyIMiWGAgvL+p1b0efThcxErp8nwAKLVEAAAMzHoAAANXVAP//7YMA
Date: Sat, 23 Oct 2010 01:19:36 +0000
Message-ID: <C8E7B076.2B105%john_brzozowski@cable.comcast.com>
In-Reply-To: <69BB450D-B503-4F3D-8B70-7AAF17F0E95C@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1FC2EE44C40B1A49AEF6A77EC34DFE9F@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: 'IPv6 Operations' <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Oct 2010 01:18:04 -0000

On 10/22/10 6:26 PM, "Ole Troan" <ot@cisco.com> wrote:

> Brian,
>=20
>>>> To add to Tony's point, I have to agree that there are folks that do n=
ot
>>>> have experience operating networks, specifically deploying IPv6, that =
seem
>>>> to enjoy asserting their assumptions and views.  Instead of doing this=
 it
>>>> might be useful (and more productive) if folks first tried to understa=
nd
>>>> how
>>>> various types of networks work before making recommendations, etc.
>>>=20
>>> perhaps it would be equally productive if the operators tried to unders=
tand
>>> how end-users would want to build their networks?
>>>=20
>>> I base my previous assumption on RFC3177. as we're on an IETF list, is =
there
>>> any other IETF recommendation for a different allocation model?
>>=20
>> On 2010-10-18 07:00, Fred Baker wrote:
>>=20
>>>>> Next week (I'm giving you an extra week's notice as I know you are bu=
sy),
>>>>> the IETF IPv6 Operations Working Group is initiating a two week worki=
ng
>>>>> group last call of
>>>>>=20
>>>>> http://tools.ietf.org/html/draft-ietf-v6ops-3177bis-end-sites
>>>>>  "IPv6 Address Assignment to End Sites", Thomas Narten, Geoff Huston,
>>>>>  Rosalea Roberts
>=20
> do you think rfc3177bis changes this?
> i.e. does it no longer advocate that "sites should get sufficient address
> space without jumping through hoops"? and that this should be a long live=
d
> address block assignment, not one which is subject to dynamically change =
as
> the end user network grows or shrinks?
[jjmb] the not changing and long lived parts are not real world by default.
Size changing seems like a reasonable expectation.
>=20
> I have no issue with delegation of address space of arbitrary length.
> I have an issue with:
>  - the expectation that an RR will know what to ask for
[jjmb] again, I disagree.  Sorry.
>  - that RFC3633 provides a suitable mechanism for negotiating address spa=
ce
> size
>=20
> as one of the authors of RFC3633, I think it is fair that I declare what
> assumptions that document was written under. my assumption was one of
> delegation of long-lived prefixes without any negotiation, i.e. with
> assignment size set by the delegating routers. and that is in the spirit =
the
> document is written. if operators want to delegate prefixes in a differen=
t
> fashion, they have to be aware that the tool (3633) may not be up for the
> task.
[jjmb] when RFC3633 was written how many networks deployed prefix delegatio=
n
widely?
>=20
> cheers,
> Ole

=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
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From john_brzozowski@cable.comcast.com  Fri Oct 22 18:23:32 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D51B13A6804 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 18:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.678
X-Spam-Level: 
X-Spam-Status: No, score=-107.678 tagged_above=-999 required=5 tests=[AWL=-0.115, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2s0VDaFDZ969 for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 18:23:28 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 51C923A689D for <v6ops@ietf.org>; Fri, 22 Oct 2010 18:23:27 -0700 (PDT)
Received: from ([24.40.55.42]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.101304941; Fri, 22 Oct 2010 21:25:01 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by PACDCEXHUB01.cable.comcast.com ([fe80::d1e7:20b5:9b63:21a6%12]) with mapi id 14.01.0255.000; Fri, 22 Oct 2010 21:25:01 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: =?iso-8859-1?Q?Ole_Tr=F8an?= <otroan@employees.org>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
Thread-Index: ActyIazf2T6t3TrIl0mUPJfZCE79dQAIhAqA//+/WgCAAEx7AIAADvuA
Date: Sat, 23 Oct 2010 01:25:00 +0000
Message-ID: <C8E7B1BB.2B12B%john_brzozowski@cable.comcast.com>
In-Reply-To: <3C8235FC-FB34-483E-B0E3-613409A04457@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <9839D03DD0AA7F4B82DCDDA91D72052E@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Oct 2010 01:23:32 -0000

On 10/22/10 4:31 PM, "Ole Tr=F8an" <otroan@employees.org> wrote:

> John,
>=20
>> The IGD in this would have to know about the sensor network to ensure
>> traffic to it can be routed right?  The IGD at the edge of the customer
>> premise needs to have some awareness some where no?  Even if the IGD was
>> issue a /56, it would still have to support some form of hierarchical PD=
 to
>> provision and enable the sensor network right?
>=20
> are you suggesting that one shouldn't be able to build IPv6 home networks
> using manual configuration?
[jjmb] nope
>=20
> cheers,
> Ole
>=20
>=20
>>> John - regarding the size of the prefix to request, here is a simple
>>> example.
>>> We expect Zigbee IP sensor network to connect through a dual-interface
>>> gateway
>>> to the home network and then to the IGD.  The sensor network needs a pr=
efix
>>> for the 802.15.4 network, but the IGD only has a single interface.  How=
 does
>>> the IGD know to ask for a prefix shorter than /64?  In general, how doe=
s the
>>> IGD know, a priori, the architecture of the residential network so it c=
an
>>> ask
>>> for an appropriately sized prefix?
>>>=20
>>> - Ralph
>>>=20
>>> On Oct 22, 2010, at 3:45 PM 10/22/10, Brzozowski, John wrote:
>>>=20
>>>> On 10/21/10 5:03 AM, "Ole Tr=F8an" <otroan@employees.org> wrote:
>>>>=20
>>>>> John,
>>>>>=20
>>>>> [...]
>>>>>=20
>>>>>>> as more advanced home networks evolve, it is going to be difficult =
for
>>>>>>> the
>>>>>>> border router to know the number of links that exists or may appear=
 in
>>>>>>> the
>>>>>>> future. the intention with PD was always that the prefix size was a
>>>>>>> contractual matter, not one which is negotiated 'real time'.
>>>>>> [jjmb] Hmmm...RFC3633 is a contract?
>>>>>=20
>>>>> a fax replacement. I'd expect when I buy service from an ISP the cont=
ract
>>>>> between me and the ISP also includes the size of the prefix I will be
>>>>> assigned
>>>>> as well as guarantees about its lifetime.
>>>> [jjmb] as stated in other emails we are dealing with protocols not
>>>> contracts.  Brian stated it well, this is between the subscriber and
>>>> operators, not the IETF.
>>>>>=20
>>>>> currently the hint in 3633 is just a MAY and even then there is only =
text
>>>>> suggesting that the requesting router should include a prefix, to hin=
t to
>>>>> the
>>>>> server that it would like to receive the same prefix that was presuma=
bly
>>>>> previously delegated. WPD-2 in draft-ietf-v6ops-ipv6-cpe-router-07
>>>>> includes
>>>>> a
>>>>> MAY hint to the delegating router about the size it would require and
>>>>> WPD-3
>>>>> states it MUST accept a different prefix size.
>>>> [jjmb] operators also have there own requirements, which may vary.  I =
for
>>>> one will be requiring the hint.
>>>>>=20
>>>>> DHCPv6 PD is a mechanism where the control and policy is at the DHCPv=
6 PD
>>>>> server.
>>>>>=20
>>>>> you could write a proposal to strengthen this language, but I would p=
osit
>>>>> that
>>>>> the IPv6 CE is in no position to know a priori what size to ask for.
>>>> [jjmb] really?  An IPv6 CPE has no way to determine how many and what =
sort
>>>> of interfaces it is built to support or configure with?  It is not awa=
re of
>>>> its configuration which in turn would drive its provisioning request? =
 IMO
>>>> this is most certainly something an IGD can and should be programmatic=
ally
>>>> aware of specifically when initializing.
>>>>>=20
>>>>>>> mind you, I'm not an operator and I would surely like to understand=
 the
>>>>>>> reasons why doing more negotiation would be useful? of course, one =
has
>>>>>>> to
>>>>>>> expect that every CPE supports a delegation of <=3D/64. are there r=
eally
>>>>>>> implementations which only supports a single /64? if so, I'd claim
>>>>>>> that's
>>>>>>> a
>>>>>>> bug and not in line with 3633 nor the basic ipv6 ce router requirem=
ents
>>>>>>> specification.
>>>>>> [jjmb] having flexibility is a must, making substantial fixed decisi=
ons
>>>>>> this
>>>>>> early can result in complications or even limitations.  I absolutely
>>>>>> agree
>>>>>> with one of your comments above, home networks will evolve.  As such=
 we
>>>>>> need
>>>>>> to ensure we have the ability to accommodate the same over time.  An
>>>>>> incremental approach supports this goal.  Yes there are implementati=
ons
>>>>>> that
>>>>>> only support a /64, nothing shorter largely because they physically =
do
>>>>>> not
>>>>>> have the need and/or ability to support anything else.  If a device =
has
>>>>>> only
>>>>>> one IPv4 LAN and cannot be upgraded to support more (including
>>>>>> hierarchical
>>>>>> PD) why would this be a bug?  I think we will have to agree to disag=
ree,
>>>>>> I
>>>>>> do not view this as a bug.  I do think this is inline with RFC3633 a=
nd
>>>>>> the
>>>>>> IPv6 CPE router requirements.  A lot of work has been done over the =
past
>>>>>> couple of years to get some existing routers to be software upgradab=
le to
>>>>>> support native IPv6 as such there may be some devices with lesser
>>>>>> capabilities.  Having a minimal level of support for IPv6 is better =
than
>>>>>> none, right?  Finally, there may be a wide range of routers built ov=
er
>>>>>> time
>>>>>> that range in caliber and features.
>>>>>=20
>>>>> I think we are in agreement. I'm certainly not suggesting that e.g. a=
 /56
>>>>> is
>>>>> the only way it can be done. nor that delegations have to be rigid. e=
very
>>>>> implementation must support any prefix length thrown at it, with the
>>>>> exception
>>>>> of getting a so small address block that it doesn't get a single /64 =
per
>>>>> link.
>>>>>=20
>>>>> I'm just saying that the rfc3633 "hint" may not be very useful; and t=
hat
>>>>> delegating the absolute minimum address block required may be problem=
atic.
>>>>> for
>>>>> example if the CE after a delegation is done determines that it needs=
 a
>>>>> larger
>>>>> block, the home network may have to be renumbered.
>>>> [jjmb] if a CE can only support the minimum why is it a problem for it=
 to
>>>> be
>>>> provisioning with the minimum?  If a CE after its initial provisioning=
 is
>>>> reconfigured to support additional VLANs renumbering will have to occu=
r
>>>> anyway no?
>>>>>=20
>>>>> thinking of DHCP PD as a fax replacement, lets you not have to think =
about
>>>>> all
>>>>> the hard corner cases. ;-)
>>>> [jjmb] I still am not clear to the reference to fax replacement, sorry=
.
>>>>>=20
>>>>> cheers,
>>>>> Ole
>>>>=20
>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>> John Jason Brzozowski
>>>> Comcast Cable
>>>> e) mailto:john_brzozowski@cable.comcast.com
>>>> o) 609-377-6594
>>>> m) 484-962-0060
>>>> w) http://www.comcast6.net
>>>> =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
>>>>=20
>>>> _______________________________________________
>>>> v6ops mailing list
>>>> v6ops@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>=20
>>=20
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> John Jason Brzozowski
>> Comcast Cable
>> e) mailto:john_brzozowski@cable.comcast.com
>> o) 609-377-6594
>> m) 484-962-0060
>> w) http://www.comcast6.net
>> =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
>>=20
>=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From john_brzozowski@cable.comcast.com  Fri Oct 22 18:25:18 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4D7C23A69AD for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 18:25:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.824
X-Spam-Level: 
X-Spam-Status: No, score=-107.824 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rm+RAo0uFvPS for <v6ops@core3.amsl.com>; Fri, 22 Oct 2010 18:25:16 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 75C833A6804 for <v6ops@ietf.org>; Fri, 22 Oct 2010 18:25:16 -0700 (PDT)
Received: from ([24.40.55.40]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.101305409; Fri, 22 Oct 2010 21:26:50 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by pacdcexhub03.cable.comcast.com ([fe80::d1dd:b302:b617:3755%12]) with mapi id 14.01.0255.000; Fri, 22 Oct 2010 21:26:49 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: Ralph Droms <rdroms@cisco.com>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
Thread-Index: ActyKDTI2T6t3TrIl0mUPJfZCE79dQAIgyUAAAHJBYA=
Date: Sat, 23 Oct 2010 01:26:48 +0000
Message-ID: <C8E7B227.2B131%john_brzozowski@cable.comcast.com>
In-Reply-To: <618B7A4B-FDAE-4F06-8580-519FF56C4F52@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <54D54F840FD3014796D41215913A220A@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Oct 2010 01:25:18 -0000

To be specific, the IGD could know what it can support based on its
configuration, etc., however, I do agree it could be difficult if not
impossible for the IGG to predict what will be connect to it in the premise=
.

John

On 10/22/10 4:35 PM, "Ralph Droms" <rdroms@cisco.com> wrote:

> Although RFC 3633 might provide a hinting mechanism, there's no good auto=
mated
> way for the IGD to know what information to put into that hint.  So there=
 is
> no way for the IGD to ensure it requests a sufficient prefix.
>=20
> - Ralph
>=20
> On Oct 22, 2010, at 4:32 PM 10/22/10, Brzozowski, John wrote:
>=20
>> To be clear, either approach has scale and/or operational challenges.
>>=20
>> So I am back to how does an IGD ensure that what it requests a prefix of
>> sufficient size from the operator?  RFC3633 loosely provides a mechanism=
,
>> why not use it?
>>=20
>>=20
>> On 10/22/10 4:28 PM, "Ralph Droms" <rdroms@cisco.com> wrote:
>>=20
>>> Doesn't seem like that will scale very well if there are more than a co=
uple
>>> of
>>> routers in the home network.
>>>=20
>>> But what do I know?  I'm not an SP network operator.
>>>=20
>>> - Ralph
>>>=20
>>>=20
>>> On Oct 22, 2010, at 4:26 PM 10/22/10, Brzozowski, John wrote:
>>>=20
>>>> Provisioning large blocks across the board may not reliably work eithe=
r.
>>>>=20
>>>> Perhaps the IGD should simply relay downstream IA_PD requests from wit=
hin
>>>> the premise and let the other RRs negotiate their own prefix requests =
with
>>>> the operator DHCPv6 servers?
>>>>=20
>>>> John
>>>>=20
>>>> On 10/22/10 4:20 PM, "Ralph Droms" <rdroms@cisco.com> wrote:
>>>>=20
>>>>> Just because the IGD has the capability to do hierarchical PD doesn't=
 mean
>>>>> it
>>>>> knows how many prefixes to ask for.
>>>>>=20
>>>>> - Ralph
>>>>>=20
>>>>> On Oct 22, 2010, at 4:18 PM 10/22/10, Brzozowski, John wrote:
>>>>>=20
>>>>>> The IGD has to some degree of awareness to ensure it gets provisione=
d
>>>>>> appropriately and can in turn support whatever is connected to it wi=
thin
>>>>>> the
>>>>>> premise.
>>>>>>=20
>>>>>>=20
>>>>>> On 10/22/10 4:06 PM, "Ralph Droms" <rdroms@cisco.com> wrote:
>>>>>>=20
>>>>>>>=20
>>>>>>> On Oct 22, 2010, at 3:57 PM 10/22/10, Brzozowski, John wrote:
>>>>>>>=20
>>>>>>>> Ralph,
>>>>>>>>=20
>>>>>>>> The IGD in this would have to know about the sensor network to ens=
ure
>>>>>>>> traffic to it can be routed right?  The IGD at the edge of the cus=
tomer
>>>>>>>> premise needs to have some awareness some where no?  Even if the I=
GD
>>>>>>>> was
>>>>>>>> issue a /56, it would still have to support some form of hierarchi=
cal
>>>>>>>> PD
>>>>>>>> to
>>>>>>>> provision and enable the sensor network right?
>>>>>>>>=20
>>>>>>>> John
>>>>>>>=20
>>>>>>> Yes.
>>>>>>>=20
>>>>>>> - Ralph
>>>>>>>=20
>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> On 10/22/10 3:49 PM, "Ralph Droms" <rdroms@cisco.com> wrote:
>>>>>>>>=20
>>>>>>>>> John - regarding the size of the prefix to request, here is a sim=
ple
>>>>>>>>> example.
>>>>>>>>> We expect Zigbee IP sensor network to connect through a dual-inte=
rface
>>>>>>>>> gateway
>>>>>>>>> to the home network and then to the IGD.  The sensor network need=
s a
>>>>>>>>> prefix
>>>>>>>>> for the 802.15.4 network, but the IGD only has a single interface=
.
>>>>>>>>> How
>>>>>>>>> does
>>>>>>>>> the IGD know to ask for a prefix shorter than /64?  In general, h=
ow
>>>>>>>>> does
>>>>>>>>> the
>>>>>>>>> IGD know, a priori, the architecture of the residential network s=
o it
>>>>>>>>> can
>>>>>>>>> ask
>>>>>>>>> for an appropriately sized prefix?
>>>>>>>>>=20
>>>>>>>>> - Ralph
>>>>>>>>>=20
>>>>>>>>> On Oct 22, 2010, at 3:45 PM 10/22/10, Brzozowski, John wrote:
>>>>>>>>>=20
>>>>>>>>>> On 10/21/10 5:03 AM, "Ole Tr=F8an" <otroan@employees.org> wrote:
>>>>>>>>>>=20
>>>>>>>>>>> John,
>>>>>>>>>>>=20
>>>>>>>>>>> [...]
>>>>>>>>>>>=20
>>>>>>>>>>>> as more advanced home networks evolve, it is going to be diffi=
cult
>>>>>>>>>>>> for
>>>>>>>>>>>> the
>>>>>>>>>>>> border router to know the number of links that exists or may a=
ppear
>>>>>>>>>>>> in
>>>>>>>>>>>> the
>>>>>>>>>>>> future. the intention with PD was always that the prefix size =
was a
>>>>>>>>>>>> contractual matter, not one which is negotiated 'real time'.
>>>>>>>>>>>> [jjmb] Hmmm...RFC3633 is a contract?
>>>>>>>>>>>=20
>>>>>>>>>>> a fax replacement. I'd expect when I buy service from an ISP th=
e
>>>>>>>>>>> contract
>>>>>>>>>>> between me and the ISP also includes the size of the prefix I w=
ill
>>>>>>>>>>> be
>>>>>>>>>>> assigned
>>>>>>>>>>> as well as guarantees about its lifetime.
>>>>>>>>>> [jjmb] as stated in other emails we are dealing with protocols n=
ot
>>>>>>>>>> contracts.  Brian stated it well, this is between the subscriber=
 and
>>>>>>>>>> operators, not the IETF.
>>>>>>>>>>>=20
>>>>>>>>>>> currently the hint in 3633 is just a MAY and even then there is=
 only
>>>>>>>>>>> text
>>>>>>>>>>> suggesting that the requesting router should include a prefix, =
to
>>>>>>>>>>> hint
>>>>>>>>>>> to
>>>>>>>>>>> the
>>>>>>>>>>> server that it would like to receive the same prefix that was
>>>>>>>>>>> presumably
>>>>>>>>>>> previously delegated. WPD-2 in draft-ietf-v6ops-ipv6-cpe-router=
-07
>>>>>>>>>>> includes
>>>>>>>>>>> a
>>>>>>>>>>> MAY hint to the delegating router about the size it would requi=
re
>>>>>>>>>>> and
>>>>>>>>>>> WPD-3
>>>>>>>>>>> states it MUST accept a different prefix size.
>>>>>>>>>> [jjmb] operators also have there own requirements, which may var=
y.  I
>>>>>>>>>> for
>>>>>>>>>> one will be requiring the hint.
>>>>>>>>>>>=20
>>>>>>>>>>> DHCPv6 PD is a mechanism where the control and policy is at the
>>>>>>>>>>> DHCPv6
>>>>>>>>>>> PD
>>>>>>>>>>> server.
>>>>>>>>>>>=20
>>>>>>>>>>> you could write a proposal to strengthen this language, but I w=
ould
>>>>>>>>>>> posit
>>>>>>>>>>> that
>>>>>>>>>>> the IPv6 CE is in no position to know a priori what size to ask=
 for.
>>>>>>>>>> [jjmb] really?  An IPv6 CPE has no way to determine how many and=
 what
>>>>>>>>>> sort
>>>>>>>>>> of interfaces it is built to support or configure with?  It is n=
ot
>>>>>>>>>> aware
>>>>>>>>>> of
>>>>>>>>>> its configuration which in turn would drive its provisioning req=
uest?
>>>>>>>>>> IMO
>>>>>>>>>> this is most certainly something an IGD can and should be
>>>>>>>>>> programmatically
>>>>>>>>>> aware of specifically when initializing.
>>>>>>>>>>>=20
>>>>>>>>>>>> mind you, I'm not an operator and I would surely like to under=
stand
>>>>>>>>>>>> the
>>>>>>>>>>>> reasons why doing more negotiation would be useful? of course,=
 one
>>>>>>>>>>>> has
>>>>>>>>>>>> to
>>>>>>>>>>>> expect that every CPE supports a delegation of <=3D/64. are th=
ere
>>>>>>>>>>>> really
>>>>>>>>>>>> implementations which only supports a single /64? if so, I'd c=
laim
>>>>>>>>>>>> that's
>>>>>>>>>>>> a
>>>>>>>>>>>> bug and not in line with 3633 nor the basic ipv6 ce router
>>>>>>>>>>>> requirements
>>>>>>>>>>>> specification.
>>>>>>>>>>>> [jjmb] having flexibility is a must, making substantial fixed
>>>>>>>>>>>> decisions
>>>>>>>>>>>> this
>>>>>>>>>>>> early can result in complications or even limitations.  I
>>>>>>>>>>>> absolutely
>>>>>>>>>>>> agree
>>>>>>>>>>>> with one of your comments above, home networks will evolve.  A=
s
>>>>>>>>>>>> such
>>>>>>>>>>>> we
>>>>>>>>>>>> need
>>>>>>>>>>>> to ensure we have the ability to accommodate the same over tim=
e.
>>>>>>>>>>>> An
>>>>>>>>>>>> incremental approach supports this goal.  Yes there are
>>>>>>>>>>>> implementations
>>>>>>>>>>>> that
>>>>>>>>>>>> only support a /64, nothing shorter largely because they physi=
cally
>>>>>>>>>>>> do
>>>>>>>>>>>> not
>>>>>>>>>>>> have the need and/or ability to support anything else.  If a d=
evice
>>>>>>>>>>>> has
>>>>>>>>>>>> only
>>>>>>>>>>>> one IPv4 LAN and cannot be upgraded to support more (including
>>>>>>>>>>>> hierarchical
>>>>>>>>>>>> PD) why would this be a bug?  I think we will have to agree to
>>>>>>>>>>>> disagree,
>>>>>>>>>>>> I
>>>>>>>>>>>> do not view this as a bug.  I do think this is inline with RFC=
3633
>>>>>>>>>>>> and
>>>>>>>>>>>> the
>>>>>>>>>>>> IPv6 CPE router requirements.  A lot of work has been done ove=
r the
>>>>>>>>>>>> past
>>>>>>>>>>>> couple of years to get some existing routers to be software
>>>>>>>>>>>> upgradable
>>>>>>>>>>>> to
>>>>>>>>>>>> support native IPv6 as such there may be some devices with les=
ser
>>>>>>>>>>>> capabilities.  Having a minimal level of support for IPv6 is b=
etter
>>>>>>>>>>>> than
>>>>>>>>>>>> none, right?  Finally, there may be a wide range of routers bu=
ilt
>>>>>>>>>>>> over
>>>>>>>>>>>> time
>>>>>>>>>>>> that range in caliber and features.
>>>>>>>>>>>=20
>>>>>>>>>>> I think we are in agreement. I'm certainly not suggesting that =
e.g.
>>>>>>>>>>> a
>>>>>>>>>>> /56
>>>>>>>>>>> is
>>>>>>>>>>> the only way it can be done. nor that delegations have to be ri=
gid.
>>>>>>>>>>> every
>>>>>>>>>>> implementation must support any prefix length thrown at it, wit=
h the
>>>>>>>>>>> exception
>>>>>>>>>>> of getting a so small address block that it doesn't get a singl=
e /64
>>>>>>>>>>> per
>>>>>>>>>>> link.
>>>>>>>>>>>=20
>>>>>>>>>>> I'm just saying that the rfc3633 "hint" may not be very useful;=
 and
>>>>>>>>>>> that
>>>>>>>>>>> delegating the absolute minimum address block required may be
>>>>>>>>>>> problematic.
>>>>>>>>>>> for
>>>>>>>>>>> example if the CE after a delegation is done determines that it
>>>>>>>>>>> needs
>>>>>>>>>>> a
>>>>>>>>>>> larger
>>>>>>>>>>> block, the home network may have to be renumbered.
>>>>>>>>>> [jjmb] if a CE can only support the minimum why is it a problem =
for
>>>>>>>>>> it
>>>>>>>>>> to
>>>>>>>>>> be
>>>>>>>>>> provisioning with the minimum?  If a CE after its initial
>>>>>>>>>> provisioning
>>>>>>>>>> is
>>>>>>>>>> reconfigured to support additional VLANs renumbering will have t=
o
>>>>>>>>>> occur
>>>>>>>>>> anyway no?
>>>>>>>>>>>=20
>>>>>>>>>>> thinking of DHCP PD as a fax replacement, lets you not have to =
think
>>>>>>>>>>> about
>>>>>>>>>>> all
>>>>>>>>>>> the hard corner cases. ;-)
>>>>>>>>>> [jjmb] I still am not clear to the reference to fax replacement,
>>>>>>>>>> sorry.
>>>>>>>>>>>=20
>>>>>>>>>>> cheers,
>>>>>>>>>>> Ole
>>>>>>>>>>=20
>>>>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>>>>>>>> John Jason Brzozowski
>>>>>>>>>> Comcast Cable
>>>>>>>>>> e) mailto:john_brzozowski@cable.comcast.com
>>>>>>>>>> o) 609-377-6594
>>>>>>>>>> m) 484-962-0060
>>>>>>>>>> w) http://www.comcast6.net
>>>>>>>>>> =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
>>>>>>>>>>=20
>>>>>>>>>> _______________________________________________
>>>>>>>>>> v6ops mailing list
>>>>>>>>>> v6ops@ietf.org
>>>>>>>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>>>>>>>=20
>>>>>>>>=20
>>>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>>>>>> John Jason Brzozowski
>>>>>>>> Comcast Cable
>>>>>>>> e) mailto:john_brzozowski@cable.comcast.com
>>>>>>>> o) 609-377-6594
>>>>>>>> m) 484-962-0060
>>>>>>>> w) http://www.comcast6.net
>>>>>>>> =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
>>>>>>>>=20
>>>>>>>=20
>>>>>>=20
>>>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>>>> John Jason Brzozowski
>>>>>> Comcast Cable
>>>>>> e) mailto:john_brzozowski@cable.comcast.com
>>>>>> o) 609-377-6594
>>>>>> m) 484-962-0060
>>>>>> w) http://www.comcast6.net
>>>>>> =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
>>>>>>=20
>>>>>=20
>>>>=20
>>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>> John Jason Brzozowski
>>>> Comcast Cable
>>>> e) mailto:john_brzozowski@cable.comcast.com
>>>> o) 609-377-6594
>>>> m) 484-962-0060
>>>> w) http://www.comcast6.net
>>>> =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
>>>>=20
>>>=20
>>=20
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> John Jason Brzozowski
>> Comcast Cable
>> e) mailto:john_brzozowski@cable.comcast.com
>> o) 609-377-6594
>> m) 484-962-0060
>> w) http://www.comcast6.net
>> =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
>>=20
>=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From wwwrun@rfc-editor.org  Fri Oct 22 18:34:42 2010
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6133428C129; Fri, 22 Oct 2010 18:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.401
X-Spam-Level: 
X-Spam-Status: No, score=-102.401 tagged_above=-999 required=5 tests=[AWL=0.199, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XktmMn1EDjdJ; Fri, 22 Oct 2010 18:34:41 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 541AC28C128; Fri, 22 Oct 2010 18:34:41 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B73A7E0702; Fri, 22 Oct 2010 18:36:20 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20101023013620.B73A7E0702@rfc-editor.org>
Date: Fri, 22 Oct 2010 18:36:20 -0700 (PDT)
Cc: v6ops@ietf.org, rfc-editor@rfc-editor.org
Subject: [v6ops] RFC 6036 on Emerging Service Provider Scenarios for IPv6 Deployment
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Oct 2010 01:34:42 -0000

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

        
        RFC 6036

        Title:      Emerging Service Provider Scenarios for 
                    IPv6 Deployment 
        Author:     B. Carpenter, S. Jiang
        Status:     Informational
        Stream:     IETF
        Date:       October 2010
        Mailbox:    brian.e.carpenter@gmail.com, 
                    shengjiang@huawei.com
        Pages:      23
        Characters: 45113
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-v6ops-isp-scenarios-00.txt

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

This document describes practices and plans that are emerging among
Internet Service Providers for the deployment of IPv6 services.  They
are based on practical experience so far, as well as current plans
and requirements, reported in a survey of a number of ISPs carried
out in early 2010.  This document identifies a number of technology
gaps, but it does not make recommendations.  This document is not 
an Internet Standards Track specification; it is published for 
informational purposes.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From gert@space.net  Sat Oct 23 02:18:54 2010
Return-Path: <gert@space.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 49CE83A67FE for <v6ops@core3.amsl.com>; Sat, 23 Oct 2010 02:18:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.477
X-Spam-Level: 
X-Spam-Status: No, score=-2.477 tagged_above=-999 required=5 tests=[AWL=0.122,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VXTdX8Gr14i2 for <v6ops@core3.amsl.com>; Sat, 23 Oct 2010 02:18:53 -0700 (PDT)
Received: from mobil.space.net (mobil.Space.Net [IPv6:2001:608:2:81::2]) by core3.amsl.com (Postfix) with ESMTP id 063853A6767 for <v6ops@ietf.org>; Sat, 23 Oct 2010 02:18:52 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id D647AF81A8 for <v6ops@ietf.org>; Sat, 23 Oct 2010 11:20:30 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id B4BFBF81B9 for <v6ops@ietf.org>; Sat, 23 Oct 2010 11:20:30 +0200 (CEST)
Received: (qmail 98125 invoked by uid 1007); 23 Oct 2010 11:20:30 +0200
Date: Sat, 23 Oct 2010 11:20:30 +0200
From: Gert Doering <gert@space.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20101023092030.GU32268@Space.Net>
References: <187F9308-79C5-4A5D-95F0-0D5A23EFBB18@free.fr> <4CC07295.8000603@gont.com.ar> <28A6DE3B-3D4D-45DF-98D3-4B7AFE0E6CF1@free.fr> <4CC07EEA.6000306@gont.com.ar> <44C27CB3-0633-46E4-A919-6351526D0DFA@free.fr> <1EA76BAD7F050648910C041BDDED8CD5013FDBD1@PRDCG4EXVW01-5.OSS.PRD> <4CC1F0EA.8090304@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="R2V/8qS8qdQvAgx5"
Content-Disposition: inline
In-Reply-To: <4CC1F0EA.8090304@gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: Scott Beuker <Scott.Beuker@sjrb.ca>, v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Oct 2010 09:18:54 -0000

--R2V/8qS8qdQvAgx5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Sat, Oct 23, 2010 at 09:15:38AM +1300, Brian E Carpenter wrote:
> On 2010-10-23 08:04, Gert Doering wrote:
>=20
> > One approach to rework 3056 would be to completely deprecate the=20
> > 6to4-with-anycast model. =20
>=20
> That is to say, deprecate RFC 3068 and revert to the pure RFC 3056 model.

Well, yes.  Sorry for mixing these RFCs.

> Good idea. Could you push my toothpaste back into the tube, too, please ;=
-)

Well, it's not like we haven't done this before.  A6/bitstring depreciation
comes to mind...

Gert Doering
        -- NetMaster
--=20
did you enable IPv6 on something today...?

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

--R2V/8qS8qdQvAgx5
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)

iQCVAwUBTMKo3qkuBuNlUUl1AQL7DwQApZDRGY+9Gxv00TlnHCIMvm9VY9V3N4un
u03aXMiD6pqs/PkxWkctzL8MnUdW50tejoO9+yBpixhVyiuAVX8A6mBY46Fkgfn0
8l1LBUmGTMp/Zgq8LZEDVCBpVUIxb4w2tmXCBl3ViidlUfqu32KR7czWu4EE8B9x
T3PLpS+wMDg=
=9SLI
-----END PGP SIGNATURE-----

--R2V/8qS8qdQvAgx5--

From gert@space.net  Sat Oct 23 02:50:18 2010
Return-Path: <gert@space.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5BA893A6783 for <v6ops@core3.amsl.com>; Sat, 23 Oct 2010 02:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.489
X-Spam-Level: 
X-Spam-Status: No, score=-2.489 tagged_above=-999 required=5 tests=[AWL=0.110,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jW3K32LM--Fh for <v6ops@core3.amsl.com>; Sat, 23 Oct 2010 02:50:17 -0700 (PDT)
Received: from mobil.space.net (mobil.Space.Net [IPv6:2001:608:2:81::2]) by core3.amsl.com (Postfix) with ESMTP id E4F793A67D7 for <v6ops@ietf.org>; Sat, 23 Oct 2010 02:50:16 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id E60D4F81A2 for <v6ops@ietf.org>; Sat, 23 Oct 2010 11:51:54 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id C6F42F81A5 for <v6ops@ietf.org>; Sat, 23 Oct 2010 11:51:54 +0200 (CEST)
Received: (qmail 2385 invoked by uid 1007); 23 Oct 2010 11:51:54 +0200
Date: Sat, 23 Oct 2010 11:51:54 +0200
From: Gert Doering <gert@space.net>
To: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
Message-ID: <20101023095154.GW32268@Space.Net>
References: <20101022085025.GM32268@Space.Net> <C8E76456.2AFD8%john_brzozowski@cable.comcast.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IODF8mTJbQXq3HpY"
Content-Disposition: inline
In-Reply-To: <C8E76456.2AFD8%john_brzozowski@cable.comcast.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Oct 2010 09:50:18 -0000

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

Hi,

On Fri, Oct 22, 2010 at 07:54:48PM +0000, Brzozowski, John wrote:
> Are you saying you prefer two independent requests? =20

I'm saying that "two indendent requests" are not going to work.  Our
provisioning system stores "customer X gets IPv6 prefix Y::/56" - and=20
that's what it will hand out in response to an IPv6 DHCP PD request.

If a second request comes it, it will either hand out the same prefix, or
tell the client "go away, nothing here for you".

> If I am reading your
> mail correctly, it sounds like a right-sized IA_PD that is shorter than a
> /64 would still work for you right?  The IGD would have to split the pref=
ix
> up and allocate it to the various LAN segments, etc. right?

Yes.

Gert Doering
        -- NetMaster
--=20
did you enable IPv6 on something today...?

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

--IODF8mTJbQXq3HpY
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (FreeBSD)

iQCVAwUBTMKwOqkuBuNlUUl1AQJMMgQAnug5nDg50y2g4fFtQnTH6g9GGBKg1G2C
/CDYvOWqVEwdPTGctYh9frI+B06m7yqKCezmbL0hTYk9JafUF5VxCdaOirrb0Qgi
PETLBK+Q0JX17bRDCDIrMtqieHUnGm6IGQc2znnJF/c2lnm6qWe7GWyAimAcRiwo
sZLYghToLbg=
=zres
-----END PGP SIGNATURE-----

--IODF8mTJbQXq3HpY--

From gert@space.net  Sat Oct 23 02:52:04 2010
Return-Path: <gert@space.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B41DD3A67D7 for <v6ops@core3.amsl.com>; Sat, 23 Oct 2010 02:52:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QK7R7HW+VBnB for <v6ops@core3.amsl.com>; Sat, 23 Oct 2010 02:52:04 -0700 (PDT)
Received: from mobil.space.net (mobil.Space.Net [IPv6:2001:608:2:81::2]) by core3.amsl.com (Postfix) with ESMTP id BF73D3A6783 for <v6ops@ietf.org>; Sat, 23 Oct 2010 02:52:03 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id 3FCDEF81A3 for <v6ops@ietf.org>; Sat, 23 Oct 2010 11:53:43 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 284C5F81A5 for <v6ops@ietf.org>; Sat, 23 Oct 2010 11:53:43 +0200 (CEST)
Received: (qmail 51900 invoked by uid 1007); 23 Oct 2010 11:53:43 +0200
Date: Sat, 23 Oct 2010 11:53:43 +0200
From: Gert Doering <gert@space.net>
To: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
Message-ID: <20101023095343.GX32268@Space.Net>
References: <DE7AE48C-76C8-4D1E-946B-43CD520FD86C@cisco.com> <C8E76BB2.2B026%john_brzozowski@cable.comcast.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C8E76BB2.2B026%john_brzozowski@cable.comcast.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Oct 2010 09:52:05 -0000

Hi,

On Fri, Oct 22, 2010 at 08:26:15PM +0000, Brzozowski, John wrote:
> Provisioning large blocks across the board may not reliably work either.
> 
> Perhaps the IGD should simply relay downstream IA_PD requests from within
> the premise and let the other RRs negotiate their own prefix requests with
> the operator DHCPv6 servers?

Our provisioning system will give the customer *one* prefix (/56 or /48).

How the customer splits this in their home is their business, and we don't
want to hear about it.  That is: hierarchical PD is fine, sending extra
PD requests to us for every router in their home is not going to work.

Gert Doering
        -- NetMaster
-- 
did you enable IPv6 on something today...?

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

From john_brzozowski@cable.comcast.com  Sat Oct 23 04:43:10 2010
Return-Path: <john_brzozowski@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 284633A686C for <v6ops@core3.amsl.com>; Sat, 23 Oct 2010 04:43:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.125
X-Spam-Level: 
X-Spam-Status: No, score=-108.125 tagged_above=-999 required=5 tests=[AWL=0.338, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wUvJ-mqKErv4 for <v6ops@core3.amsl.com>; Sat, 23 Oct 2010 04:43:08 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 261CA3A6855 for <v6ops@ietf.org>; Sat, 23 Oct 2010 04:43:07 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.101353059; Sat, 23 Oct 2010 07:44:42 -0400
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by PACDCEXHUB02.cable.comcast.com ([fe80::11d4:f530:37a0:9f4e%12]) with mapi id 14.01.0255.000; Sat, 23 Oct 2010 07:44:41 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: Gert Doering <gert@space.net>
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
Thread-Index: AQHLb7qA2T6t3TrIl0mUPJfZCE79dZNKB0SAgAA+QwCAAKTAgIAAFYsA///1tYCAAM4qgIAAPPyAgACsfomAALlnAIABLN8A///cioA=
Date: Sat, 23 Oct 2010 11:44:40 +0000
Message-ID: <C8E842FB.2B1F6%john_brzozowski@cable.comcast.com>
In-Reply-To: <20101023095154.GW32268@Space.Net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.6.0.100712
x-originating-ip: [147.191.125.12]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <23442983FD28F04F918E12C252714225@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF V6OPS WG <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Oct 2010 11:43:10 -0000

Thanks for clarifying.


On 10/23/10 5:51 AM, "Gert Doering" <gert@space.net> wrote:

> Hi,
>=20
> On Fri, Oct 22, 2010 at 07:54:48PM +0000, Brzozowski, John wrote:
>> Are you saying you prefer two independent requests?
>=20
> I'm saying that "two indendent requests" are not going to work.  Our
> provisioning system stores "customer X gets IPv6 prefix Y::/56" - and
> that's what it will hand out in response to an IPv6 DHCP PD request.
>=20
> If a second request comes it, it will either hand out the same prefix, or
> tell the client "go away, nothing here for you".
>=20
>> If I am reading your
>> mail correctly, it sounds like a right-sized IA_PD that is shorter than =
a
>> /64 would still work for you right?  The IGD would have to split the pre=
fix
>> up and allocate it to the various LAN segments, etc. right?
>=20
> Yes.
>=20
> Gert Doering
>         -- NetMaster

=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
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=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


From dr@cluenet.de  Sat Oct 23 08:09:42 2010
Return-Path: <dr@cluenet.de>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3A8083A6863 for <v6ops@core3.amsl.com>; Sat, 23 Oct 2010 08:09: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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vBtzDHlNCiJ4 for <v6ops@core3.amsl.com>; Sat, 23 Oct 2010 08:09:41 -0700 (PDT)
Received: from mail1.cluenet.de (mail1.cluenet.de [IPv6:2001:1440:201:101::5]) by core3.amsl.com (Postfix) with ESMTP id C377E3A67DF for <v6ops@ietf.org>; Sat, 23 Oct 2010 08:09:40 -0700 (PDT)
Received: by mail1.cluenet.de (Postfix, from userid 500) id 1413710842D; Sat, 23 Oct 2010 17:11:19 +0200 (CEST)
Date: Sat, 23 Oct 2010 17:11:19 +0200
From: Daniel Roesen <dr@cluenet.de>
To: v6ops@ietf.org
Message-ID: <20101023151119.GA19644@srv03.cluenet.de>
Mail-Followup-To: v6ops@ietf.org
References: <08DEEF72-2BA4-44AF-B625-5444F52F5CF5@apple.com> <C8E653E2.2AC8E%john_brzozowski@cable.comcast.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C8E653E2.2AC8E%john_brzozowski@cable.comcast.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Oct 2010 15:09:42 -0000

On Fri, Oct 22, 2010 at 12:32:28AM +0000, Brzozowski, John wrote:
> [jjmb] I think an IGD should request what it can support.

What about IGDs offering their users to set static routes?
What about IGDs supporting DHCPv6-PD towards the LAN?

Difficult to say, what size "it can support" in those cases.

Perhaps such an IGD should then request a /56 or /48 (switchable)?


Best regards,
Daniel

-- 
CLUE-RIPE -- Jabber: dr@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0

From ipng@69706e6720323030352d30312d31340a.nosense.org  Sat Oct 23 08:24:22 2010
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D9B8E3A682F for <v6ops@core3.amsl.com>; Sat, 23 Oct 2010 08:24:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.155
X-Spam-Level: 
X-Spam-Status: No, score=-1.155 tagged_above=-999 required=5 tests=[AWL=0.140,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EOHAQL8Hcezv for <v6ops@core3.amsl.com>; Sat, 23 Oct 2010 08:24:20 -0700 (PDT)
Received: from smtp1.adam.net.au (smtp1.adam.net.au [202.136.110.253]) by core3.amsl.com (Postfix) with ESMTP id DBD993A67DF for <v6ops@ietf.org>; Sat, 23 Oct 2010 08:24:19 -0700 (PDT)
Received: from 182-239-171-173.ip.adam.com.au ([182.239.171.173] helo=opy.nosense.org) by smtp1.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1P9fyj-0002bA-9g; Sun, 24 Oct 2010 01:55:53 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 743E13B32F; Sun, 24 Oct 2010 01:55:52 +1030 (CST)
Date: Sun, 24 Oct 2010 01:55:52 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: "Bernie Volz (volz)" <volz@cisco.com>
Message-ID: <20101024015552.5b831c55@opy.nosense.org>
In-Reply-To: <D9B5773329187548A0189ED65036678904932107@XMB-RCD-101.cisco.com>
References: <20101022135409.11E1328C0E8@core3.amsl.com> <20101023034107.2e049007@opy.nosense.org> <804E93BB-B90E-427B-8A83-98E1D36DDC3F@cisco.com> <D9B5773329187548A0189ED65036678904932107@XMB-RCD-101.cisco.com>
X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: v6ops mailing list <v6ops@ietf.org>
Subject: Re: [v6ops] Document Action: 'Recommended Simple SecurityCapabilities in Customer Premises Equipment for ProvidingResidential IPv6 Internet Service' to Informational RFC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Oct 2010 15:24:22 -0000

On Fri, 22 Oct 2010 14:38:23 -0500
"Bernie Volz (volz)" <volz@cisco.com> wrote:

> Just so the record is correct, technically they only got to 76:
> 
> http://www.ietf.org/id/draft-hixie-thewebsocketprotocol-77.txt:
> 
> ---
> This Internet-Draft, draft-hixie-thewebsocketprotocol-76.txt, has been
> replaced by another
> document, draft-ietf-hybi-thewebsocketprotocol-01.txt, and has been
> deleted from the 
> Internet-Drafts directory.
> 
> Internet-Drafts are not archival documents, and copies of
> Internet-Drafts
> that have been deleted from the directory are not available.  The
> Secretariat does not have any information regarding the future plans of
> the author(s) or working group, if applicable, with respect to this
> deleted Internet-Draft.  For more information, or to request a copy of
> the document, please contact the author(s) directly. 
> 
> Draft Author(s):
> 
>  I. Hickson <ian@hixie.ch>
> ---
> 
> Kind of sad they didn't keep going, but 76 is a going to be a tough
> record to beat -- I would have long given up?
> 

I've read in Radia Perlman's book that one of the ATM AAL standards was
published unimplementable, just so that they could cross off the
"published standard" check box. The IETF is obviously far more
pragmatic than that, however it'd be possibly useful to have a status
of "unRFC", to capture a historical representation of the effort people
put into it even if it didn't eventuate as an RFC :-) I think there is
quite commonly just as much value in knowing about what doesn't
work as there is in knowing what does.

Regards,
Mark.


> - Bernie
> 
> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
> Of Ralph Droms (rdroms)
> Sent: Friday, October 22, 2010 3:28 PM
> To: Mark Smith
> Cc: v6ops mailing list
> Subject: Re: [v6ops] Document Action: 'Recommended Simple
> SecurityCapabilities in Customer Premises Equipment for
> ProvidingResidential IPv6 Internet Service' to Informational RFC
> 
> With a little research - regrettably, we didn't record the actual rev
> number in RFC 3315 - the highest numbered rev of the DHCPv6 spec I could
> find was draft-ietf-dhc-dhcpv6-28.
> 
> From the Acknowledgments in RFC 3315:
> 
>    And, thanks to Steve Deering for pointing out at IETF 51 in London
>    that the DHCPv6 specification has the highest revision number of any
>    Internet Draft.
> 
> In any event, that record has been significantly exceeded by more recent
> drafts: draft-hixie-thewebsocketprotocol-77.txt 
> 
> - Ralph
> 
> On Oct 22, 2010, at 1:11 PM 10/22/10, Mark Smith wrote:
> 
> > On Fri, 22 Oct 2010 06:54:09 -0700 (PDT)
> > The IESG <iesg-secretary@ietf.org> wrote:
> > 
> >> The IESG has approved the following document:
> >> 
> >> - 'Recommended Simple Security Capabilities in Customer Premises 
> >>   Equipment for Providing Residential IPv6 Internet Service '
> >>   <draft-ietf-v6ops-cpe-simple-security-16.txt> as an Informational
> RFC
> >> 
> > 
> > Well done everybody, especially James. I think I've read somewhere
> that
> > the DHCPv6 spec had set a record at 15 revisions ... it's just been
> > beaten :-)
> > 
> >> 
> >> This document is the product of the IPv6 Operations Working Group. 
> >> 
> >> The IESG contact persons are Ron Bonica and Dan Romascanu.
> >> 
> >> A URL of this Internet-Draft is:
> >>
> http://www.ietf.org/internet-drafts/draft-ietf-v6ops-cpe-simple-security
> -16.txt
> >> 
> >> Technical Summary
> >> 
> >> This document identifies a set of recommendations for the makers of
> >> devices describing how to provide for "simple security" capabilities
> >> at the perimeter of local-area IPv6 networks in Internet-enabled
> >> homes and small offices.
> >> 
> >> Working Group Summary
> >> 
> >> The working group was divided on the concept of defining or
> recommending
> >> the use of firewalls; as a result, this document is very explicitly a
> set
> >> of recommendations for those that would choose to build or deploy a
> >> firewall without making any recommendation on whether anyone should
> do
> >> either. It describes a simple stateful firewall, permeable to traffic
> that
> >> is secured using IPsec.
> >> 
> >> Document Quality
> >> 
> >> There is at least one deployed implementation of this firewall, and
> >> expected to be others. The document clearly specifies a consensus set
> of
> >> recommendations for such firewalls.
> >> 
> >> Personel
> >> 
> >> Fred Baker is shepherd.
> >> 
> >> RFC Editor Note
> >> 
> >> OLD TEXT:
> >> 
> >> REC-13: 
> >> 
> >> By DEFAULT, Internet gateways SHOULD, automatically download
> >> and install software updates for extending IPv6 simple security for
> >> support of future standard upper layer transports and extension
> >> headers.
> >> 
> >> NEW TEXT:
> >> 
> >> REC-13:
> >> Residential Internet Gateways SHOULD provide a convenient means to 
> >> securely update their firmware, for the installation of security 
> >> patches and other manufacturer-recommended changes.
> >> 
> >> Vendors can expect users and operators to have differing viewpoints 
> >> on the maintenance of patches, with some preferring automated update 
> >> and some preferring manual initiation, and those preferring automated
> 
> >> update wanting to download from a vendor site or one managed by the 
> >> network operator. To handle the disparity, vendors are well advised 
> >> if they provide manual and automated options. In the automated case, 
> >> they would do well to facilitate pre-configuration of the download 
> >> URL and a means of validating the software image such as a
> certificate.
> >> 
> >> _______________________________________________
> >> v6ops mailing list
> >> v6ops@ietf.org
> >> https://www.ietf.org/mailman/listinfo/v6ops
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

From victor.kuarsingh@gmail.com  Sat Oct 23 08:53:40 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 751ED3A67E6 for <v6ops@core3.amsl.com>; Sat, 23 Oct 2010 08:53:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ACCmV8XTuOH8 for <v6ops@core3.amsl.com>; Sat, 23 Oct 2010 08:53:39 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 573A23A676A for <v6ops@ietf.org>; Sat, 23 Oct 2010 08:53:39 -0700 (PDT)
Received: by gwb17 with SMTP id 17so1374712gwb.31 for <v6ops@ietf.org>; Sat, 23 Oct 2010 08:55:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=i4/WHaXSC9Lir+b/4y9FQgZl8p4fB2o2LFrfa9kfvu0=; b=VzR0bTfYQS3EDR9z9X6A3HAbdV/GQSKi76iD634eW2/74nKUZH0bDEe+/0RzuervgC XcJUoBjd3L2BRoTTKBEkGOO2lITeXjLwbyUS6io+VTWKymYZvr5bC0SgAZrCyC5ldyAQ PCxFSO4YyubFvuB9jO5SVBx5Wp4+relGxvf2Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=Y9MRfuwM3BM5J6e+CDyGCLYR6Sv6++0GY4ZxTc3tdzq8LYiL2ReO0r38cgRQqcF0Ls 0XGG3ZEYgJL+7zp5d1sdBonw47RfMvjZ+jqlzzpPfHJuWzp8appghVfuFvrhHjIii1pj fbsY8KvOQG5jLXjn/m1MWBAwJfBsBEqEB6wuw=
Received: by 10.150.144.10 with SMTP id r10mr7241476ybd.34.1287849319558; Sat, 23 Oct 2010 08:55:19 -0700 (PDT)
Received: from [192.168.100.149] ([67.224.83.162]) by mx.google.com with ESMTPS id p38sm850370ybk.4.2010.10.23.08.55.13 (version=SSLv3 cipher=RC4-MD5); Sat, 23 Oct 2010 08:55:18 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Sat, 23 Oct 2010 11:55:09 -0400
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: Gert Doering <gert@space.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <C8E87D9D.105B5%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
Thread-Index: ActyyqsdsZheNTIr9kmZ6EO0lHHNrw==
In-Reply-To: <20101023092030.GU32268@Space.Net>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: Scott Beuker <Scott.Beuker@sjrb.ca>, v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Oct 2010 15:53:40 -0000

Gert,

Just a question..

RFC3068 (with RFC3056) works and is deployed widely in production networks
(via OSs, Gateways and other equipment).

Why would we depreciate something that works before all the viable
alternatives (6RD, Native IPv6 and new things like 6a44) are still not out
there in mass?  Why reduce that IPv6 glue space?

I would say we wait until those newer technologies are considered deployed
and then consider depreciating something that actually works and is out
there.  It seems premature in my mind, given that the only issue we see is
the the performance related to return path (with was what we were trying to
help correct).  Other then this... It work.

Plus, depreciating it would take time since it hard to force customers to
upgrade OSs (although this has become automated in most OSs) and consumer
equipment (many customers do not upgrade past store rev firmware).

Trust me, when the other technologies are out there, and viable in mass,
providers will leverage them.

On the point of

" If there's real interest to reach those servers, the clients will find
a way to get IPv6 - but it's unlikely that we'll see IPv6-only servers
any time soon."

I do agree that IPv6-only servers are less likely soon (but still a threat
after IPv4 runout, but IPv6-only endpoints is possible (i.e. Other host).
AS to customers "finding a way to get IPv6", once again, I don't even think
most know what IPv6 is - much less seek it out.  They would just detect
"brokenness" should something be IPv6-only and have access to IPv4-only.

My analogy to Internet usage for most is like "gas in the car".  Most people
put gas in the card, turn the key and press the accelerator/break.  All the
rest "just works". Our mission (as operators) will be to make things "just
work".

Just a thought.

Regards,

Victor


On 23/10/10 5:20 AM, "Gert Doering" <gert@space.net> wrote:

> Hi,
> 
> On Sat, Oct 23, 2010 at 09:15:38AM +1300, Brian E Carpenter wrote:
>> On 2010-10-23 08:04, Gert Doering wrote:
>> 
>>> One approach to rework 3056 would be to completely deprecate the
>>> 6to4-with-anycast model.
>> 
>> That is to say, deprecate RFC 3068 and revert to the pure RFC 3056 model.
> 
> Well, yes.  Sorry for mixing these RFCs.
> 
>> Good idea. Could you push my toothpaste back into the tube, too, please ;-)
> 
> Well, it's not like we haven't done this before.  A6/bitstring depreciation
> comes to mind...
> 
> Gert Doering
>         -- NetMaster



From gert@space.net  Sat Oct 23 09:43:11 2010
Return-Path: <gert@space.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5FE893A68E4 for <v6ops@core3.amsl.com>; Sat, 23 Oct 2010 09:43:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.507
X-Spam-Level: 
X-Spam-Status: No, score=-2.507 tagged_above=-999 required=5 tests=[AWL=0.092,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KPkc2WWHEQZy for <v6ops@core3.amsl.com>; Sat, 23 Oct 2010 09:43:10 -0700 (PDT)
Received: from mobil.space.net (mobil.Space.Net [IPv6:2001:608:2:81::2]) by core3.amsl.com (Postfix) with ESMTP id D0C543A68DB for <v6ops@ietf.org>; Sat, 23 Oct 2010 09:43:09 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id 3FE31F81AE for <v6ops@ietf.org>; Sat, 23 Oct 2010 18:44:48 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 1EB54F81A2 for <v6ops@ietf.org>; Sat, 23 Oct 2010 18:44:48 +0200 (CEST)
Received: (qmail 43389 invoked by uid 1007); 23 Oct 2010 18:44:47 +0200
Date: Sat, 23 Oct 2010 18:44:47 +0200
From: Gert Doering <gert@space.net>
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>
Message-ID: <20101023164447.GZ32268@Space.Net>
References: <20101023092030.GU32268@Space.Net> <C8E87D9D.105B5%victor.kuarsingh@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cA3IEVIgmXpDDqpy"
Content-Disposition: inline
In-Reply-To: <C8E87D9D.105B5%victor.kuarsingh@gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: Scott Beuker <Scott.Beuker@sjrb.ca>, v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Oct 2010 16:43:11 -0000

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

Hi,

On Sat, Oct 23, 2010 at 11:55:09AM -0400, Victor Kuarsingh wrote:
> Just a question..
>=20
> RFC3068 (with RFC3056) works and is deployed widely in production networks
> (via OSs, Gateways and other equipment).

Well, whether "6to4+anycast relay" (RFC 3068) "works" seems to be a matter=
=20
of interpretation - if it works, why would we need 6to4-PMT?

Obviously, it does not work sufficiently well - and since the envisioned
need ("connect to ipv6-only content") isn't there (there is no ipv6-only
content), but it does harm, it seems to be more useful to deprecate it
completely, instead of investing more work into something that is not
useful.

[..]
> My analogy to Internet usage for most is like "gas in the car".  Most peo=
ple
> put gas in the card, turn the key and press the accelerator/break.  All t=
he
> rest "just works". Our mission (as operators) will be to make things "just
> work".

Yes, and to me, "fiddling with 6to4 anycast, wasting more effort and
breaking one of the most important bits of IPv6, end-to-end transparency
between IPv6-speaking nodes, in process" is not a good way to make things
"just work".

If "gas in the car" people notice that certain thing are problematic, like
"leaded gas", they stop using them.

Gert Doering
        -- NetMaster
--=20
did you enable IPv6 on something today...?

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

--cA3IEVIgmXpDDqpy
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)

iQCVAwUBTMMQ/qkuBuNlUUl1AQLHiQP9Hju54gF7NJ+0GLX42Muif3TwnJjjppzp
KrKGGyHF8knb56CvlXSrVqAEIWltYjC6+ajWxhsx2xE3QyQWxD0QjGTc26P92WV+
CDV9tokMov+k7W5utnOU8EBUHclEx9fjNWFLheKfGJG0F4yWtE9c3Mo+HhMxRgTz
+g+wkWvj50g=
=AZae
-----END PGP SIGNATURE-----

--cA3IEVIgmXpDDqpy--

From fred@cisco.com  Sun Oct 24 10:59:16 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 42B603A68E4 for <v6ops@core3.amsl.com>; Sun, 24 Oct 2010 10:59:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.323
X-Spam-Level: 
X-Spam-Status: No, score=-110.323 tagged_above=-999 required=5 tests=[AWL=0.276, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jslufjn+S9RI for <v6ops@core3.amsl.com>; Sun, 24 Oct 2010 10:59:15 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 6BC623A682F for <v6ops@ietf.org>; Sun, 24 Oct 2010 10:59:15 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAP4QxEyrR7Hu/2dsb2JhbAChZ3GeVJsohUgEhFSFeYMG
X-IronPort-AV: E=Sophos;i="4.58,232,1286150400"; d="scan'208";a="205872747"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 24 Oct 2010 18:00:58 +0000
Received: from Freds-Computer.local (sjc-vpn5-1754.cisco.com [10.21.94.218]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o9OHxhFn012706; Sun, 24 Oct 2010 18:00:53 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Sun, 24 Oct 2010 11:00:58 -0700
X-PGP-Universal: processed; by Freds-Computer.local on Sun, 24 Oct 2010 11:00:58 -0700
From: Fred Baker <fred@cisco.com>
Date: Sun, 24 Oct 2010 11:00:50 -0700
Message-Id: <174BC871-6568-4569-B4E4-3ADDEB0C565C@cisco.com>
To: IPv6 Operations <v6ops@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: v6ops-chairs@tools.ietf.org, Ron Bonica <ron@bonica.org>
Subject: [v6ops] draft-ietf-v6ops-3177bis-end-sites WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Oct 2010 17:59:16 -0000

This is to initiate a two week working group last call of =
draft-ietf-v6ops-3177bis-end-sites. Please read it now. If you find nits =
(spelling errors, minor suggested wording changes, etc), comment to the =
authors; if you find greater issues, such as disagreeing with a =
statement or finding additional issues that need to be addressed, please =
post your comments to the list.

We are looking specifically for comments on the importance of the =
document as well as its content. If you have read the document and =
believe it to be of operational utility, that is also an important =
comment to make.=20=

From fred@cisco.com  Sun Oct 24 11:03:16 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E7D723A68E4 for <v6ops@core3.amsl.com>; Sun, 24 Oct 2010 11:03:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.952
X-Spam-Level: 
X-Spam-Status: No, score=-109.952 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OdB1UOGMSzRr for <v6ops@core3.amsl.com>; Sun, 24 Oct 2010 11:03:16 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 243CA3A68D1 for <v6ops@ietf.org>; Sun, 24 Oct 2010 11:03:16 -0700 (PDT)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAO8RxEyrRN+K/2dsb2JhbAChZ3GeW5sngn6CSgSEVIV5gwY
X-IronPort-AV: E=Sophos;i="4.58,232,1286150400"; d="scan'208";a="274873771"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-5.cisco.com with ESMTP; 24 Oct 2010 18:04:59 +0000
Received: from Freds-Computer.local (sjc-vpn5-1754.cisco.com [10.21.94.218]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o9OI4pQZ029908; Sun, 24 Oct 2010 18:04:54 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Sun, 24 Oct 2010 11:04:59 -0700
X-PGP-Universal: processed; by Freds-Computer.local on Sun, 24 Oct 2010 11:04:59 -0700
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <174BC871-6568-4569-B4E4-3ADDEB0C565C@cisco.com>
Date: Sun, 24 Oct 2010 11:04:44 -0700
Message-Id: <2017CAB1-7D08-4AEF-81CE-1235AF19C13F@cisco.com>
References: <174BC871-6568-4569-B4E4-3ADDEB0C565C@cisco.com>
To: IPv6 Operations <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: V6ops Chairs <v6ops-chairs@tools.ietf.org>, Ron Bonica <ron@bonica.org>
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Oct 2010 18:03:17 -0000

On Oct 24, 2010, at 11:00 AM, Fred Baker wrote:

> This is to initiate a two week working group last call of =
draft-ietf-v6ops-3177bis-end-sites. Please read it now. If you find nits =
(spelling errors, minor suggested wording changes, etc), comment to the =
authors; if you find greater issues, such as disagreeing with a =
statement or finding additional issues that need to be addressed, please =
post your comments to the list.

I should add that this is an unusual WGLC for us; I try to not overlap =
actual IETF meetings, but this one will close on the seventh of =
November. Clearing the decks as we have ~22 more we will need to deal =
with, some of which probably should go to the IESG relatively soon.

> We are looking specifically for comments on the importance of the =
document as well as its content. If you have read the document and =
believe it to be of operational utility, that is also an important =
comment to make.=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From brian.e.carpenter@gmail.com  Sun Oct 24 12:31:53 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BD4003A68E2 for <v6ops@core3.amsl.com>; Sun, 24 Oct 2010 12:31:53 -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.117, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4aSUMtlitiNZ for <v6ops@core3.amsl.com>; Sun, 24 Oct 2010 12:31:52 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id C2BF53A68D6 for <v6ops@ietf.org>; Sun, 24 Oct 2010 12:31:51 -0700 (PDT)
Received: by ywp6 with SMTP id 6so1134727ywp.31 for <v6ops@ietf.org>; Sun, 24 Oct 2010 12:33:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=eSidgok3nK6dBVQMZC3o8zHnvC4tytBzZWIuEqk7Wl8=; b=N2RKkCGL+HSdMfH4N2qUVucA4zUQ1gOfaIxC0k6mqDK9c4vPyOl4EmjBOEPAcMXzyz z3I5WgX6ypVzWVi/DeZvCX8AwjCsZkwzxcRCpFSHV7uqCHX+gnDWhQYtVbqeDRayXmPG cDIh1htQ0AiPk7SC3ihHDEzep+NQilMM9gZns=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=Cl3Hjmg6/c3D19zlM7HNLq+l+Y9xv2IF7QnHxiDlAQnnOHhMbjfpbok7eDCfLhSycd 51VY7drn9V7z2DDIbA/v72+LOphZPGV5gnIQGS1tlIRBd0JmsAG2a2xjnnYSPxSgb4ge q+lJ03KyR6/gMguPP/wBK4eoSuD46JJK7BaSA=
Received: by 10.101.74.11 with SMTP id b11mr4674821anl.204.1287948813735; Sun, 24 Oct 2010 12:33:33 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.142.15]) by mx.google.com with ESMTPS id z10sm7360289anj.14.2010.10.24.12.33.30 (version=SSLv3 cipher=RC4-MD5); Sun, 24 Oct 2010 12:33:33 -0700 (PDT)
Message-ID: <4CC48A08.5050200@gmail.com>
Date: Mon, 25 Oct 2010 08:33:28 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <174BC871-6568-4569-B4E4-3ADDEB0C565C@cisco.com>
In-Reply-To: <174BC871-6568-4569-B4E4-3ADDEB0C565C@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, v6ops-chairs@tools.ietf.org, Ron Bonica <ron@bonica.org>
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Oct 2010 19:31:53 -0000

This is very important, as it aligns the IETF's technical guidance
with the reality of address management faced by the RIRs. RFC 3177
was a rather theoretical document (which I wrote a fair chunk of),
and it's time to officially retire it.

I believe the draft is ready, and overdue.

   Brian Carpenter

On 2010-10-25 07:00, Fred Baker wrote:
> This is to initiate a two week working group last call of draft-ietf-v6ops-3177bis-end-sites. Please read it now. If you find nits (spelling errors, minor suggested wording changes, etc), comment to the authors; if you find greater issues, such as disagreeing with a statement or finding additional issues that need to be addressed, please post your comments to the list.
> 
> We are looking specifically for comments on the importance of the document as well as its content. If you have read the document and believe it to be of operational utility, that is also an important comment to make. 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> 

From randy@psg.com  Sun Oct 24 18:19:59 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D7FA3A67BE for <v6ops@core3.amsl.com>; Sun, 24 Oct 2010 18:19:59 -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.044,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1mxyzLT1M9Wh for <v6ops@core3.amsl.com>; Sun, 24 Oct 2010 18:19:58 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 19C103A6767 for <v6ops@ietf.org>; Sun, 24 Oct 2010 18:19:58 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1PABkj-0005dP-QA; Mon, 25 Oct 2010 01:21:34 +0000
Date: Sun, 24 Oct 2010 18:21:33 -0700
Message-ID: <m2zku33w4i.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <174BC871-6568-4569-B4E4-3ADDEB0C565C@cisco.com>
References: <174BC871-6568-4569-B4E4-3ADDEB0C565C@cisco.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: v6ops mailing list <v6ops@ietf.org>, Ron Bonica <ron@bonica.org>
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 01:19:59 -0000

> This is to initiate a two week working group last call of
> draft-ietf-v6ops-3177bis-end-sites.

<support>

From fred@cisco.com  Sun Oct 24 18:38:51 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 01FF03A67FA for <v6ops@core3.amsl.com>; Sun, 24 Oct 2010 18:38:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.329
X-Spam-Level: 
X-Spam-Status: No, score=-110.329 tagged_above=-999 required=5 tests=[AWL=0.270, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R0EOVYjD7ZUx for <v6ops@core3.amsl.com>; Sun, 24 Oct 2010 18:38:49 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 889DF3A6767 for <v6ops@ietf.org>; Sun, 24 Oct 2010 18:38:49 -0700 (PDT)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAAt9xEyrR7Ht/2dsb2JhbAChXnGgAps5hUgEhFSFCm+DBg
X-IronPort-AV: E=Sophos;i="4.58,233,1286150400"; d="scan'208";a="374102225"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-1.cisco.com with ESMTP; 25 Oct 2010 01:40:33 +0000
Received: from stealth-10-32-244-222.cisco.com (stealth-10-32-244-222.cisco.com [10.32.244.222]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o9P1ePO3022279 for <v6ops@ietf.org>; Mon, 25 Oct 2010 01:40:28 GMT
Received: from [127.0.0.1] by stealth-10-32-244-222.cisco.com (PGP Universal service); Sun, 24 Oct 2010 18:40:33 -0700
X-PGP-Universal: processed; by stealth-10-32-244-222.cisco.com on Sun, 24 Oct 2010 18:40:33 -0700
From: Fred Baker <fred@cisco.com>
Date: Sun, 24 Oct 2010 18:40:18 -0700
References: <5A6D953473350C4B9995546AFE9939EE0B14C490@RWC-EX1.corp.seven.com>
To: IPv6 Operations <v6ops@ietf.org>
Message-Id: <694C636B-D954-4AF0-800E-DF9F2137841A@cisco.com>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [v6ops] Fwd: draft-ietf-v6ops-3177bis-end-sites WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 01:38:51 -0000

Begin forwarded message:

> From: "George Bonser" <gbonser@seven.com>
> Date: October 24, 2010 1:29:05 PM PDT
> To: "IPv6 operators forum" <ipv6-ops@lists.cluenet.de>
> Subject: RE: draft-ietf-v6ops-3177bis-end-sites WGLC
> 
> One thing that concerns me is this:
> 
> " RFC3177 suggested that some multihoming approaches (e.g., GSE) might
>   benefit from having a fixed /48 boundary. This no longer appears to
>   be a consideration."
> 
> As long as those approaches keep any smaller assignments out of the
> global routing table, then fine.  It is going to be hard enough for
> dual-stacked operators getting full routes to deal with the explosion of
> /48 routes from PI space that will happen when the current v4 multihomed
> nets start announcing their /48 assignments.
> 
> A v6 route consumes 4x the resources on a router as a v4 route does. 
> A network that is multihomed on v4 will likely also be multihomed on v6.
> A network will likely be multihomed on both protocols at the same time
> initially and for some period after they begin to announce their v6
> assignment.
> 
> Given the above, when the mass migration begins, there will be no
> reduction in the v4 table and an explosion of the v6 table.  Routers are
> going to blow up once the combined table gets to about 500,000 v4 route
> equivalent.  Granted, due to the larger assignments in v6, the migration
> of individual network blocks will not be 1-to-1 in that an end site with
> multiple non-contiguous v4 small assignments can operate with a larger
> v6 aggregate but nevertheless the v4 table will not shrink and the v6
> table will grow.
> 
> I am currently accepting down to a /48 from PI space but not accepting
> nets that small from PA space.  It is going to be pretty hard for folks
> to try to multihome using PA space.  Even if they convince their
> upstream to punch a hole in their aggregate and announce a smaller net,
> getting other people to accept that smaller net is going to be a
> problem.
> 
> In summary, anything smaller than a /48 in PI space is likely to be
> useless if it is announced globally as many will not accept it.
> 
> 
> 
>> -----Original Message-----
>> From: ipv6-ops-bounces+gbonser=seven.com@lists.cluenet.de
> [mailto:ipv6-
>> ops-bounces+gbonser=seven.com@lists.cluenet.de] On Behalf Of Fred
> Baker
>> Sent: Sunday, October 24, 2010 11:01 AM
>> To: IPv6 operators forum
>> Subject: draft-ietf-v6ops-3177bis-end-sites WGLC
>> 
>> The IETF IPv6 Operations Working Group is initiating a two week
> working
>> group last call of
>> 
>> http://tools.ietf.org/html/draft-ietf-v6ops-3177bis-end-sites
>>  "IPv6 Address Assignment to End Sites", Thomas Narten, Geoff Huston,
>>  Rosalea Roberts
>> 
>> In essence, this is a change to the advice that the IETF gave the RIRs
>> in RFC 3177. We had indicated at that time that we believed that
>> allocating a /48 to each end site was important, for various reasons.
>> We at this point believe that a better model allows the LIR to
> allocate
>> diffrent length prefixes to their customers in accordance with the
>> network's needs.
>> 
>> If you find issues, such as disagreeing with a statement or finding
>> additional issues that need to be addressed, please post your comments
>> to v6ops@ietf.org.
>> 
>> We are looking specifically for comments on the importance of the
>> document as well as its content. If you have read the document and
>> believe it to be of operational utility, that is also an important
>> comment to make.


From randy@psg.com  Sun Oct 24 20:02:24 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A46D93A693B for <v6ops@core3.amsl.com>; Sun, 24 Oct 2010 20:02:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.557
X-Spam-Level: 
X-Spam-Status: No, score=-2.557 tagged_above=-999 required=5 tests=[AWL=0.042,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uSONS4Wl5o18 for <v6ops@core3.amsl.com>; Sun, 24 Oct 2010 20:02:23 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id ACE013A6939 for <v6ops@ietf.org>; Sun, 24 Oct 2010 20:02:23 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1PADLx-0005tv-80; Mon, 25 Oct 2010 03:04:06 +0000
Date: Sun, 24 Oct 2010 20:04:04 -0700
Message-ID: <m2lj5n3rdn.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <694C636B-D954-4AF0-800E-DF9F2137841A@cisco.com>
References: <5A6D953473350C4B9995546AFE9939EE0B14C490@RWC-EX1.corp.seven.com> <694C636B-D954-4AF0-800E-DF9F2137841A@cisco.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Fwd: draft-ietf-v6ops-3177bis-end-sites WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 03:02:24 -0000

>> In summary, anything smaller than a /48 in PI space is likely to be
>> useless if it is announced globally as many will not accept it.

what people will generally accept is ephemeral.  it once used to be /24
in v4 space.  then it clamped down to /19 except in swamp.  then it
became rir allocation boundaries.  then it became /24 again.  and i
suspect that, within five years, it could be longer than /24.

don't try to hard code it in an rfc.

randy

From gbonser@seven.com  Sun Oct 24 20:06:22 2010
Return-Path: <gbonser@seven.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2B1273A6929 for <v6ops@core3.amsl.com>; Sun, 24 Oct 2010 20:06: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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lzWnSEB11KPJ for <v6ops@core3.amsl.com>; Sun, 24 Oct 2010 20:06:20 -0700 (PDT)
Received: from wex.seven.com (wex.seven.com [208.87.204.25]) by core3.amsl.com (Postfix) with ESMTP id 0FFB83A6359 for <v6ops@ietf.org>; Sun, 24 Oct 2010 20:06:18 -0700 (PDT)
Received: from wex.seven.com ([10.1.16.28]) by wex.seven.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 24 Oct 2010 20:08:02 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 24 Oct 2010 20:08:01 -0700
Message-ID: <5A6D953473350C4B9995546AFE9939EE0B14C49E@RWC-EX1.corp.seven.com>
In-Reply-To: <m2lj5n3rdn.wl%randy@psg.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops] Fwd: draft-ietf-v6ops-3177bis-end-sites WGLC
Thread-Index: Actz8VgMldvBYJgWQgKG5ykI2qIaxgAACiAQ
References: <5A6D953473350C4B9995546AFE9939EE0B14C490@RWC-EX1.corp.seven.com><694C636B-D954-4AF0-800E-DF9F2137841A@cisco.com> <m2lj5n3rdn.wl%randy@psg.com>
From: "George Bonser" <gbonser@seven.com>
To: "Randy Bush" <randy@psg.com>
X-OriginalArrivalTime: 25 Oct 2010 03:08:02.0351 (UTC) FILETIME=[D5EBE3F0:01CB73F1]
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Fwd: draft-ietf-v6ops-3177bis-end-sites WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 03:07:10 -0000

>=20
> what people will generally accept is ephemeral.  it once used to be
/24
> in v4 space.  then it clamped down to /19 except in swamp.  then it
> became rir allocation boundaries.  then it became /24 again.  and i
> suspect that, within five years, it could be longer than /24.
>=20
> don't try to hard code it in an rfc.

It will get easier once we see the v4 table begin to shrink but
initially it is going to be difficult while the v4 table undergoes
further fragmentation at the same time those nets are moving to v6.

But I agree, probably not worth hard coding policy in an RFC but I read
it as a recommendation not as a rule.





From randy@psg.com  Sun Oct 24 20:29:59 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4646B3A6359 for <v6ops@core3.amsl.com>; Sun, 24 Oct 2010 20:29:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.558
X-Spam-Level: 
X-Spam-Status: No, score=-2.558 tagged_above=-999 required=5 tests=[AWL=0.041,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EgV5EgVm4POW for <v6ops@core3.amsl.com>; Sun, 24 Oct 2010 20:29:58 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 30E603A68A4 for <v6ops@ietf.org>; Sun, 24 Oct 2010 20:29:58 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1PADme-0005yP-Ae; Mon, 25 Oct 2010 03:31:40 +0000
Date: Sun, 24 Oct 2010 20:31:39 -0700
Message-ID: <m2eibf3q3o.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "George Bonser" <gbonser@seven.com>
In-Reply-To: <5A6D953473350C4B9995546AFE9939EE0B14C49E@RWC-EX1.corp.seven.com>
References: <5A6D953473350C4B9995546AFE9939EE0B14C490@RWC-EX1.corp.seven.com> <694C636B-D954-4AF0-800E-DF9F2137841A@cisco.com> <m2lj5n3rdn.wl%randy@psg.com> <5A6D953473350C4B9995546AFE9939EE0B14C49E@RWC-EX1.corp.seven.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Fwd: draft-ietf-v6ops-3177bis-end-sites WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 03:29:59 -0000

> It will get easier once we see the v4 table begin to shrink but
> initially it is going to be difficult while the v4 table undergoes
> further fragmentation at the same time those nets are moving to v6.

ephemeral

> But I agree, probably not worth hard coding policy in an RFC but I
> read it as a recommendation not as a rule.

we should not be saying much at all about policy.  that is the domain of
the ops community, not a technical standards body.  and that is the very
good thing about this draft.

randy

From remi.despres@free.fr  Mon Oct 25 00:34:02 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 66DF13A67DA for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 00:34:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.177
X-Spam-Level: 
X-Spam-Status: No, score=-1.177 tagged_above=-999 required=5 tests=[AWL=0.172,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kHzhUmuD6czW for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 00:34:01 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.19]) by core3.amsl.com (Postfix) with ESMTP id DB0093A672F for <v6ops@ietf.org>; Mon, 25 Oct 2010 00:33:56 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2302.sfr.fr (SMTP Server) with ESMTP id 9CF477000089; Mon, 25 Oct 2010 09:35:31 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2302.sfr.fr (SMTP Server) with ESMTP id E33F77000087; Mon, 25 Oct 2010 09:35:30 +0200 (CEST)
X-SFR-UUID: 20101025073530930.E33F77000087@msfrf2302.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <C8E87D9D.105B5%victor.kuarsingh@gmail.com>
Date: Mon, 25 Oct 2010 09:35:29 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <660EFF7C-8621-4B74-B836-178594D71BE6@free.fr>
References: <C8E87D9D.105B5%victor.kuarsingh@gmail.com>
To: v6ops v6ops <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1081)
Cc: Scott Beuker <Scott.Beuker@sjrb.ca>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 07:34:02 -0000

Le 23 oct. 2010 =E0 17:55, Victor Kuarsingh a =E9crit :
> ...
> Why would we depreciate something that works before all the viable
> alternatives (6RD, Native IPv6 and new things like 6a44) are still not =
out
> there in mass?  Why reduce that IPv6 glue space?
> ...
> My analogy to Internet usage for most is like "gas in the car".  Most =
people
> put gas in the card, turn the key and press the accelerator/break.  =
All the
> rest "just works".

> Our mission (as operators) will be to make things "just
> work".

Agreed, what is needed is what "just works".

Now:
* Native IPv6 "just works"
 1. guaranteed e2e address transparency (OK for peer-to-peer)
 2. guaranteed connectivity
 3. ISP control of customer QoS
* 6to4 between two 6to4 addresses (without 6o4 relays) "just works":
 1. guaranteed e2e address transparency
 2. guaranteed connectivity
 3. ISP control of customer QoS (that of IPv4)
* 6to4 between a 6to4 address and a native-IPv6 address (with 2 6to4 =
relays) "doesn't just work":
 1. (e2e address transparency still available)
 2. guaranteed connectivity is LOST
 3. ISP control of customer QoS is LOST

If SOME ISPs would deploy 6to4-PMT, i.e. add NAT66's to 6to4 relays, =
6to4 would EVEN LESS "just work":
- For 6to4 customers of 6to4-PMT ISPs:
 1. e2e address transparency is LOST (peer-to-peer in Ipv6 is broken)
 2. guaranteed connectivity is still LOST  (depends on whether remote =
native-IPv6 hosts access 6to4 relays)
 3. ISP control of customer QoS is still LOST (if remote native-IPv6 =
hosts have access to 6to4 relays, it depends on which ones)=20
- For native IPv6 customers
 1. guaranteed e2e address transparency is LOST (remote native IPv6 =
addresses may now be translated on their way)
 2. guaranteed connectivity with 6to4 addresses is still LOST (not all =
6to4 addresses are 6to4-PMT addresses)
 3. ISP control of customer QoS is still LOST (not all 6to4 addresses =
are 6to4-PMT addresses)
- For 6to4 customers of ISPs that haven't 6to4-PMT:
 1. e2e address transparency is LOST (they may be talking to 6to4-PMT =
customers)
 2. guaranteed connectivity is still LOST (they may have no access to a =
6to4 relay)
 3. ISP control of customer QoS is LOST (if they access some 6to4 =
relays, it depends on which ones)

6to4-PMT is simple, a quality, but, by combining two mechanisms that =
already create more problems than they solve (6to4 relays and NAT66), it =
can only lead to poor user experience in IPv6.

The technical content of the above can be challenged if one finds that =
is has mistakes.
But if it is right, the conclusion is that, to only keep solutions that =
"just work", using the 6to4 anycast address in 6to4 customers should be =
turned off, at least by default, and that where 6to4 relays are still in =
use, no NAT66 of any form should be added to them.=20


> Plus, depreciating it would take time since it hard to force customers =
to
> upgrade OSs (although this has become automated in most OSs) and =
consumer
> equipment (many customers do not upgrade past store rev firmware).

Deprecating a spec only means "if you have the choice, no longer do it".
In my understanding, deprecating 6to4-anycast in customer devices =
doesn't mean that 6to4 relays that exist today should be dismantled.
As long as operators of these relays don't offer native IPv6, and see =
that they still have users, they are perfectly entitled to maintain =
these relays for these users.


To conclude, the proposal is that IETF:
- deprecates the use of the 6to4-relay anycast address in 6to4 routers=20=

- explains why associating NAT66's with 6to4 relays should be avoided
This will contribute to make IPv6 something that "just works".=20

Regards,
RD


>=20
> Just a thought.
>=20
> Regards,
>=20
> Victor
>=20
>=20
> On 23/10/10 5:20 AM, "Gert Doering" <gert@space.net> wrote:
>=20
>> Hi,
>>=20
>> On Sat, Oct 23, 2010 at 09:15:38AM +1300, Brian E Carpenter wrote:
>>> On 2010-10-23 08:04, Gert Doering wrote:
>>>=20
>>>> One approach to rework 3056 would be to completely deprecate the
>>>> 6to4-with-anycast model.
>>>=20
>>> That is to say, deprecate RFC 3068 and revert to the pure RFC 3056 =
model.
>>=20
>> Well, yes.  Sorry for mixing these RFCs.
>>=20
>>> Good idea. Could you push my toothpaste back into the tube, too, =
please ;-)
>>=20
>> Well, it's not like we haven't done this before.  A6/bitstring =
depreciation
>> comes to mind...
>>=20
>> Gert Doering
>>        -- NetMaster
>=20
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops



From remi.despres@free.fr  Mon Oct 25 01:27:34 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D2353A697D for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 01:27:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.679
X-Spam-Level: 
X-Spam-Status: No, score=-0.679 tagged_above=-999 required=5 tests=[AWL=-0.330, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_BACKHAIR_44=1, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o1oY9yx7iaUq for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 01:27:33 -0700 (PDT)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.81]) by core3.amsl.com (Postfix) with ESMTP id 6F4A63A698E for <v6ops@ietf.org>; Mon, 25 Oct 2010 01:27:32 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2419.sfr.fr (SMTP Server) with ESMTP id 34FA37000097; Mon, 25 Oct 2010 10:29:16 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2419.sfr.fr (SMTP Server) with ESMTP id D94C37000096; Mon, 25 Oct 2010 10:29:15 +0200 (CEST)
X-SFR-UUID: 20101025082915890.D94C37000096@msfrf2419.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <20101022190434.GT32268@Space.Net>
Date: Mon, 25 Oct 2010 10:29:12 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C0D635F-D164-49FB-BF98-85F7A7B103CA@free.fr>
References: <043801cb7210$c99d17f0$5cd747d0$@net> <C8E74947.1055B%victor.kuarsingh@gmail.com> <20101022190434.GT32268@Space.Net>
To: Gert Doering <gert@space.net>
X-Mailer: Apple Mail (2.1081)
Cc: 'IETF V6OPS WG' <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 08:27:34 -0000

Hi, Gert,=20

+1, see below.

Le 22 oct. 2010 =E0 21:04, Gert Doering a =E9crit :

> Hi,
>=20
> On Fri, Oct 22, 2010 at 01:59:35PM -0400, Victor Kuarsingh wrote:
>> We (operators) just had the distinct impression that the rules set in =
3056
>> (as I was informed the other day) were "firm" and not likely to be =
broken.
>> Brian noted the other day that 3056 was fitted with that text based =
on
>> "feedback" at that time.  Do you think this can be reversed / =
modified?  I
>> got the impression there is considerable negative support on this.


> One approach to rework 3056 would be to completely deprecate the=20
> 6to4-with-anycast model.  Get the vendors to drop it from their
> operating systems (at least as "default-on") - possibly adding new
> rules that only 6to4<->6to4 traffic is allowed to use the 6to4 =
tunnels,
> and that traffic destined to other IPv6 addresses MUST NOT be sent
> with a source address of 2002::

Full agreement.
In practice, that's:
- deprecation of RFC 3068 (An Anycast Prefix for 6to4 Relay Routers) =20
- modification of RFC 3056 (Connection of IPv6 Domains via IPv4 Clouds), =
to eliminate or at least complete with  the reference to 6to4 relays (or =
at least complete it with a serious warning):
This is restoring the original 6to4 model of =
tools.ietf.org/id/draft-ietf-ngtrans-6to4-00, which works just fine.=20

Regards,
RD


>=20
> So, yes, unreachability for "IPv4-only clients" to "IPv6-only =
servers".
>=20
> If there's real interest to reach those servers, the clients will find
> a way to get IPv6 - but it's unlikely that we'll see IPv6-only servers
> any time soon.
>=20
> Gert Doering
>        -- NetMaster
> --=20
> did you enable IPv6 on something today...?
>=20
> SpaceNet AG                        Vorstand: Sebastian v. Bomhard
> Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. =
Grundner-Culemann
> D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
> Tel: +49 (89) 32356-444            USt-IdNr.: DE813185279
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops



From remi.despres@free.fr  Mon Oct 25 01:33:25 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB98D3A6956 for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 01:33:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.477
X-Spam-Level: 
X-Spam-Status: No, score=-1.477 tagged_above=-999 required=5 tests=[AWL=0.472,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OpB2speRPQWq for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 01:33:24 -0700 (PDT)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.81]) by core3.amsl.com (Postfix) with ESMTP id 91DB13A68B0 for <v6ops@ietf.org>; Mon, 25 Oct 2010 01:33:24 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2419.sfr.fr (SMTP Server) with ESMTP id D21977000088; Mon, 25 Oct 2010 10:35:08 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2419.sfr.fr (SMTP Server) with ESMTP id AEA25700009C; Mon, 25 Oct 2010 10:35:05 +0200 (CEST)
X-SFR-UUID: 20101025083505715.AEA25700009C@msfrf2419.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <174BC871-6568-4569-B4E4-3ADDEB0C565C@cisco.com>
Date: Mon, 25 Oct 2010 10:35:04 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <73AADE49-E703-43DD-8684-94AB26D62906@free.fr>
References: <174BC871-6568-4569-B4E4-3ADDEB0C565C@cisco.com>
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>, v6ops-chairs@tools.ietf.org, Ron Bonica <ron@bonica.org>
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 08:33:26 -0000

The document is really important.
Support.
RD

Le 24 oct. 2010 =E0 20:00, Fred Baker a =E9crit :
> ..
> We are looking specifically for comments on the importance of the =
document as well as its content. If you have read the document and =
believe it to be of operational utility, that is also an important =
comment to make.=20



From teemu.savolainen@nokia.com  Mon Oct 25 01:56:47 2010
Return-Path: <teemu.savolainen@nokia.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 127993A6991 for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 01:56:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.287
X-Spam-Level: 
X-Spam-Status: No, score=-6.287 tagged_above=-999 required=5 tests=[AWL=-0.289, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YCcYYhQVSA0y for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 01:56:37 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id 086273A696C for <v6ops@ietf.org>; Mon, 25 Oct 2010 01:56:36 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-mx06.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o9P8vVT8008639; Mon, 25 Oct 2010 11:58:10 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 25 Oct 2010 11:57:52 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.6]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 25 Oct 2010 11:57:51 +0300
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-02.mgdnok.nokia.com ([65.54.30.6]) with mapi; Mon, 25 Oct 2010 10:57:50 +0200
From: <teemu.savolainen@nokia.com>
To: <rkoodli@cisco.com>, <fred@cisco.com>, <v6ops@ietf.org>
Date: Mon, 25 Oct 2010 10:57:49 +0200
Thread-Topic: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
Thread-Index: ActopRH/JoCme+MzQXiyJfFN4kSgHQIcAP9gACK/4tkAoGaQgA==
Message-ID: <18034D4D7FE9AE48BF19AB1B0EF2729F5F056DA6ED@NOK-EUMSG-01.mgdnok.nokia.com>
References: <18034D4D7FE9AE48BF19AB1B0EF2729F5F0418A89E@NOK-EUMSG-01.mgdnok.nokia.com> <C8E65E7C.A1E3%rkoodli@cisco.com>
In-Reply-To: <C8E65E7C.A1E3%rkoodli@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_18034D4D7FE9AE48BF19AB1B0EF2729F5F056DA6EDNOKEUMSG01mgd_"
MIME-Version: 1.0
X-OriginalArrivalTime: 25 Oct 2010 08:57:51.0891 (UTC) FILETIME=[B4A98630:01CB7422]
X-Nokia-AV: Clean
Cc: v6ops-chairs@tools.ietf.org, ron@bonica.org
Subject: Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 08:56:47 -0000

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

Rajeev,

I agree that anything may happen in the future:)

Hence IPv4 on-demand could happen, but I don't see it happening at the mome=
nt. Hence the draft should be clear that it is something that might be doab=
le, but not something is there out of the box just for network operator to =
activate.

DHCPv4: for WiFi DHCPv4 is used for sure, of course. But a handset that use=
s DHCPv4 for WiFi, but not for cellular (as it is point-to-point), needs mo=
difications. These modifications needs justification, IOP testing, and so f=
orth *for no benefit* for the handset. And of course not all handsets come =
with WiFi, but may come with dual-stack cellular. Justifying introduction o=
f a feature that does not bring benefits but requires effort (money) is oft=
entimes challenging - even if standard would allow. And AFAIK there is no r=
eally significant deployments of DHCPv4 on handsets over cellular that I wo=
uld be aware.

On-demand PDN connection and on-demand IPv4 addressing: I'm against for bot=
h. Tunneling like DS-Lite would be far easier (static private address, and =
then NAT bindings on-demand).

Best regards,

Teemu


From: ext Rajeev Koodli [mailto:rkoodli@cisco.com]
Sent: 22. lokakuuta 2010 07:18
To: Savolainen Teemu (Nokia-MS/Tampere); Fred Baker; v6ops@ietf.org
Cc: v6ops-chairs@tools.ietf.org; ron@bonica.org
Subject: Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC


Hi Teemu,

Thanks for your feedback.

On-demand approaches: we had a good discussion already on the matter, and I=
 have revised the ID based on that discussion. Yes, there are no handsets d=
oing this, but we left it open for laptops which may do this. If this is no=
t a possibility at all, it would remain as an option; at this stage, I am n=
ot sure if we should say it is Not an option at all..

DHCPv4 on cellular handsets: again, the statement is not implying that they=
 will surely implement DHCPv4. May be you can see what's coming in the futu=
re better than I do, but I am going with the option that already exists in =
3GPP standards - PCO to defer address allocation and then using DHCPv4. Aga=
in, this may never be done, but it's premature to say it will never be done=
. Besides, consider the handsets accessing the EPC via WiFi interface, and =
not the cellular interface. Would you say that handsets will not do DHCPv4 =
over WiFi as well?

Yes, there are additional considerations, and the ID is not making any reco=
mmendations to use on-demand/DHCPv4.As you point out, the ID is only pointi=
ng out that carriers may consider investigating the on-demand addressing.
(BTW, on-demand PDN is subject to session inactivity timers, and is not the=
 same as on-demand IPv4 addressing).

3G always-on: okay, I will add some clarifying text.

Regards,

-Rajeev


On 10/21/10 5:01 AM, "teemu.savolainen@nokia.com" <teemu.savolainen@nokia.c=
om> wrote:
Hi,

Section 3.1: it is true that IPv4 PDN on-demand and deferred IPv4 address a=
llocations are "approaches" in theory, but I do not believe their applicabi=
lity in practice. E.g. what is the likelyhood that popular desktop OSes wou=
ld suddenly implement that kind of features (isn't the style usually ask DH=
CPv4 right at interface up and then renew forever)?

Section 3.1: I do not believe cellular handsets will implement DHCPv4 for c=
ellular interfaces. Hence I disagree with:"this may very well change in the=
 future release". Cellular handsets have managed without DHCPv4 since the d=
awn of packet switched cellular networks. Why on earth they would now start=
 to use DHCPv4 on cellular access at the very twilight of IPv4?

The "additional considerations" is huge, like there is no benefit whatsoeve=
r for hosts to do IPv4 on-demand or deferred IPv4 address allocation. Also =
it is non-trivial, like whether DHCPv4 should be triggered if application b=
inds socket to 127.0.0.1..

I also slightly disagree with this:" On the other hand, in the existing 3G =
UMTS networks, there is no requirement for an always-on connection". While =
there is no such requirement from standards bodies, essentially for many de=
vices there is from the end user direction: users want to have IM/Skype/ema=
il always on. Should be clarified.

I seem to agree with the conclusions document draws at the end of section 3=
.1 (there is nothing wrong in doing investigations of on-demand PDN..:)

Best regards,

Teemu


From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of e=
xt Fred Baker
Sent: 10. lokakuuta 2010 21:00
To: IPv6 Operations
Cc: v6ops-chairs@tools.ietf.org; Ron Bonica
Subject: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC


This is to initiate a two week working group last call of draft-ietf-v6ops-=
v6-in-mobile-networks. Please read it now. If you find nits (spelling error=
s, minor suggested wording changes, etc), comment to the authors; if you fi=
nd greater issues, such as disagreeing with a statement or finding addition=
al issues that need to be addressed, please post your comments to the list.



We are looking specifically for comments on the importance of the document =
as well as its content. If you have read the document and believe it to be =
of operational utility, that is also an important comment to make.
________________________________
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" 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 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC</title>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{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:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=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:#1F497D'>Rajeev,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>I agree that anything may happen in the future</span><span
style=3D'font-size:11.0pt;font-family:Wingdings;color:#1F497D'>J</span><spa=
n
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'=
> <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Hence IPv4 on-demand could happen, but I don&#8217;t see it =
happening
at the moment. Hence the draft should be clear that it is something that mi=
ght
be doable, but not something is there out of the box just for network opera=
tor
to activate.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>DHCPv4: for WiFi DHCPv4 is used for sure, of course. But a
handset that uses DHCPv4 for WiFi, but not for cellular (as it is
point-to-point), needs modifications. These modifications needs justificati=
on,
IOP testing, and so forth *<b>for no benefit</b>* for the handset. And of
course not all handsets come with WiFi, but may come with dual-stack cellul=
ar. Justifying
introduction of a feature that does not bring benefits but requires effort
(money) is oftentimes challenging &#8211; even if standard would allow. And=
 AFAIK
there is no really significant deployments of DHCPv4 on handsets over cellu=
lar
that I would be aware. <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>On-demand PDN connection and on-demand IPv4 addressing: I&#8=
217;m
against for both. Tunneling like DS-Lite would be far easier (static privat=
e
address, and then NAT bindings on-demand).<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Best regards,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Teemu<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> ext Rajeev Ko=
odli
[mailto:rkoodli@cisco.com] <br>
<b>Sent:</b> 22. lokakuuta 2010 07:18<br>
<b>To:</b> Savolainen Teemu (Nokia-MS/Tampere); Fred Baker; v6ops@ietf.org<=
br>
<b>Cc:</b> v6ops-chairs@tools.ietf.org; ron@bonica.org<br>
<b>Subject:</b> Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC<o:p=
></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span style=3D'font-siz=
e:11.0pt;
font-family:"Calibri","sans-serif"'><br>
Hi Teemu,<br>
<br>
Thanks for your feedback.<br>
<br>
On-demand approaches: we had a good discussion already on the matter, and I
have revised the ID based on that discussion. Yes, there are no handsets do=
ing
this, but we left it open for laptops which may do this. If this is not a
possibility at all, it would remain as an option; at this stage, I am not s=
ure
if we should say it is Not an option at all..<br>
<br>
DHCPv4 on cellular handsets: again, the statement is not implying that they
will surely implement DHCPv4. May be you can see what&#8217;s coming in the=
 future
better than I do, but I am going with the option that already exists in 3GP=
P
standards &#8211; PCO to defer address allocation and then using DHCPv4. Ag=
ain, this
may never be done, but it&#8217;s premature to say it <i>will</i> never be =
done.
Besides, consider the handsets accessing the EPC via WiFi interface, and no=
t
the cellular interface. Would you say that handsets will not do DHCPv4 over
WiFi as well?<br>
<br>
Yes, there are additional considerations, and the ID is not making any
recommendations to use on-demand/DHCPv4.As you point out, the ID is only
pointing out that carriers may consider investigating the on-demand address=
ing.<br>
(BTW, on-demand PDN is subject to session inactivity timers, and is not the
same as on-demand IPv4 addressing).<br>
<br>
3G always-on: okay, I will add some clarifying text.<br>
<br>
Regards,<br>
<br>
-Rajeev<br>
<br>
<br>
On 10/21/10 5:01 AM, &quot;<a href=3D"teemu.savolainen@nokia.com">teemu.sav=
olainen@nokia.com</a>&quot;
&lt;<a href=3D"teemu.savolainen@nokia.com">teemu.savolainen@nokia.com</a>&g=
t;
wrote:</span><o:p></o:p></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span style=3D'font-siz=
e:11.0pt;
font-family:"Calibri","sans-serif";color:#1F497D'>Hi,<br>
&nbsp;<br>
Section 3.1: it is true that IPv4 PDN on-demand and deferred IPv4 address
allocations are &#8220;approaches&#8221; in theory, but I do not believe th=
eir
applicability in practice. E.g. what is the likelyhood that popular desktop
OSes would suddenly implement that kind of features (isn&#8217;t the style =
usually
ask DHCPv4 right at interface up and then renew forever)?<br>
&nbsp;<br>
Section 3.1: I do not believe cellular handsets will implement DHCPv4 for
cellular interfaces. Hence I disagree with:&#8221;this may very well change=
 in the
future release&#8221;. Cellular handsets have managed without DHCPv4 since =
the dawn
of packet switched cellular networks. Why on earth they would now start to =
use
DHCPv4 on cellular access at the very twilight of IPv4? <br>
&nbsp;<br>
The &#8220;additional considerations&#8221; is huge, like there is no benef=
it whatsoever
for hosts to do IPv4 on-demand or deferred IPv4 address allocation. Also it=
 is
non-trivial, like whether DHCPv4 should be triggered if application binds
socket to 127.0.0.1..<br>
&nbsp;<br>
I also slightly disagree with this:&#8221; On the other hand, in the existi=
ng 3G UMTS
networks, there is no requirement for an always-on connection&#8221;. While=
 there is
no such requirement from standards bodies, essentially for many devices the=
re
is from the end user direction: users want to have IM/Skype/email always on=
.
Should be clarified.<br>
&nbsp;<br>
I seem to agree with the conclusions document draws at the end of section 3=
.1
(there is nothing wrong in doing investigations of on-demand PDN..</span><s=
pan
style=3D'font-size:11.0pt;font-family:Wingdings;color:#1F497D'>J<br>
</span><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><br>
Best regards,<br>
&nbsp;<br>
Teemu<br>
&nbsp;<br>
</span><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>=
<br>
</span><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"=
'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a
href=3D"v6ops-bounces@ietf.org">v6ops-bounces@ietf.org</a> [<a
href=3D"mailto:v6ops-bounces@ietf.org">mailto:v6ops-bounces@ietf.org</a>] <=
b>On
Behalf Of </b>ext Fred Baker<br>
<b>Sent:</b> 10. lokakuuta 2010 21:00<br>
<b>To:</b> IPv6 Operations<br>
<b>Cc:</b> <a href=3D"v6ops-chairs@tools.ietf.org">v6ops-chairs@tools.ietf.=
org</a>;
Ron Bonica<br>
<b>Subject:</b> [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC<br>
</span><br>
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><br>
</span><span style=3D'font-size:9.0pt;font-family:"Helvetica","sans-serif"'=
>This
is to initiate a two week working group last call of
draft-ietf-v6ops-v6-in-mobile-networks. Please read it now. If you find nit=
s
(spelling errors, minor suggested wording changes, etc), comment to the
authors; if you find greater issues, such as disagreeing with a statement o=
r
finding additional issues that need to be addressed, please post your comme=
nts
to the list.<br>
</span><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>=
<br>
</span><span style=3D'font-size:9.0pt;font-family:"Helvetica","sans-serif"'=
><br>
</span><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>=
<br>
</span><span style=3D'font-size:9.0pt;font-family:"Helvetica","sans-serif"'=
>We
are looking specifically for comments on the importance of the document as =
well
as its content. If you have read the document and believe it to be of
operational utility, that is also an important comment to make.</span><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p></=
span></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>

<hr size=3D3 width=3D"95%" align=3Dcenter>

</span></div>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:Consolas'>=
_______________________________________________<br>
v6ops mailing list<br>
<a href=3D"v6ops@ietf.org">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops">https://www.ietf.or=
g/mailman/listinfo/v6ops</a></span><o:p></o:p></p>

</div>

</div>

</body>

</html>

--_000_18034D4D7FE9AE48BF19AB1B0EF2729F5F056DA6EDNOKEUMSG01mgd_--

From ipng@69706e6720323030352d30312d31340a.nosense.org  Mon Oct 25 02:05:46 2010
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B81513A6979 for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 02:05:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.46
X-Spam-Level: 
X-Spam-Status: No, score=-1.46 tagged_above=-999 required=5 tests=[AWL=0.435,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 84Z19zkHRxHK for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 02:05:45 -0700 (PDT)
Received: from smtp1.adam.net.au (smtp1.adam.net.au [202.136.110.253]) by core3.amsl.com (Postfix) with ESMTP id 1DE8F3A6982 for <v6ops@ietf.org>; Mon, 25 Oct 2010 02:05:41 -0700 (PDT)
Received: from 182-239-171-173.ip.adam.com.au ([182.239.171.173] helo=opy.nosense.org) by smtp1.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1PAJ1S-0005py-N6; Mon, 25 Oct 2010 19:37:18 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id B70F23B32F; Mon, 25 Oct 2010 19:37:17 +1030 (CST)
Date: Mon, 25 Oct 2010 19:37:16 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Ole Troan <ot@cisco.com>
Message-ID: <20101025193716.6bb624f3@opy.nosense.org>
In-Reply-To: <69BB450D-B503-4F3D-8B70-7AAF17F0E95C@cisco.com>
References: <C8E76098.2AFB6%john_brzozowski@cable.comcast.com> <6D313496-536D-4952-8599-F4B5D8386168@cisco.com> <4CC209DD.6020801@gmail.com> <69BB450D-B503-4F3D-8B70-7AAF17F0E95C@cisco.com>
X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: 'IPv6 Operations' <v6ops@ietf.org>, "Brzozowski, John" <John_Brzozowski@cable.comcast.com>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 09:05:46 -0000

On Sat, 23 Oct 2010 00:26:00 +0200
Ole Troan <ot@cisco.com> wrote:

> Brian,
> 
> >>> To add to Tony's point, I have to agree that there are folks that do not
> >>> have experience operating networks, specifically deploying IPv6, that seem
> >>> to enjoy asserting their assumptions and views.  Instead of doing this it
> >>> might be useful (and more productive) if folks first tried to understand how
> >>> various types of networks work before making recommendations, etc.
> >> 
> >> perhaps it would be equally productive if the operators tried to understand how end-users would want to build their networks?
> >> 
> >> I base my previous assumption on RFC3177. as we're on an IETF list, is there any other IETF recommendation for a different allocation model?
> > 
> > On 2010-10-18 07:00, Fred Baker wrote:
> > 
> >>>> Next week (I'm giving you an extra week's notice as I know you are busy), the IETF IPv6 Operations Working Group is initiating a two week working group last call of 
> >>>> 
> >>>> http://tools.ietf.org/html/draft-ietf-v6ops-3177bis-end-sites
> >>>>  "IPv6 Address Assignment to End Sites", Thomas Narten, Geoff Huston,
> >>>>  Rosalea Roberts
> 
> do you think rfc3177bis changes this?
> i.e. does it no longer advocate that "sites should get sufficient address space without jumping through hoops"? and that this should be a long lived address block assignment, not one which is subject to dynamically change as the end user network grows or shrinks?
> 
> I have no issue with delegation of address space of arbitrary length.
> I have an issue with:
>  - the expectation that an RR will know what to ask for
>  - that RFC3633 provides a suitable mechanism for negotiating address space size
> 
> as one of the authors of RFC3633, I think it is fair that I declare what assumptions that document was written under. my assumption was one of delegation of long-lived prefixes without any negotiation, i.e. with assignment size set by the delegating routers. and that is in the spirit the document is written. if operators want to delegate prefixes in a different fashion, they have to be aware that the tool (3633) may not be up for the task.
> 

If you start trying to play the 'right sizing' game, you're
treating the IPv6 address space like it is scarce. You're unnecessarily
increasing your operational effort because you'll now have to monitor
prefix utilisation, periodically add to the pool, make projections
about future utilisation, possibly deal with a service outage if you
don't make good future projections and exhaust the pool (likely at
night in a residential environment), and record more details about who
had what prefix at what time and now also the prefix length that they
had at that time.

Or you can just throw address space at the problem, giving
most typical customers more than they're likely to need, and
eliminate all this unnecessary effort and risk.

Regards,
Mark.


From sander@steffann.nl  Mon Oct 25 02:45:49 2010
Return-Path: <sander@steffann.nl>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B6CC53A69B7 for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 02:45:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VkLuz0KEquJe for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 02:45:48 -0700 (PDT)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by core3.amsl.com (Postfix) with ESMTP id 06D3D3A6998 for <v6ops@ietf.org>; Mon, 25 Oct 2010 02:45:47 -0700 (PDT)
Received: from macpro.10ww.steffann.nl (unknown [IPv6:2001:610:6ce:1:224:36ff:feef:1d89]) by mail.sintact.nl (Postfix) with ESMTP id 13A0C2052; Mon, 25 Oct 2010 11:47:31 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <20101025193716.6bb624f3@opy.nosense.org>
Date: Mon, 25 Oct 2010 11:47:30 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1DC22719-4C51-4B60-B1A7-4FC5CF7DEA00@steffann.nl>
References: <C8E76098.2AFB6%john_brzozowski@cable.comcast.com> <6D313496-536D-4952-8599-F4B5D8386168@cisco.com> <4CC209DD.6020801@gmail.com> <69BB450D-B503-4F3D-8B70-7AAF17F0E95C@cisco.com> <20101025193716.6bb624f3@opy.nosense.org>
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Mailer: Apple Mail (2.1081)
Cc: 'IPv6 Operations' <v6ops@ietf.org>, "Brzozowski, John" <John_Brzozowski@cable.comcast.com>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 09:45:49 -0000

> If you start trying to play the 'right sizing' game, you're
> treating the IPv6 address space like it is scarce. You're =
unnecessarily
> increasing your operational effort because you'll now have to monitor
> prefix utilisation, periodically add to the pool, make projections
> about future utilisation, possibly deal with a service outage if you
> don't make good future projections and exhaust the pool (likely at
> night in a residential environment), and record more details about who
> had what prefix at what time and now also the prefix length that they
> had at that time.
>=20
> Or you can just throw address space at the problem, giving
> most typical customers more than they're likely to need, and
> eliminate all this unnecessary effort and risk.

Yes please. I want IPv6 deployment to be as easy and painless as =
possible. I'll give every customer a /48 or a /56 and stop worrying =
about 'right sizing'. We have enough IPv6 address space for this, and =
these dynamic assignment mechanisms have too many possible points of =
failure (as you pointed out).

- Sander


From Wesley.E.George@sprint.com  Mon Oct 25 06:23:37 2010
Return-Path: <Wesley.E.George@sprint.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB9B23A6877 for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 06:23:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.669
X-Spam-Level: 
X-Spam-Status: No, score=-3.669 tagged_above=-999 required=5 tests=[AWL=-0.070, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RuSD8oRn-9og for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 06:23:35 -0700 (PDT)
Received: from AM1EHSOBE004.bigfish.com (am1ehsobe004.messaging.microsoft.com [213.199.154.207]) by core3.amsl.com (Postfix) with ESMTP id 6296C3A686B for <v6ops@ietf.org>; Mon, 25 Oct 2010 06:23:35 -0700 (PDT)
Received: from mail34-am1-R.bigfish.com (10.3.201.253) by AM1EHSOBE004.bigfish.com (10.3.204.24) with Microsoft SMTP Server id 14.1.225.8; Mon, 25 Oct 2010 13:25:19 +0000
Received: from mail34-am1 (localhost.localdomain [127.0.0.1])	by mail34-am1-R.bigfish.com (Postfix) with ESMTP id C781C1C7815F; Mon, 25 Oct 2010 13:25:19 +0000 (UTC)
X-SpamScore: -32
X-BigFish: VS-32(zz542N1432Nzz1202hzz8275dh1033ILz2fh2a8h61h)
X-Spam-TCS-SCL: 0:0
X-Forefront-Antispam-Report: KIP:(null); UIP:(null); IPVD:NLI; H:pdaasdm2.corp.sprint.com; RD:smtpda2.sprint.com; EFVD:NLI
Received: from mail34-am1 (localhost.localdomain [127.0.0.1]) by mail34-am1 (MessageSwitch) id 1288013119548927_25999; Mon, 25 Oct 2010 13:25:19 +0000 (UTC)
Received: from AM1EHSMHS011.bigfish.com (unknown [10.3.201.241])	by mail34-am1.bigfish.com (Postfix) with ESMTP id 824CD228050; Mon, 25 Oct 2010 13:25:19 +0000 (UTC)
Received: from pdaasdm2.corp.sprint.com (144.229.32.57) by AM1EHSMHS011.bigfish.com (10.3.207.111) with Microsoft SMTP Server (TLS) id 14.1.225.8; Mon, 25 Oct 2010 13:25:17 +0000
Received: from PDAWEH01.ad.sprint.com (PDAWEH01.corp.sprint.com [144.226.110.69])	by pdaasdm2.corp.sprint.com (Sentrion-MTA-4.0.5/Sentrion-MTA-4.0.5) with ESMTP id o9PDJEsl007015 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 25 Oct 2010 08:19:46 -0500
Received: from PLSWM12A.ad.sprint.com ([fe80::dd81:e8a1:cd6b:78f]) by PDAWEH01.ad.sprint.com ([2002:90e2:6e45::90e2:6e45]) with mapi id 14.01.0255.000; Mon, 25 Oct 2010 08:24:51 -0500
From: "George, Wes E IV [NTK]" <Wesley.E.George@sprint.com>
To: Fred Baker <fred@cisco.com>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] draft-ietf-v6ops-3177bis-end-sites WGLC
Thread-Index: AQHLc6V4wbLLHaEnLEeC/812uJU+KpNRqFbQ
Date: Mon, 25 Oct 2010 13:24:51 +0000
Message-ID: <54E900DC635DAB4DB7A6D799B3C4CD8E01760B@PLSWM12A.ad.sprint.com>
References: <174BC871-6568-4569-B4E4-3ADDEB0C565C@cisco.com>
In-Reply-To: <174BC871-6568-4569-B4E4-3ADDEB0C565C@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.153.203.31]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: sprint.com
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 13:23:38 -0000

> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
> Of Fred Baker
> Subject: [v6ops] draft-ietf-v6ops-3177bis-end-sites WGLC
>
> This is to initiate a two week working group last call of draft-ietf-
> v6ops-3177bis-end-sites.
>If you have read the document and
> believe it to be of operational utility, that is also an important
> comment to make.
[WES] I support this document

Wes George

________________________________

This e-mail may contain Sprint Nextel proprietary information intended for =
the sole use of the recipient(s). Any use by others is prohibited. If you a=
re not the intended recipient, please contact the sender and delete all cop=
ies of the message.


From ricpatara@gmail.com  Mon Oct 25 07:21:12 2010
Return-Path: <ricpatara@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 356423A69CF for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 07:21:12 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xm8cgCHhkGCl for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 07:21:08 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id 408213A685B for <v6ops@ietf.org>; Mon, 25 Oct 2010 07:21:08 -0700 (PDT)
Received: by gya6 with SMTP id 6so2288247gya.31 for <v6ops@ietf.org>; Mon, 25 Oct 2010 07:22:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=cuiJcTNrJ+WHHgT+EteJtwwwBm0k3DwwVPpsdXdVczc=; b=deQIDhPXiJQPbXsMtmlz8t2T7rS3cdRH6L5bOPSCpHEefHz73vzB210Hxh+WLKsd7X 8UgodjK9wtIaMEQR0jEUSeYc0UFsy3ajxXCn/Y+KR8+6P/ibeuTFnvhLs4A1rGIjUkNA xBncQSiM9/baVvGaYupQ/rwIQ5yV/ve+KVLmI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=UNDAgIQ9Z+IZXHswYmvA2MswzBYe3wF723zVJ/DOQa0NMtqw1hgih++tBt9uZEcblo yQoEavBLMvaH9vkNnMgmcTbmdsQl4s5vde6gSkb88reb0EITjaLl9hCBK+W2jKU7JwYY RrE1Ts85iohJ/Y5bpJzxw+nym3JQH1MKPD068=
Received: by 10.100.121.18 with SMTP id t18mr2612306anc.125.1288016573141; Mon, 25 Oct 2010 07:22:53 -0700 (PDT)
Received: from [200.160.3.105] (3.105.net.registro.br [200.160.3.105]) by mx.google.com with ESMTPS id b25sm8753198anb.3.2010.10.25.07.22.51 (version=SSLv3 cipher=RC4-MD5); Mon, 25 Oct 2010 07:22:52 -0700 (PDT)
From: Ricardo Patara <ricpatara@gmail.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <174BC871-6568-4569-B4E4-3ADDEB0C565C@cisco.com>
References: <174BC871-6568-4569-B4E4-3ADDEB0C565C@cisco.com>
Content-Type: text/plain; charset="ISO-8859-15"
Date: Mon, 25 Oct 2010 12:22:49 -0200
Message-ID: <1288016569.1813.5.camel@patara>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>, v6ops-chairs@tools.ietf.org, Ron, Bonica <ron@bonica.org>
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 14:21:12 -0000

I also support this document

 Ricardo

On Dom, 2010-10-24 at 11:00 -0700, Fred Baker wrote:
> This is to initiate a two week working group last call of draft-ietf-v6ops-3177bis-end-sites. Please read it now. If you find nits (spelling errors, minor suggested wording changes, etc), comment to the authors; if you find greater issues, such as disagreeing with a statement or finding additional issues that need to be addressed, please post your comments to the list.
> 
> We are looking specifically for comments on the importance of the document as well as its content. If you have read the document and believe it to be of operational utility, that is also an important comment to make. 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From bs7652@att.com  Mon Oct 25 07:38:22 2010
Return-Path: <bs7652@att.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7617C3A69ED for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 07:38:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.43
X-Spam-Level: 
X-Spam-Status: No, score=-106.43 tagged_above=-999 required=5 tests=[AWL=0.169, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kHRE0xpbGNJs for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 07:38:18 -0700 (PDT)
Received: from mail146.messagelabs.com (mail146.messagelabs.com [216.82.241.147]) by core3.amsl.com (Postfix) with ESMTP id D10DA3A6A1C for <v6ops@ietf.org>; Mon, 25 Oct 2010 07:38:17 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: bs7652@att.com
X-Msg-Ref: server-9.tower-146.messagelabs.com!1288017601!25636988!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 22513 invoked from network); 25 Oct 2010 14:40:02 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-9.tower-146.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 25 Oct 2010 14:40:02 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o9PEdN3R004332; Mon, 25 Oct 2010 10:39:24 -0400
Received: from 01GAF5142010624.AD.BLS.COM (01GAF5142010624.ad.bls.com [139.76.131.91]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with SMTP id o9PEdHLq004221; Mon, 25 Oct 2010 10:39:17 -0400
Received: from 01NC27689010625.AD.BLS.COM ([90.144.44.200]) by 01GAF5142010624.AD.BLS.COM with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 25 Oct 2010 10:39:54 -0400
Received: from 01NC27689010650.AD.BLS.COM ([90.144.44.120]) by 01NC27689010625.AD.BLS.COM with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 25 Oct 2010 10:39:53 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 25 Oct 2010 10:39:52 -0400
Message-ID: <750BF7861EBBE048B3E648B4BB6E8F4F172336E1@crexc50p>
In-Reply-To: <20101023095343.GX32268@Space.Net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
Thread-Index: ActymDPW7RrO0/ciRn61mmYSSdwMBgBsqtKA
References: <DE7AE48C-76C8-4D1E-946B-43CD520FD86C@cisco.com><C8E76BB2.2B026%john_brzozowski@cable.comcast.com> <20101023095343.GX32268@Space.Net>
From: "STARK, BARBARA H (ATTLABS)" <bs7652@att.com>
To: "Gert Doering" <gert@space.net>, "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
X-OriginalArrivalTime: 25 Oct 2010 14:39:53.0618 (UTC) FILETIME=[7C908F20:01CB7452]
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] DHCPv6 vs ND strikes again (was: New version available)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 14:38:22 -0000

+1 on what Gert said. Which is consistent with IPv6 architecture
recommendations I've seen coming from Broadband Forum. Which causes me
to suspect it is a provisioning methodology planned to be used by many.
Barbara

> > Provisioning large blocks across the board may not reliably work
> either.
> >
> > Perhaps the IGD should simply relay downstream IA_PD requests from
> within
> > the premise and let the other RRs negotiate their own prefix
requests
> with
> > the operator DHCPv6 servers?
>=20
> Our provisioning system will give the customer *one* prefix (/56 or
> /48).
>=20
> How the customer splits this in their home is their business, and we
> don't
> want to hear about it.  That is: hierarchical PD is fine, sending
extra
> PD requests to us for every router in their home is not going to work.
>=20
> Gert Doering

From rkoodli@cisco.com  Mon Oct 25 09:11:06 2010
Return-Path: <rkoodli@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F3613A6A97 for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 09:11:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.662
X-Spam-Level: 
X-Spam-Status: No, score=-108.662 tagged_above=-999 required=5 tests=[AWL=-0.060, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7YB5HaDc8QAX for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 09:10:36 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 986B73A6A98 for <v6ops@ietf.org>; Mon, 25 Oct 2010 09:10:16 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhkGAC5JxUytJV2c/2dsb2JhbACBRZ9GU3GgfpwrgnWCUwSEVIV5gww
X-IronPort-AV: E=Sophos;i="4.58,236,1286150400";  d="scan'208,217";a="174763571"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rtp-iport-1.cisco.com with ESMTP; 25 Oct 2010 16:11:49 +0000
Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id o9PGBn1F000980;  Mon, 25 Oct 2010 16:11:49 GMT
Received: from xmb-rcd-111.cisco.com ([72.163.62.153]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 25 Oct 2010 11:11:49 -0500
Received: from 10.21.147.86 ([10.21.147.86]) by XMB-RCD-111.cisco.com ([72.163.62.153]) with Microsoft Exchange Server HTTP-DAV ;  Mon, 25 Oct 2010 16:11:49 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Mon, 25 Oct 2010 09:24:24 -0700
From: Rajeev Koodli <rkoodli@cisco.com>
To: <teemu.savolainen@nokia.com>, Fred Baker <fred@cisco.com>, <v6ops@ietf.org>
Message-ID: <C8EAFD48.A335%rkoodli@cisco.com>
Thread-Topic: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
Thread-Index: ActopRH/JoCme+MzQXiyJfFN4kSgHQIcAP9gACK/4tkAoGaQgAAP2Y+p
In-Reply-To: <18034D4D7FE9AE48BF19AB1B0EF2729F5F056DA6ED@NOK-EUMSG-01.mgdnok.nokia.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3370843464_11845358"
X-OriginalArrivalTime: 25 Oct 2010 16:11:49.0786 (UTC) FILETIME=[5474FFA0:01CB745F]
Cc: v6ops-chairs@tools.ietf.org, ron@bonica.org
Subject: Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 16:11:06 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3370843464_11845358
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable


Teemu,

I am not sure how it is an issue to run DHCPv4 over WiFi and not use DHCPv4
over cellular.
AFAICT, iPhone seems to be doing it today; please correct me otherwise.

Thanks,

-Rajeev



On 10/25/10 1:57 AM, "teemu.savolainen@nokia.com"
<teemu.savolainen@nokia.com> wrote:

> Rajeev,
> =20
> I agree that anything may happen in the futureJ
> =20
> Hence IPv4 on-demand could happen, but I don=B9t see it happening at the mo=
ment.
> Hence the draft should be clear that it is something that might be doable=
, but
> not something is there out of the box just for network operator to activa=
te.
> =20
> DHCPv4: for WiFi DHCPv4 is used for sure, of course. But a handset that u=
ses
> DHCPv4 for WiFi, but not for cellular (as it is point-to-point), needs
> modifications. These modifications needs justification, IOP testing, and =
so
> forth *for no benefit* for the handset. And of course not all handsets co=
me
> with WiFi, but may come with dual-stack cellular. Justifying introduction=
 of a
> feature that does not bring benefits but requires effort (money) is often=
times
> challenging =AD even if standard would allow. And AFAIK there is no really
> significant deployments of DHCPv4 on handsets over cellular that I would =
be
> aware.=20
> =20
> On-demand PDN connection and on-demand IPv4 addressing: I=B9m against for b=
oth.
> Tunneling like DS-Lite would be far easier (static private address, and t=
hen
> NAT bindings on-demand).
> =20
> Best regards,
> =20
> Teemu
> =20
> =20
>=20
> From: ext Rajeev Koodli [mailto:rkoodli@cisco.com]
> Sent: 22. lokakuuta 2010 07:18
> To: Savolainen Teemu (Nokia-MS/Tampere); Fred Baker; v6ops@ietf.org
> Cc: v6ops-chairs@tools.ietf.org; ron@bonica.org
> Subject: Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
> =20
>=20
> Hi Teemu,
>=20
> Thanks for your feedback.
>=20
> On-demand approaches: we had a good discussion already on the matter, and=
 I
> have revised the ID based on that discussion. Yes, there are no handsets =
doing
> this, but we left it open for laptops which may do this. If this is not a
> possibility at all, it would remain as an option; at this stage, I am not=
 sure
> if we should say it is Not an option at all..
>=20
> DHCPv4 on cellular handsets: again, the statement is not implying that th=
ey
> will surely implement DHCPv4. May be you can see what=B9s coming in the fut=
ure
> better than I do, but I am going with the option that already exists in 3=
GPP
> standards =AD PCO to defer address allocation and then using DHCPv4. Again,=
 this
> may never be done, but it=B9s premature to say it will never be done. Besid=
es,
> consider the handsets accessing the EPC via WiFi interface, and not the
> cellular interface. Would you say that handsets will not do DHCPv4 over W=
iFi
> as well?
>=20
> Yes, there are additional considerations, and the ID is not making any
> recommendations to use on-demand/DHCPv4.As you point out, the ID is only
> pointing out that carriers may consider investigating the on-demand
> addressing.
> (BTW, on-demand PDN is subject to session inactivity timers, and is not t=
he
> same as on-demand IPv4 addressing).
>=20
> 3G always-on: okay, I will add some clarifying text.
>=20
> Regards,
>=20
> -Rajeev
>=20
>=20
> On 10/21/10 5:01 AM, "teemu.savolainen@nokia.com" <teemu.savolainen@nokia=
.com>
> wrote:
> Hi,
> =20
> Section 3.1: it is true that IPv4 PDN on-demand and deferred IPv4 address
> allocations are =B3approaches=B2 in theory, but I do not believe their
> applicability in practice. E.g. what is the likelyhood that popular deskt=
op
> OSes would suddenly implement that kind of features (isn=B9t the style usua=
lly
> ask DHCPv4 right at interface up and then renew forever)?
> =20
> Section 3.1: I do not believe cellular handsets will implement DHCPv4 for
> cellular interfaces. Hence I disagree with:=B2this may very well change in =
the
> future release=B2. Cellular handsets have managed without DHCPv4 since the =
dawn
> of packet switched cellular networks. Why on earth they would now start t=
o use
> DHCPv4 on cellular access at the very twilight of IPv4?
> =20
> The =B3additional considerations=B2 is huge, like there is no benefit whatsoe=
ver
> for hosts to do IPv4 on-demand or deferred IPv4 address allocation. Also =
it is
> non-trivial, like whether DHCPv4 should be triggered if application binds
> socket to 127.0.0.1..
> =20
> I also slightly disagree with this:=B2 On the other hand, in the existing 3=
G
> UMTS networks, there is no requirement for an always-on connection=B2. Whil=
e
> there is no such requirement from standards bodies, essentially for many
> devices there is from the end user direction: users want to have
> IM/Skype/email always on. Should be clarified.
> =20
> I seem to agree with the conclusions document draws at the end of section=
 3.1
> (there is nothing wrong in doing investigations of on-demand PDN..J
>=20
> Best regards,
> =20
> Teemu
> =20
>=20
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of=
 ext
> Fred Baker
> Sent: 10. lokakuuta 2010 21:00
> To: IPv6 Operations
> Cc: v6ops-chairs@tools.ietf.org; Ron Bonica
> Subject: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
>=20
>=20
> This is to initiate a two week working group last call of
> draft-ietf-v6ops-v6-in-mobile-networks. Please read it now. If you find n=
its
> (spelling errors, minor suggested wording changes, etc), comment to the
> authors; if you find greater issues, such as disagreeing with a statement=
 or
> finding additional issues that need to be addressed, please post your com=
ments
> to the list.
>=20
>=20
>=20
> We are looking specifically for comments on the importance of the documen=
t as
> well as its content. If you have read the document and believe it to be o=
f
> operational utility, that is also an important comment to make.
>=20
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>=20


--B_3370843464_11845358
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:11pt=
'><BR>
Teemu,<BR>
<BR>
I am not sure how it is an issue to run DHCPv4 over WiFi and not use DHCPv4=
 over cellular.<BR>
AFAICT, iPhone seems to be doing it today; please correct me otherwise.<BR>
<BR>
Thanks,<BR>
<BR>
-Rajeev<BR>
<BR>
<BR>
<BR>
On 10/25/10 1:57 AM, &quot;<a href=3D"teemu.savolainen@nokia.com">teemu.savol=
ainen@nokia.com</a>&quot; &lt;<a href=3D"teemu.savolainen@nokia.com">teemu.sav=
olainen@nokia.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><=
SPAN STYLE=3D'font-size:11pt'><FONT COLOR=3D"#1F497D">Rajeev,<BR>
&nbsp;<BR>
I agree that anything may happen in the future</FONT></SPAN></FONT><SPAN ST=
YLE=3D'font-size:11pt'><FONT COLOR=3D"#1F497D"><FONT FACE=3D"Wingdings">J</FONT><F=
ONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> <BR>
&nbsp;<BR>
Hence IPv4 on-demand could happen, but I don&#8217;t see it happening at th=
e moment. Hence the draft should be clear that it is something that might be=
 doable, but not something is there out of the box just for network operator=
 to activate.<BR>
&nbsp;<BR>
DHCPv4: for WiFi DHCPv4 is used for sure, of course. But a handset that use=
s DHCPv4 for WiFi, but not for cellular (as it is point-to-point), needs mod=
ifications. These modifications needs justification, IOP testing, and so for=
th *<B>for no benefit</B>* for the handset. And of course not all handsets c=
ome with WiFi, but may come with dual-stack cellular. Justifying introductio=
n of a feature that does not bring benefits but requires effort (money) is o=
ftentimes challenging &#8211; even if standard would allow. And AFAIK there =
is no really significant deployments of DHCPv4 on handsets over cellular tha=
t I would be aware. <BR>
&nbsp;<BR>
On-demand PDN connection and on-demand IPv4 addressing: I&#8217;m against f=
or both. Tunneling like DS-Lite would be far easier (static private address,=
 and then NAT bindings on-demand).<BR>
&nbsp;<BR>
Best regards,<BR>
&nbsp;<BR>
Teemu<BR>
&nbsp;<BR>
&nbsp;<BR>
</FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><BR>
</FONT></SPAN><FONT SIZE=3D"2"><FONT FACE=3D"Tahoma, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:10pt'><B>From:</B> ext Rajeev Koodli [<a href=3D"mailt=
o:rkoodli@cisco.com">mailto:rkoodli@cisco.com</a>] <BR>
<B>Sent:</B> 22. lokakuuta 2010 07:18<BR>
<B>To:</B> Savolainen Teemu (Nokia-MS/Tampere); Fred Baker; <a href=3D"v6ops@=
ietf.org">v6ops@ietf.org</a><BR>
<B>Cc:</B> <a href=3D"v6ops-chairs@tools.ietf.org">v6ops-chairs@tools.ietf.or=
g</a>; <a href=3D"ron@bonica.org">ron@bonica.org</a><BR>
<B>Subject:</B> Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Times New Roman"><SPAN STYLE=3D'font-size:12=
pt'> <BR>
</SPAN></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'=
font-size:11pt'><BR>
Hi Teemu,<BR>
<BR>
Thanks for your feedback.<BR>
<BR>
On-demand approaches: we had a good discussion already on the matter, and I=
 have revised the ID based on that discussion. Yes, there are no handsets do=
ing this, but we left it open for laptops which may do this. If this is not =
a possibility at all, it would remain as an option; at this stage, I am not =
sure if we should say it is Not an option at all..<BR>
<BR>
DHCPv4 on cellular handsets: again, the statement is not implying that they=
 will surely implement DHCPv4. May be you can see what&#8217;s coming in the=
 future better than I do, but I am going with the option that already exists=
 in 3GPP standards &#8211; PCO to defer address allocation and then using DH=
CPv4. Again, this may never be done, but it&#8217;s premature to say it <I>w=
ill</I> never be done. Besides, consider the handsets accessing the EPC via =
WiFi interface, and not the cellular interface. Would you say that handsets =
will not do DHCPv4 over WiFi as well?<BR>
<BR>
Yes, there are additional considerations, and the ID is not making any reco=
mmendations to use on-demand/DHCPv4.As you point out, the ID is only pointin=
g out that carriers may consider investigating the on-demand addressing.<BR>
(BTW, on-demand PDN is subject to session inactivity timers, and is not the=
 same as on-demand IPv4 addressing).<BR>
<BR>
3G always-on: okay, I will add some clarifying text.<BR>
<BR>
Regards,<BR>
<BR>
-Rajeev<BR>
<BR>
<BR>
On 10/21/10 5:01 AM, &quot;<a href=3D"teemu.savolainen@nokia.com">teemu.savol=
ainen@nokia.com</a>&quot; &lt;<a href=3D"teemu.savolainen@nokia.com">teemu.sav=
olainen@nokia.com</a>&gt; wrote:<BR>
<FONT COLOR=3D"#1F497D">Hi,<BR>
&nbsp;<BR>
Section 3.1: it is true that IPv4 PDN on-demand and deferred IPv4 address a=
llocations are &#8220;approaches&#8221; in theory, but I do not believe thei=
r applicability in practice. E.g. what is the likelyhood that popular deskto=
p OSes would suddenly implement that kind of features (isn&#8217;t the style=
 usually ask DHCPv4 right at interface up and then renew forever)?<BR>
&nbsp;<BR>
Section 3.1: I do not believe cellular handsets will implement DHCPv4 for c=
ellular interfaces. Hence I disagree with:&#8221;this may very well change i=
n the future release&#8221;. Cellular handsets have managed without DHCPv4 s=
ince the dawn of packet switched cellular networks. Why on earth they would =
now start to use DHCPv4 on cellular access at the very twilight of IPv4? <BR=
>
&nbsp;<BR>
The &#8220;additional considerations&#8221; is huge, like there is no benef=
it whatsoever for hosts to do IPv4 on-demand or deferred IPv4 address alloca=
tion. Also it is non-trivial, like whether DHCPv4 should be triggered if app=
lication binds socket to 127.0.0.1..<BR>
&nbsp;<BR>
I also slightly disagree with this:&#8221; On the other hand, in the existi=
ng 3G UMTS networks, there is no requirement for an always-on connection&#82=
21;. While there is no such requirement from standards bodies, essentially f=
or many devices there is from the end user direction: users want to have IM/=
Skype/email always on. Should be clarified.<BR>
&nbsp;<BR>
I seem to agree with the conclusions document draws at the end of section 3=
.1 (there is nothing wrong in doing investigations of on-demand PDN..</FONT>=
</SPAN></FONT><SPAN STYLE=3D'font-size:11pt'><FONT COLOR=3D"#1F497D"><FONT FACE=3D=
"Wingdings">J<BR>
</FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><BR>
Best regards,<BR>
&nbsp;<BR>
Teemu<BR>
&nbsp;<BR>
</FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><BR>
</FONT></SPAN><FONT SIZE=3D"2"><FONT FACE=3D"Tahoma, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:10pt'><B>From:</B> <a href=3D"v6ops-bounces@ietf.org">=
v6ops-bounces@ietf.org</a> [<a href=3D"mailto:v6ops-bounces@ietf.org">mailto:v=
6ops-bounces@ietf.org</a>] <B>On Behalf Of </B>ext Fred Baker<BR>
<B>Sent:</B> 10. lokakuuta 2010 21:00<BR>
<B>To:</B> IPv6 Operations<BR>
<B>Cc:</B> <a href=3D"v6ops-chairs@tools.ietf.org">v6ops-chairs@tools.ietf.or=
g</a>; Ron Bonica<BR>
<B>Subject:</B> [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Times New Roman"><SPAN STYLE=3D'font-size:12=
pt'><BR>
</SPAN></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'=
font-size:11pt'><BR>
</SPAN></FONT><FONT SIZE=3D"1"><FONT FACE=3D"Helvetica, Verdana, Arial"><SPAN S=
TYLE=3D'font-size:9pt'>This is to initiate a two week working group last call =
of draft-ietf-v6ops-v6-in-mobile-networks. Please read it now. If you find n=
its (spelling errors, minor suggested wording changes, etc), comment to the =
authors; if you find greater issues, such as disagreeing with a statement or=
 finding additional issues that need to be addressed, please post your comme=
nts to the list.<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN =
STYLE=3D'font-size:11pt'><BR>
</SPAN></FONT><FONT SIZE=3D"1"><FONT FACE=3D"Helvetica, Verdana, Arial"><SPAN S=
TYLE=3D'font-size:9pt'><BR>
</SPAN></FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN =
STYLE=3D'font-size:11pt'><BR>
</SPAN></FONT><FONT SIZE=3D"1"><FONT FACE=3D"Helvetica, Verdana, Arial"><SPAN S=
TYLE=3D'font-size:9pt'>We are looking specifically for comments on the importa=
nce of the document as well as its content. If you have read the document an=
d believe it to be of operational utility, that is also an important comment=
 to make.
</SPAN></FONT></FONT>
<P ALIGN=3DCENTER>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:11pt=
'><HR ALIGN=3DCENTER SIZE=3D"3" WIDTH=3D"95%"></SPAN></FONT>
<P>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:11pt=
'><BR>
</SPAN></FONT><FONT SIZE=3D"2"><FONT FACE=3D"Consolas, Courier New, Courier"><S=
PAN STYLE=3D'font-size:10pt'>_______________________________________________<B=
R>
v6ops mailing list<BR>
<a href=3D"v6ops@ietf.org">v6ops@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops">https://www.ietf.org/=
mailman/listinfo/v6ops</a><BR>
</SPAN></FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN =
STYLE=3D'font-size:11pt'><BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--B_3370843464_11845358--


From Bill.Armstrong@chartercom.com  Mon Oct 25 09:30:09 2010
Return-Path: <Bill.Armstrong@chartercom.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 113013A68CC for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 09:30:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.819
X-Spam-Level: 
X-Spam-Status: No, score=-1.819 tagged_above=-999 required=5 tests=[AWL=0.180,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kq1MvIk+ihJx for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 09:30:07 -0700 (PDT)
Received: from mail.chartercom.com (mail.chartercom.com [24.217.29.16]) by core3.amsl.com (Postfix) with ESMTP id 1A3CE3A6ACB for <v6ops@ietf.org>; Mon, 25 Oct 2010 09:30:06 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.58,236,1286168400"; d="scan'208";a="123841204"
Received: from unknown (HELO KSTLMEXHTP02.CORP.CHARTERCOM.COM) ([192.168.31.32]) by mail.chartercom.com with ESMTP; 25 Oct 2010 11:31:51 -0500
Received: from KSTLMEXCP02MBX.CORP.CHARTERCOM.COM ([192.168.31.13]) by KSTLMEXHTP02.CORP.CHARTERCOM.COM ([192.168.31.32]) with mapi; Mon, 25 Oct 2010 11:31:51 -0500
From: "Armstrong, Bill R" <Bill.Armstrong@chartercom.com>
To: Fred Baker <fred@cisco.com>, IPv6 Operations <v6ops@ietf.org>
Date: Mon, 25 Oct 2010 11:31:49 -0500
Thread-Topic: [v6ops] draft-ietf-v6ops-3177bis-end-sites WGLC
Thread-Index: ActzpW1WdfFggL3oS62vnG8gAH0hBQAvHtoA
Message-ID: <E71300B9B9041340B238540990BF04530916154D6D@KSTLMEXCP02MBX.CORP.CHARTERCOM.COM>
References: <174BC871-6568-4569-B4E4-3ADDEB0C565C@cisco.com>
In-Reply-To: <174BC871-6568-4569-B4E4-3ADDEB0C565C@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: "v6ops-chairs@tools.ietf.org" <v6ops-chairs@tools.ietf.org>, Ron Bonica <ron@bonica.org>
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 16:30:09 -0000

Support.


-Bill


-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of F=
red Baker
Sent: Sunday, October 24, 2010 1:01 PM
To: IPv6 Operations
Cc: v6ops-chairs@tools.ietf.org; Ron Bonica
Subject: [v6ops] draft-ietf-v6ops-3177bis-end-sites WGLC

This is to initiate a two week working group last call of draft-ietf-v6ops-=
3177bis-end-sites. Please read it now. If you find nits (spelling errors, m=
inor suggested wording changes, etc), comment to the authors; if you find g=
reater issues, such as disagreeing with a statement or finding additional i=
ssues that need to be addressed, please post your comments to the list.

We are looking specifically for comments on the importance of the document =
as well as its content. If you have read the document and believe it to be =
of operational utility, that is also an important comment to make.=20
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

E-MAIL CONFIDENTIALITY NOTICE:=20

=20

=20

=20

The contents of this e-mail message and=20
any attachments are intended solely for the=20
addressee(s) and may contain confidential=20
and/or legally privileged information. If you=20
are not the intended recipient of this message=20
or if this message has been addressed to you=20
in error, please immediately alert the sender
 by reply e-mail and then delete this message=20
and any attachments. If you are not the=20
intended recipient, you are notified that=20
any use, dissemination, distribution, copying,=20
or storage of this message or any attachment=20
is strictly prohibited.









From rja.lists@gmail.com  Mon Oct 25 10:52:09 2010
Return-Path: <rja.lists@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B5063A6919 for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 10:52:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.348
X-Spam-Level: 
X-Spam-Status: No, score=-2.348 tagged_above=-999 required=5 tests=[AWL=0.251,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l14PV6pNvcGH for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 10:52:08 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id F1E913A68D2 for <v6ops@ietf.org>; Mon, 25 Oct 2010 10:52:07 -0700 (PDT)
Received: by qyk5 with SMTP id 5so1759809qyk.10 for <v6ops@ietf.org>; Mon, 25 Oct 2010 10:53:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:content-type :content-transfer-encoding:subject:date:message-id:to:mime-version :x-mailer; bh=LzmTTnPKkPa5diuEs+EiySQPlc4DseDFDIRNrRp7eHc=; b=A/Y1/3CGmeZ98l5dBMhI7xMVYV15ILOUgQYUNsDJwSkfxwlNnF9AicPf1u1Kp8NNXt YMjKY8tb50t3yE6RxmYe7eqPM3pvHjSFUBw8X/u6/Rc+xK8GDHEuUKX1xTy6wc/I57FS 8vHZaqKKbj2wxRYzsWYxMUVYQWIEnXrGgy1Sw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=nN1SIRnemTeGUVKsc9+hKqjFDLHZRNH4RE8EaP5s6anfKtl0L9l0goInI7A834IBJG ZbhQxlmtuFZUxVtmDvoATYQCvzGI4Rk2KWP24URaH21DexBk9H3etJa3tDYe6uKe9zuX zl46xvroCa6mSV+IiDYJuzXkgWYgXkom3cwWE=
Received: by 10.229.225.130 with SMTP id is2mr6176956qcb.263.1288029232906; Mon, 25 Oct 2010 10:53:52 -0700 (PDT)
Received: from [10.30.20.5] (pool-96-225-170-25.nrflva.fios.verizon.net [96.225.170.25]) by mx.google.com with ESMTPS id t17sm6306046qcp.14.2010.10.25.10.53.51 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 25 Oct 2010 10:53:52 -0700 (PDT)
From: RJ Atkinson <rja.lists@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Mon, 25 Oct 2010 13:53:50 -0400
Message-Id: <49F119D8-F6D4-4873-A177-4EE911BD268E@gmail.com>
To: v6ops@ietf.org
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Subject: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 17:52:09 -0000

Section 4:
----------

This section seems incomplete in that it does not clearly indicate
that assignment of routing prefixes longer than 64-bits would
violate existing (and several emerging) standards AND that use of=20
routing prefixes longer than 64-bits similarly likely would be=20
problematic.

	There are a number of active I-Ds headed towards publication
that assume the Routing Prefix is not longer than 64 bits.  It seems
very likely that at least one such I-D would be published, implemented,
and deployed.  =20

	Further, there is an IAB statement on the desirability of
retaining the 64-bit size for the IPv6 Interface ID:
	=
<http://www.iab.org/appeals/kre-ipng-address-arch-draft-standard-response.=
html>

	Last, and perhaps most compelling, RFC-4291, Section 2.5.4
explicitly states that Global Unicast IPv6 addresses (that aren't
IPv4-compatible/mapped addresses) have a 64-bit Interface ID field.

At least the IAB statement above and RFC-4291 ought to be cited,
and there should be text in this I-D about the requirement that
unicast routing prefixes not be longer than 64-bits.  That
requirement should be repeated in the summary.

While some might consider this obvious, it is sensible=20
to repeat this requirement, especially since that the I-D=20
already has Section 4 titled  "Impact on IPv6 Standards"



Section 5:=20
-----------

This text in Section 5 can be read in several different ways.
It ought to be edited for clarity.

>       - assigning a longer prefix to an end site, compared with the
>         existing prefixes the end site already has assigned to it, is
>         likely to increase operational costs and complexity for the =
end
>         site, with insufficient benefit to anyone.

I'm not crystal clear what meaning is intended.
One possible rephrasing of that might be:

	 - If a site already has existing IPv6 routing prefixes assigned =
to it,
           then it is likely to increase operational costs and =
complexity for
	   that site, with insufficient benefit to anyone, if a new IPv6 =
routing
	   prefix with a longer prefix-length is assigned to that site.

If the above is the intended meaning, I'd submit the version
above is more easily read and would eliminate ambiguity.


Also in Section 5:
------------------

If the DFZ RIB/FIB sizes for IPv6 grow at the geometric (exponential ?)
rates seen for IPv4, this creates BGP-related operational complexity.
It also tends to drive up capital costs for operators.

So it seems to me that there ought also to be some mention of the =
operational=20
issues created if either the size of the inter-domain routing table =
becomes=20
unduly large or and the growth rate of the inter-domain routing table =
becomes=20
unduly fast.  Someone other than me can probably phrase this concern =
more
clearly. =20

A citation of the IAB RAWS workshop report might also be relevant=20
if such text is added.

Yours,

Ran


From sthaug@nethelp.no  Mon Oct 25 11:24:15 2010
Return-Path: <sthaug@nethelp.no>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A0153A682F for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 11:24:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.378
X-Spam-Level: 
X-Spam-Status: No, score=-2.378 tagged_above=-999 required=5 tests=[AWL=0.221,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id awiKGW-SA48S for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 11:24:14 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by core3.amsl.com (Postfix) with SMTP id BED593A6867 for <v6ops@ietf.org>; Mon, 25 Oct 2010 11:24:13 -0700 (PDT)
Received: (qmail 2631 invoked from network); 25 Oct 2010 18:25:57 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 25 Oct 2010 18:25:57 -0000
Date: Mon, 25 Oct 2010 20:25:57 +0200 (CEST)
Message-Id: <20101025.202557.74664409.sthaug@nethelp.no>
To: rja.lists@gmail.com
From: sthaug@nethelp.no
In-Reply-To: <49F119D8-F6D4-4873-A177-4EE911BD268E@gmail.com>
References: <49F119D8-F6D4-4873-A177-4EE911BD268E@gmail.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: v6ops@ietf.org
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 18:24:15 -0000

> 	There are a number of active I-Ds headed towards publication
> that assume the Routing Prefix is not longer than 64 bits.  It seems
> very likely that at least one such I-D would be published, implemented,
> and deployed.   

That may be so - however, prefixes longer than 64 bits are in active
use today, and I see no sign of such use stopping any time soon.

> At least the IAB statement above and RFC-4291 ought to be cited,
> and there should be text in this I-D about the requirement that
> unicast routing prefixes not be longer than 64-bits.  That
> requirement should be repeated in the summary.

Do you think this is likely to stop people from using prefixes longer
than 64 bits?

Steinar Haug, Nethelp consulting, sthaug@nethelp.no

From randy@psg.com  Mon Oct 25 11:49:22 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 126DA3A693F for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 11:49:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.559
X-Spam-Level: 
X-Spam-Status: No, score=-2.559 tagged_above=-999 required=5 tests=[AWL=0.040,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JBazc5zL1ucl for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 11:49:21 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id C87FD3A66B4 for <v6ops@ietf.org>; Mon, 25 Oct 2010 11:49:20 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1PAS8P-0008HP-Iw; Mon, 25 Oct 2010 18:51:05 +0000
Date: Mon, 25 Oct 2010 11:51:05 -0700
Message-ID: <m2zku214yu.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <49F119D8-F6D4-4873-A177-4EE911BD268E@gmail.com>
References: <49F119D8-F6D4-4873-A177-4EE911BD268E@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: v6ops@ietf.org
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 18:49:22 -0000

> This section seems incomplete in that it does not clearly indicate
> that assignment of routing prefixes longer than 64-bits would violate
> existing (and several emerging) standards AND that use of routing
> prefixes longer than 64-bits similarly likely would be problematic.

they darn well better had not be

96 more bits, no magic.  please no magic.

randy

From rja.lists@gmail.com  Mon Oct 25 12:32:12 2010
Return-Path: <rja.lists@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5CF983A6809 for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 12:32:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.36
X-Spam-Level: 
X-Spam-Status: No, score=-2.36 tagged_above=-999 required=5 tests=[AWL=0.239,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N5yQZdD6AQ8C for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 12:32:01 -0700 (PDT)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id 878063A6AC4 for <v6ops@ietf.org>; Mon, 25 Oct 2010 12:31:48 -0700 (PDT)
Received: by pwi6 with SMTP id 6so688120pwi.31 for <v6ops@ietf.org>; Mon, 25 Oct 2010 12:33:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:content-type:mime-version :subject:from:in-reply-to:date:content-transfer-encoding:message-id :references:to:x-mailer; bh=f+3Fj5O7bDfaMIY60gQlD2LgxATVjHLQT/fUve4X/qQ=; b=MPHcQ8iZ8ESA3CM7u5xvngHPDufs8RUI6R+N7Kk1QG+R3Z+0chE3uM8BzYeguRCirh gSI7CGUNuaKUDeDb7DtriVrv2I7XCjQrf8xIhwsBPoIK9QYQP/5KiCTrp1qD3SSne6Mq +r+asqGcxDxthV3nyk41zquF7mlsAgnIPK9Lw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=NmMlEuTpje8gqWKx9pFTqUijXeh/SnjUouyG15woh6btDDDPKfYZIIDf0kw3xmKZ0e 9QvzP93ViBhumuARfYOstvIRTej5ZYg/uQa9GEM7wn+CWYJJJqCanTH470o6urgasNQL mYHxe76UIwoiSN2LBksPhmhyDGZFqPO8ratEc=
Received: by 10.142.186.4 with SMTP id j4mr5346740wff.285.1288035206880; Mon, 25 Oct 2010 12:33:26 -0700 (PDT)
Received: from [10.30.20.5] (pool-96-225-170-25.nrflva.fios.verizon.net [96.225.170.25]) by mx.google.com with ESMTPS id c40sm1742128vcs.25.2010.10.25.12.33.25 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 25 Oct 2010 12:33:25 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <20101025.202557.74664409.sthaug@nethelp.no>
Date: Mon, 25 Oct 2010 15:33:23 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <EB708A3F-3D63-4B29-8F5A-8AA69681B544@gmail.com>
References: <49F119D8-F6D4-4873-A177-4EE911BD268E@gmail.com> <20101025.202557.74664409.sthaug@nethelp.no>
To: v6ops@ietf.org
X-Mailer: Apple Mail (2.1081)
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 19:32:12 -0000

On 25  Oct 2010, at 14:25 , sthaug@nethelp.no wrote:
> Do you think this is likely to stop people
> from using prefixes longer than 64 bits?


BOTTOM LINE:

It ought to reduce the chance that RIRs and ISPs/LIRs
will delegate prefixes longer than 64 bits to sites.  
That outcome would be very helpful to the recipients 
of such delegated prefixes.

ANALYSIS:

One might wish that RFC-4291, RFC-3513, RFC-2373, and 
other IETF documents covering the IPv6 protocol did not 
specify 64-bits for the Interface ID, but that part of 
the IPv6 specs is now over a decade old -- and widely
implemented in various OSs and (within the IPv6 universe)
also widely deployed.

To quote from RFC-3513, Section 2.5.1, a mere 7 years ago
(& the same text appears in the same section of RFC-4291):

	For all unicast addresses, except those that start 
	with binary value 000, Interface IDs are required 
	to be 64 bits long and to be constructed in Modified 
	EUI-64 format.

There is also operational experience that routing prefixes
longer than 64 bits are problematic in at least some current
IPv6 deployments.  One might wish that were not the case,
but I know of several deployments that have already been
bitten by this.[1]

It would be quite exceptional for an IETF WG to publish
an advice document that discusses some standards issues,
but ignores other standards issues that are also relevant.

Best wishes,

Ran
rja.lists@gmail.com

[1] Configuring a very long prefix on forming the IP address 
on a point-to-point link between 2 routers seems to work OK, 
according to those reports, provided one doesn't try to advertise 
those very long prefixes in an IPv6-capable routing protocol.


From rja.lists@gmail.com  Mon Oct 25 12:34:39 2010
Return-Path: <rja.lists@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B512E3A68E2 for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 12:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.371
X-Spam-Level: 
X-Spam-Status: No, score=-2.371 tagged_above=-999 required=5 tests=[AWL=0.228,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YYVAS+MaRF6X for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 12:34:32 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id AFB393A68DE for <v6ops@ietf.org>; Mon, 25 Oct 2010 12:34:31 -0700 (PDT)
Received: by qwb7 with SMTP id 7so1696964qwb.31 for <v6ops@ietf.org>; Mon, 25 Oct 2010 12:36:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:content-type:mime-version :subject:from:in-reply-to:date:content-transfer-encoding:message-id :references:to:x-mailer; bh=Xgb/31RCri9HEy8TgJuM7Iq+CpLMduvCnaGRMVGD/Gk=; b=ur39pOtl83SPpO3ECO+DfXDJh0mQJnj9cbxvmxsZ3U26auDkac8QEkpfnST/91d7v5 /BYM2I/GjRVLNxx9cEowMVKsYlT1fkdABa4E0wLoV2T25jQquP0qefN7oWy5IkMc8jIc t7nm8AKkAtTX8zP0YG0KCJvp+8ByhV0WM0XkI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=OI2ATk5lSfLVUiHEq16kYonAGcDx4k0scIc4jk3LtC97Olq3TM65UAyTrXV2CCc8uL oAeSVFrMZiAubhqROAVMlcTYPdfKPiMIx/28mv9+Vxd4PQv43fMmUQk2HnfKCU3MA/rg hJXoIjJ04HczClbim211jgC/Q5SZmDE85YAL0=
Received: by 10.224.199.9 with SMTP id eq9mr582952qab.47.1288035377049; Mon, 25 Oct 2010 12:36:17 -0700 (PDT)
Received: from [10.30.20.5] (pool-96-225-170-25.nrflva.fios.verizon.net [96.225.170.25]) by mx.google.com with ESMTPS id m7sm6399202qck.1.2010.10.25.12.36.15 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 25 Oct 2010 12:36:16 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <m2zku214yu.wl%randy@psg.com>
Date: Mon, 25 Oct 2010 15:36:14 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <9A7160F0-D026-49A9-95E9-474BDE070F9C@gmail.com>
References: <49F119D8-F6D4-4873-A177-4EE911BD268E@gmail.com> <m2zku214yu.wl%randy@psg.com>
To: v6ops@ietf.org
X-Mailer: Apple Mail (2.1081)
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 19:34:39 -0000

On 25  Oct 2010, at 14:51 , Randy Bush wrote:
>> This section seems incomplete in that it does not clearly indicate
>> that assignment of routing prefixes longer than 64-bits would violate
>> existing (and several emerging) standards AND that use of routing
>> prefixes longer than 64-bits similarly likely would be problematic.
> 
> they darn well better had not be

Several network operators have already discovered that
delegating prefixes longer than 64-bits is operationally
problematic.

> 96 more bits, no magic.  please no magic.

Over a decade too late.  

Cheers,

Ran


From gert@space.net  Mon Oct 25 12:42:05 2010
Return-Path: <gert@space.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 722BB3A68C1 for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 12:42:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.508
X-Spam-Level: 
X-Spam-Status: No, score=-2.508 tagged_above=-999 required=5 tests=[AWL=0.091,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qaYqgw5IsenP for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 12:42:04 -0700 (PDT)
Received: from mobil.space.net (mobil.Space.Net [IPv6:2001:608:2:81::2]) by core3.amsl.com (Postfix) with ESMTP id 68FFF3A682B for <v6ops@ietf.org>; Mon, 25 Oct 2010 12:42:03 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id B1CF0F80DE for <v6ops@ietf.org>; Mon, 25 Oct 2010 21:43:47 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 8730DF80F9 for <v6ops@ietf.org>; Mon, 25 Oct 2010 21:43:47 +0200 (CEST)
Received: (qmail 44160 invoked by uid 1007); 25 Oct 2010 21:43:47 +0200
Date: Mon, 25 Oct 2010 21:43:47 +0200
From: Gert Doering <gert@space.net>
To: RJ Atkinson <rja.lists@gmail.com>
Message-ID: <20101025194347.GA32268@Space.Net>
References: <49F119D8-F6D4-4873-A177-4EE911BD268E@gmail.com> <20101025.202557.74664409.sthaug@nethelp.no> <EB708A3F-3D63-4B29-8F5A-8AA69681B544@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <EB708A3F-3D63-4B29-8F5A-8AA69681B544@gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: v6ops@ietf.org
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 19:42:05 -0000

Hi,

On Mon, Oct 25, 2010 at 03:33:23PM -0400, RJ Atkinson wrote:
> [1] Configuring a very long prefix on forming the IP address 
> on a point-to-point link between 2 routers seems to work OK, 
> according to those reports, provided one doesn't try to advertise 
> those very long prefixes in an IPv6-capable routing protocol.

OSPFv3 and BGP seem to handle /128 prefixes just fine over here.

Which routing protocol would that be, that one having problems?

Would that be a problem of the *protocol* or just one specific vendor
implementation?

Gert Doering
        -- NetMaster
-- 
did you enable IPv6 on something today...?

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

From sthaug@nethelp.no  Mon Oct 25 12:58:51 2010
Return-Path: <sthaug@nethelp.no>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A47F33A693F for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 12:58:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.384
X-Spam-Level: 
X-Spam-Status: No, score=-2.384 tagged_above=-999 required=5 tests=[AWL=0.215,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id haQU2n9rAxo2 for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 12:58:50 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by core3.amsl.com (Postfix) with SMTP id 1BD753A68E5 for <v6ops@ietf.org>; Mon, 25 Oct 2010 12:58:49 -0700 (PDT)
Received: (qmail 14298 invoked from network); 25 Oct 2010 20:00:32 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 25 Oct 2010 20:00:32 -0000
Date: Mon, 25 Oct 2010 22:00:32 +0200 (CEST)
Message-Id: <20101025.220032.41712705.sthaug@nethelp.no>
To: gert@space.net
From: sthaug@nethelp.no
In-Reply-To: <20101025194347.GA32268@Space.Net>
References: <20101025.202557.74664409.sthaug@nethelp.no> <EB708A3F-3D63-4B29-8F5A-8AA69681B544@gmail.com> <20101025194347.GA32268@Space.Net>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: v6ops@ietf.org
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 19:58:51 -0000

> > [1] Configuring a very long prefix on forming the IP address 
> > on a point-to-point link between 2 routers seems to work OK, 
> > according to those reports, provided one doesn't try to advertise 
> > those very long prefixes in an IPv6-capable routing protocol.
> 
> OSPFv3 and BGP seem to handle /128 prefixes just fine over here.
> 
> Which routing protocol would that be, that one having problems?
> 
> Would that be a problem of the *protocol* or just one specific vendor
> implementation?

That's what I suspect. We're running IPv6 on Cisco and Juniper gear
here, with /64s, /126s, /127s, /128s and some other prefix lengths,
in IS-IS and BGP. It all works, no problems observed.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no

From sthaug@nethelp.no  Mon Oct 25 12:59:57 2010
Return-Path: <sthaug@nethelp.no>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4B53E3A6940 for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 12:59:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.39
X-Spam-Level: 
X-Spam-Status: No, score=-2.39 tagged_above=-999 required=5 tests=[AWL=0.209,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2lR0W+A1LkiX for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 12:59:56 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by core3.amsl.com (Postfix) with SMTP id 513A73A68BB for <v6ops@ietf.org>; Mon, 25 Oct 2010 12:59:55 -0700 (PDT)
Received: (qmail 14525 invoked from network); 25 Oct 2010 20:01:40 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 25 Oct 2010 20:01:40 -0000
Date: Mon, 25 Oct 2010 22:01:40 +0200 (CEST)
Message-Id: <20101025.220140.71173872.sthaug@nethelp.no>
To: rja.lists@gmail.com
From: sthaug@nethelp.no
In-Reply-To: <9A7160F0-D026-49A9-95E9-474BDE070F9C@gmail.com>
References: <49F119D8-F6D4-4873-A177-4EE911BD268E@gmail.com> <m2zku214yu.wl%randy@psg.com> <9A7160F0-D026-49A9-95E9-474BDE070F9C@gmail.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: v6ops@ietf.org
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 19:59:57 -0000

> Several network operators have already discovered that
> delegating prefixes longer than 64-bits is operationally
> problematic.
> 
> > 96 more bits, no magic.  please no magic.
> 
> Over a decade too late.  

I would claim that trying to legislate prefixes being 64 bits or
shorter only, is over a decade too late.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no

From ot@cisco.com  Mon Oct 25 13:01:53 2010
Return-Path: <ot@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD2173A6A08 for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 13:01:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.591
X-Spam-Level: 
X-Spam-Status: No, score=-8.591 tagged_above=-999 required=5 tests=[AWL=2.008,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7oY-Y8nQxrMh for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 13:01:52 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 7744E3A6B0C for <v6ops@ietf.org>; Mon, 25 Oct 2010 13:01:52 -0700 (PDT)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AokEABd/xUyQ/khMgWdsb2JhbAChTxUBARYiIqFpnFeFSASKTQ
X-IronPort-AV: E=Sophos;i="4.58,237,1286150400"; d="scan'208";a="67511505"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 25 Oct 2010 20:03:37 +0000
Received: from dhcp-10-55-85-159.cisco.com (dhcp-10-55-85-159.cisco.com [10.55.85.159]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id o9PK3bkQ012503; Mon, 25 Oct 2010 20:03:37 GMT
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <ot@cisco.com>
In-Reply-To: <20101025194347.GA32268@Space.Net>
Date: Mon, 25 Oct 2010 22:03:36 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6265A25E-D35A-4678-B84C-499913488859@cisco.com>
References: <49F119D8-F6D4-4873-A177-4EE911BD268E@gmail.com> <20101025.202557.74664409.sthaug@nethelp.no> <EB708A3F-3D63-4B29-8F5A-8AA69681B544@gmail.com> <20101025194347.GA32268@Space.Net>
To: Gert Doering <gert@space.net>
X-Mailer: Apple Mail (2.1081)
Cc: v6ops@ietf.org, RJ Atkinson <rja.lists@gmail.com>
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 20:01:53 -0000

>> [1] Configuring a very long prefix on forming the IP address=20
>> on a point-to-point link between 2 routers seems to work OK,=20
>> according to those reports, provided one doesn't try to advertise=20
>> those very long prefixes in an IPv6-capable routing protocol.
>=20
> OSPFv3 and BGP seem to handle /128 prefixes just fine over here.
>=20
> Which routing protocol would that be, that one having problems?
>=20
> Would that be a problem of the *protocol* or just one specific vendor
> implementation?

this document is about IPv6 address assignment to end sites.
a prefix longer than /64 would generally not work.
even a single /64 in "general deployments" is problematic (e.g. an IPv6 =
CE router can take a /64 for it's own internal interfaces), leaving =
nothing for LAN side interfaces.

I think the IETF should make a general recommendation leading to =
deployments where end sites are not forced to implement IPv6 NATs.=20

cheers,
Ole=

From tony@lava.net  Mon Oct 25 13:13:30 2010
Return-Path: <tony@lava.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D6C323A6B30 for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 13:13:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.229
X-Spam-Level: 
X-Spam-Status: No, score=-2.229 tagged_above=-999 required=5 tests=[AWL=0.371,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gvmy86QT5Y0Y for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 13:13:28 -0700 (PDT)
Received: from outgoing03.lava.net (outgoing03.lava.net [IPv6:2001:1888:0:1:202:b3ff:fe1d:6b98]) by core3.amsl.com (Postfix) with ESMTP id 564C73A6B31 for <v6ops@ietf.org>; Mon, 25 Oct 2010 13:13:24 -0700 (PDT)
Received: from [2001:1888::a:214:51ff:fe29:1e4e] (unknown [IPv6:2001:1888:0:a:214:51ff:fe29:1e4e]) by outgoing03.lava.net (Postfix) with ESMTPS id 14ABE101E6; Mon, 25 Oct 2010 10:15:09 -1000 (HST)
Date: Mon, 25 Oct 2010 10:15:08 -1000 (HST)
From: Antonio Querubin <tony@lava.net>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <174BC871-6568-4569-B4E4-3ADDEB0C565C@cisco.com>
Message-ID: <alpine.OSX.2.00.1010250934480.142@cust11794.lava.net>
References: <174BC871-6568-4569-B4E4-3ADDEB0C565C@cisco.com>
User-Agent: Alpine 2.00 (OSX 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 20:13:31 -0000

On Sun, 24 Oct 2010, Fred Baker wrote:

> This is to initiate a two week working group last call of 
> draft-ietf-v6ops-3177bis-end-sites. Please read it now. If you find nits

Support.

> document as well as its content. If you have read the document and 
> believe it to be of operational utility, that is also an important 
> comment to make.

Probably most helpful for the ops folks still new to IPv6 and still trying 
to figure out their assignment schemes.  The recurring debates over 
assignment sizes in the ops community will probably continue but perhaps 
this clarification might reduce some of the jabs directed at the IETF :)

Antonio Querubin
808-545-5282 x3003
e-mail/xmpp:  tony@lava.net

From fred@cisco.com  Mon Oct 25 13:25:55 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 01C1C3A6B6A for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 13:25:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.346
X-Spam-Level: 
X-Spam-Status: No, score=-110.346 tagged_above=-999 required=5 tests=[AWL=0.253, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wzUL1LMWiX4F for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 13:25:54 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id A86A13A6B30 for <v6ops@ietf.org>; Mon, 25 Oct 2010 13:25:53 -0700 (PDT)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.58,237,1286150400"; d="scan'208";a="275423335"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-5.cisco.com with ESMTP; 25 Oct 2010 20:27:39 +0000
Received: from stealth-10-32-244-222.cisco.com (stealth-10-32-244-222.cisco.com [10.32.244.222]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o9PKQiFg008063; Mon, 25 Oct 2010 20:27:34 GMT
Received: from [127.0.0.1] by stealth-10-32-244-222.cisco.com (PGP Universal service); Mon, 25 Oct 2010 13:27:39 -0700
X-PGP-Universal: processed; by stealth-10-32-244-222.cisco.com on Mon, 25 Oct 2010 13:27:39 -0700
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <6265A25E-D35A-4678-B84C-499913488859@cisco.com>
Date: Mon, 25 Oct 2010 13:27:33 -0700
Message-Id: <0CBE9709-6BBA-4A9C-B996-54F0229B429C@cisco.com>
References: <49F119D8-F6D4-4873-A177-4EE911BD268E@gmail.com> <20101025.202557.74664409.sthaug@nethelp.no> <EB708A3F-3D63-4B29-8F5A-8AA69681B544@gmail.com> <20101025194347.GA32268@Space.Net> <6265A25E-D35A-4678-B84C-499913488859@cisco.com>
To: Ole Troan <ot@cisco.com>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: v6ops@ietf.org, RJ Atkinson <rja.lists@gmail.com>
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 20:25:55 -0000

On Oct 25, 2010, at 1:03 PM, Ole Troan wrote:

> I think the IETF should make a general recommendation leading to =
deployments where end sites are not forced to implement IPv6 NATs.=20

I'm all for that. The issue, of course, that is bringing discussion of =
NATs is not the traditional uses of NATs (address amplification, =
topology obfuscation, and prophylactic perimeter security, each of which =
is unnecessary given IPv6 or bogus on its face), but of scaling routing. =
As I said to someone else on another list we're both on not too long =
ago, "if you want to tell us how to scalably manage O(10^7) IPv6 PI =
prefixes without translation, without rearranging all of the operator's =
transit contracts (which would be one of the side-effects of Metro =
Addressing), and without aggregation, I guess I'm all ears." This is the =
flip side of the point that Tony, Marla, and Jason were making in the =
draft they discussed recently, and were very loudly told that the =
operational community was going to do what it was going to do, and that =
meant that multihoming means PI addressing.=

From sthaug@nethelp.no  Mon Oct 25 13:43:36 2010
Return-Path: <sthaug@nethelp.no>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC9BB3A6867 for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 13:43:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.396
X-Spam-Level: 
X-Spam-Status: No, score=-2.396 tagged_above=-999 required=5 tests=[AWL=0.203,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pzppnGEdjI+a for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 13:43:35 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by core3.amsl.com (Postfix) with SMTP id EFC9D3A63D3 for <v6ops@ietf.org>; Mon, 25 Oct 2010 13:43:34 -0700 (PDT)
Received: (qmail 20719 invoked from network); 25 Oct 2010 20:45:18 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 25 Oct 2010 20:45:18 -0000
Date: Mon, 25 Oct 2010 22:45:18 +0200 (CEST)
Message-Id: <20101025.224518.104116551.sthaug@nethelp.no>
To: rja.lists@gmail.com
From: sthaug@nethelp.no
In-Reply-To: <EB708A3F-3D63-4B29-8F5A-8AA69681B544@gmail.com>
References: <49F119D8-F6D4-4873-A177-4EE911BD268E@gmail.com> <20101025.202557.74664409.sthaug@nethelp.no> <EB708A3F-3D63-4B29-8F5A-8AA69681B544@gmail.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: v6ops@ietf.org
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 20:43:36 -0000

> > Do you think this is likely to stop people
> > from using prefixes longer than 64 bits?
> 
> 
> BOTTOM LINE:
> 
> It ought to reduce the chance that RIRs and ISPs/LIRs
> will delegate prefixes longer than 64 bits to sites.  
> That outcome would be very helpful to the recipients 
> of such delegated prefixes.

As of today, if I had a customer connecting to my network on a real
point-to-point link (SDH, serial, etc), I would assign a /127 prefix
for this link - and expect the customer use this prefix. I could be
convinced to assign a /64 but then I'd have to require the customer
to actually *use* a /127. This is because a /127 is (IMHO) the only
reasonable way of preventing a loop on such links.

In my mind there is a definite difference between assignment and use.
For my residential customers I would assign a /56 (using DHCP-PD). I'm
fine with an RFC saying that longer than /64 should not be assigned
to such customers. Trying to legislate against the *usage* of longer
than /64 is simply wrong - and many years too late.

> To quote from RFC-3513, Section 2.5.1, a mere 7 years ago
> (& the same text appears in the same section of RFC-4291):
> 
> 	For all unicast addresses, except those that start 
> 	with binary value 000, Interface IDs are required 
> 	to be 64 bits long and to be constructed in Modified 
> 	EUI-64 format.

That's fine. There is no *enforcement* of this paragraph unless you
really ask for it - which means that there are quite a few addresses 
in use out there which don't follow the modified EUI-64 format.

> There is also operational experience that routing prefixes
> longer than 64 bits are problematic in at least some current
> IPv6 deployments.  One might wish that were not the case,
> but I know of several deployments that have already been
> bitten by this.[1]

Since routing prefixes longer than 64 bits are in reasonably wide use,
I'd expect such implementations to be fixed, in order to survive.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no

From ipng@69706e6720323030352d30312d31340a.nosense.org  Mon Oct 25 13:57:19 2010
Return-Path: <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 526BF3A68C7 for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 13:57:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.474
X-Spam-Level: 
X-Spam-Status: No, score=-1.474 tagged_above=-999 required=5 tests=[AWL=0.421,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xopXZOBBIuOB for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 13:57:14 -0700 (PDT)
Received: from smtp1.adam.net.au (smtp1.adam.net.au [202.136.110.253]) by core3.amsl.com (Postfix) with ESMTP id E44DA3A68DC for <v6ops@ietf.org>; Mon, 25 Oct 2010 13:57:13 -0700 (PDT)
Received: from 182-239-171-173.ip.adam.com.au ([182.239.171.173] helo=opy.nosense.org) by smtp1.adam.net.au with esmtp (Exim 4.63) (envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>) id 1PAU88-0000oz-Vv; Tue, 26 Oct 2010 07:28:57 +1030
Received: from opy.nosense.org (localhost.localdomain [IPv6:::1]) by opy.nosense.org (Postfix) with ESMTP id 4757E3B31E; Tue, 26 Oct 2010 07:28:56 +1030 (CST)
Date: Tue, 26 Oct 2010 07:28:54 +1030
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: sthaug@nethelp.no
Message-ID: <20101026072854.1dab9fa1@opy.nosense.org>
In-Reply-To: <20101025.220140.71173872.sthaug@nethelp.no>
References: <49F119D8-F6D4-4873-A177-4EE911BD268E@gmail.com> <m2zku214yu.wl%randy@psg.com> <9A7160F0-D026-49A9-95E9-474BDE070F9C@gmail.com> <20101025.220140.71173872.sthaug@nethelp.no>
X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; x86_64-unknown-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: v6ops@ietf.org, rja.lists@gmail.com
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 20:57:19 -0000

On Mon, 25 Oct 2010 22:01:40 +0200 (CEST)
sthaug@nethelp.no wrote:

> > Several network operators have already discovered that
> > delegating prefixes longer than 64-bits is operationally
> > problematic.
> > 
> > > 96 more bits, no magic.  please no magic.
> > 
> > Over a decade too late.  
> 
> I would claim that trying to legislate prefixes being 64 bits or
> shorter only, is over a decade too late.
> 

So you don't consider published RFCs "legislation"?

I'm never comfortable with the approach of "it works so it must be
right". The only reason it is working might be just that you've been
lucky. Luck isn't reliable.* Things working by design are always going
to be more reliable than things that work by luck.


Regards,
Mark.


(* Apparently you can run a four stroke engine on two stroke fuel - I'm
not sure for how long - the guy who said he did it didn't say - but
since it is working, does that make it right? _Luckily_ he only did it
for a short time so he probably didn't damage anything.)

From teemu.savolainen@nokia.com  Mon Oct 25 13:58:59 2010
Return-Path: <teemu.savolainen@nokia.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 48D043A68DC for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 13:58:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.282
X-Spam-Level: 
X-Spam-Status: No, score=-6.282 tagged_above=-999 required=5 tests=[AWL=-0.284, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id syxQ-UL3FsJG for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 13:58:41 -0700 (PDT)
Received: from mgw-mx06.nokia.com (smtp.nokia.com [192.100.122.233]) by core3.amsl.com (Postfix) with ESMTP id 5C35D3A68E5 for <v6ops@ietf.org>; Mon, 25 Oct 2010 13:58:40 -0700 (PDT)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-mx06.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id o9PL07O7031371; Tue, 26 Oct 2010 00:00:10 +0300
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by vaebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 26 Oct 2010 00:00:03 +0300
Received: from vaebh101.NOE.Nokia.com ([10.160.244.22]) by vaebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 25 Oct 2010 23:59:58 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.5]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 25 Oct 2010 23:59:49 +0300
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-01.mgdnok.nokia.com ([65.54.30.5]) with mapi; Mon, 25 Oct 2010 22:59:48 +0200
From: <teemu.savolainen@nokia.com>
To: <rkoodli@cisco.com>, <fred@cisco.com>, <v6ops@ietf.org>
Date: Mon, 25 Oct 2010 22:59:46 +0200
Thread-Topic: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
Thread-Index: ActopRH/JoCme+MzQXiyJfFN4kSgHQIcAP9gACK/4tkAoGaQgAAP2Y+pAAgy+TA=
Message-ID: <18034D4D7FE9AE48BF19AB1B0EF2729F5F056DAAFC@NOK-EUMSG-01.mgdnok.nokia.com>
References: <18034D4D7FE9AE48BF19AB1B0EF2729F5F056DA6ED@NOK-EUMSG-01.mgdnok.nokia.com> <C8EAFD48.A335%rkoodli@cisco.com>
In-Reply-To: <C8EAFD48.A335%rkoodli@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_18034D4D7FE9AE48BF19AB1B0EF2729F5F056DAAFCNOKEUMSG01mgd_"
MIME-Version: 1.0
X-OriginalArrivalTime: 25 Oct 2010 20:59:49.0363 (UTC) FILETIME=[8FE33430:01CB7487]
X-Nokia-AV: Clean
Cc: v6ops-chairs@tools.ietf.org, ron@bonica.org
Subject: Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 20:58:59 -0000

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

Hi,

Remember the host-based vs. network-based mobility discussions?

I am essentially using the "network-based" camp's argumentation herein: mod=
ifying large host population (in time!) to support IPv4 on-demand (especial=
ly with DHCPv4) on cellular access is an infeasible approach and the dual-s=
tack using network should just implement some flavor of NAT instead.

Actually I think the reason is even stronger with the IPv4 on-demand. With =
DSMIP6 a host actually gains benefits (like mobility always and not just wi=
thin an administrative domain), but with IPv4 on-demand, or with DHCPv4 on =
cellular, the host gains nothing.

Best regards,

Teemu

P.S. We don't use iOS but you do network elements. Maybe you have packet ca=
ptures to share?

From: ext Rajeev Koodli [mailto:rkoodli@cisco.com]
Sent: 25. lokakuuta 2010 19:24
To: Savolainen Teemu (Nokia-MS/Tampere); Fred Baker; v6ops@ietf.org
Cc: v6ops-chairs@tools.ietf.org; ron@bonica.org
Subject: Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC


Teemu,

I am not sure how it is an issue to run DHCPv4 over WiFi and not use DHCPv4=
 over cellular.
AFAICT, iPhone seems to be doing it today; please correct me otherwise.

Thanks,

-Rajeev



On 10/25/10 1:57 AM, "teemu.savolainen@nokia.com" <teemu.savolainen@nokia.c=
om> wrote:
Rajeev,

I agree that anything may happen in the future:)

Hence IPv4 on-demand could happen, but I don't see it happening at the mome=
nt. Hence the draft should be clear that it is something that might be doab=
le, but not something is there out of the box just for network operator to =
activate.

DHCPv4: for WiFi DHCPv4 is used for sure, of course. But a handset that use=
s DHCPv4 for WiFi, but not for cellular (as it is point-to-point), needs mo=
difications. These modifications needs justification, IOP testing, and so f=
orth *for no benefit* for the handset. And of course not all handsets come =
with WiFi, but may come with dual-stack cellular. Justifying introduction o=
f a feature that does not bring benefits but requires effort (money) is oft=
entimes challenging - even if standard would allow. And AFAIK there is no r=
eally significant deployments of DHCPv4 on handsets over cellular that I wo=
uld be aware.

On-demand PDN connection and on-demand IPv4 addressing: I'm against for bot=
h. Tunneling like DS-Lite would be far easier (static private address, and =
then NAT bindings on-demand).

Best regards,

Teemu



From: ext Rajeev Koodli [mailto:rkoodli@cisco.com]
Sent: 22. lokakuuta 2010 07:18
To: Savolainen Teemu (Nokia-MS/Tampere); Fred Baker; v6ops@ietf.org
Cc: v6ops-chairs@tools.ietf.org; ron@bonica.org
Subject: Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC


Hi Teemu,

Thanks for your feedback.

On-demand approaches: we had a good discussion already on the matter, and I=
 have revised the ID based on that discussion. Yes, there are no handsets d=
oing this, but we left it open for laptops which may do this. If this is no=
t a possibility at all, it would remain as an option; at this stage, I am n=
ot sure if we should say it is Not an option at all..

DHCPv4 on cellular handsets: again, the statement is not implying that they=
 will surely implement DHCPv4. May be you can see what's coming in the futu=
re better than I do, but I am going with the option that already exists in =
3GPP standards - PCO to defer address allocation and then using DHCPv4. Aga=
in, this may never be done, but it's premature to say it will never be done=
. Besides, consider the handsets accessing the EPC via WiFi interface, and =
not the cellular interface. Would you say that handsets will not do DHCPv4 =
over WiFi as well?

Yes, there are additional considerations, and the ID is not making any reco=
mmendations to use on-demand/DHCPv4.As you point out, the ID is only pointi=
ng out that carriers may consider investigating the on-demand addressing.
(BTW, on-demand PDN is subject to session inactivity timers, and is not the=
 same as on-demand IPv4 addressing).

3G always-on: okay, I will add some clarifying text.

Regards,

-Rajeev


On 10/21/10 5:01 AM, "teemu.savolainen@nokia.com" <teemu.savolainen@nokia.c=
om> wrote:
Hi,

Section 3.1: it is true that IPv4 PDN on-demand and deferred IPv4 address a=
llocations are "approaches" in theory, but I do not believe their applicabi=
lity in practice. E.g. what is the likelyhood that popular desktop OSes wou=
ld suddenly implement that kind of features (isn't the style usually ask DH=
CPv4 right at interface up and then renew forever)?

Section 3.1: I do not believe cellular handsets will implement DHCPv4 for c=
ellular interfaces. Hence I disagree with:"this may very well change in the=
 future release". Cellular handsets have managed without DHCPv4 since the d=
awn of packet switched cellular networks. Why on earth they would now start=
 to use DHCPv4 on cellular access at the very twilight of IPv4?

The "additional considerations" is huge, like there is no benefit whatsoeve=
r for hosts to do IPv4 on-demand or deferred IPv4 address allocation. Also =
it is non-trivial, like whether DHCPv4 should be triggered if application b=
inds socket to 127.0.0.1..

I also slightly disagree with this:" On the other hand, in the existing 3G =
UMTS networks, there is no requirement for an always-on connection". While =
there is no such requirement from standards bodies, essentially for many de=
vices there is from the end user direction: users want to have IM/Skype/ema=
il always on. Should be clarified.

I seem to agree with the conclusions document draws at the end of section 3=
.1 (there is nothing wrong in doing investigations of on-demand PDN..:)

Best regards,

Teemu


From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of e=
xt Fred Baker
Sent: 10. lokakuuta 2010 21:00
To: IPv6 Operations
Cc: v6ops-chairs@tools.ietf.org; Ron Bonica
Subject: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC


This is to initiate a two week working group last call of draft-ietf-v6ops-=
v6-in-mobile-networks. Please read it now. If you find nits (spelling error=
s, minor suggested wording changes, etc), comment to the authors; if you fi=
nd greater issues, such as disagreeing with a statement or finding addition=
al issues that need to be addressed, please post your comments to the list.



We are looking specifically for comments on the importance of the document =
as well as its content. If you have read the document and believe it to be =
of operational utility, that is also an important comment to make.
________________________________

_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<title>Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC</title>
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
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:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=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:#1F497D'>Hi,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Remember the host-based vs. network-based mobility discussio=
ns?<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>I am essentially using the &#8220;network-based&#8221; camp&=
#8217;s
argumentation herein: modifying large host population (in time!) to support=
 IPv4
on-demand (especially with DHCPv4) on cellular access is an infeasible appr=
oach
and the dual-stack using network should just implement some flavor of NAT i=
nstead.
<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Actually I think the reason is even stronger with the IPv4
on-demand. With DSMIP6 a host actually gains benefits (like mobility always=
 and
not just within an administrative domain), but with IPv4 on-demand, or with
DHCPv4 on cellular, the host gains nothing. <o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Best regards,<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Teemu<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>P.S. We don&#8217;t use iOS but you do network elements. May=
be
you have packet captures to share?<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> ext Rajeev Ko=
odli
[mailto:rkoodli@cisco.com] <br>
<b>Sent:</b> 25. lokakuuta 2010 19:24<br>
<b>To:</b> Savolainen Teemu (Nokia-MS/Tampere); Fred Baker; v6ops@ietf.org<=
br>
<b>Cc:</b> v6ops-chairs@tools.ietf.org; ron@bonica.org<br>
<b>Subject:</b> Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC<o:p=
></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span style=3D'font-siz=
e:11.0pt;
font-family:"Calibri","sans-serif"'><br>
Teemu,<br>
<br>
I am not sure how it is an issue to run DHCPv4 over WiFi and not use DHCPv4
over cellular.<br>
AFAICT, iPhone seems to be doing it today; please correct me otherwise.<br>
<br>
Thanks,<br>
<br>
-Rajeev<br>
<br>
<br>
<br>
On 10/25/10 1:57 AM, &quot;<a href=3D"teemu.savolainen@nokia.com">teemu.sav=
olainen@nokia.com</a>&quot;
&lt;<a href=3D"teemu.savolainen@nokia.com">teemu.savolainen@nokia.com</a>&g=
t;
wrote:</span><o:p></o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Rajeev,<br>
&nbsp;<br>
I agree that anything may happen in the future</span><span style=3D'font-si=
ze:
11.0pt;font-family:Wingdings;color:#1F497D'>J</span><span style=3D'font-siz=
e:
11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> <br>
&nbsp;<br>
Hence IPv4 on-demand could happen, but I don&#8217;t see it happening at th=
e
moment. Hence the draft should be clear that it is something that might be
doable, but not something is there out of the box just for network operator=
 to
activate.<br>
&nbsp;<br>
DHCPv4: for WiFi DHCPv4 is used for sure, of course. But a handset that use=
s
DHCPv4 for WiFi, but not for cellular (as it is point-to-point), needs
modifications. These modifications needs justification, IOP testing, and so
forth *<b>for no benefit</b>* for the handset. And of course not all handse=
ts
come with WiFi, but may come with dual-stack cellular. Justifying introduct=
ion
of a feature that does not bring benefits but requires effort (money) is
oftentimes challenging &#8211; even if standard would allow. And AFAIK ther=
e is
no really significant deployments of DHCPv4 on handsets over cellular that =
I
would be aware. <br>
&nbsp;<br>
On-demand PDN connection and on-demand IPv4 addressing: I&#8217;m against f=
or
both. Tunneling like DS-Lite would be far easier (static private address, a=
nd
then NAT bindings on-demand).<br>
&nbsp;<br>
Best regards,<br>
&nbsp;<br>
Teemu<br>
&nbsp;<br>
&nbsp;<br>
</span><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>=
<br>
</span><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"=
'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> ext Rajeev Ko=
odli [<a
href=3D"mailto:rkoodli@cisco.com">mailto:rkoodli@cisco.com</a>] <br>
<b>Sent:</b> 22. lokakuuta 2010 07:18<br>
<b>To:</b> Savolainen Teemu (Nokia-MS/Tampere); Fred Baker; <a
href=3D"v6ops@ietf.org">v6ops@ietf.org</a><br>
<b>Cc:</b> <a href=3D"v6ops-chairs@tools.ietf.org">v6ops-chairs@tools.ietf.=
org</a>;
<a href=3D"ron@bonica.org">ron@bonica.org</a><br>
<b>Subject:</b> Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC<br>
</span><br>
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><br>
Hi Teemu,<br>
<br>
Thanks for your feedback.<br>
<br>
On-demand approaches: we had a good discussion already on the matter, and I
have revised the ID based on that discussion. Yes, there are no handsets do=
ing
this, but we left it open for laptops which may do this. If this is not a
possibility at all, it would remain as an option; at this stage, I am not s=
ure
if we should say it is Not an option at all..<br>
<br>
DHCPv4 on cellular handsets: again, the statement is not implying that they
will surely implement DHCPv4. May be you can see what&#8217;s coming in the
future better than I do, but I am going with the option that already exists=
 in
3GPP standards &#8211; PCO to defer address allocation and then using DHCPv=
4.
Again, this may never be done, but it&#8217;s premature to say it <i>will</=
i>
never be done. Besides, consider the handsets accessing the EPC via WiFi
interface, and not the cellular interface. Would you say that handsets will=
 not
do DHCPv4 over WiFi as well?<br>
<br>
Yes, there are additional considerations, and the ID is not making any
recommendations to use on-demand/DHCPv4.As you point out, the ID is only
pointing out that carriers may consider investigating the on-demand address=
ing.<br>
(BTW, on-demand PDN is subject to session inactivity timers, and is not the
same as on-demand IPv4 addressing).<br>
<br>
3G always-on: okay, I will add some clarifying text.<br>
<br>
Regards,<br>
<br>
-Rajeev<br>
<br>
<br>
On 10/21/10 5:01 AM, &quot;<a href=3D"teemu.savolainen@nokia.com">teemu.sav=
olainen@nokia.com</a>&quot;
&lt;<a href=3D"teemu.savolainen@nokia.com">teemu.savolainen@nokia.com</a>&g=
t;
wrote:<br>
<span style=3D'color:#1F497D'>Hi,<br>
&nbsp;<br>
Section 3.1: it is true that IPv4 PDN on-demand and deferred IPv4 address
allocations are &#8220;approaches&#8221; in theory, but I do not believe th=
eir
applicability in practice. E.g. what is the likelyhood that popular desktop
OSes would suddenly implement that kind of features (isn&#8217;t the style
usually ask DHCPv4 right at interface up and then renew forever)?<br>
&nbsp;<br>
Section 3.1: I do not believe cellular handsets will implement DHCPv4 for
cellular interfaces. Hence I disagree with:&#8221;this may very well change=
 in
the future release&#8221;. Cellular handsets have managed without DHCPv4 si=
nce
the dawn of packet switched cellular networks. Why on earth they would now =
start
to use DHCPv4 on cellular access at the very twilight of IPv4? <br>
&nbsp;<br>
The &#8220;additional considerations&#8221; is huge, like there is no benef=
it
whatsoever for hosts to do IPv4 on-demand or deferred IPv4 address allocati=
on.
Also it is non-trivial, like whether DHCPv4 should be triggered if applicat=
ion
binds socket to 127.0.0.1..<br>
&nbsp;<br>
I also slightly disagree with this:&#8221; On the other hand, in the existi=
ng
3G UMTS networks, there is no requirement for an always-on connection&#8221=
;.
While there is no such requirement from standards bodies, essentially for m=
any
devices there is from the end user direction: users want to have IM/Skype/e=
mail
always on. Should be clarified.<br>
&nbsp;<br>
I seem to agree with the conclusions document draws at the end of section 3=
.1
(there is nothing wrong in doing investigations of on-demand PDN..</span></=
span><span
style=3D'font-size:11.0pt;font-family:Wingdings;color:#1F497D'>J<br>
</span><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><br>
Best regards,<br>
&nbsp;<br>
Teemu<br>
&nbsp;<br>
</span><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>=
<br>
</span><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"=
'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a
href=3D"v6ops-bounces@ietf.org">v6ops-bounces@ietf.org</a> [<a
href=3D"mailto:v6ops-bounces@ietf.org">mailto:v6ops-bounces@ietf.org</a>] <=
b>On
Behalf Of </b>ext Fred Baker<br>
<b>Sent:</b> 10. lokakuuta 2010 21:00<br>
<b>To:</b> IPv6 Operations<br>
<b>Cc:</b> <a href=3D"v6ops-chairs@tools.ietf.org">v6ops-chairs@tools.ietf.=
org</a>;
Ron Bonica<br>
<b>Subject:</b> [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC<br>
</span><br>
<span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><br>
</span><span style=3D'font-size:9.0pt;font-family:"Helvetica","sans-serif"'=
>This
is to initiate a two week working group last call of draft-ietf-v6ops-v6-in=
-mobile-networks.
Please read it now. If you find nits (spelling errors, minor suggested word=
ing
changes, etc), comment to the authors; if you find greater issues, such as
disagreeing with a statement or finding additional issues that need to be
addressed, please post your comments to the list.<br>
</span><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>=
<br>
</span><span style=3D'font-size:9.0pt;font-family:"Helvetica","sans-serif"'=
><br>
</span><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>=
<br>
</span><span style=3D'font-size:9.0pt;font-family:"Helvetica","sans-serif"'=
>We
are looking specifically for comments on the importance of the document as =
well
as its content. If you have read the document and believe it to be of
operational utility, that is also an important comment to make. </span><o:p=
></o:p></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>

<hr size=3D3 width=3D"95%" align=3Dcenter>

</span></div>

<p style=3D'margin-bottom:12.0pt'><span style=3D'font-size:11.0pt;font-fami=
ly:"Calibri","sans-serif"'><br>
</span><span style=3D'font-size:10.0pt;font-family:Consolas'>______________=
_________________________________<br>
v6ops mailing list<br>
<a href=3D"v6ops@ietf.org">v6ops@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops">https://www.ietf.or=
g/mailman/listinfo/v6ops</a></span><o:p></o:p></p>

</div>

</div>

</body>

</html>

--_000_18034D4D7FE9AE48BF19AB1B0EF2729F5F056DAAFCNOKEUMSG01mgd_--

From root@core3.amsl.com  Mon Oct 25 14:45:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: v6ops@ietf.org
Delivered-To: v6ops@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 474DF3A68F2; Mon, 25 Oct 2010 14:45:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20101025214502.474DF3A68F2@core3.amsl.com>
Date: Mon, 25 Oct 2010 14:45:02 -0700 (PDT)
Cc: v6ops@ietf.org
Subject: [v6ops] I-D Action:draft-ietf-v6ops-rogue-ra-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 21:45:02 -0000

--NextPart

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


	Title           : Rogue IPv6 Router Advertisement Problem Statement
	Author(s)       : T. Chown, S. Venaas
	Filename        : draft-ietf-v6ops-rogue-ra-02.txt
	Pages           : 16
	Date            : 2010-10-25

When deploying IPv6, whether IPv6-only or dual-stack, routers are
configured to send IPv6 Router Advertisements to convey information
to nodes that enable them to autoconfigure on the network.  This
information includes the implied default router address taken from
the observed source address of the Router Advertisement (RA) message,
as well as on-link prefix information.  However, unintended
misconfigurations by users or administrators, or possibly malicious
attacks on the network, may lead to bogus RAs being present, which in
turn can cause operational problems for hosts on the network.  In
this draft we summarise the scenarios in which rogue RAs may be
observed and present a list of possible solutions to the problem.  We
focus on the unintended causes of rogue RAs in the text.  The goal of
this text is to be Informational, and as such to present a framework
around which solutions can be proposed and discussed.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-rogue-ra-02.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-v6ops-rogue-ra-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-10-25144023.I-D@ietf.org>


--NextPart--

From rkoodli@cisco.com  Mon Oct 25 14:46:36 2010
Return-Path: <rkoodli@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B1EA13A680F for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 14:46:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.652
X-Spam-Level: 
X-Spam-Status: No, score=-108.652 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6X7A1GIA0CMU for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 14:46:25 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id D1EA43A6868 for <v6ops@ietf.org>; Mon, 25 Oct 2010 14:46:22 -0700 (PDT)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsMFALOXxUytJV2Y/2dsb2JhbACBRZ86VHGiUJxUgnWCUwSEVIV5gww
X-IronPort-AV: E=Sophos;i="4.58,237,1286150400";  d="scan'208,217";a="174897641"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rtp-iport-1.cisco.com with ESMTP; 25 Oct 2010 21:48:07 +0000
Received: from xbh-rcd-302.cisco.com (xbh-rcd-302.cisco.com [72.163.63.9]) by rcdn-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id o9PLm7DV014073;  Mon, 25 Oct 2010 21:48:07 GMT
Received: from xmb-rcd-111.cisco.com ([72.163.62.153]) by xbh-rcd-302.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 25 Oct 2010 16:48:07 -0500
Received: from 10.21.64.48 ([10.21.64.48]) by XMB-RCD-111.cisco.com ([72.163.62.153]) with Microsoft Exchange Server HTTP-DAV ;  Mon, 25 Oct 2010 21:48:07 +0000
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Mon, 25 Oct 2010 15:00:41 -0700
From: Rajeev Koodli <rkoodli@cisco.com>
To: <teemu.savolainen@nokia.com>, Fred Baker <fred@cisco.com>, <v6ops@ietf.org>
Message-ID: <C8EB4C19.A37C%rkoodli@cisco.com>
Thread-Topic: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
Thread-Index: ActopRH/JoCme+MzQXiyJfFN4kSgHQIcAP9gACK/4tkAoGaQgAAP2Y+pAAgy+TAAA4ui1g==
In-Reply-To: <18034D4D7FE9AE48BF19AB1B0EF2729F5F056DAAFC@NOK-EUMSG-01.mgdnok.nokia.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3370863641_13066704"
X-OriginalArrivalTime: 25 Oct 2010 21:48:07.0891 (UTC) FILETIME=[4F8B7A30:01CB748E]
Cc: v6ops-chairs@tools.ietf.org, ron@bonica.org
Subject: Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 21:46:36 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3370863641_13066704
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable


Teemu,

I remember well, and am not suggesting anything host-specific.

You stated =B3But a handset that uses DHCPv4 for WiFi, but not for cellular
(as it is point-to-point), needs modifications. =B3

I pointed that iPhone already does that today. I don=B9t know what you call
this =AD host modification etc. But, IMHO, it does not matter what you call;
it=B9s already out there.

The ID is not stating any requirement for the hosts, but brings the
possibilities and the associated issues.

Regards,

-Rajeev


On 10/25/10 1:59 PM, "teemu.savolainen@nokia.com"
<teemu.savolainen@nokia.com> wrote:

> Hi,
> =20
> Remember the host-based vs. network-based mobility discussions?
> =20
> I am essentially using the =B3network-based=B2 camp=B9s argumentation herein:
> modifying large host population (in time!) to support IPv4 on-demand
> (especially with DHCPv4) on cellular access is an infeasible approach and=
 the
> dual-stack using network should just implement some flavor of NAT instead=
.
> =20
> Actually I think the reason is even stronger with the IPv4 on-demand. Wit=
h
> DSMIP6 a host actually gains benefits (like mobility always and not just
> within an administrative domain), but with IPv4 on-demand, or with DHCPv4=
 on
> cellular, the host gains nothing.
> =20
> Best regards,
> =20
> Teemu
> =20
> P.S. We don=B9t use iOS but you do network elements. Maybe you have packet
> captures to share?
> =20
>=20
> From: ext Rajeev Koodli [mailto:rkoodli@cisco.com]
> Sent: 25. lokakuuta 2010 19:24
> To: Savolainen Teemu (Nokia-MS/Tampere); Fred Baker; v6ops@ietf.org
> Cc: v6ops-chairs@tools.ietf.org; ron@bonica.org
> Subject: Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
> =20
>=20
> Teemu,
>=20
> I am not sure how it is an issue to run DHCPv4 over WiFi and not use DHCP=
v4
> over cellular.
> AFAICT, iPhone seems to be doing it today; please correct me otherwise.
>=20
> Thanks,
>=20
> -Rajeev
>=20
>=20
>=20
> On 10/25/10 1:57 AM, "teemu.savolainen@nokia.com" <teemu.savolainen@nokia=
.com>
> wrote:
> Rajeev,
> =20
> I agree that anything may happen in the futureJ
> =20
> Hence IPv4 on-demand could happen, but I don=B9t see it happening at the mo=
ment.
> Hence the draft should be clear that it is something that might be doable=
, but
> not something is there out of the box just for network operator to activa=
te.
> =20
> DHCPv4: for WiFi DHCPv4 is used for sure, of course. But a handset that u=
ses
> DHCPv4 for WiFi, but not for cellular (as it is point-to-point), needs
> modifications. These modifications needs justification, IOP testing, and =
so
> forth *for no benefit* for the handset. And of course not all handsets co=
me
> with WiFi, but may come with dual-stack cellular. Justifying introduction=
 of a
> feature that does not bring benefits but requires effort (money) is often=
times
> challenging =AD even if standard would allow. And AFAIK there is no really
> significant deployments of DHCPv4 on handsets over cellular that I would =
be
> aware.=20
> =20
> On-demand PDN connection and on-demand IPv4 addressing: I=B9m against for b=
oth.
> Tunneling like DS-Lite would be far easier (static private address, and t=
hen
> NAT bindings on-demand).
> =20
> Best regards,
> =20
> Teemu
> =20
> =20
>=20
> From: ext Rajeev Koodli [mailto:rkoodli@cisco.com]
> Sent: 22. lokakuuta 2010 07:18
> To: Savolainen Teemu (Nokia-MS/Tampere); Fred Baker; v6ops@ietf.org
> Cc: v6ops-chairs@tools.ietf.org; ron@bonica.org
> Subject: Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
>=20
>=20
> Hi Teemu,
>=20
> Thanks for your feedback.
>=20
> On-demand approaches: we had a good discussion already on the matter, and=
 I
> have revised the ID based on that discussion. Yes, there are no handsets =
doing
> this, but we left it open for laptops which may do this. If this is not a
> possibility at all, it would remain as an option; at this stage, I am not=
 sure
> if we should say it is Not an option at all..
>=20
> DHCPv4 on cellular handsets: again, the statement is not implying that th=
ey
> will surely implement DHCPv4. May be you can see what=B9s coming in the fut=
ure
> better than I do, but I am going with the option that already exists in 3=
GPP
> standards =AD PCO to defer address allocation and then using DHCPv4. Again,=
 this
> may never be done, but it=B9s premature to say it will never be done. Besid=
es,
> consider the handsets accessing the EPC via WiFi interface, and not the
> cellular interface. Would you say that handsets will not do DHCPv4 over W=
iFi
> as well?
>=20
> Yes, there are additional considerations, and the ID is not making any
> recommendations to use on-demand/DHCPv4.As you point out, the ID is only
> pointing out that carriers may consider investigating the on-demand
> addressing.
> (BTW, on-demand PDN is subject to session inactivity timers, and is not t=
he
> same as on-demand IPv4 addressing).
>=20
> 3G always-on: okay, I will add some clarifying text.
>=20
> Regards,
>=20
> -Rajeev
>=20
>=20
> On 10/21/10 5:01 AM, "teemu.savolainen@nokia.com" <teemu.savolainen@nokia=
.com>
> wrote:
> Hi,
> =20
> Section 3.1: it is true that IPv4 PDN on-demand and deferred IPv4 address
> allocations are =B3approaches=B2 in theory, but I do not believe their
> applicability in practice. E.g. what is the likelyhood that popular deskt=
op
> OSes would suddenly implement that kind of features (isn=B9t the style usua=
lly
> ask DHCPv4 right at interface up and then renew forever)?
> =20
> Section 3.1: I do not believe cellular handsets will implement DHCPv4 for
> cellular interfaces. Hence I disagree with:=B2this may very well change in =
the
> future release=B2. Cellular handsets have managed without DHCPv4 since the =
dawn
> of packet switched cellular networks. Why on earth they would now start t=
o use
> DHCPv4 on cellular access at the very twilight of IPv4?
> =20
> The =B3additional considerations=B2 is huge, like there is no benefit whatsoe=
ver
> for hosts to do IPv4 on-demand or deferred IPv4 address allocation. Also =
it is
> non-trivial, like whether DHCPv4 should be triggered if application binds
> socket to 127.0.0.1..
> =20
> I also slightly disagree with this:=B2 On the other hand, in the existing 3=
G
> UMTS networks, there is no requirement for an always-on connection=B2. Whil=
e
> there is no such requirement from standards bodies, essentially for many
> devices there is from the end user direction: users want to have
> IM/Skype/email always on. Should be clarified.
> =20
> I seem to agree with the conclusions document draws at the end of section=
 3.1
> (there is nothing wrong in doing investigations of on-demand PDN..J
>=20
> Best regards,
> =20
> Teemu
> =20
>=20
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of=
 ext
> Fred Baker
> Sent: 10. lokakuuta 2010 21:00
> To: IPv6 Operations
> Cc: v6ops-chairs@tools.ietf.org; Ron Bonica
> Subject: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
>=20
>=20
> This is to initiate a two week working group last call of
> draft-ietf-v6ops-v6-in-mobile-networks. Please read it now. If you find n=
its
> (spelling errors, minor suggested wording changes, etc), comment to the
> authors; if you find greater issues, such as disagreeing with a statement=
 or
> finding additional issues that need to be addressed, please post your com=
ments
> to the list.
>=20
>=20
>=20
> We are looking specifically for comments on the importance of the documen=
t as
> well as its content. If you have read the document and believe it to be o=
f
> operational utility, that is also an important comment to make.
>=20
>=20
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>=20


--B_3370863641_13066704
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:11pt=
'><BR>
Teemu,<BR>
<BR>
I remember well, and am not suggesting anything host-specific.<BR>
<BR>
You stated &#8220;<FONT COLOR=3D"#1E487C">But a handset that uses DHCPv4 for =
WiFi, but not for cellular (as it is point-to-point), needs modifications. &=
#8220;<BR>
<BR>
</FONT>I pointed that iPhone already does that today. I don&#8217;t know wh=
at you call this &#8211; host modification etc. But, IMHO, it does not matte=
r what you call; it&#8217;s already out there. <BR>
<BR>
The ID is not stating any requirement for the hosts, but brings the possibi=
lities and the associated issues. <BR>
<BR>
Regards,<BR>
<BR>
-Rajeev<BR>
<BR>
<BR>
On 10/25/10 1:59 PM, &quot;<a href=3D"teemu.savolainen@nokia.com">teemu.savol=
ainen@nokia.com</a>&quot; &lt;<a href=3D"teemu.savolainen@nokia.com">teemu.sav=
olainen@nokia.com</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><=
SPAN STYLE=3D'font-size:11pt'><FONT COLOR=3D"#1F497D">Hi,<BR>
&nbsp;<BR>
Remember the host-based vs. network-based mobility discussions?<BR>
&nbsp;<BR>
I am essentially using the &#8220;network-based&#8221; camp&#8217;s argumen=
tation herein: modifying large host population (in time!) to support IPv4 on=
-demand (especially with DHCPv4) on cellular access is an infeasible approac=
h and the dual-stack using network should just implement some flavor of NAT =
instead. <BR>
&nbsp;<BR>
Actually I think the reason is even stronger with the IPv4 on-demand. With =
DSMIP6 a host actually gains benefits (like mobility always and not just wit=
hin an administrative domain), but with IPv4 on-demand, or with DHCPv4 on ce=
llular, the host gains nothing. <BR>
&nbsp;<BR>
Best regards,<BR>
&nbsp;<BR>
Teemu<BR>
&nbsp;<BR>
P.S. We don&#8217;t use iOS but you do network elements. Maybe you have pac=
ket captures to share?<BR>
&nbsp;<BR>
</FONT><BR>
</SPAN></FONT><FONT SIZE=3D"2"><FONT FACE=3D"Tahoma, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:10pt'><B>From:</B> ext Rajeev Koodli [<a href=3D"mailt=
o:rkoodli@cisco.com">mailto:rkoodli@cisco.com</a>] <BR>
<B>Sent:</B> 25. lokakuuta 2010 19:24<BR>
<B>To:</B> Savolainen Teemu (Nokia-MS/Tampere); Fred Baker; <a href=3D"v6ops@=
ietf.org">v6ops@ietf.org</a><BR>
<B>Cc:</B> <a href=3D"v6ops-chairs@tools.ietf.org">v6ops-chairs@tools.ietf.or=
g</a>; <a href=3D"ron@bonica.org">ron@bonica.org</a><BR>
<B>Subject:</B> Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Times New Roman"><SPAN STYLE=3D'font-size:12=
pt'> <BR>
</SPAN></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'=
font-size:11pt'><BR>
Teemu,<BR>
<BR>
I am not sure how it is an issue to run DHCPv4 over WiFi and not use DHCPv4=
 over cellular.<BR>
AFAICT, iPhone seems to be doing it today; please correct me otherwise.<BR>
<BR>
Thanks,<BR>
<BR>
-Rajeev<BR>
<BR>
<BR>
<BR>
On 10/25/10 1:57 AM, &quot;<a href=3D"teemu.savolainen@nokia.com">teemu.savol=
ainen@nokia.com</a>&quot; &lt;<a href=3D"teemu.savolainen@nokia.com">teemu.sav=
olainen@nokia.com</a>&gt; wrote:<BR>
<FONT COLOR=3D"#1F497D">Rajeev,<BR>
&nbsp;<BR>
I agree that anything may happen in the future</FONT></SPAN></FONT><SPAN ST=
YLE=3D'font-size:11pt'><FONT COLOR=3D"#1F497D"><FONT FACE=3D"Wingdings">J</FONT><F=
ONT FACE=3D"Calibri, Verdana, Helvetica, Arial"> <BR>
&nbsp;<BR>
Hence IPv4 on-demand could happen, but I don&#8217;t see it happening at th=
e moment. Hence the draft should be clear that it is something that might be=
 doable, but not something is there out of the box just for network operator=
 to activate.<BR>
&nbsp;<BR>
DHCPv4: for WiFi DHCPv4 is used for sure, of course. But a handset that use=
s DHCPv4 for WiFi, but not for cellular (as it is point-to-point), needs mod=
ifications. These modifications needs justification, IOP testing, and so for=
th *<B>for no benefit</B>* for the handset. And of course not all handsets c=
ome with WiFi, but may come with dual-stack cellular. Justifying introductio=
n of a feature that does not bring benefits but requires effort (money) is o=
ftentimes challenging &#8211; even if standard would allow. And AFAIK there =
is no really significant deployments of DHCPv4 on handsets over cellular tha=
t I would be aware. <BR>
&nbsp;<BR>
On-demand PDN connection and on-demand IPv4 addressing: I&#8217;m against f=
or both. Tunneling like DS-Lite would be far easier (static private address,=
 and then NAT bindings on-demand).<BR>
&nbsp;<BR>
Best regards,<BR>
&nbsp;<BR>
Teemu<BR>
&nbsp;<BR>
&nbsp;<BR>
</FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><BR>
</FONT></SPAN><FONT SIZE=3D"2"><FONT FACE=3D"Tahoma, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:10pt'><B>From:</B> ext Rajeev Koodli [<a href=3D"mailt=
o:rkoodli@cisco.com">mailto:rkoodli@cisco.com</a>] <BR>
<B>Sent:</B> 22. lokakuuta 2010 07:18<BR>
<B>To:</B> Savolainen Teemu (Nokia-MS/Tampere); Fred Baker; <a href=3D"v6ops@=
ietf.org">v6ops@ietf.org</a><BR>
<B>Cc:</B> <a href=3D"v6ops-chairs@tools.ietf.org">v6ops-chairs@tools.ietf.or=
g</a>; <a href=3D"ron@bonica.org">ron@bonica.org</a><BR>
<B>Subject:</B> Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Times New Roman"><SPAN STYLE=3D'font-size:12=
pt'><BR>
</SPAN></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'=
font-size:11pt'><BR>
Hi Teemu,<BR>
<BR>
Thanks for your feedback.<BR>
<BR>
On-demand approaches: we had a good discussion already on the matter, and I=
 have revised the ID based on that discussion. Yes, there are no handsets do=
ing this, but we left it open for laptops which may do this. If this is not =
a possibility at all, it would remain as an option; at this stage, I am not =
sure if we should say it is Not an option at all..<BR>
<BR>
DHCPv4 on cellular handsets: again, the statement is not implying that they=
 will surely implement DHCPv4. May be you can see what&#8217;s coming in the=
 future better than I do, but I am going with the option that already exists=
 in 3GPP standards &#8211; PCO to defer address allocation and then using DH=
CPv4. Again, this may never be done, but it&#8217;s premature to say it <I>w=
ill</I> never be done. Besides, consider the handsets accessing the EPC via =
WiFi interface, and not the cellular interface. Would you say that handsets =
will not do DHCPv4 over WiFi as well?<BR>
<BR>
Yes, there are additional considerations, and the ID is not making any reco=
mmendations to use on-demand/DHCPv4.As you point out, the ID is only pointin=
g out that carriers may consider investigating the on-demand addressing.<BR>
(BTW, on-demand PDN is subject to session inactivity timers, and is not the=
 same as on-demand IPv4 addressing).<BR>
<BR>
3G always-on: okay, I will add some clarifying text.<BR>
<BR>
Regards,<BR>
<BR>
-Rajeev<BR>
<BR>
<BR>
On 10/21/10 5:01 AM, &quot;<a href=3D"teemu.savolainen@nokia.com">teemu.savol=
ainen@nokia.com</a>&quot; &lt;<a href=3D"teemu.savolainen@nokia.com">teemu.sav=
olainen@nokia.com</a>&gt; wrote:<BR>
<FONT COLOR=3D"#1F497D">Hi,<BR>
&nbsp;<BR>
Section 3.1: it is true that IPv4 PDN on-demand and deferred IPv4 address a=
llocations are &#8220;approaches&#8221; in theory, but I do not believe thei=
r applicability in practice. E.g. what is the likelyhood that popular deskto=
p OSes would suddenly implement that kind of features (isn&#8217;t the style=
 usually ask DHCPv4 right at interface up and then renew forever)?<BR>
&nbsp;<BR>
Section 3.1: I do not believe cellular handsets will implement DHCPv4 for c=
ellular interfaces. Hence I disagree with:&#8221;this may very well change i=
n the future release&#8221;. Cellular handsets have managed without DHCPv4 s=
ince the dawn of packet switched cellular networks. Why on earth they would =
now start to use DHCPv4 on cellular access at the very twilight of IPv4? <BR=
>
&nbsp;<BR>
The &#8220;additional considerations&#8221; is huge, like there is no benef=
it whatsoever for hosts to do IPv4 on-demand or deferred IPv4 address alloca=
tion. Also it is non-trivial, like whether DHCPv4 should be triggered if app=
lication binds socket to 127.0.0.1..<BR>
&nbsp;<BR>
I also slightly disagree with this:&#8221; On the other hand, in the existi=
ng 3G UMTS networks, there is no requirement for an always-on connection&#82=
21;. While there is no such requirement from standards bodies, essentially f=
or many devices there is from the end user direction: users want to have IM/=
Skype/email always on. Should be clarified.<BR>
&nbsp;<BR>
I seem to agree with the conclusions document draws at the end of section 3=
.1 (there is nothing wrong in doing investigations of on-demand PDN..</FONT>=
</SPAN></FONT><SPAN STYLE=3D'font-size:11pt'><FONT COLOR=3D"#1F497D"><FONT FACE=3D=
"Wingdings">J<BR>
</FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><BR>
Best regards,<BR>
&nbsp;<BR>
Teemu<BR>
&nbsp;<BR>
</FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><BR>
</FONT></SPAN><FONT SIZE=3D"2"><FONT FACE=3D"Tahoma, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:10pt'><B>From:</B> <a href=3D"v6ops-bounces@ietf.org">=
v6ops-bounces@ietf.org</a> [<a href=3D"mailto:v6ops-bounces@ietf.org">mailto:v=
6ops-bounces@ietf.org</a>] <B>On Behalf Of </B>ext Fred Baker<BR>
<B>Sent:</B> 10. lokakuuta 2010 21:00<BR>
<B>To:</B> IPv6 Operations<BR>
<B>Cc:</B> <a href=3D"v6ops-chairs@tools.ietf.org">v6ops-chairs@tools.ietf.or=
g</a>; Ron Bonica<BR>
<B>Subject:</B> [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Times New Roman"><SPAN STYLE=3D'font-size:12=
pt'><BR>
</SPAN></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'=
font-size:11pt'><BR>
</SPAN></FONT><FONT SIZE=3D"1"><FONT FACE=3D"Helvetica, Verdana, Arial"><SPAN S=
TYLE=3D'font-size:9pt'>This is to initiate a two week working group last call =
of draft-ietf-v6ops-v6-in-mobile-networks. Please read it now. If you find n=
its (spelling errors, minor suggested wording changes, etc), comment to the =
authors; if you find greater issues, such as disagreeing with a statement or=
 finding additional issues that need to be addressed, please post your comme=
nts to the list.<BR>
</SPAN></FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN =
STYLE=3D'font-size:11pt'><BR>
</SPAN></FONT><FONT SIZE=3D"1"><FONT FACE=3D"Helvetica, Verdana, Arial"><SPAN S=
TYLE=3D'font-size:9pt'><BR>
</SPAN></FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN =
STYLE=3D'font-size:11pt'><BR>
</SPAN></FONT><FONT SIZE=3D"1"><FONT FACE=3D"Helvetica, Verdana, Arial"><SPAN S=
TYLE=3D'font-size:9pt'>We are looking specifically for comments on the importa=
nce of the document as well as its content. If you have read the document an=
d believe it to be of operational utility, that is also an important comment=
 to make.=20
</SPAN></FONT></FONT>
<P ALIGN=3DCENTER>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:11pt=
'><HR ALIGN=3DCENTER SIZE=3D"3" WIDTH=3D"95%"></SPAN></FONT>
<P>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:11pt=
'><BR>
<BR>
</SPAN></FONT><FONT SIZE=3D"2"><FONT FACE=3D"Consolas, Courier New, Courier"><S=
PAN STYLE=3D'font-size:10pt'>_______________________________________________<B=
R>
v6ops mailing list<BR>
<a href=3D"v6ops@ietf.org">v6ops@ietf.org</a><BR>
<a href=3D"https://www.ietf.org/mailman/listinfo/v6ops">https://www.ietf.org/=
mailman/listinfo/v6ops</a><BR>
</SPAN></FONT></FONT><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN =
STYLE=3D'font-size:11pt'><BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--B_3370863641_13066704--


From root@core3.amsl.com  Mon Oct 25 15:00:03 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: v6ops@ietf.org
Delivered-To: v6ops@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 45B753A682B; Mon, 25 Oct 2010 15:00:03 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20101025220003.45B753A682B@core3.amsl.com>
Date: Mon, 25 Oct 2010 15:00:03 -0700 (PDT)
Cc: v6ops@ietf.org
Subject: [v6ops] I-D Action:draft-ietf-v6ops-tunnel-security-concerns-04.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 22:00:03 -0000

--NextPart

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


	Title           : Security Concerns With IP Tunneling
	Author(s)       : S. Krishnan, et al.
	Filename        : draft-ietf-v6ops-tunnel-security-concerns-04.txt
	Pages           : 19
	Date            : 2010-10-25

A number of security concerns with IP tunnels are documented in this
memo.  The intended audience of this document includes network
administrators and future protocol developers.  The primary intent of
this document is to raise the awareness level regarding the security
issues with IP tunnels as deployed today.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-tunnel-security-concerns-04.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-v6ops-tunnel-security-concerns-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-10-25145124.I-D@ietf.org>


--NextPart--

From brian.e.carpenter@gmail.com  Mon Oct 25 15:03:46 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 81AB33A68A2 for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 15:03:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.417
X-Spam-Level: 
X-Spam-Status: No, score=-102.417 tagged_above=-999 required=5 tests=[AWL=0.182, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cPiUL09kXZSB for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 15:03:45 -0700 (PDT)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by core3.amsl.com (Postfix) with ESMTP id EDC2A3A693A for <v6ops@ietf.org>; Mon, 25 Oct 2010 15:03:40 -0700 (PDT)
Received: by wwe15 with SMTP id 15so1334246wwe.1 for <v6ops@ietf.org>; Mon, 25 Oct 2010 15:05:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ywPgJM5RcUJ6TGfHoi7heXt7wpF6SScijg/WB/DXzpQ=; b=NZA+JlHMHKJHzcV2o0SM0CDp+asSDIuY2x8Qs28eBJRLMGsPtj6K9mhGY9o+JF91xZ /BHwoVHPAy7459BzeJs3NES77lDGN4hbCbkypS3ryV74jfc23jtVj5dyyLDLWgLI9UeK gVFaOKeKVEStvJo1i7fUU9WDAt2UEmE2L6rg8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=M0wAIYplp7Xzy4vnQeB8Hqi2nxaqoKWp6Jet90pDNRRGVuDUm6QebqPR/hklBzgnum HHuqJdFv5P8wR6tltH+5WKArhnmKPcgySdjOKUqzEfrHSEK8UYL1qVzSibzt/cMXyqQa 2lvov6Rp2Q2S443H3qOM7Tu4Df2uOrOei20j0=
Received: by 10.216.156.9 with SMTP id l9mr939136wek.38.1288044314919; Mon, 25 Oct 2010 15:05:14 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.142.15]) by mx.google.com with ESMTPS id l14sm4565476weq.11.2010.10.25.15.05.11 (version=SSLv3 cipher=RC4-MD5); Mon, 25 Oct 2010 15:05:14 -0700 (PDT)
Message-ID: <4CC5FF13.7090302@gmail.com>
Date: Tue, 26 Oct 2010 11:05:07 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: sthaug@nethelp.no
References: <49F119D8-F6D4-4873-A177-4EE911BD268E@gmail.com>	<20101025.202557.74664409.sthaug@nethelp.no>	<EB708A3F-3D63-4B29-8F5A-8AA69681B544@gmail.com> <20101025.224518.104116551.sthaug@nethelp.no>
In-Reply-To: <20101025.224518.104116551.sthaug@nethelp.no>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: v6ops@ietf.org, rja.lists@gmail.com
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 22:03:46 -0000

On 2010-10-26 09:45, sthaug@nethelp.no wrote:
>>> Do you think this is likely to stop people
>>> from using prefixes longer than 64 bits?
>>
>> BOTTOM LINE:
>>
>> It ought to reduce the chance that RIRs and ISPs/LIRs
>> will delegate prefixes longer than 64 bits to sites.  
>> That outcome would be very helpful to the recipients 
>> of such delegated prefixes.
> 
> As of today, if I had a customer connecting to my network on a real
> point-to-point link (SDH, serial, etc), I would assign a /127 prefix
> for this link - and expect the customer use this prefix. I could be
> convinced to assign a /64 but then I'd have to require the customer
> to actually *use* a /127. This is because a /127 is (IMHO) the only
> reasonable way of preventing a loop on such links.

The draft talks about assignments to sites, not to point to point
links. I think we've hammered out consensus that /127 is just fine
for pt2pt links.

Sites won't work properly today with prefixes longer than 64 bits,
because sites use SLAAC by default. If 3177bis doesn't point that
out, it should do.

    Brian

From root@core3.amsl.com  Mon Oct 25 15:15:35 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: v6ops@ietf.org
Delivered-To: v6ops@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id AA8D83A680F; Mon, 25 Oct 2010 15:15:29 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20101025221533.AA8D83A680F@core3.amsl.com>
Date: Mon, 25 Oct 2010 15:15:30 -0700 (PDT)
Cc: v6ops@ietf.org
Subject: [v6ops] I-D Action:draft-ietf-v6ops-v6-in-mobile-networks-02.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 22:15:35 -0000

--NextPart

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


	Title           : Mobile Networks Considerations for IPv6 Deployment
	Author(s)       : R. Koodli
	Filename        : draft-ietf-v6ops-v6-in-mobile-networks-02.txt
	Pages           : 17
	Date            : 2010-10-25

Mobile Internet access from smartphones and other mobile devices is
accelerating the exhaustion of IPv4 addresses.  IPv6 is widely seen
as crucial for the continued operation and growth of the Internet,
and in particular, it is critical in mobile networks.  This document
discusses the issues that arise when deploying IPv6 in mobile
networks.  Hence, this document can be a useful reference for service
providers and network designers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-v6-in-mobile-networks-02.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-v6ops-v6-in-mobile-networks-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-10-25151016.I-D@ietf.org>


--NextPart--

From sthaug@nethelp.no  Mon Oct 25 15:16:04 2010
Return-Path: <sthaug@nethelp.no>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 16DBA3A6BF2 for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 15:16:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[AWL=0.198,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B7DJQL6G2MPK for <v6ops@core3.amsl.com>; Mon, 25 Oct 2010 15:16:01 -0700 (PDT)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by core3.amsl.com (Postfix) with SMTP id 5137F3A6BF8 for <v6ops@ietf.org>; Mon, 25 Oct 2010 15:15:59 -0700 (PDT)
Received: (qmail 30281 invoked from network); 25 Oct 2010 22:17:44 -0000
Received: from bizet.nethelp.no (HELO localhost) (195.1.209.33) by bizet.nethelp.no with SMTP; 25 Oct 2010 22:17:44 -0000
Date: Tue, 26 Oct 2010 00:17:44 +0200 (CEST)
Message-Id: <20101026.001744.39242977.sthaug@nethelp.no>
To: brian.e.carpenter@gmail.com
From: sthaug@nethelp.no
In-Reply-To: <4CC5FF13.7090302@gmail.com>
References: <EB708A3F-3D63-4B29-8F5A-8AA69681B544@gmail.com> <20101025.224518.104116551.sthaug@nethelp.no> <4CC5FF13.7090302@gmail.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: v6ops@ietf.org
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 22:16:04 -0000

> The draft talks about assignments to sites, not to point to point
> links. I think we've hammered out consensus that /127 is just fine
> for pt2pt links.
> 
> Sites won't work properly today with prefixes longer than 64 bits,
> because sites use SLAAC by default. If 3177bis doesn't point that
> out, it should do.

Agreed, /64 or shorter should be assigned to sites. We assign /56 to
residential customers, and /48 or /56 to business customers.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no



From randy@psg.com  Tue Oct 26 17:11:42 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6AD743A690C for <v6ops@core3.amsl.com>; Tue, 26 Oct 2010 17:11:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.56
X-Spam-Level: 
X-Spam-Status: No, score=-2.56 tagged_above=-999 required=5 tests=[AWL=0.039,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Y2IaKR+qLOt for <v6ops@core3.amsl.com>; Tue, 26 Oct 2010 17:11:34 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 2732A3A6836 for <v6ops@ietf.org>; Tue, 26 Oct 2010 17:11:28 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1PAtdW-000Dho-HI; Wed, 27 Oct 2010 00:13:02 +0000
Date: Wed, 27 Oct 2010 09:13:01 +0900
Message-ID: <m2sjzswl0y.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <EB708A3F-3D63-4B29-8F5A-8AA69681B544@gmail.com>
References: <49F119D8-F6D4-4873-A177-4EE911BD268E@gmail.com> <20101025.202557.74664409.sthaug@nethelp.no> <EB708A3F-3D63-4B29-8F5A-8AA69681B544@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: v6ops@ietf.org
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Oct 2010 00:11:43 -0000

>> Do you think this is likely to stop people
>> from using prefixes longer than 64 bits?
> It ought to reduce the chance that RIRs and ISPs/LIRs
> will delegate prefixes longer than 64 bits to sites.  

and it will reduce the probablity of comets impacting on an ietf
meeting.

can we focus on reality here?

randy

From randy@psg.com  Tue Oct 26 17:12:30 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7EB2E3A6836 for <v6ops@core3.amsl.com>; Tue, 26 Oct 2010 17:12:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level: 
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c0JnaKjU0RnT for <v6ops@core3.amsl.com>; Tue, 26 Oct 2010 17:12:19 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id CCF163A6918 for <v6ops@ietf.org>; Tue, 26 Oct 2010 17:12:17 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1PAteX-000Di3-91; Wed, 27 Oct 2010 00:14:05 +0000
Date: Wed, 27 Oct 2010 09:14:04 +0900
Message-ID: <m2r5fcwkz7.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Steinar Haug <sthaug@nethelp.no>
In-Reply-To: <20101025.220032.41712705.sthaug@nethelp.no>
References: <20101025.202557.74664409.sthaug@nethelp.no> <EB708A3F-3D63-4B29-8F5A-8AA69681B544@gmail.com> <20101025194347.GA32268@Space.Net> <20101025.220032.41712705.sthaug@nethelp.no>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: v6ops@ietf.org
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Oct 2010 00:12:31 -0000

> That's what I suspect. We're running IPv6 on Cisco and Juniper gear
> here, with /64s, /126s, /127s, /128s and some other prefix lengths, in
> IS-IS and BGP. It all works, no problems observed.

and i would not touch a vendor who could not do so.  so we know of such
vendors?  time for attitude adjustment time.

randy

From brian.e.carpenter@gmail.com  Tue Oct 26 18:46:36 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CC6153A6950 for <v6ops@core3.amsl.com>; Tue, 26 Oct 2010 18:46:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.581
X-Spam-Level: 
X-Spam-Status: No, score=-102.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j1TzuiyjA0Dr for <v6ops@core3.amsl.com>; Tue, 26 Oct 2010 18:46:35 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id A5FCD3A6907 for <v6ops@ietf.org>; Tue, 26 Oct 2010 18:46:35 -0700 (PDT)
Received: by qyk5 with SMTP id 5so172343qyk.10 for <v6ops@ietf.org>; Tue, 26 Oct 2010 18:48:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=DsblhB2SuVml8jJQ46XiMsGbdn+jAXnN95kPd1O/wtM=; b=f7fUxz3+b7I6umhJ3eAMACQVcA1bwGolih7W1yRi3HN7usujOLt27Hg4UXLXOiNWcY RBtQM2zBWpuwcFcSVX0SmOMOXrX22Z4U755/lDD3ap5KySeAP041Bljod3d/NX1OV+8l j2l96ZfmVVRp+QcJvRaBOpU95+S5UbU5mCUh4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; b=opMEy5O3RiOuWZ8RpUG/VQlFtDP4q7h/A38z2XBAhvjjHCaiui+R8lB47gcM1yZdtG 4BdLAxRBxIdW29ZduSt2wkJ/qc+CxJtzcEG/QpqLo0xZ1zYu5/TVmeMPa1CtH5Dbapj5 ytcgFJw6dXv/tn36reCcbc5X7HZ7RE74aCwXk=
Received: by 10.229.225.208 with SMTP id it16mr1214233qcb.247.1288144102936; Tue, 26 Oct 2010 18:48:22 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id ew4sm2386679vcb.23.2010.10.26.18.48.20 (version=SSLv3 cipher=RC4-MD5); Tue, 26 Oct 2010 18:48:22 -0700 (PDT)
Message-ID: <4CC784E3.9090307@gmail.com>
Date: Wed, 27 Oct 2010 14:48:19 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IPv6 Operations <v6ops@ietf.org>
References: <20101025153004.4D5883A6A7F@core3.amsl.com>
In-Reply-To: <20101025153004.4D5883A6A7F@core3.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [v6ops] I-D Action:draft-wing-v6ops-happy-eyeballs-ipv6-01.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Oct 2010 01:46:37 -0000

Hi,

> 3.  Problem Statement
...
>    As discussed in more detail in Section 3.2, IPv6 connectivity is
>    sometimes broken entirely or slower than native IPv4 connectivity.

Could you add something like:

Later in the transition process, it is likely that the exact opposite of
this will apply. A strategy is needed that deals equally well with both of
these situations.

> 4.1.  IPv6
...
>    The first thread that succeeds returns the completed connection to
>    the parent code and aborts the other thread (Section 4.2.2).


Is there a race condition here?

> 4.2.4.  Determining Address Type
> 
>    [[[ IS THIS SECTION NECESSARY ??

I don't see why.

> 4.2.5.  Debugging and Troubleshooting
> 
>    This mechanism is aimed to help the user experience in case of
>    connectivity problems.  However, this precise reason also makes it
>    tougher to use these applications as a means of the verification that
>    the problems are fixed.  To assist in that regard, the applications
>    implementing the proposal in this document SHOULD also provide a
>    mechanism to temporarily use only one address family.

Could I suggest that the last sentence should be

 To assist in that regard, the applications
 implementing the proposal in this document MUST also provide a
 configurable mechanism to use only one address family if both
 are available.

I think it really is a MUST for trouble-shooting, and the key
point isn't that it's temporary but that it can be switched on
and off.

Regards
   Brian Carpenter

From pekkas@netcore.fi  Wed Oct 27 00:32:54 2010
Return-Path: <pekkas@netcore.fi>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 519273A68FB for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 00:32:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.507
X-Spam-Level: 
X-Spam-Status: No, score=-102.507 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZJXZ1dLJ79U9 for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 00:32:52 -0700 (PDT)
Received: from netcore.fi (eunet-gw.ipv6.netcore.fi [IPv6:2001:670:86:3001::1]) by core3.amsl.com (Postfix) with ESMTP id D59593A67A7 for <v6ops@ietf.org>; Wed, 27 Oct 2010 00:32:51 -0700 (PDT)
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.13.8/8.13.8) with ESMTP id o9R7YbBV007288 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Oct 2010 10:34:37 +0300
Received: from localhost (pekkas@localhost) by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id o9R7YbXL007285; Wed, 27 Oct 2010 10:34:37 +0300
Date: Wed, 27 Oct 2010 10:34:37 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Randy Bush <randy@psg.com>
In-Reply-To: <m2r5fcwkz7.wl%randy@psg.com>
Message-ID: <alpine.LRH.2.00.1010271032420.7151@netcore.fi>
References: <20101025.202557.74664409.sthaug@nethelp.no> <EB708A3F-3D63-4B29-8F5A-8AA69681B544@gmail.com> <20101025194347.GA32268@Space.Net> <20101025.220032.41712705.sthaug@nethelp.no> <m2r5fcwkz7.wl%randy@psg.com>
User-Agent: Alpine 2.00 (LRH 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: clamav-milter 0.96.4 at otso.netcore.fi
X-Virus-Status: Clean
Cc: v6ops@ietf.org
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Oct 2010 07:32:54 -0000

On Wed, 27 Oct 2010, Randy Bush wrote:
>> That's what I suspect. We're running IPv6 on Cisco and Juniper gear
>> here, with /64s, /126s, /127s, /128s and some other prefix lengths, in
>> IS-IS and BGP. It all works, no problems observed.
>
> and i would not touch a vendor who could not do so.  so we know of such
> vendors?  time for attitude adjustment time.

FWIW, some time ago a customer reported a forwarding loop problem on 
their equipment which seemed to have been caused by an Extreme 
Networks device when configured w/ >64b prefix.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

From randy@psg.com  Wed Oct 27 00:39:54 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB1293A6826 for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 00:39:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.563
X-Spam-Level: 
X-Spam-Status: No, score=-2.563 tagged_above=-999 required=5 tests=[AWL=0.036,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id diyoV74Tm+UD for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 00:39:49 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id D9E643A68D2 for <v6ops@ietf.org>; Wed, 27 Oct 2010 00:39:41 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1PB0dT-000FBN-NN; Wed, 27 Oct 2010 07:41:28 +0000
Date: Wed, 27 Oct 2010 16:41:26 +0900
Message-ID: <m262woulp5.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Pekka Savola <pekkas@netcore.fi>
In-Reply-To: <alpine.LRH.2.00.1010271032420.7151@netcore.fi>
References: <20101025.202557.74664409.sthaug@nethelp.no> <EB708A3F-3D63-4B29-8F5A-8AA69681B544@gmail.com> <20101025194347.GA32268@Space.Net> <20101025.220032.41712705.sthaug@nethelp.no> <m2r5fcwkz7.wl%randy@psg.com> <alpine.LRH.2.00.1010271032420.7151@netcore.fi>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: v6ops mailing list <v6ops@ietf.org>
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Oct 2010 07:39:55 -0000

>> and i would not touch a vendor who could not do so.  so we know of
>> such vendors?  time for attitude adjustment time.
> 
> FWIW, some time ago a customer reported a forwarding loop problem on 
> their equipment which seemed to have been caused by an Extreme 
> Networks device when configured w/ >64b prefix.

great.  was a bug report filed?  until fixed, will avoid broken vendor.

randy

From remi.despres@free.fr  Wed Oct 27 03:24:29 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 989863A693B for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 03:24:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.53
X-Spam-Level: 
X-Spam-Status: No, score=-1.53 tagged_above=-999 required=5 tests=[AWL=0.419,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PGlDY00y9YYr for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 03:24:28 -0700 (PDT)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.84]) by core3.amsl.com (Postfix) with ESMTP id 78F823A6933 for <v6ops@ietf.org>; Wed, 27 Oct 2010 03:24:28 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2414.sfr.fr (SMTP Server) with ESMTP id 26C7D7000093; Wed, 27 Oct 2010 12:26:17 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2414.sfr.fr (SMTP Server) with ESMTP id 635117000097; Wed, 27 Oct 2010 12:26:16 +0200 (CEST)
X-SFR-UUID: 20101027102616406.635117000097@msfrf2414.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <4CC784E3.9090307@gmail.com>
Date: Wed, 27 Oct 2010 12:26:15 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1494EB97-3846-420B-8F67-5574E1405A53@free.fr>
References: <20101025153004.4D5883A6A7F@core3.amsl.com> <4CC784E3.9090307@gmail.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>, Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1081)
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-wing-v6ops-happy-eyeballs-ipv6-01.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Oct 2010 10:24:29 -0000

Hi, Brian, Dan,

This proposal is IMHO very useful.
I support that it can become a WG document.


Le 27 oct. 2010 =E0 03:48, Brian E Carpenter a =E9crit :

> Hi,
>=20
>> 3.  Problem Statement
> ...
>>   As discussed in more detail in Section 3.2, IPv6 connectivity is
>>   sometimes broken entirely or slower than native IPv4 connectivity.
>=20
> Could you add something like:
>=20
> Later in the transition process, it is likely that the exact opposite =
of
> this will apply. A strategy is needed that deals equally well with =
both of
> these situations.

Agreed.
(The problem is also similar to that which already exists in IPv4 when =
the DNS returns several A records.)


Also, sec 3 says:  =20
   "Reasons for such failure include no connection to the IPv6 Internet,
   broken 6to4 or Teredo tunnels, and broken IPv6 peering."

It could usefully be clarified that these failures have different =
natures, e.g. with:
"Reasons for such failure include missing paths between some 6to4 =
addresses and native IPv6 addresses, incompatible NAT types between some =
Teredo addresses, or temporary breakage of IPv6 paths."

Note that a hosts that has an IPv6 address other than 6to4 should have a =
both-way connection to the IPv6 Internet unless something is temporarily =
broken.=20


>=20
>> 4.1.  IPv6
> ...
>>   The first thread that succeeds returns the completed connection to
>>   the parent code and aborts the other thread (Section 4.2.2).
>=20
>=20
> Is there a race condition here?

Not that I see.
The connection initiator makes the decision in view of what *he sees* as =
the first one to succeed.


>=20
>> 4.2.4.  Determining Address Type
>>=20
>>   [[[ IS THIS SECTION NECESSARY ??
>=20
> I don't see why.

The subject is worth looking at, IMHO, but seems out of scope for this =
draft which should stand for itself.

>=20
>> 4.2.5.  Debugging and Troubleshooting
>>=20
>>   This mechanism is aimed to help the user experience in case of
>>   connectivity problems.  However, this precise reason also makes it
>>   tougher to use these applications as a means of the verification =
that
>>   the problems are fixed.  To assist in that regard, the applications
>>   implementing the proposal in this document SHOULD also provide a
>>   mechanism to temporarily use only one address family.
>=20
> Could I suggest that the last sentence should be
>=20
> To assist in that regard, the applications
> implementing the proposal in this document MUST also provide a
> configurable mechanism to use only one address family if both
> are available.

>=20
> I think it really is a MUST for trouble-shooting, and the key
> point isn't that it's temporary but that it can be switched on
> and off.

SHOULD seems good enough to me (equivalent to a MUST unless you find =
some good raison against it), but MUST is OK too.

Regards,
RD




From Nick.Heatley@everythingeverywhere.com  Wed Oct 27 06:14:50 2010
Return-Path: <Nick.Heatley@everythingeverywhere.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 743C13A67FB for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 06:14:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.299
X-Spam-Level: 
X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=1.299,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZmiWBTY2Rq1G for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 06:14:41 -0700 (PDT)
Received: from mail140.messagelabs.com (mail140.messagelabs.com [85.158.137.83]) by core3.amsl.com (Postfix) with SMTP id ADC9F3A6A43 for <v6ops@ietf.org>; Wed, 27 Oct 2010 06:13:49 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: Nick.Heatley@everythingeverywhere.com
X-Msg-Ref: server-10.tower-140.messagelabs.com!1288185338!11442443!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [193.36.79.211]
Received: (qmail 20235 invoked from network); 27 Oct 2010 13:15:38 -0000
Received: from unknown (HELO autechre) (193.36.79.211) by server-10.tower-140.messagelabs.com with SMTP; 27 Oct 2010 13:15:38 -0000
Received: from hatmmar02.TMOUSERSUK.AD.T-MOBILE.CO.UK (Not Verified[194.34.15.199]) by autechre with MailMarshal (v6, 8, 2, 9371) id <B4cc8262b0001>; Wed, 27 Oct 2010 14:16:27 +0100
Received: from hatmsg002.TMOUSERSUK.AD.T-MOBILE.CO.UK (Not Verified[10.243.193.76]) by hatmmar02.TMOUSERSUK.AD.T-MOBILE.CO.UK with MailMarshal (v6, 8, 3, 9481) id <B4cc825f80002>; Wed, 27 Oct 2010 14:15:36 +0100
Received: from HATMSG025.TMOUSERSUK.AD.T-MOBILE.CO.UK ([10.243.197.36]) by hatmsg002.TMOUSERSUK.AD.T-MOBILE.CO.UK with Microsoft SMTPSVC(6.0.3790.4675); Wed, 27 Oct 2010 14:15:37 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB75D9.0B2DFBB6"
Date: Wed, 27 Oct 2010 14:15:36 +0100
Message-ID: <E7C3026796D78841949FD2274E3A946204C79485@HATMSG025.TMOUSERSUK.AD.T-MOBILE.CO.UK>
In-Reply-To: <C8E65E7C.A1E3%rkoodli@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC
thread-index: ActopRH/JoCme+MzQXiyJfFN4kSgHQIcAP9gACK/4tkAqHzlMA==
From: "Heatley, Nick " <Nick.Heatley@everythingeverywhere.com>
To: "Rajeev Koodli" <rkoodli@cisco.com>, "Fred Baker" <fred@cisco.com>, <v6ops@ietf.org>
X-OriginalArrivalTime: 27 Oct 2010 13:15:37.0115 (UTC) FILETIME=[0B7AEEB0:01CB75D9]
X-Mailman-Approved-At: Wed, 27 Oct 2010 06:19:57 -0700
Cc: v6ops-chairs@tools.ietf.org
Subject: [v6ops]  draft-ietf-v6ops-v6-in-mobile-networks WGLC
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Oct 2010 13:17:15 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB75D9.0B2DFBB6
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hi Rajeev,

An interesting and potentially useful draft, thanks.

To refine the draft I would kindly ask you to consider the 4 items
below:

=20

Section 3.1

The document states:

>In other words, the IETF's recommended model of dual-stack IPv6 and
IPv4 networks is readily applicable to mobile networks with the support
for distinct APNs and the ability to carry IPv6 traffic on PDP/PDN
connections.

=20

1. I see an additional barrier to dual stack for mobile - the PDP
resource overhead in RAN and Core from two PDPs (separate PDP for v4 and
v6). I think you mention this but do you regard it as a barrier or not?

There is the resource aspects from the number of sessions supported, and
also there may be licensing costs, a commercial barrier to dual stack
for the mass market.

This has a bearing on the Operator's IPv6 introduction strategy.

=20

2. Mitigation to this resource overhead could be =20

i) Implement IPv6-only-bearer, as per section 3.3=20

Or (ii) to couple the dual-stack-bearer with LTE (Release 9 network)

Can both these points be mentioned where dual stack is recommended, to
balance the argument?

=20

3. I would like to propose a specific sub section in Section 3 covering
the advantages of "IPv6 in the LTE network" (with more information on
the combined v4v6 pdp/pdn connection).

=20

Combined v4v6 pdp/pdn connection

-          LTE introduces the v4v6 combined PDP which is supported by a
release 8 terminal.

-          The LTE Release 9 network allows the v4v6 combined PDP to be
maintained consistently in LTE and when falling back to 3G/2G.

-          This removes the overhead of two PDPs in 2G/3G, as well as
LTE.

-          Given an operator's LTE coverage may start in major urban
areas and take time to rollout nationally, and the dual PDP resource
issues (as above), then a LTE Release 9 network can work optimally with
dual stack. Depending on timescales, some mobile operators may use LTE
as the vehicle for enabling a dual stack bearer network.

=20

[Note that some people prefer "LTE" rather than "4G" as it can be argued
that only LTE-Advanced (Release 10) is truly 4G by the standards
definition. I leave that one up to you :-)]

=20

4. Finally if you are releasing a draft on "IPv6 in mobile networks" I
would request you include something on IP version for packet voice
meaning specifically Voice in LTE networks. I would expect this to fall
under the LTE section. Otherwise I would argue this document is "v6 for
mobile internet" :-)

Is it intentional that packet voice is an omission? I appreciate that
some discussions here are not yet concluded. However IP version is very
relevant and a steer here could help the industry.

I am happy to send you my thoughts on packet voice and IP addressing
issues.

=20

Just my 2 cents for your consideration!

Best Regards,

Nick Heatley

=20

=20

=20


NOTICE AND DISCLAIMER
This e-mail (including any attachments) is intended for the above-named p=
erson(s).  If you are not the intended recipient, notify the sender immed=
iately, delete this email from your system and do not disclose or use for=
=20any purpose. =20
=20
We may monitor all incoming and outgoing emails in line with current legi=
slation. We have taken steps to ensure that this email and attachments ar=
e free from any virus, but it remains your responsibility to ensure that =
viruses do not adversely affect you.=20

Everything Everywhere Limited
Registered in England and Wales
Company Registered Number: 02382161
Registered Office Address: Hatfield Business Park, Hatfield, Hertfordshir=
e, AL10 9BW

------_=_NextPart_001_01CB75D9.0B2DFBB6
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">
<title>Re: [v6ops] draft-ietf-v6ops-v6-in-mobile-networks WGLC</title>

<style>
<!--
=20/* Font Definitions */
=20@font-face
=09{font-family:Wingdings;
=09panose-1:5 0 0 0 0 0 0 0 0 0;}
=20/* Style Definitions */
=20p.MsoNormal, li.MsoNormal, div.MsoNormal
=09{margin:0cm;
=09margin-bottom:.0001pt;
=09font-size:12.0pt;
=09font-family:"Times New Roman";}
a:link, span.MsoHyperlink
=09{color:blue;
=09text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
=09{color:blue;
=09text-decoration:underline;}
p
=09{margin-right:0cm;
=09margin-left:0cm;
=09font-size:12.0pt;
=09font-family:"Times New Roman";}
p.HTMLPreformatted1, li.HTMLPreformatted1, div.HTMLPreformatted1
=09{margin:0cm;
=09margin-bottom:.0001pt;
=09line-height:14.4pt;
=09font-size:10.0pt;
=09font-family:"Courier New";}
span.EmailStyle19
=09{font-family:Arial;
=09color:navy;}
span.ms-rtecustom-med-grey1
=09{color:#999999;
=09background:white;}
@page Section1
=09{size:595.3pt 841.9pt;
=09margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
=09{page:Section1;}
=20/* List Definitions */
=20ol
=09{margin-bottom:0cm;}
ul
=09{margin-bottom:0cm;}
-->
</style>

</head>

<body lang=3DEN-GB link=3Dblue vlink=3Dblue>

<div class=3DSection1>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>An interesting and potentially usefu=
l
draft, thanks.</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>To refine the draft I would kindly a=
sk you
to consider the 4 items below:</span></font></p>

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

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

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

<p class=3DHTMLPreformatted1><font size=3D2 face=3D"Courier New"><span
style=3D'font-size:10.0pt'>&gt;In other words, the IETF's recommended mod=
el of
dual-stack IPv6 and IPv4 networks is readily applicable to mobile network=
s with
the support for distinct APNs and the ability to carry IPv6 traffic on PD=
P/PDN
connections.</span></font></p>

<p class=3DHTMLPreformatted1><font size=3D2 face=3D"Courier New"><span
style=3D'font-size:10.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>1. I see an additional barrier to du=
al
stack for mobile - the PDP resource overhead in RAN and Core from two PDP=
s
(separate PDP for v4 and v6). I think you mention this but do you regard =
it as
a barrier or not?</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>There is the resource aspects from t=
he
number of sessions supported, and also there may be licensing costs, a
commercial barrier to dual stack for the mass market.</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>This has a bearing on the Operator&#=
8217;s
IPv6 introduction strategy.</span></font></p>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>2. Mitigation to this resource overh=
ead
could be&nbsp; </span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>i) Implement IPv6-only-bearer, as pe=
r
section 3.3 </span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Or (ii) to couple the dual-stack-bea=
rer
with LTE (Release 9 network)</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Can both these points be mentioned w=
here
dual stack is recommended, to balance the argument?</span></font></p>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>3. I would like to propose a specifi=
c sub
section in Section 3 covering the advantages of &#8220;IPv6 in the LTE
network&#8221; (with more information on the combined v4v6 pdp/pdn connec=
tion).</span></font></p>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Combined v4v6 pdp/pdn connection</sp=
an></font></p>

<p class=3DMsoNormal style=3D'margin-left:36.0pt;text-indent:-18.0pt'><fo=
nt size=3D2
color=3Dnavy face=3DArial><span style=3D'font-size:10.0pt;font-family:Ari=
al;
color:navy'>-<font size=3D1 face=3D"Times New Roman"><span style=3D'font:=
7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
</span></font></span></font><font size=3D2 color=3Dnavy face=3DArial><spa=
n
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>LTE introduces th=
e v4v6
combined PDP which is supported by a release 8 terminal.</span></font></p=
>

<p class=3DMsoNormal style=3D'margin-left:36.0pt;text-indent:-18.0pt'><fo=
nt size=3D2
color=3Dnavy face=3DArial><span style=3D'font-size:10.0pt;font-family:Ari=
al;
color:navy'>-<font size=3D1 face=3D"Times New Roman"><span style=3D'font:=
7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
</span></font></span></font><font size=3D2 color=3Dnavy face=3DArial><spa=
n
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>The LTE Release 9=
=20network
allows the v4v6 combined PDP to be maintained consistently in LTE and whe=
n
falling back to 3G/2G.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:36.0pt;text-indent:-18.0pt'><fo=
nt size=3D2
color=3Dnavy face=3DArial><span style=3D'font-size:10.0pt;font-family:Ari=
al;
color:navy'>-<font size=3D1 face=3D"Times New Roman"><span style=3D'font:=
7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
</span></font></span></font><font size=3D2 color=3Dnavy face=3DArial><spa=
n
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>This removes the =
overhead
of two PDPs in 2G/3G, as well as LTE.</span></font></p>

<p class=3DMsoNormal style=3D'margin-left:36.0pt;text-indent:-18.0pt'><fo=
nt size=3D2
color=3Dnavy face=3DArial><span style=3D'font-size:10.0pt;font-family:Ari=
al;
color:navy'>-<font size=3D1 face=3D"Times New Roman"><span style=3D'font:=
7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;
</span></font></span></font><font size=3D2 color=3Dnavy face=3DArial><spa=
n
style=3D'font-size:10.0pt;font-family:Arial;color:navy'>Given an operator=
&#8217;s
LTE coverage may start in major urban areas and take time to rollout
nationally, and the dual PDP resource issues (as above), then a LTE Relea=
se 9
network can work optimally with dual stack. Depending on timescales, some=
=20mobile
operators may use LTE as the vehicle for enabling a dual stack bearer net=
work.</span></font></p>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>[Note that some people prefer
&#8220;LTE&#8221; rather than &#8220;4G&#8221; as it can be argued that o=
nly
LTE-Advanced (Release 10) is truly 4G by the standards definition. I leav=
e that
one up to you </span></font><font size=3D2 color=3Dnavy face=3DWingdings>=
<span
style=3D'font-size:10.0pt;font-family:Wingdings;color:navy'>J</span></fon=
t><font
size=3D2 color=3Dnavy face=3DArial><span style=3D'font-size:10.0pt;font-f=
amily:Arial;
color:navy'>]</span></font></p>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>4. Finally if you are releasing a dr=
aft on
&#8220;IPv6 in mobile networks&#8221; I would request you include somethi=
ng on IP
version for packet voice meaning specifically Voice in LTE networks. I wo=
uld
expect this to fall under the LTE section. Otherwise I would argue this
document is &#8220;v6 for mobile internet&#8221; </span></font><font size=
=3D2
color=3Dnavy face=3DWingdings><span style=3D'font-size:10.0pt;font-family=
:Wingdings;
color:navy'>J</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Is it intentional that packet voice =
is an
omission? I appreciate that some discussions here are not yet concluded.
However IP version is very relevant and a steer here could help the indus=
try.</span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I am happy to send you my thoughts o=
n
packet voice and IP addressing issues.</span></font></p>

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

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span style=
=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Just my 2 cents for your considerati=
on!</span></font></p>

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

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

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

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

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

</div>


<P>NOTICE AND DISCLAIMER<BR>This e-mail (including any attachments) is in=
tended=20
for the above-named person(s).&nbsp; If you are not the intended recipien=
t,=20
notify the sender immediately, delete this email from your system and do =
not=20
disclose or use for any purpose.&nbsp; <BR>&nbsp;<BR>We may monitor all i=
ncoming=20
and outgoing emails in line with current legislation. We have taken steps=
=20to=20
ensure that this email and attachments are free from any virus, but it re=
mains=20
your responsibility to ensure that viruses do not adversely affect you. <=
/P>
<P>Everything Everywhere Limited<BR>Registered in England and Wales<BR>Co=
mpany=20
Registered Number: 02382161<BR>Registered Office Address: Hatfield Busine=
ss=20
Park, Hatfield, Hertfordshire, AL10 9BW</P>
</body>

</html>

------_=_NextPart_001_01CB75D9.0B2DFBB6--

From scott.brim@gmail.com  Wed Oct 27 07:34:48 2010
Return-Path: <scott.brim@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 402523A6925 for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 07:34:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.557
X-Spam-Level: 
X-Spam-Status: No, score=-102.557 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dox2Zc8Jv82r for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 07:34:45 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 4335F3A6784 for <v6ops@ietf.org>; Wed, 27 Oct 2010 07:34:45 -0700 (PDT)
Received: by vws6 with SMTP id 6so52713vws.31 for <v6ops@ietf.org>; Wed, 27 Oct 2010 07:36:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=jnUgBfNmxIbRTgr1wB7TKi9YbHJxZ+C4iOTXXfNhtkk=; b=C8LlFt0arYGXTU0qjTuX1zlFtQng8/Nxxk8uAzsVfaH8CgfiXGdadLjVE21pjNGv6Z 3IiV7cpjxY+l38CZCV2WM4fDRo1YRpP6zN6g+Wee86PjTs0NmIKd4SCxrGq/0Kolgsjv K+akiKFGZekORSFsB5awrMvI2Ty3vyLSCXHb4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=nzstxVZDGl3IK15C5FRFBDEIOjWou168GFuDEuqxl6N9FHBiSkJ3K49LcT3YtKUmaq t8j9t6594nyeId0E8z3Y8pI1hWwi8JoZz01ZJmFcOCS/e7NZ30wlcsN665Q0VqXHyEyv DVYqXuEvMGlx8N3na5QD09emDpvsuTrrbi//I=
Received: by 10.220.195.77 with SMTP id eb13mr1021991vcb.119.1288190194444; Wed, 27 Oct 2010 07:36:34 -0700 (PDT)
Received: from sbrim-mbp.local (198-135-0-233.cisco.com [198.135.0.233]) by mx.google.com with ESMTPS id p32sm4544782vbl.5.2010.10.27.07.36.32 (version=SSLv3 cipher=RC4-MD5); Wed, 27 Oct 2010 07:36:33 -0700 (PDT)
Message-ID: <4CC838EF.8070003@gmail.com>
Date: Wed, 27 Oct 2010 10:36:31 -0400
From: Scott Brim <scott.brim@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.11) Gecko/20101013 Thunderbird/3.1.5
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <20101025153004.4D5883A6A7F@core3.amsl.com> <4CC784E3.9090307@gmail.com>
In-Reply-To: <4CC784E3.9090307@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-wing-v6ops-happy-eyeballs-ipv6-01.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Oct 2010 14:34:48 -0000

On 10/26/2010 21:48 EDT, Brian E Carpenter wrote:
>> 4.2.5.  Debugging and Troubleshooting
>>
>>    This mechanism is aimed to help the user experience in case of
>>    connectivity problems.  However, this precise reason also makes it
>>    tougher to use these applications as a means of the verification that
>>    the problems are fixed.  To assist in that regard, the applications
>>    implementing the proposal in this document SHOULD also provide a
>>    mechanism to temporarily use only one address family.
> 
> Could I suggest that the last sentence should be
> 
>  To assist in that regard, the applications
>  implementing the proposal in this document MUST also provide a
>  configurable mechanism to use only one address family if both
>  are available.
> 
> I think it really is a MUST for trouble-shooting, and the key
> point isn't that it's temporary but that it can be switched on
> and off.

The essence of this section is that there should be some way to bypass
the nice features of happy eyeballs in order to be able to probe what's
really going on in the network at the app level.

I agree that "temporary" isn't the key point, and would remove that.
However, I don't believe that _all_ applications _must_ implement a
bypass mechanism, as Brian suggests.  The only apps that must implement
it are the ones that need it: debugging tools, for instance.  You don't
need to use a web browser in order to do a traceroute.  So, since this
choice is on a per-application basis, I suggest

  To assist in that regard, environments implementing the proposal
  in this document MUST provide a mechanism by which an application MAY
  be able use only one particular address family.

Scott

From fred@cisco.com  Wed Oct 27 08:01:10 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4B48A3A695E for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 08:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.059
X-Spam-Level: 
X-Spam-Status: No, score=-109.059 tagged_above=-999 required=5 tests=[AWL=-1.127, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, RCVD_NUMERIC_HELO=2.067, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bkwz8LIpbSOv for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 08:01:06 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 8FEFB3A6A13 for <v6ops@ietf.org>; Wed, 27 Oct 2010 08:01:05 -0700 (PDT)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAMbbx0yrR7H+/2dsb2JhbAChUQhxogGcHYVIBIRXhXyDCA
X-IronPort-AV: E=Sophos;i="4.58,246,1286150400"; d="scan'208";a="374985792"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-1.cisco.com with ESMTP; 27 Oct 2010 15:02:55 +0000
Received: from 202.10.224.10.in-addr.arpa (sjc-vpn5-59.cisco.com [10.21.88.59]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o9RF2MKD019534 for <v6ops@ietf.org>; Wed, 27 Oct 2010 15:02:49 GMT
Received: from [127.0.0.1] by 202.10.224.10.in-addr.arpa (PGP Universal service); Wed, 27 Oct 2010 08:02:54 -0700
X-PGP-Universal: processed; by 202.10.224.10.in-addr.arpa on Wed, 27 Oct 2010 08:02:54 -0700
Mime-Version: 1.0 (Apple Message framework v1081)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4CC48191.2040608@bogus.com>
Date: Wed, 27 Oct 2010 07:02:01 -0700
Message-Id: <F9AA6756-5D41-44FC-82E4-E70F37971689@cisco.com>
References: <52E02B43-ECEA-434C-85FE-4C244A812EBB@cisco.com> <m27hh99eu8.wl%randy@psg.com> <2518253F-C880-4E99-AF35-35B285F28AB8@cisco.com> <4CC3CCAE.70502@bogus.com> <4AF82CFC-9FC3-49F5-A16F-0DF67358E166@cisco.com> <4CC46E40.30000@bogus.com> <777203F2-7E40-46B9-A85D-131C282EA795@cisco.com> <4CC48191.2040608@bogus.com>
To: IPv6 Operations <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1081)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Re: [v6ops] Etiquette
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Oct 2010 15:01:10 -0000

Last week, I said

On Oct 21, 2010, at 12:16 PM, Fred Baker wrote:
> The chairs just received a note concerned about decorum on the list. =
In general, this list should be about items mentioned in the charter. If =
we have comments about companies, their products, or their deployments, =
it would be best if we took those up directly with the networks or =
vendors in question rather than using this forum.

The chairs have been contacted by another party that is concerned about =
the clarity of the statement; he thought it could be interpreted to =
preclude some perfectly legitimate discussions, which of course was not =
the intent. After some discussion with my co-chairs, let me revise the =
statement to say this:


The citation of implemention specific details (device, network, =
management etc) in the process of understanding a problem in scope for =
v6ops is appropriate. The standards of routine ietf discourse apply.

v6ops is, however, not a surrogate for RFP, RFE, or technical support =
roles at either network providers or equipment vendors. Topics that are =
better answered in those venues are out of scope for v6ops discussion.


I hope that's adequately clear.=

From ostokes@extremenetworks.com  Wed Oct 27 11:43:33 2010
Return-Path: <ostokes@extremenetworks.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C6DB43A6991 for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 11:43:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id veYHqI3NJHqe for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 11:43:32 -0700 (PDT)
Received: from ussc-casht-p1.extremenetworks.com (ussc-casht-p1.extremenetworks.com [207.179.9.62]) by core3.amsl.com (Postfix) with ESMTP id 6EA103A698E for <v6ops@ietf.org>; Wed, 27 Oct 2010 11:43:24 -0700 (PDT)
Received: from USEXCHANGE.corp.extremenetworks.com ([10.0.4.74]) by ussc-casht-p2.corp.extremenetworks.com ([10.255.181.88]) with mapi; Wed, 27 Oct 2010 11:45:15 -0700
From: Olen Stokes <ostokes@extremenetworks.com>
To: 'Randy Bush' <randy@psg.com>, Pekka Savola <pekkas@netcore.fi>
Date: Wed, 27 Oct 2010 11:45:13 -0700
Thread-Topic: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt
Thread-Index: Act1qmvXvjbHjCGURf2D7vqEPv+QDQAXCjzA
Message-ID: <6738A78F51650A4FAEDCF6844B26C21473CF3826E6@USEXCHANGE.corp.extremenetworks.com>
References: <20101025.202557.74664409.sthaug@nethelp.no> <EB708A3F-3D63-4B29-8F5A-8AA69681B544@gmail.com> <20101025194347.GA32268@Space.Net> <20101025.220032.41712705.sthaug@nethelp.no>	<m2r5fcwkz7.wl%randy@psg.com> <alpine.LRH.2.00.1010271032420.7151@netcore.fi> <m262woulp5.wl%randy@psg.com>
In-Reply-To: <m262woulp5.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: v6ops mailing list <v6ops@ietf.org>
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Oct 2010 18:43:33 -0000

The latest EXOS code release corrects reported customer problems.  Please s=
ee EXOS release documentation for additional information about support for =
IPv6 routes with masks > 64 bits.

In keeping with today's email about "Etiquette", I would be happy to take a=
ny additional discussion offline.

Olen

-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of R=
andy Bush
Sent: Wednesday, October 27, 2010 3:41 AM
To: Pekka Savola
Cc: v6ops mailing list
Subject: Re: [v6ops] draft-ietf-v6ops-3177bis-end-sites-00.txt

>> and i would not touch a vendor who could not do so.  so we know of
>> such vendors?  time for attitude adjustment time.
>=20
> FWIW, some time ago a customer reported a forwarding loop problem on=20
> their equipment which seemed to have been caused by an Extreme=20
> Networks device when configured w/ >64b prefix.

great.  was a bug report filed?  until fixed, will avoid broken vendor.

randy
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

From brian.e.carpenter@gmail.com  Wed Oct 27 15:34:48 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0FF993A6768 for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 15:34:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cJZD1I9s-Dpm for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 15:34:46 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id AF6C73A6405 for <v6ops@ietf.org>; Wed, 27 Oct 2010 15:34:45 -0700 (PDT)
Received: by wyb28 with SMTP id 28so1209649wyb.31 for <v6ops@ietf.org>; Wed, 27 Oct 2010 15:36:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Dom0KuMFg2sYQiVsI0SuUT71+6fO30NadR/oVElE4es=; b=PB7dRG2TaK6bNh8ZfS6IiaSwFsQeVS5qUHRFDHjk5J9nyDW5bb4J00GR8X3OihX0vE GlbGou1jVlHWh70p2RVuJIVeMYAluRqu0XQwPCh0/U9ds1lyNuuAYDW/Vtqk8TgAcokd /6KJnEP1CW7SnUwGDlYo88kwbUhOPAfA/Ce5E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=qXH33g2W+gPymxNuVHIaRL7houdc1sOOU1zOU+cEdD/xUoBNm1OgA3UxN4n7RNf0sc u6Hd16c98n1RupoIjT8weaOchbwsPIxh+9vgpLQaJXR8zQoilhlqlv/k3Fd6FKf6bYaj dmY46KaaWean8glSqlc/RFm74n3DZ110ppZ2E=
Received: by 10.216.154.202 with SMTP id h52mr4870442wek.46.1288218995571; Wed, 27 Oct 2010 15:36:35 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id w29sm233135weq.19.2010.10.27.15.36.32 (version=SSLv3 cipher=RC4-MD5); Wed, 27 Oct 2010 15:36:34 -0700 (PDT)
Message-ID: <4CC8A96B.9090109@gmail.com>
Date: Thu, 28 Oct 2010 11:36:27 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
References: <20101025153004.4D5883A6A7F@core3.amsl.com> <4CC784E3.9090307@gmail.com> <4CC838EF.8070003@gmail.com>
In-Reply-To: <4CC838EF.8070003@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-wing-v6ops-happy-eyeballs-ipv6-01.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Oct 2010 22:34:48 -0000

Hi Scott,

On 2010-10-28 03:36, Scott Brim wrote:
> On 10/26/2010 21:48 EDT, Brian E Carpenter wrote:
>>> 4.2.5.  Debugging and Troubleshooting
>>>
>>>    This mechanism is aimed to help the user experience in case of
>>>    connectivity problems.  However, this precise reason also makes it
>>>    tougher to use these applications as a means of the verification that
>>>    the problems are fixed.  To assist in that regard, the applications
>>>    implementing the proposal in this document SHOULD also provide a
>>>    mechanism to temporarily use only one address family.
>> Could I suggest that the last sentence should be
>>
>>  To assist in that regard, the applications
>>  implementing the proposal in this document MUST also provide a
>>  configurable mechanism to use only one address family if both
>>  are available.
>>
>> I think it really is a MUST for trouble-shooting, and the key
>> point isn't that it's temporary but that it can be switched on
>> and off.
> 
> The essence of this section is that there should be some way to bypass
> the nice features of happy eyeballs in order to be able to probe what's
> really going on in the network at the app level.
> 
> I agree that "temporary" isn't the key point, and would remove that.
> However, I don't believe that _all_ applications _must_ implement a
> bypass mechanism, as Brian suggests.  The only apps that must implement
> it are the ones that need it: debugging tools, for instance.  You don't
> need to use a web browser in order to do a traceroute.  So, since this
> choice is on a per-application basis, I suggest
> 
>   To assist in that regard, environments implementing the proposal
>   in this document MUST provide a mechanism by which an application MAY
>   be able use only one particular address family.

Well, I am not too bothered about this, but let me say that I have
many times had occasion to flip the state of network.dns.disableIPv6
in Firefox, independently of doing traceroute.

   Brian

From victor.kuarsingh@gmail.com  Wed Oct 27 19:13:05 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EAC623A67FE for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 19:13:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=-0.450, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9TDepAc3O-ST for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 19:13:04 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id 5EBF53A67FB for <v6ops@ietf.org>; Wed, 27 Oct 2010 19:13:04 -0700 (PDT)
Received: by gwb15 with SMTP id 15so999974gwb.31 for <v6ops@ietf.org>; Wed, 27 Oct 2010 19:14:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=15yO5ug05DUnCB/Lg1+QuJm2PGzAArKuw5ZXQ6wCppI=; b=P8pVaCVSYmpMAaIwgKw/wXT5qEZaZwtiil3iERPExLhc4BvkTQ/m//eHZgAZXc3UEI GHUaprglWOIQhm+22OLtGrbmnbhb3Yfq+KPQBx+v5JT4aeFw7tZ9pW7lAlC4WykM9k8r R47fQqlBMU4V5xGb7rdKmdEut38puVUIt21nQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=F7c8CuM8wXhKphfkpQ6Ovif4ZUeGBkxHaki+8c5YZUt9drWvaUh4NKW8glhXsSZYVR TYnUJeRfVAeA6n+Rhs6znpn063AvGSubhmMfenEttmvlnqP+eqQuCMB+Ax7P4t12TGuK zOiDmmuRujkbu0Fg/FNWnQA4y5kRxWjkDVfzA=
Received: by 10.151.144.8 with SMTP id w8mr16592435ybn.430.1288232094368; Wed, 27 Oct 2010 19:14:54 -0700 (PDT)
Received: from [192.168.100.149] ([67.224.83.162]) by mx.google.com with ESMTPS id f46sm333057yhc.17.2010.10.27.19.14.48 (version=SSLv3 cipher=RC4-MD5); Wed, 27 Oct 2010 19:14:53 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Wed, 27 Oct 2010 22:14:45 -0400
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: =?ISO-8859-1?B?UultaQ==?= =?ISO-8859-1?B?IERlc3By6XM=?= <remi.despres@free.fr>, v6ops v6ops <v6ops@ietf.org>
Message-ID: <C8EE54D5.10A40%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
Thread-Index: Act2ReNk6v9PyBTHEU63uZl+wWnoHQ==
In-Reply-To: <660EFF7C-8621-4B74-B836-178594D71BE6@free.fr>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
Cc: Scott Beuker <Scott.Beuker@sjrb.ca>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2010 02:13:06 -0000

Remi,

I do appreciate the points from the group.  I agree, IPv6 native =3D
good/best.  I also agree, where I cannot have Native IPv6, we will provide =
a
more managed solution (like 6RD).  Don't get me wrong, I will push for IPv6
with all my might and effort.

But unfortunately, neither of these options help operators where there are
"unmanaged" devices which are not yet upgraded to support such technologies=
.
Believe it or not, many persons do not ever upgrade their firmware in their
home gateways)

Operators need an option to help customers who have not yet replaced
equipment which has a "current set" of features (and as noted, this often
includes 6to4 default operation).  PMT offered a way of doing this such tha=
t
the customer would get a level of service by default based on current
hardware.

The intent is not to use PMT as a "good IPv6" option, but rather as a "last
resort IPv6 option" if needed.  I cannot stress enough that this is not
intended to challenge, distract or replace real IPv6 deployments.  But, man=
y
operators have commented on this list that the reality in our networks is
that we cannot control all our CPE endpoints, and replacing them is many
times out of our control.

We will continue to persuade users to upgrade/replace their equipment, but
experience has shown us that this takes time, and often times unsuccessful
(refusal, unwillingness etc)

It appears that that a number of commenter's in this list would rather us
(operators) not address this segment of the population, and just "hope" tha=
t
IPv4 only will work for them (again, I understand the risk of IPv6 only
endpoints is low, but possible).

I offer this question to the list, what "option" is available for the
"non-upgraded" and "IPv4 only" endpoints? I will say that quoting a new
technology like 6RD and native IPv6 are not options for the use case we hav=
e
presented.  Ignoring these customers is also not an option.  We are in the
business of helping customers even if they don't help themselves (to the
extent possible).

Would the group agree with this statement "we would rather provide no IPv6
at all rather then IPv6 based on 6to4-PMT"?

Again, our goal (in order of preference)
1. Provide IPv6 Native
2. Provided Managed Tunnel IPv6 (like 6RD)
3. If uncontrolled/un-upgraded CPE - provide last resort option (which PMT
was one of our suggestions)
4. Do nothing and hope for the best (I hate this one the most)

Constructive options welcome.  I am not trying to be difficult or
belligerent, but rather looking for solutions to problems.

Regards,

Victor



On 25/10/10 3:35 AM, "R=E9mi Despr=E9s" <remi.despres@free.fr> wrote:

>=20
> Le 23 oct. 2010 =E0 17:55, Victor Kuarsingh a =E9crit :
>> ...
>> Why would we depreciate something that works before all the viable
>> alternatives (6RD, Native IPv6 and new things like 6a44) are still not o=
ut
>> there in mass?  Why reduce that IPv6 glue space?
>> ...
>> My analogy to Internet usage for most is like "gas in the car".  Most pe=
ople
>> put gas in the card, turn the key and press the accelerator/break.  All =
the
>> rest "just works".
>=20
>> Our mission (as operators) will be to make things "just
>> work".
>=20
> Agreed, what is needed is what "just works".
>=20
> Now:
> * Native IPv6 "just works"
>  1. guaranteed e2e address transparency (OK for peer-to-peer)
>  2. guaranteed connectivity
>  3. ISP control of customer QoS
> * 6to4 between two 6to4 addresses (without 6o4 relays) "just works":
>  1. guaranteed e2e address transparency
>  2. guaranteed connectivity
>  3. ISP control of customer QoS (that of IPv4)
> * 6to4 between a 6to4 address and a native-IPv6 address (with 2 6to4 rela=
ys)
> "doesn't just work":
>  1. (e2e address transparency still available)
>  2. guaranteed connectivity is LOST
>  3. ISP control of customer QoS is LOST
>=20
> If SOME ISPs would deploy 6to4-PMT, i.e. add NAT66's to 6to4 relays, 6to4
> would EVEN LESS "just work":
> - For 6to4 customers of 6to4-PMT ISPs:
>  1. e2e address transparency is LOST (peer-to-peer in Ipv6 is broken)
>  2. guaranteed connectivity is still LOST  (depends on whether remote
> native-IPv6 hosts access 6to4 relays)
>  3. ISP control of customer QoS is still LOST (if remote native-IPv6 host=
s
> have access to 6to4 relays, it depends on which ones)
> - For native IPv6 customers
>  1. guaranteed e2e address transparency is LOST (remote native IPv6 addre=
sses
> may now be translated on their way)
>  2. guaranteed connectivity with 6to4 addresses is still LOST (not all 6t=
o4
> addresses are 6to4-PMT addresses)
>  3. ISP control of customer QoS is still LOST (not all 6to4 addresses are
> 6to4-PMT addresses)
> - For 6to4 customers of ISPs that haven't 6to4-PMT:
>  1. e2e address transparency is LOST (they may be talking to 6to4-PMT
> customers)
>  2. guaranteed connectivity is still LOST (they may have no access to a 6=
to4
> relay)
>  3. ISP control of customer QoS is LOST (if they access some 6to4 relays,=
 it
> depends on which ones)
>=20
> 6to4-PMT is simple, a quality, but, by combining two mechanisms that alre=
ady
> create more problems than they solve (6to4 relays and NAT66), it can only=
 lead
> to poor user experience in IPv6.
>=20
> The technical content of the above can be challenged if one finds that is=
 has
> mistakes.
> But if it is right, the conclusion is that, to only keep solutions that "=
just
> work", using the 6to4 anycast address in 6to4 customers should be turned =
off,
> at least by default, and that where 6to4 relays are still in use, no NAT6=
6 of
> any form should be added to them.
>=20
>=20
>> Plus, depreciating it would take time since it hard to force customers t=
o
>> upgrade OSs (although this has become automated in most OSs) and consume=
r
>> equipment (many customers do not upgrade past store rev firmware).
>=20
> Deprecating a spec only means "if you have the choice, no longer do it".
> In my understanding, deprecating 6to4-anycast in customer devices doesn't=
 mean
> that 6to4 relays that exist today should be dismantled.
> As long as operators of these relays don't offer native IPv6, and see tha=
t
> they still have users, they are perfectly entitled to maintain these rela=
ys
> for these users.
>=20
>=20
> To conclude, the proposal is that IETF:
> - deprecates the use of the 6to4-relay anycast address in 6to4 routers
> - explains why associating NAT66's with 6to4 relays should be avoided
> This will contribute to make IPv6 something that "just works".
>=20
> Regards,
> RD
>=20
>=20
>>=20
>> Just a thought.
>>=20
>> Regards,
>>=20
>> Victor
>>=20
>>=20
>> On 23/10/10 5:20 AM, "Gert Doering" <gert@space.net> wrote:
>>=20
>>> Hi,
>>>=20
>>> On Sat, Oct 23, 2010 at 09:15:38AM +1300, Brian E Carpenter wrote:
>>>> On 2010-10-23 08:04, Gert Doering wrote:
>>>>=20
>>>>> One approach to rework 3056 would be to completely deprecate the
>>>>> 6to4-with-anycast model.
>>>>=20
>>>> That is to say, deprecate RFC 3068 and revert to the pure RFC 3056 mod=
el.
>>>=20
>>> Well, yes.  Sorry for mixing these RFCs.
>>>=20
>>>> Good idea. Could you push my toothpaste back into the tube, too, pleas=
e ;-)
>>>=20
>>> Well, it's not like we haven't done this before.  A6/bitstring deprecia=
tion
>>> comes to mind...
>>>=20
>>> Gert Doering
>>>        -- NetMaster
>>=20
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>=20
>=20



From randy@psg.com  Wed Oct 27 19:37:31 2010
Return-Path: <randy@psg.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8BB423A680A for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 19:37:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.564
X-Spam-Level: 
X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.035,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WbT70D++A6AU for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 19:37:28 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by core3.amsl.com (Postfix) with ESMTP id 60C5D3A67AF for <v6ops@ietf.org>; Wed, 27 Oct 2010 19:37:27 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <randy@psg.com>) id 1PBIOa-000IpG-Da; Thu, 28 Oct 2010 02:39:16 +0000
Date: Thu, 28 Oct 2010 11:39:15 +0900
Message-ID: <m2eibb2g8c.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>
In-Reply-To: <C8EE54D5.10A40%victor.kuarsingh@gmail.com>
References: <660EFF7C-8621-4B74-B836-178594D71BE6@free.fr> <C8EE54D5.10A40%victor.kuarsingh@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Cc: v6ops mailing list <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2010 02:37:31 -0000

> The intent is not to use PMT as a "good IPv6" option, but rather as a
> "last resort IPv6 option" if needed.

none, i repeat _none_, of the non-native/dual deployments, 6to4, pmt,
6rd, teredo, ... are good ipv6 options.  they are hacks to get around
choosing not to deploy real ipv6.

the perceived quality of the various non-good hacks varies mainly by
environment and implementation.  but they are all hacks to get around
not deploying ipv6.

> many operators have commented on this list that the reality in our
> networks is that we cannot control all our CPE endpoints, and
> replacing them is many times out of our control.

i used the word "chooising" above carefully.  it is all a trade-off.
replacing cpe may be quite expensive, but one might choose to do it and
one might not.  i would not belabor this seemingly trivial point except
that it places an upper bound on my sympathy for non-depolyment and for
how grotty a hack i am willing to tolerate.

> I offer this question to the list, what "option" is available for the
> "non-upgraded" and "IPv4 only" endpoints? I will say that quoting a
> new technology like 6RD and native IPv6 are not options for the use
> case we have presented.  Ignoring these customers is also not an
> option.  We are in the business of helping customers even if they
> don't help themselves (to the extent possible).

and what does this have to do with ipv6 deployment and operation?

randy

From jhw@apple.com  Wed Oct 27 20:49:47 2010
Return-Path: <jhw@apple.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BE6D73A6814 for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 20:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SdeCCLRgBQnM for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 20:49:45 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id C0C833A6831 for <v6ops@ietf.org>; Wed, 27 Oct 2010 20:49:43 -0700 (PDT)
Received: from relay14.apple.com (relay14.apple.com [17.128.113.52]) by mail-out4.apple.com (Postfix) with ESMTP id F2336B88EB08 for <v6ops@ietf.org>; Wed, 27 Oct 2010 20:51:34 -0700 (PDT)
X-AuditID: 11807134-b7c05ae000002d5d-8e-4cc8f3463ea8
Received: from elliott.apple.com (elliott.apple.com [17.151.62.13]) by relay14.apple.com (Apple SCV relay) with SMTP id DA.E4.11613.643F8CC4; Wed, 27 Oct 2010 20:51:34 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from [172.16.1.7] (adit.conjury.org [75.101.54.88]) by elliott.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LAZ000CKEPY8F60@elliott.apple.com> for v6ops@ietf.org; Wed, 27 Oct 2010 20:51:34 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <C8EE54D5.10A40%victor.kuarsingh@gmail.com>
Date: Wed, 27 Oct 2010 20:51:33 -0700
Message-id: <8F908F17-8693-49FD-9824-D8F9F58AB77F@apple.com>
References: <C8EE54D5.10A40%victor.kuarsingh@gmail.com>
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2010 03:49:48 -0000

On Oct 27, 2010, at 19:14, Victor Kuarsingh wrote:
> 
> I offer this question to the list, what "option" is available for the "non-upgraded" and "IPv4 only" endpoints?

As mentioned in I-D.ietf-behave-v6v4-framework, the only remaining option available to you is RFC 2766.  It's been moved to historic status [RFC 4966] because it has its problems, but it would be better than 6to4-PMT, because it would not introduce NAT66 into otherwise apparently IPv6-native paths between the IPv6 subscriber network and the public IPv6 Internet.

> Would the group agree with this statement "we would rather provide no IPv6 at all rather then IPv6 based on 6to4-PMT"?

I would rather see NAT-PT deployed than 6to4-PMT.  I strongly believe that each and every deployment of 6to4-PMT will separately detract from the welfare of everyone in the Internet community.  If it's widely deployed, it would be an epic disaster for the IPv6 transition overall.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



From victor.kuarsingh@gmail.com  Wed Oct 27 20:54:44 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DDC913A680B for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 20:54:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.374
X-Spam-Level: 
X-Spam-Status: No, score=-2.374 tagged_above=-999 required=5 tests=[AWL=0.225,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BsXUp0Xk-5Jx for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 20:54:13 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id C39FD3A6836 for <v6ops@ietf.org>; Wed, 27 Oct 2010 20:54:12 -0700 (PDT)
Received: by vws3 with SMTP id 3so94884vws.31 for <v6ops@ietf.org>; Wed, 27 Oct 2010 20:56:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=/MwRqL0vI9SR0YUeOcDfKWqfY0eAtHGJAd+GLYoHmcs=; b=xoUaYDVzsiUwfPF56FuOxqQkBcTK3NylPbqmpfACPOeLSR+P86jZzbobDOPUUVglpc OQtIv8eFbzqhURVYOGaOZUEMswZx7Q6nd9BGztF9jn5trazBZXpGZVlXTOd5R2CHa5jX 77/tLmS835XZQ53ThVHLgqHG2diqlVHhwnGN8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=gUDRHhpxvbDbKhXEIWoOOy9SItiThgmt7T+S81LGnLw5yRPh34B2RxZ7dPpXoFWnzP NlZRp33CNZFWu69I7CbFVWcjHtDKD0Xr/tZi3F6IW47zoIGpS39vfIgOPujQtSGynGcD hVh0yrbHezw0GHIr6F0eRbnsF1ub5oRDQlZDQ=
Received: by 10.220.90.203 with SMTP id j11mr298668vcm.197.1288238163673; Wed, 27 Oct 2010 20:56:03 -0700 (PDT)
Received: from [192.168.100.149] ([67.224.83.162]) by mx.google.com with ESMTPS id p32sm370908vbl.5.2010.10.27.20.56.01 (version=SSLv3 cipher=RC4-MD5); Wed, 27 Oct 2010 20:56:03 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Wed, 27 Oct 2010 23:55:53 -0400
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: Randy Bush <randy@psg.com>
Message-ID: <C8EE6C89.10A45%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
Thread-Index: Act2VAQzkcprlQEnLUinRqowVxgRUw==
In-Reply-To: <m2eibb2g8c.wl%randy@psg.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: v6ops mailing list <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2010 03:54:45 -0000

>> The intent is not to use PMT as a "good IPv6" option, but rather as a
>> "last resort IPv6 option" if needed.
> 
> none, i repeat _none_, of the non-native/dual deployments, 6to4, pmt,
> 6rd, teredo, ... are good ipv6 options.  they are hacks to get around
> choosing not to deploy real ipv6.
> 
> the perceived quality of the various non-good hacks varies mainly by
> environment and implementation.  but they are all hacks to get around
> not deploying ipv6.

Agreed, PMT is yet another hack. I cannot argue that.  But a hack based on
some existing (deployed) functionality (I am not waiting for the mass market
to filter in this behavior based on hardware turnover and/or firmware
updates [considering many don't do this anyway])

> 
>> many operators have commented on this list that the reality in our
>> networks is that we cannot control all our CPE endpoints, and
>> replacing them is many times out of our control.
> 
> i used the word "chooising" above carefully.  it is all a trade-off.
> replacing cpe may be quite expensive, but one might choose to do it and
> one might not.  i would not belabor this seemingly trivial point except
> that it places an upper bound on my sympathy for non-depolyment and for
> how grotty a hack i am willing to tolerate.
> 
I think we will need to agree to disagree here.  I think suggesting that
operators are not choosing to deploy IPv6 by not supplying IPv6 gateways at
mass (where the normal case was customers bring their own gateways) is not a
true reflection of what is feasible in many cases.

I am not saying that some operations are not being lazy, but that is not my
case.  We are working hard at it.

>> I offer this question to the list, what "option" is available for the
>> "non-upgraded" and "IPv4 only" endpoints? I will say that quoting a
>> new technology like 6RD and native IPv6 are not options for the use
>> case we have presented.  Ignoring these customers is also not an
>> option.  We are in the business of helping customers even if they
>> don't help themselves (to the extent possible).
> 
> and what does this have to do with ipv6 deployment and operation?
> 
I would suggest that PMT, although another hack, is attempting to provide
some level of IPv6 connectivity, so it fits here.  6to4, although over IPv4,
is still IPv6 over the top.

Victor




From victor.kuarsingh@gmail.com  Wed Oct 27 21:09:03 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D05AA3A683F for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 21:09:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.374
X-Spam-Level: 
X-Spam-Status: No, score=-2.374 tagged_above=-999 required=5 tests=[AWL=0.225,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NxEtzFjsxQT0 for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 21:09:02 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id D25993A683C for <v6ops@ietf.org>; Wed, 27 Oct 2010 21:08:48 -0700 (PDT)
Received: by gya6 with SMTP id 6so1021056gya.31 for <v6ops@ietf.org>; Wed, 27 Oct 2010 21:10:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=MOMpsNJoaVvjlFCRXrzuYtjyR6FksKwEGFYHmnYR+mw=; b=ovwY0i0zXX1RV3TyKwA1oAW4qZMEzcILUsdEighTAD1HVnW9bqtaxmiSkBoChE+RF3 t5QX6x8npac/xtC0fellOuyhnmSjVnLarSzMnYxMfSjCQWjJK+9xODPrAp8CGSJpT0ZG 3pqp5lKqEXabNs0DLrTiZJg4FyB9UuC2IjaFs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=A6vNVCXi5rqyfTAEjCKXHUvcm2i4ZXlqpZnvaxSL7O/TT3MBfV0z+Q/4DRrV7xNxRh OPy+0OniJ9911jblcZoAlQ8tos5RPeHknuh0jnxU3jloHfGrc1+DnFC4XJzdbe7DyWXR sc5VPf8C5+jNQ/XV8/e+pxQBpD+ABCKbp8AyE=
Received: by 10.90.24.8 with SMTP id 8mr2045241agx.184.1288239039628; Wed, 27 Oct 2010 21:10:39 -0700 (PDT)
Received: from [192.168.100.149] ([67.224.83.162]) by mx.google.com with ESMTPS id m66sm410502yha.21.2010.10.27.21.10.37 (version=SSLv3 cipher=RC4-MD5); Wed, 27 Oct 2010 21:10:38 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Thu, 28 Oct 2010 00:10:30 -0400
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: james woodyatt <jhw@apple.com>
Message-ID: <C8EE6FF6.10A47%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] Reasons not to endorse NAT66/6to4
Thread-Index: Act2Vg7uyH2NwkP9oEO59S3fBDvEBQ==
In-Reply-To: <8F908F17-8693-49FD-9824-D8F9F58AB77F@apple.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2010 04:09:03 -0000

James,

> On Oct 27, 2010, at 19:14, Victor Kuarsingh wrote:
>> 
>> I offer this question to the list, what "option" is available for the
>> "non-upgraded" and "IPv4 only" endpoints?
> 
> As mentioned in I-D.ietf-behave-v6v4-framework, the only remaining option
> available to you is RFC 2766.  It's been moved to historic status [RFC 4966]
> because it has its problems, but it would be better than 6to4-PMT, because it
> would not introduce NAT66 into otherwise apparently IPv6-native paths between
> the IPv6 subscriber network and the public IPv6 Internet.

I was under the impression that part of the list of drawbacks to RFC2766 was
related to the IPv4 Network -> IPv6 Internet type flows (managing state, etc
- but I will re-read 4966).

Are you suggesting translating from IPv4 to IPv6 is better then IPv6 to
IPv6? (PT66/NAT66)  Both remove e2e transparency (so no gain here either
way).  Maybe I am off here, but I would have thought that in-family
translation beats cross-family translation.

> 
>> Would the group agree with this statement "we would rather provide no IPv6 at
>> all rather then IPv6 based on 6to4-PMT"?
> 
> I would rather see NAT-PT deployed than 6to4-PMT.  I strongly believe that
> each and every deployment of 6to4-PMT will separately detract from the welfare
> of everyone in the Internet community.  If it's widely deployed, it would be
> an epic disaster for the IPv6 transition overall.

"epic disaster" seems a bit harsh, perhaps testing and characterization
would better defined how good or bad this is.

I think one of your concerns here is that the use of PMT would potentially
inhibit IPv6 deployment if operators do this in place of working on IPv6,
but this is not the intent.  I think you give this option too much credit -
I don't think this would stop IPv6 deployments (opinion stated). I think it
would be used for what it's intended - last resort until operators can
influence the right change at the customer CPE/host.

If I got this right, it's more about possible actions of operations rather
then actually characteristics of the option (which as Remi noted have
fallbacks - which are duly noted and would require due diligence to
characterize)

Regards,

Victor





From remi.despres@free.fr  Thu Oct 28 01:08:14 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C4B1F3A6869 for <v6ops@core3.amsl.com>; Thu, 28 Oct 2010 01:08:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.247
X-Spam-Level: 
X-Spam-Status: No, score=-1.247 tagged_above=-999 required=5 tests=[AWL=0.102,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W9yDMTCzcigx for <v6ops@core3.amsl.com>; Thu, 28 Oct 2010 01:08:13 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.21]) by core3.amsl.com (Postfix) with ESMTP id B68CF3A67AC for <v6ops@ietf.org>; Thu, 28 Oct 2010 01:08:12 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2313.sfr.fr (SMTP Server) with ESMTP id B3234700008A; Thu, 28 Oct 2010 10:10:03 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2313.sfr.fr (SMTP Server) with ESMTP id DB2AE7000088; Thu, 28 Oct 2010 10:10:02 +0200 (CEST)
X-SFR-UUID: 20101028081002897.DB2AE7000088@msfrf2313.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <C8EE54D5.10A40%victor.kuarsingh@gmail.com>
Date: Thu, 28 Oct 2010 10:10:01 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1F2A8C2C-3875-4F1E-82E8-37DFACC37FDB@free.fr>
References: <C8EE54D5.10A40%victor.kuarsingh@gmail.com>
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>
X-Mailer: Apple Mail (2.1081)
Cc: Scott Beuker <Scott.Beuker@sjrb.ca>, v6ops v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2010 08:08:14 -0000

Le 28 oct. 2010 =E0 04:14, Victor Kuarsingh a =E9crit :

> Remi,
>=20
> I do appreciate the points from the group.  I agree, IPv6 native =3D
> good/best.  I also agree, where I cannot have Native IPv6, we will =
provide a
> more managed solution (like 6RD).

Note that a useful distinction here is between native-IPv6 ROUTING and =
native-IPv6 ADDRESSES.
6rd does provide native-IPv6 ADDRESSES to customers (unlike 5to4 and =
Teredo).
This is because users can't even detect that their IPv6 packets traverse =
some IPv4-only routing domain via tunnels. =20


> But unfortunately, neither of these options help operators where there =
are
> "unmanaged" devices which are not yet upgraded to support such =
technologies.
> Believe it or not, many persons do not ever upgrade their firmware in =
their
> home gateways)

Not only I do believe it, but its is precisely why, with Brian and =
Sheng, we propose 6a44 (www.ietf.org/id/draft-despres-softwire-6a44-01).
- It offers to native-IPv6 addresses to 6a44-capable hosts that are =
behind NAT44-CPEs.
- It is plug and play.
- Traffic between two hosts behind the same NAT44-CPE remains within =
their site.
- It can work even in sites that only get private IPv4 addresses of RFC =
1918.=20
 =20
> Operators need an option to help customers who have not yet replaced
> equipment which has a "current set" of features (and as noted, this =
often
> includes 6to4 default operation).

That's why current 6to4 users shouldn't lose the ability to be reached =
at their 6to4 address, including by hosts that have native-Ipv6 =
addresses and routes via 6to4 relays.
Adding a NAT66 to 6to4 relays breaks this ability.
This technical reality MUST NOT be ignored. =20

> ... But, many
> operators have commented on this list that the reality in our networks =
is
> that we cannot control all our CPE endpoints, and replacing them is =
many
> times out of our control.

Indeed, and 6a44 has been designed for them.
(We have to face that many existing CPEs don't support 6to4.)=20

> It appears that that a number of commenter's in this list would rather =
us
> (operators) not address this segment of the population, and just =
"hope" that
> IPv4 only will work for them

I noticed that too, and believe they don't understand the situation.

All my personal efforts, from 6rd to 6a44, and including opposition to =
endorsing the NAT66-6to4 combination, are to promote good user =
experience with IPv6.


> I offer this question to the list, what "option" is available for the
> "non-upgraded" and "IPv4 only" endpoints?

If neither the host not the CPE is upgraded, the host is left with =
IPv4-only and NAT44's, with their limitations.


> Would the group agree with this statement "we would rather provide no =
IPv6
> at all rather then IPv6 based on 6to4-PMT"?

That's a strange question because adding NAT66 to 6to4 doesn't increase =
the number of IPv6 addresses offered to customers.
It just modifies what a host can do with its IPv6 address:
(a) It ensures a return path for connections from 6to4 to native IPv6=20
(b) It breaks the possibility to be reachable at this IPv6 address.

It has to be faced that (b) would be a terrible step backward for 6to4 =
(and for IPv6 in general).
(See what James Woodyatt, among the well-known best friends of 6to4, =
says about it.) =20


> Constructive options welcome. =20


6a44 is a constructive option.
(Reactions to the proposal are most welcome.)

Destructive proposals are legitimate only as long as it isn't clear that =
they are destructive.
And it happens (unfortunately I agree) that adding NAT66 to 6to4 IS =
destructive=20


Regards,
RD

Red




> I am not trying to be difficult or
> belligerent, but rather looking for solutions to problems.
>=20
> Regards,
>=20
> Victor
>=20
>=20
>=20
> On 25/10/10 3:35 AM, "R=E9mi Despr=E9s" <remi.despres@free.fr> wrote:
>=20
>>=20
>> Le 23 oct. 2010 =E0 17:55, Victor Kuarsingh a =E9crit :
>>> ...
>>> Why would we depreciate something that works before all the viable
>>> alternatives (6RD, Native IPv6 and new things like 6a44) are still =
not out
>>> there in mass?  Why reduce that IPv6 glue space?
>>> ...
>>> My analogy to Internet usage for most is like "gas in the car".  =
Most people
>>> put gas in the card, turn the key and press the accelerator/break.  =
All the
>>> rest "just works".
>>=20
>>> Our mission (as operators) will be to make things "just
>>> work".
>>=20
>> Agreed, what is needed is what "just works".
>>=20
>> Now:
>> * Native IPv6 "just works"
>> 1. guaranteed e2e address transparency (OK for peer-to-peer)
>> 2. guaranteed connectivity
>> 3. ISP control of customer QoS
>> * 6to4 between two 6to4 addresses (without 6o4 relays) "just works":
>> 1. guaranteed e2e address transparency
>> 2. guaranteed connectivity
>> 3. ISP control of customer QoS (that of IPv4)
>> * 6to4 between a 6to4 address and a native-IPv6 address (with 2 6to4 =
relays)
>> "doesn't just work":
>> 1. (e2e address transparency still available)
>> 2. guaranteed connectivity is LOST
>> 3. ISP control of customer QoS is LOST
>>=20
>> If SOME ISPs would deploy 6to4-PMT, i.e. add NAT66's to 6to4 relays, =
6to4
>> would EVEN LESS "just work":
>> - For 6to4 customers of 6to4-PMT ISPs:
>> 1. e2e address transparency is LOST (peer-to-peer in Ipv6 is broken)
>> 2. guaranteed connectivity is still LOST  (depends on whether remote
>> native-IPv6 hosts access 6to4 relays)
>> 3. ISP control of customer QoS is still LOST (if remote native-IPv6 =
hosts
>> have access to 6to4 relays, it depends on which ones)
>> - For native IPv6 customers
>> 1. guaranteed e2e address transparency is LOST (remote native IPv6 =
addresses
>> may now be translated on their way)
>> 2. guaranteed connectivity with 6to4 addresses is still LOST (not all =
6to4
>> addresses are 6to4-PMT addresses)
>> 3. ISP control of customer QoS is still LOST (not all 6to4 addresses =
are
>> 6to4-PMT addresses)
>> - For 6to4 customers of ISPs that haven't 6to4-PMT:
>> 1. e2e address transparency is LOST (they may be talking to 6to4-PMT
>> customers)
>> 2. guaranteed connectivity is still LOST (they may have no access to =
a 6to4
>> relay)
>> 3. ISP control of customer QoS is LOST (if they access some 6to4 =
relays, it
>> depends on which ones)
>>=20
>> 6to4-PMT is simple, a quality, but, by combining two mechanisms that =
already
>> create more problems than they solve (6to4 relays and NAT66), it can =
only lead
>> to poor user experience in IPv6.
>>=20
>> The technical content of the above can be challenged if one finds =
that is has
>> mistakes.
>> But if it is right, the conclusion is that, to only keep solutions =
that "just
>> work", using the 6to4 anycast address in 6to4 customers should be =
turned off,
>> at least by default, and that where 6to4 relays are still in use, no =
NAT66 of
>> any form should be added to them.
>>=20
>>=20
>>> Plus, depreciating it would take time since it hard to force =
customers to
>>> upgrade OSs (although this has become automated in most OSs) and =
consumer
>>> equipment (many customers do not upgrade past store rev firmware).
>>=20
>> Deprecating a spec only means "if you have the choice, no longer do =
it".
>> In my understanding, deprecating 6to4-anycast in customer devices =
doesn't mean
>> that 6to4 relays that exist today should be dismantled.
>> As long as operators of these relays don't offer native IPv6, and see =
that
>> they still have users, they are perfectly entitled to maintain these =
relays
>> for these users.
>>=20
>>=20
>> To conclude, the proposal is that IETF:
>> - deprecates the use of the 6to4-relay anycast address in 6to4 =
routers
>> - explains why associating NAT66's with 6to4 relays should be avoided
>> This will contribute to make IPv6 something that "just works".
>>=20
>> Regards,
>> RD
>>=20
>>=20
>>>=20
>>> Just a thought.
>>>=20
>>> Regards,
>>>=20
>>> Victor
>>>=20
>>>=20
>>> On 23/10/10 5:20 AM, "Gert Doering" <gert@space.net> wrote:
>>>=20
>>>> Hi,
>>>>=20
>>>> On Sat, Oct 23, 2010 at 09:15:38AM +1300, Brian E Carpenter wrote:
>>>>> On 2010-10-23 08:04, Gert Doering wrote:
>>>>>=20
>>>>>> One approach to rework 3056 would be to completely deprecate the
>>>>>> 6to4-with-anycast model.
>>>>>=20
>>>>> That is to say, deprecate RFC 3068 and revert to the pure RFC 3056 =
model.
>>>>=20
>>>> Well, yes.  Sorry for mixing these RFCs.
>>>>=20
>>>>> Good idea. Could you push my toothpaste back into the tube, too, =
please ;-)
>>>>=20
>>>> Well, it's not like we haven't done this before.  A6/bitstring =
depreciation
>>>> comes to mind...
>>>>=20
>>>> Gert Doering
>>>>       -- NetMaster
>>>=20
>>>=20
>>> _______________________________________________
>>> v6ops mailing list
>>> v6ops@ietf.org
>>> https://www.ietf.org/mailman/listinfo/v6ops
>>=20
>>=20
>=20
>=20



From gvandeve@cisco.com  Thu Oct 28 01:39:03 2010
Return-Path: <gvandeve@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 947643A67AB for <v6ops@core3.amsl.com>; Thu, 28 Oct 2010 01:39:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.209
X-Spam-Level: 
X-Spam-Status: No, score=-10.209 tagged_above=-999 required=5 tests=[AWL=-0.210, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eZcV7ayEodfG for <v6ops@core3.amsl.com>; Thu, 28 Oct 2010 01:39:01 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 091A13A6873 for <v6ops@ietf.org>; Thu, 28 Oct 2010 01:39:00 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAPrTyEyrRN+J/2dsb2JhbAChRHGjApwphUgEjWE
X-IronPort-AV: E=Sophos;i="4.58,250,1286150400"; d="scan'208";a="208079867"
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-4.cisco.com with ESMTP; 28 Oct 2010 08:40:51 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id o9S8efkg001306; Thu, 28 Oct 2010 08:40:50 GMT
Received: from xmb-ams-101.cisco.com ([144.254.74.76]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 28 Oct 2010 10:40:49 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 28 Oct 2010 10:40:47 +0200
Message-ID: <4269EA985EACD24987D82DAE2FEC62E502786806@XMB-AMS-101.cisco.com>
In-Reply-To: <C8EE6FF6.10A47%victor.kuarsingh@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops] Reasons not to endorse NAT66/6to4
Thread-Index: Act2Vg7uyH2NwkP9oEO59S3fBDvEBQAJTjcw
References: <8F908F17-8693-49FD-9824-D8F9F58AB77F@apple.com> <C8EE6FF6.10A47%victor.kuarsingh@gmail.com>
From: "Gunter Van de Velde (gvandeve)" <gvandeve@cisco.com>
To: "Victor Kuarsingh" <victor.kuarsingh@gmail.com>, "james woodyatt" <jhw@apple.com>
X-OriginalArrivalTime: 28 Oct 2010 08:40:49.0620 (UTC) FILETIME=[D2949940:01CB767B]
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2010 08:39:03 -0000

In general, I prefer a managed service... I mostlikely have a SLA with
the provider and pay=20
for the service, so I expect acceptable quality in return.

If Billy-Bob, the couch potato can by that service access Internet
resources otherwise not available, then Billy-Bob is happy.
(because Billy-Bob does not care what is happening under the curtains...
neither for v4 and neither for v6 magic)

@James, I assume you meant NAT64 and not NAT-PT?

G/

-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
Of Victor Kuarsingh
Sent: Thursday, October 28, 2010 6:11 AM
To: james woodyatt
Cc: IPv6 Operations
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4

James,

> On Oct 27, 2010, at 19:14, Victor Kuarsingh wrote:
>>=20
>> I offer this question to the list, what "option" is available for the
>> "non-upgraded" and "IPv4 only" endpoints?
>=20
> As mentioned in I-D.ietf-behave-v6v4-framework, the only remaining
option
> available to you is RFC 2766.  It's been moved to historic status [RFC
4966]
> because it has its problems, but it would be better than 6to4-PMT,
because it
> would not introduce NAT66 into otherwise apparently IPv6-native paths
between
> the IPv6 subscriber network and the public IPv6 Internet.

I was under the impression that part of the list of drawbacks to RFC2766
was
related to the IPv4 Network -> IPv6 Internet type flows (managing state,
etc
- but I will re-read 4966).

Are you suggesting translating from IPv4 to IPv6 is better then IPv6 to
IPv6? (PT66/NAT66)  Both remove e2e transparency (so no gain here either
way).  Maybe I am off here, but I would have thought that in-family
translation beats cross-family translation.

>=20
>> Would the group agree with this statement "we would rather provide no
IPv6 at
>> all rather then IPv6 based on 6to4-PMT"?
>=20
> I would rather see NAT-PT deployed than 6to4-PMT.  I strongly believe
that
> each and every deployment of 6to4-PMT will separately detract from the
welfare
> of everyone in the Internet community.  If it's widely deployed, it
would be
> an epic disaster for the IPv6 transition overall.

"epic disaster" seems a bit harsh, perhaps testing and characterization
would better defined how good or bad this is.

I think one of your concerns here is that the use of PMT would
potentially
inhibit IPv6 deployment if operators do this in place of working on
IPv6,
but this is not the intent.  I think you give this option too much
credit -
I don't think this would stop IPv6 deployments (opinion stated). I think
it
would be used for what it's intended - last resort until operators can
influence the right change at the customer CPE/host.

If I got this right, it's more about possible actions of operations
rather
then actually characteristics of the option (which as Remi noted have
fallbacks - which are duly noted and would require due diligence to
characterize)

Regards,

Victor




_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

From marc.blanchet@viagenie.ca  Thu Oct 28 01:51:30 2010
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C43C3A6831 for <v6ops@core3.amsl.com>; Thu, 28 Oct 2010 01:51:30 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3KaXJ4BkN-7a for <v6ops@core3.amsl.com>; Thu, 28 Oct 2010 01:51:25 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id 29EAC3A6868 for <v6ops@ietf.org>; Thu, 28 Oct 2010 01:51:24 -0700 (PDT)
Received: from mbl.local (jazz.viagenie.ca [206.123.31.2]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 2189920D01 for <v6ops@ietf.org>; Thu, 28 Oct 2010 04:53:13 -0400 (EDT)
Message-ID: <4CC939F1.2050008@viagenie.ca>
Date: Thu, 28 Oct 2010 09:53:05 +0100
From: Marc Blanchet <marc.blanchet@viagenie.ca>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fr; rv:1.9.2.11) Gecko/20101013 Lightning/1.0b2 Thunderbird/3.1.5
MIME-Version: 1.0
To: v6ops@ietf.org
References: <8F908F17-8693-49FD-9824-D8F9F58AB77F@apple.com>	<C8EE6FF6.10A47%victor.kuarsingh@gmail.com> <4269EA985EACD24987D82DAE2FEC62E502786806@XMB-AMS-101.cisco.com>
In-Reply-To: <4269EA985EACD24987D82DAE2FEC62E502786806@XMB-AMS-101.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2010 08:51:30 -0000

My take on 6to4-PMT:
- not nice. a hack. (not our first hack, will not be the last one,  not 
the worst one, but you may have a different opinion)
- pretty short time lifetime (well, things live around much longer than 
usually thought of, but anyway: in the grand scheme of things, should be 
"short")
- I understand (and agree to some level) the reasons for deploying such 
schemes.
- if this is being implemented and deployed, then it would be good to be 
documented somewhere in an RFC.
- I have only one concern which has been raised before in one way or 
another: what is the real footprint of 6to4-enabled devices in broadband 
networks now and soon that is enough big to justify working on this scheme?
- So I suggest the following if-then-else:
  if the 6to4 footprint is enough "high", then work within IETF wg 
(behave?) to make an RFC, else get reviewers in this community and 
elsewhere to comment/improve the spec and send it to RFC editor for 
individual submission, experimental or informational track.

Marc.
-- 
=========
IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca
Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca
DTN news service: http://reeves.viagenie.ca
NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca


From remi.despres@free.fr  Thu Oct 28 05:19:29 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 063403A6879 for <v6ops@core3.amsl.com>; Thu, 28 Oct 2010 05:19:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.552
X-Spam-Level: 
X-Spam-Status: No, score=-1.552 tagged_above=-999 required=5 tests=[AWL=0.397,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4HHZU6f9qhBP for <v6ops@core3.amsl.com>; Thu, 28 Oct 2010 05:19:28 -0700 (PDT)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.82]) by core3.amsl.com (Postfix) with ESMTP id 051C33A684D for <v6ops@ietf.org>; Thu, 28 Oct 2010 05:19:28 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2409.sfr.fr (SMTP Server) with ESMTP id 4285F7000092; Thu, 28 Oct 2010 14:21:19 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2409.sfr.fr (SMTP Server) with ESMTP id ACA007000086; Thu, 28 Oct 2010 14:21:18 +0200 (CEST)
X-SFR-UUID: 20101028122118707.ACA007000086@msfrf2409.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <4CC939F1.2050008@viagenie.ca>
Date: Thu, 28 Oct 2010 14:21:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E6D00A2-9A5A-4A0C-AC97-B7081373FB27@free.fr>
References: <8F908F17-8693-49FD-9824-D8F9F58AB77F@apple.com>	<C8EE6FF6.10A47%victor.kuarsingh@gmail.com> <4269EA985EACD24987D82DAE2FEC62E502786806@XMB-AMS-101.cisco.com> <4CC939F1.2050008@viagenie.ca>
To: Marc Blanchet <marc.blanchet@viagenie.ca>
X-Mailer: Apple Mail (2.1081)
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2010 12:19:29 -0000

Le 28 oct. 2010 =E0 10:53, Marc Blanchet a =E9crit :

> My take on 6to4-PMT:
> - not nice. a hack. (not our first hack, will not be the last one,  =
not the worst one, but you may have a different opinion)

Couldn't you join James and myself to understand that 6t4-PMT does more =
harm to 6to4, and to IPv6 in general, than it improves it?

Once more:
6to4 users have today the ability to be reached at their 6to4 addresses, =
not only from other 6to4 addresses, but also from  native-Ipv6 addresses =
that have routes to any 6to4 relay.
Adding a NAT66 to a 6to4 relays breaks this ability for all users that =
depend on this relay.
This technical reality is destructive, and MUST NOT be ignored.


Putting  6rd in the same undifferentiated category as 6to4-PMT, although =
6rd permitted the largest deployment of native IPv6 addresses so far, =
with happy ISPs and happy customers, and without operational loose ends =
where it is applicable, doesn't contribute, IMHO, to promote =
availability of good quality IPv6.=20

Regards,
RD=20

=20



From Jean-Francois.TremblayING@videotron.com  Thu Oct 28 08:19:32 2010
Return-Path: <Jean-Francois.TremblayING@videotron.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ABC913A67DA; Thu, 28 Oct 2010 08:19:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[AWL=0.151,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RK0wb47Vwe-o; Thu, 28 Oct 2010 08:19:30 -0700 (PDT)
Received: from mx01.videotron.com (mx01.videotron.com [24.201.243.152]) by core3.amsl.com (Postfix) with ESMTP id EC6EB3A6893; Thu, 28 Oct 2010 08:19:29 -0700 (PDT)
In-Reply-To: <4CC939F1.2050008@viagenie.ca>
To: marc.blanchet@viagenie.ca
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006
Message-ID: <OF1B6E009F.72E9D181-ON852577CA.005249C7-852577CA.0054539D@videotron.com>
From: Jean-Francois.TremblayING@videotron.com
Date: Thu, 28 Oct 2010 11:21:07 -0400
X-MIMETrack: Serialize by Router on DOMMTL11/SRV/GVL(Release 7.0.2FP1|January 10, 2007) at 2010-10-28 11:21:11, Serialize complete at 2010-10-28 11:21:11
Content-Type: multipart/alternative; boundary="=_alternative 0054539C852577CA_="
Cc: v6ops@ietf.org, v6ops-bounces@ietf.org
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2010 15:19:32 -0000

Message en plusieurs parties au format MIME
--=_alternative 0054539C852577CA_=
Content-Type: text/plain; charset="US-ASCII"

Marc Blanchet wrote: 
> - I have only one concern which has been raised before in one way or 
> another: what is the real footprint of 6to4-enabled devices in broadband 

> networks now and soon that is enough big to justify working on this 
scheme?

Marc, 
See Erik Kline's answer from a few days ago (below). 0.1% is quite low, 
but that's still 1000 out of every 1 million ISP clients. Still a large 
amount for technical support to handle. But these customers will be
calling only if the 6to4 return path is sufficiently broken for 
them to feel the pain on the IPv6-enabled sites they go to. 

IMHO, only real life will tell if 6to4+NAT66 is really useful. That
will require a significant amount of IPv6 content to be available 
first. From an ISP point of view, it's merely a tool to be used if
that specific pain point becomes a problem. 

Erik Kline wrote: 
> I don't know if these numbers are relevant to anybody but me, but
> here's the latest:
> 
>     - of the clients in one of our experiments that connect to a
> dualstack hostname, 0.2% (up from 0.04% 2 years ago!) connect with
> native (or apparently native) IPv6, and an additional 0.1% connect
> with 6to4.

JF



My take on 6to4-PMT:
- not nice. a hack. (not our first hack, will not be the last one,  not 
the worst one, but you may have a different opinion)
- pretty short time lifetime (well, things live around much longer than 
usually thought of, but anyway: in the grand scheme of things, should be 
"short")
- I understand (and agree to some level) the reasons for deploying such 
schemes.
- if this is being implemented and deployed, then it would be good to be 
documented somewhere in an RFC.
- I have only one concern which has been raised before in one way or 
another: what is the real footprint of 6to4-enabled devices in broadband 
networks now and soon that is enough big to justify working on this 
scheme?
- So I suggest the following if-then-else:
  if the 6to4 footprint is enough "high", then work within IETF wg 
(behave?) to make an RFC, else get reviewers in this community and 
elsewhere to comment/improve the spec and send it to RFC editor for 
individual submission, experimental or informational track.

Marc.
-- 
=========
IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca
Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca
DTN news service: http://reeves.viagenie.ca
NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca

_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops


--=_alternative 0054539C852577CA_=
Content-Type: text/html; charset="US-ASCII"


<br><tt><font size=2>Marc Blanchet wrote: </font></tt>
<br><tt><font size=2>&gt; - I have only one concern which has been raised
before in one way or </font></tt>
<br><tt><font size=2>&gt; another: what is the real footprint of 6to4-enabled
devices in broadband </font></tt>
<br><tt><font size=2>&gt; networks now and soon that is enough big to justify
working on this scheme?</font></tt>
<br>
<br><tt><font size=2>Marc, </font></tt>
<br><tt><font size=2>See Erik Kline's answer from a few days ago (below).
0.1% is quite low, </font></tt>
<br><tt><font size=2>but that's still 1000 out of every 1 million ISP clients.
Still a large </font></tt>
<br><tt><font size=2>amount for technical support to handle. But these
customers will be</font></tt>
<br><tt><font size=2>calling only if the 6to4 return path is sufficiently
broken for </font></tt>
<br><tt><font size=2>them to feel the pain on the IPv6-enabled sites they
go to. </font></tt>
<br>
<br><tt><font size=2>IMHO, only real life will tell if 6to4+NAT66 is really
useful. That</font></tt>
<br><tt><font size=2>will require a significant amount of IPv6 content
to be available </font></tt>
<br><tt><font size=2>first. From an ISP point of view, it's merely a tool
to be used if</font></tt>
<br><tt><font size=2>that specific pain point becomes a problem. </font></tt>
<br>
<br><tt><font size=2>Erik Kline wrote: </font></tt>
<br><tt><font size=2>&gt; I don't know if these numbers are relevant to
anybody but me, but<br>
&gt; here's the latest:<br>
&gt; <br>
&gt; &nbsp; &nbsp; - of the clients in one of our experiments that connect
to a<br>
&gt; dualstack hostname, 0.2% (up from 0.04% 2 years ago!) connect with<br>
&gt; native (or apparently native) IPv6, and an additional 0.1% connect<br>
&gt; with 6to4.</font></tt><font size=2 face="sans-serif"><br>
</font>
<br><font size=2 face="Default Sans Serif">JF<br>
</font>
<br>
<br>
<br><tt><font size=2>My take on 6to4-PMT:<br>
- not nice. a hack. (not our first hack, will not be the last one, &nbsp;not
<br>
the worst one, but you may have a different opinion)<br>
- pretty short time lifetime (well, things live around much longer than
<br>
usually thought of, but anyway: in the grand scheme of things, should be
<br>
&quot;short&quot;)<br>
- I understand (and agree to some level) the reasons for deploying such
<br>
schemes.<br>
- if this is being implemented and deployed, then it would be good to be
<br>
documented somewhere in an RFC.<br>
- I have only one concern which has been raised before in one way or <br>
another: what is the real footprint of 6to4-enabled devices in broadband
<br>
networks now and soon that is enough big to justify working on this scheme?<br>
- So I suggest the following if-then-else:<br>
 &nbsp;if the 6to4 footprint is enough &quot;high&quot;, then work within
IETF wg <br>
(behave?) to make an RFC, else get reviewers in this community and <br>
elsewhere to comment/improve the spec and send it to RFC editor for <br>
individual submission, experimental or informational track.<br>
<br>
Marc.<br>
-- <br>
=========<br>
IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca<br>
Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca<br>
DTN news service: http://reeves.viagenie.ca<br>
NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca<br>
<br>
_______________________________________________<br>
v6ops mailing list<br>
v6ops@ietf.org<br>
https://www.ietf.org/mailman/listinfo/v6ops<br>
</font></tt>
<br>
--=_alternative 0054539C852577CA_=--

From wwwrun@rfc-editor.org  Wed Oct 27 20:08:12 2010
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2491C3A67FF for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 20:08:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.391
X-Spam-Level: 
X-Spam-Status: No, score=-102.391 tagged_above=-999 required=5 tests=[AWL=0.209, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mvjMVv89pyWl for <v6ops@core3.amsl.com>; Wed, 27 Oct 2010 20:08:11 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id EEBC03A67AC for <v6ops@ietf.org>; Wed, 27 Oct 2010 20:08:10 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4CBAFE06E0; Wed, 27 Oct 2010 20:10:02 -0700 (PDT)
To: brian.e.carpenter@gmail.com, shengjiang@huawei.com, dromasca@avaya.com, rbonica@juniper.net, fred.baker@cisco.com, joelja@bogus.com, kurtis@kurtis.pp.se
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20101028031002.4CBAFE06E0@rfc-editor.org>
Date: Wed, 27 Oct 2010 20:10:02 -0700 (PDT)
X-Mailman-Approved-At: Thu, 28 Oct 2010 08:32:19 -0700
Cc: v6ops@ietf.org, rfc-editor@rfc-editor.org
Subject: [v6ops] [Editorial Errata Reported] RFC6036 (2585)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2010 03:08:12 -0000

The following errata report has been submitted for RFC6036,
"Emerging Service Provider Scenarios for IPv6 Deployment".

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

--------------------------------------
Type: Editorial
Reported by: Brian Carpenter <brian.e.carpenter@gmail.com>

Section: 2.5

Original Text
-------------
   84% support or plan DNS Authentication, Authorization, Accounting,
   and Auditing (AAAA) queries over IPv6, and all but one of these
   include reverse DNS lookup for IPv6.

Corrected Text
--------------
   84% support or plan DNS AAAA queries over IPv6, and all but one of
   these include reverse DNS lookup for IPv6.


Notes
-----
AAAA is not an acronym in this context; it is an RR type.

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. 

--------------------------------------
RFC6036 (draft-ietf-v6ops-isp-scenarios-00)
--------------------------------------
Title               : Emerging Service Provider Scenarios for IPv6 Deployment
Publication Date    : October 2010
Author(s)           : B. Carpenter, S. Jiang
Category            : INFORMATIONAL
Source              : IPv6 Operations
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG

From marc.blanchet@viagenie.ca  Thu Oct 28 09:08:05 2010
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 369863A68EB for <v6ops@core3.amsl.com>; Thu, 28 Oct 2010 09:08: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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cxrlbo1zWmXP for <v6ops@core3.amsl.com>; Thu, 28 Oct 2010 09:08:04 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id BB7463A68DB for <v6ops@ietf.org>; Thu, 28 Oct 2010 09:08:03 -0700 (PDT)
Received: from mbl.local (jazz.viagenie.ca [206.123.31.2]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 0C21D20D1E; Thu, 28 Oct 2010 12:09:52 -0400 (EDT)
Message-ID: <4CC9A04B.9010702@viagenie.ca>
Date: Thu, 28 Oct 2010 17:09:47 +0100
From: Marc Blanchet <marc.blanchet@viagenie.ca>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fr; rv:1.9.2.11) Gecko/20101013 Lightning/1.0b2 Thunderbird/3.1.5
MIME-Version: 1.0
To: Jean-Francois.TremblayING@videotron.com
References: <OF1B6E009F.72E9D181-ON852577CA.005249C7-852577CA.0054539D@videotron.com>
In-Reply-To: <OF1B6E009F.72E9D181-ON852577CA.005249C7-852577CA.0054539D@videotron.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2010 16:08:05 -0000

Le 10-10-28 16:21, Jean-Francois.TremblayING@videotron.com a écrit :
>
> Marc Blanchet wrote:
>  > - I have only one concern which has been raised before in one way or
>  > another: what is the real footprint of 6to4-enabled devices in broadband
>  > networks now and soon that is enough big to justify working on this
> scheme?
>
> Marc,
> See Erik Kline's answer from a few days ago (below).

I saw it. I was responding in the generic way and gives others to 
document their findings.

> 0.1% is quite low,
> but that's still 1000 out of every 1 million ISP clients. Still a large
> amount for technical support to handle. But these customers will be
> calling only if the 6to4 return path is sufficiently broken for
> them to feel the pain on the IPv6-enabled sites they go to.
>
> IMHO, only real life will tell if 6to4+NAT66 is really useful. That
> will require a significant amount of IPv6 content to be available
> first.

well, an important content provider already is v6 enabled... for some 
providers, this single content provider generates a significant part of 
their trafic...

> From an ISP point of view, it's merely a tool to be used if
> that specific pain point becomes a problem.

well, from what you wrote, it looks like an independent track 
experimental RFC is probably what you need.

Marc.

>
> Erik Kline wrote:
>  > I don't know if these numbers are relevant to anybody but me, but
>  > here's the latest:
>  >
>  > - of the clients in one of our experiments that connect to a
>  > dualstack hostname, 0.2% (up from 0.04% 2 years ago!) connect with
>  > native (or apparently native) IPv6, and an additional 0.1% connect
>  > with 6to4.
>
> JF
>
>
>
> My take on 6to4-PMT:
> - not nice. a hack. (not our first hack, will not be the last one, not
> the worst one, but you may have a different opinion)
> - pretty short time lifetime (well, things live around much longer than
> usually thought of, but anyway: in the grand scheme of things, should be
> "short")
> - I understand (and agree to some level) the reasons for deploying such
> schemes.
> - if this is being implemented and deployed, then it would be good to be
> documented somewhere in an RFC.
> - I have only one concern which has been raised before in one way or
> another: what is the real footprint of 6to4-enabled devices in broadband
> networks now and soon that is enough big to justify working on this scheme?
> - So I suggest the following if-then-else:
> if the 6to4 footprint is enough "high", then work within IETF wg
> (behave?) to make an RFC, else get reviewers in this community and
> elsewhere to comment/improve the spec and send it to RFC editor for
> individual submission, experimental or informational track.
>
> Marc.
> --
> =========
> IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca
> Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca
> DTN news service: http://reeves.viagenie.ca
> NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>


-- 
=========
IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca
Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca
DTN news service: http://reeves.viagenie.ca
NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca


From Jean-Francois.TremblayING@videotron.com  Thu Oct 28 09:25:21 2010
Return-Path: <Jean-Francois.TremblayING@videotron.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 02CCE3A6834 for <v6ops@core3.amsl.com>; Thu, 28 Oct 2010 09:25:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.168
X-Spam-Level: 
X-Spam-Status: No, score=-2.168 tagged_above=-999 required=5 tests=[AWL=0.430,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h4YCAR8UL2Z2 for <v6ops@core3.amsl.com>; Thu, 28 Oct 2010 09:25:20 -0700 (PDT)
Received: from mx01.videotron.com (mx01.videotron.com [24.201.243.152]) by core3.amsl.com (Postfix) with ESMTP id 113793A67F2 for <v6ops@ietf.org>; Thu, 28 Oct 2010 09:25:19 -0700 (PDT)
In-Reply-To: <4CC9A04B.9010702@viagenie.ca>
To: marc.blanchet@viagenie.ca
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006
Message-ID: <OF4CC3DD90.9363337F-ON852577CA.00599EC4-852577CA.005A5D37@videotron.com>
From: Jean-Francois.TremblayING@videotron.com
Date: Thu, 28 Oct 2010 12:27:04 -0400
X-MIMETrack: Serialize by Router on DOMMTL11/SRV/GVL(Release 7.0.2FP1|January 10, 2007) at 2010-10-28 12:27:01, Serialize complete at 2010-10-28 12:27:01
Content-Type: multipart/alternative; boundary="=_alternative 005A5D37852577CA_="
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2010 16:25:21 -0000

Message en plusieurs parties au format MIME
--=_alternative 005A5D37852577CA_=
Content-Type: text/plain; charset="US-ASCII"

>> IMHO, only real life will tell if 6to4+NAT66 is really useful. That
>> will require a significant amount of IPv6 content to be available
>> first.
>
> well, an important content provider already is v6 enabled... for some 
> providers, this single content provider generates a significant part of 
> their trafic...

Available IPv6 content == AAAA sent by default, no strings attached

I believe the content provider you are referring to does not fall into
that category, although I admire their efforts to figure out the 
operational issues related to IPv6 deployment. 

JF



--=_alternative 005A5D37852577CA_=
Content-Type: text/html; charset="US-ASCII"


<br>
<br>
<br><tt><font size=2>&gt;&gt; IMHO, only real life will tell if 6to4+NAT66
is really useful. That<br>
&gt;&gt; will require a significant amount of IPv6 content to be available<br>
&gt;&gt; first.<br>
&gt;<br>
&gt; well, an important content provider already is v6 enabled... for some
<br>
&gt; providers, this single content provider generates a significant part
of <br>
&gt; their trafic...<br>
</font></tt>
<br><tt><font size=2>Available IPv6 content == AAAA sent by default, no
strings attached</font></tt>
<br>
<br><tt><font size=2>I believe the content provider you are referring to
does not fall into</font></tt>
<br><tt><font size=2>that category, although I admire their efforts to
figure out the </font></tt>
<br><tt><font size=2>operational issues related to IPv6 deployment. </font></tt>
<br><tt><font size=2><br>
JF</font></tt>
<br>
<br>
<br>
--=_alternative 005A5D37852577CA_=--

From ek@google.com  Thu Oct 28 09:53:56 2010
Return-Path: <ek@google.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 899AB3A69AC for <v6ops@core3.amsl.com>; Thu, 28 Oct 2010 09:53:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.916
X-Spam-Level: 
X-Spam-Status: No, score=-107.916 tagged_above=-999 required=5 tests=[AWL=2.060, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dMvD8Wm7MTnU for <v6ops@core3.amsl.com>; Thu, 28 Oct 2010 09:53:55 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [74.125.121.35]) by core3.amsl.com (Postfix) with ESMTP id 24D1B3A6955 for <v6ops@ietf.org>; Thu, 28 Oct 2010 09:53:54 -0700 (PDT)
Received: from hpaq1.eem.corp.google.com (hpaq1.eem.corp.google.com [172.25.149.1]) by smtp-out.google.com with ESMTP id o9SGtgNU015271 for <v6ops@ietf.org>; Thu, 28 Oct 2010 09:55:46 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1288284946; bh=xXn24h1JCUWfSS8aIV0LoTNd2mw=; h=MIME-Version:In-Reply-To:References:Date:Message-ID:Subject:From: To:Cc:Content-Type; b=xPKGot0vB4FLOiJ5L/cloU7N1Xmw1Ru4KJhp4YX6QVR7MJSVdnvuvDEkHkfCYBIL5 dsuwSSA93LQym7UaVp/PA==
Received: from qwk4 (qwk4.prod.google.com [10.241.195.132]) by hpaq1.eem.corp.google.com with ESMTP id o9SGnvpV007322 for <v6ops@ietf.org>; Thu, 28 Oct 2010 09:49:57 -0700
Received: by qwk4 with SMTP id 4so2172822qwk.9 for <v6ops@ietf.org>; Thu, 28 Oct 2010 09:49:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=vF+mD6ahSRXcOw/8jfsibpGzvHbC+W3tcCn/19QHAJA=; b=xwxNKX6ccVrazkmN7/oU7t6s5S8in2gFDL4whDrlmN6QUf1XRTCaM0WWRsE/kJMulJ aoLHvJjaDI81eYA5hmwg==
DomainKey-Signature: a=rsa-sha1; c=nofws; d=google.com; s=beta; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=cPhLZXvSIGxX2jEXkTFFXagBK+pxXwbkEIkdZF+BsHKlRvdKHWUJlX64nzlmohhBEn TJtlqZIgCjpcuakeWMcA==
MIME-Version: 1.0
Received: by 10.229.248.79 with SMTP id mf15mr10466445qcb.181.1288284595785; Thu, 28 Oct 2010 09:49:55 -0700 (PDT)
Received: by 10.229.78.228 with HTTP; Thu, 28 Oct 2010 09:49:55 -0700 (PDT)
In-Reply-To: <C8EE6FF6.10A47%victor.kuarsingh@gmail.com>
References: <8F908F17-8693-49FD-9824-D8F9F58AB77F@apple.com> <C8EE6FF6.10A47%victor.kuarsingh@gmail.com>
Date: Thu, 28 Oct 2010 09:49:55 -0700
Message-ID: <AANLkTikw_nbX483tiYuKnkSYpMJrjsExOCObU9qwq2cs@mail.gmail.com>
From: Erik Kline <ek@google.com>
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>
Content-Type: multipart/alternative; boundary=0016e64ccc6ab391d70493b02145
X-System-Of-Record: true
Cc: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2010 16:53:56 -0000

--0016e64ccc6ab391d70493b02145
Content-Type: text/plain; charset=UTF-8

>
> Are you suggesting translating from IPv4 to IPv6 is better then IPv6 to
> IPv6? (PT66/NAT66)  Both remove e2e transparency (so no gain here either
> way).  Maybe I am off here, but I would have thought that in-family
> translation beats cross-family translation.


IMHO nothing is worth enshrining this as a "valid use case" for NAT66.
 You're inviting a devil in to your house for tea and cake, and it may not
leave when you ask.  That there are still architectural/design flaws for
which NAT66 may ultimately be necessary I would be willing to admit, if only
for the sake of discussion.  But not this.  6to4 is one third today what it
was 2 years ago.  Let it pass in peace.

NATing from IPv4 to IPv6 for your customers leaves NAT a part of the IPv4
leaf network/administrative domain, and doesn't carry that practice forward
into IPv6.

As  (I believe) Albert Einstein said, "We can't solve problems by using the
same kind of thinking we used when we created them."  [Apologies if I'm
mistaken.]

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

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Are you suggesti=
ng translating from IPv4 to IPv6 is better then IPv6 to<br>
IPv6? (PT66/NAT66) =C2=A0Both remove e2e transparency (so no gain here eith=
er<br>
way). =C2=A0Maybe I am off here, but I would have thought that in-family<br=
>
translation beats cross-family translation.</blockquote><div><br></div><div=
>IMHO nothing is worth enshrining this as a &quot;valid use case&quot; for =
NAT66. =C2=A0You&#39;re inviting a devil in to your house for tea and cake,=
 and it may not leave when you ask. =C2=A0That there are still architectura=
l/design flaws for which NAT66 may ultimately be necessary I would be willi=
ng to admit, if only for the sake of discussion. =C2=A0But not this. =C2=A0=
6to4 is one third today what it was 2 years ago. =C2=A0Let it pass in peace=
.</div>
<div><br></div><div>NATing from IPv4 to IPv6 for your customers leaves NAT =
a part of the IPv4 leaf network/administrative domain, and doesn&#39;t carr=
y that practice forward into IPv6.</div><div><br></div><div><div>As=C2=A0=
=C2=A0(I believe)=C2=A0Albert Einstein said, &quot;We can&#39;t solve probl=
ems by using the same kind of thinking we used when we created them.&quot; =
=C2=A0[Apologies if I&#39;m mistaken.]</div>
</div><meta http-equiv=3D"content-type" content=3D"text/html; charset=3Dutf=
-8"></div>

--0016e64ccc6ab391d70493b02145--

From cb.list6@gmail.com  Thu Oct 28 09:55:25 2010
Return-Path: <cb.list6@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1DFF83A69C5; Thu, 28 Oct 2010 09:55:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.864
X-Spam-Level: 
X-Spam-Status: No, score=-1.864 tagged_above=-999 required=5 tests=[AWL=0.135,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xLN-Ow6Lk1Nk; Thu, 28 Oct 2010 09:55:22 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id EA4AC3A69B7; Thu, 28 Oct 2010 09:55:21 -0700 (PDT)
Received: by qwb7 with SMTP id 7so2242684qwb.31 for <multiple recipients>; Thu, 28 Oct 2010 09:57:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=NSRuOuND6qeRsnRxSH9tMgR84apzIxbvrKOquc46dC8=; b=HJW+m7sX3c/Wm0kFFuE0ECp9IVd95FDSFI8rUptPDvWQpd3WnfZJr47FlzgTzQnV8w iFSXqSiCbp3+CGgTW7uZKdCWg9C+QK60gpUQ7+jQKZB1PRTXJ/Y2ryBYrPWdCXpHZjGg sWtDwvOyKFa67BuvwL5bsD/dnOYL8lXpe9p5U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=SVQoTW0D457CmsPoVLtRMrGF7QCvIuOVTiN9y8Qx5TcsyCjbFNUIAJ+n99LAztyz+U 99Cmh+VOV4IXY/KZA4DnJSgNbUTP64x471AVLKE/F8I6SKY8VW0mrQafigPQVOt/eE/f 9mEqYuNGxk7NoZm8Csza4c2Wmef5FL0Ol/ybQ=
MIME-Version: 1.0
Received: by 10.224.89.4 with SMTP id c4mr4764177qam.69.1288285032892; Thu, 28 Oct 2010 09:57:12 -0700 (PDT)
Received: by 10.229.245.201 with HTTP; Thu, 28 Oct 2010 09:57:12 -0700 (PDT)
In-Reply-To: <OF1B6E009F.72E9D181-ON852577CA.005249C7-852577CA.0054539D@videotron.com>
References: <4CC939F1.2050008@viagenie.ca> <OF1B6E009F.72E9D181-ON852577CA.005249C7-852577CA.0054539D@videotron.com>
Date: Thu, 28 Oct 2010 09:57:12 -0700
Message-ID: <AANLkTik9sGnyAH4JtDq673zm6h7OfJPaOz0ZsZQOpNXj@mail.gmail.com>
From: Cameron Byrne <cb.list6@gmail.com>
To: Jean-Francois.TremblayING@videotron.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: v6ops@ietf.org, v6ops-bounces@ietf.org
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2010 16:55:25 -0000

On Thu, Oct 28, 2010 at 8:21 AM,
<Jean-Francois.TremblayING@videotron.com> wrote:
>
> Marc Blanchet wrote:
>> - I have only one concern which has been raised before in one way or
>> another: what is the real footprint of 6to4-enabled devices in broadband
>> networks now and soon that is enough big to justify working on this
>> scheme?
>
> Marc,
> See Erik Kline's answer from a few days ago (below). 0.1% is quite low,
> but that's still 1000 out of every 1 million ISP clients. Still a large
> amount for technical support to handle. But these customers will be
> calling only if the 6to4 return path is sufficiently broken for
> them to feel the pain on the IPv6-enabled sites they go to.
>

I believe most of the brokenness has to do with in-home networks or
host configurations.

PMT will not fix broken 6to4, if i understand it right, it only
improves latency performance.

So, with or without PMT, 0.1% will still be broken  ... assuming 0.1%
brokenness is not the result of latency, if i understand all this
correctly.



> IMHO, only real life will tell if 6to4+NAT66 is really useful. That
> will require a significant amount of IPv6 content to be available

IPv6-only content, right? Because dual stack content with use IPv4.  I
personally don't think there will be such a thing a real IPv6-only
content that is meaningful to more than 1% of your subscribers,
hopefully those are not the broken 1%.  Maybe real IPv6-only p2p or
something like that.

> first. From an ISP point of view, it's merely a tool to be used if
> that specific pain point becomes a problem.
>

Great.  If you think there is value, you don't need the IETF's
permission, right?

Cameron

> Erik Kline wrote:
>> I don't know if these numbers are relevant to anybody but me, but
>> here's the latest:
>>
>> =A0 =A0 - of the clients in one of our experiments that connect to a
>> dualstack hostname, 0.2% (up from 0.04% 2 years ago!) connect with
>> native (or apparently native) IPv6, and an additional 0.1% connect
>> with 6to4.
>
> JF
>
>
>
> My take on 6to4-PMT:
> - not nice. a hack. (not our first hack, will not be the last one, =A0not
> the worst one, but you may have a different opinion)
> - pretty short time lifetime (well, things live around much longer than
> usually thought of, but anyway: in the grand scheme of things, should be
> "short")
> - I understand (and agree to some level) the reasons for deploying such
> schemes.
> - if this is being implemented and deployed, then it would be good to be
> documented somewhere in an RFC.
> - I have only one concern which has been raised before in one way or
> another: what is the real footprint of 6to4-enabled devices in broadband
> networks now and soon that is enough big to justify working on this schem=
e?
> - So I suggest the following if-then-else:
> =A0if the 6to4 footprint is enough "high", then work within IETF wg
> (behave?) to make an RFC, else get reviewers in this community and
> elsewhere to comment/improve the spec and send it to RFC editor for
> individual submission, experimental or informational track.
>
> Marc.
> --
> =3D=3D=3D=3D=3D=3D=3D=3D=3D
> IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca
> Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca
> DTN news service: http://reeves.viagenie.ca
> NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>
>

From Jean-Francois.TremblayING@videotron.com  Thu Oct 28 10:14:46 2010
Return-Path: <Jean-Francois.TremblayING@videotron.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BA99A3A677C; Thu, 28 Oct 2010 10:14:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.222
X-Spam-Level: 
X-Spam-Status: No, score=-2.222 tagged_above=-999 required=5 tests=[AWL=0.376,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jkSB1LfLDdMh; Thu, 28 Oct 2010 10:14:45 -0700 (PDT)
Received: from mx02.videotron.com (mx02.videotron.com [24.201.243.151]) by core3.amsl.com (Postfix) with ESMTP id 9444C3A67F2; Thu, 28 Oct 2010 10:14:45 -0700 (PDT)
In-Reply-To: <AANLkTik9sGnyAH4JtDq673zm6h7OfJPaOz0ZsZQOpNXj@mail.gmail.com>
To: cb.list6@gmail.com
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006
Message-ID: <OFD019B22D.84F4B458-ON852577CA.005DA950-852577CA.005EE3A0@videotron.com>
From: Jean-Francois.TremblayING@videotron.com
Date: Thu, 28 Oct 2010 13:16:30 -0400
X-MIMETrack: Serialize by Router on DOMMTL11/SRV/GVL(Release 7.0.2FP1|January 10, 2007) at 2010-10-28 13:16:27, Serialize complete at 2010-10-28 13:16:27
Content-Type: multipart/alternative; boundary="=_alternative 005EE39F852577CA_="
Cc: v6ops@ietf.org, v6ops-bounces@ietf.org
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2010 17:14:46 -0000

Message en plusieurs parties au format MIME
--=_alternative 005EE39F852577CA_=
Content-Type: text/plain; charset="US-ASCII"

> PMT will not fix broken 6to4, if i understand it right, it only
> improves latency performance.
> 
> So, with or without PMT, 0.1% will still be broken  ... assuming 0.1%
> brokenness is not the result of latency, if i understand all this
> correctly.

PMT improves return path routing, which affects latency, yes. 
Brokeness is not caused by latency but by broken 6to4 return 
reachability (the first is an effect, the second is the root cause). 
In this regard, PMT improving return routability does improve 6to4 
brokeness. Victor's and Yiu's draft is only a short-term solution 
to this problem, nothing more. 

>> IMHO, only real life will tell if 6to4+NAT66 is really useful. That
>> will require a significant amount of IPv6 content to be available
> IPv6-only content, right? Because dual stack content with use IPv4.  I
> personally don't think there will be such a thing a real IPv6-only
> content that is meaningful to more than 1% of your subscribers,
> hopefully those are not the broken 1%.  Maybe real IPv6-only p2p or
> something like that.

I didn't mention IPv6-only content. I'm using Erik's number of 0.1%
of IPv6 users still using 6to4 in priority over IPv4. If that gets 
fixed in OS implementations by the time significant content is over v6, 
then there's isn't a problem to solve anymore. And we all go home happy. 

>> first. From an ISP point of view, it's merely a tool to be used if
>> that specific pain point becomes a problem.
>
> Great.  If you think there is value, you don't need the IETF's
> permission, right?

Not all vendors implement procotols without an RFC (or at least a 
draft to give them guidance). 

JF


--=_alternative 005EE39F852577CA_=
Content-Type: text/html; charset="US-ASCII"


<br>
<br><tt><font size=2><br>
&gt; PMT will not fix broken 6to4, if i understand it right, it only<br>
&gt; improves latency performance.<br>
&gt; <br>
&gt; So, with or without PMT, 0.1% will still be broken &nbsp;... assuming
0.1%<br>
&gt; brokenness is not the result of latency, if i understand all this<br>
&gt; correctly.<br>
<br>
PMT improves return path routing, which affects latency, yes. </font></tt>
<br><tt><font size=2>Brokeness is not caused by latency but by broken 6to4
return </font></tt>
<br><tt><font size=2>reachability (the first is an effect, the second is
the root cause). </font></tt>
<br><tt><font size=2>In this regard, PMT improving return routability does
improve 6to4 </font></tt>
<br><tt><font size=2>brokeness. Victor's and Yiu's draft is only a short-term
solution </font></tt>
<br><tt><font size=2>to this problem, nothing more. &nbsp;<br>
<br>
&gt;&gt; IMHO, only real life will tell if 6to4+NAT66 is really useful.
That<br>
&gt;&gt; will require a significant amount of IPv6 content to be available<br>
&gt; IPv6-only content, right? Because dual stack content with use IPv4.
&nbsp;I<br>
&gt; personally don't think there will be such a thing a real IPv6-only<br>
&gt; content that is meaningful to more than 1% of your subscribers,<br>
&gt; hopefully those are not the broken 1%. &nbsp;Maybe real IPv6-only
p2p or<br>
&gt; something like that.<br>
</font></tt>
<br><tt><font size=2>I didn't mention IPv6-only content. I'm using Erik's
number of 0.1%</font></tt>
<br><tt><font size=2>of IPv6 users still using 6to4 in priority over IPv4.
If that gets </font></tt>
<br><tt><font size=2>fixed in OS implementations by the time significant
content is over v6, </font></tt>
<br><tt><font size=2>then there's isn't a problem to solve anymore. And
we all go home happy. </font></tt>
<br><tt><font size=2><br>
&gt;&gt; first. From an ISP point of view, it's merely a tool to be used
if<br>
&gt;&gt; that specific pain point becomes a problem.<br>
&gt;<br>
&gt; Great. &nbsp;If you think there is value, you don't need the IETF's<br>
&gt; permission, right?<br>
</font></tt>
<br><tt><font size=2>Not all vendors implement procotols without an RFC
(or at least a </font></tt>
<br><tt><font size=2>draft to give them guidance). </font></tt>
<br>
<br><tt><font size=2>JF<br>
</font></tt>
<br>
--=_alternative 005EE39F852577CA_=--

From marc.blanchet@viagenie.ca  Thu Oct 28 15:42:17 2010
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 547773A67DB for <v6ops@core3.amsl.com>; Thu, 28 Oct 2010 15:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4LZS3YqqGbn9 for <v6ops@core3.amsl.com>; Thu, 28 Oct 2010 15:42:16 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id B928E3A6778 for <v6ops@ietf.org>; Thu, 28 Oct 2010 15:42:15 -0700 (PDT)
Received: from mbl.local (62-50-199-254.client.stsn.net [62.50.199.254]) by jazz.viagenie.ca (Postfix) with ESMTPSA id A00F720D1E; Thu, 28 Oct 2010 18:44:07 -0400 (EDT)
Message-ID: <4CC9FCB6.8090207@viagenie.ca>
Date: Thu, 28 Oct 2010 23:44:06 +0100
From: Marc Blanchet <marc.blanchet@viagenie.ca>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fr; rv:1.9.2.11) Gecko/20101013 Lightning/1.0b2 Thunderbird/3.1.5
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
References: <8F908F17-8693-49FD-9824-D8F9F58AB77F@apple.com>	<C8EE6FF6.10A47%victor.kuarsingh@gmail.com> <4269EA985EACD24987D82DAE2FEC62E502786806@XMB-AMS-101.cisco.com> <4CC939F1.2050008@viagenie.ca> <6E6D00A2-9A5A-4A0C-AC97-B7081373FB27@free.fr>
In-Reply-To: <6E6D00A2-9A5A-4A0C-AC97-B7081373FB27@free.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2010 22:42:17 -0000

Le 10-10-28 13:21, Rémi Després a écrit :
>
> Le 28 oct. 2010 à 10:53, Marc Blanchet a écrit :
>
>> My take on 6to4-PMT:
>> - not nice. a hack. (not our first hack, will not be the last one,  not the worst one, but you may have a different opinion)
>
> Couldn't you join James and myself to understand that 6t4-PMT does more harm to 6to4, and to IPv6 in general, than it improves it?
>
> Once more:
> 6to4 users have today the ability to be reached at their 6to4 addresses, not only from other 6to4 addresses, but also from  native-Ipv6 addresses that have routes to any 6to4 relay.
> Adding a NAT66 to a 6to4 relays breaks this ability for all users that depend on this relay.
> This technical reality is destructive, and MUST NOT be ignored.
>

well, what I wrote is a proposal going forward:
- either there is a clear demonstration of a "good" number of 6to4 devices,
- if not, I suggested authors to go to the RFC-editor individual submission.

I think that was a constructive suggestion and fair.

>
> Putting  6rd in the same undifferentiated category as 6to4-PMT,

I did not. There was no "6rd" in the email I sent.

although 6rd permitted the largest deployment of native IPv6 addresses 
so far, with happy ISPs and happy customers, and without operational 
loose ends where it is applicable, doesn't contribute, IMHO, to promote 
availability of good quality IPv6.

>

Marc.

> Regards,
> RD
>
>


-- 
=========
IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca
Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca
DTN news service: http://reeves.viagenie.ca
NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca


From alh-ietf@tndh.net  Thu Oct 28 15:49:50 2010
Return-Path: <alh-ietf@tndh.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 893373A6767 for <v6ops@core3.amsl.com>; Thu, 28 Oct 2010 15:49:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.393
X-Spam-Level: *
X-Spam-Status: No, score=1.393 tagged_above=-999 required=5 tests=[AWL=0.372,  BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, FH_HOST_EQ_D_D_D_D=0.765,  HOST_EQ_STATICB=1.372, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R60ZyEK9-n80 for <v6ops@core3.amsl.com>; Thu, 28 Oct 2010 15:49:49 -0700 (PDT)
Received: from tndh.net (static-66-15-163-216.bdsl.verizon.net [66.15.163.216]) by core3.amsl.com (Postfix) with ESMTP id 316763A659C for <v6ops@ietf.org>; Thu, 28 Oct 2010 15:49:49 -0700 (PDT)
X-AuthUser: alh-ietf@tndh.net
Received: from ahainW7 ([192.168.123.15]:55194) by tndh.net with [XMail 1.27 ESMTP Server] id <S18C2265> for <v6ops@ietf.org> from <alh-ietf@tndh.net>; Thu, 28 Oct 2010 15:51:33 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Erik Kline'" <ek@google.com>, "'Victor Kuarsingh'" <victor.kuarsingh@gmail.com>
References: <8F908F17-8693-49FD-9824-D8F9F58AB77F@apple.com>	<C8EE6FF6.10A47%victor.kuarsingh@gmail.com> <AANLkTikw_nbX483tiYuKnkSYpMJrjsExOCObU9qwq2cs@mail.gmail.com>
In-Reply-To: <AANLkTikw_nbX483tiYuKnkSYpMJrjsExOCObU9qwq2cs@mail.gmail.com>
Date: Thu, 28 Oct 2010 15:51:32 -0700
Message-ID: <092801cb76f2$ac3838c0$04a8aa40$@net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0929_01CB76B7.FFD960C0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Act2wRHTIhngK9tjSQuJLXN5RSHtHgALIyfA
Content-Language: en-us
Cc: 'IPv6 Operations' <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2010 22:49:50 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0929_01CB76B7.FFD960C0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

I have to agree with Erik here. For the number of people that would have =
a significant enough customer base using 6to4 that they might consider =
PMT, the world would be MUCH better off with a handful of > /16 =
announcements in BGP, than having to deal with the NAT66 nonsense =
forever. Shortsighted hacks that bring along dangerous baggage MUST NOT =
be standardized.=20

=20

Do whatever you are going to do to support your customers, but =
don=E2=80=99t expect the world to standardize your model.=20

=20

Tony

=20

=20

From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf =
Of Erik Kline
Sent: Thursday, October 28, 2010 9:50 AM
To: Victor Kuarsingh
Cc: IPv6 Operations
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4

=20

Are you suggesting translating from IPv4 to IPv6 is better then IPv6 to
IPv6? (PT66/NAT66)  Both remove e2e transparency (so no gain here either
way).  Maybe I am off here, but I would have thought that in-family
translation beats cross-family translation.

=20

IMHO nothing is worth enshrining this as a "valid use case" for NAT66.  =
You're inviting a devil in to your house for tea and cake, and it may =
not leave when you ask.  That there are still architectural/design flaws =
for which NAT66 may ultimately be necessary I would be willing to admit, =
if only for the sake of discussion.  But not this.  6to4 is one third =
today what it was 2 years ago.  Let it pass in peace.

=20

NATing from IPv4 to IPv6 for your customers leaves NAT a part of the =
IPv4 leaf network/administrative domain, and doesn't carry that practice =
forward into IPv6.

=20

As  (I believe) Albert Einstein said, "We can't solve problems by using =
the same kind of thinking we used when we created them."  [Apologies if =
I'm mistaken.]


------=_NextPart_000_0929_01CB76B7.FFD960C0
Content-Type: text/html;
	charset="utf-8"
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=3Dutf-8">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I have to agree with Erik here. For the number of people =
that
would have a significant enough customer base using 6to4 that they might
consider PMT, the world would be MUCH better off with a handful of &gt; =
/16
announcements in BGP, than having to deal with the NAT66 nonsense =
forever.
Shortsighted hacks that bring along dangerous baggage MUST NOT be =
standardized.
<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Do whatever you are going to do to support your =
customers, but
don=E2=80=99t expect the world to standardize your model. =
<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Tony<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
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'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] <b>On Behalf Of =
</b>Erik
Kline<br>
<b>Sent:</b> Thursday, October 28, 2010 9:50 AM<br>
<b>To:</b> Victor Kuarsingh<br>
<b>Cc:</b> IPv6 Operations<br>
<b>Subject:</b> Re: [v6ops] Reasons not to endorse =
NAT66/6to4<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div>

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

<p class=3DMsoNormal>Are you suggesting translating from IPv4 to IPv6 is =
better
then IPv6 to<br>
IPv6? (PT66/NAT66) &nbsp;Both remove e2e transparency (so no gain here =
either<br>
way). &nbsp;Maybe I am off here, but I would have thought that =
in-family<br>
translation beats cross-family translation.<o:p></o:p></p>

</blockquote>

<div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

<div>

<p class=3DMsoNormal>IMHO nothing is worth enshrining this as a =
&quot;valid use
case&quot; for NAT66. &nbsp;You're inviting a devil in to your house for =
tea
and cake, and it may not leave when you ask. &nbsp;That there are still =
architectural/design
flaws for which NAT66 may ultimately be necessary I would be willing to =
admit,
if only for the sake of discussion. &nbsp;But not this. &nbsp;6to4 is =
one third
today what it was 2 years ago. &nbsp;Let it pass in =
peace.<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

<div>

<p class=3DMsoNormal>NATing from IPv4 to IPv6 for your customers leaves =
NAT a
part of the IPv4 leaf network/administrative domain, and doesn't carry =
that
practice forward into IPv6.<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

<div>

<div>

<p class=3DMsoNormal>As&nbsp;&nbsp;(I believe)&nbsp;Albert Einstein =
said,
&quot;We can't solve problems by using the same kind of thinking we used =
when
we created them.&quot; &nbsp;[Apologies if I'm mistaken.]<o:p></o:p></p>

</div>

</div>

</div>

</div>

</div>

</body>

</html>

------=_NextPart_000_0929_01CB76B7.FFD960C0--


From remi.despres@free.fr  Fri Oct 29 00:27:43 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CAF4A3A6A17 for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 00:27:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.563
X-Spam-Level: 
X-Spam-Status: No, score=-1.563 tagged_above=-999 required=5 tests=[AWL=0.386,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q2IeNjl6oQB3 for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 00:27:41 -0700 (PDT)
Received: from smtp22.services.sfr.fr (smtp22.services.sfr.fr [93.17.128.11]) by core3.amsl.com (Postfix) with ESMTP id 02FA13A6A15 for <v6ops@ietf.org>; Fri, 29 Oct 2010 00:27:41 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2209.sfr.fr (SMTP Server) with ESMTP id 71D797000088; Fri, 29 Oct 2010 09:29:34 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2209.sfr.fr (SMTP Server) with ESMTP id 0ED3B700008B; Fri, 29 Oct 2010 09:29:33 +0200 (CEST)
X-SFR-UUID: 20101029072934608.0ED3B700008B@msfrf2209.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <4CC9FCB6.8090207@viagenie.ca>
Date: Fri, 29 Oct 2010 09:29:33 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8D152EF7-E9F9-4C57-B894-9E27D9D2CC71@free.fr>
References: <8F908F17-8693-49FD-9824-D8F9F58AB77F@apple.com>	<C8EE6FF6.10A47%victor.kuarsingh@gmail.com> <4269EA985EACD24987D82DAE2FEC62E502786806@XMB-AMS-101.cisco.com> <4CC939F1.2050008@viagenie.ca> <6E6D00A2-9A5A-4A0C-AC97-B7081373FB27@free.fr> <4CC9FCB6.8090207@viagenie.ca>
To: Marc Blanchet <marc.blanchet@viagenie.ca>
X-Mailer: Apple Mail (2.1081)
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2010 07:27:43 -0000

Le 29 oct. 2010 =E0 00:44, Marc Blanchet a =E9crit :

> Le 10-10-28 13:21, R=E9mi Despr=E9s a =E9crit :
>>=20
>> Le 28 oct. 2010 =E0 10:53, Marc Blanchet a =E9crit :
>>=20
>>> My take on 6to4-PMT:
>>> - not nice. a hack. (not our first hack, will not be the last one,  =
not the worst one, but you may have a different opinion)
>>=20
>> Couldn't you join James and myself to understand that 6t4-PMT does =
more harm to 6to4, and to IPv6 in general, than it improves it?
>>=20
>> Once more:
>> 6to4 users have today the ability to be reached at their 6to4 =
addresses, not only from other 6to4 addresses, but also from  =
native-Ipv6 addresses that have routes to any 6to4 relay.
>> Adding a NAT66 to a 6to4 relays breaks this ability for all users =
that depend on this relay.
>> This technical reality is destructive, and MUST NOT be ignored.
>>=20
>=20
> well, what I wrote is a proposal going forward:
> - either there is a clear demonstration of a "good" number of 6to4 =
devices,

The more 6to4 users, the worse it is to make them unreachable at their =
6to4 address.

> - if not, I suggested authors to go to the RFC-editor individual =
submission.

Always possible.
To become an RFC, however, "Once the RFC Editor thinks a document may be =
suited for RFC publication, the RFC Editor asks the IESG to review the =
documents for conflicts with the IETF standards process or work done in =
the IETF community."

The hope, in this context, is that IESG will have noted that adding =
NAT66 to 6to4 deteriorates 6to4 for those that use it today across 6to4 =
relays, and depend on its key property that 6to4 addresses can be used =
for incoming reachability.
(This feature is  completely lost).

BTW, do you acknowledge this fact, or do you negate it, or do you =
consider it as uncertain?

>> Putting  6rd in the same undifferentiated category as 6to4-PMT,
>=20
> I did not. There was no "6rd" in the email I sent.

True!
Sorry for this mistake.=20
I still don't trace how I made it (maybe a copy and paste while working =
in parallel on two answers).=20
Anyway, thanks for correcting me.


Regards,
RD




From yiu_lee@cable.comcast.com  Fri Oct 29 00:49:26 2010
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 17B413A6A1E for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 00:49:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.291
X-Spam-Level: 
X-Spam-Status: No, score=-107.291 tagged_above=-999 required=5 tests=[AWL=0.572, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5ji8Sw3wXMUx for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 00:49:24 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 72A9A3A683B for <v6ops@ietf.org>; Fri, 29 Oct 2010 00:49:24 -0700 (PDT)
Received: from ([24.40.55.42]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.102942575; Fri, 29 Oct 2010 03:51:14 -0400
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by PACDCEXHUB01.cable.comcast.com ([fe80::d1e7:20b5:9b63:21a6%12]) with mapi id 14.01.0255.000; Fri, 29 Oct 2010 03:51:14 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: Marc Blanchet <marc.blanchet@viagenie.ca>
Thread-Topic: [v6ops] Reasons not to endorse NAT66/6to4
Thread-Index: AQHLdlNyMw/aDPO+TEiF52De1thBkZNWAoUAgABLhICAAANwgIABgSQA
Date: Fri, 29 Oct 2010 07:51:13 +0000
Message-ID: <3E0DC513-7480-411A-89CD-9E5AF32DE2BE@Cable.Comcast.com>
References: <8F908F17-8693-49FD-9824-D8F9F58AB77F@apple.com> <C8EE6FF6.10A47%victor.kuarsingh@gmail.com> <4269EA985EACD24987D82DAE2FEC62E502786806@XMB-AMS-101.cisco.com> <4CC939F1.2050008@viagenie.ca>
In-Reply-To: <4CC939F1.2050008@viagenie.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <21EC941C74718546A59DBB5D11A57699@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2010 07:49:26 -0000

Hi Marc,

Sorry to jump in late. I think your proposal is fair. The reason why =20
we presented this to IETF is because we wanted to document which may =20
happen in some ISP networks. Some ISP may deploy it w/ or w/o RFC #. =20
Yes 6to4 has finished it's job, I really hope it's number will drop to =20
0 next year. Meanwhile, we still have few hundred thousand users using =20
6to4. Victor, Scott and JF have voice their opinions why we did it. We =20
presented it and we wanted to hear what the WG thinks. If everybody =20
thinks this is a bad idea, we at least have an I-D that explains this. =20
One day if somebody saw this in the wild, we would have a reference.

Cheers,
Yiu

On Oct 28, 2010, at 4:53 AM, "Marc Blanchet" =20
<marc.blanchet@viagenie.ca> wrote:

> My take on 6to4-PMT:
> - not nice. a hack. (not our first hack, will not be the last one,  =20
> not the worst one, but you may have a different opinion)
> - pretty short time lifetime (well, things live around much longer =20
> than usually thought of, but anyway: in the grand scheme of things, =20
> should be "short")
> - I understand (and agree to some level) the reasons for deploying =20
> such schemes.
> - if this is being implemented and deployed, then it would be good =20
> to be documented somewhere in an RFC.
> - I have only one concern which has been raised before in one way or =20
> another: what is the real footprint of 6to4-enabled devices in =20
> broadband networks now and soon that is enough big to justify =20
> working on this scheme?
> - So I suggest the following if-then-else:
> if the 6to4 footprint is enough "high", then work within IETF wg =20
> (behave?) to make an RFC, else get reviewers in this community and =20
> elsewhere to comment/improve the spec and send it to RFC editor for =20
> individual submission, experimental or informational track.
>
> Marc.
> --=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D
> IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca
> Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca
> DTN news service: http://reeves.viagenie.ca
> NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

From marc.blanchet@viagenie.ca  Fri Oct 29 01:21:35 2010
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 679373A6A37 for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 01:21:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level: 
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9oVJq70vdUMm for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 01:21:33 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id 48D073A6A27 for <v6ops@ietf.org>; Fri, 29 Oct 2010 01:21:33 -0700 (PDT)
Received: from mbl.local (62-50-196-112.client.stsn.net [62.50.196.112]) by jazz.viagenie.ca (Postfix) with ESMTPSA id ED20B21106; Fri, 29 Oct 2010 04:23:25 -0400 (EDT)
Message-ID: <4CCA847C.6080007@viagenie.ca>
Date: Fri, 29 Oct 2010 09:23:24 +0100
From: Marc Blanchet <marc.blanchet@viagenie.ca>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fr; rv:1.9.2.11) Gecko/20101013 Lightning/1.0b2 Thunderbird/3.1.5
MIME-Version: 1.0
To: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
References: <8F908F17-8693-49FD-9824-D8F9F58AB77F@apple.com>	<C8EE6FF6.10A47%victor.kuarsingh@gmail.com> <4269EA985EACD24987D82DAE2FEC62E502786806@XMB-AMS-101.cisco.com> <4CC939F1.2050008@viagenie.ca> <3E0DC513-7480-411A-89CD-9E5AF32DE2BE@Cable.Comcast.com>
In-Reply-To: <3E0DC513-7480-411A-89CD-9E5AF32DE2BE@Cable.Comcast.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2010 08:21:35 -0000

Le 10-10-29 08:51, Lee, Yiu a écrit :
> Hi Marc,
>
> Sorry to jump in late. I think your proposal is fair. The reason why
> we presented this to IETF is because we wanted to document which may
> happen in some ISP networks. Some ISP may deploy it w/ or w/o RFC #.
> Yes 6to4 has finished it's job, I really hope it's number will drop to
> 0 next year. Meanwhile, we still have few hundred thousand users using
> 6to4. Victor, Scott and JF have voice their opinions why we did it. We
> presented it and we wanted to hear what the WG thinks. If everybody
> thinks this is a bad idea, we at least have an I-D that explains this.

great that you did document it. If it gets implemented and deployed, 
then the best thing is to get it documented.

> One day if somebody saw this in the wild, we would have a reference.

However, I-D expires. That is why I suggested that you might want to 
think about going individual submission to RFC-editor for experimental 
track. That will give a permanent document that can be more easily 
referenced.

Marc.

>
> Cheers,
> Yiu
>
> On Oct 28, 2010, at 4:53 AM, "Marc Blanchet"
> <marc.blanchet@viagenie.ca>  wrote:
>
>> My take on 6to4-PMT:
>> - not nice. a hack. (not our first hack, will not be the last one,
>> not the worst one, but you may have a different opinion)
>> - pretty short time lifetime (well, things live around much longer
>> than usually thought of, but anyway: in the grand scheme of things,
>> should be "short")
>> - I understand (and agree to some level) the reasons for deploying
>> such schemes.
>> - if this is being implemented and deployed, then it would be good
>> to be documented somewhere in an RFC.
>> - I have only one concern which has been raised before in one way or
>> another: what is the real footprint of 6to4-enabled devices in
>> broadband networks now and soon that is enough big to justify
>> working on this scheme?
>> - So I suggest the following if-then-else:
>> if the 6to4 footprint is enough "high", then work within IETF wg
>> (behave?) to make an RFC, else get reviewers in this community and
>> elsewhere to comment/improve the spec and send it to RFC editor for
>> individual submission, experimental or informational track.
>>
>> Marc.
>> --
>> =========
>> IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca
>> Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca
>> DTN news service: http://reeves.viagenie.ca
>> NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca
>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops


-- 
=========
IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca
Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca
DTN news service: http://reeves.viagenie.ca
NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca


From remi.despres@free.fr  Fri Oct 29 02:49:52 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 53AE13A6819 for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 02:49:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.265
X-Spam-Level: 
X-Spam-Status: No, score=-1.265 tagged_above=-999 required=5 tests=[AWL=0.084,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fOTyO-7d73Eo for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 02:49:51 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.20]) by core3.amsl.com (Postfix) with ESMTP id 15CFD3A67AC for <v6ops@ietf.org>; Fri, 29 Oct 2010 02:49:51 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2322.sfr.fr (SMTP Server) with ESMTP id 8F2AD700008D; Fri, 29 Oct 2010 11:51:44 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2322.sfr.fr (SMTP Server) with ESMTP id E48E27000092; Fri, 29 Oct 2010 11:51:43 +0200 (CEST)
X-SFR-UUID: 20101029095143936.E48E27000092@msfrf2322.sfr.fr
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Date: Fri, 29 Oct 2010 11:51:44 +0200
Message-Id: <5958963B-3617-41A7-B413-7D0B880AE09C@free.fr>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, Dave Thaler <dthaler@microsoft.com>, Jim Hoagland <Jim_Hoagland@symantec.com>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
Cc: v6ops <v6ops@ietf.org>, Keith Moore <moore@network-heretics.com>
Subject: [v6ops] draft-ietf-v6ops-tunnel-security-concerns-04 - applicability to 6to4 and 6rd
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2010 09:49:52 -0000

Hi, Suresh, Dave, Jim,

Thanks for the detailed and valuable analysis contained in this draft.

I tried to check which of the identified security concerns apply to the =
following deployed scenarios:
- 6to4 between two 6to4 routers
- 6rd in an ISP network.
They have in common that, in their application scenarios, tunnels =
traverse neither any NAT nor any firewall, and that tunnel endpoint =
addresses are algorithmically derived from addresses contained in =
tunneled packets.

This is what I obtained:=20

o 2.1. Network Security Bypass=20
=3D> Non applicable because no FW is traversed

o 2.2. IP Ingress and Egress Filtering Bypass=20
=3D> Not applicable if consistency checks between encapsulated and =
encapsulating addresses checks are performed at tunnel exits, as =
recommended in 6to4 and 6rd specifications .

o 2.3.  Source Routing After the Tunnel Client=20
=3D> No new risk is introduced by the fact that IPv6 has been locally =
tunneled before reaching a  routing function where source routing, if =
not appropriately controlled, can create a problem.=20

o 3.1 Inefficiency of Selective Network Filtering of All Tunneled =
Packets
=3D> Non applicable because no FW is traversed

o 3.2. Problems with deep packet inspection of tunneled data packets
=3D> Non applicable because no FW is traversed (deep packet inspection =
can apply to decapsulated packets independently of their having been =
tunneled).

o 4.1 to 4.3 (NAT Holes Increase Attack Surface, Exposure of a NAT Hole, =
Public Tunnels Widen Holes in Restricted NATs)
=3D> Non applicable because no NAT is traversed

o 5.1 and 5.2 (Feasibility of Guessing Tunnel Addresses, Profiling =
Targets Based on Tunnel Address)
=3D> Non applicable because encapsulation headers add no information =
that isn't present in encapsulated headers

o 6.1. Attacks Facilitated By Changing Tunnel Server Setting
=3D> Non applicable in 6to4 to 6to4 because tunnel addresses are purely =
algorithmic (without any parameter).
=3D> 6rd is as reliable in this respect as the mechanism used to convey =
ISP parameters to hosts, e.g. DHCP.
NOTE: IMHO, the reference to draft-ietf-v6ops-tunnel-loops would better =
be in a separate paragraph than in a sentence at the end of this section =
(minor point).

In my understanding, this confirms that these two scenarios can reliably =
be deployed.
Thank you for correcting me if I missed something.


Regards,
RD


Le 21 oct. 2010 =E0 19:30, internet-drafts@ietf.org a =E9crit :

> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> This draft is a work item of the IPv6 Operations Working Group of the =
IETF.
>=20
>=20
> 	Title           : Security Concerns With IP Tunneling
> 	Author(s)       : S. Krishnan, et al.
> 	Filename        : =
draft-ietf-v6ops-tunnel-security-concerns-03.txt
> 	Pages           : 19
> 	Date            : 2010-10-21
>=20
> A number of security concerns with IP tunnels are documented in this
> memo.  The intended audience of this document includes network
> administrators and future protocol developers.  The primary intent of
> this document is to raise the awareness level regarding the security
> issues with IP tunnels as deployed today.
>=20
> A URL for this Internet-Draft is:
> =
http://www.ietf.org/internet-drafts/draft-ietf-v6ops-tunnel-security-conce=
rns-03.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> <Pi=E8ce jointe Mail>_______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From marc.blanchet@viagenie.ca  Fri Oct 29 02:59:48 2010
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 373DC3A6840 for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 02:59:48 -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.050, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0eM5z7IKnudL for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 02:59:47 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by core3.amsl.com (Postfix) with ESMTP id 1944B3A6810 for <v6ops@ietf.org>; Fri, 29 Oct 2010 02:59:47 -0700 (PDT)
Received: from mbl.local (jazz.viagenie.ca [206.123.31.2]) by jazz.viagenie.ca (Postfix) with ESMTPSA id C19FD20E54; Fri, 29 Oct 2010 06:01:38 -0400 (EDT)
Message-ID: <4CCA9B7C.8060006@viagenie.ca>
Date: Fri, 29 Oct 2010 11:01:32 +0100
From: Marc Blanchet <marc.blanchet@viagenie.ca>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; fr; rv:1.9.2.11) Gecko/20101013 Lightning/1.0b2 Thunderbird/3.1.5
MIME-Version: 1.0
To: =?ISO-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
References: <8F908F17-8693-49FD-9824-D8F9F58AB77F@apple.com>	<C8EE6FF6.10A47%victor.kuarsingh@gmail.com> <4269EA985EACD24987D82DAE2FEC62E502786806@XMB-AMS-101.cisco.com> <4CC939F1.2050008@viagenie.ca> <6E6D00A2-9A5A-4A0C-AC97-B7081373FB27@free.fr> <4CC9FCB6.8090207@viagenie.ca> <8D152EF7-E9F9-4C57-B894-9E27D9D2CC71@free.fr>
In-Reply-To: <8D152EF7-E9F9-4C57-B894-9E27D9D2CC71@free.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2010 09:59:48 -0000

Le 10-10-29 08:29, Rémi Després a écrit :
>> - if not, I suggested authors to go to the RFC-editor individual submission.
>
> Always possible.
> To become an RFC, however, "Once the RFC Editor thinks a document may be suited for RFC publication, the RFC Editor asks the IESG to review the documents for conflicts with the IETF standards process or work done in the IETF community."
>
> The hope, in this context, is that IESG will have noted that adding NAT66 to 6to4 deteriorates 6to4 for those that use it today across 6to4 relays, and depend on its key property that 6to4 addresses can be used for incoming reachability.
> (This feature is  completely lost).
>

The IESG may state whatever they think about the 
proposed-experimental-RFC. Whatever they write as an IESG note, it still 
gets one of the goals which is documenting a specification of an 
implementation that is deployed and used on the Internet.

Marc.

-- 
=========
IPv6 book: Migrating to IPv6, Wiley. http://www.ipv6book.ca
Stun/Turn server for VoIP NAT-FW traversal: http://numb.viagenie.ca
DTN news service: http://reeves.viagenie.ca
NAT64-DNS64 Opensource: http://ecdysis.viagenie.ca


From prvs=9119165b2=Scott.Beuker@sjrb.ca  Fri Oct 29 11:07:49 2010
Return-Path: <prvs=9119165b2=Scott.Beuker@sjrb.ca>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C7DB03A695B for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 11:07:49 -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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aBMRXKSIAh8y for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 11:07:49 -0700 (PDT)
Received: from prdcg4ipta02x-ext.shaw.ca (prdcg4ipta02x-ext.shaw.ca [204.209.208.147]) by core3.amsl.com (Postfix) with ESMTP id DF0F33A68DB for <v6ops@ietf.org>; Fri, 29 Oct 2010 11:07:48 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.58,260,1286172000"; d="scan'208";a="158525501"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Date: Fri, 29 Oct 2010 12:09:42 -0600
Message-ID: <1EA76BAD7F050648910C041BDDED8CD5013FDC28@PRDCG4EXVW01-5.OSS.PRD>
In-Reply-To: <AANLkTikw_nbX483tiYuKnkSYpMJrjsExOCObU9qwq2cs@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops] Reasons not to endorse NAT66/6to4
Thread-Index: Act2wPASAZpCdD5qSIuP9/kX0ZQ+7gA00RuQ
References: <8F908F17-8693-49FD-9824-D8F9F58AB77F@apple.com><C8EE6FF6.10A47%victor.kuarsingh@gmail.com> <AANLkTikw_nbX483tiYuKnkSYpMJrjsExOCObU9qwq2cs@mail.gmail.com>
From: <Scott.Beuker@sjrb.ca>
To: <ek@google.com>
X-OriginalArrivalTime: 29 Oct 2010 18:09:41.0314 (UTC) FILETIME=[75118A20:01CB7794]
X-TM-AS-Product-Ver: SMEX-8.0.0.1285-6.500.1024-17732.007
X-TM-AS-Result: No--4.801200-0.000000-31
X-TM-AS-User-Approved-Sender: Yes
X-TM-AS-User-Blocked-Sender: No
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2010 18:07:50 -0000

IjZ0bzQgaXMgb25lIHRoaXJkIHRvZGF5IHdoYXQgaXQgd2FzIDIgeWVhcnMgYWdvLiINCg0KQ291
bGQgeW91IHBsZWFzZSBlbGFib3JhdGUgb24gdGhpcyBpbnRlcmVzdGluZyBmYWN0PyBCZWNhdXNl
IGl0IHJ1bnMgY29udHJhcnkgdG8gZXZlcnl0aGluZyBJIGhhdmUgc2VlbiBvbiB0aGUgbWF0dGVy
Lg0KDQotIFNjb3R0DQo=

From dwing@cisco.com  Fri Oct 29 12:19:56 2010
Return-Path: <dwing@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E6DA3A686B for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 12:19:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.307
X-Spam-Level: 
X-Spam-Status: No, score=-110.307 tagged_above=-999 required=5 tests=[AWL=-0.008, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D8G1OUHKnkyb for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 12:19:54 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id C65E53A69CB for <v6ops@ietf.org>; Fri, 29 Oct 2010 12:19:54 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFAHq7ykyrR7H+/2dsb2JhbACUe4xWcaNNnBaFSASEVw
X-IronPort-AV: E=Sophos;i="4.58,260,1286150400"; d="scan'208";a="209057260"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-4.cisco.com with ESMTP; 29 Oct 2010 19:21:49 +0000
Received: from dwingWS (sjc-vpn3-281.cisco.com [10.21.65.25]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o9TJLiS8027377; Fri, 29 Oct 2010 19:21:44 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "=?iso-8859-1?Q?'R=E9mi_Despr=E9s'?=" <remi.despres@free.fr>, "'Victor Kuarsingh'" <victor.kuarsingh@gmail.com>
References: <C8EE54D5.10A40%victor.kuarsingh@gmail.com> <1F2A8C2C-3875-4F1E-82E8-37DFACC37FDB@free.fr>
In-Reply-To: <1F2A8C2C-3875-4F1E-82E8-37DFACC37FDB@free.fr>
Date: Fri, 29 Oct 2010 12:21:44 -0700
Message-ID: <142101cb779e$893aeeb0$9bb0cc10$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Act2d5CjTLM3XxXtTE2iP7GYf3+SSwBJndag
Content-Language: en-us
Cc: 'Scott Beuker' <Scott.Beuker@sjrb.ca>, 'v6ops v6ops' <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref	draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2010 19:19:56 -0000

R=E9mi Despr=E9s wrote:

> > Operators need an option to help customers who have not yet replaced
> > equipment which has a "current set" of features (and as noted, this
> > often includes 6to4 default operation).
>=20
> That's why current 6to4 users shouldn't lose the ability to be reached
> at their 6to4 address, including by hosts that have native-Ipv6
> addresses and routes via 6to4 relays.
> Adding a NAT66 to 6to4 relays breaks this ability.
> This technical reality MUST NOT be ignored. =20

I don't believe Victor's PMT breaks that ability. =20

The 6to4 host is still accessible via its 6to4 address, which won't=20
go through the provider's NAT66.  The provider *could* break that=20
ability (just like they could break 6to4 without PMT), but I don't=20
recall draft-kuarsingh-v6ops-provider-managed-tunnel suggesting
that providers break this ability.

-d


From jhw@apple.com  Fri Oct 29 12:36:07 2010
Return-Path: <jhw@apple.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 955653A69CE for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 12:36:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.39
X-Spam-Level: 
X-Spam-Status: No, score=-106.39 tagged_above=-999 required=5 tests=[AWL=0.209, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WJ1rxHI14m7f for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 12:36:02 -0700 (PDT)
Received: from mail-out3.apple.com (mail-out.apple.com [17.254.13.22]) by core3.amsl.com (Postfix) with ESMTP id 30C7C3A69AF for <v6ops@ietf.org>; Fri, 29 Oct 2010 12:36:00 -0700 (PDT)
Received: from relay15.apple.com (relay15.apple.com [17.128.113.54]) by mail-out3.apple.com (Postfix) with ESMTP id 1E67CB2EBE41 for <v6ops@ietf.org>; Fri, 29 Oct 2010 12:37:54 -0700 (PDT)
X-AuditID: 11807136-b7b3aae0000033cc-64-4ccb229169af
Received: from et.apple.com (et.apple.com [17.151.62.12]) by relay15.apple.com (Apple SCV relay) with SMTP id BB.F5.13260.1922BCC4; Fri, 29 Oct 2010 12:37:54 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from il0602f-dhcp196.apple.com (il0602f-dhcp196.apple.com [17.206.50.196]) by et.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LB200J26H75O380@et.apple.com> for v6ops@ietf.org; Fri, 29 Oct 2010 12:37:53 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <142101cb779e$893aeeb0$9bb0cc10$@com>
Date: Fri, 29 Oct 2010 12:37:53 -0700
Message-id: <A238D5BD-A660-47F3-B10B-FC99D3378BCF@apple.com>
References: <C8EE54D5.10A40%victor.kuarsingh@gmail.com> <1F2A8C2C-3875-4F1E-82E8-37DFACC37FDB@free.fr> <142101cb779e$893aeeb0$9bb0cc10$@com>
To: v6ops v6ops <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [v6ops] Reasons not to endorse	NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2010 19:36:07 -0000

On Oct 29, 2010, at 12:21, Dan Wing wrote:
> 
> I don't believe Victor's PMT breaks that ability.  

I'm certain it does.

> The 6to4 host is still accessible via its 6to4 address, which won't 
> go through the provider's NAT66.  The provider *could* break that 
> ability (just like they could break 6to4 without PMT), but I don't 
> recall draft-kuarsingh-v6ops-provider-managed-tunnel suggesting
> that providers break this ability.

I have native dual-stack IPv4/IPv6 service on my home network.  I operate my own 6to4-relay that encapsulates all traffic to 2002::/16 destinations in the IPv4 tunnel and sends it to my service provider's IPv4 default router.

Say you're located at a 6to4-PMT subscriber site.  I want to reach your host at its 6to4 address (let's say the address was referred to me somehow by somebody using 6to4 to communicate with your host, e.g. your own host itself).

So I send a SYN packet from 2001:db8::1 to 2002:aabb:ccdd::$IID.  Where does the ACK go?  Through the 6to4 relay at 192.88.99.1 and then through the NAT66, which rewrites the source address so I don't recognize it.  Kaboom.  Fail.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



From gert@space.net  Fri Oct 29 13:04:37 2010
Return-Path: <gert@space.net>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CF6973A691A for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 13:04:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.517
X-Spam-Level: 
X-Spam-Status: No, score=-2.517 tagged_above=-999 required=5 tests=[AWL=0.082,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8p0EmAFRz8SH for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 13:04:36 -0700 (PDT)
Received: from mobil.space.net (mobil.Space.Net [IPv6:2001:608:2:81::2]) by core3.amsl.com (Postfix) with ESMTP id 682C43A6857 for <v6ops@ietf.org>; Fri, 29 Oct 2010 13:04:34 -0700 (PDT)
Received: from mobil.space.net (localhost [127.0.0.1]) by mobil.space.net (Postfix) with ESMTP id A93B2F83FD for <v6ops@ietf.org>; Fri, 29 Oct 2010 22:06:28 +0200 (CEST)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 79AE6F8422 for <v6ops@ietf.org>; Fri, 29 Oct 2010 22:06:28 +0200 (CEST)
Received: (qmail 38663 invoked by uid 1007); 29 Oct 2010 22:06:28 +0200
Date: Fri, 29 Oct 2010 22:06:28 +0200
From: Gert Doering <gert@space.net>
To: Dan Wing <dwing@cisco.com>
Message-ID: <20101029200628.GF32268@Space.Net>
References: <C8EE54D5.10A40%victor.kuarsingh@gmail.com> <1F2A8C2C-3875-4F1E-82E8-37DFACC37FDB@free.fr> <142101cb779e$893aeeb0$9bb0cc10$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <142101cb779e$893aeeb0$9bb0cc10$@com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: 'Scott Beuker' <Scott.Beuker@sjrb.ca>, 'v6ops v6ops' <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref	draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2010 20:04:37 -0000

Hi,

On Fri, Oct 29, 2010 at 12:21:44PM -0700, Dan Wing wrote:
> I don't believe Victor's PMT breaks that ability.  
> 
> The 6to4 host is still accessible via its 6to4 address, which won't 
> go through the provider's NAT66.  The provider *could* break that 
> ability (just like they could break 6to4 without PMT), but I don't 
> recall draft-kuarsingh-v6ops-provider-managed-tunnel suggesting
> that providers break this ability.

If the connection comes from a native IPv6 (non 6to4) host, the reply
packet will go through the NAT66, and will arrive with a different 
address than the other end is expecting to hear from.

Sounds broken to me.

(6to4<->6to4 will not be broken, but that is not broken today either)

Gert Doering
        -- NetMaster
-- 
did you enable IPv6 on something today...?

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

From dwing@cisco.com  Fri Oct 29 13:15:54 2010
Return-Path: <dwing@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B8AF73A6857 for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 13:15:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.157
X-Spam-Level: 
X-Spam-Status: No, score=-110.157 tagged_above=-999 required=5 tests=[AWL=-0.158, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SeHYgiJ5Qb9c for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 13:15:53 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id C71BD3A6767 for <v6ops@ietf.org>; Fri, 29 Oct 2010 13:15:53 -0700 (PDT)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFAF/IykyrR7H+/2dsb2JhbACUe4xWcaN2nByFSASEVw
X-IronPort-AV: E=Sophos;i="4.58,261,1286150400"; d="scan'208";a="278077998"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-5.cisco.com with ESMTP; 29 Oct 2010 20:17:48 +0000
Received: from dwingWS (sjc-vpn3-281.cisco.com [10.21.65.25]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o9TKHm2C018781; Fri, 29 Oct 2010 20:17:48 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'james woodyatt'" <jhw@apple.com>, "'v6ops v6ops'" <v6ops@ietf.org>
References: <C8EE54D5.10A40%victor.kuarsingh@gmail.com> <1F2A8C2C-3875-4F1E-82E8-37DFACC37FDB@free.fr> <142101cb779e$893aeeb0$9bb0cc10$@com> <A238D5BD-A660-47F3-B10B-FC99D3378BCF@apple.com>
In-Reply-To: <A238D5BD-A660-47F3-B10B-FC99D3378BCF@apple.com>
Date: Fri, 29 Oct 2010 13:17:48 -0700
Message-ID: <144701cb77a6$5b4b7760$11e26620$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Act3oMmLQZteTFHxQQS3OhZweASLyAAAIw6Q
Content-Language: en-us
Subject: Re: [v6ops] Reasons not to endorse	NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2010 20:15:54 -0000

> -----Original Message-----
> From: james woodyatt [mailto:jhw@apple.com]
> Sent: Friday, October 29, 2010 12:38 PM
> To: v6ops v6ops
> Cc: Dan Wing
> Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-
> kuarsingh-v6ops-provider-managed-tunnel-00)
> 
> On Oct 29, 2010, at 12:21, Dan Wing wrote:
> >
> > I don't believe Victor's PMT breaks that ability.
> 
> I'm certain it does.
> 
> > The 6to4 host is still accessible via its 6to4 address, which won't
> > go through the provider's NAT66.  The provider *could* break that
> > ability (just like they could break 6to4 without PMT), but I don't
> > recall draft-kuarsingh-v6ops-provider-managed-tunnel suggesting
> > that providers break this ability.
> 
> I have native dual-stack IPv4/IPv6 service on my home network.  I
> operate my own 6to4-relay that encapsulates all traffic to 2002::/16
> destinations in the IPv4 tunnel and sends it to my service provider's
> IPv4 default router.
> 
> Say you're located at a 6to4-PMT subscriber site.  I want to reach your
> host at its 6to4 address (let's say the address was referred to me
> somehow by somebody using 6to4 to communicate with your host, e.g. your
> own host itself).
> 
> So I send a SYN packet from 2001:db8::1 to 2002:aabb:ccdd::$IID.  Where
> does the ACK go?  Through the 6to4 relay at 192.88.99.1 and then
> through the NAT66, which rewrites the source address so I don't
> recognize it.  Kaboom.  Fail.

I was thinking of ICE, running over UDP (e.g., with XMPP or SIP), which
doesn't break.  You are right that TCP breaks.  Thanks.

-d



From jhw@apple.com  Fri Oct 29 13:30:17 2010
Return-Path: <jhw@apple.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7368C3A6827 for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 13:30:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.4
X-Spam-Level: 
X-Spam-Status: No, score=-106.4 tagged_above=-999 required=5 tests=[AWL=0.199,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J4Cg2px18qS6 for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 13:30:16 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id 8A83D3A6833 for <v6ops@ietf.org>; Fri, 29 Oct 2010 13:30:16 -0700 (PDT)
Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out4.apple.com (Postfix) with ESMTP id DBD88B8F5370 for <v6ops@ietf.org>; Fri, 29 Oct 2010 13:32:11 -0700 (PDT)
X-AuditID: 11807137-b7bf7ae000000f05-ec-4ccb2f4be9b5
Received: from gertie.apple.com (gertie.apple.com [17.151.62.15]) by relay16.apple.com (Apple SCV relay) with SMTP id 6C.62.03845.B4F2BCC4; Fri, 29 Oct 2010 13:32:11 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from il0602f-dhcp196.apple.com (il0602f-dhcp196.apple.com [17.206.50.196]) by gertie.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LB200L09JPNT070@gertie.apple.com> for v6ops@ietf.org; Fri, 29 Oct 2010 13:32:11 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <144701cb77a6$5b4b7760$11e26620$@com>
Date: Fri, 29 Oct 2010 13:32:11 -0700
Message-id: <04ABF851-5B0A-4B62-8729-A0C1FC2701F7@apple.com>
References: <C8EE54D5.10A40%victor.kuarsingh@gmail.com> <1F2A8C2C-3875-4F1E-82E8-37DFACC37FDB@free.fr> <142101cb779e$893aeeb0$9bb0cc10$@com> <A238D5BD-A660-47F3-B10B-FC99D3378BCF@apple.com> <144701cb77a6$5b4b7760$11e26620$@com>
To: v6ops v6ops <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [v6ops] Reasons not to endorse	NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2010 20:30:17 -0000

On Oct 29, 2010, at 13:17, Dan Wing wrote:

> I was thinking of ICE, running over UDP (e.g., with XMPP or SIP), which
> doesn't break.  You are right that TCP breaks.  Thanks.

Same thing happens with IKE, which is UDP.  Basically, anything where my host sends a packet to yours and expects to get a response packet where your source address matches my destination address, i.e. most connection-oriented applications and anything that sets up a host-to-host association for a traffic flow, e.g. SCTP.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



From dwing@cisco.com  Fri Oct 29 13:34:51 2010
Return-Path: <dwing@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B9E7C3A6AB4 for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 13:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.532
X-Spam-Level: 
X-Spam-Status: No, score=-110.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MrcztQ0Y+-2T for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 13:34:28 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id BBAD83A6827 for <v6ops@ietf.org>; Fri, 29 Oct 2010 13:34:24 -0700 (PDT)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFAEvNykyrRN+K/2dsb2JhbACUe4xWcaQGnB+FSASEVw
X-IronPort-AV: E=Sophos;i="4.58,261,1286150400"; d="scan'208";a="375822913"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-1.cisco.com with ESMTP; 29 Oct 2010 20:36:20 +0000
Received: from dwingWS (sjc-vpn3-281.cisco.com [10.21.65.25]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id o9TKaJoZ018651; Fri, 29 Oct 2010 20:36:19 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "'james woodyatt'" <jhw@apple.com>, "'v6ops v6ops'" <v6ops@ietf.org>
References: <C8EE54D5.10A40%victor.kuarsingh@gmail.com> <1F2A8C2C-3875-4F1E-82E8-37DFACC37FDB@free.fr> <142101cb779e$893aeeb0$9bb0cc10$@com> <A238D5BD-A660-47F3-B10B-FC99D3378BCF@apple.com> <144701cb77a6$5b4b7760$11e26620$@com> <04ABF851-5B0A-4B62-8729-A0C1FC2701F7@apple.com>
In-Reply-To: <04ABF851-5B0A-4B62-8729-A0C1FC2701F7@apple.com>
Date: Fri, 29 Oct 2010 13:36:19 -0700
Message-ID: <148901cb77a8$f17c0900$d4741b00$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Act3qHdN4l5i00uOQoq5lSqgihKxJAAAFKew
Content-Language: en-us
Subject: Re: [v6ops] Reasons not to endorse	NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2010 20:34:57 -0000

> > I was thinking of ICE, running over UDP (e.g., with XMPP or SIP),
> > which doesn't break.  You are right that TCP breaks.  Thanks.
> 
> Same thing happens with IKE, which is UDP.  Basically, anything where
> my host sends a packet to yours and expects to get a response packet
> where your source address matches my destination address, i.e. most
> connection-oriented applications and anything that sets up a host-to-
> host association for a traffic flow, e.g. SCTP.

*Nodding in agreement*.  Nonetheless, I was thinking of ICE.  Mea culpa, 
once again.

-d



From brian.e.carpenter@gmail.com  Fri Oct 29 14:02:25 2010
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6435E3A6AC5 for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 14:02:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.424
X-Spam-Level: 
X-Spam-Status: No, score=-102.424 tagged_above=-999 required=5 tests=[AWL=0.175, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xtr8hZhjUgbH for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 14:02:23 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 7F36D3A6AC3 for <v6ops@ietf.org>; Fri, 29 Oct 2010 14:02:23 -0700 (PDT)
Received: by ewy27 with SMTP id 27so2121657ewy.31 for <v6ops@ietf.org>; Fri, 29 Oct 2010 14:04:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=0gfhKZeO5kt2+40s23MB+5y+VNENWLaxwd07aJuDVi0=; b=ItzlwY7yj15raOWeHu5ShQZIun9uxQOwUnTUUN4nzO4hIawUUy1AqcXUdlsFJZjHJT 4yoh3WyZRLkMw8ErC+I8igXGoT7sJujDtBQ4J9H/ZqEJYYV5jQmVwdE3m0ejTUdFULQ1 oAXFlHIfz4Q0ZukIMpYDNu7ZwQCTirHoTOpoM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=mrlVwwo1D9oRByrDn3uMxBpe1rZGAn+MPEEygAejZNzXV6FiIrTs584S8cH5pI2YUC sQyPBKVIY/fBH+rYX9Oz5FL9P7kydASXPdsjqxz2bdoMaOqgeuh7EcT/lbuQhQUXJW/n 5pouvsPJMa5vm990/yHH3fOEzxn/pGmH8vsGA=
Received: by 10.213.27.132 with SMTP id i4mr10914027ebc.43.1288386258192; Fri, 29 Oct 2010 14:04:18 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.142.15]) by mx.google.com with ESMTPS id x54sm2049602eeh.11.2010.10.29.14.04.14 (version=SSLv3 cipher=RC4-MD5); Fri, 29 Oct 2010 14:04:17 -0700 (PDT)
Message-ID: <4CCB36C9.7000807@gmail.com>
Date: Sat, 30 Oct 2010 10:04:09 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: james woodyatt <jhw@apple.com>
References: <C8EE54D5.10A40%victor.kuarsingh@gmail.com>	<1F2A8C2C-3875-4F1E-82E8-37DFACC37FDB@free.fr>	<142101cb779e$893aeeb0$9bb0cc10$@com> <A238D5BD-A660-47F3-B10B-FC99D3378BCF@apple.com>
In-Reply-To: <A238D5BD-A660-47F3-B10B-FC99D3378BCF@apple.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: v6ops v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2010 21:02:25 -0000

On 2010-10-30 08:37, james woodyatt wrote:
> On Oct 29, 2010, at 12:21, Dan Wing wrote:
>> I don't believe Victor's PMT breaks that ability.  
> 
> I'm certain it does.
> 
>> The 6to4 host is still accessible via its 6to4 address, which won't 
>> go through the provider's NAT66.  The provider *could* break that 
>> ability (just like they could break 6to4 without PMT), but I don't 
>> recall draft-kuarsingh-v6ops-provider-managed-tunnel suggesting
>> that providers break this ability.
> 
> I have native dual-stack IPv4/IPv6 service on my home network.  I operate my own 6to4-relay that encapsulates all traffic to 2002::/16 destinations in the IPv4 tunnel and sends it to my service provider's IPv4 default router.
> 
> Say you're located at a 6to4-PMT subscriber site.  I want to reach your host at its 6to4 address (let's say the address was referred to me somehow by somebody using 6to4 to communicate with your host, e.g. your own host itself).
> 
> So I send a SYN packet from 2001:db8::1 to 2002:aabb:ccdd::$IID.  Where does the ACK go?  Through the 6to4 relay at 192.88.99.1 and then through the NAT66, which rewrites the source address so I don't recognize it.  Kaboom.  Fail.

How does the initiator know that the listener's address is 2002:aabb:ccdd::$IID
in the first place? Did the listener site forget to install two-faced DNS, which
seems to be the only way this could be hacked around to work?

It's no real surprise that a server behind a NAT doesn't work properly without
a kludge. NAT doubleplusungood, once again.

   Brian

From jhw@apple.com  Fri Oct 29 14:47:26 2010
Return-Path: <jhw@apple.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 764683A6AD0 for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 14:47:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.408
X-Spam-Level: 
X-Spam-Status: No, score=-106.408 tagged_above=-999 required=5 tests=[AWL=0.191, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7eA-7jMyXVT3 for <v6ops@core3.amsl.com>; Fri, 29 Oct 2010 14:47:25 -0700 (PDT)
Received: from mail-out4.apple.com (mail-out.apple.com [17.254.13.23]) by core3.amsl.com (Postfix) with ESMTP id CBD9E3A6AC4 for <v6ops@ietf.org>; Fri, 29 Oct 2010 14:47:24 -0700 (PDT)
Received: from relay16.apple.com (relay16.apple.com [17.128.113.55]) by mail-out4.apple.com (Postfix) with ESMTP id 23FBCB8F997B for <v6ops@ietf.org>; Fri, 29 Oct 2010 14:49:20 -0700 (PDT)
X-AuditID: 11807137-b7bf7ae000000f05-9d-4ccb415f0ced
Received: from gertie.apple.com (gertie.apple.com [17.151.62.15]) by relay16.apple.com (Apple SCV relay) with SMTP id A0.7A.03845.0614BCC4; Fri, 29 Oct 2010 14:49:20 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
Received: from il0602f-dhcp196.apple.com (il0602f-dhcp196.apple.com [17.206.50.196]) by gertie.apple.com (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPSA id <0LB200LIFNA7T080@gertie.apple.com> for v6ops@ietf.org; Fri, 29 Oct 2010 14:49:19 -0700 (PDT)
From: james woodyatt <jhw@apple.com>
In-reply-to: <4CCB36C9.7000807@gmail.com>
Date: Fri, 29 Oct 2010 14:49:19 -0700
Message-id: <F7BCF45C-CA06-4420-B058-9C5106310B8C@apple.com>
References: <C8EE54D5.10A40%victor.kuarsingh@gmail.com> <1F2A8C2C-3875-4F1E-82E8-37DFACC37FDB@free.fr> <142101cb779e$893aeeb0$9bb0cc10$@com> <A238D5BD-A660-47F3-B10B-FC99D3378BCF@apple.com> <4CCB36C9.7000807@gmail.com>
To: v6ops v6ops <v6ops@ietf.org>
X-Mailer: Apple Mail (2.1082)
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Oct 2010 21:47:26 -0000

On Oct 29, 2010, at 14:04, Brian E Carpenter wrote:
> 
> How does the initiator know that the listener's address is 2002:aabb:ccdd::$IID
> in the first place? Did the listener site forget to install two-faced DNS, which
> seems to be the only way this could be hacked around to work?

The listener didn't ask to be located behind the provider NAT66 middlebox.

The listener host probably used Dynamic DNS to register all its global-scope interface addresses.  Or maybe the initiator is an FTP server that's trying to open the data port on the client host in response to a PORT command.  Or maybe the initiator is a BitTorrent peer.  Or maybe the initiator is an IKE responder that's been manually configured with the 6to4 address in its security policy database.  Or.  Or.  Or.

Yes, this would be a good time to plug I-D.carpenter-referral-ps again.  I swear, it's like playing a game of whack-a-mole.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



From remi.despres@free.fr  Sat Oct 30 00:48:01 2010
Return-Path: <remi.despres@free.fr>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 865F93A69BB for <v6ops@core3.amsl.com>; Sat, 30 Oct 2010 00:48:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.574
X-Spam-Level: 
X-Spam-Status: No, score=-1.574 tagged_above=-999 required=5 tests=[AWL=0.375,  BAYES_00=-2.599, HELO_EQ_FR=0.35, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gVW+qtBJvrjl for <v6ops@core3.amsl.com>; Sat, 30 Oct 2010 00:47:58 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.19]) by core3.amsl.com (Postfix) with ESMTP id 498333A69BA for <v6ops@ietf.org>; Sat, 30 Oct 2010 00:47:58 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2304.sfr.fr (SMTP Server) with ESMTP id EE5CC7000081; Sat, 30 Oct 2010 09:49:53 +0200 (CEST)
Received: from [192.168.0.20] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2304.sfr.fr (SMTP Server) with ESMTP id 0FEA8700008B; Sat, 30 Oct 2010 09:49:53 +0200 (CEST)
X-SFR-UUID: 20101030074953652.0FEA8700008B@msfrf2304.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <20101029200628.GF32268@Space.Net>
Date: Sat, 30 Oct 2010 09:49:52 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <78783399-4EFD-41FC-9DD8-866B3FA9A0A6@free.fr>
References: <C8EE54D5.10A40%victor.kuarsingh@gmail.com> <1F2A8C2C-3875-4F1E-82E8-37DFACC37FDB@free.fr> <142101cb779e$893aeeb0$9bb0cc10$@com> <20101029200628.GF32268@Space.Net>
To: Dan Wing <dwing@cisco.com>
X-Mailer: Apple Mail (2.1081)
Cc: Scott Beuker <Scott.Beuker@sjrb.ca>, v6ops v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Oct 2010 07:48:01 -0000

Dan,

>=20
> On Fri, Oct 29, 2010 at 12:21:44PM -0700, Dan Wing wrote:
>> ...
>> I don't believe Victor's PMT breaks that ability. =20
>> ...

Le 29 oct. 2010 =E0 22:06, Gert Doering a =E9crit :
> ...If the connection comes from a native IPv6 (non 6to4) host, the =
reply
> packet will go through the NAT66, and will arrive with a different=20
> address than the other end is expecting to hear from.
>=20
> Sounds broken to me.

Same understanding.


> (6to4<->6to4 will not be broken, but that is not broken today either)

Idem.

Regards,
RD




From joelja@bogus.com  Sat Oct 30 11:35:29 2010
Return-Path: <joelja@bogus.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E95B63A6972 for <v6ops@core3.amsl.com>; Sat, 30 Oct 2010 11:35:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.793
X-Spam-Level: 
X-Spam-Status: No, score=-101.793 tagged_above=-999 required=5 tests=[AWL=-0.486, BAYES_00=-2.599, MISSING_HEADERS=1.292, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AEA36Io6w+gX for <v6ops@core3.amsl.com>; Sat, 30 Oct 2010 11:35:27 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 283703A6999 for <v6ops@ietf.org>; Sat, 30 Oct 2010 11:35:17 -0700 (PDT)
Received: from joelja-mac.local (m2a5e36d0.tmodns.net [208.54.94.42]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id o9UIahdR028904 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sat, 30 Oct 2010 18:37:01 GMT (envelope-from joelja@bogus.com)
Message-ID: <4CCC64B1.6020806@bogus.com>
Date: Sat, 30 Oct 2010 11:32:17 -0700
From: Joel Jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
References: <C8EE54D5.10A40%victor.kuarsingh@gmail.com>	<1F2A8C2C-3875-4F1E-82E8-37DFACC37FDB@free.fr>	<142101cb779e$893aeeb0$9bb0cc10$@com>	<20101029200628.GF32268@Space.Net> <78783399-4EFD-41FC-9DD8-866B3FA9A0A6@free.fr>
In-Reply-To: <78783399-4EFD-41FC-9DD8-866B3FA9A0A6@free.fr>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Sat, 30 Oct 2010 18:37:09 +0000 (UTC)
Cc: v6ops v6ops <v6ops@ietf.org>, V6ops Chairs <v6ops-chairs@tools.ietf.org>
Subject: [v6ops] Summary Observations:  Reasons not to endorse NAT66/6to4
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Oct 2010 18:35:29 -0000

The threads associated with the discussion of:

draft-kuarsingh-v6ops-provider-managed-tunnel-00

have generated order of a hundred messages from more than two dozen
participants since 10/21.

While it would probably be useful to characterize a couple of the more
cogent points of argumentation, I think a simpler observation is that if
it were proposed, that there would clearly be strong opposition to this
document as a working group item and I don't see it advancing along that
track.

In that mean time I think it is safe to let this thread cool off.

thanks
joel

From victor.kuarsingh@gmail.com  Sun Oct 31 11:29:28 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 064433A69F0 for <v6ops@core3.amsl.com>; Sun, 31 Oct 2010 11:29:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tX9GSi1JIilZ for <v6ops@core3.amsl.com>; Sun, 31 Oct 2010 11:29:27 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id 1B19B3A694A for <v6ops@ietf.org>; Sun, 31 Oct 2010 11:29:27 -0700 (PDT)
Received: by ywp6 with SMTP id 6so3082274ywp.31 for <v6ops@ietf.org>; Sun, 31 Oct 2010 11:31:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=BL2CPVK/3SpDPFCuMgLDOasMGTFVzqswlqle7M73cG8=; b=GcmLpOirhQnt2l2FUSiDaMzzcnpzvwvqUUcC3L0vLuvcTGMowAcKzCoAND3yMwg9Zb dj4qgJqHlEPYpEz0RQCpzL6B+mV7P6UtaqxsSpN+5aFstpHmLjfy2nt+5CPxTGiSLzBQ jIS2uLpaaK3//OfTjfWzxYiiqekpARfShaS40=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=DbhBNZpX9Om+zfOWYkBXK6oju+FV+UtGtIQQPfeZLvB2THx3qx0Rv0UTwHldWzUVBz 7qmjmGe0AdUJQ/wK/JJIPWphGSYrccVSgf8QhA9d3BGhd1/j3x0ECqtTHma3adsbvqPf 1eG2MKdyt5YYBkR9AksH52gs8XWsgSscARpOo=
Received: by 10.90.4.34 with SMTP id 34mr7521213agd.140.1288549884297; Sun, 31 Oct 2010 11:31:24 -0700 (PDT)
Received: from [192.168.100.149] ([67.224.83.162]) by mx.google.com with ESMTPS id z4sm4284283yhz.1.2010.10.31.11.31.21 (version=SSLv3 cipher=RC4-MD5); Sun, 31 Oct 2010 11:31:22 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Sun, 31 Oct 2010 14:31:27 -0400
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: james woodyatt <jhw@apple.com>, v6ops v6ops <v6ops@ietf.org>
Message-ID: <C8F32E3F.10C18%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
Thread-Index: Act5KdQkEID2YS/qh021bJ5SFf5kMg==
In-Reply-To: <F7BCF45C-CA06-4420-B058-9C5106310B8C@apple.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Oct 2010 18:29:28 -0000

James,

Agreed, there are defiantly issues when NATing (even 6to6).

Just as an additional point, one of the use cases is when IPv4 runs out and
the customer is now behind a provider NAT44 (which in most cases means
NAT444 - the infamous double NAT).

At this point many operations will need to apply either RFC1918 or (key
issue) public Space (either from their own pool as overlap, from RIR special
block, camped space etc).  In the second case, NAT is now unavoidable for
such customers (in IPv4 space).  So we are in a "bad" scenario either way.
In this case, 6to4 (if on by default) will activate and be broken (since no
real return path for that address exits in the 6to4 model).

In this case, IPv4 will unlikely have a level of additional brokenness.  In
this case, the single NAT66 may still be better then the double NAT44
(NAT444).

An additional NAT66 will enter the the Internet world, one way or the other
(i.e. Dual homing enterprises), this may also be a good chance to see what
the actual real world impacts are of this type of translation are. (it is
also very easy to turn off/on).

Just an additional set of thoughts.

Regards,

Victor


On 29/10/10 5:49 PM, "james woodyatt" <jhw@apple.com> wrote:

> On Oct 29, 2010, at 14:04, Brian E Carpenter wrote:
>> 
>> How does the initiator know that the listener's address is
>> 2002:aabb:ccdd::$IID
>> in the first place? Did the listener site forget to install two-faced DNS,
>> which
>> seems to be the only way this could be hacked around to work?
> 
> The listener didn't ask to be located behind the provider NAT66 middlebox.
> 
> The listener host probably used Dynamic DNS to register all its global-scope
> interface addresses.  Or maybe the initiator is an FTP server that's trying to
> open the data port on the client host in response to a PORT command.  Or maybe
> the initiator is a BitTorrent peer.  Or maybe the initiator is an IKE
> responder that's been manually configured with the 6to4 address in its
> security policy database.  Or.  Or.  Or.
> 
> Yes, this would be a good time to plug I-D.carpenter-referral-ps again.  I
> swear, it's like playing a game of whack-a-mole.
> 
> 
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, communications engineering
> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops



From fred@cisco.com  Sun Oct 31 11:43:26 2010
Return-Path: <fred@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 976CA3A69F4 for <v6ops@core3.amsl.com>; Sun, 31 Oct 2010 11:43:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.42
X-Spam-Level: 
X-Spam-Status: No, score=-110.42 tagged_above=-999 required=5 tests=[AWL=0.179, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4yibutJYWjKc for <v6ops@core3.amsl.com>; Sun, 31 Oct 2010 11:43:25 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id E46863A69F2 for <v6ops@ietf.org>; Sun, 31 Oct 2010 11:43:20 -0700 (PDT)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAJRVzUyrR7H+/2dsb2JhbAChSXGeN5s0hUQEhFeFfYMI
X-IronPort-AV: E=Sophos;i="4.58,268,1286150400"; d="scan'208";a="612336187"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-6.cisco.com with ESMTP; 31 Oct 2010 18:45:20 +0000
Received: from [10.224.10.122] (sjc-vpn6-1035.cisco.com [10.21.124.11]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id o9VIjIMU015637; Sun, 31 Oct 2010 18:45:18 GMT
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Fred Baker <fred@cisco.com>
In-Reply-To: <C8F32E3F.10C18%victor.kuarsingh@gmail.com>
Date: Sun, 31 Oct 2010 11:45:17 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <EF65FE4C-528E-496F-A461-2FF9F5ED1DB6@cisco.com>
References: <C8F32E3F.10C18%victor.kuarsingh@gmail.com>
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>
X-Mailer: Apple Mail (2.1081)
Cc: v6ops v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Oct 2010 18:43:26 -0000

On Oct 31, 2010, at 11:31 AM, Victor Kuarsingh wrote:

> Just as an additional point, one of the use cases is when IPv4 runs =
out and the customer is now behind a provider NAT44 (which in most cases =
means NAT444 - the infamous double NAT).

yes, of course. And we already have a lot of that; Verizon, at the =
recent Google IPv6 conference, said they have 70 instances of 10.0.0.0/8 =
in their network, and I have to believe that many of them have =
residential routers, which generally incorporate NAT, behind them. =
Service in Latin America, Central Asia, the middle east, and Africa have =
used service provider NAT for a long time. So this is not exactly new.

I would lump that under "address amplification" - making there be more =
addresses by re-using them in a context. You probably are aware of the =
implications of the service, but I'll make that explicit. People in =
those regions don't generally talk about "being on the Internet". They =
talk about how many "steps away" they are from the Internet. They don't =
generally offer services from those domains; it's far more common to =
find an Africa person using a gmail or yahoo address than a local =
address, for example, and web sites tend to be in places that have good =
accessibility, usually hosting companies. This is true for all the =
reasons Keith has been pointing out - from their perspective, the =
service works better, as they are not forced to simply be a consumer of =
it.

So, yes, one of the use cases of IPv4/IPv4 NAT will be continuity of =
business during the coexistence period. That is an absolute fact, and =
not much worth discussing from my perspective. At least not on this =
list.=

From victor.kuarsingh@gmail.com  Sun Oct 31 12:01:29 2010
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 976023A69FD for <v6ops@core3.amsl.com>; Sun, 31 Oct 2010 12:01:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.112
X-Spam-Level: 
X-Spam-Status: No, score=-2.112 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wfVO6LTuDh4F for <v6ops@core3.amsl.com>; Sun, 31 Oct 2010 12:01:28 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id B9BDC3A69E6 for <v6ops@ietf.org>; Sun, 31 Oct 2010 12:01:28 -0700 (PDT)
Received: by ywp6 with SMTP id 6so3091003ywp.31 for <v6ops@ietf.org>; Sun, 31 Oct 2010 12:03:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:user-agent:date:subject:from :to:cc:message-id:thread-topic:thread-index:in-reply-to:mime-version :content-type:content-transfer-encoding; bh=cBqc98+Rt9BOq2ONrxAieX9092F84R+IM6Vce782LCo=; b=FnYRgJ9lgIobfV7a2l0pRbtbSJqBCjyFRL3M6A/tmy5PzB8mO7U0AcgZokiN9Pgmaq LPxGBMAW5mfpUuKpsPzbBiL9Tvqg8nGeA4DPPwKVu+/49F346tDNam08XgZ2ggYAEmqo zr5IcyPDwz+FrVhKANjvf7Kr9XC7/QAsn6Zs0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=OtqJA8WBb6T63Gj4hOvSRveZj9Oebxhyx0MTq+hnVcHGwgz9mpuVqi5IIjrZqYxkAK jeFV+CO4JSO4NjbSiujJpQ5zjLTlRbV9QWLOSfzfy84GId+i6upH01afnInWuoiQ2uZO jaHa+DxteHhyDr1ildKa1MViDaguFLJbOlF1U=
Received: by 10.91.143.17 with SMTP id v17mr7381173agn.136.1288551808164; Sun, 31 Oct 2010 12:03:28 -0700 (PDT)
Received: from [192.168.100.149] ([67.224.83.162]) by mx.google.com with ESMTPS id j7sm4308907yha.18.2010.10.31.12.03.24 (version=SSLv3 cipher=RC4-MD5); Sun, 31 Oct 2010 12:03:27 -0700 (PDT)
User-Agent: Microsoft-Entourage/12.20.0.090605
Date: Sun, 31 Oct 2010 15:03:18 -0400
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: Fred Baker <fred@cisco.com>
Message-ID: <C8F335B6.10C1D%victor.kuarsingh@gmail.com>
Thread-Topic: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
Thread-Index: Act5LkcwJ/wFk3E+5E+aJ5/EFs7fPQ==
In-Reply-To: <EF65FE4C-528E-496F-A461-2FF9F5ED1DB6@cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: v6ops v6ops <v6ops@ietf.org>
Subject: Re: [v6ops] Reasons not to endorse NAT66/6to4(ref draft-kuarsingh-v6ops-provider-managed-tunnel-00)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Oct 2010 19:01:29 -0000

Fred,

Understood, I just made mention of it as it has a connection to some
protocols like 6to4, and Teredo - which break under NAT444 (in some cases)
and are there to provide IPv6 connectivity.

Issue 1 - Teredo under NAT444 is problematic (reference
draft-donley-nat444-impacts)
Issue 2 - 6to4 under NAT444 when non-RFC1918 addressing is used

I am not here to actually discuss NAT444 on it's own - within v6ops.

Regards,

Victor


On 31/10/10 2:45 PM, "Fred Baker" <fred@cisco.com> wrote:

> 
> On Oct 31, 2010, at 11:31 AM, Victor Kuarsingh wrote:
> 
>> Just as an additional point, one of the use cases is when IPv4 runs out and
>> the customer is now behind a provider NAT44 (which in most cases means NAT444
>> - the infamous double NAT).
> 
> yes, of course. And we already have a lot of that; Verizon, at the recent
> Google IPv6 conference, said they have 70 instances of 10.0.0.0/8 in their
> network, and I have to believe that many of them have residential routers,
> which generally incorporate NAT, behind them. Service in Latin America,
> Central Asia, the middle east, and Africa have used service provider NAT for a
> long time. So this is not exactly new.
> 
> I would lump that under "address amplification" - making there be more
> addresses by re-using them in a context. You probably are aware of the
> implications of the service, but I'll make that explicit. People in those
> regions don't generally talk about "being on the Internet". They talk about
> how many "steps away" they are from the Internet. They don't generally offer
> services from those domains; it's far more common to find an Africa person
> using a gmail or yahoo address than a local address, for example, and web
> sites tend to be in places that have good accessibility, usually hosting
> companies. This is true for all the reasons Keith has been pointing out - from
> their perspective, the service works better, as they are not forced to simply
> be a consumer of it.
> 
> So, yes, one of the use cases of IPv4/IPv4 NAT will be continuity of business
> during the coexistence period. That is an absolute fact, and not much worth
> discussing from my perspective. At least not on this list.


