
From ogud@ogud.com  Sun Dec  1 12:53:12 2013
Return-Path: <ogud@ogud.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C22391AE134 for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 12:53:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FzuK9m1R25Nr for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 12:53:10 -0800 (PST)
Received: from smtp82.ord1c.emailsrvr.com (smtp82.ord1c.emailsrvr.com [108.166.43.82]) by ietfa.amsl.com (Postfix) with ESMTP id 5F4361AE10E for <dhcwg@ietf.org>; Sun,  1 Dec 2013 12:53:10 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 4E179500B1 for <dhcwg@ietf.org>; Sun,  1 Dec 2013 15:53:08 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 1895D50099 for <dhcwg@ietf.org>; Sun,  1 Dec 2013 15:53:08 -0500 (EST)
From: Olafur Gudmundsson <ogud@ogud.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9D48D309-64DE-49CB-9E7C-220A0996C352"
Date: Sun, 1 Dec 2013 15:53:07 -0500
References: <20131201204227.7978.2067.idtracker@ietfa.amsl.com>
To: dhcwg@ietf.org
Message-Id: <83842BD2-0261-472F-9CA1-AFBFB47EAD91@ogud.com>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Subject: [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 01 Dec 2013 20:53:13 -0000

--Apple-Mail=_9D48D309-64DE-49CB-9E7C-220A0996C352
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


Hi,=20

I wrote up this short document in order to address a problem seen in =
certain devices
that do not have good time at startup. The document  proposes a DHCv4 =
option and
DHCPv6 option to supply current time to a device. (there is also a =
proposed ND option
for the same thing).=20

I looked into using option 152 from Bulk Query but that is only 32 bit =
long, and=20
it seems cleaner to just get a 64bit time_t option into DHC

Comments please=20

	Olafur


Begin forwarded message:

> From: internet-drafts@ietf.org
> Subject: New Version Notification for =
draft-ogud-dhc-udp-time-option-01.txt
> Date: December 1, 2013 3:42:27 PM EST
> To: Olafur Gudmundsson <ogud@ogud.com>
>=20
>=20
> A new version of I-D, draft-ogud-dhc-udp-time-option-01.txt
> has been successfully submitted by Olafur Gudmundsson and posted to =
the
> IETF repository.
>=20
> Filename:	 draft-ogud-dhc-udp-time-option
> Revision:	 01
> Title:		 Providing Time over DHCP and ND for devices w/o =
reliable clock upon boot
> Creation date:	 2013-12-01
> Group:		 Individual Submission
> Number of pages: 7
> URL:             =
http://www.ietf.org/internet-drafts/draft-ogud-dhc-udp-time-option-01.txt
> Status:          =
http://datatracker.ietf.org/doc/draft-ogud-dhc-udp-time-option
> Htmlized:        =
http://tools.ietf.org/html/draft-ogud-dhc-udp-time-option-01
> Diff:            =
http://www.ietf.org/rfcdiff?url2=3Ddraft-ogud-dhc-udp-time-option-01
>=20
> Abstract:
>   Many small inexpensive computing devices like home routers, Rasberry
>   Pi etc. do not have a battery to allow clock chip to keep track of
>   time, thus the systems have no idea what the current time is upon
>   boot.  Number of modern services take Time Synchronization for
>   granted, but operating systems do not allow the start of these
>   services to be deferred until after accurate clock has been
>   confirmed.
>=20
>   NTP provides accurate fine grain clock synchronization but in order
>   for NTP to succeed DNS needs to work.  DNSSEC resolvers will fail if
>   system clock is off by more than little bit.  This draft proposes a
>   mechanism to offer "reasonable" current time to devices upon boot =
via
>   DHCP, DHCPv6 and ND.
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> The IETF Secretariat
>=20


--Apple-Mail=_9D48D309-64DE-49CB-9E7C-220A0996C352
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<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-line-break: after-white-space; =
"><div><br></div>Hi,&nbsp;<div><br><div>I wrote up this short document =
in order to address a problem seen in certain devices</div><div>that do =
not have good time at startup. The document &nbsp;proposes a DHCv4 =
option and</div><div>DHCPv6 option to supply current time to a device. =
(there is also a proposed ND option</div><div>for the same =
thing).&nbsp;</div><div><br></div><div>I looked into using option 152 =
from Bulk Query but that is only 32 bit long, and&nbsp;</div><div>it =
seems cleaner to just get a 64bit time_t option into =
DHC</div><div><br></div><div>Comments =
please&nbsp;</div><div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	=
</span>Olafur</div><div><br></div><div><div><br><div>Begin forwarded =
message:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1.0);"><b>From: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;"><a =
href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a><br><=
/span></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1.0);"><b>Subject: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;"><b>New Version Notification for =
draft-ogud-dhc-udp-time-option-01.txt</b><br></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1.0);"><b>Date: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;">December 1, 2013 =
3:42:27 PM EST<br></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1.0);"><b>To: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;">Olafur Gudmundsson &lt;<a =
href=3D"mailto:ogud@ogud.com">ogud@ogud.com</a>&gt;<br></span></div><br><d=
iv><br>A new version of I-D, =
draft-ogud-dhc-udp-time-option-01.txt<br>has been successfully submitted =
by Olafur Gudmundsson and posted to the<br>IETF =
repository.<br><br>Filename:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span> =
draft-ogud-dhc-udp-time-option<br>Revision:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span> 01<br>Title:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span> =
Providing Time over DHCP and ND for devices w/o reliable clock upon =
boot<br>Creation date:<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span> 2013-12-01<br>Group:<span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span> =
Individual Submission<br>Number of pages: 7<br>URL: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a=
 =
href=3D"http://www.ietf.org/internet-drafts/draft-ogud-dhc-udp-time-option=
-01.txt">http://www.ietf.org/internet-drafts/draft-ogud-dhc-udp-time-optio=
n-01.txt</a><br>Status: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://datatracker.ietf.org/doc/draft-ogud-dhc-udp-time-option">ht=
tp://datatracker.ietf.org/doc/draft-ogud-dhc-udp-time-option</a><br>Htmliz=
ed: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://tools.ietf.org/html/draft-ogud-dhc-udp-time-option-01">http=
://tools.ietf.org/html/draft-ogud-dhc-udp-time-option-01</a><br>Diff: =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a =
href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ogud-dhc-udp-time-option-=
01">http://www.ietf.org/rfcdiff?url2=3Ddraft-ogud-dhc-udp-time-option-01</=
a><br><br>Abstract:<br> &nbsp;&nbsp;Many small inexpensive computing =
devices like home routers, Rasberry<br> &nbsp;&nbsp;Pi etc. do not have =
a battery to allow clock chip to keep track of<br> &nbsp;&nbsp;time, =
thus the systems have no idea what the current time is upon<br> =
&nbsp;&nbsp;boot. &nbsp;Number of modern services take Time =
Synchronization for<br> &nbsp;&nbsp;granted, but operating systems do =
not allow the start of these<br> &nbsp;&nbsp;services to be deferred =
until after accurate clock has been<br> &nbsp;&nbsp;confirmed.<br><br> =
&nbsp;&nbsp;NTP provides accurate fine grain clock synchronization but =
in order<br> &nbsp;&nbsp;for NTP to succeed DNS needs to work. =
&nbsp;DNSSEC resolvers will fail if<br> &nbsp;&nbsp;system clock is off =
by more than little bit. &nbsp;This draft proposes a<br> =
&nbsp;&nbsp;mechanism to offer "reasonable" current time to devices upon =
boot via<br> &nbsp;&nbsp;DHCP, DHCPv6 and ND.<br><br><br><br><br>Please =
note that it may take a couple of minutes from the time of =
submission<br>until the htmlized version and diff are available at <a =
href=3D"http://tools.ietf.org">tools.ietf.org</a>.<br><br>The IETF =
Secretariat<br><br></div></blockquote></div><br></div></div></body></html>=

--Apple-Mail=_9D48D309-64DE-49CB-9E7C-220A0996C352--

From Ted.Lemon@nominum.com  Sun Dec  1 13:18:15 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA0FE1AE16D for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 13:18:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZwCuQ1Lc55s6 for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 13:18:13 -0800 (PST)
Received: from exprod7og128.obsmtp.com (exprod7og128.obsmtp.com [64.18.2.121]) by ietfa.amsl.com (Postfix) with ESMTP id 980AC1ADF69 for <dhcwg@ietf.org>; Sun,  1 Dec 2013 13:18:13 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob128.postini.com ([64.18.6.12]) with SMTP ID DSNKUpunk43d23VGSAidywBzDkffFOPPVdYS@postini.com; Sun, 01 Dec 2013 13:18: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 7C09F1B8244 for <dhcwg@ietf.org>; Sun,  1 Dec 2013 13:18:11 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 58A94190043; Sun,  1 Dec 2013 13:18:11 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sun, 1 Dec 2013 13:18:11 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <83842BD2-0261-472F-9CA1-AFBFB47EAD91@ogud.com>
Date: Sun, 1 Dec 2013 16:18:09 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <C0A2F49F-7695-47E9-8AB0-7F94116437F9@nominum.com>
References: <20131201204227.7978.2067.idtracker@ietfa.amsl.com> <83842BD2-0261-472F-9CA1-AFBFB47EAD91@ogud.com>
To: Olafur Gudmundsson <ogud@ogud.com>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 01 Dec 2013 21:18:15 -0000

On Dec 1, 2013, at 3:53 PM, Olafur Gudmundsson <ogud@ogud.com> wrote:
> I wrote up this short document in order to address a problem seen in =
certain devices
> that do not have good time at startup. The document  proposes a DHCv4 =
option and
> DHCPv6 option to supply current time to a device. (there is also a =
proposed ND option
> for the same thing).=20
>=20
> I looked into using option 152 from Bulk Query but that is only 32 bit =
long, and=20
> it seems cleaner to just get a 64bit time_t option into DHC

I think it's worth thinking about the threat model this addresses, and =
the threats to which it exposes clients.   The threat model it addresses =
is the one where ancient DNSSEC responses are replayed in order to fool =
the client with stale information that would fail to validate (right?).

The problem is that the trust model for DHCP doesn't provide any =
assurance that the time being provided by DHCP will be any more =
trustworthy, even if the DHCP message is authenticated using the new =
proposal for doing public-key authentication of DHCP messages.  This =
authentication model typically depends on a leap of faith or else a =
pre-shared public key.   In the latter case, the time could be =
considered reasonably trustworthy.   In the former case, there's no =
reason at all to consider it trustworthy=97if the DNS server on the =
network is going to attack you, so is the DHCP server.

Hm, okay.   The one thing I can see this protecting against is the case =
of a rogue DNS server attempting to slam responses at a client on an =
otherwise-trustworthy wire.   But this is a really hard attack=97it has =
to have stored an old signed DNS hierarchy with stale keys that have =
been compromised.   This seems like it would be a fairly difficult =
achievement=97to present a consistent out-of-date hierarchy, the rogue =
server would have to have or get answers to any conceivable query that =
could be made against it, and be able to produce them faster than the =
real DNS server.   Even if it has a copy of an old root key, this is a =
tall order, and furthermore depends on the client resolver not having a =
more recent root key, which could be used to disprove the attacker's =
assertion that an old key is current.   It seems like SAVI would be a =
better way to prevent this attack.

What am I missing here?

(None of this is to say that a time option is necessarily a bad idea=97I'm=
 just not convinced that it addresses a plausible threat model.)=

From ogud@ogud.com  Sun Dec  1 14:05:55 2013
Return-Path: <ogud@ogud.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BE7D1AE1C3 for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 14:05:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0HoCvpMBWn-U for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 14:05:53 -0800 (PST)
Received: from smtp114.ord1c.emailsrvr.com (smtp114.ord1c.emailsrvr.com [108.166.43.114]) by ietfa.amsl.com (Postfix) with ESMTP id 5DE801AE1BC for <dhcwg@ietf.org>; Sun,  1 Dec 2013 14:05:53 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp7.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 447C61B8089; Sun,  1 Dec 2013 17:05:51 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp7.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 192F31B80A2;  Sun,  1 Dec 2013 17:05:49 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <C0A2F49F-7695-47E9-8AB0-7F94116437F9@nominum.com>
Date: Sun, 1 Dec 2013 17:05:48 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B0A571B5-438A-47AB-AAA4-00D3FC077E22@ogud.com>
References: <20131201204227.7978.2067.idtracker@ietfa.amsl.com> <83842BD2-0261-472F-9CA1-AFBFB47EAD91@ogud.com> <C0A2F49F-7695-47E9-8AB0-7F94116437F9@nominum.com>
To: Ted Lemon <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1510)
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 01 Dec 2013 22:05:55 -0000

On Dec 1, 2013, at 4:18 PM, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Dec 1, 2013, at 3:53 PM, Olafur Gudmundsson <ogud@ogud.com> wrote:
>> I wrote up this short document in order to address a problem seen in =
certain devices
>> that do not have good time at startup. The document  proposes a DHCv4 =
option and
>> DHCPv6 option to supply current time to a device. (there is also a =
proposed ND option
>> for the same thing).=20
>>=20
>> I looked into using option 152 from Bulk Query but that is only 32 =
bit long, and=20
>> it seems cleaner to just get a 64bit time_t option into DHC
>=20
> I think it's worth thinking about the threat model this addresses, and =
the threats to which it exposes clients.   The threat model it addresses =
is the one where ancient DNSSEC responses are replayed in order to fool =
the client with stale information that would fail to validate (right?).

The "threat" the document is trying to address, device wants to DNSSEC =
or CERT validation but clock is far off thus VALID credentials fail =
validation.=20
I can solve this for DNS by enabling DNSSEC after time is "reasonable", =
but then the next protocol comes along that needs this same thing =85.=20=


The threat that this document "creates" is spoof of time thus old CERT's =
and DNSSEC records can be replayed, in order for that to succeed the
attacker needs to know what the device wants to do and the attacker can =
only do this on local link.=20

>=20
> The problem is that the trust model for DHCP doesn't provide any =
assurance that the time being provided by DHCP will be any more =
trustworthy, even if the DHCP message is authenticated using the new =
proposal for doing public-key authentication of DHCP messages.  This =
authentication model typically depends on a leap of faith or else a =
pre-shared public key.   In the latter case, the time could be =
considered reasonably trustworthy.   In the former case, there's no =
reason at all to consider it trustworthy=97if the DNS server on the =
network is going to attack you, so is the DHCP server.
>=20

If we take this to its logical conclusion why should anyone think it got =
a good address from the DHCP server?=20
or a good DNS resolver?=20

we are already making a leap-of-faith by accepting these how much worse =
is to accept "time" ?=20

Well if I'm in random coffee shop yes then I would be concerned, but the =
router on the ISP connection at my home?=20

For things to work right we have to create a hierarchy of time =
credentials inside the host=20
at the bottom is=20
	"clock close to Jan 1 1970"   =3D=3D> OK ask DHCP and/or ND for =
time=20

Then:=20
	"last saved time + X days < clock " =3D=3D=3D> long time since =
last check what does DHCP say pick highest value=20
=09
	"clock is > last saved time" =3D=3D> we are ok see if NTP works=20=


At the top=20
	"NTP radio and GPS time signal" =3D=3D> use this to set clock=20


> Hm, okay.   The one thing I can see this protecting against is the =
case of a rogue DNS server attempting to slam responses at a client on =
an otherwise-trustworthy wire.   But this is a really hard attack=97it =
has to have stored an old signed DNS hierarchy with stale keys that have =
been compromised.   This seems like it would be a fairly difficult =
achievement=97to present a consistent out-of-date hierarchy, the rogue =
server would have to have or get answers to any conceivable query that =
could be made against it, and be able to produce them faster than the =
real DNS server.   Even if it has a copy of an old root key, this is a =
tall order, and furthermore depends on the client resolver not having a =
more recent root key, which could be used to disprove the attacker's =
assertion that an old key is current.   It seems like SAVI would be a =
better way to prevent this attack.
>=20
> What am I missing here?
>=20

There is no need to spoof time to downgrade DNSSEC on local link, you =
need some device to answer w/o RRSIG records for all questions asked no =
matter where the questions go. =3D=3D> the document does not make things =
worse.=20
Right now not being able to get time from local network is IDENTICAL to =
getting bad time from DHCP.=20


> (None of this is to say that a time option is necessarily a bad =
idea=97I'm just not convinced that it addresses a plausible threat =
model.)

Right,  but the draft does not make things any worse, if I want to spoof =
time, the easy way is to forge addresses for NTP servers to the ones I =
control, I do this by having the local (trusted) resolvers (supplied by =
untrustworthy DHCP) strip out all RRsig records, and I forge answers for =
all attempts trying to reach outside DNS servers/resolvers. =20
Actually for clients that use the NTP DHCP option all I need to forge =
there are bad NTP server names.=20

These attacks can only be conducted by someone that is on-path, and sees =
the DHCP messages.=20

	Olafur


From Ted.Lemon@nominum.com  Sun Dec  1 14:29:22 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEBA11AE1EB for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 14:29:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 44C26HKu8tVd for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 14:29:20 -0800 (PST)
Received: from exprod7og128.obsmtp.com (exprod7og128.obsmtp.com [64.18.2.121]) by ietfa.amsl.com (Postfix) with ESMTP id BDBA51AE1DE for <dhcwg@ietf.org>; Sun,  1 Dec 2013 14:29:20 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob128.postini.com ([64.18.6.12]) with SMTP ID DSNKUpu4PkAGgMqdU2uWPb2DKs+vhEFtLEHI@postini.com; Sun, 01 Dec 2013 14:29:19 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 73FF81B82EA for <dhcwg@ietf.org>; Sun,  1 Dec 2013 14:29:18 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 5086A190043; Sun,  1 Dec 2013 14:29:18 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sun, 1 Dec 2013 14:29:18 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <B0A571B5-438A-47AB-AAA4-00D3FC077E22@ogud.com>
Date: Sun, 1 Dec 2013 17:29:14 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <331C154E-1A09-4BDD-A70A-AB67BEA2E1E8@nominum.com>
References: <20131201204227.7978.2067.idtracker@ietfa.amsl.com> <83842BD2-0261-472F-9CA1-AFBFB47EAD91@ogud.com> <C0A2F49F-7695-47E9-8AB0-7F94116437F9@nominum.com> <B0A571B5-438A-47AB-AAA4-00D3FC077E22@ogud.com>
To: Olafur Gudmundsson <ogud@ogud.com>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 01 Dec 2013 22:29:22 -0000

On Dec 1, 2013, at 5:05 PM, Olafur Gudmundsson <ogud@ogud.com> wrote:
> The "threat" the document is trying to address, device wants to DNSSEC =
or CERT validation but clock is far off thus VALID credentials fail =
validation.=20

Ah, thanks for explaining.   This is what I was missing=97you're not =
doing this to avoid a threat at all, but rather to simply make DNSSEC =
work in a possibly non-secure mode until such time as you can bootstrap =
better time information.

This would be worth mentioning in the introduction and/or the security =
considerations section. You allude to it in the security considerations, =
but it's pretty oblique.

It is worth pointing out that NTP doesn't actually need DNS to work=97DHCP=
 can deliver NTP server addresses as IP addresses.   That said, this =
option seems to add value, since there is no guarantee that devices that =
implement the existing DHCP NTP will not send FQDNs rather than IP =
addresses.


From mayer@ntp.org  Sun Dec  1 16:31:47 2013
Return-Path: <mayer@ntp.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0513B1AE212 for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 16:31:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ic-JisuIabp8 for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 16:31:45 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by ietfa.amsl.com (Postfix) with ESMTP id 15E4E1AE297 for <dhcwg@ietf.org>; Sun,  1 Dec 2013 16:31:44 -0800 (PST)
Received: from pool-173-76-224-232.bstnma.fios.verizon.net ([173.76.224.232] helo=[192.168.1.3]) by mail1.ntp.org with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <mayer@ntp.org>) id 1VnHQJ-0004FJ-DI; Mon, 02 Dec 2013 00:31:40 +0000
Message-ID: <529BD4CF.6000408@ntp.org>
Date: Sun, 01 Dec 2013 19:31:11 -0500
From: Danny Mayer <mayer@ntp.org>
Organization: NTP
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>, Olafur Gudmundsson <ogud@ogud.com>
References: <20131201204227.7978.2067.idtracker@ietfa.amsl.com> <83842BD2-0261-472F-9CA1-AFBFB47EAD91@ogud.com> <C0A2F49F-7695-47E9-8AB0-7F94116437F9@nominum.com> <B0A571B5-438A-47AB-AAA4-00D3FC077E22@ogud.com> <331C154E-1A09-4BDD-A70A-AB67BEA2E1E8@nominum.com>
In-Reply-To: <331C154E-1A09-4BDD-A70A-AB67BEA2E1E8@nominum.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-SA-Exim-Connect-IP: 173.76.224.232
X-SA-Exim-Rcpt-To: ted.lemon@nominum.com, ogud@ogud.com, dhcwg@ietf.org, ntpwg@lists.ntp.org, volz@cisco.com
X-SA-Exim-Mail-From: mayer@ntp.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mayer@ntp.org
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Dec 2013 00:31:47 -0000

On 12/1/2013 5:29 PM, Ted Lemon wrote:
> On Dec 1, 2013, at 5:05 PM, Olafur Gudmundsson <ogud@ogud.com> wrote:
>> The "threat" the document is trying to address, device wants to
DNSSEC or CERT validation but clock is far off thus VALID credentials
fail validation.
> 
> Ah, thanks for explaining. This is what I was missing—you're not
> doing
this to avoid a threat at all, but rather to simply make DNSSEC work in
a possibly non-secure mode until such time as you can bootstrap better
time information.
> 
> This would be worth mentioning in the introduction and/or the
> security
considerations section. You allude to it in the security considerations,
but it's pretty oblique.
> 
> It is worth pointing out that NTP doesn't actually need DNS to
work—DHCP can deliver NTP server addresses as IP addresses. That said,
this option seems to add value, since there is no guarantee that devices
that implement the existing DHCP NTP will not send FQDNs rather than IP
addresses.

I had a long discussion with Bernie over the issue of delivering NTP IP
addresses via DHCP. We understand the issues you raised concerning
DNSSEC and have no disagreement about that. The problem is that for NTP
DNS names are preferred over IP addresses because that allows a server
maintainer to retire an NTP server. With an IP address there is no
chance that your local instance will know about this and continue to
bombard the old address. Moreover the newer pool option cannot be used
to any advantage.

When was the last time you looked at your NTP configuration and verified
that all of the servers listed are still valid? How often will DHCP
servers do this as a matter of course before providing such
provisioning? We have systems that are being bombarded by requests even
though no NTP server is responding to queries. We have plenty of
evidence of this. Even worse we have seen home routers which have
hard-coded IP addresses for NTP servers embedded. How long are those
going to be in operation?

I think we need to figure out how to get around the Catch-22 situation
of DNSSEC requiring relatively good time and NTP wanting to be able to
use DNS to find valid NTP servers.

We need a joint agreement on how to deal with this between DHCP and NTP
Working Groups assuming that is a viable option in the first place.
RFC5908 was not a good indication of this.

Danny


From leo.liubing@huawei.com  Sun Dec  1 17:22:24 2013
Return-Path: <leo.liubing@huawei.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 590B21AE2A8 for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 17:22:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vrTIh-HsQhId for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 17:22:21 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 21B411AE23B for <dhcwg@ietf.org>; Sun,  1 Dec 2013 17:22:20 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BAX19606; Mon, 02 Dec 2013 01:22:18 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 2 Dec 2013 01:21:32 +0000
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 2 Dec 2013 01:22:16 +0000
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.72]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Mon, 2 Dec 2013 09:22:11 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 - Respond by Dec 2, 2013
Thread-Index: Ac7kgW5Zu29batgdRjKYwweN6OdP2gHNcU1QANFmzmA=
Date: Mon, 2 Dec 2013 01:22:10 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D8214E6@nkgeml506-mbx.china.huawei.com>
References: <489D13FBFA9B3E41812EA89F188F018E1AD98DE0@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADC2A5B@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADC2A5B@xmb-rcd-x04.cisco.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.132]
Content-Type: multipart/alternative; boundary="_000_8AE0F17B87264D4CAC7DE0AA6C406F453D8214E6nkgeml506mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 - Respond by Dec 2, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 01:22:24 -0000

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

Hi, All

I support moving forward this document.

Best Regards,
Bing

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Thursday, November 28, 2013 5:31 AM
To: dhcwg@ietf.org
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 - Respon=
d by Dec 2, 2013

This is friendly reminder that we need responses by end of day (anywhere in=
 the world) December 2nd. Sorry for the 'late' reminder for those in the US=
 enjoying Thanksgiving.

So far, there has only been Sheng's (document shepherd) comments.

<WG Co-Chair Hat OFF>
I add my support for this document (with Sheng's comments addressed as he c=
aptured my nits and more).


-        Bernie

From: dhcwg-bounces@ietf.org<mailto:dhcwg-bounces@ietf.org> [mailto:dhcwg-b=
ounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Monday, November 18, 2013 12:15 PM
To: dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Subject: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 - Respond by=
 Dec 2, 2013


Folks, the authors of draft-ietf-dhc-dhcpv6-unknown-msg-03 (http://tools.ie=
tf.org/html/draft-ietf-dhc-dhcpv6-unknown-msg-03) believe it is ready for w=
orking group last call. Please review this draft and indicate whether or no=
t you feel it is ready to be published. Your input is important! Please res=
pond by Dec 2nd, 2013.



At the time of this writing, there is no IPR reported against this draft.



Thanks,


-        Tomek & Bernie


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"\7EAF\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"\6279\6CE8\6846\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Char
	{mso-style-name:"\7EAF\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\7EAF\6587\672C;
	font-family:SimSun;}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.Char0
	{mso-style-name:"\6279\6CE8\6846\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\6279\6CE8\6846\6587\672C;
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:866522167;
	mso-list-type:hybrid;
	mso-list-template-ids:1690722640 1420754368 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1
	{mso-list-id:1895698345;
	mso-list-type:hybrid;
	mso-list-template-ids:142488886 -808004726 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></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=3D"ZH-CN" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">Hi, All<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">I support moving forward this document.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">Best Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D">Bing<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;color=
:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> dhcwg [mailto:dhcwg-bounces@ietf.org]
<b>On Behalf Of </b>Bernie Volz (volz)<br>
<b>Sent:</b> Thursday, November 28, 2013 5:31 AM<br>
<b>To:</b> dhcwg@ietf.org<br>
<b>Subject:</b> Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 -=
 Respond by Dec 2, 2013<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">This is=
 friendly reminder that we need responses by end of day (anywhere in the wo=
rld) December 2<sup>nd</sup>. Sorry for the &#8216;late&#8217; reminder for=
 those in the US enjoying Thanksgiving.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">So far,=
 there has only been Sheng&#8217;s (document shepherd) comments.<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">&lt;WG =
Co-Chair Hat OFF&gt;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">I add m=
y support for this document (with Sheng&#8217;s comments addressed as he ca=
ptured my nits and more).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l1 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-US" style=3D"color:#1F497D">=
<span style=3D"mso-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New =
Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US" style=3D"color:#1F497D"=
>Bernie<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;">
<a href=3D"mailto:dhcwg-bounces@ietf.org">dhcwg-bounces@ietf.org</a> [<a hr=
ef=3D"mailto:dhcwg-bounces@ietf.org">mailto:dhcwg-bounces@ietf.org</a>]
<b>On Behalf Of </b>Bernie Volz (volz)<br>
<b>Sent:</b> Monday, November 18, 2013 12:15 PM<br>
<b>To:</b> <a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><br>
<b>Subject:</b> [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 - Res=
pond by Dec 2, 2013<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Folks, the authors of draft-=
ietf-dhc-dhcpv6-unknown-msg-03 (<a href=3D"http://tools.ietf.org/html/draft=
-ietf-dhc-dhcpv6-unknown-msg-03">http://tools.ietf.org/html/draft-ietf-dhc-=
dhcpv6-unknown-msg-03</a>) believe it
 is ready for working group last call. Please review this draft and indicat=
e whether or not you feel it is ready to be published. Your input is import=
ant! Please respond by Dec 2<sup>nd</sup>, 2013.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">At the time of this writing,=
 there is no IPR reported against this draft.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">Thanks,<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo4"><![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:=
Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">Tomek &amp; Bernie<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</body>
</html>

--_000_8AE0F17B87264D4CAC7DE0AA6C406F453D8214E6nkgeml506mbxchi_--

From Ted.Lemon@nominum.com  Sun Dec  1 18:37:06 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC571AE2C3 for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 18:37:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7bO3JgZHIufu for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 18:37:04 -0800 (PST)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id 9F5CC1AE238 for <dhcwg@ietf.org>; Sun,  1 Dec 2013 18:37:04 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKUpvyTgwqxvKP1RiyfjSgXzLi2akBRs5z@postini.com; Sun, 01 Dec 2013 18:37:02 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 655561B82F0 for <dhcwg@ietf.org>; Sun,  1 Dec 2013 18:37:02 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 40901190043; Sun,  1 Dec 2013 18:37:02 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sun, 1 Dec 2013 18:37:02 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <529BD4CF.6000408@ntp.org>
Date: Sun, 1 Dec 2013 21:36:59 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <A775B456-E8F6-4111-AFB3-B51BB92ABFC7@nominum.com>
References: <20131201204227.7978.2067.idtracker@ietfa.amsl.com> <83842BD2-0261-472F-9CA1-AFBFB47EAD91@ogud.com> <C0A2F49F-7695-47E9-8AB0-7F94116437F9@nominum.com> <B0A571B5-438A-47AB-AAA4-00D3FC077E22@ogud.com> <331C154E-1A09-4BDD-A70A-AB67BEA2E1E8@nominum.com> <529BD4CF.6000408@ntp.org>
To: <mayer@ntp.org>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 02:37:06 -0000

On Dec 1, 2013, at 7:31 PM, Danny Mayer <mayer@ntp.org> wrote:
> We need a joint agreement on how to deal with this between DHCP and =
NTP
> Working Groups assuming that is a viable option in the first place.
> RFC5908 was not a good indication of this.

RFC 5908 got approved pretty much accidentally, without finishing the =
review process in the DHC working group.   It was a major screwup, and I =
don't precisely know how it happened.   It doesn't really do what you =
wanted, and it certainly doesn't do what we wanted.   I agree that this =
needs to be resolved, but the resolution has to be based on reasoning, =
not an instinctive reaction to past pain.

I'm not even convinced that DHCP is the right way to distribute NTP =
server information.   I suspect Olafur may be thinking about the case =
that's more common at present, which is that an FQDN is hard-coded into =
the O.S. distribution, and resolved at startup time.   In that case, =
DHCP's ability to deliver NTP server IP addresses doesn't help.

As for the home router use model, it may be that what you really want is =
for the home router to query for an FQDN-only DHCP option from the ISP =
DHCP server, and then resolve that FQDN and respond to DHCP clients on =
the homenet with an IP address.   Since the FQDN is not hard-coded, and =
the IP address is (one hopes) resolved either at query time or when its =
TTL expires, this ought to prevent a repeat of the firmware burn-in =
incident.


From Ted.Lemon@nominum.com  Sun Dec  1 21:13:33 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 048D41AE3E2 for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 21:13:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id txsJa4IdF5FH for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 21:13:31 -0800 (PST)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id 53FC11AE3E0 for <dhcwg@ietf.org>; Sun,  1 Dec 2013 21:13:31 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKUpwW+eC+y1P8KtjegzUPKGOEEE4nQVCa@postini.com; Sun, 01 Dec 2013 21:13:29 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 038F01B82C3 for <dhcwg@ietf.org>; Sun,  1 Dec 2013 21:13:28 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id CFB62190043; Sun,  1 Dec 2013 21:13:27 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sun, 1 Dec 2013 21:13:27 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net>
Date: Mon, 2 Dec 2013 00:13:17 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <D5CCC8A9-10FF-4D57-AB42-D39AB4D8730F@nominum.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net>
To: Hal Murray <hmurray@megapathdsl.net>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: NTP Working Group <ntpwg@lists.ntp.org>, Bernie Volz <volz@cisco.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 05:13:33 -0000

On Dec 1, 2013, at 11:47 PM, Hal Murray <hmurray@megapathdsl.net> wrote:
> Does DNS using DNSSEC return a specific error code for time-invalid?  =
Or just=20
> a generic didn't-work?

A response with a bad clock fails to validate, which is the same as no =
response.

> How close does the time have to be for DNSSEC to work?

Closer than 1970.

> Could this problem be solved by setting up a bank of NTP servers at =
well=20
> known IP Addresses?  Say, one next to each root DNS server.  If you =
tried to=20
> do that, I'd expect a serious problem would be overload because idiots =
would=20
> try to use them for normal NTP use rather than just getting off the =
ground. =20
> It might be possible to discourage that by making them return crappy =
time.

History suggests otherwise.   If an IP address is hardcoded, it will get =
pummeled by devices that are too dumb to give up.

> Most ISPs already provide DNS servers for their customers.  How do =
their IP=20
> address get setup in home routers?  Could NTP servers piggyback on =
that=20
> mechanism if ISPs also provided NTP servers?

You mean DHCP?   Yes, that's what we're talking about.


From mayer@ntp.org  Sun Dec  1 21:27:43 2013
Return-Path: <mayer@ntp.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 884C01AE3D0 for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 21:27:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JrQdLkO5tCTX for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 21:27:42 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by ietfa.amsl.com (Postfix) with ESMTP id 36EE71AE269 for <dhcwg@ietf.org>; Sun,  1 Dec 2013 21:27:42 -0800 (PST)
Received: from static-108-1-140-117.bstnma.east.verizon.net ([108.1.140.117] helo=[10.10.10.102]) by mail1.ntp.org with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <mayer@ntp.org>) id 1VnM2i-0005zH-Q1; Mon, 02 Dec 2013 05:27:38 +0000
Message-ID: <529C1A31.2080900@ntp.org>
Date: Mon, 02 Dec 2013 00:27:13 -0500
From: Danny Mayer <mayer@ntp.org>
Organization: NTP
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Hal Murray <hmurray@megapathdsl.net>,  Ted Lemon <ted.lemon@nominum.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net>
In-Reply-To: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 108.1.140.117
X-SA-Exim-Rcpt-To: hmurray@megapathdsl.net, ted.lemon@nominum.com, ntpwg@lists.ntp.org, dhcwg@ietf.org, volz@cisco.com, ogud@ogud.com
X-SA-Exim-Mail-From: mayer@ntp.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mayer@ntp.org
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Dec 2013 05:27:43 -0000

On 12/1/2013 11:47 PM, Hal Murray wrote:
> Does DNS using DNSSEC return a specific error code for time-invalid?  Or just 
> a generic didn't-work?
> 
> How close does the time have to be for DNSSEC to work?
> 

That's a question that should be asked in the dnsext WG mailing list
(though technically the Working Group is now closed). Olafur and I
(apart from Ted who is IETF area director) are probably the only ones on
these lists who participate in that mailing list. Olafur was one of the
cochairs of the DNS ext working group.

The document does not describe the DNSSEC requirements for accurate time
and probably should so that it can be assessed in that light.
The ones I know about are RRSIG inception time and expiration time and
then there are certificate expiration date-times.

The proposal seems to suggest that a timestamp in 64-bit time_t be
distributed by DHCP. I'm not sure why not a NTP timestamp instead.
However most systems running a DNS server is likely to have a static
address in the first place and that is what DHCP distributes as
nameservers to query. Since they use static addresses do they
participate in DHCP services at all? And who says that the DHCP server
itself has accurate time?

> Could this problem be solved by setting up a bank of NTP servers at well 
> known IP Addresses?  Say, one next to each root DNS server.  If you tried to 
> do that, I'd expect a serious problem would be overload because idiots would 
> try to use them for normal NTP use rather than just getting off the ground.  
> It might be possible to discourage that by making them return crappy time.
> 

No, it would just overwhelm them. See the NIST time servers for an
example of heavy load.

> 
> ted.lemon@nominum.com said:
>> As for the home router use model, it may be that what you really want is for
>> the home router to query for an FQDN-only DHCP option from the ISP DHCP
>> server, and then resolve that FQDN and respond to DHCP clients on the
>> homenet with an IP address.   Since the FQDN is not hard-coded, and the IP
>> address is (one hopes) resolved either at query time or when its TTL
>> expires, this ought to prevent a repeat of the firmware burn-in incident. 
> 
> Most ISPs already provide DNS servers for their customers.  How do their IP 
> address get setup in home routers?  Could NTP servers piggyback on that 
> mechanism if ISPs also provided NTP servers?

I wish they would provide NTP services in the same way. Unfortunately
although most ISP's will have NTP servers they do not usually tell their
customers about them and they certainly do not provide authenticated
packets like autokey.

Danny

From stenn@stenn.ntp.org  Sun Dec  1 21:39:03 2013
Return-Path: <stenn@stenn.ntp.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D339B1AE41D for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 21:39:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SIs7E-YVzBNG for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 21:39:02 -0800 (PST)
Received: from stenn.ntp.org (stenn.ntp.org [149.20.68.30]) by ietfa.amsl.com (Postfix) with ESMTP id BB87D1AE3FF for <dhcwg@ietf.org>; Sun,  1 Dec 2013 21:39:02 -0800 (PST)
Received: from localhost.ntp.org ([::1] helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1VnMCF-00004p-O7; Mon, 02 Dec 2013 05:37:27 +0000
From: Harlan Stenn <stenn@ntp.org>
To: Hal Murray <hmurray@megapathdsl.net>
In-reply-to: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net>
Comments: In-reply-to Hal Murray <hmurray@megapathdsl.net> message dated "Sun, 01 Dec 2013 20:47:34 -0800."
X-Mailer: MH-E 7.4.2; nmh 1.5; XEmacs 21.4 (patch 22)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Mon, 02 Dec 2013 05:37:27 +0000
Message-Id: <E1VnMCF-00004p-O7@stenn.ntp.org>
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Ted Lemon <ted.lemon@nominum.com>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 05:39:04 -0000

We already know we want to discuss how long NTP will use an IP it got
from a DNS lookup.

We know there is no good API to get the TTL from this lookup.

An IP can easily be moved to another machine; there's no reason to have
a TTL for these.

On the other hand, there is a way to update ntpd's config file.

See http://support.ntp.org/Dev/GettingNtpdItsConfiguration for more
information, and we might want to look at "refreshing" URL-based
configurations on a schedule.

H

From sunqi.csnet.thu@gmail.com  Sun Dec  1 22:13:04 2013
Return-Path: <sunqi.csnet.thu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03B811AE269 for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 22:13:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K0SQ5W5_dLah for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 22:13:01 -0800 (PST)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id ED2C41AE15C for <dhcwg@ietf.org>; Sun,  1 Dec 2013 22:13:00 -0800 (PST)
Received: by mail-pd0-f170.google.com with SMTP id g10so17511803pdj.1 for <dhcwg@ietf.org>; Sun, 01 Dec 2013 22:12:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=jMpSqdHMDBZg0rKy12ijdmDJO9BvOEUWrLh1Ix9ZdfQ=; b=u0pc/DyH3fa+ZgBSAayn3Gqkvp/62j2NPBrDZylfRXVPuZgHmybQgqSUoGGvN5D/GD l90wMw5iBzI12nJPgPudwFHuQezYtI1QC+D7IELIrtqVd2ZKVIHY28tuldlhqE9XgfEO R3mvMfcWe4XYylDrd3uTfTmC+VS6wg1CWQYrT1X40W06WU5zT7aHPMsh79qNE8yYkzxS SnUczjqvZ7+PponhXtA8LePUVkn7HNThDRQW1COjt/qSKe2PZC7XN3w7VBmt1Pmd8r8X MNZVkaP3VL+cSO1ckKa6gkZqhZSAaY389LeWfH1XiiCMCCBWl3jL1rnGynVNNxv5WTJU hkMg==
X-Received: by 10.66.191.162 with SMTP id gz2mr1621511pac.151.1385964778890; Sun, 01 Dec 2013 22:12:58 -0800 (PST)
Received: from [192.168.199.122] ([166.111.68.231]) by mx.google.com with ESMTPSA id ye1sm135913904pab.19.2013.12.01.22.12.56 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 01 Dec 2013 22:12:58 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-3--364319935
From: Qi Sun <sunqi.csnet.thu@gmail.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADC41A3@xmb-rcd-x04.cisco.com>
Date: Mon, 2 Dec 2013 14:12:52 +0800
Message-Id: <F476551F-B235-4334-8A54-13E72984D1CF@gmail.com>
References: <CEBB74DD.9C090%ian.farrer@telekom.de> <124F1F54-5997-46D9-A6F1-54F94E3D6423@gmail.com> <5295FCDD.9000300@viagenie.ca> <51308BAA-5F33-44B9-AB72-6AE42BA5E11D@gmail.com> <5296356D.90405@viagenie.ca> <489D13FBFA9B3E41812EA89F188F018E1ADC24C4@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADC25C8@xmb-rcd-x04.cisco.com> <CAF+sHxHSrZ5zEXrn0RpZqCUcfJ3xiisgFYKLCo5adBcMP3rGzA@mail.gmail.com> <6D0BACEB-D945-413B-98D9-3333092F45F6@cisco.com> <CAF+sHxGCk0hG2U+qMc+b=uk90c+c-4_WTJp-mxLLe-Vx_tuwCQ@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1ADC41A3@xmb-rcd-x04.cisco.com>
To: Bernie Volz (volz) <volz@cisco.com>
X-Mailer: Apple Mail (2.1085)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 06:13:04 -0000

--Apple-Mail-3--364319935
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


Hi Bernie,

Thanks for considering this. It could optimize the DHCPv4 unicast case, =
but may bring in some complexity.=20

IMHO, this is the current model:

When DHCPv4 unicast, the 4o6 client sends unicast packets to the =
available servers (listed in the 4o6 Server Address option), of course, =
with the Unicast Flag set. The server that was selected by the client =
will reply while the other servers would silently drop the packets. Then =
the client will get response from the dedicated server.=20

I'm not sure if this model would cause potential issues (it works, =
IMHO). Could you please point out if I missed anything? =20

Thanks,
Qi


On 2013-11-29, at =E4=B8=8A=E5=8D=8812:20, Bernie Volz (volz) wrote:

> The Server-Unicast option (if this is adopted) would be in the =
BOOTREPLYV6 which is processed by the 4o6 DHCP Client and does not =
impact the normal DHCPv6 transactions. (The 4o6 DHCP Client would =
request this in the ORO in the BOOTREQUESTV6.)
> =20
> I=E2=80=99m not sure if this is worth it. But just figured I=E2=80=99d =
suggest it.
> =20
> -          Bernie
> =20
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Cong Liu
> Sent: Thursday, November 28, 2013 10:44 AM
> To: Bernie Volz (volz)
> Cc: dhcwg@ietf.org
> Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - =
Respond by Dec 9, 2013
> =20
> Hi Bernie,
> =20
> Sorry, I thought you were talking about reuse 4o6 Server Address =
option.
> =20
> If regular DHCPv6 process is not affected by reusing Server Unicast =
option, I think it's a good solution.
> =20
> Cong
> =20
> 2013/11/28 Bernie Volz (volz) <volz@cisco.com>
> Cong, I don't understand this. Server-unicast option can only specify =
one address.
> =20
> The 4o6 client has two lists - the "broadcast" list and the "unicast" =
list. When v4 packet is to be "broadcast", the "broadcast" list is used. =
When unicast and the unicast list is not empty, it is used; otherwise =
broadcast list is used. Broadcast list comes from new 4o6 option or the =
v6 multicast address. Unicast list is empty unless the server's v4 lease =
that was selected sent a server-unicast option.
> =20
> Yes, if v4 client sends broadcast, packet could go to multiple servers =
but that's what happens with native v4.
> =20
> Anyway, just a thought to reduce traffic for v4 unicast case.
> =20
> - Bernie (from iPad)
>=20
> On Nov 28, 2013, at 2:32 AM, "Cong Liu" <gnocuil@gmail.com> wrote:
>=20
> Hi Bernie,
> =20
> 2013/11/28 Bernie Volz (volz) <volz@cisco.com>
> Here's a question we can also ponder ...
>=20
> Should we perhaps allow the server to send back the Server-Unicast =
option to tell the 4o6 Client where it can send unicast (DHCPv4) packets =
to? This would allow DHCPv4 unicast packets to be sent directly to the =
server (of course inside a BOOTREQUESTV6 message).
> =20
> Assume IPv6 lease time is 100s, and IPv4 lease time is 200s. Then the =
4o6 Client receives a Server-Unicast option (which may contains 10 =
unicast addresses) every 100s, and a Server-Unicast option (which =
contains 1 unicast address) every 200s. I think it adds more complexity =
for client to deal with the same option from different servers (DHCPv6 / =
DHCP4o6).
> =20
> Best Regards,
> Cong
> _______________________________________________
>=20
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
> =20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


--Apple-Mail-3--364319935
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><base href=3D"x-msg://33/"></head><body style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Heiti SC'; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: 'Heiti SC'; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Heiti SC'; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Heiti SC'; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div>Hi =
Bernie,</div><div><br></div><div>Thanks for considering this. It could =
optimize the DHCPv4 unicast case, but may bring in some =
complexity.&nbsp;</div><div><br></div><div>IMHO, this is the current =
model:</div><div><br></div><div>When DHCPv4 unicast, the 4o6 client =
sends unicast packets to the available servers (listed in the 4o6 Server =
Address option), of course, with the Unicast Flag set. The server that =
was selected by the client will reply while the other servers would =
silently drop the packets. Then the client will get response from the =
dedicated server.&nbsp;</div><div><br></div><div>I'm not sure if this =
model would cause potential issues (it works, IMHO). Could you please =
point out if I missed anything? =
&nbsp;</div><div><br></div><div>Thanks,</div>Qi<br><br></div></span></div>=
</span></div></span></span>
</div>
<br><div><div>On 2013-11-29, at =E4=B8=8A=E5=8D=8812:20, Bernie Volz =
(volz) wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: 'Heiti SC'; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">The =
Server-Unicast option (if this is adopted) would be in the BOOTREPLYV6 =
which is processed by the 4o6 DHCP Client and does not impact the normal =
DHCPv6 transactions. (The 4o6 DHCP Client would request this in the ORO =
in the BOOTREQUESTV6.)<o:p></o:p></span></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); ">I=E2=80=99m not sure if this is =
worth it. But just figured I=E2=80=99d suggest =
it.<o:p></o:p></span></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0.5in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; text-indent: =
-0.25in; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); "><span>-<span style=3D"font: =
normal normal normal 7pt/normal 'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span></span><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">Bernie<o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><b><span =
style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; =
">From:</span></b><span style=3D"font-size: 10pt; font-family: Tahoma, =
sans-serif; "><span class=3D"Apple-converted-space">&nbsp;</span>dhcwg =
[mailto:dhcwg-bounces@ietf.org]<span =
class=3D"Apple-converted-space">&nbsp;</span><b>On Behalf Of<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Cong =
Liu<br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Thursday, November 28, 2013 =
10:44 AM<br><b>To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Bernie Volz =
(volz)<br><b>Cc:</b><span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:dhcwg@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">dhcwg@ietf.org</a><br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Re: [dhcwg] WGLC for =
draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, =
2013<o:p></o:p></span></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">Hi =
Bernie,<o:p></o:p></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">Sorry, I thought you were =
talking about reuse 4o6 Server Address =
option.<o:p></o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">If regular DHCPv6 process =
is not affected by reusing&nbsp;<span style=3D"color: black; ">Server =
Unicast option, I think it's a good =
solution.</span><o:p></o:p></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"color: =
black; ">Cong</span><o:p></o:p></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">2013/11/28 Bernie Volz =
(volz) &lt;<a href=3D"mailto:volz@cisco.com" target=3D"_blank" =
style=3D"color: blue; text-decoration: underline; =
">volz@cisco.com</a>&gt;<o:p></o:p></div><div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; ">Cong, I don't understand this. Server-unicast option =
can only specify one address.<o:p></o:p></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><o:p>&nbsp;</o:p></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; ">The 4o6 client has two lists - the "broadcast" list and =
the "unicast" list. When v4 packet is to be "broadcast", the "broadcast" =
list is used. When unicast and the unicast list is not empty, it is =
used; otherwise broadcast list is used. Broadcast list comes from new =
4o6 option or the v6 multicast address. Unicast list is empty unless the =
server's v4 lease that was selected sent a server-unicast =
option.<o:p></o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">Yes, if v4 client sends =
broadcast, packet could go to multiple servers but that's what happens =
with native v4.<o:p></o:p></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">Anyway, just a thought to =
reduce traffic for v4 unicast case.<o:p></o:p></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><o:p>&nbsp;</o:p></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; ">- Bernie (from =
iPad)<o:p></o:p></div></div><div><div><div><p class=3D"MsoNormal" =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 12pt; font-size: 12pt; font-family: 'Times New Roman', =
serif; "><br>On Nov 28, 2013, at 2:32 AM, "Cong Liu" &lt;<a =
href=3D"mailto:gnocuil@gmail.com" target=3D"_blank" style=3D"color: =
blue; text-decoration: underline; ">gnocuil@gmail.com</a>&gt; =
wrote:<o:p></o:p></p></div><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt; "><div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">Hi =
Bernie,<o:p></o:p></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">2013/11/28 Bernie Volz =
(volz) &lt;<a href=3D"mailto:volz@cisco.com" target=3D"_blank" =
style=3D"color: blue; text-decoration: underline; =
">volz@cisco.com</a>&gt;<o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">Here's a question we can =
also ponder ...<br><br>Should we perhaps allow the server to send back =
the Server-Unicast option to tell the 4o6 Client where it can send =
unicast (DHCPv4) packets to? This would allow DHCPv4 unicast packets to =
be sent directly to the server (of course inside a BOOTREQUESTV6 =
message).<o:p></o:p></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">Assume IPv6 lease time is =
100s, and IPv4 lease time is 200s. Then the 4o6 Client receives =
a&nbsp;<span style=3D"font-size: 10.5pt; font-family: Arial, sans-serif; =
">Server-Unicast option (which may contains 10 unicast addresses) every =
100s, and&nbsp;</span>a&nbsp;<span style=3D"font-size: 10.5pt; =
font-family: Arial, sans-serif; ">Server-Unicast option (which contains =
1 unicast address) every 200s. I think it adds =
more&nbsp;complexity&nbsp;for client to deal with the same option from =
different servers (DHCPv6 / =
DHCP4o6).</span><o:p></o:p></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
10.5pt; font-family: Arial, sans-serif; ">Best =
Regards,</span><o:p></o:p></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 10.5pt; font-family: Arial, sans-serif; =
">Cong</span><o:p></o:p></div></div></div></div></div></div></blockquote><=
/div></div><blockquote style=3D"margin-top: 5pt; margin-bottom: 5pt; =
"><div><div style=3D"margin-top: 0in; margin-right: 0in; margin-left: =
0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; =
">_______________________________________________<o:p></o:p></div><div><di=
v style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><br>dhcwg mailing list<br><a =
href=3D"mailto:dhcwg@ietf.org" target=3D"_blank" style=3D"color: blue; =
text-decoration: underline; ">dhcwg@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/dhcwg" target=3D"_blank" =
style=3D"color: blue; text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/dhcwg</a><o:p></o:p></div></div></=
div></blockquote></div></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div></div></div>_______________________________=
________________<br>dhcwg mailing list<br><a =
href=3D"mailto:dhcwg@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">dhcwg@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/dhcwg" style=3D"color: =
blue; text-decoration: underline; =
">https://www.ietf.org/mailman/listinfo/dhcwg</a><br></div></span></blockq=
uote></div><br></body></html>=

--Apple-Mail-3--364319935--

From imp@bsdimp.com  Sun Dec  1 22:44:20 2013
Return-Path: <imp@bsdimp.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD90B1AE430 for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 22:44:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ptaFaSey8Y1N for <dhcwg@ietfa.amsl.com>; Sun,  1 Dec 2013 22:44:19 -0800 (PST)
Received: from mail-ie0-f170.google.com (mail-ie0-f170.google.com [209.85.223.170]) by ietfa.amsl.com (Postfix) with ESMTP id 14FC51AE42E for <dhcwg@ietf.org>; Sun,  1 Dec 2013 22:44:18 -0800 (PST)
Received: by mail-ie0-f170.google.com with SMTP id qd12so20355775ieb.15 for <dhcwg@ietf.org>; Sun, 01 Dec 2013 22:44:16 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=hxuriIhvYgqb//cL5upEal9Qx4mZNSkISMD/QiiDoqU=; b=FPhn1QHQUh7rVwrTJufYfHspi9rEI8g+v39ORvfTqS8h9l8e+snYweS6lx84HKi9FE 0GJ7AUVU6A0Z3HMqGHvAFzO61WFaulfs+96oiwT/mclf7YRbpxh72pF5DVmYYbC2Glkz uhYkqgc9XXUU7Cn+p6l6NjErbQV+/likvMRNQP5gSN5MR+MYzPZvx/ofT/xqLNlojAb9 V+Hr43UDZcfGuKVVgDt9pMMz/J28ZI8g4dfaBRPdqDlENTB6+s8WvhAqpZjR8PBva0E/ +WnTHr+fWLylJjqyRKYLx/A3Is0T/EjQ7pnee+wjvhe4oxBMLkO4buLdDZcgpLWoY8KD HcJg==
X-Gm-Message-State: ALoCoQnn7qhPgGLer6Bc0Q68U2E0TsZPS1Thbub+0SpOBWPho3hK5N8qs49QkcD+Rb4N1PkoxQFz
X-Received: by 10.43.106.198 with SMTP id dv6mr368644icc.51.1385966656579; Sun, 01 Dec 2013 22:44:16 -0800 (PST)
Received: from 53.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id u1sm64644385ige.1.2013.12.01.22.44.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 01 Dec 2013 22:44:15 -0800 (PST)
Sender: Warner Losh <wlosh@bsdimp.com>
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Warner Losh <imp@bsdimp.com>
In-Reply-To: <D5CCC8A9-10FF-4D57-AB42-D39AB4D8730F@nominum.com>
Date: Sun, 1 Dec 2013 23:44:14 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <F53087EB-C5E0-4305-929D-5BFEA3C266AD@bsdimp.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <D5CCC8A9-10FF-4D57-AB42-D39AB4D8730F@nominum.com>
To: Ted Lemon <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1085)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 06:45:42 -0000

On Dec 1, 2013, at 10:13 PM, Ted Lemon wrote:
>> How close does the time have to be for DNSSEC to work?
> 
> Closer than 1970.

So 5 years in the future is no problem?

Warner


From msiodelski@gmail.com  Mon Dec  2 01:32:46 2013
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD37E1AE082 for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 01:32:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J1hbTGCSq9QG for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 01:32:45 -0800 (PST)
Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 52C041AE07D for <dhcwg@ietf.org>; Mon,  2 Dec 2013 01:32:45 -0800 (PST)
Received: by mail-ie0-f179.google.com with SMTP id x13so20782826ief.10 for <dhcwg@ietf.org>; Mon, 02 Dec 2013 01:32:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=MBUGxQzeFwvY7fghP8/jYSCD3KSOplF0mKHc8YI2w7Q=; b=prSiFTsodqEvUyV1NhtHO2snoeA2jPbGEVn7Zz6ngjhUWLVew00g6qRzcJ+Y4emDbl th2WIsNhf8YLdzz1ChE4y361Qu9vneM1uPDBiggBkyMVRqfWIGrLsC4ZtBoBMUttvphr 0/5BoK2M5sIUi8846cqa6nuX3vS9r/c7x/uzw3SDa3piA8nBDHtz+Rsl6Dail8QZFizz WS75KFN9xmpC0M9MMiaM49OknDVVp7l28LtM2uREqZdGRSfT9GXQhIfh98/vbuSoH/pC xugDaZgpRZX6duWeZFUv/xdkJHeBA9BWRA/OHoHyHijYTQ41ez1g8um9auHm6VN0Ky/E RIjA==
MIME-Version: 1.0
X-Received: by 10.42.148.200 with SMTP id s8mr233364icv.67.1385976763176; Mon, 02 Dec 2013 01:32:43 -0800 (PST)
Received: by 10.50.32.33 with HTTP; Mon, 2 Dec 2013 01:32:43 -0800 (PST)
In-Reply-To: <AC25F22F-A27C-40FC-B4AF-9EA886D973A6@gmail.com>
References: <489D13FBFA9B3E41812EA89F188F018E1AD98DE0@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADC2A5B@xmb-rcd-x04.cisco.com> <CAFGoqUMh-xT+GsJQNHGUcisqcphAVFZXnQ6ac+GXq76wBBiyYw@mail.gmail.com> <AC25F22F-A27C-40FC-B4AF-9EA886D973A6@gmail.com>
Date: Mon, 2 Dec 2013 10:32:43 +0100
Message-ID: <CAFGoqUOtzad1iNMrqs5vyy5wqewxw445Q_iAiKgYjgLvocR5EQ@mail.gmail.com>
From: Marcin Siodelski <msiodelski@gmail.com>
To: Qi Sun <sunqi.csnet.thu@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 - Respond by Dec 2, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 09:32:46 -0000

>> ISSUE 2
>> In this sentence:
>>
>> "In the case that a new type of relay message is sent to a relay agent
>>   but the relay agent doesn't recognize it, the message is put into a
>>   Relay-forward message and sent to the server."
>>
>> Why "new type of relay message", not "new type of message"? I don't
>> quite understand what the relay message is in this context.
>
> [Qi] A new type of relay message targets at the relay agent. If a relay a=
gent recognizes the message, then it should consume the message. Otherwise,=
 the relay just sends the message to the server (in a Relay-forward message=
), so that the server gets the information that this relay doesn't support =
the new relay agent message.
> In Bullet (b), the message doesn't take the relay agent as the target.
> If this part isn't clear enough, we can improve it.
>

Thanks for this explanation. Let me rephrase my question, because I
was asking about slightly different thing....

Would it still be ok if we had this text: "In the case that a new type
of message is sent to a relay agent..... ", instead of "In the case
that a new type of relay message is sent to a relay agent..."? Simply
removed "relay". I don't understand how "relay message" is different
from the "message" or "valid message".

Thanks,
Marcin

From sunqi.csnet.thu@gmail.com  Mon Dec  2 04:26:39 2013
Return-Path: <sunqi.csnet.thu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37F001AE46D for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 04:26:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id amHCHUUBguav for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 04:26:37 -0800 (PST)
Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id C05381AE470 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 04:26:35 -0800 (PST)
Received: by mail-pb0-f41.google.com with SMTP id jt11so18877244pbb.14 for <dhcwg@ietf.org>; Mon, 02 Dec 2013 04:26:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=I56s7UOENpBCgHHTxGoaQMOkdxWTrge/XTO2PHBeOAo=; b=uOWfGV4tQ4zAiRNLfbGlIUvcqTT0OMKjlpe/jrVkU9AAdKtbbhbOxPT8KK23ioiXb+ A7mmqxQLmKBU5IHAlNvqMHIMWRYtpSSp5rJo7+tDM/tM/JmVf+IUg/XlvD5m1xjDqoCD A9CIdu4Q9xXR1gKJOMRPmnepoN8NIYdWqV/agzhliTwVFxAHP9ypTeMxxCVy+cnizaF/ gm6oQReAk6wGixFSvSQsvDgi0poluGeXktqENqfiyivQI8teGrcamo89Yr3/BXn5x64U wSeBFfTmiheFcgL/bGTiqOvG48Lo/2xZrZ5oTG8S3WlpIAYl38xe8djMtjxwM3TLkZ1U EDqA==
X-Received: by 10.66.180.200 with SMTP id dq8mr68085340pac.104.1385987193569;  Mon, 02 Dec 2013 04:26:33 -0800 (PST)
Received: from [192.168.199.122] ([166.111.68.231]) by mx.google.com with ESMTPSA id ki1sm122286419pbd.1.2013.12.02.04.26.30 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Dec 2013 04:26:32 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=utf-8
From: Qi Sun <sunqi.csnet.thu@gmail.com>
In-Reply-To: <CAFGoqUOtzad1iNMrqs5vyy5wqewxw445Q_iAiKgYjgLvocR5EQ@mail.gmail.com>
Date: Mon, 2 Dec 2013 20:26:28 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <DEEB7D15-5356-4A9C-A899-9CBC6B14C326@gmail.com>
References: <489D13FBFA9B3E41812EA89F188F018E1AD98DE0@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADC2A5B@xmb-rcd-x04.cisco.com> <CAFGoqUMh-xT+GsJQNHGUcisqcphAVFZXnQ6ac+GXq76wBBiyYw@mail.gmail.com> <AC25F22F-A27C-40FC-B4AF-9EA886D973A6@gmail.com> <CAFGoqUOtzad1iNMrqs5vyy5wqewxw445Q_iAiKgYjgLvocR5EQ@mail.gmail.com>
To: Marcin Siodelski <msiodelski@gmail.com>
X-Mailer: Apple Mail (2.1085)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 - Respond by Dec 2, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 12:26:39 -0000

Hi Marcin,

On 2013-12-2, at =E4=B8=8B=E5=8D=885:32, Marcin Siodelski wrote:

>>> ISSUE 2
>>> In this sentence:
>>>=20
>>> "In the case that a new type of relay message is sent to a relay =
agent
>>>  but the relay agent doesn't recognize it, the message is put into a
>>>  Relay-forward message and sent to the server."
>>>=20
>>> Why "new type of relay message", not "new type of message"? I don't
>>> quite understand what the relay message is in this context.
>>=20
>> [Qi] A new type of relay message targets at the relay agent. If a =
relay agent recognizes the message, then it should consume the message. =
Otherwise, the relay just sends the message to the server (in a =
Relay-forward message), so that the server gets the information that =
this relay doesn't support the new relay agent message.
>> In Bullet (b), the message doesn't take the relay agent as the =
target.
>> If this part isn't clear enough, we can improve it.
>>=20
>=20
> Thanks for this explanation. Let me rephrase my question, because I
> was asking about slightly different thing....
>=20
> Would it still be ok if we had this text: "In the case that a new type
> of message is sent to a relay agent..... ", instead of "In the case
> that a new type of relay message is sent to a relay agent..."? Simply
> removed "relay". I don't understand how "relay message" is different
> from the "message" or "valid message".
>=20

Thanks for your patience. What I wanted to say was that the new type of =
message targets at the relay agent rather than the client/server. IMHO, =
if remove "relay", the relationship between this paragraph and the =
bullet (b) might be a little confusing.=20
How about this:

   In the case that a new type of message targets at a relay agent
   but the relay agent does not recognize it, ...

Would the expression be better?

Thanks,=20
Qi





From msiodelski@gmail.com  Mon Dec  2 04:38:03 2013
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3C371AE45C for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 04:38:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P1utPGnOUHLh for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 04:38:02 -0800 (PST)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 37C661AE343 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 04:38:02 -0800 (PST)
Received: by mail-pb0-f47.google.com with SMTP id um1so18706364pbc.6 for <dhcwg@ietf.org>; Mon, 02 Dec 2013 04:38:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=KXdUi3O99DzGVHLt8uKRgkOPr8mSeq5IM7YoC4nrDD8=; b=0+KrYykY7cgMHkGaQABO3FenFe0gbEE+9NagLn8taZiZAD6W1zPcQQjYs4A3rtZcn5 FAJRsZ74ZSYrGT0yRppBK3GN0lR1NUA/vrDIYhAjeZI23ghoEbtLgjVonxjZiu3lVWB7 qyMKLAL43RYvm1ls6ivHyhymBM9B3zlV2ium27VYUA+T0hgOOrwB8CShC8Wvz/sJKoca SbctbaYa2pYlwKmgeTLtipPy++pDg4D0eK/0l6oENfNbsQQRsPQokPLfmBkD1aIb9ouU WCdbV24DekTuslYd1h35SCLp9tuxIQ0hmvh0fy//We1rl95PT8YsCdRezy9PRI8t4oGz pKUA==
MIME-Version: 1.0
X-Received: by 10.66.149.37 with SMTP id tx5mr27898229pab.81.1385987880075; Mon, 02 Dec 2013 04:38:00 -0800 (PST)
Received: by 10.70.130.169 with HTTP; Mon, 2 Dec 2013 04:38:00 -0800 (PST)
In-Reply-To: <DEEB7D15-5356-4A9C-A899-9CBC6B14C326@gmail.com>
References: <489D13FBFA9B3E41812EA89F188F018E1AD98DE0@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADC2A5B@xmb-rcd-x04.cisco.com> <CAFGoqUMh-xT+GsJQNHGUcisqcphAVFZXnQ6ac+GXq76wBBiyYw@mail.gmail.com> <AC25F22F-A27C-40FC-B4AF-9EA886D973A6@gmail.com> <CAFGoqUOtzad1iNMrqs5vyy5wqewxw445Q_iAiKgYjgLvocR5EQ@mail.gmail.com> <DEEB7D15-5356-4A9C-A899-9CBC6B14C326@gmail.com>
Date: Mon, 2 Dec 2013 13:38:00 +0100
Message-ID: <CAFGoqUPoth6VbdX8hPZaeN4Hh5Fi7eBJXBhcO8NmqirQqePSvg@mail.gmail.com>
From: Marcin Siodelski <msiodelski@gmail.com>
To: Qi Sun <sunqi.csnet.thu@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 - Respond by Dec 2, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 12:38:04 -0000

On Mon, Dec 2, 2013 at 1:26 PM, Qi Sun <sunqi.csnet.thu@gmail.com> wrote:
>
> Hi Marcin,
>
> On 2013-12-2, at =E4=B8=8B=E5=8D=885:32, Marcin Siodelski wrote:
>
>>>> ISSUE 2
>>>> In this sentence:
>>>>
>>>> "In the case that a new type of relay message is sent to a relay agent
>>>>  but the relay agent doesn't recognize it, the message is put into a
>>>>  Relay-forward message and sent to the server."
>>>>
>>>> Why "new type of relay message", not "new type of message"? I don't
>>>> quite understand what the relay message is in this context.
>>>
>>> [Qi] A new type of relay message targets at the relay agent. If a relay=
 agent recognizes the message, then it should consume the message. Otherwis=
e, the relay just sends the message to the server (in a Relay-forward messa=
ge), so that the server gets the information that this relay doesn't suppor=
t the new relay agent message.
>>> In Bullet (b), the message doesn't take the relay agent as the target.
>>> If this part isn't clear enough, we can improve it.
>>>
>>
>> Thanks for this explanation. Let me rephrase my question, because I
>> was asking about slightly different thing....
>>
>> Would it still be ok if we had this text: "In the case that a new type
>> of message is sent to a relay agent..... ", instead of "In the case
>> that a new type of relay message is sent to a relay agent..."? Simply
>> removed "relay". I don't understand how "relay message" is different
>> from the "message" or "valid message".
>>
>
> Thanks for your patience. What I wanted to say was that the new type of m=
essage targets at the relay agent rather than the client/server. IMHO, if r=
emove "relay", the relationship between this paragraph and the bullet (b) m=
ight be a little confusing.
> How about this:
>
>    In the case that a new type of message targets at a relay agent
>    but the relay agent does not recognize it, ...
>
> Would the expression be better?
>

IMHO, that is much better. In the former case, the verb "send" makes
it ambiguous - message sent to a relay agent doesn't have to be
necessarily consumed/processed by relay, it could be forwarded. At
least this is how I read it. :-)

Marcin

From ogud@ogud.com  Mon Dec  2 05:14:04 2013
Return-Path: <ogud@ogud.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3E5A1AE21A for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 05:14:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I_RRWykK-Szk for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 05:14:02 -0800 (PST)
Received: from smtp82.ord1c.emailsrvr.com (smtp82.ord1c.emailsrvr.com [108.166.43.82]) by ietfa.amsl.com (Postfix) with ESMTP id B6D9A1ADF78 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 05:14:01 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 95ACB500CE; Mon,  2 Dec 2013 08:13:59 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 0F08350089;  Mon,  2 Dec 2013 08:13:56 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net>
Date: Mon, 2 Dec 2013 08:13:56 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <25AE7031-096A-4F01-B754-7FAC4D4F8E84@ogud.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net>
To: Hal Murray <hmurray@megapathdsl.net>
X-Mailer: Apple Mail (2.1510)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, Bernie Volz <volz@cisco.com>, Ted Lemon <ted.lemon@nominum.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 13:14:05 -0000

On Dec 1, 2013, at 11:47 PM, Hal Murray <hmurray@megapathdsl.net> wrote:

> Does DNS using DNSSEC return a specific error code for time-invalid?  =
Or just=20
> a generic didn't-work?
>=20

RCODE=3D=3DSERVFAIL,=20

> How close does the time have to be for DNSSEC to work?

somewhere between a month and an hour depending on what device is =
looking up
for X.509 this might be somewhere between a year and a minute=20
it all depends on how close to the edge the providers of Validatable =
Signatures still keep using them.=20


>=20
> Could this problem be solved by setting up a bank of NTP servers at =
well=20
> known IP Addresses?  Say, one next to each root DNS server.  If you =
tried to=20
> do that, I'd expect a serious problem would be overload because idiots =
would=20
> try to use them for normal NTP use rather than just getting off the =
ground. =20
> It might be possible to discourage that by making them return crappy =
time.
>=20

IFF there were enough NTP servers on a any cast addresss that might work =
most of the time.=20
The draft is proposing to do this via naturally distributed solution the =
local DHCP server or router for ND, thus eliminating the need
for any additional infrastructure, this is based on the assumption that =
these "servers" have decent idea what the current time is.=20

The problem in nutshell is that devices have to use their own time =
source or a distant one.=20
To me it seems having a local (i.e. on local network but off device) is =
a reasonable starting point to get to the great distant one.=20

>=20
> ted.lemon@nominum.com said:
>> As for the home router use model, it may be that what you really want =
is for
>> the home router to query for an FQDN-only DHCP option from the ISP =
DHCP
>> server, and then resolve that FQDN and respond to DHCP clients on the
>> homenet with an IP address.   Since the FQDN is not hard-coded, and =
the IP
>> address is (one hopes) resolved either at query time or when its TTL
>> expires, this ought to prevent a repeat of the firmware burn-in =
incident.=20
>=20
> Most ISPs already provide DNS servers for their customers.  How do =
their IP=20
> address get setup in home routers?  Could NTP servers piggyback on =
that=20
> mechanism if ISPs also provided NTP servers?
>=20
>=20

DHCP NAMESERVER option returns the IP address of the DNS resolvers,=20

	Olafur


From ogud@ogud.com  Mon Dec  2 05:20:39 2013
Return-Path: <ogud@ogud.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EACD1AE474 for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 05:20:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S2hiTNmCzKeG for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 05:20:37 -0800 (PST)
Received: from smtp114.ord1c.emailsrvr.com (smtp114.ord1c.emailsrvr.com [108.166.43.114]) by ietfa.amsl.com (Postfix) with ESMTP id 9C7A21AE428 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 05:20:37 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp7.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 67DCD1B8141; Mon,  2 Dec 2013 08:20:35 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp7.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 01EB81B810F;  Mon,  2 Dec 2013 08:20:34 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <A775B456-E8F6-4111-AFB3-B51BB92ABFC7@nominum.com>
Date: Mon, 2 Dec 2013 08:20:33 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <13CAC983-13D6-450E-B436-2E639B6FC751@ogud.com>
References: <20131201204227.7978.2067.idtracker@ietfa.amsl.com> <83842BD2-0261-472F-9CA1-AFBFB47EAD91@ogud.com> <C0A2F49F-7695-47E9-8AB0-7F94116437F9@nominum.com> <B0A571B5-438A-47AB-AAA4-00D3FC077E22@ogud.com> <331C154E-1A09-4BDD-A70A-AB67BEA2E1E8@nominum.com> <529BD4CF.6000408@ntp.org> <A775B456-E8F6-4111-AFB3-B51BB92ABFC7@nominum.com>
To: Ted Lemon <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1510)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, Bernie Volz <volz@cisco.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 13:20:39 -0000

On Dec 1, 2013, at 9:36 PM, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Dec 1, 2013, at 7:31 PM, Danny Mayer <mayer@ntp.org> wrote:
>> We need a joint agreement on how to deal with this between DHCP and =
NTP
>> Working Groups assuming that is a viable option in the first place.
>> RFC5908 was not a good indication of this.
>=20
> RFC 5908 got approved pretty much accidentally, without finishing the =
review process in the DHC working group.   It was a major screwup, and I =
don't precisely know how it happened.   It doesn't really do what you =
wanted, and it certainly doesn't do what we wanted.   I agree that this =
needs to be resolved, but the resolution has to be based on reasoning, =
not an instinctive reaction to past pain.
>=20
> I'm not even convinced that DHCP is the right way to distribute NTP =
server information.   I suspect Olafur may be thinking about the case =
that's more common at present, which is that an FQDN is hard-coded into =
the O.S. distribution, and resolved at startup time.   In that case, =
DHCP's ability to deliver NTP server IP addresses doesn't help.
>=20

> As for the home router use model, it may be that what you really want =
is for the home router to query for an FQDN-only DHCP option from the =
ISP DHCP server, and then resolve that FQDN and respond to DHCP clients =
on the homenet with an IP address.   Since the FQDN is not hard-coded, =
and the IP address is (one hopes) resolved either at query time or when =
its TTL expires, this ought to prevent a repeat of the firmware burn-in =
incident.
>=20


Strictly speaking there is no difference between OS burned in NTP server =
name and DHCP server provided NTP server name, both=20
require DNS resolution, root zone is signed, thus if the box wants to do =
DNSSEC validation as soon as it can, we end up with one of:=20
	disable DNSSEC=20
	false negative on validation=20

repeat for any protocol that wants to open TLS or IPSEC connection =
before NTP completes.=20
Giving out a NTP server address (as in IP address)  that is outside =
"local" net is not responsible behavior.

Right now for inexpensive boxes we have a choice of "real-bad" and =
"outstanding" time source, I'm advocating for something in the middle=20
i.e. quick-and-close time for the devices that do not keep time when =
off.=20

When been doing research on Open Recursive DNS Resolvers we keep finding =
more and more devices that answer all questions with=20
answers that are basically current time either in binary, or text. This =
to me implies that there is hidden need for quick-and-dirty time.=20

If you have not been following the changes in DNS, there is a push to =
move the resolution/validation to edge i.e. run resolver/validators on =
edge devices or even in applications as the "ISP" resolvers can not be =
counted on to do DNSSEC, and in many cases play games with answers.=20

	Olafur



From ogud@ogud.com  Mon Dec  2 05:47:06 2013
Return-Path: <ogud@ogud.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFD211AE476 for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 05:47:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tWjrFOPRXnpG for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 05:47:04 -0800 (PST)
Received: from smtp82.ord1c.emailsrvr.com (smtp82.ord1c.emailsrvr.com [108.166.43.82]) by ietfa.amsl.com (Postfix) with ESMTP id CA1BA1AE474 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 05:47:04 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 7B9DF50326; Mon,  2 Dec 2013 08:47:02 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id F16D55031A;  Mon,  2 Dec 2013 08:47:01 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <529C1A31.2080900@ntp.org>
Date: Mon, 2 Dec 2013 08:47:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org>
To: mayer@ntp.org
X-Mailer: Apple Mail (2.1510)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Hal Murray <hmurray@megapathdsl.net>, Ted Lemon <ted.lemon@nominum.com>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 13:47:07 -0000

On Dec 2, 2013, at 12:27 AM, Danny Mayer <mayer@ntp.org> wrote:

> On 12/1/2013 11:47 PM, Hal Murray wrote:
>> Does DNS using DNSSEC return a specific error code for time-invalid?  =
Or just=20
>> a generic didn't-work?
>>=20
>> How close does the time have to be for DNSSEC to work?
>>=20
>=20
> That's a question that should be asked in the dnsext WG mailing list
> (though technically the Working Group is now closed). Olafur and I
> (apart from Ted who is IETF area director) are probably the only ones =
on
> these lists who participate in that mailing list. Olafur was one of =
the
> cochairs of the DNS ext working group.
>=20
> The document does not describe the DNSSEC requirements for accurate =
time
> and probably should so that it can be assessed in that light.
> The ones I know about are RRSIG inception time and expiration time and
> then there are certificate expiration date-times.
>=20
> The proposal seems to suggest that a timestamp in 64-bit time_t be
> distributed by DHCP. I'm not sure why not a NTP timestamp instead.
> However most systems running a DNS server is likely to have a static
> address in the first place and that is what DHCP distributes as
> nameservers to query. Since they use static addresses do they
> participate in DHCP services at all? And who says that the DHCP server
> itself has accurate time?
>=20

Danny, Thanks for the kind introduction=20

The reason for time_t is the dhcp-client can feed that directly into =
following call:
	 settimeofday(const struct timeval *tp, const struct timezone =
*tzp)

If there is better construct I wold be happy to update the draft with =
that.=20

Be careful when you say "most systems running a DNS server"=20
are you talking about resolver or authoritative server. =20

In the second case you are right they are static and frequently well =
provisioned with good bandwidth, and=20
at boot time the system has good idea why the current time is, but for =
all practical purposes unless they are signing
on the fly they do not need accurate time.=20

ON THE OTHER HAND, resolvers and X.509 certificate checking is =
distributed and can take=20
place on any device. As I said in another message DNS resolution is =
being pushed to the edge=20
as devices that migrate between networks cannot count on the "local =
resolvers" to be "DNSSEC ready"=20

You are right we can not count on the DHCP server to have good time, =
thus any DHCP server answering=20
with the proposed option would need to make sure it has "decent current =
time", that is the reason I say in the
draft that the time should be within 10 minutes.=20
When playing with cheap home routers I discovered that the devices can =
easily drift an hour a day, if NTP is not
invoked regularly, most of these devices just use 'ntpdate' and =
frequently run it from startup script once.=20

>> Could this problem be solved by setting up a bank of NTP servers at =
well=20
>> known IP Addresses?  Say, one next to each root DNS server.  If you =
tried to=20
>> do that, I'd expect a serious problem would be overload because =
idiots would=20
>> try to use them for normal NTP use rather than just getting off the =
ground. =20
>> It might be possible to discourage that by making them return crappy =
time.
>>=20
>=20
> No, it would just overwhelm them. See the NIST time servers for an
> example of heavy load.
>=20
>>=20
>> ted.lemon@nominum.com said:
>>> As for the home router use model, it may be that what you really =
want is for
>>> the home router to query for an FQDN-only DHCP option from the ISP =
DHCP
>>> server, and then resolve that FQDN and respond to DHCP clients on =
the
>>> homenet with an IP address.   Since the FQDN is not hard-coded, and =
the IP
>>> address is (one hopes) resolved either at query time or when its TTL
>>> expires, this ought to prevent a repeat of the firmware burn-in =
incident.=20
>>=20
>> Most ISPs already provide DNS servers for their customers.  How do =
their IP=20
>> address get setup in home routers?  Could NTP servers piggyback on =
that=20
>> mechanism if ISPs also provided NTP servers?
>=20
> I wish they would provide NTP services in the same way. Unfortunately
> although most ISP's will have NTP servers they do not usually tell =
their
> customers about them and they certainly do not provide authenticated
> packets like autokey.
>=20
> Danny

Will a hotel network provide NTP server, and would you trust it?=20
Will a coffee shop provide NTP server ???=20

	Olafur


From mcr@sandelman.ca  Mon Dec  2 06:30:05 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D44B1AE49A for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 06:30:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VUDsEGGtBZHr for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 06:30:03 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 2C52B1AE498 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 06:30:03 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id C6B1C20168; Mon,  2 Dec 2013 10:43:10 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 2733E63B88; Mon,  2 Dec 2013 09:29:55 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 16E7563AEF; Mon,  2 Dec 2013 09:29:55 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg\@ietf.org WG" <dhcwg@ietf.org>
In-Reply-To: <529C1A31.2080900@ntp.org>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Mon, 02 Dec 2013 09:29:55 -0500
Message-ID: <25552.1385994595@sandelman.ca>
Sender: mcr@sandelman.ca
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 14:30:05 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


    > On 12/1/2013 11:47 PM, Hal Murray wrote:
    >> Does DNS using DNSSEC return a specific error code for time-invalid?
    >> Or just a generic didn't-work?
    >>=20
    >> How close does the time have to be for DNSSEC to work?

Sadly, DNSEXT did not (despite repeatedly trying to socialize this idea a
decade ago) give anything other than SERVERR when things fail.  That isn't =
to
say that it can be done, but there is no standard way to do this.

Time SHOULD be within 1 hour, but in practice, records are signed with
30-day periods, so as long as you aren't in error across that boundary,=20
you could be 12 or even 24 hours off.=20=20

Having your time in the past (trying to validate things in the future) is
likely the more common case -- it's also likely the less vulnerable
situation, as if someone is going to replay old data, they are likely going
to replay it from the real past, not, the future :-)

Many suggest to turn off time validation when a CPE router boots up until it
can validate enough DNS to get time records --- if one runs the DNSSEC for
the NTP server well, then the records will validate for years at a time.
If the CPE touches a file after getting valid time after booting, then the
CPE won't be back in 1970, it will know the time is at least as recent as
when it last validated time via DNSSEC-secured NTP.

Danny Mayer <mayer@ntp.org> wrote:
    > That's a question that should be asked in the dnsext WG mailing list
    > (though technically the Working Group is now closed). Olafur and I
    > (apart from Ted who is IETF area director) are probably the only ones
    > on these lists who participate in that mailing list. Olafur was one of
    > the cochairs of the DNS ext working group.

I have done all of the above.

    > The proposal seems to suggest that a timestamp in 64-bit time_t be
    > distributed by DHCP. I'm not sure why not a NTP timestamp instead.

I agree.

=2D-=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUpyZYIqHRg3pndX9AQKtDgQA0AnRJTofqIjdFIv0A7G61DY7TijAyHIf
9FRryTEpiI3xdCTNeO9IlUPTUwpaOfzmDfzDsARaC6gvrvEQ41/AugKtGyEY8Qlj
B673nSD0+W+tDfnIyW/rMVfk+XMnVAODMnEhpKAhCMSpt9z3j/1cUjNcob8+8157
8HSbboryiag=
=7HDw
-----END PGP SIGNATURE-----
--=-=-=--

From mcr@sandelman.ca  Mon Dec  2 06:30:57 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48BC31AE492 for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 06:30:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M4yGcH0v_ZUE for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 06:30:56 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id E107C1AE490 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 06:30:55 -0800 (PST)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id F3DB720168; Mon,  2 Dec 2013 10:44:04 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id A192563B88; Mon,  2 Dec 2013 09:30:50 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 7692963AEF; Mon,  2 Dec 2013 09:30:50 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Warner Losh <imp@bsdimp.com>
In-Reply-To: <F53087EB-C5E0-4305-929D-5BFEA3C266AD@bsdimp.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <D5CCC8A9-10FF-4D57-AB42-D39AB4D8730F@nominum.com> <F53087EB-C5E0-4305-929D-5BFEA3C266AD@bsdimp.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Mon, 02 Dec 2013 09:30:50 -0500
Message-ID: <25757.1385994650@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Hal Murray <hmurray@megapathdsl.net>, Ted Lemon <ted.lemon@nominum.com>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 14:30:57 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


Warner Losh <imp@bsdimp.com> wrote:
    > On Dec 1, 2013, at 10:13 PM, Ted Lemon wrote:
    >>> How close does the time have to be for DNSSEC to work?
    >>=20
    >> Closer than 1970.

    > So 5 years in the future is no problem?

Under strict DNSSEC rules, 5 years in the future is the same as 5 years in
the past.

=2D-=20
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works=20



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUpyZl4qHRg3pndX9AQJB0QQA4q0+j/QErXzqBRrO5WGByRviNEIVcj2o
YzTDsmbOanm/xVN9J1E0DacfKa1xKCUtmLeQPRZ8SgOsaJEPTXVysFb8BNWDD+YD
Xvergv68vcR3TEgTzbaVm97wCNjQQxVNhg2W+CsTXlJi34nILVlWDAvUrEW73AeI
TWjNmLqLrCY=
=4WuZ
-----END PGP SIGNATURE-----
--=-=-=--

From Ted.Lemon@nominum.com  Mon Dec  2 06:38:24 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22CDC1AE493 for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 06:38:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n6Ew2HaAjSKv for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 06:38:22 -0800 (PST)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id B4A491AE490 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 06:38:22 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKUpybXOZjn/yf5conA5Yjv/Fwo2HzUYO4@postini.com; Mon, 02 Dec 2013 06:38:20 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 9DDE21B82D0 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 06:38:19 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 7217E190043; Mon,  2 Dec 2013 06:38:19 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 2 Dec 2013 06:38:19 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <F53087EB-C5E0-4305-929D-5BFEA3C266AD@bsdimp.com>
Date: Mon, 2 Dec 2013 09:38:12 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <E96CB645-2197-4475-B760-71E8B686C023@nominum.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <D5CCC8A9-10FF-4D57-AB42-D39AB4D8730F@nominum.com> <F53087EB-C5E0-4305-929D-5BFEA3C266AD@bsdimp.com>
To: Warner Losh <imp@bsdimp.com>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 14:38:24 -0000

On Dec 2, 2013, at 1:44 AM, Warner Losh <imp@bsdimp.com> wrote:
> So 5 years in the future is no problem?

I was being mildly facetious, since this is a question that's pretty =
easy to answer, but difficult to answer precisely.   The answer depends =
on the zone configuration, but generally speaking "within days" is =
probably good enough.   See =
http://tools.ietf.org/html/rfc6781#section-4.4.2.2


From ghane0@gmail.com  Mon Dec  2 04:12:53 2013
Return-Path: <ghane0@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 440161AE351 for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 04:12:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xWzQo6E3DWKS for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 04:12:52 -0800 (PST)
Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 01F581AE343 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 04:12:51 -0800 (PST)
Received: by mail-pb0-f53.google.com with SMTP id ma3so18635958pbc.26 for <dhcwg@ietf.org>; Mon, 02 Dec 2013 04:12:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ZQ4IogRSQRzuxLogrj+B3LuXjhMBFim+6QpPRQy9b0g=; b=vhaQtzJCxfFiwTJSjIR3hD3lYn2+xP14g/mu8ElucP8VmHTh3s9DDkbUtwx1fQIPho lt2vSs0cv/R1Ske7QjoqsFT+vNP9CrlQBHJRfy1CXTcgjBPVnBZEAgcNoSllfnWz3Qoj QZQFK//Hb/QjsweDazXnwU4CqkXf1B25QJqvZ7rKh/lOqHc5Nvr0sG9AiYR8uajgIkId JlokGdS7s+menzfYdm+LTtAQlQqC1oFS5CmF8NIjvoRjVFHbL/Rfw98Yt7HCG9MGMjhJ wOlsFYyY8v9uMG7I0OdmyZWbTYJN+j5rP4zNWR5ih0lFn28KO+6kR2tsZLEHUVaBwV1r 71Mg==
X-Received: by 10.66.218.198 with SMTP id pi6mr67672766pac.107.1385986369597;  Mon, 02 Dec 2013 04:12:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.70.94.103 with HTTP; Mon, 2 Dec 2013 04:12:29 -0800 (PST)
In-Reply-To: <529BD4CF.6000408@ntp.org>
References: <20131201204227.7978.2067.idtracker@ietfa.amsl.com> <83842BD2-0261-472F-9CA1-AFBFB47EAD91@ogud.com> <C0A2F49F-7695-47E9-8AB0-7F94116437F9@nominum.com> <B0A571B5-438A-47AB-AAA4-00D3FC077E22@ogud.com> <331C154E-1A09-4BDD-A70A-AB67BEA2E1E8@nominum.com> <529BD4CF.6000408@ntp.org>
From: Sanjeev Gupta <ghane0@gmail.com>
Date: Mon, 2 Dec 2013 20:12:29 +0800
Message-ID: <CAHZk5Wf4u4vrfVVO=jyPK=dtwYYYQvvbnYZuRX1+f0fH_M97VQ@mail.gmail.com>
To: mayer@ntp.org
Content-Type: multipart/alternative; boundary=047d7b5d3ebe3937a804ec8c19b5
X-Mailman-Approved-At: Mon, 02 Dec 2013 06:48:06 -0800
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Ted Lemon <ted.lemon@nominum.com>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 12:12:53 -0000

--047d7b5d3ebe3937a804ec8c19b5
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Dec 2, 2013 at 8:31 AM, Danny Mayer <mayer@ntp.org> wrote:

> The problem is that for NTP
> DNS names are preferred over IP addresses because that allows a server
> maintainer to retire an NTP server.
>

With the "server" directive, once the FQDN is resolved by the system
resolver, ntpd will continue with tah IP address, even if the FQDN changes,
till it is restarted.

We are talking only about time at startup, right?

Then, I do not see any issues if the DHCP server specifies a IP address; as
long as the server administrator can manage to check that the IP is valid
(for a short time in the future).

1. The DHCP server administrator SHOULD specify the IP address of a valid
NTP server.

or

2. DHCP Server software MUST resolve the NTP server name to an IP address
before providing it to clients

Or am I missing something even more basic?

-- 
Sanjeev Gupta
+65 98551208     http://www.linkedin.com/in/ghane

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Mon, Dec 2, 2013 at 8:31 AM, Danny Mayer <span dir=3D"ltr">&lt;<a href=
=3D"mailto:mayer@ntp.org" target=3D"_blank">mayer@ntp.org</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">

<div id=3D":1nq" style=3D"overflow:hidden">The problem is that for NTP<br>
DNS names are preferred over IP addresses because that allows a server<br>
maintainer to retire an NTP server. </div></blockquote></div><br></div><div=
 class=3D"gmail_extra">With the &quot;server&quot; directive, once the FQDN=
 is resolved by the system resolver, ntpd will continue with tah IP address=
, even if the FQDN changes, till it is restarted.<br>

<br></div><div class=3D"gmail_extra">We are talking only about time at star=
tup, right?<br><br></div><div class=3D"gmail_extra">Then, I do not see any =
issues if the DHCP server specifies a IP address; as long as the server adm=
inistrator can manage to check that the IP is valid (for a short time in th=
e future). <br>

<br></div><div class=3D"gmail_extra">1. The DHCP server administrator SHOUL=
D specify the IP address of a valid NTP server.<br><br></div><div class=3D"=
gmail_extra">or<br><br></div><div class=3D"gmail_extra">2. DHCP Server soft=
ware MUST resolve the NTP server name to an IP address before providing it =
to clients<br>

</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Or am=
 I missing something even more basic?<br></div><div class=3D"gmail_extra"><=
br clear=3D"all"><div>-- <br>Sanjeev Gupta<br>+65 98551208=A0 =A0=A0 <a hre=
f=3D"http://www.linkedin.com/in/ghane">http://www.linkedin.com/in/ghane</a>=
</div>


</div></div>

--047d7b5d3ebe3937a804ec8c19b5--

From volz@cisco.com  Mon Dec  2 06:48:08 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B36F1AE482 for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 06:48:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.502
X-Spam-Level: 
X-Spam-Status: No, score=-9.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5pbKIdrPgHVU for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 06:48:06 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) by ietfa.amsl.com (Postfix) with ESMTP id 8618D1AE335 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 06:48:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7300; q=dns/txt; s=iport; t=1385995682; x=1387205282; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=itYU/g0U6dQqrffRXEHO/LbCcq5LgmqDbEC+M/LUJHc=; b=L0OKv+gR6Txh0YvZ5EAhYSz75K2iDVhqMdwcazTzQOXziwxHGdxWlUsH +JBAA82GxeA2XVQOxThJS6K50C9exs1n6rF3NPMyKzc/sfZZbvK8N5Mjt DnOxy6gbuGB69VHC4ejxJUJQi3MrhTkC0GyFpYRzhaeAP2bN7+8/sk+gH M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFAHSdnFKtJV2a/2dsb2JhbABZgwc4U4J6tWcYgQ0WdIIlAQEBBAEBASAROgQHDAQCAQYCDgMEAQEBAgIGHQMCAgIfBgsUAQgIAQEEAQ0FCIdnAw8NlAqbYYhVDYc0EwSBKYtOgWAxBwaCZTWBEwOWKY5FhTmBa4E+gio
X-IronPort-AV: E=Sophos;i="4.93,811,1378857600";  d="scan'208";a="3651079"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-8.cisco.com with ESMTP; 02 Dec 2013 14:47:43 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rB2ElgFA000342 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 2 Dec 2013 14:47:43 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0123.003; Mon, 2 Dec 2013 08:47:42 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Marcin Siodelski <msiodelski@gmail.com>, Qi Sun <sunqi.csnet.thu@gmail.com>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 - Respond by Dec 2, 2013
Thread-Index: Ac7kgW5Zu29batgdRjKYwweN6OdP2gHNcU1QAOKQ87oAEqMiAAAAZx4AAAlkqmA=
Date: Mon, 2 Dec 2013 14:47:41 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1ADC8C82@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1AD98DE0@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADC2A5B@xmb-rcd-x04.cisco.com> <CAFGoqUMh-xT+GsJQNHGUcisqcphAVFZXnQ6ac+GXq76wBBiyYw@mail.gmail.com> <AC25F22F-A27C-40FC-B4AF-9EA886D973A6@gmail.com> <CAFGoqUOtzad1iNMrqs5vyy5wqewxw445Q_iAiKgYjgLvocR5EQ@mail.gmail.com> <DEEB7D15-5356-4A9C-A899-9CBC6B14C326@gmail.com> <CAFGoqUPoth6VbdX8hPZaeN4Hh5Fi7eBJXBhcO8NmqirQqePSvg@mail.gmail.com>
In-Reply-To: <CAFGoqUPoth6VbdX8hPZaeN4Hh5Fi7eBJXBhcO8NmqirQqePSvg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.252.96]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 - Respond by Dec 2, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 14:48:08 -0000

SGk6DQoNCkFsc28sIHNob3VsZCB3ZSBwZXJoYXBzIGNsZWFuIHVwIChiKSBhcyB0byB3aGF0IGV4
YWN0bHkgY29uc3RpdHV0ZXMgJ3RhcmdldCBvZiB0aGUgbWVzc2FnZSc/IE9uZSBkZXRlcm1pbmF0
aW9uIG9mICd0YXJnZXQnIG1pZ2h0IGJlIHRoYXQgSVB2NiBkZXN0aW5hdGlvbiBhZGRyZXNzIGlu
IHRoZSBwYWNrZXQgaXMgb25lIG9mIHRoZSByZWxheSdzIHVuaWNhc3QgYWRkcmVzc2VzLiBBbm90
aGVyIHdvdWxkIGJlIHRoZSBtZXNzYWdlIHR5cGU/IEkgdGhpbmsgdGhpcyBkZWZpbml0aW9uIGlz
IHByaW1hcmlseSBiYXNlZCBvbiBtZXNzYWdlIHR5cGU/Pw0KDQoNCkhlcmUncyBhIGJ1bmNoIG9m
IG5pdHMgLyBzdWdnZXN0aW9ucyBmb3IgdGhlIGRvY3VtZW50Og0KDQpSZWdhcmRpbmcgdGhlIHNl
Y3Rpb24gNC4xIGlzc3VlOg0KDQogICBJbiB0aGUgY2FzZSB0aGF0IGEgbmV3IHR5cGUgb2YgcmVs
YXkgbWVzc2FnZSBpcyBzZW50IHRvIGEgcmVsYXkgYWdlbnQNCiAgIGJ1dCB0aGUgcmVsYXkgYWdl
bnQgZG9lc24ndCByZWNvZ25pemUgaXQsIHRoZSBtZXNzYWdlIGlzIHB1dCBpbnRvIGENCiAgIFJl
bGF5LWZvcndhcmQgbWVzc2FnZSBhbmQgc2VudCB0byB0aGUgc2VydmVyLiAgVGhlbiB0aGUgc2Vy
dmVyIGtub3dzDQogICB0aGUgcmVsYXkgYWdlbnQgZG9lc24ndCBzdXBwb3J0IHRoZSBuZXcgbWVz
c2FnZS4NCg0KSG93IGFib3V0Og0KDQogICBUaGlzIGRlZmluaXRpb24gb2Ygd2hhdCBjb25zdGl0
dXRlcyBhICd2YWxpZCBtZXNzYWdlJyBmb3IgdGhlIHJlbGF5IHdpbGwNCiAgIGF2b2lkIHRoZSBu
ZWVkIGZvciBjaGFuZ2VzIHRvIHJlbGF5IGFnZW50cyB3aGVuIG5ldyBjbGllbnQvc2VydmVyDQog
ICBtZXNzYWdlIHR5cGVzIGFyZSBkZWZpbmVkLiBIb3dldmVyLCBjaGFuZ2VzIHRvIHJlbGF5IGFn
ZW50cyB3aWxsIGJlDQogICByZXF1aXJlZCB3aGVuIGEgbmV3IG1lc3NhZ2UgdHlwZSBub3QgaW50
ZW5kZWQgdG8gYmUgZm9yd2FyZGVkDQogICB0b3dhcmRzIHRoZSBzZXJ2ZXIgaXMgZGVmaW5lZCAo
YW5kIHRoaXMgY2Fubm90IGJlIGF2b2lkZWQgYXMgdGhlIHJlbGF5DQogICBuZWVkcyB0aGUgbG9n
aWMgdG8gcHJvY2VzcyB0aGF0IG1lc3NhZ2UgYW55d2F5KS4NCg0KLS0tDQoNCjMuICBQcm9ibGVt
IFN0YXRlbWVudA0KDQogICBUaGUgcmVsYXkgYWdlbnQgaXMgYm91bmQgdG8gc2VuZCBhIG1lc3Nh
Z2UgZWl0aGVyIHRvIHRoZSBzZXJ2ZXIgb3IgdG8NCiAgIHRoZSBjbGllbnQuICBCdXQgUkZDMzMx
NSBkb2Vzbid0IGV4cGxpY2l0bHkgZGVzY3JpYmUgaG93IHRoZSByZWxheQ0KICAgYWdlbnQgY2Fu
IGZpbmQgb3V0IGl0IHNob3VsZCBzZW5kIGEgbWVzc2FnZSB0b3dhcmRzIHRoZSBzZXJ2ZXIgb3IN
CiAgIHRvd2FyZHMgdGhlIGNsaWVudC4NCg0KICAgQW5vdGhlciBpc3N1ZSBpcyB0aGF0LCBpdCdz
IG5vdCBzcGVjaWZpYyBpbiBSRkMzMzE1IGFib3V0IHdoYXQgYQ0KICAgcmVsYXkgYWdlbnQgc2hv
dWxkIGRvIGlmIGl0IGRvZXNuJ3QgcmVjb2duaXplIHRoZSByZWNlaXZlZCBtZXNzYWdlcy4NCiAg
IFRoZSByZWxheSBhZ2VudCBpc24ndCByZXF1aXJlZCB0byByZWxheSB0aGUgbWVzc2FnZXMsIG5v
ciBhZHZpc2VkIHRvDQogICBkcm9wIHRoZW0uDQoNCiAgIEluIGFkZGl0aW9uLCB0aGVyZSBpcyBu
byBzcGVjaWZpYyByZXF1aXJlbWVudCBvZiB0aGUgY2xpZW50IG9yIHNlcnZlcg0KICAgb24gZGVh
bGluZyB3aXRoIGFuIHVua25vd24gbWVzc2FnZSBpbiBSRkMzMzE1Lg0KDQpIb3cgYWJvdXQ6DQoN
CiAgIFRoZSByZWxheSBhZ2VudCBpcyBib3VuZCB0byBzZW5kIGEgbWVzc2FnZSBlaXRoZXIgdG8g
dGhlIHNlcnZlciBvciB0bw0KICAgdGhlIGNsaWVudC4gIEJ1dCBSRkMzMzE1IGRvZXNuJ3QgZXhw
bGljaXRseSBkZXNjcmliZSBob3cgdGhlIHJlbGF5DQogICBhZ2VudCBjYW4gZmluZCBvdXQgaWYg
aXQgc2hvdWxkIHNlbmQgYSBtZXNzYWdlIHRvd2FyZHMgdGhlIHNlcnZlciBvcg0KICAgdG93YXJk
cyB0aGUgY2xpZW50Lg0KDQogICBBbm90aGVyIGlzc3VlIGlzIHRoYXQgUkZDMzMxNSBpcyBub3Qg
c3BlY2lmaWMgYWJvdXQgd2hhdCBhDQogICByZWxheSBhZ2VudCBzaG91bGQgZG8gaWYgaXQgZG9l
cyBub3QgcmVjb2duaXplIGEgcmVjZWl2ZWQgbWVzc2FnZTsNCiAgIHRoZSByZWxheSBhZ2VudCBp
cyBub3QgcmVxdWlyZWQgdG8gcmVsYXkgdGhlIG1lc3NhZ2UsIG5vciBhZHZpc2VkIHRvDQogICBk
cm9wIHRoZSBtZXNzYWdlLiANCg0KICAgSW4gYWRkaXRpb24sIHRoZXJlIGlzIG5vIHNwZWNpZmlj
IHJlcXVpcmVtZW50IGZvciBkZWFsaW5nIHdpdGgNCiAgIHVua25vd24gbWVzc2FnZXMgYnkgdGhl
IGNsaWVudCBvciBzZXJ2ZXIgaW4gUkZDMzMxNS4NCg0KQW5kIHdoYXQgYWJvdXQgYWRkaW5nOg0K
DQogICAgQW5kIGl0IGlzIGV4cGVjdGVkIHRoYXQgbW9zdCBmdXR1cmUgREhDUHY2IG1lc3NhZ2Vz
IHdpbGwgbm90IGJlDQogICAgdXNlZCB0byBjb21tdW5pY2F0ZSBkaXJlY3RseSB3aXRoIHJlbGF5
IGFnZW50cyAodGhvdWdoIHRoZXkgbWF5DQogICAgbmVlZCB0byBiZSByZWxheWVkIGJ5IHJlbGF5
IGFnZW50cykuDQoNCg0KSW4gdGhlIHJlc3Qgb2YgdGhlIGRvY3VtZW50IChhcyBTaGVuZyBvdXRs
aW5lZCksIHBsZWFzZSByZXBsYWNlIG4ndCB3aXRoIG5vdCAoaS5lLiwgZG9lc24ndCBzaG91bGQg
YmUgcmVwbGFjZWQgYnkgZG9lcyBub3QpLg0KDQotIEJlcm5pZQ0KDQotLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLQ0KRnJvbTogZGhjd2cgW21haWx0bzpkaGN3Zy1ib3VuY2VzQGlldGYub3JnXSBP
biBCZWhhbGYgT2YgTWFyY2luIFNpb2RlbHNraQ0KU2VudDogTW9uZGF5LCBEZWNlbWJlciAwMiwg
MjAxMyA3OjM4IEFNDQpUbzogUWkgU3VuDQpDYzogZGhjd2dAaWV0Zi5vcmc7IEJlcm5pZSBWb2x6
ICh2b2x6KQ0KU3ViamVjdDogUmU6IFtkaGN3Z10gV0dMQyBmb3IgZHJhZnQtaWV0Zi1kaGMtZGhj
cHY2LXVua25vd24tbXNnLTAzIC0gUmVzcG9uZCBieSBEZWMgMiwgMjAxMw0KDQpPbiBNb24sIERl
YyAyLCAyMDEzIGF0IDE6MjYgUE0sIFFpIFN1biA8c3VucWkuY3NuZXQudGh1QGdtYWlsLmNvbT4g
d3JvdGU6DQo+DQo+IEhpIE1hcmNpbiwNCj4NCj4gT24gMjAxMy0xMi0yLCBhdCDkuIvljYg1OjMy
LCBNYXJjaW4gU2lvZGVsc2tpIHdyb3RlOg0KPg0KPj4+PiBJU1NVRSAyDQo+Pj4+IEluIHRoaXMg
c2VudGVuY2U6DQo+Pj4+DQo+Pj4+ICJJbiB0aGUgY2FzZSB0aGF0IGEgbmV3IHR5cGUgb2YgcmVs
YXkgbWVzc2FnZSBpcyBzZW50IHRvIGEgcmVsYXkgDQo+Pj4+IGFnZW50ICBidXQgdGhlIHJlbGF5
IGFnZW50IGRvZXNuJ3QgcmVjb2duaXplIGl0LCB0aGUgbWVzc2FnZSBpcyBwdXQgDQo+Pj4+IGlu
dG8gYSAgUmVsYXktZm9yd2FyZCBtZXNzYWdlIGFuZCBzZW50IHRvIHRoZSBzZXJ2ZXIuIg0KPj4+
Pg0KPj4+PiBXaHkgIm5ldyB0eXBlIG9mIHJlbGF5IG1lc3NhZ2UiLCBub3QgIm5ldyB0eXBlIG9m
IG1lc3NhZ2UiPyBJIGRvbid0IA0KPj4+PiBxdWl0ZSB1bmRlcnN0YW5kIHdoYXQgdGhlIHJlbGF5
IG1lc3NhZ2UgaXMgaW4gdGhpcyBjb250ZXh0Lg0KPj4+DQo+Pj4gW1FpXSBBIG5ldyB0eXBlIG9m
IHJlbGF5IG1lc3NhZ2UgdGFyZ2V0cyBhdCB0aGUgcmVsYXkgYWdlbnQuIElmIGEgcmVsYXkgYWdl
bnQgcmVjb2duaXplcyB0aGUgbWVzc2FnZSwgdGhlbiBpdCBzaG91bGQgY29uc3VtZSB0aGUgbWVz
c2FnZS4gT3RoZXJ3aXNlLCB0aGUgcmVsYXkganVzdCBzZW5kcyB0aGUgbWVzc2FnZSB0byB0aGUg
c2VydmVyIChpbiBhIFJlbGF5LWZvcndhcmQgbWVzc2FnZSksIHNvIHRoYXQgdGhlIHNlcnZlciBn
ZXRzIHRoZSBpbmZvcm1hdGlvbiB0aGF0IHRoaXMgcmVsYXkgZG9lc24ndCBzdXBwb3J0IHRoZSBu
ZXcgcmVsYXkgYWdlbnQgbWVzc2FnZS4NCj4+PiBJbiBCdWxsZXQgKGIpLCB0aGUgbWVzc2FnZSBk
b2Vzbid0IHRha2UgdGhlIHJlbGF5IGFnZW50IGFzIHRoZSB0YXJnZXQuDQo+Pj4gSWYgdGhpcyBw
YXJ0IGlzbid0IGNsZWFyIGVub3VnaCwgd2UgY2FuIGltcHJvdmUgaXQuDQo+Pj4NCj4+DQo+PiBU
aGFua3MgZm9yIHRoaXMgZXhwbGFuYXRpb24uIExldCBtZSByZXBocmFzZSBteSBxdWVzdGlvbiwg
YmVjYXVzZSBJIA0KPj4gd2FzIGFza2luZyBhYm91dCBzbGlnaHRseSBkaWZmZXJlbnQgdGhpbmcu
Li4uDQo+Pg0KPj4gV291bGQgaXQgc3RpbGwgYmUgb2sgaWYgd2UgaGFkIHRoaXMgdGV4dDogIklu
IHRoZSBjYXNlIHRoYXQgYSBuZXcgDQo+PiB0eXBlIG9mIG1lc3NhZ2UgaXMgc2VudCB0byBhIHJl
bGF5IGFnZW50Li4uLi4gIiwgaW5zdGVhZCBvZiAiSW4gdGhlIA0KPj4gY2FzZSB0aGF0IGEgbmV3
IHR5cGUgb2YgcmVsYXkgbWVzc2FnZSBpcyBzZW50IHRvIGEgcmVsYXkgYWdlbnQuLi4iPyANCj4+
IFNpbXBseSByZW1vdmVkICJyZWxheSIuIEkgZG9uJ3QgdW5kZXJzdGFuZCBob3cgInJlbGF5IG1l
c3NhZ2UiIGlzIA0KPj4gZGlmZmVyZW50IGZyb20gdGhlICJtZXNzYWdlIiBvciAidmFsaWQgbWVz
c2FnZSIuDQo+Pg0KPg0KPiBUaGFua3MgZm9yIHlvdXIgcGF0aWVuY2UuIFdoYXQgSSB3YW50ZWQg
dG8gc2F5IHdhcyB0aGF0IHRoZSBuZXcgdHlwZSBvZiBtZXNzYWdlIHRhcmdldHMgYXQgdGhlIHJl
bGF5IGFnZW50IHJhdGhlciB0aGFuIHRoZSBjbGllbnQvc2VydmVyLiBJTUhPLCBpZiByZW1vdmUg
InJlbGF5IiwgdGhlIHJlbGF0aW9uc2hpcCBiZXR3ZWVuIHRoaXMgcGFyYWdyYXBoIGFuZCB0aGUg
YnVsbGV0IChiKSBtaWdodCBiZSBhIGxpdHRsZSBjb25mdXNpbmcuDQo+IEhvdyBhYm91dCB0aGlz
Og0KPg0KPiAgICBJbiB0aGUgY2FzZSB0aGF0IGEgbmV3IHR5cGUgb2YgbWVzc2FnZSB0YXJnZXRz
IGF0IGEgcmVsYXkgYWdlbnQNCj4gICAgYnV0IHRoZSByZWxheSBhZ2VudCBkb2VzIG5vdCByZWNv
Z25pemUgaXQsIC4uLg0KPg0KPiBXb3VsZCB0aGUgZXhwcmVzc2lvbiBiZSBiZXR0ZXI/DQo+DQoN
CklNSE8sIHRoYXQgaXMgbXVjaCBiZXR0ZXIuIEluIHRoZSBmb3JtZXIgY2FzZSwgdGhlIHZlcmIg
InNlbmQiIG1ha2VzIGl0IGFtYmlndW91cyAtIG1lc3NhZ2Ugc2VudCB0byBhIHJlbGF5IGFnZW50
IGRvZXNuJ3QgaGF2ZSB0byBiZSBuZWNlc3NhcmlseSBjb25zdW1lZC9wcm9jZXNzZWQgYnkgcmVs
YXksIGl0IGNvdWxkIGJlIGZvcndhcmRlZC4gQXQgbGVhc3QgdGhpcyBpcyBob3cgSSByZWFkIGl0
LiA6LSkNCg0KTWFyY2luDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KZGhjd2cgbWFpbGluZyBsaXN0DQpkaGN3Z0BpZXRmLm9yZw0KaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kaGN3Zw0K

From mayer@ntp.org  Mon Dec  2 07:24:43 2013
Return-Path: <mayer@ntp.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 199031AE486 for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 07:24:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jRWWhNYPIlqM for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 07:24:41 -0800 (PST)
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by ietfa.amsl.com (Postfix) with ESMTP id 6648F1AE435 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 07:24:41 -0800 (PST)
Received: from [198.22.153.36] (helo=[10.2.64.86]) by mail1.ntp.org with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <mayer@ntp.org>) id 1VnVMP-000Dj4-RG; Mon, 02 Dec 2013 15:24:36 +0000
Message-ID: <529CA616.3010402@ntp.org>
Date: Mon, 02 Dec 2013 10:24:06 -0500
From: Danny Mayer <mayer@ntp.org>
Organization: NTP
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Olafur Gudmundsson <ogud@ogud.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com>
In-Reply-To: <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 198.22.153.36
X-SA-Exim-Rcpt-To: ogud@ogud.com, hmurray@megapathdsl.net, ted.lemon@nominum.com, ntpwg@lists.ntp.org, dhcwg@ietf.org, volz@cisco.com
X-SA-Exim-Mail-From: mayer@ntp.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Hal Murray <hmurray@megapathdsl.net>, Ted Lemon <ted.lemon@nominum.com>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mayer@ntp.org
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Dec 2013 15:24:43 -0000

On 12/2/2013 8:47 AM, Olafur Gudmundsson wrote:
> 
> On Dec 2, 2013, at 12:27 AM, Danny Mayer <mayer@ntp.org> wrote:
> 
>> On 12/1/2013 11:47 PM, Hal Murray wrote:
>>> Does DNS using DNSSEC return a specific error code for time-invalid?  Or just 
>>> a generic didn't-work?
>>>
>>> How close does the time have to be for DNSSEC to work?
>>>
>>
>> That's a question that should be asked in the dnsext WG mailing list
>> (though technically the Working Group is now closed). Olafur and I
>> (apart from Ted who is IETF area director) are probably the only ones on
>> these lists who participate in that mailing list. Olafur was one of the
>> cochairs of the DNS ext working group.
>>
>> The document does not describe the DNSSEC requirements for accurate time
>> and probably should so that it can be assessed in that light.
>> The ones I know about are RRSIG inception time and expiration time and
>> then there are certificate expiration date-times.
>>
>> The proposal seems to suggest that a timestamp in 64-bit time_t be
>> distributed by DHCP. I'm not sure why not a NTP timestamp instead.
>> However most systems running a DNS server is likely to have a static
>> address in the first place and that is what DHCP distributes as
>> nameservers to query. Since they use static addresses do they
>> participate in DHCP services at all? And who says that the DHCP server
>> itself has accurate time?
>>
> 
> Danny, Thanks for the kind introduction 
> 
> The reason for time_t is the dhcp-client can feed that directly into following call:
> 	 settimeofday(const struct timeval *tp, const struct timezone *tzp)
> 
> If there is better construct I wold be happy to update the draft with that. 
> 
> Be careful when you say "most systems running a DNS server" 
> are you talking about resolver or authoritative server.  
> 

I actually mostly meant resolvers and authorative servers are really no
different in the sense being discussed here.

> In the second case you are right they are static and frequently well provisioned with good bandwidth, and 
> at boot time the system has good idea why the current time is, but for all practical purposes unless they are signing
> on the fly they do not need accurate time. 
> 
> ON THE OTHER HAND, resolvers and X.509 certificate checking is distributed and can take 
> place on any device. As I said in another message DNS resolution is being pushed to the edge 
> as devices that migrate between networks cannot count on the "local resolvers" to be "DNSSEC ready" 
> 
I doubt that the number of "local resolvers" used by the general
populace that can support DNSSEC reach even .1% today, never mind
whether the server has it enabled.

> You are right we can not count on the DHCP server to have good time, thus any DHCP server answering 
> with the proposed option would need to make sure it has "decent current time", that is the reason I say in the
> draft that the time should be within 10 minutes. 
> When playing with cheap home routers I discovered that the devices can easily drift an hour a day, if NTP is not
> invoked regularly, most of these devices just use 'ntpdate' and frequently run it from startup script once. 
> 
>>> Could this problem be solved by setting up a bank of NTP servers at well 
>>> known IP Addresses?  Say, one next to each root DNS server.  If you tried to 
>>> do that, I'd expect a serious problem would be overload because idiots would 
>>> try to use them for normal NTP use rather than just getting off the ground.  
>>> It might be possible to discourage that by making them return crappy time.
>>>
>>
>> No, it would just overwhelm them. See the NIST time servers for an
>> example of heavy load.
>>
>>>
>>> ted.lemon@nominum.com said:
>>>> As for the home router use model, it may be that what you really want is for
>>>> the home router to query for an FQDN-only DHCP option from the ISP DHCP
>>>> server, and then resolve that FQDN and respond to DHCP clients on the
>>>> homenet with an IP address.   Since the FQDN is not hard-coded, and the IP
>>>> address is (one hopes) resolved either at query time or when its TTL
>>>> expires, this ought to prevent a repeat of the firmware burn-in incident. 
>>>
>>> Most ISPs already provide DNS servers for their customers.  How do their IP 
>>> address get setup in home routers?  Could NTP servers piggyback on that 
>>> mechanism if ISPs also provided NTP servers?
>>
>> I wish they would provide NTP services in the same way. Unfortunately
>> although most ISP's will have NTP servers they do not usually tell their
>> customers about them and they certainly do not provide authenticated
>> packets like autokey.
>>
>> Danny
> 
> Will a hotel network provide NTP server, and would you trust it? 
> Will a coffee shop provide NTP server ??? 
> 

I would consider them no better than the ISP's. They only provide basic
services and almost certainly not NTP. But then how many applications
out there will demand DNSSEC authenticated information? Generally there
is no API to specify that from an application. When this gets into
browser software and banks give DNSSEC authenticated addresses then it
might take off.

Danny


> 	Olafur
> 
> 
> 


From ogud@ogud.com  Mon Dec  2 07:31:58 2013
Return-Path: <ogud@ogud.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02DC81A1F62 for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 07:31:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id toHOVHjAOUp6 for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 07:31:55 -0800 (PST)
Received: from smtp98.ord1c.emailsrvr.com (smtp98.ord1c.emailsrvr.com [108.166.43.98]) by ietfa.amsl.com (Postfix) with ESMTP id AB06B1A1F65 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 07:31:55 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp5.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 495C11B00B1; Mon,  2 Dec 2013 10:31:53 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp5.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id BB2DA1B00B2;  Mon,  2 Dec 2013 10:31:52 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <529CA616.3010402@ntp.org>
Date: Mon, 2 Dec 2013 10:31:50 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D82E52A5-F0CF-4A0A-AE1B-0440CAAC8CE7@ogud.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <529CA616.3010402@ntp.org>
To: mayer@ntp.org
X-Mailer: Apple Mail (2.1510)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Hal Murray <hmurray@megapathdsl.net>, Ted Lemon <ted.lemon@nominum.com>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 15:31:58 -0000

On Dec 2, 2013, at 10:24 AM, Danny Mayer <mayer@ntp.org> wrote:

> On 12/2/2013 8:47 AM, Olafur Gudmundsson wrote:
>>=20
>> On Dec 2, 2013, at 12:27 AM, Danny Mayer <mayer@ntp.org> wrote:
>>=20
>>> On 12/1/2013 11:47 PM, Hal Murray wrote:
>>>> Does DNS using DNSSEC return a specific error code for =
time-invalid?  Or just=20
>>>> a generic didn't-work?
>>>>=20
>>>> How close does the time have to be for DNSSEC to work?
>>>>=20
>>>=20
>>> That's a question that should be asked in the dnsext WG mailing list
>>> (though technically the Working Group is now closed). Olafur and I
>>> (apart from Ted who is IETF area director) are probably the only =
ones on
>>> these lists who participate in that mailing list. Olafur was one of =
the
>>> cochairs of the DNS ext working group.
>>>=20
>>> The document does not describe the DNSSEC requirements for accurate =
time
>>> and probably should so that it can be assessed in that light.
>>> The ones I know about are RRSIG inception time and expiration time =
and
>>> then there are certificate expiration date-times.
>>>=20
>>> The proposal seems to suggest that a timestamp in 64-bit time_t be
>>> distributed by DHCP. I'm not sure why not a NTP timestamp instead.
>>> However most systems running a DNS server is likely to have a static
>>> address in the first place and that is what DHCP distributes as
>>> nameservers to query. Since they use static addresses do they
>>> participate in DHCP services at all? And who says that the DHCP =
server
>>> itself has accurate time?
>>>=20
>>=20
>> Danny, Thanks for the kind introduction=20
>>=20
>> The reason for time_t is the dhcp-client can feed that directly into =
following call:
>> 	 settimeofday(const struct timeval *tp, const struct timezone =
*tzp)
>>=20
>> If there is better construct I wold be happy to update the draft with =
that.=20
>>=20
>> Be careful when you say "most systems running a DNS server"=20
>> are you talking about resolver or authoritative server. =20
>>=20
>=20
> I actually mostly meant resolvers and authorative servers are really =
no
> different in the sense being discussed here.
>=20
>> In the second case you are right they are static and frequently well =
provisioned with good bandwidth, and=20
>> at boot time the system has good idea why the current time is, but =
for all practical purposes unless they are signing
>> on the fly they do not need accurate time.=20
>>=20
>> ON THE OTHER HAND, resolvers and X.509 certificate checking is =
distributed and can take=20
>> place on any device. As I said in another message DNS resolution is =
being pushed to the edge=20
>> as devices that migrate between networks cannot count on the "local =
resolvers" to be "DNSSEC ready"=20
>>=20
> I doubt that the number of "local resolvers" used by the general
> populace that can support DNSSEC reach even .1% today, never mind
> whether the server has it enabled.
>=20

Chrome and Firefox have DNSSEC validation libraries in testing.=20
Once they turn that on the numbers will jump.=20
X.509 cert checks happen on edge devices today in large numbers.=20
This is not just for DNSSEC this is for any device that wants to do time =
check before NTP can finish.=20


>> You are right we can not count on the DHCP server to have good time, =
thus any DHCP server answering=20
>> with the proposed option would need to make sure it has "decent =
current time", that is the reason I say in the
>> draft that the time should be within 10 minutes.=20
>> When playing with cheap home routers I discovered that the devices =
can easily drift an hour a day, if NTP is not
>> invoked regularly, most of these devices just use 'ntpdate' and =
frequently run it from startup script once.=20
>>=20
>>>> Could this problem be solved by setting up a bank of NTP servers at =
well=20
>>>> known IP Addresses?  Say, one next to each root DNS server.  If you =
tried to=20
>>>> do that, I'd expect a serious problem would be overload because =
idiots would=20
>>>> try to use them for normal NTP use rather than just getting off the =
ground. =20
>>>> It might be possible to discourage that by making them return =
crappy time.
>>>>=20
>>>=20
>>> No, it would just overwhelm them. See the NIST time servers for an
>>> example of heavy load.
>>>=20
>>>>=20
>>>> ted.lemon@nominum.com said:
>>>>> As for the home router use model, it may be that what you really =
want is for
>>>>> the home router to query for an FQDN-only DHCP option from the ISP =
DHCP
>>>>> server, and then resolve that FQDN and respond to DHCP clients on =
the
>>>>> homenet with an IP address.   Since the FQDN is not hard-coded, =
and the IP
>>>>> address is (one hopes) resolved either at query time or when its =
TTL
>>>>> expires, this ought to prevent a repeat of the firmware burn-in =
incident.=20
>>>>=20
>>>> Most ISPs already provide DNS servers for their customers.  How do =
their IP=20
>>>> address get setup in home routers?  Could NTP servers piggyback on =
that=20
>>>> mechanism if ISPs also provided NTP servers?
>>>=20
>>> I wish they would provide NTP services in the same way. =
Unfortunately
>>> although most ISP's will have NTP servers they do not usually tell =
their
>>> customers about them and they certainly do not provide authenticated
>>> packets like autokey.
>>>=20
>>> Danny
>>=20
>> Will a hotel network provide NTP server, and would you trust it?=20
>> Will a coffee shop provide NTP server ???=20
>>=20
>=20
> I would consider them no better than the ISP's. They only provide =
basic
> services and almost certainly not NTP. But then how many applications
> out there will demand DNSSEC authenticated information? Generally =
there
> is no API to specify that from an application. When this gets into
> browser software and banks give DNSSEC authenticated addresses then it
> might take off.
>=20
> Danny
>=20
See above,=20

	Olafur


From imp@bsdimp.com  Mon Dec  2 07:32:08 2013
Return-Path: <imp@bsdimp.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5DD31AE493 for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 07:32:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ts2EsTFCKlWd for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 07:32:07 -0800 (PST)
Received: from mail-ie0-f173.google.com (mail-ie0-f173.google.com [209.85.223.173]) by ietfa.amsl.com (Postfix) with ESMTP id D9F421A1F74 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 07:32:06 -0800 (PST)
Received: by mail-ie0-f173.google.com with SMTP id to1so20973068ieb.18 for <dhcwg@ietf.org>; Mon, 02 Dec 2013 07:32:04 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=9SR3GvhEptT54gn7lUwnPRYSCeME0P8YR+HWO1DQY/s=; b=Jm3iYALmVCjZFbSPNuYT95VbJpMYAH6+tTrdjVwfq61qsQOLpzikiqX/HL1UGqdqyK ogovGankamT9kVuFaaQ2+xn8yoC1nKWW8hulaMeNg5lZnUBwLWvllZVvdZs1lXGvCwvD E08+Is3EuGgH0DK9c0/1N/q7PG6O7KTy9ISPKf0DeuHNwucffpf2ppNrxkjaMkLhLqeL tE/o/HYLqbuy1rhRgdgm43R4k8Z3r8Aond3wmU7cwZ2WnZtHFvsjjiTObYuhGEQScYAJ fsBM9XZXxTn9zgp+wu5pwlMsFSWNHN5PaM25gjoNuhSg2hm+cyO6eHwshMd6b6qi3HvG tuFg==
X-Gm-Message-State: ALoCoQmBGlSV9uAiK61RY70wN4ZUoBiofxoiaO3eHleVyidaxe7ICDsE0H3/EiZLiVOfd0phasOV
X-Received: by 10.50.16.68 with SMTP id e4mr18460998igd.12.1385998324247; Mon, 02 Dec 2013 07:32:04 -0800 (PST)
Received: from 53.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id da14sm26843873igc.1.2013.12.02.07.32.03 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Dec 2013 07:32:03 -0800 (PST)
Sender: Warner Losh <wlosh@bsdimp.com>
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Warner Losh <imp@bsdimp.com>
In-Reply-To: <529CA616.3010402@ntp.org>
Date: Mon, 2 Dec 2013 08:32:02 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <529CA616.3010402@ntp.org>
To: mayer@ntp.org
X-Mailer: Apple Mail (2.1085)
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, Ted Lemon <ted.lemon@nominum.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 15:32:09 -0000

On Dec 2, 2013, at 8:24 AM, Danny Mayer wrote:
>> Danny, Thanks for the kind introduction=20
>>=20
>> The reason for time_t is the dhcp-client can feed that directly into =
following call:
>> 	 settimeofday(const struct timeval *tp, const struct timezone =
*tzp)

During a leap second, the value of time_t is not well defined because by =
definition leap seconds don't happen in time_t/POSIX time scale (don't =
happen -- well don't consume space in the time_t timescale is more =
pedantically correct). Obscure point likely worth noting...  But using a =
NTP time stamp doesn't save you, since during a leap second its value is =
well defined, but the same as another second (ntp distinguishes in bits =
set in other parts of the header). Assuming the tolerance for this =
application is >> 1s, this won't matter, but might be worth specifying =
that during a leap second, the value returned shall be either the value =
of the prior second or the value of the next second to make it conform =
to most current usage.

Warner


From volz@cisco.com  Mon Dec  2 08:54:38 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B89C41AD6D2 for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 08:54:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level: 
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cvckbQgMU5OW for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 08:54:36 -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 2A4FC1AD6D1 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 08:54:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=31702; q=dns/txt; s=iport; t=1386003274; x=1387212874; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=mdP7ANQ47/hU6FjAApPHojm7pwky8SG19SotM15uRX0=; b=C+XDa9qpD/R+827XIN/Q120OheFzUE23gxKRqpBBsWcOycYbfzljfnva oLx6rI5i3ycMMQU3AE1mqG2Fr1J3/1A6/qW1B/RPIDy254KyC45E76ioh wgZ3KSiu6dIC96+WQtM6Vy/qytH5T6+Jd8UmRIAdjF7C1G39WEbzOB73k 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AggFAEW6nFKtJXG//2dsb2JhbABZgkNEOFOCerVqGIENFnSCJQEBAQQBAQEgCkELEAIBBgIRBAEBCxYHAwICAh8GCxQJCAIEDgUIE4dUAw8NlDmbYYhjDYZiEwSMd4FgFhcEBgEGgmU1gRMDlimORYU5gWuBPoIq
X-IronPort-AV: E=Sophos;i="4.93,811,1378857600";  d="scan'208,217";a="288816830"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-6.cisco.com with ESMTP; 02 Dec 2013 16:54:33 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id rB2GsXSR027475 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 2 Dec 2013 16:54:33 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0123.003; Mon, 2 Dec 2013 10:54:32 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Qi Sun <sunqi.csnet.thu@gmail.com>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond	by Dec 9, 2013
Thread-Index: AQHO7yWSS0MmG+jVj0KJEABUOdok9ppBH2XQ
Date: Mon, 2 Dec 2013 16:54:32 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1ADC94F2@xmb-rcd-x04.cisco.com>
References: <CEBB74DD.9C090%ian.farrer@telekom.de> <124F1F54-5997-46D9-A6F1-54F94E3D6423@gmail.com> <5295FCDD.9000300@viagenie.ca> <51308BAA-5F33-44B9-AB72-6AE42BA5E11D@gmail.com> <5296356D.90405@viagenie.ca> <489D13FBFA9B3E41812EA89F188F018E1ADC24C4@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADC25C8@xmb-rcd-x04.cisco.com> <CAF+sHxHSrZ5zEXrn0RpZqCUcfJ3xiisgFYKLCo5adBcMP3rGzA@mail.gmail.com> <6D0BACEB-D945-413B-98D9-3333092F45F6@cisco.com> <CAF+sHxGCk0hG2U+qMc+b=uk90c+c-4_WTJp-mxLLe-Vx_tuwCQ@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1ADC41A3@xmb-rcd-x04.cisco.com> <F476551F-B235-4334-8A54-13E72984D1CF@gmail.com>
In-Reply-To: <F476551F-B235-4334-8A54-13E72984D1CF@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.252.96]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1ADC94F2xmbrcdx04ciscoc_"
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond	by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 16:54:38 -0000

--_000_489D13FBFA9B3E41812EA89F188F018E1ADC94F2xmbrcdx04ciscoc_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

UWk6DQoNClRoZXJlIGFyZSBubyBpc3N1ZXMgY2F1c2VkIGJ5IG5vdCBhZGRpbmcgdGhpcyBjYXBh
YmlsaXR5Lg0KDQpUaGUgYmVuZWZpdCwgYXQgdGhlIGNvc3Qgb2YgbW9yZSBjb21wbGV4aXR5LCB3
b3VsZCBiZSBmZXdlciBwYWNrZXRzIGJlaW5nIHByb2Nlc3NlZCBieSB0aGUg4oCYYXZhaWxhYmxl
4oCZIHNlcnZlcnMuDQoNCkkgd2FzIGp1c3QgcmFpc2luZyBpdCBhcyBhIHBvc3NpYmlsaXR5IGZv
ciB0aGUgV0cgdG8gY29uc2lkZXIuIEkgaGF2ZSBubyBpc3N1ZSBpZiB3ZSBkZWNpZGUgdGhhdCB0
aGUgYmVuZWZpdCBpcyBub3Qgd29ydGggdGhlIGNvc3QgKGFuZCB0aHVzIGxlYXZlIHRoaXMgY29t
cGxldGVseSBvdXQgb2YgdGhlIGRvY3VtZW50KS4NCg0KDQotICAgICAgICAgIEJlcm5pZQ0KDQpG
cm9tOiBkaGN3ZyBbbWFpbHRvOmRoY3dnLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBR
aSBTdW4NClNlbnQ6IE1vbmRheSwgRGVjZW1iZXIgMDIsIDIwMTMgMToxMyBBTQ0KVG86IEJlcm5p
ZSBWb2x6ICh2b2x6KQ0KQ2M6IGRoY3dnQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW2RoY3dnXSBX
R0xDIGZvciBkcmFmdC1pZXRmLWRoYy1kaGNwdjQtb3Zlci1kaGNwdjYtMDMgLSBSZXNwb25kIGJ5
IERlYyA5LCAyMDEzDQoNCg0KSGkgQmVybmllLA0KDQpUaGFua3MgZm9yIGNvbnNpZGVyaW5nIHRo
aXMuIEl0IGNvdWxkIG9wdGltaXplIHRoZSBESENQdjQgdW5pY2FzdCBjYXNlLCBidXQgbWF5IGJy
aW5nIGluIHNvbWUgY29tcGxleGl0eS4NCg0KSU1ITywgdGhpcyBpcyB0aGUgY3VycmVudCBtb2Rl
bDoNCg0KV2hlbiBESENQdjQgdW5pY2FzdCwgdGhlIDRvNiBjbGllbnQgc2VuZHMgdW5pY2FzdCBw
YWNrZXRzIHRvIHRoZSBhdmFpbGFibGUgc2VydmVycyAobGlzdGVkIGluIHRoZSA0bzYgU2VydmVy
IEFkZHJlc3Mgb3B0aW9uKSwgb2YgY291cnNlLCB3aXRoIHRoZSBVbmljYXN0IEZsYWcgc2V0LiBU
aGUgc2VydmVyIHRoYXQgd2FzIHNlbGVjdGVkIGJ5IHRoZSBjbGllbnQgd2lsbCByZXBseSB3aGls
ZSB0aGUgb3RoZXIgc2VydmVycyB3b3VsZCBzaWxlbnRseSBkcm9wIHRoZSBwYWNrZXRzLiBUaGVu
IHRoZSBjbGllbnQgd2lsbCBnZXQgcmVzcG9uc2UgZnJvbSB0aGUgZGVkaWNhdGVkIHNlcnZlci4N
Cg0KSSdtIG5vdCBzdXJlIGlmIHRoaXMgbW9kZWwgd291bGQgY2F1c2UgcG90ZW50aWFsIGlzc3Vl
cyAoaXQgd29ya3MsIElNSE8pLiBDb3VsZCB5b3UgcGxlYXNlIHBvaW50IG91dCBpZiBJIG1pc3Nl
ZCBhbnl0aGluZz8NCg0KVGhhbmtzLA0KUWkNCg0KT24gMjAxMy0xMS0yOSwgYXQg5LiK5Y2IMTI6
MjAsIEJlcm5pZSBWb2x6ICh2b2x6KSB3cm90ZToNCg0KDQpUaGUgU2VydmVyLVVuaWNhc3Qgb3B0
aW9uIChpZiB0aGlzIGlzIGFkb3B0ZWQpIHdvdWxkIGJlIGluIHRoZSBCT09UUkVQTFlWNiB3aGlj
aCBpcyBwcm9jZXNzZWQgYnkgdGhlIDRvNiBESENQIENsaWVudCBhbmQgZG9lcyBub3QgaW1wYWN0
IHRoZSBub3JtYWwgREhDUHY2IHRyYW5zYWN0aW9ucy4gKFRoZSA0bzYgREhDUCBDbGllbnQgd291
bGQgcmVxdWVzdCB0aGlzIGluIHRoZSBPUk8gaW4gdGhlIEJPT1RSRVFVRVNUVjYuKQ0KDQpJ4oCZ
bSBub3Qgc3VyZSBpZiB0aGlzIGlzIHdvcnRoIGl0LiBCdXQganVzdCBmaWd1cmVkIEnigJlkIHN1
Z2dlc3QgaXQuDQoNCi0gICAgICAgICAgQmVybmllDQoNCkZyb206IGRoY3dnIFttYWlsdG86ZGhj
d2ctYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIENvbmcgTGl1DQpTZW50OiBUaHVyc2Rh
eSwgTm92ZW1iZXIgMjgsIDIwMTMgMTA6NDQgQU0NClRvOiBCZXJuaWUgVm9seiAodm9seikNCkNj
OiBkaGN3Z0BpZXRmLm9yZzxtYWlsdG86ZGhjd2dAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogW2Ro
Y3dnXSBXR0xDIGZvciBkcmFmdC1pZXRmLWRoYy1kaGNwdjQtb3Zlci1kaGNwdjYtMDMgLSBSZXNw
b25kIGJ5IERlYyA5LCAyMDEzDQoNCkhpIEJlcm5pZSwNCg0KU29ycnksIEkgdGhvdWdodCB5b3Ug
d2VyZSB0YWxraW5nIGFib3V0IHJldXNlIDRvNiBTZXJ2ZXIgQWRkcmVzcyBvcHRpb24uDQoNCklm
IHJlZ3VsYXIgREhDUHY2IHByb2Nlc3MgaXMgbm90IGFmZmVjdGVkIGJ5IHJldXNpbmcgU2VydmVy
IFVuaWNhc3Qgb3B0aW9uLCBJIHRoaW5rIGl0J3MgYSBnb29kIHNvbHV0aW9uLg0KDQpDb25nDQoN
CjIwMTMvMTEvMjggQmVybmllIFZvbHogKHZvbHopIDx2b2x6QGNpc2NvLmNvbTxtYWlsdG86dm9s
ekBjaXNjby5jb20+Pg0KQ29uZywgSSBkb24ndCB1bmRlcnN0YW5kIHRoaXMuIFNlcnZlci11bmlj
YXN0IG9wdGlvbiBjYW4gb25seSBzcGVjaWZ5IG9uZSBhZGRyZXNzLg0KDQpUaGUgNG82IGNsaWVu
dCBoYXMgdHdvIGxpc3RzIC0gdGhlICJicm9hZGNhc3QiIGxpc3QgYW5kIHRoZSAidW5pY2FzdCIg
bGlzdC4gV2hlbiB2NCBwYWNrZXQgaXMgdG8gYmUgImJyb2FkY2FzdCIsIHRoZSAiYnJvYWRjYXN0
IiBsaXN0IGlzIHVzZWQuIFdoZW4gdW5pY2FzdCBhbmQgdGhlIHVuaWNhc3QgbGlzdCBpcyBub3Qg
ZW1wdHksIGl0IGlzIHVzZWQ7IG90aGVyd2lzZSBicm9hZGNhc3QgbGlzdCBpcyB1c2VkLiBCcm9h
ZGNhc3QgbGlzdCBjb21lcyBmcm9tIG5ldyA0bzYgb3B0aW9uIG9yIHRoZSB2NiBtdWx0aWNhc3Qg
YWRkcmVzcy4gVW5pY2FzdCBsaXN0IGlzIGVtcHR5IHVubGVzcyB0aGUgc2VydmVyJ3MgdjQgbGVh
c2UgdGhhdCB3YXMgc2VsZWN0ZWQgc2VudCBhIHNlcnZlci11bmljYXN0IG9wdGlvbi4NCg0KWWVz
LCBpZiB2NCBjbGllbnQgc2VuZHMgYnJvYWRjYXN0LCBwYWNrZXQgY291bGQgZ28gdG8gbXVsdGlw
bGUgc2VydmVycyBidXQgdGhhdCdzIHdoYXQgaGFwcGVucyB3aXRoIG5hdGl2ZSB2NC4NCg0KQW55
d2F5LCBqdXN0IGEgdGhvdWdodCB0byByZWR1Y2UgdHJhZmZpYyBmb3IgdjQgdW5pY2FzdCBjYXNl
Lg0KDQotIEJlcm5pZSAoZnJvbSBpUGFkKQ0KDQpPbiBOb3YgMjgsIDIwMTMsIGF0IDI6MzIgQU0s
ICJDb25nIExpdSIgPGdub2N1aWxAZ21haWwuY29tPG1haWx0bzpnbm9jdWlsQGdtYWlsLmNvbT4+
IHdyb3RlOg0KSGkgQmVybmllLA0KDQoyMDEzLzExLzI4IEJlcm5pZSBWb2x6ICh2b2x6KSA8dm9s
ekBjaXNjby5jb208bWFpbHRvOnZvbHpAY2lzY28uY29tPj4NCkhlcmUncyBhIHF1ZXN0aW9uIHdl
IGNhbiBhbHNvIHBvbmRlciAuLi4NCg0KU2hvdWxkIHdlIHBlcmhhcHMgYWxsb3cgdGhlIHNlcnZl
ciB0byBzZW5kIGJhY2sgdGhlIFNlcnZlci1VbmljYXN0IG9wdGlvbiB0byB0ZWxsIHRoZSA0bzYg
Q2xpZW50IHdoZXJlIGl0IGNhbiBzZW5kIHVuaWNhc3QgKERIQ1B2NCkgcGFja2V0cyB0bz8gVGhp
cyB3b3VsZCBhbGxvdyBESENQdjQgdW5pY2FzdCBwYWNrZXRzIHRvIGJlIHNlbnQgZGlyZWN0bHkg
dG8gdGhlIHNlcnZlciAob2YgY291cnNlIGluc2lkZSBhIEJPT1RSRVFVRVNUVjYgbWVzc2FnZSku
DQoNCkFzc3VtZSBJUHY2IGxlYXNlIHRpbWUgaXMgMTAwcywgYW5kIElQdjQgbGVhc2UgdGltZSBp
cyAyMDBzLiBUaGVuIHRoZSA0bzYgQ2xpZW50IHJlY2VpdmVzIGEgU2VydmVyLVVuaWNhc3Qgb3B0
aW9uICh3aGljaCBtYXkgY29udGFpbnMgMTAgdW5pY2FzdCBhZGRyZXNzZXMpIGV2ZXJ5IDEwMHMs
IGFuZCBhIFNlcnZlci1VbmljYXN0IG9wdGlvbiAod2hpY2ggY29udGFpbnMgMSB1bmljYXN0IGFk
ZHJlc3MpIGV2ZXJ5IDIwMHMuIEkgdGhpbmsgaXQgYWRkcyBtb3JlIGNvbXBsZXhpdHkgZm9yIGNs
aWVudCB0byBkZWFsIHdpdGggdGhlIHNhbWUgb3B0aW9uIGZyb20gZGlmZmVyZW50IHNlcnZlcnMg
KERIQ1B2NiAvIERIQ1A0bzYpLg0KDQpCZXN0IFJlZ2FyZHMsDQpDb25nDQpfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KDQpkaGN3ZyBtYWlsaW5nIGxpc3QN
CmRoY3dnQGlldGYub3JnPG1haWx0bzpkaGN3Z0BpZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vZGhjd2cNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCmRoY3dnIG1haWxpbmcgbGlzdA0KZGhjd2dAaWV0Zi5vcmc8
bWFpbHRvOmRoY3dnQGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9kaGN3Zw0KDQo=

--_000_489D13FBFA9B3E41812EA89F188F018E1ADC94F2xmbrcdx04ciscoc_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6eD0idXJuOnNjaGVtYXMtbWljcm9z
b2Z0LWNvbTpvZmZpY2U6ZXhjZWwiIHhtbG5zOm09Imh0dHA6Ly9zY2hlbWFzLm1pY3Jvc29mdC5j
b20vb2ZmaWNlLzIwMDQvMTIvb21tbCIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnL1RSL1JFQy1o
dG1sNDAiPg0KPGhlYWQ+DQo8bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVR5cGUiIGNvbnRlbnQ9
InRleHQvaHRtbDsgY2hhcnNldD11dGYtOCI+DQo8bWV0YSBuYW1lPSJHZW5lcmF0b3IiIGNvbnRl
bnQ9Ik1pY3Jvc29mdCBXb3JkIDE0IChmaWx0ZXJlZCBtZWRpdW0pIj4NCjxiYXNlIGhyZWY9Ingt
bXNnOi8vMzMvIj48c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseTpXaW5nZGluZ3M7DQoJcGFub3NlLTE6NSAwIDAgMCAwIDAgMCAwIDAg
MDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJNUyBNaW5jaG8iOw0KCXBhbm9zZS0xOjIg
MiA2IDkgNCAyIDUgOCAzIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiTVMgTWluY2hv
IjsNCglwYW5vc2UtMToyIDIgNiA5IDQgMiA1IDggMyA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1m
YW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIg
NDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQE1TIE1pbmNobyI7DQoJcGFub3NlLTE6
MiAyIDYgOSA0IDIgNSA4IDMgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJIZWl0aSBT
QyI7DQoJcGFub3NlLTE6MCAwIDAgMCAwIDAgMCAwIDAgMDt9DQovKiBTdHlsZSBEZWZpbml0aW9u
cyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46
MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQt
ZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVy
bGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29y
YXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0K
CXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlv
bjp1bmRlcmxpbmU7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0YXRlLCBkaXYuTXNvQWNldGF0
ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IkJhbGxvb24gVGV4
dCBDaGFyIjsNCgltYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6OC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMtc2VyaWYiO30NCnAuTXNvTGlz
dFBhcmFncmFwaCwgbGkuTXNvTGlzdFBhcmFncmFwaCwgZGl2Lk1zb0xpc3RQYXJhZ3JhcGgNCgl7
bXNvLXN0eWxlLXByaW9yaXR5OjM0Ow0KCW1hcmdpbi10b3A6MGluOw0KCW1hcmdpbi1yaWdodDow
aW47DQoJbWFyZ2luLWJvdHRvbTowaW47DQoJbWFyZ2luLWxlZnQ6LjVpbjsNCgltYXJnaW4tYm90
dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3
IFJvbWFuIiwic2VyaWYiO30NCnNwYW4uYXBwbGUtc3R5bGUtc3Bhbg0KCXttc28tc3R5bGUtbmFt
ZTphcHBsZS1zdHlsZS1zcGFuO30NCnNwYW4uYXBwbGUtY29udmVydGVkLXNwYWNlDQoJe21zby1z
dHlsZS1uYW1lOmFwcGxlLWNvbnZlcnRlZC1zcGFjZTt9DQpzcGFuLkJhbGxvb25UZXh0Q2hhcg0K
CXttc28tc3R5bGUtbmFtZToiQmFsbG9vbiBUZXh0IENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0
eTo5OTsNCgltc28tc3R5bGUtbGluazoiQmFsbG9vbiBUZXh0IjsNCglmb250LWZhbWlseToiVGFo
b21hIiwic2Fucy1zZXJpZiI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjENCgl7bXNvLXN0eWxlLXR5cGU6
cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCglj
b2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1v
bmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41
aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNl
Y3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi8qIExpc3QgRGVmaW5pdGlvbnMgKi8NCkBs
aXN0IGwwDQoJe21zby1saXN0LWlkOjEwNzEzNDI0MzE7DQoJbXNvLWxpc3QtdHlwZTpoeWJyaWQ7
DQoJbXNvLWxpc3QtdGVtcGxhdGUtaWRzOjE3ODY2OTI2NDQgODMwMTE5MDY2IDY3Njk4NjkxIDY3
Njk4NjkzIDY3Njk4Njg5IDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3Njk4NjkxIDY3Njk4
NjkzO30NCkBsaXN0IGwwOmxldmVsMQ0KCXttc28tbGV2ZWwtc3RhcnQtYXQ6MjsNCgltc28tbGV2
ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6LTsNCgltc28tbGV2ZWwt
dGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1p
bmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJbXNv
LWZhcmVhc3QtZm9udC1mYW1pbHk6Q2FsaWJyaTsNCgltc28tYmlkaS1mb250LWZhbWlseToiVGlt
ZXMgTmV3IFJvbWFuIjt9DQpAbGlzdCBsMDpsZXZlbDINCgl7bXNvLWxldmVsLW51bWJlci1mb3Jt
YXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7
DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsN
Cglmb250LWZhbWlseToiQ291cmllciBOZXciLCJzZXJpZiI7fQ0KQGxpc3QgbDA6bGV2ZWwzDQoJ
e21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJ
bXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0
Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3Qg
bDA6bGV2ZWw0DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwt
dGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1w
b3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpTeW1ib2w7
fQ0KQGxpc3QgbDA6bGV2ZWw1DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCglt
c28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1u
dW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6
IkNvdXJpZXIgTmV3Iiwic2VyaWYiO30NCkBsaXN0IGwwOmxldmVsNg0KCXttc28tbGV2ZWwtbnVt
YmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWIt
c3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVu
dDotLjI1aW47DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwwOmxldmVsNw0KCXtt
c28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1z
by1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsN
Cgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwwOmxl
dmVsOA0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6
bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9u
OmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyIs
InNlcmlmIjt9DQpAbGlzdCBsMDpsZXZlbDkNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVs
bGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCglt
c28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZv
bnQtZmFtaWx5OldpbmdkaW5nczt9DQpvbA0KCXttYXJnaW4tYm90dG9tOjBpbjt9DQp1bA0KCXtt
YXJnaW4tYm90dG9tOjBpbjt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0K
PG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwh
W2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9
ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlv
dXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0i
Ymx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0Qi
PlFpOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7
Y29sb3I6IzFGNDk3RCI+VGhlcmUgYXJlIG5vIGlzc3VlcyBjYXVzZWQgYnkgbm90IGFkZGluZyB0
aGlzIGNhcGFiaWxpdHkuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1z
ZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5UaGUgYmVuZWZpdCwgYXQgdGhlIGNvc3Qgb2YgbW9y
ZSBjb21wbGV4aXR5LCB3b3VsZCBiZSBmZXdlciBwYWNrZXRzIGJlaW5nIHByb2Nlc3NlZCBieSB0
aGUg4oCYYXZhaWxhYmxl4oCZIHNlcnZlcnMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0Qi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5JIHdhcyBqdXN0IHJhaXNpbmcg
aXQgYXMgYSBwb3NzaWJpbGl0eSBmb3IgdGhlIFdHIHRvIGNvbnNpZGVyLiBJIGhhdmUgbm8gaXNz
dWUgaWYgd2UgZGVjaWRlIHRoYXQgdGhlIGJlbmVmaXQgaXMgbm90IHdvcnRoIHRoZSBjb3N0IChh
bmQgdGh1cyBsZWF2ZSB0aGlzIGNvbXBsZXRlbHkNCiBvdXQgb2YgdGhlIGRvY3VtZW50KS48bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJ0ZXh0LWluZGVudDotLjI1aW47bXNv
LWxpc3Q6bDAgbGV2ZWwxIGxmbzEiPjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdub3Jl
Ij4tPHNwYW4gc3R5bGU9ImZvbnQ6Ny4wcHQgJnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4m
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsNCjwv
c3Bhbj48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7
Y29sb3I6IzFGNDk3RCI+QmVybmllPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTti
b3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJv
bTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gZGhjd2cgW21haWx0bzpk
aGN3Zy1ib3VuY2VzQGlldGYub3JnXQ0KPGI+T24gQmVoYWxmIE9mIDwvYj5RaSBTdW48YnI+DQo8
Yj5TZW50OjwvYj4gTW9uZGF5LCBEZWNlbWJlciAwMiwgMjAxMyAxOjEzIEFNPGJyPg0KPGI+VG86
PC9iPiBCZXJuaWUgVm9seiAodm9seik8YnI+DQo8Yj5DYzo8L2I+IGRoY3dnQGlldGYub3JnPGJy
Pg0KPGI+U3ViamVjdDo8L2I+IFJlOiBbZGhjd2ddIFdHTEMgZm9yIGRyYWZ0LWlldGYtZGhjLWRo
Y3B2NC1vdmVyLWRoY3B2Ni0wMyAtIFJlc3BvbmQgYnkgRGVjIDksIDIwMTM8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMy41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVpdGkgU0Mm
cXVvdDssJnF1b3Q7c2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPkhpIEJlcm5pZSw8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEzLjVwdDtmb250LWZhbWlseTomcXVvdDtIZWl0aSBTQyZxdW90Oywm
cXVvdDtzZXJpZiZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMy41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVpdGkgU0MmcXVvdDssJnF1b3Q7c2VyaWYm
cXVvdDs7Y29sb3I6YmxhY2siPlRoYW5rcyBmb3IgY29uc2lkZXJpbmcgdGhpcy4gSXQgY291bGQg
b3B0aW1pemUgdGhlIERIQ1B2NCB1bmljYXN0IGNhc2UsIGJ1dCBtYXkgYnJpbmcgaW4gc29tZSBj
b21wbGV4aXR5LiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTMuNXB0O2ZvbnQtZmFt
aWx5OiZxdW90O0hlaXRpIFNDJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEzLjVwdDtmb250LWZhbWlseTomcXVvdDtI
ZWl0aSBTQyZxdW90OywmcXVvdDtzZXJpZiZxdW90Oztjb2xvcjpibGFjayI+SU1ITywgdGhpcyBp
cyB0aGUgY3VycmVudCBtb2RlbDo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEzLjVwdDtmb250
LWZhbWlseTomcXVvdDtIZWl0aSBTQyZxdW90OywmcXVvdDtzZXJpZiZxdW90Oztjb2xvcjpibGFj
ayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMy41cHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7SGVpdGkgU0MmcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPldoZW4gREhD
UHY0IHVuaWNhc3QsIHRoZSA0bzYgY2xpZW50IHNlbmRzIHVuaWNhc3QgcGFja2V0cyB0byB0aGUg
YXZhaWxhYmxlIHNlcnZlcnMgKGxpc3RlZCBpbiB0aGUgNG82IFNlcnZlciBBZGRyZXNzIG9wdGlv
biksIG9mIGNvdXJzZSwgd2l0aCB0aGUgVW5pY2FzdCBGbGFnIHNldC4NCiBUaGUgc2VydmVyIHRo
YXQgd2FzIHNlbGVjdGVkIGJ5IHRoZSBjbGllbnQgd2lsbCByZXBseSB3aGlsZSB0aGUgb3RoZXIg
c2VydmVycyB3b3VsZCBzaWxlbnRseSBkcm9wIHRoZSBwYWNrZXRzLiBUaGVuIHRoZSBjbGllbnQg
d2lsbCBnZXQgcmVzcG9uc2UgZnJvbSB0aGUgZGVkaWNhdGVkIHNlcnZlci4mbmJzcDs8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEzLjVwdDtmb250LWZhbWlseTomcXVvdDtIZWl0aSBTQyZxdW90
OywmcXVvdDtzZXJpZiZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMy41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVpdGkgU0MmcXVvdDssJnF1b3Q7c2Vy
aWYmcXVvdDs7Y29sb3I6YmxhY2siPkknbSBub3Qgc3VyZSBpZiB0aGlzIG1vZGVsIHdvdWxkIGNh
dXNlIHBvdGVudGlhbCBpc3N1ZXMgKGl0IHdvcmtzLCBJTUhPKS4gQ291bGQgeW91IHBsZWFzZSBw
b2ludCBvdXQgaWYgSSBtaXNzZWQgYW55dGhpbmc/ICZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTMuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlaXRpIFNDJnF1b3Q7LCZxdW90O3Nlcmlm
JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEzLjVw
dDtmb250LWZhbWlseTomcXVvdDtIZWl0aSBTQyZxdW90OywmcXVvdDtzZXJpZiZxdW90Oztjb2xv
cjpibGFjayI+VGhhbmtzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTMuNXB0Ij48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEzLjVwdDtmb250LWZhbWlseTomcXVvdDtIZWl0aSBTQyZxdW90OywmcXVvdDtzZXJp
ZiZxdW90Oztjb2xvcjpibGFjayI+UWk8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiAyMDEzLTExLTI5
LCBhdCA8c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7TVMgTWluY2hvJnF1b3Q7Ij7kuIrl
jYg8L3NwYW4+MTI6MjAsIEJlcm5pZSBWb2x6ICh2b2x6KSB3cm90ZTo8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGJyPg0KPGJyPg0KPG86cD48L286cD48L3A+
DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90Oztjb2xvcjojMUY0OTdEIj5UaGUgU2VydmVyLVVuaWNhc3Qgb3B0aW9uIChpZiB0aGlz
IGlzIGFkb3B0ZWQpIHdvdWxkIGJlIGluIHRoZSBCT09UUkVQTFlWNiB3aGljaCBpcyBwcm9jZXNz
ZWQgYnkgdGhlIDRvNiBESENQIENsaWVudCBhbmQgZG9lcyBub3QgaW1wYWN0IHRoZSBub3JtYWwg
REhDUHY2IHRyYW5zYWN0aW9ucy4NCiAoVGhlIDRvNiBESENQIENsaWVudCB3b3VsZCByZXF1ZXN0
IHRoaXMgaW4gdGhlIE9STyBpbiB0aGUgQk9PVFJFUVVFU1RWNi4pPC9zcGFuPjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90Oztjb2xvcjojMUY0OTdEIj5J4oCZbSBub3Qgc3VyZSBpZiB0aGlzIGlzIHdvcnRoIGl0
LiBCdXQganVzdCBmaWd1cmVkIEnigJlkIHN1Z2dlc3QgaXQuPC9zcGFuPjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0idGV4dC1pbmRlbnQ6LS4yNWluIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7
Y29sb3I6IzFGNDk3RCI+LTwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjcuMHB0O2NvbG9y
OiMxRjQ5N0QiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOzxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj48
L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkJlcm5pZTwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj4mbmJzcDs8L3NwYW4+
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGNsYXNzPSJh
cHBsZS1jb252ZXJ0ZWQtc3BhY2UiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4mbmJzcDs8
L3NwYW4+PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5kaGN3Zw0KIFs8YSBocmVm
PSJtYWlsdG86ZGhjd2ctYm91bmNlc0BpZXRmLm9yZyI+bWFpbHRvOmRoY3dnLWJvdW5jZXNAaWV0
Zi5vcmc8L2E+XTxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bh
bj48Yj5PbiBCZWhhbGYgT2Y8c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNwYWNlIj4mbmJz
cDs8L3NwYW4+PC9iPkNvbmcgTGl1PGJyPg0KPGI+U2VudDo8L2I+PHNwYW4gY2xhc3M9ImFwcGxl
LWNvbnZlcnRlZC1zcGFjZSI+Jm5ic3A7PC9zcGFuPlRodXJzZGF5LCBOb3ZlbWJlciAyOCwgMjAx
MyAxMDo0NCBBTTxicj4NCjxiPlRvOjwvYj48c3BhbiBjbGFzcz0iYXBwbGUtY29udmVydGVkLXNw
YWNlIj4mbmJzcDs8L3NwYW4+QmVybmllIFZvbHogKHZvbHopPGJyPg0KPGI+Q2M6PC9iPjxzcGFu
IGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj48YSBocmVmPSJtYWls
dG86ZGhjd2dAaWV0Zi5vcmciPmRoY3dnQGlldGYub3JnPC9hPjxicj4NCjxiPlN1YmplY3Q6PC9i
PjxzcGFuIGNsYXNzPSJhcHBsZS1jb252ZXJ0ZWQtc3BhY2UiPiZuYnNwOzwvc3Bhbj5SZTogW2Ro
Y3dnXSBXR0xDIGZvciBkcmFmdC1pZXRmLWRoYy1kaGNwdjQtb3Zlci1kaGNwdjYtMDMgLSBSZXNw
b25kIGJ5IERlYyA5LCAyMDEzPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SGkgQmVybmllLDxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+U29ycnksIEkgdGhvdWdodCB5b3Ugd2VyZSB0YWxraW5nIGFib3V0IHJldXNlIDRvNiBTZXJ2
ZXIgQWRkcmVzcyBvcHRpb24uPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPklmIHJlZ3VsYXIg
REhDUHY2IHByb2Nlc3MgaXMgbm90IGFmZmVjdGVkIGJ5IHJldXNpbmcmbmJzcDs8c3BhbiBzdHls
ZT0iY29sb3I6YmxhY2siPlNlcnZlciBVbmljYXN0IG9wdGlvbiwgSSB0aGluayBpdCdzIGEgZ29v
ZCBzb2x1dGlvbi48L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJjb2xvcjpibGFjayI+Q29uZzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+
DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjIwMTMvMTEvMjgg
QmVybmllIFZvbHogKHZvbHopICZsdDs8YSBocmVmPSJtYWlsdG86dm9sekBjaXNjby5jb20iIHRh
cmdldD0iX2JsYW5rIj52b2x6QGNpc2NvLmNvbTwvYT4mZ3Q7PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkNvbmcsIEkgZG9u
J3QgdW5kZXJzdGFuZCB0aGlzLiBTZXJ2ZXItdW5pY2FzdCBvcHRpb24gY2FuIG9ubHkgc3BlY2lm
eSBvbmUgYWRkcmVzcy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhlIDRvNiBjbGllbnQg
aGFzIHR3byBsaXN0cyAtIHRoZSAmcXVvdDticm9hZGNhc3QmcXVvdDsgbGlzdCBhbmQgdGhlICZx
dW90O3VuaWNhc3QmcXVvdDsgbGlzdC4gV2hlbiB2NCBwYWNrZXQgaXMgdG8gYmUgJnF1b3Q7YnJv
YWRjYXN0JnF1b3Q7LCB0aGUgJnF1b3Q7YnJvYWRjYXN0JnF1b3Q7IGxpc3QgaXMgdXNlZC4gV2hl
biB1bmljYXN0IGFuZCB0aGUgdW5pY2FzdCBsaXN0IGlzIG5vdCBlbXB0eSwgaXQgaXMgdXNlZDsg
b3RoZXJ3aXNlIGJyb2FkY2FzdCBsaXN0IGlzIHVzZWQuDQogQnJvYWRjYXN0IGxpc3QgY29tZXMg
ZnJvbSBuZXcgNG82IG9wdGlvbiBvciB0aGUgdjYgbXVsdGljYXN0IGFkZHJlc3MuIFVuaWNhc3Qg
bGlzdCBpcyBlbXB0eSB1bmxlc3MgdGhlIHNlcnZlcidzIHY0IGxlYXNlIHRoYXQgd2FzIHNlbGVj
dGVkIHNlbnQgYSBzZXJ2ZXItdW5pY2FzdCBvcHRpb24uPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPlllcywgaWYgdjQgY2xpZW50IHNlbmRzIGJyb2FkY2FzdCwgcGFja2V0IGNvdWxkIGdvIHRv
IG11bHRpcGxlIHNlcnZlcnMgYnV0IHRoYXQncyB3aGF0IGhhcHBlbnMgd2l0aCBuYXRpdmUgdjQu
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFueXdheSwganVzdCBhIHRob3VnaHQgdG8gcmVk
dWNlIHRyYWZmaWMgZm9yIHY0IHVuaWNhc3QgY2FzZS48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+LSBCZXJuaWUgKGZyb20gaVBhZCk8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8
ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJv
dHRvbToxMi4wcHQiPjxicj4NCk9uIE5vdiAyOCwgMjAxMywgYXQgMjozMiBBTSwgJnF1b3Q7Q29u
ZyBMaXUmcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzpnbm9jdWlsQGdtYWlsLmNvbSIgdGFyZ2V0
PSJfYmxhbmsiPmdub2N1aWxAZ21haWwuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0
b206NS4wcHQiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SGkg
QmVybmllLDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjIwMTMvMTEvMjggQmVybmllIFZvbHogKHZvbHopICZsdDs8YSBo
cmVmPSJtYWlsdG86dm9sekBjaXNjby5jb20iIHRhcmdldD0iX2JsYW5rIj52b2x6QGNpc2NvLmNv
bTwvYT4mZ3Q7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5IZXJlJ3MgYSBxdWVzdGlvbiB3ZSBjYW4gYWxzbyBwb25kZXIgLi4uPGJyPg0KPGJyPg0K
U2hvdWxkIHdlIHBlcmhhcHMgYWxsb3cgdGhlIHNlcnZlciB0byBzZW5kIGJhY2sgdGhlIFNlcnZl
ci1VbmljYXN0IG9wdGlvbiB0byB0ZWxsIHRoZSA0bzYgQ2xpZW50IHdoZXJlIGl0IGNhbiBzZW5k
IHVuaWNhc3QgKERIQ1B2NCkgcGFja2V0cyB0bz8gVGhpcyB3b3VsZCBhbGxvdyBESENQdjQgdW5p
Y2FzdCBwYWNrZXRzIHRvIGJlIHNlbnQgZGlyZWN0bHkgdG8gdGhlIHNlcnZlciAob2YgY291cnNl
IGluc2lkZSBhIEJPT1RSRVFVRVNUVjYgbWVzc2FnZSkuPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Bc3N1
bWUgSVB2NiBsZWFzZSB0aW1lIGlzIDEwMHMsIGFuZCBJUHY0IGxlYXNlIHRpbWUgaXMgMjAwcy4g
VGhlbiB0aGUgNG82IENsaWVudCByZWNlaXZlcyBhJm5ic3A7PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90OyI+U2VydmVyLVVuaWNhc3Qgb3B0aW9uICh3aGljaCBtYXkgY29udGFpbnMgMTAgdW5pY2Fz
dCBhZGRyZXNzZXMpIGV2ZXJ5IDEwMHMsIGFuZCZuYnNwOzwvc3Bhbj5hJm5ic3A7PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7
c2Fucy1zZXJpZiZxdW90OyI+U2VydmVyLVVuaWNhc3QNCiBvcHRpb24gKHdoaWNoIGNvbnRhaW5z
IDEgdW5pY2FzdCBhZGRyZXNzKSBldmVyeSAyMDBzLiBJIHRoaW5rIGl0IGFkZHMgbW9yZSZuYnNw
O2NvbXBsZXhpdHkmbmJzcDtmb3IgY2xpZW50IHRvIGRlYWwgd2l0aCB0aGUgc2FtZSBvcHRpb24g
ZnJvbSBkaWZmZXJlbnQgc2VydmVycyAoREhDUHY2IC8gREhDUDRvNikuPC9zcGFuPjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZh
bWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5CZXN0IFJlZ2Fy
ZHMsPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+Q29uZzwvc3Bh
bj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHls
ZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX188bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48YnI+DQpkaGN3ZyBtYWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJtYWls
dG86ZGhjd2dAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5kaGN3Z0BpZXRmLm9yZzwvYT48YnI+
DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RoY3dnIiB0
YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9kaGN3
ZzwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90
ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEzLjVwdDtmb250LWZhbWlseTomcXVvdDtIZWl0aSBT
QyZxdW90OywmcXVvdDtzZXJpZiZxdW90OyI+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX188YnI+DQpkaGN3ZyBtYWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJt
YWlsdG86ZGhjd2dAaWV0Zi5vcmciPmRoY3dnQGlldGYub3JnPC9hPjxicj4NCjxhIGhyZWY9Imh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZGhjd2ciPmh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vZGhjd2c8L2E+PG86cD48L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_489D13FBFA9B3E41812EA89F188F018E1ADC94F2xmbrcdx04ciscoc_--

From Ted.Lemon@nominum.com  Mon Dec  2 09:13:00 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E063D1ACCE6 for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 09:13:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A_rqZ5fMdmzy for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 09:12:59 -0800 (PST)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id 797F91ACCDF for <dhcwg@ietf.org>; Mon,  2 Dec 2013 09:12:59 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKUpy/mUX6aOleJ8LcGEtqIWAwWQeaDE9c@postini.com; Mon, 02 Dec 2013 09:12:57 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 03A4C1B82EF for <dhcwg@ietf.org>; Mon,  2 Dec 2013 09:12:56 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id DE797190043; Mon,  2 Dec 2013 09:12:55 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 2 Dec 2013 09:12:55 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com>
Date: Mon, 2 Dec 2013 12:12:48 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <4AA650D3-2AD2-4C83-8450-DC3926AC9416@nominum.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <529CA616.3010402@ntp.org> <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com>
To: Warner Losh <imp@bsdimp.com>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 17:13:01 -0000

On Dec 2, 2013, at 10:32 AM, Warner Losh <imp@bsdimp.com> wrote:
> Assuming the tolerance for this application is >> 1s, this won't =
matter, but might be worth specifying that during a leap second, the =
value returned shall be either the value of the prior second or the =
value of the next second to make it conform to most current usage.

I think the expectation is that the time will be updated with a more =
accurate mechanism later, and an error of 1s is not worth worrying about =
for typical devices, so this is almost certainly overkill.


From imp@bsdimp.com  Mon Dec  2 10:13:04 2013
Return-Path: <imp@bsdimp.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42CE41AD73F for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 10:13:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 87Ltki_yO_eP for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 10:13:02 -0800 (PST)
Received: from mail-ie0-f181.google.com (mail-ie0-f181.google.com [209.85.223.181]) by ietfa.amsl.com (Postfix) with ESMTP id 8AA171AD8F3 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 10:13:02 -0800 (PST)
Received: by mail-ie0-f181.google.com with SMTP id e14so20811581iej.26 for <dhcwg@ietf.org>; Mon, 02 Dec 2013 10:13:00 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=cfYwbFBhUBk+5kYSFEOqd73pn2n2nOvfZ+S7Tc8+O7A=; b=czj7pICTqG2zyhWPDZsOjdw4TIqGi/zWmBdYsZykWcXupMFThFkv+H8bbDGwxdEQxm 43TdtbyaPvbRyikMgbx2vDbY1L2Na1sI3gXQSUt1J1rarFZWAiJyG5EGHRt8OPrnW/SI fejhuzPqwpzuQ3wQ3ohWSllDpfRmSGID8elRlli/JHCo9WxZHT+7+yf3hXqnbtF5w+1A Y0CK6uF5unvv6KfI+MuU4g3YHp1Xwh68mDjk9ydHvdPSZxVTzOh454JIZke9d/4sIwKu BybfMAriUyzCrNuIm1hNiYcxsLlGJZBACK36Vh9yQzwQonOknnlK+EEGTvr9lKHhUDdg AafQ==
X-Gm-Message-State: ALoCoQmFODEIy4iYDSPvtd5DyilmVYgFtJPWtaQFvJqYJ97AlgeCfD1Vbhjhqnci/Ip+gVRpvbav
X-Received: by 10.42.42.132 with SMTP id t4mr1929976ice.90.1386007980059; Mon, 02 Dec 2013 10:13:00 -0800 (PST)
Received: from fusionlt2834a.int.fusionio.com ([209.117.142.2]) by mx.google.com with ESMTPSA id x5sm67786946iga.6.2013.12.02.10.12.59 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Dec 2013 10:12:59 -0800 (PST)
Sender: Warner Losh <wlosh@bsdimp.com>
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Warner Losh <imp@bsdimp.com>
In-Reply-To: <4AA650D3-2AD2-4C83-8450-DC3926AC9416@nominum.com>
Date: Mon, 2 Dec 2013 11:12:57 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7C1A1F32-EED7-4990-A550-DB66BAB6AAD4@bsdimp.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <529CA616.3010402@ntp.org> <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com> <4AA650D3-2AD2-4C83-8450-DC3926AC9416@nominum.com>
To: Ted Lemon <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1085)
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 18:13:04 -0000

On Dec 2, 2013, at 10:12 AM, Ted Lemon wrote:

> On Dec 2, 2013, at 10:32 AM, Warner Losh <imp@bsdimp.com> wrote:
>> Assuming the tolerance for this application is >> 1s, this won't =
matter, but might be worth specifying that during a leap second, the =
value returned shall be either the value of the prior second or the =
value of the next second to make it conform to most current usage.
>=20
> I think the expectation is that the time will be updated with a more =
accurate mechanism later, and an error of 1s is not worth worrying about =
for typical devices, so this is almost certainly overkill.

This isn't to prevent an error of a second, but to bound the error to a =
second by adopting the main work arounds that are in practice today =
which do that.

Warner


From otroan@employees.org  Mon Dec  2 11:21:47 2013
Return-Path: <otroan@employees.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D249B1AC4A7 for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 11:21:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7NQvfdxpo0-s for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 11:21:47 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id A4BF71AD94A for <dhcwg@ietf.org>; Mon,  2 Dec 2013 11:21:46 -0800 (PST)
X-Files: signature.asc : 496
X-IronPort-AV: E=Sophos;i="4.93,812,1378857600"; d="asc'?scan'208";a="954840"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by aer-iport-2.cisco.com with ESMTP; 02 Dec 2013 19:21:43 +0000
Received: from dhcp-10-61-106-42.cisco.com (dhcp-10-61-106-42.cisco.com [10.61.106.42]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rB2JLaPb014294 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 2 Dec 2013 19:21:38 GMT
Content-Type: multipart/signed; boundary="Apple-Mail=_0F034E42-4B7C-489A-8B33-1E31834185CA"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com>
Date: Mon, 2 Dec 2013 20:21:36 +0100
Message-Id: <3219ECB2-F220-403B-984B-7254677528DE@employees.org>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
X-Mailer: Apple Mail (2.1822)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 19:21:48 -0000

--Apple-Mail=_0F034E42-4B7C-489A-8B33-1E31834185CA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> Folks, the authors of draft-ietf-dhc-dhcpv4-over-dhcpv6-03 =
(http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-03.txt) =
believe it is ready for working group last call. Please review this =
draft and indicate whether or not you feel it is ready to be published. =
Your input is important! Please respond by Dec 9th, 2013.

I do not support publication of this document.
I believe that using DHCPv4 as currently specified (RFC2131, RFC5107, =
RFC3456, RFC3046) is sufficient also for A+P softwire tunnels.

RFC7040 references DHCPv4 over IPv6. is this working group also going to =
specify this alternative transport?

cheers,
Ole


--Apple-Mail=_0F034E42-4B7C-489A-8B33-1E31834185CA
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJSnN3AAAoJEFuJXizso86g36MIAKLXlooS4TVtD7jPKtNP1YhP
sPFxkbjdWCS6lPGS7O7q5WMcqYyD3xYgWX9VwOKxOpXHEn7uzlSFsFB/AttQEqZg
mSiqfO/0JyXPPBTBR6OPt+0vDFJH0Y4mYKVRPL6QR7IfET8MyoYHOnxiSWvTNMiq
LurOtha2fHAhoB1qkYgb/ONlO0SAup3u9BGQAJdbg7W6fEx4gCltJUmY0qfCyi9V
DCc8B7Sfpp2NqSsNRIL11eA44yiIdQ1vueifItWoiF8Nu9aSAv0JJaRCNPtCawP4
tEzRMdCrHGKWorLHBKYNUQx0vbgYTbfM7HDP+2AP6rIHcqkde+SxYtnvluMhiTo=
=4p7B
-----END PGP SIGNATURE-----

--Apple-Mail=_0F034E42-4B7C-489A-8B33-1E31834185CA--

From stenn@stenn.ntp.org  Mon Dec  2 12:01:46 2013
Return-Path: <stenn@stenn.ntp.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06ABB1ADEB4 for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 12:01:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iHoAVBxwqaoO for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 12:01:44 -0800 (PST)
Received: from stenn.ntp.org (stenn.ntp.org [149.20.68.30]) by ietfa.amsl.com (Postfix) with ESMTP id 7917C1ADF4B for <dhcwg@ietf.org>; Mon,  2 Dec 2013 12:01:34 -0800 (PST)
Received: from localhost.ntp.org ([::1] helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1VnZdi-0000fA-CY; Mon, 02 Dec 2013 19:58:42 +0000
From: Harlan Stenn <stenn@ntp.org>
To: Warner Losh <imp@bsdimp.com>
In-reply-to: <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <529CA616.3010402@ntp.org> <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com>
Comments: In-reply-to Warner Losh <imp@bsdimp.com> message dated "Mon, 02 Dec 2013 08:32:02 -0700."
X-Mailer: MH-E 7.4.2; nmh 1.5; XEmacs 21.4 (patch 22)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Mon, 02 Dec 2013 19:58:42 +0000
Message-Id: <E1VnZdi-0000fA-CY@stenn.ntp.org>
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, Ted Lemon <ted.lemon@nominum.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 20:01:46 -0000

Warner Losh writes:
>>> The reason for time_t is the dhcp-client can feed that directly into
>>> following call: settimeofday(const struct timeval *tp, const struct
>>> timezone *tzp)
> 
> During a leap second, the value of time_t is not well defined because
> by definition leap seconds don't happen in time_t/POSIX time scale
> (don't happen -- well don't consume space in the time_t timescale is
> more pedantically correct). Obscure point likely worth noting...  But
> using a NTP time stamp doesn't save you, since during a leap second
> its value is well defined, but the same as another second (ntp
> distinguishes in bits set in other parts of the header). Assuming the
> tolerance for this application is >> 1s, this won't matter, but might
> be worth specifying that during a leap second, the value returned
> shall be either the value of the prior second or the value of the next
> second to make it conform to most current usage.

It's actually fuzzier than that, and this situation (which is handled
differently with ntpd under unix, ntpd under windows, and on systems
that "smear" the leap second over a longer period) is one of the cases
handled by the General Timestamp API project at Network Time Foundation,
described at http://nwtime.org/projects/timestamp-api/ .

H

From Ted.Lemon@nominum.com  Mon Dec  2 12:05:02 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA3601ADF2F for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 12:05:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0adEJbkB_E-S for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 12:05:01 -0800 (PST)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by ietfa.amsl.com (Postfix) with ESMTP id 60B221ADEB4 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 12:05:01 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKUpzn6zXwoFOqgyEugn96ByyxsQOChN7r@postini.com; Mon, 02 Dec 2013 12:04:59 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 21D961B82DD for <dhcwg@ietf.org>; Mon,  2 Dec 2013 12:04:59 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 03B63190043; Mon,  2 Dec 2013 12:04:59 -0800 (PST)
Received: from [192.168.1.3] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 2 Dec 2013 12:04:58 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <20131202185648.91031406060@ip-64-139-1-69.sjc.megapath.net>
Date: Mon, 2 Dec 2013 15:04:54 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <19044894-42C6-498C-88E5-85FCAE4C5F00@nominum.com>
References: <20131202185648.91031406060@ip-64-139-1-69.sjc.megapath.net>
To: Hal Murray <hmurray@megapathdsl.net>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 20:05:03 -0000

On Dec 2, 2013, at 1:56 PM, Hal Murray <hmurray@megapathdsl.net> wrote:
> ted.lemon@nominum.com said:
> [Context is NTP servers next to root DNS servers.]
>> History suggests otherwise.   If an IP address is hardcoded, it will =
get
>> pummeled by devices that are too dumb to give up.=20
>=20
> That's why I was suggesting a crappy clock.  Can we get something that =
is=20
> crappy enough that nobody would use it for anything other than getting =
off=20
> the ground yet still good enough for DNSSEC to work?

No.   Think about this seriously.   Who is going to tweak this?   The =
end-user?   This isn't realistic.   We had millions of home gateways =
DDOSing a university NTP server for years because the router vendor =
burned the IP address of the NTP server into the firmware.   I doubt =
anybody got decent time out of this arrangement, but nevertheless it =
persisted.

> Are there two layers of DHCP?  ISP to home router and home router to =
PC.

Yes.

> If ISPs ran NTP servers, say next to their DNS servers, could DHCP =
provide IP=20
> Addresses for both DNS and NTP servers over both hops?

Yes.

> Is it reasonable to trust an ISP's NTP servers?

See my first response on this thread: =
http://www.ietf.org/mail-archive/web/dhcwg/current/msg15039.html



From imp@bsdimp.com  Mon Dec  2 12:09:13 2013
Return-Path: <imp@bsdimp.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FA881AD8D5 for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 12:09:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X2jfgJzPf_Aq for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 12:09:11 -0800 (PST)
Received: from mail-ie0-f173.google.com (mail-ie0-f173.google.com [209.85.223.173]) by ietfa.amsl.com (Postfix) with ESMTP id BBE3B1ADEC4 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 12:09:11 -0800 (PST)
Received: by mail-ie0-f173.google.com with SMTP id to1so22177209ieb.32 for <dhcwg@ietf.org>; Mon, 02 Dec 2013 12:09:09 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=nD9qyZRQWP+8a0aK7r3rOhfixl0Br4i8b0ZCbbROZ5g=; b=WFj2FBRfxWeW4rszf9eD8hRhlKjoYZKzv8RVoohee/Dsmxspgwcal/43Jz6vwrQXu5 t8i1zff8HdN+xxjlCcqWrm77qfz8hLhFFtMB2VPiZ5qT8zIqc7S1JpOYFZoMPslD2gO5 Nq3F4CjM4olRhKapnKjtmmcSa0UMuMlMKIL8lTFXNgZDqdexcBi7dgameBUTweQK0zSB 3IUxU1QJBMJHyc5jroyl1u1GSPuu0kNjTOJazWSQeuBMc6jJC3mON0Tnim4gZhKZB0RW BT0rrmJXHceqtnJTsMzsWBDDojuIXDLCm8XFhhawfHi6H4dK381HbdMDU5v/GoVamv9J DUMQ==
X-Gm-Message-State: ALoCoQmw4seVhjXopzhOHFNEWzJ/u7fc7Bv4AA4++K9BXIGs/RiYTi6PuhnK+naYwpCffoVwpPF6
X-Received: by 10.50.30.66 with SMTP id q2mr19728670igh.17.1386014949269; Mon, 02 Dec 2013 12:09:09 -0800 (PST)
Received: from fusionlt2834a.int.fusionio.com ([209.117.142.2]) by mx.google.com with ESMTPSA id j16sm67621228igf.6.2013.12.02.12.09.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Dec 2013 12:09:08 -0800 (PST)
Sender: Warner Losh <wlosh@bsdimp.com>
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Warner Losh <imp@bsdimp.com>
In-Reply-To: <E1VnZdi-0000fA-CY@stenn.ntp.org>
Date: Mon, 2 Dec 2013 13:09:06 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <220ED02D-AE73-436F-A81F-BDF54611173B@bsdimp.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <529CA616.3010402@ntp.org> <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com> <E1VnZdi-0000fA-CY@stenn.ntp.org>
To: Harlan Stenn <stenn@ntp.org>
X-Mailer: Apple Mail (2.1085)
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, Ted Lemon <ted.lemon@nominum.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 20:09:13 -0000

On Dec 2, 2013, at 12:58 PM, Harlan Stenn wrote:

> Warner Losh writes:
>>>> The reason for time_t is the dhcp-client can feed that directly =
into
>>>> following call: settimeofday(const struct timeval *tp, const struct
>>>> timezone *tzp)
>>=20
>> During a leap second, the value of time_t is not well defined because
>> by definition leap seconds don't happen in time_t/POSIX time scale
>> (don't happen -- well don't consume space in the time_t timescale is
>> more pedantically correct). Obscure point likely worth noting...  But
>> using a NTP time stamp doesn't save you, since during a leap second
>> its value is well defined, but the same as another second (ntp
>> distinguishes in bits set in other parts of the header). Assuming the
>> tolerance for this application is >> 1s, this won't matter, but might
>> be worth specifying that during a leap second, the value returned
>> shall be either the value of the prior second or the value of the =
next
>> second to make it conform to most current usage.
>=20
> It's actually fuzzier than that, and this situation (which is handled
> differently with ntpd under unix, ntpd under windows, and on systems
> that "smear" the leap second over a longer period) is one of the cases
> handled by the General Timestamp API project at Network Time =
Foundation,
> described at http://nwtime.org/projects/timestamp-api/ .

Actually, in all those cases it is within a second of the 'real' time, =
hence specifying that it should be one second or the other seems =
appropriate. The timestamp APIs are for sub-second resolution, while the =
time_t in this protocol has only a second resolution... The main point =
is that it should be (a) specified to be what's going to most likely =
happen (or keep bounds on the error)  and (b) something sane that =
doesn't introduce errors > tolerance of the protocol. Having it be =
completely unspecified is a mistake, since -1 could be returned...

Warner


From stenn@stenn.ntp.org  Mon Dec  2 13:34:50 2013
Return-Path: <stenn@stenn.ntp.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCB5C1ADF67 for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 13:34:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mskFynJ4i4AF for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 13:34:49 -0800 (PST)
Received: from stenn.ntp.org (stenn.ntp.org [149.20.68.30]) by ietfa.amsl.com (Postfix) with ESMTP id 397AE1ADF10 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 13:34:49 -0800 (PST)
Received: from localhost.ntp.org ([::1] helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1Vnb6D-0000lV-Gy; Mon, 02 Dec 2013 21:32:13 +0000
From: Harlan Stenn <stenn@ntp.org>
To: Warner Losh <imp@bsdimp.com>
In-reply-to: <220ED02D-AE73-436F-A81F-BDF54611173B@bsdimp.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <529CA616.3010402@ntp.org> <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com> <E1VnZdi-0000fA-CY@stenn.ntp.org> <220ED02D-AE73-436F-A81F-BDF54611173B@bsdimp.com>
Comments: In-reply-to Warner Losh <imp@bsdimp.com> message dated "Mon, 02 Dec 2013 13:09:06 -0700."
X-Mailer: MH-E 7.4.2; nmh 1.5; XEmacs 21.4 (patch 22)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Mon, 02 Dec 2013 21:32:13 +0000
Message-Id: <E1Vnb6D-0000lV-Gy@stenn.ntp.org>
Cc: Harlan Stenn <stenn@ntp.org>, Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, Ted Lemon <ted.lemon@nominum.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 21:34:51 -0000

Warner Losh writes:
> On Dec 2, 2013, at 12:58 PM, Harlan Stenn wrote:
>> It's actually fuzzier than that, and this situation (which is handled
>> differently with ntpd under unix, ntpd under windows, and on systems
>> that "smear" the leap second over a longer period) is one of the
>> cases handled by the General Timestamp API project at Network Time
>> Foundation, described at http://nwtime.org/projects/timestamp-api/ .
> 
> Actually, in all those cases it is within a second of the 'real' time,
> hence specifying that it should be one second or the other seems
> appropriate. The timestamp APIs are for sub-second resolution, while the
> time_t in this protocol has only a second resolution... The main point
> is that it should be (a) specified to be what's going to most likely
> happen (or keep bounds on the error)  and (b) something sane that
> doesn't introduce errors > tolerance of the protocol. Having it be
> completely unspecified is a mistake, since -1 could be returned...

I'd suspect that usually 1 second will be the ballpark, but it's pretty
easy to find situations where the system clock is out by more than that.

I mention the General Timestamp API because that effort is looking at
use cases like this one from a larger persepective.

H

From marka@isc.org  Mon Dec  2 14:03:33 2013
Return-Path: <marka@isc.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AF061ADF84 for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 14:03:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GJNBRiyFD8hg for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 14:03:32 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 18E2C1ADF79 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 14:03:32 -0800 (PST)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 47B33C94C0; Mon,  2 Dec 2013 22:03:13 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1386021809; bh=xaXM16kQLJhvMxMUPLWuhXhPSHitZKWkP9oD0TH0Ko0=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=b1+cMHZapIZCdDaamQbo4Hf1X9sFBVN9g9NrEUdcuPvT5wlQ996rb1JtcWVCSzwO6 5GPiPdi4YAjndWAH8zsmshtJ0xTy/U/4MsBlZBGGhM0cBPH0wtXkkweN4GY8kRwB+V eiEQ2ldqbZ93BZ1HdtBP3SmZrjXqs45pLcEWxG7w=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Mon,  2 Dec 2013 22:03:13 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id A24D2160436; Mon,  2 Dec 2013 22:10:55 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 5D36316034F; Mon,  2 Dec 2013 22:10:55 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 85669B04BBE; Tue,  3 Dec 2013 09:03:11 +1100 (EST)
To: Harlan Stenn <stenn@ntp.org>
From: Mark Andrews <marka@isc.org>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <529CA616.3010402@ntp.org> <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com> <E1VnZdi-0000fA-CY@stenn.ntp.org> <220ED02D-AE73-436F-A81F-BDF54611173B@bsdimp.com> <E1Vnb6D-0000lV-Gy@stenn.ntp.org>
In-reply-to: Your message of "Mon, 02 Dec 2013 21:32:13 -0000." <E1Vnb6D-0000lV-Gy@stenn.ntp.org>
Date: Tue, 03 Dec 2013 09:03:11 +1100
Message-Id: <20131202220311.85669B04BBE@rock.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, Ted Lemon <ted.lemon@nominum.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Warner Losh <imp@bsdimp.com>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 22:03:33 -0000

The inception and expiration times in RRSIGs is specified as seconds
since 00:00:00 Jan 1 1970 UTC excluding leap seconds modulo 2^32.

There are no recommended fudge factors to use when evaluating these
times though named sets the expire time to 3600 seconds in the past
by default when generating RRSIGs.  I believe the other signers do
similar.  I've considered making the inception timestamp a whole
day in the past to cope with badly set timezones.

The signature validity intervals are on the order of days.  Named
defaults to 30 days.  They are regenerated about a week before they
are due expire if not already regenerated due to zone content
changes.  The records should expire from caches before they become
invalid if re-signing is being done properly.

So if the validator and the signer are both within 30 minutes of
the true time validation should succeed.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From marka@isc.org  Mon Dec  2 14:15:37 2013
Return-Path: <marka@isc.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7402F1ADFB1 for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 14:15:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.881
X-Spam-Level: 
X-Spam-Status: No, score=-5.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ocP82BLpPVFc for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 14:15:36 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) by ietfa.amsl.com (Postfix) with ESMTP id CB0FA1ADFB0 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 14:15:35 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id D130A2383B6; Mon,  2 Dec 2013 22:15:21 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id CB52D160436; Mon,  2 Dec 2013 22:23:03 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 97C6D16034F; Mon,  2 Dec 2013 22:23:03 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id BF773B04CC1; Tue,  3 Dec 2013 09:15:19 +1100 (EST)
From: Mark Andrews <marka@isc.org>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <529CA616.3010402@ntp.org> <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com> <E1VnZdi-0000fA-CY@stenn.ntp.org> <220ED02D-AE73-436F-A81F-BDF54611173B@bsdimp.com> <E1Vnb6D-0000lV-Gy@stenn.ntp.org> <20131202220311.85669B04BBE@rock.dv.isc.org>
In-reply-to: Your message of "Tue, 03 Dec 2013 09:03:11 +1100." <20131202220311.85669B04BBE@rock.dv.isc.org>
Date: Tue, 03 Dec 2013 09:15:19 +1100
Message-Id: <20131202221519.BF773B04CC1@rock.dv.isc.org>
Cc: Harlan Stenn <stenn@ntp.org>, Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, Ted Lemon <ted.lemon@nominum.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Dec 2013 22:15:37 -0000

In message <20131202220311.85669B04BBE@rock.dv.isc.org>, Mark Andrews writes:
> 
> The inception and expiration times in RRSIGs is specified as seconds
> since 00:00:00 Jan 1 1970 UTC excluding leap seconds modulo 2^32.
> 
> There are no recommended fudge factors to use when evaluating these
> times though named sets the expire time to 3600 seconds in the past

That should read "inception time to 3600 seconds in the past"

> by default when generating RRSIGs.  I believe the other signers do
> similar.  I've considered making the inception timestamp a whole
> day in the past to cope with badly set timezones.
> 
> The signature validity intervals are on the order of days.  Named
> defaults to 30 days.  They are regenerated about a week before they
> are due expire if not already regenerated due to zone content
> changes.  The records should expire from caches before they become
> invalid if re-signing is being done properly.
> 
> So if the validator and the signer are both within 30 minutes of
> the true time validation should succeed.
> 
> Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From bingxuere@gmail.com  Mon Dec  2 16:39:45 2013
Return-Path: <bingxuere@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FC1B1ADFDD for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 16:39:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8cHE4UIqVJOg for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 16:39:42 -0800 (PST)
Received: from mail-ve0-x232.google.com (mail-ve0-x232.google.com [IPv6:2607:f8b0:400c:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id BF0191ADFDC for <dhcwg@ietf.org>; Mon,  2 Dec 2013 16:39:41 -0800 (PST)
Received: by mail-ve0-f178.google.com with SMTP id c14so9774471vea.9 for <dhcwg@ietf.org>; Mon, 02 Dec 2013 16:39:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=IBUxi49dudaGzE2Ljebhxgv0N1M3bcN2cqUlZTY99RY=; b=MKtWgoECm4j/Wi4ZcmizNb8w2A0jUbzxEp9AGCDxjr+popDAQrISjiWhjX1XK8KxzT rtrAIVxYDa83/VjMPm0wBF6C1MvbOB50G0rLEw8DsT6a70VA6FWbe5TmZqjafCVtgOSW sfQcW/pvDxRJ40pp/hxjdZRoKfXDVNR0fR/UEUuZaao+40adTbPDygWVXVBytHOqymSZ zyQRlFbiqesM9JV+zeV4A8WuvjqPLHaVNWZiMMYaT/MSSO6UMWnmB46CFhwjQgzfopSf 7tuPExAHiBTiyOJl+ThPitSKoqcNwGwIsdvpM/w3AaQieIeCjGe7Z98ETrB6FGzOxPpm Dn3g==
X-Received: by 10.221.29.8 with SMTP id rw8mr54492vcb.56.1386031179120; Mon, 02 Dec 2013 16:39:39 -0800 (PST)
MIME-Version: 1.0
Received: by 10.220.93.6 with HTTP; Mon, 2 Dec 2013 16:38:59 -0800 (PST)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADC8C82@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1AD98DE0@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADC2A5B@xmb-rcd-x04.cisco.com> <CAFGoqUMh-xT+GsJQNHGUcisqcphAVFZXnQ6ac+GXq76wBBiyYw@mail.gmail.com> <AC25F22F-A27C-40FC-B4AF-9EA886D973A6@gmail.com> <CAFGoqUOtzad1iNMrqs5vyy5wqewxw445Q_iAiKgYjgLvocR5EQ@mail.gmail.com> <DEEB7D15-5356-4A9C-A899-9CBC6B14C326@gmail.com> <CAFGoqUPoth6VbdX8hPZaeN4Hh5Fi7eBJXBhcO8NmqirQqePSvg@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1ADC8C82@xmb-rcd-x04.cisco.com>
From: Qiong <bingxuere@gmail.com>
Date: Tue, 3 Dec 2013 08:38:59 +0800
Message-ID: <CAH3bfACQzYqc4CY=OiW2BTUOe93FrLLVkj2KsS_XU4XKd6mbkw@mail.gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: multipart/alternative; boundary=001a1133951014503804ec968898
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 - Respond by Dec 2, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Dec 2013 00:39:45 -0000

--001a1133951014503804ec968898
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Dear all,

This document is short but useful for DHCPv6 when new types of messages are
defined.
An editorial suggestion: The doc should be consistent with 'to', 'toward'
and 'towards'.

Thanks
Qiong


On Mon, Dec 2, 2013 at 10:47 PM, Bernie Volz (volz) <volz@cisco.com> wrote:

> Hi:
>
> Also, should we perhaps clean up (b) as to what exactly constitutes
> 'target of the message'? One determination of 'target' might be that IPv6
> destination address in the packet is one of the relay's unicast addresses=
.
> Another would be the message type? I think this definition is primarily
> based on message type??
>
>
> Here's a bunch of nits / suggestions for the document:
>
> Regarding the section 4.1 issue:
>
>    In the case that a new type of relay message is sent to a relay agent
>    but the relay agent doesn't recognize it, the message is put into a
>    Relay-forward message and sent to the server.  Then the server knows
>    the relay agent doesn't support the new message.
>
> How about:
>
>    This definition of what constitutes a 'valid message' for the relay wi=
ll
>    avoid the need for changes to relay agents when new client/server
>    message types are defined. However, changes to relay agents will be
>    required when a new message type not intended to be forwarded
>    towards the server is defined (and this cannot be avoided as the relay
>    needs the logic to process that message anyway).
>
> ---
>
> 3.  Problem Statement
>
>    The relay agent is bound to send a message either to the server or to
>    the client.  But RFC3315 doesn't explicitly describe how the relay
>    agent can find out it should send a message towards the server or
>    towards the client.
>
>    Another issue is that, it's not specific in RFC3315 about what a
>    relay agent should do if it doesn't recognize the received messages.
>    The relay agent isn't required to relay the messages, nor advised to
>    drop them.
>
>    In addition, there is no specific requirement of the client or server
>    on dealing with an unknown message in RFC3315.
>
> How about:
>
>    The relay agent is bound to send a message either to the server or to
>    the client.  But RFC3315 doesn't explicitly describe how the relay
>    agent can find out if it should send a message towards the server or
>    towards the client.
>
>    Another issue is that RFC3315 is not specific about what a
>    relay agent should do if it does not recognize a received message;
>    the relay agent is not required to relay the message, nor advised to
>    drop the message.
>
>    In addition, there is no specific requirement for dealing with
>    unknown messages by the client or server in RFC3315.
>
> And what about adding:
>
>     And it is expected that most future DHCPv6 messages will not be
>     used to communicate directly with relay agents (though they may
>     need to be relayed by relay agents).
>
>
> In the rest of the document (as Sheng outlined), please replace n't with
> not (i.e., doesn't should be replaced by does not).
>
> - Bernie
>
> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Marcin Siodelski
> Sent: Monday, December 02, 2013 7:38 AM
> To: Qi Sun
> Cc: dhcwg@ietf.org; Bernie Volz (volz)
> Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 -
> Respond by Dec 2, 2013
>
> On Mon, Dec 2, 2013 at 1:26 PM, Qi Sun <sunqi.csnet.thu@gmail.com> wrote:
> >
> > Hi Marcin,
> >
> > On 2013-12-2, at =E4=B8=8B=E5=8D=885:32, Marcin Siodelski wrote:
> >
> >>>> ISSUE 2
> >>>> In this sentence:
> >>>>
> >>>> "In the case that a new type of relay message is sent to a relay
> >>>> agent  but the relay agent doesn't recognize it, the message is put
> >>>> into a  Relay-forward message and sent to the server."
> >>>>
> >>>> Why "new type of relay message", not "new type of message"? I don't
> >>>> quite understand what the relay message is in this context.
> >>>
> >>> [Qi] A new type of relay message targets at the relay agent. If a
> relay agent recognizes the message, then it should consume the message.
> Otherwise, the relay just sends the message to the server (in a
> Relay-forward message), so that the server gets the information that this
> relay doesn't support the new relay agent message.
> >>> In Bullet (b), the message doesn't take the relay agent as the target=
.
> >>> If this part isn't clear enough, we can improve it.
> >>>
> >>
> >> Thanks for this explanation. Let me rephrase my question, because I
> >> was asking about slightly different thing....
> >>
> >> Would it still be ok if we had this text: "In the case that a new
> >> type of message is sent to a relay agent..... ", instead of "In the
> >> case that a new type of relay message is sent to a relay agent..."?
> >> Simply removed "relay". I don't understand how "relay message" is
> >> different from the "message" or "valid message".
> >>
> >
> > Thanks for your patience. What I wanted to say was that the new type of
> message targets at the relay agent rather than the client/server. IMHO, i=
f
> remove "relay", the relationship between this paragraph and the bullet (b=
)
> might be a little confusing.
> > How about this:
> >
> >    In the case that a new type of message targets at a relay agent
> >    but the relay agent does not recognize it, ...
> >
> > Would the expression be better?
> >
>
> IMHO, that is much better. In the former case, the verb "send" makes it
> ambiguous - message sent to a relay agent doesn't have to be necessarily
> consumed/processed by relay, it could be forwarded. At least this is how =
I
> read it. :-)
>
> Marcin
> _______________________________________________
> 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
>



--=20
=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=3D=3D=3D=3D=3D
Qiong Sun
China Telecom Beijing Research Institude


Open source code:
lightweight 4over6: *http://sourceforge.net/projects/laft6/
<http://sourceforge.net/projects/laft6/>*
PCP-natcoord:* http://sourceforge.net/projects/pcpportsetdemo/
<http://sourceforge.net/projects/pcpportsetdemo/> *
=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=3D=3D=3D=3D=3D=3D

--001a1133951014503804ec968898
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear all,<div><br></div><div><div>This document is short b=
ut useful for DHCPv6 when new types of messages are=20
defined. </div>
<div>An editorial suggestion: The doc should be consistent with &#39;to&#39=
;,=20
&#39;toward&#39; and &#39;towards&#39;.=C2=A0</div></div><div><br></div><di=
v>Thanks</div><div>Qiong</div></div><div class=3D"gmail_extra"><br><br><div=
 class=3D"gmail_quote">On Mon, Dec 2, 2013 at 10:47 PM, Bernie Volz (volz) =
<span dir=3D"ltr">&lt;<a href=3D"mailto:volz@cisco.com" target=3D"_blank">v=
olz@cisco.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi:<br>
<br>
Also, should we perhaps clean up (b) as to what exactly constitutes &#39;ta=
rget of the message&#39;? One determination of &#39;target&#39; might be th=
at IPv6 destination address in the packet is one of the relay&#39;s unicast=
 addresses. Another would be the message type? I think this definition is p=
rimarily based on message type??<br>


<br>
<br>
Here&#39;s a bunch of nits / suggestions for the document:<br>
<br>
Regarding the section 4.1 issue:<br>
<div class=3D"im"><br>
=C2=A0 =C2=A0In the case that a new type of relay message is sent to a rela=
y agent<br>
=C2=A0 =C2=A0but the relay agent doesn&#39;t recognize it, the message is p=
ut into a<br>
</div>=C2=A0 =C2=A0Relay-forward message and sent to the server. =C2=A0Then=
 the server knows<br>
=C2=A0 =C2=A0the relay agent doesn&#39;t support the new message.<br>
<br>
How about:<br>
<br>
=C2=A0 =C2=A0This definition of what constitutes a &#39;valid message&#39; =
for the relay will<br>
=C2=A0 =C2=A0avoid the need for changes to relay agents when new client/ser=
ver<br>
=C2=A0 =C2=A0message types are defined. However, changes to relay agents wi=
ll be<br>
=C2=A0 =C2=A0required when a new message type not intended to be forwarded<=
br>
=C2=A0 =C2=A0towards the server is defined (and this cannot be avoided as t=
he relay<br>
=C2=A0 =C2=A0needs the logic to process that message anyway).<br>
<br>
---<br>
<br>
3. =C2=A0Problem Statement<br>
<br>
=C2=A0 =C2=A0The relay agent is bound to send a message either to the serve=
r or to<br>
=C2=A0 =C2=A0the client. =C2=A0But RFC3315 doesn&#39;t explicitly describe =
how the relay<br>
<div class=3D"im">=C2=A0 =C2=A0agent can find out it should send a message =
towards the server or<br>
=C2=A0 =C2=A0towards the client.<br>
<br>
</div>=C2=A0 =C2=A0Another issue is that, it&#39;s not specific in RFC3315 =
about what a<br>
=C2=A0 =C2=A0relay agent should do if it doesn&#39;t recognize the received=
 messages.<br>
=C2=A0 =C2=A0The relay agent isn&#39;t required to relay the messages, nor =
advised to<br>
=C2=A0 =C2=A0drop them.<br>
<br>
=C2=A0 =C2=A0In addition, there is no specific requirement of the client or=
 server<br>
=C2=A0 =C2=A0on dealing with an unknown message in RFC3315.<br>
<br>
How about:<br>
<br>
=C2=A0 =C2=A0The relay agent is bound to send a message either to the serve=
r or to<br>
=C2=A0 =C2=A0the client. =C2=A0But RFC3315 doesn&#39;t explicitly describe =
how the relay<br>
=C2=A0 =C2=A0agent can find out if it should send a message towards the ser=
ver or<br>
=C2=A0 =C2=A0towards the client.<br>
<br>
=C2=A0 =C2=A0Another issue is that RFC3315 is not specific about what a<br>
=C2=A0 =C2=A0relay agent should do if it does not recognize a received mess=
age;<br>
=C2=A0 =C2=A0the relay agent is not required to relay the message, nor advi=
sed to<br>
=C2=A0 =C2=A0drop the message.<br>
<br>
=C2=A0 =C2=A0In addition, there is no specific requirement for dealing with=
<br>
=C2=A0 =C2=A0unknown messages by the client or server in RFC3315.<br>
<br>
And what about adding:<br>
<br>
=C2=A0 =C2=A0 And it is expected that most future DHCPv6 messages will not =
be<br>
=C2=A0 =C2=A0 used to communicate directly with relay agents (though they m=
ay<br>
=C2=A0 =C2=A0 need to be relayed by relay agents).<br>
<br>
<br>
In the rest of the document (as Sheng outlined), please replace n&#39;t wit=
h not (i.e., doesn&#39;t should be replaced by does not).<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
- Bernie<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
-----Original Message-----<br>
From: dhcwg [mailto:<a href=3D"mailto:dhcwg-bounces@ietf.org">dhcwg-bounces=
@ietf.org</a>] On Behalf Of Marcin Siodelski<br>
Sent: Monday, December 02, 2013 7:38 AM<br>
To: Qi Sun<br>
Cc: <a href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>; Bernie Volz (volz=
)<br>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 - Respon=
d by Dec 2, 2013<br>
<br>
On Mon, Dec 2, 2013 at 1:26 PM, Qi Sun &lt;<a href=3D"mailto:sunqi.csnet.th=
u@gmail.com">sunqi.csnet.thu@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi Marcin,<br>
&gt;<br>
&gt; On 2013-12-2, at =E4=B8=8B=E5=8D=885:32, Marcin Siodelski wrote:<br>
&gt;<br>
&gt;&gt;&gt;&gt; ISSUE 2<br>
&gt;&gt;&gt;&gt; In this sentence:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; &quot;In the case that a new type of relay message is sent=
 to a relay<br>
&gt;&gt;&gt;&gt; agent =C2=A0but the relay agent doesn&#39;t recognize it, =
the message is put<br>
&gt;&gt;&gt;&gt; into a =C2=A0Relay-forward message and sent to the server.=
&quot;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Why &quot;new type of relay message&quot;, not &quot;new t=
ype of message&quot;? I don&#39;t<br>
&gt;&gt;&gt;&gt; quite understand what the relay message is in this context=
.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; [Qi] A new type of relay message targets at the relay agent. I=
f a relay agent recognizes the message, then it should consume the message.=
 Otherwise, the relay just sends the message to the server (in a Relay-forw=
ard message), so that the server gets the information that this relay doesn=
&#39;t support the new relay agent message.<br>


&gt;&gt;&gt; In Bullet (b), the message doesn&#39;t take the relay agent as=
 the target.<br>
&gt;&gt;&gt; If this part isn&#39;t clear enough, we can improve it.<br>
&gt;&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Thanks for this explanation. Let me rephrase my question, because =
I<br>
&gt;&gt; was asking about slightly different thing....<br>
&gt;&gt;<br>
&gt;&gt; Would it still be ok if we had this text: &quot;In the case that a=
 new<br>
&gt;&gt; type of message is sent to a relay agent..... &quot;, instead of &=
quot;In the<br>
&gt;&gt; case that a new type of relay message is sent to a relay agent...&=
quot;?<br>
&gt;&gt; Simply removed &quot;relay&quot;. I don&#39;t understand how &quot=
;relay message&quot; is<br>
&gt;&gt; different from the &quot;message&quot; or &quot;valid message&quot=
;.<br>
&gt;&gt;<br>
&gt;<br>
&gt; Thanks for your patience. What I wanted to say was that the new type o=
f message targets at the relay agent rather than the client/server. IMHO, i=
f remove &quot;relay&quot;, the relationship between this paragraph and the=
 bullet (b) might be a little confusing.<br>


&gt; How about this:<br>
&gt;<br>
&gt; =C2=A0 =C2=A0In the case that a new type of message targets at a relay=
 agent<br>
&gt; =C2=A0 =C2=A0but the relay agent does not recognize it, ...<br>
&gt;<br>
&gt; Would the expression be better?<br>
&gt;<br>
<br>
IMHO, that is much better. In the former case, the verb &quot;send&quot; ma=
kes it ambiguous - message sent to a relay agent doesn&#39;t have to be nec=
essarily consumed/processed by relay, it could be forwarded. At least this =
is how I read it. :-)<br>


<br>
Marcin<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>
_______________________________________________<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><br clear=3D"all"><div><br></div>-- <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=3D=3D=3D=3D=3D<br>Qiong Su=
n<br>China Telecom Beijing Research Institude<br><br><br>Open source code:<=
br>lightweight 4over6: <i><a href=3D"http://sourceforge.net/projects/laft6/=
" target=3D"_blank">http://sourceforge.net/projects/laft6/</a></i><br>

PCP-natcoord:<i> <a href=3D"http://sourceforge.net/projects/pcpportsetdemo/=
" target=3D"_blank">http://sourceforge.net/projects/pcpportsetdemo/</a> </i=
><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=3D=3D=3D=3D=3D=3D<br=
><br>
</div>

--001a1133951014503804ec968898--

From volz@cisco.com  Mon Dec  2 17:46:46 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CF7C1AE01D for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 17:46:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.502
X-Spam-Level: 
X-Spam-Status: No, score=-9.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nZy2DXiNgkcJ for <dhcwg@ietfa.amsl.com>; Mon,  2 Dec 2013 17:46:45 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) by ietfa.amsl.com (Postfix) with ESMTP id 28C9E1AE009 for <dhcwg@ietf.org>; Mon,  2 Dec 2013 17:46:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1283; q=dns/txt; s=iport; t=1386035203; x=1387244803; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=s1R06+0WGAodjmMPLh2cNw47v9ACdT1qNnyPB0GS3BU=; b=MSsTjVbYAZ5cD8LRqCTW2ikSYiKhjORH05SqBJn3xC6i1d/TwJw5ZhK2 1ruVRJuxpqmJWb1m4NKtOZo+zuxv3XFpdouA1AYJst/Ll6vFahnX6e0i1 8Fv293tn3AoCy4BIwe6ZVkCBkyoMbVvxEy+apGhZwV/iVw5qbECp+0Brp g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAMo3nVKtJXG+/2dsb2JhbABZgwc4uTuBGxZ0giUBAQEDATo/EAIBCA4oEDIlAQEEDgWHewbAaBeOVTMHgyCBEwOYFJITgWuBPg
X-IronPort-AV: E=Sophos;i="4.93,814,1378857600";  d="scan'208";a="3820933"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by alln-iport-2.cisco.com with ESMTP; 03 Dec 2013 01:46:35 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id rB31kZsU026747 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 3 Dec 2013 01:46:35 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.03.0123.003; Mon, 2 Dec 2013 19:46:34 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ole Troan <otroan@employees.org>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
Thread-Index: Ac7pYNYYaEg536DmSXaLna21+HapNwGZSwcAAADfOVc=
Date: Tue, 3 Dec 2013 01:46:33 +0000
Message-ID: <70E0AB50-27FB-4388-96DB-F46D260E553B@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com>, <3219ECB2-F220-403B-984B-7254677528DE@employees.org>
In-Reply-To: <3219ECB2-F220-403B-984B-7254677528DE@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>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Dec 2013 01:46:46 -0000

Hi:

That's an informational RFC and references (informational) work in progress=
 (which sometimes changes or is even abandoned). That's the risk the IETF a=
cknowledges with such references.

If DHCPv4 works "as is", what more do you need from the DHC WG? Use DHCPv4 =
"as is" - what's stopping you?

We are trying to solve the general problem when all that can be assured is =
the ability to send IPv6 packets.

We will consider your objection during the rough consensus review.

- Bernie (from iPad)

On Dec 2, 2013, at 2:21 PM, "Ole Troan" <otroan@employees.org> wrote:

>> Folks, the authors of draft-ietf-dhc-dhcpv4-over-dhcpv6-03 (http://tools=
.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-03.txt) believe it is read=
y for working group last call. Please review this draft and indicate whethe=
r or not you feel it is ready to be published. Your input is important! Ple=
ase respond by Dec 9th, 2013.
>=20
> I do not support publication of this document.
> I believe that using DHCPv4 as currently specified (RFC2131, RFC5107, RFC=
3456, RFC3046) is sufficient also for A+P softwire tunnels.
>=20
> RFC7040 references DHCPv4 over IPv6. is this working group also going to =
specify this alternative transport?
>=20
> cheers,
> Ole
>=20

From otroan@employees.org  Tue Dec  3 01:30:22 2013
Return-Path: <otroan@employees.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 820081AE0DC for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 01:30:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3nEyXrvccce3 for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 01:30:21 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id D71641AE0D8 for <dhcwg@ietf.org>; Tue,  3 Dec 2013 01:30:20 -0800 (PST)
X-Files: signature.asc : 496
X-IronPort-AV: E=Sophos;i="4.93,816,1378857600"; d="asc'?scan'208";a="985275"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-2.cisco.com with ESMTP; 03 Dec 2013 09:30:17 +0000
Received: from dhcp-lys02-vla252-10-147-116-75.cisco.com (dhcp-lys02-vla252-10-147-116-75.cisco.com [10.147.116.75]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id rB39UAeD023426 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 3 Dec 2013 09:30:12 GMT
Content-Type: multipart/signed; boundary="Apple-Mail=_094FB5F6-2C17-4FB6-BF34-11985DF34ADB"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <70E0AB50-27FB-4388-96DB-F46D260E553B@cisco.com>
Date: Tue, 3 Dec 2013 10:30:09 +0100
Message-Id: <77AB54E8-7150-49DC-A9B6-65CFCDA0D28A@employees.org>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com>, <3219ECB2-F220-403B-984B-7254677528DE@employees.org> <70E0AB50-27FB-4388-96DB-F46D260E553B@cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
X-Mailer: Apple Mail (2.1822)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Dec 2013 09:30:22 -0000

--Apple-Mail=_094FB5F6-2C17-4FB6-BF34-11985DF34ADB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Bernie,

> That's an informational RFC and references (informational) work in =
progress (which sometimes changes or is even abandoned). That's the risk =
the IETF acknowledges with such references.

you are saying that RFC7040 should be updated?

> If DHCPv4 works "as is", what more do you need from the DHC WG? Use =
DHCPv4 "as is" - what's stopping you?

to stop inventing solutions to non-existing problems.

> We are trying to solve the general problem when all that can be =
assured is the ability to send IPv6 packets.

I have asked multiple times for an explanation of what you are trying to =
achieve, and what makes this a "general problem".
I don't believe there is such a problem. and not one that makes sense in =
an A+P / softwire context.

> We will consider your objection during the rough consensus review.

I would expect so. note also for your shepherding document that I have =
threatened an appeal.

Best regards,
Ole


> - Bernie (from iPad)
>=20
> On Dec 2, 2013, at 2:21 PM, "Ole Troan" <otroan@employees.org> wrote:
>=20
>>> Folks, the authors of draft-ietf-dhc-dhcpv4-over-dhcpv6-03 =
(http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-03.txt) =
believe it is ready for working group last call. Please review this =
draft and indicate whether or not you feel it is ready to be published. =
Your input is important! Please respond by Dec 9th, 2013.
>>=20
>> I do not support publication of this document.
>> I believe that using DHCPv4 as currently specified (RFC2131, RFC5107, =
RFC3456, RFC3046) is sufficient also for A+P softwire tunnels.
>>=20
>> RFC7040 references DHCPv4 over IPv6. is this working group also going =
to specify this alternative transport?
>>=20
>> cheers,
>> Ole
>>=20


--Apple-Mail=_094FB5F6-2C17-4FB6-BF34-11985DF34ADB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJSnaShAAoJEFuJXizso86glsYIAIvPE5RuumdlShApnfz0jq4J
h6TtMNW6wvkeJvnK3COXeenPwcGGkQBJdNA+5Rfx8rdhhBx+/1VO3VacLA6w4PDb
iCABUV8YPhL8f1k0gFqg6CiphgK1N/FMwYgLaHE3rmqhhyubvyQUVBFtk+oEOg3v
18f+XJtcxTldJpu4dexO0RS1rEQzwlEeHULAvQNh03ZX7AdoLzoXjY2usZzYFAc/
ezPU6+8c6V90mmU1ppjujDttGFJg89cPimfQxicV2T/nN0Z4k7qLruJu4U464NzB
Xv9KpqomaK/Hjw8JoY/itAfC3Hj5+RWPKgnIIYGfwQMUiCWl930ngR+7S4CR20g=
=Keq+
-----END PGP SIGNATURE-----

--Apple-Mail=_094FB5F6-2C17-4FB6-BF34-11985DF34ADB--

From volz@cisco.com  Tue Dec  3 03:34:14 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31A111AE105 for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 03:34:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.502
X-Spam-Level: 
X-Spam-Status: No, score=-9.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tp8oEGJHp_dm for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 03:34:12 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id 5BC411AE112 for <dhcwg@ietf.org>; Tue,  3 Dec 2013 03:34:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2213; q=dns/txt; s=iport; t=1386070450; x=1387280050; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=g4+EcIfRV9xOWgIcm0rgrr9NrVCRLAfxvrcNf8i5A2o=; b=gb4KX6AMiPHldlVCiEXMU3CnKi5jIgC858qtwZ4RS5Xl3C3VH5kyL0/p lCEYUr4QJ+ZhtcnlHhTebgfi3w+zZTIW7Qct2Iy/pvsceWBvZGhAkurxV lzX0qE4r3t+Z5lizWLblWAyGnFEhCEFcwrB9hhFHum3JhHgv5rchn3cOv 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFAHfBnVKtJXG+/2dsb2JhbABagwc4uTqBHBZ0giUBAQEDATo/BQsCAQgOCh4QMiUBAQQOBRuHYAYNwSAXjkszB4MggRMDmBSBMJBjgWuBPg
X-IronPort-AV: E=Sophos;i="4.93,817,1378857600";  d="scan'208";a="3917632"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by alln-iport-6.cisco.com with ESMTP; 03 Dec 2013 11:34:03 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id rB3BY3tE031796 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 3 Dec 2013 11:34:03 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0123.003; Tue, 3 Dec 2013 05:34:02 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ole Troan <otroan@employees.org>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
Thread-Index: Ac7pYNYYaEg536DmSXaLna21+HapNwGZSwcAAADfOVcAHMNogP//vgf4
Date: Tue, 3 Dec 2013 11:34:01 +0000
Message-ID: <EB4A3EBF-B08F-4465-A69B-63325E2E3EDA@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com>, <3219ECB2-F220-403B-984B-7254677528DE@employees.org> <70E0AB50-27FB-4388-96DB-F46D260E553B@cisco.com>, <77AB54E8-7150-49DC-A9B6-65CFCDA0D28A@employees.org>
In-Reply-To: <77AB54E8-7150-49DC-A9B6-65CFCDA0D28A@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>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Dec 2013 11:34:14 -0000

I don't understand your points here. Your solution is not what RFC 7040 ref=
erences either. And in fact the dhcpv4-over-dhcpv6 solution is very close t=
o the dhcpv4-over-ipv6 solution as in some of the models it also only uses =
IPv6 packets.=20

- Bernie (from iPad)

> On Dec 3, 2013, at 4:30 AM, "Ole Troan" <otroan@employees.org> wrote:
>=20
> Bernie,
>=20
>> That's an informational RFC and references (informational) work in progr=
ess (which sometimes changes or is even abandoned). That's the risk the IET=
F acknowledges with such references.
>=20
> you are saying that RFC7040 should be updated?
>=20
>> If DHCPv4 works "as is", what more do you need from the DHC WG? Use DHCP=
v4 "as is" - what's stopping you?
>=20
> to stop inventing solutions to non-existing problems.
>=20
>> We are trying to solve the general problem when all that can be assured =
is the ability to send IPv6 packets.
>=20
> I have asked multiple times for an explanation of what you are trying to =
achieve, and what makes this a "general problem".
> I don't believe there is such a problem. and not one that makes sense in =
an A+P / softwire context.
>=20
>> We will consider your objection during the rough consensus review.
>=20
> I would expect so. note also for your shepherding document that I have th=
reatened an appeal.
>=20
> Best regards,
> Ole
>=20
>=20
>> - Bernie (from iPad)
>>=20
>> On Dec 2, 2013, at 2:21 PM, "Ole Troan" <otroan@employees.org> wrote:
>>=20
>>>> Folks, the authors of draft-ietf-dhc-dhcpv4-over-dhcpv6-03 (http://too=
ls.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-03.txt) believe it is re=
ady for working group last call. Please review this draft and indicate whet=
her or not you feel it is ready to be published. Your input is important! P=
lease respond by Dec 9th, 2013.
>>>=20
>>> I do not support publication of this document.
>>> I believe that using DHCPv4 as currently specified (RFC2131, RFC5107, R=
FC3456, RFC3046) is sufficient also for A+P softwire tunnels.
>>>=20
>>> RFC7040 references DHCPv4 over IPv6. is this working group also going t=
o specify this alternative transport?
>>>=20
>>> cheers,
>>> Ole
>=20

From otroan@employees.org  Tue Dec  3 03:54:48 2013
Return-Path: <otroan@employees.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 462731AE11B for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 03:54:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qS4MBUVSbvyu for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 03:54:47 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id B3CED1AE0FC for <dhcwg@ietf.org>; Tue,  3 Dec 2013 03:54:46 -0800 (PST)
X-Files: signature.asc : 496
X-IronPort-AV: E=Sophos;i="4.93,817,1378857600"; d="asc'?scan'208";a="993055"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by aer-iport-2.cisco.com with ESMTP; 03 Dec 2013 11:54:43 +0000
Received: from dhcp-lys02-vla252-10-147-116-75.cisco.com (dhcp-lys02-vla252-10-147-116-75.cisco.com [10.147.116.75]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rB3BsaSx001283 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 3 Dec 2013 11:54:38 GMT
Content-Type: multipart/signed; boundary="Apple-Mail=_A886E61B-9247-4633-92A0-5BAD06ACFC60"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <EB4A3EBF-B08F-4465-A69B-63325E2E3EDA@cisco.com>
Date: Tue, 3 Dec 2013 12:54:40 +0100
Message-Id: <03FEB951-90D6-4DAF-9793-76ACFD1A30D3@employees.org>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com>, <3219ECB2-F220-403B-984B-7254677528DE@employees.org> <70E0AB50-27FB-4388-96DB-F46D260E553B@cisco.com>, <77AB54E8-7150-49DC-A9B6-65CFCDA0D28A@employees.org> <EB4A3EBF-B08F-4465-A69B-63325E2E3EDA@cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
X-Mailer: Apple Mail (2.1822)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Dec 2013 11:54:48 -0000

--Apple-Mail=_A886E61B-9247-4633-92A0-5BAD06ACFC60
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Bernie,

> I don't understand your points here. Your solution is not what RFC =
7040 references either. And in fact the dhcpv4-over-dhcpv6 solution is =
very close to the dhcpv4-over-ipv6 solution as in some of the models it =
also only uses IPv6 packets.=20

my point was that you've already put one alternative way of carrying =
DHCPv4 out there. my question was if you should try to put that cat back =
into the bag?

in any case, let's not digress on RFC7040. that wasn't the point.

it appears you think it is important that DHCPv4 uses "only IPv6 =
packets". that's what a tunnel does, why do you think DHCPv4 needs to =
build its own transport?

cheers,
Ole


>=20
> - Bernie (from iPad)
>=20
>> On Dec 3, 2013, at 4:30 AM, "Ole Troan" <otroan@employees.org> wrote:
>>=20
>> Bernie,
>>=20
>>> That's an informational RFC and references (informational) work in =
progress (which sometimes changes or is even abandoned). That's the risk =
the IETF acknowledges with such references.
>>=20
>> you are saying that RFC7040 should be updated?
>>=20
>>> If DHCPv4 works "as is", what more do you need from the DHC WG? Use =
DHCPv4 "as is" - what's stopping you?
>>=20
>> to stop inventing solutions to non-existing problems.
>>=20
>>> We are trying to solve the general problem when all that can be =
assured is the ability to send IPv6 packets.
>>=20
>> I have asked multiple times for an explanation of what you are trying =
to achieve, and what makes this a "general problem".
>> I don't believe there is such a problem. and not one that makes sense =
in an A+P / softwire context.
>>=20
>>> We will consider your objection during the rough consensus review.
>>=20
>> I would expect so. note also for your shepherding document that I =
have threatened an appeal.
>>=20
>> Best regards,
>> Ole
>>=20
>>=20
>>> - Bernie (from iPad)
>>>=20
>>> On Dec 2, 2013, at 2:21 PM, "Ole Troan" <otroan@employees.org> =
wrote:
>>>=20
>>>>> Folks, the authors of draft-ietf-dhc-dhcpv4-over-dhcpv6-03 =
(http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-03.txt) =
believe it is ready for working group last call. Please review this =
draft and indicate whether or not you feel it is ready to be published. =
Your input is important! Please respond by Dec 9th, 2013.
>>>>=20
>>>> I do not support publication of this document.
>>>> I believe that using DHCPv4 as currently specified (RFC2131, =
RFC5107, RFC3456, RFC3046) is sufficient also for A+P softwire tunnels.
>>>>=20
>>>> RFC7040 references DHCPv4 over IPv6. is this working group also =
going to specify this alternative transport?
>>>>=20
>>>> cheers,
>>>> Ole
>>=20


--Apple-Mail=_A886E61B-9247-4633-92A0-5BAD06ACFC60
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJSncaAAAoJEFuJXizso86gnT8IANAakdyNf4miaG3mZclE9Kd9
mtvJpSZklSGKPkEPazF5fwVZyU8kHDK605MxgS4imjuMkAWV1Lr+ItwHAyTXc2GQ
PUwUk4jRNHy75ixIkB/BkXWAydPaFrI0+TgD+3pd8xnxAyI/XJ8bzhNWilRJogaM
B5uT0nT9STt9mF1JJNrtlb06ubYiU3IQVv8lHM3/U4oVHBCfMncnKoAkzR2+ASWz
LEs/xls0NW75TqmiqQARZuur31tBTt63ef6XwMbRXvaAwI67z5eQJOCCynuT1zv5
Lmva5cKCkBms0aeLB8TRvcZWVXwzxn/yLVVTxw9CbB+cfEEQ1ytVTAlR6uF/Ffw=
=vSvH
-----END PGP SIGNATURE-----

--Apple-Mail=_A886E61B-9247-4633-92A0-5BAD06ACFC60--

From stenc@s-carlsen.dk  Tue Dec  3 04:12:49 2013
Return-Path: <stenc@s-carlsen.dk>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69A521AE126 for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 04:12:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.89
X-Spam-Level: 
X-Spam-Status: No, score=-0.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DK=1.009, HTML_MESSAGE=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IpjI8LwZTRIw for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 04:12:47 -0800 (PST)
Received: from mail2.s-carlsen.dk (0134100024.0.fullrate.dk [90.185.128.210]) by ietfa.amsl.com (Postfix) with ESMTP id 36BF11AE122 for <dhcwg@ietf.org>; Tue,  3 Dec 2013 04:12:46 -0800 (PST)
Received: from silver3wired.s-carlsen.dk (silver3Wired.s-carlsen.dk [192.168.16.204]) by mail2.s-carlsen.dk (Postfix) with ESMTPA id 7B0922765 for <dhcwg@ietf.org>; Tue,  3 Dec 2013 13:12:40 +0100 (CET)
Message-ID: <529DCAB8.90101@s-carlsen.dk>
Date: Tue, 03 Dec 2013 13:12:40 +0100
From: Sten Carlsen <stenc@s-carlsen.dk>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com>, <3219ECB2-F220-403B-984B-7254677528DE@employees.org> <70E0AB50-27FB-4388-96DB-F46D260E553B@cisco.com>, <77AB54E8-7150-49DC-A9B6-65CFCDA0D28A@employees.org> <EB4A3EBF-B08F-4465-A69B-63325E2E3EDA@cisco.com> <03FEB951-90D6-4DAF-9793-76ACFD1A30D3@employees.org>
In-Reply-To: <03FEB951-90D6-4DAF-9793-76ACFD1A30D3@employees.org>
X-Enigmail-Version: 1.6
Content-Type: multipart/alternative; boundary="------------080807030607010102080105"
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Dec 2013 12:12:49 -0000

This is a multi-part message in MIME format.
--------------080807030607010102080105
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On 03/12/13 12.54, Ole Troan wrote:
> Bernie,
>
>> I don't understand your points here. Your solution is not what RFC
7040 references either. And in fact the dhcpv4-over-dhcpv6 solution is
very close to the dhcpv4-over-ipv6 solution as in some of the models it
also only uses IPv6 packets.
>
> my point was that you've already put one alternative way of carrying
DHCPv4 out there. my question was if you should try to put that cat back
into the bag?
>
> in any case, let's not digress on RFC7040. that wasn't the point.
>
> it appears you think it is important that DHCPv4 uses "only IPv6
packets". that's what a tunnel does, why do you think DHCPv4 needs to
build its own transport?
A couple of questions comes to mind here (at least my mind):
- - Is the IPv4 island expected to be a real island all on it's own OR
is it an island connected via a tunnel to other islands of IPv4?
- - Will the DHCP4 server have IPv4 connectivity via the tunnel and
maybe more or will it be all IPv6, with only the DHCP4 communicating
over it's own protocol?
>
>
> cheers,
> Ole
>
>

- -- 
Best regards

Sten Carlsen

No improvements come from shouting:

       "MALE BOVINE MANURE!!!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSncq3AAoJEGlQ1JzTWDCB2ogP/3xt9GEpshUKutsW82khXmFQ
41j7f8dAsIk2BvwQZ6/xEiHoFAs2hw7OaJHpNPmWR0OkUd6SXSsN/SFOreAze7wW
AGYYslf2r/1+9Vo4GON3aeKz1x70nQMGA3kDtMgmXQ2CcsKe90khODORpvNiEeSQ
OEr6f/kNN3hvGxvzWwkX0biDSTSk63OVnnWNatr2GneSaHbvpuCo12c9+dJQnhBU
fo8rKOS3YbzWhG4nDBGjVrWs/8BkoL9bB1esOwSp9oOT6H8fanSC0VJXAd3ZeVPd
gB8OPgY6iFefHyTLhn9vcZo8lL8JnjQJL8DRZIGwa9SLDXTefbpCX3FlDDjoWGfl
qwak1zTydAflosyTJh++VSphzMuQ6sNjSSO7eQbzaF0L2iM12C+K2C2PZmj8oZj2
rBrzxd/t2xJp3i99uRM0D5FXN5WBfBLLxvfztpBLOaJ+huCGXAstH8wIHnLzmtwf
W+Qm++NTTrAe0C8NE9wMaNaAB2CduBj3sWKBvpFvkSwmqh61zGOyCnXr1JlLER8j
6P9XrMxKup0Kq5zimHoGc6ej7aFEnby4EMYpVDtwNmO4q/30r3SEQjUWtlffzV4E
k8hfMCKNydrXG18Z/JwRS8Y3dXC2xWdueiHUk+dJD+Qpc5kWcExrVBxrLLTMhvz6
DgLtiSYRI4w1+/ZiorMX
=mBol
-----END PGP SIGNATURE-----


--------------080807030607010102080105
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFCC" text="#000000">
    <br>
    -----BEGIN PGP SIGNED MESSAGE-----<br>
    Hash: SHA1<br>
    <br>
    <br>
    On 03/12/13 12.54, Ole Troan wrote:<br>
    <span style="white-space: pre;">&gt; Bernie,<br>
      &gt;<br>
      &gt;&gt; I don't understand your points here. Your solution is not
      what RFC 7040 references either. And in fact the
      dhcpv4-over-dhcpv6 solution is very close to the dhcpv4-over-ipv6
      solution as in some of the models it also only uses IPv6 packets.
      <br>
      &gt;<br>
      &gt; my point was that you've already put one alternative way of
      carrying DHCPv4 out there. my question was if you should try to
      put that cat back into the bag?<br>
      &gt;<br>
      &gt; in any case, let's not digress on RFC7040. that wasn't the
      point.<br>
      &gt;<br>
      &gt; it appears you think it is important that DHCPv4 uses "only
      IPv6 packets". that's what a tunnel does, why do you think DHCPv4
      needs to build its own transport?</span><br>
    A couple of questions comes to mind here (at least my mind):<br>
    - - Is the IPv4 island expected to be a real island all on it's own
    OR is it an island connected via a tunnel to other islands of IPv4?<br>
    - - Will the DHCP4 server have IPv4 connectivity via the tunnel and
    maybe more or will it be all IPv6, with only the DHCP4 communicating
    over it's own protocol?<br>
    <span style="white-space: pre;">&gt;<br>
      &gt;<br>
      &gt; cheers,<br>
      &gt; Ole<br>
      &gt;<br>
      &gt;</span><br>
    <br>
    - -- <br>
    Best regards<br>
    <br>
    Sten Carlsen<br>
    <br>
    No improvements come from shouting:<br>
    <br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "MALE BOVINE MANURE!!!"<br>
    -----BEGIN PGP SIGNATURE-----<br>
    Version: GnuPG/MacGPG2 v2.0.18 (Darwin)<br>
    Comment: Using GnuPG with Thunderbird - <a class="moz-txt-link-freetext" href="http://www.enigmail.net/">http://www.enigmail.net/</a><br>
    <br>
    iQIcBAEBAgAGBQJSncq3AAoJEGlQ1JzTWDCB2ogP/3xt9GEpshUKutsW82khXmFQ<br>
    41j7f8dAsIk2BvwQZ6/xEiHoFAs2hw7OaJHpNPmWR0OkUd6SXSsN/SFOreAze7wW<br>
    AGYYslf2r/1+9Vo4GON3aeKz1x70nQMGA3kDtMgmXQ2CcsKe90khODORpvNiEeSQ<br>
    OEr6f/kNN3hvGxvzWwkX0biDSTSk63OVnnWNatr2GneSaHbvpuCo12c9+dJQnhBU<br>
    fo8rKOS3YbzWhG4nDBGjVrWs/8BkoL9bB1esOwSp9oOT6H8fanSC0VJXAd3ZeVPd<br>
    gB8OPgY6iFefHyTLhn9vcZo8lL8JnjQJL8DRZIGwa9SLDXTefbpCX3FlDDjoWGfl<br>
    qwak1zTydAflosyTJh++VSphzMuQ6sNjSSO7eQbzaF0L2iM12C+K2C2PZmj8oZj2<br>
    rBrzxd/t2xJp3i99uRM0D5FXN5WBfBLLxvfztpBLOaJ+huCGXAstH8wIHnLzmtwf<br>
    W+Qm++NTTrAe0C8NE9wMaNaAB2CduBj3sWKBvpFvkSwmqh61zGOyCnXr1JlLER8j<br>
    6P9XrMxKup0Kq5zimHoGc6ej7aFEnby4EMYpVDtwNmO4q/30r3SEQjUWtlffzV4E<br>
    k8hfMCKNydrXG18Z/JwRS8Y3dXC2xWdueiHUk+dJD+Qpc5kWcExrVBxrLLTMhvz6<br>
    DgLtiSYRI4w1+/ZiorMX<br>
    =mBol<br>
    -----END PGP SIGNATURE-----<br>
    <br>
  </body>
</html>

--------------080807030607010102080105--

From mcr@sandelman.ca  Tue Dec  3 06:15:10 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 015D61ACB4E for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 06:15:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ntNuZRGDi42J for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 06:15:01 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 73E931AD694 for <dhcwg@ietf.org>; Tue,  3 Dec 2013 06:15:01 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 4A9D82002F; Tue,  3 Dec 2013 10:28:13 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id E2C9063B87; Tue,  3 Dec 2013 09:14:54 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id D49C263AEF; Tue,  3 Dec 2013 09:14:54 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <D82E52A5-F0CF-4A0A-AE1B-0440CAAC8CE7@ogud.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <529CA616.3010402@ntp.org> <D82E52A5-F0CF-4A0A-AE1B-0440CAAC8CE7@ogud.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 03 Dec 2013 09:14:54 -0500
Message-ID: <25458.1386080094@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, Ted Lemon <ted.lemon@nominum.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Dec 2013 14:15:10 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


Olafur Gudmundsson <ogud@ogud.com> wrote:
    >> I doubt that the number of "local resolvers" used by the general
    >> populace that can support DNSSEC reach even .1% today, never mind
    >> whether the server has it enabled.
    >>=20

    Olafur> Chrome and Firefox have DNSSEC validation libraries in testing.=
=20
    Olafur> Once they turn that on the numbers will jump.=20
    Olafur> X.509 cert checks happen on edge devices today in large numbers=
.=20
    Olafur> This is not just for DNSSEC this is for any device that wants to
    Olafur> do time check before NTP can finish.=20=20

X.509 checks happen "above" IP, closest to the application where one can ask
the user if they are sure.
DNSSEC checks happen "within" IP --- often on devices without users or
interfaces.

Home/CPE gateways will need to have a process to bootstrap to secure time,
and we will need to write this up in homenet, and if a DHCP option to provi=
de
time to within an hour helps, GOOD.

=2D-=20
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works=20



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBUp3nXoqHRg3pndX9AQIhjwQApp3DwwXv/Fno3MvsLV58+1Y8q7AQuEx6
qnlPZSM+m9iB+c8IQ5rooObUh9JSD6bhldbJzVcokRfPmZsgeXT+9SBFTca8+16K
FD+dT6iQODeoG29Ob0K7I06kFzs7S0lvAap+lBB/PDWvw6cLtPtUR7fh0vtP2iqm
JtZuvZTmBls=
=Fc5X
-----END PGP SIGNATURE-----
--=-=-=--

From Ted.Lemon@nominum.com  Tue Dec  3 06:44:19 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EB0D1AE13B for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 06:44:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 60d9kSFFUkmY for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 06:44:18 -0800 (PST)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id 675B11AE01E for <dhcwg@ietf.org>; Tue,  3 Dec 2013 06:44:18 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKUp3uQAElb5Q8xVBKkb+lizD8WAgt0HWj@postini.com; Tue, 03 Dec 2013 06:44:16 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id CE2F41B8216 for <dhcwg@ietf.org>; Tue,  3 Dec 2013 06:44:15 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id C1108190043; Tue,  3 Dec 2013 06:44:15 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 3 Dec 2013 06:44:15 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <77AB54E8-7150-49DC-A9B6-65CFCDA0D28A@employees.org>
Date: Tue, 3 Dec 2013 09:44:14 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <89B43E38-358E-49C7-ACF1-FDF0E0E4D3DA@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com>, <3219ECB2-F220-403B-984B-7254677528DE@employees.org> <70E0AB50-27FB-4388-96DB-F46D260E553B@cisco.com> <77AB54E8-7150-49DC-A9B6-65CFCDA0D28A@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Dec 2013 14:44:19 -0000

On Dec 3, 2013, at 4:30 AM, Ole Troan <otroan@employees.org> wrote:
> I would expect so. note also for your shepherding document that I have =
threatened an appeal.

If you think this proposal is genuinely useless, then you should feel =
comfortable in implementing the solution you prefer, and ignoring the =
working group's recommendation. But I think you are not comfortable =
doing that=97you are saying this because you expect that you will have =
to implement this, because there will be demand for it.

Is that correct?


From Ted.Lemon@nominum.com  Tue Dec  3 06:49:16 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E37DF1AE11C for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 06:49:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vHCpt9pnkcgC for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 06:49:15 -0800 (PST)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by ietfa.amsl.com (Postfix) with ESMTP id 3B47E1AE11A for <dhcwg@ietf.org>; Tue,  3 Dec 2013 06:49:15 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKUp3vaN9/DSOUrXoHbfjvbDXHojDzTDQE@postini.com; Tue, 03 Dec 2013 06:49:13 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 3D1A21B82B9 for <dhcwg@ietf.org>; Tue,  3 Dec 2013 06:49:12 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 2C3F4190043; Tue,  3 Dec 2013 06:49:12 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 3 Dec 2013 06:49:12 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <03FEB951-90D6-4DAF-9793-76ACFD1A30D3@employees.org>
Date: Tue, 3 Dec 2013 09:49:09 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <EB5FEBF0-476C-42C3-A2EC-8B51CCB30011@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com>, <3219ECB2-F220-403B-984B-7254677528DE@employees.org> <70E0AB50-27FB-4388-96DB-F46D260E553B@cisco.com>, <77AB54E8-7150-49DC-A9B6-65CFCDA0D28A@employees.org> <EB4A3EBF-B08F-4465-A69B-63325E2E3EDA@cisco.com> <03FEB951-90D6-4DAF-9793-76ACFD1A30D3@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Dec 2013 14:49:17 -0000

On Dec 3, 2013, at 6:54 AM, Ole Troan <otroan@employees.org> wrote:
> it appears you think it is important that DHCPv4 uses "only IPv6 =
packets". that's what a tunnel does, why do you think DHCPv4 needs to =
build its own transport?

Ole, this is a straw-man argument.   Nobody ever said that.   I would =
hate to see the working group try to argue this point.   Please try to =
stick to arguing about things people have actually said, or you are just =
creating useless noise and wasting peoples' valuable time.


From kurt@roeckx.be  Tue Dec  3 04:27:32 2013
Return-Path: <kurt@roeckx.be>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F9731AE128 for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 04:27:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bI-HKaO7csZA for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 04:27:30 -0800 (PST)
Received: from juliette.telenet-ops.be (juliette.telenet-ops.be [195.130.137.74]) by ietfa.amsl.com (Postfix) with ESMTP id 12A4E1ADEB6 for <dhcwg@ietf.org>; Tue,  3 Dec 2013 04:27:29 -0800 (PST)
Received: from intrepid.roeckx.be ([94.226.199.45]) by juliette.telenet-ops.be with bizsmtp id x0TR1m00R0zFtyu060TRSQ; Tue, 03 Dec 2013 13:27:26 +0100
Received: by intrepid.roeckx.be (Postfix, from userid 1000) id 5B30F1FE0213; Tue,  3 Dec 2013 13:27:25 +0100 (CET)
Date: Tue, 3 Dec 2013 13:27:25 +0100
From: Kurt Roeckx <kurt@roeckx.be>
To: Danny Mayer <mayer@ntp.org>
Message-ID: <20131203122725.GD2329@roeckx.be>
References: <20131201204227.7978.2067.idtracker@ietfa.amsl.com> <83842BD2-0261-472F-9CA1-AFBFB47EAD91@ogud.com> <C0A2F49F-7695-47E9-8AB0-7F94116437F9@nominum.com> <B0A571B5-438A-47AB-AAA4-00D3FC077E22@ogud.com> <331C154E-1A09-4BDD-A70A-AB67BEA2E1E8@nominum.com> <529BD4CF.6000408@ntp.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <529BD4CF.6000408@ntp.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Mailman-Approved-At: Tue, 03 Dec 2013 07:19:15 -0800
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Ted Lemon <ted.lemon@nominum.com>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Dec 2013 12:27:32 -0000

On Sun, Dec 01, 2013 at 07:31:11PM -0500, Danny Mayer wrote:
> I think we need to figure out how to get around the Catch-22 situation
> of DNSSEC requiring relatively good time and NTP wanting to be able to
> use DNS to find valid NTP servers.

If the box doesn't have an rtc, and so maybe starts in 1970, and
doesn't have anything it can trust there is no way out of it.  You
first need _something_ you can trust be it time or some
certificate.

I do not trust my ISP, so I don't see how I can get that started
and be sure that both my time are correct and dnssec validates
properly.  The only way I see around this is that someone manually
checks that the time is correct.


Kurt


From kurt@roeckx.be  Tue Dec  3 04:49:33 2013
Return-Path: <kurt@roeckx.be>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7E691AE13E for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 04:49:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AFAK0ifjRg-Y for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 04:49:32 -0800 (PST)
Received: from georges.telenet-ops.be (georges.telenet-ops.be [195.130.137.68]) by ietfa.amsl.com (Postfix) with ESMTP id C3EDE1ADEA6 for <dhcwg@ietf.org>; Tue,  3 Dec 2013 04:49:31 -0800 (PST)
Received: from intrepid.roeckx.be ([94.226.199.45]) by georges.telenet-ops.be with bizsmtp id x0pS1m00X0zFtyu060pShZ; Tue, 03 Dec 2013 13:49:28 +0100
Received: by intrepid.roeckx.be (Postfix, from userid 1000) id F0B141FE0213; Tue,  3 Dec 2013 13:49:25 +0100 (CET)
Date: Tue, 3 Dec 2013 13:49:25 +0100
From: Kurt Roeckx <kurt@roeckx.be>
To: Olafur Gudmundsson <ogud@ogud.com>
Message-ID: <20131203124925.GE2329@roeckx.be>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Mailman-Approved-At: Tue, 03 Dec 2013 07:19:15 -0800
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, Ted Lemon <ted.lemon@nominum.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Dec 2013 12:49:34 -0000

On Mon, Dec 02, 2013 at 08:47:01AM -0500, Olafur Gudmundsson wrote:
> 
> The reason for time_t is the dhcp-client can feed that directly into following call:
> 	 settimeofday(const struct timeval *tp, const struct timezone *tzp)

I don't think that is something we want every dhcp client to do.
If ntpd is running you really don't want something else to change
the time.


Kurt


From simon.perreault@viagenie.ca  Tue Dec  3 07:29:13 2013
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD9A71AE155 for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 07:29:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9nSrkkt_jcEj for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 07:29:10 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id D2F4B1AE148 for <dhcwg@ietf.org>; Tue,  3 Dec 2013 07:29:10 -0800 (PST)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:2d71:2167:859d:507d]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 0BFBA401F1 for <dhcwg@ietf.org>; Tue,  3 Dec 2013 10:29:08 -0500 (EST)
Message-ID: <529DF8C3.9090602@viagenie.ca>
Date: Tue, 03 Dec 2013 10:29:07 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <3219ECB2-F220-403B-984B-7254677528DE@employees.org>
In-Reply-To: <3219ECB2-F220-403B-984B-7254677528DE@employees.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Dec 2013 15:29:14 -0000

Le 2013-12-02 14:21, Ole Troan a écrit :
>> Folks, the authors of draft-ietf-dhc-dhcpv4-over-dhcpv6-03 (http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-03.txt) believe it is ready for working group last call. Please review this draft and indicate whether or not you feel it is ready to be published. Your input is important! Please respond by Dec 9th, 2013.
>
> I do not support publication of this document.
> I believe that using DHCPv4 as currently specified (RFC2131, RFC5107, RFC3456, RFC3046) is sufficient also for A+P softwire tunnels.

IMHO Ole's objection is legitimate and my understanding of it is that he 
disagrees with the conclusion of draft-ietf-dhc-v4configuration.

The way I see it, consensus on draft-ietf-dhc-v4configuration is the 
core issue. If we don't already have consensus on the analysis of the 
problem space and of the proposed solutions, I don't see how we can send 
one of the proposed solutions to IESG.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From Ted.Lemon@nominum.com  Tue Dec  3 07:31:23 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 378581AE08C for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 07:31:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dv5JxdOUK2cc for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 07:31:22 -0800 (PST)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id D2AE61AE048 for <dhcwg@ietf.org>; Tue,  3 Dec 2013 07:31:21 -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 DSNKUp35R6c3BvLDihK1//t/wfKwJ3QZso9C@postini.com; Tue, 03 Dec 2013 07:31:19 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 327111B82C6 for <dhcwg@ietf.org>; Tue,  3 Dec 2013 07:31:19 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 15A6F190043; Tue,  3 Dec 2013 07:31:19 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 3 Dec 2013 07:31:18 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <529DF8C3.9090602@viagenie.ca>
Date: Tue, 3 Dec 2013 10:31:17 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <6806356F-C854-48CB-A1FE-CCB3E7451ADE@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <3219ECB2-F220-403B-984B-7254677528DE@employees.org> <529DF8C3.9090602@viagenie.ca>
To: Simon Perreault <simon.perreault@viagenie.ca>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Dec 2013 15:31:23 -0000

On Dec 3, 2013, at 10:29 AM, Simon Perreault =
<simon.perreault@viagenie.ca> wrote:
> The way I see it, consensus on draft-ietf-dhc-v4configuration is the =
core issue. If we don't already have consensus on the analysis of the =
problem space and of the proposed solutions, I don't see how we can send =
one of the proposed solutions to IESG.

Who is "we"?


From simon.perreault@viagenie.ca  Tue Dec  3 07:41:50 2013
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97C761AE105 for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 07:41:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IiTMkK6QzEKE for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 07:41:49 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 115CD1AE120 for <dhcwg@ietf.org>; Tue,  3 Dec 2013 07:41:49 -0800 (PST)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:2d71:2167:859d:507d]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 44590401F1; Tue,  3 Dec 2013 10:41:46 -0500 (EST)
Message-ID: <529DFBBA.3030608@viagenie.ca>
Date: Tue, 03 Dec 2013 10:41:46 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <3219ECB2-F220-403B-984B-7254677528DE@employees.org> <529DF8C3.9090602@viagenie.ca> <6806356F-C854-48CB-A1FE-CCB3E7451ADE@nominum.com>
In-Reply-To: <6806356F-C854-48CB-A1FE-CCB3E7451ADE@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Dec 2013 15:41:50 -0000

Le 2013-12-03 10:31, Ted Lemon a écrit :
> On Dec 3, 2013, at 10:29 AM, Simon Perreault <simon.perreault@viagenie.ca> wrote:
>> The way I see it, consensus on draft-ietf-dhc-v4configuration is the core issue. If we don't already have consensus on the analysis of the problem space and of the proposed solutions, I don't see how we can send one of the proposed solutions to IESG.
>
> Who is "we"?

The working group.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From Ted.Lemon@nominum.com  Tue Dec  3 08:09:23 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAE0E1A1F6F for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 08:09:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DBsyaxlG6sdk for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 08:09:22 -0800 (PST)
Received: from exprod7og108.obsmtp.com (exprod7og108.obsmtp.com [64.18.2.169]) by ietfa.amsl.com (Postfix) with ESMTP id 121A21AE018 for <dhcwg@ietf.org>; Tue,  3 Dec 2013 08:09:22 -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 DSNKUp4CL0DD4RB+zUiHKeViFLtoReoFcGBU@postini.com; Tue, 03 Dec 2013 08:09:19 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 4304C1B82D0 for <dhcwg@ietf.org>; Tue,  3 Dec 2013 08:09:19 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 285A2190043; Tue,  3 Dec 2013 08:09:19 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 3 Dec 2013 08:09:19 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <529DFBBA.3030608@viagenie.ca>
Date: Tue, 3 Dec 2013 11:09:17 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <4129ADB7-8203-4225-AC6F-653962852BED@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <3219ECB2-F220-403B-984B-7254677528DE@employees.org> <529DF8C3.9090602@viagenie.ca> <6806356F-C854-48CB-A1FE-CCB3E7451ADE@nominum.com> <529DFBBA.3030608@viagenie.ca>
To: Simon Perreault <simon.perreault@viagenie.ca>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Dec 2013 16:09:24 -0000

On Dec 3, 2013, at 10:41 AM, Simon Perreault =
<simon.perreault@viagenie.ca> wrote:
> The working group.

Which working group?


From simon.perreault@viagenie.ca  Tue Dec  3 08:20:31 2013
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0BAA1ADFB4 for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 08:20:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yDHHMS7ABlp3 for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 08:20:30 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6DFA11ACCDC for <dhcwg@ietf.org>; Tue,  3 Dec 2013 08:20:30 -0800 (PST)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:2d71:2167:859d:507d]) by jazz.viagenie.ca (Postfix) with ESMTPSA id A19BE401F1; Tue,  3 Dec 2013 11:20:27 -0500 (EST)
Message-ID: <529E04CB.9090008@viagenie.ca>
Date: Tue, 03 Dec 2013 11:20:27 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <3219ECB2-F220-403B-984B-7254677528DE@employees.org> <529DF8C3.9090602@viagenie.ca> <6806356F-C854-48CB-A1FE-CCB3E7451ADE@nominum.com> <529DFBBA.3030608@viagenie.ca> <4129ADB7-8203-4225-AC6F-653962852BED@nominum.com>
In-Reply-To: <4129ADB7-8203-4225-AC6F-653962852BED@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Dec 2013 16:20:32 -0000

Le 2013-12-03 11:09, Ted Lemon a écrit :
>> The working group.
>
> Which working group?

DHC.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From tomasz.mrugalski@gmail.com  Tue Dec  3 10:35:18 2013
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00F8D1AE17E for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 10:35:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5NFbrSAUmrQA for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 10:35:16 -0800 (PST)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 4812C1A8032 for <dhcwg@ietf.org>; Tue,  3 Dec 2013 10:35:16 -0800 (PST)
Received: by mail-we0-f170.google.com with SMTP id w61so14128210wes.15 for <dhcwg@ietf.org>; Tue, 03 Dec 2013 10:35:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=VYtAIEknAFNSzBOfXbuK5G8ChciD6mp7G8VLignq7+c=; b=anIT8Vgtc+mzi9pZpXnchgCBDH0QcGeBq6P81AgmP6Qzi2OPAc9eHtmDRpavVld1wH 2L12541b8+gGz9Ki11bmwZ49kbqCRvEmrb4K71JNfvP9DQ3XrzWOI4ychgtf6Xjuy06q q54HnwU7zBBSEe5SzKyppvfsr8UCdUkBDA0xNOVJjNsaJV5tGqKU3YGLCanBXjrKc0S6 MLq63o9yctbZZC44ZmnIENPkikNZFjEvWCzVQ0iBAHeDx8TfY4oFHkSykjIHu5QZmnOW SXo6/FFs/F/Tc6FqilAqrSeVSv5K4U2NF/onYueX0azw/d8VVxCIx+s348JMvP2MQbfZ RFeg==
X-Received: by 10.180.10.135 with SMTP id i7mr3911598wib.1.1386095713053; Tue, 03 Dec 2013 10:35:13 -0800 (PST)
Received: from ?IPv6:2001:470:6061:0:f66d:4ff:fe96:58f2? ([2001:470:6061:0:f66d:4ff:fe96:58f2]) by mx.google.com with ESMTPSA id dn2sm7857818wid.1.2013.12.03.10.35.11 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 03 Dec 2013 10:35:12 -0800 (PST)
Message-ID: <529E244D.3030308@gmail.com>
Date: Tue, 03 Dec 2013 19:34:53 +0100
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
References: <489D13FBFA9B3E41812EA89F188F018E1AD89A8C@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1AD89A8C@xmb-rcd-x04.cisco.com>
X-Enigmail-Version: 1.5.2
X-TagToolbar-Keys: D20131203193453736
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: [dhcwg] draft-raghuvanshi-dhc-dhcpv6-active-leasequery-00 adoption call successful
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Dec 2013 18:35:18 -0000

On 11.11.2013 17:03, Bernie Volz (volz) wrote:
> This call is being initiated to confirm whether there is indeed WG
> consensus to adopt this work as DHC WG item. Please state whether or not
> you're in favor of the adoption by replying to this mail. If you are not
> in favor, please also state your objections in your response. This
> adoption call will complete on November 25, 2013.
Sorry for a slight delay regarding this summary. I was on vacation last
week. Since Bernie and authors of that drafts work for the same company,
it is better for me to gauge the consensus.

Luckily, that was a very easy thing to do. There's very clear support
for adopting this work without any objections raised, so the adoption
call is successful. Authors, please upload your draft as WG
draft-ietf-dhc-dhcpv6-active-leasequery-00.

There were several voices raised regarding v4 active leasequery.
Together with Bernie we decided that if authors want to pursue v4 active
leasequery, they can do so using separate draft. Although DHCPv4 work is
technically outside of our charter, we asked for permission our
responsible AD if it would be ok to adopt it and got Ted's permission.
IIRC there was v4 active leasequery draft, but it expired. I think
reviving it and then doing adoption call would be the easiest way to
move forward.

On a practical note, having 2 drafts is easier to handle than one, for
multiple reasons. First, the text would be unnecessarily bloated ("in v4
use this, in v6 use that" in many places). Second, v4 has much less
enthusiastic support in the WG, so it is less likely that it will
conclude the standardization path. Third, having 2 drafts is much easier
to gauge consensus on separate drafts. Finally, some implementors are
interested in v6 only, so forcing them the deal with the v4 text is
unnecessary.

Tomek


From tomasz.mrugalski@gmail.com  Tue Dec  3 12:00:28 2013
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F8BA1AE1D9 for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 12:00:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tBLWEGo9r3SS for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 12:00:26 -0800 (PST)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 5AE1D1AE1EA for <dhcwg@ietf.org>; Tue,  3 Dec 2013 12:00:21 -0800 (PST)
Received: by mail-wg0-f49.google.com with SMTP id x12so13792939wgg.4 for <dhcwg@ietf.org>; Tue, 03 Dec 2013 12:00:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=yDvwPVLVH7HKykNlvXCzXZqxHJQ/DZncxZIZQ3cqyNw=; b=Rx00zCIhmbidH1hVh2oyK2cqdijS9FSWxpWzmzc87PQ0W9wmxqG4nNopMNnkbMieoa dBSp9JoYldDB24gRgB6aIUF9QzUMxJgLRd6iyAlddGLckFyCvC51TLzYBMvJAf6qOyae u8vX9fvRtfbVdqRbgMsnBaVg1GmRG/BKOBNBycJkUg2eIJzl5ZC7Eh1bkdBb5nbDaswI 2EJ9ukBc+VnAG6CE7DVlg/LsZ3iu+Q4d90XbOK+l2txruD5Ttwv/F/vj5rtwKPrCnkYT gwae42HfqE+6baRUAT3U4m/SVKzKFpoGnPnIZfSBqVZTR3K7RpgF20NPHR7pbe6NnfIG ipJQ==
X-Received: by 10.194.235.230 with SMTP id up6mr20652229wjc.30.1386100818049;  Tue, 03 Dec 2013 12:00:18 -0800 (PST)
Received: from ?IPv6:2001:470:6061:0:f66d:4ff:fe96:58f2? ([2001:470:6061:0:f66d:4ff:fe96:58f2]) by mx.google.com with ESMTPSA id dn2sm8505179wid.1.2013.12.03.12.00.16 for <dhcwg@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 03 Dec 2013 12:00:17 -0800 (PST)
Message-ID: <529E383E.4050302@gmail.com>
Date: Tue, 03 Dec 2013 20:59:58 +0100
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <489D13FBFA9B3E41812EA89F188F018E1AD98DE0@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1AD98DE0@xmb-rcd-x04.cisco.com>
X-Enigmail-Version: 1.5.2
X-TagToolbar-Keys: D20131203205958906
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 - Respond by Dec 2, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Dec 2013 20:00:28 -0000

On 18.11.2013 18:15, Bernie Volz (volz) wrote:
> Folks, the authors of draft-ietf-dhc-dhcpv6-unknown-msg-03
> (http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-unknown-msg-03)
> believe it is ready for working group last call. Please review this
> draft and indicate whether or not you feel it is ready to be published.
> Your input is important! Please respond by Dec 2^nd , 2013.

I strongly support this document moving forward after the comments below
are addressed.

1. Abstract. The full name of the protocol is "Dynamic Host
Configuration Protocol for IPv6", not "Dynamic Host Configuration
Protocol version 6". (That is also used in section 1) .There is no such
thing as DHCPv6 function node. I propose to update the abstract as:

   Dynamic Host Configuration Protocol for IPv6 (DHCPv6) isn't specific
   about handling messages with unknown types.  This memo describes the
   problems and defines how a DHCPv6 entities node should behave when
   receiving unknown messages. This document updates RFC 3315.

2. Section 3: "Another issue is that, it's not specific in RFC3315 about
what a relay agent... " => "Another issue is that RFC3315 does not
specify what a relay agent..."

3. Section 4.1 "In the case that a new type of relay message is sent to
a relay agent but the relay agent doesn't recognize it, the message is
put into a Relay-forward message and sent to the server.  Then the
server knows the relay agent doesn't support the new message.". The last
sentence is not true. The server can't really distinguish if the relay
supports the message or not, as in both cases the reaction (forward
towards the server) would be the same.

I think removing the last sentence would be helpful here.

Alternatively, perhaps you wanted to discuss the case where the new
message is sent to the relay by the server, relay doesn't support it, so
it forwards it back to the server. That is a worthy thing to mention,
but the current text does not reflect that situation. You may address
that by extending the first sentence a bit: "In the case that a new type
of relay message is sent by the server to a relay agent but the relay
agent doesn't recognize it, the message is put into a Relay-forward
message and sent to the server.".

If you don't have any preference, I would prefer the first approach
(remove second sentence) as it is more generic.

4. Section 4.2 "If the relay agent received messages other than
Relay-forward and Relay-reply, it MUST forward them as is described in
Section 20.1.1 of [RFC3315].". This sentence is incorrect. See RFC6977
and the Reconfigure-reply message definition. Relays are often have
requestor capability, so they are likely to receive LEASEQUERY-REPLY,
LEASEQUERY-DATA and LEASEQUERY-DONE messages as well (See RFC5007 and
5460). There may be other message types that are are targeted at the
relay agent itself (and not expected to be relayed).

Anyway, I think the right thing to say here is:

   If the relay agent received a Relay-forward message, Section 20.1.2
   of [RFC3315] defines the related behavior.  If the relay agent
   received messages other than Relay-forward and Relay-reply and the
   relay agent does not recognize its message type, it MUST forward
   them as is described in Section 20.1.1 of [RFC3315].

Thank you for doing this work. It is very useful clarification.

Tomek





From Ted.Lemon@nominum.com  Tue Dec  3 12:02:54 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 344E41AD8DC for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 12:02:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MMS1CTVbq0Ar for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 12:02:53 -0800 (PST)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by ietfa.amsl.com (Postfix) with ESMTP id E46631ACC88 for <dhcwg@ietf.org>; Tue,  3 Dec 2013 12:02:52 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKUp446hF932d9lxRJSRv63d+qBDSs24dK@postini.com; Tue, 03 Dec 2013 12:02:50 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 2C8621B82D0 for <dhcwg@ietf.org>; Tue,  3 Dec 2013 12:02:50 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 09024190043; Tue,  3 Dec 2013 12:02:50 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 3 Dec 2013 12:02:49 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <529E383E.4050302@gmail.com>
Date: Tue, 3 Dec 2013 15:02:49 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <3E77E4ED-890B-4C09-A9AC-C458B6A07F7A@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1AD98DE0@xmb-rcd-x04.cisco.com> <529E383E.4050302@gmail.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 - Respond by Dec 2, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 03 Dec 2013 20:02:54 -0000

By the way, I recently learned about this resource:

https://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt

This is a list of all the abbreviations the RFC editor is aware of, with =
the ones that need not be expanded marked with an asterisk.   DHCP is =
marked with an asterisk.   So you don't need to write it out=97just =
write DHCP, and the reader is expected to know what it stands for.


From tomasz.mrugalski@gmail.com  Tue Dec  3 16:03:01 2013
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D30EF1ADFA9 for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 16:03:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HJfNt_esisO7 for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 16:02:59 -0800 (PST)
Received: from mail-ee0-x22b.google.com (mail-ee0-x22b.google.com [IPv6:2a00:1450:4013:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id A111F1ADF9D for <dhcwg@ietf.org>; Tue,  3 Dec 2013 16:02:58 -0800 (PST)
Received: by mail-ee0-f43.google.com with SMTP id c13so1921082eek.16 for <dhcwg@ietf.org>; Tue, 03 Dec 2013 16:02:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=4gTy5p3fguzFw0A2IpVYbL1wbNgWeZUOv1algemuVeE=; b=bVilupHIHidKCzP9mm33u4d0vrFW+cQNjvP2qPuYw9rgscvB+WQjUMObh+FVFcPw74 fiFhceSLsdozJE8SmALdz9F6siPyRuKEWZOnPZZ5sqM1WSA8qvFA+TTIy98mda+XDdfl FNwOiboEnjikDj27ghDVqmmv+PX61orque+G6G2FnSCiqM4rZ6RkXh7m59XynNkRKaum lpMm15omkFWSg8ME6sFpz5tPM0Zy2PWWlUjti5O6uQYHVyCiuCNhbd8DY7DneC0X1fTi 9eNp4RkQnonYqnI2KmQeh6Clqc4Xmv3+Xhd/Fcw+5MsxNQzqI83wJ7SkSx3LkmNOv567 1Upg==
X-Received: by 10.14.193.132 with SMTP id k4mr8439619een.55.1386115375314; Tue, 03 Dec 2013 16:02:55 -0800 (PST)
Received: from thomson-osx.local (host-109-107-11-157.ip.jarsat.pl. [109.107.11.157]) by mx.google.com with ESMTPSA id j46sm88075784eew.18.2013.12.03.16.02.53 for <dhcwg@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 03 Dec 2013 16:02:54 -0800 (PST)
Message-ID: <529E712F.5040303@gmail.com>
Date: Wed, 04 Dec 2013 01:02:55 +0100
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: DHC WG <dhcwg@ietf.org>
References: <489D13FBFA9B3E41812EA89F188F018E1ADCE99F@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADCE99F@xmb-rcd-x04.cisco.com>
X-Enigmail-Version: 1.6
X-Forwarded-Message-Id: <489D13FBFA9B3E41812EA89F188F018E1ADCE99F@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] DHCPv6bis mailing list created
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Dec 2013 00:03:02 -0000

Hi everyone,

The IETF secretariat created a dedicated non-WG mailing list for the
DHCPv6-bis work: dhcpv6bis. The list info, mail archive and other
details are here: https://www.ietf.org/mailman/listinfo/dhcpv6bis

We have received more volunteers for the bis work than we could accept.
Thank you for everyone who volunteered. We made a decision to limit the
design/editors team to 6 people at this phase, with Ted as a responsible
AD as a honorable member. The team includes Andrew Yourtchenko, Bernie
Volz, Marcin Siodelski, Michael Richardson, Sheng Jiang, Ted Lemon and
Tomek Mrugalski. Bernie and I made the decision based on prior
contributions, availability to dedicate time for this effort,
involvement in actual implementations and security experience.

If you volunteered or are interested in this work and you're not on the
list, don't despair. There will be plenty of opportunities to
contribute. The editors team is mostly doing editorial work at this
stage. The immediate next steps for the team is to have XMLs for RFC3315
and 3633. Once that is done, the fun part will start. We will have to
merge those two and consider what is the absolute minimum of other
RFCs/drafts that we need to merge, assemble a list of issues to
potentially correct/clarify/fix and then go over them one by one and
decide if we want to address it or not. That discussion will be taking
place on dhcpv6bis list. The list and its archives is open. Feel free to
browse and/or subscribe.

Before/after all important milestones we will be sending updates to dhc
list. We will try to keep the traffic to minimum on dhc, and have all
discussions on dhcpv6bis list. It seems likely that we'll have
presentations during every meeting.

If you are interested in details, we have our repo with nroff, txt and
XML files here: https://github.com/dhcwg/rfc3315bis. Please keep in mind
that this is NOT an official repo, merely a convenient place to store
intermediate files. We will periodically be uploading snapshots of that
work using the usual IETF drill.

Bernie & Tomek



From stenn@stenn.ntp.org  Tue Dec  3 17:40:34 2013
Return-Path: <stenn@stenn.ntp.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B15B1ADFE2 for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 17:40:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gXUTSZ47tQWk for <dhcwg@ietfa.amsl.com>; Tue,  3 Dec 2013 17:40:32 -0800 (PST)
Received: from stenn.ntp.org (stenn.ntp.org [IPv6:2001:4f8:fff7:1::30]) by ietfa.amsl.com (Postfix) with ESMTP id 43A031ADFD8 for <dhcwg@ietf.org>; Tue,  3 Dec 2013 17:40:31 -0800 (PST)
Received: from localhost.ntp.org ([::1] helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1Vo1Rq-0001tQ-05; Wed, 04 Dec 2013 01:40:18 +0000
From: Harlan Stenn <stenn@ntp.org>
To: Kurt Roeckx <kurt@roeckx.be>
In-reply-to: <20131203124925.GE2329@roeckx.be>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <20131203124925.GE2329@roeckx.be>
Comments: In-reply-to Kurt Roeckx <kurt@roeckx.be> message dated "Tue, 03 Dec 2013 13:49:25 +0100."
X-Mailer: MH-E 7.4.2; nmh 1.5; XEmacs 21.4 (patch 22)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Wed, 04 Dec 2013 01:40:17 +0000
Message-Id: <E1Vo1Rq-0001tQ-05@stenn.ntp.org>
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, Ted Lemon <ted.lemon@nominum.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] [ntpwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Dec 2013 01:40:34 -0000

Kurt Roeckx writes:
> > 	 settimeofday(const struct timeval *tp, const struct timezone *tzp)
> 
> I don't think that is something we want every dhcp client to do.
> If ntpd is running you really don't want something else to change
> the time.

There is a difference between DHCP at startup and a DHCP "refresh".

I suspect that a DHCP refresh should leave the clock alone.

For the startup case:

I think the best solution to this problem for LAN-connected devices will
turn out to be PTP.  And if that is not available, if you can't trust
your DHCP server to tell you what time it is, why would you trust it to
give you an IP address?

H

From gnocuil@gmail.com  Wed Dec  4 01:12:37 2013
Return-Path: <gnocuil@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 938991ADF7C for <dhcwg@ietfa.amsl.com>; Wed,  4 Dec 2013 01:12:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a-G6ftUkjIRL for <dhcwg@ietfa.amsl.com>; Wed,  4 Dec 2013 01:12:35 -0800 (PST)
Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 374E31ADF73 for <dhcwg@ietf.org>; Wed,  4 Dec 2013 01:12:35 -0800 (PST)
Received: by mail-qc0-f169.google.com with SMTP id r5so3271324qcx.28 for <dhcwg@ietf.org>; Wed, 04 Dec 2013 01:12:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=bhBIdHhVVz/tMZY4nQ/RYgnyxuJvH5i983onrhefB64=; b=MaU94Dz7NJjtDYqc8GmjgOOAVKp7o2Xcgg5w/W92Mn0jW4bcqVnRRndyaErd78F+qv g9aOvQZhsW2117HC5xZfEHEbB3vFIVOa0z2ar6fGgQ1b2sUdbIN7fptAyv1NWjHoRbSt POPqUNpC/oaSMATUpsa6HitmKwap06ab2NkoYJgsTiJFcUOvM6FIhqjeDu4HadSIDQ9j Ru/k1u9RdPtzAvuc82n+41Tm8ZANTw8VsszYO4qsOy4Nzz2T5KTKxUZbkWX2st9D/KRN F+9IGD3nO09Z3rky5CCFlUuX2QZ6VtKohVTNb9Q7lA/irRoJO29kLnM/bw5B+JYsKuGc sFJw==
X-Received: by 10.49.15.202 with SMTP id z10mr112476932qec.46.1386148352134; Wed, 04 Dec 2013 01:12:32 -0800 (PST)
MIME-Version: 1.0
Received: by 10.96.161.103 with HTTP; Wed, 4 Dec 2013 01:12:11 -0800 (PST)
In-Reply-To: <3E77E4ED-890B-4C09-A9AC-C458B6A07F7A@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1AD98DE0@xmb-rcd-x04.cisco.com> <529E383E.4050302@gmail.com> <3E77E4ED-890B-4C09-A9AC-C458B6A07F7A@nominum.com>
From: Cong Liu <gnocuil@gmail.com>
Date: Wed, 4 Dec 2013 17:12:11 +0800
Message-ID: <CAF+sHxHhSp-=P9E7NLWDsYi_0gy-Qha0GXNko+UVxJz_QrxPbQ@mail.gmail.com>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary=047d7bb03c8422948504ecb1d0e8
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 - Respond by Dec 2, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Dec 2013 09:12:37 -0000

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

Dear all,

I support this document moving forward.

Best Regards,
Cong


2013/12/4 Ted Lemon <ted.lemon@nominum.com>

> By the way, I recently learned about this resource:
>
> https://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt
>
> This is a list of all the abbreviations the RFC editor is aware of, with
> the ones that need not be expanded marked with an asterisk.   DHCP is
> marked with an asterisk.   So you don't need to write it out=97just write
> DHCP, and the reader is expected to know what it stands for.
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>

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

<div dir=3D"ltr"><div><span style=3D"font-family:arial,sans-serif;font-size=
:14px">Dear all,</span><br></div><div><span style=3D"font-family:arial,sans=
-serif;font-size:14px"><br></span></div><div><span style=3D"font-family:ari=
al,sans-serif;font-size:14px">I support this document moving forward.</span=
><br>

</div><div><span style=3D"font-family:arial,sans-serif;font-size:14px"><br>=
</span></div><div><span style=3D"font-family:arial,sans-serif;font-size:14p=
x">Best Regards,</span></div><div><span style=3D"font-family:arial,sans-ser=
if;font-size:14px">Cong</span></div>

<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2013/12/4 Ted=
 Lemon <span dir=3D"ltr">&lt;<a href=3D"mailto:ted.lemon@nominum.com" targe=
t=3D"_blank">ted.lemon@nominum.com</a>&gt;</span><br><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">

By the way, I recently learned about this resource:<br>
<br>
<a href=3D"https://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt"=
 target=3D"_blank">https://www.rfc-editor.org/rfc-style-guide/abbrev.expans=
ion.txt</a><br>
<br>
This is a list of all the abbreviations the RFC editor is aware of, with th=
e ones that need not be expanded marked with an asterisk. =A0 DHCP is marke=
d with an asterisk. =A0 So you don&#39;t need to write it out=97just write =
DHCP, and the reader is expected to know what it stands for.<br>


<div class=3D"HOEnZb"><div class=3D"h5"><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></div></div>

--047d7bb03c8422948504ecb1d0e8--

From gnocuil@gmail.com  Wed Dec  4 01:17:50 2013
Return-Path: <gnocuil@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A3BD1ADFD0 for <dhcwg@ietfa.amsl.com>; Wed,  4 Dec 2013 01:17:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7GrtMjxYKbxz for <dhcwg@ietfa.amsl.com>; Wed,  4 Dec 2013 01:17:48 -0800 (PST)
Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 806B61ADF73 for <dhcwg@ietf.org>; Wed,  4 Dec 2013 01:17:48 -0800 (PST)
Received: by mail-qc0-f174.google.com with SMTP id n7so1894656qcx.33 for <dhcwg@ietf.org>; Wed, 04 Dec 2013 01:17:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=wcKDB11UayznEMD7HQZwT5gwmdogPJsC3a3G9vV0l5A=; b=Ru4KGd61ZUo1aX6aQYMeCp+huYSwiyTk429auu8H7BhVA1sjby2naN/vHcDkYTtGQL xgM9UcOeIGdc0crB24JlseXO4dTGK2opHhalCh62tCPtnuOvnHEkoILZKA1d1xZfeL7j u53N5Fg1Th1A0vuEU0PSKBs/FNr2C6kfetBvP6RbzFbdJIzKx5TAHxXl1+ug90tWLGki 9ShyBUn23Tn/2PvV/jNAW/A/UyqZZtL9eutFEt8CnNkixH1h72V4/MNWbDop4JOSqWpT fHrrVHlgIB93CCW7yBw1pgqaAhDrVhW2TlYZB1aCAtXr4AR0/7/zH3iLnf6vVpduMwNQ ZLUA==
X-Received: by 10.49.15.202 with SMTP id z10mr112518149qec.46.1386148665465; Wed, 04 Dec 2013 01:17:45 -0800 (PST)
MIME-Version: 1.0
Received: by 10.96.161.103 with HTTP; Wed, 4 Dec 2013 01:17:25 -0800 (PST)
In-Reply-To: <529E04CB.9090008@viagenie.ca>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <3219ECB2-F220-403B-984B-7254677528DE@employees.org> <529DF8C3.9090602@viagenie.ca> <6806356F-C854-48CB-A1FE-CCB3E7451ADE@nominum.com> <529DFBBA.3030608@viagenie.ca> <4129ADB7-8203-4225-AC6F-653962852BED@nominum.com> <529E04CB.9090008@viagenie.ca>
From: Cong Liu <gnocuil@gmail.com>
Date: Wed, 4 Dec 2013 17:17:25 +0800
Message-ID: <CAF+sHxGsLjpbN1fjR_w5MM7OAf+h=2_Pn33gcoTw=V8Xp=1zvQ@mail.gmail.com>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary=047d7bb03c84cf9f7d04ecb1e28f
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Dec 2013 09:17:50 -0000

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

Dear all,

I support this document moving forward. And I support the conclusion in
current draft-ietf-dhc-v4configuration-02 that
DHCPv4oDHCPv6 is the best underlying approach for provisioning IPv4
parameters over an IPv6 only network.

Best Regards,
Cong


2013/12/4 Simon Perreault <simon.perreault@viagenie.ca>

> Le 2013-12-03 11:09, Ted Lemon a =E9crit :
>
>  The working group.
>>>
>>
>> Which working group?
>>
>
> DHC.
>
>
> Simon
> --
> DTN made easy, lean, and smart --> http://postellation.viagenie.ca
> NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
> STUN/TURN server               --> http://numb.viagenie.ca
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>

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

<div dir=3D"ltr"><div style=3D"font-family:arial,sans-serif;font-size:14px"=
>Dear all,<br></div><div style=3D"font-family:arial,sans-serif;font-size:14=
px"><br></div><div><font face=3D"arial, sans-serif"><span style=3D"font-siz=
e:14px">I support this document moving forward. And I support the conclusio=
n in current=A0draft-ietf-dhc-v4configuration-02 that</span></font></div>

<div><span style=3D"font-family:arial;font-size:1em;color:rgb(0,0,0)">DHCPv=
4oDHCPv6 is=A0</span><font color=3D"#000000"><span style=3D"font-size:14px"=
>the best underlying approach for=A0</span></font><span style=3D"font-size:=
14px;color:rgb(0,0,0)">provisioning IPv4 parameters over an IPv6 only netwo=
rk.</span></div>

<div style=3D"font-family:arial,sans-serif;font-size:14px"><br></div><div s=
tyle=3D"font-family:arial,sans-serif;font-size:14px">Best Regards,</div><di=
v style=3D"font-family:arial,sans-serif;font-size:14px">Cong</div></div><di=
v class=3D"gmail_extra">

<br><br><div class=3D"gmail_quote">2013/12/4 Simon Perreault <span dir=3D"l=
tr">&lt;<a href=3D"mailto:simon.perreault@viagenie.ca" target=3D"_blank">si=
mon.perreault@viagenie.ca</a>&gt;</span><br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

Le 2013-12-03 11:09, Ted Lemon a =E9crit :<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The working group.<br>
</blockquote>
<br>
Which working group?<br>
</blockquote>
<br></div>
DHC.<div class=3D"im HOEnZb"><br>
<br>
Simon<br>
-- <br>
DTN made easy, lean, and smart --&gt; <a href=3D"http://postellation.viagen=
ie.ca" target=3D"_blank">http://postellation.viagenie.<u></u>ca</a><br>
NAT64/DNS64 open-source =A0 =A0 =A0 =A0--&gt; <a href=3D"http://ecdysis.via=
genie.ca" target=3D"_blank">http://ecdysis.viagenie.ca</a><br>
STUN/TURN server =A0 =A0 =A0 =A0 =A0 =A0 =A0 --&gt; <a href=3D"http://numb.=
viagenie.ca" target=3D"_blank">http://numb.viagenie.ca</a><br></div><div cl=
ass=3D"HOEnZb"><div class=3D"h5">
______________________________<u></u>_________________<br>
dhcwg mailing list<br>
<a href=3D"mailto:dhcwg@ietf.org" target=3D"_blank">dhcwg@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dhcwg" target=3D"_blank">h=
ttps://www.ietf.org/mailman/<u></u>listinfo/dhcwg</a><br>
</div></div></blockquote></div><br></div>

--047d7bb03c84cf9f7d04ecb1e28f--

From internet-drafts@ietf.org  Wed Dec  4 01:44:11 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 556F91AE22B; Wed,  4 Dec 2013 01:44:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bqdKpEBGTJ7M; Wed,  4 Dec 2013 01:44:09 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B2F6E1ADFCC; Wed,  4 Dec 2013 01:44: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: 4.83.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131204094409.23363.90608.idtracker@ietfa.amsl.com>
Date: Wed, 04 Dec 2013 01:44:09 -0800
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-active-leasequery-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Dec 2013 09:44:11 -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 Group =
of the IETF.

	Title           : DHCPv6 Active Leasequery
	Author(s)       : Dushyant Raghuvanshi
                          Kim Kinnear
                          Deepak Kukrety
	Filename        : draft-ietf-dhc-dhcpv6-active-leasequery-00.txt
	Pages           : 25
	Date            : 2013-12-03

Abstract:
   The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) has been
   extended with a Leasequery capability that allows a requestor to
   request information about DHCPv6 bindings.  That mechanism is limited
   to queries for DHCPv6 binding data updates until the time DHCPv6
   server receive the Leasequery request.  Continuous update of an
   external requestor with Leasequery data is sometimes desired.  This
   document expands on the DHCPv6 Leasequery protocol, and allows for
   active transfer of real-time DHCPv6 binding information data via TCP.
   This document also extends DHCPv6 Bulk Leasequery by adding new
   options.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-active-leasequery

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-active-leasequery-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From kkinnear@cisco.com  Wed Dec  4 08:24:37 2013
Return-Path: <kkinnear@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A565C1AE2B9 for <dhcwg@ietfa.amsl.com>; Wed,  4 Dec 2013 08:24:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.502
X-Spam-Level: 
X-Spam-Status: No, score=-9.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0X7FW1N1u8Nv for <dhcwg@ietfa.amsl.com>; Wed,  4 Dec 2013 08:24:35 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id 7DDE11AE105 for <dhcwg@ietf.org>; Wed,  4 Dec 2013 08:24:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2887; q=dns/txt; s=iport; t=1386174272; x=1387383872; h=mime-version:subject:from:date:cc: content-transfer-encoding:message-id:references:to; bh=+NGcp/wrG0ML1+WvGMjrrK/QlZcT7u39CLir7+axz+Q=; b=WDlSehgq37FA8nsPgWffv4dhHwa3e6F8JUVLPtbDxFkpUsgosUYDj66T QI7InQfX4e/xvnLxToXVRBsyBTBfeIvsZmyTOs8pSBAezpm0XSWLXOU+0 cEqkRMe5HnnYDann4Nr7x8A87xwADkuL6vI3UHaNm/TLeOC6gfej5qw0V A=;
X-IronPort-AV: E=Sophos;i="4.93,825,1378857600";  d="scan'208";a="4287222"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by alln-iport-6.cisco.com with ESMTP; 04 Dec 2013 16:24:32 +0000
Received: from [10.131.32.164] ([10.131.32.164]) (authenticated bits=0) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id rB4GOVJn009348 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 4 Dec 2013 16:24:32 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Kim Kinnear <kkinnear@cisco.com>
Date: Wed, 4 Dec 2013 11:24:30 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D5A32E2B-CAA1-4ECB-AA86-7CD567738A62@cisco.com>
References: <20131204150103.9960.74169.idtracker@ietfa.amsl.com>
To: dhcwg@ietf.org
X-Mailer: Apple Mail (2.1510)
X-Authenticated-User: kkinnear
Cc: "Bernie Volz \(volz\)" <volz@cisco.com>, Kim Kinnear <kkinnear@cisco.com>
Subject: [dhcwg] New Version Notification for draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Dec 2013 16:24:37 -0000

Folks,

During the adoption discussion about DHCPv6 Active Leasequery there
was some discussion about having a corresponding DHCPv4 Active
Leasequery capability.  If there is sufficient interest in a DHCPv4
Active Leasequery capability to parallel the DHCPv6 capability that
was adopted as a DHC WG work item recently, then we can decide whether
or not we want to have two drafts moving toward two RFC's, or combine
them into one draft.

But the first question is whether or not there is sufficient interest
in having a DHCPv4 Active Leasequery capability at all!

In order to help decide this question, I have updated the existing
DHCPv4 Active Leasequery draft from a couple of years ago, and
resubmitted it as an individual submission -- as recommended by Bernie
and Tomek.

Below you can find the information on how to find this new draft.

Regards -- Kim


Begin forwarded message:

> From: <internet-drafts@ietf.org>
> Subject: New Version Notification for =
draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
> Date: December 4, 2013 10:01:03 AM EST
> To: Bernie Volz <volz@cisco.com>, Mark Stapp <mjs@cisco.com>, Kim =
Kinnear <kkinnear@cisco.com>, Neil Russell <neil.e.russell@gmail.com>
>=20
>=20
> A new version of I-D, =
draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
> has been successfully submitted by Kim Kinnear and posted to the
> IETF repository.
>=20
> Filename:	 draft-kinnear-dhc-dhcpv4-active-leasequery
> Revision:	 02
> Title:		 Active DHCPv4 Lease Query
> Creation date:	 2013-12-04
> Group:		 Individual Submission
> Number of pages: 22
> URL:             =
http://www.ietf.org/internet-drafts/draft-kinnear-dhc-dhcpv4-active-leaseq=
uery-02.txt
> Status:          =
http://datatracker.ietf.org/doc/draft-kinnear-dhc-dhcpv4-active-leasequery=

> Htmlized:        =
http://tools.ietf.org/html/draft-kinnear-dhc-dhcpv4-active-leasequery-02
> Diff:            =
http://www.ietf.org/rfcdiff?url2=3Ddraft-kinnear-dhc-dhcpv4-active-leasequ=
ery-02
>=20
> Abstract:
>   The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has been
>   extended with a Leasequery capability that allows a client to =
request
>   information about DHCPv4 bindings.  That mechanism is limited to
>   queries for individual bindings.  In some situations individual
>   binding queries may not be efficient, or even possible.  In =
addition,
>   continuous update of an external client with Leasequery data is
>   sometimes desired. This document expands on the DHCPv4 Leasequery
>   protocol, and allows for active transfer of near real-time DHCPv4
>   address binding information data via TCP.
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> The IETF Secretariat
>=20


From volz@cisco.com  Wed Dec  4 08:46:45 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D8191AE078 for <dhcwg@ietfa.amsl.com>; Wed,  4 Dec 2013 08:46:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kjHt3y9-cDbj for <dhcwg@ietfa.amsl.com>; Wed,  4 Dec 2013 08:46:42 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id A7E231ADFB4 for <dhcwg@ietf.org>; Wed,  4 Dec 2013 08:46:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4129; q=dns/txt; s=iport; t=1386175600; x=1387385200; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=G6l9LYPVv/s0JIXJz8cHJCtLrKdxyrLbshIlSARWx9M=; b=jH33PtQUIo1KjfwKEypGgt5yFjh8wyCtR/c/cYiGfCx/SGEoGuXzozw+ 4vR2MAdPSaCelcTSXs9b+2FASPyUDPnqwJApz0iPmj9t8hWMKcKNNlkUN kCat5yto/LlaZLkw5EFwW2sSbe2sXhE5Rn3c3Q1I+r22nWDNOzX46IKKe o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiEFANpbn1KtJV2Y/2dsb2JhbABagwc4TQa4Y4EjFnSCJQEBAQMBHR0/BQcGARkDAQEBCxQxER0JAQQBCQQFCAGHZwMJBggFukQNhxMXjG2BOQcBAR4xDYMagRMDlDGBeIMbiyqFOYFrgT6BaAkXIg
X-IronPort-AV: E=Sophos;i="4.93,825,1378857600"; d="scan'208";a="289365138"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-6.cisco.com with ESMTP; 04 Dec 2013 16:46:39 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id rB4GkdSD022458 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 4 Dec 2013 16:46:39 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0123.003; Wed, 4 Dec 2013 10:46:39 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Kim Kinnear (kkinnear)" <kkinnear@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
Thread-Index: Ac7xD0TQ86CV+plkQwGdrBXmDcXNyw==
Date: Wed, 4 Dec 2013 16:46:38 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1ADD09A3@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.65.118]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Dec 2013 16:46:45 -0000

Hi all:

This is a WG Call for Adoption for http://tools.ietf.org/html/draft-kinnear=
-dhc-dhcpv4-active-leasequery-02. This call is being initiated to determine=
 whether there is WG consensus to adopt this work as DHC WG item. Please st=
ate whether or not you're in favor of the adoption by replying to this mail=
. If you are not in favor, please also state your objections in your respon=
se. This adoption call will complete on December 18, 2013.

This call is being initiated because during the call for adoption for draft=
-raghuvanshi-dhc-dhcpv6-active-leasequery-00, which was just adopted, sever=
al people asked about the related DHCPv4 work. Kim republished the DHCPv4 d=
raft (with minor updates) as it had expired a while ago. So, we are seeking=
 input as to whether the WG should now also work on the DHCPv4 version of a=
ctive leasequery, given that the DHCPv6 version was adopted.

Regards,
Tomek & Bernie

-----Original Message-----
From: Kim Kinnear (kkinnear)=20
Sent: Wednesday, December 04, 2013 11:25 AM
To: dhcwg@ietf.org
Cc: Kim Kinnear (kkinnear); Bernie Volz (volz); Tomek Mrugalski
Subject: New Version Notification for draft-kinnear-dhc-dhcpv4-active-lease=
query-02.txt


Folks,

During the adoption discussion about DHCPv6 Active Leasequery there was som=
e discussion about having a corresponding DHCPv4 Active Leasequery capabili=
ty.  If there is sufficient interest in a DHCPv4 Active Leasequery capabili=
ty to parallel the DHCPv6 capability that was adopted as a DHC WG work item=
 recently, then we can decide whether or not we want to have two drafts mov=
ing toward two RFC's, or combine them into one draft.

But the first question is whether or not there is sufficient interest in ha=
ving a DHCPv4 Active Leasequery capability at all!

In order to help decide this question, I have updated the existing
DHCPv4 Active Leasequery draft from a couple of years ago, and resubmitted =
it as an individual submission -- as recommended by Bernie and Tomek.

Below you can find the information on how to find this new draft.

Regards -- Kim


Begin forwarded message:

> From: <internet-drafts@ietf.org>
> Subject: New Version Notification for=20
> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
> Date: December 4, 2013 10:01:03 AM EST
> To: Bernie Volz <volz@cisco.com>, Mark Stapp <mjs@cisco.com>, Kim=20
> Kinnear <kkinnear@cisco.com>, Neil Russell <neil.e.russell@gmail.com>
>=20
>=20
> A new version of I-D,=20
> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
> has been successfully submitted by Kim Kinnear and posted to the IETF=20
> repository.
>=20
> Filename:	 draft-kinnear-dhc-dhcpv4-active-leasequery
> Revision:	 02
> Title:		 Active DHCPv4 Lease Query
> Creation date:	 2013-12-04
> Group:		 Individual Submission
> Number of pages: 22
> URL:             http://www.ietf.org/internet-drafts/draft-kinnear-dhc-dh=
cpv4-active-leasequery-02.txt
> Status:          http://datatracker.ietf.org/doc/draft-kinnear-dhc-dhcpv4=
-active-leasequery
> Htmlized:        http://tools.ietf.org/html/draft-kinnear-dhc-dhcpv4-acti=
ve-leasequery-02
> Diff:            http://www.ietf.org/rfcdiff?url2=3Ddraft-kinnear-dhc-dhc=
pv4-active-leasequery-02
>=20
> Abstract:
>   The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has been
>   extended with a Leasequery capability that allows a client to request
>   information about DHCPv4 bindings.  That mechanism is limited to
>   queries for individual bindings.  In some situations individual
>   binding queries may not be efficient, or even possible.  In addition,
>   continuous update of an external client with Leasequery data is
>   sometimes desired. This document expands on the DHCPv4 Leasequery
>   protocol, and allows for active transfer of near real-time DHCPv4
>   address binding information data via TCP.
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of=20
> submission until the htmlized version and diff are available at tools.iet=
f.org.
>=20
> The IETF Secretariat
>=20


From matthew@dempsky.org  Thu Dec  5 10:18:24 2013
Return-Path: <matthew@dempsky.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9204F1AE0E1 for <dhcwg@ietfa.amsl.com>; Thu,  5 Dec 2013 10:18:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dNRMj0l4Xf9b for <dhcwg@ietfa.amsl.com>; Thu,  5 Dec 2013 10:18:22 -0800 (PST)
Received: from mail-la0-f47.google.com (mail-la0-f47.google.com [209.85.215.47]) by ietfa.amsl.com (Postfix) with ESMTP id 9145E1AE06C for <dhcwg@ietf.org>; Thu,  5 Dec 2013 10:18:22 -0800 (PST)
Received: by mail-la0-f47.google.com with SMTP id ep20so10489527lab.34 for <dhcwg@ietf.org>; Thu, 05 Dec 2013 10:18:18 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=Vtu+9SzrCZoR9ESXPwp5FHA7UjNWOvU6RHc/Wr/hqhw=; b=asbbfcDN4gRHUegwQgmnUUyrz7xRzKn+3pIH78QvBl063s2lzPVkZCud3zgrkWqDTJ cue6JsbMZXgnX2VE32SyhgA4GTMUakLwFb3lyDa/AdeoNSmtDzInZKLBATvbiBYyO/UR dtfaEDw7iVSKPBtWFYfkut/PGQgNZnHdFu9WipQ9n2lgqghqNrxF2lUskild7apMteAy 35Qg+zjEtTJG08/1xBGUo3tSPpN/gHlPN3Q8j27W/hJYqstPchkEa1/D3pv3KCk+zS7m 8ZNY3NZSnN9i3V4Nr6Fwgv/j7kBi9+AORkyJ92u173dFqoo3RpEmh5DyOJm6AW1/TmQJ o+ZQ==
X-Gm-Message-State: ALoCoQn6/vFPBIDGpejKkLvk80luy5+ggLgBMZpLZ3Vw7Ojq7tLmAWk9KRPWjVbQfLp8E7/y3G9/
MIME-Version: 1.0
X-Received: by 10.112.151.42 with SMTP id un10mr5249181lbb.7.1386267498455; Thu, 05 Dec 2013 10:18:18 -0800 (PST)
Received: by 10.152.22.132 with HTTP; Thu, 5 Dec 2013 10:18:18 -0800 (PST)
Date: Thu, 5 Dec 2013 10:18:18 -0800
Message-ID: <CANKkrzEew4WtYpa33GL3QB-8Wd8jGZTEv5djkOr9LbOMa7+icw@mail.gmail.com>
From: Matthew Dempsky <matthew@dempsky.org>
To: dhcwg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [dhcwg] Any documentation for handling /32 IPv4 assignments from DHCP?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 05 Dec 2013 18:18:24 -0000

In dhcp-4.2.5-P1/client/scripts/linux, there's this code for adding
routes based on the Router (3) and Subnet Mask (1) options:

    for router in $new_routers; do
      if [ "x$new_subnet_mask" = "x255.255.255.255" ] ; then
        route add -host $router dev $interface
      fi
      route add default gw $router $metric_arg dev $interface
    done

Is this special case logic for subnet_mask==255.255.255.255 codified
anywhere?  I'm working on adding similar logic to OpenBSD's DHCP
client (so OpenBSD can connect to a network currently supported by ISC
DHCP on Linux), but I'm having trouble finding any authoritative
documentation explaining the correct behavior here.

In particular, ISC DHCP 4.2.5-P1 only adds the "dev" route for Router
(3), but I'm wondering if they should be added for Static Route (33)
and/or Classless Static Route Option (121) too?

Thanks

From internet-drafts@ietf.org  Fri Dec  6 04:13:03 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD2351AE337; Fri,  6 Dec 2013 04:13:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MwPCo0FUizu3; Fri,  6 Dec 2013 04:13:01 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D50771ADED8; Fri,  6 Dec 2013 04:13:01 -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: 4.83.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131206121301.28214.78204.idtracker@ietfa.amsl.com>
Date: Fri, 06 Dec 2013 04:13:01 -0800
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-v4configuration-03.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 06 Dec 2013 12:13:04 -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 Group =
of the IETF.

	Title           : Provisioning IPv4 Configuration Over IPv6 Only Networks
	Author(s)       : Branimir Rajtar
                          Ian Farrer
	Filename        : draft-ietf-dhc-v4configuration-03.txt
	Pages           : 18
	Date            : 2013-12-06

Abstract:
   As IPv6 becomes more widely adopted, some service providers are
   choosing to deploy IPv6 only networks without dual-stack
   functionality for IPv4.  However, as access to IPv4 based services
   will continue to be a requirement for the foreseeable future, IPv4
   over IPv6 mechanisms, such as softwire tunnels are being developed.

   In order to provision end-user's hosts with the IPv4 configuration
   necessary for such mechanisms, a number of different approaches have
   been proposed.  This memo discusses each of the proposals, identifies
   the benefits and drawbacks and recommends a single approach as the
   basis for future deployment and development.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-v4configuration

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-v4configuration-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dhc-v4configuration-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From otroan@employees.org  Fri Dec  6 06:09:22 2013
Return-Path: <otroan@employees.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EA431ADF9D for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 06:09:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X6lSazLFbHdk for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 06:09:21 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 2C1651ADF43 for <dhcwg@ietf.org>; Fri,  6 Dec 2013 06:09:21 -0800 (PST)
X-Files: signature.asc : 496
X-IronPort-AV: E=Sophos;i="4.93,841,1378857600"; d="asc'?scan'208";a="1177609"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by aer-iport-2.cisco.com with ESMTP; 06 Dec 2013 14:09:16 +0000
Received: from dhcp-10-61-103-53.cisco.com (dhcp-10-61-103-53.cisco.com [10.61.103.53]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rB6E9CQg010688 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 6 Dec 2013 14:09:13 GMT
Content-Type: multipart/signed; boundary="Apple-Mail=_E6AB0AC5-8FED-46F4-B6DC-14AC6F4150FB"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <77AB54E8-7150-49DC-A9B6-65CFCDA0D28A@employees.org>
Date: Fri, 6 Dec 2013 15:09:11 +0100
Message-Id: <E69EB59A-B0BD-479A-B392-1E24C1C868E5@employees.org>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com>, <3219ECB2-F220-403B-984B-7254677528DE@employees.org> <70E0AB50-27FB-4388-96DB-F46D260E553B@cisco.com> <77AB54E8-7150-49DC-A9B6-65CFCDA0D28A@employees.org>
To: "Bernie Volz (volz)" <volz@cisco.com>
X-Mailer: Apple Mail (2.1822)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 06 Dec 2013 14:09:22 -0000

--Apple-Mail=_E6AB0AC5-8FED-46F4-B6DC-14AC6F4150FB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

>> We are trying to solve the general problem when all that can be =
assured is the ability to send IPv6 packets.
>=20
> I have asked multiple times for an explanation of what you are trying =
to achieve, and what makes this a "general problem".

anyone with an answer to this?

cheers,
Ole

--Apple-Mail=_E6AB0AC5-8FED-46F4-B6DC-14AC6F4150FB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJSodqIAAoJEFuJXizso86guYIIAKwSK/MEydXLodnboYKpArzT
KE/gr5656pWbmN7C3bmqpf5472aAMu6opR4g1Gqp74sQ0Tgy77NJ5EOSZtwvBQlB
0ZjQO+CDkVoeSQAuD/BiUKiBTU3qS1a+yzGCNZmo7Ob7j7gFtaIQ64OV3o9/E9np
Y+UKiXk0XogmObuujkJn7jw64MZuAbZKborRMGYyRjd/Qzsn3lXGJ4xANI0Ln/x8
E3EZ4W6pnrIQVju9N9jSDuYdAyxrw9idOGJV334tIPs/OrwXzJpelCQMAlB27oXh
BKc2OgSN8Q59hH53OqnlzAIYAxdPc7CRWVRgfkix2ZpDhSTANMqjLieO4Gb0c0g=
=xDyi
-----END PGP SIGNATURE-----

--Apple-Mail=_E6AB0AC5-8FED-46F4-B6DC-14AC6F4150FB--

From volz@cisco.com  Fri Dec  6 07:05:42 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EADAE1AE050 for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 07:05:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level: 
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Prw2UBL47ETr for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 07:05:36 -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 9DF211ADFF3 for <dhcwg@ietf.org>; Fri,  6 Dec 2013 07:05:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=62160; q=dns/txt; s=iport; t=1386342332; x=1387551932; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=bCP/7B2popILlUgS15EqQEp5d6GP3iIR845VsHzRJQA=; b=dGtBcxux60TnOq0TVBtN8oTCqXS5FkomC5x7azpvboovIvH7HTwW4yd6 GWKdgePBx3BEaFnR+a0gFP9epXOeXrUeoTffeYLZhVtkJ7TbyFB8m8a29 iLXBTSbXxG+tpTtqIMwHMjQjWbgBZUbAd7xjIPgyu7HRgb5heiy5TK/pc E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnAHAE3noVKtJV2Z/2dsb2JhbABZgkNEOFOwL4hRgSEWbQeCJQEBAQQMDhM6CwcQAgEIEQEDAQELFgEGBzIUAwYIAQEEDgUIAYd5DcB6F45fMQYBBoMagRMDk29ChROQY4Mpgio
X-IronPort-AV: E=Sophos;i="4.93,841,1378857600";  d="scan'208,217";a="289855702"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-6.cisco.com with ESMTP; 06 Dec 2013 15:05:30 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id rB6F5UhA004424 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 6 Dec 2013 15:05:30 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.03.0123.003; Fri, 6 Dec 2013 09:05:30 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
Thread-Index: Ac7pYNYYaEg536DmSXaLna21+HapNwJLQwCw
Date: Fri, 6 Dec 2013 15:05:29 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1ADD590C@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.244.216]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1ADD590Cxmbrcdx04ciscoc_"
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 06 Dec 2013 07:09:27 -0800
Cc: "draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org" <draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 06 Dec 2013 15:05:42 -0000

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

Hi:

As the assigned document shepherd for this work, I have reviewed it fairly =
carefully. And, I have the follow more significant comments regarding this =
draft:


1.       I've already commented on the two vs. one option issue. I think si=
mplifying this to use a single option which is returned by the server to en=
able this feature and, optionally, specify a list of IPv6 addresses to whic=
h to send the packets.

2.       I think we should rename the messages to be BOOTP, not BOOT. BOOTP=
REQUESTV6 and BOOTPREPLYV6 (and Bootp-request-v6, Bootp-reply-v6). (I also =
wonder whether we really need the v6, but it may help in clarifying this fr=
om standard BOOTP packets, so OK to leave it.)

3.       At the end of section 7 (Use of the Boot-request-v6 Unicast flag),=
 I think it would be useful to add a note to make it clear that this flag r=
epresents how the DHCPv4 packet would have been sent, not how the v6 packet=
 is sent. (Note: The "Unicast" flag reflects the how the DHCPv4 packet woul=
d have been sent; not how the DHCPv6 packet itself is sent.)

4.       In section 8 (4o6 DHCP Client Behavior), should we be clear that e=
verything is 'interface' specific? 'Client' here is a bit open to its meani=
ng. Though on the other hand, everything with respect to DHCP is typically =
interface specific so perhaps clarifying this isn't that critical.

5.       Also in section 8, it may be useful to add something about IPv6 so=
urce address considerations ... Section 13 of RFC3315 doesn't mention the I=
Pv6 source address, but it is important that packets sent to a global addre=
ss have sufficient scope. Though in most cases, this can be left to the ker=
nel (if the source address is unspecified).

6.       Also in section 8, for "There are no explicit transmission paramet=
ers associated with a Boot[p]-request-v6 message." I think adding ", as thi=
s is governed by the DHCPv4, [RFC2131], "state machine"." Or something like=
 that.

7.       In section 10, 2nd paragraph, I wonder if "...broadcast or unicast=
 address if DHCPv4 protocol was used" should be "broadcast or unicast addre=
ss if IPv4 has been used." The packet is transmitted over IPv4. But this is=
 minor.

8.       In section 12 (IANA Considerations), please improve this to make i=
t clear exactly what registry. You may want to look at the SOLMAX draft tex=
t:

IANA is requested to assign one option code each for OPTION_SOL_MAX_RT and =
OPTION_INF_MAX_RT from the "DHCP Option Codes" table of the Dynamic Host Co=
nfiguration Protocol for IPv6 (DHCPv6) Registry.

There have been a few cases where IANA used the wrong table; while we will =
hopefully catch that ...

You could even provide the URL for the table (http://www.iana.org/assignmen=
ts/dhcpv6-parameters/dhcpv6-parameters.xml).

9.       A general issue ... I wonder whether we have a kind of catch-22. A=
s DHCP is interface specific, and the tunnel interface may not be able to '=
come up' until after the address is assigned, what interface is this 'DHCPv=
4' (4o6) client associated with? Is it the v6 interface? Or a 'provisional'=
 tunnel interface? Or, is this left up to the implementation to deal with (=
since in one sense it probably doesn't matter much - except of course if on=
e was trying to bring up multiple tunnel interfaces over the same v6 interf=
ace; but that requires other special logic so may not be a concern).


As well as the following minor nits (note that I did NOT apply changes to t=
he message names as indicated in 2 above):

In section 1, Introduction:

   This document describes a transport mechanism to carry DHCPv4
   messages using DHCPv6 protocol, for the dynamic provisioning of IPv4
   addresses and other DHCPv4 specific configuration parameters across
   IPv6-only networks.  It leverages the existing infrastructure for
   DHCPv4, e.g. failover, DNS updates, leasequery, etc.

Line 2, should be (add the, remove comma):

   messages using the DHCPv6 protocol for the dynamic provisioning of IPv4

In section 3, Terminology:


   CPE:                  Customer Premises Equipment (also known as

                         Customer Provided Equipment), which provides

                         the access of devices connected to Local Area

                         Network (typically at customer's site/home) to

                         Internet Service Provider's network.
Should be (add a and the twice):


   CPE:                  Customer Premises Equipment (also known as

                         Customer Provided Equipment), which provides

                         the access of devices connected to a Local Area

                         Network (typically at the customer's site/home) to

                         The Internet Service Provider's network.

In section 4, Architecture Overview:


   Typically, a 4o6 DHCP client communicates with the 4o6 DHCP servers

   using well-known All_DHCP_Relay_Agents_and_Servers multicast address.

Should be (add the):


   Typically, a 4o6 DHCP client communicates with the 4o6 DHCP servers

   Using the well-known All_DHCP_Relay_Agents_and_Servers multicast address=
.

And also:


   Client SHOULD request the 4o6 Server Address Option from a DHCPv6

   server and the server may be configured to respond to the client with

   one such option that contains one or more unicast addresses of the

   4o6 DHCP Servers.  The server includes 4o6 Server Address Option in

   Advertise and Reply messages.  The format of the option is defined in

   Section 6.3<http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6=
-03#section-6.3>.

Should be (add the twice):


   The client SHOULD request the 4o6 Server Address Option from a DHCPv6

   server and the server may be configured to respond to the client with

   one such option that contains one or more unicast addresses of the

   4o6 DHCP Servers.  The server includes the 4o6 Server Address Option in

   Advertise and Reply messages.  The format of the option is defined in

   Section 6.3<http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6=
-03#section-6.3>.

In section 5.2, Message formats:


   msg-type        Identifies message type.  It can be either

                   BOOTREQUESTV6 (TBD) or BOOTREPLYV6 (TBD) which

                   corresponds to the Boot-request-v6 or Boot-reply-v6,

                   respectively.

Should be (add the):


   msg-type        Identifies the message type.  It can be either

                   BOOTREQUESTV6 (TBD) or BOOTREPLYV6 (TBD) which

                   corresponds to the Boot-request-v6 or Boot-reply-v6,

                   respectively.

In section 7, Use of the Boot-Request-v4 Unicast Flag


   A DHCPv4 client conforming to the [RFC2131<http://tools.ietf.org/html/rf=
c2131>] may send its DHCPREQUEST

   message to either broadcast or unicast address depending on its

   state.  For example, the client in the RENEWING state uses a unicast

   address to contact a DHCPv4 server to renew its lease.  The client in

   the REBINDING state uses a broadcast address.  If there is a DHCPv4

   relay agent in the middle, a client in the RENEWING state may send a

   DHCPREQUEST message to the unicast address of the relay agent.  In

   such case the server can't find out whether the client sent a message

   to a unicast or broadcast address and thus it can't determine the

   client's state.  [RFC5010<http://tools.ietf.org/html/rfc5010>] introduce=
d the "Flags Suboption" which

   relay agents add to relayed messages to indicate whether broadcast or

   unicast was used by the client.

Should be (remove the, replace "it can't find out" with "the server may be =
unable to", replace "can't" with "is unable to"):


   A DHCPv4 client conforming to[RFC2131<http://tools.ietf.org/html/rfc2131=
>] may send its DHCPREQUEST

   message to either broadcast or unicast address depending on its

   state.  For example, the client in the RENEWING state uses a unicast

   address to contact a DHCPv4 server to renew its lease.  The client in

   the REBINDING state uses a broadcast address.  If there is a DHCPv4

   relay agent in the middle, a client in the RENEWING state may send a

   DHCPREQUEST message to the unicast address of the relay agent.  In

   such case the server is unable to determine whether the client sent a me=
ssage

   to a unicast or broadcast address and thus the server may be unable to d=
etermine the

   client's state.  [RFC5010<http://tools.ietf.org/html/rfc5010>] introduce=
d the "Flags Suboption" which

   relay agents add to relayed messages to indicate whether broadcast or

   unicast was used by the client.

And in the following, drop "the" before the RFC?


   In DHCPv4 over DHCPv6, IPv6 is used to deliver DHCPv4 messages to the

   4o6 DHCP Server.  There is no relation between the outer IPv6 address

   and the inner DHCPv4 message.  So the server is not able to know

   whether the DHCPv4 messages should have been sent using broadcast or

   unicast in IPv4 by checking the IPv6 address.  This is similar to the

   case addressed by the [RFC5010<http://tools.ietf.org/html/rfc5010>].

And in the following add "The" before Client (The client MUST...):


   In order to allow the server to determine the client's state, the

   "Unicast" flag is carried in the Boot-request-v6 message.  Client

   MUST set this flag to 1 when the DHCPv4 message would have been sent

In section 8, 4o6 DHCP Client Behavior:

In the first bullet, change doesn't to does not.

And:


   o  If the client receives both options, it SHOULD enable the DHCPv4

      -over-DHCPv6 function and send requests to the unicast address(es)

      in the 4o6 Server Address Option.

Should be (add SHOULD and add each of):


   o  If the client receives both options, it SHOULD enable the DHCPv4

      -over-DHCPv6 function and SHOULD send requests to each of the unicast=
 address(es)

      in the 4o6 Server Address Option.

Add "the" before "DHCP protocol" in:


   The client signaled by the server to use DHCPv4 over DHCPv6 SHOULD

   cease to send DHCPv4 messages using DHCP protocol described in

Also:


   Client MUST follow rules defined in Section 7<http://tools.ietf.org/html=
/draft-ietf-dhc-dhcpv4-over-dhcpv6-03#section-7> when setting Unicast

   flag.

May be improved by adding "based on the DHCPv4 destination):


   Client MUST follow rules defined in Section 7<http://tools.ietf.org/html=
/draft-ietf-dhc-dhcpv4-over-dhcpv6-03#section-7> when setting Unicast

   Flag based on the DHCPv4 destination.

And in:


   On receiving a Boot-reply-v6 message, the client MUST look for the

   BOOTP Message option within this message.  If this option is not

   found, the Boot-reply-v6 message is discarded.  If the BOOTP Message

   Option presents, the client extracts the DHCPv4 message it contains

   and processes it as described in section 4.4 of [RFC2131]<http://tools.i=
etf.org/html/rfc2131#section-4.4>.

The "presents" is odd. Did you mean "is present"?

And finally, in section 11:


   which can cause an amplification attack.  To avoid this, the client

   MUST check if there are repeated IPv6 addresses in a 4o6 Server

   Address Option when receiving one.  The client MUST ignore those

   duplicated unicast IPv6 addresses.

Perhaps change 'repeated' to 'duplicate'? As you use that in the next sente=
nce, so better to be consistent?


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Sunday, November 24, 2013 5:03 PM
To: dhcwg@ietf.org
Subject: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by=
 Dec 9, 2013


Folks, the authors of draft-ietf-dhc-dhcpv4-over-dhcpv6-03 (http://tools.ie=
tf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-03.txt) believe it is ready f=
or working group last call. Please review this draft and indicate whether o=
r not you feel it is ready to be published. Your input is important! Please=
 respond by Dec 9th, 2013.



At the time of this writing, there is no IPR reported against this draft.



Bernie will be the document shepherd.



Thanks,


-          Tomek & Bernie


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
h2
	{mso-style-priority:9;
	mso-style-link:"Heading 2 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:18.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:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.Heading2Char
	{mso-style-name:"Heading 2 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 2";
	font-weight:bold;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.grey
	{mso-style-name:grey;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:131949666;
	mso-list-type:hybrid;
	mso-list-template-ids:-2079948192 -261062568 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:6;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1
	{mso-list-id:348676280;
	mso-list-type:hybrid;
	mso-list-template-ids:-1464332512 618420372 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2
	{mso-list-id:866522167;
	mso-list-type:hybrid;
	mso-list-template-ids:1690722640 1420754368 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l2:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l2:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l2:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l2:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l2:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l2:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l2:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l3
	{mso-list-id:1493788668;
	mso-list-type:hybrid;
	mso-list-template-ids:-1133855032 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l3:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l3:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l3:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l3:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi:<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">As the assigned docume=
nt shepherd for this work, I have reviewed it fairly carefully. And, I have=
 the follow more significant comments regarding this draft:<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo3"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">1.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">I&#8217;ve alr=
eady commented on the two vs. one option issue. I think simplifying this to=
 use a single option which is returned by the server to enable this feature=
 and, optionally, specify a list of IPv6
 addresses to which to send the packets.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo3"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">2.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">I think we sho=
uld rename the messages to be BOOTP, not BOOT. BOOTPREQUESTV6 and BOOTPREPL=
YV6 (and Bootp-request-v6, Bootp-reply-v6). (I also wonder whether we reall=
y need the v6, but it may help in
 clarifying this from standard BOOTP packets, so OK to leave it.)<o:p></o:p=
></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo3"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">3.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">At the end of =
section 7 (Use of the Boot-request-v6 Unicast flag), I think it would be us=
eful to add a note to make it clear that this flag represents how the DHCPv=
4 packet would have been sent, not
 how the v6 packet is sent. (Note: The &#8220;Unicast&#8221; flag reflects =
the how the DHCPv4 packet would have been sent; not how the DHCPv6 packet i=
tself is sent.)<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo3"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">4.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">In section 8 (=
4o6 DHCP Client Behavior), should we be clear that everything is &#8216;int=
erface&#8217; specific? &#8216;Client&#8217; here is a bit open to its mean=
ing. Though on the other hand, everything with respect to
 DHCP is typically interface specific so perhaps clarifying this isn&#8217;=
t that critical.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo3"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">5.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Also in sectio=
n 8, it may be useful to add something about IPv6 source address considerat=
ions &#8230; Section 13 of RFC3315 doesn&#8217;t mention the IPv6 source ad=
dress, but it is important that packets sent to
 a global address have sufficient scope. Though in most cases, this can be =
left to the kernel (if the source address is unspecified).<o:p></o:p></span=
></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo3"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">6.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Also in sectio=
n 8, for &#8220;There are no explicit transmission parameters associated wi=
th a Boot[p]-request-v6 message.&#8221; I think adding &#8220;, as this is =
governed by the DHCPv4, [RFC2131], &#8220;state machine&#8221;.&#8221;
 Or something like that.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo3"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">7.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">In section 10,=
 2<sup>nd</sup> paragraph, I wonder if &#8220;&#8230;broadcast or unicast a=
ddress if DHCPv4 protocol was used&#8221; should be &#8220;broadcast or uni=
cast address if IPv4 has been used.&#8221; The packet is transmitted
 over IPv4. But this is minor.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo3"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">8.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">In section 12 =
(IANA Considerations), please improve this to make it clear exactly what re=
gistry. You may want to look at the SOLMAX draft text:<o:p></o:p></span></p=
>
<p class=3D"MsoListParagraph" style=3D"margin-left:1.0in"><span style=3D"co=
lor:#1F497D">IANA is requested to assign one option code each for OPTION_SO=
L_MAX_RT and OPTION_INF_MAX_RT from the &quot;DHCP Option Codes&quot; table=
 of the Dynamic Host Configuration Protocol for
 IPv6 (DHCPv6) Registry.<o:p></o:p></span></p>
<p class=3D"MsoListParagraph"><span style=3D"color:#1F497D">There have been=
 a few cases where IANA used the wrong table; while we will hopefully catch=
 that &#8230;<o:p></o:p></span></p>
<p class=3D"MsoListParagraph"><span style=3D"color:#1F497D">You could even =
provide the URL for the table (</span><a href=3D"http://www.iana.org/assign=
ments/dhcpv6-parameters/dhcpv6-parameters.xml">http://www.iana.org/assignme=
nts/dhcpv6-parameters/dhcpv6-parameters.xml</a>).<span style=3D"color:#1F49=
7D"><o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l3 level=
1 lfo3"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">9.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">A general issu=
e &#8230; I wonder whether we have a kind of catch-22. As DHCP is interface=
 specific, and the tunnel interface may not be able to &#8216;come up&#8217=
; until after the address is assigned, what interface
 is this &#8216;DHCPv4&#8217; (4o6) client associated with? Is it the v6 in=
terface? Or a &#8216;provisional&#8217; tunnel interface? Or, is this left =
up to the implementation to deal with (since in one sense it probably doesn=
&#8217;t matter much &#8211; except of course if one was trying to bring
 up multiple tunnel interfaces over the same v6 interface; but that require=
s other special logic so may not be a concern).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">As well as the followi=
ng minor nits (note that I did NOT apply changes to the message names as in=
dicated in 2 above):<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In section 1, Introduc=
tion:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp=
; This document describes a transport mechanism to carry DHCPv4<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp=
; messages using DHCPv6 protocol, for the dynamic provisioning of IPv4<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp=
; addresses and other DHCPv4 specific configuration parameters across<o:p><=
/o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp=
; IPv6-only networks.&nbsp; It leverages the existing infrastructure for<o:=
p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp=
; DHCPv4, e.g. failover, DNS updates, leasequery, etc.<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Line 2, should be (add=
 the, remove comma):<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal" style=3D"page-break-before:always"><span style=3D"fo=
nt-size:12.0pt;font-family:&quot;Courier New&quot;;color:black">&nbsp;&nbsp=
; messages using the DHCPv6 protocol for the dynamic provisioning of IPv4<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In section 3, Terminol=
ogy:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; CPE:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Customer Premises Eq=
uipment (also known as<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Customer Provided Equipment), which provides<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; the access of devices connected to Local Area<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Network (typically at customer's site/home) to<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Internet Service Provider's network.<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Should be (add a and t=
he twice):<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; CPE:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Customer Premises Eq=
uipment (also known as<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Customer Provided Equipment), which provides<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; the access of devices connected to a Local Area<o:p></o:p></span></pre=
>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Network (typically at the customer's site/home) to<o:p></o:p></span></=
pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; The Internet Service Provider's network.<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In section 4, Architec=
ture Overview:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; Typically, a 4o6 DHCP client communicates with the 4=
o6 DHCP servers<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; using well-known All_DHCP_Relay_Agents_and_Servers m=
ulticast address.<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Should be (add the):<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; Typically, a 4o6 DHCP client communicates with the 4=
o6 DHCP servers<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; Using the well-known All_DHCP_Relay_Agents_and_Serve=
rs multicast address.<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">And also:<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; Client SHOULD request the 4o6 Server Address Option =
from a DHCPv6<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; server and the server may be configured to respond t=
o the client with<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; one such option that contains one or more unicast ad=
dresses of the<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; 4o6 DHCP Servers.&nbsp; The server includes 4o6 Serv=
er Address Option in<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; Advertise and Reply messages.&nbsp; The format of th=
e option is defined in<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; <a href=3D"http://tools.ietf.org/html/draft-ietf-dhc=
-dhcpv4-over-dhcpv6-03#section-6.3">Section 6.3</a>.<o:p></o:p></span></pre=
>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Should be (add the twi=
ce):<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; The client SHOULD request the 4o6 Server Address Opt=
ion from a DHCPv6<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; server and the server may be configured to respond t=
o the client with<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; one such option that contains one or more unicast ad=
dresses of the<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; 4o6 DHCP Servers.&nbsp; The server includes the 4o6 =
Server Address Option in<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; Advertise and Reply messages.&nbsp; The format of th=
e option is defined in<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; <a href=3D"http://tools.ietf.org/html/draft-ietf-dhc=
-dhcpv4-over-dhcpv6-03#section-6.3">Section 6.3</a>.<o:p></o:p></span></pre=
>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In section 5.2, Messag=
e formats:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; msg-type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I=
dentifies message type.&nbsp; It can be either<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; BOOTREQUESTV6 (TBD) or BOOTREPL=
YV6 (TBD) which<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; corresponds to the Boot-request=
-v6 or Boot-reply-v6,<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; respectively.<o:p></o:p></span>=
</pre>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Should be (add the):<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; msg-type&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I=
dentifies the message type.&nbsp; It can be either<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;BOOTREQUESTV6 (TBD) or BOOTREPL=
YV6 (TBD) which<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; corresponds to the Boot-request=
-v6 or Boot-reply-v6,<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; respectively.<o:p></o:p></span>=
</pre>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In section 7, Use of t=
he Boot-Request-v4 Unicast Flag<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; A DHCPv4 client conforming to the [<a href=3D"http:/=
/tools.ietf.org/html/rfc2131" title=3D"&quot;Dynamic Host Configuration Pro=
tocol&quot;">RFC2131</a>] may send its DHCPREQUEST<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; message to either broadcast or unicast address depen=
ding on its<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; state.&nbsp; For example, the client in the RENEWING=
 state uses a unicast<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; address to contact a DHCPv4 server to renew its leas=
e.&nbsp; The client in<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; the REBINDING state uses a broadcast address.&nbsp; =
If there is a DHCPv4<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; relay agent in the middle, a client in the RENEWING =
state may send a<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; DHCPREQUEST message to the unicast address of the re=
lay agent.&nbsp; In<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; such case the server can't find out whether the clie=
nt sent a message<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; to a unicast or broadcast address and thus it can't =
determine the<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; client's state.&nbsp; [<a href=3D"http://tools.ietf.=
org/html/rfc5010" title=3D"&quot;The Dynamic Host Configuration Protocol Ve=
rsion 4 (DHCPv4) Relay Agent Flags Suboption&quot;">RFC5010</a>] introduced=
 the &quot;Flags Suboption&quot; which<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; relay agents add to relayed messages to indicate whe=
ther broadcast or<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; unicast was used by the client.<o:p></o:p></span></p=
re>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Should be (remove the,=
 replace &#8220;it can&#8217;t find out&#8221; with &#8220;the server may b=
e unable to&#8221;, replace &#8220;can&#8217;t&#8221; with &#8220;is unable=
 to&#8221;):<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; A DHCPv4 client conforming to[<a href=3D"http://tool=
s.ietf.org/html/rfc2131" title=3D"&quot;Dynamic Host Configuration Protocol=
&quot;">RFC2131</a>] may send its DHCPREQUEST<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; message to either broadcast or unicast address depen=
ding on its<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; state.&nbsp; For example, the client in the RENEWING=
 state uses a unicast<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; address to contact a DHCPv4 server to renew its leas=
e.&nbsp; The client in<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; the REBINDING state uses a broadcast address.&nbsp; =
If there is a DHCPv4<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; relay agent in the middle, a client in the RENEWING =
state may send a<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; DHCPREQUEST message to the unicast address of the re=
lay agent.&nbsp; In<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; such case the server is unable to determine whether =
the client sent a message<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; to a unicast or broadcast address and thus the serve=
r may be unable to determine the<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; client's state.&nbsp; [<a href=3D"http://tools.ietf.=
org/html/rfc5010" title=3D"&quot;The Dynamic Host Configuration Protocol Ve=
rsion 4 (DHCPv4) Relay Agent Flags Suboption&quot;">RFC5010</a>] introduced=
 the &quot;Flags Suboption&quot; which<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; relay agents add to relayed messages to indicate whe=
ther broadcast or<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; unicast was used by the client.<o:p></o:p></span></p=
re>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">And in the following, =
drop &#8220;the&#8221; before the RFC?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; In DHCPv4 over DHCPv6, IPv6 is used to deliver DHCPv=
4 messages to the<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; 4o6 DHCP Server.&nbsp; There is no relation between =
the outer IPv6 address<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; and the inner DHCPv4 message.&nbsp; So the server is=
 not able to know<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; whether the DHCPv4 messages should have been sent us=
ing broadcast or<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; unicast in IPv4 by checking the IPv6 address.&nbsp; =
This is similar to the<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; case addressed by the [<a href=3D"http://tools.ietf.=
org/html/rfc5010" title=3D"&quot;The Dynamic Host Configuration Protocol Ve=
rsion 4 (DHCPv4) Relay Agent Flags Suboption&quot;">RFC5010</a>].<o:p></o:p=
></span></pre>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">And in the following a=
dd &#8220;The&#8221; before Client (The client MUST&#8230;):<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; In order to allow the server to determine the client=
's state, the<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; &quot;Unicast&quot; flag is carried in the Boot-requ=
est-v6 message.&nbsp; Client<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; MUST set this flag to 1 when the DHCPv4 message woul=
d have been sent<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In section 8, 4o6 DHCP=
 Client Behavior:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">In the first bullet, c=
hange doesn&#8217;t to does not.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">And:<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; o&nbsp; If the client receives both options, it SHOU=
LD enable the DHCPv4<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -over-DHCPv6 function and send req=
uests to the unicast address(es)<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in the 4o6 Server Address Option.<=
o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Should be (add SHOULD =
and add each of):<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; o&nbsp; If the client receives both options, it SHOU=
LD enable the DHCPv4<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -over-DHCPv6 function and SHOULD s=
end requests to each of the unicast address(es)<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in the 4o6 Server Address Option.<=
o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Add &#8220;the&#8221; =
before &#8220;DHCP protocol&#8221; in:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; The client signaled by the server to use DHCPv4 over=
 DHCPv6 SHOULD<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; cease to send DHCPv4 messages using DHCP protocol de=
scribed in<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Also:<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; Client MUST follow rules defined in <a href=3D"http:=
//tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-03#section-7">Secti=
on 7</a> when setting Unicast<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; flag.<o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">May be improved by add=
ing &#8220;based on the DHCPv4 destination):<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; Client MUST follow rules defined in <a href=3D"http:=
//tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-03#section-7">Secti=
on 7</a> when setting Unicast<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; Flag based on the DHCPv4 destination.<o:p></o:p></sp=
an></pre>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">And in:<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; On receiving a Boot-reply-v6 message, the client MUS=
T look for the<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; BOOTP Message option within this message.&nbsp; If t=
his option is not<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; found, the Boot-reply-v6 message is discarded.&nbsp;=
 If the BOOTP Message<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; Option presents, the client extracts the DHCPv4 mess=
age it contains<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; and processes it as described in <a href=3D"http://t=
ools.ietf.org/html/rfc2131#section-4.4">section&nbsp;4.4 of [RFC2131]</a>.<=
o:p></o:p></span></pre>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The &#8220;presents&#8=
221; is odd. Did you mean &#8220;is present&#8221;?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">And finally, in sectio=
n 11:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; which can cause an amplification attack.&nbsp; To av=
oid this, the client<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; MUST check if there are repeated IPv6 addresses in a=
 4o6 Server<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; Address Option when receiving one.&nbsp; The client =
MUST ignore those<o:p></o:p></span></pre>
<pre style=3D"page-break-before:always"><span style=3D"font-size:12.0pt;col=
or:black">&nbsp;&nbsp; duplicated unicast IPv6 addresses.<o:p></o:p></span>=
</pre>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Perhaps change &#8216;=
repeated&#8217; to &#8216;duplicate&#8217;? As you use that in the next sen=
tence, so better to be consistent?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo5"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Bernie<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> dhcwg [m=
ailto:dhcwg-bounces@ietf.org]
<b>On Behalf Of </b>Bernie Volz (volz)<br>
<b>Sent:</b> Sunday, November 24, 2013 5:03 PM<br>
<b>To:</b> dhcwg@ietf.org<br>
<b>Subject:</b> [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Res=
pond by Dec 9, 2013<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Folks, the authors of draft-ietf-dhc-dhcpv4-over-=
dhcpv6-03 (<a href=3D"http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over=
-dhcpv6-03.txt">http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv=
6-03.txt</a>) believe it is ready for
 working group last call. Please review this draft and indicate whether or =
not you feel it is ready to be published. Your input is important! Please r=
espond by Dec 9<sup>th</sup>, 2013.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">At the time of this writing, there is no IPR repo=
rted against this draft.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Bernie will be the document shepherd.<o:p></o:p><=
/p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l2 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Tomek &amp; Bernie<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1ADD590Cxmbrcdx04ciscoc_--

From Ted.Lemon@nominum.com  Fri Dec  6 08:09:04 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B2A21AE091 for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 08:09:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zHrA-Ou6Q8U3 for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 08:09:00 -0800 (PST)
Received: from exprod7og119.obsmtp.com (exprod7og119.obsmtp.com [64.18.2.16]) by ietfa.amsl.com (Postfix) with ESMTP id DD1CD1AE0A0 for <dhcwg@ietf.org>; Fri,  6 Dec 2013 08:08:59 -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 DSNKUqH2mInXlAA2Px9wwDnglFA3ASGlogTI@postini.com; Fri, 06 Dec 2013 08:08:56 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 29EB51B82E2 for <dhcwg@ietf.org>; Fri,  6 Dec 2013 08:08:56 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id F04A6190043; Fri,  6 Dec 2013 08:08:55 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 6 Dec 2013 08:08:55 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <E69EB59A-B0BD-479A-B392-1E24C1C868E5@employees.org>
Date: Fri, 6 Dec 2013 11:08:53 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <E8FCD266-CAE7-4625-A07B-ACD20CB15A34@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com>, <3219ECB2-F220-403B-984B-7254677528DE@employees.org> <70E0AB50-27FB-4388-96DB-F46D260E553B@cisco.com> <77AB54E8-7150-49DC-A9B6-65CFCDA0D28A@employees.org> <E69EB59A-B0BD-479A-B392-1E24C1C868E5@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 06 Dec 2013 16:09:04 -0000

On Dec 6, 2013, at 9:09 AM, Ole Troan <otroan@employees.org> wrote:
> anyone with an answer to this?

DHCPv4 over DHCPv6 provides a mechanism for transporting DHCPv4 packets =
over an IPv6 network layer without the support of a pre-established =
4over6 tunnel.   It has the added benefit of providing information about =
the IPv6 network over which the request is sent, as a result of having =
passed through one or more DHCPv6 relay agents.   This information would =
not be available in the case of a DHCPv4 packet carried directly over a =
pre-established tunnel.

I would characterize it as a solution that can work well in the context =
of an existing IPv6 network with DHCPv6 service, and that is general in =
the sense that it does not assume a particular use model other than =
"DHCPv4 over a plain IPv6 network."   But you are right to point out =
that it is not a "general solution" if "general" is left unqualified.


From simon.perreault@viagenie.ca  Fri Dec  6 08:17:55 2013
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54EC91AE030 for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 08:17:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.502
X-Spam-Level: 
X-Spam-Status: No, score=-0.502 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BGqTl2Lp5TJl for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 08:17:49 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 34E521ADFFB for <dhcwg@ietf.org>; Fri,  6 Dec 2013 08:17:49 -0800 (PST)
Received: from porto.nomis80.org (ringo.viagenie.ca [206.123.31.67]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 376EA401FC for <dhcwg@ietf.org>; Fri,  6 Dec 2013 11:17:45 -0500 (EST)
Message-ID: <52A1F8A8.3020200@viagenie.ca>
Date: Fri, 06 Dec 2013 11:17:44 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 06 Dec 2013 16:17:55 -0000

Le 2013-11-24 17:02, Bernie Volz (volz) a écrit :
> Folks, the authors of draft-ietf-dhc-dhcpv4-over-dhcpv6-03
> (http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-03.txt)
> believe it is ready for working group last call. Please review this
> draft and indicate whether or not you feel it is ready to be published.
> Your input is important! Please respond by Dec 9^th , 2013.

Here's my review. I tried not to read Bernie's review so as not to be 
influenced by it, so there may be some overlap.

The major comments are:

1. Section "4. Architecture Overview" ends before explaining a crucial 
point: what does the client do with the IPv4 configuration it has 
received? For example, when it receives an IPv4 address, does it assign 
it to an interface? Which one? We need a general idea of how this works 
before this section is over.

(Now that I have read the full draft, I realize that this is not 
discussed at all. If this is out of scope, then that means this RFC is 
not readily usable without another RFC describing how to use it in one 
particular context. That could be fine if that's the intent, but then 
that should be stated explicitly in this RFC.)

2. I already mentioned that we should have only one option for enabling 
and conveying the 4o6 server address (unicast or multicast). Just go 
with Bernie's suggestion.

Minor comments inline...

Simon

>
>
>
>
> DHC Working Group                                                 Q. Sun
> Internet-Draft                                                    Y. Cui
> Intended status: Standards Track                     Tsinghua University
> Expires: May 26, 2014                                       M. Siodelski
>                                                                      ISC
>                                                              S. Krishnan
>                                                                 Ericsson
>                                                                I. Farrer
>                                                      Deutsche Telekom AG
>                                                        November 22, 2013
>
>
>                       DHCPv4 over DHCPv6 Transport
>                   draft-ietf-dhc-dhcpv4-over-dhcpv6-03
>
> Abstract
>
>    IPv4 connectivity is still needed as networks migrate towards IPv6.
>    Users require IPv4 configuration even if the uplink to their service
>    provider supports IPv6 only.  This document describes a mechanism for
>    obtaining IPv4 configuration information dynamically in IPv6 networks
>    by carrying DHCPv4 messages over DHCPv6 transport.  Two new DHCPv6
>    messages as well as new DHCPv6 options are defined for the purpose of
>    conveying DHCPv4 messages through IPv6 networks.
>
> Status of This Memo
>
>    This Internet-Draft is submitted in full conformance with the
>    provisions of BCP 78 and BCP 79.
>
>    Internet-Drafts are working documents of the Internet Engineering
>    Task Force (IETF).  Note that other groups may also distribute
>    working documents as Internet-Drafts.  The list of current Internet-
>    Drafts is at http://datatracker.ietf.org/drafts/current/.
>
>    Internet-Drafts are draft documents valid for a maximum of six months
>    and may be updated, replaced, or obsoleted by other documents at any
>    time.  It is inappropriate to use Internet-Drafts as reference
>    material or to cite them other than as "work in progress."
>
>    This Internet-Draft will expire on May 26, 2014.
>
> Copyright Notice
>
>    Copyright (c) 2013 IETF Trust and the persons identified as the
>    document authors.  All rights reserved.
>
>    This document is subject to BCP 78 and the IETF Trust's Legal
>
>
>
> Sun, et al.               Expires May 26, 2014                  [Page 1]
> 
> Internet-Draft             DHCPv4 over DHCPv6              November 2013
>
>
>    Provisions Relating to IETF Documents
>    (http://trustee.ietf.org/license-info) in effect on the date of
>    publication of this document.  Please review these documents
>    carefully, as they describe your rights and restrictions with respect
>    to this document.  Code Components extracted from this document must
>    include Simplified BSD License text as described in Section 4.e of
>    the Trust Legal Provisions and are provided without warranty as
>    described in the Simplified BSD License.
>
> Table of Contents
>
>    1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
>    2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
>    3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
>    4.  Architecture Overview . . . . . . . . . . . . . . . . . . . .   3
>    5.  New DHCPv6 Messages . . . . . . . . . . . . . . . . . . . . .   5
>      5.1.  Message Types . . . . . . . . . . . . . . . . . . . . . .   5
>      5.2.  Message Formats . . . . . . . . . . . . . . . . . . . . .   5
>      5.3.  Boot-request-v6 Message Flags . . . . . . . . . . . . . .   6
>      5.4.  Boot-reply-v6 Message Flags . . . . . . . . . . . . . . .   6
>    6.  New DHCPv6 Options  . . . . . . . . . . . . . . . . . . . . .   7
>      6.1.  BOOTP Message Option Format . . . . . . . . . . . . . . .   7
>      6.2.  DHCPv4-over-DHCPv6 Enable Option Format . . . . . . . . .   7
>      6.3.  4o6 Server Address Option Format  . . . . . . . . . . . .   8
>    7.  Use of the Boot-request-v6 Unicast Flag . . . . . . . . . . .   8
>    8.  4o6 DHCP Client Behavior  . . . . . . . . . . . . . . . . . .   9
>    9.  Relay Agent Behavior  . . . . . . . . . . . . . . . . . . . .  10
>    10. 4o6 DHCP Server Behavior  . . . . . . . . . . . . . . . . . .  11
>    11. Security Considerations . . . . . . . . . . . . . . . . . . .  11
>    12. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
>    13. Contributors List . . . . . . . . . . . . . . . . . . . . . .  12
>    14. References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
>      14.1.  Normative References . . . . . . . . . . . . . . . . . .  12
>      14.2.  Informative References . . . . . . . . . . . . . . . . .  13
>    Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13
>
> 1.  Introduction
>
>    As the migration towards IPv6 continues, IPv6-only networks will
>    become more prevalent.  At the same time, IPv4 connectivity will
>    continue to be provided as a service over IPv6-only networks.  In
>    addition to providing IPv4 addresses for clients of this service,
>    other IPv4 configuration parameters may also need to be provided
>    (e.g.  addresses of IPv4-only services).
>
>    This document describes a transport mechanism to carry DHCPv4
>    messages using DHCPv6 protocol, for the dynamic provisioning of IPv4
>    addresses and other DHCPv4 specific configuration parameters across
>
>
>
> Sun, et al.               Expires May 26, 2014                  [Page 2]
> 
> Internet-Draft             DHCPv4 over DHCPv6              November 2013
>
>
>    IPv6-only networks.  It leverages the existing infrastructure for
>    DHCPv4, e.g. failover, DNS updates, leasequery, etc.
>
> 2.  Requirements Language
>
>    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>    document are to be interpreted as described in [RFC2119].
>
> 3.  Terminology
>
>    This document makes use of the following terms:
>
>    4o6 DHCP Client:      A DHCP client which supports both DHCPv6
>                          protocol [RFC3315] as well as the DHCPv4 over
>                          DHCPv6 protocol described in this document.
>                          Such a client is capable to request its IPv6

s/to request/of requesting/

>                          configuration using DHCPv6 and IPv4
>                          configuration using DHCPv4 over DHCPv6.
>
>    4o6 DHCP Server:      A DHCP server that is capable of processing
>                          DHCPv4 packets encapsulated in the BOOTP
>                          Message option (defined below).
>
>    CPE:                  Customer Premises Equipment (also known as
>                          Customer Provided Equipment), which provides
>                          the access of devices connected to Local Area
>                          Network (typically at customer's site/home) to
>                          Internet Service Provider's network.
>
>    DHCPv4 over DHCPv6:   A protocol described in this document, which is
>                          used to carry DHCPv4 messages in the payload of
>                          DHCPv6 messages.
>
> 4.  Architecture Overview
>
>    The architecture described in this document addresses a typical use
>    case, where a DHCP client's uplink supports IPv6 only and the Service
>    Provider's network supports IPv6 and limited IPv4 services.  In this
>    scenario, the client can only use the IPv6 network to access IPv4
>    services.  So it must configure IPv4 services using IPv6 as the
>    underlying network protocol.
>
>    Although the purpose of this document is to address the problem of
>    communication between the DHCPv4 client and the DHCPv4 server, the
>    mechanism that it describes does not restrict the transported
>    messages types only to DHCPv4.  As the DHCPv4 message is a special
>    type of the BOOTP message, BOOTP messages can also be transported
>
>
>
> Sun, et al.               Expires May 26, 2014                  [Page 3]
> 
> Internet-Draft             DHCPv4 over DHCPv6              November 2013
>
>
>    using the same mechanism.
>
>    DHCP clients can be running on CPE devices, end hosts or any other
>    device which supports the DHCP client function.  At the time of
>    writing, DHCP clients on CPE devices are easier to modify compared to
>    those implemented on end hosts.  As a result, this document uses the
>    CPE as an example for describing the mechanism.  This does not
>    preclude any end-host, or other device requiring IPv4 configuration,
>    from implementing the mechanism in the future.
>
>    This mechanism works by carrying DHCPv4 messages encapsulated within
>    DHCPv6 messages.  Figure 1, below, illustrates one possible
>    deployment architecture.
>
>    The 4o6 DHCP client implements a new DHCPv6 message called Boot-
>    request-v6, which contains a new option called BOOTP Message option.
>    The format of this option is described in Section 6.1.
>
>    The DHCPv6 message can be transmitted either via DHCPv6 Relay Agents
>    or directly to the 4o6 DHCP Server.  The server replies with a Boot-
>    reply-v6 message, which is a new DHCPv6 message type.  This message
>    carries the DHCPv4 response encapsulated in the BOOTP Message option.
>
>                   _____________             _____________
>                  /             \           /             \
>                  |             |           |             |
>         +--------+-+  IPv6   +-+-----------+-+  IPv6   +-+--------+
>         | 4o6 DHCP | network |    DHCPv6     | network | 4o6 DHCP |
>         |  Client  +---------+  Relay Agent  +---------+  Server  |
>         | (on CPE) |         |               |         |          |
>         +--------+-+         +-+-----------+-+         +-+--------+
>                  |             |           |             |
>                  \_____________/           \_____________/
>

Could the left "IPv6 network" be renamed to "IPv6 link"?

>
>                       Figure 1: Architecture Overview
>
>    By default, the DHCPv4-over-DHCPv6 function MUST be disabled on the
>    client.  Before the client can use DHCPv4 over DHCPv6, it MUST obtain
>    the IPv6 configuration.  It requests the DHCPv4-over-DHCPv6 Enable
>    option by sending its code in Option Request Option (ORO) described
>    in [RFC3315].  The DHCPv6 server includes the DHCPv4-over-DHCPv6
>    Enable option in response to a client's request to instruct the
>    client to use DHCPv4 over DHCPv6 for IPv4 configuration.  The format
>    of the DHCPv4-over-DHCPv6 Enable option is described in Section 6.2.
>
>    Typically, a 4o6 DHCP client communicates with the 4o6 DHCP servers
>    using well-known All_DHCP_Relay_Agents_and_Servers multicast address.
>
>
>
> Sun, et al.               Expires May 26, 2014                  [Page 4]
> 
> Internet-Draft             DHCPv4 over DHCPv6              November 2013
>
>
>    Client SHOULD request the 4o6 Server Address Option from a DHCPv6
>    server and the server may be configured to respond to the client with
>    one such option that contains one or more unicast addresses of the
>    4o6 DHCP Servers.  The server includes 4o6 Server Address Option in
>    Advertise and Reply messages.  The format of the option is defined in
>    Section 6.3.
>
> 5.  New DHCPv6 Messages
>
>    There are two new DHCPv6 messages defined in this document which
>    carry DHCPv4 messages between a client and a server using DHCPv6
>    protocol: Boot-request-v6 and Boot-reply-v6.  This section describes
>    the structures of these messages.
>
> 5.1.  Message Types
>
>    BOOTREQUESTV6 (TBD):  Identifies a Boot-request-v6 message.  A 4o6
>                          DHCP client sends this message to a 4o6 DHCP
>                          server.  The BOOTP Message Option carried by
>                          this message contains a BOOTREQUEST message
>                          that the 4o6 DHCP client uses to request IPv4
>                          configuration parameters from the server.
>
>    BOOTREPLYV6 (TBD):    Identifies a Boot-reply-v6 message.  A 4o6 DHCP
>                          server sends this message to a 4o6 DHCP client.
>                          It contains a BOOTP Message Option carrying a
>                          BOOTREPLY message in response to a BOOTREQUEST
>                          received by the server in the BOOTP Message
>                          Option of the Boot-request-v6 message.
>
> 5.2.  Message Formats
>
>    Both DHCPv6 messages defined in this document share the following
>    format:
>
>      0                   1                   2                   3
>      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

Please move the previous two lines to the right by one character.

>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>      |    msg-type   |                     flags                     |
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>      |                                                               |
>      .                            options                            .
>      .                           (variable)                          .
>      |                                                               |
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>                       Figure 2: Architecture Overview
>
>
>
>
> Sun, et al.               Expires May 26, 2014                  [Page 5]
> 
> Internet-Draft             DHCPv4 over DHCPv6              November 2013
>
>
>    msg-type        Identifies message type.  It can be either
>                    BOOTREQUESTV6 (TBD) or BOOTREPLYV6 (TBD) which
>                    corresponds to the Boot-request-v6 or Boot-reply-v6,
>                    respectively.
>
>    flags           Specifies flags which provide additional information
>                    required by the server to process a DHCPv4 message
>                    encapsulated in Boot-request-v6 message, or required
>                    by the client to process DHCPv4 message encapsulated
>                    in Boot-reply-v6 message.
>
>    options         The options carried by the message.  The BOOTP
>                    Message Option described in Section 6.1 MUST be
>                    carried by the message.
>
> 5.3.  Boot-request-v6 Message Flags
>
>    The "flags" field of the Boot-request-v6 is used to carry additional
>    information which may be used by the server to process the
>    encapsulated DHCPv4 message.  Currently only one bit of this field is
>    used.  Remaining bits are reserved for the future use.  The "flags"
>    field has the following format:
>
>              0                   1                   2
>              0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4

Please move the previous two lines to the right by one character. Also 
remove the "4" at the end.

>              +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>              |U|                 Reserved                    |
>              +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>                   Figure 3: Boot-request-v6 flags format
>
>    U               Unicast Flag.  If set to 1, it indicates that the
>                    DHCPv4 message encapsulated with the Boot-request-v6
>                    message would be sent to a unicast address if it was
>                    sent using IPv4.  If this flag is set to 0, it
>                    indicates that the DHCPv4 message would be sent to

Add "the" here.

>                    broadcast address if it was sent using IPv4.
>
>    Reserved        Bits reserved for future use.  A client that doesn't
>                    implement future extensions using these bits MUST set
>                    them to 0.

Suggestion: replace the previous sentence with the idiomatic "MUST be 
set to zero when sending and MUST be ignored when receiving." Leave it 
to future RFCs to override that.

>
> 5.4.  Boot-reply-v6 Message Flags
>
>    This document introduces no flags to be carried in the "flags" field
>    of the Boot-reply-v6 message.  They are all reserved for the future
>    use.  The 4o6 Server MUST set all bits of this field to 0 and the 4o6
>    client MUST ignore the content in this field.
>
>
>
> Sun, et al.               Expires May 26, 2014                  [Page 6]
> 
> Internet-Draft             DHCPv4 over DHCPv6              November 2013
>
>
> 6.  New DHCPv6 Options
>
> 6.1.  BOOTP Message Option Format
>
>    The BOOTP Message option carries a BOOTP message that is sent by the
>    client or the server.  Such BOOTP messages exclude any IP or UDP
>    headers.
>
>    The format of the BOOTP Message Option is:
>
>      0                   1                   2                   3
>      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

Move the previous two lines one character to the right.

>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>      |        OPTION_BOOTP_MSG       |           option-len          |
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>      |                                                               |
>      .                         BOOTP-message                         .
>      .                                                               .
>      .                                                               .
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>                    Figure 4: BOOTP Message Option Format
>
>    option-code     OPTION_BOOTP_MSG (TBD).
>
>    option-len      Length of BOOTP message.
>
>    BOOTP-message   The BOOTP message sent by the client or the server.
>                    In a Boot-request-v6 message it contains a
>                    BOOTREQUEST message sent by a client.  In a Boot-
>                    reply-v6 message it contains a BOOTREPLY message sent
>                    by a server in response to a client.
>
> 6.2.  DHCPv4-over-DHCPv6 Enable Option Format
>
>    The DHCPv4-over-DHCPv6 Enable option is sent by the DHCPv6-only
>    server to signal that the client SHOULD use DHCPv4 over DHCPv6 to
>    obtain IPv4 configuration.  The server includes this option if it is
>    requested by the client.
>
>    The format of the DHCPv4-over-DHCPv6 Enable option is:
>
>      0                   1                   2                   3
>      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

Please move the previous two lines one character to the right.

>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>      |  OPTION_DHCP4_O_DHCP6_ENABLE  |           option-len          |
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>
> Sun, et al.               Expires May 26, 2014                  [Page 7]
> 
> Internet-Draft             DHCPv4 over DHCPv6              November 2013
>
>
>              Figure 5: DHCPv4-over-DHCPv6 Enable Option Format
>
>    option-code     OPTION_DHCP4_O_DHCP6_ENABLE (TBD).
>
>    option-len      0
>
> 6.3.  4o6 Server Address Option Format
>
>    The 4o6 Server Address option carries one or more unicast IPv6
>    addresses of the 4o6 DHCP Server(s).  The DHCPv6-only server includes
>    this option if it is requested by the client.
>
>    The format of the 4o6 Server Address option is:
>
>      0                   1                   2                   3
>      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

Please move the previous two lines one character to the right.

>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>      | OPTION_DHCP4_O_DHCP6_SERVER   |           option-len          |
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>      |                                                               |
>      .                        IPv6 Address(es)                       .
>      .                                                               .
>      .                                                               .
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>                 Figure 6: 4o6 Servers Address Option Format
>
>    option-code     OPTION_DHCP4_O_DHCP6_SERVER (TBD).
>
>    option-len      Length of the IPv6 address(es) carried by the option,
>                    i.e. multiple of 16 octets.
>
>    IPv6 Address    One or more IPv6 addresses of the 4o6 DHCP Server(s).
>
> 7.  Use of the Boot-request-v6 Unicast Flag
>
>    A DHCPv4 client conforming to the [RFC2131] may send its DHCPREQUEST
>    message to either broadcast or unicast address depending on its
>    state.  For example, the client in the RENEWING state uses a unicast
>    address to contact a DHCPv4 server to renew its lease.  The client in
>    the REBINDING state uses a broadcast address.  If there is a DHCPv4
>    relay agent in the middle, a client in the RENEWING state may send a
>    DHCPREQUEST message to the unicast address of the relay agent.  In
>    such case the server can't find out whether the client sent a message
>    to a unicast or broadcast address and thus it can't determine the
>    client's state.  [RFC5010] introduced the "Flags Suboption" which
>    relay agents add to relayed messages to indicate whether broadcast or
>
>
>
> Sun, et al.               Expires May 26, 2014                  [Page 8]
> 
> Internet-Draft             DHCPv4 over DHCPv6              November 2013
>
>
>    unicast was used by the client.
>
>    In DHCPv4 over DHCPv6, IPv6 is used to deliver DHCPv4 messages to the
>    4o6 DHCP Server.  There is no relation between the outer IPv6 address
>    and the inner DHCPv4 message.  So the server is not able to know
>    whether the DHCPv4 messages should have been sent using broadcast or
>    unicast in IPv4 by checking the IPv6 address.  This is similar to the
>    case addressed by the [RFC5010].
>
>    In order to allow the server to determine the client's state, the
>    "Unicast" flag is carried in the Boot-request-v6 message.  Client
>    MUST set this flag to 1 when the DHCPv4 message would have been sent
>    to the unicast address if using DHCPv4 over IPv4.  This flag MUST be
>    set to 0 if the DHCPv4 client would have sent the message to the
>    broadcast address in IPv4.  The choice whether a given message should
>    be sent to a broadcast or unicast address MUST be made based on the

The intent behind that MUST is fuzzy. Suggestion: replace with "is made 
based on..."

>    [RFC2131] and its extensions.
>
> 8.  4o6 DHCP Client Behavior
>
>    The DHCPv4-over-DHCPv6 function MUST be disabled by default.  The
>    client MUST obtain its IPv6 configuration before using DHCPv4 over
>    DHCPv6.  The client that intends to use DHCPv4 over DHCPv6 MUST
>    request the DHCPv4-over-DHCPv6 Enable Option and SHOULD request the
>    4o6 Server Address Option in the Option Request Option (ORO) in every
>    Solicit, Request, Renew and Information-request messages.  The 4o6
>    DHCP client MUST NOT request the DHCPv4-over-DHCPv6 Enable Option nor
>    the 4o6 Server Address Option in the Boot-request-v6 message.
>
>    The DHCPv6 server MAY include these options in the responses to the
>    client.  The client determines how to enable the DHCPv4-over-DHCPv6
>    function based on the presence / absence of the two options:
>
>    o  If the client doesn't receive the DHCPv4-over-DHCPv6 Enable
>       option, it MUST NOT enable the DHCPv4-over-DHCPv6 function.  In
>       the case where the DHCPv4 over DHCPv6 service is running, the
>       client MUST disable the function.

I don't understand the last sentence. What is a "DHCPv4 over DHCPv6 
service"?

>
>    o  If the client receives the DHCPv4-over-DHCPv6 Enable Option but no
>       4o6 Servers Address Option, it SHOULD enable the DHCPv4-over-

Why not MUST?

>       DHCPv6 function and use IPv6 All_DHCP_Relay_Agents_and_Servers
>       multicast address to communicate with servers and relays.
>
>    o  If the client receives both options, it SHOULD enable the DHCPv4

Why not MUST?

>       -over-DHCPv6 function and send requests to the unicast address(es)
>       in the 4o6 Server Address Option.
>
>    o  If the client only receives 4o6 Server Address Option, the client
>
>
>
> Sun, et al.               Expires May 26, 2014                  [Page 9]
> 
> Internet-Draft             DHCPv4 over DHCPv6              November 2013
>
>
>       MUST ignore the 4o6 Server Address Option and MUST NOT enable the
>       DHCPv4-over-DHCPv6 function.
>
>    The client supporting DHCPv4 over DHCPv6 SHOULD use Information
>    Refresh Time Option [RFC4242] to refresh the status of DHCPv4-over-
>    DHCPv6 service as well as other DHCPv6 configuration data.
>
>    The client signaled by the server to use DHCPv4 over DHCPv6 SHOULD

Why not MUST?

>    cease to send DHCPv4 messages using DHCP protocol described in
>    [RFC2131] and use the DHCPv4 over DHCPv6 to request IPv4
>    configuration from the 4o6 DHCP Server.

This directive needs to be rewritten so that it applies only to the 
interface in question, not to the whole client node. It should also be 
rewritten to account for the fact that the client may not have been 
doing regular DHCPv4 in the first place (you cannot cease doing 
something that you are not doing).

>    The DHCPv4 message is stored
>    verbatim in the BOOTP Message option carried by the Boot-request-v6
>    message.  The client MUST put exactly one BOOTP Message option into a
>    single Boot-request-v6 message.
>
>    Client MUST follow rules defined in Section 7 when setting Unicast
>    flag.
>
>    If the client has not received the 4o6 Server Addresses option from
>    the DHCPv6 server, it transmits the Boot-request-v6 message as
>    specified in Section 13 of [RFC3315].  If the client received this
>    option, it SHOULD send Boot-request-v6 message to all unicast
>    addresses listed in the option.
>
>    On receiving a Boot-reply-v6 message, the client MUST look for the
>    BOOTP Message option within this message.  If this option is not
>    found, the Boot-reply-v6 message is discarded.  If the BOOTP Message
>    Option presents, the client extracts the DHCPv4 message it contains
>    and processes it as described in section 4.4 of [RFC2131].
>
>    When dealing with IPv4 configuration, the 4o6 DHCP client SHOULD

Why not MUST?

>    follow the normal DHCPv4 retransmission requirements and strategy as
>    specified in section 4.1 of [RFC2131].  There are no explicit
>    transmission parameters associated with a Boot-request-v6 message.
>
>    The 4o6 DHCP client MUST implement [RFC4361] to ensure that the
>    device correctly identifies itself.
>
> 9.  Relay Agent Behavior
>
>    When a DHCPv6 relay agent receives a Boot-request-v6 message, it may
>    not recognize this message.  It can just forward this message as in
>    [I-D.ietf-dhc-dhcpv6-unknown-msg].
>
>    Additionally, the DHCPv6 relay agent MAY allow the configuration of a
>    dedicated DHCPv4 over DHCPv6 specific destination address(es),
>    differing from the address(es) of the DHCPv6-only server(s).  To
>    implement this function, the relay checks the received DHCPv6 message
>
>
>
> Sun, et al.               Expires May 26, 2014                 [Page 10]
> 
> Internet-Draft             DHCPv4 over DHCPv6              November 2013
>
>
>    type and forwards according to the following logic:
>
>    1.  If the message type is BOOTREQUESTV6, the packet is relayed to
>        the configured 4o6 DHCP Server's address(es) in the form of
>        normal DHCPv6 packet (i.e. DHCPv6/UDP/IPv6).
>
>    2.  For any other DHCPv6 message type, forward according to section
>        20 of [RFC3315].
>
>    The above logic only allows for separate relay destinations
>    configured on the relay agent closest to the client (single relay
>    hop).  Multiple relaying hops are not considered in the case of
>    separate relay destinations.
>
> 10.  4o6 DHCP Server Behavior
>
>    When the server receives a Boot-request-v6 message from a client, it
>    searches for the BOOTP Message Option.  The server discards the
>    packet without this option.  The server MAY notify an administrator
>    about the receipt of a malformed packet.  The mechanism for this
>    notification is out of scope for this document
>
>    If the server finds a valid BOOTP Message option, it extracts the
>    original DHCPv4 message and the contents of the "flags" field carried
>    in the Boot-request-v6 message and uses them to generate the
>    appropriate DHCPv4 response (server to client message).  The response
>    is generated as described in [RFC2131] with the exception that the
>    server SHOULD use the information carried in the "flags" field of the
>    Boot-request-v6 message to find out whether the client's message
>    would have been sent to the broadcast or unicast address if DHCPv4
>    protocol was used.  This is useful for the server to determine the
>    state of the client.  The use of the "flags" field is described in
>    detail in Section 7.
>
>    When appropriate DHCPv4 response is generated, the 4o6 Server places
>    it in the payload of a BOOTP Message Option, which it puts into the
>    Boot-reply-v6 message.
>
>    If the Boot-request-v6 message was received directly by the server,
>    the Boot-reply-v6 message MUST be unicast from the interface on which
>    the original message was received.
>
>    If the Boot-request-v6 message was received in a Relay-forward
>    message, the server creates a Relay-reply message with the Boot-
>    reply-v6 message in the payload of a Relay Message option, and
>    responds as described in section 20.3 of [RFC3315].
>
> 11.  Security Considerations
>
>
>
> Sun, et al.               Expires May 26, 2014                 [Page 11]
> 
> Internet-Draft             DHCPv4 over DHCPv6              November 2013
>
>
>    In this specification, DHCPv4 messages are encapsulated in the newly
>    defined option and messages.  This is similar to the handling of the
>    current relay agent messages.  In order to bypass firewalls or
>    network authentication gateways, a malicious attacker may leverage
>    this feature to convey other messages using DHCPv6, i.e. use DHCPv6
>    as a form of encapsulation.  However, the potential risk from this is
>    no more severe than that with the current DHCPv4 and DHCPv6 practice.
>
>    There are chances that a rogue DHCPv6 server may reply with a 4o6
>    Server Address Option containing duplicated unicast IPv6 addresses,
>    which can cause an amplification attack.  To avoid this, the client
>    MUST check if there are repeated IPv6 addresses in a 4o6 Server
>    Address Option when receiving one.  The client MUST ignore those
>    duplicated unicast IPv6 addresses.
>
> 12.  IANA Considerations
>
>    IANA is requested to allocate three DHCPv6 option codes for use by
>    OPTION_BOOTP_MSG, OPTION_DHCP4_O_DHCP6_ENABLE and
>    OPTION_DHCP4_O_DHCP6_SERVERS, and two DHCPv6 message type codes for
>    the BOOTREQUESTV6 and BOOTREPLYV6.
>
> 13.  Contributors List
>
>    Many thanks to Ted Lemon, Bernie Volz, Tomek Mrugalski, Yuchi Chen
>    and Cong Liu, for their great contributions to the draft.
>
> 14.  References
>
> 14.1.  Normative References
>
>    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
>               Requirement Levels", BCP 14, RFC 2119, March 1997.
>
>    [RFC2131]  Droms, R., "Dynamic Host Configuration Protocol", RFC
>               2131, March 1997.
>
>    [RFC3315]  Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C.,
>               and M. Carney, "Dynamic Host Configuration Protocol for
>               IPv6 (DHCPv6)", RFC 3315, July 2003.
>
>    [RFC4242]  Venaas, S., Chown, T., and B. Volz, "Information Refresh
>               Time Option for Dynamic Host Configuration Protocol for
>               IPv6 (DHCPv6)", RFC 4242, November 2005.
>
>    [RFC4361]  Lemon, T. and B. Sommerfeld, "Node-specific Client
>               Identifiers for Dynamic Host Configuration Protocol
>               Version Four (DHCPv4)", RFC 4361, February 2006.
>
>
>
> Sun, et al.               Expires May 26, 2014                 [Page 12]
> 
> Internet-Draft             DHCPv4 over DHCPv6              November 2013
>
>
> 14.2.  Informative References
>
>    [I-D.ietf-dhc-dhcpv6-unknown-msg]
>               Cui, Y., Sun, Q., and T. Lemon, "Handling Unknown DHCPv6
>               Messages", draft-ietf-dhc-dhcpv6-unknown-msg-03 (work in
>               progress), November 2013.
>
>    [RFC5010]  Kinnear, K., Normoyle, M., and M. Stapp, "The Dynamic Host
>               Configuration Protocol Version 4 (DHCPv4) Relay Agent
>               Flags Suboption", RFC 5010, September 2007.
>
> Authors' Addresses
>
>    Qi Sun
>    Tsinghua University
>    Beijing  100084
>    P.R.China
>
>    Phone: +86-10-6278-5822
>    Email: sunqi@csnet1.cs.tsinghua.edu.cn
>
>
>    Yong Cui
>    Tsinghua University
>    Beijing  100084
>    P.R.China
>
>    Phone: +86-10-6260-3059
>    Email: yong@csnet1.cs.tsinghua.edu.cn
>
>
>    Marcin Siodelski
>    950 Charter Street
>    Redwood City, CA  94063
>    USA
>
>    Phone: +1 650 423 1431
>    Email: msiodelski@gmail.com
>
>
>    Suresh Krishnan
>    Ericsson
>
>    Email: suresh.krishnan@ericsson.com
>
>
>
>
>
>
>
> Sun, et al.               Expires May 26, 2014                 [Page 13]
> 
> Internet-Draft             DHCPv4 over DHCPv6              November 2013
>
>
>    Ian Farrer
>    Deutsche Telekom AG
>    GTN-FM4,Landgrabenweg 151
>    Bonn, NRW  53227
>    Germany
>
>    Email: ian.farrer@telekom.de
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Sun, et al.               Expires May 26, 2014                 [Page 14]


-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From alexandru.petrescu@gmail.com  Fri Dec  6 08:20:16 2013
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B4841AE3A8 for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 08:20:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0dwM-olzLE5o for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 08:20:14 -0800 (PST)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id 16CBE1AE07B for <dhcwg@ietf.org>; Fri,  6 Dec 2013 08:20:13 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id rB6GK9pv015363; Fri, 6 Dec 2013 17:20:09 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 01ABE200D13; Fri,  6 Dec 2013 17:20:20 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id E90FA200CE8; Fri,  6 Dec 2013 17:20:19 +0100 (CET)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id rB6GK5H5005907; Fri, 6 Dec 2013 17:20:09 +0100
Message-ID: <52A1F936.3040902@gmail.com>
Date: Fri, 06 Dec 2013 17:20:06 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Matthew Dempsky <matthew@dempsky.org>, dhcwg@ietf.org
References: <CANKkrzEew4WtYpa33GL3QB-8Wd8jGZTEv5djkOr9LbOMa7+icw@mail.gmail.com>
In-Reply-To: <CANKkrzEew4WtYpa33GL3QB-8Wd8jGZTEv5djkOr9LbOMa7+icw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [dhcwg] Any documentation for handling /32 IPv4 assignments from DHCP?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 06 Dec 2013 16:20:16 -0000

Hello Matthew,

I see no other answer, but I have some thoughts.

First, I am not sure why this script is written that way.  When a router 
address is allocated by DHCP ('option routers') it is typically a 
default router, and hence it must have that 'default' qualifier in the 
subsequent route add command.  The first lines of the script would be 
nonsense.

On another hand, one may allocate a prefix (instead of an address), and 
hence it would need that prefix to be reachable through that router.

Le 05/12/2013 19:18, Matthew Dempsky a écrit :
> In dhcp-4.2.5-P1/client/scripts/linux, there's this code for adding
> routes based on the Router (3) and Subnet Mask (1) options:
>
>      for router in $new_routers; do
>        if [ "x$new_subnet_mask" = "x255.255.255.255" ] ; then
>          route add -host $router dev $interface

I wonder whether those two lines above have anything to do with IPv4 
Subnet Allocation RFC6656 "Description of Cisco Systems' Subnet 
Allocation Option for DHCPv4" INFORMATIONAL.

>        fi
>        route add default gw $router $metric_arg dev $interface
>      done
>
> Is this special case logic for subnet_mask==255.255.255.255 codified
> anywhere?

I dont know.

>  I'm working on adding similar logic to OpenBSD's DHCP
> client (so OpenBSD can connect to a network currently supported by ISC
> DHCP on Linux),

That is a very good goal.

> but I'm having trouble finding any authoritative
> documentation explaining the correct behavior here.

Maybe one would ask the author of that script why did s/he write it that 
way?  Does the script have a author name in the head.

> In particular, ISC DHCP 4.2.5-P1 only adds the "dev" route for Router
> (3), but I'm wondering if they should be added for Static Route (33)
> and/or Classless Static Route Option (121) too?

I dont know.

Alex

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



From matthew@dempsky.org  Fri Dec  6 11:59:25 2013
Return-Path: <matthew@dempsky.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1A681AE0A0 for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 11:59:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8EahA6ujiA0W for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 11:59:24 -0800 (PST)
Received: from mail-lb0-f180.google.com (mail-lb0-f180.google.com [209.85.217.180]) by ietfa.amsl.com (Postfix) with ESMTP id 145181AE06F for <dhcwg@ietf.org>; Fri,  6 Dec 2013 11:59:23 -0800 (PST)
Received: by mail-lb0-f180.google.com with SMTP id w6so472558lbh.11 for <dhcwg@ietf.org>; Fri, 06 Dec 2013 11:59:19 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=4iXarbHUoB5pZQMEpT+aGyOLh9c+1WOlhuxHrTgxgv8=; b=cjdf8l6Q6gKOOhIXZAeGzaJEyiPaYYBq82K3yvDsQ/qqFumVVejtkIOXn/0ihEjgU1 cMjGvkevpwVe0K90cezaP115RioNNykWUwShVSZxk5bMCcO90ANxBDyxw3yuduWlVT2A WSjnhEr+rNSlvt2nBrSu6ga9rlsLEnONP91tCxgEfxBARsS43JSTyBVBp4sm5qKMVnD9 jETQXXzrGKFxZRBKb25HH/6dZ49T5c9G08Drvz3fYnC5DeRUAVo2xecqfIcT4ACP4SQz 6ds5LhdPXRkvaVLL5O4d/KM8nnw9yavXG3xjMBG7RSHGoMjo+sdNGJVZNmisecmwvlGp NJsA==
X-Gm-Message-State: ALoCoQk4FdKiZKQcRzvnpwAVQQ9lk7KDTrIvN+gd7BZmQnBSQJX/svN8OTL3zUTqERASNAZjI8IU
MIME-Version: 1.0
X-Received: by 10.112.92.112 with SMTP id cl16mr1322248lbb.15.1386359959390; Fri, 06 Dec 2013 11:59:19 -0800 (PST)
Received: by 10.152.22.132 with HTTP; Fri, 6 Dec 2013 11:59:19 -0800 (PST)
In-Reply-To: <52A1F936.3040902@gmail.com>
References: <CANKkrzEew4WtYpa33GL3QB-8Wd8jGZTEv5djkOr9LbOMa7+icw@mail.gmail.com> <52A1F936.3040902@gmail.com>
Date: Fri, 6 Dec 2013 11:59:19 -0800
Message-ID: <CANKkrzFTaD8=bMb0EX7k48tmuj1VSZfbwr+5GO0H_0k-_6VJ-Q@mail.gmail.com>
From: Matthew Dempsky <matthew@dempsky.org>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Any documentation for handling /32 IPv4 assignments from DHCP?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 06 Dec 2013 19:59:25 -0000

On Fri, Dec 6, 2013 at 8:20 AM, Alexandru Petrescu
<alexandru.petrescu@gmail.com> wrote:
> First, I am not sure why this script is written that way.  When a router
> address is allocated by DHCP ('option routers') it is typically a default
> router, and hence it must have that 'default' qualifier in the subsequent
> route add command.  The first lines of the script would be nonsense.

Oh, sorry, I should have provided some more background information.

On Linux, a command like "route add -host 5.6.7.8 dev eth0" tells the
Linux kernel that IP address 5.6.7.8 is directly addressable via eth0,
even if there's no otherwise appropriate IP/netmask assignment on eth0
that includes 5.6.7.8.

E.g., the network I'm trying to connect to is giving a DHCP lease like
"IP: 1.2.3.4, Subnet Mask: 255.255.255.255, Router: 5.6.7.8".  The
issue is if you simply configure the interface like

    ifconfig eth0 inet 1.2.3.4 netmask 255.255.255.255
    route add default 5.6.7.8

then there's no existing route for 5.6.7.8, so the default route is
rejected as invalid.

ISC DHCP has that extra netmask==255.255.255.255 check so that it
instead executes

    ifconfig eth0 inet 1.2.3.4 netmask 255.255.255.255
    route add -host 5.6.7.8 dev eth0
    route add default 5.6.7.8

which allows the default route to then be added successfully, because
5.6.7.8 is now reachable via eth0 (using srcip 1.2.3.4).  Effectively,
eth0 is now treated as a point-to-point network consisting of only
1.2.3.4 and 5.6.7.8.

> I wonder whether those two lines above have anything to do with IPv4 Subnet
> Allocation RFC6656 "Description of Cisco Systems' Subnet Allocation Option
> for DHCPv4" INFORMATIONAL.

I don't think so.  The network I'm using doesn't send a DHCP response
with option 220, and ISC DHCP doesn't appear to support it either.

> Maybe one would ask the author of that script why did s/he write it that
> way?  Does the script have a author name in the head.

I'll try tracking down an ISC DHCP author.  (I was kinda hoping maybe
one would be on dhcwg.)

Thanks

From tom.taylor.stds@gmail.com  Fri Dec  6 12:02:02 2013
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC3151AE0A0 for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 12:02:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cxsZNVjKYoLf for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 12:02:00 -0800 (PST)
Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com [IPv6:2607:f8b0:4001:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 1B2471AE074 for <dhcwg@ietf.org>; Fri,  6 Dec 2013 12:01:59 -0800 (PST)
Received: by mail-ie0-f180.google.com with SMTP id tp5so2055354ieb.25 for <dhcwg@ietf.org>; Fri, 06 Dec 2013 12:01:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Q4d6vxTpoQOle82EUEz7RfwiiiUj7Slb4QCUcDDs8fw=; b=df3u3fpX5XAJj0NE3kaG90TzvkywxIGtGlo1OpYGYiOF0Q52yVFtOhD3suOE/i9Zx7 JhkoA1DMn0XTMW0YCpAtroojIrtRjhbaF5+yTzf7EOtoT3L3PZQ40c9zIRYnhDGGemZu rL0efINhv03+L68SX5Hmjrl9feoza6AHbX1kRodCxb9HWJ/lZuYML0c6zjTNLSkpX69i 7TCR3X+JEKVRZm6jH4PEwiohzmjgoZzgAz9EQRbwrCv+4tbU6Rp6YjHw2OSbjbfiG9D0 bbRabvtejqMp4NC3yNVqBvIvlghG6Vmn1Qi4zxWdFRU35nOuwSOY1xEneP9fEKCby3sn /Nhg==
X-Received: by 10.50.61.205 with SMTP id s13mr4374095igr.29.1386360115257; Fri, 06 Dec 2013 12:01:55 -0800 (PST)
Received: from [192.168.1.65] ([64.56.250.4]) by mx.google.com with ESMTPSA id x6sm5331771igb.3.2013.12.06.12.01.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 06 Dec 2013 12:01:54 -0800 (PST)
Message-ID: <52A22D2F.9020003@gmail.com>
Date: Fri, 06 Dec 2013 15:01:51 -0500
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
References: <489D13FBFA9B3E41812EA89F188F018E185CDA1C@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E185CDA1C@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] WGLC - draft-ietf-dhc-option-guidelines-12 - Respond by July 15
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 06 Dec 2013 20:02:02 -0000

I've just reviewed all the discussion of Server address and I think what 
I'm about to say is still relevant. This is just a trivial wording remark.

The last paragraph of Section 4 says:

    Typically, a 4o6 DHCP client communicates with the 4o6 DHCP servers
    using well-known All_DHCP_Relay_Agents_and_Servers multicast address.
    Client SHOULD request the 4o6 Server Address Option from a DHCPv6
    server and the server may be configured to respond to the client with
    one such option that contains one or more unicast addresses of the
    4o6 DHCP Servers.  The server includes 4o6 Server Address Option in
    Advertise and Reply messages.  The format of the option is defined in
    Section 6.3.

The word "typically" in the first sentence seems to clash with "[The] 
client SHOULD request ..." in the next sentence. Do you mean to say 
"initially" rather than "typically"?

Tom Taylor

On 01/07/2013 5:44 PM, Bernie Volz (volz) wrote:
> The draft-ietf-dhc-option-guidelines-12,
> http://tools.ietf.org/html/draft-ietf-dhc-option-guidelines-12,
> addresses the comments from the previous (-11) last call. While
> originally I expected to have a short (1 week) last call for the
> updated document, I think it best to have the standard 2 weeks given
> the time of year (and the Independence Day holiday in the US).
>
>
>
> Please review the draft and indicate whether or not you feel this
> version is ready to be published. Your response matters to the
> process, so please do respond.
>
>
>
> Do note: While I encourage full reviews, the main focus is to assure
> we have consensus on the recent changes from the -11. The -11 WGLC
> support will be taken into consideration.
>
>
>
> As Tomek is an author, I will evaluate consensus after July 15,
> 2013.
>
>
>
> -          Bernie
>
>
>
>
>
> _______________________________________________ dhcwg mailing list
> dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>

From Ted.Lemon@nominum.com  Fri Dec  6 12:15:50 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 084901AE3B9 for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 12:15:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g6Ng-zfnPz8z for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 12:15:48 -0800 (PST)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id 8E0631AE3A2 for <dhcwg@ietf.org>; Fri,  6 Dec 2013 12:15:48 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKUqIwcN42e3fXgbm22xDghWEbQSUZMzWq@postini.com; Fri, 06 Dec 2013 12:15: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 C882A1B82E3 for <dhcwg@ietf.org>; Fri,  6 Dec 2013 12:15:44 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id B7582190043; Fri,  6 Dec 2013 12:15:44 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 6 Dec 2013 12:15:38 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <52A22D2F.9020003@gmail.com>
Date: Fri, 6 Dec 2013 15:15:36 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <3147A6AE-0705-4A1B-8206-BEEB1FC4045C@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E185CDA1C@xmb-rcd-x04.cisco.com> <52A22D2F.9020003@gmail.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] WGLC - draft-ietf-dhc-option-guidelines-12 - Respond by July 15
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 06 Dec 2013 20:15:50 -0000

On Dec 6, 2013, at 3:01 PM, Tom Taylor <tom.taylor.stds@gmail.com> =
wrote:
>   Typically, a 4o6 DHCP client communicates with the 4o6 DHCP servers

I'm confused.   Is there now text in the option guidelines draft about =
DHCPv4-over-DHCPv6?


From tomasz.mrugalski@gmail.com  Fri Dec  6 12:17:09 2013
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B6D51AE3C0 for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 12:17:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CoVYd-bfWHWB for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 12:17:07 -0800 (PST)
Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 7E05F1AE107 for <dhcwg@ietf.org>; Fri,  6 Dec 2013 12:17:07 -0800 (PST)
Received: by mail-we0-f171.google.com with SMTP id q58so1170639wes.30 for <dhcwg@ietf.org>; Fri, 06 Dec 2013 12:17:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=FfbzxghqcnLU/IBwbVPx5p7FIxdSj6Z4i1pVwbK2OUE=; b=fZGMUABmMtsTPOhXligKU34CYC+nyNbfmtYwLPXHcpc3QA4ygcDQJntPcrK5Bc1BYQ F6DbMCmwVwKOd5/E4hUmi1FDgJqiocmwjbECrWOZShDnUDqN/rWMw2idsabjpqVLz+3i eej9OUgNg20FVHo4B2BPyN0yTnvGq0mRZQPY58OJz6mXItbM9VKyhpXE9gpX2Kra4sOi UiGt7AJ4UcTzpsOr1gFgkuJr3BYULtyLXuZ9B++M/DP4NldJvezc/nX2P1jlV8apa3hN y9MWXbWFx8NxqYUyDnBFyFB6xET9/yjq+FnP/33RILGl6dRDtPy1zyOjcc+/4KhUUK9q KZTA==
X-Received: by 10.194.171.34 with SMTP id ar2mr5831553wjc.81.1386361023307; Fri, 06 Dec 2013 12:17:03 -0800 (PST)
Received: from ?IPv6:2001:470:6061:0:f66d:4ff:fe96:58f2? ([2001:470:6061:0:f66d:4ff:fe96:58f2]) by mx.google.com with ESMTPSA id qc10sm9301112wic.9.2013.12.06.12.17.01 for <dhcwg@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 06 Dec 2013 12:17:02 -0800 (PST)
Message-ID: <52A230B7.9040909@gmail.com>
Date: Fri, 06 Dec 2013 21:16:55 +0100
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <489D13FBFA9B3E41812EA89F188F018E185CDA1C@xmb-rcd-x04.cisco.com> <52A22D2F.9020003@gmail.com>
In-Reply-To: <52A22D2F.9020003@gmail.com>
X-Enigmail-Version: 1.5.2
X-TagToolbar-Keys: D20131206211655738
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] WGLC - draft-ietf-dhc-option-guidelines-12 - Respond by July 15
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 06 Dec 2013 20:17:09 -0000

On 06.12.2013 21:01, Tom Taylor wrote:
> I've just reviewed all the discussion of Server address and I think what
> I'm about to say is still relevant. This is just a trivial wording remark.
> 
> The last paragraph of Section 4 says:
> 
>    Typically, a 4o6 DHCP client communicates with the 4o6 DHCP servers
Eh, what?

You are responding to a last call that ended by July 15. It was about
option-guidelines-12. The latest version is now -14 and it just came
back from IESG.

Furthermore, what you are commenting on is from
draft-ietf-dhc-dhcpv4-over-dhcpv6 draft. That's a very different draft.
However, your comment is very timely sent as dhcpv4-over-dhcpv6 is going
through WGLC right now.

I will let the dhcp4-over-dhcpv6 authors respond, but (with my chair hat
off), I think "typically" is better. The 4o6 client communicates with
the server over All_DHCP_Relay_Agents_and_Server all the time, unless
server sends server address option. In principle it is very similar to
server unicast in plain DHCPv6. That option is somewhat infrequently
used. I expect the same to be true in dhcpv4-over-dhcpv6, so I think
"typically" is the right word here.

If you understood the text differently, perhaps the draft needs a bit of
clarification to explain that usage of 4o6 Server Address Option is
optional and you can have perfectly working 4o6 solution without it.

Tomek


From volz@cisco.com  Fri Dec  6 12:20:24 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 091EA1AE167 for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 12:20:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kQoHiky5habf for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 12:20:20 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 7A2041AE107 for <dhcwg@ietf.org>; Fri,  6 Dec 2013 12:20:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2709; q=dns/txt; s=iport; t=1386361217; x=1387570817; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=+q0y4UGONknRoX1ieXeQhgfgX+0BA68rpM6y1zTB/Ug=; b=BNMlz0roBsMf14xZwNqyaIc3wCXYOu0nE0qCmEf347LaFT7XYNBDwUxQ kEGMY+N0q8hRzts681yaAp5yKd8etaHD5omprrEKZZ3GHq3niz9k0gqLv pwLujAxfeVCKkFyGlvXEjL/37qhkMQZkVjrfZJw9IFN14TlVaKv5EORWt s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAHYwolKtJV2Y/2dsb2JhbABZgwc4U7kEgSMWdIIlAQEBBAEBARodNBcGAQgRBAEBAQoUCS4LFAkJAQQBEgiHeg3AcReOXQI+gxqBEwOZRJBjgWuBPoIq
X-IronPort-AV: E=Sophos;i="4.93,842,1378857600"; d="scan'208";a="289873665"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-2.cisco.com with ESMTP; 06 Dec 2013 20:20:08 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id rB6KK1Hl029420 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 6 Dec 2013 20:20:03 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0123.003; Fri, 6 Dec 2013 14:20:01 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
Thread-Index: Ac7ywFiOXFinITfhQ4SAN2eVQP2gUw==
Date: Fri, 6 Dec 2013 20:20:00 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1ADD660D@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.244.216]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 06 Dec 2013 20:20:24 -0000

Fixed the subject ...

Yes, this is a good point. I am not sure initially is any better.

Perhaps this should just be reworded to say that the client uses one of the=
 two methods (multicast to All_DHCP_Relay_Agents_and_Servers) or to the lis=
t indicated in the option.

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Tom Taylor
Sent: Friday, December 06, 2013 3:02 PM
To: Bernie Volz (volz); dhcwg@ietf.org
Subject: Re: [dhcwg] WGLC - draft-ietf-dhc-option-guidelines-12 - Respond b=
y July 15

I've just reviewed all the discussion of Server address and I think what I'=
m about to say is still relevant. This is just a trivial wording remark.

The last paragraph of Section 4 says:

    Typically, a 4o6 DHCP client communicates with the 4o6 DHCP servers
    using well-known All_DHCP_Relay_Agents_and_Servers multicast address.
    Client SHOULD request the 4o6 Server Address Option from a DHCPv6
    server and the server may be configured to respond to the client with
    one such option that contains one or more unicast addresses of the
    4o6 DHCP Servers.  The server includes 4o6 Server Address Option in
    Advertise and Reply messages.  The format of the option is defined in
    Section 6.3.

The word "typically" in the first sentence seems to clash with "[The] clien=
t SHOULD request ..." in the next sentence. Do you mean to say "initially" =
rather than "typically"?

Tom Taylor

On 01/07/2013 5:44 PM, Bernie Volz (volz) wrote:
> The draft-ietf-dhc-option-guidelines-12,
> http://tools.ietf.org/html/draft-ietf-dhc-option-guidelines-12,
> addresses the comments from the previous (-11) last call. While=20
> originally I expected to have a short (1 week) last call for the=20
> updated document, I think it best to have the standard 2 weeks given=20
> the time of year (and the Independence Day holiday in the US).
>
>
>
> Please review the draft and indicate whether or not you feel this=20
> version is ready to be published. Your response matters to the=20
> process, so please do respond.
>
>
>
> Do note: While I encourage full reviews, the main focus is to assure=20
> we have consensus on the recent changes from the -11. The -11 WGLC=20
> support will be taken into consideration.
>
>
>
> As Tomek is an author, I will evaluate consensus after July 15, 2013.
>
>
>
> -          Bernie
>
>
>
>
>
> _______________________________________________ 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 tom.taylor.stds@gmail.com  Fri Dec  6 12:49:41 2013
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46F411AE3E2 for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 12:49:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cva-06zb0pBM for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 12:49:39 -0800 (PST)
Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 81BC21AE3D4 for <dhcwg@ietf.org>; Fri,  6 Dec 2013 12:49:39 -0800 (PST)
Received: by mail-ie0-f175.google.com with SMTP id x13so2166851ief.6 for <dhcwg@ietf.org>; Fri, 06 Dec 2013 12:49:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=z48UUvJqNPVug0qBGUno2aqwNQ/gHasJLZDNDO5misA=; b=LWvt8aVOQuzzw5Enef2MKKpNjsYiEvYusNebd7l7FSR2x82HIYxHZmApeuszE+1EJT Vnoh4KPij9HQUhULF1N9GNa6sYmsf7qTwAhGIOenGbgxlnIcMZKuaJ6iFxYmkRDKU/kB 7wjCFQE1jvFSHmSswss/kS3TlCKzN7R5YnxKbgNMJ4OmaKk5W6r2cPZqu2iIQ0Bb42JQ Sufzi3x96NHB6VCQxaYPYzQ72BxvOjOVVBkImptRul9uNUOx3lSLymikutGoUCDO4x2h 5GQbHCGI8z1RxeToRI0h1UnzbOMs1x36fRLW/Sd4j6O7HJXtn+l2aQtZeGD/LeBObUqO +b/w==
X-Received: by 10.50.79.138 with SMTP id j10mr4729137igx.2.1386362975684; Fri, 06 Dec 2013 12:49:35 -0800 (PST)
Received: from [192.168.1.65] ([64.56.250.4]) by mx.google.com with ESMTPSA id k6sm5534596igx.8.2013.12.06.12.49.34 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 06 Dec 2013 12:49:35 -0800 (PST)
Message-ID: <52A2385C.7020706@gmail.com>
Date: Fri, 06 Dec 2013 15:49:32 -0500
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
References: <489D13FBFA9B3E41812EA89F188F018E1ADD660D@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADD660D@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 06 Dec 2013 20:49:41 -0000

I think "initially" is correct. When the client first comes up, it does 
not normally have a server unicast address. Even though the client and 
server have not yet agreed on 4o6 provisioning at that point, the client 
has reached the 4o6 server using multicast.

Tom

On 06/12/2013 3:20 PM, Bernie Volz (volz) wrote:
> Fixed the subject ...
>
> Yes, this is a good point. I am not sure initially is any better.
>
> Perhaps this should just be reworded to say that the client uses one
> of the two methods (multicast to All_DHCP_Relay_Agents_and_Servers)
> or to the list indicated in the option.
>
> - Bernie
>
> -----Original Message----- From: dhcwg
> [mailto:dhcwg-bounces@ietf.org] On Behalf Of Tom Taylor Sent: Friday,
> December 06, 2013 3:02 PM To: Bernie Volz (volz); dhcwg@ietf.org
> Subject: Re: [dhcwg] WGLC - draft-ietf-dhc-option-guidelines-12 -
> Respond by July 15
>
> I've just reviewed all the discussion of Server address and I think
> what I'm about to say is still relevant. This is just a trivial
> wording remark.
>
> The last paragraph of Section 4 says:
>
> Typically, a 4o6 DHCP client communicates with the 4o6 DHCP servers
> using well-known All_DHCP_Relay_Agents_and_Servers multicast
> address. Client SHOULD request the 4o6 Server Address Option from a
> DHCPv6 server and the server may be configured to respond to the
> client with one such option that contains one or more unicast
> addresses of the 4o6 DHCP Servers.  The server includes 4o6 Server
> Address Option in Advertise and Reply messages.  The format of the
> option is defined in Section 6.3.
>
> The word "typically" in the first sentence seems to clash with "[The]
> client SHOULD request ..." in the next sentence. Do you mean to say
> "initially" rather than "typically"?
>
> Tom Taylor
>
...

From volz@cisco.com  Fri Dec  6 13:00:13 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6085B1AE0D8 for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 13:00:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.502
X-Spam-Level: 
X-Spam-Status: No, score=-9.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZYPYcJJlkSBl for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 13:00:09 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) by ietfa.amsl.com (Postfix) with ESMTP id 953461AE08E for <dhcwg@ietf.org>; Fri,  6 Dec 2013 13:00:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2620; q=dns/txt; s=iport; t=1386363606; x=1387573206; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=xg1SERrOV/bmG87aYib5Hm1rpTV9ExdGapx2UvjkrKM=; b=a0MDBA79+BDAwYYdHoLLEKF02e7fYcQfmbFN7zfKaQll7OoWNncRUXbH 28NoUXA1MLwneRtjmggdX5ek9vaA+0xpeU+6xCy+uyy1ujqkHcKsH6rVe 1/TfkwxA8hVhPvvGSnHhnv1of4UTfwwD+wWdpAm2qUjNNPOtMLPIrTWgm 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAKc5olKtJV2d/2dsb2JhbABZgwc4U7kIgSMWdIIlAQEBBAEBATc0FwQCAQgRBAEBAQoUCQcnCxQJCAEBBAESCId6DcBwEwSOXzgGgxqBEwOqJ4FrgT6CKg
X-IronPort-AV: E=Sophos;i="4.93,842,1378857600";  d="scan'208";a="4935835"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-1.cisco.com with ESMTP; 06 Dec 2013 21:00:05 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id rB6L05w4009904 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 6 Dec 2013 21:00:05 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0123.003; Fri, 6 Dec 2013 15:00:04 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
Thread-Index: Ac7ywFiOXFinITfhQ4SAN2eVQP2gUwANpwMAAAxFV6A=
Date: Fri, 6 Dec 2013 21:00:04 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1ADD6721@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADD660D@xmb-rcd-x04.cisco.com> <52A2385C.7020706@gmail.com>
In-Reply-To: <52A2385C.7020706@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.244.216]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 06 Dec 2013 21:00:13 -0000

No. That is not the case. The 4o6 DHCP client doesn't start communicating u=
ntil it has received the option(s) from the DHCPv6 server and then it knows=
 whether it got a list of servers to send to or whether it should use the d=
efault multicast address. Read the paragraph previous to the one in questio=
n.

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Tom Taylor
Sent: Friday, December 06, 2013 3:50 PM
To: Bernie Volz (volz); dhcwg@ietf.org
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respon=
d by Dec 9, 2013

I think "initially" is correct. When the client first comes up, it does not=
 normally have a server unicast address. Even though the client and server =
have not yet agreed on 4o6 provisioning at that point, the client has reach=
ed the 4o6 server using multicast.

Tom

On 06/12/2013 3:20 PM, Bernie Volz (volz) wrote:
> Fixed the subject ...
>
> Yes, this is a good point. I am not sure initially is any better.
>
> Perhaps this should just be reworded to say that the client uses one=20
> of the two methods (multicast to All_DHCP_Relay_Agents_and_Servers)
> or to the list indicated in the option.
>
> - Bernie
>
> -----Original Message----- From: dhcwg [mailto:dhcwg-bounces@ietf.org]=20
> On Behalf Of Tom Taylor Sent: Friday, December 06, 2013 3:02 PM To:=20
> Bernie Volz (volz); dhcwg@ietf.org
> Subject: Re: [dhcwg] WGLC - draft-ietf-dhc-option-guidelines-12 -=20
> Respond by July 15
>
> I've just reviewed all the discussion of Server address and I think=20
> what I'm about to say is still relevant. This is just a trivial=20
> wording remark.
>
> The last paragraph of Section 4 says:
>
> Typically, a 4o6 DHCP client communicates with the 4o6 DHCP servers=20
> using well-known All_DHCP_Relay_Agents_and_Servers multicast address.=20
> Client SHOULD request the 4o6 Server Address Option from a
> DHCPv6 server and the server may be configured to respond to the=20
> client with one such option that contains one or more unicast=20
> addresses of the 4o6 DHCP Servers.  The server includes 4o6 Server=20
> Address Option in Advertise and Reply messages.  The format of the=20
> option is defined in Section 6.3.
>
> The word "typically" in the first sentence seems to clash with "[The]=20
> client SHOULD request ..." in the next sentence. Do you mean to say=20
> "initially" rather than "typically"?
>
> Tom Taylor
>
...
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg

From tom.taylor.stds@gmail.com  Fri Dec  6 18:38:23 2013
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F26F31AE0F6 for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 18:38:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c08bEBkoDkZq for <dhcwg@ietfa.amsl.com>; Fri,  6 Dec 2013 18:38:20 -0800 (PST)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id CA4E21AE110 for <dhcwg@ietf.org>; Fri,  6 Dec 2013 18:38:20 -0800 (PST)
Received: by mail-ie0-f177.google.com with SMTP id tp5so2726175ieb.22 for <dhcwg@ietf.org>; Fri, 06 Dec 2013 18:38:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=8oVUbaJrLsdYhl9UiOp473nVqub5dQkPkShTS7Hy7mc=; b=dhyDkJCA/FO2dl7cdY6Y5h+xBIo+maVX64LDBF4ha3/z115U2Ns1zrrshalCM2Y3F1 WYrEm70IpTaGpI9j76WOI7nXh03OOsNebx7joKEoEHSY50bqPxfo6r25BwFpXyifYOAS flsyjwbk5uGxIK7rJeW+el8QAMindO3FBKblvPnbTspvYrb0a2d9YPAxRK/ZJ+GTnUIG QCL1aQ3tb9Pucr+fskvrtj+66WovWho26ocpWGhPyGynpLE4sb32bBVpLaFgGLzQxFSN 3IBSCi91SRGNHu071MuBFYSjguTYHPP2itPmidHFYnhwSNVva/cv9MZjxpagDOZeXv9u 1cpg==
X-Received: by 10.50.82.41 with SMTP id f9mr5658868igy.26.1386383896879; Fri, 06 Dec 2013 18:38:16 -0800 (PST)
Received: from [192.168.1.65] ([64.56.250.4]) by mx.google.com with ESMTPSA id v9sm1058096igh.7.2013.12.06.18.38.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 06 Dec 2013 18:38:16 -0800 (PST)
Message-ID: <52A28A14.3060906@gmail.com>
Date: Fri, 06 Dec 2013 21:38:12 -0500
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
References: <489D13FBFA9B3E41812EA89F188F018E1ADD660D@xmb-rcd-x04.cisco.com> <52A2385C.7020706@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1ADD6721@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADD6721@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Dec 2013 02:38:23 -0000

I think this hinges on when the client starts acting as a 4o6 client, 
which is not clear but really doesn't matter. May I suggest the 
following phrasing:

"Again by default, a 4o6 client communicates with the 4o6 DHCP servers
  using the well-known All_DHCP_Relay_Agents_and_Servers multicast
  address.  However, the client SHOULD ...".

Tom Taylor


On 06/12/2013 4:00 PM, Bernie Volz (volz) wrote:
> No. That is not the case. The 4o6 DHCP client doesn't start
> communicating until it has received the option(s) from the DHCPv6
> server and then it knows whether it got a list of servers to send to
> or whether it should use the default multicast address. Read the
> paragraph previous to the one in question.
>
> - Bernie
>
> -----Original Message----- From: dhcwg
> [mailto:dhcwg-bounces@ietf.org] On Behalf Of Tom Taylor Sent: Friday,
> December 06, 2013 3:50 PM To: Bernie Volz (volz); dhcwg@ietf.org
> Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 -
> Respond by Dec 9, 2013
>
> I think "initially" is correct. When the client first comes up, it
> does not normally have a server unicast address. Even though the
> client and server have not yet agreed on 4o6 provisioning at that
> point, the client has reached the 4o6 server using multicast.
>
> Tom
>
> On 06/12/2013 3:20 PM, Bernie Volz (volz) wrote:
>> Fixed the subject ...
>>
>> Yes, this is a good point. I am not sure initially is any better.
>>
>> Perhaps this should just be reworded to say that the client uses
>> one of the two methods (multicast to
>> All_DHCP_Relay_Agents_and_Servers) or to the list indicated in the
>> option.
>>
>> - Bernie
>>
>> -----Original Message----- From: dhcwg
>> [mailto:dhcwg-bounces@ietf.org] On Behalf Of Tom Taylor Sent:
>> Friday, December 06, 2013 3:02 PM To: Bernie Volz (volz);
>> dhcwg@ietf.org Subject: Re: [dhcwg] WGLC -
>> draft-ietf-dhc-option-guidelines-12 - Respond by July 15
>>
>> I've just reviewed all the discussion of Server address and I
>> think what I'm about to say is still relevant. This is just a
>> trivial wording remark.
>>
>> The last paragraph of Section 4 says:
>>
>> Typically, a 4o6 DHCP client communicates with the 4o6 DHCP
>> servers using well-known All_DHCP_Relay_Agents_and_Servers
>> multicast address. Client SHOULD request the 4o6 Server Address
>> Option from a DHCPv6 server and the server may be configured to
>> respond to the client with one such option that contains one or
>> more unicast addresses of the 4o6 DHCP Servers.  The server
>> includes 4o6 Server Address Option in Advertise and Reply messages.
>> The format of the option is defined in Section 6.3.
>>
>> The word "typically" in the first sentence seems to clash with
>> "[The] client SHOULD request ..." in the next sentence. Do you mean
>> to say "initially" rather than "typically"?
>>
>> Tom Taylor
>>
> ... _______________________________________________ dhcwg mailing
> list dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
>

From internet-drafts@ietf.org  Mon Dec  9 10:26:32 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFC8A1AE433; Mon,  9 Dec 2013 10:26:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xtVtxBgVJCtI; Mon,  9 Dec 2013 10:26:30 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E65EC1AE329; Mon,  9 Dec 2013 10:26:29 -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: 4.83.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131209182629.3798.19997.idtracker@ietfa.amsl.com>
Date: Mon, 09 Dec 2013 10:26:29 -0800
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-option-guidelines-15.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Dec 2013 18:26:33 -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 Group =
of the IETF.

	Title           : Guidelines for Creating New DHCPv6 Options
	Author(s)       : David W. Hankins
                          Tomek Mrugalski
                          Marcin Siodelski
                          Sheng Jiang
                          Suresh Krishnan
	Filename        : draft-ietf-dhc-option-guidelines-15.txt
	Pages           : 33
	Date            : 2013-12-09

Abstract:
   This document provides guidance to prospective DHCPv6 Option
   developers to help them creating option formats that are easily
   adoptable by existing DHCPv6 software.  It also provides guidelines
   for expert reviewers to evaluate new registrations.  This document
   updates RFC3315.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-option-guidelines

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-option-guidelines-15

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dhc-option-guidelines-15


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From tomasz.mrugalski@gmail.com  Mon Dec  9 10:37:36 2013
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E7341AE056 for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 10:37:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ixoJNnYmGtKH for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 10:37:34 -0800 (PST)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 340741AE043 for <dhcwg@ietf.org>; Mon,  9 Dec 2013 10:37:34 -0800 (PST)
Received: by mail-wg0-f48.google.com with SMTP id z12so3800274wgg.3 for <dhcwg@ietf.org>; Mon, 09 Dec 2013 10:37:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=V4Oemgls+QDFKFHck+/aXyjWfJqSbjbE6Fv8qOgJ99Q=; b=VNPx4yUvS0tEERzG3advJphu+IeLKy9cT0tlbCAdDNJXg2i1XO5nVdqJsGjU2CoTgL cp7VF352bsKaXrXD6bVRLlRFJ/ZR6DZ/mUgIh4g/Uo497MoHK9WCU4UBirNtZdPIMaZA npQjzzjHVZpXyKDjw0FQWAqlqMPurkwkRIvPjpGcZUp15NpD3C/XjBouUtRBo1Jn3/2i JY9mQNbzBolL9bBJZWjcCiymc5DK0Q/bwFDZiqpCocDgjOgu2+2sgVNdWoiyYrxwdnGL 5zA153hGDOZ9fUI4fjAnfc5AoqSdD5i7uZxtZ59HYMJPc/WUuC7te/j1Zjk8ddk52gex qEIw==
X-Received: by 10.180.105.199 with SMTP id go7mr15474871wib.53.1386614248558;  Mon, 09 Dec 2013 10:37:28 -0800 (PST)
Received: from ?IPv6:2001:470:6061:0:f66d:4ff:fe96:58f2? ([2001:470:6061:0:f66d:4ff:fe96:58f2]) by mx.google.com with ESMTPSA id x19sm27193192wia.5.2013.12.09.10.37.26 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Dec 2013 10:37:27 -0800 (PST)
Message-ID: <52A60DDE.6010405@gmail.com>
Date: Mon, 09 Dec 2013 19:37:18 +0100
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: "Bernie Volz" <volz@cisco.com>, dhcwg@ietf.org
References: <20131209182629.3798.19997.idtracker@ietfa.amsl.com>
In-Reply-To: <20131209182629.3798.19997.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.5.2
X-TagToolbar-Keys: D20131209193718770
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] Changes in draft-ietf-dhc-option-guidelines-15
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Dec 2013 18:37:36 -0000

Hi all,

After a long time, we finally managed to address (hopefully) all the
issues raised during IESG review. There's surprisingly large number of
changes:
- FQDN vs addresses section rewritten
  (addresses 2 or 3 DISCUSSes)
- Privacy considerations section added
  (Stephen Farrell requested it)
- Added clarification that the doc can be used during experts review
  (addressed Benoit Claise's positive DISCUSS)
- the wording about RFC5908 (NTP option) ugliness was eased. The text
  simply states that it should not be used as a template for new
  options. (Brian Haberman was unhappy about old text)
- added references to RFC5986, RFC5223
  (Richard Barnes' comment)
- added clarification to text if the draft updates 3315 or not
  (result of latest discussions about unknown-msg draft)
- many smaller clarifications and explanations
  (other nits from IESG)

Most of them could be considered clarification changes, except the one
about address vs FQDN. -14 text strongly suggested using address, unless
there are compelling reasons to use FQDN. The new text tries to make
more balanced approach and explores benefits and flaws of each
approach. This updated text has been agreed with IESG members that
raised DISCUSSes about its previous version.

Since this changes what WG agreed to, I'd like ask Bernie to run a short
WGLC on this to confirm that WG does not have strong objections in that
matter.

Tomek

On 09.12.2013 19:26, 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           : Guidelines for Creating New DHCPv6 Options
> 	Author(s)       : David W. Hankins
>                           Tomek Mrugalski
>                           Marcin Siodelski
>                           Sheng Jiang
>                           Suresh Krishnan
> 	Filename        : draft-ietf-dhc-option-guidelines-15.txt
> 	Pages           : 33
> 	Date            : 2013-12-09
> 
> Abstract:
>    This document provides guidance to prospective DHCPv6 Option
>    developers to help them creating option formats that are easily
>    adoptable by existing DHCPv6 software.  It also provides guidelines
>    for expert reviewers to evaluate new registrations.  This document
>    updates RFC3315.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dhc-option-guidelines
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-dhc-option-guidelines-15
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-option-guidelines-15
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
> 


From volz@cisco.com  Mon Dec  9 10:56:18 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5F0A1AE067 for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 10:56:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.501
X-Spam-Level: 
X-Spam-Status: No, score=-9.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B74r9GFt9a1O for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 10:56:13 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id C9C961ADFB4 for <dhcwg@ietf.org>; Mon,  9 Dec 2013 10:56:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10262; q=dns/txt; s=iport; t=1386615368; x=1387824968; h=from:to:subject:date:message-id:mime-version; bh=9MVdyp1aGo4B8krCI0Tk3Ymv7iQPEUYf8UzKWXcUyi0=; b=Xmc47JRGSn0cLCvBd+JP+y7LBROfM1xPAB93RhU43PvZK7OAX6crazDX WeL+0j0zErnP4XBq1aU3cIY7K9SCh+qUwLTPlceaAKkABjdjzBm0xiqJm yaKRtyu/gD8uMkVX2mqerQhksbo4v9wyxwlGRfeqqslpFxy0gxW693xWY U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvoGAAsRplKtJV2Z/2dsb2JhbABZgkNEOFOwQ4hSgTEWbQeCJwEELTgGIAEqViYBBBuHeg2jJp5FF45fg1iBEwOZRJBjgWuBPoIq
X-IronPort-AV: E=Sophos;i="4.93,859,1378857600"; d="scan'208,217";a="5456612"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-6.cisco.com with ESMTP; 09 Dec 2013 18:56:07 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id rB9Iu7wa031342 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Mon, 9 Dec 2013 18:56:07 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0123.003; Mon, 9 Dec 2013 12:56:07 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: (short) WGLC to confirm changes to draft-ietf-dhc-option-guidelines-15 - respond by December 16th
Thread-Index: Ac71D/14vu8Kz443ScCeXnNhzdEAcQ==
Date: Mon, 9 Dec 2013 18:56:06 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1ADDA991@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.241.102]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1ADDA991xmbrcdx04ciscoc_"
MIME-Version: 1.0
Subject: [dhcwg] (short) WGLC to confirm changes to draft-ietf-dhc-option-guidelines-15 - respond by December 16th
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Dec 2013 18:56:18 -0000

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

Hi:

While an earlier version of draft-ietf-dhc-option-guidelines was last calle=
d and went to the IESG, some of the IESG feedback changed the document in s=
ignificant ways and thus we would appreciate the WG review these changes. Y=
ou can use the tools at http://tools.ietf.org/html/draft-ietf-dhc-option-gu=
idelines to see the differences.

There is NO need to respond if you are in agreement (though you may certain=
ly do so).

If you do have issues with the changes made, please respond detailing your =
objections.

This will be a 1 week last call and thus you must respond by (end of day an=
ywhere in the world) December 16th.

Here's the list from Tomek's message outlining the major changes:


There's surprisingly large number of changes:

- FQDN vs addresses section rewritten

  (addresses 2 or 3 DISCUSSes)

- Privacy considerations section added

  (Stephen Farrell requested it)

- Added clarification that the doc can be used during experts review

  (addressed Benoit Claise's positive DISCUSS)

- the wording about RFC5908 (NTP option) ugliness was eased. The text

  simply states that it should not be used as a template for new

  options. (Brian Haberman was unhappy about old text)

- added references to RFC5986, RFC5223

  (Richard Barnes' comment)

- added clarification to text if the draft updates 3315 or not

  (result of latest discussions about unknown-msg draft)

- many smaller clarifications and explanations

  (other nits from IESG)



Most of them could be considered clarification changes, except the one abou=
t address vs FQDN. -14 text strongly suggested using address, unless there =
are compelling reasons to use FQDN. The new text tries to make more balance=
d approach and explores benefits and flaws of each approach. This updated t=
ext has been agreed with IESG members that raised DISCUSSes about its previ=
ous version.



-          Bernie and Tomek




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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:86121113;
	mso-list-type:hybrid;
	mso-list-template-ids:-296438916 20998308 67698691 67698693 67698689 67698=
691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">While an earlier version of draft-ietf-dhc-option-gu=
idelines was last called and went to the IESG, some of the IESG feedback ch=
anged the document in significant ways and thus we would appreciate the WG =
review these changes. You can use
 the tools at <a href=3D"http://tools.ietf.org/html/draft-ietf-dhc-option-g=
uidelines">
http://tools.ietf.org/html/draft-ietf-dhc-option-guidelines</a> to see the =
differences.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">There is NO need to respond if you are in agreement =
(though you may certainly do so).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">If you do have issues with the changes made, please =
respond detailing your objections.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This will be a 1 week last call and thus you must re=
spond by (end of day anywhere in the world) December 16<sup>th</sup>.<o:p><=
/o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Here&#8217;s the list from Tomek&#8217;s message out=
lining the major changes:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">There's surprisingly large number of changes:<o:p=
></o:p></p>
<p class=3D"MsoPlainText">- FQDN vs addresses section rewritten<o:p></o:p><=
/p>
<p class=3D"MsoPlainText">&nbsp; (addresses 2 or 3 DISCUSSes)<o:p></o:p></p=
>
<p class=3D"MsoPlainText">- Privacy considerations section added<o:p></o:p>=
</p>
<p class=3D"MsoPlainText">&nbsp; (Stephen Farrell requested it)<o:p></o:p><=
/p>
<p class=3D"MsoPlainText">- Added clarification that the doc can be used du=
ring experts review<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp; (addressed Benoit Claise's positive DISCUS=
S)<o:p></o:p></p>
<p class=3D"MsoPlainText">- the wording about RFC5908 (NTP option) ugliness=
 was eased. The text<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp; simply states that it should not be used a=
s a template for new<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp; options. (Brian Haberman was unhappy about=
 old text)<o:p></o:p></p>
<p class=3D"MsoPlainText">- added references to RFC5986, RFC5223<o:p></o:p>=
</p>
<p class=3D"MsoPlainText">&nbsp; (Richard Barnes' comment)<o:p></o:p></p>
<p class=3D"MsoPlainText">- added clarification to text if the draft update=
s 3315 or not<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp; (result of latest discussions about unknow=
n-msg draft)<o:p></o:p></p>
<p class=3D"MsoPlainText">- many smaller clarifications and explanations<o:=
p></o:p></p>
<p class=3D"MsoPlainText">&nbsp; (other nits from IESG)<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Most of them could be considered clarification ch=
anges, except the one about address vs FQDN. -14 text strongly suggested us=
ing address, unless there are compelling reasons to use FQDN. The new text =
tries to make more balanced approach
 and explores benefits and flaws of each approach. This updated text has be=
en agreed with IESG members that raised DISCUSSes about its previous versio=
n.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-left:.5in;text-indent:-.25in;mso-=
list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=3D"font:7=
.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;
</span></span><![endif]>Bernie and Tomek<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1ADDA991xmbrcdx04ciscoc_--

From Ted.Lemon@nominum.com  Mon Dec  9 11:17:37 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 646B81AE07A for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 11:17:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eQsLxcFU3VB5 for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 11:17:34 -0800 (PST)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by ietfa.amsl.com (Postfix) with ESMTP id C4B571AE4CB for <dhcwg@ietf.org>; Mon,  9 Dec 2013 11:17:34 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKUqYXSvabXAHLUR73+jDk3JcOmTI/35E1@postini.com; Mon, 09 Dec 2013 11:17:30 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 E35D91B82D0 for <dhcwg@ietf.org>; Mon,  9 Dec 2013 11:17:29 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id C2151190043; Mon,  9 Dec 2013 11:17:29 -0800 (PST)
Received: from vpna-132.vpn.nominum.com (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 9 Dec 2013 11:17:29 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <52A60DDE.6010405@gmail.com>
Date: Mon, 9 Dec 2013 14:17:25 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <722D47B4-9B4B-460F-BC53-B82807053E99@nominum.com>
References: <20131209182629.3798.19997.idtracker@ietfa.amsl.com> <52A60DDE.6010405@gmail.com>
To: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] Changes in draft-ietf-dhc-option-guidelines-15
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Dec 2013 19:17:37 -0000

Here's my review of the update, AD hat off.

Section 8, paragraph 3, talking about providing lists of IP addresses:

   This problem may be partially addressed by
   providing a list of addresses, rather than just a single one.  That,
   on the other hand, complicates client operation, as some kind of
   failover procedure has to be defined and implemented.

This goes against existing practice=97almost no DHCP option returns only =
a single IP address for a server, nor is this expected behavior.   =
Furthermore, cycling through a list of addresses is easy, and you'd have =
to do it with a DNS response as well.   So I don't think this point =
makes sense.

Next paragraph:

OLD:
   This allows pointing at
   more localized services.  However, such a practice requires violating
   DNS principles ('split horizon'), and hence is not recommended.
NEW:
   This is one way to provide localized addressing.   However, in order
   to do this, it is necessary to violate the DNS convention that a =
query
   on a particular name should always return the same answer (aside from
   ordering of IP addresses in the response, which is supposed to be =
varied
   by the name server).   This same locality of reference for =
configuration
   information can be achieved directly using DHCP, since the DHCP =
server
   must know the network topology in order to provide IP address or
   prefix configuration.

Next paragraph:

OLD:
   The other type of ambiguity is related to multiple provisioning
   domains (see Section 12), and may get a different answer from the DNS
   depending on which interface or DNS server is used to do the
   resolution.  This is particularly a problem when the normal expected
   use of the option makes sense with private DNS zone(s), as might be
   the case with a corporate VPN.  It may also be the case that the
   client has explicit DNS server configured so may not be using the
   corporate internal DNS server.
NEW:
   The other type of ambiguity is related to multiple provisioning
   domains (see Section 12).   The stub resolver on the DHCP client
   cannot at present be assumed to make the DNS query for a DHCP-
   supplied FQDN on the same interface on which it received its
   DHCP configuration, and may therefore get a different answer from
   the DNS than was intended.

   This is particularly a problem when
   the normal expected use of the option makes sense with private
   DNS zone(s), as might be the case on an enterprise network.  It
   may also be the case that the client has an explicit DNS server
   configured, and may therefore never query the enterprise network's
   internal DNS server.

This advice is simply wrong:

   It may be generalized that the preference for address or FQDN depends=09=

   on its envisaged usage.  Short lived (immediately consumed) data=09
   should be address based, while long timed information is better=09
   served with FQDN.

I don't think this is the basis on which the distinction should be made. =
  E.g., is the DNS server IP address a short-term data item?   I don't =
think so.   It's reasonable to expect that any data returned by the DHCP =
server will be used for the duration of the lease, so this distinction =
provides no guidance.

This paragraph likewise offers no useful guidance:

   Another aspect that should be considered is time required for the=09
   clients to notice any configuration changes.  Consider a case where a=09=

   server configures a service A using address and service B using FQDN.=09=

   When an administrator decides to update the configuration, he or she=09=

   can update the DHCP server configuration to change both services.  If=09=

   the clients do not support reconfigure (which is an optional feature=09=

   of RFC3315, but in some environments, e.g. cable modems, is=09
   mandatory), the configuration will be updated on clients after T1=09
   timer elapses.  Depending on the nature of the change (is it a new=09
   server added to a cluster of already operating servers or a new=09
   server that replaces the only available server that crashed?), this=09=

   may be an issue.  On the other hand, updating service B may be=09
   achieved with DNS record update.  That information may be cached by=09=

   caching DNS servers for up to TTL.  Depending on the values of T1 and=09=

   TTL, one update may be faster than another.  Furthermore, depending=09=

   on the nature of the change (planned modification or unexpected=09
   failure), T1 or TTL may be lowered before the change to speed up new=09=

   configuration adoption.

Since we don't know what the TTL or the T1 time will be, as protocol =
designers, we simply can't make assumptions about whether a DHCP option =
will be refreshed more quickly based on T1 or TTL.   Realistically, =
expectations about sudden network reconfiguration information being =
quickly propagated to the client are simply not dependable unless =
reconfigure is in fact available.

Next paragraph:


   Addresses have a benefit of being easier to implemented and handle by=09=

   the DHCP software.  An address option is simpler to use, its=09
   validation is trivial (multiple of 16 constitutes a valid option), is=09=

   explicit and does not allow any ambiguity.  It is faster (does not=09
   require extra round trip time), so it is more efficient, which can be=09=

   especially important for energy restricted devices.  It also does not=09=

   require having resolution capability.

If you keep the last sentence, it should say this:
   It also does not require that the client implement DNS resolution.

However, I'm not convinced that this is a compelling argument.

Section 16, paragraph 2:

   If multiple instances are=09
   allowed, the document MUST explain how to use them.  Care should be=09=

   taken to not assume the they will be processed in the other they=09
   appear in the message.  See Section 17 for more details.

s/other/order/

In section 22, looks like an editing error:

   On the other hand, if a new document replaces, modifies
   existing behavior, it should be noted that it updates the other
   document.  For example, [RFC6644] clearly updates [RFC3315] as it
   replaces existing with new text.
s/replaces, modifies/replaces or modifies/



From kkinnear@cisco.com  Mon Dec  9 13:08:12 2013
Return-Path: <kkinnear@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6C221AE5A2 for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 13:08:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BHSkCpen-2KX for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 13:08:10 -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 7C3591AE5A5 for <dhcwg@ietf.org>; Mon,  9 Dec 2013 13:08:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4480; q=dns/txt; s=iport; t=1386623280; x=1387832880; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=z6DoI7Tq5MdhyEJNDiiQ6oqPCZFPZLQ6ImZXSvjlWSg=; b=O5xeiBRLFKv3OjiW6U64sRGwuwoox4PQDzeiUahhrCzAiVoprV7CQbVC CVK8k0GxJAW5K1OmJiJFzPmAw8BAAcTQZdail17umJyhU2kzrSj2ONUcG CH6eYp1cZU1xeLvvfsNadWeS5O9GN9OD4PrMn5W42iNhakVOZDht35p2Q 0=;
X-IronPort-AV: E=Sophos;i="4.93,860,1378857600"; d="scan'208";a="99939644"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-4.cisco.com with ESMTP; 09 Dec 2013 21:07:59 +0000
Received: from [161.44.65.108] ([161.44.65.108]) (authenticated bits=0) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rB9L7ucQ019834 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 9 Dec 2013 21:07:57 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Kim Kinnear <kkinnear@cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADD09A3@xmb-rcd-x04.cisco.com>
Date: Mon, 9 Dec 2013 16:07:55 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <36CBBA0C-386C-4F0D-80FE-1F30F7898611@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADD09A3@xmb-rcd-x04.cisco.com>
To: Bernie Volz (volz) <volz@cisco.com>
X-Mailer: Apple Mail (2.1510)
X-Authenticated-User: kkinnear
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Kim Kinnear <kkinnear@cisco.com>
Subject: Re: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Dec 2013 21:08:12 -0000

Perhaps unsurprisingly, I support the working group adopting
this draft as a work item.

Regards -- Kim

On Dec 4, 2013, at 11:46 AM, Bernie Volz (volz) <volz@cisco.com> wrote:

> Hi all:
>=20
> This is a WG Call for Adoption for =
http://tools.ietf.org/html/draft-kinnear-dhc-dhcpv4-active-leasequery-02. =
This call is being initiated to determine whether there is WG consensus =
to adopt this work as DHC WG item. Please state whether or not you're in =
favor of the adoption by replying to this mail. If you are not in favor, =
please also state your objections in your response. This adoption call =
will complete on December 18, 2013.
>=20
> This call is being initiated because during the call for adoption for =
draft-raghuvanshi-dhc-dhcpv6-active-leasequery-00, which was just =
adopted, several people asked about the related DHCPv4 work. Kim =
republished the DHCPv4 draft (with minor updates) as it had expired a =
while ago. So, we are seeking input as to whether the WG should now also =
work on the DHCPv4 version of active leasequery, given that the DHCPv6 =
version was adopted.
>=20
> Regards,
> Tomek & Bernie
>=20
> -----Original Message-----
> From: Kim Kinnear (kkinnear)=20
> Sent: Wednesday, December 04, 2013 11:25 AM
> To: dhcwg@ietf.org
> Cc: Kim Kinnear (kkinnear); Bernie Volz (volz); Tomek Mrugalski
> Subject: New Version Notification for =
draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
>=20
>=20
> Folks,
>=20
> During the adoption discussion about DHCPv6 Active Leasequery there =
was some discussion about having a corresponding DHCPv4 Active =
Leasequery capability.  If there is sufficient interest in a DHCPv4 =
Active Leasequery capability to parallel the DHCPv6 capability that was =
adopted as a DHC WG work item recently, then we can decide whether or =
not we want to have two drafts moving toward two RFC's, or combine them =
into one draft.
>=20
> But the first question is whether or not there is sufficient interest =
in having a DHCPv4 Active Leasequery capability at all!
>=20
> In order to help decide this question, I have updated the existing
> DHCPv4 Active Leasequery draft from a couple of years ago, and =
resubmitted it as an individual submission -- as recommended by Bernie =
and Tomek.
>=20
> Below you can find the information on how to find this new draft.
>=20
> Regards -- Kim
>=20
>=20
> Begin forwarded message:
>=20
>> From: <internet-drafts@ietf.org>
>> Subject: New Version Notification for=20
>> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
>> Date: December 4, 2013 10:01:03 AM EST
>> To: Bernie Volz <volz@cisco.com>, Mark Stapp <mjs@cisco.com>, Kim=20
>> Kinnear <kkinnear@cisco.com>, Neil Russell <neil.e.russell@gmail.com>
>>=20
>>=20
>> A new version of I-D,=20
>> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
>> has been successfully submitted by Kim Kinnear and posted to the IETF=20=

>> repository.
>>=20
>> Filename:	 draft-kinnear-dhc-dhcpv4-active-leasequery
>> Revision:	 02
>> Title:		 Active DHCPv4 Lease Query
>> Creation date:	 2013-12-04
>> Group:		 Individual Submission
>> Number of pages: 22
>> URL:             =
http://www.ietf.org/internet-drafts/draft-kinnear-dhc-dhcpv4-active-leaseq=
uery-02.txt
>> Status:          =
http://datatracker.ietf.org/doc/draft-kinnear-dhc-dhcpv4-active-leasequery=

>> Htmlized:        =
http://tools.ietf.org/html/draft-kinnear-dhc-dhcpv4-active-leasequery-02
>> Diff:            =
http://www.ietf.org/rfcdiff?url2=3Ddraft-kinnear-dhc-dhcpv4-active-leasequ=
ery-02
>>=20
>> Abstract:
>>  The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has been
>>  extended with a Leasequery capability that allows a client to =
request
>>  information about DHCPv4 bindings.  That mechanism is limited to
>>  queries for individual bindings.  In some situations individual
>>  binding queries may not be efficient, or even possible.  In =
addition,
>>  continuous update of an external client with Leasequery data is
>>  sometimes desired. This document expands on the DHCPv4 Leasequery
>>  protocol, and allows for active transfer of near real-time DHCPv4
>>  address binding information data via TCP.
>>=20
>>=20
>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of=20
>> submission until the htmlized version and diff are available at =
tools.ietf.org.
>>=20
>> The IETF Secretariat
>>=20
>=20


From Ted.Lemon@nominum.com  Mon Dec  9 13:59:57 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDA6D1AE5B9 for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 13:59:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4sY0qeonNi3a for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 13:59:56 -0800 (PST)
Received: from exprod7og127.obsmtp.com (exprod7og127.obsmtp.com [64.18.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id C40641AE57C for <dhcwg@ietf.org>; Mon,  9 Dec 2013 13:59:56 -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 DSNKUqY9V0bxrMvaE4SUCZrksqonOOmZN1E+@postini.com; Mon, 09 Dec 2013 13:59:52 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 C5B331B82B6 for <dhcwg@ietf.org>; Mon,  9 Dec 2013 13:59:51 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id A56C7190043; Mon,  9 Dec 2013 13:59:51 -0800 (PST)
Received: from vpna-132.vpn.nominum.com (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 9 Dec 2013 13:59:51 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADD09A3@xmb-rcd-x04.cisco.com>
Date: Mon, 9 Dec 2013 16:59:47 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <41E0E078-319B-47BF-B8EE-8B93E1521E26@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADD09A3@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Dec 2013 21:59:57 -0000

On Dec 4, 2013, at 11:46 AM, Bernie Volz (volz) <volz@cisco.com> wrote:
> So, we are seeking input as to whether the WG should now also work on =
the DHCPv4 version of active leasequery, given that the DHCPv6 version =
was adopted.

Not at all wearing my AD hat, I think it's worth doing.


From volz@cisco.com  Mon Dec  9 18:38:58 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C2661AE0FB for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 18:38:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8KuMx-dMdeEm for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 18:38:56 -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 5685F1ADED7 for <dhcwg@ietf.org>; Mon,  9 Dec 2013 18:38:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1745; q=dns/txt; s=iport; t=1386643131; x=1387852731; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=tuvriIA+12bB2nS5LL/moGS9uz65+58+4dNbJAAGX1k=; b=gVAgOXCP7HWseiuqiiwNYrQldPTrx7BXuBfAMds6jIcFUZHx58ZvCy/t s7b9a1ylaf/OoP6D3zKW6bmeuJpC+bd/2VLeL40dv1bgrsFvIPSPeQVoy PYQ7AbnaI0zS27BZ2ThVcSNvDRHVza0DXKxdpSJjwdkPkInr+ggHeLWT9 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoYFADB+plKtJXG+/2dsb2JhbABZgwc4U7kTgSIWbQeCJQEBAQQdHUsEAgEIEQQBAQsUCQcyFAkIAQEEEwiHeg3AUheOPwEBHgYyBoMagRMDmUSQY4FrgT6BcTk
X-IronPort-AV: E=Sophos;i="4.93,862,1378857600"; d="scan'208";a="290453479"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-7.cisco.com with ESMTP; 10 Dec 2013 02:38:51 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id rBA2cp4O005758 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Tue, 10 Dec 2013 02:38:51 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0123.003; Mon, 9 Dec 2013 20:38:51 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
Thread-Index: Ac7xD0TQ86CV+plkQwGdrBXmDcXNywEEvfxQ
Date: Tue, 10 Dec 2013 02:38:50 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1ADDBD00@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADD09A3@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADD09A3@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.241.102]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 10 Dec 2013 02:38:58 -0000

<WG co-chair hat off>

I support adopting this work - but I am a co-author so that's probably not =
a big surprise.

As the WG has adopted the DHCPv6 work, this really should be pretty easy, f=
rom a IETF standards view, to work on as it is similar extensions to the DH=
CPv4 bulk leasequery to support this.

<WG co-chair hat on>

While it is an early reminder as we still have more than a week to go, but =
... please do forward your thoughts after reviewing the document.

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Wednesday, December 04, 2013 11:47 AM
To: Kim Kinnear (kkinnear); dhcwg@ietf.org
Subject: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequer=
y-02 - Respond by Dec 18

Hi all:

This is a WG Call for Adoption for http://tools.ietf.org/html/draft-kinnear=
-dhc-dhcpv4-active-leasequery-02. This call is being initiated to determine=
 whether there is WG consensus to adopt this work as DHC WG item. Please st=
ate whether or not you're in favor of the adoption by replying to this mail=
. If you are not in favor, please also state your objections in your respon=
se. This adoption call will complete on December 18, 2013.

This call is being initiated because during the call for adoption for draft=
-raghuvanshi-dhc-dhcpv6-active-leasequery-00, which was just adopted, sever=
al people asked about the related DHCPv4 work. Kim republished the DHCPv4 d=
raft (with minor updates) as it had expired a while ago. So, we are seeking=
 input as to whether the WG should now also work on the DHCPv4 version of a=
ctive leasequery, given that the DHCPv6 version was adopted.

Regards,
Tomek & Bernie


From volz@cisco.com  Mon Dec  9 20:03:41 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43C631AE18B for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 20:03:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.501
X-Spam-Level: 
X-Spam-Status: No, score=-9.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cLmJ2U9QNSCg for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 20:03:39 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) by ietfa.amsl.com (Postfix) with ESMTP id 77B541AE183 for <dhcwg@ietf.org>; Mon,  9 Dec 2013 20:03:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10965; q=dns/txt; s=iport; t=1386648214; x=1387857814; h=from:to:subject:date:message-id:mime-version; bh=NjcSI6mD3lDteUu6CFiPXnyY42+qjkfsxGtE7O5BqLw=; b=WGjrGq4n+oCgIR7ViLekRT3w1VPRaqf59Xgx58Af9z6BiLba9fLT34YZ +YIAbCu+QIdrHSB8g8tst7XBCs9ACSUJjSU2aRUWhx3CxoL0mgk7ZdNcA Vywh1ApX09Cq1CiNPRX3z8hnzuoPwPcMmiNQ3FH1aSKzQJiLY8xn2w2M3 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkIHACiSplKtJV2Z/2dsb2JhbABZgkNEOFOwQYhSgSIWbQeCJQEBAQQtXgEZBAEBCx05FAkJAQQTCId6DaFxnlwXjl83gyGBEwOZRJBjgWuBPoIq
X-IronPort-AV: E=Sophos;i="4.93,863,1378857600"; d="scan'208,217";a="5577509"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-8.cisco.com with ESMTP; 10 Dec 2013 04:03:34 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id rBA43YYs002392 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Tue, 10 Dec 2013 04:03:34 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0123.003; Mon, 9 Dec 2013 22:03:33 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Results of WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 - Respond by Dec 2, 2013
Thread-Index: Ac71XIs8GojyoksERLKCFoTytxvHPA==
Date: Tue, 10 Dec 2013 04:03:32 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1ADDBFF8@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.241.102]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1ADDBFF8xmbrcdx04ciscoc_"
MIME-Version: 1.0
Subject: [dhcwg] Results of WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 - Respond by Dec 2, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 10 Dec 2013 04:03:41 -0000

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

Hi:

We believe this document has sufficient support to move forward and there w=
ere no objections.

The authors are requested to publish an updated draft with the reported iss=
ues and nits addressed, at which point publication will be requested.


-          Bernie

From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of B=
ernie Volz (volz)
Sent: Monday, November 18, 2013 12:15 PM
To: dhcwg@ietf.org
Subject: [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 - Respond by=
 Dec 2, 2013


Folks, the authors of draft-ietf-dhc-dhcpv6-unknown-msg-03 (http://tools.ie=
tf.org/html/draft-ietf-dhc-dhcpv6-unknown-msg-03) believe it is ready for w=
orking group last call. Please review this draft and indicate whether or no=
t you feel it is ready to be published. Your input is important! Please res=
pond by Dec 2nd, 2013.



At the time of this writing, there is no IPR reported against this draft.



Thanks,


-          Tomek & Bernie


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
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;}
/* List Definitions */
@list l0
	{mso-list-id:866522167;
	mso-list-type:hybrid;
	mso-list-template-ids:1690722640 1420754368 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1
	{mso-list-id:912355465;
	mso-list-type:hybrid;
	mso-list-template-ids:324035966 1704460954 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:5;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi:<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">We believe this docume=
nt has sufficient support to move forward and there were no objections.<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">The authors are reques=
ted to publish an updated draft with the reported issues and nits addressed=
, at which point publication will be requested.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo3"><![if !supportLists]><span style=3D"color:#1F497D"><span style=3D"m=
so-list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"color:#1F497D">Bernie<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> dhcwg-bo=
unces@ietf.org [mailto:dhcwg-bounces@ietf.org]
<b>On Behalf Of </b>Bernie Volz (volz)<br>
<b>Sent:</b> Monday, November 18, 2013 12:15 PM<br>
<b>To:</b> dhcwg@ietf.org<br>
<b>Subject:</b> [dhcwg] WGLC for draft-ietf-dhc-dhcpv6-unknown-msg-03 - Res=
pond by Dec 2, 2013<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Folks, the authors of draft-ietf-dhc-dhcpv6-unkno=
wn-msg-03 (<a href=3D"http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-unkn=
own-msg-03">http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-unknown-msg-03=
</a>) believe it is ready for working
 group last call. Please review this draft and indicate whether or not you =
feel it is ready to be published. Your input is important! Please respond b=
y Dec 2<sup>nd</sup>, 2013.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">At the time of this writing, there is no IPR repo=
rted against this draft.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Tomek &amp; Bernie<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1ADDBFF8xmbrcdx04ciscoc_--

From draghuva@cisco.com  Mon Dec  9 20:29:45 2013
Return-Path: <draghuva@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFA191AE199 for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 20:29:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.502
X-Spam-Level: 
X-Spam-Status: No, score=-9.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SgN2pQHT1C6x for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 20:29:43 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id 9BFB91AE197 for <dhcwg@ietf.org>; Mon,  9 Dec 2013 20:29:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4492; q=dns/txt; s=iport; t=1386649778; x=1387859378; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=cdC1jbnNvAd8hzBShk1UAhatQBMDuuhlk+ADIFAmjFo=; b=ehnzQnjJf3I8+KuM75K100VT25inwvmuhTsxXRGllHd04oklastZEjT0 OkTxkONMvkIhBMhc2JTPEtHsZTegUqvHUWlRZsjX+JPaPDqTbAN99GPck 3uF6LEDfLpGF5RDlOOBty+II4CaXZGO93CP2ZhhtD9YpIa1TLlnsF6yco 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAMuXplKtJXHA/2dsb2JhbABZgwc4TQa5E4EjFnSCJQEBAQQBAQEaHTQXBgEIEQMBAQEfMQYLHQoEAQkJCYdnAw8IBblWDYZnF4x9gTsHAQEcQIQtA5QxgXiBa4EwiyqFOYFrgT6BaAkXIg
X-IronPort-AV: E=Sophos;i="4.93,863,1378857600";  d="scan'208";a="5577683"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by alln-iport-4.cisco.com with ESMTP; 10 Dec 2013 04:29:38 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id rBA4TcfE004886 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Tue, 10 Dec 2013 04:29:38 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.34]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0123.003; Mon, 9 Dec 2013 22:29:37 -0600
From: "Dushyant Raghuvanshi (draghuva)" <draghuva@cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, "Kim Kinnear (kkinnear)" <kkinnear@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
Thread-Index: AQHO9WBvCfAoyNkwCEyQ9quqPOif0Q==
Date: Tue, 10 Dec 2013 04:29:37 +0000
Message-ID: <CECC9632.246DA%draghuva@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.62.128]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1674729BFAEA934BB18B162D75DD9599@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 10 Dec 2013 04:29:46 -0000

I support this draft to be adopted as working group item.

Thanks,
Dushyant.

On 04/12/13 10:16 PM, "Bernie Volz (volz)" <volz@cisco.com> wrote:

>Hi all:
>
>This is a WG Call for Adoption for
>http://tools.ietf.org/html/draft-kinnear-dhc-dhcpv4-active-leasequery-02.
>This call is being initiated to determine whether there is WG consensus
>to adopt this work as DHC WG item. Please state whether or not you're in
>favor of the adoption by replying to this mail. If you are not in favor,
>please also state your objections in your response. This adoption call
>will complete on December 18, 2013.
>
>This call is being initiated because during the call for adoption for
>draft-raghuvanshi-dhc-dhcpv6-active-leasequery-00, which was just
>adopted, several people asked about the related DHCPv4 work. Kim
>republished the DHCPv4 draft (with minor updates) as it had expired a
>while ago. So, we are seeking input as to whether the WG should now also
>work on the DHCPv4 version of active leasequery, given that the DHCPv6
>version was adopted.
>
>Regards,
>Tomek & Bernie
>
>-----Original Message-----
>From: Kim Kinnear (kkinnear)
>Sent: Wednesday, December 04, 2013 11:25 AM
>To: dhcwg@ietf.org
>Cc: Kim Kinnear (kkinnear); Bernie Volz (volz); Tomek Mrugalski
>Subject: New Version Notification for
>draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
>
>
>Folks,
>
>During the adoption discussion about DHCPv6 Active Leasequery there was
>some discussion about having a corresponding DHCPv4 Active Leasequery
>capability.  If there is sufficient interest in a DHCPv4 Active
>Leasequery capability to parallel the DHCPv6 capability that was adopted
>as a DHC WG work item recently, then we can decide whether or not we want
>to have two drafts moving toward two RFC's, or combine them into one
>draft.
>
>But the first question is whether or not there is sufficient interest in
>having a DHCPv4 Active Leasequery capability at all!
>
>In order to help decide this question, I have updated the existing
>DHCPv4 Active Leasequery draft from a couple of years ago, and
>resubmitted it as an individual submission -- as recommended by Bernie
>and Tomek.
>
>Below you can find the information on how to find this new draft.
>
>Regards -- Kim
>
>
>Begin forwarded message:
>
>> From: <internet-drafts@ietf.org>
>> Subject: New Version Notification for
>> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
>> Date: December 4, 2013 10:01:03 AM EST
>> To: Bernie Volz <volz@cisco.com>, Mark Stapp <mjs@cisco.com>, Kim
>> Kinnear <kkinnear@cisco.com>, Neil Russell <neil.e.russell@gmail.com>
>>=20
>>=20
>> A new version of I-D,
>> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
>> has been successfully submitted by Kim Kinnear and posted to the IETF
>> repository.
>>=20
>> Filename:	 draft-kinnear-dhc-dhcpv4-active-leasequery
>> Revision:	 02
>> Title:		 Active DHCPv4 Lease Query
>> Creation date:	 2013-12-04
>> Group:		 Individual Submission
>> Number of pages: 22
>> URL:           =20
>>http://www.ietf.org/internet-drafts/draft-kinnear-dhc-dhcpv4-active-lease
>>query-02.txt
>> Status:        =20
>>http://datatracker.ietf.org/doc/draft-kinnear-dhc-dhcpv4-active-leasequer
>>y
>> Htmlized:      =20
>>http://tools.ietf.org/html/draft-kinnear-dhc-dhcpv4-active-leasequery-02
>> Diff:          =20
>>http://www.ietf.org/rfcdiff?url2=3Ddraft-kinnear-dhc-dhcpv4-active-leaseq=
ue
>>ry-02
>>=20
>> Abstract:
>>   The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has been
>>   extended with a Leasequery capability that allows a client to request
>>   information about DHCPv4 bindings.  That mechanism is limited to
>>   queries for individual bindings.  In some situations individual
>>   binding queries may not be efficient, or even possible.  In addition,
>>   continuous update of an external client with Leasequery data is
>>   sometimes desired. This document expands on the DHCPv4 Leasequery
>>   protocol, and allows for active transfer of near real-time DHCPv4
>>   address binding information data via TCP.
>>=20
>>=20
>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of
>> submission until the htmlized version and diff are available at
>>tools.ietf.org.
>>=20
>> The IETF Secretariat
>>=20
>
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www.ietf.org/mailman/listinfo/dhcwg


From dkukrety@cisco.com  Mon Dec  9 20:46:18 2013
Return-Path: <dkukrety@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 361B81AE1A0 for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 20:46:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.502
X-Spam-Level: 
X-Spam-Status: No, score=-9.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eFd0NMkzhZ75 for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 20:46:16 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) by ietfa.amsl.com (Postfix) with ESMTP id C0F971AE197 for <dhcwg@ietf.org>; Mon,  9 Dec 2013 20:46:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4628; q=dns/txt; s=iport; t=1386650771; x=1387860371; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=MdKcFdOUrYfg0DYA3B5pCFvj88OandxEIG3i/a0iGEY=; b=iWL+AlKoJ2wy0B750blg5q17x3mVhsDZzzv/NqpAcNHl8fvrv1G+Dhir 2sK8a9mTW3R7Bk6eUNIn+9hN90MesvIauORCaVxo4S7Wa+HjW6GpvQvvD K3ui3ZVKlDSydpWsb5nBksNvE9aZr2t4xe912el+7WZpj/fIFcL4LHRb0 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYFAEWcplKtJV2Z/2dsb2JhbABZgwc4TQa5E4EjFnSCJQEBAQMBAQEBGh00EAcEAgEIEQMBAQELFAkHIQYLFAkIAQEEAQkJCAGHZwMJBggFuVUNhmcXjH2BOwcBAR44BoMagRMDlDGBeIMbiyqFOYFrgT6BaAkXIg
X-IronPort-AV: E=Sophos;i="4.93,863,1378857600";  d="scan'208";a="5574824"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-3.cisco.com with ESMTP; 10 Dec 2013 04:45:57 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id rBA4jvxK018055 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Tue, 10 Dec 2013 04:45:57 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.30]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0123.003; Mon, 9 Dec 2013 22:45:57 -0600
From: "Deepak Kukrety (dkukrety)" <dkukrety@cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, "Kim Kinnear (kkinnear)" <kkinnear@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
Thread-Index: Ac7xD0TQ86CV+plkQwGdrBXmDcXNywEU0brA
Date: Tue, 10 Dec 2013 04:45:56 +0000
Message-ID: <D11924848C1D9B47805849761D83FC1E3F892999@xmb-rcd-x01.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADD09A3@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADD09A3@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.52.24]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 10 Dec 2013 04:46:18 -0000

I support adopting this work as DHC WG item.

Regards
Deepak

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Wednesday, December 04, 2013 10:17 PM
To: Kim Kinnear (kkinnear); dhcwg@ietf.org
Subject: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequer=
y-02 - Respond by Dec 18

Hi all:

This is a WG Call for Adoption for http://tools.ietf.org/html/draft-kinnear=
-dhc-dhcpv4-active-leasequery-02. This call is being initiated to determine=
 whether there is WG consensus to adopt this work as DHC WG item. Please st=
ate whether or not you're in favor of the adoption by replying to this mail=
. If you are not in favor, please also state your objections in your respon=
se. This adoption call will complete on December 18, 2013.

This call is being initiated because during the call for adoption for draft=
-raghuvanshi-dhc-dhcpv6-active-leasequery-00, which was just adopted, sever=
al people asked about the related DHCPv4 work. Kim republished the DHCPv4 d=
raft (with minor updates) as it had expired a while ago. So, we are seeking=
 input as to whether the WG should now also work on the DHCPv4 version of a=
ctive leasequery, given that the DHCPv6 version was adopted.

Regards,
Tomek & Bernie

-----Original Message-----
From: Kim Kinnear (kkinnear)=20
Sent: Wednesday, December 04, 2013 11:25 AM
To: dhcwg@ietf.org
Cc: Kim Kinnear (kkinnear); Bernie Volz (volz); Tomek Mrugalski
Subject: New Version Notification for draft-kinnear-dhc-dhcpv4-active-lease=
query-02.txt


Folks,

During the adoption discussion about DHCPv6 Active Leasequery there was som=
e discussion about having a corresponding DHCPv4 Active Leasequery capabili=
ty.  If there is sufficient interest in a DHCPv4 Active Leasequery capabili=
ty to parallel the DHCPv6 capability that was adopted as a DHC WG work item=
 recently, then we can decide whether or not we want to have two drafts mov=
ing toward two RFC's, or combine them into one draft.

But the first question is whether or not there is sufficient interest in ha=
ving a DHCPv4 Active Leasequery capability at all!

In order to help decide this question, I have updated the existing
DHCPv4 Active Leasequery draft from a couple of years ago, and resubmitted =
it as an individual submission -- as recommended by Bernie and Tomek.

Below you can find the information on how to find this new draft.

Regards -- Kim


Begin forwarded message:

> From: <internet-drafts@ietf.org>
> Subject: New Version Notification for=20
> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
> Date: December 4, 2013 10:01:03 AM EST
> To: Bernie Volz <volz@cisco.com>, Mark Stapp <mjs@cisco.com>, Kim=20
> Kinnear <kkinnear@cisco.com>, Neil Russell <neil.e.russell@gmail.com>
>=20
>=20
> A new version of I-D,=20
> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
> has been successfully submitted by Kim Kinnear and posted to the IETF=20
> repository.
>=20
> Filename:	 draft-kinnear-dhc-dhcpv4-active-leasequery
> Revision:	 02
> Title:		 Active DHCPv4 Lease Query
> Creation date:	 2013-12-04
> Group:		 Individual Submission
> Number of pages: 22
> URL:             http://www.ietf.org/internet-drafts/draft-kinnear-dhc-dh=
cpv4-active-leasequery-02.txt
> Status:          http://datatracker.ietf.org/doc/draft-kinnear-dhc-dhcpv4=
-active-leasequery
> Htmlized:        http://tools.ietf.org/html/draft-kinnear-dhc-dhcpv4-acti=
ve-leasequery-02
> Diff:            http://www.ietf.org/rfcdiff?url2=3Ddraft-kinnear-dhc-dhc=
pv4-active-leasequery-02
>=20
> Abstract:
>   The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has been
>   extended with a Leasequery capability that allows a client to request
>   information about DHCPv4 bindings.  That mechanism is limited to
>   queries for individual bindings.  In some situations individual
>   binding queries may not be efficient, or even possible.  In addition,
>   continuous update of an external client with Leasequery data is
>   sometimes desired. This document expands on the DHCPv4 Leasequery
>   protocol, and allows for active transfer of near real-time DHCPv4
>   address binding information data via TCP.
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of=20
> submission until the htmlized version and diff are available at tools.iet=
f.org.
>=20
> The IETF Secretariat
>=20

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

From jiangsheng@huawei.com  Mon Dec  9 22:13:58 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C8CE1AE23D for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 22:13:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ezsVJD4B4E16 for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 22:13:55 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7B85D1AE23C for <dhcwg@ietf.org>; Mon,  9 Dec 2013 22:13:55 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AYV10858; Tue, 10 Dec 2013 06:13:49 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 10 Dec 2013 06:13:41 +0000
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 10 Dec 2013 06:13:48 +0000
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.51]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.03.0158.001; Tue, 10 Dec 2013 14:13:40 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
Thread-Index: Ac7xD0TQ86CV+plkQwGdrBXmDcXNywEEvfxQABMpveA=
Date: Tue, 10 Dec 2013 06:13:39 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923ADC3975@nkgeml512-mbx.china.huawei.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADD09A3@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADDBD00@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADDBD00@xmb-rcd-x04.cisco.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 10 Dec 2013 06:13:58 -0000

SSBzdXBwb3J0IHRoZSBhZG9wdGlvbiBvZiB0aGUgZG9jdW1lbnQuIFVzZWZ1bCB3b3JrLg0KDQpT
aGVuZw0KDQo+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj5Gcm9tOiBkaGN3ZyBbbWFpbHRv
OmRoY3dnLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBCZXJuaWUgVm9seiAodm9seikN
Cj5TZW50OiBUdWVzZGF5LCBEZWNlbWJlciAxMCwgMjAxMyAxMDozOSBBTQ0KPlRvOiBkaGN3Z0Bp
ZXRmLm9yZw0KPlN1YmplY3Q6IFJlOiBbZGhjd2ddIFdHIEFkb3B0aW9uIENhbGwNCj5kcmFmdC1r
aW5uZWFyLWRoYy1kaGNwdjQtYWN0aXZlLWxlYXNlcXVlcnktMDIgLSBSZXNwb25kIGJ5IERlYyAx
OA0KPg0KPjxXRyBjby1jaGFpciBoYXQgb2ZmPg0KPg0KPkkgc3VwcG9ydCBhZG9wdGluZyB0aGlz
IHdvcmsgLSBidXQgSSBhbSBhIGNvLWF1dGhvciBzbyB0aGF0J3MgcHJvYmFibHkgbm90IGENCj5i
aWcgc3VycHJpc2UuDQo+DQo+QXMgdGhlIFdHIGhhcyBhZG9wdGVkIHRoZSBESENQdjYgd29yaywg
dGhpcyByZWFsbHkgc2hvdWxkIGJlIHByZXR0eSBlYXN5LA0KPmZyb20gYSBJRVRGIHN0YW5kYXJk
cyB2aWV3LCB0byB3b3JrIG9uIGFzIGl0IGlzIHNpbWlsYXIgZXh0ZW5zaW9ucyB0byB0aGUNCj5E
SENQdjQgYnVsayBsZWFzZXF1ZXJ5IHRvIHN1cHBvcnQgdGhpcy4NCj4NCj48V0cgY28tY2hhaXIg
aGF0IG9uPg0KPg0KPldoaWxlIGl0IGlzIGFuIGVhcmx5IHJlbWluZGVyIGFzIHdlIHN0aWxsIGhh
dmUgbW9yZSB0aGFuIGEgd2VlayB0byBnbywgYnV0IC4uLg0KPnBsZWFzZSBkbyBmb3J3YXJkIHlv
dXIgdGhvdWdodHMgYWZ0ZXIgcmV2aWV3aW5nIHRoZSBkb2N1bWVudC4NCj4NCj4tIEJlcm5pZQ0K
Pg0KPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+RnJvbTogZGhjd2cgW21haWx0bzpkaGN3
Zy1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgQmVybmllIFZvbHoNCj4odm9seikNCj5T
ZW50OiBXZWRuZXNkYXksIERlY2VtYmVyIDA0LCAyMDEzIDExOjQ3IEFNDQo+VG86IEtpbSBLaW5u
ZWFyIChra2lubmVhcik7IGRoY3dnQGlldGYub3JnDQo+U3ViamVjdDogW2RoY3dnXSBXRyBBZG9w
dGlvbiBDYWxsDQo+ZHJhZnQta2lubmVhci1kaGMtZGhjcHY0LWFjdGl2ZS1sZWFzZXF1ZXJ5LTAy
IC0gUmVzcG9uZCBieSBEZWMgMTgNCj4NCj5IaSBhbGw6DQo+DQo+VGhpcyBpcyBhIFdHIENhbGwg
Zm9yIEFkb3B0aW9uIGZvcg0KPmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWtpbm5l
YXItZGhjLWRoY3B2NC1hY3RpdmUtbGVhc2VxdWVyeS0wMi4NCj5UaGlzIGNhbGwgaXMgYmVpbmcg
aW5pdGlhdGVkIHRvIGRldGVybWluZSB3aGV0aGVyIHRoZXJlIGlzIFdHIGNvbnNlbnN1cyB0bw0K
PmFkb3B0IHRoaXMgd29yayBhcyBESEMgV0cgaXRlbS4gUGxlYXNlIHN0YXRlIHdoZXRoZXIgb3Ig
bm90IHlvdSdyZSBpbiBmYXZvcg0KPm9mIHRoZSBhZG9wdGlvbiBieSByZXBseWluZyB0byB0aGlz
IG1haWwuIElmIHlvdSBhcmUgbm90IGluIGZhdm9yLCBwbGVhc2UgYWxzbw0KPnN0YXRlIHlvdXIg
b2JqZWN0aW9ucyBpbiB5b3VyIHJlc3BvbnNlLiBUaGlzIGFkb3B0aW9uIGNhbGwgd2lsbCBjb21w
bGV0ZSBvbg0KPkRlY2VtYmVyIDE4LCAyMDEzLg0KPg0KPlRoaXMgY2FsbCBpcyBiZWluZyBpbml0
aWF0ZWQgYmVjYXVzZSBkdXJpbmcgdGhlIGNhbGwgZm9yIGFkb3B0aW9uIGZvcg0KPmRyYWZ0LXJh
Z2h1dmFuc2hpLWRoYy1kaGNwdjYtYWN0aXZlLWxlYXNlcXVlcnktMDAsIHdoaWNoIHdhcyBqdXN0
IGFkb3B0ZWQsDQo+c2V2ZXJhbCBwZW9wbGUgYXNrZWQgYWJvdXQgdGhlIHJlbGF0ZWQgREhDUHY0
IHdvcmsuIEtpbSByZXB1Ymxpc2hlZCB0aGUNCj5ESENQdjQgZHJhZnQgKHdpdGggbWlub3IgdXBk
YXRlcykgYXMgaXQgaGFkIGV4cGlyZWQgYSB3aGlsZSBhZ28uIFNvLCB3ZSBhcmUNCj5zZWVraW5n
IGlucHV0IGFzIHRvIHdoZXRoZXIgdGhlIFdHIHNob3VsZCBub3cgYWxzbyB3b3JrIG9uIHRoZSBE
SENQdjQNCj52ZXJzaW9uIG9mIGFjdGl2ZSBsZWFzZXF1ZXJ5LCBnaXZlbiB0aGF0IHRoZSBESENQ
djYgdmVyc2lvbiB3YXMgYWRvcHRlZC4NCj4NCj5SZWdhcmRzLA0KPlRvbWVrICYgQmVybmllDQo+
DQo+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj5kaGN3
ZyBtYWlsaW5nIGxpc3QNCj5kaGN3Z0BpZXRmLm9yZw0KPmh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vZGhjd2cNCg==

From neil.e.russell@gmail.com  Mon Dec  9 17:07:17 2013
Return-Path: <neil.e.russell@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7903C1AE0A3 for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 17:07:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lcajSBOylO7S for <dhcwg@ietfa.amsl.com>; Mon,  9 Dec 2013 17:07:16 -0800 (PST)
Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 4CD7C1AE0AE for <dhcwg@ietf.org>; Mon,  9 Dec 2013 17:07:15 -0800 (PST)
Received: by mail-qa0-f42.google.com with SMTP id k4so3223147qaq.15 for <dhcwg@ietf.org>; Mon, 09 Dec 2013 17:07:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version; bh=cfQ6fDdq9m+7dV8yfo4XC0BcK4jOjNdfBId+4FudDWc=; b=wKnvPOQJrE6ISFm/A3iMkIOR6Cvxbsx0I2K1YW+690LAbEgqAz3+RHiLRgj+iUJrcy sDlJScS+d7f2RV//F12AxO0SZ6CA8Dg6EFP45h9BMHnB4YsJ5MhEAnM8or5rhS1sdpQE E47im6AfFD9O1RQp/gRurTbyEriaXlpRZrushfbieRGyi6C8tHOGr537gdGMoZzx8bDT 3+zV+MBWoUJECFcoqQ1WCRF4NR5Xpx7+8arpoL8kyKkMY9okHLRe4Mib054Fo9H6UmEI 7q8ivtaNyS5Bh4uzwrGZ12F4Bl0vXWNS3rCt1EQj4avY0hhEANntAfxp046xI8qiVDVz TvOw==
X-Received: by 10.224.24.131 with SMTP id v3mr39863625qab.48.1386637630156; Mon, 09 Dec 2013 17:07:10 -0800 (PST)
Received: from neilsmacbookpro.home (pool-173-48-248-82.bstnma.fios.verizon.net. [173.48.248.82]) by mx.google.com with ESMTPSA id u17sm35673729qeb.4.2013.12.09.17.07.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Dec 2013 17:07:09 -0800 (PST)
From: Neil Russell <neil.e.russell@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Mon, 9 Dec 2013 20:07:18 -0500
Message-Id: <2A006079-131C-4F61-8F42-7E7CFFBF0FF6@gmail.com>
To: dhcwg@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
X-Mailer: Apple Mail (2.1822)
X-Mailman-Approved-At: Tue, 10 Dec 2013 04:56:05 -0800
Cc: Bernie Volz <volz@cisco.com>, Kim Kinnear <kkinnear@cisco.com>
Subject: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 10 Dec 2013 12:45:46 -0000

Hi,

I support the adoption of this draft.

--N

neil.e.russell@gmail.com



From Mathias.Samuelson@nominum.com  Tue Dec 10 13:57:03 2013
Return-Path: <Mathias.Samuelson@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDBC01AE08B for <dhcwg@ietfa.amsl.com>; Tue, 10 Dec 2013 13:57:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qMlGx5Z8dwM4 for <dhcwg@ietfa.amsl.com>; Tue, 10 Dec 2013 13:57:01 -0800 (PST)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id A07381AE04B for <dhcwg@ietf.org>; Tue, 10 Dec 2013 13:57:01 -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 DSNKUqeOKOupDxl0JwOgRi8UqPpuCx7SDqyO@postini.com; Tue, 10 Dec 2013 13:56:56 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 0138C1B82E1 for <dhcwg@ietf.org>; Tue, 10 Dec 2013 13:56:56 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id DBF90190043; Tue, 10 Dec 2013 13:56:55 -0800 (PST)
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.03.0158.001; Tue, 10 Dec 2013 13:56:56 -0800
From: Mathias Samuelson <Mathias.Samuelson@nominum.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Thread-Topic: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
Thread-Index: Ac7xD0TQ86CV+plkQwGdrBXmDcXNywFJobKA
Date: Tue, 10 Dec 2013 21:56:55 +0000
Message-ID: <84B906A2-32FF-4597-ADBB-7B100D759530@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADD09A3@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADD09A3@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B3E24B77882CC74790AE478365A08609@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Kim Kinnear \(kkinnear\)" <kkinnear@cisco.com>
Subject: Re: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 10 Dec 2013 21:57:04 -0000

Hi,

I definitely support adopting this as a WG work item.

Thanks
Mathias

On Dec 4, 2013, at 8:46 AM, Bernie Volz (volz) <volz@cisco.com> wrote:

> Hi all:
>=20
> This is a WG Call for Adoption for http://tools.ietf.org/html/draft-kinne=
ar-dhc-dhcpv4-active-leasequery-02. This call is being initiated to determi=
ne whether there is WG consensus to adopt this work as DHC WG item. Please =
state whether or not you're in favor of the adoption by replying to this ma=
il. If you are not in favor, please also state your objections in your resp=
onse. This adoption call will complete on December 18, 2013.
>=20
> This call is being initiated because during the call for adoption for dra=
ft-raghuvanshi-dhc-dhcpv6-active-leasequery-00, which was just adopted, sev=
eral people asked about the related DHCPv4 work. Kim republished the DHCPv4=
 draft (with minor updates) as it had expired a while ago. So, we are seeki=
ng input as to whether the WG should now also work on the DHCPv4 version of=
 active leasequery, given that the DHCPv6 version was adopted.
>=20
> Regards,
> Tomek & Bernie
>=20
> -----Original Message-----
> From: Kim Kinnear (kkinnear)=20
> Sent: Wednesday, December 04, 2013 11:25 AM
> To: dhcwg@ietf.org
> Cc: Kim Kinnear (kkinnear); Bernie Volz (volz); Tomek Mrugalski
> Subject: New Version Notification for draft-kinnear-dhc-dhcpv4-active-lea=
sequery-02.txt
>=20
>=20
> Folks,
>=20
> During the adoption discussion about DHCPv6 Active Leasequery there was s=
ome discussion about having a corresponding DHCPv4 Active Leasequery capabi=
lity.  If there is sufficient interest in a DHCPv4 Active Leasequery capabi=
lity to parallel the DHCPv6 capability that was adopted as a DHC WG work it=
em recently, then we can decide whether or not we want to have two drafts m=
oving toward two RFC's, or combine them into one draft.
>=20
> But the first question is whether or not there is sufficient interest in =
having a DHCPv4 Active Leasequery capability at all!
>=20
> In order to help decide this question, I have updated the existing
> DHCPv4 Active Leasequery draft from a couple of years ago, and resubmitte=
d it as an individual submission -- as recommended by Bernie and Tomek.
>=20
> Below you can find the information on how to find this new draft.
>=20
> Regards -- Kim
>=20
>=20
> Begin forwarded message:
>=20
>> From: <internet-drafts@ietf.org>
>> Subject: New Version Notification for=20
>> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
>> Date: December 4, 2013 10:01:03 AM EST
>> To: Bernie Volz <volz@cisco.com>, Mark Stapp <mjs@cisco.com>, Kim=20
>> Kinnear <kkinnear@cisco.com>, Neil Russell <neil.e.russell@gmail.com>
>>=20
>>=20
>> A new version of I-D,=20
>> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
>> has been successfully submitted by Kim Kinnear and posted to the IETF=20
>> repository.
>>=20
>> Filename:	 draft-kinnear-dhc-dhcpv4-active-leasequery
>> Revision:	 02
>> Title:		 Active DHCPv4 Lease Query
>> Creation date:	 2013-12-04
>> Group:		 Individual Submission
>> Number of pages: 22
>> URL:             http://www.ietf.org/internet-drafts/draft-kinnear-dhc-d=
hcpv4-active-leasequery-02.txt
>> Status:          http://datatracker.ietf.org/doc/draft-kinnear-dhc-dhcpv=
4-active-leasequery
>> Htmlized:        http://tools.ietf.org/html/draft-kinnear-dhc-dhcpv4-act=
ive-leasequery-02
>> Diff:            http://www.ietf.org/rfcdiff?url2=3Ddraft-kinnear-dhc-dh=
cpv4-active-leasequery-02
>>=20
>> Abstract:
>>  The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has been
>>  extended with a Leasequery capability that allows a client to request
>>  information about DHCPv4 bindings.  That mechanism is limited to
>>  queries for individual bindings.  In some situations individual
>>  binding queries may not be efficient, or even possible.  In addition,
>>  continuous update of an external client with Leasequery data is
>>  sometimes desired. This document expands on the DHCPv4 Leasequery
>>  protocol, and allows for active transfer of near real-time DHCPv4
>>  address binding information data via TCP.
>>=20
>>=20
>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of=20
>> submission until the htmlized version and diff are available at tools.ie=
tf.org.
>>=20
>> The IETF Secretariat
>>=20
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

Mathias Samuelson | Sr. Product Manager
mobile: +1.650.491.4193 | office: +1.650.381.6225
Nominum | www.nominum.com | mathias.samuelson@nominum.com


From gnocuil@gmail.com  Wed Dec 11 03:49:42 2013
Return-Path: <gnocuil@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8ADB1AC7EE for <dhcwg@ietfa.amsl.com>; Wed, 11 Dec 2013 03:49:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YJW48gOCTkLy for <dhcwg@ietfa.amsl.com>; Wed, 11 Dec 2013 03:49:41 -0800 (PST)
Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 20F251AC4AB for <dhcwg@ietf.org>; Wed, 11 Dec 2013 03:49:41 -0800 (PST)
Received: by mail-qc0-f170.google.com with SMTP id x13so5055800qcv.15 for <dhcwg@ietf.org>; Wed, 11 Dec 2013 03:49:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=qvqMCgQ5CFTqFFcaDS2VI01SIJUENaVufLTCliDFmlQ=; b=LiKmStBk91dFW7U/kSvrNknCdE42JVD+Y9IlhCdkLBjgh8BS+/rWZzwJszM+0Ydsqe eSeue7VrwKxJKDCMqjDF3kfJsspIUcmgPFZuvJg1gFh8nYmkLfOSRN5C1qZtnVy5jyfB oGtYvnnLXWxZC1KpUgZcmb0yPjg39NPrkASa4eNUI9Tq2ILH1yZIdg+Jxo6mFIXjTgrU /7PHqenDYCYHla+MlirLgFIM0gTeGdd8xxhjCA2/yjnBWJl8NrZMk+xX2tSwRslPBBNM pLttUIvLs4IT11weGDfwzg1zfUt0KgQvItVC27desR2K83ZaHO0Dg6tbnSIApIUt5mkO gFiA==
X-Received: by 10.49.36.161 with SMTP id r1mr1865786qej.4.1386762575433; Wed, 11 Dec 2013 03:49:35 -0800 (PST)
MIME-Version: 1.0
Received: by 10.96.161.103 with HTTP; Wed, 11 Dec 2013 03:49:15 -0800 (PST)
In-Reply-To: <52A1F8A8.3020200@viagenie.ca>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <52A1F8A8.3020200@viagenie.ca>
From: Cong Liu <gnocuil@gmail.com>
Date: Wed, 11 Dec 2013 19:49:15 +0800
Message-ID: <CAF+sHxH0c9miyc5piK8f9SCjd8rn34Y6p1-73Mrox5QKQDSW3Q@mail.gmail.com>
To: Simon Perreault <simon.perreault@viagenie.ca>
Content-Type: multipart/alternative; boundary=047d7b671d82b2704c04ed40d283
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Dec 2013 11:49:43 -0000

--047d7b671d82b2704c04ed40d283
Content-Type: text/plain; charset=ISO-8859-1

Hi Simon,

2013/12/7 Simon Perreault <simon.perreault@viagenie.ca>

> The major comments are:
>
> 1. Section "4. Architecture Overview" ends before explaining a crucial
> point: what does the client do with the IPv4 configuration it has received?
> For example, when it receives an IPv4 address, does it assign it to an
> interface? Which one? We need a general idea of how this works before this
> section is over.
>
> (Now that I have read the full draft, I realize that this is not discussed
> at all. If this is out of scope, then that means this RFC is not readily
> usable without another RFC describing how to use it in one particular
> context. That could be fine if that's the intent, but then that should be
> stated explicitly in this RFC.)
>

When client receives an IPv4 address, it will assign it because it's
DHCPv4. The difference is to which interface the IPv4 address is assigned.
It's described in -00 version of this draft: "The IPv4 address allocated
from the server MAY be assigned to a
different interface from the IPv6 interface requesting the information."
Maybe it should be added back to cover this issue.

Best Regards,
Cong

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

<div dir=3D"ltr">Hi Simon,<div class=3D"gmail_extra"><br><div class=3D"gmai=
l_quote">2013/12/7 Simon Perreault <span dir=3D"ltr">&lt;<a href=3D"mailto:=
simon.perreault@viagenie.ca" target=3D"_blank">simon.perreault@viagenie.ca<=
/a>&gt;</span><br>


<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">The major comments are:<br>
<br>
1. Section &quot;4. Architecture Overview&quot; ends before explaining a cr=
ucial point: what does the client do with the IPv4 configuration it has rec=
eived? For example, when it receives an IPv4 address, does it assign it to =
an interface? Which one? We need a general idea of how this works before th=
is section is over.<br>



<br>
(Now that I have read the full draft, I realize that this is not discussed =
at all. If this is out of scope, then that means this RFC is not readily us=
able without another RFC describing how to use it in one particular context=
. That could be fine if that&#39;s the intent, but then that should be stat=
ed explicitly in this RFC.)<br>


</blockquote><div><br></div><div>When client receives an IPv4 address, it w=
ill assign it because it&#39;s DHCPv4. The difference is to which interface=
 the IPv4 address is assigned.</div><div>It&#39;s described in -00 version =
of this draft: &quot;The IPv4 address allocated from the server MAY be assi=
gned to a<br>

</div><div>different interface from the IPv6 interface requesting the infor=
mation.&quot; Maybe it should be added back to cover this issue.</div><div>=
<br></div><div>Best Regards,</div><div>Cong</div></div></div></div>

--047d7b671d82b2704c04ed40d283--

From sunqi.csnet.thu@gmail.com  Wed Dec 11 07:23:17 2013
Return-Path: <sunqi.csnet.thu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6101C1ADFBF for <dhcwg@ietfa.amsl.com>; Wed, 11 Dec 2013 07:23:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IMH3j8DrdgNN for <dhcwg@ietfa.amsl.com>; Wed, 11 Dec 2013 07:23:15 -0800 (PST)
Received: from mail-pb0-x22d.google.com (mail-pb0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 72C161ADFB5 for <dhcwg@ietf.org>; Wed, 11 Dec 2013 07:23:15 -0800 (PST)
Received: by mail-pb0-f45.google.com with SMTP id rp16so10153266pbb.32 for <dhcwg@ietf.org>; Wed, 11 Dec 2013 07:23:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=eDNwW5aroaw9lnP79ikLlJ9G/ESc5ViELEvVvmNGbak=; b=A7K+EBj3wph8TIa8S8V+UO+TJx37ybjcYzfVJiaUGCpsXjpS/9uhYCk3yyKi4j1AQ/ OvE6yFO+w6dBmLEZiNu2c/md+fqD5rkUCDkNLKpV/b0hJ7pDcH9q5CM7ZdHwaBd1RvTR P94AnbpL7KGEeVu42/t9wCiQesvXY4Y9j8C43ztf085lfXLhISA3GogB/d1NyQGyoC2E ALv9osBMXc0ypSUYA/XTq7JJS558kH1yTvmaw1QqRKDg99Q05CyPasrz677Wosgmsw6D S+hh7gZF6H+C7ULxVpREBbzBeTMgZu2vb+IS/ah/1M/ZyIRbqkoqiyaxYzgBj2pVhQDP EiUg==
X-Received: by 10.67.3.34 with SMTP id bt2mr2277824pad.3.1386775388802; Wed, 11 Dec 2013 07:23:08 -0800 (PST)
Received: from [192.168.1.110] ([59.64.255.197]) by mx.google.com with ESMTPSA id by1sm32918331pbd.25.2013.12.11.07.23.04 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 11 Dec 2013 07:23:08 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-43-446282126
From: Qi Sun <sunqi.csnet.thu@gmail.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADD590C@xmb-rcd-x04.cisco.com>
Date: Wed, 11 Dec 2013 23:22:55 +0800
Message-Id: <CE4E8958-57AA-4D87-AA80-F2B12FF1A698@gmail.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADD590C@xmb-rcd-x04.cisco.com>
To: Bernie Volz (volz) <volz@cisco.com>
X-Mailer: Apple Mail (2.1085)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org" <draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Dec 2013 15:23:17 -0000

--Apple-Mail-43-446282126
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


Hi Bernie,=20

Many thanks for your thorough review! We will address the issues you =
mentioned in the next version.

About item 2:

> 2.       I think we should rename the messages to be BOOTP, not BOOT. =
BOOTPREQUESTV6 and BOOTPREPLYV6 (and Bootp-request-v6, Bootp-reply-v6). =
(I also wonder whether we really need the v6, but it may help in =
clarifying this from standard BOOTP packets, so OK to leave it.)

I check the the RFC 951 (Bootstrap Protocol) that defines BOOTP =
messages. The two message types defined is BOOTREQUEST and BOOTREPLY. In =
order to be consistent with that naming system, we chose BOOTREQUESTV6 =
and BOOTREPLYV6 as the new message names in DHCPv4 over DHCPv6.=20

Would it be OK if we keep the current message names?

Best Regards,
Qi

>=20
> =20
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz =
(volz)
> Sent: Sunday, November 24, 2013 5:03 PM
> To: dhcwg@ietf.org
> Subject: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - =
Respond by Dec 9, 2013
> =20
> Folks, the authors of draft-ietf-dhc-dhcpv4-over-dhcpv6-03 =
(http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-03.txt) =
believe it is ready for working group last call. Please review this =
draft and indicate whether or not you feel it is ready to be published. =
Your input is important! Please respond by Dec 9th, 2013.
> =20
> At the time of this writing, there is no IPR reported against this =
draft.
> =20
> Bernie will be the document shepherd.
> =20
> Thanks,
> =20
> -          Tomek & Bernie
> =20


--Apple-Mail-43-446282126
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><base href=3D"x-msg://356/"></head><body style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Heiti SC'; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: 'Heiti SC'; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Heiti SC'; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Heiti SC'; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div>Hi =
Bernie,&nbsp;</div><div><br></div><div>Many thanks for your thorough =
review! We will address the issues you mentioned in the next =
version.</div><div><br></div><div>About item =
2:</div><div><br></div></div></span></div></span></div></span></span></div=
><div><blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; font-family: 'Heiti SC'; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0.5in; margin-bottom: 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; text-indent: -0.25in; =
"><span style=3D"color: rgb(31, 73, 125); "><span>2.<span style=3D"font: =
normal normal normal 7pt/normal 'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span></span><span =
style=3D"color: rgb(31, 73, 125); ">I think we should rename the =
messages to be BOOTP, not BOOT. BOOTPREQUESTV6 and BOOTPREPLYV6 (and =
Bootp-request-v6, Bootp-reply-v6). (I also wonder whether we really need =
the v6, but it may help in clarifying this from standard BOOTP packets, =
so OK to leave =
it.)</span></div></div></div></span></blockquote><div><br></div><div>I =
check the the RFC 951 (Bootstrap Protocol) that defines BOOTP messages. =
The two message types defined is BOOTREQUEST and BOOTREPLY. In order to =
be consistent with that naming system, we chose BOOTREQUESTV6 and =
BOOTREPLYV6 as the new message names in DHCPv4 over =
DHCPv6.&nbsp;</div><div><br></div><div>Would it be OK if we keep the =
current message names?</div><div><br></div><div>Best =
Regards,</div><div>Qi</div><div><br></div><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: 'Heiti SC'; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><font class=3D"Apple-style-span"=
 color=3D"#1f497d"><br></font></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><span style=3D"color: rgb(31, =
73, 125); "><o:p>&nbsp;</o:p></span></div><div><div =
style=3D"border-right-style: none; border-bottom-style: none; =
border-left-style: none; border-width: initial; border-color: initial; =
border-top-style: solid; border-top-color: rgb(181, 196, 223); =
border-top-width: 1pt; padding-top: 3pt; padding-right: 0in; =
padding-bottom: 0in; padding-left: 0in; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><b><span style=3D"font-size: =
10pt; font-family: Tahoma, sans-serif; ">From:</span></b><span =
style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; "><span =
class=3D"Apple-converted-space">&nbsp;</span>dhcwg =
[mailto:dhcwg-bounces@ietf.org]<span =
class=3D"Apple-converted-space">&nbsp;</span><b>On Behalf Of<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Bernie Volz =
(volz)<br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Sunday, November 24, 2013 =
5:03 PM<br><b>To:</b><span class=3D"Apple-converted-space">&nbsp;</span><a=
 href=3D"mailto:dhcwg@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">dhcwg@ietf.org</a><br><b>Subject:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>[dhcwg] WGLC for =
draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, =
2013<o:p></o:p></span></div></div></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; ">Folks, the authors of draft-ietf-dhc-dhcpv4-over-dhcpv6-03 =
(<a =
href=3D"http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-03.tx=
t" style=3D"color: blue; text-decoration: underline; =
">http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-03.txt</a>)=
 believe it is ready for working group last call. Please review this =
draft and indicate whether or not you feel it is ready to be published. =
Your input is important! Please respond by Dec 9<sup>th</sup>, =
2013.<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; ">At the time of this =
writing, there is no IPR reported against this =
draft.<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif; ">Bernie will be the =
document shepherd.<o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; ">Thanks,<o:p></o:p></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0.5in; =
margin-bottom: 0.0001pt; font-size: 11pt; font-family: Calibri, =
sans-serif; text-indent: -0.25in; "><span>-<span style=3D"font: normal =
normal normal 7pt/normal 'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span>Tomek &amp; =
Bernie<o:p></o:p></div><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></div></div></div></span></blockquote></div><br></body>=
</html>=

--Apple-Mail-43-446282126--

From simon.perreault@viagenie.ca  Wed Dec 11 08:03:13 2013
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B1BC1AE017 for <dhcwg@ietfa.amsl.com>; Wed, 11 Dec 2013 08:03:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TAD1xq35Rvq1 for <dhcwg@ietfa.amsl.com>; Wed, 11 Dec 2013 08:03:11 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id C13E41AE013 for <dhcwg@ietf.org>; Wed, 11 Dec 2013 08:03:11 -0800 (PST)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:b146:2fa2:7507:a763]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 1433B403CA; Wed, 11 Dec 2013 11:03:06 -0500 (EST)
Message-ID: <52A88CB9.5010806@viagenie.ca>
Date: Wed, 11 Dec 2013 11:03:05 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Cong Liu <gnocuil@gmail.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <52A1F8A8.3020200@viagenie.ca> <CAF+sHxH0c9miyc5piK8f9SCjd8rn34Y6p1-73Mrox5QKQDSW3Q@mail.gmail.com>
In-Reply-To: <CAF+sHxH0c9miyc5piK8f9SCjd8rn34Y6p1-73Mrox5QKQDSW3Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Dec 2013 16:03:13 -0000

Le 2013-12-11 06:49, Cong Liu a écrit :
>     1. Section "4. Architecture Overview" ends before explaining a
>     crucial point: what does the client do with the IPv4 configuration
>     it has received? For example, when it receives an IPv4 address, does
>     it assign it to an interface? Which one? We need a general idea of
>     how this works before this section is over.
>
>     (Now that I have read the full draft, I realize that this is not
>     discussed at all. If this is out of scope, then that means this RFC
>     is not readily usable without another RFC describing how to use it
>     in one particular context. That could be fine if that's the intent,
>     but then that should be stated explicitly in this RFC.)
>
>
> When client receives an IPv4 address, it will assign it because it's
> DHCPv4. The difference is to which interface the IPv4 address is assigned.
> It's described in -00 version of this draft: "The IPv4 address allocated
> from the server MAY be assigned to a
> different interface from the IPv6 interface requesting the information."
> Maybe it should be added back to cover this issue.

I would expect much more substantial informative text to be added to the 
draft. Some things can be left out of scope for this draft, but at least 
enumerating and describing what those things are is necessary.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From volz@cisco.com  Wed Dec 11 08:19:07 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E372F1AE06F for <dhcwg@ietfa.amsl.com>; Wed, 11 Dec 2013 08:19:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.501
X-Spam-Level: 
X-Spam-Status: No, score=-9.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lcKRwnXSxFCx for <dhcwg@ietfa.amsl.com>; Wed, 11 Dec 2013 08:19:04 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by ietfa.amsl.com (Postfix) with ESMTP id 9AB871AE026 for <dhcwg@ietf.org>; Wed, 11 Dec 2013 08:19:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18139; q=dns/txt; s=iport; t=1386778739; x=1387988339; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=hqoHXY6+Sm0Uv2H35VbeIXC5fPYGr9sffqJFpOvMbs4=; b=j47zV7N4BYT/81xYVDqEV2H21jy1vnqUdek1ZV2pL007KBU1zwP19Eax RIbz9WBjXyANn2E95mJ+aqNIys2Z7eZhBXO4lEn1bDsZuwRWKAY54jAFy mRHsAGzla3i9nl/KE+msdovHaP1RdJR4JfqBJZzQ1+e04nshd2hvovqHg M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap4GADiPqFKtJXG9/2dsb2JhbABZgkNEOFOwQohXgR0WdIIlAQEBBC1MEAIBCBEEAQELHQchERQJCAIEDgUIh2gDDw27FQ2GZxeMdYFiMQYBBoJMT4ETBJQxgXiDG4sqhTmDKYIq
X-IronPort-AV: E=Sophos;i="4.93,872,1378857600"; d="scan'208,217";a="6031549"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by alln-iport-5.cisco.com with ESMTP; 11 Dec 2013 16:18:58 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id rBBGIwkg029596 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 11 Dec 2013 16:18:58 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0123.003; Wed, 11 Dec 2013 10:18:57 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Qi Sun <sunqi.csnet.thu@gmail.com>
Thread-Topic: WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
Thread-Index: AQHO9oTumc0qzwABOkWLVa4A0SsWkJpPKoOw
Date: Wed, 11 Dec 2013 16:18:58 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1ADDF49A@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADD590C@xmb-rcd-x04.cisco.com> <CE4E8958-57AA-4D87-AA80-F2B12FF1A698@gmail.com>
In-Reply-To: <CE4E8958-57AA-4D87-AA80-F2B12FF1A698@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.65.131]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1ADDF49Axmbrcdx04ciscoc_"
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org" <draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Dec 2013 16:19:08 -0000

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

Hi:

What's in a name anyway? (http://idioms.thefreedictionary.com/What's+in+a+n=
ame%3F)

My concern with BOOT is that people might confuse it with booting, not addr=
ess assignment. Even BOOTP may not be the best. (I think I may have suggest=
ed using the underlying v4 protocol name early on?)

If no one else has any view on this, leave it alone. I just wanted to raise=
 this issue to make sure the WG was OK with the message names.


-          Bernie

From: Qi Sun [mailto:sunqi.csnet.thu@gmail.com]
Sent: Wednesday, December 11, 2013 10:23 AM
To: Bernie Volz (volz)
Cc: dhcwg@ietf.org; draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org
Subject: Re: WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec=
 9, 2013


Hi Bernie,

Many thanks for your thorough review! We will address the issues you mentio=
ned in the next version.

About item 2:

2.       I think we should rename the messages to be BOOTP, not BOOT. BOOTP=
REQUESTV6 and BOOTPREPLYV6 (and Bootp-request-v6, Bootp-reply-v6). (I also =
wonder whether we really need the v6, but it may help in clarifying this fr=
om standard BOOTP packets, so OK to leave it.)

I check the the RFC 951 (Bootstrap Protocol) that defines BOOTP messages. T=
he two message types defined is BOOTREQUEST and BOOTREPLY. In order to be c=
onsistent with that naming system, we chose BOOTREQUESTV6 and BOOTREPLYV6 a=
s the new message names in DHCPv4 over DHCPv6.

Would it be OK if we keep the current message names?

Best Regards,
Qi



From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Sunday, November 24, 2013 5:03 PM
To: dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Subject: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by=
 Dec 9, 2013

Folks, the authors of draft-ietf-dhc-dhcpv4-over-dhcpv6-03 (http://tools.ie=
tf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-03.txt) believe it is ready f=
or working group last call. Please review this draft and indicate whether o=
r not you feel it is ready to be published. Your input is important! Please=
 respond by Dec 9th, 2013.

At the time of this writing, there is no IPR reported against this draft.

Bernie will be the document shepherd.

Thanks,

-          Tomek & Bernie



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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<base href=3D"x-msg://356/"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:"Heiti SC";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
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;}
/* List Definitions */
@list l0
	{mso-list-id:222907644;
	mso-list-type:hybrid;
	mso-list-template-ids:-71033262 830497500 67698691 67698693 67698689 67698=
691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:5;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">What&#8217;s in a name an=
yway? (</span><a href=3D"http://idioms.thefreedictionary.com/What's&#43;in&=
#43;a&#43;name%3F">http://idioms.thefreedictionary.com/What's&#43;in&#43;a&=
#43;name%3F</a><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1F497D">)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">My concern with BOOT is t=
hat people might confuse it with booting, not address assignment. Even BOOT=
P may not be the best. (I think I may have suggested using
 the underlying v4 protocol name early on?)<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">If no one else has any vi=
ew on this, leave it alone. I just wanted to raise this issue to make sure =
the WG was OK with the message names.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><span style=3D"mso-=
list:Ignore">-<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Bernie<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Qi Sun [=
mailto:sunqi.csnet.thu@gmail.com]
<br>
<b>Sent:</b> Wednesday, December 11, 2013 10:23 AM<br>
<b>To:</b> Bernie Volz (volz)<br>
<b>Cc:</b> dhcwg@ietf.org; draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org=
<br>
<b>Subject:</b> Re: WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond=
 by Dec 9, 2013<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;He=
iti SC&quot;,&quot;serif&quot;;color:black">Hi Bernie,&nbsp;<o:p></o:p></sp=
an></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;He=
iti SC&quot;,&quot;serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;He=
iti SC&quot;,&quot;serif&quot;;color:black">Many thanks for your thorough r=
eview! We will address the issues you mentioned in the next version.<o:p></=
o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;He=
iti SC&quot;,&quot;serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;He=
iti SC&quot;,&quot;serif&quot;;color:black">About item 2:<o:p></o:p></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;He=
iti SC&quot;,&quot;serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</div>
</div>
</div>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div style=3D"margin-left:.5in">
<p class=3D"MsoNormal" style=3D"text-indent:-.25in"><span style=3D"font-siz=
e:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F49=
7D">2.</span><span style=3D"font-size:7.0pt;color:#1F497D">&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;<span class=3D"apple-converted-space">&nbsp;</span></sp=
an><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">I
 think we should rename the messages to be BOOTP, not BOOT. BOOTPREQUESTV6 =
and BOOTPREPLYV6 (and Bootp-request-v6, Bootp-reply-v6). (I also wonder whe=
ther we really need the v6, but it may help in clarifying this from standar=
d BOOTP packets, so OK to leave
 it.)</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;"><o:p></o:p></span></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I check the the RFC 951 (Bootstrap Protocol) that de=
fines BOOTP messages. The two message types defined is BOOTREQUEST and BOOT=
REPLY. In order to be consistent with that naming system, we chose BOOTREQU=
ESTV6 and BOOTREPLYV6 as the new message
 names in DHCPv4 over DHCPv6.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Would it be OK if we keep the current message names?=
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Qi<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=
=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;=
"><o:p></o:p></span></p>
</div>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in;border-width:initial;border-color:initial">
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span class=3D"apple-=
converted-space"><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&q=
uot;,&quot;sans-serif&quot;">&nbsp;</span></span><span style=3D"font-size:1=
0.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">dhcwg
 [<a href=3D"mailto:dhcwg-bounces@ietf.org">mailto:dhcwg-bounces@ietf.org</=
a>]<span class=3D"apple-converted-space">&nbsp;</span><b>On Behalf Of<span =
class=3D"apple-converted-space">&nbsp;</span></b>Bernie Volz (volz)<br>
<b>Sent:</b><span class=3D"apple-converted-space">&nbsp;</span>Sunday, Nove=
mber 24, 2013 5:03 PM<br>
<b>To:</b><span class=3D"apple-converted-space">&nbsp;</span><a href=3D"mai=
lto:dhcwg@ietf.org">dhcwg@ietf.org</a><br>
<b>Subject:</b><span class=3D"apple-converted-space">&nbsp;</span>[dhcwg] W=
GLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013</span=
><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;"><o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Folks, the authors of draft-ietf-dhc-dh=
cpv4-over-dhcpv6-03 (<a href=3D"http://tools.ietf.org/html/draft-ietf-dhc-d=
hcpv4-over-dhcpv6-03.txt">http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-=
over-dhcpv6-03.txt</a>)
 believe it is ready for working group last call. Please review this draft =
and indicate whether or not you feel it is ready to be published. Your inpu=
t is important! Please respond by Dec 9<sup>th</sup>, 2013.<o:p></o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">At the time of this writing, there is n=
o IPR reported against this draft.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Bernie will be the document shepherd.<o=
:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Thanks,<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div style=3D"margin-left:.5in">
<p class=3D"MsoNormal" style=3D"text-indent:-.25in"><span style=3D"font-siz=
e:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">-</span><s=
pan style=3D"font-size:7.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;<span class=3D"apple-converted-space">&nbsp;</span></span><span st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;">Tomek
 &amp; Bernie<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1ADDF49Axmbrcdx04ciscoc_--

From msiodelski@gmail.com  Wed Dec 11 11:39:38 2013
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E6601AE1D7 for <dhcwg@ietfa.amsl.com>; Wed, 11 Dec 2013 11:39:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k1HA44gSd8lT for <dhcwg@ietfa.amsl.com>; Wed, 11 Dec 2013 11:39:37 -0800 (PST)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 0307A1AE195 for <dhcwg@ietf.org>; Wed, 11 Dec 2013 11:39:36 -0800 (PST)
Received: by mail-ie0-f173.google.com with SMTP id to1so11805068ieb.32 for <dhcwg@ietf.org>; Wed, 11 Dec 2013 11:39:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Ywe+Ex1dDskBaY+rDzbVDkR3LRL6ajnK8aa0/7Y8iHk=; b=kz8gQvRGnPV+X3DG4ZuVFhPS6a6I1Y38umGU1K4174JghTRmamzdrtOaZL8pvujdsb Z5WnoF1qtXg8lEPSDAFDeijPlzJsCagDlRDnsenDDD17AM5lLUaQBxYikhZ/gMPXdnWV pbi5uBYAWqtiG8sKhp6Cp4V9OG/fZ6SPsgNPhQBiN9FlzB6Pe1MpKy6ow7u1i3NTRLr5 g077CjkQmJNQHkjEd/P+Yf7a7Tt56Cxc3ZW9pGPgc9XHTkrMeSxcUMJ/PBPti3XBf574 aH9IcdJ+2tE1VBhNJ+i4f212ePblqJmy68wzyKkxHYgdY4gKOesRG2bu/eRUKX+OuX+K l0Wg==
MIME-Version: 1.0
X-Received: by 10.43.8.66 with SMTP id or2mr2640705icb.19.1386790771290; Wed, 11 Dec 2013 11:39:31 -0800 (PST)
Received: by 10.50.32.33 with HTTP; Wed, 11 Dec 2013 11:39:31 -0800 (PST)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADD590C@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADD590C@xmb-rcd-x04.cisco.com>
Date: Wed, 11 Dec 2013 20:39:31 +0100
Message-ID: <CAFGoqUMbbH3h2ouf+9JphYoM2wTGK0tiRSSscPMuPB4Xq51XGg@mail.gmail.com>
From: Marcin Siodelski <msiodelski@gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org" <draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 11 Dec 2013 19:39:38 -0000

On Fri, Dec 6, 2013 at 4:05 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
>
> 9.       A general issue =85 I wonder whether we have a kind of catch-22.=
 As
> DHCP is interface specific, and the tunnel interface may not be able to
> =91come up=92 until after the address is assigned, what interface is this
> =91DHCPv4=92 (4o6) client associated with? Is it the v6 interface? Or a
> =91provisional=92 tunnel interface? Or, is this left up to the implementa=
tion to
> deal with (since in one sense it probably doesn=92t matter much =96 excep=
t of
> course if one was trying to bring up multiple tunnel interfaces over the
> same v6 interface; but that requires other special logic so may not be a
> concern).
>
>

I wonder if we have to associate the 4o6 client with any interface
before the tunnel configuration arrives. The draft mandates that
conforming implementation uses RFC4361 so there should be no problem
of lacking chaddr on the client side. I think we should also mention
that RFC6842 should be implemented on the server side so as it
respects a client identifier, not chaddr.
Before the client gets the tunnel configuration the tunnel interface
doesn't exist. The 4o6 client just generates the client identifier
(unique by IAID) for the tunnel to be established. Once the v4
configuration is complete, the tunnel is created and the client
associates the client identifier with this tunnel/interface.

Marcin

From Ted.Lemon@nominum.com  Wed Dec 11 20:20:23 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03FB81ADF7C for <dhcwg@ietfa.amsl.com>; Wed, 11 Dec 2013 20:20:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lz36Y3r_qLhj for <dhcwg@ietfa.amsl.com>; Wed, 11 Dec 2013 20:20:21 -0800 (PST)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id 5E1371ADF73 for <dhcwg@ietf.org>; Wed, 11 Dec 2013 20:20:21 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKUqk5fz+jQoFwLYevHaLXugnVd0MeJ5/D@postini.com; Wed, 11 Dec 2013 20:20:15 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 740131B82DC for <dhcwg@ietf.org>; Wed, 11 Dec 2013 20:20:15 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 498CC190043; Wed, 11 Dec 2013 20:20:15 -0800 (PST)
Received: from vpna-132.vpn.nominum.com (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 11 Dec 2013 20:20:15 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAFGoqUMbbH3h2ouf+9JphYoM2wTGK0tiRSSscPMuPB4Xq51XGg@mail.gmail.com>
Date: Wed, 11 Dec 2013 23:20:11 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <EFF87BCD-CD0E-46B5-B4B2-107DF49ABD1E@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADD590C@xmb-rcd-x04.cisco.com> <CAFGoqUMbbH3h2ouf+9JphYoM2wTGK0tiRSSscPMuPB4Xq51XGg@mail.gmail.com>
To: Marcin Siodelski <msiodelski@gmail.com>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>, "draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org" <draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 12 Dec 2013 04:20:23 -0000

On Dec 11, 2013, at 2:39 PM, Marcin Siodelski <msiodelski@gmail.com> =
wrote:
> Before the client gets the tunnel configuration the tunnel interface
> doesn't exist. The 4o6 client just generates the client identifier
> (unique by IAID) for the tunnel to be established. Once the v4
> configuration is complete, the tunnel is created and the client
> associates the client identifier with this tunnel/interface.

I think it's important to be aware that this function is for "getting an =
IPv4 configuration," not "configuring an interface."   The document =
should certainly say as much as it can about what to do with the =
configuration, but we're really documenting a mechanism here for getting =
a configuration from a DHCP server, not documenting specific use cases =
for that mechanism.   So e.g. the expectation is that if lw4over6 uses =
this mechanism, it will say what to do with the information gathered as =
a result.   If some future spec needs this mechanism, it will say =
something that might be quite different. It is un-possible that this =
mechanism might be used without some other spec referring to it.


From sunqi.csnet.thu@gmail.com  Thu Dec 12 04:40:04 2013
Return-Path: <sunqi.csnet.thu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA4581AE28A for <dhcwg@ietfa.amsl.com>; Thu, 12 Dec 2013 04:40:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fhXHAQXxqibG for <dhcwg@ietfa.amsl.com>; Thu, 12 Dec 2013 04:40:01 -0800 (PST)
Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 286BA1AE287 for <dhcwg@ietf.org>; Thu, 12 Dec 2013 04:40:01 -0800 (PST)
Received: by mail-pd0-f178.google.com with SMTP id y10so434625pdj.9 for <dhcwg@ietf.org>; Thu, 12 Dec 2013 04:39:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=TUc4unQ/7BdwSiZx75tMNLvoN2w/Fi0bCFmBLx9nYk0=; b=YZW3VvDob9eis2jGgoPOjA/0gXMXAmUbgIpjboCXTBgZ2EOJ8y6/l2KqG5jtZtSfXE tYMphwtUPsXn9Rn0ASllRjkYPuhGqqjbNQJQeRyZ9jCHujRrmPtbdDRG5g0MQJR1B7Wz XLrCKAYMqMEuS6XvnrhA+H9stuPWItbUZFw1B/3hBKxhKdN1Frx7uBvYS8Fz+v214nn4 iy32zL1Z3eXaDHfJYnjDe8UNVtZrp8CYsbJU06MOAa5DUj2oaN5sgfA78b4qjhTYMpdc LVsjPW+vfHxI/LV0IDetYsXmbCOF8gaJIkHLIvA4Gfdo2jXxw5y4396ghzg4Irj/IvTw pxJw==
X-Received: by 10.68.173.132 with SMTP id bk4mr1297997pbc.169.1386851995130; Thu, 12 Dec 2013 04:39:55 -0800 (PST)
Received: from [192.168.199.122] ([166.111.68.231]) by mx.google.com with ESMTPSA id qw8sm39939066pbb.27.2013.12.12.04.39.52 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 12 Dec 2013 04:39:54 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-66-522896407
From: Qi Sun <sunqi.csnet.thu@gmail.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADDF49A@xmb-rcd-x04.cisco.com>
Date: Thu, 12 Dec 2013 20:39:49 +0800
Message-Id: <F0A0E7AD-387E-4F9C-8200-4297E79BA566@gmail.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADD590C@xmb-rcd-x04.cisco.com> <CE4E8958-57AA-4D87-AA80-F2B12FF1A698@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1ADDF49A@xmb-rcd-x04.cisco.com>
To: Bernie Volz (volz) <volz@cisco.com>
X-Mailer: Apple Mail (2.1085)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org" <draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 12 Dec 2013 12:40:04 -0000

--Apple-Mail-66-522896407
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


Hi Bernie,

I'm OK with your suggestion (using the  BOOTPREQUESTV6 and =
BOOTPREPLYV6).

Thanks!
Qi=20


On 2013-12-12, at =E4=B8=8A=E5=8D=8812:18, Bernie Volz (volz) wrote:

> Hi:
> =20
> What=E2=80=99s in a name anyway? =
(http://idioms.thefreedictionary.com/What's+in+a+name%3F)
> =20
> My concern with BOOT is that people might confuse it with booting, not =
address assignment. Even BOOTP may not be the best. (I think I may have =
suggested using the underlying v4 protocol name early on?)
> =20
> If no one else has any view on this, leave it alone. I just wanted to =
raise this issue to make sure the WG was OK with the message names.
> =20
> -          Bernie
> =20
> From: Qi Sun [mailto:sunqi.csnet.thu@gmail.com]=20
> Sent: Wednesday, December 11, 2013 10:23 AM
> To: Bernie Volz (volz)
> Cc: dhcwg@ietf.org; draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org
> Subject: Re: WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond =
by Dec 9, 2013
> =20
> =20
> Hi Bernie,=20
> =20
> Many thanks for your thorough review! We will address the issues you =
mentioned in the next version.
> =20
> About item 2:
> =20
> 2.       I think we should rename the messages to be BOOTP, not BOOT. =
BOOTPREQUESTV6 and BOOTPREPLYV6 (and Bootp-request-v6, Bootp-reply-v6). =
(I also wonder whether we really need the v6, but it may help in =
clarifying this from standard BOOTP packets, so OK to leave it.)
> =20
> I check the the RFC 951 (Bootstrap Protocol) that defines BOOTP =
messages. The two message types defined is BOOTREQUEST and BOOTREPLY. In =
order to be consistent with that naming system, we chose BOOTREQUESTV6 =
and BOOTREPLYV6 as the new message names in DHCPv4 over DHCPv6.=20
> =20
> Would it be OK if we keep the current message names?
> =20
> Best Regards,
> Qi
> =20
> =20
> =20
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz =
(volz)
> Sent: Sunday, November 24, 2013 5:03 PM
> To: dhcwg@ietf.org
> Subject: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - =
Respond by Dec 9, 2013
> =20
> Folks, the authors of draft-ietf-dhc-dhcpv4-over-dhcpv6-03 =
(http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-03.txt) =
believe it is ready for working group last call. Please review this =
draft and indicate whether or not you feel it is ready to be published. =
Your input is important! Please respond by Dec 9th, 2013.
> =20
> At the time of this writing, there is no IPR reported against this =
draft.
> =20
> Bernie will be the document shepherd.
> =20
> Thanks,
> =20
> -          Tomek & Bernie
> =20
> =20


--Apple-Mail-66-522896407
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><base href=3D"x-msg://356/"></head><body style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Heiti SC'; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: 'Heiti SC'; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Heiti SC'; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Heiti SC'; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div>Hi =
Bernie,</div><div><br></div><div>I'm OK with your suggestion (using the =
&nbsp;BOOTPREQUESTV6 and =
BOOTPREPLYV6).</div><div><br></div><div>Thanks!</div><div>Qi&nbsp;</div><b=
r></div></span></div></span></div></span></span>
</div>
<br><div><div>On 2013-12-12, at =E4=B8=8A=E5=8D=8812:18, Bernie Volz =
(volz) wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: 'Heiti SC'; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
">Hi:<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
">What=E2=80=99s in a name anyway? (</span><a =
href=3D"http://idioms.thefreedictionary.com/What's+in+a+name%3F" =
style=3D"color: blue; text-decoration: underline; =
">http://idioms.thefreedictionary.com/What's+in+a+name%3F</a><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">)<o:p></o:p></span></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); "><o:p>&nbsp;</o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); ">My concern with BOOT is that =
people might confuse it with booting, not address assignment. Even BOOTP =
may not be the best. (I think I may have suggested using the underlying =
v4 protocol name early on?)<o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); ">If no =
one else has any view on this, leave it alone. I just wanted to raise =
this issue to make sure the WG was OK with the message =
names.<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0.5in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; text-indent: =
-0.25in; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); "><span>-<span style=3D"font: =
normal normal normal 7pt/normal 'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span></span><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">Bernie<o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; color: rgb(31, 73, 125); =
"><o:p>&nbsp;</o:p></span></div><div><div style=3D"border-right-style: =
none; border-bottom-style: none; border-left-style: none; border-width: =
initial; border-color: initial; border-top-style: solid; =
border-top-color: rgb(181, 196, 223); border-top-width: 1pt; =
padding-top: 3pt; padding-right: 0in; padding-bottom: 0in; padding-left: =
0in; "><div style=3D"margin-top: 0in; margin-right: 0in; margin-left: =
0in; margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><b><span style=3D"font-size: 10pt; font-family: Tahoma, =
sans-serif; ">From:</span></b><span style=3D"font-size: 10pt; =
font-family: Tahoma, sans-serif; "><span =
class=3D"Apple-converted-space">&nbsp;</span>Qi Sun =
[mailto:sunqi.csnet.thu@gmail.com]<span =
class=3D"Apple-converted-space">&nbsp;</span><br><b>Sent:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Wednesday, December 11, =
2013 10:23 AM<br><b>To:</b><span =
class=3D"Apple-converted-space">&nbsp;</span>Bernie Volz =
(volz)<br><b>Cc:</b><span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:dhcwg@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">dhcwg@ietf.org</a>;<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org" =
style=3D"color: blue; text-decoration: underline; =
">draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org</a><br><b>Subject:</b><=
span class=3D"Apple-converted-space">&nbsp;</span>Re: WGLC for =
draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, =
2013<o:p></o:p></span></div></div></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: 12pt; =
font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div><div><div><div><div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 13.5pt; font-family: 'Heiti =
SC', serif; color: black; ">Hi =
Bernie,&nbsp;<o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 13.5pt; font-family: 'Heiti SC', serif; color: =
black; "><o:p>&nbsp;</o:p></span></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 13.5pt; font-family: 'Heiti =
SC', serif; color: black; ">Many thanks for your thorough review! We =
will address the issues you mentioned in the next =
version.<o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 13.5pt; font-family: 'Heiti SC', serif; color: =
black; "><o:p>&nbsp;</o:p></span></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 13.5pt; font-family: 'Heiti =
SC', serif; color: black; ">About item =
2:<o:p></o:p></span></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
13.5pt; font-family: 'Heiti SC', serif; color: black; =
"><o:p>&nbsp;</o:p></span></div></div></div></div></div></div><div><blockq=
uote style=3D"margin-top: 5pt; margin-bottom: 5pt; "><div><div =
style=3D"margin-left: 0.5in; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; text-indent: -0.25in; =
"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
color: rgb(31, 73, 125); ">2.</span><span style=3D"font-size: 7pt; =
color: rgb(31, 73, 125); ">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span =
class=3D"apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">I think we should rename the messages to be BOOTP, =
not BOOT. BOOTPREQUESTV6 and BOOTPREPLYV6 (and Bootp-request-v6, =
Bootp-reply-v6). (I also wonder whether we really need the v6, but it =
may help in clarifying this from standard BOOTP packets, so OK to leave =
it.)</span><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; "><o:p></o:p></span></div></div></div></blockquote><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><o:p>&nbsp;</o:p></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; ">I check the the RFC 951 (Bootstrap Protocol) that =
defines BOOTP messages. The two message types defined is BOOTREQUEST and =
BOOTREPLY. In order to be consistent with that naming system, we chose =
BOOTREQUESTV6 and BOOTREPLYV6 as the new message names in DHCPv4 over =
DHCPv6.&nbsp;<o:p></o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; ">Would it be OK if we keep =
the current message names?<o:p></o:p></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><o:p>&nbsp;</o:p></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; ">Best Regards,<o:p></o:p></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; ">Qi<o:p></o:p></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; =
"><o:p>&nbsp;</o:p></div></div><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt; "><div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></span></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">&nbsp;</span><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; =
"><o:p></o:p></span></div></div><div><div style=3D"border-right-style: =
none; border-bottom-style: none; border-left-style: none; border-width: =
initial; border-color: initial; border-top-style: solid; padding-top: =
3pt; padding-right: 0in; padding-bottom: 0in; padding-left: 0in; =
border-width: initial; border-color: initial; "><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><b><span style=3D"font-size: 10pt; font-family: Tahoma, =
sans-serif; ">From:</span></b><span class=3D"apple-converted-space"><span =
style=3D"font-size: 10pt; font-family: Tahoma, sans-serif; =
">&nbsp;</span></span><span style=3D"font-size: 10pt; font-family: =
Tahoma, sans-serif; ">dhcwg [<a href=3D"mailto:dhcwg-bounces@ietf.org" =
style=3D"color: blue; text-decoration: underline; =
">mailto:dhcwg-bounces@ietf.org</a>]<span =
class=3D"apple-converted-space">&nbsp;</span><b>On Behalf Of<span =
class=3D"apple-converted-space">&nbsp;</span></b>Bernie Volz =
(volz)<br><b>Sent:</b><span =
class=3D"apple-converted-space">&nbsp;</span>Sunday, November 24, 2013 =
5:03 PM<br><b>To:</b><span class=3D"apple-converted-space">&nbsp;</span><a=
 href=3D"mailto:dhcwg@ietf.org" style=3D"color: blue; text-decoration: =
underline; ">dhcwg@ietf.org</a><br><b>Subject:</b><span =
class=3D"apple-converted-space">&nbsp;</span>[dhcwg] WGLC for =
draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, =
2013</span><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; "><o:p></o:p></span></div></div></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; ">&nbsp;<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; ">Folks, the authors of draft-ietf-dhc-dhcpv4-over-dhcpv6-03 =
(<a =
href=3D"http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-03.tx=
t" style=3D"color: blue; text-decoration: underline; =
">http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-over-dhcpv6-03.txt</a>)=
 believe it is ready for working group last call. Please review this =
draft and indicate whether or not you feel it is ready to be published. =
Your input is important! Please respond by Dec 9<sup>th</sup>, =
2013.<o:p></o:p></span></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; =
">&nbsp;<o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">At the =
time of this writing, there is no IPR reported against this =
draft.<o:p></o:p></span></div></div><div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; =
">&nbsp;<o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">Bernie =
will be the document shepherd.<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; ">&nbsp;<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; ">Thanks,<o:p></o:p></span></div></div><div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; ">&nbsp;<o:p></o:p></span></div></div><div =
style=3D"margin-left: 0.5in; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
12pt; font-family: 'Times New Roman', serif; text-indent: -0.25in; =
"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
">-</span><span style=3D"font-size: 7pt; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span =
class=3D"apple-converted-space">&nbsp;</span></span><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">Tomek =
&amp; Bernie<o:p></o:p></span></div></div><div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 12pt; font-family: 'Times New Roman', serif; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
">&nbsp;<o:p></o:p></span></div></div></div></blockquote></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; =
"><o:p>&nbsp;</o:p></div></div></div></span></blockquote></div><br></body>=
</html>=

--Apple-Mail-66-522896407--

From Ted.Lemon@nominum.com  Thu Dec 12 06:48:48 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B4081AE307 for <dhcwg@ietfa.amsl.com>; Thu, 12 Dec 2013 06:48:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.6
X-Spam-Level: 
X-Spam-Status: No, score=-3.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fUlq1DLr9qV4 for <dhcwg@ietfa.amsl.com>; Thu, 12 Dec 2013 06:48:47 -0800 (PST)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id E969E1AE304 for <dhcwg@ietf.org>; Thu, 12 Dec 2013 06:48:46 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKUqnMyXhVJUWWZHNApYVvRETdDbQL2WYc@postini.com; Thu, 12 Dec 2013 06:48:41 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 922631B82E2 for <dhcwg@ietf.org>; Thu, 12 Dec 2013 06:48:40 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 6E406190043; Thu, 12 Dec 2013 06:48:40 -0800 (PST)
Received: from vpna-132.vpn.nominum.com (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 12 Dec 2013 06:48:40 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <F0A0E7AD-387E-4F9C-8200-4297E79BA566@gmail.com>
Date: Thu, 12 Dec 2013 09:48:35 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <0676A81F-E5B1-423C-8233-A5B143908A3A@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADD590C@xmb-rcd-x04.cisco.com> <CE4E8958-57AA-4D87-AA80-F2B12FF1A698@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1ADDF49A@xmb-rcd-x04.cisco.com> <F0A0E7AD-387E-4F9C-8200-4297E79BA566@gmail.com>
To: Qi Sun <sunqi.csnet.thu@gmail.com>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>, "draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org" <draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 12 Dec 2013 14:48:48 -0000

On Dec 12, 2013, at 7:39 AM, Qi Sun <sunqi.csnet.thu@gmail.com> wrote:
> I'm OK with your suggestion (using the  BOOTPREQUESTV6 and =
BOOTPREPLYV6).

The only reason to use BOOTREQUESTv6 and BOOTREPLYv6 is the similarity =
between that name and the name of the BOOTP packet that DHCPv4 rides in. =
  If you are going to change the name, you might as well call it =
DHCPv4QUERY and DHCPv4RESPONSE or something.   Using the BOOTP name =
allows you to avoid confusion between DHCPREQUEST/DHCPREPLY and =
DHCPv4REQUEST/DHCPv4REPLY, but you could use QUERY/RESPONSE to avoid =
that just as well.

Anyway, I don't think BOOTPREQUESTv6 makes a whole lot of sense.


From volz@cisco.com  Thu Dec 12 09:01:17 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD5A1ADFFD for <dhcwg@ietfa.amsl.com>; Thu, 12 Dec 2013 09:01:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.302
X-Spam-Level: 
X-Spam-Status: No, score=-8.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_55=0.6, J_CHICKENPOX_57=0.6, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1201UZ8cFT1i for <dhcwg@ietfa.amsl.com>; Thu, 12 Dec 2013 09:01:15 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id 9D7AA1ADF92 for <dhcwg@ietf.org>; Thu, 12 Dec 2013 09:01:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1836; q=dns/txt; s=iport; t=1386867669; x=1388077269; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=W9V93glHf+TAdzA/fG8UljpbWWzzHNB36et2XA1JfhA=; b=g/CTnbRL0PZB75eCfCqQ7yoZFrqjCrYJugzha49pqifABuP0gnHkRMnT vfUGPwIFDA7XAd6FxgOXcsQ5rZ5yPbxeyty/qAJ+dLOXqeDg4qLBemyTx swfQR+/YEcY27ctkaXEXqZtn7A5RV9U7r8ioEHqjPsa5QogvFO+S0RFIo Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhMFAGfqqVKtJV2a/2dsb2JhbABZgwqBDbhbgRwWdIIlAQEBBDo/DAQCAQgRBAEBAQoUCQchERQJCAIEAQ0FCIdoAxG7WA2HEheNAIFjMQcGgxuBEwSWKo5FhTqBa4E+gio
X-IronPort-AV: E=Sophos;i="4.93,879,1378857600";  d="scan'208";a="6336819"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-4.cisco.com with ESMTP; 12 Dec 2013 17:01:08 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rBCH18Y7027033 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 12 Dec 2013 17:01:08 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0123.003; Thu, 12 Dec 2013 11:01:08 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Ted Lemon <ted.lemon@nominum.com>, Qi Sun <sunqi.csnet.thu@gmail.com>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
Thread-Index: AQHO90lArmKZq0TABkWmduI/5klrZppQxvXA
Date: Thu, 12 Dec 2013 17:01:07 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1ADE2293@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADD590C@xmb-rcd-x04.cisco.com> <CE4E8958-57AA-4D87-AA80-F2B12FF1A698@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1ADDF49A@xmb-rcd-x04.cisco.com> <F0A0E7AD-387E-4F9C-8200-4297E79BA566@gmail.com> <0676A81F-E5B1-423C-8233-A5B143908A3A@nominum.com>
In-Reply-To: <0676A81F-E5B1-423C-8233-A5B143908A3A@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.65.131]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org" <draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 12 Dec 2013 17:01:17 -0000

I wonder whether DHCPV4REQUEST and DHCPV4REPLY (perhaps with a hyphen) may =
actually be better choices for the V6 messages. While the underlying protoc=
ol is BOOTP, that name is somewhat misleading and most everything now uses =
DHCP[v4] -- yes, I know that I was likely the source of those original mess=
age names.

I'm not sure using QUERY/RESPONSE adds much value.

But again, I really have no good answer here and was not trying to promote =
one name over the other - I was just asking the WG the question as to wheth=
er these are good message names or whether we wanted to change them now, be=
fore we are stuck with them 'forever'.

It is a minor issue (as what goes over the wire is really a message type co=
de), but it does make a difference in tools (i.e., packet decoders), logs, =
and in source code.

- Bernie

-----Original Message-----
From: Ted Lemon [mailto:ted.lemon@nominum.com]=20
Sent: Thursday, December 12, 2013 9:49 AM
To: Qi Sun
Cc: Bernie Volz (volz); dhcwg@ietf.org; draft-ietf-dhc-dhcpv4-over-dhcpv6@t=
ools.ietf.org
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respon=
d by Dec 9, 2013

On Dec 12, 2013, at 7:39 AM, Qi Sun <sunqi.csnet.thu@gmail.com> wrote:
> I'm OK with your suggestion (using the  BOOTPREQUESTV6 and BOOTPREPLYV6).

The only reason to use BOOTREQUESTv6 and BOOTREPLYv6 is the similarity betw=
een that name and the name of the BOOTP packet that DHCPv4 rides in.   If y=
ou are going to change the name, you might as well call it DHCPv4QUERY and =
DHCPv4RESPONSE or something.   Using the BOOTP name allows you to avoid con=
fusion between DHCPREQUEST/DHCPREPLY and DHCPv4REQUEST/DHCPv4REPLY, but you=
 could use QUERY/RESPONSE to avoid that just as well.

Anyway, I don't think BOOTPREQUESTv6 makes a whole lot of sense.


From msiodelski@gmail.com  Thu Dec 12 10:19:13 2013
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAF8B1ADC03 for <dhcwg@ietfa.amsl.com>; Thu, 12 Dec 2013 10:19:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_55=0.6, J_CHICKENPOX_57=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sfjTh3iiewIc for <dhcwg@ietfa.amsl.com>; Thu, 12 Dec 2013 10:19:11 -0800 (PST)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id C1F6D1AD75F for <dhcwg@ietf.org>; Thu, 12 Dec 2013 10:19:10 -0800 (PST)
Received: by mail-ie0-f173.google.com with SMTP id to1so1207655ieb.32 for <dhcwg@ietf.org>; Thu, 12 Dec 2013 10:19:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=CIuXNfVyOGRoAldPqDMk3pNlqNRjNIyNnKVF0u8UPQk=; b=GnJ74X9+GHd5ZFErtjZzUHy6zhTIvLcspQWkqbsDiidcDvw28lkSWFKRuJMWb03EGV 0Ojy59b4s6NYyxffK731gKLghQqYgFygVdNvwl0HXJuhaA/uQbwRJVbrCOKm3OdJ6Fx8 1ywTNzMdqTOWuKhCMYWX1qc+HwZqRT2RnEsjyi0MDSRg60TMDt/JoCe/G4+mM5W69C3T F85csT1C1RoJ2yhYFdsDafjTNEdbhnxPAwjsmpycw0Iycb6XCPjE9Y/K65qI9QprAtcg 1iX8q48REFqLnQPHwmq8/FICh/T6s9Xy8m8CDAUh+0nVIWebafn78HNmZZHFB8TirTUu sztg==
MIME-Version: 1.0
X-Received: by 10.43.8.66 with SMTP id or2mr7578843icb.19.1386872344729; Thu, 12 Dec 2013 10:19:04 -0800 (PST)
Received: by 10.50.32.33 with HTTP; Thu, 12 Dec 2013 10:19:04 -0800 (PST)
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADE2293@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADD590C@xmb-rcd-x04.cisco.com> <CE4E8958-57AA-4D87-AA80-F2B12FF1A698@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1ADDF49A@xmb-rcd-x04.cisco.com> <F0A0E7AD-387E-4F9C-8200-4297E79BA566@gmail.com> <0676A81F-E5B1-423C-8233-A5B143908A3A@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1ADE2293@xmb-rcd-x04.cisco.com>
Date: Thu, 12 Dec 2013 19:19:04 +0100
Message-ID: <CAFGoqUNZMXjNEx8=DhWPuqdmemWNfd6Exr4CtS3_p34sUpnVVQ@mail.gmail.com>
From: Marcin Siodelski <msiodelski@gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <ted.lemon@nominum.com>, "draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org" <draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 12 Dec 2013 18:19:13 -0000

On Thu, Dec 12, 2013 at 6:01 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> I wonder whether DHCPV4REQUEST and DHCPV4REPLY (perhaps with a hyphen) ma=
y actually be better choices for the V6 messages. While the underlying prot=
ocol is BOOTP, that name is somewhat misleading and most everything now use=
s DHCP[v4] -- yes, I know that I was likely the source of those original me=
ssage names.
>
I think you were the source of the names, Bernie. And I also think I
was the one who changed the original names to those that you suggested
:)
On reflection, I think we should revert it to something that has
DHCPV4 in it - it is less confusing and it is much easier to read than
BOOTREQUESTV6. I like DHCPV4-REQUEST/DHCPV4-REPLY.

Marcin

From Ted.Lemon@nominum.com  Thu Dec 12 10:28:03 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A9001AE3BB for <dhcwg@ietfa.amsl.com>; Thu, 12 Dec 2013 10:28:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3
X-Spam-Level: 
X-Spam-Status: No, score=-3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  J_CHICKENPOX_55=0.6, J_CHICKENPOX_57=0.6, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SCHTOr3EjmL1 for <dhcwg@ietfa.amsl.com>; Thu, 12 Dec 2013 10:28:01 -0800 (PST)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id B2B981AE3B6 for <dhcwg@ietf.org>; Thu, 12 Dec 2013 10:28:01 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUqoAKy4nYXBRDDAcWUQuX0GJiBDOuAux@postini.com; Thu, 12 Dec 2013 10:27:56 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id C53CF1B82C3 for <dhcwg@ietf.org>; Thu, 12 Dec 2013 10:27:55 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id BE590190043; Thu, 12 Dec 2013 10:27:55 -0800 (PST)
Received: from vpna-132.vpn.nominum.com (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 12 Dec 2013 10:27:55 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADE2293@xmb-rcd-x04.cisco.com>
Date: Thu, 12 Dec 2013 13:27:55 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <E9C0ED69-964E-4A47-AAC0-2848EA1490D7@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADD590C@xmb-rcd-x04.cisco.com> <CE4E8958-57AA-4D87-AA80-F2B12FF1A698@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1ADDF49A@xmb-rcd-x04.cisco.com> <F0A0E7AD-387E-4F9C-8200-4297E79BA566@gmail.com> <0676A81F-E5B1-423C-8233-A5B143908A3A@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1ADE2293@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org" <draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 12 Dec 2013 18:28:03 -0000

On Dec 12, 2013, at 12:01 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> I wonder whether DHCPV4REQUEST and DHCPV4REPLY (perhaps with a hyphen) =
may actually be better choices for the V6 messages.

I think this is going to create confusion.   But it's not desperately =
important.


From damalhot@cisco.com  Thu Dec 12 10:31:22 2013
Return-Path: <damalhot@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E6F51AE0BE for <dhcwg@ietfa.amsl.com>; Thu, 12 Dec 2013 10:31:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.502
X-Spam-Level: 
X-Spam-Status: No, score=-9.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3AXYQ2yJymsI for <dhcwg@ietfa.amsl.com>; Thu, 12 Dec 2013 10:31:19 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) by ietfa.amsl.com (Postfix) with ESMTP id CA9A81AE3C2 for <dhcwg@ietf.org>; Thu, 12 Dec 2013 10:31:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3414; q=dns/txt; s=iport; t=1386873074; x=1388082674; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=xcPzQi1JfdGZnowRaw56UsdOK21uplDBhXT/RNOgStU=; b=TRgH/3TxQshq6IM2nF2+cEKcqHb76BUIb4GIzfsU2Vai7LQvXAyv02T/ hxdo03/w4pZaI+2zjFjCIm/nLEjo8TEJhV2cKh9vhBS12aHPWcykF6VeP kKzac5+XdxaVNk+UWowjJ+/pL3DFiH40D8tARMGnifpbd/5c2t54BMq/1 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjIFAKb/qVKtJV2a/2dsb2JhbABZgwo4Twa4W4EdFnSCJQEBAQMBAQEBNzQJAgUHBAIBCBEDAQEBCxQJByEGCxQJCAIEAQkEBQgBh2cDCQgIBbtMDYcKF40AgTwnMQcGgxuBEwSUMoF4gxuLKoU6gWuBPoFoQg
X-IronPort-AV: E=Sophos;i="4.93,879,1378857600";  d="scan'208";a="6350905"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-1.cisco.com with ESMTP; 12 Dec 2013 18:31:07 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rBCIV6X6024024 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Thu, 12 Dec 2013 18:31:06 GMT
Received: from xmb-aln-x03.cisco.com ([169.254.6.155]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0123.003; Thu, 12 Dec 2013 12:31:06 -0600
From: "Darpan Malhotra (damalhot)" <damalhot@cisco.com>
To: "Kim Kinnear (kkinnear)" <kkinnear@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] New Version Notification for draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
Thread-Index: AQHO8Q1gcDpw+YXsQECLcOf+FLDz/ZpQ7TKw
Date: Thu, 12 Dec 2013 18:31:05 +0000
Message-ID: <7E887AE87A54714684B968773B57C8A31DA704B9@xmb-aln-x03.cisco.com>
References: <20131204150103.9960.74169.idtracker@ietfa.amsl.com> <D5A32E2B-CAA1-4ECB-AA86-7CD567738A62@cisco.com>
In-Reply-To: <D5A32E2B-CAA1-4ECB-AA86-7CD567738A62@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.65.45.19]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] New Version Notification for	draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 12 Dec 2013 18:31:22 -0000

I support adoption of this draft.

Regards,
Darpan

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Kim Kinnear (kkinn=
ear)
Sent: Wednesday, December 04, 2013 9:55 PM
To: dhcwg@ietf.org
Cc: Bernie Volz (volz); Kim Kinnear (kkinnear)
Subject: [dhcwg] New Version Notification for draft-kinnear-dhc-dhcpv4-acti=
ve-leasequery-02.txt


Folks,

During the adoption discussion about DHCPv6 Active Leasequery there was som=
e discussion about having a corresponding DHCPv4 Active Leasequery capabili=
ty.  If there is sufficient interest in a DHCPv4 Active Leasequery capabili=
ty to parallel the DHCPv6 capability that was adopted as a DHC WG work item=
 recently, then we can decide whether or not we want to have two drafts mov=
ing toward two RFC's, or combine them into one draft.

But the first question is whether or not there is sufficient interest in ha=
ving a DHCPv4 Active Leasequery capability at all!

In order to help decide this question, I have updated the existing
DHCPv4 Active Leasequery draft from a couple of years ago, and resubmitted =
it as an individual submission -- as recommended by Bernie and Tomek.

Below you can find the information on how to find this new draft.

Regards -- Kim


Begin forwarded message:

> From: <internet-drafts@ietf.org>
> Subject: New Version Notification for=20
> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
> Date: December 4, 2013 10:01:03 AM EST
> To: Bernie Volz <volz@cisco.com>, Mark Stapp <mjs@cisco.com>, Kim=20
> Kinnear <kkinnear@cisco.com>, Neil Russell <neil.e.russell@gmail.com>
>=20
>=20
> A new version of I-D,=20
> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
> has been successfully submitted by Kim Kinnear and posted to the IETF=20
> repository.
>=20
> Filename:	 draft-kinnear-dhc-dhcpv4-active-leasequery
> Revision:	 02
> Title:		 Active DHCPv4 Lease Query
> Creation date:	 2013-12-04
> Group:		 Individual Submission
> Number of pages: 22
> URL:             http://www.ietf.org/internet-drafts/draft-kinnear-dhc-dh=
cpv4-active-leasequery-02.txt
> Status:          http://datatracker.ietf.org/doc/draft-kinnear-dhc-dhcpv4=
-active-leasequery
> Htmlized:        http://tools.ietf.org/html/draft-kinnear-dhc-dhcpv4-acti=
ve-leasequery-02
> Diff:            http://www.ietf.org/rfcdiff?url2=3Ddraft-kinnear-dhc-dhc=
pv4-active-leasequery-02
>=20
> Abstract:
>   The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has been
>   extended with a Leasequery capability that allows a client to request
>   information about DHCPv4 bindings.  That mechanism is limited to
>   queries for individual bindings.  In some situations individual
>   binding queries may not be efficient, or even possible.  In addition,
>   continuous update of an external client with Leasequery data is
>   sometimes desired. This document expands on the DHCPv4 Leasequery
>   protocol, and allows for active transfer of near real-time DHCPv4
>   address binding information data via TCP.
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of=20
> submission until the htmlized version and diff are available at tools.iet=
f.org.
>=20
> The IETF Secretariat
>=20

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

From volz@cisco.com  Thu Dec 12 13:26:25 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D4A21ADF8B for <dhcwg@ietfa.amsl.com>; Thu, 12 Dec 2013 13:26:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.302
X-Spam-Level: 
X-Spam-Status: No, score=-8.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_55=0.6, J_CHICKENPOX_57=0.6, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4cDOMYa7cj9N for <dhcwg@ietfa.amsl.com>; Thu, 12 Dec 2013 13:26:24 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id 545191ADED5 for <dhcwg@ietf.org>; Thu, 12 Dec 2013 13:26:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1554; q=dns/txt; s=iport; t=1386883578; x=1388093178; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=zl6Him6vu+OwWKmWblNi2yneX+veJ4UouX7MrTY6Raw=; b=cKdOFCxbDOJ+3jshOmgtQx+4mkcT0KkTc+Sr/ilIlhNEM04u9GHMUB2j PiAUv4ppvo+fITqLh/bFFHwndYuwf21cy1OG7J0Wcp8eVl8ZK9ZjsH+Qb pYrsylUgQH3xrjsAU/xFSkZV4hDaSnn0f8tNBx1N2UaOwItXh9peL3enC Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFALwoqlKtJV2a/2dsb2JhbABZgwo4VbhYgR0WdIIlAQEBBAEBATc0CwwEAgEIDgMEAQEBChQJBycLFAkIAgQOBQiHfA3DJBMEjmMxBwaDHIETBKopgWuBPoIq
X-IronPort-AV: E=Sophos;i="4.95,473,1384300800";  d="scan'208";a="6398647"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-4.cisco.com with ESMTP; 12 Dec 2013 21:26:18 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id rBCLQIvo019253 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 12 Dec 2013 21:26:18 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0123.003; Thu, 12 Dec 2013 15:26:17 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Marcin Siodelski <msiodelski@gmail.com>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
Thread-Index: AQHO90lArmKZq0TABkWmduI/5klrZppQxvXAgAB8VAD//88B8A==
Date: Thu, 12 Dec 2013 21:26:16 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1ADE290C@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADD590C@xmb-rcd-x04.cisco.com> <CE4E8958-57AA-4D87-AA80-F2B12FF1A698@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1ADDF49A@xmb-rcd-x04.cisco.com> <F0A0E7AD-387E-4F9C-8200-4297E79BA566@gmail.com> <0676A81F-E5B1-423C-8233-A5B143908A3A@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1ADE2293@xmb-rcd-x04.cisco.com> <CAFGoqUNZMXjNEx8=DhWPuqdmemWNfd6Exr4CtS3_p34sUpnVVQ@mail.gmail.com>
In-Reply-To: <CAFGoqUNZMXjNEx8=DhWPuqdmemWNfd6Exr4CtS3_p34sUpnVVQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.65.131]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <ted.lemon@nominum.com>, "draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org" <draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 12 Dec 2013 21:26:25 -0000

I already indicated (twice) that I was likely the source of the current nam=
es (though I believe I suggested BOOTP, not BOOT, because that was the prot=
ocol). Not all my ideas are good and sometimes what looks good at first tur=
ns out to be poor when seen in more context or given more thought.

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Marcin Siodelski
Sent: Thursday, December 12, 2013 1:19 PM
To: Bernie Volz (volz)
Cc: dhcwg@ietf.org; Ted Lemon; draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf=
.org
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respon=
d by Dec 9, 2013

On Thu, Dec 12, 2013 at 6:01 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> I wonder whether DHCPV4REQUEST and DHCPV4REPLY (perhaps with a hyphen) ma=
y actually be better choices for the V6 messages. While the underlying prot=
ocol is BOOTP, that name is somewhat misleading and most everything now use=
s DHCP[v4] -- yes, I know that I was likely the source of those original me=
ssage names.
>
I think you were the source of the names, Bernie. And I also think I was th=
e one who changed the original names to those that you suggested
:)
On reflection, I think we should revert it to something that has
DHCPV4 in it - it is less confusing and it is much easier to read than BOOT=
REQUESTV6. I like DHCPV4-REQUEST/DHCPV4-REPLY.

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

From sunqi.csnet.thu@gmail.com  Thu Dec 12 19:15:37 2013
Return-Path: <sunqi.csnet.thu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC9E51AE0AD for <dhcwg@ietfa.amsl.com>; Thu, 12 Dec 2013 19:15:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_55=0.6, J_CHICKENPOX_57=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TFfNEpSMeMWr for <dhcwg@ietfa.amsl.com>; Thu, 12 Dec 2013 19:15:36 -0800 (PST)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 7F8E81AE03A for <dhcwg@ietf.org>; Thu, 12 Dec 2013 19:15:36 -0800 (PST)
Received: by mail-pd0-f170.google.com with SMTP id g10so1646721pdj.29 for <dhcwg@ietf.org>; Thu, 12 Dec 2013 19:15:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Dcb1vvmjHPpJDPWy8gIa6xpVzWfj3Br5JLbm8AVfGqA=; b=RByGNZPKyr9T4Ks/oxKHFMaAuGtY8Htzn/6nElwWrLnt6nT8plrb3PsZ+0QzrM6H4v r6Xtaku/vcCVMAZyicpiKsnIOItt/rvQ/NTdQf/ZL00czEt5WJI1GSLuzFwhXYe/n1Gi JbZEs4eVt5Ze14VROCNJDjyCezR5pypMqBytsxugtjjacwLyIfgkuSevYjzYDGAoSmyW RGkn+D/beneqnnG5wxw8QZqIvK1vs6oMCEPMOlm3+96KXsiIT9h5XwGQeHAsK0xb39KP 6tF9O5EeYP/A6O/nbF5kPMR2OWO25a4w3MccxMqebRhwS/eTChQn515G58g1Rqb1f2t6 q9dg==
X-Received: by 10.66.147.193 with SMTP id tm1mr423717pab.56.1386904530498; Thu, 12 Dec 2013 19:15:30 -0800 (PST)
Received: from [192.168.199.122] ([166.111.68.231]) by mx.google.com with ESMTPSA id oa3sm907344pbb.15.2013.12.12.19.15.27 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 12 Dec 2013 19:15:29 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=utf-8
From: Qi Sun <sunqi.csnet.thu@gmail.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADE2293@xmb-rcd-x04.cisco.com>
Date: Fri, 13 Dec 2013 11:15:23 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <46A68A10-2A09-47DD-BE80-0A30C76320B8@gmail.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADD590C@xmb-rcd-x04.cisco.com> <CE4E8958-57AA-4D87-AA80-F2B12FF1A698@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1ADDF49A@xmb-rcd-x04.cisco.com> <F0A0E7AD-387E-4F9C-8200-4297E79BA566@gmail.com> <0676A81F-E5B1-423C-8233-A5B143908A3A@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1ADE2293@xmb-rcd-x04.cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, Marcin Siodelski <msiodelski@gmail.com>
X-Mailer: Apple Mail (2.1085)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Ted Lemon <ted.lemon@nominum.com>, "draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org" <draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 13 Dec 2013 03:15:37 -0000

Hi,=20

I would prefer DHCPV4-QUERY and DHCPV4-RESPONSE. IMHO, the =
DHCPV4-REQUEST/REPLY might cause confusion with DHCPREQUEST in RFC2131.=20=



Best Regards,
Qi


On 2013-12-13, at =E4=B8=8A=E5=8D=881:01, Bernie Volz (volz) wrote:

> I wonder whether DHCPV4REQUEST and DHCPV4REPLY (perhaps with a hyphen) =
may actually be better choices for the V6 messages. While the underlying =
protocol is BOOTP, that name is somewhat misleading and most everything =
now uses DHCP[v4] -- yes, I know that I was likely the source of those =
original message names.
>=20
> I'm not sure using QUERY/RESPONSE adds much value.
>=20
> But again, I really have no good answer here and was not trying to =
promote one name over the other - I was just asking the WG the question =
as to whether these are good message names or whether we wanted to =
change them now, before we are stuck with them 'forever'.
>=20
> It is a minor issue (as what goes over the wire is really a message =
type code), but it does make a difference in tools (i.e., packet =
decoders), logs, and in source code.
>=20
> - Bernie
>=20
> -----Original Message-----
> From: Ted Lemon [mailto:ted.lemon@nominum.com]=20
> Sent: Thursday, December 12, 2013 9:49 AM
> To: Qi Sun
> Cc: Bernie Volz (volz); dhcwg@ietf.org; =
draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org
> Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - =
Respond by Dec 9, 2013
>=20
> On Dec 12, 2013, at 7:39 AM, Qi Sun <sunqi.csnet.thu@gmail.com> wrote:
>> I'm OK with your suggestion (using the  BOOTPREQUESTV6 and =
BOOTPREPLYV6).
>=20
> The only reason to use BOOTREQUESTv6 and BOOTREPLYv6 is the similarity =
between that name and the name of the BOOTP packet that DHCPv4 rides in. =
  If you are going to change the name, you might as well call it =
DHCPv4QUERY and DHCPv4RESPONSE or something.   Using the BOOTP name =
allows you to avoid confusion between DHCPREQUEST/DHCPREPLY and =
DHCPv4REQUEST/DHCPv4REPLY, but you could use QUERY/RESPONSE to avoid =
that just as well.
>=20
> Anyway, I don't think BOOTPREQUESTv6 makes a whole lot of sense.
>=20
>=20


From msiodelski@gmail.com  Thu Dec 12 19:46:43 2013
Return-Path: <msiodelski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1C4E1AE10D for <dhcwg@ietfa.amsl.com>; Thu, 12 Dec 2013 19:46:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_55=0.6, J_CHICKENPOX_57=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DmN0Pjm8dniF for <dhcwg@ietfa.amsl.com>; Thu, 12 Dec 2013 19:46:42 -0800 (PST)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 955F61AE107 for <dhcwg@ietf.org>; Thu, 12 Dec 2013 19:46:42 -0800 (PST)
Received: by mail-ie0-f177.google.com with SMTP id tp5so2094785ieb.36 for <dhcwg@ietf.org>; Thu, 12 Dec 2013 19:46:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=6Y3UcXCINcSEIt+3K39ub5fcAQ9uKrJbL7PFwHKuCKE=; b=0dsZC5BhZCjSC88liX0wyayCJnqEM5GRvPN7Q1EYge7oiH39eu3B2QUscZSKBRTcp9 XNH9AuB1oza/50WM3leOxprIwZtJOYZoo29HlOOBvscFQpkZtbG2SPJioIMBIINGoRDW 88mi8M+cUHRYZ4X5IawqNBahvzzci0Ka4jp+q0rn7wNrtUFY/5pku68d/CeK9sgIJf1p Q2vLxdyHev1V9iAYT3iQF0bH3jcMl72EaOq5pespCbKaZQgRAcCQH5rhNQS330/gnt5i qi1rOiKiXU7SN4SkE1PJbL9mNOg2FQXu0XnD3JlqsIUNtT0LHHUpKiUlzMZ6BKiBlsIY mSOw==
MIME-Version: 1.0
X-Received: by 10.43.117.131 with SMTP id fm3mr211176icc.33.1386906396378; Thu, 12 Dec 2013 19:46:36 -0800 (PST)
Received: by 10.50.32.33 with HTTP; Thu, 12 Dec 2013 19:46:36 -0800 (PST)
In-Reply-To: <46A68A10-2A09-47DD-BE80-0A30C76320B8@gmail.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADD590C@xmb-rcd-x04.cisco.com> <CE4E8958-57AA-4D87-AA80-F2B12FF1A698@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1ADDF49A@xmb-rcd-x04.cisco.com> <F0A0E7AD-387E-4F9C-8200-4297E79BA566@gmail.com> <0676A81F-E5B1-423C-8233-A5B143908A3A@nominum.com> <489D13FBFA9B3E41812EA89F188F018E1ADE2293@xmb-rcd-x04.cisco.com> <46A68A10-2A09-47DD-BE80-0A30C76320B8@gmail.com>
Date: Fri, 13 Dec 2013 04:46:36 +0100
Message-ID: <CAFGoqUMt3KaP3Oeq77FVS5KR7AfC2VDFhtAcycW-d7CSQ1xr1Q@mail.gmail.com>
From: Marcin Siodelski <msiodelski@gmail.com>
To: Qi Sun <sunqi.csnet.thu@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>, "draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org" <draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org>, Ted Lemon <ted.lemon@nominum.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 13 Dec 2013 03:46:43 -0000

That is fine by me, Qi.

Marcin

On Fri, Dec 13, 2013 at 4:15 AM, Qi Sun <sunqi.csnet.thu@gmail.com> wrote:
>
> Hi,
>
> I would prefer DHCPV4-QUERY and DHCPV4-RESPONSE. IMHO, the DHCPV4-REQUEST=
/REPLY might cause confusion with DHCPREQUEST in RFC2131.
>
>
> Best Regards,
> Qi
>
>
> On 2013-12-13, at =E4=B8=8A=E5=8D=881:01, Bernie Volz (volz) wrote:
>
>> I wonder whether DHCPV4REQUEST and DHCPV4REPLY (perhaps with a hyphen) m=
ay actually be better choices for the V6 messages. While the underlying pro=
tocol is BOOTP, that name is somewhat misleading and most everything now us=
es DHCP[v4] -- yes, I know that I was likely the source of those original m=
essage names.
>>
>> I'm not sure using QUERY/RESPONSE adds much value.
>>
>> But again, I really have no good answer here and was not trying to promo=
te one name over the other - I was just asking the WG the question as to wh=
ether these are good message names or whether we wanted to change them now,=
 before we are stuck with them 'forever'.
>>
>> It is a minor issue (as what goes over the wire is really a message type=
 code), but it does make a difference in tools (i.e., packet decoders), log=
s, and in source code.
>>
>> - Bernie
>>
>> -----Original Message-----
>> From: Ted Lemon [mailto:ted.lemon@nominum.com]
>> Sent: Thursday, December 12, 2013 9:49 AM
>> To: Qi Sun
>> Cc: Bernie Volz (volz); dhcwg@ietf.org; draft-ietf-dhc-dhcpv4-over-dhcpv=
6@tools.ietf.org
>> Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Res=
pond by Dec 9, 2013
>>
>> On Dec 12, 2013, at 7:39 AM, Qi Sun <sunqi.csnet.thu@gmail.com> wrote:
>>> I'm OK with your suggestion (using the  BOOTPREQUESTV6 and BOOTPREPLYV6=
).
>>
>> The only reason to use BOOTREQUESTv6 and BOOTREPLYv6 is the similarity b=
etween that name and the name of the BOOTP packet that DHCPv4 rides in.   I=
f you are going to change the name, you might as well call it DHCPv4QUERY a=
nd DHCPv4RESPONSE or something.   Using the BOOTP name allows you to avoid =
confusion between DHCPREQUEST/DHCPREPLY and DHCPv4REQUEST/DHCPv4REPLY, but =
you could use QUERY/RESPONSE to avoid that just as well.
>>
>> Anyway, I don't think BOOTPREQUESTv6 makes a whole lot of sense.
>>
>>
>

From volz@cisco.com  Sat Dec 14 07:11:36 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 038611ADF26 for <dhcwg@ietfa.amsl.com>; Sat, 14 Dec 2013 07:11:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.501
X-Spam-Level: 
X-Spam-Status: No, score=-9.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YkRzvnzphUg4 for <dhcwg@ietfa.amsl.com>; Sat, 14 Dec 2013 07:11:19 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) by ietfa.amsl.com (Postfix) with ESMTP id 91CB01AE124 for <dhcwg@ietf.org>; Sat, 14 Dec 2013 07:11:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10303; q=dns/txt; s=iport; t=1387033861; x=1388243461; h=from:to:subject:date:message-id:mime-version; bh=vMTqkUfEbY+pehJBW1l7o4bHAEK/m0XidosZBB70LPM=; b=InIGrmtzGQmW2ANPKRcodM3bMLn0e16QJzH9gwcwIZIBIUDPGYKup2yL EKb6mEQebuW6gMIiuO5E4KzMpZzcukIdbmRJjpVU+5SRgCjy1ThaTqm7I 4iumDye6Cj6BaniszAGsSVtic9H6Ko81sMjJQgoBGnC6Fe3O/84q/rr+Q 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AisFALl0rFKtJXG+/2dsb2JhbABZgkZEOFW4YYEbFnSCJwEELV4BKlYmAQQbh3yjFKZdF45og1uBEwSqKoFsgT6CKg
X-IronPort-AV: E=Sophos;i="4.95,485,1384300800"; d="scan'208,217";a="6788750"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by alln-iport-2.cisco.com with ESMTP; 14 Dec 2013 15:10:47 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id rBEFAlac028415 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Sat, 14 Dec 2013 15:10:47 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0123.003; Sat, 14 Dec 2013 09:10:46 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: Results of WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
Thread-Index: Ac743qQ8LugREmTXTeyq+h7sadwKJg==
Date: Sat, 14 Dec 2013 15:10:46 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1ADE84D3@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.246.112]
Content-Type: multipart/alternative; boundary="_000_489D13FBFA9B3E41812EA89F188F018E1ADE84D3xmbrcdx04ciscoc_"
MIME-Version: 1.0
Subject: [dhcwg] Results of WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Dec 2013 15:11:36 -0000

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

This is to announce the results of the WGLC on draft-ietf-dhc-dhcpv4-over-d=
hcpv6-03.

There were discussions on several topics and a list of nits, so a new draft=
 will be needed.

Our determination of the rough consensus is that this work should advance. =
However, as a new draft is required and as a WGLC on the related draft-ietf=
-dhc-v4configuration-03 is in progress, we will await an updated draft and =
the outcome of the WGLC on draft-ietf-dhc-v4configuration-03 before finaliz=
ing on next steps.

The authors are requested to publish an updated draft to address the points=
 raised during the WGLC.

Given (at least) two people's concerns about this work (which are probably =
more directed at the conclusion of draft-ietf-dhc-v4configuration), we shou=
ld remember the original issue was how to configure IPv4 stacks on IPv6 isl=
ands. The WG consensus for that was, I believe, clearly to use DHCPv4. And =
while draft-ietf-dhc-dhcpv4-over-dhcpv6 solves this when 'native' IPv4 comm=
unication is not possible, it is not always required - i.e., if 'native' DH=
CPv4 (over IPv4) is usable. So, the appropriate conclusions from both sets =
of work are l believe:

1.       Use DHCPv4 for IPv4 configuration.

2.       Use DHCPv4 'as is' when possible.

3.       Use draft-ietf-dhc-dhcpv4-over-dhcpv6 when DHCPv4 'as is' is not p=
ossible (i.e., no ability to get native IPv4 packets to a DHCPv4 relay or s=
erver).


-          Bernie & Tomek


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:782577354;
	mso-list-type:hybrid;
	mso-list-template-ids:-1739543618 1832801198 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1
	{mso-list-id:820927867;
	mso-list-type:hybrid;
	mso-list-template-ids:292721482 67698703 67698713 67698715 67698703 676987=
13 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">This is to announce the results of the WGLC on draft=
-ietf-dhc-dhcpv4-over-dhcpv6-03.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">There were discussions on several topics and a list =
of nits, so a new draft will be needed.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Our determination of the rough consensus is that thi=
s work should advance. However, as a new draft is required and as a WGLC on=
 the related draft-ietf-dhc-v4configuration-03 is in progress, we will awai=
t an updated draft and the outcome
 of the WGLC on draft-ietf-dhc-v4configuration-03 before finalizing on next=
 steps.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The authors are requested to publish an updated draf=
t to address the points raised during the WGLC.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Given (at least) two people&#8217;s concerns about t=
his work (which are probably more directed at the conclusion of draft-ietf-=
dhc-v4configuration), we should remember the original issue was how to conf=
igure IPv4 stacks on IPv6 islands. The WG
 consensus for that was, I believe, clearly to use DHCPv4. And while draft-=
ietf-dhc-dhcpv4-over-dhcpv6 solves this when &#8216;native&#8217; IPv4 comm=
unication is not possible, it is not always required &#8211; i.e., if &#821=
6;native&#8217; DHCPv4 (over IPv4) is usable. So, the appropriate
 conclusions from both sets of work are l believe:<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">1.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span><![endif]>Use DHCPv4 for IPv4 configuration.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">2.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span><![endif]>Use DHCPv4 &#8216;as is&#8217; when possible.<o:p><=
/o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l1 level=
1 lfo2"><![if !supportLists]><span style=3D"mso-list:Ignore">3.<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;
</span></span><![endif]>Use draft-ietf-dhc-dhcpv4-over-dhcpv6 when DHCPv4 &=
#8216;as is&#8217; is not possible (i.e., no ability to get native IPv4 pac=
kets to a DHCPv4 relay or server).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Bernie &amp; Tomek<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_489D13FBFA9B3E41812EA89F188F018E1ADE84D3xmbrcdx04ciscoc_--

From internet-drafts@ietf.org  Sun Dec 15 19:25:43 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CE081AE25A; Sun, 15 Dec 2013 19:25:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NvULFUw10k4N; Sun, 15 Dec 2013 19:25:38 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E1BB31AE222; Sun, 15 Dec 2013 19:25:37 -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: 4.83.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131216032537.25601.52596.idtracker@ietfa.amsl.com>
Date: Sun, 15 Dec 2013 19:25:37 -0800
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-unknown-msg-04.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 16 Dec 2013 03:25:44 -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 Group =
of the IETF.

	Title           : Handling Unknown DHCPv6 Messages
	Author(s)       : Yong Cui
                          Qi Sun
                          Ted Lemon
	Filename        : draft-ietf-dhc-dhcpv6-unknown-msg-04.txt
	Pages           : 6
	Date            : 2013-12-15

Abstract:
   DHCPv6 is not specific about handling messages with unknown types.
   This memo describes the problems and defines how a DHCPv6 server,
   client or relay agent should behave when receiving unknown DHCPv6
   messages.  This document updates RFC3315.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-unknown-msg

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-unknown-msg-04

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dhc-dhcpv6-unknown-msg-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From sunqi.csnet.thu@gmail.com  Sun Dec 15 19:30:10 2013
Return-Path: <sunqi.csnet.thu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB6B71AE247 for <dhcwg@ietfa.amsl.com>; Sun, 15 Dec 2013 19:30:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1JgMOIv-mlt1 for <dhcwg@ietfa.amsl.com>; Sun, 15 Dec 2013 19:30:06 -0800 (PST)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 89CBF1AE23B for <dhcwg@ietf.org>; Sun, 15 Dec 2013 19:30:06 -0800 (PST)
Received: by mail-pb0-f51.google.com with SMTP id up15so4919161pbc.10 for <dhcwg@ietf.org>; Sun, 15 Dec 2013 19:30:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:date:references:to:message-id :mime-version; bh=8pdO6/aBtxBaEMLN45gz7c44VIjf6CUSEhn8n3NJW/g=; b=xUbvVKNhVCdhn400hzGRVYvVaRm+S3q1ns0QhbaPZWAJaQ4G2MwIsWbudXh72eT2jR sB4YfY7hp90yGWM/Olxv/ak+fo+n7PpVqqhIzFfb8VWwdC45XFAp+0VZeHyGXJjdVflG pse8YC/zQk9v/zmjxuIBrk1lSahVhmyvQr/k1/4SL/VL5yn4xMXzi5VIz4ji5mEgvt+M hrzzziL68cYXS2BT7sl6HClm96uTFBfLmI7rTeQz4G6SrAA/5/q72V26Vr1y+E+3OA53 jcsTrjIEodUSPZLwsqvyWFoSBCR32PbfSlhTbBy3npz98cHvl6lun9gmrWQE1KXXPakP fVZg==
X-Received: by 10.68.170.225 with SMTP id ap1mr17489556pbc.117.1387164606115;  Sun, 15 Dec 2013 19:30:06 -0800 (PST)
Received: from [192.168.199.122] ([166.111.68.231]) by mx.google.com with ESMTPSA id at4sm22450302pbc.30.2013.12.15.19.30.04 for <dhcwg@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 15 Dec 2013 19:30:05 -0800 (PST)
From: Qi Sun <sunqi.csnet.thu@gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-18-835507709
Date: Mon, 16 Dec 2013 11:30:00 +0800
References: <20131216032537.25601.52596.idtracker@ietfa.amsl.com>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Message-Id: <E60FC26B-8075-46AB-B61A-EBB37FE9A509@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Subject: [dhcwg] Fwd: I-D Action: draft-ietf-dhc-dhcpv6-unknown-msg-04.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 16 Dec 2013 03:30:10 -0000

--Apple-Mail-18-835507709
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Dear all,

We have updated the draft-ietf-dhc-dhcpv6-unknown-msg. Major changes =
are:=20

1) Update the Sec 3 (Problem Statement)
2) Rename the Sec 4.1 to "A Valid Message for Constructing a New =
Relay-forward Message" to avoid the confusion about what 'valid' is for.
3) Reword the definition to the 'valid' message and the subsequent =
paragraph about unknown messages targeting at the relay agent.
4) Choose "toward" among "toward/towards/to" when describing the =
relaying direction.
5) Use the pre-RFC5378 boilerplate.
6) Correct some nits.

Thanks a lot for your inputs during the WGLC.=20

Best Regards,
Qi


Begin forwarded message:

> From: internet-drafts@ietf.org
> Date: 2013=E5=B9=B412=E6=9C=8816=E6=97=A5 =
=E4=B8=8A=E5=8D=8811=E6=97=B625=E5=88=8637=E7=A7=92=E6=A0=BC=E6=9E=97=E5=B0=
=BC=E6=B2=BB=E6=A0=87=E5=87=86=E6=97=B6=E9=97=B4+0800
> To: i-d-announce@ietf.org
> Cc: dhcwg@ietf.org
> Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-unknown-msg-04.txt
>=20
>=20
> 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.
>=20
> 	Title           : Handling Unknown DHCPv6 Messages
> 	Author(s)       : Yong Cui
>                          Qi Sun
>                          Ted Lemon
> 	Filename        : draft-ietf-dhc-dhcpv6-unknown-msg-04.txt
> 	Pages           : 6
> 	Date            : 2013-12-15
>=20
> Abstract:
>   DHCPv6 is not specific about handling messages with unknown types.
>   This memo describes the problems and defines how a DHCPv6 server,
>   client or relay agent should behave when receiving unknown DHCPv6
>   messages.  This document updates RFC3315.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-unknown-msg
>=20
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-unknown-msg-04
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dhc-dhcpv6-unknown-msg-04
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


--Apple-Mail-18-835507709
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; color: rgb(0, 0, 0); font-family: 'Heiti SC'; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: 'Heiti SC'; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Heiti SC'; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Heiti SC'; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><!--?xml version=3D"1.0" =
encoding=3D"UTF-8"?-->

<span class=3D"Apple-style-span" style=3D"font-family: Arial; ">Dear =
all,</span><div style=3D"font-family: Arial; "><br></div><div =
style=3D"font-family: Arial; ">We have updated =
the&nbsp;draft-ietf-dhc-dhcpv6-unknown-msg. Major changes =
are:&nbsp;</div><div style=3D"font-family: Arial; "><br></div><div =
xmlns=3D"http://www.w3.org/1999/xhtml" style=3D"font-family: Arial; ">1) =
Update the Sec 3 (Problem Statement)</div><div =
xmlns=3D"http://www.w3.org/1999/xhtml" style=3D"font-family: Arial; ">2) =
Rename the Sec 4.1 to "A Valid Message for Constructing a New =
Relay-forward Message" to avoid the confusion about what 'valid' is =
for.</div><div xmlns=3D"http://www.w3.org/1999/xhtml" =
style=3D"font-family: Arial; ">3) Reword the definition to the 'valid' =
message and the subsequent paragraph about unknown messages targeting at =
the relay agent.</div><div xmlns=3D"http://www.w3.org/1999/xhtml" =
style=3D"font-family: Arial; ">4) Choose "toward" among =
"toward/towards/to" when describing the relaying direction.</div><div =
xmlns=3D"http://www.w3.org/1999/xhtml" style=3D"font-family: Arial; ">5) =
Use the&nbsp;pre-RFC5378 boilerplate.</div><div style=3D"font-family: =
Arial; ">6) Correct some nits.<br></div><div style=3D"font-family: =
Arial; "><br></div><div style=3D"font-family: Arial; ">Thanks a lot for =
your inputs during the WGLC.&nbsp;</div><div style=3D"font-family: =
Arial; "><br></div><div style=3D"font-family: Arial; ">Best =
Regards,</div><div style=3D"font-family: Arial; =
">Qi</div><br></div></span></div></span></div></span></span>
</div>
<div><br><div>Begin forwarded message:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>From: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><a =
href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a><br><=
/span></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1);"><b>Date: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;">2013=E5=B9=B412=E6=9C=8816=E6=97=A5 =
=E4=B8=8A=E5=8D=8811=E6=97=B625=E5=88=8637=E7=A7=92=E6=A0=BC=E6=9E=97=E5=B0=
=BC=E6=B2=BB=E6=A0=87=E5=87=86=E6=97=B6=E9=97=B4+0800<br></span></div><div=
 style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>To: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><a =
href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a><br></span>=
</div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Cc: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><a =
href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><br></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Subject: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><b>[dhcwg] I-D =
Action: =
draft-ietf-dhc-dhcpv6-unknown-msg-04.txt</b><br></span></div><br><div><br>=
A New Internet-Draft is available from the on-line Internet-Drafts =
directories.<br> This draft is a work item of the Dynamic Host =
Configuration Working Group of the IETF.<br><br><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Title =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Handling =
Unknown DHCPv6 Messages<br><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Author(s) =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Yong Cui<br> =
&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;&nbs=
p;Qi Sun<br> =
&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;&nbs=
p;Ted Lemon<br><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Filename &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
draft-ietf-dhc-dhcpv6-unknown-msg-04.txt<br><span class=3D"Apple-tab-span"=
 style=3D"white-space:pre">	</span>Pages =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 6<br><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Date =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
2013-12-15<br><br>Abstract:<br> &nbsp;&nbsp;DHCPv6 is not specific about =
handling messages with unknown types.<br> &nbsp;&nbsp;This memo =
describes the problems and defines how a DHCPv6 server,<br> =
&nbsp;&nbsp;client or relay agent should behave when receiving unknown =
DHCPv6<br> &nbsp;&nbsp;messages. &nbsp;This document updates =
RFC3315.<br><br><br>The IETF datatracker status page for this draft =
is:<br><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-unknown-msg=
">https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-unknown-msg</a><b=
r><br>There's also a htmlized version available =
at:<br>http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-unknown-msg-04<br>=
<br>A diff from the previous version is available =
at:<br>http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dhc-dhcpv6-unknown-ms=
g-04<br><br><br>Please note that it may take a couple of minutes from =
the time of submission<br>until the htmlized version and diff are =
available at tools.ietf.org.<br><br>Internet-Drafts are also available =
by anonymous FTP =
at:<br>ftp://ftp.ietf.org/internet-drafts/<br><br>________________________=
_______________________<br>dhcwg mailing =
list<br>dhcwg@ietf.org<br>https://www.ietf.org/mailman/listinfo/dhcwg<br><=
/div></blockquote></div><br></body></html>=

--Apple-Mail-18-835507709--

From sunqi.csnet.thu@gmail.com  Sun Dec 15 20:33:23 2013
Return-Path: <sunqi.csnet.thu@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE2FA1AE2AF for <dhcwg@ietfa.amsl.com>; Sun, 15 Dec 2013 20:33:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z86f1jNOm-qd for <dhcwg@ietfa.amsl.com>; Sun, 15 Dec 2013 20:33:19 -0800 (PST)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 16D111AE075 for <dhcwg@ietf.org>; Sun, 15 Dec 2013 20:33:19 -0800 (PST)
Received: by mail-pa0-f51.google.com with SMTP id fa1so2420414pad.38 for <dhcwg@ietf.org>; Sun, 15 Dec 2013 20:33:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:mime-version:content-type:subject:date:in-reply-to:to :references:message-id; bh=gI49ZmrERSAoIwuwX9J+SLUDDt++P30JdfUPaiS96ho=; b=m3F5I03e6abr7/cdqWxJEE4jtX97s60Q7h8ISU82l57UBnzx/k8iaI9Qesw5xU3cKz eGz1/Wlac5xyIJmxVNNrSICzqjy8luxwvOniwsep6whgmIGyiCYubJbO0vRRhrjdsOSc 9VeF6szXZ4dUbTu5ZU4yTnSUEOjkuyMLsYDzO8nmBA645csaaE0rv8HWYQMemTSD34g2 xZ5YY7FcB769q4eS6r1CnI0Q5IOIocQVviFSHRs4R1VDNUGZ+j9sZQLDsd3GRbSmJTqU m7TgVq3xo3oLo9IbI+psjgwAu8V7dlZJRCNlfRIHO6e/wqOWd5qXmMj1ILhgfC4r44o9 eX0A==
X-Received: by 10.66.137.7 with SMTP id qe7mr17628075pab.40.1387168398585; Sun, 15 Dec 2013 20:33:18 -0800 (PST)
Received: from [192.168.199.122] ([166.111.68.231]) by mx.google.com with ESMTPSA id gv10sm22815736pbd.0.2013.12.15.20.33.15 for <dhcwg@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 15 Dec 2013 20:33:18 -0800 (PST)
From: Qi Sun <sunqi.csnet.thu@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-21-839298455
Date: Mon, 16 Dec 2013 12:33:11 +0800
In-Reply-To: <E60FC26B-8075-46AB-B61A-EBB37FE9A509@gmail.com>
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>
References: <20131216032537.25601.52596.idtracker@ietfa.amsl.com> <E60FC26B-8075-46AB-B61A-EBB37FE9A509@gmail.com>
Message-Id: <EF458E73-4FC6-4FB0-A5B9-7974210615E4@gmail.com>
X-Mailer: Apple Mail (2.1085)
Subject: [dhcwg] Request for review on draft-ietf-dhc-dhcpv6-unknown-msg-04.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 16 Dec 2013 04:33:23 -0000

--Apple-Mail-21-839298455
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


Dear all,
=20
Please can you review draft-ietf-dhc-dhcpv6-unknown-msg-04 to see if =
this version has addressed your concerns.=20
Many thanks!

Best Regards,
Qi=20


On 2013-12-16, at =E4=B8=8A=E5=8D=8811:30, Qi Sun wrote:

> Dear all,
>=20
> We have updated the draft-ietf-dhc-dhcpv6-unknown-msg. Major changes =
are:=20
>=20
> 1) Update the Sec 3 (Problem Statement)
> 2) Rename the Sec 4.1 to "A Valid Message for Constructing a New =
Relay-forward Message" to avoid the confusion about what 'valid' is for.
> 3) Reword the definition to the 'valid' message and the subsequent =
paragraph about unknown messages targeting at the relay agent.
> 4) Choose "toward" among "toward/towards/to" when describing the =
relaying direction.
> 5) Use the pre-RFC5378 boilerplate.
> 6) Correct some nits.
>=20
> Thanks a lot for your inputs during the WGLC.=20
>=20
> Best Regards,
> Qi
>=20
>=20
> Begin forwarded message:
>=20
>> From: internet-drafts@ietf.org
>> Date: 2013=E5=B9=B412=E6=9C=8816=E6=97=A5 =
=E4=B8=8A=E5=8D=8811=E6=97=B625=E5=88=8637=E7=A7=92=E6=A0=BC=E6=9E=97=E5=B0=
=BC=E6=B2=BB=E6=A0=87=E5=87=86=E6=97=B6=E9=97=B4+0800
>> To: i-d-announce@ietf.org
>> Cc: dhcwg@ietf.org
>> Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv6-unknown-msg-04.txt
>>=20
>>=20
>> 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.
>>=20
>> 	Title           : Handling Unknown DHCPv6 Messages
>> 	Author(s)       : Yong Cui
>>                          Qi Sun
>>                          Ted Lemon
>> 	Filename        : draft-ietf-dhc-dhcpv6-unknown-msg-04.txt
>> 	Pages           : 6
>> 	Date            : 2013-12-15
>>=20
>> Abstract:
>>   DHCPv6 is not specific about handling messages with unknown types.
>>   This memo describes the problems and defines how a DHCPv6 server,
>>   client or relay agent should behave when receiving unknown DHCPv6
>>   messages.  This document updates RFC3315.
>>=20
>>=20
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-unknown-msg
>>=20
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-unknown-msg-04
>>=20
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dhc-dhcpv6-unknown-msg-04=

>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of =
submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>=20
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>=20
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www.ietf.org/mailman/listinfo/dhcwg
>=20


--Apple-Mail-21-839298455
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Heiti SC'; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: 'Heiti SC'; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: =
normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: =
0px; -webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Heiti SC'; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
'Heiti SC'; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div>Dear =
all,</div><div>&nbsp;</div><div>Please can you review =
draft-ietf-dhc-dhcpv6-unknown-msg-04&nbsp;to see if this version has =
addressed your concerns.&nbsp;</div><div>Many =
thanks!</div><div><br></div><div>Best =
Regards,</div>Qi&nbsp;<br><br></div></span></div></span></div></span></spa=
n>
</div>
<br><div><div>On 2013-12-16, at =E4=B8=8A=E5=8D=8811:30, Qi Sun =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><div><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: 'Heiti SC'; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: 'Heiti SC'; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; font-family: 'Heiti SC'; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; font-family: 'Heiti SC'; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><!--?xml version=3D"1.0" =
encoding=3D"UTF-8"?-->

<span class=3D"Apple-style-span" style=3D"font-family: Arial; ">Dear =
all,</span><div style=3D"font-family: Arial; "><br></div><div =
style=3D"font-family: Arial; ">We have updated =
the&nbsp;draft-ietf-dhc-dhcpv6-unknown-msg. Major changes =
are:&nbsp;</div><div style=3D"font-family: Arial; "><br></div><div =
xmlns=3D"http://www.w3.org/1999/xhtml" style=3D"font-family: Arial; ">1) =
Update the Sec 3 (Problem Statement)</div><div =
xmlns=3D"http://www.w3.org/1999/xhtml" style=3D"font-family: Arial; ">2) =
Rename the Sec 4.1 to "A Valid Message for Constructing a New =
Relay-forward Message" to avoid the confusion about what 'valid' is =
for.</div><div xmlns=3D"http://www.w3.org/1999/xhtml" =
style=3D"font-family: Arial; ">3) Reword the definition to the 'valid' =
message and the subsequent paragraph about unknown messages targeting at =
the relay agent.</div><div xmlns=3D"http://www.w3.org/1999/xhtml" =
style=3D"font-family: Arial; ">4) Choose "toward" among =
"toward/towards/to" when describing the relaying direction.</div><div =
xmlns=3D"http://www.w3.org/1999/xhtml" style=3D"font-family: Arial; ">5) =
Use the&nbsp;pre-RFC5378 boilerplate.</div><div style=3D"font-family: =
Arial; ">6) Correct some nits.<br></div><div style=3D"font-family: =
Arial; "><br></div><div style=3D"font-family: Arial; ">Thanks a lot for =
your inputs during the WGLC.&nbsp;</div><div style=3D"font-family: =
Arial; "><br></div><div style=3D"font-family: Arial; ">Best =
Regards,</div><div style=3D"font-family: Arial; =
">Qi</div><br></div></span></div></span></div></span></span>
</div>
<div><br><div>Begin forwarded message:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>From: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><a =
href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a><br><=
/span></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1);"><b>Date: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;">2013=E5=B9=B412=E6=9C=8816=E6=97=A5 =
=E4=B8=8A=E5=8D=8811=E6=97=B625=E5=88=8637=E7=A7=92=E6=A0=BC=E6=9E=97=E5=B0=
=BC=E6=B2=BB=E6=A0=87=E5=87=86=E6=97=B6=E9=97=B4+0800<br></span></div><div=
 style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>To: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><a =
href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a><br></span>=
</div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Cc: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><a =
href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</a><br></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Subject: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><b>[dhcwg] I-D =
Action: =
draft-ietf-dhc-dhcpv6-unknown-msg-04.txt</b><br></span></div><br><div><br>=
A New Internet-Draft is available from the on-line Internet-Drafts =
directories.<br> This draft is a work item of the Dynamic Host =
Configuration Working Group of the IETF.<br><br><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Title =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Handling =
Unknown DHCPv6 Messages<br><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Author(s) =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Yong Cui<br> =
&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;&nbs=
p;Qi Sun<br> =
&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;&nbs=
p;Ted Lemon<br><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Filename &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
draft-ietf-dhc-dhcpv6-unknown-msg-04.txt<br><span class=3D"Apple-tab-span"=
 style=3D"white-space:pre">	</span>Pages =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: 6<br><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Date =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
2013-12-15<br><br>Abstract:<br> &nbsp;&nbsp;DHCPv6 is not specific about =
handling messages with unknown types.<br> &nbsp;&nbsp;This memo =
describes the problems and defines how a DHCPv6 server,<br> =
&nbsp;&nbsp;client or relay agent should behave when receiving unknown =
DHCPv6<br> &nbsp;&nbsp;messages. &nbsp;This document updates =
RFC3315.<br><br><br>The IETF datatracker status page for this draft =
is:<br><a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-unknown-msg=
">https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv6-unknown-msg</a><b=
r><br>There's also a htmlized version available at:<br><a =
href=3D"http://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-unknown-msg-04">h=
ttp://tools.ietf.org/html/draft-ietf-dhc-dhcpv6-unknown-msg-04</a><br><br>=
A diff from the previous version is available at:<br><a =
href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dhc-dhcpv6-unknown-m=
sg-04">http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dhc-dhcpv6-unknown-ms=
g-04</a><br><br><br>Please note that it may take a couple of minutes =
from the time of submission<br>until the htmlized version and diff are =
available at tools.ietf.org.<br><br>Internet-Drafts are also available =
by anonymous FTP =
at:<br>ftp://ftp.ietf.org/internet-drafts/<br><br>________________________=
_______________________<br>dhcwg mailing =
list<br>dhcwg@ietf.org<br>https://www.ietf.org/mailman/listinfo/dhcwg<br><=
/div></blockquote></div><br></div></blockquote></div><br></body></html>=

--Apple-Mail-21-839298455--

From simon.perreault@viagenie.ca  Mon Dec 16 06:40:33 2013
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87ED61ADFFA for <dhcwg@ietfa.amsl.com>; Mon, 16 Dec 2013 06:40:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level: 
X-Spam-Status: No, score=-2.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m4vjVbfZzYkA for <dhcwg@ietfa.amsl.com>; Mon, 16 Dec 2013 06:40:32 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id EE0471ADFF2 for <dhcwg@ietf.org>; Mon, 16 Dec 2013 06:40:31 -0800 (PST)
Received: from porto.nomis80.org (ringo.viagenie.ca [206.123.31.67]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 1D9C34002A for <dhcwg@ietf.org>; Mon, 16 Dec 2013 09:40:31 -0500 (EST)
Message-ID: <52AF10DE.9020106@viagenie.ca>
Date: Mon, 16 Dec 2013 09:40:30 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <489D13FBFA9B3E41812EA89F188F018E1ADE84D3@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADE84D3@xmb-rcd-x04.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [dhcwg] Results of WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 16 Dec 2013 14:40:33 -0000

Le 2013-12-14 10:10, Bernie Volz (volz) a écrit :
> WGLC on the related draft-ietf-dhc-v4configuration-03 is in progress

Is this true? I can't find the announcement, and the datatracker doesn't 
show the draft as being in WGLC...

Thanks,
Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

From tomasz.mrugalski@gmail.com  Mon Dec 16 06:58:07 2013
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EADE1AE32E for <dhcwg@ietfa.amsl.com>; Mon, 16 Dec 2013 06:58:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XykNfZMsGFqZ for <dhcwg@ietfa.amsl.com>; Mon, 16 Dec 2013 06:58:05 -0800 (PST)
Received: from mail-bk0-x22d.google.com (mail-bk0-x22d.google.com [IPv6:2a00:1450:4008:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 746FE1ADFDC for <dhcwg@ietf.org>; Mon, 16 Dec 2013 06:58:05 -0800 (PST)
Received: by mail-bk0-f45.google.com with SMTP id mx13so2372083bkb.18 for <dhcwg@ietf.org>; Mon, 16 Dec 2013 06:58:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=FmMEaM8tucqEOYR0quS+qSX5A/+f+OWY/UUFMDbixLE=; b=YR84nkf/eC44jEfXEuZ533yXo5wDss3V4XdncVyDlShuNiHzAnACCxy6y4FU0WBXVc otgfyQERHXGQ5qFS8DZMNI+6F5TtJVQWt1fhnD50HWyYPabisXjEXM058RSfBH9xokOq 3HLeeAx8AYzLG1BDnwq7qnxp2rD0U1gTyDtWtt9dzWFX50W83A6SjXswPLZ46wpDO1Jo Hixfkk1K08Yv3Nu+zuNyQ6o++ycHgnKlHLkaWTRWtRcAJDBTFcqeNZ7nTS/T64aJEGND DIuQ+4d77E5BhHoXZE1usqzgTD/oohNw1Kkn6ALyXep3DDHjvK/PtxtGRzaPC9SX2GjY re9Q==
X-Received: by 10.204.173.69 with SMTP id o5mr562232bkz.74.1387205884222; Mon, 16 Dec 2013 06:58:04 -0800 (PST)
Received: from ?IPv6:2001:470:6061:0:f66d:4ff:fe96:58f2? ([2001:470:6061:0:f66d:4ff:fe96:58f2]) by mx.google.com with ESMTPSA id dg4sm10756650bkc.10.2013.12.16.06.58.02 for <dhcwg@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Dec 2013 06:58:03 -0800 (PST)
Message-ID: <52AF14EE.7020107@gmail.com>
Date: Mon, 16 Dec 2013 15:57:50 +0100
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <489D13FBFA9B3E41812EA89F188F018E1ADE84D3@xmb-rcd-x04.cisco.com> <52AF10DE.9020106@viagenie.ca>
In-Reply-To: <52AF10DE.9020106@viagenie.ca>
X-Enigmail-Version: 1.5.2
X-TagToolbar-Keys: D20131216155750802
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Subject: Re: [dhcwg] Results of WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 16 Dec 2013 14:58:07 -0000

On 16.12.2013 15:40, Simon Perreault wrote:
> Le 2013-12-14 10:10, Bernie Volz (volz) a écrit :
>> WGLC on the related draft-ietf-dhc-v4configuration-03 is in progress
> 
> Is this true? I can't find the announcement, and the datatracker doesn't
> show the draft as being in WGLC...
No, that was a mistake. Bernie and I exchanged preliminary WGLC
announcement text, but due to the discussion about dhcpv4-over-dhcpv6 we
still haven't sent it out. So no - there is no WGLC on v4configuration
yet, but there likely will be in the next couple days.
It will be long enough so people who take holiday + new year vacation
will be able to get back and post their comments when they get back in
January.

Tomek


From jiangsheng@huawei.com  Mon Dec 16 17:02:32 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AF391ADFBD for <dhcwg@ietfa.amsl.com>; Mon, 16 Dec 2013 17:02:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.738
X-Spam-Level: 
X-Spam-Status: No, score=-4.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z1I7bGNU03w0 for <dhcwg@ietfa.amsl.com>; Mon, 16 Dec 2013 17:02:30 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 22BDB1ADFC5 for <dhcwg@ietf.org>; Mon, 16 Dec 2013 17:02:28 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BBM65965; Tue, 17 Dec 2013 01:02:27 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 17 Dec 2013 01:02:02 +0000
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 17 Dec 2013 01:02:26 +0000
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.51]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0158.001; Tue, 17 Dec 2013 09:02:22 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Qi Sun <sunqi.csnet.thu@gmail.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] Request for review on draft-ietf-dhc-dhcpv6-unknown-msg-04.txt
Thread-Index: AQHO+hf7TXXY3uQ/gUq0zggzz582BppXkqHQ
Date: Tue, 17 Dec 2013 01:02:21 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923ADC841F@nkgeml512-mbx.china.huawei.com>
References: <20131216032537.25601.52596.idtracker@ietfa.amsl.com> <E60FC26B-8075-46AB-B61A-EBB37FE9A509@gmail.com> <EF458E73-4FC6-4FB0-A5B9-7974210615E4@gmail.com>
In-Reply-To: <EF458E73-4FC6-4FB0-A5B9-7974210615E4@gmail.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: multipart/alternative; boundary="_000_5D36713D8A4E7348A7E10DF7437A4B923ADC841Fnkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [dhcwg] Request for review on	draft-ietf-dhc-dhcpv6-unknown-msg-04.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 17 Dec 2013 01:02:32 -0000

--_000_5D36713D8A4E7348A7E10DF7437A4B923ADC841Fnkgeml512mbxchi_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGksIGF1dGhvcnMsDQoNClRoYW5rcyBmb3IgYWRkcmVzc2luZyBteSBjb21tZW50cy4gVGhpcyB2
ZXJzaW9uIGxvb2tzIGdvb2QgZm9yIG1lLg0KDQpSZWdhcmRzLA0KDQpTaGVuZw0KDQpGcm9tOiBk
aGN3ZyBbbWFpbHRvOmRoY3dnLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBRaSBTdW4N
ClNlbnQ6IE1vbmRheSwgRGVjZW1iZXIgMTYsIDIwMTMgMTI6MzMgUE0NClRvOiBkaGN3Z0BpZXRm
Lm9yZyBXRw0KU3ViamVjdDogW2RoY3dnXSBSZXF1ZXN0IGZvciByZXZpZXcgb24gZHJhZnQtaWV0
Zi1kaGMtZGhjcHY2LXVua25vd24tbXNnLTA0LnR4dA0KDQoNCkRlYXIgYWxsLA0KDQpQbGVhc2Ug
Y2FuIHlvdSByZXZpZXcgZHJhZnQtaWV0Zi1kaGMtZGhjcHY2LXVua25vd24tbXNnLTA0IHRvIHNl
ZSBpZiB0aGlzIHZlcnNpb24gaGFzIGFkZHJlc3NlZCB5b3VyIGNvbmNlcm5zLg0KTWFueSB0aGFu
a3MhDQoNCkJlc3QgUmVnYXJkcywNClFpDQoNCk9uIDIwMTMtMTItMTYsIGF0IOS4iuWNiDExOjMw
LCBRaSBTdW4gd3JvdGU6DQoNCg0KRGVhciBhbGwsDQoNCldlIGhhdmUgdXBkYXRlZCB0aGUgZHJh
ZnQtaWV0Zi1kaGMtZGhjcHY2LXVua25vd24tbXNnLiBNYWpvciBjaGFuZ2VzIGFyZToNCg0KMSkg
VXBkYXRlIHRoZSBTZWMgMyAoUHJvYmxlbSBTdGF0ZW1lbnQpDQoyKSBSZW5hbWUgdGhlIFNlYyA0
LjEgdG8gIkEgVmFsaWQgTWVzc2FnZSBmb3IgQ29uc3RydWN0aW5nIGEgTmV3IFJlbGF5LWZvcndh
cmQgTWVzc2FnZSIgdG8gYXZvaWQgdGhlIGNvbmZ1c2lvbiBhYm91dCB3aGF0ICd2YWxpZCcgaXMg
Zm9yLg0KMykgUmV3b3JkIHRoZSBkZWZpbml0aW9uIHRvIHRoZSAndmFsaWQnIG1lc3NhZ2UgYW5k
IHRoZSBzdWJzZXF1ZW50IHBhcmFncmFwaCBhYm91dCB1bmtub3duIG1lc3NhZ2VzIHRhcmdldGlu
ZyBhdCB0aGUgcmVsYXkgYWdlbnQuDQo0KSBDaG9vc2UgInRvd2FyZCIgYW1vbmcgInRvd2FyZC90
b3dhcmRzL3RvIiB3aGVuIGRlc2NyaWJpbmcgdGhlIHJlbGF5aW5nIGRpcmVjdGlvbi4NCjUpIFVz
ZSB0aGUgcHJlLVJGQzUzNzggYm9pbGVycGxhdGUuDQo2KSBDb3JyZWN0IHNvbWUgbml0cy4NCg0K
VGhhbmtzIGEgbG90IGZvciB5b3VyIGlucHV0cyBkdXJpbmcgdGhlIFdHTEMuDQoNCkJlc3QgUmVn
YXJkcywNClFpDQoNCg0KQmVnaW4gZm9yd2FyZGVkIG1lc3NhZ2U6DQoNCg0KRnJvbTogaW50ZXJu
ZXQtZHJhZnRzQGlldGYub3JnPG1haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmc+DQpEYXRl
OiAyMDEz5bm0MTLmnIgxNuaXpSDkuIrljYgxMeaXtjI15YiGMzfnp5LmoLzmnpflsLzmsrvmoIfl
h4bml7bpl7QrMDgwMA0KVG86IGktZC1hbm5vdW5jZUBpZXRmLm9yZzxtYWlsdG86aS1kLWFubm91
bmNlQGlldGYub3JnPg0KQ2M6IGRoY3dnQGlldGYub3JnPG1haWx0bzpkaGN3Z0BpZXRmLm9yZz4N
ClN1YmplY3Q6IFtkaGN3Z10gSS1EIEFjdGlvbjogZHJhZnQtaWV0Zi1kaGMtZGhjcHY2LXVua25v
d24tbXNnLTA0LnR4dA0KDQoNCkEgTmV3IEludGVybmV0LURyYWZ0IGlzIGF2YWlsYWJsZSBmcm9t
IHRoZSBvbi1saW5lIEludGVybmV0LURyYWZ0cyBkaXJlY3Rvcmllcy4NClRoaXMgZHJhZnQgaXMg
YSB3b3JrIGl0ZW0gb2YgdGhlIER5bmFtaWMgSG9zdCBDb25maWd1cmF0aW9uIFdvcmtpbmcgR3Jv
dXAgb2YgdGhlIElFVEYuDQoNCiAgIFRpdGxlICAgICAgICAgICA6IEhhbmRsaW5nIFVua25vd24g
REhDUHY2IE1lc3NhZ2VzDQogICBBdXRob3IocykgICAgICAgOiBZb25nIEN1aQ0KICAgICAgICAg
ICAgICAgICAgICAgICAgIFFpIFN1bg0KICAgICAgICAgICAgICAgICAgICAgICAgIFRlZCBMZW1v
bg0KICAgRmlsZW5hbWUgICAgICAgIDogZHJhZnQtaWV0Zi1kaGMtZGhjcHY2LXVua25vd24tbXNn
LTA0LnR4dA0KICAgUGFnZXMgICAgICAgICAgIDogNg0KICAgRGF0ZSAgICAgICAgICAgIDogMjAx
My0xMi0xNQ0KDQpBYnN0cmFjdDoNCiAgREhDUHY2IGlzIG5vdCBzcGVjaWZpYyBhYm91dCBoYW5k
bGluZyBtZXNzYWdlcyB3aXRoIHVua25vd24gdHlwZXMuDQogIFRoaXMgbWVtbyBkZXNjcmliZXMg
dGhlIHByb2JsZW1zIGFuZCBkZWZpbmVzIGhvdyBhIERIQ1B2NiBzZXJ2ZXIsDQogIGNsaWVudCBv
ciByZWxheSBhZ2VudCBzaG91bGQgYmVoYXZlIHdoZW4gcmVjZWl2aW5nIHVua25vd24gREhDUHY2
DQogIG1lc3NhZ2VzLiAgVGhpcyBkb2N1bWVudCB1cGRhdGVzIFJGQzMzMTUuDQoNCg0KVGhlIElF
VEYgZGF0YXRyYWNrZXIgc3RhdHVzIHBhZ2UgZm9yIHRoaXMgZHJhZnQgaXM6DQpodHRwczovL2Rh
dGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLWRoYy1kaGNwdjYtdW5rbm93bi1tc2cN
Cg0KVGhlcmUncyBhbHNvIGEgaHRtbGl6ZWQgdmVyc2lvbiBhdmFpbGFibGUgYXQ6DQpodHRwOi8v
dG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWRoYy1kaGNwdjYtdW5rbm93bi1tc2ctMDQN
Cg0KQSBkaWZmIGZyb20gdGhlIHByZXZpb3VzIHZlcnNpb24gaXMgYXZhaWxhYmxlIGF0Og0KaHR0
cDovL3d3dy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtaWV0Zi1kaGMtZGhjcHY2LXVua25v
d24tbXNnLTA0DQoNCg0KUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBt
aW51dGVzIGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbg0KdW50aWwgdGhlIGh0bWxpemVkIHZl
cnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZy4NCg0KSW50ZXJu
ZXQtRHJhZnRzIGFyZSBhbHNvIGF2YWlsYWJsZSBieSBhbm9ueW1vdXMgRlRQIGF0Og0KZnRwOi8v
ZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy8NCg0KX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCmRoY3dnIG1haWxpbmcgbGlzdA0KZGhjd2dAaWV0Zi5v
cmc8bWFpbHRvOmRoY3dnQGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9kaGN3Zw0KDQoNCg==

--_000_5D36713D8A4E7348A7E10DF7437A4B923ADC841Fnkgeml512mbxchi_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTIgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk65a6L5L2TOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0K
QGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQg
NSAzIDUgNCA2IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglw
YW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5
OiJcQOWui+S9kyI7DQoJcGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpAZm9udC1mYWNl
DQoJe2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9
DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJIZWl0aSBTQyI7DQoJcGFub3NlLTE6MCAwIDAg
MCAwIDAgMCAwIDAgMDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxp
Lk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206
LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OuWui+S9kzt9DQphOmxp
bmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpi
bHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5
cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7
DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLk1zb0FjZXRhdGUsIGxpLk1zb0FjZXRh
dGUsIGRpdi5Nc29BY2V0YXRlDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUt
bGluazoi5om55rOo5qGG5paH5pysIENoYXIiOw0KCW1hcmdpbjowY207DQoJbWFyZ2luLWJvdHRv
bTouMDAwMXB0Ow0KCWZvbnQtc2l6ZTo5LjBwdDsNCglmb250LWZhbWlseTrlrovkvZM7fQ0Kc3Bh
bi5hcHBsZS1zdHlsZS1zcGFuDQoJe21zby1zdHlsZS1uYW1lOmFwcGxlLXN0eWxlLXNwYW47fQ0K
c3Bhbi5hcHBsZS10YWItc3Bhbg0KCXttc28tc3R5bGUtbmFtZTphcHBsZS10YWItc3Bhbjt9DQpz
cGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250
LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5D
aGFyDQoJe21zby1zdHlsZS1uYW1lOiLmibnms6jmoYbmlofmnKwgQ2hhciI7DQoJbXNvLXN0eWxl
LXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOuaJueazqOahhuaWh+acrDsNCglmb250LWZh
bWlseTrlrovkvZM7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9u
bHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIu
MHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA5MC4wcHQgNzIuMHB0IDkwLjBwdDt9DQpkaXYu
V29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBn
dGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIx
MDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpz
aGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIg
Lz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxh
bmc9IlpILUNOIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRT
ZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkhpLCBhdXRob3JzLDxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90Oztjb2xvcjojMUY0OTdEIj5UaGFua3MgZm9yIGFkZHJlc3NpbmcgbXkgY29tbWVudHMu
IFRoaXMgdmVyc2lvbiBsb29rcyBnb29kIGZvciBtZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTox
MC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29s
b3I6IzFGNDk3RCI+UmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMx
RjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+
U2hlbmc8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0
OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0KPGRp
diBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRp
bmc6My4wcHQgMGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9t
YSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9t
YSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gZGhjd2cgW21haWx0bzpkaGN3Zy1ib3Vu
Y2VzQGlldGYub3JnXQ0KPGI+T24gQmVoYWxmIE9mIDwvYj5RaSBTdW48YnI+DQo8Yj5TZW50Ojwv
Yj4gTW9uZGF5LCBEZWNlbWJlciAxNiwgMjAxMyAxMjozMyBQTTxicj4NCjxiPlRvOjwvYj4gZGhj
d2dAaWV0Zi5vcmcgV0c8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gW2RoY3dnXSBSZXF1ZXN0IGZvciBy
ZXZpZXcgb24gZHJhZnQtaWV0Zi1kaGMtZGhjcHY2LXVua25vd24tbXNnLTA0LnR4dDxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTMuNXB0O2ZvbnQtZmFtaWx5OiZx
dW90O0hlaXRpIFNDJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj5EZWFyIGFs
bCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMy41cHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7SGVpdGkgU0MmcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDs7Y29sb3I6YmxhY2siPiZu
YnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEzLjVwdDtmb250LWZh
bWlseTomcXVvdDtIZWl0aSBTQyZxdW90OywmcXVvdDtzZXJpZiZxdW90Oztjb2xvcjpibGFjayI+
UGxlYXNlIGNhbiB5b3UgcmV2aWV3IGRyYWZ0LWlldGYtZGhjLWRoY3B2Ni11bmtub3duLW1zZy0w
NCZuYnNwO3RvIHNlZSBpZiB0aGlzIHZlcnNpb24gaGFzIGFkZHJlc3NlZCB5b3VyIGNvbmNlcm5z
LiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEzLjVwdDtmb250
LWZhbWlseTomcXVvdDtIZWl0aSBTQyZxdW90OywmcXVvdDtzZXJpZiZxdW90Oztjb2xvcjpibGFj
ayI+TWFueSB0aGFua3MhPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTMu
NXB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlaXRpIFNDJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7O2Nv
bG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTox
My41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVpdGkgU0MmcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDs7
Y29sb3I6YmxhY2siPkJlc3QgUmVnYXJkcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEzLjVwdCI+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTMuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0hl
aXRpIFNDJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj5RaSZuYnNwOzxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiPk9uIDIwMTMtMTItMTYsIGF0IDwvc3Bhbj7kuIrljYg8c3BhbiBsYW5nPSJFTi1VUyI+MTE6
MzAsIFFpIFN1biB3cm90ZTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48YnI+DQo8YnI+DQo8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGNsYXNzPSJhcHBsZS1zdHlsZS1zcGFuIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMy41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RGVhciBhbGwsPC9zcGFuPjwvc3Bhbj48c3BhbiBsYW5n
PSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMy41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVpdGkg
U0MmcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6
ZToxMy41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90OyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTMuNXB0
O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPldl
IGhhdmUgdXBkYXRlZCB0aGUmbmJzcDtkcmFmdC1pZXRmLWRoYy1kaGNwdjYtdW5rbm93bi1tc2cu
IE1ham9yIGNoYW5nZXMgYXJlOiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9u
dC1zaXplOjEzLjVwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZTox
My41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
OyI+MSkgVXBkYXRlIHRoZSBTZWMgMyAoUHJvYmxlbSBTdGF0ZW1lbnQpPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTMuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjIpIFJlbmFtZSB0aGUgU2VjIDQuMSB0byAmcXVv
dDtBIFZhbGlkIE1lc3NhZ2UgZm9yIENvbnN0cnVjdGluZyBhIE5ldyBSZWxheS1mb3J3YXJkIE1l
c3NhZ2UmcXVvdDsgdG8gYXZvaWQgdGhlIGNvbmZ1c2lvbiBhYm91dCB3aGF0ICd2YWxpZCcgaXMg
Zm9yLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEzLjVwdDtmb250LWZh
bWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4zKSBSZXdvcmQg
dGhlIGRlZmluaXRpb24gdG8gdGhlICd2YWxpZCcgbWVzc2FnZSBhbmQgdGhlIHN1YnNlcXVlbnQg
cGFyYWdyYXBoIGFib3V0IHVua25vd24gbWVzc2FnZXMgdGFyZ2V0aW5nIGF0IHRoZSByZWxheSBh
Z2VudC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMy41cHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+NCkgQ2hvb3Nl
ICZxdW90O3Rvd2FyZCZxdW90OyBhbW9uZyAmcXVvdDt0b3dhcmQvdG93YXJkcy90byZxdW90OyB3
aGVuIGRlc2NyaWJpbmcgdGhlIHJlbGF5aW5nIGRpcmVjdGlvbi48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMy41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+NSkgVXNlIHRoZSZuYnNwO3ByZS1SRkM1Mzc4IGJvaWxl
cnBsYXRlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEzLjVwdDtmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij42KSBDb3Jy
ZWN0IHNvbWUgbml0cy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMy41
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTMuNXB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPlRoYW5rcyBh
IGxvdCBmb3IgeW91ciBpbnB1dHMgZHVyaW5nIHRoZSBXR0xDLiZuYnNwOzxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEzLjVwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMy41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90OyI+QmVzdCBSZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1zaXplOjEzLjVwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVv
dDtzYW5zLXNlcmlmJnF1b3Q7Ij5RaTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTMu
NXB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlaXRpIFNDJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7Ij48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIj5CZWdpbiBmb3J3YXJkZWQgbWVzc2FnZTo8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48YnI+
DQo8YnI+DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PGI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTMuNXB0O2ZvbnQtZmFt
aWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOg0K
PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMy41cHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxh
IGhyZWY9Im1haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmciPmludGVybmV0LWRyYWZ0c0Bp
ZXRmLm9yZzwvYT48L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjEzLjVwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2Em
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RGF0ZToNCjwvc3Bhbj48L2I+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTMuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZl
dGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4yMDEzPC9zcGFuPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTMuNXB0Ij7lubQ8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTMuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7Ij4xMjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEzLjVwdCI+
5pyIPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEzLjVwdDtmb250
LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+MTY8
L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMy41cHQiPuaXpTwvc3Bhbj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEzLjVwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90OyI+DQo8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMy41
cHQiPuS4iuWNiDwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMy41
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDsiPjExPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTMuNXB0Ij7ml7Y8L3NwYW4+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTMuNXB0O2ZvbnQtZmFtaWx5OiZxdW90
O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4yNTwvc3Bhbj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEzLjVwdCI+5YiGPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1zaXplOjEzLjVwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssJnF1
b3Q7c2Fucy1zZXJpZiZxdW90OyI+Mzc8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMy41
cHQiPuenkuagvOael+WwvOayu+agh+WHhuaXtumXtDwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMy41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiYjNDM7MDgwMDwvc3Bhbj48c3BhbiBsYW5nPSJFTi1V
UyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PGI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTMuNXB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5UbzoN
Cjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTMuNXB0O2Zv
bnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij48
YSBocmVmPSJtYWlsdG86aS1kLWFubm91bmNlQGlldGYub3JnIj5pLWQtYW5ub3VuY2VAaWV0Zi5v
cmc8L2E+PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImZvbnQtc2l6ZToxMy41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkNjOg0KPC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMy41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxhIGhyZWY9Im1haWx0bzpkaGN3Z0BpZXRmLm9y
ZyI+ZGhjd2dAaWV0Zi5vcmc8L2E+PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMy41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
SGVsdmV0aWNhJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPlN1YmplY3Q6IFtkaGN3Z10g
SS1EIEFjdGlvbjogZHJhZnQtaWV0Zi1kaGMtZGhjcHY2LXVua25vd24tbXNnLTA0LnR4dDwvc3Bh
bj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyI+PGJyPg0KQSBOZXcgSW50ZXJuZXQtRHJhZnQgaXMgYXZhaWxhYmxlIGZyb20gdGhlIG9uLWxp
bmUgSW50ZXJuZXQtRHJhZnRzIGRpcmVjdG9yaWVzLjxicj4NClRoaXMgZHJhZnQgaXMgYSB3b3Jr
IGl0ZW0gb2YgdGhlIER5bmFtaWMgSG9zdCBDb25maWd1cmF0aW9uIFdvcmtpbmcgR3JvdXAgb2Yg
dGhlIElFVEYuPGJyPg0KPGJyPg0KPHNwYW4gY2xhc3M9ImFwcGxlLXRhYi1zcGFuIj4mbmJzcDsm
bmJzcDsgPC9zcGFuPlRpdGxlICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOzogSGFuZGxpbmcgVW5rbm93biBESENQdjYgTWVzc2FnZXM8
YnI+DQo8c3BhbiBjbGFzcz0iYXBwbGUtdGFiLXNwYW4iPiZuYnNwOyZuYnNwOyA8L3NwYW4+QXV0
aG9yKHMpICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzogWW9uZyBDdWk8YnI+
DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtRaSBTdW48YnI+DQombmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtUZWQgTGVtb248YnI+DQo8c3BhbiBjbGFzcz0i
YXBwbGUtdGFiLXNwYW4iPiZuYnNwOyZuYnNwOyA8L3NwYW4+RmlsZW5hbWUgJm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7OiBkcmFmdC1pZXRmLWRoYy1kaGNwdjYtdW5r
bm93bi1tc2ctMDQudHh0PGJyPg0KPHNwYW4gY2xhc3M9ImFwcGxlLXRhYi1zcGFuIj4mbmJzcDsm
bmJzcDsgPC9zcGFuPlBhZ2VzICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOzogNjxicj4NCjxzcGFuIGNsYXNzPSJhcHBsZS10YWItc3Bh
biI+Jm5ic3A7Jm5ic3A7IDwvc3Bhbj5EYXRlICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzogMjAxMy0xMi0xNTxicj4NCjxi
cj4NCkFic3RyYWN0Ojxicj4NCiZuYnNwOyZuYnNwO0RIQ1B2NiBpcyBub3Qgc3BlY2lmaWMgYWJv
dXQgaGFuZGxpbmcgbWVzc2FnZXMgd2l0aCB1bmtub3duIHR5cGVzLjxicj4NCiZuYnNwOyZuYnNw
O1RoaXMgbWVtbyBkZXNjcmliZXMgdGhlIHByb2JsZW1zIGFuZCBkZWZpbmVzIGhvdyBhIERIQ1B2
NiBzZXJ2ZXIsPGJyPg0KJm5ic3A7Jm5ic3A7Y2xpZW50IG9yIHJlbGF5IGFnZW50IHNob3VsZCBi
ZWhhdmUgd2hlbiByZWNlaXZpbmcgdW5rbm93biBESENQdjY8YnI+DQombmJzcDsmbmJzcDttZXNz
YWdlcy4gJm5ic3A7VGhpcyBkb2N1bWVudCB1cGRhdGVzIFJGQzMzMTUuPGJyPg0KPGJyPg0KPGJy
Pg0KVGhlIElFVEYgZGF0YXRyYWNrZXIgc3RhdHVzIHBhZ2UgZm9yIHRoaXMgZHJhZnQgaXM6PGJy
Pg0KPGEgaHJlZj0iaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1k
aGMtZGhjcHY2LXVua25vd24tbXNnIj5odHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9k
cmFmdC1pZXRmLWRoYy1kaGNwdjYtdW5rbm93bi1tc2c8L2E+PGJyPg0KPGJyPg0KVGhlcmUncyBh
bHNvIGEgaHRtbGl6ZWQgdmVyc2lvbiBhdmFpbGFibGUgYXQ6PGJyPg0KPGEgaHJlZj0iaHR0cDov
L3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1kaGMtZGhjcHY2LXVua25vd24tbXNnLTA0
Ij5odHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWRoYy1kaGNwdjYtdW5rbm93
bi1tc2ctMDQ8L2E+PGJyPg0KPGJyPg0KQSBkaWZmIGZyb20gdGhlIHByZXZpb3VzIHZlcnNpb24g
aXMgYXZhaWxhYmxlIGF0Ojxicj4NCjxhIGhyZWY9Imh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlm
Zj91cmwyPWRyYWZ0LWlldGYtZGhjLWRoY3B2Ni11bmtub3duLW1zZy0wNCI+aHR0cDovL3d3dy5p
ZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtaWV0Zi1kaGMtZGhjcHY2LXVua25vd24tbXNnLTA0
PC9hPjxicj4NCjxicj4NCjxicj4NClBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRha2UgYSBjb3Vw
bGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Npb248YnI+DQp1bnRpbCB0aGUg
aHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3Jn
Ljxicj4NCjxicj4NCkludGVybmV0LURyYWZ0cyBhcmUgYWxzbyBhdmFpbGFibGUgYnkgYW5vbnlt
b3VzIEZUUCBhdDo8YnI+DQo8YSBocmVmPSJmdHA6Ly9mdHAuaWV0Zi5vcmcvaW50ZXJuZXQtZHJh
ZnRzLyI+ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy88L2E+PGJyPg0KPGJyPg0K
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQpkaGN3
ZyBtYWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJtYWlsdG86ZGhjd2dAaWV0Zi5vcmciPmRoY3dn
QGlldGYub3JnPC9hPjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vZGhjd2ciPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZGhj
d2c8L2E+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8
L2h0bWw+DQo=

--_000_5D36713D8A4E7348A7E10DF7437A4B923ADC841Fnkgeml512mbxchi_--

From volz@cisco.com  Thu Dec 19 06:59:23 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FABF1ADF9C for <dhcwg@ietfa.amsl.com>; Thu, 19 Dec 2013 06:59:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.039
X-Spam-Level: 
X-Spam-Status: No, score=-15.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rcSeQeK_yJ-W for <dhcwg@ietfa.amsl.com>; Thu, 19 Dec 2013 06:59:21 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id B3EB71ADFB4 for <dhcwg@ietf.org>; Thu, 19 Dec 2013 06:59:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5367; q=dns/txt; s=iport; t=1387465158; x=1388674758; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=Rb6aAKLpqlEXZkQxxOuL8V+UIlXsd/P54bkGDvzM8bM=; b=iBoD6i7H54soGMZ2swT3Ek4Gt02l3KMVZ3ZlVyad+CcqmoYOFhe23brR KbAcNIBQdDeKNY3DgHK3rE32IXtQdUDIHqV+T6wEDMvYWktsoSp6sn2Ba +6Z3/XfxuLwJEqNDVaD8xWwL6/Cjg2SfiJRDMI8VcN4m8eVOpv8FFFnav o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwFAL4Is1KtJXHA/2dsb2JhbABZgws4Twa5KoETFnSCJQEBAQMBAQEBGh00EAcEAgEIEQMBAQELFAkHIQYLFAkIAQEECgkIAYdnAwkICAXDTA2GfBeMf4E7BwEBHjgGgx2BEwSUM4F4gxuLKoU6gW2BPoFoCRci
X-IronPort-AV: E=Sophos;i="4.95,512,1384300800"; d="scan'208";a="289656278"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-9.cisco.com with ESMTP; 19 Dec 2013 14:59:17 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id rBJExHET025375 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Thu, 19 Dec 2013 14:59:17 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0123.003; Thu, 19 Dec 2013 08:59:17 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
Thread-Index: Ac7xD0TQ86CV+plkQwGdrBXmDcXNywLuutdw
Date: Thu, 19 Dec 2013 14:59:16 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1ADF3041@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADD09A3@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADD09A3@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.241.164]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 19 Dec 2013 14:59:23 -0000

While we are now technically past the respond by date, I will make one last=
 plea for comments regarding adopting this as a WG item.

We did receive responses from two non-authors, but I don't really feel that=
 is strong enough to consider adopting this. No one objected, so that does =
weigh in favor of adopting it.

Because I am a co-author, I will leave it for Tomek to decide whether this =
document should be adopted. I will ask him to hold off announcing results u=
ntil Monday, December 23 (so send your response by Sunday).

Again, if you haven't responded and have a few minutes, please consider whe=
ther the WG should adopt or not. We did adopt the DHCPv6 version of this wo=
rk, so it would not be a stretch to adopt for DHCPv4 as the motivation is i=
dentical.

- Bernie

-----Original Message-----
From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Wednesday, December 04, 2013 11:47 AM
To: Kim Kinnear (kkinnear); dhcwg@ietf.org
Subject: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequer=
y-02 - Respond by Dec 18

Hi all:

This is a WG Call for Adoption for http://tools.ietf.org/html/draft-kinnear=
-dhc-dhcpv4-active-leasequery-02. This call is being initiated to determine=
 whether there is WG consensus to adopt this work as DHC WG item. Please st=
ate whether or not you're in favor of the adoption by replying to this mail=
. If you are not in favor, please also state your objections in your respon=
se. This adoption call will complete on December 18, 2013.

This call is being initiated because during the call for adoption for draft=
-raghuvanshi-dhc-dhcpv6-active-leasequery-00, which was just adopted, sever=
al people asked about the related DHCPv4 work. Kim republished the DHCPv4 d=
raft (with minor updates) as it had expired a while ago. So, we are seeking=
 input as to whether the WG should now also work on the DHCPv4 version of a=
ctive leasequery, given that the DHCPv6 version was adopted.

Regards,
Tomek & Bernie

-----Original Message-----
From: Kim Kinnear (kkinnear)=20
Sent: Wednesday, December 04, 2013 11:25 AM
To: dhcwg@ietf.org
Cc: Kim Kinnear (kkinnear); Bernie Volz (volz); Tomek Mrugalski
Subject: New Version Notification for draft-kinnear-dhc-dhcpv4-active-lease=
query-02.txt


Folks,

During the adoption discussion about DHCPv6 Active Leasequery there was som=
e discussion about having a corresponding DHCPv4 Active Leasequery capabili=
ty.  If there is sufficient interest in a DHCPv4 Active Leasequery capabili=
ty to parallel the DHCPv6 capability that was adopted as a DHC WG work item=
 recently, then we can decide whether or not we want to have two drafts mov=
ing toward two RFC's, or combine them into one draft.

But the first question is whether or not there is sufficient interest in ha=
ving a DHCPv4 Active Leasequery capability at all!

In order to help decide this question, I have updated the existing
DHCPv4 Active Leasequery draft from a couple of years ago, and resubmitted =
it as an individual submission -- as recommended by Bernie and Tomek.

Below you can find the information on how to find this new draft.

Regards -- Kim


Begin forwarded message:

> From: <internet-drafts@ietf.org>
> Subject: New Version Notification for=20
> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
> Date: December 4, 2013 10:01:03 AM EST
> To: Bernie Volz <volz@cisco.com>, Mark Stapp <mjs@cisco.com>, Kim=20
> Kinnear <kkinnear@cisco.com>, Neil Russell <neil.e.russell@gmail.com>
>=20
>=20
> A new version of I-D,=20
> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
> has been successfully submitted by Kim Kinnear and posted to the IETF=20
> repository.
>=20
> Filename:	 draft-kinnear-dhc-dhcpv4-active-leasequery
> Revision:	 02
> Title:		 Active DHCPv4 Lease Query
> Creation date:	 2013-12-04
> Group:		 Individual Submission
> Number of pages: 22
> URL:             http://www.ietf.org/internet-drafts/draft-kinnear-dhc-dh=
cpv4-active-leasequery-02.txt
> Status:          http://datatracker.ietf.org/doc/draft-kinnear-dhc-dhcpv4=
-active-leasequery
> Htmlized:        http://tools.ietf.org/html/draft-kinnear-dhc-dhcpv4-acti=
ve-leasequery-02
> Diff:            http://www.ietf.org/rfcdiff?url2=3Ddraft-kinnear-dhc-dhc=
pv4-active-leasequery-02
>=20
> Abstract:
>   The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has been
>   extended with a Leasequery capability that allows a client to request
>   information about DHCPv4 bindings.  That mechanism is limited to
>   queries for individual bindings.  In some situations individual
>   binding queries may not be efficient, or even possible.  In addition,
>   continuous update of an external client with Leasequery data is
>   sometimes desired. This document expands on the DHCPv4 Leasequery
>   protocol, and allows for active transfer of near real-time DHCPv4
>   address binding information data via TCP.
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of=20
> submission until the htmlized version and diff are available at tools.iet=
f.org.
>=20
> The IETF Secretariat
>=20

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

From kkinnear@cisco.com  Thu Dec 19 07:32:33 2013
Return-Path: <kkinnear@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 537991ADFC4 for <dhcwg@ietfa.amsl.com>; Thu, 19 Dec 2013 07:32:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hsB2RddgE5z9 for <dhcwg@ietfa.amsl.com>; Thu, 19 Dec 2013 07:32:30 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) by ietfa.amsl.com (Postfix) with ESMTP id B49361ADFBA for <dhcwg@ietf.org>; Thu, 19 Dec 2013 07:32:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6437; q=dns/txt; s=iport; t=1387467149; x=1388676749; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=CKS6xWMO0ef0gNPdovu14nq2wtsbEvYxNqhDLvnN/pk=; b=GDtO9eb4mQwgEzk6lRNdvypvjZGq6phi/QwgQSVEgwiqL0hQAnq/WVdQ 1jk2qfaDw9jqRwnHhF4lgv1E+kaUKL0jxM3a43URiBcnZ7eKWrS6CNC5/ OKwVkfX2uhZD45/Krlhc747FKA7oONZLFRfCaSNzdQZHiGiyhURfMyeYK I=;
X-IronPort-AV: E=Sophos;i="4.95,512,1384300800";  d="scan'208";a="7919898"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-1.cisco.com with ESMTP; 19 Dec 2013 15:32:26 +0000
Received: from [161.44.65.110] ([161.44.65.110]) (authenticated bits=0) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id rBJFWOAF029495 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 19 Dec 2013 15:32:25 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Kim Kinnear <kkinnear@cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADF3041@xmb-rcd-x04.cisco.com>
Date: Thu, 19 Dec 2013 10:32:24 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A517C82-84E5-47A7-A5B9-337DB408859B@cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADD09A3@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADF3041@xmb-rcd-x04.cisco.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
X-Mailer: Apple Mail (2.1510)
X-Authenticated-User: kkinnear
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Kim Kinnear <kkinnear@cisco.com>
Subject: Re: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 19 Dec 2013 15:32:33 -0000

Bernie,

I'm confused.  I count responses from 6 non-authors on this work:

Ted Lemon 		12/9/13 4:59pm
Sheng Jiang 		12/10/13 1:13pm
Mathias Samelson 	12/10/13 4:56pm
Dushyant Raghuvanshi 	12/9/13 11:29pm
Darpan Malhotra 	12/12/13 1:31pm
Deepak Kukrety 		12/9/13 11:45pm

Now, my mail reader didn't gather all of these together for me easily, =
and
I don't know why.  But I do see them in my email.  The times above are
the times in my email reader (EST), for reference.

I'm not saying that we need to adopt this or not, but it seems to me
that we should be counting the folks that responded.

Thanks -- Kim


On Dec 19, 2013, at 9:59 AM, "Bernie Volz (volz)" <volz@cisco.com> =
wrote:

> While we are now technically past the respond by date, I will make one =
last plea for comments regarding adopting this as a WG item.
>=20
> We did receive responses from two non-authors, but I don't really feel =
that is strong enough to consider adopting this. No one objected, so =
that does weigh in favor of adopting it.
>=20
> Because I am a co-author, I will leave it for Tomek to decide whether =
this document should be adopted. I will ask him to hold off announcing =
results until Monday, December 23 (so send your response by Sunday).
>=20
> Again, if you haven't responded and have a few minutes, please =
consider whether the WG should adopt or not. We did adopt the DHCPv6 =
version of this work, so it would not be a stretch to adopt for DHCPv4 =
as the motivation is identical.
>=20
> - Bernie
>=20
> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz =
(volz)
> Sent: Wednesday, December 04, 2013 11:47 AM
> To: Kim Kinnear (kkinnear); dhcwg@ietf.org
> Subject: [dhcwg] WG Adoption Call =
draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
>=20
> Hi all:
>=20
> This is a WG Call for Adoption for =
http://tools.ietf.org/html/draft-kinnear-dhc-dhcpv4-active-leasequery-02. =
This call is being initiated to determine whether there is WG consensus =
to adopt this work as DHC WG item. Please state whether or not you're in =
favor of the adoption by replying to this mail. If you are not in favor, =
please also state your objections in your response. This adoption call =
will complete on December 18, 2013.
>=20
> This call is being initiated because during the call for adoption for =
draft-raghuvanshi-dhc-dhcpv6-active-leasequery-00, which was just =
adopted, several people asked about the related DHCPv4 work. Kim =
republished the DHCPv4 draft (with minor updates) as it had expired a =
while ago. So, we are seeking input as to whether the WG should now also =
work on the DHCPv4 version of active leasequery, given that the DHCPv6 =
version was adopted.
>=20
> Regards,
> Tomek & Bernie
>=20
> -----Original Message-----
> From: Kim Kinnear (kkinnear)=20
> Sent: Wednesday, December 04, 2013 11:25 AM
> To: dhcwg@ietf.org
> Cc: Kim Kinnear (kkinnear); Bernie Volz (volz); Tomek Mrugalski
> Subject: New Version Notification for =
draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
>=20
>=20
> Folks,
>=20
> During the adoption discussion about DHCPv6 Active Leasequery there =
was some discussion about having a corresponding DHCPv4 Active =
Leasequery capability.  If there is sufficient interest in a DHCPv4 =
Active Leasequery capability to parallel the DHCPv6 capability that was =
adopted as a DHC WG work item recently, then we can decide whether or =
not we want to have two drafts moving toward two RFC's, or combine them =
into one draft.
>=20
> But the first question is whether or not there is sufficient interest =
in having a DHCPv4 Active Leasequery capability at all!
>=20
> In order to help decide this question, I have updated the existing
> DHCPv4 Active Leasequery draft from a couple of years ago, and =
resubmitted it as an individual submission -- as recommended by Bernie =
and Tomek.
>=20
> Below you can find the information on how to find this new draft.
>=20
> Regards -- Kim
>=20
>=20
> Begin forwarded message:
>=20
>> From: <internet-drafts@ietf.org>
>> Subject: New Version Notification for=20
>> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
>> Date: December 4, 2013 10:01:03 AM EST
>> To: Bernie Volz <volz@cisco.com>, Mark Stapp <mjs@cisco.com>, Kim=20
>> Kinnear <kkinnear@cisco.com>, Neil Russell <neil.e.russell@gmail.com>
>>=20
>>=20
>> A new version of I-D,=20
>> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
>> has been successfully submitted by Kim Kinnear and posted to the IETF=20=

>> repository.
>>=20
>> Filename:	 draft-kinnear-dhc-dhcpv4-active-leasequery
>> Revision:	 02
>> Title:		 Active DHCPv4 Lease Query
>> Creation date:	 2013-12-04
>> Group:		 Individual Submission
>> Number of pages: 22
>> URL:             =
http://www.ietf.org/internet-drafts/draft-kinnear-dhc-dhcpv4-active-leaseq=
uery-02.txt
>> Status:          =
http://datatracker.ietf.org/doc/draft-kinnear-dhc-dhcpv4-active-leasequery=

>> Htmlized:        =
http://tools.ietf.org/html/draft-kinnear-dhc-dhcpv4-active-leasequery-02
>> Diff:            =
http://www.ietf.org/rfcdiff?url2=3Ddraft-kinnear-dhc-dhcpv4-active-leasequ=
ery-02
>>=20
>> Abstract:
>>  The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has been
>>  extended with a Leasequery capability that allows a client to =
request
>>  information about DHCPv4 bindings.  That mechanism is limited to
>>  queries for individual bindings.  In some situations individual
>>  binding queries may not be efficient, or even possible.  In =
addition,
>>  continuous update of an external client with Leasequery data is
>>  sometimes desired. This document expands on the DHCPv4 Leasequery
>>  protocol, and allows for active transfer of near real-time DHCPv4
>>  address binding information data via TCP.
>>=20
>>=20
>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of=20
>> submission until the htmlized version and diff are available at =
tools.ietf.org.
>>=20
>> The IETF Secretariat
>>=20
>=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 volz@cisco.com  Thu Dec 19 07:48:46 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69BC41AE00A for <dhcwg@ietfa.amsl.com>; Thu, 19 Dec 2013 07:48:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.039
X-Spam-Level: 
X-Spam-Status: No, score=-15.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EEwrMjKlmbuU for <dhcwg@ietfa.amsl.com>; Thu, 19 Dec 2013 07:48:44 -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 BDB8D1ADFDA for <dhcwg@ietf.org>; Thu, 19 Dec 2013 07:48:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7570; q=dns/txt; s=iport; t=1387468122; x=1388677722; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=S93AwKBdR8OOmPGRPBD6mtUg05UbLj06dhHJtGK8DaQ=; b=c//AkQwkSVsqubXHUNvmpFpJhZrpSn4i0C0fq/2cch4HtKgKxIVEsInj bSU+TkYuy55xEF0bbIs7roA5Us6LTsSeViDqi+sNBUQnfcpUn5VAer8ER LrDe9vtbADOFXIf1SUf7gyyR6JJZOgts5buCaqbu3/qnZXr5oqPI0QyLY M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FADQUs1KtJXHA/2dsb2JhbABZgws4SQYGuSmBFBZ0giUBAQEDAQEBARodNAsFBwQCAQgRAwEBAQsUCQchBgsUCQgBAQQKBAUIAYdnAwkICAXDaw2GfBeMf4ExCgYCAR4xBwaDHYETAQOUM4F4gxuLKoU6gW2BPoFoQg
X-IronPort-AV: E=Sophos;i="4.95,512,1384300800"; d="scan'208";a="292476545"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-1.cisco.com with ESMTP; 19 Dec 2013 15:48:41 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id rBJFmf8n010399 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <dhcwg@ietf.org>; Thu, 19 Dec 2013 15:48:41 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.232]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0123.003; Thu, 19 Dec 2013 09:48:41 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Kim Kinnear (kkinnear)" <kkinnear@cisco.com>
Thread-Topic: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
Thread-Index: Ac7xD0TQ86CV+plkQwGdrBXmDcXNywLuutdwAA3njgAADI6OEA==
Date: Thu, 19 Dec 2013 15:48:40 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1ADF3287@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADD09A3@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADF3041@xmb-rcd-x04.cisco.com> <2A517C82-84E5-47A7-A5B9-337DB408859B@cisco.com>
In-Reply-To: <2A517C82-84E5-47A7-A5B9-337DB408859B@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.241.164]
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] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 19 Dec 2013 15:48:46 -0000

Kim & DHC WG ...

I excluded Dushyant, Darpan, and Deepak (they aren't authors of the dhcpv4 =
work, but of the dhcpv6 - except for Darpan but he works with us at Cisco -=
 and I didn't feel that this longer answer was required but I guess I shoul=
d have include it). They are certainly all valid opinions, but there is som=
e "conflict of interest".

I did miss Sheng's response - not sure why I missed it when I had Outlook s=
earch for the draft name in DHC WG email.

In the future I should avoid putting counts in as "rough consensus" is not =
about "counting votes". And should just state that we are interesting in ge=
tting 'more' opinions.

Anyway, let's see what happens ... as I'm leaving the decision up to Tomek =
(and he should do his own analysis) and we'll see if there is any more inte=
rest expressed.

- Bernie

-----Original Message-----
From: Kim Kinnear (kkinnear)=20
Sent: Thursday, December 19, 2013 10:32 AM
To: Bernie Volz (volz)
Cc: Kim Kinnear (kkinnear); dhcwg@ietf.org
Subject: Re: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-lease=
query-02 - Respond by Dec 18


Bernie,

I'm confused.  I count responses from 6 non-authors on this work:

Ted Lemon 		12/9/13 4:59pm
Sheng Jiang 		12/10/13 1:13pm
Mathias Samelson 	12/10/13 4:56pm
Dushyant Raghuvanshi 	12/9/13 11:29pm
Darpan Malhotra 	12/12/13 1:31pm
Deepak Kukrety 		12/9/13 11:45pm

Now, my mail reader didn't gather all of these together for me easily, and =
I don't know why.  But I do see them in my email.  The times above are the =
times in my email reader (EST), for reference.

I'm not saying that we need to adopt this or not, but it seems to me that w=
e should be counting the folks that responded.

Thanks -- Kim


On Dec 19, 2013, at 9:59 AM, "Bernie Volz (volz)" <volz@cisco.com> wrote:

> While we are now technically past the respond by date, I will make one la=
st plea for comments regarding adopting this as a WG item.
>=20
> We did receive responses from two non-authors, but I don't really feel th=
at is strong enough to consider adopting this. No one objected, so that doe=
s weigh in favor of adopting it.
>=20
> Because I am a co-author, I will leave it for Tomek to decide whether thi=
s document should be adopted. I will ask him to hold off announcing results=
 until Monday, December 23 (so send your response by Sunday).
>=20
> Again, if you haven't responded and have a few minutes, please consider w=
hether the WG should adopt or not. We did adopt the DHCPv6 version of this =
work, so it would not be a stretch to adopt for DHCPv4 as the motivation is=
 identical.
>=20
> - Bernie
>=20
> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz=20
> (volz)
> Sent: Wednesday, December 04, 2013 11:47 AM
> To: Kim Kinnear (kkinnear); dhcwg@ietf.org
> Subject: [dhcwg] WG Adoption Call=20
> draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
>=20
> Hi all:
>=20
> This is a WG Call for Adoption for http://tools.ietf.org/html/draft-kinne=
ar-dhc-dhcpv4-active-leasequery-02. This call is being initiated to determi=
ne whether there is WG consensus to adopt this work as DHC WG item. Please =
state whether or not you're in favor of the adoption by replying to this ma=
il. If you are not in favor, please also state your objections in your resp=
onse. This adoption call will complete on December 18, 2013.
>=20
> This call is being initiated because during the call for adoption for dra=
ft-raghuvanshi-dhc-dhcpv6-active-leasequery-00, which was just adopted, sev=
eral people asked about the related DHCPv4 work. Kim republished the DHCPv4=
 draft (with minor updates) as it had expired a while ago. So, we are seeki=
ng input as to whether the WG should now also work on the DHCPv4 version of=
 active leasequery, given that the DHCPv6 version was adopted.
>=20
> Regards,
> Tomek & Bernie
>=20
> -----Original Message-----
> From: Kim Kinnear (kkinnear)
> Sent: Wednesday, December 04, 2013 11:25 AM
> To: dhcwg@ietf.org
> Cc: Kim Kinnear (kkinnear); Bernie Volz (volz); Tomek Mrugalski
> Subject: New Version Notification for=20
> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
>=20
>=20
> Folks,
>=20
> During the adoption discussion about DHCPv6 Active Leasequery there was s=
ome discussion about having a corresponding DHCPv4 Active Leasequery capabi=
lity.  If there is sufficient interest in a DHCPv4 Active Leasequery capabi=
lity to parallel the DHCPv6 capability that was adopted as a DHC WG work it=
em recently, then we can decide whether or not we want to have two drafts m=
oving toward two RFC's, or combine them into one draft.
>=20
> But the first question is whether or not there is sufficient interest in =
having a DHCPv4 Active Leasequery capability at all!
>=20
> In order to help decide this question, I have updated the existing
> DHCPv4 Active Leasequery draft from a couple of years ago, and resubmitte=
d it as an individual submission -- as recommended by Bernie and Tomek.
>=20
> Below you can find the information on how to find this new draft.
>=20
> Regards -- Kim
>=20
>=20
> Begin forwarded message:
>=20
>> From: <internet-drafts@ietf.org>
>> Subject: New Version Notification for=20
>> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
>> Date: December 4, 2013 10:01:03 AM EST
>> To: Bernie Volz <volz@cisco.com>, Mark Stapp <mjs@cisco.com>, Kim=20
>> Kinnear <kkinnear@cisco.com>, Neil Russell <neil.e.russell@gmail.com>
>>=20
>>=20
>> A new version of I-D,
>> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
>> has been successfully submitted by Kim Kinnear and posted to the IETF=20
>> repository.
>>=20
>> Filename:	 draft-kinnear-dhc-dhcpv4-active-leasequery
>> Revision:	 02
>> Title:		 Active DHCPv4 Lease Query
>> Creation date:	 2013-12-04
>> Group:		 Individual Submission
>> Number of pages: 22
>> URL:             http://www.ietf.org/internet-drafts/draft-kinnear-dhc-d=
hcpv4-active-leasequery-02.txt
>> Status:          http://datatracker.ietf.org/doc/draft-kinnear-dhc-dhcpv=
4-active-leasequery
>> Htmlized:        http://tools.ietf.org/html/draft-kinnear-dhc-dhcpv4-act=
ive-leasequery-02
>> Diff:            http://www.ietf.org/rfcdiff?url2=3Ddraft-kinnear-dhc-dh=
cpv4-active-leasequery-02
>>=20
>> Abstract:
>>  The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has been =20
>> extended with a Leasequery capability that allows a client to request =20
>> information about DHCPv4 bindings.  That mechanism is limited to =20
>> queries for individual bindings.  In some situations individual =20
>> binding queries may not be efficient, or even possible.  In addition, =20
>> continuous update of an external client with Leasequery data is =20
>> sometimes desired. This document expands on the DHCPv4 Leasequery =20
>> protocol, and allows for active transfer of near real-time DHCPv4 =20
>> address binding information data via TCP.
>>=20
>>=20
>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of=20
>> submission until the htmlized version and diff are available at tools.ie=
tf.org.
>>=20
>> The IETF Secretariat
>>=20
>=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 Mathias.Samuelson@nominum.com  Sat Dec 21 01:29:42 2013
Return-Path: <Mathias.Samuelson@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B8BB1A1F74 for <dhcwg@ietfa.amsl.com>; Sat, 21 Dec 2013 01:29:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rLbRSb37yvqo for <dhcwg@ietfa.amsl.com>; Sat, 21 Dec 2013 01:29:39 -0800 (PST)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id 0F3931A1EF9 for <dhcwg@ietf.org>; Sat, 21 Dec 2013 01:29:38 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKUrVfgGbdwIzRJl9WdH8iNaFK84iUD0MR@postini.com; Sat, 21 Dec 2013 01:29:37 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 44EF01B82AE for <dhcwg@ietf.org>; Sat, 21 Dec 2013 01:29:36 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 0C6BC190043; Sat, 21 Dec 2013 01:29:36 -0800 (PST)
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.03.0158.001; Sat, 21 Dec 2013 01:29:30 -0800
From: Mathias Samuelson <Mathias.Samuelson@nominum.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Thread-Topic: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
Thread-Index: Ac7xD0TQ86CV+plkQwGdrBXmDcXNywLuutdwAGoAxQA=
Date: Sat, 21 Dec 2013 09:29:29 +0000
Message-ID: <AA6DAB18-159B-41B5-99F2-DA2707371B39@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADD09A3@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADF3041@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADF3041@xmb-rcd-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <39038E4C1336304AAFC88E4224E405E8@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Dec 2013 09:29:42 -0000

Bernie, all,

I just wanted to provide some context as for why I think that this work sho=
uld be adopted.

Most of the CSP customers I work with either operate IPv4 only, or dual-sta=
ck IPv4 / IPv6 networks or is progressing in that direction. Native IPv6 an=
d more specifically IPv6-only networks seem to be an outliner *at this poin=
t*.

What I also see is that all of our CSP customers using our DHCP server for =
dual-stack service use the same DHCP servers for both stacks. It would be i=
nteresting to hear if others have a different experience, but at least with=
 the data I have the CSPs want to run DHCPv4 and DHCPv6 in the same servers=
.

>From that point of view alone, I think it makes a lot of sense to adopt the=
 active leasequery work for both DHCPv4 and DHCPv6, or not at all (but I th=
ink we should do this work because there is value in having a standardized =
way of getting a stream of lease binding updates from the DHCP servers).

Someone who will find a use for active leasequery is likely to find a use f=
or it for both stacks. The corollary would be that I think that doing this =
work for just one or the other of DHCPv4 and DHCPv6 is going to be relative=
ly useless in reality. :-)

Taking my product management hat on, I think it would also suck to be force=
d into inconsistent feature sets for DHCPv4 and DHCPv6. ;-)

Mathias

On Dec 19, 2013, at 3:59 PM, Bernie Volz (volz) <volz@cisco.com> wrote:

> While we are now technically past the respond by date, I will make one la=
st plea for comments regarding adopting this as a WG item.
>=20
> We did receive responses from two non-authors, but I don't really feel th=
at is strong enough to consider adopting this. No one objected, so that doe=
s weigh in favor of adopting it.
>=20
> Because I am a co-author, I will leave it for Tomek to decide whether thi=
s document should be adopted. I will ask him to hold off announcing results=
 until Monday, December 23 (so send your response by Sunday).
>=20
> Again, if you haven't responded and have a few minutes, please consider w=
hether the WG should adopt or not. We did adopt the DHCPv6 version of this =
work, so it would not be a stretch to adopt for DHCPv4 as the motivation is=
 identical.
>=20
> - Bernie
>=20
> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (vol=
z)
> Sent: Wednesday, December 04, 2013 11:47 AM
> To: Kim Kinnear (kkinnear); dhcwg@ietf.org
> Subject: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequ=
ery-02 - Respond by Dec 18
>=20
> Hi all:
>=20
> This is a WG Call for Adoption for http://tools.ietf.org/html/draft-kinne=
ar-dhc-dhcpv4-active-leasequery-02. This call is being initiated to determi=
ne whether there is WG consensus to adopt this work as DHC WG item. Please =
state whether or not you're in favor of the adoption by replying to this ma=
il. If you are not in favor, please also state your objections in your resp=
onse. This adoption call will complete on December 18, 2013.
>=20
> This call is being initiated because during the call for adoption for dra=
ft-raghuvanshi-dhc-dhcpv6-active-leasequery-00, which was just adopted, sev=
eral people asked about the related DHCPv4 work. Kim republished the DHCPv4=
 draft (with minor updates) as it had expired a while ago. So, we are seeki=
ng input as to whether the WG should now also work on the DHCPv4 version of=
 active leasequery, given that the DHCPv6 version was adopted.
>=20
> Regards,
> Tomek & Bernie
>=20
> -----Original Message-----
> From: Kim Kinnear (kkinnear)=20
> Sent: Wednesday, December 04, 2013 11:25 AM
> To: dhcwg@ietf.org
> Cc: Kim Kinnear (kkinnear); Bernie Volz (volz); Tomek Mrugalski
> Subject: New Version Notification for draft-kinnear-dhc-dhcpv4-active-lea=
sequery-02.txt
>=20
>=20
> Folks,
>=20
> During the adoption discussion about DHCPv6 Active Leasequery there was s=
ome discussion about having a corresponding DHCPv4 Active Leasequery capabi=
lity.  If there is sufficient interest in a DHCPv4 Active Leasequery capabi=
lity to parallel the DHCPv6 capability that was adopted as a DHC WG work it=
em recently, then we can decide whether or not we want to have two drafts m=
oving toward two RFC's, or combine them into one draft.
>=20
> But the first question is whether or not there is sufficient interest in =
having a DHCPv4 Active Leasequery capability at all!
>=20
> In order to help decide this question, I have updated the existing
> DHCPv4 Active Leasequery draft from a couple of years ago, and resubmitte=
d it as an individual submission -- as recommended by Bernie and Tomek.
>=20
> Below you can find the information on how to find this new draft.
>=20
> Regards -- Kim
>=20
>=20
> Begin forwarded message:
>=20
>> From: <internet-drafts@ietf.org>
>> Subject: New Version Notification for=20
>> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
>> Date: December 4, 2013 10:01:03 AM EST
>> To: Bernie Volz <volz@cisco.com>, Mark Stapp <mjs@cisco.com>, Kim=20
>> Kinnear <kkinnear@cisco.com>, Neil Russell <neil.e.russell@gmail.com>
>>=20
>>=20
>> A new version of I-D,=20
>> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
>> has been successfully submitted by Kim Kinnear and posted to the IETF=20
>> repository.
>>=20
>> Filename:	 draft-kinnear-dhc-dhcpv4-active-leasequery
>> Revision:	 02
>> Title:		 Active DHCPv4 Lease Query
>> Creation date:	 2013-12-04
>> Group:		 Individual Submission
>> Number of pages: 22
>> URL:             http://www.ietf.org/internet-drafts/draft-kinnear-dhc-d=
hcpv4-active-leasequery-02.txt
>> Status:          http://datatracker.ietf.org/doc/draft-kinnear-dhc-dhcpv=
4-active-leasequery
>> Htmlized:        http://tools.ietf.org/html/draft-kinnear-dhc-dhcpv4-act=
ive-leasequery-02
>> Diff:            http://www.ietf.org/rfcdiff?url2=3Ddraft-kinnear-dhc-dh=
cpv4-active-leasequery-02
>>=20
>> Abstract:
>>  The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has been
>>  extended with a Leasequery capability that allows a client to request
>>  information about DHCPv4 bindings.  That mechanism is limited to
>>  queries for individual bindings.  In some situations individual
>>  binding queries may not be efficient, or even possible.  In addition,
>>  continuous update of an external client with Leasequery data is
>>  sometimes desired. This document expands on the DHCPv4 Leasequery
>>  protocol, and allows for active transfer of near real-time DHCPv4
>>  address binding information data via TCP.
>>=20
>>=20
>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of=20
>> submission until the htmlized version and diff are available at tools.ie=
tf.org.
>>=20
>> The IETF Secretariat
>>=20
>=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

Mathias Samuelson | Sr. Product Manager
mobile: +1.650.491.4193 | office: +1.650.381.6225
Nominum | www.nominum.com | mathias.samuelson@nominum.com


From volz@cisco.com  Sat Dec 21 14:54:27 2013
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B5621AE0D3 for <dhcwg@ietfa.amsl.com>; Sat, 21 Dec 2013 14:54:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Fx75r3zG-mO for <dhcwg@ietfa.amsl.com>; Sat, 21 Dec 2013 14:54:25 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id 321651AE0AB for <dhcwg@ietf.org>; Sat, 21 Dec 2013 14:54:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8714; q=dns/txt; s=iport; t=1387666462; x=1388876062; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=PO43O1I+njgHc1BlNd5IM6oeWppBXNcf7yCy0HmBbdk=; b=YIVH4rxfr5qdQRn4mlF/mouQMQ2OHa5ytqmKMCbvVfHUqUVQlS6aTxj0 nWc1IainPq6nDhc0wBPUkw4o2p3MlSmcdHY3NpHrmLvSAqIAsaJLMHBiW D5EYKPDzqerNOjeqieAGiGYhfha+BFpSLPCI/3VAEqUS0i6c1D3gZnqRQ s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmMFAMYbtlKtJV2b/2dsb2JhbABVA4MLOE8GuT6BEhZ0giUBAQEDAQEBARodDyULBQcCAgIBCBEDAQEBCxQJBxYLBgsUCQgBAQQKBAUIAYdnAwkICAXDfQ2GUhcEjQ6BOwcBAR4hEAcGC4MSgRMElDOBeIMciyqFOoFvgT6BaAkXIg
X-IronPort-AV: E=Sophos;i="4.95,529,1384300800";  d="scan'208";a="8402549"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-6.cisco.com with ESMTP; 21 Dec 2013 22:54:18 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rBLMsJAB008039 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 21 Dec 2013 22:54:19 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.230]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0123.003; Sat, 21 Dec 2013 16:54:18 -0600
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Mathias Samuelson <Mathias.Samuelson@nominum.com>
Thread-Topic: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
Thread-Index: Ac7xD0TQ86CV+plkQwGdrBXmDcXNywLuutdwAGoAxQAACwSOYA==
Date: Sat, 21 Dec 2013 22:54:16 +0000
Message-ID: <489D13FBFA9B3E41812EA89F188F018E1ADFA118@xmb-rcd-x04.cisco.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADD09A3@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADF3041@xmb-rcd-x04.cisco.com> <AA6DAB18-159B-41B5-99F2-DA2707371B39@nominum.com>
In-Reply-To: <AA6DAB18-159B-41B5-99F2-DA2707371B39@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.241.117]
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] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Respond by Dec 18
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Dec 2013 22:54:27 -0000

Yes, I fully agree. It is also why we added the DHCPv6 capability to our se=
rvers after we did DHCPv4 and customers started using it (and as most custo=
mers are still v4 centric, the v4 capability was more important to most).

Another point is that while it certainly is extra work, it is much easier t=
o do it again for the 2nd protocol than first time around, even with the v4=
/v6 differences. And, as this basically extends bulk leasequery, at least m=
uch of the packet processing / building code is already in place. And from =
the draft perspective, the motivation for both are the same.

Thus, the delta to the WG should be fairly small.

(And, when the DHCPv6 failover requirements draft went to the IESG, they we=
re wondering what happened to the V4 failover work ...)

I'm certainly in favor of adopting the v4 work as well. But we need WG part=
icipation to make this a success, hence why I think the response from non-i=
nvolved parties was a bit lower than I would have hoped for.

Perhaps most people don't care either way as there were no objections.

- Bernie

-----Original Message-----
From: Mathias Samuelson [mailto:Mathias.Samuelson@nominum.com]=20
Sent: Saturday, December 21, 2013 4:29 AM
To: Bernie Volz (volz)
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-lease=
query-02 - Respond by Dec 18

Bernie, all,

I just wanted to provide some context as for why I think that this work sho=
uld be adopted.

Most of the CSP customers I work with either operate IPv4 only, or dual-sta=
ck IPv4 / IPv6 networks or is progressing in that direction. Native IPv6 an=
d more specifically IPv6-only networks seem to be an outliner *at this poin=
t*.

What I also see is that all of our CSP customers using our DHCP server for =
dual-stack service use the same DHCP servers for both stacks. It would be i=
nteresting to hear if others have a different experience, but at least with=
 the data I have the CSPs want to run DHCPv4 and DHCPv6 in the same servers=
.

>From that point of view alone, I think it makes a lot of sense to adopt the=
 active leasequery work for both DHCPv4 and DHCPv6, or not at all (but I th=
ink we should do this work because there is value in having a standardized =
way of getting a stream of lease binding updates from the DHCP servers).

Someone who will find a use for active leasequery is likely to find a use f=
or it for both stacks. The corollary would be that I think that doing this =
work for just one or the other of DHCPv4 and DHCPv6 is going to be relative=
ly useless in reality. :-)

Taking my product management hat on, I think it would also suck to be force=
d into inconsistent feature sets for DHCPv4 and DHCPv6. ;-)

Mathias

On Dec 19, 2013, at 3:59 PM, Bernie Volz (volz) <volz@cisco.com> wrote:

> While we are now technically past the respond by date, I will make one la=
st plea for comments regarding adopting this as a WG item.
>=20
> We did receive responses from two non-authors, but I don't really feel th=
at is strong enough to consider adopting this. No one objected, so that doe=
s weigh in favor of adopting it.
>=20
> Because I am a co-author, I will leave it for Tomek to decide whether thi=
s document should be adopted. I will ask him to hold off announcing results=
 until Monday, December 23 (so send your response by Sunday).
>=20
> Again, if you haven't responded and have a few minutes, please consider w=
hether the WG should adopt or not. We did adopt the DHCPv6 version of this =
work, so it would not be a stretch to adopt for DHCPv4 as the motivation is=
 identical.
>=20
> - Bernie
>=20
> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (vol=
z)
> Sent: Wednesday, December 04, 2013 11:47 AM
> To: Kim Kinnear (kkinnear); dhcwg@ietf.org
> Subject: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequ=
ery-02 - Respond by Dec 18
>=20
> Hi all:
>=20
> This is a WG Call for Adoption for http://tools.ietf.org/html/draft-kinne=
ar-dhc-dhcpv4-active-leasequery-02. This call is being initiated to determi=
ne whether there is WG consensus to adopt this work as DHC WG item. Please =
state whether or not you're in favor of the adoption by replying to this ma=
il. If you are not in favor, please also state your objections in your resp=
onse. This adoption call will complete on December 18, 2013.
>=20
> This call is being initiated because during the call for adoption for dra=
ft-raghuvanshi-dhc-dhcpv6-active-leasequery-00, which was just adopted, sev=
eral people asked about the related DHCPv4 work. Kim republished the DHCPv4=
 draft (with minor updates) as it had expired a while ago. So, we are seeki=
ng input as to whether the WG should now also work on the DHCPv4 version of=
 active leasequery, given that the DHCPv6 version was adopted.
>=20
> Regards,
> Tomek & Bernie
>=20
> -----Original Message-----
> From: Kim Kinnear (kkinnear)=20
> Sent: Wednesday, December 04, 2013 11:25 AM
> To: dhcwg@ietf.org
> Cc: Kim Kinnear (kkinnear); Bernie Volz (volz); Tomek Mrugalski
> Subject: New Version Notification for draft-kinnear-dhc-dhcpv4-active-lea=
sequery-02.txt
>=20
>=20
> Folks,
>=20
> During the adoption discussion about DHCPv6 Active Leasequery there was s=
ome discussion about having a corresponding DHCPv4 Active Leasequery capabi=
lity.  If there is sufficient interest in a DHCPv4 Active Leasequery capabi=
lity to parallel the DHCPv6 capability that was adopted as a DHC WG work it=
em recently, then we can decide whether or not we want to have two drafts m=
oving toward two RFC's, or combine them into one draft.
>=20
> But the first question is whether or not there is sufficient interest in =
having a DHCPv4 Active Leasequery capability at all!
>=20
> In order to help decide this question, I have updated the existing
> DHCPv4 Active Leasequery draft from a couple of years ago, and resubmitte=
d it as an individual submission -- as recommended by Bernie and Tomek.
>=20
> Below you can find the information on how to find this new draft.
>=20
> Regards -- Kim
>=20
>=20
> Begin forwarded message:
>=20
>> From: <internet-drafts@ietf.org>
>> Subject: New Version Notification for=20
>> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
>> Date: December 4, 2013 10:01:03 AM EST
>> To: Bernie Volz <volz@cisco.com>, Mark Stapp <mjs@cisco.com>, Kim=20
>> Kinnear <kkinnear@cisco.com>, Neil Russell <neil.e.russell@gmail.com>
>>=20
>>=20
>> A new version of I-D,=20
>> draft-kinnear-dhc-dhcpv4-active-leasequery-02.txt
>> has been successfully submitted by Kim Kinnear and posted to the IETF=20
>> repository.
>>=20
>> Filename:	 draft-kinnear-dhc-dhcpv4-active-leasequery
>> Revision:	 02
>> Title:		 Active DHCPv4 Lease Query
>> Creation date:	 2013-12-04
>> Group:		 Individual Submission
>> Number of pages: 22
>> URL:             http://www.ietf.org/internet-drafts/draft-kinnear-dhc-d=
hcpv4-active-leasequery-02.txt
>> Status:          http://datatracker.ietf.org/doc/draft-kinnear-dhc-dhcpv=
4-active-leasequery
>> Htmlized:        http://tools.ietf.org/html/draft-kinnear-dhc-dhcpv4-act=
ive-leasequery-02
>> Diff:            http://www.ietf.org/rfcdiff?url2=3Ddraft-kinnear-dhc-dh=
cpv4-active-leasequery-02
>>=20
>> Abstract:
>>  The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has been
>>  extended with a Leasequery capability that allows a client to request
>>  information about DHCPv4 bindings.  That mechanism is limited to
>>  queries for individual bindings.  In some situations individual
>>  binding queries may not be efficient, or even possible.  In addition,
>>  continuous update of an external client with Leasequery data is
>>  sometimes desired. This document expands on the DHCPv4 Leasequery
>>  protocol, and allows for active transfer of near real-time DHCPv4
>>  address binding information data via TCP.
>>=20
>>=20
>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of=20
>> submission until the htmlized version and diff are available at tools.ie=
tf.org.
>>=20
>> The IETF Secretariat
>>=20
>=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

Mathias Samuelson | Sr. Product Manager
mobile: +1.650.491.4193 | office: +1.650.381.6225
Nominum | www.nominum.com | mathias.samuelson@nominum.com


From tomasz.mrugalski@gmail.com  Mon Dec 23 03:37:34 2013
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69B511ADFA4 for <dhcwg@ietfa.amsl.com>; Mon, 23 Dec 2013 03:37:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C4KFyV4cvQpB for <dhcwg@ietfa.amsl.com>; Mon, 23 Dec 2013 03:37:33 -0800 (PST)
Received: from mail-ee0-x22b.google.com (mail-ee0-x22b.google.com [IPv6:2a00:1450:4013:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id AC3221ADFA3 for <dhcwg@ietf.org>; Mon, 23 Dec 2013 03:37:32 -0800 (PST)
Received: by mail-ee0-f43.google.com with SMTP id c13so2257403eek.2 for <dhcwg@ietf.org>; Mon, 23 Dec 2013 03:37:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=duD6iOc+ry0/kQc+lC+xu/8GnPqzLMhHKA3loXLC1Yg=; b=jVP31ZSechJBUuYpTnC0rhFtk8WVXwE8EtboX9vtYZgelnCkxzmCiO8IwkZtnENWpq pwVAwnhBq0Guhuw/rvNHc6n4uFhiGSLhoNpNi1jsn0Qf3wr2/Qw6OXB0UdwlMytAnb1u Qrl8lRGLGBaEuybAvp/PHmxW/6Xyn9xIVl4acRqOGkBmFcNfodK2gK5H86B/8W9Sdf2A MPL9PamYKCeRNXCVZBesfobE4DOD07+qCJ5p5rPybu7COB4BKDlRIDcHGDeikmLSsyds W30zEX46EGOqFnk2cso07F+6tJfX2h178P7db7DhUXt+k5aEilU35dMSYhWzuV3oGPxn +B+g==
X-Received: by 10.15.54.72 with SMTP id s48mr20626337eew.3.1387798648887; Mon, 23 Dec 2013 03:37:28 -0800 (PST)
Received: from thomson-osx.local (078088096057.lomza.vectranet.pl. [78.88.96.57]) by mx.google.com with ESMTPSA id g47sm44749497eeo.19.2013.12.23.03.37.27 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 23 Dec 2013 03:37:28 -0800 (PST)
Message-ID: <52B82076.1080007@gmail.com>
Date: Mon, 23 Dec 2013 12:37:26 +0100
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: DHC WG <dhcwg@ietf.org>
References: <489D13FBFA9B3E41812EA89F188F018E1ADD09A3@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1ADD09A3@xmb-rcd-x04.cisco.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: [dhcwg] WG Adoption Call draft-kinnear-dhc-dhcpv4-active-leasequery-02 - Adopted
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 23 Dec 2013 11:37:34 -0000

On 04.12.2013, 17:46, Bernie Volz (volz) wrote:
> Hi all:
> 
> This is a WG Call for Adoption for
> http://tools.ietf.org/html/draft-kinnear-dhc-dhcpv4-active-leasequery-02.
> This call is being initiated to determine whether there is WG
> consensus to adopt this work as DHC WG item. Please state whether or
> not you're in favor of the adoption by replying to this mail. If you
> are not in favor, please also state your objections in your response.
> This adoption call will complete on December 18, 2013.

With my chair hat off, I do not support this work. It is not that I'm
objecting it, either. I would count my vote as abstain. Personally I
thought that having active leasequery standardized for v6 only would be
another (small) incentive to migrate to IPv6. But the reality, as
Mathias nicely described it, is that for the foreseeable future, we will
have v4-only and dual-stack networks and people who intend to deploy
active leasequery will need it for both protocols. So since the v6 draft
is moving forward and the work needed to make its v4 counterpart is
minimal, I suppose it is ok to define the same capability for both
protocols.

With my chair hat on:
As Bernie is co-author of this work, I had to assess this adoption call
on my own. There is support for doing this work, but it is somewhat
smaller than for its v6 counter-part. There were quite a few people
supporting this draft, but many of them were directly or indirectly
involved in the work. There was noone objecting that work.

I made a decision to adopt this work. The draft passed adoption call.
But I wanted to make it clear: the level of support expressed is
disappointing and it will not be sufficient to pass WGLC. If you (the
generic you, I'm addressing all WG participants here) are interested in
moving this work forward, please be more active.

Authors, please upload this draft as WG item.

Tomek

From internet-drafts@ietf.org  Mon Dec 23 09:00:23 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53F0F1AE1C0; Mon, 23 Dec 2013 09:00:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BrOQN_rY-kNi; Mon, 23 Dec 2013 09:00:21 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B5FB51AE1AE; Mon, 23 Dec 2013 09:00:21 -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: 4.90
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131223170021.8675.27325.idtracker@ietfa.amsl.com>
Date: Mon, 23 Dec 2013 09:00:21 -0800
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-option-guidelines-16.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 23 Dec 2013 17:00:23 -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 Group =
of the IETF.

        Title           : Guidelines for Creating New DHCPv6 Options
        Authors         : David W. Hankins
                          Tomek Mrugalski
                          Marcin Siodelski
                          Sheng Jiang
                          Suresh Krishnan
	Filename        : draft-ietf-dhc-option-guidelines-16.txt
	Pages           : 34
	Date            : 2013-12-23

Abstract:
   This document provides guidance to prospective DHCPv6 Option
   developers to help them creating option formats that are easily
   adoptable by existing DHCPv6 software.  It also provides guidelines
   for expert reviewers to evaluate new registrations.  This document
   updates RFC3315.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-option-guidelines/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-option-guidelines-16

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dhc-option-guidelines-16


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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


From tomasz.mrugalski@gmail.com  Mon Dec 23 09:07:31 2013
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A77771AE1C5 for <dhcwg@ietfa.amsl.com>; Mon, 23 Dec 2013 09:07:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KfRUeE1nZREo for <dhcwg@ietfa.amsl.com>; Mon, 23 Dec 2013 09:07:30 -0800 (PST)
Received: from mail-ea0-f169.google.com (mail-ea0-f169.google.com [209.85.215.169]) by ietfa.amsl.com (Postfix) with ESMTP id A182D1AE1B3 for <dhcwg@ietf.org>; Mon, 23 Dec 2013 09:07:29 -0800 (PST)
Received: by mail-ea0-f169.google.com with SMTP id l9so2133265eaj.0 for <dhcwg@ietf.org>; Mon, 23 Dec 2013 09:06:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=0z/siUWG5EPc/qcdr4iZcNtnKMosyssonHM2XdGgGCQ=; b=aF7N+3QjclBIU5ISpVQlD8bZ08RKXLDwObrDf7CVYYqkm9sfVDDTH/BlrI0Qjr57xZ H6yT4tmTCAR3Rri2f64DsGuIZxkHe0kevezVATWZhMYekzQQKhna+XvQSZ3OWgTIDLFI rk2vha7giY5pIA+3epRDNwBm6i6Do5Pt8nHh23HsSxQbaaCCgBOiPh3LkAWvQMKOI/TU trXjVvYmSmmTywXNSxA8UulbUbwbWnuDMC+x4AWGyvnnGCFCsGJQbBH9l94navZ5p1b2 BlwtA8u01vA6iN0XX3LH+iDSe9wbB3EhC5KmAahg2hDSWm1MKTIMVTJehYVESwhuL762 MjnA==
X-Received: by 10.14.4.67 with SMTP id 43mr3698524eei.70.1387818410784; Mon, 23 Dec 2013 09:06:50 -0800 (PST)
Received: from thomson-osx.local (078088096057.lomza.vectranet.pl. [78.88.96.57]) by mx.google.com with ESMTPSA id n1sm47265696eep.20.2013.12.23.09.06.48 for <dhcwg@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 23 Dec 2013 09:06:50 -0800 (PST)
Message-ID: <52B86DA6.8070506@gmail.com>
Date: Mon, 23 Dec 2013 18:06:46 +0100
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <20131223170021.8675.27325.idtracker@ietfa.amsl.com>
In-Reply-To: <20131223170021.8675.27325.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-option-guidelines-16.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 23 Dec 2013 17:07:31 -0000

This is probably the last update. It hopefully addresses the last
outstanding issues raised by IESG: Brian asked to remove NTP as an
example of a service that should be conveyed as an address and Ted had a
couple editorial suggestions.

Merry Christmas (for those who celebrate it), Happy Holidays (for those
who don't) and Happy New Year!

Tomek

On 23.12.2013, 18:00, 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           : Guidelines for Creating New DHCPv6 Options
>         Authors         : David W. Hankins
>                           Tomek Mrugalski
>                           Marcin Siodelski
>                           Sheng Jiang
>                           Suresh Krishnan
> 	Filename        : draft-ietf-dhc-option-guidelines-16.txt
> 	Pages           : 34
> 	Date            : 2013-12-23
> 
> Abstract:
>    This document provides guidance to prospective DHCPv6 Option
>    developers to help them creating option formats that are easily
>    adoptable by existing DHCPv6 software.  It also provides guidelines
>    for expert reviewers to evaluate new registrations.  This document
>    updates RFC3315.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dhc-option-guidelines/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-dhc-option-guidelines-16
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-option-guidelines-16
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
> 


From internet-drafts@ietf.org  Thu Dec 26 11:12:36 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 380BD1AE26F; Thu, 26 Dec 2013 11:12:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k_58movUfH5S; Thu, 26 Dec 2013 11:12:34 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 36CEC1AE009; Thu, 26 Dec 2013 11:12:34 -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: 4.90
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131226191234.15730.77676.idtracker@ietfa.amsl.com>
Date: Thu, 26 Dec 2013 11:12:34 -0800
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-dhcpv4-active-leasequery-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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, 26 Dec 2013 19:12:36 -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 Group =
of the IETF.

        Title           : Active DHCPv4 Lease Query
        Authors         : Kim Kinnear
                          Mark Stapp
                          Bernie Volz
                          Neil Russell
	Filename        : draft-ietf-dhc-dhcpv4-active-leasequery-00.txt
	Pages           : 22
	Date            : 2013-12-26

Abstract:
   The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has been
   extended with a Leasequery capability that allows a client to request
   information about DHCPv4 bindings.  That mechanism is limited to
   queries for individual bindings.  In some situations individual
   binding queries may not be efficient, or even possible.  In addition,
   continuous update of an external client with Leasequery data is
   sometimes desired.  This document expands on the DHCPv4 Leasequery
   protocol, and allows for active transfer of near real-time DHCPv4
   address binding information data via TCP.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dhc-dhcpv4-active-leasequery/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dhc-dhcpv4-active-leasequery-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

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

