
From ovautrin@juniper.net  Sun Oct  3 21:38:46 2010
Return-Path: <ovautrin@juniper.net>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A29213A6F2B for <pppext@core3.amsl.com>; Sun,  3 Oct 2010 21:38:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.493
X-Spam-Level: 
X-Spam-Status: No, score=-6.493 tagged_above=-999 required=5 tests=[AWL=0.106,  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 zBv2vT343IrO for <pppext@core3.amsl.com>; Sun,  3 Oct 2010 21:38:45 -0700 (PDT)
Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by core3.amsl.com (Postfix) with ESMTP id B34293A6F2A for <pppext@ietf.org>; Sun,  3 Oct 2010 21:38:45 -0700 (PDT)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob117.postini.com ([64.18.6.12]) with SMTP ID DSNKTKlagUV0sUC1eKbzYs6CuxYoP/vgRZkb@postini.com; Sun, 03 Oct 2010 21:39:40 PDT
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Sun, 3 Oct 2010 21:38:59 -0700
From: Olivier Vautrin <ovautrin@juniper.net>
To: James Carlson <carlsonj@workingcode.com>
Date: Sun, 3 Oct 2010 21:39:05 -0700
Thread-Topic: [Pppext] new draft published: draft-vautrin-pppext-ipv6-mlppp-id-00.txt
Thread-Index: Acs9fZewv0/yVzpTTsWTd0E2iGhgtgmACBng
Message-ID: <84600D05C20FF943918238042D7670FD37320BD91C@EMBX01-HQ.jnpr.net>
References: <4C659616.3070304@workingcode.com> <4C659EB9.4050405@workingcode.com> <84600D05C20FF943918238042D7670FD36D7087F7A@EMBX01-HQ.jnpr.net> <4C6998B1.5060908@workingcode.com>
In-Reply-To: <4C6998B1.5060908@workingcode.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: "pppext@ietf.org" <pppext@ietf.org>, "blourdel@cisco.com" <blourdel@cisco.com>
Subject: Re: [Pppext] new draft published:	draft-vautrin-pppext-ipv6-mlppp-id-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Oct 2010 04:38:46 -0000

Hello, I published this draft with the new name to show that it needs to be=
 under the pppext WG.

This is now:
http://www.ietf.org/id/draft-vautrin-pppext-ipv6-mlppp-id-00.txt

Thanks,
Olivier

> -----Original Message-----
> From: James Carlson [mailto:carlsonj@workingcode.com]
> Sent: Monday, August 16, 2010 1:00 PM
> To: Olivier Vautrin
> Cc: blourdel@cisco.com; pppext@ietf.org
> Subject: Re: [Pppext] new draft published: draft-vautrin-6man-ipv6-
> mlppp-id-00.txt
>=20
> Olivier Vautrin wrote:
> > Hello James, thanks for your feedback please see below.
> >
> > Yes, I think this document should be a WG document. I thought 6man WG
> would be the right place, but I guess PPPext WG makes more sense.
>=20
> OK; thanks.  Consider it done.  You'd need our group's approval anyway
> to modify the IANA registry for the new E-D Class value.

From carlsonj@workingcode.com  Mon Oct  4 04:59:48 2010
Return-Path: <carlsonj@workingcode.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8FE1D3A6F93 for <pppext@core3.amsl.com>; Mon,  4 Oct 2010 04:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.46
X-Spam-Level: 
X-Spam-Status: No, score=-102.46 tagged_above=-999 required=5 tests=[AWL=0.139, 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 gvvZ83fK3mqz for <pppext@core3.amsl.com>; Mon,  4 Oct 2010 04:59:47 -0700 (PDT)
Received: from carlson.workingcode.com (carlsonj-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1d9::2]) by core3.amsl.com (Postfix) with ESMTP id 891283A6F90 for <pppext@ietf.org>; Mon,  4 Oct 2010 04:59:47 -0700 (PDT)
Received: from [10.50.23.149] (gate.abinitio.com [65.170.40.132]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id o94C0ZCX021574 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Oct 2010 08:00:36 -0400 (EDT)
Message-ID: <4CA9C1E3.4020807@workingcode.com>
Date: Mon, 04 Oct 2010 08:00:35 -0400
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090605)
MIME-Version: 1.0
To: Olivier Vautrin <ovautrin@juniper.net>
References: <4C659616.3070304@workingcode.com> <4C659EB9.4050405@workingcode.com> <84600D05C20FF943918238042D7670FD36D7087F7A@EMBX01-HQ.jnpr.net> <4C6998B1.5060908@workingcode.com> <84600D05C20FF943918238042D7670FD37320BD91C@EMBX01-HQ.jnpr.net>
In-Reply-To: <84600D05C20FF943918238042D7670FD37320BD91C@EMBX01-HQ.jnpr.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-DCC-x.dcc-servers-Metrics: carlson; whitelist
Cc: "pppext@ietf.org" <pppext@ietf.org>, "blourdel@cisco.com" <blourdel@cisco.com>
Subject: Re: [Pppext] new draft published:	draft-vautrin-pppext-ipv6-mlppp-id-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Oct 2010 11:59:48 -0000

Olivier Vautrin wrote:
> Hello, I published this draft with the new name to show that it needs to be under the pppext WG.
> 
> This is now:
> http://www.ietf.org/id/draft-vautrin-pppext-ipv6-mlppp-id-00.txt

I would have expected the name to be draft-pppext-..., but no matter.  I
 have a number of editorial comments that I'll send to you separately,
but the current text looks mostly good to me technically.  One nit at
that level: section 5 (IANA Considerations) says "None," but you're
allocating a new Endpoint Discriminator value, and these are registered
with IANA.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

From vjs@calcite.rhyolite.com  Mon Oct  4 06:38:27 2010
Return-Path: <vjs@calcite.rhyolite.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC18F3A6F8D for <pppext@core3.amsl.com>; Mon,  4 Oct 2010 06:38:27 -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 ekzeBbYEEi7h for <pppext@core3.amsl.com>; Mon,  4 Oct 2010 06:38:27 -0700 (PDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [IPv6:2001:4978:230::3]) by core3.amsl.com (Postfix) with ESMTP id E8D213A6C2A for <pppext@ietf.org>; Mon,  4 Oct 2010 06:38:26 -0700 (PDT)
Received: from calcite.rhyolite.com (localhost [127.0.0.1]) by calcite.rhyolite.com (8.14.4/8.14.4) with ESMTP id o94DdENk018639 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) env-from <vjs@calcite.rhyolite.com>; Mon, 4 Oct 2010 13:39:15 GMT
Received: (from vjs@localhost) by calcite.rhyolite.com (8.14.4/8.14.4/Submit) id o94DdDR3018638; Mon, 4 Oct 2010 13:39:13 GMT
Date: Mon, 4 Oct 2010 13:39:13 GMT
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <201010041339.o94DdDR3018638@calcite.rhyolite.com>
To: carlsonj@workingcode.com, ovautrin@juniper.net
In-Reply-To: <4CA9C1E3.4020807@workingcode.com>
X-DCC-Rhyolite-Metrics: calcite.rhyolite.com; whitelist
Cc: pppext@ietf.org, blourdel@cisco.com
Subject: Re: [Pppext] new draft published:	draft-vautrin-pppext-ipv6-mlppp-id-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Oct 2010 13:38:28 -0000

> From: James Carlson <carlsonj@workingcode.com>
> To: Olivier Vautrin <ovautrin@juniper.net>
> Cc: "pppext@ietf.org" <pppext@ietf.org>,
>         "blourdel@cisco.com" <blourdel@cisco.com>

> but the current text looks mostly good to me technically.  

I agree.


Vernon Schryver    vjs@rhyolite.com

From carlsonj@workingcode.com  Mon Oct 18 06:26:35 2010
Return-Path: <carlsonj@workingcode.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F347C3A6BDB for <pppext@core3.amsl.com>; Mon, 18 Oct 2010 06:26:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.188
X-Spam-Level: 
X-Spam-Status: No, score=-102.188 tagged_above=-999 required=5 tests=[AWL=-0.189, 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 810PUueerePk for <pppext@core3.amsl.com>; Mon, 18 Oct 2010 06:26:34 -0700 (PDT)
Received: from carlson.workingcode.com (carlsonj-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1d9::2]) by core3.amsl.com (Postfix) with ESMTP id E4C383A6AB8 for <pppext@ietf.org>; Mon, 18 Oct 2010 06:26:33 -0700 (PDT)
Received: from [10.50.23.149] (gate.abinitio.com [65.170.40.132]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id o9IDRlNT007527 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Oct 2010 09:27:47 -0400 (EDT)
Message-ID: <4CBC4B52.5010106@workingcode.com>
Date: Mon, 18 Oct 2010 09:27:46 -0400
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090605)
MIME-Version: 1.0
To: "pppext@ietf.org" <pppext@ietf.org>, huj@ctbri.com.cn
Content-Type: multipart/mixed; boundary="------------060207020509060101030302"
X-DCC-sonic.net-Metrics: carlson; whitelist
Subject: [Pppext] two new IPv6CP individual submissions
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Oct 2010 13:26:35 -0000

This is a multi-part message in MIME format.
--------------060207020509060101030302
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Two new IPv6CP individual submissions are attached.  I believe that both
of these should receive attention in the PPPEXT working group.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

--------------060207020509060101030302
Content-Type: message/rfc822;
 name="I-D Action:draft-hu-pppext-ipv6cp-requirements-00.txt.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename*0="I-D Action:draft-hu-pppext-ipv6cp-requirements-00.txt.eml"

Return-Path: <i-d-announce-bounces@ietf.org>
X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on
	carlson.workingcode.com
X-Spam-Level: 
X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00
	autolearn=ham version=3.2.4
Received: from mail.ietf.org (mail.ietf.org [IPv6:2001:1890:1112:1::20])
	by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id o9I2Wl56028337
	for <carlsonj@workingcode.com>; Sun, 17 Oct 2010 22:32:47 -0400 (EDT)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 821EF3A6C84;
	Sun, 17 Oct 2010 19:30:11 -0700 (PDT)
X-Original-To: i-d-announce@ietf.org
Delivered-To: i-d-announce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 360693A6C7A; Sun, 17 Oct 2010 19:30:03 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-hu-pppext-ipv6cp-requirements-00.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20101018023005.360693A6C7A@core3.amsl.com>
Date: Sun, 17 Oct 2010 19:30:03 -0700 (PDT)
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/i-d-announce>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
Sender: i-d-announce-bounces@ietf.org
Errors-To: i-d-announce-bounces@ietf.org
X-DCC-x.dcc-servers-Metrics: carlson; whitelist

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : PPPv6 Problem statement and requirements
	Author(s)       : J. Hu, et al.
	Filename        : draft-hu-pppext-ipv6cp-requirements-00.txt
	Pages           : 6
	Date            : 2010-10-17

The IPv6 Control Protocol (IPv6CP) is a NCP that allows for the
negotiation of parameters for an IPv6 interface over PPP. In IPv6
networks, PPP (PPPoE) will still be an important mechanism for
connecting broadband access users. However, IPv6CP only defines the
Interface-Identifier option, other parameters such as IPv6 Address,
Primary and alternative DNS server addresses, and delegated prefix
have to be configured by other methods rather than IPv6CP.

This document describes problems the ISPs faced and lists
requirements related when deploying IPv6 in broadband access network
over PPP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-hu-pppext-ipv6cp-requirements-00.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-hu-pppext-ipv6cp-requirements-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--

--------------060207020509060101030302
Content-Type: message/rfc822;
 name="Attached Message"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="Attached Message"

Return-Path: <i-d-announce-bounces@ietf.org>
X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on
	carlson.workingcode.com
X-Spam-Level: 
X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00
	autolearn=ham version=3.2.4
Received: from mail.ietf.org (mail.ietf.org [IPv6:2001:1890:1112:1::20])
	by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id o9I2kjLv028491
	for <carlsonj@workingcode.com>; Sun, 17 Oct 2010 22:46:45 -0400 (EDT)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by core3.amsl.com (Postfix) with ESMTP id 06AA33A6C6C;
	Sun, 17 Oct 2010 19:45:04 -0700 (PDT)
X-Original-To: i-d-announce@ietf.org
Delivered-To: i-d-announce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0)
	id 2CAC23A6A3E; Sun, 17 Oct 2010 19:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action:draft-hu-pppext-ipv6cp-extensions-00.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20101018024502.2CAC23A6A3E@core3.amsl.com>
Date: Sun, 17 Oct 2010 19:45:01 -0700 (PDT)
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/i-d-announce>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
	<mailto:i-d-announce-request@ietf.org?subject=subscribe>
Sender: i-d-announce-bounces@ietf.org
Errors-To: i-d-announce-bounces@ietf.org
X-DCC-x.dcc-servers-Metrics: carlson; whitelist

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : PPP IPv6 Control Protocol Extensions
	Author(s)       : J. Hu, et al.
	Filename        : draft-hu-pppext-ipv6cp-extensions-00.txt
	Pages           : 11
	Date            : 2010-10-17

The IPv6 Control Protocol (IPv6CP) is one of Network Control
Protocols(NCPs) that are defined by the Point-to-Point Protocol(PPP)
for establishing and configuring different network protocols.

This document extends the IPv6CP for negotiating and configuring IPv6
network parameters over PPP links, including IPv6 address, IPv6
prefix, primary and alternative DNS server addresses.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-hu-pppext-ipv6cp-extensions-00.txt

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

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

--NextPart
Content-Type: Message/External-body;
	name="draft-hu-pppext-ipv6cp-extensions-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--

--------------060207020509060101030302--

From carlsonj@workingcode.com  Mon Oct 18 11:55:36 2010
Return-Path: <carlsonj@workingcode.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 34FB33A69F0 for <pppext@core3.amsl.com>; Mon, 18 Oct 2010 11:55:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.171
X-Spam-Level: 
X-Spam-Status: No, score=-102.171 tagged_above=-999 required=5 tests=[AWL=-0.172, 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 jSOCGkXXWpMS for <pppext@core3.amsl.com>; Mon, 18 Oct 2010 11:55:35 -0700 (PDT)
Received: from carlson.workingcode.com (carlsonj-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1d9::2]) by core3.amsl.com (Postfix) with ESMTP id 4362A3A6BBC for <pppext@ietf.org>; Mon, 18 Oct 2010 11:55:35 -0700 (PDT)
Received: from [10.50.23.149] (gate.abinitio.com [65.170.40.132]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id o9IIm8c0012993 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 18 Oct 2010 14:48:08 -0400 (EDT)
Message-ID: <4CBC9666.5060302@workingcode.com>
Date: Mon, 18 Oct 2010 14:48:06 -0400
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090605)
MIME-Version: 1.0
To: "pppext@ietf.org" <pppext@ietf.org>
References: <20101018023005.360693A6C7A@core3.amsl.com>
In-Reply-To: <20101018023005.360693A6C7A@core3.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-DCC-sonic.net-Metrics: carlson; whitelist
Cc: chenyq@ctbri.com.cn, huj@ctbri.com.cn, maodf@chinatelecom.com.cn, zhaohl@ctbri.com.cn
Subject: Re: [Pppext] I-D Action:draft-hu-pppext-ipv6cp-requirements-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Oct 2010 18:55:36 -0000

> 	Title           : PPPv6 Problem statement and requirements
> 	Author(s)       : J. Hu, et al.
> 	Filename        : draft-hu-pppext-ipv6cp-requirements-00.txt

I've read this draft, and I have a few initial fairly high-level
questions about it before offering any detailed comments.  (And since
the second draft appears to depend on the first, it seems that this one
is the right place to start.)

1.  The "Problem Statement" contains many assertions about problems
    with the design and use of IPv6CP.  But there are many known and
    interoperable implementations available today.  Are these newly
    discovered problems?  And do any of the existing implementations
    suffer from them?  (In other words: "what problems need to be
    fixed?")

2.  Many of the issues raised are not specifically related to PPP,
    and are issues any time you have an IPv6 link over any datalink
    medium, and when used in a particular type of deployment.  Why
    are the solutions specific to IPv6CP and not general in nature?

3.  Have you read through the working group archives?  Many of these
    issues have been addressed over the years -- some of them more
    than once.  In particular, there's established working group
    consensus that the results of RFC 1877 should not be replicated
    for IPv6.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

From hujie.331@gmail.com  Wed Oct 20 06:05:32 2010
Return-Path: <hujie.331@gmail.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C96473A67F9 for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 06:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.379
X-Spam-Level: 
X-Spam-Status: No, score=-0.379 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, TVD_SPACE_RATIO=2.219]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3k19QsVVRt7C for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 06:05:32 -0700 (PDT)
Received: from mail-ww0-f47.google.com (mail-ww0-f47.google.com [74.125.82.47]) by core3.amsl.com (Postfix) with ESMTP id 210703A6768 for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 06:05:31 -0700 (PDT)
Received: by wwb28 with SMTP id 28so3616461wwb.16 for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 06:07:04 -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=zyFfV3kBsgfV2hswCSY5217Ji7H7DhB5v6WbZUuyo2I=; b=Wc9R5xU6EyXytiw+q8zW+o17vBVe2y5XxPqMggNASFvWk1sRJ68dmngdqwJpv5lWHq foFfPrcEHg9KD5iDGHDZeEeGawVKZbC/VtqjRKepM1ijm/C6VDFFjhMJSM/WTbfoqgJa U0p4lrBW+jaUvhQND9O5XI3XxT+SAl8Rjam94=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=xYUKaXCMOhxr46651iAry80AhGQUtNjWErzYi+HAEt3u2yGYybdRiHsUcTQ2UUN0Yp ftyipPdp1mCXI++LPHT4rA7MUxEQBUpc5jx4DwUmPhpX+2RmkAKp9M4mKSrb/ATxrZRU PswnFNFokhsQlAHRAJ9Ly9DmW3qC2GMBXiwM8=
MIME-Version: 1.0
Received: by 10.216.82.197 with SMTP id o47mr7599527wee.45.1287580023898; Wed, 20 Oct 2010 06:07:03 -0700 (PDT)
Received: by 10.216.3.140 with HTTP; Wed, 20 Oct 2010 06:07:03 -0700 (PDT)
Date: Wed, 20 Oct 2010 21:07:03 +0800
Message-ID: <AANLkTi=R8S96QhWVyf-DMjrn4VhxEwBnSHkFzFdcRu2n@mail.gmail.com>
From: Jie Hu <hujie.331@gmail.com>
To: pppext@core3.amsl.com
Content-Type: multipart/alternative; boundary=001636eefd2af1ebc404930c15c5
Subject: [Pppext]  I-D Action:draft-hu-pppext-ipv6cp-requirements-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 13:09:00 -0000

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



--001636eefd2af1ebc404930c15c5
Content-Type: text/html; charset=ISO-8859-1



--001636eefd2af1ebc404930c15c5--

From carlsonj@workingcode.com  Wed Oct 20 06:29:51 2010
Return-Path: <carlsonj@workingcode.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A51F63A67D9 for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 06:29:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.157
X-Spam-Level: 
X-Spam-Status: No, score=-102.157 tagged_above=-999 required=5 tests=[AWL=-0.158, 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 3Po+XsJPJgDX for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 06:29:50 -0700 (PDT)
Received: from carlson.workingcode.com (carlsonj-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1d9::2]) by core3.amsl.com (Postfix) with ESMTP id DAF293A67D1 for <pppext@ietf.org>; Wed, 20 Oct 2010 06:29:49 -0700 (PDT)
Received: from [10.50.23.149] (gate.abinitio.com [65.170.40.132]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id o9KDV5jm020460 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Oct 2010 09:31:07 -0400 (EDT)
Message-ID: <4CBEEF16.1030304@workingcode.com>
Date: Wed, 20 Oct 2010 09:31:02 -0400
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090605)
MIME-Version: 1.0
To: huj@ctbri.com.cn
References: <201010200936.o9K9auaj016890@carlson.workingcode.com>
In-Reply-To: <201010200936.o9K9auaj016890@carlson.workingcode.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-DCC-x.dcc-servers-Metrics: carlson; whitelist
Cc: pppext@ietf.org
Subject: Re: [Pppext] I-D Action:draft-hu-pppext-ipv6cp-requirements-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 13:29:51 -0000

[Standard email text quoting instead of highlights would be appreciated.
 Long threads with more than one contributor can get confusing otherwise.]

huj@ctbri.com.cn wrote:
> > >       Title           : PPPv6 Problem statement and requirements
> > >       Author(s)       : J. Hu, et al.
> > >       Filename        : draft-hu-pppext-ipv6cp-requirements-00.txt
[...]
> > 1.  The "Problem Statement" contains many assertions about problems
> >    with the design and use of IPv6CP.  But there are many known and
> >    interoperable implementations available today.  Are these newly
> >    discovered problems?  And do any of the existing implementations
> >    suffer from them?  (In other words: "what problems need to be
> >    fixed?")
>
> From the perspective of the ISP who wish to deliver the IPv6 servcies
> over PPP,
> and in the same way as for IPv4, the problems listed in the "Problem
> Statement"
> are all needed to be solved.  :-)
>
> Some are well known, and some may be not fully discussed like,
>
>    o More transaction steps caused by extra control protocols
>       introduced will result in longer response time and higher risk of
>       exception.

Has this problem been measured anywhere?

Are we talking about two extra packets?  Perhaps four?

What sorts of "risks" are involved?  How often do they happen and how
do they compare with the risks of the proposed solution?  Is there any
way to mitigate the risks?

My question quoted above wasn't a request for a restatement of the
same specific claims made in the draft.  I've already read the draft.
Instead, I'm asking if anyone has documented any actual problems in
real systems, and further if those problems stem from fundamental
protocol issues (which we could fix here) or from poor implementations
(which we cannot).

>    o How to determine the moment when the status of IPv6CP negotiation
>       comes to "OPEN", so as to get corresponding AAA activities started?

This is an implementation issue and is out of scope in this working
group.

For what it's worth, the typical answer (on a BSD-like system) is that
the driver will cause the IFF_RUNNING flag to be set on the IP
interface when the corresponding NCP reaches Opened state.
Implementation issues for some specific system may vary and are (as I
mentioned) out of scope here.

>    o ISPs have to change current network infrastructure accordingly,
>       such as installing DHCPv6 server somewhere in the network
>       (standalone or embedded) which will not only increase both CAPEX
>       and OPEX, but result in scalability problems when the number of
>       subscribers grows.

Change in what way?

If this refers to the fact that ISPs will need upgraded or otherwise
modified equipment -- and perhaps altogether new gear -- to deal with
IPv6, then this is a known issue, and not something that can be solved
in PPP.

If this refers to the need to understand and use new protocols with
IPv6 than were previously used for IPv4, then this is a general
problem.  It doesn't just affect PPP; it affects everything.

It almost sounds like the text above is attempting to assert that
modifying PPP will somehow be "simpler."  But that's obviously false,
because existing equipment (including gear manufactured in the last
decade or so) already has built-in support for the existing IPv6CP in
PPP as well as DHCPv6 and other relevant protocols.  *ANY*
newly-designed protocol extensions will take years to make it to the
field in usable form.  Thus, additions made here will only slow things
down.

>    o Some unnecessary functions will be involved. For example,
>       functions like Address Resolution, On-link Prefix List
>       Advertisement, Default Router Advertisement, etc. defined in ND
>       are actually not needed for a simple PPP link.

Those sound out of scope for this working group.  They sound like
issues for one of the IPv6 or routing groups instead.

However, I'll observe that the necessity depends on the deployment.
In a system that has both PPP and other links, the fact that all of
them run the same router and neighbor discovery is a big benefit, and
not a defect.  It means that everything works the same way everywhere
-- which greatly enhances manageability and reliability.

>    o Individual active state machine has to be maintained for each
>       protocol, and conflicts may exist (such as multiple lifetime
>       counters)

That sort of problem does occur if there's duplication of effort, as
is proposed in these drafts.

I do not see how this occurs with the existing documented protocols.
This claim will require substantially more detail.

> > 2.  Many of the issues raised are not specifically related to PPP,
> >    and are issues any time you have an IPv6 link over any datalink
> >    medium, and when used in a particular type of deployment.  Why
> >    are the solutions specific to IPv6CP and not general in nature?
>
> We don't want to comment on the current mechanisms of configuring IPv6,
> like ND,
> DHCPv6, and the interoperable issues related.  ;-)
> PPP is a very simple kind of datalink for both IPv4 and IPv6, where
> things like address
> resolution, default gateway are actually not needed.
> So, why can't we make it simple as what we did in IPv4?

If there are people having difficulties with IPv6, Neighbor Discovery,
or DHCPv6, I believe that the right place to address those issues
would be in working groups that focus on these areas, or perhaps in
deployment-related working groups.

The reasons we don't want to design new solutions for problems that
have already been solved using other protocols are:

  - Creating multiple solutions to the same problem causes new
    problems: namely that implementors who implement both PPP and DHCP
    will need to figure out what to do when the configuration
    information from PPP conflicts with the information from other
    sources.  This is a nearly intractable problem for IPv4, and
    (speaking as an implementor) we don't wish to see it spread.

  - There's simply no hope that PPP could adequately fill the role
    that DHCP serves.  DHCP has far too many useful extensions for us
    to repeat that working group's effort in any reasonable manner.
    Similar things are true for Neighbor Discovery and Router
    Advertisements and for the general-purpose routing protocols.

  - It's a waste of time and effort.  It produces considerably more
    work for PPP implementors and vendors who end up needing to
    support "all" available mechanisms rather than using just the
    purpose-built ones.

  - Any new protocol or extensions designed here (or in other IETF
    groups) will take a long time to be specified, implemented,
    tested, and finally deployed.  If someone is having a problem now
    with IPv6 deployment due to a perceived lack of features in PPP,
    any resolution we have will be at least months or years in coming.
    Existing protocols, by contrast, are available right now.

  - It causes an undesirable split between PPP and other datalink
    protocols.  For simplicity of management, ease of use,
    reliability, and implementation reasons, I strongly prefer to see
    the same mechanisms used for all, rather than having
    datalink-specific mechanisms tailored to special environments.

There's a strong bias here against creating new options and protocols
just for mere convenience, particularly when they duplicate things
that already exist and are known to work.  New extensions must show
actual need in some form, such as unalterable defects in the existing
solutions.

> > 3.  Have you read through the working group archives?  Many of these
> >    issues have been addressed over the years -- some of them more
> >    than once.  In particular, there's established working group
> >    consensus that the results of RFC 1877 should not be replicated
> >    for IPv6.
>
> Yes, of course, we've read the archives(after 2004) carefully.
> Right, several drafts have ever been posted trying to solve some of
> these problems, but not moving forward.

Correct; there was no consensus to do so.

> That's why we wrote a requirement draft to clarify the problems.
> We don't want to doubt the consensus established before.  While frankly,
> we do have concerns.
> The discussions and consensus were made many years ago. At that time we
> guess there were no one
> really planning to deploy IPv6 in their networks for commercial use
> right way.

I can't speak directly for others here, but I do know that I was
involved in a couple of implementations and deployments of IPv6, and I
suspect that several other folks here were as well.  We were doing
this stuff over a decade ago.

Again, if there are new problems, then I encourage those with direct
experience with the problems to document them clearly.  I'm not swayed
by references to vague "risks" or clear misunderstandings, nor would I
expect the consensus to move much without details.

> But now, under the great pressure of IPv4 address exhaustion, we try to
> evaluate critical mechanisms for IPv6
> deployment carefully, including the PPP scenario, always keeping the
> CAPEX, OPEX, migrating smoothly etc. in mind,
> then brought up the problems in the draft.

That's great, but there's no detail.

> One RFC will make real sense only if it is verified by implementations
> in real world and finally got widely deployed.
> RFC 1887 could be an example, no matter what the background is and why
> it was produced.
> On the other hand, PPP WG has done great job for IPv4, why not do it
> again for IPv6?
> In particular, currently IPCP works quite well for establishing IPv4
> connectivity and with AAA infrastructure too.
> Why not continue the same way for IPv6 over the simple PPP link?

Because it was a mistake.

I assume you're referring to RFC 1877 (the name server extensions for
PPP) and not 1887 (IPv6 address allocation).

RFC 1877 was a mistake because there already was an accepted solution
for this problem: folks had been running BOOTP and (later) DHCP over
SLIP and PPP for many years.  And, if you look at the draft closely,
you'll note that it didn't go through the working group process.
Instead, it just documented what one vendor chose to deploy without
benefit of the usual standards review (and apparently without having
secured the Option Type numbers through IANA).

Other vendors had to suffer with the consequences, which included deep
conflicts and duplications that exist to this day.  Resolving data
that comes from PPP on some links and from DHCP on others is
complicated.

I don't think repeating mistakes is a good idea, and I doubt that
you'll find much consensus here for that sort of extension in IPv6CP.

> So, we kindly suggest the WG should reconsider that.

You will need to convince others here to support your effort.  I'm
nominally the chair of the group, but I'm just one member.  I'll defer
to the consensus.

But, in my opinion, these drafts have a long way to go in order to be
persuasive, and the outlook seems hazy to me.  I don't see how we can
proceed with a deliberate duplication of effort expended by other
working groups.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

From carlsonj@workingcode.com  Wed Oct 20 06:57:31 2010
Return-Path: <carlsonj@workingcode.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 459943A6819 for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 06:57:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.444
X-Spam-Level: 
X-Spam-Status: No, score=-102.444 tagged_above=-999 required=5 tests=[AWL=0.155, 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 PC-devZl+Pp9 for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 06:57:30 -0700 (PDT)
Received: from carlson.workingcode.com (carlsonj-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1d9::2]) by core3.amsl.com (Postfix) with ESMTP id 349873A680B for <pppext@ietf.org>; Wed, 20 Oct 2010 06:57:30 -0700 (PDT)
Received: from [10.50.23.149] (gate.abinitio.com [65.170.40.132]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id o9KDwtKr020729 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Oct 2010 09:58:56 -0400 (EDT)
Message-ID: <4CBEF59F.1070107@workingcode.com>
Date: Wed, 20 Oct 2010 09:58:55 -0400
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090605)
MIME-Version: 1.0
To: huj@ctbri.com.cn
References: <201010200936.o9K9auaj016890@carlson.workingcode.com> <4CBEEF16.1030304@workingcode.com>
In-Reply-To: <4CBEEF16.1030304@workingcode.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-DCC-x.dcc-servers-Metrics: carlson; whitelist
Cc: pppext@ietf.org
Subject: Re: [Pppext] I-D Action:draft-hu-pppext-ipv6cp-requirements-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 13:57:31 -0000

James Carlson wrote:
> You will need to convince others here to support your effort.  I'm
> nominally the chair of the group, but I'm just one member.  I'll defer
> to the consensus.

To be precise, I should have said "just one participant."  It's not a
membership-based organization.  Sorry about the poor word choice; it
wasn't meant to be exclusionary.

In any event, the point remains the same.  I don't yet see the value in
what's being proposed, and it seems to be just a repetition of past
discarded proposals, but if there's a consensus among participants
otherwise, I'll go with that.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

From vjs@calcite.rhyolite.com  Wed Oct 20 07:28:11 2010
Return-Path: <vjs@calcite.rhyolite.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4851D3A69D7 for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 07:28:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WfRhqgGqurOI for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 07:28:10 -0700 (PDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [IPv6:2001:4978:230::3]) by core3.amsl.com (Postfix) with ESMTP id DD2A73A6830 for <pppext@ietf.org>; Wed, 20 Oct 2010 07:28:09 -0700 (PDT)
Received: from calcite.rhyolite.com (localhost [127.0.0.1]) by calcite.rhyolite.com (8.14.4/8.14.4) with ESMTP id o9KETNWQ092486 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) env-from <vjs@calcite.rhyolite.com>; Wed, 20 Oct 2010 14:29:24 GMT
Received: (from vjs@localhost) by calcite.rhyolite.com (8.14.4/8.14.4/Submit) id o9KETNpi092485; Wed, 20 Oct 2010 14:29:23 GMT
Date: Wed, 20 Oct 2010 14:29:23 GMT
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <201010201429.o9KETNpi092485@calcite.rhyolite.com>
To: carlsonj@workingcode.com, huj@ctbri.com.cn
In-Reply-To: <4CBEEF16.1030304@workingcode.com>
X-DCC-Rhyolite-Metrics: calcite.rhyolite.com; whitelist
Cc: pppext@ietf.org
Subject: Re: [Pppext] I-D Action:draft-hu-pppext-ipv6cp-requirements-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 14:28:11 -0000

> From: James Carlson <carlsonj@workingcode.com>
> To: huj@ctbri.com.cn
> Cc: pppext@ietf.org

> > Yes, of course, we've read the archives(after 2004) carefully.
> > Right, several drafts have ever been posted trying to solve some of
> > these problems, but not moving forward.
>
> Correct; there was no consensus to do so.

There was a clear consensus to not do so.  That differs from
a lack of consensus.


> > But now, under the great pressure of IPv4 address exhaustion, we try to
> > evaluate critical mechanisms for IPv6

IPv4 addresses will be exhausted before a standards track RFC could
be approved.  Any real IPv6/PPP problems at this late date must be
addressed elsewhere.

> > One RFC will make real sense only if it is verified by implementations
> > in real world and finally got widely deployed.

No RFC can be approved by the IAB etc. in time to encourage independent
implementations until long after the last IPv4 address has been assigned.

China Telecom must have started testing and working with IPv6 years
ago, just like the rest of us.  If China Telecom really thinks that
the problems described in the drafts must be solved by extending the
point-to-point protocol instead of using the existing, familiar,
standardized, and widely implemented mechanisms, then China Telecom
must have already built, tested, and deployed in alpha testing prototype
implementations of the proposed PPP extensions.  What has been observed,
especially in the alpha testing?


Vernon Schryver    vjs@rhyolite.com

From jacniq@gmail.com  Wed Oct 20 10:23:46 2010
Return-Path: <jacniq@gmail.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ADE1B3A68F6 for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 10:23:46 -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=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 uwkMFoCznjNw for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 10:23:44 -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 7BEC43A69E7 for <pppext@ietf.org>; Wed, 20 Oct 2010 10:23:43 -0700 (PDT)
Received: by bwz14 with SMTP id 14so3070741bwz.31 for <pppext@ietf.org>; Wed, 20 Oct 2010 10:25:16 -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; bh=bFjCRlP0IccSMGw449FUomKhg3vB4HBp21GfQkfRZ3c=; b=xX0IFZGuE1VNUgGB/zt2OMrlY+VtzePzwBOIS2FtoS5beIgFggS+Gp0YzKw1Fl4WJw mAydwz/Ak5lBxiSUi0raMQ7AKeFCDIteMcAqLroi0JdJNzHPzEKxBigWTi8SLXsrj8kB EnX/eypcWONvJQ3dIMBWDbTunHJtsMxdyjU4I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ZcMCU6A3zudhc7MtVk5G7m9iowwmNhpcz6AejC6Um/xHyF24i5dmVZVwN/d9knAxsE y703gOxejxEiExqc+dnCVAsy7kafbI+7WOTCCYYPQG2T98aSpsoLJlykr/Wn1spTLlN4 kUbtwz41DuISGxLR1qn106R+zeBmMlIpxNGqk=
MIME-Version: 1.0
Received: by 10.204.27.20 with SMTP id g20mr7032344bkc.114.1287595514711; Wed, 20 Oct 2010 10:25:14 -0700 (PDT)
Received: by 10.204.66.129 with HTTP; Wed, 20 Oct 2010 10:25:14 -0700 (PDT)
In-Reply-To: <4CBEEF16.1030304@workingcode.com>
References: <201010200936.o9K9auaj016890@carlson.workingcode.com> <4CBEEF16.1030304@workingcode.com>
Date: Thu, 21 Oct 2010 01:25:14 +0800
Message-ID: <AANLkTi=Ew3MW9_L-jKPsdGU8SYGYzwnuzB_yhKOexpco@mail.gmail.com>
From: Jacni Qin <jacniq@gmail.com>
To: James Carlson <carlsonj@workingcode.com>
Content-Type: multipart/alternative; boundary=000325559ee644cd6404930fb125
Cc: pppext@ietf.org, huj@ctbri.com.cn
Subject: Re: [Pppext] I-D Action:draft-hu-pppext-ipv6cp-requirements-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 17:23:46 -0000

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

Dear James,

Please see inline,

On Wed, Oct 20, 2010 at 9:31 PM, James Carlson <carlsonj@workingcode.com>wrote:

> [Standard email text quoting instead of highlights would be appreciated.
>  Long threads with more than one contributor can get confusing otherwise.]
>
> huj@ctbri.com.cn wrote:
> > > >       Title           : PPPv6 Problem statement and requirements
> > > >       Author(s)       : J. Hu, et al.
> > > >       Filename        : draft-hu-pppext-ipv6cp-requirements-00.txt
> [...]
> > > 1.  The "Problem Statement" contains many assertions about problems
> > >    with the design and use of IPv6CP.  But there are many known and
> > >    interoperable implementations available today.  Are these newly
> > >    discovered problems?  And do any of the existing implementations
> > >    suffer from them?  (In other words: "what problems need to be
> > >    fixed?")
> >
> > From the perspective of the ISP who wish to deliver the IPv6 servcies
> > over PPP,
> > and in the same way as for IPv4, the problems listed in the "Problem
> > Statement"
> > are all needed to be solved.  :-)
> >
> > Some are well known, and some may be not fully discussed like,
> >
> >    o More transaction steps caused by extra control protocols
> >       introduced will result in longer response time and higher risk of
> >       exception.
>
> Has this problem been measured anywhere?
>
> Are we talking about two extra packets?  Perhaps four?
>
> What sorts of "risks" are involved?  How often do they happen and how
> do they compare with the risks of the proposed solution?  Is there any
> way to mitigate the risks?
>

--> Get all things done by IPv6CP but not involving ND or DHCPv6 ? ;-)


> My question quoted above wasn't a request for a restatement of the
> same specific claims made in the draft.  I've already read the draft.
> Instead, I'm asking if anyone has documented any actual problems in
> real systems, and further if those problems stem from fundamental
> protocol issues (which we could fix here) or from poor implementations
> (which we cannot).
>
> >    o How to determine the moment when the status of IPv6CP negotiation
> >       comes to "OPEN", so as to get corresponding AAA activities started?
>
> This is an implementation issue and is out of scope in this working
> group.
>

--> I guess the authors mean that since IPv6CP just provides interface-id,
and only when the IPv6 addresses
and other elements are successfully configured by ND or DHCPv6, the status
of NCP can come to "OPEN".


>
> For what it's worth, the typical answer (on a BSD-like system) is that
> the driver will cause the IFF_RUNNING flag to be set on the IP
> interface when the corresponding NCP reaches Opened state.
> Implementation issues for some specific system may vary and are (as I
> mentioned) out of scope here.
>
> >    o ISPs have to change current network infrastructure accordingly,
> >       such as installing DHCPv6 server somewhere in the network
> >       (standalone or embedded) which will not only increase both CAPEX
> >       and OPEX, but result in scalability problems when the number of
> >       subscribers grows.
>
> Change in what way?
>

--> As mentioned here, "installing DHCPv6 server somewhere" ?
Currently, there is no DHCPv4 server installed for the IPv4 over PPP.


>
> If this refers to the fact that ISPs will need upgraded or otherwise
> modified equipment -- and perhaps altogether new gear -- to deal with
> IPv6, then this is a known issue, and not something that can be solved
> in PPP.
>
> If this refers to the need to understand and use new protocols with
> IPv6 than were previously used for IPv4, then this is a general
> problem.  It doesn't just affect PPP; it affects everything.
>
> It almost sounds like the text above is attempting to assert that
> modifying PPP will somehow be "simpler."  But that's obviously false,
> because existing equipment (including gear manufactured in the last
> decade or so) already has built-in support for the existing IPv6CP in
> PPP as well as DHCPv6 and other relevant protocols.  *ANY*
> newly-designed protocol extensions will take years to make it to the
> field in usable form.  Thus, additions made here will only slow things
> down.
>
> >    o Some unnecessary functions will be involved. For example,
> >       functions like Address Resolution, On-link Prefix List
> >       Advertisement, Default Router Advertisement, etc. defined in ND
> >       are actually not needed for a simple PPP link.
>
> Those sound out of scope for this working group.  They sound like
> issues for one of the IPv6 or routing groups instead.
>

--> I think this is a special case for PPP. Those are still needed for other
date links, such as Ethernet.

>
> However, I'll observe that the necessity depends on the deployment.
> In a system that has both PPP and other links, the fact that all of
> them run the same router and neighbor discovery is a big benefit, and
> not a defect.  It means that everything works the same way everywhere
> -- which greatly enhances manageability and reliability.
>
> >    o Individual active state machine has to be maintained for each
> >       protocol, and conflicts may exist (such as multiple lifetime
> >       counters)
>
> That sort of problem does occur if there's duplication of effort, as
> is proposed in these drafts.
>
> I do not see how this occurs with the existing documented protocols.
> This claim will require substantially more detail.
>
> > > 2.  Many of the issues raised are not specifically related to PPP,
> > >    and are issues any time you have an IPv6 link over any datalink
> > >    medium, and when used in a particular type of deployment.  Why
> > >    are the solutions specific to IPv6CP and not general in nature?
> >
> > We don't want to comment on the current mechanisms of configuring IPv6,
> > like ND,
> > DHCPv6, and the interoperable issues related.  ;-)
> > PPP is a very simple kind of datalink for both IPv4 and IPv6, where
> > things like address
> > resolution, default gateway are actually not needed.
> > So, why can't we make it simple as what we did in IPv4?
>
> If there are people having difficulties with IPv6, Neighbor Discovery,
> or DHCPv6, I believe that the right place to address those issues
> would be in working groups that focus on these areas, or perhaps in
> deployment-related working groups.
>
> The reasons we don't want to design new solutions for problems that
> have already been solved using other protocols are:
>
>  - Creating multiple solutions to the same problem causes new
>    problems: namely that implementors who implement both PPP and DHCP
>    will need to figure out what to do when the configuration
>    information from PPP conflicts with the information from other
>    sources.  This is a nearly intractable problem for IPv4, and
>    (speaking as an implementor) we don't wish to see it spread.
>
>  - There's simply no hope that PPP could adequately fill the role
>    that DHCP serves.  DHCP has far too many useful extensions for us
>    to repeat that working group's effort in any reasonable manner.
>    Similar things are true for Neighbor Discovery and Router
>    Advertisements and for the general-purpose routing protocols.
>

--> While many of those extensions are not needed for PPP link.

>
>  - It's a waste of time and effort.  It produces considerably more
>    work for PPP implementors and vendors who end up needing to
>    support "all" available mechanisms rather than using just the
>    purpose-built ones.
>

--> There have been overlapping functions between ND and DHCPv6 which result
in
implementation issues. Why not solving it for PPP by PPP itself?
You may argue that this will further aggravate the issue, but from different
perspective,
this is a straightforward way rather than waiting for ND and DHCPv6 solving
that problem.
:-)


>
>  - Any new protocol or extensions designed here (or in other IETF
>    groups) will take a long time to be specified, implemented,
>    tested, and finally deployed.  If someone is having a problem now
>    with IPv6 deployment due to a perceived lack of features in PPP,
>    any resolution we have will be at least months or years in coming.
>    Existing protocols, by contrast, are available right now.
>
>  - It causes an undesirable split between PPP and other datalink
>    protocols.  For simplicity of management, ease of use,
>    reliability, and implementation reasons, I strongly prefer to see
>    the same mechanisms used for all, rather than having
>    datalink-specific mechanisms tailored to special environments.
>
> There's a strong bias here against creating new options and protocols
> just for mere convenience, particularly when they duplicate things
> that already exist and are known to work.  New extensions must show
> actual need in some form, such as unalterable defects in the existing
> solutions.
>
> > > 3.  Have you read through the working group archives?  Many of these
> > >    issues have been addressed over the years -- some of them more
> > >    than once.  In particular, there's established working group
> > >    consensus that the results of RFC 1877 should not be replicated
> > >    for IPv6.
> >
> > Yes, of course, we've read the archives(after 2004) carefully.
> > Right, several drafts have ever been posted trying to solve some of
> > these problems, but not moving forward.
>
> Correct; there was no consensus to do so.
>
> > That's why we wrote a requirement draft to clarify the problems.
> > We don't want to doubt the consensus established before.  While frankly,
> > we do have concerns.
> > The discussions and consensus were made many years ago. At that time we
> > guess there were no one
> > really planning to deploy IPv6 in their networks for commercial use
> > right way.
>
> I can't speak directly for others here, but I do know that I was
> involved in a couple of implementations and deployments of IPv6, and I
> suspect that several other folks here were as well.  We were doing
> this stuff over a decade ago.
>
> Again, if there are new problems, then I encourage those with direct
> experience with the problems to document them clearly.  I'm not swayed
> by references to vague "risks" or clear misunderstandings, nor would I
> expect the consensus to move much without details.
>
> > But now, under the great pressure of IPv4 address exhaustion, we try to
> > evaluate critical mechanisms for IPv6
> > deployment carefully, including the PPP scenario, always keeping the
> > CAPEX, OPEX, migrating smoothly etc. in mind,
> > then brought up the problems in the draft.
>
> That's great, but there's no detail.
>
> > One RFC will make real sense only if it is verified by implementations
> > in real world and finally got widely deployed.
> > RFC 1887 could be an example, no matter what the background is and why
> > it was produced.
> > On the other hand, PPP WG has done great job for IPv4, why not do it
> > again for IPv6?
> > In particular, currently IPCP works quite well for establishing IPv4
> > connectivity and with AAA infrastructure too.
> > Why not continue the same way for IPv6 over the simple PPP link?
>
> Because it was a mistake.
>
> I assume you're referring to RFC 1877 (the name server extensions for
> PPP) and not 1887 (IPv6 address allocation).
>
> RFC 1877 was a mistake because there already was an accepted solution
> for this problem: folks had been running BOOTP and (later) DHCP over
> SLIP and PPP for many years.  And, if you look at the draft closely,
> you'll note that it didn't go through the working group process.
> Instead, it just documented what one vendor chose to deploy without
> benefit of the usual standards review (and apparently without having
> secured the Option Type numbers through IANA).
>

--> You mean the Type numbers in RFC1877 are not assigned by IANA?
I'm sorry if I missed something.

Cheers,
Jacni


>
> Other vendors had to suffer with the consequences, which included deep
> conflicts and duplications that exist to this day.  Resolving data
> that comes from PPP on some links and from DHCP on others is
> complicated.
>
> I don't think repeating mistakes is a good idea, and I doubt that
> you'll find much consensus here for that sort of extension in IPv6CP.
>
> > So, we kindly suggest the WG should reconsider that.
>
> You will need to convince others here to support your effort.  I'm
> nominally the chair of the group, but I'm just one member.  I'll defer
> to the consensus.
>
> But, in my opinion, these drafts have a long way to go in order to be
> persuasive, and the outlook seems hazy to me.  I don't see how we can
> proceed with a deliberate duplication of effort expended by other
> working groups.
>
> --
> James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>
> _______________________________________________
> Pppext mailing list
> Pppext@ietf.org
> https://www.ietf.org/mailman/listinfo/pppext
>

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

<font color=3D"#000000"><font face=3D"verdana,sans-serif">Dear James,<br><b=
r>Please see inline,<br></font></font><br><div class=3D"gmail_quote">On Wed=
, Oct 20, 2010 at 9:31 PM, James Carlson <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:carlsonj@workingcode.com">carlsonj@workingcode.com</a>&gt;</span> wro=
te:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">[Standard email t=
ext quoting instead of highlights would be appreciated.<br>
=A0Long threads with more than one contributor can get confusing otherwise.=
]<br>
<div class=3D"im"><br>
<a href=3D"mailto:huj@ctbri.com.cn">huj@ctbri.com.cn</a> wrote:<br>
&gt; &gt; &gt; =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : PPPv6 Problem statem=
ent and requirements<br>
&gt; &gt; &gt; =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : J. Hu, et al.<br>
&gt; &gt; &gt; =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-hu-pppext-ipv6cp=
-requirements-00.txt<br>
</div>[...]<br>
<div class=3D"im">&gt; &gt; 1. =A0The &quot;Problem Statement&quot; contain=
s many assertions about problems<br>
&gt; &gt; =A0 =A0with the design and use of IPv6CP. =A0But there are many k=
nown and<br>
&gt; &gt; =A0 =A0interoperable implementations available today. =A0Are thes=
e newly<br>
&gt; &gt; =A0 =A0discovered problems? =A0And do any of the existing impleme=
ntations<br>
&gt; &gt; =A0 =A0suffer from them? =A0(In other words: &quot;what problems =
need to be<br>
&gt; &gt; =A0 =A0fixed?&quot;)<br>
&gt;<br>
</div>&gt; From the perspective of the ISP who wish to deliver the IPv6 ser=
vcies<br>
&gt; over PPP,<br>
&gt; and in the same way as for IPv4, the problems listed in the &quot;Prob=
lem<br>
&gt; Statement&quot;<br>
&gt; are all needed to be solved. =A0:-)<br>
&gt;<br>
&gt; Some are well known, and some may be not fully discussed like,<br>
&gt;<br>
&gt; =A0 =A0o More transaction steps caused by extra control protocols<br>
&gt; =A0 =A0 =A0 introduced will result in longer response time and higher =
risk of<br>
&gt; =A0 =A0 =A0 exception.<br>
<br>
Has this problem been measured anywhere?<br>
<br>
Are we talking about two extra packets? =A0Perhaps four?<br>
<br>
What sorts of &quot;risks&quot; are involved? =A0How often do they happen a=
nd how<br>
do they compare with the risks of the proposed solution? =A0Is there any<br=
>
way to mitigate the risks?<br></blockquote><div><br>--&gt; Get all things d=
one by IPv6CP but not involving ND or DHCPv6 ? ;-) <br><br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1p=
x solid rgb(204, 204, 204); padding-left: 1ex;">

<br>
My question quoted above wasn&#39;t a request for a restatement of the<br>
same specific claims made in the draft. =A0I&#39;ve already read the draft.=
<br>
Instead, I&#39;m asking if anyone has documented any actual problems in<br>
real systems, and further if those problems stem from fundamental<br>
protocol issues (which we could fix here) or from poor implementations<br>
(which we cannot).<br>
<br>
&gt; =A0 =A0o How to determine the moment when the status of IPv6CP negotia=
tion<br>
&gt; =A0 =A0 =A0 comes to &quot;OPEN&quot;, so as to get corresponding AAA =
activities started?<br>
<br>
This is an implementation issue and is out of scope in this working<br>
group.<br></blockquote><div><br>--&gt; I guess the authors mean that since =
IPv6CP just provides interface-id, and only when the IPv6 addresses<br>and =
other elements are successfully configured by ND or DHCPv6, the status of N=
CP can come to &quot;OPEN&quot;.<br>
=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt=
 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
For what it&#39;s worth, the typical answer (on a BSD-like system) is that<=
br>
the driver will cause the IFF_RUNNING flag to be set on the IP<br>
interface when the corresponding NCP reaches Opened state.<br>
Implementation issues for some specific system may vary and are (as I<br>
mentioned) out of scope here.<br>
<br>
&gt; =A0 =A0o ISPs have to change current network infrastructure accordingl=
y,<br>
&gt; =A0 =A0 =A0 such as installing DHCPv6 server somewhere in the network<=
br>
&gt; =A0 =A0 =A0 (standalone or embedded) which will not only increase both=
 CAPEX<br>
&gt; =A0 =A0 =A0 and OPEX, but result in scalability problems when the numb=
er of<br>
&gt; =A0 =A0 =A0 subscribers grows.<br>
<br>
Change in what way?<br></blockquote><div><br>--&gt; As mentioned here, &quo=
t;installing DHCPv6 server somewhere&quot; ?<br>Currently, there is no DHCP=
v4 server installed for the IPv4 over PPP.<br>=A0<br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px soli=
d rgb(204, 204, 204); padding-left: 1ex;">

<br>
If this refers to the fact that ISPs will need upgraded or otherwise<br>
modified equipment -- and perhaps altogether new gear -- to deal with<br>
IPv6, then this is a known issue, and not something that can be solved<br>
in PPP.<br>
<br>
If this refers to the need to understand and use new protocols with<br>
IPv6 than were previously used for IPv4, then this is a general<br>
problem. =A0It doesn&#39;t just affect PPP; it affects everything.<br>
<br>
It almost sounds like the text above is attempting to assert that<br>
modifying PPP will somehow be &quot;simpler.&quot; =A0But that&#39;s obviou=
sly false,<br>
because existing equipment (including gear manufactured in the last<br>
decade or so) already has built-in support for the existing IPv6CP in<br>
PPP as well as DHCPv6 and other relevant protocols. =A0*ANY*<br>
newly-designed protocol extensions will take years to make it to the<br>
field in usable form. =A0Thus, additions made here will only slow things<br=
>
down.<br>
<br>
&gt; =A0 =A0o Some unnecessary functions will be involved. For example,<br>
&gt; =A0 =A0 =A0 functions like Address Resolution, On-link Prefix List<br>
&gt; =A0 =A0 =A0 Advertisement, Default Router Advertisement, etc. defined =
in ND<br>
&gt; =A0 =A0 =A0 are actually not needed for a simple PPP link.<br>
<br>
Those sound out of scope for this working group. =A0They sound like<br>
issues for one of the IPv6 or routing groups instead.<br></blockquote><div>=
<br>--&gt; I think this is a special case for PPP. Those are still needed f=
or other date links, such as Ethernet. <br></div><blockquote class=3D"gmail=
_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204,=
 204, 204); padding-left: 1ex;">

<br>
However, I&#39;ll observe that the necessity depends on the deployment.<br>
In a system that has both PPP and other links, the fact that all of<br>
them run the same router and neighbor discovery is a big benefit, and<br>
not a defect. =A0It means that everything works the same way everywhere<br>
-- which greatly enhances manageability and reliability.<br>
<br>
&gt; =A0 =A0o Individual active state machine has to be maintained for each=
<br>
&gt; =A0 =A0 =A0 protocol, and conflicts may exist (such as multiple lifeti=
me<br>
&gt; =A0 =A0 =A0 counters)<br>
<br>
That sort of problem does occur if there&#39;s duplication of effort, as<br=
>
is proposed in these drafts.<br>
<br>
I do not see how this occurs with the existing documented protocols.<br>
This claim will require substantially more detail.<br>
<div class=3D"im"><br>
&gt; &gt; 2. =A0Many of the issues raised are not specifically related to P=
PP,<br>
&gt; &gt; =A0 =A0and are issues any time you have an IPv6 link over any dat=
alink<br>
&gt; &gt; =A0 =A0medium, and when used in a particular type of deployment. =
=A0Why<br>
&gt; &gt; =A0 =A0are the solutions specific to IPv6CP and not general in na=
ture?<br>
&gt;<br>
</div>&gt; We don&#39;t want to comment on the current mechanisms of config=
uring IPv6,<br>
&gt; like ND,<br>
&gt; DHCPv6, and the interoperable issues related. =A0;-)<br>
&gt; PPP is a very simple kind of datalink for both IPv4 and IPv6, where<br=
>
&gt; things like address<br>
&gt; resolution, default gateway are actually not needed.<br>
&gt; So, why can&#39;t we make it simple as what we did in IPv4?<br>
<br>
If there are people having difficulties with IPv6, Neighbor Discovery,<br>
or DHCPv6, I believe that the right place to address those issues<br>
would be in working groups that focus on these areas, or perhaps in<br>
deployment-related working groups.<br>
<br>
The reasons we don&#39;t want to design new solutions for problems that<br>
have already been solved using other protocols are:<br>
<br>
 =A0- Creating multiple solutions to the same problem causes new<br>
 =A0 =A0problems: namely that implementors who implement both PPP and DHCP<=
br>
 =A0 =A0will need to figure out what to do when the configuration<br>
 =A0 =A0information from PPP conflicts with the information from other<br>
 =A0 =A0sources. =A0This is a nearly intractable problem for IPv4, and<br>
 =A0 =A0(speaking as an implementor) we don&#39;t wish to see it spread.<br=
>
<br>
 =A0- There&#39;s simply no hope that PPP could adequately fill the role<br=
>
 =A0 =A0that DHCP serves. =A0DHCP has far too many useful extensions for us=
<br>
 =A0 =A0to repeat that working group&#39;s effort in any reasonable manner.=
<br>
 =A0 =A0Similar things are true for Neighbor Discovery and Router<br>
 =A0 =A0Advertisements and for the general-purpose routing protocols.<br></=
blockquote><div><br>--&gt; While many of those extensions are not needed fo=
r PPP link. <br></div><blockquote class=3D"gmail_quote" style=3D"margin: 0p=
t 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1=
ex;">

<br>
 =A0- It&#39;s a waste of time and effort. =A0It produces considerably more=
<br>
 =A0 =A0work for PPP implementors and vendors who end up needing to<br>
 =A0 =A0support &quot;all&quot; available mechanisms rather than using just=
 the<br>
 =A0 =A0purpose-built ones.<br></blockquote><div><br>--&gt; There have been=
 overlapping functions between ND and DHCPv6 which result in<br>implementat=
ion issues. Why not solving it for PPP by PPP itself?<br>You may argue that=
 this will further aggravate the issue, but from different perspective,<br>
this is a straightforward way rather than waiting for ND and DHCPv6 solving=
 that problem.<br>:-)<br>=A0<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);=
 padding-left: 1ex;">

<br>
 =A0- Any new protocol or extensions designed here (or in other IETF<br>
 =A0 =A0groups) will take a long time to be specified, implemented,<br>
 =A0 =A0tested, and finally deployed. =A0If someone is having a problem now=
<br>
 =A0 =A0with IPv6 deployment due to a perceived lack of features in PPP,<br=
>
 =A0 =A0any resolution we have will be at least months or years in coming.<=
br>
 =A0 =A0Existing protocols, by contrast, are available right now.<br>
<br>
 =A0- It causes an undesirable split between PPP and other datalink<br>
 =A0 =A0protocols. =A0For simplicity of management, ease of use,<br>
 =A0 =A0reliability, and implementation reasons, I strongly prefer to see<b=
r>
 =A0 =A0the same mechanisms used for all, rather than having<br>
 =A0 =A0datalink-specific mechanisms tailored to special environments.<br>
<br>
There&#39;s a strong bias here against creating new options and protocols<b=
r>
just for mere convenience, particularly when they duplicate things<br>
that already exist and are known to work. =A0New extensions must show<br>
actual need in some form, such as unalterable defects in the existing<br>
solutions.<br>
<div class=3D"im"><br>
&gt; &gt; 3. =A0Have you read through the working group archives? =A0Many o=
f these<br>
&gt; &gt; =A0 =A0issues have been addressed over the years -- some of them =
more<br>
&gt; &gt; =A0 =A0than once. =A0In particular, there&#39;s established worki=
ng group<br>
&gt; &gt; =A0 =A0consensus that the results of RFC 1877 should not be repli=
cated<br>
&gt; &gt; =A0 =A0for IPv6.<br>
&gt;<br>
</div>&gt; Yes, of course, we&#39;ve read the archives(after 2004) carefull=
y.<br>
&gt; Right, several drafts have ever been posted trying to solve some of<br=
>
&gt; these problems, but not moving forward.<br>
<br>
Correct; there was no consensus to do so.<br>
<br>
&gt; That&#39;s why we wrote a requirement draft to clarify the problems.<b=
r>
&gt; We don&#39;t want to doubt the consensus established before. =A0While =
frankly,<br>
&gt; we do have concerns.<br>
&gt; The discussions and consensus were made many years ago. At that time w=
e<br>
&gt; guess there were no one<br>
&gt; really planning to deploy IPv6 in their networks for commercial use<br=
>
&gt; right way.<br>
<br>
I can&#39;t speak directly for others here, but I do know that I was<br>
involved in a couple of implementations and deployments of IPv6, and I<br>
suspect that several other folks here were as well. =A0We were doing<br>
this stuff over a decade ago.<br>
<br>
Again, if there are new problems, then I encourage those with direct<br>
experience with the problems to document them clearly. =A0I&#39;m not swaye=
d<br>
by references to vague &quot;risks&quot; or clear misunderstandings, nor wo=
uld I<br>
expect the consensus to move much without details.<br>
<br>
&gt; But now, under the great pressure of IPv4 address exhaustion, we try t=
o<br>
&gt; evaluate critical mechanisms for IPv6<br>
&gt; deployment carefully, including the PPP scenario, always keeping the<b=
r>
&gt; CAPEX, OPEX, migrating smoothly etc. in mind,<br>
&gt; then brought up the problems in the draft.<br>
<br>
That&#39;s great, but there&#39;s no detail.<br>
<br>
&gt; One RFC will make real sense only if it is verified by implementations=
<br>
&gt; in real world and finally got widely deployed.<br>
&gt; RFC 1887 could be an example, no matter what the background is and why=
<br>
&gt; it was produced.<br>
&gt; On the other hand, PPP WG has done great job for IPv4, why not do it<b=
r>
&gt; again for IPv6?<br>
&gt; In particular, currently IPCP works quite well for establishing IPv4<b=
r>
&gt; connectivity and with AAA infrastructure too.<br>
&gt; Why not continue the same way for IPv6 over the simple PPP link?<br>
<br>
Because it was a mistake.<br>
<br>
I assume you&#39;re referring to RFC 1877 (the name server extensions for<b=
r>
PPP) and not 1887 (IPv6 address allocation).<br>
<br>
RFC 1877 was a mistake because there already was an accepted solution<br>
for this problem: folks had been running BOOTP and (later) DHCP over<br>
SLIP and PPP for many years. =A0And, if you look at the draft closely,<br>
you&#39;ll note that it didn&#39;t go through the working group process.<br=
>
Instead, it just documented what one vendor chose to deploy without<br>
benefit of the usual standards review (and apparently without having<br>
secured the Option Type numbers through IANA).<br></blockquote><div><br>--&=
gt; You mean the Type numbers in RFC1877 are not assigned by IANA? <br>I&#3=
9;m sorry if I missed something.<br><br>Cheers,<br>Jacni<br>=A0<br></div>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Other vendors had to suffer with the consequences, which included deep<br>
conflicts and duplications that exist to this day. =A0Resolving data<br>
that comes from PPP on some links and from DHCP on others is<br>
complicated.<br>
<br>
I don&#39;t think repeating mistakes is a good idea, and I doubt that<br>
you&#39;ll find much consensus here for that sort of extension in IPv6CP.<b=
r>
<br>
&gt; So, we kindly suggest the WG should reconsider that.<br>
<br>
You will need to convince others here to support your effort. =A0I&#39;m<br=
>
nominally the chair of the group, but I&#39;m just one member. =A0I&#39;ll =
defer<br>
to the consensus.<br>
<br>
But, in my opinion, these drafts have a long way to go in order to be<br>
persuasive, and the outlook seems hazy to me. =A0I don&#39;t see how we can=
<br>
proceed with a deliberate duplication of effort expended by other<br>
working groups.<br>
<div><div></div><div class=3D"h5"><br>
--<br>
James Carlson =A0 =A0 =A0 =A0 42.703N 71.076W =A0 =A0 =A0 =A0 &lt;<a href=
=3D"mailto:carlsonj@workingcode.com">carlsonj@workingcode.com</a>&gt;<br>
_______________________________________________<br>
Pppext mailing list<br>
<a href=3D"mailto:Pppext@ietf.org">Pppext@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pppext" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/pppext</a><br>
</div></div></blockquote></div><br>

--000325559ee644cd6404930fb125--

From jacniq@gmail.com  Wed Oct 20 10:34:44 2010
Return-Path: <jacniq@gmail.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C1E153A68FB for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 10:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.198
X-Spam-Level: 
X-Spam-Status: No, score=-2.198 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 3QPprs4W+NdH for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 10:34:43 -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 4BCD63A6897 for <pppext@ietf.org>; Wed, 20 Oct 2010 10:34:43 -0700 (PDT)
Received: by bwz14 with SMTP id 14so3081172bwz.31 for <pppext@ietf.org>; Wed, 20 Oct 2010 10:36:16 -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; bh=pF6kT6gM1yfPh+pxseMCu5d4WpLz7BpLFBlL3HPrmKY=; b=wOSFqzVwkUQArDZH706ikL3bNVovJQuDkdgWpe5jG1UenbEvHPv2nrKjaKZ7NzJ7bT 8kmEXPkxmGI5PykrP+X58+QjW4QJPYoiHgL3kog4lKlRWKp4B03xi5URah+Ep0GVN0NL NsbPLAQDsvxAVKWIZHXOq+0UEFCrw+jgRNZQ4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=dgZIPSbWtpqxbogiywt1uSQtByptACub5ZDTffcG2gbdVlm0UZOt94wIUduWXibjtf zn0H9TMa5mdfhPgySTxHGKQ1E0HId1NpG6K1wFrsUDcavVZse4BMTT+0hzWuhECrfJnc 0I6+kftl8DjbOvK6qFpl3nJv5MATJIulONtrI=
MIME-Version: 1.0
Received: by 10.204.103.67 with SMTP id j3mr7271076bko.94.1287596174570; Wed, 20 Oct 2010 10:36:14 -0700 (PDT)
Received: by 10.204.66.129 with HTTP; Wed, 20 Oct 2010 10:36:14 -0700 (PDT)
In-Reply-To: <201010201429.o9KETNpi092485@calcite.rhyolite.com>
References: <4CBEEF16.1030304@workingcode.com> <201010201429.o9KETNpi092485@calcite.rhyolite.com>
Date: Thu, 21 Oct 2010 01:36:14 +0800
Message-ID: <AANLkTin6+sARKL1YoOpogD9KLNcJONX4HYHWtMg7e0AO@mail.gmail.com>
From: Jacni Qin <jacniq@gmail.com>
To: Vernon Schryver <vjs@calcite.rhyolite.com>
Content-Type: multipart/alternative; boundary=0016e6dee8e899772904930fd833
Cc: pppext@ietf.org, huj@ctbri.com.cn
Subject: Re: [Pppext] I-D Action:draft-hu-pppext-ipv6cp-requirements-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 17:34:44 -0000

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

Dear Vernon,

Please see inline,

On Wed, Oct 20, 2010 at 10:29 PM, Vernon Schryver
<vjs@calcite.rhyolite.com>wrote:

> > From: James Carlson <carlsonj@workingcode.com>
> > To: huj@ctbri.com.cn
> > Cc: pppext@ietf.org
>
> > > Yes, of course, we've read the archives(after 2004) carefully.
> > > Right, several drafts have ever been posted trying to solve some of
> > > these problems, but not moving forward.
> >
> > Correct; there was no consensus to do so.
>
> There was a clear consensus to not do so.  That differs from
> a lack of consensus.
>
>
> > > But now, under the great pressure of IPv4 address exhaustion, we try to
> > > evaluate critical mechanisms for IPv6
>
> IPv4 addresses will be exhausted before a standards track RFC could
> be approved.  Any real IPv6/PPP problems at this late date must be
> addressed elsewhere.
>

> > > One RFC will make real sense only if it is verified by implementations
> > > in real world and finally got widely deployed.
>
> No RFC can be approved by the IAB etc. in time to encourage independent
> implementations until long after the last IPv4 address has been assigned.
>

How about an informational document like RFC1877 ?


> China Telecom must have started testing and working with IPv6 years
> ago, just like the rest of us.  If China Telecom really thinks that
> the problems described in the drafts must be solved by extending the
> point-to-point protocol instead of using the existing, familiar,
> standardized, and widely implemented mechanisms,


--> Do you mean running ND + DHCPv6 + IPv6CP ? is this widely implemented
for IPv6 over PPP?
Could you share some experience on this?

Many thanks,
Jacni



> then China Telecom
> must have already built, tested, and deployed in alpha testing prototype
> implementations of the proposed PPP extensions.  What has been observed,
> especially in the alpha testing?
>
>
> Vernon Schryver    vjs@rhyolite.com
> _______________________________________________
> Pppext mailing list
> Pppext@ietf.org
> https://www.ietf.org/mailman/listinfo/pppext
>

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

<font color=3D"#000000"><font face=3D"verdana,sans-serif">Dear Vernon,<br><=
br>Please see inline,<br></font></font><br><div class=3D"gmail_quote">On We=
d, Oct 20, 2010 at 10:29 PM, Vernon Schryver <span dir=3D"ltr">&lt;<a href=
=3D"mailto:vjs@calcite.rhyolite.com">vjs@calcite.rhyolite.com</a>&gt;</span=
> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">&gt; From: James =
Carlson &lt;<a href=3D"mailto:carlsonj@workingcode.com">carlsonj@workingcod=
e.com</a>&gt;<br>

&gt; To: <a href=3D"mailto:huj@ctbri.com.cn">huj@ctbri.com.cn</a><br>
&gt; Cc: <a href=3D"mailto:pppext@ietf.org">pppext@ietf.org</a><br>
<div class=3D"im"><br>
&gt; &gt; Yes, of course, we&#39;ve read the archives(after 2004) carefully=
.<br>
&gt; &gt; Right, several drafts have ever been posted trying to solve some =
of<br>
&gt; &gt; these problems, but not moving forward.<br>
&gt;<br>
&gt; Correct; there was no consensus to do so.<br>
<br>
</div>There was a clear consensus to not do so. =A0That differs from<br>
a lack of consensus.<br>
<div class=3D"im"><br>
<br>
&gt; &gt; But now, under the great pressure of IPv4 address exhaustion, we =
try to<br>
&gt; &gt; evaluate critical mechanisms for IPv6<br>
<br>
</div>IPv4 addresses will be exhausted before a standards track RFC could<b=
r>
be approved. =A0Any real IPv6/PPP problems at this late date must be<br>
addressed elsewhere.<br></blockquote><blockquote class=3D"gmail_quote" styl=
e=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); =
padding-left: 1ex;">
<div class=3D"im"><br>
&gt; &gt; One RFC will make real sense only if it is verified by implementa=
tions<br>
&gt; &gt; in real world and finally got widely deployed.<br>
<br>
</div>No RFC can be approved by the IAB etc. in time to encourage independe=
nt<br>
implementations until long after the last IPv4 address has been assigned.<b=
r></blockquote><div><br>How about an informational document like RFC1877 ? =
<br><br></div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0p=
t 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">

<br>
China Telecom must have started testing and working with IPv6 years<br>
ago, just like the rest of us. =A0If China Telecom really thinks that<br>
the problems described in the drafts must be solved by extending the<br>
point-to-point protocol instead of using the existing, familiar,<br>
standardized, and widely implemented mechanisms, </blockquote><div><br>--&g=
t; Do you mean running ND + DHCPv6 + IPv6CP ? is this widely implemented fo=
r IPv6 over PPP?<br>Could you share some experience on this?<br><br>Many th=
anks,<br>
Jacni<br><br>=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin=
: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-lef=
t: 1ex;">then China Telecom<br>
must have already built, tested, and deployed in alpha testing prototype<br=
>
implementations of the proposed PPP extensions. =A0What has been observed,<=
br>
especially in the alpha testing?<br>
<font color=3D"#888888"><br>
<br>
Vernon Schryver =A0 =A0<a href=3D"mailto:vjs@rhyolite.com">vjs@rhyolite.com=
</a><br>
</font><div><div></div><div class=3D"h5">__________________________________=
_____________<br>
Pppext mailing list<br>
<a href=3D"mailto:Pppext@ietf.org">Pppext@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pppext" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/pppext</a><br>
</div></div></blockquote></div><br>

--0016e6dee8e899772904930fd833--

From i.goyret@alcatel-lucent.com  Wed Oct 20 11:06:19 2010
Return-Path: <i.goyret@alcatel-lucent.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9EA713A68C8 for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 11:06:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.875
X-Spam-Level: 
X-Spam-Status: No, score=-101.875 tagged_above=-999 required=5 tests=[AWL=0.124, 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 5yU2UoVXAur3 for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 11:06:18 -0700 (PDT)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id 7ADD33A68C0 for <pppext@ietf.org>; Wed, 20 Oct 2010 11:06:18 -0700 (PDT)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id o9KI0HeQ002474 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 20 Oct 2010 13:01:17 -0500 (CDT)
Received: from cliff.eng.ascend.com (cliff.eng.ascend.com [135.140.53.169]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id o9KI0EBM004566 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 20 Oct 2010 13:00:15 -0500
Received: from igoyret-c1.alcatel-lucent.com (dhcp-135-140-27-184 [135.140.27.184]) by cliff.eng.ascend.com (8.13.1/8.13.1) with ESMTP id o9KI09KG032319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Oct 2010 11:00:09 -0700
Message-Id: <201010201800.o9KI09KG032319@cliff.eng.ascend.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 20 Oct 2010 10:57:35 -0700
To: James Carlson <carlsonj@workingcode.com>
From: Ignacio Goyret <i.goyret@alcatel-lucent.com>
In-Reply-To: <4CBC9666.5060302@workingcode.com>
References: <20101018023005.360693A6C7A@core3.amsl.com> <4CBC9666.5060302@workingcode.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
Cc: "pppext@ietf.org" <pppext@ietf.org>, chenyq@ctbri.com.cn, huj@ctbri.com.cn, maodf@chinatelecom.com.cn, zhaohl@ctbri.com.cn
Subject: Re: [Pppext] I-D Action:draft-hu-pppext-ipv6cp-requirements-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 18:06:19 -0000

FWIW, I agree with James' statements/questions.
-Ignacio Goyret

At 02:48 PM 10/18/2010 -0400, James Carlson wrote:
>>       Title           : PPPv6 Problem statement and requirements
>>       Author(s)       : J. Hu, et al.
>>       Filename        : draft-hu-pppext-ipv6cp-requirements-00.txt
>
>I've read this draft, and I have a few initial fairly high-level
>questions about it before offering any detailed comments.  (And since
>the second draft appears to depend on the first, it seems that this one
>is the right place to start.)
>
>1.  The "Problem Statement" contains many assertions about problems
>    with the design and use of IPv6CP.  But there are many known and
>    interoperable implementations available today.  Are these newly
>    discovered problems?  And do any of the existing implementations
>    suffer from them?  (In other words: "what problems need to be
>    fixed?")
>
>2.  Many of the issues raised are not specifically related to PPP,
>    and are issues any time you have an IPv6 link over any datalink
>    medium, and when used in a particular type of deployment.  Why
>    are the solutions specific to IPv6CP and not general in nature?
>
>3.  Have you read through the working group archives?  Many of these
>    issues have been addressed over the years -- some of them more
>    than once.  In particular, there's established working group
>    consensus that the results of RFC 1877 should not be replicated
>    for IPv6.
>
>-- 
>James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>
>_______________________________________________
>Pppext mailing list
>Pppext@ietf.org
>https://www.ietf.org/mailman/listinfo/pppext


From carlsonj@workingcode.com  Wed Oct 20 11:07:49 2010
Return-Path: <carlsonj@workingcode.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B3BF93A68C8 for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 11:07:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.155
X-Spam-Level: 
X-Spam-Status: No, score=-102.155 tagged_above=-999 required=5 tests=[AWL=-0.156, 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 Z+g2eb1W6jNj for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 11:07:48 -0700 (PDT)
Received: from carlson.workingcode.com (carlsonj-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1d9::2]) by core3.amsl.com (Postfix) with ESMTP id ECEB93A68C0 for <pppext@ietf.org>; Wed, 20 Oct 2010 11:07:47 -0700 (PDT)
Received: from [10.50.23.149] (gate.abinitio.com [65.170.40.132]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id o9KI99Oo024626 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Oct 2010 14:09:09 -0400 (EDT)
Message-ID: <4CBF3044.3090102@workingcode.com>
Date: Wed, 20 Oct 2010 14:09:08 -0400
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090605)
MIME-Version: 1.0
To: Jacni Qin <jacniq@gmail.com>
References: <201010200936.o9K9auaj016890@carlson.workingcode.com>	<4CBEEF16.1030304@workingcode.com> <AANLkTi=Ew3MW9_L-jKPsdGU8SYGYzwnuzB_yhKOexpco@mail.gmail.com>
In-Reply-To: <AANLkTi=Ew3MW9_L-jKPsdGU8SYGYzwnuzB_yhKOexpco@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-DCC-sonic.net-Metrics: carlson; whitelist
Cc: pppext@ietf.org, huj@ctbri.com.cn
Subject: Re: [Pppext] I-D Action:draft-hu-pppext-ipv6cp-requirements-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 18:07:49 -0000

Jacni Qin wrote:
> On Wed, Oct 20, 2010 at 9:31 PM, James Carlson <carlsonj@workingcode.com
> <mailto:carlsonj@workingcode.com>> wrote:
>     huj@ctbri.com.cn <mailto:huj@ctbri.com.cn> wrote:
>     > Some are well known, and some may be not fully discussed like,
>     >
>     >    o More transaction steps caused by extra control protocols
>     >       introduced will result in longer response time and higher
>     risk of
>     >       exception.
> 
>     Has this problem been measured anywhere?
> 
>     Are we talking about two extra packets?  Perhaps four?
> 
>     What sorts of "risks" are involved?  How often do they happen and how
>     do they compare with the risks of the proposed solution?  Is there any
>     way to mitigate the risks?
> 
> 
> --> Get all things done by IPv6CP but not involving ND or DHCPv6 ? ;-)

That doesn't appear to answer the questions.

Yes, of course, given sufficient time, money, and motivation, IPv6CP
could be redesigned to do almost any job.  We could even add a "Google
Query" option to it, so that users don't have to fuss with TCP or IP to
get their most common tasks done.  That would remove more "risk" from users.

But this isn't a case where there's infinite capacity or demand.  We
have to weigh the opportunities provided by new extensions against the
costs they impose on others (who will often be forced to implement for
the sake of interoperability, whether they need the feature or not).  In
this case, it seems to me to be very unclear what benefits we get from
these changes.

Thus, I'd like to know what compels us to make changes to these
protocols.  Concrete examples of things that don't work with the
existing protocols (and can't be made to work in any reasonable manner)
but that do work with the proposed solution would be very helpful.

>     >    o How to determine the moment when the status of IPv6CP negotiation
>     >       comes to "OPEN", so as to get corresponding AAA activities
>     started?
> 
>     This is an implementation issue and is out of scope in this working
>     group.
> 
> 
> --> I guess the authors mean that since IPv6CP just provides
> interface-id, and only when the IPv6 addresses
> and other elements are successfully configured by ND or DHCPv6, the
> status of NCP can come to "OPEN".

That's still an implementation issue.

For one arbitrary data point, Solaris plumbs new interfaces for each
address, whether configured by ND or DHCPv6, and applications can easily
detect these events using routing sockets or by scanning the interface
table.

Other systems may vary.  The important point, though, is that these
issues have nothing whatsoever to do with the bits on the wire, and
that's the only thing that's really in scope here.

(The one exception I could imagine is where a protocol is so badly
designed that it's just infeasible to produce a reasonable
implementation.  I don't think that's the case here, as we have multiple
independent interoperable implementations of all of the existing
protocols under discussion.)

>     >    o ISPs have to change current network infrastructure accordingly,
>     >       such as installing DHCPv6 server somewhere in the network
>     >       (standalone or embedded) which will not only increase both CAPEX
>     >       and OPEX, but result in scalability problems when the number of
>     >       subscribers grows.
> 
>     Change in what way?
> 
> 
> --> As mentioned here, "installing DHCPv6 server somewhere" ?
> Currently, there is no DHCPv4 server installed for the IPv4 over PPP.

I think that misses the point I'm making.

If you deploy IPv6 at all, then you need to make changes.  At a minimum,
you need to configure some IPv6 routers so that all those PPP users can
reach some useful sites.

That's change.  The fact that you _may_ also need DHCPv6 (depending on
your deployment requirements) is just an additional item to consider.

Adding these new options will _not_ obviate all change.  In fact,
they'll just make the problem worse: users will need modified clients
that have these new (currently unavailable) options, and ISPs will need
upgrade PPP servers that include the new features.

I don't believe that by adding yet more changes to the existing
protocols one can reduce the overall amount of work.

>     >    o Some unnecessary functions will be involved. For example,
>     >       functions like Address Resolution, On-link Prefix List
>     >       Advertisement, Default Router Advertisement, etc. defined in ND
>     >       are actually not needed for a simple PPP link.
> 
>     Those sound out of scope for this working group.  They sound like
>     issues for one of the IPv6 or routing groups instead.
> 
> 
> --> I think this is a special case for PPP. Those are still needed for
> other date links, such as Ethernet.

Again, how (and whether) you use higher level protocols over your PPP
link is an issue for those higher-level protocols.

I don't believe that it's in scope here.

However, as a matter of design, I do think that it's unwise to create
new special cases where there aren't any.  It makes overall system
testing for vendors much more difficult and reduces coverage.

>      - There's simply no hope that PPP could adequately fill the role
>        that DHCP serves.  DHCP has far too many useful extensions for us
>        to repeat that working group's effort in any reasonable manner.
>        Similar things are true for Neighbor Discovery and Router
>        Advertisements and for the general-purpose routing protocols.
> 
> 
> --> While many of those extensions are not needed for PPP link.

How do we know when to stop?

>      - It's a waste of time and effort.  It produces considerably more
>        work for PPP implementors and vendors who end up needing to
>        support "all" available mechanisms rather than using just the
>        purpose-built ones.
> 
> 
> --> There have been overlapping functions between ND and DHCPv6 which
> result in
> implementation issues. Why not solving it for PPP by PPP itself?
> You may argue that this will further aggravate the issue, but from
> different perspective,
> this is a straightforward way rather than waiting for ND and DHCPv6
> solving that problem.
> :-)

We're all in this boat together.  I see no benefit from adding
complexity to PPP as a way of "fixing" somebody else's problem.

Remember: hardware, software, and deployments are short in duration, but
protocols are forever.  If we change this, it'll be that way "forever,"
long after whatever problems you see in ND/DHCPv6 have been resolved.

>     RFC 1877 was a mistake because there already was an accepted solution
>     for this problem: folks had been running BOOTP and (later) DHCP over
>     SLIP and PPP for many years.  And, if you look at the draft closely,
>     you'll note that it didn't go through the working group process.
>     Instead, it just documented what one vendor chose to deploy without
>     benefit of the usual standards review (and apparently without having
>     secured the Option Type numbers through IANA).
> 
> 
> --> You mean the Type numbers in RFC1877 are not assigned by IANA?
> I'm sorry if I missed something.

My recollection of the event was that the vendor in question shipped the
feature, then documented it in an I-D, and only after that got the
numbers assigned by IANA.  That's why the numbers chosen (128...131) are
so strange; they were likely picked to be "unlikely" to be in use
anywhere else.

There's more to it than that.  The protocol described in that RFC is
backwards -- it has the side with the configured information giving
Configure-Naks and the side using the information sending the
Configure-Requests.  It's not like the others.

In any event, the point I was making was that RFC 1877 is a poor role
model for future documents.  And to Vern's point, I do think there is
consensus in the working group that we do _not_ want to repeat that bit
of history.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

From fitz@jfitz.com  Wed Oct 20 11:48:39 2010
Return-Path: <fitz@jfitz.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 945A23A67D9 for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 11:48:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.008
X-Spam-Level: ****
X-Spam-Status: No, score=4.008 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_PACBELL_D=3.944, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_32=0.6, RDNS_DYNAMIC=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 dGOL4jzilXUh for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 11:48:36 -0700 (PDT)
Received: from jfitz.com (adsl-69-233-182-147.dsl.pltn13.pacbell.net [69.233.182.147]) by core3.amsl.com (Postfix) with SMTP id 7A4CD3A6827 for <pppext@ietf.org>; Wed, 20 Oct 2010 11:48:34 -0700 (PDT)
Received: (qmail 773 invoked from network); 20 Oct 2010 18:50:06 -0000
Received: from office-gw-vpn.jfitz.com (HELO ?192.168.12.77?) (192.168.12.77) by bub-vpn.jfitz.com with SMTP; 20 Oct 2010 18:49:55 -0000
From: John Fitzgibbon <fitz@jfitz.com>
To: pppext@ietf.org
Date: Wed, 20 Oct 2010 11:48:29 -0700
User-Agent: KMail/1.9.4
References: <201010200936.o9K9auaj016890@carlson.workingcode.com> <AANLkTi=Ew3MW9_L-jKPsdGU8SYGYzwnuzB_yhKOexpco@mail.gmail.com> <4CBF3044.3090102@workingcode.com>
In-Reply-To: <4CBF3044.3090102@workingcode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <201010201148.29798.fitz@jfitz.com>
Cc: huj@ctbri.com.cn
Subject: Re: [Pppext] I-D Action:draft-hu-pppext-ipv6cp-requirements-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 18:48:40 -0000

> we have multiple
> independent interoperable implementations of all of the existing
> protocols under discussion.

I agree.

Significant IPv6 rollouts have already gone through interoperability testing. 
The various combinations of PPP, Stateless IPv6 Auto-Discovery and 
Stateful/Stateless DHCPv6 are reasonably well established at this point. 

In relation to the question about increased risks and response times, I'd 
imagine that introducing an IPv6CP option as an alternative config mechanism 
will increase the overall complexity of a fully interoperable system, and, 
everything else being equal, adding complexity increases risk. In terms of 
response, if you end up needing DHCPv6 anyway for some other purpose, then 
you're probably increasing the overall response time if some config is 
negotiated by IPv6CP and some by DHCPv6.

While it's certainly tempting to start down the path of "if I did just this 
one thing in IPv6CP, I wouldn't need ND or DHCPv6...", we know from 
experience that this causes more trouble than it's worth as the list of "just 
one more thing" grows.

Bottom line: PPP is designed for establishing a link, DHCP is designed for 
(extensible) configuration, and Stateless Auto-Config is designed to provide 
basic IPv6 connectivity. Can't we just leave it at that?

John Fitzgibbon


On Wednesday 20 October 2010 11:09, James Carlson wrote:
> Jacni Qin wrote:
> > On Wed, Oct 20, 2010 at 9:31 PM, James Carlson <carlsonj@workingcode.com
> > <mailto:carlsonj@workingcode.com>> wrote:
> >
> >     huj@ctbri.com.cn <mailto:huj@ctbri.com.cn> wrote:
> >     > Some are well known, and some may be not fully discussed like,
> >     >
> >     >    o More transaction steps caused by extra control protocols
> >     >       introduced will result in longer response time and higher
> >
> >     risk of
> >
> >     >       exception.
> >
> >     Has this problem been measured anywhere?
> >
> >     Are we talking about two extra packets?  Perhaps four?
> >
> >     What sorts of "risks" are involved?  How often do they happen and how
> >     do they compare with the risks of the proposed solution?  Is there
> > any way to mitigate the risks?
> >
> >
> > --> Get all things done by IPv6CP but not involving ND or DHCPv6 ? ;-)
>
> That doesn't appear to answer the questions.
>
> Yes, of course, given sufficient time, money, and motivation, IPv6CP
> could be redesigned to do almost any job.  We could even add a "Google
> Query" option to it, so that users don't have to fuss with TCP or IP to
> get their most common tasks done.  That would remove more "risk" from
> users.
>
> But this isn't a case where there's infinite capacity or demand.  We
> have to weigh the opportunities provided by new extensions against the
> costs they impose on others (who will often be forced to implement for
> the sake of interoperability, whether they need the feature or not).  In
> this case, it seems to me to be very unclear what benefits we get from
> these changes.
>
> Thus, I'd like to know what compels us to make changes to these
> protocols.  Concrete examples of things that don't work with the
> existing protocols (and can't be made to work in any reasonable manner)
> but that do work with the proposed solution would be very helpful.
>
> >     >    o How to determine the moment when the status of IPv6CP
> >     > negotiation comes to "OPEN", so as to get corresponding AAA
> >     > activities
> >
> >     started?
> >
> >     This is an implementation issue and is out of scope in this working
> >     group.
> >
> >
> > --> I guess the authors mean that since IPv6CP just provides
> > interface-id, and only when the IPv6 addresses
> > and other elements are successfully configured by ND or DHCPv6, the
> > status of NCP can come to "OPEN".
>
> That's still an implementation issue.
>
> For one arbitrary data point, Solaris plumbs new interfaces for each
> address, whether configured by ND or DHCPv6, and applications can easily
> detect these events using routing sockets or by scanning the interface
> table.
>
> Other systems may vary.  The important point, though, is that these
> issues have nothing whatsoever to do with the bits on the wire, and
> that's the only thing that's really in scope here.
>
> (The one exception I could imagine is where a protocol is so badly
> designed that it's just infeasible to produce a reasonable
> implementation.  I don't think that's the case here, as we have multiple
> independent interoperable implementations of all of the existing
> protocols under discussion.)
>
> >     >    o ISPs have to change current network infrastructure
> >     > accordingly, such as installing DHCPv6 server somewhere in the
> >     > network (standalone or embedded) which will not only increase both
> >     > CAPEX and OPEX, but result in scalability problems when the number
> >     > of subscribers grows.
> >
> >     Change in what way?
> >
> >
> > --> As mentioned here, "installing DHCPv6 server somewhere" ?
> > Currently, there is no DHCPv4 server installed for the IPv4 over PPP.
>
> I think that misses the point I'm making.
>
> If you deploy IPv6 at all, then you need to make changes.  At a minimum,
> you need to configure some IPv6 routers so that all those PPP users can
> reach some useful sites.
>
> That's change.  The fact that you _may_ also need DHCPv6 (depending on
> your deployment requirements) is just an additional item to consider.
>
> Adding these new options will _not_ obviate all change.  In fact,
> they'll just make the problem worse: users will need modified clients
> that have these new (currently unavailable) options, and ISPs will need
> upgrade PPP servers that include the new features.
>
> I don't believe that by adding yet more changes to the existing
> protocols one can reduce the overall amount of work.
>
> >     >    o Some unnecessary functions will be involved. For example,
> >     >       functions like Address Resolution, On-link Prefix List
> >     >       Advertisement, Default Router Advertisement, etc. defined in
> >     > ND are actually not needed for a simple PPP link.
> >
> >     Those sound out of scope for this working group.  They sound like
> >     issues for one of the IPv6 or routing groups instead.
> >
> >
> > --> I think this is a special case for PPP. Those are still needed for
> > other date links, such as Ethernet.
>
> Again, how (and whether) you use higher level protocols over your PPP
> link is an issue for those higher-level protocols.
>
> I don't believe that it's in scope here.
>
> However, as a matter of design, I do think that it's unwise to create
> new special cases where there aren't any.  It makes overall system
> testing for vendors much more difficult and reduces coverage.
>
> >      - There's simply no hope that PPP could adequately fill the role
> >        that DHCP serves.  DHCP has far too many useful extensions for us
> >        to repeat that working group's effort in any reasonable manner.
> >        Similar things are true for Neighbor Discovery and Router
> >        Advertisements and for the general-purpose routing protocols.
> >
> >
> > --> While many of those extensions are not needed for PPP link.
>
> How do we know when to stop?
>
> >      - It's a waste of time and effort.  It produces considerably more
> >        work for PPP implementors and vendors who end up needing to
> >        support "all" available mechanisms rather than using just the
> >        purpose-built ones.
> >
> >
> > --> There have been overlapping functions between ND and DHCPv6 which
> > result in
> > implementation issues. Why not solving it for PPP by PPP itself?
> > You may argue that this will further aggravate the issue, but from
> > different perspective,
> > this is a straightforward way rather than waiting for ND and DHCPv6
> > solving that problem.
> >
> > :-)
>
> We're all in this boat together.  I see no benefit from adding
> complexity to PPP as a way of "fixing" somebody else's problem.
>
> Remember: hardware, software, and deployments are short in duration, but
> protocols are forever.  If we change this, it'll be that way "forever,"
> long after whatever problems you see in ND/DHCPv6 have been resolved.
>
> >     RFC 1877 was a mistake because there already was an accepted solution
> >     for this problem: folks had been running BOOTP and (later) DHCP over
> >     SLIP and PPP for many years.  And, if you look at the draft closely,
> >     you'll note that it didn't go through the working group process.
> >     Instead, it just documented what one vendor chose to deploy without
> >     benefit of the usual standards review (and apparently without having
> >     secured the Option Type numbers through IANA).
> >
> >
> > --> You mean the Type numbers in RFC1877 are not assigned by IANA?
> > I'm sorry if I missed something.
>
> My recollection of the event was that the vendor in question shipped the
> feature, then documented it in an I-D, and only after that got the
> numbers assigned by IANA.  That's why the numbers chosen (128...131) are
> so strange; they were likely picked to be "unlikely" to be in use
> anywhere else.
>
> There's more to it than that.  The protocol described in that RFC is
> backwards -- it has the side with the configured information giving
> Configure-Naks and the side using the information sending the
> Configure-Requests.  It's not like the others.
>
> In any event, the point I was making was that RFC 1877 is a poor role
> model for future documents.  And to Vern's point, I do think there is
> consensus in the working group that we do _not_ want to repeat that bit
> of history.

From vjs@calcite.rhyolite.com  Wed Oct 20 12:39:56 2010
Return-Path: <vjs@calcite.rhyolite.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE39E3A68C7 for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 12:39:55 -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_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 H7IYeAGV4l3B for <pppext@core3.amsl.com>; Wed, 20 Oct 2010 12:39:54 -0700 (PDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [IPv6:2001:4978:230::3]) by core3.amsl.com (Postfix) with ESMTP id BB97E3A6838 for <pppext@ietf.org>; Wed, 20 Oct 2010 12:39:53 -0700 (PDT)
Received: from calcite.rhyolite.com (localhost [127.0.0.1]) by calcite.rhyolite.com (8.14.4/8.14.4) with ESMTP id o9KJfBJ3040046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) env-from <vjs@calcite.rhyolite.com>; Wed, 20 Oct 2010 19:41:12 GMT
Received: (from vjs@localhost) by calcite.rhyolite.com (8.14.4/8.14.4/Submit) id o9KJfAAs040045; Wed, 20 Oct 2010 19:41:10 GMT
Date: Wed, 20 Oct 2010 19:41:10 GMT
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <201010201941.o9KJfAAs040045@calcite.rhyolite.com>
To: jacniq@gmail.com
In-Reply-To: <AANLkTin6+sARKL1YoOpogD9KLNcJONX4HYHWtMg7e0AO@mail.gmail.com>
X-DCC-Rhyolite-Metrics: calcite.rhyolite.com; whitelist
Cc: pppext@ietf.org, huj@ctbri.com.cn
Subject: Re: [Pppext] I-D Action:draft-hu-pppext-ipv6cp-requirements-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 19:39:56 -0000

> From: Jacni Qin <jacniq@gmail.com>
> To: Vernon Schryver <vjs@calcite.rhyolite.com>
> Cc: pppext@ietf.org, huj@ctbri.com.cn

> > No RFC can be approved by the IAB etc. in time to encourage independent
> > implementations until long after the last IPv4 address has been assigned.
>
> How about an informational document like RFC1877 ?

Informational RFCs rarely convince very large organizations such
as those with "telecom" in their names to do or not do anything.

I think even an Informational RFC from the PPP extensions working
group would need approval of the IAB etc.  (I hope James or someone
will correct me if I'm wrong about that.)  I'm certain that anything
published under the rubric of the WG would need WG consensus.


> > China Telecom must have started testing and working with IPv6 years
> > ago, just like the rest of us.  If China Telecom really thinks that
> > the problems described in the drafts must be solved by extending the
> > point-to-point protocol instead of using the existing, familiar,
> > standardized, and widely implemented mechanisms,
>
> --> Do you mean running ND + DHCPv6 + IPv6CP ? is this widely implemented
> for IPv6 over PPP?
> Could you share some experience on this?

In this case I think the responsibility for sharing experience
rests on those proposing new standards to solve problems.


Vernon Schryver    vjs@rhyolite.com

From jacniq@gmail.com  Sun Oct 24 08:00:58 2010
Return-Path: <jacniq@gmail.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8BE983A689E for <pppext@core3.amsl.com>; Sun, 24 Oct 2010 08:00:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.148
X-Spam-Level: 
X-Spam-Status: No, score=-2.148 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 CJbAN2B8s+ek for <pppext@core3.amsl.com>; Sun, 24 Oct 2010 08:00:56 -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 2A57D3A6866 for <pppext@ietf.org>; Sun, 24 Oct 2010 08:00:56 -0700 (PDT)
Received: by bwz12 with SMTP id 12so2802942bwz.31 for <pppext@ietf.org>; Sun, 24 Oct 2010 08:02:38 -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; bh=FoViFplX5zGB7sLrnQ+uXF5ywuSQSaR5F2nVRtDvs4g=; b=N0kWWAfC+gf/K4T9DKDu7rtOEV7QUzcI+wn7iJKUeVssNVoiD67qi0tS/h2W6qAfrY eQbSZ+wjV96yQvdHIPUzZaCb5az6AuM8OQImfEMTq7LJelkIk6713FFjYfs++BtKJ/uE VREcfoY5wsEJ0x3xmav3oXFiSk99wGoC0erhM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=EUoNKL9OkSOwjOh0DCLfEwQmE9RVlrpp/24Up49p3UZUUG11uY0hh2PIOe2XgXlDkl Eh3fTVgXEUqE/zOmnx2Wl8UGBUJYWA1fU8MBqpUoTql8EotmP3IJz2XJZWDpwbFOBvSb A/ErFj63n4oeGOxYZMra1qU23TodWBKeZPPcw=
MIME-Version: 1.0
Received: by 10.204.62.136 with SMTP id x8mr3970191bkh.192.1287932557958; Sun, 24 Oct 2010 08:02:37 -0700 (PDT)
Received: by 10.204.66.129 with HTTP; Sun, 24 Oct 2010 08:02:37 -0700 (PDT)
In-Reply-To: <4CBF3044.3090102@workingcode.com>
References: <201010200936.o9K9auaj016890@carlson.workingcode.com> <4CBEEF16.1030304@workingcode.com> <AANLkTi=Ew3MW9_L-jKPsdGU8SYGYzwnuzB_yhKOexpco@mail.gmail.com> <4CBF3044.3090102@workingcode.com>
Date: Sun, 24 Oct 2010 23:02:37 +0800
Message-ID: <AANLkTimqv=vbY0vPrpAii_F4jLQYrn_Hh+ocqR2cv00B@mail.gmail.com>
From: Jacni Qin <jacniq@gmail.com>
To: James Carlson <carlsonj@workingcode.com>
Content-Type: multipart/alternative; boundary=001636c5ac249c9d0604935e2a18
Cc: pppext@ietf.org, huj@ctbri.com.cn
Subject: Re: [Pppext] I-D Action:draft-hu-pppext-ipv6cp-requirements-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Oct 2010 15:00:58 -0000

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

Dear James,

Thanks for your response, please see inline below,


On Thu, Oct 21, 2010 at 2:09 AM, James Carlson <carlsonj@workingcode.com>wrote:

> Jacni Qin wrote:
> > On Wed, Oct 20, 2010 at 9:31 PM, James Carlson <carlsonj@workingcode.com
> > <mailto:carlsonj@workingcode.com>> wrote:
> >     huj@ctbri.com.cn <mailto:huj@ctbri.com.cn> wrote:
> >     > Some are well known, and some may be not fully discussed like,
> >     >
> >     >    o More transaction steps caused by extra control protocols
> >     >       introduced will result in longer response time and higher
> >     risk of
> >     >       exception.
> >
> >     Has this problem been measured anywhere?
> >
> >     Are we talking about two extra packets?  Perhaps four?
> >
> >     What sorts of "risks" are involved?  How often do they happen and how
> >     do they compare with the risks of the proposed solution?  Is there
> any
> >     way to mitigate the risks?
> >
> >
> > --> Get all things done by IPv6CP but not involving ND or DHCPv6 ? ;-)
>
> That doesn't appear to answer the questions.
>
> Yes, of course, given sufficient time, money, and motivation, IPv6CP
> could be redesigned to do almost any job.  We could even add a "Google
> Query" option to it, so that users don't have to fuss with TCP or IP to
> get their most common tasks done.  That would remove more "risk" from
> users.
>
> --> Do you want to have a try? ;-)


> But this isn't a case where there's infinite capacity or demand.  We
> have to weigh the opportunities provided by new extensions against the
> costs they impose on others (who will often be forced to implement for
> the sake of interoperability, whether they need the feature or not).  In
> this case, it seems to me to be very unclear what benefits we get from
> these changes.
>
> Thus, I'd like to know what compels us to make changes to these
> protocols.  Concrete examples of things that don't work with the
> existing protocols (and can't be made to work in any reasonable manner)
> but that do work with the proposed solution would be very helpful.
>
> >     >    o How to determine the moment when the status of IPv6CP
> negotiation
> >     >       comes to "OPEN", so as to get corresponding AAA activities
> >     started?
> >
> >     This is an implementation issue and is out of scope in this working
> >     group.
> >
> >
> > --> I guess the authors mean that since IPv6CP just provides
> > interface-id, and only when the IPv6 addresses
> > and other elements are successfully configured by ND or DHCPv6, the
> > status of NCP can come to "OPEN".
>
> That's still an implementation issue.
>
> For one arbitrary data point, Solaris plumbs new interfaces for each
> address, whether configured by ND or DHCPv6, and applications can easily
> detect these events using routing sockets or by scanning the interface
> table.
>
> Other systems may vary.  The important point, though, is that these
> issues have nothing whatsoever to do with the bits on the wire, and
> that's the only thing that's really in scope here.
>
> (The one exception I could imagine is where a protocol is so badly
> designed that it's just infeasible to produce a reasonable
> implementation.  I don't think that's the case here, as we have multiple
> independent interoperable implementations of all of the existing
> protocols under discussion.)
>
> >     >    o ISPs have to change current network infrastructure
> accordingly,
> >     >       such as installing DHCPv6 server somewhere in the network
> >     >       (standalone or embedded) which will not only increase both
> CAPEX
> >     >       and OPEX, but result in scalability problems when the number
> of
> >     >       subscribers grows.
> >
> >     Change in what way?
> >
> >
> > --> As mentioned here, "installing DHCPv6 server somewhere" ?
> > Currently, there is no DHCPv4 server installed for the IPv4 over PPP.
>
> I think that misses the point I'm making.
>
> If you deploy IPv6 at all, then you need to make changes.  At a minimum,
> you need to configure some IPv6 routers so that all those PPP users can
> reach some useful sites.
>
> That's change.  The fact that you _may_ also need DHCPv6 (depending on
> your deployment requirements) is just an additional item to consider.
>
> Adding these new options will _not_ obviate all change.  In fact,
> they'll just make the problem worse: users will need modified clients
> that have these new (currently unavailable) options, and ISPs will need
> upgrade PPP servers that include the new features.
>

--> If we consider the transition of current IPv4 services over PPP to Dual
Stack where probably both IPv4 and IPv6 are running over a single link
established by LCP, IPv6CP will be enable, right? (may be I'm wrong about
this point?)
If so, shall we get the DHCPv6 involved which also requires all those you
mentioned above? That's even harder for the legacy devices on both sides of
the PPP link.
Or we can add several Options to IPv6CP which has been enabled?


> I don't believe that by adding yet more changes to the existing
> protocols one can reduce the overall amount of work.
>
> >     >    o Some unnecessary functions will be involved. For example,
> >     >       functions like Address Resolution, On-link Prefix List
> >     >       Advertisement, Default Router Advertisement, etc. defined in
> ND
> >     >       are actually not needed for a simple PPP link.
> >
> >     Those sound out of scope for this working group.  They sound like
> >     issues for one of the IPv6 or routing groups instead.
> >
> >
> > --> I think this is a special case for PPP. Those are still needed for
> > other date links, such as Ethernet.
>
> Again, how (and whether) you use higher level protocols over your PPP
> link is an issue for those higher-level protocols.
>
> I don't believe that it's in scope here.
>
> However, as a matter of design, I do think that it's unwise to create
> new special cases where there aren't any.  It makes overall system
> testing for vendors much more difficult and reduces coverage.
>
> >      - There's simply no hope that PPP could adequately fill the role
> >        that DHCP serves.  DHCP has far too many useful extensions for us
> >        to repeat that working group's effort in any reasonable manner.
> >        Similar things are true for Neighbor Discovery and Router
> >        Advertisements and for the general-purpose routing protocols.
> >
> >
> > --> While many of those extensions are not needed for PPP link.
>
> How do we know when to stop?
>
> >      - It's a waste of time and effort.  It produces considerably more
> >        work for PPP implementors and vendors who end up needing to
> >        support "all" available mechanisms rather than using just the
> >        purpose-built ones.
> >
> >
> > --> There have been overlapping functions between ND and DHCPv6 which
> > result in
> > implementation issues. Why not solving it for PPP by PPP itself?
> > You may argue that this will further aggravate the issue, but from
> > different perspective,
> > this is a straightforward way rather than waiting for ND and DHCPv6
> > solving that problem.
> > :-)
>
> We're all in this boat together.  I see no benefit from adding
> complexity to PPP as a way of "fixing" somebody else's problem.
>

--> Ok, that is a problem, right?
Only talking about PPP, not other kinds of data links.
If we can solve the problem on PPP, isn't it a benefit?


> Remember: hardware, software, and deployments are short in duration, but
> protocols are forever.  If we change this, it'll be that way "forever,"
> long after whatever problems you see in ND/DHCPv6 have been resolved.
>
> >     RFC 1877 was a mistake because there already was an accepted solution
> >     for this problem: folks had been running BOOTP and (later) DHCP over
> >     SLIP and PPP for many years.  And, if you look at the draft closely,
> >     you'll note that it didn't go through the working group process.
> >     Instead, it just documented what one vendor chose to deploy without
> >     benefit of the usual standards review (and apparently without having
> >     secured the Option Type numbers through IANA).
> >
> >
> > --> You mean the Type numbers in RFC1877 are not assigned by IANA?
> > I'm sorry if I missed something.
>
> My recollection of the event was that the vendor in question shipped the
> feature, then documented it in an I-D, and only after that got the
> numbers assigned by IANA.  That's why the numbers chosen (128...131) are
> so strange; they were likely picked to be "unlikely" to be in use
> anywhere else.
>

--> Thanks for the information.

Cheers,
Jacni



>
> There's more to it than that.  The protocol described in that RFC is
> backwards -- it has the side with the configured information giving
> Configure-Naks and the side using the information sending the
> Configure-Requests.  It's not like the others.
>
> In any event, the point I was making was that RFC 1877 is a poor role
> model for future documents.  And to Vern's point, I do think there is
> consensus in the working group that we do _not_ want to repeat that bit
> of history.
>
> --
> James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>
>

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

<font color=3D"#000000"><font face=3D"verdana,sans-serif">Dear James,<br><b=
r>Thanks for your response, please see inline below,<br><br></font></font><=
br><div class=3D"gmail_quote">On Thu, Oct 21, 2010 at 2:09 AM, James Carlso=
n <span dir=3D"ltr">&lt;<a href=3D"mailto:carlsonj@workingcode.com">carlson=
j@workingcode.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class=3D"im"=
>Jacni Qin wrote:<br>
&gt; On Wed, Oct 20, 2010 at 9:31 PM, James Carlson &lt;<a href=3D"mailto:c=
arlsonj@workingcode.com">carlsonj@workingcode.com</a><br>
</div>&gt; &lt;mailto:<a href=3D"mailto:carlsonj@workingcode.com">carlsonj@=
workingcode.com</a>&gt;&gt; wrote:<br>
<div class=3D"im">&gt; =A0 =A0 <a href=3D"mailto:huj@ctbri.com.cn">huj@ctbr=
i.com.cn</a> &lt;mailto:<a href=3D"mailto:huj@ctbri.com.cn">huj@ctbri.com.c=
n</a>&gt; wrote:<br>
&gt; =A0 =A0 &gt; Some are well known, and some may be not fully discussed =
like,<br>
&gt; =A0 =A0 &gt;<br>
&gt; =A0 =A0 &gt; =A0 =A0o More transaction steps caused by extra control p=
rotocols<br>
&gt; =A0 =A0 &gt; =A0 =A0 =A0 introduced will result in longer response tim=
e and higher<br>
&gt; =A0 =A0 risk of<br>
&gt; =A0 =A0 &gt; =A0 =A0 =A0 exception.<br>
&gt;<br>
&gt; =A0 =A0 Has this problem been measured anywhere?<br>
&gt;<br>
&gt; =A0 =A0 Are we talking about two extra packets? =A0Perhaps four?<br>
&gt;<br>
&gt; =A0 =A0 What sorts of &quot;risks&quot; are involved? =A0How often do =
they happen and how<br>
&gt; =A0 =A0 do they compare with the risks of the proposed solution? =A0Is=
 there any<br>
&gt; =A0 =A0 way to mitigate the risks?<br>
&gt;<br>
&gt;<br>
&gt; --&gt; Get all things done by IPv6CP but not involving ND or DHCPv6 ? =
;-)<br>
<br>
</div>That doesn&#39;t appear to answer the questions.<br>
<br>
Yes, of course, given sufficient time, money, and motivation, IPv6CP<br>
could be redesigned to do almost any job. =A0We could even add a &quot;Goog=
le<br>
Query&quot; option to it, so that users don&#39;t have to fuss with TCP or =
IP to<br>
get their most common tasks done. =A0That would remove more &quot;risk&quot=
; from users.<br>
<br></blockquote><div>--&gt; Do you want to have a try? ;-)<br>=A0<br></div=
><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; bord=
er-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
But this isn&#39;t a case where there&#39;s infinite capacity or demand. =
=A0We<br>
have to weigh the opportunities provided by new extensions against the<br>
costs they impose on others (who will often be forced to implement for<br>
the sake of interoperability, whether they need the feature or not). =A0In<=
br>
this case, it seems to me to be very unclear what benefits we get from<br>
these changes.<br>
<br>
Thus, I&#39;d like to know what compels us to make changes to these<br>
protocols. =A0Concrete examples of things that don&#39;t work with the<br>
existing protocols (and can&#39;t be made to work in any reasonable manner)=
<br>
but that do work with the proposed solution would be very helpful.<br>
<div class=3D"im"><br>
&gt; =A0 =A0 &gt; =A0 =A0o How to determine the moment when the status of I=
Pv6CP negotiation<br>
&gt; =A0 =A0 &gt; =A0 =A0 =A0 comes to &quot;OPEN&quot;, so as to get corre=
sponding AAA activities<br>
&gt; =A0 =A0 started?<br>
&gt;<br>
&gt; =A0 =A0 This is an implementation issue and is out of scope in this wo=
rking<br>
&gt; =A0 =A0 group.<br>
&gt;<br>
&gt;<br>
&gt; --&gt; I guess the authors mean that since IPv6CP just provides<br>
&gt; interface-id, and only when the IPv6 addresses<br>
&gt; and other elements are successfully configured by ND or DHCPv6, the<br=
>
&gt; status of NCP can come to &quot;OPEN&quot;.<br>
<br>
</div>That&#39;s still an implementation issue.<br>
<br>
For one arbitrary data point, Solaris plumbs new interfaces for each<br>
address, whether configured by ND or DHCPv6, and applications can easily<br=
>
detect these events using routing sockets or by scanning the interface<br>
table.<br>
<br>
Other systems may vary. =A0The important point, though, is that these<br>
issues have nothing whatsoever to do with the bits on the wire, and<br>
that&#39;s the only thing that&#39;s really in scope here.<br>
<br>
(The one exception I could imagine is where a protocol is so badly<br>
designed that it&#39;s just infeasible to produce a reasonable<br>
implementation. =A0I don&#39;t think that&#39;s the case here, as we have m=
ultiple<br>
independent interoperable implementations of all of the existing<br>
protocols under discussion.)<br>
<div class=3D"im"><br>
&gt; =A0 =A0 &gt; =A0 =A0o ISPs have to change current network infrastructu=
re accordingly,<br>
&gt; =A0 =A0 &gt; =A0 =A0 =A0 such as installing DHCPv6 server somewhere in=
 the network<br>
&gt; =A0 =A0 &gt; =A0 =A0 =A0 (standalone or embedded) which will not only =
increase both CAPEX<br>
&gt; =A0 =A0 &gt; =A0 =A0 =A0 and OPEX, but result in scalability problems =
when the number of<br>
&gt; =A0 =A0 &gt; =A0 =A0 =A0 subscribers grows.<br>
&gt;<br>
&gt; =A0 =A0 Change in what way?<br>
&gt;<br>
&gt;<br>
&gt; --&gt; As mentioned here, &quot;installing DHCPv6 server somewhere&quo=
t; ?<br>
&gt; Currently, there is no DHCPv4 server installed for the IPv4 over PPP.<=
br>
<br>
</div>I think that misses the point I&#39;m making.<br>
<br>
If you deploy IPv6 at all, then you need to make changes. =A0At a minimum,<=
br>
you need to configure some IPv6 routers so that all those PPP users can<br>
reach some useful sites.<br>
<br>
That&#39;s change. =A0The fact that you _may_ also need DHCPv6 (depending o=
n<br>
your deployment requirements) is just an additional item to consider.<br>
<br>
Adding these new options will _not_ obviate all change. =A0In fact,<br>
they&#39;ll just make the problem worse: users will need modified clients<b=
r>
that have these new (currently unavailable) options, and ISPs will need<br>
upgrade PPP servers that include the new features.<br></blockquote><div><br=
>--&gt; If we consider the transition of current IPv4 services over PPP to =
Dual Stack where probably both IPv4 and IPv6 are running over a single link=
<br>
established by LCP, IPv6CP will be enable, right? (may be I&#39;m wrong abo=
ut this point?)<br>If so, shall we get the DHCPv6 involved which also requi=
res all those you mentioned above? That&#39;s even harder for the legacy de=
vices on both sides of the PPP link.<br>
Or we can add several Options to IPv6CP which has been enabled?<br><br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; bor=
der-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
I don&#39;t believe that by adding yet more changes to the existing<br>
protocols one can reduce the overall amount of work.<br>
<div class=3D"im"><br>
&gt; =A0 =A0 &gt; =A0 =A0o Some unnecessary functions will be involved. For=
 example,<br>
&gt; =A0 =A0 &gt; =A0 =A0 =A0 functions like Address Resolution, On-link Pr=
efix List<br>
&gt; =A0 =A0 &gt; =A0 =A0 =A0 Advertisement, Default Router Advertisement, =
etc. defined in ND<br>
&gt; =A0 =A0 &gt; =A0 =A0 =A0 are actually not needed for a simple PPP link=
.<br>
&gt;<br>
&gt; =A0 =A0 Those sound out of scope for this working group. =A0They sound=
 like<br>
&gt; =A0 =A0 issues for one of the IPv6 or routing groups instead.<br>
&gt;<br>
&gt;<br>
&gt; --&gt; I think this is a special case for PPP. Those are still needed =
for<br>
&gt; other date links, such as Ethernet.<br>
<br>
</div>Again, how (and whether) you use higher level protocols over your PPP=
<br>
link is an issue for those higher-level protocols.<br>
<br>
I don&#39;t believe that it&#39;s in scope here.<br>
<br>
However, as a matter of design, I do think that it&#39;s unwise to create<b=
r>
new special cases where there aren&#39;t any. =A0It makes overall system<br=
>
testing for vendors much more difficult and reduces coverage.<br>
<div class=3D"im"><br>
&gt; =A0 =A0 =A0- There&#39;s simply no hope that PPP could adequately fill=
 the role<br>
&gt; =A0 =A0 =A0 =A0that DHCP serves. =A0DHCP has far too many useful exten=
sions for us<br>
&gt; =A0 =A0 =A0 =A0to repeat that working group&#39;s effort in any reason=
able manner.<br>
&gt; =A0 =A0 =A0 =A0Similar things are true for Neighbor Discovery and Rout=
er<br>
&gt; =A0 =A0 =A0 =A0Advertisements and for the general-purpose routing prot=
ocols.<br>
&gt;<br>
&gt;<br>
&gt; --&gt; While many of those extensions are not needed for PPP link.<br>
<br>
</div>How do we know when to stop?<br>
<div class=3D"im"><br>
&gt; =A0 =A0 =A0- It&#39;s a waste of time and effort. =A0It produces consi=
derably more<br>
&gt; =A0 =A0 =A0 =A0work for PPP implementors and vendors who end up needin=
g to<br>
&gt; =A0 =A0 =A0 =A0support &quot;all&quot; available mechanisms rather tha=
n using just the<br>
&gt; =A0 =A0 =A0 =A0purpose-built ones.<br>
&gt;<br>
&gt;<br>
&gt; --&gt; There have been overlapping functions between ND and DHCPv6 whi=
ch<br>
&gt; result in<br>
&gt; implementation issues. Why not solving it for PPP by PPP itself?<br>
&gt; You may argue that this will further aggravate the issue, but from<br>
&gt; different perspective,<br>
&gt; this is a straightforward way rather than waiting for ND and DHCPv6<br=
>
&gt; solving that problem.<br>
&gt; :-)<br>
<br>
</div>We&#39;re all in this boat together. =A0I see no benefit from adding<=
br>
complexity to PPP as a way of &quot;fixing&quot; somebody else&#39;s proble=
m.<br></blockquote><div><br>--&gt; Ok, that is a problem, right?<br>Only ta=
lking about PPP, not other kinds of data links.<br>If we can solve the prob=
lem on PPP, isn&#39;t it a benefit?<br>
<br></div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.=
8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Remember: hardware, software, and deployments are short in duration, but<br=
>
protocols are forever. =A0If we change this, it&#39;ll be that way &quot;fo=
rever,&quot;<br>
long after whatever problems you see in ND/DHCPv6 have been resolved.<br>
<div class=3D"im"><br>
&gt; =A0 =A0 RFC 1877 was a mistake because there already was an accepted s=
olution<br>
&gt; =A0 =A0 for this problem: folks had been running BOOTP and (later) DHC=
P over<br>
&gt; =A0 =A0 SLIP and PPP for many years. =A0And, if you look at the draft =
closely,<br>
&gt; =A0 =A0 you&#39;ll note that it didn&#39;t go through the working grou=
p process.<br>
&gt; =A0 =A0 Instead, it just documented what one vendor chose to deploy wi=
thout<br>
&gt; =A0 =A0 benefit of the usual standards review (and apparently without =
having<br>
&gt; =A0 =A0 secured the Option Type numbers through IANA).<br>
&gt;<br>
&gt;<br>
&gt; --&gt; You mean the Type numbers in RFC1877 are not assigned by IANA?<=
br>
&gt; I&#39;m sorry if I missed something.<br>
<br>
</div>My recollection of the event was that the vendor in question shipped =
the<br>
feature, then documented it in an I-D, and only after that got the<br>
numbers assigned by IANA. =A0That&#39;s why the numbers chosen (128...131) =
are<br>
so strange; they were likely picked to be &quot;unlikely&quot; to be in use=
<br>
anywhere else.<br></blockquote><div><br>--&gt; Thanks for the information.<=
br><br>Cheers,<br>Jacni<br><br>=A0<br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204,=
 204); padding-left: 1ex;">

<br>
There&#39;s more to it than that. =A0The protocol described in that RFC is<=
br>
backwards -- it has the side with the configured information giving<br>
Configure-Naks and the side using the information sending the<br>
Configure-Requests. =A0It&#39;s not like the others.<br>
<br>
In any event, the point I was making was that RFC 1877 is a poor role<br>
model for future documents. =A0And to Vern&#39;s point, I do think there is=
<br>
consensus in the working group that we do _not_ want to repeat that bit<br>
of history.<br>
<font color=3D"#888888"><br>
--<br>
</font><div><div></div><div class=3D"h5">James Carlson =A0 =A0 =A0 =A0 42.7=
03N 71.076W =A0 =A0 =A0 =A0 &lt;<a href=3D"mailto:carlsonj@workingcode.com"=
>carlsonj@workingcode.com</a>&gt;<br>
</div></div></blockquote></div><br>

--001636c5ac249c9d0604935e2a18--

From jacniq@gmail.com  Sun Oct 24 08:15:57 2010
Return-Path: <jacniq@gmail.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E5E4F3A688D for <pppext@core3.amsl.com>; Sun, 24 Oct 2010 08:15:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.118
X-Spam-Level: 
X-Spam-Status: No, score=-2.118 tagged_above=-999 required=5 tests=[AWL=-0.120, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 MAeRck7i1de4 for <pppext@core3.amsl.com>; Sun, 24 Oct 2010 08:15:55 -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 0100A3A68A7 for <pppext@ietf.org>; Sun, 24 Oct 2010 08:15:54 -0700 (PDT)
Received: by bwz12 with SMTP id 12so2810102bwz.31 for <pppext@ietf.org>; Sun, 24 Oct 2010 08:17:37 -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; bh=lTqnE/LG50P/8i0cVPzter5eZr1RC1+/mlytJ1OXFcE=; b=ldE36yM637t3S1Y1Hz9lho5xglde2TLMATuWW2JpSC3p++Sl9PQAPWDEoqgDa8KniK aemxlDE/hcBLqaJGYVn4dFWUkVg8/ZNnRO+H7gQ9TgoGeQk9OYjANvZbfDORnKBmE7gr YbB9yZehzo7UmFLfBPpzFX1sWkjifB0qGoiok=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=lyYbhUi/s6IPbJGSFmFqbo2k4JQ440LiU4FjDV33slCyIXbyc0+JwkX7+0H7s/3gBP w1iBTJBb4fIlHIm6kVSK2bcgUoX2o3oCp37z/C5XF0S3ygbUfyWyRdmYaLQ87nhDmS0I yPRA2EEIrln2AMEC7nkS/k9yhpoKUqmShyuuk=
MIME-Version: 1.0
Received: by 10.204.62.136 with SMTP id x8mr3979965bkh.192.1287933457242; Sun, 24 Oct 2010 08:17:37 -0700 (PDT)
Received: by 10.204.66.129 with HTTP; Sun, 24 Oct 2010 08:17:37 -0700 (PDT)
In-Reply-To: <201010201148.29798.fitz@jfitz.com>
References: <201010200936.o9K9auaj016890@carlson.workingcode.com> <AANLkTi=Ew3MW9_L-jKPsdGU8SYGYzwnuzB_yhKOexpco@mail.gmail.com> <4CBF3044.3090102@workingcode.com> <201010201148.29798.fitz@jfitz.com>
Date: Sun, 24 Oct 2010 23:17:37 +0800
Message-ID: <AANLkTi=xu-9E3XJuHgnEfYhTPrH9xG9cx8_W1qNPYyse@mail.gmail.com>
From: Jacni Qin <jacniq@gmail.com>
To: John Fitzgibbon <fitz@jfitz.com>
Content-Type: multipart/alternative; boundary=001636c5ac24369ab604935e6075
Cc: pppext@ietf.org, huj@ctbri.com.cn
Subject: Re: [Pppext] I-D Action:draft-hu-pppext-ipv6cp-requirements-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Oct 2010 15:15:58 -0000

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

Dear John,

Thanks for your comments, please see below,

On Thu, Oct 21, 2010 at 2:48 AM, John Fitzgibbon <fitz@jfitz.com> wrote:

> > we have multiple
> > independent interoperable implementations of all of the existing
> > protocols under discussion.
>
> I agree.
>
> Significant IPv6 rollouts have already gone through interoperability
> testing.
> The various combinations of PPP, Stateless IPv6 Auto-Discovery and
> Stateful/Stateless DHCPv6 are reasonably well established at this point.
>
> In relation to the question about increased risks and response times, I'd
> imagine that introducing an IPv6CP option as an alternative config
> mechanism
> will increase the overall complexity of a fully interoperable system, and,
> everything else being equal, adding complexity increases risk. In terms of
> response, if you end up needing DHCPv6 anyway for some other purpose, then
> you're probably increasing the overall response time if some config is
> negotiated by IPv6CP and some by DHCPv6.
>
> While it's certainly tempting to start down the path of "if I did just this
> one thing in IPv6CP, I wouldn't need ND or DHCPv6...", we know from
> experience that this causes more trouble than it's worth as the list of
> "just
> one more thing" grows.
>
> Bottom line: PPP is designed for establishing a link, DHCP is designed for
> (extensible) configuration, and Stateless Auto-Config is designed to
> provide
> basic IPv6 connectivity. Can't we just leave it at that?
>

--> I'm not sure the if the consensus has been reached on the ND & DHCPv6
about this.
Following your point, shall we propose to disable/get rid of IPv6CP, then
run DHCP or ND over PPP?
Or just because the interface-id thing concerns us that we can't do so?

Cheers,
Jacni



>
> John Fitzgibbon
>
>
> On Wednesday 20 October 2010 11:09, James Carlson wrote:
> > Jacni Qin wrote:
> > > On Wed, Oct 20, 2010 at 9:31 PM, James Carlson <
> carlsonj@workingcode.com
> > > <mailto:carlsonj@workingcode.com>> wrote:
> > >
> > >     huj@ctbri.com.cn <mailto:huj@ctbri.com.cn> wrote:
> > >     > Some are well known, and some may be not fully discussed like,
> > >     >
> > >     >    o More transaction steps caused by extra control protocols
> > >     >       introduced will result in longer response time and higher
> > >
> > >     risk of
> > >
> > >     >       exception.
> > >
> > >     Has this problem been measured anywhere?
> > >
> > >     Are we talking about two extra packets?  Perhaps four?
> > >
> > >     What sorts of "risks" are involved?  How often do they happen and
> how
> > >     do they compare with the risks of the proposed solution?  Is there
> > > any way to mitigate the risks?
> > >
> > >
> > > --> Get all things done by IPv6CP but not involving ND or DHCPv6 ? ;-)
> >
> > That doesn't appear to answer the questions.
> >
> > Yes, of course, given sufficient time, money, and motivation, IPv6CP
> > could be redesigned to do almost any job.  We could even add a "Google
> > Query" option to it, so that users don't have to fuss with TCP or IP to
> > get their most common tasks done.  That would remove more "risk" from
> > users.
> >
> > But this isn't a case where there's infinite capacity or demand.  We
> > have to weigh the opportunities provided by new extensions against the
> > costs they impose on others (who will often be forced to implement for
> > the sake of interoperability, whether they need the feature or not).  In
> > this case, it seems to me to be very unclear what benefits we get from
> > these changes.
> >
> > Thus, I'd like to know what compels us to make changes to these
> > protocols.  Concrete examples of things that don't work with the
> > existing protocols (and can't be made to work in any reasonable manner)
> > but that do work with the proposed solution would be very helpful.
> >
> > >     >    o How to determine the moment when the status of IPv6CP
> > >     > negotiation comes to "OPEN", so as to get corresponding AAA
> > >     > activities
> > >
> > >     started?
> > >
> > >     This is an implementation issue and is out of scope in this working
> > >     group.
> > >
> > >
> > > --> I guess the authors mean that since IPv6CP just provides
> > > interface-id, and only when the IPv6 addresses
> > > and other elements are successfully configured by ND or DHCPv6, the
> > > status of NCP can come to "OPEN".
> >
> > That's still an implementation issue.
> >
> > For one arbitrary data point, Solaris plumbs new interfaces for each
> > address, whether configured by ND or DHCPv6, and applications can easily
> > detect these events using routing sockets or by scanning the interface
> > table.
> >
> > Other systems may vary.  The important point, though, is that these
> > issues have nothing whatsoever to do with the bits on the wire, and
> > that's the only thing that's really in scope here.
> >
> > (The one exception I could imagine is where a protocol is so badly
> > designed that it's just infeasible to produce a reasonable
> > implementation.  I don't think that's the case here, as we have multiple
> > independent interoperable implementations of all of the existing
> > protocols under discussion.)
> >
> > >     >    o ISPs have to change current network infrastructure
> > >     > accordingly, such as installing DHCPv6 server somewhere in the
> > >     > network (standalone or embedded) which will not only increase
> both
> > >     > CAPEX and OPEX, but result in scalability problems when the
> number
> > >     > of subscribers grows.
> > >
> > >     Change in what way?
> > >
> > >
> > > --> As mentioned here, "installing DHCPv6 server somewhere" ?
> > > Currently, there is no DHCPv4 server installed for the IPv4 over PPP.
> >
> > I think that misses the point I'm making.
> >
> > If you deploy IPv6 at all, then you need to make changes.  At a minimum,
> > you need to configure some IPv6 routers so that all those PPP users can
> > reach some useful sites.
> >
> > That's change.  The fact that you _may_ also need DHCPv6 (depending on
> > your deployment requirements) is just an additional item to consider.
> >
> > Adding these new options will _not_ obviate all change.  In fact,
> > they'll just make the problem worse: users will need modified clients
> > that have these new (currently unavailable) options, and ISPs will need
> > upgrade PPP servers that include the new features.
> >
> > I don't believe that by adding yet more changes to the existing
> > protocols one can reduce the overall amount of work.
> >
> > >     >    o Some unnecessary functions will be involved. For example,
> > >     >       functions like Address Resolution, On-link Prefix List
> > >     >       Advertisement, Default Router Advertisement, etc. defined
> in
> > >     > ND are actually not needed for a simple PPP link.
> > >
> > >     Those sound out of scope for this working group.  They sound like
> > >     issues for one of the IPv6 or routing groups instead.
> > >
> > >
> > > --> I think this is a special case for PPP. Those are still needed for
> > > other date links, such as Ethernet.
> >
> > Again, how (and whether) you use higher level protocols over your PPP
> > link is an issue for those higher-level protocols.
> >
> > I don't believe that it's in scope here.
> >
> > However, as a matter of design, I do think that it's unwise to create
> > new special cases where there aren't any.  It makes overall system
> > testing for vendors much more difficult and reduces coverage.
> >
> > >      - There's simply no hope that PPP could adequately fill the role
> > >        that DHCP serves.  DHCP has far too many useful extensions for
> us
> > >        to repeat that working group's effort in any reasonable manner.
> > >        Similar things are true for Neighbor Discovery and Router
> > >        Advertisements and for the general-purpose routing protocols.
> > >
> > >
> > > --> While many of those extensions are not needed for PPP link.
> >
> > How do we know when to stop?
> >
> > >      - It's a waste of time and effort.  It produces considerably more
> > >        work for PPP implementors and vendors who end up needing to
> > >        support "all" available mechanisms rather than using just the
> > >        purpose-built ones.
> > >
> > >
> > > --> There have been overlapping functions between ND and DHCPv6 which
> > > result in
> > > implementation issues. Why not solving it for PPP by PPP itself?
> > > You may argue that this will further aggravate the issue, but from
> > > different perspective,
> > > this is a straightforward way rather than waiting for ND and DHCPv6
> > > solving that problem.
> > >
> > > :-)
> >
> > We're all in this boat together.  I see no benefit from adding
> > complexity to PPP as a way of "fixing" somebody else's problem.
> >
> > Remember: hardware, software, and deployments are short in duration, but
> > protocols are forever.  If we change this, it'll be that way "forever,"
> > long after whatever problems you see in ND/DHCPv6 have been resolved.
> >
> > >     RFC 1877 was a mistake because there already was an accepted
> solution
> > >     for this problem: folks had been running BOOTP and (later) DHCP
> over
> > >     SLIP and PPP for many years.  And, if you look at the draft
> closely,
> > >     you'll note that it didn't go through the working group process.
> > >     Instead, it just documented what one vendor chose to deploy without
> > >     benefit of the usual standards review (and apparently without
> having
> > >     secured the Option Type numbers through IANA).
> > >
> > >
> > > --> You mean the Type numbers in RFC1877 are not assigned by IANA?
> > > I'm sorry if I missed something.
> >
> > My recollection of the event was that the vendor in question shipped the
> > feature, then documented it in an I-D, and only after that got the
> > numbers assigned by IANA.  That's why the numbers chosen (128...131) are
> > so strange; they were likely picked to be "unlikely" to be in use
> > anywhere else.
> >
> > There's more to it than that.  The protocol described in that RFC is
> > backwards -- it has the side with the configured information giving
> > Configure-Naks and the side using the information sending the
> > Configure-Requests.  It's not like the others.
> >
> > In any event, the point I was making was that RFC 1877 is a poor role
> > model for future documents.  And to Vern's point, I do think there is
> > consensus in the working group that we do _not_ want to repeat that bit
> > of history.
>

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

<font color=3D"#000000"><font face=3D"verdana,sans-serif">Dear John,<br><br=
>Thanks for your comments, please see below,<br></font></font><br><div clas=
s=3D"gmail_quote">On Thu, Oct 21, 2010 at 2:48 AM, John Fitzgibbon <span di=
r=3D"ltr">&lt;<a href=3D"mailto:fitz@jfitz.com">fitz@jfitz.com</a>&gt;</spa=
n> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class=3D"im"=
>&gt; we have multiple<br>
&gt; independent interoperable implementations of all of the existing<br>
&gt; protocols under discussion.<br>
<br>
</div>I agree.<br>
<br>
Significant IPv6 rollouts have already gone through interoperability testin=
g.<br>
The various combinations of PPP, Stateless IPv6 Auto-Discovery and<br>
Stateful/Stateless DHCPv6 are reasonably well established at this point.<br=
>
<br>
In relation to the question about increased risks and response times, I&#39=
;d<br>
imagine that introducing an IPv6CP option as an alternative config mechanis=
m<br>
will increase the overall complexity of a fully interoperable system, and,<=
br>
everything else being equal, adding complexity increases risk. In terms of<=
br>
response, if you end up needing DHCPv6 anyway for some other purpose, then<=
br>
you&#39;re probably increasing the overall response time if some config is<=
br>
negotiated by IPv6CP and some by DHCPv6.<br>
<br>
While it&#39;s certainly tempting to start down the path of &quot;if I did =
just this<br>
one thing in IPv6CP, I wouldn&#39;t need ND or DHCPv6...&quot;, we know fro=
m<br>
experience that this causes more trouble than it&#39;s worth as the list of=
 &quot;just<br>
one more thing&quot; grows.<br>
<br>
Bottom line: PPP is designed for establishing a link, DHCP is designed for<=
br>
(extensible) configuration, and Stateless Auto-Config is designed to provid=
e<br>
basic IPv6 connectivity. Can&#39;t we just leave it at that?<br></blockquot=
e><div><br>--&gt; I&#39;m not sure the if the consensus has been reached on=
 the ND &amp; DHCPv6 about this.<br>Following your point, shall we propose =
to disable/get rid of IPv6CP, then run DHCP or ND over PPP?<br>
Or just because the interface-id thing concerns us that we can&#39;t do so?=
 <br><br>Cheers,<br>Jacni<br><br>=A0</div><blockquote class=3D"gmail_quote"=
 style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 2=
04); padding-left: 1ex;">

<font color=3D"#888888"><br>
John Fitzgibbon<br>
</font><div><div></div><div class=3D"h5"><br>
<br>
On Wednesday 20 October 2010 11:09, James Carlson wrote:<br>
&gt; Jacni Qin wrote:<br>
&gt; &gt; On Wed, Oct 20, 2010 at 9:31 PM, James Carlson &lt;<a href=3D"mai=
lto:carlsonj@workingcode.com">carlsonj@workingcode.com</a><br>
&gt; &gt; &lt;mailto:<a href=3D"mailto:carlsonj@workingcode.com">carlsonj@w=
orkingcode.com</a>&gt;&gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 <a href=3D"mailto:huj@ctbri.com.cn">huj@ctbri.com.cn</a> =
&lt;mailto:<a href=3D"mailto:huj@ctbri.com.cn">huj@ctbri.com.cn</a>&gt; wro=
te:<br>
&gt; &gt; =A0 =A0 &gt; Some are well known, and some may be not fully discu=
ssed like,<br>
&gt; &gt; =A0 =A0 &gt;<br>
&gt; &gt; =A0 =A0 &gt; =A0 =A0o More transaction steps caused by extra cont=
rol protocols<br>
&gt; &gt; =A0 =A0 &gt; =A0 =A0 =A0 introduced will result in longer respons=
e time and higher<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 risk of<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 &gt; =A0 =A0 =A0 exception.<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 Has this problem been measured anywhere?<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 Are we talking about two extra packets? =A0Perhaps four?<=
br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 What sorts of &quot;risks&quot; are involved? =A0How ofte=
n do they happen and how<br>
&gt; &gt; =A0 =A0 do they compare with the risks of the proposed solution? =
=A0Is there<br>
&gt; &gt; any way to mitigate the risks?<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; --&gt; Get all things done by IPv6CP but not involving ND or DHCP=
v6 ? ;-)<br>
&gt;<br>
&gt; That doesn&#39;t appear to answer the questions.<br>
&gt;<br>
&gt; Yes, of course, given sufficient time, money, and motivation, IPv6CP<b=
r>
&gt; could be redesigned to do almost any job. =A0We could even add a &quot=
;Google<br>
&gt; Query&quot; option to it, so that users don&#39;t have to fuss with TC=
P or IP to<br>
&gt; get their most common tasks done. =A0That would remove more &quot;risk=
&quot; from<br>
&gt; users.<br>
&gt;<br>
&gt; But this isn&#39;t a case where there&#39;s infinite capacity or deman=
d. =A0We<br>
&gt; have to weigh the opportunities provided by new extensions against the=
<br>
&gt; costs they impose on others (who will often be forced to implement for=
<br>
&gt; the sake of interoperability, whether they need the feature or not). =
=A0In<br>
&gt; this case, it seems to me to be very unclear what benefits we get from=
<br>
&gt; these changes.<br>
&gt;<br>
&gt; Thus, I&#39;d like to know what compels us to make changes to these<br=
>
&gt; protocols. =A0Concrete examples of things that don&#39;t work with the=
<br>
&gt; existing protocols (and can&#39;t be made to work in any reasonable ma=
nner)<br>
&gt; but that do work with the proposed solution would be very helpful.<br>
&gt;<br>
&gt; &gt; =A0 =A0 &gt; =A0 =A0o How to determine the moment when the status=
 of IPv6CP<br>
&gt; &gt; =A0 =A0 &gt; negotiation comes to &quot;OPEN&quot;, so as to get =
corresponding AAA<br>
&gt; &gt; =A0 =A0 &gt; activities<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 started?<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 This is an implementation issue and is out of scope in th=
is working<br>
&gt; &gt; =A0 =A0 group.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; --&gt; I guess the authors mean that since IPv6CP just provides<b=
r>
&gt; &gt; interface-id, and only when the IPv6 addresses<br>
&gt; &gt; and other elements are successfully configured by ND or DHCPv6, t=
he<br>
&gt; &gt; status of NCP can come to &quot;OPEN&quot;.<br>
&gt;<br>
&gt; That&#39;s still an implementation issue.<br>
&gt;<br>
&gt; For one arbitrary data point, Solaris plumbs new interfaces for each<b=
r>
&gt; address, whether configured by ND or DHCPv6, and applications can easi=
ly<br>
&gt; detect these events using routing sockets or by scanning the interface=
<br>
&gt; table.<br>
&gt;<br>
&gt; Other systems may vary. =A0The important point, though, is that these<=
br>
&gt; issues have nothing whatsoever to do with the bits on the wire, and<br=
>
&gt; that&#39;s the only thing that&#39;s really in scope here.<br>
&gt;<br>
&gt; (The one exception I could imagine is where a protocol is so badly<br>
&gt; designed that it&#39;s just infeasible to produce a reasonable<br>
&gt; implementation. =A0I don&#39;t think that&#39;s the case here, as we h=
ave multiple<br>
&gt; independent interoperable implementations of all of the existing<br>
&gt; protocols under discussion.)<br>
&gt;<br>
&gt; &gt; =A0 =A0 &gt; =A0 =A0o ISPs have to change current network infrast=
ructure<br>
&gt; &gt; =A0 =A0 &gt; accordingly, such as installing DHCPv6 server somewh=
ere in the<br>
&gt; &gt; =A0 =A0 &gt; network (standalone or embedded) which will not only=
 increase both<br>
&gt; &gt; =A0 =A0 &gt; CAPEX and OPEX, but result in scalability problems w=
hen the number<br>
&gt; &gt; =A0 =A0 &gt; of subscribers grows.<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 Change in what way?<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; --&gt; As mentioned here, &quot;installing DHCPv6 server somewher=
e&quot; ?<br>
&gt; &gt; Currently, there is no DHCPv4 server installed for the IPv4 over =
PPP.<br>
&gt;<br>
&gt; I think that misses the point I&#39;m making.<br>
&gt;<br>
&gt; If you deploy IPv6 at all, then you need to make changes. =A0At a mini=
mum,<br>
&gt; you need to configure some IPv6 routers so that all those PPP users ca=
n<br>
&gt; reach some useful sites.<br>
&gt;<br>
&gt; That&#39;s change. =A0The fact that you _may_ also need DHCPv6 (depend=
ing on<br>
&gt; your deployment requirements) is just an additional item to consider.<=
br>
&gt;<br>
&gt; Adding these new options will _not_ obviate all change. =A0In fact,<br=
>
&gt; they&#39;ll just make the problem worse: users will need modified clie=
nts<br>
&gt; that have these new (currently unavailable) options, and ISPs will nee=
d<br>
&gt; upgrade PPP servers that include the new features.<br>
&gt;<br>
&gt; I don&#39;t believe that by adding yet more changes to the existing<br=
>
&gt; protocols one can reduce the overall amount of work.<br>
&gt;<br>
&gt; &gt; =A0 =A0 &gt; =A0 =A0o Some unnecessary functions will be involved=
. For example,<br>
&gt; &gt; =A0 =A0 &gt; =A0 =A0 =A0 functions like Address Resolution, On-li=
nk Prefix List<br>
&gt; &gt; =A0 =A0 &gt; =A0 =A0 =A0 Advertisement, Default Router Advertisem=
ent, etc. defined in<br>
&gt; &gt; =A0 =A0 &gt; ND are actually not needed for a simple PPP link.<br=
>
&gt; &gt;<br>
&gt; &gt; =A0 =A0 Those sound out of scope for this working group. =A0They =
sound like<br>
&gt; &gt; =A0 =A0 issues for one of the IPv6 or routing groups instead.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; --&gt; I think this is a special case for PPP. Those are still ne=
eded for<br>
&gt; &gt; other date links, such as Ethernet.<br>
&gt;<br>
&gt; Again, how (and whether) you use higher level protocols over your PPP<=
br>
&gt; link is an issue for those higher-level protocols.<br>
&gt;<br>
&gt; I don&#39;t believe that it&#39;s in scope here.<br>
&gt;<br>
&gt; However, as a matter of design, I do think that it&#39;s unwise to cre=
ate<br>
&gt; new special cases where there aren&#39;t any. =A0It makes overall syst=
em<br>
&gt; testing for vendors much more difficult and reduces coverage.<br>
&gt;<br>
&gt; &gt; =A0 =A0 =A0- There&#39;s simply no hope that PPP could adequately=
 fill the role<br>
&gt; &gt; =A0 =A0 =A0 =A0that DHCP serves. =A0DHCP has far too many useful =
extensions for us<br>
&gt; &gt; =A0 =A0 =A0 =A0to repeat that working group&#39;s effort in any r=
easonable manner.<br>
&gt; &gt; =A0 =A0 =A0 =A0Similar things are true for Neighbor Discovery and=
 Router<br>
&gt; &gt; =A0 =A0 =A0 =A0Advertisements and for the general-purpose routing=
 protocols.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; --&gt; While many of those extensions are not needed for PPP link=
.<br>
&gt;<br>
&gt; How do we know when to stop?<br>
&gt;<br>
&gt; &gt; =A0 =A0 =A0- It&#39;s a waste of time and effort. =A0It produces =
considerably more<br>
&gt; &gt; =A0 =A0 =A0 =A0work for PPP implementors and vendors who end up n=
eeding to<br>
&gt; &gt; =A0 =A0 =A0 =A0support &quot;all&quot; available mechanisms rathe=
r than using just the<br>
&gt; &gt; =A0 =A0 =A0 =A0purpose-built ones.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; --&gt; There have been overlapping functions between ND and DHCPv=
6 which<br>
&gt; &gt; result in<br>
&gt; &gt; implementation issues. Why not solving it for PPP by PPP itself?<=
br>
&gt; &gt; You may argue that this will further aggravate the issue, but fro=
m<br>
&gt; &gt; different perspective,<br>
&gt; &gt; this is a straightforward way rather than waiting for ND and DHCP=
v6<br>
&gt; &gt; solving that problem.<br>
&gt; &gt;<br>
&gt; &gt; :-)<br>
&gt;<br>
&gt; We&#39;re all in this boat together. =A0I see no benefit from adding<b=
r>
&gt; complexity to PPP as a way of &quot;fixing&quot; somebody else&#39;s p=
roblem.<br>
&gt;<br>
&gt; Remember: hardware, software, and deployments are short in duration, b=
ut<br>
&gt; protocols are forever. =A0If we change this, it&#39;ll be that way &qu=
ot;forever,&quot;<br>
&gt; long after whatever problems you see in ND/DHCPv6 have been resolved.<=
br>
&gt;<br>
&gt; &gt; =A0 =A0 RFC 1877 was a mistake because there already was an accep=
ted solution<br>
&gt; &gt; =A0 =A0 for this problem: folks had been running BOOTP and (later=
) DHCP over<br>
&gt; &gt; =A0 =A0 SLIP and PPP for many years. =A0And, if you look at the d=
raft closely,<br>
&gt; &gt; =A0 =A0 you&#39;ll note that it didn&#39;t go through the working=
 group process.<br>
&gt; &gt; =A0 =A0 Instead, it just documented what one vendor chose to depl=
oy without<br>
&gt; &gt; =A0 =A0 benefit of the usual standards review (and apparently wit=
hout having<br>
&gt; &gt; =A0 =A0 secured the Option Type numbers through IANA).<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; --&gt; You mean the Type numbers in RFC1877 are not assigned by I=
ANA?<br>
&gt; &gt; I&#39;m sorry if I missed something.<br>
&gt;<br>
&gt; My recollection of the event was that the vendor in question shipped t=
he<br>
&gt; feature, then documented it in an I-D, and only after that got the<br>
&gt; numbers assigned by IANA. =A0That&#39;s why the numbers chosen (128...=
131) are<br>
&gt; so strange; they were likely picked to be &quot;unlikely&quot; to be i=
n use<br>
&gt; anywhere else.<br>
&gt;<br>
&gt; There&#39;s more to it than that. =A0The protocol described in that RF=
C is<br>
&gt; backwards -- it has the side with the configured information giving<br=
>
&gt; Configure-Naks and the side using the information sending the<br>
&gt; Configure-Requests. =A0It&#39;s not like the others.<br>
&gt;<br>
&gt; In any event, the point I was making was that RFC 1877 is a poor role<=
br>
&gt; model for future documents. =A0And to Vern&#39;s point, I do think the=
re is<br>
&gt; consensus in the working group that we do _not_ want to repeat that bi=
t<br>
&gt; of history.<br>
</div></div></blockquote></div><br>

--001636c5ac24369ab604935e6075--

From carlsonj@workingcode.com  Sun Oct 24 18:57:36 2010
Return-Path: <carlsonj@workingcode.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F73D3A692D for <pppext@core3.amsl.com>; Sun, 24 Oct 2010 18:57:36 -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_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 yAPzxS4FYkt2 for <pppext@core3.amsl.com>; Sun, 24 Oct 2010 18:57:35 -0700 (PDT)
Received: from carlson.workingcode.com (carlsonj-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1d9::2]) by core3.amsl.com (Postfix) with ESMTP id 36B1F3A692C for <pppext@ietf.org>; Sun, 24 Oct 2010 18:57:34 -0700 (PDT)
Received: from dhcp-226.workingcode.com (dhcp-226 [192.168.254.226]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id o9P1x03a022175 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Sun, 24 Oct 2010 21:59:01 -0400 (EDT)
Message-ID: <4CC4E464.8000704@workingcode.com>
Date: Sun, 24 Oct 2010 21:59:00 -0400
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.11) Gecko/20101013 Lightning/1.0b2 Thunderbird/3.1.5
MIME-Version: 1.0
To: Jacni Qin <jacniq@gmail.com>
References: <201010200936.o9K9auaj016890@carlson.workingcode.com>	<AANLkTi=Ew3MW9_L-jKPsdGU8SYGYzwnuzB_yhKOexpco@mail.gmail.com>	<4CBF3044.3090102@workingcode.com>	<201010201148.29798.fitz@jfitz.com> <AANLkTi=xu-9E3XJuHgnEfYhTPrH9xG9cx8_W1qNPYyse@mail.gmail.com>
In-Reply-To: <AANLkTi=xu-9E3XJuHgnEfYhTPrH9xG9cx8_W1qNPYyse@mail.gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-DCC-EATSERVER-Metrics: carlson; whitelist
Cc: pppext@ietf.org, huj@ctbri.com.cn
Subject: Re: [Pppext] I-D Action:draft-hu-pppext-ipv6cp-requirements-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 01:57:36 -0000

On 10/24/10 11:17 AM, Jacni Qin wrote:
> Dear John,
> 
> Thanks for your comments, please see below,
> 
> On Thu, Oct 21, 2010 at 2:48 AM, John Fitzgibbon <fitz@jfitz.com
> <mailto:fitz@jfitz.com>> wrote:
>     Bottom line: PPP is designed for establishing a link, DHCP is
>     designed for
>     (extensible) configuration, and Stateless Auto-Config is designed to
>     provide
>     basic IPv6 connectivity. Can't we just leave it at that?
> 
> 
> --> I'm not sure the if the consensus has been reached on the ND &
> DHCPv6 about this.
> Following your point, shall we propose to disable/get rid of IPv6CP,
> then run DHCP or ND over PPP?
> Or just because the interface-id thing concerns us that we can't do so?

The Interface ID problem is a fairly important issue.  IPv6's address
autoconfiguration mechanism depends on a source of IDs that's known to
be reasonably free of duplicates on a link.  The EUI-64 mechanism works
great on Ethernet, but isn't available on PPP, because PPP links just
don't have hardware addresses.

So, if one were to get rid of IPv6CP and just send unbidden IPv6
packets, how would non-duplicate IIDs be established?

In any event, I think this line of reasoning may be missing an important
point.  Even if the IID problem could be solved without IPv6CP, we have
the problem of existing implementations.

That trumps everything.  We have existing implementations of these
protocols, and they're deployed widely.  Making changes is no trivial
matter.  We can't just wipe the slate clean and do something arbitrarily
different.

I believe that includes adding extensions to IPv6CP to duplicate
functionality that's already deployed in DHCPv6.  And that's why I would
insist that we have a very compelling argument in favor of the proposed
drafts -- not just "this would be easier" but an explanation of why the
existing protocols in use today don't work.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

From carlsonj@workingcode.com  Sun Oct 24 19:08:03 2010
Return-Path: <carlsonj@workingcode.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 089DC3A6929 for <pppext@core3.amsl.com>; Sun, 24 Oct 2010 19:08:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.199
X-Spam-Level: 
X-Spam-Status: No, score=-102.199 tagged_above=-999 required=5 tests=[AWL=-0.200, 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 8yA4zgwH10vh for <pppext@core3.amsl.com>; Sun, 24 Oct 2010 19:08:02 -0700 (PDT)
Received: from carlson.workingcode.com (carlsonj-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1d9::2]) by core3.amsl.com (Postfix) with ESMTP id A48503A68A4 for <pppext@ietf.org>; Sun, 24 Oct 2010 19:08:01 -0700 (PDT)
Received: from dhcp-226.workingcode.com (dhcp-226 [192.168.254.226]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id o9P29bmO022489 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Sun, 24 Oct 2010 22:09:37 -0400 (EDT)
Message-ID: <4CC4E6E1.2070605@workingcode.com>
Date: Sun, 24 Oct 2010 22:09:37 -0400
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.11) Gecko/20101013 Lightning/1.0b2 Thunderbird/3.1.5
MIME-Version: 1.0
To: Jacni Qin <jacniq@gmail.com>
References: <201010200936.o9K9auaj016890@carlson.workingcode.com>	<4CBEEF16.1030304@workingcode.com>	<AANLkTi=Ew3MW9_L-jKPsdGU8SYGYzwnuzB_yhKOexpco@mail.gmail.com>	<4CBF3044.3090102@workingcode.com> <AANLkTimqv=vbY0vPrpAii_F4jLQYrn_Hh+ocqR2cv00B@mail.gmail.com>
In-Reply-To: <AANLkTimqv=vbY0vPrpAii_F4jLQYrn_Hh+ocqR2cv00B@mail.gmail.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-DCC-sonic.net-Metrics: carlson; whitelist
Cc: pppext@ietf.org, huj@ctbri.com.cn
Subject: Re: [Pppext] I-D Action:draft-hu-pppext-ipv6cp-requirements-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 02:08:03 -0000

On 10/24/10 11:02 AM, Jacni Qin wrote:
> On Thu, Oct 21, 2010 at 2:09 AM, James Carlson <carlsonj@workingcode.com
> <mailto:carlsonj@workingcode.com>> wrote:
>     Yes, of course, given sufficient time, money, and motivation, IPv6CP
>     could be redesigned to do almost any job.  We could even add a "Google
>     Query" option to it, so that users don't have to fuss with TCP or IP to
>     get their most common tasks done.  That would remove more "risk"
>     from users.
> 
> --> Do you want to have a try? ;-)

Of course not.  But I don't see much of a line between the extensions
proposed in these drafts and such draftier ideas.

>     Adding these new options will _not_ obviate all change.  In fact,
>     they'll just make the problem worse: users will need modified clients
>     that have these new (currently unavailable) options, and ISPs will need
>     upgrade PPP servers that include the new features.
> 
> 
> --> If we consider the transition of current IPv4 services over PPP to
> Dual Stack where probably both IPv4 and IPv6 are running over a single link
> established by LCP, IPv6CP will be enable, right? (may be I'm wrong
> about this point?)
> If so, shall we get the DHCPv6 involved which also requires all those
> you mentioned above? That's even harder for the legacy devices on both
> sides of the PPP link.
> Or we can add several Options to IPv6CP which has been enabled?

New options don't come from thin air.  They need to be designed,
implemented by many different people, integrated into useful systems,
tested widely, and finally deployed.  It's a very high barrier -- and
will undoubtedly take years to accomplish, even if we could somehow get
consensus on the changes.

There are existing systems that support IPv6CP and support DHCPv6 today.
 Those are the ones I care about most.  I care very much less about ones
that people haven't yet invented ... particularly when IPv6 has been in
deployed products for well over a decade.

Yes, I agree that if there are existing "legacy" systems that don't
support IPv6 (really? in 2010?), then the maintainers of those things
will have quite a mountain to scale.

However, I don't agree that I'm making that arduous task any easier by
agreeing to a proposal to make PPP even more complicated.  In fact, I
suspect it makes it worse.  Those implementers will have to choose between:

  a. Implement only the PPP option, which isn't deployed today, won't be
deployed tomorrow, and won't be available for some time to come.

  b. Implement both mechanisms, and figure out how to get them to work
together so that the existing protocols can be used today.

  c. Implement only the already-documented protocols, all of which are
easily available as open source code, and forget about these extensions.

Which one of those is best for this hypothetical legacy implementer?

>     We're all in this boat together.  I see no benefit from adding
>     complexity to PPP as a way of "fixing" somebody else's problem.
> 
> 
> --> Ok, that is a problem, right?
> Only talking about PPP, not other kinds of data links.
> If we can solve the problem on PPP, isn't it a benefit?

Not that I can see.  It only makes the problem more complex by having
piecemeal solutions in place.


-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

From fitz@jfitz.com  Mon Oct 25 09:33:05 2010
Return-Path: <fitz@jfitz.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F0E8A3A6AC2 for <pppext@core3.amsl.com>; Mon, 25 Oct 2010 09:33:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.008
X-Spam-Level: ****
X-Spam-Status: No, score=4.008 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_PACBELL_D=3.944, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_32=0.6, RDNS_DYNAMIC=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 IKPHcNjLNlDD for <pppext@core3.amsl.com>; Mon, 25 Oct 2010 09:33:01 -0700 (PDT)
Received: from jfitz.com (adsl-69-233-182-147.dsl.pltn13.pacbell.net [69.233.182.147]) by core3.amsl.com (Postfix) with SMTP id 2C7BF3A6AC0 for <pppext@ietf.org>; Mon, 25 Oct 2010 09:32:56 -0700 (PDT)
Received: (qmail 65980 invoked from network); 25 Oct 2010 16:34:39 -0000
Received: from office-gw-vpn.jfitz.com (HELO ?192.168.12.77?) (192.168.12.77) by bub-vpn.jfitz.com with SMTP; 25 Oct 2010 16:34:26 -0000
From: John Fitzgibbon <fitz@jfitz.com>
To: Jacni Qin <jacniq@gmail.com>
Date: Mon, 25 Oct 2010 09:32:54 -0700
User-Agent: KMail/1.9.4
References: <201010200936.o9K9auaj016890@carlson.workingcode.com> <201010201148.29798.fitz@jfitz.com> <AANLkTi=xu-9E3XJuHgnEfYhTPrH9xG9cx8_W1qNPYyse@mail.gmail.com>
In-Reply-To: <AANLkTi=xu-9E3XJuHgnEfYhTPrH9xG9cx8_W1qNPYyse@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <201010250932.54323.fitz@jfitz.com>
Cc: pppext@ietf.org, huj@ctbri.com.cn
Subject: Re: [Pppext] I-D Action:draft-hu-pppext-ipv6cp-requirements-00.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 16:33:05 -0000

Hi Jacni,
Taking the specific question you addressed to me:

> Following your point, shall we propose to disable/get rid of IPv6CP, then
> run DHCP or ND over PPP?
> Or just because the interface-id thing concerns us that we can't do so?

No, and not just because of the interface ID, but because it's mandatory:

Section 2 of RFC 2472:

   Before any IPv6 packets may be communicated, PPP MUST reach the
   Network-Layer Protocol phase, and the IPv6 Control Protocol MUST
   reach the Opened state.

Theoretically, it may be possible to complete IPv6CP without requesting any 
specific configuration, (i.e. no interface ID), but any implementations I've 
seen adhere to the following recommendation, (to the point where I'd consider 
this a de-facto "MUST"):

Section 5 of RFC 2472:
   The Interface Identifier of IPv6 unicast addresses [6] of a PPP
   interface, SHOULD be negotiated in the IPV6CP phase of the PPP
   connection setup

Once IPv6CP is complete, the remaining configuration of (an) IPv6 interface(s) 
can proceed pretty much as-normal. As noted in the RFC, you may choose to 
skip Duplicate Address Detection if you've negotiated an Interface ID, 
(because your ID should not be ACK'ed if it's not unique).

Beyond this, any issues that arise with IPv6 configuration belong in the 
domain of the appropriate IPv6 working group, though, as James points out, 
given the widespread deployment of IPv6 technology, I'd imagine that there 
would need to be a compelling argument that things are broken or unworkable 
before changes to existing protocols would be given serious consideration.

John Fitzgibbon

On Sunday 24 October 2010 08:17, Jacni Qin wrote:
> Dear John,
>
> Thanks for your comments, please see below,
>
> On Thu, Oct 21, 2010 at 2:48 AM, John Fitzgibbon <fitz@jfitz.com> wrote:
> > > we have multiple
> > > independent interoperable implementations of all of the existing
> > > protocols under discussion.
> >
> > I agree.
> >
> > Significant IPv6 rollouts have already gone through interoperability
> > testing.
> > The various combinations of PPP, Stateless IPv6 Auto-Discovery and
> > Stateful/Stateless DHCPv6 are reasonably well established at this point.
> >
> > In relation to the question about increased risks and response times, I'd
> > imagine that introducing an IPv6CP option as an alternative config
> > mechanism
> > will increase the overall complexity of a fully interoperable system,
> > and, everything else being equal, adding complexity increases risk. In
> > terms of response, if you end up needing DHCPv6 anyway for some other
> > purpose, then you're probably increasing the overall response time if
> > some config is negotiated by IPv6CP and some by DHCPv6.
> >
> > While it's certainly tempting to start down the path of "if I did just
> > this one thing in IPv6CP, I wouldn't need ND or DHCPv6...", we know from
> > experience that this causes more trouble than it's worth as the list of
> > "just
> > one more thing" grows.
> >
> > Bottom line: PPP is designed for establishing a link, DHCP is designed
> > for (extensible) configuration, and Stateless Auto-Config is designed to
> > provide
> > basic IPv6 connectivity. Can't we just leave it at that?
>
> --> I'm not sure the if the consensus has been reached on the ND & DHCPv6
> about this.
> Following your point, shall we propose to disable/get rid of IPv6CP, then
> run DHCP or ND over PPP?
> Or just because the interface-id thing concerns us that we can't do so?
>
> Cheers,
> Jacni
>
> > John Fitzgibbon
> >
> > On Wednesday 20 October 2010 11:09, James Carlson wrote:
> > > Jacni Qin wrote:
> > > > On Wed, Oct 20, 2010 at 9:31 PM, James Carlson <
> >
> > carlsonj@workingcode.com
> >
> > > > <mailto:carlsonj@workingcode.com>> wrote:
> > > >
> > > >     huj@ctbri.com.cn <mailto:huj@ctbri.com.cn> wrote:
> > > >     > Some are well known, and some may be not fully discussed like,
> > > >     >
> > > >     >    o More transaction steps caused by extra control protocols
> > > >     >       introduced will result in longer response time and higher
> > > >
> > > >     risk of
> > > >
> > > >     >       exception.
> > > >
> > > >     Has this problem been measured anywhere?
> > > >
> > > >     Are we talking about two extra packets?  Perhaps four?
> > > >
> > > >     What sorts of "risks" are involved?  How often do they happen and
> >
> > how
> >
> > > >     do they compare with the risks of the proposed solution?  Is
> > > > there any way to mitigate the risks?
> > > >
> > > >
> > > > --> Get all things done by IPv6CP but not involving ND or DHCPv6 ?
> > > > ;-)
> > >
> > > That doesn't appear to answer the questions.
> > >
> > > Yes, of course, given sufficient time, money, and motivation, IPv6CP
> > > could be redesigned to do almost any job.  We could even add a "Google
> > > Query" option to it, so that users don't have to fuss with TCP or IP to
> > > get their most common tasks done.  That would remove more "risk" from
> > > users.
> > >
> > > But this isn't a case where there's infinite capacity or demand.  We
> > > have to weigh the opportunities provided by new extensions against the
> > > costs they impose on others (who will often be forced to implement for
> > > the sake of interoperability, whether they need the feature or not). 
> > > In this case, it seems to me to be very unclear what benefits we get
> > > from these changes.
> > >
> > > Thus, I'd like to know what compels us to make changes to these
> > > protocols.  Concrete examples of things that don't work with the
> > > existing protocols (and can't be made to work in any reasonable manner)
> > > but that do work with the proposed solution would be very helpful.
> > >
> > > >     >    o How to determine the moment when the status of IPv6CP
> > > >     > negotiation comes to "OPEN", so as to get corresponding AAA
> > > >     > activities
> > > >
> > > >     started?
> > > >
> > > >     This is an implementation issue and is out of scope in this
> > > > working group.
> > > >
> > > >
> > > > --> I guess the authors mean that since IPv6CP just provides
> > > > interface-id, and only when the IPv6 addresses
> > > > and other elements are successfully configured by ND or DHCPv6, the
> > > > status of NCP can come to "OPEN".
> > >
> > > That's still an implementation issue.
> > >
> > > For one arbitrary data point, Solaris plumbs new interfaces for each
> > > address, whether configured by ND or DHCPv6, and applications can
> > > easily detect these events using routing sockets or by scanning the
> > > interface table.
> > >
> > > Other systems may vary.  The important point, though, is that these
> > > issues have nothing whatsoever to do with the bits on the wire, and
> > > that's the only thing that's really in scope here.
> > >
> > > (The one exception I could imagine is where a protocol is so badly
> > > designed that it's just infeasible to produce a reasonable
> > > implementation.  I don't think that's the case here, as we have
> > > multiple independent interoperable implementations of all of the
> > > existing protocols under discussion.)
> > >
> > > >     >    o ISPs have to change current network infrastructure
> > > >     > accordingly, such as installing DHCPv6 server somewhere in the
> > > >     > network (standalone or embedded) which will not only increase
> >
> > both
> >
> > > >     > CAPEX and OPEX, but result in scalability problems when the
> >
> > number
> >
> > > >     > of subscribers grows.
> > > >
> > > >     Change in what way?
> > > >
> > > >
> > > > --> As mentioned here, "installing DHCPv6 server somewhere" ?
> > > > Currently, there is no DHCPv4 server installed for the IPv4 over PPP.
> > >
> > > I think that misses the point I'm making.
> > >
> > > If you deploy IPv6 at all, then you need to make changes.  At a
> > > minimum, you need to configure some IPv6 routers so that all those PPP
> > > users can reach some useful sites.
> > >
> > > That's change.  The fact that you _may_ also need DHCPv6 (depending on
> > > your deployment requirements) is just an additional item to consider.
> > >
> > > Adding these new options will _not_ obviate all change.  In fact,
> > > they'll just make the problem worse: users will need modified clients
> > > that have these new (currently unavailable) options, and ISPs will need
> > > upgrade PPP servers that include the new features.
> > >
> > > I don't believe that by adding yet more changes to the existing
> > > protocols one can reduce the overall amount of work.
> > >
> > > >     >    o Some unnecessary functions will be involved. For example,
> > > >     >       functions like Address Resolution, On-link Prefix List
> > > >     >       Advertisement, Default Router Advertisement, etc. defined
> >
> > in
> >
> > > >     > ND are actually not needed for a simple PPP link.
> > > >
> > > >     Those sound out of scope for this working group.  They sound like
> > > >     issues for one of the IPv6 or routing groups instead.
> > > >
> > > >
> > > > --> I think this is a special case for PPP. Those are still needed
> > > > for other date links, such as Ethernet.
> > >
> > > Again, how (and whether) you use higher level protocols over your PPP
> > > link is an issue for those higher-level protocols.
> > >
> > > I don't believe that it's in scope here.
> > >
> > > However, as a matter of design, I do think that it's unwise to create
> > > new special cases where there aren't any.  It makes overall system
> > > testing for vendors much more difficult and reduces coverage.
> > >
> > > >      - There's simply no hope that PPP could adequately fill the role
> > > >        that DHCP serves.  DHCP has far too many useful extensions for
> >
> > us
> >
> > > >        to repeat that working group's effort in any reasonable
> > > > manner. Similar things are true for Neighbor Discovery and Router
> > > > Advertisements and for the general-purpose routing protocols.
> > > >
> > > >
> > > > --> While many of those extensions are not needed for PPP link.
> > >
> > > How do we know when to stop?
> > >
> > > >      - It's a waste of time and effort.  It produces considerably
> > > > more work for PPP implementors and vendors who end up needing to
> > > > support "all" available mechanisms rather than using just the
> > > > purpose-built ones.
> > > >
> > > >
> > > > --> There have been overlapping functions between ND and DHCPv6 which
> > > > result in
> > > > implementation issues. Why not solving it for PPP by PPP itself?
> > > > You may argue that this will further aggravate the issue, but from
> > > > different perspective,
> > > > this is a straightforward way rather than waiting for ND and DHCPv6
> > > > solving that problem.
> > > >
> > > > :-)
> > >
> > > We're all in this boat together.  I see no benefit from adding
> > > complexity to PPP as a way of "fixing" somebody else's problem.
> > >
> > > Remember: hardware, software, and deployments are short in duration,
> > > but protocols are forever.  If we change this, it'll be that way
> > > "forever," long after whatever problems you see in ND/DHCPv6 have been
> > > resolved.
> > >
> > > >     RFC 1877 was a mistake because there already was an accepted
> >
> > solution
> >
> > > >     for this problem: folks had been running BOOTP and (later) DHCP
> >
> > over
> >
> > > >     SLIP and PPP for many years.  And, if you look at the draft
> >
> > closely,
> >
> > > >     you'll note that it didn't go through the working group process.
> > > >     Instead, it just documented what one vendor chose to deploy
> > > > without benefit of the usual standards review (and apparently without
> >
> > having
> >
> > > >     secured the Option Type numbers through IANA).
> > > >
> > > >
> > > > --> You mean the Type numbers in RFC1877 are not assigned by IANA?
> > > > I'm sorry if I missed something.
> > >
> > > My recollection of the event was that the vendor in question shipped
> > > the feature, then documented it in an I-D, and only after that got the
> > > numbers assigned by IANA.  That's why the numbers chosen (128...131)
> > > are so strange; they were likely picked to be "unlikely" to be in use
> > > anywhere else.
> > >
> > > There's more to it than that.  The protocol described in that RFC is
> > > backwards -- it has the side with the configured information giving
> > > Configure-Naks and the side using the information sending the
> > > Configure-Requests.  It's not like the others.
> > >
> > > In any event, the point I was making was that RFC 1877 is a poor role
> > > model for future documents.  And to Vern's point, I do think there is
> > > consensus in the working group that we do _not_ want to repeat that bit
> > > of history.
