From dhcwg-bounces@ietf.org Sun Jun 03 18:42:57 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Huymi-0004PO-FR; Sun, 03 Jun 2007 18:42:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Huymh-0004PJ-2W
	for dhcwg@ietf.org; Sun, 03 Jun 2007 18:42:51 -0400
Received: from the.hankinsfamily.info ([204.152.186.148]
	helo=hankinsfamily.info) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Huymf-0003is-N7
	for dhcwg@ietf.org; Sun, 03 Jun 2007 18:42:51 -0400
Received: from navarre.mercenary.net (c-76-102-106-124.hsd1.ca.comcast.net
	[76.102.106.124]) (authenticated bits=0)
	by hankinsfamily.info (8.13.8/8.13.8) with ESMTP id l53Mgmne010710
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <dhcwg@ietf.org>; Sun, 3 Jun 2007 15:42:48 -0700
Received: by navarre.mercenary.net (Postfix, from userid 1000)
	id EEF733B89D; Sun,  3 Jun 2007 15:57:06 -0700 (PDT)
Date: Sun, 3 Jun 2007 15:57:06 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: Re: [dhcwg] A question on receipt of Reply Messages in a client.
Message-ID: <20070603225706.GA668@isc.org>
References: <8544922.24201179704245938.JavaMail.weblogic@ep_ml28>
	<8E296595B6471A4689555D5D725EBB210421BE23@xmb-rtp-20a.amer.cisco.com>
Mime-Version: 1.0
In-Reply-To: <8E296595B6471A4689555D5D725EBB210421BE23@xmb-rtp-20a.amer.cisco.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1319977505=="
Errors-To: dhcwg-bounces@ietf.org


--===============1319977505==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK"
Content-Disposition: inline


--CE+1k2dSO48ffgeK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, May 28, 2007 at 11:16:47PM -0400, Bernie Volz (volz) wrote:
> When the client does the Solicit/Advertise/Request/Reply, it may get new =
addresses but it can transition to them properly.

Actually, RFC3315 section 18.1.8 (Receipt of Reply Messages) specifies
that the client "sends a Request message if the IA contained a Status
Code option with the NoBinding status."

So, not Solicit, but yeah, same difference.

I think there's some potential for infinite loops here, because a client
is going to include all its configured addresses (not just the ones it
got from the server it's Renewing/Rebinding).

So the next time a client renews or rebinds, it'll get the NoBinding
status code again and back to Request again.  I think Request should
complete (but may not if the server is issuing NoBinding for
Requests...), so that mitigates how much extra traffic there is.

Also, it's probably unlikely that the old addresses won't exceed their
valid lifetime before the new t1 expires.

> Perhaps 3315 could have had some language that a client may wait a short =
period for responses and take the "best" Reply to a REBIND (ie, perhaps one=
 that does not have any status code options?). But, it seems that this woul=
d have little practical benefit for the added complexity.

I think for example that a client engaged in communication with an
authenticated server is not going to want to take the first reply it
receives, and may not even wish to accept replies in the absence of
an authenticated reply.

So I suspect that will wind up being true regardless.

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

--CE+1k2dSO48ffgeK
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFGY0dCcXeLeWu2vmoRAiPTAJ94w9Vmso+soSOkdn2eYxvNwLTctACgjtKd
3BmbMBk91kDYQxlfEgShfyE=
=ETLs
-----END PGP SIGNATURE-----

--CE+1k2dSO48ffgeK--


--===============1319977505==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1319977505==--




From dhcwg-bounces@ietf.org Wed Jun 06 19:21:52 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hw4p1-000258-1c; Wed, 06 Jun 2007 19:21:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hw4p0-00023L-IQ
	for dhcwg@ietf.org; Wed, 06 Jun 2007 19:21:46 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hw4oz-0005ZN-7k
	for dhcwg@ietf.org; Wed, 06 Jun 2007 19:21:46 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 4E15D5A6E5; Wed,  6 Jun 2007 16:21:44 -0700 (PDT)
Date: Wed, 6 Jun 2007 16:21:44 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Message-ID: <20070606232144.GI23844@isc.org>
Mime-Version: 1.0
User-Agent: Mutt/1.5.9i
X-Spam-Score: -2.3 (--)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Subject: [dhcwg] wyse 1000's
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2069619448=="
Errors-To: dhcwg-bounces@ietf.org


--===============2069619448==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="qOrJKOH36bD5yhNe"
Content-Disposition: inline


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

Two more vendor-used options in the site-local space came to my
attention today.  Options 161 and 162, by something that identifies
itself in a vendor-class-identifier as "wyse-1000".

    http://marc.info/?l=3Ddhcp-users&m=3D118117049321236&w=3D2

I'm not suggesting any action, I think this usage is extremely rare
judging by google, but wanted to mention it anyway.

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

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

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

iD8DBQFGZ0GIcXeLeWu2vmoRArUbAJ4hbvraQ7N9guoalAmB3xTrRQxMUQCgiaWK
Nvyl6F+A3aGw6Pw8xH4o0No=
=El65
-----END PGP SIGNATURE-----

--qOrJKOH36bD5yhNe--


--===============2069619448==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============2069619448==--




From dhcwg-bounces@ietf.org Fri Jun 08 14:36:58 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HwjKN-0006iS-3v; Fri, 08 Jun 2007 14:36:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HwjKM-0006iN-9B
	for dhcwg@ietf.org; Fri, 08 Jun 2007 14:36:50 -0400
Received: from terminus.zytor.com ([192.83.249.54])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwjKK-00036h-TT
	for dhcwg@ietf.org; Fri, 08 Jun 2007 14:36:50 -0400
Received: from mail.hos.anvin.org (c-67-169-144-158.hsd1.ca.comcast.net
	[67.169.144.158]) (authenticated bits=0)
	by terminus.zytor.com (8.13.8/8.13.8) with ESMTP id l58IXaj8024340
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 8 Jun 2007 11:33:38 -0700
Received: from tazenda.hos.anvin.org (tazenda.hos.anvin.org [172.27.0.16])
	by mail.hos.anvin.org (8.13.8/8.13.8) with ESMTP id l58IXax5007524;
	Fri, 8 Jun 2007 11:33:36 -0700
Received: from tazenda.hos.anvin.org (localhost.localdomain [127.0.0.1])
	by tazenda.hos.anvin.org (8.13.8/8.13.6) with ESMTP id l58IXZfA008115; 
	Fri, 8 Jun 2007 11:33:36 -0700
Message-ID: <4669A0FF.6080406@zytor.com>
Date: Fri, 08 Jun 2007 11:33:35 -0700
From: "H. Peter Anvin" <hpa@zytor.com>
User-Agent: Thunderbird 2.0.0.0 (X11/20070419)
MIME-Version: 1.0
To: dhcwg@ietf.org
References: <8E296595B6471A4689555D5D725EBB2103FE37E6@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <8E296595B6471A4689555D5D725EBB2103FE37E6@xmb-rtp-20a.amer.cisco.com>
X-Enigmail-Version: 0.95.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.88.7/3380/Fri Jun 8 05:34:26 2007 on
	terminus.zytor.com
X-Virus-Status: Clean
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Subject: [dhcwg] draft-raj-dhc-tftp-addr-option-02
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Hello,

I looked over the RFC 3942 status report and the above option.  I'm a
bit surprised by the following statement:

>    Small devices, such as IP phones, have a need for downloading their
>    configuration from a TFTP server on the network.  There are commonly
>    accepted methods to discover this server via DHCP; the "sname" field
>    in the DHCP header [2] , the "TFTP Server name" option (#66) [3] .
>    Both of these sources of information, however, contain the TFTP
>    server's hostname.  That hostname must then be translated to an IP
>    address.  The usual method to accomplish this would be DNS. [4] This
>    means the firmware in a small "network appliance" device would need
>    to implement the DNS protocol in order to perform this translation.
>    This unacceptably increases the firmware code size.

In my experience, this is most commonly discovered via the "siaddr"
field in the DHCP response.  I think it would be advisable if this
document described the intended semantic differences between this option
and the siaddr field, as I'm a bit concerned that different bootloaders
might have different expectations of what this file should contain.

If this is specifically intended for a configuration file, it probably
should be named "configuration file server".  In that sense, it would be
a companion option to option 209 specified in draft-ietf-dhc-pxelinux-01.

	-hpa

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



From dhcwg-bounces@ietf.org Mon Jun 11 07:19:40 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hxhvn-0007Ds-Ge; Mon, 11 Jun 2007 07:19:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hxhvl-00077n-R9; Mon, 11 Jun 2007 07:19:29 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hxhvk-0006Uo-QN; Mon, 11 Jun 2007 07:19:29 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 11 Jun 2007 07:19:28 -0400
X-IronPort-AV: i="4.16,407,1175486400"; 
	d="scan'208"; a="123267190:sNHT177538580"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5BBJSJ8005028; 
	Mon, 11 Jun 2007 07:19:28 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5BBJSBe021806; 
	Mon, 11 Jun 2007 11:19:28 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 11 Jun 2007 07:19:27 -0400
Received: from 10.86.243.70 ([10.86.243.70]) by xmb-rtp-211.amer.cisco.com
	([64.102.31.118]) via Exchange Front-End Server email.cisco.com
	([64.102.31.38]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon, 11 Jun 2007 11:19:27 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Mon, 11 Jun 2007 07:19:40 -0400
From: Ralph Droms <rdroms@cisco.com>
To: <mip4@ietf.org>, DHC WG <dhcwg@ietf.org>
Message-ID: <C292A80C.45C40%rdroms@cisco.com>
Thread-Topic: mip4 and dhc WG joint last call on draft-ietf-mip4-gen-ext-03.txt
Thread-Index: AcesGmb3pawnLhgNEdy3NQARJOT6eg==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 11 Jun 2007 11:19:27.0950 (UTC)
	FILETIME=[5FC93EE0:01C7AC1A]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1280; t=1181560768;
	x=1182424768; 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:=20mip4=20and=20dhc=20WG=20joint=20last=20call=20on=20draft-ietf
	-mip4-gen-ext-03.txt |Sender:=20
	|To:=20<mip4@ietf.org>,=20DHC=20WG=20<dhcwg@ietf.org>;
	bh=NwtBKtyd+PjmUfnuYpdWGS4iS0Nm2BRFbSQeRsL3mOc=;
	b=c7eUNNLj7YlMiWtVXn1/1muCPyTnZMyCeixtCR5k0WJ/1XSPEVZp/IiPOGy1QK1x8KutiAmV
	N9YU5IXzdS4EtzP72vMHyGLjODyYBoLrA/Wg6LZ2sZaA4jOnxLu0WdPl;
Authentication-Results: rtp-dkim-2; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: 
Subject: [dhcwg] mip4 and dhc WG joint last call on
	draft-ietf-mip4-gen-ext-03.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

This message announces a joint WG last call for the mip4 and dhc WGs
on "Mobile IPv4 Extension for Configuration Options Exchange"
<draft-ietf-mip4-gen-ext-03.txt>.  The last call will conclude at
1700EDT, Monday, 06/25/07.

The dhc WG is asked to review the use of DHCP options in this draft to
pass configuration information to a mobile node.

Please respond to this joint WG last call.  Responses may be sent to
either mip4@ietf.org or dhcwg@ietf.org.  If you support acceptance of
the document without change, respond with a simple acknowledgment, so
that support for the document can be assessed.  Lack of discussion
does not represent positive support.  If there is no expression of
support for acceptance during the WG last call, the document will not
be advanced to the IESG.

draft-ietf-mip4-gen-ext-03.txt describes the mechanism for providing
the host configuration information during Mobile IP registration.  One
or more Configuration Options Exchange Extensions may be included in
the registration message to provide the Mobile Node the configuration
parameters needed for network service (e.g.  DNS).  This draft is
available as
http://www.ietf.org/internet-drafts/draft-ietf-mip4-gen-ext-03.txt

- Stig Venaas, Ralph Droms
  dhc WG chairs


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



From dhcwg-bounces@ietf.org Mon Jun 11 17:36:03 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxrYM-0003UW-I3; Mon, 11 Jun 2007 17:35:58 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HxrYL-0003UE-0q; Mon, 11 Jun 2007 17:35:57 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1HxrYK-0008AP-9P; Mon, 11 Jun 2007 17:35:56 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 0BF862AC88;
	Mon, 11 Jun 2007 21:35:26 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HxrXp-0004d4-PW; Mon, 11 Jun 2007 17:35:25 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1HxrXp-0004d4-PW@stiedprstage1.ietf.org>
Date: Mon, 11 Jun 2007 17:35:25 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: dhc mailing list <dhcwg@ietf.org>, dhc chair <dhc-chairs@tools.ietf.org>,
	Internet Architecture Board <iab@iab.org>,
	RFC Editor <rfc-editor@rfc-editor.org>
Subject: [dhcwg] Protocol Action: 'DHCPv6 Relay Agent Echo Request 
 Option' to Proposed Standard 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

The IESG has approved the following document:

- 'DHCPv6 Relay Agent Echo Request Option '
   <draft-ietf-dhc-dhcpv6-ero-01.txt> as a Proposed Standard

This document is the product of the Dynamic Host Configuration Working 
Group. 

The IESG contact persons are Jari Arkko and Mark Townsley.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-ero-01.txt

Technical Summary
 
  This document specifies a Relay Agent Echo Request 
  option for the Dynamic Host Configuration Protocol for
  IPv6 (DHCPv6).  The option allows a DHCPv6 relay agent to 
  request a list of relay agent options that the server 
  echoes back to the relay agent.

Working Group Summary
 
  This document is a product of the Dynamic Host Configuration
  Working Group of the IETF.

Protocol Quality
 
  There are no known implementations of the protocol.
  However, the need for this option was identified by 
  Comcast and Cisco during planning for deployment of
  DHCPv6 as a part of the DOCSIS 3.0 specification. 
  Therefore, we expect Cisco and other vendors of equipment 
  compatible with DOCSIS 3.0 to implement the option, and
  we expect Comcast and other cable service providers to
  use the option in their DOCSIS 3.0 deployments.
  No special reviews were performed or required.

  Jari Arkko has reviewed this specification for the IESG.
  A review was requested from the IP Directorate, and
  Brian Haberman reviewed the specification.


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



From dhcwg-bounces@ietf.org Thu Jun 14 10:56:08 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hyqjx-0002Rb-R0; Thu, 14 Jun 2007 10:56:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hyqjv-0002RD-BU; Thu, 14 Jun 2007 10:55:59 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hyqjv-0004vT-1u; Thu, 14 Jun 2007 10:55:59 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 14 Jun 2007 10:55:57 -0400
X-IronPort-AV: i="4.16,421,1175486400"; 
	d="scan'208"; a="123622096:sNHT4097722776"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5EEtvCP023006; 
	Thu, 14 Jun 2007 10:55:57 -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.12.10/8.12.6) with ESMTP id l5EEtu5r013064; 
	Thu, 14 Jun 2007 14:55:57 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 14 Jun 2007 10:55:51 -0400
Received: from 161.44.65.201 ([161.44.65.201]) by xmb-rtp-211.amer.cisco.com
	([64.102.31.118]) via Exchange Front-End Server email.cisco.com
	([64.102.31.21]) with Microsoft Exchange Server HTTP-DAV ; 
	Thu, 14 Jun 2007 14:55:51 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Thu, 14 Jun 2007 10:56:13 -0400
From: Ralph Droms <rdroms@cisco.com>
To: <mip6@ietf.org>, DHC WG <dhcwg@ietf.org>
Message-ID: <C296CF4D.46306%rdroms@cisco.com>
Thread-Topic: Joint mip6 and dhc WG last call on
	draft-ietf-mip6-bootstrapping-integrated and draft-ietf-mip6-hiopt
Thread-Index: AceulCajZVDLdBqHEdy5ogARJOT6eg==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 14 Jun 2007 14:55:51.0945 (UTC)
	FILETIME=[1A16E790:01C7AE94]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1819; t=1181832957;
	x=1182696957; c=relaxed/simple; s=rtpdkim1001;
	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:=20Joint=20mip6=20and=20dhc=20WG=20last=20call=20on=0A=20draft-i
	etf-mip6-bootstrapping-integrated=20and=20draft-ietf-mip6-hiopt
	|Sender:=20
	|To:=20<mip6@ietf.org>,=20DHC=20WG=20<dhcwg@ietf.org>;
	bh=0l9pDSZb46w8CzpetVFAuhVCV0yS00Rb28fb/SPWgFk=;
	b=VxG8473dGVNZU44Bty6PaoKdkZg2+lAjDCpM1WrUQNFxxLLZXlQOJyJKO2e9XmwrtV66nJYv
	LZEapIaZc6bzri1vEWSYptOEGRfAU9k06k60ix0N5PuKdtzBPFNiZrhP;
Authentication-Results: rtp-dkim-1; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 1.5 (+)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: 
Subject: [dhcwg] Joint mip6 and dhc WG last call on
 draft-ietf-mip6-bootstrapping-integrated and draft-ietf-mip6-hiopt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org


This message announces a joint mip6 and dhc WG last call on
"MIP6-bootstrapping for the Integrated Scenario"
<draft-ietf-mip6-bootstrapping-integrated-04.txt> and "DHCP Option for
Home Information Discovery in MIPv6" <draft-ietf-mip6-hiopt-05.txt>.
The last call will conclude at 1700EDT on 06/28/07.

Note that draft-ietf-mip6-hiopt-05.txt was recently submitted for
publication and should appear on all the usual I-D repositories soon.

The dhc WG is asked to review the use and design of DHCP options in
these documents.

Please respond to this WG last call.  Responses may be sent to either
mip6@ietf.org or dhcwg@ietf.org.  If you support acceptance of the
documents without change, respond with a simple acknowledgment, so that
support for the document can be assessed.  Lack of discussion does not
represent positive support.  If there is no expression of support for
acceptance during the WG last call, the documents will not be advanced
to the IESG.

Summary of documents:

In an integrated mobility scenario, the mobile node's mobility service
is authorized by the same service authorizer as the network access
service authorizer.  draft-ietf-mip6-bootstrapping-integrated-04.txt
defines a method for home agent information discovery for the
integrated scenario.  draft-ietf-mip6-hiopt-05.txt defines a
DHCP-based scheme to enable dynamic discovery of Mobile IPv6 home
agent address, home agent FQDN and home subnet.  New DHCP options are
defined to carry the information from a DHCP server to the DHCP client
running on the mobile node.

These drafts are available as:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-bootstrapping-integrated
-04.txt
and http://www.ietf.org/internet-drafts/draft-ietf-mip6-hiopt-05.txt

- Stig Venaas, Ralph Droms
  dhc WG chairs


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



From dhcwg-bounces@ietf.org Thu Jun 14 16:33:45 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hyw0k-00038C-SH; Thu, 14 Jun 2007 16:33:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hyw0i-0002gH-NU
	for dhcwg@ietf.org; Thu, 14 Jun 2007 16:33:40 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Hyw0f-0002yQ-7X
	for dhcwg@ietf.org; Thu, 14 Jun 2007 16:33:40 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-1.cisco.com with ESMTP; 14 Jun 2007 13:33:36 -0700
X-IronPort-AV: i="4.16,422,1175497200"; d="scan'208"; a="3227196:sNHT23282244"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l5EKXacZ019282; 
	Thu, 14 Jun 2007 13:33:36 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5EKXWaI009241;
	Thu, 14 Jun 2007 20:33:36 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 14 Jun 2007 13:33:32 -0700
Received: from [10.32.254.179] ([10.32.254.179]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 14 Jun 2007 13:33:31 -0700
In-Reply-To: <4669A0FF.6080406@zytor.com>
References: <8E296595B6471A4689555D5D725EBB2103FE37E6@xmb-rtp-20a.amer.cisco.com>
	<4669A0FF.6080406@zytor.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <349E3A31-AEEB-433F-BE50-00559B0B0EBC@cisco.com>
Content-Transfer-Encoding: 7bit
From: Richard Johnson <raj@cisco.com>
Subject: Re: [dhcwg] draft-raj-dhc-tftp-addr-option-02
Date: Thu, 14 Jun 2007 13:33:02 -0700
To: "H. Peter Anvin" <hpa@zytor.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 14 Jun 2007 20:33:31.0921 (UTC)
	FILETIME=[45F9E810:01C7AEC3]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3602; t=1181853216;
	x=1182717216; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=raj@cisco.com;
	z=From:=20Richard=20Johnson=20<raj@cisco.com>
	|Subject:=20Re=3A=20[dhcwg]=20draft-raj-dhc-tftp-addr-option-02
	|Sender:=20; bh=W02KjN9lM7+Sw2gYKItIqfg0lk09Q9SQf/KcGKGVwHU=;
	b=t1DPP1NVL6BbZI9VAq31glnxEaVHRqmaTigMJigrCgBch0FwFe1tgxnT0+BymN1CsjOhNlrQ
	3iNpHWaYT9qoaKUfkSMHBDj6akcM59DPvyawHuSMuDpXlckb8dPmDTnH;
Authentication-Results: sj-dkim-4; header.From=raj@cisco.com; dkim=pass (sig
	from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Sorry it took me a while to get in touch with the people who actually  
make use of this option and let them address this.  Here are the  
reasons given for going with a new option for this:

1) siaddr field is/was not configurable on some DHCP servers.
	e.g  Microsoft's DHCP server
2) siaddr field only allows for one IP address.
3) some DHCP servers seem to fill in their own IP address as siaddr!
	e.g. Novell's DHCP server
4) some customers were already using siaddr for something else

We have further discussed this option, however, and it has become  
apparent that it really shouldn't be a general purpose "TFTP server  
address" option.  It's only used for VoIP devices to find their  
configuration server and this functionality can (and probably will)  
migrate away from using TFTP.

We're thinking the option should instead be titled, "VoIP Device  
Configuration Server address(es)".  In this respect it's sorta like  
other options which already exist such as:

    68      Home-Agent-Addrs         N    Home Agent  
Addresses                  [RFC2132]
    69      SMTP-Server              N    Simple Mail Server  
Addresses          [RFC2132]
    70      POP3-Server              N    Post Office Server  
Addresses          [RFC2132]
    71      NNTP-Server              N    Network News Server  
Addresses         [RFC2132]
    72      WWW-Server               N    WWW Server  
Addresses                  [RFC2132]
    73      Finger-Server            N    Finger Server  
Addresses               [RFC2132]
    74      IRC-Server               N    Chat Server  
Addresses                 [RFC2132]
    75      StreetTalk-Server        N    StreetTalk Server  
Addresses           [RFC2132]
    76      STDA-Server              N    ST Directory Assist.  
Addresses        [RFC2132]

and many others.

/raj


On Jun 8, 2007, at 11:33 AM, H. Peter Anvin wrote:

> Hello,
>
> I looked over the RFC 3942 status report and the above option.  I'm a
> bit surprised by the following statement:
>
>>    Small devices, such as IP phones, have a need for downloading  
>> their
>>    configuration from a TFTP server on the network.  There are  
>> commonly
>>    accepted methods to discover this server via DHCP; the "sname"  
>> field
>>    in the DHCP header [2] , the "TFTP Server name" option (#66) [3] .
>>    Both of these sources of information, however, contain the TFTP
>>    server's hostname.  That hostname must then be translated to an IP
>>    address.  The usual method to accomplish this would be DNS. [4]  
>> This
>>    means the firmware in a small "network appliance" device would  
>> need
>>    to implement the DNS protocol in order to perform this  
>> translation.
>>    This unacceptably increases the firmware code size.
>
> In my experience, this is most commonly discovered via the "siaddr"
> field in the DHCP response.  I think it would be advisable if this
> document described the intended semantic differences between this  
> option
> and the siaddr field, as I'm a bit concerned that different  
> bootloaders
> might have different expectations of what this file should contain.
>
> If this is specifically intended for a configuration file, it probably
> should be named "configuration file server".  In that sense, it  
> would be
> a companion option to option 209 specified in draft-ietf-dhc- 
> pxelinux-01.
>
> 	-hpa
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg

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



From dhcwg-bounces@ietf.org Thu Jun 14 16:46:59 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HywDa-0001rg-6V; Thu, 14 Jun 2007 16:46:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HywDY-0001ra-Gw
	for dhcwg@ietf.org; Thu, 14 Jun 2007 16:46:56 -0400
Received: from terminus.zytor.com ([192.83.249.54])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HywDW-0006ug-VY
	for dhcwg@ietf.org; Thu, 14 Jun 2007 16:46:56 -0400
Received: from mail.hos.anvin.org (c-67-169-144-158.hsd1.ca.comcast.net
	[67.169.144.158]) (authenticated bits=0)
	by terminus.zytor.com (8.13.8/8.13.8) with ESMTP id l5EKhiTI004734
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 14 Jun 2007 13:43:44 -0700
Received: from tazenda.hos.anvin.org (tazenda.hos.anvin.org [172.27.0.16])
	by mail.hos.anvin.org (8.13.8/8.13.8) with ESMTP id l5EKhiOp021899;
	Thu, 14 Jun 2007 13:43:44 -0700
Received: from tazenda.hos.anvin.org (localhost.localdomain [127.0.0.1])
	by tazenda.hos.anvin.org (8.13.8/8.13.6) with ESMTP id l5EKheqJ002553; 
	Thu, 14 Jun 2007 13:43:41 -0700
Message-ID: <4671A87C.1080408@zytor.com>
Date: Thu, 14 Jun 2007 13:43:40 -0700
From: "H. Peter Anvin" <hpa@zytor.com>
User-Agent: Thunderbird 2.0.0.0 (X11/20070419)
MIME-Version: 1.0
To: Richard Johnson <raj@cisco.com>
Subject: Re: [dhcwg] draft-raj-dhc-tftp-addr-option-02
References: <8E296595B6471A4689555D5D725EBB2103FE37E6@xmb-rtp-20a.amer.cisco.com>
	<4669A0FF.6080406@zytor.com>
	<349E3A31-AEEB-433F-BE50-00559B0B0EBC@cisco.com>
In-Reply-To: <349E3A31-AEEB-433F-BE50-00559B0B0EBC@cisco.com>
X-Enigmail-Version: 0.95.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.88.7/3419/Thu Jun 14 06:49:39 2007 on
	terminus.zytor.com
X-Virus-Status: Clean
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Richard Johnson wrote:
> Sorry it took me a while to get in touch with the people who actually
> 
> We're thinking the option should instead be titled, "VoIP Device
> Configuration Server address(es)".  In this respect it's sorta like
> other options which already exist such as:
> 

I would drop the "VoIP Device" prefix, unless you think there is a
strong reason to limit this to only VoIP devices.  I can definitely see
it as desirable to be able to request that a configuration file is
obtained from a different location than the boot file.

	-hpa

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



From dhcwg-bounces@ietf.org Thu Jun 14 17:54:17 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyxGb-0007g7-5o; Thu, 14 Jun 2007 17:54:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyxGa-0007fz-2y
	for dhcwg@ietf.org; Thu, 14 Jun 2007 17:54:08 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HyxGX-0005Rv-N1
	for dhcwg@ietf.org; Thu, 14 Jun 2007 17:54:08 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-3.cisco.com with ESMTP; 14 Jun 2007 14:54:05 -0700
X-IronPort-AV: i="4.16,422,1175497200"; 
	d="scan'208"; a="494305205:sNHT45399204"
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 l5ELs56n028955; 
	Thu, 14 Jun 2007 14:54:05 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5ELs420001163;
	Thu, 14 Jun 2007 21:54:04 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 14 Jun 2007 14:54:04 -0700
Received: from [10.32.254.179] ([10.32.254.179]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 14 Jun 2007 14:54:04 -0700
In-Reply-To: <4671A87C.1080408@zytor.com>
References: <8E296595B6471A4689555D5D725EBB2103FE37E6@xmb-rtp-20a.amer.cisco.com>
	<4669A0FF.6080406@zytor.com>
	<349E3A31-AEEB-433F-BE50-00559B0B0EBC@cisco.com>
	<4671A87C.1080408@zytor.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <1919DDA9-759A-4C05-A8C9-4B4B7B315B5F@cisco.com>
Content-Transfer-Encoding: 7bit
From: Richard Johnson <raj@cisco.com>
Subject: Re: [dhcwg] draft-raj-dhc-tftp-addr-option-02
Date: Thu, 14 Jun 2007 14:53:35 -0700
To: "H. Peter Anvin" <hpa@zytor.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 14 Jun 2007 21:54:04.0507 (UTC)
	FILETIME=[866C02B0:01C7AECE]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1527; t=1181858045;
	x=1182722045; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=raj@cisco.com;
	z=From:=20Richard=20Johnson=20<raj@cisco.com>
	|Subject:=20Re=3A=20[dhcwg]=20draft-raj-dhc-tftp-addr-option-02
	|Sender:=20; bh=KgS7l/R+KMaEuP2MXcQEH/T2boQ9JM6bZ9+hLUko2jY=;
	b=I0nhy+/AH4vp500ktPn9FSeat9F5vvCT0+gn1cYRFW+WIQkAAMj88ewRzLFvytj1Ayo288Vz
	LM2knLhhpRS6NWAmuEkHGPCj/ESHoxd1ZGGDyZEAAKWBEQDATFMszmyR;
Authentication-Results: sj-dkim-2; header.From=raj@cisco.com; dkim=pass (sig
	from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

If we have a more generalized "Configuration Server Address(es)",  
wouldn't that present potential problems in cases where some devices  
on a link are of one type and need one "configuration server", while  
other devices on the same link are of a different type and thus need  
a different "configuration server"?  Maybe distinction could be made  
using the Class-ID, but I'm not sure that helps all that much for  
most situations/customers.  I would think it would be better to have  
a more specific "VoIP configuration server" such that configuration  
on the DHCP server for that option would end up only applying to  
clients which ask for that particular option, while other devices  
could ask for other "configuration server" options.  Isn't this the  
primary reason for currently having so many different types of "XYZ  
server address" options?

/raj

On Jun 14, 2007, at 1:43 PM, H. Peter Anvin wrote:

> Richard Johnson wrote:
>> Sorry it took me a while to get in touch with the people who actually
>>
>> We're thinking the option should instead be titled, "VoIP Device
>> Configuration Server address(es)".  In this respect it's sorta like
>> other options which already exist such as:
>>
>
> I would drop the "VoIP Device" prefix, unless you think there is a
> strong reason to limit this to only VoIP devices.  I can definitely  
> see
> it as desirable to be able to request that a configuration file is
> obtained from a different location than the boot file.
>
> 	-hpa

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



From dhcwg-bounces@ietf.org Thu Jun 14 18:39:18 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyxyG-0000cI-Bz; Thu, 14 Jun 2007 18:39:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyxyF-0000cC-Ae
	for dhcwg@ietf.org; Thu, 14 Jun 2007 18:39:15 -0400
Received: from terminus.zytor.com ([192.83.249.54])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyxyE-0004Ho-WF
	for dhcwg@ietf.org; Thu, 14 Jun 2007 18:39:15 -0400
Received: from mail.hos.anvin.org (c-67-169-144-158.hsd1.ca.comcast.net
	[67.169.144.158]) (authenticated bits=0)
	by terminus.zytor.com (8.13.8/8.13.8) with ESMTP id l5EMa4C9023242
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 14 Jun 2007 15:36:05 -0700
Received: from tazenda.hos.anvin.org (tazenda.hos.anvin.org [172.27.0.16])
	by mail.hos.anvin.org (8.13.8/8.13.8) with ESMTP id l5EMa4Ac022706;
	Thu, 14 Jun 2007 15:36:04 -0700
Received: from tazenda.hos.anvin.org (localhost.localdomain [127.0.0.1])
	by tazenda.hos.anvin.org (8.13.8/8.13.6) with ESMTP id l5EMa4Qk004023; 
	Thu, 14 Jun 2007 15:36:04 -0700
Message-ID: <4671C2D4.3080506@zytor.com>
Date: Thu, 14 Jun 2007 15:36:04 -0700
From: "H. Peter Anvin" <hpa@zytor.com>
User-Agent: Thunderbird 2.0.0.0 (X11/20070419)
MIME-Version: 1.0
To: Richard Johnson <raj@cisco.com>
Subject: Re: [dhcwg] draft-raj-dhc-tftp-addr-option-02
References: <8E296595B6471A4689555D5D725EBB2103FE37E6@xmb-rtp-20a.amer.cisco.com>
	<4669A0FF.6080406@zytor.com>
	<349E3A31-AEEB-433F-BE50-00559B0B0EBC@cisco.com>
	<4671A87C.1080408@zytor.com>
	<1919DDA9-759A-4C05-A8C9-4B4B7B315B5F@cisco.com>
In-Reply-To: <1919DDA9-759A-4C05-A8C9-4B4B7B315B5F@cisco.com>
X-Enigmail-Version: 0.95.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.88.7/3419/Thu Jun 14 06:49:39 2007 on
	terminus.zytor.com
X-Virus-Status: Clean
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Richard Johnson wrote:
> If we have a more generalized "Configuration Server Address(es)",
> wouldn't that present potential problems in cases where some devices on
> a link are of one type and need one "configuration server", while other
> devices on the same link are of a different type and thus need a
> different "configuration server"?  Maybe distinction could be made using
> the Class-ID, but I'm not sure that helps all that much for most
> situations/customers.  I would think it would be better to have a more
> specific "VoIP configuration server" such that configuration on the DHCP
> server for that option would end up only applying to clients which ask
> for that particular option, while other devices could ask for other
> "configuration server" options.  Isn't this the primary reason for
> currently having so many different types of "XYZ server address" options?

Using that logic, we'd run out of option codes pretty darn quickly.

I think that's exactly why the Vendor Class Identifier exists.

In particular, consider your statement:

> I would think it would be better to have a more specific "VoIP configuration server" such that configuration on the DHCP server for that option would end up only applying to clients which ask for that particular option, while other devices could ask for other "configuration server" options.

Here you seem to imply that there is something magic about VoIP devices
that makes them distinct from "other" devices.  That *exactly* same
argument can be made for, quite literally, any number of other device
classes.  Furthermore, it's entirely likely that, say, Cisco VoIP phones
will need an entirely different configuration file than, say, Avaya or
Nortel, making this argument even more specious.

	-hpa

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



From dhcwg-bounces@ietf.org Thu Jun 14 18:44:08 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hyy2x-0000rP-1L; Thu, 14 Jun 2007 18:44:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hyy2v-0000gz-7R
	for dhcwg@ietf.org; Thu, 14 Jun 2007 18:44:05 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hyy2u-00058z-TU
	for dhcwg@ietf.org; Thu, 14 Jun 2007 18:44:05 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 14 Jun 2007 15:44:04 -0700
X-IronPort-AV: i="4.16,422,1175497200"; 
	d="scan'208"; a="165435214:sNHT45618372"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id l5EMi4ei028550; 
	Thu, 14 Jun 2007 15:44:04 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l5EMhptf008485;
	Thu, 14 Jun 2007 22:44:04 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 14 Jun 2007 15:43:55 -0700
Received: from [10.32.254.179] ([10.32.254.179]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 14 Jun 2007 15:43:55 -0700
In-Reply-To: <4671C2D4.3080506@zytor.com>
References: <8E296595B6471A4689555D5D725EBB2103FE37E6@xmb-rtp-20a.amer.cisco.com>
	<4669A0FF.6080406@zytor.com>
	<349E3A31-AEEB-433F-BE50-00559B0B0EBC@cisco.com>
	<4671A87C.1080408@zytor.com>
	<1919DDA9-759A-4C05-A8C9-4B4B7B315B5F@cisco.com>
	<4671C2D4.3080506@zytor.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <5814D8D7-CD5D-44BD-BDA9-D29431D74826@cisco.com>
Content-Transfer-Encoding: 7bit
From: Richard Johnson <raj@cisco.com>
Subject: Re: [dhcwg] draft-raj-dhc-tftp-addr-option-02
Date: Thu, 14 Jun 2007 15:43:26 -0700
To: "H. Peter Anvin" <hpa@zytor.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 14 Jun 2007 22:43:55.0677 (UTC)
	FILETIME=[7D4C54D0:01C7AED5]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2477; t=1181861044;
	x=1182725044; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=raj@cisco.com;
	z=From:=20Richard=20Johnson=20<raj@cisco.com>
	|Subject:=20Re=3A=20[dhcwg]=20draft-raj-dhc-tftp-addr-option-02
	|Sender:=20; bh=BnnPVSKzwkREApIafL+SzFiVJtv9U4AqoX6Xqvsx5t0=;
	b=dQZa7P1DDYMHdqqkM5+DBwys85fYlblvYHGMw3JQ5rXamcXB/qZ4pqZ5CDVtQbYdWkft6ZMO
	nT+Fg/xMMPxgwmEL93Gk846XoYv40xIWAzdLGDByze0U1WLlsvlrmxt5;
Authentication-Results: sj-dkim-4; header.From=raj@cisco.com; dkim=pass (sig
	from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Yep, I realized all of that when I said it. :)

Of course, there already exist many different "configuration server"  
options, of which I only named a few in a previous message.  I guess  
they're all historical and the WG would currently be supporting the  
idea that no new "XZY server address" options would be allowed  
because all such new options should be Vendor Specific suboptions.

I would tend to agree with this, actually.  I wonder if this is the  
more general view of the WG?

/raj

On Jun 14, 2007, at 3:36 PM, H. Peter Anvin wrote:

> Richard Johnson wrote:
>> If we have a more generalized "Configuration Server Address(es)",
>> wouldn't that present potential problems in cases where some  
>> devices on
>> a link are of one type and need one "configuration server", while  
>> other
>> devices on the same link are of a different type and thus need a
>> different "configuration server"?  Maybe distinction could be made  
>> using
>> the Class-ID, but I'm not sure that helps all that much for most
>> situations/customers.  I would think it would be better to have a  
>> more
>> specific "VoIP configuration server" such that configuration on  
>> the DHCP
>> server for that option would end up only applying to clients which  
>> ask
>> for that particular option, while other devices could ask for other
>> "configuration server" options.  Isn't this the primary reason for
>> currently having so many different types of "XYZ server address"  
>> options?
>
> Using that logic, we'd run out of option codes pretty darn quickly.
>
> I think that's exactly why the Vendor Class Identifier exists.
>
> In particular, consider your statement:
>
>> I would think it would be better to have a more specific "VoIP  
>> configuration server" such that configuration on the DHCP server  
>> for that option would end up only applying to clients which ask  
>> for that particular option, while other devices could ask for  
>> other "configuration server" options.
>
> Here you seem to imply that there is something magic about VoIP  
> devices
> that makes them distinct from "other" devices.  That *exactly* same
> argument can be made for, quite literally, any number of other device
> classes.  Furthermore, it's entirely likely that, say, Cisco VoIP  
> phones
> will need an entirely different configuration file than, say, Avaya or
> Nortel, making this argument even more specious.
>
> 	-hpa

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



From dhcwg-bounces@ietf.org Thu Jun 14 19:16:45 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HyyYT-00018n-G5; Thu, 14 Jun 2007 19:16:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HyyE0-00058X-6a
	for dhcwg@ietf.org; Thu, 14 Jun 2007 18:55:32 -0400
Received: from exprod7og59.obsmtp.com ([64.18.2.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyyDw-0007op-0r
	for dhcwg@ietf.org; Thu, 14 Jun 2007 18:55:31 -0400
Received: from source ([81.200.64.181]) (using TLSv1) by
	exprod7ob59.obsmtp.com ([64.18.6.12]) with SMTP; 
	Thu, 14 Jun 2007 15:54:30 PDT
Received: from mail.nominum.com (mail.nominum.com [81.200.64.186])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by shell-ng.nominum.com (Postfix) with ESMTP id 5175256860;
	Thu, 14 Jun 2007 15:54:30 -0700 (PDT)
	(envelope-from Ted.Lemon@nominum.com)
X-Spam-Status: No, hits=0.0 required=8.4
	tests=CUSTOM_RULE_FROM: ALLOW,TOTAL_SCORE: 0.000
X-Spam-Level: 
Received: from [66.93.162.100] ([66.93.162.100])
	(authenticated user mellon@nominum.com) by mail.nominum.com
	(using TLSv1/SSLv3 with cipher AES128-SHA (128 bits));
	Thu, 14 Jun 2007 15:54:27 -0700
In-Reply-To: <5814D8D7-CD5D-44BD-BDA9-D29431D74826@cisco.com>
References: <8E296595B6471A4689555D5D725EBB2103FE37E6@xmb-rtp-20a.amer.cisco.com>
	<4669A0FF.6080406@zytor.com>
	<349E3A31-AEEB-433F-BE50-00559B0B0EBC@cisco.com>
	<4671A87C.1080408@zytor.com>
	<1919DDA9-759A-4C05-A8C9-4B4B7B315B5F@cisco.com>
	<4671C2D4.3080506@zytor.com>
	<5814D8D7-CD5D-44BD-BDA9-D29431D74826@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <87CD4CE6-74D1-4548-B5F3-F59CE3F5E8D1@nominum.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] draft-raj-dhc-tftp-addr-option-02
Date: Thu, 14 Jun 2007 15:54:18 -0700
To: Richard Johnson <raj@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Cc: dhcwg@ietf.org, "H. Peter Anvin" <hpa@zytor.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Jun 14, 2007, at 3:43 PM, Richard Johnson wrote:
> I would tend to agree with this, actually.  I wonder if this is the  
> more general view of the WG?

I'd rather stuff got documented, in general.   But if something  
really is vendor-specific, it ought to go into vendor-specific  
options; I think that an i-d describing it is still desirable, though.


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



From dhcwg-bounces@ietf.org Thu Jun 14 19:20:10 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hyybn-0002YV-C5; Thu, 14 Jun 2007 19:20:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hyybl-0002XH-SY
	for dhcwg@ietf.org; Thu, 14 Jun 2007 19:20:05 -0400
Received: from terminus.zytor.com ([192.83.249.54])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hyybk-0006CN-Gv
	for dhcwg@ietf.org; Thu, 14 Jun 2007 19:20:05 -0400
Received: from mail.hos.anvin.org (c-67-169-144-158.hsd1.ca.comcast.net
	[67.169.144.158]) (authenticated bits=0)
	by terminus.zytor.com (8.13.8/8.13.8) with ESMTP id l5ENGsOd029678
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 14 Jun 2007 16:16:54 -0700
Received: from tazenda.hos.anvin.org (tazenda.hos.anvin.org [172.27.0.16])
	by mail.hos.anvin.org (8.13.8/8.13.8) with ESMTP id l5ENGsYX023004;
	Thu, 14 Jun 2007 16:16:54 -0700
Received: from tazenda.hos.anvin.org (localhost.localdomain [127.0.0.1])
	by tazenda.hos.anvin.org (8.13.8/8.13.6) with ESMTP id l5ENGrTQ004229; 
	Thu, 14 Jun 2007 16:16:54 -0700
Message-ID: <4671CC65.4060902@zytor.com>
Date: Thu, 14 Jun 2007 16:16:53 -0700
From: "H. Peter Anvin" <hpa@zytor.com>
User-Agent: Thunderbird 2.0.0.0 (X11/20070419)
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] draft-raj-dhc-tftp-addr-option-02
References: <8E296595B6471A4689555D5D725EBB2103FE37E6@xmb-rtp-20a.amer.cisco.com>
	<4669A0FF.6080406@zytor.com>
	<349E3A31-AEEB-433F-BE50-00559B0B0EBC@cisco.com>
	<4671A87C.1080408@zytor.com>
	<1919DDA9-759A-4C05-A8C9-4B4B7B315B5F@cisco.com>
	<4671C2D4.3080506@zytor.com>
	<5814D8D7-CD5D-44BD-BDA9-D29431D74826@cisco.com>
	<87CD4CE6-74D1-4548-B5F3-F59CE3F5E8D1@nominum.com>
In-Reply-To: <87CD4CE6-74D1-4548-B5F3-F59CE3F5E8D1@nominum.com>
X-Enigmail-Version: 0.95.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.88.7/3420/Thu Jun 14 15:16:42 2007 on
	terminus.zytor.com
X-Virus-Status: Clean
X-Spam-Score: 0.1 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: dhcwg@ietf.org, Richard Johnson <raj@cisco.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Ted Lemon wrote:
> On Jun 14, 2007, at 3:43 PM, Richard Johnson wrote:
>> I would tend to agree with this, actually.  I wonder if this is the
>> more general view of the WG?
> 
> I'd rather stuff got documented, in general.   But if something really
> is vendor-specific, it ought to go into vendor-specific options; I think
> that an i-d describing it is still desirable, though.
> 

I think that having "configuration file server" and "configuration file
path" options still make sense, though.  They're vendor-independent at
the syntactic level, meaning that you can at least provide places to put
them into the DHCP configuration file without having to write a
syntactical specification for the server to know what you're talking about.

	-hpa

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



From dhcwg-bounces@ietf.org Fri Jun 15 04:29:51 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hz7Bf-0000Yk-Fi; Fri, 15 Jun 2007 04:29:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hz7Bd-0000YX-TG
	for dhcwg@ietf.org; Fri, 15 Jun 2007 04:29:41 -0400
Received: from intermail.se.dataphone.net ([212.37.1.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hz7Bc-0002QK-GP
	for dhcwg@ietf.org; Fri, 15 Jun 2007 04:29:41 -0400
Received: from [213.115.152.226] (account budm@weird-solutions.com HELO
	offset.weird.se)
	by intermail.se.dataphone.net (CommuniGate Pro SMTP 4.2)
	with ESMTP id 43444574 for dhcwg@ietf.org;
	Fri, 15 Jun 2007 10:29:38 +0200
From: Bud Millwood <budm@weird-solutions.com>
Organization: Weird Solutions, Inc.
To: dhcwg@ietf.org
Subject: Re: [dhcwg] draft-raj-dhc-tftp-addr-option-02
Date: Fri, 15 Jun 2007 10:01:02 +0200
User-Agent: KMail/1.8
References: <8E296595B6471A4689555D5D725EBB2103FE37E6@xmb-rtp-20a.amer.cisco.com>
	<87CD4CE6-74D1-4548-B5F3-F59CE3F5E8D1@nominum.com>
	<4671CC65.4060902@zytor.com>
In-Reply-To: <4671CC65.4060902@zytor.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200706151001.02304.budm@weird-solutions.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bud Millwood <budm@weird-solutions.com>
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Friday 15 June 2007 01:16, H. Peter Anvin wrote:
> Ted Lemon wrote:
> > On Jun 14, 2007, at 3:43 PM, Richard Johnson wrote:
> >> I would tend to agree with this, actually.  I wonder if this is the
> >> more general view of the WG?
> >
> > I'd rather stuff got documented, in general.   But if something really
> > is vendor-specific, it ought to go into vendor-specific options; I think
> > that an i-d describing it is still desirable, though.
>
> I think that having "configuration file server" and "configuration file
> path" options still make sense, though.  They're vendor-independent at
> the syntactic level, meaning that you can at least provide places to put
> them into the DHCP configuration file without having to write a
> syntactical specification for the server to know what you're talking about.

I agree.

I had a short discussion with Bernie about this a few months ago (concerning 
DHCPv6). I was under the impression that general-purpose "config server/ 
config path" options would be a good idea for many types of devices. His 
input, at the time, was simply to explain why these options weren't needed 
for DOCSIS 3.0 (they're vendor-specific).

- Bud

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



From dhcwg-bounces@ietf.org Fri Jun 15 16:05:01 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HzI2R-00082n-06; Fri, 15 Jun 2007 16:04:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HzI2O-00082T-Sr
	for dhcwg@ietf.org; Fri, 15 Jun 2007 16:04:52 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzI2M-0007lx-T2
	for dhcwg@ietf.org; Fri, 15 Jun 2007 16:04:52 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 15 Jun 2007 16:04:50 -0400
X-IronPort-AV: i="4.16,426,1175486400"; 
	d="txt'?scan'208"; a="62883037:sNHT121003754"
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 l5FK4oNQ021287
	for <dhcwg@ietf.org>; Fri, 15 Jun 2007 16:04:50 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5FK4d61015149
	for <dhcwg@ietf.org>; Fri, 15 Jun 2007 20:04:50 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.1830); 
	Fri, 15 Jun 2007 16:04:50 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C7AF88.6DFA455C"
Date: Fri, 15 Jun 2007 16:04:48 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB21044BE0C0@xmb-rtp-20a.amer.cisco.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: Revised DHCPv6 Leasequery Draft
Thread-Index: AceviG1qwsUkAMfERtait+K9G/IF2w==
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: <dhcwg@ietf.org>
X-OriginalArrivalTime: 15 Jun 2007 20:04:50.0027 (UTC)
	FILETIME=[6E0F7BB0:01C7AF88]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=32356; t=1181937890;
	x=1182801890; 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:=20Revised=20DHCPv6=20Leasequery=20Draft |Sender:=20
	|To:=20<dhcwg@ietf.org>;
	bh=un1xSIDZuU5iGjGbO4D+BKTDaz5XJQV0YlQonhv8nKo=;
	b=fO/4xEeCl+YYVb4HmT5TDDuz5JGcvX+drRjMccHF7pM9tYvv9CcSc7qGC6+ahPX6buISoMvz
	qyD8faAgW3lOx2UhEdsp4kEXURu1knUyBrsU+tQpJSEz0knxSEyY753W;
Authentication-Results: rtp-dkim-2; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 054490fec19f6a94c68e63428d06db69
Subject: [dhcwg] Revised DHCPv6 Leasequery Draft
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7AF88.6DFA455C
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello:

The IESG review and IETF last-call process uncovered a bunch of issues
with regards to the draft-ietf-dhc-dhcpv6-leasequery-00 draft and I've
just submitted a revised version to address those nits and more
significant issues.

For those that want to review the revised draft now, you can do so at
ftp://ftpeng.cisco.com/volz/draft-ietf-dhc-dhcpv6-leasequery-01.txt.
Attached is also the differences between the two drafts.

The highlight of the changes (from the change log in the draft) are:

   The changes between draft-ietf-dhc-dhcpv6-leaesquery-00 and this
   version were as a result of the IETF last-call and IESG review:
   o  Several spelling, typographical, and grammatical corrections were
      made.
   o  The Terminology section was expanded to define more of the terms
      used, using the definitions from RFC 4388 [3].
   o  The Introduction and Protocol Overview sections were revised to
      explicitly reference material in RFC 4388 [3] and also indicate
      some of the key differences.
   o  The Security Considerations section was reworked.
   o  The IANA Considerations section now specifies how new query-type
      codes are assigned - through Standards Action.
   o  Additional references were added as a result of the above changes.

   Thanks to those that pointed out the above issues during the last-
   call process, including Jari Arkko, Lars Eggert, Sam Hartman, Alfred
   Hoenes, Tim Polk, and the folks at IANA.

The IESG status of this draft and issues can be viewed at
https://datatracker.ietf.org/public/pidtracker.cgi?command=3Dprint_ballot=
&
ballot_id=3D2449&filename=3Ddraft-ietf-dhc-dhcpv6-leasequery.

I did circulate a preliminary version to those that had pointed out
issues (minor or major) and have received comments back from most that
this version addresses their concerns, including Tim Polk.

- Bernie

------_=_NextPart_001_01C7AF88.6DFA455C
Content-Type: text/plain;
	name="lq-diffs.txt"
Content-Transfer-Encoding: base64
Content-Description: lq-diffs.txt
Content-Disposition: attachment;
	filename="lq-diffs.txt"

DQogQWJzdHJhY3QNCiANCi0gICBUaGlzIGRvY3VtZW50IHNwZWNpZmllcyBhIGxlYXNlcXVlcnkg
ZXhjaGFuZ2UgZm9yIHRoZSBEeW5hbWljIEhvc3QNCi0gICBDb25maWd1cmF0aW9uIFByb3RvY29s
IGZvciBJUHY2IChESENQdjYpIHdoaWNoIGNhbiBiZSB1c2VkIHRvIG9idGFpbg0KKyAgIFRoaXMg
ZG9jdW1lbnQgc3BlY2lmaWVzIGxlYXNlcXVlcnkgZm9yIHRoZSBEeW5hbWljIEhvc3QgQ29uZmln
dXJhdGlvbg0KKyAgIFByb3RvY29sIGZvciBJUHY2IChESENQdjYpIHdoaWNoIGNhbiBiZSB1c2Vk
IGFzIGEgbWVhbnMgdG8gb2J0YWluDQogICAgbGVhc2UgaW5mb3JtYXRpb24gYWJvdXQgREhDUHY2
IGNsaWVudHMgZnJvbSBhIERIQ1B2NiBzZXJ2ZXIuICBUaGlzDQogICAgZG9jdW1lbnQgc3BlY2lm
aWVzIHRoZSBzY29wZSBvZiBkYXRhIHRoYXQgY2FuIGJlIHJldHJpZXZlZCBhcyB3ZWxsIGFzDQog
ICAgYm90aCBESENQdjYgbGVhc2VxdWVyeSByZXF1ZXN0b3IgYW5kIHNlcnZlciBiZWhhdmlvci4g
IFRoaXMgZG9jdW1lbnQNCiAgICBleHRlbmRzIERIQ1B2Ni4NCiANCiAxLiAgSW50cm9kdWN0aW9u
DQogDQogICAgVGhlIERIQ1B2NiBbMl0gcHJvdG9jb2wgc3BlY2lmaWVzIGEgbWVjaGFuaXNtIGZv
ciB0aGUgYXNzaWdubWVudCBvZg0KDQotLS0NCg0KICAgIGFzc2lnbmVkIHVzaW5nIERIQ1B2NiBb
Ml0gWzRdLiAgU3BlY2lmaWMgZXhhbXBsZXMgd2hlcmUgdGhpcw0KICAgIGluZm9ybWF0aW9uIGhh
cyBpbGx1c3RyYXRlZCB2YWx1ZSBhcmUgaW4gYnJvYWRiYW5kIG5ldHdvcmtzIHRvDQogICAgZmFj
aWxpdGF0ZSBhY2Nlc3MgY29udHJvbCBieSBlZGdlIGRldmljZXMuICBUaGlzIGNhcGFiaWxpdHkg
dG8NCi0gICBwcm9ncmFtbWF0aWNhbGx5IGV4dHJhY3QgbGVhc2UgZGF0YSBmcm9tIHRoZSBESENQ
djYgc2VydmVyIGlzIGNhbGxlZA0KKyAgIHByb2dyYW1pdGNhbGx5IGV4dHJhY3QgbGVhc2UgZGF0
YSBmcm9tIHRoZSBESENQdjYgc2VydmVyIGlzIGNhbGxlZA0KICAgIGxlYXNlcXVlcnkuDQogDQot
ICAgVGhlIGxlYXNlcXVlcnkgY2FwYWJpbGl0eSBkZXNjcmliZWQgaW4gdGhpcyBkb2N1bWVudCBw
YXJhbGxlbHMgdGhlDQotICAgREhDUHY0IGxlYXNlcXVlcnkgY2FwYWJpbGl0eSBkb2N1bWVudGVk
IGluIFszXS4gIEFzIHN1Y2gsIGl0IHNoYXJlcw0KLSAgIHRoZSBiYXNpYyBtb3RpdmF0aW9ucywg
YmFja2dyb3VuZCwgZGVzaWduIGdvYWxzIGFuZCBjb25zdHJhaW50cyBhcw0KLSAgIGRlc2NyaWJl
ZCBpbiBbM10uICBEaWZmZXJlbmNlcyBhcmUgZHVlIHRvIHRoZSBkaWZmZXJlbmNlcyBiZXR3ZWVu
DQotICAgSVB2NCBhbmQgSVB2NiBhbmQgYnkgZXh0ZW5zaW9uLCBESENQdjQgYW5kIERIQ1B2Ni4g
IEZvciBleGFtcGxlLA0KLSAgIE5laWdoYm9yIERpc2NvdmVyeSBbN10gaXMgdXNlZCBpbiBJUHY2
IGluc3RlYWQgb2YgQVJQIFs4XSAoc2VjdGlvbg0KLSAgIDQuMSBvZiBbM10pIGFuZCBET0NTSVMg
My4wIFsxMV0gZGVmaW5lcyBJUHY2IHN1cHBvcnQgZm9yIGNhYmxlIG1vZGVtDQotICAgZW52aXJv
bm1lbnRzLg0KKyAgIEV4aXN0aW5nIHNwZWNpZmljYXRpb25zLCBzdWNoIGFzIFszXSBhcmUgbGV2
ZXJhZ2VkIGFzIGEgYmFzaXMgZm9yDQorICAgZXh0ZW5kaW5nIHRoZSBESENQdjYgcHJvdG9jb2wg
dG8gc3VwcG9ydCBsZWFzZXF1ZXJ5LiAgVGhlIG1vdGl2YXRpb25zDQorICAgYW5kIGp1c3RpZmlj
YXRpb25zIGlkZW50aWZpZWQgaW4gWzNdIGFsc28gZ2VuZXJhbGx5IGFwcGx5IHRvIHRoaXMNCisg
ICBzcGVjaWZpY2F0aW9uLiAgRnVydGhlcm1vcmUsIGFkdmFuY2VtZW50cyBpbiBESENQdjYgWzJd
IGFyZSBleHBhbmRlZA0KKyAgIHVwb24gdG8gc3BlY2lmeSBhZGRpdGlvbmFsIG1lYW5zIGJ5IHdo
aWNoIElQdjYgYWRkcmVzcyBhbmQgZGVsZWdhdGVkDQorICAgcHJlZml4IGxlYXNlIGRhdGEgY2Fu
IGJlIHJldHJpZXZlZCB0aHJvdWdoIERIQ1B2NiBsZWFzZXF1ZXJ5Lg0KIA0KIA0KIDIuICBUZXJt
aW5vbG9neQ0KDQotLS0NCg0KICAgIERIQ1B2NiB0ZXJtaW5vbG9neSBpcyBkZWZpbmVkIGluIFsy
XS4gIFRlcm1pbm9sb2d5IHNwZWNpZmljIHRvIERIQ1B2Ng0KICAgIGxlYXNlcXVlcnkgY2FuIGJl
IGZvdW5kIGJlbG93Og0KIA0KLSAgICAgICBhY2Nlc3MgY29uY2VudHJhdG9yDQotICAgICAgICAg
ICAgICAgICAgICAgICBBbiBhY2Nlc3MgY29uY2VudHJhdG9yIGlzIGEgcm91dGVyIG9yIHN3aXRj
aA0KLSAgICAgICAgICAgICAgICAgICAgICAgYXQgdGhlIGJyb2FkYmFuZCBhY2Nlc3MgcHJvdmlk
ZXIncyBlZGdlIG9mIGENCi0gICAgICAgICAgICAgICAgICAgICAgIHB1YmxpYyBicm9hZGJhbmQg
YWNjZXNzIG5ldHdvcmsuIFRoaXMgZG9jdW1lbnQNCi0gICAgICAgICAgICAgICAgICAgICAgIGFz
c3VtZXMgdGhhdCB0aGUgYWNjZXNzIGNvbmNlbnRyYXRvciBpbmNsdWRlcw0KLSAgICAgICAgICAg
ICAgICAgICAgICAgdGhlIERIQ1B2NiByZWxheSBhZ2VudCBmdW5jdGlvbmFsaXR5Lg0KLQ0KICAg
ICAgICBjbGllbnQocykgICAgICAgVGhlIG5vZGVzIHRoYXQgaGF2ZSBvbmUgb3IgbW9yZSBiaW5k
aW5ncw0KICAgICAgICAgICAgICAgICAgICAgICAgd2l0aCBhIERIQ1B2NiBzZXJ2ZXIuIFRoaXMg
ZG9lcyBub3QgcmVmZXIgdG8NCiAgICAgICAgICAgICAgICAgICAgICAgIHRoZSBub2RlIGlzc3Vp
bmcgdGhlIExFQVNFUVVFUlkgdW5sZXNzIGl0DQogICAgICAgICAgICAgICAgICAgICAgICBpdHNl
bGYgaGFzIG9uZSBvciBtb3JlIGJpbmRpbmdzIHdpdGggYSBESENQdjYNCiAgICAgICAgICAgICAg
ICAgICAgICAgIHNlcnZlci4NCiANCi0gICAgICAgZ2xlYW5pbmcgICAgICAgIEdsZWFuaW5nIGlz
IHRoZSBleHRyYWN0aW9uIG9mIGxvY2F0aW9uDQotICAgICAgICAgICAgICAgICAgICAgICBpbmZv
cm1hdGlvbiBmcm9tIERIQ1B2NiBtZXNzYWdlcywgYXMgdGhlDQotICAgICAgICAgICAgICAgICAg
ICAgICBtZXNzYWdlcyBhcmUgZm9yd2FyZGVkIGJ5IHRoZSBESENQIHJlbGF5IGFnZW50DQotICAg
ICAgICAgICAgICAgICAgICAgICBmdW5jdGlvbi4NCi0NCi0gICAgICAgbG9jYXRpb24gaW5mb3Jt
YXRpb24NCi0gICAgICAgICAgICAgICAgICAgICAgIExvY2F0aW9uIGluZm9ybWF0aW9uIGlzIGlu
Zm9ybWF0aW9uIG5lZWRlZCBieQ0KLSAgICAgICAgICAgICAgICAgICAgICAgdGhlIGFjY2VzcyBj
b25jZW50cmF0b3IgdG8gZm9yd2FyZCB0cmFmZmljIHRvDQotICAgICAgICAgICAgICAgICAgICAg
ICBhIGJyb2FkYmFuZC1hY2Nlc3NpYmxlIGhvc3QuIFRoaXMgaW5mb3JtYXRpb24NCi0gICAgICAg
ICAgICAgICAgICAgICAgIGluY2x1ZGVzIGtub3dsZWRnZSBvZiB0aGUgaG9zdCBoYXJkd2FyZQ0K
LSAgICAgICAgICAgICAgICAgICAgICAgYWRkcmVzcywgdGhlIHBvcnQgb3IgdmlydHVhbCBjaXJj
dWl0IHRoYXQNCi0gICAgICAgICAgICAgICAgICAgICAgIGxlYWRzIHRvIHRoZSBob3N0LCBhbmQv
b3IgdGhlIGhhcmR3YXJlIGFkZHJlc3MNCi0gICAgICAgICAgICAgICAgICAgICAgIG9mIHRoZSBp
bnRlcnZlbmluZyBzdWJzY3JpYmVyIG1vZGVtLg0KLQ0KICAgICAgICByZXF1ZXN0b3IgICAgICAg
VGhlIG5vZGUgdGhhdCBzZW5kcyBMRUFTRVFVRVJZIG1lc3NhZ2VzIHRvIG9uZQ0KICAgICAgICAg
ICAgICAgICAgICAgICAgb3IgbW9yZSBzZXJ2ZXJzIHRvIHJldHJpZXZlIGluZm9ybWF0aW9uIG9u
IHRoZQ0KICAgICAgICAgICAgICAgICAgICAgICAgYmluZGluZ3MgZm9yIGEgY2xpZW50Lg0KIA0K
IA0KLQ0KIDMuICBQcm90b2NvbCBPdmVydmlldw0KIA0KICAgIFRoZSBmb2N1cyBvZiB0aGlzIGRv
Y3VtZW50IGlzIHRvIGV4dGVuZCB0aGUgREhDUHY2IHByb3RvY29sIHRvIGFsbG93DQoNCi0tLQ0K
IA0KICAgIE9uZSBpbXBvcnRhbnQgbW90aXZhdGluZyBleGFtcGxlIGlzIHRoYXQgdGhlIExFQVNF
UVVFUlkgbWVzc2FnZQ0KICAgIGFsbG93cyBhY2Nlc3MgY29uY2VudHJhdG9ycyB0byBxdWVyeSBE
SENQIHNlcnZlcnMgdG8gb2J0YWluIGxvY2F0aW9uDQotICAgaW5mb3JtYXRpb24gb2YgYnJvYWRi
YW5kIGFjY2VzcyBuZXR3b3JrIGRldmljZXMuICBUaGlzIGlzIGRlc2NyaWJlZA0KLSAgIGluIHNl
Y3Rpb24gMSBvZiBbM10gZm9yIElQdjQuDQorICAgaW5mb3JtYXRpb24gb2YgYnJvYWRiYW5kIGFj
Y2VzcyBuZXR3b3JrIGRldmljZXMuDQorDQorICAgVGhlIGxlYXNlcXVlcnkgY2FwYWJpbGl0eSBk
ZXNjcmliZWQgaW4gdGhpcyBkb2N1bWVudCBwYXJhbGxlbHMgdGhlDQorICAgREhDUHY0IGxlYXNl
cXVlcnkgY2FwYWJpbGl0eSBkb2N1bWVudGVkIGluIFszXS4gIEFzIHN1Y2gsIGl0IHNoYXJlcw0K
KyAgIG1hbnkgb2YgdGhlIGJhc2ljIG1vdGl2YXRpb25zLCBkZXNpZ24gZ29hbHMgYW5kIGNvbnN0
cmFpbnRzIGFzIHRoZQ0KKyAgIGNhcGFiaWxpdHkgZGVzY3JpYmVkIGluIFNlY3Rpb24gNCBvZiBb
M10uDQogDQogMy4xLiAgT24tRGVtYW5kIFF1ZXJ5DQogDQotLS0NCiANCiAzLjMuICBRdWVyeSBU
eXBlcw0KIA0KLSAgIExlYXNlcXVlcnkgcHJvdmlkZXMgZm9yIHRoZSBmb2xsb3dpbmcgcXVlcmll
czoNCisgICBMZWFzcXVlcnkgcHJvdmlkZXMgZm9yIHRoZSBmb2xsb3dpbmcgcXVlcmllczoNCiAN
CiAgICBRdWVyeSBieSBJUHY2IGFkZHJlc3MgLSAgVGhpcyBxdWVyeSBhbGxvd3MgYSByZXF1ZXN0
b3IgdG8gcmVxdWVzdA0KICAgICAgIGZyb20gYSBzZXJ2ZXIgdGhlIGJpbmRpbmdzIGZvciBhIGNs
aWVudCB0aGF0IGVpdGhlciBpcyBib3VuZCB0bw0KDQotLS0NCiANCiA0LjEuMi4gIE9wdGlvbnMN
CiANCisNCiA0LjEuMi4xLiAgUXVlcnkgT3B0aW9uDQogDQotICAgVGhlIFF1ZXJ5IG9wdGlvbiBp
cyB1c2VkIG9ubHkgaW4gYSBMRUFTRVFVRVJZIG1lc3NhZ2UgYW5kIGlkZW50aWZpZXMNCi0gICB0
aGUgcXVlcnkgYmVpbmcgcGVyZm9ybWVkLiAgVGhlIG9wdGlvbiBpbmNsdWRlcyB0aGUgcXVlcnkg
dHlwZSwgbGluay0NCi0gICBhZGRyZXNzIChvciAwOjowKSwgYW5kIG9wdGlvbihzKSB0byBwcm92
aWRlIGRhdGEgbmVlZGVkIGZvciB0aGUNCi0gICBxdWVyeS4NCisgICBUaGUgTGVhc2VxdWVyeSBR
dWVyeSBvcHRpb24gaXMgdXNlZCBvbmx5IGluIGEgTEVBU0VRVUVSWSBtZXNzYWdlIGFuZA0KKyAg
IGlkZW50aWZpZXMgdGhlIHF1ZXJ5IGJlaW5nIHBlcmZvcm1lZC4gIFRoZSBvcHRpb24gaW5jbHVk
ZXMgdGhlIHF1ZXJ5DQorICAgdHlwZSwgbGluay1hZGRyZXNzIChvciAwOjowKSwgYW5kIG9wdGlv
bihzKSB0byBwcm92aWRlIGRhdGEgbmVlZGVkDQorICAgZm9yIHRoZSBxdWVyeS4NCiANCiAgICBU
aGUgZm9ybWF0IG9mIHRoZSBRdWVyeSBvcHRpb24gaXMgc2hvd24gYmVsb3c6DQogDQotLS0NCg0K
ICAgIHByb3ZpZGVzIHRoZSByZWxheSBhZ2VudCBpbmZvcm1hdGlvbiB1c2VkIHdoZW4gdGhlIGNs
aWVudCBsYXN0DQogICAgY29tbXVuaWNhdGVkIHdpdGggdGhlIHNlcnZlci4NCiANCi0gICBUaGUg
Zm9ybWF0IG9mIHRoZSBSZWxheSBEYXRhIG9wdGlvbiBpcyBzaG93biBiZWxvdzoNCisgICBUaGUg
Zm9ybWF0IG9mIHRoZSBDbGllbnQgTGlua3Mgb3B0aW9uIGlzIHNob3duIGJlbG93Og0KIA0KICAg
ICAgICAgMCAgICAgICAgICAgICAgICAgICAxICAgICAgICAgICAgICAgICAgIDIgICAgICAgICAg
ICAgICAgICAgMw0KICAgICAgICAgMCAxIDIgMyA0IDUgNiA3IDggOSAwIDEgMiAzIDQgNSA2IDcg
OCA5IDAgMSAyIDMgNCA1IDYgNyA4IDkgMCAxDQoNCg0KLS0tDQogDQogICAgVGhpcyBvcHRpb24g
aXMgdXNlZCBieSB0aGUgc2VydmVyIHRvIHJldHVybiBmdWxsIHJlbGF5IGFnZW50DQogICAgaW5m
b3JtYXRpb24gZm9yIGEgY2xpZW50LiAgSXQgTVVTVCBOT1QgYmUgcmV0dXJuZWQgaWYgdGhlIHNl
cnZlciBkb2VzDQotICAgbm90IGhhdmUgc3VjaCBpbmZvcm1hdGlvbiwgZWl0aGVyIGJlY2F1c2Ug
dGhlIGNsaWVudCBjb21tdW5pY2F0ZWQNCi0gICBkaXJlY3RseSAod2l0aG91dCByZWxheSBhZ2Vu
dCkgd2l0aCB0aGUgc2VydmVyIG9yIGlmIHRoZSBzZXJ2ZXIgZGlkDQotICAgbm90IHJldGFpbiBz
dWNoIGluZm9ybWF0aW9uLg0KKyAgIG5vdCBoYXZlIHN1Y2ggaW5mb3JtYXRpb24sIGVpdGhlciBi
ZWNhdXNlIHRoZSBjbGllbnQgbGFzdA0KKyAgIGNvbW11bmljYXRlZCBkaXJlY3RseSAod2l0aG91
dCByZWxheSBhZ2VudCkgd2l0aCB0aGUgc2VydmVyIG9yIGlmIHRoZQ0KKyAgIHNlcnZlciBkb2Vz
IG5vdCByZXRhaW5lZCBzdWNoIGluZm9ybWF0aW9uLg0KIA0KICAgIElmIHJldHVybmVkLCB0aGUg
REhDUC1yZWxheS1tZXNzYWdlIE1VU1QgY29udGFpbiBhIHZhbGlkIChwZXJoYXBzDQogICAgbXVs
dGktaG9wKSBSRUxBWS1GT1JXIG1lc3NhZ2UgYXMgbW9zdCByZWNlbnRseSByZWNlaXZlZCBieSB0
aGUgc2VydmVyDQoNCi0tLQ0KDQogICAgVGhpcyBvcHRpb24gU0hPVUxEIG9ubHkgYmUgcmV0dXJu
ZWQgaWYgcmVxdWVzdGVkIGJ5IHRoZSBPUFRJT05fT1JPIG9mDQogICAgdGhlIE9QVElPTl9MUV9R
VUVSWS4NCiANCisNCiA0LjEuMi41LiAgQ2xpZW50IExpbmsgT3B0aW9uDQogDQogICAgVGhlIENs
aWVudCBMaW5rIG9wdGlvbiBpcyB1c2VkIG9ubHkgaW4gYSBMRUFTRVFVRVJZLVJFUExZIG1lc3Nh
Z2UgYW5kDQoNCi0tLQ0KDQogICAgICAgcmVxdWVzdG9yLg0KICAgIG8gIFNlbmQgdG8gbXVsdGlw
bGUgc2VydmVycyBieSBtdWx0aWNhc3RpbmcgdG8gdGhlIEFsbF9ESENQX1NlcnZlcnMNCiAgICAg
ICBhZGRyZXNzLg0KLSAgIG8gIFRlcm1pbmF0ZSB0aGUgcmVxdWVzdC4NCisgICBvICBUZXJtaW5h
dGUgdGhlIGxlYXNlcXVlcnkuDQogDQogNC4zLjMuICBSZWNlaXB0IG9mIExFQVNFUVVFUlktUkVQ
TFkNCiANCiAgICBBIHN1Y2Nlc3NmdWwgTEVBU0VRVUVSWS1SRVBMWSBpcyBvbmUgd2l0aG91dCBh
biBPUFRJT05fU1RBVFVTX0NPREUNCiAgICBvcHRpb24gKG9yIGFuIE9QVElPTl9TVEFUVVNfQ09E
RSBvcHRpb24gd2l0aCBhIHN1Y2Nlc3MgY29kZSkuICBUaGVyZQ0KLSAgIGFyZSB0aHJlZSB2YXJp
YW50czoNCi0gICAxLiAgSWYgdGhlIHNlcnZlciBoYWQgYmluZGluZ3MgZm9yIHRoZSByZXF1ZXN0
ZWQgY2xpZW50LCB0aGUgbWVzc2FnZQ0KKyAgIGFyZSB0aHJlZSB2YXJpZW50czoNCisgICAxLiAg
SWYgdGhlIHNlcnZlciBoYXMgYmluZGluZ3MgZm9yIHRoZSByZXF1ZXN0ZWQgY2xpZW50LCB0aGUg
bWVzc2FnZQ0KICAgICAgICBpbmNsdWRlcyBhbiBPUFRJT05fQ0xJRU5UX0RBVEEgb3B0aW9uIGFu
ZCB0aGUgcmVxdWVzdG9yIGV4dHJhY3RzDQotICAgICAgIHRoZSBjbGllbnQgZGF0YSBmcm9tIHRo
ZSBMRUFTRVFVRVJZLVJFUExZIGFuZCB1cGRhdGVzIGl0cyBiaW5kaW5nDQorICAgICAgIHRoZSBj
bGllbnQgZGF0YSBmb3IgdGhlIExFQVNFUVVFUlktUkVQTFkgYW5kIHVwZGF0ZXMgaXRzIGJpbmRp
bmcNCiAgICAgICAgaW5mb3JtYXRpb24gZGF0YWJhc2UuICBJZiB0aGUgT1BUSU9OX0NMSUVOVF9E
QVRBIGNvbnRhaW5zIG5vDQogICAgICAgIE9QVElPTl9DTFRfVElNRSwgdGhlIHJlcXVlc3RvciBT
SE9VTEQgc2lsZW50bHkgZGlzY2FyZCB0aGUNCiAgICAgICAgT1BUSU9OX0NMSUVOVF9EQVRBIG9w
dGlvbi4NCg0KLS0tDQoNCiAgICAgICAgdGhlIG1lc3NhZ2UgaW5jbHVkZXMgYW4gT1BUSU9OX0NM
SUVOVF9MSU5LIG9wdGlvbi4gIFRoZSByZXF1ZXN0b3INCiAgICAgICAgd2lsbCBuZWVkIHRvIHJl
aXNzdWUgTEVBU0VRVUVSWSBtZXNzYWdlcyB1c2luZyBlYWNoIG9mIHRoZQ0KICAgICAgICByZXR1
cm5lZCBsaW5rLWFkZHJlc3NlcyB0byBvYnRhaW4gdGhlIGNsaWVudCdzIGJpbmRpbmdzLg0KLSAg
IDMuICBJZiB0aGUgc2VydmVyIGhhZCBubyBiaW5kaW5ncyBmb3IgdGhlIGNsaWVudCwgbmVpdGhl
ciB0aGUNCisgICAzLiAgSWYgdGhlIHNlcnZlciBoYXMgbm8gYmluZGluZ3MgZm9yIHRoZSBjbGll
bnQsIG5laXRoZXIgdGhlDQogICAgICAgIE9QVElPTl9DTElFTlRfREFUQSBub3IgT1BUSU9OX0NM
SUVOVF9MSU5LIG9wdGlvbiB3aWxsIGJlIHByZXNlbnQuDQogDQogICAgQW4gdW5zdWNjZXNzZnVs
IExFQVNFUVVFUlktUkVQTFkgaXMgb25lIHRoYXQgaGFzIGFuDQoNCi0tLQ0KDQogNC40LjIuICBD
b25zdHJ1Y3RpbmcgdGhlIENsaWVudCdzIE9QVElPTl9DTElFTlRfREFUQQ0KIA0KICAgIEFuIE9Q
VElPTl9DTElFTlRfREFUQSBvcHRpb24gaW4gYSBMRUFTRVFVRVJZLVJFUExZIG1lc3NhZ2UgTVVT
VA0KLSAgIG1pbmltYWxseSBjb250YWluIHRoZSBmb2xsb3dpbmcgb3B0aW9uczoNCisgICBtaW5p
bWFsbHkgY29udGFpbiB0aGUgZm9sbG93aW5nIGRhdGEuDQogICAgMS4gIE9QVElPTl9DTElFTlRJ
RA0KLSAgIDIuICBPUFRJT05fSUFBRERSIGFuZC9vciBPUFRJT05fSUFQUkVGSVgNCi0gICAzLiAg
T1BUSU9OX0NMVF9USU1FDQorICAgMi4gIE9QVElPTl9JQUFERFINCisgICAzLiAgT1BUSU9OX0lB
UFJFRklYDQorICAgNC4gIE9QVElPTl9DTFRfVElNRQ0KIA0KICAgIERlcGVuZGluZyBvbiB0aGUg
YmluZGluZ3MgdGhlIGNsaWVudCBoYXMgb24gYSBsaW5rLCBlaXRoZXINCiAgICBPUFRJT05fSUFB
RERSIG9wdGlvbnMsIE9QVElPTl9JQVBSRUZJWCBvcHRpb25zLCBvciBib3RoIG1heSBiZQ0KDQot
LS0NCiANCiA1LiAgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMNCiANCisgICBUaGUgc2VuZGVycyBv
ZiBMRUFTRVFVRVJZIG1lc3NhZ2VzIGFyZSBleHBlY3RlZCB0byBiZSB3aXRoaW4gdGhlIHNhbWUN
CisgICBzZWN1cml0eSBkb21haW4gYXMgdGhlIERIQ1B2NiBzZXJ2ZXIuICBBcyBzdWNoLCB0aGUg
c2VjdXJpdHkgdGhyZWF0DQorICAgdG8gREhDUHY2IGxlYXNlcXVlcnkgaXMgaW5oZXJlbnRseSBh
biBpbnNpZGVyIHRocmVhdC4gIEhvd2V2ZXIsIHRoaXMNCisgICBkb2N1bWVudCBkb2Vzbid0IHBy
b2hpYml0IGVudGl0aWVzIGluIGV4dGVybmFsIHNlY3VyaXR5IGRvbWFpbnMgZnJvbQ0KKyAgIHNl
bmRpbmcgTEVBU0VRVUVSWSBtZXNzYWdlcyB0byBESENQdjYgc2VydmVycy4gIFJlZ2FyZGxlc3Mg
b2YgdGhlDQorICAgbmV0d29yayBjb25maWd1cmF0aW9uLCBob3dldmVyLCB0aGUgcG90ZW50aWFs
IGF0dGFja3MgYnkgaW5zaWRlcnMgYW5kDQorICAgb3V0c2lkZXJzIGFyZSB0aGUgc2FtZS4NCisN
CisgICBJZiB0aGUgcmVxdWVzdG9yIGlzIGFuIGFjY2VzcyBjb25jZW50cmF0b3IsIERIQ1B2NiBs
ZWFzZXF1ZXJ5DQorICAgc2VjdXJpdHkgU0hPVUxEIGZvbGxvdyBzZWN1cml0eSBiZXR3ZWVuIHRo
ZSByZWxheSBhZ2VudCBhbmQgdGhlDQorICAgREhDUHY2IHNlcnZlciBhcyBkZXNjcmliZWQgaW4g
WzJdIFNlY3Rpb25zIDIxLjEgYW5kIDIyLjExLg0KKyAgIFJlcXVlc3RvcnMgYXJlIGVzc2VudGlh
bGx5IGEgREhDUHY2IGNsaWVudCBmb3IgdGhlIHB1cnBvc2VzIG9mIHRoZQ0KKyAgIExFQVNFUVVF
UlkgbWVzc2FnZS4gIFRodXMsIERIQ1B2NiBhdXRoZW50aWNhdGlvbiBbMl0gaXMgYWxzbyBhbg0K
KyAgIGFwcHJvcHJpYXRlIG1lY2hhbmlzbSBmb3Igc2VjdXJpbmcgTEVBU0VRVUVSWSBhbmQgTEVB
U0VRVUVSWS1SRVBMWQ0KKyAgIG1lc3NhZ2VzLg0KKw0KICAgIEFjY2VzcyBjb25jZW50cmF0b3Jz
IGFyZSBleHBlY3RlZCB0byBiZSBjb21tb24gbGVhc2VxdWVyeSByZXF1ZXN0b3JzLg0KLSAgIEFj
Y2VzcyBjb25jZW50cmF0b3JzIHRoYXQgdXNlIERIQ1B2NiBnbGVhbmluZyAoaS5lLiwgWzEwXSks
IHJlZnJlc2hlZA0KKyAgIEFjY2VzcyBjb25jZW50cmF0b3JzIHRoYXQgdXNlIERIQ1B2NiBnbGVh
bmluZyAoaS5lLiwgWzZdKSwgcmVmcmVzaGVkDQogICAgd2l0aCBMRUFTRVFVRVJZIG1lc3NhZ2Vz
LCB3aWxsIG1haW50YWluIGFjY3VyYXRlIGNsaWVudC9iaW5kaW5nDQogICAgaW5mb3JtYXRpb24u
ICBUaGlzIGVuc3VyZXMgdGhhdCB0aGUgYWNjZXNzIGNvbmNlbnRyYXRvciBjYW4gZm9yd2FyZA0K
ICAgIGRhdGEgdHJhZmZpYyB0byB0aGUgaW50ZW5kZWQgZGVzdGluYXRpb24gaW4gdGhlIGJyb2Fk
YmFuZCBhY2Nlc3MNCiAgICBuZXR3b3JrLCBjYW4gcGVyZm9ybSBJUHY2IHNvdXJjZSBhZGRyZXNz
IHZlcmlmaWNhdGlvbiBvZiBkYXRhZ3JhbXMNCiAgICBmcm9tIHRoZSBhY2Nlc3MgbmV0d29yaywg
YW5kIGNhbiBlbmNyeXB0IHRyYWZmaWMgdGhhdCBjYW4gb25seSBiZQ0KLSAgIGRlY3J5cHRlZCBi
eSB0aGUgaW50ZW5kZWQgYWNjZXNzIG1vZGVtIChlLmcuLCBbMTJdIGFuZCBbMTNdKS4gIFRodXMs
DQotICAgdGhlIGxlYXNlcXVlcnkgY2FwYWJpbGl0eSBhbGxvd3MgYW4gYWNjZXNzIGNvbmNlbnRy
YXRvciB0byBwcm92aWRlDQotICAgY29uc2lkZXJhYmx5IGVuaGFuY2VkIHNlY3VyaXR5Lg0KLQ0K
LSAgIFRoZSAiU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMiIHNlY3Rpb24gb2YgWzJdIGRldGFpbHMg
dGhlIGdlbmVyYWwNCi0gICB0aHJlYXRzIHRvIERIQ1B2NiwgYW5kIHRodXMgdG8gTEVBU0VRVUVS
WSBtZXNzYWdlcy4gIFRoZQ0KLSAgICJBdXRoZW50aWNhdGlvbiBvZiBESENQIE1lc3NhZ2VzIiBz
ZWN0aW9uIG9mIFsyXSBkZXNjcmliZXMgc2VjdXJpbmcNCi0gICBjb21tdW5pY2F0aW9uIGJldHdl
ZW4gcmVsYXkgYWdlbnRzIGFuZCBzZXJ2ZXJzLCBhcyB3ZWxsIGFzIGNsaWVudHMNCi0gICBhbmQg
c2VydmVycy4gIElmIHRoZSByZXF1ZXN0b3IgaXMgYW4gYWNjZXNzIGNvbmNlbnRyYXRvciwgdGhl
IElQc2VjDQotICAgWzldIGJhc2VkIHNlY3VyaXR5IGFzIGRlc2NyaWJlZCBpbiBbMl0gc2VjdGlv
biAyMS4xIFNIT1VMRCBiZSB1c2VkLg0KLSAgIE90aGVyIHR5cGVzIG9mIHJlcXVlc3RvcnMgYXJl
IGVzc2VudGlhbGx5IERIQ1B2NiBjbGllbnRzLiAgVGh1cywNCi0gICBESENQdjYgYXV0aGVudGlj
YXRpb24sIHNlY3Rpb24gMjEgb2YgWzJdLCBpcyBhbiBhcHByb3ByaWF0ZSBtZWNoYW5pc20NCi0g
ICBmb3Igc2VjdXJpbmcgTEVBU0VRVUVSWSBhbmQgTEVBU0VRVUVSWS1SRVBMWSBtZXNzYWdlcy4g
IEFzIHRoZSBudW1iZXINCi0gICBvZiBsZWFzZXF1ZXJ5IHJlcXVlc3RvcnMgYW5kIHNlcnZlcnMg
aW4gYW4gYWRtaW5pc3RyYXRpdmUgZG9tYWluIGlzDQotICAgcmVsYXRpdmVseSBzbWFsbCwgYW55
IHNoYXJlZCBrZXkgZGlzdHJpYnV0aW9uIGlzc3VlcyBhcmUgbWluaW1pemVkLg0KLQ0KLSAgIEFm
dGVyIGltcGxlbWVudGluZyB0aGUgYWJvdmUgYXBwcm9hY2hlcywgdGhlIERIQ1B2NiBzZXJ2ZXIg
c2hvdWxkDQotICAgb25seSBiZSBjb21tdW5pY2F0aW5nIHdpdGggdHJ1c3RlZCBMRUFTRVFVRVJZ
IHJlcXVlc3RvcnMsIGFuZCBzbw0KLSAgIHNlY3VyaXR5IG5lZWRzIHNob3VsZCBiZSBtZXQuDQot
DQotICAgSG93ZXZlciwgbm90IGFsbCB0cmFmZmljIG9yaWdpbmF0ZXMgZGlyZWN0bHkgZnJvbSB0
aGVzZSB0cnVzdGVkDQotICAgcmVxdWVzdG9ycy4gIEZvciBleGFtcGxlLCB0cnVzdGVkIHJlbGF5
IGFnZW50cyBjYW4gcmVsYXkgTEVBU0VRVUVSWQ0KLSAgIG1lc3NhZ2VzIGZyb20gdW50cnVzdGVk
IHJlcXVlc3RvcnMgb3IgZWxzZXdoZXJlIGluIHRoZSBuZXR3b3JrLiAgVGhpcw0KLSAgIFNIT1VM
RCBiZSBwcmV2ZW50ZWQgYXQgbGVhc3QgYXQgdGhlIHBlcmltZXRlciByZWxheSBhZ2VudHMgKG9y
IG9uIGFsbA0KLSAgIHJlbGF5IGFnZW50cyB1bmxlc3MgcmVsYXllZCBMRUFTRVFVRVJZIG1lc3Nh
Z2VzIGFyZSByZXF1aXJlZCBmb3Igc29tZQ0KLSAgIHJlcXVlc3RvcnMpLiAgREhDUHY2IHNlcnZl
cnMgTUFZIGJlIGNvbmZpZ3VyZWQgdG8gZGlzY2FyZCByZWxheWVkDQotICAgTEVBU0VRVUVSWSBt
ZXNzYWdlcyBvciByZXN0cmljdCByZWxheSBjaGFpbmluZy4NCisgICBkZWNyeXB0ZWQgYnkgdGhl
IGludGVuZGVkIGFjY2VzcyBtb2RlbSAoZS5nLiwgWzddIGFuZCBbOF0pLiAgVGh1cywNCisgICB0
aGUgTEVBU0VRVUVSWSBtZXNzYWdlIGFsbG93cyBhbiBhY2Nlc3MgY29uY2VudHJhdG9yIHRvIHBy
b3ZpZGUNCisgICBjb25zaWRlcmFibHkgZW5oYW5jZWQgc2VjdXJpdHkuICBESENQdjYgc2VydmVy
cyBTSE9VTEQgcHJldmVudA0KKyAgIGV4cG9zdXJlIG9mIHRoZWlyIGluZm9ybWF0aW9uIChwYXJ0
aWN1bGFybHkgdGhlIG1hcHBpbmcgb2YgaGFyZHdhcmUNCisgICBhZGRyZXNzIHRvIElQdjYgYWRk
cmVzcywgd2hpY2ggY2FuIGJlIGFuIGludmFzaW9uIG9mIGJyb2FkYmFuZA0KKyAgIHN1YnNjcmli
ZXIgcHJpdmFjeSkgYnkgZW1wbG95aW5nIHRoZSB0ZWNobmlxdWVzIGRldGFpbGVkIGluIFsyXSwN
CisgICBTZWN0aW9uIDIxLCAiQXV0aGVudGljYXRpb24gb2YgREhDUCBNZXNzYWdlcyIuDQogDQog
ICAgREhDUHY2IHNlcnZlcnMgU0hPVUxEIGFsc28gcHJvdmlkZSBmb3IgdGhlIGFiaWxpdHkgdG8g
cmVzdHJpY3QgdGhlDQotICAgaW5mb3JtYXRpb24gcmV0dXJuZWQgZm9yIGEgY2xpZW50IGluIGEg
TEVBU0VRVUVSWS1SRVBMWSBldmVuIHRvIGENCi0gICB0cnVzdGVkIExFQVNFUVVFUlkgcmVxdWVz
dG9yLCBhcyBkZXNjcmliZWQgaW4gU2VjdGlvbiA0LjQuMi4NCisgICBpbmZvcm1hdGlvbiB0aGF0
IHRoZXkgbWFrZSB2aWEgbGVhc2VxdWVyeSwgYXMgZGVzY3JpYmVkIGluDQorICAgU2VjdGlvbiA0
LjQuMi4NCiANCi0gICBTaW5jZSBldmVuIHRydXN0ZWQgYWNjZXNzIGNvbmNlbnRyYXRvcnMgbWF5
IGdlbmVyYXRlIExFQVNFUVVFUlkNCi0gICByZXF1ZXN0cyBhcyBhIHJlc3VsdCBvZiBhY3Rpdml0
eSBleHRlcm5hbCB0byB0aGUgYWNjZXNzIGNvbmNlbnRyYXRvciwNCi0gICBhY2Nlc3MgY29uY2Vu
dHJhdG9ycyBTSE9VTEQgbWluaW1pemUgcG90ZW50aWFsIGRlbmlhbCBvZiBzZXJ2aWNlDQotICAg
YXR0YWNrcyBvbiB0aGUgREhDUHY2IHNlcnZlcnMgYnkgbWluaW1pemluZyB0aGUgZ2VuZXJhdGlv
biBvZg0KLSAgIExFQVNFUVVFUlkgbWVzc2FnZXMuICBJbiBwYXJ0aWN1bGFyLCB0aGUgYWNjZXNz
IGNvbmNlbnRyYXRvciBTSE9VTEQNCi0gICBlbXBsb3kgbmVnYXRpdmUgY2FjaGluZyAoaS5lLiwg
Y2FjaGUgdGhlIGZhY3QgdGhhdCBhIHBhcnRpY3VsYXINCi0gICByZWNlbnQgcXVlcnkgZmFpbGVk
IHRvIHJldHVybiBjbGllbnQgZGF0YSkgYW5kIGFkZHJlc3MgcmVzdHJpY3Rpb25zDQotICAgd2hl
cmUgcG9zc2libGUgKGkuZS4sIGRvbid0IHNlbmQgYSBMRUFTRVFVRVJZIG1lc3NhZ2UgZm9yIGFk
ZHJlc3Nlcw0KLSAgIG91dHNpZGUgb2YgdGhlIHJhbmdlIG9mIHRoZSBhdHRhY2hlZCBicm9hZGJh
bmQgYWNjZXNzIG5ldHdvcmtzKS4NCi0gICBUb2dldGhlciwgdGhlc2UgbWVjaGFuaXNtcyBsaW1p
dCB0aGUgYWNjZXNzIGNvbmNlbnRyYXRvciB0bw0KLSAgIHRyYW5zbWl0dGluZyBvbmUgTEVBU0VR
VUVSWSBtZXNzYWdlIChleGNsdWRpbmcgbWVzc2FnZSByZXRyaWVzKSBwZXINCi0gICBsZWdpdGlt
YXRlIGJyb2FkYmFuZCBhY2Nlc3MgbmV0d29yayBhZGRyZXNzIGFmdGVyIGEgcmVib290IGV2ZW50
Lg0KLQ0KLSAgIFBhY2tldCBmbG9vZGluZyBkZW5pYWwgb2Ygc2VydmljZSBhdHRhY2tzIGNhbiBy
ZXN1bHQgaW4gdGhlDQotICAgZXhoYXVzdGlvbiBvZiBwcm9jZXNzaW5nIHJlc291cmNlcywgdGh1
cyBwcmV2ZW50aW5nIHRoZSBzZXJ2ZXIgZnJvbQ0KLSAgIHNlcnZpbmcgbGVnaXRpbWF0ZSBhbmQg
cmVndWxhciBESENQdjYgY2xpZW50cyBhcyB3ZWxsIGFzIGxlZ2l0aW1hdGUNCi0gICBESENQdjYg
TEVBU0VRVUVSWSByZXF1ZXN0b3JzLCBkZW55aW5nIGNvbmZpZ3VyYXRpb25zIHRvIGxlZ2l0aW1h
dGUNCi0gICBESENQdjYgY2xpZW50cyBhcyB3ZWxsIGxlYXNlIGluZm9ybWF0aW9uIHRvIGxlZ2l0
aW1hdGUgREhDUHY2DQotICAgTEVBU0VRVUVSWSByZXF1ZXN0b3JzLiAgV2hpbGUgdGhlc2UgYXR0
YWNrcyBhcmUgdW5saWtlbHkgd2hlbiBvbmx5DQotICAgY29tbXVuaWNhdGluZyB3aXRoIHRydXN0
ZWQgTEVBU0VRVUVSWSByZXF1ZXN0b3JzLCB0aGUgcG9zc2liaWxpdHkNCi0gICBhbHdheXMgZXhp
c3RzIHRoYXQgdGhlIHRydXN0IGlzIG1pc3BsYWNlZCwgc2VjdXJpdHkgdGVjaG5pcXVlcyBhcmUN
Ci0gICBjb21wcm9taXNlZCwgb3IgZXZlbiB0cnVzdGVkIHJlcXVlc3RvcnMgY2FuIGhhdmUgYnVn
cyBpbiB0aGVtLg0KLSAgIFRoZXJlZm9yZSB0ZWNobmlxdWVzIGZvciBkZWZlbmRpbmcgYWdhaW5z
dCBwYWNrZXQgZmxvb2RpbmcgZGVuaWFsIG9mDQotICAgc2VydmljZSBhcmUgYWx3YXlzIGEgZ29v
ZCBpZGVhLCBhbmQgdGhleSBpbmNsdWRlIGdvb2QgcGVyaW1ldGVyDQotICAgc2VjdXJpdHkgYXMg
bWVudGlvbmVkIGVhcmxpZXIgYW5kIHJhdGUgbGltaXRpbmcgREhDUHY2IHRyYWZmaWMgYnkNCi0g
ICByZWxheSBhZ2VudHMsIG90aGVyIG5ldHdvcmsgZWxlbWVudHMsIG9yIHRoZSBzZXJ2ZXIgaXRz
ZWxmLg0KLQ0KLSAgIE9uZSB3YXkgdG8gYXR0YWNrIGFuIGFjY2VzcyBjb25jZW50cmF0b3IgKGFz
IG9wcG9zZWQgdG8gYSBESENQdjYNCi0gICBzZXJ2ZXIpIGFzIGEgTEVBU0VRVUVSWSByZXF1ZXN0
b3IgaXMgdGhlIGVzdGFibGlzaG1lbnQgb2YgYSBtYWxpY2lvdXMNCi0gICBzZXJ2ZXIgd2l0aCB0
aGUgaW50ZW50IG9mIHByb3ZpZGluZyBpbmNvcnJlY3QgbGVhc2Ugb3Igcm91dGUNCi0gICBpbmZv
cm1hdGlvbiB0byB0aGUgYWNjZXNzIGNvbmNlbnRyYXRvciwgdGh3YXJ0aW5nIHNvdXJjZSBJUHY2
IGFkZHJlc3MNCi0gICB2ZXJpZmljYXRpb24gYW5kIHByZXZlbnRpbmcgY29ycmVjdCByb3V0aW5n
LiAgVGhpcyB0eXBlIG9mIGF0dGFjayBjYW4NCi0gICBiZSBtaW5pbWl6ZWQgYnkgdXNpbmcgSVBz
ZWMgYXMgZGVzY3JpYmVkIGluIHNlY3Rpb24gMjEuMSBvZiBbMl0uDQorICAgREhDUHY2IHNlcnZl
cnMgc3VwcG9ydGluZyBMRUFTRVFVRVJZIFNIT1VMRCBlbnN1cmUgdGhhdCB0aGV5IGNhbm5vdA0K
KyAgIGJlIHN1Y2Nlc3NmdWxseSBhdHRhY2tlZCBieSBiZWluZyBmbG9vZGVkIHdpdGggbGFyZ2Ug
cXVhbnRpdGllcyBvZg0KKyAgIExFQVNFUVVFUlkgbWVzc2FnZXMgaW4gYSBzaG9ydCB0aW1lLiAg
SW4gc29tZSBlbnZpcm9ubWVudHMsIGl0IG1heSBiZQ0KKyAgIGFwcHJvcHJpYXRlIHRvIGNvbmZp
Z3VyZSBhIERIQ1B2NiBzZXJ2ZXIgd2l0aCB0aGUgSVB2NiBzb3VyY2UNCisgICBhZGRyZXNzZXMg
b2YgdGhlIHJlbGF5IGFnZW50cyBmb3Igd2hpY2ggaXQgbWF5IHJlc3BvbmQgdG8gTEVBU0VRVUVS
WQ0KKyAgIG1lc3NhZ2VzLCB0aGVyZWJ5IGFsbG93aW5nIGl0IHRvIHJlc3BvbmQgb25seSB0byBy
ZXF1ZXN0cyBmcm9tIG9ubHkgYQ0KKyAgIGhhbmRmdWwgb2YgcmVsYXkgYWdlbnRzLiAgVGhpcyBk
b2VzIG5vdCBwcm92aWRlIGFueSB0cnVlIHNlY3VyaXR5LA0KKyAgIGJ1dCBtYXkgYmUgdXNlZnVs
IHRvIHRod2FydCB1bnNvcGhpc3RpY2F0ZWQgYXR0YWNrcyBvZiB2YXJpb3VzIHNvcnRzLg0KKw0K
KyAgIFJlcGxheWVkIG1lc3NhZ2VzIGNhbiByZXByZXNlbnQgYSBET1MgYXR0YWNrIHRocm91Z2gg
ZXhoYXVzdGlvbiBvZg0KKyAgIHByb2Nlc3NpbmcgcmVzb3VyY2VzLCBib2d1cyBsZWFzZXF1ZXJ5
IHJlcXVlc3RvcnMgY2FuIHNlbmQgYSBsb3Qgb2YNCisgICBMRUFTRVFVRVJZIG1lc3NhZ2VzIHRv
IG92ZXJ3aGVsbSBhIERIQ1B2NiBzZXJ2ZXIsIHRodXMgcHJldmVudGluZyB0aGUNCisgICBzZXJ2
ZXIgZnJvbSBzZXJ2aW5nIGxlZ2l0aW1hdGUgYW5kIHJlZ3VsYXIgREhDUHY2IGNsaWVudHMgYXMg
d2VsbCBhcw0KKyAgIGxlZ2l0aW1hdGUgREhDUHY2IGxlYXNlcXVlcnkgcmVxdWVzdG9ycywgZGVu
eWluZyBjb25maWd1cmF0aW9ucyB0bw0KKyAgIGxlZ2l0aW1hdGUgREhDUHY2IGNsaWVudHMgYXMg
d2VsbCBsZWFzZSBpbmZvcm1hdGlvbiB0byBsZWdpdGltYXRlDQorICAgREhDUHY2IGxlYXNlcXVl
cnkgcmVxdWVzdG9ycy4NCisNCisgICBPbmUgYXR0YWNrIHNwZWNpZmljIHRvIGFuIGFjY2VzcyBj
b25jZW50cmF0b3IgYXMgYSByZXF1ZXN0b3IgaXMgdGhlDQorICAgZXN0YWJsaXNobWVudCBvZiBh
IG1hbGljaW91cyBzZXJ2ZXIgd2l0aCB0aGUgaW50ZW50IG9mIHByb3ZpZGluZw0KKyAgIGluY29y
cmVjdCBsZWFzZSBvciByb3V0ZSBpbmZvcm1hdGlvbiB0byB0aGUgYWNjZXNzIGNvbmNlbnRyYXRv
ciwNCisgICB0aHdhcnRpbmcgc291cmNlIElQdjYgYWRkcmVzcyB2ZXJpZmljYXRpb24gYW5kIHBy
ZXZlbnRpbmcgY29ycmVjdA0KKyAgIHJvdXRpbmcuDQogDQogDQogNi4gIElBTkEgQ29uc2lkZXJh
dGlvbnMNCg0KLS0tDQoNCiAgICAgICBRVUVSWV9CWV9BRERSRVNTICAgICAgIDENCiAgICAgICBR
VUVSWV9CWV9DTElFTlRJRCAgICAgIDINCiANCi0gICBOZXcgT1BUSU9OX0xRX1FVRVJZIG9wdGlv
biBxdWVyeS10eXBlIGNvZGVzIGFyZSBhc3NpZ25lZCB0aHJvdWdoDQotICAgU3RhbmRhcmRzIEFj
dGlvbiwgYXMgZGVmaW5lZCBpbiBbNl0uDQotDQogDQogNy4gIEFja25vd2xlZGdlbWVudHMNCiAN
Ci0tLQ0KDQogICAgICAgT1BUSU9OX0xRX1JFTEFZX0RBVEEgb3B0aW9uLg0KICAgIG8gIEFuZCwg
b3RoZXIgbWlub3IgY2hhbmdlcyB0byBhY2NvbW1vZGF0ZSB0aGUgYWJvdmUuDQogDQotICAgVGhl
IGNoYW5nZXMgYmV0d2VlbiBkcmFmdC1pZXRmLWRoYy1kaGN2cDYtbGVhc2VxdWVyeS0wMSBhbmQN
Ci0gICBkcmFmdC1pZXRmLWRoY3B2Ni1sZWFzZXF1ZXJ5LTAwICh0aGUgY29ycmVjdGVkIGRvY3Vt
ZW50IG5hbWUpIHdlcmU6DQorICAgVGhlIGNoYW5nZXMgYmV0d2VlbiBkcmFmdC1pZXRmLWRoYy1k
aGN2cDYtbGVhc2VxdWVyeS0wMSBhbmQgdGhpcw0KKyAgIHZlcnNpb24gd2l0aCB0aGUgY29ycmVj
dGVkIGRvY3VtZW50IG5hbWUgd2VyZToNCiAgICBvICBGaXhlZCBkcmFmdCBuYW1lIChoYWQgZGhj
dnA2IGluc3RlYWQgb2YgZGhjcHY2KS4NCiAgICBvICBSZW1vdmVkIHJlZmVyZW5jZSB0byBTUlNO
IEktRCBhbmQgYXNzb2NpYXRlZCB0ZXh0LiAgU1JTTiBpcyBvbmx5DQogICAgICAgbmVlZGVkIGlm
IGFuZCB3aGVuIFJBQU4gbW92ZXMgZm9yd2FyZCAoaW4gb3IgY2xvc2UgdG8gaXRzIGN1cnJlbnQN
CiAgICAgICBmb3JtKS4NCi0gICBvICBBZGRlZCBbMTJdIGFuZCBbMTNdIHJlZmVyZW5jZXMgdGhh
dCB3ZXJlIG1pc3NpbmcgKHJlZmVyZW5jZWQgaW4NCisgICBvICBBZGRlZCBbN10gYW5kIFs4XSBy
ZWZlcmVuY2VzIHRoYXQgd2VyZSBtaXNzaW5nIChyZWZlcmVuY2VkIGluDQogICAgICAgU2VjdXJp
dHkgQ29uc2lkZXJhdGlvbnMgc2VjdGlvbikuDQogICAgbyAgVXBkYXRlZCBSQUFOIEktRCByZWZl
cmVuY2UgdG8gY3VycmVudCB2ZXJzaW9uLg0KICAgIG8gIFVwZGF0ZWQgYm9pbGVycGxhdGUgYW5k
IGNvcHlyaWdodCB5ZWFyLg0KIA0KLSAgIFRoZSBjaGFuZ2VzIGJldHdlZW4gZHJhZnQtaWV0Zi1k
aGMtZGhjcHY2LWxlYWVzcXVlcnktMDAgYW5kIHRoaXMNCi0gICB2ZXJzaW9uIHdlcmUgYXMgYSBy
ZXN1bHQgb2YgdGhlIElFVEYgbGFzdC1jYWxsIGFuZCBJRVNHIHJldmlldzoNCi0gICBvICBTZXZl
cmFsIHNwZWxsaW5nLCB0eXBvZ3JhcGhpY2FsLCBhbmQgZ3JhbW1hdGljYWwgY29ycmVjdGlvbnMg
d2VyZQ0KLSAgICAgIG1hZGUuDQotICAgbyAgVGhlIFRlcm1pbm9sb2d5IHNlY3Rpb24gd2FzIGV4
cGFuZGVkIHRvIGRlZmluZSBtb3JlIG9mIHRoZSB0ZXJtcw0KLSAgICAgIHVzZWQsIHVzaW5nIHRo
ZSBkZWZpbml0aW9ucyBmcm9tIFJGQyA0Mzg4IFszXS4NCi0gICBvICBUaGUgSW50cm9kdWN0aW9u
IGFuZCBQcm90b2NvbCBPdmVydmlldyBzZWN0aW9ucyB3ZXJlIHJldmlzZWQgdG8NCi0gICAgICBl
eHBsaWNpdGx5IHJlZmVyZW5jZSBtYXRlcmlhbCBpbiBSRkMgNDM4OCBbM10gYW5kIGFsc28gaW5k
aWNhdGUNCi0gICAgICBzb21lIG9mIHRoZSBrZXkgZGlmZmVyZW5jZXMuDQotICAgbyAgVGhlIFNl
Y3VyaXR5IENvbnNpZGVyYXRpb25zIHNlY3Rpb24gd2FzIHJld29ya2VkLg0KLSAgIG8gIFRoZSBJ
QU5BIENvbnNpZGVyYXRpb25zIHNlY3Rpb24gbm93IHNwZWNpZmllcyBob3cgbmV3IHF1ZXJ5LXR5
cGUNCi0gICAgICBjb2RlcyBhcmUgYXNzaWduZWQgLSB0aHJvdWdoIFN0YW5kYXJkcyBBY3Rpb24u
DQotICAgbyAgQWRkaXRpb25hbCByZWZlcmVuY2VzIHdlcmUgYWRkZWQgYXMgYSByZXN1bHQgb2Yg
dGhlIGFib3ZlIGNoYW5nZXMuDQotDQotICAgVGhhbmtzIHRvIHRob3NlIHRoYXQgcG9pbnRlZCBv
dXQgdGhlIGFib3ZlIGlzc3VlcyBkdXJpbmcgdGhlIGxhc3QtDQotICAgY2FsbCBwcm9jZXNzLCBp
bmNsdWRpbmcgSmFyaSBBcmtrbywgTGFycyBFZ2dlcnQsIFNhbSBIYXJ0bWFuLCBBbGZyZWQNCi0g
ICBIb2VuZXMsIFRpbSBQb2xrLCBhbmQgdGhlIGZvbGtzIGF0IElBTkEuDQotDQogDQogOS4gIFJl
ZmVyZW5jZXMNCiANCiA5LjEuICBOb3JtYXRpdmUgUmVmZXJlbmNlcw0KIA0KLSAgIFsxXSAgIEJy
YWRuZXIsIFMuLCAiS2V5IHdvcmRzIGZvciB1c2UgaW4gUkZDcyB0byBJbmRpY2F0ZSBSZXF1aXJl
bWVudA0KLSAgICAgICAgIExldmVscyIsIEJDUCAxNCwgUkZDIDIxMTksIE1hcmNoIDE5OTcuDQor
ICAgWzFdICBCcmFkbmVyLCBTLiwgIktleSB3b3JkcyBmb3IgdXNlIGluIFJGQ3MgdG8gSW5kaWNh
dGUgUmVxdWlyZW1lbnQNCisgICAgICAgIExldmVscyIsIEJDUCAxNCwgUkZDIDIxMTksIE1hcmNo
IDE5OTcuDQogDQotICAgWzJdICAgRHJvbXMsIFIuLCBCb3VuZCwgSi4sIFZvbHosIEIuLCBMZW1v
biwgVC4sIFBlcmtpbnMsIEMuLCBhbmQgTS4NCi0gICAgICAgICBDYXJuZXksICJEeW5hbWljIEhv
c3QgQ29uZmlndXJhdGlvbiBQcm90b2NvbCBmb3IgSVB2Ng0KLSAgICAgICAgIChESENQdjYpIiwg
UkZDIDMzMTUsIEp1bHkgMjAwMy4NCi0NCi0gICBbM10gICBXb3VuZHksIFIuIGFuZCBLLiBLaW5u
ZWFyLCAiRHluYW1pYyBIb3N0IENvbmZpZ3VyYXRpb24gUHJvdG9jb2wNCi0gICAgICAgICAoREhD
UCkgTGVhc2VxdWVyeSIsIFJGQyA0Mzg4LCBGZWJydWFyeSAyMDA2Lg0KLQ0KLSAgIFs0XSAgIFRy
b2FuLCBPLiBhbmQgUi4gRHJvbXMsICJJUHY2IFByZWZpeCBPcHRpb25zIGZvciBEeW5hbWljIEhv
c3QNCi0gICAgICAgICBDb25maWd1cmF0aW9uIFByb3RvY29sIChESENQKSB2ZXJzaW9uIDYiLCBS
RkMgMzYzMywNCi0gICAgICAgICBEZWNlbWJlciAyMDAzLg0KKyAgIFsyXSAgRHJvbXMsIFIuLCBC
b3VuZCwgSi4sIFZvbHosIEIuLCBMZW1vbiwgVC4sIFBlcmtpbnMsIEMuLCBhbmQgTS4NCisgICAg
ICAgIENhcm5leSwgIkR5bmFtaWMgSG9zdCBDb25maWd1cmF0aW9uIFByb3RvY29sIGZvciBJUHY2
IChESENQdjYpIiwNCisgICAgICAgIFJGQyAzMzE1LCBKdWx5IDIwMDMuDQorDQorICAgWzNdICBX
b3VuZHksIFIuIGFuZCBLLiBLaW5uZWFyLCAiRHluYW1pYyBIb3N0IENvbmZpZ3VyYXRpb24gUHJv
dG9jb2wNCisgICAgICAgIChESENQKSBMZWFzZXF1ZXJ5IiwgUkZDIDQzODgsIEZlYnJ1YXJ5IDIw
MDYuDQorDQorICAgWzRdICBUcm9hbiwgTy4gYW5kIFIuIERyb21zLCAiSVB2NiBQcmVmaXggT3B0
aW9ucyBmb3IgRHluYW1pYyBIb3N0DQorICAgICAgICBDb25maWd1cmF0aW9uIFByb3RvY29sIChE
SENQKSB2ZXJzaW9uIDYiLCBSRkMgMzYzMywNCisgICAgICAgIERlY2VtYmVyIDIwMDMuDQogDQog
OS4yLiAgSW5mb3JtYXRpdmUgUmVmZXJlbmNlcw0KIA0KLSAgIFs1XSAgIERyb21zLCBSLiwgIkR5
bmFtaWMgSG9zdCBDb25maWd1cmF0aW9uIFByb3RvY29sIiwgUkZDIDIxMzEsDQotICAgICAgICAg
TWFyY2ggMTk5Ny4NCi0NCi0gICBbNl0gICBOYXJ0ZW4sIFQuIGFuZCBILiBBbHZlc3RyYW5kLCAi
R3VpZGVsaW5lcyBmb3IgV3JpdGluZyBhbiBJQU5BDQotICAgICAgICAgQ29uc2lkZXJhdGlvbnMg
U2VjdGlvbiBpbiBSRkNzIiwgQkNQIDI2LCBSRkMgMjQzNCwNCi0gICAgICAgICBPY3RvYmVyIDE5
OTguDQotDQotICAgWzddICAgTmFydGVuLCBULiwgTm9yZG1hcmssIEUuLCBhbmQgVy4gU2ltcHNv
biwgIk5laWdoYm9yIERpc2NvdmVyeQ0KLSAgICAgICAgIGZvciBJUCBWZXJzaW9uIDYgKElQdjYp
IiwgUkZDIDI0NjEsIERlY2VtYmVyIDE5OTguDQotDQotICAgWzhdICAgUGx1bW1lciwgRC4sICJF
dGhlcm5ldCBBZGRyZXNzIFJlc29sdXRpb24gUHJvdG9jb2w6IE9yDQotICAgICAgICAgY29udmVy
dGluZyBuZXR3b3JrIHByb3RvY29sIGFkZHJlc3NlcyB0byA0OC5iaXQgRXRoZXJuZXQNCi0gICAg
ICAgICBhZGRyZXNzIGZvciB0cmFuc21pc3Npb24gb24gRXRoZXJuZXQgaGFyZHdhcmUiLCBTVEQg
MzcsDQotICAgICAgICAgUkZDIDgyNiwgTm92ZW1iZXIgMTk4Mi4NCi0NCi0gICBbOV0gICBLZW50
LCBTLiBhbmQgUi4gQXRraW5zb24sICJTZWN1cml0eSBBcmNoaXRlY3R1cmUgZm9yIHRoZQ0KLSAg
ICAgICAgIEludGVybmV0IFByb3RvY29sIiwgUkZDIDI0MDEsIE5vdmVtYmVyIDE5OTguDQotDQot
ICAgWzEwXSAgRHJvbXMsIFIuLCAiREhDUHY2IFJlbGF5IEFnZW50IEFzc2lnbm1lbnQgTm90aWZp
Y2F0aW9uIChSQUFOKQ0KLSAgICAgICAgIE9wdGlvbiIsIGRyYWZ0LWlldGYtZGhjLWRoY3B2Ni1h
Z2VudG9wdC1kZWxlZ2F0ZS0wMiAod29yayBpbg0KLSAgICAgICAgIHByb2dyZXNzKSwgTm92ZW1i
ZXIgMjAwNi4NCi0NCi0gICBbMTFdICBDYWJsZUxhYnMsICJEYXRhLU92ZXItQ2FibGUgU2Vydmlj
ZSBJbnRlcmZhY2UgU3BlY2lmaWNhdGlvbnM6DQotICAgICAgICAgRE9DU0lTIDMuMCwgTUFDIGFu
ZCBVcHBlciBMYXllciBQcm90b2NvbHMgSW50ZXJmYWNlDQotICAgICAgICAgU3BlY2lmaWNhdGlv
biwgQ00tU1AtTVVMUEl2My4wLUkwNC0wNzA1MTgiLCBNYXkgMjAwNywgYXZhaWxhYmxlDQotICAg
ICAgICAgYXQgaHR0cDovL3d3dy5jYWJsZW1vZGVtLmNvbS8uDQotDQotICAgWzEyXSAgU0NURSBE
YXRhIFN0YW5kYXJkcyBTdWJjb21taXR0ZWUsICJEYXRhLU92ZXItQ2FibGUgU2VydmljZQ0KLSAg
ICAgICAgIEludGVyZmFjZSBTcGVjaWZpY2F0aW9uczogRE9DU0lTIDEuMCBCYXNlbGluZSBQcml2
YWN5IEludGVyZmFjZQ0KLSAgICAgICAgIFNwZWNpZmljYXRpb24gU0NURSAyMi0yIDIwMDIiLCAy
MDAyLCBhdmFpbGFibGUgYXQNCi0gICAgICAgICBodHRwOi8vd3d3LnNjdGUub3JnL3N0YW5kYXJk
cy8uDQotDQotICAgWzEzXSAgQ2FibGVMYWJzLCAiRGF0YS1PdmVyLUNhYmxlIFNlcnZpY2UgSW50
ZXJmYWNlIFNwZWNpZmljYXRpb25zOg0KLSAgICAgICAgIEJhc2VsaW5lIFByaXZhY3kgUGx1cyBJ
bnRlcmZhY2UgU3BlY2lmaWNhdGlvbiBDTS1TUC1CUEkrX0kxMi0NCi0gICAgICAgICAwNTA4MTIi
LCBBdWd1c3QgMjAwNSwgYXZhaWxhYmxlIGF0IGh0dHA6Ly93d3cuY2FibGVtb2RlbS5jb20vLg0K
LQ0KLQ0KKyAgIFs1XSAgRHJvbXMsIFIuLCAiRHluYW1pYyBIb3N0IENvbmZpZ3VyYXRpb24gUHJv
dG9jb2wiLCBSRkMgMjEzMSwNCisgICAgICAgIE1hcmNoIDE5OTcuDQogDQorICAgWzZdICBEcm9t
cywgUi4sICJESENQdjYgUmVsYXkgQWdlbnQgQXNzaWdubWVudCBOb3RpZmljYXRpb24gKFJBQU4p
DQorICAgICAgICBPcHRpb24iLCBkcmFmdC1pZXRmLWRoYy1kaGNwdjYtYWdlbnRvcHQtZGVsZWdh
dGUtMDIgKHdvcmsgaW4NCisgICAgICAgIHByb2dyZXNzKSwgTm92ZW1iZXIgMjAwNi4NCisNCisg
ICBbN10gIFNDVEUgRGF0YSBTdGFuZGFyZHMgU3ViY29tbWl0dGVlLCAiRGF0YS1PdmVyLUNhYmxl
IFNlcnZpY2UNCisgICAgICAgIEludGVyZmFjZSBTcGVjaWZpY2F0aW9uczogRE9DU0lTIDEuMCBC
YXNlbGluZSBQcml2YWN5IEludGVyZmFjZQ0KKyAgICAgICAgU3BlY2lmaWNhdGlvbiBTQ1RFIDIy
LTIgMjAwMiIsIDIwMDIsIGF2YWlsYWJsZSBhdA0KKyAgICAgICAgaHR0cDovL3d3dy5zY3RlLm9y
Zy9zdGFuZGFyZHMvLg0KKw0KKyAgIFs4XSAgQ2FibGVMYWIsICJEYXRhLU92ZXItQ2FibGUgU2Vy
dmljZSBJbnRlcmZhY2UgU3BlY2lmaWNhdGlvbnM6DQorICAgICAgICBCYXNlbGluZSBQcml2YWN5
IFBsdXMgSW50ZXJmYWNlIFNwZWNpZmljYXRpb24gQ00tU1AtQlBJK19JMTItDQorICAgICAgICAw
NTA4MTIiLCBBdWd1c3QgMjAwNSwgYXZhaWxhYmxlIGF0IGh0dHA6Ly93d3cuY2FibGVtb2RlbS5j
b20vLg0K

------_=_NextPart_001_01C7AF88.6DFA455C
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

------_=_NextPart_001_01C7AF88.6DFA455C--




From dhcwg-bounces@ietf.org Sat Jun 16 14:35:00 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hzd6u-0002vr-2k; Sat, 16 Jun 2007 14:34:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hzd6t-0002vl-8f
	for dhcwg@ietf.org; Sat, 16 Jun 2007 14:34:55 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Hzd6m-0006xS-OI
	for dhcwg@ietf.org; Sat, 16 Jun 2007 14:34:55 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 16 Jun 2007 14:34:48 -0400
X-IronPort-AV: i="4.16,430,1175486400"; 
	d="scan'208"; a="123808340:sNHT43500316"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5GIYlJk003103
	for <dhcwg@ietf.org>; Sat, 16 Jun 2007 14:34:47 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5GIYcBi019833
	for <dhcwg@ietf.org>; Sat, 16 Jun 2007 18:34:47 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.1830); 
	Sat, 16 Jun 2007 14:34:40 -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
Subject: RE: [dhcwg] draft-raj-dhc-tftp-addr-option-02
Date: Sat, 16 Jun 2007 14:34:39 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB21044BE1CE@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <200706151001.02304.budm@weird-solutions.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] draft-raj-dhc-tftp-addr-option-02
Thread-Index: AcevJ2H7P91e55erR0mviymRoKm43ABHUNKQ
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: <dhcwg@ietf.org>
X-OriginalArrivalTime: 16 Jun 2007 18:34:40.0444 (UTC)
	FILETIME=[001C5FC0:01C7B045]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=491; t=1182018887;
	x=1182882887; 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]=20draft-raj-dhc-tftp-addr-option-02
	|Sender:=20 |To:=20<dhcwg@ietf.org>;
	bh=bmw8ty9sXnkKiKc5P/ft/kJ2oVaHCkYSlEQtqJqwHAI=;
	b=EOM3mrNs54lurpLoTOPbJ+60aMaP47EeS8uPqzyXLl+6uJDDNP/L4LjRLdDsdzUgMvVY5e/v
	OgqTt7Ms5/c46RwN1uayTLeVquBfU94xj2gbttNSs8U4T76NsSsAnHuY;
Authentication-Results: rtp-dkim-2; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

The fundamental question is whether this is documenting existing usage
so that this meets the requirements put forward in RFC 3942 to document
that usage in order to have the option assigned, or whether we are
trying to develop a new standard.

If we're documenting existing usage (which is I believe the point of the
draft), then calling it something specific to what it is used for is
appropriate.

If we're trying to develop a new standard, let the debate continue.

- Bernie

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



From dhcwg-bounces@ietf.org Sun Jun 17 07:54:47 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HztL8-0000Q8-Ma; Sun, 17 Jun 2007 07:54:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HztL6-0000Pr-9L
	for dhcwg@ietf.org; Sun, 17 Jun 2007 07:54:40 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HztL5-000163-JP
	for dhcwg@ietf.org; Sun, 17 Jun 2007 07:54:40 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 17 Jun 2007 04:54:39 -0700
X-IronPort-AV: i="4.16,431,1175497200"; 
	d="scan'208,217"; a="166743249:sNHT99118197"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5HBscoV017947
	for <dhcwg@ietf.org>; Sun, 17 Jun 2007 04:54:38 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l5HBscV1022293
	for <dhcwg@ietf.org>; Sun, 17 Jun 2007 11:54:38 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sun, 17 Jun 2007 07:54:38 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Sun, 17 Jun 2007 07:54:37 -0400
Message-ID: <6F66F4F04858B945B836804F0F2AE6BB01F57AB5@xmb-rtp-211.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: 2007-2008 NomCom
Thread-Index: Acew1keHN4STDklPSrGFl+NxSgCE/A==
From: "Ralph Droms \(rdroms\)" <rdroms@cisco.com>
To: <dhcwg@ietf.org>
X-OriginalArrivalTime: 17 Jun 2007 11:54:38.0051 (UTC)
	FILETIME=[47FB9B30:01C7B0D6]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=9671; t=1182081278;
	x=1182945278; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rdroms@cisco.com;
	z=From:=20=22Ralph=20Droms=20\(rdroms\)=22=20<rdroms@cisco.com>
	|Subject:=202007-2008=20NomCom |Sender:=20;
	bh=/WNUvKLgVJMO7CsbW4Hjl59BjySZjiUX9MKMY0upC9Y=;
	b=FHGhnV3dIwc6Yv8MO7s8s3khhK34+xO+ANAmdKz48TE+cMyk5oaO/qHezQdUoKz6eKXarC13
	qhgNCtb6rP2Km1AmhVE4EhZyOLZTfDHOXgNxsZhSe5jd5ZTq35TixpBC;
Authentication-Results: sj-dkim-2; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.5 (/)
X-Scan-Signature: f1405b5eaa25d745f8c52e3273d3af78
Subject: [dhcwg] 2007-2008 NomCom
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0857603554=="
Errors-To: dhcwg-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0857603554==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7B0D6.47BDE022"

This is a multi-part message in MIME format.

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

dhc WG members - please read the announcement below and consider =
volunteering for the NomCom.

I strongly recommend volunteering - I've participated as both a member =
and as chair - as a way of giving back to the IETF and as a way of =
helping to select the next leadership of the I* organizations.

- Ralph

From: Lakshminath Dondeti
To: IETF Announcement
Date: June 4, 2007
Subject: Nomcom 2007-8: First Call for Volunteers

Folks,

If you have attended 3 out of the past 5 IETF meetings, you are eligible =
to
serve on Nomcom 2007-2008.  Please volunteer and you may become one of =
the
voting members of the committee that selects about half of the members
to the
IESG and IAB and one IAOC member.  RFC 3777 describes the process and =
the
responsibilities in detail.  Below is the list of people from the IESG,
IAB and
IAOC whose terms end during the March 2008 IETF meeting.

IAOC:

Ed Juskevicius

IAB:

Leslie Daigle
Elwyn Davies
Kevin Fall
Olaf Kolkman
David Oran
Eric Rescorla

IESG:

Lisa Dusseault -- Applications Area Director Jari Arkko -- Internet Area
Director Dan Romascanu -- Operations and Management Area Director Cullen
Jennings -- Real-time Applications and Infrastructure Area Director Ross
Callon
--- Routing Area Director Sam Hartman -- Security Area Director Magnus
Westerlund -- Transport Area Director

Before volunteering, please think about whether you want to be
considered for
one of those positions instead.  If you are already convinced, please
send an
email before 12:00 noon ET (16:00 UTC/GMT) on July 5, 2007 (otherwise,
please
read on)

To: ldondeti@qualcomm.com
Subject: Nomcom 2007-8 Volunteer
Body:

<Your Full Name>   // As you enter in the IETF Registration Form,
                           // First/Given name followed by Last/Family =
Name
<Current Primary Affiliation> // typically what goes in the Company =
field
                                          //  in the IETF Registration =
Form
[<all email addresses used to Register for the past 5 IETF meetings>]
<Preferred
email address>  //
<Telephone number>         // For confirmation if selected

Please expect an email response from me within 1-2 days stating whether
you are
qualified or not.  If you don't receive anything, please re-send your
email with
the tag (duplicate) in the subject line.

Not convinced yet?  Please consider that nomcom members play an
important role
in shaping the leadership of the IETF.  If you are a people person, you =
will
enjoy meeting many of the active contributors to the IETF.  If you =
prefer
instead to read a lot of email, well, we have that too.  Being a nomcom
member
is also an important responsibility: it requires adherence to
confidentiality
rules and some time commitment from the members.  The term begins just
prior to
the Chicago meeting and we expect most of the work to be completed by
January
2008.  During this period, the nomcom members

-- collect requirements from the community and interviews candidates
     during the Chicago and Vancouver IETF meetings
-- review candidates' statements and weighs community feedback
-- participate in candidate selection deliberations (weekly conferences
calls)

Nomcom members are selected following a publicly verifiable random =
selection
method specified in RFC 3797.

For the nomcom to work as it should, the pool from which the volunteers =
are
chosen should be as large as possible. The more people who volunteer,
the better
chance we have of choosing a random yet representative cross section of
the IETF
population.

Ensuring the leadership of the IETF is fair and balanced and comprised
of those
who can lead the IETF in the right direction is an important
responsibility that
rests on the IETF participants at large.  Volunteering for the nomcom is
a good
way of contributing in that direction.  So please volunteer!

thanks,
Lakshminath


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7651.59">
<TITLE>2007-2008 NomCom</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>dhc WG members - please read the announcement below =
and consider volunteering for the NomCom.<BR>
<BR>
I strongly recommend volunteering - I've participated as both a member =
and as chair - as a way of giving back to the IETF and as a way of =
helping to select the next leadership of the I* organizations.<BR>
<BR>
- Ralph<BR>
<BR>
From: Lakshminath Dondeti<BR>
To: IETF Announcement<BR>
Date: June 4, 2007<BR>
Subject: Nomcom 2007-8: First Call for Volunteers<BR>
<BR>
Folks,<BR>
<BR>
If you have attended 3 out of the past 5 IETF meetings, you are eligible =
to<BR>
serve on Nomcom 2007-2008.&nbsp; Please volunteer and you may become one =
of the<BR>
voting members of the committee that selects about half of the =
members<BR>
to the<BR>
IESG and IAB and one IAOC member.&nbsp; RFC 3777 describes the process =
and the<BR>
responsibilities in detail.&nbsp; Below is the list of people from the =
IESG,<BR>
IAB and<BR>
IAOC whose terms end during the March 2008 IETF meeting.<BR>
<BR>
IAOC:<BR>
<BR>
Ed Juskevicius<BR>
<BR>
IAB:<BR>
<BR>
Leslie Daigle<BR>
Elwyn Davies<BR>
Kevin Fall<BR>
Olaf Kolkman<BR>
David Oran<BR>
Eric Rescorla<BR>
<BR>
IESG:<BR>
<BR>
Lisa Dusseault -- Applications Area Director Jari Arkko -- Internet =
Area<BR>
Director Dan Romascanu -- Operations and Management Area Director =
Cullen<BR>
Jennings -- Real-time Applications and Infrastructure Area Director =
Ross<BR>
Callon<BR>
--- Routing Area Director Sam Hartman -- Security Area Director =
Magnus<BR>
Westerlund -- Transport Area Director<BR>
<BR>
Before volunteering, please think about whether you want to be<BR>
considered for<BR>
one of those positions instead.&nbsp; If you are already convinced, =
please<BR>
send an<BR>
email before 12:00 noon ET (16:00 UTC/GMT) on July 5, 2007 =
(otherwise,<BR>
please<BR>
read on)<BR>
<BR>
To: ldondeti@qualcomm.com<BR>
Subject: Nomcom 2007-8 Volunteer<BR>
Body:<BR>
<BR>
&lt;Your Full Name&gt;&nbsp;&nbsp; // As you enter in the IETF =
Registration Form,<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; // First/Given name followed by Last/Family Name<BR>
&lt;Current Primary Affiliation&gt; // typically what goes in the =
Company field<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; //&nbsp; in the IETF Registration Form<BR>
[&lt;all email addresses used to Register for the past 5 IETF =
meetings&gt;]<BR>
&lt;Preferred<BR>
email address&gt;&nbsp; //<BR>
&lt;Telephone number&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
// For confirmation if selected<BR>
<BR>
Please expect an email response from me within 1-2 days stating =
whether<BR>
you are<BR>
qualified or not.&nbsp; If you don't receive anything, please re-send =
your<BR>
email with<BR>
the tag (duplicate) in the subject line.<BR>
<BR>
Not convinced yet?&nbsp; Please consider that nomcom members play an<BR>
important role<BR>
in shaping the leadership of the IETF.&nbsp; If you are a people person, =
you will<BR>
enjoy meeting many of the active contributors to the IETF.&nbsp; If you =
prefer<BR>
instead to read a lot of email, well, we have that too.&nbsp; Being a =
nomcom<BR>
member<BR>
is also an important responsibility: it requires adherence to<BR>
confidentiality<BR>
rules and some time commitment from the members.&nbsp; The term begins =
just<BR>
prior to<BR>
the Chicago meeting and we expect most of the work to be completed =
by<BR>
January<BR>
2008.&nbsp; During this period, the nomcom members<BR>
<BR>
-- collect requirements from the community and interviews candidates<BR>
&nbsp;&nbsp;&nbsp;&nbsp; during the Chicago and Vancouver IETF =
meetings<BR>
-- review candidates' statements and weighs community feedback<BR>
-- participate in candidate selection deliberations (weekly =
conferences<BR>
calls)<BR>
<BR>
Nomcom members are selected following a publicly verifiable random =
selection<BR>
method specified in RFC 3797.<BR>
<BR>
For the nomcom to work as it should, the pool from which the volunteers =
are<BR>
chosen should be as large as possible. The more people who =
volunteer,<BR>
the better<BR>
chance we have of choosing a random yet representative cross section =
of<BR>
the IETF<BR>
population.<BR>
<BR>
Ensuring the leadership of the IETF is fair and balanced and =
comprised<BR>
of those<BR>
who can lead the IETF in the right direction is an important<BR>
responsibility that<BR>
rests on the IETF participants at large.&nbsp; Volunteering for the =
nomcom is<BR>
a good<BR>
way of contributing in that direction.&nbsp; So please volunteer!<BR>
<BR>
thanks,<BR>
Lakshminath<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7B0D6.47BDE022--


--===============0857603554==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0857603554==--




From dhcwg-bounces@ietf.org Sun Jun 17 21:42:57 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I06Gc-0006PD-L0; Sun, 17 Jun 2007 21:42:54 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I06Gb-0006P4-7A
	for dhcwg@ietf.org; Sun, 17 Jun 2007 21:42:53 -0400
Received: from ind-iport-1.cisco.com ([64.104.129.195])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I06GO-0003vT-G8
	for dhcwg@ietf.org; Sun, 17 Jun 2007 21:42:53 -0400
Received: from hkg-dkim-1.cisco.com ([10.75.231.161])
	by ind-iport-1.cisco.com with ESMTP; 18 Jun 2007 20:11:11 +0530
X-IronPort-AV: i="4.16,432,1175452200"; 
	d="scan'208"; a="82310740:sNHT235002484"
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 l5I1gWrJ015160
	for <dhcwg@ietf.org>; Mon, 18 Jun 2007 09:42:32 +0800
Received: from xbh-hkg-412.apac.cisco.com (xbh-hkg-412.cisco.com
	[64.104.123.69])
	by hkg-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5I1W5qK007977
	for <dhcwg@ietf.org>; Mon, 18 Jun 2007 01:42:32 GMT
Received: from xfe-hkg-411.apac.cisco.com ([64.104.123.70]) by
	xbh-hkg-412.apac.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 18 Jun 2007 09:42:15 +0800
Received: from emakko.cisco.com ([64.104.9.16]) by xfe-hkg-411.apac.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 18 Jun 2007 09:42:14 +0800
Received: from mstenber by emakko.cisco.com with local (Exim 4.63)
	(envelope-from <mstenber@cisco.com>)
	id 1I06Fx-0003nI-Pk; Mon, 18 Jun 2007 10:42:13 +0900
From: Markus Stenberg <mstenber@cisco.com>
To: "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] draft-raj-dhc-tftp-addr-option-02
Organization: cisco Systems, Inc.
References: <8E296595B6471A4689555D5D725EBB21044BE1CE@xmb-rtp-20a.amer.cisco.com>
Date: Mon, 18 Jun 2007 10:42:13 +0900
In-Reply-To: <8E296595B6471A4689555D5D725EBB21044BE1CE@xmb-rtp-20a.amer.cisco.com>
	(Bernie Volz's message of "Sat, 16 Jun 2007 14:34:39 -0400")
Message-ID: <87ps3uyr62.fsf@emakko.cisco.com>
User-Agent: Gnus/5.110006 (No Gnus v0.6) XEmacs/21.4.19 (linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 18 Jun 2007 01:42:14.0695 (UTC)
	FILETIME=[E5A62B70:01C7B149]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1670; t=1182130952;
	x=1182994952; c=relaxed/simple; s=hkgdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mstenber@cisco.com;
	z=From:=20Markus=20Stenberg=20<mstenber@cisco.com>
	|Subject:=20Re=3A=20[dhcwg]=20draft-raj-dhc-tftp-addr-option-02
	|Sender:=20; bh=0h1BAwT4h0EEz4v87oEdixwFmlo+nEtUHmX+VLu9y18=;
	b=PD+VyoMvaIAMDrqg76T28lQ5wqpFsZZXyp4t8S7Xp5ODtbrjYt654TX4yT2Dmi0VlQMR3CSh
	7NyjPvVigSFxqB+cMIyMxWj893CMV79EAqGaDyLzVlY3qtMHYhwXEQyKQqwgekTDVaaKPOVC6U
	17LkGFAGj0PUSFH8dJquPVDxE=;
Authentication-Results: hkg-dkim-1; header.From=mstenber@cisco.com; dkim=pass (
	sig from cisco.com/hkgdkim1002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

"Bernie Volz \(volz\)" <volz@cisco.com> writes:
> The fundamental question is whether this is documenting existing usage
> so that this meets the requirements put forward in RFC 3942 to document
> that usage in order to have the option assigned, or whether we are
> trying to develop a new standard.
>
> If we're documenting existing usage (which is I believe the point of the
> draft), then calling it something specific to what it is used for is
> appropriate.

Agreed. I think that documenting existing solutions is a good idea.

> If we're trying to develop a new standard, let the debate continue.

One thing about the new standard that wasn't brought up yet (I think) is
that even with multiple devices requiring different types of configuration
(Cisco, Avaya phone example), there are many ways of providing them with
correct type-specific configuration with just one 'config option' and still
get meaningful results, for example

- have policies per device (or DUID-mask if they're allocated in some way
  that determines device type), or

- have policies per MAC-mask (ugly)

Pushing it just to all clients wouldn't make sense though (well, at least
if the client type of every client was not known). 'Hey, all clients, here
is a configuration blob you can try.. if you can parse it.. and won't have
problems with it.. use it.' doesn't sound like ideal option semantics to me
;)

Therefore I think that there would be _some_ value for defining just one
configuration blob option, as I think that offering all N types of
configuration payload for a device which cares about 0-1 types would not be
useful.

Cheers,

-Markus

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



From dhcwg-bounces@ietf.org Mon Jun 18 15:50:13 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0NEn-0005kI-3H; Mon, 18 Jun 2007 15:50:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0NEg-0005hv-KH; Mon, 18 Jun 2007 15:50:02 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I0NEg-0001TF-7e; Mon, 18 Jun 2007 15:50:02 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 1EAF726E86;
	Mon, 18 Jun 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I0NEg-00087T-0c; Mon, 18 Jun 2007 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I0NEg-00087T-0c@stiedprstage1.ietf.org>
Date: Mon, 18 Jun 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-dhcpv6-leasequery-01.txt 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

--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		: DHCPv6 Leasequery
	Author(s)	: J. Brzozowski, et al.
	Filename	: draft-ietf-dhc-dhcpv6-leasequery-01.txt
	Pages		: 23
	Date		: 2007-6-18
	
This document specifies a leasequery exchange for the Dynamic Host
   Configuration Protocol for IPv6 (DHCPv6) which can be used to obtain
   lease information about DHCPv6 clients from a DHCPv6 server.  This
   document specifies the scope of data that can be retrieved as well as
   both DHCPv6 leasequery requestor and server behavior.  This document
   extends DHCPv6.

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

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-dhc-dhcpv6-leasequery-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-dhcpv6-leasequery-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-6-18113213.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dhc-dhcpv6-leasequery-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-dhc-dhcpv6-leasequery-01.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-6-18113213.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--




From dhcwg-bounces@ietf.org Tue Jun 19 11:59:27 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0g73-0002Jb-Pd; Tue, 19 Jun 2007 11:59:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0g72-0002JQ-Hx
	for dhcwg@ietf.org; Tue, 19 Jun 2007 11:59:24 -0400
Received: from kecgate03.infosysconsulting.com ([220.227.179.21]
	helo=Kecgate03.infosys.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0g71-0000bo-NC
	for dhcwg@ietf.org; Tue, 19 Jun 2007 11:59:24 -0400
Received: from indhubbhs01.ad.infosys.com ([192.168.200.81]) by
	Kecgate03.infosys.com with InterScan Message Security Suite;
	Tue, 19 Jun 2007 21:29:51 +0530
Received: from blrkechub01.ad.infosys.com ([10.66.236.41]) by
	indhubbhs01.ad.infosys.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Jun 2007 21:29:06 +0530
Received: from BLRKECMBX02.ad.infosys.com ([10.66.236.22]) by
	blrkechub01.ad.infosys.com ([10.66.236.41]) with mapi; Tue, 19 Jun 2007
	21:29:05 +0530
From: bharat_joshi <bharat_joshi@infosys.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Date: Tue, 19 Jun 2007 21:25:03 +0530
Thread-Topic: I-D ACTION:draft-joshi-dhc-layer2-relay-agent-01.txt 
Thread-Index: AcevhruYKh18v/q6To2xBtbETtoJRADA3c2k
Message-ID: <31D55C4D55BEED48A4459EB64567589A092705F634@BLRKECMBX02.ad.infosys.com>
References: <E1HzHo2-0005jB-2U@stiedprstage1.ietf.org>
In-Reply-To: <E1HzHo2-0005jB-2U@stiedprstage1.ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/mixed;
	boundary="_003_31D55C4D55BEED48A4459EB64567589A092705F634BLRKECMBX02ad_"
MIME-Version: 1.0
X-OriginalArrivalTime: 19 Jun 2007 15:59:06.0020 (UTC)
	FILETIME=[C3998E40:01C7B28A]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Subject: [dhcwg] FW: I-D ACTION:draft-joshi-dhc-layer2-relay-agent-01.txt 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

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


Hi All,

      We have published a revised version of our draft 'Layer 2 Relay=
 Agent'. This takes care of certain concenrs raised some time back.

      Please review this document and let us know your comments and=
 suggestions.

Thanks,
Bharat
________________________________________
From: Internet-Drafts@ietf.org [Internet-Drafts@ietf.org]
Sent: Saturday, June 16, 2007 1:20 AM
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-joshi-dhc-layer2-relay-agent-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.


        Title           : Layer 2 Relay Agent
        Author(s)       : B. Joshi, et al.
        Filename        : draft-joshi-dhc-layer2-relay-agent-01.txt
        Pages           : 24
        Date            : 2007-6-15

In Layer 2 Access Networks, Access Concentrators are present between
   DHCP Clients and Relay Agent.  In this case, the Relay Agent can not
   uniquely identify the end host and hence can not add unique 'Relay
   Agent Information' option corresponding to the end hosts in DHCP
   messages.  As the Access concentrators are closer to the end hosts,
   they can uniquely identify the end hosts and add the Relay Agent
   Information option in the DHCP message.  Access concentrators do not
   set the 'giaddr' field.  Access Concentrators in this mode are
   typically known as Layer 2 Relay agents.

   This document provides insight to the behavior of the Access
   Concentrators which act as DHCP Layer 2 Relay Agents in Access
   Networks.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-joshi-dhc-layer2-relay-agent-01.t=
xt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
"get draft-joshi-dhc-layer2-relay-agent-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE /internet-drafts/draft-joshi-dhc-layer2-relay-agent-01.txt".

NOTE:   The mail server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" utility.  To use this
        feature, insert the command "ENCODING mime" before the "FILE"
        command.  To decode the response(s), you will need "munpack" or
        a MIME-compliant mail reader.  Different MIME-compliant mail=
 readers
        exhibit different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have been split
        up into multiple messages), so check your local documentation on
        how to manipulate these messages.

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


**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended=
 solely for the use of the addressee(s). If you are not the intended=
 recipient, please notify the sender by e-mail and delete the original=
 message. Further, you are not to copy, disclose, or distribute this e-mail=
 or its contents to any other person and any such actions are unlawful.=
 This e-mail may contain viruses. Infosys has taken every reasonable=
 precaution to minimize this risk, but is not liable for any damage you may=
 sustain as a result of any virus in this e-mail. You should carry out your=
 own virus checks before opening the e-mail or attachment. Infosys reserves=
 the right to monitor and review the content of all messages sent to or=
 from this e-mail address. Messages sent to or from this e-mail address may=
 be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
--_003_31D55C4D55BEED48A4459EB64567589A092705F634BLRKECMBX02ad_
Content-Type: message/external-body; name="ATT244621151.TXT"
Content-Description: ATT244621151.TXT
Content-Disposition: attachment; filename="ATT244621151.TXT"; size=0;
	creation-date="Sat, 16 Jun 2007 03:34:13 GMT";
	modification-date="Sat, 16 Jun 2007 03:34:13 GMT"
Content-Transfer-Encoding: base64


Q29udGVudC1UeXBlOiBNZXNzYWdlL0V4dGVybmFsLWJvZHk7IGFjY2Vzcy10eXBlPSJtYWlsLXNl
cnZlciI7DQoJc2VydmVyPSJtYWlsc2VydkBpZXRmLm9yZyINCg0KQ29udGVudC1UeXBlOiB0ZXh0
L3BsYWluDQpDb250ZW50LUlEOiA8MjAwNy02LTE1MTQwODIyLkktREBpZXRmLm9yZz4NCg0KRU5D
T0RJTkcgbWltZQ0KRklMRSAvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWpvc2hpLWRoYy1sYXllcjIt
cmVsYXktYWdlbnQtMDEudHh0DQo=

--_003_31D55C4D55BEED48A4459EB64567589A092705F634BLRKECMBX02ad_
Content-Type: text/plain; name="ATT244621152.txt"
Content-Description: ATT244621152.txt
Content-Disposition: attachment; filename="ATT244621152.txt"; size=0;
	creation-date="Sat, 16 Jun 2007 03:34:13 GMT";
	modification-date="Sat, 16 Jun 2007 03:34:13 GMT"
Content-Transfer-Encoding: base64

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkktRC1Bbm5v
dW5jZSBtYWlsaW5nIGxpc3QNCkktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cxLmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vaS1kLWFubm91bmNlDQo=

--_003_31D55C4D55BEED48A4459EB64567589A092705F634BLRKECMBX02ad_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--_003_31D55C4D55BEED48A4459EB64567589A092705F634BLRKECMBX02ad_--





From dhcwg-bounces@ietf.org Tue Jun 19 12:00:45 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0g8L-0003QO-2M; Tue, 19 Jun 2007 12:00:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0g83-0002h7-4a
	for dhcwg@ietf.org; Tue, 19 Jun 2007 12:00:27 -0400
Received: from kecgate02.progeon.com ([61.95.162.76]
	helo=kecgate02.infosys.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I0g82-0000rT-A3
	for dhcwg@ietf.org; Tue, 19 Jun 2007 12:00:27 -0400
Received: from indhubbhs01.ad.infosys.com ([192.168.200.81]) by
	kecgate02.infosys.com with InterScan Message Security Suite;
	Tue, 19 Jun 2007 21:29:03 +0530
Received: from blrkechub01.ad.infosys.com ([10.66.236.41]) by
	indhubbhs01.ad.infosys.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 19 Jun 2007 21:30:18 +0530
Received: from BLRKECMBX02.ad.infosys.com ([10.66.236.22]) by
	blrkechub01.ad.infosys.com ([10.66.236.41]) with mapi; Tue, 19 Jun 2007
	21:30:18 +0530
From: bharat_joshi <bharat_joshi@infosys.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Date: Tue, 19 Jun 2007 21:29:14 +0530
Thread-Topic: I-D ACTION:draft-kurapati-dhc-relay-chaining-dhcpv4-01.txt 
Thread-Index: AcevhrleE6PpMXyWQYWSLeNh93/s8QDBA854
Message-ID: <31D55C4D55BEED48A4459EB64567589A092705F635@BLRKECMBX02.ad.infosys.com>
References: <E1HzHo2-0005j8-1q@stiedprstage1.ietf.org>
In-Reply-To: <E1HzHo2-0005j8-1q@stiedprstage1.ietf.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/mixed;
	boundary="_003_31D55C4D55BEED48A4459EB64567589A092705F635BLRKECMBX02ad_"
MIME-Version: 1.0
X-OriginalArrivalTime: 19 Jun 2007 16:00:18.0754 (UTC)
	FILETIME=[EEF3E220:01C7B28A]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 6ffdee8af20de249c24731d8414917d3
Subject: [dhcwg] FW: I-D
	ACTION:draft-kurapati-dhc-relay-chaining-dhcpv4-01.txt 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

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


Hi All,

      We have published a revised version of our draft 'Relay Chaining in=
 DHCPv4'.

      Please review this document and let us know your comments and=
 suggestions.

Thanks,
Bharat
________________________________________
From: Internet-Drafts@ietf.org [Internet-Drafts@ietf.org]
Sent: Saturday, June 16, 2007 1:20 AM
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-kurapati-dhc-relay-chaining-dhcpv4-01.txt

A New Internet-Draft is available from the on-line Internet-Drafts
directories.


        Title           : Relay Chaining in DHCPv4
        Author(s)       : B. Joshi, P. Kurapati
        Filename        : draft-kurapati-dhc-relay-chaining-dhcpv4-01.txt
        Pages           : 16
        Date            : 2007-6-15

DHCP Relay Agents eliminate the necessity of having a DHCP server on
   each physical network.  In certain network configurations, a DHCP
   server may be multiple subnets away from the DHCP client and multiple
   Relay Agents may be configured to relay DHCP messages to and from
   DHCP client.  Such configuration can be supported only when each
   Relay Agent adds certain Information to DHCP messages before relaying
   them.  This additional information helps in relaying the DHCP reply
   back to the DHCP client through the same path.  This mechanism is
   referred as Relay Chaining.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-kurapati-dhc-relay-chaining-dhcpv=
4-01.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then
"get draft-kurapati-dhc-relay-chaining-dhcpv4-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
        mailserv@ietf.org.
In the body type:
        "FILE=
 /internet-drafts/draft-kurapati-dhc-relay-chaining-dhcpv4-01.txt".

NOTE:   The mail server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" utility.  To use this
        feature, insert the command "ENCODING mime" before the "FILE"
        command.  To decode the response(s), you will need "munpack" or
        a MIME-compliant mail reader.  Different MIME-compliant mail=
 readers
        exhibit different behavior, especially when dealing with
        "multipart" MIME messages (i.e. documents which have been split
        up into multiple messages), so check your local documentation on
        how to manipulate these messages.

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


**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended=
 solely for the use of the addressee(s). If you are not the intended=
 recipient, please notify the sender by e-mail and delete the original=
 message. Further, you are not to copy, disclose, or distribute this e-mail=
 or its contents to any other person and any such actions are unlawful.=
 This e-mail may contain viruses. Infosys has taken every reasonable=
 precaution to minimize this risk, but is not liable for any damage you may=
 sustain as a result of any virus in this e-mail. You should carry out your=
 own virus checks before opening the e-mail or attachment. Infosys reserves=
 the right to monitor and review the content of all messages sent to or=
 from this e-mail address. Messages sent to or from this e-mail address may=
 be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
--_003_31D55C4D55BEED48A4459EB64567589A092705F635BLRKECMBX02ad_
Content-Type: message/external-body; name="ATT244621166.TXT"
Content-Description: ATT244621166.TXT
Content-Disposition: attachment; filename="ATT244621166.TXT"; size=0;
	creation-date="Sat, 16 Jun 2007 03:34:16 GMT";
	modification-date="Sat, 16 Jun 2007 03:34:16 GMT"
Content-Transfer-Encoding: base64


Q29udGVudC1UeXBlOiBNZXNzYWdlL0V4dGVybmFsLWJvZHk7IGFjY2Vzcy10eXBlPSJtYWlsLXNl
cnZlciI7DQoJc2VydmVyPSJtYWlsc2VydkBpZXRmLm9yZyINCg0KQ29udGVudC1UeXBlOiB0ZXh0
L3BsYWluDQpDb250ZW50LUlEOiA8MjAwNy02LTE1MTQwNjQ4LkktREBpZXRmLm9yZz4NCg0KRU5D
T0RJTkcgbWltZQ0KRklMRSAvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWt1cmFwYXRpLWRoYy1yZWxh
eS1jaGFpbmluZy1kaGNwdjQtMDEudHh0DQo=

--_003_31D55C4D55BEED48A4459EB64567589A092705F635BLRKECMBX02ad_
Content-Type: text/plain; name="ATT244621167.txt"
Content-Description: ATT244621167.txt
Content-Disposition: attachment; filename="ATT244621167.txt"; size=0;
	creation-date="Sat, 16 Jun 2007 03:34:16 GMT";
	modification-date="Sat, 16 Jun 2007 03:34:16 GMT"
Content-Transfer-Encoding: base64

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkktRC1Bbm5v
dW5jZSBtYWlsaW5nIGxpc3QNCkktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cxLmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vaS1kLWFubm91bmNlDQo=

--_003_31D55C4D55BEED48A4459EB64567589A092705F635BLRKECMBX02ad_
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--_003_31D55C4D55BEED48A4459EB64567589A092705F635BLRKECMBX02ad_--





From dhcwg-bounces@ietf.org Tue Jun 19 12:19:06 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0gQ4-0004XC-Cl; Tue, 19 Jun 2007 12:19:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I0gQ1-0004X2-FT
	for dhcwg@ietf.org; Tue, 19 Jun 2007 12:19:01 -0400
Received: from h216-18-16-189.gtcust.grouptelecom.net ([216.18.16.189]
	helo=zeus.incognito.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I0gPz-00052u-6u
	for dhcwg@ietf.org; Tue, 19 Jun 2007 12:19:01 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: [dhcwg] FW:
	I-DACTION:draft-kurapati-dhc-relay-chaining-dhcpv4-01.txt 
Content-Transfer-Encoding: quoted-printable
Date: Tue, 19 Jun 2007 09:18:57 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Message-ID: <403B5316AD7A254C9024875BAE481D4EB0E71D@zeus.incognito.com>
In-Reply-To: <31D55C4D55BEED48A4459EB64567589A092705F635@BLRKECMBX02.ad.infosys.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] FW:
	I-DACTION:draft-kurapati-dhc-relay-chaining-dhcpv4-01.txt 
Thread-Index: AcevhrleE6PpMXyWQYWSLeNh93/s8QDBA854AABvDyA=
References: <E1HzHo2-0005j8-1q@stiedprstage1.ietf.org>
	<31D55C4D55BEED48A4459EB64567589A092705F635@BLRKECMBX02.ad.infosys.com>
From: "Andre Kostur" <akostur@incognito.com>
To: "bharat_joshi" <bharat_joshi@infosys.com>,
	<dhcwg@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

> From: bharat_joshi [mailto:bharat_joshi@infosys.com]=20
> Sent: Tuesday, June 19, 2007 8:59 AM
>=20
> Hi All,
>=20
>       We have published a revised version of our draft 'Relay=20
> Chaining in DHCPv4'.
>=20
>       Please review this document and let us know your=20
> comments and suggestions.

Have you considered the interaction of this feature with RFC 4030 (DHCP
Authentication for Relay Agents)?

Let's assume that you have:

  Device -> Relay1 -> Relay2 -> Relay3 -> Relay4 -> DHCPSvr

And that the DHCPSvr and all relays in between wish to exchange
authentication information.  The DHCPSvr will have to reconstruct the
incoming packet 4 times to get the packet as it was seen by each relay
in turn so that it can calculate the hash at each hop, as well as the
server will have to write the returned hash into the packet going back
in 4 places.


Also, I'm not sure what you are getting at in section 7 when you say:

      A Relay Agents relaying DHCP messages to another Relay Agent are
      essentially DHCP clients for the DHCP messages.  Thus, RFC3118 [4]
      is an appropriate mechanism for these DHCP messages.

RFC 3118 already has a clause that the hash is calculated as if option
82 wasn't in the packet.

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



From dhcwg-bounces@ietf.org Tue Jun 19 15:51:14 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0jjM-0003X7-8e; Tue, 19 Jun 2007 15:51:12 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0jii-0002LQ-Pi; Tue, 19 Jun 2007 15:50:33 -0400
Received: from ns4.neustar.com ([156.154.24.139])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I0jii-0002Hk-Fi; Tue, 19 Jun 2007 15:50:32 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns4.neustar.com (Postfix) with ESMTP id 65E5D2ACB8;
	Tue, 19 Jun 2007 19:50:02 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I0jiE-0004lN-4g; Tue, 19 Jun 2007 15:50:02 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1I0jiE-0004lN-4g@stiedprstage1.ietf.org>
Date: Tue, 19 Jun 2007 15:50:02 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-subnet-alloc-05.txt 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

--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		: Subnet Allocation Option
	Author(s)	: R. Johnson, et al.
	Filename	: draft-ietf-dhc-subnet-alloc-05.txt
	Pages		: 31
	Date		: 2007-6-19
	
This document defines a new DHCP option which is passed between the
   DHCP Client and the DHCP Server to request dynamic allocation of a
   subnet, give specifications of subnet(s) allocated, and report usage
   statistics.  This memo documents the current usage of the option in
   agreement with RFC-3942[7], which declares that any pre-existing
   usages of option numbers in the range 128 - 223 should be documented
   and the working group will try to officially assign those numbers to
   those options.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-subnet-alloc-05.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-dhc-subnet-alloc-05.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-dhc-subnet-alloc-05.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-6-19115855.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dhc-subnet-alloc-05.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-dhc-subnet-alloc-05.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-6-19115855.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--NextPart--




From dhcwg-bounces@ietf.org Wed Jun 20 09:46:01 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I10VR-0003tv-34; Wed, 20 Jun 2007 09:45:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I10VP-0003tp-Tz
	for dhcwg@ietf.org; Wed, 20 Jun 2007 09:45:55 -0400
Received: from intermail.se.dataphone.net ([212.37.1.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I10VO-0004HC-Gh
	for dhcwg@ietf.org; Wed, 20 Jun 2007 09:45:55 -0400
Received: from [213.115.152.226] (account budm@weird-solutions.com HELO
	offset.weird.se)
	by intermail.se.dataphone.net (CommuniGate Pro SMTP 4.2)
	with ESMTP id 43661452 for dhcwg@ietf.org;
	Wed, 20 Jun 2007 15:45:53 +0200
From: Bud Millwood <budm@weird-solutions.com>
Organization: Weird Solutions, Inc.
To: dhcwg@ietf.org
Date: Wed, 20 Jun 2007 15:16:44 +0200
User-Agent: KMail/1.8
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200706201516.44236.budm@weird-solutions.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Subject: [dhcwg] Prefix delegation
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bud Millwood <budm@weird-solutions.com>
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

I'm browsing through RFC 3633, and trying to wrap my head around exactly who 
has what responsibilities with Prefix Delegation, and I'd appreciate if 
someone could clarify these basic questions:

If an intermediate router is doing prefix delegation, can that router query a 
DHCP server for a set of prefixes that it can delegate?

Can a DHCP server directly support PD without the intermediate router being 
involved? Is there any reason PD cannot be handled directly by the DHCP 
server?

- Bud

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



From dhcwg-bounces@ietf.org Wed Jun 20 09:58:06 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I10hB-0001OR-Br; Wed, 20 Jun 2007 09:58:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I10h9-0001O6-Nx
	for dhcwg@ietf.org; Wed, 20 Jun 2007 09:58:03 -0400
Received: from paoakoavas10.cable.comcast.com ([208.17.35.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I10h8-0008Bv-DR
	for dhcwg@ietf.org; Wed, 20 Jun 2007 09:58:03 -0400
Received: from ([10.52.116.31])
	by paoakoavas10.cable.comcast.com with ESMTP  id KP-TDCH7.33941197;
	Wed, 20 Jun 2007 09:57:37 -0400
Received: from NJCHLEXCMB01.cable.comcast.com ([172.24.2.44]) by
	PAOAKEXCSMTP02.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 20 Jun 2007 09:57:37 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] Prefix delegation
Date: Wed, 20 Jun 2007 09:52:42 -0400
Message-ID: <997BC128AE961E4A8B880CD7442D9480174D38@NJCHLEXCMB01.cable.comcast.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Prefix delegation
Thread-Index: AcezQWy6q3nr3Hv7QpKs+rC50nSsrAAANkgq
References: <200706201516.44236.budm@weird-solutions.com>
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: "Bud Millwood" <budm@weird-solutions.com>,
	<dhcwg@ietf.org>
X-OriginalArrivalTime: 20 Jun 2007 13:57:37.0188 (UTC)
	FILETIME=[F587CE40:01C7B342]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

hello bud,

I believe the answer is both  are technically viable.  dhcp-pd can =
certainly be handled without the intermediate router being involved with =
prefix acquisition, however, the intermediate router or some portion of =
the underlying network will require information about the delegated =
prefix to ensure routability.

john
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20
John Jason Brzozowski (CISSP, RHCT)
Comcast Corporation
e) mailto:john_brzozowski@cable.comcast.com
m) 609-377-6594
p) 856-324-2671
dc) 168*45683*22
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D



-----Original Message-----
From: Bud Millwood [mailto:budm@weird-solutions.com]
Sent: Wed 6/20/2007 9:16 AM
To: dhcwg@ietf.org
Subject: [dhcwg] Prefix delegation
=20
I'm browsing through RFC 3633, and trying to wrap my head around exactly =
who=20
has what responsibilities with Prefix Delegation, and I'd appreciate if=20
someone could clarify these basic questions:

If an intermediate router is doing prefix delegation, can that router =
query a=20
DHCP server for a set of prefixes that it can delegate?

Can a DHCP server directly support PD without the intermediate router =
being=20
involved? Is there any reason PD cannot be handled directly by the DHCP=20
server?

- Bud

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


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



From dhcwg-bounces@ietf.org Wed Jun 20 10:10:38 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I10tJ-0002RS-7X; Wed, 20 Jun 2007 10:10:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I10tG-0002D7-TD
	for dhcwg@ietf.org; Wed, 20 Jun 2007 10:10:34 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I10tE-0003uX-Cb
	for dhcwg@ietf.org; Wed, 20 Jun 2007 10:10:34 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 20 Jun 2007 10:10:32 -0400
X-IronPort-AV: i="4.16,443,1175486400"; 
	d="scan'208"; a="124119924:sNHT48252550"
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 l5KEAWUQ016975; 
	Wed, 20 Jun 2007 10:10:32 -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.12.10/8.12.6) with ESMTP id l5KEAR5j016629; 
	Wed, 20 Jun 2007 14:10:27 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Jun 2007 10:10:19 -0400
Received: from 10.86.242.247 ([10.86.242.247]) by xmb-rtp-211.amer.cisco.com
	([64.102.31.118]) via Exchange Front-End Server email.cisco.com
	([64.102.31.38]) with Microsoft Exchange Server HTTP-DAV ; 
	Wed, 20 Jun 2007 14:10:18 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Wed, 20 Jun 2007 10:10:52 -0400
Subject: Re: [dhcwg] Prefix delegation
From: Ralph Droms <rdroms@cisco.com>
To: Bud Millwood <budm@weird-solutions.com>, <dhcwg@ietf.org>
Message-ID: <C29EADAC.46F89%rdroms@cisco.com>
Thread-Topic: [dhcwg] Prefix delegation
Thread-Index: AcezRM9GDaB1jR84Edya/wARJOT6eg==
In-Reply-To: <200706201516.44236.budm@weird-solutions.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 20 Jun 2007 14:10:19.0300 (UTC)
	FILETIME=[BBC8DE40:01C7B344]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1258; t=1182348632;
	x=1183212632; 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]=20Prefix=20delegation |Sender:=20
	|To:=20Bud=20Millwood=20<budm@weird-solutions.com>,=20<dhcwg@ietf.org>; 
	bh=GUu6BqX3Cw1HWWkhGqyIFLDg2lSr/j/+GmgmFSezbIo=;
	b=GsLzz3wnFW0kDuuV5n01iDXoseraFElbPIKib7eIMshSNhEAPnCU0IFowl1GeODg3NRUMixq
	x5dspJvA7a4w66tHo3JqUZ+7VL1J2kquCRpPkvlb3kd2gII0BpJUURxv;
Authentication-Results: rtp-dkim-2; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Responses in line...


On 6/20/07 9:16 AM, "Bud Millwood" <budm@weird-solutions.com> wrote:

> I'm browsing through RFC 3633, and trying to wrap my head around exactly who
> has what responsibilities with Prefix Delegation, and I'd appreciate if
> someone could clarify these basic questions:
> 
> If an intermediate router is doing prefix delegation, can that router query a
> DHCP server for a set of prefixes that it can delegate?

Well, assuming that the intermediate router is running a DHCP server to do
PD, there is no formal definition for "hierarchical" PD from a central DHCP
server to multiple subsidiary DHCP servers.  However, there's no reason a
subsidiary server couldn't request, say, a /40 from the central server and
then delegate /48s to requesting routers.

> Can a DHCP server directly support PD without the intermediate router being
> involved? Is there any reason PD cannot be handled directly by the DHCP
> server?

I think this model is exactly what is described in RFC 3633.  The
"delegating router" runs a DHCP server and delegates directly to the
requesting router.

What RFC 3633 doesn't talk about is PD through a relay agetn.  There are
routing issues that need to be solved.

> - Bud

- Ralph


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



From dhcwg-bounces@ietf.org Wed Jun 20 10:56:17 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I11bS-0007vh-9C; Wed, 20 Jun 2007 10:56:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I11bQ-0007lW-T8
	for dhcwg@ietf.org; Wed, 20 Jun 2007 10:56:12 -0400
Received: from intermail.se.dataphone.net ([212.37.1.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I11bO-0002uM-Ie
	for dhcwg@ietf.org; Wed, 20 Jun 2007 10:56:12 -0400
Received: from [213.115.152.226] (account budm@weird-solutions.com HELO
	offset.weird.se)
	by intermail.se.dataphone.net (CommuniGate Pro SMTP 4.2)
	with ESMTP id 43664769 for dhcwg@ietf.org;
	Wed, 20 Jun 2007 16:56:09 +0200
From: Bud Millwood <budm@weird-solutions.com>
Organization: Weird Solutions, Inc.
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Prefix delegation
Date: Wed, 20 Jun 2007 16:26:59 +0200
User-Agent: KMail/1.8
References: <C29EADAC.46F89%rdroms@cisco.com>
In-Reply-To: <C29EADAC.46F89%rdroms@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200706201627.00023.budm@weird-solutions.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bud Millwood <budm@weird-solutions.com>
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Thanks to both of you for the responses. It seems there's really no need for a 
formal definition of heirarchical PD as long as the delegating router can be 
configured to ask the next upstream delegating router (or central server) for 
a prefix.

> > Can a DHCP server directly support PD without the intermediate router
> > being involved? Is there any reason PD cannot be handled directly by the
> > DHCP server?
>
> I think this model is exactly what is described in RFC 3633.  The
> "delegating router" runs a DHCP server and delegates directly to the
> requesting router.
>
> What RFC 3633 doesn't talk about is PD through a relay agetn.  There are
> routing issues that need to be solved.

So this means that until the routing issues are solved, a given router cannot 
(should not?) be both a delegating router and a relay agent?

And if you want to centrally manage all delegated prefixes from a non-router:

  - The DHCP server can delegate directly to a CPE router
 - The DHCP server can delegate to a delegating router that's upstream from 
the CPE router

Sound right?

- Bud

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



From dhcwg-bounces@ietf.org Wed Jun 20 10:57:49 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I11cz-0000Gv-GE; Wed, 20 Jun 2007 10:57:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I11cx-0000GU-On
	for dhcwg@ietf.org; Wed, 20 Jun 2007 10:57:47 -0400
Received: from kecgate06.progeon.com ([61.95.162.82]
	helo=kecgate06.infosys.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I11cu-0003YO-1C
	for dhcwg@ietf.org; Wed, 20 Jun 2007 10:57:47 -0400
Received: from indhubbhs01.ad.infosys.com ([192.168.200.81]) by
	kecgate06.infosys.com with InterScan Message Security Suite;
	Wed, 20 Jun 2007 20:28:22 +0530
Received: from blrkechub04.ad.infosys.com ([10.66.236.44]) by
	indhubbhs01.ad.infosys.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Jun 2007 20:27:42 +0530
Received: from BLRKECMBX02.ad.infosys.com ([10.66.236.22]) by
	blrkechub04.ad.infosys.com ([10.66.236.44]) with mapi; Wed, 20 Jun 2007
	20:27:41 +0530
From: bharat_joshi <bharat_joshi@infosys.com>
To: 'Andre Kostur' <akostur@incognito.com>, "'dhcwg@ietf.org'" <dhcwg@ietf.org>
Date: Wed, 20 Jun 2007 20:27:38 +0530
Subject: RE: [dhcwg] FW:
	I-DACTION:draft-kurapati-dhc-relay-chaining-dhcpv4-01.txt 
Thread-Topic: [dhcwg] FW:
	I-DACTION:draft-kurapati-dhc-relay-chaining-dhcpv4-01.txt 
Thread-Index: AcevhrleE6PpMXyWQYWSLeNh93/s8QDBA854AABvDyAALwJWAA==
Message-ID: <31D55C4D55BEED48A4459EB64567589A092719D2F5@BLRKECMBX02.ad.infosys.com>
References: <E1HzHo2-0005j8-1q@stiedprstage1.ietf.org>
	<31D55C4D55BEED48A4459EB64567589A092705F635@BLRKECMBX02.ad.infosys.com>
	<403B5316AD7A254C9024875BAE481D4EB0E71D@zeus.incognito.com>
In-Reply-To: <403B5316AD7A254C9024875BAE481D4EB0E71D@zeus.incognito.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
X-OriginalArrivalTime: 20 Jun 2007 14:57:42.0072 (UTC)
	FILETIME=[5A357380:01C7B34B]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org


Hi Andre,

    Thanks a lot for your comments. Please see my response in line.

Thanks,
Bharat

> >       We have published a revised version of our draft 'Relay
> > Chaining in DHCPv4'.
> >
> >       Please review this document and let us know your
> > comments and suggestions.
>
> Have you considered the interaction of this feature with RFC 4030 (DHCP
> Authentication for Relay Agents)?
>

We did not consider this.

> Let's assume that you have:
>
>   Device -> Relay1 -> Relay2 -> Relay3 -> Relay4 -> DHCPSvr
>
> And that the DHCPSvr and all relays in between wish to exchange
> authentication information.

Does each relay agent really need to exchange authentication information=
 with DHCP server? I think not. It looks to me that Relay1 should exchange=
 authentication information with Relay2 and Relay2 with Relay3 and so on.

I think by exchanging authentication information you mean that both relay=
 and DHCP server knows how to process a message send by other.

>  The DHCPSvr will have to reconstruct the
> incoming packet 4 times to get the packet as it was seen by each relay
> in turn so that it can calculate the hash at each hop, as well as the
> server will have to write the returned hash into the packet going back
> in 4 places.

I think it should work as follows:

Relay1 adds relay agent information option with authentication option and=
 send it to relay2. relay2 knows how to process it. Now relay2 adds its own=
 relay agent information option and authentication option and send it to=
 relay3. relay3 knows how to process it. Relay3 would do the same and send=
 it to relay4 and finally relay4 would do the same and send it to DHCP=
 server.

As DHCP server exchange authentication information with relay4, it can=
 process this information. Now to find out the Relay Agent information for=
 the 'Device' [that can be used for applying policy], I think DHCP server=
 must be configured with authentication information of relay1.

I understand that there is more processing involved in all the relay agents=
 and DHCP server.

> Also, I'm not sure what you are getting at in section 7 when you say:
>
>       A Relay Agents relaying DHCP messages to another Relay Agent are
>       essentially DHCP clients for the DHCP messages.  Thus, RFC3118 [4]
>       is an appropriate mechanism for these DHCP messages.
>
> RFC 3118 already has a clause that the hash is calculated as if option
> 82 wasn't in the packet.

I think this is incorrect. We shall correct it in our next version.

**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended=
 solely for the use of the addressee(s). If you are not the intended=
 recipient, please notify the sender by e-mail and delete the original=
 message. Further, you are not to copy, disclose, or distribute this e-mail=
 or its contents to any other person and any such actions are unlawful.=
 This e-mail may contain viruses. Infosys has taken every reasonable=
 precaution to minimize this risk, but is not liable for any damage you may=
 sustain as a result of any virus in this e-mail. You should carry out your=
 own virus checks before opening the e-mail or attachment. Infosys reserves=
 the right to monitor and review the content of all messages sent to or=
 from this e-mail address. Messages sent to or from this e-mail address may=
 be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

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



From dhcwg-bounces@ietf.org Wed Jun 20 11:04:05 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I11j2-00073z-TQ; Wed, 20 Jun 2007 11:04:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I11j1-00073r-BA
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:04:03 -0400
Received: from paoakoavas10.cable.comcast.com ([208.17.35.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I11iy-0005IK-2r
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:04:03 -0400
Received: from ([24.40.15.118])
	by paoakoavas10.cable.comcast.com with ESMTP  id KP-TDCH7.33945715;
	Wed, 20 Jun 2007 11:03:37 -0400
Received: from PACDCEXCMB05.cable.comcast.com ([24.40.15.116]) by
	PACDCEXCSMTP04.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 20 Jun 2007 11:03:37 -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
Subject: RE: [dhcwg] Prefix delegation
Date: Wed, 20 Jun 2007 11:03:36 -0400
Message-ID: <EF2F0EC839870F43A6637360BC12ABD40243F441@PACDCEXCMB05.cable.comcast.com>
In-Reply-To: <C29EADAC.46F89%rdroms@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Prefix delegation
Thread-Index: AcezRM9GDaB1jR84Edya/wARJOT6egABzT6Q
From: "Durand, Alain" <Alain_Durand@cable.comcast.com>
To: "Ralph Droms" <rdroms@cisco.com>,
	"Bud Millwood" <budm@weird-solutions.com>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 20 Jun 2007 15:03:37.0324 (UTC)
	FILETIME=[2DF49AC0:01C7B34C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

=20
> From: Ralph Droms [mailto:rdroms@cisco.com]=20
>
> What RFC 3633 doesn't talk about is PD through a relay agetn.=20
> There are routing issues that need to be solved.

This is an important issue that need to be solved if we ever want
prefix delegation to be deployed in a large scale.

  - Alain.

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



From dhcwg-bounces@ietf.org Wed Jun 20 11:09:51 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I11ob-00025b-UL; Wed, 20 Jun 2007 11:09:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I11ob-00025W-1z
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:09:49 -0400
Received: from pacdcimo02.cable.comcast.com ([24.40.8.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I11oa-0007Dx-QT
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:09:49 -0400
Received: from ([10.52.116.31])
	by pacdcimo02.cable.comcast.com with ESMTP  id KP-GZL85.8619253;
	Wed, 20 Jun 2007 11:09:36 -0400
Received: from NJCHLEXCMB01.cable.comcast.com ([172.24.2.44]) by
	PAOAKEXCSMTP02.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 20 Jun 2007 11:09:36 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] Prefix delegation
Date: Wed, 20 Jun 2007 11:09:36 -0400
Message-ID: <997BC128AE961E4A8B880CD7442D9480174D3C@NJCHLEXCMB01.cable.comcast.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Prefix delegation
Thread-Index: AcezSzaCa8FgFSWnQnSB8AnHNoLzmQAAFqjw
References: <C29EADAC.46F89%rdroms@cisco.com>
	<200706201627.00023.budm@weird-solutions.com>
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: "Bud Millwood" <budm@weird-solutions.com>,
	<dhcwg@ietf.org>
X-OriginalArrivalTime: 20 Jun 2007 15:09:36.0797 (UTC)
	FILETIME=[0437D4D0:01C7B34D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

cannot is probably too strong I think it can be done, there might be =
some limitations.

one more note regarding the latter scenario.  in this case if dhcpv6 is =
used to delegate a prefix to a delegating router the dhcp server will =
only ever have knowledge of the delegated prefix not the sub-delegates.  =
depending on your use case this might not be an issue for some I suspect =
it would.

john
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20
John Jason Brzozowski (CISSP, RHCT)
Comcast Corporation
e) mailto:john_brzozowski@cable.comcast.com
m) 609-377-6594
p) 856-324-2671
dc) 168*45683*22
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D



-----Original Message-----
From: Bud Millwood [mailto:budm@weird-solutions.com]
Sent: Wed 6/20/2007 10:26 AM
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Prefix delegation
=20
Thanks to both of you for the responses. It seems there's really no need =
for a=20
formal definition of heirarchical PD as long as the delegating router =
can be=20
configured to ask the next upstream delegating router (or central =
server) for=20
a prefix.

> > Can a DHCP server directly support PD without the intermediate =
router
> > being involved? Is there any reason PD cannot be handled directly by =
the
> > DHCP server?
>
> I think this model is exactly what is described in RFC 3633.  The
> "delegating router" runs a DHCP server and delegates directly to the
> requesting router.
>
> What RFC 3633 doesn't talk about is PD through a relay agetn.  There =
are
> routing issues that need to be solved.

So this means that until the routing issues are solved, a given router =
cannot=20
(should not?) be both a delegating router and a relay agent?

And if you want to centrally manage all delegated prefixes from a =
non-router:

  - The DHCP server can delegate directly to a CPE router
 - The DHCP server can delegate to a delegating router that's upstream =
from=20
the CPE router

Sound right?

- Bud

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


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



From dhcwg-bounces@ietf.org Wed Jun 20 11:19:36 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I11y3-0000wB-2k; Wed, 20 Jun 2007 11:19:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I11y1-0000w1-8T
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:19:33 -0400
Received: from intermail.se.dataphone.net ([212.37.1.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I11xz-0002DM-SX
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:19:33 -0400
Received: from [213.115.152.226] (account budm@weird-solutions.com HELO
	offset.weird.se)
	by intermail.se.dataphone.net (CommuniGate Pro SMTP 4.2)
	with ESMTP id 43665600; Wed, 20 Jun 2007 17:19:30 +0200
From: Bud Millwood <budm@weird-solutions.com>
Organization: Weird Solutions, Inc.
To: "Brzozowski, John" <John_Brzozowski@cable.comcast.com>
Subject: Re: [dhcwg] Prefix delegation
Date: Wed, 20 Jun 2007 16:50:20 +0200
User-Agent: KMail/1.8
References: <C29EADAC.46F89%rdroms@cisco.com>
	<200706201627.00023.budm@weird-solutions.com>
	<997BC128AE961E4A8B880CD7442D9480174D3C@NJCHLEXCMB01.cable.comcast.com>
In-Reply-To: <997BC128AE961E4A8B880CD7442D9480174D3C@NJCHLEXCMB01.cable.comcast.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200706201650.20795.budm@weird-solutions.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bud Millwood <budm@weird-solutions.com>
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Wednesday 20 June 2007 17:09, Brzozowski, John wrote:

> one more note regarding the latter scenario.  in this case if dhcpv6 is
> used to delegate a prefix to a delegating router the dhcp server will only
> ever have knowledge of the delegated prefix not the sub-delegates. 
> depending on your use case this might not be an issue for some I suspect it
> would.

Sure, but I figure that if you're delegating to a delegator, then that's 
exactly the behavior you want - the DHCP server relenquishes control of the 
entire prefix to the delegating router.

- Bud

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



From dhcwg-bounces@ietf.org Wed Jun 20 11:27:42 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I125t-0000C3-7t; Wed, 20 Jun 2007 11:27:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I125s-0000By-7Y
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:27:40 -0400
Received: from pacdcimo01.cable.comcast.com ([24.40.8.145])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I125q-0003nD-Uw
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:27:40 -0400
Received: from ([24.40.15.118])
	by pacdcimo01.cable.comcast.com with ESMTP  id KP-BXT38.4760841;
	Wed, 20 Jun 2007 11:27:13 -0400
Received: from PACDCEXCMB05.cable.comcast.com ([24.40.15.116]) by
	PACDCEXCSMTP04.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 20 Jun 2007 11:27:12 -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
Subject: RE: [dhcwg] Prefix delegation
Date: Wed, 20 Jun 2007 11:27:11 -0400
Message-ID: <EF2F0EC839870F43A6637360BC12ABD40243F46B@PACDCEXCMB05.cable.comcast.com>
In-Reply-To: <200706201650.20795.budm@weird-solutions.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Prefix delegation
Thread-Index: AcezTnlODXXGlLq9RiiBMsSsahmkGwAALy2A
From: "Durand, Alain" <Alain_Durand@cable.comcast.com>
To: "Bud Millwood" <budm@weird-solutions.com>,
	"Brzozowski, John" <John_Brzozowski@cable.comcast.com>
X-OriginalArrivalTime: 20 Jun 2007 15:27:12.0992 (UTC)
	FILETIME=[79C26600:01C7B34F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

> -----Original Message-----
> From: Bud Millwood [mailto:budm@weird-solutions.com]=20
>
> Sure, but I figure that if you're delegating to a delegator,=20
> then that's exactly the behavior you want - the DHCP server=20
> relenquishes control of the entire prefix to the delegating router.

Bud,

There are two things you need to consider:
a) the delegation of a prefix
b) the accounting/reporting of the same

If you do sub-delegation, you may have a hard time to do b)

   - Alain.

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



From dhcwg-bounces@ietf.org Wed Jun 20 11:30:34 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I128f-0006sJ-Sw; Wed, 20 Jun 2007 11:30:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I128e-0006s8-Ee
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:30:32 -0400
Received: from intermail.se.dataphone.net ([212.37.1.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I128d-0004lC-5W
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:30:32 -0400
Received: from [213.115.152.226] (account budm@weird-solutions.com HELO
	offset.weird.se)
	by intermail.se.dataphone.net (CommuniGate Pro SMTP 4.2)
	with ESMTP id 43666028; Wed, 20 Jun 2007 17:30:30 +0200
From: Bud Millwood <budm@weird-solutions.com>
Organization: Weird Solutions, Inc.
To: "Durand, Alain" <Alain_Durand@cable.comcast.com>
Subject: Re: [dhcwg] Prefix delegation
Date: Wed, 20 Jun 2007 17:01:20 +0200
User-Agent: KMail/1.8
References: <EF2F0EC839870F43A6637360BC12ABD40243F441@PACDCEXCMB05.cable.comcast.com>
In-Reply-To: <EF2F0EC839870F43A6637360BC12ABD40243F441@PACDCEXCMB05.cable.comcast.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200706201701.20225.budm@weird-solutions.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: dhcwg@ietf.org, Ralph Droms <rdroms@cisco.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bud Millwood <budm@weird-solutions.com>
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Wednesday 20 June 2007 17:03, Durand, Alain wrote:
> > From: Ralph Droms [mailto:rdroms@cisco.com]
> >
> > What RFC 3633 doesn't talk about is PD through a relay agetn.
> > There are routing issues that need to be solved.

Do you mean that there's a problem if there are *any* relay agents between a 
server and a delegating router?

> This is an important issue that need to be solved if we ever want
> prefix delegation to be deployed in a large scale.

I think I'm missing something here. If a CPE router is a delegating router, 
and any intermediate routers are *not* delegating routers, a central DHCP 
server can delegate prefixes to the CPE routers, right? Is there a routing 
problem with this configuration?

- Bud

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



From dhcwg-bounces@ietf.org Wed Jun 20 11:31:18 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I129O-00081M-2a; Wed, 20 Jun 2007 11:31:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I129M-00080b-J0
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:31:16 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I129L-00058y-8u
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:31:16 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 20 Jun 2007 17:31:15 +0200
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 l5KFVE3Z030128; 
	Wed, 20 Jun 2007 17:31:14 +0200
Received: from gpk-xdm-001.cisco.com (gpk-xdm-001.cisco.com [64.103.70.176])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5KFVDDR019555; 
	Wed, 20 Jun 2007 15:31:13 GMT
Received: from gpk-xdm-001.cisco.com (localhost.localdomain [127.0.0.1])
	by gpk-xdm-001.cisco.com (8.13.1/8.13.1) with ESMTP id l5KFVDeQ020346; 
	Wed, 20 Jun 2007 16:31:13 +0100
Received: (from otroan@localhost)
	by gpk-xdm-001.cisco.com (8.13.1/8.13.1/Submit) id l5KFVCtH020345;
	Wed, 20 Jun 2007 16:31:12 +0100
X-Authentication-Warning: gpk-xdm-001.cisco.com: otroan set sender to
	ot@cisco.com using -f
From: Ole Troan <ot@cisco.com>
To: "Durand\, Alain" <Alain_Durand@cable.comcast.com>
Subject: Re: [dhcwg] Prefix delegation
References: <EF2F0EC839870F43A6637360BC12ABD40243F441@PACDCEXCMB05.cable.comcast.com>
Date: Wed, 20 Jun 2007 16:31:12 +0100
In-Reply-To: <EF2F0EC839870F43A6637360BC12ABD40243F441@PACDCEXCMB05.cable.comcast.com>
	(Alain Durand's message of "Wed\, 20 Jun 2007 11\:03\:36 -0400")
Message-ID: <7t5645i7idb.fsf@gpk-xdm-001.cisco.com>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=421; t=1182353474;
	x=1183217474; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=ot@cisco.com;
	z=From:=20Ole=20Troan=20<ot@cisco.com>
	|Subject:=20Re=3A=20[dhcwg]=20Prefix=20delegation |Sender:=20;
	bh=DQNAwZ2/vsD2Qw0tjheNTnYSLU73aLnfukTzOgZQsxQ=;
	b=X6ekDLbSTfb+0pt+dtmQqPp9nIfYYX8Mdt9Gl3xSYVSooVfETFmnhRhqUExnKezpvM8W9EZd
	XDdjNwCPAKF3l3sLED+gylsQmWxPzRuuz2TeZ9ZUE97bAiJf9BwGXT9K;
Authentication-Results: ams-dkim-1; header.From=ot@cisco.com; dkim=pass (sig
	from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: dhcwg@ietf.org, Bud Millwood <budm@weird-solutions.com>,
	Ralph Droms <rdroms@cisco.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

>  
>> From: Ralph Droms [mailto:rdroms@cisco.com] 
>>
>> What RFC 3633 doesn't talk about is PD through a relay agetn. 
>> There are routing issues that need to be solved.
>
> This is an important issue that need to be solved if we ever want
> prefix delegation to be deployed in a large scale.

this draft explores the solution space:
http://tools.ietf.org/html/draft-stenberg-pd-route-maintenance-00

/ot

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



From dhcwg-bounces@ietf.org Wed Jun 20 11:35:42 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I12Dc-0001t0-UG; Wed, 20 Jun 2007 11:35:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I12Dc-0001ss-97
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:35:40 -0400
Received: from pacdcimo01.cable.comcast.com ([24.40.8.145])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I12Db-0007N0-26
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:35:40 -0400
Received: from ([10.52.116.30])
	by pacdcimo01.cable.comcast.com with ESMTP  id KP-BXT38.4761451;
	Wed, 20 Jun 2007 11:35:21 -0400
Received: from NJCHLEXCMB01.cable.comcast.com ([172.24.2.44]) by
	PAOAKEXCSMTP01.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 20 Jun 2007 11:35:21 -0400
Received: from 172.24.120.57 ([172.24.120.57]) by
	NJCHLEXCMB01.cable.comcast.com ([172.24.2.44]) via Exchange
	Front-End Server webmail.comcast.com ([24.40.8.152]) with
	Microsoft Exchange Server HTTP-DAV ; Wed, 20 Jun 2007 15:35:21 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Wed, 20 Jun 2007 11:33:29 -0400
Subject: Re: [dhcwg] Prefix delegation
From: John Jason Brzozowski <john_brzozowski@cable.comcast.com>
To: Bud Millwood <budm@weird-solutions.com>
Message-ID: <C29EC109.208D9%john_brzozowski@cable.comcast.com>
Thread-Topic: [dhcwg] Prefix delegation
Thread-Index: AcezUFngmJ4U4h9DEdyHTQAX8tljeA==
In-Reply-To: <200706201650.20795.budm@weird-solutions.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 20 Jun 2007 15:35:21.0714 (UTC)
	FILETIME=[9D0F7520:01C7B350]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Yes, I just wanted to make sure that was clear.  It is an important point
that will not work in some deployments.

John


On 6/20/07 10:50 AM, "Bud Millwood" <budm@weird-solutions.com> wrote:

> On Wednesday 20 June 2007 17:09, Brzozowski, John wrote:
> 
>> one more note regarding the latter scenario.  in this case if dhcpv6 is
>> used to delegate a prefix to a delegating router the dhcp server will only
>> ever have knowledge of the delegated prefix not the sub-delegates.
>> depending on your use case this might not be an issue for some I suspect it
>> would.
> 
> Sure, but I figure that if you're delegating to a delegator, then that's
> exactly the behavior you want - the DHCP server relenquishes control of the
> entire prefix to the delegating router.
> 
> - Bud

=========================================
John Jason Brzozowski (CISSP, RHCT)
Comcast Corporation
e) mailto:john_brzozowski@cable.comcast.com
m) 609-377-6594
p) 856-324-2671
=========================================


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



From dhcwg-bounces@ietf.org Wed Jun 20 11:36:57 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I12Er-0003gI-3H; Wed, 20 Jun 2007 11:36:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I12Ep-0003cb-SE
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:36:55 -0400
Received: from intermail.se.dataphone.net ([212.37.1.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I12En-0007t6-IL
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:36:55 -0400
Received: from [213.115.152.226] (account budm@weird-solutions.com HELO
	offset.weird.se)
	by intermail.se.dataphone.net (CommuniGate Pro SMTP 4.2)
	with ESMTP id 43666293; Wed, 20 Jun 2007 17:36:52 +0200
From: Bud Millwood <budm@weird-solutions.com>
Organization: Weird Solutions, Inc.
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Prefix delegation
Date: Wed, 20 Jun 2007 17:07:42 +0200
User-Agent: KMail/1.8
References: <EF2F0EC839870F43A6637360BC12ABD40243F441@PACDCEXCMB05.cable.comcast.com>
	<200706201701.20225.budm@weird-solutions.com>
In-Reply-To: <200706201701.20225.budm@weird-solutions.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200706201707.43018.budm@weird-solutions.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: "Durand, Alain" <Alain_Durand@cable.comcast.com>,
	Ralph Droms <rdroms@cisco.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bud Millwood <budm@weird-solutions.com>
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Wednesday 20 June 2007 17:01, Bud Millwood wrote:
> On Wednesday 20 June 2007 17:03, Durand, Alain wrote:
> > > From: Ralph Droms [mailto:rdroms@cisco.com]
> > >
> > > What RFC 3633 doesn't talk about is PD through a relay agetn.
> > > There are routing issues that need to be solved.
>
> Do you mean that there's a problem if there are *any* relay agents between
> a server and a delegating router?
>
> > This is an important issue that need to be solved if we ever want
> > prefix delegation to be deployed in a large scale.
>
> I think I'm missing something here. If a CPE router is a delegating router,
> and any intermediate routers are *not* delegating routers, a central DHCP
> server can delegate prefixes to the CPE routers, right? Is there a routing
> problem with this configuration?

Scratch that, I think I got my terminology wrong. If a CPE router requests a 
prefix, it's not considered a "delegating router", right? The CPE router is 
then just a router with a DHCP server that happens to have been configured 
using prefix delegation.

So I think I mean, if a CPE router requests a prefix through a relay agent, 
and a central DHCP server delegates that prefix to the CPE router, then: Is 
there a routing problem with the relay agent, or anywhere else in this 
scenario?

(Thanks for the link Ole)

- Bud

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



From dhcwg-bounces@ietf.org Wed Jun 20 11:37:29 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I12FN-00057m-Nm; Wed, 20 Jun 2007 11:37:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I12FM-00055W-HY
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:37:28 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I12FL-0007xs-45
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:37:28 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 20 Jun 2007 08:37:00 -0700
X-IronPort-AV: i="4.16,443,1175497200"; 
	d="scan'208"; a="168809968:sNHT1642058775"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5KFb0Gv019836; 
	Wed, 20 Jun 2007 08:37:00 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l5KFaltv020274;
	Wed, 20 Jun 2007 15:36:59 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Jun 2007 11:36:57 -0400
Received: from 10.86.242.247 ([10.86.242.247]) by xmb-rtp-211.amer.cisco.com
	([64.102.31.118]) via Exchange Front-End Server email.cisco.com
	([64.102.31.21]) with Microsoft Exchange Server HTTP-DAV ; 
	Wed, 20 Jun 2007 15:36:57 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Wed, 20 Jun 2007 11:37:31 -0400
Subject: Re: [dhcwg] Prefix delegation
From: Ralph Droms <rdroms@cisco.com>
To: Bud Millwood <budm@weird-solutions.com>, <dhcwg@ietf.org>
Message-ID: <C29EC1FB.46FD5%rdroms@cisco.com>
Thread-Topic: [dhcwg] Prefix delegation
Thread-Index: AcezUOoeKNUPoh9EEdya/wARJOT6eg==
In-Reply-To: <200706201627.00023.budm@weird-solutions.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 20 Jun 2007 15:36:57.0683 (UTC)
	FILETIME=[D6432A30:01C7B350]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2674; t=1182353820;
	x=1183217820; c=relaxed/simple; s=sjdkim2002;
	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]=20Prefix=20delegation |Sender:=20;
	bh=GXhJwZfc3TsiW8Gz85cxjR902QdUlrzqwOE9lHGGmD4=;
	b=dmCizpid9NMdM8akQ/86EltdwsFU0tKKnByCrqmISOKSlxpSMJRp6mnyKSXf30/sbVAB2tbe
	5HNjsomwdMW+LhALZYXmJothnxMVo3p7+IXcnX3NZvOeufZh2HmJpph7;
Authentication-Results: sj-dkim-2; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Bud - there's a simple (although perhaps only partial) solution for the
routing issue: choose appropriate aggregation so all of the prefixes
delegated through a given relay agent belong to a single prefix.  Now
configure the router on which the relay agent runs to inject routing
information for the aggregated prefix.

+---+
|RR1+----|
+---+    |    +-----------+       +----------+
+---+    |    |Relay agent|       |   DHCP   |
|RR2+----+----+  Router   +--...--+  Server  |
+---+    |    +-----------+       +----------+
+---+    |  dead:beef:ca00::/40
|RR3|----|
+---+              
                   
                   
In this picture, the router is statically configured to advertise
dead:beef:ca00::/40 and the DHCP server is configured to delegate prefixes
from dead:beef:ca00::/40 to the requesting routers RR*.  So, when the DHCP
server delegates dead:beef:ca01::/48 to RR1, the routing info for the
delegated prefix is advertised by the aggregating prefix from the router.

Routing between the relay agent/router and the RRs can be established
through RAAN and DHCPv6 leasequery.

And this only works if its OK to restrict the prefixes assigned to the RRs
to a single aggregating prefix.  That restriction may not be acceptable for
some ISPs.

- Ralph


On 6/20/07 10:26 AM, "Bud Millwood" <budm@weird-solutions.com> wrote:

> Thanks to both of you for the responses. It seems there's really no need for a
> formal definition of heirarchical PD as long as the delegating router can be
> configured to ask the next upstream delegating router (or central server) for
> a prefix.
> 
>>> Can a DHCP server directly support PD without the intermediate router
>>> being involved? Is there any reason PD cannot be handled directly by the
>>> DHCP server?
>> 
>> I think this model is exactly what is described in RFC 3633.  The
>> "delegating router" runs a DHCP server and delegates directly to the
>> requesting router.
>> 
>> What RFC 3633 doesn't talk about is PD through a relay agetn.  There are
>> routing issues that need to be solved.
> 
> So this means that until the routing issues are solved, a given router cannot
> (should not?) be both a delegating router and a relay agent?
> 
> And if you want to centrally manage all delegated prefixes from a non-router:
> 
>   - The DHCP server can delegate directly to a CPE router
>  - The DHCP server can delegate to a delegating router that's upstream from
> the CPE router
> 
> Sound right?
> 
> - Bud
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg

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



From dhcwg-bounces@ietf.org Wed Jun 20 11:41:12 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I12It-0008H5-9N; Wed, 20 Jun 2007 11:41:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I12Ir-0008Gw-SE
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:41:05 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I12Ip-0000RF-JQ
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:41:05 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 20 Jun 2007 17:41:04 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5KFf3Pr023239; 
	Wed, 20 Jun 2007 17:41:03 +0200
Received: from gpk-xdm-001.cisco.com (gpk-xdm-001.cisco.com [64.103.70.176])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5KFf2DR022483; 
	Wed, 20 Jun 2007 15:41:02 GMT
Received: from gpk-xdm-001.cisco.com (localhost.localdomain [127.0.0.1])
	by gpk-xdm-001.cisco.com (8.13.1/8.13.1) with ESMTP id l5KFf2l1020483; 
	Wed, 20 Jun 2007 16:41:02 +0100
Received: (from otroan@localhost)
	by gpk-xdm-001.cisco.com (8.13.1/8.13.1/Submit) id l5KFf2NV020482;
	Wed, 20 Jun 2007 16:41:02 +0100
X-Authentication-Warning: gpk-xdm-001.cisco.com: otroan set sender to
	ot@cisco.com using -f
From: Ole Troan <ot@cisco.com>
To: Bud Millwood <budm@weird-solutions.com>
Subject: Re: [dhcwg] Prefix delegation
References: <EF2F0EC839870F43A6637360BC12ABD40243F441@PACDCEXCMB05.cable.comcast.com>
	<200706201701.20225.budm@weird-solutions.com>
Date: Wed, 20 Jun 2007 16:41:01 +0100
In-Reply-To: <200706201701.20225.budm@weird-solutions.com> (Bud Millwood's
	message of "Wed\, 20 Jun 2007 17\:01\:20 +0200")
Message-ID: <7t5y7ie63ci.fsf@gpk-xdm-001.cisco.com>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1073; t=1182354063;
	x=1183218063; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=ot@cisco.com;
	z=From:=20Ole=20Troan=20<ot@cisco.com>
	|Subject:=20Re=3A=20[dhcwg]=20Prefix=20delegation |Sender:=20;
	bh=yHiVBOQMj9WBj1jlcq7ygklQjuoRdNiGbFsWiMYE1b4=;
	b=mmCSk+vDfTyA/oDi/GY/N2XxTUNaxqK3DlZjsDNV3IYMZVvr/Z5iNHlHTqfTmONK1aLNQ++v
	c2pPL3hi7z88tGxQEchOkgi24ZoPQkHnYQlAS6BLeuqZjAI3+dNRF5Dc;
Authentication-Results: ams-dkim-2; header.From=ot@cisco.com; dkim=pass (sig
	from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: "Durand, Alain" <Alain_Durand@cable.comcast.com>, dhcwg@ietf.org,
	Ralph Droms <rdroms@cisco.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

>> > From: Ralph Droms [mailto:rdroms@cisco.com]
>> >
>> > What RFC 3633 doesn't talk about is PD through a relay agetn.
>> > There are routing issues that need to be solved.
>
> Do you mean that there's a problem if there are *any* relay agents between a 
> server and a delegating router?
>
>> This is an important issue that need to be solved if we ever want
>> prefix delegation to be deployed in a large scale.
>
> I think I'm missing something here. If a CPE router is a delegating router, 
> and any intermediate routers are *not* delegating routers, a central DHCP 
> server can delegate prefixes to the CPE routers, right? Is there a routing 
> problem with this configuration?

not necessarily. someone has to inject a route for the delegated prefix
into the routing system. the PD spec is silent on this.  it would
typically either be the requesting router or the first-hop router
(delegating router or DHCP relay) from the perspective on the requesting
router. you can of course do this in a hierarchical manner too as you
suggest.

/ot

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



From dhcwg-bounces@ietf.org Wed Jun 20 11:44:50 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I12MT-0000An-Dm; Wed, 20 Jun 2007 11:44:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I12MR-0000AU-P0
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:44:47 -0400
Received: from paoakoavas10.cable.comcast.com ([208.17.35.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I12MQ-0001zV-I6
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:44:47 -0400
Received: from ([10.52.116.31])
	by paoakoavas10.cable.comcast.com with ESMTP  id KP-TDCH7.33948784;
	Wed, 20 Jun 2007 11:44:35 -0400
Received: from PACDCEXCMB05.cable.comcast.com ([24.40.15.116]) by
	PAOAKEXCSMTP02.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 20 Jun 2007 11:44:35 -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
Subject: RE: [dhcwg] Prefix delegation
Date: Wed, 20 Jun 2007 11:44:33 -0400
Message-ID: <EF2F0EC839870F43A6637360BC12ABD40243F48D@PACDCEXCMB05.cable.comcast.com>
In-Reply-To: <200706201701.20225.budm@weird-solutions.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Prefix delegation
Thread-Index: AcezUBTwWmHgTlrLSGq4IKzK8JBxKgAAWymA
From: "Durand, Alain" <Alain_Durand@cable.comcast.com>
To: "Bud Millwood" <budm@weird-solutions.com>
X-OriginalArrivalTime: 20 Jun 2007 15:44:36.0000 (UTC)
	FILETIME=[E770CA00:01C7B351]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: dhcwg@ietf.org, Ralph Droms <rdroms@cisco.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

> -----Original Message-----
> From: Bud Millwood [mailto:budm@weird-solutions.com]=20
> I think I'm missing something here. If a CPE router is a=20
> delegating router, and any intermediate routers are *not*=20
> delegating routers, a central DHCP server can delegate=20
> prefixes to the CPE routers, right? Is there a routing=20
> problem with this configuration?

Not really. You have a problem if the delegating router is the
first hop router after the CPE.=20

   - Alain.

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



From dhcwg-bounces@ietf.org Wed Jun 20 11:47:50 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I12PL-0000TB-C7; Wed, 20 Jun 2007 11:47:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I12PK-0000T5-28
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:47:46 -0400
Received: from paoakoavas10.cable.comcast.com ([208.17.35.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I12PI-0002R6-S8
	for dhcwg@ietf.org; Wed, 20 Jun 2007 11:47:46 -0400
Received: from ([10.52.116.31])
	by paoakoavas10.cable.comcast.com with ESMTP  id KP-TDCH7.33949032;
	Wed, 20 Jun 2007 11:47:34 -0400
Received: from PACDCEXCMB05.cable.comcast.com ([24.40.15.116]) by
	PAOAKEXCSMTP02.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 20 Jun 2007 11:47:34 -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
Subject: RE: [dhcwg] Prefix delegation
Date: Wed, 20 Jun 2007 11:47:31 -0400
Message-ID: <EF2F0EC839870F43A6637360BC12ABD40243F48F@PACDCEXCMB05.cable.comcast.com>
In-Reply-To: <C29EC1FB.46FD5%rdroms@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Prefix delegation
Thread-Index: AcezUOoeKNUPoh9EEdya/wARJOT6egAAREww
From: "Durand, Alain" <Alain_Durand@cable.comcast.com>
To: "Ralph Droms" <rdroms@cisco.com>,
	"Bud Millwood" <budm@weird-solutions.com>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 20 Jun 2007 15:47:34.0203 (UTC)
	FILETIME=[51A868B0:01C7B352]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

=20

> -----Original Message-----
> From: Ralph Droms [mailto:rdroms@cisco.com]=20
> Bud - there's a simple (although perhaps only partial)=20
> solution for the routing issue: choose appropriate=20
> aggregation so all of the prefixes delegated through a given=20
> relay agent belong to a single prefix.  Now configure the=20
> router on which the relay agent runs to inject routing=20
> information for the aggregated prefix.
>
>[...]
>=20
> And this only works if its OK to restrict the prefixes=20
> assigned to the RRs to a single aggregating prefix.  That=20
> restriction may not be acceptable for some ISPs.

A clear limitation to this model is what happen if, at some point
down the road, you need to 'split' the router, eg for capacity issue...
You cannot keep the agregate in place.

   - Alain.

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



From dhcwg-bounces@ietf.org Wed Jun 20 12:21:36 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I12vz-0007B6-7P; Wed, 20 Jun 2007 12:21:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I12vy-00073r-5D
	for dhcwg@ietf.org; Wed, 20 Jun 2007 12:21:30 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I12vw-0005E8-TO
	for dhcwg@ietf.org; Wed, 20 Jun 2007 12:21:30 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 20 Jun 2007 12:21:29 -0400
X-IronPort-AV: i="4.16,443,1175486400"; 
	d="scan'208"; a="124135534:sNHT46745164"
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 l5KGLSE0022075; 
	Wed, 20 Jun 2007 12:21:28 -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.12.10/8.12.6) with ESMTP id l5KGLS5f026407; 
	Wed, 20 Jun 2007 16:21:28 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Jun 2007 12:21:24 -0400
Received: from 10.86.242.247 ([10.86.242.247]) by xmb-rtp-211.amer.cisco.com
	([64.102.31.118]) via Exchange Front-End Server email.cisco.com
	([64.102.31.38]) with Microsoft Exchange Server HTTP-DAV ; 
	Wed, 20 Jun 2007 16:21:23 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Wed, 20 Jun 2007 12:21:58 -0400
Subject: Re: [dhcwg] Prefix delegation
From: Ralph Droms <rdroms@cisco.com>
To: "Durand, Alain" <Alain_Durand@cable.comcast.com>,
	Bud Millwood <budm@weird-solutions.com>, <dhcwg@ietf.org>
Message-ID: <C29ECC66.46FFB%rdroms@cisco.com>
Thread-Topic: [dhcwg] Prefix delegation
Thread-Index: AcezUOoeKNUPoh9EEdya/wARJOT6egAAREwwAAFJHh0=
In-Reply-To: <EF2F0EC839870F43A6637360BC12ABD40243F48F@PACDCEXCMB05.cable.comcast.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 20 Jun 2007 16:21:24.0134 (UTC)
	FILETIME=[0B974C60:01C7B357]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1141; t=1182356488;
	x=1183220488; 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]=20Prefix=20delegation |Sender:=20
	|To:=20=22Durand, =20Alain=22=20<Alain_Durand@cable.comcast.com>,
	=0A=20=20
	=20=20=20=20=20=20Bud=20Millwood=20<budm@weird-solutions.com>,
	=20<dhcwg@ie tf.org>;
	bh=nr28sjWEE5LwR4+wb/15V3eucqpBVnKaMP8AjLHx3IU=;
	b=w7/0At5CAkmSkpPBlCPXnOc7jW5rOmyMh8iCAko6QYDBT+B9zgdCIb+dag3tEHBtal2nAQdD
	xvgAde5gJUy9PS5FqwWlK4UOY3S8KifdVZ2WtxEWh/MXKnAa7T2uV3/y;
Authentication-Results: rtp-dkim-2; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Right, and the constraint restricts customer mobility between aggregating
routers (relay agent/router in my picture) if you want to give the customer
a static prefix assignment and avoid customer renumbering.

- Ralph


On 6/20/07 11:47 AM, "Durand, Alain" <Alain_Durand@cable.comcast.com> wrote:

>  
> 
>> -----Original Message-----
>> From: Ralph Droms [mailto:rdroms@cisco.com]
>> Bud - there's a simple (although perhaps only partial)
>> solution for the routing issue: choose appropriate
>> aggregation so all of the prefixes delegated through a given
>> relay agent belong to a single prefix.  Now configure the
>> router on which the relay agent runs to inject routing
>> information for the aggregated prefix.
>> 
>> [...]
>> 
>> And this only works if its OK to restrict the prefixes
>> assigned to the RRs to a single aggregating prefix.  That
>> restriction may not be acceptable for some ISPs.
> 
> A clear limitation to this model is what happen if, at some point
> down the road, you need to 'split' the router, eg for capacity issue...
> You cannot keep the agregate in place.
> 
>    - Alain.

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



From dhcwg-bounces@ietf.org Wed Jun 20 16:02:46 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I16O4-0007lo-22; Wed, 20 Jun 2007 16:02:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I16O2-0007lj-Ra
	for dhcwg@ietf.org; Wed, 20 Jun 2007 16:02:42 -0400
Received: from intermail.se.dataphone.net ([212.37.1.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I16O1-0002ND-Ed
	for dhcwg@ietf.org; Wed, 20 Jun 2007 16:02:42 -0400
Received: from [213.115.152.226] (account budm@weird-solutions.com HELO
	offset.weird.se)
	by intermail.se.dataphone.net (CommuniGate Pro SMTP 4.2)
	with ESMTP id 43674155; Wed, 20 Jun 2007 22:02:39 +0200
From: Bud Millwood <budm@weird-solutions.com>
Organization: Weird Solutions, Inc.
To: Ralph Droms <rdroms@cisco.com>,
 dhcwg@ietf.org
Subject: Re: [dhcwg] Prefix delegation
Date: Wed, 20 Jun 2007 21:33:27 +0200
User-Agent: KMail/1.8
References: <C29EC1FB.46FD5%rdroms@cisco.com>
In-Reply-To: <C29EC1FB.46FD5%rdroms@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200706202133.27395.budm@weird-solutions.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bud Millwood <budm@weird-solutions.com>
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Wednesday 20 June 2007 17:37, you wrote:

> Bud - there's a simple (although perhaps only partial) solution for the
> routing issue: choose appropriate aggregation so all of the prefixes
> delegated through a given relay agent belong to a single prefix.  Now
> configure the router on which the relay agent runs to inject routing
> information for the aggregated prefix.
>
> +---+
>
> |RR1+----|
>
> +---+    |    +-----------+       +----------+
> +---+    |    |Relay agent|       |   DHCP   |
>
> |RR2+----+----+  Router   +--...--+  Server  |
>
> +---+    |    +-----------+       +----------+
> +---+    |  dead:beef:ca00::/40
>
> |RR3|----|
>
> +---+
>
>
> In this picture, the router is statically configured to advertise
> dead:beef:ca00::/40 and the DHCP server is configured to delegate prefixes
> from dead:beef:ca00::/40 to the requesting routers RR*.  So, when the DHCP
> server delegates dead:beef:ca01::/48 to RR1, the routing info for the
> delegated prefix is advertised by the aggregating prefix from the router.

Aha - this was the *only* scenario I considered viable with PD.

Thanks for the input, all of you. I think I'll ice this for the time being, 
and take a closer look at it some other time.

- Bud

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



From dhcwg-bounces@ietf.org Mon Jun 25 10:42:47 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2pm7-0007iE-U8; Mon, 25 Jun 2007 10:42:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2pm6-0007i5-II; Mon, 25 Jun 2007 10:42:42 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I2pm6-00086e-1W; Mon, 25 Jun 2007 10:42:42 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-3.cisco.com with ESMTP; 25 Jun 2007 07:42:41 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aq4HACZwf0arR7PD/2dsb2JhbACOfA
X-IronPort-AV: i="4.16,460,1175497200"; 
	d="scan'208"; a="497399431:sNHT111362532"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l5PEgfC2024321; 
	Mon, 25 Jun 2007 07:42:41 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l5PEgEl6004197;
	Mon, 25 Jun 2007 14:42:40 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 25 Jun 2007 10:42:25 -0400
Received: from 161.44.65.201 ([161.44.65.201]) by xmb-rtp-211.amer.cisco.com
	([64.102.31.118]) via Exchange Front-End Server email.cisco.com
	([64.102.31.38]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon, 25 Jun 2007 14:42:25 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Mon, 25 Jun 2007 10:43:12 -0400
From: Ralph Droms <rdroms@cisco.com>
To: <mip6@ietf.org>, DHC WG <dhcwg@ietf.org>
Message-ID: <C2A54CC0.47BBC%rdroms@cisco.com>
Thread-Topic: EXTENDED: Joint mip6 and dhc WG last call on
	draft-ietf-mip6-bootstrapping-integrated and draft-ietf-mip6-hiopt
Thread-Index: Ace3NyerZjoiHiMqEdylKAARJOT6eg==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 25 Jun 2007 14:42:25.0577 (UTC)
	FILETIME=[0C002990:01C7B737]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1932; t=1182782561;
	x=1183646561; c=relaxed/simple; s=sjdkim3002;
	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:=20EXTENDED=3A=20Joint=20mip6=20and=20dhc=20WG=20last=20call=20o
	n=0A=20draft-ietf-mip6-bootstrapping-integrated=20and=20draft-ietf-mip6-hi
	opt |Sender:=20;
	bh=Jqh+1ftH03rANJN2x5Tzcvdv8A/CEQxF4QxjMkw7BQ0=;
	b=COWTFu+mFVo9bjqYk8aA4w7JYYJSQMDKH/sOctIUqcPtgAuEuDhcTMWQXulVDPCvsF4yNOJ4
	/W32aMFl+JPbunz5XsMjIwsEQvjMPTBk8cHJHTkq/my3PNlPb5O+dDFe;
Authentication-Results: sj-dkim-3; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 1.5 (+)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: 
Subject: [dhcwg] EXTENDED: Joint mip6 and dhc WG last call on
 draft-ietf-mip6-bootstrapping-integrated and draft-ietf-mip6-hiopt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

There has been no response to this WG last call, so the deadline will be
extended to 1700EDT, 07/02/07.

=====
This message announces a joint mip6 and dhc WG last call on
"MIP6-bootstrapping for the Integrated Scenario"
<draft-ietf-mip6-bootstrapping-integrated-04.txt> and "DHCP Option for
Home Information Discovery in MIPv6" <draft-ietf-mip6-hiopt-05.txt>.
The last call will conclude at 1700EDT on 06/28/07.

Note that draft-ietf-mip6-hiopt-05.txt was recently submitted for
publication and should appear on all the usual I-D repositories soon.

The dhc WG is asked to review the use and design of DHCP options in
these documents.

Please respond to this WG last call.  Responses may be sent to either
mip6@ietf.org or dhcwg@ietf.org.  If you support acceptance of the
documents without change, respond with a simple acknowledgment, so that
support for the document can be assessed.  Lack of discussion does not
represent positive support.  If there is no expression of support for
acceptance during the WG last call, the documents will not be advanced
to the IESG.

Summary of documents:

In an integrated mobility scenario, the mobile node's mobility service
is authorized by the same service authorizer as the network access
service authorizer.  draft-ietf-mip6-bootstrapping-integrated-04.txt
defines a method for home agent information discovery for the
integrated scenario.  draft-ietf-mip6-hiopt-05.txt defines a
DHCP-based scheme to enable dynamic discovery of Mobile IPv6 home
agent address, home agent FQDN and home subnet.  New DHCP options are
defined to carry the information from a DHCP server to the DHCP client
running on the mobile node.

These drafts are available as:
http://www.ietf.org/internet-drafts/draft-ietf-mip6-bootstrapping-integrated
-04.txt
and http://www.ietf.org/internet-drafts/draft-ietf-mip6-hiopt-05.txt

- Stig Venaas, Ralph Droms
  dhc WG chairs


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



From dhcwg-bounces@ietf.org Mon Jun 25 14:48:01 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2tbR-0006MW-QQ; Mon, 25 Jun 2007 14:47:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2tbP-0006MR-Pz
	for dhcwg@ietf.org; Mon, 25 Jun 2007 14:47:55 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2tbN-0002x1-4P
	for dhcwg@ietf.org; Mon, 25 Jun 2007 14:47:55 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 713B05A6E5; Mon, 25 Jun 2007 11:47:52 -0700 (PDT)
Date: Mon, 25 Jun 2007 11:47:52 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: DHC WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] EXTENDED: Joint mip6 and dhc WG last call on
	draft-ietf-mip6-bootstrapping-integrated and draft-ietf-mip6-hiopt
Message-ID: <20070625184752.GB6852@isc.org>
References: <C2A54CC0.47BBC%rdroms@cisco.com>
Mime-Version: 1.0
In-Reply-To: <C2A54CC0.47BBC%rdroms@cisco.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1143101332=="
Errors-To: dhcwg-bounces@ietf.org


--===============1143101332==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="YiEDa0DAkWCtVeE4"
Content-Disposition: inline


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

On Mon, Jun 25, 2007 at 10:43:12AM -0400, Ralph Droms wrote:
> There has been no response to this WG last call, so the deadline will be
> extended to 1700EDT, 07/02/07.

My excuse is that I was in Alaska.

> http://www.ietf.org/internet-drafts/draft-ietf-mip6-bootstrapping-integra=
ted
> -04.txt

Correction (I think?):

  http://www.ietf.org/internet-drafts/draft-ietf-mip6-bootstrapping-integra=
ted-dhc-04.txt

I actually don't see a lot in there for DHCWG to review.  Maybe I'm
not looking hard enough?

I am a little concerned (but only a little) at the extent to which
it defines simplified RFC3315 behaviour ("summarizing" the process
in which a client is identified and configured).


   (3) The Relay Agent intercepts the Information Request from the

I think "receives" is a better word, considering that the packet is
transmitted to a multicast address.  "intercept" has more of an
insinuation that the relay would not normally receive the packet.


So I see no problem advancing this draft to the IESG.


> and http://www.ietf.org/internet-drafts/draft-ietf-mip6-hiopt-05.txt

ISC DHCP and others share option processing code between the v4
and v6 side of the house.  I don't know about the others, but the
net effect for ISC DHCP is that code 0 is treated as an "end tag"
(code 255, or "code all ones" for any code width, is not).  This
sounds a little weird, but that's the contrivance of the loop we
selected.

If the sub-options could be numbered from 1, then this draft would
be compatible with our currently released alpha.

If not, then it would take new code, adding more branches between
each run of the option processing loop.


I note also that the sub-option codes are 8-bit code/length pairs.
That doesn't affect ISC DHCP, but I wanted to point it out for other
implementors.

I think this is the first time we've seen non-16-bit code/lengths
inside DHCPv6?


   If the request message carries more than one Home Network Identifier
   options, the reply message MUST contain Home Network Information
   options as many as Home Network Identifier options in the request.

I think 'as many' wants to be moved left 4 words or so.

Second, I think MUST is too strong, since if the DHCP server is not
configured with values, it will be unable to reply.  Consider
specifically server software that does not (yet) have support for
these options - they will certainly have no code which enforces the
construction of 'empty' options.


   The
   Home Network Information options in the reply SHOULD appear in the
   same order as Home Network Identifier options in the request and the
   matching is based on the sequential order of options.  This provides
   a way of matching for Home Network Information options with the same
   id-type.

I don't get it.  The options SHOULD ppear in the same order, which
means they might not, and the order is also used to match replies
against requests?  So the protocol stipulates that sometimes replies
will not match their requests?

I'm pretty sure this doesn't work, and I'm pretty certain that
we don't want to stipulate the strict ordering of the options.


So, I'm not in favor of advancing this document.

If there is a requirement for mulitple instances of these options,
it would be my strong preference for the mechanism to more closely
mimic IA_* options than has been presented here.

I'd also like to see the sub-option-codes numbered from 1, but that's
not a requirement.

--=20
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
				 https://secure.isc.org/store/t-shirt/
--=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

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

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

iD8DBQFGgA3YcXeLeWu2vmoRAhaGAKCt10ubQLGcdbRfK2A4kr7YjkiwzwCgodS7
aBtvSpQhdv3niJtbCz2i288=
=lULS
-----END PGP SIGNATURE-----

--YiEDa0DAkWCtVeE4--


--===============1143101332==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1143101332==--




From dhcwg-bounces@ietf.org Mon Jun 25 16:10:39 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2utI-0000IX-Hx; Mon, 25 Jun 2007 16:10:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2utG-00008q-Sa; Mon, 25 Jun 2007 16:10:26 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I2utG-0003fu-Hh; Mon, 25 Jun 2007 16:10:26 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 5947C26E72;
	Mon, 25 Jun 2007 20:10:26 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I2utG-0006uM-8h; Mon, 25 Jun 2007 16:10:26 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1I2utG-0006uM-8h@stiedprstage1.ietf.org>
Date: Mon, 25 Jun 2007 16:10:26 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: dhc mailing list <dhcwg@ietf.org>, dhc chair <dhc-chairs@tools.ietf.org>,
	Internet Architecture Board <iab@iab.org>, iana@iana.org,
	RFC Editor <rfc-editor@rfc-editor.org>
Subject: [dhcwg] Protocol Action: 'DHCPv4 Relay Agent Flags Suboption' 
 to Proposed Standard 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

The IESG has approved the following document:

- 'DHCPv4 Relay Agent Flags Suboption '
   <draft-ietf-dhc-relay-agent-flags-03.txt> as a Proposed Standard

This document is the product of the Dynamic Host Configuration Working 
Group. 

The IESG contact persons are Jari Arkko and Mark Townsley.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-relay-agent-flags-03.txt

Technical Summary
 
  The document specifies a relay agent suboption that a relay agent
  must include in the relay agent information option. The suboption
  contains flags that an agent can use to provide the server
  information about a client that would otherwise not be available
  to the server. This document also specifies one flag for this
  option to tell the server whether the client messages was sent as
  unicast or broadcast. This flag is useful when server override as
  specified in draft-ietf-dhc-server-override-04 is used.

Working Group Summary

  An issue with server override and server not being able to know
  whether the client message was unicast or broadcast (to
  distinguish between renew and rebind) was brought up in response
  to IETF last call of draft-ietf-dhc-server-override-03 in February
  2006. After discussions in the wg in February and March it was
  concluded that some relay agent sub-option was needed for this.
  This draft was adopted as a wg item after verifying consensus
  on the wg mailing list in June 2006. WGLC was done in September
  2006. Several people supported this document and none were
  against. There were some editorial comments. This new revision
  has been changed to accomodate those comments.

Protocol Quality

  The protocol specified in this document specifies a new DHCPv4
  relay agent suboption. The specification of this protocol is
  pretty simple, and should be trivial to implement.

  Jari Arkko has reviewed this specification for the
  IESG. Thomas Narten has reviewed this specification
  for the IP Directorate.

Note to RFC Editor

   Please expand the acronym DHCP on its first use in the title and in
   the abstract.

   In the last line of the first paragraph of the Introduction,
   the period should go after the references:

   OLD:
   DHCP Server.  [RFC2131] [RFC2132] [RFC3046]
   NEW:
   DHCP Server  [RFC2131] [RFC2132] [RFC3046].


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



From dhcwg-bounces@ietf.org Mon Jun 25 21:42:44 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I304d-0005Sb-Ty; Mon, 25 Jun 2007 21:42:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I304b-0005S6-Rn; Mon, 25 Jun 2007 21:42:29 -0400
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I304a-0007Di-LL; Mon, 25 Jun 2007 21:42:29 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 5A52526E72;
	Tue, 26 Jun 2007 01:42:28 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I304a-0005M4-8k; Mon, 25 Jun 2007 21:42:28 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1I304a-0005M4-8k@stiedprstage1.ietf.org>
Date: Mon, 25 Jun 2007 21:42:28 -0400
X-Spam-Score: -2.8 (--)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: dhc mailing list <dhcwg@ietf.org>, dhc chair <dhc-chairs@tools.ietf.org>,
	Internet Architecture Board <iab@iab.org>, iana@iana.org,
	RFC Editor <rfc-editor@rfc-editor.org>
Subject: [dhcwg] Protocol Action: 'DHCPv6 Leasequery' to Proposed Standard 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

The IESG has approved the following document:

- 'DHCPv6 Leasequery '
   <draft-ietf-dhc-dhcpv6-leasequery-01.txt> as a Proposed Standard

This document is the product of the Dynamic Host Configuration Working 
Group. 

The IESG contact persons are Jari Arkko and Mark Townsley.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-leasequery-01.txt

Technical Summary
 
  "DHCPv6 Leasequery" <draft-ietf-dhc-dhcpv6-leasequery-00.txt>
   specifies a mechanism, "leasequery", for the Dynamic Host
   Configuration Protocol for IPv6 (DHCPv6) through which lease
   information about DHCPv6 clients can be obtained from a DHCPv6
   server.  This document specifies the scope of data that can be
   retrieved as well as both DHCPv6 leasequery requestor and server
   behavior.  This document extends DHCPv6.
 
Working Group Summary
 
  There was significant WG involvement in the development of the final
  version of this document.  There was strong consensus from a few
  individuals, with no dissenting opinions, in response to the WG last
  call. 
 
Protocol Quality
 
  There are no known implementations of the protocol.  Comcast
  contributed to the document, so it is expected that there will be
  implementations to meet Comcast and other DOCSIS 3.0 deployment
  requirements.  No special reviews were performed or required.

  The mechanism in this document is related to and based in
  implementation and deployment experience with a similar leasequery
  mechanism for DHCPv4, RFC 4388.

  Jari Arkko has reviewed this specification for the IESG.
  In addition, Margaret Wasserman from IP Directorate has 
  reviewed the specification.


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



From dhcwg-bounces@ietf.org Tue Jun 26 18:28:41 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3JWa-0003nj-4i; Tue, 26 Jun 2007 18:28:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3JWY-0003kW-De
	for dhcwg@ietf.org; Tue, 26 Jun 2007 18:28:38 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3JVb-0000Xk-Op
	for dhcwg@ietf.org; Tue, 26 Jun 2007 18:28:38 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 4AD9F5A6E5; Tue, 26 Jun 2007 15:27:39 -0700 (PDT)
Date: Tue, 26 Jun 2007 15:27:39 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Message-ID: <20070626222739.GH3771@isc.org>
Mime-Version: 1.0
User-Agent: Mutt/1.5.9i
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Subject: [dhcwg] DHCPv6 ORO - mandatory?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0561491614=="
Errors-To: dhcwg-bounces@ietf.org


--===============0561491614==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="JwB53PgKC5A7+0Ej"
Content-Disposition: inline


--JwB53PgKC5A7+0Ej
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

ISC "dhclient -6" will refuse to run if you do not configure an Option
Request Option in the config file (at some point, we'll create a
default list if none is configured, but we're not there yet).

This is because of:

18.1.1. Creation and Transmission of Request Messages
=2E..
   The client MUST include an Option Request option (see section 22.7)
   to indicate the options the client is interested in receiving.  The
   client MAY include options with data values as hints to the server
   about parameter values the client would like to have returned.

This MUST is missing from the creation/transmission of other
messages (such as Renew and Rebind), and the section 22.7 entry:

   A client MAY include an Option Request option in a Solicit, Request,
   Renew, Rebind, Confirm or Information-request message to inform the
   server about options the client wants the server to send to the
   client.  A server MAY include an Option Request option in a
   Reconfigure option to indicate which options the client should
   request from the server.

seems to relax the requirement from MUST to MAY (and other language
in the RFC supports this).


So the question of the day is wether or not section 18.1.1 was an
editing error - someone missed this while relaxing the requirement?

Or, are clients required ("MUST") to provide the ORO only on Requests?

--=20
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil?	 https://secure.isc.org/store/t-shirt/
--=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

--JwB53PgKC5A7+0Ej
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFGgZLbcXeLeWu2vmoRAv3ZAJwPSghIbhnN1+vmpBtehLtYLs4nngCdEwoI
pOph7dDiyhcYbhFK0ybZetc=
=Gbr7
-----END PGP SIGNATURE-----

--JwB53PgKC5A7+0Ej--


--===============0561491614==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0561491614==--




From dhcwg-bounces@ietf.org Tue Jun 26 18:44:54 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3JmE-00007P-T7; Tue, 26 Jun 2007 18:44:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3JmC-00007D-Sa
	for dhcwg@ietf.org; Tue, 26 Jun 2007 18:44:49 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3Jly-0003yq-U6
	for dhcwg@ietf.org; Tue, 26 Jun 2007 18:44:48 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 26 Jun 2007 18:44:35 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CANoygUZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,464,1175486400"; 
	d="scan'208"; a="124629712:sNHT39477150"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5QMiYbM017688; 
	Tue, 26 Jun 2007 18:44:34 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l5QMiKM3008936; 
	Tue, 26 Jun 2007 22:44:34 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.1830); 
	Tue, 26 Jun 2007 18:44:20 -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
Subject: RE: [dhcwg] DHCPv6 ORO - mandatory?
Date: Tue, 26 Jun 2007 18:44:19 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB2104618EE1@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <20070626222739.GH3771@isc.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] DHCPv6 ORO - mandatory?
Thread-Index: Ace4QWLBz0jD4RrQR4CXOMJ3OpNuYAAAbBQg
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "David W. Hankins" <David_Hankins@isc.org>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 26 Jun 2007 22:44:20.0607 (UTC)
	FILETIME=[891D58F0:01C7B843]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2579; t=1182897874;
	x=1183761874; c=relaxed/simple; s=rtpdkim1001;
	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]=20DHCPv6=20ORO=20-=20mandatory?
	|Sender:=20
	|To:=20=22David=20W.=20Hankins=22=20<David_Hankins@isc.org>,
	=20<dhcwg@iet f.org>;
	bh=YVb7WRF72YhZs7rmB6nMAKbip1eWAieDAwdpk+91dg8=;
	b=LE7kzVOIvcB+ikLF8L/+5FQBRl1Oi8YXkpvO0kpQkXLaRvFAxibxRJuT6A0tB1Qs113IIXFr
	nvLAJ2PakQwnkVjbBZRmtcsBtWE9DdzbPBjRJw3xrhBDCgx4SgMVrGVN;
Authentication-Results: rtp-dkim-1; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

David:

I interprete:

   The client MUST include an Option Request option (see section 22.7)
   to indicate the options the client is interested in receiving.  The

To mean that if the client is NOT interested in receiving any options,
it would not include an ORO (or perhaps send an empty ORO)?

Our server doesn't require you to include an ORO, for what it is worth.
RFC 3315 Section 15 also doesn't include the lack of an ORO as a reason
to drop a packet.

So, I think this was an editing error. Either leave the MUST and say "if
the client is" or change it to MAY to be consistent with the other uses
(latter is probably better). I guess another errata.

- Bernie

-----Original Message-----
From: David W. Hankins [mailto:David_Hankins@isc.org]=20
Sent: Tuesday, June 26, 2007 6:28 PM
To: dhcwg@ietf.org
Subject: [dhcwg] DHCPv6 ORO - mandatory?

ISC "dhclient -6" will refuse to run if you do not configure an Option
Request Option in the config file (at some point, we'll create a
default list if none is configured, but we're not there yet).

This is because of:

18.1.1. Creation and Transmission of Request Messages
...
   The client MUST include an Option Request option (see section 22.7)
   to indicate the options the client is interested in receiving.  The
   client MAY include options with data values as hints to the server
   about parameter values the client would like to have returned.

This MUST is missing from the creation/transmission of other
messages (such as Renew and Rebind), and the section 22.7 entry:

   A client MAY include an Option Request option in a Solicit, Request,
   Renew, Rebind, Confirm or Information-request message to inform the
   server about options the client wants the server to send to the
   client.  A server MAY include an Option Request option in a
   Reconfigure option to indicate which options the client should
   request from the server.

seems to relax the requirement from MUST to MAY (and other language
in the RFC supports this).


So the question of the day is wether or not section 18.1.1 was an
editing error - someone missed this while relaxing the requirement?

Or, are clients required ("MUST") to provide the ORO only on Requests?

--=20
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil?	 https://secure.isc.org/store/t-shirt/
--=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

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



From dhcwg-bounces@ietf.org Tue Jun 26 21:44:03 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3MZd-0002In-G6; Tue, 26 Jun 2007 21:44:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3MZc-0002Id-Bl
	for dhcwg@ietf.org; Tue, 26 Jun 2007 21:44:00 -0400
Received: from pacdcimo02.cable.comcast.com ([24.40.8.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3MZY-0004Ul-2I
	for dhcwg@ietf.org; Tue, 26 Jun 2007 21:44:00 -0400
Received: from ([10.52.116.30])
	by pacdcimo02.cable.comcast.com with ESMTP  id KP-GZL85.8824606;
	Tue, 26 Jun 2007 21:43:37 -0400
Received: from NJCHLEXCMB01.cable.comcast.com ([172.24.2.44]) by
	PAOAKEXCSMTP01.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 26 Jun 2007 21:43:36 -0400
Received: from 74.95.78.52 ([74.95.78.52]) by NJCHLEXCMB01.cable.comcast.com
	([172.24.2.44]) via Exchange Front-End Server
	webmail.comcast.com ([24.40.8.154]) with Microsoft Exchange
	Server HTTP-DAV ; Wed, 27 Jun 2007 01:43:36 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Tue, 26 Jun 2007 21:41:39 -0400
Subject: Re: [dhcwg] DHCPv6 ORO - mandatory?
From: John Jason Brzozowski <john_brzozowski@cable.comcast.com>
To: David Hankins <David_Hankins@isc.org>,
	"dhcwg@ietf.org" <dhcwg@ietf.org>
Message-ID: <C2A73893.22A04%john_brzozowski@cable.comcast.com>
Thread-Topic: [dhcwg] DHCPv6 ORO - mandatory?
Thread-Index: Ace4XE4XjGMRsiRPEdyVtwAX8tljeA==
In-Reply-To: <20070626222739.GH3771@isc.org>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 27 Jun 2007 01:43:36.0958 (UTC)
	FILETIME=[946641E0:01C7B85C]
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

David,

I think this is an extension of the exchange Ted and I had on the ISC
mailing list.  IMHO always requiring an ORO seems wrong, so perhaps this was
an editing error.

John

On 6/26/07 6:27 PM, "David W. Hankins" <David_Hankins@isc.org> wrote:

> ISC "dhclient -6" will refuse to run if you do not configure an Option
> Request Option in the config file (at some point, we'll create a
> default list if none is configured, but we're not there yet).
> 
> This is because of:
> 
> 18.1.1. Creation and Transmission of Request Messages
> ...
>    The client MUST include an Option Request option (see section 22.7)
>    to indicate the options the client is interested in receiving.  The
>    client MAY include options with data values as hints to the server
>    about parameter values the client would like to have returned.
> 
> This MUST is missing from the creation/transmission of other
> messages (such as Renew and Rebind), and the section 22.7 entry:
> 
>    A client MAY include an Option Request option in a Solicit, Request,
>    Renew, Rebind, Confirm or Information-request message to inform the
>    server about options the client wants the server to send to the
>    client.  A server MAY include an Option Request option in a
>    Reconfigure option to indicate which options the client should
>    request from the server.
> 
> seems to relax the requirement from MUST to MAY (and other language
> in the RFC supports this).
> 
> 
> So the question of the day is wether or not section 18.1.1 was an
> editing error - someone missed this while relaxing the requirement?
> 
> Or, are clients required ("MUST") to provide the ORO only on Requests?

=========================================
John Jason Brzozowski (CISSP, RHCT)
Comcast Corporation
e) mailto:john_brzozowski@cable.comcast.com
m) 609-377-6594
p) 856-324-2671
=========================================


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



From dhcwg-bounces@ietf.org Tue Jun 26 21:46:23 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3Mbv-0002sY-93; Tue, 26 Jun 2007 21:46:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3Mbu-0002rJ-78
	for dhcwg@ietf.org; Tue, 26 Jun 2007 21:46:22 -0400
Received: from pacdcimo02.cable.comcast.com ([24.40.8.146])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3Mbp-0004wK-U6
	for dhcwg@ietf.org; Tue, 26 Jun 2007 21:46:22 -0400
Received: from ([10.195.246.152])
	by pacdcimo02.cable.comcast.com with ESMTP  id KP-GZL85.8824626;
	Tue, 26 Jun 2007 21:45:51 -0400
Received: from NJCHLEXCMB01.cable.comcast.com ([172.24.2.44]) by
	NJMDCEXCRLY01.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 26 Jun 2007 21:45:50 -0400
Received: from 74.95.78.52 ([74.95.78.52]) by NJCHLEXCMB01.cable.comcast.com
	([172.24.2.44]) via Exchange Front-End Server
	webmail.comcast.com ([24.40.8.154]) with Microsoft Exchange
	Server HTTP-DAV ; Wed, 27 Jun 2007 01:45:50 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Tue, 26 Jun 2007 21:43:52 -0400
Subject: Re: [dhcwg] DHCPv6 ORO - mandatory?
From: John Jason Brzozowski <john_brzozowski@cable.comcast.com>
To: Bernie Volz <volz@cisco.com>, David Hankins <David_Hankins@isc.org>,
	"dhcwg@ietf.org" <dhcwg@ietf.org>
Message-ID: <C2A73918.22A08%john_brzozowski@cable.comcast.com>
Thread-Topic: [dhcwg] DHCPv6 ORO - mandatory?
Thread-Index: Ace4QWLBz0jD4RrQR4CXOMJ3OpNuYAAAbBQgAAZik38=
In-Reply-To: <8E296595B6471A4689555D5D725EBB2104618EE1@xmb-rtp-20a.amer.cisco.com>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 27 Jun 2007 01:45:50.0963 (UTC)
	FILETIME=[E445CC30:01C7B85C]
X-Spam-Score: 1.6 (+)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

See below.

John


On 6/26/07 6:44 PM, "Bernie Volz (volz)" <volz@cisco.com> wrote:

> David:
> 
> I interprete:
> 
>    The client MUST include an Option Request option (see section 22.7)
>    to indicate the options the client is interested in receiving.  The
> 
> To mean that if the client is NOT interested in receiving any options,
> it would not include an ORO (or perhaps send an empty ORO)?
[jjmb] I would agree.
> 
> Our server doesn't require you to include an ORO, for what it is worth.
> RFC 3315 Section 15 also doesn't include the lack of an ORO as a reason
> to drop a packet.
> 
> So, I think this was an editing error. Either leave the MUST and say "if
> the client is" or change it to MAY to be consistent with the other uses
> (latter is probably better). I guess another errata.
[jjmb] I am with Bernie the latter seems like a better route.
> 
> - Bernie
> 
> -----Original Message-----
> From: David W. Hankins [mailto:David_Hankins@isc.org]
> Sent: Tuesday, June 26, 2007 6:28 PM
> To: dhcwg@ietf.org
> Subject: [dhcwg] DHCPv6 ORO - mandatory?
> 
> ISC "dhclient -6" will refuse to run if you do not configure an Option
> Request Option in the config file (at some point, we'll create a
> default list if none is configured, but we're not there yet).
> 
> This is because of:
> 
> 18.1.1. Creation and Transmission of Request Messages
> ...
>    The client MUST include an Option Request option (see section 22.7)
>    to indicate the options the client is interested in receiving.  The
>    client MAY include options with data values as hints to the server
>    about parameter values the client would like to have returned.
> 
> This MUST is missing from the creation/transmission of other
> messages (such as Renew and Rebind), and the section 22.7 entry:
> 
>    A client MAY include an Option Request option in a Solicit, Request,
>    Renew, Rebind, Confirm or Information-request message to inform the
>    server about options the client wants the server to send to the
>    client.  A server MAY include an Option Request option in a
>    Reconfigure option to indicate which options the client should
>    request from the server.
> 
> seems to relax the requirement from MUST to MAY (and other language
> in the RFC supports this).
> 
> 
> So the question of the day is wether or not section 18.1.1 was an
> editing error - someone missed this while relaxing the requirement?
> 
> Or, are clients required ("MUST") to provide the ORO only on Requests?

=========================================
John Jason Brzozowski (CISSP, RHCT)
Comcast Corporation
e) mailto:john_brzozowski@cable.comcast.com
m) 609-377-6594
p) 856-324-2671
=========================================


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



From dhcwg-bounces@ietf.org Wed Jun 27 00:59:26 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3Pch-0008Rm-Eo; Wed, 27 Jun 2007 00:59:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3Pcf-0008Hk-CE
	for dhcwg@ietf.org; Wed, 27 Jun 2007 00:59:21 -0400
Received: from exprod7og56.obsmtp.com ([64.18.2.167])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3PcV-00026s-6s
	for dhcwg@ietf.org; Wed, 27 Jun 2007 00:59:21 -0400
Received: from source ([81.200.64.181]) (using TLSv1) by
	exprod7ob56.obsmtp.com ([64.18.6.12]) with SMTP; 
	Tue, 26 Jun 2007 21:59:09 PDT
Received: from mail.nominum.com (mail.nominum.com [81.200.64.186])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by shell-ng.nominum.com (Postfix) with ESMTP id 149C756860;
	Tue, 26 Jun 2007 21:59:09 -0700 (PDT)
	(envelope-from Ted.Lemon@nominum.com)
X-Spam-Status: No, hits=0.0 required=8.4
	tests=CUSTOM_RULE_FROM: ALLOW,TOTAL_SCORE: 0.000
X-Spam-Level: 
Received: from [10.59.1.113] ([209.124.158.60])
	(authenticated user mellon@nominum.com) by mail.nominum.com
	(using TLSv1/SSLv3 with cipher AES128-SHA (128 bits));
	Tue, 26 Jun 2007 21:59:05 -0700
In-Reply-To: <C2A73893.22A04%john_brzozowski@cable.comcast.com>
References: <C2A73893.22A04%john_brzozowski@cable.comcast.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <00C1A66B-B31A-4966-801C-C7590A38D9A3@nominum.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] DHCPv6 ORO - mandatory?
Date: Tue, 26 Jun 2007 20:58:49 -0800
To: John Jason Brzozowski <john_brzozowski@cable.comcast.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Jun 26, 2007, at 5:41 PM, John Jason Brzozowski wrote:
> I think this is an extension of the exchange Ted and I had on the ISC
> mailing list.  IMHO always requiring an ORO seems wrong, so perhaps  
> this was
> an editing error.

As I stated during that conversation, I actually think making the ORO  
optional is just begging for interoperability problems.   The  
server's behavior in the case where no ORO is provided is undefined;  
that means that it's probably not what the client author would have  
anticipated.   So this interpretation runs the risk of a repeat of  
the "popular server deemed standard" problem we had with DHCPv4,  
where DHCP client implementations were generally tested against a  
single server which didn't follow the standard very well, and when  
that worked the authors assumed that the clients were correct.    
Interoperability problems resulting from this still crop up from time  
to time.

So I would argue that if we do a correction to RFC3315, the ORO  
should be made mandatory, not optional.   I don't think servers can  
savely drop packets with no ORO, but it's unrealistic to expect  
correct behavior if you don't send an ORO, whether the standard  
requires it or not.



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



From dhcwg-bounces@ietf.org Wed Jun 27 01:43:04 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3QIw-0000Fv-B9; Wed, 27 Jun 2007 01:43:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3QIu-0000FY-Kh
	for dhcwg@ietf.org; Wed, 27 Jun 2007 01:43:00 -0400
Received: from tyholt.uninett.no ([2001:700:1::eecb])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3QIj-0006Ju-MK
	for dhcwg@ietf.org; Wed, 27 Jun 2007 01:43:00 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by tyholt.uninett.no (Postfix) with ESMTP id 56F87B5B4E;
	Wed, 27 Jun 2007 07:42:48 +0200 (CEST)
Received: from tyholt.uninett.no ([127.0.0.1])
	by localhost (tyholt.uninett.no [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 05575-03; Wed, 27 Jun 2007 07:42:48 +0200 (CEST)
Received: from [IPv6?2001?700?1?1100?1dc3?403b?dbc6?6c1] (unknown
	[IPv6:2001:700:1:1100:1dc3:403b:dbc6:6c1])
	by tyholt.uninett.no (Postfix) with ESMTP id DB61FB5B4D;
	Wed, 27 Jun 2007 07:42:47 +0200 (CEST)
Message-ID: <4681F8D7.6040702@uninett.no>
Date: Wed, 27 Jun 2007 07:42:47 +0200
From: Stig Venaas <stig.venaas@uninett.no>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: dhcwg <dhcwg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at uninett.no
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4
Cc: Ralph Droms <rdroms@cisco.com>
Subject: [dhcwg] Call for agenda items for dhc wg meeting at IETF 69 in
	Chicago
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

We need to come up with a draft agenda soon. Please email Ralph
and me if you wish to present at the dhc wg meeting at IETF 69.

Stig

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



From dhcwg-bounces@ietf.org Wed Jun 27 03:32:42 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3S0x-00029Z-Ak; Wed, 27 Jun 2007 03:32:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3S0v-000295-Fs
	for dhcwg@ietf.org; Wed, 27 Jun 2007 03:32:33 -0400
Received: from zns001-0m9001.yokogawa.co.jp ([203.174.79.138])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3S0q-0001eu-Q7
	for dhcwg@ietf.org; Wed, 27 Jun 2007 03:32:33 -0400
Received: from zns001-0m9001.yokogawa.co.jp (localhost [127.0.0.1])
	by zns001-0m9001.yokogawa.co.jp (8.12.10+Sun/8.12.10) with ESMTP id
	l5R7WPP1023822; Wed, 27 Jun 2007 16:32:25 +0900 (JST)
Received: from EXCHANGE03.jp.ykgw.net (zex001-0m9003.jp.ykgw.net [10.0.11.23])
	by zns001-0m9001.yokogawa.co.jp (8.12.10+Sun/8.12.10) with ESMTP id
	l5R7WPB1023815; Wed, 27 Jun 2007 16:32:25 +0900 (JST)
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
Subject: RE: [dhcwg] DHCPv6 ORO - mandatory?
Date: Wed, 27 Jun 2007 16:32:19 +0900
Message-ID: <0260031F55435342859BFB2CCA6773D81B898B98@EXCHANGE03.jp.ykgw.net>
In-Reply-To: <8E296595B6471A4689555D5D725EBB2104618EE1@xmb-rtp-20a.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] DHCPv6 ORO - mandatory?
Thread-Index: Ace4QWLBz0jD4RrQR4CXOMJ3OpNuYAAAbBQgABJSv0A=
From: <Hideshi.Enokihara@jp.yokogawa.com>
To: <volz@cisco.com>, <David_Hankins@isc.org>, <dhcwg@ietf.org>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

I think that if this is kind of an editing error,
also section 17.1.1 should be corrected.

17.1.1. Creation of Solicit Messages
(snip)
   The client SHOULD include an Option Request option (see section 22.7)
   to indicate the options the client is interested in receiving.  The
   client MAY additionally include instances of those options that are
   identified in the Option Request option, with data values as hints to
   the server about parameter values the client would like to have
   returned.
(snip)

This "SHOULD" also change to "MAY" or somthing?

Regards,

> -----Original Message-----
> From: Bernie Volz (volz) [mailto:volz@cisco.com]=20
> Sent: Wednesday, June 27, 2007 7:44 AM
> To: David W. Hankins; dhcwg@ietf.org
> Subject: RE: [dhcwg] DHCPv6 ORO - mandatory?
>=20
> David:
>=20
> I interprete:
>=20
>    The client MUST include an Option Request option (see section 22.7)
>    to indicate the options the client is interested in receiving.  The
>=20
> To mean that if the client is NOT interested in receiving any=20
> options, it would not include an ORO (or perhaps send an empty ORO)?
>=20
> Our server doesn't require you to include an ORO, for what it=20
> is worth.
> RFC 3315 Section 15 also doesn't include the lack of an ORO=20
> as a reason to drop a packet.
>=20
> So, I think this was an editing error. Either leave the MUST=20
> and say "if the client is" or change it to MAY to be=20
> consistent with the other uses (latter is probably better). I=20
> guess another errata.
>=20
> - Bernie
>=20
> -----Original Message-----
> From: David W. Hankins [mailto:David_Hankins@isc.org]
> Sent: Tuesday, June 26, 2007 6:28 PM
> To: dhcwg@ietf.org
> Subject: [dhcwg] DHCPv6 ORO - mandatory?
>=20
> ISC "dhclient -6" will refuse to run if you do not configure=20
> an Option Request Option in the config file (at some point,=20
> we'll create a default list if none is configured, but we're=20
> not there yet).
>=20
> This is because of:
>=20
> 18.1.1. Creation and Transmission of Request Messages ...
>    The client MUST include an Option Request option (see section 22.7)
>    to indicate the options the client is interested in receiving.  The
>    client MAY include options with data values as hints to the server
>    about parameter values the client would like to have returned.
>=20
> This MUST is missing from the creation/transmission of other=20
> messages (such as Renew and Rebind), and the section 22.7 entry:
>=20
>    A client MAY include an Option Request option in a=20
> Solicit, Request,
>    Renew, Rebind, Confirm or Information-request message to inform the
>    server about options the client wants the server to send to the
>    client.  A server MAY include an Option Request option in a
>    Reconfigure option to indicate which options the client should
>    request from the server.
>=20
> seems to relax the requirement from MUST to MAY (and other=20
> language in the RFC supports this).
>=20
>=20
> So the question of the day is wether or not section 18.1.1=20
> was an editing error - someone missed this while relaxing the=20
> requirement?
>=20
> Or, are clients required ("MUST") to provide the ORO only on Requests?
>=20
> --
> Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
> Why settle for the lesser evil?	=20
> https://secure.isc.org/store/t-shirt/
> --=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
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg
>=20

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



From dhcwg-bounces@ietf.org Wed Jun 27 03:40:36 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3S8d-0002mE-Nf; Wed, 27 Jun 2007 03:40:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3S8c-0002m8-Qk
	for dhcwg@ietf.org; Wed, 27 Jun 2007 03:40:30 -0400
Received: from zns001-0m9001.yokogawa.co.jp ([203.174.79.138])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3S7i-00032K-2D
	for dhcwg@ietf.org; Wed, 27 Jun 2007 03:40:30 -0400
Received: from zns001-0m9001.yokogawa.co.jp (localhost [127.0.0.1])
	by zns001-0m9001.yokogawa.co.jp (8.12.10+Sun/8.12.10) with ESMTP id
	l5R7dVP1027466; Wed, 27 Jun 2007 16:39:31 +0900 (JST)
Received: from EXCHANGE03.jp.ykgw.net (zex001-0m9003.jp.ykgw.net [10.0.11.23])
	by zns001-0m9001.yokogawa.co.jp (8.12.10+Sun/8.12.10) with ESMTP id
	l5R7dOB1027358; Wed, 27 Jun 2007 16:39:24 +0900 (JST)
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
Subject: RE: [dhcwg] DHCPv6 ORO - mandatory?
Date: Wed, 27 Jun 2007 16:39:23 +0900
Message-ID: <0260031F55435342859BFB2CCA6773D81B898B99@EXCHANGE03.jp.ykgw.net>
In-Reply-To: <00C1A66B-B31A-4966-801C-C7590A38D9A3@nominum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] DHCPv6 ORO - mandatory?
Thread-Index: Ace4eA4fnYsNv9a7RAuQaE8ai2BqDwAFU6vA
From: <Hideshi.Enokihara@jp.yokogawa.com>
To: <Ted.Lemon@nominum.com>, <john_brzozowski@cable.comcast.com>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

=20
> optional is just begging for interoperability problems.   The =20
> server's behavior in the case where no ORO is provided is=20
> undefined;=20
How about following sections?

17.2.2. Creation and Transmission of Advertise Messages
(snip)
   The server includes options the server will return to the client in a
   subsequent Reply message.  The information in these options may be
   used by the client in the selection of a server if the client
   receives more than one Advertise message.  If the client has included
   an Option Request option in the Solicit message, the server includes
   options in the Advertise message containing configuration parameters
   for all of the options identified in the Option Request option that
   the server has been configured to return to the client.  The server
   MAY return additional options to the client if it has been configured
   to do so.  The server must be aware of the recommendations on packet
   sizes and the use of fragmentation in section 5 of RFC 2460.

18.2. Server Behavior
(snip)

   In most Reply messages, the server includes options containing
   configuration information for the client.  The server must be aware
   of the recommendations on packet sizes and the use of fragmentation
   in section 5 of RFC 2460.  If the client included an Option Request
   option in its message, the server includes options in the Reply
   message containing configuration parameters for all of the options
   identified in the Option Request option that the server has been
   configured to return to the client.  The server MAY return additional
   options to the client if it has been configured to do so.

Regards,
Hideshi
> -----Original Message-----
> From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
> Sent: Wednesday, June 27, 2007 1:59 PM
> To: John Jason Brzozowski
> Cc: dhcwg@ietf.org
> Subject: Re: [dhcwg] DHCPv6 ORO - mandatory?
>=20
> On Jun 26, 2007, at 5:41 PM, John Jason Brzozowski wrote:
> > I think this is an extension of the exchange Ted and I had=20
> on the ISC=20
> > mailing list.  IMHO always requiring an ORO seems wrong, so perhaps=20
> > this was an editing error.
>=20
> As I stated during that conversation, I actually think making=20
> the ORO =20
> optional is just begging for interoperability problems.   The =20
> server's behavior in the case where no ORO is provided is=20
> undefined; that means that it's probably not what the client=20
> author would have =20
> anticipated.   So this interpretation runs the risk of a repeat of =20
> the "popular server deemed standard" problem we had with=20
> DHCPv4, where DHCP client implementations were generally=20
> tested against a single server which didn't follow the=20
> standard very well, and when =20
> that worked the authors assumed that the clients were correct.   =20
> Interoperability problems resulting from this still crop up=20
> from time to time.
>=20
> So I would argue that if we do a correction to RFC3315, the ORO =20
> should be made mandatory, not optional.   I don't think servers can =20
> savely drop packets with no ORO, but it's unrealistic to=20
> expect correct behavior if you don't send an ORO, whether the=20
> standard requires it or not.
>=20
>=20
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg
>=20

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



From dhcwg-bounces@ietf.org Wed Jun 27 05:40:30 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3U0d-0006Q8-7I; Wed, 27 Jun 2007 05:40:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3U0c-0006Pu-TK
	for dhcwg@ietf.org; Wed, 27 Jun 2007 05:40:22 -0400
Received: from tyholt.uninett.no ([2001:700:1::eecb])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3U0R-0006ws-44
	for dhcwg@ietf.org; Wed, 27 Jun 2007 05:40:22 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by tyholt.uninett.no (Postfix) with ESMTP id B6966B5AB3
	for <dhcwg@ietf.org>; Wed, 27 Jun 2007 11:40:09 +0200 (CEST)
Received: from tyholt.uninett.no ([127.0.0.1])
	by localhost (tyholt.uninett.no [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 02073-01-19 for <dhcwg@ietf.org>;
	Wed, 27 Jun 2007 11:40:09 +0200 (CEST)
Received: from [IPv6?2001?700?1?7?215?f2ff?fe35?307d] (sverresborg.uninett.no
	[IPv6:2001:700:1:7:215:f2ff:fe35:307d])
	by tyholt.uninett.no (Postfix) with ESMTP id 7C436B5A54
	for <dhcwg@ietf.org>; Wed, 27 Jun 2007 11:40:09 +0200 (CEST)
Message-ID: <46823079.5050405@uninett.no>
Date: Wed, 27 Jun 2007 11:40:09 +0200
From: Stig Venaas <stig.venaas@uninett.no>
User-Agent: Thunderbird 2.0.0.0 (X11/20070529)
MIME-Version: 1.0
To: dhcwg <dhcwg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at uninett.no
X-Spam-Score: -2.8 (--)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Subject: [dhcwg] dhc wg last call on  draft-ietf-dhc-pxelinux-01
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

This message announces a dhc wg last call on "PXELINUX Use of 'Site
Local' Option Space" <draft-ietf-dhc-pxelinux-01.txt>.  The last call
will conclude at 1700EDT on Mon, 2007-07-09.

Please respond to this WG last call.  If you support acceptance of the
document without change, respond with a simple acknowledgment, so that
support for the document can be assessed.  Lack of discussion does not
represent positive support.  If there is no expression of support for
acceptance during the WG last call, the document will not be advanced
to the IESG.

draft-ietf-dhc-pxelinux-01 is in response to the process of
reclassifying site-specific options, RFC 3942, and describes the use
by PXELINUX of some DHCP Option Codes numbering from 208-211.  These
codes were designated 'Site Local' prior to this action, and are
redefined by RFC 3942 as available for allocation as standard DHCP
Options.

Stig

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



From dhcwg-bounces@ietf.org Wed Jun 27 13:37:09 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3bRz-0001Nw-A1; Wed, 27 Jun 2007 13:37:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3bRy-0001MF-29
	for dhcwg@ietf.org; Wed, 27 Jun 2007 13:37:06 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3bRB-0002kz-Kg
	for dhcwg@ietf.org; Wed, 27 Jun 2007 13:37:06 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id CE7D45A6E7; Wed, 27 Jun 2007 10:36:14 -0700 (PDT)
Date: Wed, 27 Jun 2007 10:36:14 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: DHC WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] DHCPv6 ORO - mandatory?
Message-ID: <20070627173614.GB10297@isc.org>
References: <20070626222739.GH3771@isc.org>
	<C2A73893.22A04%john_brzozowski@cable.comcast.com>
Mime-Version: 1.0
In-Reply-To: <C2A73893.22A04%john_brzozowski@cable.comcast.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -2.3 (--)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0013557717=="
Errors-To: dhcwg-bounces@ietf.org


--===============0013557717==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="hQiwHBbRI9kgIhsi"
Content-Disposition: inline


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

On Tue, Jun 26, 2007 at 09:41:39PM -0400, John Jason Brzozowski wrote:
> I think this is an extension of the exchange Ted and I had on the ISC
> mailing list.

That's correct, I thought you two had struck upon a question for the
WG to clarify the rfc.

The thread is here for the curious;

  http://marc.info/?t=3D118164061200001&r=3D1&w=3D2

> IMHO always requiring an ORO seems wrong, so perhaps this was
> an editing error.

Given the weight of other text (quoted by Hideshi), I think it is an
editing error as well.  I possibly would have preferred that the ORO
was client mandatory (even if servers were allowed to answer in its
absence), given our experiences with the DHCPv4 PRL.

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

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

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

iD8DBQFGgqAOcXeLeWu2vmoRAgObAKC0HhDrlz96TpycgxwPQ0hD4eNtvACcCitM
Ny3gbsbkXQffWuP1dnq3mV4=
=imfv
-----END PGP SIGNATURE-----

--hQiwHBbRI9kgIhsi--


--===============0013557717==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0013557717==--




From dhcwg-bounces@ietf.org Wed Jun 27 13:56:49 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3bl2-0005GH-AP; Wed, 27 Jun 2007 13:56:48 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3bl0-00058P-Od
	for dhcwg@ietf.org; Wed, 27 Jun 2007 13:56:46 -0400
Received: from goliath.isc.org ([204.152.187.72])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3bl0-0000jT-Gc
	for dhcwg@ietf.org; Wed, 27 Jun 2007 13:56:46 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 7244A5A6E5; Wed, 27 Jun 2007 10:56:13 -0700 (PDT)
Date: Wed, 27 Jun 2007 10:56:13 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: DHC WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] DHCPv6 ORO - mandatory?
Message-ID: <20070627175613.GC10297@isc.org>
References: <C2A73893.22A04%john_brzozowski@cable.comcast.com>
	<00C1A66B-B31A-4966-801C-C7590A38D9A3@nominum.com>
Mime-Version: 1.0
In-Reply-To: <00C1A66B-B31A-4966-801C-C7590A38D9A3@nominum.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0507847940=="
Errors-To: dhcwg-bounces@ietf.org


--===============0507847940==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="5QAgd0e35j3NYeGe"
Content-Disposition: inline


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

On Tue, Jun 26, 2007 at 08:58:49PM -0800, Ted Lemon wrote:
> anticipated.   So this interpretation runs the risk of a repeat of =20
> the "popular server deemed standard" problem we had with DHCPv4, =20
> where DHCP client implementations were generally tested against a =20
> single server which didn't follow the standard very well, and when =20
> that worked the authors assumed that the clients were correct.   =20
> Interoperability problems resulting from this still crop up from time =20
> to time.

Just to clarify; have we had historic interop problems where the
DHCPv4 PRL was omitted entirely?

I am aware of multiple problems where a DHCPv4 client provides a PRL
with options omitted (subnet-mask, 252, ...).

Examining the problems we've had is very instructional, so I'm
curious if there have been other failure modes.

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

--5QAgd0e35j3NYeGe
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFGgqS9cXeLeWu2vmoRAijyAJ9TuKdyi3VmcchYFyZ7rm+deMoulgCeLA7f
xGWuQDPgLH/OYsH9Cw63HSg=
=swod
-----END PGP SIGNATURE-----

--5QAgd0e35j3NYeGe--


--===============0507847940==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0507847940==--




From dhcwg-bounces@ietf.org Wed Jun 27 14:30:52 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3cI0-0005vN-6y; Wed, 27 Jun 2007 14:30:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3cHz-0005vC-7B
	for dhcwg@ietf.org; Wed, 27 Jun 2007 14:30:51 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3cHF-0004xg-Gl
	for dhcwg@ietf.org; Wed, 27 Jun 2007 14:30:51 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id EE0BD5A6E5; Wed, 27 Jun 2007 11:30:04 -0700 (PDT)
Date: Wed, 27 Jun 2007 11:30:04 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: DHC WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] DHCPv6 ORO - mandatory?
Message-ID: <20070627183004.GD10297@isc.org>
References: <8E296595B6471A4689555D5D725EBB2104618EE1@xmb-rtp-20a.amer.cisco.com>
	<0260031F55435342859BFB2CCA6773D81B898B98@EXCHANGE03.jp.ykgw.net>
Mime-Version: 1.0
In-Reply-To: <0260031F55435342859BFB2CCA6773D81B898B98@EXCHANGE03.jp.ykgw.net>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0958083160=="
Errors-To: dhcwg-bounces@ietf.org


--===============0958083160==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="4zI0WCX1RcnW9Hbu"
Content-Disposition: inline


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

On Wed, Jun 27, 2007 at 04:32:19PM +0900, Hideshi.Enokihara@jp.yokogawa.com=
 wrote:
> 17.1.1. Creation of Solicit Messages
> (snip)
>    The client SHOULD include an Option Request option (see section 22.7)
>    to indicate the options the client is interested in receiving.  The
>    client MAY additionally include instances of those options that are
>    identified in the Option Request option, with data values as hints to
>    the server about parameter values the client would like to have
>    returned.
> (snip)
>=20
> This "SHOULD" also change to "MAY" or somthing?

I think 'MAY' regardless of which direction the other section goes.

The only reason the client includes an ORO in the Solicit is so that
it can observe the options in the Advertise to select a server (to
choose a server which gives options it likes better).

If a client isn't using offered options or their contents in server
selection, then there's no real reason to provide an ORO.  Conversely,
if it is, then it MUST if it expects to get what it wants.

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

--4zI0WCX1RcnW9Hbu
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFGgqyscXeLeWu2vmoRAiblAKCpj7CZiZAQ6Oxkq0TdFE3rH1GNEwCgtCUf
vEBcxx1+dutgdENxubcmZ/E=
=u+IQ
-----END PGP SIGNATURE-----

--4zI0WCX1RcnW9Hbu--


--===============0958083160==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0958083160==--




From dhcwg-bounces@ietf.org Wed Jun 27 17:10:57 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3emu-0003D0-9O; Wed, 27 Jun 2007 17:10:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3ems-00038e-GB
	for dhcwg@ietf.org; Wed, 27 Jun 2007 17:10:55 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3emX-0004Ab-Jo
	for dhcwg@ietf.org; Wed, 27 Jun 2007 17:10:54 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 27 Jun 2007 17:10:33 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CANdugkZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,467,1175486400"; 
	d="scan'208"; a="63843024:sNHT40772084"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5RLAXMv009581; 
	Wed, 27 Jun 2007 17:10:33 -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.12.10/8.12.6) with ESMTP id l5RLAGLr022080; 
	Wed, 27 Jun 2007 21:10:33 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.1830); 
	Wed, 27 Jun 2007 17:10:20 -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
Subject: RE: [dhcwg] DHCPv6 ORO - mandatory?
Date: Wed, 27 Jun 2007 17:10:15 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB210461934A@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <00C1A66B-B31A-4966-801C-C7590A38D9A3@nominum.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] DHCPv6 ORO - mandatory?
Thread-Index: Ace4d/k7RwV1BCiKQmGuW8NVyETmYAAh0SYQ
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "Ted Lemon" <Ted.Lemon@nominum.com>,
	"John Jason Brzozowski" <john_brzozowski@cable.comcast.com>
X-OriginalArrivalTime: 27 Jun 2007 21:10:20.0421 (UTC)
	FILETIME=[91B70350:01C7B8FF]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2108; t=1182978633;
	x=1183842633; c=relaxed/simple; s=rtpdkim1001;
	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]=20DHCPv6=20ORO=20-=20mandatory?
	|Sender:=20 |To:=20=22Ted=20Lemon=22=20<Ted.Lemon@nominum.com>,
	=0A=20=20=20=20=20=20=
	20=20=22John=20Jason=20Brzozowski=22=20<john_brzozowski@cable.comcast.com>;
	bh=GcirP3tzMliF4WsofcyXo/qba3e0sEaN8RiBR+pzaRk=;
	b=L2NSef2FxFRZLfZ+i3no3jPfa6haZWQ6WLxkuHascgPtiDtqrSh7wZ6UPePPyUID9/VDv1DC
	i0TsUBeP3/uoEuwYNdqfUJ3KE2uqQuz1hahsb50ACwvLvoxBEuTAOTix;
Authentication-Results: rtp-dkim-1; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Ted:

I disagree. If a client *just* wants addresses, why should it include an
ORO?

What needs to be clear is if no ORO is provided, no options (other than
those related to the core protocol which are NOT typically in the ORO)
will be returned by the server.

I think, though perhaps you don't, that the ORO SHOULD NOT include IA_NA
(and IAADDR), Server Identifier, Client Identifier option numbers
because these not OPTIONAL for the server to return.

- Bernie=20

-----Original Message-----
From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
Sent: Wednesday, June 27, 2007 12:59 AM
To: John Jason Brzozowski
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] DHCPv6 ORO - mandatory?

On Jun 26, 2007, at 5:41 PM, John Jason Brzozowski wrote:
> I think this is an extension of the exchange Ted and I had on the ISC
> mailing list.  IMHO always requiring an ORO seems wrong, so perhaps =20
> this was
> an editing error.

As I stated during that conversation, I actually think making the ORO =20
optional is just begging for interoperability problems.   The =20
server's behavior in the case where no ORO is provided is undefined; =20
that means that it's probably not what the client author would have =20
anticipated.   So this interpretation runs the risk of a repeat of =20
the "popular server deemed standard" problem we had with DHCPv4, =20
where DHCP client implementations were generally tested against a =20
single server which didn't follow the standard very well, and when =20
that worked the authors assumed that the clients were correct.   =20
Interoperability problems resulting from this still crop up from time =20
to time.

So I would argue that if we do a correction to RFC3315, the ORO =20
should be made mandatory, not optional.   I don't think servers can =20
savely drop packets with no ORO, but it's unrealistic to expect =20
correct behavior if you don't send an ORO, whether the standard =20
requires it or not.



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

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



From dhcwg-bounces@ietf.org Wed Jun 27 17:56:11 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3fUZ-0005q4-JF; Wed, 27 Jun 2007 17:56:03 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3fUY-0005bW-5B
	for dhcwg@ietf.org; Wed, 27 Jun 2007 17:56:02 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3fUX-0005ww-PE
	for dhcwg@ietf.org; Wed, 27 Jun 2007 17:56:02 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 27 Jun 2007 17:56:01 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAIR5gkZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,468,1175486400"; 
	d="scan'208"; a="63847172:sNHT49119844"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5RLu1cQ028893; 
	Wed, 27 Jun 2007 17:56:01 -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.12.10/8.12.6) with ESMTP id l5RLtaLv003657; 
	Wed, 27 Jun 2007 21:55:56 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.1830); 
	Wed, 27 Jun 2007 17:55:54 -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
Subject: RE: [dhcwg] DHCPv6 ORO - mandatory?
Date: Wed, 27 Jun 2007 17:55:58 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB210461937D@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <0260031F55435342859BFB2CCA6773D81B898B99@EXCHANGE03.jp.ykgw.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] DHCPv6 ORO - mandatory?
Thread-Index: Ace4eA4fnYsNv9a7RAuQaE8ai2BqDwAFU6vAABya1DA=
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: <Hideshi.Enokihara@jp.yokogawa.com>, <Ted.Lemon@nominum.com>,
	<john_brzozowski@cable.comcast.com>
X-OriginalArrivalTime: 27 Jun 2007 21:55:54.0789 (UTC)
	FILETIME=[EF867550:01C7B905]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4759; t=1182981361;
	x=1183845361; c=relaxed/simple; s=rtpdkim1001;
	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]=20DHCPv6=20ORO=20-=20mandatory?
	|Sender:=20
	|To:=20<Hideshi.Enokihara@jp.yokogawa.com>, =20<Ted.Lemon@nominum.com>,
	=0A
	=20=20=20=20=20=20=20=20<john_brzozowski@cable.comcast.com>;
	bh=NonokmHNwehEMOnV6lWC+/bxc7zZQ4A8NFKi9hNQ5RQ=;
	b=V8FT0jmyQqD88o9VAF8Ug6p+CVWU+KDVMZsY0mtmZIvO042460As9clNSn3N228G7k/f4Iwy
	MDrjwbXx6mfLtIlmqAut0eMBaYZbOZ4nCplmzquRg+pdOTxHK2U7yjTG;
Authentication-Results: rtp-dkim-1; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

I'd like to see text (perhaps it is already in RFC 3315) that clarifies
that a client *MUST* include the ORO if it expects a particular option
(other than the "core" protocol options) to be returned in an Advertise
or Reply. If a client does not include the option in the ORO, then the
server SHOULD NOT send it to the client. SHOULD NOT is correct here,
because server policy might dictate otherwise. Note also that this does
not guarantee that the server will provide each of these options (the
server may have not been configured with appropriate information) nor
does it mean that the client will only get the options it requested.

This is the problem we've had with DHCPv4 - often clients expect options
to be returned that they haven't explicitly requested in their PRL
(though I think that generally hasn't been a big issue with clients
lately).

- Bernie=20

-----Original Message-----
From: Hideshi.Enokihara@jp.yokogawa.com
[mailto:Hideshi.Enokihara@jp.yokogawa.com]=20
Sent: Wednesday, June 27, 2007 3:39 AM
To: Ted.Lemon@nominum.com; john_brzozowski@cable.comcast.com
Cc: dhcwg@ietf.org
Subject: RE: [dhcwg] DHCPv6 ORO - mandatory?

=20
> optional is just begging for interoperability problems.   The =20
> server's behavior in the case where no ORO is provided is=20
> undefined;=20
How about following sections?

17.2.2. Creation and Transmission of Advertise Messages
(snip)
   The server includes options the server will return to the client in a
   subsequent Reply message.  The information in these options may be
   used by the client in the selection of a server if the client
   receives more than one Advertise message.  If the client has included
   an Option Request option in the Solicit message, the server includes
   options in the Advertise message containing configuration parameters
   for all of the options identified in the Option Request option that
   the server has been configured to return to the client.  The server
   MAY return additional options to the client if it has been configured
   to do so.  The server must be aware of the recommendations on packet
   sizes and the use of fragmentation in section 5 of RFC 2460.

18.2. Server Behavior
(snip)

   In most Reply messages, the server includes options containing
   configuration information for the client.  The server must be aware
   of the recommendations on packet sizes and the use of fragmentation
   in section 5 of RFC 2460.  If the client included an Option Request
   option in its message, the server includes options in the Reply
   message containing configuration parameters for all of the options
   identified in the Option Request option that the server has been
   configured to return to the client.  The server MAY return additional
   options to the client if it has been configured to do so.

Regards,
Hideshi
> -----Original Message-----
> From: Ted Lemon [mailto:Ted.Lemon@nominum.com]=20
> Sent: Wednesday, June 27, 2007 1:59 PM
> To: John Jason Brzozowski
> Cc: dhcwg@ietf.org
> Subject: Re: [dhcwg] DHCPv6 ORO - mandatory?
>=20
> On Jun 26, 2007, at 5:41 PM, John Jason Brzozowski wrote:
> > I think this is an extension of the exchange Ted and I had=20
> on the ISC=20
> > mailing list.  IMHO always requiring an ORO seems wrong, so perhaps=20
> > this was an editing error.
>=20
> As I stated during that conversation, I actually think making=20
> the ORO =20
> optional is just begging for interoperability problems.   The =20
> server's behavior in the case where no ORO is provided is=20
> undefined; that means that it's probably not what the client=20
> author would have =20
> anticipated.   So this interpretation runs the risk of a repeat of =20
> the "popular server deemed standard" problem we had with=20
> DHCPv4, where DHCP client implementations were generally=20
> tested against a single server which didn't follow the=20
> standard very well, and when =20
> that worked the authors assumed that the clients were correct.   =20
> Interoperability problems resulting from this still crop up=20
> from time to time.
>=20
> So I would argue that if we do a correction to RFC3315, the ORO =20
> should be made mandatory, not optional.   I don't think servers can =20
> savely drop packets with no ORO, but it's unrealistic to=20
> expect correct behavior if you don't send an ORO, whether the=20
> standard requires it or not.
>=20
>=20
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg
>=20

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

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



From dhcwg-bounces@ietf.org Wed Jun 27 19:17:37 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3glR-0005QE-Ec; Wed, 27 Jun 2007 19:17:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3glQ-0005Nb-CK
	for dhcwg@ietf.org; Wed, 27 Jun 2007 19:17:32 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3gkr-0008NT-6V
	for dhcwg@ietf.org; Wed, 27 Jun 2007 19:17:32 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 7655E5A6E5; Wed, 27 Jun 2007 16:16:48 -0700 (PDT)
Date: Wed, 27 Jun 2007 16:16:48 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: DHC WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] DHCPv6 ORO - mandatory?
Message-ID: <20070627231648.GJ10297@isc.org>
References: <0260031F55435342859BFB2CCA6773D81B898B99@EXCHANGE03.jp.ykgw.net>
	<8E296595B6471A4689555D5D725EBB210461937D@xmb-rtp-20a.amer.cisco.com>
Mime-Version: 1.0
In-Reply-To: <8E296595B6471A4689555D5D725EBB210461937D@xmb-rtp-20a.amer.cisco.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0109577627=="
Errors-To: dhcwg-bounces@ietf.org


--===============0109577627==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="3U8TY7m7wOx7RL1F"
Content-Disposition: inline


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

On Wed, Jun 27, 2007 at 05:55:58PM -0400, Bernie Volz (volz) wrote:
> or Reply. If a client does not include the option in the ORO, then the
> server SHOULD NOT send it to the client. SHOULD NOT is correct here,

We would have to capture that entire discussion in an RFC.  Just
saying the server SHOULD NOT is not enough, because some implementors
will just write to that spec - if they're like me and have a common
library for DHCPv4 and DHCPv6, then it's actually a lot of work to
special-case DHCPv6 behaviour so that a PRL is not manufactured from
option space contents.

So I worry we'll get implementations that send all configured options
and cite SHOULD NOT as conforming.  Then we'll get clients that rely
on that behaviour.


I'm a big fan of requiring clients (even only new clients) to send a
zero length ORO.  That's clear.  That's hard to misinterpret.  It's
even intuitive.  You have to have tried to get the logical result, so
it shouldn't be a surprise.

An absent ORO is intuitively unclear, and it's a big job to provide
that clarity.

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

--3U8TY7m7wOx7RL1F
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFGgu/gcXeLeWu2vmoRAsECAJ4uzjQOQ/pbgE6frKMaTvQZpmZG2gCeMyWN
Oe8QniBYaoQFK8Ohxmbzslk=
=NWwr
-----END PGP SIGNATURE-----

--3U8TY7m7wOx7RL1F--


--===============0109577627==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0109577627==--




From dhcwg-bounces@ietf.org Thu Jun 28 06:17:14 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3r3k-0007Nt-0h; Thu, 28 Jun 2007 06:17:08 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3r3g-0007Ia-PN; Thu, 28 Jun 2007 06:17:04 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I3r3g-0008Sy-H1; Thu, 28 Jun 2007 06:17:04 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 28 Jun 2007 03:16:55 -0700
X-IronPort-AV: i="4.16,469,1175497200"; 
	d="scan'208"; a="173624676:sNHT43120341"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l5SAGtIR020896; 
	Thu, 28 Jun 2007 03:16:55 -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.12.10/8.12.6) with ESMTP id l5SAGtXH013062;
	Thu, 28 Jun 2007 10:16:55 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 28 Jun 2007 06:16:54 -0400
Received: from 10.86.242.209 ([10.86.242.209]) by xmb-rtp-211.amer.cisco.com
	([64.102.31.118]) via Exchange Front-End Server email.cisco.com
	([64.102.31.38]) with Microsoft Exchange Server HTTP-DAV ; 
	Thu, 28 Jun 2007 10:16:54 +0000
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Thu, 28 Jun 2007 06:17:40 -0400
From: Ralph Droms <rdroms@cisco.com>
To: <mip4@ietf.org>, DHC WG <dhcwg@ietf.org>
Message-ID: <C2A90304.482C8%rdroms@cisco.com>
Thread-Topic: EXTENDED: mip4 and dhc WG joint last call on
	draft-ietf-mip4-gen-ext-03.txt
Thread-Index: Ace5bY6yzSyTZiVgEdyNKgARJOT6eg==
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 28 Jun 2007 10:16:54.0751 (UTC)
	FILETIME=[73BA46F0:01C7B96D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1395; t=1183025815;
	x=1183889815; c=relaxed/simple; s=sjdkim3002;
	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:=20EXTENDED=3A=20mip4=20and=20dhc=20WG=20joint=20last=20call=20o
	n=0A=20draft-ietf-mip4-gen-ext-03.txt |Sender:=20;
	bh=EEu3M1J35iNfLCr5x3/1foNanm6EhwtgairKlrzoNf0=;
	b=rmdWL5xc5kob3U34BwCFWSSL/YHcn2eEiqJ1zgnKI7PSK+FnahVXJMgczgPCwU6JcySfz8pS
	feMXfOGXHTfK4Fnb0drBY3dEFn1J7tJS/4iJGtn+8SM3MeEJIQOT8zkW;
Authentication-Results: sj-dkim-3; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: 
Subject: [dhcwg] EXTENDED: mip4 and dhc WG joint last call on
 draft-ietf-mip4-gen-ext-03.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

There has been no response to this WG last call, so the deadline will be
extended to 1700EDT, 07/05/07.

=====
This message announces a joint WG last call for the mip4 and dhc WGs
on "Mobile IPv4 Extension for Configuration Options Exchange"
<draft-ietf-mip4-gen-ext-03.txt>.  The last call will conclude at
1700EDT, Monday, 06/25/07.

The dhc WG is asked to review the use of DHCP options in this draft to
pass configuration information to a mobile node.

Please respond to this joint WG last call.  Responses may be sent to
either mip4@ietf.org or dhcwg@ietf.org.  If you support acceptance of
the document without change, respond with a simple acknowledgment, so
that support for the document can be assessed.  Lack of discussion
does not represent positive support.  If there is no expression of
support for acceptance during the WG last call, the document will not
be advanced to the IESG.

draft-ietf-mip4-gen-ext-03.txt describes the mechanism for providing
the host configuration information during Mobile IP registration.  One
or more Configuration Options Exchange Extensions may be included in
the registration message to provide the Mobile Node the configuration
parameters needed for network service (e.g.  DNS).  This draft is
available as
http://www.ietf.org/internet-drafts/draft-ietf-mip4-gen-ext-03.txt

- Stig Venaas, Ralph Droms
  dhc WG chairs


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



From dhcwg-bounces@ietf.org Thu Jun 28 11:48:50 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3wEg-0006GR-4F; Thu, 28 Jun 2007 11:48:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3wEe-0006GE-If
	for dhcwg@ietf.org; Thu, 28 Jun 2007 11:48:44 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3wEC-00013c-7x
	for dhcwg@ietf.org; Thu, 28 Jun 2007 11:48:44 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id AFA5F5A6E5; Thu, 28 Jun 2007 08:48:15 -0700 (PDT)
Date: Thu, 28 Jun 2007 08:48:15 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: DHC WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] EXTENDED: mip4 and dhc WG joint last call on
	draft-ietf-mip4-gen-ext-03.txt
Message-ID: <20070628154815.GB4877@isc.org>
References: <C2A90304.482C8%rdroms@cisco.com>
Mime-Version: 1.0
In-Reply-To: <C2A90304.482C8%rdroms@cisco.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -2.8 (--)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0723835752=="
Errors-To: dhcwg-bounces@ietf.org


--===============0723835752==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="V0207lvV8h4k8FAm"
Content-Disposition: inline


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

On Thu, Jun 28, 2007 at 06:17:40AM -0400, Ralph Droms wrote:
> http://www.ietf.org/internet-drafts/draft-ietf-mip4-gen-ext-03.txt

   This document defines a new extension that can be used to carry
   configuration parameters from the Foreign Agent and/or Home Agent
   during Mobile IPv4 registration.  This configuration parameters
   include DHCP option (Parameter Request List) defined in [RFC2132].

The last sentence reads funny.  May I suggest;

   The extension supports the use of multiple configuration parameter
   formats, and this document defines one such format: the use of
   standard DHCP Options [RFC2132].


This bit;

   The Mobile Node may request values for specific configuration
   parameters from the Home Agent and/or Foreign Agent by including the
   'Parameter Request List' option (defined in [RFC2132]) in the
   Registration Request.  The list of requested parameters is specified
   as a string of octets, where each octet is a valid DHCP option code
   as defined in [RFC2132].  If this extension is included in the

Suggests that you can only draw from RFC2132 for DHCP options within
this space.  It also tersely (re)defines the Parameter Request List's
format...a pet peeve of mine.  Reminding the use is probably useful,
but for the 'string of octets' that should really refer to 2132 (and
its updates).

Also, s/may/MAY/?

   The Mobile Node MAY request values for specific configuration
   parameters from the Home Agent and/or Foreign Agent by including the
   Parameter Request List Option [RFC2132] in the Registration Request.
   If the Mobile Node does include a Parameter Request List, it MUST
   list the DHCP Option Code of each option it desires configuration
   parameters for.  The Home Agent will only include parameters that
   appear on the Parameter Request List.

But I'm not a MIP guy so maybe that should be Foreign Agent?


The ascii art in Figure 3 appears to be wrong.  Or I can't figure
it out.  Why are the subsequent ascii art figures using different
terminology ("Ent" and "DHCP" or "Ent" and "Rsv") than the first
figure, which defines the fields as "Entity-Type" and "Sub-Type"?

It took me quite awhile to realize what I was looking at - I thought
these were all different protocols or different messages!


I think this draft is very nearly ready for the IESG, but I think
at least the ascii art bits need to be smoothed out.  The wording
bits I've suggested are pretty minor.

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

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

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

iD8DBQFGg9g/cXeLeWu2vmoRAiONAJ469owAznlig6fCUalur1/yP06GPwCeKhgs
edzYHkI36W7FxgrRTmaisOk=
=JILg
-----END PGP SIGNATURE-----

--V0207lvV8h4k8FAm--


--===============0723835752==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============0723835752==--




From dhcwg-bounces@ietf.org Thu Jun 28 15:06:33 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3zK3-0000Ot-SO; Thu, 28 Jun 2007 15:06:31 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3zK2-0000Ny-TJ
	for dhcwg@ietf.org; Thu, 28 Jun 2007 15:06:30 -0400
Received: from terminus.zytor.com ([192.83.249.54])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3zK2-0007yv-II
	for dhcwg@ietf.org; Thu, 28 Jun 2007 15:06:30 -0400
Received: from titan.hos.anvin.org ([205.233.54.227]) (authenticated bits=0)
	by terminus.zytor.com (8.13.8/8.13.8) with ESMTP id l5SJ1q2Y000951
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 28 Jun 2007 12:01:55 -0700
Message-ID: <4684059E.8050806@zytor.com>
Date: Thu, 28 Jun 2007 15:01:50 -0400
From: "H. Peter Anvin" <hpa@zytor.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070615)
MIME-Version: 1.0
To: Stig Venaas <stig.venaas@uninett.no>
Subject: Re: [dhcwg] dhc wg last call on  draft-ietf-dhc-pxelinux-01
References: <46823079.5050405@uninett.no>
In-Reply-To: <46823079.5050405@uninett.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.88.7/3545/Wed Jun 27 20:08:05 2007 on
	terminus.zytor.com
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: dhcwg <dhcwg@ietf.org>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Stig Venaas wrote:
> This message announces a dhc wg last call on "PXELINUX Use of 'Site
> Local' Option Space" <draft-ietf-dhc-pxelinux-01.txt>.  The last call
> will conclude at 1700EDT on Mon, 2007-07-09.
> 
> Please respond to this WG last call.  If you support acceptance of the
> document without change, respond with a simple acknowledgment, so that
> support for the document can be assessed.  Lack of discussion does not
> represent positive support.  If there is no expression of support for
> acceptance during the WG last call, the document will not be advanced
> to the IESG.
> 
> draft-ietf-dhc-pxelinux-01 is in response to the process of
> reclassifying site-specific options, RFC 3942, and describes the use
> by PXELINUX of some DHCP Option Codes numbering from 208-211.  These
> codes were designated 'Site Local' prior to this action, and are
> redefined by RFC 3942 as available for allocation as standard DHCP
> Options.

As the developer of PXELINUX, I support this document, and greatly 
appreciate David's efforts in preparing it.

	-hpa


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



From dhcwg-bounces@ietf.org Fri Jun 29 00:26:32 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I483y-000674-NX; Fri, 29 Jun 2007 00:26:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I483x-00062p-Lj
	for dhcwg@ietf.org; Fri, 29 Jun 2007 00:26:29 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I483w-0002pa-TP
	for dhcwg@ietf.org; Fri, 29 Jun 2007 00:26:29 -0400
Received: from ep_ms5_bk (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0JKD00HY7QZ66F@mailout3.samsung.com> for dhcwg@ietf.org;
	Fri, 29 Jun 2007 13:25:54 +0900 (KST)
Received: from ep_spt02 (ms5.samsung.com [203.254.225.113])
	by ms5.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004))
	with ESMTP id <0JKD00MKVQZ5WE@ms5.samsung.com> for dhcwg@ietf.org; Fri,
	29 Jun 2007 13:25:54 +0900 (KST)
Content-return: prohibited
Date: Fri, 29 Jun 2007 04:25:53 +0000 (GMT)
From: Heejin Jang <heejin.jang@samsung.com>
Subject: Re: Re: [dhcwg] EXTENDED: Joint mip6 and dhc WG last call on
	draft-ietf-mip6-bootstrapping-integrated and draft-ietf-mip6-hiopt
To: "David W. Hankins" <David_Hankins@isc.org>
Message-id: <0JKD00MKWQZ5WE@ms5.samsung.com>
MIME-version: 1.0
MIME-version: 1.0
X-Priority: 3
Msgkey: 20070629042553869@heejin.jang
X-MTR: 20070629042553869@heejin.jang
X-EPLocale: ko_KR.windows-1252
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
X-EPApproval-Locale: 
X-Generator: NamoMIME 6.0.0.8
X-Spam-Score: 3.4 (+++)
X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d
Cc: DHC WG <dhcwg@ietf.org>, jinchoe@samsung.com/
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: heejin.jang@samsung.com
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1261040748=="
Errors-To: dhcwg-bounces@ietf.org

--===============1261040748==
Content-return: prohibited
Content-type: text/html; charset=windows-1252
Content-transfer-encoding: base64

PEhUTUw+PEhFQUQ+CjxNRVRBIGh0dHAtZXF1aXY9Q29udGVudC1UeXBlIGNvbnRlbnQ9J3RleHQv
aHRtbDsgY2hhcnNldD13aW5kb3dzLTEyNTInPgo8dGl0bGU+U2Ftc3VuZyBFbnRlcnByaXNlIFBv
cnRhbCBteVNpbmdsZTwvdGl0bGU+CjxzdHlsZT4gUCwgdGQsIGxpIHtmb250LWZhbWlseTpBcmlh
bCwgYXJpYWw7IGZvbnQtc2l6ZTo5cHQ7IG1hcmdpbi10b3A6NXB4O21hcmdpbi1ib3R0b206NXB4
O30gYm9keXtmb250LWZhbWlseTpBcmlhbCwgYXJpYWw7IGZvbnQtc2l6ZTo5cHQ7fTwvc3R5bGU+
CjwvSEVBRD48Qk9EWT5IaSwgRGF2aWQuDQo8cD4mbmJzcDs8L3A+DQo8cD5HbGFkIHRvIGhlYXIg
dGhlIHVzZWZ1bCBjb21tZW50cyBmcm9tIGRoY3dnLjwvcD4NCjxwPlRoYW5rcyBmb3IgeW91ciBm
ZWVkYmFjayBhbmQgc2VlIHRoZSBpbmxpbmUgYmVsb3cgcmVnYXJkaW5nIGhpb3B0IGRyYWZ0LiA8
L3A+DQo8cD4mbmJzcDs8L3A+DQo8cD4tIFJlZ2FyZHMsIDwvcD4NCjxwPkhlZWppbjwvcD4NCjxw
PiZuYnNwOy0tLS0tLS0tIDxiPk9yaWdpbmFsIE1lc3NhZ2U8L2I+IC0tLS0tLS08YnI+PGI+U2Vu
ZGVyPC9iPiA6IERhdmlkIFcuIEhhbmtpbnMmbHQ7RGF2aWRfSGFua2luc0Bpc2Mub3JnJmd0Ozxi
cj48Yj5EYXRlPC9iPiAgIDogMjAwNy0wNi0yNiAwMzo0Nzxicj48Yj5UaXRsZTwvYj4gIDogUmU6
IFtkaGN3Z10gRVhURU5ERUQ6IEpvaW50IG1pcDYgYW5kIGRoYyBXRyBsYXN0IGNhbGwgb24NCglk
cmFmdC1pZXRmLW1pcDYtYm9vdHN0cmFwcGluZy1pbnRlZ3JhdGVkIGFuZCBkcmFmdC1pZXRmLW1p
cDYtaGlvcHQ8YnI+PGJyPk9uJm5ic3A7TW9uLCZuYnNwO0p1biZuYnNwOzI1LCZuYnNwOzIwMDcm
bmJzcDthdCZuYnNwOzEwOjQzOjEyQU0mbmJzcDstMDQwMCwmbmJzcDtSYWxwaCZuYnNwO0Ryb21z
Jm5ic3A7d3JvdGU6DQo8YnI+Jmd0OyZuYnNwO1RoZXJlJm5ic3A7aGFzJm5ic3A7YmVlbiZuYnNw
O25vJm5ic3A7cmVzcG9uc2UmbmJzcDt0byZuYnNwO3RoaXMmbmJzcDtXRyZuYnNwO2xhc3QmbmJz
cDtjYWxsLCZuYnNwO3NvJm5ic3A7dGhlJm5ic3A7ZGVhZGxpbmUmbmJzcDt3aWxsJm5ic3A7YmUN
Cjxicj4mZ3Q7Jm5ic3A7ZXh0ZW5kZWQmbmJzcDt0byZuYnNwOzE3MDBFRFQsJm5ic3A7MDcvMDIv
MDcuDQo8YnI+DQo8YnI+TXkmbmJzcDtleGN1c2UmbmJzcDtpcyZuYnNwO3RoYXQmbmJzcDtJJm5i
c3A7d2FzJm5ic3A7aW4mbmJzcDtBbGFza2EuDQo8YnI+DQo8YnI+Jmd0OyZuYnNwO2h0dHA6Ly93
d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWlldGYtbWlwNi1ib290c3RyYXBwaW5n
LWludGVncmF0ZWQNCjxicj4mZ3Q7Jm5ic3A7LTA0LnR4dA0KPGJyPg0KPGJyPkNvcnJlY3Rpb24m
bmJzcDsoSSZuYnNwO3RoaW5rPyk6DQo8YnI+DQo8YnI+Jm5ic3A7Jm5ic3A7aHR0cDovL3d3dy5p
ZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtaWV0Zi1taXA2LWJvb3RzdHJhcHBpbmctaW50
ZWdyYXRlZC1kaGMtMDQudHh0DQo8YnI+DQo8YnI+SSZuYnNwO2FjdHVhbGx5Jm5ic3A7ZG9uJiMz
OTt0Jm5ic3A7c2VlJm5ic3A7YSZuYnNwO2xvdCZuYnNwO2luJm5ic3A7dGhlcmUmbmJzcDtmb3Im
bmJzcDtESENXRyZuYnNwO3RvJm5ic3A7cmV2aWV3LiZuYnNwOyZuYnNwO01heWJlJm5ic3A7SSYj
Mzk7bQ0KPGJyPm5vdCZuYnNwO2xvb2tpbmcmbmJzcDtoYXJkJm5ic3A7ZW5vdWdoPw0KPGJyPg0K
PGJyPkkmbmJzcDthbSZuYnNwO2EmbmJzcDtsaXR0bGUmbmJzcDtjb25jZXJuZWQmbmJzcDsoYnV0
Jm5ic3A7b25seSZuYnNwO2EmbmJzcDtsaXR0bGUpJm5ic3A7YXQmbmJzcDt0aGUmbmJzcDtleHRl
bnQmbmJzcDt0byZuYnNwO3doaWNoDQo8YnI+aXQmbmJzcDtkZWZpbmVzJm5ic3A7c2ltcGxpZmll
ZCZuYnNwO1JGQzMzMTUmbmJzcDtiZWhhdmlvdXImbmJzcDsoJnF1b3Q7c3VtbWFyaXppbmcmcXVv
dDsmbmJzcDt0aGUmbmJzcDtwcm9jZXNzDQo8YnI+aW4mbmJzcDt3aGljaCZuYnNwO2EmbmJzcDtj
bGllbnQmbmJzcDtpcyZuYnNwO2lkZW50aWZpZWQmbmJzcDthbmQmbmJzcDtjb25maWd1cmVkKS4N
Cjxicj4NCjxicj4NCjxicj4mbmJzcDsmbmJzcDsmbmJzcDsoMykmbmJzcDtUaGUmbmJzcDtSZWxh
eSZuYnNwO0FnZW50Jm5ic3A7aW50ZXJjZXB0cyZuYnNwO3RoZSZuYnNwO0luZm9ybWF0aW9uJm5i
c3A7UmVxdWVzdCZuYnNwO2Zyb20mbmJzcDt0aGUNCjxicj4NCjxicj5JJm5ic3A7dGhpbmsmbmJz
cDsmcXVvdDtyZWNlaXZlcyZxdW90OyZuYnNwO2lzJm5ic3A7YSZuYnNwO2JldHRlciZuYnNwO3dv
cmQsJm5ic3A7Y29uc2lkZXJpbmcmbmJzcDt0aGF0Jm5ic3A7dGhlJm5ic3A7cGFja2V0Jm5ic3A7
aXMNCjxicj50cmFuc21pdHRlZCZuYnNwO3RvJm5ic3A7YSZuYnNwO211bHRpY2FzdCZuYnNwO2Fk
ZHJlc3MuJm5ic3A7Jm5ic3A7JnF1b3Q7aW50ZXJjZXB0JnF1b3Q7Jm5ic3A7aGFzJm5ic3A7bW9y
ZSZuYnNwO29mJm5ic3A7YW4NCjxicj5pbnNpbnVhdGlvbiZuYnNwO3RoYXQmbmJzcDt0aGUmbmJz
cDtyZWxheSZuYnNwO3dvdWxkJm5ic3A7bm90Jm5ic3A7bm9ybWFsbHkmbmJzcDtyZWNlaXZlJm5i
c3A7dGhlJm5ic3A7cGFja2V0Lg0KPGJyPg0KPGJyPg0KPGJyPlNvJm5ic3A7SSZuYnNwO3NlZSZu
YnNwO25vJm5ic3A7cHJvYmxlbSZuYnNwO2FkdmFuY2luZyZuYnNwO3RoaXMmbmJzcDtkcmFmdCZu
YnNwO3RvJm5ic3A7dGhlJm5ic3A7SUVTRy4NCjxicj4NCjxicj4NCjxicj4mZ3Q7Jm5ic3A7YW5k
Jm5ic3A7aHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtaWV0Zi1taXA2
LWhpb3B0LTA1LnR4dA0KPGJyPg0KPGJyPklTQyZuYnNwO0RIQ1AmbmJzcDthbmQmbmJzcDtvdGhl
cnMmbmJzcDtzaGFyZSZuYnNwO29wdGlvbiZuYnNwO3Byb2Nlc3NpbmcmbmJzcDtjb2RlJm5ic3A7
YmV0d2VlbiZuYnNwO3RoZSZuYnNwO3Y0DQo8YnI+YW5kJm5ic3A7djYmbmJzcDtzaWRlJm5ic3A7
b2YmbmJzcDt0aGUmbmJzcDtob3VzZS4mbmJzcDsmbmJzcDtJJm5ic3A7ZG9uJiMzOTt0Jm5ic3A7
a25vdyZuYnNwO2Fib3V0Jm5ic3A7dGhlJm5ic3A7b3RoZXJzLCZuYnNwO2J1dCZuYnNwO3RoZQ0K
PGJyPm5ldCZuYnNwO2VmZmVjdCZuYnNwO2ZvciZuYnNwO0lTQyZuYnNwO0RIQ1AmbmJzcDtpcyZu
YnNwO3RoYXQmbmJzcDtjb2RlJm5ic3A7MCZuYnNwO2lzJm5ic3A7dHJlYXRlZCZuYnNwO2FzJm5i
c3A7YW4mbmJzcDsmcXVvdDtlbmQmbmJzcDt0YWcmcXVvdDsNCjxicj4oY29kZSZuYnNwOzI1NSwm
bmJzcDtvciZuYnNwOyZxdW90O2NvZGUmbmJzcDthbGwmbmJzcDtvbmVzJnF1b3Q7Jm5ic3A7Zm9y
Jm5ic3A7YW55Jm5ic3A7Y29kZSZuYnNwO3dpZHRoLCZuYnNwO2lzJm5ic3A7bm90KS4mbmJzcDsm
bmJzcDtUaGlzDQo8YnI+c291bmRzJm5ic3A7YSZuYnNwO2xpdHRsZSZuYnNwO3dlaXJkLCZuYnNw
O2J1dCZuYnNwO3RoYXQmIzM5O3MmbmJzcDt0aGUmbmJzcDtjb250cml2YW5jZSZuYnNwO29mJm5i
c3A7dGhlJm5ic3A7bG9vcCZuYnNwO3dlDQo8YnI+c2VsZWN0ZWQuDQo8YnI+DQo8YnI+SWYmbmJz
cDt0aGUmbmJzcDtzdWItb3B0aW9ucyZuYnNwO2NvdWxkJm5ic3A7YmUmbmJzcDtudW1iZXJlZCZu
YnNwO2Zyb20mbmJzcDsxLCZuYnNwO3RoZW4mbmJzcDt0aGlzJm5ic3A7ZHJhZnQmbmJzcDt3b3Vs
ZA0KPGJyPmJlJm5ic3A7Y29tcGF0aWJsZSZuYnNwO3dpdGgmbmJzcDtvdXImbmJzcDtjdXJyZW50
bHkmbmJzcDtyZWxlYXNlZCZuYnNwO2FscGhhLg0KPGJyPg0KPGJyPklmJm5ic3A7bm90LCZuYnNw
O3RoZW4mbmJzcDtpdCZuYnNwO3dvdWxkJm5ic3A7dGFrZSZuYnNwO25ldyZuYnNwO2NvZGUsJm5i
c3A7YWRkaW5nJm5ic3A7bW9yZSZuYnNwO2JyYW5jaGVzJm5ic3A7YmV0d2Vlbg0KPGJyPmVhY2gm
bmJzcDtydW4mbmJzcDtvZiZuYnNwO3RoZSZuYnNwO29wdGlvbiZuYnNwO3Byb2Nlc3NpbmcmbmJz
cDtsb29wLg0KPGJyPg0KPC9wPg0KPHA+Jm5ic3A7PC9wPg0KPHA+SGVlamluICZndDsmZ3Q7IE9r
LiBXZSdsbCByZWZsZWN0IHRoaXMgcG9pbnQgc28gdGhhdCBzdWItb3B0aW9ucyBzdGFydCBmcm9t
IA0KbnVtYmVyIDEuPC9wPg0KPHA+PGJyPkkmbmJzcDtub3RlJm5ic3A7YWxzbyZuYnNwO3RoYXQm
bmJzcDt0aGUmbmJzcDtzdWItb3B0aW9uJm5ic3A7Y29kZXMmbmJzcDthcmUmbmJzcDs4LWJpdCZu
YnNwO2NvZGUvbGVuZ3RoJm5ic3A7cGFpcnMuDQo8YnI+VGhhdCZuYnNwO2RvZXNuJiMzOTt0Jm5i
c3A7YWZmZWN0Jm5ic3A7SVNDJm5ic3A7REhDUCwmbmJzcDtidXQmbmJzcDtJJm5ic3A7d2FudGVk
Jm5ic3A7dG8mbmJzcDtwb2ludCZuYnNwO2l0Jm5ic3A7b3V0Jm5ic3A7Zm9yJm5ic3A7b3RoZXIN
Cjxicj5pbXBsZW1lbnRvcnMuDQo8YnI+DQo8YnI+SSZuYnNwO3RoaW5rJm5ic3A7dGhpcyZuYnNw
O2lzJm5ic3A7dGhlJm5ic3A7Zmlyc3QmbmJzcDt0aW1lJm5ic3A7d2UmIzM5O3ZlJm5ic3A7c2Vl
biZuYnNwO25vbi0xNi1iaXQmbmJzcDtjb2RlL2xlbmd0aHMNCjxicj5pbnNpZGUmbmJzcDtESENQ
djY/DQo8YnI+DQo8L3A+DQo8cD4mbmJzcDs8L3A+DQo8cD5IZWVqaW4gJmd0OyZndDsgSVB2NiBt
YWluIG9wdGlvbnMgJmFtcDsgbGVuZ3RocyBhcmUmbmJzcDtkZWZpbmVkIGFzJm5ic3A7MTYgYml0
LWZpZWxkcyANCmJ1dCBJIGNhbm5vdCBmaW5kIGFueSAxNiBiaXRzIGNvZGUgJmFtcDsgbGVuZ3Ro
IGluIElQdjYgc3ViLW9wdGlvbnMuPC9wPg0KPHA+U29tZSBvZiBzdWItb3B0aW9ucyAoQmluZGlu
ZyBVbmlxdWUgSWRlbnRpZmljYXRpb24gb3B0aW9uKSBvciBwcm9wb3NhbHMgc3VnZ2VzdGVkIA0K
dG8gdXNlIDgtYml0IGNvZGUgJmFtcDsgbGVuZ3RoIElQdjYgc3ViLW9wdGlvbnMuPC9wPg0KPHA+
IElzIHRoZXJlIGFueSBzdWItb3B0aW9uIHdpdGggMTYgYml0cyBjb2RlICZhbXA7IGxlbmd0aCBp
biBJUHY2PyBJZiBJIG1pc3NlZCANCnNvbWV0aGluZywga2luZGx5IGxldCBtZSBrbm93IGl0LiA8
L3A+DQo8cD48YnI+Jm5ic3A7Jm5ic3A7Jm5ic3A7SWYmbmJzcDt0aGUmbmJzcDtyZXF1ZXN0Jm5i
c3A7bWVzc2FnZSZuYnNwO2NhcnJpZXMmbmJzcDttb3JlJm5ic3A7dGhhbiZuYnNwO29uZSZuYnNw
O0hvbWUmbmJzcDtOZXR3b3JrJm5ic3A7SWRlbnRpZmllcg0KPGJyPiZuYnNwOyZuYnNwOyZuYnNw
O29wdGlvbnMsJm5ic3A7dGhlJm5ic3A7cmVwbHkmbmJzcDttZXNzYWdlJm5ic3A7TVVTVCZuYnNw
O2NvbnRhaW4mbmJzcDtIb21lJm5ic3A7TmV0d29yayZuYnNwO0luZm9ybWF0aW9uDQo8YnI+Jm5i
c3A7Jm5ic3A7Jm5ic3A7b3B0aW9ucyZuYnNwO2FzJm5ic3A7bWFueSZuYnNwO2FzJm5ic3A7SG9t
ZSZuYnNwO05ldHdvcmsmbmJzcDtJZGVudGlmaWVyJm5ic3A7b3B0aW9ucyZuYnNwO2luJm5ic3A7
dGhlJm5ic3A7cmVxdWVzdC4NCjxicj4NCjxicj5JJm5ic3A7dGhpbmsmbmJzcDsmIzM5O2FzJm5i
c3A7bWFueSYjMzk7Jm5ic3A7d2FudHMmbmJzcDt0byZuYnNwO2JlJm5ic3A7bW92ZWQmbmJzcDts
ZWZ0Jm5ic3A7NCZuYnNwO3dvcmRzJm5ic3A7b3ImbmJzcDtzby4NCjxicj4NCjwvcD4NCjxwPiZu
YnNwOzwvcD4NCjxwPkhlZWppbiAmZ3Q7Jmd0OyBUaGFua3MgZm9yIGNvcnJlY3RpbmcgdGhpcy48
L3A+DQo8cD4NCjxicj5TZWNvbmQsJm5ic3A7SSZuYnNwO3RoaW5rJm5ic3A7TVVTVCZuYnNwO2lz
Jm5ic3A7dG9vJm5ic3A7c3Ryb25nLCZuYnNwO3NpbmNlJm5ic3A7aWYmbmJzcDt0aGUmbmJzcDtE
SENQJm5ic3A7c2VydmVyJm5ic3A7aXMmbmJzcDtub3QNCjxicj5jb25maWd1cmVkJm5ic3A7d2l0
aCZuYnNwO3ZhbHVlcywmbmJzcDtpdCZuYnNwO3dpbGwmbmJzcDtiZSZuYnNwO3VuYWJsZSZuYnNw
O3RvJm5ic3A7cmVwbHkuJm5ic3A7Jm5ic3A7Q29uc2lkZXINCjxicj5zcGVjaWZpY2FsbHkmbmJz
cDtzZXJ2ZXImbmJzcDtzb2Z0d2FyZSZuYnNwO3RoYXQmbmJzcDtkb2VzJm5ic3A7bm90Jm5ic3A7
KHlldCkmbmJzcDtoYXZlJm5ic3A7c3VwcG9ydCZuYnNwO2Zvcg0KPGJyPnRoZXNlJm5ic3A7b3B0
aW9ucyZuYnNwOy0mbmJzcDt0aGV5Jm5ic3A7d2lsbCZuYnNwO2NlcnRhaW5seSZuYnNwO2hhdmUm
bmJzcDtubyZuYnNwO2NvZGUmbmJzcDt3aGljaCZuYnNwO2VuZm9yY2VzJm5ic3A7dGhlDQo8YnI+
Y29uc3RydWN0aW9uJm5ic3A7b2YmbmJzcDsmIzM5O2VtcHR5JiMzOTsmbmJzcDtvcHRpb25zLg0K
PGJyPg0KPGJyPg0KSGVlamluICZndDsmZ3Q7IFRoZSB1c2Ugb2YgJ01VU1QnIGlzIHNlbGVjdGVk
IHRha2luZyBpbnRvIGFjY291bnQgb3B0aW9uIG9yZGVyaW5nIA0KYW5kIG1hcHBpbmcuPC9wPg0K
PHA+Jm5ic3A7V2l0aG91dCB0aGUgc2FtZSBudW1iZXIgb2Ygb3B0aW9ucyBpbiByZXBseSwgb3B0
aW9ucyB3aXRoIHRoZSBzYW1lIA0KaWQtdHlwZSBjYW5ub3QgYmUgbWFwcGVkPC9wPg0KPHA+YmFz
ZWQgb24gb3JkZXJpbmcuIFRoaXMgaXMgYWxzbyAgcmVsYXRpdmUgdG8gdGhlJm5ic3A7Zm9sbG93
aW5nIGFuc3dlci48L3A+DQo8cD48YnI+Jm5ic3A7Jm5ic3A7Jm5ic3A7VGhlDQo8YnI+Jm5ic3A7
Jm5ic3A7Jm5ic3A7SG9tZSZuYnNwO05ldHdvcmsmbmJzcDtJbmZvcm1hdGlvbiZuYnNwO29wdGlv
bnMmbmJzcDtpbiZuYnNwO3RoZSZuYnNwO3JlcGx5Jm5ic3A7U0hPVUxEJm5ic3A7YXBwZWFyJm5i
c3A7aW4mbmJzcDt0aGUNCjxicj4mbmJzcDsmbmJzcDsmbmJzcDtzYW1lJm5ic3A7b3JkZXImbmJz
cDthcyZuYnNwO0hvbWUmbmJzcDtOZXR3b3JrJm5ic3A7SWRlbnRpZmllciZuYnNwO29wdGlvbnMm
bmJzcDtpbiZuYnNwO3RoZSZuYnNwO3JlcXVlc3QmbmJzcDthbmQmbmJzcDt0aGUNCjxicj4mbmJz
cDsmbmJzcDsmbmJzcDttYXRjaGluZyZuYnNwO2lzJm5ic3A7YmFzZWQmbmJzcDtvbiZuYnNwO3Ro
ZSZuYnNwO3NlcXVlbnRpYWwmbmJzcDtvcmRlciZuYnNwO29mJm5ic3A7b3B0aW9ucy4mbmJzcDsm
bmJzcDtUaGlzJm5ic3A7cHJvdmlkZXMNCjxicj4mbmJzcDsmbmJzcDsmbmJzcDthJm5ic3A7d2F5
Jm5ic3A7b2YmbmJzcDttYXRjaGluZyZuYnNwO2ZvciZuYnNwO0hvbWUmbmJzcDtOZXR3b3JrJm5i
c3A7SW5mb3JtYXRpb24mbmJzcDtvcHRpb25zJm5ic3A7d2l0aCZuYnNwO3RoZSZuYnNwO3NhbWUN
Cjxicj4mbmJzcDsmbmJzcDsmbmJzcDtpZC10eXBlLg0KPGJyPg0KPGJyPkkmbmJzcDtkb24mIzM5
O3QmbmJzcDtnZXQmbmJzcDtpdC4mbmJzcDsmbmJzcDtUaGUmbmJzcDtvcHRpb25zJm5ic3A7U0hP
VUxEJm5ic3A7cHBlYXImbmJzcDtpbiZuYnNwO3RoZSZuYnNwO3NhbWUmbmJzcDtvcmRlciwmbmJz
cDt3aGljaA0KPGJyPm1lYW5zJm5ic3A7dGhleSZuYnNwO21pZ2h0Jm5ic3A7bm90LCZuYnNwO2Fu
ZCZuYnNwO3RoZSZuYnNwO29yZGVyJm5ic3A7aXMmbmJzcDthbHNvJm5ic3A7dXNlZCZuYnNwO3Rv
Jm5ic3A7bWF0Y2gmbmJzcDtyZXBsaWVzDQo8YnI+YWdhaW5zdCZuYnNwO3JlcXVlc3RzPyZuYnNw
OyZuYnNwO1NvJm5ic3A7dGhlJm5ic3A7cHJvdG9jb2wmbmJzcDtzdGlwdWxhdGVzJm5ic3A7dGhh
dCZuYnNwO3NvbWV0aW1lcyZuYnNwO3JlcGxpZXMNCjxicj53aWxsJm5ic3A7bm90Jm5ic3A7bWF0
Y2gmbmJzcDt0aGVpciZuYnNwO3JlcXVlc3RzPw0KPGJyPg0KPGJyPkkmIzM5O20mbmJzcDtwcmV0
dHkmbmJzcDtzdXJlJm5ic3A7dGhpcyZuYnNwO2RvZXNuJiMzOTt0Jm5ic3A7d29yaywmbmJzcDth
bmQmbmJzcDtJJiMzOTttJm5ic3A7cHJldHR5Jm5ic3A7Y2VydGFpbiZuYnNwO3RoYXQNCjxicj53
ZSZuYnNwO2RvbiYjMzk7dCZuYnNwO3dhbnQmbmJzcDt0byZuYnNwO3N0aXB1bGF0ZSZuYnNwO3Ro
ZSZuYnNwO3N0cmljdCZuYnNwO29yZGVyaW5nJm5ic3A7b2YmbmJzcDt0aGUmbmJzcDtvcHRpb25z
LjwvcD4NCjxwPiZuYnNwOzwvcD4NCjxwPlNvLCZuYnNwO0kmIzM5O20mbmJzcDtub3QmbmJzcDtp
biZuYnNwO2Zhdm9yJm5ic3A7b2YmbmJzcDthZHZhbmNpbmcmbmJzcDt0aGlzJm5ic3A7ZG9jdW1l
bnQuDQo8YnI+DQo8YnI+SWYmbmJzcDt0aGVyZSZuYnNwO2lzJm5ic3A7YSZuYnNwO3JlcXVpcmVt
ZW50Jm5ic3A7Zm9yJm5ic3A7bXVsaXRwbGUmbmJzcDtpbnN0YW5jZXMmbmJzcDtvZiZuYnNwO3Ro
ZXNlJm5ic3A7b3B0aW9ucywNCjxicj5pdCZuYnNwO3dvdWxkJm5ic3A7YmUmbmJzcDtteSZuYnNw
O3N0cm9uZyZuYnNwO3ByZWZlcmVuY2UmbmJzcDtmb3ImbmJzcDt0aGUmbmJzcDttZWNoYW5pc20m
bmJzcDt0byZuYnNwO21vcmUmbmJzcDtjbG9zZWx5DQo8YnI+bWltaWMmbmJzcDtJQV8qJm5ic3A7
b3B0aW9ucyZuYnNwO3RoYW4mbmJzcDtoYXMmbmJzcDtiZWVuJm5ic3A7cHJlc2VudGVkJm5ic3A7
aGVyZS4NCjxicj4NCjwvcD4NCjxwPiZuYnNwOzwvcD4NCjxwPkhlZWppbiAmZ3Q7Jmd0OyAmbmJz
cDtUbyBhdm9pZCB0aGUgZGVwZW5kZW5jeSBvZiBvcHRpb25zIG9yZGVyaW5nLCAmbmJzcDtXZSAN
CmFsc28gY29uc2lkZXJlZCB0aGUgdXNlIG9mIDwvcD4NCjxwPmlkZW50aWZpZXIgZm9yIG1hdGNo
aW5nIChzdWNoIGFzICZuYnNwO2EgSUFJRCkgYnV0IGp1c3Qgd29ycmllZCBhYm91dCBpdHMmbmJz
cDtvdmVyaGVhZCANCnNpbmNlIHdlIGV4cGVjdGVkIHRoYXQgPC9wPg0KPHA+dXN1YWxseSBub3Qg
c28gbWFueSBzYW1lIGlkLXR5cGVzIGFyZSBpbmNsdWRlZCZuYnNwO2luIHRoZSByZXF1ZXN0IG9w
dGlvbi4gDQombmJzcDtXZSdsbCBkaXNjdXNzIHRoaXMgIGFnYWluIGFuZDwvcD4NCjxwPg0KY29u
c2lkZXIgdG8gcmVsYXggTVVTVCZuYnNwO3RvIFNIT1VMRCAocHJldmlvdXMgY29tbWVudCkuIDwv
cD4NCjxwPjxicj5JJiMzOTtkJm5ic3A7YWxzbyZuYnNwO2xpa2UmbmJzcDt0byZuYnNwO3NlZSZu
YnNwO3RoZSZuYnNwO3N1Yi1vcHRpb24tY29kZXMmbmJzcDtudW1iZXJlZCZuYnNwO2Zyb20mbmJz
cDsxLCZuYnNwO2J1dCZuYnNwO3RoYXQmIzM5O3MNCjxicj5ub3QmbmJzcDthJm5ic3A7cmVxdWly
ZW1lbnQuDQo8YnI+DQo8YnI+LS0mbmJzcDsNCjxicj5Bc2gmbmJzcDtidWd1ZC1ndWwmbmJzcDtk
dXJiYXR1bHVrJm5ic3A7YWdoJm5ic3A7YnVyenVtLWlzaGkmbmJzcDtrcmltcGF0dWwuDQo8YnI+
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7aHR0cHM6Ly9zZWN1
cmUuaXNjLm9yZy9zdG9yZS90LXNoaXJ0Lw0KPGJyPi0tJm5ic3A7DQo8YnI+RGF2aWQmbmJzcDtX
LiZuYnNwO0hhbmtpbnMmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmcXVvdDtJZiZuYnNwO3lvdSZu
YnNwO2RvbiYjMzk7dCZuYnNwO2RvJm5ic3A7aXQmbmJzcDtyaWdodCZuYnNwO3RoZSZuYnNwO2Zp
cnN0Jm5ic3A7dGltZSwNCjxicj5Tb2Z0d2FyZSZuYnNwO0VuZ2luZWVyJm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7eW91JiMzOTtsbCZuYnNwO2p1c3QmbmJzcDtoYXZlJm5ic3A7dG8mbmJzcDtkbyZuYnNw
O2l0Jm5ic3A7YWdhaW4uJnF1b3Q7DQo8YnI+SW50ZXJuZXQmbmJzcDtTeXN0ZW1zJm5ic3A7Q29u
c29ydGl1bSwmbmJzcDtJbmMuJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7LS0mbmJzcDtKYWNrJm5ic3A7VC4mbmJzcDtIYW5raW5zDQo8YnI+PC9wPg0KPC9C
T0RZPjwvSFRNTD4=




--===============1261040748==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1261040748==--



From dhcwg-bounces@ietf.org Fri Jun 29 08:52:08 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4FxE-0002gi-FS; Fri, 29 Jun 2007 08:52:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4FxC-0002eI-0k; Fri, 29 Jun 2007 08:52:02 -0400
Received: from zcars04f.nortel.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I4Fwb-0007Vu-R6; Fri, 29 Jun 2007 08:52:01 -0400
Received: from zrc2hxm2.corp.nortel.com (zrc2hxm2.corp.nortel.com
	[47.103.123.73])
	by zcars04f.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id
	l5TCpHE23754; Fri, 29 Jun 2007 12:51:17 GMT
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
Subject: RE: [dhcwg] EXTENDED: mip4 and dhc WG joint last call on
	draft-ietf-mip4-gen-ext-03.txt
Date: Fri, 29 Jun 2007 07:51:09 -0500
Message-ID: <6FC4416DDE56C44DA0AEE67BC7CA4371154315E6@zrc2hxm2.corp.nortel.com>
In-Reply-To: <C2A90304.482C8%rdroms@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] EXTENDED: mip4 and dhc WG joint last call on
	draft-ietf-mip4-gen-ext-03.txt
thread-index: Ace5bY6yzSyTZiVgEdyNKgARJOT6egA3hzew
References: <C2A90304.482C8%rdroms@cisco.com>
From: "Ahmad Muhanna" <amuhanna@nortel.com>
To: "Ralph Droms" <rdroms@cisco.com>, <mip4@ietf.org>,
	"DHC WG" <dhcwg@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org


I support advancing this draft to an RFC.

Regards,
Ahmad

> -----Original Message-----
> From: Ralph Droms [mailto:rdroms@cisco.com]=20
> Sent: Thursday, June 28, 2007 5:18 AM
> To: mip4@ietf.org; DHC WG
> Subject: [dhcwg] EXTENDED: mip4 and dhc WG joint last call on=20
> draft-ietf-mip4-gen-ext-03.txt
>=20
> There has been no response to this WG last call, so the=20
> deadline will be extended to 1700EDT, 07/05/07.
>=20
> =3D=3D=3D=3D=3D
> This message announces a joint WG last call for the mip4 and=20
> dhc WGs on "Mobile IPv4 Extension for Configuration Options Exchange"
> <draft-ietf-mip4-gen-ext-03.txt>.  The last call will=20
> conclude at 1700EDT, Monday, 06/25/07.
>=20
> The dhc WG is asked to review the use of DHCP options in this=20
> draft to pass configuration information to a mobile node.
>=20
> Please respond to this joint WG last call.  Responses may be=20
> sent to either mip4@ietf.org or dhcwg@ietf.org.  If you=20
> support acceptance of the document without change, respond=20
> with a simple acknowledgment, so that support for the=20
> document can be assessed.  Lack of discussion does not=20
> represent positive support.  If there is no expression of=20
> support for acceptance during the WG last call, the document=20
> will not be advanced to the IESG.
>=20
> draft-ietf-mip4-gen-ext-03.txt describes the mechanism for=20
> providing the host configuration information during Mobile IP=20
> registration.  One or more Configuration Options Exchange=20
> Extensions may be included in the registration message to=20
> provide the Mobile Node the configuration parameters needed=20
> for network service (e.g.  DNS).  This draft is available as=20
> http://www.ietf.org/internet-drafts/draft-ietf-mip4-gen-ext-03.txt
>=20
> - Stig Venaas, Ralph Droms
>   dhc WG chairs
>=20
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg
>=20

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



From dhcwg-bounces@ietf.org Fri Jun 29 12:32:25 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4JOP-0004na-9S; Fri, 29 Jun 2007 12:32:21 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4JOO-0004k5-EF
	for dhcwg@ietf.org; Fri, 29 Jun 2007 12:32:20 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I4JOO-0006SA-0K
	for dhcwg@ietf.org; Fri, 29 Jun 2007 12:32:20 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 29 Jun 2007 12:31:59 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAIfRhEZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,476,1175486400"; 
	d="scan'208"; a="64020569:sNHT178855112"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5TGVx1k020658; 
	Fri, 29 Jun 2007 12:31:59 -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.12.10/8.12.6) with ESMTP id l5TGVSsK014944; 
	Fri, 29 Jun 2007 16:31:45 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.1830); 
	Fri, 29 Jun 2007 12:31:39 -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
Subject: RE: [dhcwg] EXTENDED: Joint mip6 and dhc WG last call
	ondraft-ietf-mip6-bootstrapping-integrated and draft-ietf-mip6-hiopt
Date: Fri, 29 Jun 2007 12:31:38 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB2104619A7D@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <20070625184752.GB6852@isc.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] EXTENDED: Joint mip6 and dhc WG last call
	ondraft-ietf-mip6-bootstrapping-integrated and
	draft-ietf-mip6-hiopt
Thread-Index: Ace3WWg/XZxh5Z7cRKKieidQRaE8LgDDjaMg
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "DHC WG" <dhcwg@ietf.org>, <heejin.jang@samsung.com>,
	<alper01.yegin@partner.samsung.com>, <kchowdhury@starentnetworks.com>, 
	<athene@sait.samsung.co.kr>
X-OriginalArrivalTime: 29 Jun 2007 16:31:39.0295 (UTC)
	FILETIME=[F7F92AF0:01C7BA6A]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7010; t=1183134719;
	x=1183998719; c=relaxed/simple; s=rtpdkim1001;
	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]=20EXTENDED=3A=20Joint=20mip6=20and=20dhc=20WG
	=20last=20call=20ondraft-ietf-mip6-bootstrapping-integrated=20and=20draft-
	ietf-mip6-hiopt |Sender:=20
	|To:=20=22DHC=20WG=22=20<dhcwg@ietf.org>, =20<heejin.jang@samsung.com>,
	=0A
	=20=20=20=20=20=20=20=20<alper01.yegin@partner.samsung.com>,
	=20<kchowdhury @starentnetworks.com>,
	=0A=20=20=20=20=20=20=20=20<athene@sait.samsung.co.k r>;
	bh=whAmq3ojn6h4Coswyhfb+o3A6yfrmoCkQ/67jPbtLu0=;
	b=HoWzyRI7MFIv+6GotuTX8AEPE8U/DjxMyQyXhS1KAha1muA1t0mFh44WWu6ki9T2CEyYmP2j
	CxiIJnlyGF7S5168KGzBLxOnLE+HzMMjVot/MWUBQV5IR6dXcaUP7h8H;
Authentication-Results: rtp-dkim-1; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9af087f15dbdd4c64ae6bbcdbc5b1d44
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Regarding
http://www.ietf.org/internet-drafts/draft-ietf-mip6-hiopt-05.txt, David
did an excellent and thorough review.

I too have many of the same issues as David.

1. Use of 16-bit suboptions in OPTION_MIP6-RELAY and OPTION_MIP6-HNINF.
Using 8-bit suboptions just complicates implementations that must
support this and packages that decode it. For DHCPv6, we really should
stick to use 16-bit TLV data *ALL THE WAY*. And, the cost of 2 more
bytes/suboption isn't a big deal.

But, perhaps these really aren't sub-option but instead radius encoded
attributes ("This option carries the RADIUS or Diameter attributes that
are received at the NAS from the AAAH.")? In that case, shouldn't the
sub-options description clearly indicate that and be radius-attributes
or something like that. It is CRITICAL to note that for radius
attributes, the L field in the TLV *includes* the L field (which is not
the case for DHCP options!).

But, then "3.2.1.  MIP6 Relay Agent Sub-option" lists these suboptions
which clearly are not the radius encode attributes.

2. Do not use suboption 0. All other sub-options that I'm aware of
always start numbering at 1 and you're just asking for trouble with
implementations (apparently such as ISC's) that assume 0 is not "valid".
We also have code that would break if sub-option 0 is used in our server
(though for a completely different reason than the ISC issue).

While you can argue that any suboption value should be valid, that isn't
the issue. If you want these options supported by implementations,
everything you can do to make that easy to do (by following existing
conventions) will make it that much easier for the support to be added.
If a lot of code needs to be reworked and retested, you're not as likely
to get the options deployed.


[The remaining comments are probably more because of my ignorance of
this solution as I haven't kept up with the MIP6 work.]

3. Is there a need to establish a registry for id-type in these options,
or does this already exist somewhere else in the MIP6 space? If it does
exist elsewhere, how about referencing that?=20

If these are newly assigned values, wouldn't using 0 for no-preference
make more sense?

4. Is there a need to establish a registry for the suboptions for these
options?

5. Home Network Identifier field:

- "In this case, the Home Network Identifier field SHOULD be set to 0."
Don't you mean that it should not be present? (IE, option length should
be 2 and just have the id-type and reserved bytes?)

- It might be useful to indicate that this Home Network Identifier field
does NOT include a null byte to terminate the string? Or, perhaps this
should always be null terminated and hence why you say "SHOULD be set to
0"?


Bottom line, I agree with David that we SHOULD NOT advance this draft at
this time. It still needs work.

- Bernie

-----Original Message-----
From: David W. Hankins [mailto:David_Hankins@isc.org]=20
Sent: Monday, June 25, 2007 2:48 PM
To: DHC WG
Subject: Re: [dhcwg] EXTENDED: Joint mip6 and dhc WG last call
ondraft-ietf-mip6-bootstrapping-integrated and draft-ietf-mip6-hiopt

On Mon, Jun 25, 2007 at 10:43:12AM -0400, Ralph Droms wrote:
> There has been no response to this WG last call, so the deadline will
be
> extended to 1700EDT, 07/02/07.

My excuse is that I was in Alaska.

>
http://www.ietf.org/internet-drafts/draft-ietf-mip6-bootstrapping-integr
ated
> -04.txt

Correction (I think?):

=20
http://www.ietf.org/internet-drafts/draft-ietf-mip6-bootstrapping-integr
ated-dhc-04.txt

I actually don't see a lot in there for DHCWG to review.  Maybe I'm
not looking hard enough?

I am a little concerned (but only a little) at the extent to which
it defines simplified RFC3315 behaviour ("summarizing" the process
in which a client is identified and configured).


   (3) The Relay Agent intercepts the Information Request from the

I think "receives" is a better word, considering that the packet is
transmitted to a multicast address.  "intercept" has more of an
insinuation that the relay would not normally receive the packet.


So I see no problem advancing this draft to the IESG.


> and http://www.ietf.org/internet-drafts/draft-ietf-mip6-hiopt-05.txt

ISC DHCP and others share option processing code between the v4
and v6 side of the house.  I don't know about the others, but the
net effect for ISC DHCP is that code 0 is treated as an "end tag"
(code 255, or "code all ones" for any code width, is not).  This
sounds a little weird, but that's the contrivance of the loop we
selected.

If the sub-options could be numbered from 1, then this draft would
be compatible with our currently released alpha.

If not, then it would take new code, adding more branches between
each run of the option processing loop.


I note also that the sub-option codes are 8-bit code/length pairs.
That doesn't affect ISC DHCP, but I wanted to point it out for other
implementors.

I think this is the first time we've seen non-16-bit code/lengths
inside DHCPv6?


   If the request message carries more than one Home Network Identifier
   options, the reply message MUST contain Home Network Information
   options as many as Home Network Identifier options in the request.

I think 'as many' wants to be moved left 4 words or so.

Second, I think MUST is too strong, since if the DHCP server is not
configured with values, it will be unable to reply.  Consider
specifically server software that does not (yet) have support for
these options - they will certainly have no code which enforces the
construction of 'empty' options.


   The
   Home Network Information options in the reply SHOULD appear in the
   same order as Home Network Identifier options in the request and the
   matching is based on the sequential order of options.  This provides
   a way of matching for Home Network Information options with the same
   id-type.

I don't get it.  The options SHOULD ppear in the same order, which
means they might not, and the order is also used to match replies
against requests?  So the protocol stipulates that sometimes replies
will not match their requests?

I'm pretty sure this doesn't work, and I'm pretty certain that
we don't want to stipulate the strict ordering of the options.


So, I'm not in favor of advancing this document.

If there is a requirement for mulitple instances of these options,
it would be my strong preference for the mechanism to more closely
mimic IA_* options than has been presented here.

I'd also like to see the sub-option-codes numbered from 1, but that's
not a requirement.

--=20
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
				 https://secure.isc.org/store/t-shirt/
--=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

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



From dhcwg-bounces@ietf.org Fri Jun 29 12:35:49 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4JRk-0008Cu-11; Fri, 29 Jun 2007 12:35:48 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4JRi-0008Co-Bo
	for dhcwg@ietf.org; Fri, 29 Jun 2007 12:35:46 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I4JRh-0006jl-SF
	for dhcwg@ietf.org; Fri, 29 Jun 2007 12:35:46 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 29 Jun 2007 12:35:43 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAArShEZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,476,1175486400"; 
	d="scan'208"; a="124898021:sNHT611416632"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l5TGZgor022498; 
	Fri, 29 Jun 2007 12:35:42 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5TGZC78028893; 
	Fri, 29 Jun 2007 16:35:46 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.1830); 
	Fri, 29 Jun 2007 12:35:41 -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
Subject: RE: [dhcwg] EXTENDED: Joint mip6 and dhc WG last call
	ondraft-ietf-mip6-bootstrapping-integrated and draft-ietf-mip6-hiopt
Date: Fri, 29 Jun 2007 12:35:40 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB2104619A81@xmb-rtp-20a.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] EXTENDED: Joint mip6 and dhc WG last call
	ondraft-ietf-mip6-bootstrapping-integrated and
	draft-ietf-mip6-hiopt
Thread-Index: Ace3WWg/XZxh5Z7cRKKieidQRaE8LgDDjaMgAADfX1A=
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "DHC WG" <dhcwg@ietf.org>, <kchowdhury@starentnetworks.com>,
	<a.yegin@partner.samsung.com>
X-OriginalArrivalTime: 29 Jun 2007 16:35:41.0226 (UTC)
	FILETIME=[882CE8A0:01C7BA6B]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7665; t=1183134942;
	x=1183998942; c=relaxed/simple; s=rtpdkim1001;
	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]=20EXTENDED=3A=20Joint=20mip6=20and=20dhc=20WG
	=20last=20call=20ondraft-ietf-mip6-bootstrapping-integrated=20and=20draft-
	ietf-mip6-hiopt |Sender:=20
	|To:=20=22DHC=20WG=22=20<dhcwg@ietf.org>,
	=20<kchowdhury@starentnetworks.c
	om>,=0A=20=20=20=20=20=20=20=20<a.yegin@partner.samsung.com>;
	bh=ytSyX8COqh3Y9r7Vt7KN9iRTvatYljS6rc4LqrCYNlU=;
	b=LaWfLqFk3uleNrM9bHgfSbj0tlJqwNFTNJfJGh3Ff2v2bXTyWacMzWdHjjMzGgcqjsGe8M1P
	/cTqc5ZjD9lR++A0plOoRu7MftRXST3OvhVhpE0DTJW3/hxfbpDGbjDt;
Authentication-Results: rtp-dkim-1; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Regarding the other draft,
http://www.ietf.org/internet-drafts/draft-ietf-mip6-bootstrapping-integr
ated-dhc-04.txt:

As this depends on the mip6-hiopt draft, I think we should hold off on
this draft too.

They need to advance together.

- Bernie

-----Original Message-----
From: Bernie Volz (volz)=20
Sent: Friday, June 29, 2007 12:32 PM
To: DHC WG; 'heejin.jang@samsung.com';
'alper01.yegin@partner.samsung.com'; 'kchowdhury@starentnetworks.com';
'athene@sait.samsung.co.kr'
Cc: 'David W. Hankins'
Subject: RE: [dhcwg] EXTENDED: Joint mip6 and dhc WG last call
ondraft-ietf-mip6-bootstrapping-integrated and draft-ietf-mip6-hiopt

Regarding
http://www.ietf.org/internet-drafts/draft-ietf-mip6-hiopt-05.txt, David
did an excellent and thorough review.

I too have many of the same issues as David.

1. Use of 16-bit suboptions in OPTION_MIP6-RELAY and OPTION_MIP6-HNINF.
Using 8-bit suboptions just complicates implementations that must
support this and packages that decode it. For DHCPv6, we really should
stick to use 16-bit TLV data *ALL THE WAY*. And, the cost of 2 more
bytes/suboption isn't a big deal.

But, perhaps these really aren't sub-option but instead radius encoded
attributes ("This option carries the RADIUS or Diameter attributes that
are received at the NAS from the AAAH.")? In that case, shouldn't the
sub-options description clearly indicate that and be radius-attributes
or something like that. It is CRITICAL to note that for radius
attributes, the L field in the TLV *includes* the L field (which is not
the case for DHCP options!).

But, then "3.2.1.  MIP6 Relay Agent Sub-option" lists these suboptions
which clearly are not the radius encode attributes.

2. Do not use suboption 0. All other sub-options that I'm aware of
always start numbering at 1 and you're just asking for trouble with
implementations (apparently such as ISC's) that assume 0 is not "valid".
We also have code that would break if sub-option 0 is used in our server
(though for a completely different reason than the ISC issue).

While you can argue that any suboption value should be valid, that isn't
the issue. If you want these options supported by implementations,
everything you can do to make that easy to do (by following existing
conventions) will make it that much easier for the support to be added.
If a lot of code needs to be reworked and retested, you're not as likely
to get the options deployed.


[The remaining comments are probably more because of my ignorance of
this solution as I haven't kept up with the MIP6 work.]

3. Is there a need to establish a registry for id-type in these options,
or does this already exist somewhere else in the MIP6 space? If it does
exist elsewhere, how about referencing that?=20

If these are newly assigned values, wouldn't using 0 for no-preference
make more sense?

4. Is there a need to establish a registry for the suboptions for these
options?

5. Home Network Identifier field:

- "In this case, the Home Network Identifier field SHOULD be set to 0."
Don't you mean that it should not be present? (IE, option length should
be 2 and just have the id-type and reserved bytes?)

- It might be useful to indicate that this Home Network Identifier field
does NOT include a null byte to terminate the string? Or, perhaps this
should always be null terminated and hence why you say "SHOULD be set to
0"?


Bottom line, I agree with David that we SHOULD NOT advance this draft at
this time. It still needs work.

- Bernie

-----Original Message-----
From: David W. Hankins [mailto:David_Hankins@isc.org]=20
Sent: Monday, June 25, 2007 2:48 PM
To: DHC WG
Subject: Re: [dhcwg] EXTENDED: Joint mip6 and dhc WG last call
ondraft-ietf-mip6-bootstrapping-integrated and draft-ietf-mip6-hiopt

On Mon, Jun 25, 2007 at 10:43:12AM -0400, Ralph Droms wrote:
> There has been no response to this WG last call, so the deadline will
be
> extended to 1700EDT, 07/02/07.

My excuse is that I was in Alaska.

>
http://www.ietf.org/internet-drafts/draft-ietf-mip6-bootstrapping-integr
ated
> -04.txt

Correction (I think?):

=20
http://www.ietf.org/internet-drafts/draft-ietf-mip6-bootstrapping-integr
ated-dhc-04.txt

I actually don't see a lot in there for DHCWG to review.  Maybe I'm
not looking hard enough?

I am a little concerned (but only a little) at the extent to which
it defines simplified RFC3315 behaviour ("summarizing" the process
in which a client is identified and configured).


   (3) The Relay Agent intercepts the Information Request from the

I think "receives" is a better word, considering that the packet is
transmitted to a multicast address.  "intercept" has more of an
insinuation that the relay would not normally receive the packet.


So I see no problem advancing this draft to the IESG.


> and http://www.ietf.org/internet-drafts/draft-ietf-mip6-hiopt-05.txt

ISC DHCP and others share option processing code between the v4
and v6 side of the house.  I don't know about the others, but the
net effect for ISC DHCP is that code 0 is treated as an "end tag"
(code 255, or "code all ones" for any code width, is not).  This
sounds a little weird, but that's the contrivance of the loop we
selected.

If the sub-options could be numbered from 1, then this draft would
be compatible with our currently released alpha.

If not, then it would take new code, adding more branches between
each run of the option processing loop.


I note also that the sub-option codes are 8-bit code/length pairs.
That doesn't affect ISC DHCP, but I wanted to point it out for other
implementors.

I think this is the first time we've seen non-16-bit code/lengths
inside DHCPv6?


   If the request message carries more than one Home Network Identifier
   options, the reply message MUST contain Home Network Information
   options as many as Home Network Identifier options in the request.

I think 'as many' wants to be moved left 4 words or so.

Second, I think MUST is too strong, since if the DHCP server is not
configured with values, it will be unable to reply.  Consider
specifically server software that does not (yet) have support for
these options - they will certainly have no code which enforces the
construction of 'empty' options.


   The
   Home Network Information options in the reply SHOULD appear in the
   same order as Home Network Identifier options in the request and the
   matching is based on the sequential order of options.  This provides
   a way of matching for Home Network Information options with the same
   id-type.

I don't get it.  The options SHOULD ppear in the same order, which
means they might not, and the order is also used to match replies
against requests?  So the protocol stipulates that sometimes replies
will not match their requests?

I'm pretty sure this doesn't work, and I'm pretty certain that
we don't want to stipulate the strict ordering of the options.


So, I'm not in favor of advancing this document.

If there is a requirement for mulitple instances of these options,
it would be my strong preference for the mechanism to more closely
mimic IA_* options than has been presented here.

I'd also like to see the sub-option-codes numbered from 1, but that's
not a requirement.

--=20
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
				 https://secure.isc.org/store/t-shirt/
--=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

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



From dhcwg-bounces@ietf.org Fri Jun 29 16:19:11 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Mvr-0002K0-81; Fri, 29 Jun 2007 16:19:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Mvp-000290-1N; Fri, 29 Jun 2007 16:19:05 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I4MvS-0002bH-8L; Fri, 29 Jun 2007 16:19:05 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 29 Jun 2007 16:18:41 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAB8GhUZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,476,1175486400"; 
	d="scan'208"; a="64043355:sNHT39304278"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5TKIfxo011734; 
	Fri, 29 Jun 2007 16:18:41 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5TKIf6a001047; 
	Fri, 29 Jun 2007 20:18:41 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.1830); 
	Fri, 29 Jun 2007 16:18:41 -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
Subject: RE: [dhcwg] EXTENDED: mip4 and dhc WG joint last call on
	draft-ietf-mip4-gen-ext-03.txt
Date: Fri, 29 Jun 2007 16:18:40 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB2104619B99@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <C2A90304.482C8%rdroms@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] EXTENDED: mip4 and dhc WG joint last call on
	draft-ietf-mip4-gen-ext-03.txt
Thread-Index: Ace5bY6yzSyTZiVgEdyNKgARJOT6egBG+QRQ
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "Ralph Droms \(rdroms\)" <rdroms@cisco.com>, <mip4@ietf.org>,
	"DHC WG" <dhcwg@ietf.org>
X-OriginalArrivalTime: 29 Jun 2007 20:18:41.0720 (UTC)
	FILETIME=[AF924380:01C7BA8A]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2250; t=1183148321;
	x=1184012321; 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]=20EXTENDED=3A=20mip4=20and=20dhc=20WG=20joint
	=20last=20call=20on=20draft-ietf-mip4-gen-ext-03.txt
	|Sender:=20
	|To:=20=22Ralph=20Droms=20\(rdroms\)=22=20<rdroms@cisco.com>,
	=20<mip4@iet
	f.org>,=0A=20=20=20=20=20=20=20=20=22DHC=20WG=22=20<dhcwg@ietf.org>;
	bh=cD3gSgNOpPI5MSFuLXKK6KZDhsz5GPWRSo5l2ntT4w0=;
	b=MDs9NreN/oS3W8mSeC3SQN8YHn7m78BLf3qaF1pPEuIM0hZrSnLnPkFygslf6p+5vU+URDHZ
	Sr9IzjV9S/WI7M6avutv4hoyrRCq6hEsqNJP4SaAhRD9QdvoIW4daXfw;
Authentication-Results: rtp-dkim-2; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Ralph, et al:

This document only references DHCP and does not alter or extend it, so I
see no strong need for wide review by the DHC WG.

One suggestion is to add the "Note that DHCP option codes (OpCode)
referenced by this document are defined in [RFC2132].", that is in the
IANA Considerations, earlier because the IANA Considerations are usually
dropped when the RFC is produced. So, this might get lost (and isn't
really an IANA Considerations issue anyway).

- Bernie

-----Original Message-----
From: Ralph Droms (rdroms)=20
Sent: Thursday, June 28, 2007 6:18 AM
To: mip4@ietf.org; DHC WG
Subject: [dhcwg] EXTENDED: mip4 and dhc WG joint last call on
draft-ietf-mip4-gen-ext-03.txt

There has been no response to this WG last call, so the deadline will be
extended to 1700EDT, 07/05/07.

=3D=3D=3D=3D=3D
This message announces a joint WG last call for the mip4 and dhc WGs
on "Mobile IPv4 Extension for Configuration Options Exchange"
<draft-ietf-mip4-gen-ext-03.txt>.  The last call will conclude at
1700EDT, Monday, 06/25/07.

The dhc WG is asked to review the use of DHCP options in this draft to
pass configuration information to a mobile node.

Please respond to this joint WG last call.  Responses may be sent to
either mip4@ietf.org or dhcwg@ietf.org.  If you support acceptance of
the document without change, respond with a simple acknowledgment, so
that support for the document can be assessed.  Lack of discussion
does not represent positive support.  If there is no expression of
support for acceptance during the WG last call, the document will not
be advanced to the IESG.

draft-ietf-mip4-gen-ext-03.txt describes the mechanism for providing
the host configuration information during Mobile IP registration.  One
or more Configuration Options Exchange Extensions may be included in
the registration message to provide the Mobile Node the configuration
parameters needed for network service (e.g.  DNS).  This draft is
available as
http://www.ietf.org/internet-drafts/draft-ietf-mip4-gen-ext-03.txt

- Stig Venaas, Ralph Droms
  dhc WG chairs


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

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



From dhcwg-bounces@ietf.org Fri Jun 29 17:20:30 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4NtC-0004Mt-QH; Fri, 29 Jun 2007 17:20:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4NtB-0004Ml-Vk
	for dhcwg@ietf.org; Fri, 29 Jun 2007 17:20:25 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4NsJ-0001k7-Rx
	for dhcwg@ietf.org; Fri, 29 Jun 2007 17:20:25 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 29 Jun 2007 17:19:31 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAOYThUZAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.16,476,1175486400"; 
	d="scan'208"; a="124925662:sNHT40478976"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5TLJVSL004203; 
	Fri, 29 Jun 2007 17:19:31 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5TLJT6a016790; 
	Fri, 29 Jun 2007 21:19:29 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.1830); 
	Fri, 29 Jun 2007 17:19:28 -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
Subject: RE: [dhcwg] dhc wg last call on  draft-ietf-dhc-pxelinux-01
Date: Fri, 29 Jun 2007 17:19:28 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB2104619BF1@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <46823079.5050405@uninett.no>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] dhc wg last call on  draft-ietf-dhc-pxelinux-01
Thread-Index: Ace4nzo7p38aIPS3SSaRrGqqpr2ArgB8n2hw
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "Stig Venaas" <stig.venaas@uninett.no>, "dhcwg" <dhcwg@ietf.org>,
	"David W. Hankins" <David_Hankins@isc.org>
X-OriginalArrivalTime: 29 Jun 2007 21:19:28.0939 (UTC)
	FILETIME=[2D7BB7B0:01C7BA93]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2973; t=1183151971;
	x=1184015971; 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]=20dhc=20wg=20last=20call=20on=20=20draft-ietf
	-dhc-pxelinux-01 |Sender:=20
	|To:=20=22Stig=20Venaas=22=20<stig.venaas@uninett.no>,
	=20=22dhcwg=22=20<d hcwg@ietf.org>,
	=0A=20=20=20=20=20=20=20=20=22David=20W.=20Hankins=22=20<Da
	vid_Hankins@isc.org>;
	bh=5QNWTNnfXYZ101hgx/R9RNXxEtQBw1rmVy5/HgjRPPk=;
	b=ZscICPrawCpSJ21Z3Nn+qtL7fFiEYh/FjwMHB6Vdxn9R7gqrFm2zCO2Mtl7pcdDSqh6tp9Np
	XSz2wgRFcxcFTRHqQSYoGMvz8BUx4Bbp1aqnwxevu4UuAEQcY+Zn/+HW;
Authentication-Results: rtp-dkim-2; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

I fully support this document moving forward.

I suggest that perhaps:

   1.  Move DHCPv4 Option code 208 from 'Tentatively Assigned' to
       'Unassigned, Last Resort'.  It is hoped that Unassigned DHCP
       Option Codes (that had never been Tentatively Assigned) SHOULD be
       allocated prior to assigning this option code, but otherwise
       SHOULD be allocated before any option code that has been
       Tentatively Assigned, or Assigned.

Also might recommend that this option code (even as a last resort) not
be used for a future purpose that could result in the magic value
appearing in the option? Though we'll probably long have forgotten this!

Therefore, I think it makes more sense to just allocate 208 to PXELINUX,
but call it a deprecated option. Then if 10 years from now we're out of
option codes, we could reclaim it. But, if we never need it, no harm
done. I also think this is easier than tagging it as "last resort".

This of course also impacts section 3.4, which would have to be
reworded.

A couple of nits:

1. Rename section 6 to "Reboot Time Option".

   3.  MAGIC Option . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4.  Configuration File Option  . . . . . . . . . . . . . . . . . .  5
   5.  Path Prefix Option . . . . . . . . . . . . . . . . . . . . . .  6
   6.  Option 211 - Reboot Time . . . . . . . . . . . . . . . . . . .  8

2. Perhaps the title should just be "PXELINUX Options"? As 'Site Local'
are now redefined (per RFC 3942) and as this just documents the PXELINUX
usage.

I don't think there would be need to respind this document for any of
these (if adopted) - they can be handled as notes to the RFC-Editor?

- Bernie

-----Original Message-----
From: Stig Venaas [mailto:stig.venaas@uninett.no]=20
Sent: Wednesday, June 27, 2007 5:40 AM
To: dhcwg
Subject: [dhcwg] dhc wg last call on draft-ietf-dhc-pxelinux-01

This message announces a dhc wg last call on "PXELINUX Use of 'Site
Local' Option Space" <draft-ietf-dhc-pxelinux-01.txt>.  The last call
will conclude at 1700EDT on Mon, 2007-07-09.

Please respond to this WG last call.  If you support acceptance of the
document without change, respond with a simple acknowledgment, so that
support for the document can be assessed.  Lack of discussion does not
represent positive support.  If there is no expression of support for
acceptance during the WG last call, the document will not be advanced
to the IESG.

draft-ietf-dhc-pxelinux-01 is in response to the process of
reclassifying site-specific options, RFC 3942, and describes the use
by PXELINUX of some DHCP Option Codes numbering from 208-211.  These
codes were designated 'Site Local' prior to this action, and are
redefined by RFC 3942 as available for allocation as standard DHCP
Options.

Stig

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

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



From dhcwg-bounces@ietf.org Sat Jun 30 00:20:33 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4URe-00059V-B8; Sat, 30 Jun 2007 00:20:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4URc-00055E-UF
	for dhcwg@ietf.org; Sat, 30 Jun 2007 00:20:24 -0400
Received: from terminus.zytor.com ([192.83.249.54])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4URY-0007bU-I5
	for dhcwg@ietf.org; Sat, 30 Jun 2007 00:20:24 -0400
Received: from titan.hos.anvin.org ([207.219.199.245]) (authenticated bits=0)
	by terminus.zytor.com (8.13.8/8.13.8) with ESMTP id l5U4Gv1p005125
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 29 Jun 2007 21:16:59 -0700
Message-ID: <4685D938.6020204@zytor.com>
Date: Sat, 30 Jun 2007 00:16:56 -0400
From: "H. Peter Anvin" <hpa@zytor.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070615)
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>
Subject: Re: [dhcwg] dhc wg last call on  draft-ietf-dhc-pxelinux-01
References: <8E296595B6471A4689555D5D725EBB2104619BF1@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <8E296595B6471A4689555D5D725EBB2104619BF1@xmb-rtp-20a.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.88.7/3560/Fri Jun 29 16:32:19 2007 on
	terminus.zytor.com
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: dhcwg <dhcwg@ietf.org>, Stig Venaas <stig.venaas@uninett.no>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Bernie Volz (volz) wrote:
> 
> 1. Rename section 6 to "Reboot Time Option".
> 
>    3.  MAGIC Option . . . . . . . . . . . . . . . . . . . . . . . . .  4
>    4.  Configuration File Option  . . . . . . . . . . . . . . . . . .  5
>    5.  Path Prefix Option . . . . . . . . . . . . . . . . . . . . . .  6
>    6.  Option 211 - Reboot Time . . . . . . . . . . . . . . . . . . .  8
> 
> 2. Perhaps the title should just be "PXELINUX Options"? As 'Site Local'
> are now redefined (per RFC 3942) and as this just documents the PXELINUX
> usage.
> 

I personally think that would be unfortunate.  At least 209 and 211 I 
believe would be generally useful, and 210 certainly would have 
applicability to at least some set of other NBPs.

	-hpa

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



From dhcwg-bounces@ietf.org Sat Jun 30 00:32:03 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4Ucs-0003Hm-4H; Sat, 30 Jun 2007 00:32:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4Ucr-0003Hh-HK
	for dhcwg@ietf.org; Sat, 30 Jun 2007 00:32:01 -0400
Received: from terminus.zytor.com ([192.83.249.54])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4Ucm-0002Gt-7S
	for dhcwg@ietf.org; Sat, 30 Jun 2007 00:32:01 -0400
Received: from titan.hos.anvin.org ([207.219.199.245]) (authenticated bits=0)
	by terminus.zytor.com (8.13.8/8.13.8) with ESMTP id l5U4Se9i006070
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 29 Jun 2007 21:28:43 -0700
Message-ID: <4685DBF7.8070900@zytor.com>
Date: Sat, 30 Jun 2007 00:28:39 -0400
From: "H. Peter Anvin" <hpa@zytor.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070615)
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>
Subject: Re: [dhcwg] dhc wg last call on  draft-ietf-dhc-pxelinux-01
References: <8E296595B6471A4689555D5D725EBB2104619BF1@xmb-rtp-20a.amer.cisco.com>
	<4685D938.6020204@zytor.com>
In-Reply-To: <4685D938.6020204@zytor.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.88.7/3560/Fri Jun 29 16:32:19 2007 on
	terminus.zytor.com
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: dhcwg <dhcwg@ietf.org>, Stig Venaas <stig.venaas@uninett.no>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

H. Peter Anvin wrote:
>>
>> 2. Perhaps the title should just be "PXELINUX Options"? As 'Site Local'
>> are now redefined (per RFC 3942) and as this just documents the PXELINUX
>> usage.
> 
> I personally think that would be unfortunate.  At least 209 and 211 I 
> believe would be generally useful, and 210 certainly would have 
> applicability to at least some set of other NBPs.
> 

Please disregard this previous message.  I'm clearly posting way too late.

Quite on the contrary, I believe Bernie is correct.

	-hpa



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



From dhcwg-bounces@ietf.org Sat Jun 30 15:24:27 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4iYM-0001BB-7n; Sat, 30 Jun 2007 15:24:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4iYK-0001B4-KY
	for dhcwg@ietf.org; Sat, 30 Jun 2007 15:24:16 -0400
Received: from terminus.zytor.com ([192.83.249.54])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4iYB-0007rg-BI
	for dhcwg@ietf.org; Sat, 30 Jun 2007 15:24:16 -0400
Received: from titan.hos.anvin.org ([205.233.54.227]) (authenticated bits=0)
	by terminus.zytor.com (8.13.8/8.13.8) with ESMTP id l5UJKq2M024305
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sat, 30 Jun 2007 12:20:54 -0700
Message-ID: <4686AD10.2030302@zytor.com>
Date: Sat, 30 Jun 2007 15:20:48 -0400
From: "H. Peter Anvin" <hpa@zytor.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070615)
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>
Subject: Re: [dhcwg] DHCPv6 ORO - mandatory?
References: <8E296595B6471A4689555D5D725EBB210461934A@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <8E296595B6471A4689555D5D725EBB210461934A@xmb-rtp-20a.amer.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.88.7/3562/Sat Jun 30 09:36:29 2007 on
	terminus.zytor.com
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: dhcwg@ietf.org, Ted Lemon <Ted.Lemon@nominum.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Bernie Volz (volz) wrote:
> Ted:
> 
> I disagree. If a client *just* wants addresses, why should it include an
> ORO?
> 
> What needs to be clear is if no ORO is provided, no options (other than
> those related to the core protocol which are NOT typically in the ORO)
> will be returned by the server.
> 
> I think, though perhaps you don't, that the ORO SHOULD NOT include IA_NA
> (and IAADDR), Server Identifier, Client Identifier option numbers
> because these not OPTIONAL for the server to return.
> 

Wouldn't the safest thing be:

The client SHOULD send the ORO which SHOULD include these options;
the server MUST return these options regardless of whether or not an ORO 
is included and whether or not these options are included in the ORO.

	-hpa

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



From dhcwg-bounces@ietf.org Sat Jun 30 15:35:15 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4iiu-0006Tb-Ab; Sat, 30 Jun 2007 15:35:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4iir-0006Ny-9w
	for dhcwg@ietf.org; Sat, 30 Jun 2007 15:35:10 -0400
Received: from exprod7og61.obsmtp.com ([64.18.2.177])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4iiW-0001ao-VC
	for dhcwg@ietf.org; Sat, 30 Jun 2007 15:35:09 -0400
Received: from source ([81.200.64.181]) (using TLSv1) by
	exprod7ob61.obsmtp.com ([64.18.6.12]) with SMTP; 
	Sat, 30 Jun 2007 12:33:51 PDT
Received: from mail.nominum.com (mail.nominum.com [81.200.64.186])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by shell-ng.nominum.com (Postfix) with ESMTP id 1513256876;
	Sat, 30 Jun 2007 12:33:51 -0700 (PDT)
	(envelope-from Ted.Lemon@nominum.com)
X-Spam-Status: No, hits=0.0 required=8.4
	tests=CUSTOM_RULE_FROM: ALLOW,TOTAL_SCORE: 0.000
X-Spam-Level: 
Received: from [66.93.162.130] ([66.93.162.130])
	(authenticated user mellon@nominum.com) by mail.nominum.com
	(using TLSv1/SSLv3 with cipher AES128-SHA (128 bits));
	Sat, 30 Jun 2007 12:33:48 -0700
In-Reply-To: <4686AD10.2030302@zytor.com>
References: <8E296595B6471A4689555D5D725EBB210461934A@xmb-rtp-20a.amer.cisco.com>
	<4686AD10.2030302@zytor.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <BE3FFF8A-704B-4790-A768-87445D4740B2@nominum.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] DHCPv6 ORO - mandatory?
Date: Sat, 30 Jun 2007 12:33:40 -0700
To: H. Peter Anvin <hpa@zytor.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: dhcwg@ietf.org, "Bernie Volz \(volz\)" <volz@cisco.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Jun 30, 2007, at 12:20 PM, H. Peter Anvin wrote:
> The client SHOULD send the ORO which SHOULD include these options;
> the server MUST return these options regardless of whether or not  
> an ORO is included and whether or not these options are included in  
> the ORO.

Then there's no point in the SHOULD - the server will do the same  
thing no matter what the client does, so there's no need to suggest  
that the client do anything.



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



From dhcwg-bounces@ietf.org Sat Jun 30 15:59:29 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4j6P-00036H-C1; Sat, 30 Jun 2007 15:59:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4j6N-00036C-LG
	for dhcwg@ietf.org; Sat, 30 Jun 2007 15:59:27 -0400
Received: from terminus.zytor.com ([192.83.249.54])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4j5g-0005V5-Bj
	for dhcwg@ietf.org; Sat, 30 Jun 2007 15:59:27 -0400
Received: from titan.hos.anvin.org ([205.233.54.227]) (authenticated bits=0)
	by terminus.zytor.com (8.13.8/8.13.8) with ESMTP id l5UJtVqE026222
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sat, 30 Jun 2007 12:55:32 -0700
Message-ID: <4686B531.7040401@zytor.com>
Date: Sat, 30 Jun 2007 15:55:29 -0400
From: "H. Peter Anvin" <hpa@zytor.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070615)
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] DHCPv6 ORO - mandatory?
References: <8E296595B6471A4689555D5D725EBB210461934A@xmb-rtp-20a.amer.cisco.com>
	<4686AD10.2030302@zytor.com>
	<BE3FFF8A-704B-4790-A768-87445D4740B2@nominum.com>
In-Reply-To: <BE3FFF8A-704B-4790-A768-87445D4740B2@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.88.7/3562/Sat Jun 30 09:36:29 2007 on
	terminus.zytor.com
X-Virus-Status: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: dhcwg@ietf.org, "Bernie Volz \(volz\)" <volz@cisco.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Ted Lemon wrote:
> On Jun 30, 2007, at 12:20 PM, H. Peter Anvin wrote:
>> The client SHOULD send the ORO which SHOULD include these options;
>> the server MUST return these options regardless of whether or not an 
>> ORO is included and whether or not these options are included in the ORO.
> 
> Then there's no point in the SHOULD - the server will do the same thing 
> no matter what the client does, so there's no need to suggest that the 
> client do anything.
> 

... except in the case of bugs in the server (be conservative in what 
you send and all that...)

	-hpa

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



From dhcwg-bounces@ietf.org Sat Jun 30 16:22:33 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4jSi-0007vJ-Jp; Sat, 30 Jun 2007 16:22:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4jSh-0007rl-81
	for dhcwg@ietf.org; Sat, 30 Jun 2007 16:22:31 -0400
Received: from exprod7og57.obsmtp.com ([64.18.2.169])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4jSW-0001gx-7E
	for dhcwg@ietf.org; Sat, 30 Jun 2007 16:22:31 -0400
Received: from source ([81.200.64.181]) (using TLSv1) by
	exprod7ob57.obsmtp.com ([64.18.6.12]) with SMTP; 
	Sat, 30 Jun 2007 13:21:22 PDT
Received: from mail.nominum.com (mail.nominum.com [81.200.64.186])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by shell-ng.nominum.com (Postfix) with ESMTP id AF52F56845;
	Sat, 30 Jun 2007 13:21:22 -0700 (PDT)
	(envelope-from Ted.Lemon@nominum.com)
X-Spam-Status: No, hits=0.0 required=8.4
	tests=CUSTOM_RULE_FROM: ALLOW,TOTAL_SCORE: 0.000
X-Spam-Level: 
Received: from [66.93.162.130] ([66.93.162.130])
	(authenticated user mellon@nominum.com) by mail.nominum.com
	(using TLSv1/SSLv3 with cipher AES128-SHA (128 bits));
	Sat, 30 Jun 2007 13:21:20 -0700
In-Reply-To: <4686B531.7040401@zytor.com>
References: <8E296595B6471A4689555D5D725EBB210461934A@xmb-rtp-20a.amer.cisco.com>
	<4686AD10.2030302@zytor.com>
	<BE3FFF8A-704B-4790-A768-87445D4740B2@nominum.com>
	<4686B531.7040401@zytor.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <73A16C02-0368-41DB-A87A-9C0C80F08075@nominum.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] DHCPv6 ORO - mandatory?
Date: Sat, 30 Jun 2007 13:21:12 -0700
To: H. Peter Anvin <hpa@zytor.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: dhcwg@ietf.org, "Bernie Volz \(volz\)" <volz@cisco.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Jun 30, 2007, at 12:55 PM, H. Peter Anvin wrote:
> ... except in the case of bugs in the server (be conservative in  
> what you send and all that...)

You're mistaking the meaning of being liberal in what you accept and  
conservative in what you send.   What it means is that you should  
always be in compliance when you send stuff.   And you may want  
workarounds in your *implementation* to avoid well-known problems.    
But you do not write the *protocol* this way - this is advice for  
implementors.

And anyway, I think the main point of that admonition was to get  
people to behave well on the IETF mailing lists, not actually advice  
about implementing protocols.   I mean, an IPSEC implementation  
that's liberal about what it accepts isn't going to be very secure,  
is it?   :')



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



