
From Carl.Wuyts@technicolor.com  Thu Dec  1 02:35:07 2011
Return-Path: <Carl.Wuyts@technicolor.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 2CCE321F8C48 for <dhcwg@ietfa.amsl.com>; Thu,  1 Dec 2011 02:35:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ECMZ-H0wBYov for <dhcwg@ietfa.amsl.com>; Thu,  1 Dec 2011 02:35:06 -0800 (PST)
Received: from na3sys009aog110.obsmtp.com (na3sys009aog110.obsmtp.com [74.125.149.203]) by ietfa.amsl.com (Postfix) with ESMTP id 8013621F8C45 for <dhcwg@ietf.org>; Thu,  1 Dec 2011 02:35:03 -0800 (PST)
Received: from MOPESEDGE01.eu.thmulti.com ([129.35.174.203]) (using TLSv1) by na3sys009aob110.postini.com ([74.125.148.12]) with SMTP ID DSNKTtdYSuX6CYpvbuYBvXAjmSe1n0IgapcW@postini.com; Thu, 01 Dec 2011 02:35:05 PST
Received: from MOPESMAILHC03.eu.thmulti.com (141.11.100.132) by mail3.technicolor.com (141.11.253.22) with Microsoft SMTP Server (TLS) id 8.3.192.1; Thu, 1 Dec 2011 11:30:36 +0100
Received: from MOPESMBX01.eu.thmulti.com ([169.254.155.121]) by MOPESMAILHC03.eu.thmulti.com ([141.11.100.132]) with mapi; Thu, 1 Dec 2011 11:30:42 +0100
From: Wuyts Carl <Carl.Wuyts@technicolor.com>
To: peng-wu <peng-wu@foxmail.com>, Ted Lemon <Ted.Lemon@nominum.com>, "Andre Kostur" <akostur@incognito.com>
Date: Thu, 1 Dec 2011 11:30:41 +0100
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt
Thread-Index: Acyv9AfAGMCwAjzBT0CfgR19QwKMmgAHptVg
Message-ID: <867F4B6A1672E541A94676D556793ACD0CB42FD544@MOPESMBX01.eu.thmulti.com>
References: <20111130161440.17091.31129.idtracker@ietfa.amsl.com><CAL10_BrtWTQ8aXYYd-FX09gDLAowWfRzEf5PrGu9hoff6Ki1-A@mail.gmail.com>, <0DAAE1C6-6E44-4939-962A-E4AD9E611380@nominum.com> <20111201143915185454109@foxmail.com>
In-Reply-To: <20111201143915185454109@foxmail.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt
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, 01 Dec 2011 10:35:07 -0000

Hello all,

Recently, the v6ops group have been discussing the update of RFC6204 (into =
RFC6204, latest version: http://www.ietf.org/id/draft-ietf-v6ops-6204bis-03=
.txt).  Compared with the initial RFC6204, now both 6rd and DSLite requirem=
ents have been added.
Copy from that doc:
""
DLW-4:  If the IPv6 CE Router is configured with a public IPv4
           address on its WAN interface, where public IPv4 address is
           defined as any address which is not in the private IP address
           space specified in [RFC5735], then the IPv6 CE Router SHOULD
           disable the DS-Lite B4 element.
""
This DHCP over IPv6 draft mentions the 2 mechanism: DSLite if no more publi=
c space available, and the discussed draft draft-ietf-dhc-dhcpv4-over-ipv6-=
00.txt.  I've suggested to remove the above requirement, but it ended up as=
 described above: a SHOULD requirement (was a MUST before).=20

I'd say it's getting a bit tricky now.  The DHCPv4 over IPv6 draft and the =
RFC6204bis are sharing some "components", e.g. the DSLite DHCPv6 option (RF=
C6334).  Although the requirement of RFC6204bis has been re-phrased to shou=
ld it literally says that "the CPE SHOULD disable the DSLite tunnel in case=
 of public IPv4 presence on the link", while this draft is adding an IPv4 p=
ublic address to the tunnel interface.  Both DSLite and 4over6 are in fact =
similar interface/tunnel types, so might all become a bit confusing, no ??

regs

Carl Wuyts
GCD System Architect Networking
CONNECT DIVISION
carl.wuyts@technicolor.com
tel.: +32 3 443 65 90


Prins Boudewijnlaan 47=A0=A0-=A0=A02650 Edegem=A0=A0-=A0=A0Belgium
Technicolor Delivery Technologies Belgium NV
Registered office (maatschappelijke zetel): Prins Boudewijnlaan 47, 2650 Ed=
egem, Belgium
Company registration number (ondernemingsnummer): 0428837295 - RPR Antwerpe=
n

Help preserve the color of our world - Think before you print.




-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of p=
eng-wu
Sent: donderdag 1 december 2011 7:39
To: Ted Lemon; Andre Kostur
Cc: dhc WG
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt

Hi Andre,

Thanks for your review in such a short time :) As Ted has explained, the us=
er case we already have is Hub & Spoke IPv4-over-IPv6, where end users spar=
sely distributed in the IPv6 network has IPv4 communication demand, so they=
 build IPv4-in-IPv6  tunnels with a remote router which is connected to IPv=
4. For this "tunneled" IPv4 access, end users need IPv4 address provisioned=
  from the remote router. So the IPv4 devices that wishes to operator in th=
is environment need to support IPv4-in-IPv6 tunnel besides the DHCP extensi=
on, which means changes on the device is already needed anyway.
Details on scenarios & tunnel mechanisms can be found in:=20
http://tools.ietf.org/html/draft-ietf-softwire-public-4over6-00
http://tools.ietf.org/html/draft-cui-softwire-b4-translated-ds-lite-04


About the suggestion to place the additional behaviours on the upstream rou=
ter: we actually have mechanism for this case, such as configured tunnel & =
RFC5565. But that's another secanrio. The critical difference is that, the =
ISPs don't want to provison native IPv4 in the last hop of their IPv6 netwo=
rk anymore.  They want go with only IPv6.

As to performing the 4 to 6 translation, that's a totally different story.
For example, the first thing coming to my mind is that, with 4 to 6 transla=
tion the remote end of the communication would be IPv6, while with 4over6 t=
unnel the remote end would lie in IPv4. I believe the Softwire and Behave W=
G have agreed that tunneling and translation have respective application sc=
enarios. Actually in this case, network-side
4 to 6 translation (NAT-PT) was obsoleted for quite a lot issues while host=
-side 4 to 6 translation would bring much more changes to the OS than tunne=
l. So tunnel would actually be a reasonable choice here...

Back to the blu-ray player example you raised, I guess usually such a devic=
e would locate behind a home gateway/CPE rather than connect to the ISP net=
work directly. Then your gateway/CPE would implement the CRA funtions and i=
nteract with the remote DHCP server, while your player only interacts with =
the gatway/CPE to get a private IPv4 address. Just like what happens today.=
=20

Hope this helps to understand the intension.
BTW, we're trying to find a way of implementing CRA so that it could cooper=
ate with the existing DHCP client implementation. Then we don't have to mod=
ify the client so there'll be less changes.
--------------
peng-wu
>On Nov 30, 2011, at 12:05 PM, Andre Kostur wrote:
>On first reading I'm concerned about the architecture in general.
>
>Thanks for reading it.   I don't think the use case you're describing is o=
ne that the authors of the draft have in mind; I agree with you that it's u=
nlikely that this use case would work.   However, the intended use for this=
 technique is in a device that already understands how to set up a stateles=
s 4over6 tunnel, so presumably this isn't the only change that would be req=
uired on the device.
>
>The intended use as I understand it is in a situation where we have a gene=
rally working IPv6 network, but there are a few remaining applications that=
 need IPv4 addresses.   Because these applications are sparsely distributed=
 through the network, setting up infrastructure to support them in each loc=
ation where they might be needed doesn't make sense.   Instead, you put thi=
s technology on those nodes that need it, and those nodes are expected to b=
e few, and far between.
>
>Peng Wu could probably explain the intention here better than I can.
>
>
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg

From shemant@cisco.com  Thu Dec  1 05:50:49 2011
Return-Path: <shemant@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 D0BD711E86E6 for <dhcwg@ietfa.amsl.com>; Thu,  1 Dec 2011 05:50:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.571
X-Spam-Level: 
X-Spam-Status: No, score=-6.571 tagged_above=-999 required=5 tests=[AWL=0.028,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LHpn2kgjIdD8 for <dhcwg@ietfa.amsl.com>; Thu,  1 Dec 2011 05:50:35 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 2620611E86F4 for <dhcwg@ietf.org>; Thu,  1 Dec 2011 05:50:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=1069; q=dns/txt; s=iport; t=1322747435; x=1323957035; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=YHkDh5I4jSHnSmRy5yfUmsZhTcjMFv7R5F0klf0IBDg=; b=UG2BezK52ecunWNjzkLmILToJSURgmznqTClAuh/a/oJ8oOWslVQtbEr 8MZXy0boNd02/tTOBrRnuL/fWrUrchXqt0MWjkBpnMGIAZwW6PQUyuPiF eDKQSw/BCnx/VzHISH4FwAJoEf6vkRlj2/DDId+iuyji/+3XadbypQpoY s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqMAAICF106tJXHA/2dsb2JhbABEmlaQI4EFgXIBAQEEEgEdCj8MBAIBCBEEAQELBhcBBgFFCQgBAQQBEggaoRoBnlWKPWMEiCieYA
X-IronPort-AV: E=Sophos;i="4.71,278,1320624000"; d="scan'208";a="40332256"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-7.cisco.com with ESMTP; 01 Dec 2011 13:50:33 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core2-5.cisco.com (8.14.3/8.14.3) with ESMTP id pB1DoX3W008071;  Thu, 1 Dec 2011 13:50:33 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 1 Dec 2011 07:50:32 -0600
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 1 Dec 2011 07:50:31 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C3036CE2CF@XMB-RCD-109.cisco.com>
In-Reply-To: <867F4B6A1672E541A94676D556793ACD0CB42FD544@MOPESMBX01.eu.thmulti.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt
Thread-Index: Acyv9AfAGMCwAjzBT0CfgR19QwKMmgAHptVgAAc2f2A=
References: <20111130161440.17091.31129.idtracker@ietfa.amsl.com><CAL10_BrtWTQ8aXYYd-FX09gDLAowWfRzEf5PrGu9hoff6Ki1-A@mail.gmail.com>, <0DAAE1C6-6E44-4939-962A-E4AD9E611380@nominum.com><20111201143915185454109@foxmail.com> <867F4B6A1672E541A94676D556793ACD0CB42FD544@MOPESMBX01.eu.thmulti.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Wuyts Carl" <Carl.Wuyts@technicolor.com>, "peng-wu" <peng-wu@foxmail.com>, "Ted Lemon" <Ted.Lemon@nominum.com>, "AndreKostur" <akostur@incognito.com>
X-OriginalArrivalTime: 01 Dec 2011 13:50:32.0908 (UTC) FILETIME=[31E790C0:01CCB030]
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt
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, 01 Dec 2011 13:50:50 -0000

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Wuyts Carl
Sent: Thursday, December 01, 2011 5:31 AM
To: peng-wu; Ted Lemon; AndreKostur
Cc: dhc WG
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt

>I'd say it's getting a bit tricky now.  The DHCPv4 over IPv6 draft and
the RFC6204bis are sharing some "components", e.g. the DSLite >DHCPv6
option (RFC6334).  Although the requirement of RFC6204bis has been
re-phrased to should it literally says that "the CPE SHOULD >disable the
DSLite tunnel in case of public IPv4 presence on the link",=20

Note if the CPE router WAN is assigned a public IPv4 address, the SP
supports native IPv4 and why does the CPE then need DS-Lite? I don't
think a use case exists for native IPv4 and DS-Lite running concurrently
on the CE router.  Neither does DS-Lite have a sunsetting because what
does DS-Lite sunset to?  Native IPv4?  Hmm, the reason the network went
to DS-Lite is because public IPv4 address space is depleted. =20

Hemant




From Carl.Wuyts@technicolor.com  Thu Dec  1 06:02:05 2011
Return-Path: <Carl.Wuyts@technicolor.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 B911921F8E2A for <dhcwg@ietfa.amsl.com>; Thu,  1 Dec 2011 06:02:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nv-+mTpifMgY for <dhcwg@ietfa.amsl.com>; Thu,  1 Dec 2011 06:02:05 -0800 (PST)
Received: from na3sys009aog113.obsmtp.com (na3sys009aog113.obsmtp.com [74.125.149.209]) by ietfa.amsl.com (Postfix) with ESMTP id 9ADBB11E86EE for <dhcwg@ietf.org>; Thu,  1 Dec 2011 06:01:34 -0800 (PST)
Received: from MOPESEDGE01.eu.thmulti.com ([129.35.174.203]) (using TLSv1) by na3sys009aob113.postini.com ([74.125.148.12]) with SMTP ID DSNKTteIu3D41yKg/dOt+6ol/GCxstX/PDfp@postini.com; Thu, 01 Dec 2011 06:01:38 PST
Received: from MOPESMAILHC01.eu.thmulti.com (141.11.100.25) by mail3.technicolor.com (141.11.253.22) with Microsoft SMTP Server (TLS) id 8.3.192.1; Thu, 1 Dec 2011 14:57:41 +0100
Received: from MOPESMBX01.eu.thmulti.com ([169.254.155.121]) by MOPESMAILHC01.eu.thmulti.com ([141.11.100.25]) with mapi; Thu, 1 Dec 2011 14:57:47 +0100
From: Wuyts Carl <Carl.Wuyts@technicolor.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>, peng-wu <peng-wu@foxmail.com>, Ted Lemon <Ted.Lemon@nominum.com>, AndreKostur <akostur@incognito.com>
Date: Thu, 1 Dec 2011 14:57:46 +0100
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt
Thread-Index: Acyv9AfAGMCwAjzBT0CfgR19QwKMmgAHptVgAAc2f2AAAFQm4A==
Message-ID: <867F4B6A1672E541A94676D556793ACD0CB42FD6D7@MOPESMBX01.eu.thmulti.com>
References: <20111130161440.17091.31129.idtracker@ietfa.amsl.com><CAL10_BrtWTQ8aXYYd-FX09gDLAowWfRzEf5PrGu9hoff6Ki1-A@mail.gmail.com>, <0DAAE1C6-6E44-4939-962A-E4AD9E611380@nominum.com><20111201143915185454109@foxmail.com> <867F4B6A1672E541A94676D556793ACD0CB42FD544@MOPESMBX01.eu.thmulti.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3036CE2CF@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C3036CE2CF@XMB-RCD-109.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt
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, 01 Dec 2011 14:02:05 -0000

I don't agree.  The above draft is about a v6-only access network, so CPE-P=
E link is v6-only.
I agree on the fact that you in that case don't have to use DSLite, but in =
the above draft, there's no native v4 link next to the v6.

Carl Wuyts
GCD System Architect Networking
CONNECT DIVISION
carl.wuyts@technicolor.com
tel.: +32 3 443 65 90


Prins Boudewijnlaan 47=A0=A0-=A0=A02650 Edegem=A0=A0-=A0=A0Belgium
Technicolor Delivery Technologies Belgium NV
Registered office (maatschappelijke zetel): Prins Boudewijnlaan 47, 2650 Ed=
egem, Belgium
Company registration number (ondernemingsnummer): 0428837295 - RPR Antwerpe=
n

Help preserve the color of our world - Think before you print.





-----Original Message-----
From: Hemant Singh (shemant) [mailto:shemant@cisco.com]=20
Sent: donderdag 1 december 2011 14:51
To: Wuyts Carl; peng-wu; Ted Lemon; AndreKostur
Cc: dhc WG
Subject: RE: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of W=
uyts Carl
Sent: Thursday, December 01, 2011 5:31 AM
To: peng-wu; Ted Lemon; AndreKostur
Cc: dhc WG
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt

>I'd say it's getting a bit tricky now.  The DHCPv4 over IPv6 draft and
the RFC6204bis are sharing some "components", e.g. the DSLite >DHCPv6 optio=
n (RFC6334).  Although the requirement of RFC6204bis has been re-phrased to=
 should it literally says that "the CPE SHOULD >disable the DSLite tunnel i=
n case of public IPv4 presence on the link",=20

Note if the CPE router WAN is assigned a public IPv4 address, the SP suppor=
ts native IPv4 and why does the CPE then need DS-Lite? I don't think a use =
case exists for native IPv4 and DS-Lite running concurrently on the CE rout=
er.  Neither does DS-Lite have a sunsetting because what does DS-Lite sunse=
t to?  Native IPv4?  Hmm, the reason the network went to DS-Lite is because=
 public IPv4 address space is depleted. =20

Hemant




From shemant@cisco.com  Thu Dec  1 06:06:59 2011
Return-Path: <shemant@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 1A1FE11E814F for <dhcwg@ietfa.amsl.com>; Thu,  1 Dec 2011 06:06:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.574
X-Spam-Level: 
X-Spam-Status: No, score=-6.574 tagged_above=-999 required=5 tests=[AWL=0.025,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pf6qtAtq9q+y for <dhcwg@ietfa.amsl.com>; Thu,  1 Dec 2011 06:06:58 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 50B8B11E8130 for <dhcwg@ietf.org>; Thu,  1 Dec 2011 06:06:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=2561; q=dns/txt; s=iport; t=1322748412; x=1323958012; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=eeROc/5rGYzOTTYIRfBX4/stCV3KWPOt9GG9x4x7HQY=; b=YCJ10k15ZbEpXYx2UNkOfUc4oCBX6dxpkZGE0ZS4ri/dF16RnusBjP0Z 9OmHBBxldOjTGJoJU2l47P4O3RmWqLbFsePfUxVZnPGvddOo4Wxp4f535 9jYBsTeXlnwwDHbAMnRc3ZvxOqIPuF/tAFFOdyeNhx7MIjaH1HgdkQa7X 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqMAAMSJ106tJV2b/2dsb2JhbABEmlaQI4EFgXIBAQEEEgEdSQwEAgEIEQQBAQsGFwEGAUUJCAEBBAESCBqhGQGeVYo9YwSHdDSeYA
X-IronPort-AV: E=Sophos;i="4.71,278,1320624000"; d="scan'208";a="40319369"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-6.cisco.com with ESMTP; 01 Dec 2011 14:06:52 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pB1E6pnQ001901;  Thu, 1 Dec 2011 14:06:51 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 1 Dec 2011 08:06:26 -0600
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 1 Dec 2011 08:06:26 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C3036CE2E6@XMB-RCD-109.cisco.com>
In-Reply-To: <867F4B6A1672E541A94676D556793ACD0CB42FD6D7@MOPESMBX01.eu.thmulti.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt
Thread-Index: Acyv9AfAGMCwAjzBT0CfgR19QwKMmgAHptVgAAc2f2AAAFQm4AAAW15g
References: <20111130161440.17091.31129.idtracker@ietfa.amsl.com><CAL10_BrtWTQ8aXYYd-FX09gDLAowWfRzEf5PrGu9hoff6Ki1-A@mail.gmail.com>, <0DAAE1C6-6E44-4939-962A-E4AD9E611380@nominum.com><20111201143915185454109@foxmail.com> <867F4B6A1672E541A94676D556793ACD0CB42FD544@MOPESMBX01.eu.thmulti.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3036CE2CF@XMB-RCD-109.cisco.com> <867F4B6A1672E541A94676D556793ACD0CB42FD6D7@MOPESMBX01.eu.thmulti.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Wuyts Carl" <Carl.Wuyts@technicolor.com>, "peng-wu" <peng-wu@foxmail.com>, "Ted Lemon" <Ted.Lemon@nominum.com>, "AndreKostur" <akostur@incognito.com>
X-OriginalArrivalTime: 01 Dec 2011 14:06:26.0725 (UTC) FILETIME=[6A6C7D50:01CCB032]
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt
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, 01 Dec 2011 14:06:59 -0000

Carl,

We are in agreement.  I am not commenting on the dhcpv4-over-ipv6 =
document.  I was only explaining the CE router text as to why the text =
says if native IPv4 is available why use DS-Lite.

Hemant

-----Original Message-----
From: Wuyts Carl [mailto:Carl.Wuyts@technicolor.com]=20
Sent: Thursday, December 01, 2011 8:58 AM
To: Hemant Singh (shemant); peng-wu; Ted Lemon; AndreKostur
Cc: dhc WG
Subject: RE: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt

I don't agree.  The above draft is about a v6-only access network, so =
CPE-PE link is v6-only.
I agree on the fact that you in that case don't have to use DSLite, but =
in the above draft, there's no native v4 link next to the v6.

Carl Wuyts
GCD System Architect Networking
CONNECT DIVISION
carl.wuyts@technicolor.com
tel.: +32 3 443 65 90


Prins Boudewijnlaan 47=A0=A0-=A0=A02650 Edegem=A0=A0-=A0=A0Belgium
Technicolor Delivery Technologies Belgium NV
Registered office (maatschappelijke zetel): Prins Boudewijnlaan 47, 2650 =
Edegem, Belgium
Company registration number (ondernemingsnummer): 0428837295 - RPR =
Antwerpen

Help preserve the color of our world - Think before you print.





-----Original Message-----
From: Hemant Singh (shemant) [mailto:shemant@cisco.com]=20
Sent: donderdag 1 december 2011 14:51
To: Wuyts Carl; peng-wu; Ted Lemon; AndreKostur
Cc: dhc WG
Subject: RE: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf =
Of Wuyts Carl
Sent: Thursday, December 01, 2011 5:31 AM
To: peng-wu; Ted Lemon; AndreKostur
Cc: dhc WG
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt

>I'd say it's getting a bit tricky now.  The DHCPv4 over IPv6 draft and
the RFC6204bis are sharing some "components", e.g. the DSLite >DHCPv6 =
option (RFC6334).  Although the requirement of RFC6204bis has been =
re-phrased to should it literally says that "the CPE SHOULD >disable the =
DSLite tunnel in case of public IPv4 presence on the link",=20

Note if the CPE router WAN is assigned a public IPv4 address, the SP =
supports native IPv4 and why does the CPE then need DS-Lite? I don't =
think a use case exists for native IPv4 and DS-Lite running concurrently =
on the CE router.  Neither does DS-Lite have a sunsetting because what =
does DS-Lite sunset to?  Native IPv4?  Hmm, the reason the network went =
to DS-Lite is because public IPv4 address space is depleted. =20

Hemant




From Carl.Wuyts@technicolor.com  Thu Dec  1 06:24:11 2011
Return-Path: <Carl.Wuyts@technicolor.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 A216811E8392 for <dhcwg@ietfa.amsl.com>; Thu,  1 Dec 2011 06:24:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rh73Z9yxusjT for <dhcwg@ietfa.amsl.com>; Thu,  1 Dec 2011 06:24:11 -0800 (PST)
Received: from na3sys009aog108.obsmtp.com (na3sys009aog108.obsmtp.com [74.125.149.199]) by ietfa.amsl.com (Postfix) with ESMTP id AE71711E8385 for <dhcwg@ietf.org>; Thu,  1 Dec 2011 06:24:06 -0800 (PST)
Received: from mopesedge02.eu.thmulti.com ([129.35.174.203]) (using TLSv1) by na3sys009aob108.postini.com ([74.125.148.12]) with SMTP ID DSNKTteOBbATYWJLfroGcm3e8dGS7C05lAHR@postini.com; Thu, 01 Dec 2011 06:24:10 PST
Received: from MOPESMAILHC03.eu.thmulti.com (141.11.100.132) by mopesedge02.eu.thmulti.com (141.11.253.23) with Microsoft SMTP Server (TLS) id 8.3.192.1; Thu, 1 Dec 2011 15:23:47 +0100
Received: from MOPESMBX01.eu.thmulti.com ([169.254.155.121]) by MOPESMAILHC03.eu.thmulti.com ([141.11.100.132]) with mapi; Thu, 1 Dec 2011 15:23:51 +0100
From: Wuyts Carl <Carl.Wuyts@technicolor.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>, peng-wu <peng-wu@foxmail.com>, Ted Lemon <Ted.Lemon@nominum.com>, AndreKostur <akostur@incognito.com>
Date: Thu, 1 Dec 2011 15:23:49 +0100
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt
Thread-Index: Acyv9AfAGMCwAjzBT0CfgR19QwKMmgAHptVgAAc2f2AAAFQm4AAAW15gAACRRbA=
Message-ID: <867F4B6A1672E541A94676D556793ACD0CB42FD70E@MOPESMBX01.eu.thmulti.com>
References: <20111130161440.17091.31129.idtracker@ietfa.amsl.com><CAL10_BrtWTQ8aXYYd-FX09gDLAowWfRzEf5PrGu9hoff6Ki1-A@mail.gmail.com>, <0DAAE1C6-6E44-4939-962A-E4AD9E611380@nominum.com><20111201143915185454109@foxmail.com> <867F4B6A1672E541A94676D556793ACD0CB42FD544@MOPESMBX01.eu.thmulti.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3036CE2CF@XMB-RCD-109.cisco.com> <867F4B6A1672E541A94676D556793ACD0CB42FD6D7@MOPESMBX01.eu.thmulti.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3036CE2E6@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C3036CE2E6@XMB-RCD-109.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt
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, 01 Dec 2011 14:24:11 -0000

No worries, but these things are all pretty much in the same area, hence yo=
u might get the feeling that some things are contra-dicting each other, suc=
h as the public IPv4 address presence and it's reqs on it in RFc6204bis.

Carl Wuyts
GCD System Architect Networking
CONNECT DIVISION
carl.wuyts@technicolor.com
tel.: +32 3 443 65 90


Prins Boudewijnlaan 47=A0=A0-=A0=A02650 Edegem=A0=A0-=A0=A0Belgium
Technicolor Delivery Technologies Belgium NV
Registered office (maatschappelijke zetel): Prins Boudewijnlaan 47, 2650 Ed=
egem, Belgium
Company registration number (ondernemingsnummer): 0428837295 - RPR Antwerpe=
n

Help preserve the color of our world - Think before you print.





-----Original Message-----
From: Hemant Singh (shemant) [mailto:shemant@cisco.com]=20
Sent: donderdag 1 december 2011 15:06
To: Wuyts Carl; peng-wu; Ted Lemon; AndreKostur
Cc: dhc WG
Subject: RE: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt

Carl,

We are in agreement.  I am not commenting on the dhcpv4-over-ipv6 document.=
  I was only explaining the CE router text as to why the text says if nativ=
e IPv4 is available why use DS-Lite.

Hemant

-----Original Message-----
From: Wuyts Carl [mailto:Carl.Wuyts@technicolor.com]
Sent: Thursday, December 01, 2011 8:58 AM
To: Hemant Singh (shemant); peng-wu; Ted Lemon; AndreKostur
Cc: dhc WG
Subject: RE: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt

I don't agree.  The above draft is about a v6-only access network, so CPE-P=
E link is v6-only.
I agree on the fact that you in that case don't have to use DSLite, but in =
the above draft, there's no native v4 link next to the v6.

Carl Wuyts
GCD System Architect Networking
CONNECT DIVISION
carl.wuyts@technicolor.com
tel.: +32 3 443 65 90


Prins Boudewijnlaan 47=A0=A0-=A0=A02650 Edegem=A0=A0-=A0=A0Belgium Technico=
lor Delivery Technologies Belgium NV Registered office (maatschappelijke ze=
tel): Prins Boudewijnlaan 47, 2650 Edegem, Belgium Company registration num=
ber (ondernemingsnummer): 0428837295 - RPR Antwerpen

Help preserve the color of our world - Think before you print.





-----Original Message-----
From: Hemant Singh (shemant) [mailto:shemant@cisco.com]
Sent: donderdag 1 december 2011 14:51
To: Wuyts Carl; peng-wu; Ted Lemon; AndreKostur
Cc: dhc WG
Subject: RE: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of W=
uyts Carl
Sent: Thursday, December 01, 2011 5:31 AM
To: peng-wu; Ted Lemon; AndreKostur
Cc: dhc WG
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt

>I'd say it's getting a bit tricky now.  The DHCPv4 over IPv6 draft and
the RFC6204bis are sharing some "components", e.g. the DSLite >DHCPv6 optio=
n (RFC6334).  Although the requirement of RFC6204bis has been re-phrased to=
 should it literally says that "the CPE SHOULD >disable the DSLite tunnel i=
n case of public IPv4 presence on the link",=20

Note if the CPE router WAN is assigned a public IPv4 address, the SP suppor=
ts native IPv4 and why does the CPE then need DS-Lite? I don't think a use =
case exists for native IPv4 and DS-Lite running concurrently on the CE rout=
er.  Neither does DS-Lite have a sunsetting because what does DS-Lite sunse=
t to?  Native IPv4?  Hmm, the reason the network went to DS-Lite is because=
 public IPv4 address space is depleted. =20

Hemant




From jouni.nospam@gmail.com  Thu Dec  1 08:30:09 2011
Return-Path: <jouni.nospam@gmail.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 7E2C111E8231 for <dhcwg@ietfa.amsl.com>; Thu,  1 Dec 2011 08:30:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F7gyGSmKGppb for <dhcwg@ietfa.amsl.com>; Thu,  1 Dec 2011 08:30:08 -0800 (PST)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 46BD911E822D for <dhcwg@ietf.org>; Thu,  1 Dec 2011 08:30:08 -0800 (PST)
Received: by lahj13 with SMTP id j13so950522lah.31 for <dhcwg@ietf.org>; Thu, 01 Dec 2011 08:30:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=SyWyX5yhXbyCm2xpxqhJfMafF/z1Gz6Ss7RI3CAK5dY=; b=NWouZty/yFParN5TjClrZta5C15RrjgiGRVTYEMYcLN3Fp2tIPQTGEV3Wr1gZEqacV P753AEmh9oMCB6ioMgK1ahPi9Xgoe9q3SkxEKdUTx64vtm2g761ZfhwYoDRSbscqV5Pm fw/9P90yrNctuP5ha/Kxe3F619KZVsxH9bO8Q=
Received: by 10.152.110.102 with SMTP id hz6mr5160760lab.11.1322757007293; Thu, 01 Dec 2011 08:30:07 -0800 (PST)
Received: from [10.37.43.191] ([77.95.242.69]) by mx.google.com with ESMTPS id px20sm5616454lab.2.2011.12.01.08.29.57 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 01 Dec 2011 08:30:02 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: jouni korhonen <jouni.nospam@gmail.com>
In-Reply-To: <EEA697BD-5981-45D9-A8B9-0551417CAAAD@nttv6.net>
Date: Thu, 1 Dec 2011 18:29:30 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DB557C30-4634-4789-A2C4-19BD79A5C769@gmail.com>
References: <EEA697BD-5981-45D9-A8B9-0551417CAAAD@nttv6.net>
To: Arifumi Matsumoto <arifumi@nttv6.net>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1084)
Subject: [dhcwg] Review of draft-ietf-6man-addr-select-opt-01
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, 01 Dec 2011 16:30:09 -0000

Hi,

I promised to make a review of this I-D. My comments can be found here:
http://deadcoderssociety.net/6man.pdf

There are two main things:
1) I suggest to remove all text that references into the future =
regarding ongoing work etc. That will look a bit weird when actual RFCs =
come out etc.
2) It is not clear what happens when DASP_OPTION is received from =
multiple sources and in all cases Section 4.2. "trust" requirements are =
met. Will the last received policy overwrite all previously learned?

Also I did not quite get the "leak of privacy information". Could you =
elaborate that a bit further in the I-D. And finally, regarding the =
prefix encoding in the option I would myself prefer 1 octet granularity =
over 4.. or is there a specific reason for selecting 4? (DHCPv6 options =
do not have alignment requirements)

- Jouni

On Nov 9, 2011, at 10:21 AM, Arifumi Matsumoto wrote:

> All,
>=20
> at Quebec, Tim Chown presented about address selection documents
> discussed in 6man WG, and requested reviewers for the draft
> draft-ietf-6man-addr-select-opt-01.
> slides are http://tools.ietf.org/agenda/81/slides/dhc-13.pdf
>=20
> IIRC, one reviewer was chosen at that time, and the other was left
> undecided.
>=20
> So, my questions are
> the review was submitted somewhere ?
> the other reviewer was chosen ?
>=20
> --
> Arifumi Matsumoto
>  NGN System Architecture Project
>  NTT Service Integration Laboratories
>  E-mail: arifumi@nttv6.net
>  TEL +81-422-59-3334 FAX +81-422-59-6364
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From Ted.Lemon@nominum.com  Thu Dec  1 08:37:15 2011
Return-Path: <Ted.Lemon@nominum.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 2280711E8295 for <dhcwg@ietfa.amsl.com>; Thu,  1 Dec 2011 08:37:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.357
X-Spam-Level: 
X-Spam-Status: No, score=-106.357 tagged_above=-999 required=5 tests=[AWL=0.241, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bwr-ZUaEOZ3A for <dhcwg@ietfa.amsl.com>; Thu,  1 Dec 2011 08:37:14 -0800 (PST)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id F1D9011E8266 for <dhcwg@ietf.org>; Thu,  1 Dec 2011 08:37:12 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKTtetLEWM7Hvgc5q6L85tF/938H1Xix9b@postini.com; Thu, 01 Dec 2011 08:37:13 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 517FC1B827C for <dhcwg@ietf.org>; Thu,  1 Dec 2011 08:36:58 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id A928B190052; Thu,  1 Dec 2011 08:36:55 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.01.0339.001; Thu, 1 Dec 2011 08:36:55 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Wuyts Carl <Carl.Wuyts@technicolor.com>
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt
Thread-Index: AQHMsBTklUmU2oOu4Uep6NgAq9bX9pXHtNAA
Date: Thu, 1 Dec 2011 16:36:54 +0000
Message-ID: <5C9A4996-07B2-479C-8A19-40CF69F8932B@nominum.com>
References: <20111130161440.17091.31129.idtracker@ietfa.amsl.com><CAL10_BrtWTQ8aXYYd-FX09gDLAowWfRzEf5PrGu9hoff6Ki1-A@mail.gmail.com>, <0DAAE1C6-6E44-4939-962A-E4AD9E611380@nominum.com> <20111201143915185454109@foxmail.com> <867F4B6A1672E541A94676D556793ACD0CB42FD544@MOPESMBX01.eu.thmulti.com>
In-Reply-To: <867F4B6A1672E541A94676D556793ACD0CB42FD544@MOPESMBX01.eu.thmulti.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_5C9A499607B2479C8A1940CF69F8932Bnominumcom_"
MIME-Version: 1.0
Cc: Andre Kostur <akostur@incognito.com>, dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt
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, 01 Dec 2011 16:37:15 -0000

--_000_5C9A499607B2479C8A1940CF69F8932Bnominumcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On Dec 1, 2011, at 5:30 AM, Wuyts Carl wrote:
I'd say it's getting a bit tricky now.  The DHCPv4 over IPv6 draft and the =
RFC6204bis are sharing some "components", e.g. the DSLite DHCPv6 option (RF=
C6334).  Although the requirement of RFC6204bis has been re-phrased to shou=
ld it literally says that "the CPE SHOULD disable the DSLite tunnel in case=
 of public IPv4 presence on the link", while this draft is adding an IPv4 p=
ublic address to the tunnel interface.  Both DSLite and 4over6 are in fact =
similar interface/tunnel types, so might all become a bit confusing, no ??

Carl, as a group, we are not qualified to make architectural decisions abou=
t IPv6 transition technologies that don't directly involve DHCP.   We adopt=
ed this work because we were asked to do so as part of an effort from the s=
oftwires working group.   If you think this is a bad architecture, please r=
aise that discussion there.   I get the impression that it's been discussed=
 to death, though.


--_000_5C9A499607B2479C8A1940CF69F8932Bnominumcom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <3CF404F1E8B7AC42AEA198C15ACAE5BB@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 1, 2011, at 5:30 AM, Wuyts Carl wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">I'd
 say it's getting a bit tricky now. &nbsp;The DHCPv4 over IPv6 draft and th=
e RFC6204bis are sharing some &quot;components&quot;, e.g. the DSLite DHCPv=
6 option (RFC6334). &nbsp;Although the requirement of RFC6204bis has been r=
e-phrased to should it literally says that &quot;the CPE
 SHOULD disable the DSLite tunnel in case of public IPv4 presence on the li=
nk&quot;, while this draft is adding an IPv4 public address to the tunnel i=
nterface. &nbsp;Both DSLite and 4over6 are in fact similar interface/tunnel=
 types, so might all become a bit confusing,
 no ??</span></blockquote>
</div>
<br>
<div>Carl, as a group, we are not qualified to make architectural decisions=
 about IPv6 transition technologies that don't directly involve DHCP. &nbsp=
; We adopted this work because we were asked to do so as part of an effort =
from the softwires working group. &nbsp; If
 you think this is a bad architecture, please raise that discussion there. =
&nbsp; I get the impression that it's been discussed to death, though.</div=
>
<div><br>
</div>
</body>
</html>

--_000_5C9A499607B2479C8A1940CF69F8932Bnominumcom_--

From hisuntao@gmail.com  Wed Nov 30 10:30:27 2011
Return-Path: <hisuntao@gmail.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 461271F0C3B; Wed, 30 Nov 2011 10:30:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MnXpYvYaBHdR; Wed, 30 Nov 2011 10:30:26 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 32F7421F8B29; Wed, 30 Nov 2011 10:30:26 -0800 (PST)
Received: by vcbfy13 with SMTP id fy13so793536vcb.31 for <multiple recipients>; Wed, 30 Nov 2011 10:30:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2U/S+8zlFLdKDpU5faZ4B+uGMJEMyy1I+8HOKR1ovEw=; b=fe0/7bQ7bIM2XlgYsAOfpGrSEVm306+rMrTaZpOEahVTgmA2hJ7Jb2qsTY+CBAFXjk Hm0vkzACglm4unAV5V03p4+ODKbtlxFXhhVG9dk4I5s8cjGiCSPfphqcbdBdXp7oXw7i CK+Ys+mp6D0R62XqqKHwO2qQ0Ekv5jWI8HhQo=
MIME-Version: 1.0
Received: by 10.52.24.13 with SMTP id q13mr3095610vdf.104.1322677825740; Wed, 30 Nov 2011 10:30:25 -0800 (PST)
Received: by 10.220.194.133 with HTTP; Wed, 30 Nov 2011 10:30:25 -0800 (PST)
In-Reply-To: <DF1C8CC9-13D0-494B-AB45-5A17AECD1CB4@nominum.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com> <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com> <201111212036.pALKa0eO019515@cichlid.raleigh.ibm.com> <0DF2CC29-9D10-4DCB-8B12-7216D628FAAF@nominum.com> <F4EFC3D8-AF56-4D90-AE08-767FC68CC468@employees.org> <DF1C8CC9-13D0-494B-AB45-5A17AECD1CB4@nominum.com>
Date: Thu, 1 Dec 2011 02:30:25 +0800
Message-ID: <CA+H2C9a+=JA25iBkk0XWNEuPuYkN_P1ONZUgDJXQyAVo9bV6Mw@mail.gmail.com>
From: Tao Sun <hisuntao@gmail.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=20cf3071cd00f49f6f04b2f7ed64
X-Mailman-Approved-At: Thu, 01 Dec 2011 08:40:01 -0800
Cc: Thomas Narten <narten@us.ibm.com>, "ipv6@ietf.org" <ipv6@ietf.org>, MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] [mif]  Conflict between RA and DHCP in MIF case
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: Wed, 30 Nov 2011 18:30:27 -0000

--20cf3071cd00f49f6f04b2f7ed64
Content-Type: text/plain; charset=ISO-8859-1

Sorry for jump to this discussion thread late.
The route policy shall be well considered by the operator/network. If we
discuss confliction, it is more like to be the network configuration that
may appear for MIF host rather than the mechanism of DHCPv6 or RA. Even we
only use RIO, the confliction may still apprear on different interfaces.

You may refer to the problem analysis discussed and agreed in 3GPP:
http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_85_XiAN/Docs/S2-112902.zip
Regards,

Tao
On Tue, Nov 22, 2011 at 11:31 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

>   On Nov 22, 2011, at 8:18 AM, Ole Troan wrote:
>
> for clarification, that was not my proposal. my suggestion was to merge
> all information within one "provisioning domain".
>
> unsure if we will end up with provisioning domain = link, as detection of
> multiple provisioning domains on a single link may not be trivial in all
> corner cases.
>
>
> I agree with you that right now detecting provisioning domains is not
> trivial; indeed, in some cases it's impossible.   However, if you think
> provisioning domain == link, then that's a problem that needs fixing.
> Indeed, that's *the* problem that needs fixing.   I think we have to fix
> it; if we punt, we're going to pay for it later.
>
>
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif
>
>

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

<div>Sorry for jump to this=A0discussion thread=A0late. </div>
<div>The route policy shall be well considered by the operator/network. If =
we discuss confliction, it is more like to be the network configuration tha=
t may appear for MIF host rather than the mechanism of DHCPv6 or RA. Even=
=A0we only use RIO, the confliction may still apprear on different interfac=
es.</div>

<div><br>You may=A0refer to the=A0problem analysis discussed and agreed in =
3GPP:<br><a href=3D"http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_85_XiAN/D=
ocs/S2-112902.zip">http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_85_XiAN/Do=
cs/S2-112902.zip</a><br>
</div>
<div>Regards,</div>
<div>=A0</div>
<div>Tao<br></div>
<div class=3D"gmail_quote">On Tue, Nov 22, 2011 at 11:31 PM, Ted Lemon <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:Ted.Lemon@nominum.com">Ted.Lemon@nominu=
m.com</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex=
; PADDING-LEFT: 1ex" class=3D"gmail_quote">
<div style=3D"WORD-WRAP: break-word">
<div class=3D"im">
<div>
<div>On Nov 22, 2011, at 8:18 AM, Ole Troan wrote:</div>
<blockquote type=3D"cite"><span style=3D"TEXT-TRANSFORM: none; TEXT-INDENT:=
 0px; BORDER-COLLAPSE: separate; FONT: medium Helvetica; WHITE-SPACE: norma=
l; LETTER-SPACING: normal; WORD-SPACING: 0px">for clarification, that was n=
ot my proposal. my suggestion was to merge all information within one &quot=
;provisioning domain&quot;.</span></blockquote>

<blockquote type=3D"cite"><span style=3D"TEXT-TRANSFORM: none; TEXT-INDENT:=
 0px; BORDER-COLLAPSE: separate; FONT: medium Helvetica; WHITE-SPACE: norma=
l; LETTER-SPACING: normal; WORD-SPACING: 0px">unsure if we will end up with=
 provisioning domain =3D link, as detection of multiple provisioning domain=
s on a single link may not be trivial in all corner cases.</span></blockquo=
te>
</div><br></div>
<div>I agree with you that right now detecting provisioning domains is not =
trivial; indeed, in some cases it&#39;s impossible. =A0 However, if you thi=
nk provisioning domain =3D=3D link, then that&#39;s a problem that needs fi=
xing. =A0 Indeed, that&#39;s *the* problem that needs fixing. =A0 I think w=
e have to fix it; if we punt, we&#39;re going to pay for it later.</div>

<div><br></div></div><br>_______________________________________________<br=
>mif mailing list<br><a href=3D"mailto:mif@ietf.org">mif@ietf.org</a><br><a=
 href=3D"https://www.ietf.org/mailman/listinfo/mif" target=3D"_blank">https=
://www.ietf.org/mailman/listinfo/mif</a><br>
<br></blockquote></div><br>

--20cf3071cd00f49f6f04b2f7ed64--

From peng-wu@foxmail.com  Thu Dec  1 09:03:30 2011
Return-Path: <peng-wu@foxmail.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 288B51F0C74 for <dhcwg@ietfa.amsl.com>; Thu,  1 Dec 2011 09:03:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.667
X-Spam-Level: ****
X-Spam-Status: No, score=4.667 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_DSN=1.495, FROM_EXCESS_BASE64=1.456, HTML_MESSAGE=0.001, HTML_NONELEMENT_30_40=0.001, J_CHICKENPOX_13=0.6, MIME_BASE64_TEXT=1.753, RCVD_IN_BL_SPAMCOP_NET=1.96]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lfww-HlWkz-Y for <dhcwg@ietfa.amsl.com>; Thu,  1 Dec 2011 09:03:28 -0800 (PST)
Received: from smtpbg55.qq.com (smtpbg55.qq.com [64.71.138.44]) by ietfa.amsl.com (Postfix) with SMTP id 9EF631F0C71 for <dhcwg@ietf.org>; Thu,  1 Dec 2011 09:03:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qq.com; s=s0907; t=1322758983; bh=69aKp+W10QoMj6FtjM0B3S6dC1HaY5hy+rxibS8ypJ0=; h=X-QQ-SSF:X-QQ-BUSINESS-ORIGIN:X-Originating-IP:X-QQ-STYLE: X-QQ-mid:From:To:Cc:Subject:Mime-Version:Content-Type: Content-Transfer-Encoding:Date:X-Priority:Message-ID:X-QQ-MIME: X-Mailer:X-QQ-Mailer:X-QQ-ReplyHash; b=GoTCIccmsGkYqjRGVEUmwWklk7KRZ2A7vqtoW9p0iN4I7cOLDh531yiP1bEnMiQsT 3T7qYQ1aEUy0mkhuFfKMx4dJyagtO0XCWcwDGYG7B2qQGy657dcxqTDLlMouqBW
X-QQ-SSF: 00000000000000F0000000000000000
X-QQ-BUSINESS-ORIGIN: 2
X-Originating-IP: 59.66.45.204
X-QQ-STYLE: 
X-QQ-mid: webmail218t1322758978t596298
From: "=?ISO-8859-1?B?UGVuZyBXdQ==?=" <peng-wu@foxmail.com>
To: "=?ISO-8859-1?B?V3V5dHMgQ2FybA==?=" <Carl.Wuyts@technicolor.com>, "=?ISO-8859-1?B?VGVkIExlbW9u?=" <Ted.Lemon@nominum.com>, "=?ISO-8859-1?B?QW5kcmVLb3N0dXI=?=" <akostur@incognito.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_4ED7B342_084D2978_7D7A9D25"
Content-Transfer-Encoding: 8Bit
Date: Fri, 2 Dec 2011 01:02:58 +0800
X-Priority: 3
Message-ID: <tencent_11B048E361F4C8294D17BA80@qq.com>
X-QQ-MIME: TCMime 1.0 by Tencent
X-Mailer: QQMail 2.x
X-QQ-Mailer: QQMail 2.x
X-QQ-ReplyHash: 4005883252
Cc: =?ISO-8859-1?B?ZGhjIFdH?= <dhcwg@ietf.org>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt
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, 01 Dec 2011 17:03:30 -0000

This is a multi-part message in MIME format.

------=_NextPart_4ED7B342_084D2978_7D7A9D25
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: base64

SGkgQ2FybCwNCg0KVGhpcyBpcyBxdWl0ZSBpbnRlcmVzdGluZy4gVGhhbmtzIGZvciBicmlu
ZyB0aGlzIHVwLg0KTXkgdW5kZXJzdGFuZGluZyBvZiBob3cgcGVvcGxlIHdvcmsgd2l0aCBS
RkM2MDI0IGlzIHRoYXQsIHdlIGRldmVsb3AgYSBuZXcgdHJhbnNpdGlvbiB0ZWNobmlxdWUs
IGdldCBpdCBhcHByb3ZlZCBpbiBTb2Z0d2lyZSBvciBCZWhhdmUsIHRoZW4gd2UgcHV0IHRo
ZSBDUEUgcmVxdWlyZW1lbnQgb2YgdGhpcyB0ZWNoIGludG8gUkZDNjIwNC4NCkRTTGl0ZSwg
YXMgYSBzdGF0ZWZ1bCBJUHY0LW92ZXItSVB2NiB0ZWNoLCBoYXMgYmVlbiBzdGFuZGFyZGl6
ZWQsIHNvIFJGQzYwMjQgZ2V0IHVwZGF0ZSBmb3IgdGhpcyB0ZWNoLg0KTm93IHdlIGFsc28g
aGFzIDRvdmVyNiBhcyBhIHBlci1zdWJzY3JpYmVyIHN0YXRlIElQdjQtb3Zlci1JUHY2IHRl
Y2ggYW5kIE1BUCBhcyBhIHN0YXRlbGVzcyBJUHY0LW92ZXItSVB2NiB0ZWNoLCBib3RoIG9u
Z29pbmcgaW4gc29mdHdpcmUuDQpXZSdsbCBzZWUgd2hhdCB3ZSBjYW4gZG8gb24gUkZDNjIw
NCB3aGVuIHdlIGdldCA0b3ZlcjYgZG9uZSBpbiBTb2Z0d2lyZS4NCkFueXdheSwgdGhpcyBp
cyBwcm9iYWJseSBvdXQgb2YgdGhlIHNjb3BlIG9mIHRoaXMgbWFpbGluZ2xpc3QsIGJ1dCB0
aGFuayB5b3UgYWdhaW46KQ0KIA0KIA0KLS0tLS0tLS0tLS0tLS0tLS0tIE9yaWdpbmFsIC0t
LS0tLS0tLS0tLS0tLS0tLQ0KRnJvbTogICJXdXl0cyBDYXJsIjxDYXJsLld1eXRzQHRlY2hu
aWNvbG9yLmNvbT47DQpEYXRlOiAgVGh1LCBEZWMgMSwgMjAxMSAwNjozMCBQTQ0KVG86ICAi
cGVuZy13dSI8cGVuZy13dUBmb3htYWlsLmNvbT47ICJUZWQgTGVtb24iPFRlZC5MZW1vbkBu
b21pbnVtLmNvbT47ICJBbmRyZUtvc3R1ciI8YWtvc3R1ckBpbmNvZ25pdG8uY29tPjsgDQpD
YzogICJkaGMgV0ciPGRoY3dnQGlldGYub3JnPjsgDQpTdWJqZWN0OiAgUkU6IFtkaGN3Z10g
SS1EIEFjdGlvbjogZHJhZnQtaWV0Zi1kaGMtZGhjcHY0LW92ZXItaXB2Ni0wMC50eHQNCg0K
IA0KSGVsbG8gYWxsLA0KDQpSZWNlbnRseSwgdGhlIHY2b3BzIGdyb3VwIGhhdmUgYmVlbiBk
aXNjdXNzaW5nIHRoZSB1cGRhdGUgb2YgUkZDNjIwNCAoaW50byBSRkM2MjA0LCBsYXRlc3Qg
dmVyc2lvbjogaHR0cDovL3d3dy5pZXRmLm9yZy9pZC9kcmFmdC1pZXRmLXY2b3BzLTYyMDRi
aXMtMDMudHh0KS4gIENvbXBhcmVkIHdpdGggdGhlIGluaXRpYWwgUkZDNjIwNCwgbm93IGJv
dGggNnJkIGFuZCBEU0xpdGUgcmVxdWlyZW1lbnRzIGhhdmUgYmVlbiBhZGRlZC4NCkNvcHkg
ZnJvbSB0aGF0IGRvYzoNCiIiDQpETFctNDogIElmIHRoZSBJUHY2IENFIFJvdXRlciBpcyBj
b25maWd1cmVkIHdpdGggYSBwdWJsaWMgSVB2NA0KICAgICAgICAgICBhZGRyZXNzIG9uIGl0
cyBXQU4gaW50ZXJmYWNlLCB3aGVyZSBwdWJsaWMgSVB2NCBhZGRyZXNzIGlzDQogICAgICAg
ICAgIGRlZmluZWQgYXMgYW55IGFkZHJlc3Mgd2hpY2ggaXMgbm90IGluIHRoZSBwcml2YXRl
IElQIGFkZHJlc3MNCiAgICAgICAgICAgc3BhY2Ugc3BlY2lmaWVkIGluIFtSRkM1NzM1XSwg
dGhlbiB0aGUgSVB2NiBDRSBSb3V0ZXIgU0hPVUxEDQogICAgICAgICAgIGRpc2FibGUgdGhl
IERTLUxpdGUgQjQgZWxlbWVudC4NCiIiDQpUaGlzIERIQ1Agb3ZlciBJUHY2IGRyYWZ0IG1l
bnRpb25zIHRoZSAyIG1lY2hhbmlzbTogRFNMaXRlIGlmIG5vIG1vcmUgcHVibGljIHNwYWNl
IGF2YWlsYWJsZSwgYW5kIHRoZSBkaXNjdXNzZWQgZHJhZnQgZHJhZnQtaWV0Zi1kaGMtZGhj
cHY0LW92ZXItaXB2Ni0wMC50eHQuICBJJ3ZlIHN1Z2dlc3RlZCB0byByZW1vdmUgdGhlIGFi
b3ZlIHJlcXVpcmVtZW50LCBidXQgaXQgZW5kZWQgdXAgYXMgZGVzY3JpYmVkIGFib3ZlOiBh
IFNIT1VMRCByZXF1aXJlbWVudCAod2FzIGEgTVVTVCBiZWZvcmUpLiANCg0KSSdkIHNheSBp
dCdzIGdldHRpbmcgYSBiaXQgdHJpY2t5IG5vdy4gIFRoZSBESENQdjQgb3ZlciBJUHY2IGRy
YWZ0IGFuZCB0aGUgUkZDNjIwNGJpcyBhcmUgc2hhcmluZyBzb21lICJjb21wb25lbnRzIiwg
ZS5nLiB0aGUgRFNMaXRlIERIQ1B2NiBvcHRpb24gKFJGQzYzMzQpLiAgQWx0aG91Z2ggdGhl
IHJlcXVpcmVtZW50IG9mIFJGQzYyMDRiaXMgaGFzIGJlZW4gcmUtcGhyYXNlZCB0byBzaG91
bGQgaXQgbGl0ZXJhbGx5IHNheXMgdGhhdCAidGhlIENQRSBTSE9VTEQgZGlzYWJsZSB0aGUg
RFNMaXRlIHR1bm5lbCBpbiBjYXNlIG9mIHB1YmxpYyBJUHY0IHByZXNlbmNlIG9uIHRoZSBs
aW5rIiwgd2hpbGUgdGhpcyBkcmFmdCBpcyBhZGRpbmcgYW4gSVB2NCBwdWJsaWMgYWRkcmVz
cyB0byB0aGUgdHVubmVsIGludGVyZmFjZS4gIEJvdGggRFNMaXRlIGFuZCA0b3ZlcjYgYXJl
IGluIGZhY3Qgc2ltaWxhciBpbnRlcmZhY2UvdHVubmVsIHR5cGVzLCBzbyBtaWdodCBhbGwg
YmVjb21lIGEgYml0IGNvbmZ1c2luZywgbm8gPz8NCg0KcmVncw0KDQpDYXJsIFd1eXRzDQpH
Q0QgU3lzdGVtIEFyY2hpdGVjdCBOZXR3b3JraW5nDQpDT05ORUNUIERJVklTSU9ODQpjYXJs
Lnd1eXRzQHRlY2huaWNvbG9yLmNvbQ0KdGVsLjogKzMyIDMgNDQzIDY1IDkwDQoNCg0KUHJp
bnMgQm91ZGV3aWpubGFhbiA0NyAgLSAgMjY1MCBFZGVnZW0gIC0gIEJlbGdpdW0NClRlY2hu
aWNvbG9yIERlbGl2ZXJ5IFRlY2hub2xvZ2llcyBCZWxnaXVtIE5WDQpSZWdpc3RlcmVkIG9m
ZmljZSAobWFhdHNjaGFwcGVsaWprZSB6ZXRlbCk6IFByaW5zIEJvdWRld2lqbmxhYW4gNDcs
IDI2NTAgRWRlZ2VtLCBCZWxnaXVtDQpDb21wYW55IHJlZ2lzdHJhdGlvbiBudW1iZXIgKG9u
ZGVybmVtaW5nc251bW1lcik6IDA0Mjg4MzcyOTUgLSBSUFIgQW50d2VycGVuDQoNCkhlbHAg
cHJlc2VydmUgdGhlIGNvbG9yIG9mIG91ciB3b3JsZCAtIFRoaW5rIGJlZm9yZSB5b3UgcHJp
bnQuDQoNCg0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBkaGN3Zy1i
b3VuY2VzQGlldGYub3JnIFttYWlsdG86ZGhjd2ctYm91bmNlc0BpZXRmLm9yZ10gT24gQmVo
YWxmIE9mIHBlbmctd3UNClNlbnQ6IGRvbmRlcmRhZyAxIGRlY2VtYmVyIDIwMTEgNzozOQ0K
VG86IFRlZCBMZW1vbjsgQW5kcmUgS29zdHVyDQpDYzogZGhjIFdHDQpTdWJqZWN0OiBSZTog
W2RoY3dnXSBJLUQgQWN0aW9uOiBkcmFmdC1pZXRmLWRoYy1kaGNwdjQtb3Zlci1pcHY2LTAw
LnR4dA0KDQpIaSBBbmRyZSwNCg0KVGhhbmtzIGZvciB5b3VyIHJldmlldyBpbiBzdWNoIGEg
c2hvcnQgdGltZSA6KSBBcyBUZWQgaGFzIGV4cGxhaW5lZCwgdGhlIHVzZXIgY2FzZSB3ZSBh
bHJlYWR5IGhhdmUgaXMgSHViICYgU3Bva2UgSVB2NC1vdmVyLUlQdjYsIHdoZXJlIGVuZCB1
c2VycyBzcGFyc2VseSBkaXN0cmlidXRlZCBpbiB0aGUgSVB2NiBuZXR3b3JrIGhhcyBJUHY0
IGNvbW11bmljYXRpb24gZGVtYW5kLCBzbyB0aGV5IGJ1aWxkIElQdjQtaW4tSVB2NiAgdHVu
bmVscyB3aXRoIGEgcmVtb3RlIHJvdXRlciB3aGljaCBpcyBjb25uZWN0ZWQgdG8gSVB2NC4g
Rm9yIHRoaXMgInR1bm5lbGVkIiBJUHY0IGFjY2VzcywgZW5kIHVzZXJzIG5lZWQgSVB2NCBh
ZGRyZXNzIHByb3Zpc2lvbmVkICBmcm9tIHRoZSByZW1vdGUgcm91dGVyLiBTbyB0aGUgSVB2
NCBkZXZpY2VzIHRoYXQgd2lzaGVzIHRvIG9wZXJhdG9yIGluIHRoaXMgZW52aXJvbm1lbnQg
bmVlZCB0byBzdXBwb3J0IElQdjQtaW4tSVB2NiB0dW5uZWwgYmVzaWRlcyB0aGUgREhDUCBl
eHRlbnNpb24sIHdoaWNoIG1lYW5zIGNoYW5nZXMgb24gdGhlIGRldmljZSBpcyBhbHJlYWR5
IG5lZWRlZCBhbnl3YXkuDQpEZXRhaWxzIG9uIHNjZW5hcmlvcyAmIHR1bm5lbCBtZWNoYW5p
c21zIGNhbiBiZSBmb3VuZCBpbjogDQpodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFm
dC1pZXRmLXNvZnR3aXJlLXB1YmxpYy00b3ZlcjYtMDANCmh0dHA6Ly90b29scy5pZXRmLm9y
Zy9odG1sL2RyYWZ0LWN1aS1zb2Z0d2lyZS1iNC10cmFuc2xhdGVkLWRzLWxpdGUtMDQNCg0K
DQpBYm91dCB0aGUgc3VnZ2VzdGlvbiB0byBwbGFjZSB0aGUgYWRkaXRpb25hbCBiZWhhdmlv
dXJzIG9uIHRoZSB1cHN0cmVhbSByb3V0ZXI6IHdlIGFjdHVhbGx5IGhhdmUgbWVjaGFuaXNt
IGZvciB0aGlzIGNhc2UsIHN1Y2ggYXMgY29uZmlndXJlZCB0dW5uZWwgJiBSRkM1NTY1LiBC
dXQgdGhhdCdzIGFub3RoZXIgc2VjYW5yaW8uIFRoZSBjcml0aWNhbCBkaWZmZXJlbmNlIGlz
IHRoYXQsIHRoZSBJU1BzIGRvbid0IHdhbnQgdG8gcHJvdmlzb24gbmF0aXZlIElQdjQgaW4g
dGhlIGxhc3QgaG9wIG9mIHRoZWlyIElQdjYgbmV0d29yayBhbnltb3JlLiAgVGhleSB3YW50
IGdvIHdpdGggb25seSBJUHY2Lg0KDQpBcyB0byBwZXJmb3JtaW5nIHRoZSA0IHRvIDYgdHJh
bnNsYXRpb24sIHRoYXQncyBhIHRvdGFsbHkgZGlmZmVyZW50IHN0b3J5Lg0KRm9yIGV4YW1w
bGUsIHRoZSBmaXJzdCB0aGluZyBjb21pbmcgdG8gbXkgbWluZCBpcyB0aGF0LCB3aXRoIDQg
dG8gNiB0cmFuc2xhdGlvbiB0aGUgcmVtb3RlIGVuZCBvZiB0aGUgY29tbXVuaWNhdGlvbiB3
b3VsZCBiZSBJUHY2LCB3aGlsZSB3aXRoIDRvdmVyNiB0dW5uZWwgdGhlIHJlbW90ZSBlbmQg
d291bGQgbGllIGluIElQdjQuIEkgYmVsaWV2ZSB0aGUgU29mdHdpcmUgYW5kIEJlaGF2ZSBX
RyBoYXZlIGFncmVlZCB0aGF0IHR1bm5lbGluZyBhbmQgdHJhbnNsYXRpb24gaGF2ZSByZXNw
ZWN0aXZlIGFwcGxpY2F0aW9uIHNjZW5hcmlvcy4gQWN0dWFsbHkgaW4gdGhpcyBjYXNlLCBu
ZXR3b3JrLXNpZGUNCjQgdG8gNiB0cmFuc2xhdGlvbiAoTkFULVBUKSB3YXMgb2Jzb2xldGVk
IGZvciBxdWl0ZSBhIGxvdCBpc3N1ZXMgd2hpbGUgaG9zdC1zaWRlIDQgdG8gNiB0cmFuc2xh
dGlvbiB3b3VsZCBicmluZyBtdWNoIG1vcmUgY2hhbmdlcyB0byB0aGUgT1MgdGhhbiB0dW5u
ZWwuIFNvIHR1bm5lbCB3b3VsZCBhY3R1YWxseSBiZSBhIHJlYXNvbmFibGUgY2hvaWNlIGhl
cmUuLi4NCg0KQmFjayB0byB0aGUgYmx1LXJheSBwbGF5ZXIgZXhhbXBsZSB5b3UgcmFpc2Vk
LCBJIGd1ZXNzIHVzdWFsbHkgc3VjaCBhIGRldmljZSB3b3VsZCBsb2NhdGUgYmVoaW5kIGEg
aG9tZSBnYXRld2F5L0NQRSByYXRoZXIgdGhhbiBjb25uZWN0IHRvIHRoZSBJU1AgbmV0d29y
ayBkaXJlY3RseS4gVGhlbiB5b3VyIGdhdGV3YXkvQ1BFIHdvdWxkIGltcGxlbWVudCB0aGUg
Q1JBIGZ1bnRpb25zIGFuZCBpbnRlcmFjdCB3aXRoIHRoZSByZW1vdGUgREhDUCBzZXJ2ZXIs
IHdoaWxlIHlvdXIgcGxheWVyIG9ubHkgaW50ZXJhY3RzIHdpdGggdGhlIGdhdHdheS9DUEUg
dG8gZ2V0IGEgcHJpdmF0ZSBJUHY0IGFkZHJlc3MuIEp1c3QgbGlrZSB3aGF0IGhhcHBlbnMg
dG9kYXkuIA0KDQpIb3BlIHRoaXMgaGVscHMgdG8gdW5kZXJzdGFuZCB0aGUgaW50ZW5zaW9u
Lg0KQlRXLCB3ZSdyZSB0cnlpbmcgdG8gZmluZCBhIHdheSBvZiBpbXBsZW1lbnRpbmcgQ1JB
IHNvIHRoYXQgaXQgY291bGQgY29vcGVyYXRlIHdpdGggdGhlIGV4aXN0aW5nIERIQ1AgY2xp
ZW50IGltcGxlbWVudGF0aW9uLiBUaGVuIHdlIGRvbid0IGhhdmUgdG8gbW9kaWZ5IHRoZSBj
bGllbnQgc28gdGhlcmUnbGwgYmUgbGVzcyBjaGFuZ2VzLg0KLS0tLS0tLS0tLS0tLS0NCnBl
bmctd3UNCj5PbiBOb3YgMzAsIDIwMTEsIGF0IDEyOjA1IFBNLCBBbmRyZSBLb3N0dXIgd3Jv
dGU6DQo+T24gZmlyc3QgcmVhZGluZyBJJ20gY29uY2VybmVkIGFib3V0IHRoZSBhcmNoaXRl
Y3R1cmUgaW4gZ2VuZXJhbC4NCj4NCj5UaGFua3MgZm9yIHJlYWRpbmcgaXQuICAgSSBkb24n
dCB0aGluayB0aGUgdXNlIGNhc2UgeW91J3JlIGRlc2NyaWJpbmcgaXMgb25lIHRoYXQgdGhl
IGF1dGhvcnMgb2YgdGhlIGRyYWZ0IGhhdmUgaW4gbWluZDsgSSBhZ3JlZSB3aXRoIHlvdSB0
aGF0IGl0J3MgdW5saWtlbHkgdGhhdCB0aGlzIHVzZSBjYXNlIHdvdWxkIHdvcmsuICAgSG93
ZXZlciwgdGhlIGludGVuZGVkIHVzZSBmb3IgdGhpcyB0ZWNobmlxdWUgaXMgaW4gYSBkZXZp
Y2UgdGhhdCBhbHJlYWR5IHVuZGVyc3RhbmRzIGhvdyB0byBzZXQgdXAgYSBzdGF0ZWxlc3Mg
NG92ZXI2IHR1bm5lbCwgc28gcHJlc3VtYWJseSB0aGlzIGlzbid0IHRoZSBvbmx5IGNoYW5n
ZSB0aGF0IHdvdWxkIGJlIHJlcXVpcmVkIG9uIHRoZSBkZXZpY2UuDQo+DQo+VGhlIGludGVu
ZGVkIHVzZSBhcyBJIHVuZGVyc3RhbmQgaXQgaXMgaW4gYSBzaXR1YXRpb24gd2hlcmUgd2Ug
aGF2ZSBhIGdlbmVyYWxseSB3b3JraW5nIElQdjYgbmV0d29yaywgYnV0IHRoZXJlIGFyZSBh
IGZldyByZW1haW5pbmcgYXBwbGljYXRpb25zIHRoYXQgbmVlZCBJUHY0IGFkZHJlc3Nlcy4g
ICBCZWNhdXNlIHRoZXNlIGFwcGxpY2F0aW9ucyBhcmUgc3BhcnNlbHkgZGlzdHJpYnV0ZWQg
dGhyb3VnaCB0aGUgbmV0d29yaywgc2V0dGluZyB1cCBpbmZyYXN0cnVjdHVyZSB0byBzdXBw
b3J0IHRoZW0gaW4gZWFjaCBsb2NhdGlvbiB3aGVyZSB0aGV5IG1pZ2h0IGJlIG5lZWRlZCBk
b2Vzbid0IG1ha2Ugc2Vuc2UuICAgSW5zdGVhZCwgeW91IHB1dCB0aGlzIHRlY2hub2xvZ3kg
b24gdGhvc2Ugbm9kZXMgdGhhdCBuZWVkIGl0LCBhbmQgdGhvc2Ugbm9kZXMgYXJlIGV4cGVj
dGVkIHRvIGJlIGZldywgYW5kIGZhciBiZXR3ZWVuLg0KPg0KPlBlbmcgV3UgY291bGQgcHJv
YmFibHkgZXhwbGFpbiB0aGUgaW50ZW50aW9uIGhlcmUgYmV0dGVyIHRoYW4gSSBjYW4uDQo+
DQo+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0K
ZGhjd2cgbWFpbGluZyBsaXN0DQpkaGN3Z0BpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby9kaGN3Zw==

------=_NextPart_4ED7B342_084D2978_7D7A9D25
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: base64

SGkgQ2FybCw8YnI+PGJyPlRoaXMgaXMgcXVpdGUgaW50ZXJlc3RpbmcuIFRoYW5rcyBmb3Ig
YnJpbmcgdGhpcyB1cC48YnI+TXkgdW5kZXJzdGFuZGluZyBvZiBob3cgcGVvcGxlIHdvcmsg
d2l0aCBSRkM2MDI0IGlzIHRoYXQsIHdlIGRldmVsb3AgYSBuZXcgdHJhbnNpdGlvbiB0ZWNo
bmlxdWUsIGdldCBpdCBhcHByb3ZlZCBpbiBTb2Z0d2lyZSBvciBCZWhhdmUsIHRoZW4gd2Ug
cHV0IHRoZSBDUEUgcmVxdWlyZW1lbnQgb2YgdGhpcyB0ZWNoIGludG8gUkZDNjIwNC48YnI+
RFNMaXRlLCBhcyBhIHN0YXRlZnVsIElQdjQtb3Zlci1JUHY2IHRlY2gsIGhhcyBiZWVuIHN0
YW5kYXJkaXplZCwgc28gUkZDNjAyNCBnZXQgdXBkYXRlIGZvciB0aGlzIHRlY2guPGJyPk5v
dyB3ZSBhbHNvIGhhcyA0b3ZlcjYgYXMgYSBwZXItc3Vic2NyaWJlciBzdGF0ZSBJUHY0LW92
ZXItSVB2NiB0ZWNoIGFuZCBNQVAgYXMgYSBzdGF0ZWxlc3MgSVB2NC1vdmVyLUlQdjYgdGVj
aCwgYm90aCBvbmdvaW5nIGluIHNvZnR3aXJlLjxicj5XZSdsbCBzZWUgd2hhdCB3ZSBjYW4g
ZG8gb24gUkZDNjIwNCB3aGVuIHdlIGdldCA0b3ZlcjYgZG9uZSBpbiBTb2Z0d2lyZS48YnI+
PGRpdj48aW5jbHVkZXRhaWw+PGRpdj5Bbnl3YXksIHRoaXMgaXMgcHJvYmFibHkgb3V0IG9m
IHRoZSBzY29wZSBvZiB0aGlzIG1haWxpbmdsaXN0LCBidXQgdGhhbmsgeW91IGFnYWluOik8
YnI+Jm5ic3A7PC9kaXY+PGRpdj4mbmJzcDs8L2Rpdj48ZGl2IHN0eWxlPSJmb250OlZlcmRh
bmEgbm9ybWFsIDE0cHg7Y29sb3I6IzAwMDsiPjxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTJw
eDtGT05ULUZBTUlMWTogQXJpYWwgTmFycm93O3BhZGRpbmc6MnB4IDAgMnB4IDA7Ij4tLS0t
LS0tLS0tLS0tLS0tLS0mbmJzcDtPcmlnaW5hbCZuYnNwOy0tLS0tLS0tLS0tLS0tLS0tLTwv
ZGl2PjxkaXYgc3R5bGU9IkZPTlQtU0laRTogMTJweDtiYWNrZ3JvdW5kOiNlZmVmZWY7cGFk
ZGluZzo4cHg7Ij48ZGl2IGlkPSJtZW51X3NlbmRlciI+PGI+RnJvbTogPC9iPiZuYnNwOyJX
dXl0cyBDYXJsIiZsdDtDYXJsLld1eXRzQHRlY2huaWNvbG9yLmNvbSZndDs7PC9kaXY+PGRp
dj48Yj5EYXRlOiA8L2I+Jm5ic3A7VGh1LCBEZWMgMSwgMjAxMSAwNjozMCBQTTwvZGl2Pjxk
aXY+PGI+VG86IDwvYj4mbmJzcDsicGVuZy13dSImbHQ7cGVuZy13dUBmb3htYWlsLmNvbSZn
dDs7ICJUZWQgTGVtb24iJmx0O1RlZC5MZW1vbkBub21pbnVtLmNvbSZndDs7ICJBbmRyZUtv
c3R1ciImbHQ7YWtvc3R1ckBpbmNvZ25pdG8uY29tJmd0OzsgPHdicj48L2Rpdj48ZGl2Pjxi
PkNjOiA8L2I+Jm5ic3A7ImRoYyBXRyImbHQ7ZGhjd2dAaWV0Zi5vcmcmZ3Q7OyA8d2JyPjwv
ZGl2PjxkaXY+PGI+U3ViamVjdDogPC9iPiZuYnNwO1JFOiBbZGhjd2ddIEktRCBBY3Rpb246
IGRyYWZ0LWlldGYtZGhjLWRoY3B2NC1vdmVyLWlwdjYtMDAudHh0PC9kaXY+PC9kaXY+PGRp
dj4mbmJzcDs8L2Rpdj5IZWxsbyBhbGwsPGJyPjxicj5SZWNlbnRseSwgdGhlIHY2b3BzIGdy
b3VwIGhhdmUgYmVlbiBkaXNjdXNzaW5nIHRoZSB1cGRhdGUgb2YgUkZDNjIwNCAoaW50byBS
RkM2MjA0LCBsYXRlc3QgdmVyc2lvbjogaHR0cDovL3d3dy5pZXRmLm9yZy9pZC9kcmFmdC1p
ZXRmLXY2b3BzLTYyMDRiaXMtMDMudHh0KS4mbmJzcDsgQ29tcGFyZWQgd2l0aCB0aGUgaW5p
dGlhbCBSRkM2MjA0LCBub3cgYm90aCA2cmQgYW5kIERTTGl0ZSByZXF1aXJlbWVudHMgaGF2
ZSBiZWVuIGFkZGVkLjxicj5Db3B5IGZyb20gdGhhdCBkb2M6PGJyPiIiPGJyPkRMVy00OiZu
YnNwOyBJZiB0aGUgSVB2NiBDRSBSb3V0ZXIgaXMgY29uZmlndXJlZCB3aXRoIGEgcHVibGlj
IElQdjQ8YnI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7IGFkZHJlc3Mgb24gaXRzIFdBTiBpbnRlcmZhY2UsIHdoZXJlIHB1
YmxpYyBJUHY0IGFkZHJlc3MgaXM8YnI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IGRlZmluZWQgYXMgYW55IGFkZHJlc3Mg
d2hpY2ggaXMgbm90IGluIHRoZSBwcml2YXRlIElQIGFkZHJlc3M8YnI+Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHNwYWNl
IHNwZWNpZmllZCBpbiBbUkZDNTczNV0sIHRoZW4gdGhlIElQdjYgQ0UgUm91dGVyIFNIT1VM
RDxicj4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsgZGlzYWJsZSB0aGUgRFMtTGl0ZSBCNCBlbGVtZW50Ljxicj4iIjxicj5U
aGlzIERIQ1Agb3ZlciBJUHY2IGRyYWZ0IG1lbnRpb25zIHRoZSAyIG1lY2hhbmlzbTogRFNM
aXRlIGlmIG5vIG1vcmUgcHVibGljIHNwYWNlIGF2YWlsYWJsZSwgYW5kIHRoZSBkaXNjdXNz
ZWQgZHJhZnQgZHJhZnQtaWV0Zi1kaGMtZGhjcHY0LW92ZXItaXB2Ni0wMC50eHQuJm5ic3A7
IEkndmUgc3VnZ2VzdGVkIHRvIHJlbW92ZSB0aGUgYWJvdmUgcmVxdWlyZW1lbnQsIGJ1dCBp
dCBlbmRlZCB1cCBhcyBkZXNjcmliZWQgYWJvdmU6IGEgU0hPVUxEIHJlcXVpcmVtZW50ICh3
YXMgYSBNVVNUIGJlZm9yZSkuIDxicj48YnI+SSdkIHNheSBpdCdzIGdldHRpbmcgYSBiaXQg
dHJpY2t5IG5vdy4mbmJzcDsgVGhlIERIQ1B2NCBvdmVyIElQdjYgZHJhZnQgYW5kIHRoZSBS
RkM2MjA0YmlzIGFyZSBzaGFyaW5nIHNvbWUgImNvbXBvbmVudHMiLCBlLmcuIHRoZSBEU0xp
dGUgREhDUHY2IG9wdGlvbiAoUkZDNjMzNCkuJm5ic3A7IEFsdGhvdWdoIHRoZSByZXF1aXJl
bWVudCBvZiBSRkM2MjA0YmlzIGhhcyBiZWVuIHJlLXBocmFzZWQgdG8gc2hvdWxkIGl0IGxp
dGVyYWxseSBzYXlzIHRoYXQgInRoZSBDUEUgU0hPVUxEIGRpc2FibGUgdGhlIERTTGl0ZSB0
dW5uZWwgaW4gY2FzZSBvZiBwdWJsaWMgSVB2NCBwcmVzZW5jZSBvbiB0aGUgbGluayIsIHdo
aWxlIHRoaXMgZHJhZnQgaXMgYWRkaW5nIGFuIElQdjQgcHVibGljIGFkZHJlc3MgdG8gdGhl
IHR1bm5lbCBpbnRlcmZhY2UuJm5ic3A7IEJvdGggRFNMaXRlIGFuZCA0b3ZlcjYgYXJlIGlu
IGZhY3Qgc2ltaWxhciBpbnRlcmZhY2UvdHVubmVsIHR5cGVzLCBzbyBtaWdodCBhbGwgYmVj
b21lIGEgYml0IGNvbmZ1c2luZywgbm8gPz88YnI+PGJyPnJlZ3M8YnI+PGJyPkNhcmwgV3V5
dHM8YnI+R0NEIFN5c3RlbSBBcmNoaXRlY3QgTmV0d29ya2luZzxicj5DT05ORUNUIERJVklT
SU9OPGJyPmNhcmwud3V5dHNAdGVjaG5pY29sb3IuY29tPGJyPnRlbC46ICszMiAzIDQ0MyA2
NSA5MDxicj48YnI+PGJyPlByaW5zIEJvdWRld2lqbmxhYW4gNDcgIC0gIDI2NTAgRWRlZ2Vt
ICAtICBCZWxnaXVtPGJyPlRlY2huaWNvbG9yIERlbGl2ZXJ5IFRlY2hub2xvZ2llcyBCZWxn
aXVtIE5WPGJyPlJlZ2lzdGVyZWQgb2ZmaWNlIChtYWF0c2NoYXBwZWxpamtlIHpldGVsKTog
UHJpbnMgQm91ZGV3aWpubGFhbiA0NywgMjY1MCBFZGVnZW0sIEJlbGdpdW08YnI+Q29tcGFu
eSByZWdpc3RyYXRpb24gbnVtYmVyIChvbmRlcm5lbWluZ3NudW1tZXIpOiAwNDI4ODM3Mjk1
IC0gUlBSIEFudHdlcnBlbjxicj48YnI+SGVscCBwcmVzZXJ2ZSB0aGUgY29sb3Igb2Ygb3Vy
IHdvcmxkIC0gVGhpbmsgYmVmb3JlIHlvdSBwcmludC48YnI+PGJyPjxicj48YnI+PGJyPi0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPGJyPkZyb206IGRoY3dnLWJvdW5jZXNAaWV0Zi5v
cmcgW21haWx0bzpkaGN3Zy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgcGVuZy13
dTxicj5TZW50OiBkb25kZXJkYWcgMSBkZWNlbWJlciAyMDExIDc6Mzk8YnI+VG86IFRlZCBM
ZW1vbjsgQW5kcmUgS29zdHVyPGJyPkNjOiBkaGMgV0c8YnI+U3ViamVjdDogUmU6IFtkaGN3
Z10gSS1EIEFjdGlvbjogZHJhZnQtaWV0Zi1kaGMtZGhjcHY0LW92ZXItaXB2Ni0wMC50eHQ8
YnI+PGJyPkhpIEFuZHJlLDxicj48YnI+VGhhbmtzIGZvciB5b3VyIHJldmlldyBpbiBzdWNo
IGEgc2hvcnQgdGltZSA6KSBBcyBUZWQgaGFzIGV4cGxhaW5lZCwgdGhlIHVzZXIgY2FzZSB3
ZSBhbHJlYWR5IGhhdmUgaXMgSHViICZhbXA7IFNwb2tlIElQdjQtb3Zlci1JUHY2LCB3aGVy
ZSBlbmQgdXNlcnMgc3BhcnNlbHkgZGlzdHJpYnV0ZWQgaW4gdGhlIElQdjYgbmV0d29yayBo
YXMgSVB2NCBjb21tdW5pY2F0aW9uIGRlbWFuZCwgc28gdGhleSBidWlsZCBJUHY0LWluLUlQ
djYmbmJzcDsgdHVubmVscyB3aXRoIGEgcmVtb3RlIHJvdXRlciB3aGljaCBpcyBjb25uZWN0
ZWQgdG8gSVB2NC4gRm9yIHRoaXMgInR1bm5lbGVkIiBJUHY0IGFjY2VzcywgZW5kIHVzZXJz
IG5lZWQgSVB2NCBhZGRyZXNzIHByb3Zpc2lvbmVkJm5ic3A7IGZyb20gdGhlIHJlbW90ZSBy
b3V0ZXIuIFNvIHRoZSBJUHY0IGRldmljZXMgdGhhdCB3aXNoZXMgdG8gb3BlcmF0b3IgaW4g
dGhpcyBlbnZpcm9ubWVudCBuZWVkIHRvIHN1cHBvcnQgSVB2NC1pbi1JUHY2IHR1bm5lbCBi
ZXNpZGVzIHRoZSBESENQIGV4dGVuc2lvbiwgd2hpY2ggbWVhbnMgY2hhbmdlcyBvbiB0aGUg
ZGV2aWNlIGlzIGFscmVhZHkgbmVlZGVkIGFueXdheS48YnI+RGV0YWlscyBvbiBzY2VuYXJp
b3MgJmFtcDsgdHVubmVsIG1lY2hhbmlzbXMgY2FuIGJlIGZvdW5kIGluOiA8YnI+aHR0cDov
L3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1zb2Z0d2lyZS1wdWJsaWMtNG92ZXI2
LTAwPGJyPmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWN1aS1zb2Z0d2lyZS1i
NC10cmFuc2xhdGVkLWRzLWxpdGUtMDQ8YnI+PGJyPjxicj5BYm91dCB0aGUgc3VnZ2VzdGlv
biB0byBwbGFjZSB0aGUgYWRkaXRpb25hbCBiZWhhdmlvdXJzIG9uIHRoZSB1cHN0cmVhbSBy
b3V0ZXI6IHdlIGFjdHVhbGx5IGhhdmUgbWVjaGFuaXNtIGZvciB0aGlzIGNhc2UsIHN1Y2gg
YXMgY29uZmlndXJlZCB0dW5uZWwgJmFtcDsgUkZDNTU2NS4gQnV0IHRoYXQncyBhbm90aGVy
IHNlY2FucmlvLiBUaGUgY3JpdGljYWwgZGlmZmVyZW5jZSBpcyB0aGF0LCB0aGUgSVNQcyBk
b24ndCB3YW50IHRvIHByb3Zpc29uIG5hdGl2ZSBJUHY0IGluIHRoZSBsYXN0IGhvcCBvZiB0
aGVpciBJUHY2IG5ldHdvcmsgYW55bW9yZS4mbmJzcDsgVGhleSB3YW50IGdvIHdpdGggb25s
eSBJUHY2Ljxicj48YnI+QXMgdG8gcGVyZm9ybWluZyB0aGUgNCB0byA2IHRyYW5zbGF0aW9u
LCB0aGF0J3MgYSB0b3RhbGx5IGRpZmZlcmVudCBzdG9yeS48YnI+Rm9yIGV4YW1wbGUsIHRo
ZSBmaXJzdCB0aGluZyBjb21pbmcgdG8gbXkgbWluZCBpcyB0aGF0LCB3aXRoIDQgdG8gNiB0
cmFuc2xhdGlvbiB0aGUgcmVtb3RlIGVuZCBvZiB0aGUgY29tbXVuaWNhdGlvbiB3b3VsZCBi
ZSBJUHY2LCB3aGlsZSB3aXRoIDRvdmVyNiB0dW5uZWwgdGhlIHJlbW90ZSBlbmQgd291bGQg
bGllIGluIElQdjQuIEkgYmVsaWV2ZSB0aGUgU29mdHdpcmUgYW5kIEJlaGF2ZSBXRyBoYXZl
IGFncmVlZCB0aGF0IHR1bm5lbGluZyBhbmQgdHJhbnNsYXRpb24gaGF2ZSByZXNwZWN0aXZl
IGFwcGxpY2F0aW9uIHNjZW5hcmlvcy4gQWN0dWFsbHkgaW4gdGhpcyBjYXNlLCBuZXR3b3Jr
LXNpZGU8YnI+NCB0byA2IHRyYW5zbGF0aW9uIChOQVQtUFQpIHdhcyBvYnNvbGV0ZWQgZm9y
IHF1aXRlIGEgbG90IGlzc3VlcyB3aGlsZSBob3N0LXNpZGUgNCB0byA2IHRyYW5zbGF0aW9u
IHdvdWxkIGJyaW5nIG11Y2ggbW9yZSBjaGFuZ2VzIHRvIHRoZSBPUyB0aGFuIHR1bm5lbC4g
U28gdHVubmVsIHdvdWxkIGFjdHVhbGx5IGJlIGEgcmVhc29uYWJsZSBjaG9pY2UgaGVyZS4u
Ljxicj48YnI+QmFjayB0byB0aGUgYmx1LXJheSBwbGF5ZXIgZXhhbXBsZSB5b3UgcmFpc2Vk
LCBJIGd1ZXNzIHVzdWFsbHkgc3VjaCBhIGRldmljZSB3b3VsZCBsb2NhdGUgYmVoaW5kIGEg
aG9tZSBnYXRld2F5L0NQRSByYXRoZXIgdGhhbiBjb25uZWN0IHRvIHRoZSBJU1AgbmV0d29y
ayBkaXJlY3RseS4gVGhlbiB5b3VyIGdhdGV3YXkvQ1BFIHdvdWxkIGltcGxlbWVudCB0aGUg
Q1JBIGZ1bnRpb25zIGFuZCBpbnRlcmFjdCB3aXRoIHRoZSByZW1vdGUgREhDUCBzZXJ2ZXIs
IHdoaWxlIHlvdXIgcGxheWVyIG9ubHkgaW50ZXJhY3RzIHdpdGggdGhlIGdhdHdheS9DUEUg
dG8gZ2V0IGEgcHJpdmF0ZSBJUHY0IGFkZHJlc3MuIEp1c3QgbGlrZSB3aGF0IGhhcHBlbnMg
dG9kYXkuIDxicj48YnI+SG9wZSB0aGlzIGhlbHBzIHRvIHVuZGVyc3RhbmQgdGhlIGludGVu
c2lvbi48YnI+QlRXLCB3ZSdyZSB0cnlpbmcgdG8gZmluZCBhIHdheSBvZiBpbXBsZW1lbnRp
bmcgQ1JBIHNvIHRoYXQgaXQgY291bGQgY29vcGVyYXRlIHdpdGggdGhlIGV4aXN0aW5nIERI
Q1AgY2xpZW50IGltcGxlbWVudGF0aW9uLiBUaGVuIHdlIGRvbid0IGhhdmUgdG8gbW9kaWZ5
IHRoZSBjbGllbnQgc28gdGhlcmUnbGwgYmUgbGVzcyBjaGFuZ2VzLjxicj4tLS0tLS0tLS0t
LS0tLTxicj5wZW5nLXd1PGJyPiZndDtPbiBOb3YgMzAsIDIwMTEsIGF0IDEyOjA1IFBNLCBB
bmRyZSBLb3N0dXIgd3JvdGU6PGJyPiZndDtPbiBmaXJzdCByZWFkaW5nIEknbSBjb25jZXJu
ZWQgYWJvdXQgdGhlIGFyY2hpdGVjdHVyZSBpbiBnZW5lcmFsLjxicj4mZ3Q7PGJyPiZndDtU
aGFua3MgZm9yIHJlYWRpbmcgaXQuJm5ic3A7Jm5ic3A7IEkgZG9uJ3QgdGhpbmsgdGhlIHVz
ZSBjYXNlIHlvdSdyZSBkZXNjcmliaW5nIGlzIG9uZSB0aGF0IHRoZSBhdXRob3JzIG9mIHRo
ZSBkcmFmdCBoYXZlIGluIG1pbmQ7IEkgYWdyZWUgd2l0aCB5b3UgdGhhdCBpdCdzIHVubGlr
ZWx5IHRoYXQgdGhpcyB1c2UgY2FzZSB3b3VsZCB3b3JrLiZuYnNwOyZuYnNwOyBIb3dldmVy
LCB0aGUgaW50ZW5kZWQgdXNlIGZvciB0aGlzIHRlY2huaXF1ZSBpcyBpbiBhIGRldmljZSB0
aGF0IGFscmVhZHkgdW5kZXJzdGFuZHMgaG93IHRvIHNldCB1cCBhIHN0YXRlbGVzcyA0b3Zl
cjYgdHVubmVsLCBzbyBwcmVzdW1hYmx5IHRoaXMgaXNuJ3QgdGhlIG9ubHkgY2hhbmdlIHRo
YXQgd291bGQgYmUgcmVxdWlyZWQgb24gdGhlIGRldmljZS48YnI+Jmd0Ozxicj4mZ3Q7VGhl
IGludGVuZGVkIHVzZSBhcyBJIHVuZGVyc3RhbmQgaXQgaXMgaW4gYSBzaXR1YXRpb24gd2hl
cmUgd2UgaGF2ZSBhIGdlbmVyYWxseSB3b3JraW5nIElQdjYgbmV0d29yaywgYnV0IHRoZXJl
IGFyZSBhIGZldyByZW1haW5pbmcgYXBwbGljYXRpb25zIHRoYXQgbmVlZCBJUHY0IGFkZHJl
c3Nlcy4mbmJzcDsmbmJzcDsgQmVjYXVzZSB0aGVzZSBhcHBsaWNhdGlvbnMgYXJlIHNwYXJz
ZWx5IGRpc3RyaWJ1dGVkIHRocm91Z2ggdGhlIG5ldHdvcmssIHNldHRpbmcgdXAgaW5mcmFz
dHJ1Y3R1cmUgdG8gc3VwcG9ydCB0aGVtIGluIGVhY2ggbG9jYXRpb24gd2hlcmUgdGhleSBt
aWdodCBiZSBuZWVkZWQgZG9lc24ndCBtYWtlIHNlbnNlLiZuYnNwOyZuYnNwOyBJbnN0ZWFk
LCB5b3UgcHV0IHRoaXMgdGVjaG5vbG9neSBvbiB0aG9zZSBub2RlcyB0aGF0IG5lZWQgaXQs
IGFuZCB0aG9zZSBub2RlcyBhcmUgZXhwZWN0ZWQgdG8gYmUgZmV3LCBhbmQgZmFyIGJldHdl
ZW4uPGJyPiZndDs8YnI+Jmd0O1BlbmcgV3UgY291bGQgcHJvYmFibHkgZXhwbGFpbiB0aGUg
aW50ZW50aW9uIGhlcmUgYmV0dGVyIHRoYW4gSSBjYW4uPGJyPiZndDs8YnI+Jmd0Ozxicj5f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj5kaGN3
ZyBtYWlsaW5nIGxpc3Q8YnI+ZGhjd2dAaWV0Zi5vcmc8YnI+aHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby9kaGN3Zzxicj48L2Rpdj48L2luY2x1ZGV0YWlsPjwvZGl2
Pg==

------=_NextPart_4ED7B342_084D2978_7D7A9D25--


From Carl.Wuyts@technicolor.com  Thu Dec  1 23:22:39 2011
Return-Path: <Carl.Wuyts@technicolor.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 7B3F711E8098 for <dhcwg@ietfa.amsl.com>; Thu,  1 Dec 2011 23:22:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.289
X-Spam-Level: 
X-Spam-Status: No, score=-5.289 tagged_above=-999 required=5 tests=[AWL=-1.111, BAYES_00=-2.599, EXTRA_MPART_TYPE=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_GIF_ATTACH=1.42]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TCQrYT1lbYzJ for <dhcwg@ietfa.amsl.com>; Thu,  1 Dec 2011 23:22:37 -0800 (PST)
Received: from na3sys009aog106.obsmtp.com (na3sys009aob106.obsmtp.com [74.125.149.76]) by ietfa.amsl.com (Postfix) with ESMTP id E082E11E807F for <dhcwg@ietf.org>; Thu,  1 Dec 2011 23:22:32 -0800 (PST)
Received: from MOPESEDGE01.eu.thmulti.com ([129.35.174.203]) (using TLSv1) by na3sys009aob106.postini.com ([74.125.148.12]) with SMTP ID DSNKTth8p0aKffF6rCDx9YyJr5YNa7w997ht@postini.com; Thu, 01 Dec 2011 23:22:35 PST
Received: from MOPESMAILHC01.eu.thmulti.com (141.11.100.25) by mail3.technicolor.com (141.11.253.22) with Microsoft SMTP Server (TLS) id 8.3.192.1; Fri, 2 Dec 2011 08:19:56 +0100
Received: from MOPESMBX01.eu.thmulti.com ([169.254.155.121]) by MOPESMAILHC01.eu.thmulti.com ([141.11.100.25]) with mapi; Fri, 2 Dec 2011 08:20:04 +0100
From: Wuyts Carl <Carl.Wuyts@technicolor.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Date: Fri, 2 Dec 2011 08:20:03 +0100
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt
Thread-Index: AQHMsBTklUmU2oOu4Uep6NgAq9bX9pXHtNAAgABv16A=
Message-ID: <867F4B6A1672E541A94676D556793ACD0CB42FD801@MOPESMBX01.eu.thmulti.com>
References: <20111130161440.17091.31129.idtracker@ietfa.amsl.com><CAL10_BrtWTQ8aXYYd-FX09gDLAowWfRzEf5PrGu9hoff6Ki1-A@mail.gmail.com>, <0DAAE1C6-6E44-4939-962A-E4AD9E611380@nominum.com> <20111201143915185454109@foxmail.com> <867F4B6A1672E541A94676D556793ACD0CB42FD544@MOPESMBX01.eu.thmulti.com> <5C9A4996-07B2-479C-8A19-40CF69F8932B@nominum.com>
In-Reply-To: <5C9A4996-07B2-479C-8A19-40CF69F8932B@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/related; boundary="_006_867F4B6A1672E541A94676D556793ACD0CB42FD801MOPESMBX01eut_"; type="multipart/alternative"
MIME-Version: 1.0
Cc: Andre Kostur <akostur@incognito.com>, dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt
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: Fri, 02 Dec 2011 07:22:39 -0000

--_006_867F4B6A1672E541A94676D556793ACD0CB42FD801MOPESMBX01eut_
Content-Type: multipart/alternative;
	boundary="_000_867F4B6A1672E541A94676D556793ACD0CB42FD801MOPESMBX01eut_"

--_000_867F4B6A1672E541A94676D556793ACD0CB42FD801MOPESMBX01eut_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Ted, I read "we are not qualified to make architectural decisions about IPv=
6 transition technologies that don't directly involve DHCP".  Good, however=
, the RFC6204 initially was putting a req in place to state that the CPE MU=
ST wait for the RA prior of starting its DHCPv6 client.  This is linked to =
DHCP I'd say, no ?  I see too many times that links are being made between =
protocols or check for address or ....  It is OK to say that one should wai=
t for it, so to leave it open as implementation choice or configuration pos=
sibility for the vendor.

Carl Wuyts
GCD System Architect Networking
Connect Division

carl.wuyts@technicolor.com<mailto:carl.wuyts@technicolor.com>
tel.: +32 3 443 65 90
[cid:image001.gif@01CCB0CB.30F87260]<http://twitter.com/#!/TechnicolorIPv6>
[cid:image002.gif@01CCB0CB.30F87260]<http://www.technicolor.com/>
Prins Boudewijnlaan 47  -  2650 Edegem  -  Belgium

Technicolor Delivery Technologies Belgium NV
Registered office (maatschappelijke zetel): Prins Boudewijnlaan 47, 2650 Ed=
egem, Belgium
Company registration number (ondernemingsnummer): 0428837295 - RPR Antwerpe=
n
[cid:image003.gif@01CCB0CB.30F87260]

Help preserve the color of our world - Think before you print.





From: Ted Lemon [mailto:Ted.Lemon@nominum.com]
Sent: donderdag 1 december 2011 17:37
To: Wuyts Carl
Cc: peng-wu; Andre Kostur; dhc WG
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt

On Dec 1, 2011, at 5:30 AM, Wuyts Carl wrote:
I'd say it's getting a bit tricky now.  The DHCPv4 over IPv6 draft and the =
RFC6204bis are sharing some "components", e.g. the DSLite DHCPv6 option (RF=
C6334).  Although the requirement of RFC6204bis has been re-phrased to shou=
ld it literally says that "the CPE SHOULD disable the DSLite tunnel in case=
 of public IPv4 presence on the link", while this draft is adding an IPv4 p=
ublic address to the tunnel interface.  Both DSLite and 4over6 are in fact =
similar interface/tunnel types, so might all become a bit confusing, no ??

Carl, as a group, we are not qualified to make architectural decisions abou=
t IPv6 transition technologies that don't directly involve DHCP.   We adopt=
ed this work because we were asked to do so as part of an effort from the s=
oftwires working group.   If you think this is a bad architecture, please r=
aise that discussion there.   I get the impression that it's been discussed=
 to death, though.


--_000_867F4B6A1672E541A94676D556793ACD0CB42FD801MOPESMBX01eut_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#def=
ault#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Trebuchet MS";
	panose-1:2 11 6 3 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Ted, I re=
ad &#8220;</span><span style=3D'font-size:11.0pt;font-family:"Calibri","san=
s-serif"'>we are not qualified to make architectural decisions about IPv6 t=
ransition technologies that don't directly involve DHCP&#8221;.&nbsp; Good,=
 however, the RFC6204 initially was putting a req in place to state that th=
e CPE MUST wait for the RA prior of starting its DHCPv6 client.&nbsp; This =
is linked to DHCP I&#8217;d say, no ?&nbsp; I see too many times that links=
 are being made between protocols or check for address or &#8230;.&nbsp; It=
 is OK to say that one should wait for it, so to leave it open as implement=
ation choice or configuration possibility for the vendor.</span><span style=
=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p=
></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font=
-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><=
div><table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D=
0><tr><td valign=3Dtop style=3D'padding:1.5pt 0cm 1.5pt 0cm'><table class=
=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0><tr><td valign=
=3Dtop style=3D'border:none;border-top:solid #9D9FA2 1.0pt;padding:1.5pt 0c=
m 1.5pt 0cm'><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-f=
amily:"Trebuchet MS","sans-serif";color:#1F497D'>Carl Wuyts<o:p></o:p></spa=
n></b></p><p class=3DMsoNormal><span style=3D'font-size:9.0pt;font-family:"=
Trebuchet MS","sans-serif";color:#1F497D'>GCD System Architect Networking<o=
:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fo=
nt-family:"Trebuchet MS","sans-serif";color:#1F497D;text-transform:uppercas=
e'>Connect Division</span><span style=3D'font-size:10.0pt;font-family:"Treb=
uchet MS","sans-serif";color:#1F497D'><o:p></o:p></span></p></td></tr><tr><=
td valign=3Dtop style=3D'padding:1.5pt 0cm 1.5pt 0cm'><p class=3DMsoNormal>=
<span style=3D'font-size:9.0pt;font-family:"Trebuchet MS","sans-serif";colo=
r:#1F497D'><a href=3D"mailto:carl.wuyts@technicolor.com"><span style=3D'col=
or:#662D91'>carl.wuyts@technicolor.com</span></a></span><span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p><=
/span></p><p class=3DMsoNormal><span style=3D'font-size:9.0pt;font-family:"=
Trebuchet MS","sans-serif";color:#1F497D'>tel.: +32 3 443 65 90<o:p></o:p><=
/span></p><p class=3DMsoNormal><a href=3D"http://twitter.com/#!/Technicolor=
IPv6"><span style=3D'font-size:9.0pt;font-family:"Trebuchet MS","sans-serif=
";color:blue;text-decoration:none'><img border=3D0 width=3D24 height=3D24 i=
d=3D"Picture_x0020_1" src=3D"cid:image001.gif@01CCB0CB.30F87260" alt=3Dtwit=
ter></span></a><span style=3D'font-size:9.0pt;font-family:"Trebuchet MS","s=
ans-serif";color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal><a hre=
f=3D"http://www.technicolor.com/" target=3D"_blank"><span style=3D'font-siz=
e:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#6A9D17;text-decorat=
ion:none'><img border=3D0 width=3D114 height=3D69 id=3D"Picture_x0020_2" sr=
c=3D"cid:image002.gif@01CCB0CB.30F87260" alt=3D"Visit technicolor.com"></sp=
an></a><span style=3D'font-size:10.0pt;font-family:"Trebuchet MS","sans-ser=
if";color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:9.0pt;font-family:"Trebuchet MS","sans-serif";color:#1F497D'>=
Prins Boudewijnlaan 47&nbsp;&nbsp;-&nbsp;&nbsp;2650 Edegem&nbsp;&nbsp;-&nbs=
p;&nbsp;Belgium<o:p></o:p></span></p></td></tr><tr><td valign=3Dtop style=
=3D'border:none;border-top:solid #9D9FA2 1.0pt;padding:1.5pt 0cm 1.5pt 0cm'=
><p class=3DMsoNormal><b><span lang=3DNL-BE style=3D'font-size:7.0pt;font-f=
amily:"Arial","sans-serif";color:#9D9FA2'>Technicolor Delivery Technologies=
 Belgium NV</span></b><b><span lang=3DNL-BE style=3D'font-size:7.0pt;font-f=
amily:"Arial","sans-serif";color:#9D9FA2'><o:p></o:p></span></b></p><p clas=
s=3DMsoNormal><b><span lang=3DNL-BE style=3D'font-size:7.0pt;font-family:"A=
rial","sans-serif";color:#9D9FA2'>Registered office (maatschappelijke zetel=
): Prins Boudewijnlaan 47, 2650 Edegem, Belgium<o:p></o:p></span></b></p><p=
 class=3DMsoNormal><b><span style=3D'font-size:7.0pt;font-family:"Arial","s=
ans-serif";color:#9D9FA2'>Company registration number (ondernemingsnummer):=
 0428837295 - RPR Antwerpen<o:p></o:p></span></b></p><table class=3DMsoNorm=
alTable border=3D0 cellspacing=3D0 cellpadding=3D0><tr><td valign=3Dtop sty=
le=3D'padding:1.5pt 0cm 1.5pt 0cm'><p class=3DMsoNormal><span style=3D'font=
-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#1F497D'><img bo=
rder=3D0 width=3D28 height=3D33 id=3D"Picture_x0020_3" src=3D"cid:image003.=
gif@01CCB0CB.30F87260" alt=3DEco><o:p></o:p></span></p></td><td style=3D'pa=
dding:1.5pt 0cm 1.5pt 4.5pt'><p class=3DMsoNormal><i><span style=3D'font-si=
ze:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#9D9FA2'>Help prese=
rve the color of our world - Think before you print.<o:p></o:p></span></i><=
/p></td></tr></table></td></tr></table></td></tr></table><p class=3DMsoNorm=
al><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color=
:#1F497D'><o:p>&nbsp;</o:p></span></p></div><p class=3DMsoNormal><span styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:=
p>&nbsp;</o:p></span></p><div><div style=3D'border:none;border-top:solid #B=
5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span style=
=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><sp=
an style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Ted Lemon =
[mailto:Ted.Lemon@nominum.com] <br><b>Sent:</b> donderdag 1 december 2011 1=
7:37<br><b>To:</b> Wuyts Carl<br><b>Cc:</b> peng-wu; Andre Kostur; dhc WG<b=
r><b>Subject:</b> Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-0=
0.txt<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:=
p></p><div><div><p class=3DMsoNormal>On Dec 1, 2011, at 5:30 AM, Wuyts Carl=
 wrote:<o:p></o:p></p></div><blockquote style=3D'margin-top:5.0pt;margin-bo=
ttom:5.0pt'><p class=3DMsoNormal><span class=3Dapple-style-span><span style=
=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'>I'd say it's get=
ting a bit tricky now. &nbsp;The DHCPv4 over IPv6 draft and the RFC6204bis =
are sharing some &quot;components&quot;, e.g. the DSLite DHCPv6 option (RFC=
6334). &nbsp;Although the requirement of RFC6204bis has been re-phrased to =
should it literally says that &quot;the CPE SHOULD disable the DSLite tunne=
l in case of public IPv4 presence on the link&quot;, while this draft is ad=
ding an IPv4 public address to the tunnel interface. &nbsp;Both DSLite and =
4over6 are in fact similar interface/tunnel types, so might all become a bi=
t confusing, no ??</span></span><o:p></o:p></p></blockquote></div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>Carl, as a grou=
p, we are not qualified to make architectural decisions about IPv6 transiti=
on technologies that don't directly involve DHCP. &nbsp; We adopted this wo=
rk because we were asked to do so as part of an effort from the softwires w=
orking group. &nbsp; If you think this is a bad architecture, please raise =
that discussion there. &nbsp; I get the impression that it's been discussed=
 to death, though.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp=
;</o:p></p></div></div></body></html>=

--_000_867F4B6A1672E541A94676D556793ACD0CB42FD801MOPESMBX01eut_--

--_006_867F4B6A1672E541A94676D556793ACD0CB42FD801MOPESMBX01eut_
Content-Type: image/gif; name="image001.gif"
Content-Description: image001.gif
Content-Disposition: inline; filename="image001.gif"; size=1351;
	creation-date="Fri, 02 Dec 2011 07:20:03 GMT";
	modification-date="Fri, 02 Dec 2011 07:20:03 GMT"
Content-ID: <image001.gif@01CCB0CB.30F87260>
Content-Transfer-Encoding: base64

R0lGODlhGAAYAPcAAAAAAP///1Sfum/L64bW8o7h/ofU74fT7pHb9pfa8u75/VbD5VzG6FvF5l3G
513F5l/G51/F5mHH52PH6GPI6GPI52TH6GXJ6GbI6GnK6mjJ6WjK6WzL6m/M63HN6nPN6nTN63fR
7XnR7XTI5FeVqnnN537T7n7R7H/T7X3O6Y3f+4jV73m903/E2oDE2pTf+ZPc9JTa8Zfa8aDd8LDj
9MXr9+z5/er3+/r9/imy1yyx1S202S2z1zK43TW63jW32zS22Ta53Te73za32zq84Dm53Du73j2/
4j2+4T283z273kHB5D++4EHA4kG/4UPA40K/4UTB5EbD5UbB40rJ7EjD5ErG6EnE5knE5Ua720rE
5kvG507J607I6U3G50/K60u+3U2/4U7A4k2/3lLI6E/A31XN7lHC4VnP8FfL61PD4lXD5FXF41vR
8VfG5VO92lrJ51a+21i/21/O7F7L6VnB3VzE4mHN6l/H5V3D30+lvWDH41/E4GDF4WLH42rL6GvP
6l+2znLZ9W7Q62C1zGO50HXZ9HTY83ba9XXX8mW70nLO6nHN6We803rd+HXV73zf+mm91HXS62vA
12GpvWavw2ixxVmWp2qxxYDW7X3Q52yzxm+2yW60x4HS6HC2yXG3ynzD2I7a75Xb7pvh9F+HkqTg
8ajg76ff7qri8bPo97fm9Ljm9MXw/Mfw/NDz/dDx+tbx+dz0++H1++f5/uv5/Six1S+22jG01zK1
2EXD5E/M7U7H50yvyWPY91zJ5WjZ92za927b+HHY82G4z3Xd+FurwHXa9Xfc93ne+F+rv37h+2u/
1YDi/H7c9YHh+YLh+YXi+mqyxWuzxork+ovj+o3l+3K4ypXn+12PnJrm+qXp+63j8cLx/M/0/ef4
/Jfp+57q+6Xt/Kjv/avv/a3v/a7w/bPw/bzz/uP6/+z7/vP9/7fz/r30/sD0/sX1/sn2/tT4/9L2
/d/6/+X7/+b7/+r8/+v7/sz3/tr5/ub8/+39//v///3///7//////yH5BAEAAP8ALAAAAAAYABgA
AAj/AP8JHEiwoMGCAgggOGCg4YqHEB8aOPCCAEESKmR84MABg0cOHUKGHDCAA4gEBQaOiIHBwgQO
pmrQEEEhg80NGnJewACDhcAUJyBMwBArgL8ACkxc2MBUg8cLEEy0+PkhQoMZAerNmxegBoMLFChc
AFsBQggXAkswerBgVYB8+eLtu7GorgcKDipIcBBi6r8SHtiyCoAPH7x6AXAoxjELRYO9IUIJlGMn
jBi37zLHo2fPXj19/hT8WRMGDzGBb7LosIUqADp07WC7c9eOHbwAmnjwGBNIYBwwuHK0NleOOLnj
5MaxC+BpR64zp//JGQNkx6kA4rKXO8ede7oAe378/1BTSGCdMkNunfIXLhw4eQH6yU88KoiSImzK
/8tzpkiPVP1gg4013gRgYGKmEMEEE0a4oYhAeahhhA/c8FMNNdF0s4466tyzTgCrOAFFEnA0IhAf
bCQhhCkBVPMMNDDC+GI3AUiCBBNwRCJQH24wgUQmAWwjTDJEFllMNAGIcoQTdDAjkB9uODGFFLHw
o00wwGSZpS/bBJDJEk80+eQvTVQhxR2zBECLK6202c0rAchCxhVR3DGJb5I0gYUXVqRBCiy1BFqL
Dd+oMocVW+jyCCEC6ZEIIFps0cUXVOyCRhuYomEGFVx0wcsghlwyUC/DOHPIMcg4AskyzbS6DCSO
ICSDiDOCGFNQNspUYgkmm3TCCSjXgPJJJ9NIYwklpRyk7LIDBQQAOw==

--_006_867F4B6A1672E541A94676D556793ACD0CB42FD801MOPESMBX01eut_
Content-Type: image/gif; name="image002.gif"
Content-Description: image002.gif
Content-Disposition: inline; filename="image002.gif"; size=1834;
	creation-date="Fri, 02 Dec 2011 07:20:03 GMT";
	modification-date="Fri, 02 Dec 2011 07:20:03 GMT"
Content-ID: <image002.gif@01CCB0CB.30F87260>
Content-Transfer-Encoding: base64

R0lGODlhcgBFAOZ/AEGueqipqmgxkACLS4ORyPb294DFpZrMVqvi+sXr2Ie3laLXtnRHnLQlZO3J
2M+pxP7pJvqtgePqmqOIvYLKnACP1fewoXa65/vCov71sdqRnc6OpPvrlcU/benvs7qmzpzR8P/n
rc7imtLntMkhU/V7Hf/yl+fZ6f3HipjL7b+MraKs1h+WXIrU9fNrPv/dkaTIrpQpd/JlIr8kXv/o
ALa3uO0bLwCmUQC68pKSlf/CDgxNosvbKtvb3IzGP8nJyoiJjPaWgH+Ag3Z3euTk5Y3Y+MTfm+3t
7r/AwZubnvBSJQCZ3NLS0//eAwN+yE84la9fmdjkX//RSiPB855BhP/ILiCvY9HeRvLkCvmykSld
q/aNl4Dd+cPT6O85Q2m+Q6zRONnM5OPx0PR3OR2Z2eOttkCr4Lfbm//uQPWMWbeLscPbysbs/OP1
/ZeLwPaLN9blff/iEvXlByCi3nzB69eqvN7r4uzysHfDWSCKzu+Uh8R4pR6j4IVfqm1ucf///yH5
BAEAAH8ALAAAAAByAEUAAAf/gH+Cg4SFhoeIiYqLjI2Oj5CRkpOUlZaXmJmam5ydnp+goaKjpKWm
p6ipqqusra6vsLGys7S1tqF+Oat+freMubu9vorAkkhIlryqBQWXxZBEvD2VyqhEQtPJupJJScnC
pzV+2dTbqdWnSX4BNTWDR+01RIUFSO0/zX/AP+1Mg/x/iLRDku9PO0JH7NXA906hv0Ho/vSId2TQ
xB4Jf1gKwKujoB8deWn8OCTkkIp+gAAJGUBQjnUhgUAEB9Lkx5C58lUr8DLkSHE5Spqb1IMjkh7T
evgZ4o9JyYrR/Mib2FKfHyH4kPBq1rPGkR4lH1ZjsvQH0gDIlA7RSGSlN6uC/zgCmfcjrEFeQuRd
EkeO48g/IN2pQ2boasGV014+/MPRHdw/QsYZUve3wFO4R5YWBOlN3FtMfAetBJKj9EpdEQk9+/My
sWRB4hxXS3koNcdpypRWnXnXMejXf4SWHt4yNcShrVkDjy1o9lDehELnXldIGfNMoV0CJxSZnGrk
kpPDltpc2FZDK+eJlqwsmsx3V3trEvdXK5CKgvKJu59fLHjX5FxXjVz5fHUXEPmAJER5gkQ2UgHq
uHMdJiANkcNIK+WSQ2TraaiZPv8pFyB5jxWwkoUvLWjiVUlkmE01RJQERACRISifJhxR90cBNUTG
YkE1ZAgEYTnsxlgO8wSA5P8/F7pkDo8+AvFgj7wkoR5r5hChzlU1JNjkMGCGKeaYZJZp5pmqsIHA
mmyCkMKbcK4g55wrfGDnnR88oOeedZTh558WBCqoBRgUaigGISSqaAgZNOroHR5EKqkHI1Rq6QKY
ZroADJx2CoMdjxSAQBGkktoCHRekqioBrLZKgBsTxCqrGirUaqsGuOaqgR5B9OprBMAGG8ELxBb7
ggnIJmuCBMw2K4EIRkQb7RkUVGstBQpkq60CazTSRqmlnqrqqq6yCqusstqqrq65+uqusMGiYCyx
HCiLLAfONguttEZQe22122oLQ0GHsAGuqeOSW+656E6grq0bsIuru7/CG4H/vPMea++y+TK7r7T+
/huwtqAiMsXJKE/BBxkst5yHFjDHrAUDNNdMMxU450xFBzz3zLMXQAfthQtjFG30G1UkrXQVEDTt
dNNXRC31FWAcYPXVeFih9dZWsOD11ywAkAgOZJeNwxIVpK22Ezu07fYOTwgg99wCxGD33TE0MMPe
fJNgw9+A26CEDIQXXoIOiCeuQxM0NO44FjxELjkPYPhg+eVf3KD55jcM4PnnA4iNiNllo6122my/
3XbcdMuN9916872334H/PXjhhB+uOOKMO9445JNHXvnllmfOueagfy76IaSTbfrpqavOeuuv2x27
7LTXfjvuuu/eu+/ABz88//HGH5+858sb0vzZp6Ou+uqtu1799X3Xbjvuue/Ou++/By888cU7HvLO
l75CrO95a3sf3OJXt/nJbnb2Exz+ZNA9xX3vcf6jHAB9UD7OnS90Y2seAt33vunRrXp5e+AMshe4
7RlOf4vjHw3CN7nxYU6AnSNgCEk3wgpE720mnBsK6QdB+7kwf/q7YP/8BwcxOPGJC8DhBwtIiAO2
z4cKDKL8XkfEFUbwiBSEoRJpIIcomPGMUbiDIRIgRR2OToRXrEAX5kjHLvSBgUNUIQsBB8YSSOGP
gJRCHGRIA0ewUYBTTAQXFslILswhjoe4Y/zy+EASbOGSmNyCCyYog0OggYeQhgSAKEcJABa40RFm
gKQhThCGVrryAZR84CHSwElPgrISADhlI1J5RUc4IJaym2UtSZHL5FFREbxsny9RuAcHOPOZDjgE
BrJAzWpmoRQLMIA2t7kASCTzdI44ARTGSU4oPABN6EynOtfJzna6853wjKc850nPetrznvjMpz73
yc9++tMUgQAAOw==

--_006_867F4B6A1672E541A94676D556793ACD0CB42FD801MOPESMBX01eut_
Content-Type: image/gif; name="image003.gif"
Content-Description: image003.gif
Content-Disposition: inline; filename="image003.gif"; size=493;
	creation-date="Fri, 02 Dec 2011 07:20:04 GMT";
	modification-date="Fri, 02 Dec 2011 07:20:04 GMT"
Content-ID: <image003.gif@01CCB0CB.30F87260>
Content-Transfer-Encoding: base64

R0lGODlhHAAhAMQAALHNVVqXGZu+IqbFNv79/ury0pK4H2SdaJzAJNjlq/3++vL34srdiSl5Mfj7
8OHrvDmDE5u+Kb3VbtDgm5jCnJC2IqDBJHqqHoazHsfYxcfco+/58f7///7+/v///f///yH5BAAA
AAAALAAAAAAcACEAAAX/4CeOZGmeaKqubOumXSfKL0rT9RiTe65/nl0vxxE1KB3Ph6b8KGYjT/Pn
ORwIHmy0FEQFCZRG5yldJnEqD6ezaWQIHMJDApAwCthgF8hbEqwEBQARAoWFEgskQWgiChwFDRoD
hpQCA3hLQGhxSWABFpQIlAMPT2NoeTIJEBigooavlzJDS0UdHAkBEAivAoSjDklTQAROuBYQn7+/
lBJJS01SUgoJoskWvaECCWUiHEEKtw+8BtegvoWxiYtqSmsLhBblEALn2hLDH3HTAIXYuhfqVeLF
TZ8SR3oSULKAQVeAChYi8kJwCUg4BcVkOOiXDgHDACAvXMBQoWQEOw6iahwsMCmdAI8CKoiciUEA
gAJ8aBC4xfKlz3QRsVGcoICMJidKOjhgMKCXqKcAJqSMIkwEuw8OHjCQwNVOggJPvqm4ZUJGuw47
lajlA0Sat28xyJZV9APasGEcvknBkU9TjJ1WrTZZE9hHihAAOw==

--_006_867F4B6A1672E541A94676D556793ACD0CB42FD801MOPESMBX01eut_--

From Ted.Lemon@nominum.com  Fri Dec  2 09:38:17 2011
Return-Path: <Ted.Lemon@nominum.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 074FC21F87D6 for <dhcwg@ietfa.amsl.com>; Fri,  2 Dec 2011 09:38:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.488
X-Spam-Level: 
X-Spam-Status: No, score=-106.488 tagged_above=-999 required=5 tests=[AWL=0.110, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mR1CYlPxAiJB for <dhcwg@ietfa.amsl.com>; Fri,  2 Dec 2011 09:38:16 -0800 (PST)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id 3ECA821F86AA for <dhcwg@ietf.org>; Fri,  2 Dec 2011 09:38:16 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKTtkNByg7zEpS62Gp9qeENQS7BHO713al@postini.com; Fri, 02 Dec 2011 09:38:16 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D35F31B82B3 for <dhcwg@ietf.org>; Fri,  2 Dec 2011 09:38:14 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id BBF21190052; Fri,  2 Dec 2011 09:38:13 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0339.001; Fri, 2 Dec 2011 09:38:13 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Wuyts Carl <Carl.Wuyts@technicolor.com>
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt
Thread-Index: AQHMsBTklUmU2oOu4Uep6NgAq9bX9pXHtNAAgABv16CAATOfAA==
Date: Fri, 2 Dec 2011 17:38:12 +0000
Message-ID: <9025F22B-5730-4CA7-A8B4-2892A76D22D8@nominum.com>
References: <20111130161440.17091.31129.idtracker@ietfa.amsl.com><CAL10_BrtWTQ8aXYYd-FX09gDLAowWfRzEf5PrGu9hoff6Ki1-A@mail.gmail.com>, <0DAAE1C6-6E44-4939-962A-E4AD9E611380@nominum.com> <20111201143915185454109@foxmail.com> <867F4B6A1672E541A94676D556793ACD0CB42FD544@MOPESMBX01.eu.thmulti.com> <5C9A4996-07B2-479C-8A19-40CF69F8932B@nominum.com> <867F4B6A1672E541A94676D556793ACD0CB42FD801@MOPESMBX01.eu.thmulti.com>
In-Reply-To: <867F4B6A1672E541A94676D556793ACD0CB42FD801@MOPESMBX01.eu.thmulti.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_9025F22B57304CA7A8B42892A76D22D8nominumcom_"
MIME-Version: 1.0
Cc: Andre Kostur <akostur@incognito.com>, dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt
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: Fri, 02 Dec 2011 17:38:17 -0000

--_000_9025F22B57304CA7A8B42892A76D22D8nominumcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

On Dec 2, 2011, at 2:20 AM, Wuyts Carl wrote:
Ted, I read =93we are not qualified to make architectural decisions about I=
Pv6 transition technologies that don't directly involve DHCP=94.  Good, how=
ever, the RFC6204 initially was putting a req in place to state that the CP=
E MUST wait for the RA prior of starting its DHCPv6 client.  This is linked=
 to DHCP I=92d say, no ?  I see too many times that links are being made be=
tween protocols or check for address or =85.  It is OK to say that one shou=
ld wait for it, so to leave it open as implementation choice or configurati=
on possibility for the vendor.

What does this have to do with DHCPv4 over IPv6?   RFC6204 is not a DHC wor=
king group document.   I'm going to give you my best answer to this questio=
n under a separate subject line.


--_000_9025F22B57304CA7A8B42892A76D22D8nominumcom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <4898ABCAC0E1314CB6DDF3E23EF5D36F@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 2, 2011, at 2:20 AM, Wuyts Carl wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; "><span class=3D"Apple-style-span" style=
=3D"font-family: 'Times New Roman', serif; font-size: 16px; "><span style=
=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 1=
25); ">Ted,
 I read =93</span><span style=3D"font-size: 11pt; font-family: Calibri, san=
s-serif; ">we are not qualified to make architectural decisions about IPv6 =
transition technologies that don't directly involve DHCP=94.&nbsp; Good, ho=
wever, the RFC6204 initially was putting a
 req in place to state that the CPE MUST wait for the RA prior of starting =
its DHCPv6 client.&nbsp; This is linked to DHCP I=92d say, no ?&nbsp; I see=
 too many times that links are being made between protocols or check for ad=
dress or =85.&nbsp; It is OK to say that one should
 wait for it, so to leave it open as implementation choice or configuration=
 possibility for the vendor.</span></span></span></blockquote>
</div>
<br>
<div>What does this have to do with DHCPv4 over IPv6? &nbsp; RFC6204 is not=
 a DHC working group document. &nbsp; I'm going to give you my best answer =
to this question under a separate subject line.</div>
<div><br>
</div>
</body>
</html>

--_000_9025F22B57304CA7A8B42892A76D22D8nominumcom_--

From Ted.Lemon@nominum.com  Fri Dec  2 09:41:24 2011
Return-Path: <Ted.Lemon@nominum.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 6B2EF11E80C5 for <dhcwg@ietfa.amsl.com>; Fri,  2 Dec 2011 09:41:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.498
X-Spam-Level: 
X-Spam-Status: No, score=-106.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W3EqP0GAMh1s for <dhcwg@ietfa.amsl.com>; Fri,  2 Dec 2011 09:41:23 -0800 (PST)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 6372F11E80B4 for <dhcwg@ietf.org>; Fri,  2 Dec 2011 09:41:23 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKTtkNwooww5ah3vG+4ygdckQx1VAphVsL@postini.com; Fri, 02 Dec 2011 09:41:23 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 698721B8299 for <dhcwg@ietf.org>; Fri,  2 Dec 2011 09:41:22 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 630CE190052; Fri,  2 Dec 2011 09:41:22 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0339.001; Fri, 2 Dec 2011 09:41:22 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: dhc WG <dhcwg@ietf.org>
Thread-Topic: To wait for RA or not to wait?
Thread-Index: AQHMsRmaAFDsJ61sskWNi8UGYH6hlQ==
Date: Fri, 2 Dec 2011 17:41:21 +0000
Message-ID: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <5D83731FD9B57C4482F7B0533100E4C5@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [dhcwg] To wait for RA or not to wait?
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: Fri, 02 Dec 2011 17:41:24 -0000

> Ted, I read =93we are not qualified to make architectural decisions about=
 IPv6 transition technologies that don't directly involve DHCP=94.  Good, h=
owever, the RFC6204 initially was putting a req in place to state that the =
CPE MUST wait for the RA prior of starting its DHCPv6 client.  This is link=
ed to DHCP I=92d say, no ?  I see too many times that links are being made =
between protocols or check for address or =85.  It is OK to say that one sh=
ould wait for it, so to leave it open as implementation choice or configura=
tion possibility for the vendor.

If I had it to do over again, I'd do RA and DHCP a lot differently, but at =
this point I think in general we should assume that we will always have RAs=
, and DHCP clients should wait for them.   DHCP doesn't really work without=
 the RA=97even if you get an address, you have no default route.


From Carl.Wuyts@technicolor.com  Fri Dec  2 10:52:34 2011
Return-Path: <Carl.Wuyts@technicolor.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 E7A3111E80FC for <dhcwg@ietfa.amsl.com>; Fri,  2 Dec 2011 10:52:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.221
X-Spam-Level: 
X-Spam-Status: No, score=-6.221 tagged_above=-999 required=5 tests=[AWL=0.378,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B5fZJh1KmYAz for <dhcwg@ietfa.amsl.com>; Fri,  2 Dec 2011 10:52:34 -0800 (PST)
Received: from na3sys009aog120.obsmtp.com (na3sys009aog120.obsmtp.com [74.125.149.140]) by ietfa.amsl.com (Postfix) with ESMTP id C318C11E80FA for <dhcwg@ietf.org>; Fri,  2 Dec 2011 10:52:32 -0800 (PST)
Received: from MOPESEDGE01.eu.thmulti.com ([129.35.174.203]) (using TLSv1) by na3sys009aob120.postini.com ([74.125.148.12]) with SMTP ID DSNKTtkeYN+B6MdBmN2tyztdNeGjY/ThzVla@postini.com; Fri, 02 Dec 2011 10:52:33 PST
Received: from MOPESMAILHC03.eu.thmulti.com (141.11.100.132) by mail3.technicolor.com (141.11.253.22) with Microsoft SMTP Server (TLS) id 8.3.192.1; Fri, 2 Dec 2011 19:47:42 +0100
Received: from MOPESMBX01.eu.thmulti.com ([141.11.100.105]) by MOPESMAILHC03.eu.thmulti.com ([141.11.100.132]) with mapi; Fri, 2 Dec 2011 19:47:50 +0100
From: Wuyts Carl <Carl.Wuyts@technicolor.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, dhc WG <dhcwg@ietf.org>
Date: Fri, 2 Dec 2011 19:47:47 +0100
Thread-Topic: To wait for RA or not to wait?
Thread-Index: AQHMsRmaAFDsJ61sskWNi8UGYH6hlZXI4trA
Message-ID: <867F4B6A1672E541A94676D556793ACD0CB42FDABE@MOPESMBX01.eu.thmulti.com>
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com>
In-Reply-To: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Fri, 02 Dec 2011 18:52:35 -0000

Well, you should wait, maybe, but you must wait: for sure no MUST!
You can perfectly add a default route statically in case you want to.  Diff=
erent customers have different ideas about it, some prefer no RAs, so one h=
as to be able to cope with it.  Moreover, there's no reason to "couple" RA =
to DHCP, they are independent protocols, so should be able to work independ=
ent.  It's fine to wait for it if you prefer, but one has to have the optio=
n to not do this.

Carl Wuyts
GCD System Architect Networking
CONNECT DIVISION
carl.wuyts@technicolor.com
tel.: +32 3 443 65 90


Prins Boudewijnlaan 47=A0=A0-=A0=A02650 Edegem=A0=A0-=A0=A0Belgium
Technicolor Delivery Technologies Belgium NV
Registered office (maatschappelijke zetel): Prins Boudewijnlaan 47, 2650 Ed=
egem, Belgium
Company registration number (ondernemingsnummer): 0428837295 - RPR Antwerpe=
n

Help preserve the color of our world - Think before you print.




-----Original Message-----
From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
Sent: vrijdag 2 december 2011 18:41
To: dhc WG
Cc: Wuyts Carl
Subject: To wait for RA or not to wait?

> Ted, I read "we are not qualified to make architectural decisions about I=
Pv6 transition technologies that don't directly involve DHCP".  Good, howev=
er, the RFC6204 initially was putting a req in place to state that the CPE =
MUST wait for the RA prior of starting its DHCPv6 client.  This is linked t=
o DHCP I'd say, no ?  I see too many times that links are being made betwee=
n protocols or check for address or ..  It is OK to say that one should wai=
t for it, so to leave it open as implementation choice or configuration pos=
sibility for the vendor.

If I had it to do over again, I'd do RA and DHCP a lot differently, but at =
this point I think in general we should assume that we will always have RAs=
, and DHCP clients should wait for them.   DHCP doesn't really work without=
 the RA-even if you get an address, you have no default route.


From Ted.Lemon@nominum.com  Fri Dec  2 11:35:54 2011
Return-Path: <Ted.Lemon@nominum.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 269E511E80AA for <dhcwg@ietfa.amsl.com>; Fri,  2 Dec 2011 11:35:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.505
X-Spam-Level: 
X-Spam-Status: No, score=-106.505 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KdMkDzU5UkRU for <dhcwg@ietfa.amsl.com>; Fri,  2 Dec 2011 11:35:53 -0800 (PST)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by ietfa.amsl.com (Postfix) with ESMTP id 4EFBD11E80A3 for <dhcwg@ietf.org>; Fri,  2 Dec 2011 11:35:53 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKTtkok0hGCT1noQEQZwi8TuTVn+DTcEW6@postini.com; Fri, 02 Dec 2011 11:35:53 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 0D94B1B8291 for <dhcwg@ietf.org>; Fri,  2 Dec 2011 11:35:47 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 01E4C190052; Fri,  2 Dec 2011 11:35:47 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.01.0339.001; Fri, 2 Dec 2011 11:35:46 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Wuyts Carl <Carl.Wuyts@technicolor.com>
Thread-Topic: To wait for RA or not to wait?
Thread-Index: AQHMsRmaAFDsJ61sskWNi8UGYH6hlZXI4trAgACUOoA=
Date: Fri, 2 Dec 2011 19:35:45 +0000
Message-ID: <BEA0EE13-9223-4D60-837C-AEAF74FAFD6E@nominum.com>
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com> <867F4B6A1672E541A94676D556793ACD0CB42FDABE@MOPESMBX01.eu.thmulti.com>
In-Reply-To: <867F4B6A1672E541A94676D556793ACD0CB42FDABE@MOPESMBX01.eu.thmulti.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_BEA0EE1392234D60837CAEAF74FAFD6Enominumcom_"
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Fri, 02 Dec 2011 19:35:54 -0000

--_000_BEA0EE1392234D60837CAEAF74FAFD6Enominumcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

On Dec 2, 2011, at 1:47 PM, Wuyts Carl wrote:
You can perfectly add a default route statically in case you want to.  Diff=
erent customers have different ideas about it, some prefer no RAs, so one h=
as to be able to cope with it.

This is equivalent to saying that different customers have different ideas =
about whether they want their network to work.   No they can't add a defaul=
t route statically=97that's absurd.   If they were going to statically conf=
igure the host, why bother with DHCP at all?

Moreover, there's no reason to "couple" RA to DHCP, they are independent pr=
otocols, so should be able to work independent.  It's fine to wait for it i=
f you prefer, but one has to have the option to not do this.

They are coupled.   They do not work independently.   Whether that was the =
right architecture choice or not, the issue has been decided.


--_000_BEA0EE1392234D60837CAEAF74FAFD6Enominumcom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <1C1A7E63CE9D9D4F94B5EBD3F36D97A4@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 2, 2011, at 1:47 PM, Wuyts Carl wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">You
 can perfectly add a default route statically in case you want to. &nbsp;Di=
fferent customers have different ideas about it, some prefer no RAs, so one=
 has to be able to cope with it.</span></blockquote>
<div><br>
</div>
<div>This is equivalent to saying that different customers have different i=
deas about whether they want their network to work. &nbsp; No they can't ad=
d a default route statically=97that's absurd. &nbsp; If they were going to =
statically configure the host, why bother with
 DHCP at all?</div>
<div><br>
</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">Moreover,
 there's no reason to &quot;couple&quot; RA to DHCP, they are independent p=
rotocols, so should be able to work independent. &nbsp;It's fine to wait fo=
r it if you prefer, but one has to have the option to not do this.<br>
</span></blockquote>
</div>
<br>
<div>They are coupled. &nbsp; They do not work independently. &nbsp; Whethe=
r that was the right architecture choice or not, the issue has been decided=
.</div>
<div><br>
</div>
</body>
</html>

--_000_BEA0EE1392234D60837CAEAF74FAFD6Enominumcom_--

From ichiroumakino@gmail.com  Fri Dec  2 13:38:06 2011
Return-Path: <ichiroumakino@gmail.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 C3EEF1F0C61 for <dhcwg@ietfa.amsl.com>; Fri,  2 Dec 2011 13:38:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.469
X-Spam-Level: 
X-Spam-Status: No, score=-3.469 tagged_above=-999 required=5 tests=[AWL=0.130,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L9KaUF2HTdym for <dhcwg@ietfa.amsl.com>; Fri,  2 Dec 2011 13:38:06 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0C06D1F0C4F for <dhcwg@ietf.org>; Fri,  2 Dec 2011 13:38:05 -0800 (PST)
Received: by wgbdr13 with SMTP id dr13so1454329wgb.13 for <dhcwg@ietf.org>; Fri, 02 Dec 2011 13:38:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=yAGfIV3H1bCJUKcWm3tJk24f6CCpIDPK/cqUvPtupQo=; b=ULQvkstCK6nD1Uf5/N/sNLBmtuol+MRmphls4So+7tzbC/gVA10Jarjb72bs4NtzzU UUJgueVPYrDfIe0rhhyOoD5EZxp0SZD4+xTH8EoM0TvqKcISXDvZbfAhVPk0tbzCydNX TyuV2sbkkh1u3UJ5Lah0nX4YmIad/F6RzKcxQ=
Received: by 10.227.208.81 with SMTP id gb17mr7394388wbb.26.1322861885216; Fri, 02 Dec 2011 13:38:05 -0800 (PST)
Received: from dhcp-10-55-81-140.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id ca18sm4044872wib.13.2011.12.02.13.38.03 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 02 Dec 2011 13:38:04 -0800 (PST)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: Ole Troan <otroan@employees.org>
In-Reply-To: <BEA0EE13-9223-4D60-837C-AEAF74FAFD6E@nominum.com>
Date: Fri, 2 Dec 2011 22:38:02 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2F5A4C2C-B219-47E6-B3C4-43CA8EE3B420@employees.org>
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com> <867F4B6A1672E541A94676D556793ACD0CB42FDABE@MOPESMBX01.eu.thmulti.com> <BEA0EE13-9223-4D60-837C-AEAF74FAFD6E@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1084)
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Fri, 02 Dec 2011 21:38:06 -0000

Ted,

>> You can perfectly add a default route statically in case you want to. =
 Different customers have different ideas about it, some prefer no RAs, =
so one has to be able to cope with it.
>=20
> This is equivalent to saying that different customers have different =
ideas about whether they want their network to work.   No they can't add =
a default route statically=97that's absurd.   If they were going to =
statically configure the host, why bother with DHCP at all?
>=20
>> Moreover, there's no reason to "couple" RA to DHCP, they are =
independent protocols, so should be able to work independent.  It's fine =
to wait for it if you prefer, but one has to have the option to not do =
this.
>=20
> They are coupled.   They do not work independently.   Whether that was =
the right architecture choice or not, the issue has been decided.

that's not the case for DHCP PD. when DHCP is used to configure routers.

cheers,
Ole=

From Ted.Lemon@nominum.com  Fri Dec  2 18:46:33 2011
Return-Path: <Ted.Lemon@nominum.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 BDD0C1F0C49 for <dhcwg@ietfa.amsl.com>; Fri,  2 Dec 2011 18:46:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.512
X-Spam-Level: 
X-Spam-Status: No, score=-106.512 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jglRwtfXvjt1 for <dhcwg@ietfa.amsl.com>; Fri,  2 Dec 2011 18:46:33 -0800 (PST)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 163CF1F0C45 for <dhcwg@ietf.org>; Fri,  2 Dec 2011 18:46:32 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKTtmNiLOX2laXJp7aruq/yVvmJ0OF8q/X@postini.com; Fri, 02 Dec 2011 18:46:33 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id AFA021B8299 for <dhcwg@ietf.org>; Fri,  2 Dec 2011 18:46:31 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 4EFC8190052; Fri,  2 Dec 2011 18:46:30 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.01.0339.001; Fri, 2 Dec 2011 18:46:30 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ole Troan <otroan@employees.org>
Thread-Topic: [dhcwg] To wait for RA or not to wait?
Thread-Index: AQHMsRmaAFDsJ61sskWNi8UGYH6hlZXI4trAgACUOoCAACIqAP//0BMo
Date: Sat, 3 Dec 2011 02:46:29 +0000
Message-ID: <933A3C48-3B77-4E0D-A301-67736999E14A@nominum.com>
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com> <867F4B6A1672E541A94676D556793ACD0CB42FDABE@MOPESMBX01.eu.thmulti.com> <BEA0EE13-9223-4D60-837C-AEAF74FAFD6E@nominum.com>, <2F5A4C2C-B219-47E6-B3C4-43CA8EE3B420@employees.org>
In-Reply-To: <2F5A4C2C-B219-47E6-B3C4-43CA8EE3B420@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Sat, 03 Dec 2011 02:46:33 -0000

On Dec 2, 2011, at 4:38 PM, "Ole Troan" <otroan@employees.org> wrote:
> that's not the case for DHCP PD. when DHCP is used to configure routers.

It seems to me based on the conversations we've been having in other workin=
g groups that how DHCP with PD works is far from settled.


From Ted.Lemon@nominum.com  Fri Dec  2 19:18:56 2011
Return-Path: <Ted.Lemon@nominum.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 BDBEC1F0C50 for <dhcwg@ietfa.amsl.com>; Fri,  2 Dec 2011 19:18:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.218
X-Spam-Level: 
X-Spam-Status: No, score=-106.218 tagged_above=-999 required=5 tests=[AWL=-0.219, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7QnvBqjigkWT for <dhcwg@ietfa.amsl.com>; Fri,  2 Dec 2011 19:18:56 -0800 (PST)
Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by ietfa.amsl.com (Postfix) with ESMTP id EA8671F0C45 for <dhcwg@ietf.org>; Fri,  2 Dec 2011 19:18:55 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob121.postini.com ([64.18.6.12]) with SMTP ID DSNKTtmVH4G8t7ZOYk6yB/7S3XsN9EnLII9Z@postini.com; Fri, 02 Dec 2011 19:18:56 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id AC0351B8297 for <dhcwg@ietf.org>; Fri,  2 Dec 2011 19:18:54 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 1FECC190052 for <dhcwg@ietf.org>; Fri,  2 Dec 2011 19:18:52 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.01.0339.001; Fri, 2 Dec 2011 19:18:52 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: dhc WG <dhcwg@ietf.org>
Thread-Topic: Some high-priority errata for RFC3315/3396...
Thread-Index: AcyxakejwUXOElp7STCtYjgcemUphw==
Date: Sat, 3 Dec 2011 03:18:51 +0000
Message-ID: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C41300143F50A248B1F8AB26A0AD57D3@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Sat, 03 Dec 2011 03:18:56 -0000

There's been a bit of a discussion going on in the v6ops working group abou=
t a problem in the DHCP protocol that has to do with the coexistence of sta=
teful address allocation and prefix delegation.

The problem is that it's entirely possible that a PD requesting router migh=
t also want an IP address to number its upstream interface, so it might sen=
d a DHCP Solicit message containing both an IA_NA and an IA_PD.    Suppose =
the DHCP server is willing to do prefix delegation, but expects the RR to d=
o SLAAC for the upstream address.   In this case, it's going to send an IA_=
PD containing one or more prefixes, but an IA_NA containing no addresses.

RFC3315 wasn't written with RFC3361 in mind, so it doesn't really talk abou=
t what to do in this case.   It also doesn't address the problem of what to=
 do if an IA_TA appears in the solicit, but the server isn't configured to =
offer temporary addresses.   This hasn't been much of an issue since I don'=
t know of any clients that actually request temporary addresses, but of cou=
rse it is an issue for IA_PD.

There exist two errata that address this issue: erratum 2471 and erratum 24=
72.   These errata propose to have the status code appear inside the IA_NA =
option rather than in the outer layer of the Advertise message.   A similar=
 erratum exists for RFC3361, proposing to put the status code option in the=
 IA_PD option instead of, similarly, in the outer layer of the packet.

In addition, the following observation has been made:

  The other unclear problem area is around how to deal with IA_PD and IA_NA=
:
    * Client requests both IA_NA and IA_PD in the same session, gets only I=
A_PD.
      - Does it fork off a separate session for IA_NA and continues sending=
 SOLICITs for only the IA_NA?
      - Reset the DHCP client, and tries again?
      - Keeps single session, and continues to ask for IA_NA on next RENEW?
=20
      all 3 behaviors have been seen in the wild plus some additional patho=
logical cases.
      in general dealing with multiple stateful options in DHCP is underspe=
cified.

So the topic for discussion in the working group here is as follows:

1. Is what is proposed in the errata the right thing?   Should we in fact h=
ave status codes inside of IA_* options instead of in the main packet?

2. If so, what is the full set of edits to RFC3315 and RFC3361 that are req=
uired to do this?
2a. What do we do for clients that don't implement the errata?

3. If not, what should we do instead?

4. If the client gets an IA_NA and no IA_PD, or vice versa, which of the th=
ree behaviors listed above should it follow?   Is it bad that different cli=
ents do this differently?

5. What have I missed?

Comments?   Criticisms?   Rotten tomatoes?

From ichiroumakino@gmail.com  Sat Dec  3 01:53:35 2011
Return-Path: <ichiroumakino@gmail.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 8C86D21F8B22 for <dhcwg@ietfa.amsl.com>; Sat,  3 Dec 2011 01:53:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.476
X-Spam-Level: 
X-Spam-Status: No, score=-3.476 tagged_above=-999 required=5 tests=[AWL=0.123,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ayK4Chpj2jFI for <dhcwg@ietfa.amsl.com>; Sat,  3 Dec 2011 01:53:35 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id B82DD21F8AD6 for <dhcwg@ietf.org>; Sat,  3 Dec 2011 01:53:34 -0800 (PST)
Received: by wgbdr13 with SMTP id dr13so2321948wgb.13 for <dhcwg@ietf.org>; Sat, 03 Dec 2011 01:53:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=gqPHGlPaSosT6hG2Te/ON7ENLWHV7eu+ML7AN+McKCo=; b=oA5dpl2iFpvm/OZlBaMaVWUC+rSCtZft9zaVMgASs3NsMG+QZY8zYCARWm7Vr9InCY tlhC4vPhvR90vJVuGPkDc5ty5sMy8ZcP+h7o9WiPEmwGsdJiH8Po6O8s6cBr+nslRReA sDO59o8DNOAFYghzoyf6skzHAu2oJ7TndTwIw=
Received: by 10.180.105.232 with SMTP id gp8mr2707905wib.65.1322906013839; Sat, 03 Dec 2011 01:53:33 -0800 (PST)
Received: from dhcp-10-55-89-163.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id m30sm15200255wbo.14.2011.12.03.01.53.31 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 03 Dec 2011 01:53:31 -0800 (PST)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <933A3C48-3B77-4E0D-A301-67736999E14A@nominum.com>
Date: Sat, 3 Dec 2011 10:53:31 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <99E92F98-5026-44F3-A8E6-9D65D613B80B@employees.org>
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com> <867F4B6A1672E541A94676D556793ACD0CB42FDABE@MOPESMBX01.eu.thmulti.com> <BEA0EE13-9223-4D60-837C-AEAF74FAFD6E@nominum.com>, <2F5A4C2C-B219-47E6-B3C4-43CA8EE3B420@employees.org> <933A3C48-3B77-4E0D-A301-67736999E14A@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1084)
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Sat, 03 Dec 2011 09:53:35 -0000

Ted,

>> that's not the case for DHCP PD. when DHCP is used to configure =
routers.
>=20
> It seems to me based on the conversations we've been having in other =
working groups that how DHCP with PD works is far from settled.

we have had working interoperable implementations of DHCPv6 PD since =
2003.
the "how PD should work with host configuration protocols" is a recent =
discussion. please don't rewrite history. if people want that changed =
now, fine. but you will find no basis in 3633 for that "unsettledness".

cheers,
Ole


From ichiroumakino@gmail.com  Sat Dec  3 03:30:14 2011
Return-Path: <ichiroumakino@gmail.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 BD42A21F9395 for <dhcwg@ietfa.amsl.com>; Sat,  3 Dec 2011 03:30:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.182
X-Spam-Level: 
X-Spam-Status: No, score=-3.182 tagged_above=-999 required=5 tests=[AWL=-0.183, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 86r391mPPAlN for <dhcwg@ietfa.amsl.com>; Sat,  3 Dec 2011 03:30:14 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id E0EDA21F9396 for <dhcwg@ietf.org>; Sat,  3 Dec 2011 03:30:13 -0800 (PST)
Received: by wgbdr13 with SMTP id dr13so2431869wgb.13 for <dhcwg@ietf.org>; Sat, 03 Dec 2011 03:30:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=MfYvVfG2KBxpVFjDRmaUL1WyYcQ/oxqIknj7HAq37R4=; b=IDhWf/l9QIdI+U+6du2CWQybDJjAWGPyQhT4OoVcZcJlJSTf+8XBfplyiVRKxeWS2k psETYxLM0/1a1iKzOss5pAWNFIeSJcIJTV9FHWrwapXsojOTTy0Bhr/bLp4s/GJ4bhXw c86wc8jfOqLdjC5BBoitKnaDvGw9OuuEE0qOY=
Received: by 10.227.206.82 with SMTP id ft18mr2019079wbb.21.1322911811420; Sat, 03 Dec 2011 03:30:11 -0800 (PST)
Received: from dhcp-10-55-90-228.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id n9sm10391276wbo.16.2011.12.03.03.30.07 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 03 Dec 2011 03:30:08 -0800 (PST)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com>
Date: Sat, 3 Dec 2011 12:30:06 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <66EBF10F-A971-48BD-968B-1202CBF94B49@employees.org>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1084)
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Sat, 03 Dec 2011 11:30:14 -0000

Ted,

s/3361/3633/g

phrased another way:
do we think we can do better than treating each stateful DHCPv6 option =
(IA_NA, IA_TA, IA_PD) as separate protocol instances?
as in:
A DHCPv6 client MUST initiate a separate session for each IA_ option it =
will request. DHCPv6 message behaviour and initiation will have slight =
variations per option type. A DHCPv6 server that has more than one =
stateful option to give to a client, MUST only include the requested IA_ =
option in any reply to the client.

cheers,
Ole

On Dec 3, 2011, at 4:18 , Ted Lemon wrote:

> There's been a bit of a discussion going on in the v6ops working group =
about a problem in the DHCP protocol that has to do with the coexistence =
of stateful address allocation and prefix delegation.
>=20
> The problem is that it's entirely possible that a PD requesting router =
might also want an IP address to number its upstream interface, so it =
might send a DHCP Solicit message containing both an IA_NA and an IA_PD. =
   Suppose the DHCP server is willing to do prefix delegation, but =
expects the RR to do SLAAC for the upstream address.   In this case, =
it's going to send an IA_PD containing one or more prefixes, but an =
IA_NA containing no addresses.
>=20
> RFC3315 wasn't written with RFC3361 in mind, so it doesn't really talk =
about what to do in this case.   It also doesn't address the problem of =
what to do if an IA_TA appears in the solicit, but the server isn't =
configured to offer temporary addresses.   This hasn't been much of an =
issue since I don't know of any clients that actually request temporary =
addresses, but of course it is an issue for IA_PD.
>=20
> There exist two errata that address this issue: erratum 2471 and =
erratum 2472.   These errata propose to have the status code appear =
inside the IA_NA option rather than in the outer layer of the Advertise =
message.   A similar erratum exists for RFC3361, proposing to put the =
status code option in the IA_PD option instead of, similarly, in the =
outer layer of the packet.
>=20
> In addition, the following observation has been made:
>=20
>  The other unclear problem area is around how to deal with IA_PD and =
IA_NA:
>    * Client requests both IA_NA and IA_PD in the same session, gets =
only IA_PD.
>      - Does it fork off a separate session for IA_NA and continues =
sending SOLICITs for only the IA_NA?
>      - Reset the DHCP client, and tries again?
>      - Keeps single session, and continues to ask for IA_NA on next =
RENEW?
>=20
>      all 3 behaviors have been seen in the wild plus some additional =
pathological cases.
>      in general dealing with multiple stateful options in DHCP is =
underspecified.
>=20
> So the topic for discussion in the working group here is as follows:
>=20
> 1. Is what is proposed in the errata the right thing?   Should we in =
fact have status codes inside of IA_* options instead of in the main =
packet?
>=20
> 2. If so, what is the full set of edits to RFC3315 and RFC3361 that =
are required to do this?
> 2a. What do we do for clients that don't implement the errata?
>=20
> 3. If not, what should we do instead?
>=20
> 4. If the client gets an IA_NA and no IA_PD, or vice versa, which of =
the three behaviors listed above should it follow?   Is it bad that =
different clients do this differently?
>=20
> 5. What have I missed?
>=20
> Comments?   Criticisms?   Rotten tomatoes?
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From mohta@necom830.hpcl.titech.ac.jp  Sat Dec  3 04:19:26 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 08FE521F8C3A for <dhcwg@ietfa.amsl.com>; Sat,  3 Dec 2011 04:19:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.655
X-Spam-Level: 
X-Spam-Status: No, score=0.655 tagged_above=-999 required=5 tests=[AWL=-0.745,  BAYES_05=-1.11, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aSz-LL3TaKFA for <dhcwg@ietfa.amsl.com>; Sat,  3 Dec 2011 04:19:25 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 9DC3C21F8C1B for <dhcwg@ietf.org>; Sat,  3 Dec 2011 04:19:21 -0800 (PST)
Received: (qmail 67575 invoked from network); 3 Dec 2011 12:52:11 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 3 Dec 2011 12:52:11 -0000
Message-ID: <4EDA13B7.9090402@necom830.hpcl.titech.ac.jp>
Date: Sat, 03 Dec 2011 21:19:03 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com>
In-Reply-To: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Sat, 03 Dec 2011 12:19:26 -0000

Ted Lemon wrote:

> If I had it to do over again, I'd do RA and DHCP a lot differently,
> but at this point I think in general we should assume that we will
> always have RAs, and DHCP clients should wait for them.

You may think so.

However, the reality is that, because of DAD latency forced by
RA, people are trying to avoid RA.

						Masataka Ohta

From Ted.Lemon@nominum.com  Sat Dec  3 08:49:36 2011
Return-Path: <Ted.Lemon@nominum.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 E498C21F8EA7 for <dhcwg@ietfa.amsl.com>; Sat,  3 Dec 2011 08:49:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.204
X-Spam-Level: 
X-Spam-Status: No, score=-106.204 tagged_above=-999 required=5 tests=[AWL=-0.206, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8t4vM1t53EvV for <dhcwg@ietfa.amsl.com>; Sat,  3 Dec 2011 08:49:36 -0800 (PST)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 5AC2021F8E8B for <dhcwg@ietf.org>; Sat,  3 Dec 2011 08:49:33 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKTtpTHJpoRr4QsOmnBJIdiYhE/HOc91yk@postini.com; Sat, 03 Dec 2011 08:49:33 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 4771D1B829F for <dhcwg@ietf.org>; Sat,  3 Dec 2011 08:49:32 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id B05D7190052; Sat,  3 Dec 2011 08:49:29 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0339.001; Sat, 3 Dec 2011 08:49:29 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Thread-Topic: [dhcwg] To wait for RA or not to wait?
Thread-Index: AQHMsRmaAFDsJ61sskWNi8UGYH6hlZXKj2aAgABLjQA=
Date: Sat, 3 Dec 2011 16:49:28 +0000
Message-ID: <6DA3E757-414F-41C3-A8A2-FA89EC7F6C8C@nominum.com>
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com> <4EDA13B7.9090402@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4EDA13B7.9090402@necom830.hpcl.titech.ac.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_6DA3E757414F41C3A8A2FA89EC7F6C8Cnominumcom_"
MIME-Version: 1.0
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Sat, 03 Dec 2011 16:49:37 -0000

--_000_6DA3E757414F41C3A8A2FA89EC7F6C8Cnominumcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Dec 3, 2011, at 7:19 AM, Masataka Ohta wrote:
However, the reality is that, because of DAD latency forced by
RA, people are trying to avoid RA.

This is very interesting, but ought to be in an ops doc, not a rumor.   Or =
maybe it already is in an ops doc that I missed?   There's been some intere=
sting discussion of various problems with RA in v6ops recently.


--_000_6DA3E757414F41C3A8A2FA89EC7F6C8Cnominumcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <3EC286C61E5D0B47B226439C2F0A933B@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 3, 2011, at 7:19 AM, Masataka Ohta wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">However,
 the reality is that, because of DAD latency forced by<br>
RA, people are trying to avoid RA.</span></blockquote>
</div>
<br>
<div>This is very interesting, but ought to be in an ops doc, not a rumor. =
&nbsp; Or maybe it already is in an ops doc that I missed? &nbsp; There's b=
een some interesting discussion of various problems with RA in v6ops recent=
ly.</div>
<div><br>
</div>
</body>
</html>

--_000_6DA3E757414F41C3A8A2FA89EC7F6C8Cnominumcom_--

From Ted.Lemon@nominum.com  Sat Dec  3 09:27:28 2011
Return-Path: <Ted.Lemon@nominum.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 7100821F9311 for <dhcwg@ietfa.amsl.com>; Sat,  3 Dec 2011 09:27:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.492
X-Spam-Level: 
X-Spam-Status: No, score=-106.492 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rPbpI2tVHsU8 for <dhcwg@ietfa.amsl.com>; Sat,  3 Dec 2011 09:27:27 -0800 (PST)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id 31D7121F9309 for <dhcwg@ietf.org>; Sat,  3 Dec 2011 09:27:27 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKTtpb/oxb7x+lNQhcALLNHWMsZeYB2pp5@postini.com; Sat, 03 Dec 2011 09:27:27 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 2715E1B8299 for <dhcwg@ietf.org>; Sat,  3 Dec 2011 09:27:26 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 0E9BC190052; Sat,  3 Dec 2011 09:27:26 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.01.0339.001; Sat, 3 Dec 2011 09:27:26 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ole Troan <otroan@employees.org>
Thread-Topic: [dhcwg] To wait for RA or not to wait?
Thread-Index: AQHMsRmaAFDsJ61sskWNi8UGYH6hlZXI4trAgACUOoCAACIqAP//0BMogAD9a4CAAH7PgA==
Date: Sat, 3 Dec 2011 17:27:24 +0000
Message-ID: <AD584676-3745-4709-ACED-E0928DF4515B@nominum.com>
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com> <867F4B6A1672E541A94676D556793ACD0CB42FDABE@MOPESMBX01.eu.thmulti.com> <BEA0EE13-9223-4D60-837C-AEAF74FAFD6E@nominum.com>, <2F5A4C2C-B219-47E6-B3C4-43CA8EE3B420@employees.org> <933A3C48-3B77-4E0D-A301-67736999E14A@nominum.com> <99E92F98-5026-44F3-A8E6-9D65D613B80B@employees.org>
In-Reply-To: <99E92F98-5026-44F3-A8E6-9D65D613B80B@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_AD58467637454709ACEDE0928DF4515Bnominumcom_"
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Sat, 03 Dec 2011 17:27:28 -0000

--_000_AD58467637454709ACEDE0928DF4515Bnominumcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Dec 3, 2011, at 4:53 AM, Ole Troan wrote:
we have had working interoperable implementations of DHCPv6 PD since 2003.
the "how PD should work with host configuration protocols" is a recent disc=
ussion. please don't rewrite history. if people want that changed now, fine=
. but you will find no basis in 3633 for that "unsettledness".

Sorry, I expressed myself poorly (perhaps due to not having really thought =
carefully about what I intended to say... :)

What I mean is that as far as I understand it, the behavior that all these =
implementations are interoperating with is not explicitly described anywher=
e in an RFC.   The reason we have interoperating implementations is either =
the UNH testing lab, implementors using other implementations as references=
, or discussion amongst implementors.   The correct way for us to get inter=
operability is for the protocol spec to say what to do, not either of these=
 three otherwise very good things.


--_000_AD58467637454709ACEDE0928DF4515Bnominumcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <FDE784B93E352941A7081EBBAD2CAEDC@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 3, 2011, at 4:53 AM, Ole Troan wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">we
 have had working interoperable implementations of DHCPv6 PD since 2003.<br=
>
the &quot;how PD should work with host configuration protocols&quot; is a r=
ecent discussion. please don't rewrite history. if people want that changed=
 now, fine. but you will find no basis in 3633 for that &quot;unsettledness=
&quot;.</span></blockquote>
</div>
<br>
<div>Sorry, I expressed myself poorly (perhaps due to not having really tho=
ught carefully about what I intended to say... :)</div>
<div><br>
</div>
<div>What I mean is that as far as I understand it, the behavior that all t=
hese implementations are interoperating with is not explicitly described an=
ywhere in an RFC. &nbsp; The reason we have interoperating implementations =
is either the UNH testing lab, implementors
 using other implementations as references, or discussion amongst implement=
ors. &nbsp; The correct way for us to get interoperability is for the proto=
col spec to say what to do, not either of these three otherwise very good t=
hings.</div>
<div><br>
</div>
</body>
</html>

--_000_AD58467637454709ACEDE0928DF4515Bnominumcom_--

From ichiroumakino@gmail.com  Sat Dec  3 09:45:07 2011
Return-Path: <ichiroumakino@gmail.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 2936821F8E51 for <dhcwg@ietfa.amsl.com>; Sat,  3 Dec 2011 09:45:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BBEStXuXFKUc for <dhcwg@ietfa.amsl.com>; Sat,  3 Dec 2011 09:45:06 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7813921F8AD6 for <dhcwg@ietf.org>; Sat,  3 Dec 2011 09:45:06 -0800 (PST)
Received: by eaak10 with SMTP id k10so576569eaa.31 for <dhcwg@ietf.org>; Sat, 03 Dec 2011 09:45:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=DLAY46SXNPuZH5TRWtqDxieU1PgZIWliwYmcL4PN7+c=; b=Mx6ee6xcKbrdi041RTxoRjYrdkepPoNTo6AdnuwdTRQznNv5JvynKMmRkXGI+OKqxN ZzSh81v0lBBOjWKGfFbAcrG9fybt1rLRMfPxBKWy6Kh+f9iA2BCS/2k/bXll4vmsCi8V J7b7tcbB7NJWIQO/+UlrMIvsInSHF8x7NxGuk=
Received: by 10.213.10.11 with SMTP id n11mr174520ebn.81.1322934305655; Sat, 03 Dec 2011 09:45:05 -0800 (PST)
Received: from gomlefisk.lan (141.84-48-218.nextgentel.com. [84.48.218.141]) by mx.google.com with ESMTPS id v3sm39177002eej.7.2011.12.03.09.45.00 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 03 Dec 2011 09:45:04 -0800 (PST)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <AD584676-3745-4709-ACED-E0928DF4515B@nominum.com>
Date: Sat, 3 Dec 2011 18:44:56 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <36614E3C-60D5-4941-B7B1-D0550F0FAF5A@employees.org>
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com> <867F4B6A1672E541A94676D556793ACD0CB42FDABE@MOPESMBX01.eu.thmulti.com> <BEA0EE13-9223-4D60-837C-AEAF74FAFD6E@nominum.com>, <2F5A4C2C-B219-47E6-B3C4-43CA8EE3B420@employees.org> <933A3C48-3B77-4E0D-A301-67736999E14A@nominum.com> <99E92F98-5026-44F3-A8E6-9D65D613B80B@employees.org> <AD584676-3745-4709-ACED-E0928DF4515B@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1084)
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Sat, 03 Dec 2011 17:45:07 -0000

Ted,

>> we have had working interoperable implementations of DHCPv6 PD since =
2003.
>> the "how PD should work with host configuration protocols" is a =
recent discussion. please don't rewrite history. if people want that =
changed now, fine. but you will find no basis in 3633 for that =
"unsettledness".
>=20
> Sorry, I expressed myself poorly (perhaps due to not having really =
thought carefully about what I intended to say... :)
>=20
> What I mean is that as far as I understand it, the behavior that all =
these implementations are interoperating with is not explicitly =
described anywhere in an RFC.   The reason we have interoperating =
implementations is either the UNH testing lab, implementors using other =
implementations as references, or discussion amongst implementors.   The =
correct way for us to get interoperability is for the protocol spec to =
say what to do, not either of these three otherwise very good things.

fully with you on that.
let's describe the right things to do in DHC, and solve the =
interoperability issues within DHC, without depending on other =
protocols.

cheers,
Ole=

From mohta@necom830.hpcl.titech.ac.jp  Sat Dec  3 17:38:45 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 6357B21F84FA for <dhcwg@ietfa.amsl.com>; Sat,  3 Dec 2011 17:38:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.359
X-Spam-Level: 
X-Spam-Status: No, score=0.359 tagged_above=-999 required=5 tests=[AWL=-0.151,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ULc0uedCjZay for <dhcwg@ietfa.amsl.com>; Sat,  3 Dec 2011 17:38:45 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 9517B21F84DB for <dhcwg@ietf.org>; Sat,  3 Dec 2011 17:38:44 -0800 (PST)
Received: (qmail 78731 invoked from network); 4 Dec 2011 02:11:31 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 4 Dec 2011 02:11:31 -0000
Message-ID: <4EDACEE4.5080905@necom830.hpcl.titech.ac.jp>
Date: Sun, 04 Dec 2011 10:37:40 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com> <4EDA13B7.9090402@necom830.hpcl.titech.ac.jp> <6DA3E757-414F-41C3-A8A2-FA89EC7F6C8C@nominum.com>
In-Reply-To: <6DA3E757-414F-41C3-A8A2-FA89EC7F6C8C@nominum.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Sun, 04 Dec 2011 01:38:45 -0000

Ted Lemon wrote:

>> However, the reality is that, because of DAD latency forced by
>> RA, people are trying to avoid RA.

> This is very interesting, but ought to be in an ops doc, not
> a rumor.

The problem in the real world is that for mobile nodes
DAD latency means loss of communication during handover
between cells, if the nodes move quickly or the cells
are small.

Some people recognized it at the last 802.11 interim
meeting.

> Or maybe it already is in an ops doc that I missed?

I don't know. It is real pain to discuss against IPv6
people who do not understand operational issues at all.

> There's been some interesting discussion of various
> problems with RA in v6ops recently.

If RA is obsoleted entirely, it will make IPv6 a lot
less broken.

						Masataka Ohta

From Ted.Lemon@nominum.com  Sat Dec  3 19:18:50 2011
Return-Path: <Ted.Lemon@nominum.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 6AA6721F93A3 for <dhcwg@ietfa.amsl.com>; Sat,  3 Dec 2011 19:18:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.514
X-Spam-Level: 
X-Spam-Status: No, score=-106.514 tagged_above=-999 required=5 tests=[AWL=0.084, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QiafEuyYAT1f for <dhcwg@ietfa.amsl.com>; Sat,  3 Dec 2011 19:18:49 -0800 (PST)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id 91FF321F939E for <dhcwg@ietf.org>; Sat,  3 Dec 2011 19:18:49 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKTtrmhZaMkaerkzFYbBCMGgOq8TQ/v76y@postini.com; Sat, 03 Dec 2011 19:18:49 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 230BE1B829F for <dhcwg@ietf.org>; Sat,  3 Dec 2011 19:18:29 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 0A8A3190052; Sat,  3 Dec 2011 19:18:28 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.01.0339.001; Sat, 3 Dec 2011 19:18:28 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Thread-Topic: [dhcwg] To wait for RA or not to wait?
Thread-Index: AQHMsRmaAFDsJ61sskWNi8UGYH6hlZXKj2aAgABLjQCAAJOUAIAAHCcA
Date: Sun, 4 Dec 2011 03:18:27 +0000
Message-ID: <60C9046A-F5E9-4B34-9056-48EA34788E81@nominum.com>
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com> <4EDA13B7.9090402@necom830.hpcl.titech.ac.jp> <6DA3E757-414F-41C3-A8A2-FA89EC7F6C8C@nominum.com> <4EDACEE4.5080905@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4EDACEE4.5080905@necom830.hpcl.titech.ac.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_60C9046AF5E94B34905648EA34788E81nominumcom_"
MIME-Version: 1.0
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Sun, 04 Dec 2011 03:18:50 -0000

--_000_60C9046AF5E94B34905648EA34788E81nominumcom_
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable

On Dec 3, 2011, at 8:37 PM, Masataka Ohta wrote:
I don't know. It is real pain to discuss against IPv6
people who do not understand operational issues at all.

Margaret Wasserman gave a presentation at the recent IETF in Taipei about p=
ower consumption issues with RA, but I don't recall hearing a presentation =
about DAD latency during handoff.   I suspect the work Margaret is doing mi=
ght help with this, though=1B$B!=3D=1B(Byou might want to look at it.   I s=
aw a _lot_ more concrete discussion of operational issues in Taipei than I'=
ve seen in any previous IETF, which I took to be a hopeful sign, although I=
 suspect it is going to create a lot of work for us.

If RA is obsoleted entirely, it will make IPv6 a lot
less broken.

I don't disagree with you, but if we could obsolete RA, DHCP would not curr=
ently be a full replacement at the moment, and I am _not_ referring to the =
route option.   DHCP doesn't currently support multihoming properly.   So w=
e would have to do a bit of additional work.   And in any case, obsoleting =
RA is not a decision the DHC working group can take: it's something for 6ma=
n.



--_000_60C9046AF5E94B34905648EA34788E81nominumcom_
Content-Type: text/html; charset="iso-2022-jp"
Content-ID: <E10BFF1EC5B5B84BBBF6B3C8C2793692@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-2022-=
jp">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 3, 2011, at 8:37 PM, Masataka Ohta wrote:</div>
<div>
<blockquote type=3D"cite">I don't know. It is real pain to discuss against =
IPv6<br>
people who do not understand operational issues at all.</blockquote>
<br>
</div>
<div>Margaret Wasserman gave a presentation at the recent IETF in Taipei ab=
out power consumption issues with RA, but I don't recall hearing a presenta=
tion about DAD latency during handoff. &nbsp; I suspect the work Margaret i=
s doing might help with this, though=1B$B!=3D=1B(Byou
 might want to look at it. &nbsp; I saw a _lot_ more concrete discussion of=
 operational issues in Taipei than I've seen in any previous IETF, which I =
took to be a hopeful sign, although I suspect it is going to create a lot o=
f work for us.</div>
<div><br>
</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">If
 RA is obsoleted entirely, it will make IPv6 a lot<br>
less broken.</span></blockquote>
</div>
<br>
<div>I don't disagree with you, but if we could obsolete RA, DHCP would not=
 currently be a full replacement at the moment, and I am _not_ referring to=
 the route option. &nbsp; DHCP doesn't currently support multihoming proper=
ly. &nbsp; So we would have to do a bit of
 additional work. &nbsp; And in any case, obsoleting RA is not a decision t=
he DHC working group can take: it's something for 6man.</div>
<div><br>
</div>
<div><br>
</div>
</body>
</html>

--_000_60C9046AF5E94B34905648EA34788E81nominumcom_--

From mohta@necom830.hpcl.titech.ac.jp  Sun Dec  4 00:36:45 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 899EB21F84A9 for <dhcwg@ietfa.amsl.com>; Sun,  4 Dec 2011 00:36:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.084
X-Spam-Level: 
X-Spam-Status: No, score=0.084 tagged_above=-999 required=5 tests=[AWL=0.174,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AHLzCn1zuY12 for <dhcwg@ietfa.amsl.com>; Sun,  4 Dec 2011 00:36:45 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id A6F3B21F84A7 for <dhcwg@ietf.org>; Sun,  4 Dec 2011 00:36:43 -0800 (PST)
Received: (qmail 85278 invoked from network); 4 Dec 2011 09:09:25 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 4 Dec 2011 09:09:25 -0000
Message-ID: <4EDB30FC.1020204@necom830.hpcl.titech.ac.jp>
Date: Sun, 04 Dec 2011 17:36:12 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com> <4EDA13B7.9090402@necom830.hpcl.titech.ac.jp> <6DA3E757-414F-41C3-A8A2-FA89EC7F6C8C@nominum.com> <4EDACEE4.5080905@necom830.hpcl.titech.ac.jp> <60C9046A-F5E9-4B34-9056-48EA34788E81@nominum.com>
In-Reply-To: <60C9046A-F5E9-4B34-9056-48EA34788E81@nominum.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Sun, 04 Dec 2011 08:36:45 -0000

Ted Lemon wrote:

> but I don't
> recall hearing a presentation about DAD latency during handoff.

It was discussed in IEEE802.11.

> I suspect the work Margaret is doing might help with this,
> though$B!=(Byou might want to look at it.   I saw a _lot_ more
> concrete discussion of operational issues in Taipei than
> I've seen in any previous IETF, which I took to be a
> hopeful sign, although I suspect it is going to create a
> lot of work for us.

Their approach for the operational issues is to make ND
even more complex, I'm afraid, only to make the issues
more complicated.

>> If RA is obsoleted entirely, it will make IPv6 a lot
>> less broken.

> I don't disagree with you, but if we could obsolete RA, DHCP
> would not currently be a full replacement at the moment,
> and I am _not_ referring to the route option.

The only reasonable, or, end to end, way for an end system
connected to multiple routers obtain route information is
to snoop IGP.

In addition, the only reasonable way for an end system
connected to one or more routers to select proper source
address is to let IGP carry source prefix information
appropriate for each routing table entry.

> DHCP doesn't currently support multihoming properly.

Neither RA nor DHCP can, unless either is bloated to be
an IGP with source prefix information.

> So we would have to do a bit of additional work.

Yes, but not here.

> And in any case, obsoleting RA is not a decision the
> DHC working group can take: it's something for 6man.

Here, you can assume DHCPv6 used without RA. Let
someone else bother on route issues.

					Masataka Ohta

From shemant@cisco.com  Sun Dec  4 08:15:50 2011
Return-Path: <shemant@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 80E8F21F85A1 for <dhcwg@ietfa.amsl.com>; Sun,  4 Dec 2011 08:15:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.55
X-Spam-Level: 
X-Spam-Status: No, score=-6.55 tagged_above=-999 required=5 tests=[AWL=0.049,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2lA6cb1O14Il for <dhcwg@ietfa.amsl.com>; Sun,  4 Dec 2011 08:15:49 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id ADF6F21F8593 for <dhcwg@ietf.org>; Sun,  4 Dec 2011 08:15:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=739; q=dns/txt; s=iport; t=1323015349; x=1324224949; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=p4d4pGInAg/lv9W8lMB32w0J+Y/ObLc5qfD5U2zatgw=; b=hkTsmd1CNE6uIf6ALcAzytlCtwoCcq7mV8el3DGDfEENyefmXtMQHYXt fDUMndRnWRhRtIg/1O4xBmfMTZou7D350E9iG1Pj1hTQOEB8b88GednrI lk1r083D1AJYx9I3Rfj63J7rNFukZ3Kn30UZphAb6PX6tOoq+QiFZ9NWw 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwBAFqc206tJXHB/2dsb2JhbABEDpl6jlQBgVOBBYFyAQEBBBIBHQo/DAQCAQgOAwQBAQsGFwEGAUUJCAEBBAESCBqfKAGdTIo+YwSILZ4QVg
X-IronPort-AV: E=Sophos;i="4.71,294,1320624000"; d="scan'208";a="41017624"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-2.cisco.com with ESMTP; 04 Dec 2011 16:15:49 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core2-6.cisco.com (8.14.3/8.14.3) with ESMTP id pB4GFnRV008084;  Sun, 4 Dec 2011 16:15:49 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 4 Dec 2011 10:15:48 -0600
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 4 Dec 2011 10:15:47 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C3037785E5@XMB-RCD-109.cisco.com>
In-Reply-To: <4EDB30FC.1020204@necom830.hpcl.titech.ac.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] To wait for RA or not to wait?
Thread-Index: AcyyX91KQPWAozP2SDaac5p1jQjxMgAP4CqA
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com><4EDA13B7.9090402@necom830.hpcl.titech.ac.jp><6DA3E757-414F-41C3-A8A2-FA89EC7F6C8C@nominum.com><4EDACEE4.5080905@necom830.hpcl.titech.ac.jp><60C9046A-F5E9-4B34-9056-48EA34788E81@nominum.com> <4EDB30FC.1020204@necom830.hpcl.titech.ac.jp>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Masataka Ohta" <mohta@necom830.hpcl.titech.ac.jp>, "Ted Lemon" <Ted.Lemon@nominum.com>
X-OriginalArrivalTime: 04 Dec 2011 16:15:48.0728 (UTC) FILETIME=[FC2D6780:01CCB29F]
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Sun, 04 Dec 2011 16:15:50 -0000

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Masataka Ohta
Sent: Sunday, December 04, 2011 3:36 AM
To: Ted Lemon
Cc: <dhcwg@ietf.org>
Subject: Re: [dhcwg] To wait for RA or not to wait?

>The only reasonable, or, end to end, way for an end system
>connected to multiple routers obtain route information is
>to snoop IGP.

If the end system is a host, it's a non-starter to have a host
participate in an IGP with a router in the network.  If the end system
is a router, in wireline broadband deployment the access concentrator
terminates over 100K end systems, the network does not prefer to run
routing from the end systems to the access concentrator.

Hemant

From shemant@cisco.com  Sun Dec  4 11:34:22 2011
Return-Path: <shemant@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 3E4A421F8593 for <dhcwg@ietfa.amsl.com>; Sun,  4 Dec 2011 11:34:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.25
X-Spam-Level: 
X-Spam-Status: No, score=-6.25 tagged_above=-999 required=5 tests=[AWL=-0.252,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XRE8B3rwvzej for <dhcwg@ietfa.amsl.com>; Sun,  4 Dec 2011 11:34:21 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 085A621F858D for <dhcwg@ietf.org>; Sun,  4 Dec 2011 11:34:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=10414; q=dns/txt; s=iport; t=1323027261; x=1324236861; h=mime-version:subject:date:message-id:in-reply-to: references:from:to:cc; bh=hgdqwIYUH9aB4yiRVAsV2sgxXXsVmg5w8IzDgH5K8Ko=; b=kC8HU+UgksmiBUGjbRIFP0dKXsGZA1RVTKDti2u7/qjMtAzqAxgtxNkL 0ulqPUC+Qaa1TXfdsEEtzmyMaRbXH4eCMQcg3eWT4v/t4jhsAI9bv+v+z VKLEktMAMnRXggTBS2yiGVqaF/QXiwHTDy7HCBPbVnnVhfjqaS67e4YCY Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwBAALL206tJV2a/2dsb2JhbABEDoI/lzuOVAGBU4EFgXIBAQEDARIBCREDSQwEAgEIDgMEAQELBhcBBgFFCQgBAQQBEggBCw6HZQiXHQGdQYo+YwSILZ4QVg
X-IronPort-AV: E=Sophos;i="4.71,294,1320624000"; d="scan'208,217";a="41056331"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-7.cisco.com with ESMTP; 04 Dec 2011 19:34:20 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pB4JYKR5016217;  Sun, 4 Dec 2011 19:34:20 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 4 Dec 2011 13:34:19 -0600
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCB2BB.B79B075A"
Date: Sun, 4 Dec 2011 13:34:17 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C303778606@XMB-RCD-109.cisco.com>
In-Reply-To: <4EDB30FC.1020204@necom830.hpcl.titech.ac.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] To wait for RA or not to wait?
Thread-Index: AcyyX91KQPWAozP2SDaac5p1jQjxMgARQ4Mw
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com><4EDA13B7.9090402@necom830.hpcl.titech.ac.jp><6DA3E757-414F-41C3-A8A2-FA89EC7F6C8C@nominum.com><4EDACEE4.5080905@necom830.hpcl.titech.ac.jp><60C9046A-F5E9-4B34-9056-48EA34788E81@nominum.com> <4EDB30FC.1020204@necom830.hpcl.titech.ac.jp>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Masataka Ohta" <mohta@necom830.hpcl.titech.ac.jp>, "Ted Lemon" <Ted.Lemon@nominum.com>
X-OriginalArrivalTime: 04 Dec 2011 19:34:19.0857 (UTC) FILETIME=[B7C37410:01CCB2BB]
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Sun, 04 Dec 2011 19:34:22 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CCB2BB.B79B075A
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20

=20

-----Original Message-----

From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Masataka Ohta

Sent: Sunday, December 04, 2011 3:36 AM

To: Ted Lemon

Cc: <dhcwg@ietf.org>

Subject: Re: [dhcwg] To wait for RA or not to wait?

=20

=20

>>In addition, the only reasonable way for an end system

>>connected to one or more routers to select proper source

>>address is to let IGP carry source prefix information

>>appropriate for each routing table entry.

=20

I already replied today that the IGP is a non-starter.  For hosts that a
router supports, it's best that a SAS Policy Table is sent to the host
using DHCPv6.  See the IETF 6man WG documents that are revising rfc3484
and has related documents.  Please also see the email I sent recently to
v6ops below.

=20

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

=20

>> DHCP doesn't currently support multihoming properly.

=20

>Neither RA nor DHCP can, unless either is bloated to be

>an IGP with source prefix information.

=20

Both DHCP and RA for basic behavior use IPv6 multicast - the RA is
multicast to the nodes on the link and the DHCPv6 SOLICIT is multicast
from a DHCPv6 client.  Thus we should not bother looking into either of
DHCPv6 or the IPv6 ND RA for multihoming.  Multihoming is better mapped
to router and host for behavior.  Routers are best served, if
multihomed, to use PBR where PBR works by keying off of the
source-address of the packets the router has to forward.  With hosts
being multihomed, the router could provide the SAS Policy Table to the
hosts via DHCPv6 or the SAS Policy table is manually configured on the
hosts.

=20

There is still the fundamental problem open which is how does the host
get a default router if DHCPv6 provides only an IPv6 address to the host
and the host does not receive an RA that provided the default router to
the host.  Sticking the default router information in a DHCPv6 option is
nowhere close to consensus in the IETF community. =20

=20

Hemant


------_=_NextPart_001_01CCB2BB.B79B075A
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'>-----Original =
Message-----<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'>From: <a =
href=3D"mailto:dhcwg-bounces@ietf.org">dhcwg-bounces@ietf.org</a> <a =
href=3D"mailto:[mailto:dhcwg-bounces@ietf.org]">[mailto:dhcwg-bounces@iet=
f.org]</a> On Behalf Of Masataka Ohta<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'>Sent: Sunday, =
December 04, 2011 3:36 AM<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'>To: Ted =
Lemon<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'>Cc: &lt;<a =
href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>&gt;<o:p></o:p></span></=
p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'>Subject: Re: =
[dhcwg] To wait for RA or not to wait?<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'>&gt;&gt;In =
addition, the only reasonable way for an end =
system<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'>&gt;&gt;connected =
to one or more routers to select proper source<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'>&gt;&gt;address is =
to let IGP carry source prefix information<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'>&gt;&gt;appropriate =
for each routing table entry.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'>I already replied =
today that the IGP is a non-starter.&nbsp; For hosts that a router =
supports, it's best that a SAS Policy Table is sent to the host using =
DHCPv6.&nbsp; See the IETF 6man WG documents that are revising rfc3484 =
and has related documents.&nbsp; Please also see the email I sent =
recently to v6ops below.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'><a =
href=3D"http://www.ietf.org/mail-archive/web/v6ops/current/msg11508.html"=
>http://www.ietf.org/mail-archive/web/v6ops/current/msg11508.html</a><o:p=
></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'>&gt;&gt; DHCP =
doesn't currently support multihoming properly.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'>&gt;Neither RA nor =
DHCP can, unless either is bloated to be<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'>&gt;an IGP with =
source prefix information.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'>Both DHCP and RA =
for basic behavior use IPv6 multicast - the RA is multicast to the nodes =
on the link and the DHCPv6 SOLICIT is multicast from a DHCPv6 =
client.&nbsp; Thus we should not bother looking into either of DHCPv6 or =
the IPv6 ND RA for multihoming.&nbsp; Multihoming is better mapped to =
router and host for behavior.&nbsp; Routers are best served, if =
multihomed, to use PBR where PBR works by keying off of the =
source-address of the packets the router has to forward.&nbsp; With =
hosts being multihomed, the router could provide the SAS Policy Table to =
the hosts via DHCPv6 or the SAS Policy table is manually configured on =
the hosts.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier New"'>There is still the =
fundamental problem open which is how does the host get a default router =
if DHCPv6 provides only an IPv6 address to the host and the host does =
not receive an RA that provided the default router to the host.&nbsp; =
Sticking the default router information in a DHCPv6 option is nowhere =
close to consensus in the IETF community.&nbsp; <o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Courier =
New"'>Hemant<o:p></o:p></span></p></div></body></html>
------_=_NextPart_001_01CCB2BB.B79B075A--

From mohta@necom830.hpcl.titech.ac.jp  Sun Dec  4 12:40:14 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 9B90C21F8478 for <dhcwg@ietfa.amsl.com>; Sun,  4 Dec 2011 12:40:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.059
X-Spam-Level: 
X-Spam-Status: No, score=0.059 tagged_above=-999 required=5 tests=[AWL=0.149,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s3OCyJK4GZ0U for <dhcwg@ietfa.amsl.com>; Sun,  4 Dec 2011 12:40:14 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id CFE6521F846A for <dhcwg@ietf.org>; Sun,  4 Dec 2011 12:40:13 -0800 (PST)
Received: (qmail 92489 invoked from network); 4 Dec 2011 21:12:40 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 4 Dec 2011 21:12:40 -0000
Message-ID: <4EDBDA5C.2080103@necom830.hpcl.titech.ac.jp>
Date: Mon, 05 Dec 2011 05:38:52 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com><4EDA13B7.9090402@necom830.hpcl.titech.ac.jp><6DA3E757-414F-41C3-A8A2-FA89EC7F6C8C@nominum.com><4EDACEE4.5080905@necom830.hpcl.titech.ac.jp><60C9046A-F5E9-4B34-9056-48EA34788E81@nominum.com> <4EDB30FC.1020204@necom830.hpcl.titech.ac.jp> <5B6B2B64C9FE2A489045EEEADDAFF2C3037785E5@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C3037785E5@XMB-RCD-109.cisco.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Sun, 04 Dec 2011 20:40:14 -0000

Hemant Singh (shemant) wrote:

>> The only reasonable, or, end to end, way for an end system
>> connected to multiple routers obtain route information is
>> to snoop IGP.

> If the end system is a host, it's a non-starter to have a host
> participate in an IGP with a router in the network.

That is an unfounded and wrong statement.

The fundamental problem is in source address selection, against
which default routers and longest matches are assured to be
"incomplete" and "incorrect" by the end to end argument:

	http://groups.csail.mit.edu/ana/Publications/PubPDFs/End-to-End%20Arguments%20in%20System%20Design.pdf
	The function in question can completely and correctly
	be implemented only with the knowledge and help of
	the application standing at the end points of the
	communication system. Therefore, providing that
	questioned function as a feature of the communication
	system itself is not possible.

Note that routers are in "the communication system".

> If the end system
> is a router, in wireline broadband deployment the access concentrator
> terminates over 100K end systems, the network does not prefer to run
> routing from the end systems to the access concentrator.

You don't have to do so for (most?) users with only one source
address, which is the case where default routers will do.

Without involving dynamics of IGP, you may also add statically
distinguishable source addresses such as link local ones,
though it is an unnecessary complication.

Beyond that, approaches not heavily involving end systems is,
at most, "incomplete" and "incorrect".

						Masataka Ohta

From mohta@necom830.hpcl.titech.ac.jp  Sun Dec  4 12:52:32 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 6DCE621F87C5 for <dhcwg@ietfa.amsl.com>; Sun,  4 Dec 2011 12:52:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.041
X-Spam-Level: 
X-Spam-Status: No, score=0.041 tagged_above=-999 required=5 tests=[AWL=0.131,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yRK9Fe362u-b for <dhcwg@ietfa.amsl.com>; Sun,  4 Dec 2011 12:52:32 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id B556E21F86F6 for <dhcwg@ietf.org>; Sun,  4 Dec 2011 12:52:31 -0800 (PST)
Received: (qmail 92603 invoked from network); 4 Dec 2011 21:25:46 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 4 Dec 2011 21:25:46 -0000
Message-ID: <4EDBDD6D.4080006@necom830.hpcl.titech.ac.jp>
Date: Mon, 05 Dec 2011 05:51:57 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com><4EDA13B7.9090402@necom830.hpcl.titech.ac.jp><6DA3E757-414F-41C3-A8A2-FA89EC7F6C8C@nominum.com><4EDACEE4.5080905@necom830.hpcl.titech.ac.jp><60C9046A-F5E9-4B34-9056-48EA34788E81@nominum.com> <4EDB30FC.1020204@necom830.hpcl.titech.ac.jp> <5B6B2B64C9FE2A489045EEEADDAFF2C303778606@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C303778606@XMB-RCD-109.cisco.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Sun, 04 Dec 2011 20:52:32 -0000

Hemant Singh (shemant) wrote:

> For hosts that a
> router supports, it's best that a SAS Policy Table is sent to the host
> using DHCPv6.

The operational problem, then, is that the table reflecting
IGP dynamics can not be constructed automatically without
IGP carrying source prefix information with each routing
table entries.

Having such an IGP, it's snooping IGP through DHC, as I wrote:

> The only reasonable, or, end to end, way for an end system
> connected to multiple routers obtain route information is
> to snoop IGP.

> There is still the fundamental problem open which is how does the host
> get a default router

Don't to that.

If you have a reasonable SAS policy table, each entry of the
table can and should have a router to use.

						Masataka Ohta

From shemant@cisco.com  Sun Dec  4 16:09:06 2011
Return-Path: <shemant@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 2129C21F86F6 for <dhcwg@ietfa.amsl.com>; Sun,  4 Dec 2011 16:09:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.545
X-Spam-Level: 
X-Spam-Status: No, score=-6.545 tagged_above=-999 required=5 tests=[AWL=0.054,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5feJb0IvKFOt for <dhcwg@ietfa.amsl.com>; Sun,  4 Dec 2011 16:09:05 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 805DE21F85DB for <dhcwg@ietf.org>; Sun,  4 Dec 2011 16:09:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=618; q=dns/txt; s=iport; t=1323043745; x=1324253345; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=whI4dQVnXOFSDpUoZwAATAjs+Nn5drHd58eauu1YDLQ=; b=kPaxMNw3TP8FYZau43OzSxEjXL/5qv+A7PprsmTGWvKIdsV9pMkq9YKV IuneUrpUed/V3u1bp3UtpU8VofZnduCZN1YW/jSftTPc9sgJqZkuZ0o61 2NwxEkDWxOqNZNsxenI+Hs+mutQo1a4AsuoBlMW/T5JjS+LC4gG9+5bMQ Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEBANcK3E6tJV2Y/2dsb2JhbABEDpoBjlQBgVOBBYFyAQEBBBIBHQpLBAIBCA4DBAEBCwYXAQYBRQkIAQEEARIIGp5pAZ1Aij5jBIgtnhBW
X-IronPort-AV: E=Sophos;i="4.71,295,1320624000"; d="scan'208";a="41068601"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-5.cisco.com with ESMTP; 05 Dec 2011 00:09:05 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pB5095ZP007882;  Mon, 5 Dec 2011 00:09:05 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 4 Dec 2011 18:09:04 -0600
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 4 Dec 2011 18:09:03 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C303778615@XMB-RCD-109.cisco.com>
In-Reply-To: <4EDBDA5C.2080103@necom830.hpcl.titech.ac.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] To wait for RA or not to wait?
Thread-Index: AcyyxO768BE0kf6iTIKmjHvasrhFuAAHOKIQ
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com><4EDA13B7.9090402@necom830.hpcl.titech.ac.jp><6DA3E757-414F-41C3-A8A2-FA89EC7F6C8C@nominum.com><4EDACEE4.5080905@necom830.hpcl.titech.ac.jp><60C9046A-F5E9-4B34-9056-48EA34788E81@nominum.com><4EDB30FC.1020204@necom830.hpcl.titech.ac.jp><5B6B2B64C9FE2A489045EEEADDAFF2C3037785E5@XMB-RCD-109.cisco.com> <4EDBDA5C.2080103@necom830.hpcl.titech.ac.jp>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Masataka Ohta" <mohta@necom830.hpcl.titech.ac.jp>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 05 Dec 2011 00:09:04.0630 (UTC) FILETIME=[19743160:01CCB2E2]
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Mon, 05 Dec 2011 00:09:06 -0000

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Masataka Ohta
Sent: Sunday, December 04, 2011 3:39 PM
To: dhcwg@ietf.org
Subject: Re: [dhcwg] To wait for RA or not to wait?

>The fundamental problem is in source address selection, against
>which default routers and longest matches are assured to be
>"incomplete" and "incorrect" by the end to end argument:

If a host has multiple default routers, then issue MSR from the routers
to the host as specified in RFC 4191.  Just does not make sense to run
routing between a router and a host.

Hemant


From shemant@cisco.com  Sun Dec  4 19:20:22 2011
Return-Path: <shemant@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 3CB9121F86AA for <dhcwg@ietfa.amsl.com>; Sun,  4 Dec 2011 19:20:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.546
X-Spam-Level: 
X-Spam-Status: No, score=-6.546 tagged_above=-999 required=5 tests=[AWL=0.053,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GvKdNQbQlw80 for <dhcwg@ietfa.amsl.com>; Sun,  4 Dec 2011 19:20:21 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 579D421F8663 for <dhcwg@ietf.org>; Sun,  4 Dec 2011 19:20:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1579; q=dns/txt; s=iport; t=1323055221; x=1324264821; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=TicQZlue6YPM2m5n+Nzze21XugUBTQpGA7dK8pDco0I=; b=EcVd1plEEEYApR33gr1d7JCq5nSwEHXpHIT4/xc+mMSepP06w1RgRZzj PW+9BknAYjRsGIOXbXn3Rhi7ydGMq5h0iFyS8dfeHfxPLiWfHw0J8gsTW iU5vVlGsrhpkZbH2R+aJkHQZe7IWjXkutikAKI5I0aYU2yvrKZCkpzVeH 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhABABEppk6tJXG+/2dsb2JhbACQRY4WeIhwi2WSNIYZBIZQjXmKCFQ
X-IronPort-AV: E=Sophos;i="4.69,622,1315180800"; d="scan'208";a="38581309"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-9.cisco.com with ESMTP; 05 Dec 2011 03:20:20 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core2-3.cisco.com (8.14.3/8.14.3) with ESMTP id pB53K60u005549;  Mon, 5 Dec 2011 03:20:06 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 4 Dec 2011 21:20:06 -0600
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 4 Dec 2011 21:20:05 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C303778634@XMB-RCD-109.cisco.com>
In-Reply-To: <4EDB30FC.1020204@necom830.hpcl.titech.ac.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] To wait for RA or not to wait?
Thread-Index: AcyyX91KQPWAozP2SDaac5p1jQjxMgAm1WQw
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com><4EDA13B7.9090402@necom830.hpcl.titech.ac.jp><6DA3E757-414F-41C3-A8A2-FA89EC7F6C8C@nominum.com><4EDACEE4.5080905@necom830.hpcl.titech.ac.jp><60C9046A-F5E9-4B34-9056-48EA34788E81@nominum.com> <4EDB30FC.1020204@necom830.hpcl.titech.ac.jp>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Masataka Ohta" <mohta@necom830.hpcl.titech.ac.jp>, "Ted Lemon" <Ted.Lemon@nominum.com>
X-OriginalArrivalTime: 05 Dec 2011 03:20:06.0217 (UTC) FILETIME=[C9179390:01CCB2FC]
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Mon, 05 Dec 2011 03:20:22 -0000

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Masataka Ohta
Sent: Sunday, December 04, 2011 3:36 AM
To: Ted Lemon
Cc: <dhcwg@ietf.org>
Subject: Re: [dhcwg] To wait for RA or not to wait?

>>Ted Lemon wrote:

>> but I don't
>> recall hearing a presentation about DAD latency during handoff.

> It was discussed in IEEE802.11.

What is this DAD latency?  Is it the roughly two seconds a node waits
before the node deems DAD has passed for the node's IPv6 address?
Further, what had DAD latency got to do with waiting for the RA?   Soon
as a node is enabled for IPv6, the node creates an IPv6 link-local
address and then issues a DAD for the link-local.  But while the DAD
procedure is going on, the node is likely to receive an RA.   Certainly
the node can't initiate DHCPv6 until the DAD procedure completes (in up
to two secs) because the node sources the DHCPv6 messages with the IPv6
link-local.  Frankly the node can wait for the RA which gives the node a
default router until the node has to send a unicast packet out to the
network.  To reduce any two seconds DAD delay, one can use Optimistic
DAD - I am digressing here if there is no association found between DAD
latency and the issue of waiting for the RA.

I still belong to a camp that says don't wait for the RA to initiate
DHCPv6.  By the time DHCPv6 completes, the DHCPv6 client is expected to
see and RA.  If the node does not receive the RA by then, manual
intervention by a sys admin of the network is needed.

Hemant

From mohta@necom830.hpcl.titech.ac.jp  Sun Dec  4 19:29:05 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 AF63721F8AD3 for <dhcwg@ietfa.amsl.com>; Sun,  4 Dec 2011 19:29:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.026
X-Spam-Level: 
X-Spam-Status: No, score=0.026 tagged_above=-999 required=5 tests=[AWL=0.116,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6BpwwH-xYae8 for <dhcwg@ietfa.amsl.com>; Sun,  4 Dec 2011 19:29:05 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id CB9E821F8ACE for <dhcwg@ietf.org>; Sun,  4 Dec 2011 19:29:04 -0800 (PST)
Received: (qmail 469 invoked from network); 5 Dec 2011 04:01:49 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 5 Dec 2011 04:01:49 -0000
Message-ID: <4EDC3A53.8060203@necom830.hpcl.titech.ac.jp>
Date: Mon, 05 Dec 2011 12:28:19 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com><4EDA13B7.9090402@necom830.hpcl.titech.ac.jp><6DA3E757-414F-41C3-A8A2-FA89EC7F6C8C@nominum.com><4EDACEE4.5080905@necom830.hpcl.titech.ac.jp><60C9046A-F5E9-4B34-9056-48EA34788E81@nominum.com><4EDB30FC.1020204@necom830.hpcl.titech.ac.jp><5B6B2B64C9FE2A489045EEEADDAFF2C3037785E5@XMB-RCD-109.cisco.com> <4EDBDA5C.2080103@necom830.hpcl.titech.ac.jp> <5B6B2B64C9FE2A489045EEEADDAFF2C303778615@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C303778615@XMB-RCD-109.cisco.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org
Subject: [dhcwg] No default routers (was Re: To wait for RA or not to wait?)
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: Mon, 05 Dec 2011 03:29:05 -0000

Hemant Singh (shemant) wrote:

>> The fundamental problem is in source address selection, against
>> which default routers and longest matches are assured to be
>> "incomplete" and "incorrect" by the end to end argument:

> If a host has multiple default routers,

I'm saying to have not multiple but *NO* default routers.

> then issue MSR from the routers
> to the host as specified in RFC 4191.

Having multiple "incomplete" and "incorrect" entities
makes the matter worse.

> Just does not make sense to run routing between a router and a host.

What does not make sense is to have a default router even
though there are multiple source addresses, in which case
the only reasonable thing to do is to let an end system
maintain a routing table with an appropriate source address
and the next hop router for each routing table entry.

					Masataka Ohta



From Carl.Wuyts@technicolor.com  Sun Dec  4 22:51:16 2011
Return-Path: <Carl.Wuyts@technicolor.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 1A21321F8B7E for <dhcwg@ietfa.amsl.com>; Sun,  4 Dec 2011 22:51:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.086
X-Spam-Level: 
X-Spam-Status: No, score=-5.086 tagged_above=-999 required=5 tests=[AWL=-0.908, BAYES_00=-2.599, EXTRA_MPART_TYPE=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_GIF_ATTACH=1.42]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rzJviBd0AuUW for <dhcwg@ietfa.amsl.com>; Sun,  4 Dec 2011 22:51:14 -0800 (PST)
Received: from na3sys009aog124.obsmtp.com (na3sys009aog124.obsmtp.com [74.125.149.151]) by ietfa.amsl.com (Postfix) with ESMTP id 1AC6621F8B7B for <dhcwg@ietf.org>; Sun,  4 Dec 2011 22:51:11 -0800 (PST)
Received: from MOPESEDGE01.eu.thmulti.com ([129.35.174.203]) (using TLSv1) by na3sys009aob124.postini.com ([74.125.148.12]) with SMTP ID DSNKTtxpzCkyOsdYlXHEll/Oky8YfS4vZxmz@postini.com; Sun, 04 Dec 2011 22:51:13 PST
Received: from MOPESMAILHC01.eu.thmulti.com (141.11.100.25) by mail3.technicolor.com (141.11.253.22) with Microsoft SMTP Server (TLS) id 8.3.192.1; Mon, 5 Dec 2011 07:50:05 +0100
Received: from MOPESMBX01.eu.thmulti.com ([169.254.155.121]) by MOPESMAILHC01.eu.thmulti.com ([141.11.100.25]) with mapi; Mon, 5 Dec 2011 07:50:06 +0100
From: Wuyts Carl <Carl.Wuyts@technicolor.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Date: Mon, 5 Dec 2011 07:50:05 +0100
Thread-Topic: To wait for RA or not to wait?
Thread-Index: AQHMsRmaAFDsJ61sskWNi8UGYH6hlZXI4trAgACUOoCAA1oVwA==
Message-ID: <867F4B6A1672E541A94676D556793ACD0CB42FDB00@MOPESMBX01.eu.thmulti.com>
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com> <867F4B6A1672E541A94676D556793ACD0CB42FDABE@MOPESMBX01.eu.thmulti.com> <BEA0EE13-9223-4D60-837C-AEAF74FAFD6E@nominum.com>
In-Reply-To: <BEA0EE13-9223-4D60-837C-AEAF74FAFD6E@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/related; boundary="_006_867F4B6A1672E541A94676D556793ACD0CB42FDB00MOPESMBX01eut_"; type="multipart/alternative"
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Mon, 05 Dec 2011 06:51:16 -0000

--_006_867F4B6A1672E541A94676D556793ACD0CB42FDB00MOPESMBX01eut_
Content-Type: multipart/alternative;
	boundary="_000_867F4B6A1672E541A94676D556793ACD0CB42FDB00MOPESMBX01eut_"

--_000_867F4B6A1672E541A94676D556793ACD0CB42FDB00MOPESMBX01eut_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

So, what if I get my routes over DHCPv6 then ?  It'll be available at some =
time, no ??
There's no default route to inject, not manual, not by RA ??  Re-define the=
 document again, and yet again ask the CPE vendors to changes their impleme=
ntation ?

Carl Wuyts
GCD System Architect Networking
Connect Division

carl.wuyts@technicolor.com<mailto:carl.wuyts@technicolor.com>
tel.: +32 3 443 65 90
[cid:image001.gif@01CCB322.80B55850]<http://twitter.com/#!/TechnicolorIPv6>
[cid:image002.gif@01CCB322.80B55850]<http://www.technicolor.com/>
Prins Boudewijnlaan 47  -  2650 Edegem  -  Belgium

Technicolor Delivery Technologies Belgium NV
Registered office (maatschappelijke zetel): Prins Boudewijnlaan 47, 2650 Ed=
egem, Belgium
Company registration number (ondernemingsnummer): 0428837295 - RPR Antwerpe=
n
[cid:image003.gif@01CCB322.80B55850]

Help preserve the color of our world - Think before you print.





From: Ted Lemon [mailto:Ted.Lemon@nominum.com]
Sent: vrijdag 2 december 2011 20:36
To: Wuyts Carl
Cc: dhc WG
Subject: Re: To wait for RA or not to wait?

On Dec 2, 2011, at 1:47 PM, Wuyts Carl wrote:
You can perfectly add a default route statically in case you want to.  Diff=
erent customers have different ideas about it, some prefer no RAs, so one h=
as to be able to cope with it.

This is equivalent to saying that different customers have different ideas =
about whether they want their network to work.   No they can't add a defaul=
t route statically-that's absurd.   If they were going to statically config=
ure the host, why bother with DHCP at all?

Moreover, there's no reason to "couple" RA to DHCP, they are independent pr=
otocols, so should be able to work independent.  It's fine to wait for it i=
f you prefer, but one has to have the option to not do this.


They are coupled.   They do not work independently.   Whether that was the =
right architecture choice or not, the issue has been decided.


--_000_867F4B6A1672E541A94676D556793ACD0CB42FDB00MOPESMBX01eut_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#def=
ault#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Trebuchet MS";
	panose-1:2 11 6 3 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>So, what =
if I get my routes over DHCPv6 then ?&nbsp; It&#8217;ll be available at som=
e time, no ??<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>There&#8217;=
s no default route to inject, not manual, not by RA ??&nbsp; Re-define the =
document again, and yet again ask the CPE vendors to changes their implemen=
tation ?<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size=
:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p>=
</span></p><div><table class=3DMsoNormalTable border=3D0 cellspacing=3D0 ce=
llpadding=3D0><tr><td valign=3Dtop style=3D'padding:1.5pt 0cm 1.5pt 0cm'><t=
able class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0><tr>=
<td valign=3Dtop style=3D'border:none;border-top:solid #9D9FA2 1.0pt;paddin=
g:1.5pt 0cm 1.5pt 0cm'><p class=3DMsoNormal><b><span style=3D'font-size:10.=
0pt;font-family:"Trebuchet MS","sans-serif";color:#1F497D'>Carl Wuyts<o:p><=
/o:p></span></b></p><p class=3DMsoNormal><span style=3D'font-size:9.0pt;fon=
t-family:"Trebuchet MS","sans-serif";color:#1F497D'>GCD System Architect Ne=
tworking<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size=
:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#1F497D;text-transfor=
m:uppercase'>Connect Division</span><span style=3D'font-size:10.0pt;font-fa=
mily:"Trebuchet MS","sans-serif";color:#1F497D'><o:p></o:p></span></p></td>=
</tr><tr><td valign=3Dtop style=3D'padding:1.5pt 0cm 1.5pt 0cm'><p class=3D=
MsoNormal><span style=3D'font-size:9.0pt;font-family:"Trebuchet MS","sans-s=
erif";color:#1F497D'><a href=3D"mailto:carl.wuyts@technicolor.com"><span st=
yle=3D'color:#662D91'>carl.wuyts@technicolor.com</span></a></span><span sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o=
:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:9.0pt;fon=
t-family:"Trebuchet MS","sans-serif";color:#1F497D'>tel.: +32 3 443 65 90<o=
:p></o:p></span></p><p class=3DMsoNormal><a href=3D"http://twitter.com/#!/T=
echnicolorIPv6"><span style=3D'font-size:9.0pt;font-family:"Trebuchet MS","=
sans-serif";color:blue;text-decoration:none'><img border=3D0 width=3D24 hei=
ght=3D24 id=3D"Picture_x0020_1" src=3D"cid:image001.gif@01CCB322.80B55850" =
alt=3Dtwitter></span></a><span style=3D'font-size:9.0pt;font-family:"Trebuc=
het MS","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNor=
mal><a href=3D"http://www.technicolor.com/" target=3D"_blank"><span style=
=3D'font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#6A9D17;=
text-decoration:none'><img border=3D0 width=3D114 height=3D69 id=3D"Picture=
_x0020_2" src=3D"cid:image002.gif@01CCB322.80B55850" alt=3D"Visit technicol=
or.com"></span></a><span style=3D'font-size:10.0pt;font-family:"Trebuchet M=
S","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNormal><=
span style=3D'font-size:9.0pt;font-family:"Trebuchet MS","sans-serif";color=
:#1F497D'>Prins Boudewijnlaan 47&nbsp;&nbsp;-&nbsp;&nbsp;2650 Edegem&nbsp;&=
nbsp;-&nbsp;&nbsp;Belgium<o:p></o:p></span></p></td></tr><tr><td valign=3Dt=
op style=3D'border:none;border-top:solid #9D9FA2 1.0pt;padding:1.5pt 0cm 1.=
5pt 0cm'><p class=3DMsoNormal><b><span lang=3DNL-BE style=3D'font-size:7.0p=
t;font-family:"Arial","sans-serif";color:#9D9FA2'>Technicolor Delivery Tech=
nologies Belgium NV</span></b><b><span lang=3DNL-BE style=3D'font-size:7.0p=
t;font-family:"Arial","sans-serif";color:#9D9FA2'><o:p></o:p></span></b></p=
><p class=3DMsoNormal><b><span lang=3DNL-BE style=3D'font-size:7.0pt;font-f=
amily:"Arial","sans-serif";color:#9D9FA2'>Registered office (maatschappelij=
ke zetel): Prins Boudewijnlaan 47, 2650 Edegem, Belgium<o:p></o:p></span></=
b></p><p class=3DMsoNormal><b><span style=3D'font-size:7.0pt;font-family:"A=
rial","sans-serif";color:#9D9FA2'>Company registration number (ondernemings=
nummer): 0428837295 - RPR Antwerpen<o:p></o:p></span></b></p><table class=
=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0><tr><td valign=
=3Dtop style=3D'padding:1.5pt 0cm 1.5pt 0cm'><p class=3DMsoNormal><span sty=
le=3D'font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#1F497=
D'><img border=3D0 width=3D28 height=3D33 id=3D"Picture_x0020_3" src=3D"cid=
:image003.gif@01CCB322.80B55850" alt=3DEco><o:p></o:p></span></p></td><td s=
tyle=3D'padding:1.5pt 0cm 1.5pt 4.5pt'><p class=3DMsoNormal><i><span style=
=3D'font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:#9D9FA2'=
>Help preserve the color of our world - Think before you print.<o:p></o:p><=
/span></i></p></td></tr></table></td></tr></table></td></tr></table><p clas=
s=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-s=
erif";color:#1F497D'><o:p>&nbsp;</o:p></span></p></div><p class=3DMsoNormal=
><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#=
1F497D'><o:p>&nbsp;</o:p></span></p><div><div style=3D'border:none;border-t=
op:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><=
span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</sp=
an></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Ted Lemon [mailto:Ted.Lemon@nominum.com] <br><b>Sent:</b> vrijdag 2 decembe=
r 2011 20:36<br><b>To:</b> Wuyts Carl<br><b>Cc:</b> dhc WG<br><b>Subject:</=
b> Re: To wait for RA or not to wait?<o:p></o:p></span></p></div></div><p c=
lass=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On Dec=
 2, 2011, at 1:47 PM, Wuyts Carl wrote:<o:p></o:p></p></div><blockquote sty=
le=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p class=3DMsoNormal><span clas=
s=3Dapple-style-span><span style=3D'font-size:13.5pt;font-family:"Helvetica=
","sans-serif"'>You can perfectly add a default route statically in case yo=
u want to. &nbsp;Different customers have different ideas about it, some pr=
efer no RAs, so one has to be able to cope with it.</span></span><o:p></o:p=
></p></blockquote><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div=
><p class=3DMsoNormal>This is equivalent to saying that different customers=
 have different ideas about whether they want their network to work. &nbsp;=
 No they can't add a default route statically&#8212;that's absurd. &nbsp; I=
f they were going to statically configure the host, why bother with DHCP at=
 all?<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></=
div><blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p class=3DM=
soNormal><span class=3Dapple-style-span><span style=3D'font-size:13.5pt;fon=
t-family:"Helvetica","sans-serif"'>Moreover, there's no reason to &quot;cou=
ple&quot; RA to DHCP, they are independent protocols, so should be able to =
work independent. &nbsp;It's fine to wait for it if you prefer, but one has=
 to have the option to not do this.</span></span><span style=3D'font-size:1=
3.5pt;font-family:"Helvetica","sans-serif"'><br><br></span><o:p></o:p></p><=
/blockquote></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=
=3DMsoNormal>They are coupled. &nbsp; They do not work independently. &nbsp=
; Whether that was the right architecture choice or not, the issue has been=
 decided.<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></=
p></div></div></body></html>=

--_000_867F4B6A1672E541A94676D556793ACD0CB42FDB00MOPESMBX01eut_--

--_006_867F4B6A1672E541A94676D556793ACD0CB42FDB00MOPESMBX01eut_
Content-Type: image/gif; name="image001.gif"
Content-Description: image001.gif
Content-Disposition: inline; filename="image001.gif"; size=1351;
	creation-date="Mon, 05 Dec 2011 06:50:06 GMT";
	modification-date="Mon, 05 Dec 2011 06:50:06 GMT"
Content-ID: <image001.gif@01CCB322.80B55850>
Content-Transfer-Encoding: base64

R0lGODlhGAAYAPcAAAAAAP///1Sfum/L64bW8o7h/ofU74fT7pHb9pfa8u75/VbD5VzG6FvF5l3G
513F5l/G51/F5mHH52PH6GPI6GPI52TH6GXJ6GbI6GnK6mjJ6WjK6WzL6m/M63HN6nPN6nTN63fR
7XnR7XTI5FeVqnnN537T7n7R7H/T7X3O6Y3f+4jV73m903/E2oDE2pTf+ZPc9JTa8Zfa8aDd8LDj
9MXr9+z5/er3+/r9/imy1yyx1S202S2z1zK43TW63jW32zS22Ta53Te73za32zq84Dm53Du73j2/
4j2+4T283z273kHB5D++4EHA4kG/4UPA40K/4UTB5EbD5UbB40rJ7EjD5ErG6EnE5knE5Ua720rE
5kvG507J607I6U3G50/K60u+3U2/4U7A4k2/3lLI6E/A31XN7lHC4VnP8FfL61PD4lXD5FXF41vR
8VfG5VO92lrJ51a+21i/21/O7F7L6VnB3VzE4mHN6l/H5V3D30+lvWDH41/E4GDF4WLH42rL6GvP
6l+2znLZ9W7Q62C1zGO50HXZ9HTY83ba9XXX8mW70nLO6nHN6We803rd+HXV73zf+mm91HXS62vA
12GpvWavw2ixxVmWp2qxxYDW7X3Q52yzxm+2yW60x4HS6HC2yXG3ynzD2I7a75Xb7pvh9F+HkqTg
8ajg76ff7qri8bPo97fm9Ljm9MXw/Mfw/NDz/dDx+tbx+dz0++H1++f5/uv5/Six1S+22jG01zK1
2EXD5E/M7U7H50yvyWPY91zJ5WjZ92za927b+HHY82G4z3Xd+FurwHXa9Xfc93ne+F+rv37h+2u/
1YDi/H7c9YHh+YLh+YXi+mqyxWuzxork+ovj+o3l+3K4ypXn+12PnJrm+qXp+63j8cLx/M/0/ef4
/Jfp+57q+6Xt/Kjv/avv/a3v/a7w/bPw/bzz/uP6/+z7/vP9/7fz/r30/sD0/sX1/sn2/tT4/9L2
/d/6/+X7/+b7/+r8/+v7/sz3/tr5/ub8/+39//v///3///7//////yH5BAEAAP8ALAAAAAAYABgA
AAj/AP8JHEiwoMGCAgggOGCg4YqHEB8aOPCCAEESKmR84MABg0cOHUKGHDCAA4gEBQaOiIHBwgQO
pmrQEEEhg80NGnJewACDhcAUJyBMwBArgL8ACkxc2MBUg8cLEEy0+PkhQoMZAerNmxegBoMLFChc
AFsBQggXAkswerBgVYB8+eLtu7GorgcKDipIcBBi6r8SHtiyCoAPH7x6AXAoxjELRYO9IUIJlGMn
jBi37zLHo2fPXj19/hT8WRMGDzGBb7LosIUqADp07WC7c9eOHbwAmnjwGBNIYBwwuHK0NleOOLnj
5MaxC+BpR64zp//JGQNkx6kA4rKXO8ede7oAe378/1BTSGCdMkNunfIXLhw4eQH6yU88KoiSImzK
/8tzpkiPVP1gg4013gRgYGKmEMEEE0a4oYhAeahhhA/c8FMNNdF0s4466tyzTgCrOAFFEnA0IhAf
bCQhhCkBVPMMNDDC+GI3AUiCBBNwRCJQH24wgUQmAWwjTDJEFllMNAGIcoQTdDAjkB9uODGFFLHw
o00wwGSZpS/bBJDJEk80+eQvTVQhxR2zBECLK6202c0rAchCxhVR3DGJb5I0gYUXVqRBCiy1BFqL
Dd+oMocVW+jyCCEC6ZEIIFps0cUXVOyCRhuYomEGFVx0wcsghlwyUC/DOHPIMcg4AskyzbS6DCSO
ICSDiDOCGFNQNspUYgkmm3TCCSjXgPJJJ9NIYwklpRyk7LIDBQQAOw==

--_006_867F4B6A1672E541A94676D556793ACD0CB42FDB00MOPESMBX01eut_
Content-Type: image/gif; name="image002.gif"
Content-Description: image002.gif
Content-Disposition: inline; filename="image002.gif"; size=1834;
	creation-date="Mon, 05 Dec 2011 06:50:06 GMT";
	modification-date="Mon, 05 Dec 2011 06:50:06 GMT"
Content-ID: <image002.gif@01CCB322.80B55850>
Content-Transfer-Encoding: base64

R0lGODlhcgBFAOZ/AEGueqipqmgxkACLS4ORyPb294DFpZrMVqvi+sXr2Ie3laLXtnRHnLQlZO3J
2M+pxP7pJvqtgePqmqOIvYLKnACP1fewoXa65/vCov71sdqRnc6OpPvrlcU/benvs7qmzpzR8P/n
rc7imtLntMkhU/V7Hf/yl+fZ6f3HipjL7b+MraKs1h+WXIrU9fNrPv/dkaTIrpQpd/JlIr8kXv/o
ALa3uO0bLwCmUQC68pKSlf/CDgxNosvbKtvb3IzGP8nJyoiJjPaWgH+Ag3Z3euTk5Y3Y+MTfm+3t
7r/AwZubnvBSJQCZ3NLS0//eAwN+yE84la9fmdjkX//RSiPB855BhP/ILiCvY9HeRvLkCvmykSld
q/aNl4Dd+cPT6O85Q2m+Q6zRONnM5OPx0PR3OR2Z2eOttkCr4Lfbm//uQPWMWbeLscPbysbs/OP1
/ZeLwPaLN9blff/iEvXlByCi3nzB69eqvN7r4uzysHfDWSCKzu+Uh8R4pR6j4IVfqm1ucf///yH5
BAEAAH8ALAAAAAByAEUAAAf/gH+Cg4SFhoeIiYqLjI2Oj5CRkpOUlZaXmJmam5ydnp+goaKjpKWm
p6ipqqusra6vsLGys7S1tqF+Oat+freMubu9vorAkkhIlryqBQWXxZBEvD2VyqhEQtPJupJJScnC
pzV+2dTbqdWnSX4BNTWDR+01RIUFSO0/zX/AP+1Mg/x/iLRDku9PO0JH7NXA906hv0Ho/vSId2TQ
xB4Jf1gKwKujoB8deWn8OCTkkIp+gAAJGUBQjnUhgUAEB9Lkx5C58lUr8DLkSHE5Spqb1IMjkh7T
evgZ4o9JyYrR/Mib2FKfHyH4kPBq1rPGkR4lH1ZjsvQH0gDIlA7RSGSlN6uC/zgCmfcjrEFeQuRd
EkeO48g/IN2pQ2boasGV014+/MPRHdw/QsYZUve3wFO4R5YWBOlN3FtMfAetBJKj9EpdEQk9+/My
sWRB4hxXS3koNcdpypRWnXnXMejXf4SWHt4yNcShrVkDjy1o9lDehELnXldIGfNMoV0CJxSZnGrk
kpPDltpc2FZDK+eJlqwsmsx3V3trEvdXK5CKgvKJu59fLHjX5FxXjVz5fHUXEPmAJER5gkQ2UgHq
uHMdJiANkcNIK+WSQ2TraaiZPv8pFyB5jxWwkoUvLWjiVUlkmE01RJQERACRISifJhxR90cBNUTG
YkE1ZAgEYTnsxlgO8wSA5P8/F7pkDo8+AvFgj7wkoR5r5hChzlU1JNjkMGCGKeaYZJZp5pmqsIHA
mmyCkMKbcK4g55wrfGDnnR88oOeedZTh558WBCqoBRgUaigGISSqaAgZNOroHR5EKqkHI1Rq6QKY
ZroADJx2CoMdjxSAQBGkktoCHRekqioBrLZKgBsTxCqrGirUaqsGuOaqgR5B9OprBMAGG8ELxBb7
ggnIJmuCBMw2K4EIRkQb7RkUVGstBQpkq60CazTSRqmlnqrqqq6yCqusstqqrq65+uqusMGiYCyx
HCiLLAfONguttEZQe22122oLQ0GHsAGuqeOSW+656E6grq0bsIuru7/CG4H/vPMea++y+TK7r7T+
/huwtqAiMsXJKE/BBxkst5yHFjDHrAUDNNdMMxU450xFBzz3zLMXQAfthQtjFG30G1UkrXQVEDTt
dNNXRC31FWAcYPXVeFih9dZWsOD11ywAkAgOZJeNwxIVpK22Ezu07fYOTwgg99wCxGD33TE0MMPe
fJNgw9+A26CEDIQXXoIOiCeuQxM0NO44FjxELjkPYPhg+eVf3KD55jcM4PnnA4iNiNllo6122my/
3XbcdMuN9916872334H/PXjhhB+uOOKMO9445JNHXvnllmfOueagfy76IaSTbfrpqavOeuuv2x27
7LTXfjvuuu/eu+/ABz88//HGH5+858sb0vzZp6Ou+uqtu1799X3Xbjvuue/Ou++/By888cU7HvLO
l75CrO95a3sf3OJXt/nJbnb2Exz+ZNA9xX3vcf6jHAB9UD7OnS90Y2seAt33vunRrXp5e+AMshe4
7RlOf4vjHw3CN7nxYU6AnSNgCEk3wgpE720mnBsK6QdB+7kwf/q7YP/8BwcxOPGJC8DhBwtIiAO2
z4cKDKL8XkfEFUbwiBSEoRJpIIcomPGMUbiDIRIgRR2OToRXrEAX5kjHLvSBgUNUIQsBB8YSSOGP
gJRCHGRIA0ewUYBTTAQXFslILswhjoe4Y/zy+EASbOGSmNyCCyYog0OggYeQhgSAKEcJABa40RFm
gKQhThCGVrryAZR84CHSwElPgrISADhlI1J5RUc4IJaym2UtSZHL5FFREbxsny9RuAcHOPOZDjgE
BrJAzWpmoRQLMIA2t7kASCTzdI44ARTGSU4oPABN6EynOtfJzna6853wjKc850nPetrznvjMpz73
yc9++tMUgQAAOw==

--_006_867F4B6A1672E541A94676D556793ACD0CB42FDB00MOPESMBX01eut_
Content-Type: image/gif; name="image003.gif"
Content-Description: image003.gif
Content-Disposition: inline; filename="image003.gif"; size=493;
	creation-date="Mon, 05 Dec 2011 06:50:06 GMT";
	modification-date="Mon, 05 Dec 2011 06:50:06 GMT"
Content-ID: <image003.gif@01CCB322.80B55850>
Content-Transfer-Encoding: base64

R0lGODlhHAAhAMQAALHNVVqXGZu+IqbFNv79/ury0pK4H2SdaJzAJNjlq/3++vL34srdiSl5Mfj7
8OHrvDmDE5u+Kb3VbtDgm5jCnJC2IqDBJHqqHoazHsfYxcfco+/58f7///7+/v///f///yH5BAAA
AAAALAAAAAAcACEAAAX/4CeOZGmeaKqubOumXSfKL0rT9RiTe65/nl0vxxE1KB3Ph6b8KGYjT/Pn
ORwIHmy0FEQFCZRG5yldJnEqD6ezaWQIHMJDApAwCthgF8hbEqwEBQARAoWFEgskQWgiChwFDRoD
hpQCA3hLQGhxSWABFpQIlAMPT2NoeTIJEBigooavlzJDS0UdHAkBEAivAoSjDklTQAROuBYQn7+/
lBJJS01SUgoJoskWvaECCWUiHEEKtw+8BtegvoWxiYtqSmsLhBblEALn2hLDH3HTAIXYuhfqVeLF
TZ8SR3oSULKAQVeAChYi8kJwCUg4BcVkOOiXDgHDACAvXMBQoWQEOw6iahwsMCmdAI8CKoiciUEA
gAJ8aBC4xfKlz3QRsVGcoICMJidKOjhgMKCXqKcAJqSMIkwEuw8OHjCQwNVOggJPvqm4ZUJGuw47
lajlA0Sat28xyJZV9APasGEcvknBkU9TjJ1WrTZZE9hHihAAOw==

--_006_867F4B6A1672E541A94676D556793ACD0CB42FDB00MOPESMBX01eut_--

From mohta@necom830.hpcl.titech.ac.jp  Mon Dec  5 01:24:58 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 B5B9221F8AE9 for <dhcwg@ietfa.amsl.com>; Mon,  5 Dec 2011 01:24:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.014
X-Spam-Level: 
X-Spam-Status: No, score=0.014 tagged_above=-999 required=5 tests=[AWL=0.104,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sc9VrExQtIOL for <dhcwg@ietfa.amsl.com>; Mon,  5 Dec 2011 01:24:58 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id E442C21F845D for <dhcwg@ietf.org>; Mon,  5 Dec 2011 01:24:57 -0800 (PST)
Received: (qmail 5211 invoked from network); 5 Dec 2011 09:58:08 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 5 Dec 2011 09:58:08 -0000
Message-ID: <4EDC8DC2.8030408@necom830.hpcl.titech.ac.jp>
Date: Mon, 05 Dec 2011 18:24:18 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com><4EDA13B7.9090402@necom830.hpcl.titech.ac.jp><6DA3E757-414F-41C3-A8A2-FA89EC7F6C8C@nominum.com><4EDACEE4.5080905@necom830.hpcl.titech.ac.jp><60C9046A-F5E9-4B34-9056-48EA34788E81@nominum.com> <4EDB30FC.1020204@necom830.hpcl.titech.ac.jp> <5B6B2B64C9FE2A489045EEEADDAFF2C303778634@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C303778634@XMB-RCD-109.cisco.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Mon, 05 Dec 2011 09:24:58 -0000

Hemant Singh (shemant) wrote:

> What is this DAD latency?  Is it the roughly two seconds a node waits
> before the node deems DAD has passed for the node's IPv6 address?

Yes. But environment I'm assuming is a bit complicated, because
the purpose of 802.11ai is to minimize the number of 802.11
frames (which may carry multiple information) exchanged,
hopefully within short period of time, before establishing
connection. Note also that it is just my idea and
nothing is determined by 802.11ai.

It is possible to set up a link with all the necessary information
such as address, DNS server, security, route) with just a three
way handshake, one of which is a beacon frame.

> Further, what had DAD latency got to do with waiting for the RA?   Soon
> as a node is enabled for IPv6, the node creates an IPv6 link-local
> address and then issues a DAD for the link-local.

That's not applicable to 802.11, because the link is
not always enabled.

And, I don't think link-local address with DAD, which requires
delay which means separate frames, is acceptable. Instead,
some "addresses determined through other mechanisms", which
may actually be identical to link-local address, may be used
without DAD.

> But while the DAD
> procedure is going on, the node is likely to receive an RA.

There is no DAD expected, so far.

And, there is another delay caused by RA minimum interval
of 3 seconds (unless the router is supporting mobility
(RFC3775)), which is partly why RA-initiated DHCP is no good.

Note that RA may be piggy backed in 802.11 beacon, to reduce
frame exchanges. However, it will almost always violate the
minimum interval requirement unless a base station is a
mobility supporting router.

> Frankly the node can wait for the RA which gives the node a
> default router until the node has to send a unicast packet out to the
> network.

I don't think default router useful with multiple source
addresses (save link local ones). For 802.11ai, it can
be assumed that there is only one source address and
default router information should be made available
through DHCPv6 or directly by a field of 802.11ai.

						Masataka Ohta

From shemant@cisco.com  Mon Dec  5 06:04:22 2011
Return-Path: <shemant@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 CDC4021F8BB8 for <dhcwg@ietfa.amsl.com>; Mon,  5 Dec 2011 06:04:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.247
X-Spam-Level: 
X-Spam-Status: No, score=-6.247 tagged_above=-999 required=5 tests=[AWL=-0.249, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QHjITWCZDNCz for <dhcwg@ietfa.amsl.com>; Mon,  5 Dec 2011 06:04:21 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 27E6221F8BB7 for <dhcwg@ietf.org>; Mon,  5 Dec 2011 06:04:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=7266; q=dns/txt; s=iport; t=1323093861; x=1324303461; h=mime-version:subject:date:message-id:in-reply-to: references:from:to:cc; bh=1mpfUg0LC2Q3MW5iOi5pBjui+CvftygoSGH5jToL8Rk=; b=jPGl4DU501S5vxCGU39/MkeC17BH5UeshsfLcEkEOYJNkE3xhWXHtqQG 9vNo89w8uxnoF9dShvbazTsWobfBJjQWD+xhkj6pkHKTwDQVMamMs2maa CNETLjnbbr3r6eKluBJhG+WtoYDpNHKjY/Br3yxIz+GJbaO7Z8xNIbI98 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsgAAInO3E6tJV2d/2dsb2JhbABEgk2XRY5UAYFVgQWBcgEBAQQSAQkRA0kQAgEIEQQBAQsGFwEGAUUJCAIEARIIGp5pAZ4jij5jBIgtnmY
X-IronPort-AV: E=Sophos;i="4.71,299,1320624000"; d="scan'208,217";a="41204159"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-5.cisco.com with ESMTP; 05 Dec 2011 14:04:20 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core-6.cisco.com (8.14.3/8.14.3) with ESMTP id pB5E4KIx030906;  Mon, 5 Dec 2011 14:04:20 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 5 Dec 2011 08:04:20 -0600
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCB356.C80BD2A7"
Date: Mon, 5 Dec 2011 08:04:19 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C30377869C@XMB-RCD-109.cisco.com>
In-Reply-To: <867F4B6A1672E541A94676D556793ACD0CB42FDB00@MOPESMBX01.eu.thmulti.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] To wait for RA or not to wait?
Thread-Index: AQHMsRmaAFDsJ61sskWNi8UGYH6hlZXI4trAgACUOoCAA1oVwIAAdWrw
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com><867F4B6A1672E541A94676D556793ACD0CB42FDABE@MOPESMBX01.eu.thmulti.com><BEA0EE13-9223-4D60-837C-AEAF74FAFD6E@nominum.com> <867F4B6A1672E541A94676D556793ACD0CB42FDB00@MOPESMBX01.eu.thmulti.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Wuyts Carl" <Carl.Wuyts@technicolor.com>, "Ted Lemon" <Ted.Lemon@nominum.com>
X-OriginalArrivalTime: 05 Dec 2011 14:04:20.0393 (UTC) FILETIME=[C8C6C190:01CCB356]
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Mon, 05 Dec 2011 14:04:22 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CCB356.C80BD2A7
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Actually, I, Wes Beebee, and some other folks have commented in v6ops
for using DHCPv6 to carry the default route information.  What happens
when the RA and DHCPv6 have conflicting information and which
information wins?  That is why I said in my email from Sunday that the
DHCPv6 default route option is nowhere close to consensus.   I still
prefer the existing means IPv6 has to signal a default router to a host
in the IPv6 ND RA.  Further if I recall correctly, the reason the
question (wait for RA or not) came up is because a DHCPv6 server was
getting bogged down with one client sending too many SOLICITs when the
SP was not ready to serve DHCPv6.    To the server storm problem we said
use the Ralph Droms' new draft that changes the SOL_MAX_RT.   So do we
have to discuss the "To wait for RA or not to wait" to initiate DHCPv6?
There is one screw case when a DHC client initiates DHCPv6, completes
DHCPv6, but does not receive any RA, what does the client do for default
route or default router?  In such a case, I don't think we can do
anything but require manual intervention.  =20

=20

Hemant

=20

From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Wuyts Carl
Sent: Monday, December 05, 2011 1:50 AM
To: Ted Lemon
Cc: dhc WG
Subject: Re: [dhcwg] To wait for RA or not to wait?

=20

So, what if I get my routes over DHCPv6 then ?  It'll be available at
some time, no ??

There's no default route to inject, not manual, not by RA ??  Re-define
the document again, and yet again ask the CPE vendors to changes their
implementation ?

=20


------_=_NextPart_001_01CCB356.C80BD2A7
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Courier =
New","serif";color:#1F497D'>Actually, I, Wes Beebee, and some other =
folks have commented in v6ops for using DHCPv6 to carry the default =
route information.&nbsp; What happens when the RA and DHCPv6 have =
conflicting information and which information wins?&nbsp; That is why I =
said in my email from Sunday that the DHCPv6 default route option is =
nowhere close to consensus.&nbsp;&nbsp; I still prefer the existing =
means IPv6 has to signal a default router to a host in the IPv6 ND =
RA.&nbsp; Further if I recall correctly, the reason the question (wait =
for RA or not) came up is because a DHCPv6 server was getting bogged =
down with one client sending too many SOLICITs when the SP was not ready =
to serve DHCPv6.&nbsp; &nbsp;&nbsp;To the server storm problem we said =
use the Ralph Droms&#8217; new draft that changes the =
SOL_MAX_RT.&nbsp;&nbsp; So do we have to discuss the &#8220;To wait for =
RA or not to wait&#8221; to initiate DHCPv6?&nbsp; There is one screw =
case when a DHC client initiates DHCPv6, completes DHCPv6, but does not =
receive any RA, what does the client do for default route or default =
router?&nbsp; In such a case, I don&#8217;t think we can do anything but =
require manual intervention.&nbsp;&nbsp; <o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Courier =
New","serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Courier =
New","serif";color:#1F497D'>Hemant<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] <b>On Behalf Of =
</b>Wuyts Carl<br><b>Sent:</b> Monday, December 05, 2011 1:50 =
AM<br><b>To:</b> Ted Lemon<br><b>Cc:</b> dhc WG<br><b>Subject:</b> Re: =
[dhcwg] To wait for RA or not to =
wait?<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>So, what if I get my routes over DHCPv6 then ?&nbsp; It&#8217;ll be =
available at some time, no ??<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>There&#8217;s no default route to inject, not manual, not by RA =
??&nbsp; Re-define the document again, and yet again ask the CPE vendors =
to changes their implementation ?<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p></div></body></html>
------_=_NextPart_001_01CCB356.C80BD2A7--

From Ted.Lemon@nominum.com  Mon Dec  5 07:32:19 2011
Return-Path: <Ted.Lemon@nominum.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 2F34221F8BBC for <dhcwg@ietfa.amsl.com>; Mon,  5 Dec 2011 07:32:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.517
X-Spam-Level: 
X-Spam-Status: No, score=-106.517 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Al0J55kKNx2a for <dhcwg@ietfa.amsl.com>; Mon,  5 Dec 2011 07:32:18 -0800 (PST)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by ietfa.amsl.com (Postfix) with ESMTP id 522A821F8B54 for <dhcwg@ietf.org>; Mon,  5 Dec 2011 07:32:18 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKTtzj9nyNFzEFbKopLJ7jpqM2K4eE7ZOZ@postini.com; Mon, 05 Dec 2011 07:32:18 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 674501B8228 for <dhcwg@ietf.org>; Mon,  5 Dec 2011 07:32:06 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 30F9F190052; Mon,  5 Dec 2011 07:32:06 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.01.0339.001; Mon, 5 Dec 2011 07:32:06 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Thread-Topic: [dhcwg] No default routers (was Re: To wait for RA or not to wait?)
Thread-Index: AQHMsv4PjwCHVzQ3QUOmjt/PlMSR6JXN5jQA
Date: Mon, 5 Dec 2011 15:32:05 +0000
Message-ID: <ECC2D256-6D9D-4373-A267-24234100E211@nominum.com>
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com><4EDA13B7.9090402@necom830.hpcl.titech.ac.jp><6DA3E757-414F-41C3-A8A2-FA89EC7F6C8C@nominum.com><4EDACEE4.5080905@necom830.hpcl.titech.ac.jp><60C9046A-F5E9-4B34-9056-48EA34788E81@nominum.com><4EDB30FC.1020204@necom830.hpcl.titech.ac.jp><5B6B2B64C9FE2A489045EEEADDAFF2C3037785E5@XMB-RCD-109.cisco.com> <4EDBDA5C.2080103@necom830.hpcl.titech.ac.jp> <5B6B2B64C9FE2A489045EEEADDAFF2C303778615@XMB-RCD-109.cisco.com> <4EDC3A53.8060203@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4EDC3A53.8060203@necom830.hpcl.titech.ac.jp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_ECC2D2566D9D4373A26724234100E211nominumcom_"
MIME-Version: 1.0
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Subject: Re: [dhcwg] No default routers (was Re: To wait for RA or not to wait?)
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: Mon, 05 Dec 2011 15:32:19 -0000

--_000_ECC2D2566D9D4373A26724234100E211nominumcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Dec 4, 2011, at 10:28 PM, Masataka Ohta wrote:
What does not make sense is to have a default router even
though there are multiple source addresses, in which case
the only reasonable thing to do is to let an end system
maintain a routing table with an appropriate source address
and the next hop router for each routing table entry.

Presumably you would still need what would effectively be a default route, =
though, right?   You'd just have more specific routes that were associated =
with various source addresses, and you'd want the host to use those routes =
and those source addresses for those prefixes.   Once the host is communica=
ting off the provider network, any globally valid source address ought to w=
ork.


--_000_ECC2D2566D9D4373A26724234100E211nominumcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <86889E9F9F4FF143B5062244BD97684D@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 4, 2011, at 10:28 PM, Masataka Ohta wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">What
 does not make sense is to have a default router even<br>
though there are multiple source addresses, in which case<br>
the only reasonable thing to do is to let an end system<br>
maintain a routing table with an appropriate source address<br>
and the next hop router for each routing table entry.</span></blockquote>
</div>
<br>
<div>Presumably you would still need what would effectively be a default ro=
ute, though, right? &nbsp; You'd just have more specific routes that were a=
ssociated with various source addresses, and you'd want the host to use tho=
se routes and those source addresses
 for those prefixes. &nbsp; Once the host is communicating off the provider=
 network, any globally valid source address ought to work.</div>
<div><br>
</div>
</body>
</html>

--_000_ECC2D2566D9D4373A26724234100E211nominumcom_--

From ot@cisco.com  Mon Dec  5 12:21:45 2011
Return-Path: <ot@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 A920411E8100 for <dhcwg@ietfa.amsl.com>; Mon,  5 Dec 2011 12:21:44 -0800 (PST)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xGw2T3T1RAhk for <dhcwg@ietfa.amsl.com>; Mon,  5 Dec 2011 12:21:43 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id D6F0711E80CD for <dhcwg@ietf.org>; Mon,  5 Dec 2011 12:21:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ot@cisco.com; l=3700; q=dns/txt; s=iport; t=1323116502; x=1324326102; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=qbUZQ6SPZzU9QVOQ8HWtYTQNsFQsKulhzlSFLr0iYbI=; b=Juy/a8I1l8OQVUnCA1V8fJ5j405PV2WwS84WuAO+nZHP2ykwea1QpPS4 ZHImR0/ZanEJtP4OYfQmiXRIiL+/NY83B6yxZb+xDEoKdK96O6a9hOpDs YvSUu411PUROuvHu5JtGvSGAa3O5NLa8ENWjsIWdktPKRSPZ/oOnUN7sl g=;
X-IronPort-AV: E=Sophos;i="4.71,300,1320624000"; d="scan'208";a="123086704"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 05 Dec 2011 20:21:42 +0000
Received: from dhcp-10-55-80-221.cisco.com (dhcp-10-55-80-221.cisco.com [10.55.80.221]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pB5KLfOd018955; Mon, 5 Dec 2011 20:21:41 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <ot@cisco.com>
In-Reply-To: <750BF7861EBBE048B3E648B4BB6E8F4F214FB748@crexc50p>
Date: Mon, 5 Dec 2011 21:21:40 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E46A2E66-ADF7-4BD5-9BD9-4A4D91C2E0F9@cisco.com>
References: <CAFBA0C7.1B8403%john_brzozowski@cable.comcast.com> <27630529-B761-4AE7-B82F-A6A343E203E0@cisco.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3036CE263@XMB-RCD-109.cisco.com> <C67D840A-9A3A-4FEC-BB1C-6EE975F9E126@gmail.com> <7CA7ACE6-8F84-4422-8891-CC5F0719BD69@cisco.com> <CAKD1Yr1oic-6Y3Sr_YMy_QLY=5cSQYyz8ybkBKJD25shtxmpXw@mail.gmail.com> <D2CACB00-BFF7-46EA-9239-620E6950DF7D@cisco.com> <A8D68D39-2D0D-449A-9894-9A95EB0116B9@gmail.com> <CAKD1Yr0_t6MJkFZe8gBd+JFxoVEiUDNdu-cfTSaRGcXE2m_1GA@mail.gmail.com> <A9A742D6-08FD-4871-99B8-DB173070E98A@nominum.com> <7E9CDB49-E846-4C03-B828-0DC59C1C4522@gmail.com> <2EF2D64D-74AD-4188-A676-0983A2312926@nominum.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778448@XMB-RCD-109.cisco.com> <5CE46365-718A-47D7-B40B-537BE3434E1A@nominum.com>, <C4BFAE25-3CE8-4348-9A9B-4E0485C055FF@cisco.com> <7EED226A-96AC-4FB9-8489-6E024F4900F7@nominum.com> <2E51BF04-F114-4510-9EE5-482A0EE46414@cisco.com> <750BF7861EBBE048B3E648B4BB6E8F4F214FB748@crexc50p>
To: "STARK, BARBARA H" <bs7652@att.com>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Mon, 05 Dec 2011 12:26:25 -0800
Cc: Ted Lemon <Ted.Lemon@nominum.com>, Ralph Droms <rdroms.ietf@gmail.com>, Joel Jaeggli <joelja@bogus.com>, dhc Chairs <dhc-chairs@tools.ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, dhc WG <dhcwg@ietf.org>, "<cpe-router@external.cisco.com>" <cpe-router@external.cisco.com>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [dhcwg] IMPORTANT - Re: Question on 6204bis
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: Mon, 05 Dec 2011 20:21:45 -0000

Barbara,

[please move this to the DHC working group (cc'ed)]

>> 1) Scoping of the NoAddrsAvail in the IA_* options. Dealt with in the
>> existing errata
>> 2) Change of SOLICIT timer (Dealt with in Ralph's draft)
>> 3) The other unclear problem area is around how to deal with IA_PD =
and
>> IA_NA:
>>   * Client requests both IA_NA and IA_PD in the same session, gets
>> only IA_PD.
>>      - Does it fork off a separate session for IA_NA and continues
>> sending SOLICITs for only the IA_NA?
>>      - Reset the DHCP client, and tries again?
>>      - Keeps single session, and continues to ask for IA_NA on next
>> RENEW?
>=20
> I agree with the statement made in 1. I agree that 2 is not a part of
> 6204bis and hope that Ralph's draft is successful.
>=20
> As for 3, I'm confused as to the problem.

CPE requests both IA_NA, IA_PD. the DHCP server has a policy to only =
give out e.g. IA_PD.
this also applies in the case where a client requests both IA_NA and =
IA_TA...
the DHCP specifications do not describe how a client should behave in =
this case.

cheers,
Ole

> We have an unnumbered model that is defined that describes the desired
> behavior for a device that gets only IA_PD (WAA-7, not to be confused
> with WPD-7). The device takes an address for itself from the delegated
> prefix, and puts it on some non-WAN interface (internal or LAN). It's
> happy. I would not expect it to continue sending SOLICITs or to reset
> the DHCPv6 client. I don't care if it asks for IA_NA on RENEW. The
> server should be able to handle it either way. As should the client. =
No
> need to specify "don't cares".
>=20
> We also have an exclusion to the unnumbered model, that requires =
devices
> to support the unnumbered model unless they are configured to require =
a
> global IPv6 address on the WAN (also in WAA-7). I've argued against
> providing more detail about this configured mode, and will continue to
> do so. It is up to the organizations (e.g., CableLabs) defining such a
> configured mode, to also define the desired behavior for what the CE
> router does when it doesn't get a global IPv6 address on the WAN
> interface. I don't see that 6204bis needs to address this. 6204bis can
> acknowledge the existence of configured modes, without needing to
> specify them. Implementing special configured modes is not a =
requirement
> of 6204 or 6204bis, which means the doc doesn't need to say how to do
> them.
>=20
> Note that a DHCPv6 server and the access network have to be able to
> handle devices that support the unnumbered model, if the provider
> intends to allow any non-SP-procured devices on that access network. I
> consider that reasonable. If the access network / DHCPv6 server hands
> out IA_PD but not IA_NA, I don't see why it should somehow not allow
> traffic from the delegated prefix to be properly routed. If it routes
> traffic from/to that prefix, then I don't see what the problem is. If =
it
> won't be routing that traffic to/from that prefix, then it shouldn't =
be
> handing out the prefix.=20
>=20
> The "unnumbered model" CE router will think it's up and running, per
> 6204 and 6204bis, and it's a naughty access network that lets it =
believe
> this, if this isn't true. The "configured" CE router will do whatever
> the configuration specifiers tell it to do. This "configured mode" =
isn't
> something dhc wg or 6204bis needs to deal with. There's nothing in any
> of the dhc RFCs or errata that prohibits existence of such a =
configured
> mode. Which means it's allowed, and other orgs are free to specify it
> and specify how it works in their devices.
> Barbara


From bs7652@att.com  Mon Dec  5 13:04:30 2011
Return-Path: <bs7652@att.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 050DE1F0C76 for <dhcwg@ietfa.amsl.com>; Mon,  5 Dec 2011 13:04:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.523
X-Spam-Level: 
X-Spam-Status: No, score=-106.523 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QXsbXFouhhas for <dhcwg@ietfa.amsl.com>; Mon,  5 Dec 2011 13:04:29 -0800 (PST)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by ietfa.amsl.com (Postfix) with ESMTP id 4D7991F0C5C for <dhcwg@ietf.org>; Mon,  5 Dec 2011 13:04:29 -0800 (PST)
X-Env-Sender: bs7652@att.com
X-Msg-Ref: server-13.tower-119.messagelabs.com!1323119067!4321292!1
X-Originating-IP: [144.160.20.146]
X-StarScan-Version: 6.4.2; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28906 invoked from network); 5 Dec 2011 21:04:27 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-13.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 5 Dec 2011 21:04:27 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.5) with ESMTP id pB5L2xGK019540; Mon, 5 Dec 2011 16:03:00 -0500
Received: from 01AL10015010627.AD.BLS.COM (sfldmibbcraeninet1-v2.pmtr.mwst.att.com [10.231.16.33]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.5) with ESMTP id pB5L2sJu019360; Mon, 5 Dec 2011 16:02:54 -0500
Received: from 01NC27689010627.AD.BLS.COM ([90.144.44.202]) by 01AL10015010627.AD.BLS.COM with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 5 Dec 2011 15:03:30 -0600
Received: from 01NC27689010650.AD.BLS.COM ([90.144.44.120]) by 01NC27689010627.AD.BLS.COM with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 5 Dec 2011 16:03:29 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 5 Dec 2011 16:04:19 -0500
Message-ID: <750BF7861EBBE048B3E648B4BB6E8F4F214FB832@crexc50p>
In-Reply-To: <E46A2E66-ADF7-4BD5-9BD9-4A4D91C2E0F9@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IMPORTANT - Re: Question on 6204bis
Thread-Index: Acyzi2killcTweH4QeOoCpSsAH/MPAAA0RsA
References: <CAFBA0C7.1B8403%john_brzozowski@cable.comcast.com> <27630529-B761-4AE7-B82F-A6A343E203E0@cisco.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3036CE263@XMB-RCD-109.cisco.com> <C67D840A-9A3A-4FEC-BB1C-6EE975F9E126@gmail.com> <7CA7ACE6-8F84-4422-8891-CC5F0719BD69@cisco.com> <CAKD1Yr1oic-6Y3Sr_YMy_QLY=5cSQYyz8ybkBKJD25shtxmpXw@mail.gmail.com> <D2CACB00-BFF7-46EA-9239-620E6950DF7D@cisco.com> <A8D68D39-2D0D-449A-9894-9A95EB0116B9@gmail.com> <CAKD1Yr0_t6MJkFZe8gBd+JFxoVEiUDNdu-cfTSaRGcXE2m_1GA@mail.gmail.com> <A9A742D6-08FD-4871-99B8-DB173070E98A@nominum.com> <7E9CDB49-E846-4C03-B828-0DC59C1C4522@gmail.com> <2EF2D64D-74AD-4188-A676-0983A2312926@nominum.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778448@XMB-RCD-109.cisco.com> <5CE46365-718A-47D7-B40B-537BE3434E1A@nominum.com>, <C4BFAE25-3CE8-4348-9A9B-4E0485C055FF@cisco.com> <7EED226A-96AC-4FB9-8489-6E024F4900F7@nominum.com> <2E51BF04-F114-4510-9EE5-482A0EE46414@cisco.com> <750BF7861EBBE048B3E648B4BB6E8F4F214FB748@crexc50p> <E46A2E66- ADF7-4BD 5-9BD9-4A4D91C2E0F9@cisco.com>
From: "STARK, BARBARA H" <bs7652@att.com>
To: "Ole Troan" <ot@cisco.com>
X-OriginalArrivalTime: 05 Dec 2011 21:03:29.0982 (UTC) FILETIME=[57197DE0:01CCB391]
X-Mailman-Approved-At: Mon, 05 Dec 2011 13:09:35 -0800
Cc: Ted Lemon <Ted.Lemon@nominum.com>, Ralph Droms <rdroms.ietf@gmail.com>, Joel Jaeggli <joelja@bogus.com>, dhc Chairs <dhc-chairs@tools.ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, dhc WG <dhcwg@ietf.org>, cpe-router@external.cisco.com, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [dhcwg] IMPORTANT - Re: Question on 6204bis
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: Mon, 05 Dec 2011 21:04:30 -0000

> CPE requests both IA_NA, IA_PD. the DHCP server has a policy to only
> give out e.g. IA_PD.
> this also applies in the case where a client requests both IA_NA and
> IA_TA...
> the DHCP specifications do not describe how a client should behave in
> this case.
>=20
> cheers,
> Ole

Which, per 6204 and 6204bis results in the unnumbered model being
utilized. Unless (per 6204bis) the device is configured to require a
global address on its WAN. Then the device does whatever the specifiers
of that configuration tell it to do.

I don't see a problem. And I don't see a need for dhc wg to specify
additional client behavior. Per the lack of current guidance in dhc RFCs
and errata, device designers/profile specifiers/etc. are free to specify
how they want their devices to behave when they get one IA and not
another. They are free to design devices that don't do SLAAC and request
IA_NA and go belly-up if no IA_NA, if that's consistent with the
environment where the devices will operate. Or not. Or requests IA_NA
and IA_TA and are happy with either, but not both. Or are only happy
with both. Or really don't care if they get either one (maybe because
they tried SLAAC, too, and got something there). They can design devices
that can tolerate getting an address by SLAAC and/or IA_NA or
unnumbered. Or that require IA_NA. Or that require SLAAC and ignore all
M bits and never to DHCPv6 (and I think there's quite a few of those).
And that's exactly what 6204(bis) is doing. It's taking a particular
environment and defining device behavior that will work in that
environment, and consistent with protocol standards. It is as it should
be. The protocol standards do not need to be over-specified.=20

But the errata are needed. A NoAddrsAvail needs to be specific to an IA,
and not preclude the sending of one IA but not another.
Barbara


From internet-drafts@ietf.org  Mon Dec  5 20:21:09 2011
Return-Path: <internet-drafts@ietf.org>
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 D5C8121F8AEC; Mon,  5 Dec 2011 20:21:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QvdMzGpe3RKm; Mon,  5 Dec 2011 20:21:09 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E1B521F8AE1; Mon,  5 Dec 2011 20:21:09 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64
Message-ID: <20111206042109.24513.55610.idtracker@ietfa.amsl.com>
Date: Mon, 05 Dec 2011 20:21:09 -0800
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-tunnel-00.txt
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: Tue, 06 Dec 2011 04:21:10 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Dynamic Host Configuration Working Gr=
oup of the IETF.

	Title           : DHCPv6 through Tunnels
	Author(s)       : Ole Troan
                          Marc Blanchet
                          Xiaohu Xu
                          Dayong Guo
	Filename        : draft-ietf-dhc-dhcpv6-tunnel-00.txt
	Pages           : 5
	Date            : 2011-10-12

   The host configuration protocol DHCPv6 [RFC3315] relies on link-local
   addressing and multicast to function.  However, most of the existing
   6over4 tunnel link types (e.g., 6rd [RFC5969] ) don't support IPv6
   link-local addresses and even IPv6 multicast addresses.  Taking 6rd
   as an example, this document specifies how DHCPv6 can be used across
   such tunnel links .


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-tunnel-00.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-tunnel-00.txt


From mohta@necom830.hpcl.titech.ac.jp  Mon Dec  5 21:04:13 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 0A2751F0C45 for <dhcwg@ietfa.amsl.com>; Mon,  5 Dec 2011 21:04:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.003
X-Spam-Level: 
X-Spam-Status: No, score=-0.003 tagged_above=-999 required=5 tests=[AWL=0.087,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pdclycUU+Hqo for <dhcwg@ietfa.amsl.com>; Mon,  5 Dec 2011 21:04:12 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id E71681F0C43 for <dhcwg@ietf.org>; Mon,  5 Dec 2011 21:03:59 -0800 (PST)
Received: (qmail 25837 invoked from network); 6 Dec 2011 05:37:37 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 6 Dec 2011 05:37:37 -0000
Message-ID: <4EDDA230.5080804@necom830.hpcl.titech.ac.jp>
Date: Tue, 06 Dec 2011 14:03:44 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: dhcwg@ietf.org, Ted Lemon <Ted.Lemon@nominum.com>
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com><4EDA13B7.9090402@necom830.hpcl.titech.ac.jp><6DA3E757-414F-41C3-A8A2-FA89EC7F6C8C@nominum.com><4EDACEE4.5080905@necom830.hpcl.titech.ac.jp><60C9046A-F5E9-4B34-9056-48EA34788E81@nominum.com><4EDB30FC.1020204@necom830.hpcl.titech.ac.jp><5B6B2B64C9FE2A489045EEEADDAFF2C3037785E5@XMB-RCD-109.cisco.com> <4EDBDA5C.2080103@necom830.hpcl.titech.ac.jp> <5B6B2B64C9FE2A489045EEEADDAFF2C303778615@XMB-RCD-109.cisco.com> <4EDC3A53.8060203@necom830.hpcl.titech.ac.jp> <ECC2D256-6D9D-4373-A267-24234100E211@nominum.com>
In-Reply-To: <ECC2D256-6D9D-4373-A267-24234100E211@nominum.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] No default routers (was Re: To wait for RA or not to wait?)
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: Tue, 06 Dec 2011 05:04:13 -0000

Ted Lemon wrote:

>> What does not make sense is to have a default router even
>> though there are multiple source addresses, in which case
>> the only reasonable thing to do is to let an end system
>> maintain a routing table with an appropriate source address
>> and the next hop router for each routing table entry.
>
> Presumably you would still need what would effectively
> be a default route, though, right?

No, not at all. Some people may be saying "multiple addresses"
purposelessly, but my objective to support multiple addresses
is to remove the default route, which, in turn, makes
multiple address support more efficient.

Default route may be desired if default free RT is too large,
because of excessive multihoming by routing. However, if
multihoming is properly architected with multiple addresses
to assign an address for each homing, RT can be aggregated
at ISP level or above that the default free RT can be
very small.

Moreover, the default free RT gives a useful hint for an
end system to choose the best (w.r.t. IGP metric)
destination address currently reachable among its peers
multiple addresses. That is, response of multihoming with
multiple addresses does not always rely on time out and
is at least as good as multihoming by routing.

> You'd just have more specific routes that were associated with
> various source addresses, and you'd want the host to use
> those routes and those source addresses for those prefixes.

No, as your peer has the right to select the destination
address of reply packets from your multiple addresses, there
is no point to have source address selection for that purpose.

> Once the host is communicating off the provider network, any
> globally valid source address ought to work.

Yes, as routing over the Internet is highly asymmetric, there
is no point to expect longest match means return routability.

The only valid reason to have source address selection is
to police source address spoofing.

Granted that some people may be saying "source address
selection" purposelessly.

						Masataka Ohta

From rdroms.ietf@gmail.com  Tue Dec  6 10:14:42 2011
Return-Path: <rdroms.ietf@gmail.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 1556221F8BAD for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 10:14:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aH-jRB4Bpcvx for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 10:14:41 -0800 (PST)
Received: from mail-qw0-f51.google.com (mail-qw0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id D358921F8BA2 for <dhcwg@ietf.org>; Tue,  6 Dec 2011 10:14:40 -0800 (PST)
Received: by qadb12 with SMTP id b12so4456143qad.10 for <dhcwg@ietf.org>; Tue, 06 Dec 2011 10:14:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=RyBWR6uH2us7QRNcfP+r9+ySvpiXFKzS92ig5DuLaTY=; b=SNxNNxFOd7TKcXgyEvg6oSifSwX5D3NDclDT+7WskPDwFcTmm0egZRfpz9yySxJl0s 8Xwt+uAKJm9T/A9IQfObm/Rsofxc5nGSbF8hH9w2H3iwtmzGXrDATQvyWdwbBW4GLuYm VHzhpdCkBunKrZSd2bE9qNqsO7zQU7jz4bwYw=
Received: by 10.224.211.194 with SMTP id gp2mr13178375qab.99.1323195278877; Tue, 06 Dec 2011 10:14:38 -0800 (PST)
Received: from [161.44.65.173] ([161.44.65.173]) by mx.google.com with ESMTPS id dm3sm33581759qab.12.2011.12.06.10.14.37 (version=SSLv3 cipher=OTHER); Tue, 06 Dec 2011 10:14:37 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com>
Date: Tue, 6 Dec 2011 13:14:33 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com>
To: dhc WG <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Tue, 06 Dec 2011 18:14:42 -0000

On Dec 2, 2011, at 10:18 PM 12/2/11, Ted Lemon wrote:

> [...]
>=20
> There exist two errata that address this issue: erratum 2471 and =
erratum 2472.   These errata propose to have the status code appear =
inside the IA_NA option rather than in the outer layer of the Advertise =
message.   A similar erratum exists for RFC3361, proposing to put the =
status code option in the IA_PD option instead of, similarly, in the =
outer layer of the packet.

For those unfamiliar with the RFC Errata process, the two errata for RFC =
3315 are available at:
http://www.rfc-editor.org/errata_search.php?eid=3D2471
http://www.rfc-editor.org/errata_search.php?eid=3D2472

The related errata for RFC 3633 are at:

http://www.rfc-editor.org/errata_search.php?eid=3D2469
http://www.rfc-editor.org/errata_search.php?eid=3D2470

> In addition, the following observation has been made:
>=20
>  The other unclear problem area is around how to deal with IA_PD and =
IA_NA:
>    * Client requests both IA_NA and IA_PD in the same session, gets =
only IA_PD.
>      - Does it fork off a separate session for IA_NA and continues =
sending SOLICITs for only the IA_NA?
>      - Reset the DHCP client, and tries again?
>      - Keeps single session, and continues to ask for IA_NA on next =
RENEW?
>=20
>      all 3 behaviors have been seen in the wild plus some additional =
pathological cases.
>      in general dealing with multiple stateful options in DHCP is =
underspecified.
>=20
> So the topic for discussion in the working group here is as follows:
>=20
> 1. Is what is proposed in the errata the right thing?   Should we in =
fact have status codes inside of IA_* options instead of in the main =
packet?

In my opinion, the corrections proposed in these errata should be made.

> 2. If so, what is the full set of edits to RFC3315 and RFC3361 that =
are required to do this?

I think the errata specify the full set of edits required to implement =
the change.

> 2a. What do we do for clients that don't implement the errata?

Client processing for a status code of NoAddrsAvail in a Reply message =
in RFC 3315 is somewhat different from the processing of NoAddrsAvail in =
an Advertise message.  Section 18.1.8 of RFC 3315 specifies that the =
client looks for NoAddrsAvail in each IA individually.

If the server treats all clients as having implemented the errata, it =
will include the NoAddrsAvail in the IA_*s rather than in the main body =
of the Advertise messages.  If the client does not act on those =
NoAddrsAvail status codes will be notified of the NoAddrsAvail in the IA =
in the Reply message.

> 3. If not, what should we do instead?

The errata should be accepted.

> 4. If the client gets an IA_NA and no IA_PD, or vice versa, which of =
the three behaviors listed above should it follow?   Is it bad that =
different clients do this differently?

Seems to me the client should take the NoAddrsAvail as an indication =
that the server does not intend to fulfill the request for that IA.  I =
suggest the third behavior should be specified.

> 5. What have I missed?

Nothing I can think of...

> Comments?   Criticisms?   Rotten tomatoes?

Thanks for laying out the discussion as you have.  I think the answers =
to questions 1-3 are somewhat independent of the answers to question 4.  =
We can go ahead with acting on the 4 errata before we have an answer to =
4.

At the same time, we need to answer 4 as soon as possible, which should =
be in place and specified before the expected surge in production of =
IPv6-compatible home gateways.

- Ralph

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


From shemant@cisco.com  Tue Dec  6 10:57:59 2011
Return-Path: <shemant@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 A9FF821F8C0C for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 10:57:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.522
X-Spam-Level: 
X-Spam-Status: No, score=-6.522 tagged_above=-999 required=5 tests=[AWL=0.076,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hhfXd4gjL+HT for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 10:57:59 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id EC3CA21F8C35 for <dhcwg@ietf.org>; Tue,  6 Dec 2011 10:57:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5942; q=dns/txt; s=iport; t=1323197879; x=1324407479; h=mime-version:subject:date:message-id:in-reply-to: references:from:to; bh=eODT62v3UTUB/1ptkpNN77A6TNzun39f4SsVR5ChjUE=; b=WtVnRN5LJKEar8Qq4ZBk/53GrSdfyNb+MLitbCS1LtJ7DK7Ax9lnZ17j +559ACDiwTIaETSJDp3h9biPUUP0Nz9TEG8BcCJTtqVd+j7iYw1s3iUm2 AggZwZYI28flwtVAwVMIE3bOBZeKwusfrSeb+i8r9bhfeyD8tuJoiLhsC 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhEBABEppk6tJV2c/2dsb2JhbACCJY4gjhZ4lFWSNIYZBIZQjXmKXA
X-IronPort-AV: E=Sophos;i="4.69,632,1315180800"; d="scan'208,217";a="39127712"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-9.cisco.com with ESMTP; 06 Dec 2011 18:57:58 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id pB6Ivwag025610;  Tue, 6 Dec 2011 18:57:58 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 6 Dec 2011 12:57:57 -0600
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCB448.F84500AD"
Date: Tue, 6 Dec 2011 12:57:57 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com>
In-Reply-To: <4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: Acy0Qu+TKXkfnobRS4aUiHSKKDLPdwAA2wxw
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com> <4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Ralph Droms" <rdroms.ietf@gmail.com>, "dhc WG" <dhcwg@ietf.org>
X-OriginalArrivalTime: 06 Dec 2011 18:57:57.0885 (UTC) FILETIME=[F80872D0:01CCB448]
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Tue, 06 Dec 2011 18:57:59 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CCB448.F84500AD
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Ralph Droms
Sent: Tuesday, December 06, 2011 1:15 PM
To: dhc WG
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...

=20

=20

>At the same time, we need to answer 4 as soon as possible, which should
be in place and specified before the expected surge in production of
IPv6->compatible home gateways.

=20

I do not think it is acceptable to let different clients do three
different behaviors.  The behavior has got to be consistent for every
DHC client.  I am not going with choice 3 yet because the Renew is a
unicast message between the client and the server and now my CMTS DHCPv6
relay agent has to sniff unicast DHCPv6 messages in the fast path.  At
least the CMTS relay agent does need to track any IA_NA, IA_PD doled out
to a DHCPv6 client in the CMTS downstream.  Maybe choice 1 is fine where
the client accepts one option and then sends subsequent SOLICITs for the
other option.  To keep the server from getting pounded if choice 1 is
picked, use the new Ralph's draft SOL_MAX_RT option.   =20

=20

If folks balk at choices 1 and 2, then I am still open to choice 3.

=20

Thanks,

=20

Hemant


------_=_NextPart_001_01CCB448.F84500AD
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>-----Original Message-----<br>From: =
dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of =
Ralph Droms<br>Sent: Tuesday, December 06, 2011 1:15 PM<br>To: dhc =
WG<br>Subject: Re: [dhcwg] Some high-priority errata for =
RFC3315/3396...</p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'>&gt;At the same time, we need to =
answer 4 as soon as possible, which should be in place and specified =
before the expected surge in production of IPv6-&gt;compatible home =
gateways.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New";color:black'>I do not think it is acceptable to let different =
clients do three different behaviors.&nbsp; The behavior has got to be =
consistent for every DHC client. &nbsp;I am not going with choice 3 yet =
because the Renew is a unicast message between the client and the server =
and now my CMTS DHCPv6 relay agent has to sniff unicast DHCPv6 messages =
in the fast path.&nbsp; At least the CMTS relay agent does need to track =
any IA_NA, IA_PD doled out to a DHCPv6 client in the CMTS =
downstream.&nbsp; Maybe choice 1 is fine where the client accepts one =
option and then sends subsequent SOLICITs for the other option.&nbsp; To =
keep the server from getting pounded if choice 1 is picked, use the new =
Ralph's draft SOL_MAX_RT option. =
&nbsp;&nbsp;&nbsp;<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New";color:black'>If folks balk at choices 1 and 2, then I am still open =
to choice 3.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New";color:black'>Thanks,<o:p></o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'font-family:"Courier =
New";color:black'>Hemant<o:p></o:p></span></p></div></body></html>
------_=_NextPart_001_01CCB448.F84500AD--

From rdroms.ietf@gmail.com  Tue Dec  6 11:03:33 2011
Return-Path: <rdroms.ietf@gmail.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 5E82B21F8BE4 for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 11:03:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fkk7G5yY5pBH for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 11:03:33 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id C5D9E21F8BC5 for <dhcwg@ietf.org>; Tue,  6 Dec 2011 11:03:32 -0800 (PST)
Received: by qcsf15 with SMTP id f15so3038691qcs.31 for <dhcwg@ietf.org>; Tue, 06 Dec 2011 11:03:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=6wpheGDNguUe09zP49KxvqKS2x16KjI6rVbA3+nHYZg=; b=JeH9BZLrF9uhqzGN6J//gArfq/2lJqt5umFR3O0qdTFH17fmfS/66IEySuaIjsoUVc PNoLZVK2iPQh5egKNefs1f956Lm79XGGEZO4GTnx4ItMcFGl0COQDsy1oaFmNTEJ86t4 NF9GLWZnFpvA/22edBR6ExvH+lEL6NE5YIMnM=
Received: by 10.229.63.89 with SMTP id a25mr3391821qci.68.1323198212177; Tue, 06 Dec 2011 11:03:32 -0800 (PST)
Received: from [161.44.65.173] ([161.44.65.173]) by mx.google.com with ESMTPS id v5sm33771620qao.21.2011.12.06.11.03.30 (version=SSLv3 cipher=OTHER); Tue, 06 Dec 2011 11:03:31 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com>
Date: Tue, 6 Dec 2011 14:03:28 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com> <4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Tue, 06 Dec 2011 19:03:33 -0000

Hemant - DHCPv6 uses multicast for all messages unless the server has =
explicitly sent the server-unicast option.  Read section 18 of RFC 3315.

- Ralph

On Dec 6, 2011, at 1:57 PM 12/6/11, Hemant Singh (shemant) wrote:

> =20
> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf =
Of Ralph Droms
> Sent: Tuesday, December 06, 2011 1:15 PM
> To: dhc WG
> Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
> =20
> =20
> >At the same time, we need to answer 4 as soon as possible, which =
should be in place and specified before the expected surge in production =
of IPv6->compatible home gateways.
> =20
> I do not think it is acceptable to let different clients do three =
different behaviors.  The behavior has got to be consistent for every =
DHC client.  I am not going with choice 3 yet because the Renew is a =
unicast message between the client and the server and now my CMTS DHCPv6 =
relay agent has to sniff unicast DHCPv6 messages in the fast path.  At =
least the CMTS relay agent does need to track any IA_NA, IA_PD doled out =
to a DHCPv6 client in the CMTS downstream.  Maybe choice 1 is fine where =
the client accepts one option and then sends subsequent SOLICITs for the =
other option.  To keep the server from getting pounded if choice 1 is =
picked, use the new Ralph's draft SOL_MAX_RT option.   =20
> =20
> If folks balk at choices 1 and 2, then I am still open to choice 3.
> =20
> Thanks,
> =20
> Hemant


From shemant@cisco.com  Tue Dec  6 11:09:27 2011
Return-Path: <shemant@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 2414821F8BBA for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 11:09:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HrVmIlpsAZeo for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 11:09:26 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 5848121F8B80 for <dhcwg@ietf.org>; Tue,  6 Dec 2011 11:09:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=1983; q=dns/txt; s=iport; t=1323198566; x=1324408166; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=ZP1JZ0K9YS1Qh023CDksvzL225RVg1S1oejbzr39XoE=; b=EuU8tmGAEPoDR7f9pzt0Mm+EsjCpiJImPf7TvKPTdmINB4rtVjUSTgCc hgLxtVh0GrDn6jbsrVIiPPePW7fQ+KcFFwiqhzv4gPCzoQ/+uCC0QAlTv MvWvbo3dwbCSCUp3CtT/owQOxeLMebFuh0ecete5knup70swCgpXJrSL4 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AokAAB9o3k6tJV2c/2dsb2JhbABDmh2QP4EFgXIBAQEBAxIBFAkKPwwEAgEIDgMEAQELBhcBBgEgJQkIAQEEEwganl0BnlWKT2MEiC6XHodZ
X-IronPort-AV: E=Sophos;i="4.71,307,1320624000"; d="scan'208";a="41643462"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-7.cisco.com with ESMTP; 06 Dec 2011 19:09:25 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id pB6J9PS9032598;  Tue, 6 Dec 2011 19:09:25 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 6 Dec 2011 13:09:25 -0600
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 6 Dec 2011 13:09:25 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com>
In-Reply-To: <4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: Acy0SgXzhh9Co0HVRPOxM9/+ree61wAABmJA
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com> <4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com> <4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Ralph Droms" <rdroms.ietf@gmail.com>
X-OriginalArrivalTime: 06 Dec 2011 19:09:25.0551 (UTC) FILETIME=[91E9F3F0:01CCB44A]
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Tue, 06 Dec 2011 19:09:27 -0000

Ralph,

OK, got it.  I was confused from DHCPv4.  So when the server-unicast
option is set, then the relay does have to sniff unicast DHCPv6 messages
which is not a new problem for choice 3.  Thus I am for choice 3.

Thanks,

Hemant


-----Original Message-----
From: Ralph Droms [mailto:rdroms.ietf@gmail.com]=20
Sent: Tuesday, December 06, 2011 2:03 PM
To: Hemant Singh (shemant)
Cc: dhc WG
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...

Hemant - DHCPv6 uses multicast for all messages unless the server has
explicitly sent the server-unicast option.  Read section 18 of RFC 3315.

- Ralph

On Dec 6, 2011, at 1:57 PM 12/6/11, Hemant Singh (shemant) wrote:

> =20
> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Ralph Droms
> Sent: Tuesday, December 06, 2011 1:15 PM
> To: dhc WG
> Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
> =20
> =20
> >At the same time, we need to answer 4 as soon as possible, which
should be in place and specified before the expected surge in production
of IPv6->compatible home gateways.
> =20
> I do not think it is acceptable to let different clients do three
different behaviors.  The behavior has got to be consistent for every
DHC client.  I am not going with choice 3 yet because the Renew is a
unicast message between the client and the server and now my CMTS DHCPv6
relay agent has to sniff unicast DHCPv6 messages in the fast path.  At
least the CMTS relay agent does need to track any IA_NA, IA_PD doled out
to a DHCPv6 client in the CMTS downstream.  Maybe choice 1 is fine where
the client accepts one option and then sends subsequent SOLICITs for the
other option.  To keep the server from getting pounded if choice 1 is
picked, use the new Ralph's draft SOL_MAX_RT option.   =20
> =20
> If folks balk at choices 1 and 2, then I am still open to choice 3.
> =20
> Thanks,
> =20
> Hemant


From Ted.Lemon@nominum.com  Tue Dec  6 11:23:05 2011
Return-Path: <Ted.Lemon@nominum.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 726AF21F8BC5 for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 11:23:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.52
X-Spam-Level: 
X-Spam-Status: No, score=-106.52 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nk8jzzZsUHNE for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 11:23:04 -0800 (PST)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id 87CB921F8507 for <dhcwg@ietf.org>; Tue,  6 Dec 2011 11:23:04 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKTt5ri5gAgphdWntM+cyyJlGRdaQhhWtX@postini.com; Tue, 06 Dec 2011 11:23:04 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 6AF0A1B8237 for <dhcwg@ietf.org>; Tue,  6 Dec 2011 11:22:51 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 5360D190052; Tue,  6 Dec 2011 11:22:51 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0339.001; Tue, 6 Dec 2011 11:22:51 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: AcyxakejwUXOElp7STCtYjgcemUphwDG63mAAAGEB4AAADFTAAAANTKAAAB3qAA=
Date: Tue, 6 Dec 2011 19:22:51 +0000
Message-ID: <D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com> <4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com> <4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_D2A0EC975C604D2398CA3E0E269872DFnominumcom_"
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Tue, 06 Dec 2011 19:23:05 -0000

--_000_D2A0EC975C604D2398CA3E0E269872DFnominumcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Dec 6, 2011, at 2:09 PM, Hemant Singh (shemant) wrote:
OK, got it.  I was confused from DHCPv4.  So when the server-unicast
option is set, then the relay does have to sniff unicast DHCPv6 messages
which is not a new problem for choice 3.  Thus I am for choice 3.

I think we should be aware that choice 3 does have the side effect that if =
a DHCP that would offer an IA_NA is offline, and then comes back online, a =
client that follows choice 3 as I understand it will never get an IA_NA.   =
I realize that choice 3 (accept an offer that contains an IA_PD and no IA_N=
A, keep asking for IA_NA in subsequent renews, and do not fork another requ=
estor for IA_NA) is attractive for the case where there is no DHCP server o=
n the wire that *could* offer an IA_NA, however, since it will stop the cli=
ent soliciting for an IA_NA it will never get, and hence reduce the load on=
 the server.

Having said that, I think that DHCP currently is simply broken with respect=
 to multiple provisioning domains on the same wire.  The case where choice =
3 fails is a case where there are multiple provisioning domains on the wire=
.   So I think that if we solve the MPD problem, we will also have addresse=
d the problem with choice 3.   Until we solve the MPD problem, we really ca=
n't solve the problem with choice 3.

So I am willing to provisionally agree that choice 3 is the right choice, t=
hat RFC3315bis should mandate choice 3, and that we need an additional erra=
ta that mandates choice 3.

Ralph, I have to disagree with you that simply blessing the four errata you=
 mentioned solves this problem.   We need more text, unfortunately.


--_000_D2A0EC975C604D2398CA3E0E269872DFnominumcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <FF570BDB5D567047936C5D842A08C2C2@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 6, 2011, at 2:09 PM, Hemant Singh (shemant) wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">OK,
 got it. &nbsp;I was confused from DHCPv4. &nbsp;So when the server-unicast=
<br>
option is set, then the relay does have to sniff unicast DHCPv6 messages<br=
>
which is not a new problem for choice 3. &nbsp;Thus I am for choice 3.</spa=
n></blockquote>
</div>
<br>
<div>I think we should be aware that choice 3 does have the side effect tha=
t if a DHCP that would offer an IA_NA is offline, and then comes back onlin=
e, a client that follows choice 3 as I understand it will never get an IA_N=
A. &nbsp; I realize that choice 3 (accept
 an offer that contains an IA_PD and no IA_NA, keep asking for IA_NA in sub=
sequent renews, and do not fork another requestor for IA_NA) is attractive =
for the case where there is no DHCP server on the wire that *could* offer a=
n IA_NA, however, since it will
 stop the client soliciting for an IA_NA it will never get, and hence reduc=
e the load on the server.</div>
<div><br>
</div>
<div>Having said that, I think that DHCP currently is simply broken with re=
spect to multiple provisioning domains on the same wire. &nbsp;The case whe=
re choice 3 fails is a case where there are multiple provisioning domains o=
n the wire. &nbsp; So I think that if we solve
 the MPD problem, we will also have addressed the problem with choice 3. &n=
bsp; Until we solve the MPD problem, we really can't solve the problem with=
 choice 3.</div>
<div><br>
</div>
<div>So I am willing to provisionally agree that choice 3 is the right choi=
ce, that RFC3315bis should mandate choice 3, and that we need an additional=
 errata that mandates choice 3.</div>
<div><br>
</div>
<div>Ralph, I have to disagree with you that simply blessing the four errat=
a you mentioned solves this problem. &nbsp; We need more text, unfortunatel=
y.</div>
<div><br>
</div>
</body>
</html>

--_000_D2A0EC975C604D2398CA3E0E269872DFnominumcom_--

From rdroms.ietf@gmail.com  Tue Dec  6 11:34:19 2011
Return-Path: <rdroms.ietf@gmail.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 61A5F21F8BBF for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 11:34:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S6ATRvJY4Wpx for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 11:34:18 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id C9DA821F8BBE for <dhcwg@ietf.org>; Tue,  6 Dec 2011 11:34:18 -0800 (PST)
Received: by qadb15 with SMTP id b15so3064755qad.10 for <dhcwg@ietf.org>; Tue, 06 Dec 2011 11:34:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=c7iYSdQtzfkhe0FHeR2n6vPaHoZ4issNXYMPt+YG2Og=; b=orazo3Ur83+gKOlSYZ9+0B/L4/Hu25VO2Dbz37Hz6HNDKFhGDYRNbDz6MkSQQw5r74 6o9LuzjZ+pyE6g9/LvzAu8YTvzybv0Hhwewadns0Fv/3SDYsbVp6NNARPgOUcgMLyEtt UMskJndV6AY+TNdxyTdM/iZFd1HlhUxw4E9eE=
Received: by 10.224.180.131 with SMTP id bu3mr13477979qab.5.1323200058339; Tue, 06 Dec 2011 11:34:18 -0800 (PST)
Received: from [161.44.65.173] ([161.44.65.173]) by mx.google.com with ESMTPS id df3sm33947943qab.6.2011.12.06.11.34.16 (version=SSLv3 cipher=OTHER); Tue, 06 Dec 2011 11:34:17 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com>
Date: Tue, 6 Dec 2011 14:34:14 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <95FDEE46-2731-4419-921B-1DA3A4F3FD92@gmail.com>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com> <4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com> <4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com> <D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Tue, 06 Dec 2011 19:34:19 -0000

Ted...

On Dec 6, 2011, at 2:22 PM 12/6/11, Ted Lemon wrote:

> On Dec 6, 2011, at 2:09 PM, Hemant Singh (shemant) wrote:
>> OK, got it.  I was confused from DHCPv4.  So when the server-unicast
>> option is set, then the relay does have to sniff unicast DHCPv6 =
messages
>> which is not a new problem for choice 3.  Thus I am for choice 3.
>=20
> I think we should be aware that choice 3 does have the side effect =
that if a DHCP that would offer an IA_NA is offline, and then comes back =
online, a client that follows choice 3 as I understand it will never get =
an IA_NA.   I realize that choice 3 (accept an offer that contains an =
IA_PD and no IA_NA, keep asking for IA_NA in subsequent renews, and do =
not fork another requestor for IA_NA) is attractive for the case where =
there is no DHCP server on the wire that *could* offer an IA_NA, =
however, since it will stop the client soliciting for an IA_NA it will =
never get, and hence reduce the load on the server.
>=20
> Having said that, I think that DHCP currently is simply broken with =
respect to multiple provisioning domains on the same wire.  The case =
where choice 3 fails is a case where there are multiple provisioning =
domains on the wire.   So I think that if we solve the MPD problem, we =
will also have addressed the problem with choice 3.   Until we solve the =
MPD problem, we really can't solve the problem with choice 3.
>=20
> So I am willing to provisionally agree that choice 3 is the right =
choice, that RFC3315bis should mandate choice 3, and that we need an =
additional errata that mandates choice 3.
>=20
> Ralph, I have to disagree with you that simply blessing the four =
errata you mentioned solves this problem.   We need more text, =
unfortunately.

To clarify...  In my opinion, the errata are necessary but not =
sufficient.  The errata are correct taken by themselves and can be =
approved on their own merit.  The errata enable a solution to the =
problem in your original point 4, but more text is required for the =
complete solution.

- Ralph


From jmpolk@cisco.com  Tue Dec  6 11:38:05 2011
Return-Path: <jmpolk@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 AADC121F8BB8 for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 11:38:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.556
X-Spam-Level: 
X-Spam-Status: No, score=-106.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4S7fQqB6Kmzq for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 11:38:04 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id DFDD921F8BAD for <dhcwg@ietf.org>; Tue,  6 Dec 2011 11:38:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=4321; q=dns/txt; s=iport; t=1323200284; x=1324409884; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=bgLijp3d+q3NVGMNNw3sHhb67rHb1dbxuKUvL1Bds5k=; b=Y2/sGuqA8ABQ4IDbiQgzhGME0uskamq2yY1wzrL02Jgn1xIgq2UaLY8o Soi0XMd/LbjQWVXZmVrMmJzt9YpmKVXLgRD4YnQssx4nt10j6D2WN6ys3 yz1EaZ5E1zAsFh0d1fCNQR1CwOrtfru7EyQ9FTcErxsBrAdNM5Q2yc+1M c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAIRu3k6rRDoI/2dsb2JhbABDql2BBYFyAQEBAQMBAQEPASUCMQMLEAcEGB4QGQ4wBhMbB4dtln0BnlEEik9jBIgunnc
X-IronPort-AV: E=Sophos;i="4.71,308,1320624000"; d="scan'208";a="16367357"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 06 Dec 2011 19:38:04 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8711.cisco.com [10.99.80.18]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pB6Jc3pD028634; Tue, 6 Dec 2011 19:38:04 GMT
Message-Id: <201112061938.pB6Jc3pD028634@mtv-core-3.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 06 Dec 2011 13:38:08 -0600
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <C042ECF1-C246-4090-A4C6-6B20302227FA@gmail.com>
References: <6B961032-728D-43D6-81E3-9862EF9ADA09@gmail.com> <2207D364-CADB-43D2-907B-204180A6E4CC@nominum.com> <201110032203.p93M3f5I031107@mtv-core-3.cisco.com> <5EA79C2C-F4A2-4D88-85DC-E2F4B931E11A@nominum.com> <201110041732.p94HW6s3000630@mtv-core-1.cisco.com> <67AEBF45-5C47-43B4-B86C-482ED32E41D3@nominum.com> <201110042006.p94K6NX8001171@mtv-core-3.cisco.com> <578BA924-AE98-4B72-8857-949C9B76D6F6@nominum.com> <478F3A8B-6ADE-4BC2-BCBE-7214AD983727@gmail.com> <201110042057.p94KvlAJ004802@mtv-core-3.cisco.com> <C042ECF1-C246-4090-A4C6-6B20302227FA@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Ralph Droms <rdroms.ietf@gmail.com>, Lemon Ted <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] review of draft-ietf-geopriv-dhcp-lbyr-uri-option
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: Tue, 06 Dec 2011 19:38:05 -0000

Circling back around on this draft's feedback from this WG.

Two folks have stated clearly on this list that the second lifetime 
timer <valid-for> (for considering whether or not the information at 
the location URI is good or stale (and needing a refresh)) is a bad 
idea within DHCP.  From this, I have 2 questions for this WG:

#1 - do others agree?

and

#2 - should the <valid-for> field (and idea) be removed from this ID?

As the doc's editor, I believe this is the last open item holding up 
this draft from progressing to the IESG.

Thank you for those who respond - even if it's only a yes/no to 
either question. This draft can't progress without a resolution to this issue.

James

At 03:01 PM 10/4/2011, Ralph Droms wrote:

>On Oct 4, 2011, at 4:57 PM 10/4/11, James M. Polk wrote:
>
> > At 03:31 PM 10/4/2011, Ralph Droms wrote:
> >
> >> On Oct 4, 2011, at 4:25 PM 10/4/11, Ted Lemon wrote:
> >>
> >> > On Oct 4, 2011, at 4:06 PM, James M. Polk wrote:
> >> >> I shortened the bullet, but what you say above is part of 
> what I suggested (i.e., needing a trigger upon change of an AP), 
> but that didn't satisfy the discussion in Geopriv.
> >> >
> >> > Interesting.   So they are willing to take a solution that 
> doesn't fix the problem, but reject a solution that does fix the 
> problem?   They can certainly fly in the face of reason like this 
> if they want, but that's not a good reason to change the way the 
> DHCP protocol works.
> >> >
> >> >>> In this situation you are not using DHCP, so it's not an issue.
> >> >>
> >> >> as cut-n-dry (or black-n-white) as you see this, others see 
> grey (unfortunately).
> >> >
> >> > This is actually the same as the previous question.   Even if 
> they were to use DHCP, a lifetime on the address wouldn't actually 
> solve the stated problem, because again the device needs to notice 
> that it's changed cells.
> >> >
> >> > And by the way, in both of these cases, even supposing that we 
> did change the DHCP protocol in the way that's been proposed, how 
> would the DHCP server know that the device was connecting through a 
> different access point or cell tower?
> >>
> >> And how does the host, after receiving the new URI from its DHCP 
> client, notify all the holders of that URI that the URI has changed?
> >
> > I'm a little twisted around, and not completely following your 
> question. Are you asking how does the host inform remote hosts that 
> the URI it sent previously is no longer good or needs to be replaced?
> >        - Answer - it needs to send the new URI to all the
> >          remote hosts again (each time), which IMO defeats
> >          the purpose, but this is what Geopriv wanted
>
>...and I may have missed this from the draft or other background: 
>does the host maintain a list of all other hosts to which it has 
>sent the URI so it can update those hosts?
>
>...which, as you say, seems to defeat the whole purpose of a "permanent" URI.
>
>- Ralph
>
> >
> >
> >> >
> >> >> The DHC WG stating there is a problem with the Valid-For 
> field within this document is something concrete that the (Geopriv) 
> chairs would need to address with and into DHC, IMO.
> >> >
> >> > Right, so I would be curious to hear from other DHC working 
> group members as to whether they have an opinion on whether the 
> DHCP protocol should be extended with an additional lifetime on 
> geopriv URIs.   Bear in mind that all DHCP clients would have to be 
> modified to support this feature.
> >>
> >> I don't think it's acceptable to extend the DHCP specification 
> and state machine to include an additional lifetime on geopriv URIs 
> for a couple of reasons:
> >>
> >> * in the specific case, the change doesn't solve the problem
> >> * in the general case, forcing the recoding of the core code in 
> DHCP clients and servers to accommodate this new option is inappropriate
> >>
> >> I- Ralph
> >
> > Thanks - I think this is why Robert asked the experts on DHCP.
> >
> > Other comments, concerns or questions?
> >
> > James
> >
> >
> >> >
> >> > Thoughts?   Comments?
> >> >
> >
>
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www.ietf.org/mailman/listinfo/dhcwg


From Ted.Lemon@nominum.com  Tue Dec  6 12:33:07 2011
Return-Path: <Ted.Lemon@nominum.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 B3FEF21F8B72 for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 12:33:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.523
X-Spam-Level: 
X-Spam-Status: No, score=-106.523 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u2bbOpiJvndT for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 12:33:07 -0800 (PST)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id E148B21F8B12 for <dhcwg@ietf.org>; Tue,  6 Dec 2011 12:33:06 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKTt58ARddso3J2qNtBkKf9lqb7V/ksSQ6@postini.com; Tue, 06 Dec 2011 12:33:06 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id AD1601B8237 for <dhcwg@ietf.org>; Tue,  6 Dec 2011 12:33:04 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 74F67190052; Tue,  6 Dec 2011 12:33:04 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0339.001; Tue, 6 Dec 2011 12:33:04 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: AcyxakejwUXOElp7STCtYjgcemUphwDG63mAAAGEB4AAADFTAAAANTKAAAB3qAAAAGY5AAACDugA
Date: Tue, 6 Dec 2011 20:33:04 +0000
Message-ID: <601EE481-E4B8-48DC-9885-0FB3302DC8CB@nominum.com>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com> <4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com> <4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com> <D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com> <95FDEE46-2731-4419-921B-1DA3A4F3FD92@gmail.com>
In-Reply-To: <95FDEE46-2731-4419-921B-1DA3A4F3FD92@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_601EE481E4B848DC98850FB3302DC8CBnominumcom_"
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Tue, 06 Dec 2011 20:33:07 -0000

--_000_601EE481E4B848DC98850FB3302DC8CBnominumcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Dec 6, 2011, at 2:34 PM, Ralph Droms wrote:
To clarify...  In my opinion, the errata are necessary but not sufficient. =
 The errata are correct taken by themselves and can be approved on their ow=
n merit.  The errata enable a solution to the problem in your original poin=
t 4, but more text is required for the complete solution.

Fair enough.   However, I think approving them by themselves creates an inc=
onsistency in the standard that still needs to be addressed, so we have to =
address it before we approve them.


--_000_601EE481E4B848DC98850FB3302DC8CBnominumcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <151FBCECED676D4C864BE19E3811B5A1@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 6, 2011, at 2:34 PM, Ralph Droms wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">To
 clarify... &nbsp;In my opinion, the errata are necessary but not sufficien=
t. &nbsp;The errata are correct taken by themselves and can be approved on =
their own merit. &nbsp;The errata enable a solution to the problem in your =
original point 4, but more text is required for
 the complete solution.</span></blockquote>
</div>
<br>
<div>Fair enough. &nbsp; However, I think approving them by themselves crea=
tes an inconsistency in the standard that still needs to be addressed, so w=
e have to address it before we approve them.</div>
<div><br>
</div>
</body>
</html>

--_000_601EE481E4B848DC98850FB3302DC8CBnominumcom_--

From Ted.Lemon@nominum.com  Tue Dec  6 12:36:34 2011
Return-Path: <Ted.Lemon@nominum.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 BDCEF21F8B74 for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 12:36:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.525
X-Spam-Level: 
X-Spam-Status: No, score=-106.525 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HIcKt2Ia7RM4 for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 12:36:34 -0800 (PST)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by ietfa.amsl.com (Postfix) with ESMTP id C8EFE21F8B12 for <dhcwg@ietf.org>; Tue,  6 Dec 2011 12:36:33 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob108.postini.com ([64.18.6.12]) with SMTP ID DSNKTt58zy4UBWLnpZDlxHVp1Ds4xmukjXgg@postini.com; Tue, 06 Dec 2011 12:36:33 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 5349C1B8237 for <dhcwg@ietf.org>; Tue,  6 Dec 2011 12:36:31 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 47DF0190052; Tue,  6 Dec 2011 12:36:31 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0339.001; Tue, 6 Dec 2011 12:36:31 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "James M. Polk" <jmpolk@cisco.com>
Thread-Topic: [dhcwg] review of draft-ietf-geopriv-dhcp-lbyr-uri-option
Thread-Index: AQHMggfbXjkViOtBlkentTTh6SBa8ZVrha+AgAAcNwCAABC0gIABNcEAgAAB8YCAACkqgIAABVuAgAABvwCAAAdDgIAAARMAgGL8TwCAABBXgA==
Date: Tue, 6 Dec 2011 20:36:31 +0000
Message-ID: <34043C82-5190-475B-8765-70B9C16FF4D7@nominum.com>
References: <6B961032-728D-43D6-81E3-9862EF9ADA09@gmail.com> <2207D364-CADB-43D2-907B-204180A6E4CC@nominum.com> <201110032203.p93M3f5I031107@mtv-core-3.cisco.com> <5EA79C2C-F4A2-4D88-85DC-E2F4B931E11A@nominum.com> <201110041732.p94HW6s3000630@mtv-core-1.cisco.com> <67AEBF45-5C47-43B4-B86C-482ED32E41D3@nominum.com> <201110042006.p94K6NX8001171@mtv-core-3.cisco.com> <578BA924-AE98-4B72-8857-949C9B76D6F6@nominum.com> <478F3A8B-6ADE-4BC2-BCBE-7214AD983727@gmail.com> <201110042057.p94KvlAJ004802@mtv-core-3.cisco.com> <C042ECF1-C246-4090-A4C6-6B20302227FA@gmail.com> <201112061938.pB6Jc3pD028634@mtv-core-3.cisco.com>
In-Reply-To: <201112061938.pB6Jc3pD028634@mtv-core-3.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_34043C825190475B876570B9C16FF4D7nominumcom_"
MIME-Version: 1.0
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] review of draft-ietf-geopriv-dhcp-lbyr-uri-option
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: Tue, 06 Dec 2011 20:36:34 -0000

--_000_34043C825190475B876570B9C16FF4D7nominumcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Dec 6, 2011, at 2:38 PM, James M. Polk wrote:
Two folks have stated clearly on this list that the second lifetime timer <=
valid-for> (for considering whether or not the information at the location =
URI is good or stale (and needing a refresh)) is a bad idea within DHCP.  F=
rom this, I have 2 questions for this WG:

#1 - do others agree?

I'm one of the people who objected, so I guess I'm not "others," but I defi=
nitely agree.

#2 - should the <valid-for> field (and idea) be removed from this ID?

Yes.

As the doc's editor, I believe this is the last open item holding up this d=
raft from progressing to the IESG.

No, the other problem is that the document does not address the rather seri=
ous problem of provisioning the DHCP server with these URIs.   As I underst=
and it, the expected use case is that the DHCP server will contact some oth=
er server to figure out which URI to send, before it sends the response to =
the DHCP client.   This is not consistent with general practice, and I don'=
t think it's an appropriate use of the DHCP protocol.


--_000_34043C825190475B876570B9C16FF4D7nominumcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <AB690159CDBD2E43ABAA087B0D6DB644@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 6, 2011, at 2:38 PM, James M. Polk wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">Two
 folks have stated clearly on this list that the second lifetime timer &lt;=
valid-for&gt; (for considering whether or not the information at the locati=
on URI is good or stale (and needing a refresh)) is a bad idea within DHCP.=
 &nbsp;From this, I have 2 questions for this
 WG:<br>
<br>
#1 - do others agree?<br>
</span></blockquote>
<div><br>
</div>
I'm one of the people who objected, so I guess I'm not &quot;others,&quot; =
but I definitely agree.</div>
<div><br>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">#2
 - should the &lt;valid-for&gt; field (and idea) be removed from this ID?<b=
r>
</span></blockquote>
<div><br>
</div>
Yes.</div>
<div><br>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">As
 the doc's editor, I believe this is the last open item holding up this dra=
ft from progressing to the IESG.</span></blockquote>
</div>
<br>
<div>No, the other problem is that the document does not address the rather=
 serious problem of provisioning the DHCP server with these URIs. &nbsp; As=
 I understand it, the expected use case is that the DHCP server will contac=
t some other server to figure out which
 URI to send, before it sends the response to the DHCP client. &nbsp; This =
is not consistent with general practice, and I don't think it's an appropri=
ate use of the DHCP protocol.</div>
<div><br>
</div>
</body>
</html>

--_000_34043C825190475B876570B9C16FF4D7nominumcom_--

From rdroms.ietf@gmail.com  Tue Dec  6 13:07:36 2011
Return-Path: <rdroms.ietf@gmail.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 4289D11E8083 for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 13:07:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JSt1KqXEioFp for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 13:07:35 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id B0AE311E8073 for <dhcwg@ietf.org>; Tue,  6 Dec 2011 13:07:35 -0800 (PST)
Received: by qcsf15 with SMTP id f15so3188004qcs.31 for <dhcwg@ietf.org>; Tue, 06 Dec 2011 13:07:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=cSoiSvlNTKiNkVk7t0ae1CkVopqShW4QmfGfRJhVxAc=; b=chJT7O5+1kRXM+icOTTmUeZVHS5CRQ6VEZX8KHVj+l2ZmrC2LIkYGsUEQrY0jTgnDV lrwoHQyn9WqCQorjY+7CHi/ztv2oPh+EpArnCSr0I3Zq+cnRVm/t6t6nINXVQrzme6/J NuCxQC1EBeKJLTu2mHh3IzW/BIX7zCtof7u/8=
Received: by 10.229.64.76 with SMTP id d12mr3481693qci.124.1323205655216; Tue, 06 Dec 2011 13:07:35 -0800 (PST)
Received: from [161.44.65.173] ([161.44.65.173]) by mx.google.com with ESMTPS id dm3sm34348988qab.12.2011.12.06.13.07.33 (version=SSLv3 cipher=OTHER); Tue, 06 Dec 2011 13:07:34 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <601EE481-E4B8-48DC-9885-0FB3302DC8CB@nominum.com>
Date: Tue, 6 Dec 2011 16:07:31 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E70EB90-F9B2-46FB-8E4A-FB63429E94B9@gmail.com>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com> <4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com> <4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com> <D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com> <95FDEE46-2731-4419-921B-1DA3A4F3FD92@gmail.com> <601EE481-E4B8-48DC-9885-0FB3302DC8CB@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Tue, 06 Dec 2011 21:07:36 -0000

On Dec 6, 2011, at 3:33 PM 12/6/11, Ted Lemon wrote:

> On Dec 6, 2011, at 2:34 PM, Ralph Droms wrote:
>> To clarify...  In my opinion, the errata are necessary but not =
sufficient.  The errata are correct taken by themselves and can be =
approved on their own merit.  The errata enable a solution to the =
problem in your original point 4, but more text is required for the =
complete solution.
>=20
> Fair enough.   However, I think approving them by themselves creates =
an inconsistency in the standard that still needs to be addressed, so we =
have to address it before we approve them.

What is the inconsistency you see?

- Ralph

>=20


From Ted.Lemon@nominum.com  Tue Dec  6 13:11:32 2011
Return-Path: <Ted.Lemon@nominum.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 D9E5121F8C51 for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 13:11:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.53
X-Spam-Level: 
X-Spam-Status: No, score=-106.53 tagged_above=-999 required=5 tests=[AWL=0.068, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cRfYpMxgUlIO for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 13:11:32 -0800 (PST)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id 1B07521F8C49 for <dhcwg@ietf.org>; Tue,  6 Dec 2011 13:11:32 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKTt6E97oiXaGeTjm89uQWawjRZrSuBZ/6@postini.com; Tue, 06 Dec 2011 13:11:32 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 346BD1B8237 for <dhcwg@ietf.org>; Tue,  6 Dec 2011 13:11:19 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 1A94D190052; Tue,  6 Dec 2011 13:11:18 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0339.001; Tue, 6 Dec 2011 13:11:18 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: AcyxakejwUXOElp7STCtYjgcemUphwDG63mAAAGEB4AAADFTAAAANTKAAAB3qAAAAGY5AAACDugAAAEzHIAAACKTgA==
Date: Tue, 6 Dec 2011 21:11:17 +0000
Message-ID: <521D1731-F4AD-471E-AF34-FAA22B7395EC@nominum.com>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com> <4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com> <4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com> <D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com> <95FDEE46-2731-4419-921B-1DA3A4F3FD92@gmail.com> <601EE481-E4B8-48DC-9885-0FB3302DC8CB@nominum.com> <4E70EB90-F9B2-46FB-8E4A-FB63429E94B9@gmail.com>
In-Reply-To: <4E70EB90-F9B2-46FB-8E4A-FB63429E94B9@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_521D1731F4AD471EAF34FAA22B7395ECnominumcom_"
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Tue, 06 Dec 2011 21:11:33 -0000

--_000_521D1731F4AD471EAF34FAA22B7395ECnominumcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Dec 6, 2011, at 4:07 PM, Ralph Droms wrote:
What is the inconsistency you see?

We're told to treat status codes as nested, but not what to do when we get =
an offer that contains an IA_PD and not an IA_NA, and not what to do when w=
e receive a status code that's not nested, and not what to do as a server i=
f we have to send status codes for both IA_PD and IA_NA.   Maybe "incomplet=
e" is a better choice of words, but the point is that if we just make these=
 four changes, we are going to create more permutations in acceptable set o=
f behaviors that servers and clients may follow.   This is really bad for i=
nteroperability, and we can't easily take it back once it's done.


--_000_521D1731F4AD471EAF34FAA22B7395ECnominumcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <2FAD908104CBA84897A598BE842062FD@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 6, 2011, at 4:07 PM, Ralph Droms wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">What
 is the inconsistency you see?<br>
</span></blockquote>
</div>
<br>
<div>We're told to treat status codes as nested, but not what to do when we=
 get an offer that contains an IA_PD and not an IA_NA, and not what to do w=
hen we receive a status code that's not nested, and not what to do as a ser=
ver if we have to send status codes
 for both IA_PD and IA_NA. &nbsp; Maybe &quot;incomplete&quot; is a better =
choice of words, but the point is that if we just make these four changes, =
we are going to create more permutations in acceptable set of behaviors tha=
t servers and clients may follow. &nbsp; This is really
 bad for interoperability, and we can't easily take it back once it's done.=
</div>
<div><br>
</div>
</body>
</html>

--_000_521D1731F4AD471EAF34FAA22B7395ECnominumcom_--

From ichiroumakino@gmail.com  Tue Dec  6 13:42:01 2011
Return-Path: <ichiroumakino@gmail.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 A39A321F8997 for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 13:42:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.474
X-Spam-Level: 
X-Spam-Status: No, score=-3.474 tagged_above=-999 required=5 tests=[AWL=0.125,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y1t79dcvDmaA for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 13:42:01 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id D942921F854E for <dhcwg@ietf.org>; Tue,  6 Dec 2011 13:42:00 -0800 (PST)
Received: by bkbzs8 with SMTP id zs8so232820bkb.31 for <dhcwg@ietf.org>; Tue, 06 Dec 2011 13:41:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=AcZhPICBMx5sAHjWuG1/PXnfU+oFiEXw+1CiXAhcbik=; b=T14yvCl7cRuEo2ahkXiOsjgYSwbWe8ZQ78mpmnFj9hQhg/NJM6r9+mkHxoDiWN2B/C 8uG+2hFg0cbqBlQ3nIsdCMwg0oZqPsQQchIXwiF9S9f3Y7KBMpl2WWBjT8B/Rp9aloNU zfkJLhuIFo1DpakLQoOWs1L1bN3XUVOrYz7jg=
Received: by 10.180.72.146 with SMTP id d18mr20132153wiv.12.1323207712590; Tue, 06 Dec 2011 13:41:52 -0800 (PST)
Received: from ams3-vpn-dhcp4725.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id bi9sm8038096wib.11.2011.12.06.13.41.50 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 06 Dec 2011 13:41:51 -0800 (PST)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <521D1731-F4AD-471E-AF34-FAA22B7395EC@nominum.com>
Date: Tue, 6 Dec 2011 22:41:49 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <964CFF2F-5E31-4221-A1CA-AF9C5AC00AF1@employees.org>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com> <4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com> <4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com> <D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com> <95FDEE46-2731-4419-921B-1DA3A4F3FD92@gmail.com> <601EE481-E4B8-48DC-9885-0FB3302DC8CB@nominum.com> <4E70EB90-F9B2-46FB-8E4A-FB63429E94B9@gmail.com> <521D1731-F4AD-471E-AF34-FAA22B7395EC@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1084)
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Tue, 06 Dec 2011 21:42:01 -0000

Ted,

>> What is the inconsistency you see?
>=20
> We're told to treat status codes as nested, but not what to do when we =
get an offer that contains an IA_PD and not an IA_NA, and not what to do =
when we receive a status code that's not nested, and not what to do as a =
server if we have to send status codes for both IA_PD and IA_NA.   Maybe =
"incomplete" is a better choice of words, but the point is that if we =
just make these four changes, we are going to create more permutations =
in acceptable set of behaviors that servers and clients may follow.   =
This is really bad for interoperability, and we can't easily take it =
back once it's done.

you have all the permutations today.
I was hoping this set of changes were all done as a "package", so that =
we also close this last loose thread. I don't think anyone suggested =
only doign the 4 existing errata(?)

cheers,
Ole=

From Ted.Lemon@nominum.com  Tue Dec  6 13:44:19 2011
Return-Path: <Ted.Lemon@nominum.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 AB2EF21F8573 for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 13:44:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.532
X-Spam-Level: 
X-Spam-Status: No, score=-106.532 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wtXtonKBXd4n for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 13:44:19 -0800 (PST)
Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id E25F121F856F for <dhcwg@ietf.org>; Tue,  6 Dec 2011 13:44:18 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob117.postini.com ([64.18.6.12]) with SMTP ID DSNKTt6MsStEmlU/Qv+KExqEtizTbbFc31UE@postini.com; Tue, 06 Dec 2011 13:44:18 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id E0C271B80D4 for <dhcwg@ietf.org>; Tue,  6 Dec 2011 13:44:16 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 45C19190052; Tue,  6 Dec 2011 13:44:14 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.01.0339.001; Tue, 6 Dec 2011 13:44:14 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ole Troan <otroan@employees.org>
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: AcyxakejwUXOElp7STCtYjgcemUphwDG63mAAAGEB4AAADFTAAAANTKAAAB3qAAAAGY5AAACDugAAAEzHIAAACKTgAABEBiAAAAWgAA=
Date: Tue, 6 Dec 2011 21:44:13 +0000
Message-ID: <9A58CC53-8756-43DF-8F22-B3A72CB855C6@nominum.com>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com> <4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com> <4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com> <D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com> <95FDEE46-2731-4419-921B-1DA3A4F3FD92@gmail.com> <601EE481-E4B8-48DC-9885-0FB3302DC8CB@nominum.com> <4E70EB90-F9B2-46FB-8E4A-FB63429E94B9@gmail.com> <521D1731-F4AD-471E-AF34-FAA22B7395EC@nominum.com> <964CFF2F-5E31-4221-A1CA-AF9C5AC00AF1@employees.org>
In-Reply-To: <964CFF2F-5E31-4221-A1CA-AF9C5AC00AF1@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_9A58CC53875643DF8F22B3A72CB855C6nominumcom_"
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Tue, 06 Dec 2011 21:44:19 -0000

--_000_9A58CC53875643DF8F22B3A72CB855C6nominumcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Dec 6, 2011, at 4:41 PM, Ole Troan wrote:
you have all the permutations today.
I was hoping this set of changes were all done as a "package", so that we a=
lso close this last loose thread. I don't think anyone suggested only doign=
 the 4 existing errata(?)

In that case we're in agreement.   I would really like it if someone else c=
ould carefully analyze the set of changes required to RFC3315 and propose t=
hem as a single erratum, and do the same for RFC3361.   I can do it, but I =
have a really long to-do list at the moment.   Of course, I suppose I'm not=
 unique in this... :)


--_000_9A58CC53875643DF8F22B3A72CB855C6nominumcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <218D894687E4DF4A96F76A90694678E2@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 6, 2011, at 4:41 PM, Ole Troan wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">you
 have all the permutations today.<br>
I was hoping this set of changes were all done as a &quot;package&quot;, so=
 that we also close this last loose thread. I don't think anyone suggested =
only doign the 4 existing errata(?)</span></blockquote>
</div>
<br>
<div>In that case we're in agreement. &nbsp; I would really like it if some=
one else could carefully analyze the set of changes required to RFC3315 and=
 propose them as a single erratum, and do the same for RFC3361. &nbsp; I ca=
n do it, but I have a really long to-do list
 at the moment. &nbsp; Of course, I suppose I'm not unique in this... :)</d=
iv>
<div><br>
</div>
</body>
</html>

--_000_9A58CC53875643DF8F22B3A72CB855C6nominumcom_--

From mohta@necom830.hpcl.titech.ac.jp  Tue Dec  6 13:54:09 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 2431521F851A for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 13:54:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.01
X-Spam-Level: 
X-Spam-Status: No, score=-0.01 tagged_above=-999 required=5 tests=[AWL=0.080,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4PuyVP11x-SX for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 13:54:08 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 4D87621F84B1 for <dhcwg@ietf.org>; Tue,  6 Dec 2011 13:54:08 -0800 (PST)
Received: (qmail 39614 invoked from network); 6 Dec 2011 22:21:05 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 6 Dec 2011 22:21:05 -0000
Message-ID: <4EDE8D38.9010807@necom830.hpcl.titech.ac.jp>
Date: Wed, 07 Dec 2011 06:46:32 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com><867F4B6A1672E541A94676D556793ACD0CB42FDABE@MOPESMBX01.eu.thmulti.com><BEA0EE13-9223-4D60-837C-AEAF74FAFD6E@nominum.com> <867F4B6A1672E541A94676D556793ACD0CB42FDB00@MOPESMBX01.eu.thmulti.com> <5B6B2B64C9FE2A489045EEEADDAFF2C30377869C@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C30377869C@XMB-RCD-109.cisco.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: dhc WG <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Tue, 06 Dec 2011 21:54:09 -0000

Hemant Singh (shemant) wrote:

> What happens
> when the RA and DHCPv6 have conflicting information and which
> information wins?

Wrong question.

The proper question to ask is:

	What if the RA and DHCPv6 have conflicting information?

and the answer is:

	That is an operational error, which can be solved only
	operationally.

	Implementations should report an error.

	There can not be such a thing as a fool proof protocol
	against all the foolish operations.

Then, more important question to ask is:

	What if ND is not used at all and some information is
	missing.

and the answer is:

	Operators will supply the missing information through
	DHCPv6 or some other protocol not necessarily under
	IETF control.

						Masataka Ohta

From shemant@cisco.com  Tue Dec  6 14:25:22 2011
Return-Path: <shemant@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 A4C3521F8C4A for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 14:25:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.525
X-Spam-Level: 
X-Spam-Status: No, score=-6.525 tagged_above=-999 required=5 tests=[AWL=0.074,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MMN6LuHMuYbP for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 14:25:22 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 0F19121F8C49 for <dhcwg@ietf.org>; Tue,  6 Dec 2011 14:25:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=420; q=dns/txt; s=iport; t=1323210322; x=1324419922; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=M3F4WMCI6zgJ0QCQ4agin3gqV69cw6a17nDiG7eR/no=; b=eQN/H3eXyhgMUETm9fhpXymPDCJ6aaa+5AluioEKnv2o9Nude7yoiEmq G3FNwXP6RXaN0eznyDvZF7x/p3uNu8jH6kwnEFy6k8U8DB4+LpDCUDR7R 3TEaiPtM1hbvrr5JqFxEXIUuk7pWqWG4AOWmCv8iqBpRnMw8pQ9yt+zvj c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao0AACeV3k6tJXG8/2dsb2JhbABDDpoQjmUBgVqBBYFyAQEBAwESAR0KPwUHBAIBCA4DBAEBCwYXAQYBRQkIAQEEEwgah2WXJgGeTYpPYwSILp4hVg
X-IronPort-AV: E=Sophos;i="4.71,309,1320624000"; d="scan'208";a="41677174"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-2.cisco.com with ESMTP; 06 Dec 2011 22:25:21 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core2-1.cisco.com (8.14.3/8.14.3) with ESMTP id pB6MPL7x015998;  Tue, 6 Dec 2011 22:25:21 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 6 Dec 2011 16:25:21 -0600
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 6 Dec 2011 16:25:20 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C303778E63@XMB-RCD-109.cisco.com>
In-Reply-To: <4EDE8D38.9010807@necom830.hpcl.titech.ac.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] To wait for RA or not to wait?
Thread-Index: Acy0YKKTrsX9+XqNQvKm18EE4auTyQABSf6g
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com><867F4B6A1672E541A94676D556793ACD0CB42FDABE@MOPESMBX01.eu.thmulti.com><BEA0EE13-9223-4D60-837C-AEAF74FAFD6E@nominum.com> <867F4B6A1672E541A94676D556793ACD0CB42FDB00@MOPESMBX01.eu.thmulti.com> <5B6B2B64C9FE2A489045EEEADDAFF2C30377869C@XMB-RCD-109.cisco.com> <4EDE8D38.9010807@necom830.hpcl.titech.ac.jp>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Masataka Ohta" <mohta@necom830.hpcl.titech.ac.jp>
X-OriginalArrivalTime: 06 Dec 2011 22:25:21.0997 (UTC) FILETIME=[F14D3FD0:01CCB465]
Cc: dhc WG <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Tue, 06 Dec 2011 22:25:22 -0000

-----Original Message-----
From: Masataka Ohta [mailto:mohta@necom830.hpcl.titech.ac.jp]=20
Sent: Tuesday, December 06, 2011 4:47 PM
To: Hemant Singh (shemant)
Cc: Wuyts Carl; Ted Lemon; dhc WG
Subject: Re: [dhcwg] To wait for RA or not to wait?

>	Implementations should report an error.

The implementation resides in a cable modem with no console.  The
implementation reports the error to who?

Hemant

From jmpolk@cisco.com  Tue Dec  6 17:04:02 2011
Return-Path: <jmpolk@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 1C0DC21F8586 for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 17:04:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.562
X-Spam-Level: 
X-Spam-Status: No, score=-106.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vw4KYBuzm1Ah for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 17:04:01 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 2FC7921F8509 for <dhcwg@ietf.org>; Tue,  6 Dec 2011 17:04:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=1554; q=dns/txt; s=iport; t=1323219841; x=1324429441; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=QbnvoLQCciIL/Hz0dQYV+3vLM6LBizuSEUyJD/NHJp4=; b=ItdN29wt4Qx5QH5Fh+ywDaIKGTd/inKar+InQUNor6i/bmMjpekSz5dA RLOhIGuEKjo/FpZhpmhYSXfI+0k/EN1TxdI88zHrCFNWPtZrrSBwxq393 gxBNovAwNxwUJC7SmK8OSKMDLM+sfWuIN3UR3ZEt18BZBlzobNR8sEbwA w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EACC73k6rRDoH/2dsb2JhbABDql6BBYFyAQEBBBIBJQI/EAcEGB4QGT4GNZ8bAZ14izIEiC6edw
X-IronPort-AV: E=Sophos;i="4.71,310,1320624000"; d="scan'208";a="18194022"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-4.cisco.com with ESMTP; 07 Dec 2011 01:04:01 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8711.cisco.com [10.99.80.18]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pB71408l026419; Wed, 7 Dec 2011 01:04:00 GMT
Message-Id: <201112070104.pB71408l026419@mtv-core-2.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 06 Dec 2011 19:04:05 -0600
To: Ted Lemon <Ted.Lemon@nominum.com>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <34043C82-5190-475B-8765-70B9C16FF4D7@nominum.com>
References: <6B961032-728D-43D6-81E3-9862EF9ADA09@gmail.com> <2207D364-CADB-43D2-907B-204180A6E4CC@nominum.com> <201110032203.p93M3f5I031107@mtv-core-3.cisco.com> <5EA79C2C-F4A2-4D88-85DC-E2F4B931E11A@nominum.com> <201110041732.p94HW6s3000630@mtv-core-1.cisco.com> <67AEBF45-5C47-43B4-B86C-482ED32E41D3@nominum.com> <201110042006.p94K6NX8001171@mtv-core-3.cisco.com> <578BA924-AE98-4B72-8857-949C9B76D6F6@nominum.com> <478F3A8B-6ADE-4BC2-BCBE-7214AD983727@gmail.com> <201110042057.p94KvlAJ004802@mtv-core-3.cisco.com> <C042ECF1-C246-4090-A4C6-6B20302227FA@gmail.com> <201112061938.pB6Jc3pD028634@mtv-core-3.cisco.com> <34043C82-5190-475B-8765-70B9C16FF4D7@nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [dhcwg] review of draft-ietf-geopriv-dhcp-lbyr-uri-option
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: Wed, 07 Dec 2011 01:04:02 -0000

At 02:36 PM 12/6/2011, Ted Lemon wrote:
>On Dec 6, 2011, at 2:38 PM, James M. Polk wrote:
>>Two folks have stated clearly on this list that the second lifetime 
>>timer <valid-for> (for considering whether or not the information 
>>at the location URI is good or stale (and needing a refresh)) is a 
>>bad idea within DHCP.  From this, I have 2 questions for this WG:
>>
>>#1 - do others agree?
>
>I'm one of the people who objected, so I guess I'm not "others," but 
>I definitely agree.
>
>>#2 - should the <valid-for> field (and idea) be removed from this ID?
>
>Yes.

I'm not forgetting you here, I'm just looking for others to jump on 
or state a different opinion.


>>As the doc's editor, I believe this is the last open item holding 
>>up this draft from progressing to the IESG.
>
>No, the other problem is that the document does not address the 
>rather serious problem of provisioning the DHCP server with these 
>URIs.   As I understand it, the expected use case is that the DHCP 
>server will contact some other server to figure out which URI to 
>send, before it sends the response to the DHCP client.   This is not 
>consistent with general practice, and I don't think it's an 
>appropriate use of the DHCP protocol.

not consistent - yet - there are 3 standards track RFCs that have 
this functionality at their core RFC 3825 (from 2004), RFC 4776 and 
RFC 6225 (admittedly 6225 obsoletes 3825), so this function is 
already in line with previous specifications from within Geopriv using DHCP.

James




From Ted.Lemon@nominum.com  Tue Dec  6 18:45:46 2011
Return-Path: <Ted.Lemon@nominum.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 47B7911E80A5 for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 18:45:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.534
X-Spam-Level: 
X-Spam-Status: No, score=-106.534 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q9nUf4rZbtHJ for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 18:45:45 -0800 (PST)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id DB6DF11E80A0 for <dhcwg@ietf.org>; Tue,  6 Dec 2011 18:45:44 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKTt7TTNONfncy/Gb3FYMdYbcP2/8a79j9@postini.com; Tue, 06 Dec 2011 18:45:44 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 01D5C1B8252 for <dhcwg@ietf.org>; Tue,  6 Dec 2011 18:45:32 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 8B1FF190052; Tue,  6 Dec 2011 18:45:30 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.01.0339.001; Tue, 6 Dec 2011 18:45:30 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "James M. Polk" <jmpolk@cisco.com>
Thread-Topic: [dhcwg] review of draft-ietf-geopriv-dhcp-lbyr-uri-option
Thread-Index: AQHMggfbXjkViOtBlkentTTh6SBa8ZVrha+AgAAcNwCAABC0gIABNcEAgAAB8YCAACkqgIAABVuAgAABvwCAAAdDgIAAARMAgGL8TwCAABBXgIAASruAgAAcVYA=
Date: Wed, 7 Dec 2011 02:45:30 +0000
Message-ID: <F0766A12-F4F6-4684-BFA5-B9DF9875186D@nominum.com>
References: <6B961032-728D-43D6-81E3-9862EF9ADA09@gmail.com> <2207D364-CADB-43D2-907B-204180A6E4CC@nominum.com> <201110032203.p93M3f5I031107@mtv-core-3.cisco.com> <5EA79C2C-F4A2-4D88-85DC-E2F4B931E11A@nominum.com> <201110041732.p94HW6s3000630@mtv-core-1.cisco.com> <67AEBF45-5C47-43B4-B86C-482ED32E41D3@nominum.com> <201110042006.p94K6NX8001171@mtv-core-3.cisco.com> <578BA924-AE98-4B72-8857-949C9B76D6F6@nominum.com> <478F3A8B-6ADE-4BC2-BCBE-7214AD983727@gmail.com> <201110042057.p94KvlAJ004802@mtv-core-3.cisco.com> <C042ECF1-C246-4090-A4C6-6B20302227FA@gmail.com> <201112061938.pB6Jc3pD028634@mtv-core-3.cisco.com> <34043C82-5190-475B-8765-70B9C16FF4D7@nominum.com> <201112070104.pB71408l026419@mtv-core-2.cisco.com>
In-Reply-To: <201112070104.pB71408l026419@mtv-core-2.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_F0766A12F4F64684BFA5B9DF9875186Dnominumcom_"
MIME-Version: 1.0
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, Robert Sparks <rjsparks@nostrum.com>
Subject: Re: [dhcwg] review of draft-ietf-geopriv-dhcp-lbyr-uri-option
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: Wed, 07 Dec 2011 02:45:46 -0000

--_000_F0766A12F4F64684BFA5B9DF9875186Dnominumcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

On Dec 6, 2011, at 8:04 PM, James M. Polk wrote:
not consistent - yet - there are 3 standards track RFCs that have this func=
tionality at their core RFC 3825 (from 2004), RFC 4776 and RFC 6225 (admitt=
edly 6225 obsoletes 3825), so this function is already in line with previou=
s specifications from within Geopriv using DHCP.

RFC3285 and RFC6225 were never last-called in the DHC working group, and go=
 quite strongly against existing practice.   I would like to see them depre=
cated=97I don't expect that they'll ever see significant adoption.   So the=
 fact that RFC6225 says to do something is not a good reason for future RFC=
s to say to do something similar.

Essentially the problem is that you've decided to use DHCP as a transport, =
and DHCP is not a transport.   If you need to do this sort of thing, you re=
ally ought to be doing it *after* DHCP, not as a part of DHCP.

BTW, these are my opinions; I'd be curious to know if other DHC working gro=
up participants agree, or think I'm out in left field.   In particular, has=
 anybody implemented RFC6225?


--_000_F0766A12F4F64684BFA5B9DF9875186Dnominumcom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <FE6EDFC364D5294891E0AA53D385FD11@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 6, 2011, at 8:04 PM, James M. Polk wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">not
 consistent - yet - there are 3 standards track RFCs that have this functio=
nality at their core RFC 3825 (from 2004), RFC 4776 and RFC 6225 (admittedl=
y 6225 obsoletes 3825), so this function is already in line with previous s=
pecifications from within Geopriv
 using DHCP.</span></blockquote>
</div>
<br>
<div>RFC3285 and RFC6225 were never last-called in the DHC working group, a=
nd go quite strongly against existing practice. &nbsp; I would like to see =
them deprecated=97I don't expect that they'll ever see significant adoption=
. &nbsp; So the fact that RFC6225 says to do
 something is not a good reason for future RFCs to say to do something simi=
lar.</div>
<div><br>
</div>
<div>Essentially the problem is that you've decided to use DHCP as a transp=
ort, and DHCP is not a transport. &nbsp; If you need to do this sort of thi=
ng, you really ought to be doing it *after* DHCP, not as a part of DHCP.&nb=
sp;</div>
<div><br>
</div>
<div>BTW, these are my opinions; I'd be curious to know if other DHC workin=
g group participants agree, or think I'm out in left field. &nbsp; In parti=
cular, has anybody implemented RFC6225?</div>
<div><br>
</div>
</body>
</html>

--_000_F0766A12F4F64684BFA5B9DF9875186Dnominumcom_--

From mohta@necom830.hpcl.titech.ac.jp  Tue Dec  6 19:19:46 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 34FE621F8BB6 for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 19:19:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.015
X-Spam-Level: 
X-Spam-Status: No, score=-0.015 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uzlGBagpf2nK for <dhcwg@ietfa.amsl.com>; Tue,  6 Dec 2011 19:19:42 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 6E6C611E80A0 for <dhcwg@ietf.org>; Tue,  6 Dec 2011 19:19:42 -0800 (PST)
Received: (qmail 45442 invoked from network); 7 Dec 2011 03:53:09 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 7 Dec 2011 03:53:09 -0000
Message-ID: <4EDEDB21.4090902@necom830.hpcl.titech.ac.jp>
Date: Wed, 07 Dec 2011 12:18:57 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com><867F4B6A1672E541A94676D556793ACD0CB42FDABE@MOPESMBX01.eu.thmulti.com><BEA0EE13-9223-4D60-837C-AEAF74FAFD6E@nominum.com> <867F4B6A1672E541A94676D556793ACD0CB42FDB00@MOPESMBX01.eu.thmulti.com> <5B6B2B64C9FE2A489045EEEADDAFF2C30377869C@XMB-RCD-109.cisco.com> <4EDE8D38.9010807@necom830.hpcl.titech.ac.jp> <5B6B2B64C9FE2A489045EEEADDAFF2C303778E63@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C303778E63@XMB-RCD-109.cisco.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Wed, 07 Dec 2011 03:19:46 -0000

Hemant Singh (shemant) wrote:

>> 	Implementations should report an error.

> The implementation resides in a cable modem with no console.

Can't the cable modem send its own packet?

> The implementation reports the error to who?

Operators.

						Masataka Ohta

From shemant@cisco.com  Wed Dec  7 09:22:19 2011
Return-Path: <shemant@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 4749F21F8C89 for <dhcwg@ietfa.amsl.com>; Wed,  7 Dec 2011 09:22:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.527
X-Spam-Level: 
X-Spam-Status: No, score=-6.527 tagged_above=-999 required=5 tests=[AWL=0.072,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HFKbYaIpt1o6 for <dhcwg@ietfa.amsl.com>; Wed,  7 Dec 2011 09:22:18 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id A448521F8C88 for <dhcwg@ietf.org>; Wed,  7 Dec 2011 09:22:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=414; q=dns/txt; s=iport; t=1323278537; x=1324488137; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=6OiDwZu4LAeGS0nCUJpLo8Dh9O+siydE5a2MgZyrcqU=; b=Dn5fvSp3OS7IKTRTUdWFOlVbSsgda5y+DIu883Gp3d8zrX0t0uYuxOpl MF8826rUPcsoyAho4QhKHye/5ti9neVOrlc8A7UX1DqWYY8tj2mRDD3xj 4ZuBpAIbjYOPptnJdWuWRBLxFVCHZQHVAJLa6l0cYdPBFUY7v/3y4mq3A M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArQAAOyf306tJXHA/2dsb2JhbABDDpoVjlcBgVmBBYFyAQEBBBIBHQpLBAIBCA4DBAEBCwYXAQYBRQkIAQEEARIIGqA9AZ4wilFjBIgunilW
X-IronPort-AV: E=Sophos;i="4.71,315,1320624000"; d="scan'208";a="41957640"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-7.cisco.com with ESMTP; 07 Dec 2011 17:22:14 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core2-5.cisco.com (8.14.3/8.14.3) with ESMTP id pB7HMEkm031800;  Wed, 7 Dec 2011 17:22:14 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 7 Dec 2011 11:22:14 -0600
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 7 Dec 2011 11:22:13 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C3037790E1@XMB-RCD-109.cisco.com>
In-Reply-To: <4EDEDB21.4090902@necom830.hpcl.titech.ac.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] To wait for RA or not to wait?
Thread-Index: Acy0jxSEP5pNNNktR/Kd3d9y2itLbwAdYUxg
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com><867F4B6A1672E541A94676D556793ACD0CB42FDABE@MOPESMBX01.eu.thmulti.com><BEA0EE13-9223-4D60-837C-AEAF74FAFD6E@nominum.com><867F4B6A1672E541A94676D556793ACD0CB42FDB00@MOPESMBX01.eu.thmulti.com><5B6B2B64C9FE2A489045EEEADDAFF2C30377869C@XMB-RCD-109.cisco.com><4EDE8D38.9010807@necom830.hpcl.titech.ac.jp><5B6B2B64C9FE2A489045EEEADDAFF2C303778E63@XMB-RCD-109.cisco.com> <4EDEDB21.4090902@necom830.hpcl.titech.ac.jp>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Masataka Ohta" <mohta@necom830.hpcl.titech.ac.jp>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 07 Dec 2011 17:22:14.0407 (UTC) FILETIME=[C3110170:01CCB504]
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Wed, 07 Dec 2011 17:22:19 -0000

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Masataka Ohta
Sent: Tuesday, December 06, 2011 10:19 PM
To: dhcwg@ietf.org
Subject: Re: [dhcwg] To wait for RA or not to wait?

>Can't the cable modem send its own packet?

Send how and using what protocol?  New protocol would have to be
developed.

>Operators.

Using what protocol?

Hemant

From rdroms.ietf@gmail.com  Wed Dec  7 11:01:24 2011
Return-Path: <rdroms.ietf@gmail.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 BFDB521F8B87 for <dhcwg@ietfa.amsl.com>; Wed,  7 Dec 2011 11:01:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hBwVXzH2YJLT for <dhcwg@ietfa.amsl.com>; Wed,  7 Dec 2011 11:01:24 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2C40B21F8B84 for <dhcwg@ietf.org>; Wed,  7 Dec 2011 11:01:24 -0800 (PST)
Received: by qcsf15 with SMTP id f15so790607qcs.31 for <dhcwg@ietf.org>; Wed, 07 Dec 2011 11:01:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=H6sAwDhx89r830Q47fwAwrM/DGkvb/PEO44HbjHOsAI=; b=HulZZi1HSyAd0n4PRuRCR0fv72rhbF71/UTe1i/3lVyhZlzWHP7CmvIrMk3cvCh9nn fOFb/axPsic7etCHwEun++GUGzqtuDo617dGzmRD9E9OBm9XmkcwQhYafwmg1ljoe3W5 WA5zpB0GxX3WwMLlxaVrNiffXlTBpHl9Qt5gQ=
Received: by 10.229.3.141 with SMTP id 13mr18963qcn.147.1323284482672; Wed, 07 Dec 2011 11:01:22 -0800 (PST)
Received: from [161.44.65.173] ([161.44.65.173]) by mx.google.com with ESMTPS id j7sm4919097qaq.11.2011.12.07.11.01.20 (version=SSLv3 cipher=OTHER); Wed, 07 Dec 2011 11:01:21 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <9A58CC53-8756-43DF-8F22-B3A72CB855C6@nominum.com>
Date: Wed, 7 Dec 2011 14:01:19 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <088C56B4-8B06-4736-8FAC-1CF6FCE1A556@gmail.com>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com> <4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com> <4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com> <D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com> <95FDEE46-2731-4419-921B-1DA3A4F3FD92@gmail.com> <601EE481-E4B8-48DC-9885-0FB3302DC8CB@nominum.com> <4E70EB90-F9B2-46FB-8E4A-FB63429E94B9@gmail.com> <521D1731-F4AD-471E-AF34-FAA22B7395EC@nominum.com> <964CFF2F-5E31-4221-A1CA-AF9C5AC00AF1@employees.org> <9A58CC53-8756-43DF-8F22-B3A72CB855C6@nominum.com>
To: dhc WG <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
Cc: Ralph Droms <rdroms.ietf@gmail.com>, Lemon Ted <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Wed, 07 Dec 2011 19:01:24 -0000

dhc WG - it is important that we get a discussion on these errata and =
related changes from which the chairs and I can determine a consensus =
for a solution.  If the dhc WG doesn't approve/extend/update the errata =
and other changes required by the errata, the work will be done =
elsewhere ... and it really *should* be done here in the dhc WG.

If you have questions about the nature of the problem, the use scenario, =
etc., please ask...

- Ralph

On Dec 6, 2011, at 4:44 PM 12/6/11, Ted Lemon wrote:

> On Dec 6, 2011, at 4:41 PM, Ole Troan wrote:
>> you have all the permutations today.
>> I was hoping this set of changes were all done as a "package", so =
that we also close this last loose thread. I don't think anyone =
suggested only doign the 4 existing errata(?)
>=20
> In that case we're in agreement.   I would really like it if someone =
else could carefully analyze the set of changes required to RFC3315 and =
propose them as a single erratum, and do the same for RFC3361.   I can =
do it, but I have a really long to-do list at the moment.   Of course, I =
suppose I'm not unique in this... :)
>=20


From mohta@necom830.hpcl.titech.ac.jp  Wed Dec  7 12:46:32 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 ED2CD1F0C59 for <dhcwg@ietfa.amsl.com>; Wed,  7 Dec 2011 12:46:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.02
X-Spam-Level: 
X-Spam-Status: No, score=-0.02 tagged_above=-999 required=5 tests=[AWL=0.070,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wlp2woxy1u16 for <dhcwg@ietfa.amsl.com>; Wed,  7 Dec 2011 12:46:32 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 294811F0C58 for <dhcwg@ietf.org>; Wed,  7 Dec 2011 12:46:32 -0800 (PST)
Received: (qmail 59043 invoked from network); 7 Dec 2011 21:20:14 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 7 Dec 2011 21:20:14 -0000
Message-ID: <4EDFD071.7090107@necom830.hpcl.titech.ac.jp>
Date: Thu, 08 Dec 2011 05:45:37 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com><867F4B6A1672E541A94676D556793ACD0CB42FDABE@MOPESMBX01.eu.thmulti.com><BEA0EE13-9223-4D60-837C-AEAF74FAFD6E@nominum.com><867F4B6A1672E541A94676D556793ACD0CB42FDB00@MOPESMBX01.eu.thmulti.com><5B6B2B64C9FE2A489045EEEADDAFF2C30377869C@XMB-RCD-109.cisco.com><4EDE8D38.9010807@necom830.hpcl.titech.ac.jp><5B6B2B64C9FE2A489045EEEADDAFF2C303778E63@XMB-RCD-109.cisco.com> <4EDEDB21.4090902@necom830.hpcl.titech.ac.jp> <5B6B2B64C9FE2A489045EEEADDAFF2C3037790E1@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C3037790E1@XMB-RCD-109.cisco.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Wed, 07 Dec 2011 20:46:33 -0000

Hemant Singh (shemant) wrote:

>> Can't the cable modem send its own packet?
> 
> Send how and using what protocol?

It's like asking "what standard is used between a cable modem
monitoring PC and its console".

Let operators decide.

> New protocol would have to be
> developed.

Operators may or may not, though most will use existing ones
such as syslog.

					Masataka Ohta

From Ted.Lemon@nominum.com  Wed Dec  7 13:40:02 2011
Return-Path: <Ted.Lemon@nominum.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 6902421F8AD6 for <dhcwg@ietfa.amsl.com>; Wed,  7 Dec 2011 13:40:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.536
X-Spam-Level: 
X-Spam-Status: No, score=-106.536 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1FA6dXGIwvjH for <dhcwg@ietfa.amsl.com>; Wed,  7 Dec 2011 13:40:01 -0800 (PST)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id 01EDC21F8A69 for <dhcwg@ietf.org>; Wed,  7 Dec 2011 13:39:59 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKTt/dLXSS02MIg7VJG4bU8Kf/Mc88dITR@postini.com; Wed, 07 Dec 2011 13:40:00 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 162AA1B82C2 for <dhcwg@ietf.org>; Wed,  7 Dec 2011 13:39:57 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 0232B190052; Wed,  7 Dec 2011 13:39:57 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0339.001; Wed, 7 Dec 2011 13:39:56 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Robert Sparks <rjsparks@nostrum.com>
Thread-Topic: [dhcwg] review of draft-ietf-geopriv-dhcp-lbyr-uri-option
Thread-Index: AQHMggfbXjkViOtBlkentTTh6SBa8ZVrha+AgAAcNwCAABC0gIABNcEAgAAB8YCAACkqgIAABVuAgAABvwCAAAdDgIAAARMAgGL8TwCAABBXgIAASruAgAAcVYCAATqAAIAAAnYA
Date: Wed, 7 Dec 2011 21:39:56 +0000
Message-ID: <B109A44F-7F49-407A-89DD-8EA50E56BBB4@nominum.com>
References: <6B961032-728D-43D6-81E3-9862EF9ADA09@gmail.com> <2207D364-CADB-43D2-907B-204180A6E4CC@nominum.com> <201110032203.p93M3f5I031107@mtv-core-3.cisco.com> <5EA79C2C-F4A2-4D88-85DC-E2F4B931E11A@nominum.com> <201110041732.p94HW6s3000630@mtv-core-1.cisco.com> <67AEBF45-5C47-43B4-B86C-482ED32E41D3@nominum.com> <201110042006.p94K6NX8001171@mtv-core-3.cisco.com> <578BA924-AE98-4B72-8857-949C9B76D6F6@nominum.com> <478F3A8B-6ADE-4BC2-BCBE-7214AD983727@gmail.com> <201110042057.p94KvlAJ004802@mtv-core-3.cisco.com> <C042ECF1-C246-4090-A4C6-6B20302227FA@gmail.com> <201112061938.pB6Jc3pD028634@mtv-core-3.cisco.com> <34043C82-5190-475B-8765-70B9C16FF4D7@nominum.com> <201112070104.pB71408l026419@mtv-core-2.cisco.com> <F0766A12-F4F6-4684-BFA5-B9DF9875186D@nominum.com> <4EDFDB1C.3040102@nostrum.com>
In-Reply-To: <4EDFDB1C.3040102@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_B109A44F7F49407A89DD8EA50E56BBB4nominumcom_"
MIME-Version: 1.0
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>, "James M. Polk" <jmpolk@cisco.com>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] review of draft-ietf-geopriv-dhcp-lbyr-uri-option
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: Wed, 07 Dec 2011 21:40:02 -0000

--_000_B109A44F7F49407A89DD8EA50E56BBB4nominumcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

On Dec 7, 2011, at 4:31 PM, Robert Sparks wrote:
For 6225, there could be an external service that's always letting the serv=
er know where a given dhc client
is, whether the client is asking or not, and while there are easy to envisi=
on scenarios where that wouldn't
be reasonable for scaling reasons (you would want the external service to b=
e a little more clever in what it
chose to provide), I don't think that actually violates existing practice.

What is the *actual* deployment scenario?


--_000_B109A44F7F49407A89DD8EA50E56BBB4nominumcom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <397CA60E01314142B5DA4D80381D52CA@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 7, 2011, at 4:31 PM, Robert Sparks wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">For
 6225, there could be an external service that's always letting the server =
know where a given dhc client<br>
is, whether the client is asking or not, and while there are easy to envisi=
on scenarios where that wouldn't<br>
be reasonable for scaling reasons (you would want the external service to b=
e a little more clever in what it<br>
chose to provide), I don't think that actually violates existing practice.<=
/span></blockquote>
</div>
<br>
<div>What is the *actual* deployment scenario?</div>
<div><br>
</div>
</body>
</html>

--_000_B109A44F7F49407A89DD8EA50E56BBB4nominumcom_--

From rjsparks@nostrum.com  Wed Dec  7 13:31:15 2011
Return-Path: <rjsparks@nostrum.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 E45A311E80AE for <dhcwg@ietfa.amsl.com>; Wed,  7 Dec 2011 13:31:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z1Wz-sKK9nyB for <dhcwg@ietfa.amsl.com>; Wed,  7 Dec 2011 13:31:15 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 21B9C11E808A for <dhcwg@ietf.org>; Wed,  7 Dec 2011 13:31:14 -0800 (PST)
Received: from dn3-177.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id pB7LV8dX001455 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 7 Dec 2011 15:31:10 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <4EDFDB1C.3040102@nostrum.com>
Date: Wed, 07 Dec 2011 15:31:08 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <6B961032-728D-43D6-81E3-9862EF9ADA09@gmail.com> <2207D364-CADB-43D2-907B-204180A6E4CC@nominum.com> <201110032203.p93M3f5I031107@mtv-core-3.cisco.com> <5EA79C2C-F4A2-4D88-85DC-E2F4B931E11A@nominum.com> <201110041732.p94HW6s3000630@mtv-core-1.cisco.com> <67AEBF45-5C47-43B4-B86C-482ED32E41D3@nominum.com> <201110042006.p94K6NX8001171@mtv-core-3.cisco.com> <578BA924-AE98-4B72-8857-949C9B76D6F6@nominum.com> <478F3A8B-6ADE-4BC2-BCBE-7214AD983727@gmail.com> <201110042057.p94KvlAJ004802@mtv-core-3.cisco.com> <C042ECF1-C246-4090-A4C6-6B20302227FA@gmail.com> <201112061938.pB6Jc3pD028634@mtv-core-3.cisco.com> <34043C82-5190-475B-8765-70B9C16FF4D7@nominum.com> <201112070104.pB71408l026419@mtv-core-2.cisco.com> <F0766A12-F4F6-4684-BFA5-B9DF9875186D@nominum.com>
In-Reply-To: <F0766A12-F4F6-4684-BFA5-B9DF9875186D@nominum.com>
Content-Type: multipart/alternative; boundary="------------030707020006010009070808"
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-Mailman-Approved-At: Wed, 07 Dec 2011 13:40:26 -0800
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>, "James M. Polk" <jmpolk@cisco.com>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] review of draft-ietf-geopriv-dhcp-lbyr-uri-option
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: Wed, 07 Dec 2011 21:31:16 -0000

This is a multi-part message in MIME format.
--------------030707020006010009070808
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

On 12/6/11 8:45 PM, Ted Lemon wrote:
> On Dec 6, 2011, at 8:04 PM, James M. Polk wrote:
>> not consistent - yet - there are 3 standards track RFCs that have 
>> this functionality at their core RFC 3825 (from 2004), RFC 4776 and 
>> RFC 6225 (admittedly 6225 obsoletes 3825), so this function is 
>> already in line with previous specifications from within Geopriv 
>> using DHCP.
>
> RFC3285 and RFC6225 were never last-called in the DHC working group, 
> and go quite strongly against existing practice.   I would like to see 
> them deprecated—I don't expect that they'll ever see significant 
> adoption.   So the fact that RFC6225 says to do something is not a 
> good reason for future RFCs to say to do something similar.
>
> Essentially the problem is that you've decided to use DHCP as a 
> transport, and DHCP is not a transport.   If you need to do this sort 
> of thing, you really ought to be doing it *after* DHCP, not as a part 
> of DHCP.
>
> BTW, these are my opinions; I'd be curious to know if other DHC 
> working group participants agree, or think I'm out in left field.   In 
> particular, has anybody implemented RFC6225?
>
Ted -

If I've understood what you've written before, I don't think 6225 goes 
as strongly against existing practice
as you state here, and I'd like to uplevel a little to see if I have, in 
fact, understood correctly.

If I have it right, the essence of (this part of) your concern is that a 
dhcp server can't be constrained
to go ask an external process for the information it needs to respond to 
a request. That is, it needs
to be able to respond to the request with the data it has at the time 
the request arrives. The operational
model is that the data you have to respond with is the kind of stuff the 
server admin would enter as
configuration (and it's possible that the admin would need to type very 
fast). It would be ok for an external
process to be providing new information, but not ok to require the 
server to ask that external process for
information (or wait on it if information became stale, etc.)

For 6225, there could be an external service that's always letting the 
server know where a given dhc client
is, whether the client is asking or not, and while there are easy to 
envision scenarios where that wouldn't
be reasonable for scaling reasons (you would want the external service 
to be a little more clever in what it
chose to provide), I don't think that actually violates existing practice.

Am I completely wrong?

If I'm not wrong, then I think I have suggestions for changes to the 
dhcp-lbyr-uri-option draft that would
address this part of the concern.

RjS




--------------030707020006010009070808
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    On 12/6/11 8:45 PM, Ted Lemon wrote:
    <blockquote
      cite="mid:F0766A12-F4F6-4684-BFA5-B9DF9875186D@nominum.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div>
        <div>On Dec 6, 2011, at 8:04 PM, James M. Polk wrote:</div>
        <blockquote type="cite"><span class="Apple-style-span"
            style="border-collapse: separate; font-family: Helvetica;
            font-style: normal; font-variant: normal; font-weight:
            normal; letter-spacing: normal; line-height: normal;
            orphans: 2; text-align: -webkit-auto; text-indent: 0px;
            text-transform: none; white-space: normal; widows: 2;
            word-spacing: 0px; -webkit-border-horizontal-spacing: 0px;
            -webkit-border-vertical-spacing: 0px;
            -webkit-text-decorations-in-effect: none;
            -webkit-text-size-adjust: auto; -webkit-text-stroke-width:
            0px; font-size: medium; ">not consistent - yet - there are 3
            standards track RFCs that have this functionality at their
            core RFC 3825 (from 2004), RFC 4776 and RFC 6225 (admittedly
            6225 obsoletes 3825), so this function is already in line
            with previous specifications from within Geopriv using DHCP.</span></blockquote>
      </div>
      <br>
      <div>RFC3285 and RFC6225 were never last-called in the DHC working
        group, and go quite strongly against existing practice.   I
        would like to see them deprecated—I don't expect that they'll
        ever see significant adoption.   So the fact that RFC6225 says
        to do something is not a good reason for future RFCs to say to
        do something similar.</div>
      <div><br>
      </div>
      <div>Essentially the problem is that you've decided to use DHCP as
        a transport, and DHCP is not a transport.   If you need to do
        this sort of thing, you really ought to be doing it *after*
        DHCP, not as a part of DHCP. </div>
      <div><br>
      </div>
      <div>BTW, these are my opinions; I'd be curious to know if other
        DHC working group participants agree, or think I'm out in left
        field.   In particular, has anybody implemented RFC6225?</div>
      <div><br>
      </div>
    </blockquote>
    Ted - <br>
    <br>
    If I've understood what you've written before, I don't think 6225
    goes as strongly against existing practice<br>
    as you state here, and I'd like to uplevel a little to see if I
    have, in fact, understood correctly.<br>
    <br>
    If I have it right, the essence of (this part of) your concern is
    that a dhcp server can't be constrained<br>
    to go ask an external process for the information it needs to
    respond to a request. That is, it needs<br>
    to be able to respond to the request with the data it has at the
    time the request arrives. The operational<br>
    model is that the data you have to respond with is the kind of stuff
    the server admin would enter as<br>
    configuration (and it's possible that the admin would need to type
    very fast). It would be ok for an external<br>
    process to be providing new information, but not ok to require the
    server to ask that external process for<br>
    information (or wait on it if information became stale, etc.)<br>
    <br>
    For 6225, there could be an external service that's always letting
    the server know where a given dhc client<br>
    is, whether the client is asking or not, and while there are easy to
    envision scenarios where that wouldn't<br>
    be reasonable for scaling reasons (you would want the external
    service to be a little more clever in what it<br>
    chose to provide), I don't think that actually violates existing
    practice.<br>
    <br>
    Am I completely wrong?<br>
    <br>
    If I'm not wrong, then I think I have suggestions for changes to the
    dhcp-lbyr-uri-option draft that would<br>
    address this part of the concern.<br>
    <br>
    RjS<br>
    <br>
     <br>
    <br>
  </body>
</html>

--------------030707020006010009070808--

From Carl.Wuyts@technicolor.com  Wed Dec  7 23:39:49 2011
Return-Path: <Carl.Wuyts@technicolor.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 C5EDC11E8080 for <dhcwg@ietfa.amsl.com>; Wed,  7 Dec 2011 23:39:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.737
X-Spam-Level: 
X-Spam-Status: No, score=-5.737 tagged_above=-999 required=5 tests=[AWL=0.262,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yZNnBEPh6yRs for <dhcwg@ietfa.amsl.com>; Wed,  7 Dec 2011 23:39:49 -0800 (PST)
Received: from na3sys009aog109.obsmtp.com (na3sys009aog109.obsmtp.com [74.125.149.201]) by ietfa.amsl.com (Postfix) with ESMTP id CE26611E807F for <dhcwg@ietf.org>; Wed,  7 Dec 2011 23:39:46 -0800 (PST)
Received: from mopesedge02.eu.thmulti.com ([129.35.174.203]) (using TLSv1) by na3sys009aob109.postini.com ([74.125.148.12]) with SMTP ID DSNKTuBptox80eD/1QjG0/QqzOGClfUpMI44@postini.com; Wed, 07 Dec 2011 23:39:48 PST
Received: from MOPESMAILHC01.eu.thmulti.com (141.11.100.25) by mopesedge02.eu.thmulti.com (141.11.253.23) with Microsoft SMTP Server (TLS) id 8.3.192.1; Thu, 8 Dec 2011 08:38:14 +0100
Received: from MOPESMBX01.eu.thmulti.com ([169.254.155.121]) by MOPESMAILHC01.eu.thmulti.com ([141.11.100.25]) with mapi; Thu, 8 Dec 2011 08:38:22 +0100
From: Wuyts Carl <Carl.Wuyts@technicolor.com>
To: Ole Troan <otroan@employees.org>, Ted Lemon <Ted.Lemon@nominum.com>
Date: Thu, 8 Dec 2011 08:38:21 +0100
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: AcyxrvDLFRNpP0jPR/yTrpdNLgYP9QDyptfA
Message-ID: <867F4B6A1672E541A94676D556793ACD0CB445C90C@MOPESMBX01.eu.thmulti.com>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com> <66EBF10F-A971-48BD-968B-1202CBF94B49@employees.org>
In-Reply-To: <66EBF10F-A971-48BD-968B-1202CBF94B49@employees.org>
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: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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, 08 Dec 2011 07:39:49 -0000

All,

I think solution 3, i.e. including ia_na in renew if not received, would be=
 ok for us.

Some additional remark/Q:
While TR181 was progressing on defining the DHCPv6 part some time ago, we'v=
e already given some feedback on the modelling, e.g. the model has been mad=
e as such that 1 DHCPv6 client can "connect" to several DHCPv6 servers at t=
he SAME time.  So, in order to get you options, you can potentially get the=
m from different DHCPv6 servers.  (so, not to check who can give you what o=
ptions, but really to fetch options from different servers at the same time=
)

Now I read the below discussion on what to do if no ia_na gets provided, on=
ly ia_pd.

Maybe I'm cutting some corners here, but I think the main thing missing in =
the RFC3315 is a clear state machine.  This opens up the gate for interpret=
ations.  I've asked our BBF representative back then to challenge the autho=
rs to provide us the procedure (i.e. state machine) to use when an option w=
ould have either different content, is no longer available at some server, =
...  I've seen nothing on it.

Today, I've bumped onto this discussion.  As mentioned already, solution 3,=
 including the ia_na in the renew if not received sounds reasonable to us, =
but I saw some other possibilities like continuing to send discovers for th=
e ia_na only.  I must say I'm quite surprised to see this kind of proposal =
??!!
The same applies here: clear state machine would help a lot in these matter=
s.

Regs
Carl





-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of O=
le Troan
Sent: zaterdag 3 december 2011 12:30
To: Ted Lemon
Cc: dhc WG
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...

Ted,

s/3361/3633/g

phrased another way:
do we think we can do better than treating each stateful DHCPv6 option (IA_=
NA, IA_TA, IA_PD) as separate protocol instances?
as in:
A DHCPv6 client MUST initiate a separate session for each IA_ option it wil=
l request. DHCPv6 message behaviour and initiation will have slight variati=
ons per option type. A DHCPv6 server that has more than one stateful option=
 to give to a client, MUST only include the requested IA_ option in any rep=
ly to the client.

cheers,
Ole

On Dec 3, 2011, at 4:18 , Ted Lemon wrote:

> There's been a bit of a discussion going on in the v6ops working group ab=
out a problem in the DHCP protocol that has to do with the coexistence of s=
tateful address allocation and prefix delegation.
>=20
> The problem is that it's entirely possible that a PD requesting router mi=
ght also want an IP address to number its upstream interface, so it might s=
end a DHCP Solicit message containing both an IA_NA and an IA_PD.    Suppos=
e the DHCP server is willing to do prefix delegation, but expects the RR to=
 do SLAAC for the upstream address.   In this case, it's going to send an I=
A_PD containing one or more prefixes, but an IA_NA containing no addresses.
>=20
> RFC3315 wasn't written with RFC3361 in mind, so it doesn't really talk ab=
out what to do in this case.   It also doesn't address the problem of what =
to do if an IA_TA appears in the solicit, but the server isn't configured t=
o offer temporary addresses.   This hasn't been much of an issue since I do=
n't know of any clients that actually request temporary addresses, but of c=
ourse it is an issue for IA_PD.
>=20
> There exist two errata that address this issue: erratum 2471 and erratum =
2472.   These errata propose to have the status code appear inside the IA_N=
A option rather than in the outer layer of the Advertise message.   A simil=
ar erratum exists for RFC3361, proposing to put the status code option in t=
he IA_PD option instead of, similarly, in the outer layer of the packet.
>=20
> In addition, the following observation has been made:
>=20
>  The other unclear problem area is around how to deal with IA_PD and IA_N=
A:
>    * Client requests both IA_NA and IA_PD in the same session, gets only =
IA_PD.
>      - Does it fork off a separate session for IA_NA and continues sendin=
g SOLICITs for only the IA_NA?
>      - Reset the DHCP client, and tries again?
>      - Keeps single session, and continues to ask for IA_NA on next RENEW=
?
>=20
>      all 3 behaviors have been seen in the wild plus some additional path=
ological cases.
>      in general dealing with multiple stateful options in DHCP is undersp=
ecified.
>=20
> So the topic for discussion in the working group here is as follows:
>=20
> 1. Is what is proposed in the errata the right thing?   Should we in fact=
 have status codes inside of IA_* options instead of in the main packet?
>=20
> 2. If so, what is the full set of edits to RFC3315 and RFC3361 that are r=
equired to do this?
> 2a. What do we do for clients that don't implement the errata?
>=20
> 3. If not, what should we do instead?
>=20
> 4. If the client gets an IA_NA and no IA_PD, or vice versa, which of the =
three behaviors listed above should it follow?   Is it bad that different c=
lients do this differently?
>=20
> 5. What have I missed?
>=20
> Comments?   Criticisms?   Rotten tomatoes?
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

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

From Ted.Lemon@nominum.com  Thu Dec  8 09:27:13 2011
Return-Path: <Ted.Lemon@nominum.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 3848F21F8B70 for <dhcwg@ietfa.amsl.com>; Thu,  8 Dec 2011 09:27:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.538
X-Spam-Level: 
X-Spam-Status: No, score=-106.538 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f3pnUYeUuEjj for <dhcwg@ietfa.amsl.com>; Thu,  8 Dec 2011 09:27:12 -0800 (PST)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by ietfa.amsl.com (Postfix) with ESMTP id 4505E21F8B5C for <dhcwg@ietf.org>; Thu,  8 Dec 2011 09:27:10 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKTuDzbbmmLPdgRs8wuck0FqkcOU67FOzh@postini.com; Thu, 08 Dec 2011 09:27:10 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 386E11B82D9 for <dhcwg@ietf.org>; Thu,  8 Dec 2011 09:27:09 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 227F1190052; Thu,  8 Dec 2011 09:27:09 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0339.001; Thu, 8 Dec 2011 09:27:09 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Robert Sparks <rjsparks@nostrum.com>
Thread-Topic: [dhcwg] review of draft-ietf-geopriv-dhcp-lbyr-uri-option
Thread-Index: AQHMggfbXjkViOtBlkentTTh6SBa8ZVrha+AgAAcNwCAABC0gIABNcEAgAAB8YCAACkqgIAABVuAgAABvwCAAAdDgIAAARMAgGL8TwCAABBXgIAASruAgAAcVYCAATqAAIABTicA
Date: Thu, 8 Dec 2011 17:27:08 +0000
Message-ID: <DD9D3CC6-715B-4C14-8303-1E4810E5343E@nominum.com>
References: <6B961032-728D-43D6-81E3-9862EF9ADA09@gmail.com> <2207D364-CADB-43D2-907B-204180A6E4CC@nominum.com> <201110032203.p93M3f5I031107@mtv-core-3.cisco.com> <5EA79C2C-F4A2-4D88-85DC-E2F4B931E11A@nominum.com> <201110041732.p94HW6s3000630@mtv-core-1.cisco.com> <67AEBF45-5C47-43B4-B86C-482ED32E41D3@nominum.com> <201110042006.p94K6NX8001171@mtv-core-3.cisco.com> <578BA924-AE98-4B72-8857-949C9B76D6F6@nominum.com> <478F3A8B-6ADE-4BC2-BCBE-7214AD983727@gmail.com> <201110042057.p94KvlAJ004802@mtv-core-3.cisco.com> <C042ECF1-C246-4090-A4C6-6B20302227FA@gmail.com> <201112061938.pB6Jc3pD028634@mtv-core-3.cisco.com> <34043C82-5190-475B-8765-70B9C16FF4D7@nominum.com> <201112070104.pB71408l026419@mtv-core-2.cisco.com> <F0766A12-F4F6-4684-BFA5-B9DF9875186D@nominum.com> <4EDFDB1C.3040102@nostrum.com>
In-Reply-To: <4EDFDB1C.3040102@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_DD9D3CC6715B4C1483031E4810E5343Enominumcom_"
MIME-Version: 1.0
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>, "James M. Polk" <jmpolk@cisco.com>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] review of draft-ietf-geopriv-dhcp-lbyr-uri-option
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, 08 Dec 2011 17:27:13 -0000

--_000_DD9D3CC6715B4C1483031E4810E5343Enominumcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

On Dec 7, 2011, at 4:31 PM, Robert Sparks wrote:
If I have it right, the essence of (this part of) your concern is that a dh=
cp server can't be constrained
to go ask an external process for the information it needs to respond to a =
request. That is, it needs
to be able to respond to the request with the data it has at the time the r=
equest arrives. The operational
model is that the data you have to respond with is the kind of stuff the se=
rver admin would enter as
configuration (and it's possible that the admin would need to type very fas=
t). It would be ok for an external
process to be providing new information, but not ok to require the server t=
o ask that external process for
information (or wait on it if information became stale, etc.)

So I've been ruminating about this since my rather terse response yesterday=
.   I think it's inappropriate for me as an individual or as a working grou=
p chair to be the only one weighing in on this.   I have some pretty strong=
 opinions about what standards should require of DHCP servers, and I don't =
really think my opinions are inherently right=97they're just opinions.

My essential concern about this document is that it seems to be placing exp=
ectations on a DHCP server that I think a typical DHCP server vendor would =
not be comfortable with.   At the same time, it's also clear to me that the=
re are DHCP servers out there that could certainly serve this data, even if=
 they did an in-band query from another server to fetch it.   I know Nominu=
m's DHCP server can do this, and I am pretty sure CNR can do it as well.

So what I'm saying is that I don't really think it's wrong for a DHCP serve=
r to do this.   My concern is that it might not be practical for an IETF do=
cument to effectively _require_ that a DHCP server do this.

That's a fairly weak objection.   If this document were to go through and b=
ecome a standard, and people didn't want to implement it, they just wouldn'=
t implement it.

So perhaps it would help if the document were simply clearer about what it =
was asking of the DHCP server.   Right now it's a bit vague=97all the out-o=
f-band or in-band querying is implied rather than explicitly stated.   This=
 is part of what I was getting at by asking about real expected use cases.

Robert, can you or James speak to that?   I don't want you to feel like I'm=
 trying to checkmate you by getting you to admit to a use case that's forbi=
dden=97I don't think it's true that the use case I'm reluctant to encourage=
 is in fact forbidden.   I just feel like right now the way this is expecte=
d to be used is unstated and vague, and it would be better if it were not. =
  That is, it would be better for you to really make a case for how you act=
ually intend to use this option than for us to gloss over it.


--_000_DD9D3CC6715B4C1483031E4810E5343Enominumcom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <57A7A31251D6814CA376372377FC8D2E@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 7, 2011, at 4:31 PM, Robert Sparks wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">If
 I have it right, the essence of (this part of) your concern is that a dhcp=
 server can't be constrained<br>
to go ask an external process for the information it needs to respond to a =
request. That is, it needs<br>
to be able to respond to the request with the data it has at the time the r=
equest arrives. The operational<br>
model is that the data you have to respond with is the kind of stuff the se=
rver admin would enter as<br>
configuration (and it's possible that the admin would need to type very fas=
t). It would be ok for an external<br>
process to be providing new information, but not ok to require the server t=
o ask that external process for<br>
information (or wait on it if information became stale, etc.)</span></block=
quote>
</div>
<br>
<div>So I've been ruminating about this since my rather terse response yest=
erday. &nbsp; I think it's inappropriate for me as an individual or as a wo=
rking group chair to be the only one weighing in on this. &nbsp; I have som=
e pretty strong opinions about what standards
 should require of DHCP servers, and I don't really think my opinions are i=
nherently right=97they're just opinions.</div>
<div><br>
</div>
<div>My essential concern about this document is that it seems to be placin=
g expectations on a DHCP server that I think a typical DHCP server vendor w=
ould not be comfortable with. &nbsp; At the same time, it's also clear to m=
e that there are DHCP servers out there
 that could certainly serve this data, even if they did an in-band query fr=
om another server to fetch it. &nbsp; I know Nominum's DHCP server can do t=
his, and I am pretty sure CNR can do it as well.</div>
<div><br>
</div>
<div>So what I'm saying is that I don't really think it's wrong for a DHCP =
server to do this. &nbsp; My concern is that it might not be practical for =
an IETF document to effectively _require_ that a DHCP server do this.</div>
<div><br>
</div>
<div>That's a fairly weak objection. &nbsp; If this document were to go thr=
ough and become a standard, and people didn't want to implement it, they ju=
st wouldn't implement it.</div>
<div><br>
</div>
<div>So perhaps it would help if the document were simply clearer about wha=
t it was asking of the DHCP server. &nbsp; Right now it's a bit vague=97all=
 the out-of-band or in-band querying is implied rather than explicitly stat=
ed. &nbsp; This is part of what I was getting
 at by asking about real expected use cases.</div>
<div><br>
</div>
<div>Robert, can you or James speak to that? &nbsp; I don't want you to fee=
l like I'm trying to checkmate you by getting you to admit to a use case th=
at's forbidden=97I don't think it's true that the use case I'm reluctant to=
 encourage is in fact forbidden. &nbsp; I just
 feel like right now the way this is expected to be used is unstated and va=
gue, and it would be better if it were not. &nbsp; That is, it would be bet=
ter for you to really make a case for how you actually intend to use this o=
ption than for us to gloss over it.</div>
<div><br>
</div>
</body>
</html>

--_000_DD9D3CC6715B4C1483031E4810E5343Enominumcom_--

From rjsparks@nostrum.com  Thu Dec  8 11:58:30 2011
Return-Path: <rjsparks@nostrum.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 7BA3E21F8438 for <dhcwg@ietfa.amsl.com>; Thu,  8 Dec 2011 11:58:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FtkKFUYtlsuZ for <dhcwg@ietfa.amsl.com>; Thu,  8 Dec 2011 11:58:29 -0800 (PST)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id BADA121F8478 for <dhcwg@ietf.org>; Thu,  8 Dec 2011 11:58:28 -0800 (PST)
Received: from unexplicable.local (pool-173-57-95-103.dllstx.fios.verizon.net [173.57.95.103]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id pB8JwIJI003398 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 8 Dec 2011 13:58:25 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <4EE116DA.7000901@nostrum.com>
Date: Thu, 08 Dec 2011 13:58:18 -0600
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <6B961032-728D-43D6-81E3-9862EF9ADA09@gmail.com> <2207D364-CADB-43D2-907B-204180A6E4CC@nominum.com> <201110032203.p93M3f5I031107@mtv-core-3.cisco.com> <5EA79C2C-F4A2-4D88-85DC-E2F4B931E11A@nominum.com> <201110041732.p94HW6s3000630@mtv-core-1.cisco.com> <67AEBF45-5C47-43B4-B86C-482ED32E41D3@nominum.com> <201110042006.p94K6NX8001171@mtv-core-3.cisco.com> <578BA924-AE98-4B72-8857-949C9B76D6F6@nominum.com> <478F3A8B-6ADE-4BC2-BCBE-7214AD983727@gmail.com> <201110042057.p94KvlAJ004802@mtv-core-3.cisco.com> <C042ECF1-C246-4090-A4C6-6B20302227FA@gmail.com> <201112061938.pB6Jc3pD028634@mtv-core-3.cisco.com> <34043C82-5190-475B-8765-70B9C16FF4D7@nominum.com> <201112070104.pB71408l026419@mtv-core-2.cisco.com> <F0766A12-F4F6-4684-BFA5-B9DF9875186D@nominum.com> <4EDFDB1C.3040102@nostrum.com> <DD9D3CC6-715B-4C14-8303-1E4810E5343E@nominum.com>
In-Reply-To: <DD9D3CC6-715B-4C14-8303-1E4810E5343E@nominum.com>
Content-Type: multipart/alternative; boundary="------------080705090007080300070602"
Received-SPF: pass (nostrum.com: 173.57.95.103 is authenticated by a trusted mechanism)
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>, "James M. Polk" <jmpolk@cisco.com>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] review of draft-ietf-geopriv-dhcp-lbyr-uri-option
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, 08 Dec 2011 19:58:30 -0000

This is a multi-part message in MIME format.
--------------080705090007080300070602
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

On 12/8/11 11:27 AM, Ted Lemon wrote:
> On Dec 7, 2011, at 4:31 PM, Robert Sparks wrote:
>> If I have it right, the essence of (this part of) your concern is 
>> that a dhcp server can't be constrained
>> to go ask an external process for the information it needs to respond 
>> to a request. That is, it needs
>> to be able to respond to the request with the data it has at the time 
>> the request arrives. The operational
>> model is that the data you have to respond with is the kind of stuff 
>> the server admin would enter as
>> configuration (and it's possible that the admin would need to type 
>> very fast). It would be ok for an external
>> process to be providing new information, but not ok to require the 
>> server to ask that external process for
>> information (or wait on it if information became stale, etc.)
>
> So I've been ruminating about this since my rather terse response 
> yesterday.   I think it's inappropriate for me as an individual or as 
> a working group chair to be the only one weighing in on this.   I have 
> some pretty strong opinions about what standards should require of 
> DHCP servers, and I don't really think my opinions are inherently 
> right—they're just opinions.
>
> My essential concern about this document is that it seems to be 
> placing expectations on a DHCP server that I think a typical DHCP 
> server vendor would not be comfortable with.   At the same time, it's 
> also clear to me that there are DHCP servers out there that could 
> certainly serve this data, even if they did an in-band query from 
> another server to fetch it.   I know Nominum's DHCP server can do 
> this, and I am pretty sure CNR can do it as well.
>
> So what I'm saying is that I don't really think it's wrong for a DHCP 
> server to do this.   My concern is that it might not be practical for 
> an IETF document to effectively _require_ that a DHCP server do this.
>
> That's a fairly weak objection.   If this document were to go through 
> and become a standard, and people didn't want to implement it, they 
> just wouldn't implement it.
>
> So perhaps it would help if the document were simply clearer about 
> what it was asking of the DHCP server.   Right now it's a bit 
> vague—all the out-of-band or in-band querying is implied rather than 
> explicitly stated.   This is part of what I was getting at by asking 
> about real expected use cases.
Thanks Ted - I agree that we need to make the document clearer. This 
document should not be causing the refresh mechanics at a dhcp server or 
client to change, and it shouldn't be asking the server to do something
fundamentally different from the kinds of things it already does in 
order to satisfy the request. I don't think we really have anybody 
asking for that, but we need to make the document clear so we're sure. 
This is where I was
trying to focus the first part of the conversation (please do let me 
know if what I had in that message was right
or not).

I'm going to take a stab at answering what I think you're asking for 
real expected use cases. But be aware
of this context:

Email list conversations around how location references are created, 
moved around, and consumed have been
notoriously difficult. It's easy to make assumptions, both as the reader 
and writer, when trying to make short
points that lead folks to start talking passionately past each other. I 
think that might have happened early
in the discussion of this document on this list. The way we've dealt 
with it is to capture things in the drafts
(many now RFCs) in more detail. When things start to seem odd, please 
refer back to those to see if they
clear up the oddness. A good touchstone starting place is RFC5808 
section 3 (including its subsections).
Because of the context, this is going to be verbose, and nit-sensitive - 
please read it as an attempt to
balance being specific with being concise.

The use case this draft is addressing is allowing a host to be 
configured (via dhcp) with a reference to
a location object that it can hand off (convey) to other elements. If 
those elements are able to use the
reference successfully, they get the location object and can use it as 
part of whatever function they
are running (these elements are called location recipients).

The mechanism is intended to be general - there is no one specific 
expected use case, but some of the
major instances used while developing the architecture include giving an 
application on your (fixed)
desktop the ability to tell the local pizza delivery service where it 
is, and your mobile phone the ability
to tell an emergency response center where it is.

The reference itself will not typically change rapidly - that's a major 
advantage of using a reference instead
of providing location-by-value. If you had a deployment where you didn't 
need to worry about who you've
given the reference to in the past, it could be configured once and have 
a very long life. In a more general
deployment, the reference itself will need to occasionally change - but 
note that it does so based on the
application use requirements, not inherently because the bits (location) 
that the reference points to might
have changed. For instance, you might be willing to let some delivery 
service know were you are right now,
but you don't want them to be able to use the reference you give them 
next week. This is where the location
URI expiration notion becomes important - it lets the host know how long 
the location server will honor
the reference. It lets the applications on the host make an informed 
decision about who they expose the
reference to (I might be willing to give a reference to one of my 
friends that's good for several days, but
I might choose not to hand one of those to the cab company in the city 
I'm visiting).

There are some applications where you don't want to give the same 
reference to two different location recipients.
Those applications would be better served using a different location 
configuration protocol than the one we're
talking about here, such as HELD (RFC5985).

Let me stop there and ask if I'm on a path to address your question or 
if you were looking for something
completely different.

Given what's above, I'd like to reiterate the point the we should 
clarify the draft to make it clear we're not
trying to change what a dhcp client or server does. How we fix how it's 
trying to convey URI expiration needs
to get that part right. I don't think we should remove it from the 
information that is configured, and I don't
think we should tie it to the lease time (either by making it being 
exactly the lease time, or by artificially
stimulating refreshes based on it. Rather, this is a management 
coordination task/policy decision for the
administrative domain. A reasonable Location Information Service that is 
having its URIs configured into
hosts using dhcp should be configured to have the exipiry of those URIs 
be at least as long as the expected
lease time.


> Robert, can you or James speak to that?   I don't want you to feel 
> like I'm trying to checkmate you by getting you to admit to a use case 
> that's forbidden—I don't think it's true that the use case I'm 
> reluctant to encourage is in fact forbidden.   I just feel like right 
> now the way this is expected to be used is unstated and vague, and it 
> would be better if it were not.   That is, it would be better for you 
> to really make a case for how you actually intend to use this option 
> than for us to gloss over it.
>


--------------080705090007080300070602
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    On 12/8/11 11:27 AM, Ted Lemon wrote:
    <blockquote
      cite="mid:DD9D3CC6-715B-4C14-8303-1E4810E5343E@nominum.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div>
        <div>On Dec 7, 2011, at 4:31 PM, Robert Sparks wrote:</div>
        <blockquote type="cite"><span class="Apple-style-span"
            style="border-collapse: separate; font-family: Helvetica;
            font-style: normal; font-variant: normal; font-weight:
            normal; letter-spacing: normal; line-height: normal;
            orphans: 2; text-align: -webkit-auto; text-indent: 0px;
            text-transform: none; white-space: normal; widows: 2;
            word-spacing: 0px; -webkit-border-horizontal-spacing: 0px;
            -webkit-border-vertical-spacing: 0px;
            -webkit-text-decorations-in-effect: none;
            -webkit-text-size-adjust: auto; -webkit-text-stroke-width:
            0px; font-size: medium; ">If I have it right, the essence of
            (this part of) your concern is that a dhcp server can't be
            constrained<br>
            to go ask an external process for the information it needs
            to respond to a request. That is, it needs<br>
            to be able to respond to the request with the data it has at
            the time the request arrives. The operational<br>
            model is that the data you have to respond with is the kind
            of stuff the server admin would enter as<br>
            configuration (and it's possible that the admin would need
            to type very fast). It would be ok for an external<br>
            process to be providing new information, but not ok to
            require the server to ask that external process for<br>
            information (or wait on it if information became stale,
            etc.)</span></blockquote>
      </div>
      <br>
      <div>So I've been ruminating about this since my rather terse
        response yesterday.   I think it's inappropriate for me as an
        individual or as a working group chair to be the only one
        weighing in on this.   I have some pretty strong opinions about
        what standards should require of DHCP servers, and I don't
        really think my opinions are inherently right—they're just
        opinions.</div>
      <div><br>
      </div>
      <div>My essential concern about this document is that it seems to
        be placing expectations on a DHCP server that I think a typical
        DHCP server vendor would not be comfortable with.   At the same
        time, it's also clear to me that there are DHCP servers out
        there that could certainly serve this data, even if they did an
        in-band query from another server to fetch it.   I know
        Nominum's DHCP server can do this, and I am pretty sure CNR can
        do it as well.</div>
      <div><br>
      </div>
      <div>So what I'm saying is that I don't really think it's wrong
        for a DHCP server to do this.   My concern is that it might not
        be practical for an IETF document to effectively _require_ that
        a DHCP server do this.</div>
      <div><br>
      </div>
      <div>That's a fairly weak objection.   If this document were to go
        through and become a standard, and people didn't want to
        implement it, they just wouldn't implement it.</div>
      <div><br>
      </div>
      <div>So perhaps it would help if the document were simply clearer
        about what it was asking of the DHCP server.   Right now it's a
        bit vague—all the out-of-band or in-band querying is implied
        rather than explicitly stated.   This is part of what I was
        getting at by asking about real expected use cases.</div>
    </blockquote>
    Thanks Ted - I agree that we need to make the document clearer. This
    document should not be causing the refresh mechanics at a dhcp
    server or client to change, and it shouldn't be asking the server to
    do something<br>
    fundamentally different from the kinds of things it already does in
    order to satisfy the request. I don't think we really have anybody
    asking for that, but we need to make the document clear so we're
    sure. This is where I was<br>
    trying to focus the first part of the conversation (please do let me
    know if what I had in that message was right<br>
    or not).<br>
    <br>
    I'm going to take a stab at answering what I think you're asking for
    real expected use cases. But be aware<br>
    of this context:<br>
    <br>
    Email list conversations around how location references are created,
    moved around, and consumed have been<br>
    notoriously difficult. It's easy to make assumptions, both as the
    reader and writer, when trying to make short<br>
    points that lead folks to start talking passionately past each
    other. I think that might have happened early<br>
    in the discussion of this document on this list. The way we've dealt
    with it is to capture things in the drafts<br>
    (many now RFCs) in more detail. When things start to seem odd,
    please refer back to those to see if they<br>
    clear up the oddness. A good touchstone starting place is RFC5808
    section 3 (including its subsections).<br>
    Because of the context, this is going to be verbose, and
    nit-sensitive - please read it as an attempt to <br>
    balance being specific with being concise.<br>
    <br>
    The use case this draft is addressing is allowing a host to be
    configured (via dhcp) with a reference to<br>
    a location object that it can hand off (convey) to other elements.
    If those elements are able to use the<br>
    reference successfully, they get the location object and can use it
    as part of whatever function they<br>
    are running (these elements are called location recipients).<br>
    <br>
    The mechanism is intended to be general - there is no one specific
    expected use case, but some of the<br>
    major instances used while developing the architecture include
    giving an application on your (fixed)<br>
    desktop the ability to tell the local pizza delivery service where
    it is, and your mobile phone the ability<br>
    to tell an emergency response center where it is.<br>
    <br>
    The reference itself will not typically change rapidly - that's a
    major advantage of using a reference instead<br>
    of providing location-by-value. If you had a deployment where you
    didn't need to worry about who you've<br>
    given the reference to in the past, it could be configured once and
    have a very long life. In a more general<br>
    deployment, the reference itself will need to occasionally change -
    but note that it does so based on the<br>
    application use requirements, not inherently because the bits
    (location) that the reference points to might<br>
    have changed. For instance, you might be willing to let some
    delivery service know were you are right now,<br>
    but you don't want them to be able to use the reference you give
    them next week. This is where the location<br>
    URI expiration notion becomes important - it lets the host know how
    long the location server will honor<br>
    the reference. It lets the applications on the host make an informed
    decision about who they expose the<br>
    reference to (I might be willing to give a reference to one of my
    friends that's good for several days, but<br>
    I might choose not to hand one of those to the cab company in the
    city I'm visiting). <br>
    <br>
    There are some applications where you don't want to give the same
    reference to two different location recipients.<br>
    Those applications would be better served using a different location
    configuration protocol than the one we're<br>
    talking about here, such as HELD (RFC5985).<br>
    <br>
    Let me stop there and ask if I'm on a path to address your question
    or if you were looking for something<br>
    completely different.<br>
    <br>
    Given what's above, I'd like to reiterate the point the we should
    clarify the draft to make it clear we're not<br>
    trying to change what a dhcp client or server does. How we fix how
    it's trying to convey URI expiration needs<br>
    to get that part right. I don't think we should remove it from the
    information that is configured, and I don't<br>
    think we should tie it to the lease time (either by making it being
    exactly the lease time, or by artificially<br>
    stimulating refreshes based on it. Rather, this is a management
    coordination task/policy decision for the<br>
    administrative domain. A reasonable Location Information Service
    that is having its URIs configured into<br>
    hosts using dhcp should be configured to have the exipiry of those
    URIs be at least as long as the expected<br>
    lease time.<br>
    <br>
    <br>
    <blockquote
      cite="mid:DD9D3CC6-715B-4C14-8303-1E4810E5343E@nominum.com"
      type="cite">
      <div>Robert, can you or James speak to that?   I don't want you to
        feel like I'm trying to checkmate you by getting you to admit to
        a use case that's forbidden—I don't think it's true that the use
        case I'm reluctant to encourage is in fact forbidden.   I just
        feel like right now the way this is expected to be used is
        unstated and vague, and it would be better if it were not.  
        That is, it would be better for you to really make a case for
        how you actually intend to use this option than for us to gloss
        over it.</div>
      <div><br>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------080705090007080300070602--

From shemant@cisco.com  Thu Dec  8 14:00:25 2011
Return-Path: <shemant@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 3A84621F86A6 for <dhcwg@ietfa.amsl.com>; Thu,  8 Dec 2011 14:00:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.521
X-Spam-Level: 
X-Spam-Status: No, score=-6.521 tagged_above=-999 required=5 tests=[AWL=0.078,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fQBCy2Q-0BEX for <dhcwg@ietfa.amsl.com>; Thu,  8 Dec 2011 14:00:24 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id B068B21F84ED for <dhcwg@ietf.org>; Thu,  8 Dec 2011 14:00:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=873; q=dns/txt; s=iport; t=1323381624; x=1324591224; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=vrrXrtas6Qr8azaaAio+DZQ1t+1FjlYQoQRHiRe38Wo=; b=NFfBh2SWW/WzZXPqLDU+Z8HFs6Q8hu/k8rYgDUG2nnSqs1361VBOAD8u 5zqTM+eaSdP6R4YcV+b0lnlat5p09S6Tcm0Gc8PAlzrvxz+GWb1EPFPhw JCb9Rbx9/oDSJwtbr73kq2uQh25pJC8huHOoa4/sZRw6GHBxlR+hHm1CO g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhABABEppk6tJV2Z/2dsb2JhbACQRY4WeJRVkjSGGQSGUI15ighU
X-IronPort-AV: E=Sophos;i="4.71,321,1320624000"; d="scan'208";a="39866918"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-9.cisco.com with ESMTP; 08 Dec 2011 22:00:24 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pB8M0OGs011573;  Thu, 8 Dec 2011 22:00:24 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 8 Dec 2011 16:00:24 -0600
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 8 Dec 2011 16:00:21 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C303829003@XMB-RCD-109.cisco.com>
In-Reply-To: <4EDFD071.7090107@necom830.hpcl.titech.ac.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] To wait for RA or not to wait?
Thread-Index: Acy1IUHyZeVjg/0/Tu+oVuucgpk4PgA0niBA
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com><867F4B6A1672E541A94676D556793ACD0CB42FDABE@MOPESMBX01.eu.thmulti.com><BEA0EE13-9223-4D60-837C-AEAF74FAFD6E@nominum.com><867F4B6A1672E541A94676D556793ACD0CB42FDB00@MOPESMBX01.eu.thmulti.com><5B6B2B64C9FE2A489045EEEADDAFF2C30377869C@XMB-RCD-109.cisco.com><4EDE8D38.9010807@necom830.hpcl.titech.ac.jp><5B6B2B64C9FE2A489045EEEADDAFF2C303778E63@XMB-RCD-109.cisco.com> <4EDEDB21.4090902@necom830.hpcl.titech.ac.jp> <5B6B2B64C9FE2A489045EEEADDAFF2C3037790E1@XMB-RCD-109.cisco.com> <4EDFD071.7090107@necom830.hpcl.titech.ac.jp>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Masataka Ohta" <mohta@necom830.hpcl.titech.ac.jp>
X-OriginalArrivalTime: 08 Dec 2011 22:00:24.0099 (UTC) FILETIME=[C94FA730:01CCB5F4]
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] To wait for RA or not to wait?
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, 08 Dec 2011 22:00:25 -0000

-----Original Message-----
From: Masataka Ohta [mailto:mohta@necom830.hpcl.titech.ac.jp]=20
Sent: Wednesday, December 07, 2011 3:46 PM
To: Hemant Singh (shemant)
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] To wait for RA or not to wait?

>It's like asking "what standard is used between a cable modem
>monitoring PC and its console".
>Let operators decide.

No standards exist yet and that's a huge problem.

>Operators may or may not, though most will use existing ones
>such as syslog.

Several cable modems in the U.S. that I have used do not support syslog.
One has to assume there won't be any indication for an error like this
from consumer devices and design protocols robust enough to not have to
cause such conflicting errors between two sources of information
providing the same data.=20

I have no further comment on this topic.

Hemant

From rdroms.ietf@gmail.com  Thu Dec  8 14:06:41 2011
Return-Path: <rdroms.ietf@gmail.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 90C1E21F8B12 for <dhcwg@ietfa.amsl.com>; Thu,  8 Dec 2011 14:06:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hGjDenndsZPp for <dhcwg@ietfa.amsl.com>; Thu,  8 Dec 2011 14:06:41 -0800 (PST)
Received: from mail-qw0-f51.google.com (mail-qw0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id E7DC621F8ADE for <dhcwg@ietf.org>; Thu,  8 Dec 2011 14:06:40 -0800 (PST)
Received: by qadz3 with SMTP id z3so1634801qad.10 for <dhcwg@ietf.org>; Thu, 08 Dec 2011 14:06:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=BUt8JnxZ73AwZuBVLZ3iQjjOQasZKpeiHuf+oQQlq8w=; b=kKUDdamCniSqhGD9nhphX61cHE8cIYdgJjTtR7CZcieP27cbmPEl7Ti9SAtVWsoKKa mdltW6Smh9/sIXYRE1b4onCRVH2JaL+v9DfNLjyuxiHRIUI4213xk+qqQs3Rd22G5nBt 6n/ncD8NtLh/DuzoeR8GmFeJEghwRhj2VT3Gw=
Received: by 10.224.212.10 with SMTP id gq10mr4703697qab.75.1323382000430; Thu, 08 Dec 2011 14:06:40 -0800 (PST)
Received: from [10.86.254.144] (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPS id i10sm12302908qac.17.2011.12.08.14.06.38 (version=SSLv3 cipher=OTHER); Thu, 08 Dec 2011 14:06:39 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <521D1731-F4AD-471E-AF34-FAA22B7395EC@nominum.com>
Date: Thu, 8 Dec 2011 17:06:37 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4079EE5F-3682-42BD-9FC2-2D8FFE2F6B46@gmail.com>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com> <4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com> <4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com> <D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com> <95FDEE46-2731-4419-921B-1DA3A4F3FD92@gmail.com> <601EE481-E4B8-48DC-9885-0FB3302DC8CB@nominum.com> <4E70EB90-F9B2-46FB-8E4A-FB63429E94B9@gmail.com> <521D1731-F4AD-471E-AF34-FAA22B7395EC@nominum.com>
To: dhc WG <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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, 08 Dec 2011 22:06:41 -0000

The context for this discussion is an I-D intended for publication as =
Informational and updating RFC 6204: "Basic Requirements for IPv6 =
Customer Edge Routers," draft-ietf-v6ops-6204bis.  The specific problem =
is defining the behavior of a IPv6 CE router that sends both an IA_PD =
and an IA_NA in a Request message, and receives a delegated prefix in =
the IA_PD but no assigned address in the IA_NA.

BTW, "this scenario can't happen" is not an answer; details available on =
request.

The four errata cited earlier in this thread partially solve the problem =
by scoping the NoAddrsAvail status code so the client can determine =
which prefix and address requests were not fulfilled.  However, the =
client's behavior after receiving NoAddrsAvail for some but not all IA_* =
needs to be defined.

The following requirements from draft-ietf-v6ops-6204bis are related to =
this issue:

   W-5:  DHCPv6 address assignment (IA_NA) and DHCPv6 prefix delegation
         (IA_PD) SHOULD be done as a single DHCPv6 session.

   WPD-5:  If the IPv6 CE router is configured to initiate DHCPv6 before
           receiving a Router Advertisement, it MUST also request an
           IA_NA option in DHCPv6.
=20
   WPD-7:  If the IPv6 CE router requests both an IA_NA and an IA_PD
           option in DHCPv6, it MUST accept an IA_PD option in DHCPv6
           Advertise/Reply messages, even if the message does not
           contain any addresses, unless configured to only obtain its
           WAN IPv6 address via DHCPv6.

The dhc WG needs to generate a single erratum or set of errata that form =
a complete solution to the problem, so we can accept it/them against RFC =
3315 and RFC 3633.  draft-ietf-v6ops-6204bis can then cite the =
erratum/errata.

- Ralph

On Dec 6, 2011, at 4:11 PM 12/6/11, Ted Lemon wrote:

> On Dec 6, 2011, at 4:07 PM, Ralph Droms wrote:
>> What is the inconsistency you see?
>=20
> We're told to treat status codes as nested, but not what to do when we =
get an offer that contains an IA_PD and not an IA_NA, and not what to do =
when we receive a status code that's not nested, and not what to do as a =
server if we have to send status codes for both IA_PD and IA_NA.   Maybe =
"incomplete" is a better choice of words, but the point is that if we =
just make these four changes, we are going to create more permutations =
in acceptable set of behaviors that servers and clients may follow.   =
This is really bad for interoperability, and we can't easily take it =
back once it's done.
>=20


From mohta@necom830.hpcl.titech.ac.jp  Fri Dec  9 00:11:10 2011
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 9D1E021F841B for <dhcwg@ietfa.amsl.com>; Fri,  9 Dec 2011 00:11:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.015
X-Spam-Level: 
X-Spam-Status: No, score=0.015 tagged_above=-999 required=5 tests=[AWL=0.105,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qEfXXv2fH6Bp for <dhcwg@ietfa.amsl.com>; Fri,  9 Dec 2011 00:11:10 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id C3C1111E8093 for <dhcwg@ietf.org>; Fri,  9 Dec 2011 00:11:08 -0800 (PST)
Received: (qmail 90589 invoked from network); 9 Dec 2011 08:45:17 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 9 Dec 2011 08:45:17 -0000
Message-ID: <4EE1C286.1010100@necom830.hpcl.titech.ac.jp>
Date: Fri, 09 Dec 2011 17:10:46 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <A44BD847-A71B-49DB-80A2-B4B39F52ED58@nominum.com><867F4B6A1672E541A94676D556793ACD0CB42FDABE@MOPESMBX01.eu.thmulti.com><BEA0EE13-9223-4D60-837C-AEAF74FAFD6E@nominum.com><867F4B6A1672E541A94676D556793ACD0CB42FDB00@MOPESMBX01.eu.thmulti.com><5B6B2B64C9FE2A489045EEEADDAFF2C30377869C@XMB-RCD-109.cisco.com><4EDE8D38.9010807@necom830.hpcl.titech.ac.jp><5B6B2B64C9FE2A489045EEEADDAFF2C303778E63@XMB-RCD-109.cisco.com> <4EDEDB21.4090902@necom830.hpcl.titech.ac.jp> <5B6B2B64C9FE2A489045EEEADDAFF2C3037790E1@XMB-RCD-109.cisco.com> <4EDFD071.7090107@necom830.hpcl.titech.ac.jp> <5B6B2B64C9FE2A489045EEEADDAFF2C303829003@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C303829003@XMB-RCD-109.cisco.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] To wait for RA or not to wait?
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: Fri, 09 Dec 2011 08:11:10 -0000

Hemant Singh (shemant) wrote:

>> It's like asking "what standard is used between a cable modem
>> monitoring PC and its console".
>> Let operators decide.
> 
> No standards exist yet and that's a huge problem.

What? Can't you connect your PC and its console?

>> Operators may or may not, though most will use existing ones
>> such as syslog.
> 
> Several cable modems in the U.S. that I have used do not support syslog.

It means there is no point for IETF to develop a new protocol
to make cable modems report errors, because they will not be
used by several cable modem makers.

So?

> One has to assume there won't be any indication for an error like this
> from consumer devices and design protocols robust enough to not have to
> cause such conflicting errors between two sources of information
> providing the same data.

I wrote:

	Implementations should report an error.

not,

	Implementations MUST report an error.

Neither protocols nor implementations can be fool proof against
all the operational errors.

> I have no further comment on this topic.

Wise enough.

						Masataka Ohta

From Ted.Lemon@nominum.com  Fri Dec  9 09:58:36 2011
Return-Path: <Ted.Lemon@nominum.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 7FB7A21F8469 for <dhcwg@ietfa.amsl.com>; Fri,  9 Dec 2011 09:58:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.54
X-Spam-Level: 
X-Spam-Status: No, score=-106.54 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AD8UQZKktGEL for <dhcwg@ietfa.amsl.com>; Fri,  9 Dec 2011 09:58:36 -0800 (PST)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id C8F8021F8478 for <dhcwg@ietf.org>; Fri,  9 Dec 2011 09:58:35 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKTuJMPzhWd8rtXgnaRKSTLhtsr1s1wS+O@postini.com; Fri, 09 Dec 2011 09:58:35 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id B6D671B82CC for <dhcwg@ietf.org>; Fri,  9 Dec 2011 09:58:22 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 9FEE1190052 for <dhcwg@ietf.org>; Fri,  9 Dec 2011 09:58:21 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0339.001; Fri, 9 Dec 2011 09:58:21 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Thread-Topic: WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-00
Thread-Index: AQHMtpwjAljFLrkpaEuFQR2ym6HpQw==
Date: Fri, 9 Dec 2011 17:58:21 +0000
Message-ID: <EBA5E737-027B-40F2-AE1D-A48A2051F441@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <CC388D40B345044FA1B2E895786778AF@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-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: Fri, 09 Dec 2011 17:58:36 -0000

Ralph's put in an individual submission draft with Jari as the sponsoring A=
D.   The draft attempts to solve a problem ISPs are having where in a massi=
ve IPv6 network that isn't entirely deployed, devices are requesting config=
uration too often.

Ralph's draft proposes a new option whereby a DHCP server can indicate in r=
esponse to a solicit that the client should use a larger value for SOL_MAX_=
RT.   This means that clients will continue their exponential backoff to wh=
atever limit is stated in the offer, and reduces the overall traffic on the=
 DHCP servers at the core of the network.

The draft is an individual submission, so it doesn't technically have to pa=
ss dhcwg last call=97just IETF last call.   However, since the dhcwg is whe=
re DHCP protocol extensions are done, I'm doing a last call here to encoura=
ge people to review it=97it would really help if some wg participants would=
 review it and think about the implications.

If we don't hear anything by December 23, Jari will continue the process of=
 advancing the draft.   If you do read the draft, please comment here as to=
 whether you support it, and please offer any suggestions you may have.

Thanks!


From volz@cisco.com  Sat Dec 10 19:04:31 2011
Return-Path: <volz@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 3F8B521F8AFB for <dhcwg@ietfa.amsl.com>; Sat, 10 Dec 2011 19:04:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OLKrnm99rtiD for <dhcwg@ietfa.amsl.com>; Sat, 10 Dec 2011 19:04:28 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 1FCAB21F8AF5 for <dhcwg@ietf.org>; Sat, 10 Dec 2011 19:04:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=volz@cisco.com; l=18541; q=dns/txt; s=iport; t=1323572668; x=1324782268; h=mime-version:subject:date:message-id:in-reply-to: references:from:to:cc; bh=aI9sQc7xcxVGpzA/XrurhnMACY2bJasG6GvFYL6qfEE=; b=FETSNdc12Q4ZC6CimliTUQbzb8ebZ2Vq+jE4V5CGDe0EoLBwi85+OkZy Xq14xMaprlvjt+myupiOKxSw0iQkxbE8KaJqpH6Xk8uDi7vMext2D8ThV PkSx/dLOGejSzkmUdlPUWLxN61bPiCrSDmZ7l3Fkx3JgoZGK8G15bDxNW w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqkAANEc5E6tJV2a/2dsb2JhbABDgk2XdJA+gQWBcgEBAQEDEgEJEQNEBRACAQgRBAEBCwYXAQYBRQkIAgQBEggWBJ5bAZ1OiwpjBIgxnwY
X-IronPort-AV: E=Sophos;i="4.71,333,1320624000"; d="scan'208,217";a="42888069"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-5.cisco.com with ESMTP; 11 Dec 2011 03:04:27 +0000
Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pBB34Qm9027259;  Sun, 11 Dec 2011 03:04:26 GMT
Received: from xmb-rcd-101.cisco.com ([72.163.62.143]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 10 Dec 2011 21:04:26 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCB7B1.97854956"
Date: Sat, 10 Dec 2011 21:04:25 -0600
Message-ID: <D9B5773329187548A0189ED6503667890A199E5A@XMB-RCD-101.cisco.com>
In-Reply-To: <D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: AcyxakejwUXOElp7STCtYjgcemUphwDG63mAAAGEB4AAADFTAAAANTKAAAB3qAAAx95lQA==
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com><4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com><4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com> <D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Ted Lemon" <Ted.Lemon@nominum.com>, "Hemant Singh (shemant)" <shemant@cisco.com>
X-OriginalArrivalTime: 11 Dec 2011 03:04:26.0887 (UTC) FILETIME=[97AFB170:01CCB7B1]
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Sun, 11 Dec 2011 03:04:31 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CCB7B1.97854956
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I think that later including the IA_NA in a renew for the IA_PD in the
RENEW is problematic ...

=20

Read RFC 3315, 18.2.3:

=20

   When the server receives a Renew message that contains an IA option

   from a client, it locates the client's binding and verifies that the

   information in the IA from the client matches the information stored

   for that client.

=20

   If the server cannot find a client entry for the IA the server

   returns the IA containing no addresses with a Status Code option set

   to NoBinding in the Reply message.

=20

This would require servers to remember bindings for items that they have
no leases for, which seems rather odd? When should a server 'forget' a
binding?=20

=20

I think the cleanest is to use separate requests.

=20

What if you had two DHCPv6 servers - one that offered addresses and one
that offered prefixes ... Would the client accept both advertises?

=20

If you have separate transactions, a lot of these issues go away.

=20

I regret having suggested to Hemant a while ago when RFC 6204 was in
Internet-Draft stage to have the CPE make one request, not two. I think
treating the requests completely separate, while perhaps a bit less
efficient, is just so much cleaner from an implementation and testing
standpoint.

=20

=20

While RFC 3315 and RFC 3633 handle no address/prefix differently, I
really don't see that as such a big deal. A client can easily understand
that NoAddrsAvail applies only to addresses, not prefixes. Personally, I
would leave this alone. I really see no win to changing this because
clients will have to support BOTH the old and new standard as they
cannot assure what servers they will be communicating with - SO WHAT
BENEFIT IS THERE????? It just adds to complexity and testing. I do NOT
think this change in the errata is CORRECT. I "vote" against it.

=20

Cisco Network Registrar DHCP server has been sending back these results
per the RFCs and it works just fine. Note that if we do send back an
IA_PD with prefix information, we "violate" RFC 3315 text that says the
NoAddrsAvail shouldn't include "other configuration" options ... so we
will send "other configuration" options back to the client *if* we send
back either IAPREFIX or IAADDR options (in the appropriate bindings).

=20

We also discussed this issue at the DHCPv6 bakeoffs long ago.

=20

-          Bernie

=20

From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Ted Lemon
Sent: Tuesday, December 06, 2011 2:23 PM
To: Hemant Singh (shemant)
Cc: dhc WG; Ralph Droms
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...

=20

On Dec 6, 2011, at 2:09 PM, Hemant Singh (shemant) wrote:

	OK, got it.  I was confused from DHCPv4.  So when the
server-unicast
	option is set, then the relay does have to sniff unicast DHCPv6
messages
	which is not a new problem for choice 3.  Thus I am for choice
3.

=20

I think we should be aware that choice 3 does have the side effect that
if a DHCP that would offer an IA_NA is offline, and then comes back
online, a client that follows choice 3 as I understand it will never get
an IA_NA.   I realize that choice 3 (accept an offer that contains an
IA_PD and no IA_NA, keep asking for IA_NA in subsequent renews, and do
not fork another requestor for IA_NA) is attractive for the case where
there is no DHCP server on the wire that *could* offer an IA_NA,
however, since it will stop the client soliciting for an IA_NA it will
never get, and hence reduce the load on the server.

=20

Having said that, I think that DHCP currently is simply broken with
respect to multiple provisioning domains on the same wire.  The case
where choice 3 fails is a case where there are multiple provisioning
domains on the wire.   So I think that if we solve the MPD problem, we
will also have addressed the problem with choice 3.   Until we solve the
MPD problem, we really can't solve the problem with choice 3.

=20

So I am willing to provisionally agree that choice 3 is the right
choice, that RFC3315bis should mandate choice 3, and that we need an
additional errata that mandates choice 3.

=20

Ralph, I have to disagree with you that simply blessing the four errata
you mentioned solves this problem.   We need more text, unfortunately.

=20


------_=_NextPart_001_01CCB7B1.97854956
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:667904412;
	mso-list-type:hybrid;
	mso-list-template-ids:1371813778 -1090759538 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple style=3D'word-wrap: break-word;-webkit-nbsp-mode: =
space;-webkit-line-break: after-white-space'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I think that later including the IA_NA in a renew for the IA_PD in =
the RENEW is problematic &#8230;<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Read RFC 3315, 18.2.3:<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; When =
the server receives a Renew message that contains an IA =
option<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; from a =
client, it locates the client's binding and verifies that =
the<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
information in the IA from the client matches the information =
stored<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; for =
that client.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;font-family:"Courier =
New"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; If the =
server cannot find a client entry for the IA the =
server<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-autospace:none'><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
returns the IA containing no addresses with a Status Code option =
set<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; to =
NoBinding in the Reply message.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>This would require servers to remember bindings for items that they =
have no leases for, which seems rather odd? When should a server =
&#8216;forget&#8217; a binding? <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I think the cleanest is to use separate =
requests.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>What if you had two DHCPv6 servers &#8211; one that offered addresses =
and one that offered prefixes &#8230; Would the client accept both =
advertises?<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>If you have separate transactions, a lot of these issues go =
away.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I regret having suggested to Hemant a while ago when RFC 6204 was in =
Internet-Draft stage to have the CPE make one request, not two. I think =
treating the requests completely separate, while perhaps a bit less =
efficient, is just so much cleaner from an implementation and testing =
standpoint.<o:p></o:p></span></p><div =
style=3D'mso-element:para-border-div;border:none;border-bottom:solid =
windowtext 1.0pt;padding:0in 0in 1.0pt 0in'><p class=3DMsoNormal =
style=3D'border:none;padding:0in'><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p></div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>While RFC 3315 and RFC 3633 handle no address/prefix differently, I =
really don&#8217;t see that as such a big deal. A client can easily =
understand that NoAddrsAvail applies only to addresses, not prefixes. =
Personally, I would leave this alone. I really see no win to changing =
this because clients will have to support BOTH the old and new standard =
as they cannot assure what servers they will be communicating with =
&#8211; SO WHAT BENEFIT IS THERE????? It just adds to complexity and =
testing. I do NOT think this change in the errata is CORRECT. =
</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:red'>I=
 &#8220;vote&#8221; against it.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Cisco Network Registrar DHCP server has been sending back these =
results per the RFCs and it works just fine. Note that if we do send =
back an IA_PD with prefix information, we &#8220;violate&#8221; RFC 3315 =
text that says the NoAddrsAvail shouldn&#8217;t include &#8220;other =
configuration&#8221; options &#8230; so we will send &#8220;other =
configuration&#8221; options back to the client *<b>if</b>* we send back =
either IAPREFIX or IAADDR options (in the appropriate =
bindings).<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>We also discussed this issue at the DHCPv6 bakeoffs long =
ago.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Bernie<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] <b>On Behalf Of =
</b>Ted Lemon<br><b>Sent:</b> Tuesday, December 06, 2011 2:23 =
PM<br><b>To:</b> Hemant Singh (shemant)<br><b>Cc:</b> dhc WG; Ralph =
Droms<br><b>Subject:</b> Re: [dhcwg] Some high-priority errata for =
RFC3315/3396...<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On =
Dec 6, 2011, at 2:09 PM, Hemant Singh (shemant) =
wrote:<o:p></o:p></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal><span class=3Dapple-style-span><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'>OK, got =
it. &nbsp;I was confused from DHCPv4. &nbsp;So when the =
server-unicast</span></span><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'><br><span=
 class=3Dapple-style-span>option is set, then the relay does have to =
sniff unicast DHCPv6 messages</span><br><span =
class=3Dapple-style-span>which is not a new problem for choice 3. =
&nbsp;Thus I am for choice =
3.</span></span><o:p></o:p></p></blockquote></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>I think =
we should be aware that choice 3 does have the side effect that if a =
DHCP that would offer an IA_NA is offline, and then comes back online, a =
client that follows choice 3 as I understand it will never get an IA_NA. =
&nbsp; I realize that choice 3 (accept an offer that contains an IA_PD =
and no IA_NA, keep asking for IA_NA in subsequent renews, and do not =
fork another requestor for IA_NA) is attractive for the case where there =
is no DHCP server on the wire that *could* offer an IA_NA, however, =
since it will stop the client soliciting for an IA_NA it will never get, =
and hence reduce the load on the server.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Having said that, I think that DHCP currently is =
simply broken with respect to multiple provisioning domains on the same =
wire. &nbsp;The case where choice 3 fails is a case where there are =
multiple provisioning domains on the wire. &nbsp; So I think that if we =
solve the MPD problem, we will also have addressed the problem with =
choice 3. &nbsp; Until we solve the MPD problem, we really can't solve =
the problem with choice 3.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>So I am willing to provisionally agree that choice 3 =
is the right choice, that RFC3315bis should mandate choice 3, and that =
we need an additional errata that mandates choice =
3.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Ralph, I have to disagree with you that simply =
blessing the four errata you mentioned solves this problem. &nbsp; We =
need more text, unfortunately.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------_=_NextPart_001_01CCB7B1.97854956--

From volz@cisco.com  Sat Dec 10 19:07:30 2011
Return-Path: <volz@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 A3E8421F8B25 for <dhcwg@ietfa.amsl.com>; Sat, 10 Dec 2011 19:07:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IQ+OUborT-YW for <dhcwg@ietfa.amsl.com>; Sat, 10 Dec 2011 19:07:29 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 6DC8B21F8B01 for <dhcwg@ietf.org>; Sat, 10 Dec 2011 19:07:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=volz@cisco.com; l=6100; q=dns/txt; s=iport; t=1323572849; x=1324782449; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=UMf9YYxCgEesq5DiEndw6M/0HdZGPJDGXy6S6ULriRY=; b=gzwb3/oZMjDaLrWCPuHypN5htne53MRHzKekW97q8tn0DeMPouXtTvMG DIM3FrDFYpzWDQ0K8pKJFuT86ZDKvFuXRsQheIa7W5kMY5M+dkDDJkbw+ 8Oxq/pcycsLcZqQMgBmGsVN7ijFBXRXZuqBDzVdhtEQHlNpEULe5IxPvv s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqkAAM0d5E6tJXG8/2dsb2JhbABDmkGQPoEFgXIBAQEBAgEBAQEPAR0KNAsFBwQCAQgRBAEBCwYXAQYBJh8JCAEBBAESCBMHh2YIlm0BnUoEiwpjBIgxnwY
X-IronPort-AV: E=Sophos;i="4.71,333,1320624000"; d="scan'208";a="42881867"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-4.cisco.com with ESMTP; 11 Dec 2011 03:07:28 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core2-1.cisco.com (8.14.3/8.14.3) with ESMTP id pBB37SGm029605;  Sun, 11 Dec 2011 03:07:28 GMT
Received: from xmb-rcd-101.cisco.com ([72.163.62.143]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 10 Dec 2011 21:07:28 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 10 Dec 2011 21:07:27 -0600
Message-ID: <D9B5773329187548A0189ED6503667890A199E5B@XMB-RCD-101.cisco.com>
In-Reply-To: <867F4B6A1672E541A94676D556793ACD0CB445C90C@MOPESMBX01.eu.thmulti.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: AcyxrvDLFRNpP0jPR/yTrpdNLgYP9QDyptfAAI4JFbA=
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com><66EBF10F-A971-48BD-968B-1202CBF94B49@employees.org> <867F4B6A1672E541A94676D556793ACD0CB445C90C@MOPESMBX01.eu.thmulti.com>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Wuyts Carl" <Carl.Wuyts@technicolor.com>, "Ole Troan" <otroan@employees.org>, "Ted Lemon" <Ted.Lemon@nominum.com>
X-OriginalArrivalTime: 11 Dec 2011 03:07:28.0632 (UTC) FILETIME=[0403C780:01CCB7B2]
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Sun, 11 Dec 2011 03:07:30 -0000

>Maybe I'm cutting some corners here, but I think the main thing missing
in the RFC3315 is a clear state machine.

While there is no state machine diagram, the state machine is very clear
if you do a separate requests for each IA_*. Keep-it-simple.

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Wuyts Carl
Sent: Thursday, December 08, 2011 2:38 AM
To: Ole Troan; Ted Lemon
Cc: dhc WG
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...

All,

I think solution 3, i.e. including ia_na in renew if not received, would
be ok for us.

Some additional remark/Q:
While TR181 was progressing on defining the DHCPv6 part some time ago,
we've already given some feedback on the modelling, e.g. the model has
been made as such that 1 DHCPv6 client can "connect" to several DHCPv6
servers at the SAME time.  So, in order to get you options, you can
potentially get them from different DHCPv6 servers.  (so, not to check
who can give you what options, but really to fetch options from
different servers at the same time)

Now I read the below discussion on what to do if no ia_na gets provided,
only ia_pd.

Maybe I'm cutting some corners here, but I think the main thing missing
in the RFC3315 is a clear state machine.  This opens up the gate for
interpretations.  I've asked our BBF representative back then to
challenge the authors to provide us the procedure (i.e. state machine)
to use when an option would have either different content, is no longer
available at some server, ...  I've seen nothing on it.

Today, I've bumped onto this discussion.  As mentioned already, solution
3, including the ia_na in the renew if not received sounds reasonable to
us, but I saw some other possibilities like continuing to send discovers
for the ia_na only.  I must say I'm quite surprised to see this kind of
proposal ??!!
The same applies here: clear state machine would help a lot in these
matters.

Regs
Carl





-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Ole Troan
Sent: zaterdag 3 december 2011 12:30
To: Ted Lemon
Cc: dhc WG
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...

Ted,

s/3361/3633/g

phrased another way:
do we think we can do better than treating each stateful DHCPv6 option
(IA_NA, IA_TA, IA_PD) as separate protocol instances?
as in:
A DHCPv6 client MUST initiate a separate session for each IA_ option it
will request. DHCPv6 message behaviour and initiation will have slight
variations per option type. A DHCPv6 server that has more than one
stateful option to give to a client, MUST only include the requested IA_
option in any reply to the client.

cheers,
Ole

On Dec 3, 2011, at 4:18 , Ted Lemon wrote:

> There's been a bit of a discussion going on in the v6ops working group
about a problem in the DHCP protocol that has to do with the coexistence
of stateful address allocation and prefix delegation.
>=20
> The problem is that it's entirely possible that a PD requesting router
might also want an IP address to number its upstream interface, so it
might send a DHCP Solicit message containing both an IA_NA and an IA_PD.
Suppose the DHCP server is willing to do prefix delegation, but expects
the RR to do SLAAC for the upstream address.   In this case, it's going
to send an IA_PD containing one or more prefixes, but an IA_NA
containing no addresses.
>=20
> RFC3315 wasn't written with RFC3361 in mind, so it doesn't really talk
about what to do in this case.   It also doesn't address the problem of
what to do if an IA_TA appears in the solicit, but the server isn't
configured to offer temporary addresses.   This hasn't been much of an
issue since I don't know of any clients that actually request temporary
addresses, but of course it is an issue for IA_PD.
>=20
> There exist two errata that address this issue: erratum 2471 and
erratum 2472.   These errata propose to have the status code appear
inside the IA_NA option rather than in the outer layer of the Advertise
message.   A similar erratum exists for RFC3361, proposing to put the
status code option in the IA_PD option instead of, similarly, in the
outer layer of the packet.
>=20
> In addition, the following observation has been made:
>=20
>  The other unclear problem area is around how to deal with IA_PD and
IA_NA:
>    * Client requests both IA_NA and IA_PD in the same session, gets
only IA_PD.
>      - Does it fork off a separate session for IA_NA and continues
sending SOLICITs for only the IA_NA?
>      - Reset the DHCP client, and tries again?
>      - Keeps single session, and continues to ask for IA_NA on next
RENEW?
>=20
>      all 3 behaviors have been seen in the wild plus some additional
pathological cases.
>      in general dealing with multiple stateful options in DHCP is
underspecified.
>=20
> So the topic for discussion in the working group here is as follows:
>=20
> 1. Is what is proposed in the errata the right thing?   Should we in
fact have status codes inside of IA_* options instead of in the main
packet?
>=20
> 2. If so, what is the full set of edits to RFC3315 and RFC3361 that
are required to do this?
> 2a. What do we do for clients that don't implement the errata?
>=20
> 3. If not, what should we do instead?
>=20
> 4. If the client gets an IA_NA and no IA_PD, or vice versa, which of
the three behaviors listed above should it follow?   Is it bad that
different clients do this differently?
>=20
> 5. What have I missed?
>=20
> Comments?   Criticisms?   Rotten tomatoes?
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

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

From volz@cisco.com  Sat Dec 10 19:10:42 2011
Return-Path: <volz@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 111EA21F858C for <dhcwg@ietfa.amsl.com>; Sat, 10 Dec 2011 19:10:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8rY91iEBVn85 for <dhcwg@ietfa.amsl.com>; Sat, 10 Dec 2011 19:10:40 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id BF4C421F85A7 for <dhcwg@ietf.org>; Sat, 10 Dec 2011 19:10:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=volz@cisco.com; l=3225; q=dns/txt; s=iport; t=1323573040; x=1324782640; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=mpf3aSOarKeVErdWQyL8DCJO6dhAqlah8xE6eVkfSu0=; b=ledhuchxLVdwOWVbfqSve+n75Evn5iLtKyLceT7MiPGMh5kzsER7xino NDjAbbVkKtw/oNnFauEZehvdXJyz0xe5vjPCnpgBFaVFNzet9Uy1un/0v /FAYbcABSH0GWjG32rV8DS1cg+1eDY0fgAVYXgA8ciMy0xv4rgv3zD8ow A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqkAAAse5E6tJXG//2dsb2JhbABDmkGQPoEFgXIBAQEBAgEBAQEPAR0KNBAHBAIBCA4DBAEBAQoGFwEGASYfCQgBAQQBEggTB4dmCJZtAZ1KBIsKYwSIMZ8G
X-IronPort-AV: E=Sophos;i="4.71,333,1320624000"; d="scan'208";a="42874307"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-8.cisco.com with ESMTP; 11 Dec 2011 03:10:01 +0000
Received: from xbh-rcd-302.cisco.com (xbh-rcd-302.cisco.com [72.163.63.9]) by rcdn-core2-4.cisco.com (8.14.3/8.14.3) with ESMTP id pBB3A1Wh031757;  Sun, 11 Dec 2011 03:10:01 GMT
Received: from xmb-rcd-101.cisco.com ([72.163.62.143]) by xbh-rcd-302.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 10 Dec 2011 21:10:01 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 10 Dec 2011 21:10:00 -0600
Message-ID: <D9B5773329187548A0189ED6503667890A199E5C@XMB-RCD-101.cisco.com>
In-Reply-To: <4079EE5F-3682-42BD-9FC2-2D8FFE2F6B46@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: Acy19ayG6fF4fZqvTOasg7yUvmogFQBvG5hA
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com><4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com><4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com><D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com><95FDEE46-2731-4419-921B-1DA3A4F3FD92@gmail.com><601EE481-E4B8-48DC-9885-0FB3302DC8CB@nominum.com><4E70EB90-F9B2-46FB-8E4A-FB63429E94B9@gmail.com><521D1731-F4AD-471E-AF34-FAA22B7395EC@nominum.com> <4079EE5F-3682-42BD-9FC2-2D8FFE2F6B46@gmail.com>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Ralph Droms" <rdroms.ietf@gmail.com>, "dhc WG" <dhcwg@ietf.org>
X-OriginalArrivalTime: 11 Dec 2011 03:10:01.0562 (UTC) FILETIME=[5F2B0BA0:01CCB7B2]
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Sun, 11 Dec 2011 03:10:42 -0000

Simple ... fix these to specify separate requests!!!

W-5 should be:

   W-5:  DHCPv6 address assignment (IA_NA) and DHCPv6 prefix delegation
         (IA_PD) SHOULD NOT be done as a single DHCPv6 session - each
         SHOULD be done in a separate DHCPv6 session.

Similar changes to the others.

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Ralph Droms
Sent: Thursday, December 08, 2011 5:07 PM
To: dhc WG
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...

The context for this discussion is an I-D intended for publication as
Informational and updating RFC 6204: "Basic Requirements for IPv6
Customer Edge Routers," draft-ietf-v6ops-6204bis.  The specific problem
is defining the behavior of a IPv6 CE router that sends both an IA_PD
and an IA_NA in a Request message, and receives a delegated prefix in
the IA_PD but no assigned address in the IA_NA.

BTW, "this scenario can't happen" is not an answer; details available on
request.

The four errata cited earlier in this thread partially solve the problem
by scoping the NoAddrsAvail status code so the client can determine
which prefix and address requests were not fulfilled.  However, the
client's behavior after receiving NoAddrsAvail for some but not all IA_*
needs to be defined.

The following requirements from draft-ietf-v6ops-6204bis are related to
this issue:

   W-5:  DHCPv6 address assignment (IA_NA) and DHCPv6 prefix delegation
         (IA_PD) SHOULD be done as a single DHCPv6 session.

   WPD-5:  If the IPv6 CE router is configured to initiate DHCPv6 before
           receiving a Router Advertisement, it MUST also request an
           IA_NA option in DHCPv6.
=20
   WPD-7:  If the IPv6 CE router requests both an IA_NA and an IA_PD
           option in DHCPv6, it MUST accept an IA_PD option in DHCPv6
           Advertise/Reply messages, even if the message does not
           contain any addresses, unless configured to only obtain its
           WAN IPv6 address via DHCPv6.

The dhc WG needs to generate a single erratum or set of errata that form
a complete solution to the problem, so we can accept it/them against RFC
3315 and RFC 3633.  draft-ietf-v6ops-6204bis can then cite the
erratum/errata.

- Ralph

On Dec 6, 2011, at 4:11 PM 12/6/11, Ted Lemon wrote:

> On Dec 6, 2011, at 4:07 PM, Ralph Droms wrote:
>> What is the inconsistency you see?
>=20
> We're told to treat status codes as nested, but not what to do when we
get an offer that contains an IA_PD and not an IA_NA, and not what to do
when we receive a status code that's not nested, and not what to do as a
server if we have to send status codes for both IA_PD and IA_NA.   Maybe
"incomplete" is a better choice of words, but the point is that if we
just make these four changes, we are going to create more permutations
in acceptable set of behaviors that servers and clients may follow.
This is really bad for interoperability, and we can't easily take it
back once it's done.
>=20

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

From volz@cisco.com  Sat Dec 10 19:16:56 2011
Return-Path: <volz@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 B037821F85A8 for <dhcwg@ietfa.amsl.com>; Sat, 10 Dec 2011 19:16:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T0aJIpOoeCvY for <dhcwg@ietfa.amsl.com>; Sat, 10 Dec 2011 19:16:55 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id C3E0C21F8562 for <dhcwg@ietf.org>; Sat, 10 Dec 2011 19:16:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=volz@cisco.com; l=2195; q=dns/txt; s=iport; t=1323573415; x=1324783015; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=NzRzRAa9+mqHSZ8/orIHLWX0YgY5D0WEAWlxsjrlXqg=; b=mteWyC8x4agMKw6Aey1+eaQPaFb+g84cAHcez4GOWSMeyzaNuNeuNpHP 4GCimLFYyK+5jR1M4PLfAFdw/47BFaJhvgZkFmOzDp5vfhFf3e8WRwK8B TKbWXuiyyZCC7moWLHKqOt7unkjKkWnaWOPqnT1eGYQjAgew3F4yit4ii 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqkAAFUg5E6tJXG9/2dsb2JhbABDmkGQPoEFgXIBAQEBAwEBAQ8BHQo0CwwEAgEIEQQBAQsGFwEGASYfCQgCBAESCBqHbpZxAZ1JBIsKYwSIMZ8G
X-IronPort-AV: E=Sophos;i="4.71,333,1320624000"; d="scan'208";a="42877739"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-3.cisco.com with ESMTP; 11 Dec 2011 03:16:55 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core2-2.cisco.com (8.14.3/8.14.3) with ESMTP id pBB3GtIe026028;  Sun, 11 Dec 2011 03:16:55 GMT
Received: from xmb-rcd-101.cisco.com ([72.163.62.143]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 10 Dec 2011 21:16:55 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sat, 10 Dec 2011 21:16:54 -0600
Message-ID: <D9B5773329187548A0189ED6503667890A199E5D@XMB-RCD-101.cisco.com>
In-Reply-To: <EBA5E737-027B-40F2-AE1D-A48A2051F441@nominum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-00
Thread-Index: AQHMtpwjAljFLrkpaEuFQR2ym6HpQ5XV+CLA
References: <EBA5E737-027B-40F2-AE1D-A48A2051F441@nominum.com>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Ted Lemon" <Ted.Lemon@nominum.com>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 11 Dec 2011 03:16:55.0028 (UTC) FILETIME=[559CF340:01CCB7B3]
Cc: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-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: Sun, 11 Dec 2011 03:16:56 -0000

I think this draft needs to be updated a bit. It never mentions ANYTHING
about IA_PD.

I think whenever a server returns NoAddrsAvail or NoPrefixAvail status,
it should be able to provide this option in the response to indicate to
the client a new SOL_MAX_RT value for the IA type(s) requested by the
client.

The draft fails to solve the situation where a CPE routers that request
both an IA_NA and IA_PD (whether in one or two requests) does so
frequently. The current draft handles the case where addresses are not
being provided, but fails to handle the case where IA_PDs are also not
being provided.

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Ted Lemon
Sent: Friday, December 09, 2011 12:58 PM
To: dhcwg@ietf.org WG
Subject: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-00

Ralph's put in an individual submission draft with Jari as the
sponsoring AD.   The draft attempts to solve a problem ISPs are having
where in a massive IPv6 network that isn't entirely deployed, devices
are requesting configuration too often.

Ralph's draft proposes a new option whereby a DHCP server can indicate
in response to a solicit that the client should use a larger value for
SOL_MAX_RT.   This means that clients will continue their exponential
backoff to whatever limit is stated in the offer, and reduces the
overall traffic on the DHCP servers at the core of the network.

The draft is an individual submission, so it doesn't technically have to
pass dhcwg last call-just IETF last call.   However, since the dhcwg is
where DHCP protocol extensions are done, I'm doing a last call here to
encourage people to review it-it would really help if some wg
participants would review it and think about the implications.

If we don't hear anything by December 23, Jari will continue the process
of advancing the draft.   If you do read the draft, please comment here
as to whether you support it, and please offer any suggestions you may
have.

Thanks!

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

From Ted.Lemon@nominum.com  Sat Dec 10 23:07:55 2011
Return-Path: <Ted.Lemon@nominum.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 428E321F8B2E for <dhcwg@ietfa.amsl.com>; Sat, 10 Dec 2011 23:07:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.541
X-Spam-Level: 
X-Spam-Status: No, score=-106.541 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tFaB20AZNLnu for <dhcwg@ietfa.amsl.com>; Sat, 10 Dec 2011 23:07:54 -0800 (PST)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by ietfa.amsl.com (Postfix) with ESMTP id C2BF921F8AF8 for <dhcwg@ietf.org>; Sat, 10 Dec 2011 23:07:53 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKTuRWujvi8zYd1/1tNcc0uk95L+PejpjG@postini.com; Sat, 10 Dec 2011 23:07:53 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 60BE41B82D0 for <dhcwg@ietf.org>; Sat, 10 Dec 2011 23:07:38 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 3F740190052; Sat, 10 Dec 2011 23:07:38 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-02.WIN.NOMINUM.COM ([64.89.228.134]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.01.0339.001; Sat, 10 Dec 2011 23:07:38 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: AcyxakejwUXOElp7STCtYjgcemUphwDG63mAAAGEB4AAADFTAAAANTKAAAB3qAAAx95lQAAZ6WwA
Date: Sun, 11 Dec 2011 07:07:37 +0000
Message-ID: <FB7E334C-A138-4168-9C18-E142059391CC@nominum.com>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com><4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com><4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com> <D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com> <D9B5773329187548A0189ED6503667890A199E5A@XMB-RCD-101.cisco.com>
In-Reply-To: <D9B5773329187548A0189ED6503667890A199E5A@XMB-RCD-101.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_FB7E334CA13841689C18E142059391CCnominumcom_"
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Sun, 11 Dec 2011 07:07:55 -0000

--_000_FB7E334CA13841689C18E142059391CCnominumcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

On Dec 10, 2011, at 10:04 PM, Bernie Volz (volz) wrote:
   If the server cannot find a client entry for the IA the server
   returns the IA containing no addresses with a Status Code option set
   to NoBinding in the Reply message.

This would require servers to remember bindings for items that they have no=
 leases for, which seems rather odd? When should a server =91forget=92 a bi=
nding?

But doesn't it make sense in this case that there is no binding?   Why woul=
d the server need to remember anything?   Are you saying that the problem i=
s that since 3315 doesn't say the server can allocate an address at this po=
int, it can't?

Cisco Network Registrar DHCP server has been sending back these results per=
 the RFCs and it works just fine. Note that if we do send back an IA_PD wit=
h prefix information, we =93violate=94 RFC 3315 text that says the NoAddrsA=
vail shouldn=92t include =93other configuration=94 options =85 so we will s=
end =93other configuration=94 options back to the client *if* we send back =
either IAPREFIX or IAADDR options (in the appropriate bindings).

This is slightly OT, but if you think this is the right behavior, you shoul=
d probably submit an erratum for it if you haven't already.


--_000_FB7E334CA13841689C18E142059391CCnominumcom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <23BB215A179E1D4581AEB4B6F2B06DEB@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 10, 2011, at 10:04 PM, Bernie Volz (volz) wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 10pt; font-family: 'Courier New'; ">&nbsp;&nbsp; =
If the server cannot find a client entry for the IA the server<o:p></o:p></=
span></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 10pt; font-family: 'Courier New'; ">&nbsp;&nbsp; =
returns the IA containing no addresses with a Status Code option set<o:p></=
o:p></span></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 10pt; font-family: 'Courier New'; ">&nbsp;&nbsp; =
to NoBinding in the Reply message.</span><span style=3D"font-size: 11pt; fo=
nt-family: Calibri, sans-serif; color: rgb(31, 73, 125); "><o:p></o:p></spa=
n></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: rg=
b(31, 73, 125); "><o:p>&nbsp;</o:p></span></div>
<div style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; margin-=
bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New Roman', serif; "=
>
<span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: rg=
b(31, 73, 125); ">This would require servers to remember bindings for items=
 that they have no leases for, which seems rather odd? When should a server=
 =91forget=92 a binding?</span></div>
</span></blockquote>
</div>
<br>
<div>But doesn't it make sense in this case that there is no binding? &nbsp=
; Why would the server need to remember anything? &nbsp; Are you saying tha=
t the problem is that since 3315 doesn't say the server can allocate an add=
ress at this point, it can't?</div>
<div>
<div>
<div><span class=3D"Apple-style-span" style=3D"border-collapse: separate; f=
ont-family: Helvetica; font-style: normal; font-variant: normal; font-weigh=
t: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-al=
ign: -webkit-auto; text-indent: 0px; text-transform: none; white-space: nor=
mal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: n=
one; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-s=
ize: medium; "><span class=3D"Apple-style-span" style=3D"color: rgb(31, 73,=
 125); font-family: Calibri, sans-serif; font-size: 15px; "><br>
</span></span></div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; "><span class=3D"Apple-style-span" style=
=3D"color: rgb(31, 73, 125); font-family: Calibri, sans-serif; font-size: 1=
5px; ">Cisco
 Network Registrar DHCP server has been sending back these results per the =
RFCs and it works just fine. Note that if we do send back an IA_PD with pre=
fix information, we =93violate=94 RFC 3315 text that says the NoAddrsAvail =
shouldn=92t include =93other configuration=94
 options =85 so we will send =93other configuration=94 options back to the =
client *<b>if</b>* we send back either IAPREFIX or IAADDR options (in the a=
ppropriate bindings).</span></span></blockquote>
</div>
<br>
</div>
<div>This is slightly OT, but if you think this is the right behavior, you =
should probably submit an erratum for it if you haven't already.</div>
<div><br>
</div>
</body>
</html>

--_000_FB7E334CA13841689C18E142059391CCnominumcom_--

From volz@cisco.com  Sun Dec 11 06:48:44 2011
Return-Path: <volz@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 2CFE021F84D2 for <dhcwg@ietfa.amsl.com>; Sun, 11 Dec 2011 06:48:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.523
X-Spam-Level: 
X-Spam-Status: No, score=-6.523 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bt0d4zmluGDV for <dhcwg@ietfa.amsl.com>; Sun, 11 Dec 2011 06:48:42 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 521E021F842B for <dhcwg@ietf.org>; Sun, 11 Dec 2011 06:48:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=volz@cisco.com; l=12879; q=dns/txt; s=iport; t=1323614922; x=1324824522; h=mime-version:subject:date:message-id:in-reply-to: references:from:to:cc; bh=rU0a+Q8UgW/o65ZGVOEyw1aWgoVgmmShLx4PA4+apJU=; b=JoH8u42eAVt/rQbOVjpTmMMY0jw6OIanW2ybTpL2ji6oOmpGwT6OxsuX gyrnSKq5oD7DNxbGMOgqVCzUAOWBpYwyU+WxGTj9cYG8Yh5Am07yVLQIJ Rz///LnvYLzHEEk/itB/XsLIC+Izm5+ARewxOgmiU9KHUhv+iSyi7FArE 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApQAABHC5E6tJV2a/2dsb2JhbABDgk2XZZA+gQWBcgEBAQQSAQkRA0kQAgEIEQQBAQsGFwEGAUUJCAIEEwganlgBnS+LCmMEiDGfBg
X-IronPort-AV: E=Sophos;i="4.71,335,1320624000"; d="scan'208,217";a="42935144"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-6.cisco.com with ESMTP; 11 Dec 2011 14:48:35 +0000
Received: from xbh-rcd-302.cisco.com (xbh-rcd-302.cisco.com [72.163.63.9]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pBBEmZ0G009581;  Sun, 11 Dec 2011 14:48:35 GMT
Received: from xmb-rcd-101.cisco.com ([72.163.62.143]) by xbh-rcd-302.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 11 Dec 2011 08:48:35 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCB813.F569C18B"
Date: Sun, 11 Dec 2011 08:48:31 -0600
Message-ID: <D9B5773329187548A0189ED6503667890A199E6B@XMB-RCD-101.cisco.com>
In-Reply-To: <FB7E334C-A138-4168-9C18-E142059391CC@nominum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: AcyxakejwUXOElp7STCtYjgcemUphwDG63mAAAGEB4AAADFTAAAANTKAAAB3qAAAx95lQAAZ6WwAAAC68VA=
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com><4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com><4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com> <D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com> <D9B5773329187548A0189ED6503667890A199E5A@XMB-RCD-101.cisco.com> <FB7E334C-A138-4168-9C18-E142059391CC@nominum.com>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Ted Lemon" <Ted.Lemon@nominum.com>
X-OriginalArrivalTime: 11 Dec 2011 14:48:35.0185 (UTC) FILETIME=[F5A25E10:01CCB813]
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Sun, 11 Dec 2011 14:48:44 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CCB813.F569C18B
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

>Are you saying that the problem is that since 3315 doesn't say the
server can allocate an address at this point, it can't?

=20

Correct. That is what RFC 3315 says. As the Solicit/Request didn't
return an IAADDR for the IA_NA, the binding would not exist and hence
RENEW says the server must return NoBinding status. So, that forces the
client to go back to Solicit/Request for the IA_NA.

=20

-          Bernie

=20

From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
Sent: Sunday, December 11, 2011 2:08 AM
To: Bernie Volz (volz)
Cc: Hemant Singh (shemant); dhc WG; Ralph Droms
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...

=20

On Dec 10, 2011, at 10:04 PM, Bernie Volz (volz) wrote:

	   If the server cannot find a client entry for the IA the
server

	   returns the IA containing no addresses with a Status Code
option set

	   to NoBinding in the Reply message.

	=20

	This would require servers to remember bindings for items that
they have no leases for, which seems rather odd? When should a server
'forget' a binding?

=20

But doesn't it make sense in this case that there is no binding?   Why
would the server need to remember anything?   Are you saying that the
problem is that since 3315 doesn't say the server can allocate an
address at this point, it can't?





	Cisco Network Registrar DHCP server has been sending back these
results per the RFCs and it works just fine. Note that if we do send
back an IA_PD with prefix information, we "violate" RFC 3315 text that
says the NoAddrsAvail shouldn't include "other configuration" options
... so we will send "other configuration" options back to the client
*if* we send back either IAPREFIX or IAADDR options (in the appropriate
bindings).

=20

This is slightly OT, but if you think this is the right behavior, you
should probably submit an erratum for it if you haven't already.

=20


------_=_NextPart_001_01CCB813.F569C18B
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:713234949;
	mso-list-type:hybrid;
	mso-list-template-ids:-497546710 -443755858 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:23;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple style=3D'word-wrap: break-word;-webkit-nbsp-mode: =
space;-webkit-line-break: after-white-space'><div =
class=3DWordSection1><p class=3DMsoNormal>&gt;Are you saying that the =
problem is that since 3315 doesn't say the server can allocate an =
address at this point, it can't?<o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Correct. That is what RFC 3315 says. As the Solicit/Request =
didn&#8217;t return an IAADDR for the IA_NA, the binding would not exist =
and hence RENEW says the server must return NoBinding status. So, that =
forces the client to go back to Solicit/Request for the =
IA_NA.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Bernie<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Ted Lemon [mailto:Ted.Lemon@nominum.com] <br><b>Sent:</b> Sunday, =
December 11, 2011 2:08 AM<br><b>To:</b> Bernie Volz (volz)<br><b>Cc:</b> =
Hemant Singh (shemant); dhc WG; Ralph Droms<br><b>Subject:</b> Re: =
[dhcwg] Some high-priority errata for =
RFC3315/3396...<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On =
Dec 10, 2011, at 10:04 PM, Bernie Volz (volz) =
wrote:<o:p></o:p></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><div><p =
class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; If the server cannot find a client entry for the IA =
the server</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
returns the IA containing no addresses with a Status Code option =
set</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; to =
NoBinding in the Reply message.</span><o:p></o:p></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;</span><o:p></o:p></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>This would require servers to remember bindings for items that they =
have no leases for, which seems rather odd? When should a server =
&#8216;forget&#8217; a =
binding?</span><o:p></o:p></p></div></blockquote></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>But =
doesn't it make sense in this case that there is no binding? &nbsp; Why =
would the server need to remember anything? &nbsp; Are you saying that =
the problem is that since 3315 doesn't say the server can allocate an =
address at this point, it can't?<o:p></o:p></p></div><div><div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><br><br></span><o:p></o:p></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal><span class=3Dapple-style-span><span =
style=3D'font-size:11.5pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Cisco Network Registrar DHCP server has been sending back these =
results per the RFCs and it works just fine. Note that if we do send =
back an IA_PD with prefix information, we &#8220;violate&#8221; RFC 3315 =
text that says the NoAddrsAvail shouldn&#8217;t include &#8220;other =
configuration&#8221; options &#8230; so we will send &#8220;other =
configuration&#8221; options back to the client *<b>if</b>* we send back =
either IAPREFIX or IAADDR options (in the appropriate =
bindings).</span></span><o:p></o:p></p></blockquote></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>This is slightly OT, but if you think this is the =
right behavior, you should probably submit an erratum for it if you =
haven't already.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------_=_NextPart_001_01CCB813.F569C18B--

From shemant@cisco.com  Sun Dec 11 08:18:07 2011
Return-Path: <shemant@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 B548C21F851F for <dhcwg@ietfa.amsl.com>; Sun, 11 Dec 2011 08:18:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.516
X-Spam-Level: 
X-Spam-Status: No, score=-6.516 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cN+0ybYr4rCD for <dhcwg@ietfa.amsl.com>; Sun, 11 Dec 2011 08:18:06 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id B9A3621F8513 for <dhcwg@ietf.org>; Sun, 11 Dec 2011 08:18:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=4159; q=dns/txt; s=iport; t=1323620286; x=1324829886; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=7ExUXECqFxQuzl+lW9HrIZhDxDwVAYNE0/wi7N0C10M=; b=E8/7X//KsX5l7UrDxQ7DgmjQi4iIZWdAByeuQB0tfotKDG8UXr7G0s2n G52lqV2n1XfL9Yj9xFLG+M8EujgZFlTMP9dcntA/eKXJdafu9Sb8c1z+c 92lBisvJd/YNuf/4b0Z+y15T+fJMHcTJZsgQvT1SWMBWXq18jk5jaKYLH A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoUAAJ3W5E6tJXG9/2dsb2JhbABDmjKQPoEFgXIBAQEBAgEBAQEPAR0KNAsFBwQCAQgRBAEBAQoGFwEGASYfCQgBAQQBEggTB4dmCJZZAZ0pBIsKYwSIMZ8G
X-IronPort-AV: E=Sophos;i="4.71,335,1320624000"; d="scan'208";a="42967923"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-1.cisco.com with ESMTP; 11 Dec 2011 16:18:06 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core2-2.cisco.com (8.14.3/8.14.3) with ESMTP id pBBGI6oh002543;  Sun, 11 Dec 2011 16:18:06 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 11 Dec 2011 10:18:06 -0600
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 11 Dec 2011 10:18:05 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C3038294A8@XMB-RCD-109.cisco.com>
In-Reply-To: <D9B5773329187548A0189ED6503667890A199E5C@XMB-RCD-101.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: Acy19ayG6fF4fZqvTOasg7yUvmogFQBvG5hAABthwgA=
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com><4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com><4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com><D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com><95FDEE46-2731-4419-921B-1DA3A4F3FD92@gmail.com><601EE481-E4B8-48DC-9885-0FB3302DC8CB@nominum.com><4E70EB90-F9B2-46FB-8E4A-FB63429E94B9@gmail.com><521D1731-F4AD-471E-AF34-FAA22B7395EC@nominum.com><4079EE5F-3682-42BD-9FC2-2D8FFE2F6B46@gmail.com> <D9B5773329187548A0189ED6503667890A199E5C@XMB-RCD-101.cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, "Ralph Droms" <rdroms.ietf@gmail.com>, "dhc WG" <dhcwg@ietf.org>
X-OriginalArrivalTime: 11 Dec 2011 16:18:06.0200 (UTC) FILETIME=[77023780:01CCB820]
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Sun, 11 Dec 2011 16:18:07 -0000

Bernie,

For W-5 what is the harm with keeping the SHOULD which you recommend to
change to a SHOULD NOT? I have a DHCPv6 relay agent which after reload
has to get 100K DHCPv6 clients online as expeditiously as possible.  In
such a network, I have the DHCPv6 server serving both the IA_NA and the
IA_PD so that one single SOLICIT per client gets both options to the
client.  Why send 200K SOLICITs when one can make do with 100K SOLICITs?
The CMTS DHCPv6 relay agent upstream is also a bandwidth constrained
link. =20

Hemant=20

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Bernie Volz (volz)
Sent: Saturday, December 10, 2011 10:10 PM
To: Ralph Droms; dhc WG
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...

Simple ... fix these to specify separate requests!!!

W-5 should be:

   W-5:  DHCPv6 address assignment (IA_NA) and DHCPv6 prefix delegation
         (IA_PD) SHOULD NOT be done as a single DHCPv6 session - each
         SHOULD be done in a separate DHCPv6 session.

Similar changes to the others.

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Ralph Droms
Sent: Thursday, December 08, 2011 5:07 PM
To: dhc WG
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...

The context for this discussion is an I-D intended for publication as
Informational and updating RFC 6204: "Basic Requirements for IPv6
Customer Edge Routers," draft-ietf-v6ops-6204bis.  The specific problem
is defining the behavior of a IPv6 CE router that sends both an IA_PD
and an IA_NA in a Request message, and receives a delegated prefix in
the IA_PD but no assigned address in the IA_NA.

BTW, "this scenario can't happen" is not an answer; details available on
request.

The four errata cited earlier in this thread partially solve the problem
by scoping the NoAddrsAvail status code so the client can determine
which prefix and address requests were not fulfilled.  However, the
client's behavior after receiving NoAddrsAvail for some but not all IA_*
needs to be defined.

The following requirements from draft-ietf-v6ops-6204bis are related to
this issue:

   W-5:  DHCPv6 address assignment (IA_NA) and DHCPv6 prefix delegation
         (IA_PD) SHOULD be done as a single DHCPv6 session.

   WPD-5:  If the IPv6 CE router is configured to initiate DHCPv6 before
           receiving a Router Advertisement, it MUST also request an
           IA_NA option in DHCPv6.
=20
   WPD-7:  If the IPv6 CE router requests both an IA_NA and an IA_PD
           option in DHCPv6, it MUST accept an IA_PD option in DHCPv6
           Advertise/Reply messages, even if the message does not
           contain any addresses, unless configured to only obtain its
           WAN IPv6 address via DHCPv6.

The dhc WG needs to generate a single erratum or set of errata that form
a complete solution to the problem, so we can accept it/them against RFC
3315 and RFC 3633.  draft-ietf-v6ops-6204bis can then cite the
erratum/errata.

- Ralph

On Dec 6, 2011, at 4:11 PM 12/6/11, Ted Lemon wrote:

> On Dec 6, 2011, at 4:07 PM, Ralph Droms wrote:
>> What is the inconsistency you see?
>=20
> We're told to treat status codes as nested, but not what to do when we
get an offer that contains an IA_PD and not an IA_NA, and not what to do
when we receive a status code that's not nested, and not what to do as a
server if we have to send status codes for both IA_PD and IA_NA.   Maybe
"incomplete" is a better choice of words, but the point is that if we
just make these four changes, we are going to create more permutations
in acceptable set of behaviors that servers and clients may follow.
This is really bad for interoperability, and we can't easily take it
back once it's done.
>=20

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

From shemant@cisco.com  Sun Dec 11 08:35:22 2011
Return-Path: <shemant@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 3A8B521F84B9 for <dhcwg@ietfa.amsl.com>; Sun, 11 Dec 2011 08:35:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.516
X-Spam-Level: 
X-Spam-Status: No, score=-6.516 tagged_above=-999 required=5 tests=[AWL=0.082,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rtg775FTMz0l for <dhcwg@ietfa.amsl.com>; Sun, 11 Dec 2011 08:35:20 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 9A3F221F84B8 for <dhcwg@ietf.org>; Sun, 11 Dec 2011 08:35:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=10962; q=dns/txt; s=iport; t=1323621320; x=1324830920; h=mime-version:subject:date:message-id:in-reply-to: references:from:to:cc; bh=JiODbme2clUjuoElchAh5tAWAFBu7WC+xp+g9h28kGQ=; b=HbWKLnQWRHMMtdqdJl8mHym1K3zzDNY4p+SEND973jnKGV55thnkyVxN CzyZ66RfAsNXwPG21ccY5aUsi6KWdFi43za+MC0I9ut3Mt7Pf7zRGDTHM lf6cFj+FAuMENeTEl1ZDWvt4VDRlVQgzX/9YTRU85KNYYFlru4QcvJ0EQ 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoUAAHXb5E6tJXG//2dsb2JhbABDgk2XZZA/gQWBcgEBAQEDEgEJEQNJEAIBCBEEAQELBhgGAU4IAgQBGhqeRQGdLYsKYwSHfjOfBg
X-IronPort-AV: E=Sophos;i="4.71,335,1320624000"; d="scan'208,217";a="42977112"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-7.cisco.com with ESMTP; 11 Dec 2011 16:35:20 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core2-4.cisco.com (8.14.3/8.14.3) with ESMTP id pBBGZKMD029959;  Sun, 11 Dec 2011 16:35:20 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 11 Dec 2011 10:35:19 -0600
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCB822.DF05CB6B"
Date: Sun, 11 Dec 2011 10:35:19 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C3038294AF@XMB-RCD-109.cisco.com>
In-Reply-To: <D9B5773329187548A0189ED6503667890A199E6B@XMB-RCD-101.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: AcyxakejwUXOElp7STCtYjgcemUphwDG63mAAAGEB4AAADFTAAAANTKAAAB3qAAAx95lQAAZ6WwAAAC68VAAAiUAQA==
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com><4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com><4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com> <D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com> <D9B5773329187548A0189ED6503667890A199E5A@XMB-RCD-101.cisco.com> <FB7E334C-A138-4168-9C18-E142059391CC@nominum.com> <D9B5773329187548A0189ED6503667890A199E6B@XMB-RCD-101.cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, "Ted Lemon" <Ted.Lemon@nominum.com>
X-OriginalArrivalTime: 11 Dec 2011 16:35:19.0940 (UTC) FILETIME=[DF2A6C40:01CCB822]
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Sun, 11 Dec 2011 16:35:22 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CCB822.DF05CB6B
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

The Renew includes the Client Identifier option and also other IA's the =
client is renewing.  With the Client Identifier option the server can =
search for the client in the server database and find one or more IA's =
to return.  So seeing a new option in the Renew, why can't the server =
allocate a new IA_NA  to return to the client?   Since we are discussing =
changing RFC 3315, is such a thought (perhaps na=EFve - am not a DHCPv6 =
guru) possible for a change.  =20

=20

Hemant

=20

From: Bernie Volz (volz)=20
Sent: Sunday, December 11, 2011 9:49 AM
To: Ted Lemon
Cc: Hemant Singh (shemant); dhc WG; Ralph Droms
Subject: RE: [dhcwg] Some high-priority errata for RFC3315/3396...

=20

>Are you saying that the problem is that since 3315 doesn't say the =
server can allocate an address at this point, it can't?

=20

Correct. That is what RFC 3315 says. As the Solicit/Request didn't =
return an IAADDR for the IA_NA, the binding would not exist and hence =
RENEW says the server must return NoBinding status. So, that forces the =
client to go back to Solicit/Request for the IA_NA.

=20

-        Bernie


------_=_NextPart_001_01CCB822.DF05CB6B
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1"><meta name=3DGenerator content=3D"Microsoft Word =
12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:713234949;
	mso-list-type:hybrid;
	mso-list-template-ids:-497546710 -443755858 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:23;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple style=3D'word-wrap: break-word;-webkit-nbsp-mode: =
space;-webkit-line-break: after-white-space'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>The Renew includes the Client Identifier option and also other =
IA&#8217;s the client is renewing.=A0 With the Client Identifier option =
the server can search for the client in the server database and find one =
or more IA&#8217;s to return.=A0 So seeing a new option in the Renew, =
why can&#8217;t the server allocate a new IA_NA=A0 to return to the =
client?=A0=A0 Since we are discussing changing RFC 3315, is such a =
thought (perhaps na=EFve &#8211; am not a DHCPv6 guru) possible for a =
change.=A0=A0 <o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hemant<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Bernie Volz (volz) <br><b>Sent:</b> Sunday, December 11, 2011 9:49 =
AM<br><b>To:</b> Ted Lemon<br><b>Cc:</b> Hemant Singh (shemant); dhc WG; =
Ralph Droms<br><b>Subject:</b> RE: [dhcwg] Some high-priority errata for =
RFC3315/3396...<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>&gt;Are you =
saying that the problem is that since 3315 doesn't say the server can =
allocate an address at this point, it can't?<o:p></o:p></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Correct. That is what RFC 3315 says. As the Solicit/Request =
didn&#8217;t return an IAADDR for the IA_NA, the binding would not exist =
and hence RENEW says the server must return NoBinding status. So, that =
forces the client to go back to Solicit/Request for the =
IA_NA.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo2'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Bernie<o:p></o:p></span></p></div></body></html>
------_=_NextPart_001_01CCB822.DF05CB6B--

From Ted.Lemon@nominum.com  Sun Dec 11 09:05:19 2011
Return-Path: <Ted.Lemon@nominum.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 B113621F8510 for <dhcwg@ietfa.amsl.com>; Sun, 11 Dec 2011 09:05:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.543
X-Spam-Level: 
X-Spam-Status: No, score=-106.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N3crcCJvyUHA for <dhcwg@ietfa.amsl.com>; Sun, 11 Dec 2011 09:05:19 -0800 (PST)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id CC2C621F84DF for <dhcwg@ietf.org>; Sun, 11 Dec 2011 09:05:18 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKTuTiwW4Xh9y+aJTdyzYYEUcYrMKvXchm@postini.com; Sun, 11 Dec 2011 09:05:18 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 908701B8286 for <dhcwg@ietf.org>; Sun, 11 Dec 2011 09:05:04 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id F0B91190052; Sun, 11 Dec 2011 09:05:01 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-02.WIN.NOMINUM.COM ([64.89.228.134]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0339.001; Sun, 11 Dec 2011 09:05:01 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: AcyxakejwUXOElp7STCtYjgcemUphwDG63mAAAGEB4AAADFTAAAANTKAAAB3qAAAAGY5AAACDugAAAEzHIAAACKTgABmgwiAAG8tqgAAG4YDgAABo56A
Date: Sun, 11 Dec 2011 17:05:01 +0000
Message-ID: <39799F0D-F473-4A71-9E8D-A7E1DA6B5B5F@nominum.com>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com><4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com><4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com><D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com><95FDEE46-2731-4419-921B-1DA3A4F3FD92@gmail.com><601EE481-E4B8-48DC-9885-0FB3302DC8CB@nominum.com><4E70EB90-F9B2-46FB-8E4A-FB63429E94B9@gmail.com><521D1731-F4AD-471E-AF34-FAA22B7395EC@nominum.com><4079EE5F-3682-42BD-9FC2-2D8FFE2F6B46@gmail.com> <D9B5773329187548A0189ED6503667890A199E5C@XMB-RCD-101.cisco.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3038294A8@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C3038294A8@XMB-RCD-109.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <27D37620B5CAD34FB000E56230EA274C@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Sun, 11 Dec 2011 17:05:19 -0000

On Dec 11, 2011, at 11:18 AM, Hemant Singh (shemant) wrote:
> Why send 200K SOLICITs when one can make do with 100K SOLICITs?

I think the core issue that needs to be resolved here is whether or not we =
_can_ make an update to the protocol that allows what you want, Hemant, or =
whether Bernie's position of keeping it simple is better.   Definitely at t=
he moment option 3 is not recognized as a valid behavior in RFC3315: an RFC=
3315-compliant DHCP server would _always_ respond to an IA_NA that wasn't f=
ulfilled in the original Solicit with a NoBinding status.

But as you say, Bernie's proposal requires us to send twice as many initial=
 Solicits, and that adds up to a lot.   So that argues for the option where=
 if there is a negative response to the IA_NA, but not the IA_PD, the clien=
t bifurcates its state machine.   This is actually something we discussed b=
ack when we were writing RFC3315, and is behavior that we anticipated then,=
 in that case for situations where the DHCP client wanted to get addresses =
on two prefixes, and the DHCP server only offered addresses on one.

At the time we weren't sure when or why this would happen, so we didn't mak=
e any strong recommendations about how to do it, instead deferring to whate=
ver insight the future might bring.   Well, now it seems that we have that =
insight.

> So seeing a new option in the Renew, why can=92t the server allocate a ne=
w IA_NA  to return to the client?   Since we are discussing changing RFC 33=
15, is such a thought (perhaps na=EFve =96 am not a DHCPv6 guru) possible f=
or a change.=20

So yes, in order to get option 3, we need to change RFC3315.   We are alrea=
dy proposing a change, so we could do this if that were the consensus.   Ho=
wever, there's a bit of a choice to be made.

We could go with the dead simple option that Bernie proposes: one state mac=
hine for IA_NA, one per IA_PD.   This requires fairly minimal changes, but =
has a big downside in doubling the traffic to the server.

Actually, though, that's not the complete story.   Since the client will be=
 getting a NoAddrsAvail response on the IA_NA, it will keep trying, which m=
eans that we'll actually see *substantially* more traffic in this case if w=
e follow the "keep it simple" approach.

The same is true of the bifurcation approach.   It saves us the initial sol=
icit packet, but none of the subsequent ones.   So in the case where there =
is going to be no address offered on the IA_NA, this isn't particularly win=
ning=97we still get a ton of traffic.   In the case that we have one server=
 serving both IA_NA and IA_PD, however, this is a marginal win: it halves t=
he traffic hitting the server.

The third case, where we make a change to RFC3315 as Hemant suggests to all=
ow addresses to be allocated on renew, is the biggest win in terms of reduc=
ing traffic.   We can send a single solicit, and when we get the IA_PD, we =
give up on the IA_NA until the next renew, and trust that if addresses beco=
me available, the server we've chosen will offer us one.

Of course, the third alternative does mean that if the DHCP server that off=
ers IA_NAs is down when a particular client first connects to the network, =
it will never get an IA_NA.

So I think the question that needs to be answered, if you have read this fa=
r, is whether the use case where one server serves IA_NA and a different se=
rver serves IA_PD is a realistic use case that we need to address.=

From volz@cisco.com  Sun Dec 11 17:08:32 2011
Return-Path: <volz@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 0E34621F8469 for <dhcwg@ietfa.amsl.com>; Sun, 11 Dec 2011 17:08:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.539
X-Spam-Level: 
X-Spam-Status: No, score=-6.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WnI1PTvYMOAC for <dhcwg@ietfa.amsl.com>; Sun, 11 Dec 2011 17:08:31 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 04F3021F8467 for <dhcwg@ietf.org>; Sun, 11 Dec 2011 17:08:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=volz@cisco.com; l=5757; q=dns/txt; s=iport; t=1323652111; x=1324861711; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=pQarhZmStxTMqQawgg1w3NODc7KEWvCGTKi77InaOF4=; b=DZnbKbCKpjBiC2TzgCpVidDeOiJ44wfRUgT1oMoIhd8P6eVws0wGtiEk bVqaSqL4QHppXWUL5APghtKD10knd5PaPaek6dCoOtoJ/foJUxLGJtLXO KuXip0LpZB8+Z6dtGJuQeCSYIw6BQ5SYZKnnA79R8S3/EnaSuvGB3WJBK o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap8AANRS5U6tJV2c/2dsb2JhbAA5CpozkEGBBYFyAQEBAwESAR1JBQcEAgEIEQQBAQEKBhcBBgFFCQgCBAESCBYEh2aWPQGdJog0glZjBId+M58G
X-IronPort-AV: E=Sophos;i="4.71,336,1320624000"; d="scan'208";a="43029644"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-1.cisco.com with ESMTP; 12 Dec 2011 01:08:30 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id pBC18Uqa025567;  Mon, 12 Dec 2011 01:08:30 GMT
Received: from xmb-rcd-101.cisco.com ([72.163.62.143]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 11 Dec 2011 19:08:30 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 11 Dec 2011 19:08:28 -0600
Message-ID: <D9B5773329187548A0189ED6503667890A199ECC@XMB-RCD-101.cisco.com>
In-Reply-To: <39799F0D-F473-4A71-9E8D-A7E1DA6B5B5F@nominum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: AcyxakejwUXOElp7STCtYjgcemUphwDG63mAAAGEB4AAADFTAAAANTKAAAB3qAAAAGY5AAACDugAAAEzHIAAACKTgABmgwiAAG8tqgAAG4YDgAABo56AAABXjzA=
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com><4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com><4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com><D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com><95FDEE46-2731-4419-921B-1DA3A4F3FD92@gmail.com><601EE481-E4B8-48DC-9885-0FB3302DC8CB@nominum.com><4E70EB90-F9B2-46FB-8E4A-FB63429E94B9@gmail.com><521D1731-F4AD-471E-AF34-FAA22B7395EC@nominum.com><4079EE5F-3682-42BD-9FC2-2D8FFE2F6B46@gmail.com> <D9B5773329187548A0189ED6503667890A199E5C@XMB-RCD-101.cisco.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3038294A8@XMB-RCD-109.cisco.com> <39799F0D-F473-4A71-9E8D-A7E1DA6B5B5F@nominum.com>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Ted Lemon" <Ted.Lemon@nominum.com>, "Hemant Singh (shemant)" <shemant@cisco.com>
X-OriginalArrivalTime: 12 Dec 2011 01:08:30.0435 (UTC) FILETIME=[8FBB1B30:01CCB86A]
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Mon, 12 Dec 2011 01:08:32 -0000

>Since the client will be getting a NoAddrsAvail response
>on the IA_NA, it will keep trying, which means that we'll
>actually see *substantially* more traffic in this case if
>we follow the "keep it simple" approach.

I assume we'll be recommending Ralph's MAX_SOL_RT internet-draft to =
reduce this burden.


>From Hemant's message:

> For W-5 what is the harm with keeping the SHOULD which you recommend =
to change to a SHOULD NOT?

I guess it really doesn't matter if the client wants to try for both in =
a single request ... it just comes down to what happens if it gets only =
addresses or only prefixes - what does the client do then?

If it is supposed to keep trying (of course, adopting Ralph's MAX_SOL_RT =
internet-draft) for the one that it didn't get, that's fine ... just =
means more testing on the part of the coder. (There are other issues =
with piggybacking the address and prefix requests in a single "session" =
as the lifetimes and renewal times could be different and then either =
the client renews both at the earlier time or splits the requests. Most =
probably just renew at the earlier time.)

If the client is supposed to just wait until a "normal" RENEW and we =
allow the server to process the unknown binding (treating it like a =
REQUEST), that's fine too but it means that you can't have one server =
provide addresses and another prefixes (which is probably a marginal =
case).


It just seems to me that the client state machine is a bit easier to =
implement and test if you avoid putting both in a single request and =
treat them completely separate. Yes, it does mean more requests - but =
each request is also a bit simpler. It also has other benefits since it =
avoids confusion of 'other configuration' data - the PD related other =
configuration options are then easier to identify and pass on to clients =
eventually getting addresses from those delegated prefixes.

- Bernie

-----Original Message-----
From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
Sent: Sunday, December 11, 2011 12:05 PM
To: Hemant Singh (shemant)
Cc: Bernie Volz (volz); Ralph Droms; dhc WG
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...

On Dec 11, 2011, at 11:18 AM, Hemant Singh (shemant) wrote:
> Why send 200K SOLICITs when one can make do with 100K SOLICITs?

I think the core issue that needs to be resolved here is whether or not =
we _can_ make an update to the protocol that allows what you want, =
Hemant, or whether Bernie's position of keeping it simple is better.   =
Definitely at the moment option 3 is not recognized as a valid behavior =
in RFC3315: an RFC3315-compliant DHCP server would _always_ respond to =
an IA_NA that wasn't fulfilled in the original Solicit with a NoBinding =
status.

But as you say, Bernie's proposal requires us to send twice as many =
initial Solicits, and that adds up to a lot.   So that argues for the =
option where if there is a negative response to the IA_NA, but not the =
IA_PD, the client bifurcates its state machine.   This is actually =
something we discussed back when we were writing RFC3315, and is =
behavior that we anticipated then, in that case for situations where the =
DHCP client wanted to get addresses on two prefixes, and the DHCP server =
only offered addresses on one.

At the time we weren't sure when or why this would happen, so we didn't =
make any strong recommendations about how to do it, instead deferring to =
whatever insight the future might bring.   Well, now it seems that we =
have that insight.

> So seeing a new option in the Renew, why can't the server allocate a =
new IA_NA  to return to the client?   Since we are discussing changing =
RFC 3315, is such a thought (perhaps na=EFve - am not a DHCPv6 guru) =
possible for a change.=20

So yes, in order to get option 3, we need to change RFC3315.   We are =
already proposing a change, so we could do this if that were the =
consensus.   However, there's a bit of a choice to be made.

We could go with the dead simple option that Bernie proposes: one state =
machine for IA_NA, one per IA_PD.   This requires fairly minimal =
changes, but has a big downside in doubling the traffic to the server.

Actually, though, that's not the complete story.   Since the client will =
be getting a NoAddrsAvail response on the IA_NA, it will keep trying, =
which means that we'll actually see *substantially* more traffic in this =
case if we follow the "keep it simple" approach.

The same is true of the bifurcation approach.   It saves us the initial =
solicit packet, but none of the subsequent ones.   So in the case where =
there is going to be no address offered on the IA_NA, this isn't =
particularly winning-we still get a ton of traffic.   In the case that =
we have one server serving both IA_NA and IA_PD, however, this is a =
marginal win: it halves the traffic hitting the server.

The third case, where we make a change to RFC3315 as Hemant suggests to =
allow addresses to be allocated on renew, is the biggest win in terms of =
reducing traffic.   We can send a single solicit, and when we get the =
IA_PD, we give up on the IA_NA until the next renew, and trust that if =
addresses become available, the server we've chosen will offer us one.

Of course, the third alternative does mean that if the DHCP server that =
offers IA_NAs is down when a particular client first connects to the =
network, it will never get an IA_NA.

So I think the question that needs to be answered, if you have read this =
far, is whether the use case where one server serves IA_NA and a =
different server serves IA_PD is a realistic use case that we need to =
address.

From Ted.Lemon@nominum.com  Sun Dec 11 19:08:58 2011
Return-Path: <Ted.Lemon@nominum.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 7261421F850D for <dhcwg@ietfa.amsl.com>; Sun, 11 Dec 2011 19:08:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.544
X-Spam-Level: 
X-Spam-Status: No, score=-106.544 tagged_above=-999 required=5 tests=[AWL=0.054, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1z-+HWFpRQJ8 for <dhcwg@ietfa.amsl.com>; Sun, 11 Dec 2011 19:08:57 -0800 (PST)
Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by ietfa.amsl.com (Postfix) with ESMTP id 7E61821F84D7 for <dhcwg@ietf.org>; Sun, 11 Dec 2011 19:08:57 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob121.postini.com ([64.18.6.12]) with SMTP ID DSNKTuVwN9t8qymdpA9qkT/G9cyVnOMOb2y7@postini.com; Sun, 11 Dec 2011 19:08:57 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 27E9B1B8299 for <dhcwg@ietf.org>; Sun, 11 Dec 2011 19:08:39 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 0D532190052; Sun, 11 Dec 2011 19:08:38 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-02.WIN.NOMINUM.COM ([64.89.228.134]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0339.001; Sun, 11 Dec 2011 19:08:37 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: AcyxakejwUXOElp7STCtYjgcemUphwDG63mAAAGEB4AAADFTAAAANTKAAAB3qAAAAGY5AAACDugAAAEzHIAAACKTgABmgwiAAG8tqgAAG4YDgAABo56AAABXjzAAFLzmAA==
Date: Mon, 12 Dec 2011 03:08:36 +0000
Message-ID: <F2FF6C58-B6EA-4FB3-8B77-DFA5D98C2805@nominum.com>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com><4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com><4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com><D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com><95FDEE46-2731-4419-921B-1DA3A4F3FD92@gmail.com><601EE481-E4B8-48DC-9885-0FB3302DC8CB@nominum.com><4E70EB90-F9B2-46FB-8E4A-FB63429E94B9@gmail.com><521D1731-F4AD-471E-AF34-FAA22B7395EC@nominum.com><4079EE5F-3682-42BD-9FC2-2D8FFE2F6B46@gmail.com> <D9B5773329187548A0189ED6503667890A199E5C@XMB-RCD-101.cisco.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3038294A8@XMB-RCD-109.cisco.com> <39799F0D-F473-4A71-9E8D-A7E1DA6B5B5F@nominum.com> <D9B5773329187548A0189ED6503667890A199ECC@XMB-RCD-101.cisco.com>
In-Reply-To: <D9B5773329187548A0189ED6503667890A199ECC@XMB-RCD-101.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_F2FF6C58B6EA4FB38B77DFA5D98C2805nominumcom_"
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Mon, 12 Dec 2011 03:08:58 -0000

--_000_F2FF6C58B6EA4FB38B77DFA5D98C2805nominumcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On Dec 11, 2011, at 8:08 PM, Bernie Volz (volz) wrote:
It just seems to me that the client state machine is a bit easier to implem=
ent and test if you avoid putting both in a single request and treat them c=
ompletely separate. Yes, it does mean more requests - but each request is a=
lso a bit simpler. It also has other benefits since it avoids confusion of =
'other configuration' data - the PD related other configuration options are=
 then easier to identify and pass on to clients eventually getting addresse=
s from those delegated prefixes.

So you agree with Lorenzo that the O bit signifies the availability of PD i=
nformation?

I think that there is no difference in the client state machine if it can b=
ifurcate after sending a unified Solicit.   That's really a transport issue=
, not a state machine issue: if both state machines want to request their r=
espective IA_NA and IA_PD at the same time, you combine them in a single so=
licit; otherwise you send them separately.

I think there's a better way to deal with the issue of using different serv=
ers to configure different things, which will take a bit longer to address =
and hence should be addressed separately.   So I'd be pretty happy to simpl=
y say that a Renew with an unsatisfied IA_NA can allocate an address for th=
at IA_NA, and that the client should only have one state machine when it wa=
nts both an IA_NA and an IA_PD.


--_000_F2FF6C58B6EA4FB38B77DFA5D98C2805nominumcom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <F0ED8FE35C941541994C325CD4AEDAB8@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 11, 2011, at 8:08 PM, Bernie Volz (volz) wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">It
 just seems to me that the client state machine is a bit easier to implemen=
t and test if you avoid putting both in a single request and treat them com=
pletely separate. Yes, it does mean more requests - but each request is als=
o a bit simpler. It also has other
 benefits since it avoids confusion of 'other configuration' data - the PD =
related other configuration options are then easier to identify and pass on=
 to clients eventually getting addresses from those delegated prefixes.</sp=
an></blockquote>
</div>
<br>
<div>So you agree with Lorenzo that the O bit signifies the availability of=
 PD information?</div>
<div><br>
</div>
<div>I think that there is no difference in the client state machine if it =
can bifurcate after sending a unified Solicit. &nbsp; That's really a trans=
port issue, not a state machine issue: if both state machines want to reque=
st their respective IA_NA and IA_PD at
 the same time, you combine them in a single solicit; otherwise you send th=
em separately.</div>
<div><br>
</div>
<div>I think there's a better way to deal with the issue of using different=
 servers to configure different things, which will take a bit longer to add=
ress and hence should be addressed separately. &nbsp; So I'd be pretty happ=
y to simply say that a Renew with an
 unsatisfied IA_NA can allocate an address for that IA_NA, and that the cli=
ent should only have one state machine when it wants both an IA_NA and an I=
A_PD.&nbsp;</div>
<div><br>
</div>
</body>
</html>

--_000_F2FF6C58B6EA4FB38B77DFA5D98C2805nominumcom_--

From volz@cisco.com  Sun Dec 11 19:45:58 2011
Return-Path: <volz@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 BBE2521F863E for <dhcwg@ietfa.amsl.com>; Sun, 11 Dec 2011 19:45:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.548
X-Spam-Level: 
X-Spam-Status: No, score=-6.548 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FOboGsgwKb5C for <dhcwg@ietfa.amsl.com>; Sun, 11 Dec 2011 19:45:57 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id DB71221F847A for <dhcwg@ietf.org>; Sun, 11 Dec 2011 19:45:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=volz@cisco.com; l=9563; q=dns/txt; s=iport; t=1323661557; x=1324871157; h=mime-version:subject:date:message-id:in-reply-to: references:from:to:cc; bh=S4Ujpy/9JG8yyXE86IRkmf1IW0A9i63WE+xI9GdTNSI=; b=ILc1plZ7FhTh0W8/wonCCceZi3nJy7R+TdMhxC6JzJFRNfii+n1cuQje cBDkM0r9V/6MJMdeMVk7u7rXqGrhKFDGJseFlE+744ipNCieUtueVb58a 1Hz5c67fY4W2smeO9JmgdNrBX3A3TUsP/hILLLGP9JUWXwHhnxEztA7yh E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: An0AACJ45U6tJV2Z/2dsb2JhbAA5CoJNl2aQQYEFgXIBAQEEEgEJEQNJEAIBCBEEAQELBhcBBgFFCQgCBBMIGp41AZ0niDSCVmMEiDGfBg
X-IronPort-AV: E=Sophos;i="4.71,336,1320624000"; d="scan'208,217";a="43046743"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-1.cisco.com with ESMTP; 12 Dec 2011 03:45:55 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pBC3jtEN024480;  Mon, 12 Dec 2011 03:45:55 GMT
Received: from xmb-rcd-101.cisco.com ([72.163.62.143]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 11 Dec 2011 21:45:55 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCB880.8D14A48F"
Date: Sun, 11 Dec 2011 21:45:53 -0600
Message-ID: <D9B5773329187548A0189ED6503667890A199EEB@XMB-RCD-101.cisco.com>
In-Reply-To: <F2FF6C58-B6EA-4FB3-8B77-DFA5D98C2805@nominum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: AcyxakejwUXOElp7STCtYjgcemUphwDG63mAAAGEB4AAADFTAAAANTKAAAB3qAAAAGY5AAACDugAAAEzHIAAACKTgABmgwiAAG8tqgAAG4YDgAABo56AAABXjzAAFLzmAAAPhx1Q
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com><4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com><4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com><D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com><95FDEE46-2731-4419-921B-1DA3A4F3FD92@gmail.com><601EE481-E4B8-48DC-9885-0FB3302DC8CB@nominum.com><4E70EB90-F9B2-46FB-8E4A-FB63429E94B9@gmail.com><521D1731-F4AD-471E-AF34-FAA22B7395EC@nominum.com><4079EE5F-3682-42BD-9FC2-2D8FFE2F6B46@gmail.com> <D9B5773329187548A0189ED6503667890A199E5C@XMB-RCD-101.cisco.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3038294A8@XMB-RCD-109.cisco.com> <39799F0D-F473-4A71-9E8D-A7E1DA6B5B5F@nominum.com> <D9B5773329187548A0189ED6503667890A199ECC@XMB-RCD-101.cisco.com> <F2FF6C58-B6EA-4FB3-8B77-DFA5D98C2805@nominum.com>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Ted Lemon" <Ted.Lemon@nominum.com>
X-OriginalArrivalTime: 12 Dec 2011 03:45:55.0181 (UTC) FILETIME=[8D3CF9D0:01CCB880]
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Mon, 12 Dec 2011 03:45:58 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CCB880.8D14A48F
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

>So you agree with Lorenzo that the O bit signifies the availability of
PD information?

=20

Not sure how you draw that conclusion. I didn't think we were discussing
this question.

=20

To me M means managed stuff (i.e., Solicit with IA_NA and/or IA_PD)
whereas O means Information-Request.

=20

-          Bernie

=20

From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
Sent: Sunday, December 11, 2011 10:09 PM
To: Bernie Volz (volz)
Cc: Hemant Singh (shemant); Ralph Droms; dhc WG
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...

=20

On Dec 11, 2011, at 8:08 PM, Bernie Volz (volz) wrote:

	It just seems to me that the client state machine is a bit
easier to implement and test if you avoid putting both in a single
request and treat them completely separate. Yes, it does mean more
requests - but each request is also a bit simpler. It also has other
benefits since it avoids confusion of 'other configuration' data - the
PD related other configuration options are then easier to identify and
pass on to clients eventually getting addresses from those delegated
prefixes.

=20

So you agree with Lorenzo that the O bit signifies the availability of
PD information?

=20

I think that there is no difference in the client state machine if it
can bifurcate after sending a unified Solicit.   That's really a
transport issue, not a state machine issue: if both state machines want
to request their respective IA_NA and IA_PD at the same time, you
combine them in a single solicit; otherwise you send them separately.

=20

I think there's a better way to deal with the issue of using different
servers to configure different things, which will take a bit longer to
address and hence should be addressed separately.   So I'd be pretty
happy to simply say that a Renew with an unsatisfied IA_NA can allocate
an address for that IA_NA, and that the client should only have one
state machine when it wants both an IA_NA and an IA_PD.=20

=20


------_=_NextPart_001_01CCB880.8D14A48F
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:66148580;
	mso-list-type:hybrid;
	mso-list-template-ids:-1002260772 616043608 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple style=3D'word-wrap: break-word;-webkit-nbsp-mode: =
space;-webkit-line-break: after-white-space'><div =
class=3DWordSection1><p class=3DMsoNormal>&gt;So you agree with Lorenzo =
that the O bit signifies the availability of PD =
information?<o:p></o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Not sure how you draw that conclusion. I didn&#8217;t think we were =
discussing this question.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>To me M means managed stuff (i.e., Solicit with IA_NA and/or IA_PD) =
whereas O means Information-Request.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Bernie<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Ted Lemon [mailto:Ted.Lemon@nominum.com] <br><b>Sent:</b> Sunday, =
December 11, 2011 10:09 PM<br><b>To:</b> Bernie Volz =
(volz)<br><b>Cc:</b> Hemant Singh (shemant); Ralph Droms; dhc =
WG<br><b>Subject:</b> Re: [dhcwg] Some high-priority errata for =
RFC3315/3396...<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On =
Dec 11, 2011, at 8:08 PM, Bernie Volz (volz) =
wrote:<o:p></o:p></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal><span class=3Dapple-style-span><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'>It just =
seems to me that the client state machine is a bit easier to implement =
and test if you avoid putting both in a single request and treat them =
completely separate. Yes, it does mean more requests - but each request =
is also a bit simpler. It also has other benefits since it avoids =
confusion of 'other configuration' data - the PD related other =
configuration options are then easier to identify and pass on to clients =
eventually getting addresses from those delegated =
prefixes.</span></span><o:p></o:p></p></blockquote></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>So you =
agree with Lorenzo that the O bit signifies the availability of PD =
information?<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
think that there is no difference in the client state machine if it can =
bifurcate after sending a unified Solicit. &nbsp; That's really a =
transport issue, not a state machine issue: if both state machines want =
to request their respective IA_NA and IA_PD at the same time, you =
combine them in a single solicit; otherwise you send them =
separately.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
think there's a better way to deal with the issue of using different =
servers to configure different things, which will take a bit longer to =
address and hence should be addressed separately. &nbsp; So I'd be =
pretty happy to simply say that a Renew with an unsatisfied IA_NA can =
allocate an address for that IA_NA, and that the client should only have =
one state machine when it wants both an IA_NA and an =
IA_PD.&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------_=_NextPart_001_01CCB880.8D14A48F--

From Ted.Lemon@nominum.com  Sun Dec 11 21:04:17 2011
Return-Path: <Ted.Lemon@nominum.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 6F12021F853A for <dhcwg@ietfa.amsl.com>; Sun, 11 Dec 2011 21:04:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.545
X-Spam-Level: 
X-Spam-Status: No, score=-106.545 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6LF5mdpzzWCD for <dhcwg@ietfa.amsl.com>; Sun, 11 Dec 2011 21:04:17 -0800 (PST)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by ietfa.amsl.com (Postfix) with ESMTP id AA07E21F84FD for <dhcwg@ietf.org>; Sun, 11 Dec 2011 21:04:16 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKTuWLRIQcaOsqdwHE1A+6ykOQm6AspF8h@postini.com; Sun, 11 Dec 2011 21:04:16 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 9410B1B8299 for <dhcwg@ietf.org>; Sun, 11 Dec 2011 21:04:03 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 7BCD8190052; Sun, 11 Dec 2011 21:04:02 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-02.WIN.NOMINUM.COM ([64.89.228.134]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.01.0339.001; Sun, 11 Dec 2011 21:04:02 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: AcyxakejwUXOElp7STCtYjgcemUphwDG63mAAAGEB4AAADFTAAAANTKAAAB3qAAAAGY5AAACDugAAAEzHIAAACKTgABmgwiAAG8tqgAAG4YDgAABo56AAABXjzAAFLzmAAAPhx1Q//8d6pk=
Date: Mon, 12 Dec 2011 05:04:01 +0000
Message-ID: <358A60A1-CBA1-40CD-BB39-4FDDFBE794B3@nominum.com>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com><4E7DBCFD-CAE3-4D63-8CB0-4BB75526768F@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D03@XMB-RCD-109.cisco.com><4F4D6714-7D70-4F94-82B7-3C564C35ECE2@gmail.com><5B6B2B64C9FE2A489045EEEADDAFF2C303778D25@XMB-RCD-109.cisco.com><D2A0EC97-5C60-4D23-98CA-3E0E269872DF@nominum.com><95FDEE46-2731-4419-921B-1DA3A4F3FD92@gmail.com><601EE481-E4B8-48DC-9885-0FB3302DC8CB@nominum.com><4E70EB90-F9B2-46FB-8E4A-FB63429E94B9@gmail.com><521D1731-F4AD-471E-AF34-FAA22B7395EC@nominum.com><4079EE5F-3682-42BD-9FC2-2D8FFE2F6B46@gmail.com> <D9B5773329187548A0189ED6503667890A199E5C@XMB-RCD-101.cisco.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3038294A8@XMB-RCD-109.cisco.com> <39799F0D-F473-4A71-9E8D-A7E1DA6B5B5F@nominum.com> <D9B5773329187548A0189ED6503667890A199ECC@XMB-RCD-101.cisco.com> <F2FF6C58-B6EA-4FB3-8B77-DFA5D98C2805@nominum.com>, <D9B5773329187548A0189ED6503667890A199EEB@XMB-RCD-101.cisco.com>
In-Reply-To: <D9B5773329187548A0189ED6503667890A199EEB@XMB-RCD-101.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_358A60A1CBA140CDBB394FDDFBE794B3nominumcom_"
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Mon, 12 Dec 2011 05:04:17 -0000

--_000_358A60A1CBA140CDBB394FDDFBE794B3nominumcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

On Dec 11, 2011, at 10:45 PM, "Bernie Volz (volz)" <volz@cisco.com<mailto:v=
olz@cisco.com>> wrote:
Not sure how you draw that conclusion. I didn=92t think we were discussing =
this question.
 To me M means managed stuff (i.e., Solicit with IA_NA and/or IA_PD) wherea=
s O means Information-Request.

Hm, okay.   I drew the conclusion from the way you grouped IA_PD with other=
 information, but I must have misunderstood.   Unfortunately, there isn't f=
irm agreement outside of the DHCP community that the M bit applies to PD as=
 well as regular addressing.   We never made it explicit.


--_000_358A60A1CBA140CDBB394FDDFBE794B3nominumcom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body bgcolor=3D"#FFFFFF">
<div>On Dec 11, 2011, at 10:45 PM, &quot;Bernie Volz (volz)&quot; &lt;<a hr=
ef=3D"mailto:volz@cisco.com">volz@cisco.com</a>&gt; wrote:<br>
</div>
<blockquote type=3D"cite">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Not sure how you draw tha=
t conclusion. I didn=92t think we were discussing this question.<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
span class=3D"Apple-style-span" style=3D"color: rgb(31, 73, 125); font-fami=
ly: Calibri, sans-serif; font-size: 15px; -webkit-tap-highlight-color: rgba=
(26, 26, 26, 0.296875); -webkit-composition-fill-color: rgba(175, 192, 227,=
 0.230469); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469); =
">To
 me M means managed stuff (i.e., Solicit with IA_NA and/or IA_PD) whereas O=
 means Information-Request.</span></p>
</blockquote>
<br>
<div></div>
<div>Hm, okay. &nbsp; I drew the conclusion from the way you grouped IA_PD =
with other information, but I must have misunderstood. &nbsp; Unfortunately=
, there isn't firm agreement outside of the DHCP community that the M bit a=
pplies to PD as well as regular addressing.
 &nbsp; We never made it explicit.</div>
<div><br>
</div>
</body>
</html>

--_000_358A60A1CBA140CDBB394FDDFBE794B3nominumcom_--

From Hans.Dedecker@technicolor.com  Mon Dec 12 01:32:21 2011
Return-Path: <Hans.Dedecker@technicolor.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 DCDA821F8AF8 for <dhcwg@ietfa.amsl.com>; Mon, 12 Dec 2011 01:32:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level: 
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lg9xNp42cJDz for <dhcwg@ietfa.amsl.com>; Mon, 12 Dec 2011 01:32:20 -0800 (PST)
Received: from na3sys009aog108.obsmtp.com (na3sys009aog108.obsmtp.com [74.125.149.199]) by ietfa.amsl.com (Postfix) with ESMTP id E2DA721F8AF0 for <dhcwg@ietf.org>; Mon, 12 Dec 2011 01:32:18 -0800 (PST)
Received: from mopesedge02.eu.thmulti.com ([129.35.174.203]) (using TLSv1) by na3sys009aob108.postini.com ([74.125.148.12]) with SMTP ID DSNKTuXKFEh5W1z7OHiipFJyzrWTi8eJAdi5@postini.com; Mon, 12 Dec 2011 01:32:20 PST
Received: from MOPESMAILHC03.eu.thmulti.com (141.11.100.132) by mopesedge02.eu.thmulti.com (141.11.253.23) with Microsoft SMTP Server (TLS) id 8.3.192.1; Mon, 12 Dec 2011 10:29:51 +0100
Received: from MOPESMBX01.eu.thmulti.com ([169.254.155.121]) by MOPESMAILHC03.eu.thmulti.com ([141.11.100.132]) with mapi; Mon, 12 Dec 2011 10:30:14 +0100
From: Dedecker Hans <Hans.Dedecker@technicolor.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, Ole Troan <otroan@employees.org>, Ted Lemon <Ted.Lemon@nominum.com>, Wuyts Carl <Carl.Wuyts@technicolor.com>
Date: Mon, 12 Dec 2011 10:30:09 +0100
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: AcyxrvDLFRNpP0jPR/yTrpdNLgYP9QDyptfAAI4JFbAAPd6z4A==
Message-ID: <3F4910A77924AF44876B1A096ECC92A7D411F1897C@MOPESMBX01.eu.thmulti.com>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com><66EBF10F-A971-48BD-968B-1202CBF94B49@employees.org> <867F4B6A1672E541A94676D556793ACD0CB445C90C@MOPESMBX01.eu.thmulti.com> <D9B5773329187548A0189ED6503667890A199E5B@XMB-RCD-101.cisco.com>
In-Reply-To: <D9B5773329187548A0189ED6503667890A199E5B@XMB-RCD-101.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Mon, 12 Dec 2011 09:32:22 -0000

Don't agree that creating separate requests for each IA_* will make the DHC=
Pv6 client state machine simpler. Let's just think about the non IA_ option=
s (eg DNS recursive name server) which are potentially included in the resp=
onses by the DHCPv6 servers. If for the IA_PD response the server includes =
DNS recursive name server option A and for IA_NA the server includes name s=
erver option B which one should be used ? Maybe this is not so important wh=
en the the reponses orginate from the same server but what if the responses=
 come from different servers ? If everything is done in one request such co=
mplexity will not arise; also I'm wondering what the ORO option value shoul=
d contain for each separate IA_x request?
To me it seems the state machine will only get complexer as the behavior sh=
ould be clear/defined for all options and not only the IA_PD/IA_NA options.


Regs,
Hans =20

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of B=
ernie Volz (volz)
Sent: zondag 11 december 2011 4:07
To: Wuyts Carl; Ole Troan; Ted Lemon
Cc: dhc WG
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...

>Maybe I'm cutting some corners here, but I think the main thing missing
in the RFC3315 is a clear state machine.

While there is no state machine diagram, the state machine is very clear if=
 you do a separate requests for each IA_*. Keep-it-simple.

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of W=
uyts Carl
Sent: Thursday, December 08, 2011 2:38 AM
To: Ole Troan; Ted Lemon
Cc: dhc WG
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...

All,

I think solution 3, i.e. including ia_na in renew if not received, would be=
 ok for us.

Some additional remark/Q:
While TR181 was progressing on defining the DHCPv6 part some time ago, we'v=
e already given some feedback on the modelling, e.g. the model has been mad=
e as such that 1 DHCPv6 client can "connect" to several DHCPv6 servers at t=
he SAME time.  So, in order to get you options, you can potentially get the=
m from different DHCPv6 servers.  (so, not to check who can give you what o=
ptions, but really to fetch options from different servers at the same time=
)

Now I read the below discussion on what to do if no ia_na gets provided, on=
ly ia_pd.

Maybe I'm cutting some corners here, but I think the main thing missing in =
the RFC3315 is a clear state machine.  This opens up the gate for interpret=
ations.  I've asked our BBF representative back then to challenge the autho=
rs to provide us the procedure (i.e. state machine) to use when an option w=
ould have either different content, is no longer available at some server, =
...  I've seen nothing on it.

Today, I've bumped onto this discussion.  As mentioned already, solution 3,=
 including the ia_na in the renew if not received sounds reasonable to us, =
but I saw some other possibilities like continuing to send discovers for th=
e ia_na only.  I must say I'm quite surprised to see this kind of proposal =
??!!
The same applies here: clear state machine would help a lot in these matter=
s.

Regs
Carl





-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of O=
le Troan
Sent: zaterdag 3 december 2011 12:30
To: Ted Lemon
Cc: dhc WG
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...

Ted,

s/3361/3633/g

phrased another way:
do we think we can do better than treating each stateful DHCPv6 option (IA_=
NA, IA_TA, IA_PD) as separate protocol instances?
as in:
A DHCPv6 client MUST initiate a separate session for each IA_ option it wil=
l request. DHCPv6 message behaviour and initiation will have slight variati=
ons per option type. A DHCPv6 server that has more than one stateful option=
 to give to a client, MUST only include the requested IA_ option in any rep=
ly to the client.

cheers,
Ole

On Dec 3, 2011, at 4:18 , Ted Lemon wrote:

> There's been a bit of a discussion going on in the v6ops working group
about a problem in the DHCP protocol that has to do with the coexistence of=
 stateful address allocation and prefix delegation.
>=20
> The problem is that it's entirely possible that a PD requesting router
might also want an IP address to number its upstream interface, so it might=
 send a DHCP Solicit message containing both an IA_NA and an IA_PD.
Suppose the DHCP server is willing to do prefix delegation, but expects
the RR to do SLAAC for the upstream address.   In this case, it's going
to send an IA_PD containing one or more prefixes, but an IA_NA containing n=
o addresses.
>=20
> RFC3315 wasn't written with RFC3361 in mind, so it doesn't really talk
about what to do in this case.   It also doesn't address the problem of
what to do if an IA_TA appears in the solicit, but the server isn't
configured to offer temporary addresses.   This hasn't been much of an
issue since I don't know of any clients that actually request temporary add=
resses, but of course it is an issue for IA_PD.
>=20
> There exist two errata that address this issue: erratum 2471 and
erratum 2472.   These errata propose to have the status code appear
inside the IA_NA option rather than in the outer layer of the Advertise
message.   A similar erratum exists for RFC3361, proposing to put the
status code option in the IA_PD option instead of, similarly, in the outer =
layer of the packet.
>=20
> In addition, the following observation has been made:
>=20
>  The other unclear problem area is around how to deal with IA_PD and
IA_NA:
>    * Client requests both IA_NA and IA_PD in the same session, gets
only IA_PD.
>      - Does it fork off a separate session for IA_NA and continues
sending SOLICITs for only the IA_NA?
>      - Reset the DHCP client, and tries again?
>      - Keeps single session, and continues to ask for IA_NA on next
RENEW?
>=20
>      all 3 behaviors have been seen in the wild plus some additional
pathological cases.
>      in general dealing with multiple stateful options in DHCP is
underspecified.
>=20
> So the topic for discussion in the working group here is as follows:
>=20
> 1. Is what is proposed in the errata the right thing?   Should we in
fact have status codes inside of IA_* options instead of in the main packet=
?
>=20
> 2. If so, what is the full set of edits to RFC3315 and RFC3361 that
are required to do this?
> 2a. What do we do for clients that don't implement the errata?
>=20
> 3. If not, what should we do instead?
>=20
> 4. If the client gets an IA_NA and no IA_PD, or vice versa, which of
the three behaviors listed above should it follow?   Is it bad that
different clients do this differently?
>=20
> 5. What have I missed?
>=20
> Comments?   Criticisms?   Rotten tomatoes?
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

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

From ichiroumakino@gmail.com  Mon Dec 12 02:01:13 2011
Return-Path: <ichiroumakino@gmail.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 DF1E821F8B04 for <dhcwg@ietfa.amsl.com>; Mon, 12 Dec 2011 02:01:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.489
X-Spam-Level: 
X-Spam-Status: No, score=-3.489 tagged_above=-999 required=5 tests=[AWL=0.110,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id inIjMBV9cVJy for <dhcwg@ietfa.amsl.com>; Mon, 12 Dec 2011 02:01:13 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1BA2E21F8B02 for <dhcwg@ietf.org>; Mon, 12 Dec 2011 02:01:12 -0800 (PST)
Received: by faas1 with SMTP id s1so1219230faa.31 for <dhcwg@ietf.org>; Mon, 12 Dec 2011 02:01:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=q9BEWvBjQUIJJyCPjEcGAQ18wBUHhqFmFRaBcbAwDOk=; b=Am6Ta27At2rPY61BotYA+LkuwKOifdPdxjPe/5Or4e0MEy9nC+3nr8W+75GngXrTv+ vmXHUTJmDLlk5E8T4EKi19KP7WGyyXquvS1RY1ObDSE4JLFb4gfOXB8iX7TDC589ta/U nvfe2M79VQCSpsf2NnNF8nNOim9JpxrIgJz6I=
Received: by 10.180.91.137 with SMTP id ce9mr21949883wib.5.1323684072054; Mon, 12 Dec 2011 02:01:12 -0800 (PST)
Received: from [10.147.12.196] (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id m13sm22814344wbh.0.2011.12.12.02.01.09 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 12 Dec 2011 02:01:10 -0800 (PST)
Sender: Ole Troan <ichiroumakino@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <otroan@employees.org>
In-Reply-To: <3F4910A77924AF44876B1A096ECC92A7D411F1897C@MOPESMBX01.eu.thmulti.com>
Date: Mon, 12 Dec 2011 11:01:08 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC492F1B-5B24-44C7-856D-AECBB9FCB3AD@employees.org>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com><66EBF10F-A971-48BD-968B-1202CBF94B49@employees.org> <867F4B6A1672E541A94676D556793ACD0CB445C90C@MOPESMBX01.eu.thmulti.com> <D9B5773329187548A0189ED6503667890A199E5B@XMB-RCD-101.cisco.com> <3F4910A77924AF44876B1A096ECC92A7D411F1897C@MOPESMBX01.eu.thmulti.com>
To: Dedecker Hans <Hans.Dedecker@technicolor.com>
X-Mailer: Apple Mail (2.1084)
Cc: dhc WG <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Mon, 12 Dec 2011 10:01:14 -0000

>=20
> Don't agree that creating separate requests for each IA_* will make =
the DHCPv6 client state machine simpler. Let's just think about the non =
IA_ options (eg DNS recursive name server) which are potentially =
included in the responses by the DHCPv6 servers. If for the IA_PD =
response the server includes DNS recursive name server option A and for =
IA_NA the server includes name server option B which one should be used =
? Maybe this is not so important when the the reponses orginate from the =
same server but what if the responses come from different servers ? If =
everything is done in one request such complexity will not arise; also =
I'm wondering what the ORO option value should contain for each separate =
IA_x request?
> To me it seems the state machine will only get complexer as the =
behavior should be clear/defined for all options and not only the =
IA_PD/IA_NA options.

and this doesn't only apply to IA_PD versus IA_NA. it would also apply =
to IA_TA, and any other stateful option that we may concoct in the =
future.

my assumption has been:
 - a single interface of a DHCP client is bound to a single DHCP domain.
 - in a DHCP domain all DHCP servers are operated by a single =
administrative entity

is it then not a configuration error that multiple DHCP servers give a =
different view of the world?

cheers,
Ole=

From Ted.Lemon@nominum.com  Mon Dec 12 12:27:07 2011
Return-Path: <Ted.Lemon@nominum.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 5790C21F8ACA for <dhcwg@ietfa.amsl.com>; Mon, 12 Dec 2011 12:27:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.547
X-Spam-Level: 
X-Spam-Status: No, score=-106.547 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EtAbRG82pIgg for <dhcwg@ietfa.amsl.com>; Mon, 12 Dec 2011 12:27:06 -0800 (PST)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id 81E7621F84D5 for <dhcwg@ietf.org>; Mon, 12 Dec 2011 12:27:06 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKTuZjjbWxz7EOOLNtqA83aD3sDNPKZXhs@postini.com; Mon, 12 Dec 2011 12:27:06 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 81A291B8272 for <dhcwg@ietf.org>; Mon, 12 Dec 2011 12:26:53 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 6DEA2190052; Mon, 12 Dec 2011 12:26:52 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-02.WIN.NOMINUM.COM ([64.89.228.134]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0339.001; Mon, 12 Dec 2011 12:26:52 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ole Troan <otroan@employees.org>
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: AcyxakejwUXOElp7STCtYjgcemUphwAh65kAAPNdA4AAjWnGgAA/qDWAAAEVBAAAFdpXgA==
Date: Mon, 12 Dec 2011 20:26:52 +0000
Message-ID: <6CC91264-8D82-4FC6-AE4E-99B1A5BCC47F@nominum.com>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com><66EBF10F-A971-48BD-968B-1202CBF94B49@employees.org> <867F4B6A1672E541A94676D556793ACD0CB445C90C@MOPESMBX01.eu.thmulti.com> <D9B5773329187548A0189ED6503667890A199E5B@XMB-RCD-101.cisco.com> <3F4910A77924AF44876B1A096ECC92A7D411F1897C@MOPESMBX01.eu.thmulti.com> <FC492F1B-5B24-44C7-856D-AECBB9FCB3AD@employees.org>
In-Reply-To: <FC492F1B-5B24-44C7-856D-AECBB9FCB3AD@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_6CC912648D824FC6AE4E99B1A5BCC47Fnominumcom_"
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Mon, 12 Dec 2011 20:27:07 -0000

--_000_6CC912648D824FC6AE4E99B1A5BCC47Fnominumcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Dec 12, 2011, at 5:01 AM, Ole Troan wrote:
- a single interface of a DHCP client is bound to a single DHCP domain.
- in a DHCP domain all DHCP servers are operated by a single administrative=
 entity

is it then not a configuration error that multiple DHCP servers give a diff=
erent view of the world?

Your assumptions are essentially the assumptions we started out with, and t=
he conclusion you draw from them is correct, as far as it goes.   I think u=
sing that conclusion to resolve the question we are discussing is fine.   H=
owever, I think that it's also turned out that the assumptions are incorrec=
t, and we need to address that going forward.   I don't think we should try=
 to address it as part of this discussion, however.


--_000_6CC912648D824FC6AE4E99B1A5BCC47Fnominumcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <5EA7D70297AAF449AC230BE38B23D684@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 12, 2011, at 5:01 AM, Ole Troan wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">-
 a single interface of a DHCP client is bound to a single DHCP domain.<br>
- in a DHCP domain all DHCP servers are operated by a single administrative=
 entity<br>
<br>
is it then not a configuration error that multiple DHCP servers give a diff=
erent view of the world?</span></blockquote>
</div>
<br>
<div>Your assumptions are essentially the assumptions we started out with, =
and the conclusion you draw from them is correct, as far as it goes. &nbsp;=
 I think using that conclusion to resolve the question we are discussing is=
 fine. &nbsp; However, I think that it's also
 turned out that the assumptions are incorrect, and we need to address that=
 going forward. &nbsp; I don't think we should try to address it as part of=
 this discussion, however.</div>
<div><br>
</div>
</body>
</html>

--_000_6CC912648D824FC6AE4E99B1A5BCC47Fnominumcom_--

From Carl.Wuyts@technicolor.com  Tue Dec 13 00:40:35 2011
Return-Path: <Carl.Wuyts@technicolor.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 C231B21F86A4 for <dhcwg@ietfa.amsl.com>; Tue, 13 Dec 2011 00:40:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.77
X-Spam-Level: 
X-Spam-Status: No, score=-5.77 tagged_above=-999 required=5 tests=[AWL=0.229,  BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MuloHDURCD9A for <dhcwg@ietfa.amsl.com>; Tue, 13 Dec 2011 00:40:34 -0800 (PST)
Received: from na3sys009aog115.obsmtp.com (na3sys009aog115.obsmtp.com [74.125.149.238]) by ietfa.amsl.com (Postfix) with ESMTP id B5F7821F852E for <dhcwg@ietf.org>; Tue, 13 Dec 2011 00:40:31 -0800 (PST)
Received: from MOPESEDGE01.eu.thmulti.com ([129.35.174.203]) (using TLSv1) by na3sys009aob115.postini.com ([74.125.148.12]) with SMTP ID DSNKTucPca5vzBkVDQSIelVs5rGaMAUVreKB@postini.com; Tue, 13 Dec 2011 00:40:34 PST
Received: from MOPESMAILHC02.eu.thmulti.com (141.11.100.29) by mail3.technicolor.com (141.11.253.22) with Microsoft SMTP Server (TLS) id 8.3.192.1; Tue, 13 Dec 2011 09:35:51 +0100
Received: from MOPESMBX01.eu.thmulti.com ([169.254.155.121]) by MOPESMAILHC02.eu.thmulti.com ([141.11.100.29]) with mapi; Tue, 13 Dec 2011 09:35:43 +0100
From: Wuyts Carl <Carl.Wuyts@technicolor.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, Ole Troan <otroan@employees.org>, Ted Lemon <Ted.Lemon@nominum.com>
Date: Tue, 13 Dec 2011 09:35:40 +0100
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: AcyxrvDLFRNpP0jPR/yTrpdNLgYP9QDyptfAAI4JFbAAb+698A==
Message-ID: <867F4B6A1672E541A94676D556793ACD0CB445D3DC@MOPESMBX01.eu.thmulti.com>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com><66EBF10F-A971-48BD-968B-1202CBF94B49@employees.org> <867F4B6A1672E541A94676D556793ACD0CB445C90C@MOPESMBX01.eu.thmulti.com> <D9B5773329187548A0189ED6503667890A199E5B@XMB-RCD-101.cisco.com>
In-Reply-To: <D9B5773329187548A0189ED6503667890A199E5B@XMB-RCD-101.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Tue, 13 Dec 2011 08:40:35 -0000

Sorry, but fully disagree on a couple of things here.
1. The state machine is not very clear, maybe to some of us, but the fact t=
hat there's so much discussion today proves my point I'd say
2. As far as I know, I don't see the split (everything in separate requests=
) either present in this RFC
3. On one hand, you'd like to split, on the other there's the draft to avoi=
d 'storms' (max_sol_rt) is also being dragged to the discussion, sounds a b=
it contradictive
4. This RFC6204bis is due to be applied on ALL CPEs, not only very powerful=
 with huge amounts of memory and flash.  When you would start splitting up =
everything, you would have to keep track of each request individually, doub=
ling (tripling,...) up the amount of memory too.

Overall, I don't think that splitting up can introduce more simplicity anyw=
ay, sounds very unlikely.

Regs
Carl


-----Original Message-----
From: Bernie Volz (volz) [mailto:volz@cisco.com]=20
Sent: zondag 11 december 2011 4:07
To: Wuyts Carl; Ole Troan; Ted Lemon
Cc: dhc WG
Subject: RE: [dhcwg] Some high-priority errata for RFC3315/3396...

>Maybe I'm cutting some corners here, but I think the main thing missing
in the RFC3315 is a clear state machine.

While there is no state machine diagram, the state machine is very clear if=
 you do a separate requests for each IA_*. Keep-it-simple.

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of W=
uyts Carl
Sent: Thursday, December 08, 2011 2:38 AM
To: Ole Troan; Ted Lemon
Cc: dhc WG
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...

All,

I think solution 3, i.e. including ia_na in renew if not received, would be=
 ok for us.

Some additional remark/Q:
While TR181 was progressing on defining the DHCPv6 part some time ago, we'v=
e already given some feedback on the modelling, e.g. the model has been mad=
e as such that 1 DHCPv6 client can "connect" to several DHCPv6 servers at t=
he SAME time.  So, in order to get you options, you can potentially get the=
m from different DHCPv6 servers.  (so, not to check who can give you what o=
ptions, but really to fetch options from different servers at the same time=
)

Now I read the below discussion on what to do if no ia_na gets provided, on=
ly ia_pd.

Maybe I'm cutting some corners here, but I think the main thing missing in =
the RFC3315 is a clear state machine.  This opens up the gate for interpret=
ations.  I've asked our BBF representative back then to challenge the autho=
rs to provide us the procedure (i.e. state machine) to use when an option w=
ould have either different content, is no longer available at some server, =
...  I've seen nothing on it.

Today, I've bumped onto this discussion.  As mentioned already, solution 3,=
 including the ia_na in the renew if not received sounds reasonable to us, =
but I saw some other possibilities like continuing to send discovers for th=
e ia_na only.  I must say I'm quite surprised to see this kind of proposal =
??!!
The same applies here: clear state machine would help a lot in these matter=
s.

Regs
Carl





-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of O=
le Troan
Sent: zaterdag 3 december 2011 12:30
To: Ted Lemon
Cc: dhc WG
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...

Ted,

s/3361/3633/g

phrased another way:
do we think we can do better than treating each stateful DHCPv6 option (IA_=
NA, IA_TA, IA_PD) as separate protocol instances?
as in:
A DHCPv6 client MUST initiate a separate session for each IA_ option it wil=
l request. DHCPv6 message behaviour and initiation will have slight variati=
ons per option type. A DHCPv6 server that has more than one stateful option=
 to give to a client, MUST only include the requested IA_ option in any rep=
ly to the client.

cheers,
Ole

On Dec 3, 2011, at 4:18 , Ted Lemon wrote:

> There's been a bit of a discussion going on in the v6ops working group
about a problem in the DHCP protocol that has to do with the coexistence of=
 stateful address allocation and prefix delegation.
>=20
> The problem is that it's entirely possible that a PD requesting router
might also want an IP address to number its upstream interface, so it might=
 send a DHCP Solicit message containing both an IA_NA and an IA_PD.
Suppose the DHCP server is willing to do prefix delegation, but expects
the RR to do SLAAC for the upstream address.   In this case, it's going
to send an IA_PD containing one or more prefixes, but an IA_NA containing n=
o addresses.
>=20
> RFC3315 wasn't written with RFC3361 in mind, so it doesn't really talk
about what to do in this case.   It also doesn't address the problem of
what to do if an IA_TA appears in the solicit, but the server isn't
configured to offer temporary addresses.   This hasn't been much of an
issue since I don't know of any clients that actually request temporary add=
resses, but of course it is an issue for IA_PD.
>=20
> There exist two errata that address this issue: erratum 2471 and
erratum 2472.   These errata propose to have the status code appear
inside the IA_NA option rather than in the outer layer of the Advertise
message.   A similar erratum exists for RFC3361, proposing to put the
status code option in the IA_PD option instead of, similarly, in the outer =
layer of the packet.
>=20
> In addition, the following observation has been made:
>=20
>  The other unclear problem area is around how to deal with IA_PD and
IA_NA:
>    * Client requests both IA_NA and IA_PD in the same session, gets
only IA_PD.
>      - Does it fork off a separate session for IA_NA and continues
sending SOLICITs for only the IA_NA?
>      - Reset the DHCP client, and tries again?
>      - Keeps single session, and continues to ask for IA_NA on next
RENEW?
>=20
>      all 3 behaviors have been seen in the wild plus some additional
pathological cases.
>      in general dealing with multiple stateful options in DHCP is
underspecified.
>=20
> So the topic for discussion in the working group here is as follows:
>=20
> 1. Is what is proposed in the errata the right thing?   Should we in
fact have status codes inside of IA_* options instead of in the main packet=
?
>=20
> 2. If so, what is the full set of edits to RFC3315 and RFC3361 that
are required to do this?
> 2a. What do we do for clients that don't implement the errata?
>=20
> 3. If not, what should we do instead?
>=20
> 4. If the client gets an IA_NA and no IA_PD, or vice versa, which of
the three behaviors listed above should it follow?   Is it bad that
different clients do this differently?
>=20
> 5. What have I missed?
>=20
> Comments?   Criticisms?   Rotten tomatoes?
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

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

From rdroms.ietf@gmail.com  Tue Dec 13 09:38:54 2011
Return-Path: <rdroms.ietf@gmail.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 69C1421F8AC9 for <dhcwg@ietfa.amsl.com>; Tue, 13 Dec 2011 09:38:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.299
X-Spam-Level: 
X-Spam-Status: No, score=-103.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PWWjxVxYQRhF for <dhcwg@ietfa.amsl.com>; Tue, 13 Dec 2011 09:38:53 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6C6A121F8783 for <dhcwg@ietf.org>; Tue, 13 Dec 2011 09:38:53 -0800 (PST)
Received: by qadb15 with SMTP id b15so4031619qad.10 for <dhcwg@ietf.org>; Tue, 13 Dec 2011 09:38:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=7GYVoV3dUHQabLPO8se0Mpb7igqnkTlmIln9OqR3KdE=; b=iVgoMUAE7pHtVqhq+7a+fOJzDPL6GlccY5EKfRrqE95X2BPP2IHH2/GEA6YBUM7Iyj g1911+EHfbfQ5LFpqlCO4p80XqfCsYI+QK4/vDlta257jkPtlvlFuB+oAyzexQiLv2qj eABSAb7t4NCC8V5CraPS8um2F7sVaxfQiJAZg=
Received: by 10.224.17.209 with SMTP id t17mr4063640qaa.24.1323797932878; Tue, 13 Dec 2011 09:38:52 -0800 (PST)
Received: from [161.44.65.173] ([161.44.65.173]) by mx.google.com with ESMTPS id ed2sm44726277qab.15.2011.12.13.09.38.50 (version=SSLv3 cipher=OTHER); Tue, 13 Dec 2011 09:38:50 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <867F4B6A1672E541A94676D556793ACD0CB445C90C@MOPESMBX01.eu.thmulti.com>
Date: Tue, 13 Dec 2011 12:38:48 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <A4856B30-0DEF-4366-95CC-2D94F553EFBD@gmail.com>
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com> <66EBF10F-A971-48BD-968B-1202CBF94B49@employees.org> <867F4B6A1672E541A94676D556793ACD0CB445C90C@MOPESMBX01.eu.thmulti.com>
To: dhc WG <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
Cc: Ralph Droms <rdroms.ietf@gmail.com>, Lemon Ted <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Tue, 13 Dec 2011 17:38:54 -0000

On Dec 8, 2011, at 2:38 AM 12/8/11, Wuyts Carl wrote:

> All,
>=20
> I think solution 3, i.e. including ia_na in renew if not received, =
would be ok for us.
>=20
> Some additional remark/Q:
> While TR181 was progressing on defining the DHCPv6 part some time ago, =
we've already given some feedback on the modelling, e.g. the model has =
been made as such that 1 DHCPv6 client can "connect" to several DHCPv6 =
servers at the SAME time.  So, in order to get you options, you can =
potentially get them from different DHCPv6 servers.  (so, not to check =
who can give you what options, but really to fetch options from =
different servers at the same time)
>=20
> Now I read the below discussion on what to do if no ia_na gets =
provided, only ia_pd.
>=20
> Maybe I'm cutting some corners here, but I think the main thing =
missing in the RFC3315 is a clear state machine.  This opens up the gate =
for interpretations.  I've asked our BBF representative back then to =
challenge the authors to provide us the procedure (i.e. state machine) =
to use when an option would have either different content, is no longer =
available at some server, ...  I've seen nothing on it.

As a bit of history, the WG made an explicit decision not to include a =
description of a state machine in RFC 3315, because the state machine in =
RFC 2131 (DHCPv4) was:

* observed to have had too much influence on implementors,
* necessarily incomplete, and
* not accurate relative to the formal protocol description in the text =
of RFC 2131.

So, can we describe the desired client behavior in the situation under =
discussion?  Perhaps something like (note that I'm writing this up =
pretty much on the fly without any in-depth analysis):

* if an IA_* request is granted, accept and manage (Renew, etc.) the =
assigned addresses as described in RFC 3315
* if an IA_* request is denied with NoAddrsAvail, continue to retry the =
request no more frequently than allowed by the retry backoff rules; if =
the denied request includes a SOL_MAX_RT option, use that new value for =
the backoff rules
* a client may choose to optimize by combining IA_* requests in a single =
message, as long as the rules about frequency of requests are adhered to

This set of rules would allow independent instances of a DHCP client for =
each IA_*, or would allow a single client to combine the management of =
several IA_* into a single series of messages; e.g., include an IA_* =
request that was previously denied in a subsequent Renew message.  The =
use of the SOL_MAX_RT option would allow control of the volume of DHCPv6 =
traffic.

One question would be the effect on the server - is handling the various =
IA_* requests sufficiently orthogonal that the various requests from =
these rules would not represent an undue burden on the server?

Bringing this back around to the SOL_MAX_RT option draft, seems like the =
SOL_MAX_RT option should be scoped to the individual RAs.

- Ralph

> Today, I've bumped onto this discussion.  As mentioned already, =
solution 3, including the ia_na in the renew if not received sounds =
reasonable to us, but I saw some other possibilities like continuing to =
send discovers for the ia_na only.  I must say I'm quite surprised to =
see this kind of proposal ??!!
> The same applies here: clear state machine would help a lot in these =
matters.
>=20
> Regs
> Carl
>=20
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf =
Of Ole Troan
> Sent: zaterdag 3 december 2011 12:30
> To: Ted Lemon
> Cc: dhc WG
> Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
>=20
> Ted,
>=20
> s/3361/3633/g
>=20
> phrased another way:
> do we think we can do better than treating each stateful DHCPv6 option =
(IA_NA, IA_TA, IA_PD) as separate protocol instances?
> as in:
> A DHCPv6 client MUST initiate a separate session for each IA_ option =
it will request. DHCPv6 message behaviour and initiation will have =
slight variations per option type. A DHCPv6 server that has more than =
one stateful option to give to a client, MUST only include the requested =
IA_ option in any reply to the client.
>=20
> cheers,
> Ole
>=20
> On Dec 3, 2011, at 4:18 , Ted Lemon wrote:
>=20
>> There's been a bit of a discussion going on in the v6ops working =
group about a problem in the DHCP protocol that has to do with the =
coexistence of stateful address allocation and prefix delegation.
>>=20
>> The problem is that it's entirely possible that a PD requesting =
router might also want an IP address to number its upstream interface, =
so it might send a DHCP Solicit message containing both an IA_NA and an =
IA_PD.    Suppose the DHCP server is willing to do prefix delegation, =
but expects the RR to do SLAAC for the upstream address.   In this case, =
it's going to send an IA_PD containing one or more prefixes, but an =
IA_NA containing no addresses.
>>=20
>> RFC3315 wasn't written with RFC3361 in mind, so it doesn't really =
talk about what to do in this case.   It also doesn't address the =
problem of what to do if an IA_TA appears in the solicit, but the server =
isn't configured to offer temporary addresses.   This hasn't been much =
of an issue since I don't know of any clients that actually request =
temporary addresses, but of course it is an issue for IA_PD.
>>=20
>> There exist two errata that address this issue: erratum 2471 and =
erratum 2472.   These errata propose to have the status code appear =
inside the IA_NA option rather than in the outer layer of the Advertise =
message.   A similar erratum exists for RFC3361, proposing to put the =
status code option in the IA_PD option instead of, similarly, in the =
outer layer of the packet.
>>=20
>> In addition, the following observation has been made:
>>=20
>> The other unclear problem area is around how to deal with IA_PD and =
IA_NA:
>>   * Client requests both IA_NA and IA_PD in the same session, gets =
only IA_PD.
>>     - Does it fork off a separate session for IA_NA and continues =
sending SOLICITs for only the IA_NA?
>>     - Reset the DHCP client, and tries again?
>>     - Keeps single session, and continues to ask for IA_NA on next =
RENEW?
>>=20
>>     all 3 behaviors have been seen in the wild plus some additional =
pathological cases.
>>     in general dealing with multiple stateful options in DHCP is =
underspecified.
>>=20
>> So the topic for discussion in the working group here is as follows:
>>=20
>> 1. Is what is proposed in the errata the right thing?   Should we in =
fact have status codes inside of IA_* options instead of in the main =
packet?
>>=20
>> 2. If so, what is the full set of edits to RFC3315 and RFC3361 that =
are required to do this?
>> 2a. What do we do for clients that don't implement the errata?
>>=20
>> 3. If not, what should we do instead?
>>=20
>> 4. If the client gets an IA_NA and no IA_PD, or vice versa, which of =
the three behaviors listed above should it follow?   Is it bad that =
different clients do this differently?
>>=20
>> 5. What have I missed?
>>=20
>> Comments?   Criticisms?   Rotten tomatoes?
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From shemant@cisco.com  Tue Dec 13 09:40:47 2011
Return-Path: <shemant@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 B312721F8ACE for <dhcwg@ietfa.amsl.com>; Tue, 13 Dec 2011 09:40:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.521
X-Spam-Level: 
X-Spam-Status: No, score=-6.521 tagged_above=-999 required=5 tests=[AWL=0.078,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ND2+UZLd1cp6 for <dhcwg@ietfa.amsl.com>; Tue, 13 Dec 2011 09:40:47 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 1535121F8783 for <dhcwg@ietf.org>; Tue, 13 Dec 2011 09:40:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=2025; q=dns/txt; s=iport; t=1323798047; x=1325007647; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=EPouVs8CNw+cXkeRXRDQaCRazzOQQWAPwLGsDCHdr9I=; b=GaAp7yfPwoUYhojYEfj01o9i+Gt/mLiK0lmIyiQwvPcgtakt9rjRHPst oxCJs/+vvewIsm4lqhiCRrVc3ytm3plBV41itOwKdyAfXFCexNfe5406N iol72clZXIA7lBGTAxPVDQzS7ZHy1U9CcMPhAvyURFSFVgodPB1rng5tO E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArYAAE6N506tJXG9/2dsb2JhbABDmlWQUIEFgXIBAQEEEgEdCj8MBAIBCBEEAQELBhcBBgFFCQgBAQQBEgganzcBnieLAGMEiDCfCQ
X-IronPort-AV: E=Sophos;i="4.71,347,1320624000"; d="scan'208";a="43618409"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-5.cisco.com with ESMTP; 13 Dec 2011 17:40:46 +0000
Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core2-2.cisco.com (8.14.3/8.14.3) with ESMTP id pBDHekEc017365;  Tue, 13 Dec 2011 17:40:46 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 13 Dec 2011 11:40:46 -0600
X-Mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 13 Dec 2011 11:40:45 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C3038E52D2@XMB-RCD-109.cisco.com>
In-Reply-To: <867F4B6A1672E541A94676D556793ACD0CB445D3DC@MOPESMBX01.eu.thmulti.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Some high-priority errata for RFC3315/3396...
Thread-Index: AcyxrvDLFRNpP0jPR/yTrpdNLgYP9QDyptfAAI4JFbAAb+698AAS3jTQ
References: <406706A9-7430-4EF1-86BB-CD3BF3FC05B5@nominum.com><66EBF10F-A971-48BD-968B-1202CBF94B49@employees.org><867F4B6A1672E541A94676D556793ACD0CB445C90C@MOPESMBX01.eu.thmulti.com><D9B5773329187548A0189ED6503667890A199E5B@XMB-RCD-101.cisco.com> <867F4B6A1672E541A94676D556793ACD0CB445D3DC@MOPESMBX01.eu.thmulti.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Wuyts Carl" <Carl.Wuyts@technicolor.com>, "Bernie Volz (volz)" <volz@cisco.com>, "Ole Troan" <otroan@employees.org>, "Ted Lemon" <Ted.Lemon@nominum.com>
X-OriginalArrivalTime: 13 Dec 2011 17:40:46.0696 (UTC) FILETIME=[58855680:01CCB9BE]
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...
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: Tue, 13 Dec 2011 17:40:47 -0000

Seeing replies from Carl and Hans, even the DHCPv6 client vendors do not
like splitting each option processing in a new process.  I as a DHCPv6
relay agent vendor already said the SP DHCPv6 relay agent such as a CMTS
will have to process 100K SOLICITs vs. 200K SOLICITs if the DHCPv6
clients issue one SOLICIT for both the IA_NA and the IA_PD.  It would be
good that the SP maintain one DHCPv6 server to allocate both the IA_NA
and the IA_PD.   Then if a client asked for both options but only got
one, we have a SP provisioning system configuration error to look into.
If we can avoid separate processes to ask for each option, that would be
my preference too - subject to such a restriction, now let's see what we
have to change in the client and server behavior.=20

I appreciate the time Ted and Bernie spend replying over a weekend.

Thanks,

Hemant

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Wuyts Carl
Sent: Tuesday, December 13, 2011 3:36 AM
To: Bernie Volz (volz); Ole Troan; Ted Lemon
Cc: dhc WG
Subject: Re: [dhcwg] Some high-priority errata for RFC3315/3396...

Sorry, but fully disagree on a couple of things here.
1. The state machine is not very clear, maybe to some of us, but the
fact that there's so much discussion today proves my point I'd say
2. As far as I know, I don't see the split (everything in separate
requests) either present in this RFC
3. On one hand, you'd like to split, on the other there's the draft to
avoid 'storms' (max_sol_rt) is also being dragged to the discussion,
sounds a bit contradictive
4. This RFC6204bis is due to be applied on ALL CPEs, not only very
powerful with huge amounts of memory and flash.  When you would start
splitting up everything, you would have to keep track of each request
individually, doubling (tripling,...) up the amount of memory too.

Overall, I don't think that splitting up can introduce more simplicity
anyway, sounds very unlikely.

Regs
Carl



From rdroms.ietf@gmail.com  Thu Dec 15 06:56:21 2011
Return-Path: <rdroms.ietf@gmail.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 127A121F8AD6 for <dhcwg@ietfa.amsl.com>; Thu, 15 Dec 2011 06:56:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.449
X-Spam-Level: 
X-Spam-Status: No, score=-103.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IY9ED+k4frr8 for <dhcwg@ietfa.amsl.com>; Thu, 15 Dec 2011 06:56:20 -0800 (PST)
Received: from mail-qw0-f51.google.com (mail-qw0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4540321F8AD2 for <dhcwg@ietf.org>; Thu, 15 Dec 2011 06:56:20 -0800 (PST)
Received: by qadz3 with SMTP id z3so1374846qad.10 for <dhcwg@ietf.org>; Thu, 15 Dec 2011 06:56:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=mPRrLCOQ/AlValPVDeoBSFbVtpRocBbr4lFe/fK61BM=; b=kdFy7Y9D9RxBt+kMtRcqNWhG46aPTWnbed78IO0krzFHwLZu9xkhS4CagdD5gj1aMz n8ZZ6Xw+HfFocHEwelczPWmKHIh5vT56HQUBSxBaIWnGnNpDX6NDtDgLX4+BCle3iEcq vd8G/FF/HG/I8eVt50+/N8MYWY/HVNDEv8KR4=
Received: by 10.224.86.200 with SMTP id t8mr913080qal.29.1323960979801; Thu, 15 Dec 2011 06:56:19 -0800 (PST)
Received: from rtp-rdroms-8912.cisco.com (rtp-isp-nat1.cisco.com. [64.102.254.33]) by mx.google.com with ESMTPS id h9sm13254514qac.13.2011.12.15.06.56.17 (version=SSLv3 cipher=OTHER); Thu, 15 Dec 2011 06:56:18 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <D9B5773329187548A0189ED6503667890A199E5D@XMB-RCD-101.cisco.com>
Date: Thu, 15 Dec 2011 09:56:16 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <64188822-4E63-449C-B048-A4D6340252BD@gmail.com>
References: <EBA5E737-027B-40F2-AE1D-A48A2051F441@nominum.com> <D9B5773329187548A0189ED6503667890A199E5D@XMB-RCD-101.cisco.com>
To: dhc WG <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-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, 15 Dec 2011 14:56:21 -0000

I've published rev -01 taking into account comments from Bernie and =
others.

The changes:

* simplifies the discussion of "why is this option is needed"
* applies the new SOL_MAX_RT value to any Solicits (leaving aside the =
question of how a client will deal with an Advertise that satisfies, =
e.g., an IA_NA request but not an IA_PD request)
* requires client to request the option in an ORO
* clarifies that the server returns the option in the main body of a =
response

I think this option can be moved forward without tying it to the =
resolution of partial IA_* assignments.  This option simplify modifies =
the default value of SOL_MAX_RT.  Any future modifications to the =
definition and use of SOL_MAX_RT would be independent of this option - =
i.e., would be specified in terms of SOL_MAX_RT or some new MAX_RT =
defaults - so this new option would apply (or not) regardless.

Pragmatically, there is interest in the SP and vendor community to move =
this option forward so the soon-to-be deployed IPv6-capable CE routers =
can mitigate issues with certain deployment scenarios.

- Ralph

On Dec 10, 2011, at 10:16 PM 12/10/11, Bernie Volz (volz) wrote:

> I think this draft needs to be updated a bit. It never mentions =
ANYTHING
> about IA_PD.
>=20
> I think whenever a server returns NoAddrsAvail or NoPrefixAvail =
status,
> it should be able to provide this option in the response to indicate =
to
> the client a new SOL_MAX_RT value for the IA type(s) requested by the
> client.
>=20
> The draft fails to solve the situation where a CPE routers that =
request
> both an IA_NA and IA_PD (whether in one or two requests) does so
> frequently. The current draft handles the case where addresses are not
> being provided, but fails to handle the case where IA_PDs are also not
> being provided.
>=20
> - Bernie
>=20
> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
> Of Ted Lemon
> Sent: Friday, December 09, 2011 12:58 PM
> To: dhcwg@ietf.org WG
> Subject: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-00
>=20
> Ralph's put in an individual submission draft with Jari as the
> sponsoring AD.   The draft attempts to solve a problem ISPs are having
> where in a massive IPv6 network that isn't entirely deployed, devices
> are requesting configuration too often.
>=20
> Ralph's draft proposes a new option whereby a DHCP server can indicate
> in response to a solicit that the client should use a larger value for
> SOL_MAX_RT.   This means that clients will continue their exponential
> backoff to whatever limit is stated in the offer, and reduces the
> overall traffic on the DHCP servers at the core of the network.
>=20
> The draft is an individual submission, so it doesn't technically have =
to
> pass dhcwg last call-just IETF last call.   However, since the dhcwg =
is
> where DHCP protocol extensions are done, I'm doing a last call here to
> encourage people to review it-it would really help if some wg
> participants would review it and think about the implications.
>=20
> If we don't hear anything by December 23, Jari will continue the =
process
> of advancing the draft.   If you do read the draft, please comment =
here
> as to whether you support it, and please offer any suggestions you may
> have.
>=20
> Thanks!
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From mellon@fugue.com  Thu Dec 15 11:17:16 2011
Return-Path: <mellon@fugue.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 B781321F8548 for <dhcwg@ietfa.amsl.com>; Thu, 15 Dec 2011 11:17:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OU7WlP+7gmYo for <dhcwg@ietfa.amsl.com>; Thu, 15 Dec 2011 11:17:15 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 6146321F85EF for <dhcwg@ietf.org>; Thu, 15 Dec 2011 11:17:15 -0800 (PST)
Received: from [IPv6:2001:470:1f07:1486:a0ed:afc5:e47e:9fda] (unknown [IPv6:2001:470:1f07:1486:a0ed:afc5:e47e:9fda]) by toccata.fugue.com (Postfix) with ESMTPSA id 532BB2381FA8 for <dhcwg@ietf.org>; Thu, 15 Dec 2011 14:17:12 -0500 (EST)
From: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Thu, 15 Dec 2011 14:17:10 -0500
Message-Id: <27E2BF10-7AEE-4B64-B04A-87708CB02C00@fugue.com>
To: dhc WG <dhcwg@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1251.1)
X-Mailer: Apple Mail (2.1251.1)
Subject: [dhcwg] WGLC: draft-ietf-dhc-relay-id-suboption-09.txt
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, 15 Dec 2011 19:17:16 -0000

This is a pretty brief document that defines a relay agent identifier =
that can be sent in option 82.   It's been through WGLC and sent to the =
IESG once, but the author was unable to respond to IESG comments, so it =
got dropped.   Bharat Joshi took it over back in June and has updated it =
and requested comment.

We didn't hear any comment on the mailing list.   I've read the draft =
and it looks reasonable, but I'd like to see more review, so I'm doing =
this last call in hopes that someone will take the time to look at the =
document.   Because of the Christmas and New Years' holidays that some =
participants will be celebrating, we won't call consensus on this until =
January 5.

If you think this document is useful and should be published, please say =
so.   If you don't think it should be published, please say so.   If you =
haven't read the document, please don't express an opinion about it.

Thanks!


From internet-drafts@ietf.org  Thu Dec 15 19:08:13 2011
Return-Path: <internet-drafts@ietf.org>
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 6205B1F0C6C; Thu, 15 Dec 2011 19:08:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ghoV21ioeTa; Thu, 15 Dec 2011 19:08:13 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02D9821F8514; Thu, 15 Dec 2011 19:08:13 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111216030813.20761.36524.idtracker@ietfa.amsl.com>
Date: Thu, 15 Dec 2011 19:08:13 -0800
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-reconfigure-rebind-09.txt
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: Fri, 16 Dec 2011 03:08:13 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Dynamic Host Configuration Working Gr=
oup of the IETF.

	Title           : Rebind Capability in DHCPv6 Reconfigure Messages
	Author(s)       : D. R. Evans
                          Ralph Droms
                          Sheng Jiang
	Filename        : draft-ietf-dhc-dhcpv6-reconfigure-rebind-09.txt
	Pages           : 8
	Date            : 2011-12-15

   This document updates RFC 3315 to allow the Rebind message type to
   appear in the Reconfigure Message option of a Reconfigure message,
   which extends the Reconfigure message to allow a DHCPv6 server to
   cause a DHCPv6 client to send a Rebind message.  The document also
   clarifies how a DHCPv6 client responds to a received Reconfigure
   message.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-reconfigure-rebin=
d-09.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-reconfigure-rebind=
-09.txt


From volz@cisco.com  Thu Dec 15 19:25:36 2011
Return-Path: <volz@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 46E3B21F889A for <dhcwg@ietfa.amsl.com>; Thu, 15 Dec 2011 19:25:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.556
X-Spam-Level: 
X-Spam-Status: No, score=-6.556 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NZJ5PFEM9AWA for <dhcwg@ietfa.amsl.com>; Thu, 15 Dec 2011 19:25:35 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id D640B21F8888 for <dhcwg@ietf.org>; Thu, 15 Dec 2011 19:25:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8351; q=dns/txt; s=iport; t=1324005934; x=1325215534; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=lWDjb0AAmU/94qlFMPPM3lr5Y8w2m+/NG3WKdpVKZTI=; b=RwuTNKKrJvA4GJhqU7FIk1YBaqayou3VWqSYlL6OB+CiV/n+VL9Yqrro SA5tP9RqUmNTSEssxUTn554lpnqG1XujLOjbS+5PhSiGg6U12VHHFD4Wv rlb6JQ3aGhGKRH/veXiolSCp4v+KHqUA+C5SzKDR3nt0OgWdCLlJT7Npo A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhABABEppk6tJXHB/2dsb2JhbACQRY4WeIhwi2WSNIMngnIEhlCNeYpc
X-IronPort-AV: E=Sophos;i="4.71,360,1320624000"; d="scan'208";a="41947213"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-9.cisco.com with ESMTP; 16 Dec 2011 03:25:34 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core2-6.cisco.com (8.14.3/8.14.3) with ESMTP id pBG3PYDF016292;  Fri, 16 Dec 2011 03:25:34 GMT
Received: from xmb-rcd-101.cisco.com ([72.163.62.143]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 15 Dec 2011 21:25:34 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 15 Dec 2011 21:25:32 -0600
Message-ID: <D9B5773329187548A0189ED6503667890A2DA469@XMB-RCD-101.cisco.com>
In-Reply-To: <64188822-4E63-449C-B048-A4D6340252BD@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-00
Thread-Index: Acy7Obd8gUoaC5lwReif1v1HvRRFIwAZE5zg
References: <EBA5E737-027B-40F2-AE1D-A48A2051F441@nominum.com><D9B5773329187548A0189ED6503667890A199E5D@XMB-RCD-101.cisco.com> <64188822-4E63-449C-B048-A4D6340252BD@gmail.com>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Ralph Droms" <rdroms.ietf@gmail.com>, "dhc WG" <dhcwg@ietf.org>
X-OriginalArrivalTime: 16 Dec 2011 03:25:34.0339 (UTC) FILETIME=[5F364530:01CCBBA2]
Subject: Re: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-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: Fri, 16 Dec 2011 03:25:36 -0000

Ralph:

The following text in section 3:

   If a DHCPv6 client receives an IA_NA or IA_TA option containing a
   SOL_MAX_RT option, the client MUST set its internal SOL_MAX_RT
   parameter to the value contained in the SOL_MAX_RT option.  As a
   result of receiving this option, the DHCPv6 client MUST NOT send any
   Solicit messages more frequently than allowed by the retransmission
   mechanism defined in sections 17.1.2 and 14 of RFC 315 [RFC3315].

Fails to mention IA_PD (you probably forgot to update that sentence).

And, I thought we were also considering using this when a client is not
given any addresses AND/OR delegated any prefixes? But, perhaps you
don't think that is necessary? If it is necessary (do read further down
to the end as there are some other potential issues to consider with
that), this draft would need to update several sections of RFC 3315? In
particular:

17.1.3. Receipt of Advertise Messages

   The client MUST ignore any Advertise message that includes a Status
   Code option containing the value NoAddrsAvail, with the exception
   that the client MAY display the associated status message to the
   user.

...

17.2.2. Creation and Transmission of Advertise Messages

...

   If the server will not assign any addresses to any IAs in a
   subsequent Request from the client, the server MUST send an Advertise
   message to the client that includes only a Status Code option with
   code NoAddrsAvail and a status message for the user, a Server
   Identifier option with the server's DUID, and a Client Identifier
   option with the client's DUID.


17.1.3 has a MUST ignore. If the client included the SOL_MAX_RT option
in the ORO, then it should not ignore but check for that option?

17.2.2 says MUST include only ... again, if client requested SOL_MAX_RT
option in the ORO, server SHOULD include it.

So, your section 2. "Update to RFC 3315" would need to say something
about that these sections are impacted.

---

I also wonder whether to reduce the impact of the Security
Considerations section we should impose some limit to the SOL_MAX_RT
value that can be communicated by a Server. I was thinking that
something like a day (86,400 seconds) would be a reasonable limit. But,
not sure it really helps that much as that is rather long to be without
[IPv6] service. And, if you had 10 Million devices on a network (and
assuming they all were at that SOL_MAX_RT value), that results in 116
Solicits/second which is probably still a fairly high rate. If you
limited it to a week, that rate drops to 17 packets/second.

---

Some nits the RFC editor would likely catch ....

3.  SOL_MAX_RT option
...

  mechanism defined in sections 17.1.2 and 14 of RFC 315 [RFC3315].
                                                     ^^^

4.  Security Considerations

   This document introduces one security considerations beyond those
                                                      ^?
   described in RFC 3315 [RFC3315].

6.  Normative References

The references should include RFC 3633 as you now mention IA_PD (even
before my issue above).

Why do you include the following as it is never referenced?

   [RFC2461]  Narten, T., Nordmark, E., and W. Simpson, "Neighbor
              Discovery for IP Version 6 (IPv6)", RFC 2461,
              December 1998.

Perhaps it was explicitly referenced in the -00 draft because of the M/O
bits?

---

A few other nits:

In section 1, it says "high volume of aggregated traffic at a DHCPv6
server" ... would also cause high volumes of traffic if there is no
DHCPv6 server. Might also revise section 2 (significantly reducing the
aggregated traffic at the DHCPv6 server). I think the "at the DHCPv6
server" can be dropped?

Especially if we change the draft to allow the SOL_MAX_RT option to be
communicated when no addresses (and/or prefixes) are provided, it would
be worth (in section 3) to indicate that a client should use the server
provided SOL_MAX_RT value until some 'hard' reboot (not just a soft
reset) -- some devices may soft reset every so often when waiting to
come online which would defeat the utility of the server provided
SOL_MAX_RT. Also, that an updated SOL_MAX_RT value should not cause the
client to in any way reset its Solicit timer (we don't want it to reset
the current timing algorithm (other than to cap the timeout) if
retrying).

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Ralph Droms
Sent: Thursday, December 15, 2011 9:56 AM
To: dhc WG
Subject: Re: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-00

I've published rev -01 taking into account comments from Bernie and
others.

The changes:

* simplifies the discussion of "why is this option is needed"
* applies the new SOL_MAX_RT value to any Solicits (leaving aside the
question of how a client will deal with an Advertise that satisfies,
e.g., an IA_NA request but not an IA_PD request)
* requires client to request the option in an ORO
* clarifies that the server returns the option in the main body of a
response

I think this option can be moved forward without tying it to the
resolution of partial IA_* assignments.  This option simplify modifies
the default value of SOL_MAX_RT.  Any future modifications to the
definition and use of SOL_MAX_RT would be independent of this option -
i.e., would be specified in terms of SOL_MAX_RT or some new MAX_RT
defaults - so this new option would apply (or not) regardless.

Pragmatically, there is interest in the SP and vendor community to move
this option forward so the soon-to-be deployed IPv6-capable CE routers
can mitigate issues with certain deployment scenarios.

- Ralph

On Dec 10, 2011, at 10:16 PM 12/10/11, Bernie Volz (volz) wrote:

> I think this draft needs to be updated a bit. It never mentions
ANYTHING
> about IA_PD.
>=20
> I think whenever a server returns NoAddrsAvail or NoPrefixAvail
status,
> it should be able to provide this option in the response to indicate
to
> the client a new SOL_MAX_RT value for the IA type(s) requested by the
> client.
>=20
> The draft fails to solve the situation where a CPE routers that
request
> both an IA_NA and IA_PD (whether in one or two requests) does so
> frequently. The current draft handles the case where addresses are not
> being provided, but fails to handle the case where IA_PDs are also not
> being provided.
>=20
> - Bernie
>=20
> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
> Of Ted Lemon
> Sent: Friday, December 09, 2011 12:58 PM
> To: dhcwg@ietf.org WG
> Subject: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-00
>=20
> Ralph's put in an individual submission draft with Jari as the
> sponsoring AD.   The draft attempts to solve a problem ISPs are having
> where in a massive IPv6 network that isn't entirely deployed, devices
> are requesting configuration too often.
>=20
> Ralph's draft proposes a new option whereby a DHCP server can indicate
> in response to a solicit that the client should use a larger value for
> SOL_MAX_RT.   This means that clients will continue their exponential
> backoff to whatever limit is stated in the offer, and reduces the
> overall traffic on the DHCP servers at the core of the network.
>=20
> The draft is an individual submission, so it doesn't technically have
to
> pass dhcwg last call-just IETF last call.   However, since the dhcwg
is
> where DHCP protocol extensions are done, I'm doing a last call here to
> encourage people to review it-it would really help if some wg
> participants would review it and think about the implications.
>=20
> If we don't hear anything by December 23, Jari will continue the
process
> of advancing the draft.   If you do read the draft, please comment
here
> as to whether you support it, and please offer any suggestions you may
> have.
>=20
> Thanks!
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

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

From Ted.Lemon@nominum.com  Thu Dec 15 21:53:29 2011
Return-Path: <Ted.Lemon@nominum.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 9DAC121F850E for <dhcwg@ietfa.amsl.com>; Thu, 15 Dec 2011 21:53:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.548
X-Spam-Level: 
X-Spam-Status: No, score=-106.548 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GRL-Z7XKDK-c for <dhcwg@ietfa.amsl.com>; Thu, 15 Dec 2011 21:53:28 -0800 (PST)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id 827C821F84DF for <dhcwg@ietf.org>; Thu, 15 Dec 2011 21:53:27 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKTurc1LMHKfKYAMJhDH8QWLCpTFHSn+CR@postini.com; Thu, 15 Dec 2011 21:53:27 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 5BF661B82B5 for <dhcwg@ietf.org>; Thu, 15 Dec 2011 21:53:24 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id C5E01190052; Thu, 15 Dec 2011 21:53:21 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-02.WIN.NOMINUM.COM ([64.89.228.134]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0339.001; Thu, 15 Dec 2011 21:53:22 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Thread-Topic: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-00
Thread-Index: AQHMtpwjAljFLrkpaEuFQR2ym6HpQ5XV+CLAgAeUJQCAAHHWAA==
Date: Fri, 16 Dec 2011 05:53:21 +0000
Message-ID: <741CB57E-F60F-49A4-8F2C-A888F45E1BD9@nominum.com>
References: <EBA5E737-027B-40F2-AE1D-A48A2051F441@nominum.com> <D9B5773329187548A0189ED6503667890A199E5D@XMB-RCD-101.cisco.com> <64188822-4E63-449C-B048-A4D6340252BD@gmail.com>
In-Reply-To: <64188822-4E63-449C-B048-A4D6340252BD@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_741CB57EF60F49A48F2CA888F45E1BD9nominumcom_"
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-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: Fri, 16 Dec 2011 05:53:29 -0000

--_000_741CB57EF60F49A48F2CA888F45E1BD9nominumcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Dec 15, 2011, at 9:56 AM, Ralph Droms wrote:
Pragmatically, there is interest in the SP and vendor community to move thi=
s option forward so the soon-to-be deployed IPv6-capable CE routers can mit=
igate issues with certain deployment scenarios.

Ralph, are you arguing that we should pass this on sooner than the date I o=
riginally proposed?   Given that we've had some review and that we generall=
y don't get late review, and that this particular review is informal, I'm n=
ot entirely opposed to that, but please let me know if that's what you inte=
nded.


--_000_741CB57EF60F49A48F2CA888F45E1BD9nominumcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <F94087084C2BA3438E17C0D7C411C436@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 15, 2011, at 9:56 AM, Ralph Droms wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">Pragmatically,
 there is interest in the SP and vendor community to move this option forwa=
rd so the soon-to-be deployed IPv6-capable CE routers can mitigate issues w=
ith certain deployment scenarios.</span></blockquote>
</div>
<br>
<div>Ralph, are you arguing that we should pass this on sooner than the dat=
e I originally proposed? &nbsp; Given that we've had some review and that w=
e generally don't get late review, and that this particular review is infor=
mal, I'm not entirely opposed to that,
 but please let me know if that's what you intended.</div>
<div><br>
</div>
</body>
</html>

--_000_741CB57EF60F49A48F2CA888F45E1BD9nominumcom_--

From bharat_joshi@infosys.com  Fri Dec 16 03:15:23 2011
Return-Path: <bharat_joshi@infosys.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 9ED1F21F8B10 for <dhcwg@ietfa.amsl.com>; Fri, 16 Dec 2011 03:15:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ZS588eICvZN for <dhcwg@ietfa.amsl.com>; Fri, 16 Dec 2011 03:15:22 -0800 (PST)
Received: from kecgate02.infosys.com (kecgate02.infosys.com [122.98.14.32]) by ietfa.amsl.com (Postfix) with ESMTP id 686CE21F8B0B for <dhcwg@ietf.org>; Fri, 16 Dec 2011 03:15:21 -0800 (PST)
X-TM-IMSS-Message-ID: <1ff7542100367249@infosys.com>
Received: from blrkechub03.ad.infosys.com ([10.66.236.43]) by infosys.com ([122.98.14.32]) with ESMTP (TREND IMSS SMTP Service 7.1) id 1ff7542100367249 ; Fri, 16 Dec 2011 16:43:48 +0530
Received: from BLRKECMBX02.ad.infosys.com ([10.66.236.22]) by blrkechub03.ad.infosys.com ([10.66.236.43]) with mapi; Fri, 16 Dec 2011 16:45:17 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Date: Fri, 16 Dec 2011 16:44:02 +0530
Thread-Topic: [dhcwg] WGLC: draft-ietf-dhc-relay-id-suboption-09.txt
Thread-Index: Acy7Xi/tOLuD9DEHRj+pvsaw+/kD4AAhaG7x
Message-ID: <31D55C4D55BEED48A4459EB64567589A118933FC9A@BLRKECMBX02.ad.infosys.com>
References: <27E2BF10-7AEE-4B64-B04A-87708CB02C00@fugue.com>
In-Reply-To: <27E2BF10-7AEE-4B64-B04A-87708CB02C00@fugue.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] WGLC: draft-ietf-dhc-relay-id-suboption-09.txt
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: Fri, 16 Dec 2011 11:15:23 -0000

I support this draft (I am also one of the author) if it counts.

Regards,
Bharat
________________________________________
From: dhcwg-bounces@ietf.org [dhcwg-bounces@ietf.org] On Behalf Of Ted Le=
mon [mellon@fugue.com]
Sent: Friday, December 16, 2011 12:47 AM
To: dhc WG
Subject: [dhcwg] WGLC: draft-ietf-dhc-relay-id-suboption-09.txt

This is a pretty brief document that defines a relay agent identifier tha=
t can be sent in option 82.   It's been through WGLC and sent to the IESG=
 once, but the author was unable to respond to IESG comments, so it got d=
ropped.   Bharat Joshi took it over back in June and has updated it and r=
equested comment.

We didn't hear any comment on the mailing list.   I've read the draft and=
 it looks reasonable, but I'd like to see more review, so I'm doing this =
last call in hopes that someone will take the time to look at the documen=
t.   Because of the Christmas and New Years' holidays that some participa=
nts will be celebrating, we won't call consensus on this until January 5.

If you think this document is useful and should be published, please say =
so.   If you don't think it should be published, please say so.   If you =
haven't read the document, please don't express an opinion about it.

Thanks!

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

**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended sol=
ely 
for the use of the addressee(s). If you are not the intended recipient, p=
lease 
notify the sender by e-mail and delete the original message. Further, you=
 are not 
to copy, disclose, or distribute this e-mail or its contents to any other=
 person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys h=
as taken 
every reasonable precaution to minimize this risk, but is not liable for =
any damage 
you may sustain as a result of any virus in this e-mail. You should carry=
 out your 
own virus checks before opening the e-mail or attachment. Infosys reserve=
s the 
right to monitor and review the content of all messages sent to or from t=
his e-mail 
address. Messages sent to or from this e-mail address may be stored on th=
e 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

From rdroms.ietf@gmail.com  Fri Dec 16 08:59:48 2011
Return-Path: <rdroms.ietf@gmail.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 6951821F8BDC for <dhcwg@ietfa.amsl.com>; Fri, 16 Dec 2011 08:59:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.499
X-Spam-Level: 
X-Spam-Status: No, score=-103.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4zbkMjVrMH4R for <dhcwg@ietfa.amsl.com>; Fri, 16 Dec 2011 08:59:47 -0800 (PST)
Received: from mail-qw0-f51.google.com (mail-qw0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4D08F21F8B3D for <dhcwg@ietf.org>; Fri, 16 Dec 2011 08:59:47 -0800 (PST)
Received: by qadz3 with SMTP id z3so2176314qad.10 for <dhcwg@ietf.org>; Fri, 16 Dec 2011 08:59:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=R8Ok7rREN6t/8lqVsq+qPEOw1uGn9iOeWQV984F0EnE=; b=fSjeUJyXpU8B0vNTnpou8cG0SfiofUzzEPPo+lVDiP2xKAQcJ7RtZ41WiwXa1geFKm 8BOwQJ20X0epmzTUhxFlpsUMuaPyjAD3M4YerbMDIaVsnjoKqIO+/jTYvGBtQwRCZzgN Tvpyq/nJBpragaliMFSX4LuE8jZdUnEq9FVmU=
Received: by 10.224.98.8 with SMTP id o8mr12700728qan.79.1324054786802; Fri, 16 Dec 2011 08:59:46 -0800 (PST)
Received: from rtp-rdroms-8912.cisco.com (rtp-isp-nat1.cisco.com. [64.102.254.33]) by mx.google.com with ESMTPS id h9sm20605893qac.13.2011.12.16.08.59.44 (version=SSLv3 cipher=OTHER); Fri, 16 Dec 2011 08:59:45 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <D9B5773329187548A0189ED6503667890A2DA469@XMB-RCD-101.cisco.com>
Date: Fri, 16 Dec 2011 11:59:41 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <8E526A49-8354-4375-AA56-D2D9398848D4@gmail.com>
References: <EBA5E737-027B-40F2-AE1D-A48A2051F441@nominum.com><D9B5773329187548A0189ED6503667890A199E5D@XMB-RCD-101.cisco.com> <64188822-4E63-449C-B048-A4D6340252BD@gmail.com> <D9B5773329187548A0189ED6503667890A2DA469@XMB-RCD-101.cisco.com>
To: Bernie Volz (volz) <volz@cisco.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-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: Fri, 16 Dec 2011 16:59:48 -0000

On Dec 15, 2011, at 10:25 PM 12/15/11, Bernie Volz (volz) wrote:

> Ralph:
>=20
> The following text in section 3:
>=20
>   If a DHCPv6 client receives an IA_NA or IA_TA option containing a
>   SOL_MAX_RT option, the client MUST set its internal SOL_MAX_RT
>   parameter to the value contained in the SOL_MAX_RT option.  As a
>   result of receiving this option, the DHCPv6 client MUST NOT send any
>   Solicit messages more frequently than allowed by the retransmission
>   mechanism defined in sections 17.1.2 and 14 of RFC 315 [RFC3315].
>=20
> Fails to mention IA_PD (you probably forgot to update that sentence).

Oops.  Actually, I meant to edit out all references to IA_NA or IA_PD.  =
The goal is to simply change the default SOL_MAX_RT as that parameter is =
defined in RFC 3315, leaving aside any considerations of extended =
mechanisms for dealing with unsatisfied IA_* requests.
>=20
> And, I thought we were also considering using this when a client is =
not
> given any addresses AND/OR delegated any prefixes? But, perhaps you
> don't think that is necessary? If it is necessary (do read further =
down
> to the end as there are some other potential issues to consider with
> that), this draft would need to update several sections of RFC 3315? =
In
> particular:
>=20
> 17.1.3. Receipt of Advertise Messages
>=20
>   The client MUST ignore any Advertise message that includes a Status
>   Code option containing the value NoAddrsAvail, with the exception
>   that the client MAY display the associated status message to the
>   user.
>=20
> ...
>=20
> 17.2.2. Creation and Transmission of Advertise Messages
>=20
> ...
>=20
>   If the server will not assign any addresses to any IAs in a
>   subsequent Request from the client, the server MUST send an =
Advertise
>   message to the client that includes only a Status Code option with
>   code NoAddrsAvail and a status message for the user, a Server
>   Identifier option with the server's DUID, and a Client Identifier
>   option with the client's DUID.
>=20
>=20
> 17.1.3 has a MUST ignore. If the client included the SOL_MAX_RT option
> in the ORO, then it should not ignore but check for that option?
>=20
> 17.2.2 says MUST include only ... again, if client requested =
SOL_MAX_RT
> option in the ORO, server SHOULD include it.
>=20
> So, your section 2. "Update to RFC 3315" would need to say something
> about that these sections are impacted.

Yes.  Good catch.

> ---
>=20
> I also wonder whether to reduce the impact of the Security
> Considerations section we should impose some limit to the SOL_MAX_RT
> value that can be communicated by a Server. I was thinking that
> something like a day (86,400 seconds) would be a reasonable limit. =
But,
> not sure it really helps that much as that is rather long to be =
without
> [IPv6] service. And, if you had 10 Million devices on a network (and
> assuming they all were at that SOL_MAX_RT value), that results in 116
> Solicits/second which is probably still a fairly high rate. If you
> limited it to a week, that rate drops to 17 packets/second.

I'll leave this topic open for discussion.

> ---
>=20
> Some nits the RFC editor would likely catch ....
>=20
> 3.  SOL_MAX_RT option
> ...
>=20
>  mechanism defined in sections 17.1.2 and 14 of RFC 315 [RFC3315].
>                                                     ^^^

OK.

> 4.  Security Considerations
>=20
>   This document introduces one security considerations beyond those
>                                                      ^?
>   described in RFC 3315 [RFC3315].

OK.

> 6.  Normative References
>=20
> The references should include RFC 3633 as you now mention IA_PD (even
> before my issue above).

OK.

> Why do you include the following as it is never referenced?
>=20
>   [RFC2461]  Narten, T., Nordmark, E., and W. Simpson, "Neighbor
>              Discovery for IP Version 6 (IPv6)", RFC 2461,
>              December 1998.
>=20
> Perhaps it was explicitly referenced in the -00 draft because of the =
M/O
> bits?

Right.

>=20
> ---
>=20
> A few other nits:
>=20
> In section 1, it says "high volume of aggregated traffic at a DHCPv6
> server" ... would also cause high volumes of traffic if there is no
> DHCPv6 server. Might also revise section 2 (significantly reducing the
> aggregated traffic at the DHCPv6 server). I think the "at the DHCPv6
> server" can be dropped?

Maybe, except if there is no DHCPv6 server, the traffic issue can be =
mitigated by turning off the relay agents.

> Especially if we change the draft to allow the SOL_MAX_RT option to be
> communicated when no addresses (and/or prefixes) are provided, it =
would
> be worth (in section 3) to indicate that a client should use the =
server
> provided SOL_MAX_RT value until some 'hard' reboot (not just a soft
> reset) -- some devices may soft reset every so often when waiting to
> come online which would defeat the utility of the server provided
> SOL_MAX_RT. Also, that an updated SOL_MAX_RT value should not cause =
the
> client to in any way reset its Solicit timer (we don't want it to =
reset
> the current timing algorithm (other than to cap the timeout) if
> retrying).

Hm.  I'm not sure how to specify "hard reboot" versus "soft reset"...

- Ralph

>=20
> - Bernie
>=20
> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
> Of Ralph Droms
> Sent: Thursday, December 15, 2011 9:56 AM
> To: dhc WG
> Subject: Re: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-00
>=20
> I've published rev -01 taking into account comments from Bernie and
> others.
>=20
> The changes:
>=20
> * simplifies the discussion of "why is this option is needed"
> * applies the new SOL_MAX_RT value to any Solicits (leaving aside the
> question of how a client will deal with an Advertise that satisfies,
> e.g., an IA_NA request but not an IA_PD request)
> * requires client to request the option in an ORO
> * clarifies that the server returns the option in the main body of a
> response
>=20
> I think this option can be moved forward without tying it to the
> resolution of partial IA_* assignments.  This option simplify modifies
> the default value of SOL_MAX_RT.  Any future modifications to the
> definition and use of SOL_MAX_RT would be independent of this option -
> i.e., would be specified in terms of SOL_MAX_RT or some new MAX_RT
> defaults - so this new option would apply (or not) regardless.
>=20
> Pragmatically, there is interest in the SP and vendor community to =
move
> this option forward so the soon-to-be deployed IPv6-capable CE routers
> can mitigate issues with certain deployment scenarios.
>=20
> - Ralph
>=20
> On Dec 10, 2011, at 10:16 PM 12/10/11, Bernie Volz (volz) wrote:
>=20
>> I think this draft needs to be updated a bit. It never mentions
> ANYTHING
>> about IA_PD.
>>=20
>> I think whenever a server returns NoAddrsAvail or NoPrefixAvail
> status,
>> it should be able to provide this option in the response to indicate
> to
>> the client a new SOL_MAX_RT value for the IA type(s) requested by the
>> client.
>>=20
>> The draft fails to solve the situation where a CPE routers that
> request
>> both an IA_NA and IA_PD (whether in one or two requests) does so
>> frequently. The current draft handles the case where addresses are =
not
>> being provided, but fails to handle the case where IA_PDs are also =
not
>> being provided.
>>=20
>> - Bernie
>>=20
>> -----Original Message-----
>> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On =
Behalf
>> Of Ted Lemon
>> Sent: Friday, December 09, 2011 12:58 PM
>> To: dhcwg@ietf.org WG
>> Subject: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-00
>>=20
>> Ralph's put in an individual submission draft with Jari as the
>> sponsoring AD.   The draft attempts to solve a problem ISPs are =
having
>> where in a massive IPv6 network that isn't entirely deployed, devices
>> are requesting configuration too often.
>>=20
>> Ralph's draft proposes a new option whereby a DHCP server can =
indicate
>> in response to a solicit that the client should use a larger value =
for
>> SOL_MAX_RT.   This means that clients will continue their exponential
>> backoff to whatever limit is stated in the offer, and reduces the
>> overall traffic on the DHCP servers at the core of the network.
>>=20
>> The draft is an individual submission, so it doesn't technically have
> to
>> pass dhcwg last call-just IETF last call.   However, since the dhcwg
> is
>> where DHCP protocol extensions are done, I'm doing a last call here =
to
>> encourage people to review it-it would really help if some wg
>> participants would review it and think about the implications.
>>=20
>> If we don't hear anything by December 23, Jari will continue the
> process
>> of advancing the draft.   If you do read the draft, please comment
> here
>> as to whether you support it, and please offer any suggestions you =
may
>> have.
>>=20
>> Thanks!
>>=20
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From Ted.Lemon@nominum.com  Fri Dec 16 12:52:40 2011
Return-Path: <Ted.Lemon@nominum.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 2800B1F0C51 for <dhcwg@ietfa.amsl.com>; Fri, 16 Dec 2011 12:52:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.551
X-Spam-Level: 
X-Spam-Status: No, score=-106.551 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lOY9WX4kfilr for <dhcwg@ietfa.amsl.com>; Fri, 16 Dec 2011 12:52:39 -0800 (PST)
Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id 5AC811F0C3F for <dhcwg@ietf.org>; Fri, 16 Dec 2011 12:52:39 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob117.postini.com ([64.18.6.12]) with SMTP ID DSNKTuuvlrdmI30e0G7lCq40bLd/JS//YrFl@postini.com; Fri, 16 Dec 2011 12:52:39 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 822411B82D1 for <dhcwg@ietf.org>; Fri, 16 Dec 2011 12:52:38 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 66D68190052; Fri, 16 Dec 2011 12:52:38 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-02.WIN.NOMINUM.COM ([64.89.228.134]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.01.0339.001; Fri, 16 Dec 2011 12:52:38 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Thread-Topic: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-00
Thread-Index: AQHMtpwjAljFLrkpaEuFQR2ym6HpQ5XV+CLAgAeUJQCAANFYAIAA43mAgABBFIA=
Date: Fri, 16 Dec 2011 20:52:37 +0000
Message-ID: <8E9FC29E-6CBA-430C-AF70-CC9F6BD571AA@nominum.com>
References: <EBA5E737-027B-40F2-AE1D-A48A2051F441@nominum.com><D9B5773329187548A0189ED6503667890A199E5D@XMB-RCD-101.cisco.com> <64188822-4E63-449C-B048-A4D6340252BD@gmail.com> <D9B5773329187548A0189ED6503667890A2DA469@XMB-RCD-101.cisco.com> <8E526A49-8354-4375-AA56-D2D9398848D4@gmail.com>
In-Reply-To: <8E526A49-8354-4375-AA56-D2D9398848D4@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_8E9FC29E6CBA430CAF70CC9F6BD571AAnominumcom_"
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-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: Fri, 16 Dec 2011 20:52:40 -0000

--_000_8E9FC29E6CBA430CAF70CC9F6BD571AAnominumcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Dec 16, 2011, at 11:59 AM, Ralph Droms wrote:
I also wonder whether to reduce the impact of the Security
Considerations section we should impose some limit to the SOL_MAX_RT
value that can be communicated by a Server. I was thinking that
something like a day (86,400 seconds) would be a reasonable limit. But,
not sure it really helps that much as that is rather long to be without
[IPv6] service. And, if you had 10 Million devices on a network (and
assuming they all were at that SOL_MAX_RT value), that results in 116
Solicits/second which is probably still a fairly high rate. If you
limited it to a week, that rate drops to 17 packets/second.

I'll leave this topic open for discussion.

I think that if the DHCP client is required not to cache the value of SOL_M=
AX_RT across restarts, that would address this concern.   You know the stan=
dard IT crowd question: did you turn it off and then on again?


--_000_8E9FC29E6CBA430CAF70CC9F6BD571AAnominumcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <36D896294F04FB458B8794A994C0D3D9@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 16, 2011, at 11:59 AM, Ralph Droms wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">
<div>
<blockquote type=3D"cite">I also wonder whether to reduce the impact of the=
 Security<br>
</blockquote>
<blockquote type=3D"cite">Considerations section we should impose some limi=
t to the SOL_MAX_RT<br>
</blockquote>
<blockquote type=3D"cite">value that can be communicated by a Server. I was=
 thinking that<br>
</blockquote>
<blockquote type=3D"cite">something like a day (86,400 seconds) would be a =
reasonable limit. But,<br>
</blockquote>
<blockquote type=3D"cite">not sure it really helps that much as that is rat=
her long to be without<br>
</blockquote>
<blockquote type=3D"cite">[IPv6] service. And, if you had 10 Million device=
s on a network (and<br>
</blockquote>
<blockquote type=3D"cite">assuming they all were at that SOL_MAX_RT value),=
 that results in 116<br>
</blockquote>
<blockquote type=3D"cite">Solicits/second which is probably still a fairly =
high rate. If you<br>
</blockquote>
<blockquote type=3D"cite">limited it to a week, that rate drops to 17 packe=
ts/second.<br>
</blockquote>
<br>
I'll leave this topic open for discussion.</div>
</span></blockquote>
</div>
<br>
<div>I think that if the DHCP client is required not to cache the value of =
SOL_MAX_RT across restarts, that would address this concern. &nbsp; You kno=
w the standard IT crowd question: did you turn it off and then on again?</d=
iv>
<div><br>
</div>
</body>
</html>

--_000_8E9FC29E6CBA430CAF70CC9F6BD571AAnominumcom_--

From wwwrun@rfc-editor.org  Fri Dec 16 12:52:44 2011
Return-Path: <wwwrun@rfc-editor.org>
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 8864C1F0C62; Fri, 16 Dec 2011 12:52:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.12
X-Spam-Level: 
X-Spam-Status: No, score=-102.12 tagged_above=-999 required=5 tests=[AWL=-0.120, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WMDpmxW9e-Cq; Fri, 16 Dec 2011 12:52:44 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 262FB1F0C51; Fri, 16 Dec 2011 12:52:43 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id DFCE772E004; Fri, 16 Dec 2011 12:51:36 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20111216205136.DFCE772E004@rfc-editor.org>
Date: Fri, 16 Dec 2011 12:51:36 -0800 (PST)
Cc: dhcwg@ietf.org, rfc-editor@rfc-editor.org
Subject: [dhcwg] RFC 6422 on Relay-Supplied DHCP Options
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: Fri, 16 Dec 2011 20:52:44 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6422

        Title:      Relay-Supplied DHCP Options 
        Author:     T. Lemon, Q. Wu
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2011
        Mailbox:    mellon@nominum.com, 
                    sunseawq@huawei.com
        Pages:      8
        Characters: 16056
        Updates:    RFC3315

        I-D Tag:    draft-ietf-dhc-dhcpv6-relay-supplied-options-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6422.txt

DHCPv6 relay agents cannot communicate with DHCPv6 clients directly.
However, in some cases, the relay agent possesses some information
that would be useful to the DHCPv6 client.  This document describes a
mechanism whereby the DHCPv6 relay agent can provide such information
to the DHCPv6 server, which can, in turn, pass this information on to
the DHCP client.

This document updates RFC 3315 (DHCPv6) by making explicit the
implicit requirement that relay agents not modify the content of
encapsulation payloads as they are relayed back toward clients.  
[STANDARDS-TRACK]

This document is a product of the Dynamic Host Configuration Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From volz@cisco.com  Fri Dec 16 12:56:03 2011
Return-Path: <volz@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 E355D11E8094 for <dhcwg@ietfa.amsl.com>; Fri, 16 Dec 2011 12:56:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.561
X-Spam-Level: 
X-Spam-Status: No, score=-6.561 tagged_above=-999 required=5 tests=[AWL=0.037,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1kCIpBRa+YF3 for <dhcwg@ietfa.amsl.com>; Fri, 16 Dec 2011 12:56:02 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 59B1611E80A6 for <dhcwg@ietf.org>; Fri, 16 Dec 2011 12:56:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=volz@cisco.com; l=11292; q=dns/txt; s=iport; t=1324068962; x=1325278562; h=mime-version:subject:date:message-id:in-reply-to: references:from:to:cc; bh=ALv47sbjnMyhnWVp8sq83Zx5Z5fPe7PDYSO/fcWWJi4=; b=Ug0ylUTVBICSalonIfzxMZ3Woa2MwZlUQcC/3anV2TR0IJux5RwSLYDP DPcojbN8xvDXxp/mcW+yHDE4BKcnHzEQ1Y/7YE/S1iRoK1bi6YlP0ZNTM AlMaB7m/ImSDqX2UcfTN9d2uC/i1b3Jp5nQYNzFNmKgC/jWyZdFjPwlQ8 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoUAABiv606tJXHA/2dsb2JhbABEgk6YPJBLgQWBcgEBAQQSAQkRA0kQAgEIEQQBAQsGFwEGAUUJCAIEARIIGqFOAZ4xiyFjBIg0nw0
X-IronPort-AV: E=Sophos;i="4.71,365,1320624000"; d="scan'208,217";a="44694353"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-4.cisco.com with ESMTP; 16 Dec 2011 20:56:01 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core2-5.cisco.com (8.14.3/8.14.3) with ESMTP id pBGKu1wF013490;  Fri, 16 Dec 2011 20:56:01 GMT
Received: from xmb-rcd-101.cisco.com ([72.163.62.143]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 16 Dec 2011 14:56:01 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCBC35.1E43FAF3"
Date: Fri, 16 Dec 2011 14:56:04 -0600
Message-ID: <D9B5773329187548A0189ED6503667890A2DA6C0@XMB-RCD-101.cisco.com>
In-Reply-To: <8E9FC29E-6CBA-430C-AF70-CC9F6BD571AA@nominum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-00
Thread-Index: AQHMtpwjAljFLrkpaEuFQR2ym6HpQ5XV+CLAgAeUJQCAANFYAIAA43mAgABBFID//3pd8A==
References: <EBA5E737-027B-40F2-AE1D-A48A2051F441@nominum.com><D9B5773329187548A0189ED6503667890A199E5D@XMB-RCD-101.cisco.com> <64188822-4E63-449C-B048-A4D6340252BD@gmail.com> <D9B5773329187548A0189ED6503667890A2DA469@XMB-RCD-101.cisco.com> <8E526A49-8354-4375-AA56-D2D9398848D4@gmail.com> <8E9FC29E-6CBA-430C-AF70-CC9F6BD571AA@nominum.com>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Ted Lemon" <Ted.Lemon@nominum.com>, "Ralph Droms" <rdroms.ietf@gmail.com>
X-OriginalArrivalTime: 16 Dec 2011 20:56:01.0712 (UTC) FILETIME=[1E742B00:01CCBC35]
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-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: Fri, 16 Dec 2011 20:56:04 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CCBC35.1E43FAF3
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

There are really two issues:

=20

1.       If the client always 'resets' and never uses the server
provided value, then the server provided value has no usefulness.

2.       We don't want the client to keep the server provided value in
'stable storage' between hard power cycles.

=20

This is tricky to describe.

=20

-          Bernie

=20

From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
Sent: Friday, December 16, 2011 3:53 PM
To: Ralph Droms
Cc: Bernie Volz (volz); dhc WG
Subject: Re: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-00

=20

On Dec 16, 2011, at 11:59 AM, Ralph Droms wrote:

		I also wonder whether to reduce the impact of the
Security

		Considerations section we should impose some limit to
the SOL_MAX_RT

		value that can be communicated by a Server. I was
thinking that

		something like a day (86,400 seconds) would be a
reasonable limit. But,

		not sure it really helps that much as that is rather
long to be without

		[IPv6] service. And, if you had 10 Million devices on a
network (and

		assuming they all were at that SOL_MAX_RT value), that
results in 116

		Solicits/second which is probably still a fairly high
rate. If you

		limited it to a week, that rate drops to 17
packets/second.

=09
	I'll leave this topic open for discussion.

=20

I think that if the DHCP client is required not to cache the value of
SOL_MAX_RT across restarts, that would address this concern.   You know
the standard IT crowd question: did you turn it off and then on again?

=20


------_=_NextPart_001_01CCBC35.1E43FAF3
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:947350380;
	mso-list-type:hybrid;
	mso-list-template-ids:187879106 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1093430750;
	mso-list-type:hybrid;
	mso-list-template-ids:-988232362 -1159986896 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple style=3D'word-wrap: break-word;-webkit-nbsp-mode: =
space;-webkit-line-break: after-white-space'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>There are really two issues:<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>If the client always &#8216;resets&#8217; and never uses the server =
provided value, then the server provided value has no =
usefulness.<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>We don&#8217;t want the client to keep the server provided value in =
&#8216;stable storage&#8217; between hard power =
cycles.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>This is tricky to describe.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l1 level1 lfo2'><![if =
!supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><span style=3D'mso-list:Ignore'>-<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Bernie<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Ted Lemon [mailto:Ted.Lemon@nominum.com] <br><b>Sent:</b> Friday, =
December 16, 2011 3:53 PM<br><b>To:</b> Ralph Droms<br><b>Cc:</b> Bernie =
Volz (volz); dhc WG<br><b>Subject:</b> Re: [dhcwg] WGLC: =
draft-droms-dhc-dhcpv6-solmaxrt-update-00<o:p></o:p></span></p></div></di=
v><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p =
class=3DMsoNormal>On Dec 16, 2011, at 11:59 AM, Ralph Droms =
wrote:<o:p></o:p></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'>I also =
wonder whether to reduce the impact of the =
Security<o:p></o:p></span></p></blockquote><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'>Considera=
tions section we should impose some limit to the =
SOL_MAX_RT<o:p></o:p></span></p></blockquote><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'>value =
that can be communicated by a Server. I was thinking =
that<o:p></o:p></span></p></blockquote><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'>something=
 like a day (86,400 seconds) would be a reasonable limit. =
But,<o:p></o:p></span></p></blockquote><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'>not sure =
it really helps that much as that is rather long to be =
without<o:p></o:p></span></p></blockquote><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'>[IPv6] =
service. And, if you had 10 Million devices on a network =
(and<o:p></o:p></span></p></blockquote><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'>assuming =
they all were at that SOL_MAX_RT value), that results in =
116<o:p></o:p></span></p></blockquote><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'>Solicits/=
second which is probably still a fairly high rate. If =
you<o:p></o:p></span></p></blockquote><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'>limited =
it to a week, that rate drops to 17 =
packets/second.<o:p></o:p></span></p></blockquote><p =
class=3DMsoNormal><span =
style=3D'font-size:13.5pt;font-family:"Helvetica","sans-serif"'><br>I'll =
leave this topic open for =
discussion.<o:p></o:p></span></p></div></blockquote></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>I think =
that if the DHCP client is required not to cache the value of SOL_MAX_RT =
across restarts, that would address this concern. &nbsp; You know the =
standard IT crowd question: did you turn it off and then on =
again?<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------_=_NextPart_001_01CCBC35.1E43FAF3--

From rdroms.ietf@gmail.com  Fri Dec 16 12:57:48 2011
Return-Path: <rdroms.ietf@gmail.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 529BC1F0C68 for <dhcwg@ietfa.amsl.com>; Fri, 16 Dec 2011 12:57:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.539
X-Spam-Level: 
X-Spam-Status: No, score=-103.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pjRqqYRIt5Dn for <dhcwg@ietfa.amsl.com>; Fri, 16 Dec 2011 12:57:47 -0800 (PST)
Received: from mail-qw0-f51.google.com (mail-qw0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id C0ED31F0C5B for <dhcwg@ietf.org>; Fri, 16 Dec 2011 12:57:47 -0800 (PST)
Received: by qadz3 with SMTP id z3so2313902qad.10 for <dhcwg@ietf.org>; Fri, 16 Dec 2011 12:57:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=cyGa305SXP6U8LjeMMnEOx4Lsw/84OyuuqwZX2k0Bb8=; b=EwzugcPCavV4bwhaaWpOmqIpBXm3VxwkuEwGZjmBz6iwzKjP1ZOrF+OfZ+HPph3D4r kiUx/0N9nnnnmjSJxIXLdqUSVDYct0p3XTxQ+FKPd8f4r5S2cg3hx2aLouR/o9JuVKHa qjXU1U15mRppG6Ltk8DKUyUrSQJJvAM6TLjUQ=
Received: by 10.224.96.72 with SMTP id g8mr14331378qan.56.1324069067255; Fri, 16 Dec 2011 12:57:47 -0800 (PST)
Received: from rtp-rdroms-8912.cisco.com (rtp-isp-nat1.cisco.com. [64.102.254.33]) by mx.google.com with ESMTPS id dj8sm21648698qab.19.2011.12.16.12.57.45 (version=SSLv3 cipher=OTHER); Fri, 16 Dec 2011 12:57:46 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <741CB57E-F60F-49A4-8F2C-A888F45E1BD9@nominum.com>
Date: Fri, 16 Dec 2011 15:57:44 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D9188E43-7695-4397-BA02-667DCF089228@gmail.com>
References: <EBA5E737-027B-40F2-AE1D-A48A2051F441@nominum.com> <D9B5773329187548A0189ED6503667890A199E5D@XMB-RCD-101.cisco.com> <64188822-4E63-449C-B048-A4D6340252BD@gmail.com> <741CB57E-F60F-49A4-8F2C-A888F45E1BD9@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC: draft-droms-dhc-dhcpv6-solmaxrt-update-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: Fri, 16 Dec 2011 20:57:48 -0000

Nope, no need to move faster.  Just wanted to remind the WG that it =
would be better to comment sooner rather than later...

- Ralph

On Dec 16, 2011, at 12:53 AM 12/16/11, Ted Lemon wrote:

> On Dec 15, 2011, at 9:56 AM, Ralph Droms wrote:
>> Pragmatically, there is interest in the SP and vendor community to =
move this option forward so the soon-to-be deployed IPv6-capable CE =
routers can mitigate issues with certain deployment scenarios.
>=20
> Ralph, are you arguing that we should pass this on sooner than the =
date I originally proposed?   Given that we've had some review and that =
we generally don't get late review, and that this particular review is =
informal, I'm not entirely opposed to that, but please let me know if =
that's what you intended.
>=20


From iesg-secretary@ietf.org  Mon Dec 19 09:06:38 2011
Return-Path: <iesg-secretary@ietf.org>
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 476C31F0C50; Mon, 19 Dec 2011 09:06:38 -0800 (PST)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zM1k9MSBJuTQ; Mon, 19 Dec 2011 09:06:37 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE67421F84B9; Mon, 19 Dec 2011 09:06:37 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111219170637.20167.36066.idtracker@ietfa.amsl.com>
Date: Mon, 19 Dec 2011 09:06:37 -0800
Cc: dhcwg@ietf.org
Subject: [dhcwg] Last Call: <draft-ietf-dhc-vpn-option-14.txt> (Virtual Subnet	Selection Options for DHCPv4 and DHCPv6) to Proposed Standard
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
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: Mon, 19 Dec 2011 17:06:38 -0000

The IESG has received a request from the Dynamic Host Configuration WG
(dhc) to consider the following document:
- 'Virtual Subnet Selection Options for DHCPv4 and DHCPv6'
  <draft-ietf-dhc-vpn-option-14.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2012-01-04. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This memo defines a Virtual Subnet Selection (VSS) option for each of
   DHCPv4 and DHCPv6, and a VSS sub-option carried in the DHCPv4 relay-
   agent-information option.  These are intended for use by DHCP
   clients, relay agents, and proxy clients in situations where VSS
   information needs to be passed to the DHCP server for proper address
   or prefix allocation to take place.

   For the DHCPv4 option and relay-agent-information sub-option, this
   memo documents existing usage as per RFC 3942 [RFC3942].  This memo
   updates RFC 3046 [RFC3046] regarding details relating to copying of
   sub-options (see Section 8).




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-dhc-vpn-option/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-dhc-vpn-option/


The following IPR Declarations may be related to this I-D:

   http://datatracker.ietf.org/ipr/1245/




From iesg-secretary@ietf.org  Mon Dec 19 11:52:07 2011
Return-Path: <iesg-secretary@ietf.org>
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 AC5CB21F8472; Mon, 19 Dec 2011 11:52:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.546
X-Spam-Level: 
X-Spam-Status: No, score=-102.546 tagged_above=-999 required=5 tests=[AWL=0.053, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OTQ-x9iThZIt; Mon, 19 Dec 2011 11:52:07 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0996E21F8319; Mon, 19 Dec 2011 11:52:07 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111219195206.6134.35948.idtracker@ietfa.amsl.com>
Date: Mon, 19 Dec 2011 11:52:06 -0800
Cc: dhcwg@ietf.org
Subject: [dhcwg] REVISED Last Call: <draft-ietf-dhc-vpn-option-14.txt> (Virtual Subnet	Selection Options for DHCPv4 and DHCPv6) to Proposed Standard
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
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: Mon, 19 Dec 2011 19:52:08 -0000

The IESG has received a request from the Dynamic Host Configuration WG
(dhc) to consider the following document:
- 'Virtual Subnet Selection Options for DHCPv4 and DHCPv6'
  <draft-ietf-dhc-vpn-option-14.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Note that this document has been
extensively revised based on previous IESG review, and this is a
second IETF Last Call on this document.  Please send substantive
comments to the ietf@ietf.org mailing lists by 2012-01-04.
Exceptionally, comments may be sent to iesg@ietf.org instead.  In
either case, please retain the beginning of the Subject line to allow
automated sorting.

Abstract


   This memo defines a Virtual Subnet Selection (VSS) option for each of
   DHCPv4 and DHCPv6, and a VSS sub-option carried in the DHCPv4 relay-
   agent-information option.  These are intended for use by DHCP
   clients, relay agents, and proxy clients in situations where VSS
   information needs to be passed to the DHCP server for proper address
   or prefix allocation to take place.

   For the DHCPv4 option and relay-agent-information sub-option, this
   memo documents existing usage as per RFC 3942 [RFC3942].  This memo
   updates RFC 3046 [RFC3046] regarding details relating to copying of
   sub-options (see Section 8).




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-dhc-vpn-option/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-dhc-vpn-option/


The following IPR Declarations may be related to this I-D:

   http://datatracker.ietf.org/ipr/1245/




From internet-drafts@ietf.org  Mon Dec 19 23:39:25 2011
Return-Path: <internet-drafts@ietf.org>
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 0A67D11E80DC; Mon, 19 Dec 2011 23:39:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cw4natlQCSu8; Mon, 19 Dec 2011 23:39:24 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A540711E80A2; Mon, 19 Dec 2011 23:39:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111220073924.5093.77071.idtracker@ietfa.amsl.com>
Date: Mon, 19 Dec 2011 23:39:24 -0800
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-pd-exclude-04.txt
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: Tue, 20 Dec 2011 07:39:25 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Dynamic Host Configuration Working Gr=
oup of the IETF.

	Title           : Prefix Exclude Option for DHCPv6-based Prefix Delegation
	Author(s)       : Jouni Korhonen
                          Teemu Savolainen
                          Suresh Krishnan
                          Ole Troan
	Filename        : draft-ietf-dhc-pd-exclude-04.txt
	Pages           : 10
	Date            : 2011-12-19

   This specification defines an optional mechanism to allow exclusion
   of one specific prefix from a delegated prefix set when using DHCPv6-
   based prefix delegation.  The new mechanism updates RFC 3633.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-pd-exclude-04.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-pd-exclude-04.txt


From internet-drafts@ietf.org  Wed Dec 21 08:42:21 2011
Return-Path: <internet-drafts@ietf.org>
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 2C35E21F889A; Wed, 21 Dec 2011 08:42:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level: 
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id knv1FLJtoDQm; Wed, 21 Dec 2011 08:42:20 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9A9321F84D6; Wed, 21 Dec 2011 08:42:20 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111221164220.13693.80809.idtracker@ietfa.amsl.com>
Date: Wed, 21 Dec 2011 08:42:20 -0800
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-forcerenew-nonce-03.txt
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: Wed, 21 Dec 2011 16:42:21 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Dynamic Host Configuration Working Gr=
oup of the IETF.

	Title           : Forcerenew Nonce Authentication
	Author(s)       : David Miles
                          Wojciech Dec
                          James Bristow
                          Roberta Maglione
	Filename        : draft-ietf-dhc-forcerenew-nonce-03.txt
	Pages           : 11
	Date            : 2011-12-21

   DHCP Forcerenew allows for the reconfiguration of a single host by
   forcing the DHCP client into a Renew state on a trigger from the DHCP
   server.  In Forcerenew Nonce Authentication the server sends a nonce
   with the client on the initial DHCP ACK that is used for subsequent
   validation of a Forcerenew message.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-forcerenew-nonce-03.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-forcerenew-nonce-03.txt


From mayer@ntp.org  Sun Dec 25 21:13:35 2011
Return-Path: <mayer@ntp.org>
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 9D65221F899F; Sun, 25 Dec 2011 21:13:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.966
X-Spam-Level: 
X-Spam-Status: No, score=-2.966 tagged_above=-999 required=5 tests=[AWL=-0.967, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rzjv7KtjOG0q; Sun, 25 Dec 2011 21:13:35 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by ietfa.amsl.com (Postfix) with ESMTP id 364C721F852E; Sun, 25 Dec 2011 21:13:35 -0800 (PST)
Received: from pool-141-157-189-77.bstnma.btas.verizon.net ([141.157.189.77] helo=[10.10.10.102]) by mail1.ntp.org with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76 (FreeBSD)) (envelope-from <mayer@ntp.org>) id 1Rf2sJ-0007U3-LQ; Mon, 26 Dec 2011 05:13:33 +0000
Message-ID: <4EF80273.6030809@ntp.org>
Date: Mon, 26 Dec 2011 00:13:23 -0500
From: Danny Mayer <mayer@ntp.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A9@INBANSXCHMBSA1.in.alcatel-lucent.com>
In-Reply-To: <7C362EEF9C7896468B36C9B79200D8350D026F16A9@INBANSXCHMBSA1.in.alcatel-lucent.com>
X-Enigmail-Version: 1.3.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 141.157.189.77
X-SA-Exim-Rcpt-To: manav.bhatia@alcatel-lucent.com, tictoc@ietf.org, ntpwg@lists.ntp.org, dhcwg@ietf.org
X-SA-Exim-Mail-From: mayer@ntp.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: NTP WG <ntpwg@lists.ntp.org>, DHCP Working Group <dhcwg@ietf.org>, TICTOC WG <tictoc@ietf.org>
Subject: Re: [dhcwg] [TICTOC] IPv6 Router Advertisement Option for NTP Server Configuration
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: Mon, 26 Dec 2011 05:13:35 -0000

On 12/19/2011 8:29 PM, Bhatia, Manav (Manav) wrote:
> Hi,
> 
> We have posted a new draft that extends Router Advertisements to
include information about the one or more NTP servers present in the
network. This is useful where the delays in acquiring server addresses
and communicating with the servers are critical (mobile environment for
example).
> 
> 
http://www.ietf.org/internet-drafts/draft-bcd-6man-ntp-server-ra-opt-00.txt
> 
> Would be great to get some feedback from the NTP and the TICTOC WGs.
> 
> We will also be soliciting comments from the v6man WG.
> 

Is there a reason that RFC5908 - "Network Time Protocol (NTP) Server
Option for DHCPv6" is not sufficient for this? Why do we need yet
another way of specifying NTP servers? I'm copying the DHC working group
on this though I think some of them are also on the 6man WG mailing list
as well.

Danny

From Ted.Lemon@nominum.com  Mon Dec 26 08:33:57 2011
Return-Path: <Ted.Lemon@nominum.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 E8A5521F8BA7; Mon, 26 Dec 2011 08:33:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.431
X-Spam-Level: 
X-Spam-Status: No, score=-106.431 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LI1ljYzK8yo9; Mon, 26 Dec 2011 08:33:57 -0800 (PST)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id 04F9E21F8BA2; Mon, 26 Dec 2011 08:33:56 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKTvih6IooQK+LTI1+vSSAgmOrihg2QROj@postini.com; Mon, 26 Dec 2011 08:33:57 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id E8C5D1B82C0; Mon, 26 Dec 2011 08:33:43 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 6A97019005D; Mon, 26 Dec 2011 08:33:42 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.01.0339.001; Mon, 26 Dec 2011 08:33:42 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Danny Mayer <mayer@ntp.org>
Thread-Topic: [dhcwg] [TICTOC] IPv6 Router Advertisement Option for NTP Server Configuration
Thread-Index: AQHMw40mU7wszRgSIUyM0fUrTlN4QJXu10KA
Date: Mon, 26 Dec 2011 16:33:41 +0000
Message-ID: <15A1ACF1-F886-4CEF-B448-D4D77B4F2D64@nominum.com>
References: <7C362EEF9C7896468B36C9B79200D8350D026F16A9@INBANSXCHMBSA1.in.alcatel-lucent.com> <4EF80273.6030809@ntp.org>
In-Reply-To: <4EF80273.6030809@ntp.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: multipart/alternative; boundary="_000_15A1ACF1F8864CEFB448D4D77B4F2D64nominumcom_"
MIME-Version: 1.0
Cc: NTP WG <ntpwg@lists.ntp.org>, DHCP Working Group <dhcwg@ietf.org>, "Bhatia, Manav \(Manav\)" <manav.bhatia@alcatel-lucent.com>, TICTOC WG <tictoc@ietf.org>
Subject: Re: [dhcwg] [TICTOC] IPv6 Router Advertisement Option for NTP	Server Configuration
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: Mon, 26 Dec 2011 16:33:58 -0000

--_000_15A1ACF1F8864CEFB448D4D77B4F2D64nominumcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Dec 26, 2011, at 12:13 AM, Danny Mayer wrote:
Is there a reason that RFC5908 - "Network Time Protocol (NTP) Server
Option for DHCPv6" is not sufficient for this? Why do we need yet
another way of specifying NTP servers? I'm copying the DHC working group
on this though I think some of them are also on the 6man WG mailing list
as well.

It's actually a really bad idea to have two ways of configuring the same in=
formation.   The choice to provide DNS server information via RA was a mist=
ake that is now creating unnecessary complexity in stacks.   This is not so=
mething that should be duplicated for additional RA options.


--_000_15A1ACF1F8864CEFB448D4D77B4F2D64nominumcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <573DF0769E96104BA1D7E1BE2FCBAE69@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On Dec 26, 2011, at 12:13 AM, Danny Mayer wrote:</div>
<blockquote type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-=
collapse: separate; font-family: Helvetica; font-style: normal; font-varian=
t: normal; font-weight: normal; letter-spacing: normal; line-height: normal=
; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: n=
one; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-hori=
zontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-dec=
orations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stro=
ke-width: 0px; font-size: medium; ">Is
 there a reason that RFC5908 - &quot;Network Time Protocol (NTP) Server<br>
Option for DHCPv6&quot; is not sufficient for this? Why do we need yet<br>
another way of specifying NTP servers? I'm copying the DHC working group<br=
>
on this though I think some of them are also on the 6man WG mailing list<br=
>
as well.</span></blockquote>
</div>
<br>
<div>It's actually a really bad idea to have two ways of configuring the sa=
me information. &nbsp; The choice to provide DNS server information via RA =
was a mistake that is now creating unnecessary complexity in stacks. &nbsp;=
 This is not something that should be duplicated
 for additional RA options.</div>
<div><br>
</div>
</body>
</html>

--_000_15A1ACF1F8864CEFB448D4D77B4F2D64nominumcom_--

From zhou.sujing@zte.com.cn  Tue Dec 27 21:32:04 2011
Return-Path: <zhou.sujing@zte.com.cn>
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 C614F21F8AAF for <dhcwg@ietfa.amsl.com>; Tue, 27 Dec 2011 21:32:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.239
X-Spam-Level: 
X-Spam-Status: No, score=-97.239 tagged_above=-999 required=5 tests=[AWL=0.246, BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bU8U4qia7neC for <dhcwg@ietfa.amsl.com>; Tue, 27 Dec 2011 21:32:04 -0800 (PST)
Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 7ED7C21F8A91 for <dhcwg@ietf.org>; Tue, 27 Dec 2011 21:32:03 -0800 (PST)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 53829262235339; Wed, 28 Dec 2011 13:29:55 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.15] with StormMail ESMTP id 4315.262235339; Wed, 28 Dec 2011 13:31:51 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id pBS5Vkbm076483 for <dhcwg@ietf.org>; Wed, 28 Dec 2011 13:31:46 +0800 (GMT-8) (envelope-from zhou.sujing@zte.com.cn)
To: dhcwg@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF073C68FB.E10BB191-ON48257974.001E46A2-48257974.001E60AE@zte.com.cn>
From: zhou.sujing@zte.com.cn
Date: Wed, 28 Dec 2011 13:31:39 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-12-28 13:31:47, Serialize complete at 2011-12-28 13:31:47
Content-Type: multipart/alternative; boundary="=_alternative 001E60AB48257974_="
X-MAIL: mse01.zte.com.cn pBS5Vkbm076483
Subject: [dhcwg] a brief review on draft-xu-dhc-cadhcp-01
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: Wed, 28 Dec 2011 05:32:05 -0000

This is a multipart message in MIME format.
--=_alternative 001E60AB48257974_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQteHUtZGhjLWNhZGhjcC0wMQ0KDQpzZWN0
aW9uIDMNCiAgICJJZiB0aGUgREhDUCBzZXJ2ZXIgaXMgYXV0aGVudGljYXRlZCBieSBhIHRydXN0
ZWQgc2VydmVyLCB0aGUgREhDUCANCnNlcnZlcg0KICAgZG93bmxvYWRzIHRoZSBESENQIGNsaWVu
dCBjZXJ0aWZpY2F0ZSBmcm9tIHRoZSB0cnVzdGVkIHNlcnZlci5UaGUNCiAgIGNlcnRpZmljYXRl
IG1heSBiZSBwcm90ZWN0ZWQgd2l0aCB0aGUgc2VjdXJlIHR1bm5lbCwgc3VjaCBhcywgU1NMLw0K
ICAgVExTLCB3aGljaCBlc3RhYmxpc2hlZCBiZXR3ZWVuIHRoZSBESENQIHNlcnZlciBhbmQgdGhl
IHRydXN0ZWQNCiAgIHNlcnZlci4gIFRocm91Z2ggdGhlIGF1dGhlbnRpY2F0aW9uIGJldHdlZW4g
REhDUCBzZXJ2ZXIgYW5kIHRoZQ0KICAgdHJ1c3RlZCBzZXJ2ZXIsIG9ubHkgdGhlIGxlZ2l0aW1h
dGUgREhDUCBzZXJ2ZXIgb3IgdGhlIGF1dGhlbnRpY2F0ZWQNCiAgIERIQ1Agc2VydmVyIGNhbiBv
YnRhaW4gdGhlIGNlcnRpZmljYXRlIG9mIHRoZSBESENQIGNsaWVudCBmcm9tIHRoZQ0KICAgdHJ1
c3RlZCBzZXJ2ZXIuIg0KLS0td2h5IHByb3RlY3QgdGhlIGNsaWVudCBjZXJ0aWZpY2F0ZT8NCg0K
c2VjdGlvaW4gNCANCiAgICJXaGVuIERIQ1BPRkZFUiBtZXNzYWdlIGlzIGJyb2FkY2FzdCwgREhD
UCBzZXJ2ZXIgc2VuZHMgdG8gREhDUCBjbGllbnQNCiAgIERIQ1BPRkZFUiBtZXNzYWdlLCB3aGlj
aCBjb250YWlucyB0aGUgcHVibGljIGtleSBvZiBESENQIHNlcnZlciwgdGhlDQogICBjZXJ0aWZp
Y2F0ZSBVUkwgb2YgdGhlIERIQ1Agc2VydmVyIGFuZCB0aGUgc2lnbmF0dXJlIG9mIHRoZSBESENQ
T0ZGRVINCiAgIHdpdGggdGhlIHByaXZhdGUga2V5IG9mIHRoZSBESENQIHNlcnZlci4gIFdoZW4g
REhDUCBjbGllbnQgcmVjZWl2ZXMNCiAgIHRoZSBwdWJsaWMga2V5IG9mIHRoZSBzZXJ2ZXIsIGl0
IGNvbnNpZGVycyB0aGlzIGNlcnRpZmljYXRlIGFzIGENCiAgIHZhbGlkIG9uZSB0ZW1wb3Jhcmls
eS4gIFRoZSBjbGllbnQgYXV0aGVudGljYXRlcyB0aGUgREhDUE9GRkVSIHdpdGgNCiAgIHRoaXMg
REhDUCBwdWJsaWMga2V5IGFuZCBnZXRzIHRoZSBJUCBhZGRyZXNzIGFsbG9jYXRlZCBieSB0aGUg
c2VydmVyLg0KICAgQXQgdGhhdCwgdGhlIGNsaWVudCBhY2hpZXZlcyB0aGUgY2VydGlmaWNhdGUg
b2YgREhDUCBzZXJ2ZXIgd2l0aCB0aGUNCiAgIFVSTCwgYW5kIGNoZWNrcyB3aGV0aGVyIHRoaXMg
Y2VydGlmaWNhdGVzIG1hdGNoIHdpdGggdGhlIHB1YmxpYyBrZXkNCiAgIGNhcnJpZWQgaW4gREhD
UE9GRVIgbWVzc2FnZS4gIElmIHRoZXkgbWF0Y2gsIHRoZSBjbGllbnQgY2FuIGFmZmlybQ0KICAg
dGhlIHZhbGlkaXR5IG9mIHRoZSBzZXJ2ZXIuIg0KICAtLS1pbWFnaW4gdGhlIGZvbGxvd2luZyBh
dHRhY2s6DQogICAgQSByb2d1ZSBzZXJ2ZXIgcHV0IHRoZSBVUkwgb2YgaXRzIGNlcnRpZmNpYXRl
IGluIERIQ1BPRkZFUiwgYW5kIHRoZSANCnNlcnZlciByZWZlcnJlZCB0byBieSB0aGUgVVJMIA0K
aXMgdW5kZXIgdGhlIGNvbnRyb2wgb2YgdGhlIHJvZ3VlIHNlcnZlciwgdGhlbiBjbGllbnQgbWF0
Y2ggdGhlIHB1YmxpYyBrZXkgDQp3aXRoIHRoZSBjZXJ0aWZpY2F0ZSBwcm92aWRlZCBieSANCnRo
ZSByb2d1ZSBzZXJ2ZXIgY29udHJvbGxlZCAgc2VydmVyLCBpdCB3aWxsIGFsd2F5cyBnZXQgYSBt
YXRjaCByZXN1bHQuDQoNCg0KICAtLS1JbWFnaW4gYW5vdGhlciBhdHRhY2ujuiBhbiBlYXZlc2Ry
b3BwZXIgb2J0YWluZWQgREhDUERJU0NPVkVSLCB0aGVuIA0KaXQgc2VuZCB0aGVtIHRvIHRoZSBz
ZXJ2ZXIsDQp0aGUgc2VydmVyIHdpbGwgdmFsaWRhdGUgdGhlIG1lc3NhZ2Vzo6wgdmFsaWQgb2Yg
Y291cnNlLCB0aGVuIHRoZSBzZXJ2ZXIgDQp3aWxsIGFzc2lnbiBJUCBhZGRyZXNzZXMgdG8gdGhl
IHNlbmRlcnMsIHJlc3VsdGluZyANCmEgZGVuaWFsIG9mIHNlcnZpY2UuIA0KDQpSZWdhcmRzfn5+
DQoNCi1TdWppbmcgWmhvdQ0K
--=_alternative 001E60AB48257974_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPmh0dHA6Ly90b29scy5pZXRmLm9y
Zy9odG1sL2RyYWZ0LXh1LWRoYy1jYWRoY3AtMDE8L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6
ZT0yIGZhY2U9InNhbnMtc2VyaWYiPnNlY3Rpb24gMzwvZm9udD4NCjxicj48Zm9udCBzaXplPTIg
ZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwOyZxdW90O0lmIHRoZSBESENQIHNlcnZlcg0K
aXMgYXV0aGVudGljYXRlZCBieSBhIHRydXN0ZWQgc2VydmVyLCB0aGUgREhDUCBzZXJ2ZXI8L2Zv
bnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwOyAmbmJzcDtkb3du
bG9hZHMgdGhlIERIQ1AgY2xpZW50DQpjZXJ0aWZpY2F0ZSBmcm9tIHRoZSB0cnVzdGVkIHNlcnZl
ci5UaGU8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwOyAm
bmJzcDtjZXJ0aWZpY2F0ZSBtYXkgYmUgcHJvdGVjdGVkDQp3aXRoIHRoZSBzZWN1cmUgdHVubmVs
LCBzdWNoIGFzLCBTU0wvPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlm
Ij4mbmJzcDsgJm5ic3A7VExTLCB3aGljaCBlc3RhYmxpc2hlZA0KYmV0d2VlbiB0aGUgREhDUCBz
ZXJ2ZXIgYW5kIHRoZSB0cnVzdGVkPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5z
LXNlcmlmIj4mbmJzcDsgJm5ic3A7c2VydmVyLiAmbmJzcDtUaHJvdWdoIHRoZQ0KYXV0aGVudGlj
YXRpb24gYmV0d2VlbiBESENQIHNlcnZlciBhbmQgdGhlPC9mb250Pg0KPGJyPjxmb250IHNpemU9
MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgJm5ic3A7dHJ1c3RlZCBzZXJ2ZXIsIG9ubHkgdGhl
DQpsZWdpdGltYXRlIERIQ1Agc2VydmVyIG9yIHRoZSBhdXRoZW50aWNhdGVkPC9mb250Pg0KPGJy
Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgJm5ic3A7REhDUCBzZXJ2ZXIg
Y2FuIG9idGFpbg0KdGhlIGNlcnRpZmljYXRlIG9mIHRoZSBESENQIGNsaWVudCBmcm9tIHRoZTwv
Zm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwO3Ry
dXN0ZWQgc2VydmVyLiZxdW90OzwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1z
ZXJpZiI+LS0td2h5IHByb3RlY3QgdGhlIGNsaWVudCBjZXJ0aWZpY2F0ZT88L2ZvbnQ+DQo8YnI+
DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPnNlY3Rpb2luIDQgPC9mb250Pg0K
PGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgJm5ic3A7JnF1b3Q7V2hl
biBESENQT0ZGRVIgbWVzc2FnZQ0KaXMgYnJvYWRjYXN0LCBESENQIHNlcnZlciBzZW5kcyB0byBE
SENQIGNsaWVudDwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5i
c3A7ICZuYnNwO0RIQ1BPRkZFUiBtZXNzYWdlLCB3aGljaA0KY29udGFpbnMgdGhlIHB1YmxpYyBr
ZXkgb2YgREhDUCBzZXJ2ZXIsIHRoZTwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fu
cy1zZXJpZiI+Jm5ic3A7ICZuYnNwO2NlcnRpZmljYXRlIFVSTCBvZiB0aGUNCkRIQ1Agc2VydmVy
IGFuZCB0aGUgc2lnbmF0dXJlIG9mIHRoZSBESENQT0ZGRVI8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6
ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwOyAmbmJzcDt3aXRoIHRoZSBwcml2YXRlIGtleSBv
Zg0KdGhlIERIQ1Agc2VydmVyLiAmbmJzcDtXaGVuIERIQ1AgY2xpZW50IHJlY2VpdmVzPC9mb250
Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgJm5ic3A7dGhlIHB1
YmxpYyBrZXkgb2YgdGhlIHNlcnZlciwNCml0IGNvbnNpZGVycyB0aGlzIGNlcnRpZmljYXRlIGFz
IGE8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwOyAmbmJz
cDt2YWxpZCBvbmUgdGVtcG9yYXJpbHkuDQombmJzcDtUaGUgY2xpZW50IGF1dGhlbnRpY2F0ZXMg
dGhlIERIQ1BPRkZFUiB3aXRoPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNl
cmlmIj4mbmJzcDsgJm5ic3A7dGhpcyBESENQIHB1YmxpYyBrZXkgYW5kDQpnZXRzIHRoZSBJUCBh
ZGRyZXNzIGFsbG9jYXRlZCBieSB0aGUgc2VydmVyLjwvZm9udD4NCjxicj48Zm9udCBzaXplPTIg
ZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwO0F0IHRoYXQsIHRoZSBjbGllbnQgYWNoaWV2
ZXMNCnRoZSBjZXJ0aWZpY2F0ZSBvZiBESENQIHNlcnZlciB3aXRoIHRoZTwvZm9udD4NCjxicj48
Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwO1VSTCwgYW5kIGNoZWNr
cyB3aGV0aGVyDQp0aGlzIGNlcnRpZmljYXRlcyBtYXRjaCB3aXRoIHRoZSBwdWJsaWMga2V5PC9m
b250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgJm5ic3A7Y2Fy
cmllZCBpbiBESENQT0ZFUiBtZXNzYWdlLg0KJm5ic3A7SWYgdGhleSBtYXRjaCwgdGhlIGNsaWVu
dCBjYW4gYWZmaXJtPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4m
bmJzcDsgJm5ic3A7dGhlIHZhbGlkaXR5IG9mIHRoZSBzZXJ2ZXIuJnF1b3Q7PC9mb250Pg0KPGJy
Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgLS0taW1hZ2luIHRoZSBmb2xs
b3dpbmcgYXR0YWNrOjwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+
Jm5ic3A7ICZuYnNwOyBBIHJvZ3VlIHNlcnZlciBwdXQgdGhlDQpVUkwgb2YgaXRzIGNlcnRpZmNp
YXRlIGluIERIQ1BPRkZFUiwgYW5kIHRoZSBzZXJ2ZXIgcmVmZXJyZWQgdG8gYnkgdGhlDQpVUkwg
PC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5pcyB1bmRlciB0aGUg
Y29udHJvbCBvZiB0aGUgcm9ndWUgc2VydmVyLA0KdGhlbiBjbGllbnQgbWF0Y2ggdGhlIHB1Ymxp
YyBrZXkgd2l0aCB0aGUgY2VydGlmaWNhdGUgcHJvdmlkZWQgYnkgPC9mb250Pg0KPGJyPjxmb250
IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj50aGUgcm9ndWUgc2VydmVyIGNvbnRyb2xsZWQgJm5i
c3A7c2VydmVyLA0KaXQgd2lsbCBhbHdheXMgZ2V0IGEgbWF0Y2ggcmVzdWx0LjwvZm9udD4NCjxi
cj4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7IC0tLUlt
YWdpbiBhbm90aGVyIGF0dGFja6O6IGFuDQplYXZlc2Ryb3BwZXIgb2J0YWluZWQgREhDUERJU0NP
VkVSLCB0aGVuIGl0IHNlbmQgdGhlbSB0byB0aGUgc2VydmVyLDwvZm9udD4NCjxicj48Zm9udCBz
aXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+dGhlIHNlcnZlciB3aWxsIHZhbGlkYXRlIHRoZSBtZXNz
YWdlc6OsDQp2YWxpZCBvZiBjb3Vyc2UsIHRoZW4gdGhlIHNlcnZlciB3aWxsIGFzc2lnbiBJUCBh
ZGRyZXNzZXMgdG8gdGhlIHNlbmRlcnMsDQpyZXN1bHRpbmcgPC9mb250Pg0KPGJyPjxmb250IHNp
emU9MiBmYWNlPSJzYW5zLXNlcmlmIj5hIGRlbmlhbCBvZiBzZXJ2aWNlLiA8L2ZvbnQ+DQo8YnI+
DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlJlZ2FyZHN+fn48YnI+DQo8YnI+
DQotU3VqaW5nIFpob3U8L2ZvbnQ+DQo=
--=_alternative 001E60AB48257974_=--


From zhou.sujing@zte.com.cn  Tue Dec 27 21:40:04 2011
Return-Path: <zhou.sujing@zte.com.cn>
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 62F4921F8B0E for <dhcwg@ietfa.amsl.com>; Tue, 27 Dec 2011 21:40:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.962
X-Spam-Level: 
X-Spam-Status: No, score=-100.962 tagged_above=-999 required=5 tests=[AWL=-0.877, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id piiKSQ4bjhvY for <dhcwg@ietfa.amsl.com>; Tue, 27 Dec 2011 21:40:03 -0800 (PST)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id F026E21F8B0C for <dhcwg@ietf.org>; Tue, 27 Dec 2011 21:40:02 -0800 (PST)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 56690262235339; Wed, 28 Dec 2011 13:20:57 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.16] with StormMail ESMTP id 57327.262235339; Wed, 28 Dec 2011 13:39:45 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id pBS5dln9083746 for <dhcwg@ietf.org>; Wed, 28 Dec 2011 13:39:47 +0800 (GMT-8) (envelope-from zhou.sujing@zte.com.cn)
To: dhcwg@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF90EDB28B.0DF91825-ON48257974.001EE72E-48257974.001F1C62@zte.com.cn>
From: zhou.sujing@zte.com.cn
Date: Wed, 28 Dec 2011 13:39:40 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2011-12-28 13:39:48, Serialize complete at 2011-12-28 13:39:48
Content-Type: multipart/alternative; boundary="=_alternative 001F1C6248257974_="
X-MAIL: mse01.zte.com.cn pBS5dln9083746
Subject: [dhcwg] draft-xu-dhc-cadhcp-01
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: Wed, 28 Dec 2011 05:40:04 -0000

This is a multipart message in MIME format.
--=_alternative 001F1C6248257974_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

aHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQteHUtZGhjLWNhZGhjcC0wMQ0Kc2VjdGlv
biAzDQogICAiSWYgdGhlIERIQ1Agc2VydmVyIGlzIGF1dGhlbnRpY2F0ZWQgYnkgYSB0cnVzdGVk
IHNlcnZlciwgdGhlIERIQ1AgDQpzZXJ2ZXINCiAgIGRvd25sb2FkcyB0aGUgREhDUCBjbGllbnQg
Y2VydGlmaWNhdGUgZnJvbSB0aGUgdHJ1c3RlZCBzZXJ2ZXIuVGhlDQogICBjZXJ0aWZpY2F0ZSBt
YXkgYmUgcHJvdGVjdGVkIHdpdGggdGhlIHNlY3VyZSB0dW5uZWwsIHN1Y2ggYXMsIFNTTC8NCiAg
IFRMUywgd2hpY2ggZXN0YWJsaXNoZWQgYmV0d2VlbiB0aGUgREhDUCBzZXJ2ZXIgYW5kIHRoZSB0
cnVzdGVkDQogICBzZXJ2ZXIuICBUaHJvdWdoIHRoZSBhdXRoZW50aWNhdGlvbiBiZXR3ZWVuIERI
Q1Agc2VydmVyIGFuZCB0aGUNCiAgIHRydXN0ZWQgc2VydmVyLCBvbmx5IHRoZSBsZWdpdGltYXRl
IERIQ1Agc2VydmVyIG9yIHRoZSBhdXRoZW50aWNhdGVkDQogICBESENQIHNlcnZlciBjYW4gb2J0
YWluIHRoZSBjZXJ0aWZpY2F0ZSBvZiB0aGUgREhDUCBjbGllbnQgZnJvbSB0aGUNCiAgIHRydXN0
ZWQgc2VydmVyLiINCi0tLXdoeSBwcm90ZWN0IHRoZSBjbGllbnQgY2VydGlmaWNhdGU/DQoNCnNl
Y3Rpb2luIDQgDQogICAiV2hlbiBESENQT0ZGRVIgbWVzc2FnZSBpcyBicm9hZGNhc3QsIERIQ1Ag
c2VydmVyIHNlbmRzIHRvIERIQ1AgY2xpZW50DQogICBESENQT0ZGRVIgbWVzc2FnZSwgd2hpY2gg
Y29udGFpbnMgdGhlIHB1YmxpYyBrZXkgb2YgREhDUCBzZXJ2ZXIsIHRoZQ0KICAgY2VydGlmaWNh
dGUgVVJMIG9mIHRoZSBESENQIHNlcnZlciBhbmQgdGhlIHNpZ25hdHVyZSBvZiB0aGUgREhDUE9G
RkVSDQogICB3aXRoIHRoZSBwcml2YXRlIGtleSBvZiB0aGUgREhDUCBzZXJ2ZXIuICBXaGVuIERI
Q1AgY2xpZW50IHJlY2VpdmVzDQogICB0aGUgcHVibGljIGtleSBvZiB0aGUgc2VydmVyLCBpdCBj
b25zaWRlcnMgdGhpcyBjZXJ0aWZpY2F0ZSBhcyBhDQogICB2YWxpZCBvbmUgdGVtcG9yYXJpbHku
ICBUaGUgY2xpZW50IGF1dGhlbnRpY2F0ZXMgdGhlIERIQ1BPRkZFUiB3aXRoDQogICB0aGlzIERI
Q1AgcHVibGljIGtleSBhbmQgZ2V0cyB0aGUgSVAgYWRkcmVzcyBhbGxvY2F0ZWQgYnkgdGhlIHNl
cnZlci4NCiAgIEF0IHRoYXQsIHRoZSBjbGllbnQgYWNoaWV2ZXMgdGhlIGNlcnRpZmljYXRlIG9m
IERIQ1Agc2VydmVyIHdpdGggdGhlDQogICBVUkwsIGFuZCBjaGVja3Mgd2hldGhlciB0aGlzIGNl
cnRpZmljYXRlcyBtYXRjaCB3aXRoIHRoZSBwdWJsaWMga2V5DQogICBjYXJyaWVkIGluIERIQ1BP
RkVSIG1lc3NhZ2UuICBJZiB0aGV5IG1hdGNoLCB0aGUgY2xpZW50IGNhbiBhZmZpcm0NCiAgIHRo
ZSB2YWxpZGl0eSBvZiB0aGUgc2VydmVyLiINCiAgLS0taW1hZ2luIHRoZSBmb2xsb3dpbmcgYXR0
YWNrOg0KICAgIEEgcm9ndWUgc2VydmVyIHB1dCB0aGUgVVJMIG9mIGl0cyBjZXJ0aWZjaWF0ZSBp
biBESENQT0ZGRVIsIGFuZCB0aGUgDQpzZXJ2ZXIgcmVmZXJyZWQgdG8gYnkgdGhlIFVSTCANCmlz
IHVuZGVyIHRoZSBjb250cm9sIG9mIHRoZSByb2d1ZSBzZXJ2ZXIsIHRoZW4gY2xpZW50IG1hdGNo
IHRoZSBwdWJsaWMga2V5IA0Kd2l0aCB0aGUgY2VydGlmaWNhdGUgcHJvdmlkZWQgYnkgDQp0aGUg
cm9ndWUgc2VydmVyIGNvbnRyb2xsZWQgIHNlcnZlciwgaXQgd2lsbCBhbHdheXMgZ2V0IGEgbWF0
Y2ggcmVzdWx0Lg0KDQoNCiAgIEltYWdpbiBhbm90aGVyIGF0dGFja6O6IGFuIGVhdmVzZHJvcHBl
ciBvYnRhaW5lZCBESENQRElTQ09WRVIsIHRoZW4gaXQgDQpzZW5kIHRoZW0gdG8gdGhlIHNlcnZl
ciwNCnRoZSBzZXJ2ZXIgd2lsbCB2YWxpZGF0ZSB0aGUgbWVzc2FnZXOjrCB2YWxpZCBvZiBjb3Vy
c2UsIHRoZW4gdGhlIHNlcnZlciANCndpbGwgYXNzaWduIElQIGFkZHJlc3NlcyB0byB0aGUgc2Vu
ZGVycywgcmVzdWx0aW5nIA0KYSBkZW5pYWwgb2Ygc2VydmljZS4gDQoNClJlZ2FyZHN+fn4NCg0K
LVN1amluZyBaaG91DQo=
--=_alternative 001F1C6248257974_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPmh0dHA6Ly90b29scy5pZXRmLm9y
Zy9odG1sL2RyYWZ0LXh1LWRoYy1jYWRoY3AtMDE8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZh
Y2U9InNhbnMtc2VyaWYiPnNlY3Rpb24gMzwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0i
c2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwOyZxdW90O0lmIHRoZSBESENQIHNlcnZlcg0KaXMgYXV0
aGVudGljYXRlZCBieSBhIHRydXN0ZWQgc2VydmVyLCB0aGUgREhDUCBzZXJ2ZXI8L2ZvbnQ+DQo8
YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwOyAmbmJzcDtkb3dubG9hZHMg
dGhlIERIQ1AgY2xpZW50DQpjZXJ0aWZpY2F0ZSBmcm9tIHRoZSB0cnVzdGVkIHNlcnZlci5UaGU8
L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwOyAmbmJzcDtj
ZXJ0aWZpY2F0ZSBtYXkgYmUgcHJvdGVjdGVkDQp3aXRoIHRoZSBzZWN1cmUgdHVubmVsLCBzdWNo
IGFzLCBTU0wvPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJz
cDsgJm5ic3A7VExTLCB3aGljaCBlc3RhYmxpc2hlZA0KYmV0d2VlbiB0aGUgREhDUCBzZXJ2ZXIg
YW5kIHRoZSB0cnVzdGVkPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlm
Ij4mbmJzcDsgJm5ic3A7c2VydmVyLiAmbmJzcDtUaHJvdWdoIHRoZQ0KYXV0aGVudGljYXRpb24g
YmV0d2VlbiBESENQIHNlcnZlciBhbmQgdGhlPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNl
PSJzYW5zLXNlcmlmIj4mbmJzcDsgJm5ic3A7dHJ1c3RlZCBzZXJ2ZXIsIG9ubHkgdGhlDQpsZWdp
dGltYXRlIERIQ1Agc2VydmVyIG9yIHRoZSBhdXRoZW50aWNhdGVkPC9mb250Pg0KPGJyPjxmb250
IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgJm5ic3A7REhDUCBzZXJ2ZXIgY2FuIG9i
dGFpbg0KdGhlIGNlcnRpZmljYXRlIG9mIHRoZSBESENQIGNsaWVudCBmcm9tIHRoZTwvZm9udD4N
Cjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwO3RydXN0ZWQg
c2VydmVyLiZxdW90OzwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+
LS0td2h5IHByb3RlY3QgdGhlIGNsaWVudCBjZXJ0aWZpY2F0ZT88L2ZvbnQ+DQo8YnI+DQo8YnI+
PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPnNlY3Rpb2luIDQgPC9mb250Pg0KPGJyPjxm
b250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgJm5ic3A7JnF1b3Q7V2hlbiBESENQ
T0ZGRVIgbWVzc2FnZQ0KaXMgYnJvYWRjYXN0LCBESENQIHNlcnZlciBzZW5kcyB0byBESENQIGNs
aWVudDwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZu
YnNwO0RIQ1BPRkZFUiBtZXNzYWdlLCB3aGljaA0KY29udGFpbnMgdGhlIHB1YmxpYyBrZXkgb2Yg
REhDUCBzZXJ2ZXIsIHRoZTwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJp
ZiI+Jm5ic3A7ICZuYnNwO2NlcnRpZmljYXRlIFVSTCBvZiB0aGUNCkRIQ1Agc2VydmVyIGFuZCB0
aGUgc2lnbmF0dXJlIG9mIHRoZSBESENQT0ZGRVI8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZh
Y2U9InNhbnMtc2VyaWYiPiZuYnNwOyAmbmJzcDt3aXRoIHRoZSBwcml2YXRlIGtleSBvZg0KdGhl
IERIQ1Agc2VydmVyLiAmbmJzcDtXaGVuIERIQ1AgY2xpZW50IHJlY2VpdmVzPC9mb250Pg0KPGJy
Pjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgJm5ic3A7dGhlIHB1YmxpYyBr
ZXkgb2YgdGhlIHNlcnZlciwNCml0IGNvbnNpZGVycyB0aGlzIGNlcnRpZmljYXRlIGFzIGE8L2Zv
bnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwOyAmbmJzcDt2YWxp
ZCBvbmUgdGVtcG9yYXJpbHkuDQombmJzcDtUaGUgY2xpZW50IGF1dGhlbnRpY2F0ZXMgdGhlIERI
Q1BPRkZFUiB3aXRoPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4m
bmJzcDsgJm5ic3A7dGhpcyBESENQIHB1YmxpYyBrZXkgYW5kDQpnZXRzIHRoZSBJUCBhZGRyZXNz
IGFsbG9jYXRlZCBieSB0aGUgc2VydmVyLjwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0i
c2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwO0F0IHRoYXQsIHRoZSBjbGllbnQgYWNoaWV2ZXMNCnRo
ZSBjZXJ0aWZpY2F0ZSBvZiBESENQIHNlcnZlciB3aXRoIHRoZTwvZm9udD4NCjxicj48Zm9udCBz
aXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwO1VSTCwgYW5kIGNoZWNrcyB3aGV0
aGVyDQp0aGlzIGNlcnRpZmljYXRlcyBtYXRjaCB3aXRoIHRoZSBwdWJsaWMga2V5PC9mb250Pg0K
PGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgJm5ic3A7Y2FycmllZCBp
biBESENQT0ZFUiBtZXNzYWdlLg0KJm5ic3A7SWYgdGhleSBtYXRjaCwgdGhlIGNsaWVudCBjYW4g
YWZmaXJtPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsg
Jm5ic3A7dGhlIHZhbGlkaXR5IG9mIHRoZSBzZXJ2ZXIuJnF1b3Q7PC9mb250Pg0KPGJyPjxmb250
IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj4mbmJzcDsgLS0taW1hZ2luIHRoZSBmb2xsb3dpbmcg
YXR0YWNrOjwvZm9udD4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7
ICZuYnNwOyBBIHJvZ3VlIHNlcnZlciBwdXQgdGhlDQpVUkwgb2YgaXRzIGNlcnRpZmNpYXRlIGlu
IERIQ1BPRkZFUiwgYW5kIHRoZSBzZXJ2ZXIgcmVmZXJyZWQgdG8gYnkgdGhlDQpVUkwgPC9mb250
Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5pcyB1bmRlciB0aGUgY29udHJv
bCBvZiB0aGUgcm9ndWUgc2VydmVyLA0KdGhlbiBjbGllbnQgbWF0Y2ggdGhlIHB1YmxpYyBrZXkg
d2l0aCB0aGUgY2VydGlmaWNhdGUgcHJvdmlkZWQgYnkgPC9mb250Pg0KPGJyPjxmb250IHNpemU9
MiBmYWNlPSJzYW5zLXNlcmlmIj50aGUgcm9ndWUgc2VydmVyIGNvbnRyb2xsZWQgJm5ic3A7c2Vy
dmVyLA0KaXQgd2lsbCBhbHdheXMgZ2V0IGEgbWF0Y2ggcmVzdWx0LjwvZm9udD4NCjxicj4NCjxi
cj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7ICZuYnNwO0ltYWdp
biBhbm90aGVyIGF0dGFja6O6DQphbiBlYXZlc2Ryb3BwZXIgb2J0YWluZWQgREhDUERJU0NPVkVS
LCB0aGVuIGl0IHNlbmQgdGhlbSB0byB0aGUgc2VydmVyLDwvZm9udD4NCjxicj48Zm9udCBzaXpl
PTIgZmFjZT0ic2Fucy1zZXJpZiI+dGhlIHNlcnZlciB3aWxsIHZhbGlkYXRlIHRoZSBtZXNzYWdl
c6OsDQp2YWxpZCBvZiBjb3Vyc2UsIHRoZW4gdGhlIHNlcnZlciB3aWxsIGFzc2lnbiBJUCBhZGRy
ZXNzZXMgdG8gdGhlIHNlbmRlcnMsDQpyZXN1bHRpbmcgPC9mb250Pg0KPGJyPjxmb250IHNpemU9
MiBmYWNlPSJzYW5zLXNlcmlmIj5hIGRlbmlhbCBvZiBzZXJ2aWNlLiA8L2ZvbnQ+DQo8YnI+DQo8
YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlJlZ2FyZHN+fn48YnI+DQo8YnI+DQot
U3VqaW5nIFpob3U8L2ZvbnQ+DQo=
--=_alternative 001F1C6248257974_=--


From internet-drafts@ietf.org  Fri Dec 30 02:32:18 2011
Return-Path: <internet-drafts@ietf.org>
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 D18DE21F8B30; Fri, 30 Dec 2011 02:32:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.589
X-Spam-Level: 
X-Spam-Status: No, score=-102.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4qN7ovNBoYtJ; Fri, 30 Dec 2011 02:32:18 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6874821F845A; Fri, 30 Dec 2011 02:32:18 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111230103218.32581.53611.idtracker@ietfa.amsl.com>
Date: Fri, 30 Dec 2011 02:32:18 -0800
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-secure-dhcpv6-04.txt
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: Fri, 30 Dec 2011 10:32:19 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Dynamic Host Configuration Working Gr=
oup of the IETF.

	Title           : Secure DHCPv6 Using CGAs
	Author(s)       : Sheng Jiang
                          Sean Shen
	Filename        : draft-ietf-dhc-secure-dhcpv6-04.txt
	Pages           : 16
	Date            : 2011-12-30

   The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) enables
   DHCP servers to pass configuration parameters. It offers
   configuration flexibility. If not secured, DHCPv6 is vulnerable to
   various attacks, particularly fake attack. This document analyzes the
   security issues of DHCPv6 and specifies security mechanisms, mainly
   using CGAs.




A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-secure-dhcpv6-04.txt

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

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-secure-dhcpv6-04.txt

