
From wdec@cisco.com  Tue Jun  2 10:19:32 2009
Return-Path: <wdec@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A809B3A67CC for <dhcwg@core3.amsl.com>; Tue,  2 Jun 2009 10:19:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ffgvqT-mp1Iw for <dhcwg@core3.amsl.com>; Tue,  2 Jun 2009 10:19:31 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 0B3163A6A00 for <dhcwg@ietf.org>; Tue,  2 Jun 2009 10:18:40 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.41,292,1241395200"; d="scan'208";a="41866734"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 02 Jun 2009 17:18:40 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n52HIemb012484;  Tue, 2 Jun 2009 19:18:40 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n52HIeFd018424; Tue, 2 Jun 2009 17:18:40 GMT
Received: from xmb-ams-33b.cisco.com ([144.254.231.86]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Tue, 2 Jun 2009 19:18:40 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 2 Jun 2009 19:18:35 +0200
Message-ID: <D9872168DBD43A41BD71FFC4713274D407249AF8@xmb-ams-33b.emea.cisco.com>
In-Reply-To: <C43D8589-4584-4AED-9F26-75AF7E7B2F68@nominum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Process: draft-ietf-dec-route-option and draft-droms-dhc-dhcpv6-default-router
Thread-Index: AcnQCQ9skadsOcQiRkmtGceRj+e/kwTlV2OQ
References: <C43D8589-4584-4AED-9F26-75AF7E7B2F68@nominum.com>
From: "Wojciech Dec (wdec)" <wdec@cisco.com>
To: "Ted Lemon" <Ted.Lemon@nominum.com>, "dhc WG" <dhcwg@ietf.org>
X-OriginalArrivalTime: 02 Jun 2009 17:18:40.0775 (UTC) FILETIME=[2C84D970:01C9E3A6]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=5520; t=1243963120; x=1244827120; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=wdec@cisco.com; z=From:=20=22Wojciech=20Dec=20(wdec)=22=20<wdec@cisco.com> |Subject:=20RE=3A=20[dhcwg]=20Process=3A=20draft-ietf-dec-r oute-option=20and=20draft-droms-dhc-dhcpv6-default-router |Sender:=20; bh=Ymjg+qwMjohHS6GEtpUskpWU9tUDYldTsNT8OQPUV1A=; b=EsW/GFByfFtTbwsk4rW3XOIcqvJoQFnn0756m69DaI6yeoSo8Jd0P+rC39 a35QtS3lD8HpWiYoJHH0Li8CXvGW6Hp34886aP2uTC1TLGi9KRpNWMtGe2ap b4ykxtLbll;
Authentication-Results: ams-dkim-1; header.From=wdec@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; ); 
Subject: Re: [dhcwg] Process: draft-ietf-dec-route-option and draft-droms-dhc-dhcpv6-default-router
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 02 Jun 2009 17:19:32 -0000

I strongly doubt in that there will be a single way in which the whole
of the world chooses to use and deploy IPv6 auto-provisioning, as well
as in the wisdom of IETF picking and enforcing one such choice. Various
communities have different motivations for preferring say an RA-only or
a DHCP-only model or a mix of both.  Provided that none of these
fundamentally break IPv6 or causes industry wide incompatibility,
besides perhaps religious preferences, I do not see why DHC work on
these should not proceed. (Re incompatibility and using an analogy from
IPv4, expecting a host without a dhcp client to work on a network whose
designer specifically intended for DHCPv4 to be used isn't very
reasonable, irrespective of the wisdom or otherwise of the designer's
choice.)

As such I see it both within the DHC WG community's responsibility and
interest to continue to define standards that support deployment of such
preferences and allow the choice to be made by the eventual adopters who
are the de-facto experts of their domain. The confusion regarding the
role of RAs vs DHCP, and the present day inconsistency of
implementations is actually one point that already makes IPv6 deployment
harder than it needed be. Time to straighten this out (a point that goes
beyond these two drafts).

Now, given that the DHC WG is by all accounts the community with the DHC
WG experts it's only reasonable for it to continue to define DHCP
options and functionality that are of interest, while engaging in
discussions with other WGs who may share some of interest or be working
on alternatives if say info model reuse is something of common interest.
It's likely to be futile to expect another WG to gather the right mix of
dhcp and subject-whatever matter experts to do that work; if they're
interested, they will come to dhc.

My 2c,
Woj.

> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org]=20
> On Behalf Of Ted Lemon
> Sent: 08 May 2009 20:16
> To: dhc WG
> Subject: [dhcwg] Process:=20
> draft-ietf-mip6-bootstrapping-integrated-dhc=20
> anddraft-droms-dhc-dhcpv6-default-router
>=20
> John and I were just talking about how to get a good=20
> discussion going on the working group mailing list on these=20
> two items, which came up at =20
> the IETF74 meeting.   I think in order to do that we need to divide =20
> the discussion up into three parts:
>=20
> 1. Is this something that should happen?
> 2. Who should do it?
> 3. What should the documents say?
>=20
> Once we divide it up this way, it becomes obvious to me that=20
> the first part of the discussion simply isn't within the=20
> charter of the DHC =20
> working group.   There are certainly participants in the DHC working =20
> group who have an interest in this discussion, and ultimately=20
> if the IETF were to proceed in defining these DHCPv6 options,=20
> it would be something that would require the involvement of=20
> the DHC working group, so it seems natural to bring it up in=20
> the DHC working group, but actually it's futile to do so -=20
> it's just a waste of everybody's time.
>=20
> As for the second discussion, I don't get the sense that=20
> there is consensus among participants in the DHC working=20
> group that we should be doing this work. I don't get the=20
> sense that there is consensus that =20
> we should not, either.   The point is that the interested parties in =20
> the DHC working group should be having this discussion somewhere else
> - perhaps int area, perhaps routing area, perhaps some other working =20
> group.   And then once a conclusion has been reached, I think=20
> it would =20
> be fine to come back to the DHC working group and say "will=20
> you now do =20
> this?"   But I don't think that conclusion has been reached yet.
>=20
> As for the third discussion, there are aspects of that=20
> discussion that make sense to have in the DHC working group,=20
> but there are other =20
> aspects that clearly aren't within our area of expertise.   What the =20
> options should look like is probably our issue, although others may =20
> have opinions about that.   How to resolve inconsistencies between =20
> what might be received in an RA, and what might be received=20
> in a DHCP message, really isn't our area of expertise.
>=20
> The reason I am writing this up now is to ask the=20
> participants in the =20
> working group to comment on this.   Would anybody disagree with this =20
> division of the discussion?   Would anybody disagree with what I've =20
> said about where each part of this discussion ought to occur?=20
>   If so, =20
> please explain.   If not, I'd like to encourage the=20
> interested parties =20
> not to get discouraged about this, but rather to take up the=20
> work of finding a home for these discussions, to have the=20
> discussions, see what consensus arises, and bring that back to us.
>=20
> If the consensus of the working group is that we *ought* to=20
> be responsible for these discussions, then we should start=20
> talking about =20
> rechartering to include this work in our charter.   If=20
> nothing else, I =20
> suspect that will trigger some fruitful discussion with=20
> interested parties who are not regular participants in the=20
> DHC working group.
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>=20

From cra@WPI.EDU  Tue Jun  2 12:14:36 2009
Return-Path: <cra@WPI.EDU>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC7DE28C19B for <dhcwg@core3.amsl.com>; Tue,  2 Jun 2009 12:14:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wlycdkYe8s13 for <dhcwg@core3.amsl.com>; Tue,  2 Jun 2009 12:14:36 -0700 (PDT)
Received: from mail1.wpi.edu (MAIL1.WPI.EDU [130.215.36.91]) by core3.amsl.com (Postfix) with ESMTP id 9A0F928C24B for <dhcwg@ietf.org>; Tue,  2 Jun 2009 12:14:15 -0700 (PDT)
Received: from SMTP.WPI.EDU (SMTP.WPI.EDU [130.215.36.186]) by mail1.wpi.edu (8.14.3/8.14.3) with ESMTP id n52JEAEs016759 for <dhcwg@ietf.org>; Tue, 2 Jun 2009 15:14:10 -0400
Received: from angus.ind.WPI.EDU (ANGUS.IND.WPI.EDU [130.215.130.21]) by SMTP.WPI.EDU (8.14.2/8.14.2) with ESMTP id n52JEAGK017764 for <dhcwg@ietf.org>; Tue, 2 Jun 2009 15:14:10 -0400 (envelope-from cra@WPI.EDU)
Received: from angus.ind.WPI.EDU (angus.ind.WPI.EDU [127.0.0.1]) by angus.ind.WPI.EDU (8.14.2/8.14.2) with ESMTP id n52JEAYk026923 for <dhcwg@ietf.org>; Tue, 2 Jun 2009 15:14:10 -0400
Received: (from cra@localhost) by angus.ind.WPI.EDU (8.14.2/8.14.2/Submit) id n52JEA7g026922 for dhcwg@ietf.org; Tue, 2 Jun 2009 15:14:10 -0400
X-Authentication-Warning: angus.ind.WPI.EDU: cra set sender to cra@WPI.EDU using -f
Date: Tue, 2 Jun 2009 15:14:10 -0400
From: Chuck Anderson <cra@WPI.EDU>
To: dhcwg@ietf.org
Message-ID: <20090602191409.GC22133@angus.ind.WPI.EDU>
Mail-Followup-To: dhcwg@ietf.org
References: <C43D8589-4584-4AED-9F26-75AF7E7B2F68@nominum.com> <D9872168DBD43A41BD71FFC4713274D407249AF8@xmb-ams-33b.emea.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <D9872168DBD43A41BD71FFC4713274D407249AF8@xmb-ams-33b.emea.cisco.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Subject: Re: [dhcwg] Process: draft-ietf-dec-route-option and	draft-droms-dhc-dhcpv6-default-router
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 02 Jun 2009 19:14:37 -0000

On Tue, Jun 02, 2009 at 07:18:35PM +0200, Wojciech Dec (wdec) wrote:
> I do not see why DHC work on these should not proceed.
...
> As such I see it both within the DHC WG community's responsibility and
> interest to continue to define standards that support deployment of such
> preferences and allow the choice to be made by the eventual adopters who
> are the de-facto experts of their domain. The confusion regarding the
> role of RAs vs DHCP, and the present day inconsistency of
> implementations is actually one point that already makes IPv6 deployment
> harder than it needed be. Time to straighten this out (a point that goes
> beyond these two drafts).

+1

> Now, given that the DHC WG is by all accounts the community with the DHC
> WG experts it's only reasonable for it to continue to define DHCP
> options and functionality that are of interest, while engaging in
> discussions with other WGs who may share some of interest or be working
> on alternatives if say info model reuse is something of common interest.
> It's likely to be futile to expect another WG to gather the right mix of
> dhcp and subject-whatever matter experts to do that work; if they're
> interested, they will come to dhc.

Agreed.

From retvari@tmit.bme.hu  Tue Jun  2 07:55:03 2009
Return-Path: <retvari@tmit.bme.hu>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E02E73A6CC0 for <dhcwg@core3.amsl.com>; Tue,  2 Jun 2009 07:55:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.855
X-Spam-Level: *
X-Spam-Status: No, score=1.855 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HELO_EQ_HU=1.35, HOST_EQ_HU=1.245]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PBV4Edju5NN1 for <dhcwg@core3.amsl.com>; Tue,  2 Jun 2009 07:55:03 -0700 (PDT)
Received: from mail.bme.hu (mail.bme.hu [152.66.115.60]) by core3.amsl.com (Postfix) with ESMTP id 27B8B28C140 for <dhcwg@ietf.org>; Tue,  2 Jun 2009 07:54:49 -0700 (PDT)
Received: from weber.tmit.bme.hu ([152.66.244.111]) by mail.bme.hu (Lotus Domino Release 6.5.1) with ESMTP id 2009060216545253-4942 ; Tue, 2 Jun 2009 16:54:52 +0200 
From: Gabor Retvari <retvari@tmit.bme.hu>
To: dhcwg@ietf.org
Date: Tue, 2 Jun 2009 16:50:42 +0200
User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405)
MIME-Version: 1.0
Message-Id: <200906021650.42591.retvari@tmit.bme.hu>
X-MIMETrack: Itemize by SMTP Server on BME_NOTES_1/BME(Release 6.5.1|January 21, 2004) at 2009.06.02 16:54:52, Serialize by Router on BME_NOTES_1/BME(Release 6.5.1|January 21, 2004) at 2009.06.02 16:54:55, Serialize complete at 2009.06.02 16:54:55
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
X-Mailman-Approved-At: Thu, 04 Jun 2009 09:13:33 -0700
Subject: [dhcwg] DHCPv6: Canonical way to handle an unknown option
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 02 Jun 2009 15:03:52 -0000

Dear all,

What is the best way to handle a DHCPv6 message that contains an unknown 
DHCPv6 option? Should an implementation drop the message as a whole, once it 
encounters an unknown option in it, or should it drop only the option and 
carry on processing the rest of the message that it can make sense of? (It 
seems to me that wide-dhcp, for instance, implements the latter behavior.)

Could any one provide me with a pointer on the recommended way to handle 
unknown options in DHCPv6 implementations?

Best regards,
Gabor

From David_Hankins@isc.org  Thu Jun  4 12:33:59 2009
Return-Path: <David_Hankins@isc.org>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 332363A67BD for <dhcwg@core3.amsl.com>; Thu,  4 Jun 2009 12:33:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VgtQkO57-DRA for <dhcwg@core3.amsl.com>; Thu,  4 Jun 2009 12:33:58 -0700 (PDT)
Received: from hankinsfamily.info (the.hankinsfamily.info [204.152.186.148]) by core3.amsl.com (Postfix) with ESMTP id 5D7373A70DA for <dhcwg@ietf.org>; Thu,  4 Jun 2009 12:33:58 -0700 (PDT)
Received: from david.isc.org (c-67-188-70-48.hsd1.ca.comcast.net [67.188.70.48]) (authenticated bits=0) by hankinsfamily.info (8.13.8/8.13.8) with ESMTP id n54JYOSd027425 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <dhcwg@ietf.org>; Thu, 4 Jun 2009 12:34:24 -0700
Received: by david.isc.org (Postfix, from userid 10200) id 93F2216E1B3; Thu,  4 Jun 2009 12:34:00 -0700 (PDT)
Date: Thu, 4 Jun 2009 12:34:00 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: DHC WG <dhcwg@ietf.org>
Message-ID: <20090604193400.GF4148@isc.org>
References: <200906021650.42591.retvari@tmit.bme.hu>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Y/WcH0a6A93yCHGr"
Content-Disposition: inline
In-Reply-To: <200906021650.42591.retvari@tmit.bme.hu>
User-Agent: Mutt/1.5.16 (2007-06-09)
Subject: Re: [dhcwg] DHCPv6: Canonical way to handle an unknown option
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 04 Jun 2009 19:33:59 -0000

--Y/WcH0a6A93yCHGr
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 02, 2009 at 04:50:42PM +0200, Gabor Retvari wrote:
> What is the best way to handle a DHCPv6 message that contains an unknown=
=20
> DHCPv6 option? Should an implementation drop the message as a whole, once=
 it=20
> encounters an unknown option in it, or should it drop only the option and=
=20
> carry on processing the rest of the message that it can make sense of? (I=
t=20
> seems to me that wide-dhcp, for instance, implements the latter behavior.)
>=20
> Could any one provide me with a pointer on the recommended way to handle=
=20
> unknown options in DHCPv6 implementations?

I don't know if there are any pointers.  ISC DHCP's v4 and v6 client
(they both operate the same way in this regard) will only reject a
packet if it lacks options that are mandatory by the protocol.  It
does not reject a packet with a new option (exception: bugs in the
software, long story).

New options are cached, since it cannot be known what the option's
format is ahead of time, they are stored as an opaque hexadecimal
string.  When configuration is comitted, they are passed to the system
(like all known option codes) as environment variables, so that the
operator or integrator can potentially digest and use them before the
software is updated.

It is reasonable to omit or disregard an unknown option.  Not all
implementations have variable sized lease storage, and quite a few
will not be interested in any options it cannot use directly itself.

Failing to process a packet with an unknown option is probably the
worst possible behaviour.

--=20
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins

--Y/WcH0a6A93yCHGr
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQFKKCGocXeLeWu2vmoRAiRNAJ9K1wv1Nl8/93kj6IH4xlGHVnmS8QCfY/tp
Tf0NAoEtOvTLf68kWgUKtcQ=
=Wuoa
-----END PGP SIGNATURE-----

--Y/WcH0a6A93yCHGr--

From Ted.Lemon@nominum.com  Thu Jun  4 12:52:48 2009
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C31D73A6E07 for <dhcwg@core3.amsl.com>; Thu,  4 Jun 2009 12:52:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EufkraWIs-WC for <dhcwg@core3.amsl.com>; Thu,  4 Jun 2009 12:52:48 -0700 (PDT)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by core3.amsl.com (Postfix) with ESMTP id D5CCD3A6944 for <dhcwg@ietf.org>; Thu,  4 Jun 2009 12:52:47 -0700 (PDT)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKSigmCw0lGxRMi6yDsHZAdE4zvKf5U8vK@postini.com; Thu, 04 Jun 2009 12:52:50 PDT
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 57A0B1BD0A9 for <dhcwg@ietf.org>; Thu,  4 Jun 2009 12:52:56 -0700 (PDT)
Received: from [10.0.0.208] (71.32.40.139) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.1.336.0; Thu, 4 Jun 2009 12:52:42 -0700
Message-ID: <A03E3CD5-383C-4970-8974-DFA135E58684@nominum.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
To: dhc WG <dhcwg@ietf.org>
In-Reply-To: <20090604193400.GF4148@isc.org>
Content-Type: text/plain; charset="US-ASCII"; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 (Apple Message framework v935.3)
Date: Thu, 4 Jun 2009 12:52:41 -0700
References: <200906021650.42591.retvari@tmit.bme.hu> <20090604193400.GF4148@isc.org>
X-Mailer: Apple Mail (2.935.3)
Subject: Re: [dhcwg] DHCPv6: Canonical way to handle an unknown option
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 04 Jun 2009 19:52:48 -0000

This raises an interesting question - in several places RFC3115 talks  
about a "valid Reply message," but the term is never defined.   We  
aren't told what makes a Reply message "valid" or "invalid."   So I  
understand the writer's confusion, and this ought to be clarified.   I  
would assume that "valid" means "well-formed," which is to say "parses  
without encountering anything the RFC hasn't told you how to parse."    
You've been told how to parse options, so I would say that an unknown  
option is valid in this context, but the RFC provides no guidance.

Anyway, the bottom line is that logically it doesn't make sense to  
drop packets with unknown options - it's entirely possible that these  
options represent a valid protocol extension that was added after you  
implemented your client, and it would be a mistake for your client to  
fail because of this.   Rather, it should ignore what it doesn't  
understand, as long as it's well-formed.   Otherwise, some protocol  
enhancement down the road could suddenly result in your client failing  
dependably, and you really don't want those phone calls.


From budm@weird-solutions.com  Fri Jun  5 00:15:20 2009
Return-Path: <budm@weird-solutions.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 49A2E3A6910 for <dhcwg@core3.amsl.com>; Fri,  5 Jun 2009 00:15:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level: 
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6tYsw8A119xB for <dhcwg@core3.amsl.com>; Fri,  5 Jun 2009 00:15:19 -0700 (PDT)
Received: from cl36.gs02.gridserver.com (cl36.gs02.gridserver.com [64.13.232.45]) by core3.amsl.com (Postfix) with ESMTP id 6B5FF3A672F for <dhcwg@ietf.org>; Fri,  5 Jun 2009 00:15:19 -0700 (PDT)
Received: from static-213-115-152-226.sme.bredbandsbolaget.se ([213.115.152.226]:34366 helo=offset.weird.se) by cl36.gs02.gridserver.com with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.63) (envelope-from <budm@weird-solutions.com>) id 1MCTe5-0002U7-NS for dhcwg@ietf.org; Fri, 05 Jun 2009 00:15:21 -0700
From: Bud Millwood <budm@weird-solutions.com>
Organization: Weird Solutions, Inc.
To: dhcwg@ietf.org
Date: Fri, 5 Jun 2009 09:08:36 +0200
User-Agent: KMail/1.9.9
References: <200906021650.42591.retvari@tmit.bme.hu>
In-Reply-To: <200906021650.42591.retvari@tmit.bme.hu>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200906050908.37143.budm@weird-solutions.com>
X-Authenticated-User: 39280 budm@broadbandprovisioner.com
Subject: Re: [dhcwg] DHCPv6: Canonical way to handle an unknown option
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Bud Millwood <budm@weird-solutions.com>
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 05 Jun 2009 07:15:20 -0000

On Tuesday 02 June 2009, Gabor Retvari wrote:
> Dear all,
>
> What is the best way to handle a DHCPv6 message that contains an unknown
> DHCPv6 option? Should an implementation drop the message as a whole, once
> it encounters an unknown option in it, or should it drop only the option
> and carry on processing the rest of the message that it can make sense of?
> (It seems to me that wide-dhcp, for instance, implements the latter
> behavior.)
>
> Could any one provide me with a pointer on the recommended way to handle
> unknown options in DHCPv6 implementations?

The de-facto standard for adding new options to DHCPv4 has always been that if 
a sender transmits an option, and the reply does not contain the option (or 
does not contain any explicit reply to that option), the server does not 
understand the option. The sender can then alter its behavior accordingly.

This long-time standard behavior implies that it is the norm for a server to 
drop unknown options (from the sender's perspective; what you do with them 
internally is your business). I highly doubt that this group would recommend 
any other behavior for DHCPv6.

- Bud

Bud Millwood
Weird Solutions, Inc.
http://www.weird-solutions.com
tel: +46 8 758 3700
fax: +46 8 758 3687

From David_Hankins@isc.org  Fri Jun  5 14:55:33 2009
Return-Path: <David_Hankins@isc.org>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 582E43A697C for <dhcwg@core3.amsl.com>; Fri,  5 Jun 2009 14:55:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1m6KWbdKDiBN for <dhcwg@core3.amsl.com>; Fri,  5 Jun 2009 14:55:32 -0700 (PDT)
Received: from hankinsfamily.info (the.hankinsfamily.info [204.152.186.148]) by core3.amsl.com (Postfix) with ESMTP id 71A3D3A68A6 for <dhcwg@ietf.org>; Fri,  5 Jun 2009 14:55:32 -0700 (PDT)
Received: from david.isc.org (c-67-188-70-48.hsd1.ca.comcast.net [67.188.70.48]) (authenticated bits=0) by hankinsfamily.info (8.13.8/8.13.8) with ESMTP id n55Ltuwo003355 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Jun 2009 14:55:56 -0700
Received: by david.isc.org (Postfix, from userid 10200) id 6F1E616E1B3; Fri,  5 Jun 2009 14:55:32 -0700 (PDT)
Date: Fri, 5 Jun 2009 14:55:32 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: Ted Lemon <Ted.Lemon@nominum.com>
Message-ID: <20090605215532.GD4040@isc.org>
References: <200906021650.42591.retvari@tmit.bme.hu> <20090604193400.GF4148@isc.org> <A03E3CD5-383C-4970-8974-DFA135E58684@nominum.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="eHhjakXzOLJAF9wJ"
Content-Disposition: inline
In-Reply-To: <A03E3CD5-383C-4970-8974-DFA135E58684@nominum.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
Cc: dhc WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] DHCPv6: Canonical way to handle an unknown option
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 05 Jun 2009 21:55:33 -0000

--eHhjakXzOLJAF9wJ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jun 04, 2009 at 12:52:41PM -0700, Ted Lemon wrote:
> This raises an interesting question - in several places RFC3115 talks abo=
ut=20
> a "valid Reply message," but the term is never defined.   We aren't told=
=20
> what makes a Reply message "valid" or "invalid."   So I understand the=20
> writer's confusion, and this ought to be clarified.   I would assume that=
=20
> "valid" means "well-formed," which is to say "parses without encountering=
=20
> anything the RFC hasn't told you how to parse."   You've been told how to=
=20
> parse options, so I would say that an unknown option is valid in this=20
> context, but the RFC provides no guidance.

There are message validation sections in 3315 that describe how to
validate the various kinds of messages (must contain this and that,
must not contain those other things...).  I've always assumed that
valid, in the context of 3315's own lexicon, means that the message
has passed those tests.

I'm becoming increasingly aware of a different but related open issue
in both DHCPv4 and DHCPv6 - the client's selection criteria when
presented with multiple offers (or advertises).

DHCPv4 describes a selection period, but doesn't hint at selection
mechanisms.  3315 hints, which I've tried to implement to the best
of my ability, but is self-inconsistent in its hints, and
inconsistency in client implementations here could lead to
interoperability issues.

In particular, in either protocol, if a client de-selects a server's
offer due to some failing criteria ("i require options x,y,z to
operate, you did not supply z"), the server (and operator) has no
feedback to understand the nature of the deselection.  The client is
simply silent in this case, which is identical behaviour to UDP packet
loss.


At some point I'll set forward to do something about that ("write a
draft"), but at least for me that time is not today.  If someone else
has the energy, I think it would be good for there to be an optional
to implement selection algorithm, that also introduces a new option
for a client to advertise the results of selection, and a new message
so that option can be used when selection resulted in zero leases
(without declining the lease).

That's also an opportunity to reinforce simple ideas like, if you
see a new option you don't understand, ignore it.

--=20
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins

--eHhjakXzOLJAF9wJ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQFKKZRUcXeLeWu2vmoRArYfAJ941dArkSM6BYSPq9VJE8tKFlEfQwCcDbbb
PCRX+mQxL7hXb0HlvxNZ4ME=
=frlb
-----END PGP SIGNATURE-----

--eHhjakXzOLJAF9wJ--

From alper.yegin@yegin.org  Tue Jun 16 00:37:05 2009
Return-Path: <alper.yegin@yegin.org>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC3993A6887 for <dhcwg@core3.amsl.com>; Tue, 16 Jun 2009 00:37:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.15
X-Spam-Level: 
X-Spam-Status: No, score=-1.15 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D196XN7db6qd for <dhcwg@core3.amsl.com>; Tue, 16 Jun 2009 00:37:04 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id AE5ED3A6405 for <dhcwg@ietf.org>; Tue, 16 Jun 2009 00:37:04 -0700 (PDT)
Received: from LENOVO (dsl88-247-34762.ttnet.net.tr [88.247.135.202]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MKp8S-1MGT4z2fXO-000fwA; Tue, 16 Jun 2009 03:27:41 -0400
From: "Alper Yegin" <alper.yegin@yegin.org>
To: "'John Jason Brzozowski'" <john_brzozowski@cable.comcast.com>, "'dhc WG'" <dhcwg@ietf.org>
References: <20090325201231.7A5943A6BD6@core3.amsl.com> <C5F02B3C.9F5EA%john_brzozowski@cable.comcast.com>
In-Reply-To: <C5F02B3C.9F5EA%john_brzozowski@cable.comcast.com>
Date: Tue, 16 Jun 2009 10:27:29 +0300
Message-ID: <086b01c9ee53$ea8a53c0$bf9efb40$@yegin@yegin.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcmthjRi37KhcuPQRiiZLYeAreRjLQALbYBcECboaeA=
Content-Language: en-us
X-Provags-ID: V01U2FsdGVkX19aMcCE5LuI7/RCOMgUZv4aQ/snQpFKkTnypgm judw60F0RoXFTNBgRjdz/iyasFpvtvfYGqH4m82UbdEfbYZHSN phJ2EL8kYq5xnc0vj0lnA==
Subject: Re: [dhcwg] FW: New Version Notification for draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 16 Jun 2009 07:37:05 -0000

Hello,

I just read this I-D. I'd like to thank authors for putting this analysis
together. 

I'd like to note that there were several points raised on the mailing lists
before. Since I didn't see them being covered in this I-D, I was wondering
what the analysis authors think/thought about them. Can we get their opinion
on these specific issues:


- The role of NAS with respect to DHCP is unclear. For some part it is
acting as a DHCP relay, for others as a DHCP server (as it terminates DHCP
messages and generates DHCP messages -- for EAP). Is the NAS playing two
distinct DHCP roles within the same DHCP session? How well does that fit
DHCP?

- NAS (acting as DHCP relay) is inserting DHCP options towards the DHCP
client. I'm not aware of DHCP relays inserting options in that direction. To
say the least, that breaks the end-to-end security, such as the one using
RFC 3118.

- " The client sends a Solicit message with an Option specifying the
   session authentication protocol as EAP to the
   All_DHCP_Relay_Agents_and_Servers address to find available DHCP
   servers.  Any server that can authenticate and address it responds
   with a DHCPEAP-REQ message."

This is talking about a DHCP server sending a "request" to the DHCP
"client", quite the opposite of current DHCP architecture. How well does
that fit the state machine?

- According to EAP, the EAP authenticator has to be able to retransmit EAP
requests. That means the NAS has to rexmit DHCPEAP-REQ to the DHCP client
until it receives a DHCPEAP-RES. How does this fit "DHCP"?

- EAP re-authentication may be initiated by the network. How would this be
handled? It requires the DHCP client to receive an unsolicited DHCP request
message from the NAS (a DHCP relay??). "DHCP client receiving a request from
relay" sounds quite non-standard to me.

- Finally, I wonder how orderly delivery of EAP (as mandated by RFC 3748) is
satisfied by this proposed EAP lower layer. 


Regards,

Alper











> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
> Of John Jason Brzozowski
> Sent: Thursday, March 26, 2009 3:41 AM
> To: dhc WG
> Subject: [dhcwg] FW: New Version Notification for draft-brzozowski-
> dhcp-eap-analysis-00
> 
> FYI
> 
> John
> 
> ------ Forwarded Message
> From: IETF I-D Submission Tool <idsubmission@ietf.org>
> Date: Wed, 25 Mar 2009 16:12:31 -0400
> To: <mellon@nominum.com>
> Cc: "Brzozowski, John" <john_brzozowski@cable.comcast.com>, Geoffrey
> Holan
> <geoffrey.holan@telus.com>
> Subject: New Version Notification for
> draft-brzozowski-dhcp-eap-analysis-00
> 
> 
> 
> A new version of I-D, draft-brzozowski-dhcp-eap-analysis-00.txt has
> been
> successfuly submitted by Ted Lemon and posted to the IETF repository.
> 
> Filename:        draft-brzozowski-dhcp-eap-analysis
> Revision:        00
> Title:           DHCP Authentication Analysis
> Creation_date:   2009-03-25
> WG ID:           Independent Submission
> Number_of_pages: 9
> 
> Abstract:
> This document analyzes and technically evaluate the techniques
> proposed to support end-user authentication using extensions to DHCP.
> 
> 
> 
> The IETF Secretariat.
> 
> 
> 
> ------ End of Forwarded Message
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg



From ric@cisco.com  Tue Jun 16 02:43:51 2009
Return-Path: <ric@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA5183A6838 for <dhcwg@core3.amsl.com>; Tue, 16 Jun 2009 02:43:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WMlH7GBDEgsf for <dhcwg@core3.amsl.com>; Tue, 16 Jun 2009 02:43:50 -0700 (PDT)
Received: from syd-iport-1.cisco.com (syd-iport-1.cisco.com [64.104.193.196]) by core3.amsl.com (Postfix) with ESMTP id 3590A3A6D64 for <dhcwg@ietf.org>; Tue, 16 Jun 2009 02:43:43 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,227,1243814400"; d="scan'208";a="55832187"
Received: from hkg-dkim-1.cisco.com ([10.75.231.161]) by syd-iport-1.cisco.com with ESMTP; 16 Jun 2009 09:43:30 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n5G9hTVc005606;  Tue, 16 Jun 2009 17:43:29 +0800
Received: from xbh-bgl-411.cisco.com (xbh-bgl-411.cisco.com [72.163.129.201]) by hkg-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n5G9hNod013984; Tue, 16 Jun 2009 09:43:29 GMT
Received: from xbh-hkg-411.apac.cisco.com ([64.104.123.72]) by xbh-bgl-411.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 16 Jun 2009 15:12:23 +0530
Received: from xfe-hkg-411.apac.cisco.com ([64.104.123.70]) by xbh-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 16 Jun 2009 17:42:22 +0800
Received: from syd-rpruss-8713.cisco.com ([10.67.232.180]) by xfe-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 16 Jun 2009 17:42:20 +0800
Message-Id: <704F21DF-1F6A-4D78-AF8B-D0F2E9964659@cisco.com>
From: Richard Pruss <ric@cisco.com>
To: Alper Yegin <alper.yegin@yegin.org>
In-Reply-To: <086b01c9ee53$ea8a53c0$bf9efb40$@yegin@yegin.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 16 Jun 2009 19:42:19 +1000
References: <20090325201231.7A5943A6BD6@core3.amsl.com> <C5F02B3C.9F5EA%john_brzozowski@cable.comcast.com> <086b01c9ee53$ea8a53c0$bf9efb40$@yegin@yegin.org>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 16 Jun 2009 09:42:21.0088 (UTC) FILETIME=[BEBCAA00:01C9EE66]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4620; t=1245145410; x=1246009410; c=relaxed/simple; s=hkgdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ric@cisco.com; z=From:=20Richard=20Pruss=20<ric@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20FW=3A=20New=20Version=20Notif ication=20for=20draft-brzozowski-dhcp-eap-analysis-00 |Sender:=20; bh=rkrQlXDmZBJ1XALBisw2vwfbZEp50Hpj59hTgvjj2Pc=; b=NSwgeyIQ25+xjsct4Pj6I6x6h3ZtCUwkeYbQjG1Qrj3uluV1HhLK73T3Q7 2J51vqmP9yk+fvjAiUiqh3UjALwX2ZpPTZ0cNZv+Vpq5ZcgB+mXzhyqRXEsh N0swOwErtl0SNLN9LLc8r7swuQT9iWBRyciXrKb9b/Vo5/MycaSz4=;
Authentication-Results: hkg-dkim-1; header.From=ric@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim1002 verified; ); 
Cc: 'dhc WG' <dhcwg@ietf.org>
Subject: Re: [dhcwg] FW: New Version Notification for draft-brzozowski-dhcp-eap-analysis-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 16 Jun 2009 09:43:52 -0000

On 16/06/2009, at 5:27 PM, Alper Yegin wrote:

> Hello,
>
> I just read this I-D. I'd like to thank authors for putting this  
> analysis
> together.
>
> I'd like to note that there were several points raised on the  
> mailing lists
> before. Since I didn't see them being covered in this I-D, I was  
> wondering
> what the analysis authors think/thought about them. Can we get their  
> opinion
> on these specific issues:
>
>
> - The role of NAS with respect to DHCP is unclear. For some part it is
> acting as a DHCP relay, for others as a DHCP server (as it  
> terminates DHCP
> messages and generates DHCP messages -- for EAP). Is the NAS playing  
> two
> distinct DHCP roles within the same DHCP session? How well does that  
> fit
> DHCP?

Yes, in Broadband the NAS can be a relay or a server at the operators  
choice.


>
> - NAS (acting as DHCP relay) is inserting DHCP options towards the  
> DHCP
> client. I'm not aware of DHCP relays inserting options in that  
> direction. To
> say the least, that breaks the end-to-end security, such as the one  
> using
> RFC 3118.

Depends how the keying for RFC 3118 was implemented.  We have a draft
as you are aware that has the NAS aware of the keys.

>
> - " The client sends a Solicit message with an Option specifying the
>   session authentication protocol as EAP to the
>   All_DHCP_Relay_Agents_and_Servers address to find available DHCP
>   servers.  Any server that can authenticate and address it responds
>   with a DHCPEAP-REQ message."
>
> This is talking about a DHCP server sending a "request" to the DHCP
> "client", quite the opposite of current DHCP architecture. How well  
> does
> that fit the state machine?

Draw the diagram of what you are talking it is so trivially obvious, I  
fail to understand your question.

>
> - According to EAP, the EAP authenticator has to be able to  
> retransmit EAP
> requests. That means the NAS has to rexmit DHCPEAP-REQ to the DHCP  
> client
> until it receives a DHCPEAP-RES. How does this fit "DHCP"?

As specified in the draft and now in multiple implementations.

>
> - EAP re-authentication may be initiated by the network. How would  
> this be
> handled?

Really?  Is it a requirement in broadband separate to re-addressing?

> It requires the DHCP client to receive an unsolicited DHCP request
> message from the NAS (a DHCP relay??). "DHCP client receiving a  
> request from
> relay" sounds quite non-standard to me.



>
> - Finally, I wonder how orderly delivery of EAP (as mandated by RFC  
> 3748) is
> satisfied by this proposed EAP lower layer.

This is a boring academic point with no relevance to real networking,  
can simply be answered
with the statement that there is no transport difference between EAP  
running over PPPoE,
than their is with EAP running over DHCP on an Ethernet network.

- Ric



>
>
> Regards,
>
> Alper
>
>
>
>
>
>
>
>
>
>
>
>> -----Original Message-----
>> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On  
>> Behalf
>> Of John Jason Brzozowski
>> Sent: Thursday, March 26, 2009 3:41 AM
>> To: dhc WG
>> Subject: [dhcwg] FW: New Version Notification for draft-brzozowski-
>> dhcp-eap-analysis-00
>>
>> FYI
>>
>> John
>>
>> ------ Forwarded Message
>> From: IETF I-D Submission Tool <idsubmission@ietf.org>
>> Date: Wed, 25 Mar 2009 16:12:31 -0400
>> To: <mellon@nominum.com>
>> Cc: "Brzozowski, John" <john_brzozowski@cable.comcast.com>, Geoffrey
>> Holan
>> <geoffrey.holan@telus.com>
>> Subject: New Version Notification for
>> draft-brzozowski-dhcp-eap-analysis-00
>>
>>
>>
>> A new version of I-D, draft-brzozowski-dhcp-eap-analysis-00.txt has
>> been
>> successfuly submitted by Ted Lemon and posted to the IETF repository.
>>
>> Filename:        draft-brzozowski-dhcp-eap-analysis
>> Revision:        00
>> Title:           DHCP Authentication Analysis
>> Creation_date:   2009-03-25
>> WG ID:           Independent Submission
>> Number_of_pages: 9
>>
>> Abstract:
>> This document analyzes and technically evaluate the techniques
>> proposed to support end-user authentication using extensions to DHCP.
>>
>>
>>
>> The IETF Secretariat.
>>
>>
>>
>> ------ End of Forwarded Message
>>
>> _______________________________________________
>> 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 Jun 18 11:19:36 2009
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 167D928C447 for <dhcwg@core3.amsl.com>; Thu, 18 Jun 2009 11:19:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M04otFu+Fqgz for <dhcwg@core3.amsl.com>; Thu, 18 Jun 2009 11:19:35 -0700 (PDT)
Received: from syd-iport-1.cisco.com (syd-iport-1.cisco.com [64.104.193.196]) by core3.amsl.com (Postfix) with ESMTP id 7FA6528C458 for <dhcwg@ietf.org>; Thu, 18 Jun 2009 11:19:05 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,246,1243814400"; d="scan'208";a="56079419"
Received: from hkg-dkim-1.cisco.com ([10.75.231.161]) by syd-iport-1.cisco.com with ESMTP; 18 Jun 2009 18:19:15 +0000
Received: from hkg-core-1.cisco.com (hkg-core-1.cisco.com [64.104.123.94]) by hkg-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n5IIJEwK030021;  Fri, 19 Jun 2009 02:19:14 +0800
Received: from xbh-hkg-411.apac.cisco.com (xbh-hkg-411.cisco.com [64.104.123.72]) by hkg-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n5IIJEps003570; Thu, 18 Jun 2009 18:19:14 GMT
Received: from xbh-rtp-211.amer.cisco.com ([64.102.31.102]) by xbh-hkg-411.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 19 Jun 2009 02:18:58 +0800
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 18 Jun 2009 14:18:51 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 18 Jun 2009 14:18:49 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB210D4E8EF9@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <997BC128AE961E4A8B880CD7442D948003E340B2@NJCHLEXCMB01.cable.comcast.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Agenda items for IETF75 dhcwg - First Call
Thread-Index: AcnUKkgX8FLowQubmEKQyBE6LZ6cggABy+YgAAFW86IHApWW0A==
References: <C630DCE2.A5FF2%john_brzozowski@cable.comcast.com> <8E296595B6471A4689555D5D725EBB210CBABEA7@xmb-rtp-20a.amer.cisco.com> <997BC128AE961E4A8B880CD7442D948003E340B2@NJCHLEXCMB01.cable.comcast.com>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 18 Jun 2009 18:18:51.0161 (UTC) FILETIME=[3B160890:01C9F041]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2489; t=1245349154; x=1246213154; c=relaxed/simple; s=hkgdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=volz@cisco.com; z=From:=20=22Bernie=20Volz=20(volz)=22=20<volz@cisco.com> |Subject:=20RE=3A=20[dhcwg]=20Agenda=20items=20for=20IETF75 =20dhcwg=20-=20First=20Call |Sender:=20; bh=HTfz5toQqkVdfkZNg5UdoV+9jxWlpmX/AIE5Qe/99n4=; b=JwVeQLbdYiCMwhdAWvACXbJ4K5tSYxeRXbZnxqecccbwgRmLl23yvwAUYR LU4Ob8zxtVQntOTHUV5nNAPm/glf34YCfz0q8Yjn77qF5NJQNHpbLNknoxm/ vAFpKzQFn7cYwxv250ZZejxlb5nSPvI4lF6s2w8dDXuRkNc7KLunM=;
Authentication-Results: hkg-dkim-1; header.From=volz@cisco.com; dkim=pass ( sig from cisco.com/hkgdkim1002 verified; ); 
Cc: dhc Chairs <dhc-chairs@tools.ietf.org>
Subject: Re: [dhcwg] Agenda items for IETF75 dhcwg - First Call
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 18 Jun 2009 18:19:36 -0000

It has been 5 weeks ... no progress yet ...

- Bernie

-----Original Message-----
From: Brzozowski, John [mailto:John_Brzozowski@Cable.Comcast.com]=20
Sent: Wednesday, May 13, 2009 10:00 PM
To: Bernie Volz (volz); dhcwg@ietf.org
Cc: dhc Chairs
Subject: RE: [dhcwg] Agenda items for IETF75 dhcwg - First Call

Bernie,
=20
Ted and I have discussed next steps for all the open items below and
then some.  Expect to see movement on all these items over the next
couple of weeks.
=20
Let us know if you have any additional questions.

John
---------------------------------------------------=20
John Jason Brzozowski
Comcast Corporation
e) mailto:john_brzozowski@cable.comcast.com
m) 609-377-6594
---------------------------------------------------

________________________________

From: Bernie Volz (volz) [mailto:volz@cisco.com]
Sent: Wed 5/13/2009 9:35 PM
To: Brzozowski, John; dhcwg@ietf.org
Cc: dhc Chairs
Subject: RE: [dhcwg] Agenda items for IETF75 dhcwg - First Call



What's up with some of the drafts that are supposed to be going to the
IETF/IESG?

For example, my two drafts are still in "I-D Exists"?

draft-ietf-dhc-dhcpv4-bulk-leasequery-00 [draft]  2009-02-13 Active
I-D Exists=20
draft-ietf-dhc-dhcpv4-vendor-message-00 [draft]  2009-01-12 Active
I-D Exists =20

>From the IETF 74 slides:

- Ready for submission to IESG
draft-ietf-dhc-container-opt   [this one is at the IESG]
draft-ietf-dhc-dhcpv6-reconfigure-rebind   [still just I-D Exists]
draft-ietf-dhc-subnet-alloc  [still just I-D Exists]
draft-ietf-dhc-vpn-option  [still just I-D Exists]
- In WG last call
draft-ietf-dhc-dhcpv4-vendor-message   [still just I-D Exists]
draft-ietf-dhc-dhcpv6-vendor-message   [still just I-D Exists]
draft-ietf-dhc-relay-id-suboption   [still just I-D Exists]
- Ready for WG last call
draft-ietf-dhc-dhcpv4-bulk-leasequery   [no last call started]

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of John Jason Brzozowski
Sent: Wednesday, May 13, 2009 8:24 PM
To: dhcwg@ietf.org
Cc: dhc Chairs
Subject: [dhcwg] Agenda items for IETF75 dhcwg - First Call

This is the first call for agenda items for the IETF 75 dhcwg meeting in
Stockholm.  Please send your requests directly to the chairs.

Thanks,

Ted and John

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




From gwz@net-zen.net  Thu Jun 18 19:31:28 2009
Return-Path: <gwz@net-zen.net>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A9A43A685E for <dhcwg@core3.amsl.com>; Thu, 18 Jun 2009 19:31:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.062
X-Spam-Level: 
X-Spam-Status: No, score=-2.062 tagged_above=-999 required=5 tests=[AWL=-0.082, BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hTZwqwtflMBW for <dhcwg@core3.amsl.com>; Thu, 18 Jun 2009 19:31:27 -0700 (PDT)
Received: from smtpout04.prod.mesa1.secureserver.net (smtpout04-01.prod.mesa1.secureserver.net [64.202.165.196]) by core3.amsl.com (Postfix) with SMTP id C0D563A67D7 for <dhcwg@ietf.org>; Thu, 18 Jun 2009 19:31:27 -0700 (PDT)
Received: (qmail 20453 invoked from network); 19 Jun 2009 02:31:36 -0000
Received: from unknown (124.122.163.140) by smtpout04.prod.mesa1.secureserver.net (64.202.165.196) with ESMTP; 19 Jun 2009 02:31:36 -0000
From: "Glen Zorn" <gwz@net-zen.net>
To: "'Bernie Volz \(volz\)'" <volz@cisco.com>, "'Brzozowski, John'" <John_Brzozowski@Cable.Comcast.com>, <dhcwg@ietf.org>
References: <C630DCE2.A5FF2%john_brzozowski@cable.comcast.com>	<8E296595B6471A4689555D5D725EBB210CBABEA7@xmb-rtp-20a.amer.cisco.com>	<997BC128AE961E4A8B880CD7442D948003E340B2@NJCHLEXCMB01.cable.comcast.com> <8E296595B6471A4689555D5D725EBB210D4E8EF9@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <8E296595B6471A4689555D5D725EBB210D4E8EF9@xmb-rtp-20a.amer.cisco.com>
Date: Fri, 19 Jun 2009 09:27:55 +0700
Organization: Network Zen
Message-ID: <019701c9f085$90af1640$b20d42c0$@net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcnUKkgX8FLowQubmEKQyBE6LZ6cggABy+YgAAFW86IHApWW0AAQ/HEw
Content-Language: en-us
Cc: 'dhc Chairs' <dhc-chairs@tools.ietf.org>
Subject: Re: [dhcwg] Agenda items for IETF75 dhcwg - First Call
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 19 Jun 2009 02:31:28 -0000

Bernie Volz (volz) [mailto://volz@cisco.com] writes:

> It has been 5 weeks ... no progress yet ...

Only 5 weeks?  What a whiner ;-)!  Call back in 5 months & welcome to the
IETF...

...

~ gwz

I'm an advocate of free love.  What else can I say?  I think people should
do what they like, enjoy what they enjoy, and we should enjoy their enjoying
what they enjoy.
  -- Judith Malina




From mellon@fugue.com  Mon Jun 22 15:29:57 2009
Return-Path: <mellon@fugue.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1E77328C28F for <dhcwg@core3.amsl.com>; Mon, 22 Jun 2009 15:29:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RQLxFMAI58xd for <dhcwg@core3.amsl.com>; Mon, 22 Jun 2009 15:29:55 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by core3.amsl.com (Postfix) with ESMTP id 02B8328C281 for <dhcwg@ietf.org>; Mon, 22 Jun 2009 15:29:45 -0700 (PDT)
Received: from [IPv6:2001:470:8:11e:21f:f3ff:fe8b:9f45] (unknown [IPv6:2001:470:8:11e:21f:f3ff:fe8b:9f45]) by toccata.fugue.com (Postfix) with ESMTPSA id 45BA834E445A for <dhcwg@ietf.org>; Mon, 22 Jun 2009 15:32:35 -0700 (MST)
Message-Id: <8BCD585A-B3C5-44BC-8F1A-BEC13048F29E@fugue.com>
From: Ted Lemon <mellon@fugue.com>
To: dhc WG <dhcwg@ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 22 Jun 2009 15:29:56 -0700
X-Mailer: Apple Mail (2.935.3)
Subject: [dhcwg] Comments for draft-ietf-dhc-dhcpv4-leasequery-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 22 Jun 2009 22:29:57 -0000

There are a lot of editorial comments here, and a few comments having  
to do with protocol issues.   I should note that we have had no  
independent readings of the document other than mine, and it received  
no support during the working group last call.   As of now I believe  
the document requires revision before we do another working group last  
call, so there's no need to rush in now and state your support for it.

Thanks to Kim, Bernie, Neil and Mark for their hard work in merging  
the two previous bulk leasequery documents.   I'm sorry my comments  
here are so voluminous, but I feel like they were worth the effort it  
took to do them, and I hope the authors take them as constructive and  
not nitpicky.



This:

The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has been  
extended with a Leasequery capability that allows a requestor 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. This document  
expands on the DHCPv4 Leasequery protocol to allow for bulk transfer  
of DHCPv4 address binding data via TCP.

Might be better worded this way:

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

Page 3:

configured DHCPv4 servers (see Figure 1). In this process, some relay  
agents also glean the lease information sent by the server and  
maintain this locally. This information is used for a variety of  
purposes, including prevention of spoofing attempts from the DHCPv4  
clients and to install routes. When a relay agent reboots, this  
information is frequently lost.

maybe change to this:

configured DHCPv4 servers (see Figure 1). In this process, some relay  
agents also glean lease information sent by the server and cache it  
locally. This information is used for a variety of purposes.   Two  
examples are prevention of spoofing attempts from the DHCPv4 clients,  
and installation of routes. When a relay agent reboots, this  
information is frequently lost.

Page 4:

Different query types are needed where a relay agent can query the  
server without waiting for the traffic from or for the clients, as  
well as a different transmission technique more conducive to the  
transmission of large quantities of data.

maybe change to this:

Some applications require the ability to query the server without  
waiting for traffic from or to clients. This query capability in turn  
requires an underlying transport more suitable to the bulk  
transmission of data.

Page 7:

For a DSLAM having multiple DSL ports, multiple IP addresses may be  
assigned using DHCPv4 to a single port and the number of DHCPv4  
clients on a port may be unknown. The DSLAM may also not know the  
network portions of the IP addresses that are assigned to its DHCPv4  
clients.

maybe change to this:

For a DSLAM having multiple DSL ports, multiple IP addresses may be  
assigned to DHCPv4 clients on a single port and the number of DHCPv4  
clients on that port may be unknown. The DSLAM may also not know the  
network portions of the IP addresses that are assigned to its DHCPv4  
clients.

Page 8:

The existing data driven approach required by [RFC4388] means that the  
Leasequeries can only be performed after an Access Concentrator  
receives data. To implement antispoofing, packets need to be dropped  
until it gets the lease information from DHCPv4 server. If an Access  
Concentrator finishes the Leasequeries before it starts receiving  
data, then there is no need to drop legitimate packets. In this way,  
outage time may be reduced.

to:

The existing data driven approach required by [RFC4388] means that the  
Leasequeries can only be performed after an Access Concentrator  
receives data. To implement antispoofing, the concentrator must drop  
packets for each client until it gets lease information from DHCPv4  
server for that client. If an Access Concentrator finishes the  
Leasequeries before it starts receiving data, then there is no need to  
drop legitimate packets. In this way, outage time may be reduced.

Page 15:

The start-time-of-state option allows the receiver to determine the  
time at which the IP address transitioned into its current state.

to:

The start-time-of-state option allows the receiver to determine the  
time at which the IP address made the transition into its current state.

Page 16, section 7.2.5:

You have a lot of admonitions about what the query start time must be  
and must not be, which I don't think actually communicate what you  
want the implementation to do.   You should just tell the  
implementation how to compute this value; otherwise I don't see how an  
interoperable implementation that follows the rules you've given here  
is possible.

maybe something like this:

7.2.5. query-start-time

The query-start-time option specifies a start query time to the DHCPv4  
server. If specified, only bindings that have changed on or after the  
query-start-time should be included in the response to the query.    
The requester MUST compute the query-start-time relative to a lease it  
has recovered from stable storage, and MUST specify that time in terms  
of the DHCPv4 server's clock at the time of the query recovered from  
stable storage.

For example, suppose the requester had previously received information  
on a lease from the server.   At that time, the server had sent a base- 
time option containing a time of X.   Subsequently the server sent a  
DHCPLEASEACTIVE message with a lease time of Y.   If this is the last  
lease the requester remembers receiving, it would use X+Y for the  
query start time, indicating that it would like to receive all updates  
from that time onward.

The same comment applies to query-end-time.

In section 7.2.7, I don't really understand why the relay agent needs  
to know more than that the lease is still active, or is no longer  
active.   This seems to be an extension on the functionality provided  
by DHCPLEASEQUERY, relating to failover, but (a) it seems unnecessary,  
(b) I have no idea what the DSLAM would do with it, and (c) because of  
that, it seems like it could result in interoperability problems as  
different implementors make different guesses as to how to handle  
it.   You could save a lot of text by just taking this out.   Same  
with data-source.

I can see where it might be helpful to use this for disambiguating in  
cases where one server reports a lease as free and another reports it  
as allocated, but it might be better to simply specify rules for when  
a server should claim to have knowledge about a lease - if a  
particular IP address is in its peer's pool, and is not known to have  
been allocated, perhaps that IP address should simply not be mentioned  
in a DHCPBULKLEASEQUERY reply.   It would be entirely permissible and  
expected in some cases for that to happen.

Page 21:

Messages from the DHCPv4 server come as multiple responses to a single  
DHCPBULKLEASEQUERY message. Thus, each DHCPBULKLEASEQUERY request MUST  
have a xid (transaction-id) unique on the connection on which it is  
sent, and all of the messages which come as a response to it all  
contain the same xid as the request. It is the xid which allows the  
data-streams of two different DHCPBULKLEASEQUERY requests to be  
demultiplexed by the requestor.

to:

Messages from the DHCPv4 server come as multiple responses to a single  
DHCPBULKLEASEQUERY message. Thus, each DHCPBULKLEASEQUERY request MUST  
have a xid (transaction-id) unique on the connection on which it is  
sent.   All of the messages which come as a response to that message  
will contain the same xid as the request. It is the xid which allows  
the data-streams of two different DHCPBULKLEASEQUERY requests to be  
demultiplexed by the requestor.

Page 21:

A requestor MAY send a DHCPBULKLEASEQUERY request to a DHCPv4 server  
and immediately close the transmission side of its TCP connection, and  
then read the resulting response messages from the DHCPv4 server. This  
is not required, and the usual approach is to leave both sides of the  
TCP connection up until at least the conclusion of the Bulk Leasequery.

You don't need to say this; I would take it out.

Page 23:

Both of the query-start-time and query-end-time options (if they  
appear) MUST be in the time context of the DHCPv4 server to which the  
Bulk Leasequery is directed. In the absence of information to the  
contrary, the requestor SHOULD assume that the time context on the  
DHCPv4 server is identical to the time context on the requestor.

In the event that previous operations have determined that the time  
context on the DHCPv4 server to which the Bulk Leasequery is addressed  
differs from the time context of the requestor, the time context of  
the DHCPv4 server MUST be used. Use of the query-start-time or the  
query-end-time options or both can serve to reduce the amount of data  
transferred over the TCP connection by a considerable amount.

You really haven't told us what to do here.   I don't see how  
interoperability can be achieved.   See my comments on these options  
earlier.   I would just delete this text, since you already have text  
explaining this earlier in the document.

Page 23:

If the TCP connection becomes blocked or stops being writeable while  
the requestor is sending its query, the requestor SHOULD be prepared  
to terminate the connection after BULK_LQ_DATA_TIMEOUT. We make this  
recommendation to allow requestors to control the period of time they  
are willing to wait before abandoning a connection, independent of  
notifications from the TCP implementations they may be using.

How does an implementation "prepare to terminate" the connection?   I  
think what you mean is something like this:

The TCP connection may become blocked or stop being writeable while  
the requestor is sending its query.   Should this happen, the  
implementation's behavior is controlled by two variables:  
BULK_LQ_DATA_TIMEOUT, and whatever configuration the operator may have  
provided.   When this situation is detected, the requester SHOULD set  
a timer using the lesser of BULK_LQ_DATA_TIMEOUT or the operator- 
configured timeout.   If that timer expires, the requester SHOULD  
terminate the connection.

This same comment applies to section 8.3, and the prescribed antidote  
is the same.

Also on Page 23:

If a response message does not contain a DHCPv4 server-identifier  
option (option 54), then the server-identifier option from the  
previous message should be used. Thus, the DHCPv4 server MUST send the  
server-identifier option in the first response message, and MAY send  
it in subsequent response message for the same request.

Why aren't you saying this?

The DHCPv4 server MUST send a server-identifier option (option 54) in  
the first response to any DHCPBULKLEASEQUERY message.   The DHCPv4  
server SHOULD NOT send server identifier options in subsequent  
responses to that DHCPBULKLEASEQUERY message.   The requester MUST  
cache the server-identifier option from the first response and apply  
it to any subsequent responses.

(In a large response dataset, the space consumed by repetition of the  
same server-identifier option could be substantial.   Either that, or  
make sending the option mandatory in every message.   If you have to  
have this code in the requester, might as well take advantage of it.)

Section 8.4 is unimplementable as written.   I'm sure it describes an  
implementation that someone has done, but it provides no concrete  
guidance or math for the implementor.   As such, it should either be  
deleted, or made explicit.

Regarding section 8.6, as I've said previously in this commentary, I  
think it would be better to specify the client behavior in such a way  
that the conflicts proposed in this section simply do not happen.    
This section is not specific enough to foster interoperability.

Page 28:

A server MAY process more than one query at a time. A server that does  
not support more than one query at a time on a single connection MUST  
return a DHCPLEASEQUERYDONE message containing a dhcp-message option  
with a status-code of NotAllowed to the unsupported queries.  
Alternatively, a server that does not support more than one query at a  
time on a single connection MAY chose to simply read one query and  
only read any subsequent queries after processing of the current query  
is complete.

There are two problems with this paragraph.   First, you have given  
implementors an option where no option is necessary.   Just specify  
one or the other.   Second, if you specify that the server needn't  
read each message from the connection until it's ready to process it,  
then you need to change the last paragraph in section 8.2, since a  
conforming implementation could easily set up a situation where the  
connection appears to be blocked, which would trigger the requester to  
drop the connection, even though nothing was wrong.

Section 8.8:

Either the requestor or DHCPv4 server MAY close the TCP connection at  
any time. The requestor MAY choose to retain the connection if it  
intends to issue additional queries or if other queries are currently  
using the connection. Note that this requestor behavior does not  
guarantee that the connection will be available for additional  
queries: the server might decide to close the connection based on its  
own configuration.

This seems broken.   It's easy to imagine situations where one side or  
the other closes the connection in compliance with this statement and  
triggers a timeout on the other end which causes legitimate data to be  
discarded.   I think you need to specify a non-error connection  
termination protocol to make this work (and you should - otherwise  
nobody's allowed to close the connection, which would be worse).

In section 9.1, you seem to be specifying an authorization model based  
on the IP source-address of the requestor.   You do not mention this  
in the security considerations section.   This is likely to trigger  
pushback from the IESG.

You use the same "should be prepared" language in these sections that  
you used in section 8.2 and 8.3.   You need to specify exactly what  
the server does, not just say "should be prepared."   The language I  
suggested for section 8.2, with appropriate modifications, would be  
acceptable here as well, at least to me.

Page 30, 31:

A Bulk Leasequery response MUST contain no more than one message for  
each IP address configured in the DHCPv4 server. In addition, a Bulk  
Leasequery may well take significant time between the beginning and  
end of the processing of all of the messages required to satisfy the  
Bulk Leasequery query. During this time, the state of some of the IP  
addresses sent early in the response may change prior to the  
completion of the entire response to the Bulk Leasequery. This is  
normal and expected -- there is no requirement for the entire response  
to a Bulk Leasequery to represent an instantaneous snapshot of the  
state of the IP address bindings of a DHCPv4 server. Quite the  
contrary -- as the cursor moves through the IP addresses in whatever  
order is convenient to the DHCPv4 server, the state of IP addresses  
already examined can change and a DHCPv4 server MUST NOT try to  
examine IP addresses already scanned in an attempt to "keep up" with  
the ongoing state changes of all of the IP addresses. To do so would  
make it difficult to meet the requirement to send only one message per  
IP address in response to a Bulk Leasequery and would also make it  
difficult to know when to finish the Bulk Leasequery.

to:

When responding to a DHCPBULKLEASEQUERY message, the DHCPv4 server  
MUST NOT send more than one message for each applicable IP address,  
even if the state of some of those IP addresses changes during the  
processing of the message.   Updates to such IP address state are  
already handled by normal protocol processing, so no special effort is  
needed here. (I hope!)

Page 33:

A DHCPv4 server MAY always compare the address binding information for  
an IP address against a time window if it follows the following  
guidelines. If there is no query-start-time, then the DHCPv4 server  
MUST assume the query-start-time is equivalent to a time prior to any  
time that resides in any IP address binding. If there is no query- end- 
time, the DHCPv4 server MUST assume that the query-end-time is  
equivalent to a time that is later than any time that resides in any  
IP address binding.

You can't use "MAY" like this.   This text is an implementation  
suggestion; I would suggest that you state this simply in terms of  
requirements, without talking about how those requirements might be  
implemented.

Also page 33:

Even if the query-start-time or query-end-time option value is being  
used to limit the amount of data flow from the DHCPv4 server to the  
requestor, there is no requirement placed on the DHCPv4 server to  
return address binding data in any order and certainly not in any  
order based on time.

When the DHCPv4 server has no additional information to send to the  
requestor, it will send a DHCPLEASEQUERYDONE message.

to:

The DHCPv4 server MAY return address binding data in any order, as  
long as binding information for any given IP address is not  
repeated.   When all binding data for a given DHCPBULKLEASEQUERY has  
been sent, the DHCPv4 server MUST send a DHCPBULKLEASEQUERYDONE message.

Page 34:

[RFC2131] and [RFC4388] specify that every response message MUST  
contain the server-identifier option. However, that option will be the  
same for every response from a particular DHCPBULKLEASEQUERY request.  
Thus, the DHCPv4 server MUST include the server-identifier option in  
the first message sent in response to a DHCPBULKLEASEQUERY. It MAY  
include the server-identifier in later messages as well, but there is  
no requirement for it to do so.

I strongly suggest that you change the MAY here to a SHOULD NOT.    
Also, note that you are repeating something you specified earlier, so  
it would be good to delete one or the other paragraph.

Also on page 34:

The message type of DHCPLEASEACTIVE or DHCPLEASEUNASSIGNED is based on  
the value of the dhcp-state option.  If the dhcp-state option value is  
ACTIVE, then the message type is DHCPLEASEACTIVE, otherwise the  
message type is DHCPLEASEUNASSIGNED.

Once again I suggest you get rid of the dhcp-state message and simply  
say what should happen here for IP addresses that are managed by  
failover and those that are managed by a single server.

Specifically, any IP address that is in the FREE state on the primary  
is DHCPLEASEUNASSIGNED.   Any IP address that is in the BACKUP state  
on the primary is not reported on at all.   Any IP address that is in  
the FREE state on the secondary is not reported on at all.   Any IP  
address that is in the BACKUP state on the secondary is  
DHCPLEASEUNASSIGNED.   Likewise for all the other permutations; I  
think that in any of the states where the failover peer would renew  
the lease, it's active, and in states where it wouldn't renew the  
lease, it's either unassigned, or shouldn't be mentioned.

Also, in point 4, you mention a grace period on the expired state, but  
as far as I know no such thing exists.

Page 35:

As discussed in Section 8.3, requestors may want to leverage an  
existing connection if they need to make multiple queries. Servers MAY  
support reading and processing multiple queries from a single  
connection. A server MUST NOT read more query messages from a  
connection than it is prepared to process simultaneously.

to:

As discussed in Section 8.3, requestors may want to use a connection  
that has already been established when they need to make additional  
queries. Servers MAY support reading and processing multiple queries  
from a single connection. A server MUST NOT read more query messages  
from a connection than it is prepared to process simultaneously.

And:

DHCPv4 server implementations may offer administrative control to  
enable or disable this feature. DHCPv4 server implementations that are  
able to process queries in parallel should offer be configurable to  
limit the number of simultaneous queries permitted from any one  
requester.

[And in total?]

Page 36:

The server MUST close its end of the TCP connection if it encounters  
an error sending data on the connection. The server MUST close its end  
of the TCP connection if it finds that it has to abort an in- process  
request. A server aborting an in-process request SHOULD attempt to  
signal that to its requestors by using the QueryTerminated status code  
in the dhcp-message option in a DHCPLEASEQUERYDONE message, including  
a message string indicating details of the reason for the abort. If  
the server detects that the requesting end of the connection has been  
closed, the server MUST close its end of the connection after it has  
finished processing any outstanding requests.

This is in conflict with section 8.8, which says the server can drop  
the connection at any time.   Also, why should the server finish  
processing outstanding requests if the remote end of the connection  
has closed?   Shouldn't it just drop the connection immediately?

Section 10:

As I mentioned earlier, the only authorization model for this protocol  
is based on the requestor's IP address, and there is no  
authentication.   At a minimum this should be mentioned in the  
security considerations section.

I think the appendix belongs in a requirements document, or on the  
mailing list, not in the draft.


From sangitarajankar@gmail.com  Tue Jun 23 21:41:40 2009
Return-Path: <sangitarajankar@gmail.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 82E503A6F2E for <dhcwg@core3.amsl.com>; Tue, 23 Jun 2009 21:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q9d9-MxtRfRD for <dhcwg@core3.amsl.com>; Tue, 23 Jun 2009 21:41:39 -0700 (PDT)
Received: from mail-pz0-f197.google.com (mail-pz0-f197.google.com [209.85.222.197]) by core3.amsl.com (Postfix) with ESMTP id C04993A67A8 for <dhcwg@ietf.org>; Tue, 23 Jun 2009 21:41:39 -0700 (PDT)
Received: by pzk35 with SMTP id 35so473182pzk.29 for <dhcwg@ietf.org>; Tue, 23 Jun 2009 21:41:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=YNo5IQIPMyxNPcCqQAecJbt0tNedl8nMiYgOC2fE5aA=; b=shMevDXK29AwnbEdAFIId6Tk9qmJh9DrxJxOrAjLr7GfJrqFuQNK5JPrmvQlYPzxdB Lcvf0kx14HDRn9mM+u3efkbTT7oukaL9MNBTWrp6B1B7Qfj3kXQvqi10jrjkLW2Xm47c mSNzcBehaq2xcFu1w7Tn6TSe2uUSfp15r4ZUs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=DoC7h3XgGOlgEFKrJ+JMB3Y5/iOZMpW8yxRTXOzHxJnZFTEXA91fSYxN1z3XjhEmff OOgGZaKnIA+z8ZM0gHw8Gt419EkMerQxLaccAPw8BFWjss2XW8edlDeLXnGdGMD+jfYr Wz/M+blA7n5p/4BcbsJ8qYmY39x3qkqf3fEIw=
MIME-Version: 1.0
Received: by 10.142.161.1 with SMTP id j1mr230447wfe.349.1245818206514; Tue,  23 Jun 2009 21:36:46 -0700 (PDT)
Date: Wed, 24 Jun 2009 10:06:46 +0530
Message-ID: <2853c5340906232136qa9d921aj454a5e6be19bc8c8@mail.gmail.com>
From: Sangita Rajankar <sangitarajankar@gmail.com>
To: dhcwg@ietf.org
Content-Type: multipart/alternative; boundary=000e0cd14ea4a76ec8046d10a73b
Subject: [dhcwg] DHCP using JDHCP
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 24 Jun 2009 04:41:40 -0000

--000e0cd14ea4a76ec8046d10a73b
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi,
I am sangita rajankar, working on network administration. I have developed
DHCP server using JDHCP library. the program is working fine. I just wanted
to share the work with your working group. kindly reply to this.

thanks

with regards

sangita

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

<div>Hi,</div>
<div>I am sangita rajankar, working on network administration. I have devel=
oped DHCP server using JDHCP library. the program is working fine. I just w=
anted to share the work with your working group. kindly reply to this.</div=
>

<div>=A0</div>
<div>thanks</div>
<div>=A0</div>
<div>with regards</div>
<div>=A0</div>
<div>sangita</div>

--000e0cd14ea4a76ec8046d10a73b--

From David.Miles@alcatel-lucent.com.au  Wed Jun 24 01:32:34 2009
Return-Path: <David.Miles@alcatel-lucent.com.au>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2B7BA28C128 for <dhcwg@core3.amsl.com>; Wed, 24 Jun 2009 01:32:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KKHeOiVvBcjh for <dhcwg@core3.amsl.com>; Wed, 24 Jun 2009 01:32:31 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by core3.amsl.com (Postfix) with ESMTP id 9D9B73A6863 for <dhcwg@ietf.org>; Wed, 24 Jun 2009 01:32:31 -0700 (PDT)
Received: from ihrh1.emsr.lucent.com (h135-1-218-53.lucent.com [135.1.218.53]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id n5O8WKKt005476;  Wed, 24 Jun 2009 03:32:20 -0500 (CDT)
Received: from mail.apac.alcatel-lucent.com (h202-65-2-130.alcatel.com [202.65.2.130]) by ihrh1.emsr.lucent.com (8.13.8/emsr) with ESMTP id n5O8WHdY021741; Wed, 24 Jun 2009 03:32:18 -0500 (CDT)
Received: from sgsinsbhs02.ad4.ad.alcatel.com (sgsinsbhs02.ap.lucent.com [135.254.109.35]) by mail.apac.alcatel-lucent.com (8.13.7/8.13.7/Alcanet1.0) with ESMTP id n5O8Sxs1024843; Wed, 24 Jun 2009 16:29:00 +0800
Received: from SGSINSMBS02.ad4.ad.alcatel.com ([135.254.109.29]) by sgsinsbhs02.ad4.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 24 Jun 2009 16:32:14 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 24 Jun 2009 16:32:07 +0800
Message-ID: <986DCE2E44129444B6435ABE8C9E424D03832D3F@SGSINSMBS02.ad4.ad.alcatel.com>
In-Reply-To: <8BCD585A-B3C5-44BC-8F1A-BEC13048F29E@fugue.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Comments for draft-ietf-dhc-dhcpv4-leasequery-00.txt
Thread-Index: AcnziRUBDpHGZd5hRh28DncwMQXnJwBHEGsg
References: <8BCD585A-B3C5-44BC-8F1A-BEC13048F29E@fugue.com>
From: "MILES DAVID" <David.Miles@alcatel-lucent.com.au>
To: "Ted Lemon" <mellon@fugue.com>, "dhc WG" <dhcwg@ietf.org>
X-OriginalArrivalTime: 24 Jun 2009 08:32:14.0123 (UTC) FILETIME=[467EBFB0:01C9F4A6]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 202.65.2.130
Subject: Re: [dhcwg] Comments for draft-ietf-dhc-dhcpv4-leasequery-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 24 Jun 2009 08:32:34 -0000

Additional comments - Ted's comments are much more specific whereas I'm
asking some questions re general approach. Sorry for their lateness.

1) Is very DSLAM centric - suggest we need to generalize the use case to
any relay agent. The background re fast/slow path in the Motivation
section is unnecessary. Suggest Motivation can be boiled down to
"extending the current individual Leasequery protocol [RFC 4388] to
support a bulk query".

2) Notice that as a new proposal this has a lot of commonality with the
SAVI protocols for anti-spoofing.

3) Section 7.2.1 assigns new DHCP message type values - these should be
TBA/IANA.

4) Section 7.2.2 proposes dhcp-message formats that are somewhat
confusing: it specifies constrained format 3 character ASCII field where
the characters must be base10. As the table appears to be simple
incrementing error codes I would suggest an simple 16-bit result code
and associated table vs the left-, middle-, right-number format in
7.2.2. I do not think we should overload option 56 for error messages as
currently opt 56 is defined for text to display to end-client. I don't
see any harm in creating a new DHCP option for lease-query to convey
server-to-relay errors/results (ie, as done with the base-time and
start-time-of-state messages).

5) I dont think we should mix absolute and relative time scales in the
same single message. As currently proposed base-time is an absolute time
and all other time values are offsets from this base-time option. Is
there a way we can avoid absolute times all together thus avoiding the
need for time sync between relay and DHCP server? Given the leasequery
returns things like lease (which are timers) could we not get away with
returning the remaining lease time? I'm not sure I can appreciate value
in the relay agent knowing what the original lease time was.

6) With section 7.2.5/7.2.6 I feel we are overcomplicating the query
with time ranges. Why would a relay agent not want to recover all leases
- further this requires a DHCP server to maintain an explicit
last-modified time for every lease.

7) The states RELEASED, ABANDONED, RESET suggest the server keeps state
of leases that have expired - I can see that this is a function of the
time-based query - but it puts a huge burden on a DHCP server. See point
6 wrt returning all valid leases. These time-bound queries could lead to
out-of-sync problems between server and relay and as the motivation
appears to be state recovery it seems pragmatic to return all state
instead of a time-based subset. In reality how many relay-agents could
even implement a time-bound query after a reload (ie, do they really
know the second they were rebooted or lost power)?

8) This proposal requires a TCP connection between server and relay
agent thus necessitating an IP address on the relay agent. This seems to
be at odds with the objectives outlined in the L2 Relay and LDRA drafts.
In these drafts relay-agent (often a DSLAM) does -not- require an IP
address nor is it desirable. This proposal will require the DSLAM has an
IP address that is routable to the DHCP server - also the draft says in
section 5 that "No relaying of Bulk Leasequery messages is specified".
This means a logical topology change in many ISP networks and is not
aligned with the broadband architectures put forward by other
organisations like Broadband Forum TR-101.


BR,

-d

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Ted Lemon
Sent: Tuesday, June 23, 2009 8:00 AM
To: dhc WG
Subject: [dhcwg] Comments for draft-ietf-dhc-dhcpv4-leasequery-00.txt

There are a lot of editorial comments here, and a few comments having =20
to do with protocol issues.   I should note that we have had no =20
independent readings of the document other than mine, and it received =20
no support during the working group last call.   As of now I believe =20
the document requires revision before we do another working group last =20
call, so there's no need to rush in now and state your support for it.

Thanks to Kim, Bernie, Neil and Mark for their hard work in merging =20
the two previous bulk leasequery documents.   I'm sorry my comments =20
here are so voluminous, but I feel like they were worth the effort it =20
took to do them, and I hope the authors take them as constructive and =20
not nitpicky.



This:

The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has been =20
extended with a Leasequery capability that allows a requestor to =20
request information about DHCPv4 bindings. That mechanism is limited =20
to queries for individual bindings. In some situations individual =20
binding queries may not be efficient, or even possible. This document =20
expands on the DHCPv4 Leasequery protocol to allow for bulk transfer =20
of DHCPv4 address binding data via TCP.

Might be better worded this way:

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

Page 3:

configured DHCPv4 servers (see Figure 1). In this process, some relay =20
agents also glean the lease information sent by the server and =20
maintain this locally. This information is used for a variety of =20
purposes, including prevention of spoofing attempts from the DHCPv4 =20
clients and to install routes. When a relay agent reboots, this =20
information is frequently lost.

maybe change to this:

configured DHCPv4 servers (see Figure 1). In this process, some relay =20
agents also glean lease information sent by the server and cache it =20
locally. This information is used for a variety of purposes.   Two =20
examples are prevention of spoofing attempts from the DHCPv4 clients, =20
and installation of routes. When a relay agent reboots, this =20
information is frequently lost.

Page 4:

Different query types are needed where a relay agent can query the =20
server without waiting for the traffic from or for the clients, as =20
well as a different transmission technique more conducive to the =20
transmission of large quantities of data.

maybe change to this:

Some applications require the ability to query the server without =20
waiting for traffic from or to clients. This query capability in turn =20
requires an underlying transport more suitable to the bulk =20
transmission of data.

Page 7:

For a DSLAM having multiple DSL ports, multiple IP addresses may be =20
assigned using DHCPv4 to a single port and the number of DHCPv4 =20
clients on a port may be unknown. The DSLAM may also not know the =20
network portions of the IP addresses that are assigned to its DHCPv4 =20
clients.

maybe change to this:

For a DSLAM having multiple DSL ports, multiple IP addresses may be =20
assigned to DHCPv4 clients on a single port and the number of DHCPv4 =20
clients on that port may be unknown. The DSLAM may also not know the =20
network portions of the IP addresses that are assigned to its DHCPv4 =20
clients.

Page 8:

The existing data driven approach required by [RFC4388] means that the =20
Leasequeries can only be performed after an Access Concentrator =20
receives data. To implement antispoofing, packets need to be dropped =20
until it gets the lease information from DHCPv4 server. If an Access =20
Concentrator finishes the Leasequeries before it starts receiving =20
data, then there is no need to drop legitimate packets. In this way, =20
outage time may be reduced.

to:

The existing data driven approach required by [RFC4388] means that the =20
Leasequeries can only be performed after an Access Concentrator =20
receives data. To implement antispoofing, the concentrator must drop =20
packets for each client until it gets lease information from DHCPv4 =20
server for that client. If an Access Concentrator finishes the =20
Leasequeries before it starts receiving data, then there is no need to =20
drop legitimate packets. In this way, outage time may be reduced.

Page 15:

The start-time-of-state option allows the receiver to determine the =20
time at which the IP address transitioned into its current state.

to:

The start-time-of-state option allows the receiver to determine the =20
time at which the IP address made the transition into its current state.

Page 16, section 7.2.5:

You have a lot of admonitions about what the query start time must be =20
and must not be, which I don't think actually communicate what you =20
want the implementation to do.   You should just tell the =20
implementation how to compute this value; otherwise I don't see how an =20
interoperable implementation that follows the rules you've given here =20
is possible.

maybe something like this:

7.2.5. query-start-time

The query-start-time option specifies a start query time to the DHCPv4 =20
server. If specified, only bindings that have changed on or after the =20
query-start-time should be included in the response to the query.   =20
The requester MUST compute the query-start-time relative to a lease it =20
has recovered from stable storage, and MUST specify that time in terms =20
of the DHCPv4 server's clock at the time of the query recovered from =20
stable storage.

For example, suppose the requester had previously received information =20
on a lease from the server.   At that time, the server had sent a base-=20
time option containing a time of X.   Subsequently the server sent a =20
DHCPLEASEACTIVE message with a lease time of Y.   If this is the last =20
lease the requester remembers receiving, it would use X+Y for the =20
query start time, indicating that it would like to receive all updates =20
from that time onward.

The same comment applies to query-end-time.

In section 7.2.7, I don't really understand why the relay agent needs =20
to know more than that the lease is still active, or is no longer =20
active.   This seems to be an extension on the functionality provided =20
by DHCPLEASEQUERY, relating to failover, but (a) it seems unnecessary, =20
(b) I have no idea what the DSLAM would do with it, and (c) because of =20
that, it seems like it could result in interoperability problems as =20
different implementors make different guesses as to how to handle =20
it.   You could save a lot of text by just taking this out.   Same =20
with data-source.

I can see where it might be helpful to use this for disambiguating in =20
cases where one server reports a lease as free and another reports it =20
as allocated, but it might be better to simply specify rules for when =20
a server should claim to have knowledge about a lease - if a =20
particular IP address is in its peer's pool, and is not known to have =20
been allocated, perhaps that IP address should simply not be mentioned =20
in a DHCPBULKLEASEQUERY reply.   It would be entirely permissible and =20
expected in some cases for that to happen.

Page 21:

Messages from the DHCPv4 server come as multiple responses to a single =20
DHCPBULKLEASEQUERY message. Thus, each DHCPBULKLEASEQUERY request MUST =20
have a xid (transaction-id) unique on the connection on which it is =20
sent, and all of the messages which come as a response to it all =20
contain the same xid as the request. It is the xid which allows the =20
data-streams of two different DHCPBULKLEASEQUERY requests to be =20
demultiplexed by the requestor.

to:

Messages from the DHCPv4 server come as multiple responses to a single =20
DHCPBULKLEASEQUERY message. Thus, each DHCPBULKLEASEQUERY request MUST =20
have a xid (transaction-id) unique on the connection on which it is =20
sent.   All of the messages which come as a response to that message =20
will contain the same xid as the request. It is the xid which allows =20
the data-streams of two different DHCPBULKLEASEQUERY requests to be =20
demultiplexed by the requestor.

Page 21:

A requestor MAY send a DHCPBULKLEASEQUERY request to a DHCPv4 server =20
and immediately close the transmission side of its TCP connection, and =20
then read the resulting response messages from the DHCPv4 server. This =20
is not required, and the usual approach is to leave both sides of the =20
TCP connection up until at least the conclusion of the Bulk Leasequery.

You don't need to say this; I would take it out.

Page 23:

Both of the query-start-time and query-end-time options (if they =20
appear) MUST be in the time context of the DHCPv4 server to which the =20
Bulk Leasequery is directed. In the absence of information to the =20
contrary, the requestor SHOULD assume that the time context on the =20
DHCPv4 server is identical to the time context on the requestor.

In the event that previous operations have determined that the time =20
context on the DHCPv4 server to which the Bulk Leasequery is addressed =20
differs from the time context of the requestor, the time context of =20
the DHCPv4 server MUST be used. Use of the query-start-time or the =20
query-end-time options or both can serve to reduce the amount of data =20
transferred over the TCP connection by a considerable amount.

You really haven't told us what to do here.   I don't see how =20
interoperability can be achieved.   See my comments on these options =20
earlier.   I would just delete this text, since you already have text =20
explaining this earlier in the document.

Page 23:

If the TCP connection becomes blocked or stops being writeable while =20
the requestor is sending its query, the requestor SHOULD be prepared =20
to terminate the connection after BULK_LQ_DATA_TIMEOUT. We make this =20
recommendation to allow requestors to control the period of time they =20
are willing to wait before abandoning a connection, independent of =20
notifications from the TCP implementations they may be using.

How does an implementation "prepare to terminate" the connection?   I =20
think what you mean is something like this:

The TCP connection may become blocked or stop being writeable while =20
the requestor is sending its query.   Should this happen, the =20
implementation's behavior is controlled by two variables: =20
BULK_LQ_DATA_TIMEOUT, and whatever configuration the operator may have =20
provided.   When this situation is detected, the requester SHOULD set =20
a timer using the lesser of BULK_LQ_DATA_TIMEOUT or the operator-=20
configured timeout.   If that timer expires, the requester SHOULD =20
terminate the connection.

This same comment applies to section 8.3, and the prescribed antidote =20
is the same.

Also on Page 23:

If a response message does not contain a DHCPv4 server-identifier =20
option (option 54), then the server-identifier option from the =20
previous message should be used. Thus, the DHCPv4 server MUST send the =20
server-identifier option in the first response message, and MAY send =20
it in subsequent response message for the same request.

Why aren't you saying this?

The DHCPv4 server MUST send a server-identifier option (option 54) in =20
the first response to any DHCPBULKLEASEQUERY message.   The DHCPv4 =20
server SHOULD NOT send server identifier options in subsequent =20
responses to that DHCPBULKLEASEQUERY message.   The requester MUST =20
cache the server-identifier option from the first response and apply =20
it to any subsequent responses.

(In a large response dataset, the space consumed by repetition of the =20
same server-identifier option could be substantial.   Either that, or =20
make sending the option mandatory in every message.   If you have to =20
have this code in the requester, might as well take advantage of it.)

Section 8.4 is unimplementable as written.   I'm sure it describes an =20
implementation that someone has done, but it provides no concrete =20
guidance or math for the implementor.   As such, it should either be =20
deleted, or made explicit.

Regarding section 8.6, as I've said previously in this commentary, I =20
think it would be better to specify the client behavior in such a way =20
that the conflicts proposed in this section simply do not happen.   =20
This section is not specific enough to foster interoperability.

Page 28:

A server MAY process more than one query at a time. A server that does =20
not support more than one query at a time on a single connection MUST =20
return a DHCPLEASEQUERYDONE message containing a dhcp-message option =20
with a status-code of NotAllowed to the unsupported queries. =20
Alternatively, a server that does not support more than one query at a =20
time on a single connection MAY chose to simply read one query and =20
only read any subsequent queries after processing of the current query =20
is complete.

There are two problems with this paragraph.   First, you have given =20
implementors an option where no option is necessary.   Just specify =20
one or the other.   Second, if you specify that the server needn't =20
read each message from the connection until it's ready to process it, =20
then you need to change the last paragraph in section 8.2, since a =20
conforming implementation could easily set up a situation where the =20
connection appears to be blocked, which would trigger the requester to =20
drop the connection, even though nothing was wrong.

Section 8.8:

Either the requestor or DHCPv4 server MAY close the TCP connection at =20
any time. The requestor MAY choose to retain the connection if it =20
intends to issue additional queries or if other queries are currently =20
using the connection. Note that this requestor behavior does not =20
guarantee that the connection will be available for additional =20
queries: the server might decide to close the connection based on its =20
own configuration.

This seems broken.   It's easy to imagine situations where one side or =20
the other closes the connection in compliance with this statement and =20
triggers a timeout on the other end which causes legitimate data to be =20
discarded.   I think you need to specify a non-error connection =20
termination protocol to make this work (and you should - otherwise =20
nobody's allowed to close the connection, which would be worse).

In section 9.1, you seem to be specifying an authorization model based =20
on the IP source-address of the requestor.   You do not mention this =20
in the security considerations section.   This is likely to trigger =20
pushback from the IESG.

You use the same "should be prepared" language in these sections that =20
you used in section 8.2 and 8.3.   You need to specify exactly what =20
the server does, not just say "should be prepared."   The language I =20
suggested for section 8.2, with appropriate modifications, would be =20
acceptable here as well, at least to me.

Page 30, 31:

A Bulk Leasequery response MUST contain no more than one message for =20
each IP address configured in the DHCPv4 server. In addition, a Bulk =20
Leasequery may well take significant time between the beginning and =20
end of the processing of all of the messages required to satisfy the =20
Bulk Leasequery query. During this time, the state of some of the IP =20
addresses sent early in the response may change prior to the =20
completion of the entire response to the Bulk Leasequery. This is =20
normal and expected -- there is no requirement for the entire response =20
to a Bulk Leasequery to represent an instantaneous snapshot of the =20
state of the IP address bindings of a DHCPv4 server. Quite the =20
contrary -- as the cursor moves through the IP addresses in whatever =20
order is convenient to the DHCPv4 server, the state of IP addresses =20
already examined can change and a DHCPv4 server MUST NOT try to =20
examine IP addresses already scanned in an attempt to "keep up" with =20
the ongoing state changes of all of the IP addresses. To do so would =20
make it difficult to meet the requirement to send only one message per =20
IP address in response to a Bulk Leasequery and would also make it =20
difficult to know when to finish the Bulk Leasequery.

to:

When responding to a DHCPBULKLEASEQUERY message, the DHCPv4 server =20
MUST NOT send more than one message for each applicable IP address, =20
even if the state of some of those IP addresses changes during the =20
processing of the message.   Updates to such IP address state are =20
already handled by normal protocol processing, so no special effort is =20
needed here. (I hope!)

Page 33:

A DHCPv4 server MAY always compare the address binding information for =20
an IP address against a time window if it follows the following =20
guidelines. If there is no query-start-time, then the DHCPv4 server =20
MUST assume the query-start-time is equivalent to a time prior to any =20
time that resides in any IP address binding. If there is no query- end-=20
time, the DHCPv4 server MUST assume that the query-end-time is =20
equivalent to a time that is later than any time that resides in any =20
IP address binding.

You can't use "MAY" like this.   This text is an implementation =20
suggestion; I would suggest that you state this simply in terms of =20
requirements, without talking about how those requirements might be =20
implemented.

Also page 33:

Even if the query-start-time or query-end-time option value is being =20
used to limit the amount of data flow from the DHCPv4 server to the =20
requestor, there is no requirement placed on the DHCPv4 server to =20
return address binding data in any order and certainly not in any =20
order based on time.

When the DHCPv4 server has no additional information to send to the =20
requestor, it will send a DHCPLEASEQUERYDONE message.

to:

The DHCPv4 server MAY return address binding data in any order, as =20
long as binding information for any given IP address is not =20
repeated.   When all binding data for a given DHCPBULKLEASEQUERY has =20
been sent, the DHCPv4 server MUST send a DHCPBULKLEASEQUERYDONE message.

Page 34:

[RFC2131] and [RFC4388] specify that every response message MUST =20
contain the server-identifier option. However, that option will be the =20
same for every response from a particular DHCPBULKLEASEQUERY request. =20
Thus, the DHCPv4 server MUST include the server-identifier option in =20
the first message sent in response to a DHCPBULKLEASEQUERY. It MAY =20
include the server-identifier in later messages as well, but there is =20
no requirement for it to do so.

I strongly suggest that you change the MAY here to a SHOULD NOT.   =20
Also, note that you are repeating something you specified earlier, so =20
it would be good to delete one or the other paragraph.

Also on page 34:

The message type of DHCPLEASEACTIVE or DHCPLEASEUNASSIGNED is based on =20
the value of the dhcp-state option.  If the dhcp-state option value is =20
ACTIVE, then the message type is DHCPLEASEACTIVE, otherwise the =20
message type is DHCPLEASEUNASSIGNED.

Once again I suggest you get rid of the dhcp-state message and simply =20
say what should happen here for IP addresses that are managed by =20
failover and those that are managed by a single server.

Specifically, any IP address that is in the FREE state on the primary =20
is DHCPLEASEUNASSIGNED.   Any IP address that is in the BACKUP state =20
on the primary is not reported on at all.   Any IP address that is in =20
the FREE state on the secondary is not reported on at all.   Any IP =20
address that is in the BACKUP state on the secondary is =20
DHCPLEASEUNASSIGNED.   Likewise for all the other permutations; I =20
think that in any of the states where the failover peer would renew =20
the lease, it's active, and in states where it wouldn't renew the =20
lease, it's either unassigned, or shouldn't be mentioned.

Also, in point 4, you mention a grace period on the expired state, but =20
as far as I know no such thing exists.

Page 35:

As discussed in Section 8.3, requestors may want to leverage an =20
existing connection if they need to make multiple queries. Servers MAY =20
support reading and processing multiple queries from a single =20
connection. A server MUST NOT read more query messages from a =20
connection than it is prepared to process simultaneously.

to:

As discussed in Section 8.3, requestors may want to use a connection =20
that has already been established when they need to make additional =20
queries. Servers MAY support reading and processing multiple queries =20
from a single connection. A server MUST NOT read more query messages =20
from a connection than it is prepared to process simultaneously.

And:

DHCPv4 server implementations may offer administrative control to =20
enable or disable this feature. DHCPv4 server implementations that are =20
able to process queries in parallel should offer be configurable to =20
limit the number of simultaneous queries permitted from any one =20
requester.

[And in total?]

Page 36:

The server MUST close its end of the TCP connection if it encounters =20
an error sending data on the connection. The server MUST close its end =20
of the TCP connection if it finds that it has to abort an in- process =20
request. A server aborting an in-process request SHOULD attempt to =20
signal that to its requestors by using the QueryTerminated status code =20
in the dhcp-message option in a DHCPLEASEQUERYDONE message, including =20
a message string indicating details of the reason for the abort. If =20
the server detects that the requesting end of the connection has been =20
closed, the server MUST close its end of the connection after it has =20
finished processing any outstanding requests.

This is in conflict with section 8.8, which says the server can drop =20
the connection at any time.   Also, why should the server finish =20
processing outstanding requests if the remote end of the connection =20
has closed?   Shouldn't it just drop the connection immediately?

Section 10:

As I mentioned earlier, the only authorization model for this protocol =20
is based on the requestor's IP address, and there is no =20
authentication.   At a minimum this should be mentioned in the =20
security considerations section.

I think the appendix belongs in a requirements document, or on the =20
mailing list, not in the draft.

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

From mellon@fugue.com  Wed Jun 24 17:19:13 2009
Return-Path: <mellon@fugue.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B7BF23A6DA8 for <dhcwg@core3.amsl.com>; Wed, 24 Jun 2009 17:19:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vT5iL-5K2k82 for <dhcwg@core3.amsl.com>; Wed, 24 Jun 2009 17:19:12 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by core3.amsl.com (Postfix) with ESMTP id C42DB3A69A3 for <dhcwg@ietf.org>; Wed, 24 Jun 2009 17:18:38 -0700 (PDT)
Received: from [IPv6:2001:470:8:11e:21f:f3ff:fe8b:9f45] (unknown [IPv6:2001:470:8:11e:21f:f3ff:fe8b:9f45]) by toccata.fugue.com (Postfix) with ESMTPSA id D1F6234E446F for <dhcwg@ietf.org>; Wed, 24 Jun 2009 17:21:36 -0700 (MST)
Message-Id: <01820741-C028-4091-BF37-190DA261AE9F@fugue.com>
From: Ted Lemon <mellon@fugue.com>
To: dhc WG <dhcwg@ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Wed, 24 Jun 2009 17:18:52 -0700
X-Mailer: Apple Mail (2.935.3)
Subject: [dhcwg] draft-miles-dhc-dhcpv5-ldra-02.txt: adopt as a working group item?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 25 Jun 2009 00:19:13 -0000

This is something we discussed in the meeting in San Francisco.   The  
consensus there was to adopt.   So unless there are objections here,  
we will adopt this as a working group item.   We'll wait until next  
Wednesday, June 24th at 5:00 PST; if no objections are heard by then,  
LDRA will become a working group item.


From root@core3.amsl.com  Wed Jun 24 17:45:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: dhcwg@ietf.org
Delivered-To: dhcwg@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 5B02B3A6B32; Wed, 24 Jun 2009 17:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090625004501.5B02B3A6B32@core3.amsl.com>
Date: Wed, 24 Jun 2009 17:45:01 -0700 (PDT)
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action:draft-ietf-dhc-forcerenew-nonce-00.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 25 Jun 2009 00:45:01 -0000

--NextPart

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           : Forcerenew Nonce Authentication
	Author(s)       : D. Miles, et al.
	Filename        : draft-ietf-dhc-forcerenew-nonce-00.txt
	Pages           : 11
	Date            : 2009-06-03

DHCP Forcerenew allows for the reconfiguration of a single host by
forcing the DHCP client into a Renew state on a trigger from the DHCP
server.  In Forcerenew Nonce Authentication the server exchanges a
nonce with the client on the initial DHCP ACK that is used for
subsequent validation of a Forcerenew message.

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

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

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-dhc-forcerenew-nonce-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-06-24173032.I-D@ietf.org>


--NextPart--

From Ted.Lemon@nominum.com  Thu Jun 25 00:33:31 2009
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D18583A6C5D for <dhcwg@core3.amsl.com>; Thu, 25 Jun 2009 00:33:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.248
X-Spam-Level: 
X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5 tests=[AWL=0.351,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yKbV-OAv1PTJ for <dhcwg@core3.amsl.com>; Thu, 25 Jun 2009 00:33:31 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by core3.amsl.com (Postfix) with ESMTP id A737B3A6AAC for <dhcwg@ietf.org>; Thu, 25 Jun 2009 00:33:30 -0700 (PDT)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKSkMoGLfjuJWUuEqUelxlK7g7c29JCDlN@postini.com; Thu, 25 Jun 2009 00:33:48 PDT
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 498731BD0A3 for <dhcwg@ietf.org>; Thu, 25 Jun 2009 00:32:52 -0700 (PDT)
Received: from uma.here (71.32.40.139) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.1.336.0; Thu, 25 Jun 2009 00:32:39 -0700
Message-ID: <533DAB08-0708-477B-BB4F-DB27B37EF869@nominum.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
To: dhc WG <dhcwg@ietf.org>
In-Reply-To: <01820741-C028-4091-BF37-190DA261AE9F@fugue.com>
Content-Type: text/plain; charset="US-ASCII"; format=flowed
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 (Apple Message framework v935.3)
Date: Thu, 25 Jun 2009 00:32:38 -0700
References: <01820741-C028-4091-BF37-190DA261AE9F@fugue.com>
X-Mailer: Apple Mail (2.935.3)
Subject: Re: [dhcwg] draft-miles-dhc-dhcpv5-ldra-02.txt: adopt as a working group item?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 25 Jun 2009 07:33:31 -0000

On Jun 24, 2009, at 5:18 PM, Ted Lemon wrote:
> We'll wait until next
> Wednesday, June 24th at 5:00 PST; if no objections are heard by then,
> LDRA will become a working group item.

That's next Wednesday, July 1 at 5:00 PM PST, just to be clear...   :'}

From Ted.Lemon@nominum.com  Thu Jun 25 00:57:22 2009
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 260E33A6D71 for <dhcwg@core3.amsl.com>; Thu, 25 Jun 2009 00:57:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.336
X-Spam-Level: 
X-Spam-Status: No, score=-6.336 tagged_above=-999 required=5 tests=[AWL=0.263,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hDNrAs2u5-FE for <dhcwg@core3.amsl.com>; Thu, 25 Jun 2009 00:57:21 -0700 (PDT)
Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by core3.amsl.com (Postfix) with ESMTP id 1C1203A6896 for <dhcwg@ietf.org>; Thu, 25 Jun 2009 00:57:21 -0700 (PDT)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP ID DSNKSkMtinUKody60Zac0ulw4hvSCjx57yiY@postini.com; Thu, 25 Jun 2009 00:57:39 PDT
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 93EE21BD089 for <dhcwg@ietf.org>; Thu, 25 Jun 2009 00:27:31 -0700 (PDT)
Received: from uma.here (71.32.40.139) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.1.336.0; Thu, 25 Jun 2009 00:27:18 -0700
Message-ID: <C32CD809-6BF9-4817-88ED-A734E6EF3FD6@nominum.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
To: dhc WG <dhcwg@ietf.org>
Content-Type: text/plain; charset="US-ASCII"; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 (Apple Message framework v935.3)
Date: Thu, 25 Jun 2009 00:27:17 -0700
X-Mailer: Apple Mail (2.935.3)
Subject: [dhcwg] Add WG item: draft-hunt-dhcpv6-clarify-mrc-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 25 Jun 2009 07:57:22 -0000

This was discussed at the San Francisco IETF, and the consensus in the  
room was to adopt it as a working group item.   The draft clarifies an  
ambiguity in the handling of the Maximum Retry Count (MRC) constant.   
This draft will become a working group item if no objections are heard  
prior to Thursday, 7/2/2009, by 5:00 pm.


From volz@cisco.com  Thu Jun 25 19:06:05 2009
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1FBF33A693B for <dhcwg@core3.amsl.com>; Thu, 25 Jun 2009 19:06:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SF+WNERqCG8l for <dhcwg@core3.amsl.com>; Thu, 25 Jun 2009 19:06:04 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 1DECE3A687C for <dhcwg@ietf.org>; Thu, 25 Jun 2009 19:06:04 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,294,1243814400"; d="scan'208";a="332049825"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 26 Jun 2009 02:06:14 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n5Q26EiS008323;  Thu, 25 Jun 2009 19:06:14 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n5Q268LF019875; Fri, 26 Jun 2009 02:06:14 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 25 Jun 2009 22:06:13 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 25 Jun 2009 22:06:11 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB210D698F94@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <C32CD809-6BF9-4817-88ED-A734E6EF3FD6@nominum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Add WG item: draft-hunt-dhcpv6-clarify-mrc-00
Thread-Index: Acn1ap/JN7tvxpG9QUaEKvZfA+FCxgAl3HKA
References: <C32CD809-6BF9-4817-88ED-A734E6EF3FD6@nominum.com>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Ted Lemon" <Ted.Lemon@nominum.com>, "dhc WG" <dhcwg@ietf.org>
X-OriginalArrivalTime: 26 Jun 2009 02:06:13.0255 (UTC) FILETIME=[AE5E4170:01C9F602]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1365; t=1245981974; x=1246845974; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=volz@cisco.com; z=From:=20=22Bernie=20Volz=20(volz)=22=20<volz@cisco.com> |Subject:=20RE=3A=20[dhcwg]=20Add=20WG=20item=3A=20draft-hu nt-dhcpv6-clarify-mrc-00 |Sender:=20; bh=ofC9lN5FIeOPBjzsvtoeUXyt7pq2SKVrj1/LL1ne5DM=; b=MXpUPzckx5MGLJDsxN7iHTMWOh4/hiAczS/wDHKNwW3j4u0m+Pp4UC14bo zaMwwrE6z2kpGJ3xdt/gygvSxxW4I4p0Su2qt3nc6TNiW/bi+fEAlFrOUzFW +TuEU8dW0z;
Authentication-Results: sj-dkim-2; header.From=volz@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Subject: Re: [dhcwg] Add WG item: draft-hunt-dhcpv6-clarify-mrc-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 26 Jun 2009 02:06:05 -0000

While I have no objection to taking this on, I do wonder whether it is
time for the DHC WG to consider a 3315bis document. I'd be willing to
work on this (as "editor"). And, I think it would be preferable to have
a 'new' replacement document rather than having lots of little documents
(though getting to the replacement document may take some time).

So, for the MRC issue, I'd prefer to see this rolled into a 3315bis
rather than having it end up as its own RFC.

Perhaps something the DHC chairs can discuss at the Stockholm IETF (I
don't be there as I'll be in China for the July 22, 2009 total solar
eclipse and sightseeing).

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Ted Lemon
Sent: Thursday, June 25, 2009 3:27 AM
To: dhc WG
Subject: [dhcwg] Add WG item: draft-hunt-dhcpv6-clarify-mrc-00

This was discussed at the San Francisco IETF, and the consensus in the =20
room was to adopt it as a working group item.   The draft clarifies an =20
ambiguity in the handling of the Maximum Retry Count (MRC) constant.  =20
This draft will become a working group item if no objections are heard =20
prior to Thursday, 7/2/2009, by 5:00 pm.

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

From volz@cisco.com  Fri Jun 26 06:07:39 2009
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 96EC63A6AE0 for <dhcwg@core3.amsl.com>; Fri, 26 Jun 2009 06:07:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hBWWq2FiRYKb for <dhcwg@core3.amsl.com>; Fri, 26 Jun 2009 06:07:38 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 4D4FF3A6ADF for <dhcwg@ietf.org>; Fri, 26 Jun 2009 06:07:38 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,296,1243814400"; d="scan'208";a="173147283"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by sj-iport-3.cisco.com with ESMTP; 26 Jun 2009 13:05:10 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n5QD59oe020728;  Fri, 26 Jun 2009 09:05:09 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n5QD59di005218; Fri, 26 Jun 2009 13:05:09 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 26 Jun 2009 09:05:09 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 26 Jun 2009 09:05:08 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB210D699039@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <20090626042727.GA46169@isc.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Add WG item: draft-hunt-dhcpv6-clarify-mrc-00
Thread-Index: Acn2FmtGZwQLVtPIQhyFYa2yG9hqFAARfbCg
References: <C32CD809-6BF9-4817-88ED-A734E6EF3FD6@nominum.com> <8E296595B6471A4689555D5D725EBB210D698F94@xmb-rtp-20a.amer.cisco.com> <20090626042727.GA46169@isc.org>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Evan Hunt" <each@isc.org>
X-OriginalArrivalTime: 26 Jun 2009 13:05:09.0141 (UTC) FILETIME=[BB97B450:01C9F65E]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2739; t=1246021509; x=1246885509; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=volz@cisco.com; z=From:=20=22Bernie=20Volz=20(volz)=22=20<volz@cisco.com> |Subject:=20RE=3A=20[dhcwg]=20Add=20WG=20item=3A=20draft-hu nt-dhcpv6-clarify-mrc-00 |Sender:=20 |To:=20=22Evan=20Hunt=22=20<each@isc.org>; bh=DMYvM2FAf045apwAYNbnWZ9ZxlIIPZD3dpNMIqbrmhY=; b=IDqXukdcLwHNUh9mjmkKtLFnWr6zo8UWJnAcuLKidJDie628JRfMU9Timb 2rO/J+SN83nsj30bl0BfucaeEY2VI5lsDusU4z/wq9y9pjaWYewJ7Z7Q/1kW Ulq+vEoX/H;
Authentication-Results: rtp-dkim-2; header.From=volz@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); 
Cc: dhc WG <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Add WG item: draft-hunt-dhcpv6-clarify-mrc-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 26 Jun 2009 13:07:39 -0000

I do have a collection of additional RFC 3315 issues (including a list
of 28 issues reported by Fred Templin back in 2006 - though not all may
be things to correct).=20

I've tried to save these issues in a separate email folder as they were
reported, but I'm sure I missed a few too. And perhaps not all have been
reported via email - such as some of the issues we discussed at the
Comcast sponsored DHCPv6 bake-offs.

Most of the collected issues are 'minor' (inconsistencies and wording
improvements). Some may require a bit of debate.

I guess one strategy would be to start an I-D of RFC 3315
corrections/clarifications which could then be used to construct the
3315bis or if no one has the stomach for that effort, just published on
its own. While for the editor this seems a bit more work than just
working on the 3315bis, it is likely more useful for reviewers as they
can clearly see the changes (rather than having to find the few changes
in a 100 page document).

So, if I have some time I'll start that I-D ... we can then role
draft-hunt-dhcpv6-clarify-mrc-00 into it or continue it as a separate
document -- and just reference it in the new I-D.=20

- Bernie

-----Original Message-----
From: Evan Hunt [mailto:each@isc.org]=20
Sent: Friday, June 26, 2009 12:27 AM
To: Bernie Volz (volz)
Cc: Ted Lemon; dhc WG
Subject: Re: [dhcwg] Add WG item: draft-hunt-dhcpv6-clarify-mrc-00

> So, for the MRC issue, I'd prefer to see this rolled into a 3315bis
> rather than having it end up as its own RFC.

For the record, as the author of the clarify-MRC draft, I would be okay
with this, and in fact I suggested it in San Francisco.  The draft
resolves
a simple ambiguity in 3315--prescribing a single interpretation for text
that formerly could have been read in two ways--and thus, from an
information theory standpoint, it contains exactly one bit of
information.

Call me old-fashioned, but I like an RFC to have more bits in it than
its
RFC number does.

However, when I proposed a -bis document at the working group meeting,
it seemed to be the consensus of the room that there weren't enough
known
errata in 3315 which had had demonstrable effects on interoperability to
justify a -bis document in the near future, and so we should push ahead
with the draft in the meantime.

The MRC ambiguity is fairly minor, but I'd like to see it resolved
sooner
not later.  If there is in fact lots of material for a 3315-bis now,
then
I support the creation of such a document.  But if it's going to be a
slow
accretion over years, then I would prefer not to halt the progress of
clarify-MRC while we wait.

--
Evan Hunt -- each@isc.org
Internet Systems Consortium, Inc.

From rdroms@cisco.com  Fri Jun 26 06:59:16 2009
Return-Path: <rdroms@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D3AED3A6A8C for <dhcwg@core3.amsl.com>; Fri, 26 Jun 2009 06:59:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.262
X-Spam-Level: 
X-Spam-Status: No, score=-6.262 tagged_above=-999 required=5 tests=[AWL=0.337,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sB+fYodKJGcc for <dhcwg@core3.amsl.com>; Fri, 26 Jun 2009 06:59:15 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id A20D03A6B3A for <dhcwg@ietf.org>; Fri, 26 Jun 2009 06:58:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,297,1243814400"; d="scan'208";a="48650604"
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 26 Jun 2009 13:59:03 +0000
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n5QDx3ZU018941;  Fri, 26 Jun 2009 09:59:03 -0400
Received: from [161.44.65.104] ([161.44.65.104]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n5QDx22E025900; Fri, 26 Jun 2009 13:59:02 GMT
Message-Id: <6D8C73BB-6116-4093-BC96-581D0A2C3EB2@cisco.com>
From: Ralph Droms <rdroms@cisco.com>
To: Bernie Volz (volz) <volz@cisco.com>
In-Reply-To: <8E296595B6471A4689555D5D725EBB210D699039@xmb-rtp-20a.amer.cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 26 Jun 2009 09:59:02 -0400
References: <C32CD809-6BF9-4817-88ED-A734E6EF3FD6@nominum.com> <8E296595B6471A4689555D5D725EBB210D698F94@xmb-rtp-20a.amer.cisco.com> <20090626042727.GA46169@isc.org> <8E296595B6471A4689555D5D725EBB210D699039@xmb-rtp-20a.amer.cisco.com>
X-Mailer: Apple Mail (2.935.3)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3202; t=1246024743; x=1246888743; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rdroms@cisco.com; z=From:=20Ralph=20Droms=20<rdroms@cisco.com> |Subject:=20Re=3A=20[dhcwg]=20Add=20WG=20item=3A=20draft-hu nt-dhcpv6-clarify-mrc-00 |Sender:=20 |To:=20Bernie=20Volz=20(volz)=20<volz@cisco.com>; bh=q7dnH3mryjRSHf/tqC4hhpStGvYb94ig+NbYi6mB9F0=; b=Rp/scmQY/FHsOfY3zpwkO//eBqiTVvmqepgwcVmgjbhfmqVfm9Kgyjnhbq yb2g97DIz+EKVEyQLqhH9jEuk97FLNK7HBi/kZUOq6TvFOK3l4UenjZ5aRfu PVBk+q/vvb;
Authentication-Results: rtp-dkim-2; header.From=rdroms@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); 
Cc: dhc WG <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Add WG item: draft-hunt-dhcpv6-clarify-mrc-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 26 Jun 2009 13:59:16 -0000

Depending on the nature of the issues, the RFC errata mechanism might  
be appropriate.

- Ralph

On Jun 26, 2009, at 9:05 AM 6/26/09, Bernie Volz (volz) wrote:

> I do have a collection of additional RFC 3315 issues (including a list
> of 28 issues reported by Fred Templin back in 2006 - though not all  
> may
> be things to correct).
>
> I've tried to save these issues in a separate email folder as they  
> were
> reported, but I'm sure I missed a few too. And perhaps not all have  
> been
> reported via email - such as some of the issues we discussed at the
> Comcast sponsored DHCPv6 bake-offs.
>
> Most of the collected issues are 'minor' (inconsistencies and wording
> improvements). Some may require a bit of debate.
>
> I guess one strategy would be to start an I-D of RFC 3315
> corrections/clarifications which could then be used to construct the
> 3315bis or if no one has the stomach for that effort, just published  
> on
> its own. While for the editor this seems a bit more work than just
> working on the 3315bis, it is likely more useful for reviewers as they
> can clearly see the changes (rather than having to find the few  
> changes
> in a 100 page document).
>
> So, if I have some time I'll start that I-D ... we can then role
> draft-hunt-dhcpv6-clarify-mrc-00 into it or continue it as a separate
> document -- and just reference it in the new I-D.
>
> - Bernie
>
> -----Original Message-----
> From: Evan Hunt [mailto:each@isc.org]
> Sent: Friday, June 26, 2009 12:27 AM
> To: Bernie Volz (volz)
> Cc: Ted Lemon; dhc WG
> Subject: Re: [dhcwg] Add WG item: draft-hunt-dhcpv6-clarify-mrc-00
>
>> So, for the MRC issue, I'd prefer to see this rolled into a 3315bis
>> rather than having it end up as its own RFC.
>
> For the record, as the author of the clarify-MRC draft, I would be  
> okay
> with this, and in fact I suggested it in San Francisco.  The draft
> resolves
> a simple ambiguity in 3315--prescribing a single interpretation for  
> text
> that formerly could have been read in two ways--and thus, from an
> information theory standpoint, it contains exactly one bit of
> information.
>
> Call me old-fashioned, but I like an RFC to have more bits in it than
> its
> RFC number does.
>
> However, when I proposed a -bis document at the working group meeting,
> it seemed to be the consensus of the room that there weren't enough
> known
> errata in 3315 which had had demonstrable effects on  
> interoperability to
> justify a -bis document in the near future, and so we should push  
> ahead
> with the draft in the meantime.
>
> The MRC ambiguity is fairly minor, but I'd like to see it resolved
> sooner
> not later.  If there is in fact lots of material for a 3315-bis now,
> then
> I support the creation of such a document.  But if it's going to be a
> slow
> accretion over years, then I would prefer not to halt the progress of
> clarify-MRC while we wait.
>
> --
> Evan Hunt -- each@isc.org
> Internet Systems Consortium, Inc.
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg


From Ted.Lemon@nominum.com  Fri Jun 26 10:39:53 2009
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 123053A69A7 for <dhcwg@core3.amsl.com>; Fri, 26 Jun 2009 10:39:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.389
X-Spam-Level: 
X-Spam-Status: No, score=-6.389 tagged_above=-999 required=5 tests=[AWL=0.210,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iIbsJOIA7urK for <dhcwg@core3.amsl.com>; Fri, 26 Jun 2009 10:39:52 -0700 (PDT)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by core3.amsl.com (Postfix) with ESMTP id 8289C3A6861 for <dhcwg@ietf.org>; Fri, 26 Jun 2009 10:39:49 -0700 (PDT)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKSkUHzcbMl9+1FbhWY1CLBP165UDePiPB@postini.com; Fri, 26 Jun 2009 10:40:11 PDT
Received: from webmail.nominum.com (webmail.nominum.com [64.89.228.50]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "webmail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 3D09A1BD6F3; Fri, 26 Jun 2009 10:39:34 -0700 (PDT)
Received: from uma.here (71.32.40.139) by exchange-01.win.nominum.com (64.89.228.50) with Microsoft SMTP Server (TLS) id 8.1.336.0; Fri, 26 Jun 2009 10:39:21 -0700
Message-ID: <F2E7FCAE-3E96-400F-8096-3A03D16E29DC@nominum.com>
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Bud Millwood <budm@weird-solutions.com>
In-Reply-To: <200903171740.19574.budm@weird-solutions.com>
Content-Type: text/plain; charset="US-ASCII"; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 26 Jun 2009 10:39:19 -0700
References: <5033E739-18FA-4328-A276-E6D159052AAA@cisco.com> <200903171740.19574.budm@weird-solutions.com>
X-Mailer: Apple Mail (2.935.3)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] dhc WG last call on draft-ietf-dhc-dhcpv4-vendor-message-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 26 Jun 2009 17:39:53 -0000

Bud, when the wglc came out for the dhcpv4 and dhcpv6 versions of this  
draft, you responded positively to the dhcpv4 version, but not the  
dhcpv6 version.   Was that a deliberate or accidental omission?


From each@isc.org  Thu Jun 25 21:27:14 2009
Return-Path: <each@isc.org>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 52A7E3A68D6 for <dhcwg@core3.amsl.com>; Thu, 25 Jun 2009 21:27:14 -0700 (PDT)
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=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e0-iH-dBCCsT for <dhcwg@core3.amsl.com>; Thu, 25 Jun 2009 21:27:13 -0700 (PDT)
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) by core3.amsl.com (Postfix) with ESMTP id B970D3A693B for <dhcwg@ietf.org>; Thu, 25 Jun 2009 21:27:12 -0700 (PDT)
Received: by farside.isc.org (Postfix, from userid 10292) id 2B461E6071; Fri, 26 Jun 2009 04:27:28 +0000 (UTC)
Date: Fri, 26 Jun 2009 04:27:28 +0000
From: Evan Hunt <each@isc.org>
To: "Bernie Volz (volz)" <volz@cisco.com>
Message-ID: <20090626042727.GA46169@isc.org>
References: <C32CD809-6BF9-4817-88ED-A734E6EF3FD6@nominum.com> <8E296595B6471A4689555D5D725EBB210D698F94@xmb-rtp-20a.amer.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8E296595B6471A4689555D5D725EBB210D698F94@xmb-rtp-20a.amer.cisco.com>
User-Agent: Mutt/1.4.2.3i
X-Mailman-Approved-At: Sat, 27 Jun 2009 11:28:48 -0700
Cc: dhc WG <dhcwg@ietf.org>, Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Add WG item: draft-hunt-dhcpv6-clarify-mrc-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 26 Jun 2009 04:27:14 -0000

> So, for the MRC issue, I'd prefer to see this rolled into a 3315bis
> rather than having it end up as its own RFC.

For the record, as the author of the clarify-MRC draft, I would be okay
with this, and in fact I suggested it in San Francisco.  The draft resolves
a simple ambiguity in 3315--prescribing a single interpretation for text
that formerly could have been read in two ways--and thus, from an
information theory standpoint, it contains exactly one bit of information.

Call me old-fashioned, but I like an RFC to have more bits in it than its
RFC number does.

However, when I proposed a -bis document at the working group meeting,
it seemed to be the consensus of the room that there weren't enough known
errata in 3315 which had had demonstrable effects on interoperability to
justify a -bis document in the near future, and so we should push ahead
with the draft in the meantime.

The MRC ambiguity is fairly minor, but I'd like to see it resolved sooner
not later.  If there is in fact lots of material for a 3315-bis now, then
I support the creation of such a document.  But if it's going to be a slow
accretion over years, then I would prefer not to halt the progress of
clarify-MRC while we wait.

--
Evan Hunt -- each@isc.org
Internet Systems Consortium, Inc.

From rangaprasad.sampath@hp.com  Sun Jun 28 21:46:32 2009
Return-Path: <rangaprasad.sampath@hp.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 47CB128C0D6 for <dhcwg@core3.amsl.com>; Sun, 28 Jun 2009 21:46:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U91V01Bd+IL9 for <dhcwg@core3.amsl.com>; Sun, 28 Jun 2009 21:46:31 -0700 (PDT)
Received: from g5t0009.atlanta.hp.com (g5t0009.atlanta.hp.com [15.192.0.46]) by core3.amsl.com (Postfix) with ESMTP id 656C528C0CF for <dhcwg@ietf.org>; Sun, 28 Jun 2009 21:46:31 -0700 (PDT)
Received: from G5W0603.americas.hpqcorp.net (g5w0603.americas.hpqcorp.net [16.228.9.186]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by g5t0009.atlanta.hp.com (Postfix) with ESMTPS id 026A0304C3 for <dhcwg@ietf.org>; Mon, 29 Jun 2009 04:46:50 +0000 (UTC)
Received: from G4W1852.americas.hpqcorp.net (16.234.97.230) by G5W0603.americas.hpqcorp.net (16.228.9.186) with Microsoft SMTP Server (TLS) id 8.1.375.2; Mon, 29 Jun 2009 04:46:15 +0000
Received: from GVW1162EXB.americas.hpqcorp.net ([16.232.35.135]) by G4W1852.americas.hpqcorp.net ([16.234.97.230]) with mapi; Mon, 29 Jun 2009 04:46:06 +0000
From: "Sampath, Rangaprasad (ProCurve Networking)" <rangaprasad.sampath@hp.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Date: Mon, 29 Jun 2009 04:44:21 +0000
Thread-Topic: Query on RFC 3315 - Section 20
Thread-Index: Acn4dEVLSuK90YUGRP+ZzE3X66zpyw==
Message-ID: <B6A10B07C479604C922301A4A4CB349343681603C4@GVW1162EXB.americas.hpqcorp.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [dhcwg] Query on RFC 3315 - Section 20
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 29 Jun 2009 04:46:32 -0000

Hello Everyone..

Section 20 of RFC states the following:=20
 =20
"If the relay agent relays messages to the All_DHCP_Servers multicast
 address or other multicast addresses, it sets the Hop Limit field to
 32."

Is the RFC referring to the IPv6 header field "Hop Limit" or it is referrin=
g to the DHCPv6 header field "Hop Count" in the above statement? My impress=
ion is that the RFC is referring to the DHCPv6 header field "Hop Count" and=
 stating that this must be set to 32 if the relay agent relays messages to =
any multicast IPv6 address. If this is TRUE, then the RFC perhaps has a typ=
o. Could someone please comment on what is correct.

Thank you.

Regards,
Ranga..

From volz@cisco.com  Mon Jun 29 16:03:02 2009
Return-Path: <volz@cisco.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2DA4E3A6C6D for <dhcwg@core3.amsl.com>; Mon, 29 Jun 2009 16:03:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.449
X-Spam-Level: 
X-Spam-Status: No, score=-5.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_SHOP=2.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NEcg7Vm0mJw2 for <dhcwg@core3.amsl.com>; Mon, 29 Jun 2009 16:03:01 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 56E893A6B3E for <dhcwg@ietf.org>; Mon, 29 Jun 2009 16:03:01 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,312,1243814400"; d="scan'208";a="207302679"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-1.cisco.com with ESMTP; 29 Jun 2009 23:03:02 +0000
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n5TN32d0007641;  Mon, 29 Jun 2009 16:03:02 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id n5TN32s4010730; Mon, 29 Jun 2009 23:03:02 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 29 Jun 2009 19:03:02 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 29 Jun 2009 19:02:59 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB210D699863@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <B6A10B07C479604C922301A4A4CB349343681603C4@GVW1162EXB.americas.hpqcorp.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Query on RFC 3315 - Section 20
Thread-Index: Acn4dEVLSuK90YUGRP+ZzE3X66zpywAmNzNQ
References: <B6A10B07C479604C922301A4A4CB349343681603C4@GVW1162EXB.americas.hpqcorp.net>
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Sampath, Rangaprasad (ProCurve Networking)" <rangaprasad.sampath@hp.com>,  <dhcwg@ietf.org>
X-OriginalArrivalTime: 29 Jun 2009 23:03:02.0213 (UTC) FILETIME=[C0D95750:01C9F90D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1535; t=1246316582; x=1247180582; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=volz@cisco.com; z=From:=20=22Bernie=20Volz=20(volz)=22=20<volz@cisco.com> |Subject:=20RE=3A=20[dhcwg]=20Query=20on=20RFC=203315=20-=2 0Section=2020 |Sender:=20; bh=S3xdmv1y1n3vfHhBRvM2UrEUhuCQ4NFotkm9+qA1/zQ=; b=h2+5z/J48fQA1AfmvB7KMl8pFj53ZbxKQDph8A/yZHLwm8ll3Y+xiFqfGp nSBMEWXGg6bW4s3kBT4BSrYmNZLshLzaDsfUl/ADljkNoQrVt6538jnjQ40t 5WlKoRiape;
Authentication-Results: sj-dkim-4; header.From=volz@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Subject: Re: [dhcwg] Query on RFC 3315 - Section 20
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 29 Jun 2009 23:03:02 -0000

This is the IPv6 header that the text is referring to. When a multicast
packet is sent (over IPv6), it must have a hop limit. If 1 were used
(the default multicast hop limit), then what point would there have been
in making the All_DHCP_Servers (a site-scoped multicast address)
anything but a link-local scoped multicast address.

Perhaps a future version of the document could say "IPv6 header's hop
limit" instead of just "hop limit".

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Sampath, Rangaprasad (ProCurve Networking)
Sent: Monday, June 29, 2009 12:44 AM
To: dhcwg@ietf.org
Subject: [dhcwg] Query on RFC 3315 - Section 20

Hello Everyone..

Section 20 of RFC states the following:=20
 =20
"If the relay agent relays messages to the All_DHCP_Servers multicast
 address or other multicast addresses, it sets the Hop Limit field to
 32."

Is the RFC referring to the IPv6 header field "Hop Limit" or it is
referring to the DHCPv6 header field "Hop Count" in the above statement?
My impression is that the RFC is referring to the DHCPv6 header field
"Hop Count" and stating that this must be set to 32 if the relay agent
relays messages to any multicast IPv6 address. If this is TRUE, then the
RFC perhaps has a typo. Could someone please comment on what is correct.

Thank you.

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

From rangaprasad.sampath@hp.com  Mon Jun 29 20:45:51 2009
Return-Path: <rangaprasad.sampath@hp.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2DD8928C178 for <dhcwg@core3.amsl.com>; Mon, 29 Jun 2009 20:45:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.449
X-Spam-Level: 
X-Spam-Status: No, score=-105.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_SHOP=2.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iVRyJE8vxR9L for <dhcwg@core3.amsl.com>; Mon, 29 Jun 2009 20:45:50 -0700 (PDT)
Received: from g4t0016.houston.hp.com (g4t0016.houston.hp.com [15.201.24.19]) by core3.amsl.com (Postfix) with ESMTP id 5159E3A6956 for <dhcwg@ietf.org>; Mon, 29 Jun 2009 20:45:50 -0700 (PDT)
Received: from G3W0631.americas.hpqcorp.net (g3w0631.americas.hpqcorp.net [16.233.59.15]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by g4t0016.houston.hp.com (Postfix) with ESMTPS id BF5891474E for <dhcwg@ietf.org>; Tue, 30 Jun 2009 03:46:10 +0000 (UTC)
Received: from G3W0629.americas.hpqcorp.net (16.233.58.78) by G3W0631.americas.hpqcorp.net (16.233.59.15) with Microsoft SMTP Server (TLS) id 8.1.375.2; Tue, 30 Jun 2009 03:45:12 +0000
Received: from GVW1162EXB.americas.hpqcorp.net ([16.232.35.135]) by G3W0629.americas.hpqcorp.net ([16.233.58.78]) with mapi; Tue, 30 Jun 2009 03:45:12 +0000
From: "Sampath, Rangaprasad (ProCurve Networking)" <rangaprasad.sampath@hp.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Date: Tue, 30 Jun 2009 03:43:27 +0000
Thread-Topic: [dhcwg] Query on RFC 3315 - Section 20
Thread-Index: Acn4dEVLSuK90YUGRP+ZzE3X66zpywAmNzNQAAkxL2A=
Message-ID: <B6A10B07C479604C922301A4A4CB349343681F9793@GVW1162EXB.americas.hpqcorp.net>
References: <B6A10B07C479604C922301A4A4CB349343681603C4@GVW1162EXB.americas.hpqcorp.net> <8E296595B6471A4689555D5D725EBB210D699863@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <8E296595B6471A4689555D5D725EBB210D699863@xmb-rtp-20a.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dhcwg] Query on RFC 3315 - Section 20
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@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, 30 Jun 2009 03:45:51 -0000

Thank you Ted and Bernie for clarifying the RFC. As Bernie pointed out, it =
would be good to state "IPv6 header's Hop Limit" instead of just "Hop Limit=
" in a future revision of the document.

Regards,
Ranga..
=20

-----Original Message-----
From: Bernie Volz (volz) [mailto:volz@cisco.com]=20
Sent: Tuesday, June 30, 2009 4:33 AM
To: Sampath, Rangaprasad (ProCurve Networking); dhcwg@ietf.org
Subject: RE: [dhcwg] Query on RFC 3315 - Section 20

This is the IPv6 header that the text is referring to. When a multicast
packet is sent (over IPv6), it must have a hop limit. If 1 were used
(the default multicast hop limit), then what point would there have been
in making the All_DHCP_Servers (a site-scoped multicast address)
anything but a link-local scoped multicast address.

Perhaps a future version of the document could say "IPv6 header's hop
limit" instead of just "hop limit".

- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf
Of Sampath, Rangaprasad (ProCurve Networking)
Sent: Monday, June 29, 2009 12:44 AM
To: dhcwg@ietf.org
Subject: [dhcwg] Query on RFC 3315 - Section 20

Hello Everyone..

Section 20 of RFC states the following:=20
 =20
"If the relay agent relays messages to the All_DHCP_Servers multicast
 address or other multicast addresses, it sets the Hop Limit field to
 32."

Is the RFC referring to the IPv6 header field "Hop Limit" or it is
referring to the DHCPv6 header field "Hop Count" in the above statement?
My impression is that the RFC is referring to the DHCPv6 header field
"Hop Count" and stating that this must be set to 32 if the relay agent
relays messages to any multicast IPv6 address. If this is TRUE, then the
RFC perhaps has a typo. Could someone please comment on what is correct.

Thank you.

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