
From gvithal@gmail.com  Wed Nov  2 06:23:55 2011
Return-Path: <gvithal@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 C35C121F8D67 for <dhcwg@ietfa.amsl.com>; Wed,  2 Nov 2011 06:23:55 -0700 (PDT)
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 XUC91e0DCUqh for <dhcwg@ietfa.amsl.com>; Wed,  2 Nov 2011 06:23:55 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id B5B8321F8D42 for <dhcwg@ietf.org>; Wed,  2 Nov 2011 06:23:54 -0700 (PDT)
Received: by eyg24 with SMTP id 24so135030eyg.31 for <dhcwg@ietf.org>; Wed, 02 Nov 2011 06:23:53 -0700 (PDT)
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=3J9srHWUORAQk+3DG80WK3MwOXEA6BddaA8onE6N8yg=; b=YCHv5usWMPm9Kfe1VZkO0ROXzv/5CIz39Cw2QBidDKTkWxQ5kQlScZsE79/uoUl0Lb PutUhyVS/Zi4M4FWx/99BfKfa0iBEZgxdVTNzFkt1gHG3ieB2rPw72+8F1GRtWQocTxx DTdSTlGmvZaI3rzcRg5ea+wMci485RWjXPP9U=
MIME-Version: 1.0
Received: by 10.213.27.212 with SMTP id j20mr1704732ebc.65.1320240233806; Wed, 02 Nov 2011 06:23:53 -0700 (PDT)
Received: by 10.213.13.2 with HTTP; Wed, 2 Nov 2011 06:23:53 -0700 (PDT)
In-Reply-To: <CAAfac2i4EaMD5w0tb-6+R7m+ya3AmyfeHRJpaDukRNnUjv6qZw@mail.gmail.com>
References: <CAAfac2h1dE3z0rNqLbQacqzquBAa2S=GkXvs3=O8iZdoy2meRw@mail.gmail.com> <2B0A1E24-4309-4B1E-874B-E7161C212911@nominum.com> <38D1A504-9144-4C88-A188-B02BE4F492F0@viagenie.ca> <1DB05243-3779-409A-86FE-F15133BC0C12@nominum.com> <F377B74F-3A10-4F61-9532-1B89985FC29C@viagenie.ca> <CAAfac2hr+rUCu9CyL607un8i30kvkyEzH_TfNb2OSWgfzcpbrQ@mail.gmail.com> <179BFEB1-ABB9-45A7-BF9C-CE2F8D4DA09D@viagenie.ca> <CAAfac2gsApBfoiqMLM7bwX=LAQO_XkSSCBJ71N39pFGZzAo9BQ@mail.gmail.com> <55D5BCA7-3D6D-4757-861E-F712146463CE@viagenie.ca> <CAAfac2i4EaMD5w0tb-6+R7m+ya3AmyfeHRJpaDukRNnUjv6qZw@mail.gmail.com>
Date: Wed, 2 Nov 2011 18:53:53 +0530
Message-ID: <CAAfac2jiuymXa7J44dZjYFXuugYYNGUETmyQQOsT8+bmKTcFHg@mail.gmail.com>
From: VithalPrasad Gaitonde <gvithal@gmail.com>
To: Marc Blanchet <marc.blanchet@viagenie.ca>
Content-Type: multipart/alternative; boundary=0015174c37d2277cd004b0c062ec
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Character Encoding of DNS domain option (option 15) RFC 2132
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, 02 Nov 2011 13:23:55 -0000

--0015174c37d2277cd004b0c062ec
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Marc, Ted,

Can you please respond to the below.

Thanks,
Prasad

On Mon, Oct 31, 2011 at 6:43 PM, VithalPrasad Gaitonde <gvithal@gmail.com>w=
rote:

> Thanks Marc. Would the same apply to the Domain Name field in option 81
> defined in RFC 4702 as well.
>
> Prasad
>
> On Fri, Oct 28, 2011 at 6:06 PM, Marc Blanchet <marc.blanchet@viagenie.ca=
>wrote:
>
>>
>> Le 2011-10-28 =E0 04:22, VithalPrasad Gaitonde a =E9crit :
>>
>> > Thanks for the responses, Marc, Ted.
>> >
>> > Does that imply then that in case internationalized domain names,
>> punycode should be used ?
>>
>> punycode encoding is used for internationalized domain names. the
>> punycode encoded idn conforms to the restricted ascii. So from dhcp, dns=
,
>> ... point of view, an idn is just a regular domain name. therefore, the
>> dhcp option should have restricted ascii, whatever the domain name is a
>> normal one or an idn.
>>
>> Marc.
>>
>>
>> >
>> > Regards,
>> > Prasad
>> >
>> > On Fri, Oct 28, 2011 at 12:05 AM, Marc Blanchet <
>> marc.blanchet@viagenie.ca> wrote:
>> > to me, you are just looking into big troubles if you use a character
>> encoding for DNS names in DHCP that is different than the standardized
>> character encoding for DNS names everywhere else. so I would stick to
>> restricted ascii. no utf8. nothing else.
>> >
>> > Marc.
>> >
>> > Le 2011-10-27 =E0 13:01, VithalPrasad Gaitonde a =E9crit :
>> >
>> > > I am still a bit confused here...
>> > > To ensure interoperability with standards compliant DHCP clients,
>> what is the character encoding that the server should use...and the
>> converse.
>> > >
>> > > Or are we saying that interoperability is broken here as the standar=
d
>> is silent on the issue leaving implementations to take a possibly differ=
ent
>> approach and thereby be non-interoperable.
>> > >
>> > > Thanks,
>> > > Prasad
>> > >
>> > >
>> > > On Mon, Oct 24, 2011 at 1:19 AM, Marc Blanchet <
>> marc.blanchet@viagenie.ca> wrote:
>> > > I read it, but maybe I misunderstood. Anyway, back to the original
>> question, my point is that the character encoding of DNS domain option i=
n
>> dhcp must be restricted ascii (and that includes the support of idn).
>> > >
>> > > Marc.
>> > >
>> > > Le 2011-10-23 =E0 15:36, Ted Lemon a =E9crit :
>> > >
>> > > > On Oct 23, 2011, at 3:30 PM, Marc Blanchet wrote:
>> > > >> don't agree about UTF-8. idns are encoded on the wire as normal
>> domain names, i.e. restricted ascii.
>> > > >
>> > > > Clearly you didn't read what I said in the first paragraph.   :)
>> As you say, for DNS you can't use UTF-8.
>> > > >
>> > >
>> > >
>> >
>> >
>>
>>
>

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

<div>Hi Marc, Ted,</div><div>=A0</div><div>Can you please respond to the be=
low.</div><div>=A0</div><div>Thanks,</div><div>Prasad<br><br></div><div cla=
ss=3D"gmail_quote">On Mon, Oct 31, 2011 at 6:43 PM, VithalPrasad Gaitonde <=
span dir=3D"ltr">&lt;<a href=3D"mailto:gvithal@gmail.com">gvithal@gmail.com=
</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; paddi=
ng-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px=
; border-left-style: solid;"><div>Thanks Marc. Would the same apply to the =
Domain Name field in option 81 defined in RFC 4702 as well.</div>
<div>=A0</div><div>Prasad<br><br></div><div><div></div><div class=3D"h5"><d=
iv class=3D"gmail_quote">On Fri, Oct 28, 2011 at 6:06 PM, Marc Blanchet <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:marc.blanchet@viagenie.ca" target=3D"_=
blank">marc.blanchet@viagenie.ca</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; paddi=
ng-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px=
; border-left-style: solid;"><br>
Le 2011-10-28 =E0 04:22, VithalPrasad Gaitonde a =E9crit :<br>
<div><br>
&gt; Thanks for the responses, Marc, Ted.<br>
&gt;<br>
&gt; Does that imply then that in case internationalized domain names, puny=
code should be used ?<br>
<br>
</div>punycode encoding is used for internationalized domain names. the pun=
ycode encoded idn conforms to the restricted ascii. So from dhcp, dns, ... =
point of view, an idn is just a regular domain name. therefore, the dhcp op=
tion should have restricted ascii, whatever the domain name is a normal one=
 or an idn.<br>


<font color=3D"#888888"><br>
Marc.<br>
</font><div><div></div><div><br>
<br>
&gt;<br>
&gt; Regards,<br>
&gt; Prasad<br>
&gt;<br>
&gt; On Fri, Oct 28, 2011 at 12:05 AM, Marc Blanchet &lt;<a href=3D"mailto:=
marc.blanchet@viagenie.ca" target=3D"_blank">marc.blanchet@viagenie.ca</a>&=
gt; wrote:<br>
&gt; to me, you are just looking into big troubles if you use a character e=
ncoding for DNS names in DHCP that is different than the standardized chara=
cter encoding for DNS names everywhere else. so I would stick to restricted=
 ascii. no utf8. nothing else.<br>


&gt;<br>
&gt; Marc.<br>
&gt;<br>
&gt; Le 2011-10-27 =E0 13:01, VithalPrasad Gaitonde a =E9crit :<br>
&gt;<br>
&gt; &gt; I am still a bit confused here...<br>
&gt; &gt; To ensure interoperability with standards compliant DHCP clients,=
 what is the character encoding that the server should use...and the conver=
se.<br>
&gt; &gt;<br>
&gt; &gt; Or are we saying that interoperability is broken here as the stan=
dard is silent on the issue leaving implementations to take a possibly diff=
erent approach and thereby be non-interoperable.<br>
&gt; &gt;<br>
&gt; &gt; Thanks,<br>
&gt; &gt; Prasad<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; On Mon, Oct 24, 2011 at 1:19 AM, Marc Blanchet &lt;<a href=3D"mai=
lto:marc.blanchet@viagenie.ca" target=3D"_blank">marc.blanchet@viagenie.ca<=
/a>&gt; wrote:<br>
&gt; &gt; I read it, but maybe I misunderstood. Anyway, back to the origina=
l question, my point is that the character encoding of DNS domain option in=
 dhcp must be restricted ascii (and that includes the support of idn).<br>


&gt; &gt;<br>
&gt; &gt; Marc.<br>
&gt; &gt;<br>
&gt; &gt; Le 2011-10-23 =E0 15:36, Ted Lemon a =E9crit :<br>
&gt; &gt;<br>
&gt; &gt; &gt; On Oct 23, 2011, at 3:30 PM, Marc Blanchet wrote:<br>
&gt; &gt; &gt;&gt; don&#39;t agree about UTF-8. idns are encoded on the wir=
e as normal domain names, i.e. restricted ascii.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Clearly you didn&#39;t read what I said in the first paragra=
ph. =A0 :) =A0 As you say, for DNS you can&#39;t use UTF-8.<br>
&gt; &gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt;<br>
&gt;<br>
<br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>

--0015174c37d2277cd004b0c062ec--

From Ted.Lemon@nominum.com  Wed Nov  2 13:34:21 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 2C71E11E8157 for <dhcwg@ietfa.amsl.com>; Wed,  2 Nov 2011 13:34:21 -0700 (PDT)
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 Fvw-Db-uQEdJ for <dhcwg@ietfa.amsl.com>; Wed,  2 Nov 2011 13:34:20 -0700 (PDT)
Received: from exprod7og127.obsmtp.com (exprod7og127.obsmtp.com [64.18.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 82CF811E80BC for <dhcwg@ietf.org>; Wed,  2 Nov 2011 13:34:19 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob127.postini.com ([64.18.6.12]) with SMTP;  Wed, 02 Nov 2011 13:34:19 PDT
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 AB8F31B824C for <dhcwg@ietf.org>; Wed,  2 Nov 2011 13:34:18 -0700 (PDT)
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 9D2B7190052 for <dhcwg@ietf.org>; Wed,  2 Nov 2011 13:34:18 -0700 (PDT) (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.0323.003; Wed, 2 Nov 2011 13:34:18 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<dhcwg@ietf.org> WG" <dhcwg@ietf.org>
Thread-Topic: IETF 82 Agenda
Thread-Index: AQHMmZ7LENFIRjPkh0SKIjcXvaUWTg==
Date: Wed, 2 Nov 2011 20:34:18 +0000
Message-ID: <0EA10484-1946-457F-AEE2-CE4A7C8B6A71@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: multipart/alternative; boundary="_000_0EA104841946457FAEE2CE4A7C8B6A71nominumcom_"
MIME-Version: 1.0
Subject: [dhcwg] IETF 82 Agenda
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, 02 Nov 2011 20:34:21 -0000

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

I just uploaded the agenda, which is quite short.   I think I must have mis=
sed some submissions, but I can't find them.   If you think you're on the a=
genda, please check.

Thanks!

http://www.ietf.org/proceedings/82/agenda/dhc.html


--_000_0EA104841946457FAEE2CE4A7C8B6A71nominumcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <C1FD2937E99A5D4AB6404C4BFD01FEBA@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; ">
I just uploaded the agenda, which is quite short. &nbsp; I think I must hav=
e missed some submissions, but I can't find them. &nbsp; If you think you'r=
e on the agenda, please check.
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div><a href=3D"http://www.ietf.org/proceedings/82/agenda/dhc.html">http://=
www.ietf.org/proceedings/82/agenda/dhc.html</a></div>
<div><br>
</div>
</body>
</html>

--_000_0EA104841946457FAEE2CE4A7C8B6A71nominumcom_--

From tomasz.mrugalski@gmail.com  Thu Nov  3 14:01:31 2011
Return-Path: <tomasz.mrugalski@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 7349C1F0CA9 for <dhcwg@ietfa.amsl.com>; Thu,  3 Nov 2011 14:01:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.556
X-Spam-Level: 
X-Spam-Status: No, score=-3.556 tagged_above=-999 required=5 tests=[AWL=0.043,  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 wAjzkPf-bgJW for <dhcwg@ietfa.amsl.com>; Thu,  3 Nov 2011 14:01:31 -0700 (PDT)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id B4B6E1F0C6F for <dhcwg@ietf.org>; Thu,  3 Nov 2011 14:01:27 -0700 (PDT)
Received: by wwi36 with SMTP id 36so1731584wwi.13 for <dhcwg@ietf.org>; Thu, 03 Nov 2011 14:01:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=rC4KFWpyM1lgkBQ/DKeopc5Dp/EAyx6wZaoWKRZj59g=; b=iLUZf0kY1328BFg9HGNsVQHAX42boh2/tPzlH582T4HeWygyKHum14go0Idh7gu4y1 4sRRFs3HtFY8wU8SvZiJyvgmQHVm5H2GP4nwWqQfxGVkC3AmCk5r3rPORKNgi3dh+W3B dSsRH13/ENld7yovvJJfboOhA+lyBxKOsFuU4=
Received: by 10.227.208.71 with SMTP id gb7mr14048394wbb.7.1320354083719; Thu, 03 Nov 2011 14:01:23 -0700 (PDT)
Received: from MacBook-Tomasz-Mrugalski.local (host-109-107-11-157.ip.jarsat.pl. [109.107.11.157]) by mx.google.com with ESMTPS id fy13sm12372988wbb.18.2011.11.03.14.01.21 (version=SSLv3 cipher=OTHER); Thu, 03 Nov 2011 14:01:22 -0700 (PDT)
Message-ID: <4EB30120.9010007@gmail.com>
Date: Thu, 03 Nov 2011 22:01:20 +0100
From: Tomasz Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <0EA10484-1946-457F-AEE2-CE4A7C8B6A71@nominum.com>
In-Reply-To: <0EA10484-1946-457F-AEE2-CE4A7C8B6A71@nominum.com>
X-Enigmail-Version: 1.3.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] IETF 82 Agenda
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, 03 Nov 2011 21:01:31 -0000

On 11-11-02 21:34, Ted Lemon wrote:
> I just uploaded the agenda, which is quite short.   I think I must have
> missed some submissions, but I can't find them.   If you think you're on
> the agenda, please check.
> 
> Thanks!
> 
> http://www.ietf.org/proceedings/82/agenda/dhc.html
Ted,
I can present following things. Please add them to the agenda, if you
believe they are worthy topics for discussion.

1. Post-WGLC status of Redundancy Considerations draft
Not sure if that presentation is required. Changes are rather editorial,
with one substantial clarification.
Draft: draft-ietf-dhc-dhcpv6-redundancy-consider-02
Time slot: 5 minutes

2. DHCPv6 suboptions clarification draft.
Draft: draft-mrugalski-dhc-dhcpv6-suboptions-02
There was strong support that this clarification draft is needed.
Unfortunately, there's no concensus on how proceed with this. This
presentation will be a summary of current opinions and a request for
guideance regarding next steps.
Time slot: 5 minutes

3. DHCPv6 route options draft.
Draft: draft-ietf-mif-dhcpv6-route-option-03
I'd like to summarize WGLC that is in progress in MIF and will conclude
before Taipei. In particular, I'd like to discuss author's proposal
regarding DHCP preference over RA. It was presented in DHC already, but
routing configuration is an important topic, so I'd like to present it
once more.
Time slot: 5 minutes

Cheers,
Tomek


From Ted.Lemon@nominum.com  Thu Nov  3 15:38:30 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 8B4481F0C9F for <dhcwg@ietfa.amsl.com>; Thu,  3 Nov 2011 15:38:30 -0700 (PDT)
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.061, 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 WZVW5BLu6BMO for <dhcwg@ietfa.amsl.com>; Thu,  3 Nov 2011 15:38:30 -0700 (PDT)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id C2D6C1F0C59 for <dhcwg@ietf.org>; Thu,  3 Nov 2011 15:38:29 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP;  Thu, 03 Nov 2011 15:38:29 PDT
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 E56231B8286 for <dhcwg@ietf.org>; Thu,  3 Nov 2011 15:38:19 -0700 (PDT)
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 D721D190052; Thu,  3 Nov 2011 15:38:19 -0700 (PDT) (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.0323.003; Thu, 3 Nov 2011 15:38:20 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Tomasz Mrugalski <tomasz.mrugalski@gmail.com>
Thread-Topic: [dhcwg] IETF 82 Agenda
Thread-Index: AQHMmZ7LENFIRjPkh0SKIjcXvaUWTpWcGZMAgAAbGAA=
Date: Thu, 3 Nov 2011 22:38:19 +0000
Message-ID: <B7AF7042-E39A-483E-9588-AB8254199A5E@nominum.com>
References: <0EA10484-1946-457F-AEE2-CE4A7C8B6A71@nominum.com> <4EB30120.9010007@gmail.com>
In-Reply-To: <4EB30120.9010007@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: text/plain; charset="Windows-1252"
Content-ID: <F1B7CCD9C33CC64BBADDD553D9680950@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Subject: Re: [dhcwg] IETF 82 Agenda
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, 03 Nov 2011 22:38:30 -0000

These all look like good items for review/discussion.   Present them in the=
 way that makes the most sense to you=97I don't personally mind non-powerpo=
int agenda items.   :)


From Ted.Lemon@nominum.com  Thu Nov  3 21:27:08 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 6CCB011E8073 for <dhcwg@ietfa.amsl.com>; Thu,  3 Nov 2011 21:27:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.539
X-Spam-Level: 
X-Spam-Status: No, score=-106.539 tagged_above=-999 required=5 tests=[AWL=0.059, 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 eJn7U8hOl-2I for <dhcwg@ietfa.amsl.com>; Thu,  3 Nov 2011 21:27:07 -0700 (PDT)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by ietfa.amsl.com (Postfix) with ESMTP id B169611E8081 for <dhcwg@ietf.org>; Thu,  3 Nov 2011 21:27:06 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP;  Thu, 03 Nov 2011 21:27:06 PDT
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 4662F1B8283 for <dhcwg@ietf.org>; Thu,  3 Nov 2011 21:26:59 -0700 (PDT)
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 ABCBF190052 for <dhcwg@ietf.org>; Thu,  3 Nov 2011 21:26:56 -0700 (PDT) (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.0323.003; Thu, 3 Nov 2011 21:26:56 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<dhcwg@ietf.org> WG" <dhcwg@ietf.org>
Thread-Topic: Updated agenda...
Thread-Index: AQHMmqn8h27rEknIoUae5bRCT2E29A==
Date: Fri, 4 Nov 2011 04:26:55 +0000
Message-ID: <B119FB58-FD50-41B5-813B-C8BD5F114BBE@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: multipart/alternative; boundary="_000_B119FB58FD5041B5813BC8BD5F114BBEnominumcom_"
MIME-Version: 1.0
Subject: [dhcwg] Updated agenda...
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, 04 Nov 2011 04:27:08 -0000

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

I uploaded a new agenda earlier today that I think covers all the requested=
 presentations.   Please let me know if you think you should be on it and a=
ren't!

http://tools.ietf.org/wg/dhc/agenda


--_000_B119FB58FD5041B5813BC8BD5F114BBEnominumcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <365881DB9ABEF749822FAC526B1B9DC1@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; ">
I uploaded a new agenda earlier today that I think covers all the requested=
 presentations. &nbsp; Please let me know if you think you should be on it =
and aren't!
<div><br>
</div>
<div><a href=3D"http://tools.ietf.org/wg/dhc/agenda">http://tools.ietf.org/=
wg/dhc/agenda</a></div>
<div><br>
</div>
</body>
</html>

--_000_B119FB58FD5041B5813BC8BD5F114BBEnominumcom_--

From gvithal@gmail.com  Fri Nov  4 01:29:49 2011
Return-Path: <gvithal@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 6C71D21F8C0E for <dhcwg@ietfa.amsl.com>; Fri,  4 Nov 2011 01:29:49 -0700 (PDT)
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 ROz6hsePLGkb for <dhcwg@ietfa.amsl.com>; Fri,  4 Nov 2011 01:29:48 -0700 (PDT)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id D771D21F8C10 for <dhcwg@ietf.org>; Fri,  4 Nov 2011 01:29:47 -0700 (PDT)
Received: by eyg24 with SMTP id 24so2138475eyg.31 for <dhcwg@ietf.org>; Fri, 04 Nov 2011 01:29:47 -0700 (PDT)
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 :content-type; bh=8gFX9Xw1iIbZaptDYG/WQOjnDF8cmHiIpU6yS44AJqM=; b=e6kEKi9YXKsD+NlJZ6x2M+zlaTK0n2mrbzzFKuDlm9p5Ynpja3IflGi6+Eq9CIsoHc Qe7E9i0sw7tcj7ExDu6LjiNj21jKabCbg3veJ3pSlE2nhm9Z4NDmkkenT61AV+xR+8vY 22KuMJqONE52ZoOgzhF9HFdceXVfDMayp0tbY=
MIME-Version: 1.0
Received: by 10.213.4.75 with SMTP id 11mr147918ebq.27.1320395385207; Fri, 04 Nov 2011 01:29:45 -0700 (PDT)
Received: by 10.213.13.2 with HTTP; Fri, 4 Nov 2011 01:29:45 -0700 (PDT)
In-Reply-To: <20111024165031.21695.5842.idtracker@ietfa.amsl.com>
References: <20111024165031.21695.5842.idtracker@ietfa.amsl.com>
Date: Fri, 4 Nov 2011 13:59:45 +0530
Message-ID: <CAAfac2jr1PgvNLYjidLeXYSUymy75r7hORoGLoe=Y3vmo3FQsw@mail.gmail.com>
From: VithalPrasad Gaitonde <gvithal@gmail.com>
To: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary=0015174c128ae5fb4c04b0e48184
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-failover-requirements-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, 04 Nov 2011 08:29:49 -0000

--0015174c128ae5fb4c04b0e48184
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Tomasz, Kim,

Below are my comments on the DHCPv6 failover. Some of the comments may be
more pertinent to the design.


1.       Configuration synchronization had been left out of the purview of
the DHCP6 failover requirements document on the same lines as the DHCPv4
failover document. While the desire to keep the document simple is
understandable, configuration synchronization is a critical element of a
functional failover so that an administrator can manage the failover
subnet(s) as one logical unit instead of having to make identical changes
on 2 different servers.

        It will be good to call this out as a requirement in the document.



2.       There is a scenario where the DHCP server may be configured to
serve clients on one network adapter and communicate with partner server
(server-2-server traffic) on a different network adapter. In this scenario,
if the server loses connectivity on the network adapter used to communicate
with the clients because of network adapter (hardware) failure, there is no
intimation of the loss of service to the partner in the DHCPv4 failover
protocol. Since the servers are able to communicate with each other, the
partner remains ignorant of the loss of service to clients. This scenario
needs to be addressed to ensure high availability in case of network
adapter failure.



3.       In the partner down scenario, when both servers operate in partner
down, there is a chance of duplicate addresses on the network. This leads
to a potential conflict (unresponsive) state when they re-establish
contact. The duplicate address issue can be postponed to a large extent by
the servers giving new leases from your own pool before giving new leases
from partner=92s pool.



4.       In case of hot standby (Active-Passive) model, while majority of
addresses are owned by the primary server, secondary server will need a
portion of addresses to serve new clients while operating in
communication-interrupted state as also in partner down state before it can
take over the entire address pool (expiry of MCLT). The concept of a
percentage of IP address pool reserved for the secondary for handing out
new leases during failover needs to be captured in the information model of
the protocol.



5.       Unlike many other IETF documents,  the DHCPv4 failover document
did not clearly callout the information model in the document. IMHO, the
DHCPv6 document should call out the information model which should be
designed to cater to both the high availability as well as failover
monitoring aspects.

Thanks,
Prasad

On Mon, Oct 24, 2011 at 10:20 PM, <internet-drafts@ietf.org> wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This draft is a work item of the Dynamic Host Configuration
> Working Group of the IETF.
>
>        Title           : DHCPv6 Failover Requirements
>        Author(s)       : Tomasz Mrugalski
>                          Kim Kinnear
>        Filename        : draft-ietf-dhc-dhcpv6-failover-requirements-00.t=
xt
>        Pages           : 19
>        Date            : 2011-10-18
>
>   The DHCPv6 protocol, defined in [RFC3315] allows for multiple servers
>   to operate on a single network, however it does not define any way to
>   decide which server responds to which client queries.  Some sites are
>   interested in running multiple servers in such a way as to provide
>   increased availability in case of server failure.  In order for this
>   to work reliably, the cooperating primary and secondary servers must
>   maintain a consistent database of the lease information.  [RFC3315]
>   allows for but does not define any redundancy or failover mechanisms.
>   This document outlines requirements for DHCPv6 failover, enumerates
>   related problems, and discusses the proposed scope of work to be
>   conducted.  This document does not define a DHCPv6 failover protocol.
>
>
> A URL for this Internet-Draft is:
>
> http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-failover-requir=
ements-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-failover-require=
ments-00.txt
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>

--0015174c128ae5fb4c04b0e48184
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<div>Hi Tomasz, Kim,</div><div>=A0</div><div>Below are my comments on the D=
HCPv6 failover. Some of the comments may be more pertinent=A0to the=A0desig=
n.</div><div>=A0</div><div><font size=3D"3" face=3D"Times New Roman">

</font><p class=3D"MsoListParagraph" style=3D"margin: 0cm 0cm 0pt 36pt; tex=
t-indent: -18pt; mso-list: l0 level1 lfo1;"><span style=3D"color: rgb(31, 7=
3, 125); font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size=
: 11pt; mso-fareast-font-family: Calibri;"><span style=3D"mso-list: Ignore;=
">1.<span style=3D"font: 7pt/normal &quot;Times New Roman&quot;; font-size-=
adjust: none; font-stretch: normal;">=A0=A0=A0=A0=A0=A0
</span></span></span><span style=3D"color: rgb(31, 73, 125); font-family: &=
quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt;">Configuration =
synchronization had been left out of the purview
of the DHCP6 failover requirements document on the same lines as the DHCPv4=
 failover document.
While the desire to keep the document simple is understandable, configurati=
on synchronization is a critical element of a functional failover so that a=
n administrator can manage the failover subnet(s) as one logical unit inste=
ad of having to make identical changes on 2 different servers. </span></p>
<p class=3D"MsoListParagraph" style=3D"margin: 0cm 0cm 0pt 36pt; text-inden=
t: -18pt; mso-list: l0 level1 lfo1;"><span style=3D"color: rgb(31, 73, 125)=
; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt;=
">=A0=A0=A0=A0=A0=A0=A0 It will be good to call=A0this out=A0as a requireme=
nt in the
document.</span></p><p class=3D"MsoListParagraph" style=3D"margin: 0cm 0cm =
0pt 36pt; text-indent: -18pt; mso-list: l0 level1 lfo1;"><span style=3D"col=
or: rgb(31, 73, 125); font-family: &quot;Calibri&quot;,&quot;sans-serif&quo=
t;; font-size: 11pt;"></span>=A0</p>
<font size=3D"3" face=3D"Times New Roman">

</font><p class=3D"MsoListParagraph" style=3D"margin: 0cm 0cm 0pt 36pt; tex=
t-indent: -18pt; mso-list: l0 level1 lfo1;"><span style=3D"color: rgb(31, 7=
3, 125); font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size=
: 11pt; mso-fareast-font-family: Calibri;"><span style=3D"mso-list: Ignore;=
">2.<span style=3D"font: 7pt/normal &quot;Times New Roman&quot;; font-size-=
adjust: none; font-stretch: normal;">=A0=A0=A0=A0=A0=A0
</span></span></span><span style=3D"color: rgb(31, 73, 125); font-family: &=
quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt;">There is a sce=
nario where the DHCP server may be configured to
serve clients on one=A0network adapter=A0and communicate with partner serve=
r (server-2-server
traffic) on a different network adapter. In this scenario, if the server lo=
ses connectivity
on the=A0network adapter=A0used to communicate with the clients because of=
=A0network adapter=A0(hardware) failure, there
is no intimation of the loss of service to the partner in the DHCPv4 failov=
er protocol.
Since the servers are able to communicate with each other, the partner rema=
ins
ignorant of the loss of service to clients. This scenario needs to be addre=
ssed to ensure high availability in case of network adapter failure.</span>=
</p><p class=3D"MsoListParagraph" style=3D"margin: 0cm 0cm 0pt 36pt; text-i=
ndent: -18pt; mso-list: l0 level1 lfo1;">
<span style=3D"color: rgb(31, 73, 125); font-family: &quot;Calibri&quot;,&q=
uot;sans-serif&quot;; font-size: 11pt;"></span>=A0</p><font size=3D"3" face=
=3D"Times New Roman">

</font><p class=3D"MsoListParagraph" style=3D"margin: 0cm 0cm 0pt 36pt; tex=
t-indent: -18pt; mso-list: l0 level1 lfo1;"><span style=3D"color: rgb(31, 7=
3, 125); font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size=
: 11pt; mso-fareast-font-family: Calibri;"><span style=3D"mso-list: Ignore;=
">3.<span style=3D"font: 7pt/normal &quot;Times New Roman&quot;; font-size-=
adjust: none; font-stretch: normal;">=A0=A0=A0=A0=A0=A0
</span></span></span><span style=3D"color: rgb(31, 73, 125); font-family: &=
quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt;">In the partner=
 down scenario, when both servers operate in
partner down, there is a chance of duplicate addresses on the network. This
leads to a potential conflict (unresponsive) state when they re-establish
contact. The duplicate address issue can be postponed to a large extent by =
the
servers giving new leases from your own pool before giving new leases from
partner=92s pool.</span></p><p class=3D"MsoListParagraph" style=3D"margin: =
0cm 0cm 0pt 36pt; text-indent: -18pt; mso-list: l0 level1 lfo1;"><span styl=
e=3D"color: rgb(31, 73, 125); font-family: &quot;Calibri&quot;,&quot;sans-s=
erif&quot;; font-size: 11pt;"></span>=A0</p>
<font size=3D"3" face=3D"Times New Roman">

</font><p class=3D"MsoListParagraph" style=3D"margin: 0cm 0cm 0pt 36pt; tex=
t-indent: -18pt; mso-list: l0 level1 lfo1;"><span style=3D"color: rgb(31, 7=
3, 125); font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size=
: 11pt; mso-fareast-font-family: Calibri;"><span style=3D"mso-list: Ignore;=
">4.<span style=3D"font: 7pt/normal &quot;Times New Roman&quot;; font-size-=
adjust: none; font-stretch: normal;">=A0=A0=A0=A0=A0=A0
</span></span></span><span style=3D"color: rgb(31, 73, 125); font-family: &=
quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt;">In case of hot=
 standby (Active-Passive) model, while majority of addresses are owned by t=
he primary server, secondary server will need a portion of addresses to ser=
ve new clients while operating in communication-interrupted state as also i=
n partner down state before it can take over the entire address pool (expir=
y of MCLT). The concept of a
percentage of IP address pool reserved for the secondary for handing out ne=
w leases during failover needs to be captured in the information model of t=
he protocol.</span></p><p class=3D"MsoListParagraph" style=3D"margin: 0cm 0=
cm 0pt 36pt; text-indent: -18pt; mso-list: l0 level1 lfo1;">
<span style=3D"color: rgb(31, 73, 125); font-family: &quot;Calibri&quot;,&q=
uot;sans-serif&quot;; font-size: 11pt;"></span>=A0</p><font size=3D"3" face=
=3D"Times New Roman">

</font><p class=3D"MsoListParagraph" style=3D"margin: 0cm 0cm 0pt 36pt; tex=
t-indent: -18pt; mso-list: l0 level1 lfo1;"><span style=3D"color: rgb(31, 7=
3, 125); font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; font-size=
: 11pt; mso-fareast-font-family: Calibri;"><span style=3D"mso-list: Ignore;=
">5.<span style=3D"font: 7pt/normal &quot;Times New Roman&quot;; font-size-=
adjust: none; font-stretch: normal;">=A0=A0=A0=A0=A0=A0
</span></span></span><span style=3D"color: rgb(31, 73, 125); font-family: &=
quot;Calibri&quot;,&quot;sans-serif&quot;; font-size: 11pt;">Unlike many ot=
her IETF documents, =A0the DHCPv4 failover document
did not clearly callout the information model in the document. IMHO, the DH=
CPv6 document
should call out the information model which should be designed to cater to =
both
the high availability as well as failover monitoring aspects.</span></p><fo=
nt size=3D"3" face=3D"Times New Roman">

</font></div><div>=A0</div><div>Thanks,</div><div>Prasad<br><br></div><div =
class=3D"gmail_quote">On Mon, Oct 24, 2011 at 10:20 PM,  <span dir=3D"ltr">=
&lt;<a href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a=
>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; paddi=
ng-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px=
; border-left-style: solid;">A New Internet-Draft is available from the on-=
line Internet-Drafts directories. This draft is a work item of the Dynamic =
Host Configuration Working Group of the IETF.<br>

<br>
 =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : DHCPv6 Failover Requirements<br=
>
 =A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : Tomasz Mrugalski<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Kim Kinnear<br>
 =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-ietf-dhc-dhcpv6-failover-re=
quirements-00.txt<br>
 =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 19<br>
 =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2011-10-18<br>
<br>
 =A0 The DHCPv6 protocol, defined in [RFC3315] allows for multiple servers<=
br>
 =A0 to operate on a single network, however it does not define any way to<=
br>
 =A0 decide which server responds to which client queries. =A0Some sites ar=
e<br>
 =A0 interested in running multiple servers in such a way as to provide<br>
 =A0 increased availability in case of server failure. =A0In order for this=
<br>
 =A0 to work reliably, the cooperating primary and secondary servers must<b=
r>
 =A0 maintain a consistent database of the lease information. =A0[RFC3315]<=
br>
 =A0 allows for but does not define any redundancy or failover mechanisms.<=
br>
 =A0 This document outlines requirements for DHCPv6 failover, enumerates<br=
>
 =A0 related problems, and discusses the proposed scope of work to be<br>
 =A0 conducted. =A0This document does not define a DHCPv6 failover protocol=
.<br>
<br>
<br>
A URL for this Internet-Draft is:<br>
<a href=3D"http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-failov=
er-requirements-00.txt" target=3D"_blank">http://www.ietf.org/internet-draf=
ts/draft-ietf-dhc-dhcpv6-failover-requirements-00.txt</a><br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<br>
This Internet-Draft can be retrieved at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-failove=
r-requirements-00.txt" target=3D"_blank">ftp://ftp.ietf.org/internet-drafts=
/draft-ietf-dhc-dhcpv6-failover-requirements-00.txt</a><br>
_______________________________________________<br>
dhcwg mailing list<br>
<a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dhcwg" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/dhcwg</a><br>
</blockquote></div><br>

--0015174c128ae5fb4c04b0e48184--

From rdroms.ietf@gmail.com  Fri Nov  4 04:33:49 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 5D93D21F8C16 for <dhcwg@ietfa.amsl.com>; Fri,  4 Nov 2011 04:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.437
X-Spam-Level: 
X-Spam-Status: No, score=-103.437 tagged_above=-999 required=5 tests=[AWL=0.162, 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 ducmrnpCuDeY for <dhcwg@ietfa.amsl.com>; Fri,  4 Nov 2011 04:33:48 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id AE57E21F8C0F for <dhcwg@ietf.org>; Fri,  4 Nov 2011 04:33:48 -0700 (PDT)
Received: by vcbfl11 with SMTP id fl11so2291898vcb.31 for <dhcwg@ietf.org>; Fri, 04 Nov 2011 04:33:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; bh=oSG7EhLU6O1ii2lO2pxXjaq4aaM4jDMVUyt4sn24Jjc=; b=wsBKlzHWyTDXlsMwsDpaKO/5laSP8NZGSARhb/W6UNgCGaCmsDvKsge2EhWjPIKEsK /ReeHzvzT8Mgx/a4uDtLxbXFSJeIifAu5FhUeKomgUU+2cO5R8w+usUuBOOFedExsdJJ DwQAtgDEqOERdCbqnIbjBfaBIBWaPDjN08nvo=
Received: by 10.52.33.239 with SMTP id u15mr844475vdi.49.1320406428059; Fri, 04 Nov 2011 04:33:48 -0700 (PDT)
Received: from rtp-rdroms-8912.cisco.com (rtp-isp-nat1.cisco.com. [64.102.254.33]) by mx.google.com with ESMTPS id bx19sm13062715vdb.2.2011.11.04.04.33.46 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 04 Nov 2011 04:33:47 -0700 (PDT)
From: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Fri, 4 Nov 2011 07:33:44 -0400
Message-Id: <27AD7BB5-5295-4D97-A210-565099D12A07@gmail.com>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1251.1)
X-Mailer: Apple Mail (2.1251.1)
Subject: [dhcwg] Proposed change to MAX_SOL_RT
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, 04 Nov 2011 11:33:49 -0000

I've asked the chairs for a short slot in the Taipei WG meeting to =
discuss draft-droms-dhc-dhcpv6-maxsolrt-update-00.  While the doc won't =
officially be published until I-D publication quiet period ends, the =
important text of the draft is only 2 paragraphs, so I'm posting it now =
to encourage discussion prior to the WG meeting.

Here is text of the doc:

Abstract

  This document updates RFC 3315 by defining a new default value for
  SOL_MAX_RT.

1.  Introduction

  Section 5.5 of the DHCP specification [RFC3315] defines the default
  value of MAX_SOL_RT to be 120 seconds.  In some circumstances, this
  default will lead to an unacceptably high volume of aggregated
  traffic at a DHCPv6 server.

2.  Update to RC 3315

  This document changes section 5.5 of RFC 3315 as follows:

  OLD:
     SOL_MAX_RT      120 secs  Max Solicit timeout value

  NEW:
     SOL_MAX_RT     3600 secs  Max Solicit timeout value

  With this change, a DHCPv6 client that does not receive a
  satisfactory response will send Solicit messages with the same
  initial frequency and exponential backoff as specified in RFC 3315.
  However, the long term behavior of these DHCPv6 clients will be to
  send a Solicit message every 3600 seconds rather than every 120
  seconds, significantly reducing the aggregated traffic at the DHCPv6
  server.

  The change to MAX_SOL_RT is in response to DHCPv6 message rates
  observed at a DHCPv6 server in a deployment in which many DHCPv6
  clients are sending Solicit messages but the DHCPv6 server has been
  configured not to respond to those Solicit messages.  RFC 3315 was
  written with the expectation that the 'M' and 'O' flags in NDP
  [RFC2461] would control the use of DHCPv6 by hosts.  However, the
  current definition of the 'M' and 'O' flags in RFC 4861 [RFC4861]
  does not explicitly preclude the use of DHCPv6 by a host.  Some
  devices will initiate DHCPv6 even if RAs are received with the 'M'
  and 'O' bits set to 0.  In some circumstances, it is desirable to
  enable the assignment of IPv6 addresses through DHCPv6 to some
  nodes on a link but not to others, which cannot be implemented
  through the 'M' and 'O' bits.

Two issues to consider:

1. Is 3600 seconds the right number?  How about 7200 seconds?

2. In a scenario in which the DHCPv6 service is unresponsive for =
SOL_MAX_RT and the DHCPv6 clients are all now sending a Solicit every =
SOL_MAX_RT, the average wait time for those clients to complete the =
DHCPv6 message exchange after the DHCPv6 service comes back up will be =
MAX_SOL_RT/2.  Is that situation acceptable or should we define some =
other trigger through which the DHCPv6 clients can be signaled =
explicitly to restart the Solicit transmission algorithm in section =
17.1.2 of RFC 3315.  My personal opinion is that an additional trigger =
is unnecessary.

- Ralph


From Ted.Lemon@nominum.com  Fri Nov  4 05:47:10 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 300A321F8C3E for <dhcwg@ietfa.amsl.com>; Fri,  4 Nov 2011 05:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.542
X-Spam-Level: 
X-Spam-Status: No, score=-106.542 tagged_above=-999 required=5 tests=[AWL=0.057, 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 uthWmyRMfqf3 for <dhcwg@ietfa.amsl.com>; Fri,  4 Nov 2011 05:47:09 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id 5237721F8BEE for <dhcwg@ietf.org>; Fri,  4 Nov 2011 05:47:09 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP;  Fri, 04 Nov 2011 05:47:09 PDT
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 3354E1B82B9 for <dhcwg@ietf.org>; Fri,  4 Nov 2011 05:47:08 -0700 (PDT)
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 730D7190052; Fri,  4 Nov 2011 05:47:06 -0700 (PDT) (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.0323.003; Fri, 4 Nov 2011 05:47:06 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: VithalPrasad Gaitonde <gvithal@gmail.com>
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-failover-requirements-00.txt
Thread-Index: AQHMkm0P3mP3OsJBbECpxu9o48Vu25Wc6E6A///Sj/k=
Date: Fri, 4 Nov 2011 12:47:06 +0000
Message-ID: <71D74251-EDF5-44D1-BB6D-E2D51B1D4D73@nominum.com>
References: <20111024165031.21695.5842.idtracker@ietfa.amsl.com>, <CAAfac2jr1PgvNLYjidLeXYSUymy75r7hORoGLoe=Y3vmo3FQsw@mail.gmail.com>
In-Reply-To: <CAAfac2jr1PgvNLYjidLeXYSUymy75r7hORoGLoe=Y3vmo3FQsw@mail.gmail.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-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>
Subject: Re: [dhcwg] I-D Action:	draft-ietf-dhc-dhcpv6-failover-requirements-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, 04 Nov 2011 12:47:10 -0000

On Nov 4, 2011, at 1:29 AM, "VithalPrasad Gaitonde" <gvithal@gmail.com> wro=
te:
> Configuration synchronization had been left out of the purview of the DHC=
P6 failover requirements document on the same lines as the DHCPv4 failover =
document. While the desire to keep the document simple is understandable, c=
onfiguration synchronization is a critical element of a functional failover=
 so that an administrator can manage the failover subnet(s) as one logical =
unit instead of having to make identical changes on 2 different servers.

This is an open-ended problem, since different servers have very different =
config data models.  We declared this out of scope for DHCPv4, and I think =
that was the right decision.   I think it still is the right decision for D=
HCPv6. =

From Ted.Lemon@nominum.com  Tue Nov  8 03:45:06 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 6958B21F8C1B for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 03:45:06 -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 A51n-sQlwicQ for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 03:45:06 -0800 (PST)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id AA19B21F8C19 for <dhcwg@ietf.org>; Tue,  8 Nov 2011 03:45:05 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP;  Tue, 08 Nov 2011 03:45:05 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 F20551B813B for <dhcwg@ietf.org>; Tue,  8 Nov 2011 03:44:55 -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 30A20190052 for <dhcwg@ietf.org>; Tue,  8 Nov 2011 03:44:53 -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.0323.003; Tue, 8 Nov 2011 03:44:53 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] DHC WGLC: draft-ietf-dhc-forcerenew-nonce-01
Thread-Index: AQHMngvU09trw8MAPE6V/SosGT9YZw==
Date: Tue, 8 Nov 2011 11:44:52 +0000
Message-ID: <C6B13F40-DB79-46A4-B449-119394B5F4F3@nominum.com>
References: <282BBE8A501E1F4DA9C775F964BB21FE3EB2AECD4C@GRFMBX704BA020.griffon.local>, <C1DA0414-6F36-4BC3-888F-BA6F7C4988B8@nominum.com>
In-Reply-To: <C1DA0414-6F36-4BC3-888F-BA6F7C4988B8@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-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] DHC WGLC: draft-ietf-dhc-forcerenew-nonce-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: Tue, 08 Nov 2011 11:45:06 -0000

On Sep 23, 2011, at 10:29 AM, "Ted Lemon" <Ted.Lemon@nominum.com> wrote:

> This document has been ready for WGLC for some time and fell through the =
cracks.   Please give it one last read and let us know if you find any issu=
es.   The document basically ports the nonce functionality of DHCPv6 Reconf=
igure back to DHCPv4.
>=20
> Otherwise, if you support the document, please indicate that you do on th=
e mailing list.   If you think it's a bad idea, please let us know as well.=
   We will do a consensus call on October 7, 2011.

This WGLC got zero responses.   Is it really the case that this document ha=
s no support from the working group, even the authors?   FWIW, I think it's=
 important work and should advance, but I can't make the call on my own. =

From Ted.Lemon@nominum.com  Tue Nov  8 04:02:51 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 E2D3B21F8C17 for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 04:02:51 -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.054, 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 U4bSdqkea6Ai for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 04:02:51 -0800 (PST)
Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by ietfa.amsl.com (Postfix) with ESMTP id C21CE21F8B3B for <dhcwg@ietf.org>; Tue,  8 Nov 2011 04:02:48 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP;  Tue, 08 Nov 2011 04:02:48 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 7BB461B824F for <dhcwg@ietf.org>; Tue,  8 Nov 2011 04:02:47 -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 711E2190052; Tue,  8 Nov 2011 04:02:47 -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.0323.003; Tue, 8 Nov 2011 04:02:47 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Thread-Topic: dhc-dhcpv6-redundancy-consider-02 draft (post WGLC)
Thread-Index: AQHMjN8bxfv6f0KKZEWBXry8DeOi9pWjAuj/
Date: Tue, 8 Nov 2011 12:02:45 +0000
Message-ID: <AF86E8A2-90FE-48B1-8F2E-53974177DC17@nominum.com>
References: <4E9C45B2.5080408@gmail.com>
In-Reply-To: <4E9C45B2.5080408@gmail.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-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Chen, Jack" <jack.chen@twcable.com>, Jean-Francois Tremblay <Jean-Francois.TremblayING@videotron.com>
Subject: Re: [dhcwg] dhc-dhcpv6-redundancy-consider-02 draft (post WGLC)
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, 08 Nov 2011 12:02:52 -0000

On Oct 17, 2011, at 11:11 AM, "Tomasz Mrugalski" <tomasz.mrugalski@gmail.co=
m> wrote:
> This draft seem to successfully pass WGLC
> (http://www.ietf.org/mail-archive/web/dhcwg/current/msg11930.html).

Only one person actually expressed support for this document, so in fact it=
 did not pass WGLC. however there were a number of comments, so I presume t=
here actually is support.  Cpuld those who want this to be published please=
 formally indicate that they do?

Thanks!=

From James.Bristow@swisscom.com  Tue Nov  8 04:17:33 2011
Return-Path: <James.Bristow@swisscom.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 9B5AC21F8B73 for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 04:17:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.999
X-Spam-Level: 
X-Spam-Status: No, score=-3.999 tagged_above=-999 required=5 tests=[BAYES_50=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 yNMFCJ8Nlv85 for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 04:17:33 -0800 (PST)
Received: from mail.swisscom.com (outmail100.swisscom.com [193.222.81.100]) by ietfa.amsl.com (Postfix) with ESMTP id CA33D21F8B4D for <dhcwg@ietf.org>; Tue,  8 Nov 2011 04:17:32 -0800 (PST)
Received: by mail.swisscom.com; Tue, 8 Nov 2011 13:17:30 +0100
From: <James.Bristow@swisscom.com>
To: <dhcwg@ietf.org>
Thread-Topic: [dhcwg] DHC WGLC: draft-ietf-dhc-forcerenew-nonce-01
Thread-Index: AQHMngvU09trw8MAPE6V/SosGT9YZ5Wi36lAgAAEZmA=
Date: Tue, 8 Nov 2011 12:17:26 +0000
Message-ID: <944B9C865C895D40A9D5BD4B7D021EB21313AF97@SG000711.corproot.net>
References: <282BBE8A501E1F4DA9C775F964BB21FE3EB758B80A@GRFMBX704BA020.griffon.local>
In-Reply-To: <282BBE8A501E1F4DA9C775F964BB21FE3EB758B80A@GRFMBX704BA020.griffon.local>
Accept-Language: en-US, de-CH
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [193.222.87.4]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 08 Nov 2011 04:29:08 -0800
Subject: Re: [dhcwg] DHC WGLC: draft-ietf-dhc-forcerenew-nonce-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: Tue, 08 Nov 2011 12:18:29 -0000

We support this document.

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of T=
ed Lemon
Sent: marted=EC 8 novembre 2011 12.45
To: dhcwg@ietf.org WG
Subject: Re: [dhcwg] DHC WGLC: draft-ietf-dhc-forcerenew-nonce-01

On Sep 23, 2011, at 10:29 AM, "Ted Lemon" <Ted.Lemon@nominum.com> wrote:

> This document has been ready for WGLC for some time and fell through the =
cracks.   Please give it one last read and let us know if you find any issu=
es.   The document basically ports the nonce functionality of DHCPv6 Reconf=
igure back to DHCPv4.
>
> Otherwise, if you support the document, please indicate that you do on th=
e mailing list.   If you think it's a bad idea, please let us know as well.=
   We will do a consensus call on October 7, 2011.

This WGLC got zero responses.   Is it really the case that this document ha=
s no support from the working group, even the authors?   FWIW, I think it's=
 important work and should advance, but I can't make the call on my own.
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.


From roberta.maglione@telecomitalia.it  Tue Nov  8 05:11:49 2011
Return-Path: <roberta.maglione@telecomitalia.it>
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 CF02321F851F for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 05:11:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[AWL=0.224,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
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 V87-gIcyLQ+A for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 05:11:45 -0800 (PST)
Received: from GRFEDG702BA020.telecomitalia.it (grfedg702ba020.telecomitalia.it [156.54.233.201]) by ietfa.amsl.com (Postfix) with ESMTP id 6FE5C21F851A for <dhcwg@ietf.org>; Tue,  8 Nov 2011 05:11:45 -0800 (PST)
Received: from GRFHUB701BA020.griffon.local (10.188.101.111) by GRFEDG702BA020.telecomitalia.it (10.188.45.101) with Microsoft SMTP Server (TLS) id 8.2.254.0; Tue, 8 Nov 2011 14:11:41 +0100
Received: from GRFMBX704BA020.griffon.local ([10.188.101.16]) by grfhub701ba020.griffon.local ([10.188.101.111]) with mapi; Tue, 8 Nov 2011 14:11:41 +0100
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: 'Ted Lemon' <Ted.Lemon@nominum.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Date: Tue, 8 Nov 2011 14:11:40 +0100
Thread-Topic: [dhcwg] DHC WGLC: draft-ietf-dhc-forcerenew-nonce-01
Thread-Index: AQHMngvU09trw8MAPE6V/SosGT9YZ5Wi8yfg
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE3EB758B80B@GRFMBX704BA020.griffon.local>
References: <282BBE8A501E1F4DA9C775F964BB21FE3EB2AECD4C@GRFMBX704BA020.griffon.local>, <C1DA0414-6F36-4BC3-888F-BA6F7C4988B8@nominum.com> <C6B13F40-DB79-46A4-B449-119394B5F4F3@nominum.com>
In-Reply-To: <C6B13F40-DB79-46A4-B449-119394B5F4F3@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] DHC WGLC: draft-ietf-dhc-forcerenew-nonce-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: Tue, 08 Nov 2011 13:11:49 -0000

I support this document and I think it should advance.

Regards,
Roberta

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of T=
ed Lemon
Sent: marted=EC 8 novembre 2011 12.45
To: dhcwg@ietf.org WG
Subject: Re: [dhcwg] DHC WGLC: draft-ietf-dhc-forcerenew-nonce-01

On Sep 23, 2011, at 10:29 AM, "Ted Lemon" <Ted.Lemon@nominum.com> wrote:

> This document has been ready for WGLC for some time and fell through the =
cracks.   Please give it one last read and let us know if you find any issu=
es.   The document basically ports the nonce functionality of DHCPv6 Reconf=
igure back to DHCPv4.
>
> Otherwise, if you support the document, please indicate that you do on th=
e mailing list.   If you think it's a bad idea, please let us know as well.=
   We will do a consensus call on October 7, 2011.

This WGLC got zero responses.   Is it really the case that this document ha=
s no support from the working group, even the authors?   FWIW, I think it's=
 important work and should advance, but I can't make the call on my own.
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.


From peng-wu@foxmail.com  Tue Nov  8 05:35:02 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 000E721F8CB3 for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 05:35:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.29
X-Spam-Level: *
X-Spam-Status: No, score=1.29 tagged_above=-999 required=5 tests=[AWL=-1.218,  BAYES_20=-0.74, DNS_FROM_RFC_DSN=1.495, MIME_BASE64_TEXT=1.753]
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 imZX7Xk9q+5K for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 05:35:01 -0800 (PST)
Received: from smtpbg55.qq.com (smtpbg55.qq.com [64.71.138.44]) by ietfa.amsl.com (Postfix) with SMTP id 7152821F8C7A for <dhcwg@ietf.org>; Tue,  8 Nov 2011 05:34:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qq.com; s=s0907; t=1320759260; bh=CMefk8v8FE8T18c4KDHPiZX6hLgiIngrEe9HgQgolio=; h=X-QQ-mid:Received:X-QQ-SSF:Date:From:To:Reply-To:Subject: References:X-Priority:X-Mailer:Mime-Version:Message-ID: Content-Type:Content-Transfer-Encoding; b=KBzRZpoA8xhnNV93k1cReDqAiRwn/9/ollKXKZr6eT6MRy+TIaCTCLu1OSAyD5NgJ KcIV2JuBMv/+XOx/8iS9kqhDAmkYCxSjyCgU4eQC1IwvrLCgWS0MFvt7/wIo803
X-QQ-mid: esmtp9t1320759094t012t15275
Received: from PengWU-PC (unknown [115.231.5.207]) by esmtp4.qq.com (ESMTP) with  id ; Tue, 08 Nov 2011 21:31:32 +0800 (CST)
X-QQ-SSF: 00000000000000F0FxF000000000000
Date: Tue, 8 Nov 2011 21:31:33 +0800
From: "Peng Wu" <peng-wu@foxmail.com>
To: "Ted Lemon" <Ted.Lemon@nominum.com>,  "DHC WG" <dhcwg@ietf.org>
References: <C1741FD0-6595-4F85-8590-56C8565A59C6@nominum.com>
X-Priority: 3
X-Mailer: Foxmail 7.0.1.82[cn]
Mime-Version: 1.0
Message-ID: <2011110821313363934412@foxmail.com>
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
Subject: Re: [dhcwg] Call for adoption: draft-cui-dhc-dhcpv4-over-ipv6
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: peng-wu <peng-wu@foxmail.com>
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, 08 Nov 2011 13:35:02 -0000

SGkgYWxsLA0KDQpTaW5jZSB3ZSd2ZSBwYXNzZWQgdGhlIGRlYWRsaW5lIGFuZCB0aGVyZSdzIG5v
IG9iamVjdGlvbiBvbiB0aGlzIGRvY3VtZW50LCBjYW4gd2UgYWRvcHQgaXQgbm93Pw0KQlRXLCBj
b21tZW50cyBhcmUgc3RpbGwgd2VsY29tZSBhbnkgdGltZSA6KQ0KDQoNCi0tLS0tLS0tLS0tLS0t
DQpQZW5nIFd1DQo+VGhpcyB3YXMgZGlzY3Vzc2VkIGluIHRoZSBtZWV0aW5nIGluIFFDIGFuZCB0
aGUgc2Vuc2Ugb2YgdGhlIHJvb20gd2FzIHRoYXQgdGhlcmUgd2FzIGludGVyZXN0IGluIHRoZSB3
b3JraW5nIGdyb3VwLiAgIFBsZWFzZSByZXZpZXcgdGhlIGRvY3VtZW50IGJyaWVmbHkgYW5kIGlu
ZGljYXRlIHdoZXRoZXIgeW91IGFncmVlIHRoYXQgaXQgc2hvdWxkIGJlIGFkb3B0ZWQgb3Igb3Bw
b3NlIGl0cyBhZG9wdGlvbi4NCj4NCj5GWUkgdGhlIGJhc2ljIGlkZWEgaXMgdG8gcHJvdmlkZSBh
IG1lY2hhbmlzbSBmb3IgcmVsYXlpbmcgREhDUCBhY3Jvc3MgYSB2NiBuZXR3b3JrIGZvciB0aGUg
cHVycG9zZSBvZiBzdXBwb3J0aW5nIHY0IG5vZGVzIG9uIGEgdjYgbmV0d29yayBkdXJpbmcgdGhl
IHRyYW5zaXRpb24gcGVyaW9kLg0KPg0KPldlIHdpbGwgZGV0ZXJtaW5lIGNvbnNlbnN1cyBvbiBO
b3ZlbWJlciA0LCAyMDExLg0KPg0KPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fDQo+ZGhjd2cgbWFpbGluZyBsaXN0DQo+ZGhjd2dAaWV0Zi5vcmcNCj5odHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RoY3dnDQo+


From tomasz.mrugalski@gmail.com  Tue Nov  8 07:13:23 2011
Return-Path: <tomasz.mrugalski@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 982CC21F8CCE for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 07:13:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.566
X-Spam-Level: 
X-Spam-Status: No, score=-3.566 tagged_above=-999 required=5 tests=[AWL=0.033,  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 kwV7ARMh1cBT for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 07:13:23 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id C9C2721F8C97 for <dhcwg@ietf.org>; Tue,  8 Nov 2011 07:13:22 -0800 (PST)
Received: by wyg30 with SMTP id 30so702441wyg.31 for <dhcwg@ietf.org>; Tue, 08 Nov 2011 07:13:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-tagtoolbar-keys:content-type :content-transfer-encoding; bh=auDZ96stJ5k0IsmLmplzHMssQ5ZNwEcF6mKeUB/Nnkw=; b=lP330Az6Q5sPU6j9ydVNRzC9S03uv0aimDg0dKFc4Z9ana8iitFgDqps5MgagPmbau 9+4Cjghc21lgtgM1Xlpho0nYpxHXN4ZLpJdEglH/y2NdBTWeGP60gPtsWPsM2eR9N2Vv MWk+v6Y5BVqu06pRurutajGWrfG3WHSV6UV7o=
Received: by 10.227.202.70 with SMTP id fd6mr33110840wbb.27.1320765201935; Tue, 08 Nov 2011 07:13:21 -0800 (PST)
Received: from [10.0.0.100] (host-109-107-11-157.ip.jarsat.pl. [109.107.11.157]) by mx.google.com with ESMTPS id q30sm2033212wbn.17.2011.11.08.07.13.20 (version=SSLv3 cipher=OTHER); Tue, 08 Nov 2011 07:13:21 -0800 (PST)
Message-ID: <4EB94714.3090402@gmail.com>
Date: Tue, 08 Nov 2011 16:13:24 +0100
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110922 Lightning/1.0b2 Thunderbird/3.1.15
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <4E9C45B2.5080408@gmail.com> <AF86E8A2-90FE-48B1-8F2E-53974177DC17@nominum.com>
In-Reply-To: <AF86E8A2-90FE-48B1-8F2E-53974177DC17@nominum.com>
X-TagToolbar-Keys: D20111108161324675
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>, "Chen, Jack" <jack.chen@twcable.com>, Jean-Francois Tremblay <Jean-Francois.TremblayING@videotron.com>
Subject: Re: [dhcwg] dhc-dhcpv6-redundancy-consider-02 draft (post WGLC)
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, 08 Nov 2011 15:13:23 -0000

On 08.11.2011 13:02, Ted Lemon wrote:
> On Oct 17, 2011, at 11:11 AM, "Tomasz Mrugalski"
> <tomasz.mrugalski@gmail.com> wrote:
>> This draft seem to successfully pass WGLC 
>> (http://www.ietf.org/mail-archive/web/dhcwg/current/msg11930.html).
>
>> 
> Only one person actually expressed support for this document, so in
> fact it did not pass WGLC. however there were a number of comments,
> so I presume there actually is support.  Cpuld those who want this to
> be published please formally indicate that they do?
I support this draft. As I'm co-author, it probably doesn't count.

Tomek

From john_brzozowski@cable.comcast.com  Tue Nov  8 08:11:33 2011
Return-Path: <john_brzozowski@cable.comcast.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 E492221F891D for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 08:11:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.463
X-Spam-Level: 
X-Spam-Status: No, score=-108.463 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_HI=-8, 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 BNVuV9-Eem8p for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 08:11:28 -0800 (PST)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by ietfa.amsl.com (Postfix) with ESMTP id BBCF021F88B7 for <dhcwg@ietf.org>; Tue,  8 Nov 2011 08:11:27 -0800 (PST)
Received: from ([24.40.55.42]) by pacdcimo01.cable.comcast.com with ESMTP  id 5503620.145593656; Tue, 08 Nov 2011 11:11:21 -0500
Received: from PACDCEXMB01.cable.comcast.com ([fe80::3cf0:9cac:6c2a:7359]) by PACDCEXHUB01.cable.comcast.com ([fe80::d1e7:20b5:9b63:21a6%11]) with mapi id 14.01.0339.001; Tue, 8 Nov 2011 11:11:40 -0500
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>, Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: dhc-dhcpv6-redundancy-consider-02 draft (post WGLC)
Thread-Index: AQHMjN8bxfv6f0KKZEWBXry8DeOi9pWjAuj/gACJFgD//7xdgA==
Date: Tue, 8 Nov 2011 16:11:20 +0000
Message-ID: <CADEBEBD.1AB385%john_brzozowski@cable.comcast.com>
In-Reply-To: <4EB94714.3090402@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.13.0.110805
x-originating-ip: [147.191.125.13]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E2D6FF175C1E014598526FA9E62CD861@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: dhc WG <dhcwg@ietf.org>, Jack Chen <jack.chen@twcable.com>, Jean-Francois Tremblay <Jean-Francois.TremblayING@videotron.com>
Subject: Re: [dhcwg] dhc-dhcpv6-redundancy-consider-02 draft (post WGLC)
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, 08 Nov 2011 16:11:34 -0000

I support this as well, from what we have heard this is useful information.

John
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
John Jason Brzozowski
Comcast Cable
e) mailto:john_brzozowski@cable.comcast.com
o) 609-377-6594
m) 484-962-0060
w) http://www.comcast6.net
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D




On 11/8/11 10:13 AM, "Tomek Mrugalski" <tomasz.mrugalski@gmail.com> wrote:

>On 08.11.2011 13:02, Ted Lemon wrote:
>> On Oct 17, 2011, at 11:11 AM, "Tomasz Mrugalski"
>> <tomasz.mrugalski@gmail.com> wrote:
>>> This draft seem to successfully pass WGLC
>>> (http://www.ietf.org/mail-archive/web/dhcwg/current/msg11930.html).
>>
>>>=20
>> Only one person actually expressed support for this document, so in
>> fact it did not pass WGLC. however there were a number of comments,
>> so I presume there actually is support.  Cpuld those who want this to
>> be published please formally indicate that they do?
>I support this draft. As I'm co-author, it probably doesn't count.
>
>Tomek


From Ted.Lemon@nominum.com  Tue Nov  8 08:11: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 46FE911E8095 for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 08:11:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.546
X-Spam-Level: 
X-Spam-Status: No, score=-106.546 tagged_above=-999 required=5 tests=[AWL=0.053, 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 tVaBcfYZFNBv for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 08:11:47 -0800 (PST)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id 4992421F891D for <dhcwg@ietf.org>; Tue,  8 Nov 2011 08:11:47 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP;  Tue, 08 Nov 2011 08:11:47 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 E09911B80B7 for <dhcwg@ietf.org>; Tue,  8 Nov 2011 08:11: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 C8318190052; Tue,  8 Nov 2011 08:11:38 -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.0323.003; Tue, 8 Nov 2011 08:11:38 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: peng-wu <peng-wu@foxmail.com>
Thread-Topic: [dhcwg] Call for adoption: draft-cui-dhc-dhcpv4-over-ipv6
Thread-Index: AQHMkAAyxrNjwGADf0ePBGnmjz0jGZWjFkDWgAAr76o=
Date: Tue, 8 Nov 2011 16:11:38 +0000
Message-ID: <8D21B048-21A2-42EA-8F00-3DDA7F380C48@nominum.com>
References: <C1741FD0-6595-4F85-8590-56C8565A59C6@nominum.com>, <2011110821313363934412@foxmail.com>
In-Reply-To: <2011110821313363934412@foxmail.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-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: DHC WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] Call for adoption: draft-cui-dhc-dhcpv4-over-ipv6
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, 08 Nov 2011 16:11:54 -0000

On Nov 8, 2011, at 8:34 AM, "Peng Wu" <peng-wu@foxmail.com> wrote:

> Since we've passed the deadline and there's no objection on this document=
, can we adopt it now?
> BTW, comments are still welcome any time :)

Given the consensus of the room and no objection on-list, yes, we can adopt=
. Please submit a new version after the queues open. Thanks!


From kkinnear@cisco.com  Tue Nov  8 08:24:29 2011
Return-Path: <kkinnear@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 A068621F8B55 for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 08:24:29 -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 SUlAqxMINK8e for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 08:24:29 -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 D88BD21F8B51 for <dhcwg@ietf.org>; Tue,  8 Nov 2011 08:24:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=kkinnear@cisco.com; l=1065; q=dns/txt; s=iport; t=1320769469; x=1321979069; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=5Yf8PiT7rOXEarQ6nGxfeOxrsi2orLsFKhgImOxwBnk=; b=K3S/VsH7IrGXo51huGBQPGjcP6/kxUMyDG1crdKZ10NfmTaATjieMoqj ZcBg5qnr8BmoskAJxUEr9ELxYLaFbTVDDtCFAIheSbvXiG4apPtK7g4ZY JQ3w9E1SEcSQheS04tvGbNI7S+zyiOhGYWiO2AR8Jaa0kCAMHXptaPM8E 4=;
X-IronPort-AV: E=Sophos;i="4.69,477,1315180800"; d="scan'208";a="34233897"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-8.cisco.com with ESMTP; 08 Nov 2011 16:24:28 +0000
Received: from [161.44.65.167] ([161.44.65.167]) by rcdn-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pA8GORCE001805;  Tue, 8 Nov 2011 16:24:28 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Kim Kinnear <kkinnear@cisco.com>
In-Reply-To: <C6B13F40-DB79-46A4-B449-119394B5F4F3@nominum.com>
Date: Tue, 8 Nov 2011 11:26:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <0234DF3F-CD88-423D-A286-2081D5F685B7@cisco.com>
References: <282BBE8A501E1F4DA9C775F964BB21FE3EB2AECD4C@GRFMBX704BA020.griffon.local>, <C1DA0414-6F36-4BC3-888F-BA6F7C4988B8@nominum.com> <C6B13F40-DB79-46A4-B449-119394B5F4F3@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1084)
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Kim Kinnear <kkinnear@cisco.com>
Subject: Re: [dhcwg] DHC WGLC: draft-ietf-dhc-forcerenew-nonce-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: Tue, 08 Nov 2011 16:24:29 -0000

I support this document and think it should advance.

Regards -- Kim

On Nov 8, 2011, at 6:44 AM, Ted Lemon wrote:

> On Sep 23, 2011, at 10:29 AM, "Ted Lemon" <Ted.Lemon@nominum.com> =
wrote:
>=20
>> This document has been ready for WGLC for some time and fell through =
the cracks.   Please give it one last read and let us know if you find =
any issues.   The document basically ports the nonce functionality of =
DHCPv6 Reconfigure back to DHCPv4.
>>=20
>> Otherwise, if you support the document, please indicate that you do =
on the mailing list.   If you think it's a bad idea, please let us know =
as well.   We will do a consensus call on October 7, 2011.
>=20
> This WGLC got zero responses.   Is it really the case that this =
document has no support from the working group, even the authors?   =
FWIW, I think it's important work and should advance, but I can't make =
the call on my own.=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From rdroms.ietf@gmail.com  Tue Nov  8 12:22:07 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 2CFFB1F0C67 for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 12:22:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.491
X-Spam-Level: 
X-Spam-Status: No, score=-103.491 tagged_above=-999 required=5 tests=[AWL=0.108, 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 WfADXa2LMB4b for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 12:22:06 -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 73F141F0C4A for <dhcwg@ietf.org>; Tue,  8 Nov 2011 12:22:06 -0800 (PST)
Received: by vcbfk1 with SMTP id fk1so879957vcb.31 for <dhcwg@ietf.org>; Tue, 08 Nov 2011 12:22:05 -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=R5hqAbkHp8SmzxTJGTuudvh7VE2Gw6X4Lgrb1juVtS0=; b=Nn8vioy7Ry4pVJ5RtQLOi5jcO7c10uJ5wxeaOLcvW9ShS84/BOxw9w528XvC0gaFn4 mhiye1lI0rypk00P745vj5A68fZDSRJQ3WdCF/KLxYgzAzXz7e4VnuZwCLWO2JbMwGcM OJacNOtoGNPS2krx4zo5p1R31FB+WL/qcnL8E=
Received: by 10.52.36.131 with SMTP id q3mr24690273vdj.91.1320783725857; Tue, 08 Nov 2011 12:22:05 -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 b4sm3939771vda.7.2011.11.08.12.22.03 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 08 Nov 2011 12:22:03 -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: <27AD7BB5-5295-4D97-A210-565099D12A07@gmail.com>
Date: Tue, 8 Nov 2011 15:22:02 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D494B897-6773-4D92-9435-5E165B4306EA@gmail.com>
References: <27AD7BB5-5295-4D97-A210-565099D12A07@gmail.com>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [dhcwg] Proposed change to MAX_SOL_RT
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, 08 Nov 2011 20:22:07 -0000

Followup to previous message about changing MAX_SOL_RT...

On Nov 4, 2011, at 7:33 AM 11/4/11, Ralph Droms wrote:
>=20
> 2. In a scenario in which the DHCPv6 service is unresponsive for =
SOL_MAX_RT and the DHCPv6 clients are all now sending a Solicit every =
SOL_MAX_RT, the average wait time for those clients to complete the =
DHCPv6 message exchange after the DHCPv6 service comes back up will be =
MAX_SOL_RT/2.  Is that situation acceptable or should we define some =
other trigger through which the DHCPv6 clients can be signaled =
explicitly to restart the Solicit transmission algorithm in section =
17.1.2 of RFC 3315.  My personal opinion is that an additional trigger =
is unnecessary.

In support of my opinion, I came up with the following analysis of the =
likelihood of a client getting to the long-term MAX_SOL_RT interval =
state.=20

If the CM and CE router have been up and running, with the CE configured =
through DHCPv6, a WAN link flap will have no effect on DHCPv6 unless the =
link is down past the address/PD lease expiration...and in this case, =
the CE router will lose connectivity regardless.

If the CE router comes up without a valid address/PD lease before the =
DHCPv6 service is running, the CE router will get to the long-term state =
of waiting on average MAX_SOL_RT/2 only if the DHCPv6 service is down =
longer than MAX_SOL_RT/2.  Note that this situation will only occur if =
the CE router is coming up for the first time or coming up after its =
address/PD lease has expired.

So, a DHCPv6 client can get to that long-term state sending a Solicit =
every MAX_SOL_RT interval, but I don't think it's very likely.

Discussion welcome and encouraged.

- Ralph


From ichiroumakino@gmail.com  Tue Nov  8 12:40:04 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 63D6B11E808F for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 12:40:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.511
X-Spam-Level: 
X-Spam-Status: No, score=-3.511 tagged_above=-999 required=5 tests=[AWL=0.088,  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 baKM5CII8hzd for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 12:40:03 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 78A6D11E808E for <dhcwg@ietf.org>; Tue,  8 Nov 2011 12:40:03 -0800 (PST)
Received: by wyg30 with SMTP id 30so1101944wyg.31 for <dhcwg@ietf.org>; Tue, 08 Nov 2011 12:40:02 -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=8NIGF7y1cojdaCaQtA85dF+FH/rmDMrBYKO5upobsB8=; b=QVOVVTkinBkr1EKzdXJfJ1l2F/23THrGPrlVa5u6NhO+dEEmn577DgY3yaAhmGbJJX hQX5zp28Lz74Ky1tK1QF5LRoVMbpDk4EhRH1tlpPpGr/Dx/mAUcNJYt7UZETwwDdZ3mn JNwGaNWEm3cJQnxmXQmJ0ExBe5bZaPgdBySo0=
Received: by 10.216.186.211 with SMTP id w61mr4113242wem.75.1320784802385; Tue, 08 Nov 2011 12:40:02 -0800 (PST)
Received: from ams3-vpn-dhcp5320.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id l20sm3049306wbo.6.2011.11.08.12.40.00 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 08 Nov 2011 12:40:00 -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: <27AD7BB5-5295-4D97-A210-565099D12A07@gmail.com>
Date: Tue, 8 Nov 2011 21:39:58 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <90813655-0402-49B6-9C62-234D9BA2A510@employees.org>
References: <27AD7BB5-5295-4D97-A210-565099D12A07@gmail.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Proposed change to MAX_SOL_RT
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, 08 Nov 2011 20:40:04 -0000

Ralph,

before we jump to conclusions and change the spec, I would very much =
like to understand this better.
the issue here is a DHCP server receiving SOLICITS from clients that it =
is unwilling to serve, right?
and that all solicits are going to be discarded, not replied to and =
created a binding for.

assuming a million DHCPv6 clients with a 120 second timeout that's ~8333 =
solicits/s.
can't a vanilla DHCP server implementation handle that?=20

if a solicit packet is 150 bytes, that's only a ~12Mbps datastream...

cheers,
Ole



On Nov 4, 2011, at 12:33 , Ralph Droms wrote:

> I've asked the chairs for a short slot in the Taipei WG meeting to =
discuss draft-droms-dhc-dhcpv6-maxsolrt-update-00.  While the doc won't =
officially be published until I-D publication quiet period ends, the =
important text of the draft is only 2 paragraphs, so I'm posting it now =
to encourage discussion prior to the WG meeting.
>=20
> Here is text of the doc:
>=20
> Abstract
>=20
>  This document updates RFC 3315 by defining a new default value for
>  SOL_MAX_RT.
>=20
> 1.  Introduction
>=20
>  Section 5.5 of the DHCP specification [RFC3315] defines the default
>  value of MAX_SOL_RT to be 120 seconds.  In some circumstances, this
>  default will lead to an unacceptably high volume of aggregated
>  traffic at a DHCPv6 server.
>=20
> 2.  Update to RC 3315
>=20
>  This document changes section 5.5 of RFC 3315 as follows:
>=20
>  OLD:
>     SOL_MAX_RT      120 secs  Max Solicit timeout value
>=20
>  NEW:
>     SOL_MAX_RT     3600 secs  Max Solicit timeout value
>=20
>  With this change, a DHCPv6 client that does not receive a
>  satisfactory response will send Solicit messages with the same
>  initial frequency and exponential backoff as specified in RFC 3315.
>  However, the long term behavior of these DHCPv6 clients will be to
>  send a Solicit message every 3600 seconds rather than every 120
>  seconds, significantly reducing the aggregated traffic at the DHCPv6
>  server.
>=20
>  The change to MAX_SOL_RT is in response to DHCPv6 message rates
>  observed at a DHCPv6 server in a deployment in which many DHCPv6
>  clients are sending Solicit messages but the DHCPv6 server has been
>  configured not to respond to those Solicit messages.  RFC 3315 was
>  written with the expectation that the 'M' and 'O' flags in NDP
>  [RFC2461] would control the use of DHCPv6 by hosts.  However, the
>  current definition of the 'M' and 'O' flags in RFC 4861 [RFC4861]
>  does not explicitly preclude the use of DHCPv6 by a host.  Some
>  devices will initiate DHCPv6 even if RAs are received with the 'M'
>  and 'O' bits set to 0.  In some circumstances, it is desirable to
>  enable the assignment of IPv6 addresses through DHCPv6 to some
>  nodes on a link but not to others, which cannot be implemented
>  through the 'M' and 'O' bits.
>=20
> Two issues to consider:
>=20
> 1. Is 3600 seconds the right number?  How about 7200 seconds?
>=20
> 2. In a scenario in which the DHCPv6 service is unresponsive for =
SOL_MAX_RT and the DHCPv6 clients are all now sending a Solicit every =
SOL_MAX_RT, the average wait time for those clients to complete the =
DHCPv6 message exchange after the DHCPv6 service comes back up will be =
MAX_SOL_RT/2.  Is that situation acceptable or should we define some =
other trigger through which the DHCPv6 clients can be signaled =
explicitly to restart the Solicit transmission algorithm in section =
17.1.2 of RFC 3315.  My personal opinion is that an additional trigger =
is unnecessary.
>=20
> - Ralph
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From rdroms.ietf@gmail.com  Tue Nov  8 12:54:34 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 211DB1F0C6D for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 12:54:34 -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 XozBFMM78G3W for <dhcwg@ietfa.amsl.com>; Tue,  8 Nov 2011 12:54:33 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id DC45B1F0C6C for <dhcwg@ietf.org>; Tue,  8 Nov 2011 12:54:09 -0800 (PST)
Received: by vws5 with SMTP id 5so1009318vws.31 for <dhcwg@ietf.org>; Tue, 08 Nov 2011 12:54:09 -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=0XbRek4zXrt6VOIDw2c3nAhT7xDqgKZqdjuHYrviAYI=; b=SeBjNNeiYAh0/fA6920tKS5u4IWueUbYcCCymEGjTg0JpsBVYROsC16jy+q6AHtCqo 9N6fM3UZkIbLp/fRhh01oDlJlKgaa8kpsD7x/AjdRKNa8qk5nZRlQO4jFhzJ7JRZwqv/ wr+7s/nFM20yjSn9PGFw2rmoEIo2rsNXZ7/9o=
Received: by 10.52.90.77 with SMTP id bu13mr6034783vdb.34.1320785647149; Tue, 08 Nov 2011 12:54:07 -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 id7sm4011597vdb.21.2011.11.08.12.54.03 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 08 Nov 2011 12:54:04 -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: <90813655-0402-49B6-9C62-234D9BA2A510@employees.org>
Date: Tue, 8 Nov 2011 15:54:02 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <1953942C-2180-4AB6-9170-F20A7BF3C898@gmail.com>
References: <27AD7BB5-5295-4D97-A210-565099D12A07@gmail.com> <90813655-0402-49B6-9C62-234D9BA2A510@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1251.1)
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Proposed change to MAX_SOL_RT
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, 08 Nov 2011 20:54:34 -0000

On Nov 8, 2011, at 3:39 PM 11/8/11, Ole Troan wrote:

> Ralph,
>=20
> before we jump to conclusions and change the spec, I would very much =
like to understand this better.
> the issue here is a DHCP server receiving SOLICITS from clients that =
it is unwilling to serve, right?
> and that all solicits are going to be discarded, not replied to and =
created a binding for.

Right.

> assuming a million DHCPv6 clients with a 120 second timeout that's =
~8333 solicits/s.
> can't a vanilla DHCP server implementation handle that?=20

On the other hand, that stream of Solicits may represent a 100x increase =
over the level of traffic in the steady state.

- Ralph

> if a solicit packet is 150 bytes, that's only a ~12Mbps datastream...
>=20
> cheers,
> Ole
>=20
>=20
>=20
> On Nov 4, 2011, at 12:33 , Ralph Droms wrote:
>=20
>> I've asked the chairs for a short slot in the Taipei WG meeting to =
discuss draft-droms-dhc-dhcpv6-maxsolrt-update-00.  While the doc won't =
officially be published until I-D publication quiet period ends, the =
important text of the draft is only 2 paragraphs, so I'm posting it now =
to encourage discussion prior to the WG meeting.
>>=20
>> Here is text of the doc:
>>=20
>> Abstract
>>=20
>> This document updates RFC 3315 by defining a new default value for
>> SOL_MAX_RT.
>>=20
>> 1.  Introduction
>>=20
>> Section 5.5 of the DHCP specification [RFC3315] defines the default
>> value of MAX_SOL_RT to be 120 seconds.  In some circumstances, this
>> default will lead to an unacceptably high volume of aggregated
>> traffic at a DHCPv6 server.
>>=20
>> 2.  Update to RC 3315
>>=20
>> This document changes section 5.5 of RFC 3315 as follows:
>>=20
>> OLD:
>>    SOL_MAX_RT      120 secs  Max Solicit timeout value
>>=20
>> NEW:
>>    SOL_MAX_RT     3600 secs  Max Solicit timeout value
>>=20
>> With this change, a DHCPv6 client that does not receive a
>> satisfactory response will send Solicit messages with the same
>> initial frequency and exponential backoff as specified in RFC 3315.
>> However, the long term behavior of these DHCPv6 clients will be to
>> send a Solicit message every 3600 seconds rather than every 120
>> seconds, significantly reducing the aggregated traffic at the DHCPv6
>> server.
>>=20
>> The change to MAX_SOL_RT is in response to DHCPv6 message rates
>> observed at a DHCPv6 server in a deployment in which many DHCPv6
>> clients are sending Solicit messages but the DHCPv6 server has been
>> configured not to respond to those Solicit messages.  RFC 3315 was
>> written with the expectation that the 'M' and 'O' flags in NDP
>> [RFC2461] would control the use of DHCPv6 by hosts.  However, the
>> current definition of the 'M' and 'O' flags in RFC 4861 [RFC4861]
>> does not explicitly preclude the use of DHCPv6 by a host.  Some
>> devices will initiate DHCPv6 even if RAs are received with the 'M'
>> and 'O' bits set to 0.  In some circumstances, it is desirable to
>> enable the assignment of IPv6 addresses through DHCPv6 to some
>> nodes on a link but not to others, which cannot be implemented
>> through the 'M' and 'O' bits.
>>=20
>> Two issues to consider:
>>=20
>> 1. Is 3600 seconds the right number?  How about 7200 seconds?
>>=20
>> 2. In a scenario in which the DHCPv6 service is unresponsive for =
SOL_MAX_RT and the DHCPv6 clients are all now sending a Solicit every =
SOL_MAX_RT, the average wait time for those clients to complete the =
DHCPv6 message exchange after the DHCPv6 service comes back up will be =
MAX_SOL_RT/2.  Is that situation acceptable or should we define some =
other trigger through which the DHCPv6 clients can be signaled =
explicitly to restart the Solicit transmission algorithm in section =
17.1.2 of RFC 3315.  My personal opinion is that an additional trigger =
is unnecessary.
>>=20
>> - Ralph
>>=20
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>=20


From arifumi@nttv6.net  Wed Nov  9 00:22:23 2011
Return-Path: <arifumi@nttv6.net>
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 4A6F821F877F for <dhcwg@ietfa.amsl.com>; Wed,  9 Nov 2011 00:22:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.024
X-Spam-Level: 
X-Spam-Status: No, score=-103.024 tagged_above=-999 required=5 tests=[AWL=-0.425, 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 0kfq7hSp19QG for <dhcwg@ietfa.amsl.com>; Wed,  9 Nov 2011 00:22:22 -0800 (PST)
Received: from leo.nttv6.net (leo.nttv6.net [192.47.162.93]) by ietfa.amsl.com (Postfix) with ESMTP id 9149B21F8532 for <dhcwg@ietf.org>; Wed,  9 Nov 2011 00:22:22 -0800 (PST)
Received: from [IPv6:2001:fa8:1010::d49c:a02a:e1a7:2d4b] ([IPv6:2001:fa8:1010:0:d49c:a02a:e1a7:2d4b]) by leo.nttv6.net (8.14.5/8.14.4) with ESMTP id pA98KlaT090202 for <dhcwg@ietf.org>; Wed, 9 Nov 2011 17:20:47 +0900 (JST) (envelope-from arifumi@nttv6.net)
From: Arifumi Matsumoto <arifumi@nttv6.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 9 Nov 2011 17:21:00 +0900
Message-Id: <EEA697BD-5981-45D9-A8B9-0551417CAAAD@nttv6.net>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: [dhcwg] reviews 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: Wed, 09 Nov 2011 08:22:23 -0000

All,

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

IIRC, one reviewer was chosen at that time, and the other was left
undecided.

So, my questions are
the review was submitted somewhere ?
the other reviewer was chosen ?

--
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


From gvithal@gmail.com  Wed Nov  9 01:42:11 2011
Return-Path: <gvithal@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 E507C21F8B1E for <dhcwg@ietfa.amsl.com>; Wed,  9 Nov 2011 01:42:11 -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=[AWL=-0.000, 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 Il5ZZ15PN2dz for <dhcwg@ietfa.amsl.com>; Wed,  9 Nov 2011 01:42:11 -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 9F0F321F8AE6 for <dhcwg@ietf.org>; Wed,  9 Nov 2011 01:42:10 -0800 (PST)
Received: by eyg24 with SMTP id 24so1451608eyg.31 for <dhcwg@ietf.org>; Wed, 09 Nov 2011 01:42:09 -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=3EtGuxZ/o0FvRO8xLBd+90C3ZLVQ2G2eKpC5/xKrmjQ=; b=L6FcFbxno5mdw0ij8A/GNCKinFdRXwqJCaE+/htlQoXwMtTyfMI+5L5wQ2mp9ucObR CPxqLZRVp6ZrNVGJSChCDLkZBHdHxfb85qVxhBxDTkipfOVwQGVIVN6lXZyAbPgZxK3r M4oVoZ6zdEhKgBslRmF9F8IkIPo0X93T7ujpw=
MIME-Version: 1.0
Received: by 10.213.14.77 with SMTP id f13mr1675753eba.142.1320831729170; Wed, 09 Nov 2011 01:42:09 -0800 (PST)
Received: by 10.213.2.132 with HTTP; Wed, 9 Nov 2011 01:42:09 -0800 (PST)
In-Reply-To: <CADEBEBD.1AB385%john_brzozowski@cable.comcast.com>
References: <4EB94714.3090402@gmail.com> <CADEBEBD.1AB385%john_brzozowski@cable.comcast.com>
Date: Wed, 9 Nov 2011 15:12:09 +0530
Message-ID: <CAAfac2jqr5UcBAFm0uwy_qvs=44fkwT97A-FgbRc1Ja2fd-mvQ@mail.gmail.com>
From: VithalPrasad Gaitonde <gvithal@gmail.com>
To: "Brzozowski, John" <John_Brzozowski@cable.comcast.com>
Content-Type: multipart/alternative; boundary=0015174c13400677d704b14a1ada
Cc: dhc WG <dhcwg@ietf.org>, Jack Chen <jack.chen@twcable.com>, Jean-Francois Tremblay <Jean-Francois.TremblayING@videotron.com>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] dhc-dhcpv6-redundancy-consider-02 draft (post WGLC)
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, 09 Nov 2011 09:42:12 -0000

--0015174c13400677d704b14a1ada
Content-Type: text/plain; charset=ISO-8859-1

The documentation of these redundancy approaches serves as a useful
guidance.
Support this document.

Thanks,
Prasad

On Tue, Nov 8, 2011 at 9:41 PM, Brzozowski, John <
John_Brzozowski@cable.comcast.com> wrote:

> I support this as well, from what we have heard this is useful information.
>
> John
> =========================================
> John Jason Brzozowski
> Comcast Cable
> e) mailto:john_brzozowski@cable.comcast.com
> o) 609-377-6594
> m) 484-962-0060
> w) http://www.comcast6.net
> =========================================
>
>
>
>
> On 11/8/11 10:13 AM, "Tomek Mrugalski" <tomasz.mrugalski@gmail.com> wrote:
>
> >On 08.11.2011 13:02, Ted Lemon wrote:
> >> On Oct 17, 2011, at 11:11 AM, "Tomasz Mrugalski"
> >> <tomasz.mrugalski@gmail.com> wrote:
> >>> This draft seem to successfully pass WGLC
> >>> (http://www.ietf.org/mail-archive/web/dhcwg/current/msg11930.html).
> >>
> >>>
> >> Only one person actually expressed support for this document, so in
> >> fact it did not pass WGLC. however there were a number of comments,
> >> so I presume there actually is support.  Cpuld those who want this to
> >> be published please formally indicate that they do?
> >I support this draft. As I'm co-author, it probably doesn't count.
> >
> >Tomek
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>

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

<div>The documentation of these redundancy approaches serves as a useful gu=
idance.</div><div>Support this document.</div><div>=A0</div><div>Thanks,</d=
iv><div>Prasad=A0<br><br></div><div class=3D"gmail_quote">On Tue, Nov 8, 20=
11 at 9:41 PM, Brzozowski, John <span dir=3D"ltr">&lt;<a href=3D"mailto:Joh=
n_Brzozowski@cable.comcast.com">John_Brzozowski@cable.comcast.com</a>&gt;</=
span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; paddi=
ng-left: 1ex; border-left-color: rgb(204, 204, 204); border-left-width: 1px=
; border-left-style: solid;">I support this as well, from what we have hear=
d this is useful information.<br>

<br>
John<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
John Jason Brzozowski<br>
Comcast Cable<br>
e) mailto:<a href=3D"mailto:john_brzozowski@cable.comcast.com">john_brzozow=
ski@cable.comcast.com</a><br>
o) <a href=3D"tel:609-377-6594" value=3D"+16093776594">609-377-6594</a><br>
m) <a href=3D"tel:484-962-0060" value=3D"+14849620060">484-962-0060</a><br>
w) <a href=3D"http://www.comcast6.net" target=3D"_blank">http://www.comcast=
6.net</a><br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<div><div></div><div class=3D"h5"><br>
<br>
<br>
<br>
On 11/8/11 10:13 AM, &quot;Tomek Mrugalski&quot; &lt;<a href=3D"mailto:toma=
sz.mrugalski@gmail.com">tomasz.mrugalski@gmail.com</a>&gt; wrote:<br>
<br>
&gt;On 08.11.2011 13:02, Ted Lemon wrote:<br>
&gt;&gt; On Oct 17, 2011, at 11:11 AM, &quot;Tomasz Mrugalski&quot;<br>
&gt;&gt; &lt;<a href=3D"mailto:tomasz.mrugalski@gmail.com">tomasz.mrugalski=
@gmail.com</a>&gt; wrote:<br>
&gt;&gt;&gt; This draft seem to successfully pass WGLC<br>
&gt;&gt;&gt; (<a href=3D"http://www.ietf.org/mail-archive/web/dhcwg/current=
/msg11930.html" target=3D"_blank">http://www.ietf.org/mail-archive/web/dhcw=
g/current/msg11930.html</a>).<br>
&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt; Only one person actually expressed support for this document, so i=
n<br>
&gt;&gt; fact it did not pass WGLC. however there were a number of comments=
,<br>
&gt;&gt; so I presume there actually is support. =A0Cpuld those who want th=
is to<br>
&gt;&gt; be published please formally indicate that they do?<br>
&gt;I support this draft. As I&#39;m co-author, it probably doesn&#39;t cou=
nt.<br>
&gt;<br>
&gt;Tomek<br>
<br>
_______________________________________________<br>
dhcwg mailing list<br>
<a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dhcwg" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/dhcwg</a><br>
</div></div></blockquote></div><br>

--0015174c13400677d704b14a1ada--

From mgoller@gmail.com  Wed Nov  9 07:05:40 2011
Return-Path: <mgoller@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 BC15B21F8B74 for <dhcwg@ietfa.amsl.com>; Wed,  9 Nov 2011 07:05:40 -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 NBt4zCT5AZng for <dhcwg@ietfa.amsl.com>; Wed,  9 Nov 2011 07:05:36 -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 4E7B021F8B63 for <dhcwg@ietf.org>; Wed,  9 Nov 2011 07:05:35 -0800 (PST)
Received: by faas12 with SMTP id s12so2128145faa.31 for <dhcwg@ietf.org>; Wed, 09 Nov 2011 07:05:34 -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:content-transfer-encoding; bh=Bslp1jVkYUNspmP3+xLgAb1F/yClePaziaFG6iM4Z2A=; b=u500we2cnz4UcoVUg/rW0LyQmMIqbP6onX3ZY/B3DwSCbqSQit+zYUlUBtOVNUSjmV DvhpFzxtCVEq7fyf+fruSoAiAuKUlf5Jn8q5/D8MBb4An7R1r+4NgL/w19QTziJ/DLsk FkkiX9Oi4sjvPRpD1c2VwHrEqeR9ihVDp6Bgo=
MIME-Version: 1.0
Received: by 10.223.16.145 with SMTP id o17mr5433404faa.20.1320851133338; Wed, 09 Nov 2011 07:05:33 -0800 (PST)
Received: by 10.223.119.212 with HTTP; Wed, 9 Nov 2011 07:05:33 -0800 (PST)
In-Reply-To: <CAAfac2jqr5UcBAFm0uwy_qvs=44fkwT97A-FgbRc1Ja2fd-mvQ@mail.gmail.com>
References: <4EB94714.3090402@gmail.com> <CADEBEBD.1AB385%john_brzozowski@cable.comcast.com> <CAAfac2jqr5UcBAFm0uwy_qvs=44fkwT97A-FgbRc1Ja2fd-mvQ@mail.gmail.com>
Date: Wed, 9 Nov 2011 16:05:33 +0100
Message-ID: <CAMdbJyKP+vh1ZL-F-1avTUxv+sBMDNiEPnF4AStp=n=fyqDSbw@mail.gmail.com>
From: Marcus Goller <mgoller@gmail.com>
To: dhc WG <dhcwg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Jack Chen <jack.chen@twcable.com>, Jean-Francois Tremblay <Jean-Francois.TremblayING@videotron.com>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] dhc-dhcpv6-redundancy-consider-02 draft (post WGLC)
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, 09 Nov 2011 15:05:40 -0000

I also think this very useful to have.

Marcus

On Wed, Nov 9, 2011 at 10:42 AM, VithalPrasad Gaitonde
<gvithal@gmail.com> wrote:
> The documentation of these redundancy approaches serves as a useful
> guidance.
> Support this document.
>
> Thanks,
> Prasad
>
> On Tue, Nov 8, 2011 at 9:41 PM, Brzozowski, John
> <John_Brzozowski@cable.comcast.com> wrote:
>>
>> I support this as well, from what we have heard this is useful
>> information.
>>
>> John
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> John Jason Brzozowski
>> Comcast Cable
>> e) mailto:john_brzozowski@cable.comcast.com
>> o) 609-377-6594
>> m) 484-962-0060
>> w) http://www.comcast6.net
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>
>>
>>
>>
>> On 11/8/11 10:13 AM, "Tomek Mrugalski" <tomasz.mrugalski@gmail.com> wrot=
e:
>>
>> >On 08.11.2011 13:02, Ted Lemon wrote:
>> >> On Oct 17, 2011, at 11:11 AM, "Tomasz Mrugalski"
>> >> <tomasz.mrugalski@gmail.com> wrote:
>> >>> This draft seem to successfully pass WGLC
>> >>> (http://www.ietf.org/mail-archive/web/dhcwg/current/msg11930.html).
>> >>
>> >>>
>> >> Only one person actually expressed support for this document, so in
>> >> fact it did not pass WGLC. however there were a number of comments,
>> >> so I presume there actually is support. =A0Cpuld those who want this =
to
>> >> be published please formally indicate that they do?
>> >I support this draft. As I'm co-author, it probably doesn't count.
>> >
>> >Tomek
>>
>> _______________________________________________
>> 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 ericjb3666@yahoo.com  Wed Nov  9 09:06:58 2011
Return-Path: <ericjb3666@yahoo.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 35B401F0C34 for <dhcwg@ietfa.amsl.com>; Wed,  9 Nov 2011 09:06:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 g6-v8wG80X0E for <dhcwg@ietfa.amsl.com>; Wed,  9 Nov 2011 09:06:54 -0800 (PST)
Received: from nm26-vm0.bullet.mail.ac4.yahoo.com (nm26-vm0.bullet.mail.ac4.yahoo.com [98.139.52.242]) by ietfa.amsl.com (Postfix) with SMTP id BA0B921F8CA4 for <dhcwg@ietf.org>; Wed,  9 Nov 2011 09:06:53 -0800 (PST)
Received: from [98.139.52.190] by nm26.bullet.mail.ac4.yahoo.com with NNFMP; 09 Nov 2011 17:06:48 -0000
Received: from [98.139.52.177] by tm3.bullet.mail.ac4.yahoo.com with NNFMP; 09 Nov 2011 17:06:48 -0000
Received: from [127.0.0.1] by omp1060.mail.ac4.yahoo.com with NNFMP; 09 Nov 2011 17:06:48 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 191387.99123.bm@omp1060.mail.ac4.yahoo.com
Received: (qmail 27996 invoked by uid 60001); 9 Nov 2011 17:06:48 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1320858408; bh=LnkMBoeMbdgrJxtWpFCjsp/c+R9C/6yYeVuDi2e3dXM=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=rQAgEhXhvL/tjPRkwXYOYp9vhGsjU6SS4CCjnt8/xDWyBNxiWKotCud0KWKY82KzFTNo7pApweYmXiMSVh8Z2iFB8klisq3rCsLuVOr4yyApAMJQhWAizQ/g05xC7GQhQMn4PJQBx4MDmZclrpLi4v8MYdwxUFkIH+rM+ymaSHc=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=S+nQ6XklJpK33i29U36ke1PROvsw5xPGCFz2DiT+AWdSfoDrTfIymkuXX2bejvQ1TgrYIPguzl9K81TmPHGRGBQHxyT2Eviq6aMH6ix9iYnUZu2qBbNyA0Z36xZxB+dT582n/FrTPjltc1/gbzHfJSzEotlT8kRr12sn1Fl9FkU=;
X-YMail-OSG: e_LLZzcVM1n7qhYupww5T0FLH.Nwm29lGzDCI19ndYYfIna mdWex41glZDSzl3hF7mWfecljFql_mAbOLxjz0u28jVJ4_yPvFfqx1qB.qoo LnPJb0UOxpSePJM6YgDVqi91KwqcWgFB90Arlw5qu4tAfczGkaqol6arwDEV bEo4MUNETul.eSXpEoc23ylOKam2S9vzGhPAsmikkvA1eUTj_lGd_pEyg.UC bwV4ORcoCASypjdtJdszqL00DeAllROZUIro_ux90Er.QyZzlOoGf4yFKc8O aT.uou1mJy3vR_EKHQfq5GMVxwIIYUSGtyPuCdkz5GGUvu0BBFT7fPguZ6zh Dy45LPLl4ECmnw7sBelRIWhYmKI2q4juuH8gGzFm2mEnxNXZhv03B4FDw0mA jBxRtbAPo.uyiTdFi5c6tUUKA8bEQ4xaY8I7laUgnq8_Ls6ipMJACgfPBqWS SXcituOlD.GO.StoVoFA86Qw1mPuxF.JwZKuEz9phbzyLgFTPbcVZJtEDCow DMJUiIGCwVvqjyduUb6v.L25S9C4Vkftuxw--
Received: from [24.55.79.184] by web65811.mail.ac4.yahoo.com via HTTP; Wed, 09 Nov 2011 09:06:47 PST
X-Mailer: YahooMailWebService/0.8.114.317681
References: <mailman.3158.1320851141.2955.dhcwg@ietf.org>
Message-ID: <1320858407.761.YahooMailNeo@web65811.mail.ac4.yahoo.com>
Date: Wed, 9 Nov 2011 09:06:47 -0800 (PST)
From: Ericric Jose Benitez Centeno <ericjb3666@yahoo.com>
To: dhcwg@ietf.org
In-Reply-To: <mailman.3158.1320851141.2955.dhcwg@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="776298407-1920564092-1320858407=:761"
X-Mailman-Approved-At: Wed, 09 Nov 2011 09:45:55 -0800
Subject: Re: [dhcwg] dhcwg Digest, Vol 91, Issue 7
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ericric Jose Benitez Centeno <ericjb3666@yahoo.com>
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, 09 Nov 2011 17:06:58 -0000

--776298407-1920564092-1320858407=:761
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

unsubscribe-ericjb3666@yahoo.com=A0=0AEric Benitez=0A=0A=0A&gt;____________=
____________________=0A&gt;From: &quot;dhcwg-request@ietf.org&quot; &lt;dhc=
wg-request@ietf.org&gt;=0A&gt;To: dhcwg@ietf.org=0A&gt;Sent: Wednesday, Nov=
ember 9, 2011 12:05 PM=0A&gt;Subject: dhcwg Digest, Vol 91, Issue 7=0A&gt;=
=0A&gt;If you have received this digest without all the individual message=
=0A&gt;attachments you will need to update your digest options in your list=
=0A&gt;subscription.=A0 To do so, go to =0A&gt;=0A&gt;https://www.ietf.org/=
mailman/listinfo/dhcwg=0A&gt;=0A&gt;Click the &#39;Unsubscribe or edit opti=
ons&#39; button, log in, and set &quot;Get=0A&gt;MIME or Plain Text Digests=
?&quot; to MIME.=A0 You can set this option=0A&gt;globally for all the list=
 digests you receive at this point.=0A&gt;=0A&gt;=0A&gt;=0A&gt;Send dhcwg m=
ailing list submissions to=0A&gt;=A0=A0=A0 dhcwg@ietf.org=0A&gt;=0A&gt;To s=
ubscribe or unsubscribe via the World Wide Web, visit=0A&gt;=A0=A0=A0 https=
://www.ietf.org/mailman/listinfo/dhcwg=0A&gt;or, via email, send a message =
with subject or body &#39;help&#39; to=0A&gt;=A0=A0=A0 dhcwg-request@ietf.o=
rg=0A&gt;=0A&gt;You can reach the person managing the list at=0A&gt;=A0=A0=
=A0 dhcwg-owner@ietf.org=0A&gt;=0A&gt;When replying, please edit your Subje=
ct line so it is more specific=0A&gt;than &quot;Re: Contents of dhcwg diges=
t...&quot;=0A&gt;=0A&gt;=0A&gt;Today&#39;s Topics:=0A&gt;=0A&gt;=A0  1. Re:=
 Proposed change to MAX_SOL_RT (Ralph Droms)=0A&gt;=A0  2. Re: Proposed cha=
nge to MAX_SOL_RT (Ole Troan)=0A&gt;=A0  3. Re: Proposed change to MAX_SOL_=
RT (Ralph Droms)=0A&gt;=A0  4. reviews of draft-ietf-6man-addr-select-opt-0=
1 (Arifumi Matsumoto)=0A&gt;=A0  5. Re: dhc-dhcpv6-redundancy-consider-02 d=
raft (post WGLC)=0A&gt;=A0 =A0 =A0 (VithalPrasad Gaitonde)=0A&gt;=A0  6. Re=
: dhc-dhcpv6-redundancy-consider-02 draft (post WGLC)=0A&gt;=A0 =A0 =A0 (Ma=
rcus Goller)=0A&gt;=0A&gt;=0A&gt;------------------------------------------=
----------------------------=0A&gt;=0A&gt;Message: 1=0A&gt;Date: Tue, 8 Nov=
 2011 15:22:02 -0500=0A&gt;From: Ralph Droms &lt;rdroms.ietf@gmail.com&gt;=
=0A&gt;To: &quot;dhcwg@ietf.org WG&quot; &lt;dhcwg@ietf.org&gt;=0A&gt;Subje=
ct: Re: [dhcwg] Proposed change to MAX_SOL_RT=0A&gt;Message-ID: &lt;D494B89=
7-6773-4D92-9435-5E165B4306EA@gmail.com&gt;=0A&gt;Content-Type: text/plain;=
 charset=3Dus-ascii=0A&gt;=0A&gt;Followup to previous message about changin=
g MAX_SOL_RT...=0A&gt;=0A&gt;On Nov 4, 2011, at 7:33 AM 11/4/11, Ralph Drom=
s wrote:=0A&gt;&gt; =0A&gt;&gt; 2. In a scenario in which the DHCPv6 servic=
e is unresponsive for SOL_MAX_RT and the DHCPv6 clients are all now sending=
 a Solicit every SOL_MAX_RT, the average wait time for those clients to com=
plete the DHCPv6 message exchange after the DHCPv6 service comes back up wi=
ll be MAX_SOL_RT/2.=A0 Is that situation acceptable or should we define som=
e other trigger through which the DHCPv6 clients can be signaled explicitly=
 to restart the Solicit transmission algorithm in section 17.1.2 of RFC 331=
5.=A0 My personal opinion is that an additional trigger is unnecessary.=0A&=
gt;=0A&gt;In support of my opinion, I came up with the following analysis o=
f the likelihood of a client getting to the long-term MAX_SOL_RT interval s=
tate. =0A&gt;=0A&gt;If the CM and CE router have been up and running, with =
the CE configured through DHCPv6, a WAN link flap will have no effect on DH=
CPv6 unless the link is down past the address/PD lease expiration...and in =
this case, the CE router will lose connectivity regardless.=0A&gt;=0A&gt;If=
 the CE router comes up without a valid address/PD lease before the DHCPv6 =
service is running, the CE router will get to the long-term state of waitin=
g on average MAX_SOL_RT/2 only if the DHCPv6 service is down longer than MA=
X_SOL_RT/2.=A0 Note that this situation will only occur if the CE router is=
 coming up for the first time or coming up after its address/PD lease has e=
xpired.=0A&gt;=0A&gt;So, a DHCPv6 client can get to that long-term state se=
nding a Solicit every MAX_SOL_RT interval, but I don&#39;t think it&#39;s v=
ery likely.=0A&gt;=0A&gt;Discussion welcome and encouraged.=0A&gt;=0A&gt;- =
Ralph=0A&gt;=0A&gt;=0A&gt;=0A&gt;------------------------------=0A&gt;=0A&g=
t;Message: 2=0A&gt;Date: Tue, 8 Nov 2011 21:39:58 +0100=0A&gt;From: Ole Tro=
an &lt;otroan@employees.org&gt;=0A&gt;To: Ralph Droms &lt;rdroms.ietf@gmail=
.com&gt;=0A&gt;Cc: &quot;dhcwg@ietf.org WG&quot; &lt;dhcwg@ietf.org&gt;=0A&=
gt;Subject: Re: [dhcwg] Proposed change to MAX_SOL_RT=0A&gt;Message-ID: &lt=
;90813655-0402-49B6-9C62-234D9BA2A510@employees.org&gt;=0A&gt;Content-Type:=
 text/plain; charset=3Dus-ascii=0A&gt;=0A&gt;Ralph,=0A&gt;=0A&gt;before we =
jump to conclusions and change the spec, I would very much like to understa=
nd this better.=0A&gt;the issue here is a DHCP server receiving SOLICITS fr=
om clients that it is unwilling to serve, right?=0A&gt;and that all solicit=
s are going to be discarded, not replied to and created a binding for.=0A&g=
t;=0A&gt;assuming a million DHCPv6 clients with a 120 second timeout that&#=
39;s ~8333 solicits/s.=0A&gt;can&#39;t a vanilla DHCP server implementation=
 handle that? =0A&gt;=0A&gt;if a solicit packet is 150 bytes, that&#39;s on=
ly a ~12Mbps datastream...=0A&gt;=0A&gt;cheers,=0A&gt;Ole=0A&gt;=0A&gt;=0A&=
gt;=0A&gt;On Nov 4, 2011, at 12:33 , Ralph Droms wrote:=0A&gt;=0A&gt;&gt; I=
&#39;ve asked the chairs for a short slot in the Taipei WG meeting to discu=
ss draft-droms-dhc-dhcpv6-maxsolrt-update-00.=A0 While the doc won&#39;t of=
ficially be published until I-D publication quiet period ends, the importan=
t text of the draft is only 2 paragraphs, so I&#39;m posting it now to enco=
urage discussion prior to the WG meeting.=0A&gt;&gt; =0A&gt;&gt; Here is te=
xt of the doc:=0A&gt;&gt; =0A&gt;&gt; Abstract=0A&gt;&gt; =0A&gt;&gt;=A0 Th=
is document updates RFC 3315 by defining a new default value for=0A&gt;&gt;=
=A0 SOL_MAX_RT.=0A&gt;&gt; =0A&gt;&gt; 1.=A0 Introduction=0A&gt;&gt; =0A&gt=
;&gt;=A0 Section 5.5 of the DHCP specification [RFC3315] defines the defaul=
t=0A&gt;&gt;=A0 value of MAX_SOL_RT to be 120 seconds.=A0 In some circumsta=
nces, this=0A&gt;&gt;=A0 default will lead to an unacceptably high volume o=
f aggregated=0A&gt;&gt;=A0 traffic at a DHCPv6 server.=0A&gt;&gt; =0A&gt;&g=
t; 2.=A0 Update to RC 3315=0A&gt;&gt; =0A&gt;&gt;=A0 This document changes =
section 5.5 of RFC 3315 as follows:=0A&gt;&gt; =0A&gt;&gt;=A0 OLD:=0A&gt;&g=
t;=A0 =A0  SOL_MAX_RT=A0 =A0 =A0 120 secs=A0 Max Solicit timeout value=0A&g=
t;&gt; =0A&gt;&gt;=A0 NEW:=0A&gt;&gt;=A0 =A0  SOL_MAX_RT=A0 =A0  3600 secs=
=A0 Max Solicit timeout value=0A&gt;&gt; =0A&gt;&gt;=A0 With this change, a=
 DHCPv6 client that does not receive a=0A&gt;&gt;=A0 satisfactory response =
will send Solicit messages with the same=0A&gt;&gt;=A0 initial frequency an=
d exponential backoff as specified in RFC 3315.=0A&gt;&gt;=A0 However, the =
long term behavior of these DHCPv6 clients will be to=0A&gt;&gt;=A0 send a =
Solicit message every 3600 seconds rather than every 120=0A&gt;&gt;=A0 seco=
nds, significantly reducing the aggregated traffic at the DHCPv6=0A&gt;&gt;=
=A0 server.=0A&gt;&gt; =0A&gt;&gt;=A0 The change to MAX_SOL_RT is in respon=
se to DHCPv6 message rates=0A&gt;&gt;=A0 observed at a DHCPv6 server in a d=
eployment in which many DHCPv6=0A&gt;&gt;=A0 clients are sending Solicit me=
ssages but the DHCPv6 server has been=0A&gt;&gt;=A0 configured not to respo=
nd to those Solicit messages.=A0 RFC 3315 was=0A&gt;&gt;=A0 written with th=
e expectation that the &#39;M&#39; and &#39;O&#39; flags in NDP=0A&gt;&gt;=
=A0 [RFC2461] would control the use of DHCPv6 by hosts.=A0 However, the=0A&=
gt;&gt;=A0 current definition of the &#39;M&#39; and &#39;O&#39; flags in R=
FC 4861 [RFC4861]=0A&gt;&gt;=A0 does not explicitly preclude the use of DHC=
Pv6 by a host.=A0 Some=0A&gt;&gt;=A0 devices will initiate DHCPv6 even if R=
As are received with the &#39;M&#39;=0A&gt;&gt;=A0 and &#39;O&#39; bits set=
 to 0.=A0 In some circumstances, it is desirable to=0A&gt;&gt;=A0 enable th=
e assignment of IPv6 addresses through DHCPv6 to some=0A&gt;&gt;=A0 nodes o=
n a link but not to others, which cannot be implemented=0A&gt;&gt;=A0 throu=
gh the &#39;M&#39; and &#39;O&#39; bits.=0A&gt;&gt; =0A&gt;&gt; Two issues =
to consider:=0A&gt;&gt; =0A&gt;&gt; 1. Is 3600 seconds the right number?=A0=
 How about 7200 seconds?=0A&gt;&gt; =0A&gt;&gt; 2. In a scenario in which t=
he DHCPv6 service is unresponsive for SOL_MAX_RT and the DHCPv6 clients are=
 all now sending a Solicit every SOL_MAX_RT, the average wait time for thos=
e clients to complete the DHCPv6 message exchange after the DHCPv6 service =
comes back up will be MAX_SOL_RT/2.=A0 Is that situation acceptable or shou=
ld we define some other trigger through which the DHCPv6 clients can be sig=
naled explicitly to restart the Solicit transmission algorithm in section 1=
7.1.2 of RFC 3315.=A0 My personal opinion is that an additional trigger is =
unnecessary.=0A&gt;&gt; =0A&gt;&gt; - Ralph=0A&gt;&gt; =0A&gt;&gt; ________=
_______________________________________=0A&gt;&gt; dhcwg mailing list=0A&gt=
;&gt; dhcwg@ietf.org=0A&gt;&gt; https://www.ietf.org/mailman/listinfo/dhcwg=
=0A&gt;=0A&gt;=0A&gt;=0A&gt;------------------------------=0A&gt;=0A&gt;Mes=
sage: 3=0A&gt;Date: Tue, 8 Nov 2011 15:54:02 -0500=0A&gt;From: Ralph Droms =
&lt;rdroms.ietf@gmail.com&gt;=0A&gt;To: Ole Troan &lt;otroan@employees.org&=
gt;=0A&gt;Cc: &quot;dhcwg@ietf.org WG&quot; &lt;dhcwg@ietf.org&gt;=0A&gt;Su=
bject: Re: [dhcwg] Proposed change to MAX_SOL_RT=0A&gt;Message-ID: &lt;1953=
942C-2180-4AB6-9170-F20A7BF3C898@gmail.com&gt;=0A&gt;Content-Type: text/pla=
in; charset=3Dus-ascii=0A&gt;=0A&gt;=0A&gt;On Nov 8, 2011, at 3:39 PM 11/8/=
11, Ole Troan wrote:=0A&gt;=0A&gt;&gt; Ralph,=0A&gt;&gt; =0A&gt;&gt; before=
 we jump to conclusions and change the spec, I would very much like to unde=
rstand this better.=0A&gt;&gt; the issue here is a DHCP server receiving SO=
LICITS from clients that it is unwilling to serve, right?=0A&gt;&gt; and th=
at all solicits are going to be discarded, not replied to and created a bin=
ding for.=0A&gt;=0A&gt;Right.=0A&gt;=0A&gt;&gt; assuming a million DHCPv6 c=
lients with a 120 second timeout that&#39;s ~8333 solicits/s.=0A&gt;&gt; ca=
n&#39;t a vanilla DHCP server implementation handle that? =0A&gt;=0A&gt;On =
the other hand, that stream of Solicits may represent a 100x increase over =
the level of traffic in the steady state.=0A&gt;=0A&gt;- Ralph=0A&gt;=0A&gt=
;&gt; if a solicit packet is 150 bytes, that&#39;s only a ~12Mbps datastrea=
m...=0A&gt;&gt; =0A&gt;&gt; cheers,=0A&gt;&gt; Ole=0A&gt;&gt; =0A&gt;&gt; =
=0A&gt;&gt; =0A&gt;&gt; On Nov 4, 2011, at 12:33 , Ralph Droms wrote:=0A&gt=
;&gt; =0A&gt;&gt;&gt; I&#39;ve asked the chairs for a short slot in the Tai=
pei WG meeting to discuss draft-droms-dhc-dhcpv6-maxsolrt-update-00.=A0 Whi=
le the doc won&#39;t officially be published until I-D publication quiet pe=
riod ends, the important text of the draft is only 2 paragraphs, so I&#39;m=
 posting it now to encourage discussion prior to the WG meeting.=0A&gt;&gt;=
&gt; =0A&gt;&gt;&gt; Here is text of the doc:=0A&gt;&gt;&gt; =0A&gt;&gt;&gt=
; Abstract=0A&gt;&gt;&gt; =0A&gt;&gt;&gt; This document updates RFC 3315 by=
 defining a new default value for=0A&gt;&gt;&gt; SOL_MAX_RT.=0A&gt;&gt;&gt;=
 =0A&gt;&gt;&gt; 1.=A0 Introduction=0A&gt;&gt;&gt; =0A&gt;&gt;&gt; Section =
5.5 of the DHCP specification [RFC3315] defines the default=0A&gt;&gt;&gt; =
value of MAX_SOL_RT to be 120 seconds.=A0 In some circumstances, this=0A&gt=
;&gt;&gt; default will lead to an unacceptably high volume of aggregated=0A=
&gt;&gt;&gt; traffic at a DHCPv6 server.=0A&gt;&gt;&gt; =0A&gt;&gt;&gt; 2.=
=A0 Update to RC 3315=0A&gt;&gt;&gt; =0A&gt;&gt;&gt; This document changes =
section 5.5 of RFC 3315 as follows:=0A&gt;&gt;&gt; =0A&gt;&gt;&gt; OLD:=0A&=
gt;&gt;&gt;=A0 =A0 SOL_MAX_RT=A0 =A0 =A0 120 secs=A0 Max Solicit timeout va=
lue=0A&gt;&gt;&gt; =0A&gt;&gt;&gt; NEW:=0A&gt;&gt;&gt;=A0 =A0 SOL_MAX_RT=A0=
 =A0  3600 secs=A0 Max Solicit timeout value=0A&gt;&gt;&gt; =0A&gt;&gt;&gt;=
 With this change, a DHCPv6 client that does not receive a=0A&gt;&gt;&gt; s=
atisfactory response will send Solicit messages with the same=0A&gt;&gt;&gt=
; initial frequency and exponential backoff as specified in RFC 3315.=0A&gt=
;&gt;&gt; However, the long term behavior of these DHCPv6 clients will be t=
o=0A&gt;&gt;&gt; send a Solicit message every 3600 seconds rather than ever=
y 120=0A&gt;&gt;&gt; seconds, significantly reducing the aggregated traffic=
 at the DHCPv6=0A&gt;&gt;&gt; server.=0A&gt;&gt;&gt; =0A&gt;&gt;&gt; The ch=
ange to MAX_SOL_RT is in response to DHCPv6 message rates=0A&gt;&gt;&gt; ob=
served at a DHCPv6 server in a deployment in which many DHCPv6=0A&gt;&gt;&g=
t; clients are sending Solicit messages but the DHCPv6 server has been=0A&g=
t;&gt;&gt; configured not to respond to those Solicit messages.=A0 RFC 3315=
 was=0A&gt;&gt;&gt; written with the expectation that the &#39;M&#39; and &=
#39;O&#39; flags in NDP=0A&gt;&gt;&gt; [RFC2461] would control the use of D=
HCPv6 by hosts.=A0 However, the=0A&gt;&gt;&gt; current definition of the &#=
39;M&#39; and &#39;O&#39; flags in RFC 4861 [RFC4861]=0A&gt;&gt;&gt; does n=
ot explicitly preclude the use of DHCPv6 by a host.=A0 Some=0A&gt;&gt;&gt; =
devices will initiate DHCPv6 even if RAs are received with the &#39;M&#39;=
=0A&gt;&gt;&gt; and &#39;O&#39; bits set to 0.=A0 In some circumstances, it=
 is desirable to=0A&gt;&gt;&gt; enable the assignment of IPv6 addresses thr=
ough DHCPv6 to some=0A&gt;&gt;&gt; nodes on a link but not to others, which=
 cannot be implemented=0A&gt;&gt;&gt; through the &#39;M&#39; and &#39;O&#3=
9; bits.=0A&gt;&gt;&gt; =0A&gt;&gt;&gt; Two issues to consider:=0A&gt;&gt;&=
gt; =0A&gt;&gt;&gt; 1. Is 3600 seconds the right number?=A0 How about 7200 =
seconds?=0A&gt;&gt;&gt; =0A&gt;&gt;&gt; 2. In a scenario in which the DHCPv=
6 service is unresponsive for SOL_MAX_RT and the DHCPv6 clients are all now=
 sending a Solicit every SOL_MAX_RT, the average wait time for those client=
s to complete the DHCPv6 message exchange after the DHCPv6 service comes ba=
ck up will be MAX_SOL_RT/2.=A0 Is that situation acceptable or should we de=
fine some other trigger through which the DHCPv6 clients can be signaled ex=
plicitly to restart the Solicit transmission algorithm in section 17.1.2 of=
 RFC 3315.=A0 My personal opinion is that an additional trigger is unnecess=
ary.=0A&gt;&gt;&gt; =0A&gt;&gt;&gt; - Ralph=0A&gt;&gt;&gt; =0A&gt;&gt;&gt; =
_______________________________________________=0A&gt;&gt;&gt; dhcwg mailin=
g list=0A&gt;&gt;&gt; dhcwg@ietf.org=0A&gt;&gt;&gt; https://www.ietf.org/ma=
ilman/listinfo/dhcwg=0A&gt;&gt; =0A&gt;=0A&gt;=0A&gt;=0A&gt;---------------=
---------------=0A&gt;=0A&gt;Message: 4=0A&gt;Date: Wed, 9 Nov 2011 17:21:0=
0 +0900=0A&gt;From: Arifumi Matsumoto &lt;arifumi@nttv6.net&gt;=0A&gt;To: &=
quot;dhcwg@ietf.org WG&quot; &lt;dhcwg@ietf.org&gt;=0A&gt;Subject: [dhcwg] =
reviews of draft-ietf-6man-addr-select-opt-01=0A&gt;Message-ID: &lt;EEA697B=
D-5981-45D9-A8B9-0551417CAAAD@nttv6.net&gt;=0A&gt;Content-Type: text/plain;=
 charset=3Dus-ascii=0A&gt;=0A&gt;All,=0A&gt;=0A&gt;at Quebec, Tim Chown pre=
sented about address selection documents=0A&gt;discussed in 6man WG, and re=
quested reviewers for the draft=0A&gt;draft-ietf-6man-addr-select-opt-01.=
=0A&gt;slides are http://tools.ietf.org/agenda/81/slides/dhc-13.pdf=0A&gt;=
=0A&gt;IIRC, one reviewer was chosen at that time, and the other was left=
=0A&gt;undecided.=0A&gt;=0A&gt;So, my questions are=0A&gt;the review was su=
bmitted somewhere ?=0A&gt;the other reviewer was chosen ?=0A&gt;=0A&gt;--=
=0A&gt;Arifumi Matsumoto=0A&gt;=A0 NGN System Architecture Project=0A&gt;=
=A0 NTT Service Integration Laboratories=0A&gt;=A0 E-mail: arifumi@nttv6.ne=
t=0A&gt;=A0 TEL +81-422-59-3334 FAX +81-422-59-6364=0A&gt;=0A&gt;=0A&gt;=0A=
&gt;------------------------------=0A&gt;=0A&gt;Message: 5=0A&gt;Date: Wed,=
 9 Nov 2011 15:12:09 +0530=0A&gt;From: VithalPrasad Gaitonde &lt;gvithal@gm=
ail.com&gt;=0A&gt;To: &quot;Brzozowski, John&quot; &lt;John_Brzozowski@cabl=
e.comcast.com&gt;=0A&gt;Cc: dhc WG &lt;dhcwg@ietf.org&gt;, Jack Chen &lt;ja=
ck.chen@twcable.com&gt;,=0A&gt;=A0=A0=A0 Jean-Francois Tremblay &lt;Jean-Fr=
ancois.TremblayING@videotron.com&gt;,=A0=A0=A0 Ted=0A&gt;=A0=A0=A0 Lemon &l=
t;Ted.Lemon@nominum.com&gt;=0A&gt;Subject: Re: [dhcwg] dhc-dhcpv6-redundanc=
y-consider-02 draft (post=0A&gt;=A0=A0=A0 WGLC)=0A&gt;Message-ID:=0A&gt;=A0=
=A0=A0 &lt;CAAfac2jqr5UcBAFm0uwy_qvs=3D44fkwT97A-FgbRc1Ja2fd-mvQ@mail.gmail=
.com&gt;=0A&gt;Content-Type: text/plain; charset=3D&quot;iso-8859-1&quot;=
=0A&gt;=0A&gt;The documentation of these redundancy approaches serves as a =
useful=0A&gt;guidance.=0A&gt;Support this document.=0A&gt;=0A&gt;Thanks,=0A=
&gt;Prasad=0A&gt;=0A&gt;On Tue, Nov 8, 2011 at 9:41 PM, Brzozowski, John &l=
t;=0A&gt;John_Brzozowski@cable.comcast.com&gt; wrote:=0A&gt;=0A&gt;&gt; I s=
upport this as well, from what we have heard this is useful information.=0A=
&gt;&gt;=0A&gt;&gt; John=0A&gt;&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=0A&gt;&gt; John Jason Brzozowski=0A&gt;&gt; Comcast Cable=0A&gt;&=
gt; e) mailto:john_brzozowski@cable.comcast.com=0A&gt;&gt; o) 609-377-6594=
=0A&gt;&gt; m) 484-962-0060=0A&gt;&gt; w) http://www.comcast6.net=0A&gt;&gt=
; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A&gt;&gt;=0A&gt;&gt;=
=0A&gt;&gt;=0A&gt;&gt;=0A&gt;&gt; On 11/8/11 10:13 AM, &quot;Tomek Mrugalsk=
i&quot; &lt;tomasz.mrugalski@gmail.com&gt; wrote:=0A&gt;&gt;=0A&gt;&gt; &gt=
;On 08.11.2011 13:02, Ted Lemon wrote:=0A&gt;&gt; &gt;&gt; On Oct 17, 2011,=
 at 11:11 AM, &quot;Tomasz Mrugalski&quot;=0A&gt;&gt; &gt;&gt; &lt;tomasz.m=
rugalski@gmail.com&gt; wrote:=0A&gt;&gt; &gt;&gt;&gt; This draft seem to su=
ccessfully pass WGLC=0A&gt;&gt; &gt;&gt;&gt; (http://www.ietf.org/mail-arch=
ive/web/dhcwg/current/msg11930.html).=0A&gt;&gt; &gt;&gt;=0A&gt;&gt; &gt;&g=
t;&gt;=0A&gt;&gt; &gt;&gt; Only one person actually expressed support for t=
his document, so in=0A&gt;&gt; &gt;&gt; fact it did not pass WGLC. however =
there were a number of comments,=0A&gt;&gt; &gt;&gt; so I presume there act=
ually is support.=A0 Cpuld those who want this to=0A&gt;&gt; &gt;&gt; be pu=
blished please formally indicate that they do?=0A&gt;&gt; &gt;I support thi=
s draft. As I&#39;m co-author, it probably doesn&#39;t count.=0A&gt;&gt; &g=
t;=0A&gt;&gt; &gt;Tomek=0A&gt;&gt;=0A&gt;&gt; _____________________________=
__________________=0A&gt;&gt; dhcwg mailing list=0A&gt;&gt; dhcwg@ietf.org=
=0A&gt;&gt; https://www.ietf.org/mailman/listinfo/dhcwg=0A&gt;&gt;=0A&gt;--=
------------ next part --------------=0A&gt;An HTML attachment was scrubbed=
...=0A&gt;URL: &lt;http://www.ietf.org/mail-archive/web/dhcwg/attachments/2=
0111109/f182bec5/attachment.htm&gt;=0A&gt;=0A&gt;--------------------------=
----=0A&gt;=0A&gt;Message: 6=0A&gt;Date: Wed, 9 Nov 2011 16:05:33 +0100=0A&=
gt;From: Marcus Goller &lt;mgoller@gmail.com&gt;=0A&gt;To: dhc WG &lt;dhcwg=
@ietf.org&gt;=0A&gt;Cc: Jack Chen &lt;jack.chen@twcable.com&gt;,=A0=A0=A0 J=
ean-Francois Tremblay=0A&gt;=A0=A0=A0 &lt;Jean-Francois.TremblayING@videotr=
on.com&gt;,=A0=A0=A0 Ted Lemon=0A&gt;=A0=A0=A0 &lt;Ted.Lemon@nominum.com&gt=
;=0A&gt;Subject: Re: [dhcwg] dhc-dhcpv6-redundancy-consider-02 draft (post=
=0A&gt;=A0=A0=A0 WGLC)=0A&gt;Message-ID:=0A&gt;=A0=A0=A0 &lt;CAMdbJyKP+vh1Z=
L-F-1avTUxv+sBMDNiEPnF4AStp=3Dn=3DfyqDSbw@mail.gmail.com&gt;=0A&gt;Content-=
Type: text/plain; charset=3DISO-8859-1=0A&gt;=0A&gt;I also think this very =
useful to have.=0A&gt;=0A&gt;Marcus=0A&gt;=0A&gt;On Wed, Nov 9, 2011 at 10:=
42 AM, VithalPrasad Gaitonde=0A&gt;&lt;gvithal@gmail.com&gt; wrote:=0A&gt;&=
gt; The documentation of these redundancy approaches serves as a useful=0A&=
gt;&gt; guidance.=0A&gt;&gt; Support this document.=0A&gt;&gt;=0A&gt;&gt; T=
hanks,=0A&gt;&gt; Prasad=0A&gt;&gt;=0A&gt;&gt; On Tue, Nov 8, 2011 at 9:41 =
PM, Brzozowski, John=0A&gt;&gt; &lt;John_Brzozowski@cable.comcast.com&gt; w=
rote:=0A&gt;&gt;&gt;=0A&gt;&gt;&gt; I support this as well, from what we ha=
ve heard this is useful=0A&gt;&gt;&gt; information.=0A&gt;&gt;&gt;=0A&gt;&g=
t;&gt; John=0A&gt;&gt;&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=0A&gt;&gt;&gt; John Jason Brzozowski=0A&gt;&gt;&gt; Comcast Cable=0A&gt;&g=
t;&gt; e) mailto:john_brzozowski@cable.comcast.com=0A&gt;&gt;&gt; o) 609-37=
7-6594=0A&gt;&gt;&gt; m) 484-962-0060=0A&gt;&gt;&gt; w) http://www.comcast6=
.net=0A&gt;&gt;&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A&gt=
;&gt;&gt;=0A&gt;&gt;&gt;=0A&gt;&gt;&gt;=0A&gt;&gt;&gt;=0A&gt;&gt;&gt; On 11=
/8/11 10:13 AM, &quot;Tomek Mrugalski&quot; &lt;tomasz.mrugalski@gmail.com&=
gt; wrote:=0A&gt;&gt;&gt;=0A&gt;&gt;&gt; &gt;On 08.11.2011 13:02, Ted Lemon=
 wrote:=0A&gt;&gt;&gt; &gt;&gt; On Oct 17, 2011, at 11:11 AM, &quot;Tomasz =
Mrugalski&quot;=0A&gt;&gt;&gt; &gt;&gt; &lt;tomasz.mrugalski@gmail.com&gt; =
wrote:=0A&gt;&gt;&gt; &gt;&gt;&gt; This draft seem to successfully pass WGL=
C=0A&gt;&gt;&gt; &gt;&gt;&gt; (http://www.ietf.org/mail-archive/web/dhcwg/c=
urrent/msg11930.html).=0A&gt;&gt;&gt; &gt;&gt;=0A&gt;&gt;&gt; &gt;&gt;&gt;=
=0A&gt;&gt;&gt; &gt;&gt; Only one person actually expressed support for thi=
s document, so in=0A&gt;&gt;&gt; &gt;&gt; fact it did not pass WGLC. howeve=
r there were a number of comments,=0A&gt;&gt;&gt; &gt;&gt; so I presume the=
re actually is support. ?Cpuld those who want this to=0A&gt;&gt;&gt; &gt;&g=
t; be published please formally indicate that they do?=0A&gt;&gt;&gt; &gt;I=
 support this draft. As I&#39;m co-author, it probably doesn&#39;t count.=
=0A&gt;&gt;&gt; &gt;=0A&gt;&gt;&gt; &gt;Tomek=0A&gt;&gt;&gt;=0A&gt;&gt;&gt;=
 _______________________________________________=0A&gt;&gt;&gt; dhcwg maili=
ng list=0A&gt;&gt;&gt; dhcwg@ietf.org=0A&gt;&gt;&gt; https://www.ietf.org/m=
ailman/listinfo/dhcwg=0A&gt;&gt;=0A&gt;&gt;=0A&gt;&gt; ____________________=
___________________________=0A&gt;&gt; dhcwg mailing list=0A&gt;&gt; dhcwg@=
ietf.org=0A&gt;&gt; https://www.ietf.org/mailman/listinfo/dhcwg=0A&gt;&gt;=
=0A&gt;&gt;=0A&gt;=0A&gt;=0A&gt;------------------------------=0A&gt;=0A&gt=
;_______________________________________________=0A&gt;dhcwg mailing list=
=0A&gt;dhcwg@ietf.org=0A&gt;https://www.ietf.org/mailman/listinfo/dhcwg=0A&=
gt;=0A&gt;=0A&gt;End of dhcwg Digest, Vol 91, Issue 7=0A&gt;***************=
*********************=0A&gt;=0A&gt;=0A&gt;
--776298407-1920564092-1320858407=:761
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

unsubscribe-ericjb3666@yahoo.com<div></div><div>&nbsp;</div><div><font colo=
r=3D"#ff0000">Eric Benitez</font></div><br><blockquote style=3D"border-left=
: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><div st=
yle=3D"font-family: times new roman, new york, times, serif; font-size: 12p=
t;"><div style=3D"font-family: times new roman, new york, times, serif; fon=
t-size: 12pt;"><font size=3D"2" face=3D"Arial"><hr size=3D"1"><b><span styl=
e=3D"font-weight:bold;">From:</span></b> &quot;dhcwg-request@ietf.org&quot;=
 &lt;dhcwg-request@ietf.org&gt;<br><b><span style=3D"font-weight: bold;">To=
:</span></b> dhcwg@ietf.org<br><b><span style=3D"font-weight: bold;">Sent:<=
/span></b> Wednesday, November 9, 2011 12:05 PM<br><b><span style=3D"font-w=
eight: bold;">Subject:</span></b> dhcwg Digest, Vol 91, Issue 7<br></font><=
br>If you have received this digest without all the individual message<BR>a=
ttachments you will need to update your digest options in your list<BR>subs=
cription.&nbsp;
 To do so, go to <BR><BR><a href=3D"https://www.ietf.org/mailman/listinfo/d=
hcwg" target=3D_blank >https://www.ietf.org/mailman/listinfo/dhcwg</a><BR><=
BR>Click the 'Unsubscribe or edit options' button, log in, and set "Get<BR>=
MIME or Plain Text Digests?" to MIME.&nbsp; You can set this option<BR>glob=
ally for all the list digests you receive at this point.<BR><BR><BR><BR>Sen=
d dhcwg mailing list submissions to<BR>&nbsp;&nbsp;&nbsp; <a ymailto=3D"mai=
lto:dhcwg@ietf.org" href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><BR><B=
R>To subscribe or unsubscribe via the World Wide Web, visit<BR>&nbsp;&nbsp;=
&nbsp; <a href=3D"https://www.ietf.org/mailman/listinfo/dhcwg" target=3D_bl=
ank >https://www.ietf.org/mailman/listinfo/dhcwg</a><BR>or, via email, send=
 a message with subject or body 'help' to<BR>&nbsp;&nbsp;&nbsp; <a ymailto=
=3D"mailto:dhcwg-request@ietf.org" href=3D"mailto:dhcwg-request@ietf.org">d=
hcwg-request@ietf.org</a><BR><BR>You can reach the person managing the list
 at<BR>&nbsp;&nbsp;&nbsp; <a ymailto=3D"mailto:dhcwg-owner@ietf.org" href=
=3D"mailto:dhcwg-owner@ietf.org">dhcwg-owner@ietf.org</a><BR><BR>When reply=
ing, please edit your Subject line so it is more specific<BR>than "Re: Cont=
ents of dhcwg digest..."<BR><BR><BR>Today's Topics:<BR><BR>&nbsp;  1. Re: P=
roposed change to MAX_SOL_RT (Ralph Droms)<BR>&nbsp;  2. Re: Proposed chang=
e to MAX_SOL_RT (Ole Troan)<BR>&nbsp;  3. Re: Proposed change to MAX_SOL_RT=
 (Ralph Droms)<BR>&nbsp;  4. reviews of draft-ietf-6man-addr-select-opt-01 =
(Arifumi Matsumoto)<BR>&nbsp;  5. Re: dhc-dhcpv6-redundancy-consider-02 dra=
ft (post WGLC)<BR>&nbsp; &nbsp; &nbsp; (VithalPrasad Gaitonde)<BR>&nbsp;  6=
. Re: dhc-dhcpv6-redundancy-consider-02 draft (post WGLC)<BR>&nbsp; &nbsp; =
&nbsp; (Marcus Goller)<BR><BR><BR>-----------------------------------------=
-----------------------------<BR><BR>Message: 1<BR>Date: Tue, 8 Nov 2011 15=
:22:02 -0500<BR>From: Ralph Droms &lt;<a
 ymailto=3D"mailto:rdroms.ietf@gmail.com" href=3D"mailto:rdroms.ietf@gmail.=
com">rdroms.ietf@gmail.com</a>&gt;<BR>To: "<a ymailto=3D"mailto:dhcwg@ietf.=
org" href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a> WG" &lt;<a ymailto=
=3D"mailto:dhcwg@ietf.org" href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a=
>&gt;<BR>Subject: Re: [dhcwg] Proposed change to MAX_SOL_RT<BR>Message-ID: =
&lt;<a ymailto=3D"mailto:D494B897-6773-4D92-9435-5E165B4306EA@gmail.com" hr=
ef=3D"mailto:D494B897-6773-4D92-9435-5E165B4306EA@gmail.com">D494B897-6773-=
4D92-9435-5E165B4306EA@gmail.com</a>&gt;<BR>Content-Type: text/plain; chars=
et=3Dus-ascii<BR><BR>Followup to previous message about changing MAX_SOL_RT=
...<BR><BR>On Nov 4, 2011, at 7:33 AM 11/4/11, Ralph Droms wrote:<BR>&gt; <=
BR>&gt; 2. In a scenario in which the DHCPv6 service is unresponsive for SO=
L_MAX_RT and the DHCPv6 clients are all now sending a Solicit every SOL_MAX=
_RT, the average wait time for those clients to complete the DHCPv6 message=
 exchange
 after the DHCPv6 service comes back up will be MAX_SOL_RT/2.&nbsp; Is that=
 situation acceptable or should we define some other trigger through which =
the DHCPv6 clients can be signaled explicitly to restart the Solicit transm=
ission algorithm in section 17.1.2 of RFC 3315.&nbsp; My personal opinion i=
s that an additional trigger is unnecessary.<BR><BR>In support of my opinio=
n, I came up with the following analysis of the likelihood of a client gett=
ing to the long-term MAX_SOL_RT interval state. <BR><BR>If the CM and CE ro=
uter have been up and running, with the CE configured through DHCPv6, a WAN=
 link flap will have no effect on DHCPv6 unless the link is down past the a=
ddress/PD lease expiration...and in this case, the CE router will lose conn=
ectivity regardless.<BR><BR>If the CE router comes up without a valid addre=
ss/PD lease before the DHCPv6 service is running, the CE router will get to=
 the long-term state of waiting on average MAX_SOL_RT/2 only if the
 DHCPv6 service is down longer than MAX_SOL_RT/2.&nbsp; Note that this situ=
ation will only occur if the CE router is coming up for the first time or c=
oming up after its address/PD lease has expired.<BR><BR>So, a DHCPv6 client=
 can get to that long-term state sending a Solicit every MAX_SOL_RT interva=
l, but I don't think it's very likely.<BR><BR>Discussion welcome and encour=
aged.<BR><BR>- Ralph<BR><BR><BR><BR>------------------------------<BR><BR>M=
essage: 2<BR>Date: Tue, 8 Nov 2011 21:39:58 +0100<BR>From: Ole Troan &lt;<a=
 ymailto=3D"mailto:otroan@employees.org" href=3D"mailto:otroan@employees.or=
g">otroan@employees.org</a>&gt;<BR>To: Ralph Droms &lt;<a ymailto=3D"mailto=
:rdroms.ietf@gmail.com" href=3D"mailto:rdroms.ietf@gmail.com">rdroms.ietf@g=
mail.com</a>&gt;<BR>Cc: "<a ymailto=3D"mailto:dhcwg@ietf.org" href=3D"mailt=
o:dhcwg@ietf.org">dhcwg@ietf.org</a> WG" &lt;<a ymailto=3D"mailto:dhcwg@iet=
f.org" href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>&gt;<BR>Subject: Re=
: [dhcwg]
 Proposed change to MAX_SOL_RT<BR>Message-ID: &lt;<a ymailto=3D"mailto:9081=
3655-0402-49B6-9C62-234D9BA2A510@employees.org" href=3D"mailto:90813655-040=
2-49B6-9C62-234D9BA2A510@employees.org">90813655-0402-49B6-9C62-234D9BA2A51=
0@employees.org</a>&gt;<BR>Content-Type: text/plain; charset=3Dus-ascii<BR>=
<BR>Ralph,<BR><BR>before we jump to conclusions and change the spec, I woul=
d very much like to understand this better.<BR>the issue here is a DHCP ser=
ver receiving SOLICITS from clients that it is unwilling to serve, right?<B=
R>and that all solicits are going to be discarded, not replied to and creat=
ed a binding for.<BR><BR>assuming a million DHCPv6 clients with a 120 secon=
d timeout that's ~8333 solicits/s.<BR>can't a vanilla DHCP server implement=
ation handle that? <BR><BR>if a solicit packet is 150 bytes, that's only a =
~12Mbps datastream...<BR><BR>cheers,<BR>Ole<BR><BR><BR><BR>On Nov 4, 2011, =
at 12:33 , Ralph Droms wrote:<BR><BR>&gt; I've asked the chairs for a
 short slot in the Taipei WG meeting to discuss draft-droms-dhc-dhcpv6-maxs=
olrt-update-00.&nbsp; While the doc won't officially be published until I-D=
 publication quiet period ends, the important text of the draft is only 2 p=
aragraphs, so I'm posting it now to encourage discussion prior to the WG me=
eting.<BR>&gt; <BR>&gt; Here is text of the doc:<BR>&gt; <BR>&gt; Abstract<=
BR>&gt; <BR>&gt;&nbsp; This document updates RFC 3315 by defining a new def=
ault value for<BR>&gt;&nbsp; SOL_MAX_RT.<BR>&gt; <BR>&gt; 1.&nbsp; Introduc=
tion<BR>&gt; <BR>&gt;&nbsp; Section 5.5 of the DHCP specification [RFC3315]=
 defines the default<BR>&gt;&nbsp; value of MAX_SOL_RT to be 120 seconds.&n=
bsp; In some circumstances, this<BR>&gt;&nbsp; default will lead to an unac=
ceptably high volume of aggregated<BR>&gt;&nbsp; traffic at a DHCPv6 server=
.<BR>&gt; <BR>&gt; 2.&nbsp; Update to RC 3315<BR>&gt; <BR>&gt;&nbsp; This d=
ocument changes section 5.5 of RFC 3315 as follows:<BR>&gt;
 <BR>&gt;&nbsp; OLD:<BR>&gt;&nbsp; &nbsp;  SOL_MAX_RT&nbsp; &nbsp; &nbsp; 1=
20 secs&nbsp; Max Solicit timeout value<BR>&gt; <BR>&gt;&nbsp; NEW:<BR>&gt;=
&nbsp; &nbsp;  SOL_MAX_RT&nbsp; &nbsp;  3600 secs&nbsp; Max Solicit timeout=
 value<BR>&gt; <BR>&gt;&nbsp; With this change, a DHCPv6 client that does n=
ot receive a<BR>&gt;&nbsp; satisfactory response will send Solicit messages=
 with the same<BR>&gt;&nbsp; initial frequency and exponential backoff as s=
pecified in RFC 3315.<BR>&gt;&nbsp; However, the long term behavior of thes=
e DHCPv6 clients will be to<BR>&gt;&nbsp; send a Solicit message every 3600=
 seconds rather than every 120<BR>&gt;&nbsp; seconds, significantly reducin=
g the aggregated traffic at the DHCPv6<BR>&gt;&nbsp; server.<BR>&gt; <BR>&g=
t;&nbsp; The change to MAX_SOL_RT is in response to DHCPv6 message rates<BR=
>&gt;&nbsp; observed at a DHCPv6 server in a deployment in which many DHCPv=
6<BR>&gt;&nbsp; clients are sending Solicit messages but the DHCPv6
 server has been<BR>&gt;&nbsp; configured not to respond to those Solicit m=
essages.&nbsp; RFC 3315 was<BR>&gt;&nbsp; written with the expectation that=
 the 'M' and 'O' flags in NDP<BR>&gt;&nbsp; [RFC2461] would control the use=
 of DHCPv6 by hosts.&nbsp; However, the<BR>&gt;&nbsp; current definition of=
 the 'M' and 'O' flags in RFC 4861 [RFC4861]<BR>&gt;&nbsp; does not explici=
tly preclude the use of DHCPv6 by a host.&nbsp; Some<BR>&gt;&nbsp; devices =
will initiate DHCPv6 even if RAs are received with the 'M'<BR>&gt;&nbsp; an=
d 'O' bits set to 0.&nbsp; In some circumstances, it is desirable to<BR>&gt=
;&nbsp; enable the assignment of IPv6 addresses through DHCPv6 to some<BR>&=
gt;&nbsp; nodes on a link but not to others, which cannot be implemented<BR=
>&gt;&nbsp; through the 'M' and 'O' bits.<BR>&gt; <BR>&gt; Two issues to co=
nsider:<BR>&gt; <BR>&gt; 1. Is 3600 seconds the right number?&nbsp; How abo=
ut 7200 seconds?<BR>&gt; <BR>&gt; 2. In a scenario in which the
 DHCPv6 service is unresponsive for SOL_MAX_RT and the DHCPv6 clients are a=
ll now sending a Solicit every SOL_MAX_RT, the average wait time for those =
clients to complete the DHCPv6 message exchange after the DHCPv6 service co=
mes back up will be MAX_SOL_RT/2.&nbsp; Is that situation acceptable or sho=
uld we define some other trigger through which the DHCPv6 clients can be si=
gnaled explicitly to restart the Solicit transmission algorithm in section =
17.1.2 of RFC 3315.&nbsp; My personal opinion is that an additional trigger=
 is unnecessary.<BR>&gt; <BR>&gt; - Ralph<BR>&gt; <BR>&gt; ________________=
_______________________________<BR>&gt; dhcwg mailing list<BR>&gt; <a ymail=
to=3D"mailto:dhcwg@ietf.org" href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org<=
/a><BR>&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/dhcwg" target=
=3D_blank >https://www.ietf.org/mailman/listinfo/dhcwg</a><BR><BR><BR><BR>-=
-----------------------------<BR><BR>Message: 3<BR>Date: Tue, 8 Nov 2011
 15:54:02 -0500<BR>From: Ralph Droms &lt;<a ymailto=3D"mailto:rdroms.ietf@g=
mail.com" href=3D"mailto:rdroms.ietf@gmail.com">rdroms.ietf@gmail.com</a>&g=
t;<BR>To: Ole Troan &lt;<a ymailto=3D"mailto:otroan@employees.org" href=3D"=
mailto:otroan@employees.org">otroan@employees.org</a>&gt;<BR>Cc: "<a ymailt=
o=3D"mailto:dhcwg@ietf.org" href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</=
a> WG" &lt;<a ymailto=3D"mailto:dhcwg@ietf.org" href=3D"mailto:dhcwg@ietf.o=
rg">dhcwg@ietf.org</a>&gt;<BR>Subject: Re: [dhcwg] Proposed change to MAX_S=
OL_RT<BR>Message-ID: &lt;<a ymailto=3D"mailto:1953942C-2180-4AB6-9170-F20A7=
BF3C898@gmail.com" href=3D"mailto:1953942C-2180-4AB6-9170-F20A7BF3C898@gmai=
l.com">1953942C-2180-4AB6-9170-F20A7BF3C898@gmail.com</a>&gt;<BR>Content-Ty=
pe: text/plain; charset=3Dus-ascii<BR><BR><BR>On Nov 8, 2011, at 3:39 PM 11=
/8/11, Ole Troan wrote:<BR><BR>&gt; Ralph,<BR>&gt; <BR>&gt; before we jump =
to conclusions and change the spec, I would very much like to understand th=
is
 better.<BR>&gt; the issue here is a DHCP server receiving SOLICITS from cl=
ients that it is unwilling to serve, right?<BR>&gt; and that all solicits a=
re going to be discarded, not replied to and created a binding for.<BR><BR>=
Right.<BR><BR>&gt; assuming a million DHCPv6 clients with a 120 second time=
out that's ~8333 solicits/s.<BR>&gt; can't a vanilla DHCP server implementa=
tion handle that? <BR><BR>On the other hand, that stream of Solicits may re=
present a 100x increase over the level of traffic in the steady state.<BR><=
BR>- Ralph<BR><BR>&gt; if a solicit packet is 150 bytes, that's only a ~12M=
bps datastream...<BR>&gt; <BR>&gt; cheers,<BR>&gt; Ole<BR>&gt; <BR>&gt; <BR=
>&gt; <BR>&gt; On Nov 4, 2011, at 12:33 , Ralph Droms wrote:<BR>&gt; <BR>&g=
t;&gt; I've asked the chairs for a short slot in the Taipei WG meeting to d=
iscuss draft-droms-dhc-dhcpv6-maxsolrt-update-00.&nbsp; While the doc won't=
 officially be published until I-D publication quiet period ends,
 the important text of the draft is only 2 paragraphs, so I'm posting it no=
w to encourage discussion prior to the WG meeting.<BR>&gt;&gt; <BR>&gt;&gt;=
 Here is text of the doc:<BR>&gt;&gt; <BR>&gt;&gt; Abstract<BR>&gt;&gt; <BR=
>&gt;&gt; This document updates RFC 3315 by defining a new default value fo=
r<BR>&gt;&gt; SOL_MAX_RT.<BR>&gt;&gt; <BR>&gt;&gt; 1.&nbsp; Introduction<BR=
>&gt;&gt; <BR>&gt;&gt; Section 5.5 of the DHCP specification [RFC3315] defi=
nes the default<BR>&gt;&gt; value of MAX_SOL_RT to be 120 seconds.&nbsp; In=
 some circumstances, this<BR>&gt;&gt; default will lead to an unacceptably =
high volume of aggregated<BR>&gt;&gt; traffic at a DHCPv6 server.<BR>&gt;&g=
t; <BR>&gt;&gt; 2.&nbsp; Update to RC 3315<BR>&gt;&gt; <BR>&gt;&gt; This do=
cument changes section 5.5 of RFC 3315 as follows:<BR>&gt;&gt; <BR>&gt;&gt;=
 OLD:<BR>&gt;&gt;&nbsp; &nbsp; SOL_MAX_RT&nbsp; &nbsp; &nbsp; 120 secs&nbsp=
; Max Solicit timeout value<BR>&gt;&gt; <BR>&gt;&gt;
 NEW:<BR>&gt;&gt;&nbsp; &nbsp; SOL_MAX_RT&nbsp; &nbsp;  3600 secs&nbsp; Max=
 Solicit timeout value<BR>&gt;&gt; <BR>&gt;&gt; With this change, a DHCPv6 =
client that does not receive a<BR>&gt;&gt; satisfactory response will send =
Solicit messages with the same<BR>&gt;&gt; initial frequency and exponentia=
l backoff as specified in RFC 3315.<BR>&gt;&gt; However, the long term beha=
vior of these DHCPv6 clients will be to<BR>&gt;&gt; send a Solicit message =
every 3600 seconds rather than every 120<BR>&gt;&gt; seconds, significantly=
 reducing the aggregated traffic at the DHCPv6<BR>&gt;&gt; server.<BR>&gt;&=
gt; <BR>&gt;&gt; The change to MAX_SOL_RT is in response to DHCPv6 message =
rates<BR>&gt;&gt; observed at a DHCPv6 server in a deployment in which many=
 DHCPv6<BR>&gt;&gt; clients are sending Solicit messages but the DHCPv6 ser=
ver has been<BR>&gt;&gt; configured not to respond to those Solicit message=
s.&nbsp; RFC 3315 was<BR>&gt;&gt; written with the expectation that
 the 'M' and 'O' flags in NDP<BR>&gt;&gt; [RFC2461] would control the use o=
f DHCPv6 by hosts.&nbsp; However, the<BR>&gt;&gt; current definition of the=
 'M' and 'O' flags in RFC 4861 [RFC4861]<BR>&gt;&gt; does not explicitly pr=
eclude the use of DHCPv6 by a host.&nbsp; Some<BR>&gt;&gt; devices will ini=
tiate DHCPv6 even if RAs are received with the 'M'<BR>&gt;&gt; and 'O' bits=
 set to 0.&nbsp; In some circumstances, it is desirable to<BR>&gt;&gt; enab=
le the assignment of IPv6 addresses through DHCPv6 to some<BR>&gt;&gt; node=
s on a link but not to others, which cannot be implemented<BR>&gt;&gt; thro=
ugh the 'M' and 'O' bits.<BR>&gt;&gt; <BR>&gt;&gt; Two issues to consider:<=
BR>&gt;&gt; <BR>&gt;&gt; 1. Is 3600 seconds the right number?&nbsp; How abo=
ut 7200 seconds?<BR>&gt;&gt; <BR>&gt;&gt; 2. In a scenario in which the DHC=
Pv6 service is unresponsive for SOL_MAX_RT and the DHCPv6 clients are all n=
ow sending a Solicit every SOL_MAX_RT, the average wait time for
 those clients to complete the DHCPv6 message exchange after the DHCPv6 ser=
vice comes back up will be MAX_SOL_RT/2.&nbsp; Is that situation acceptable=
 or should we define some other trigger through which the DHCPv6 clients ca=
n be signaled explicitly to restart the Solicit transmission algorithm in s=
ection 17.1.2 of RFC 3315.&nbsp; My personal opinion is that an additional =
trigger is unnecessary.<BR>&gt;&gt; <BR>&gt;&gt; - Ralph<BR>&gt;&gt; <BR>&g=
t;&gt; _______________________________________________<BR>&gt;&gt; dhcwg ma=
iling list<BR>&gt;&gt; <a ymailto=3D"mailto:dhcwg@ietf.org" href=3D"mailto:=
dhcwg@ietf.org">dhcwg@ietf.org</a><BR>&gt;&gt; <a href=3D"https://www.ietf.=
org/mailman/listinfo/dhcwg" target=3D_blank >https://www.ietf.org/mailman/l=
istinfo/dhcwg</a><BR>&gt; <BR><BR><BR><BR>------------------------------<BR=
><BR>Message: 4<BR>Date: Wed, 9 Nov 2011 17:21:00 +0900<BR>From: Arifumi Ma=
tsumoto &lt;<a ymailto=3D"mailto:arifumi@nttv6.net"
 href=3D"mailto:arifumi@nttv6.net">arifumi@nttv6.net</a>&gt;<BR>To: "<a yma=
ilto=3D"mailto:dhcwg@ietf.org" href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.or=
g</a> WG" &lt;<a ymailto=3D"mailto:dhcwg@ietf.org" href=3D"mailto:dhcwg@iet=
f.org">dhcwg@ietf.org</a>&gt;<BR>Subject: [dhcwg] reviews of draft-ietf-6ma=
n-addr-select-opt-01<BR>Message-ID: &lt;<a ymailto=3D"mailto:EEA697BD-5981-=
45D9-A8B9-0551417CAAAD@nttv6.net" href=3D"mailto:EEA697BD-5981-45D9-A8B9-05=
51417CAAAD@nttv6.net">EEA697BD-5981-45D9-A8B9-0551417CAAAD@nttv6.net</a>&gt=
;<BR>Content-Type: text/plain; charset=3Dus-ascii<BR><BR>All,<BR><BR>at Que=
bec, Tim Chown presented about address selection documents<BR>discussed in =
6man WG, and requested reviewers for the draft<BR>draft-ietf-6man-addr-sele=
ct-opt-01.<BR>slides are <a href=3D"http://tools.ietf.org/agenda/81/slides/=
dhc-13.pdf" target=3D_blank >http://tools.ietf.org/agenda/81/slides/dhc-13.=
pdf</a><BR><BR>IIRC, one reviewer was chosen at that time, and the other wa=
s
 left<BR>undecided.<BR><BR>So, my questions are<BR>the review was submitted=
 somewhere ?<BR>the other reviewer was chosen ?<BR><BR>--<BR>Arifumi Matsum=
oto<BR>&nbsp; NGN System Architecture Project<BR>&nbsp; NTT Service Integra=
tion Laboratories<BR>&nbsp; E-mail: <a ymailto=3D"mailto:arifumi@nttv6.net"=
 href=3D"mailto:arifumi@nttv6.net">arifumi@nttv6.net</a><BR>&nbsp; TEL +81-=
422-59-3334 FAX +81-422-59-6364<BR><BR><BR><BR>----------------------------=
--<BR><BR>Message: 5<BR>Date: Wed, 9 Nov 2011 15:12:09 +0530<BR>From: Vitha=
lPrasad Gaitonde &lt;<a ymailto=3D"mailto:gvithal@gmail.com" href=3D"mailto=
:gvithal@gmail.com">gvithal@gmail.com</a>&gt;<BR>To: "Brzozowski, John" &lt=
;<a ymailto=3D"mailto:John_Brzozowski@cable.comcast.com" href=3D"mailto:Joh=
n_Brzozowski@cable.comcast.com">John_Brzozowski@cable.comcast.com</a>&gt;<B=
R>Cc: dhc WG &lt;<a ymailto=3D"mailto:dhcwg@ietf.org" href=3D"mailto:dhcwg@=
ietf.org">dhcwg@ietf.org</a>&gt;, Jack Chen &lt;<a
 ymailto=3D"mailto:jack.chen@twcable.com" href=3D"mailto:jack.chen@twcable.=
com">jack.chen@twcable.com</a>&gt;,<BR>&nbsp;&nbsp;&nbsp; Jean-Francois Tre=
mblay &lt;<a ymailto=3D"mailto:Jean-Francois.TremblayING@videotron.com" hre=
f=3D"mailto:Jean-Francois.TremblayING@videotron.com">Jean-Francois.Tremblay=
ING@videotron.com</a>&gt;,&nbsp;&nbsp;&nbsp; Ted<BR>&nbsp;&nbsp;&nbsp; Lemo=
n &lt;<a ymailto=3D"mailto:Ted.Lemon@nominum.com" href=3D"mailto:Ted.Lemon@=
nominum.com">Ted.Lemon@nominum.com</a>&gt;<BR>Subject: Re: [dhcwg] dhc-dhcp=
v6-redundancy-consider-02 draft (post<BR>&nbsp;&nbsp;&nbsp; WGLC)<BR>Messag=
e-ID:<BR>&nbsp;&nbsp;&nbsp; &lt;CAAfac2jqr5UcBAFm0uwy_qvs=3D<a ymailto=3D"m=
ailto:44fkwT97A-FgbRc1Ja2fd-mvQ@mail.gmail.com" href=3D"mailto:44fkwT97A-Fg=
bRc1Ja2fd-mvQ@mail.gmail.com">44fkwT97A-FgbRc1Ja2fd-mvQ@mail.gmail.com</a>&=
gt;<BR>Content-Type: text/plain; charset=3D"iso-8859-1"<BR><BR>The document=
ation of these redundancy approaches serves as a useful<BR>guidance.<BR>Sup=
port this
 document.<BR><BR>Thanks,<BR>Prasad<BR><BR>On Tue, Nov 8, 2011 at 9:41 PM, =
Brzozowski, John &lt;<BR><a ymailto=3D"mailto:John_Brzozowski@cable.comcast=
.com" href=3D"mailto:John_Brzozowski@cable.comcast.com">John_Brzozowski@cab=
le.comcast.com</a>&gt; wrote:<BR><BR>&gt; I support this as well, from what=
 we have heard this is useful information.<BR>&gt;<BR>&gt; John<BR>&gt; =3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>&gt; John Jason Brzozowski=
<BR>&gt; Comcast Cable<BR>&gt; e) mailto:<a ymailto=3D"mailto:john_brzozows=
ki@cable.comcast.com" href=3D"mailto:john_brzozowski@cable.comcast.com">joh=
n_brzozowski@cable.comcast.com</a><BR>&gt; o) 609-377-6594<BR>&gt; m) 484-9=
62-0060<BR>&gt; w) <a href=3D"http://www.comcast6.net" target=3D_blank >htt=
p://www.comcast6.net</a><BR>&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; On 11/8/11 10:13 AM, "Tomek =
Mrugalski" &lt;<a ymailto=3D"mailto:tomasz.mrugalski@gmail.com"
 href=3D"mailto:tomasz.mrugalski@gmail.com">tomasz.mrugalski@gmail.com</a>&=
gt; wrote:<BR>&gt;<BR>&gt; &gt;On 08.11.2011 13:02, Ted Lemon wrote:<BR>&gt=
; &gt;&gt; On Oct 17, 2011, at 11:11 AM, "Tomasz Mrugalski"<BR>&gt; &gt;&gt=
; &lt;<a ymailto=3D"mailto:tomasz.mrugalski@gmail.com" href=3D"mailto:tomas=
z.mrugalski@gmail.com">tomasz.mrugalski@gmail.com</a>&gt; wrote:<BR>&gt; &g=
t;&gt;&gt; This draft seem to successfully pass WGLC<BR>&gt; &gt;&gt;&gt; (=
<a href=3D"http://www.ietf.org/mail-archive/web/dhcwg/current/msg11930.html=
" target=3D_blank >http://www.ietf.org/mail-archive/web/dhcwg/current/msg11=
930.html</a>).<BR>&gt; &gt;&gt;<BR>&gt; &gt;&gt;&gt;<BR>&gt; &gt;&gt; Only =
one person actually expressed support for this document, so in<BR>&gt; &gt;=
&gt; fact it did not pass WGLC. however there were a number of comments,<BR=
>&gt; &gt;&gt; so I presume there actually is support.&nbsp; Cpuld those wh=
o want this to<BR>&gt; &gt;&gt; be published please formally indicate that
 they do?<BR>&gt; &gt;I support this draft. As I'm co-author, it probably d=
oesn't count.<BR>&gt; &gt;<BR>&gt; &gt;Tomek<BR>&gt;<BR>&gt; ______________=
_________________________________<BR>&gt; dhcwg mailing list<BR>&gt; <a yma=
ilto=3D"mailto:dhcwg@ietf.org" href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.or=
g</a><BR>&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/dhcwg" targe=
t=3D_blank >https://www.ietf.org/mailman/listinfo/dhcwg</a><BR>&gt;<BR>----=
---------- next part --------------<BR>An HTML attachment was scrubbed...<B=
R>URL: &lt;<a href=3D"http://www.ietf.org/mail-archive/web/dhcwg/attachment=
s/20111109/f182bec5/attachment.htm" target=3D_blank >http://www.ietf.org/ma=
il-archive/web/dhcwg/attachments/20111109/f182bec5/attachment.htm</a>&gt;<B=
R><BR>------------------------------<BR><BR>Message: 6<BR>Date: Wed, 9 Nov =
2011 16:05:33 +0100<BR>From: Marcus Goller &lt;<a ymailto=3D"mailto:mgoller=
@gmail.com" href=3D"mailto:mgoller@gmail.com">mgoller@gmail.com</a>&gt;<BR>=
To: dhc
 WG &lt;<a ymailto=3D"mailto:dhcwg@ietf.org" href=3D"mailto:dhcwg@ietf.org"=
>dhcwg@ietf.org</a>&gt;<BR>Cc: Jack Chen &lt;<a ymailto=3D"mailto:jack.chen=
@twcable.com" href=3D"mailto:jack.chen@twcable.com">jack.chen@twcable.com</=
a>&gt;,&nbsp;&nbsp;&nbsp; Jean-Francois Tremblay<BR>&nbsp;&nbsp;&nbsp; &lt;=
<a ymailto=3D"mailto:Jean-Francois.TremblayING@videotron.com" href=3D"mailt=
o:Jean-Francois.TremblayING@videotron.com">Jean-Francois.TremblayING@videot=
ron.com</a>&gt;,&nbsp;&nbsp;&nbsp; Ted Lemon<BR>&nbsp;&nbsp;&nbsp; &lt;<a y=
mailto=3D"mailto:Ted.Lemon@nominum.com" href=3D"mailto:Ted.Lemon@nominum.co=
m">Ted.Lemon@nominum.com</a>&gt;<BR>Subject: Re: [dhcwg] dhc-dhcpv6-redunda=
ncy-consider-02 draft (post<BR>&nbsp;&nbsp;&nbsp; WGLC)<BR>Message-ID:<BR>&=
nbsp;&nbsp;&nbsp; &lt;CAMdbJyKP+vh1ZL-F-1avTUxv+sBMDNiEPnF4AStp=3Dn=3D<a ym=
ailto=3D"mailto:fyqDSbw@mail.gmail.com" href=3D"mailto:fyqDSbw@mail.gmail.c=
om">fyqDSbw@mail.gmail.com</a>&gt;<BR>Content-Type: text/plain; charset=3DI=
SO-8859-1<BR><BR>I
 also think this very useful to have.<BR><BR>Marcus<BR><BR>On Wed, Nov 9, 2=
011 at 10:42 AM, VithalPrasad Gaitonde<BR>&lt;<a ymailto=3D"mailto:gvithal@=
gmail.com" href=3D"mailto:gvithal@gmail.com">gvithal@gmail.com</a>&gt; wrot=
e:<BR>&gt; The documentation of these redundancy approaches serves as a use=
ful<BR>&gt; guidance.<BR>&gt; Support this document.<BR>&gt;<BR>&gt; Thanks=
,<BR>&gt; Prasad<BR>&gt;<BR>&gt; On Tue, Nov 8, 2011 at 9:41 PM, Brzozowski=
, John<BR>&gt; &lt;<a ymailto=3D"mailto:John_Brzozowski@cable.comcast.com" =
href=3D"mailto:John_Brzozowski@cable.comcast.com">John_Brzozowski@cable.com=
cast.com</a>&gt; wrote:<BR>&gt;&gt;<BR>&gt;&gt; I support this as well, fro=
m what we have heard this is useful<BR>&gt;&gt; information.<BR>&gt;&gt;<BR=
>&gt;&gt; John<BR>&gt;&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
<BR>&gt;&gt; John Jason Brzozowski<BR>&gt;&gt; Comcast Cable<BR>&gt;&gt; e)=
 mailto:<a ymailto=3D"mailto:john_brzozowski@cable.comcast.com"
 href=3D"mailto:john_brzozowski@cable.comcast.com">john_brzozowski@cable.co=
mcast.com</a><BR>&gt;&gt; o) 609-377-6594<BR>&gt;&gt; m) 484-962-0060<BR>&g=
t;&gt; w) <a href=3D"http://www.comcast6.net" target=3D_blank >http://www.c=
omcast6.net</a><BR>&gt;&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D<BR>&gt;&gt;<BR>&gt;&gt;<BR>&gt;&gt;<BR>&gt;&gt;<BR>&gt;&gt; On 11/8/11 =
10:13 AM, "Tomek Mrugalski" &lt;<a ymailto=3D"mailto:tomasz.mrugalski@gmail=
.com" href=3D"mailto:tomasz.mrugalski@gmail.com">tomasz.mrugalski@gmail.com=
</a>&gt; wrote:<BR>&gt;&gt;<BR>&gt;&gt; &gt;On 08.11.2011 13:02, Ted Lemon =
wrote:<BR>&gt;&gt; &gt;&gt; On Oct 17, 2011, at 11:11 AM, "Tomasz Mrugalski=
"<BR>&gt;&gt; &gt;&gt; &lt;<a ymailto=3D"mailto:tomasz.mrugalski@gmail.com"=
 href=3D"mailto:tomasz.mrugalski@gmail.com">tomasz.mrugalski@gmail.com</a>&=
gt; wrote:<BR>&gt;&gt; &gt;&gt;&gt; This draft seem to successfully pass WG=
LC<BR>&gt;&gt; &gt;&gt;&gt; (<a
 href=3D"http://www.ietf.org/mail-archive/web/dhcwg/current/msg11930.html" =
target=3D_blank >http://www.ietf.org/mail-archive/web/dhcwg/current/msg1193=
0.html</a>).<BR>&gt;&gt; &gt;&gt;<BR>&gt;&gt; &gt;&gt;&gt;<BR>&gt;&gt; &gt;=
&gt; Only one person actually expressed support for this document, so in<BR=
>&gt;&gt; &gt;&gt; fact it did not pass WGLC. however there were a number o=
f comments,<BR>&gt;&gt; &gt;&gt; so I presume there actually is support. ?C=
puld those who want this to<BR>&gt;&gt; &gt;&gt; be published please formal=
ly indicate that they do?<BR>&gt;&gt; &gt;I support this draft. As I'm co-a=
uthor, it probably doesn't count.<BR>&gt;&gt; &gt;<BR>&gt;&gt; &gt;Tomek<BR=
>&gt;&gt;<BR>&gt;&gt; _______________________________________________<BR>&g=
t;&gt; dhcwg mailing list<BR>&gt;&gt; <a ymailto=3D"mailto:dhcwg@ietf.org" =
href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><BR>&gt;&gt; <a href=3D"ht=
tps://www.ietf.org/mailman/listinfo/dhcwg" target=3D_blank
 >https://www.ietf.org/mailman/listinfo/dhcwg</a><BR>&gt;<BR>&gt;<BR>&gt; _=
______________________________________________<BR>&gt; dhcwg mailing list<B=
R>&gt; <a ymailto=3D"mailto:dhcwg@ietf.org" href=3D"mailto:dhcwg@ietf.org">=
dhcwg@ietf.org</a><BR>&gt; <a href=3D"https://www.ietf.org/mailman/listinfo=
/dhcwg" target=3D_blank >https://www.ietf.org/mailman/listinfo/dhcwg</a><BR=
>&gt;<BR>&gt;<BR><BR><BR>------------------------------<BR><BR>____________=
___________________________________<BR>dhcwg mailing list<BR><a ymailto=3D"=
mailto:dhcwg@ietf.org" href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><BR=
><a href=3D"https://www.ietf.org/mailman/listinfo/dhcwg" target=3D_blank >h=
ttps://www.ietf.org/mailman/listinfo/dhcwg</a><BR><BR><BR>End of dhcwg Dige=
st, Vol 91, Issue 7<BR>************************************<BR><br><br></di=
v></div></blockquote>
--776298407-1920564092-1320858407=:761--

From Jean-Francois.TremblayING@videotron.com  Thu Nov 10 07:19:20 2011
Return-Path: <Jean-Francois.TremblayING@videotron.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 0D54321F8AB8 for <dhcwg@ietfa.amsl.com>; Thu, 10 Nov 2011 07:19:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001]
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 FdWcXxtblG9x for <dhcwg@ietfa.amsl.com>; Thu, 10 Nov 2011 07:19:19 -0800 (PST)
Received: from mx01.videotron.com (mx01.videotron.com [24.201.243.152]) by ietfa.amsl.com (Postfix) with ESMTP id 866C521F8AAA for <dhcwg@ietf.org>; Thu, 10 Nov 2011 07:19:19 -0800 (PST)
In-Reply-To: <CADEBEBD.1AB385%john_brzozowski@cable.comcast.com>
To: dhc WG <dhcwg@ietf.org>
MIME-Version: 1.0
X-KeepSent: 2E5BD6FC:CCD29895-85257944:0050C4A8; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006
Message-ID: <OF2E5BD6FC.CCD29895-ON85257944.0050C4A8-85257944.0054269A@videotron.com>
From: Jean-Francois.TremblayING@videotron.com
Date: Thu, 10 Nov 2011 10:19:07 -0500
X-MIMETrack: Serialize by Router on DOMMSG01/SRV/GVL(Release 8.5.2FP2|March 22, 2011) at 11/10/2011 10:19:08, Serialize complete at 11/10/2011 10:19:08
Content-Type: multipart/alternative; boundary="=_alternative 0054269785257944_="
X-Mailman-Approved-At: Thu, 10 Nov 2011 07:46:17 -0800
Subject: Re: [dhcwg] dhc-dhcpv6-redundancy-consider-02 draft (post WGLC)
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, 10 Nov 2011 15:19:20 -0000

Message en plusieurs parties au format MIME
--=_alternative 0054269785257944_=
Content-Type: text/plain; charset="US-ASCII"

> I support this as well, from what we have heard this is useful 
information.

</co-author hat> <operator deploying v6>
+ 1

This is already deployed in several environments and it will remain 
useful as long as the failover documents aren't completed and 
implemented by some vendors. 

/JF

--=_alternative 0054269785257944_=
Content-Type: text/html; charset="US-ASCII"


<br><tt><font size=2>&gt; I support this as well, from what we have heard
this is useful information.</font></tt>
<br>
<br><tt><font size=2>&lt;/co-author hat&gt; &lt;operator deploying v6&gt;</font></tt>
<br><tt><font size=2>+ 1</font></tt>
<br>
<br><tt><font size=2>This is already deployed in several environments and
it will remain </font></tt>
<br><tt><font size=2>useful as long as the failover documents aren't completed
and </font></tt>
<br><tt><font size=2>implemented by some vendors. </font></tt>
<br>
<br><tt><font size=2>/JF<br>
</font></tt>
--=_alternative 0054269785257944_=--

From jhutz@cmu.edu  Thu Nov 10 13:29:32 2011
Return-Path: <jhutz@cmu.edu>
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 4D56A21F8A7A for <dhcwg@ietfa.amsl.com>; Thu, 10 Nov 2011 13:29:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.609
X-Spam-Level: 
X-Spam-Status: No, score=-106.609 tagged_above=-999 required=5 tests=[AWL=-0.010, 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 rQM575L5LD04 for <dhcwg@ietfa.amsl.com>; Thu, 10 Nov 2011 13:29:31 -0800 (PST)
Received: from smtp03.srv.cs.cmu.edu (SMTP03.SRV.CS.CMU.EDU [128.2.217.198]) by ietfa.amsl.com (Postfix) with ESMTP id B223221F8A80 for <dhcwg@ietf.org>; Thu, 10 Nov 2011 13:29:31 -0800 (PST)
Received: from [66.233.146.161] (66-233-146-161.pit.clearwire-wmx.net [66.233.146.161] (may be forged)) (authenticated bits=0) by smtp03.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id pAALTQVS022028 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Nov 2011 16:29:28 -0500 (EST)
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: "ietf-krb-wg@anl.gov" <ietf-krb-wg@anl.gov>
In-Reply-To: <1318437422.3424.93.camel@destiny.pc.cs.cmu.edu>
References: <1317662486.10029.103.camel@minbar.fac.cs.cmu.edu> <1318437422.3424.93.camel@destiny.pc.cs.cmu.edu>
Content-Type: text/plain; charset="UTF-8"
Date: Thu, 10 Nov 2011 16:29:25 -0500
Message-ID: <1320960565.4307.46.camel@destiny.pc.cs.cmu.edu>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.3 
Content-Transfer-Encoding: 7bit
X-Scanned-By: mimedefang-cmuscs on 128.2.217.198
Cc: dhcwg@ietf.org, jhutz@cmu.edu
Subject: Re: [dhcwg] [Ietf-krb-wg] WG Last Call: draft-sakane-dhc-dhcpv6-kdc-option-12.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, 10 Nov 2011 21:29:32 -0000

On Wed, 2011-10-12 at 12:37 -0400, Jeffrey Hutzelman wrote:
> On Mon, 2011-10-03 at 13:21 -0400, Jeffrey Hutzelman wrote:
> > This note announces the start of a two-week last call to determine
> > whether to send the following document to the IESG:
> > 
> > Title:           Kerberos Options for DHCPv6
> > Filename:        draft-sakane-dhc-dhcpv6-kdc-option-12.txt
> > Intended Status: Standards Track(*)
> > 
> >    This document defines new four options of Dynamic Host Configuration
> >    Protocol for IPv6 (DHCPv6) to carry a set of configuration
> >    information related to the Kerberos protocol [RFC4120].
> > 
> > (*) Note that the current version of the draft says "Informational", but
> > during discussion leading up to this WGLC, I think Ted and I both agreed
> > that standards track is more appropriate.  If anyone has an objection to
> > this, please speak up.
> > 
> > This document is a product of the Kerberos working group, but since it
> > defines a DHCPv6 option, review is also required in DHC.  As a result,
> > we are running this Last Call simultaneously in both working groups.  We
> > request that any comments be sent to both <ietf-krb-wg@anl.gov> and
> > <dhcwg@ietf.org>.
> > 
> > This last call will expire at 23:59 EDT on Monday, Oct 17, 2011.
> > 
> > The file can be obtained via
> > 
> > http://tools.ietf.org/html/draft-sakane-dhc-dhcpv6-kdc-option-12.txt	
> 
> 
> So far I've seen no comments on this WGLC from either working group.
> Since this document has been in WGLC before and the changes since then
> have been discussed (if briefly) on the mailing list, I will take
> silence to mean that the Kerberos WG is OK with the updated document.
> Of course, I cannot speak for the DHC chairs.

This WGLC concluded some weeks ago with no objections or comments in
either WG.  As noted before, this was discussed and last called before,
and there is clearly support within the WG for publishing this document.
Therefore, I am sending a request to the IESG to publish this version.

-- Jeff


From volz@cisco.com  Thu Nov 10 13:55:28 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 9F4071F0C3E for <dhcwg@ietfa.amsl.com>; Thu, 10 Nov 2011 13:55:28 -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 DU84iRHaAaXq for <dhcwg@ietfa.amsl.com>; Thu, 10 Nov 2011 13:55:28 -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 09A441F0C38 for <dhcwg@ietf.org>; Thu, 10 Nov 2011 13:55:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=volz@cisco.com; l=172; q=dns/txt; s=iport; t=1320962128; x=1322171728; h=mime-version:content-transfer-encoding:subject:date: message-id:from:to; bh=/EFW4av/1gHHQ5qTRUpDc1OyWh7XYucTcOBJbbS9RXY=; b=V4mBXDZmIrbF+3X/5+q8FEO1tDxD5PKs6XwAaKl8XsrxtVbnWJ3pZcPE B0pk/IDlNb5bMvOCpHoBZdG2qWW6au+aqg96SO7DrsJ1MhmtlGD1Ar2uL wG7As8KpT27OiYHZ20FCP9OFj3I/NaN9TWpvkTDKXAbArwySYHsYDpR9v I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAOtHvE6tJV2a/2dsb2JhbABEqiyBBYFyAQEBAQIBEgEdCkQNAQgiBhgHVwEEGxqHYJgtgSYBnlCJG2MEiA+RWoxT
X-IronPort-AV: E=Sophos;i="4.69,490,1315180800"; d="scan'208";a="34929693"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-1.cisco.com with ESMTP; 10 Nov 2011 21:55:27 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pAALtRo8015280 for <dhcwg@ietf.org>; Thu, 10 Nov 2011 21:55:27 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, 10 Nov 2011 15:55:27 -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, 10 Nov 2011 15:55:26 -0600
Message-ID: <D9B5773329187548A0189ED65036678909B4E38C@XMB-RCD-101.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RE: [dhcwg] dhc-dhcpv6-redundancy-consider-02 draft (post WGLC)
Thread-Index: Acyf83Q5gHvYoQWBRHKfZQXPvt+oDQ==
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhc WG" <dhcwg@ietf.org>
X-OriginalArrivalTime: 10 Nov 2011 21:55:27.0384 (UTC) FILETIME=[74E38980:01CC9FF3]
Subject: Re: [dhcwg] dhc-dhcpv6-redundancy-consider-02 draft (post WGLC)
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, 10 Nov 2011 21:55:28 -0000

> I support this as well, from what we have heard this is useful
information.=20

</lately less involved WG "member">
+ 1

Hopefully it is not too late.

- Bernie


From volz@cisco.com  Thu Nov 10 14:05:16 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 E9CA121F8663 for <dhcwg@ietfa.amsl.com>; Thu, 10 Nov 2011 14:05:16 -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 eSJRSIKO6DB8 for <dhcwg@ietfa.amsl.com>; Thu, 10 Nov 2011 14:05:16 -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 18B0021F863E for <dhcwg@ietf.org>; Thu, 10 Nov 2011 14:05:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=volz@cisco.com; l=3175; q=dns/txt; s=iport; t=1320962716; x=1322172316; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=xW1YNIyNQAiWz1mDd9PaSCMG+O+tKFlQuZD97BrJd5Y=; b=G4ikbNEU0vhtaotHlGS826+l27EXczU80q9UINPA4PYFRWcY9iap834j bV3BUo0Gino1sg4ieXQ8jE3dKB8qIB2kEb/YxTpuIIJx6DKwynHYN7pU3 5nMDlumHkn3HMpBQtkomvY8nqviYQjdA7bYgbZpNqRraqaWPwcHLmPkib k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AskAAJlJvE6tJXG//2dsb2JhbABEmjKPeoEFgXIBAQEBAwEBAQ8BHQo0FwQCAQgOAwQBAQEKBhcBBgEmHwkIAQEEARIIGodomVsBnkoEiRtjBIgPkVqDOYka
X-IronPort-AV: E=Sophos;i="4.69,490,1315180800"; d="scan'208";a="34929064"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-4.cisco.com with ESMTP; 10 Nov 2011 22:05:15 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core2-4.cisco.com (8.14.3/8.14.3) with ESMTP id pAAM5FEo012736;  Thu, 10 Nov 2011 22:05:15 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);  Thu, 10 Nov 2011 16:05:15 -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, 10 Nov 2011 16:05:14 -0600
Message-ID: <D9B5773329187548A0189ED65036678909B4E393@XMB-RCD-101.cisco.com>
In-Reply-To: <D494B897-6773-4D92-9435-5E165B4306EA@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Proposed change to MAX_SOL_RT
Thread-Index: AcyeVBkBGsgzNPswQP6C+afIFHykTABn5NHA
References: <27AD7BB5-5295-4D97-A210-565099D12A07@gmail.com> <D494B897-6773-4D92-9435-5E165B4306EA@gmail.com>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Ralph Droms" <rdroms.ietf@gmail.com>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 10 Nov 2011 22:05:15.0334 (UTC) FILETIME=[D3559660:01CC9FF4]
Subject: Re: [dhcwg] Proposed change to MAX_SOL_RT
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, 10 Nov 2011 22:05:17 -0000

Perhaps it has been discussed (sorry if it was) ...

But another option (no pun intended) is to the have the server send back
a "SOL_MAX_RT" option to provide a client this information -- this could
be in the Advertise that says no addresses available. This does require
the server to be there and does offer a potential denial of service
attach -- but not really since it is just SOL_MAX_RT the client will
retry a number of times before using any 'bad' value.

It has the added benefit that the network operator can set the value to
what they feel is reasonable. If they aren't planning to turn things on
for 6 months, they could set it much higher than 3600.

This won't solve the issue when no DHCPv6 service is there -- then the M
& O bits are set incorrectly or the device is always doing DHCPv6.

Personally, I think both ways would be best. Though this might argue for
a lower SOL_MAX_RT than 3600 (perhaps to 600 seconds - that is 1/5th the
traffic of the 120 seconds value) and a lot less time to wait in a case
where the server(s) are down or unreachable for a bit.

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Ralph Droms
Sent: Tuesday, November 08, 2011 3:22 PM
To: dhcwg@ietf.org WG
Subject: Re: [dhcwg] Proposed change to MAX_SOL_RT

Followup to previous message about changing MAX_SOL_RT...

On Nov 4, 2011, at 7:33 AM 11/4/11, Ralph Droms wrote:
>=20
> 2. In a scenario in which the DHCPv6 service is unresponsive for
SOL_MAX_RT and the DHCPv6 clients are all now sending a Solicit every
SOL_MAX_RT, the average wait time for those clients to complete the
DHCPv6 message exchange after the DHCPv6 service comes back up will be
MAX_SOL_RT/2.  Is that situation acceptable or should we define some
other trigger through which the DHCPv6 clients can be signaled
explicitly to restart the Solicit transmission algorithm in section
17.1.2 of RFC 3315.  My personal opinion is that an additional trigger
is unnecessary.

In support of my opinion, I came up with the following analysis of the
likelihood of a client getting to the long-term MAX_SOL_RT interval
state.=20

If the CM and CE router have been up and running, with the CE configured
through DHCPv6, a WAN link flap will have no effect on DHCPv6 unless the
link is down past the address/PD lease expiration...and in this case,
the CE router will lose connectivity regardless.

If the CE router comes up without a valid address/PD lease before the
DHCPv6 service is running, the CE router will get to the long-term state
of waiting on average MAX_SOL_RT/2 only if the DHCPv6 service is down
longer than MAX_SOL_RT/2.  Note that this situation will only occur if
the CE router is coming up for the first time or coming up after its
address/PD lease has expired.

So, a DHCPv6 client can get to that long-term state sending a Solicit
every MAX_SOL_RT interval, but I don't think it's very likely.

Discussion welcome and encouraged.

- Ralph

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

From mellon@fugue.com  Thu Nov 10 21:49:23 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 1B57C21F84B4 for <dhcwg@ietfa.amsl.com>; Thu, 10 Nov 2011 21:49:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
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 E5cVufd6-pcG for <dhcwg@ietfa.amsl.com>; Thu, 10 Nov 2011 21:49:22 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 38B0F21F84B3 for <dhcwg@ietf.org>; Thu, 10 Nov 2011 21:49:22 -0800 (PST)
Received: from [192.168.3.2] (EM114-48-183-35.pool.e-mobile.ne.jp [114.48.183.35]) by toccata.fugue.com (Postfix) with ESMTPSA id E749123802BC for <dhcwg@ietf.org>; Fri, 11 Nov 2011 00:49:19 -0500 (EST)
References: <20111111042519.24509.36440.idtracker@ietfa.amsl.com>
From: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-3658F9BB-7481-4533-ACC7-4371F0679B6F
X-Mailer: iPad Mail (9A334)
Message-Id: <24457C79-4914-45D6-A860-731BCDC52330@fugue.com>
Date: Fri, 11 Nov 2011 14:49:28 +0900
To: DHC WG <dhcwg@ietf.org>
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Subject: [dhcwg] Fwd: I-D Action: draft-ietf-pcp-dhcp-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, 11 Nov 2011 05:49:23 -0000

--Apple-Mail-3658F9BB-7481-4533-ACC7-4371F0679B6F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

FYI, there is a new option spec coming from the PCP working group. I've subm=
itted comments to that working group, and would like to encourage other dhc w=
g participants to review the document.


Begin forwarded message:

> From: internet-drafts@ietf.org
> Date: November 11, 2011 1:25:19 PM GMT+09:00
> To: i-d-announce@ietf.org
> Cc: pcp@ietf.org
> Subject: I-D Action: draft-ietf-pcp-dhcp-00.txt
> Reply-To: internet-drafts@ietf.org
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts directo=
ries. This draft is a work item of the Port Control Protocol Working Group o=
f the IETF.
>=20
>    Title           : DHCP and DHCPv6 Options for the Port Control Protocol=
 (PCP)
>    Author(s)       : Mohamed Boucadair
>                          Reinaldo Penno
>                          Dan Wing
>    Filename        : draft-ietf-pcp-dhcp-00.txt
>    Pages           : 12
>    Date            : 2011-09-09
>=20
>   This document specifies DHCP (IPv4 and IPv6) options to configure
>   hosts with Port Control Protocol (PCP) Server addresses.  The use of
>   IPv4 DHCP or DHCPv6 depends on the PCP deployment scenario.
>=20
>=20
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pcp-dhcp-00.txt
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-pcp-dhcp-00.txt
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

--Apple-Mail-3658F9BB-7481-4533-ACC7-4371F0679B6F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head></head><body bgcolor=3D"#FFFFFF"><div>FYI, there is a new option=
 spec coming from the PCP working group. I've submitted comments to that wor=
king group, and would like to encourage other dhc wg participants to review t=
he document.<br><br><br>Begin forwarded message:<br><br></div><blockquote ty=
pe=3D"cite"><div><b>From:</b> <a href=3D"mailto:internet-drafts@ietf.org">in=
ternet-drafts@ietf.org</a><br><b>Date:</b> November 11, 2011 1:25:19 PM GMT+=
09:00<br><b>To:</b> <a href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ie=
tf.org</a><br><b>Cc:</b> <a href=3D"mailto:pcp@ietf.org">pcp@ietf.org</a><br=
><b>Subject:</b> <b>I-D Action: draft-ietf-pcp-dhcp-00.txt</b><br><b>Reply-T=
o:</b> <a href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org<=
/a><br><br></div></blockquote><div></div><blockquote type=3D"cite"><div><spa=
n>A New Internet-Draft is available from the on-line Internet-Drafts directo=
ries. This draft is a work item of the Port Control Protocol Working Group o=
f the IETF.</span><br><span></span><br><span> &nbsp; &nbsp;Title &nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: DHCP and DHCPv6 Options f=
or the Port Control Protocol (PCP)</span><br><span> &nbsp; &nbsp;Author(s) &=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Mohamed Boucadair</span><br><span> &nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Reinal=
do Penno</span><br><span> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;Dan Wing</span><br><span> &nbsp; &nbsp;Filename &nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: draft-ietf-pcp-dhcp-00.txt</span><br=
><span> &nbsp; &nbsp;Pages &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;: 12</span><br><span> &nbsp; &nbsp;Date &nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 2011-09-09</span><br><span></span=
><br><span> &nbsp;&nbsp;This document specifies DHCP (IPv4 and IPv6) options=
 to configure</span><br><span> &nbsp;&nbsp;hosts with Port Control Protocol (=
PCP) Server addresses. &nbsp;The use of</span><br><span> &nbsp;&nbsp;IPv4 DH=
CP or DHCPv6 depends on the PCP deployment scenario.</span><br><span></span>=
<br><span></span><br><span></span><br><span>A URL for this Internet-Draft is=
:</span><br><span><a href=3D"http://www.ietf.org/internet-drafts/draft-ietf-=
pcp-dhcp-00.txt">http://www.ietf.org/internet-drafts/draft-ietf-pcp-dhcp-00.=
txt</a></span><br><span></span><br><span>Internet-Drafts are also available b=
y anonymous FTP at:</span><br><span><a href=3D"ftp://ftp.ietf.org/internet-d=
rafts/">ftp://ftp.ietf.org/internet-drafts/</a></span><br><span></span><br><=
span>This Internet-Draft can be retrieved at:</span><br><span><a href=3D"ftp=
://ftp.ietf.org/internet-drafts/draft-ietf-pcp-dhcp-00.txt">ftp://ftp.ietf.o=
rg/internet-drafts/draft-ietf-pcp-dhcp-00.txt</a></span><br><span>__________=
_____________________________________</span><br><span>I-D-Announce mailing l=
ist</span><br><span><a href=3D"mailto:I-D-Announce@ietf.org">I-D-Announce@ie=
tf.org</a></span><br><span><a href=3D"https://www.ietf.org/mailman/listinfo/=
i-d-announce">https://www.ietf.org/mailman/listinfo/i-d-announce</a></span><=
br><span>Internet-Draft directories: <a href=3D"http://www.ietf.org/shadow.h=
tml">http://www.ietf.org/shadow.html</a></span><br><span>or <a href=3D"ftp:/=
/ftp.ietf.org/ietf/1shadow-sites.txt">ftp://ftp.ietf.org/ietf/1shadow-sites.=
txt</a></span><br></div></blockquote></body></html>=

--Apple-Mail-3658F9BB-7481-4533-ACC7-4371F0679B6F--

From volz@cisco.com  Sat Nov 12 18:49:47 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 3897721F84CD for <dhcwg@ietfa.amsl.com>; Sat, 12 Nov 2011 18:49:47 -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 gybuNOGks8ey for <dhcwg@ietfa.amsl.com>; Sat, 12 Nov 2011 18:49:46 -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 A9C7721F84CC for <dhcwg@ietf.org>; Sat, 12 Nov 2011 18:49:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=volz@cisco.com; l=1613; q=dns/txt; s=iport; t=1321152586; x=1322362186; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=NjywIIKow4LAYSu5tPLh3T0i2ihDXtbu4HVZcqqPKYU=; b=MH9TmIxMhR5gQzfbuIqtVACye/I4Ekagm1yP6RRQ3MPhh5hM5Ft4d3q0 wUSXNa+eEhvxbIH1Ad8YCL3hf6Ljke80bqQQ+kkKA/L4AcUr8fxARa7Kc rusGhqU3PMaqDbnGAEWtyyWcl5Pj4XfPRCQpvUmVNoRe5NdNbDoI0udNx o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArEAABYwv06tJXHB/2dsb2JhbABDmimQBoEFgXIBAQEDAQEBAQ8BHQo0CwUHBAIBCBEEAQEBCgYXAQYBJh8JCAEBBAESCBqHYAiYPAGdIASJHGMEiBCRYoxU
X-IronPort-AV: E=Sophos;i="4.69,501,1315180800"; d="scan'208";a="35399793"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-8.cisco.com with ESMTP; 13 Nov 2011 02:49:45 +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 pAD2njfN010553;  Sun, 13 Nov 2011 02:49:45 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);  Sat, 12 Nov 2011 20:49:44 -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, 12 Nov 2011 20:49:41 -0600
Message-ID: <D9B5773329187548A0189ED65036678909C39427@XMB-RCD-101.cisco.com>
In-Reply-To: <0234DF3F-CD88-423D-A286-2081D5F685B7@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] DHC WGLC: draft-ietf-dhc-forcerenew-nonce-01
Thread-Index: AcyeMuZ5sg2ArR54QhCJwSks/jS6EQDe8AuQ
References: <282BBE8A501E1F4DA9C775F964BB21FE3EB2AECD4C@GRFMBX704BA020.griffon.local>, <C1DA0414-6F36-4BC3-888F-BA6F7C4988B8@nominum.com><C6B13F40-DB79-46A4-B449-119394B5F4F3@nominum.com> <0234DF3F-CD88-423D-A286-2081D5F685B7@cisco.com>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Kim Kinnear (kkinnear)" <kkinnear@cisco.com>, "Ted Lemon" <Ted.Lemon@nominum.com>
X-OriginalArrivalTime: 13 Nov 2011 02:49:44.0975 (UTC) FILETIME=[E67599F0:01CCA1AE]
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] DHC WGLC: draft-ietf-dhc-forcerenew-nonce-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: Sun, 13 Nov 2011 02:49:47 -0000

Perhaps a bit too late ... but I too think this should advance ... FYI -
it is now draft-ietf-dhc-forcerenew-nonce-02.

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Kim Kinnear (kkinnear)
Sent: Tuesday, November 08, 2011 11:26 AM
To: Ted Lemon
Cc: dhcwg@ietf.org WG; Kim Kinnear (kkinnear)
Subject: Re: [dhcwg] DHC WGLC: draft-ietf-dhc-forcerenew-nonce-01


I support this document and think it should advance.

Regards -- Kim

On Nov 8, 2011, at 6:44 AM, Ted Lemon wrote:

> On Sep 23, 2011, at 10:29 AM, "Ted Lemon" <Ted.Lemon@nominum.com>
wrote:
>=20
>> This document has been ready for WGLC for some time and fell through
the cracks.   Please give it one last read and let us know if you find
any issues.   The document basically ports the nonce functionality of
DHCPv6 Reconfigure back to DHCPv4.
>>=20
>> Otherwise, if you support the document, please indicate that you do
on the mailing list.   If you think it's a bad idea, please let us know
as well.   We will do a consensus call on October 7, 2011.
>=20
> This WGLC got zero responses.   Is it really the case that this
document has no support from the working group, even the authors?
FWIW, I think it's important work and should advance, but I can't make
the call on my own.=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  Sat Nov 12 23:18:27 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 72B9011E80B1 for <dhcwg@ietfa.amsl.com>; Sat, 12 Nov 2011 23:18:27 -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.052, 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 bH3Aw2IJPlCx for <dhcwg@ietfa.amsl.com>; Sat, 12 Nov 2011 23:18:27 -0800 (PST)
Received: from exprod7og119.obsmtp.com (exprod7og119.obsmtp.com [64.18.2.16]) by ietfa.amsl.com (Postfix) with ESMTP id DC3DE11E8093 for <dhcwg@ietf.org>; Sat, 12 Nov 2011 23:18:11 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob119.postini.com ([64.18.6.12]) with SMTP ID DSNKTr9vLEKDkS3Maj6mW+v1UGBn1LZ99863@postini.com; Sat, 12 Nov 2011 23:18:12 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 2FBE21B812F for <dhcwg@ietf.org>; Sat, 12 Nov 2011 23:18:04 -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 3C7B4190052 for <dhcwg@ietf.org>; Sat, 12 Nov 2011 23:18:01 -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, 12 Nov 2011 23:18:01 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] DHC WGLC: draft-ietf-dhc-forcerenew-nonce-01
Thread-Index: AQHMngvU09trw8MAPE6V/SosGT9YZ5WjsDmAgAb3k4D//8TccA==
Date: Sun, 13 Nov 2011 07:18:00 +0000
Message-ID: <51492D86-E14B-4179-9BF0-9A13A329C76F@nominum.com>
References: <282BBE8A501E1F4DA9C775F964BB21FE3EB2AECD4C@GRFMBX704BA020.griffon.local>, <C1DA0414-6F36-4BC3-888F-BA6F7C4988B8@nominum.com><C6B13F40-DB79-46A4-B449-119394B5F4F3@nominum.com> <0234DF3F-CD88-423D-A286-2081D5F685B7@cisco.com>, <D9B5773329187548A0189ED65036678909C39427@XMB-RCD-101.cisco.com>
In-Reply-To: <D9B5773329187548A0189ED65036678909C39427@XMB-RCD-101.cisco.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-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] DHC WGLC: draft-ietf-dhc-forcerenew-nonce-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: Sun, 13 Nov 2011 07:18:27 -0000

Okay, this document didn't get any response at all during the WGLC period, =
but when I reminded people it hadn't, it got substantial support and no obj=
ections.   I really haven't heard any controversy in the working group abou=
t this draft.

So IMHO, it passed WGLC, and I'm going to write up a shepherd doc and forwa=
rd it to Ralph.   It will take me a few days to do so; if you actually do o=
bject to this document going forward, consider this your last chance to rai=
se an objection.   Do it now, or forever hold your peace.


From Ted.Lemon@nominum.com  Sat Nov 12 23:22:04 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 789A621F8AF0 for <dhcwg@ietfa.amsl.com>; Sat, 12 Nov 2011 23:22:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.549
X-Spam-Level: 
X-Spam-Status: No, score=-106.549 tagged_above=-999 required=5 tests=[AWL=0.050, 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 byQqnt1f8Q-m for <dhcwg@ietfa.amsl.com>; Sat, 12 Nov 2011 23:22:03 -0800 (PST)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by ietfa.amsl.com (Postfix) with ESMTP id 4652521F8AEE for <dhcwg@ietf.org>; Sat, 12 Nov 2011 23:22:03 -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 DSNKTr9wGoNq+wqRiDywk/+NATYicXZD369C@postini.com; Sat, 12 Nov 2011 23:22:03 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 8BB181B812F for <dhcwg@ietf.org>; Sat, 12 Nov 2011 23:22:02 -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 7BFBA190052 for <dhcwg@ietf.org>; Sat, 12 Nov 2011 23:22:02 -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, 12 Nov 2011 23:22:02 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] DHC WGLC: draft-ietf-dhc-dhcpv6-redundancy-consider-01.txt
Thread-Index: AQHModTvIhHNC7q7mEi0Py5JNhDA/g==
Date: Sun, 13 Nov 2011 07:22:01 +0000
Message-ID: <3642EE01-2BB3-4011-8052-08FF5B338FEC@nominum.com>
References: <711293BE-96C4-4BFB-86FB-0F8F123F48FE@nominum.com>
In-Reply-To: <711293BE-96C4-4BFB-86FB-0F8F123F48FE@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-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] DHC WGLC: draft-ietf-dhc-dhcpv6-redundancy-consider-01.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: Sun, 13 Nov 2011 07:22:04 -0000

On Sep 23, 2011, at 10:27 PM, "Ted Lemon" <Ted.Lemon@nominum.com> wrote:
> Please review the document one last time and indicate whether you support=
 it, or if you think it's a bad idea.   We will do a consensus call on Octo=
ber 7, 2011.

This document did not get any response during the proposed WGLC period, but=
 when I reminded the working group, it elicited a substantial response in f=
avor, and no objections (although Bernie raised a concern, which John spoke=
 to a bit).

Consequently, I think there is consensus to advance this draft, and I will =
be writing up a shepherd doc.   However, since this call is being made so l=
ate, I am willing to hear objections up until the time that I send Ralph th=
e shepherd doc.   Speak now or forever hold your peace.


From denghui02@gmail.com  Sun Nov 13 17:46:48 2011
Return-Path: <denghui02@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 CA2CF11E80EB; Sun, 13 Nov 2011 17:46:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 oSgSO8jebU7y; Sun, 13 Nov 2011 17:46:48 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 02D7111E80D7; Sun, 13 Nov 2011 17:46:47 -0800 (PST)
Received: by yenq4 with SMTP id q4so2790660yen.31 for <multiple recipients>; Sun, 13 Nov 2011 17:46:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=riLXQ7m/yrNPXAPA6MiN9WsBqkItDrclgZJ7qm51WTg=; b=wyB81GAxHTRw+ZRYj+jPwpzwXUcJPmhSWWpsvSNhBHlt5RRsqHeLe+ALwspSHFjum0 myWIJ6Ai8hFR4NBVxzrsP8L2EwlLsZto0NwxgajEgv+RnK1Jymxx0SWPh9ZqL8PWderW Y7060hIZUgF0PPJmYr4ztEqDd2VVxvTOfrYLY=
MIME-Version: 1.0
Received: by 10.236.197.72 with SMTP id s48mr11227596yhn.81.1321235207615; Sun, 13 Nov 2011 17:46:47 -0800 (PST)
Received: by 10.146.84.10 with HTTP; Sun, 13 Nov 2011 17:46:47 -0800 (PST)
Date: Mon, 14 Nov 2011 09:46:47 +0800
Message-ID: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: ipv6@ietf.org, MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary=20cf303f6c8036f66204b1a80bca
Subject: [dhcwg] 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: Mon, 14 Nov 2011 01:46:48 -0000

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

Hello 6MAN and DHCP,

Especially thanks *Wes Beebee*, Hemant Singh, Brian Carpenter, Alex and
Ted's discussion.

MIF is going to discuss the confliction between RA and DHCP on tuesday
afternoon MIF session (15:20-17:00)
the author Tomasz has propose below resolution:

The problem is about potential conflict between RA and DHCP. Our
proposed answer is as follows:

RA provides configuration to all hosts in a network. DHCP can provide
configuration on a per host basis. Therefore it may be useful to use
DHCP to "override" configuration for some hosts in a network (e.g.
engineering department has extra routes defined for a lab network). As
such, DHCP should be preferred.

However, there is also a matter of security. Both RA and DHCPv6 can be
secured. If SEND is deployed, RA is more trustworthy than DHCP, so it
should be preferred. Finally, there is such thing as secure DHCP, so if
both RA and DHCP are secure, prefer SEND. I must admit that I never
heard about any realistic deployments of secure DHCP, but it will change
over time.

This approach can be summed as: favor secure, favor DHCP. Or to be more
explicit, there's a complete list of all cases:
a) RA vs DHCP => prefer DHCP
b) RA(SEND) vs DHCP => prefer RA
c) RA vs secure DHCP => prefer DHCP
d) RA(SEND) vs secure DHCP => prefer DHCP

Does it sound reasonable?

This approach is very similar to what was described in DNS configuration
over RA and DHCP (except the part about both RA and DHCP being secure
that is not covered in RFC6106).

To summarize the discussion so far, Ted Lemon on MIF list agreed that
DHCP should be preferred. Herman Singh on 6MAN list suggested to go look
at what DNS over RA proposes and use the same approach. RFC6106, section
5.3.1covers cases a) and b). c) and d) are logical extension that takes
DHCPv6 security into consideration. My understanding is that proposed
solution will be satisfactory to everyone.

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

<div>Hello 6MAN and DHCP, </div>
<div>=A0</div>
<div>Especially=A0thanks <strong>Wes Beebee</strong>, Hemant Singh, Brian C=
arpenter, Alex and Ted&#39;s discussion.</div>
<div>=A0</div>
<div>MIF is going to discuss the confliction between RA and DHCP on tuesday=
 afternoon MIF session (15:20-17:00)=A0</div>
<div>the author Tomasz has propose below resolution:</div>
<div>=A0</div>
<div>The problem is about potential conflict between RA and DHCP. Our<br>pr=
oposed answer is as follows:<br><br>RA provides configuration to all hosts =
in a network. DHCP can provide<br>configuration on a per host basis. Theref=
ore it may be useful to use<br>
DHCP to &quot;override&quot; configuration for some hosts in a network (e.g=
.<br>engineering department has extra routes defined for a lab network). As=
<br>such, DHCP should be preferred.<br><br>However, there is also a matter =
of security. Both RA and DHCPv6 can be<br>
secured. If SEND is deployed, RA is more trustworthy than DHCP, so it<br>sh=
ould be preferred. Finally, there is such thing as secure DHCP, so if<br>bo=
th RA and DHCP are secure, prefer SEND. I must admit that I never<br>heard =
about any realistic deployments of secure DHCP, but it will change<br>
over time.<br><br>This approach can be summed as: favor secure, favor DHCP.=
 Or to be more<br>explicit, there&#39;s a complete list of all cases:<br>a)=
 RA vs DHCP =3D&gt; prefer DHCP<br>b) RA(SEND) vs DHCP =3D&gt; prefer RA<br=
>
c) RA vs secure DHCP =3D&gt; prefer DHCP<br>d) RA(SEND) vs secure DHCP =3D&=
gt; prefer DHCP<br><br>Does it sound reasonable?<br><br>This approach is ve=
ry similar to what was described in DNS configuration<br>over RA and DHCP (=
except the part about both RA and DHCP being secure<br>
that is not covered in RFC6106).<br><br>To summarize the discussion so far,=
 Ted Lemon on MIF list agreed that<br>DHCP should be preferred. Herman Sing=
h on 6MAN list suggested to go look<br>at what DNS over RA proposes and use=
 the same approach. RFC6106, section<br>
5.3.1covers cases a) and b). c) and d) are logical extension that takes<br>=
DHCPv6 security into consideration. My understanding is that proposed<br>so=
lution will be satisfactory to everyone.<br></div>

--20cf303f6c8036f66204b1a80bca--

From ichiroumakino@gmail.com  Sun Nov 13 17:59:49 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 BF55A11E8109; Sun, 13 Nov 2011 17:59:49 -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 SrWMA+93ObOo; Sun, 13 Nov 2011 17:59:49 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id EB03211E8091; Sun, 13 Nov 2011 17:59:48 -0800 (PST)
Received: by ggnr5 with SMTP id r5so433608ggn.31 for <multiple recipients>; Sun, 13 Nov 2011 17:59:48 -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=WCUXB617eBHyCXPPmNzF+X0gl4DHSxdh2Aw1lleoVpA=; b=SlyqQ8NBV3Lfoiu+hSX3iA/diOaAm2CC3oaDDRlSbLvqbV8CfPfQ28QDrloky64S5H 1OKa0UEoM4yJw05bUGC+blJm8xERDVaJiMgMJw6KnBYUYuoTB4q5CAh1Om1CSjO7Av/q Mfvrjm2wDApRTCUaP4XHoukDnLnw34hRbCRPc=
Received: by 10.68.73.71 with SMTP id j7mr32010423pbv.116.1321235987294; Sun, 13 Nov 2011 17:59:47 -0800 (PST)
Received: from sjc-vpn4-250.cisco.com (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id p10sm52531607pbd.15.2011.11.13.17.59.44 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 13 Nov 2011 17:59:45 -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: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
Date: Mon, 14 Nov 2011 09:59:40 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
To: Hui Deng <denghui02@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: MIF Mailing List <mif@ietf.org>, ipv6@ietf.org, dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] 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: Mon, 14 Nov 2011 01:59:49 -0000

Hui,

why not just merge all the information received?
e.g. if you get DNS server over DHCP and RA, use all.
if you get addresses via SLAAC and DHCP, you use all...

cheers,
Ole


On Nov 14, 2011, at 9:46 , Hui Deng wrote:

> Hello 6MAN and DHCP,
> =20
> Especially thanks Wes Beebee, Hemant Singh, Brian Carpenter, Alex and =
Ted's discussion.
> =20
> MIF is going to discuss the confliction between RA and DHCP on tuesday =
afternoon MIF session (15:20-17:00)=20
> the author Tomasz has propose below resolution:
> =20
> The problem is about potential conflict between RA and DHCP. Our
> proposed answer is as follows:
>=20
> RA provides configuration to all hosts in a network. DHCP can provide
> configuration on a per host basis. Therefore it may be useful to use
> DHCP to "override" configuration for some hosts in a network (e.g.
> engineering department has extra routes defined for a lab network). As
> such, DHCP should be preferred.
>=20
> However, there is also a matter of security. Both RA and DHCPv6 can be
> secured. If SEND is deployed, RA is more trustworthy than DHCP, so it
> should be preferred. Finally, there is such thing as secure DHCP, so =
if
> both RA and DHCP are secure, prefer SEND. I must admit that I never
> heard about any realistic deployments of secure DHCP, but it will =
change
> over time.
>=20
> This approach can be summed as: favor secure, favor DHCP. Or to be =
more
> explicit, there's a complete list of all cases:
> a) RA vs DHCP =3D> prefer DHCP
> b) RA(SEND) vs DHCP =3D> prefer RA
> c) RA vs secure DHCP =3D> prefer DHCP
> d) RA(SEND) vs secure DHCP =3D> prefer DHCP
>=20
> Does it sound reasonable?
>=20
> This approach is very similar to what was described in DNS =
configuration
> over RA and DHCP (except the part about both RA and DHCP being secure
> that is not covered in RFC6106).
>=20
> To summarize the discussion so far, Ted Lemon on MIF list agreed that
> DHCP should be preferred. Herman Singh on 6MAN list suggested to go =
look
> at what DNS over RA proposes and use the same approach. RFC6106, =
section
> 5.3.1covers cases a) and b). c) and d) are logical extension that =
takes
> DHCPv6 security into consideration. My understanding is that proposed
> solution will be satisfactory to everyone.
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From brian.e.carpenter@gmail.com  Sun Nov 13 18:20:39 2011
Return-Path: <brian.e.carpenter@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 2674A1F0C4E; Sun, 13 Nov 2011 18:20:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.442
X-Spam-Level: 
X-Spam-Status: No, score=-103.442 tagged_above=-999 required=5 tests=[AWL=0.158, 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 8O6yjVwzW8m2; Sun, 13 Nov 2011 18:20:38 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5B62B1F0C62; Sun, 13 Nov 2011 18:20:38 -0800 (PST)
Received: by yenq4 with SMTP id q4so2811608yen.31 for <multiple recipients>; Sun, 13 Nov 2011 18:20:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=x5SkQIePzE7xVG2xmaltQX4nChFg/4XxpaxQYVvRHRU=; b=SSn8S3vEnIdYmtNH2DuM8z0Y4zlsKS5ZbjjnnH3Gxj24i+nsClJLajEwkMgFsce45k qVgblvH/HRwDu6SBjXbd0YaHuD9HS+2K+t9w8pfkZ8aVn3rgWZQUFDKiW7JuhpfnIbuu HdssbrWBT9QnK0x4MZ6Z8BrPEkCMP2pgBusvU=
Received: by 10.236.116.98 with SMTP id f62mr11231472yhh.48.1321237237925; Sun, 13 Nov 2011 18:20:37 -0800 (PST)
Received: from [130.129.19.92] (dhcp-135c.meeting.ietf.org. [130.129.19.92]) by mx.google.com with ESMTPS id j25sm28619708yhm.12.2011.11.13.18.20.35 (version=SSLv3 cipher=OTHER); Sun, 13 Nov 2011 18:20:37 -0800 (PST)
Message-ID: <4EC07AEF.7070303@gmail.com>
Date: Mon, 14 Nov 2011 15:20:31 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Hui Deng <denghui02@gmail.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
In-Reply-To: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: MIF Mailing List <mif@ietf.org>, ipv6@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: Mon, 14 Nov 2011 02:20:39 -0000

> MIF is going to discuss the confliction between RA and DHCP on tuesday
> afternoon MIF session (15:20-17:00)

This clashes with SOFTWIRE. Can you do it in the 17:10 session?

Regards
   Brian

On 2011-11-14 14:46, Hui Deng wrote:
> Hello 6MAN and DHCP,
> 
> Especially thanks *Wes Beebee*, Hemant Singh, Brian Carpenter, Alex and
> Ted's discussion.
> 
> MIF is going to discuss the confliction between RA and DHCP on tuesday
> afternoon MIF session (15:20-17:00)
> the author Tomasz has propose below resolution:
> 
> The problem is about potential conflict between RA and DHCP. Our
> proposed answer is as follows:
> 
> RA provides configuration to all hosts in a network. DHCP can provide
> configuration on a per host basis. Therefore it may be useful to use
> DHCP to "override" configuration for some hosts in a network (e.g.
> engineering department has extra routes defined for a lab network). As
> such, DHCP should be preferred.
> 
> However, there is also a matter of security. Both RA and DHCPv6 can be
> secured. If SEND is deployed, RA is more trustworthy than DHCP, so it
> should be preferred. Finally, there is such thing as secure DHCP, so if
> both RA and DHCP are secure, prefer SEND. I must admit that I never
> heard about any realistic deployments of secure DHCP, but it will change
> over time.
> 
> This approach can be summed as: favor secure, favor DHCP. Or to be more
> explicit, there's a complete list of all cases:
> a) RA vs DHCP => prefer DHCP
> b) RA(SEND) vs DHCP => prefer RA
> c) RA vs secure DHCP => prefer DHCP
> d) RA(SEND) vs secure DHCP => prefer DHCP
> 
> Does it sound reasonable?
> 
> This approach is very similar to what was described in DNS configuration
> over RA and DHCP (except the part about both RA and DHCP being secure
> that is not covered in RFC6106).
> 
> To summarize the discussion so far, Ted Lemon on MIF list agreed that
> DHCP should be preferred. Herman Singh on 6MAN list suggested to go look
> at what DNS over RA proposes and use the same approach. RFC6106, section
> 5.3.1covers cases a) and b). c) and d) are logical extension that takes
> DHCPv6 security into consideration. My understanding is that proposed
> solution will be satisfactory to everyone.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif

From Ted.Lemon@nominum.com  Sun Nov 13 18:22:59 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 7B43011E8115; Sun, 13 Nov 2011 18:22:59 -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.048, 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 HzyMtLcGYYFX; Sun, 13 Nov 2011 18:22:59 -0800 (PST)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 1AD5D11E810E; Sun, 13 Nov 2011 18:22:55 -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 DSNKTsB7fWhHzHSoYUKdTaD25od0/IRG6os3@postini.com; Sun, 13 Nov 2011 18:22:55 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 0B8DB1B82B8; Sun, 13 Nov 2011 18:22:53 -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 EC26E190052; Sun, 13 Nov 2011 18:22:51 -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; Sun, 13 Nov 2011 18:22:52 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Hui Deng <denghui02@gmail.com>
Thread-Topic: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Index: AQHMom9Jeyu5uv/47kCfd4auwPXOIJWro757
Date: Mon, 14 Nov 2011 02:22:51 +0000
Message-ID: <0AAC8A70-8D90-45EA-9EB7-14D9596BA99A@nominum.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
In-Reply-To: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.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-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: MIF Mailing List <mif@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] 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: Mon, 14 Nov 2011 02:22:59 -0000

On Nov 14, 2011, at 9:46 AM, "Hui Deng" <denghui02@gmail.com> wrote:
> Finally, there is such thing as secure DHCP, so if
> both RA and DHCP are secure, prefer SEND. I must admit that I never
> heard about any realistic deployments of secure DHCP, but it will change
> over time.

This doesn't agree with the list of steps you gave subsequently.  I agree t=
o that list, but not to what is said here.  That is, if both DHCP and ND ar=
e secure, prefer DHCP. =

From Ted.Lemon@nominum.com  Sun Nov 13 18:24:43 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 5081A11E812F; Sun, 13 Nov 2011 18:24:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.552
X-Spam-Level: 
X-Spam-Status: No, score=-106.552 tagged_above=-999 required=5 tests=[AWL=0.047, 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 5wEhlOxK7Fef; Sun, 13 Nov 2011 18:24:39 -0800 (PST)
Received: from exprod7og117.obsmtp.com (exprod7og117.obsmtp.com [64.18.2.6]) by ietfa.amsl.com (Postfix) with ESMTP id 6071D11E812D; Sun, 13 Nov 2011 18:24: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 DSNKTsB75hyQMM1EIPgXAZI+xxzv48Q3CeCk@postini.com; Sun, 13 Nov 2011 18:24: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 7B1421B82B5; Sun, 13 Nov 2011 18:24: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 6DADC190052; Sun, 13 Nov 2011 18:24:38 -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; Sun, 13 Nov 2011 18:24:38 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ole Troan <otroan@employees.org>
Thread-Topic: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Index: AQHMom9Jeyu5uv/47kCfd4auwPXOIJWsI2EA//+A3Mc=
Date: Mon, 14 Nov 2011 02:24:37 +0000
Message-ID: <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org>
In-Reply-To: <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@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: "ipv6@ietf.org" <ipv6@ietf.org>, MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] 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: Mon, 14 Nov 2011 02:24:43 -0000

On Nov 14, 2011, at 9:59 AM, "Ole Troan" <otroan@employees.org> wrote:
> why not just merge all the information received?
> e.g. if you get DNS server over DHCP and RA, use all.
> if you get addresses via SLAAC and DHCP, you use all...

Because "just merge" is essentially equivalent to "just walk across the riv=
er without your feet getting wet.".  If you can write a spec that does this=
 correctly, you are probably the Messiah. =

From ichiroumakino@gmail.com  Sun Nov 13 18:30:09 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 B409E11E814C; Sun, 13 Nov 2011 18: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 18H+pg-0IfuY; Sun, 13 Nov 2011 18:30:09 -0800 (PST)
Received: from mail-pz0-f50.google.com (mail-pz0-f50.google.com [209.85.210.50]) by ietfa.amsl.com (Postfix) with ESMTP id 2661F11E8146; Sun, 13 Nov 2011 18:30:09 -0800 (PST)
Received: by pzk5 with SMTP id 5so8385536pzk.9 for <multiple recipients>; Sun, 13 Nov 2011 18:30:07 -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=OL/RTiy832CbrPkkX+uNSdoiKCy286kPwZVRx/C+bMg=; b=vu7hqD8xYWkgrJWZ8YpE7HfpC1NuwyqoX+B84qw4BYIfwoDR3w+s2s+yYFFKczW3DZ PaNQwushP99Bkcrl7qz8/yDfC92L90u8N+rvFK9CyOjWPBHyyflYxTKZytLuJG7BUkPj MfcSyyCzWbhiLMmlBxjtcH/nzm6KNo0Hc8kE4=
Received: by 10.68.7.9 with SMTP id f9mr34105931pba.47.1321237807839; Sun, 13 Nov 2011 18:30:07 -0800 (PST)
Received: from sjc-vpn4-250.cisco.com (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id b2sm52766995pbc.2.2011.11.13.18.30.04 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 13 Nov 2011 18:30:06 -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: <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>
Date: Mon, 14 Nov 2011 10:30:00 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <83E275B4-915B-4989-88BC-4FF85E78E2B6@employees.org>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1084)
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] 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: Mon, 14 Nov 2011 02:30:09 -0000

Ted,

>> why not just merge all the information received?
>> e.g. if you get DNS server over DHCP and RA, use all.
>> if you get addresses via SLAAC and DHCP, you use all...
>=20
> Because "just merge" is essentially equivalent to "just walk across =
the river without your feet getting wet.".  If you can write a spec that =
does this correctly, you are probably the Messiah.

isn't this what a host does anyway? if it has more than one router on =
the link?

cheers,
Ole


From Ted.Lemon@nominum.com  Sun Nov 13 18:32:44 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 BBED211E8156; Sun, 13 Nov 2011 18:32:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.553
X-Spam-Level: 
X-Spam-Status: No, score=-106.553 tagged_above=-999 required=5 tests=[AWL=0.046, 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 RsljRLCj2Ig8; Sun, 13 Nov 2011 18:32:44 -0800 (PST)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by ietfa.amsl.com (Postfix) with ESMTP id D72E311E815D; Sun, 13 Nov 2011 18:32:42 -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 DSNKTsB9ygQBkWaqH1t6aPuNOXtytBk/J6x4@postini.com; Sun, 13 Nov 2011 18:32:43 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 20CD61B82B4; Sun, 13 Nov 2011 18:32:42 -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 140E2190052; Sun, 13 Nov 2011 18:32: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; Sun, 13 Nov 2011 18:32:42 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ole Troan <otroan@employees.org>
Thread-Topic: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Index: AQHMom9Jeyu5uv/47kCfd4auwPXOIJWsI2EA//+A3MeAAIedAP//eqTG
Date: Mon, 14 Nov 2011 02:32:41 +0000
Message-ID: <BB7F1166-20DF-4ED3-A796-58453873FEA0@nominum.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>, <83E275B4-915B-4989-88BC-4FF85E78E2B6@employees.org>
In-Reply-To: <83E275B4-915B-4989-88BC-4FF85E78E2B6@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: "ipv6@ietf.org" <ipv6@ietf.org>, MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] 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: Mon, 14 Nov 2011 02:32:44 -0000

On Nov 14, 2011, at 10:30 AM, "Ole Troan" <otroan@employees.org> wrote:
> isn't this what a host does anyway? if it has more than one router on the=
 link?

Yes, and they reliably do it wrong.  This is why we have a MIF working grou=
p!  :)=

From ichiroumakino@gmail.com  Sun Nov 13 18:35:49 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 077A81F0C84; Sun, 13 Nov 2011 18:35:49 -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 sCnEjca8orum; Sun, 13 Nov 2011 18:35:48 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5BB751F0C82; Sun, 13 Nov 2011 18:35:48 -0800 (PST)
Received: by iaeo4 with SMTP id o4so8657083iae.31 for <multiple recipients>; Sun, 13 Nov 2011 18:35:48 -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=CBVfHdjz0vFHC1HrrG60280fjyGcT2DWKjrPiHFihCY=; b=Pebfe+GChnxOhhhv6UWNRIjx3IPQaWwLqZPSTj7AFNrFWE/yriLs6jgPtWBbT6I0uX 4nOM6yATHVAOCdnZbUf7D5DKpDfiqJ9hGq8iHh7y/VxRLeWymCFBln1fzOHP1lC9V32H Bc5A6Uen9EaS8aPjJT294/RbgC0ESihaUO/us=
Received: by 10.42.154.194 with SMTP id r2mr20951585icw.50.1321238148016; Sun, 13 Nov 2011 18:35:48 -0800 (PST)
Received: from sjc-vpn4-250.cisco.com (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id n30sm28247533ibl.4.2011.11.13.18.35.44 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 13 Nov 2011 18:35:46 -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: <BB7F1166-20DF-4ED3-A796-58453873FEA0@nominum.com>
Date: Mon, 14 Nov 2011 10:35:41 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <5DA6C509-3D10-4E56-A47C-2709030BE535@employees.org>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>, <83E275B4-915B-4989-88BC-4FF85E78E2B6@employees.org> <BB7F1166-20DF-4ED3-A796-58453873FEA0@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1084)
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] 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: Mon, 14 Nov 2011 02:35:49 -0000

>> isn't this what a host does anyway? if it has more than one router on =
the link?
>=20
> Yes, and they reliably do it wrong.  This is why we have a MIF working =
group!  :)

wouldn't they continue to do it wrong if we were to specify a default =
"policy"?
I'm in the camp of "use all the information you've got". the prefer one =
of the other by default, is heading down 3484 country, and that hasn't =
been a pleasant experience.

cheers,
Ole


From Ted.Lemon@nominum.com  Sun Nov 13 18:59: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 E0FBE11E819B; Sun, 13 Nov 2011 18:59:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.554
X-Spam-Level: 
X-Spam-Status: No, score=-106.554 tagged_above=-999 required=5 tests=[AWL=0.045, 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 rlbprWjbtrpR; Sun, 13 Nov 2011 18:59:32 -0800 (PST)
Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by ietfa.amsl.com (Postfix) with ESMTP id 02B9011E8198; Sun, 13 Nov 2011 18:59:31 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP ID DSNKTsCEE8kK+Vrx1n7JsE7t2C5d6O9FCj4k@postini.com; Sun, 13 Nov 2011 18:59: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 058C71B82B3; Sun, 13 Nov 2011 18:59: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 33506190052; Sun, 13 Nov 2011 18:59:27 -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; Sun, 13 Nov 2011 18:59:27 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ole Troan <otroan@employees.org>
Thread-Topic: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Index: AQHMom9Jeyu5uv/47kCfd4auwPXOIJWsI2EA//+A3MeAAIedAP//eqTGgACG84D//4CHUQ==
Date: Mon, 14 Nov 2011 02:59:26 +0000
Message-ID: <8CF32B5B-3A57-46F7-AB16-A50B403F7595@nominum.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>, <83E275B4-915B-4989-88BC-4FF85E78E2B6@employees.org> <BB7F1166-20DF-4ED3-A796-58453873FEA0@nominum.com>, <5DA6C509-3D10-4E56-A47C-2709030BE535@employees.org>
In-Reply-To: <5DA6C509-3D10-4E56-A47C-2709030BE535@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: "ipv6@ietf.org" <ipv6@ietf.org>, MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] 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: Mon, 14 Nov 2011 02:59:33 -0000

On Nov 14, 2011, at 10:35 AM, "Ole Troan" <otroan@employees.org> wrote:
> wouldn't they continue to do it wrong if we were to specify a default "po=
licy"?
> I'm in the camp of "use all the information you've got". the prefer one o=
f the other by default, is heading down 3484 country, and that hasn't been =
a pleasant experience.

Great, then we can disband MIF and save everyone a lot of time!  All of the=
 various failure modes, DOS attacks and spoofing attacks that are possible =
in a MIF environment aren't all that important...  :)


From mohacsi@niif.hu  Sun Nov 13 23:55:48 2011
Return-Path: <mohacsi@niif.hu>
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 6E35211E824C; Sun, 13 Nov 2011 23:55:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.004
X-Spam-Level: 
X-Spam-Status: No, score=-0.004 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_HU=1.35, HOST_EQ_HU=1.245]
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 7SwRaSKTCd0y; Sun, 13 Nov 2011 23:55:47 -0800 (PST)
Received: from mail.ki.iif.hu (mail.ki.iif.hu [IPv6:2001:738:0:411::241]) by ietfa.amsl.com (Postfix) with ESMTP id 2234011E8243; Sun, 13 Nov 2011 23:55:47 -0800 (PST)
Received: from bolha.lvs.iif.hu (bolha.lvs.iif.hu [193.225.14.181]) by mail.ki.iif.hu (Postfix) with ESMTP id 6CEB28782D; Mon, 14 Nov 2011 08:55:45 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at bolha.lvs.iif.hu
Received: from mail.ki.iif.hu ([IPv6:::ffff:193.6.222.241]) by bolha.lvs.iif.hu (bolha.lvs.iif.hu [::ffff:193.225.14.72]) (amavisd-new, port 10024) with ESMTP id lIk6E--GN1y8; Mon, 14 Nov 2011 08:55:42 +0100 (CET)
Received: by mail.ki.iif.hu (Postfix, from userid 9002) id 11A3D8782C; Mon, 14 Nov 2011 08:55:42 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by mail.ki.iif.hu (Postfix) with ESMTP id 023F8877F5; Mon, 14 Nov 2011 08:55:41 +0100 (CET)
Date: Mon, 14 Nov 2011 08:55:41 +0100 (CET)
From: Mohacsi Janos <mohacsi@niif.hu>
X-X-Sender: mohacsi@mignon.ki.iif.hu
To: Hui Deng <denghui02@gmail.com>
In-Reply-To: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
Message-ID: <alpine.BSF.2.00.1111140850130.66599@mignon.ki.iif.hu>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="0-1307643040-1321257342=:66599"
Cc: MIF Mailing List <mif@ietf.org>, ipv6@ietf.org, dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] 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: Mon, 14 Nov 2011 07:55:48 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1307643040-1321257342=:66599
Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8BIT




On Mon, 14 Nov 2011, Hui Deng wrote:

> Hello 6MAN and DHCP,
>  
> Especially thanks Wes Beebee, Hemant Singh, Brian Carpenter, Alex and Ted's discussion.
>  
> MIF is going to discuss the confliction between RA and DHCP on tuesday afternoon MIF session (15:20-17:00) 
> the author Tomasz has propose below resolution:
>  
> The problem is about potential conflict between RA and DHCP. Our
> proposed answer is as follows:
> 
> RA provides configuration to all hosts in a network. DHCP can provide
> configuration on a per host basis. Therefore it may be useful to use
> DHCP to "override" configuration for some hosts in a network (e.g.
> engineering department has extra routes defined for a lab network). As
> such, DHCP should be preferred.
> 
> However, there is also a matter of security. Both RA and DHCPv6 can be
> secured. If SEND is deployed, RA is more trustworthy than DHCP, so it
> should be preferred. Finally, there is such thing as secure DHCP, so if
> both RA and DHCP are secure, prefer SEND. I must admit that I never
> heard about any realistic deployments of secure DHCP, but it will change
> over time.
> 
> This approach can be summed as: favor secure, favor DHCP. Or to be more
> explicit, there's a complete list of all cases:
> a) RA vs DHCP => prefer DHCP
> b) RA(SEND) vs DHCP => prefer RA
> c) RA vs secure DHCP => prefer DHCP
> d) RA(SEND) vs secure DHCP => prefer DHCP
> 
> Does it sound reasonable?
> 
> This approach is very similar to what was described in DNS configuration
> over RA and DHCP (except the part about both RA and DHCP being secure
> that is not covered in RFC6106).
> 
> To summarize the discussion so far, Ted Lemon on MIF list agreed that
> DHCP should be preferred. Herman Singh on 6MAN list suggested to go look
> at what DNS over RA proposes and use the same approach. RFC6106, section
> 5.3.1covers cases a) and b). c) and d) are logical extension that takes
> DHCPv6 security into consideration. My understanding is that proposed
> solution will be satisfactory to everyone.


I think in reality it will not be very easy to implement all these things. 
Some Operating System might implement RA(SEND), some the Secure DHCP, some 
none of above. . The operator should operate the network consistently: - 
same information all the relevant channel..... This preferential treatment 
can give  some protections against malicious activity or misconfiguration.



Best Regards,
 		Janos Mohacsi
--0-1307643040-1321257342=:66599--

From Ted.Lemon@nominum.com  Mon Nov 14 01:29:14 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 BFEAB21F8EC4; Mon, 14 Nov 2011 01:29:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.558
X-Spam-Level: 
X-Spam-Status: No, score=-106.558 tagged_above=-999 required=5 tests=[AWL=0.041, 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 rpC-C+D4ZQlu; Mon, 14 Nov 2011 01:29:12 -0800 (PST)
Received: from exprod7og127.obsmtp.com (exprod7og127.obsmtp.com [64.18.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id A918521F8EC1; Mon, 14 Nov 2011 01:29:11 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob127.postini.com ([64.18.6.12]) with SMTP ID DSNKTsDfWlsuc1mRyVSRcmSwRRMFmjNZ6ab3@postini.com; Mon, 14 Nov 2011 01:29:11 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 7ED531B82B5; Mon, 14 Nov 2011 01:28: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 63C35190052; Mon, 14 Nov 2011 01:28:57 -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, 14 Nov 2011 01:28:57 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Mohacsi Janos <mohacsi@niif.hu>
Thread-Topic: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Index: AQHMom9Jeyu5uv/47kCfd4auwPXOIJWshtmA//+T8hI=
Date: Mon, 14 Nov 2011 09:28:56 +0000
Message-ID: <D5254BBA-B020-4803-B5BF-D913C27922F6@nominum.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <alpine.BSF.2.00.1111140850130.66599@mignon.ki.iif.hu>
In-Reply-To: <alpine.BSF.2.00.1111140850130.66599@mignon.ki.iif.hu>
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: "ipv6@ietf.org" <ipv6@ietf.org>, MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] 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: Mon, 14 Nov 2011 09:29:15 -0000

On Nov 14, 2011, at 3:55 PM, "Mohacsi Janos" <mohacsi@niif.hu> wrote:
> I think in reality it will not be very easy to implement all these things=
. Some Operating System might implement RA(SEND), some the Secure DHCP, som=
e none of above. . The operator should operate the network consistently: - =
same information all the relevant channel..... This preferential treatment =
can give  some protections against malicious activity or misconfiguration.

This is true, but the problem is that the RA may be trustworthy and DHCP no=
t, or vice versa. So it's not safe to assume that the information you get f=
rom each one is trustworthy, even though of course on a good network it sho=
uld be.=20


From alexandru.petrescu@gmail.com  Mon Nov 14 02:11:22 2011
Return-Path: <alexandru.petrescu@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 8487E11E813B; Mon, 14 Nov 2011 02:11:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.326
X-Spam-Level: 
X-Spam-Status: No, score=-6.326 tagged_above=-999 required=5 tests=[AWL=-0.077, BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 Ld6HmnCmtY2R; Mon, 14 Nov 2011 02:11:21 -0800 (PST)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.144]) by ietfa.amsl.com (Postfix) with ESMTP id 3153C21F8F64; Mon, 14 Nov 2011 02:08:57 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.2) with ESMTP id pAEA8IHM018751 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 14 Nov 2011 11:08:18 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id pAEA8Itn031226; Mon, 14 Nov 2011 11:08:18 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] ([132.166.133.173]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.1) with ESMTP id pAEA8HNf005826; Mon, 14 Nov 2011 11:08:18 +0100
Message-ID: <4EC0E891.1060505@gmail.com>
Date: Mon, 14 Nov 2011 11:08:17 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: dhcwg@ietf.org, mif <mif@ietf.org>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>
In-Reply-To: <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [dhcwg] 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: Mon, 14 Nov 2011 10:11:22 -0000

Le 14/11/2011 03:24, Ted Lemon a écrit :
> On Nov 14, 2011, at 9:59 AM, "Ole Troan"<otroan@employees.org>
> wrote:
>> why not just merge all the information received? e.g. if you get
>> DNS server over DHCP and RA, use all. if you get addresses via
>> SLAAC and DHCP, you use all...
>
> Because "just merge" is essentially equivalent to "just walk across
> the river without your feet getting wet.".

One ingredient helping the merge is to represent data in the same
manner.  It would hardly merge two default route entries with a
lifetime on 32bit and another on 16bit.

Alex

> If you can write a spec that does this correctly, you are probably
> the Messiah. _______________________________________________ dhcwg
> mailing list dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>



From Ted.Lemon@nominum.com  Mon Nov 14 02:26:16 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 7DAD021F8AFF; Mon, 14 Nov 2011 02:26:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.558
X-Spam-Level: 
X-Spam-Status: No, score=-106.558 tagged_above=-999 required=5 tests=[AWL=0.041, 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 6-AYzGQ40vSI; Mon, 14 Nov 2011 02:26:16 -0800 (PST)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id E075921F8468; Mon, 14 Nov 2011 02:26:13 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKTsDsxeVDLEQoMjTbPB4D6cP2l3c2KY6I@postini.com; Mon, 14 Nov 2011 02:26:14 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 EA9D21B82B4; Mon, 14 Nov 2011 02:26:12 -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 D0DB2190052; Mon, 14 Nov 2011 02:26:11 -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, 14 Nov 2011 02:26:11 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Thread-Topic: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Index: AQHMom9Jeyu5uv/47kCfd4auwPXOIJWsI2EA//+A3MeAAQeogP//fuT6
Date: Mon, 14 Nov 2011 10:26:11 +0000
Message-ID: <87379F9F-CB45-4FC1-B411-26D5BBC2DC89@nominum.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>, <4EC0E891.1060505@gmail.com>
In-Reply-To: <4EC0E891.1060505@gmail.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-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, mif <mif@ietf.org>
Subject: Re: [dhcwg] 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: Mon, 14 Nov 2011 10:26:16 -0000

On Nov 14, 2011, at 6:14 PM, "Alexandru Petrescu" <alexandru.petrescu@gmail=
.com> wrote:
> One ingredient helping the merge is to represent data in the same
> manner.  It would hardly merge two default route entries with a
> lifetime on 32bit and another on 16bit.

Again?   Oy.=20

The problem of merging has to do with orthogonal (and possibly untrustworth=
y) administrative domains, not trivial differences in data representation. =
 If /only/ the problem were that simple!=

From denghui02@gmail.com  Mon Nov 14 03:10:57 2011
Return-Path: <denghui02@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 103B421F8B7E; Mon, 14 Nov 2011 03:10:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 FExjS5TWswYC; Mon, 14 Nov 2011 03:10:56 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9459421F8B84; Mon, 14 Nov 2011 03:10:54 -0800 (PST)
Received: by yenq4 with SMTP id q4so3201678yen.31 for <multiple recipients>; Mon, 14 Nov 2011 03:10:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=Z1teKVB2wgHV9DSqbcgeaFDvjZCM/6R9OBLzxwJM56Y=; b=oFNvCqXlml+Lnm+ijwyxiMCr+QPTVMFfFpQ98SR7sxxSjGbFzSPNSMh9yDcSybthnx B6pwy2F9V17E7o2KEtJ5UzdA7Hp/uOgOgMvcTVSBeas+bcNcICt3JcR+k6hgGMw/qLAN e12H8MGaUWeojuIjo+jVllzMPLoc7tacK8hFk=
MIME-Version: 1.0
Received: by 10.236.155.2 with SMTP id i2mr13727959yhk.115.1321269038977; Mon, 14 Nov 2011 03:10:38 -0800 (PST)
Received: by 10.146.84.10 with HTTP; Mon, 14 Nov 2011 03:10:38 -0800 (PST)
Date: Mon, 14 Nov 2011 19:10:38 +0800
Message-ID: <CANF0JMDxqGPZNbTCzXUGRMvi2=aFN8VxqBnhNmt7jLRntbNybg@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>, ipv6@ietf.org
Content-Type: multipart/alternative; boundary=20cf30363adbb8934404b1afeb9f
Subject: [dhcwg] New MIF agenda posted
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, 14 Nov 2011 11:10:57 -0000

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

Hello all

We are going to postpone the mif dhc route option discussion to the second
session to avoid the confliction with Softwire

http://www.ietf.org/proceedings/82/agenda/mif.txt

thanks for your work

-Hui

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

<div>Hello all</div>
<div>=A0</div>
<div>We are going to postpone the mif dhc route option discussion to the se=
cond session to avoid the confliction with Softwire</div>
<div>=A0</div>
<div><a href=3D"http://www.ietf.org/proceedings/82/agenda/mif.txt">http://w=
ww.ietf.org/proceedings/82/agenda/mif.txt</a></div>
<div>=A0</div>
<div>thanks for your work</div>
<div>=A0</div>
<div>-Hui</div>

--20cf30363adbb8934404b1afeb9f--

From maximilien.mouton@gmail.com  Mon Nov 14 03:58:30 2011
Return-Path: <maximilien.mouton@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 8524111E8193; Mon, 14 Nov 2011 03:58:30 -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 usJrHEFm7kVn; Mon, 14 Nov 2011 03:58:30 -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 84A2111E814A; Mon, 14 Nov 2011 03:58:29 -0800 (PST)
Received: by bkbzv15 with SMTP id zv15so7175657bkb.31 for <multiple recipients>; Mon, 14 Nov 2011 03:58:27 -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:content-transfer-encoding; bh=PM43X7tV3Cu0+V5/G3yKhiFse0AXfbgnyWoWIwwoTDo=; b=Wy6zsv67ARlUmeL/MUVbAfT0XOpQ2fhZzyIG521EuxR1QaQvdbEYOVZB9cKLiLRbGx tn0qH+xKrsEJzrzjAz6b2pHpHChh+dql6Z8n7Zm2AWTFhgiF2YfphC//oSvqwtDYrVQ5 3o/5XNEmHxJGbiHo5Qm0aSGYSz3m+VYFOhh38=
MIME-Version: 1.0
Received: by 10.205.133.16 with SMTP id hw16mr11106259bkc.128.1321271907226; Mon, 14 Nov 2011 03:58:27 -0800 (PST)
Received: by 10.223.81.77 with HTTP; Mon, 14 Nov 2011 03:58:26 -0800 (PST)
In-Reply-To: <87379F9F-CB45-4FC1-B411-26D5BBC2DC89@nominum.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com> <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com> <4EC0E891.1060505@gmail.com> <87379F9F-CB45-4FC1-B411-26D5BBC2DC89@nominum.com>
Date: Mon, 14 Nov 2011 12:58:26 +0100
Message-ID: <CALGcXUr5iayG9C3pm0UpZxfYjFFbw7i-YOsNgCxW5K2wy4ROtg@mail.gmail.com>
From: Maximilien Mouton <maximilien.mouton@gmail.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Alexandru Petrescu <alexandru.petrescu@gmail.com>, mif <mif@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: Mon, 14 Nov 2011 11:58:30 -0000

Hello Ted, dhc and mif,

>
>-----Original Message-----
>From: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] On Behalf Of
>Ted Lemon
>Sent: lundi 14 novembre 2011 11:26
>To: Alexandru Petrescu
>Cc: dhcwg@ietf.org; mif
>Subject: Re: [mif] [dhcwg] Conflict between RA and DHCP in MIF case
>
>On Nov 14, 2011, at 6:14 PM, "Alexandru Petrescu" <alexandru.petrescu@gmai=
l.com> wrote:
>> One ingredient helping the merge is to represent data in the same
>> manner.=A0 It would hardly merge two default route entries with a
>> lifetime on 32bit and another on 16bit.
>
>Again?=A0=A0 Oy.
>
>The problem of merging has to do with orthogonal (and possibly untrustwort=
hy) administrative domains, not trivial differences in data representation.=
=A0 If /only/ the problem were that simple!
>


We all agree that this problem is not that simple.
I think if both RA and DHCP are trustworthy, information received can
be merge and consistent lifetimes size help to do this.
In case of conflict a choice as to be made by the client.
I agree with the rules stated by Hui.

But, for some cases, one way of managing RA and DHCP information is
already close to exist because rcf 4191 and draft route option (it is
not quite clear but it seems) propose route preference option.

Thus, with current specifications, if RA provides a default route with
a high preference and DHCP another default route with medium
preference the client should take RA's default route and vice versa.

The question is: Has this information decided by admins to prevail
over the rules stated here? If yes when?

Personally I think that clients should have the last word.


Maximilien

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

From mohta@necom830.hpcl.titech.ac.jp  Mon Nov 14 05:42:28 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 1309B11E80EF for <dhcwg@ietfa.amsl.com>; Mon, 14 Nov 2011 05:42:28 -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 8ODtBUG8TnGq for <dhcwg@ietfa.amsl.com>; Mon, 14 Nov 2011 05:42:27 -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 0AA8A11E80DA for <dhcwg@ietf.org>; Mon, 14 Nov 2011 05:42:26 -0800 (PST)
Received: (qmail 36038 invoked from network); 14 Nov 2011 14:09:27 -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; 14 Nov 2011 14:09:27 -0000
Message-ID: <4EC11A8B.50507@necom830.hpcl.titech.ac.jp>
Date: Mon, 14 Nov 2011 22:41:31 +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: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
In-Reply-To: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] 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: Mon, 14 Nov 2011 13:42:28 -0000

Hui Deng wrote:

> To summarize the discussion so far, Ted Lemon on MIF list agreed that
> DHCP should be preferred.

Then, why not just obsolete RA?

						Masataka Ohta

From pierrick.seite@orange.com  Mon Nov 14 07:41:24 2011
Return-Path: <pierrick.seite@orange.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 0C33511E82D8; Mon, 14 Nov 2011 07:41:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.155
X-Spam-Level: 
X-Spam-Status: No, score=-3.155 tagged_above=-999 required=5 tests=[AWL=0.094,  BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 plpdjwtSR6rr; Mon, 14 Nov 2011 07:41:23 -0800 (PST)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by ietfa.amsl.com (Postfix) with ESMTP id 3CD2011E82B4; Mon, 14 Nov 2011 07:41:23 -0800 (PST)
Received: from p-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id C7C09B58004; Mon, 14 Nov 2011 16:51:37 +0100 (CET)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by p-mail2.rd.francetelecom.com (Postfix) with ESMTP id BDBCB858001; Mon, 14 Nov 2011 16:51:37 +0100 (CET)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 14 Nov 2011 16:41:22 +0100
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: Mon, 14 Nov 2011 16:41:19 +0100
Message-ID: <843DA8228A1BA74CA31FB4E111A5C46202068093@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <CALGcXUr5iayG9C3pm0UpZxfYjFFbw7i-YOsNgCxW5K2wy4ROtg@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [mif] [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Index: AcyixLuKGCucSkSrSwqPgELD/3H0ggAHbP0g
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com><402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org><23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com><4EC0E891.1060505@gmail.com><87379F9F-CB45-4FC1-B411-26D5BBC2DC89@nominum.com> <CALGcXUr5iayG9C3pm0UpZxfYjFFbw7i-YOsNgCxW5K2wy4ROtg@mail.gmail.com>
From: <pierrick.seite@orange.com>
To: <maximilien.mouton@gmail.com>, <Ted.Lemon@nominum.com>
X-OriginalArrivalTime: 14 Nov 2011 15:41:22.0661 (UTC) FILETIME=[DC719950:01CCA2E3]
X-Mailman-Approved-At: Mon, 14 Nov 2011 14:04:46 -0800
Cc: dhcwg@ietf.org, mif@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: Mon, 14 Nov 2011 15:41:24 -0000

Hi,

IMU, conflict issue raises up when the node is simultaneously attached =
to two different administrative domains. In that case, we can't assume =
consistency in lifetime size or default route preference or whatever... =
In that case, it is reasonable to state that the node should apply the =
default policy as suggested by Hui. =20

Pierrick
> -----Message d'origine-----
> De=A0: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] De la part =
de
> Maximilien Mouton
> Envoy=E9=A0: lundi 14 novembre 2011 12:58
> =C0=A0: Ted Lemon
> Cc=A0: dhcwg@ietf.org; mif
> Objet=A0: Re: [mif] [dhcwg] Conflict between RA and DHCP in MIF case
>=20
> Hello Ted, dhc and mif,
>=20
> >
> >-----Original Message-----
> >From: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] On Behalf Of
> >Ted Lemon
> >Sent: lundi 14 novembre 2011 11:26
> >To: Alexandru Petrescu
> >Cc: dhcwg@ietf.org; mif
> >Subject: Re: [mif] [dhcwg] Conflict between RA and DHCP in MIF case
> >
> >On Nov 14, 2011, at 6:14 PM, "Alexandru Petrescu"
> <alexandru.petrescu@gmail.com> wrote:
> >> One ingredient helping the merge is to represent data in the same
> >> manner.=A0 It would hardly merge two default route entries with a
> >> lifetime on 32bit and another on 16bit.
> >
> >Again?=A0=A0 Oy.
> >
> >The problem of merging has to do with orthogonal (and possibly
> untrustworthy) administrative domains, not trivial differences in data
> representation.=A0 If /only/ the problem were that simple!
> >
>=20
>=20
> We all agree that this problem is not that simple.
> I think if both RA and DHCP are trustworthy, information received can
> be merge and consistent lifetimes size help to do this.
> In case of conflict a choice as to be made by the client.
> I agree with the rules stated by Hui.
>=20
> But, for some cases, one way of managing RA and DHCP information is
> already close to exist because rcf 4191 and draft route option (it is
> not quite clear but it seems) propose route preference option.
>=20
> Thus, with current specifications, if RA provides a default route with
> a high preference and DHCP another default route with medium
> preference the client should take RA's default route and vice versa.
>=20
> The question is: Has this information decided by admins to prevail
> over the rules stated here? If yes when?
>=20
> Personally I think that clients should have the last word.
>=20
>=20
> Maximilien
>=20
> >_______________________________________________
> >mif mailing list
> >mif@ietf.org
> >https://www.ietf.org/mailman/listinfo/mif
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif

From rdroms.ietf@gmail.com  Mon Nov 14 15:58: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 825B521F8E21 for <dhcwg@ietfa.amsl.com>; Mon, 14 Nov 2011 15:58:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level: 
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=0.500, 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 uBvx3W+N307p for <dhcwg@ietfa.amsl.com>; Mon, 14 Nov 2011 15:58:17 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7755821F8E1D for <dhcwg@ietf.org>; Mon, 14 Nov 2011 15:58:17 -0800 (PST)
Received: by yenq4 with SMTP id q4so4059638yen.31 for <dhcwg@ietf.org>; Mon, 14 Nov 2011 15:58:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:references :to:message-id:mime-version:x-mailer; bh=PEEzX/VPlvkAjEawrlg/Qi7k30wPb6Gl2qI1eKIpN38=; b=g0z6+joGWlIEiExniLuCsOCp461MhXh11jdpIi/G2ha9qdEUwUVuUrcvt2DxI7X+5o piaJpC49sbN3f/ynLZYcOLpmTJYUbW4BsHnyPuu4/8LpQR8qjdjTxoyRQyBt71I4Vnam H7nn3RYyqaJ4o5sGbzE57ESwlAzS0627kZUyE=
Received: by 10.68.24.65 with SMTP id s1mr53724159pbf.12.1321315094234; Mon, 14 Nov 2011 15:58:14 -0800 (PST)
Received: from [10.21.76.199] (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id lk8sm60329687pbb.4.2011.11.14.15.58.12 (version=SSLv3 cipher=OTHER); Mon, 14 Nov 2011 15:58:13 -0800 (PST)
From: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 15 Nov 2011 07:58:09 +0800
References: <20111114165021.13793.27380.idtracker@ietfa.amsl.com>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Message-Id: <7C21DE61-D540-4E0E-ACC3-A2BC22C4A72F@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1251.1)
X-Mailer: Apple Mail (2.1251.1)
Subject: [dhcwg] Fwd: New Version Notification for draft-droms-dhc-dhcpv6-maxsolrt-update-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: Mon, 14 Nov 2011 23:58:21 -0000

FYI.  Please take a quick look at this draft (it's pretty short) prior =
to a brief discussion in the WG meeting this week.

- Ralph

Begin forwarded message:

> From: internet-drafts@ietf.org
> Subject: New Version Notification for =
draft-droms-dhc-dhcpv6-maxsolrt-update-00.txt
> Date: November 15, 2011 12:50:21 AM GMT+08:00
> To: rdroms@cisco.com
> Cc: rdroms@cisco.com
>=20
> A new version of I-D, draft-droms-dhc-dhcpv6-maxsolrt-update-00.txt =
has been successfully submitted by Ralph Droms and posted to the IETF =
repository.
>=20
> Filename:	 draft-droms-dhc-dhcpv6-maxsolrt-update
> Revision:	 00
> Title:		 Modification to Default Value of MAX_SOL_RT
> Creation date:	 2011-11-14
> WG ID:		 Individual Submission
> Number of pages: 4
>=20
> Abstract:
>  This document updates RFC 3315 by redefining the default value for
>  SOL_MAX_RT and defining an option through which a DHCPv6 server can
>  override the client&#39;s default value for SOL_MAX_RT with a new =
value.
>=20
>=20
>=20
>=20
> The IETF Secretariat


From ichiroumakino@gmail.com  Tue Nov 15 05:42:27 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 F3C9411E813F; Tue, 15 Nov 2011 05:42:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.539
X-Spam-Level: 
X-Spam-Status: No, score=-3.539 tagged_above=-999 required=5 tests=[AWL=0.060,  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 EQ2JnED4l4+j; Tue, 15 Nov 2011 05:42:26 -0800 (PST)
Received: from mail-pz0-f50.google.com (mail-pz0-f50.google.com [209.85.210.50]) by ietfa.amsl.com (Postfix) with ESMTP id 72D4811E811F; Tue, 15 Nov 2011 05:42:26 -0800 (PST)
Received: by pzk5 with SMTP id 5so12761560pzk.9 for <multiple recipients>; Tue, 15 Nov 2011 05:42:25 -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=SZK/RAbhp7ycL8jNYeBDdiYvPJ72AKTj399JKaJgIxM=; b=u7HLx/2PaVEWiukaiGjQ81Aib2W5zhnSaGaOS07PZq7yQtdpmxqXLJEEwhJ0lD1OKh mqALpDnPpmwLnXsT2tdPGKPhnmzelvAVCnbFn7V79vZsXwwBPR50ydHcWGOZ2RaWuWRA 0SqBZpUw5IJAWZHFLS9242/n76zpzVK00GwH8=
Received: by 10.68.2.72 with SMTP id 8mr6871530pbs.11.1321364545778; Tue, 15 Nov 2011 05:42:25 -0800 (PST)
Received: from sjc-vpn4-486.cisco.com (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id wf19sm65091211pbb.17.2011.11.15.05.42.20 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Nov 2011 05:42:24 -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: <87379F9F-CB45-4FC1-B411-26D5BBC2DC89@nominum.com>
Date: Tue, 15 Nov 2011 21:42:13 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <452CD809-3935-4852-B0AF-F8B042742BE7@employees.org>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>, <4EC0E891.1060505@gmail.com> <87379F9F-CB45-4FC1-B411-26D5BBC2DC89@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1084)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Alexandru Petrescu <alexandru.petrescu@gmail.com>, mif <mif@ietf.org>
Subject: Re: [dhcwg] 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: Tue, 15 Nov 2011 13:42:27 -0000

>> One ingredient helping the merge is to represent data in the same
>> manner.  It would hardly merge two default route entries with a
>> lifetime on 32bit and another on 16bit.
>=20
> Again?   Oy.=20
>=20
> The problem of merging has to do with orthogonal (and possibly =
untrustworthy) administrative domains, not trivial differences in data =
representation.  If /only/ the problem were that simple!

how is a network (that I don't trust) going to tell me that I should =
trust it's information?
making DHCP preferred over RA seems irrelevant here.

cheers,
Ole


From internet-drafts@ietf.org  Tue Nov 15 11:02:20 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 4E31A11E80CF; Tue, 15 Nov 2011 11:02:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.581
X-Spam-Level: 
X-Spam-Status: No, score=-102.581 tagged_above=-999 required=5 tests=[AWL=0.018, 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 mPgzk2WO3BC5; Tue, 15 Nov 2011 11:02:15 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6EF711E8085; Tue, 15 Nov 2011 11:02:15 -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.63
Message-ID: <20111115190215.13589.40684.idtracker@ietfa.amsl.com>
Date: Tue, 15 Nov 2011 11:02:15 -0800
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-vpn-option-14.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, 15 Nov 2011 19:02:20 -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           : Virtual Subnet Selection Options for DHCPv4 and DHCPv6
	Author(s)       : Kim Kinnear
                          Richard Johnson
                          Mark Stapp
                          Jay Kumarasamy
	Filename        : draft-ietf-dhc-vpn-option-14.txt
	Pages           : 26
	Date            : 2011-11-15

   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).


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-vpn-option-14.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-vpn-option-14.txt

From Ted.Lemon@nominum.com  Tue Nov 15 13:17:39 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 387021F0C42; Tue, 15 Nov 2011 13:17:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.561
X-Spam-Level: 
X-Spam-Status: No, score=-106.561 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 A1i5gUiAskNx; Tue, 15 Nov 2011 13:17:38 -0800 (PST)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id E00591F0C4E; Tue, 15 Nov 2011 13:17:37 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKTsLW6ktkmdwJC+BR5dY4WBYGebm+54y6@postini.com; Tue, 15 Nov 2011 13:17:38 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 658E11B82A1; Tue, 15 Nov 2011 13:17:30 -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 34DD8190052; Tue, 15 Nov 2011 13:17: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; Tue, 15 Nov 2011 13:17:29 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ole Troan <otroan@employees.org>
Thread-Topic: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Index: AQHMom9Jeyu5uv/47kCfd4auwPXOIJWsI2EA//+A3MeAAQeogP//fuT6gAJPN4D///kXvA==
Date: Tue, 15 Nov 2011 21:17:29 +0000
Message-ID: <8844B648-51D8-43F3-92C2-8403FD032058@nominum.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>, <4EC0E891.1060505@gmail.com> <87379F9F-CB45-4FC1-B411-26D5BBC2DC89@nominum.com>, <452CD809-3935-4852-B0AF-F8B042742BE7@employees.org>
In-Reply-To: <452CD809-3935-4852-B0AF-F8B042742BE7@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: "dhcwg@ietf.org" <dhcwg@ietf.org>, Alexandru Petrescu <alexandru.petrescu@gmail.com>, mif <mif@ietf.org>
Subject: Re: [dhcwg] 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: Tue, 15 Nov 2011 21:17:39 -0000

On Nov 15, 2011, at 9:42 PM, "Ole Troan" <otroan@employees.org> wrote:
> how is a network (that I don't trust) going to tell me that I should trus=
t it's information?
> making DHCP preferred over RA seems irrelevant here.

Well, things have moved on from this discussion, and now we are thinking th=
at preferring DHCP actually breaks some things that people care about, so w=
e're moving back in the direction of preferring RA.   In answer to your que=
stion, of course there's no way, in the abstract, to know what you can and =
can't trust.=

From rdroms.ietf@gmail.com  Tue Nov 15 20:48:25 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 5912311E811C; Tue, 15 Nov 2011 20:48:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level: 
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=-0.100, 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 E-iG-fGMCtOs; Tue, 15 Nov 2011 20:48:21 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 28C9C11E80CC; Tue, 15 Nov 2011 20:48:21 -0800 (PST)
Received: by ywt34 with SMTP id 34so7319960ywt.31 for <multiple recipients>; Tue, 15 Nov 2011 20:48: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=8RA4qR8MwZzsctzU16FAC2qE+YJF0srkdm3D8ewHt8w=; b=WDvRkJcUaW1/EZbyoebHvy1PmQH0QvW+V+joSUecJIVPkwUdcgOLYfpVd4lw0HThNK CpyfPJZpqK/qAriFXS/OU+KaaQkAO3yZow3Cw1W/RZXDLDwZ4nN9qNYDW9OTmHnjkeL2 I1rUCk0z+/hQovLiO+R+jTlk8AMh3LHxlr92U=
Received: by 10.50.216.134 with SMTP id oq6mr33078721igc.11.1321418897942; Tue, 15 Nov 2011 20:48:17 -0800 (PST)
Received: from sjc-vpn5-293.cisco.com (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id j1sm21683501igq.2.2011.11.15.20.48.15 (version=SSLv3 cipher=OTHER); Tue, 15 Nov 2011 20:48:17 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=windows-1252
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C30354434B@XMB-RCD-109.cisco.com>
Date: Wed, 16 Nov 2011 12:48:12 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <E24C5AA6-91AD-4A22-9A9D-0128663E5641@gmail.com>
References: <269B69AA-6A20-4A15-A1E2-63A54FB973FB@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C30354434B@XMB-RCD-109.cisco.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>, IPv6 Operations <v6ops@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [dhcwg] [v6ops] DHCPv6 option for MAX_SOL_RT
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, 16 Nov 2011 04:48:25 -0000

Yeah, the text should probably refer to IA_PD as well.  Forwarding to =
dhc WG as well for comment before I make a change.

- Ralph

On Nov 16, 2011, at 12:40 PM 11/16/11, Hemant Singh (shemant) wrote:

> Ralph,
> =20
> Thanks much for the URL to the doc.  One question related to this text =
from the document snipped below between squared braces.
> =20
> [If the DHCPv6 server declines to assign any addresses to a client in
> an IA_NA or IA_TA option,]
> =20
> The WAN interface on an IPv6 CE router is using an unnumbered WAN =
model and thus the WAN DHCPv6 client request may only include an IA_PD =
option.  Thus, don=92t we have to include the IA_PD option to the text =
above?  If yes, then some other text immediately below in the document =
also changes to include the IA_PD.
> =20
> Regards,
> =20
> Hemant
> =20
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf =
Of Ralph Droms
> Sent: Wednesday, November 16, 2011 9:28 AM
> To: v6ops@ietf.org
> Subject: [v6ops] DHCPv6 option for MAX_SOL_RT
> =20
>=20
> ...is here: =
http://tools.ietf.org/html/draft-droms-dhc-dhcpv6-maxsolrt-update-00
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From shemant@cisco.com  Tue Nov 15 21:02:46 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 CF6821F0CC7; Tue, 15 Nov 2011 21:02:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.915
X-Spam-Level: 
X-Spam-Status: No, score=-5.915 tagged_above=-999 required=5 tests=[AWL=0.084,  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 PykT8sWxGaoH; Tue, 15 Nov 2011 21:02:42 -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 C78931F0C9B; Tue, 15 Nov 2011 21:02:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=1572; q=dns/txt; s=iport; t=1321419761; x=1322629361; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=yOMF7NGT99yQKkp/gU7JG9HC7O+ih3RndUha1oKlMjQ=; b=LMNZmdQU3fMp2cVmveLdkjPuANj6EeN0M1gyNeqWvfhdNwfCB4ui6LtB BqeYAB69OE7+7LVOby/+c/pBnlPvvKV1saKpJ5myogscw6bcAYixWvnV3 zHWZslOOXSIXNA44tt6rWBo31PoupROgP/0xDFIqQq+O9gUtuPDgzTYkD s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnsAAEVDw06rRDoJ/2dsb2JhbABDmWqQCIEFgXIBAQEDAQEBAQ8BHQo0CwUHBAIBCA4DBAEBCwYXAQYBIAYfCQgBAQQTCBqHYAiaXQGeVYk0YwSIFJFkgzqBTYdQ
X-IronPort-AV: E=Sophos;i="4.69,519,1315180800"; d="scan'208";a="14541471"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-4.cisco.com with ESMTP; 16 Nov 2011 05:02:41 +0000
Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pAG52frt015677; Wed, 16 Nov 2011 05:02:41 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, 15 Nov 2011 23:02:41 -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, 15 Nov 2011 23:02:37 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C30354434F@XMB-RCD-109.cisco.com>
In-Reply-To: <E24C5AA6-91AD-4A22-9A9D-0128663E5641@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops] DHCPv6 option for MAX_SOL_RT
Thread-Index: AcykGvXJ9btRCyV6QUyI2s3Df0IPbAAAfuVw
References: <269B69AA-6A20-4A15-A1E2-63A54FB973FB@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C30354434B@XMB-RCD-109.cisco.com> <E24C5AA6-91AD-4A22-9A9D-0128663E5641@gmail.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Ralph Droms" <rdroms.ietf@gmail.com>
X-OriginalArrivalTime: 16 Nov 2011 05:02:41.0151 (UTC) FILETIME=[F7DEB8F0:01CCA41C]
Cc: dhcwg@ietf.org, IPv6 Operations <v6ops@ietf.org>
Subject: Re: [dhcwg] [v6ops] DHCPv6 option for MAX_SOL_RT
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, 16 Nov 2011 05:02:47 -0000

Great, thanks,

Hemant

-----Original Message-----
From: Ralph Droms [mailto:rdroms.ietf@gmail.com]=20
Sent: Wednesday, November 16, 2011 12:48 PM
To: Hemant Singh (shemant)
Cc: Ralph Droms; IPv6 Operations; dhcwg@ietf.org WG
Subject: Re: [v6ops] DHCPv6 option for MAX_SOL_RT

Yeah, the text should probably refer to IA_PD as well.  Forwarding to
dhc WG as well for comment before I make a change.

- Ralph

On Nov 16, 2011, at 12:40 PM 11/16/11, Hemant Singh (shemant) wrote:

> Ralph,
> =20
> Thanks much for the URL to the doc.  One question related to this text
from the document snipped below between squared braces.
> =20
> [If the DHCPv6 server declines to assign any addresses to a client in
> an IA_NA or IA_TA option,]
> =20
> The WAN interface on an IPv6 CE router is using an unnumbered WAN
model and thus the WAN DHCPv6 client request may only include an IA_PD
option.  Thus, don't we have to include the IA_PD option to the text
above?  If yes, then some other text immediately below in the document
also changes to include the IA_PD.
> =20
> Regards,
> =20
> Hemant
> =20
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf
Of Ralph Droms
> Sent: Wednesday, November 16, 2011 9:28 AM
> To: v6ops@ietf.org
> Subject: [v6ops] DHCPv6 option for MAX_SOL_RT
> =20
>=20
> ...is here:
http://tools.ietf.org/html/draft-droms-dhc-dhcpv6-maxsolrt-update-00
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From brian.e.carpenter@gmail.com  Wed Nov 16 02:04:28 2011
Return-Path: <brian.e.carpenter@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 432A221F95D8; Wed, 16 Nov 2011 02:04:28 -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 izrW77luEZ0f; Wed, 16 Nov 2011 02:04:27 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4707F21F95E2; Wed, 16 Nov 2011 02:04:27 -0800 (PST)
Received: by ywt34 with SMTP id 34so7646713ywt.31 for <multiple recipients>; Wed, 16 Nov 2011 02:04:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=DHpFFub65OKbiv7ZBryZQMnUs4hr2+lzp799UIkqRYI=; b=uCpdzLO7a8BkltqysRjhSfjVA+USgEpNj7mP+aY7IRMwZYe+GHPVUuCYooeVaEPOZ2 C3pl7BW4+2E8ZZ4IZ/XhAPu9l5surus0LPcIHHaJ32sIfkM3qBkeG3pVoFTcnhUMSIFL KKfv+NrBGqdmfo+tKoc+/WYP6C3Oms9/kLXjk=
Received: by 10.236.191.198 with SMTP id g46mr25645yhn.118.1321437866485; Wed, 16 Nov 2011 02:04:26 -0800 (PST)
Received: from [130.129.19.92] (dhcp-135c.meeting.ietf.org. [130.129.19.92]) by mx.google.com with ESMTPS id f32sm84594093ani.20.2011.11.16.02.04.23 (version=SSLv3 cipher=OTHER); Wed, 16 Nov 2011 02:04:25 -0800 (PST)
Message-ID: <4EC38AA1.3070104@gmail.com>
Date: Wed, 16 Nov 2011 23:04:17 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Dmitry Anipko <Dmitry.Anipko@microsoft.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org>	<23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>, <4EC0E891.1060505@gmail.com>	<87379F9F-CB45-4FC1-B411-26D5BBC2DC89@nominum.com>, <452CD809-3935-4852-B0AF-F8B042742BE7@employees.org>	<8844B648-51D8-43F3-92C2-8403FD032058@nominum.com> <03FE6A726D13284495EF1787D25F1DF9018EDD41@TK5EX14MBXC264.redmond.corp.microsoft.com>
In-Reply-To: <03FE6A726D13284495EF1787D25F1DF9018EDD41@TK5EX14MBXC264.redmond.corp.microsoft.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, mif <mif@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
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, 16 Nov 2011 10:04:28 -0000

The main message I got was that there needs to be great care to ensure
that the semantics of information received via RA should be the
same (modulo superset/subset) as information received via DHCPv6.
That way, merging them becomes feasible.

   Brian

On 2011-11-16 22:34, Dmitry Anipko wrote:
>>> so we're moving back in the direction of preferring RA
> 
> My understanding is that part of the feedback from the room was also to move from "pick one" to "merge with tie breakers" approach, that would be no different from other cases where e.g. multiple RAs with settings of the same kind have been received and those settings are merged (specific prefixes, DNS settings etc).
> 
> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of Ted Lemon
> Sent: Tuesday, November 15, 2011 1:17 PM
> To: Ole Troan
> Cc: dhcwg@ietf.org; Alexandru Petrescu; mif
> Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case
> 
> On Nov 15, 2011, at 9:42 PM, "Ole Troan" <otroan@employees.org> wrote:
>> how is a network (that I don't trust) going to tell me that I should trust it's information?
>> making DHCP preferred over RA seems irrelevant here.
> 
> Well, things have moved on from this discussion, and now we are thinking that preferring DHCP actually breaks some things that people care about, so we're moving back in the direction of preferring RA.   In answer to your question, of course there's no way, in the abstract, to know what you can and can't trust.
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
> 
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif
> 

From Dmitry.Anipko@microsoft.com  Wed Nov 16 01:34:28 2011
Return-Path: <Dmitry.Anipko@microsoft.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 A7F6721F94B3; Wed, 16 Nov 2011 01:34:28 -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=[AWL=0.000, 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 v2qMQb3Bt8-5; Wed, 16 Nov 2011 01:34:28 -0800 (PST)
Received: from smtp.microsoft.com (smtp.microsoft.com [131.107.115.215]) by ietfa.amsl.com (Postfix) with ESMTP id 2E90421F947E; Wed, 16 Nov 2011 01:34:28 -0800 (PST)
Received: from TK5EX14HUBC101.redmond.corp.microsoft.com (157.54.7.153) by TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with Microsoft SMTP Server (TLS) id 8.2.176.0; Wed, 16 Nov 2011 01:34:27 -0800
Received: from TK5EX14MBXC264.redmond.corp.microsoft.com ([169.254.1.220]) by TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi id 14.01.0355.003; Wed, 16 Nov 2011 01:34:27 -0800
From: Dmitry Anipko <Dmitry.Anipko@microsoft.com>
To: Ted Lemon <Ted.Lemon@nominum.com>, Ole Troan <otroan@employees.org>
Thread-Topic: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Index: AQHMom9K7XpxT/ARnkOuxygcgg3TeZWsI2EAgAAG+ICAAIGMgIAABQGAgAHJGoCAAH8zgIAARtGg
Date: Wed, 16 Nov 2011 09:34:27 +0000
Message-ID: <03FE6A726D13284495EF1787D25F1DF9018EDD41@TK5EX14MBXC264.redmond.corp.microsoft.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>, <4EC0E891.1060505@gmail.com> <87379F9F-CB45-4FC1-B411-26D5BBC2DC89@nominum.com>, <452CD809-3935-4852-B0AF-F8B042742BE7@employees.org> <8844B648-51D8-43F3-92C2-8403FD032058@nominum.com>
In-Reply-To: <8844B648-51D8-43F3-92C2-8403FD032058@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.22]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 16 Nov 2011 02:14:05 -0800
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Alexandru Petrescu <alexandru.petrescu@gmail.com>, mif <mif@ietf.org>
Subject: Re: [dhcwg] 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, 16 Nov 2011 09:34:28 -0000

>> so we're moving back in the direction of preferring RA

My understanding is that part of the feedback from the room was also to mov=
e from "pick one" to "merge with tie breakers" approach, that would be no d=
ifferent from other cases where e.g. multiple RAs with settings of the same=
 kind have been received and those settings are merged (specific prefixes, =
DNS settings etc).

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of T=
ed Lemon
Sent: Tuesday, November 15, 2011 1:17 PM
To: Ole Troan
Cc: dhcwg@ietf.org; Alexandru Petrescu; mif
Subject: Re: [dhcwg] Conflict between RA and DHCP in MIF case

On Nov 15, 2011, at 9:42 PM, "Ole Troan" <otroan@employees.org> wrote:
> how is a network (that I don't trust) going to tell me that I should trus=
t it's information?
> making DHCP preferred over RA seems irrelevant here.

Well, things have moved on from this discussion, and now we are thinking th=
at preferring DHCP actually breaks some things that people care about, so w=
e're moving back in the direction of preferring RA.   In answer to your que=
stion, of course there's no way, in the abstract, to know what you can and =
can't trust.
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg


From tomasz.mrugalski@gmail.com  Wed Nov 16 03:25:28 2011
Return-Path: <tomasz.mrugalski@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 E3FD521F944D for <dhcwg@ietfa.amsl.com>; Wed, 16 Nov 2011 03:25:28 -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 d6hA0kbZbBlz for <dhcwg@ietfa.amsl.com>; Wed, 16 Nov 2011 03:25:28 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5FD4921F943E for <dhcwg@ietf.org>; Wed, 16 Nov 2011 03:25:28 -0800 (PST)
Received: by yenq4 with SMTP id q4so6340192yen.31 for <dhcwg@ietf.org>; Wed, 16 Nov 2011 03:25:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=mIOk8nTn00EJyL/xlmNv11j2HW/56s9yZ40IQ/TuEMg=; b=mMjKFloiP1hKFth8ppczPXHj2J91mYNDgFi2CDFkOUxNBpEnggzxay3PVxBCOSVb5/ +/PldfSQmFMdp3wBhVkzAcI0ed1UAGjVmryyOg+2h0skTgVR/LGTSO8kcgXYo4LLXv3B HCMRteI5Y2DPKJHodPOyETBUv2hNk3yV/+bF0=
Received: by 10.236.109.231 with SMTP id s67mr254159yhg.103.1321442728041; Wed, 16 Nov 2011 03:25:28 -0800 (PST)
Received: from dhcp-158e.meeting.ietf.org ([2001:df8:0:16:cabc:c8ff:fedf:daff]) by mx.google.com with ESMTPS id 33sm69601007ano.1.2011.11.16.03.25.25 (version=SSLv3 cipher=OTHER); Wed, 16 Nov 2011 03:25:26 -0800 (PST)
Message-ID: <4EC39DA3.70603@gmail.com>
Date: Wed, 16 Nov 2011 19:25:23 +0800
From: Tomek Mrugalski <tomasz.mrugalski@gmail.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: dhcwg@ietf.org
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com> <4EC11A8B.50507@necom830.hpcl.titech.ac.jp>
In-Reply-To: <4EC11A8B.50507@necom830.hpcl.titech.ac.jp>
X-Enigmail-Version: 1.3.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] 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, 16 Nov 2011 11:25:29 -0000

On 11-11-14 21:41, Masataka Ohta wrote:
> Hui Deng wrote:
> 
>> To summarize the discussion so far, Ted Lemon on MIF list agreed
>> that DHCP should be preferred.
> 
> Then, why not just obsolete RA?
That's definitely a step too far. There are networks that do not
deploy DHCPv6 at all. The need to work. Thus RA is and remain to be needed.

There is significant demand for networks that does not use RA at all.
In such networks DHCPv6 should be able to provision complete set of
routing information. See recent Roberta's post to MIF about rationale
(http://www.ietf.org/mail-archive/web/mif/current/msg01412.html).
Another important list of arguments is provided here:
http://www.ietf.org/proceedings/74/slides/intarea-4.pdf
(Note that it is regarding a different proposal that was abandoned. Key
messages still stand, though).

I see a parallel to the way how addresses can be obtained today
(stateless and over DHCP). Those two methods coexist. Noone sane can
claim that one or the other method will go away. Of course, there are
some cases where one or the other method strongly dominates, but such
cases cannot be generalized ("I don't use feature X, so everyone else
should not use it either" is just wrong).

During recent presentation in MIF, several important aspects were
pointed out. I'll post to MIF, homenet and DHC shortly.

Regarding
Tomek

From mohta@necom830.hpcl.titech.ac.jp  Wed Nov 16 04:04:44 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 D7D8B21F9664 for <dhcwg@ietfa.amsl.com>; Wed, 16 Nov 2011 04:04:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.023
X-Spam-Level: 
X-Spam-Status: No, score=-0.023 tagged_above=-999 required=5 tests=[AWL=0.067,  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 aaV+0bsnvIeY for <dhcwg@ietfa.amsl.com>; Wed, 16 Nov 2011 04:04:44 -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 1350A21F95CA for <dhcwg@ietf.org>; Wed, 16 Nov 2011 04:04:43 -0800 (PST)
Received: (qmail 87583 invoked from network); 16 Nov 2011 12:32:15 -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; 16 Nov 2011 12:32:15 -0000
Message-ID: <4EC3A699.5050708@necom830.hpcl.titech.ac.jp>
Date: Wed, 16 Nov 2011 21:03: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: dhcwg@ietf.org
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com> <4EC11A8B.50507@necom830.hpcl.titech.ac.jp> <4EC39DA3.70603@gmail.com>
In-Reply-To: <4EC39DA3.70603@gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] 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, 16 Nov 2011 12:04:45 -0000

Tomek Mrugalski wrote:

>>> To summarize the discussion so far, Ted Lemon on MIF list agreed
>>> that DHCP should be preferred.
>>
>> Then, why not just obsolete RA?
> That's definitely a step too far.

What is the point to have RA, only to be bothered by DAD
timeout?

> There are networks that do not deploy DHCPv6 at all.

> Thus RA is and remain to be needed.

Note that there are much more networks that do not
deploy IPv6 at all.

> There is significant demand for networks that does not use RA at all.

I know.

> In such networks DHCPv6 should be able to provision complete set of
> routing information.

That's a wrong architecture.

Routing information should be provided by routing protocols.

It is architecturally wrong to try to make end systems
independent to IGPs.

> I see a parallel to the way how addresses can be obtained today
> (stateless and over DHCP). Those two methods coexist. Noone sane can
> claim that one or the other method will go away.

It is a responsibility of IETF to remove unnecessary complexity
caused by useless RA.

Note that so called SLAAC is actually full of states, though
the states are maintained in unnecessarily distributed way by
all the related end systems (each node maintains its own state
of address assignment), which is why, stupidly enough, DAD is
required.

						Masataka Ohta

From tomasz.mrugalski@gmail.com  Thu Nov 17 06:28:05 2011
Return-Path: <tomasz.mrugalski@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 E66F611E814E for <dhcwg@ietfa.amsl.com>; Thu, 17 Nov 2011 06:28:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.239
X-Spam-Level: 
X-Spam-Status: No, score=-3.239 tagged_above=-999 required=5 tests=[AWL=-0.240, 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 lJcqzy3Wv8k9 for <dhcwg@ietfa.amsl.com>; Thu, 17 Nov 2011 06:28:05 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6ADA711E8146 for <dhcwg@ietf.org>; Thu, 17 Nov 2011 06:28:05 -0800 (PST)
Received: by ggnr5 with SMTP id r5so1307977ggn.31 for <dhcwg@ietf.org>; Thu, 17 Nov 2011 06:28:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :x-enigmail-version:content-type:content-transfer-encoding; bh=a/NfReNCJ4jH7VC+mYwNfgvvQAy/5gJR0MUT5yO7VW8=; b=u4mDWGU3+ZC9oR50qYx5cqmFBhzPCItOVi6RtrwQBGU0+ekTkYRgXeT+XCu+NAp14k zrH+FiihcoF279+tCoBeHhN2CcDo4z8OK3YSM3qOXxo2Zst5WI3dpEQbu8kRjjL9Knk6 zCyqGe1xJrSn6voI1EOZHG66g8hr7uea6lvb0=
Received: by 10.236.155.74 with SMTP id i50mr9927819yhk.23.1321540083721; Thu, 17 Nov 2011 06:28:03 -0800 (PST)
Received: from dhcp-41d0.meeting.ietf.org ([2001:df8:0:64:de2b:61ff:fee5:409c]) by mx.google.com with ESMTPS id l18sm3363022anb.22.2011.11.17.06.28.01 (version=SSLv3 cipher=OTHER); Thu, 17 Nov 2011 06:28:02 -0800 (PST)
Message-ID: <4EC519EF.3040309@gmail.com>
Date: Thu, 17 Nov 2011 22:27:59 +0800
From: Tomek Mrugalski <tomasz.mrugalski@gmail.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: DHC WG <dhcwg@ietf.org>
X-Enigmail-Version: 1.3.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Discussion on feasibility of route configuration over DHCPv6
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, 17 Nov 2011 14:28:06 -0000

Hi,
Everyone's favourite topic is back. There is pretty good chance that
current discussion will lead to either publication of
draft-ietf-mif-dhcpv6-route-option or its abandonment.

If you care about this topic, you are encouraged to read and post in:

Why we need route option thread:
http://www.ietf.org/mail-archive/web/mif/current/msg01431.html

Why we should drop route option thread:
http://www.ietf.org/mail-archive/web/mif/current/msg01432.html

There are questions raised if MIF is the best place for this option, but
since it is adopted there, MIF list seems like a reasonable place to
discuss its faith. There are at least 5 (DHC, MIF, HOMENET, V6OPS, 6MAN)
WGs that may be interested in this. There may be others. I consider
cross-posting to 5 mailing lists as highly inappropriate.

Similar posts as this will be sent to DHC, HOMENET, V6OPS and 6MAN shortly.

Cheers,
Tomek Mrugalski
ISC

From internet-drafts@ietf.org  Fri Nov 18 15:03:58 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 DFB9B1F0C7A; Fri, 18 Nov 2011 15:03:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, 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 85+fib4d-TRD; Fri, 18 Nov 2011 15:03:58 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D0C11F0C6A; Fri, 18 Nov 2011 15:03:58 -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: <20111118230358.16866.25988.idtracker@ietfa.amsl.com>
Date: Fri, 18 Nov 2011 15:03:58 -0800
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-bulk-leasequery-05.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, 18 Nov 2011 23:03:59 -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           : Bulk DHCPv4 Lease Query
	Author(s)       : Kim Kinnear
                          Bernie Volz
                          Mark Stapp
                          Bharat Joshi
                          Neil Russell
                          Pavan Kurapati
	Filename        : draft-ietf-dhc-dhcpv4-bulk-leasequery-05.txt
	Pages           : 39
	Date            : 2011-11-18

   The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) Leasequery
   extension allows a requestor to request information about DHCPv4
   bindings. This mechanism is limited to queries for individual
   bindings. In some situations individual binding queries may not be
   efficient, or even possible. This document extends the DHCPv4
   Leasequery protocol to allow for bulk transfer of DHCPv4 address
   binding data via TCP.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv4-bulk-leasequery-0=
5.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-dhcpv4-bulk-leasequery-05=
.txt


From internet-drafts@ietf.org  Sun Nov 20 23:59:10 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 337CF21F8ABD; Sun, 20 Nov 2011 23:59:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, 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 Kpe9kra978TU; Sun, 20 Nov 2011 23:59:09 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC60C21F861E; Sun, 20 Nov 2011 23:59: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: <20111121075909.6965.59618.idtracker@ietfa.amsl.com>
Date: Sun, 20 Nov 2011 23:59:09 -0800
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-host-gen-id-01.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: Mon, 21 Nov 2011 07:59: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           : Prefix Assignment in DHCPv6
	Author(s)       : Sheng Jiang
                          Frank Xia
                          Behcet Sarikaya
	Filename        : draft-ietf-dhc-host-gen-id-01.txt
	Pages           : 10
	Date            : 2011-11-20

   This document describes a procedure for configuring hosts' IPv6
   address which the prefix is assigned from a DHCPv6 server through
   DHCPv6 protocol while the interface identifiers are independently
   generated by the hosts.  The method is applicable to
   Cryptographically Generated Addresses (CGA), and other IPv6 addresses
   with host-generated interface identifiers.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-host-gen-id-01.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-host-gen-id-01.txt


From narten@us.ibm.com  Mon Nov 21 12:36:19 2011
Return-Path: <narten@us.ibm.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 571BC11E8107 for <dhcwg@ietfa.amsl.com>; Mon, 21 Nov 2011 12:36:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[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 LurEJm7Xm+04 for <dhcwg@ietfa.amsl.com>; Mon, 21 Nov 2011 12:36:18 -0800 (PST)
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by ietfa.amsl.com (Postfix) with ESMTP id C53C611E80EE for <dhcwg@ietf.org>; Mon, 21 Nov 2011 12:36:18 -0800 (PST)
Received: from /spool/local by e32.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <dhcwg@ietf.org> from <narten@us.ibm.com>; Mon, 21 Nov 2011 13:36:17 -0700
Received: from d03relay02.boulder.ibm.com ([9.17.195.227]) by e32.co.us.ibm.com ([192.168.1.132]) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Mon, 21 Nov 2011 13:36:16 -0700
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id pALKa6pM091116; Mon, 21 Nov 2011 13:36:06 -0700
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id pALKa5Yt026445; Mon, 21 Nov 2011 13:36:05 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-49-158-47.mts.ibm.com [9.49.158.47]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id pALKa1sf026148 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 Nov 2011 13:36:03 -0700
Received: from cichlid.raleigh.ibm.com (cichlid.raleigh.ibm.com [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id pALKa0eO019515; Mon, 21 Nov 2011 15:36:00 -0500
Message-Id: <201111212036.pALKa0eO019515@cichlid.raleigh.ibm.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
In-reply-to: <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>
References: <CANF0JMCo8ZnXtY7DKcoeGApYKu0Enq=O-DFvSmrmkjpSUWzB9g@mail.gmail.com>, <402398CF-7F7C-4B8B-91CE-6EDE54B6C4CC@employees.org> <23BACC91-621A-4E96-ACD6-92D226F9657A@nominum.com>
Comments: In-reply-to Ted Lemon <Ted.Lemon@nominum.com> message dated "Mon, 14 Nov 2011 02:24:37 +0000."
Date: Mon, 21 Nov 2011 15:36:00 -0500
From: Thomas Narten <narten@us.ibm.com>
x-cbid: 11112120-3270-0000-0000-000001F5EAA9
Cc: MIF Mailing List <mif@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] 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: Mon, 21 Nov 2011 20:36:19 -0000

Ted Lemon <Ted.Lemon@nominum.com> writes:

> On Nov 14, 2011, at 9:59 AM, "Ole Troan" <otroan@employees.org> wrote:
> > why not just merge all the information received?
> > e.g. if you get DNS server over DHCP and RA, use all.
> > if you get addresses via SLAAC and DHCP, you use all...

> Because "just merge" is essentially equivalent to "just walk across
> the river without your feet getting wet.".  If you can write a spec
> that does this correctly, you are probably the Messiah.

Isn't this what DHC already does? I.e., you run DHCP on two
interfaces, and get conflicting information.

The existing DHCP specs are silent on this, and the DHC WG has never
been willing to specify how to handle this case.

The case of getting conflicting DNS configuration information via DHC
seems a realistic scenario to me.

How do you propose this get handled?

Are you proposing we solve it for the DHC/RA case, but not for the
DHC/DHC case?

Thomas


From Ted.Lemon@nominum.com  Mon Nov 21 13:45: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 87C9F11E8119; Mon, 21 Nov 2011 13:45:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.573
X-Spam-Level: 
X-Spam-Status: No, score=-106.573 tagged_above=-999 required=5 tests=[AWL=0.026, 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 6X8DUkiQTjOt; Mon, 21 Nov 2011 13:45:56 -0800 (PST)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id B789211E80ED; Mon, 21 Nov 2011 13:45:54 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKTsrGiYlpmWw6Jm1FRFAY2302acyTXPM/@postini.com; Mon, 21 Nov 2011 13:45:55 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 5B6671B826E; Mon, 21 Nov 2011 13:45:45 -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 3B379190052; Mon, 21 Nov 2011 13:45: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, 21 Nov 2011 13:45:42 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Thomas Narten <narten@us.ibm.com>
Thread-Topic: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Index: AQHMom9Jeyu5uv/47kCfd4auwPXOIJWsI2EA//+A3MeADLdcAIAAE2+A
Date: Mon, 21 Nov 2011 21:45:41 +0000
Message-ID: <0DF2CC29-9D10-4DCB-8B12-7216D628FAAF@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>
In-Reply-To: <201111212036.pALKa0eO019515@cichlid.raleigh.ibm.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="us-ascii"
Content-ID: <C727F556048CAF43B52EF19ECE5F6794@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] 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: Mon, 21 Nov 2011 21:45:56 -0000

On Nov 21, 2011, at 3:36 PM, Thomas Narten wrote:
> Isn't this what DHC already does? I.e., you run DHCP on two
> interfaces, and get conflicting information.

I don't know what the antecedent to "this" was intended to be.

> The existing DHCP specs are silent on this, and the DHC WG has never
> been willing to specify how to handle this case.

Right, because it's been our position that this is not a DHCP problem.

> The case of getting conflicting DNS configuration information via DHC
> seems a realistic scenario to me.

It is completely realistic.

> How do you propose this get handled?

I think the right way to handle this is the way that the MIF working group =
has proposed: treat each provisioning domain separately.   Do not try to me=
rge information you have no basis for assuming is valid across provisioning=
 domains (which is all configuration information).   You wouldn't typically=
 send an IP packet with a source address for interface 2 out of interface 2=
.   Why would you query a DNS server out of interface 2 when you learned ab=
out it through interface 1?

> Are you proposing we solve it for the DHC/RA case, but not for the
> DHC/DHC case?

I think that having two ways of configuring things is a bad idea, and hence=
 I claim that standardizing the RA DNS server option was a mistake, one whi=
ch unfortunately can't be undone at this point.   I think that if we are go=
ing to say that RAs and DHCP servers can both provide some piece of configu=
ration information, then we kind of have to treat them as separate provisio=
ning domains.   But we can't really do that, because some information is pr=
ovided only in RAs at the moment.

My main wish is just to not make the mess any worse; secondarily, I'd like =
to do what we can to make it less bad.=

From marc.blanchet@viagenie.ca  Mon Nov 21 13:58:09 2011
Return-Path: <marc.blanchet@viagenie.ca>
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 D88B721F87D3; Mon, 21 Nov 2011 13:58:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.483
X-Spam-Level: 
X-Spam-Status: No, score=-102.483 tagged_above=-999 required=5 tests=[AWL=0.116, 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 qpWC+ip-28dw; Mon, 21 Nov 2011 13:57:49 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2]) by ietfa.amsl.com (Postfix) with ESMTP id 9791A21F8593; Mon, 21 Nov 2011 13:57:49 -0800 (PST)
Received: from [IPv6:2607:fa48:6e6b:c280:15c9:6087:dafd:d077] (unknown [IPv6:2607:fa48:6e6b:c280:15c9:6087:dafd:d077]) by jazz.viagenie.ca (Postfix) with ESMTPSA id D384621F6D; Mon, 21 Nov 2011 16:57:18 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <0DF2CC29-9D10-4DCB-8B12-7216D628FAAF@nominum.com>
Date: Mon, 21 Nov 2011 16:57:18 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5A43AEC2-9EF2-4F54-8ECE-76A254DD1B39@viagenie.ca>
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>
To: ipv6@ietf.org, MIF Mailing List <mif@ietf.org>, dhc WG <dhcwg@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [dhcwg] 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: Mon, 21 Nov 2011 21:58:10 -0000

my take: the MIF problem statement draft about to be published as RFC) =
discusses the various scenarios. probably more exists. But the issue of =
receiving config info from multiple sources is not specific to dhcpv6. =
it is related to any protocol sending config info. so it is a problem of =
pppv4, pppv6, dhcpv4, dhcpv6, RA, maybe even others.  Therefore, we need =
to find the right solution for all the cases together, instead of just =
looking at one specific provisioning protocol IP address family.  In =
this context, it appears to me that the right place to discuss that is =
within MIF wg.

my 2 cents.

Marc.

Le 2011-11-21 =E0 16:45, Ted Lemon a =E9crit :

> On Nov 21, 2011, at 3:36 PM, Thomas Narten wrote:
>> Isn't this what DHC already does? I.e., you run DHCP on two
>> interfaces, and get conflicting information.
>=20
> I don't know what the antecedent to "this" was intended to be.
>=20
>> The existing DHCP specs are silent on this, and the DHC WG has never
>> been willing to specify how to handle this case.
>=20
> Right, because it's been our position that this is not a DHCP problem.
>=20
>> The case of getting conflicting DNS configuration information via DHC
>> seems a realistic scenario to me.
>=20
> It is completely realistic.
>=20
>> How do you propose this get handled?
>=20
> I think the right way to handle this is the way that the MIF working =
group has proposed: treat each provisioning domain separately.   Do not =
try to merge information you have no basis for assuming is valid across =
provisioning domains (which is all configuration information).   You =
wouldn't typically send an IP packet with a source address for interface =
2 out of interface 2.   Why would you query a DNS server out of =
interface 2 when you learned about it through interface 1?
>=20
>> Are you proposing we solve it for the DHC/RA case, but not for the
>> DHC/DHC case?
>=20
> I think that having two ways of configuring things is a bad idea, and =
hence I claim that standardizing the RA DNS server option was a mistake, =
one which unfortunately can't be undone at this point.   I think that if =
we are going to say that RAs and DHCP servers can both provide some =
piece of configuration information, then we kind of have to treat them =
as separate provisioning domains.   But we can't really do that, because =
some information is provided only in RAs at the moment.
>=20
> My main wish is just to not make the mess any worse; secondarily, I'd =
like to do what we can to make it less bad.
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From ichiroumakino@gmail.com  Tue Nov 22 05:18:40 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 4FFB921F8CA3; Tue, 22 Nov 2011 05:18:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.559
X-Spam-Level: 
X-Spam-Status: No, score=-3.559 tagged_above=-999 required=5 tests=[AWL=0.040,  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 Cjh+Xw5uZ9-H; Tue, 22 Nov 2011 05:18:39 -0800 (PST)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by ietfa.amsl.com (Postfix) with ESMTP id 2C1D821F8CA2; Tue, 22 Nov 2011 05:18:39 -0800 (PST)
Received: by wwe3 with SMTP id 3so7216977wwe.1 for <multiple recipients>; Tue, 22 Nov 2011 05:18:37 -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=vLvqvycQR/Qk+9s7/K25kYzjx+PRYb60ICw9p3eT+pk=; b=hjLk2ozLzE45FWBL/6snPxKd/lcMDxUjvnqXs/RM/8HdGtuUb7vakItOLtuDbrevqm 0VLXBuI/oB4DHIh4/7lgujJsaiwX8xulxZgf3wEJRVIGQslRR/DFV6lKoDGvYJR8PY3W 6+uDh8SbgrHtKHr1I+dqAmNDiUnqoMKXPtZpM=
Received: by 10.227.207.146 with SMTP id fy18mr8335362wbb.18.1321967916906; Tue, 22 Nov 2011 05:18:36 -0800 (PST)
Received: from ams3-vpn-dhcp4888.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id em4sm16579372wbb.20.2011.11.22.05.18.32 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 22 Nov 2011 05:18:35 -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: <0DF2CC29-9D10-4DCB-8B12-7216D628FAAF@nominum.com>
Date: Tue, 22 Nov 2011 14:18:31 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F4EFC3D8-AF56-4D90-AE08-767FC68CC468@employees.org>
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>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1084)
Cc: Thomas Narten <narten@us.ibm.com>, MIF Mailing List <mif@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] 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: Tue, 22 Nov 2011 13:18:40 -0000

>> How do you propose this get handled?
>=20
> I think the right way to handle this is the way that the MIF working =
group has proposed: treat each provisioning domain separately.   Do not =
try to merge information you have no basis for assuming is valid across =
provisioning domains (which is all configuration information). You =
wouldn't typically send an IP packet with a source address for interface =
2 out of interface 2.   Why would you query a DNS server out of =
interface 2 when you learned about it through interface 1?

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 =3D link, as detection =
of multiple provisioning domains on a single link may not be trivial in =
all corner cases.

cheers,
Ole



From Ted.Lemon@nominum.com  Tue Nov 22 07:31: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 5E0A021F8C6B; Tue, 22 Nov 2011 07:31:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.574
X-Spam-Level: 
X-Spam-Status: No, score=-106.574 tagged_above=-999 required=5 tests=[AWL=0.024, 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 XVQMgANepJNT; Tue, 22 Nov 2011 07:31:45 -0800 (PST)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id 4B28C21F8C60; Tue, 22 Nov 2011 07:31:45 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKTsvAYCxrZBBXrBtpYQP4cofz7XIKlAc7@postini.com; Tue, 22 Nov 2011 07:31:45 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 4EBE41B827D; Tue, 22 Nov 2011 07:31:44 -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 3B048190052; Tue, 22 Nov 2011 07:31:44 -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, 22 Nov 2011 07:31:44 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ole Troan <otroan@employees.org>
Thread-Topic: [dhcwg] Conflict between RA and DHCP in MIF case
Thread-Index: AQHMom9Jeyu5uv/47kCfd4auwPXOIJWsI2EA//+A3MeADLdcAIAAE2+AgAEEqoCAACU3AA==
Date: Tue, 22 Nov 2011 15:31:43 +0000
Message-ID: <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>
In-Reply-To: <F4EFC3D8-AF56-4D90-AE08-767FC68CC468@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_DF1C8CC913D0494BAB455A17AECD1CB4nominumcom_"
MIME-Version: 1.0
Cc: Thomas Narten <narten@us.ibm.com>, MIF Mailing List <mif@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] 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: Tue, 22 Nov 2011 15:31:46 -0000

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

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 =3D link, as detection of=
 multiple provisioning domains on a single link may not be trivial in all c=
orner cases.

I agree with you that right now detecting provisioning domains is not trivi=
al; indeed, in some cases it's impossible.   However, if you think provisio=
ning domain =3D=3D 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.


--_000_DF1C8CC913D0494BAB455A17AECD1CB4nominumcom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <2DE43083E24BF04E9495A21BC58F95C9@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 Nov 22, 2011, at 8:18 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; ">for
 clarification, that was not my proposal. my suggestion was to merge all in=
formation within one &quot;provisioning domain&quot;.</span></blockquote>
<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; ">unsure
 if we will end up with provisioning domain =3D link, as detection of multi=
ple provisioning domains on a single link may not be trivial in all corner =
cases.</span></blockquote>
</div>
<br>
<div>I agree with you that right now detecting provisioning domains is not =
trivial; indeed, in some cases it's impossible. &nbsp; However, if you thin=
k provisioning domain =3D=3D link, then that's a problem that needs fixing.=
 &nbsp; Indeed, that's *the* problem that needs
 fixing. &nbsp; I think we have to fix it; if we punt, we're going to pay f=
or it later.</div>
<div><br>
</div>
</body>
</html>

--_000_DF1C8CC913D0494BAB455A17AECD1CB4nominumcom_--

From internet-drafts@ietf.org  Wed Nov 30 08:14:41 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 221E721F8BA4; Wed, 30 Nov 2011 08:14:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level: 
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.003, 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 dtwibSs9AHTJ; Wed, 30 Nov 2011 08:14:40 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACFEB21F8B56; Wed, 30 Nov 2011 08:14:40 -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: <20111130161440.17091.31129.idtracker@ietfa.amsl.com>
Date: Wed, 30 Nov 2011 08:14:40 -0800
Cc: dhcwg@ietf.org
Subject: [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: Wed, 30 Nov 2011 16:14:41 -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           : DHCPv4 over IPv6 Transport
	Author(s)       : Yong Cui
                          Peng Wu
                          Jianping Wu
                          Ted Lemon
	Filename        : draft-ietf-dhc-dhcpv4-over-ipv6-00.txt
	Pages           : 9
	Date            : 2011-11-30

   Recently, there are demands arising for IPv4 address allocation under
   IPv6 environment, especially in IPv6 transition scenarios.  This
   document describes the mechanism to survive DHCPv4 over IPv6 network.
   DHCPv4 messages are transported in IPv6 packets when traversing the
   IPv6 network.  DHCPv4 protocol behavior of the client and server is
   extended to support this IPv6 transport.  For the relay case, a new
   suboption of the Relay Agent Information Option is defined to carry
   the remote IPv6 address of the clients.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv4-over-ipv6-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-dhcpv4-over-ipv6-00.txt


From akostur@incognito.com  Wed Nov 30 09:06:04 2011
Return-Path: <akostur@incognito.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 D034F21F8BDE for <dhcwg@ietfa.amsl.com>; Wed, 30 Nov 2011 09:06:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.977
X-Spam-Level: 
X-Spam-Status: No, score=-5.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 w++NDHBW1zLG for <dhcwg@ietfa.amsl.com>; Wed, 30 Nov 2011 09:06:04 -0800 (PST)
Received: from na3sys010aog103.obsmtp.com (na3sys010aog103.obsmtp.com [74.125.245.74]) by ietfa.amsl.com (Postfix) with SMTP id 8CDA721F8BB9 for <dhcwg@ietf.org>; Wed, 30 Nov 2011 09:06:03 -0800 (PST)
Received: from mail-qw0-f52.google.com ([209.85.216.52]) (using TLSv1) by na3sys010aob103.postini.com ([74.125.244.12]) with SMTP ID DSNKTtZidNy7RaTRjKoT/P9bIHTjOiF5o6Ln@postini.com; Wed, 30 Nov 2011 09:06:03 PST
Received: by mail-qw0-f52.google.com with SMTP id y1so663387qad.11 for <dhcwg@ietf.org>; Wed, 30 Nov 2011 09:05:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.65.103 with SMTP id h39mr537847qci.202.1322672756203; Wed, 30 Nov 2011 09:05:56 -0800 (PST)
Received: by 10.229.83.130 with HTTP; Wed, 30 Nov 2011 09:05:56 -0800 (PST)
In-Reply-To: <20111130161440.17091.31129.idtracker@ietfa.amsl.com>
References: <20111130161440.17091.31129.idtracker@ietfa.amsl.com>
Date: Wed, 30 Nov 2011 09:05:56 -0800
Message-ID: <CAL10_BrtWTQ8aXYYd-FX09gDLAowWfRzEf5PrGu9hoff6Ki1-A@mail.gmail.com>
From: Andre Kostur <akostur@incognito.com>
To: dhcwg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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: Wed, 30 Nov 2011 17:06:05 -0000

On Wed, Nov 30, 2011 at 08:14, <internet-drafts@ietf.org> wrote:
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories. This draft is a work item of the Dynamic Host Configuration Working =
Group of the IETF.
>
> =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : DHCPv4 over IPv6 Transport
> =A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : Yong Cui
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Peng Wu
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Jianping Wu
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Ted Lemon
> =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-ietf-dhc-dhcpv4-over-ipv6-=
00.txt
> =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 9
> =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2011-11-30

On first reading I'm concerned about the architecture in general.  By
this draft it is imposing additional requirements on any IPv4 device
that wishes to operate in this environment.   Wouldn't it be better to
place the additional behaviours on a relay agent type behaviour on the
upstream router, or the device performing the 4 to 6 translation?  I
doubt if I'm ever going to get a firmware update on my blu-ray player
to support this new behaviour, but if the agent functionality is
pushed higher up in the the network, then any and all existing IPv4
devices that are already doing DHCP will be able to continue to
operate in this environment.


--
Andre Kostur
Senior Product Design Engineer
Incognito Software Inc.
E: akostur@incognito.com

From shemant@cisco.com  Wed Nov 30 20:37:45 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 A3D4511E80AD for <dhcwg@ietfa.amsl.com>; Wed, 30 Nov 2011 20:37:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.567
X-Spam-Level: 
X-Spam-Status: No, score=-6.567 tagged_above=-999 required=5 tests=[AWL=0.031,  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 7fcnDV8aIuFu for <dhcwg@ietfa.amsl.com>; Wed, 30 Nov 2011 20:37:43 -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 BE2CA11E8090 for <dhcwg@ietf.org>; Wed, 30 Nov 2011 20:37:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=10105; q=dns/txt; s=iport; t=1322714264; x=1323923864; h=mime-version:subject:date:message-id:from:to; bh=U9dZI9kUHBKtItfc5JcrTZXinFbKdBLqgOBcJunwDVA=; b=Nz4lMAKjYtzsCBm6ZYuFx7Ve+xNfz02+fJA6k9BPkLIklDBpT9nctiWU fr405qmwMSQry2JoLo35ATluzhnGmmzGfv88gi2WLn5o8nqJFp683GscJ qMT3L9427cACbpxh4i5CH/iCvOOrnRtG7AIG8tAQnARJ+9WG6/VHDcmnq Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqkAABUE106tJV2a/2dsb2JhbABEgk2YJpAjgQWBcgEBAQQSAQkRAz4dAQgRBAEBCwYXAQdFBwEBBQUEEwgaoDWBJgGeM4gLgjJjBIgonmA
X-IronPort-AV: E=Sophos;i="4.71,276,1320624000"; d="scan'208,217";a="40208367"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-6.cisco.com with ESMTP; 01 Dec 2011 04:37:43 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pB14bh5K023868 for <dhcwg@ietf.org>; Thu, 1 Dec 2011 04:37:43 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);  Wed, 30 Nov 2011 22:37:43 -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_01CCAFE2.F708E357"
Date: Wed, 30 Nov 2011 22:37:42 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C3036CE25E@XMB-RCD-109.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [v6ops] I-D Action: draft-ietf-v6ops-6204bis-03.txt
Thread-Index: AQHMrsV2hiQDlw7m00i9I5kWpNL4D5XEs+6AgAABWQCAACDogP//e9VAgAC4WoD//5+68IAAlceAgAEmK9A=
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: <dhcwg@ietf.org>
X-OriginalArrivalTime: 01 Dec 2011 04:37:43.0156 (UTC) FILETIME=[F7311340:01CCAFE2]
Subject: [dhcwg] FW: [v6ops] I-D Action: draft-ietf-v6ops-6204bis-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: Thu, 01 Dec 2011 04:37:45 -0000

This is a multi-part message in MIME format.

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

DHC WG folks,

=20

Could you please see if any pitfalls exits for the 2 Errata in question
below?  On the IETF IPv6 CE router design team we are discussing to
incorporate the Errata for the IPv6 CE router if the DHC WG reviews the
errata thoroughly and does not find any issues.

=20

RFC3315 errata 2471 and RFC3633 errata 2469 exist.

=20

Thanks,

=20

Hemant

=20

From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
Sent: Tuesday, November 29, 2011 9:56 PM
To: Hemant Singh (shemant)
Cc: Lorenzo Colitti; <cpe-router@external.cisco.com>; jouni korhonen
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-6204bis-03.txt

=20

On Nov 29, 2011, at 9:04 PM, Hemant Singh (shemant) wrote:

	Please suggest what specific text we could go with.   Or
rfc6204bis could just stay with its original WPD-7 bullet that anyway
address most of the errata in question.

=20

I think the right thing to do is have a discussion on the DHCwg mailing
list about updating 3315 and 3361 to address these issues.   The
proposed change does "fix" the problem; my concern is that it hasn't
been thought through in detail, and as we experienced at the last IETF,
something that sounds like a good idea at first reading doesn't
necessary stand up when it's subject to scrutiny.

=20


------_=_NextPart_001_01CCAFE2.F708E357
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=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: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.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.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
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;
	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 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'>DHC WG folks,<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'>Could you please see if any pitfalls exits for the 2 Errata in =
question below?&nbsp; On the IETF IPv6 CE router design team we are =
discussing to incorporate the Errata for the IPv6 CE router if the DHC =
WG reviews the errata thoroughly and does not find any =
issues.<o:p></o:p></span></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>RFC3315 errata 2471 and RFC3633 errata 2469 =
exist.<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'>Thanks,<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"'> =
Ted Lemon [mailto:Ted.Lemon@nominum.com] <br><b>Sent:</b> Tuesday, =
November 29, 2011 9:56 PM<br><b>To:</b> Hemant Singh =
(shemant)<br><b>Cc:</b> Lorenzo Colitti; =
&lt;cpe-router@external.cisco.com&gt;; jouni korhonen<br><b>Subject:</b> =
Re: [v6ops] I-D Action: =
draft-ietf-v6ops-6204bis-03.txt<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On =
Nov 29, 2011, at 9:04 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:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D=
'>Please suggest what specific text we could go with.&nbsp; &nbsp;Or =
rfc6204bis could just stay with its original WPD-7 bullet that anyway =
address most of the errata in =
question.</span></span><o:p></o:p></p></blockquote></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>I think =
the right thing to do is have a discussion on the DHCwg mailing list =
about updating 3315 and 3361 to address these issues. &nbsp; The =
proposed change does &quot;fix&quot; the problem; my concern is that it =
hasn't been thought through in detail, and as we experienced at the last =
IETF, something that sounds like a good idea at first reading doesn't =
necessary stand up when it's subject to =
scrutiny.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------_=_NextPart_001_01CCAFE2.F708E357--

From shemant@cisco.com  Wed Nov 30 20:39:11 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 0636C11E80AD for <dhcwg@ietfa.amsl.com>; Wed, 30 Nov 2011 20:39:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.568
X-Spam-Level: 
X-Spam-Status: No, score=-6.568 tagged_above=-999 required=5 tests=[AWL=0.030,  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 LDP++jrWHUDO for <dhcwg@ietfa.amsl.com>; Wed, 30 Nov 2011 20:39:10 -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 4137711E8090 for <dhcwg@ietf.org>; Wed, 30 Nov 2011 20:39:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=12186; q=dns/txt; s=iport; t=1322714350; x=1323923950; h=mime-version:subject:date:message-id:in-reply-to: references:from:to; bh=buKzP2e7GrHDVLtBbHwubXsONQA9AZfjZJ6zrDnkXyY=; b=ItTPuILv09reRHJlUY7H6I7PORCHbAdIVudN0X5NAomfendOUlOkWOO8 fa7/SjixawrXyNR9qmxavFNwSR8kvvk1XiHzf01xRjq53Iats3Yd0H+Zx bsW4y/r+RSlVABwz18NF80bq6NYcO8dxiL1/tL7vhnx36Y7zvDrUW8rDh g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqkAAJ8E106tJXG8/2dsb2JhbABEgk2YJpAjgQWBcgEBAQQSAQkRAz4bAgEIEQQBAQsGFwEGAUUIAQgCBAESCBqhXAGeM4o9YwSIKJ5g
X-IronPort-AV: E=Sophos;i="4.71,276,1320624000"; d="scan'208,217";a="40226622"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-7.cisco.com with ESMTP; 01 Dec 2011 04:39:10 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core2-1.cisco.com (8.14.3/8.14.3) with ESMTP id pB14d9iJ010435 for <dhcwg@ietf.org>; Thu, 1 Dec 2011 04:39:09 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);  Wed, 30 Nov 2011 22:39:09 -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_01CCAFE3.2A90D760"
Date: Wed, 30 Nov 2011 22:39:08 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C3036CE25F@XMB-RCD-109.cisco.com>
In-Reply-To: <5B6B2B64C9FE2A489045EEEADDAFF2C3036CE25E@XMB-RCD-109.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] FW: [v6ops] I-D Action: draft-ietf-v6ops-6204bis-03.txt
Thread-Index: AQHMrsV2hiQDlw7m00i9I5kWpNL4D5XEs+6AgAABWQCAACDogP//e9VAgAC4WoD//5+68IAAlceAgAEmK9CAAAJ8IA==
References: <5B6B2B64C9FE2A489045EEEADDAFF2C3036CE25E@XMB-RCD-109.cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 01 Dec 2011 04:39:09.0641 (UTC) FILETIME=[2ABDA390:01CCAFE3]
Subject: Re: [dhcwg] FW: [v6ops] I-D Action: draft-ietf-v6ops-6204bis-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: Thu, 01 Dec 2011 04:39:11 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CCAFE3.2A90D760
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

s/exits/exist.

=20

Sorry for the typo.

=20

Hemant

=20

From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Hemant Singh (shemant)
Sent: Wednesday, November 30, 2011 11:38 PM
To: dhcwg@ietf.org
Subject: [dhcwg] FW: [v6ops] I-D Action: draft-ietf-v6ops-6204bis-03.txt

=20

DHC WG folks,

=20

Could you please see if any pitfalls exist for the 2 Errata in question
below?  On the IETF IPv6 CE router design team we are discussing to
incorporate the Errata for the IPv6 CE router if the DHC WG reviews the
errata thoroughly and does not find any issues.

=20

RFC3315 errata 2471 and RFC3633 errata 2469 exist.

=20

Thanks,

=20

Hemant

=20

From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
Sent: Tuesday, November 29, 2011 9:56 PM
To: Hemant Singh (shemant)
Cc: Lorenzo Colitti; <cpe-router@external.cisco.com>; jouni korhonen
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-6204bis-03.txt

=20

On Nov 29, 2011, at 9:04 PM, Hemant Singh (shemant) wrote:

	Please suggest what specific text we could go with.   Or
rfc6204bis could just stay with its original WPD-7 bullet that anyway
address most of the errata in question.

=20

I think the right thing to do is have a discussion on the DHCwg mailing
list about updating 3315 and 3361 to address these issues.   The
proposed change does "fix" the problem; my concern is that it hasn't
been thought through in detail, and as we experienced at the last IETF,
something that sounds like a good idea at first reading doesn't
necessary stand up when it's subject to scrutiny.

=20


------_=_NextPart_001_01CCAFE3.2A90D760
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=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: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.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;}
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 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'>s/exits/exist.<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'>Sorry for the typo.<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"'> =
dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] <b>On Behalf Of =
</b>Hemant Singh (shemant)<br><b>Sent:</b> Wednesday, November 30, 2011 =
11:38 PM<br><b>To:</b> dhcwg@ietf.org<br><b>Subject:</b> [dhcwg] FW: =
[v6ops] I-D Action: =
draft-ietf-v6ops-6204bis-03.txt<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'>DHC WG folks,<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'>Could you please see if any pitfalls </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:red'>e=
xist</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'> for the 2 Errata in question below?&nbsp; On the IETF IPv6 CE router =
design team we are discussing to incorporate the Errata for the IPv6 CE =
router if the DHC WG reviews the errata thoroughly and does not find any =
issues.<o:p></o:p></span></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>RFC3315 errata 2471 and RFC3633 errata 2469 =
exist.<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'>Thanks,<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"'> =
Ted Lemon [mailto:Ted.Lemon@nominum.com] <br><b>Sent:</b> Tuesday, =
November 29, 2011 9:56 PM<br><b>To:</b> Hemant Singh =
(shemant)<br><b>Cc:</b> Lorenzo Colitti; =
&lt;cpe-router@external.cisco.com&gt;; jouni korhonen<br><b>Subject:</b> =
Re: [v6ops] I-D Action: =
draft-ietf-v6ops-6204bis-03.txt<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal>On =
Nov 29, 2011, at 9:04 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:9.0pt;font-family:"Calibri","sans-serif";color:#1F497D=
'>Please suggest what specific text we could go with.&nbsp; &nbsp;Or =
rfc6204bis could just stay with its original WPD-7 bullet that anyway =
address most of the errata in =
question.</span></span><o:p></o:p></p></blockquote></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>I think =
the right thing to do is have a discussion on the DHCwg mailing list =
about updating 3315 and 3361 to address these issues. &nbsp; The =
proposed change does &quot;fix&quot; the problem; my concern is that it =
hasn't been thought through in detail, and as we experienced at the last =
IETF, something that sounds like a good idea at first reading doesn't =
necessary stand up when it's subject to =
scrutiny.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>
------_=_NextPart_001_01CCAFE3.2A90D760--

From Ted.Lemon@nominum.com  Wed Nov 30 21:16:52 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 4E71311E80BC for <dhcwg@ietfa.amsl.com>; Wed, 30 Nov 2011 21:16:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.296
X-Spam-Level: 
X-Spam-Status: No, score=-106.296 tagged_above=-999 required=5 tests=[AWL=0.302, 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 VvSU74BfU8N4 for <dhcwg@ietfa.amsl.com>; Wed, 30 Nov 2011 21:16:51 -0800 (PST)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 7C16F11E80B6 for <dhcwg@ietf.org>; Wed, 30 Nov 2011 21:16:51 -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 DSNKTtcNwpWsU23yWv2wnUJVtw/uPlxSkrfl@postini.com; Wed, 30 Nov 2011 21:16:51 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 0F1001B8269 for <dhcwg@ietf.org>; Wed, 30 Nov 2011 21:16:50 -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 226A5190052; Wed, 30 Nov 2011 21:16: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; Wed, 30 Nov 2011 21:16:47 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Andre Kostur <akostur@incognito.com>
Thread-Topic: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-over-ipv6-00.txt
Thread-Index: AQHMr3steaJs1mf7hEKv2+0yNFE8VpXGK8sAgADMMYA=
Date: Thu, 1 Dec 2011 05:16:46 +0000
Message-ID: <0DAAE1C6-6E44-4939-962A-E4AD9E611380@nominum.com>
References: <20111130161440.17091.31129.idtracker@ietfa.amsl.com> <CAL10_BrtWTQ8aXYYd-FX09gDLAowWfRzEf5PrGu9hoff6Ki1-A@mail.gmail.com>
In-Reply-To: <CAL10_BrtWTQ8aXYYd-FX09gDLAowWfRzEf5PrGu9hoff6Ki1-A@mail.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_0DAAE1C66E444939962AE4AD9E611380nominumcom_"
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 05:16:52 -0000

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

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 on=
e that the authors of the draft have in mind; I agree with you that it's un=
likely 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 stateless=
 4over6 tunnel, so presumably this isn't the only change that would be requ=
ired on the device.

The intended use as I understand it is in a situation where we have a gener=
ally 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 loca=
tion where they might be needed doesn't make sense.   Instead, you put this=
 technology on those nodes that need it, and those nodes are expected to be=
 few, and far between.

Peng Wu could probably explain the intention here better than I can.


--_000_0DAAE1C66E444939962AE4AD9E611380nominumcom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <706EBA6958E7E145A386BD8ABC51F17B@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 Nov 30, 2011, at 12:05 PM, Andre Kostur 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; ">On
 first reading I'm concerned about the architecture in general.<span class=
=3D"Apple-converted-space">&nbsp;</span></span></blockquote>
</div>
<br>
<div>Thanks for reading it. &nbsp; I don't think the use case you're descri=
bing is one that the authors of the draft have in mind; I agree with you th=
at it's unlikely that this use case would work. &nbsp; However, the intende=
d use for this technique is in a device that
 already understands how to set up a stateless 4over6 tunnel, so presumably=
 this isn't the only change that would be required on the device.</div>
<div><br>
</div>
<div>The intended use as I understand it is in a situation where we have a =
generally working IPv6 network, but there are a few remaining applications =
that need IPv4 addresses. &nbsp; Because these applications are sparsely di=
stributed through the network, setting
 up infrastructure to support them in each location where they might be nee=
ded doesn't make sense. &nbsp; Instead, you put this technology on those no=
des that need it, and those nodes are expected to be few, and far between.<=
/div>
<div><br>
</div>
<div>Peng Wu could probably explain the intention here better than I can.</=
div>
<div><br>
</div>
</body>
</html>

--_000_0DAAE1C66E444939962AE4AD9E611380nominumcom_--

From peng-wu@foxmail.com  Wed Nov 30 22:39:43 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 EB2061F0C60 for <dhcwg@ietfa.amsl.com>; Wed, 30 Nov 2011 22:39:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.609
X-Spam-Level: **
X-Spam-Status: No, score=2.609 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_DSN=1.495, 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 Lei2n+jpf3DU for <dhcwg@ietfa.amsl.com>; Wed, 30 Nov 2011 22:39:43 -0800 (PST)
Received: from smtpbg52.qq.com (smtpbg52.qq.com [64.71.138.43]) by ietfa.amsl.com (Postfix) with SMTP id 451331F0C5D for <dhcwg@ietf.org>; Wed, 30 Nov 2011 22:39:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qq.com; s=s0907; t=1322721563; bh=pq6v73iAJOUe5BvO78q1DFGrkSNXnH5mt8zLNUm224U=; h=X-QQ-mid:Received:X-QQ-SSF:Date:From:To:Cc:Reply-To:Subject: References:X-Priority:X-GUID:X-Mailer:Mime-Version:Message-ID: Content-Type:Content-Transfer-Encoding; b=YLvUgNB45La7kv9FPGUlCOCQMP5Be3fkdfPiWRrI856l3dFx9DNDbqqZH5MCN+2y1 Zo09ke0sw6NbRkKzbUg2wrC/yDSVPL43YTJateLlDLwpX5bwDK1fHwVxc43lqG8
X-QQ-mid: esmtp1t1322721559t692t21312
Received: from weapon-PC (unknown [166.111.68.231]) by esmtp4.qq.com (ESMTP) with  id ; Thu, 01 Dec 2011 14:39:19 +0800 (CST)
X-QQ-SSF: 00000000000000F0FxF00F000000000
Date: Thu, 1 Dec 2011 14:39:15 +0800
From: peng-wu <peng-wu@foxmail.com>
To: "Ted Lemon" <Ted.Lemon@nominum.com>,  "Andre Kostur" <akostur@incognito.com>
References: <20111130161440.17091.31129.idtracker@ietfa.amsl.com><CAL10_BrtWTQ8aXYYd-FX09gDLAowWfRzEf5PrGu9hoff6Ki1-A@mail.gmail.com>, <0DAAE1C6-6E44-4939-962A-E4AD9E611380@nominum.com>
X-Priority: 3
X-GUID: 08745557-9B2D-4889-853B-36680C3DA57B
X-Mailer: Foxmail 7.0.1.81[cn]
Mime-Version: 1.0
Message-ID: <20111201143915185454109@foxmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: base64
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
Reply-To: peng-wu <peng-wu@foxmail.com>
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 06:39:44 -0000

SGkgQW5kcmUsDQoNClRoYW5rcyBmb3IgeW91ciByZXZpZXcgaW4gc3VjaCBhIHNob3J0IHRpbWUg
OikNCkFzIFRlZCBoYXMgZXhwbGFpbmVkLCB0aGUgdXNlciBjYXNlIHdlIGFscmVhZHkgaGF2ZSBp
cyBIdWIgJiBTcG9rZQ0KSVB2NC1vdmVyLUlQdjYsIHdoZXJlIGVuZCB1c2VycyBzcGFyc2VseSBk
aXN0cmlidXRlZCBpbiB0aGUgSVB2NiANCm5ldHdvcmsgaGFzIElQdjQgY29tbXVuaWNhdGlvbiBk
ZW1hbmQsIHNvIHRoZXkgYnVpbGQgSVB2NC1pbi1JUHY2DQogdHVubmVscyB3aXRoIGEgcmVtb3Rl
IHJvdXRlciB3aGljaCBpcyBjb25uZWN0ZWQgdG8gSVB2NC4gRm9yIHRoaXMNCiJ0dW5uZWxlZCIg
SVB2NCBhY2Nlc3MsIGVuZCB1c2VycyBuZWVkIElQdjQgYWRkcmVzcyBwcm92aXNpb25lZA0KIGZy
b20gdGhlIHJlbW90ZSByb3V0ZXIuIFNvIHRoZSBJUHY0IGRldmljZXMgdGhhdCB3aXNoZXMgdG8g
b3BlcmF0b3IgDQppbiB0aGlzIGVudmlyb25tZW50IG5lZWQgdG8gc3VwcG9ydCBJUHY0LWluLUlQ
djYgdHVubmVsIGJlc2lkZXMgdGhlDQpESENQIGV4dGVuc2lvbiwgd2hpY2ggbWVhbnMgY2hhbmdl
cyBvbiB0aGUgZGV2aWNlIGlzIGFscmVhZHkgDQpuZWVkZWQgYW55d2F5Lg0KRGV0YWlscyBvbiBz
Y2VuYXJpb3MgJiB0dW5uZWwgbWVjaGFuaXNtcyBjYW4gYmUgZm91bmQgaW46IA0KaHR0cDovL3Rv
b2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1zb2Z0d2lyZS1wdWJsaWMtNG92ZXI2LTAwDQpo
dHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1jdWktc29mdHdpcmUtYjQtdHJhbnNsYXRl
ZC1kcy1saXRlLTA0DQoNCg0KQWJvdXQgdGhlIHN1Z2dlc3Rpb24gdG8gcGxhY2UgdGhlIGFkZGl0
aW9uYWwgYmVoYXZpb3VycyBvbiB0aGUNCnVwc3RyZWFtIHJvdXRlcjogd2UgYWN0dWFsbHkgaGF2
ZSBtZWNoYW5pc20gZm9yIHRoaXMgY2FzZSwgc3VjaA0KYXMgY29uZmlndXJlZCB0dW5uZWwgJiBS
RkM1NTY1LiBCdXQgdGhhdCdzIGFub3RoZXIgc2VjYW5yaW8uIFRoZSANCmNyaXRpY2FsIGRpZmZl
cmVuY2UgaXMgdGhhdCwgdGhlIElTUHMgZG9uJ3Qgd2FudCB0byBwcm92aXNvbiBuYXRpdmUgSVB2
NA0KaW4gdGhlIGxhc3QgaG9wIG9mIHRoZWlyIElQdjYgbmV0d29yayBhbnltb3JlLiAgVGhleSB3
YW50IGdvIHdpdGgNCm9ubHkgSVB2Ni4NCg0KQXMgdG8gcGVyZm9ybWluZyB0aGUgNCB0byA2IHRy
YW5zbGF0aW9uLCB0aGF0J3MgYSB0b3RhbGx5IGRpZmZlcmVudCBzdG9yeS4NCkZvciBleGFtcGxl
LCB0aGUgZmlyc3QgdGhpbmcgY29taW5nIHRvIG15IG1pbmQgaXMgdGhhdCwgd2l0aCA0IHRvIDYg
DQp0cmFuc2xhdGlvbiB0aGUgcmVtb3RlIGVuZCBvZiB0aGUgY29tbXVuaWNhdGlvbiB3b3VsZCBi
ZSBJUHY2LCB3aGlsZQ0Kd2l0aCA0b3ZlcjYgdHVubmVsIHRoZSByZW1vdGUgZW5kIHdvdWxkIGxp
ZSBpbiBJUHY0LiBJIGJlbGlldmUgdGhlIA0KU29mdHdpcmUgYW5kIEJlaGF2ZSBXRyBoYXZlIGFn
cmVlZCB0aGF0IHR1bm5lbGluZyBhbmQgdHJhbnNsYXRpb24gDQpoYXZlIHJlc3BlY3RpdmUgYXBw
bGljYXRpb24gc2NlbmFyaW9zLiBBY3R1YWxseSBpbiB0aGlzIGNhc2UsIG5ldHdvcmstc2lkZSAN
CjQgdG8gNiB0cmFuc2xhdGlvbiAoTkFULVBUKSB3YXMgb2Jzb2xldGVkIGZvciBxdWl0ZSBhIGxv
dCBpc3N1ZXMgd2hpbGUNCmhvc3Qtc2lkZSA0IHRvIDYgdHJhbnNsYXRpb24gd291bGQgYnJpbmcg
bXVjaCBtb3JlIGNoYW5nZXMgdG8gdGhlIE9TDQp0aGFuIHR1bm5lbC4gU28gdHVubmVsIHdvdWxk
IGFjdHVhbGx5IGJlIGEgcmVhc29uYWJsZSBjaG9pY2UgaGVyZS4uLg0KDQpCYWNrIHRvIHRoZSBi
bHUtcmF5IHBsYXllciBleGFtcGxlIHlvdSByYWlzZWQsIEkgZ3Vlc3MgdXN1YWxseSBzdWNoIGEN
CmRldmljZSB3b3VsZCBsb2NhdGUgYmVoaW5kIGEgaG9tZSBnYXRld2F5L0NQRSByYXRoZXIgdGhh
biBjb25uZWN0DQp0byB0aGUgSVNQIG5ldHdvcmsgZGlyZWN0bHkuIFRoZW4geW91ciBnYXRld2F5
L0NQRSB3b3VsZCBpbXBsZW1lbnQNCnRoZSBDUkEgZnVudGlvbnMgYW5kIGludGVyYWN0IHdpdGgg
dGhlIHJlbW90ZSBESENQIHNlcnZlciwgd2hpbGUNCnlvdXIgcGxheWVyIG9ubHkgaW50ZXJhY3Rz
IHdpdGggdGhlIGdhdHdheS9DUEUgdG8gZ2V0IGEgcHJpdmF0ZSBJUHY0IA0KYWRkcmVzcy4gSnVz
dCBsaWtlIHdoYXQgaGFwcGVucyB0b2RheS4gDQoNCkhvcGUgdGhpcyBoZWxwcyB0byB1bmRlcnN0
YW5kIHRoZSBpbnRlbnNpb24uDQpCVFcsIHdlJ3JlIHRyeWluZyB0byBmaW5kIGEgd2F5IG9mIGlt
cGxlbWVudGluZyBDUkEgc28gdGhhdCBpdCBjb3VsZA0KY29vcGVyYXRlIHdpdGggdGhlIGV4aXN0
aW5nIERIQ1AgY2xpZW50IGltcGxlbWVudGF0aW9uLiBUaGVuIHdlIA0KZG9uJ3QgaGF2ZSB0byBt
b2RpZnkgdGhlIGNsaWVudCBzbyB0aGVyZSdsbCBiZSBsZXNzIGNoYW5nZXMuDQotLS0tLS0tLS0t
LS0tLQ0KcGVuZy13dQ0KPk9uIE5vdiAzMCwgMjAxMSwgYXQgMTI6MDUgUE0sIEFuZHJlIEtvc3R1
ciB3cm90ZToNCj5PbiBmaXJzdCByZWFkaW5nIEknbSBjb25jZXJuZWQgYWJvdXQgdGhlIGFyY2hp
dGVjdHVyZSBpbiBnZW5lcmFsLg0KPg0KPlRoYW5rcyBmb3IgcmVhZGluZyBpdC4gICBJIGRvbid0
IHRoaW5rIHRoZSB1c2UgY2FzZSB5b3UncmUgZGVzY3JpYmluZyBpcyBvbmUgdGhhdCB0aGUgYXV0
aG9ycyBvZiB0aGUgZHJhZnQgaGF2ZSBpbiBtaW5kOyBJIGFncmVlIHdpdGggeW91IHRoYXQgaXQn
cyB1bmxpa2VseSB0aGF0IHRoaXMgdXNlIGNhc2Ugd291bGQgd29yay4gICBIb3dldmVyLCB0aGUg
aW50ZW5kZWQgdXNlIGZvciB0aGlzIHRlY2huaXF1ZSBpcyBpbiBhIGRldmljZSB0aGF0IGFscmVh
ZHkgdW5kZXJzdGFuZHMgaG93IHRvIHNldCB1cCBhIHN0YXRlbGVzcyA0b3ZlcjYgdHVubmVsLCBz
byBwcmVzdW1hYmx5IHRoaXMgaXNuJ3QgdGhlIG9ubHkgY2hhbmdlIHRoYXQgd291bGQgYmUgcmVx
dWlyZWQgb24gdGhlIGRldmljZS4NCj4NCj5UaGUgaW50ZW5kZWQgdXNlIGFzIEkgdW5kZXJzdGFu
ZCBpdCBpcyBpbiBhIHNpdHVhdGlvbiB3aGVyZSB3ZSBoYXZlIGEgZ2VuZXJhbGx5IHdvcmtpbmcg
SVB2NiBuZXR3b3JrLCBidXQgdGhlcmUgYXJlIGEgZmV3IHJlbWFpbmluZyBhcHBsaWNhdGlvbnMg
dGhhdCBuZWVkIElQdjQgYWRkcmVzc2VzLiAgIEJlY2F1c2UgdGhlc2UgYXBwbGljYXRpb25zIGFy
ZSBzcGFyc2VseSBkaXN0cmlidXRlZCB0aHJvdWdoIHRoZSBuZXR3b3JrLCBzZXR0aW5nIHVwIGlu
ZnJhc3RydWN0dXJlIHRvIHN1cHBvcnQgdGhlbSBpbiBlYWNoIGxvY2F0aW9uIHdoZXJlIHRoZXkg
bWlnaHQgYmUgbmVlZGVkIGRvZXNuJ3QgbWFrZSBzZW5zZS4gICBJbnN0ZWFkLCB5b3UgcHV0IHRo
aXMgdGVjaG5vbG9neSBvbiB0aG9zZSBub2RlcyB0aGF0IG5lZWQgaXQsIGFuZCB0aG9zZSBub2Rl
cyBhcmUgZXhwZWN0ZWQgdG8gYmUgZmV3LCBhbmQgZmFyIGJldHdlZW4uDQo+DQo+UGVuZyBXdSBj
b3VsZCBwcm9iYWJseSBleHBsYWluIHRoZSBpbnRlbnRpb24gaGVyZSBiZXR0ZXIgdGhhbiBJIGNh
bi4NCj4NCj4=

