From dhcwg-bounces@ietf.org  Fri Dec  3 03:33:49 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11994
	for <dhcwg-web-archive@ietf.org>; Fri, 3 Dec 2004 03:33:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ca8yb-0005mj-QP
	for dhcwg-web-archive@ietf.org; Fri, 03 Dec 2004 03:39:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ca7OE-0006cf-NY; Fri, 03 Dec 2004 01:58:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ca5sg-0007jS-BX
	for dhcwg@megatron.ietf.org; Fri, 03 Dec 2004 00:21:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11652
	for <dhcwg@ietf.org>; Fri, 3 Dec 2004 00:21:19 -0500 (EST)
Received: from mail-sin1.microsoft.com ([207.46.50.72])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ca5yK-0001ow-VK
	for dhcwg@ietf.org; Fri, 03 Dec 2004 00:27:14 -0500
Received: from APS-MSG-02.southpacific.corp.microsoft.com ([157.60.218.52]) by
	mail-sin1.microsoft.com with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 3 Dec 2004 14:20:42 +0900
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 3 Dec 2004 13:20:33 +0800
Message-ID: <91AC940D24F18041A3A68895289CE1EE012A5B0F@APS-MSG-02.southpacific.corp.microsoft.com>
Thread-Topic: Relay Agent Options.
Thread-Index: AcTXAHV5wDh4IFhFSEiILv1BYPxVzQB9rG8g
From: "Achint Setia" <asetia@microsoft.com>
To: <dhcwg@ietf.org>
X-OriginalArrivalTime: 03 Dec 2004 05:20:43.0037 (UTC)
	FILETIME=[D5E62CD0:01C4D8F7]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Content-Transfer-Encoding: quoted-printable
Subject: [dhcwg] Relay Agent Options.
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Content-Transfer-Encoding: quoted-printable


Hi,

I have a couple of doubts regarding the Relay Agent Options:-

1. What is the motive behind allowing the relay agent to add options
while    =20
   forwarding the client packet to the server? Are they to be used by
the    =20
   server in configuration selection for the client?

2. If yes, does that mean that when the server sends back the Relay
Reply,
   the ONLY TWO options that can be included are the Relay Message and
the   =20
   interface id.
   I am asking this because I am not sure as to how the relay agent will

   handle options other than these two in the Relay Reply?

Hope someone can clarify them.

Thanks,
Achint Setia.
=20
=20

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


From dhcwg-bounces@ietf.org  Fri Dec  3 03:35:20 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12060
	for <dhcwg-web-archive@ietf.org>; Fri, 3 Dec 2004 03:35:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ca907-0005oD-Gc
	for dhcwg-web-archive@ietf.org; Fri, 03 Dec 2004 03:41:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ca7On-0006pF-8v; Fri, 03 Dec 2004 01:58:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ca60A-0000QP-HV
	for dhcwg@megatron.ietf.org; Fri, 03 Dec 2004 00:29:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12448
	for <dhcwg@ietf.org>; Fri, 3 Dec 2004 00:29:03 -0500 (EST)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ca65q-0001xu-0D
	for dhcwg@ietf.org; Fri, 03 Dec 2004 00:34:58 -0500
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by rtp-iport-1.cisco.com with ESMTP; 03 Dec 2004 00:37:19 -0500
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iB35SVqR014305
	for <dhcwg@ietf.org>; Fri, 3 Dec 2004 00:28:31 -0500 (EST)
Received: from rdroms-w2k01.cisco.com (sjc-vpn1-1387.cisco.com [10.21.101.107])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANL06972;
	Fri, 3 Dec 2004 00:28:28 -0500 (EST)
Message-Id: <4.3.2.7.2.20041203002517.02039a98@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 03 Dec 2004 00:28:25 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7e439b86d3292ef5adf93b694a43a576
Subject: [dhcwg] *DRAFT* minutes from dhc WG meeting in DC
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25eb6223a37c19d53ede858176b14339

Here are the draft minutes of the dhc WG meeting in DC.  Please review and
respond with comments by 1700 EST, Mon 2004-12-06

- Ralph Droms

-----

Administrivia                                      Ralph Droms

Droms asked about interest in DHCP server MIB,
draft-ietf-dhc-server-mib.  The specification has been reviewed by the
IESG and is close to being done.  However, one author is not
interested in continuing to work on the specification and the other
wants to confirm that there is sufficient interest before committing
to more work on the document.  Ted Lemon expressed interest in seeing
a server MIB (although not necessarily this one).  Droms will work
with Glen Waters (document co-author) to complete the specification.


Reclassifying DHCPv4 Options                       Bernie Volz

draft-ietf-dhc-reclassify-options is about to be published as an RFC.
Volz described the process for broadcasting notification of the
process specified in the document, and asked for assistance in
identifying all vendors whose use of option codes will be affected by
this specification.


DNS zone suffix option for DHCPv6                  Renxiang Yan
draft-yan-dhc-dhcpv6-opt-dnszone

Yan gave a presentation about draft-yan-dhc-dhcpv6-opt-dnszone.  The
key idea is to send the DNS domain from which a host should form its
FQDN to the host.  Ted Lemon noted that the mechanism in this
specification supposes that the host will then use DDNS to update its
DNS information.  This use of DDNS will require management of
authorization information for individual hosts, which won't scale.
The RA-based mechanism in draft-jeong-ipv6-ra-dns-autoconf has similar
issues of scale.  Further discussion will take place on the WG mailing
list before coming to a decision about taking this draft on as a WG
work item.


Vendor-Specific Information Suboption              Mark Stapp
draft-stapp-dhc-vendor-suboption

There was consensus in the room to take this draft to WG last call.
Droms will confirm consensus on the WG mailing list.


DHCP Authentication via EAP                        Mark Stapp

Stapp presented summary of idea to use EAP for DHCP authentication (no
document, yet).  The premise of this work is that requiring the use of
another set of keys around just to do DHCP is a non-starter and DNSSEC
is not ready, so Stapp suggests using credentials already provisioned
for 802.1x for DHCP authentication.  There was some discussion about
where in the authentication system (AAA server?) session keys might be
generated.  Stapp will write a draft based on his ideas for WG review.


Information Refresh Time Option for DHCPv6         Stig Venaas
draft-ietf-dhc-lifetime

Venaas gave an update about the draft, which has been previously
discussed by the WG.  The title of the specification has been changed
to "Information Refresh Time Option for DHCPv6" as the option controls
when a client contacts the DHCP server, but does not cause previously
obtained information to expire in any way.  Some minor issues were
raised about max and min values for lifetime which will be discussed
on WG mailing list.  Pending that discussion, there was consensus in
room to go to WG last call.  Consensus to be confirmed on WG mailing
list.


Multicast Reconfig. Protocol for Stateless DHCPv6  Daniel Park
draft-vijay-dhc-dhcpv6-mcast-reconf

Park gave a summary of the draft.  Droms asked why the protocol uses
Relay-reply message to notify router (through relay) to toggle 'M'/'O'
bits; isn't CLI sufficient?  Greg Daley suggested SNMP might be
appropriate to cause router to toggle 'M'/'O' bits.  Some additional
discussion about whether this mechanism is needed if "Information
Refresh Time Option for DHCPv6" is accepted for standards track.  Volz
pointed out that "multicast reconfig" is useful for unplanned
renumbering.  Park was requested to provide more detail; further
discussion will take place on the WG mailing list before coming to a
decision about taking this draft on as a WG work item.


Anycast Address Assignment using DHCPv6            Syam Madanapalli
draft-madanapalli-dhcpv6-anycast

Madanapalli presented summary of the draft.  Ted Lemon pointed out
that the slides were somewhat different from the text in
"draft-madanapalli-dhcpv6-anycast", and that the second part of the
specification (in which the services are classified) begins to look a
lot like SLP.  Droms suggested the draft might be spit into two
pieces: one for assignment and one for service classification.  There
was consensus in the room to accept the draft as a WG work item; the
consensus will be confirmed on WG mailing list.


Source Address Selection Policy option for DHCPv6  T. Fujisaki
draft-hirotaka-dhc-source-address-selection-opt

This draft provides a protocol for distribution of address selection
policy, where those policies are described in RFC 3484.  The draft is
related to other drafts about distribution of policy currently before
the ipv6 and multi6 WGs.  John Schnizlein asked if this draft is
really solving a routing problem.  Ted Lemon asked if this is for
reasonably stable and static multi-homed networks' authors agreed that
this is for source address selection policy, not routing information.
Further discussion will take place on the WG mailing list before
coming to a decision about taking this draft on as a WG work item.


DHCPv6 Relay Agent Information Option              Wing Cheong Lau
draft-droms-dhc-v6-relayopt

The consensus in the room was to accept the draft as a WG work item;
consensus will be confirmed on WG mailing list.


Clarifications on DHCPv6 Authentication            T. Jinmei
draft-ietf-dhc-dhcpv6-clarify-auth

Jinmei-san presented a list of changes to the draft in the most recent
revision and a couple of outstanding issues:
* draft recommends treating multiple exchanges as a single "session",
   which requires additional state in the server
* should this draft be published independently or rolled into a
   revision of RFC 3315?
Jinmei-san will initiate discussion of a couple of outstanding issues
and then the draft will be ready for WG last call.


DHCP Relay Agent Opt for MIPv6 bootstrapping       Kuntal Chowdhury
draft-chowdhury-dhc-mip6-agentop

J. Bharatia presented a summary of the draft, which provides a
mechanism through which a remote AAA server can pass the address of a
MIP6 home agent to a roaming MIP6 host for initial
configuration/bootstrapping.  Mark Stapp objected to the relay agent
modifying the DHCP message rather than inserting information in the
relay option wrapper.  It was mentioned that a similar draft that
accomplishes the same objective without DHCP is under consideration in
the mip6 WG. The author was requested to revise the draft to avoid
modification of the DHCP message by the relay and the WG will consider
the revised draft.


DHCP-DNS interaction                               Bernie Volz
draft-ietf-dhc-dhcpv6-fqdn
draft-ietf-dhc-fqdn-option
draft-ietf-dhc-ddns-resolution

Volz presented a status report: these drafts along with
draft-ietf-dhc-3315id-for-v4 and draft-ietf-dnsext-dhcid-rr will go to
the IESG as a package.  draft-ietf-dnsext-dhcid-rr is through WG last
call (dnsext).  The consensus in the room was to go to WG last call on
draft-ietf-dhc-fqdn-option; consensus will be confirmed on the WG
mailing list.


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


From dhcwg-bounces@ietf.org  Fri Dec  3 03:41:07 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA12330
	for <dhcwg-web-archive@ietf.org>; Fri, 3 Dec 2004 03:41:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ca95h-0005tj-3D
	for dhcwg-web-archive@ietf.org; Fri, 03 Dec 2004 03:47:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ca7Oq-0006qs-NZ; Fri, 03 Dec 2004 01:58:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ca60c-0000X6-Ki
	for dhcwg@megatron.ietf.org; Fri, 03 Dec 2004 00:29:34 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12487
	for <dhcwg@ietf.org>; Fri, 3 Dec 2004 00:29:31 -0500 (EST)
Received: from mail-sin2.microsoft.com ([207.46.50.82])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ca66H-0001yO-7D
	for dhcwg@ietf.org; Fri, 03 Dec 2004 00:35:26 -0500
Received: from APS-MSG-02.southpacific.corp.microsoft.com ([157.60.218.52]) by
	mail-sin2.microsoft.com with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 3 Dec 2004 13:29:03 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Dec 2004 13:28:59 +0800
Message-ID: <91AC940D24F18041A3A68895289CE1EE012A5B22@APS-MSG-02.southpacific.corp.microsoft.com>
Thread-Topic: DHCPv4 equivalent for DHCPv6 Options ?
Thread-Index: AcTY+P2xMvLQVcDeTgq8u87nrpwApw==
From: "Achint Setia" <asetia@microsoft.com>
To: <dhcwg@ietf.org>
X-OriginalArrivalTime: 03 Dec 2004 05:29:03.0048 (UTC)
	FILETIME=[FFEDCC80:01C4D8F8]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Subject: [dhcwg] DHCPv4 equivalent for DHCPv6 Options ?
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="===============0372430955=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: c54bc2f42d02429833c0ca4b8725abd7

This is a multi-part message in MIME format.

--===============0372430955==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4D8F8.FE775740"

This is a multi-part message in MIME format.

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

Hi,

=20

Is there any plan to have an equivalent RFC for DHCPv6 as RFC2132
defining various DHCPv4 options?

Are the DHCPv4 defined options to be supported in DHCPv6 in exactly the
same manner (syntax and behavior)

as they were in v4.

=20

Thanks,

Achint Setia.

=20

=20

=20


------_=_NextPart_001_01C4D8F8.FE775740
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Hi,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Is there any plan to have an equivalent RFC for =
DHCPv6 as
RFC2132 defining various DHCPv4 options?</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Are the DHCPv4 defined options to be supported in =
DHCPv6 in
exactly the same manner (syntax and behavior)</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>as they were in v4.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thanks,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Achint Setia.</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C4D8F8.FE775740--


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

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

--===============0372430955==--



From dhcwg-bounces@ietf.org  Fri Dec  3 03:56:08 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13156
	for <dhcwg-web-archive@ietf.org>; Fri, 3 Dec 2004 03:56:08 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ca9KF-0006BU-Pu
	for dhcwg-web-archive@ietf.org; Fri, 03 Dec 2004 04:02:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ca7PZ-0007BS-Kl; Fri, 03 Dec 2004 01:59:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ca6Ce-00018F-7f
	for dhcwg@megatron.ietf.org; Fri, 03 Dec 2004 00:42:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13419
	for <dhcwg@ietf.org>; Fri, 3 Dec 2004 00:41:56 -0500 (EST)
Received: from mail-sin2.microsoft.com ([207.46.50.82])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ca6IJ-0002DJ-Ip
	for dhcwg@ietf.org; Fri, 03 Dec 2004 00:47:52 -0500
Received: from APS-MSG-02.southpacific.corp.microsoft.com ([157.60.218.52]) by
	mail-sin2.microsoft.com with Microsoft SMTPSVC(6.0.3790.211); 
	Fri, 3 Dec 2004 13:41:22 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 3 Dec 2004 13:41:22 +0800
Message-ID: <91AC940D24F18041A3A68895289CE1EE012A5B45@APS-MSG-02.southpacific.corp.microsoft.com>
Thread-Topic: IPv6 Interface Identifiers.
Thread-Index: AcTY+rhv8YMyu34UTN6P0bvIs0y8sg==
From: "Achint Setia" <asetia@microsoft.com>
To: <dhcwg@ietf.org>
X-OriginalArrivalTime: 03 Dec 2004 05:41:22.0399 (UTC)
	FILETIME=[B89DCEF0:01C4D8FA]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d2b46e3b2dfbff2088e0b72a54104985
Subject: [dhcwg] IPv6 Interface Identifiers.
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="===============0272573651=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: ee80a2074afbfe28d15369f4e74e579d

This is a multi-part message in MIME format.

--===============0272573651==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4D8FA.B874D725"

This is a multi-part message in MIME format.

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

I had this general doubt while reading the DHCPv6 RFC (3315).

=20

When the addresses are assigned by a DHCPv6 server, the interface
identifier will correspond to the one chosen

by the server from within its scope. This can be any number depending on
how the scopes are defined at the server.

Doesn't this contradict RFC 2373, which clearly states that the 64 bit
Interface Identifier should be in EUI -64 format ?

Or does that mean the server needs to CONVERT the interface id, it has
chosen, into the EUI-64 format before assigning it

to the client?

=20

Thanks,

Achint Setia.

=20

=20

=20


------_=_NextPart_001_01C4D8FA.B874D725
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered)">
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I had this general doubt while reading the DHCPv6 RFC =
(3315).</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>When the addresses are assigned by a DHCPv6 server, =
the
interface identifier will correspond to the one chosen</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>by the server from within its scope. This can be any =
number
depending on how the scopes are defined at the server.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Doesn&#8217;t this contradict RFC 2373, which clearly =
states
that the 64 bit Interface Identifier should be in EUI -64 format =
?</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Or does that mean the server needs to CONVERT the =
interface
id, it has chosen, into the EUI-64 format before assigning =
it</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>to the client?</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thanks,</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Achint Setia.</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C4D8FA.B874D725--


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

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

--===============0272573651==--



From dhcwg-bounces@ietf.org  Fri Dec  3 10:47:00 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18226
	for <dhcwg-web-archive@ietf.org>; Fri, 3 Dec 2004 10:47:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaFju-0006Zd-Mp
	for dhcwg-web-archive@ietf.org; Fri, 03 Dec 2004 10:52:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaDOo-0000rD-Bs; Fri, 03 Dec 2004 08:23:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaBoo-000715-6h
	for dhcwg@megatron.ietf.org; Fri, 03 Dec 2004 06:41:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25689
	for <dhcwg@ietf.org>; Fri, 3 Dec 2004 06:41:43 -0500 (EST)
Received: from fivedots.coe.psu.ac.th ([202.12.73.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaBuW-00012m-Jn
	for dhcwg@ietf.org; Fri, 03 Dec 2004 06:47:41 -0500
Received: from delta.coe.psu.ac.th ([172.30.0.98] helo=delta.noi.kre.to)
	by fivedots.coe.psu.ac.th with esmtp (Exim 3.36 #1 (Debian))
	id 1CaBoh-0007BJ-00; Fri, 03 Dec 2004 18:41:39 +0700
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.noi.kre.to (8.12.9/8.11.6) with ESMTP id iB3BfbkW001980;
	Fri, 3 Dec 2004 18:41:37 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: "Achint Setia" <asetia@microsoft.com>
Subject: Re: [dhcwg] IPv6 Interface Identifiers. 
In-Reply-To: <91AC940D24F18041A3A68895289CE1EE012A5B45@APS-MSG-02.southpacific.corp.microsoft.com>
References: <91AC940D24F18041A3A68895289CE1EE012A5B45@APS-MSG-02.southpacific.corp.microsoft.com>
Date: Fri, 03 Dec 2004 18:41:37 +0700
Message-ID: <13695.1102074097@munnari.OZ.AU>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007

    Date:        Fri, 3 Dec 2004 13:41:22 +0800
    From:        "Achint Setia" <asetia@microsoft.com>
    Message-ID:  <91AC940D24F18041A3A68895289CE1EE012A5B45@APS-MSG-02.southpacific.corp.microsoft.com>

  | Doesn't this contradict RFC 2373, which clearly states that the 64 bit
  | Interface Identifier should be in EUI -64 format ?

Perhaps, though a DHCP server could certainly generate addresses
that look as if they contain EUI-64 formatted interface identifiers
if it wants to - but almost anything sensible contradicts much of
what is in that part of RFC2373 - simply ignore it, the part of
2373 that is pretending to tell people what they should (must) be
using bits for inside their addigned address space is simply nonsense.

Use addresses however you want to use them, all that matters is
that the address chosen results in packets being delivered to the
correct system.

kre

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


From dhcwg-bounces@ietf.org  Fri Dec  3 13:27:33 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15706
	for <dhcwg-web-archive@ietf.org>; Fri, 3 Dec 2004 13:27:33 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaIFK-0006rr-RB
	for dhcwg-web-archive@ietf.org; Fri, 03 Dec 2004 13:33:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaEuA-0000Mf-Rf; Fri, 03 Dec 2004 09:59:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaEF9-0001xj-B0
	for dhcwg@megatron.ietf.org; Fri, 03 Dec 2004 09:17:07 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07774
	for <dhcwg@ietf.org>; Fri, 3 Dec 2004 09:17:06 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaEKs-0004UF-Iz
	for dhcwg@ietf.org; Fri, 03 Dec 2004 09:23:04 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 03 Dec 2004 06:21:42 -0800
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iB3EGSSt004998;
	Fri, 3 Dec 2004 06:16:28 -0800 (PST)
Received: from volzw2k (che-vpn-cluster-1-188.cisco.com [10.86.240.188])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANL21824;
	Fri, 3 Dec 2004 09:16:28 -0500 (EST)
From: "Bernie Volz" <volz@cisco.com>
To: "'Achint Setia'" <asetia@microsoft.com>, <dhcwg@ietf.org>
Subject: RE: [dhcwg] Relay Agent Options.
Date: Fri, 3 Dec 2004 09:16:28 -0500
Organization: Cisco
Message-ID: <002801c4d942$ae648a30$6701a8c0@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-reply-to: <91AC940D24F18041A3A68895289CE1EE012A5B0F@APS-MSG-02.southpacific.corp.microsoft.com>
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: 7bit

Hi:

The motive is that there may be options similar to the DHCPv4 relay-agent
options that will be defined in the future. This might include subscriber
ID, remote agent ID, Radius options, etc. (I am planning to write up these
I-Ds but just haven't had the time yet.) Also, the relay agent can include
the vendor options (though RFC 3315 isn't that clear about that).

Presently, a server MUST send back the Interface-ID option and can ignore
any others (except of course for the Relay Message Option).

- Bernie

> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] 
> On Behalf Of Achint Setia
> Sent: Friday, December 03, 2004 12:21 AM
> To: dhcwg@ietf.org
> Subject: [dhcwg] Relay Agent Options.
> 
> 
> 
> Hi,
> 
> I have a couple of doubts regarding the Relay Agent Options:-
> 
> 1. What is the motive behind allowing the relay agent to add options
> while     
>    forwarding the client packet to the server? Are they to be used by
> the     
>    server in configuration selection for the client?
> 
> 2. If yes, does that mean that when the server sends back the 
> Relay Reply,
>    the ONLY TWO options that can be included are the Relay Message and
> the    
>    interface id.
>    I am asking this because I am not sure as to how the relay 
> agent will
> 
>    handle options other than these two in the Relay Reply?
> 
> Hope someone can clarify them.
> 
> Thanks,
> Achint Setia.
>  
>  
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg
> 


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


From dhcwg-bounces@ietf.org  Fri Dec  3 13:27:41 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15740
	for <dhcwg-web-archive@ietf.org>; Fri, 3 Dec 2004 13:27:41 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaIFR-0006sH-OI
	for dhcwg-web-archive@ietf.org; Fri, 03 Dec 2004 13:33:43 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaEuc-0000WH-Km; Fri, 03 Dec 2004 09:59:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaEKc-0002RV-TW
	for dhcwg@megatron.ietf.org; Fri, 03 Dec 2004 09:22:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08272
	for <dhcwg@ietf.org>; Fri, 3 Dec 2004 09:22:45 -0500 (EST)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaEQL-0004ar-Dz
	for dhcwg@ietf.org; Fri, 03 Dec 2004 09:28:43 -0500
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by rtp-iport-2.cisco.com with ESMTP; 03 Dec 2004 09:22:08 -0500
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iB3EM5qR022899; 
	Fri, 3 Dec 2004 09:22:06 -0500 (EST)
Received: from volzw2k (che-vpn-cluster-1-188.cisco.com [10.86.240.188])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANL22228;
	Fri, 3 Dec 2004 09:22:04 -0500 (EST)
From: "Bernie Volz" <volz@cisco.com>
To: "'Achint Setia'" <asetia@microsoft.com>, <dhcwg@ietf.org>
Subject: RE: [dhcwg] DHCPv4 equivalent for DHCPv6 Options ?
Date: Fri, 3 Dec 2004 09:22:04 -0500
Organization: Cisco
Message-ID: <002901c4d943$76b535c0$6701a8c0@amer.cisco.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-reply-to: <91AC940D24F18041A3A68895289CE1EE012A5B22@APS-MSG-02.southpacific.corp.microsoft.com>
Importance: Normal
X-Spam-Score: 0.3 (/)
X-Scan-Signature: a492040269d440726bfd84680622cee7
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="===============0621234774=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 325b777e1a3a618c889460b612a65510

This is a multi-part message in MIME format.

--===============0621234774==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_002A_01C4D919.8DDF2DC0"

This is a multi-part message in MIME format.

------=_NextPart_000_002A_01C4D919.8DDF2DC0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Is there any plan to have an equivalent RFC for DHCPv6 as RFC2132 =
defining
various DHCPv4 options?

=20
No, there are RFCs and I-Ds that will define DHCPv6 options. See
http://www.iana.org/assignments/dhcpv6-parameters for the official list =
of
assigned DHCPv6 option numbers and references to the RFCs that define =
them.
For work in progress, best to see
http://www.ietf.org/html.charters/dhc-charter.html.
=20
Are the DHCPv4 defined options to be supported in DHCPv6 in exactly the =
same
manner (syntax and behavior) as they were in v4.
=20
No. We decided early on that we wanted a clean slate. Therefore, if =
there
are options from DHCPv4 that are desired in DHCPv6, someone needs to =
write
an Internet-Draft and get it to an RFC.
=20
If there are vendor specific options, use the OPTION_VENDOR_CLASS and
OPTION_VENDOR_OPTS options.
=20
- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf =
Of
Achint Setia
Sent: Friday, December 03, 2004 12:29 AM
To: dhcwg@ietf.org
Subject: [dhcwg] DHCPv4 equivalent for DHCPv6 Options ?



Hi,

=20

Is there any plan to have an equivalent RFC for DHCPv6 as RFC2132 =
defining
various DHCPv4 options?

Are the DHCPv4 defined options to be supported in DHCPv6 in exactly the =
same
manner (syntax and behavior)

as they were in v4.

=20

Thanks,

Achint Setia.

=20

=20

=20


------=_NextPart_000_002A_01C4D919.8DDF2DC0
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=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2900.2523" name=3DGENERATOR>
<STYLE>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<P class=3DMsoNormal><SPAN class=3D490351614-03122004><FONT face=3DArial =
color=3D#0000ff=20
size=3D2><FONT color=3D#000000>Is there any plan to have an equivalent =
RFC for=20
DHCPv6 as RFC2132 defining various DHCPv4 =
options?</FONT></FONT></SPAN></P>
<DIV><SPAN class=3D490351614-03122004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D490351614-03122004><FONT face=3DArial color=3D#0000ff =
size=3D2>No,=20
there are RFCs and I-Ds that will define DHCPv6 options. See <A=20
href=3D"http://www.iana.org/assignments/dhcpv6-parameters">http://www.ian=
a.org/assignments/dhcpv6-parameters</A>&nbsp;for=20
the official list of assigned DHCPv6 option numbers and references to =
the RFCs=20
that define them. For work in progress, best to see <A=20
href=3D"http://www.ietf.org/html.charters/dhc-charter.html">http://www.ie=
tf.org/html.charters/dhc-charter.html</A>.</FONT></SPAN></DIV>
<DIV><SPAN class=3D490351614-03122004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D490351614-03122004><FONT face=3DArial color=3D#0000ff =
size=3D2><FONT=20
color=3D#000000>Are the DHCPv4 defined options to be supported in DHCPv6 =
in=20
exactly the same manner (syntax and behavior) <SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">as they were in=20
v4.</SPAN></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=3D490351614-03122004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D490351614-03122004><FONT face=3DArial color=3D#0000ff =
size=3D2>No. We=20
decided early on that we wanted a clean slate. Therefore, if there are =
options=20
from DHCPv4 that are desired in DHCPv6, someone needs to write an =
Internet-Draft=20
and get it to an RFC.</FONT></SPAN></DIV>
<DIV><SPAN class=3D490351614-03122004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D490351614-03122004><FONT face=3DArial color=3D#0000ff =
size=3D2>If=20
there are vendor specific options, use the OPTION_VENDOR_CLASS and=20
OPTION_VENDOR_OPTS options.</FONT></SPAN></DIV>
<DIV><SPAN class=3D490351614-03122004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D490351614-03122004><FONT face=3DArial color=3D#0000ff =
size=3D2>-=20
Bernie</FONT></SPAN><SPAN class=3D490351614-03122004></DIV></SPAN>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
  dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] <B>On Behalf Of =

  </B>Achint Setia<BR><B>Sent:</B> Friday, December 03, 2004 12:29=20
  AM<BR><B>To:</B> dhcwg@ietf.org<BR><B>Subject:</B> [dhcwg] DHCPv4 =
equivalent=20
  for DHCPv6 Options ?<BR><BR></FONT></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Hi,</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Is there any plan to =
have an=20
  equivalent RFC for DHCPv6 as RFC2132 defining various DHCPv4=20
  options?</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Are the DHCPv4 defined =
options to=20
  be supported in DHCPv6 in exactly the same manner (syntax and=20
  behavior)</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">as they were in=20
  v4.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Thanks,</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Achint =
Setia.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: =
12pt"></SPAN></FONT>&nbsp;</P></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_002A_01C4D919.8DDF2DC0--



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

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

--===============0621234774==--




From dhcwg-bounces@ietf.org  Fri Dec  3 13:28:54 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15874
	for <dhcwg-web-archive@ietf.org>; Fri, 3 Dec 2004 13:28:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaIGd-0006vK-HP
	for dhcwg-web-archive@ietf.org; Fri, 03 Dec 2004 13:34:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaEv9-00019I-E5; Fri, 03 Dec 2004 10:00:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaEP7-0002kO-2e
	for dhcwg@megatron.ietf.org; Fri, 03 Dec 2004 09:27:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08750
	for <dhcwg@ietf.org>; Fri, 3 Dec 2004 09:27:23 -0500 (EST)
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.33)
	id 1CaEUr-0004gZ-Ea
	for dhcwg@ietf.org; Fri, 03 Dec 2004 09:33:21 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 03 Dec 2004 07:34:34 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iB3EQmSt011374;
	Fri, 3 Dec 2004 06:26:49 -0800 (PST)
Received: from volzw2k (che-vpn-cluster-1-188.cisco.com [10.86.240.188])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANL22509;
	Fri, 3 Dec 2004 09:26:49 -0500 (EST)
From: "Bernie Volz" <volz@cisco.com>
To: "'Achint Setia'" <asetia@microsoft.com>, <dhcwg@ietf.org>
Subject: RE: [dhcwg] IPv6 Interface Identifiers.
Date: Fri, 3 Dec 2004 09:26:49 -0500
Organization: Cisco
Message-ID: <002e01c4d944$20702340$6701a8c0@amer.cisco.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-reply-to: <91AC940D24F18041A3A68895289CE1EE012A5B45@APS-MSG-02.southpacific.corp.microsoft.com>
Importance: Normal
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 963faf56c3a5b6715f0b71b66181e01a
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="===============1207360294=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.6 (/)
X-Scan-Signature: 612a16ba5c5f570bfc42b3ac5606ac53

This is a multi-part message in MIME format.

--===============1207360294==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_002F_01C4D91A.379A1B40"

This is a multi-part message in MIME format.

------=_NextPart_000_002F_01C4D91A.379A1B40
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The DHCPv6 server can use the client's interface-identifier to addresses =
(by
extracting it from the appropriate place - either from the source =
address or
from the relay-agent's peer-address field if relayed). Or, the DHCPv6 =
server
can other techniques to generate addresses, such as random numbers, =
perhaps
using the RFC 3041 (or better yet,
http://www.ietf.org/internet-drafts/draft-ietf-ipv6-privacy-addrs-v2-01.t=
xt)
.
=20
- Bernie

-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf =
Of
Achint Setia
Sent: Friday, December 03, 2004 12:41 AM
To: dhcwg@ietf.org
Subject: [dhcwg] IPv6 Interface Identifiers.



I had this general doubt while reading the DHCPv6 RFC (3315).

=20

When the addresses are assigned by a DHCPv6 server, the interface =
identifier
will correspond to the one chosen

by the server from within its scope. This can be any number depending on =
how
the scopes are defined at the server.

Doesn't this contradict RFC 2373, which clearly states that the 64 bit
Interface Identifier should be in EUI -64 format ?

Or does that mean the server needs to CONVERT the interface id, it has
chosen, into the EUI-64 format before assigning it

to the client?

=20

Thanks,

Achint Setia.

=20

=20

=20


------=_NextPart_000_002F_01C4D91A.379A1B40
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=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2900.2523" name=3DGENERATOR>
<STYLE>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue>
<DIV><SPAN class=3D032172214-03122004><FONT face=3DArial color=3D#0000ff =
size=3D2>The=20
DHCPv6 server can&nbsp;use the client's interface-identifier to =
addresses (by=20
extracting it from the appropriate place&nbsp;- either from the source =
address=20
or from the relay-agent's peer-address field if relayed). Or, the DHCPv6 =
server=20
can other techniques to generate addresses, such as random numbers, =
perhaps=20
using the RFC 3041 (or better yet, <A=20
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-ipv6-privacy-addrs=
-v2-01.txt">http://www.ietf.org/internet-drafts/draft-ietf-ipv6-privacy-a=
ddrs-v2-01.txt</A>).</FONT></SPAN></DIV>
<DIV><SPAN class=3D032172214-03122004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D032172214-03122004><FONT face=3DArial color=3D#0000ff =
size=3D2>-=20
Bernie</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
  dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] <B>On Behalf Of =

  </B>Achint Setia<BR><B>Sent:</B> Friday, December 03, 2004 12:41=20
  AM<BR><B>To:</B> dhcwg@ietf.org<BR><B>Subject:</B> [dhcwg] IPv6 =
Interface=20
  Identifiers.<BR><BR></FONT></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I had this general doubt =
while=20
  reading the DHCPv6 RFC (3315).</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">When the addresses are =
assigned by=20
  a DHCPv6 server, the interface identifier will correspond to the one=20
  chosen</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">by the server from =
within its=20
  scope. This can be any number depending on how the scopes are defined =
at the=20
  server.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Doesn&#8217;t this =
contradict RFC 2373,=20
  which clearly states that the 64 bit Interface Identifier should be in =
EUI -64=20
  format ?</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Or does that mean the =
server needs=20
  to CONVERT the interface id, it has chosen, into the EUI-64 format =
before=20
  assigning it</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">to the =
client?</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial">Thanks,</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Achint =
Setia.</SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"></SPAN></FONT>&nbsp;</P>
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: =
12pt"></SPAN></FONT>&nbsp;</P></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_002F_01C4D91A.379A1B40--



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

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

--===============1207360294==--




From dhcwg-bounces@ietf.org  Fri Dec  3 13:30:26 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16150
	for <dhcwg-web-archive@ietf.org>; Fri, 3 Dec 2004 13:30:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaII5-0006zr-VN
	for dhcwg-web-archive@ietf.org; Fri, 03 Dec 2004 13:36:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaEvP-0001IB-KW; Fri, 03 Dec 2004 10:00:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaERH-0003FQ-SN
	for dhcwg@megatron.ietf.org; Fri, 03 Dec 2004 09:29:39 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09019
	for <dhcwg@ietf.org>; Fri, 3 Dec 2004 09:29:38 -0500 (EST)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaEX1-0004jm-Gs
	for dhcwg@ietf.org; Fri, 03 Dec 2004 09:35:36 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-2.cisco.com with ESMTP; 03 Dec 2004 09:29:08 -0500
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iB3ET4bV005262; 
	Fri, 3 Dec 2004 09:29:05 -0500 (EST)
Received: from rdroms-w2k01.cisco.com (sjc-vpn2-567.cisco.com [10.21.114.55])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANL22633;
	Fri, 3 Dec 2004 09:29:02 -0500 (EST)
Message-Id: <4.3.2.7.2.20041203091913.0244fe90@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 03 Dec 2004 09:28:58 -0500
To: "Achint Setia" <asetia@microsoft.com>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Relay Agent Options.
In-Reply-To: <91AC940D24F18041A3A68895289CE1EE012A5B0F@APS-MSG-02.southp
	acific.corp.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb

Achint - I assume you're asking about DHCPv6?

Comments in line...

At 01:20 PM 12/3/2004 +0800, Achint Setia wrote:
>Hi,
>
>I have a couple of doubts regarding the Relay Agent Options:-
>
>1. What is the motive behind allowing the relay agent to add options
>    while forwarding the client packet to the server? Are they to be
>    used by the server in configuration selection for the client?

Relay agent options may be used by the server in determining the
configuration of the client or by the relay agent to aid in forwarding the
response from the server to the client (see RFC 3046).

>2. If yes, does that mean that when the server sends back the Relay
>    Reply, the ONLY TWO options that can be included are the Relay
>    Message and the interface id.  I am asking this because I am not
>    sure as to how the relay agent will
>    handle options other than these two in the Relay Reply?

The Relay-reply message contains the message to be forwarded to the client,
and any other options that the server is sending to the relay agent.  See
section 22.10 of RFC 3315 for more detail on the contents of the Relay-reply
message, and sections A and B of RFC 3315 for a table of which options can
appear in which messages.

>Hope someone can clarify them.
>
>Thanks,
>Achint Setia.

- Ralph Droms


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


From dhcwg-bounces@ietf.org  Fri Dec  3 13:32:25 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16465
	for <dhcwg-web-archive@ietf.org>; Fri, 3 Dec 2004 13:32:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaIK0-00076V-OB
	for dhcwg-web-archive@ietf.org; Fri, 03 Dec 2004 13:38:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaEvr-0001YY-Gh; Fri, 03 Dec 2004 10:01:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaEXp-00044Q-2q
	for dhcwg@megatron.ietf.org; Fri, 03 Dec 2004 09:36:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09585
	for <dhcwg@ietf.org>; Fri, 3 Dec 2004 09:36:23 -0500 (EST)
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.33)
	id 1CaEdY-0004un-N1
	for dhcwg@ietf.org; Fri, 03 Dec 2004 09:42:22 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-3.cisco.com with ESMTP; 03 Dec 2004 07:43:33 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iB3EZmIT000463;
	Fri, 3 Dec 2004 06:35:48 -0800 (PST)
Received: from rdroms-w2k01.cisco.com (sjc-vpn2-567.cisco.com [10.21.114.55])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANL23209;
	Fri, 3 Dec 2004 09:35:46 -0500 (EST)
Message-Id: <4.3.2.7.2.20041203092929.02451c18@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 03 Dec 2004 09:33:22 -0500
To: "Achint Setia" <asetia@microsoft.com>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] DHCPv4 equivalent for DHCPv6 Options ?
In-Reply-To: <91AC940D24F18041A3A68895289CE1EE012A5B22@APS-MSG-02.southp
	acific.corp.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5

Achint - comments in line...

At 01:28 PM 12/3/2004 +0800, Achint Setia wrote:

>Hi,
>
>Is there any plan to have an equivalent RFC for DHCPv6 as RFC2132 defining 
>various DHCPv4 options?

No.  The options defined with the original specification of DHCPv6 are in
RFC 3315 rather than a separate RFC.  New options will be specified in
separate RFCs.  We wrote a separate RFC for DHCPv4 options because there
were many more options defined at the time RFCs 2131 and RFC 2132 were
published.

>Are the DHCPv4 defined options to be supported in DHCPv6 in exactly the 
>same manner (syntax and behavior)
>as they were in v4.

No.  The dhc WG considered but rejected a plan to carry forward the
definition of all of the DHCPv4 options to DHCPv6.  Instead, we adopted the
strategy of defining new options as requirements for those options are
identified.

>Thanks,
>
>Achint Setia.

- Ralph Droms



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


From dhcwg-bounces@ietf.org  Fri Dec  3 13:34:49 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16850
	for <dhcwg-web-archive@ietf.org>; Fri, 3 Dec 2004 13:34:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaIMM-0007Dh-9p
	for dhcwg-web-archive@ietf.org; Fri, 03 Dec 2004 13:40:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaFHz-0004Rr-Q8; Fri, 03 Dec 2004 10:24:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaEkG-0006uP-5h
	for dhcwg@megatron.ietf.org; Fri, 03 Dec 2004 09:49:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11350
	for <dhcwg@ietf.org>; Fri, 3 Dec 2004 09:49:14 -0500 (EST)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaEq0-0005Cm-20
	for dhcwg@ietf.org; Fri, 03 Dec 2004 09:55:13 -0500
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by rtp-iport-1.cisco.com with ESMTP; 03 Dec 2004 09:57:33 -0500
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iB3EmgqR000652; 
	Fri, 3 Dec 2004 09:48:42 -0500 (EST)
Received: from rdroms-w2k01.cisco.com (sjc-vpn2-567.cisco.com [10.21.114.55])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANL24070;
	Fri, 3 Dec 2004 09:48:40 -0500 (EST)
Message-Id: <4.3.2.7.2.20041203093336.02468ed8@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 03 Dec 2004 09:48:35 -0500
To: "Achint Setia" <asetia@microsoft.com>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] IPv6 Interface Identifiers.
In-Reply-To: <91AC940D24F18041A3A68895289CE1EE012A5B45@APS-MSG-02.southp
	acific.corp.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2

At 01:41 PM 12/3/2004 +0800, Achint Setia wrote:

>I had this general doubt while reading the DHCPv6 RFC (3315).
>
>When the addresses are assigned by a DHCPv6 server, the interface 
>identifier will correspond to the one chosen
>by the server from within its scope. This can be any number depending on 
>how the scopes are defined at the server.
>Doesn t this contradict RFC 2373, which clearly states that the 64 bit 
>Interface Identifier should be in EUI -64 format ?
>Or does that mean the server needs to CONVERT the interface id, it has 
>chosen, into the EUI-64 format before assigning it
>to the client?

At the end of section 11 of RFC 3315, there is a paragraph that refers to
section 2.5.1 of RFC 2373 for guidance in setting the "u" (universal/local)
and "g" (individual/group) bits of the interface identifier for EUI-64
compatibility.

Note that although RFC 3315 refers to RFC 2373, RFC 3513 is the most current
specification of the IPv6 addressing architecture.

>Thanks,
>
>Achint Setia.

- Ralph Droms


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


From dhcwg-bounces@ietf.org  Fri Dec  3 14:51:15 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28783
	for <dhcwg-web-archive@ietf.org>; Fri, 3 Dec 2004 14:51:14 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaJYI-0002OL-6w
	for dhcwg-web-archive@ietf.org; Fri, 03 Dec 2004 14:57:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaJ6r-0000ev-6B; Fri, 03 Dec 2004 14:28:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaIOP-0003YF-2X
	for dhcwg@megatron.ietf.org; Fri, 03 Dec 2004 13:42:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18434
	for <dhcwg@ietf.org>; Fri, 3 Dec 2004 13:42:56 -0500 (EST)
Received: from numenor.qualcomm.com ([129.46.51.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaIUB-0007eV-ME
	for dhcwg@ietf.org; Fri, 03 Dec 2004 13:48:56 -0500
Received: from neophyte.qualcomm.com (neophyte.qualcomm.com [129.46.61.149])
	by numenor.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id
	iB3IgGhP009245
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 3 Dec 2004 10:42:17 -0800 (PST)
Received: from WLAU.qualcomm.com (wlau.qualcomm.com [129.46.74.167])
	by neophyte.qualcomm.com (8.12.10/8.12.5/1.0) with ESMTP id
	iB3IgE9A000944; Fri, 3 Dec 2004 10:42:15 -0800 (PST)
Message-Id: <6.0.0.22.2.20041203095655.04272a50@qcmail1.qualcomm.com>
X-Sender: wlau@qcmail1.qualcomm.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
Date: Fri, 03 Dec 2004 10:42:14 -0800
To: "Achint Setia" <asetia@microsoft.com>, <dhcwg@ietf.org>
From: Wing Cheong Lau <lau@qualcomm.com>
Subject: Re: [dhcwg] Relay Agent Options.
In-Reply-To: <91AC940D24F18041A3A68895289CE1EE012A5B0F@APS-MSG-02.southp
	acific.corp.microsoft.com>
References: <91AC940D24F18041A3A68895289CE1EE012A5B0F@APS-MSG-02.southpacific.corp.microsoft.com>
Mime-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 202a3ece0492a8c7e7c8672d5214398f
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="===============1950551689=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 97c820c82c68af374c4e382a80dc5017

--===============1950551689==
Content-Type: multipart/alternative;
	boundary="=====================_45274060==.ALT"

--=====================_45274060==.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

Dear Achint,

I assume the "Relay Agent Options" in your question refers to the "Relay 
Agent Information Option" proposed in
<http://bgp.potaroo.net/ietf/idref/draft-droms-dhc-v6-relayopt/rfcmarkup?repository=/away/ietf&url=/away/ietf/all-ids/draft-droms-dhc-v6-relayopt-00.txt>draft-droms-dhc-v6-relayopt-00.txt



At 09:20 PM 12/2/2004, Achint Setia wrote:

>Hi,
>
>I have a couple of doubts regarding the Relay Agent Options:-
>
>1. What is the motive behind allowing the relay agent to add options
>while
>    forwarding the client packet to the server? Are they to be used by
>the
>    server in configuration selection for the client?

Yes, the info carried by the Relay Agent Information Options is intended be 
used by the server
as HINTs for assigning configuration parameters to the client based on 
local server policy.
Similar capability exists for DHCPv4 (See RFC3046 and 
<http://bgp.potaroo.net/ietf/idref/draft-droms-dhc-v6-relayopt/rfcmarkup?repository=/away/ietf&url=/away/ietf/all-ids/draft-ietf-dhc-agentopt>draft-ietf-dhc-agentopt-radius-08.txt
for example.).

The main motivation behind 
<http://bgp.potaroo.net/ietf/idref/draft-droms-dhc-v6-relayopt/rfcmarkup?repository=/away/ietf&url=/away/ietf/all-ids/draft-droms-dhc-v6-relayopt-00.txt>draft-droms-dhc-v6-relayopt-00.txt
is to use the proposed option to allow a NAS to relay some RADIUS 
attributes received
from the HAAA server to the DHCPv6 server so as to help the latter's
assignment. Please refer to the above RFC/drafts for existing applications 
of such option
in DHCPv4 environment.


>2. If yes, does that mean that when the server sends back the Relay
>Reply,
>    the ONLY TWO options that can be included are the Relay Message and
>the
>    interface id.



>    I am asking this because I am not sure as to how the relay agent will
>
>    handle options other than these two in the Relay Reply?
As proposed in 
<http://bgp.potaroo.net/ietf/idref/draft-droms-dhc-v6-relayopt/rfcmarkup?repository=/away/ietf&url=/away/ietf/all-ids/draft-droms-dhc-v6-relayopt-00.txt>draft-droms-dhc-v6-relayopt-00.txt, 

a dhcpv6 server supporting such option will echo the Option in its Relay 
reply, which will then
be stripped away by the relay agent before the reply is passed back to the 
client.
In other words, if the proposed option is used, the Relay Reply will 
include this new Relay Agent
Information Option similar to the way how the current dhcpv6 interface id 
option is included.
Lastly, based on feedbacks received from the Mailing list and during 
IETF61, the next revision
of the draft-droms-dhc-v6-relayopt-00.txt will be focusing on the
support of RADIUS attribute relay, instead of general relay info.
Please refer to the thread of discussion in 
http://www.ietf.org/mail-archive/web/dhcwg/current/msg04136.html
for more details.

Hope this helps.

Regards,

Wing

>Hope someone can clarify them.
>
>Thanks,
>Achint Setia.
>
>
>
>_______________________________________________
>dhcwg mailing list
>dhcwg@ietf.org
>https://www1.ietf.org/mailman/listinfo/dhcwg

--=====================_45274060==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
Dear Achint,<br><br>
I assume the &quot;Relay Agent Options&quot; in your question refers to
the &quot;Relay Agent Information Option&quot; proposed in <br>
<pre><a href="http://bgp.potaroo.net/ietf/idref/draft-droms-dhc-v6-relayopt/rfcmarkup?repository=/away/ietf&amp;url=/away/ietf/all-ids/draft-droms-dhc-v6-relayopt-00.txt">draft-droms-dhc-v6-relayopt-00.txt



</a></pre>At 09:20 PM 12/2/2004, Achint Setia wrote:<br><br>
<blockquote type=cite class=cite cite>Hi,<br><br>
I have a couple of doubts regarding the Relay Agent Options:-<br><br>
1. What is the motive behind allowing the relay agent to add 
options<br>
while&nbsp;&nbsp;&nbsp;&nbsp; <br>
&nbsp;&nbsp; forwarding the client packet to the server? Are they to be
used by<br>
the&nbsp;&nbsp;&nbsp;&nbsp; <br>
&nbsp;&nbsp; server in configuration selection for the client?<br>
</blockquote><br>
Yes, the info carried by the Relay Agent Information Options is intended
be used by the server<br>
as HINTs for assigning configuration parameters to the client based on
local server policy.<br>
Similar capability exists for DHCPv4 (See RFC3046 and
<a href="http://bgp.potaroo.net/ietf/idref/draft-droms-dhc-v6-relayopt/rfcmarkup?repository=/away/ietf&amp;url=/away/ietf/all-ids/draft-ietf-dhc-agentopt"><pre>draft-ietf-dhc-agentopt</a>-radius-08.txt
</pre>for example.).&nbsp;&nbsp; <br><br>
<pre>The main motivation behind
<a href="http://bgp.potaroo.net/ietf/idref/draft-droms-dhc-v6-relayopt/rfcmarkup?repository=/away/ietf&amp;url=/away/ietf/all-ids/draft-droms-dhc-v6-relayopt-00.txt">draft-droms-dhc-v6-relayopt-00.txt
</a></pre>is to use the proposed option to allow a NAS to relay some
RADIUS attributes received <br>
from the HAAA server to the DHCPv6 server so as to help the 
latter's<br>
assignment. Please refer to the above RFC/drafts for existing
applications of such option<br>
in DHCPv4 environment.<br><br>
<br>
<blockquote type=cite class=cite cite>2. If yes, does that mean that when
the server sends back the Relay<br>
Reply,<br>
&nbsp;&nbsp; the ONLY TWO options that can be included are the Relay
Message and<br>
the&nbsp;&nbsp;&nbsp; <br>
&nbsp;&nbsp; interface id.<br>
</blockquote><br><br>
<br>
<blockquote type=cite class=cite cite>&nbsp;&nbsp; I am asking this
because I am not sure as to how the relay agent will<br><br>
&nbsp;&nbsp; handle options other than these two in the Relay 
Reply?<br>
</blockquote>As proposed in
<a href="http://bgp.potaroo.net/ietf/idref/draft-droms-dhc-v6-relayopt/rfcmarkup?repository=/away/ietf&amp;url=/away/ietf/all-ids/draft-droms-dhc-v6-relayopt-00.txt"><pre>draft-droms-dhc-v6-relayopt-00.txt</a>, 
</pre>a dhcpv6 server supporting such option will echo the Option in its
Relay reply, which will then<br>
be stripped away by the relay agent before the reply is passed back to
the client.<br>
In other words, if the proposed option is used, the Relay Reply will
include this new Relay Agent<br>
Information Option similar to the way how the current dhcpv6 interface id
option is included.<br>
Lastly, based on feedbacks received from the Mailing list and during
IETF61, the next revision<br>
of the <pre>draft-droms-dhc-v6-relayopt-00.txt will be focusing on the
</pre>support of RADIUS attribute relay, instead of general relay info.
<br>
Please refer to the thread of discussion in
<a href="http://www.ietf.org/mail-archive/web/dhcwg/current/msg04136.html" eudora="autourl">http://www.ietf.org/mail-archive/web/dhcwg/current/msg04136.html<br>
</a>for more details.&nbsp;&nbsp; <br><br>
Hope this helps. <br><br>
Regards,<br><br>
Wing<br><br>
<blockquote type=cite class=cite cite>Hope someone can clarify
them.<br><br>
Thanks,<br>
Achint Setia.<br>
&nbsp;<br>
&nbsp;<br><br>
_______________________________________________<br>
dhcwg mailing list<br>
dhcwg@ietf.org<br>
<a href="https://www1.ietf.org/mailman/listinfo/dhcwg" eudora="autourl">https://www1.ietf.org/mailman/listinfo/dhcwg</a>
</blockquote></body>
</html>

--=====================_45274060==.ALT--



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

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

--===============1950551689==--




From dhcwg-bounces@ietf.org  Fri Dec  3 15:07:35 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01086
	for <dhcwg-web-archive@ietf.org>; Fri, 3 Dec 2004 15:07:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CaJo6-00032q-Gi
	for dhcwg-web-archive@ietf.org; Fri, 03 Dec 2004 15:13:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CaJRz-000170-Lq; Fri, 03 Dec 2004 14:50:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaJ3u-00083X-Fx
	for dhcwg@megatron.ietf.org; Fri, 03 Dec 2004 14:25:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24718
	for <dhcwg@ietf.org>; Fri, 3 Dec 2004 14:25:49 -0500 (EST)
Received: from mtagate4.uk.ibm.com ([195.212.29.137])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaJ9g-0001AL-Kl
	for dhcwg@ietf.org; Fri, 03 Dec 2004 14:31:50 -0500
Received: from d06nrmr1307.portsmouth.uk.ibm.com
	(d06nrmr1307.portsmouth.uk.ibm.com [9.149.38.129])
	by mtagate4.uk.ibm.com (8.12.10/8.12.10) with ESMTP id iB3JPHSZ331830
	for <dhcwg@ietf.org>; Fri, 3 Dec 2004 19:25:17 GMT
Received: from d06ml291.portsmouth.uk.ibm.com (d06av02.portsmouth.uk.ibm.com
	[9.149.37.228])
	by d06nrmr1307.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id
	iB3JPOxg281890 for <dhcwg@ietf.org>; Fri, 3 Dec 2004 19:25:25 GMT
From: Arnaldo Gouveia <ARNALDO@pt.ibm.com>
To: dhcwg@ietf.org
Message-ID: <OFF164E8E5.36F7D990-ON00256F5F.006AB26A-00256F5F.006AB270@pt.ibm.com>
Date: Fri, 3 Dec 2004 19:25:24 +0000
X-MIMETrack: Serialize by Router on D06ML291/06/M/IBM(Release 6.51HF338 | June
	21, 2004) at 03/12/2004 19:25:26
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: [dhcwg] Arnaldo Gouveia/Portugal/IBM is out of the office.
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2





I will be out of the office starting  03-12-2004 and will not return until
09-12-2004.

I will be out of office till Dec 9


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


From dhcwg-bounces@ietf.org  Sat Dec  4 09:31:06 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02341
	for <dhcwg-web-archive@ietf.org>; Sat, 4 Dec 2004 09:31:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cab2A-0001rc-Mw
	for dhcwg-web-archive@ietf.org; Sat, 04 Dec 2004 09:37:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Caauj-0000dw-3F; Sat, 04 Dec 2004 09:29:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CV9Aa-0006gb-D2
	for dhcwg@megatron.ietf.org; Fri, 19 Nov 2004 08:51:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02128
	for <dhcwg@ietf.org>; Fri, 19 Nov 2004 08:51:20 -0500 (EST)
Received: from mx2.buaa.edu.cn ([219.239.227.26])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CV9DM-0004ov-JI
	for dhcwg@ietf.org; Fri, 19 Nov 2004 08:54:18 -0500
Received: from mx1.buaa.edu.cn (unknown [192.168.128.6])
	by mx2.buaa.edu.cn (Postfix) with ESMTP id 0456A37F72
	for <dhcwg@ietf.org>; Fri, 19 Nov 2004 21:50:49 +0800 (CST)
Received: from [211.71.8.37] by 10.0.0.131 with StormMail ESMTP id
	9652.262235339; Fri, 19 Nov 2004 22:02:44 +0800 (CST)
Message-ID: <419DFA3D.6080303@cse.buaa.edu.cn>
Date: Fri, 19 Nov 2004 21:50:53 +0800
From: Li Qin <liqin@cse.buaa.edu.cn>
User-Agent: Mozilla Thunderbird 0.8 (X11/20040926)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dhcwg@ietf.org
Subject: Re: RE: [dhcwg] Mobile Ipv6 bootstrap issue
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sat, 04 Dec 2004 09:29:31 -0500
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Content-Transfer-Encoding: 7bit

>I believe that DHCP is a good solution whenever DHCP is available on the >client.
>That's why DHCP is here. If DHCP is not available, we can't use it of course.

I think current operators would not extend DHCP to support other service.
So they prefer not modify DHCP, but use a specifical protocol.


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


From dhcwg-bounces@ietf.org  Sat Dec  4 09:35:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02551
	for <dhcwg-web-archive@ietf.org>; Sat, 4 Dec 2004 09:35:16 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cab6F-0001vu-Jo
	for dhcwg-web-archive@ietf.org; Sat, 04 Dec 2004 09:41:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Caauj-0000e1-CP; Sat, 04 Dec 2004 09:29:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CWxbO-0005Wa-C5
	for dhcwg@megatron.ietf.org; Wed, 24 Nov 2004 08:54:34 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24494
	for <dhcwg@ietf.org>; Wed, 24 Nov 2004 08:54:32 -0500 (EST)
Received: from web8404.mail.in.yahoo.com ([202.43.219.152])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CWxfF-0004zp-1K
	for dhcwg@ietf.org; Wed, 24 Nov 2004 08:58:35 -0500
Received: (qmail 21478 invoked by uid 60001); 24 Nov 2004 13:53:55 -0000
Message-ID: <20041124135355.21476.qmail@web8404.mail.in.yahoo.com>
Received: from [203.197.252.77] by web8404.mail.in.yahoo.com via HTTP;
	Wed, 24 Nov 2004 13:53:55 GMT
Date: Wed, 24 Nov 2004 13:53:55 +0000 (GMT)
From: naveen kumar <naveen_mamindla@yahoo.co.in>
To: dhcwg@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
X-Mailman-Approved-At: Sat, 04 Dec 2004 09:29:31 -0500
Subject: [dhcwg] DHCP client
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="===============0619916201=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4

--===============0619916201==
Content-Type: multipart/alternative; boundary="0-1186301129-1101304435=:20751"

--0-1186301129-1101304435=:20751
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Sir,
 
  I am running a DHCP client from the console of my system and I observed that the ipaddress of LAN port(eth0) got changed.
 
 I want to change ipaddress of WAN port (eth1).
 
Can anybody tell me the solution for this.
 
 
                                   Thanks,
regards
Naveen
 
 
 
 
 
 

Yahoo! India Matrimony: Find your life partneronline.
--0-1186301129-1101304435=:20751
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<DIV>Sir,</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp; I am running a DHCP client from the console of my system and I observed that the ipaddress of LAN port(eth0) got changed.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;I want to change ipaddress of WAN port (eth1).</DIV>
<DIV>&nbsp;</DIV>
<DIV>Can anybody tell me the solution for this.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&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; Thanks,</DIV>
<DIV>regards</DIV>
<DIV>Naveen</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV><p><font face=arial size=-1>
<a href="http://in.rd.yahoo.com/specials/mailtg/*http://yahoo.shaadi.com/india-matrimony/" target="_blank">
<b>Yahoo! India Matrimony</a>:</b> Find your life partner
<a href="http://in.rd.yahoo.com/specials/mailtg2/*http://yahoo.shaadi.com/india-matrimony/" target="_blank">online</a>.</font>
--0-1186301129-1101304435=:20751--


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

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

--===============0619916201==--



From dhcwg-bounces@ietf.org  Sat Dec  4 09:35:41 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02593
	for <dhcwg-web-archive@ietf.org>; Sat, 4 Dec 2004 09:35:41 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cab6c-0001wl-E1
	for dhcwg-web-archive@ietf.org; Sat, 04 Dec 2004 09:41:53 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Caauj-0000e6-MM; Sat, 04 Dec 2004 09:29:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CXk0E-0003Hk-BK
	for dhcwg@megatron.ietf.org; Fri, 26 Nov 2004 12:35:26 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01834
	for <dhcwg@ietf.org>; Fri, 26 Nov 2004 12:35:23 -0500 (EST)
Received: from mail.mayberryinv.com ([208.138.31.34]
	helo=apollo.mayberryinv.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CXk4X-0007Fm-Nu
	for dhcwg@ietf.org; Fri, 26 Nov 2004 12:39:54 -0500
Received: by apollo.mayberryinv.net with Internet Mail Service (5.5.2653.19)
	id <S5W3NJVL>; Fri, 26 Nov 2004 12:34:44 -0500
Message-ID: <A12445FA41F31E4583F58CDD4AF60E413582B6@apollo.mayberryinv.net>
From: Peter Fraser <peter.fraser@mayberryinv.com>
To: "'dhcwg@ietf.org'" <dhcwg@ietf.org>
Date: Fri, 26 Nov 2004 12:34:43 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
X-Mailman-Approved-At: Sat, 04 Dec 2004 09:29:31 -0500
Subject: [dhcwg] DHCP and mac Addresses
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="===============0723384217=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: f49c97ce49302a02285a2d36a99eef8c

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--===============0723384217==
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4D3DE.375F2800"

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C4D3DE.375F2800
Content-Type: text/plain

Hi 

I was wondering if I could get some help please. I'm thinking of moving from
windows 2000 DHCP servers to ISC Dhcp. Is it possible to have ISC Dhcp only
assign DHCP addresses to computers that have  particular mac addresses ? If
so, could you please tell me where I can find a HOWTO on this subject.

 

Thank You.

 

Peter Fraser 
Network Administrator 
Mayberry Investments Limited 
1 1/2 Oxford Road 
Kingston 5 

 


------_=_NextPart_001_01C4D3DE.375F2800
Content-Type: text/html

<html>

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">


<meta name=Generator content="Microsoft Word 10 (filtered)">

<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
p
	{margin-right:0in;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Hi </span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>I was wondering if I could get some help please. I'm
thinking of moving from windows 2000 DHCP servers to ISC Dhcp. Is it possible
to have ISC Dhcp only assign DHCP addresses to computers that have&nbsp; particular mac
addresses ? If so, could you please tell me where I can find a HOWTO on this
subject.</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Thank You.</span></font></p>

<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p><font size=2 face=Arial><span lang=EN-GB style='font-size:10.0pt;font-family:
 Arial'>Peter Fraser</span></font> <br>
<font size=2 face=Arial><span lang=EN-GB style='font-size:10.0pt;font-family:
Arial'>Network Administrator</span></font> <br>
<font size=2 face=Arial><span lang=EN-GB style='font-size:10.0pt;font-family:
Arial'>Mayberry Investments Limited</span></font> <br>
  <font size=2 face=Arial><span lang=EN-GB style='font-size:10.0pt;font-family:
  Arial'>1 1/2 Oxford Road</span></font> <br>
  <font size=2 face=Arial><span lang=EN-GB style='font-size:10.0pt;font-family:
  Arial'>Kingston</span></font><font size=2 face=Arial><span lang=EN-GB
style='font-size:10.0pt;font-family:Arial'> 5</span></font><span lang=EN-GB> </span></p>

<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>&nbsp;</span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C4D3DE.375F2800--



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

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

--===============0723384217==--




From dhcwg-bounces@ietf.org  Sat Dec  4 09:36:31 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02669
	for <dhcwg-web-archive@ietf.org>; Sat, 4 Dec 2004 09:36:30 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cab7S-0001yu-GE
	for dhcwg-web-archive@ietf.org; Sat, 04 Dec 2004 09:42:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Caauk-0000eB-02; Sat, 04 Dec 2004 09:29:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CaBK9-0001sJ-IR
	for dhcwg@megatron.ietf.org; Fri, 03 Dec 2004 06:10:05 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22968
	for <dhcwg@ietf.org>; Fri, 3 Dec 2004 06:10:02 -0500 (EST)
Received: from dmzraw5.extranet.tce.com ([157.254.234.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CaBPr-0000QC-AQ
	for dhcwg@ietf.org; Fri, 03 Dec 2004 06:16:00 -0500
Received: from smtprelay.indy.tce.com (unknown [157.254.96.114])
	by dmzraw5.extranet.tce.com (Postfix) with ESMTP id 51F001AD51F
	for <dhcwg@ietf.org>; Fri,  3 Dec 2004 11:09:27 +0000 (GMT)
Received: from boulsmailbh01.eu.thmulti.com (localhost [127.0.0.1])
	by smtprelay.indy.tce.com (8.9.3/8.9.1) with ESMTP id LAA20711
	for <dhcwg@ietf.org>; Fri, 3 Dec 2004 11:09:26 GMT
Received: from edgmsmail01.eu.thmulti.com ([141.11.248.9]) by
	boulsmailbh01.eu.thmulti.com with Microsoft SMTPSVC(5.0.2195.6713); 
	Fri, 3 Dec 2004 12:09:24 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 3 Dec 2004 12:09:16 +0100
Message-ID: <93CC9B09785D2943977A99C0230E30D8047820@edgmsmail01.eu.thmulti.com>
Thread-Topic: options 66, 67
Thread-Index: AcTZKIb7BskYjKEBSO6zTwDAnvtl5Q==
From: "Ooms Dirk" <Dirk.Ooms@thomson.net>
To: <dhcwg@ietf.org>
X-OriginalArrivalTime: 03 Dec 2004 11:09:25.0102 (UTC)
	FILETIME=[8C6BF0E0:01C4D928]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Sat, 04 Dec 2004 09:29:30 -0500
Cc: Ooms Dirk <Dirk.Ooms@thomson.net>
Subject: [dhcwg] options 66, 67
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: quoted-printable

Hello,

In my understanding option 66 and 67 are set by the server in case of =
option overloading. i was wondering how a server should react on a =
client that explicitly requests option 66 and 67 although the option =
space is not fully used. Should the  server copy the content of "sname" =
and "filename" into options 66 and 67, should it not return the options, =
....

dirk



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


From dhcwg-bounces@ietf.org  Sat Dec  4 10:34:27 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07262
	for <dhcwg-web-archive@ietf.org>; Sat, 4 Dec 2004 10:34:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cac1X-000304-Vr
	for dhcwg-web-archive@ietf.org; Sat, 04 Dec 2004 10:40:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cabte-0006jH-Lv; Sat, 04 Dec 2004 10:32:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cabt7-0006TW-Sn
	for dhcwg@megatron.ietf.org; Sat, 04 Dec 2004 10:31:57 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07088
	for <dhcwg@ietf.org>; Sat, 4 Dec 2004 10:31:55 -0500 (EST)
From: Patrick.Guelat@imp.ch
Received: from mx2.imp.ch ([157.161.9.17])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cabz5-0002wr-Hv
	for dhcwg@ietf.org; Sat, 04 Dec 2004 10:38:08 -0500
Received: from mx3.imp.ch (mx3.imp.ch [157.161.9.18])
	by mx2.imp.ch (8.13.1/8.13.1) with ESMTP id iB4FVi8C072832
	for <dhcwg@ietf.org>; Sat, 4 Dec 2004 16:31:46 +0100 (CET)
	(envelope-from Patrick.Guelat@imp.ch)
Received: from mx3.imp.ch (localhost [127.0.0.1])
	by mx3.imp.ch (8.12.11/8.12.11/Submit) with ESMTP id iB4FVcY8064985
	for <dhcwg@ietf.org>; Sat, 4 Dec 2004 16:31:39 +0100 (CET)
	(envelope-from Patrick.Guelat@imp.ch)
Received: (from clamav@localhost)
	by mx3.imp.ch (8.12.11/8.12.11/Submit) id iB4FVcLT064982
	for <dhcwg@ietf.org>; Sat, 4 Dec 2004 16:31:38 +0100 (CET)
	(envelope-from Patrick.Guelat@imp.ch)
Received: from nbs.imp.ch (nbs.imp.ch [157.161.4.7])
	by ns1.imp.ch (MIMEDefang) with ESMTP id iB4FVWiD098990;
	Sat, 04 Dec 2004 16:31:38 +0100 (CET)
Received: from murphy.imp.ch (murphy.imp.ch [157.161.4.77])
	by nbs.imp.ch (8.12.10/8.12.3) with ESMTP id iB4FVW2s18251818;
	Sat, 4 Dec 2004 16:31:32 +0100 (MEZ)
Date: Sat, 4 Dec 2004 16:31:32 +0100 (CET)
X-X-Sender: patg@murphy.imp.ch
To: Ooms Dirk <Dirk.Ooms@thomson.net>
Subject: Re: [dhcwg] options 66, 67
In-Reply-To: <93CC9B09785D2943977A99C0230E30D8047820@edgmsmail01.eu.thmulti.com>
Message-ID: <20041204162631.P126@murphy.imp.ch>
References: <93CC9B09785D2943977A99C0230E30D8047820@edgmsmail01.eu.thmulti.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Spam-Resent: Yes
X-Spam-Checksum: aa2518b13b912a8ab39435af3d5d50e9
X-Virus-Message-Status: No
X-Virus-Status: No, scantime="0.0011 seconds"
X-Spam-Status: No,
	hits=-4.893 required=5 scantime="4.9333 seconds" tests=BAYES_00,
	NO_REAL_NAME
X-Spam-Report: ---- Start der SpamAssassin Auswertung
	0.0 NO_REAL_NAME           From: does not include a real name
	-4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000] ---- Ende der SpamAssassin Auswertung
X-Scanned-By: MIMEDefang 2.49 on 157.161.9.64
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c

On Fri, 3 Dec 2004, Ooms Dirk wrote:

> In my understanding option 66 and 67 are set by the server in case of option overloading. i was wondering how a server should react on a client that explicitly requests option 66 and 67 although the option space is not fully used. Should the  server copy the content of "sname" and "filename" into options 66 and 67, should it not return the options, ....

IMHO, the server should honour the request and copy them to 66/67,
that's the way we did it in our implementation. We encountered some
clients (docsis cablemodems in our case) which whouldn't boot when
those options where not present.

Patrick

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


From dhcwg-bounces@ietf.org  Mon Dec  6 14:19:21 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14178
	for <dhcwg-web-archive@ietf.org>; Mon, 6 Dec 2004 14:19:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbOUi-0004kJ-Jf
	for dhcwg-web-archive@ietf.org; Mon, 06 Dec 2004 14:26:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbOJe-0005E1-IF; Mon, 06 Dec 2004 14:14:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbOCr-0004Ai-Uo; Mon, 06 Dec 2004 14:07:34 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12967;
	Mon, 6 Dec 2004 14:07:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbOJH-0004OM-QG; Mon, 06 Dec 2004 14:14:11 -0500
Received: from apache by megatron.ietf.org with local (Exim 4.32)
	id 1CbOBf-0003xJ-5z; Mon, 06 Dec 2004 14:06:19 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1CbOBf-0003xJ-5z@megatron.ietf.org>
Date: Mon, 06 Dec 2004 14:06:19 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: dhc mailing list <dhcwg@ietf.org>, dhc chair <rdroms@cisco.com>,
        Internet Architecture Board <iab@iab.org>,
        RFC Editor <rfc-editor@rfc-editor.org>
Subject: [dhcwg] Protocol Action: 'Simple Network Time Protocol
 Configuration Option for DHCPv6' to Proposed Standard 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb

The IESG has approved the following document:

- 'Simple Network Time Protocol Configuration Option for DHCPv6 '
   <draft-ietf-dhc-dhcpv6-opt-sntp-01.txt> as a Proposed Standard

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

The IESG contact persons are Margaret Wasserman and Thomas Narten.

Technical Summary
 
   This document describes a new DHCPv6 option for passing a list of
   SNTP server addresses to a client. 

Working Group Summary
 
   This document was developed by the DHC WG.  The document was 
   updated to address AD Review comments, including the removal
   of the timezone option (which may be published separately)
   and changing the document to indicate that it configures
   SNTP clients, not full NTP clients.
 
Protocol Quality
 
   This document was reviewed for the IESG by Margaret Wasserman.

RFC Editor note:

In Section 4, paragraph one, change the last sentence from:

   The server MAY list the SNTP servers in the order of preference.

to

   The server MAY list the SNTP servers in decreasing order of preference.


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


From dhcwg-bounces@ietf.org  Mon Dec  6 16:31:43 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26819
	for <dhcwg-web-archive@ietf.org>; Mon, 6 Dec 2004 16:31:43 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbQYp-00089i-Rh
	for dhcwg-web-archive@ietf.org; Mon, 06 Dec 2004 16:38:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbQNN-00026H-E5; Mon, 06 Dec 2004 16:26:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbQMj-0001oK-9z
	for dhcwg@megatron.ietf.org; Mon, 06 Dec 2004 16:25:53 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26495
	for <dhcwg@ietf.org>; Mon, 6 Dec 2004 16:25:51 -0500 (EST)
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.33)
	id 1CbQT7-00082O-Kp
	for dhcwg@ietf.org; Mon, 06 Dec 2004 16:32:32 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 06 Dec 2004 14:33:35 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iB6LPBD9000105
	for <dhcwg@ietf.org>; Mon, 6 Dec 2004 13:25:11 -0800 (PST)
Received: from rdroms-w2k01.cisco.com ([161.44.65.122])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANM69365;
	Mon, 6 Dec 2004 16:25:11 -0500 (EST)
Message-Id: <4.3.2.7.2.20041206162335.02215e80@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 06 Dec 2004 16:25:08 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e472ca43d56132790a46d9eefd95f0a5
Subject: [dhcwg] *DRAFT* minutes from dhc WG meeting in DC (2nd try)
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0cff8c3ec906d056784362c06f5f88c1


Here are the draft minutes of the dhc WG meeting in DC.  Please review and
respond with comments by 1700 EST, Mon 2004-12-06.

BTW, who acted as scribe for the jabber log, so I can credit your efforts
in the minutes?

- Ralph Droms

-----

Administrivia                                      Ralph Droms

Droms asked about interest in DHCP server MIB,
draft-ietf-dhc-server-mib.  The specification has been reviewed by the
IESG and is close to being done.  However, one author is not
interested in continuing to work on the specification and the other
wants to confirm that there is sufficient interest before committing
to more work on the document.  Ted Lemon expressed interest in seeing
a server MIB (although not necessarily this one).  Droms will work
with Glen Waters (document co-author) to complete the specification.


Reclassifying DHCPv4 Options                       Bernie Volz

draft-ietf-dhc-reclassify-options is about to be published as an RFC.
Volz described the process for broadcasting notification of the
process specified in the document, and asked for assistance in
identifying all vendors whose use of option codes will be affected by
this specification.


DNS zone suffix option for DHCPv6                  Renxiang Yan
draft-yan-dhc-dhcpv6-opt-dnszone

Yan gave a presentation about draft-yan-dhc-dhcpv6-opt-dnszone.  The
key idea is to send the DNS domain from which a host should form its
FQDN to the host.  Ted Lemon noted that the mechanism in this
specification supposes that the host will then use DDNS to update its
DNS information.  This use of DDNS will require management of
authorization information for individual hosts, which won't scale.
The RA-based mechanism in draft-jeong-ipv6-ra-dns-autoconf has similar
issues of scale.  Further discussion will take place on the WG mailing
list before coming to a decision about taking this draft on as a WG
work item.


Vendor-Specific Information Suboption              Mark Stapp
draft-stapp-dhc-vendor-suboption

There was consensus in the room to take this draft to WG last call.
Droms will confirm consensus on the WG mailing list.


DHCP Authentication via EAP                        Mark Stapp

Stapp presented summary of idea to use EAP for DHCP authentication (no
document, yet).  The premise of this work is that requiring the use of
another set of keys around just to do DHCP is a non-starter and DNSSEC
is not ready, so Stapp suggests using credentials already provisioned
for 802.1x for DHCP authentication.  There was some discussion about
where in the authentication system (AAA server?) session keys might be
generated.  Stapp will write a draft based on his ideas for WG review.


Information Refresh Time Option for DHCPv6         Stig Venaas
draft-ietf-dhc-lifetime

Venaas gave an update about the draft, which has been previously
discussed by the WG.  The title of the specification has been changed
to "Information Refresh Time Option for DHCPv6" as the option controls
when a client contacts the DHCP server, but does not cause previously
obtained information to expire in any way.  Some minor issues were
raised about max and min values for lifetime which will be discussed
on WG mailing list.  Pending that discussion, there was consensus in
room to go to WG last call.  Consensus to be confirmed on WG mailing
list.


Multicast Reconfig. Protocol for Stateless DHCPv6  Daniel Park
draft-vijay-dhc-dhcpv6-mcast-reconf

Park gave a summary of the draft.  Droms asked why the protocol uses
Relay-reply message to notify router (through relay) to toggle 'M'/'O'
bits; isn't CLI sufficient?  Greg Daley suggested SNMP might be
appropriate to cause router to toggle 'M'/'O' bits.  Some additional
discussion about whether this mechanism is needed if "Information
Refresh Time Option for DHCPv6" is accepted for standards track.  Volz
pointed out that "multicast reconfig" is useful for unplanned
renumbering.  Park was requested to provide more detail; further
discussion will take place on the WG mailing list before coming to a
decision about taking this draft on as a WG work item.


Anycast Address Assignment using DHCPv6            Syam Madanapalli
draft-madanapalli-dhcpv6-anycast

Madanapalli presented summary of the draft.  Ted Lemon pointed out
that the slides were somewhat different from the text in
"draft-madanapalli-dhcpv6-anycast", and that the second part of the
specification (in which the services are classified) begins to look a
lot like SLP.  Droms suggested the draft might be spit into two
pieces: one for assignment and one for service classification.  There
was consensus in the room to accept the draft as a WG work item; the
consensus will be confirmed on WG mailing list.


Source Address Selection Policy option for DHCPv6  T. Fujisaki
draft-hirotaka-dhc-source-address-selection-opt

This draft provides a protocol for distribution of address selection
policy, where those policies are described in RFC 3484.  The draft is
related to other drafts about distribution of policy currently before
the ipv6 and multi6 WGs.  John Schnizlein asked if this draft is
really solving a routing problem.  Ted Lemon asked if this is for
reasonably stable and static multi-homed networks' authors agreed that
this is for source address selection policy, not routing information.
Further discussion will take place on the WG mailing list before
coming to a decision about taking this draft on as a WG work item.


DHCPv6 Relay Agent Information Option              Wing Cheong Lau
draft-droms-dhc-v6-relayopt

The consensus in the room was to accept the draft as a WG work item;
consensus will be confirmed on WG mailing list.


Clarifications on DHCPv6 Authentication            T. Jinmei
draft-ietf-dhc-dhcpv6-clarify-auth

Jinmei-san presented a list of changes to the draft in the most recent
revision and a couple of outstanding issues:
* draft recommends treating multiple exchanges as a single "session",
   which requires additional state in the server
* should this draft be published independently or rolled into a
   revision of RFC 3315?
Jinmei-san will initiate discussion of a couple of outstanding issues
and then the draft will be ready for WG last call.


DHCP Relay Agent Opt for MIPv6 bootstrapping       Kuntal Chowdhury
draft-chowdhury-dhc-mip6-agentop

J. Bharatia presented a summary of the draft, which provides a
mechanism through which a remote AAA server can pass the address of a
MIP6 home agent to a roaming MIP6 host for initial
configuration/bootstrapping.  Mark Stapp objected to the relay agent
modifying the DHCP message rather than inserting information in the
relay option wrapper.  It was mentioned that a similar draft that
accomplishes the same objective without DHCP is under consideration in
the mip6 WG. The author was requested to revise the draft to avoid
modification of the DHCP message by the relay and the WG will consider
the revised draft.


DHCP-DNS interaction                               Bernie Volz
draft-ietf-dhc-dhcpv6-fqdn
draft-ietf-dhc-fqdn-option
draft-ietf-dhc-ddns-resolution

Volz presented a status report: these drafts along with
draft-ietf-dhc-3315id-for-v4 and draft-ietf-dnsext-dhcid-rr will go to
the IESG as a package.  draft-ietf-dnsext-dhcid-rr is through WG last
call (dnsext).  The consensus in the room was to go to WG last call on
draft-ietf-dhc-fqdn-option; consensus will be confirmed on the WG
mailing list. 


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


From dhcwg-bounces@ietf.org  Mon Dec  6 23:37:32 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28810
	for <dhcwg-web-archive@ietf.org>; Mon, 6 Dec 2004 23:37:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CbXD0-0000GB-8H
	for dhcwg-web-archive@ietf.org; Mon, 06 Dec 2004 23:44:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CbX51-0007Ti-Cc; Mon, 06 Dec 2004 23:36:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CbX1E-0006uD-Tm
	for dhcwg@megatron.ietf.org; Mon, 06 Dec 2004 23:32:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28559
	for <dhcwg@ietf.org>; Mon, 6 Dec 2004 23:32:05 -0500 (EST)
Received: from mailout1.samsung.com ([203.254.224.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbX7i-0000AP-Ql
	for dhcwg@ietf.org; Mon, 06 Dec 2004 23:38:51 -0500
Received: from custom-daemon.mailout1.samsung.com by mailout1.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	id <0I8C00DIB4KMDR@mailout1.samsung.com> for dhcwg@ietf.org; Tue,
	07 Dec 2004 13:31:34 +0900 (KST)
Received: from ep_mmp1 (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 <0I8C006314IGS3@mailout1.samsung.com> for dhcwg@ietf.org;
	Tue, 07 Dec 2004 13:30:16 +0900 (KST)
Received: from SYAM ([107.108.71.89])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004))
	with ESMTPA id <0I8C00GNW4ICJ3@mmp1.samsung.com> for dhcwg@ietf.org;
	Tue, 07 Dec 2004 13:30:16 +0900 (KST)
Date: Tue, 07 Dec 2004 09:57:12 +0530
From: Syam Madanapalli <syam@samsung.com>
Subject: Re: [dhcwg] *DRAFT* minutes from dhc WG meeting in DC (2nd try)
To: Ralph Droms <rdroms@cisco.com>, dhcwg@ietf.org
Message-id: <005701c4dc15$085ccd20$59476c6b@sisodomain.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Outlook Express 6.00.2800.1409
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <4.3.2.7.2.20041206162335.02215e80@flask.cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7BIT
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7BIT


Hi Ralph,

My understanding is that the second draft will be Service Discovery,
that may look like SLP but using DHCP.

The Service Classification is anyway required for the first darft also,
as the address is assigned to a particular service.

Thank you,
Syam


> 
> Anycast Address Assignment using DHCPv6            Syam Madanapalli
> draft-madanapalli-dhcpv6-anycast
> 
> Madanapalli presented summary of the draft.  Ted Lemon pointed out
> that the slides were somewhat different from the text in
> "draft-madanapalli-dhcpv6-anycast", and that the second part of the
> specification (in which the services are classified) begins to look a
> lot like SLP.  Droms suggested the draft might be spit into two
> pieces: one for assignment and one for service classification.  There
> was consensus in the room to accept the draft as a WG work item; the
> consensus will be confirmed on WG mailing list.
> 


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


From dhcwg-bounces@ietf.org  Thu Dec  9 04:31:49 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05390
	for <dhcwg-web-archive@ietf.org>; Thu, 9 Dec 2004 04:31:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CcKlJ-0000NK-Tz
	for dhcwg-web-archive@ietf.org; Thu, 09 Dec 2004 04:39:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcKaC-0001yf-9H; Thu, 09 Dec 2004 04:27:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcKXa-0001HY-QB
	for dhcwg@megatron.ietf.org; Thu, 09 Dec 2004 04:24:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04987
	for <dhcwg@ietf.org>; Thu, 9 Dec 2004 04:24:49 -0500 (EST)
Received: from tyholt.uninett.no ([158.38.60.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcKeX-0000GH-KG
	for dhcwg@ietf.org; Thu, 09 Dec 2004 04:32:02 -0500
Received: from sverresborg.uninett.no (sverresborg.uninett.no
	[IPv6:2001:700:e000:0:204:75ff:fee4:423b])
	by tyholt.uninett.no (8.12.10/8.12.10) with ESMTP id iB99Oj3U014045;
	Thu, 9 Dec 2004 10:24:45 +0100
Received: (from venaas@localhost)
	by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id iB99OiNh003097;
	Thu, 9 Dec 2004 10:24:44 +0100
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to
	Stig.Venaas@uninett.no using -f
Date: Thu, 9 Dec 2004 10:24:44 +0100
From: Stig Venaas <Stig.Venaas@uninett.no>
To: "JINMEI Tatuya / ?$B?@L@C#:H" <jinmei@isl.rdc.toshiba.co.jp>
Message-ID: <20041209092443.GA2980@sverresborg.uninett.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: Dhcwg <dhcwg@ietf.org>
Subject: [dhcwg] Authentication for stateless DHCPv6
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2

Jinmei,

We had some discussion earlier on how to do authentication of
information-request - reply without requiring any state on the
server.

I believe this is possible using the mechanism described in appendix
A of RFC 3118. The idea is to have a master key MK that the server
can use for computing they key for any given client. So for a given
client with a given DUID D, you can compute the respective key K_D
as MAC(MK, D) where MAC is a keyed one-way function. This means that
the only state needed on the server is the master key, it doesn't
need to store keys per client.

For the above to work, a client must include the Client Identifier
option in the information-request. At least section 18.1.5 of RFC
3315 has some text saying it SHOULD be included in general, and that
it MUST be included if the information-request will be authenticated.

The replay detection field should not be an issue. By using e.g. a
time stamp there's no per client state.

What do you think? I think it's doable, or am I missing something?

If this solution works, then the situation for stateless DHCPv6 is
not as bad as draft-ietf-dhc-dhcpv6-clarify-auth-00.txt indicates.

Stig

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


From dhcwg-bounces@ietf.org  Fri Dec 10 06:18:27 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04512
	for <dhcwg-web-archive@ietf.org>; Fri, 10 Dec 2004 06:18:27 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CciuI-0002A0-Pk
	for dhcwg-web-archive@ietf.org; Fri, 10 Dec 2004 06:25:55 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ccid4-0006Zk-LW; Fri, 10 Dec 2004 06:08:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CcibS-0006Br-U9
	for dhcwg@megatron.ietf.org; Fri, 10 Dec 2004 06:06:27 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03634
	for <dhcwg@ietf.org>; Fri, 10 Dec 2004 06:06:24 -0500 (EST)
Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cciic-0001uh-Q0
	for dhcwg@ietf.org; Fri, 10 Dec 2004 06:13:52 -0500
Received: from ocean.jinmei.org (unknown
	[3ffe:501:100f:1048:5c31:4b60:a406:2638])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP
	id 03CFA1521B; Fri, 10 Dec 2004 20:06:24 +0900 (JST)
Date: Fri, 10 Dec 2004 20:06:35 +0900
Message-ID: <y7vy8g6e7k4.wl@ocean.jinmei.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: Stig Venaas <Stig.Venaas@uninett.no>
In-Reply-To: <20041209092443.GA2980@sverresborg.uninett.no>
References: <20041209092443.GA2980@sverresborg.uninett.no>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0
	(SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: Dhcwg <dhcwg@ietf.org>
Subject: [dhcwg] Re: Authentication for stateless DHCPv6
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d

>>>>> On Thu, 9 Dec 2004 10:24:44 +0100, 
>>>>> Stig Venaas <Stig.Venaas@uninett.no> said:

> We had some discussion earlier on how to do authentication of
> information-request - reply without requiring any state on the
> server.

> I believe this is possible using the mechanism described in appendix
> A of RFC 3118. The idea is to have a master key MK that the server
> can use for computing they key for any given client. So for a given
> client with a given DUID D, you can compute the respective key K_D
> as MAC(MK, D) where MAC is a keyed one-way function. This means that
> the only state needed on the server is the master key, it doesn't
> need to store keys per client.

> For the above to work, a client must include the Client Identifier
> option in the information-request. At least section 18.1.5 of RFC
> 3315 has some text saying it SHOULD be included in general, and that
> it MUST be included if the information-request will be authenticated.

> The replay detection field should not be an issue. By using e.g. a
> time stamp there's no per client state.

> What do you think? I think it's doable, or am I missing something?

Thanks for the information, I've not been aware of the appendix.  I've
still not read it, but the mechanism seems to provide a reasonable
solution to the problem we are facing.  I'll look into the original
document later.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

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


From dhcwg-bounces@ietf.org  Fri Dec 10 22:03:26 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25783
	for <dhcwg-web-archive@ietf.org>; Fri, 10 Dec 2004 22:03:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ccxev-0007cW-St
	for dhcwg-web-archive@ietf.org; Fri, 10 Dec 2004 22:11:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcxSu-0002Oo-1E; Fri, 10 Dec 2004 21:58:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CcxRV-0001vu-1S; Fri, 10 Dec 2004 21:57:09 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25486;
	Fri, 10 Dec 2004 21:57:07 -0500 (EST)
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.33)
	id 1CcxYo-0007XK-DW; Fri, 10 Dec 2004 22:04:42 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 10 Dec 2004 19:49:12 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iBB2hK5M012564;
	Fri, 10 Dec 2004 18:43:21 -0800 (PST)
Received: from volzw2k (che-vpn-cluster-2-21.cisco.com [10.86.242.21])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANQ21959;
	Fri, 10 Dec 2004 21:43:19 -0500 (EST)
From: "Bernie Volz" <volz@cisco.com>
To: <ietf@ietf.org>, <dhcwg@ietf.org>
Date: Fri, 10 Dec 2004 21:43:19 -0500
Organization: Cisco
Message-ID: <005a01c4df2b$2c748cc0$6701a8c0@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: quoted-printable
Subject: [dhcwg] Notice - DHCPv4 options 128-223 soon to be IANA assignable
	(RFC 3942)
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: quoted-printable

Hi:

A new RFC has just been issued, RFC 3942
(http://www.ietf.org/rfc/rfc3942.txt): "Reclassifying DHCPv4 Options". =
The
document is a product of the IETF DHC WG and expands the range of DHCPv4
option numbers that are in the IETF/IANA assignable range. The expanded
public range reduces the site-specific options range that was originally
defined in RFC 2132..

                       Old ranges            New ranges
IETF/IANA assignable:   1-127                 1-223
Site-specific:          128-254               224-254

So, why might you care about this?

Many vendors have used "site-specific" options in the range 128-254 for
vendor-specific purposes in shipping products. And, now that IANA can =
assign
options numbers in the range 128-223 to future Internet Standard =
options, we
need your assistance to prevent potential conflicts in the use of option
codes in the newly expanded range.

RFC 3942 has a mechanism whereby IANA will not assign any option codes =
in
the newly expanded range, 128-223, for 6 months (this period will end in =
May
2005). During this 6 month period, vendors using options in the 128-223
range should come forward to let IANA and the DHC WG know of their use. =
IANA
can be contacted at mailto:iana@iana.org and the IETF DHC WG can be
contacted at mailto:dhcwg@ietf.org.

The vendor will also need to write an Internet Draft documenting that =
usage
and advance that draft to an RFC.  The Internet Draft can either be =
written
by the vendor or by the vendor providing the material for documenting =
their
usage to Bernie Volz (mailto:volz@cisco.com) for inclusion in a general
draft documenting several options.

Once the Internet Draft has been published, it will be, at the vendor's
discretion, published as an Informational RFC or entered into standards
track for publication as an Internet Standard RFC.

Therefore, please pass this email on as appropriate and contact Bernie =
Volz
for more information.

- Bernie Volz

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


From dhcwg-bounces@ietf.org  Mon Dec 13 08:48:06 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08786
	for <dhcwg-web-archive@ietf.org>; Mon, 13 Dec 2004 08:48:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CdqgN-00069N-72
	for dhcwg-web-archive@ietf.org; Mon, 13 Dec 2004 08:56:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CdqOD-0004us-I0; Mon, 13 Dec 2004 08:37:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CdqCG-0007lt-J8
	for dhcwg@megatron.ietf.org; Mon, 13 Dec 2004 08:25:04 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06283
	for <dhcwg@ietf.org>; Mon, 13 Dec 2004 08:25:03 -0500 (EST)
Received: from [210.22.146.172] (helo=asbmx.sbell.com.cn)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdqK3-0005UB-HG
	for dhcwg@ietf.org; Mon, 13 Dec 2004 08:33:09 -0500
Received: from asbwebshld.sbell.com.cn (asbwebshld [172.24.208.38])
	by asbmx.sbell.com.cn (8.12.10+Sun/8.12.3) with SMTP id iBDDJ5hi024722
	for <dhcwg@ietf.org>; Mon, 13 Dec 2004 21:19:11 +0800 (CST)
Received: FROM bellnet-mail4.sbell.com.cn BY asbwebshld.sbell.com.cn ;
	Mon Dec 13 21:24:11 2004 +0800
Received: from BELLNET-MAIL3.sbell.com.cn ([172.24.208.23]) by
	bellnet-mail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.6713); 
	Mon, 13 Dec 2004 21:24:11 +0800
content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: [dhcwg] dhcpv6 'zone suffix' option
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Date: Mon, 13 Dec 2004 21:24:11 +0800
Message-ID: <8634B809B90D6E4AACA4AB0562A1F07205EDF2@bellnet-mail3.sbell.com.cn>
Thread-Topic: [dhcwg] dhcpv6 'zone suffix' option
Thread-Index: AcThFwiCWtu1C0NbSHylSZjXzoHTVw==
From: "CTO YAN Renxiang" <Renxiang.Yan@alcatel-sbell.com.cn>
To: <dhcwg@ietf.org>
X-OriginalArrivalTime: 13 Dec 2004 13:24:11.0952 (UTC)
	FILETIME=[08B0D300:01C4E117]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
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="===============1711700359=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88

This is a multi-part message in MIME format.

--===============1711700359==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4E117.0882F82C"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4E117.0882F82C
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64

SGksIGFsbCwNCg0KSSd2ZSBzdWJtaXR0ZWQgdGhlIG5ldyB2ZXJzaW9uIG9mIHRoZSBkcmFmdCB0
byB0aGUgbWFpbGluZyBsaXN0IGZvciBzb21lIGRheXMsIGJ5IG5vdywgbm8gZmVlZGJhY2sgcmVj
ZWl2ZWQuIA0KDQpJIGJlbGlldmUgdGhlIHF1ZXN0aW9ucyByYWlzZWQgaW4gdGhlIDYxdGggbWVl
dGluZyBoYXZlIGJlZW4gY2xhcmlmaWVkIGluIHRoZSBuZXcgZHJhZnQuIFRoZSBtYWluIGNvbmNl
cm4gaXMgdGhlIHNlY3VyaXR5LiANCg0KSW4gdmVyc2lvbjEsIHdlIGdhdmUgYW4gZXhhbXBsZSwg
aW4gd2hpY2ggdXNlciB1cGRhdGVzIEROUyBSUiBpbiBETlMgc2VydmVyLiBpbiBmYWN0LCB0aGlz
IGV4YW1wbGUgaGF2ZSBubyBkaXJlY3QgcmVsYXRpb25zaGlwIHdpdGggdGhlIG9wdGlvbnMgcHJv
cG9zZWQgaW4gdGhlIGRyYWZ0LiBUaGUgaWRlYSBpbiB0aGUgZHJhZnQgb25seSBwcm9wb3NlcyBh
IG1ldGhvZCB0byBjb25maWd1cmUgdGhlIHpvbmUgc3VmZml4LiAgSXQgZG9lcyBub3QgY29uY2Vy
biB3aG8gcGVyZm9ybXMgRE5TIHVwZGF0ZS4gSW4gdmVyc2lvaW4yLCB3ZSBjbGFyaWZ5IHRoaXMg
aXNzdWUgdG8gYXZvaWQgdGhlIG1pc3VuZGVyc3RhbmRpbmcuIE1vcmVvdmVyLCBhZnRlciBkaXNj
dXNzaW9uLCAgVm9seiBhbmQgSSBhZ3JlZSB0byBhdHRhY2ggdGhlICJ6b25lIHN1ZmZpeCIgb3B0
aW9uIHdpdGggSUFfUEQgb3B0aW9uLg0KDQogRG9lcyBhbnlvbmUgaGF2ZSBvdGhlciBvcGluaW9u
cyBhYm91dCB0aGF0PyAgUGxlYXNlIGdpdmUgbWUgdGhlIGNvbW1lbnRzLCBnb29kIG9yIGJhZC4N
Cg0KVGhhbmsgeW91IQ0KDQotWWFuIA0KDQo=

------_=_NextPart_001_01C4E117.0882F82C
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PEhUTUw+CjxIRUFEPgo8TUVUQSBOQU1FPSJHRU5FUkFUT1IiIENvbnRlbnQ9Ik1pY3Jvc29mdCBE
SFRNTCBFZGl0aW5nIENvbnRyb2wiPgo8VElUTEU+PC9USVRMRT4KPC9IRUFEPgo8Qk9EWT4KPERJ
Vj48Rk9OVCBzaXplPTI+SGksIGFsbCw8L0ZPTlQ+PC9ESVY+CjxQPjxGT05UIHNpemU9Mj5JJ3Zl
IHN1Ym1pdHRlZCB0aGUgbmV3IHZlcnNpb24gb2YgdGhlIGRyYWZ0IHRvIHRoZSBtYWlsaW5nIGxp
c3QgCmZvciBzb21lIGRheXMsIGJ5IG5vdywgbm8gZmVlZGJhY2sgcmVjZWl2ZWQuIDwvRk9OVD48
L1A+CjxQPjxGT05UIHNpemU9Mj5JIGJlbGlldmUgdGhlIHF1ZXN0aW9ucyByYWlzZWQgaW4gdGhl
IDYxdGggbWVldGluZyBoYXZlIGJlZW4gCmNsYXJpZmllZCBpbiB0aGUgbmV3IGRyYWZ0LjwvRk9O
VD4gVGhlIG1haW4gY29uY2VybiBpcyB0aGUgc2VjdXJpdHkuIDwvUD4KPFA+PEZPTlQgc2l6ZT0y
PkluIHZlcnNpb24xLCB3ZSBnYXZlIGFuIGV4YW1wbGUsIGluIHdoaWNoIHVzZXIgdXBkYXRlcyBE
TlMgUlIgaW4gCkROUyBzZXJ2ZXIuIGluIGZhY3QsIHRoaXMgZXhhbXBsZSBoYXZlIG5vIGRpcmVj
dCByZWxhdGlvbnNoaXAgd2l0aCB0aGUgb3B0aW9ucyAKcHJvcG9zZWQgaW4gdGhlIGRyYWZ0LiBU
aGUgaWRlYSBpbiB0aGUgZHJhZnQgb25seSBwcm9wb3NlcyBhIG1ldGhvZCB0byBjb25maWd1cmUg
CnRoZSB6b25lIHN1ZmZpeC4mbmJzcDsgSXQgZG9lcyBub3QgY29uY2VybiB3aG8gcGVyZm9ybXMg
RE5TIHVwZGF0ZS4gPC9GT05UPjxGT05UIApzaXplPTI+SW4gdmVyc2lvaW4yLCB3ZSBjbGFyaWZ5
IHRoaXMgaXNzdWUgdG8gYXZvaWQgdGhlIG1pc3VuZGVyc3RhbmRpbmcuIApNb3Jlb3ZlciwgYWZ0
ZXIgZGlzY3Vzc2lvbiwmbmJzcDsgVm9seiBhbmQgSSBhZ3JlZSB0byBhdHRhY2ggdGhlICJ6b25l
IHN1ZmZpeCIgCm9wdGlvbiB3aXRoIElBX1BEIG9wdGlvbi48L0ZPTlQ+PC9QPgo8UD4mbmJzcDtE
b2VzIGFueW9uZSBoYXZlIG90aGVyIG9waW5pb25zIGFib3V0IHRoYXQ/Jm5ic3A7IFBsZWFzZSBn
aXZlIG1lIHRoZSAKY29tbWVudHMsIGdvb2Qgb3IgYmFkLjwvUD4KPFA+VGhhbmsgeW91ITwvUD4K
PFA+PEZPTlQgc2l6ZT0yPi1ZYW48L0ZPTlQ+IDwvUD4KPC9CT0RZPgo8L0hUTUw+

------_=_NextPart_001_01C4E117.0882F82C--


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

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

--===============1711700359==--



From dhcwg-bounces@ietf.org  Mon Dec 13 15:16:25 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14479
	for <dhcwg-web-archive@ietf.org>; Mon, 13 Dec 2004 15:16:25 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CdwkD-00081j-Qw
	for dhcwg-web-archive@ietf.org; Mon, 13 Dec 2004 15:24:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CdwYE-0006Ir-J3; Mon, 13 Dec 2004 15:12:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CdwNH-0004UK-SV
	for dhcwg@megatron.ietf.org; Mon, 13 Dec 2004 15:00:51 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12409
	for <dhcwg@ietf.org>; Mon, 13 Dec 2004 15:00:47 -0500 (EST)
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.33)
	id 1CdwV6-0007Xz-0s
	for dhcwg@ietf.org; Mon, 13 Dec 2004 15:08:57 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 13 Dec 2004 13:06:37 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iBDK06W2021740
	for <dhcwg@ietf.org>; Mon, 13 Dec 2004 12:00:12 -0800 (PST)
Received: from rdroms-w2k01.cisco.com ([161.44.65.124])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANR06753;
	Mon, 13 Dec 2004 15:00:07 -0500 (EST)
Message-Id: <4.3.2.7.2.20041213140310.00c97370@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 13 Dec 2004 15:00:05 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Subject: [dhcwg] Co-chair for dhc WG
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c

The Internet ADs and I have been discussing the appointment of a co-chair
for the dhc WG.  Reasons for appointing a co-chair include: workload
sharing; eliminating single point of failure in WG leadership; fair and open
handling by a co-chair for documents that the other co-chair has
co-authored.

We are considering a specific candidate, and I'll post an announcement once
the appointment is official.

- Ralph

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


From dhcwg-bounces@ietf.org  Tue Dec 14 10:42:09 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10730
	for <dhcwg-web-archive@ietf.org>; Tue, 14 Dec 2004 10:42:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeEwW-0004mC-EY
	for dhcwg-web-archive@ietf.org; Tue, 14 Dec 2004 10:50:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeEkA-00080A-NA; Tue, 14 Dec 2004 10:37:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeES1-0001LF-6P
	for dhcwg@megatron.ietf.org; Tue, 14 Dec 2004 10:18:58 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07501
	for <dhcwg@ietf.org>; Tue, 14 Dec 2004 10:18:55 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeEa2-00040d-H8
	for dhcwg@ietf.org; Tue, 14 Dec 2004 10:27:15 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 14 Dec 2004 07:22:14 -0800
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iBEFIKsv005043;
	Tue, 14 Dec 2004 07:18:20 -0800 (PST)
Received: from volzw2k ([161.44.65.137]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id ANR61771; Tue, 14 Dec 2004 10:18:18 -0500 (EST)
From: "Bernie Volz" <volz@cisco.com>
To: "'CTO YAN Renxiang'" <Renxiang.Yan@alcatel-sbell.com.cn>, <dhcwg@ietf.org>
Subject: RE: [dhcwg] dhcpv6 'zone suffix' option
Date: Tue, 14 Dec 2004 10:18:18 -0500
Organization: Cisco
Message-ID: <000201c4e1f0$24a46250$89412ca1@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
In-Reply-To: <8634B809B90D6E4AACA4AB0562A1F0725D6DE0@bellnet-mail3.sbell.com.cn>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: quoted-printable
Cc: mjs@cisco.com, jdq@lucent.com, Ted.Lemon@nominum.com
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: quoted-printable

Yan:

The option format is incorrect. For DHCPv6 options, the option code and
option length fields are both 16-bits. You have the option code field as
8-bits. See RFC 3315, section 22.1.

Also, I wonder whether any discussion of DNS update issues is needed -- =
the
requesting router may need a TSIG key or other authentication =
information in
order to perform any DNS updates.

- Bernie

> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org]
> On Behalf Of CTO YAN Renxiang
> Sent: Monday, November 29, 2004 8:58 PM
> To: dhcwg@ietf.org
> Cc: mjs@cisco.com; Ted.Lemon@nominum.com; jdq@lucent.com;=20
> volz@cisco.com
> Subject: re: [dhcwg] dhcpv6 'zone suffix' option
>=20
>=20
> Hi, all,
>=20
> According to the discussion before, I revised the draft based
> on the common opinions. Any question or suggestion will be=20
> appreciated.
>=20
> -Yan
>=20

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


From dhcwg-bounces@ietf.org  Tue Dec 14 11:54:44 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19995
	for <dhcwg-web-archive@ietf.org>; Tue, 14 Dec 2004 11:54:44 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeG4n-0006vF-8G
	for dhcwg-web-archive@ietf.org; Tue, 14 Dec 2004 12:03:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeFtP-00066E-CX; Tue, 14 Dec 2004 11:51:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeFjR-0003u5-Uw
	for dhcwg@megatron.ietf.org; Tue, 14 Dec 2004 11:41:01 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18984
	for <dhcwg@ietf.org>; Tue, 14 Dec 2004 11:40:59 -0500 (EST)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeFrS-0006Wj-KR
	for dhcwg@ietf.org; Tue, 14 Dec 2004 11:49:20 -0500
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by rtp-iport-1.cisco.com with ESMTP; 14 Dec 2004 11:48:11 -0500
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iBEGePQ6023827
	for <dhcwg@ietf.org>; Tue, 14 Dec 2004 11:40:25 -0500 (EST)
Received: from rdroms-w2k01.cisco.com ([161.44.65.124])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANR69624;
	Tue, 14 Dec 2004 11:40:24 -0500 (EST)
Message-Id: <4.3.2.7.2.20041214113449.02a86d40@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 14 Dec 2004 11:40:06 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Subject: [dhcwg] draft-stapp-dhc-vendor-suboption to WG last call
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad

There was consensus at the dhc WG meeting in DC to take:

draft-stapp-dhc-vendor-suboption-01.txt

to WG last call.  If there are no objections posted to the WG mailing list,
I will start a WG last call for this draft on 2004-12-17.

- Ralph

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


From dhcwg-bounces@ietf.org  Tue Dec 14 12:26:54 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23545
	for <dhcwg-web-archive@ietf.org>; Tue, 14 Dec 2004 12:26:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeGZj-00080q-QH
	for dhcwg-web-archive@ietf.org; Tue, 14 Dec 2004 12:35:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeG7F-0001K2-Hd; Tue, 14 Dec 2004 12:05:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeFxv-000742-44
	for dhcwg@megatron.ietf.org; Tue, 14 Dec 2004 11:55:59 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20090
	for <dhcwg@ietf.org>; Tue, 14 Dec 2004 11:55:57 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeG5y-0006xQ-HQ
	for dhcwg@ietf.org; Tue, 14 Dec 2004 12:04:18 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-4.cisco.com with ESMTP; 14 Dec 2004 08:55:31 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iBEGtNMI023641
	for <dhcwg@ietf.org>; Tue, 14 Dec 2004 08:55:23 -0800 (PST)
Received: from rdroms-w2k01.cisco.com ([161.44.65.124])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANR71217;
	Tue, 14 Dec 2004 11:55:24 -0500 (EST)
Message-Id: <4.3.2.7.2.20041214114014.02a94d58@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 14 Dec 2004 11:43:53 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Subject: [dhcwg] draft-ietf-dhc-lifetime to WG last call
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22

There was consensus at the dhc WG meeting in DC to take:

draft-ietf-dhc-lifetime-02.txt

to WG last call.  Here are the notes about the discussion of this draft at
the WG meeting:

   Venaas gave an update about the draft, which has been previously
   discussed by the WG.  The title of the specification has been
   changed to "Information Refresh Time Option for DHCPv6" as the
   option controls when a client contacts the DHCP server, but does not
   cause previously obtained information to expire in any way.  Some
   minor issues were raised about max and min values for lifetime which
   will be discussed on WG mailing list.  Pending that discussion,
   there was consensus in room to go to WG last call.  Consensus to be
   confirmed on WG mailing list.

Any remaining discussion about the max and min values for the refresh time
(was "lifetime") can be carried on during the WG last call.  If there are no
objections posted to the WG mailing list, I will start a WG last call for
this draft on 2004-12-17.

- Ralph

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


From dhcwg-bounces@ietf.org  Tue Dec 14 12:31:50 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23920
	for <dhcwg-web-archive@ietf.org>; Tue, 14 Dec 2004 12:31:50 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeGeh-0008Ar-7E
	for dhcwg-web-archive@ietf.org; Tue, 14 Dec 2004 12:40:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeGRR-0007pO-7J; Tue, 14 Dec 2004 12:26:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeG5a-0000oR-PL
	for dhcwg@megatron.ietf.org; Tue, 14 Dec 2004 12:03:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21207
	for <dhcwg@ietf.org>; Tue, 14 Dec 2004 12:03:52 -0500 (EST)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeGDb-0007FR-GN
	for dhcwg@ietf.org; Tue, 14 Dec 2004 12:12:12 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-2.cisco.com with ESMTP; 14 Dec 2004 12:03:20 -0500
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iBEH3H9E029978
	for <dhcwg@ietf.org>; Tue, 14 Dec 2004 12:03:17 -0500 (EST)
Received: from rdroms-w2k01.cisco.com ([161.44.65.124])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANR71978;
	Tue, 14 Dec 2004 12:03:16 -0500 (EST)
Message-Id: <4.3.2.7.2.20041214114438.02a90a48@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 14 Dec 2004 12:03:14 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Subject: [dhcwg] draft-madanapalli-dhcpv6-anycast to WG last call
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32

There was consensus at the dhc WG meeting in DC to accept:

draft-madanapalli-dhcpv6-anycast-00.txt

as a WG work item.  Here are the notes about the discussion of this draft at
the WG meeting:

   Madanapalli presented summary of the draft.  Ted Lemon pointed out
   that the slides were somewhat different from the text in
   "draft-madanapalli-dhcpv6-anycast", and that the second part of the
   specification (in which the services are classified) begins to look
   a lot like SLP.  Droms suggested the draft might be spit into two
   pieces: one for assignment and one for service classification.
   There was consensus in the room to accept the draft as a WG work
   item; the consensus will be confirmed on WG mailing list.

If there are no objections posted to the WG mailing list, the WG will accept
a revised version of the draft as a WG work item.

- Ralph

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


From dhcwg-bounces@ietf.org  Tue Dec 14 12:36:21 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24523
	for <dhcwg-web-archive@ietf.org>; Tue, 14 Dec 2004 12:36:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeGj5-0008I3-H2
	for dhcwg-web-archive@ietf.org; Tue, 14 Dec 2004 12:44:43 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeGSK-0008Hi-Ko; Tue, 14 Dec 2004 12:27:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeGCS-0002Ul-JY
	for dhcwg@megatron.ietf.org; Tue, 14 Dec 2004 12:11:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22448
	for <dhcwg@ietf.org>; Tue, 14 Dec 2004 12:10:58 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeGKV-0007cR-4G
	for dhcwg@ietf.org; Tue, 14 Dec 2004 12:19:20 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-4.cisco.com with ESMTP; 14 Dec 2004 09:10:31 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iBEHALMI002208
	for <dhcwg@ietf.org>; Tue, 14 Dec 2004 09:10:21 -0800 (PST)
Received: from rdroms-w2k01.cisco.com ([161.44.65.124])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANR72638;
	Tue, 14 Dec 2004 12:10:24 -0500 (EST)
Message-Id: <4.3.2.7.2.20041214120552.02a94d58@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 14 Dec 2004 12:09:04 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Subject: [dhcwg] draft-droms-dhc-v6-relayopt as WG work item
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad

There was consensus at the dhc WG meeting in DC to accept:

  draft-droms-dhc-v6-relayopt-00.txt

as a WG work item.  If there are no objections posted to the WG mailing
list, the WG will accept the draft as a WG work item.

- Ralph 

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


From dhcwg-bounces@ietf.org  Tue Dec 14 12:41:06 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25000
	for <dhcwg-web-archive@ietf.org>; Tue, 14 Dec 2004 12:41:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeGnf-0008Ru-7E
	for dhcwg-web-archive@ietf.org; Tue, 14 Dec 2004 12:49:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeGSL-0008IT-Ot; Tue, 14 Dec 2004 12:27:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeGD5-0002gY-VI
	for dhcwg@megatron.ietf.org; Tue, 14 Dec 2004 12:11:39 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22501
	for <dhcwg@ietf.org>; Tue, 14 Dec 2004 12:11:37 -0500 (EST)
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.33)
	id 1CeGL8-0007dC-F5
	for dhcwg@ietf.org; Tue, 14 Dec 2004 12:19:59 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-3.cisco.com with ESMTP; 14 Dec 2004 10:17:39 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iBEHB5sv001722
	for <dhcwg@ietf.org>; Tue, 14 Dec 2004 09:11:06 -0800 (PST)
Received: from rdroms-w2k01.cisco.com ([161.44.65.124])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANR72711;
	Tue, 14 Dec 2004 12:11:04 -0500 (EST)
Message-Id: <4.3.2.7.2.20041214120926.02a86218@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 14 Dec 2004 12:11:00 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Subject: [dhcwg] draft-ietf-dhc-fqdn-option to WG last call
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007

There was consensus at the dhc WG meeting in DC to take:

draft-ietf-dhc-fqdn-option-07.txt

to WG last call.  Here are the notes about the discussion of this draft at
the WG meeting:

   Volz presented a status report: these drafts along with
   draft-ietf-dhc-3315id-for-v4 and draft-ietf-dnsext-dhcid-rr will go
   to the IESG as a package.  draft-ietf-dnsext-dhcid-rr is through WG
   last call (dnsext).  The consensus in the room was to go to WG last
   call on draft-ietf-dhc-fqdn-option; consensus will be confirmed on
   the WG mailing list.

If there are no objections posted to the WG mailing list, I will start a WG
last call for this draft on 2004-12-17.


- Ralph 

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


From dhcwg-bounces@ietf.org  Tue Dec 14 17:51:20 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01579
	for <dhcwg-web-archive@ietf.org>; Tue, 14 Dec 2004 17:51:20 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeLdw-0001e0-Tx
	for dhcwg-web-archive@ietf.org; Tue, 14 Dec 2004 17:59:45 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeLPm-000449-9f; Tue, 14 Dec 2004 17:45:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeLNX-0003ab-3s
	for dhcwg@megatron.ietf.org; Tue, 14 Dec 2004 17:42:47 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00672
	for <dhcwg@ietf.org>; Tue, 14 Dec 2004 17:42:45 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeLVd-0001O4-In
	for dhcwg@ietf.org; Tue, 14 Dec 2004 17:51:09 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 14 Dec 2004 14:46:08 -0800
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iBEMgCMI025410
	for <dhcwg@ietf.org>; Tue, 14 Dec 2004 14:42:13 -0800 (PST)
Received: from rdroms-w2k01.cisco.com ([161.44.65.124])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANS04911;
	Tue, 14 Dec 2004 17:42:11 -0500 (EST)
Message-Id: <4.3.2.7.2.20041214173517.03d243f0@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 14 Dec 2004 17:42:07 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Subject: [dhcwg] draft-vijay-dhc-dhcpv6-mcast-reconf-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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2

At the dhc WG meeting in DC, the WG was asked to consider
draft-vijay-dhc-dhcpv6-mcast-reconf-01.txt for acceptance as a WG work item.
Here are the notes from the WG meeting:

   Park gave a summary of the draft.  Droms asked why the protocol uses
   Relay-reply message to notify router (through relay) to toggle
   'M'/'O' bits; isn't CLI sufficient?  Greg Daley suggested SNMP might
   be appropriate to cause router to toggle 'M'/'O' bits.  Some
   additional discussion about whether this mechanism is needed if
   "Information Refresh Time Option for DHCPv6" is accepted for
   standards track.  Volz pointed out that "multicast reconfig" is
   useful for unplanned renumbering.  Park was requested to provide
   more detail; further discussion will take place on the WG mailing
   list before coming to a decision about taking this draft on as a WG
   work item.

I need to be to be convinced of the need for this mechanism.  If the 
network is
being reconfigured (e.g., the link is renumbered), presumably the router must
be accessed to change its configuration.  Seems to me the router could be
caused to toggle the 'M'/'O' bits at the same time.  Why would a separate
message from the DHCP server be required?

The unsolicited Relay-reply message from the server requires changes in the
operation of the relay, so it can receive and process messages from the
server that don't have a matching Relay-forward message.

- Ralph

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


From dhcwg-bounces@ietf.org  Tue Dec 14 18:10:32 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03504
	for <dhcwg-web-archive@ietf.org>; Tue, 14 Dec 2004 18:10:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeLwW-00027s-Sr
	for dhcwg-web-archive@ietf.org; Tue, 14 Dec 2004 18:18:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeLls-0001vM-9p; Tue, 14 Dec 2004 18:07:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeLj9-00010X-Vh
	for dhcwg@megatron.ietf.org; Tue, 14 Dec 2004 18:05:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02897
	for <dhcwg@ietf.org>; Tue, 14 Dec 2004 18:05:05 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeLrG-000215-6y
	for dhcwg@ietf.org; Tue, 14 Dec 2004 18:13:30 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 14 Dec 2004 15:08:30 -0800
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iBEN4VVw021678;
	Tue, 14 Dec 2004 15:04:32 -0800 (PST)
Received: from volzw2k ([161.44.65.137]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id ANS06669; Tue, 14 Dec 2004 18:04:32 -0500 (EST)
From: "Bernie Volz" <volz@cisco.com>
To: "'Ralph Droms'" <rdroms@cisco.com>, <dhcwg@ietf.org>
Subject: RE: [dhcwg] draft-ietf-dhc-fqdn-option to WG last call
Date: Tue, 14 Dec 2004 18:04:32 -0500
Organization: Cisco
Message-ID: <003401c4e231$459dc960$89412ca1@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
In-Reply-To: <4.3.2.7.2.20041214120926.02a86218@flask.cisco.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176
Content-Transfer-Encoding: quoted-printable
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 33cc095b503da4365ce57c727e553cf1
Content-Transfer-Encoding: quoted-printable

I just got feedback from Olafur and want to revise the draft to clean up =
and
improve the language.

Attached is what Olafur sent me.

So, please postpone the WG last call until after the -08 draft is posted =
and
we receive some feedback on it.

- Bernie

> -----Original Message-----
> From: =D3lafur Gu=F0mundsson [mailto:ogud@ogud.com]=20
> Sent: Tuesday, December 14, 2004 2:29 PM
> To: Bernie Volz; 'Stapp, Mark'; rdroms@cisco.com; 'Olafur Gudmundsson'
> Subject: Re: Updated draft-ietf-dhc-dhc-fqdn-option
>=20
>=20
> At 14:36 10/12/2004, Bernie Volz wrote:
> >Hi:
> >
> >I've updated the DHCPv4 FQDN draft. New proposed draft and a diff of=20
> >the text are attached.
> >
> >Basically, the change was in how the RCODE1/RCODE2 fields were=20
> >described -- they are now considered deprecated.
> >
> >Please email me with any other comments that should be=20
> addressed before=20
> >I re-submit this. I'd like to resubmit by December 17th.
> >
> >- Bernie
> >
>=20
> Thanks for the head, up and my apologies for responding this=20
> late. Here are my comments:
>=20
> 1. The document needs an IANA sections that says the option=20
> is already=20
> allocated and this document updates the options use, and=20
> should be the document that IANA maintains for DHCP Options.=20
> There should be an explicit link from section 4 to IANA=20
> section and vice versa.
>=20
> 2. Document is better than before, and addresses my issue=20
> with the RCODE usage.
>=20
> 3. The document uses the words "we" as expressing editor=20
> opinions, I find this style bad in WG documents. See section=20
> 4.1 paragraph 5. (this whole paragraph was real hard to=20
> parse, please rewrite).
>=20
> 4. The RFC 2119 words are used in lower case in few places,
>          may is used in 27+ places in non upper case
>          must 1
>          required 1
>          should 13
>=20
>     please check each one to see if it is an omission of=20
> capitalization or
>     if the sentences can be reworded better without the use=20
> of the 2119 words.
>          (I found number of these sentences hard to parse)
>=20
> 5. Section 3 (applies to some later sections as well)
>          Is the intent to specify that FQDN option can ONLY=20
> be sent during
>          lease negotiation ?
>          i.e. client can not send the option after it gets an=20
> address to
>          either change the name or add a new name.
>          If the answer is yes then I think that should be=20
> stated, if the
>          answer is no then this case needs to be covered.
>          Ralph if you want me to ask the question on the mailing list
>          I will be happy to.
>=20
> 6. Can client supply multiple FQDN options ?
>          A client may not like the name assigned by server in OFFER
>          but will take that and use its permanent name also.
>          in this case I would like to see
>          99.30.1.99.in-addr.arpa.        PTR visitor-99.md.ogud.com.
>                                          PTR ralph.dhcp.org.
>                                          PTR ns.dhcp.org.
>=20
> 7. Section 4.2 is good except in paragraph 3
> s/it can simply query/is queries/
>=20
> 8. Section 4.3 paragraph 1:
> This paragraph contains text inserted during the formative=20
> stages of the IDN working group, as the output of that WG did=20
> not result in any changes to DNS label types drop everything=20
> starting with the word "Eventually".
>=20
> Section 4.3 paragraph 2:
> I MUST say this was real confusing reading, please reword.
> I think you want to say client can send PQDN (ie missing 0x00=20
> at the end). point to section where server processing of this=20
> special case is described.
>=20
> 9. Section 4.1 Paragraph 3:
> I think you want to state that FQDN contains an extra label=20
> of length 0. (ie ends with 0x00)
>=20
> 10. section 5 paragraph 2
> s/Servers will be asked in section 6/Section 6 instructs servers/
>=20
> 11. Section 5 meta comment
> I would like to see this section broken into subsections one=20
> for each processing rule.
>=20
>=20
> 12. Section 6 (see comment #11)
> is there one particular time when server SHOULD do DNS=20
> update? The answer seems to be buried in paragraphs 5 and 8.
>=20
> I found the section to be little bit out of order and not=20
> clear to read.
> Suggestion: what does server do if it sees FQDN option or=20
> does that depend on when the server gets the option?
>=20
> Put DNS processing rules in one (or more subsections)
> Put DHCP rules in clearly defined subsections
>          Request processing rules
>          reply rules
>          DNS update
>          Lease expire rules
>=20
> 13: Section 7, last sentence
> This is not area of future work but explicitly linked document.
>=20
> 14. security considerations is good.
>=20
> In short the document needs at least one more pass after=20
> these issues have been addressed.
>=20
> Feel free to post this message or any parts of it to the
> dhc mailing list.
>=20
>          Olafur

> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org]=20
> On Behalf Of Ralph Droms
> Sent: Tuesday, December 14, 2004 12:11 PM
> To: dhcwg@ietf.org
> Subject: [dhcwg] draft-ietf-dhc-fqdn-option to WG last call
>=20
>=20
> There was consensus at the dhc WG meeting in DC to take:
>=20
> draft-ietf-dhc-fqdn-option-07.txt
>=20
> to WG last call.  Here are the notes about the discussion of=20
> this draft at the WG meeting:
>=20
>    Volz presented a status report: these drafts along with
>    draft-ietf-dhc-3315id-for-v4 and draft-ietf-dnsext-dhcid-rr will go
>    to the IESG as a package.  draft-ietf-dnsext-dhcid-rr is through WG
>    last call (dnsext).  The consensus in the room was to go to WG last
>    call on draft-ietf-dhc-fqdn-option; consensus will be confirmed on
>    the WG mailing list.
>=20
> If there are no objections posted to the WG mailing list, I=20
> will start a WG last call for this draft on 2004-12-17.
>=20
>=20
> - Ralph=20
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg
>=20

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


From dhcwg-bounces@ietf.org  Tue Dec 14 18:38:14 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05453
	for <dhcwg-web-archive@ietf.org>; Tue, 14 Dec 2004 18:38:14 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeMNL-0002ex-1k
	for dhcwg-web-archive@ietf.org; Tue, 14 Dec 2004 18:46:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeMCo-0002Ye-B4; Tue, 14 Dec 2004 18:35:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeMB2-0002BJ-GW
	for dhcwg@megatron.ietf.org; Tue, 14 Dec 2004 18:33:56 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05264
	for <dhcwg@ietf.org>; Tue, 14 Dec 2004 18:33:54 -0500 (EST)
Received: from ns.ogud.com ([66.92.146.160] helo=ogud.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeMJ8-0002Zb-8I
	for dhcwg@ietf.org; Tue, 14 Dec 2004 18:42:19 -0500
Received: from Puki.ogud.com (ns.ogud.com [66.92.146.160])
	by ogud.com (8.12.11/8.12.11) with ESMTP id iBENXklX036282
	for <dhcwg@ietf.org>; Tue, 14 Dec 2004 18:33:46 -0500 (EST)
	(envelope-from ogud@ogud.com)
Message-Id: <6.1.2.0.2.20041214130143.04ee6ec0@localhost>
X-Sender: post@localhost (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Tue, 14 Dec 2004 18:33:38 -0500
To: dhcwg@ietf.org
From: =?iso-8859-1?Q?=D3lafur?= =?iso-8859-1?Q?_Gu=F0mundsson?= <ogud@ogud.com>
Subject: Re: [dhcwg] draft-ietf-dhc-fqdn-option to WG last call
In-Reply-To: <4.3.2.7.2.20041214120926.02a86218@flask.cisco.com>
References: <4.3.2.7.2.20041214120926.02a86218@flask.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Scanned-By: MIMEDefang 2.48 on 66.92.146.160
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d


At 12:11 14/12/2004, Ralph Droms wrote:
>There was consensus at the dhc WG meeting in DC to take:
>
>draft-ietf-dhc-fqdn-option-07.txt
>
>to WG last call.  Here are the notes about the discussion of this draft at
>the WG meeting:
>
>   Volz presented a status report: these drafts along with
>   draft-ietf-dhc-3315id-for-v4 and draft-ietf-dnsext-dhcid-rr will go
>   to the IESG as a package.  draft-ietf-dnsext-dhcid-rr is through WG
>   last call (dnsext).  The consensus in the room was to go to WG last
>   call on draft-ietf-dhc-fqdn-option; consensus will be confirmed on
>   the WG mailing list.
>
>If there are no objections posted to the WG mailing list, I will start a WG
>last call for this draft on 2004-12-17.

It is not ready for Last Call, after reviewing the document I sent a long
list of things to fix to the editors (most minor).

Open questions on this document:

Is FQDN option ONLY allowed to be sent by client along with DISCOVER or 
REQUEST?
  Or can client initiate this action at any time ?

Can client include multiple FQDN options if it wants multiple PTR records 
stored
in the reverse tree?

         Olafur 


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


From dhcwg-bounces@ietf.org  Wed Dec 15 00:57:53 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02373
	for <dhcwg-web-archive@ietf.org>; Wed, 15 Dec 2004 00:57:53 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeSIo-000387-V7
	for dhcwg-web-archive@ietf.org; Wed, 15 Dec 2004 01:06:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeS95-00059T-Qn; Wed, 15 Dec 2004 00:56:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeS86-0004w4-2s
	for dhcwg@megatron.ietf.org; Wed, 15 Dec 2004 00:55:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA02170
	for <dhcwg@ietf.org>; Wed, 15 Dec 2004 00:55:15 -0500 (EST)
Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeSGG-00033Q-2s
	for dhcwg@ietf.org; Wed, 15 Dec 2004 01:03:44 -0500
Received: from ocean.jinmei.org (unknown
	[3ffe:501:100f:1048:5d6c:8d58:ea58:38e0])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP
	id 428D715210; Wed, 15 Dec 2004 14:55:08 +0900 (JST)
Date: Wed, 15 Dec 2004 14:55:21 +0900
Message-ID: <y7v6534hzqu.wl@ocean.jinmei.org>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] draft-vijay-dhc-dhcpv6-mcast-reconf-01.txt
In-Reply-To: <4.3.2.7.2.20041214173517.03d243f0@flask.cisco.com>
References: <4.3.2.7.2.20041214173517.03d243f0@flask.cisco.com>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0
	(SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: 0.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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a

>>>>> On Tue, 14 Dec 2004 17:42:07 -0500, 
>>>>> Ralph Droms <rdroms@cisco.com> said:

> I need to be to be convinced of the need for this mechanism.  If the 
> network is
> being reconfigured (e.g., the link is renumbered), presumably the router must
> be accessed to change its configuration.  Seems to me the router could be
> caused to toggle the 'M'/'O' bits at the same time.  Why would a separate
> message from the DHCP server be required?

Perhaps this is not directly related to this document, but I'd like to
note that toggling the M/O flags may not help here.  In particular,
our current interpretation (as per RFC2462 and now
draft-ietf-ipv6-ra-mo-flags) is that the change from ON to OFF doesn't
have any effects on a running DHCPv6 process.  So, for example, we
cannot expect re-invocation of the process by changing the flag from
ON-to-OFF-to-ON when some network configuration changes.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

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


From dhcwg-bounces@ietf.org  Wed Dec 15 08:51:16 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01229
	for <dhcwg-web-archive@ietf.org>; Wed, 15 Dec 2004 08:51:15 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeZgy-00063O-GU
	for dhcwg-web-archive@ietf.org; Wed, 15 Dec 2004 08:59:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeZU2-0003Xk-FH; Wed, 15 Dec 2004 08:46:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeZPt-0002p5-TY
	for dhcwg@megatron.ietf.org; Wed, 15 Dec 2004 08:42:12 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00732
	for <dhcwg@ietf.org>; Wed, 15 Dec 2004 08:42:07 -0500 (EST)
Received: from tyholt.uninett.no ([158.38.60.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeZY5-0005rn-09
	for dhcwg@ietf.org; Wed, 15 Dec 2004 08:50:40 -0500
Received: from sverresborg.uninett.no (sverresborg.uninett.no
	[IPv6:2001:700:e000:0:204:75ff:fee4:423b])
	by tyholt.uninett.no (8.12.10/8.12.10) with ESMTP id iBFDfwfq006674;
	Wed, 15 Dec 2004 14:41:58 +0100
Received: (from venaas@localhost)
	by sverresborg.uninett.no (8.12.8/8.12.8/Submit) id iBFDfsn3013562;
	Wed, 15 Dec 2004 14:41:54 +0100
X-Authentication-Warning: sverresborg.uninett.no: venaas set sender to
	Stig.Venaas@uninett.no using -f
Date: Wed, 15 Dec 2004 14:41:54 +0100
From: Stig Venaas <Stig.Venaas@uninett.no>
To: "JINMEI Tatuya / ?$B?@L@C#:H" <jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: [dhcwg] draft-vijay-dhc-dhcpv6-mcast-reconf-01.txt
Message-ID: <20041215134154.GE12441@sverresborg.uninett.no>
References: <4.3.2.7.2.20041214173517.03d243f0@flask.cisco.com>
	<y7v6534hzqu.wl@ocean.jinmei.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <y7v6534hzqu.wl@ocean.jinmei.org>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: dhcwg@ietf.org, Ralph Droms <rdroms@cisco.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135

On Wed, Dec 15, 2004 at 02:55:21PM +0900, JINMEI Tatuya / ?$B?@L@C#:H wrote:
> >>>>> On Tue, 14 Dec 2004 17:42:07 -0500, 
> >>>>> Ralph Droms <rdroms@cisco.com> said:
> 
> > I need to be to be convinced of the need for this mechanism.  If the 
> > network is
> > being reconfigured (e.g., the link is renumbered), presumably the router must
> > be accessed to change its configuration.  Seems to me the router could be
> > caused to toggle the 'M'/'O' bits at the same time.  Why would a separate
> > message from the DHCP server be required?

I'm not convinced either, but I can see potential use for it.

If the router is told to announce a new prefix on the link, then I agree
that the router could be caused to toggle the bits, but at least clients
using stateless address autoconfiguration combined with stateless DHCPv6
should when seeing the new prefix hopefully make a new information-request
anyway. For clients using DHCPv6 for address configuration, the toggling
might be needed though.

There might be other cases where you want to update the client config
while the link is not renumbered. One example could be renumbering of
a link where there is a DNS server where you may need to get hosts on
other links to learn the new DNS server address. Or there may be other
changes not related to renumbering where you want clients to
reconfigure while the config on the router remains unchanged.

Even if the router config doesn't need to change, you could tell the
router via CLI/SNMP/web interface/... that it should signal hosts to
renumber. I think that might suffice.

But I can imagine cases where router and hosts are managed by
different groups of people where the people managing the hosts may not
have access to the router at all. E.g. a provider that owns the router
at the customer's site and doesn't give the customer access. In that
case I'm not sure whether the necessary trust can be established
between relay (router) and server either though.

One option might be to wait for the M/O toggling or other RA mechanism
to be deployed, and see whether there's a need for this server-relay
signalling, or if using CLI/SNMP/web interface is sufficent?

Well, it might be needed, but as I said, I'm not convinced.

> Perhaps this is not directly related to this document, but I'd like to
> note that toggling the M/O flags may not help here.  In particular,
> our current interpretation (as per RFC2462 and now
> draft-ietf-ipv6-ra-mo-flags) is that the change from ON to OFF doesn't
> have any effects on a running DHCPv6 process.  So, for example, we
> cannot expect re-invocation of the process by changing the flag from
> ON-to-OFF-to-ON when some network configuration changes.

I feel a bit uneasy about this toggling. I'm not sure how well it will
work in practice. Let's say you're changing a flag from ON to OFF and
back again. How long do you need it to be OFF for all clients to have
seen it? Can it be that some RAs are lost? If you need to leave it OFF
for a while, is it a problem if new clients on the link initially see
the flag being OFF? It might also be an issue with clients not
receiving RAs due to temporary link disconnection, say a wireless
client temporarily out of reach, or maybe a laptop being suspended for
a short while.

Stig

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


From dhcwg-bounces@ietf.org  Wed Dec 15 14:06:41 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28823
	for <dhcwg-web-archive@ietf.org>; Wed, 15 Dec 2004 14:06:41 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeecG-0006qL-A0
	for dhcwg-web-archive@ietf.org; Wed, 15 Dec 2004 14:15:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CeeLK-0002Mq-NE; Wed, 15 Dec 2004 13:57:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeeBP-0008SD-Si
	for dhcwg@megatron.ietf.org; Wed, 15 Dec 2004 13:47:31 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27078
	for <dhcwg@ietf.org>; Wed, 15 Dec 2004 13:47:30 -0500 (EST)
Received: from kaboom.isc.org ([204.152.187.72])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeeJg-0006F3-VW
	for dhcwg@ietf.org; Wed, 15 Dec 2004 13:56:05 -0500
Received: by kaboom.isc.org (Postfix, from userid 10200)
	id 0D227B246C; Wed, 15 Dec 2004 10:46:58 -0800 (PST)
Date: Wed, 15 Dec 2004 10:46:58 -0800
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] draft-ietf-dhc-fqdn-option to WG last call
Message-ID: <20041215184658.GD58434@isc.org>
References: <4.3.2.7.2.20041214120926.02a86218@flask.cisco.com>
	<003401c4e231$459dc960$89412ca1@amer.cisco.com>
Mime-Version: 1.0
In-Reply-To: <003401c4e231$459dc960$89412ca1@amer.cisco.com>
User-Agent: Mutt/1.4.2.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
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="===============0463552209=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1


--===============0463552209==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="TybLhxa8M7aNoW+V"
Content-Disposition: inline


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

On Tue, Dec 14, 2004 at 06:04:32PM -0500, Bernie Volz wrote:
> I just got feedback from Olafur and want to revise the draft to clean up =
and
> improve the language.

So long as you're editing...

After reading this draft I walked away with a feeling that the
client/server interaction between FQDNs and delayed RCODEs (the
special-case 255 values) was poorly defined.

I think there's an implicit behaviour in the draft that every REQUEST
contains an FQDN option.  So in the case where the server sends RCODEs
with 255 values, it is expected to retain the actual RCODEs whenever
they should arrive, and deliver those in the next ACK when the client
reaches its refresh timer and sends a new REQUEST?

That is to say, it all hinges on the "ddns updates made before ACK"
and "ddns updates made after ACK" language, and it's a little fuzzy
that on the next REQUEST you have hopefully completed the DDNS updates
elided from the previous one (rather than simply doing DDNS updates
all over again).

So I'd like to see that made explicit, because it could also be read
that servers choosing to delay DDNS updates will simply always return
255 values, and clients should just deal.

Perhaps both behaviours are acceptable, and it's the discretion of the
implementor?


Along the lines of wondering "How does the client get the real RCODE
when the server delays updates?" I'd had some ideas that may or may
not be worth anything:

1) The server MAY adjust the T1 and/or T2 timers of the offered lease
to exceed its DNS timeout intervals, as a technique of restarting the
DDNS update after a timeout.

2) The server SHOULD NOT transmit DDNS updates more than once without
first receiving another REQUEST from the client (this way, the failing
dns server will not be hindered by updates for clients that have gone
off-net).

3) The server MUST NOT begin DDNS updates in parallel for the same
lease (in the case where DDNS updates are done before ACK this is
implicit).


Should this draft define a behaviour when used in INFORM messages?


> > 6. Can client supply multiple FQDN options ?
> >          A client may not like the name assigned by server in OFFER
> >          but will take that and use its permanent name also.
> >          in this case I would like to see
> >          99.30.1.99.in-addr.arpa.        PTR visitor-99.md.ogud.com.
> >                                          PTR ralph.dhcp.org.
> >                                          PTR ns.dhcp.org.

Let's not go the multiple option path, this triggers concatenation
behaviour in servers.

I admit to not looking closely enough at the binary encoding of the
option to see if it is identical to that which is used in the
domain-search option (this was not the question I was trying to answer
when I read the draft).  If this is the case, then we may already be
able to  pass multiple names?

If the example included the encoded domain name, I probably would be
more clear on this.

But there is still only one flags field and one pair of RCODE fields.

So as Olafur hints, it should be explicit that the PTR RCODE applies
to all names, and the A RCODE applies to only the first evaluated
name from the encoded field (and any other names are up to the client
to negotiate).  The flags field indicating server updates again only
applies to the first evaluated name.

If the encoding is different, then we'll need yet another flags field
to indicate yet another encoding technique to support multiple names.

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

--TybLhxa8M7aNoW+V
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (FreeBSD)

iD8DBQFBwIahcXeLeWu2vmoRAghOAJ91ECQC6uvhBYoKdVR9jIZnV3V4eQCeNsS4
dBlw5+sFICd6QTLxYFiHiW0=
=foua
-----END PGP SIGNATURE-----

--TybLhxa8M7aNoW+V--


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

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

--===============0463552209==--



From dhcwg-bounces@ietf.org  Wed Dec 15 14:26:55 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00480
	for <dhcwg-web-archive@ietf.org>; Wed, 15 Dec 2004 14:26:55 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ceevq-0007NL-7O
	for dhcwg-web-archive@ietf.org; Wed, 15 Dec 2004 14:35:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ceec7-00057x-MH; Wed, 15 Dec 2004 14:15:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeeQ8-00036d-3h
	for dhcwg@megatron.ietf.org; Wed, 15 Dec 2004 14:02:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28694
	for <dhcwg@ietf.org>; Wed, 15 Dec 2004 14:02:42 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CeeYP-0006km-Fm
	for dhcwg@ietf.org; Wed, 15 Dec 2004 14:11:17 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 15 Dec 2004 11:06:16 -0800
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iBFJ25MI023710;
	Wed, 15 Dec 2004 11:02:05 -0800 (PST)
Received: from rdroms-w2k01.cisco.com ([161.44.65.124])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANS65797;
	Wed, 15 Dec 2004 14:02:09 -0500 (EST)
Message-Id: <4.3.2.7.2.20041215140100.02499e90@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 15 Dec 2004 14:02:07 -0500
To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] draft-vijay-dhc-dhcpv6-mcast-reconf-01.txt
In-Reply-To: <y7v6534hzqu.wl@ocean.jinmei.org>
References: <4.3.2.7.2.20041214173517.03d243f0@flask.cisco.com>
	<4.3.2.7.2.20041214173517.03d243f0@flask.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17

Jinmei-san - seems I should get back to reading and commenting on RFC 2462
and draft-ietf-ipv6-ra-mo-flags.  Thanks...

- Ralph

At 02:55 PM 12/15/2004 +0900, JINMEI Tatuya / 
=?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= wrote:
> >>>>> On Tue, 14 Dec 2004 17:42:07 -0500,
> >>>>> Ralph Droms <rdroms@cisco.com> said:
>
> > I need to be to be convinced of the need for this mechanism.  If the
> > network is
> > being reconfigured (e.g., the link is renumbered), presumably the 
> router must
> > be accessed to change its configuration.  Seems to me the router could be
> > caused to toggle the 'M'/'O' bits at the same time.  Why would a separate
> > message from the DHCP server be required?
>
>Perhaps this is not directly related to this document, but I'd like to
>note that toggling the M/O flags may not help here.  In particular,
>our current interpretation (as per RFC2462 and now
>draft-ietf-ipv6-ra-mo-flags) is that the change from ON to OFF doesn't
>have any effects on a running DHCPv6 process.  So, for example, we
>cannot expect re-invocation of the process by changing the flag from
>ON-to-OFF-to-ON when some network configuration changes.
>
>                                         JINMEI, Tatuya
>                                         Communication Platform Lab.
>                                         Corporate R&D Center, Toshiba Corp.
>                                         jinmei@isl.rdc.toshiba.co.jp

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


From dhcwg-bounces@ietf.org  Wed Dec 15 22:35:58 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00265
	for <dhcwg-web-archive@ietf.org>; Wed, 15 Dec 2004 22:35:58 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CemZC-0004WQ-2f
	for dhcwg-web-archive@ietf.org; Wed, 15 Dec 2004 22:44:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CemNr-00060h-Dp; Wed, 15 Dec 2004 22:32:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cem6J-00030n-5q; Wed, 15 Dec 2004 22:14:48 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22220;
	Wed, 15 Dec 2004 22:14:44 -0500 (EST)
Received: from rwcrmhc11.comcast.net ([204.127.198.35])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CemEd-00042o-QL; Wed, 15 Dec 2004 22:23:25 -0500
Received: from billmobile (c-24-6-192-177.client.comcast.net[24.6.192.177])
	by comcast.net (rwcrmhc11) with SMTP
	id <2004121603141201300g3ncfe>; Thu, 16 Dec 2004 03:14:12 +0000
From: "Bill Strahm" <bill@strahm.net>
To: <ipoverib@ietf.org>, "'Ralph Droms'" <rdroms@cisco.com>
Date: Wed, 15 Dec 2004 19:13:57 -0800
Message-ID: <001801c4e31d$48255760$1e02a8c0@BILLMOBILE>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 3d7f2f6612d734db849efa86ea692407
X-Mailman-Approved-At: Wed, 15 Dec 2004 22:32:53 -0500
Cc: dhcwg@ietf.org
Subject: [dhcwg] WG Last Call for DHCP draft
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bill@strahm.net
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="===============1536115961=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 9af087f15dbdd4c64ae6bbcdbc5b1d44

This is a multi-part message in MIME format.

--===============1536115961==
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0019_01C4E2DA.3A021760"

This is a multi-part message in MIME format.

------=_NextPart_000_0019_01C4E2DA.3A021760
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

It is time for WG last call for DHCP.  Normally I would ask for a 2 week
last call - but with a week for Christmas I would like to push the date
out to 7 Jan 2005.

 

I am CC'ing the WG Chair of the DHC WG so that we can arrange how to
handle a last call going through his working group.  If anyone needs
extra time please contact me with when you can complete your review.

 

As always comments/concerns to the WG mailing lists.

 

The draft in question is
http://www.ietf.org/internet-drafts/draft-ietf-ipoib-dhcp-over-infiniban
d-07.txt

 

Thank you

 

Bill Strahm

IPoIB WG Co-Chair


------=_NextPart_000_0019_01C4E2DA.3A021760
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DGenerator content=3D"Microsoft Word 10 (filtered)">

<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>It is time for WG last call for DHCP.&nbsp; Normally =
I would
ask for a 2 week last call &#8211; but with a week for Christmas I would =
like
to push the date out to </span></font><font size=3D2 face=3DArial><span
 style=3D'font-size:10.0pt;font-family:Arial'>7 Jan =
2005</span></font><font
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>I am CC&#8217;ing the WG Chair of the DHC WG so that =
we can
arrange how to handle a last call going through his working group.&nbsp; =
If
anyone needs extra time please contact me with when you can complete =
your
review.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>As always comments/concerns to the WG mailing =
lists.</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>The draft in question is <a
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-ipoib-dhcp-over-in=
finiband-07.txt">http://www.ietf.org/internet-drafts/draft-ietf-ipoib-dhc=
p-over-infiniband-07.txt</a></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Thank you</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Bill Strahm</span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>IPoIB WG Co-Chair</span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0019_01C4E2DA.3A021760--



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

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

--===============1536115961==--




From dhcwg-bounces@ietf.org  Wed Dec 15 23:05:53 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01968
	for <dhcwg-web-archive@ietf.org>; Wed, 15 Dec 2004 23:05:53 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cen2B-00057E-6n
	for dhcwg-web-archive@ietf.org; Wed, 15 Dec 2004 23:14:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CemsG-0002DB-IX; Wed, 15 Dec 2004 23:04:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cemk2-0001Dz-H4; Wed, 15 Dec 2004 22:55:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01231;
	Wed, 15 Dec 2004 22:55:46 -0500 (EST)
Received: from toccata.fugue.com ([204.152.186.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CemsN-0004uh-QZ; Wed, 15 Dec 2004 23:04:28 -0500
Received: from [10.33.43.94] (unknown [63.81.54.153])
	by toccata.fugue.com (Postfix) with ESMTP id B010422DD8A;
	Wed, 15 Dec 2004 20:39:31 -0700 (MST)
In-Reply-To: <001801c4e31d$48255760$1e02a8c0@BILLMOBILE>
References: <001801c4e31d$48255760$1e02a8c0@BILLMOBILE>
Mime-Version: 1.0 (Apple Message framework v682)
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <385BF31F-59E4-48AB-AD89-D24017953F60@fugue.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <mellon@fugue.com>
Subject: Re: [dhcwg] WG Last Call for DHCP draft
Date: Wed, 15 Dec 2004 20:55:34 -0700
To: Bill@strahm.net
X-Mailer: Apple Mail (2.682)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Content-Transfer-Encoding: 7bit
Cc: ipoverib@ietf.org, dhcwg@ietf.org, "'Ralph Droms'" <rdroms@cisco.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit

This draft uses a SHOULD to specify what data should be in the client 
identifier. This is in conflict with another draft that's in the 
process of working its way through to last call - 
draft-ietf-dhc-3315id-for-v4-??.txt. This is a bad thing - someone 
reading this spec will wonder which of the two specifications 
supersedes the other. I don't see any reason to specify the format of 
the client identifier in this draft - instead, refer the reader to 
draft-ietf-dhc-3315id-for-v4-??.txt and to RFC2132 for advice on how to 
format the client-identifier option.

Also, you have a reference to RFC1542. This is superseded by RFC2132, 
so you should refer to RFC2132 instead - it is a huge mistake for 
someone to read RFC1542 as advice on how to implement a DHCP client, 
and so this draft shouldn't imply that the reader ought to look at 
RFC1542 - he or she oughtn't.

Ralph, what's going on with draft-ietf-dhc-3315id-for-v4-??.txt? This 
is getting a little bit embarrassing... :'}


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


From dhcwg-bounces@ietf.org  Wed Dec 15 23:54:22 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04980
	for <dhcwg-web-archive@ietf.org>; Wed, 15 Dec 2004 23:54:22 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cenn6-0006Hx-FC
	for dhcwg-web-archive@ietf.org; Thu, 16 Dec 2004 00:03:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CenXc-0001U1-6c; Wed, 15 Dec 2004 23:47:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CenUq-0000nd-9j
	for dhcwg@megatron.ietf.org; Wed, 15 Dec 2004 23:44:12 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04188
	for <dhcwg@ietf.org>; Wed, 15 Dec 2004 23:44:08 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cend9-0005t8-8B
	for dhcwg@ietf.org; Wed, 15 Dec 2004 23:52:50 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 15 Dec 2004 20:49:25 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iBG4hOsv015024;
	Wed, 15 Dec 2004 20:43:25 -0800 (PST)
Received: from volzw2k (che-vpn-cluster-2-68.cisco.com [10.86.242.68])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANT02742;
	Wed, 15 Dec 2004 23:43:23 -0500 (EST)
From: "Bernie Volz" <volz@cisco.com>
To: "'David W. Hankins'" <David_Hankins@isc.org>, <dhcwg@ietf.org>
Subject: RE: [dhcwg] draft-ietf-dhc-fqdn-option to WG last call
Date: Wed, 15 Dec 2004 23:43:22 -0500
Organization: Cisco
Message-ID: <000501c4e329$c673f930$6901a8c0@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
In-Reply-To: <20041215184658.GD58434@isc.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
Content-Transfer-Encoding: quoted-printable
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Content-Transfer-Encoding: quoted-printable

The RCODE1 and RCODE2 fields are deprecated. The -08 draft will clearly
state this and say that the client SHOULD always set these to 0 and the
server SHOULD set them to 255. So, they will be meaningless. The =
"SHOULDs"
are there because older servers may return "real" values.

If a client needs to know whether DNS is up-to-date, it can just query =
the
DNS -- which, after all, is the authoritative source for this =
information.
Of course, it likely should go after the PTR to find out what name was
actually associated with the address.

---

I don't see much value in using this with INFORM. The DHCP server =
wouldn't
update the PTR since it didn't assign the address and thus may not have
sufficient authority to update the DNS. And, it is unlikely that the =
server
could do the A updates for similar reasons?

But, if there is WG interest in this support, it could be added. Though, =
I'm
really interested in finalizing this work as it has gone on for years. =
So,
I'd rather we clean up what's there and get it done ... If someone wants =
to
expand the work, great, but do it later and in a separate draft?

- Bernie


> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org]=20
> On Behalf Of David W. Hankins
> Sent: Wednesday, December 15, 2004 1:47 PM
> To: dhcwg@ietf.org
> Subject: Re: [dhcwg] draft-ietf-dhc-fqdn-option to WG last call
>=20
>=20
> On Tue, Dec 14, 2004 at 06:04:32PM -0500, Bernie Volz wrote:
> > I just got feedback from Olafur and want to revise the=20
> draft to clean=20
> > up and improve the language.
>=20
> So long as you're editing...
>=20
> After reading this draft I walked away with a feeling that=20
> the client/server interaction between FQDNs and delayed=20
> RCODEs (the special-case 255 values) was poorly defined.
>=20
> I think there's an implicit behaviour in the draft that every=20
> REQUEST contains an FQDN option.  So in the case where the=20
> server sends RCODEs with 255 values, it is expected to retain=20
> the actual RCODEs whenever they should arrive, and deliver=20
> those in the next ACK when the client reaches its refresh=20
> timer and sends a new REQUEST?
>=20
> That is to say, it all hinges on the "ddns updates made=20
> before ACK" and "ddns updates made after ACK" language, and=20
> it's a little fuzzy that on the next REQUEST you have=20
> hopefully completed the DDNS updates elided from the previous=20
> one (rather than simply doing DDNS updates all over again).
>=20
> So I'd like to see that made explicit, because it could also=20
> be read that servers choosing to delay DDNS updates will=20
> simply always return 255 values, and clients should just deal.
>=20
> Perhaps both behaviours are acceptable, and it's the=20
> discretion of the implementor?
>=20
>=20
> Along the lines of wondering "How does the client get the=20
> real RCODE when the server delays updates?" I'd had some=20
> ideas that may or may not be worth anything:
>=20
> 1) The server MAY adjust the T1 and/or T2 timers of the=20
> offered lease to exceed its DNS timeout intervals, as a=20
> technique of restarting the DDNS update after a timeout.
>=20
> 2) The server SHOULD NOT transmit DDNS updates more than once=20
> without first receiving another REQUEST from the client (this=20
> way, the failing dns server will not be hindered by updates=20
> for clients that have gone off-net).
>=20
> 3) The server MUST NOT begin DDNS updates in parallel for the=20
> same lease (in the case where DDNS updates are done before=20
> ACK this is implicit).
>=20
>=20
> Should this draft define a behaviour when used in INFORM messages?
>=20
>=20
> > > 6. Can client supply multiple FQDN options ?
> > >          A client may not like the name assigned by=20
> server in OFFER
> > >          but will take that and use its permanent name also.
> > >          in this case I would like to see
> > >          99.30.1.99.in-addr.arpa.        PTR=20
> visitor-99.md.ogud.com.
> > >                                          PTR ralph.dhcp.org.
> > >                                          PTR ns.dhcp.org.
>=20
> Let's not go the multiple option path, this triggers=20
> concatenation behaviour in servers.
>=20
> I admit to not looking closely enough at the binary encoding=20
> of the option to see if it is identical to that which is used=20
> in the domain-search option (this was not the question I was=20
> trying to answer when I read the draft).  If this is the=20
> case, then we may already be able to  pass multiple names?
>=20
> If the example included the encoded domain name, I probably=20
> would be more clear on this.
>=20
> But there is still only one flags field and one pair of RCODE fields.
>=20
> So as Olafur hints, it should be explicit that the PTR RCODE=20
> applies to all names, and the A RCODE applies to only the=20
> first evaluated name from the encoded field (and any other=20
> names are up to the client to negotiate).  The flags field=20
> indicating server updates again only applies to the first=20
> evaluated name.
>=20
> If the encoding is different, then we'll need yet another=20
> flags field to indicate yet another encoding technique to=20
> support multiple names.
>=20
> --=20
> David W. Hankins		"If you don't do it right the=20
> first time,
> Software Engineer			you'll just have to do=20
> it again."
> Internet Systems Consortium, Inc.		-- Jack T. Hankins
>=20

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


From dhcwg-bounces@ietf.org  Thu Dec 16 07:29:54 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18015
	for <dhcwg-web-archive@ietf.org>; Thu, 16 Dec 2004 07:29:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ceutz-0007oC-0m
	for dhcwg-web-archive@ietf.org; Thu, 16 Dec 2004 07:38:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ceuhl-0006jT-WF; Thu, 16 Dec 2004 07:26:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CeuYf-0004xh-Uv
	for dhcwg@megatron.ietf.org; Thu, 16 Dec 2004 07:16:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA17215
	for <dhcwg@ietf.org>; Thu, 16 Dec 2004 07:16:34 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ceuh5-0007UF-Fd
	for dhcwg@ietf.org; Thu, 16 Dec 2004 07:25:20 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 16 Dec 2004 04:22:06 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iBGCFwMI022823
	for <dhcwg@ietf.org>; Thu, 16 Dec 2004 04:15:59 -0800 (PST)
Received: from rdroms-w2k01.cisco.com (sjc-vpn2-524.cisco.com [10.21.114.12])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANT13863;
	Thu, 16 Dec 2004 07:16:01 -0500 (EST)
Message-Id: <4.3.2.7.2.20041216071507.01f91220@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 16 Dec 2004 07:15:57 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: [dhcwg] dhc WG last call on draft-ietf-dhc-3315id-for-v4
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab

This message announces a WG last call on "Node-Specific Client
Identifiers for DHCPv4" <draft-ietf-dhc-3315id-for-v4-03>.  The last
call will conclude at 1700EST on 2005-01-07.

Please respond to this WG last call.  If you support acceptance of the
document without change, respond with a simple acknowledgment, so that
support for the document can be assessed.

"Node-Specific Client Identifiers for DHCPv4" specifies the format
that is to be used for encoding DHCPv4 [RFC2131 and RFC2132] client
identifiers, so that those identifiers will be interchangeable with
identifiers used in the DHCPv6 protocol [RFC3315].  This draft is
available as
http://www.ietf.org/internet-drafts/draft-ietf-dhc-3315id-for-v4-03.txt


- Ralph Droms 

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


From dhcwg-bounces@ietf.org  Fri Dec 17 04:18:05 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26926
	for <dhcwg-web-archive@ietf.org>; Fri, 17 Dec 2004 04:18:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CfEO4-0005re-P4
	for dhcwg-web-archive@ietf.org; Fri, 17 Dec 2004 04:27:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfEDc-0004Qc-90; Fri, 17 Dec 2004 04:16:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfEAY-000432-KM
	for dhcwg@megatron.ietf.org; Fri, 17 Dec 2004 04:13:02 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26676
	for <dhcwg@ietf.org>; Fri, 17 Dec 2004 04:13:01 -0500 (EST)
Received: from smtp.inet.fi ([192.89.123.192])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfEJA-0005kI-Cr
	for dhcwg@ietf.org; Fri, 17 Dec 2004 04:21:56 -0500
Received: from [194.142.21.49] (gingerale.mit.sonera.com [194.142.21.49])
	by smtp.inet.fi (Postfix) with ESMTP
	id DF017EE10; Fri, 17 Dec 2004 11:13:00 +0200 (EET)
Message-ID: <41C2A310.2010509@teliasonera.com>
Date: Fri, 17 Dec 2004 11:12:48 +0200
From: Jyrki Soini <jyrki.soini@teliasonera.com>
Organization: TeliaSonera Finland
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dhcwg@ietf.org, volz@cisco.com
X-Enigmail-Version: 0.89.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: multipart/mixed; boundary="------------040308010301030605060906"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-fqdn-00.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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0

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

I have some questions and comments on draft-ietf-dhc-dhcpv6-fqdn-00.txt:

Introduction needs a paragraph stating that this option is only usable
with stateful dhcpv6 and reasoning behind the fact: e.g. dhcp server 
needs to maintain state per client for instance to remove stale dns RRs.
However, I suspect stateful DHCPv6 will not be the mechanism used to
assign addresses for hosts but stateless autoconfiguration will be used
instead. Perhaphs introduction could describe how the mechanism can
be used in that scenario?

Section 4.1 needs to be rewritten. At least I had to read it three
times to understand the usage of flag bits, that after all is not
that complicated.

Section 4.2: "Eventually, the IETF IDN Working Group is expected.."
IDN wg has since concluded. Anyhow, shouldn't option have domain-name
encoding in accordance with rfc3315 section 8 i.e. rfc1035 section 3.1?
--
Jyrki Soini

--------------040308010301030605060906
Content-Type: text/x-vcard; charset=utf-8;
 name="jyrki.soini.vcf"
Content-Disposition: attachment;
 filename="jyrki.soini.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard
fn:Jyrki Soini
n:Soini;Jyrki
org:Technology and Software Development;Emerging Technologies and Innobations
adr:P.O.Box 935;;TeliaSonera Finland;Helsiniki;;FI-00051;Finland
email;internet:jyrki.soini@teliasonera.com
title:Chief Network Architect
tel;work:+358 2040 64725
tel;fax:+358-2040-54081
tel;cell:+358 40 722 1119
x-mozilla-html:FALSE
version:2.1
end:vcard


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

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

--------------040308010301030605060906--



From dhcwg-bounces@ietf.org  Fri Dec 17 06:31:34 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06936
	for <dhcwg-web-archive@ietf.org>; Fri, 17 Dec 2004 06:31:34 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CfGTG-0000w9-S7
	for dhcwg-web-archive@ietf.org; Fri, 17 Dec 2004 06:40:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfGJJ-0005bJ-C6; Fri, 17 Dec 2004 06:30:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfGHq-0005Iq-QX
	for dhcwg@megatron.ietf.org; Fri, 17 Dec 2004 06:28:42 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA06613
	for <dhcwg@ietf.org>; Fri, 17 Dec 2004 06:28:40 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CfGQS-0000oL-OI
	for dhcwg@ietf.org; Fri, 17 Dec 2004 06:37:38 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 17 Dec 2004 03:32:33 -0800
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iBHBS0MI023133
	for <dhcwg@ietf.org>; Fri, 17 Dec 2004 03:28:01 -0800 (PST)
Received: from rdroms-w2k01.cisco.com (sjc-vpn4-262.cisco.com [10.21.81.6])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANT99233;
	Fri, 17 Dec 2004 06:28:07 -0500 (EST)
Message-Id: <4.3.2.7.2.20041217062343.02084e78@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 17 Dec 2004 06:28:04 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Subject: [dhcwg] Two new dhc WG work items
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89

The dhc WG has agreed to take on the following drafts as work items:

draft-madanapalli-dhcpv6-anycast-00.txt
draft-droms-dhc-v6-relayopt-00.txt

- Ralph

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


From dhcwg-bounces@ietf.org  Fri Dec 17 07:20:39 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10737
	for <dhcwg-web-archive@ietf.org>; Fri, 17 Dec 2004 07:20:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CfHEn-0002ID-5u
	for dhcwg-web-archive@ietf.org; Fri, 17 Dec 2004 07:29:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfH4f-0005xQ-Es; Fri, 17 Dec 2004 07:19:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfH1H-0005OC-3t
	for dhcwg@megatron.ietf.org; Fri, 17 Dec 2004 07:15:39 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10276
	for <dhcwg@ietf.org>; Fri, 17 Dec 2004 07:15:36 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CfH9t-00028X-Ft
	for dhcwg@ietf.org; Fri, 17 Dec 2004 07:24:34 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-2.cisco.com with ESMTP; 17 Dec 2004 04:19:30 -0800
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iBHCF4sv006506
	for <dhcwg@ietf.org>; Fri, 17 Dec 2004 04:15:04 -0800 (PST)
Received: from rdroms-w2k01.cisco.com (sjc-vpn4-262.cisco.com [10.21.81.6])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANU00378;
	Fri, 17 Dec 2004 07:15:02 -0500 (EST)
Message-Id: <4.3.2.7.2.20041217065355.029bac40@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 17 Dec 2004 07:10:51 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: [dhcwg] dhc WG last call on draft-ietf-dhc-vendor-suboption
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906

This message announces a WG last call on "Vendor-Specific Information
Suboption for the DHCP Relay Agent Option"
<draft-ietf-dhc-vendor-suboption-00.txt>.  The last call will
conclude at 1700 EST, 2005-01-07.

Please respond to this WG last call.  If you support acceptance of the
document without change, respond with a simple acknowledgment, so that
support for the document can be assessed.

"Vendor-Specific Information Suboption for the DHCP Relay Agent Option"
defines a new Vendor-Specific Information suboption for the Dynamic Host
Configuration Protocol's (DHCP) relay agent information
option. The suboption allows a DHCP relay agent to include
vendor-specific information in DHCP messages it forwards, as
configured by its administrator.  This draft is available as
http://www.ietf.org/internet-drafts/draft-ietf-dhc-vendor-suboption-00.txt

- Ralph Droms

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


From dhcwg-bounces@ietf.org  Fri Dec 17 07:22:28 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10901
	for <dhcwg-web-archive@ietf.org>; Fri, 17 Dec 2004 07:22:28 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CfHGY-0002Mc-2S
	for dhcwg-web-archive@ietf.org; Fri, 17 Dec 2004 07:31:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfH4f-0005xi-SH; Fri, 17 Dec 2004 07:19:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfH1H-0005OH-MD
	for dhcwg@megatron.ietf.org; Fri, 17 Dec 2004 07:15:39 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10283
	for <dhcwg@ietf.org>; Fri, 17 Dec 2004 07:15:37 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CfH9v-00028X-0c
	for dhcwg@ietf.org; Fri, 17 Dec 2004 07:24:35 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 17 Dec 2004 04:19:30 -0800
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iBHCF1o9023117
	for <dhcwg@ietf.org>; Fri, 17 Dec 2004 04:15:01 -0800 (PST)
Received: from rdroms-w2k01.cisco.com (sjc-vpn4-262.cisco.com [10.21.81.6])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANU00377;
	Fri, 17 Dec 2004 07:15:01 -0500 (EST)
Message-Id: <4.3.2.7.2.20041217071419.029d3930@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 17 Dec 2004 07:14:58 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: [dhcwg] dhc WG last call on draft-ietf-dhc-lifetime
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab

This message announces a WG last call on "Information Refresh Time
Option for DHCPv6" <draft-ietf-dhc-lifetime-02.txt>.  The last call
will conclude at 1700EST, 2005-01-07.

Please respond to this WG last call.  If you support acceptance of the
document without change, respond with a simple acknowledgment, so that
support for the document can be assessed.

"Information Refresh Time Option for DHCPv6" describes a DHCPv6 option
for specifying an upper bound for how long a client should wait before
refreshing information retrieved from DHCPv6.  It is used with
stateless DHCPv6 as there are no addresses or other entities with
lifetimes that can tell the client when to contact the DHCPv6 server
to refresh its configuration..  This draft is available as
http://www.ietf.org/internet-drafts/draft-ietf-dhc-lifetime-02.txt

- Ralph Droms 

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


From dhcwg-bounces@ietf.org  Fri Dec 17 07:36:51 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12316
	for <dhcwg-web-archive@ietf.org>; Fri, 17 Dec 2004 07:36:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CfHUQ-0002qP-Qs
	for dhcwg-web-archive@ietf.org; Fri, 17 Dec 2004 07:45:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfHGR-0008E9-70; Fri, 17 Dec 2004 07:31:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfHAp-00075q-VQ
	for dhcwg@megatron.ietf.org; Fri, 17 Dec 2004 07:25:32 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11136
	for <dhcwg@ietf.org>; Fri, 17 Dec 2004 07:25:30 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CfHJS-0002QW-7G
	for dhcwg@ietf.org; Fri, 17 Dec 2004 07:34:27 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 17 Dec 2004 04:31:10 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iBHCOvsv009391
	for <dhcwg@ietf.org>; Fri, 17 Dec 2004 04:24:57 -0800 (PST)
Received: from rdroms-w2k01.cisco.com (sjc-vpn4-262.cisco.com [10.21.81.6])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANU00742;
	Fri, 17 Dec 2004 07:24:55 -0500 (EST)
Message-Id: <4.3.2.7.2.20041217072421.029bac40@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 17 Dec 2004 07:24:53 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Subject: [dhcwg] dhc WG last call on draft-ietf-dhc-dhcpv6-fqdn
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32

This message announces a WG last call on "The DHCPv6 Client FQDN Option"
<draft-ietf-dhc-dhcpv6-fqdn-00.txt>.  The last call will conclude at
1700EST, 2005-01-07.

Please respond to this WG last call.  If you support acceptance of the
document without change, respond with a simple acknowledgment, so that
support for the document can be assessed.

"The DHCPv6 Client FQDN Option" specifies a new DHCPv6, option which
can be used to exchange information about a DHCPv6 client's
fully-qualified domain name and about responsibility for updating DNS
RRs related to the client's address assignments..  This draft is
available as
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-fqdn-00.txt

Note: the comment posted to the dhc WG mailing list by Jyrki Soini on
2004-12-17 about this draft will be considered as a "last call"
comment.

- Ralph Droms 

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


From dhcwg-bounces@ietf.org  Fri Dec 17 10:35:51 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28590
	for <dhcwg-web-archive@ietf.org>; Fri, 17 Dec 2004 10:35:51 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CfKHi-0008Vf-7X
	for dhcwg-web-archive@ietf.org; Fri, 17 Dec 2004 10:44:50 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfJvv-00026l-Ij; Fri, 17 Dec 2004 10:22:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfJqB-0000Qb-8c
	for dhcwg@megatron.ietf.org; Fri, 17 Dec 2004 10:16:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26613
	for <dhcwg@ietf.org>; Fri, 17 Dec 2004 10:16:20 -0500 (EST)
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.33)
	id 1CfJyn-0007sG-B5
	for dhcwg@ietf.org; Fri, 17 Dec 2004 10:25:19 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 17 Dec 2004 08:22:55 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iBHFFfoB016033;
	Fri, 17 Dec 2004 07:15:43 -0800 (PST)
Received: from volzw2k (che-vpn-cluster-2-68.cisco.com [10.86.242.68])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANU10162;
	Fri, 17 Dec 2004 10:14:31 -0500 (EST)
From: "Bernie Volz" <volz@cisco.com>
To: "'Jyrki Soini'" <jyrki.soini@teliasonera.com>, <dhcwg@ietf.org>,
        <rdroms@cisco.com>
Subject: RE: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-fqdn-00.txt
Date: Fri, 17 Dec 2004 10:14:31 -0500
Organization: Cisco
Message-ID: <001101c4e44b$1be243f0$6901a8c0@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-reply-to: <41C2A310.2010509@teliasonera.com>
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Content-Transfer-Encoding: quoted-printable
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Content-Transfer-Encoding: quoted-printable

Urgh!

As Olafur gave me plenty of good comments on the DHCPv4 Client FQDN =
option,
most of these apply to the DHCPv6 version and I should have requested =
that
Ralph not start the WG Last-Call on the DHCPv6 draft as well.

So, let's consider the WG Last Call stopped and once I get the DHCPv4 =
Client
FQDN option draft revised, I'll apply similar edits to the DHCPv6 one =
and
re-submit it as well.

Here's what I'm proposing for the revised DHCPv4 Client FQDN option
regarding the Flags bits. This, except for the "E" bit and DHCPv4 =
message
names, would be used for the DHCPv6 option. Let me know if you think =
this is
better.

4.1  The Flags Field

   The Format of the Flags Field is:

        0 1 2 3 4 5 6 7
       +-+-+-+-+-+-+-+-+
       |  MBZ  |N|E|O|S|
       +-+-+-+-+-+-+-+-+


   When a DHCP client sends the Client FQDN option in its DHCPDISCOVER
   and/or DHCPREQUEST messages, the client:

   o  Sets (to 1) the "S" bit if it does not desire to perform any DNS
      updates and desires the DHCP server to perform FQDN to IP (the A
      RR) DNS updates on it behalf.  If the "S" bit is clear, the client
      indicates that it intends to maintain its own FQDN to IP mapping
      update.
   o  Clears (sets to 0) the "O" bit.  The "O" bit is only meaningful in
      Client FQDN options received from a server.
   o  Sets the "E" bit to indicate that the Domain Name field is in
      DNS-style binary encoding, without compression, as described in
      RFC 1035 [3].  A client which sends the Client FQDN option SHOULD
      use this encoding.  Server implementers SHOULD note that earlier
      draft versions of this specification permitted an ASCII encoding
      of the domain name and this encoding MUST be used if the "E" bit
      is clear.  Clients which implemented this encoding were deployed
      before this specification was completed.  Server implementers
      which need to support these clients need to see the section on the
      deprecated ASCII encoding (Section 4.3.1).
   o  Clears the "N" bit unless the client desires the server not to
      perform any DNS updates on its behalf.

   When a DHCP client receives the Client FQDN option in a DHCPOFFER
   and/or DHCPACK message:

   o  If the "S" bit is set, the server has taken responsibility for the
      A RR updates and the client SHOULD NOT perform these DNS updates.
      If the "S" bit is clear, the client MAY perform the A RR updates.
   o  If the "O" bit is set, the server has overridden the client's
      request for the server not to update the A RR.  The "O" bit MUST
      only be set if the "S" bit is also set.
   o  The "E" bit indicates the encoding of the Domain Name field, and
      the bit MUST match what the client sent.
   o  If the "N" bit is set and the client had set the "N" bit in what
      it sent to the server, the client SHOULD assume the server honored
      the client's request and will not perform any DNS updates.  If a
      client has set the "N" bit but its server does not, the client
      SHOULD conclude that the server was not configured to honor the
      client's request and that the server MAY attempt to perform DNS
      updates on the client's behalf.

   The remaining bits in the Flags field are reserved for future
   assignment.  DHCP clients and servers which send the Client FQDN
   option MUST clear the MBZ bits, and they MUST ignore these bits.

- Bernie

> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org]=20
> On Behalf Of Jyrki Soini
> Sent: Friday, December 17, 2004 4:13 AM
> To: dhcwg@ietf.org; volz@cisco.com
> Subject: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-fqdn-00.txt
>=20
>=20
> I have some questions and comments on=20
> draft-ietf-dhc-dhcpv6-fqdn-00.txt:
>=20
> Introduction needs a paragraph stating that this option is=20
> only usable with stateful dhcpv6 and reasoning behind the=20
> fact: e.g. dhcp server=20
> needs to maintain state per client for instance to remove=20
> stale dns RRs. However, I suspect stateful DHCPv6 will not be=20
> the mechanism used to assign addresses for hosts but=20
> stateless autoconfiguration will be used instead. Perhaphs=20
> introduction could describe how the mechanism can be used in=20
> that scenario?
>=20
> Section 4.1 needs to be rewritten. At least I had to read it=20
> three times to understand the usage of flag bits, that after=20
> all is not that complicated.
>=20
> Section 4.2: "Eventually, the IETF IDN Working Group is=20
> expected.." IDN wg has since concluded. Anyhow, shouldn't=20
> option have domain-name encoding in accordance with rfc3315=20
> section 8 i.e. rfc1035 section 3.1?
> --
> Jyrki Soini
>=20

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


From dhcwg-bounces@ietf.org  Fri Dec 17 10:38:12 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28871
	for <dhcwg-web-archive@ietf.org>; Fri, 17 Dec 2004 10:38:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CfKJy-00007i-Ah
	for dhcwg-web-archive@ietf.org; Fri, 17 Dec 2004 10:47:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfK8D-00061U-CD; Fri, 17 Dec 2004 10:35:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfJvn-00023s-RJ
	for dhcwg@megatron.ietf.org; Fri, 17 Dec 2004 10:22:11 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27181
	for <dhcwg@ietf.org>; Fri, 17 Dec 2004 10:22:10 -0500 (EST)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfK4R-00084l-Qt
	for dhcwg@ietf.org; Fri, 17 Dec 2004 10:31:09 -0500
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by rtp-iport-1.cisco.com with ESMTP; 17 Dec 2004 10:29:53 -0500
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iBHFLaHS006090; 
	Fri, 17 Dec 2004 10:21:37 -0500 (EST)
Received: from volzw2k (che-vpn-cluster-2-68.cisco.com [10.86.242.68])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANU10835;
	Fri, 17 Dec 2004 10:21:36 -0500 (EST)
From: "Bernie Volz" <volz@cisco.com>
To: "'Jyrki Soini'" <jyrki.soini@teliasonera.com>, <dhcwg@ietf.org>
Subject: RE: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-fqdn-00.txt
Date: Fri, 17 Dec 2004 10:21:36 -0500
Organization: Cisco
Message-ID: <001201c4e44c$19570fc0$6901a8c0@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-reply-to: <41C2A310.2010509@teliasonera.com>
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: quoted-printable
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: quoted-printable

Oh, the encoding is the same. I just thought it easier to reference the
source rather than having to go through two RFCs (3315 -> 1035). But =
I'll
just reference RFC 3315 instead.

The IDN issue is already in the list of issues Olafur provided. Please =
see
my email titled "RE: [dhcwg] draft-ietf-dhc-fqdn-option to WG last call" =
on
12/14 to the DHC WG mailing list that listed Olafur's comments. Consider =
the
bulk of these to apply to the DHCPv6 Client FQDN option as well.

I'm also moving the DHCPv6 Client FQDN option to the Client message (ie,
removing it from being encapsulated in the IA_NA option). This should
simplify processing. If a client wants to use different names with =
different
bindings, it can just issue separate transactions (rather than putting
multiple bindings in a single transaction). Note that it is of course up =
the
server as to whether it allows multiple names or not in this case.

- Bernie

> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org]=20
> On Behalf Of Jyrki Soini
> Sent: Friday, December 17, 2004 4:13 AM
> To: dhcwg@ietf.org; volz@cisco.com
> Subject: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-fqdn-00.txt
>=20
>=20
> I have some questions and comments on=20
> draft-ietf-dhc-dhcpv6-fqdn-00.txt:
>=20
> Introduction needs a paragraph stating that this option is=20
> only usable with stateful dhcpv6 and reasoning behind the=20
> fact: e.g. dhcp server=20
> needs to maintain state per client for instance to remove=20
> stale dns RRs. However, I suspect stateful DHCPv6 will not be=20
> the mechanism used to assign addresses for hosts but=20
> stateless autoconfiguration will be used instead. Perhaphs=20
> introduction could describe how the mechanism can be used in=20
> that scenario?
>=20
> Section 4.1 needs to be rewritten. At least I had to read it=20
> three times to understand the usage of flag bits, that after=20
> all is not that complicated.
>=20
> Section 4.2: "Eventually, the IETF IDN Working Group is=20
> expected.." IDN wg has since concluded. Anyhow, shouldn't=20
> option have domain-name encoding in accordance with rfc3315=20
> section 8 i.e. rfc1035 section 3.1?
> --
> Jyrki Soini
>=20

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


From dhcwg-bounces@ietf.org  Fri Dec 17 13:00:36 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15864
	for <dhcwg-web-archive@ietf.org>; Fri, 17 Dec 2004 13:00:36 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CfMXp-0005qv-CQ
	for dhcwg-web-archive@ietf.org; Fri, 17 Dec 2004 13:09:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfMBt-0002Wy-Qr; Fri, 17 Dec 2004 12:46:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfM7y-00019M-Kd
	for dhcwg@megatron.ietf.org; Fri, 17 Dec 2004 12:42:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13925
	for <dhcwg@ietf.org>; Fri, 17 Dec 2004 12:42:52 -0500 (EST)
Received: from smtp.inet.fi ([192.89.123.192])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfMGe-0005C1-Gk
	for dhcwg@ietf.org; Fri, 17 Dec 2004 12:51:53 -0500
Received: from [194.142.21.49] (gingerale.mit.sonera.com [194.142.21.49])
	by smtp.inet.fi (Postfix) with ESMTP
	id 01AB45C932; Fri, 17 Dec 2004 19:42:47 +0200 (EET)
Message-ID: <41C31A66.4010107@teliasonera.com>
Date: Fri, 17 Dec 2004 19:41:58 +0200
From: Jyrki Soini <jyrki.soini@teliasonera.com>
Organization: TeliaSonera Finland
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-fqdn-00.txt
References: <001101c4e44b$1be243f0$6901a8c0@amer.cisco.com>
In-Reply-To: <001101c4e44b$1be243f0$6901a8c0@amer.cisco.com>
X-Enigmail-Version: 0.89.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: multipart/mixed; boundary="------------040107050206080402060809"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290
Cc: dhcwg@ietf.org, rdroms@cisco.com
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8

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

Bernie Volz wrote:
> Urgh!
> 
> As Olafur gave me plenty of good comments on the DHCPv4 Client FQDN option,
> most of these apply to the DHCPv6 version and I should have requested that
> Ralph not start the WG Last-Call on the DHCPv6 draft as well.
> 
> So, let's consider the WG Last Call stopped and once I get the DHCPv4 Client
> FQDN option draft revised, I'll apply similar edits to the DHCPv6 one and
> re-submit it as well.
> 
> Here's what I'm proposing for the revised DHCPv4 Client FQDN option
> regarding the Flags bits. This, except for the "E" bit and DHCPv4 message
> names, would be used for the DHCPv6 option. Let me know if you think this is
> better.
> 
> 4.1  The Flags Field
> 
>    The Format of the Flags Field is:
> 
>         0 1 2 3 4 5 6 7
>        +-+-+-+-+-+-+-+-+
>        |  MBZ  |N|E|O|S|
>        +-+-+-+-+-+-+-+-+
> 
> 
>    When a DHCP client sends the Client FQDN option in its DHCPDISCOVER
>    and/or DHCPREQUEST messages, the client:
> 
>    o  Sets (to 1) the "S" bit if it does not desire to perform any DNS
>       updates and desires the DHCP server to perform FQDN to IP (the A
>       RR) DNS updates on it behalf.  If the "S" bit is clear, the client
>       indicates that it intends to maintain its own FQDN to IP mapping
>       update.

I would remove "does not desire to perform any DNS updates and", that 
would make the sentence clearer.

s/it behalf/its behalf/

>    o  Clears (sets to 0) the "O" bit.  The "O" bit is only meaningful in
>       Client FQDN options received from a server.

o  Always clears...?

>    o  Sets the "E" bit to indicate that the Domain Name field is in
>       DNS-style binary encoding, without compression, as described in
>       RFC 1035 [3].  A client which sends the Client FQDN option SHOULD
>       use this encoding.  Server implementers SHOULD note that earlier
>       draft versions of this specification permitted an ASCII encoding
>       of the domain name and this encoding MUST be used if the "E" bit
>       is clear.  Clients which implemented this encoding were deployed
>       before this specification was completed.  Server implementers
>       which need to support these clients need to see the section on the
>       deprecated ASCII encoding (Section 4.3.1).
>    o  Clears the "N" bit unless the client desires the server not to
>       perform any DNS updates on its behalf.

How about:
o Clears the "N" bit if the client desires the server perform DNS 
updates on its behalf.

> 
>    When a DHCP client receives the Client FQDN option in a DHCPOFFER
>    and/or DHCPACK message:
> 
>    o  If the "S" bit is set, the server has taken responsibility for the
>       A RR updates and the client SHOULD NOT perform these DNS updates.
>       If the "S" bit is clear, the client MAY perform the A RR updates.
>    o  If the "O" bit is set, the server has overridden the client's
>       request for the server not to update the A RR.  The "O" bit MUST
>       only be set if the "S" bit is also set.
>    o  The "E" bit indicates the encoding of the Domain Name field, and
>       the bit MUST match what the client sent.
>    o  If the "N" bit is set and the client had set the "N" bit in what
>       it sent to the server, the client SHOULD assume the server honored
>       the client's request and will not perform any DNS updates.  If a
>       client has set the "N" bit but its server does not, the client
>       SHOULD conclude that the server was not configured to honor the
>       client's request and that the server MAY attempt to perform DNS
>       updates on the client's behalf.
> 
>    The remaining bits in the Flags field are reserved for future
>    assignment.  DHCP clients and servers which send the Client FQDN
>    option MUST clear the MBZ bits, and they MUST ignore these bits.
> 
> - Bernie
> 

Yes, this is better than before.

Still I wonder if there is reason why O bit tells that server has 
overriden client S bit setting, but N bit is handled differently?
Could flag semantics be:
S=0 client updates or does not want FQDN update at all, S=1 Server 
updates FQDN
O=0 server did as client requested, O=1 server did override request
N=0 client does PTR update or does not want it to be updated,
N=1 server updates PTR
E=1 use domain binary encoding, E=0 use deprecated ascii encoding
--
Jyrki

--------------040107050206080402060809
Content-Type: text/x-vcard; charset=utf-8;
 name="jyrki.soini.vcf"
Content-Disposition: attachment;
 filename="jyrki.soini.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard
fn:Jyrki Soini
n:Soini;Jyrki
org:Technology and Software Development;Emerging Technologies and Innobations
adr:P.O.Box 935;;TeliaSonera Finland;Helsiniki;;FI-00051;Finland
email;internet:jyrki.soini@teliasonera.com
title:Chief Network Architect
tel;work:+358 2040 64725
tel;fax:+358-2040-54081
tel;cell:+358 40 722 1119
x-mozilla-html:FALSE
version:2.1
end:vcard


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

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

--------------040107050206080402060809--



From dhcwg-bounces@ietf.org  Fri Dec 17 13:36:04 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18529
	for <dhcwg-web-archive@ietf.org>; Fri, 17 Dec 2004 13:36:04 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CfN69-0006u1-W8
	for dhcwg-web-archive@ietf.org; Fri, 17 Dec 2004 13:45:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfMpA-0004hk-Oa; Fri, 17 Dec 2004 13:27:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfMgb-0002U4-4l
	for dhcwg@megatron.ietf.org; Fri, 17 Dec 2004 13:18:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17234
	for <dhcwg@ietf.org>; Fri, 17 Dec 2004 13:18:38 -0500 (EST)
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfMpH-0006Oi-Ce
	for dhcwg@ietf.org; Fri, 17 Dec 2004 13:27:39 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-5.cisco.com with ESMTP; 17 Dec 2004 10:19:03 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iBHIHwMK027209;
	Fri, 17 Dec 2004 10:18:01 -0800 (PST)
Received: from volzw2k (che-vpn-cluster-2-68.cisco.com [10.86.242.68])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANU26774;
	Fri, 17 Dec 2004 13:18:04 -0500 (EST)
From: "Bernie Volz" <volz@cisco.com>
To: "'Jyrki Soini'" <jyrki.soini@teliasonera.com>
Subject: RE: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-fqdn-00.txt
Date: Fri, 17 Dec 2004 13:18:04 -0500
Organization: Cisco
Message-ID: <002a01c4e464$c0304d30$6901a8c0@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-reply-to: <41C31A66.4010107@teliasonera.com>
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1449ead51a2ff026dcb23465f5379250
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org, rdroms@cisco.com
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48
Content-Transfer-Encoding: 7bit

Comments below, prefixed by BV>.

- Bernie

> -----Original Message-----
> From: Jyrki Soini [mailto:jyrki.soini@teliasonera.com] 
> Sent: Friday, December 17, 2004 12:42 PM
> To: Bernie Volz
> Cc: dhcwg@ietf.org; rdroms@cisco.com
> Subject: Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-fqdn-00.txt
> 
> 
> Bernie Volz wrote:
> > Urgh!
> > 
> > As Olafur gave me plenty of good comments on the DHCPv4 Client FQDN 
> > option, most of these apply to the DHCPv6 version and I should have 
> > requested that Ralph not start the WG Last-Call on the 
> DHCPv6 draft as 
> > well.
> > 
> > So, let's consider the WG Last Call stopped and once I get 
> the DHCPv4 
> > Client FQDN option draft revised, I'll apply similar edits to the 
> > DHCPv6 one and re-submit it as well.
> > 
> > Here's what I'm proposing for the revised DHCPv4 Client FQDN option 
> > regarding the Flags bits. This, except for the "E" bit and DHCPv4 
> > message names, would be used for the DHCPv6 option. Let me 
> know if you 
> > think this is better.
> > 
> > 4.1  The Flags Field
> > 
> >    The Format of the Flags Field is:
> > 
> >         0 1 2 3 4 5 6 7
> >        +-+-+-+-+-+-+-+-+
> >        |  MBZ  |N|E|O|S|
> >        +-+-+-+-+-+-+-+-+
> > 
> > 
> >    When a DHCP client sends the Client FQDN option in its 
> DHCPDISCOVER
> >    and/or DHCPREQUEST messages, the client:
> > 
> >    o  Sets (to 1) the "S" bit if it does not desire to 
> perform any DNS
> >       updates and desires the DHCP server to perform FQDN 
> to IP (the A
> >       RR) DNS updates on it behalf.  If the "S" bit is 
> clear, the client
> >       indicates that it intends to maintain its own FQDN to 
> IP mapping
> >       update.
> 
> I would remove "does not desire to perform any DNS updates and", that 
> would make the sentence clearer.
> 
> s/it behalf/its behalf/

BV> OK.

> 
> >    o  Clears (sets to 0) the "O" bit.  The "O" bit is only 
> meaningful in
> >       Client FQDN options received from a server.
> 
> o  Always clears...?

BV> OK.

> 
> >    o  Sets the "E" bit to indicate that the Domain Name field is in
> >       DNS-style binary encoding, without compression, as 
> described in
> >       RFC 1035 [3].  A client which sends the Client FQDN 
> option SHOULD
> >       use this encoding.  Server implementers SHOULD note 
> that earlier
> >       draft versions of this specification permitted an 
> ASCII encoding
> >       of the domain name and this encoding MUST be used if 
> the "E" bit
> >       is clear.  Clients which implemented this encoding 
> were deployed
> >       before this specification was completed.  Server implementers
> >       which need to support these clients need to see the 
> section on the
> >       deprecated ASCII encoding (Section 4.3.1).
> >    o  Clears the "N" bit unless the client desires the server not to
> >       perform any DNS updates on its behalf.
> 
> How about:
> o Clears the "N" bit if the client desires the server perform DNS 
> updates on its behalf.

BV> Perhaps best to say "Sets the "N" bit if the client desires that the
BV> server perform no DNS updates on its behalf. If the "N" bit is set,
BV> the "S" bit MUST be cleared."

> 
> > 
> >    When a DHCP client receives the Client FQDN option in a DHCPOFFER
> >    and/or DHCPACK message:
> > 
> >    o  If the "S" bit is set, the server has taken 
> responsibility for the
> >       A RR updates and the client SHOULD NOT perform these 
> DNS updates.
> >       If the "S" bit is clear, the client MAY perform the A 
> RR updates.
> >    o  If the "O" bit is set, the server has overridden the client's
> >       request for the server not to update the A RR.  The 
> "O" bit MUST
> >       only be set if the "S" bit is also set.
> >    o  The "E" bit indicates the encoding of the Domain Name 
> field, and
> >       the bit MUST match what the client sent.
> >    o  If the "N" bit is set and the client had set the "N" 
> bit in what
> >       it sent to the server, the client SHOULD assume the 
> server honored
> >       the client's request and will not perform any DNS 
> updates.  If a
> >       client has set the "N" bit but its server does not, the client
> >       SHOULD conclude that the server was not configured to 
> honor the
> >       client's request and that the server MAY attempt to 
> perform DNS
> >       updates on the client's behalf.
> > 
> >    The remaining bits in the Flags field are reserved for future
> >    assignment.  DHCP clients and servers which send the Client FQDN
> >    option MUST clear the MBZ bits, and they MUST ignore these bits.
> > 
> > - Bernie
> > 
> 
> Yes, this is better than before.
> 
> Still I wonder if there is reason why O bit tells that server has 
> overriden client S bit setting, but N bit is handled 
> differently? Could flag semantics be: S=0 client updates or 
> does not want FQDN update at all, S=1 Server 
> updates FQDN
> O=0 server did as client requested, O=1 server did override 
> request N=0 client does PTR update or does not want it to be 
> updated, N=1 server updates PTR E=1 use domain binary 
> encoding, E=0 use deprecated ascii encoding

BV> We'll have to see if anyone else comments. The initial design of the
FQDN
BV> option predates my work on this so I don't have the historical context
to
BV> answer this. Also, as this option is in wide use already, we need to be
BV> careful that we're not changing things! I believe the "N" bit overrides
BV> the "S" - in the client/server processing logic which has also been
BV> significantly revised, this is hopefully clear (N bit is processed
first).

BV> I should be submitting the revised draft next week.

> --
> Jyrki
> 

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


From dhcwg-bounces@ietf.org  Fri Dec 17 19:18:37 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09272
	for <dhcwg-web-archive@ietf.org>; Fri, 17 Dec 2004 19:18:36 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CfSRh-0006zX-Lg
	for dhcwg-web-archive@ietf.org; Fri, 17 Dec 2004 19:27:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfS9Z-000869-DA; Fri, 17 Dec 2004 19:08:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfS2q-0005bu-Lc
	for dhcwg@megatron.ietf.org; Fri, 17 Dec 2004 19:02:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08115
	for <dhcwg@ietf.org>; Fri, 17 Dec 2004 19:01:57 -0500 (EST)
Received: from mailout3.samsung.com ([203.254.224.33])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfSBZ-0006VB-Ku
	for dhcwg@ietf.org; Fri, 17 Dec 2004 19:11:02 -0500
Received: from custom-daemon.mailout3.samsung.com by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	id <0I8W007015EFZL@mailout3.samsung.com> for dhcwg@ietf.org; Sat,
	18 Dec 2004 09:01:27 +0900 (KST)
Received: from ep_mmp1 (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003))
	with ESMTP id <0I8W00I7A5EE6F@mailout3.samsung.com> for dhcwg@ietf.org;
	Sat, 18 Dec 2004 09:01:27 +0900 (KST)
Received: from Alperyegin ([105.144.29.41])
	by mmp1.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004))
	with ESMTPA id <0I8W000TT5ECTU@mmp1.samsung.com> for dhcwg@ietf.org;
	Sat, 18 Dec 2004 09:01:26 +0900 (KST)
Date: Fri, 17 Dec 2004 16:01:24 -0800
From: Alper Yegin <alper.yegin@samsung.com>
Subject: RE: [dhcwg] Two new dhc WG work items
In-reply-to: <4.3.2.7.2.20041217062343.02084e78@flask.cisco.com>
To: "'Ralph Droms'" <rdroms@cisco.com>, dhcwg@ietf.org
Message-id: <00f001c4e494$b7f27730$291d9069@sisa.samsung.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-Mailer: Microsoft Outlook, Build 10.0.2627
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7BIT
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7BIT


> draft-droms-dhc-v6-relayopt-00.txt

I never understood why the relayable attributes are limited to what is
listed in 4.1.1. I'd appreciate if someone can explain the rationale.

Thank you.

Alper







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


From dhcwg-bounces@ietf.org  Sat Dec 18 11:36:05 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29620
	for <dhcwg-web-archive@ietf.org>; Sat, 18 Dec 2004 11:36:05 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cfhhm-0006eA-6w
	for dhcwg-web-archive@ietf.org; Sat, 18 Dec 2004 11:45:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CfhUq-0006sn-OZ; Sat, 18 Dec 2004 11:31:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CfhUe-0006iX-OM
	for dhcwg@megatron.ietf.org; Sat, 18 Dec 2004 11:31:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29203
	for <dhcwg@ietf.org>; Sat, 18 Dec 2004 11:31:42 -0500 (EST)
Received: from fivedots.coe.psu.ac.th ([202.12.73.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfhdW-0006ZO-JW
	for dhcwg@ietf.org; Sat, 18 Dec 2004 11:40:55 -0500
Received: from delta.coe.psu.ac.th ([172.30.0.98] helo=delta.noi.kre.to)
	by fivedots.coe.psu.ac.th with esmtp (Exim 3.36 #1 (Debian))
	id 1CfhTS-0000g3-00; Sat, 18 Dec 2004 23:30:30 +0700
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.noi.kre.to (8.12.9/8.11.6) with ESMTP id iBIGUQDS008441;
	Sat, 18 Dec 2004 23:30:27 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: "Bernie Volz" <volz@cisco.com>
Subject: Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-fqdn-00.txt 
In-Reply-To: <001101c4e44b$1be243f0$6901a8c0@amer.cisco.com> 
References: <001101c4e44b$1be243f0$6901a8c0@amer.cisco.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 18 Dec 2004 23:30:26 +0700
Message-ID: <23070.1103387426@munnari.OZ.AU>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: dhcwg@ietf.org, "'Jyrki Soini'" <jyrki.soini@teliasonera.com>,
        rdroms@cisco.com
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe

    Date:        Fri, 17 Dec 2004 10:14:31 -0500
    From:        "Bernie Volz" <volz@cisco.com>
    Message-ID:  <001101c4e44b$1be243f0$6901a8c0@amer.cisco.com>

  | Here's what I'm proposing for the revised DHCPv4 Client FQDN option
  | regarding the Flags bits.

Is there any chance of having this written in a form so that the text
simply says what the flag bits mean, rather that saying when the server
or client set or clear the things?

Personally, I find that I have no trouble working out when I am supposed
to set and clear bits to get the effect I'm after if I know what things
mean, but I find it annoying to have to reverse engineer someone's thinking
process to work out what something means from the circumstances in which
something or other would or would not, be done.

So, for example, rather than (the combination of)

	[The client] Sets (to 1) the "S" bit if it does not desire to perform
	any DNS updates and desires the DHCP server to perform FQDN to IP
	(the A RR) DNS updates on it behalf.  If the "S" bit is clear, the
	client indicates that it intends to maintain its own FQDN to IP
	mapping update.
and
	[When received by the client] If the "S" bit is set, the server has
	taken responsibility for the A RR updates and the client SHOULD NOT
	perform these DNS updates.  If the "S" bit is clear, the client MAY
	perform the A RR updates.

I'd say something more like

	S bit:  Set to 0 indicates that the client is responsible for
		any desired DNS update of the FQDN to address mapping.
		Set to 1 indicates that the server is responsible for
		updating the mapping.   The client sets this bit to
		indicate its preference, the state of the bit in a reply
		from the server indicates the action taken by the server.

I also (personal preference) dropped the SHOULD NOT about the client doing
its own updates - whether or not the client can/should update the DNS
itself is a matter for arrangement between the client and the DNS servers.
What the DHCP server tells me about this isn't likely to have much impact
on what my client attempts to do (though if I have no specific knowledge of
the domain, or its servers, I'd probably follow the DHCP server's sueggstion,
but I'd do that by setting S=1, and then observing the state of the bit in the
reply.   I actually see no reason to allow the server to override the S=0
state from the client (though of course the server isn't required to handle
S=1 from the client).

I also see no reason for the O bit, if the clint set S=0, and the reply
comes back with S=1, (which is the only time O=1 is appropriate, from what
I can see) it is pretty obvious already what happened - or is this some kind
of attempt to prevent the client from needing to keep state?   That would
be fairly pointless wouldn't it?

kre


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


From dhcwg-bounces@ietf.org  Mon Dec 20 09:34:07 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01627
	for <dhcwg-web-archive@ietf.org>; Mon, 20 Dec 2004 09:34:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgOlD-0001ju-HQ
	for dhcwg-web-archive@ietf.org; Mon, 20 Dec 2004 09:43:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgOWw-0003Ni-7R; Mon, 20 Dec 2004 09:28:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgORQ-0002jI-DH
	for dhcwg@megatron.ietf.org; Mon, 20 Dec 2004 09:23:16 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01090
	for <dhcwg@ietf.org>; Mon, 20 Dec 2004 09:23:14 -0500 (EST)
Received: from smtp.inet.fi ([192.89.123.192])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgOag-0001Vo-T1
	for dhcwg@ietf.org; Mon, 20 Dec 2004 09:32:51 -0500
Received: from [194.142.21.49] (gingerale.mit.sonera.com [194.142.21.49])
	by smtp.inet.fi (Postfix) with ESMTP
	id 3E7025DC9E; Mon, 20 Dec 2004 16:23:11 +0200 (EET)
Message-ID: <41C6E04D.2030601@teliasonera.com>
Date: Mon, 20 Dec 2004 16:23:09 +0200
From: Jyrki Soini <jyrki.soini@teliasonera.com>
Organization: TeliaSonera Finland
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Robert Elz <kre@munnari.OZ.AU>
Subject: Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-fqdn-00.txt
References: <001101c4e44b$1be243f0$6901a8c0@amer.cisco.com>
	<23070.1103387426@munnari.OZ.AU>
In-Reply-To: <23070.1103387426@munnari.OZ.AU>
X-Enigmail-Version: 0.89.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: multipart/mixed; boundary="------------070903020305050708010603"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: dhcwg@ietf.org, Bernie Volz <volz@cisco.com>, rdroms@cisco.com
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5d7a7e767f20255fce80fa0b77fb2433

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

Robert Elz wrote:
>     Date:        Fri, 17 Dec 2004 10:14:31 -0500
>     From:        "Bernie Volz" <volz@cisco.com>
>     Message-ID:  <001101c4e44b$1be243f0$6901a8c0@amer.cisco.com>
> 
>   | Here's what I'm proposing for the revised DHCPv4 Client FQDN option
>   | regarding the Flags bits.
> 
> Is there any chance of having this written in a form so that the text
> simply says what the flag bits mean, rather that saying when the server
> or client set or clear the things?
> 
> Personally, I find that I have no trouble working out when I am supposed
> to set and clear bits to get the effect I'm after if I know what things
> mean, but I find it annoying to have to reverse engineer someone's thinking
> process to work out what something means from the circumstances in which
> something or other would or would not, be done.
> 
> So, for example, rather than (the combination of)
> 
> 	[The client] Sets (to 1) the "S" bit if it does not desire to perform
> 	any DNS updates and desires the DHCP server to perform FQDN to IP
> 	(the A RR) DNS updates on it behalf.  If the "S" bit is clear, the
> 	client indicates that it intends to maintain its own FQDN to IP
> 	mapping update.
> and
> 	[When received by the client] If the "S" bit is set, the server has
> 	taken responsibility for the A RR updates and the client SHOULD NOT
> 	perform these DNS updates.  If the "S" bit is clear, the client MAY
> 	perform the A RR updates.
> 
> I'd say something more like
> 
> 	S bit:  Set to 0 indicates that the client is responsible for
> 		any desired DNS update of the FQDN to address mapping.
> 		Set to 1 indicates that the server is responsible for
> 		updating the mapping.   The client sets this bit to
> 		indicate its preference, the state of the bit in a reply
> 		from the server indicates the action taken by the server.
> 

This would make flag semantics clearer, I agree.

> I also (personal preference) dropped the SHOULD NOT about the client doing
> its own updates - whether or not the client can/should update the DNS
> itself is a matter for arrangement between the client and the DNS servers.
> What the DHCP server tells me about this isn't likely to have much impact
> on what my client attempts to do (though if I have no specific knowledge of
> the domain, or its servers, I'd probably follow the DHCP server's sueggstion,
> but I'd do that by setting S=1, and then observing the state of the bit in the
> reply.   I actually see no reason to allow the server to override the S=0
> state from the client (though of course the server isn't required to handle
> S=1 from the client).
> 
> I also see no reason for the O bit, if the clint set S=0, and the reply
> comes back with S=1, (which is the only time O=1 is appropriate, from what
> I can see) it is pretty obvious already what happened - or is this some kind
> of attempt to prevent the client from needing to keep state?   That would
> be fairly pointless wouldn't it?
> 
> kre
> 

Well, we might want to keep all flags N,E,O,S for IPv4 version for 
backwards compatibility reasons.

As far as I know, there is no (at least large intalled base) DHCPv6 FQDN 
option implementation, and we could perhaps use only two flag bits and
even name them differently. How about having:
Client sets flag:
A = 0, asks DHCPv6 server not to modify AAAA record for FQDN
     1, asks DHCPv6 server to modify AAAA record for FQDN
P = 0, asks DHCPv6 server not to modify PTR record for FQDN
     1, asks DHCPv6 server to modify PTR record for FQDN
Server indicates action:
A = 0, DHCPv6 server did not/won't modify AAAA record for FQDN
     1, DHCPv6 server did/will modify AAAA record for FQDN
P = 0, DHCPv6 server didn't/won't modify PTR record for FQDN
     1, DHCPv6 server did/will modify PTR record for FQDN
--
Jyrki

--------------070903020305050708010603
Content-Type: text/x-vcard; charset=utf-8;
 name="jyrki.soini.vcf"
Content-Disposition: attachment;
 filename="jyrki.soini.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard
fn:Jyrki Soini
n:Soini;Jyrki
org:Technology and Software Development;Emerging Technologies and Innobations
adr:P.O.Box 935;;TeliaSonera Finland;Helsiniki;;FI-00051;Finland
email;internet:jyrki.soini@teliasonera.com
title:Chief Network Architect
tel;work:+358 2040 64725
tel;fax:+358-2040-54081
tel;cell:+358 40 722 1119
x-mozilla-html:FALSE
version:2.1
end:vcard


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

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

--------------070903020305050708010603--



From dhcwg-bounces@ietf.org  Mon Dec 20 10:03:54 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04255
	for <dhcwg-web-archive@ietf.org>; Mon, 20 Dec 2004 10:03:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgPE3-0002VZ-KV
	for dhcwg-web-archive@ietf.org; Mon, 20 Dec 2004 10:13:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgP0G-0006tu-Ul; Mon, 20 Dec 2004 09:59:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgOs0-0005ec-96
	for dhcwg@megatron.ietf.org; Mon, 20 Dec 2004 09:50:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03271
	for <dhcwg@ietf.org>; Mon, 20 Dec 2004 09:50:40 -0500 (EST)
Received: from smtp.inet.fi ([192.89.123.192])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgP1E-0002AI-8X
	for dhcwg@ietf.org; Mon, 20 Dec 2004 10:00:17 -0500
Received: from [194.142.21.49] (gingerale.mit.sonera.com [194.142.21.49])
	by smtp.inet.fi (Postfix) with ESMTP
	id 64C465C4B4; Mon, 20 Dec 2004 16:50:39 +0200 (EET)
Message-ID: <41C6E6BD.8040109@teliasonera.com>
Date: Mon, 20 Dec 2004 16:50:37 +0200
From: Jyrki Soini <jyrki.soini@teliasonera.com>
Organization: TeliaSonera Finland
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-fqdn-00.txt
References: <001201c4e44c$19570fc0$6901a8c0@amer.cisco.com>
In-Reply-To: <001201c4e44c$19570fc0$6901a8c0@amer.cisco.com>
X-Enigmail-Version: 0.89.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: multipart/mixed; boundary="------------040205030302060508080403"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15

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

Bernie Volz wrote:
>
> I'm also moving the DHCPv6 Client FQDN option to the Client message (ie,
> removing it from being encapsulated in the IA_NA option). This should
> simplify processing. If a client wants to use different names with different
> bindings, it can just issue separate transactions (rather than putting
> multiple bindings in a single transaction). Note that it is of course up the
> server as to whether it allows multiple names or not in this case.
> 
> - Bernie

I'm afraid this is not a good idea. There is a clear need to bind FQDN
to IPv6 address. OPTION_IAADDR is IA_NA/IA_TA option and if we move FQDN
option to the Client message, we need to add IPv6 address(es) to FQDN 
option or create OPTION_IAADDR equivalent new Client option.

Which reminds me that we should have some option order rules written 
down. E.g. OPTION_IAADDR option(s) is(/are) associated with the FQDN 
option(s) that follow them. Or vise versa?
--
Jyrki

--------------040205030302060508080403
Content-Type: text/x-vcard; charset=utf-8;
 name="jyrki.soini.vcf"
Content-Disposition: attachment;
 filename="jyrki.soini.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard
fn:Jyrki Soini
n:Soini;Jyrki
org:Technology and Software Development;Emerging Technologies and Innobations
adr:P.O.Box 935;;TeliaSonera Finland;Helsiniki;;FI-00051;Finland
email;internet:jyrki.soini@teliasonera.com
title:Chief Network Architect
tel;work:+358 2040 64725
tel;fax:+358-2040-54081
tel;cell:+358 40 722 1119
x-mozilla-html:FALSE
version:2.1
end:vcard


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

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

--------------040205030302060508080403--



From dhcwg-bounces@ietf.org  Mon Dec 20 10:19:38 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05898
	for <dhcwg-web-archive@ietf.org>; Mon, 20 Dec 2004 10:19:37 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgPTH-00030C-CF
	for dhcwg-web-archive@ietf.org; Mon, 20 Dec 2004 10:29:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgPFr-0004bq-4q; Mon, 20 Dec 2004 10:15:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgP6T-0000kB-KP
	for dhcwg@megatron.ietf.org; Mon, 20 Dec 2004 10:05:41 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04590
	for <dhcwg@ietf.org>; Mon, 20 Dec 2004 10:05:39 -0500 (EST)
Received: from fivedots.coe.psu.ac.th ([202.12.73.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgPFj-0002cb-Ks
	for dhcwg@ietf.org; Mon, 20 Dec 2004 10:15:17 -0500
Received: from delta.coe.psu.ac.th ([172.30.0.98] helo=delta.noi.kre.to)
	by fivedots.coe.psu.ac.th with esmtp (Exim 3.36 #1 (Debian))
	id 1CgP6P-0005XF-00
	for <dhcwg@ietf.org>; Mon, 20 Dec 2004 22:05:37 +0700
Received: from munnari.OZ.AU (localhost [127.0.0.1])
	by delta.noi.kre.to (8.12.9/8.11.6) with ESMTP id iBKF5br9021052
	for <dhcwg@ietf.org>; Mon, 20 Dec 2004 22:05:38 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: dhcwg@ietf.org
In-Reply-To: <41C6E04D.2030601@teliasonera.com> 
References: <41C6E04D.2030601@teliasonera.com>
	<001101c4e44b$1be243f0$6901a8c0@amer.cisco.com>
	<23070.1103387426@munnari.OZ.AU> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 20 Dec 2004 22:05:37 +0700
Message-ID: <12591.1103555137@munnari.OZ.AU>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Subject: [dhcwg] DHCPv6 clients
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464

In a message on another thread ...

    Date:        Mon, 20 Dec 2004 16:23:09 +0200
    From:        Jyrki Soini <jyrki.soini@teliasonera.com>
    Message-ID:  <41C6E04D.2030601@teliasonera.com>

  | As far as I know, there is no (at least large intalled base) DHCPv6 FQDN 
  | option implementation,

which reminded me to ask something I have been wondering about for
a while.

I know there are available DHCPv6 (at least DHCPv6Lite) implementations
(servers) around, but are there any functional DHCPv6 clients available
yet?

And here I mean real clients, ones that actually configure a system,
I'm not interested in test/debug code that sends messages, receives
replies, and tells the user what happened (as useful as such things
are for server testing).

That is, which (if any) systems currently react correctly to the M and O
flags in IPv6 RA messages, and perform the appropriate configuration
(or attempt to) ?

kre


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


From dhcwg-bounces@ietf.org  Mon Dec 20 10:59:40 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10820
	for <dhcwg-web-archive@ietf.org>; Mon, 20 Dec 2004 10:59:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgQ62-0004Ch-2M
	for dhcwg-web-archive@ietf.org; Mon, 20 Dec 2004 11:09:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgPtB-0000Ic-Qe; Mon, 20 Dec 2004 10:56:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgPhw-0004TG-Tf
	for dhcwg@megatron.ietf.org; Mon, 20 Dec 2004 10:44:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09117
	for <dhcwg@ietf.org>; Mon, 20 Dec 2004 10:44:22 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgPrD-0003gI-Fx
	for dhcwg@ietf.org; Mon, 20 Dec 2004 10:54:00 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-1.cisco.com with ESMTP; 20 Dec 2004 07:50:37 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iBKFhmdP021231;
	Mon, 20 Dec 2004 07:43:48 -0800 (PST)
Received: from volzw2k (che-vpn-cluster-1-27.cisco.com [10.86.240.27])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANV46033;
	Mon, 20 Dec 2004 10:43:46 -0500 (EST)
From: "Bernie Volz" <volz@cisco.com>
To: "'Jyrki Soini'" <jyrki.soini@teliasonera.com>
Subject: RE: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-fqdn-00.txt
Date: Mon, 20 Dec 2004 10:43:41 -0500
Organization: Cisco
Message-ID: <003101c4e6aa$ae21dc60$6901a8c0@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <41C6E6BD.8040109@teliasonera.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: quoted-printable
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Content-Transfer-Encoding: quoted-printable

Hi:

I don't follow what you're driving at?

Do you have specific cases where a client needs a unique name associated
with each address that may be in an IA_NA. (IA_TA's are not likely to =
have
domain names, so I personally would suggest we ignore those?)

I used to think we needed a more complex mechanism, but I've not figured =
out
where this would be used and how this would work.

In the client to server communication, we really have no easy means to
associate a name with a specific address or a specific prefix.

The server might have different configurations for different prefixes. =
In
this case, though, think about who is doing what updates. The server is
doing the PTR updates and those are the ones that are likely to go to
different zones. The client MAY be doing the AAAA updates, but do you =
really
want to give the client multiple names and for what purpose?

We are trying to target this option at the most general and typical =
cases
and trying to get this off the ground. We can always expand/amend the
functionality in the future to address more complex environments.

Having a client FQDN option at the "outer-most scope" will likely be
sufficient for 99% of the cases.

- Bernie

> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org]=20
> On Behalf Of Jyrki Soini
> Sent: Monday, December 20, 2004 9:51 AM
> To: Bernie Volz
> Cc: dhcwg@ietf.org
> Subject: Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-fqdn-00.txt
>=20
>=20
> Bernie Volz wrote:
> >
> > I'm also moving the DHCPv6 Client FQDN option to the Client message=20
> > (ie, removing it from being encapsulated in the IA_NA option). This=20
> > should simplify processing. If a client wants to use=20
> different names=20
> > with different bindings, it can just issue separate transactions=20
> > (rather than putting multiple bindings in a single=20
> transaction). Note=20
> > that it is of course up the server as to whether it allows multiple=20
> > names or not in this case.
> >=20
> > - Bernie
>=20
> I'm afraid this is not a good idea. There is a clear need to=20
> bind FQDN to IPv6 address. OPTION_IAADDR is IA_NA/IA_TA=20
> option and if we move FQDN option to the Client message, we=20
> need to add IPv6 address(es) to FQDN=20
> option or create OPTION_IAADDR equivalent new Client option.
>=20
> Which reminds me that we should have some option order rules written=20
> down. E.g. OPTION_IAADDR option(s) is(/are) associated with the FQDN=20
> option(s) that follow them. Or vise versa?
> --
> Jyrki
>=20

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


From dhcwg-bounces@ietf.org  Mon Dec 20 12:27:26 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17583
	for <dhcwg-web-archive@ietf.org>; Mon, 20 Dec 2004 12:27:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgRSw-0006Yv-8X
	for dhcwg-web-archive@ietf.org; Mon, 20 Dec 2004 12:37:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgR9h-0004JS-8b; Mon, 20 Dec 2004 12:17:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgR8g-0003kW-9z
	for dhcwg@megatron.ietf.org; Mon, 20 Dec 2004 12:16:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17030
	for <dhcwg@ietf.org>; Mon, 20 Dec 2004 12:16:03 -0500 (EST)
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.33)
	id 1CgRHo-0006Hj-AU
	for dhcwg@ietf.org; Mon, 20 Dec 2004 12:25:42 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-3.cisco.com with ESMTP; 20 Dec 2004 10:23:06 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iBKHFFdP010766;
	Mon, 20 Dec 2004 09:15:16 -0800 (PST)
Received: from volzw2k (che-vpn-cluster-1-27.cisco.com [10.86.240.27])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANV54622;
	Mon, 20 Dec 2004 12:15:19 -0500 (EST)
From: "Bernie Volz" <volz@cisco.com>
To: "'Robert Elz'" <kre@munnari.OZ.AU>, <dhcwg@ietf.org>
Subject: RE: [dhcwg] DHCPv6 clients
Date: Mon, 20 Dec 2004 12:15:16 -0500
Organization: Cisco
Message-ID: <004b01c4e6b7$79f92030$6901a8c0@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <12591.1103555137@munnari.OZ.AU>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: 7bit
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: 7bit

There is dibbler which seems to configure the system.

See http://klub.com.pl/dhcpv6/.

> -----Original Message-----
> From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] 
> On Behalf Of Robert Elz
> Sent: Monday, December 20, 2004 10:06 AM
> To: dhcwg@ietf.org
> Subject: [dhcwg] DHCPv6 clients
> 
> 
> In a message on another thread ...
> 
>     Date:        Mon, 20 Dec 2004 16:23:09 +0200
>     From:        Jyrki Soini <jyrki.soini@teliasonera.com>
>     Message-ID:  <41C6E04D.2030601@teliasonera.com>
> 
>   | As far as I know, there is no (at least large intalled 
> base) DHCPv6 FQDN 
>   | option implementation,
> 
> which reminded me to ask something I have been wondering 
> about for a while.
> 
> I know there are available DHCPv6 (at least DHCPv6Lite) 
> implementations
> (servers) around, but are there any functional DHCPv6 clients 
> available yet?
> 
> And here I mean real clients, ones that actually configure a 
> system, I'm not interested in test/debug code that sends 
> messages, receives replies, and tells the user what happened 
> (as useful as such things are for server testing).
> 
> That is, which (if any) systems currently react correctly to 
> the M and O flags in IPv6 RA messages, and perform the 
> appropriate configuration (or attempt to) ?
> 
> kre
> 
> 
> _______________________________________________
> 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  Mon Dec 20 14:11:12 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23917
	for <dhcwg-web-archive@ietf.org>; Mon, 20 Dec 2004 14:11:12 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgT5O-0000WZ-5t
	for dhcwg-web-archive@ietf.org; Mon, 20 Dec 2004 14:20:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgSrJ-0001CJ-0p; Mon, 20 Dec 2004 14:06:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgSpY-0000kS-TZ; Mon, 20 Dec 2004 14:04:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23112;
	Mon, 20 Dec 2004 14:04:22 -0500 (EST)
Received: from toccata.fugue.com ([204.152.186.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgSym-0000IZ-Np; Mon, 20 Dec 2004 14:14:02 -0500
Received: from [10.0.2.5] (dsl093-162-226.tus1.dsl.speakeasy.net
	[66.93.162.226])
	by toccata.fugue.com (Postfix) with ESMTP id DCD741C1266;
	Mon, 20 Dec 2004 11:47:14 -0700 (MST)
In-Reply-To: <1103567830.20988.13.camel@reveille.sfbay.sun.com>
References: <001801c4e31d$48255760$1e02a8c0@BILLMOBILE>
	<385BF31F-59E4-48AB-AD89-D24017953F60@fugue.com>
	<1103567830.20988.13.camel@reveille.sfbay.sun.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <EEB540E0-52B9-11D9-9F12-000D93C4B69A@fugue.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <mellon@fugue.com>
Subject: Re: [Ipoverib] Re: [dhcwg] WG Last Call for DHCP draft
Date: Mon, 20 Dec 2004 12:04:11 -0700
To: Bill.Strahm@Sun.COM
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit
Cc: dhcwg@ietf.org, ipoverib@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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit

On Dec 20, 2004, at 11:37 AM, Bill Strahm wrote:
> This is the hard question... What should we do about this... I think we
> should take this  request - and say our client ID SHOULD follow RFC2132
> (if I understand the problem correctly)... Is there any non-capped
> advise that we can give ?
>
> Can you propose a change for this Vivek ?

The right change is to not say anything about the format of the client 
identifier option in the draft.   Either that, or reference the 
draft-ietf-dhc-3315id-for-v4-??.txt draft, which is (belatedly) in last 
call and will probably advance to RFC before this draft anyway (wishful 
thinking, perhaps :').



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


From dhcwg-bounces@ietf.org  Mon Dec 20 15:18:08 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00092
	for <dhcwg-web-archive@ietf.org>; Mon, 20 Dec 2004 15:18:08 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgU8B-000246-5m
	for dhcwg-web-archive@ietf.org; Mon, 20 Dec 2004 15:27:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgTxL-0002Ti-QQ; Mon, 20 Dec 2004 15:16:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CgSPK-0004pa-Dg
	for dhcwg@megatron.ietf.org; Mon, 20 Dec 2004 13:37:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21679
	for <dhcwg@ietf.org>; Mon, 20 Dec 2004 13:37:18 -0500 (EST)
Received: from brmea-mail-3.sun.com ([192.18.98.34])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CgSYc-00089y-A0
	for dhcwg@ietf.org; Mon, 20 Dec 2004 13:46:59 -0500
Received: from phys-bos-2.sfbay.sun.com ([129.146.14.24])
	by brmea-mail-3.sun.com (8.12.10/8.12.9) with ESMTP id iBKIaHW2001793
	for <dhcwg@ietf.org>; Mon, 20 Dec 2004 11:37:19 -0700 (MST)
Received: from reveille (reveille.SFBay.Sun.COM [129.146.95.151])
	by bos-mail1.sfbay.sun.com
	(Sun Java System Messaging Server 6.1 HotFix 0.02 (built Jul 26 2004))
	with ESMTP id <0I91001ULADYFO40@bos-mail1.sfbay.sun.com> for
	dhcwg@ietf.org; Mon, 20 Dec 2004 10:37:10 -0800 (PST)
Date: Mon, 20 Dec 2004 10:37:10 -0800
From: Bill Strahm <Bill.Strahm@Sun.COM>
Subject: Re: [Ipoverib] Re: [dhcwg] WG Last Call for DHCP draft
In-reply-to: <385BF31F-59E4-48AB-AD89-D24017953F60@fugue.com>
To: Ted Lemon <mellon@fugue.com>
Message-id: <1103567830.20988.13.camel@reveille.sfbay.sun.com>
Organization: Sun Microsystems
MIME-version: 1.0
X-Mailer: Evolution 2.0.2 (2.0.2-3)
Content-type: text/plain
Content-transfer-encoding: 7bit
References: <001801c4e31d$48255760$1e02a8c0@BILLMOBILE>
	<385BF31F-59E4-48AB-AD89-D24017953F60@fugue.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 20 Dec 2004 15:16:31 -0500
Cc: ipoverib@ietf.org, "'Ralph Droms'" <rdroms@cisco.com>, Bill@strahm.net,
        dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bill.Strahm@Sun.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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit

Vivek,

One question is hard, one is easy...

On Wed, 2004-12-15 at 20:55 -0700, Ted Lemon wrote:
> This draft uses a SHOULD to specify what data should be in the client 
> identifier. This is in conflict with another draft that's in the 
> process of working its way through to last call - 
> draft-ietf-dhc-3315id-for-v4-??.txt. This is a bad thing - someone 
> reading this spec will wonder which of the two specifications 
> supersedes the other. I don't see any reason to specify the format of 
> the client identifier in this draft - instead, refer the reader to 
> draft-ietf-dhc-3315id-for-v4-??.txt and to RFC2132 for advice on how to 
> format the client-identifier option.
> 
This is the hard question... What should we do about this... I think we
should take this  request - and say our client ID SHOULD follow RFC2132
(if I understand the problem correctly)... Is there any non-capped
advise that we can give ?

Can you propose a change for this Vivek ?

> Also, you have a reference to RFC1542. This is superseded by RFC2132, 
> so you should refer to RFC2132 instead - it is a huge mistake for 
> someone to read RFC1542 as advice on how to implement a DHCP client, 
> and so this draft shouldn't imply that the reader ought to look at 
> RFC1542 - he or she oughtn't.
> 
OK - this is the easy one.  Can you change the reference to RFC2132.

Any objections to this for closing this issue ?

Bill
> Ralph, what's going on with draft-ietf-dhc-3315id-for-v4-??.txt? This 
> is getting a little bit embarrassing... :'}
> 
I think this is DHC work - nothing for us to see here - IPoIB is moving
on

Bill


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


From dhcwg-bounces@ietf.org  Mon Dec 20 15:19:38 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00255
	for <dhcwg-web-archive@ietf.org>; Mon, 20 Dec 2004 15:19:38 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgU9d-00025I-VO
	for dhcwg-web-archive@ietf.org; Mon, 20 Dec 2004 15:29:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgTxM-0002UA-6v; Mon, 20 Dec 2004 15:16:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgSuV-0001dr-7t; Mon, 20 Dec 2004 14:09:35 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23838;
	Mon, 20 Dec 2004 14:09:33 -0500 (EST)
Received: from e35.co.us.ibm.com ([32.97.110.133])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgT3n-0000Su-E4; Mon, 20 Dec 2004 14:19:13 -0500
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com
	[9.17.195.106])
	by e35.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id iBKJ8xet610588;
	Mon, 20 Dec 2004 14:09:00 -0500
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168])
	by d03relay04.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id
	iBKJ8xZX119194; Mon, 20 Dec 2004 12:08:59 -0700
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1])
	by d03av02.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id
	iBKJ8xmV019550; Mon, 20 Dec 2004 12:08:59 -0700
Received: from DYN319548.beaverton.ibm.com (DYN319548.beaverton.ibm.com
	[9.47.22.85])
	by d03av02.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id
	iBKJ8vKX019469; Mon, 20 Dec 2004 12:08:58 -0700
Date: Mon, 20 Dec 2004 11:00:23 -0800 (PST)
From: Vivek Kashyap <kashyapv@us.ibm.com>
X-X-Sender: kashyapv@dyn319548.beaverton.ibm.com
To: Bill Strahm <Bill.Strahm@Sun.COM>
Subject: Re: [Ipoverib] Re: [dhcwg] WG Last Call for DHCP draft
In-Reply-To: <1103567830.20988.13.camel@reveille.sfbay.sun.com>
Message-ID: <Pine.LNX.4.44.0412201038520.24890-100000@dyn319548.beaverton.ibm.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
X-Mailman-Approved-At: Mon, 20 Dec 2004 15:16:32 -0500
Cc: ipoverib@ietf.org, dhcwg@ietf.org, Ted Lemon <mellon@fugue.com>,
        Bill@strahm.net, "'Ralph Droms'" <rdroms@cisco.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5

On Mon, 20 Dec 2004, Bill Strahm wrote:

> Vivek,
> 
> One question is hard, one is easy...
> 
> On Wed, 2004-12-15 at 20:55 -0700, Ted Lemon wrote:
> > This draft uses a SHOULD to specify what data should be in the client 
> > identifier. This is in conflict with another draft that's in the 
> > process of working its way through to last call - 
> > draft-ietf-dhc-3315id-for-v4-??.txt. This is a bad thing - someone 
> > reading this spec will wonder which of the two specifications 
> > supersedes the other. I don't see any reason to specify the format of 
> > the client identifier in this draft - instead, refer the reader to 
> > draft-ietf-dhc-3315id-for-v4-??.txt and to RFC2132 for advice on how to 
> > format the client-identifier option.
> > 
> This is the hard question... What should we do about this... I think we
> should take this  request - and say our client ID SHOULD follow RFC2132
> (if I understand the problem correctly)... Is there any non-capped
> advise that we can give ?
> 
> Can you propose a change for this Vivek ?

I have not had a chance to go over the draft Ted pointed to -- it appears to
be version -03.txt. 

However, the DHCP over InfiniBand draft does not define the client identifier 
option format itself but only describes the choices for client-identifier 
field itself. These choices are InfiniBand specific and are not likely to
be covered by a generic draft.

The text can be further clarified that the "SHOULD" only applies to the 
selection of one of the formats as described in RFC2132 to avoid any
possible confusion.  

The content of the client-identifier under Type 0 as described in the DHCP 
over InfiniBand draft is conformant to RFC2132. So is the case with the use 
of Type 32. 


> 
> > Also, you have a reference to RFC1542. This is superseded by RFC2132, 
> > so you should refer to RFC2132 instead - it is a huge mistake for 
> > someone to read RFC1542 as advice on how to implement a DHCP client, 
> > and so this draft shouldn't imply that the reader ought to look at 
> > RFC1542 - he or she oughtn't.
> > 
> OK - this is the easy one.  Can you change the reference to RFC2132.

I believe both references exist in the current draft. I'll drop the 1542 
reference.

> 
> Any objections to this for closing this issue ?
> 
> Bill
> > Ralph, what's going on with draft-ietf-dhc-3315id-for-v4-??.txt? This 
> > is getting a little bit embarrassing... :'}
> > 
> I think this is DHC work - nothing for us to see here - IPoIB is moving
> on
> 
> Bill
> 
> 
> _______________________________________________
> IPoverIB mailing list
> IPoverIB@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipoverib
> 
> 


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


From dhcwg-bounces@ietf.org  Tue Dec 21 04:16:02 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18239
	for <dhcwg-web-archive@ietf.org>; Tue, 21 Dec 2004 04:16:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CggH7-0006K9-BR
	for dhcwg-web-archive@ietf.org; Tue, 21 Dec 2004 04:25:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cgg64-0000XM-GT; Tue, 21 Dec 2004 04:14:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cgg3t-0000FB-EA
	for dhcwg@megatron.ietf.org; Tue, 21 Dec 2004 04:12:11 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17939
	for <dhcwg@ietf.org>; Tue, 21 Dec 2004 04:12:07 -0500 (EST)
Received: from smtp.inet.fi ([192.89.123.192])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CggDK-0006Ds-3c
	for dhcwg@ietf.org; Tue, 21 Dec 2004 04:21:54 -0500
Received: from [194.142.21.49] (gingerale.mit.sonera.com [194.142.21.49])
	by smtp.inet.fi (Postfix) with ESMTP
	id E9A84D8D0; Tue, 21 Dec 2004 11:12:04 +0200 (EET)
Message-ID: <41C7E8DD.6070807@teliasonera.com>
Date: Tue, 21 Dec 2004 11:11:57 +0200
From: Jyrki Soini <jyrki.soini@teliasonera.com>
Organization: TeliaSonera Finland
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-fqdn-00.txt
References: <003101c4e6aa$ae21dc60$6901a8c0@amer.cisco.com>
In-Reply-To: <003101c4e6aa$ae21dc60$6901a8c0@amer.cisco.com>
X-Enigmail-Version: 0.89.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: multipart/mixed; boundary="------------020707020409030301050207"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 789c141a303c09204b537a4078e2a63f

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

Bernie Volz wrote:
> Hi:
> 
> I don't follow what you're driving at?
> 
> Do you have specific cases where a client needs a unique name associated
> with each address that may be in an IA_NA. (IA_TA's are not likely to have
> domain names, so I personally would suggest we ignore those?)
> 
IA_TA's don't need FQDN option.

> I used to think we needed a more complex mechanism, but I've not figured out
> where this would be used and how this would work.
>
> In the client to server communication, we really have no easy means to
> associate a name with a specific address or a specific prefix.
> 
> The server might have different configurations for different prefixes. In
> this case, though, think about who is doing what updates. The server is
> doing the PTR updates and those are the ones that are likely to go to
> different zones. The client MAY be doing the AAAA updates, but do you really
> want to give the client multiple names and for what purpose?
>
This is quite marginal case, but could use the mechanism.
Say the dhcp client is a server that provides services for several 
organizations and belong to each organization domain. For some reason 
server needs different address to serve each organization. For instance 
such reason may relate to firewall policies. The addresses may be 
configured statically, but PTR update for domain is done with dhcpv6 
server assistance.

Client creates a request message
IA_NA
   OPTION_IAADDR 2001:bd8:1:1::1
   FQDN a.sample.org
   OPTION_IAADDR 2001:db8:2:2::2
   FQDN e.xample.org
   option IAADDR 2001:db8:3:3::3
   option IAADDR 2001:db8:4:4::4
   FQDN server.anydomain.net

> We are trying to target this option at the most general and typical cases
> and trying to get this off the ground. We can always expand/amend the
> functionality in the future to address more complex environments.
>
The above example is corner case, I agree.

> Having a client FQDN option at the "outer-most scope" will likely be
> sufficient for 99% of the cases.
> 
Here I have some doubt. I think stateless autoconfiguration will still
be used for address generation for most cases and stateful configuration 
with dhcpv6 will remain minor. DDNS updates with dhcpv6 server have 
operational advantages still. If stateless autoconfiguration or manual 
address configuration is used dhcpv6 server doesn't have existing 
information about client IPv6 addresses. It is possible to
provide the addressing information from client if IA_NA option 
OPTION_IAAADR is used in concert with FQDN option. If FQDN option is
moved to client option this possibility is missed. Or am I missing 
something?

> - Bernie

Jyrki

> 
> 
>>-----Original Message-----
>>From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] 
>>On Behalf Of Jyrki Soini
>>Sent: Monday, December 20, 2004 9:51 AM
>>To: Bernie Volz
>>Cc: dhcwg@ietf.org
>>Subject: Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-fqdn-00.txt
>>
>>
>>Bernie Volz wrote:
>>
>>>I'm also moving the DHCPv6 Client FQDN option to the Client message 
>>>(ie, removing it from being encapsulated in the IA_NA option). This 
>>>should simplify processing. If a client wants to use 
>>
>>different names 
>>
>>>with different bindings, it can just issue separate transactions 
>>>(rather than putting multiple bindings in a single 
>>
>>transaction). Note 
>>
>>>that it is of course up the server as to whether it allows multiple 
>>>names or not in this case.
>>>
>>>- Bernie
>>
>>I'm afraid this is not a good idea. There is a clear need to 
>>bind FQDN to IPv6 address. OPTION_IAADDR is IA_NA/IA_TA 
>>option and if we move FQDN option to the Client message, we 
>>need to add IPv6 address(es) to FQDN 
>>option or create OPTION_IAADDR equivalent new Client option.
>>
>>Which reminds me that we should have some option order rules written 
>>down. E.g. OPTION_IAADDR option(s) is(/are) associated with the FQDN 
>>option(s) that follow them. Or vise versa?
>>--
>>Jyrki
>>


--------------020707020409030301050207
Content-Type: text/x-vcard; charset=utf-8;
 name="jyrki.soini.vcf"
Content-Disposition: attachment;
 filename="jyrki.soini.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard
fn:Jyrki Soini
n:Soini;Jyrki
org:Technology and Software Development;Emerging Technologies and Innobations
adr:P.O.Box 935;;TeliaSonera Finland;Helsiniki;;FI-00051;Finland
email;internet:jyrki.soini@teliasonera.com
title:Chief Network Architect
tel;work:+358 2040 64725
tel;fax:+358-2040-54081
tel;cell:+358 40 722 1119
x-mozilla-html:FALSE
version:2.1
end:vcard


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

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

--------------020707020409030301050207--



From dhcwg-bounces@ietf.org  Tue Dec 21 10:18:03 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18172
	for <dhcwg-web-archive@ietf.org>; Tue, 21 Dec 2004 10:18:02 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CglvV-0006JO-69
	for dhcwg-web-archive@ietf.org; Tue, 21 Dec 2004 10:27:53 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CglgH-0004Q2-0x; Tue, 21 Dec 2004 10:12:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cgldg-0003b1-Bc
	for dhcwg@megatron.ietf.org; Tue, 21 Dec 2004 10:09:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17400
	for <dhcwg@ietf.org>; Tue, 21 Dec 2004 10:09:26 -0500 (EST)
Received: from shell-ng.nominum.com ([81.200.64.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cgln8-00064x-2w
	for dhcwg@ietf.org; Tue, 21 Dec 2004 10:19:16 -0500
Received: from [10.0.2.5] (dsl093-162-226.tus1.dsl.speakeasy.net
	[66.93.162.226]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
	(Client did not present a certificate)
	by shell-ng.nominum.com (Postfix) with ESMTP id AD21556893
	for <dhcwg@ietf.org>; Tue, 21 Dec 2004 07:08:53 -0800 (PST)
	(envelope-from Ted.Lemon@nominum.com)
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <41C7E8DD.6070807@teliasonera.com>
References: <003101c4e6aa$ae21dc60$6901a8c0@amer.cisco.com>
	<41C7E8DD.6070807@teliasonera.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <35A49C0A-5362-11D9-9F12-000D93C4B69A@nominum.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Comments on draft-ietf-dhc-dhcpv6-fqdn-00.txt
Date: Tue, 21 Dec 2004 08:08:45 -0700
To: dhcwg@ietf.org
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Content-Transfer-Encoding: 7bit
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit

On Dec 21, 2004, at 2:11 AM, Jyrki Soini wrote:
> Say the dhcp client is a server that provides services for several 
> organizations and belong to each organization domain. For some reason 
> server needs different address to serve each organization. For 
> instance such reason may relate to firewall policies. The addresses 
> may be configured statically, but PTR update for domain is done with 
> dhcpv6 server assistance.

In this case I think it would make the most sense to configure the 
device to update the DNS itself.   Adding a great deal of complexity in 
order to address corner cases seems like a bad idea.   Furthermore, as 
Bernie pointed out in a previous message, you can always get the 
different IP addresses in different DHCP messages if you want to send 
different FQDN options, so you aren't _prevented_ from doing this.

Anyway, the bottom line is that we talked about this, and were quite 
skeptical that this would actually occur in the real world.   We want 
to see an actual example of the problem in the real world.   Otherwise 
we're adding something to the protocol to address a problem that we 
imagine might happen, where we aren't particularly sure *how* it will 
happen.   Since this isn't a security issue, it doesn't need to be 
dealt with in advance in order to prevent a catastrophe, so there's no 
urgency in resolving the problem.


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


From dhcwg-bounces@ietf.org  Tue Dec 21 19:53:21 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28376
	for <dhcwg-web-archive@ietf.org>; Tue, 21 Dec 2004 19:53:21 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CguuI-0002Ao-Jh
	for dhcwg-web-archive@ietf.org; Tue, 21 Dec 2004 20:03:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CgucV-0000RS-Li; Tue, 21 Dec 2004 19:44:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cgub1-0008Fa-BO
	for dhcwg@megatron.ietf.org; Tue, 21 Dec 2004 19:43:19 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27243
	for <dhcwg@ietf.org>; Tue, 21 Dec 2004 19:43:13 -0500 (EST)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CguYZ-0001Cg-Qm
	for dhcwg@ietf.org; Tue, 21 Dec 2004 19:40:49 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-1.cisco.com with ESMTP; 21 Dec 2004 19:39:23 -0500
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iBM0UJgE001844; 
	Tue, 21 Dec 2004 19:30:20 -0500 (EST)
Received: from rdroms-w2k01.cisco.com (sjc-vpn4-158.cisco.com [10.21.80.158])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANW72008;
	Tue, 21 Dec 2004 19:30:15 -0500 (EST)
Message-Id: <4.3.2.7.2.20041221192812.028dddf8@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 21 Dec 2004 19:30:06 -0500
To: Robert Elz <kre@munnari.OZ.AU>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] DHCPv6 clients
In-Reply-To: <12591.1103555137@munnari.OZ.AU>
References: <41C6E04D.2030601@teliasonera.com>
	<41C6E04D.2030601@teliasonera.com>
	<001101c4e44b$1be243f0$6901a8c0@amer.cisco.com>
	<23070.1103387426@munnari.OZ.AU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352

kre - There is a DHCPv6 client in IOS that does configuration of DNS 
servers, etc., and prefix delegation (but not address assignment).  It does 
react correctly to the state of the 'O' flag.

- Ralph

At 10:05 PM 12/20/2004 +0700, Robert Elz wrote:
>In a message on another thread ...
>
>     Date:        Mon, 20 Dec 2004 16:23:09 +0200
>     From:        Jyrki Soini <jyrki.soini@teliasonera.com>
>     Message-ID:  <41C6E04D.2030601@teliasonera.com>
>
>   | As far as I know, there is no (at least large intalled base) DHCPv6 FQDN
>   | option implementation,
>
>which reminded me to ask something I have been wondering about for
>a while.
>
>I know there are available DHCPv6 (at least DHCPv6Lite) implementations
>(servers) around, but are there any functional DHCPv6 clients available
>yet?
>
>And here I mean real clients, ones that actually configure a system,
>I'm not interested in test/debug code that sends messages, receives
>replies, and tells the user what happened (as useful as such things
>are for server testing).
>
>That is, which (if any) systems currently react correctly to the M and O
>flags in IPv6 RA messages, and perform the appropriate configuration
>(or attempt to) ?
>
>kre
>
>
>_______________________________________________
>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  Tue Dec 21 22:30:14 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12877
	for <dhcwg-web-archive@ietf.org>; Tue, 21 Dec 2004 22:30:14 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CgxMA-0006ou-Oy
	for dhcwg-web-archive@ietf.org; Tue, 21 Dec 2004 22:40:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cgx7u-0005Je-7u; Tue, 21 Dec 2004 22:25:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cgx1W-0003ZW-FH
	for dhcwg@megatron.ietf.org; Tue, 21 Dec 2004 22:18:50 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12253
	for <dhcwg@ietf.org>; Tue, 21 Dec 2004 22:18:48 -0500 (EST)
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.33)
	id 1CgxB6-0006Yi-4D
	for dhcwg@ietf.org; Tue, 21 Dec 2004 22:28:45 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-3.cisco.com with ESMTP; 21 Dec 2004 20:26:17 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iBM3IFHn026458
	for <dhcwg@ietf.org>; Tue, 21 Dec 2004 19:18:16 -0800 (PST)
Received: from volzw2k (che-vpn-cluster-2-61.cisco.com [10.86.242.61])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANW81529;
	Tue, 21 Dec 2004 22:18:14 -0500 (EST)
From: "Bernie Volz" <volz@cisco.com>
To: <dhcwg@ietf.org>
Date: Tue, 21 Dec 2004 22:18:15 -0500
Organization: Cisco
Message-ID: <001001c4e7d4$e02487f0$6401a8c0@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] New Drafts - draft-volz-dhc-dhcpv6-subid-00 &
	draft-volz-dhc-dhcpv6-remoteid-00
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit

I've written 2 new individual submissions:

http://www.ietf.org/internet-drafts/draft-volz-dhc-dhcpv6-subid-00.txt

Abstract

   This memo defines a new Relay Agent Subscriber-ID option for the
   Dynamic Host Configuration Protocol for IPv6 (DHCPv6).  The option
   allows a DHCPv6 relay agent to associate a stable "Subscriber-ID"
   with DHCPv6 client messages in a way that is independent of the
   client and of the underlying physical network infrastructure.

And

http://www.ietf.org/internet-drafts/draft-volz-dhc-dhcpv6-remoteid-00.txt

   This memo defines a new Relay Agent Remote-ID option for the Dynamic
   Host Configuration Protocol for IPv6 (DHCPv6).  This option is the
   DHCPv6 equivalent for the Dynamic Host Configuration Protocol for
   IPv4 (DHCPv4) Relay Agent Option's Remote-ID suboption as specified
   in RFC 3046.

Please take a look at them and provide comments. I'd like to request these
to become DHC WG work items.

- Bernie

-----Original Message-----
From: Bernie Volz [mailto:volz@cisco.com] 
Sent: Sunday, December 19, 2004 11:41 PM
To: 'internet-drafts@ietf.org'
Subject: Please publish draft-volz-dhc-dhcpv6-subid-00 &
draft-volz-dhc-dhcpv6-remoteid-00


Hello:

Please publish the attached two drafts. You may also obtain these drafts
over the web at:

http://home.metrocast.net/~volz/draft-volz-dhc-dhcpv6-remoteid-00.txt
http://home.metrocast.net/~volz/draft-volz-dhc-dhcpv6-subid-00.txt

Thanks in advance and Happy Holidays & New Year!

- Bernie Volz

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


From dhcwg-bounces@ietf.org  Wed Dec 22 10:20:09 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02937
	for <dhcwg-web-archive@ietf.org>; Wed, 22 Dec 2004 10:20:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ch8RH-0001Q7-Q5
	for dhcwg-web-archive@ietf.org; Wed, 22 Dec 2004 10:30:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ch8Dy-00064j-5Z; Wed, 22 Dec 2004 10:16:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ch83y-0007ZM-JP
	for dhcwg@megatron.ietf.org; Wed, 22 Dec 2004 10:06:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00207
	for <dhcwg@ietf.org>; Wed, 22 Dec 2004 10:06:04 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ch8Df-0000mW-Iu
	for dhcwg@ietf.org; Wed, 22 Dec 2004 10:16:07 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 22 Dec 2004 07:10:59 -0800
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id iBMF5To9005410
	for <dhcwg@ietf.org>; Wed, 22 Dec 2004 07:05:30 -0800 (PST)
Received: from volzw2k ([161.44.65.252]) by flask.cisco.com (MOS 3.4.6-GR)
	with ESMTP id ANX02916; Wed, 22 Dec 2004 10:05:31 -0500 (EST)
From: "Bernie Volz" <volz@cisco.com>
To: <dhcwg@ietf.org>
Date: Wed, 22 Dec 2004 10:05:31 -0500
Organization: Cisco
Message-ID: <000401c4e837$ae31c880$fc412ca1@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: quoted-printable
Subject: [dhcwg] Updated  draft-ietf-dhc-fqdn-option-08.txt submitted
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: quoted-printable

Hi:

I've just submitted a revised version of the DHCPv4 Client FQDN option
(presently available at
ftp://ftp-eng.cisco.com/volz/draft-ietf-dhc-fqdn-option-08.txt).

Thanks to all those that provided comments regarding this draft over the
past several weeks, especially Olafur.

This draft has significant revisions in section 3, 4, and 5 (used to be
sections 4, 5, and 6). I would appreciate it if you could give those
sections a careful read and make sure I properly captured the existing
behavior as I don't want to redefine implemented behavior (as there are =
many
clients and servers that already support this option).

In January I will submit an updated DHCPv6 Client FQDN draft.

Thanks much and Happy Holidays!

- Bernie



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


From dhcwg-bounces@ietf.org  Thu Dec 23 21:56:09 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21753
	for <dhcwg-web-archive@ietf.org>; Thu, 23 Dec 2004 21:56:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Chfmh-00082T-La
	for dhcwg-web-archive@ietf.org; Thu, 23 Dec 2004 22:06:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ChfVl-0000Yr-3v; Thu, 23 Dec 2004 21:49:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ChfPD-0007Pd-10
	for dhcwg@megatron.ietf.org; Thu, 23 Dec 2004 21:42:15 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20980
	for <dhcwg@ietf.org>; Thu, 23 Dec 2004 21:42:12 -0500 (EST)
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.33)
	id 1ChfZC-0007o1-38
	for dhcwg@ietf.org; Thu, 23 Dec 2004 21:52:35 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-3.cisco.com with ESMTP; 23 Dec 2004 19:50:05 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iBO2fcHp016647
	for <dhcwg@ietf.org>; Thu, 23 Dec 2004 18:41:41 -0800 (PST)
Received: from insbu-view1.cisco.com (insbu-view1.cisco.com [171.71.160.12])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANY15222;
	Thu, 23 Dec 2004 21:41:37 -0500 (EST)
Date: Thu, 23 Dec 2004 18:41:37 -0800 (PST)
From: Ralph Droms <rdroms@cisco.com>
To: dhcwg@ietf.org
Message-ID: <Pine.GSO.4.58.0412231841240.26544@insbu-view1.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Subject: [dhcwg] Last Call: 'Dynamic Host Configuration Protocol (DHCPv4 and
 DHCPv6)
 Option for Civic Addresses Configuration Information' to Proposed Standard
 (fwd)
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5

FYI...

---------- Forwarded message ----------
Date: Thu, 23 Dec 2004 21:05:53 -0500
From: The IESG <iesg-secretary@ietf.org>
Reply-To: iesg@ietf.org
To: IETF-Announce <ietf-announce@ietf.org>
Cc: geopriv@ietf.org
Subject: Last Call: 'Dynamic Host Configuration Protocol (DHCPv4 and
    DHCPv6) Option for Civic Addresses Configuration Information' to Proposed
    Standard

The IESG has received a request from the Geographic Location/Privacy WG to
consider the following document:

- 'Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic
   Addresses Configuration Information '
   <draft-ietf-geopriv-dhcp-civil-04.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by 2005-01-13.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-geopriv-dhcp-civil-04.txt


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

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


From dhcwg-bounces@ietf.org  Sun Dec 26 10:32:44 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28419
	for <dhcwg-web-archive@ietf.org>; Sun, 26 Dec 2004 10:32:44 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CiaYU-0004jL-Vh
	for dhcwg-web-archive@ietf.org; Sun, 26 Dec 2004 10:43:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CiaMH-0001ZH-PI; Sun, 26 Dec 2004 10:31:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CiaH6-0000f1-LI
	for dhcwg@megatron.ietf.org; Sun, 26 Dec 2004 10:25:40 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27970
	for <dhcwg@ietf.org>; Sun, 26 Dec 2004 10:25:38 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CiaRb-0004Zl-Pg
	for dhcwg@ietf.org; Sun, 26 Dec 2004 10:36:33 -0500
Received: from sj-core-3.cisco.com (171.68.223.137)
	by sj-iport-4.cisco.com with ESMTP; 26 Dec 2004 07:25:28 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com
	[161.44.122.62])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id iBQFP56n020844
	for <dhcwg@ietf.org>; Sun, 26 Dec 2004 07:25:06 -0800 (PST)
Received: from rdroms-w2k01.cisco.com (sjc-vpn6-174.cisco.com [10.21.120.174])
	by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id ANY51170;
	Sun, 26 Dec 2004 10:25:03 -0500 (EST)
Message-Id: <4.3.2.7.2.20041226101817.01f8d260@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sun, 26 Dec 2004 10:24:57 -0500
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: [dhcwg] Co-chair for dhc WG
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2

Stig Venaas has agreed to take on the role of co-chair of the dhc WG.  His
appointment as co-chair will give us more cycles and broader representation
for WG leadership and administration, as well as important expertise and
experience with issues in IPv6 and DHCP.

Thanks, Stig, for agreeing to contribute to the dhc WG in this way.  I'm
looking forward to working with you as co-chair...

- Ralph

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


From dhcwg-bounces@ietf.org  Tue Dec 28 02:11:50 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25169
	for <dhcwg-web-archive@ietf.org>; Tue, 28 Dec 2004 02:11:50 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjBhB-00018T-6N
	for dhcwg-web-archive@ietf.org; Tue, 28 Dec 2004 02:23:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjBUG-0006CB-Qi; Tue, 28 Dec 2004 02:09:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjBN7-0002kN-Ux
	for dhcwg@megatron.ietf.org; Tue, 28 Dec 2004 02:02:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17454
	for <dhcwg@ietf.org>; Tue, 28 Dec 2004 02:02:20 -0500 (EST)
Received: from wproxy.gmail.com ([64.233.184.199])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjBXy-0000sz-Ko
	for dhcwg@ietf.org; Tue, 28 Dec 2004 02:13:35 -0500
Received: by wproxy.gmail.com with SMTP id 50so417096wri
	for <dhcwg@ietf.org>; Mon, 27 Dec 2004 23:01:47 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding;
	b=BICVhA/kfX1lehurNyPfdJZPSgDIGvsal9n5Qqbf3l8Zi5B2uxd19ESRR8fjlomR17jnMR7qOrGKz7t0eITmRkjieK0DcSSHkhTHea8QRq4CmNsdDLbSDrrpa7KvAVy6ooV9r5mTfsBxRQaLNHjDCxT3J1IWyHn1VTNTjLgjgzs=
Received: by 10.54.31.34 with SMTP id e34mr616566wre;
	Mon, 27 Dec 2004 23:01:47 -0800 (PST)
Received: by 10.54.23.37 with HTTP; Mon, 27 Dec 2004 23:01:47 -0800 (PST)
Message-ID: <72a9b062041227230145dc8347@mail.gmail.com>
Date: Tue, 28 Dec 2004 12:31:47 +0530
From: Muneer <muneerch@gmail.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] std value of offe reuse timeout
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Muneer <muneerch@gmail.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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit

hi,
  kindly let me know whether there is any standard value for dhcpoffer
reuse time out. according to rfc2131, we can have an implementation
specific mechanism for reusing the offered address. thanks in advance.

-- 
Imagination is more important than knowledge...

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


From dhcwg-bounces@ietf.org  Tue Dec 28 02:28:58 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02374
	for <dhcwg-web-archive@ietf.org>; Tue, 28 Dec 2004 02:28:57 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjBxk-0001Zj-LE
	for dhcwg-web-archive@ietf.org; Tue, 28 Dec 2004 02:40:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjBhk-0003p9-5B; Tue, 28 Dec 2004 02:23:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjBYJ-0007XI-0o
	for dhcwg@megatron.ietf.org; Tue, 28 Dec 2004 02:13:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26838
	for <dhcwg@ietf.org>; Tue, 28 Dec 2004 02:13:53 -0500 (EST)
Received: from wproxy.gmail.com ([64.233.184.205])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjBj9-0001BT-NI
	for dhcwg@ietf.org; Tue, 28 Dec 2004 02:25:08 -0500
Received: by wproxy.gmail.com with SMTP id 50so417685wri
	for <dhcwg@ietf.org>; Mon, 27 Dec 2004 23:13:23 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding;
	b=JRriUDacxGRFsCVSe7phpkDKn3CH6Qbjptfk37fBf0sJUM9g/oVnruZ27/+OJSA6PxMfb+k58YZCSd5DXrAm6O5xinJVcVk2pPW3NNZurnNf6tlb1y7XiuSayodvCuUSUM8F44kSGQdCyJ1hJcLtlDWPu1bEcyCOkfayss/VNiE=
Received: by 10.54.5.25 with SMTP id 25mr50703wre;
	Mon, 27 Dec 2004 23:13:22 -0800 (PST)
Received: by 10.54.23.37 with HTTP; Mon, 27 Dec 2004 23:13:22 -0800 (PST)
Message-ID: <72a9b062041227231335337106@mail.gmail.com>
Date: Tue, 28 Dec 2004 12:43:22 +0530
From: Muneer <muneerch@gmail.com>
To: dhcwg@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7bit
Subject: [dhcwg] std vlaue for offer reuse timeout
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Muneer <muneerch@gmail.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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Content-Transfer-Encoding: 7bit

kindly let me know whehter there is a standard value for dhcp offer
reuse timeout. according to rfc2131,

" As an implementation detail, servers SHOULD NOT reuse offered
addresses and may use an implementation-specific timeout mechanism to
decide when to reuse an offered address."

thanks in advance.
REGARDS
MUNEER

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


From dhcwg-bounces@ietf.org  Tue Dec 28 07:48:09 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21757
	for <dhcwg-web-archive@ietf.org>; Tue, 28 Dec 2004 07:48:09 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjGwg-0000kg-Jg
	for dhcwg-web-archive@ietf.org; Tue, 28 Dec 2004 07:59:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjGiI-0007Ww-A3; Tue, 28 Dec 2004 07:44:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cj9kU-0000Xg-4r
	for dhcwg@megatron.ietf.org; Tue, 28 Dec 2004 00:18:22 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09467
	for <dhcwg@ietf.org>; Tue, 28 Dec 2004 00:18:19 -0500 (EST)
Received: from web81403.mail.yahoo.com ([206.190.37.92])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1Cj9vJ-0006my-Vz
	for dhcwg@ietf.org; Tue, 28 Dec 2004 00:29:35 -0500
Message-ID: <20041228051750.50523.qmail@web81403.mail.yahoo.com>
Received: from [65.198.47.68] by web81403.mail.yahoo.com via HTTP;
	Mon, 27 Dec 2004 21:17:50 PST
X-RocketYMMF: charles.leu@sbcglobal.net
Date: Mon, 27 Dec 2004 21:17:50 -0800 (PST)
From: Charles Leu <cleu@ieee.org>
To: dhcwg@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
X-Mailman-Approved-At: Tue, 28 Dec 2004 07:44:32 -0500
Subject: [dhcwg] DHCP Option "Server Identifier"
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: cleu@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="===============1414186245=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c

--===============1414186245==
Content-Type: multipart/alternative; boundary="0-1557488497-1104211070=:50449"

--0-1557488497-1104211070=:50449
Content-Type: text/plain; charset=us-ascii

Hello,
 
I'm hoping you can clarify what seems to be a conflict between RFC 2131 and RFC 2132.
 
On page 29 of RFC 2131 within "Table 3:  Fields and options used by DHCP servers" it indicates that option "Server identifier" MUST be present in DHCPOFFER, DHCPACK, DHCPNAK messages.
 
On page 27 of RFC 2132 in section "9.7 Server Identifier" it says "This option is used in DHCPOFFER and DHCPREQUEST messages, and may optionally be included in the DHCPACK and DHCPNAK messages."
 
Thus my confusion:  If the Server Identifier option is a MUST for DHCPACK and DHCPNAK, how can it be considered optional for DHCPACK and DHCPNAK?
 
Your interpretation and clarification will be appreciated.  Thanks.
 
RSVP
Charles Leu
cleu@ieee.org
 





--0-1557488497-1104211070=:50449
Content-Type: text/html; charset=us-ascii

<DIV>
<DIV>
<DIV id=message>
<DIV>
<DIV>Hello,</DIV>
<DIV>&nbsp;</DIV>
<DIV>I'm hoping you can clarify what seems to be a conflict between RFC 2131 and RFC 2132.</DIV>
<DIV>&nbsp;</DIV>
<DIV>On page 29 of RFC 2131 within "Table 3:&nbsp; Fields and options used by DHCP servers" it indicates that option "Server identifier" MUST be present in DHCPOFFER, DHCPACK, DHCPNAK messages.</DIV>
<DIV>&nbsp;</DIV>
<DIV>On page 27 of RFC 2132 in section "9.7 Server Identifier" it says "This option is used in DHCPOFFER and DHCPREQUEST messages, and may optionally be included in the DHCPACK and DHCPNAK messages."</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thus my confusion:&nbsp; If the Server Identifier option is a MUST for DHCPACK and DHCPNAK, how can it be considered optional for DHCPACK and DHCPNAK?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Your interpretation and clarification will be appreciated.&nbsp; Thanks.</DIV>
<DIV>&nbsp;</DIV>
<DIV>RSVP</DIV>
<DIV>Charles Leu</DIV>
<DIV>cleu@ieee.org</DIV>
<DIV>&nbsp;</DIV></DIV></DIV><!-- END TOC --></DIV></DIV>
--0-1557488497-1104211070=:50449--


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

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

--===============1414186245==--



From dhcwg-bounces@ietf.org  Tue Dec 28 11:08:46 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07315
	for <dhcwg-web-archive@ietf.org>; Tue, 28 Dec 2004 11:08:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjK4t-0006Ik-BC
	for dhcwg-web-archive@ietf.org; Tue, 28 Dec 2004 11:20:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjJmt-00068s-2W; Tue, 28 Dec 2004 11:01:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjJbx-0003ho-DA
	for dhcwg@megatron.ietf.org; Tue, 28 Dec 2004 10:50:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06365
	for <dhcwg@ietf.org>; Tue, 28 Dec 2004 10:50:10 -0500 (EST)
Received: from smtp.inet.fi ([192.89.123.192])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjJmt-0005q8-CZ
	for dhcwg@ietf.org; Tue, 28 Dec 2004 11:01:31 -0500
Received: from [194.142.21.49] (gingerale.mit.sonera.com [194.142.21.49])
	by smtp.inet.fi (Postfix) with ESMTP
	id 95B325B95A; Tue, 28 Dec 2004 17:50:10 +0200 (EET)
Message-ID: <41D180AF.4060204@teliasonera.com>
Date: Tue, 28 Dec 2004 17:50:07 +0200
From: Jyrki Soini <jyrki.soini@teliasonera.com>
Organization: TeliaSonera Finland
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dhcwg@ietf.org, volz@cisco.com
X-Enigmail-Version: 0.89.5.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: multipart/mixed; boundary="------------070807040200070908060104"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Subject: [dhcwg] Comments on draft-ietf-dhc-fqdn-option-08.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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6

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

The new version of draft is much easier to read, especially the flag 
field description.

Here are some comments:

3. The Client FQDN Option

    Clients MAY send the Client FQDN option, setting appropriate Flags
    values, in both their DHCPDISCOVER and DHCPREQUEST messages.  If a
    client sends the Client FQDN option in its DHCPDISCOVER message, it
    MUST send the option in subsequent DHCPREQUEST messages.

- May client change the FQDN or flags between DHCPDISCOVER and
   DHCPREQUEST messages?

    Only one FQDN MAY appear in a message.  As per [13], multiple
    instances of this option in a message SHOULD be concatentated.

- ... As per [13] option may be splitted during encoding and later
   multiple instance of this option in a message SHOULD( or MUST) be
   concatenated in decode phase.

3.1 The Flag Field

    ... 0 indicates
    a now deprecated ASCII encoding.  Servers MUST use the same encoding
    as received from the client.

- Could clarify this by copying from 3.3.1:
    "Servers that are not prepared to
    return an ASCII encoded version MUST ignore the Client FQDN option 
(if the "E" bit is 0)."

    ... Server implementers SHOULD note that
    earlier draft versions of this specification permitted an ASCII
    encoding of the domain name and this encoding MUST be used if the "E"
    bit is 0.

- Use of SHOULD? I would delete "Server implementers SHOULD note that"
   and start: "Earlier draft versions..."

3.3.1  Deprecated ASCII Encoding

    The DNS encoding specified above MUST be supported by DHCP servers.

- This sentence is in wrong chapter.

    ... Server implementations SHOULD be aware that clients which ...
    ... Server implementers SHOULD also be aware that some client
    software could be using UTF-8 [9] character encoding.

- Use of SHOULD?

5.1  When to Perform DNS Updates

    If the server's A RR DNS update does not complete until after the
    server has replied to the DHCP client, the server's interaction with
    the DNS server MAY cause the DHCP server to change the domain name
    that it associates with the client.  This can occur, for example, if
    the server detects and resolves a domain-name conflict [6].  In such
    cases, the domain name that the server returns to the DHCP client
    would change between two DHCP exchanges.

- Should the server send a new DHCPACK message once it notices FQDN change?

--
Jyrki


--------------070807040200070908060104
Content-Type: text/x-vcard; charset=utf-8;
 name="jyrki.soini.vcf"
Content-Disposition: attachment;
 filename="jyrki.soini.vcf"
Content-Transfer-Encoding: 7bit

begin:vcard
fn:Jyrki Soini
n:Soini;Jyrki
org:Technology and Software Development;Emerging Technologies and Innobations
adr:P.O.Box 935;;TeliaSonera Finland;Helsiniki;;FI-00051;Finland
email;internet:jyrki.soini@teliasonera.com
title:Chief Network Architect
tel;work:+358 2040 64725
tel;fax:+358-2040-54081
tel;cell:+358 40 722 1119
x-mozilla-html:FALSE
version:2.1
end:vcard


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

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

--------------070807040200070908060104--



From dhcwg-bounces@ietf.org  Wed Dec 29 16:08:47 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13224
	for <dhcwg-web-archive@ietf.org>; Wed, 29 Dec 2004 16:08:46 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjlF0-0001Ag-W9
	for dhcwg-web-archive@ietf.org; Wed, 29 Dec 2004 16:20:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjkjL-0005zr-N7; Wed, 29 Dec 2004 15:47:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjkZM-0000lC-W5; Wed, 29 Dec 2004 15:37:21 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09002;
	Wed, 29 Dec 2004 15:37:19 -0500 (EST)
Message-Id: <200412292037.PAA09002@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 29 Dec 2004 15:37:19 -0500
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-bcmcv4-option-00.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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86

--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		: DHCPv4 Options for Broadcast and Multicast Control Servers
	Author(s)	: K. Chowdhury, et al.
	Filename	: draft-ietf-dhc-bcmcv4-option-00.txt
	Pages		: 12
	Date		: 2004-12-29
	
This document defines new options for Broadcast and Multicast Service
   controller discovery in an IP network.  Broadcast service is being
   developed for 3G wireless networks.  Users of the service interact
   with a controller in the network to derive informations that are
   required to receive broadcast service.  Dynamic Host Configuration
   Protocol can be used to configure the controller IPv4 addresses or
   fully qualified domain names in the user's devices.  This document
   defines the related options and option codes.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-bcmcv4-option-00.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-bcmcv4-option-00.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-bcmcv4-option-00.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: <2004-12-29153953.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dhc-bcmcv4-option-00.txt

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

Content-Type: text/plain
Content-ID: <2004-12-29153953.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From dhcwg-bounces@ietf.org  Wed Dec 29 16:11:44 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14060
	for <dhcwg-web-archive@ietf.org>; Wed, 29 Dec 2004 16:11:44 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CjlHs-0001To-7J
	for dhcwg-web-archive@ietf.org; Wed, 29 Dec 2004 16:23:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjkjO-000627-4J; Wed, 29 Dec 2004 15:47:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CjkZk-0000zj-0t; Wed, 29 Dec 2004 15:37:44 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09022;
	Wed, 29 Dec 2004 15:37:42 -0500 (EST)
Message-Id: <200412292037.PAA09022@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Wed, 29 Dec 2004 15:37:42 -0500
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D ACTION:draft-ietf-dhc-bcmcv6-option-00.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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Dynamic Host Configuration Working Group of the IETF.

	Title		: DHCPv6 Options for Broadcast and Multicast Control Servers
	Author(s)	: K. Chowdhury, et al.
	Filename	: draft-ietf-dhc-bcmcv6-option-00.txt
	Pages		: 14
	Date		: 2004-12-29
	
This document defines new options for Broadcast and Multicast Service
   controller discovery in an IP network.  Broadcast and Multicast
   service over 3G wireless networks are being developed at the time of
   writing this document.  Users of this service interact with a
   controller in the network to derive informations that are required to
   receive broadcast service.  Dynamic Host Configuration Protocol can
   be used to configure the controller IPv6 addresses in the user's
   devices.  This document defines the related options and option codes.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-bcmcv6-option-00.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-bcmcv6-option-00.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-bcmcv6-option-00.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: <2004-12-29154000.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-dhc-bcmcv6-option-00.txt

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

Content-Type: text/plain
Content-ID: <2004-12-29154000.I-D@ietf.org>


--OtherAccess--

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

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

--NextPart--





From dhcwg-bounces@ietf.org  Wed Dec 29 20:05:14 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA07282
	for <dhcwg-web-archive@ietf.org>; Wed, 29 Dec 2004 20:05:14 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cjovr-0000SA-Hz
	for dhcwg-web-archive@ietf.org; Wed, 29 Dec 2004 20:16:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cjoer-0000tO-LJ; Wed, 29 Dec 2004 19:59:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CjobA-0000DY-Cd
	for dhcwg@megatron.ietf.org; Wed, 29 Dec 2004 19:55:28 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06777
	for <dhcwg@ietf.org>; Wed, 29 Dec 2004 19:55:27 -0500 (EST)
Received: from [210.22.146.172] (helo=asbmx.sbell.com.cn)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CjomC-0000Gs-NA
	for dhcwg@ietf.org; Wed, 29 Dec 2004 20:07:04 -0500
Received: from asbwebshld.sbell.com.cn (asbwebshld [172.24.208.38])
	by asbmx.sbell.com.cn (8.12.10+Sun/8.12.3) with SMTP id iBU0mhhi005238
	for <dhcwg@ietf.org>; Thu, 30 Dec 2004 08:48:45 +0800 (CST)
Received: FROM bellnet-mail4.sbell.com.cn BY asbwebshld.sbell.com.cn ;
	Thu Dec 30 08:54:12 2004 +0800
Received: from BELLNET-MAIL3.sbell.com.cn ([172.24.208.23]) by
	bellnet-mail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.6713); 
	Thu, 30 Dec 2004 08:54:05 +0800
content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Date: Thu, 30 Dec 2004 08:50:52 +0800
Message-ID: <8634B809B90D6E4AACA4AB0562A1F07205EE13@bellnet-mail3.sbell.com.cn>
Thread-Topic: Updated draft-yan-dhc-dhcpv6-opt-dnszone-02.txt 
Thread-Index: AcTuCZyDEgDBDthmRYycGeEQwtQRUw==
From: "CTO YAN Renxiang" <Renxiang.Yan@alcatel-sbell.com.cn>
To: <dhcwg@ietf.org>
X-OriginalArrivalTime: 30 Dec 2004 00:54:05.0614 (UTC)
	FILETIME=[0FD864E0:01C4EE0A]
X-Spam-Score: 0.5 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Subject: [dhcwg] Updated draft-yan-dhc-dhcpv6-opt-dnszone-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>
Content-Type: multipart/mixed; boundary="===============0610443722=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: a8a20a483a84f747e56475e290ee868e

This is a multi-part message in MIME format.

--===============0610443722==
content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C4EE09.9C8732E6"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4EE09.9C8732E6
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

Hi all,

I've just submitted a revised version of the DNS zone option for DHCPv6,
(currently available at
 =
<http://www.ietf.org/internet-drafts/draft-yan-dhc-dhcpv6-opt-dnszone-02.=
txt> =
http://www.ietf.org/internet-drafts/draft-yan-dhc-dhcpv6-opt-dnszone-02.t=
xt )
=20
Thanks to those that provided comments to this draft over the past =
several weeks, especially Ralph and Bernie.
=20
Main difference with version -01 is that "this option can used both in =
stateless DHCPv6 and stateful DHCPv6, when used in stateful DHCPv6, it =
must be combined with IA_PD option."
=20
Please take a look at them and provide comments. I'd like to request =
this draft to become DHC WG work items.

-Renxiang Yan

------_=_NextPart_001_01C4EE09.9C8732E6
Content-Type: text/html;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dgb2312">


<META content=3D"MSHTML 6.00.2800.1458" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D263314100-30122004><FONT size=3D2>Hi =
all,</FONT></SPAN></DIV>
<DIV><FONT size=3D2></FONT><BR><FONT size=3D2>I've just submitted a =
revised version=20
of the&nbsp;<SPAN class=3D263314100-30122004>DNS =
zone</SPAN>&nbsp;option<SPAN=20
class=3D263314100-30122004> for DHCPv6,</SPAN><BR>(<SPAN=20
class=3D263314100-30122004>currently</SPAN> available at<BR></FONT><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-yan-dhc-dhcpv6-opt-dnsz=
one-02.txt"><FONT=20
size=3D2>http://www.ietf.org/internet-drafts/draft-yan-dhc-dhcpv6-opt-dns=
zone-02.txt</FONT></A><FONT=20
size=3D2>&nbsp;<SPAN class=3D263314100-30122004>)</SPAN></FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Thanks to those that provided comments&nbsp;<SPAN=20
class=3D263314100-30122004>to</SPAN> this draft over the<SPAN=20
class=3D263314100-30122004> </SPAN>past several weeks, =
especially&nbsp;<SPAN=20
class=3D263314100-30122004>Ralph and Bernie.</SPAN></FONT></DIV>
<DIV><FONT size=3D2><SPAN =
class=3D263314100-30122004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2><SPAN class=3D263314100-30122004></SPAN></FONT><FONT =

size=3D2><SPAN class=3D263314100-30122004>Main difference with version =
-01 is that=20
"this option can used both in stateless DHCPv6 and stateful DHCPv6, when =
used in=20
stateful DHCPv6, it must be combined with&nbsp;IA_PD=20
option."</SPAN></FONT></DIV>
<DIV><SPAN class=3D263314100-30122004></SPAN>&nbsp;</DIV>
<DIV><FONT size=3D2>Please take a look at them and provide comments. I'd =
like to=20
request&nbsp;<SPAN class=3D263314100-30122004>this draft </SPAN>to =
become DHC WG=20
work items.<BR></FONT></DIV>
<DIV><SPAN class=3D263314100-30122004><FONT size=3D2>-Renxiang=20
Yan</FONT></SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C4EE09.9C8732E6--


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

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

--===============0610443722==--



From dhcwg-bounces@ietf.org  Thu Dec 30 15:08:45 2004
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11740
	for <dhcwg-web-archive@ietf.org>; Thu, 30 Dec 2004 15:08:45 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Ck6mG-0001ml-CL
	for dhcwg-web-archive@ietf.org; Thu, 30 Dec 2004 15:20:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Ck6Pf-00069N-KZ; Thu, 30 Dec 2004 14:56:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Ck6Od-0005xL-RH
	for dhcwg@megatron.ietf.org; Thu, 30 Dec 2004 14:55:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10736
	for <dhcwg@ietf.org>; Thu, 30 Dec 2004 14:55:42 -0500 (EST)
Received: from kaboom.isc.org ([204.152.187.72])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ck6a1-0001U9-3O
	for dhcwg@ietf.org; Thu, 30 Dec 2004 15:07:30 -0500
Received: by kaboom.isc.org (Postfix, from userid 10200)
	id B048BB246C; Thu, 30 Dec 2004 11:55:06 -0800 (PST)
Date: Thu, 30 Dec 2004 11:55:06 -0800
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] dhc WG last call on draft-ietf-dhc-3315id-for-v4
Message-ID: <20041230195506.GB43137@isc.org>
References: <4.3.2.7.2.20041216071507.01f91220@flask.cisco.com>
Mime-Version: 1.0
In-Reply-To: <4.3.2.7.2.20041216071507.01f91220@flask.cisco.com>
User-Agent: Mutt/1.4.2.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
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="===============1408331036=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 386e0819b1192672467565a524848168


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


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

A few cosmetic errors I may as well mention first;

In the Introduction, there are newlines where they don't belong;

>  regardless of the version of DHCP they are using at any given
>
>
>  moment.  Most obviously, DNS updates made by the DHCP server on

In section 3 (Requirements):

>  - It must be possible, in cases where the DHCPv4 client is
>    expressing more than one network identity at the same time, it
>    must nevertheless be possible for the DHCPv4 server to determine
>    that the two network identities belong to the same host.

The language is redundant, and confuses the point.


In section 4.4, we have a less trivial problem:

>  The text in section 9.14, beginning with "The client identifier MAY
>  consist of" through "that meet this requirement for uniqueness." is
>  replaced with "the client identifier consists of a type field whose
>  value is normally 255, followed by a two-byte type field, followed
>  by the contents of the identifier.  The two-byte type field and the
>  format of the contents of the identifier are defined in RF3315,
>  section 9."  The text "its minimum length is 2" in the following
>  paragraph is deleted.

The one-byte type field (normally 255) is followed by a two-byte type
field?

In section 4.1 we were told the option looked like this:

>     Code  Len  Type  IAID                DUID
>     +----+----+-----+----+----+----+----+----+----+---
>     | 61 | n  | 255 | i1 | i2 | i3 | i4 | d1 | d2 |...
>     +----+----+-----+----+----+----+----+----+----+---

Which contradicts what we were just told section 4.4.  I think the
author meant that the DUID starts with a 2-byte type field, but the
DUID contents are never defined in this draft (it always refers to
rfc3315 section 9), so probably this just shouldn't be mentioned.

Because of this last bit, I don't think this draft should be advanced.

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

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (FreeBSD)

iD8DBQFB1F0acXeLeWu2vmoRAscDAKCpGEvBQQNimBafYeSTHj+tMP0boACfcOJR
lzWtL3sbdWtFWGAa7KXr6i0=
=PfSY
-----END PGP SIGNATURE-----

--UlVJffcvxoiEqYs2--


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

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

--===============1408331036==--



