Re: [Pppext] FYI, draft-qin-pppext-ipv6-addr-pref-00//FW: I-D Action:draft-huang-ipv6cp-options-00.txt

Jacni Qin <jacniq@gmail.com> Thu, 11 March 2010 13:29 UTC

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 403213A67DA for <pppext@core3.amsl.com>; Thu, 11 Mar 2010 05:29:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[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 PxgQoqDd-FrY for <pppext@core3.amsl.com>; Thu, 11 Mar 2010 05:29:57 -0800 (PST)
Received: from mail-fx0-f213.google.com (mail-fx0-f213.google.com [209.85.220.213]) by core3.amsl.com (Postfix) with ESMTP id 134643A67D8 for <Pppext@ietf.org>; Thu, 11 Mar 2010 05:29:56 -0800 (PST)
Received: by fxm5 with SMTP id 5so24421fxm.29 for <Pppext@ietf.org>; Thu, 11 Mar 2010 05:29:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=n2EXJKDwVe88h7gwJrou9riu8e3G7leBkrCbTs+gBvM=; b=NWDgbmHWW0EO9RC8JV7tZ1ujWbiW3tA9FC34TgQZSq2UnU+lqLdKDOg1XPfCx3GhLu LcPOFiKuyfMjQypySnmZ0dt9GIYhUSV0LmDWhyHthfY+X4Vndyr75tUuNSLwD1ztwDwd 4ai7DS6U98PRzplVJ0TdfXj2/dVv0x7I++4gI=
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=G+oVc2kNWLsQUjsgcJrXBDz0LHjkdWeWVVOGOQzcX8R2kROIvRqUk2VDzql0Eh4cBb EzAqnmiggTW22JmXWjpKLgDmGUZhWJCrYUoIGA3oAhisrTGSMvGTcd45mDaBy3Wzh5by 1jSe+ev2EVaLnNlh2TshaLAPr5HC7wKhkHjsM=
MIME-Version: 1.0
Received: by 10.223.62.83 with SMTP id w19mr1144408fah.22.1268314198030; Thu, 11 Mar 2010 05:29:58 -0800 (PST)
In-Reply-To: <4B98EB7D.8010900@workingcode.com>
References: <e1a14dfb1003090047p3d3786a6h8663c0c8ebfb30bc@mail.gmail.com> <4B98EB7D.8010900@workingcode.com>
Date: Thu, 11 Mar 2010 21:29:57 +0800
Message-ID: <e1a14dfb1003110529j3db04f15qa2e0b58eeb950a9b@mail.gmail.com>
From: Jacni Qin <jacniq@gmail.com>
To: James Carlson <carlsonj@workingcode.com>
Content-Type: multipart/alternative; boundary="0015173ffacc3cbbf4048186699f"
Cc: Pppext@ietf.org, liyc@gsta.com, ylq@zte.com.cn
Subject: Re: [Pppext] FYI, draft-qin-pppext-ipv6-addr-pref-00//FW: I-D Action:draft-huang-ipv6cp-options-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: Thu, 11 Mar 2010 13:29:58 -0000

hi James,

i guess the overlapping was an accident, and i have seen again your
clarification and thanks.

On Thu, Mar 11, 2010 at 9:09 PM, James Carlson <carlsonj@workingcode.com>wrote:

> Jacni Qin wrote:
> > sorry that i missed the discussion,
> >
> > we also think that the necessary extensions of IPv6CP should be done, and
> a draft has been posted in Jan.
> >
> > please refer to:
> > http://tools.ietf.org/html/draft-qin-pppext-ipv6-addr-pref-00
>
> Are you just pointing out the overlap in these two documents, or are you
> requesting that we go ahead to try to determine whether consensus exists
> on either of these or on some other document?
>
> I suggest that if there's a community for this sort of extension, then
> it would be very good for the proponents to get together and propose a
> single coherent document rather than intermittent individual
> contributions.  It would be even better if that combined document had a
> clear and compelling argument that explains why the existing mechanisms
> used on all other media are insufficient for PPP links, and thus a new
> mechanism is required.
>
> I'm unconvinced that there's any need for either of the mechanisms
> proposed, but I'm certainly willing to call for consensus on these as
> working group items, if you feel you're ready.
>
> --
> James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>
>