Re: [Pppext] I-D Action:draft-hu-pppext-ipv6cp-requirements-00.txt

James Carlson <carlsonj@workingcode.com> Mon, 18 October 2010 18:55 UTC

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>