From dhcwg-bounces@ietf.org Tue Jul 03 10:44: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 1I5jbg-0001UL-0g; Tue, 03 Jul 2007 10:43:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I5jbc-0001TZ-J6; Tue, 03 Jul 2007 10:43:52 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I5jbW-0007ZI-RW; Tue, 03 Jul 2007 10:43:52 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 03 Jul 2007 07:43:46 -0700
X-IronPort-AV: i="4.16,492,1175497200"; 
	d="scan'208"; a="176118510:sNHT71788500"
Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l63Ehkg8011410; 
	Tue, 3 Jul 2007 07:43:46 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com
	[171.70.151.144])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l63Ehjvv000004;
	Tue, 3 Jul 2007 14:43:45 GMT
Received: from xmb-sjc-236.amer.cisco.com ([128.107.191.121]) by
	xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 3 Jul 2007 07:43:45 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 3 Jul 2007 07:44:09 -0700
Message-ID: <85B2F271FDF6B949B3672BA5A7BB62FB03F25533@xmb-sjc-236.amer.cisco.com>
In-Reply-To: <C2A90304.482C8%rdroms@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] EXTENDED: mip4 and dhc WG joint last call on
	draft-ietf-mip4-gen-ext-03.txt
Thread-Index: Ace5bY6yzSyTZiVgEdyNKgARJOT6egEEv1oA
From: "Parviz Yegani \(pyegani\)" <pyegani@cisco.com>
To: "Ralph Droms \(rdroms\)" <rdroms@cisco.com>, <mip4@ietf.org>,
	"DHC WG" <dhcwg@ietf.org>
X-OriginalArrivalTime: 03 Jul 2007 14:43:45.0777 (UTC)
	FILETIME=[8F1BB610:01C7BD80]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1912; t=1183473826;
	x=1184337826; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pyegani@cisco.com;
	z=From:=20=22Parviz=20Yegani=20\(pyegani\)=22=20<pyegani@cisco.com>
	|Subject:=20RE=3A=20[Mip4]=20EXTENDED=3A=20mip4=20and=20dhc=20WG=20joint=
	20last=20call=20on=20draft-ietf-mip4-gen-ext-03.txt
	|Sender:=20; bh=y3+vKPqzlfywqZOiHDMm+jo6yYWosTrx0GdsbDpzi10=;
	b=GAf7ljw8xN0/J5G/xf8C/VDeWIKg7GcO3WXaOcaCGsxD2+GlRU8AeMn6HToicIaugU4gsjFE
	qRlKmbz7y5jVNuuOckreeDMWHrWjWXpLzMBa9+x8OyviwGsmKZ+Tw0/s;
Authentication-Results: sj-dkim-3; header.From=pyegani@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: 
Subject: [dhcwg] RE: [Mip4] 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

I support advancing this draft to an RFC.

Rgds,
Parviz=20

-----Original Message-----
From: Ralph Droms (rdroms)=20
Sent: Thursday, June 28, 2007 3:18 AM
To: mip4@ietf.org; DHC WG
Subject: [Mip4] 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



--
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/

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



From dhcwg-bounces@ietf.org Wed Jul 04 06:05: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 1I61k2-0000uH-VY; Wed, 04 Jul 2007 06:05:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I61k1-0000fs-7G
	for dhcwg@ietf.org; Wed, 04 Jul 2007 06:05:45 -0400
Received: from ug-out-1314.google.com ([66.249.92.173])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I61jw-0003Xr-T6
	for dhcwg@ietf.org; Wed, 04 Jul 2007 06:05:45 -0400
Received: by ug-out-1314.google.com with SMTP id u2so717973uge
	for <dhcwg@ietf.org>; Wed, 04 Jul 2007 03:05:40 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;
	b=W30faBadQ5X4oEe3g3YS64eA3vp2apa29Bf76uKojMdOdFAC2clNIiCjveIBtutjN84xO9PMQQXBuMbziTm+4FdVKRPFPk01m32TMaVvuIsXqqawQezEePwM2b34mJSFFHMH3KT/jiXCh2SPpld499zBWiiqMwHcu98mgCrIlCY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=bvje6cpxNMdMUsQns72IKqQln34g/04F9j4ROOaza+afMH9l8NRIJK/5V9Z1z7T/y0m3QPiUJ0Dg+uwaL/Q8hDA1Qzxvw1rncUhDl0aku2Xt1vUAd4mXG4BGpEcz4FxqG9tEqKOujReI2R5mPgHDxCgPsoZMWpgD73RV3Vx3hq0=
Received: by 10.82.156.12 with SMTP id d12mr17490531bue.1183543539840;
	Wed, 04 Jul 2007 03:05:39 -0700 (PDT)
Received: by 10.82.157.9 with HTTP; Wed, 4 Jul 2007 03:05:39 -0700 (PDT)
Message-ID: <fcef11e50707040305r72fd182cv2df0454a0039fcc7@mail.gmail.com>
Date: Wed, 4 Jul 2007 15:35:39 +0530
From: Maverick <maverick.zing@gmail.com>
To: "DHC WG" <dhcwg@ietf.org>
MIME-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Subject: [dhcwg] Issue related to FQDN creation
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="===============0399417994=="
Errors-To: dhcwg-bounces@ietf.org

--===============0399417994==
Content-Type: multipart/alternative; 
	boundary="----=_Part_118437_13609777.1183543539821"

------=_Part_118437_13609777.1183543539821
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi All,
Had a query related to creating a FQDN for the client on the DHCPv6 server.

What is the correct method of creating the FQDN option.
Assuming the client sends the DHCPv6 server just the Machine name, the
server then attaches the domain name information and sends it back to the
client.
The question that now arises is, from where does it get this domain name?
Is it ok to use the Domain Search list option to create the FQDN, if so then
we can have an array of Addresses, which one should be taken?

Or is there any other way it can be done.

Thanks in advance,
Maverick

------=_Part_118437_13609777.1183543539821
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>Hi All,</div>
<div>Had a query related to creating a FQDN for the client on the DHCPv6 server.</div>
<div>&nbsp;</div>
<div>What is the correct method of creating the FQDN option. </div>
<div>Assuming the client sends the DHCPv6 server just the Machine name, the server then attaches the domain name information and sends it back to the client.</div>
<div>The question that now arises is, from where does it get this domain name?</div>
<div>Is it ok to use the Domain Search list option to create the FQDN, if so then we can have an array of Addresses, which one should be taken?</div>
<div>&nbsp;</div>
<div>Or is there any other way it can be done.</div>
<div>&nbsp;</div>
<div>Thanks in advance,</div>
<div>Maverick</div>
<div>&nbsp;</div>

------=_Part_118437_13609777.1183543539821--


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

--===============0399417994==--




From dhcwg-bounces@ietf.org Wed Jul 04 09:23: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 1I64pU-0007wc-N5; Wed, 04 Jul 2007 09:23:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I64pT-0007wX-18
	for dhcwg@ietf.org; Wed, 04 Jul 2007 09:23:35 -0400
Received: from mailout2.samsung.com ([203.254.224.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I64pO-00073d-4s
	for dhcwg@ietf.org; Wed, 04 Jul 2007 09:23:34 -0400
Received: from ep_ms5_bk (mailout2.samsung.com [203.254.224.25])
	by mailout2.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0JKN00CURP727X@mailout2.samsung.com> for dhcwg@ietf.org;
	Wed, 04 Jul 2007 22:23:26 +0900 (KST)
Received: from ep_spt01 (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 <0JKN00HFXP736P@ms5.samsung.com> for dhcwg@ietf.org; Wed,
	04 Jul 2007 22:23:27 +0900 (KST)
Content-return: prohibited
Date: Wed, 04 Jul 2007 13:23:27 +0000 (GMT)
From: Heejin Jang <heejin.jang@samsung.com>
Subject: Re: RE: [dhcwg] EXTENDED: Joint mip6 and dhc WG last call
	ondraft-ietf-mip6-bootstrapping-integrated and draft-ietf-mip6-hiopt
To: "Bernie Volz (volz)" <volz@cisco.com>
Message-id: <1711690.6791183555407751.JavaMail.weblogic@ep_ml28>
MIME-version: 1.0
MIME-version: 1.0
X-Priority: 3
Msgkey: 20070704132327749@heejin.jang
X-MTR: 20070704132327749@heejin.jang
X-EPLocale: ko_KR.windows-1252
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
X-EPApproval-Locale: 
X-Spam-Score: 2.1 (++)
X-Scan-Signature: 0770535483960d190d4a0d020e7060bd
Cc: DHC WG <dhcwg@ietf.org>,
	"athene@sait.samsung.co.kr" <athene@sait.samsung.co.kr>,
	"alper01.yegin@partner.samsung.com" <alper01.yegin@partner.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="===============1548960452=="
Errors-To: dhcwg-bounces@ietf.org

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

SGksIEJlcm5pZS4NClRoYW5rcyBmb3IgeW91ciBvcGluaW9uLg0KDQpQbGVhc2Ugc2VlIHRoZSBp
bmxpbmUuDQoNCi0gUmVnYXJkcywgDQpIZWVqaW4gIA0KDQotLS0tLS0tIE9yaWdpbmFsIE1lc3Nh
Z2UgLS0tLS0tLQ0KU2VuZGVyIDogQmVybmllIFZvbHogKHZvbHopPHZvbHpAY2lzY28uY29tPg0K
RGF0ZSAgIDogMjAwNy0wNi0zMCAwMTozMQ0KVGl0bGUgIDogUkU6IFtkaGN3Z10gRVhURU5ERUQ6
IEpvaW50IG1pcDYgYW5kIGRoYyBXRyBsYXN0IGNhbGwgb25kcmFmdC1pZXRmLW1pcDYtYm9vdHN0
cmFwcGluZy1pbnRlZ3JhdGVkIGFuZCBkcmFmdC1pZXRmLW1pcDYtaGlvcHQNCg0KUmVnYXJkaW5n
DQpodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRmLW1pcDYtaGlv
cHQtMDUudHh0LCBEYXZpZA0KZGlkIGFuIGV4Y2VsbGVudCBhbmQgdGhvcm91Z2ggcmV2aWV3Lg0K
DQpJIHRvbyBoYXZlIG1hbnkgb2YgdGhlIHNhbWUgaXNzdWVzIGFzIERhdmlkLg0KDQoxLiBVc2Ug
b2YgMTYtYml0IHN1Ym9wdGlvbnMgaW4gT1BUSU9OX01JUDYtUkVMQVkgYW5kIE9QVElPTl9NSVA2
LUhOSU5GLg0KVXNpbmcgOC1iaXQgc3Vib3B0aW9ucyBqdXN0IGNvbXBsaWNhdGVzIGltcGxlbWVu
dGF0aW9ucyB0aGF0IG11c3QNCnN1cHBvcnQgdGhpcyBhbmQgcGFja2FnZXMgdGhhdCBkZWNvZGUg
aXQuIEZvciBESENQdjYsIHdlIHJlYWxseSBzaG91bGQNCnN0aWNrIHRvIHVzZSAxNi1iaXQgVExW
IGRhdGEgKkFMTCBUSEUgV0FZKi4gQW5kLCB0aGUgY29zdCBvZiAyIG1vcmUNCmJ5dGVzL3N1Ym9w
dGlvbiBpc24mIzM5O3QgYSBiaWcgZGVhbC4NCg0KQnV0LCBwZXJoYXBzIHRoZXNlIHJlYWxseSBh
cmVuJiMzOTt0IHN1Yi1vcHRpb24gYnV0IGluc3RlYWQgcmFkaXVzIGVuY29kZWQNCmF0dHJpYnV0
ZXMgKCJUaGlzIG9wdGlvbiBjYXJyaWVzIHRoZSBSQURJVVMgb3IgRGlhbWV0ZXIgYXR0cmlidXRl
cyB0aGF0DQphcmUgcmVjZWl2ZWQgYXQgdGhlIE5BUyBmcm9tIHRoZSBBQUFILiIpPyBJbiB0aGF0
IGNhc2UsIHNob3VsZG4mIzM5O3QgdGhlDQpzdWItb3B0aW9ucyBkZXNjcmlwdGlvbiBjbGVhcmx5
IGluZGljYXRlIHRoYXQgYW5kIGJlIHJhZGl1cy1hdHRyaWJ1dGVzDQpvciBzb21ldGhpbmcgbGlr
ZSB0aGF0LiBJdCBpcyBDUklUSUNBTCB0byBub3RlIHRoYXQgZm9yIHJhZGl1cw0KYXR0cmlidXRl
cywgdGhlIEwgZmllbGQgaW4gdGhlIFRMViAqaW5jbHVkZXMqIHRoZSBMIGZpZWxkICh3aGljaCBp
cyBub3QNCnRoZSBjYXNlIGZvciBESENQIG9wdGlvbnMhKS4NCg0KQnV0LCB0aGVuICIzLjIuMS4g
IE1JUDYgUmVsYXkgQWdlbnQgU3ViLW9wdGlvbiIgbGlzdHMgdGhlc2Ugc3Vib3B0aW9ucw0Kd2hp
Y2ggY2xlYXJseSBhcmUgbm90IHRoZSByYWRpdXMgZW5jb2RlIGF0dHJpYnV0ZXMuDQoNCkhlZWpp
bj4+ICBJdCAgY2Fubm90IGJlIGFzc3VtZWQgdGhhdCBhIG1vYmlsZSBub2RlIG9yIGEgREhDUCBz
ZXJ2ZXIgaGF2ZSANCmFiaWxpdHkgdG8gZGVjb2RlIHJhZGl1cy1lbmNvZGVkIGF0dHJpYnV0ZXMu
IFRoZW4gdGhlIHJhZGl1cy1lbmNvZGVkIGF0dHJpYnV0ZXMgDQoocmVjZWl2ZWQgZnJvbSBBQUEg
c2VydmVyKSBuZWVkIHRvIGJlIHJlLWZvcm1hdHRlZCBpbnRvIGRoY3Agb3B0aW9ucyBhdCBhIE5B
Uw0KKD1ESENQIHJlbGF5L1JhZGl1cyBjbGllbnQpIGJlZm9yZSBkZWxpdmVyaW5nIHRoZW0gdG8g
dGhlIG1vYmlsZSBub2RlLg0KVGhlcmVmb3JlLCB0aGUgcHJvcG9zZWQgc3ViLW9wdGlvbnMgYXJl
IG5vdCByYWRpdXMtZW5jb2RlZCBhdHRyaWJ1dGVzIGJ1dCANCmRoY3Agc3ViLW9wdGlvbnMuIFdl
J2xsIGFkZCB0aGlzIGRlc2NyaXB0aW9uIGluIHNlY3Rpb24gNC4yLg0KDQoyLiBEbyBub3QgdXNl
IHN1Ym9wdGlvbiAwLiBBbGwgb3RoZXIgc3ViLW9wdGlvbnMgdGhhdCBJJiMzOTttIGF3YXJlIG9m
DQphbHdheXMgc3RhcnQgbnVtYmVyaW5nIGF0IDEgYW5kIHlvdSYjMzk7cmUganVzdCBhc2tpbmcg
Zm9yIHRyb3VibGUgd2l0aA0KaW1wbGVtZW50YXRpb25zIChhcHBhcmVudGx5IHN1Y2ggYXMgSVND
JiMzOTtzKSB0aGF0IGFzc3VtZSAwIGlzIG5vdCAidmFsaWQiLg0KV2UgYWxzbyBoYXZlIGNvZGUg
dGhhdCB3b3VsZCBicmVhayBpZiBzdWItb3B0aW9uIDAgaXMgdXNlZCBpbiBvdXIgc2VydmVyDQoo
dGhvdWdoIGZvciBhIGNvbXBsZXRlbHkgZGlmZmVyZW50IHJlYXNvbiB0aGFuIHRoZSBJU0MgaXNz
dWUpLg0KDQpXaGlsZSB5b3UgY2FuIGFyZ3VlIHRoYXQgYW55IHN1Ym9wdGlvbiB2YWx1ZSBzaG91
bGQgYmUgdmFsaWQsIHRoYXQgaXNuJiMzOTt0DQp0aGUgaXNzdWUuIElmIHlvdSB3YW50IHRoZXNl
IG9wdGlvbnMgc3VwcG9ydGVkIGJ5IGltcGxlbWVudGF0aW9ucywNCmV2ZXJ5dGhpbmcgeW91IGNh
biBkbyB0byBtYWtlIHRoYXQgZWFzeSB0byBkbyAoYnkgZm9sbG93aW5nIGV4aXN0aW5nDQpjb252
ZW50aW9ucykgd2lsbCBtYWtlIGl0IHRoYXQgbXVjaCBlYXNpZXIgZm9yIHRoZSBzdXBwb3J0IHRv
IGJlIGFkZGVkLg0KSWYgYSBsb3Qgb2YgY29kZSBuZWVkcyB0byBiZSByZXdvcmtlZCBhbmQgcmV0
ZXN0ZWQsIHlvdSYjMzk7cmUgbm90IGFzIGxpa2VseQ0KdG8gZ2V0IHRoZSBvcHRpb25zIGRlcGxv
eWVkLg0KDQpIZWVqaW4+PiBSaWdodC4gdGhpcyBjb21tZW50IHdhcyByZWZsZWN0ZWQgYXMgSSBy
ZXBsaWVkIHRvIERhdmlkJ3MgbWFpbC4NCg0KW1RoZSByZW1haW5pbmcgY29tbWVudHMgYXJlIHBy
b2JhYmx5IG1vcmUgYmVjYXVzZSBvZiBteSBpZ25vcmFuY2Ugb2YNCnRoaXMgc29sdXRpb24gYXMg
SSBoYXZlbiYjMzk7dCBrZXB0IHVwIHdpdGggdGhlIE1JUDYgd29yay5dDQoNCjMuIElzIHRoZXJl
IGEgbmVlZCB0byBlc3RhYmxpc2ggYSByZWdpc3RyeSBmb3IgaWQtdHlwZSBpbiB0aGVzZSBvcHRp
b25zLA0Kb3IgZG9lcyB0aGlzIGFscmVhZHkgZXhpc3Qgc29tZXdoZXJlIGVsc2UgaW4gdGhlIE1J
UDYgc3BhY2U/IElmIGl0IGRvZXMNCmV4aXN0IGVsc2V3aGVyZSwgaG93IGFib3V0IHJlZmVyZW5j
aW5nIHRoYXQ/IA0KDQpJZiB0aGVzZSBhcmUgbmV3bHkgYXNzaWduZWQgdmFsdWVzLCB3b3VsZG4m
IzM5O3QgdXNpbmcgMCBmb3Igbm8tcHJlZmVyZW5jZQ0KbWFrZSBtb3JlIHNlbnNlPw0KDQpIZWVq
aW4+PiBUaGUgdHdvIG9wdGlvbnMgYXJlIG5ldyBvcHRpb25zIGFuZCBpdCBpcyBkZXNjcmliZWQg
aW4gc2VjdGlvbiBvZiBJQU5BIA0KY29uc2lkZXJhdGlvbi4gQWJvdXQgdXNpbmcgMiBmb3Igbm8t
cHJlZmVyZW5jZSwgdGhlIHJlYXNvbiBpcyB0aGF0ICduby1wcmVmZXJlbmNlJw0Kd2FzIGRlZmlu
ZWQgYWZ0ZXIgdGhlIGlkLXR5cGUgMCBhbmQgMS4gSG93ZXZlciwgYXMgeW91IHN1Z2dlc3RlZCwg
dGhlIHVzZSBvZiAwIHNlZW1zIA0KYmV0dGVyIGZvciBmdXR1cmUgZXh0ZW5zaW9uLiBXZSdsbCBy
ZWZsZWN0IHRoaXMuDQoNCjQuIElzIHRoZXJlIGEgbmVlZCB0byBlc3RhYmxpc2ggYSByZWdpc3Ry
eSBmb3IgdGhlIHN1Ym9wdGlvbnMgZm9yIHRoZXNlDQpvcHRpb25zPw0KDQpIZWVqaW4+PiBXZSds
bCBhZGQgc29tZSBkZXNjcmlwdGlvbiBhbHNvIGZvciBzdWItb3B0aW9ucyBpbiBJQU5BIGNvbnNp
ZGVyYXRpb24gc2VjdGlvbi4NCg0KNS4gSG9tZSBOZXR3b3JrIElkZW50aWZpZXIgZmllbGQ6DQoN
Ci0gIkluIHRoaXMgY2FzZSwgdGhlIEhvbWUgTmV0d29yayBJZGVudGlmaWVyIGZpZWxkIFNIT1VM
RCBiZSBzZXQgdG8gMC4iDQpEb24mIzM5O3QgeW91IG1lYW4gdGhhdCBpdCBzaG91bGQgbm90IGJl
IHByZXNlbnQ/IChJRSwgb3B0aW9uIGxlbmd0aCBzaG91bGQNCmJlIDIgYW5kIGp1c3QgaGF2ZSB0
aGUgaWQtdHlwZSBhbmQgcmVzZXJ2ZWQgYnl0ZXM/KQ0KDQotIEl0IG1pZ2h0IGJlIHVzZWZ1bCB0
byBpbmRpY2F0ZSB0aGF0IHRoaXMgSG9tZSBOZXR3b3JrIElkZW50aWZpZXIgZmllbGQNCmRvZXMg
Tk9UIGluY2x1ZGUgYSBudWxsIGJ5dGUgdG8gdGVybWluYXRlIHRoZSBzdHJpbmc/IE9yLCBwZXJo
YXBzIHRoaXMNCnNob3VsZCBhbHdheXMgYmUgbnVsbCB0ZXJtaW5hdGVkIGFuZCBoZW5jZSB3aHkg
eW91IHNheSAiU0hPVUxEIGJlIHNldCB0bw0KMCI/DQoNCkhlZWppbj4+IE5vLiBBbiBITiBpZGVu
dGlmaWVyIGZpZWxkIGV4aXN0cyBhbHdheXMsIGJ1dCBTSE9VTEQgYmUgaW5pdGlhbGl6ZWQgdG8g
MCANCihzdWNoIGFzIGEgcmVzZXJ2ZWQgZmllbGQpIHdoZW4gdGhlIGlkLXR5cGUgPSAwICYgMi4g
VGhlcmVmb3JlLCB0aGUgMCBpcyBub3QgTlVMTCANCmNoYXJhY3RlciAoYXNjaWkgMCkgYnV0IGlu
dGVnZXIgMCAoYXNjaWkgNDgpLiBJIHRoaW5rIHRoZXJlIGlzIG5vIGFtYmlndWl0eSBoZXJlLg0K
DQpCb3R0b20gbGluZSwgSSBhZ3JlZSB3aXRoIERhdmlkIHRoYXQgd2UgU0hPVUxEIE5PVCBhZHZh
bmNlIHRoaXMgZHJhZnQgYXQNCnRoaXMgdGltZS4gSXQgc3RpbGwgbmVlZHMgd29yay4NCg0KSGVl
amluPj4gQW55d2F5LCB0aGFua3MgZm9yIHlvdXIgaGVscGZ1bCBjb21tZW50cyB3aGljaCB3aWxs
IG1ha2UgdGhlIGRyYWZ0IGNvbXBsZXRlLiA6KQ0KDQotIEJlcm5pZQ0KDQotLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLQ0KRnJvbTogRGF2aWQgVy4gSGFua2lucyBbbWFpbHRvOkRhdmlkX0hhbmtp
bnNAaXNjLm9yZ10gDQpTZW50OiBNb25kYXksIEp1bmUgMjUsIDIwMDcgMjo0OCBQTQ0KVG86IERI
QyBXRw0KU3ViamVjdDogUmU6IFtkaGN3Z10gRVhURU5ERUQ6IEpvaW50IG1pcDYgYW5kIGRoYyBX
RyBsYXN0IGNhbGwNCm9uZHJhZnQtaWV0Zi1taXA2LWJvb3RzdHJhcHBpbmctaW50ZWdyYXRlZCBh
bmQgZHJhZnQtaWV0Zi1taXA2LWhpb3B0DQoNCk9uIE1vbiwgSnVuIDI1LCAyMDA3IGF0IDEwOjQz
OjEyQU0gLTA0MDAsIFJhbHBoIERyb21zIHdyb3RlOg0KPiBUaGVyZSBoYXMgYmVlbiBubyByZXNw
b25zZSB0byB0aGlzIFdHIGxhc3QgY2FsbCwgc28gdGhlIGRlYWRsaW5lIHdpbGwNCmJlDQo+IGV4
dGVuZGVkIHRvIDE3MDBFRFQsIDA3LzAyLzA3Lg0KDQpNeSBleGN1c2UgaXMgdGhhdCBJIHdhcyBp
biBBbGFza2EuDQoNCj4NCmh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0
LWlldGYtbWlwNi1ib290c3RyYXBwaW5nLWludGVncg0KYXRlZA0KPiAtMDQudHh0DQoNCkNvcnJl
Y3Rpb24gKEkgdGhpbms/KToNCg0KIA0KaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFm
dHMvZHJhZnQtaWV0Zi1taXA2LWJvb3RzdHJhcHBpbmctaW50ZWdyDQphdGVkLWRoYy0wNC50eHQN
Cg0KSSBhY3R1YWxseSBkb24mIzM5O3Qgc2VlIGEgbG90IGluIHRoZXJlIGZvciBESENXRyB0byBy
ZXZpZXcuICBNYXliZSBJJiMzOTttDQpub3QgbG9va2luZyBoYXJkIGVub3VnaD8NCg0KSSBhbSBh
IGxpdHRsZSBjb25jZXJuZWQgKGJ1dCBvbmx5IGEgbGl0dGxlKSBhdCB0aGUgZXh0ZW50IHRvIHdo
aWNoDQppdCBkZWZpbmVzIHNpbXBsaWZpZWQgUkZDMzMxNSBiZWhhdmlvdXIgKCJzdW1tYXJpemlu
ZyIgdGhlIHByb2Nlc3MNCmluIHdoaWNoIGEgY2xpZW50IGlzIGlkZW50aWZpZWQgYW5kIGNvbmZp
Z3VyZWQpLg0KDQoNCiAgICgzKSBUaGUgUmVsYXkgQWdlbnQgaW50ZXJjZXB0cyB0aGUgSW5mb3Jt
YXRpb24gUmVxdWVzdCBmcm9tIHRoZQ0KDQpJIHRoaW5rICJyZWNlaXZlcyIgaXMgYSBiZXR0ZXIg
d29yZCwgY29uc2lkZXJpbmcgdGhhdCB0aGUgcGFja2V0IGlzDQp0cmFuc21pdHRlZCB0byBhIG11
bHRpY2FzdCBhZGRyZXNzLiAgImludGVyY2VwdCIgaGFzIG1vcmUgb2YgYW4NCmluc2ludWF0aW9u
IHRoYXQgdGhlIHJlbGF5IHdvdWxkIG5vdCBub3JtYWxseSByZWNlaXZlIHRoZSBwYWNrZXQuDQoN
Cg0KU28gSSBzZWUgbm8gcHJvYmxlbSBhZHZhbmNpbmcgdGhpcyBkcmFmdCB0byB0aGUgSUVTRy4N
Cg0KDQo+IGFuZCBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRm
LW1pcDYtaGlvcHQtMDUudHh0DQoNCklTQyBESENQIGFuZCBvdGhlcnMgc2hhcmUgb3B0aW9uIHBy
b2Nlc3NpbmcgY29kZSBiZXR3ZWVuIHRoZSB2NA0KYW5kIHY2IHNpZGUgb2YgdGhlIGhvdXNlLiAg
SSBkb24mIzM5O3Qga25vdyBhYm91dCB0aGUgb3RoZXJzLCBidXQgdGhlDQpuZXQgZWZmZWN0IGZv
ciBJU0MgREhDUCBpcyB0aGF0IGNvZGUgMCBpcyB0cmVhdGVkIGFzIGFuICJlbmQgdGFnIg0KKGNv
ZGUgMjU1LCBvciAiY29kZSBhbGwgb25lcyIgZm9yIGFueSBjb2RlIHdpZHRoLCBpcyBub3QpLiAg
VGhpcw0Kc291bmRzIGEgbGl0dGxlIHdlaXJkLCBidXQgdGhhdCYjMzk7cyB0aGUgY29udHJpdmFu
Y2Ugb2YgdGhlIGxvb3Agd2UNCnNlbGVjdGVkLg0KDQpJZiB0aGUgc3ViLW9wdGlvbnMgY291bGQg
YmUgbnVtYmVyZWQgZnJvbSAxLCB0aGVuIHRoaXMgZHJhZnQgd291bGQNCmJlIGNvbXBhdGlibGUg
d2l0aCBvdXIgY3VycmVudGx5IHJlbGVhc2VkIGFscGhhLg0KDQpJZiBub3QsIHRoZW4gaXQgd291
bGQgdGFrZSBuZXcgY29kZSwgYWRkaW5nIG1vcmUgYnJhbmNoZXMgYmV0d2Vlbg0KZWFjaCBydW4g
b2YgdGhlIG9wdGlvbiBwcm9jZXNzaW5nIGxvb3AuDQoNCg0KSSBub3RlIGFsc28gdGhhdCB0aGUg
c3ViLW9wdGlvbiBjb2RlcyBhcmUgOC1iaXQgY29kZS9sZW5ndGggcGFpcnMuDQpUaGF0IGRvZXNu
JiMzOTt0IGFmZmVjdCBJU0MgREhDUCwgYnV0IEkgd2FudGVkIHRvIHBvaW50IGl0IG91dCBmb3Ig
b3RoZXINCmltcGxlbWVudG9ycy4NCg0KSSB0aGluayB0aGlzIGlzIHRoZSBmaXJzdCB0aW1lIHdl
JiMzOTt2ZSBzZWVuIG5vbi0xNi1iaXQgY29kZS9sZW5ndGhzDQppbnNpZGUgREhDUHY2Pw0KDQoN
CiAgIElmIHRoZSByZXF1ZXN0IG1lc3NhZ2UgY2FycmllcyBtb3JlIHRoYW4gb25lIEhvbWUgTmV0
d29yayBJZGVudGlmaWVyDQogICBvcHRpb25zLCB0aGUgcmVwbHkgbWVzc2FnZSBNVVNUIGNvbnRh
aW4gSG9tZSBOZXR3b3JrIEluZm9ybWF0aW9uDQogICBvcHRpb25zIGFzIG1hbnkgYXMgSG9tZSBO
ZXR3b3JrIElkZW50aWZpZXIgb3B0aW9ucyBpbiB0aGUgcmVxdWVzdC4NCg0KSSB0aGluayAmIzM5
O2FzIG1hbnkmIzM5OyB3YW50cyB0byBiZSBtb3ZlZCBsZWZ0IDQgd29yZHMgb3Igc28uDQoNClNl
Y29uZCwgSSB0aGluayBNVVNUIGlzIHRvbyBzdHJvbmcsIHNpbmNlIGlmIHRoZSBESENQIHNlcnZl
ciBpcyBub3QNCmNvbmZpZ3VyZWQgd2l0aCB2YWx1ZXMsIGl0IHdpbGwgYmUgdW5hYmxlIHRvIHJl
cGx5LiAgQ29uc2lkZXINCnNwZWNpZmljYWxseSBzZXJ2ZXIgc29mdHdhcmUgdGhhdCBkb2VzIG5v
dCAoeWV0KSBoYXZlIHN1cHBvcnQgZm9yDQp0aGVzZSBvcHRpb25zIC0gdGhleSB3aWxsIGNlcnRh
aW5seSBoYXZlIG5vIGNvZGUgd2hpY2ggZW5mb3JjZXMgdGhlDQpjb25zdHJ1Y3Rpb24gb2YgJiMz
OTtlbXB0eSYjMzk7IG9wdGlvbnMuDQoNCg0KICAgVGhlDQogICBIb21lIE5ldHdvcmsgSW5mb3Jt
YXRpb24gb3B0aW9ucyBpbiB0aGUgcmVwbHkgU0hPVUxEIGFwcGVhciBpbiB0aGUNCiAgIHNhbWUg
b3JkZXIgYXMgSG9tZSBOZXR3b3JrIElkZW50aWZpZXIgb3B0aW9ucyBpbiB0aGUgcmVxdWVzdCBh
bmQgdGhlDQogICBtYXRjaGluZyBpcyBiYXNlZCBvbiB0aGUgc2VxdWVudGlhbCBvcmRlciBvZiBv
cHRpb25zLiAgVGhpcyBwcm92aWRlcw0KICAgYSB3YXkgb2YgbWF0Y2hpbmcgZm9yIEhvbWUgTmV0
d29yayBJbmZvcm1hdGlvbiBvcHRpb25zIHdpdGggdGhlIHNhbWUNCiAgIGlkLXR5cGUuDQoNCkkg
ZG9uJiMzOTt0IGdldCBpdC4gIFRoZSBvcHRpb25zIFNIT1VMRCBwcGVhciBpbiB0aGUgc2FtZSBv
cmRlciwgd2hpY2gNCm1lYW5zIHRoZXkgbWlnaHQgbm90LCBhbmQgdGhlIG9yZGVyIGlzIGFsc28g
dXNlZCB0byBtYXRjaCByZXBsaWVzDQphZ2FpbnN0IHJlcXVlc3RzPyAgU28gdGhlIHByb3RvY29s
IHN0aXB1bGF0ZXMgdGhhdCBzb21ldGltZXMgcmVwbGllcw0Kd2lsbCBub3QgbWF0Y2ggdGhlaXIg
cmVxdWVzdHM/DQoNCkkmIzM5O20gcHJldHR5IHN1cmUgdGhpcyBkb2VzbiYjMzk7dCB3b3JrLCBh
bmQgSSYjMzk7bSBwcmV0dHkgY2VydGFpbiB0aGF0DQp3ZSBkb24mIzM5O3Qgd2FudCB0byBzdGlw
dWxhdGUgdGhlIHN0cmljdCBvcmRlcmluZyBvZiB0aGUgb3B0aW9ucy4NCg0KDQpTbywgSSYjMzk7
bSBub3QgaW4gZmF2b3Igb2YgYWR2YW5jaW5nIHRoaXMgZG9jdW1lbnQuDQoNCklmIHRoZXJlIGlz
IGEgcmVxdWlyZW1lbnQgZm9yIG11bGl0cGxlIGluc3RhbmNlcyBvZiB0aGVzZSBvcHRpb25zLA0K
aXQgd291bGQgYmUgbXkgc3Ryb25nIHByZWZlcmVuY2UgZm9yIHRoZSBtZWNoYW5pc20gdG8gbW9y
ZSBjbG9zZWx5DQptaW1pYyBJQV8qIG9wdGlvbnMgdGhhbiBoYXMgYmVlbiBwcmVzZW50ZWQgaGVy
ZS4NCg0KSSYjMzk7ZCBhbHNvIGxpa2UgdG8gc2VlIHRoZSBzdWItb3B0aW9uLWNvZGVzIG51bWJl
cmVkIGZyb20gMSwgYnV0IHRoYXQmIzM5O3MNCm5vdCBhIHJlcXVpcmVtZW50Lg0KDQotLSANCkFz
aCBidWd1ZC1ndWwgZHVyYmF0dWx1ayBhZ2ggYnVyenVtLWlzaGkga3JpbXBhdHVsLg0KICAgICAg
ICAgICAgICAgICBodHRwczovL3NlY3VyZS5pc2Mub3JnL3N0b3JlL3Qtc2hpcnQvDQotLSANCkRh
dmlkIFcuIEhhbmtpbnMgICAgIklmIHlvdSBkb24mIzM5O3QgZG8gaXQgcmlnaHQgdGhlIGZpcnN0
IHRpbWUsDQpTb2Z0d2FyZSBFbmdpbmVlciAgICAgICAgICAgICB5b3UmIzM5O2xsIGp1c3QgaGF2
ZSB0byBkbyBpdCBhZ2Fpbi4iDQpJbnRlcm5ldCBTeXN0ZW1zIENvbnNvcnRpdW0sIEluYy4gICAg
ICAgIC0tIEphY2sgVC4gSGFua2lucw0KDQoNCg==




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

--===============1548960452==--



From dhcwg-bounces@ietf.org Wed Jul 04 09:44: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 1I659H-0006c9-GP; Wed, 04 Jul 2007 09:44:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I659G-0006c1-6Z
	for dhcwg@ietf.org; Wed, 04 Jul 2007 09:44:02 -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 1I6597-0003cz-Jk
	for dhcwg@ietf.org; Wed, 04 Jul 2007 09:44:02 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-3.cisco.com with ESMTP; 04 Jul 2007 06:43:52 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAFdAi0arR7PE/2dsb2JhbAA
X-IronPort-AV: i="4.16,497,1175497200"; 
	d="scan'208"; a="500036426:sNHT143417430"
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 l64DhqPx007416; 
	Wed, 4 Jul 2007 06:43:52 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l64DhPmq019992;
	Wed, 4 Jul 2007 13:43:41 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); 
	Wed, 4 Jul 2007 09:43:30 -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: RE: [dhcwg] EXTENDED: Joint mip6 and dhc WG last call
	ondraft-ietf-mip6-bootstrapping-integrated and draft-ietf-mip6-hiopt
Date: Wed, 4 Jul 2007 09:43:38 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB21046AFD70@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <1711690.6791183555407751.JavaMail.weblogic@ep_ml28>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RE: [dhcwg] EXTENDED: Joint mip6 and dhc WG last call
	ondraft-ietf-mip6-bootstrapping-integrated and
	draft-ietf-mip6-hiopt
thread-index: Ace+Poa/aDHedzqYQgS4ZpRhNlQPfgAAFouw
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: <heejin.jang@samsung.com>
X-OriginalArrivalTime: 04 Jul 2007 13:43:30.0969 (UTC)
	FILETIME=[4EED8890:01C7BE41]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=10647; t=1183556632;
	x=1184420632; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=volz@cisco.com;
	z=From:=20=22Bernie=20Volz=20\(volz\)=22=20<volz@cisco.com>
	|Subject:=20RE=3A=20RE=3A=20[dhcwg]=20EXTENDED=3A=20Joint=20mip6=20and=20
	dhc=20WG=20last=20call=20ondraft-ietf-mip6-bootstrapping-integrated=20and=
	20draft-ietf-mip6-hiopt |Sender:=20;
	bh=j0KdHGeYYCgnxTniUui/XE4YIvz4gpVVQVpM0XYHnx8=;
	b=C4A8KYviioQoN7Q71jM5nUQq+wIlKCYWhuGV5iRkmtzErgmuCwa28CdnR/xJJrfzL3nnxQBc
	Ir2q8hNosUIguYr/MfNYm1W347YA9Ta0RbslJPyNaIS0mB7jMzLV0M7L;
Authentication-Results: sj-dkim-4; header.From=volz@cisco.com; dkim=pass (si
	g from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fe105289edd72640d9f392da880eefa2
Cc: DHC WG <dhcwg@ietf.org>, athene@sait.samsung.co.kr,
	alper01.yegin@partner.samsung.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

>Heejin>> No. An HN identifier field exists always, but SHOULD be
initialized to 0=20
>(such as a reserved field) when the id-type =3D 0 & 2. Therefore, the 0
is not NULL=20
>character (ascii 0) but integer 0 (ascii 48). I think there is no
ambiguity here.=20

Wow, that better be made clear as that certainly wasn't to me. Perhaps
it is obvious if you know MIP6, but you should add this clarification.
I'd suggest:

"In this case, the Home Network Identifier field SHOULD be set to a 1
character string containing the 0 character (ASCII 48)."

Also, what is the rational behind this as I don't see "0" mentioned as
being special in RFC 4282?

I think you should provide the rational for this usage as it is a bit
atypical for DHCP -- in this case, the option length is available and
could be set to 2 to mean that no HN identifier field exists and that
would be, IMHO, much cleaner than using a magic string of "0".

---

Regarding section 3.2:

3.2.  MIP6 Relay Agent Option

   This option carries the RADIUS or Diameter attributes that are
   received at the NAS from the AAAH.  The DHCP relay agent sends this
   option to the DHCP server in the Relay-Forward message.

This option really doesn't carry RADIUS or Diameter attributes. It
carries one (or more?) of the sub-options specified in 3.2.1. Though
likely these sub-options are derived from RADIUS or Diameter attributes.

- Bernie

-----Original Message-----
From: Heejin Jang [mailto:heejin.jang@samsung.com]=20
Sent: Wednesday, July 04, 2007 9:23 AM
To: Bernie Volz (volz)
Cc: DHC WG; alper01.yegin@partner.samsung.com;
kchowdhury@starentnetworks.com; athene@sait.samsung.co.kr; David W.
Hankins
Subject: Re: RE: [dhcwg] EXTENDED: Joint mip6 and dhc WG last call
ondraft-ietf-mip6-bootstrapping-integrated and draft-ietf-mip6-hiopt

Hi, Bernie.
Thanks for your opinion.

Please see the inline.

- Regards,=20
Heejin =20

------- Original Message -------
Sender : Bernie Volz (volz)<volz@cisco.com>
Date   : 2007-06-30 01:31
Title  : 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&#39;t a big deal.

But, perhaps these really aren&#39;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&#39;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.

Heejin>>  It  cannot be assumed that a mobile node or a DHCP server have

ability to decode radius-encoded attributes. Then the radius-encoded
attributes=20
(received from AAA server) need to be re-formatted into dhcp options at
a NAS
(=3DDHCP relay/Radius client) before delivering them to the mobile node.
Therefore, the proposed sub-options are not radius-encoded attributes
but=20
dhcp sub-options. We'll add this description in section 4.2.

2. Do not use suboption 0. All other sub-options that I&#39;m aware of
always start numbering at 1 and you&#39;re just asking for trouble with
implementations (apparently such as ISC&#39;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&#39;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&#39;re not as
likely
to get the options deployed.

Heejin>> Right. this comment was reflected as I replied to David's mail.

[The remaining comments are probably more because of my ignorance of
this solution as I haven&#39;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&#39;t using 0 for
no-preference
make more sense?

Heejin>> The two options are new options and it is described in section
of IANA=20
consideration. About using 2 for no-preference, the reason is that
'no-preference'
was defined after the id-type 0 and 1. However, as you suggested, the
use of 0 seems=20
better for future extension. We'll reflect this.

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

Heejin>> We'll add some description also for sub-options in IANA
consideration section.

5. Home Network Identifier field:

- "In this case, the Home Network Identifier field SHOULD be set to 0."
Don&#39;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"?

Heejin>> No. An HN identifier field exists always, but SHOULD be
initialized to 0=20
(such as a reserved field) when the id-type =3D 0 & 2. Therefore, the 0 =
is
not NULL=20
character (ascii 0) but integer 0 (ascii 48). I think there is no
ambiguity here.

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

Heejin>> Anyway, thanks for your helpful comments which will make the
draft complete. :)

- 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&#39;t see a lot in there for DHCWG to review.  Maybe
I&#39;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&#39;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&#39;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&#39;t affect ISC DHCP, but I wanted to point it out for other
implementors.

I think this is the first time we&#39;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 &#39;as many&#39; 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 &#39;empty&#39; 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&#39;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&#39;m pretty sure this doesn&#39;t work, and I&#39;m pretty certain
that
we don&#39;t want to stipulate the strict ordering of the options.


So, I&#39;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&#39;d also like to see the sub-option-codes numbered from 1, but
that&#39;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&#39;t do it right the first time,
Software Engineer             you&#39;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 Wed Jul 04 13:40: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 1I68qC-0004PE-48; Wed, 04 Jul 2007 13:40:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I68qB-0004NS-65
	for dhcwg@ietf.org; Wed, 04 Jul 2007 13:40:35 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I68q3-0007EO-Ov
	for dhcwg@ietf.org; Wed, 04 Jul 2007 13:40:35 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 04 Jul 2007 13:40:27 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AusRAJp3i0ZAZnme/2dsb2JhbAATglCaWw
X-IronPort-AV: i="4.16,498,1175486400"; 
	d="scan'208,217"; a="64348173:sNHT56500572"
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 l64HePJc031635; 
	Wed, 4 Jul 2007 13:40:25 -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 l64He4sE022429; 
	Wed, 4 Jul 2007 17:40:25 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); 
	Wed, 4 Jul 2007 13:40:24 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [dhcwg] Issue related to FQDN creation
Date: Wed, 4 Jul 2007 13:40:24 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB21046AFDAC@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <fcef11e50707040305r72fd182cv2df0454a0039fcc7@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Issue related to FQDN creation
thread-index: Ace+Iu+x/qKnSelJQkKh5NLOtZM2CwAPw4uQ
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "Maverick" <maverick.zing@gmail.com>, "DHC WG" <dhcwg@ietf.org>
X-OriginalArrivalTime: 04 Jul 2007 17:40:24.0187 (UTC)
	FILETIME=[66AA7CB0:01C7BE62]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4770; t=1183570825;
	x=1184434825; 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]=20Issue=20related=20to=20FQDN=20creation
	|Sender:=20 |To:=20=22Maverick=22=20<maverick.zing@gmail.com>,
	=20=22DHC=20WG=22=20<dh cwg@ietf.org>;
	bh=KHQxN6WzLkOm/hOx7wPJYW4Y16psB3akpLE1kt1SCtk=;
	b=A0QBMyU/U/bvZw043YnBc3FG+THFb48qCFSq8II7+/GXjS7wG/arTf97X2HgjSldPN5LAQKv
	iCs4SU0fVWN6EQ5GmH5K57z1kTPi1knDJWiP1FN/GYn6GPI3rcXbNMq4;
Authentication-Results: rtp-dkim-1; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
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>
Content-Type: multipart/mixed; boundary="===============0506210396=="
Errors-To: dhcwg-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0506210396==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7BE62.667569B9"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7BE62.667569B9
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

No, I would NOT use the domain search list option. While the domain name
is likely to be in this list, you can't assume this.
=20
If the DHCPv6 server is going to be doing DNS updates for the client
(which this model assumes), it likely needs to be configured with
information about doing those updates (as typically TSIG keys are
needed, which might be zone specific, etc.).
=20
Thus, I would assume that the DHCPv6 server gets it from other
configuration information it has specific to performing DNS updates.
This is what our server does for both DHCPv4 and DHCPv6 (and has been
doing so for years for DHCPv4).
=20
- Bernie

________________________________

From: Maverick [mailto:maverick.zing@gmail.com]=20
Sent: Wednesday, July 04, 2007 6:06 AM
To: DHC WG
Subject: [dhcwg] Issue related to FQDN creation


Hi All,
Had a query related to creating a FQDN for the client on the DHCPv6
server.
=20
What is the correct method of creating the FQDN option.=20
Assuming the client sends the DHCPv6 server just the Machine name, the
server then attaches the domain name information and sends it back to
the client.
The question that now arises is, from where does it get this domain
name?
Is it ok to use the Domain Search list option to create the FQDN, if so
then we can have an array of Addresses, which one should be taken?
=20
Or is there any other way it can be done.
=20
Thanks in advance,
Maverick
=20

------_=_NextPart_001_01C7BE62.667569B9
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3132" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D401283717-04072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>No, I would NOT use the domain search list =
option. While=20
the domain name is likely to be in this list, you can't assume=20
this.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D401283717-04072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D401283717-04072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>If the DHCPv6 server is going to be doing DNS =
updates for=20
the client (which this model assumes), it likely needs to be configured =
with=20
information about doing those updates (as typically TSIG keys are =
needed, which=20
might be zone specific, etc.).</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D401283717-04072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D401283717-04072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Thus, I would assume that the DHCPv6 server =
gets it from=20
other configuration information it has specific to performing DNS =
updates. This=20
is what our server does for both DHCPv4 and DHCPv6 (and has been doing =
so for=20
years for DHCPv4).</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D401283717-04072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D401283717-04072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>- Bernie</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Maverick =
[mailto:maverick.zing@gmail.com]=20
<BR><B>Sent:</B> Wednesday, July 04, 2007 6:06 AM<BR><B>To:</B> DHC=20
WG<BR><B>Subject:</B> [dhcwg] Issue related to FQDN=20
creation<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Hi All,</DIV>
<DIV>Had a query related to creating a FQDN for the client on the DHCPv6 =

server.</DIV>
<DIV>&nbsp;</DIV>
<DIV>What is the correct method of creating the FQDN option. </DIV>
<DIV>Assuming the client sends the DHCPv6 server just the Machine name, =
the=20
server then attaches the domain name information and sends it back to =
the=20
client.</DIV>
<DIV>The question that now arises is, from where does it get this domain =

name?</DIV>
<DIV>Is it ok to use the Domain Search list option to create the FQDN, =
if so=20
then we can have an array of Addresses, which one should be taken?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Or is there any other way it can be done.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks in advance,</DIV>
<DIV>Maverick</DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_001_01C7BE62.667569B9--


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

--===============0506210396==--




From dhcwg-bounces@ietf.org Thu Jul 05 14:04: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 1I6Vh8-0008Pg-29; Thu, 05 Jul 2007 14:04:46 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6Vh3-0007iu-8b
	for dhcwg@ietf.org; Thu, 05 Jul 2007 14:04:41 -0400
Received: from goliath.isc.org ([204.152.187.72])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I6Vh2-0007aG-T3
	for dhcwg@ietf.org; Thu, 05 Jul 2007 14:04:41 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id CAF715A6E5; Thu,  5 Jul 2007 11:04:07 -0700 (PDT)
Date: Thu, 5 Jul 2007 11:04:07 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: "Bernie Volz (volz)" <volz@cisco.com>
Subject: Re: RE: [dhcwg] EXTENDED: Joint mip6 and dhc WG last call
	ondraft-ietf-mip6-bootstrapping-integrated and draft-ietf-mip6-hiopt
Message-ID: <20070705180407.GC5507@isc.org>
References: <1711690.6791183555407751.JavaMail.weblogic@ep_ml28>
	<8E296595B6471A4689555D5D725EBB21046AFD70@xmb-rtp-20a.amer.cisco.com>
Mime-Version: 1.0
In-Reply-To: <8E296595B6471A4689555D5D725EBB21046AFD70@xmb-rtp-20a.amer.cisco.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: DHC WG <dhcwg@ietf.org>, athene@sait.samsung.co.kr, heejin.jang@samsung.com,
	alper01.yegin@partner.samsung.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>
Content-Type: multipart/mixed; boundary="===============1117171596=="
Errors-To: dhcwg-bounces@ietf.org


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


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

On Wed, Jul 04, 2007 at 09:43:38AM -0400, Bernie Volz (volz) wrote:
> >Heejin>> No. An HN identifier field exists always, but SHOULD be
> initialized to 0=20
> >(such as a reserved field) when the id-type =3D 0 & 2. Therefore, the 0
> is not NULL=20
> >character (ascii 0) but integer 0 (ascii 48). I think there is no
> ambiguity here.=20
>=20
> Wow, that better be made clear as that certainly wasn't to me. Perhaps
> it is obvious if you know MIP6, but you should add this clarification.

Me as well.  Also...

My limited reading of that material gives me the impression that a
binary zero octet is, if not a proper identity on its own, definitely
a potential element included in an identity, and so validly included
at the end of the field (as an included part of its "UTF 8" identity
string, and not serving as string termination).

I'm not sure if that is the case, but if so it may be a good idea to
give more hints in draft-mip6-hiopt that the field is an opaque
sequence of octets so far as the DHCP software is concerned, and not,
eg, an NVT-ASCII string (as is usual in DHCP text strings, and which
carries quite a lot of null-termination-anyway baggage)?

> I think you should provide the rational for this usage as it is a bit
> atypical for DHCP -- in this case, the option length is available and
> could be set to 2 to mean that no HN identifier field exists and that
> would be, IMHO, much cleaner than using a magic string of "0".

I agree.

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

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

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

iD8DBQFGjTKXcXeLeWu2vmoRAlugAKC6FM+yNNh0di9269veBuvSlw6u5ACeKwRG
2R8JwWPu1y+/z50LSbqekqk=
=Q9Zd
-----END PGP SIGNATURE-----

--Dxnq1zWXvFF0Q93v--


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

--===============1117171596==--




From dhcwg-bounces@ietf.org Thu Jul 05 19:22: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 1I6aeR-00067i-7p; Thu, 05 Jul 2007 19:22:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6aeQ-000662-Ow
	for dhcwg@ietf.org; Thu, 05 Jul 2007 19:22:18 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6aeP-0001d8-EG
	for dhcwg@ietf.org; Thu, 05 Jul 2007 19:22:18 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 9FB4B5A6E7; Thu,  5 Jul 2007 16:22:16 -0700 (PDT)
Date: Thu, 5 Jul 2007 16:22:16 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: "Bernie Volz (volz)" <volz@cisco.com>
Subject: Re: RE: [dhcwg] EXTENDED: Joint mip6 and dhc WG last call
	ondraft-ietf-mip6-bootstrapping-integrated and draft-ietf-mip6-hiopt
Message-ID: <20070705232216.GF5507@isc.org>
References: <1711690.6791183555407751.JavaMail.weblogic@ep_ml28>
	<8E296595B6471A4689555D5D725EBB21046AFD70@xmb-rtp-20a.amer.cisco.com>
	<20070705180407.GC5507@isc.org>
Mime-Version: 1.0
In-Reply-To: <20070705180407.GC5507@isc.org>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -2.8 (--)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: DHC WG <dhcwg@ietf.org>, athene@sait.samsung.co.kr, heejin.jang@samsung.com,
	alper01.yegin@partner.samsung.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>
Content-Type: multipart/mixed; boundary="===============0820568050=="
Errors-To: dhcwg-bounces@ietf.org


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


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

On Thu, Jul 05, 2007 at 11:04:07AM -0700, David W. Hankins wrote:
> My limited reading of that material gives me the impression that a

Sorry, I made this unclear in editing.  My reading of RFC4282, which
defines the format of the field in at least one case.

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

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

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

iD8DBQFGjX0ocXeLeWu2vmoRAmUoAKCymVsxIZqzLCIWy52PriDB7ERR7wCeJopS
GperFuEM4JgYhEBTW1dMCTU=
=JZcn
-----END PGP SIGNATURE-----

--Yylu36WmvOXNoKYn--


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

--===============0820568050==--




From dhcwg-bounces@ietf.org Fri Jul 06 15:28:35 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 1I6tTf-0006uO-7h; Fri, 06 Jul 2007 15:28:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I6tTd-0006u4-2l
	for dhcwg@ietf.org; Fri, 06 Jul 2007 15:28:25 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I6tTc-0003vW-D7
	for dhcwg@ietf.org; Fri, 06 Jul 2007 15:28:25 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 665675A6EC; Fri,  6 Jul 2007 12:28:23 -0700 (PDT)
Date: Fri, 6 Jul 2007 12:28:23 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: DHC WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] dhc wg last call on  draft-ietf-dhc-pxelinux-01
Message-ID: <20070706192823.GF8503@isc.org>
References: <46823079.5050405@uninett.no>
	<8E296595B6471A4689555D5D725EBB2104619BF1@xmb-rtp-20a.amer.cisco.com>
Mime-Version: 1.0
In-Reply-To: <8E296595B6471A4689555D5D725EBB2104619BF1@xmb-rtp-20a.amer.cisco.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -2.8 (--)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
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="===============1226723283=="
Errors-To: dhcwg-bounces@ietf.org


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


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

On Fri, Jun 29, 2007 at 05:19:28PM -0400, Bernie Volz (volz) wrote:
> I fully support this document moving forward.

Thank you, Bernie.

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

I think you're right, and rather wonder why I didn't think of that
first.

The objective is just to 'mark the landmine'.  I've made the changes
in my sources

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

Fixed in my sources.

> 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 sort of agree.  Both the old and new titles aren't very informative
if you don't know what 'option' means contextually.

  <title abbrev=3D"PXELINUX Options">Dynamic Host Configuration Protocol
	Options Used by PXELINUX</title>

?


More nits;

Per Stig (some time ago), I simplified the abstract (so as to remove
references).  This does mean that I had to place references in the
introduction.

Some capitalizations in the introduction's summary list of options
being documented.


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

I don't know.  If we get too many more nits, I wouldn't object to
respinning it just to simplify the process for the editor.

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

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

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

iD8DBQFGjpfXcXeLeWu2vmoRAumXAJ4mA/2oYM4+AH/fzPPahytbIvj2FQCgkrLS
wS58RsM3epHeQ+3g/FFirSw=
=GuM5
-----END PGP SIGNATURE-----

--nHwqXXcoX0o6fKCv--


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

--===============1226723283==--




From dhcwg-bounces@ietf.org Sat Jul 07 02:22:16 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 1I73gL-0003VX-JZ; Sat, 07 Jul 2007 02:22:13 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I73gJ-0003VS-OY
	for dhcwg@ietf.org; Sat, 07 Jul 2007 02:22:11 -0400
Received: from kecgate03.progeon.com ([220.227.179.21]
	helo=Kecgate03.infosys.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I73g3-0007Zn-UJ
	for dhcwg@ietf.org; Sat, 07 Jul 2007 02:22:11 -0400
Received: from indhubbhs01.ad.infosys.com ([192.168.200.81]) by
	Kecgate03.infosys.com with InterScan Message Security Suite;
	Sat, 07 Jul 2007 11:51:55 +0530
Received: from blrkechub01.ad.infosys.com ([10.66.236.41]) by
	indhubbhs01.ad.infosys.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 7 Jul 2007 11:50:46 +0530
Received: from BLRKECMBX02.ad.infosys.com ([10.66.236.22]) by
	blrkechub01.ad.infosys.com ([10.66.236.41]) with mapi; Sat, 7 Jul 2007
	11:50:46 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: 'Michael Orr' <orr@marvell.com>
Date: Sat, 7 Jul 2007 11:50:42 +0530
Thread-Index: AcfAXBrh3BtjU3wxRva+r0IRIpkOZwAACbpQ
Message-ID: <31D55C4D55BEED48A4459EB64567589A092A6B7D34@BLRKECMBX02.ad.infosys.com>
References: <31D55C4D55BEED48A4459EB64567589A092A6B7D31@BLRKECMBX02.ad.infosys.com>
In-Reply-To: <31D55C4D55BEED48A4459EB64567589A092A6B7D31@BLRKECMBX02.ad.infosys.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: 07 Jul 2007 06:20:46.0343 (UTC)
	FILETIME=[F46A8970:01C7C05E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
Cc: "'dhcwg@ietf.org'" <dhcwg@ietf.org>,
	"'stefaan.de_cnodder@alcatel-lucent.be'"
	<stefaan.de_cnodder@alcatel-lucent.be>,
	Mukund Kamath <Mukund_Kamath@infosys.com>
Subject: [dhcwg] RE: 
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 Michael,

    Thanks for your interest and review of our document. I have copied this=
 reply to DHC WG mailing list for the benefit of others. Please see my=
 response in line.

Thanks & Regards,
Bharat

> Recently, several customers asked for a L2RA
> feature, but could not define it, which
> brought me to you document.

Apart from the comments below, is there any specific feature your customers=
 have asked which is not addressed in our document?

> Please indulge me in a few comments/questions
>
> 1. It seems to me (and my customers concur) that it is important for an
> L2RA to use Unicast
>     traffic when sending towards the DHCP-server, at least as an option.
> The current text does not
>     make it clear if the L2RA forwards DHCP traffic from clients as is or
> changes them into Unicasts
>
>     It just says "... forwards it towards the DHCP server .."

L2 RA is typically a bridge and most of the times; its management interface=
 can not be used to communicate with DHCP server. It is also not configured=
 with DHCP servers or Layer 3 Relay Agent's IP address so it can not=
 unicast the DHCP request to DHCP server or layer 3 RA.

There may be multiple ways to find out the port on which DHCP server is=
 available. L2 RA are typically configured with the upstream port which is=
 used to reach the upstream routers [something similar to Uplink port]. So=
 DHCP messages are forwarded towards DHCP server. This is a broadcast of=
 the message.

>           It may be useful to refer to an expanded NW scenario than is
> shown in figure 1, where there may
>           be two (or more) layers of L2 switches between the hosts and=
 the
> L3RA. Then the importance
>           of not sending Broadcasts from the L2RA upstream becomes
> obvious.
>

I got your concern. But as mentioned above, L2 RAs are not configured with=
 either L3 RA's address or DHCP server's address and so can not unicast. Do=
 you think there is any other way this can be achieved?

> 2. In Section 4.2 the 1st paragraph states categorically that an L2RA=
 does
> not intercept Unicast DHCP messages,
>     and the next paragraph shows that sometimes they do. I suggest to
> unify the two paragraphs, and say
>     that an L2RA MAY intercept and process unicast DHCP messages as it
> does the Broadcast ones
>

Yes. There are several L2 RAs which does snoop unicast messages because=
 they maintain certain states for each address assigned through them. This=
 is done for various reasons. Let me see how I can combine these two=
 paragraphs.

> 3. The document assumes that an L2RA sends to an L3RA, which will relay=
 to
> a Server; It is conceivable
>     that no L3RA exist, and the L2RA sends directly to a server; In such
> cases, it may be good to be able
>     to fill in giaddr of the outgoing message, so that the Server sees
> itin the same way as if it came from an L3RA

Yes. This configuration is possible. A L2 RA may not have an IP address=
 that is reachable by DHCP server so it can not add a routable 'giaddr'. As=
 of now, I think a DHCP server would discard a DHCP message if it contains=
 'option 82' but not 'giaddr'. We may want to allow this for broadcast=
 messages.

> 4.  I think the discussion in section 8 of the handling of the Broadcast
> flag is relevant not just to L3RA,
>     but to L2RA also; If the host needs a Broadcast reply (i.e. the
> Broadcast flag is set) it is preferable that
>     the last switch downstream will be the one to generate the Broadcast,
> as opposed to the L3RA, which
>
>     Can be quite up the tree, and thus affect a large(r) domain;
>

This is the reason this issue has been addressed with the new sub-option.

**************** 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 Sat Jul 07 03:52: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 1I755I-00070l-TF; Sat, 07 Jul 2007 03:52:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I755H-0006m7-7H
	for dhcwg@ietf.org; Sat, 07 Jul 2007 03:52:03 -0400
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I755D-00076O-Fu
	for dhcwg@ietf.org; Sat, 07 Jul 2007 03:52:03 -0400
Received: from ep_ms5_bk (mailout1.samsung.com [203.254.224.24])
	by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0JKS00GA9TUDUZ@mailout1.samsung.com> for dhcwg@ietf.org;
	Sat, 07 Jul 2007 16:51:49 +0900 (KST)
Received: from ep_spt03 (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 <0JKS00MTYTUFK0@ms5.samsung.com> for dhcwg@ietf.org; Sat,
	07 Jul 2007 16:51:51 +0900 (KST)
Content-return: prohibited
Date: Sat, 07 Jul 2007 07:51:51 +0000 (GMT)
From: Heejin Jang <heejin.jang@samsung.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, dhcwg@ietf.org
Message-id: <9786322.236531183794711351.JavaMail.weblogic@ep_ml20>
MIME-version: 1.0
MIME-version: 1.0
X-Priority: 3
Msgkey: 20070707075151350@heejin.jang
X-MTR: 20070707075151350@heejin.jang
X-EPLocale: ko_KR.windows-1252
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
X-EPApproval-Locale: 
X-Spam-Score: 2.1 (++)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: 
Subject: [dhcwg] Re: RE: About joint mip6 and dhc WGLC for hiopt draft
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="===============0000281206=="
Errors-To: dhcwg-bounces@ietf.org

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

SGksIEJlcm5pZS4NCktpbmRseSBzZWUgdGhlIGlubGluZQ0KIA0KLSBSZWdhcmRzLCANCkhlZWpp
bi4NCiANCi0tLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLS0tDQpTZW5kZXIgOiBCZXJuaWUg
Vm9seiAodm9seik8dm9sekBjaXNjby5jb20+DQpEYXRlICAgOiAyMDA3LTA3LTA3IDAwOjMwDQpU
aXRsZSAgOiBSRTogQWJvdXQgam9pbnQgbWlwNiBhbmQgZGhjIFdHTEMgZm9yIGhpb3B0IGRyYWZ0
DQoNClllcywgYnV0IDIyLjE3IGp1c3QgZGVzY3JpYmVzIGhvdyB0aGV5IGFyZSBzdXBwb3NlZCB0
byBiZSB1c2VkOyBpdCBpcw0Kbm90IGFuIGFjdHVhbCBleGFtcGxlIG9mIHJlYWwgd29ybGQgdXNh
Z2UuDQoNCkluIERIQ1B2Niwgd2UgaGF2ZSB0ZW5kZWQgdG8gZ28gd2l0aCBuZXcgb3B0aW9ucyBp
bnN0ZWFkIG9mIHN1Yi1vcHRpb25zLg0KQnV0IHRoYXQgbWF5IGV2ZW50dWFsbHkgaGF2ZSBhIHNj
YWxpbmcgaXNzdWUgKGZvciBleGFtcGxlLCBhIEdVSSBoYXZpbmcNCmEgcHVsbC1kb3duIGxpc3Qg
b2YgMjAwMCBvcHRpb25zIGZyb20gd2hpY2ggdG8gcGljayBmcm9tIHdvdWxkIGJlDQpleHRyZW1l
bHkgYW5ub3lpbmcpLg0KDQpJdCBtaWdodCBoZWxwIHVzIG1ha2UgcmVjb21tZW5kYXRpb25zIGlm
IHdlIGtuZXcgd2hhdCB0aGUgdHlwaWNhbCB1c2FnZQ0Kd2FzLiBGb3IgZXhhbXBsZSwgaW4gdGhl
IGNhc2VzIHlvdSBoYXZlIHByZXNlbnRseSBkZWZpbmVkIHN1Yi1vcHRpb25zLA0Kd291bGQgdGhl
cmUgdHlwaWNhbGx5IG9ubHkgYmUgb25lIG9yIG1hbnk/IEluIHNlY3Rpb24gMy4yLjEgeW91IGhh
dmUNCnRocmVlIHBvc3NpYmxlIHN1Ym9wdGlvbnMgYnV0IGl0IHNlZW1zIHRvIG1lIHRoYXQgaW4g
bWFueSBjYXNlcyBvbmx5IG9uZQ0Kd291bGQgYmUgcmV0dXJuZWQgKHRob3VnaCB0aGUgcmVxdWVz
dG9yIHdvdWxkIG5vdCBrbm93IHdoaWNoKS4gVGhlIHRleHQNCmRvZXMgc2F5ICJNdWx0aXBsZSBz
dWItb3B0aW9ucyBtYXkgZXhpc3QgaW4gYSBNSVA2IFJlbGF5IEFnZW50IG9wdGlvbiIuDQoNCklu
IHRoaXMgY2FzZSwgdGhhdCBpcyBhbHNvIHRoZSBpc3N1ZSB3aXRoIHVzaW5nIHRvcC1sZXZlbCBv
cHRpb25zLiBJZg0KeW91IHJlcGxhY2VkIDMuMi4xIHdpdGggdGhyZWUgdG9wLWxldmVsIG9wdGlv
bnMsIGFuIE9STyB3b3VsZCBuZWVkIHRvDQpjb250YWluIGFsbCB0aHJlZSBvcHRpb25zIGFuZCBp
biBtYW55IGNhc2VzIG9uZSBvciBtb3JlIG1pZ2h0IG5vdCBiZQ0KYXZhaWxhYmxlLiBBbmQsIHNv
bWUgaW5mb3JtYXRpb24gaXMgbG9zdCBiZWNhdXNlIGl0IHdvdWxkIG5vdCBiZQ0KcG9zc2libGUg
dG8gaW5kaWNhdGUgYSBzZXJ2ZXImIzM5O3MgcHJlZmVyZW5jZSBmb3Igd2hpY2ggaXMgdXNlZCAo
c3Vib3B0aW9ucw0KY291bGQgYmUgb3JkZXJlZCB0byBpbmRpY2F0ZSB0aGUgZmlyc3QsIHNlY29u
ZCwgLi4uIHByZWZlcmVuY2UpLg0KU3BlY2lmeWluZyB0aGF0IHRoZSBvcmRlciBpbiB3aGljaCB0
aGUgb3B0aW9ucyBhcHBlYXJlZCBpbiB0aGUgcGFja2V0DQpoYXZlIG1lYW5pbmcgd291bGQgYmUg
dmVyeSB0cmlja3kgYW5kIG5vdCBzb21ldGhpbmcgc2VydmVycyBhbmQgY2xpZW50cw0KYXJlIGxp
a2VseSB0byBiZSBhYmxlIHRvIGVhc2lseSBoYW5kbGUgKG5vdGUgdGhhdCB0aGUgb3JkZXJpbmcg
b2YNCm11bHRpcGxlIGluc3RhbmNlcyBvZiBhIHNpbmdsZSBvcHRpb24gY2FuIGJlIG9yZGVyZWQs
IGl0IGlzIHRoZSBvcmRlciBvZg0KRElGRkVSRU5UIG9wdGlvbnMgd2hpY2ggZXNzZW50aWFsbHkg
Y2FycnkgdGhlIHNhbWUgaW5mb3JtYXRpb24gdGhvdWdoIGluDQpkaWZmZXJlbnQgZGF0YSBmb3Jt
YXRzLCB0aGF0IGlzIHRoZSBpc3N1ZSBoZXJlLikNCg0KVGhpcyBpc24mIzM5O3QgdmVyeSBkaXNz
aW1pbGFyIHRvIHRoZSBpc3N1ZXMgZmFjZWQgYnkgdGhlIDMzDQooT1BUSU9OX0JDTUNTX1NFUlZF
Ul9EKSBhbmQgMzQgKE9QVElPTl9CQ01DU19TRVJWRVJfQSkgW1JGQzQyODBdDQpvcHRpb25zLg0K
DQpBbmQsIGl0IGlzIGFjdHVhbGx5IGFuIGFyZWEgdGhhdCB3ZSB3ZXJlLCBJIHRoaW5rLCBnb2lu
ZyB0byBsb29rIGF0IC0tDQpob3cgYmVzdCB0byBoYW5kbGUgY2FzZXMgd2hlcmUgbXVsdGlwbGUg
ZGF0YSB0eXBlcyBtaWdodCBiZSByZXR1cm5lZC4NCkJ1dCwgdGhlIERIQyBXRyBoYXNuJiMzOTt0
IGRvbmUgYW55dGhpbmcgdG8gYWRkcmVzcyB0aGlzLg0KDQpUaGUgdHdvIHN0YW5kYXJkIG1ldGhv
ZHMgYXJlOg0KLSBTZXBhcmF0ZSBvcHRpb25zICh3aXRoIHRoZSBpc3N1ZXMgYXMgcGVyIGFib3Zl
KQ0KLSBBIHNpbmdsZSBvcHRpb24gd2l0aCBhICJmbGFnIiBmaWVsZCB0byBpbmRpY2F0ZSB3aGF0
IGRhdGEgZm9sbG93cyAtLQ0KdGhpcyBpcyBsaWtlIHRoZSBPUFRJT05fTUlQNi1ITklEIG9wdGlv
bi4NCg0KSSB0aGluayBmb3IgdGhlIHNlY3Rpb24gMy4yLjEgc3Vib3B0aW9ucywgeW91IGNvdWxk
IGNyZWF0ZSBhIHNpbmdsZQ0Kb3B0aW9uIHdpdGggaGFkIGEgaWQtdHlwZSwgcmVzZXJ2ZWQgZmll
bGQsIGFuZCB0aGVuIGRhdGEgKHdoaWNoIGRlcGVuZHMNCm9uIHRoZSBpZC10eXBlKS4gUmVtZW1i
ZXIsIGluIERIQ1B2NiwgbXVsdGlwbGUgaW5zdGFuY2VzIG9mIGFuIG9wdGlvbg0KYXJlIGFsbG93
ZWQuDQoNClRob3VnaCwgaWYgeW91IHdhbnRlZCBhIHNpbmdsZSBvcHRpb24sIGl0IGNvdWxkIGJl
Og0KICAgIG9wdGlvbi1jb2RlICgxNi1iaXRzKSwgb3B0aW9uLWxlbmd0aCAoMTYtYml0cyksIE5I
SS0xLWxlbg0KKDE2LWJpdHM/KSwgaWQtdHlwZSAoOC1iaXRzKSwgW3Jlc2VydmVkICg4LWJpdHMp
LF0gTkhJLTEgKHZhcmlhYmxlLA0KZGVwZW5kcyBvbiBOSEktbGVuLCBtaW51cyAyIChhc3N1bWlu
ZyByZXNlcnZlZCBmaWVsZCBpcyBwcmVzZW50KSwNCk5ISS0yLWxlbiAoMTYtYml0cyksIGlkLXR5
cGUgLi4uDQoNCiANCkhlZWppbj4+IFRoZSBpZC10eXBlIGlzIHRoZSBmaWVsZCB0byBkZXNjcmli
ZSB3aGV0aGVyIHRoZSBIQSBpcyBhc3NpZ25lZCBmcm9tIHRoZSBsb2NhbCBuZXR3b3JrIG9yIG5v
dCwgDQppdCBkb2VzIG5vdCBuZWNlc3NhcmlseSBpbmNsdWRlZCBpbiByZWxheSBvcHRpb24gKGZy
b20gTkFTIHRvIERIQ1Agc2VydmVyKSBiZWNhdXNlIGl0cyB2YWx1ZSBpcyBhbHdheXMgDQpzZXQg
dG8gMSAod2hpY2ggbWVhbnMgbm90IGxvY2FsbHkgYXNzaWduZWQgaW5mbykuIE5vdGUgdGhhdCB0
aGUgSE4gaW5mbyBpbiBOQVMgY29tZXMgZnJvbSBBQUEgc2VydmVyIA0Kb3JpZ2luYWxseS4NCkkg
dGhpbmsgdGhhdCB5b3UgbWF5IGNvbmZ1c2UgdGhlICdpZC10eXBlJyBpbiBITiBpZGVudGlmaWVy
IG9wdGlvbiB3aXRoIHRoZSAnc3ViLW9wdC1jb2RlJyBpbiBhIHJlbGF5IG9wdGlvbi4gDQoNCklm
IHlvdSdyZSBzdWdnZXN0aW5nIHRoZSB1c2Ugb2YgcmFkaXVzIGF0dHJpYnV0ZSBUTFYgaW4gc3Vi
LW9wdGlvbiBvZiByZWxheS1vcHRpb24gYXMgd2UgDQpjYW4gc2VlIGluIHJmYzQwMTQgKERIQ1B2
NCBSYWRpdXMgYXR0cmlidXRlIHN1Ym9wdGlvbiksIGl0IGNhbiBiZSBjb25zaWRlcmVkLCBidXQN
CnN0aWxsIHRoZSB0b3AtbGV2ZWwgJiBzdWItb3B0aW9uIGlzc3VlIGluIHRoZSAqSE4gaW5mb3Jt
YXRpb24gb3B0aW9uKiByZW1haW5zLiAgIA0KICANClRoaXMgaXNuJiMzOTt0IHByZXR0eSBhbmQg
bGlrZWx5IGRpZmZpY3VsdCBmb3IgYSBsb3Qgb2Ygc2VydmVycyB0byBhbGxvdw0KdXNlcnMgdG8g
Y29uZmlndXJlLg0KDQpCdXQsIGlmIHRoaXMgaXMgc29tZXRoaW5nIHRoYXQgaXNuJiMzOTt0IG1h
bnVhbGx5IGNvbmZpZ3VyZWQgYnV0IGluc3RlYWQNCmRlcml2ZWQgZnJvbSBSYWRpdXMgZGF0YSBv
biB0aGUgcmVsYXkgKHdoaWNoIGltcGxpZXMgc3BlY2lhbCBwdXJwb3NlDQpjb2RlIG9uIHRoZSBy
ZWxheSkgW2FuZCBzaW1pbGFyaWx5IG9uIHRoZSBzZXJ2ZXJdLCB0aGF0IGlzbiYjMzk7dCBhIGJp
Zw0KZGVhbC4NCg0KTk9URTogSSB1c2VkIGRpZG4mIzM5O3QgZm9sbG93IHRoZSBNSVA2IGRvY3Vt
ZW50IHVzYWdlIGFib3ZlIGFuZCBtaXhlZCBhbmQNCm1hdGNoZWQgdGhpbmdzIGZvciBpbGx1c3Ry
YXRpdmUgcHVycG9zZXMuIEZvciBleGFtcGxlLCBpZiB0aGUgc2VjdGlvbg0KMy4yLjEgc3Vib3B0
aW9ucyBhcmUgYWx3YXlzIHJlbGF5IHRvIHNlcnZlciwgdGhleSB3b3VsZCBuZXZlciBhcHBlYXIg
aW4NCmFuIE9STy4NCg0KLSBCZXJuaWUNCg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0K
RnJvbTogRGF2aWQgVy4gSGFua2lucyBbbWFpbHRvOkRhdmlkX0hhbmtpbnNAaXNjLm9yZ10gDQpT
ZW50OiBGcmlkYXksIEp1bHkgMDYsIDIwMDcgMTE6MDEgQU0NClRvOiBCZXJuaWUgVm9seiAodm9s
eikNCkNjOiBoZWVqaW4uamFuZ0BzYW1zdW5nLmNvbQ0KU3ViamVjdDogUmU6IEFib3V0IGpvaW50
IG1pcDYgYW5kIGRoYyBXR0xDIGZvciBoaW9wdCBkcmFmdA0KDQpPbiBUaHUsIEp1bCAwNSwgMjAw
NyBhdCAwOToxMDo1NVBNIC0wNDAwLCBCZXJuaWUgVm9seiAodm9seikgd3JvdGU6DQo+IFRoZXJl
IGFyZSBhY3R1YWxseSBvcHRpb25zIHRoYXQgaGF2ZSBzdWItb3B0aW9ucyAtIHRoZSB2ZW5kb3Ig
b3B0aW9ucw0KPiAob3B0aW9uIDE3KS4gRm9yIGV4YW1wbGUsIHNlZQ0KPg0KaHR0cDovL3d3dy5j
YWJsZWxhYnMuY29tL3Byb2plY3RzL2Nyb3NzcHJvamVjdC9kb3dubG9hZHMvc3BlY3MvQ0wtU1At
Q0FODQo+IE4tREhDUC1SZWctSTAxLTA3MDExOS5wZGYuDQoNClNlY3Rpb24gMjIuMTcgb2YgUkZD
MzMxNSBpcyBhbiBlYXNpZXIgcmVhZC4gOikNCg0KSSB0aGluayBpbiB0aGUgcGFzdCB0aGF0IHRo
ZXJlIGhhcyBiZWVuIGEgcHJpbmNpcGxlIHRoYXQgaWYgdGhlDQpjbGllbnQgaXMgbGlrZWx5IHRv
IG9ubHkgd2FudCBvbmUgb2YgdGhlIGRlZmluZWQgb3B0aW9ucywgYW5kIG5vdA0KYWxsIG9mIHRo
ZW0gYWxsIG9mIHRoZSB0aW1lLCB0aGF0ICYjMzk7bXVsdGlwbGUgcmVndWxhciBvcHRpb25zJiMz
OTsgYXJlDQpwcmVmZXJyYWJsZSBvbiB0aGUgYmFzaXMgdGhhdCB0aGUgY2xpZW50IGNhbiBzcGVj
aWZ5IHdoYXQgdGhleSB3YW50DQpvbiB0aGUgT1JPIG9wdGlvbiAod2l0aCBzdWItb3B0aW9ucywg
dGhlcmUgaXMgbm8gcHJlY2VkZW50IGZvcg0Kc3ViLW9wdGlvbiBPUk8sIHNvIGNsaWVudHMgd2ls
bCBiZSBnaXZlbiBhbGwgdGhlIG9wdGlvbnMpLiAgT3RoZXJ3aXNlLA0Kc3ViLW9wdGlvbnMgYXJl
IHByZWZlcnJhYmxlLg0KDQotLSANCkRhdmlkIFcuIEhhbmtpbnMgICAgIklmIHlvdSBkb24mIzM5
O3QgZG8gaXQgcmlnaHQgdGhlIGZpcnN0IHRpbWUsDQpTb2Z0d2FyZSBFbmdpbmVlciAgICAgICAg
ICAgICB5b3UmIzM5O2xsIGp1c3QgaGF2ZSB0byBkbyBpdCBhZ2Fpbi4iDQpJbnRlcm5ldCBTeXN0
ZW1zIENvbnNvcnRpdW0sIEluYy4gICAgICAgIC0tIEphY2sgVC4gSGFua2lucw0KDQoNCg==




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

--===============0000281206==--



From dhcwg-bounces@ietf.org Sat Jul 07 04:54:55 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 1I763w-0001fm-Pt; Sat, 07 Jul 2007 04:54:44 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I763t-0001fc-6I
	for dhcwg@ietf.org; Sat, 07 Jul 2007 04:54:41 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I763s-0000uH-Gb
	for dhcwg@ietf.org; Sat, 07 Jul 2007 04:54:41 -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 <0JKS000BCWQCWB@mailout3.samsung.com> for dhcwg@ietf.org;
	Sat, 07 Jul 2007 17:54:12 +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 <0JKS00BZCWQEKZ@ms5.samsung.com> for dhcwg@ietf.org; Sat,
	07 Jul 2007 17:54:15 +0900 (KST)
Content-return: prohibited
Date: Sat, 07 Jul 2007 08:54:14 +0000 (GMT)
From: Heejin Jang <heejin.jang@samsung.com>
To: "David W. Hankins" <David_Hankins@isc.org>, dhcwg@ietf.org
Message-id: <0JKS00BZDWQEKZ@ms5.samsung.com>
MIME-version: 1.0
MIME-version: 1.0
X-Priority: 3
Msgkey: 20070707085414825@heejin.jang
X-MTR: 20070707085414825@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: 4.5 (++++)
X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593
Cc: "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: [dhcwg] Re: Discussion for hiopt draft
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="===============0643351194=="
Errors-To: dhcwg-bounces@ietf.org

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

PEhUTUw+PEhFQUQ+CjxNRVRBIGh0dHAtZXF1aXY9Q29udGVudC1UeXBlIGNvbnRlbnQ9J3RleHQv
aHRtbDsgY2hhcnNldD13aW5kb3dzLTEyNTInPgo8dGl0bGU+U2Ftc3VuZyBFbnRlcnByaXNlIFBv
cnRhbCBteVNpbmdsZTwvdGl0bGU+CjxzdHlsZT4gUCwgdGQsIGxpIHtmb250LWZhbWlseTpBcmlh
bCwgYXJpYWw7IGZvbnQtc2l6ZTo5cHQ7IG1hcmdpbi10b3A6NXB4O21hcmdpbi1ib3R0b206NXB4
O30gYm9keXtmb250LWZhbWlseTpBcmlhbCwgYXJpYWw7IGZvbnQtc2l6ZTo5cHQ7fTwvc3R5bGU+
CjwvSEVBRD48Qk9EWT48cCBjbGFzcz1Nc29Ob3JtYWwgYWxpZ249bGVmdCBzdHlsZT0idGV4dC1h
bGlnbjpsZWZ0OyBtc28tbGF5b3V0LWdyaWQtYWxpZ246DQpub25lO3dvcmQtYnJlYWs6a2VlcC1h
bGwiPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J21zby1iaWRpLWZvbnQtc2l6ZToxMC4wcHQ7DQpm
b250LWZhbWlseTo/Pzttc28taGFuc2ktZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiI7bXNv
LWJpZGktZm9udC1mYW1pbHk6DQo/Pzttc28tZm9udC1rZXJuaW5nOjBwdCc+SGksIEJlcm5pZSwg
RGF2aWQgYW5kIGZvbGtzLjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbCBhbGlnbj1s
ZWZ0IHN0eWxlPSJ0ZXh0LWFsaWduOmxlZnQ7IG1zby1sYXlvdXQtZ3JpZC1hbGlnbjoNCm5vbmU7
d29yZC1icmVhazprZWVwLWFsbCI+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nbXNvLWJpZGktZm9u
dC1zaXplOjEwLjBwdDsNCmZvbnQtZmFtaWx5Oj8/O21zby1oYW5zaS1mb250LWZhbWlseToiVGlt
ZXMgTmV3IFJvbWFuIjttc28tYmlkaS1mb250LWZhbWlseToNCj8/O21zby1mb250LWtlcm5pbmc6
MHB0Jz4mbmJzcDs8L3NwYW4+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWwgYWxpZ249bGVmdCBz
dHlsZT0idGV4dC1hbGlnbjpsZWZ0OyBtc28tbGF5b3V0LWdyaWQtYWxpZ246DQpub25lO3dvcmQt
YnJlYWs6a2VlcC1hbGwiPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J21zby1iaWRpLWZvbnQtc2l6
ZToxMC4wcHQ7DQpmb250LWZhbWlseTo/Pzttc28taGFuc2ktZm9udC1mYW1pbHk6IlRpbWVzIE5l
dyBSb21hbiI7bXNvLWJpZGktZm9udC1mYW1pbHk6DQo/Pzttc28tZm9udC1rZXJuaW5nOjBwdCc+
Rm9yIHRoZSBzYWtlIG9mIGNsYXJpdHksIGEgREhDUHY2ICdtYWluIG9wdGlvbicgaW4gbXkNCnBy
ZXZpb3VzbHkgc2VudCBtYWlscyBpcyB0aGUgb3B0aW9uPC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9
TXNvTm9ybWFsIGFsaWduPWxlZnQgc3R5bGU9InRleHQtYWxpZ246bGVmdDsgbXNvLWxheW91dC1n
cmlkLWFsaWduOg0Kbm9uZTt3b3JkLWJyZWFrOmtlZXAtYWxsIj48c3BhbiBsYW5nPUVOLVVTIHN0
eWxlPSdtc28tYmlkaS1mb250LXNpemU6MTAuMHB0Ow0KZm9udC1mYW1pbHk6Pz87bXNvLWhhbnNp
LWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iO21zby1iaWRpLWZvbnQtZmFtaWx5Og0KPz87
bXNvLWZvbnQta2VybmluZzowcHQnPndob3NlIG9wdGlvbi1jb2RlIGlzIGFzc2lnbmVkIGZyb20g
dGhlIHBvb2wgb2YgdGhlDQpyZWd1bGFyIDE2LWJpdCBESENQdjYgb3B0aW9uIGNvZGVzPC9zcGFu
PjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsIGFsaWduPWxlZnQgc3R5bGU9InRleHQtYWxpZ246
bGVmdDsgbXNvLWxheW91dC1ncmlkLWFsaWduOg0Kbm9uZTt3b3JkLWJyZWFrOmtlZXAtYWxsIj48
c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdtc28tYmlkaS1mb250LXNpemU6MTAuMHB0Ow0KZm9udC1m
YW1pbHk6Pz87bXNvLWhhbnNpLWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iO21zby1iaWRp
LWZvbnQtZmFtaWx5Og0KPz87bXNvLWZvbnQta2VybmluZzowcHQnPihodHRwOi8vd3d3LmlhbmEu
b3JnL2Fzc2lnbm1lbnRzL2RoY3B2Ni1wYXJhbWV0ZXJzKQ0KaW5zdGVhZCBvZiBzdGFydGluZyBm
cm9tIHN1Yi1vcHQtY29kZSAwLjwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbCBhbGln
bj1sZWZ0IHN0eWxlPSJ0ZXh0LWFsaWduOmxlZnQ7IG1zby1sYXlvdXQtZ3JpZC1hbGlnbjoNCm5v
bmU7d29yZC1icmVhazprZWVwLWFsbCI+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nbXNvLWJpZGkt
Zm9udC1zaXplOjEwLjBwdDsNCmZvbnQtZmFtaWx5Oj8/O21zby1oYW5zaS1mb250LWZhbWlseToi
VGltZXMgTmV3IFJvbWFuIjttc28tYmlkaS1mb250LWZhbWlseToNCj8/O21zby1mb250LWtlcm5p
bmc6MHB0Jz5JdCBkb2VzIG5vdCBtZWFuIHRoYXQgdGhlIG1haW4gb3B0aW9uIGNhbm5vdCBiZSB1
c2VkDQp3aXRoaW4gYW5vdGhlciBvcHRpb24uPC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9y
bWFsIGFsaWduPWxlZnQgc3R5bGU9InRleHQtYWxpZ246bGVmdDsgbXNvLWxheW91dC1ncmlkLWFs
aWduOg0Kbm9uZTt3b3JkLWJyZWFrOmtlZXAtYWxsIj48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdt
c28tYmlkaS1mb250LXNpemU6MTAuMHB0Ow0KZm9udC1mYW1pbHk6Pz87bXNvLWhhbnNpLWZvbnQt
ZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iO21zby1iaWRpLWZvbnQtZmFtaWx5Og0KPz87bXNvLWZv
bnQta2VybmluZzowcHQnPihTbywgQmVybmllICZhbXA7IERhdmlkLCBpdCBpcyBkaWZmZXJlbnQg
ZnJvbSB0aGUNCnRvcC1sZXZlbCBvcHRpb24gaWYgeW91IG1lYW50IHRoYXQgYSB0b3AtbGV2ZWwg
b3B0aW9uIGlzPC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsIGFsaWduPWxlZnQgc3R5
bGU9InRleHQtYWxpZ246bGVmdDsgbXNvLWxheW91dC1ncmlkLWFsaWduOg0Kbm9uZTt3b3JkLWJy
ZWFrOmtlZXAtYWxsIj48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdtc28tYmlkaS1mb250LXNpemU6
MTAuMHB0Ow0KZm9udC1mYW1pbHk6Pz87bXNvLWhhbnNpLWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcg
Um9tYW4iO21zby1iaWRpLWZvbnQtZmFtaWx5Og0KPz87bXNvLWZvbnQta2VybmluZzowcHQnPnRo
ZSBvcHRpb24gd2hpY2ggY2Fubm90IGJlIGluY2x1ZGVkIHdpdGhpbiBhbm90aGVyDQpvcHRpb24p
Ljwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbCBhbGlnbj1sZWZ0IHN0eWxlPSJ0ZXh0
LWFsaWduOmxlZnQ7IG1zby1sYXlvdXQtZ3JpZC1hbGlnbjoNCm5vbmU7d29yZC1icmVhazprZWVw
LWFsbCI+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nbXNvLWJpZGktZm9udC1zaXplOjEwLjBwdDsN
CmZvbnQtZmFtaWx5Oj8/O21zby1oYW5zaS1mb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIjtt
c28tYmlkaS1mb250LWZhbWlseToNCj8/O21zby1mb250LWtlcm5pbmc6MHB0Jz4mbmJzcDs8L3Nw
YW4+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWwgYWxpZ249bGVmdCBzdHlsZT0idGV4dC1hbGln
bjpsZWZ0OyBtc28tbGF5b3V0LWdyaWQtYWxpZ246DQpub25lO3dvcmQtYnJlYWs6a2VlcC1hbGwi
PjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J21zby1iaWRpLWZvbnQtc2l6ZToxMC4wcHQ7DQpmb250
LWZhbWlseTo/Pzttc28taGFuc2ktZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiI7bXNvLWJp
ZGktZm9udC1mYW1pbHk6DQo/Pzttc28tZm9udC1rZXJuaW5nOjBwdCc+U28gaWYgaXQgZG9lcyBu
b3QgbWFrZSBhbnkgYmlnIGRpZmZlcmVuY2UgYmV0d2VlbiB0aGUNCmZvbGxvd2luZyAxKSAmYW1w
OyAyKSBmcm9tIHRoZSBwZXJzcGVjdGl2ZSBvZiA8L3NwYW4+PC9wPg0KDQo8cCBjbGFzcz1Nc29O
b3JtYWwgYWxpZ249bGVmdCBzdHlsZT0idGV4dC1hbGlnbjpsZWZ0OyBtc28tbGF5b3V0LWdyaWQt
YWxpZ246DQpub25lO3dvcmQtYnJlYWs6a2VlcC1hbGwiPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9
J21zby1iaWRpLWZvbnQtc2l6ZToxMC4wcHQ7DQpmb250LWZhbWlseTo/Pzttc28taGFuc2ktZm9u
dC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiI7bXNvLWJpZGktZm9udC1mYW1pbHk6DQo/Pzttc28t
Zm9udC1rZXJuaW5nOjBwdCc+ZGhjcHY2IGRlc2lnbiBwcmluY2lwbGUsIEkgcHJlZmVyIHRvIHVz
ZSAyKS48L3NwYW4+PC9wPg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWwgYWxpZ249bGVmdCBzdHlsZT0i
dGV4dC1hbGlnbjpsZWZ0OyBtc28tbGF5b3V0LWdyaWQtYWxpZ246DQpub25lO3dvcmQtYnJlYWs6
a2VlcC1hbGwiPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9J21zby1iaWRpLWZvbnQtc2l6ZToxMC4w
cHQ7DQpmb250LWZhbWlseTo/Pzttc28taGFuc2ktZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21h
biI7bXNvLWJpZGktZm9udC1mYW1pbHk6DQo/Pzttc28tZm9udC1rZXJuaW5nOjBwdCc+KEFueXdh
eSBpdCB3aWxsIGJlIGRlY2lkZWQgYWxzbyB3aXRoIHRoZSBjb25zZW5zdXMgb2YNCk1JUDYgV0cp
PC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsIGFsaWduPWxlZnQgc3R5bGU9InRleHQt
YWxpZ246bGVmdDsgbXNvLWxheW91dC1ncmlkLWFsaWduOg0Kbm9uZTt3b3JkLWJyZWFrOmtlZXAt
YWxsIj48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdtc28tYmlkaS1mb250LXNpemU6MTAuMHB0Ow0K
Zm9udC1mYW1pbHk6Pz87bXNvLWhhbnNpLWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iO21z
by1iaWRpLWZvbnQtZmFtaWx5Og0KPz87bXNvLWZvbnQta2VybmluZzowcHQnPiZuYnNwOzwvc3Bh
bj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbCBhbGlnbj1sZWZ0IHN0eWxlPSJ0ZXh0LWFsaWdu
OmxlZnQ7IG1zby1sYXlvdXQtZ3JpZC1hbGlnbjoNCm5vbmU7d29yZC1icmVhazprZWVwLWFsbCI+
PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nbXNvLWJpZGktZm9udC1zaXplOjEwLjBwdDsNCmZvbnQt
ZmFtaWx5Oj8/O21zby1oYW5zaS1mb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIjttc28tYmlk
aS1mb250LWZhbWlseToNCj8/O21zby1mb250LWtlcm5pbmc6MHB0Jz5Gb3IgYSBjdXJyZW50IDgt
Yml0IHN1Ym9wdGlvbiBpbiByZWxheSAmYW1wOyBITg0KaW5mb3JtYXRpb24gb3B0aW9uIGluIGhp
b3B0LTA1LDwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbCBhbGlnbj1sZWZ0IHN0eWxl
PSJ0ZXh0LWFsaWduOmxlZnQ7IG1zby1sYXlvdXQtZ3JpZC1hbGlnbjoNCm5vbmU7d29yZC1icmVh
azprZWVwLWFsbCI+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nbXNvLWJpZGktZm9udC1zaXplOjEw
LjBwdDsNCmZvbnQtZmFtaWx5Oj8/O21zby1oYW5zaS1mb250LWZhbWlseToiVGltZXMgTmV3IFJv
bWFuIjttc28tYmlkaS1mb250LWZhbWlseToNCj8/O21zby1mb250LWtlcm5pbmc6MHB0Jz4xKSAx
c3QgYXBwcm9hY2ggKGxpa2UgREhDUHY2IElBQUREUiBvcHRpb24pPC9zcGFuPjwvcD4NCg0KPHAg
Y2xhc3M9TXNvTm9ybWFsIGFsaWduPWxlZnQgc3R5bGU9InRleHQtYWxpZ246bGVmdDsgbXNvLWxh
eW91dC1ncmlkLWFsaWduOg0Kbm9uZTt3b3JkLWJyZWFrOmtlZXAtYWxsIj48c3BhbiBsYW5nPUVO
LVVTIHN0eWxlPSdtc28tYmlkaS1mb250LXNpemU6MTAuMHB0Ow0KZm9udC1mYW1pbHk6Pz87bXNv
LWhhbnNpLWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iO21zby1iaWRpLWZvbnQtZmFtaWx5
Og0KPz87bXNvLWZvbnQta2VybmluZzowcHQnPi0gYXNzaWduIGEgMTYtYml0IGNvZGUvbGVuZ3Ro
IGZyb20gdGhlIHBvb2wgb2YgdGhlDQpyZWd1bGFyIDE2LWJpdCBESENQdjYgb3B0aW9uIGNvZGVz
IDwvc3Bhbj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbCBhbGlnbj1sZWZ0IHN0eWxlPSJ0ZXh0
LWFsaWduOmxlZnQ7IG1zby1sYXlvdXQtZ3JpZC1hbGlnbjoNCm5vbmU7d29yZC1icmVhazprZWVw
LWFsbCI+PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nbXNvLWJpZGktZm9udC1zaXplOjEwLjBwdDsN
CmZvbnQtZmFtaWx5Oj8/O21zby1oYW5zaS1mb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIjtt
c28tYmlkaS1mb250LWZhbWlseToNCj8/O21zby1mb250LWtlcm5pbmc6MHB0Jz5pbnN0ZWFkIG9m
IHN0YXJ0aW5nIGZyb20gc3ViLW9wdC1jb2RlIDA8L3NwYW4+PC9wPg0KDQo8cCBjbGFzcz1Nc29O
b3JtYWwgYWxpZ249bGVmdCBzdHlsZT0idGV4dC1hbGlnbjpsZWZ0OyBtc28tbGF5b3V0LWdyaWQt
YWxpZ246DQpub25lO3dvcmQtYnJlYWs6a2VlcC1hbGwiPjxzcGFuIGxhbmc9RU4tVVMgc3R5bGU9
J21zby1iaWRpLWZvbnQtc2l6ZToxMC4wcHQ7DQpmb250LWZhbWlseTo/Pzttc28taGFuc2ktZm9u
dC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiI7bXNvLWJpZGktZm9udC1mYW1pbHk6DQo/Pzttc28t
Zm9udC1rZXJuaW5nOjBwdCc+LSBUaGlzIG9wdGlvbnMgd2lsbCBiZSBkZWxpdmVyZWQgYWx3YXlz
IGFzIGluY2x1ZGVkIGluDQpyZWxheSAmYW1wOyBITiBpbmZvcm1hdGlvbiBvcHRpb25zLjwvc3Bh
bj48L3A+DQoNCjxwIGNsYXNzPU1zb05vcm1hbCBhbGlnbj1sZWZ0IHN0eWxlPSJ0ZXh0LWFsaWdu
OmxlZnQ7IG1zby1sYXlvdXQtZ3JpZC1hbGlnbjoNCm5vbmU7d29yZC1icmVhazprZWVwLWFsbCI+
PHNwYW4gbGFuZz1FTi1VUyBzdHlsZT0nbXNvLWJpZGktZm9udC1zaXplOjEwLjBwdDsNCmZvbnQt
ZmFtaWx5Oj8/O21zby1oYW5zaS1mb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIjttc28tYmlk
aS1mb250LWZhbWlseToNCj8/O21zby1mb250LWtlcm5pbmc6MHB0Jz4mbmJzcDs8L3NwYW4+PC9w
Pg0KDQo8cCBjbGFzcz1Nc29Ob3JtYWwgYWxpZ249bGVmdCBzdHlsZT0idGV4dC1hbGlnbjpsZWZ0
OyBtc28tbGF5b3V0LWdyaWQtYWxpZ246DQpub25lO3dvcmQtYnJlYWs6a2VlcC1hbGwiPjxzcGFu
IGxhbmc9RU4tVVMgc3R5bGU9J21zby1iaWRpLWZvbnQtc2l6ZToxMC4wcHQ7DQpmb250LWZhbWls
eTo/Pzttc28taGFuc2ktZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiI7bXNvLWJpZGktZm9u
dC1mYW1pbHk6DQo/Pzttc28tZm9udC1rZXJuaW5nOjBwdCc+MikgMm5kIGFwcHJvYWNoIChsaWtl
IERIQ1B2NCBzdWJvcHRpb24pPC9zcGFuPjwvcD4NCg0KPHAgY2xhc3M9TXNvTm9ybWFsIGFsaWdu
PWxlZnQgc3R5bGU9InRleHQtYWxpZ246bGVmdDsgbXNvLWxheW91dC1ncmlkLWFsaWduOg0Kbm9u
ZTt3b3JkLWJyZWFrOmtlZXAtYWxsIj48c3BhbiBsYW5nPUVOLVVTIHN0eWxlPSdtc28tYmlkaS1m
b250LXNpemU6MTAuMHB0Ow0KZm9udC1mYW1pbHk6Pz87bXNvLWhhbnNpLWZvbnQtZmFtaWx5OiJU
aW1lcyBOZXcgUm9tYW4iO21zby1iaWRpLWZvbnQtZmFtaWx5Og0KPz87bXNvLWZvbnQta2Vybmlu
ZzowcHQnPi0gRm9yIGEgY3VycmVudCA4LWJpdCBzdWJvcHRpb24gaW4gcmVsYXkgJmFtcDsgSE4N
CmluZm9ybWF0aW9uIG9wdGlvbiBpbiBoaW9wdC0wNSw8L3NwYW4+PC9wPg0KDQo8cCBjbGFzcz1N
c29Ob3JtYWwgYWxpZ249bGVmdCBzdHlsZT0idGV4dC1hbGlnbjpsZWZ0OyBtc28tbGF5b3V0LWdy
aWQtYWxpZ246DQpub25lO3dvcmQtYnJlYWs6a2VlcC1hbGwiPjxzcGFuIGxhbmc9RU4tVVMgc3R5
bGU9J21zby1iaWRpLWZvbnQtc2l6ZToxMC4wcHQ7DQpmb250LWZhbWlseTo/Pzttc28taGFuc2kt
Zm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiI7bXNvLWJpZGktZm9udC1mYW1pbHk6DQo/Pztt
c28tZm9udC1rZXJuaW5nOjBwdCc+anVzdCBleHRlbmQgYSA4LWJpdCBjb2RlL2xlbmd0aCB0byBh
IDE2LWJpdCBhbmQgc3RhcnQNCmZyb20gc3ViLW9wdC1jb2RlIDAuPC9zcGFuPjwvcD4NCg0KPHAg
YWxpZ249ImxlZnQiIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJ0ZXh0LWFsaWduOmxlZnQ7Ij4m
bmJzcDs8L3A+DQo8cCBhbGlnbj0ibGVmdCIgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9InRleHQt
YWxpZ246bGVmdDsiPi0gUmVnYXJkcywgPC9wPg0KPHAgYWxpZ249ImxlZnQiIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJ0ZXh0LWFsaWduOmxlZnQ7Ij5IZWVqaW4uPC9wPg0KPHAgYWxpZ249Imxl
ZnQiIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJ0ZXh0LWFsaWduOmxlZnQ7Ij4mbmJzcDs8L3A+
DQo8L0JPRFk+PC9IVE1MPg==




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

--===============0643351194==--



From dhcwg-bounces@ietf.org Mon Jul 09 13:14: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 1I7woK-0006FC-1m; Mon, 09 Jul 2007 13:14:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I7woI-0006F7-Lp
	for dhcwg@ietf.org; Mon, 09 Jul 2007 13:14:06 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I7woG-0005z4-4G
	for dhcwg@ietf.org; Mon, 09 Jul 2007 13:14:06 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 5DC675A6EC; Mon,  9 Jul 2007 10:14:03 -0700 (PDT)
Date: Mon, 9 Jul 2007 10:14:03 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: DHC WG <dhcwg@ietf.org>
Message-ID: <20070709171403.GD25735@isc.org>
References: <0JKS00BZDWQEKZ@ms5.samsung.com>
Mime-Version: 1.0
In-Reply-To: <0JKS00BZDWQEKZ@ms5.samsung.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 36c793b20164cfe75332aa66ddb21196
Subject: [dhcwg] Re: Discussion for hiopt 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>
Content-Type: multipart/mixed; boundary="===============0890853521=="
Errors-To: dhcwg-bounces@ietf.org


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

This message came through all in HTML, so I'm unsure if other folks were
able to read it - I've included it in entirety below rather than just
the one piece that I wish to respond to.

All I wanted to say is I agree with your election to use the second
method that you've outlined.  I understand the HIOPT options to be
multiple disparate values that are "always sent" when they are
available, and not subject to parameter request.

But I'd like to reiterate a request that you start from sub-option
code 1.  All other sub option spaces so far have done this, and the
top level DHCP codes themselves have avoided the use of zero, I think
due to its 'magic value' ancestry in DHCPv4, and the propensity for
both these protocols to be served with common sourcecode.

I'd have to add another branch to our parsing loop to support codes
beginning with zero, which is doable, but there hasn't been any other
reason to do so yet.


On Sat, Jul 07, 2007 at 08:54:14AM +0000, Heejin Jang wrote:
> Hi, Bernie, David and folks.
>=20
>=20
>=20
> For the sake of clarity, a DHCPv6 'main option' in my previously sent mai=
ls is
> the option
>=20
> whose option-code is assigned from the pool of the regular 16-bit DHCPv6 =
option
> codes
>=20
> (http://www.iana.org/assignments/dhcpv6-parameters) instead of starting f=
rom
> sub-opt-code 0.
>=20
> It does not mean that the main option cannot be used within another optio=
n.
>=20
> (So, Bernie & David, it is different from the top-level option if you mea=
nt
> that a top-level option is
>=20
> the option which cannot be included within another option).
>=20
>=20
>=20
> So if it does not make any big difference between the following 1) & 2) f=
rom
> the perspective of
>=20
> dhcpv6 design principle, I prefer to use 2).
>=20
> (Anyway it will be decided also with the consensus of MIP6 WG)
>=20
>=20
>=20
> For a current 8-bit suboption in relay & HN information option in hiopt-0=
5,
>=20
> 1) 1st approach (like DHCPv6 IAADDR option)
>=20
> - assign a 16-bit code/length from the pool of the regular 16-bit DHCPv6 =
option
> codes
>=20
> instead of starting from sub-opt-code 0
>=20
> - This options will be delivered always as included in relay & HN informa=
tion
> options.
>=20
>=20
>=20
> 2) 2nd approach (like DHCPv4 suboption)
>=20
> - For a current 8-bit suboption in relay & HN information option in hiopt=
-05,
>=20
> just extend a 8-bit code/length to a 16-bit and start from sub-opt-code 0.
>=20
>=20
>=20
> - Regards,
>=20
> Heejin.

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

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

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

iD8DBQFGkmzbcXeLeWu2vmoRAm02AKCCkG+70h7VqXR3e1wHgJ96vUAGGACcDgGH
TZHefZbkKVlPN33r5GwJoJw=
=RV1z
-----END PGP SIGNATURE-----

--hQiwHBbRI9kgIhsi--


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

--===============0890853521==--




From dhcwg-bounces@ietf.org Tue Jul 10 09:09: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 1I8FSg-00030P-77; Tue, 10 Jul 2007 09:09:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8FSe-00030J-Ii
	for dhcwg@ietf.org; Tue, 10 Jul 2007 09:09:00 -0400
Received: from tyholt.uninett.no ([2001:700:1::eecb])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I8FSe-0003zv-1c
	for dhcwg@ietf.org; Tue, 10 Jul 2007 09:09:00 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by tyholt.uninett.no (Postfix) with ESMTP id DACBFB5A93
	for <dhcwg@ietf.org>; Tue, 10 Jul 2007 15:08:58 +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 31362-02-36 for <dhcwg@ietf.org>;
	Tue, 10 Jul 2007 15:08:58 +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 AD031B5A90
	for <dhcwg@ietf.org>; Tue, 10 Jul 2007 15:08:58 +0200 (CEST)
Message-ID: <469384EA.3050301@uninett.no>
Date: Tue, 10 Jul 2007 15:08:58 +0200
From: Stig Venaas <stig.venaas@uninett.no>
User-Agent: Thunderbird 2.0.0.4 (X11/20070627)
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: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Subject: [dhcwg] dhc wg last call on vpn-option and agent-vpn-id drafts
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 wg last call on two drafts. They are

Virtual Subnet Selection Option <draft-ietf-dhc-vpn-option-06.txt>

and

Virtual Subnet Selection Sub-Option for the Relay Agent Information 
Option for DHCPv4 <draft-ietf-dhc-agent-vpn-id-04.txt>

The last call will conclude at 1700EST on Sun, 2007-07-22.

Please respond to this WG last call.  If you support acceptance of the
documents without change, respond with a simple acknowledgment, so that
support for the documents 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.

draft-ietf-dhc-vpn-option defines a new DHCP option for passing Virtual
Subnet Selection (VSS) information between the DHCP client and the DHCP
server.  It is intended for use primarily by DHCP proxy clients in
situations where VSS information needs to be passed to the DHCP server
for proper address allocation to take place.  This document documents
option usage in line with the option reclassification in RFC 3942.
This draft is available as
http://www.ietf.org/internet-drafts/draft-ietf-dhc-vpn-option-06.txt

draft-ietf-dhc-agent-vpn-id defines a new relay-agent-information option
sub-option used by a relay agent to tell the DHCP server important
information about the VPN (called the Virtual Subnet Selection
information, or VSS) for every DHCP request it passes on to the DHCP
server, and is also used to properly forward any DHCP reply that the
DHCP server sends back to the relay agent.
This draft is available as
http://www.ietf.org/internet-drafts/draft-ietf-dhc-agent-vpn-id-04.txt

Stig

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



From dhcwg-bounces@ietf.org Wed Jul 11 07:56: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 1I8aoL-0005IL-V1; Wed, 11 Jul 2007 07:56:49 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I8aoK-0005IG-SO
	for dhcwg@ietf.org; Wed, 11 Jul 2007 07:56:48 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I8aoK-0006AU-Iy
	for dhcwg@ietf.org; Wed, 11 Jul 2007 07:56:48 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-6.cisco.com with ESMTP; 11 Jul 2007 04:56:48 -0700
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAPFhlEarR7PE/2dsb2JhbAA
X-IronPort-AV: i="4.16,526,1175497200"; 
	d="scan'208"; a="180131382:sNHT24934770"
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 l6BBulg9007025
	for <dhcwg@ietf.org>; Wed, 11 Jul 2007 04:56:47 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l6BBulmo003017
	for <dhcwg@ietf.org>; Wed, 11 Jul 2007 11:56:47 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Jul 2007 07:56:47 -0400
Received: from [192.168.1.103] ([10.86.243.42]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 11 Jul 2007 07:56:45 -0400
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: 7bit
Message-Id: <2C324C4E-08CD-485B-ADAF-F01680F00DBD@cisco.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Date: Wed, 11 Jul 2007 07:56:53 -0400
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 11 Jul 2007 11:56:46.0905 (UTC)
	FILETIME=[8EB32A90:01C7C3B2]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1538; t=1184155007;
	x=1185019007; c=relaxed/simple; s=sjdkim4002;
	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:=20*DRAFT*=20Agenda=20for=20IETF-69=20dhc=20WG=20meeting
	|Sender:=20; bh=Nqj9/G2VGDVeI1kcsQNPwgLTR1i1xbM+LIzet2e+6IE=;
	b=C+kK93qiAxTvRvV8t95C4MU0MNo/S8jHDpkreJEXjQdRgUojF7+NTWl2QbzHcRx5LCJZnwzf
	aUHI3YfKTNv3pV0gVjUjO5o8M852H/WTIDfyXV5PRgWYK5kJq/t4OUk4;
Authentication-Results: sj-dkim-4; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Subject: [dhcwg] *DRAFT* Agenda for IETF-69 dhc WG meeting
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

Draft agenda is included below.  Please contact the chairs if you  
have a topic to be added to the agenda.

                           DHC WG DRAFT agenda - IETF 67
                         0900-1130 2007-07-23 (Mon)
                    (Last revised 2007-07-11 07:55 AM ET)
                    -------------------------------------

Administrivia                                   Venaas/Droms     10  
minutes
   Agenda bashing; blue sheets; scribe; Jabber scribe

Draft last call and adoption announcements      Venaas/Droms     05  
minutes

Progressing two drafts under RFC 3942           R. Droms         10  
minutes
   <draft-ietf-dhc-subnet-alloc-05>
   <draft-raj-dhc-tftp-addr-option-02>

Update to DHCP options guideline                D. Hankins       05  
minutes
   <draft-dhankins-dhcp-option-guidelines-00>
   Accept as WG work item?

Using DHCPv6 and AAA Server for mobile station PD
                                                 B. Sarikaya      15  
minutes
   <draft-sarikaya-16ng-prefix-delegation-01>
   WG input on DHCP-related I-D

Layer 2 relay agent and relay agent chaining    P. Kurapati      15  
minutes
   <draft-joshi-dhc-layer2-relay-agent-01>
   <draft-kurapati-dhc-relay-chaining-dhcpv4-01>
   Adopt as WG work items?

TAHI DHCPv6 Test tool for IPv6 Ready Logo       Hideshi E.       05  
minutes
                                                                  
-----------
                                                                  65  
minutes

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



From dhcwg-bounces@ietf.org Wed Jul 11 15:37: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 1I8hzo-0002z1-TG; Wed, 11 Jul 2007 15:37:08 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I8hzm-0002xA-40; Wed, 11 Jul 2007 15:37:06 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I8hzl-0006dw-Or; Wed, 11 Jul 2007 15:37:06 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id 2340790020;
	Wed, 11 Jul 2007 15:35:53 -0400 (EDT)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 28908-12; Wed, 11 Jul 2007 15:35:49 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[10.2.4.28]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Wed, 11 Jul 2007 15:35:49 -0400 (EDT)
Received: from exchtewks2.starentnetworks.com ([10.2.4.27]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Wed, 11 Jul 2007 15:36:04 -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: [Mip4] RE: [dhcwg] EXTENDED: mip4 and dhc WG joint last call
	ondraft-ietf-mip4-gen-ext-03.txt
Date: Wed, 11 Jul 2007 15:35:30 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D7024DA2B4@exchtewks2.starentnetworks.com>
In-Reply-To: <8E296595B6471A4689555D5D725EBB2104619B99@xmb-rtp-20a.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] RE: [dhcwg] EXTENDED: mip4 and dhc WG joint last call
	ondraft-ietf-mip4-gen-ext-03.txt
Thread-Index: Ace5bY6yzSyTZiVgEdyNKgARJOT6egBG+QRQAlo3tcA=
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "Bernie Volz (volz)" <volz@cisco.com>,
	"Ralph Droms (rdroms)" <rdroms@cisco.com>, <mip4@ietf.org>,
	"DHC WG" <dhcwg@ietf.org>
X-OriginalArrivalTime: 11 Jul 2007 19:36:04.0616 (UTC)
	FILETIME=[B8602880:01C7C3F2]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
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 Bernie,

Thanks for the review. I think your suggestion to add the note is good
for clarification purpose. So, I see no issue adding such note in the
document.

BR,
Kuntal


> -----Original Message-----
> From: Bernie Volz (volz) [mailto:volz@cisco.com]
> Sent: Friday, June 29, 2007 3:19 PM
> To: Ralph Droms (rdroms); mip4@ietf.org; DHC WG
> Subject: [Mip4] RE: [dhcwg] EXTENDED: mip4 and dhc WG joint last call
> ondraft-ietf-mip4-gen-ext-03.txt
>=20
> Ralph, et al:
>=20
> 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.
>=20
> 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).
>=20
> - Bernie
>=20
> -----Original Message-----
> From: Ralph Droms (rdroms)
> 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
>=20
> There has been no response to this WG last call, so the 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 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.
>=20
> The dhc WG is asked to review the use of DHCP options in this draft to
> pass configuration information to a mobile node.
>=20
> 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.
>=20
> 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
>=20
> - Stig Venaas, Ralph Droms
>   dhc WG chairs
>=20
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg
>=20
>=20
> --
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/

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



From dhcwg-bounces@ietf.org Sun Jul 15 10:35: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 1IA5Bw-0002QN-4h; Sun, 15 Jul 2007 10:35:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IA5Bv-0002NG-9a
	for dhcwg@ietf.org; Sun, 15 Jul 2007 10:35:19 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IA5Br-0004XB-OK
	for dhcwg@ietf.org; Sun, 15 Jul 2007 10:35:19 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 15 Jul 2007 10:35:15 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CADbNmUZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,540,1175486400"; 
	d="scan'208"; a="65210276:sNHT47583410"
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 l6FEZF1b005171; 
	Sun, 15 Jul 2007 10:35:15 -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 l6FEZFWI007482; 
	Sun, 15 Jul 2007 14:35:15 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); 
	Sun, 15 Jul 2007 10:35:14 -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 vpn-option and agent-vpn-id drafts
Date: Sun, 15 Jul 2007 10:35:51 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB2104814125@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <469384EA.3050301@uninett.no>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] dhc wg last call on vpn-option and agent-vpn-id drafts
Thread-Index: AcfC84Q+DHEL7GsvT1qDVamS9QVq0AD9Daxg
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "Stig Venaas" <stig.venaas@uninett.no>, "dhcwg" <dhcwg@ietf.org>
X-OriginalArrivalTime: 15 Jul 2007 14:35:14.0712 (UTC)
	FILETIME=[5B726180:01C7C6ED]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=8387; t=1184510115;
	x=1185374115; 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]=20dhc=20wg=20last=20call=20on=20vpn-option=20
	and=20agent-vpn-id=20drafts |Sender:=20
	|To:=20=22Stig=20Venaas=22=20<stig.venaas@uninett.no>,
	=20=22dhcwg=22=20<d hcwg@ietf.org>;
	bh=5mAiXERtJ99Jdb/fuWQF6X2tAX1SBDgpfAW2j2F6PJQ=;
	b=agrNYQAtYooe1jaZti4s3UfMRkL35Le+5cZz/zMRbxXZpH1EsJnZF5IYp5VpGLhrPDE3o8WH
	9DGgsMYoqPelT6v2DSUtGAcbz0/Q+bzi12Ab0X+BzXiXPE0oHQOfIKQL;
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: bacfc6c7290e34d410f9bc22b825ce96
Cc: "Jay Kumarasamy \(jayk\)" <jayk@cisco.com>,
	"Richard Johnson \(raj\)" <raj@cisco.com>,
	"Mark Stapp \(mjs\)" <mjs@cisco.com>,
	"Kim Kinnear Jr. \(kkinnear\)" <kkinnear@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

Some comments on draft-ietf-dhc-vpn-option-06.txt (and also on
draft-ietf-dhc-agent-vpn-id-04.txt below):

1. I'm not sure why the document uses TBD for the option code when it
clearly should be using 221 as that it what the document is requesting -
that 221 be allocated for this option. This applies to all TBD usages in
the document.

2. In section 1. Introduction, 2nd paragraph:

   If the allocation is being done through a DHCP relay, then a relay
   suboption could be included.  In some cases, however an IP address is
   being sought by a DHCP proxy on behalf of a client (would may be
   assigned the address via a different protocol).  In this case, there
   is a need to include VSS information relating to the client as a DHCP
   option.

I don't understand what "would may be" means.

3. In section 1. Introduction, 3rd paragraph:

  addresses are acquired via DHCP and then given to the remove customer
                                                        ^^^^^^ ->
remote?

I also think PPP and IPCP should have references to the documents (or at
least be defined)?

4. In section 1. Introduction, 4th paragraph:

   This memo defines a new DHCP [2] option, the VSS Information option

Well, "This memo defines existing usage for the VSS Information option"?

As this is not a standard track document, I think it should be clear
that it is defining existing usage?

5. In section 3. VSS Information Definition

   The second type of identifier which can be placed in the VSS
   Information Option is an RFC2685 VPN-ID [4], which is typically 14
   hex digits in length (though it can be any length as far as the VSS
   Information Option is concerned).

   ...

   If the type field is set to one (1), it indicates that all following
   bytes should be interpreted in agreement with RFC2685 as a VPN
   Identifier, typically 14 hex digits.

This "14 hex digits in length" is a bit odd. I presume the 14 is decimal
and the hex digits are the ASCII representation of the digits (or are
they nibble encoded)? I think this should be clarified.

If we look at RFC 2685, it defines 7 octets of data (3 of VPN OUI
followed by 4 of VPN index). So, perhaps it would be best to specify
this as "7 octets of the RFC2685 VPN-ID"?

6. In section 3. VSS Information Definition

For clarity:

   In the event that a VSS Informmation Option and a VSS Information
   Relay Suboption are both received in a particular DHCP client packet,
   the information from the VSS Information Suboption MUST be used in
   preference to the information in the VSS Information Option.

Best if "VSS Information Suboption" was "VSS Information Relay
Suboption".

Though:
- draft-ietf-dhc-agent-vpn-id-04.txt uses "sub-option", not "suboption",
so perhaps sub-option should be used.
- draft-ietf-dhc-agent-vpn-id-04.txt also uses "Virtual Subnet Selection
sub-option" so perhaps the "Relay" part should be removed?
- I think a reference to the sub-option document should be added here
for the first usage?

7. Might be nice in section 2 or elsewhere to make a reference to the
terminology defined in draft-ietf-dhc-agent-vpn-id-04.txt?


NOTE: Some of the above comments also apply to
draft-ietf-dhc-agent-vpn-id-04.txt (such as the "14 hex digits" issue).


Some comments on draft-ietf-dhc-agent-vpn-id-04.txt (excluding the above
issues that also apply to it):

1. In the Abstract:

  If one DHCP server wishes to offer service to DHCP clients on those
     ^^^ -> replace with "a"?

Same in 1. Introduction:

   VPNs contain DHCP clients, and there is a desire to allow one DHCP
                                                             ^^^ a?
2. Section 2 should have a title? Terminology?

I also wonder whether the word "Internet" should be removed from the
definitions?

And:

      o "VPN Identifier"

        The VPN-ID is defined by [RFC 2685] to be a sequence of 14 hex
        digits.

Again, no where in 2685 is "14 hex digits" used. I'd use 7 octet
identifier?

3. In section 3. Virtual Subnet Selection Sub-option Definition

   The second type of identifier which can be placed in the virtual-
   subnet-selection sub-option is an RFC2685 VPN-ID [RFC 2685], which is
   typically 14 hex digits in length (though it can be any length as far
   as the virtual-subnet-selection sub-option is concerned).

The statement in parenthesis is rather odd as RFC 2685 clearly defines
this as 7-octets so why would this be useable for anything else. I think
it best if this text is removed.

4. General issue

This doucment is titled "Virtual Subnet Selection Sub-Option", yet in
the text it generally uses "virtual-subnet-selection sub-option".
Perhaps this should be consistent (either use the hyphen or capitalize?)
Note that the draft-ietf-dhc-vpn-option-06.txt justs used "Virtual
Subnet Selection" or "VSS information".

5. Here's a bit of an odd situation:

In section 3:

   In the event that a virtual-subnet-selection option and a virtual-
   subnet-selection sub-option are both received in a particular DHCP
   client packet, the information from the virtual-subnet-selection
   sub-option MUST be used in preference to the information in the
   virtual-subnet-selection option.

So, let's think this through ... The client adds the option and so does
the relay. The server uses the relay's option. Presumably, the server
doesn't echo the client's option. So, the client will IGNORE the
response from the server. Is this expected?

6. In 4. Security:

   The virtual-subnet-selection sub-option could be used by a client in
   order to obtain an IP address from a VPN other than the one on which
   it resides.  This attack can be partially prevented by the relay
   agent not forwarding any DHCP packet which already contains a relay-
   agent-information option.

No, the sub-option is NOT used by a client; it is used by the relay.

7. In 5. IANA Considerations:

8.  IANA Considerations

   IANA has assigned the value of TBD for the VPN Identifier sub-option
   from the DHCP Relay Agent Sub-options space [RFC 3046] for the VPN
   Identifier sub-option defined in Section 3.

Isn't IANA being REQUESTED to assign a value?

- Bernie

-----Original Message-----
From: Stig Venaas [mailto:stig.venaas@uninett.no]=20
Sent: Tuesday, July 10, 2007 9:09 AM
To: dhcwg
Subject: [dhcwg] dhc wg last call on vpn-option and agent-vpn-id drafts

This message announces a wg last call on two drafts. They are

Virtual Subnet Selection Option <draft-ietf-dhc-vpn-option-06.txt>

and

Virtual Subnet Selection Sub-Option for the Relay Agent Information=20
Option for DHCPv4 <draft-ietf-dhc-agent-vpn-id-04.txt>

The last call will conclude at 1700EST on Sun, 2007-07-22.

Please respond to this WG last call.  If you support acceptance of the
documents without change, respond with a simple acknowledgment, so that
support for the documents 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.

draft-ietf-dhc-vpn-option defines a new DHCP option for passing Virtual
Subnet Selection (VSS) information between the DHCP client and the DHCP
server.  It is intended for use primarily by DHCP proxy clients in
situations where VSS information needs to be passed to the DHCP server
for proper address allocation to take place.  This document documents
option usage in line with the option reclassification in RFC 3942.
This draft is available as
http://www.ietf.org/internet-drafts/draft-ietf-dhc-vpn-option-06.txt

draft-ietf-dhc-agent-vpn-id defines a new relay-agent-information option
sub-option used by a relay agent to tell the DHCP server important
information about the VPN (called the Virtual Subnet Selection
information, or VSS) for every DHCP request it passes on to the DHCP
server, and is also used to properly forward any DHCP reply that the
DHCP server sends back to the relay agent.
This draft is available as
http://www.ietf.org/internet-drafts/draft-ietf-dhc-agent-vpn-id-04.txt

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 Sun Jul 15 22:25: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 1IAGGo-0007N3-GC; Sun, 15 Jul 2007 22:25:06 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IAGGm-0007Mu-SP
	for dhcwg@ietf.org; Sun, 15 Jul 2007 22:25:04 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IAGGm-00084V-6C
	for dhcwg@ietf.org; Sun, 15 Jul 2007 22:25:04 -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 <0JL900JB02OSBI@mailout3.samsung.com> for dhcwg@ietf.org;
	Mon, 16 Jul 2007 11:24:28 +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 <0JL900MYJ2OUKY@ms5.samsung.com> for dhcwg@ietf.org; Mon,
	16 Jul 2007 11:24:30 +0900 (KST)
Content-return: prohibited
Date: Mon, 16 Jul 2007 02:24:30 +0000 (GMT)
From: Heejin Jang <heejin.jang@samsung.com>
Subject: Re: Re: [dhcwg] Re: Discussion for hiopt draft
To: David_Hankins@isc.org
Message-id: <28967050.270901184552670199.JavaMail.weblogic@ep_ml29>
MIME-version: 1.0
MIME-version: 1.0
X-Priority: 3
Msgkey: 20070716022430197@heejin.jang
X-MTR: 20070716022430197@heejin.jang
X-EPLocale: ko_KR.windows-1252
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
X-EPApproval-Locale: 
X-Spam-Score: 2.8 (++)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: dhcwg@ietf.org
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="===============0551151981=="
Errors-To: dhcwg-bounces@ietf.org

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

DQpIaSwgRGF2aWQuDQoNClRoYW5rcyBmb3Igc2VuZGluZyBteSBtYWlsIGFnYWluIGVuY29kZWQg
aW4gdGV4dC4NCkFzIEkgc2VudCBhIG1haWwgcHJldmlvdXNseSAoYXMgYSByZXNwb25zZSB0byAg
eW91ciBmaXJzdCBjb21tZW50cyksIA0Kd2UnbGwgc3RhcnQgdGhlIHN1Yi1vcHQtY29kZSBmcm9t
IDEgbm90IDAgYXMgeW91IHN1Z2dlc3RlZCBpZiB0aGUgMm5kIG1ldGhvZCBpcyBmaW5hbGx5IGRl
Y2lkZWQuIDopDQoNCi0gUmVnYXJkcywgDQpIZWVqaW4uDQoNCiANCg0KLS0tLS0tLSBPcmlnaW5h
bCBNZXNzYWdlIC0tLS0tLS0NClNlbmRlciA6IEhlZWppbiBKYW5nPGhlZWppbi5qYW5nQHNhbXN1
bmcuY29tPiBSJkQgU3RhZmYgTWVtYmVyL0NvbW11bmljYXRpb24gJiBOZXR3b3JraW5nIExhYi9T
YW1zdW5nIEFkdmFuY2VkIEluc3RpdHV0ZSBvZiBUZWNobm9sb2d5DQpEYXRlICAgOiAyMDA3LTA3
LTE2IDExOjEyDQpUaXRsZSAgOiBSZTogW2RoY3dnXSBSZTogRGlzY3Vzc2lvbiBmb3IgaGlvcHQg
ZHJhZnQNCg0KDQoNCiANCiANCg0KLS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tLS0NClNl
bmRlciA6IERhdmlkIFcuIEhhbmtpbnM8RGF2aWRfSGFua2luc0Bpc2Mub3JnPg0KRGF0ZSAgIDog
MjAwNy0wNy0xMCAwMjoxNA0KVGl0bGUgIDogW2RoY3dnXSBSZTogRGlzY3Vzc2lvbiBmb3IgaGlv
cHQgZHJhZnQNCg0KVGhpcyBtZXNzYWdlIGNhbWUgdGhyb3VnaCBhbGwgaW4gSFRNTCwgc28gSSYm
IzM1OzM5O20gdW5zdXJlIGlmIG90aGVyIGZvbGtzIHdlcmUNCmFibGUgdG8gcmVhZCBpdCAtIEkm
JiMzNTszOTt2ZSBpbmNsdWRlZCBpdCBpbiBlbnRpcmV0eSBiZWxvdyByYXRoZXIgdGhhbiBqdXN0
DQp0aGUgb25lIHBpZWNlIHRoYXQgSSB3aXNoIHRvIHJlc3BvbmQgdG8uDQoNCkFsbCBJIHdhbnRl
ZCB0byBzYXkgaXMgSSBhZ3JlZSB3aXRoIHlvdXIgZWxlY3Rpb24gdG8gdXNlIHRoZSBzZWNvbmQN
Cm1ldGhvZCB0aGF0IHlvdSYmIzM1OzM5O3ZlIG91dGxpbmVkLiAgSSB1bmRlcnN0YW5kIHRoZSBI
SU9QVCBvcHRpb25zIHRvIGJlDQptdWx0aXBsZSBkaXNwYXJhdGUgdmFsdWVzIHRoYXQgYXJlICJh
bHdheXMgc2VudCIgd2hlbiB0aGV5IGFyZQ0KYXZhaWxhYmxlLCBhbmQgbm90IHN1YmplY3QgdG8g
cGFyYW1ldGVyIHJlcXVlc3QuDQoNCkJ1dCBJJiYjMzU7Mzk7ZCBsaWtlIHRvIHJlaXRlcmF0ZSBh
IHJlcXVlc3QgdGhhdCB5b3Ugc3RhcnQgZnJvbSBzdWItb3B0aW9uDQpjb2RlIDEuICBBbGwgb3Ro
ZXIgc3ViIG9wdGlvbiBzcGFjZXMgc28gZmFyIGhhdmUgZG9uZSB0aGlzLCBhbmQgdGhlDQp0b3Ag
bGV2ZWwgREhDUCBjb2RlcyB0aGVtc2VsdmVzIGhhdmUgYXZvaWRlZCB0aGUgdXNlIG9mIHplcm8s
IEkgdGhpbmsNCmR1ZSB0byBpdHMgJiYjMzU7Mzk7bWFnaWMgdmFsdWUmJiMzNTszOTsgYW5jZXN0
cnkgaW4gREhDUHY0LCBhbmQgdGhlIHByb3BlbnNpdHkgZm9yDQpib3RoIHRoZXNlIHByb3RvY29s
cyB0byBiZSBzZXJ2ZWQgd2l0aCBjb21tb24gc291cmNlY29kZS4NCg0KSSYmIzM1OzM5O2QgaGF2
ZSB0byBhZGQgYW5vdGhlciBicmFuY2ggdG8gb3VyIHBhcnNpbmcgbG9vcCB0byBzdXBwb3J0IGNv
ZGVzDQpiZWdpbm5pbmcgd2l0aCB6ZXJvLCB3aGljaCBpcyBkb2FibGUsIGJ1dCB0aGVyZSBoYXNu
JiYjMzU7Mzk7dCBiZWVuIGFueSBvdGhlcg0KcmVhc29uIHRvIGRvIHNvIHlldC4NCg0KDQpPbiBT
YXQsIEp1bCAwNywgMjAwNyBhdCAwODo1NDoxNEFNICswMDAwLCBIZWVqaW4gSmFuZyB3cm90ZToN
Cj4gSGksIEJlcm5pZSwgRGF2aWQgYW5kIGZvbGtzLg0KPiANCj4gDQo+IA0KPiBGb3IgdGhlIHNh
a2Ugb2YgY2xhcml0eSwgYSBESENQdjYgJiYjMzU7Mzk7bWFpbiBvcHRpb24mJiMzNTszOTsgaW4g
bXkgcHJldmlvdXNseSBzZW50IG1haWxzIGlzDQo+IHRoZSBvcHRpb24NCj4gDQo+IHdob3NlIG9w
dGlvbi1jb2RlIGlzIGFzc2lnbmVkIGZyb20gdGhlIHBvb2wgb2YgdGhlIHJlZ3VsYXIgMTYtYml0
IERIQ1B2NiBvcHRpb24NCj4gY29kZXMNCj4gDQo+IChodHRwOi8vd3d3LmlhbmEub3JnL2Fzc2ln
bm1lbnRzL2RoY3B2Ni1wYXJhbWV0ZXJzKSBpbnN0ZWFkIG9mIHN0YXJ0aW5nIGZyb20NCj4gc3Vi
LW9wdC1jb2RlIDAuDQo+IA0KPiBJdCBkb2VzIG5vdCBtZWFuIHRoYXQgdGhlIG1haW4gb3B0aW9u
IGNhbm5vdCBiZSB1c2VkIHdpdGhpbiBhbm90aGVyIG9wdGlvbi4NCj4gDQo+IChTbywgQmVybmll
ICYgRGF2aWQsIGl0IGlzIGRpZmZlcmVudCBmcm9tIHRoZSB0b3AtbGV2ZWwgb3B0aW9uIGlmIHlv
dSBtZWFudA0KPiB0aGF0IGEgdG9wLWxldmVsIG9wdGlvbiBpcw0KPiANCj4gdGhlIG9wdGlvbiB3
aGljaCBjYW5ub3QgYmUgaW5jbHVkZWQgd2l0aGluIGFub3RoZXIgb3B0aW9uKS4NCj4gDQo+IA0K
PiANCj4gU28gaWYgaXQgZG9lcyBub3QgbWFrZSBhbnkgYmlnIGRpZmZlcmVuY2UgYmV0d2VlbiB0
aGUgZm9sbG93aW5nIDEpICYgMikgZnJvbQ0KPiB0aGUgcGVyc3BlY3RpdmUgb2YNCj4gDQo+IGRo
Y3B2NiBkZXNpZ24gcHJpbmNpcGxlLCBJIHByZWZlciB0byB1c2UgMikuDQo+IA0KPiAoQW55d2F5
IGl0IHdpbGwgYmUgZGVjaWRlZCBhbHNvIHdpdGggdGhlIGNvbnNlbnN1cyBvZiBNSVA2IFdHKQ0K
PiANCj4gDQo+IA0KPiBGb3IgYSBjdXJyZW50IDgtYml0IHN1Ym9wdGlvbiBpbiByZWxheSAmIEhO
IGluZm9ybWF0aW9uIG9wdGlvbiBpbiBoaW9wdC0wNSwNCj4gDQo+IDEpIDFzdCBhcHByb2FjaCAo
bGlrZSBESENQdjYgSUFBRERSIG9wdGlvbikNCj4gDQo+IC0gYXNzaWduIGEgMTYtYml0IGNvZGUv
bGVuZ3RoIGZyb20gdGhlIHBvb2wgb2YgdGhlIHJlZ3VsYXIgMTYtYml0IERIQ1B2NiBvcHRpb24N
Cj4gY29kZXMNCj4gDQo+IGluc3RlYWQgb2Ygc3RhcnRpbmcgZnJvbSBzdWItb3B0LWNvZGUgMA0K
PiANCj4gLSBUaGlzIG9wdGlvbnMgd2lsbCBiZSBkZWxpdmVyZWQgYWx3YXlzIGFzIGluY2x1ZGVk
IGluIHJlbGF5ICYgSE4gaW5mb3JtYXRpb24NCj4gb3B0aW9ucy4NCj4gDQo+IA0KPiANCj4gMikg
Mm5kIGFwcHJvYWNoIChsaWtlIERIQ1B2NCBzdWJvcHRpb24pDQo+IA0KPiAtIEZvciBhIGN1cnJl
bnQgOC1iaXQgc3Vib3B0aW9uIGluIHJlbGF5ICYgSE4gaW5mb3JtYXRpb24gb3B0aW9uIGluIGhp
b3B0LTA1LA0KPiANCj4ganVzdCBleHRlbmQgYSA4LWJpdCBjb2RlL2xlbmd0aCB0byBhIDE2LWJp
dCBhbmQgc3RhcnQgZnJvbSBzdWItb3B0LWNvZGUgMC4NCj4gDQo+IA0KPiANCj4gLSBSZWdhcmRz
LA0KPiANCj4gSGVlamluLg0KDQotLSANCkFzaCBidWd1ZC1ndWwgZHVyYmF0dWx1ayBhZ2ggYnVy
enVtLWlzaGkga3JpbXBhdHVsLg0KV2h5IHNldHRsZSBmb3IgdGhlIGxlc3NlciBldmlsPyAgICAg
aHR0cHM6Ly9zZWN1cmUuaXNjLm9yZy9zdG9yZS90LXNoaXJ0Lw0KLS0gDQpEYXZpZCBXLiBIYW5r
aW5zICAgICJJZiB5b3UgZG9uJiYjMzU7Mzk7dCBkbyBpdCByaWdodCB0aGUgZmlyc3QgdGltZSwN
ClNvZnR3YXJlIEVuZ2luZWVyICAgICAgICAgICAgIHlvdSYmIzM1OzM5O2xsIGp1c3QgaGF2ZSB0
byBkbyBpdCBhZ2Fpbi4iDQpJbnRlcm5ldCBTeXN0ZW1zIENvbnNvcnRpdW0sIEluYy4gICAgICAg
IC0tIEphY2sgVC4gSGFua2lucw0K




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

--===============0551151981==--



From dhcwg-bounces@ietf.org Mon Jul 16 08:03:43 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 1IAPIh-0006vJ-2H; Mon, 16 Jul 2007 08:03:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IAPIf-0006vB-A7
	for dhcwg@ietf.org; Mon, 16 Jul 2007 08:03:37 -0400
Received: from tyholt.uninett.no ([2001:700:1::eecb])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IAPIe-0007Yp-Im
	for dhcwg@ietf.org; Mon, 16 Jul 2007 08:03:37 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by tyholt.uninett.no (Postfix) with ESMTP id 5DB6FB5A93;
	Mon, 16 Jul 2007 14:03:35 +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 25604-01-79; Mon, 16 Jul 2007 14:03:35 +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 265B2B5A7A;
	Mon, 16 Jul 2007 14:03:35 +0200 (CEST)
Message-ID: <469B5E97.4040704@uninett.no>
Date: Mon, 16 Jul 2007 14:03:35 +0200
From: Stig Venaas <stig.venaas@uninett.no>
User-Agent: Thunderbird 2.0.0.4 (X11/20070627)
MIME-Version: 1.0
To: "David W. Hankins" <David_Hankins@isc.org>
Subject: Re: [dhcwg] dhc wg last call on  draft-ietf-dhc-pxelinux-01
References: <46823079.5050405@uninett.no>	<8E296595B6471A4689555D5D725EBB2104619BF1@xmb-rtp-20a.amer.cisco.com>
	<20070706192823.GF8503@isc.org>
In-Reply-To: <20070706192823.GF8503@isc.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: 41c17b4b16d1eedaa8395c26e9a251c4
Cc: DHC WG <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

We did not get much input during the wglc, but since this is just an
informational document documenting an existing protocol we believe it is 
sufficient.

I think it's good if you can post another revision with the minor 
changes discussed below before we pass it on to the IESG. Also please
run it through the idnits tool to check that there are no issues.

Stig

David W. Hankins wrote:
> On Fri, Jun 29, 2007 at 05:19:28PM -0400, Bernie Volz (volz) wrote:
>> I fully support this document moving forward.
> 
> Thank you, Bernie.
> 
>> 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".
> 
> I think you're right, and rather wonder why I didn't think of that
> first.
> 
> The objective is just to 'mark the landmine'.  I've made the changes
> in my sources
> 
>> 1. Rename section 6 to "Reboot Time Option".
> 
> Fixed in my sources.
> 
>> 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 sort of agree.  Both the old and new titles aren't very informative
> if you don't know what 'option' means contextually.
> 
>   <title abbrev="PXELINUX Options">Dynamic Host Configuration Protocol
> 	Options Used by PXELINUX</title>
> 
> ?
> 
> 
> More nits;
> 
> Per Stig (some time ago), I simplified the abstract (so as to remove
> references).  This does mean that I had to place references in the
> introduction.
> 
> Some capitalizations in the introduction's summary list of options
> being documented.
> 
> 
>> 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?
> 
> I don't know.  If we get too many more nits, I wouldn't object to
> respinning it just to simplify the process for the editor.
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> 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 Jul 19 18:46: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 1IBelP-0005GP-BC; Thu, 19 Jul 2007 18:46:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBelO-0005GI-6Z
	for dhcwg@ietf.org; Thu, 19 Jul 2007 18:46:26 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBelN-0004ea-NI
	for dhcwg@ietf.org; Thu, 19 Jul 2007 18:46:26 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 0E27A5A6E5; Thu, 19 Jul 2007 15:46:24 -0700 (PDT)
Date: Thu, 19 Jul 2007 15:46:24 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: DHC WG <dhcwg@ietf.org>
Message-ID: <20070719224624.GG15872@isc.org>
Mime-Version: 1.0
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Subject: [dhcwg] draft-dhankins-dhcp-option-guidelines-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>
Content-Type: multipart/mixed; boundary="===============0136840550=="
Errors-To: dhcwg-bounces@ietf.org


--===============0136840550==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="0vzXIDBeUiKkjNJl"
Content-Disposition: inline


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

I missed the deadline for I-D submissions (by a day), so I've finally
put it up here in the meantime:

http://www.isc.org/sw/dhcp/drafts/draft-dhankins-dhcp-option-guidelines-01.=
txt

New topics or suggestions to improve or reorganize current topics are
more than welcome.

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

--0vzXIDBeUiKkjNJl
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFGn+nAcXeLeWu2vmoRAgg5AJ96Wp8l9OSanNJ4FxFeeZfHs9yF3QCeIvsF
UZZ/nSfDr6mcbSLj2rYYTBk=
=MN6P
-----END PGP SIGNATURE-----

--0vzXIDBeUiKkjNJl--


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

--===============0136840550==--




From dhcwg-bounces@ietf.org Fri Jul 20 13:33: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 1IBwM7-0003M1-Rk; Fri, 20 Jul 2007 13:33:31 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBwM7-0003Lg-5H
	for dhcwg@ietf.org; Fri, 20 Jul 2007 13:33:31 -0400
Received: from web30812.mail.mud.yahoo.com ([68.142.201.138])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IBwM6-0007yM-PA
	for dhcwg@ietf.org; Fri, 20 Jul 2007 13:33:31 -0400
Received: (qmail 50670 invoked by uid 60001); 20 Jul 2007 17:33:30 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
	b=MOT/VG49l9/vlOykFo9l2wGhTYtpUSQZpZpUQFPWbcK2FBIJuUdvF2xMYeEluPtoFwFSw8FQwGB6lW2XDZAjcf1Ar5sBO3STMJp7XQtXRg03ldaccIy2PCovfHPAcEhCuivypohEWYrRs7sTo+YAMCX1JSHOjJbOknCY12+tOKA=;
X-YMail-OSG: M8oxlKYVM1mKAkji7XS2S5OoetIpCzvHDeNgEdH5mi3TETVuBe759MWbZQEyuiPpHi3ENrqlOUgcPLDl2HzxOkQK054ERn0hmX8mmLGTWeOUX0wkASk-
Received: from [221.134.214.250] by web30812.mail.mud.yahoo.com via HTTP;
	Fri, 20 Jul 2007 10:33:30 PDT
X-Mailer: YahooMailRC/651.41 YahooMailWebService/0.7.119
Date: Fri, 20 Jul 2007 10:33:30 -0700 (PDT)
From: RamaSubramanian KrishnaMurthi <ramasubbu_sk@yahoo.com>
To: dhcwg@ietf.org
MIME-Version: 1.0
Message-ID: <150052.50110.qm@web30812.mail.mud.yahoo.com>
X-Spam-Score: 2.2 (++)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Subject: [dhcwg] DHCPv6 Server IP address.
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="===============1750572049=="
Errors-To: dhcwg-bounces@ietf.org

--===============1750572049==
Content-Type: multipart/alternative; boundary="0-1458761074-1184952810=:50110"

--0-1458761074-1184952810=:50110
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

How can I know the DHCPv6 Server IP address on stateless and statefull mode=
? In DHCPv4, in every DHCP packet server will send its IPaddress in the sia=
ddr  field. In DHCPv6, in which field/option the sever will send its IPv6 a=
ddress?=0A =0AThanks=0A-RamaSubbu SK=0A=0A=0A       =0A____________________=
________________________________________________________________=0AYahoo! o=
neSearch: Finally, mobile search =0Athat gives answers, not web links. =0Ah=
ttp://mobile.yahoo.com/mobileweb/onesearch?refer=3D1ONXIC
--0-1458761074-1184952810=:50110
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:verdana, helvetica, sans-serif;font-size=
:10pt"><DIV></DIV>=0A<DIV>How can I know the DHCPv6 Server IP address on st=
ateless and statefull mode? In&nbsp;DHCPv4, in every DHCP packet server wil=
l send its IPaddress in the siaddr&nbsp;&nbsp;field.&nbsp;In DHCPv6, in whi=
ch field/option the sever will send its IPv6 address?<BR>&nbsp;</DIV>=0A<DI=
V><FONT color=3D#bf005f>Thanks</FONT></DIV>=0A<DIV>-<A href=3D"http://space=
s.msn.com/ramasubbu" target=3D_blank rel=3Dnofollow>RamaSubbu SK</A>&nbsp;<=
IMG src=3D"http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/14.gif"></DIV=
>=0A<DIV></DIV></div><br>=0A      <hr size=3D1>Luggage? GPS? Comic books? <=
br>=0ACheck out fitting <a href=3D"http://us.rd.yahoo.com/evt=3D48249/*http=
://search.yahoo.com/search?fr=3Doni_on_mail&p=3Dgraduation+gifts&cs=3Dbz"> =
gifts for grads</a> at Yahoo! Search.</body></html>
--0-1458761074-1184952810=:50110--


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

--===============1750572049==--




From dhcwg-bounces@ietf.org Fri Jul 20 14:12: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 1IBwxQ-0002dV-3o; Fri, 20 Jul 2007 14:12:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBwxO-0002dP-QH
	for dhcwg@ietf.org; Fri, 20 Jul 2007 14:12:02 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBwxO-0004Uc-8a
	for dhcwg@ietf.org; Fri, 20 Jul 2007 14:12:02 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id B5FBA5A6E7; Fri, 20 Jul 2007 11:12:01 -0700 (PDT)
Date: Fri, 20 Jul 2007 11:12:01 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: RamaSubramanian KrishnaMurthi <ramasubbu_sk@yahoo.com>
Subject: Re: [dhcwg] DHCPv6 Server IP address.
Message-ID: <20070720181201.GB30320@isc.org>
References: <150052.50110.qm@web30812.mail.mud.yahoo.com>
Mime-Version: 1.0
In-Reply-To: <150052.50110.qm@web30812.mail.mud.yahoo.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
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>
Content-Type: multipart/mixed; boundary="===============1715630503=="
Errors-To: dhcwg-bounces@ietf.org


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


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

On Fri, Jul 20, 2007 at 10:33:30AM -0700, RamaSubramanian KrishnaMurthi wro=
te:
> How can I know the DHCPv6 Server IP address on stateless and statefull
> mode?

The Server Unicast Option (RFC 3315 Setion 22.12).

However, the Server may not elect to transmit packets containing this
option, and if it does, it (or possibly some intervening device trying
to be too clever) may send a reply with a UseMulticast status code.

> In DHCPv4, in every DHCP packet server will send its IPaddress in the
> siaddr  field.

That is not correct.  RFC 2131 clarified the 'siaddr' field as the
address of the server to use in the "next step of the client's
bootstrap process", whatever that process may be (but probably
loading an executable image via TFTP).

Or are you looking for a DHCPv6 analogue of the next-server address?
That isn't the Unicast option.

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

--4bRzO86E/ozDv8r1
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFGoPrxcXeLeWu2vmoRAnslAJ9YM3MoBHerT8EqQaWVWXKoMccD2gCgnngZ
pgqeQ3+tYvXI2PQGysR3JLU=
=a+IO
-----END PGP SIGNATURE-----

--4bRzO86E/ozDv8r1--


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

--===============1715630503==--




From dhcwg-bounces@ietf.org Fri Jul 20 17:09: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 1IBzii-00064d-7n; Fri, 20 Jul 2007 17:09:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IBzig-00064X-C5
	for dhcwg@ietf.org; Fri, 20 Jul 2007 17:09:02 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IBzie-0008CX-Vs
	for dhcwg@ietf.org; Fri, 20 Jul 2007 17:09:02 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 20 Jul 2007 17:08:52 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAA/BoEZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,564,1175486400"; 
	d="scan'208"; a="126626151:sNHT5371431564"
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 l6KL8n0Y005713; 
	Fri, 20 Jul 2007 17:08:49 -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 l6KL8eEd002392; 
	Fri, 20 Jul 2007 21:08:49 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, 20 Jul 2007 17:08:23 -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 Server IP address.
Date: Fri, 20 Jul 2007 17:08:22 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB21048B7191@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <20070720181201.GB30320@isc.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] DHCPv6 Server IP address.
Thread-Index: AcfK+YCjnJMN6DSWRz6o3/Fp+4eukwAFweEA
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "RamaSubramanian KrishnaMurthi" <ramasubbu_sk@yahoo.com>
X-OriginalArrivalTime: 20 Jul 2007 21:08:23.0270 (UTC)
	FILETIME=[1B637060:01C7CB12]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3043; t=1184965729;
	x=1185829729; 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=20Server=20IP=20address.
	|Sender:=20
	|To:=20=22RamaSubramanian=20KrishnaMurthi=22=20<ramasubbu_sk@yahoo.com>;
	bh=/xot7w6ly6gUiONtJqikFmPXDd1Dg2+jWTXa6FCgrGs=;
	b=TSKLVFWD4aJBYPHoQfbagwOwHziieHTjDQ0x9lO6CuKzEXMIdGmLAHULl9g9Kran5x1R+tl5
	Zlg+4pqui4ORmB31MwGR0IC62AbIBGZ2reRBdi0hE7uuD/OHomRPaq2R;
Authentication-Results: rtp-dkim-1; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
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

RamaSubbu SK:

DHCPv6 clients normally will multicast their packets to the link-local
multicast address of ff02::1:2. Either the server will be on that link,
or a relay-agent will forward it on (to another relay-agent or the
server).

Thus all packets a client sends are MULTICAST to the ff02::1:2
link-local multicast address (with the IPv6 source address set to the
client's link-local address) and on-link responder (server or
relay-agent) will UNICAST the response packet to the client's link-local
address.

If a server sends a server-unicast option (which has the address of the
DHCPv6 server specified in it) to the client and the client has a
suitable address that it can use to communicate directly with the
server, it can then unicast. Note that if the server's address is a
global unicast address and the client doesn't have a global unicast
address, the client could NOT unicast.

The way a server is identified is by using a Server-ID option. In some
client packets (Solicit, for example) there is no Server-ID option
because the client doesn't know it yet (it is looking for a server to
use). In Request, Renew, Release messages, the client MUST supply the
server-id option from the Advertise it selected. All servers may receive
these requests, but only the one who's server-id matches the value
specified in the option will respond (the others drop the packet).

Note also that the server-id option MUST be used even if packets are
unicast by the client.

This is a bit different than in DHCPv4 where some client messages are
unicast directly between client and server.

- Bernie

-----Original Message-----
From: David W. Hankins [mailto:David_Hankins@isc.org]=20
Sent: Friday, July 20, 2007 2:12 PM
To: RamaSubramanian KrishnaMurthi
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] DHCPv6 Server IP address.

On Fri, Jul 20, 2007 at 10:33:30AM -0700, RamaSubramanian KrishnaMurthi
wrote:
> How can I know the DHCPv6 Server IP address on stateless and statefull
> mode?

The Server Unicast Option (RFC 3315 Setion 22.12).

However, the Server may not elect to transmit packets containing this
option, and if it does, it (or possibly some intervening device trying
to be too clever) may send a reply with a UseMulticast status code.

> In DHCPv4, in every DHCP packet server will send its IPaddress in the
> siaddr  field.

That is not correct.  RFC 2131 clarified the 'siaddr' field as the
address of the server to use in the "next step of the client's
bootstrap process", whatever that process may be (but probably
loading an executable image via TFTP).

Or are you looking for a DHCPv6 analogue of the next-server address?
That isn't the Unicast option.

--=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 Fri Jul 20 22:24: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 1IC4dt-0000x8-U8; Fri, 20 Jul 2007 22:24:25 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IC4dr-0000x0-TE
	for dhcwg@ietf.org; Fri, 20 Jul 2007 22:24:23 -0400
Received: from web30813.mail.mud.yahoo.com ([68.142.201.139])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IC4dq-0007ne-Pw
	for dhcwg@ietf.org; Fri, 20 Jul 2007 22:24:23 -0400
Received: (qmail 83598 invoked by uid 60001); 21 Jul 2007 02:24:22 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
	b=Z//7DpIXU+zZkpW+CWBJp0v8+rg9QAjZ1oaY7zIsS2B7hLEmjOhmpmA838fcV7Ey9sAZVya/F7WtUFtzUeQ1nnl0YegS5Sikc4W7fxcXjRHzE6GeCIAN99wSycIdoLdcrKVwTD+MC5lK+FOY1G9dz2OU9NZlXHyTRP9f79hsbrY=;
X-YMail-OSG: vKcS7.gVM1nW3FFQgmBBGXiBZ01WxhE_U4Q1N9vtEAMVhdYyWENOvJ_voQkV1bPpGU7QK7w3goEKaffL9BvlfOEAIdxioNaN12eQh0SORYxrXTeZQy8-
Received: from [221.134.213.76] by web30813.mail.mud.yahoo.com via HTTP;
	Fri, 20 Jul 2007 19:24:21 PDT
X-Mailer: YahooMailRC/651.41 YahooMailWebService/0.7.119
Date: Fri, 20 Jul 2007 19:24:21 -0700 (PDT)
From: RamaSubramanian KrishnaMurthi <ramasubbu_sk@yahoo.com>
Subject: Re: [dhcwg] DHCPv6 Server IP address.
To: "Bernie Volz \(volz\)" <volz@cisco.com>, dhcwg@ietf.org
MIME-Version: 1.0
Message-ID: <187405.83362.qm@web30813.mail.mud.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
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>
Content-Type: multipart/mixed; boundary="===============0729382031=="
Errors-To: dhcwg-bounces@ietf.org

--===============0729382031==
Content-Type: multipart/alternative; boundary="0-583221761-1184984661=:83362"

--0-583221761-1184984661=:83362
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Hi,=0AThanks a lot for detailed description.=0AIf the Server sends Unicast =
Option is it must that server should support Unicast feature. Why I was ask=
ing this question is from the Client we could n't find from which DHCPServe=
r the client has got the Ipaddress. If DHCP client has got IP address from =
a rogue DHCP server then it becomes cumbersome to find from which DHCPServe=
r the client has got the configuration options for both stateless & statefu=
ll mode.=0A=0AYours ever=0A-RamaSubbu SK =0A=0A=0A=0A----- Original Message=
 ----=0AFrom: Bernie Volz (volz) <volz@cisco.com>=0ATo: RamaSubramanian Kri=
shnaMurthi <ramasubbu_sk@yahoo.com>=0ACc: dhcwg@ietf.org=0ASent: Saturday, =
July 21, 2007 2:38:22 AM=0ASubject: RE: [dhcwg] DHCPv6 Server IP address.=
=0A=0A=0ARamaSubbu SK:=0A=0ADHCPv6 clients normally will multicast their pa=
ckets to the link-local=0Amulticast address of ff02::1:2. Either the server=
 will be on that link,=0Aor a relay-agent will forward it on (to another re=
lay-agent or the=0Aserver).=0A=0AThus all packets a client sends are MULTIC=
AST to the ff02::1:2=0Alink-local multicast address (with the IPv6 source a=
ddress set to the=0Aclient's link-local address) and on-link responder (ser=
ver or=0Arelay-agent) will UNICAST the response packet to the client's link=
-local=0Aaddress.=0A=0AIf a server sends a server-unicast option (which has=
 the address of the=0ADHCPv6 server specified in it) to the client and the =
client has a=0Asuitable address that it can use to communicate directly wit=
h the=0Aserver, it can then unicast. Note that if the server's address is a=
=0Aglobal unicast address and the client doesn't have a global unicast=0Aad=
dress, the client could NOT unicast.=0A=0AThe way a server is identified is=
 by using a Server-ID option. In some=0Aclient packets (Solicit, for exampl=
e) there is no Server-ID option=0Abecause the client doesn't know it yet (i=
t is looking for a server to=0Ause). In Request, Renew, Release messages, t=
he client MUST supply the=0Aserver-id option from the Advertise it selected=
. All servers may receive=0Athese requests, but only the one who's server-i=
d matches the value=0Aspecified in the option will respond (the others drop=
 the packet).=0A=0ANote also that the server-id option MUST be used even if=
 packets are=0Aunicast by the client.=0A=0AThis is a bit different than in =
DHCPv4 where some client messages are=0Aunicast directly between client and=
 server.=0A=0A- Bernie=0A=0A-----Original Message-----=0AFrom: David W. Han=
kins [mailto:David_Hankins@isc.org] =0ASent: Friday, July 20, 2007 2:12 PM=
=0ATo: RamaSubramanian KrishnaMurthi=0ACc: dhcwg@ietf.org=0ASubject: Re: [d=
hcwg] DHCPv6 Server IP address.=0A=0AOn Fri, Jul 20, 2007 at 10:33:30AM -07=
00, RamaSubramanian KrishnaMurthi=0Awrote:=0A> How can I know the DHCPv6 Se=
rver IP address on stateless and statefull=0A> mode?=0A=0AThe Server Unicas=
t Option (RFC 3315 Setion 22.12).=0A=0AHowever, the Server may not elect to=
 transmit packets containing this=0Aoption, and if it does, it (or possibly=
 some intervening device trying=0Ato be too clever) may send a reply with a=
 UseMulticast status code.=0A=0A> In DHCPv4, in every DHCP packet server wi=
ll send its IPaddress in the=0A> siaddr  field.=0A=0AThat is not correct.  =
RFC 2131 clarified the 'siaddr' field as the=0Aaddress of the server to use=
 in the "next step of the client's=0Abootstrap process", whatever that proc=
ess may be (but probably=0Aloading an executable image via TFTP).=0A=0AOr a=
re you looking for a DHCPv6 analogue of the next-server address?=0AThat isn=
't the Unicast option.=0A=0A-- =0AAsh bugud-gul durbatuluk agh burzum-ishi =
krimpatul.=0AWhy settle for the lesser evil?     https://secure.isc.org/sto=
re/t-shirt/=0A-- =0ADavid W. Hankins    "If you don't do it right the first=
 time,=0ASoftware Engineer             you'll just have to do it again."=0A=
Internet Systems Consortium, Inc.        -- Jack T. Hankins=0A=0A=0A       =
=0A________________________________________________________________________=
____________=0AGet the Yahoo! toolbar and be alerted to new email wherever =
you're surfing.=0Ahttp://new.toolbar.yahoo.com/toolbar/features/mail/index.=
php
--0-583221761-1184984661=:83362
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:verdana, helvetica, sans-serif;font-size=
:10pt"><DIV></DIV>=0A<DIV>Hi,</DIV>=0A<DIV>Thanks a lot for detailed descri=
ption.</DIV>=0A<DIV>If the Server sends Unicast Option&nbsp;is it must that=
 server should support Unicast feature. Why I was asking this question is f=
rom the Client we could n't find from which DHCPServer the client has got t=
he Ipaddress. If DHCP client has got IP address from a rogue DHCP server th=
en it becomes cumbersome to find from which DHCPServer the client has got t=
he configuration options for both stateless &amp; statefull mode.</DIV>=0A<=
DIV>&nbsp;</DIV>=0A<DIV><FONT color=3D#bf005f>Yo</FONT><FONT color=3D#0000f=
f>ur</FONT><FONT color=3D#00ff80>s e</FONT><FONT color=3D#ff007f>ve</FONT>r=
</DIV>=0A<DIV>-<A href=3D"http://spaces.msn.com/ramasubbu" target=3D_blank =
rel=3Dnofollow>RamaSubbu SK</A>&nbsp;<IMG src=3D"http://us.i1.yimg.com/us.y=
img.com/i/mesg/tsmileys2/14.gif"></DIV>=0A<DIV style=3D"FONT-SIZE: 10pt; FO=
NT-FAMILY: verdana, helvetica, sans-serif"><BR><BR>=0A<DIV style=3D"FONT-SI=
ZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">----- Origi=
nal Message ----<BR>From: Bernie Volz (volz) &lt;volz@cisco.com&gt;<BR>To: =
RamaSubramanian KrishnaMurthi &lt;ramasubbu_sk@yahoo.com&gt;<BR>Cc: dhcwg@i=
etf.org<BR>Sent: Saturday, July 21, 2007 2:38:22 AM<BR>Subject: RE: [dhcwg]=
 DHCPv6 Server IP address.<BR><BR>=0A<DIV>RamaSubbu SK:<BR><BR>DHCPv6 clien=
ts normally will multicast their packets to the link-local<BR>multicast add=
ress of ff02::1:2. Either the server will be on that link,<BR>or a relay-ag=
ent will forward it on (to another relay-agent or the<BR>server).<BR><BR>Th=
us all packets a client sends are MULTICAST to the ff02::1:2<BR>link-local =
multicast address (with the IPv6 source address set to the<BR>client's link=
-local address) and on-link responder (server or<BR>relay-agent) will UNICA=
ST the response packet to the client's link-local<BR>address.<BR><BR>If a s=
erver sends a server-unicast option (which has the address of the<BR>DHCPv6=
 server specified in it) to the client and the client has a<BR>suitable add=
ress that it can use to communicate directly with the<BR>server, it can the=
n unicast. Note that if the server's address is a<BR>global unicast address=
 and the client doesn't have a global unicast<BR>address, the client could =
NOT unicast.<BR><BR>The way a
 server is identified is by using a Server-ID option. In some<BR>client pac=
kets (Solicit, for example) there is no Server-ID option<BR>because the cli=
ent doesn't know it yet (it is looking for a server to<BR>use). In Request,=
 Renew, Release messages, the client MUST supply the<BR>server-id option fr=
om the Advertise it selected. All servers may receive<BR>these requests, bu=
t only the one who's server-id matches the value<BR>specified in the option=
 will respond (the others drop the packet).<BR><BR>Note also that the serve=
r-id option MUST be used even if packets are<BR>unicast by the client.<BR><=
BR>This is a bit different than in DHCPv4 where some client messages are<BR=
>unicast directly between client and server.<BR><BR>- Bernie<BR><BR>-----Or=
iginal Message-----<BR>From: David W. Hankins [mailto:David_Hankins@isc.org=
] <BR>Sent: Friday, July 20, 2007 2:12 PM<BR>To: RamaSubramanian KrishnaMur=
thi<BR>Cc: dhcwg@ietf.org<BR>Subject: Re: [dhcwg] DHCPv6 Server IP
 address.<BR><BR>On Fri, Jul 20, 2007 at 10:33:30AM -0700, RamaSubramanian =
KrishnaMurthi<BR>wrote:<BR>&gt; How can I know the DHCPv6 Server IP address=
 on stateless and statefull<BR>&gt; mode?<BR><BR>The Server Unicast Option =
(RFC 3315 Setion 22.12).<BR><BR>However, the Server may not elect to transm=
it packets containing this<BR>option, and if it does, it (or possibly some =
intervening device trying<BR>to be too clever) may send a reply with a UseM=
ulticast status code.<BR><BR>&gt; In DHCPv4, in every DHCP packet server wi=
ll send its IPaddress in the<BR>&gt; siaddr&nbsp;&nbsp;field.<BR><BR>That i=
s not correct.&nbsp;&nbsp;RFC 2131 clarified the 'siaddr' field as the<BR>a=
ddress of the server to use in the "next step of the client's<BR>bootstrap =
process", whatever that process may be (but probably<BR>loading an executab=
le image via TFTP).<BR><BR>Or are you looking for a DHCPv6 analogue of the =
next-server address?<BR>That isn't the Unicast option.<BR><BR>--
 <BR>Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.<BR>Why settle for =
the lesser evil?&nbsp;&nbsp;&nbsp;&nbsp; <A href=3D"https://secure.isc.org/=
store/t-shirt/" target=3D_blank>https://secure.isc.org/store/t-shirt/</A><B=
R>-- <BR>David W. Hankins&nbsp;&nbsp;&nbsp;&nbsp;"If you don't do it right =
the first time,<BR>Software Engineer&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; you'll just have to do it again."<BR>Inte=
rnet Systems Consortium, Inc.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;-- Jack T. Hankins</DIV></DIV><BR></DIV></div><br>=0A      <hr size=3D1>G=
ot a little couch potato? <br>=0ACheck out fun <a href=3D"http://us.rd.yaho=
o.com/evt=3D48248/*http://search.yahoo.com/search?fr=3Doni_on_mail&p=3Dsumm=
er+activities+for+kids&cs=3Dbz">summer activities for kids.</a></body></htm=
l>
--0-583221761-1184984661=:83362--


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

--===============0729382031==--




From dhcwg-bounces@ietf.org Sat Jul 21 06:19:48 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 1ICC3o-0007q4-VO; Sat, 21 Jul 2007 06:19:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICC3n-0007pk-FK
	for dhcwg@ietf.org; Sat, 21 Jul 2007 06:19:39 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ICC3n-0004tU-3Y
	for dhcwg@ietf.org; Sat, 21 Jul 2007 06:19:39 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 21 Jul 2007 06:19:36 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAPt5oUZAZnme/2dsb2JhbAA
X-IronPort-AV: i="4.16,566,1175486400"; 
	d="scan'208"; a="126656053:sNHT26337742"
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 l6LAJalk019188
	for <dhcwg@ietf.org>; Sat, 21 Jul 2007 06:19:36 -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 l6LAJaWI001648
	for <dhcwg@ietf.org>; Sat, 21 Jul 2007 10:19:36 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 21 Jul 2007 06:19:36 -0400
Received: from [192.168.1.105] ([10.86.242.108]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 21 Jul 2007 06:19:36 -0400
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: 7bit
Message-Id: <A7D41F2F-36F7-425D-AA5E-4B92C4E942CE@cisco.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Date: Sat, 21 Jul 2007 06:19:45 -0400
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 21 Jul 2007 10:19:36.0181 (UTC)
	FILETIME=[A372CA50:01C7CB80]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1705; t=1185013176;
	x=1185877176; 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:=20*DRAFT*=20Agenda=20for=20IETF-69=20dhc=20WG=20meeting
	|Sender:=20 |To:=20dhcwg@ietf.org;
	bh=jMLNadMrQl3xToSqSsKbxXPPBnVxv7Lz9BxgNGY6DXQ=;
	b=lNu2QJAe9wbbUVXNj3T5K/REeqeFQMggDP7lk62V/60dp273iJ5k6ZXmwdmuY4jcjQ2K20ei
	yDjHSRRrWb5lGRDy/1oPigzU1SQgsWPZoXLjUwazCQsCSmoGuRhK6lcj;
Authentication-Results: rtp-dkim-1; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: [dhcwg] *DRAFT* Agenda for IETF-69 dhc WG meeting
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

Draft agenda is included below.  Please contact the chairs if you  
have a topic to be added to the agenda.

                        DHC WG DRAFT agenda - IETF 67
                         0900-1130 2007-07-23 (Mon)
                    (Last revised 2007-07-21 06:16 AM ET)
                    -------------------------------------

Administrivia                                   Venaas/Droms     10  
minutes
   Agenda bashing; blue sheets; scribe; Jabber scribe

Draft last call and adoption announcements      Venaas/Droms     05  
minutes

Progressing two drafts under RFC 3942           R. Droms         10  
minutes
   <draft-ietf-dhc-subnet-alloc-05>
   <draft-raj-dhc-tftp-addr-option-02>

Update to DHCP options guideline                D. Hankins       05  
minutes
   <draft-dhankins-dhcp-option-guidelines-00>
   Accept as WG work item?

Using DHCPv6 and AAA Server for mobile station PD
                                                 B. Sarikaya      15  
minutes
   <draft-sarikaya-16ng-prefix-delegation-01>
   WG input on DHCP-related I-D

Layer 2 relay agent and relay agent chaining    P. Kurapati      15  
minutes
   <draft-joshi-dhc-layer2-relay-agent-01>
   <draft-kurapati-dhc-relay-chaining-dhcpv4-01>
   Adopt as WG work items?

TAHI DHCPv6 Test tool for IPv6 Ready Logo       Hideshi E.       05  
minutes

Extensions to DHCPv6 for prefix and default router information
                                                 T. Chown         10  
minutes
   Initial discussion
                                                                  
-----------
                                                                  75  
minutes

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



From dhcwg-bounces@ietf.org Sun Jul 22 12:11: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 1ICe1S-0001Nt-1s; Sun, 22 Jul 2007 12:11:06 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ICe1Q-0001Nm-M6
	for dhcwg@ietf.org; Sun, 22 Jul 2007 12:11:04 -0400
Received: from the.hankinsfamily.info ([204.152.186.148]
	helo=hankinsfamily.info)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ICe1Q-0004yq-5G
	for dhcwg@ietf.org; Sun, 22 Jul 2007 12:11:04 -0400
Received: from hcf.isc.org (dhcp-1444.ietf69.org [130.129.20.68])
	(authenticated bits=0)
	by hankinsfamily.info (8.13.8/8.13.8) with ESMTP id l6MGB2Ms000641
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <dhcwg@ietf.org>; Sun, 22 Jul 2007 09:11:03 -0700
Received: by hcf.isc.org (Postfix, from userid 10200)
	id 790FB5F300; Sun, 22 Jul 2007 11:11:21 +0200 (CEST)
Date: Sun, 22 Jul 2007 11:11:21 +0200
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] DHCPv6 Server IP address.
Message-ID: <20070722091120.GA3728@isc.org>
References: <187405.83362.qm@web30813.mail.mud.yahoo.com>
Mime-Version: 1.0
In-Reply-To: <187405.83362.qm@web30813.mail.mud.yahoo.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: 1.9 (+)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
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="===============1292860800=="
Errors-To: dhcwg-bounces@ietf.org


--===============1292860800==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="0F1p//8PRICkK4MW"
Content-Disposition: inline


--0F1p//8PRICkK4MW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Jul 20, 2007 at 07:24:21PM -0700, RamaSubramanian KrishnaMurthi wro=
te:
> If the Server sends Unicast Option is it must that server should
> support Unicast feature.

My memory is that 3315 says it MUST NOT respond to unicasts unless
it has supplied the unicast option in a message.  Supplying the
Unicast option itself is optional (it's thought to be an operator-
configurable optimization).

I may be remembering that wrong, and I don't remember any other
normative language.

> Why I was asking this question is from the Client we could n't find
> from which DHCPServer the client has got the Ipaddress.

Simply, your only and most reliable indication of 'which server gave
me this address' is the server identifier.  Which is not an address.
And could be spoofed or altered.  Unless you're using authentication,
which you probably aren't.

Since the contents are never used to address or contact the server -
only to identify to which server the client is speaking - this may
very well be a useless blob of random zeroes and ones.

> If DHCP
> client has got IP address from a rogue DHCP server then it becomes
> cumbersome to find from which DHCPServer the client has got the
> configuration options for both stateless & statefull mode.

This is a misconfigured server, or a malcontent?

If it's just a misconfigured server, have a look at the server-id
option, hope that the server is still using the same MAC address
as hopefully is listed there.  If it doesn't use one of the LL types,
you'll have to use the source MAC of the packets you're receiving.

You can hopefully find a way to get to the server from its MAC.

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

--0F1p//8PRICkK4MW
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFGox84cXeLeWu2vmoRApUCAJ0WgQ86Y16y8otBVvtonIq7KYirxgCgo98F
7VyG3JhPPfkQvs4RL/ZPU9w=
=8fdn
-----END PGP SIGNATURE-----

--0F1p//8PRICkK4MW--


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

--===============1292860800==--




From dhcwg-bounces@ietf.org Sun Jul 22 15:54:53 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 1IChVw-00043H-Uo; Sun, 22 Jul 2007 15:54:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IChVv-000436-Mc
	for dhcwg@ietf.org; Sun, 22 Jul 2007 15:54:47 -0400
Received: from the.hankinsfamily.info ([204.152.186.148]
	helo=hankinsfamily.info) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IChVu-000423-7g
	for dhcwg@ietf.org; Sun, 22 Jul 2007 15:54:47 -0400
Received: from hcf.isc.org (dhcp-1444.ietf69.org [130.129.20.68])
	(authenticated bits=0)
	by hankinsfamily.info (8.13.8/8.13.8) with ESMTP id l6MJsiK4002131
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <dhcwg@ietf.org>; Sun, 22 Jul 2007 12:54:45 -0700
Received: by hcf.isc.org (Postfix, from userid 10200)
	id 61CAA5F306; Sun, 22 Jul 2007 14:54:44 -0500 (CDT)
Date: Sun, 22 Jul 2007 14:54:43 -0500
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] dhc wg last call on vpn-option and agent-vpn-id drafts
Message-ID: <20070722195443.GB5315@isc.org>
References: <469384EA.3050301@uninett.no>
Mime-Version: 1.0
In-Reply-To: <469384EA.3050301@uninett.no>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
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="===============1142171776=="
Errors-To: dhcwg-bounces@ietf.org


--===============1142171776==
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 Tue, Jul 10, 2007 at 03:08:58PM +0200, Stig Venaas wrote:
> Virtual Subnet Selection Option <draft-ietf-dhc-vpn-option-06.txt>

Noting that Bernie has many fine points I will try not to repeat,

   All other values of the type field are invalid as of this memo and
   VSS options containing any other value than zero (0) or one (1)
   SHOULD be ignored.

We want old software to work with new protocol work, should there
ever be a document to assign new type codes.  So I don't understand
the motivation here to cause it to be ignored.  It's your existing
usage, I'm just curious why this was selected rather than allowing
operators to specify the contents by hand or such.

I would suggest simply removing this paragraph if it is not actually
documenting a current practice (in which case everyone really SHOULD
do more or less the same thing).


The Security section says:

   This option SHOULD NOT be used without also making use of the DHCP
   Authentication option [5].

But also says:

   DHCP relays MAY choose to remove the option before passing on
   DHCPDISCOVER packets.

I'm kind of confused.  You should use authentication, but relays MAY
break authentication by altering the client area of the packet?

If a relay strips this option, doesn't that just cause the client to
ignore the server (since it won't contain this option in its reply)?
Why not just drop the packet then?


I wonder if this option is used to assign overlapping address spaces
to different VPN's.  In that case, I wonder if it should contain
(even if there is no current practice) DHCPLEASEQUERY language, to
disambiguate queries.

Or I think possibly it should explicitly mention that the current
usage is not DHCPLEASEQUERY compatible?


> Virtual Subnet Selection Sub-Option for the Relay Agent Information=20
> Option for DHCPv4 <draft-ietf-dhc-agent-vpn-id-04.txt>

I think the security section was cut and paste from the client
option.  It doesn't make sense to restrict relay processing to
specific clients served by that relay in this context.

> The last call will conclude at 1700EST on Sun, 2007-07-22.

Yes!  Under the wire!

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

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

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

iD8DBQFGo7YDcXeLeWu2vmoRAgIhAJwJwN5mrJBs5yTY5zISi01/5V8REQCgobzD
7Y3K+tu4kwPM47dXriwK5IY=
=9zaz
-----END PGP SIGNATURE-----

--V0207lvV8h4k8FAm--


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

--===============1142171776==--




From dhcwg-bounces@ietf.org Mon Jul 23 23:17: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 1IDAth-0000XF-Rl; Mon, 23 Jul 2007 23:17:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDAtg-0000X9-GB
	for dhcwg@ietf.org; Mon, 23 Jul 2007 23:17:16 -0400
Received: from web84110.mail.mud.yahoo.com ([68.142.206.197])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IDAtf-0002o1-Ia
	for dhcwg@ietf.org; Mon, 23 Jul 2007 23:17:16 -0400
Received: (qmail 33673 invoked by uid 60001); 24 Jul 2007 03:17:14 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID;
	b=Na69l5kcL2hA3uc6FgxwfTvTODbvcbrTYmJ8Dwofq0VDFjpHCFZDq62H/p+XfH7yxjFFZ/fyikFJWUNHyj+CgUfAXSfjY94WabvoGHeVUHR+i02szYZcCjg3/3jiVXmMxjTPPKU+rLxMRnn9GnlDjf3PCpQWRAoYym+II+n8CU8=;
X-YMail-OSG: 0inMszkVM1ks7NGvX_KpZXsHFLbzCcp5y_cHOoRCjIUV1b87wnP0wum1zHOAeRKrzjAtkhS40YEJ1lMX_3.lwMkyMs.k1R0T5UO2a_ZWQucP0id27cY-
Received: from [130.129.22.155] by web84110.mail.mud.yahoo.com via HTTP;
	Mon, 23 Jul 2007 20:17:14 PDT
X-Mailer: YahooMailRC/651.41 YahooMailWebService/0.7.41.16
Date: Mon, 23 Jul 2007 20:17:14 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: dhcwg@ietf.org
MIME-Version: 1.0
Message-ID: <701745.32300.qm@web84110.mail.mud.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Subject: [dhcwg] Agenda for IETF-69 dhc WG meeting
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
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="===============0262024169=="
Errors-To: dhcwg-bounces@ietf.org

--===============0262024169==
Content-Type: multipart/alternative; boundary="0-1690005258-1185247034=:32300"

--0-1690005258-1185247034=:32300
Content-Type: text/plain; charset=ascii

Hi all,
  Let me write here what I proposed during the session today in hopes to stir some discussion:
In RFC 3633, IAID is defined as 4 octet field to be the unique identifier for each IA_PD. 
In view of per-Mobile Node prefix delegation, I suggest that we extend IAID to be 6 octets and use MAC address of MN for which the prefix is requested. This way the access router can keep track of each prefix it receives by associating the prefix with the MAC address. 
  IA_PD could be easily redefined to add  one more line  and make IAID to be 6 octets with the remaining to bytes reserved and the overall option length to become 16+IA_PD options.
  In case MAC address can not be used, it is possible to convert mobile equipment IDs to 6 octet MAC-like addresses (for 3GPP and 3GPP2 links).
  Your comments on this would be highly appreciated.

Regards,

Behcet

----- Original Message ----
From: Ralph Droms <rdroms@cisco.com>
To: dhcwg@ietf.org
Sent: Saturday, July 21, 2007 5:19:45 AM
Subject: [dhcwg] *DRAFT* Agenda for IETF-69 dhc WG meeting

Draft agenda is included below.  Please contact the chairs if you  
have a topic to be added to the agenda.

                        DHC WG DRAFT agenda - IETF 67
                         0900-1130 2007-07-23 (Mon)
                    (Last revised 2007-07-21 06:16 AM ET)
                    -------------------------------------

Administrivia                                   Venaas/Droms     10  
minutes
   Agenda bashing; blue sheets; scribe; Jabber scribe

Draft last call and adoption announcements      Venaas/Droms     05  
minutes

Progressing two drafts under RFC 3942           R. Droms         10  
minutes
   <draft-ietf-dhc-subnet-alloc-05>
   <draft-raj-dhc-tftp-addr-option-02>

Update to DHCP options guideline                D. Hankins       05  
minutes
   <draft-dhankins-dhcp-option-guidelines-00>
   Accept as WG work item?

Using DHCPv6 and AAA Server for mobile station PD
                                                 B. Sarikaya      15  
minutes
   <draft-sarikaya-16ng-prefix-delegation-01>
   WG input on DHCP-related I-D

Layer 2 relay agent and relay agent chaining    P. Kurapati      15  
minutes
   <draft-joshi-dhc-layer2-relay-agent-01>
   <draft-kurapati-dhc-relay-chaining-dhcpv4-01>
   Adopt as WG work items?

TAHI DHCPv6 Test tool for IPv6 Ready Logo       Hideshi E.       05  
minutes

Extensions to DHCPv6 for prefix and default router information
                                                 T. Chown         10  
minutes
   Initial discussion
                                                                  
-----------
                                                                  75  
minutes

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





--0-1690005258-1185247034=:32300
Content-Type: text/html; charset=ascii

<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:14pt"><div style="font-family: times new roman,new york,times,serif; font-size: 14pt;">Hi all,<br>&nbsp; Let me write here what I proposed during the session today in hopes to stir some discussion:<br>In RFC 3633, IAID is defined as 4 octet field to be the unique identifier for each IA_PD. <br>In view of per-Mobile Node prefix delegation, I suggest that we extend IAID to be 6 octets and use MAC address of MN for which the prefix is requested. This way the access router can keep track of each prefix it receives by associating the prefix with the MAC address. <br>&nbsp; IA_PD could be easily redefined to add&nbsp; one more line&nbsp; and make IAID to be 6 octets with the remaining to bytes reserved and the overall option length to become 16+IA_PD options.<br>&nbsp; In case MAC address can not be used, it is possible to
 convert mobile equipment IDs to 6 octet MAC-like addresses (for 3GPP and 3GPP2 links).<br>&nbsp; Your comments on this would be highly appreciated.<br><br>Regards,<br><br>Behcet<br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Ralph Droms &lt;rdroms@cisco.com&gt;<br>To: dhcwg@ietf.org<br>Sent: Saturday, July 21, 2007 5:19:45 AM<br>Subject: [dhcwg] *DRAFT* Agenda for IETF-69 dhc WG meeting<br><br><div>Draft agenda is included below.&nbsp;&nbsp;Please contact the chairs if you&nbsp;&nbsp;<br>have a topic to be added to the agenda.<br><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;DHC WG DRAFT agenda - IETF 67<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; 0900-1130 2007-07-23
 (Mon)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(Last revised 2007-07-21 06:16 AM ET)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-------------------------------------<br><br>Administrivia&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Venaas/Droms&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp;<br>minutes<br>&nbsp;&nbsp; Agenda bashing; blue sheets; scribe; Jabber scribe<br><br>Draft last call and adoption announcements&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Venaas/Droms&nbsp;&nbsp;&nbsp;&nbsp; 05&nbsp;&nbsp;<br>minutes<br><br>Progressing two drafts under RFC 3942&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; R.
 Droms&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp;<br>minutes<br>&nbsp;&nbsp; &lt;draft-ietf-dhc-subnet-alloc-05&gt;<br>&nbsp;&nbsp; &lt;draft-raj-dhc-tftp-addr-option-02&gt;<br><br>Update to DHCP options guideline&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;D. Hankins&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 05&nbsp;&nbsp;<br>minutes<br>&nbsp;&nbsp; &lt;draft-dhankins-dhcp-option-guidelines-00&gt;<br>&nbsp;&nbsp; Accept as WG work item?<br><br>Using DHCPv6 and AAA Server for mobile station PD<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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; B. Sarikaya&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;15&nbsp;&nbsp;<br>minutes<br>&nbsp;&nbsp;
 &lt;draft-sarikaya-16ng-prefix-delegation-01&gt;<br>&nbsp;&nbsp; WG input on DHCP-related I-D<br><br>Layer 2 relay agent and relay agent chaining&nbsp;&nbsp;&nbsp;&nbsp;P. Kurapati&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;15&nbsp;&nbsp;<br>minutes<br>&nbsp;&nbsp; &lt;draft-joshi-dhc-layer2-relay-agent-01&gt;<br>&nbsp;&nbsp; &lt;draft-kurapati-dhc-relay-chaining-dhcpv4-01&gt;<br>&nbsp;&nbsp; Adopt as WG work items?<br><br>TAHI DHCPv6 Test tool for IPv6 Ready Logo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Hideshi E.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 05&nbsp;&nbsp;<br>minutes<br><br>Extensions to DHCPv6 for prefix and default router information<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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; T.
 Chown&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp;<br>minutes<br>&nbsp;&nbsp; Initial
 discussion<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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br>-----------<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;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;75&nbsp;&nbsp;<br>minutes<br><br>_______________________________________________<br>dhcwg mailing list<br>dhcwg@ietf.org<br><a target="_blank"
 href="https://www1.ietf.org/mailman/listinfo/dhcwg">https://www1.ietf.org/mailman/listinfo/dhcwg</a><br></div></div><br></div></div></body></html>
--0-1690005258-1185247034=:32300--


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

--===============0262024169==--




From dhcwg-bounces@ietf.org Tue Jul 24 01:42: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 1IDDAR-0007z9-37; Tue, 24 Jul 2007 01:42:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDDAP-0007z4-H4
	for dhcwg@ietf.org; Tue, 24 Jul 2007 01:42:41 -0400
Received: from toccata.fugue.com ([204.152.186.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IDDAO-0005Ec-4y
	for dhcwg@ietf.org; Tue, 24 Jul 2007 01:42:41 -0400
Received: from [10.0.2.2] (unknown [67.97.210.2])
	by toccata.fugue.com (Postfix) with ESMTP id 1930CBC42C7;
	Mon, 23 Jul 2007 22:42:39 -0700 (MST)
Subject: Re: [dhcwg] Agenda for IETF-69 dhc WG meeting
From: Ted Lemon <mellon@fugue.com>
To: Behcet Sarikaya <sarikaya@ieee.org>
In-Reply-To: <701745.32300.qm@web84110.mail.mud.yahoo.com>
References: <701745.32300.qm@web84110.mail.mud.yahoo.com>
Content-Type: text/plain
Date: Tue, 24 Jul 2007 00:42:38 -0500
Message-Id: <1185255758.6220.45.camel@sushumna>
Mime-Version: 1.0
X-Mailer: Evolution 2.11.5 
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
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

On Mon, 2007-07-23 at 20:17 -0700, Behcet Sarikaya wrote:
> In RFC 3633, IAID is defined as 4 octet field to be the unique
> identifier for each IA_PD. 
> In view of per-Mobile Node prefix delegation, I suggest that we extend
> IAID to be 6 octets and use MAC address of MN for which the prefix is
> requested. This way the access router can keep track of each prefix it
> receives by associating the prefix with the MAC address. 

Why not make the IAID 16 octets, just in case we have a link with a
fatter address, or want to stuff a UUID in it or something?   Or we
could have it be arbitrrily long.

I don't mean to be sarcastic, but just to illustrate the problem with
this kind of thinking.   It really can't work.   The reason we chose a
four-byte IAID was to allow for a 32-bit interface index, not to allow
you to put a client-sourced identifier in it.

The question that comes to my mind with this proposal is, why not just
have the device that's getting the delegated prefix make the DHCP prefix
delegation request?   Why all this additional complexity?



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



From dhcwg-bounces@ietf.org Tue Jul 24 10:39: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 1IDLXL-0001FL-8A; Tue, 24 Jul 2007 10:38:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDLXK-0001FA-J6
	for dhcwg@ietf.org; Tue, 24 Jul 2007 10:38:54 -0400
Received: from the.hankinsfamily.info ([204.152.186.148]
	helo=hankinsfamily.info) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IDLXI-0000DW-R9
	for dhcwg@ietf.org; Tue, 24 Jul 2007 10:38:54 -0400
Received: from hcf.isc.org (dhcp-16d8.ietf69.org [130.129.22.216])
	(authenticated bits=0)
	by hankinsfamily.info (8.13.8/8.13.8) with ESMTP id l6OEcnie030427
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <dhcwg@ietf.org>; Tue, 24 Jul 2007 07:38:49 -0700
Received: by hcf.isc.org (Postfix, from userid 10200)
	id A078F1CA97; Tue, 24 Jul 2007 09:38:48 -0500 (CDT)
Date: Tue, 24 Jul 2007 09:38:48 -0500
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Agenda for IETF-69 dhc WG meeting
Message-ID: <20070724143847.GA8464@isc.org>
References: <701745.32300.qm@web84110.mail.mud.yahoo.com>
Mime-Version: 1.0
In-Reply-To: <701745.32300.qm@web84110.mail.mud.yahoo.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -4.0 (----)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
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="===============0185574332=="
Errors-To: dhcwg-bounces@ietf.org


--===============0185574332==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="C7zPtVaVf+AK4Oqc"
Content-Disposition: inline


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

On Mon, Jul 23, 2007 at 08:17:14PM -0700, Behcet Sarikaya wrote:
> In RFC 3633, IAID is defined as 4 octet field to be the unique identifier=
 for each IA_PD.=20

This is correct, but misleading.  The IAID is a discriminator for each
IA_PD (if there are more than one) within the context of each
identified client (as per the client identifier).

The IAID is not globally unique.  It is locally unique for each
unique client identifier.

In your presentation, you describe that a relay agent is mocking up a
client to represent each point to point remote client.  It most
closely resembles what we call DHCPv6 to select a client identifier
that identifies each remote client (rather than placing them all
under one identifier).

I'm sorry if you're in a pinch and you have to use one client
identifier for all clients.  That's a problem.  I don't think
we should change IA_PD to accomodate that problem.

--=20
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
--=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

--C7zPtVaVf+AK4Oqc
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFGpg73cXeLeWu2vmoRAmKqAKCBfcOnsj+L6teZWuoWI2Z7dUXKygCgjVfr
ocJJABUx4zGvx7BWhIdbxJ8=
=vmMb
-----END PGP SIGNATURE-----

--C7zPtVaVf+AK4Oqc--


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

--===============0185574332==--




From dhcwg-bounces@ietf.org Tue Jul 24 12:07: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 1IDMvJ-0003bp-Vz; Tue, 24 Jul 2007 12:07:45 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDMvJ-0003bc-3N
	for dhcwg@ietf.org; Tue, 24 Jul 2007 12:07:45 -0400
Received: from the.hankinsfamily.info ([204.152.186.148]
	helo=hankinsfamily.info)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDMvI-0006M8-Kl
	for dhcwg@ietf.org; Tue, 24 Jul 2007 12:07:44 -0400
Received: from hcf.isc.org (dhcp-16d8.ietf69.org [130.129.22.216])
	(authenticated bits=0)
	by hankinsfamily.info (8.13.8/8.13.8) with ESMTP id l6OG7hWY031228
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <dhcwg@ietf.org>; Tue, 24 Jul 2007 09:07:44 -0700
Received: by hcf.isc.org (Postfix, from userid 10200)
	id 05C2A5F316; Tue, 24 Jul 2007 11:07:42 -0500 (CDT)
Date: Tue, 24 Jul 2007 11:07:42 -0500
From: "David W. Hankins" <David_Hankins@isc.org>
To: DHC WG <dhcwg@ietf.org>
Subject: Re: [dhcwg] dhc wg last call on  draft-ietf-dhc-pxelinux-01
Message-ID: <20070724160742.GB8464@isc.org>
References: <46823079.5050405@uninett.no>
	<8E296595B6471A4689555D5D725EBB2104619BF1@xmb-rtp-20a.amer.cisco.com>
	<20070706192823.GF8503@isc.org> <469B5E97.4040704@uninett.no>
Mime-Version: 1.0
In-Reply-To: <469B5E97.4040704@uninett.no>
User-Agent: Mutt/1.5.9i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
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="===============2013043302=="
Errors-To: dhcwg-bounces@ietf.org


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


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

On Mon, Jul 16, 2007 at 02:03:35PM +0200, Stig Venaas wrote:
> I think it's good if you can post another revision with the minor=20
> changes discussed below before we pass it on to the IESG. Also please
> run it through the idnits tool to check that there are no issues.

Done and done.

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

--4bRzO86E/ozDv8r1
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFGpiPOcXeLeWu2vmoRApVnAJ9a5ko5Sd0tp33Ma/Al5C2Wb5sYFwCZAYYI
9nlxbNa4SvVFARKoacqxC8U=
=Ew60
-----END PGP SIGNATURE-----

--4bRzO86E/ozDv8r1--


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

--===============2013043302==--




From dhcwg-bounces@ietf.org Tue Jul 24 12:41: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 1IDNSA-00028h-JH; Tue, 24 Jul 2007 12:41:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDNS9-00028a-9p
	for dhcwg@ietf.org; Tue, 24 Jul 2007 12:41:41 -0400
Received: from web30814.mail.mud.yahoo.com ([68.142.201.140])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IDNS7-0004rq-WB
	for dhcwg@ietf.org; Tue, 24 Jul 2007 12:41:41 -0400
Received: (qmail 33332 invoked by uid 60001); 24 Jul 2007 16:41:39 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
	b=A7jRCu+d9oLEh4ZUjog0SdbPfaVeadGud5weNssyt6gkYqViAyeC9+6f1IMD3dSW9aeoXHqoO9B+e8kdy40ERWPx33Toc6HKev7VCmtfieeNe8xPiQomfo5ZuNhUqyDjFh0brPx8BrhTEwBxsYzIgxnOz7BkS8AKhbUiIM+i7es=;
X-YMail-OSG: yK_2EIkVM1nQlJGaqr9Dv3Jy.pMDBRXiYxNJHok875Bq0q0DgE.uuXcFwx3fIG_neoWCCxn.HIwShVVXQ.ihS5D2itz8W8W46ZeiToCeiYZlioF7Y14-
Received: from [207.46.55.28] by web30814.mail.mud.yahoo.com via HTTP;
	Tue, 24 Jul 2007 09:41:39 PDT
X-Mailer: YahooMailRC/651.41 YahooMailWebService/0.7.119
Date: Tue, 24 Jul 2007 09:41:39 -0700 (PDT)
From: RamaSubramanian KrishnaMurthi <ramasubbu_sk@yahoo.com>
To: dhcwg@ietf.org
MIME-Version: 1.0
Message-ID: <348429.32516.qm@web30814.mail.mud.yahoo.com>
X-Spam-Score: 2.4 (++)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Subject: [dhcwg] FQDN RFC 4704
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="===============1420371858=="
Errors-To: dhcwg-bounces@ietf.org

--===============1420371858==
Content-Type: multipart/alternative; boundary="0-1003923061-1185295299=:32516"

--0-1003923061-1185295299=:32516
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Hi all,=0A   I have a doubt on DHCPServer FQDN option 39 for DHCPv6 server.=
=0A   If client send the flag value as N=3D1, O=3D0, S=3D1 , i.e. asking th=
e DHCPServer to perform NO DNS updates.=0A     But the DHCPServer is config=
ure to do both AAAA and PTR forcefully. Then what should the DHCPServer sho=
uld send the values in the flags ?=0A     should it send like  N=3D0,O=3D1,=
S=3D1 ? =0A     RFC says O=3D1 only if there is change in S=3D1, in the abo=
ve scenario S is always 1.      =0A=0A =0AYours ever=0A-RamaSubbu SK=0A=0A=
=0A       =0A______________________________________________________________=
______________________Ready for the edge of your seat? =0ACheck out tonight=
's top picks on Yahoo! TV. =0Ahttp://tv.yahoo.com/
--0-1003923061-1185295299=:32516
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:verdana, helvetica, sans-serif;font-size=
:10pt"><DIV></DIV>=0A<DIV>Hi all,</DIV>=0A<DIV>&nbsp;&nbsp;&nbsp;I have a d=
oubt on DHCPServer&nbsp;FQDN option 39 for DHCPv6 server.</DIV>=0A<DIV>&nbs=
p;&nbsp; If&nbsp;client send the flag value as <SPAN style=3D"FONT-SIZE: 11=
pt; LINE-HEIGHT: 115%; FONT-FAMILY: 'Calibri','sans-serif'; mso-ascii-theme=
-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-fon=
t: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'T=
imes New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US;=
 mso-fareast-language: EN-US; mso-bidi-language: AR-SA">N=3D1, O=3D0, S=3D1=
&nbsp;, i.e. asking the DHCPServer to perform NO DNS updates.</SPAN></DIV>=
=0A<DIV><SPAN style=3D"FONT-SIZE: 11pt; LINE-HEIGHT: 115%; FONT-FAMILY: 'Ca=
libri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-fareast-font-fa=
mily: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: m=
inor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: m=
inor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-=
language: AR-SA">&nbsp;&nbsp;&nbsp;&nbsp; But the DHCPServer is configure t=
o do both AAAA and PTR forcefully. Then what should the DHCPServer should s=
end the values in the flags ?</SPAN></DIV>=0A<DIV><SPAN style=3D"FONT-SIZE:=
 11pt; LINE-HEIGHT: 115%; FONT-FAMILY: 'Calibri','sans-serif'; mso-ascii-th=
eme-font: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-=
font: minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family:=
 'Times New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-=
US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">&nbsp;&nbsp;&nbs=
p;&nbsp; should it send like&nbsp; N=3D0,O=3D1,S=3D1 ?&nbsp;</SPAN></DIV>=
=0A<DIV><SPAN style=3D"FONT-SIZE: 11pt; LINE-HEIGHT: 115%; FONT-FAMILY: 'Ca=
libri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-fareast-font-fa=
mily: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: m=
inor-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: m=
inor-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-=
language: AR-SA">&nbsp;&nbsp;&nbsp;&nbsp; RFC says O=3D1&nbsp;only&nbsp;if =
there is change in S=3D1, in the above scenario&nbsp;S is always 1.&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; </SPAN></DIV>=0A<DIV><SPAN style=3D"FONT-SIZE: 11pt;=
 LINE-HEIGHT: 115%; FONT-FAMILY: 'Calibri','sans-serif'; mso-ascii-theme-fo=
nt: minor-latin; mso-fareast-font-family: Calibri; mso-fareast-theme-font: =
minor-latin; mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Time=
s New Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; ms=
o-fareast-language: EN-US; mso-bidi-language: AR-SA"></SPAN>&nbsp;</DIV>=0A=
<DIV><SPAN style=3D"FONT-SIZE: 11pt; LINE-HEIGHT: 115%; FONT-FAMILY: 'Calib=
ri','sans-serif'; mso-ascii-theme-font: minor-latin; mso-fareast-font-famil=
y: Calibri; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: mino=
r-latin; mso-bidi-font-family: 'Times New Roman'; mso-bidi-theme-font: mino=
r-bidi; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-lan=
guage: AR-SA"></SPAN>&nbsp;</DIV>=0A<DIV><FONT color=3D#bf005f>Yo</FONT><FO=
NT color=3D#0000ff>ur</FONT><FONT color=3D#00ff80>s e</FONT><FONT color=3D#=
ff007f>ve</FONT>r</DIV>=0A<DIV>-<A href=3D"http://spaces.msn.com/ramasubbu"=
 target=3D_blank rel=3Dnofollow>RamaSubbu SK</A>&nbsp;<IMG src=3D"http://us=
.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/14.gif"></DIV>=0A<DIV></DIV></div=
><br>=0A=0A      <hr size=3D1>Park yourself in front of a world of choices =
in alternative vehicles.<br><a href=3D"http://us.rd.yahoo.com/evt=3D48246/*=
http://autos.yahoo.com/green_center/;_ylc=3DX3oDMTE5cDF2bXZzBF9TAzk3MTA3MDc=
2BHNlYwNtYWlsdGFncwRzbGsDZ3JlZW4tY2VudGVy">Visit the Yahoo! Auto Green Cent=
er.</a></body></html>
--0-1003923061-1185295299=:32516--


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

--===============1420371858==--




From dhcwg-bounces@ietf.org Tue Jul 24 15:25: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 1IDQ0s-0001cd-F3; Tue, 24 Jul 2007 15:25:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDQ0r-0001bM-2M
	for dhcwg@ietf.org; Tue, 24 Jul 2007 15:25:41 -0400
Received: from web84113.mail.mud.yahoo.com ([68.142.206.200])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IDQ0q-0000l8-GJ
	for dhcwg@ietf.org; Tue, 24 Jul 2007 15:25:41 -0400
Received: (qmail 77676 invoked by uid 60001); 24 Jul 2007 19:25:40 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID;
	b=Hq54EkJjpnWgaR6+1cMDP8C3d90TNtR01OxSTluTW30pZ9lyl3e4VFwJXy25knR8sIUq1+Fv+lOnl/gsh/OpxO8qVVqCAErAteHGvugWJKIdg4ZccsvKZ/QGR32E2Haq8/AJamj8zA+5d7gGsFdwuIvWpfTM/l372PULNdQ5oiE=;
X-YMail-OSG: M8yaGcIVM1n6X2d0gMPJ0FMiOu4OlE8bcALxz02SiPl.2zMHokFHuWrbddVR2Adj_Q--
Received: from [130.129.16.130] by web84113.mail.mud.yahoo.com via HTTP;
	Tue, 24 Jul 2007 12:25:40 PDT
X-Mailer: YahooMailRC/651.41 YahooMailWebService/0.7.41.16
Date: Tue, 24 Jul 2007 12:25:40 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: [dhcwg] Agenda for IETF-69 dhc WG meeting
To: Ted Lemon <mellon@fugue.com>
MIME-Version: 1.0
Message-ID: <124554.76596.qm@web84113.mail.mud.yahoo.com>
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
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
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="===============1757167583=="
Errors-To: dhcwg-bounces@ietf.org

--===============1757167583==
Content-Type: multipart/alternative; boundary="0-1273253867-1185305140=:76596"

--0-1273253867-1185305140=:76596
Content-Type: text/plain; charset=ascii

Comments in line.
Regards,

Behcet

----- Original Message ----
From: Ted Lemon <mellon@fugue.com>
To: Behcet Sarikaya <sarikaya@ieee.org>
Cc: dhcwg@ietf.org
Sent: Tuesday, July 24, 2007 12:42:38 AM
Subject: Re: [dhcwg] Agenda for IETF-69 dhc WG meeting

On Mon, 2007-07-23 at 20:17 -0700, Behcet Sarikaya wrote:
> In RFC 3633, IAID is defined as 4 octet field to be the unique
> identifier for each IA_PD. 
> In view of per-Mobile Node prefix delegation, I suggest that we extend
> IAID to be 6 octets and use MAC address of MN for which the prefix is
> requested. This way the access router can keep track of each prefix it
> receives by associating the prefix with the MAC address. 

Why not make the IAID 16 octets, just in case we have a link with a
fatter address, or want to stuff a UUID in it or something?   Or we
could have it be arbitrrily long.

I don't mean to be sarcastic, but just to illustrate the problem with
this kind of thinking.   It really can't work.   The reason we chose a
four-byte IAID was to allow for a 32-bit interface index, not to allow
you to put a client-sourced identifier in it.

The question that comes to my mind with this proposal is, why not just
have the device that's getting the delegated prefix make the DHCP prefix
delegation request?   Why all this additional complexity?

[behcet] IPv6 address configuration requires the device to configure an address from the prefix in RA (router advertisement) or get it from DHCP. The device does not get the prefix directly.  It is the AR that should get it and create the point to point link.

[behcet] What I have proposed is that 32-bit interface index of IAID may probably need to be revisited because of this new application of DHCP PD which is client oriented.
It is up to you, just asking.





--0-1273253867-1185305140=:76596
Content-Type: text/html; charset=ascii

<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:14pt"><div style="font-family: times new roman,new york,times,serif; font-size: 14pt;">Comments in line.<br>Regards,<br><br>Behcet<br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Ted Lemon &lt;mellon@fugue.com&gt;<br>To: Behcet Sarikaya &lt;sarikaya@ieee.org&gt;<br>Cc: dhcwg@ietf.org<br>Sent: Tuesday, July 24, 2007 12:42:38 AM<br>Subject: Re: [dhcwg] Agenda for IETF-69 dhc WG meeting<br><br><div>On Mon, 2007-07-23 at 20:17 -0700, Behcet Sarikaya wrote:<br>&gt; In RFC 3633, IAID is defined as 4 octet field to be the unique<br>&gt; identifier for each IA_PD. <br>&gt; In view of per-Mobile Node prefix delegation, I suggest that we extend<br>&gt; IAID to be 6 octets and use MAC address of MN for which the prefix is<br>&gt; requested. This way the
 access router can keep track of each prefix it<br>&gt; receives by associating the prefix with the MAC address. <br><br>Why not make the IAID 16 octets, just in case we have a link with a<br>fatter address, or want to stuff a UUID in it or something?&nbsp;&nbsp; Or we<br>could have it be arbitrrily long.<br><br>I don't mean to be sarcastic, but just to illustrate the problem with<br>this kind of thinking.&nbsp;&nbsp; It really can't work.&nbsp;&nbsp; The reason we chose a<br>four-byte IAID was to allow for a 32-bit interface index, not to allow<br>you to put a client-sourced identifier in it.<br><br>The question that comes to my mind with this proposal is, why not just<br>have the device that's getting the delegated prefix make the DHCP prefix<br>delegation request?&nbsp;&nbsp; Why all this additional complexity?<br><br>[behcet] IPv6 address configuration requires the device to configure an address from the prefix in RA (router advertisement) or get it from DHCP. The
 device does not get the prefix directly.&nbsp; It is the AR that should get it and create the point to point link.<br><br>[behcet] What I have proposed is that 32-bit interface index of IAID may probably need to be revisited because of this new application of DHCP PD which is client oriented.<br>It is up to you, just asking.<br></div></div><br></div></div></body></html>
--0-1273253867-1185305140=:76596--


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

--===============1757167583==--




From dhcwg-bounces@ietf.org Wed Jul 25 13:15: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 1IDkSn-00048Z-K4; Wed, 25 Jul 2007 13:15:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IDkSV-0003Rh-VJ; Wed, 25 Jul 2007 13:15:36 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IDkSS-0005b0-0u; Wed, 25 Jul 2007 13:15:35 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id F4221328EF;
	Wed, 25 Jul 2007 17:15:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1IDkRx-0008NS-Sf; Wed, 25 Jul 2007 13:15:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1IDkRx-0008NS-Sf@stiedprstage1.ietf.org>
Date: Wed, 25 Jul 2007 13:15:01 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-pxelinux-02.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		: Dynamic Host Configuration Protocol Options Used by PXELINUX
	Author(s)	: D. Hankins
	Filename	: draft-ietf-dhc-pxelinux-02.txt
	Pages		: 13
	Date		: 2007-7-25
	
This document describes the use by PXELINUX of some DHCP Option Codes
   numbering from 208-211.  These codes were historically designated
   'Site Local', but are presently being made available for allocation
   as standard DHCP Options.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-pxelinux-02.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-pxelinux-02.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-pxelinux-02.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-7-25120345.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dhc-pxelinux-02.txt

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

Content-Type: text/plain
Content-ID: <2007-7-25120345.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 Jul 25 13:55:02 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 1IDl4d-0007Ke-9J; Wed, 25 Jul 2007 13:54:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IDl4b-0007Ju-RZ
	for dhcwg@ietf.org; Wed, 25 Jul 2007 13:54:57 -0400
Received: from the.hankinsfamily.info ([204.152.186.148]
	helo=hankinsfamily.info) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IDl4a-00080E-4B
	for dhcwg@ietf.org; Wed, 25 Jul 2007 13:54:57 -0400
Received: from hcf.isc.org (dhcp-14ae.ietf69.org [130.129.20.174])
	(authenticated bits=0)
	by hankinsfamily.info (8.13.8/8.13.8) with ESMTP id l6PHssjI015463
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <dhcwg@ietf.org>; Wed, 25 Jul 2007 10:54:55 -0700
Received: by hcf.isc.org (Postfix, from userid 10200)
	id D5E2F5EED3; Wed, 25 Jul 2007 12:54:53 -0500 (CDT)
Date: Wed, 25 Jul 2007 12:54:53 -0500
From: "David W. Hankins" <David_Hankins@isc.org>
To: DHC WG <dhcwg@ietf.org>
Message-ID: <20070725175453.GA11723@isc.org>
Mime-Version: 1.0
User-Agent: Mutt/1.5.9i
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Subject: [dhcwg] draft-dhankins-dhcp-option-guidelines-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>
Content-Type: multipart/mixed; boundary="===============1924080281=="
Errors-To: dhcwg-bounces@ietf.org


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


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

This draft has just made it through the internet-drafts submission;

http://www.ietf.org/internet-drafts/draft-dhankins-dhcp-option-guidelines-0=
1.txt

As I mentioned in the DHC WG meeting Monday, this is the version of
the draft I would like to have considered to become a WG Item.

--=20
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
--=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

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

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

iD8DBQFGp45tcXeLeWu2vmoRAhZmAKCjyR3DcDmAWaYV4/iqhLHKNRzFQQCgiYIZ
HbKZexOp4wuvslJGNY6wfL0=
=GKdk
-----END PGP SIGNATURE-----

--FCuugMFkClbJLl1L--


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

--===============1924080281==--




From dhcwg-bounces@ietf.org Fri Jul 27 16:26: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 1IEWOE-0005LV-Bl; Fri, 27 Jul 2007 16:26:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IEWOD-0005LP-0b
	for dhcwg@ietf.org; Fri, 27 Jul 2007 16:26:21 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IEWOC-0005y2-4b
	for dhcwg@ietf.org; Fri, 27 Jul 2007 16:26:20 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 27 Jul 2007 16:26:20 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAPLxqUZAZnmf/2dsb2JhbACCZQ
X-IronPort-AV: i="4.16,590,1175486400"; 
	d="scan'208,217"; a="127254053:sNHT64003912"
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 l6RKQJbu010902; 
	Fri, 27 Jul 2007 16:26:19 -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 l6RKQBWI019241; 
	Fri, 27 Jul 2007 20:26:19 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, 27 Jul 2007 16:26:01 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [dhcwg] Agenda for IETF-69 dhc WG meeting
Date: Fri, 27 Jul 2007 16:26:00 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB21049D273C@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <124554.76596.qm@web84113.mail.mud.yahoo.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Agenda for IETF-69 dhc WG meeting
Thread-Index: AcfOKHfWnnFnVdxKQIWkUaacA7pTXQCY3tvA
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "Behcet Sarikaya" <sarikaya@ieee.org>, "Ted Lemon" <mellon@fugue.com>
X-OriginalArrivalTime: 27 Jul 2007 20:26:01.0829 (UTC)
	FILETIME=[59769150:01C7D08C]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7683; t=1185567979;
	x=1186431979; 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]=20Agenda=20for=20IETF-69=20dhc=20WG=20meeting
	|Sender:=20
	|To:=20=22Behcet=20Sarikaya=22=20<sarikaya@ieee.org>,
	=20=22Ted=20Lemon=22 =20<mellon@fugue.com>;
	bh=LekCFmYYaD1t9YWx2OshL+MFJXKgCTKaMbPcmdnvW3Y=;
	b=DuWpPlGKZFKJknjXn+Pbpd5YwbbpWSLNk5+5L8PngbA9eaitEgT1+Zbv5EKzZ5DZex/Lz/6Q
	dNDwh3sgnyjZsIWgTDX6kdJh/9G+Jiq0Cv6C6K8KAZ4V7CUCLm1DNi2d;
Authentication-Results: rtp-dkim-2; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7a0494a0224ca59418dd8f92694c1fdb
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>
Content-Type: multipart/mixed; boundary="===============0331520422=="
Errors-To: dhcwg-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0331520422==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7D08C.595DEE79"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7D08C.595DEE79
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Why doesn't the AR maintain a mapping between device and IAID (you could
use a hash of the remote device's identity - mac address or whatever -
and handle collisions appropriately).
=20
We are NOT about to break existing implementations just because you want
the field bigger. As Ted already pointed out, others might want or need
larger fields.
=20
The 4-byte IAID allows 4 billion PDs. That should be more than enough
for any application. So, if you can't stuff what you need into the
field, you'll have to develop a mapping scheme and maintain the mapping
table.
=20
- Bernie

________________________________

From: Behcet Sarikaya [mailto:behcetsarikaya@yahoo.com]=20
Sent: Tuesday, July 24, 2007 3:26 PM
To: Ted Lemon
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Agenda for IETF-69 dhc WG meeting


Comments in line.
Regards,

Behcet


----- Original Message ----
From: Ted Lemon <mellon@fugue.com>
To: Behcet Sarikaya <sarikaya@ieee.org>
Cc: dhcwg@ietf.org
Sent: Tuesday, July 24, 2007 12:42:38 AM
Subject: Re: [dhcwg] Agenda for IETF-69 dhc WG meeting


On Mon, 2007-07-23 at 20:17 -0700, Behcet Sarikaya wrote:
> In RFC 3633, IAID is defined as 4 octet field to be the unique
> identifier for each IA_PD.=20
> In view of per-Mobile Node prefix delegation, I suggest that we extend
> IAID to be 6 octets and use MAC address of MN for which the prefix is
> requested. This way the access router can keep track of each prefix it
> receives by associating the prefix with the MAC address.=20

Why not make the IAID 16 octets, just in case we have a link with a
fatter address, or want to stuff a UUID in it or something?   Or we
could have it be arbitrrily long.

I don't mean to be sarcastic, but just to illustrate the problem with
this kind of thinking.   It really can't work.   The reason we chose a
four-byte IAID was to allow for a 32-bit interface index, not to allow
you to put a client-sourced identifier in it.

The question that comes to my mind with this proposal is, why not just
have the device that's getting the delegated prefix make the DHCP prefix
delegation request?   Why all this additional complexity?

[behcet] IPv6 address configuration requires the device to configure an
address from the prefix in RA (router advertisement) or get it from
DHCP. The device does not get the prefix directly.  It is the AR that
should get it and create the point to point link.

[behcet] What I have proposed is that 32-bit interface index of IAID may
probably need to be revisited because of this new application of DHCP PD
which is client oriented.
It is up to you, just asking.



------_=_NextPart_001_01C7D08C.595DEE79
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<STYLE type=3Dtext/css>DIV {
	MARGIN: 0px
}
</STYLE>

<META content=3D"MSHTML 6.00.2900.3132" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D376102320-27072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Why doesn't the AR maintain a mapping between =
device and=20
IAID (you could use a hash of the remote device's identity - mac address =
or=20
whatever - and handle collisions appropriately).</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D376102320-27072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D376102320-27072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>We are NOT about to break existing =
implementations just=20
because you want the field bigger. As Ted already pointed out, others =
might want=20
or need larger fields.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D376102320-27072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D376102320-27072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The 4-byte IAID allows 4 billion PDs. That =
should be more=20
than enough for any application. So, if you can't stuff what you need =
into the=20
field, you'll have to develop a mapping scheme and maintain the mapping=20
table.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D376102320-27072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D376102320-27072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>- Bernie</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Behcet Sarikaya=20
[mailto:behcetsarikaya@yahoo.com] <BR><B>Sent:</B> Tuesday, July 24, =
2007 3:26=20
PM<BR><B>To:</B> Ted Lemon<BR><B>Cc:</B> =
dhcwg@ietf.org<BR><B>Subject:</B> Re:=20
[dhcwg] Agenda for IETF-69 dhc WG meeting<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV style=3D"FONT-SIZE: 14pt; FONT-FAMILY: times new roman,new =
york,times,serif">
<DIV=20
style=3D"FONT-SIZE: 14pt; FONT-FAMILY: times new roman,new =
york,times,serif">Comments=20
in line.<BR>Regards,<BR><BR>Behcet<BR><BR>
<DIV=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: times new roman,new =
york,times,serif">-----=20
Original Message ----<BR>From: Ted Lemon &lt;mellon@fugue.com&gt;<BR>To: =
Behcet=20
Sarikaya &lt;sarikaya@ieee.org&gt;<BR>Cc: dhcwg@ietf.org<BR>Sent: =
Tuesday, July=20
24, 2007 12:42:38 AM<BR>Subject: Re: [dhcwg] Agenda for IETF-69 dhc WG=20
meeting<BR><BR>
<DIV>On Mon, 2007-07-23 at 20:17 -0700, Behcet Sarikaya wrote:<BR>&gt; =
In RFC=20
3633, IAID is defined as 4 octet field to be the unique<BR>&gt; =
identifier for=20
each IA_PD. <BR>&gt; In view of per-Mobile Node prefix delegation, I =
suggest=20
that we extend<BR>&gt; IAID to be 6 octets and use MAC address of MN for =
which=20
the prefix is<BR>&gt; requested. This way the access router can keep =
track of=20
each prefix it<BR>&gt; receives by associating the prefix with the MAC =
address.=20
<BR><BR>Why not make the IAID 16 octets, just in case we have a link =
with=20
a<BR>fatter address, or want to stuff a UUID in it or =
something?&nbsp;&nbsp; Or=20
we<BR>could have it be arbitrrily long.<BR><BR>I don't mean to be =
sarcastic, but=20
just to illustrate the problem with<BR>this kind of =
thinking.&nbsp;&nbsp; It=20
really can't work.&nbsp;&nbsp; The reason we chose a<BR>four-byte IAID =
was to=20
allow for a 32-bit interface index, not to allow<BR>you to put a =
client-sourced=20
identifier in it.<BR><BR>The question that comes to my mind with this =
proposal=20
is, why not just<BR>have the device that's getting the delegated prefix =
make the=20
DHCP prefix<BR>delegation request?&nbsp;&nbsp; Why all this additional=20
complexity?<BR><BR>[behcet] IPv6 address configuration requires the =
device to=20
configure an address from the prefix in RA (router advertisement) or get =
it from=20
DHCP. The device does not get the prefix directly.&nbsp; It is the AR =
that=20
should get it and create the point to point link.<BR><BR>[behcet] What I =
have=20
proposed is that 32-bit interface index of IAID may probably need to be=20
revisited because of this new application of DHCP PD which is client=20
oriented.<BR>It is up to you, just=20
asking.<BR></DIV></DIV><BR></DIV></DIV></BODY></HTML>

------_=_NextPart_001_01C7D08C.595DEE79--


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

--===============0331520422==--




From dhcwg-bounces@ietf.org Mon Jul 30 11:09:35 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 1IFWsG-0005AZ-Co; Mon, 30 Jul 2007 11:09:32 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFWs5-00058k-Pe
	for dhcwg@ietf.org; Mon, 30 Jul 2007 11:09:21 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFWs5-0007YS-2s
	for dhcwg@ietf.org; Mon, 30 Jul 2007 11:09:21 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 30 Jul 2007 11:09:20 -0400
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AswMAGOcrUZAZnme/2dsb2JhbACCZyOFXw
X-IronPort-AV: i="4.19,198,1183348800"; 
	d="scan'208,217"; a="127403962:sNHT58101290"
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 l6UF9K2L006900; 
	Mon, 30 Jul 2007 11:09:20 -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 l6UF9KWO006995; 
	Mon, 30 Jul 2007 15:09:20 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); 
	Mon, 30 Jul 2007 11:09:17 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [dhcwg] FQDN RFC 4704
Date: Mon, 30 Jul 2007 11:09:16 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB21049D2A4F@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <348429.32516.qm@web30814.mail.mud.yahoo.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] FQDN RFC 4704
Thread-Index: AcfOEYkySLJlrrLKRLuQ+SGfTAk+dAEqZQjA
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "RamaSubramanian KrishnaMurthi" <ramasubbu_sk@yahoo.com>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 30 Jul 2007 15:09:17.0291 (UTC)
	FILETIME=[991D73B0:01C7D2BB]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=9599; t=1185808160;
	x=1186672160; 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]=20FQDN=20RFC=204704 |Sender:=20
	|To:=20=22RamaSubramanian=20KrishnaMurthi=22=20<ramasubbu_sk@yahoo.com>,
	= 20<dhcwg@ietf.org>;
	bh=mueDGYfy20uhM4PhEAsBTfXBYViJ0Jj2+8zVgKWP1pQ=;
	b=Ri8tZ329UkOPPPUVW14dXaxo1QWEjKEY2XV32ld65sV3HNmiE8x5K8QgeNIc19hVt/YLpSSs
	8nysUWW5X0PVhEM/ySKo0XnGslSz07kgIGVxjL5VgYYnpLqowY26kWSC;
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: 36fb765c89ed47dab364ab702a78e8fd
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>
Content-Type: multipart/mixed; boundary="===============0296041324=="
Errors-To: dhcwg-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0296041324==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7D2BB.98DD2308"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7D2BB.98DD2308
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I'm not sure why the client set S=3D1 in this case. RFC 4704 states in
section 5.3:
5.3. Client Desires No Server DNS Updates

A client can choose to request that the server perform no DNS updates

on its behalf. In order to inform the server of this choice, the

client SHOULD include the Client FQDN option in its SOLICIT with

Rapid Commit, REQUEST, RENEW, and REBIND messages and MAY include the

Client FQDN option in its SOLICIT. The "N" bit in the Flags field in

the option MUST be 1, and the "S" and "O" bits MUST be 0.

=20
The rules are pretty clear - if the S bit changes from what was received
from the client to what is sent back to the client, set the O bit.
Otherwise, O is clear.
=20
So, if the client did send in S=3D1 in this case, O would be clear.
=20
The S & O bits are likely meaningless when the client sends in N=3D1, =
but
best to stick to following the documented rules.
=20
- Bernie


________________________________

From: RamaSubramanian KrishnaMurthi [mailto:ramasubbu_sk@yahoo.com]=20
Sent: Tuesday, July 24, 2007 12:42 PM
To: dhcwg@ietf.org
Subject: [dhcwg] FQDN RFC 4704


Hi all,
   I have a doubt on DHCPServer FQDN option 39 for DHCPv6 server.
   If client send the flag value as N=3D1, O=3D0, S=3D1 , i.e. asking =
the
DHCPServer to perform NO DNS updates.
     But the DHCPServer is configure to do both AAAA and PTR forcefully.
Then what should the DHCPServer should send the values in the flags ?
     should it send like  N=3D0,O=3D1,S=3D1 ?=20
     RFC says O=3D1 only if there is change in S=3D1, in the above =
scenario
S is always 1.     =20
=20
=20
Yours ever
-RamaSubbu SK <http://spaces.msn.com/ramasubbu>
<http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/14.gif>=20

________________________________

Park yourself in front of a world of choices in alternative vehicles.
Visit the Yahoo! Auto Green Center.
<http://us.rd.yahoo.com/evt=3D48246/*http://autos.yahoo.com/green_center/=
;
_ylc=3DX3oDMTE5cDF2bXZzBF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDZ3JlZW4tY2=
V
udGVy>=20

------_=_NextPart_001_01C7D2BB.98DD2308
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<STYLE type=3Dtext/css>DIV {
	MARGIN: 0px
}
</STYLE>

<META content=3D"MSHTML 6.00.2900.3132" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D026510515-30072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>I'm not sure why the client set S=3D1 in this =
case.=20
</FONT></SPAN><SPAN class=3D026510515-30072007><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>RFC 4704 states in section 5.3:</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D026510515-30072007><FONT =
size=3D2>
<P>5.3. Client Desires No Server DNS Updates</P>
<P>A client can choose to request that the server perform no DNS =
updates</P>
<P>on its behalf. In order to inform the server of this choice, the</P>
<P>client SHOULD include the Client FQDN option in its SOLICIT with</P>
<P>Rapid Commit, REQUEST, RENEW, and REBIND messages and MAY include =
the</P>
<P>Client FQDN option in its SOLICIT. <STRONG>The "N" bit in the Flags =
field=20
in</STRONG></P>
<P><STRONG>the option MUST be 1, and the "S" and "O" bits MUST be=20
0.</STRONG></P></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D026510515-30072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D026510515-30072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The rules are pretty clear - if the S bit =
changes from what=20
was received from the client to what is sent back to the client, set the =
O bit.=20
Otherwise, O is clear.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D026510515-30072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D026510515-30072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>So, if the client did send in S=3D1 in this =
case, O would be=20
clear.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D026510515-30072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D026510515-30072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>The S &amp; O bits are&nbsp;likely meaningless =
when the=20
client sends in N=3D1, but best to stick to following the documented=20
rules.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D026510515-30072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D026510515-30072007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>- Bernie</FONT></SPAN></DIV><STRONG><FONT=20
size=3D2></FONT></STRONG><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> RamaSubramanian KrishnaMurthi=20
[mailto:ramasubbu_sk@yahoo.com] <BR><B>Sent:</B> Tuesday, July 24, 2007 =
12:42=20
PM<BR><B>To:</B> dhcwg@ietf.org<BR><B>Subject:</B> [dhcwg] FQDN RFC=20
4704<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV style=3D"FONT-SIZE: 10pt; FONT-FAMILY: verdana, helvetica, =
sans-serif">
<DIV></DIV>
<DIV>Hi all,</DIV>
<DIV>&nbsp;&nbsp;&nbsp;I have a doubt on DHCPServer&nbsp;FQDN option 39 =
for=20
DHCPv6 server.</DIV>
<DIV>&nbsp;&nbsp; If&nbsp;client send the flag value as <SPAN=20
style=3D"FONT-SIZE: 11pt; LINE-HEIGHT: 115%; FONT-FAMILY: =
'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; =
mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; =
mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New =
Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA">N=3D1,=20
O=3D0, S=3D1&nbsp;, i.e. asking the DHCPServer to perform NO DNS=20
updates.</SPAN></DIV>
<DIV><SPAN=20
style=3D"FONT-SIZE: 11pt; LINE-HEIGHT: 115%; FONT-FAMILY: =
'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; =
mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; =
mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New =
Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA">&nbsp;&nbsp;&nbsp;&nbsp;=20
But the DHCPServer is configure to do both AAAA and PTR forcefully. Then =
what=20
should the DHCPServer should send the values in the flags ?</SPAN></DIV>
<DIV><SPAN=20
style=3D"FONT-SIZE: 11pt; LINE-HEIGHT: 115%; FONT-FAMILY: =
'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; =
mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; =
mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New =
Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA">&nbsp;&nbsp;&nbsp;&nbsp;=20
should it send like&nbsp; N=3D0,O=3D1,S=3D1 ?&nbsp;</SPAN></DIV>
<DIV><SPAN=20
style=3D"FONT-SIZE: 11pt; LINE-HEIGHT: 115%; FONT-FAMILY: =
'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; =
mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; =
mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New =
Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA">&nbsp;&nbsp;&nbsp;&nbsp;=20
RFC says O=3D1&nbsp;only&nbsp;if there is change in S=3D1, in the above=20
scenario&nbsp;S is always 1.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </SPAN></DIV>
<DIV><SPAN=20
style=3D"FONT-SIZE: 11pt; LINE-HEIGHT: 115%; FONT-FAMILY: =
'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; =
mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; =
mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New =
Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA"></SPAN>&nbsp;</DIV>
<DIV><SPAN=20
style=3D"FONT-SIZE: 11pt; LINE-HEIGHT: 115%; FONT-FAMILY: =
'Calibri','sans-serif'; mso-ascii-theme-font: minor-latin; =
mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; =
mso-hansi-theme-font: minor-latin; mso-bidi-font-family: 'Times New =
Roman'; mso-bidi-theme-font: minor-bidi; mso-ansi-language: EN-US; =
mso-fareast-language: EN-US; mso-bidi-language: =
AR-SA"></SPAN>&nbsp;</DIV>
<DIV><FONT color=3D#bf005f>Yo</FONT><FONT color=3D#0000ff>ur</FONT><FONT =

color=3D#00ff80>s e</FONT><FONT color=3D#ff007f>ve</FONT>r</DIV>
<DIV>-<A href=3D"http://spaces.msn.com/ramasubbu" target=3D_blank=20
rel=3Dnofollow>RamaSubbu SK</A>&nbsp;<IMG=20
src=3D"http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/14.gif"=20
NOSEND=3D"1"></DIV>
<DIV></DIV></DIV><BR>
<HR SIZE=3D1>
Park yourself in front of a world of choices in alternative =
vehicles.<BR><A=20
href=3D"http://us.rd.yahoo.com/evt=3D48246/*http://autos.yahoo.com/green_=
center/;_ylc=3DX3oDMTE5cDF2bXZzBF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDZ3=
JlZW4tY2VudGVy">Visit=20
the Yahoo! Auto Green Center.</A></BODY></HTML>

------_=_NextPart_001_01C7D2BB.98DD2308--


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

--===============0296041324==--




From dhcwg-bounces@ietf.org Tue Jul 31 13:13:19 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 1IFvHW-0008FB-Lp; Tue, 31 Jul 2007 13:13:14 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IFvHU-0008E4-Ob
	for dhcwg@ietf.org; Tue, 31 Jul 2007 13:13:12 -0400
Received: from web84103.mail.mud.yahoo.com ([68.142.206.190])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IFvHT-0001EX-SY
	for dhcwg@ietf.org; Tue, 31 Jul 2007 13:13:12 -0400
Received: (qmail 60647 invoked by uid 60001); 31 Jul 2007 17:13:11 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID;
	b=B2O6WfMW5oaecKp82CZosHp85WNRn5reHblKH35Fsux05IpESecu4iflxY44DJjt3tMpNqfYInCO5NKF82d7zV58u71p36Khobzdm1uVHeGnXH8C4HEllXxgKsfAfV7G6kWS9C7u9ae+TLL+CnMIm40kbrQ6JpOd4DZdLf38VsQ=;
X-YMail-OSG: .smwQxwVM1mleGivFTfCu8jaf9ed7wiNgvNJDAAl41HWd0z2reitTyZuE7UZTcV5nGskMpkaOjG2JSxgTKKW1u8g
Received: from [206.16.17.212] by web84103.mail.mud.yahoo.com via HTTP;
	Tue, 31 Jul 2007 10:13:11 PDT
X-Mailer: YahooMailRC/651.41 YahooMailWebService/0.7.41.16
Date: Tue, 31 Jul 2007 10:13:10 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: [dhcwg] Agenda for IETF-69 dhc WG meeting
To: "Bernie Volz \(volz\)" <volz@cisco.com>, Ted Lemon <mellon@fugue.com>
MIME-Version: 1.0
Message-ID: <288761.55548.qm@web84103.mail.mud.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
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="===============1772920794=="
Errors-To: dhcwg-bounces@ietf.org

--===============1772920794==
Content-Type: multipart/alternative; boundary="0-280579711-1185901990=:55548"

--0-280579711-1185901990=:55548
Content-Type: text/plain; charset=ascii

I agree that if there are implementations we should not break them. Yes, we can recommend such a mapping in the revision.
Thanks for the feedback.

--behcet

----- Original Message ----
From: Bernie Volz (volz) <volz@cisco.com>
To: Behcet Sarikaya <sarikaya@ieee.org>; Ted Lemon <mellon@fugue.com>
Cc: dhcwg@ietf.org
Sent: Friday, July 27, 2007 3:26:00 PM
Subject: RE: [dhcwg] Agenda for IETF-69 dhc WG meeting



 
DIV {
MARGIN:0px;}



Why doesn't the AR maintain a mapping between device and 
IAID (you could use a hash of the remote device's identity - mac address or 
whatever - and handle collisions appropriately).

 

We are NOT about to break existing implementations just 
because you want the field bigger. As Ted already pointed out, others might want 
or need larger fields.

 

The 4-byte IAID allows 4 billion PDs. That should be more 
than enough for any application. So, if you can't stuff what you need into the 
field, you'll have to develop a mapping scheme and maintain the mapping 
table.

 

- Bernie




From: Behcet Sarikaya 
[mailto:behcetsarikaya@yahoo.com] 
Sent: Tuesday, July 24, 2007 3:26 
PM
To: Ted Lemon
Cc: dhcwg@ietf.org
Subject: Re: 
[dhcwg] Agenda for IETF-69 dhc WG meeting






Comments 
in line.
Regards,

Behcet


----- 
Original Message ----
From: Ted Lemon <mellon@fugue.com>
To: Behcet 
Sarikaya <sarikaya@ieee.org>
Cc: dhcwg@ietf.org
Sent: Tuesday, July 
24, 2007 12:42:38 AM
Subject: Re: [dhcwg] Agenda for IETF-69 dhc WG 
meeting


On Mon, 2007-07-23 at 20:17 -0700, Behcet Sarikaya wrote:
> In RFC 
3633, IAID is defined as 4 octet field to be the unique
> identifier for 
each IA_PD. 
> In view of per-Mobile Node prefix delegation, I suggest 
that we extend
> IAID to be 6 octets and use MAC address of MN for which 
the prefix is
> requested. This way the access router can keep track of 
each prefix it
> receives by associating the prefix with the MAC address. 


Why not make the IAID 16 octets, just in case we have a link with 
a
fatter address, or want to stuff a UUID in it or something?   Or 
we
could have it be arbitrrily long.

I don't mean to be sarcastic, but 
just to illustrate the problem with
this kind of thinking.   It 
really can't work.   The reason we chose a
four-byte IAID was to 
allow for a 32-bit interface index, not to allow
you to put a client-sourced 
identifier in it.

The question that comes to my mind with this proposal 
is, why not just
have the device that's getting the delegated prefix make the 
DHCP prefix
delegation request?   Why all this additional 
complexity?

[behcet] IPv6 address configuration requires the device to 
configure an address from the prefix in RA (router advertisement) or get it from 
DHCP. The device does not get the prefix directly.  It is the AR that 
should get it and create the point to point link.

[behcet] What I have 
proposed is that 32-bit interface index of IAID may probably need to be 
revisited because of this new application of DHCP PD which is client 
oriented.
It is up to you, just 
asking.









--0-280579711-1185901990=:55548
Content-Type: text/html; charset=ascii

<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:14pt"><div style="font-family: times new roman,new york,times,serif; font-size: 14pt;">I agree that if there are implementations we should not break them. Yes, we can recommend such a mapping in the revision.<br>Thanks for the feedback.<br><br>--behcet<br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Bernie Volz (volz) &lt;volz@cisco.com&gt;<br>To: Behcet Sarikaya &lt;sarikaya@ieee.org&gt;; Ted Lemon &lt;mellon@fugue.com&gt;<br>Cc: dhcwg@ietf.org<br>Sent: Friday, July 27, 2007 3:26:00 PM<br>Subject: RE: [dhcwg] Agenda for IETF-69 dhc WG meeting<br><br>

 
<style type="text/css">DIV {
MARGIN:0px;}
</style>


<div dir="ltr" align="left"><span class="376102320-27072007"><font color="#0000ff" face="Arial" size="2">Why doesn't the AR maintain a mapping between device and 
IAID (you could use a hash of the remote device's identity - mac address or 
whatever - and handle collisions appropriately).</font></span></div>
<div dir="ltr" align="left"><span class="376102320-27072007"><font color="#0000ff" face="Arial" size="2"></font></span>&nbsp;</div>
<div dir="ltr" align="left"><span class="376102320-27072007"><font color="#0000ff" face="Arial" size="2">We are NOT about to break existing implementations just 
because you want the field bigger. As Ted already pointed out, others might want 
or need larger fields.</font></span></div>
<div dir="ltr" align="left"><span class="376102320-27072007"><font color="#0000ff" face="Arial" size="2"></font></span>&nbsp;</div>
<div dir="ltr" align="left"><span class="376102320-27072007"><font color="#0000ff" face="Arial" size="2">The 4-byte IAID allows 4 billion PDs. That should be more 
than enough for any application. So, if you can't stuff what you need into the 
field, you'll have to develop a mapping scheme and maintain the mapping 
table.</font></span></div>
<div dir="ltr" align="left"><span class="376102320-27072007"><font color="#0000ff" face="Arial" size="2"></font></span>&nbsp;</div>
<div dir="ltr" align="left"><span class="376102320-27072007"><font color="#0000ff" face="Arial" size="2">- Bernie</font></span></div><br>
<div class="OutlookMessageHeader" dir="ltr" align="left" lang="en-us">
<hr tabindex="-1">
<font face="Tahoma" size="2"><b>From:</b> Behcet Sarikaya 
[mailto:behcetsarikaya@yahoo.com] <br><b>Sent:</b> Tuesday, July 24, 2007 3:26 
PM<br><b>To:</b> Ted Lemon<br><b>Cc:</b> dhcwg@ietf.org<br><b>Subject:</b> Re: 
[dhcwg] Agenda for IETF-69 dhc WG meeting<br></font><br></div>
<div></div>
<div style="font-size: 14pt; font-family: times new roman,new york,times,serif;">
<div style="font-size: 14pt; font-family: times new roman,new york,times,serif;">Comments 
in line.<br>Regards,<br><br>Behcet<br><br>
<div style="font-size: 12pt; font-family: times new roman,new york,times,serif;">----- 
Original Message ----<br>From: Ted Lemon &lt;mellon@fugue.com&gt;<br>To: Behcet 
Sarikaya &lt;sarikaya@ieee.org&gt;<br>Cc: dhcwg@ietf.org<br>Sent: Tuesday, July 
24, 2007 12:42:38 AM<br>Subject: Re: [dhcwg] Agenda for IETF-69 dhc WG 
meeting<br><br>
<div>On Mon, 2007-07-23 at 20:17 -0700, Behcet Sarikaya wrote:<br>&gt; In RFC 
3633, IAID is defined as 4 octet field to be the unique<br>&gt; identifier for 
each IA_PD. <br>&gt; In view of per-Mobile Node prefix delegation, I suggest 
that we extend<br>&gt; IAID to be 6 octets and use MAC address of MN for which 
the prefix is<br>&gt; requested. This way the access router can keep track of 
each prefix it<br>&gt; receives by associating the prefix with the MAC address. 
<br><br>Why not make the IAID 16 octets, just in case we have a link with 
a<br>fatter address, or want to stuff a UUID in it or something?&nbsp;&nbsp; Or 
we<br>could have it be arbitrrily long.<br><br>I don't mean to be sarcastic, but 
just to illustrate the problem with<br>this kind of thinking.&nbsp;&nbsp; It 
really can't work.&nbsp;&nbsp; The reason we chose a<br>four-byte IAID was to 
allow for a 32-bit interface index, not to allow<br>you to put a client-sourced 
identifier in it.<br><br>The question that comes to my mind with this proposal 
is, why not just<br>have the device that's getting the delegated prefix make the 
DHCP prefix<br>delegation request?&nbsp;&nbsp; Why all this additional 
complexity?<br><br>[behcet] IPv6 address configuration requires the device to 
configure an address from the prefix in RA (router advertisement) or get it from 
DHCP. The device does not get the prefix directly.&nbsp; It is the AR that 
should get it and create the point to point link.<br><br>[behcet] What I have 
proposed is that 32-bit interface index of IAID may probably need to be 
revisited because of this new application of DHCP PD which is client 
oriented.<br>It is up to you, just 
asking.<br></div></div><br></div></div></div><br></div></div></body></html>
--0-280579711-1185901990=:55548--


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

--===============1772920794==--




