Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-stateful-issues-00

"Wes Beebee (wbeebee)" <wbeebee@cisco.com> Thu, 16 August 2012 17:54 UTC

Return-Path: <wbeebee@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66B5621F8678 for <dhcwg@ietfa.amsl.com>; Thu, 16 Aug 2012 10:54:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kBCfjTPBd5mZ for <dhcwg@ietfa.amsl.com>; Thu, 16 Aug 2012 10:54:14 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id ED08121F8694 for <dhcwg@ietf.org>; Thu, 16 Aug 2012 10:54:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=wbeebee@cisco.com; l=1261; q=dns/txt; s=iport; t=1345139654; x=1346349254; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=xrhW3QTfD9O5f8xwKFq7W10H8urWksxG9eNYFvr0V2I=; b=HYKcEWrxg+dMB3Z3yamVE/8wHVOzK2cBBnAKzKWSanEPDBqOYsgte/jA NyMDC7bmLoLq+Yy1CgJNbHUXHZwtYmcXBLRgkrPy9C4sd8I+FX0u3tKxb 8Ynvgmv4UatRNWaE8eVHGcsDXPpS/QWqBozh+LqYL+C8IfIZmrWbEafq3 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAPwyLVCtJV2Y/2dsb2JhbABABbotgQeCIgEEAQEBDwEnLQcdAQg2NwslAgQBEhsHh2sLmkCgOwSLMoYvA5VPjiyBZoJf
X-IronPort-AV: E=Sophos;i="4.77,780,1336348800"; d="scan'208";a="112103343"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-1.cisco.com with ESMTP; 16 Aug 2012 17:54:13 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q7GHsD4h018043 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 16 Aug 2012 17:54:13 GMT
Received: from xmb-rcd-x08.cisco.com ([169.254.8.212]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0298.004; Thu, 16 Aug 2012 12:54:12 -0500
From: "Wes Beebee (wbeebee)" <wbeebee@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, dhc WG <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-stateful-issues-00
Thread-Index: AQHNdqZP3dOUnDeDJkKs3MsN2OTAhpdc076A
Date: Thu, 16 Aug 2012 17:54:12 +0000
Message-ID: <CC52AAA5.A35F%wbeebee@cisco.com>
In-Reply-To: <0AE8374B-0E04-48FF-B71D-2EE8FAAC9ED1@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.3.120616
x-originating-ip: [161.44.175.143]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19116.000
x-tm-as-result: No--34.207200-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B54A689BECD757458BC86E932611591A@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] WGLC: draft-ietf-dhc-dhcpv6-stateful-issues-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2012 17:54:15 -0000

Why MUST the client ignore an Advertise message with no bindings?
What if stateful and stateless options are carried in the same message?
Does this mean the stateless options will be ignored just because the
stateful 
Options failed?

In general, I think this draft addresses an important problem that needs
to be 
solved urgently.  We need to think through carefully the consequences of
the proposed 
solutions, however.

- Wes

On 8/9/12 11:14 PM, "Ted Lemon" <Ted.Lemon@nominum.com> wrote:

>The authors have requested a working group last call.   The document
>describes some problems that exist in the way DHCP clients handle
>multiple stateful options, and proposes a solution that unifies the
>client state machine to accommodate these issues.
>
>This document could use additional review, so please take the time to
>read it over and comment on it if you have any comments.   If you are in
>favor of advancing the document, please say so.   If you oppose advancing
>it, please say so, and say why.   We will evaluate the consensus based on
>these responses on August 24.
>
>Thanks!
>
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www.ietf.org/mailman/listinfo/dhcwg