From dhcwg-bounces@ietf.org Mon Apr 03 13:25:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FQSo2-0007gR-OT; Mon, 03 Apr 2006 13:25:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FQSo1-0007gM-8j
	for dhcwg@ietf.org; Mon, 03 Apr 2006 13:25:33 -0400
Received: from oak.research.panasonic.com ([150.169.1.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FQSo0-00047l-0B
	for dhcwg@ietf.org; Mon, 03 Apr 2006 13:25:33 -0400
Received: from redwood.research.panasonic.com (redwood.research.panasonic.com
	[150.169.3.3])
	by oak.research.panasonic.com (1.1.1/1.1.1) with ESMTP id
	k33HPFrs019757; Mon, 3 Apr 2006 13:25:15 -0400
Received: from [150.169.1.225] (dhcp225.Research.Panasonic.COM [150.169.1.225]
	(may be forged)) by redwood.research.panasonic.com (MOS 3.7.4b-GA)
	with ESMTP id AEO26084; Mon, 3 Apr 2006 13:24:18 -0400 (EDT)
Message-ID: <44315A7C.10405@research.panasonic.com>
Date: Mon, 03 Apr 2006 13:25:16 -0400
From: Greg Daley <gregd@research.panasonic.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: Andrea G Forte <andreaf@cs.columbia.edu>
Subject: Re: [dhcwg] draft-forte-dhc-passive-dad-01
References: <4416F10C.2000703@cs.columbia.edu>	<4419DBD9.7010706@research.panasonic.com>
	<441CC7C5.20308@cs.columbia.edu>
	<442D437C.9050406@research.panasonic.com>
	<442DB234.5080605@cs.columbia.edu>
In-Reply-To: <442DB234.5080605@cs.columbia.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: dhcwg@ietf.org, sangho@cs.columbia.edu
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Hi Andrea,

Andrea G Forte wrote:
> Greg,
> 
> please read answers inline.
> 
>> Sorry about the delay in replying.
> No problem at all. I was at the IETF meeting in Dallas.
 > Where you there as well? I would have liked to have your
 > feedback at the meeting after the presentation.

Sorry I couldn't come, my work is less focussed on IPv6
configuration at the moment.


>> Please be aware that the delays for link-local address
>> configuration will not be curtailed for this system,
>> as a link-local address is required to form a DHCP message.
>> For those addresses Optimistic DAD is still needed.
> We never intended pDAD to be a replacement for Optimistic DAD.
> pDAD is meant to address the DAD problem in IPv4 networks. We just 
> wanted to mention that perhaps it could be useful in IPv6 networks as 
> well (with all the limitations we discussed).

Certainly. Sorry I didn't provide feedback earlier about which
limitations are likely to be considered important.

> One thing I wanted to ask you about your last point is that apparently a 
> link-local address would be created mainly according to the client 
> unique ID. Another alternative would be to use something else like a 
> token of some sort. My impression though, would be that the former 
> scenario is more realistic since you want something as unique as possible.

Well, the assumption of uniqueness is not made in IPv6.  DAD is still
performed on all unicast addresses (It may seem like a waste, but it's
a MUST in Section 5.4 of RFC2462 and draft-ietf-ipv6-rfc2462bis-08,
and a MUST be supported in 4.2 and 4.5.2 of
draft-ietf-ipv6-node-requirements-11)...

Please also note that not all IPv6 link-local addresses are generated
from MAC addresses (and not even those are totally unique).

The problem with tokens is that you only want to modify 'clever' nodes
which understand your optimization without requiring changes from
'not so clever' nodes which share the same link.

Probably the best you can do is to restrict 'not so clever' nodes
using existing IPv6 operations (like preventing auto configuration
M=1, A=0).  This doesn't change their autoconfiguration and DAD
operations on the link-local addresses today, since the Autonomous
configuration (A) flags and procedures are prefix-associated.

As such a 'clever' host or system will still interact with hosts
that are performing DAD for autonomously configured link-local.
Today that's achieveable using Opti-DAD for the LL address (there
are other ways though...).


Greg

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



From dhcwg-bounces@ietf.org Mon Apr 03 22:24:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FQbDZ-0001oh-5W; Mon, 03 Apr 2006 22:24:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FQbDX-0001ob-RK
	for dhcwg@ietf.org; Mon, 03 Apr 2006 22:24:27 -0400
Received: from ns.64translator.com ([202.214.123.16])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FQbDW-0003tp-9L
	for dhcwg@ietf.org; Mon, 03 Apr 2006 22:24:27 -0400
Received: from bahamas.64translator.com ([10.21.32.3])
	by ns.64translator.com (8.13.1/8.13.1) with ESMTP id k342ONRV039416;
	Tue, 4 Apr 2006 11:24:23 +0900 (JST)
	(envelope-from Hideshi.Enokihara@jp.yokogawa.com)
Received: from thinkpad.64translator.com (dhcp248.64translator.com
	[10.21.32.248])
	by bahamas.64translator.com (8.13.1/8.13.1) with SMTP id k342OEs7072285;
	Tue, 4 Apr 2006 11:24:14 +0900 (JST)
	(envelope-from Hideshi.Enokihara@jp.yokogawa.com)
Date: Tue, 4 Apr 2006 11:22:49 +0900
From: Hideshi Enokihara <Hideshi.Enokihara@jp.yokogawa.com>
To: "Ralph Droms" <rdroms@cisco.com>
Subject: Re: [dhcwg] [Question]Is this behavior of the Reconfigure Key
	Authentication Protocol correct?
Message-Id: <20060404112249.4b8fc617.Hideshi.Enokihara@jp.yokogawa.com>
In-Reply-To: <C053349B.13D7F%rdroms@cisco.com>
References: <20060310210905.4603a74d.Hideshi.Enokihara@jp.yokogawa.com>
	<C053349B.13D7F%rdroms@cisco.com>
Organization: Yokogawa Electric Corporation
X-Mailer: Sylpheed version 1.0.5 (GTK+ 1.2.10; i386-portbld-freebsd4.9)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed 
	version=3.0.1
X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on 
	bahamas.64translator.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Hello Mr. Ralph Droms,

Thank you for your reply.

I could get correct understanding.

Best Regards,
On Sat, 1 Apr 2006 09:33:47 +0900
"Ralph Droms" <rdroms@cisco.com> wrote:

> Re: [dhcwg] [Question]Is this behavior of the Reconfigure Key Authentication Protocol correct?
> 
> Hideshi-san - Your observaation is correect: the authentication key for
> reconfiguration assumes that the key cannot be intercepted and used for
> sending malicious Reconfigure messages.
> 
> - Ralph
> 
> 
> On 3/10/06 7:09 AM, "Hideshi Enokihara" <Hideshi.Enokihara@jp.yokogawa.com>
> wrote:
> 
> > Hi all,
> >
> > I have some questions regarding Reconfigure Key Authentication Protocol.
> >
> > Is this behavior(like following) of the Reconfigure Key Authentication
> > Protocol correct?
> > ---------------------------------
> >
> >        Server  Client
> >         |       |
> >         |       |
> >         | <---- | Solicit
> >         | ----> | Advertise
> >         | <---- | Request with Reconfigure Accept Option
> >         | ----> | Reply with Reconfigure Accept Option
> >         |       |       and Authentication Option  (*1)
> >         |       |
> >         |       |
> >         | ----> | Reconfigure with comptuted Authentication (*2)
> >         | <---- | Renew or Information-Request (*3)
> >         |       |  (depend on Reconfigure message's(*2's) msg-type)
> >         | ----> | Reply (*4)
> >
> > (*1):The server transmits the 128 bits Reconfigure Key
> >      in Authentication option to the clinet.
> > (*2):The server computes an HMAC-MD5 of the Reconfigure message
> >      using the Reconfigure Key and includes the HMAC-MD5
> >      in the authentication information field in an Authentication option
> >      included in the Reconfigure message sent to the client.
> > (*3):To authenticate a Reconfigure message, the client computes
> >      an HMAC-MD5 over the DHCP Reconfigure message,
> >      using the Reconfigure Key received from the server,
> >      and the client transmits the Renew or Information-Request message
> >      without Authentication option to the Server.
> > (*4):The server transmits the Reply message without Authentication option.
> > ---------------------------------------
> > [Question1]
> > Is this behavior correct?
> >
> >
> > If this behavior is correct, I also have a question in step (*1).
> >
> > [Question2]
> > If a malicious DHCP server intercepts the Reply message(*1),
> > the malicious DHCP server can get Reconfigure Key, I think.
> > Then, the malicious DHCP server can send the Reconfigure message with
> > fallacious information.
> >
> > If this situation happens, I think that the effectiveness of Reconfigure Key
> > Authentication Protocol is lost.
> >
> > What do you think?
> > What is the purpose of Reconfigure Key Authentication Protocol?
> >
> > Best Regards,


-- 
*************************************
Hideshi Enokihara
IPv6 Business
Network & Software Development Dept.
Yokogawa Electric Corporation

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



From dhcwg-bounces@ietf.org Mon Apr 10 18:29:05 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FT4sW-0006BL-Sp; Mon, 10 Apr 2006 18:29:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FT4sV-0006BB-Is
	for dhcwg@ietf.org; Mon, 10 Apr 2006 18:28:59 -0400
Received: from kaboom.isc.org ([204.152.187.72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FT4sV-0008CC-28
	for dhcwg@ietf.org; Mon, 10 Apr 2006 18:28:59 -0400
Received: by kaboom.isc.org (Postfix, from userid 10200)
	id 9C3BDD1A40; Mon, 10 Apr 2006 15:28:57 -0700 (PDT)
Date: Mon, 10 Apr 2006 15:28:57 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Message-ID: <20060410222857.GE8352@isc.org>
Mime-Version: 1.0
User-Agent: Mutt/1.5.9i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25eb6223a37c19d53ede858176b14339
Subject: [dhcwg] Timezones again.
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="===============0712194094=="
Errors-To: dhcwg-bounces@ietf.org


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


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

First, on the subject of "imagined clients."

In the past week and change, I've been talking on this subject with
anyone who will listen.  I've been told I'm out of touch with users
needs by at least one individual, and that's not an acceptable thing
to even question.  Certainly, I am not unbiased on the subject.

I've talked with Jason Vas Dias who works on DHCP software distribution
stuff at Redhat (but his views aren't necessarily those of his
employer's).  He imparted to me a story that, in his corner of the
world, the TZ database did not have what he needed.  To get the correct,
current wall-clock time on their DHCP-connected systems, they actually
did use the time offset option (code 2) (hacking ISC "dhclient-script"
to do so) to set the wall clock.  This was done combining a fixed offset
=66rom UTC TZ database entry, and using the time-offset field as a server-
supplied means of determining what he called "the political timezone."
This worked, because the DHCP server could be reconfigured with the
correct political time offset when the correct time to do so transpires
=2E..and lease expiration timers could be reduced in advance so that
clients renewed their bindings shortly thereafter.

I've also talked with Mark Andrews, who after returning to Australia
after IETF 65 found himself in a taxi cab on the way home.  His
cell phone, his taxi driver, and his wife all disagreed on what the
correct local time was.  All because DST had been delayed a week due
to a game (cricket, I think).  The TZ database on his laptop would
also have had the wrong local wall-clock time, and that this would
have been an undesirable third false indicator.

I've also talked with a few Unix systems administrators, and no, they
don't all work at ISC.  One, Majdi Abbas at salesforce.com (whose
opinions are also not those of his employer's), refused to discuss this
option at all until I had entertained a lengthy rant from him on the
subject of the stupidity of DST and politicizing timezones.  A rant I
can't disagree with, and if we could simply do away with timezones
entirely and all live happily in UTC, I'd be for that.

But last I checked, we don't yet have that kind of power.  Yet.

I was just thinking to myself that this crossection of individuals
rather well represents our, that is ISC's, DHCP users, from vendors
who redistribute our products to actual end-users in the trenches...
which is who I was out to ask about this subject.  It doesn't really
slice into the area of experts in the field of network time, who might
be privvy to some secret knowledge the rest of us are ignorant to.

Then, while I was still editing this very email, I found myself lucky
enough to be sharing a table at lunch with Harlan Stenn, whose work on
the NTP Public Services Project might not need introduction.  I think
he qualifies as an expert in the field.

We were trying to have a technical conversation shouting at each other
over the dinn at a Red Robin (tm), and the conversation was audible...
that is not digital eg email or similar, so I don't have any notes to
quote directly.

It also may simply have been his desire to return to his burger and
get me out of his face, but he emitted nothing short of fundamental
agreement.  Certainly, I got no hint that some knowledge hidden to us
about time and history makes current correct wall-clock time undesirable
in comparison.

And if any of us weren't in on Time's Terrible Secret, certainly he
would be.


The consensus of these encounters, is: servers care about historic
time, but it's a 50/50 toss-up as to wether current wall-clock time is
more important or not.  It might be in some cases, isn't in others.
They are also generally not DHCP configured, but rather most sysadmins
favor statically configuring each server.  One less element of the
network to fail.  Desktops?  Laptops?  Historic time is irrelevant
compared to having the desktop clock emit the correct local wall-clock
time.


So, upon these reflections, I reaffirm that for most DHCP configured
devices, correct current local "wall clock" time is more important
than complete historic record of correct wall clock time.  What time
it is now is substantially more important than what time it was
yesterday to the vast majority of devices using DHCP to configure.

The way you get that is by picking one of TZ or POSIX formats, and
preferring it...but not to the exclusion of the other if only one
of the two is available.

And I reject any statement that the needs presented by these
'imaginary' clients don't exist.  Quite the contrary, they will
be the primary consumer.


So.

We have one thing, the local timezone, and three different ways of
digesting it.

We have clients that will happily digest multiple encodings, taking
the 'best' of what is offered.  I measure these to be the majority
of clients.  A subset of these may wish to actually receive multiple
encodings in order to compare them to determine which is best, but
we can't tell how many; probably not a lot as it is fairly hard
to compare two different encodings meaningfully.

We have clients that will only digest a single encoding, making
transmission of the others a waste of DHCP payload space, and
'sub-options' extra overhead.  I measure these to be the minority
of clients, but in those places where the need is real it is
crippling (eg, a phone or similar 'small' embedded device, despite
the fact that no phone DHCP stack implementors have yet to speak
up on this topic on this list referring to their needs).


We judge that it is a waste of space to send these option contents
if the client doesn't support the encoding method.  We must also
judge that it is a waste of space to send these option contents if
the client supports more than one encoding method but it will only
select one to use.

The former is obviously problematic, even rediculous.  But, it
represents a corner case, entered into by the minority of clients
that support only one of the three formats without supporting a
fallback for the POSIX string.

The latter, however, is what I perceive to be the general case.

So if solving the problematic corner case is so important we must
elide from suboptions to individual options, then how important is
the general case to solve?

Substantially more important I think.


So in summary, without typing too much more (I think I'm over quota
already), I think that if we resolve that this waste of space is
unacceptably high, we must solve the general form of the identical
waste before solving the corner case form.

With a brief footnote that the 'compatible-request-list' I floated
last message isn't the way to do that, with the format of the
options we have today (note the subset of clients that desire more
than one format to compare).

More on this after I feel I haven't typed enough re: where do we go
=66rom here.

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

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

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

iD8DBQFEOtwocXeLeWu2vmoRApZJAJ9sQqZE0WsUfAKTWNWz8PYfH66ZxQCgqFQs
EwLXD7VCWC2Q487wcMjE3P8=
=omqq
-----END PGP SIGNATURE-----

--cYtjc4pxslFTELvY--


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

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

--===============0712194094==--




From dhcwg-bounces@ietf.org Mon Apr 10 18:48:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FT5B0-0004Kb-HX; Mon, 10 Apr 2006 18:48:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FT5Az-0004KW-Vr
	for dhcwg@ietf.org; Mon, 10 Apr 2006 18:48:05 -0400
Received: from kaboom.isc.org ([204.152.187.72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FT5Ay-0000Eo-NO
	for dhcwg@ietf.org; Mon, 10 Apr 2006 18:48:05 -0400
Received: by kaboom.isc.org (Postfix, from userid 10200)
	id 332DD1A6A11; Mon, 10 Apr 2006 15:48:03 -0700 (PDT)
Date: Mon, 10 Apr 2006 15:48:03 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Message-ID: <20060410224803.GG8352@isc.org>
Mime-Version: 1.0
User-Agent: Mutt/1.5.9i
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Subject: [dhcwg] draft-dhankins-pxelinux-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>
Content-Type: multipart/mixed; boundary="===============0772335026=="
Errors-To: dhcwg-bounces@ietf.org


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


--f5QefDQHtn8hx44O
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

draft-dhankins-pxelinux-00.txt, describing the once-site-local options
currently in use by the PXELinux bootloader is now available:

	http://www.ietf.org/internet-drafts/draft-dhankins-pxelinux-00.txt

Your comments will be wrapped in gossamer ribbons and cherished upon
the mantlepiece of my home.

OK not really.

This is a stake in the sand.  I want some feedback on what to do with one
of the options if you care to have an opinion.

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

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

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

iD8DBQFEOuCjcXeLeWu2vmoRAjoPAJ9dh9x289SArzJNNTHKHl3HtBPd5ACfUXYN
muiVf/RGb4qe39SKkhTjDbs=
=9oKT
-----END PGP SIGNATURE-----

--f5QefDQHtn8hx44O--


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

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

--===============0772335026==--




From dhcwg-bounces@ietf.org Mon Apr 10 18:56:19 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FT5It-0002hP-SC; Mon, 10 Apr 2006 18:56:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FT5Ir-0002hK-VT
	for dhcwg@ietf.org; Mon, 10 Apr 2006 18:56:13 -0400
Received: from shell-ng.nominum.com ([81.200.64.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FT5Io-0000qK-E2
	for dhcwg@ietf.org; Mon, 10 Apr 2006 18:56:13 -0400
Received: from vpn-38.vpn.nominum.com (vpn-38.vpn.nominum.com [128.177.199.38])
	(using SSLv3 with cipher EXP1024-RC4-SHA (56/128 bits))
	(Client did not present a certificate)
	by shell-ng.nominum.com (Postfix) with ESMTP id 9170456835
	for <dhcwg@ietf.org>; Mon, 10 Apr 2006 15:56:09 -0700 (PDT)
	(envelope-from Ted.Lemon@nominum.com)
From: Ted Lemon <Ted.Lemon@nominum.com>
Organization: Nominum, Inc.
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Timezones again.
Date: Mon, 10 Apr 2006 15:56:04 -0700
User-Agent: KMail/1.9.1
References: <20060410222857.GE8352@isc.org>
In-Reply-To: <20060410222857.GE8352@isc.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200604101556.04459.Ted.Lemon@nominum.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d62ab47271805379d7172ee693a45db
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Forgive me for giving you a pithy one-paragraph response, David, but it sounds 
llike the status quo (time zone offset) is actually perfectly fine for you, 
and that you do not need this new option we're discussing.  I realize, 
though, that that's not what you actually said.   Is there any truth to this 
conjecture of mine?

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



From dhcwg-bounces@ietf.org Mon Apr 10 19:36:00 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FT5vI-0003t8-W6; Mon, 10 Apr 2006 19:35:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FT5vI-0003t3-5H
	for dhcwg@ietf.org; Mon, 10 Apr 2006 19:35:56 -0400
Received: from kaboom.isc.org ([204.152.187.72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FT5vG-0002IZ-SV
	for dhcwg@ietf.org; Mon, 10 Apr 2006 19:35:56 -0400
Received: by kaboom.isc.org (Postfix, from userid 10200)
	id 002901A45C0; Mon, 10 Apr 2006 16:35:53 -0700 (PDT)
Date: Mon, 10 Apr 2006 16:35:53 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Timezones again.
Message-ID: <20060410233553.GH8352@isc.org>
References: <20060410222857.GE8352@isc.org>
	<200604101556.04459.Ted.Lemon@nominum.com>
Mime-Version: 1.0
In-Reply-To: <200604101556.04459.Ted.Lemon@nominum.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
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="===============1034800946=="
Errors-To: dhcwg-bounces@ietf.org


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


--h3LYUU6HlUDSAOzy
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Apr 10, 2006 at 03:56:04PM -0700, Ted Lemon wrote:
> Forgive me for giving you a pithy one-paragraph response, David, but it sounds 
> llike the status quo (time zone offset) is actually perfectly fine for you, 
> and that you do not need this new option we're discussing.  I realize, 
> though, that that's not what you actually said.   Is there any truth to this 
> conjecture of mine?

The status quo is actually perfectly fine for Jason Vas Dias, in DHCPv4
(he even said that).

I think the options suggested by Elliot provide some utility for people
who are not Jason but would also cover his needs and also be more
complete (rather than merely being the hammer he happened to have in his
toolbox at the time, and has now grown inseparable from).

You see, any new option, no matter what we do, will be work for him to
adopt.  He's busy enough as it is.


So the lack of status quo in DHCPv6 is again defined as the primary
problem.

But, hypothetically, if we were designing protocol for Jason's set of
problems as being representative of the majority of clients needs, then
Ralph's original draft is provably an adequate solution.

I think Elliot explicitly stipulates that there is a larger problem
set to solve for, that we can do better than merely adequate, and
that's where we're getting hung up.

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

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

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

iD8DBQFEOuvZcXeLeWu2vmoRAiUTAKCKN0v0FJB0gn8A+/ZBiqUEoYRNdgCdGmNN
qvNlatCY54V61vNZL8KXLeI=
=OAsa
-----END PGP SIGNATURE-----

--h3LYUU6HlUDSAOzy--


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

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

--===============1034800946==--




From dhcwg-bounces@ietf.org Mon Apr 10 19:59:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FT6IF-00044M-2V; Mon, 10 Apr 2006 19:59:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FT6IE-00044H-GX
	for dhcwg@ietf.org; Mon, 10 Apr 2006 19:59:38 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FT6ID-0003A2-9M
	for dhcwg@ietf.org; Mon, 10 Apr 2006 19:59:38 -0400
Received: from rtp-core-2.cisco.com ([64.102.124.13])
	by rtp-iport-1.cisco.com with ESMTP; 10 Apr 2006 16:59:37 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.04,109,1144047600"; 
	d="scan'208"; a="25602566:sNHT24177412"
Received: from [68.48.124.149] (rtp-vpn4-229.cisco.com [10.82.208.229])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k3ANxaVU020321; 
	Mon, 10 Apr 2006 19:59:36 -0400 (EDT)
In-Reply-To: <200604101556.04459.Ted.Lemon@nominum.com>
References: <20060410222857.GE8352@isc.org>
	<200604101556.04459.Ted.Lemon@nominum.com>
Mime-Version: 1.0 (Apple Message framework v623)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <c7f55212645e48d56802ecac5da7f947@cisco.com>
Content-Transfer-Encoding: 7bit
From: John Schnizlein <jschnizl@cisco.com>
Subject: Re: [dhcwg] Timezones again.
Date: Mon, 10 Apr 2006 19:59:35 -0400
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.623)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org


On Apr 10, 2006, at 6:56 PM, Ted Lemon wrote:

> Forgive me for giving you a pithy one-paragraph response, David, but 
> it sounds
> llike the status quo (time zone offset) is actually perfectly fine for 
> you,
> and that you do not need this new option we're discussing.  I realize,
> though, that that's not what you actually said.   Is there any truth 
> to this
> conjecture of mine?

Although I will not presume to speak for David about his lack of need, 
I will note that he described different needs and objected to the 
suggestion that his clients are imaginary.

There are at least 3 issues that seem to be entangled tangled here.  
(1) The existing time offset (RFC 2131, option 2) lacks automatic 
changes at occasional times for the (horrible) Daylight Saving 
adjustment.  (2) The TZ database provides lots of historical 
information for hosts that have it (up to date) and lack only the name 
of the entry for where they are.  (3) Different options or sub-options 
of a new multi-purpose option could address issues 1 & 2.

IMHO assertions that all hosts need the name of the time-zone, either 
daylight-saving or otherwise overstates the requirement.  David 
provided examples where clients need just correct wall-clock time.  Of 
all the computers in my house (or pocket), only those with 
general-purpose operating systems bother with this - those with just 
radios, CD players, and/or telephone functions present just the time, 
including the one that "listens" to WWV just display the time.  For 
this set of IP hosts, computers embedded in all sorts of things, simply 
fixing the lack of offset transitions is adequate and appropriated.  
Two new options with 32-bit time values for NextOffset and 
TimeOfNextOffset would satisfy that.

The devotion displayed for the TZ (aka Olsen) database suggests that 
some hosts really want to be given the name (index into the database) 
of their time-zone, and prefer to rely on the entries in that database 
for which offset and display time-zone to display when.  A single new 
option for the name of a Zone entry in the database referred to as the 
TZ (or Olson) database string would satisfy that.

Because which of these kinds of information are useful is different for 
different clients, they should be separate options so that clients can 
choose which to request.

John

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



From dhcwg-bounces@ietf.org Mon Apr 10 20:39:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FT6uY-0001vy-BL; Mon, 10 Apr 2006 20:39:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FT6uW-0001qp-OO
	for dhcwg@ietf.org; Mon, 10 Apr 2006 20:39:12 -0400
Received: from shell-ng.nominum.com ([81.200.64.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FT6uV-0005AH-G3
	for dhcwg@ietf.org; Mon, 10 Apr 2006 20:39:12 -0400
Received: from vpn-38.vpn.nominum.com (vpn-38.vpn.nominum.com [128.177.199.38])
	(using SSLv3 with cipher EXP1024-RC4-SHA (56/128 bits))
	(Client did not present a certificate)
	by shell-ng.nominum.com (Postfix) with ESMTP id 78BF05682D;
	Mon, 10 Apr 2006 17:39:10 -0700 (PDT)
	(envelope-from Ted.Lemon@nominum.com)
From: Ted Lemon <Ted.Lemon@nominum.com>
Organization: Nominum, Inc.
To: John Schnizlein <jschnizl@cisco.com>
Subject: Re: [dhcwg] Timezones again.
Date: Mon, 10 Apr 2006 17:39:07 -0700
User-Agent: KMail/1.9.1
References: <20060410222857.GE8352@isc.org>
	<200604101556.04459.Ted.Lemon@nominum.com>
	<c7f55212645e48d56802ecac5da7f947@cisco.com>
In-Reply-To: <c7f55212645e48d56802ecac5da7f947@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200604101739.07258.Ted.Lemon@nominum.com>
X-Spam-Score: 0.0 (/)
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>
Errors-To: dhcwg-bounces@ietf.org

On Monday 10 April 2006 16:59, John Schnizlein wrote:
> Although I will not presume to speak for David about his lack of need,
> I will note that he described different needs and objected to the
> suggestion that his clients are imaginary.

I won't quote your whole summary, but I think I agree completely both with the 
conclusion you've come to, and the reasons you stated for coming to it.   It 
does indeed sounds like David's needs are fully addressed by the POSIX 
option, and that, based on the needs expressed, he would never need to 
implement the TZ option.

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



From dhcwg-bounces@ietf.org Mon Apr 10 22:20:23 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FT8UI-0005sD-Bl; Mon, 10 Apr 2006 22:20:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FT8UH-0005s8-C4
	for dhcwg@ietf.org; Mon, 10 Apr 2006 22:20:13 -0400
Received: from farside.isc.org ([204.152.187.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FT8UG-0001dJ-3F
	for dhcwg@ietf.org; Mon, 10 Apr 2006 22:20:13 -0400
Received: by farside.isc.org (Postfix, from userid 10200)
	id 3ECFEE6131; Tue, 11 Apr 2006 02:20:11 +0000 (UTC)
Date: Tue, 11 Apr 2006 02:20:11 +0000
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Timezones again.
Message-ID: <20060411022010.GA36572@isc.org>
References: <20060410222857.GE8352@isc.org>
	<200604101556.04459.Ted.Lemon@nominum.com>
	<c7f55212645e48d56802ecac5da7f947@cisco.com>
	<200604101739.07258.Ted.Lemon@nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200604101739.07258.Ted.Lemon@nominum.com>
User-Agent: Mutt/1.4.2.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Mon, Apr 10, 2006 at 05:39:07PM -0700, Ted Lemon wrote:
> I won't quote your whole summary, but I think I agree completely both with the 
> conclusion you've come to, and the reasons you stated for coming to it.   It 
> does indeed sounds like David's needs are fully addressed by the POSIX 
> option, and that, based on the needs expressed, he would never need to 
> implement the TZ option.

I thought I typed 'in the absence of'.  I can't include the entire
discussion from each of them, I tried to cover the highlights, the gist
of the spectrum, and then summarize the consensus of all parties.  The
compromise that meets all their needs.

So:

- Some clients will exist for which, when POSIX is available but TZ is not,
  would prefer to use POSIX rather than nothing at all (but normally would
  prefer TZ).  Think North America, although less so these days, or any
  environment where 'political time zone' is not at the whim of some
  uncontrollable, chaotic, random event: TZ will generally be correct, and
  preferred, POSIX in the absence of TZ (or in the case where it is somehow
  provably inaccurate for wall clock time) is a desirable fall-back position.

- Some clients will exist for which, when TZ is available but POSIX is not,
  would prefer to use TZ rather than nothing at all (but normally would
  prefer to use POSIX because TZ is almost never correct).  I don't actually
  know what geopolitical sphere Jason is operating in, but I imagine he is
  not alone.  Mark Andrews, for example, lives in an environment where
  'political time zone' was decided by wether or not a game had finished.
  TZ in the absence of POSIX is a desirable fall-back position.

I suspect the above two sets will comprise the largest portion of consumers
of these two options.

Our own client will need to fill both needs since our users span both
sides:  Whichever one is present, with a preference applied to one if both
are, that preference being user-selectable.

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

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



From dhcwg-bounces@ietf.org Mon Apr 10 23:58:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTA0u-0003kt-OH; Mon, 10 Apr 2006 23:58:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTA0t-0003kl-CB
	for dhcwg@ietf.org; Mon, 10 Apr 2006 23:57:59 -0400
Received: from shell-ng.nominum.com ([81.200.64.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTA0s-0005Ks-3T
	for dhcwg@ietf.org; Mon, 10 Apr 2006 23:57:59 -0400
Received: from vpn-38.vpn.nominum.com (vpn-38.vpn.nominum.com [128.177.199.38])
	(using SSLv3 with cipher EXP1024-RC4-SHA (56/128 bits))
	(Client did not present a certificate)
	by shell-ng.nominum.com (Postfix) with ESMTP id 34C3656833
	for <dhcwg@ietf.org>; Mon, 10 Apr 2006 20:57:57 -0700 (PDT)
	(envelope-from Ted.Lemon@nominum.com)
From: Ted Lemon <Ted.Lemon@nominum.com>
Organization: Nominum, Inc.
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Timezones again.
Date: Mon, 10 Apr 2006 20:57:53 -0700
User-Agent: KMail/1.9.1
References: <20060410222857.GE8352@isc.org>
	<200604101739.07258.Ted.Lemon@nominum.com>
	<20060411022010.GA36572@isc.org>
In-Reply-To: <20060411022010.GA36572@isc.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Disposition: inline
Message-Id: <200604102057.53300.Ted.Lemon@nominum.com>
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Monday 10 April 2006 19:20, David W. Hankins wrote:
> Our own client will need to fill both needs since our users span both
> sides: =A0Whichever one is present, with a preference applied to one if=
 both
> are, that preference being user-selectable.

Then I suggest you design your client to request both options.

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



From dhcwg-bounces@ietf.org Tue Apr 11 00:23:50 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTAPo-0005Zb-HS; Tue, 11 Apr 2006 00:23:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTAPn-0005ZW-A8
	for dhcwg@ietf.org; Tue, 11 Apr 2006 00:23:43 -0400
Received: from shell-ng.nominum.com ([81.200.64.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTAPl-0006YZ-St
	for dhcwg@ietf.org; Tue, 11 Apr 2006 00:23:43 -0400
Received: from vpn-38.vpn.nominum.com (vpn-38.vpn.nominum.com [128.177.199.38])
	(using SSLv3 with cipher EXP1024-RC4-SHA (56/128 bits))
	(Client did not present a certificate)
	by shell-ng.nominum.com (Postfix) with ESMTP id 56F3956833
	for <dhcwg@ietf.org>; Mon, 10 Apr 2006 21:23:41 -0700 (PDT)
	(envelope-from Ted.Lemon@nominum.com)
From: Ted Lemon <Ted.Lemon@nominum.com>
Organization: Nominum, Inc.
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Timezones again.
Date: Mon, 10 Apr 2006 21:23:36 -0700
User-Agent: KMail/1.9.1
References: <20060410222857.GE8352@isc.org>
	<200604101739.07258.Ted.Lemon@nominum.com>
	<20060411022010.GA36572@isc.org>
In-Reply-To: <20060411022010.GA36572@isc.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200604102123.36512.Ted.Lemon@nominum.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

> Our own client will need to fill both needs since our users span both
> sides:  Whichever one is present, with a preference applied to one if both
> are, that preference being user-selectable.

To expand on my previous one-liner, let me suggest an alternative:  for those 
implementers, such as you, who want the client to be flexible enough to take 
whatever is configured on the server, in the case where a server has not been 
configured to provide every possible option, configure your client to request 
all three, in the order that you prefer.

This has the disadvantage of consuming more packet space, although I think not 
much.   If you want to mitigate that problem, then implement the following 
heuristic in your server: if it sees that all three options have been 
requested, it responds with the first one listed for which data is available, 
and doesn't send the other two, even if data is available.   This could be a 
MAY in the protocol specification.

What I specifically want to avoid is:

1. Sending options the client didn't ask for.
2. Using a suboption encapsulation in a case where at most we need to send 
only two options.
3. Defining and requiring the implementation of a protocol for negotiating 
which suboptions to send.

I think there is a better solution than this, which we could pursue in a 
separate draft if there was demand for it.   I think a general case can be 
made for it - an option request option with preference chunks, basically.   
It would look like this:

ORO length hunk-count-1 first-choice-1 second-choice-1 third-choice-1 
hunk-count-2 first-choice-2 second-choice-2 hunk-count-3 first-choice-3 
second-choice-3 ...

You'd have one hunk for each set of alternatives; each hunk would contain 
simply a list of option codes, in order of preference.   The server would 
respond with at most one of the alternatives listed, and would send the first 
such alternative that matched, which would be the one the client most 
preferred of the choices available.

This would be general, not specific to the timezone options.   It would be 
relatively cheap to implement, because really it's just an enhancement of the 
existing option request option (or parameter request list).   The client 
would have to send two OROs, because it couldn't count on the server 
understanding both of them.   This would be a minimal problem, because 
packets coming *from* the client generally aren't crammed with options - it's 
packets coming *from* the server that are.

But I would like to separate that issue from the issue of these timezone 
options, because they are really two separate issues.   This preference-based 
option negotiation is not something that Eliot volunteered to work on.   I 
think that we get substantial value out of Eliot's work whether we do the 
best-choice ORO or not.   So tying the two together, or even really debating 
about the second in the same conversation as the first, seems (a) unnecessary 
and (b) delay-inducing.

And this is the underlying reason why I keep debating you and asking you for 
real use cases.   So there you have the question: would you be willing to 
split this debate into two?

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



From dhcwg-bounces@ietf.org Tue Apr 11 07:14:04 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTGop-0000P9-T4; Tue, 11 Apr 2006 07:13:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTGoo-0000P4-1n
	for dhcwg@ietf.org; Tue, 11 Apr 2006 07:13:58 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTFw4-0002lq-9j
	for dhcwg@ietf.org; Tue, 11 Apr 2006 06:17:24 -0400
Received: from farside.isc.org ([204.152.187.5])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FTFoD-0005SJ-6i
	for dhcwg@ietf.org; Tue, 11 Apr 2006 06:09:18 -0400
Received: from [IPv6:2001:888:1936:2:216:6fff:fe49:7d9b] (unknown
	[IPv6:2001:888:1936:2:216:6fff:fe49:7d9b])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by farside.isc.org (Postfix) with ESMTP id 5ACFBE6130
	for <dhcwg@ietf.org>; Tue, 11 Apr 2006 10:09:15 +0000 (UTC)
	(envelope-from shane@isc.org)
Message-ID: <443B8049.6050300@isc.org>
Date: Tue, 11 Apr 2006 12:09:13 +0200
From: Shane Kerr <Shane_Kerr@isc.org>
Organization: ISC
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20060404)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Timezones again.
References: <20060410222857.GE8352@isc.org>	<200604101739.07258.Ted.Lemon@nominum.com>	<20060411022010.GA36572@isc.org>
	<200604102123.36512.Ted.Lemon@nominum.com>
In-Reply-To: <200604102123.36512.Ted.Lemon@nominum.com>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: -2.6 (--)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: shane_kerr@isc.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>
Errors-To: dhcwg-bounces@ietf.org

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

Ted,

Ted Lemon wrote:
> 
> I think there is a better solution than this, which we could pursue in a 
> separate draft if there was demand for it.   I think a general case can be 
> made for it - an option request option with preference chunks, basically.   
> It would look like this:
> 
> ORO length hunk-count-1 first-choice-1 second-choice-1 third-choice-1 
> hunk-count-2 first-choice-2 second-choice-2 hunk-count-3 first-choice-3 
> second-choice-3 ...

<snip/>

> And this is the underlying reason why I keep debating you and asking you for 
> real use cases.   So there you have the question: would you be willing to 
> split this debate into two?

I like this approach. The combination of the existing TZ draft and a
mechanism for expressing option preferences would address all of my
concerns with the TZ options.

- --
Shane
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEO4BJMsfZxBO4kbQRApj0AJ9eCVnDoLx4h0+v0LYOnNESWe3jFQCglocY
YaUiYGczP7hFxE0b3tZ68Q4=
=Rr54
-----END PGP SIGNATURE-----

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



From dhcwg-bounces@ietf.org Tue Apr 11 12:09:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTLR8-0006zQ-JB; Tue, 11 Apr 2006 12:09:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTLR7-0006zL-LL
	for dhcwg@ietf.org; Tue, 11 Apr 2006 12:09:49 -0400
Received: from kaboom.isc.org ([204.152.187.72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTLR6-0007sU-7y
	for dhcwg@ietf.org; Tue, 11 Apr 2006 12:09:49 -0400
Received: by kaboom.isc.org (Postfix, from userid 10200)
	id EDB351CB16; Tue, 11 Apr 2006 09:09:46 -0700 (PDT)
Date: Tue, 11 Apr 2006 09:09:46 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Timezones again.
Message-ID: <20060411160946.GA19244@isc.org>
References: <20060410222857.GE8352@isc.org>
	<200604101739.07258.Ted.Lemon@nominum.com>
	<20060411022010.GA36572@isc.org>
	<200604102123.36512.Ted.Lemon@nominum.com>
Mime-Version: 1.0
In-Reply-To: <200604102123.36512.Ted.Lemon@nominum.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
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="===============1439494508=="
Errors-To: dhcwg-bounces@ietf.org


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


--Q68bSM7Ycu6FN28Q
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Mon, Apr 10, 2006 at 09:23:36PM -0700, Ted Lemon wrote:
> 2. Using a suboption encapsulation in a case where at most we need to send 
> only two options.

At some point, I'd like to hear your reasoning for this, but perhaps
I should wait to hear this reasoning in the Introduction section of a
draft you appear set to write (?), rather than asking you to duplicate
that effort.

> ORO length hunk-count-1 first-choice-1 second-choice-1 third-choice-1 
> hunk-count-2 first-choice-2 second-choice-2 hunk-count-3 first-choice-3 
> second-choice-3 ...
> 
> You'd have one hunk for each set of alternatives; each hunk would contain 
> simply a list of option codes, in order of preference.   The server would 
> respond with at most one of the alternatives listed, and would send the first 
> such alternative that matched, which would be the one the client most 
> preferred of the choices available.

Because when I compare these two solutions, they are very near in
function.

I tend to think of a sub-parameter-request-list as easier to implement,
but less general (it couldn't include the old time-offset option for this
set of timezone options for example, or indicate a preference for
domain-search over domain-name, or etc).

But it's possible I only have that bias because I've already implemented
sub-parameter-request: what you've already done always seems easier than
what you haven't entertained.

So, this is a new direction that deserves thought and analysis.

> understanding both of them.   This would be a minimal problem, because 
> packets coming *from* the client generally aren't crammed with options - it's 
> packets coming *from* the server that are.

Parameter-requests are usually short anyway, shorter even than the POSIX
format presently being described here (the longest common one I'm
presently aware of in DHCPv4 is 18 codes long, commonly emitted by SuSe
9.1 [1]).  The worst case application of your proposed change would be to
consume these 20 bytes plus another 38, for a total of 58 bytes.  Still
pretty small, considering.

> So there you have the question: would you be willing to 
> split this debate into two?

Yes, but this body needs to be agreed on how we're going to proceed.

Similiarly to my position on other draft controversy in recent memory, I
need to be sure we've selected a way forward before we run the work in
parallel.


But fundamentally:  You and I are in agreement on the problem set, if
not the solution, and that is measurable progress.

Thank you for your time.




[1] DHCP Listener (Java "DHCP Fingerprinting" applet)
    Author Unknown
    The University of Kansas
    Lawrence, KS, U.S.A.

    http://www.nts.ku.edu/downloads/

Derivative work:

    class "VendorIdent" {
            match option dhcp-parameter-request-list;
    }

    subclass "VendorIdent" 1:3:6:c:f:11:17:1c:1d:1f:21:28:29:2a:9:7:c8:2c {
            set os-ident = "Linux 2.6.5-7.108 Suse 9.1/Novell Desktop";
    }

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

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

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

iD8DBQFEO9TKcXeLeWu2vmoRAhpAAJ0QBG0M7/K4OvEHm15FyTgipa7eNQCfTr+P
XhxIGlxuy5ArHIJ+LelQR2Q=
=iStC
-----END PGP SIGNATURE-----

--Q68bSM7Ycu6FN28Q--


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

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

--===============1439494508==--




From dhcwg-bounces@ietf.org Tue Apr 11 15:22:20 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTOQy-0001fQ-9P; Tue, 11 Apr 2006 15:21:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTOQx-0001fL-Mb
	for dhcwg@ietf.org; Tue, 11 Apr 2006 15:21:51 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTNHZ-0003rL-9c
	for dhcwg@ietf.org; Tue, 11 Apr 2006 14:08:05 -0400
Received: from test-iport-1.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FTN2r-0000cM-H1
	for dhcwg@ietf.org; Tue, 11 Apr 2006 13:52:54 -0400
Received: from sj-core-1.cisco.com ([171.71.177.237])
	by test-iport-1.cisco.com with ESMTP; 11 Apr 2006 10:52:52 -0700
Received: from imail.cisco.com (sjc12-sbr-sw3-3f5.cisco.com [172.19.96.182])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k3BHqqw1021956;
	Tue, 11 Apr 2006 10:52:52 -0700 (PDT)
Received: from [212.254.247.4] (ams3-vpn-dhcp288.cisco.com [10.61.65.32])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id k3BHqQub024875;
	Tue, 11 Apr 2006 10:52:35 -0700
Message-ID: <443BECEB.9040109@cisco.com>
Date: Tue, 11 Apr 2006 19:52:43 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 1.5 (Macintosh/20051201)
MIME-Version: 1.0
To: "David W. Hankins" <David_Hankins@isc.org>
Subject: Re: [dhcwg] Timezones again.
References: <20060410222857.GE8352@isc.org>
In-Reply-To: <20060410222857.GE8352@isc.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=1559; t=1144777956; x=1145641956;
	c=relaxed/simple; s=oregon;
	h=To:Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=lear@cisco.com; z=From:Eliot=20Lear=20<lear@cisco.com>
	|Subject:Re=3A=20[dhcwg]=20Timezones=20again.
	|To:=22David=20W.=20Hankins=22=20<David_Hankins@isc.org>;
	X=v=3Dcisco.com=3B=20h=3D8x0Uw/eD+oMqUVOCGe7YN0+VeH0=3D;
	b=bv51k3J1MjdHYNS9AuOYkZFnsty3zOip7Q+aLKzFQ4s8HOf7JNE+RmRfr1/Xj0MAsIR9IfpO
	w/lK9uKa8i0XzmeI7Plkx4cI7MC5TPvT5kS4a+Yyr0QM0Mcx5D0I8GsD;
Authentication-Results: imail.cisco.com; header.From=lear@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: -2.0 (--)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

David,

Thank you for your note.  A few comments.

Regarding your example of a use of option 2, just because someone did
something with with it doesn't make it a good idea.  Quite the contrary
in my mind.  That person demonstrated its flaw.  Clearly POSIX is a far
better option in order to avoid synchronizing DHCP updates to DST changes.

Having said that I agree with your conclusion that while history is
nice, wall clock time is required.  My point is that the best way for a
client to get wall clock time is for it to receive something as close to
native as possible.  In MOST UNIX implementations the best approach is
the TZ database because that's what nearly all of them use.  This
requires no kernel changes and no tweaks to the environment, a hazardous
approach, always, IMHO.  Again, this makes history a side benefit.   
For Microsoft, I have a query out to the person responsible for
Microsoft DHCP and he has agreed to review the document soon, and so
I'll withhold comment.

As to Australia's problem (and the Brazil papal visit, for that matter),
one issue I've heard from SPs is that they really don't WANT to have to
provide the actual TZ definition, and would rather provide a reference
to something in the OS.  This makes the update "somebody else's
problem".  I personally don't like that approach, but if we split into
three options we get that for free IFF we say only "MUST implement" not
"MUST deploy" which is the line we usually draw, anyway.

This would also solve Ted's problem.

Regards,

Eliot

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



From dhcwg-bounces@ietf.org Tue Apr 11 15:38:17 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FTOgp-0007Ti-Tq; Tue, 11 Apr 2006 15:38:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FTOgp-0007Td-1I
	for dhcwg@ietf.org; Tue, 11 Apr 2006 15:38:15 -0400
Received: from pacdcoavas09.cable.comcast.com ([208.17.33.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FTOgm-00071h-PN
	for dhcwg@ietf.org; Tue, 11 Apr 2006 15:38:15 -0400
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
Subject: RE: [dhcwg] Timezones again.
Date: Tue, 11 Apr 2006 15:37:50 -0400
Message-ID: <6EEEACD9D7F52940BEE26F5467C02C73037CFAC2@PACDCEXCMB01.cable.comcast.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Timezones again.
Thread-Index: AcZdnU1fNeroocxjQ8SyBNtyBUyBxAAAXRuw
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: "Eliot Lear" <lear@cisco.com>
X-OriginalArrivalTime: 11 Apr 2006 19:37:52.0119 (UTC)
	FILETIME=[6C15D070:01C65D9F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

>one issue I've heard from SPs is that they really don't WANT to have to
provide the actual TZ definition, and would rather provide a reference
to something in the OS.

Speaking as a SP. :^)

If I am pushing TZ information to a end user's computer, then I agree; I
would prefer to provide a reference to something in the end user's OS.

If I am pushing TZ information to a SP-managed device such as a cable
modem (or more precisely a cable home gateway device, which enables
parental controls such as time-of-day Internet access as configured by
the customer), then there really isn't a "TZ reference to something in
the OS", so I really need to send an actual TZ definition.

-- Rich

-----Original Message-----
From: Eliot Lear [mailto:lear@cisco.com]=20
Sent: Tuesday, April 11, 2006 1:53 PM
To: David W. Hankins
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Timezones again.


David,

Thank you for your note.  A few comments.

Regarding your example of a use of option 2, just because someone did
something with with it doesn't make it a good idea.  Quite the contrary
in my mind.  That person demonstrated its flaw.  Clearly POSIX is a far
better option in order to avoid synchronizing DHCP updates to DST
changes.

Having said that I agree with your conclusion that while history is
nice, wall clock time is required.  My point is that the best way for a
client to get wall clock time is for it to receive something as close to
native as possible.  In MOST UNIX implementations the best approach is
the TZ database because that's what nearly all of them use.  This
requires no kernel changes and no tweaks to the environment, a hazardous
approach, always, IMHO.  Again, this makes history a side benefit.  =20
For Microsoft, I have a query out to the person responsible for
Microsoft DHCP and he has agreed to review the document soon, and so
I'll withhold comment.

As to Australia's problem (and the Brazil papal visit, for that matter),
one issue I've heard from SPs is that they really don't WANT to have to
provide the actual TZ definition, and would rather provide a reference
to something in the OS.  This makes the update "somebody else's
problem".  I personally don't like that approach, but if we split into
three options we get that for free IFF we say only "MUST implement" not
"MUST deploy" which is the line we usually draw, anyway.

This would also solve Ted's problem.

Regards,

Eliot

_______________________________________________
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 Apr 17 00:07:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FVL0q-0005o9-Bo; Mon, 17 Apr 2006 00:06:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FVL0p-0005np-CA
	for dhcwg@ietf.org; Mon, 17 Apr 2006 00:06:55 -0400
Received: from imc07.net ([66.39.196.183])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FVL0m-00066z-40
	for dhcwg@ietf.org; Mon, 17 Apr 2006 00:06:53 -0400
Received: from imc07.net (imc07.net [127.0.0.1])
	by imc07.net (Postfix) with ESMTP id CA9545CFA16
	for <dhcwg@ietf.org>; Sun, 16 Apr 2006 23:06:39 -0500 (CDT)
Received: (from apache@localhost)
	by imc07.net (8.13.1/8.13.1/Submit) id k3H46dhR031246;
	Sun, 16 Apr 2006 23:06:39 -0500
Date: Sun, 16 Apr 2006 23:06:39 -0500
Message-Id: <200604170406.k3H46dhR031246@imc07.net>
To: dhcwg@ietf.org
MIME-Version: 1.0
From: raj.ooty@gmail.com
X-Spam-Score: 1.5 (+)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Subject: [dhcwg] Check it out
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: raj.ooty@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>
Content-Type: multipart/mixed; boundary="===============0560697709=="
Errors-To: dhcwg-bounces@ietf.org

--===============0560697709==
Content-type: text/html; charset=iso-8859-1


Sign up so we can play
<br><br> 
								<a href="http://followhere02.com/go.asp?id=1&sourceid=friend=&friend=raj">http://followhere02.com/go.asp?id=1&sourceid=friend=&friend=raj</a>
<br><br>
								
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
								This invitation was sent on behalf of your friend, raj (raj.ooty@gmail.com).
<br>
								To stop receiving further emails, please <a href="http://followhere02.com/go.asp?id=2">follow-here</a>:
<br><br>
								Kosta Ourani, 6 
<br>
								Pera Chorio Nisou 
<br>
								P.C. 2572 Nicosia, Cyprus


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

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

--===============0560697709==--



From dhcwg-bounces@ietf.org Mon Apr 17 05:14:24 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FVPo6-0000AG-Mh; Mon, 17 Apr 2006 05:14:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FVPo5-0000AB-Iq
	for dhcwg@ietf.org; Mon, 17 Apr 2006 05:14:05 -0400
Received: from tyholt.uninett.no ([158.38.62.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FVPo4-0002C3-7x
	for dhcwg@ietf.org; Mon, 17 Apr 2006 05:14:05 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by tyholt.uninett.no (Postfix) with ESMTP id 11DB287CA1;
	Mon, 17 Apr 2006 11:14:01 +0200 (CEST)
Received: from tyholt.uninett.no ([127.0.0.1])
	by localhost (tyholt.uninett.no [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 07648-02-11; Mon, 17 Apr 2006 11:14:00 +0200 (CEST)
Received: from [IPv6?2001?700?1?1100?28a4?d464?fc81?beb9] (unknown
	[IPv6:2001:700:1:1100:28a4:d464:fc81:beb9])
	by tyholt.uninett.no (Postfix) with ESMTP id 67D3187C9F;
	Mon, 17 Apr 2006 11:14:00 +0200 (CEST)
Message-ID: <44435C51.7060107@uninett.no>
Date: Mon, 17 Apr 2006 11:13:53 +0200
From: Stig Venaas <stig.venaas@uninett.no>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: dhcwg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at uninett.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: Ralph Droms <rdroms@cisco.com>
Subject: [dhcwg] dhc WG last call on "Domain Suffix Option for 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>
Errors-To: dhcwg-bounces@ietf.org

This message announces a WG last call on "Domain Suffix Option for
DHCPv6" <draft-ietf-dhc-dhcpv6-opt-dnsdomain-02.txt>.  The last call
will conclude at 1700 ET on 2006-04-30.

Note that there was a previous last call for revision 00 of this draft. 
There were several responses during that last call, and I believe this 
version resolves the issues raised.

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

"Domain Suffix Option for DHCPv6" specifies an option passed from
server to client to specify a domain suffix name to be used for
domain name updates.  This draft is available as
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-opt-dnsdomain-02.txt

Stig

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



From dhcwg-bounces@ietf.org Mon Apr 17 08:51:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FVTCD-00022I-TY; Mon, 17 Apr 2006 08:51:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FVTCC-00022D-F0
	for dhcwg@ietf.org; Mon, 17 Apr 2006 08:51:12 -0400
Received: from tyholt.uninett.no ([158.38.62.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FVTCB-0003L7-4V
	for dhcwg@ietf.org; Mon, 17 Apr 2006 08:51:12 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by tyholt.uninett.no (Postfix) with ESMTP id DBBA887BC1
	for <dhcwg@ietf.org>; Mon, 17 Apr 2006 14:51:06 +0200 (CEST)
Received: from tyholt.uninett.no ([127.0.0.1])
	by localhost (tyholt.uninett.no [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 13682-02-33 for <dhcwg@ietf.org>;
	Mon, 17 Apr 2006 14:51:06 +0200 (CEST)
Received: from [IPv6?2001?700?1?1100?205?4eff?fe40?1762] (unknown
	[IPv6:2001:700:1:1100:205:4eff:fe40:1762])
	by tyholt.uninett.no (Postfix) with ESMTP id 56AB7B5A54
	for <dhcwg@ietf.org>; Mon, 17 Apr 2006 14:51:06 +0200 (CEST)
Message-ID: <44438F2E.1090306@uninett.no>
Date: Mon, 17 Apr 2006 13:50:54 +0100
From: Stig Venaas <stig.venaas@uninett.no>
User-Agent: Mail/News 1.5 (X11/20060407)
MIME-Version: 1.0
To: dhcwg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at uninett.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea
Subject: [dhcwg] Minutes from IETF65 dhc wg meeting
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Minutes from the IETF 65 wg meeting have been uploaded and can be found 
at http://www3.ietf.org/proceedings/06mar/minutes/dhc.txt.

Please let Ralph and me know ASAP if you have any corrections,

Stig

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



From dhcwg-bounces@ietf.org Mon Apr 17 14:17:58 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FVYIF-0003ds-RB; Mon, 17 Apr 2006 14:17:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FVYIE-0003dn-0F
	for dhcwg@ietf.org; Mon, 17 Apr 2006 14:17:46 -0400
Received: from tyholt.uninett.no ([158.38.62.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FVYIC-0005FI-Mc
	for dhcwg@ietf.org; Mon, 17 Apr 2006 14:17:45 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by tyholt.uninett.no (Postfix) with ESMTP id 1B65287BC7
	for <dhcwg@ietf.org>; Mon, 17 Apr 2006 20:17:43 +0200 (CEST)
Received: from tyholt.uninett.no ([127.0.0.1])
	by localhost (tyholt.uninett.no [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 03782-02-33 for <dhcwg@ietf.org>;
	Mon, 17 Apr 2006 20:17:42 +0200 (CEST)
Received: from [IPv6?2001?700?1?1100?78c7?664f?c4c6?7c92] (unknown
	[IPv6:2001:700:1:1100:78c7:664f:c4c6:7c92])
	by tyholt.uninett.no (Postfix) with ESMTP id 9C3AFB5A54
	for <dhcwg@ietf.org>; Mon, 17 Apr 2006 20:17:42 +0200 (CEST)
Message-ID: <4443DBEC.5010201@uninett.no>
Date: Mon, 17 Apr 2006 20:18:20 +0200
From: Stig Venaas <stig.venaas@uninett.no>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: dhcwg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at uninett.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Subject: [dhcwg] Consensus for wg last call for
	draft-ietf-dhc-dhcpv6-rfc868-servers-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>
Errors-To: dhcwg-bounces@ietf.org

At the dhc wg meeting in Dallas there were no objections to take
the draft "Time Protocol Servers and Time Offset Options for IPv6 DHCP" 
(draft-ietf-dhc-dhcpv6-rfc868-servers-00.txt) to wg last call.

If there are no objections posted to the wg mailing list by 2006-04-30, 
the chairs will start a wg last call for this draft.

Stig

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



From dhcwg-bounces@ietf.org Tue Apr 18 04:55:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FVlzV-0006xG-En; Tue, 18 Apr 2006 04:55:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FVlzV-0006xB-5J
	for dhcwg@ietf.org; Tue, 18 Apr 2006 04:55:21 -0400
Received: from tyholt.uninett.no ([158.38.62.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FVlzR-0008L8-Rr
	for dhcwg@ietf.org; Tue, 18 Apr 2006 04:55:21 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by tyholt.uninett.no (Postfix) with ESMTP id 8BBB287BD3
	for <dhcwg@ietf.org>; Tue, 18 Apr 2006 10:55:16 +0200 (CEST)
Received: from tyholt.uninett.no ([127.0.0.1])
	by localhost (tyholt.uninett.no [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 26481-01-69 for <dhcwg@ietf.org>;
	Tue, 18 Apr 2006 10:55:16 +0200 (CEST)
Received: from [158.38.160.254] (dhcp254.venaas.no [158.38.160.254])
	by tyholt.uninett.no (Postfix) with ESMTP id 5339787BCE
	for <dhcwg@ietf.org>; Tue, 18 Apr 2006 10:55:16 +0200 (CEST)
Message-ID: <4444A996.4050501@uninett.no>
Date: Tue, 18 Apr 2006 10:55:50 +0200
From: Stig Venaas <stig.venaas@uninett.no>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: dhcwg@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at uninett.no
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Subject: [dhcwg] Consensus for wg last call for
	draft-ietf-dhc-dhcpv6-agentopt-delegate-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>
Errors-To: dhcwg-bounces@ietf.org

At the dhc wg meeting in Dallas there were no objections to take
the draft "DHCP Relay Agent Assignment Notification Option" 
(draft-ietf-dhc-dhcpv6-agentopt-delegate-00.txt) to wg last call.

If there are no objections posted to the wg mailing list by 2006-04-30, 
the chairs will start a wg last call for this draft.

Stig

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



From dhcwg-bounces@ietf.org Wed Apr 19 01:57:37 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FW5gf-0005dn-Kg; Wed, 19 Apr 2006 01:57:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FW5gd-0005cs-Vl
	for dhcwg@ietf.org; Wed, 19 Apr 2006 01:57:11 -0400
Received: from shell-ng.nominum.com ([81.200.64.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FW5SD-0005Ct-OP
	for dhcwg@ietf.org; Wed, 19 Apr 2006 01:42:19 -0400
Received: from ngarcha.fugue.com (dsl093-162-134.tus1.dsl.speakeasy.net
	[66.93.162.134])
	(using SSLv3 with cipher EXP1024-RC4-SHA (56/128 bits))
	(Client did not present a certificate)
	by shell-ng.nominum.com (Postfix) with ESMTP id BE2475683C
	for <dhcwg@ietf.org>; Tue, 18 Apr 2006 22:42:14 -0700 (PDT)
	(envelope-from Ted.Lemon@nominum.com)
From: Ted Lemon <Ted.Lemon@nominum.com>
Organization: Nominum, Inc.
To: dhcwg@ietf.org
Subject: Re: [dhcwg] dhc WG last call on "Domain Suffix Option for DHCPv6"
Date: Tue, 18 Apr 2006 22:42:10 -0700
User-Agent: KMail/1.9.1
References: <44435C51.7060107@uninett.no>
In-Reply-To: <44435C51.7060107@uninett.no>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Disposition: inline
Message-Id: <200604182242.10782.Ted.Lemon@nominum.com>
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Monday 17 April 2006 02:13, Stig Venaas wrote:
> This message announces a WG last call on "Domain Suffix Option for
> DHCPv6" <draft-ietf-dhc-dhcpv6-opt-dnsdomain-02.txt>. =A0The last call
> will conclude at 1700 ET on 2006-04-30.

I support acceptance of the document.   I would like to suggest one minor=
=20
editorial change, but this is not important, and I am fine with the docum=
ent=20
going through last call as is - if it seems right to make the change, it =
can=20
be done in the final editing process.   The change is in the introduction=
:

   This document describes a new option for DHCPv6 [RFC3315] that=20
   provides a mechanism for the transfer of a domain name suffix.

Instead I think it would be clearer to say:

   This document describes a new option for DHCPv6 [RFC3315] that=20
   provides a mechanism for specifying a domain name suffix.

But as I say, this is a minor point, and I would like to see the document=
=20
advance as is rather than to go through a third last call over this issue=
.

Thanks!

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



From dhcwg-bounces@ietf.org Mon Apr 24 07:12:21 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FXyzC-0003AW-DZ; Mon, 24 Apr 2006 07:12:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FXyzB-0003AQ-5B
	for dhcwg@ietf.org; Mon, 24 Apr 2006 07:12:09 -0400
Received: from tyholt.uninett.no ([158.38.62.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FXyzA-0004jY-Le
	for dhcwg@ietf.org; Mon, 24 Apr 2006 07:12:09 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by tyholt.uninett.no (Postfix) with ESMTP id ACFD887BEE;
	Mon, 24 Apr 2006 13:12:04 +0200 (CEST)
Received: from tyholt.uninett.no ([127.0.0.1])
	by localhost (tyholt.uninett.no [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 29326-01-63; Mon, 24 Apr 2006 13:12:03 +0200 (CEST)
Received: from [IPv6?2001?700?1?7?215?f2ff?fe35?307d] (sverresborg.uninett.no
	[IPv6:2001:700:1:7:215:f2ff:fe35:307d])
	by tyholt.uninett.no (Postfix) with ESMTP id CA0E387BC9;
	Mon, 24 Apr 2006 13:12:03 +0200 (CEST)
Message-ID: <444CB283.7050103@uninett.no>
Date: Mon, 24 Apr 2006 13:12:03 +0200
From: Stig Venaas <stig.venaas@uninett.no>
User-Agent: Mozilla Thunderbird 1.0.7 (X11/20060214)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "David W. Hankins" <David_Hankins@isc.org>
Subject: Re: [dhcwg] clarifying server-id-override
References: <4422D4F5.6060506@cisco.com> <20060323203521.GC88228@isc.org>
In-Reply-To: <20060323203521.GC88228@isc.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at uninett.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

David W. Hankins wrote:
> On Thu, Mar 23, 2006 at 12:03:49PM -0500, Mark Stapp wrote:
> 
>>We spent some time discussing what happens when server-id-override and 
>>failover or load-balancing are all configured. When server-id-override 
>>is configured, relays will forward client messages to both failover or 
>>load-balancing partner servers. The client messages will all contain 
>>giaddr, and the servers will not be able to distinguish between client 
>>unicast RENEWs and client REBINDs. Both servers will have to either 
>>respond, causing extra server work, or will have to do some amount of 
>>work to determine whether they can safely ignore the client message.
>>
>>At least one person suggested that that extra work would be so onerous 
>>that we had to develop a mechanism to allow the relay to indicate 
>>whether the clients' messages had been unicast. Further, 
>>server-id-override could proceed forward only if it included a MUST, a 
>>normative reference, to that mechanism.
> 
> 
> I think I disagree with this summarization, but I suspect that is due
> either to the way I read it, or the expedience utilized in writing it.
> 
> Substantively, I think the LBA/failover and unicast/broadcast issues
> are two separate ones (and I don't think a unicast/broadcast flag is
> going to fix it).
> 
> But it doesn't matter, because I agree with your conclusion anyway.
> 
> 
>>1. I'd like to clarify the issues that can arise in the 
>>server-id-override draft, so that someone who wants to use these things 
>>in combination will be made aware of the implications.
> 
> 
> Right.  "Server-override + LBA is considered harmful."
> 
> 
>>2. I'd like to add an INFORMATIVE reference to the work-in-progress 
>>draft containing the unicast indicator, as a way to mitigate the issues 
>>in (1). That would allow server-id-override to move forward, but 
>>establishes a connection between the two mechanisms.

Having read IESG's statement on normative and informative references 
(posted to ietf-announce on April 19th), I think it's difficult to have 
an informative reference to such an indicator, even if it is optional.

 From the statement:

    in the new RFC to work. An informative reference is not normative;
    rather, it only provides additional information. For example, an
    informative reference might provide background or historical
    information. Informative references are not required to implement the
    technology in the RFC.

    Note 1: Even references that are relevant only for optional features
    must be classified as normative if they meet the above conditions for
    normative references.

If we're talking about a single bit as indicator for unicast/multicast, 
then it appears to me that we could easily add this to the draft now, 
and do new last calls ASAP. I think the last calls could all be done in 
just 2-3 months time, so not that much of a delay really. Figuring out 
how to possibly informatively reference another draft from current 
server-override draft may also take some time. I also feel a bit better 
about having this in one single document where implementing this 
indicator could at least be a SHOULD.

So my suggestion is to just quickly add this indicator to the draft and 
do new last calls. At least if we agree that such an indicator is the 
way to go.

Stig

> 
> 
> Right.  "I actually can't think of a snarky summary."  This would be
> to address the unicast/broadcast issue, whereas the above addresses
> the LBA issue.
> 
> 
>>Comments?
> 
> 
> I agree.
> 
> The only reservation being the INFORMATIVE reference should be made to
> a draft that has been accepted as a WG item (to my mind, that acceptance
> indicates the WG is committed to following through - and that we all
> agree roughly on the way in which it should go forward (but we reserve
> the right to be wrong)).
> 
> 
> 
> Discussion (expanding on my opinion);  there is actually more than one
> reason for using server-override, and in precisely one of those the
> situations we're describing are less harmful than the current reality
> it was designed to correct (not being able to communicate with a client
> at all).
> 
> I think it's perfectly reasonable to let the current problem in the
> currently defined environment be fixed, and let future work apply this
> fix to other environments (with the patches necessary).
> 
> Of course it also means that the document needs to define that
> environment, and limit the scope of its work to it (so, I repeat my
> opinion: that I think the IESG comments were on-target in this vein).
> 


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



From dhcwg-bounces@ietf.org Mon Apr 24 09:34:59 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FY1D0-0002mu-A8; Mon, 24 Apr 2006 09:34:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FY1Cz-0002mp-Bo
	for dhcwg@ietf.org; Mon, 24 Apr 2006 09:34:33 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FY1Cx-0004NH-2S
	for dhcwg@ietf.org; Mon, 24 Apr 2006 09:34:33 -0400
Received: from rtp-core-2.cisco.com ([64.102.124.13])
	by rtp-iport-2.cisco.com with ESMTP; 24 Apr 2006 09:34:30 -0400
X-IronPort-AV: i="4.04,152,1144036800"; 
	d="scan'208"; a="87079911:sNHT40814408"
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k3ODYUvF005906; 
	Mon, 24 Apr 2006 09:34:30 -0400 (EDT)
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Mon, 24 Apr 2006 09:34:30 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] dhc WG last call on "Domain Suffix Option for DHCPv6"
Date: Mon, 24 Apr 2006 09:34:28 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB210189BC9A@xmb-rtp-20a.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] dhc WG last call on "Domain Suffix Option for DHCPv6"
Thread-Index: AcZh/1wKJlTQJeilR4eq/4GWIeHzbAFoyMjA
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "Stig Venaas" <stig.venaas@uninett.no>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 24 Apr 2006 13:34:30.0542 (UTC)
	FILETIME=[D0B3EAE0:01C667A3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: "Ralph Droms \(rdroms\)" <rdroms@cisco.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

I agree with Ted's comment and would extend that text change to the
Abstract - not just the Introduction.

I also have additional nits - For the diagram in section 2, we usually
call the fields option-code and option-length, not type and length. Also
the "16-bits identifier of the type of option" is a bit odd as this is
the option-code, not the "type" of option. This is further an issue
since the remainder of the document uses "option code", not type.

But, otherwise I agree with advancing this document.

- Bernie=20

> -----Original Message-----
> From: Stig Venaas [mailto:stig.venaas@uninett.no]=20
> Sent: Monday, April 17, 2006 5:14 AM
> To: dhcwg@ietf.org
> Cc: Ralph Droms (rdroms)
> Subject: [dhcwg] dhc WG last call on "Domain Suffix Option for DHCPv6"
>=20
> This message announces a WG last call on "Domain Suffix Option for
> DHCPv6" <draft-ietf-dhc-dhcpv6-opt-dnsdomain-02.txt>.  The last call
> will conclude at 1700 ET on 2006-04-30.
>=20
> Note that there was a previous last call for revision 00 of=20
> this draft.=20
> There were several responses during that last call, and I=20
> believe this=20
> version resolves the issues raised.
>=20
> Please respond to this WG last call.  If you support acceptance of the
> document without change, respond with a simple acknowledgment, so that
> support for the document can be assessed.  Lack of discussion does not
> represent positive support.  If there is no expression of support for
> acceptance during the WG last call, the document will not be advanced
> to the IESG.
>=20
> "Domain Suffix Option for DHCPv6" specifies an option passed from
> server to client to specify a domain suffix name to be used for
> domain name updates.  This draft is available as
> http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-opt-
> dnsdomain-02.txt
>=20
> Stig
>=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 Mon Apr 24 13:53:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FY5FA-0002Uv-1y; Mon, 24 Apr 2006 13:53:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FY5F9-0002Uq-0l
	for dhcwg@ietf.org; Mon, 24 Apr 2006 13:53:03 -0400
Received: from kaboom.isc.org ([204.152.187.72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FY5F8-0008EI-8h
	for dhcwg@ietf.org; Mon, 24 Apr 2006 13:53:02 -0400
Received: by kaboom.isc.org (Postfix, from userid 10200)
	id 6B5851DDFDA; Mon, 24 Apr 2006 10:52:52 -0700 (PDT)
Date: Mon, 24 Apr 2006 10:52:52 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Message-ID: <20060424175252.GB786@isc.org>
Mime-Version: 1.0
User-Agent: Mutt/1.5.9i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1c0c3d540ad9f95212b1c2a9a2cc2595
Subject: [dhcwg] Text for draft-ietf-dhc-server-override
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="===============0719398120=="
Errors-To: dhcwg-bounces@ietf.org


--===============0719398120==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="IrhDeMKUP4DT/M7F"
Content-Disposition: inline


--IrhDeMKUP4DT/M7F
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Stig's recent message reminded me this has been sitting in my edit buffer
a bit too long.  I think it's passed the point where more time in my
edit buffer will make it any better.

I promised Kim Kinnear some text, at least as a starting point, to help
describe better the situations this option might reasonably be used since
we seem to be fairly fuzzy on that point.

To those ends I suggest:

1.  Introduction

-  There are many situations where the DHCP relay is involved and can
-  insert a relay agent option with appropriate suboptions easily into
-  DHCP DISCOVER messages.  Once the lease has been granted, however,
+  When a DHCP Client is in the INIT, INIT-REBOOT, BINDING or REBIND
+  states (or at any time a client's DHCP packet is broadcast), it is
+  able to contact a local DHCP Relay which can insert a relay agent
+  option with appropriate suboptions easily into DHCP DISCOVER or
+  REQUEST messages.  Once the lease has been granted, however,
   future DHCP RENEWAL messages are sent directly to the DHCP Server as
   specified in the Server Identifier option.  This means that the relay
   may not see the DHCP RENEWAL messages (depending upon network
   topology) and thus can not provide the same relay agent option
   information in the RENEWAL messages.

+  The relay agent circuit-id option combined with others is often used to
+  identify a specific port in a Service Provider's network, and may be
+  tied to billing or even what pool of addresses the client is allowed to
+  allocate from.  An up-to-date value, in those cases where it may change
+  such that the client can maintain IP connectivity (such as is the case
+  with multiple switch ports on the same IP subnet), is useful to those
+  ends.
+
+  But there are several situations where the relay may wish or need to
+  remain a constant part of the communication between server and client,
+  which does not include the need to supply up-to-date relay agent
+  information options:
+
+  If the client and server were not connected in terms of IP routing,
+  such as may be the case if the client were attached only to a VPN,
+  and the server had no direct attachment (or is attached to a different
+  VPN).  In such a case, the DHCP client's RENEWAL can not be received
+  by the server, which causes the client ultimately to enter REBINDING
+  state in order to extend its lease.  This is undesirable as it presents
+  a momentary loss of network connectivity to the client.  The situation
+  already requires that a DHCP Relay Agent exist which straddles both the
+  VPN and publically routed networks, so that the initial message exchanges
+  can be relayed between server and client.  But such an agent would need
+  to remain a part of the conversation between Client and Server for clients
+  to successfully RENEW their leases, so that this cross-network relay
+  service can continue to function.
+
+  If the relay was administratively configured to maintain a running
+  state based upon observations in the DHCP protocol.  For example, there
+  exist a number of implementations already of IP Firewall services which
+  seek to provide additional limitations to clients on public networks
+  that refuse to negotiate with a DHCP server ("stealing a lease").  Such
+  implementations use the DHCP ACK messages transmitted by the DHCP
+  server to build a dynamic firewall ruleset which allows IP access to
+  only those leases that have negotiated an active lease with their
+  network's DHCP server.  In so doing, clients 'stealing' leases are
+  ultimately relegated to losing global IP connectivity (if they ever had
+  it to start with).  In order to maintain an up-to-date list of permitted
+  client addresses, the Relay Agent needs to remain a part of the
+  conversation between Client and Server during RENEW state.
+
+  If the Relay Agent and Server participated in DHCP Relay Agent
+  Authentication, or IPSec, or similar means to authenticate one another
+  to justify the hole presented in Firewall configuration to communicate,
+  but such means of authentication were not available to DHCP Clients
+  resting behind a firewall.  Under such a circumstance, an IP Source
+  Address that happens to match the desired DHCP Server is not sufficient
+  to guarantee DHCP security in a firewalled network.  Such a Relay Agent
+  would serve to secure its clients from DHCP vectors of attack by serving
+  only relayed responses to them, guaranteeing all responses come from the
+  trusted DHCP Server.  This produces the identical failure mode for DHCP
+  Clients in RENEW state as was previously described for VPNs, and the
+  identical solution set is needed.
+
   This new DHCP relay agent suboption, Server Identifier override,
   allows the relay to tell the DHCP server what value to place into the
   Server Identifier option.  Using this, the relay agent can force
   RENEWAL messages to come to it instead of the server.  The relay may
   then insert the relay agent option with appropriate suboptions and
   relay the DHCPREQUEST to the actual server.  In this fashion the DHCP
   server will be provided with the same relay agent information upon
   renewals (such as Circuit-ID, Remote-ID, Device Class, etc.) as was
-  provided in the initial DISCOVER message.  In effect, this makes a
-  RENEWAL into a REBINDING.
+  provided in the initial DISCOVER message.
+
+  This has the effect of making all DHCP REQUEST messages from clients in
+  the RENEW state appear to the DHCP Server as though the client were
+  instead in the REBIND state, and therefore may be subject to network
+  attachment correction (the transmission of a DHCP NAK message to inform
+  a client it is no longer attached to the network it is presently addressed
+  on).  This is unusual for a client in RENEW state, but not incompatible,
+  and may be correct behaviour under certain specific circumstances, as
+  documented in the APPLICABILITY section.


...jumping ahead...


+4. APPLICABILITY
+
+  DHCP Server Implementations today may not perform Network Attachment
+  detection upon receiving DHCP REQUEST messages, unless it was known
+  to be received on a local interface by broadcast means, or unless it
+  was received via a DHCP Relay Agent (the giaddr field is nonzero),
+  which until the Server-Override suboption assures it was received on
+  a remote interface by broadcast means.
+
+  Consequently, this option is only applicable to environments where the
+  DHCP Relay and Server will collude to conclude correctly about the
+  actual network to which the Client is attached when it is in RENEW state.
+  This is a combination of the specific means the Relay will mark the DHCP
+  packet to identify its source of origin, and the compatible use by the
+  DHCP Server to determine the point of attachment of the client.
+  
+  This is the case under the following Applicable Environments, but MAY
+  NOT be the case otherwise, where this option SHOULD NOT be used.
+
+4.1. SIMPLE USE CASE
+
+  The DHCP Relay MUST select a Server-Override IPv4 Address which is an
+  interface address local to the subnet that the DHCP Client will be
+  addressed upon.  This carries some additional limitations:
+
+   o There is only one IPv4 subnet on the broadcast domain.
+   o There are multiple IPv4 subnets on the broadcast domain, but the DHCP
+     Relay Agent somehow knows in advance which one the client will be
+     addressed upon.
+   o The DHCP Client's implementation MUST prefer to use locally connected
+     routes to acheive the Server-Identifier, rather than to select
+     another Internet-connected interface for any reason (such as relative
+     speed, reliability, or power consumption).
+
+  By providing an address that is link-local to the DHCP Client at all
+  times, it can be assured that the client will utilize that local
+  network attachment rather than favoring any additional network
+  interfaces default routers.  This stipulates client behaviour that is
+  not specified in any DHCP protocol RFC, but is not known to be
+  implemented otherwise.
+
+  Should the DHCP Client roam to another network, and through some
+  contrivance still be able to exit its local subnet (such as might
+  be the case if both networks DHCP Relays utilized VRRP, tagged VLANs,
+  or any mechanism that produces non-unique MAC addresses), the client's
+  IP Unicast is likely to reach the DHCP Relay.  DHCP Relay behaviour in
+  this circumstance is undefined - it may either elect to indicate the
+  client is attached upon the interface the packet was actually received
+  upon, or it may elect to indicate the interface of the address the
+  client unicast its REQUEST to (the Berkeley Socket or similar from
+  which the packet was read).  It is expected that the DHCP Server will,
+  upon performing Network Address detection, emit either a DHCP NAK or
+  ACK respectively, but only in the NAK case is it possible this message
+  might reach the DHCP Client in question (assuming it is actually
+  connected to that location).
+
+  For this reason, DHCP Relay Agents SHOULD make all indications for
+  Client attachment based upon the actual physical interface the packet
+  was received upon.
+
+4.2. PRESENCE OF ADDITIONAL INFORMATION
+
+  Future DHC WG work includes defining additional Relay Agent flags
+  fields to allow a DHCP Relay to indicate wether the received packet
+  was an IP Unicast to one of the DHCP Relay's IP addresses or "not"
+  (implying the DHCP Relay received the packet via some form ofbroadcast).
+
+  In such a case, where the DHCP Relay makes use of this option, all
+  environments become applicable under the following conditions.
+
+   o The DHCP Server MUST NOT perform Network Attachment detection when
+     the DHCP Relay indicates the client packet was Unicast, and so no
+     DHCP NAK must be transmitted for this reason.
+   o The DHCP Relay MUST unicast the Server's DHCP response to the IP
+     address indicated in the 'ciaddr' field.  It MUST NOT use the normal
+     means to determine which interface to transmit the packet.  Instead,
+     normal IP Routing to the 'ciaddr' contents MUST be used.  This MAY
+     NOT be the interface to which the client is actually attached, and MAY
+     NOT be the interface from whence the DHCP Client packet that
+     precipitated a response came from.


I thought there was a third case, but I seem to have simplified it
into the simple case as I was editing.  I have this nagging feeling
I'm forgetting an environment discussed at IETF 65.



While thinking about this, I came up with some network diagrm
distillations of 'does not work' environments which I'm trying to make
"not applicable", thanks in whole to the discussion on this mailing list
and at IETF 65.  Of those, I find this one the most salient:

		+-------------+
		| DHCP Client |
		+-------------+
	10.0.0.x eth0 | | wi0  10.0.1.y
		      | |
	10.0.0.1 eth0 | | eth1 10.0.1.1
		+-------------+ eth2			+-------------+
		| DHCP Relay  |----------[Internet]-----| DHCP Server |
		+-------------+				+-------------+
		lo0:1 10.255.255.1

In the above, if the 10.255.255.1 address is used in the server-override,
all DHCP REQUEST messages sent in unicast (RENEW) will be sent via one of
the default routers selected by the DHCP Client.  Implementations vary,
but the most sensible would be to use the wired ethernet (because it has
the lower number).

If the server performs network attachment detection in this case,
as it will if giaddr is set, it will NAK one of the two incorrectly,
and that NAK packet will be able to reach the client.

After all our time running around this bush, I think the above diagram is
the most lean distillation of 'the problem' I've seen yet.  It may be
easier to just throw this network diagram in, or one like it, and explain
how it causes false network attachment detection.  "Don't do that then"
etc.

I think I've used enough 'ink' at this point however, so if someone else
wants to take a stab...



It's also amusing (and I include this for those ends explicitly) to
consider the logical extension of the use of this option by IP Firewall
environments:

	+-------------+		+-------------+		+-------------+
	| DHCP Client |		| DHCP Client |		| DHCP Client |
	+-------------+		+-------------+		+-------------+
	10.0.0.x |		10.0.1.x |		10.0.2.x |
		 |			 |			 |
	10.0.0.1 | /24		10.0.1.1 | /24		10.0.2.1 | /24
	+-------------+		+-------------+		+-------------+
	| DHCP Relay  |		| DHCP Relay  |		| DHCP Relay  |
	+-------------+		+-------------+		+-------------+
	      |			      |			      |
	      \------------[Routed Private Network]-----------/
				      |
			 10.255.254.1 | /24
				+-------------+
				| IP Firewall |	lo0:1 - 10.255.255.1
				+-------------+
				      |
				[More Routing]
				      |
				+-------------+
				| DHCP Server |
				+-------------+

At broadcast, each individual DHCP relay on these networks picks up the
client.  They're in the game until the clients are addressed.  Let us
imagine they set giaddr to their inside-interface address (the listed
10.0.x.1's), do not supply subnet-select, and provide relay agent options
that include a server-override set to 10.255.255.1.

They may or may not transmit the client packets to this second relay on
the firewall, but in either case the server responses go direct to the
first relay, so the IP firewall at best is only half inside the loop at
that stage, then fully in the loop once the clients are unicasting renews
to the firewall directly.

So, in this environment, you'd have to know the likely initial lease
time to apply to the lifetime of any dynamic firewall rules (which
you would then apply to the requested address of any DHCPREQUEST got
via relays, speculating they will succeed), and this can be more easily
enforced if you also control the DHCP Server.  This is only useful if
you're trying to keep ip routing off of clients that don't want to
emit DHCP packets at all (the DHCP server may still not allow them),
uninvited guests.

So alternatively you could engineer a backchannel and get the lease time
out of acks sent to the first line relays.

Or even more alternatively, you could purposefully give out a very short
lease time to initial bindings so there's an immediate renewal via the
firewall, then give out longer lease times now that the relay can see
them.

Or even further off the alternatives beaten path where the weeds grow
thick, they could not set giaddr, provide a relay agent information
option that includes a server-override set to 10.255.255.1 and a
subnet-selection option, and forward the packet to the IP firewall
(which will not touch the relay agent options, but will put an address
of its own on giaddr).  You would expect the IP Firewall would have to
have a way to reach the first line relay.  Let us imagine the first
line relay is known to encode this in the agent options.


Whatever the case, the clients are cetainly never attached to
10.255.254.0/24, so performing network attachment detection is rather
pointless, and broken in this environment.


Given those worst possible cases, I tried to provide reasonable
guidance in that applicability section to steer people away from use
here unless agent options start telling us their unicast or broadcast
status.

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

--IrhDeMKUP4DT/M7F
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFETRBzcXeLeWu2vmoRAihbAJ9sbJS7q0hVZDd/PJUXxQaXfQeCdACePw0q
K/E2jRO68bYpZ8eY3i/iMiM=
=GTYL
-----END PGP SIGNATURE-----

--IrhDeMKUP4DT/M7F--


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

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

--===============0719398120==--




From dhcwg-bounces@ietf.org Mon Apr 24 20:55:30 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FYBpt-00022i-Pb; Mon, 24 Apr 2006 20:55:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FYBps-00022d-G0
	for dhcwg@ietf.org; Mon, 24 Apr 2006 20:55:24 -0400
Received: from nat1.alcatel-sbell.com.cn ([202.96.203.177]
	helo=mail.alcatel-sbell.com.cn)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FYBpr-0004JG-KK
	for dhcwg@ietf.org; Mon, 24 Apr 2006 20:55:24 -0400
Received: from asbmail4.sbell.com.cn (localhost [127.0.0.1])
	by mail.alcatel-sbell.com.cn (8.12.11/8.12.11/Alcanet1.0) with ESMTP id
	k3P0p99L008641; Tue, 25 Apr 2006 08:51:18 +0800
Received: from asbmail2.sbell.com.cn ([172.24.208.62]) by 
	asbmail4.sbell.com.cn with Microsoft SMTPSVC(5.0.2195.6713);
	Tue, 25 Apr 2006 08:54:47 +0800
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=gb2312
Content-Transfer-Encoding: quoted-printable
Subject: re: [dhcwg] dhc WG last call on "Domain Suffix Option for DHCPv6"
Date: Tue, 25 Apr 2006 08:54:47 +0800
Message-ID: <9570C1261494D54D9D3115BC2C83429AA2F897@asbmail2.sbell.com.cn>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] dhc WG last call on "Domain Suffix Option for DHCPv6"
Thread-Index: AcZh/1wKJlTQJeilR4eq/4GWIeHzbAFoyMjAABfq+XA=
From: "CTO YAN Renxiang" <Renxiang.Yan@alcatel-sbell.com.cn>
To: "Bernie Volz \(volz\)" <volz@cisco.com>, <Ted.Lemon@nominum.com>,
	<dhcwg@ietf.org>
X-OriginalArrivalTime: 25 Apr 2006 00:54:47.0624 (UTC) 
	FILETIME=[D9945C80:01C66802]
X-imss-version: 2.038
X-imss-result: Passed
X-imss-approveListMatch: *@alcatel-sbell.com.cn
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: Stig Venaas <stig.venaas@uninett.no>,
	"Ralph Droms \(rdroms\)" <rdroms@cisco.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Hi, Ted and Bernie,

Good points, they make the draft precise.
Thank you!=20

Regards,
Renxiang


> -----Original Message-----
> From: Bernie Volz (volz) [mailto:volz@cisco.com]
> Sent: 2006-4-24 21:34
> To: Stig Venaas; dhcwg@ietf.org
> Cc: Ralph Droms (rdroms)
> Subject: RE: [dhcwg] dhc WG last call on "Domain Suffix Option for =
DHCPv6"
>=20
>=20
> I agree with Ted's comment and would extend that text change to the
> Abstract - not just the Introduction.
>=20
> I also have additional nits - For the diagram in section 2, we usually
> call the fields option-code and option-length, not type and=20
> length. Also
> the "16-bits identifier of the type of option" is a bit odd as this is
> the option-code, not the "type" of option. This is further an issue
> since the remainder of the document uses "option code", not type.
>=20
> But, otherwise I agree with advancing this document.
>=20
> - Bernie=20
>=20
> > -----Original Message-----
> > From: Stig Venaas [mailto:stig.venaas@uninett.no]=20
> > Sent: Monday, April 17, 2006 5:14 AM
> > To: dhcwg@ietf.org
> > Cc: Ralph Droms (rdroms)
> > Subject: [dhcwg] dhc WG last call on "Domain Suffix Option=20
> for DHCPv6"
> >=20
> > This message announces a WG last call on "Domain Suffix Option for
> > DHCPv6" <draft-ietf-dhc-dhcpv6-opt-dnsdomain-02.txt>.  The last call
> > will conclude at 1700 ET on 2006-04-30.
> >=20
> > Note that there was a previous last call for revision 00 of=20
> > this draft.=20
> > There were several responses during that last call, and I=20
> > believe this=20
> > version resolves the issues raised.
> >=20
> > Please respond to this WG last call.  If you support=20
> acceptance of the
> > document without change, respond with a simple=20
> acknowledgment, so that
> > support for the document can be assessed.  Lack of=20
> discussion does not
> > represent positive support.  If there is no expression of=20
> support for
> > acceptance during the WG last call, the document will not=20
> be advanced
> > to the IESG.
> >=20
> > "Domain Suffix Option for DHCPv6" specifies an option passed from
> > server to client to specify a domain suffix name to be used for
> > domain name updates.  This draft is available as
> > http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-opt-
> > dnsdomain-02.txt
> >=20
> > Stig
> >=20
> > _______________________________________________
> > dhcwg mailing list
> > dhcwg@ietf.org
> > https://www1.ietf.org/mailman/listinfo/dhcwg
> >=20
>=20
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg
>=20

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



From dhcwg-bounces@ietf.org Wed Apr 26 00:18:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FYbTa-0001Fv-KW; Wed, 26 Apr 2006 00:18:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FYbTZ-0001Fn-6p
	for dhcwg@ietf.org; Wed, 26 Apr 2006 00:18:05 -0400
Received: from imc05.net ([66.39.196.181])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FYbTV-0007KC-V5
	for dhcwg@ietf.org; Wed, 26 Apr 2006 00:18:05 -0400
Received: from imc05.net (imc05 [127.0.0.1])
	by imc05.net (Postfix) with ESMTP id 963361437C3
	for <dhcwg@ietf.org>; Tue, 25 Apr 2006 23:18:01 -0500 (CDT)
Received: (from apache@localhost)
	by imc05.net (8.13.1/8.13.1/Submit) id k3Q4I1Ve001736;
	Tue, 25 Apr 2006 23:18:01 -0500
Date: Tue, 25 Apr 2006 23:18:01 -0500
Message-Id: <200604260418.k3Q4I1Ve001736@imc05.net>
To: dhcwg@ietf.org
MIME-Version: 1.0
From: raj.ooty@gmail.com
X-Spam-Score: 4.6 (++++)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Subject: [dhcwg] Check it out
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: raj.ooty@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>
Content-Type: multipart/mixed; boundary="===============0807617101=="
Errors-To: dhcwg-bounces@ietf.org

--===============0807617101==
Content-type: text/html; charset=iso-8859-1


Sign up so we can play
<br><br> 
									<a href="http://followhere02.com/go.asp?id=1&sourceid=friend=&friend=">http://followhere02.com/go.asp?id=1&sourceid=friend=&friend=</a>
<br><br>
									
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
									This invitation was sent on behalf of your friend,  (raj.ooty@gmail.com).
<br>
									To stop receiving further emails, please <a href="http://followhere02.com/go.asp?id=2">follow-here</a>:
<br><br>
									Kosta Ourani, 6 
<br>
									Pera Chorio Nisou 
<br>
									P.C. 2572 Nicosia, Cyprus


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

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

--===============0807617101==--



From dhcwg-bounces@ietf.org Thu Apr 27 01:39:25 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FYzDQ-000825-De; Thu, 27 Apr 2006 01:39:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FYzDP-000820-0E
	for dhcwg@ietf.org; Thu, 27 Apr 2006 01:38:59 -0400
Received: from zns001-0m9003.yokogawa.co.jp ([203.174.79.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FYzDH-00031x-B7
	for dhcwg@ietf.org; Thu, 27 Apr 2006 01:38:58 -0400
Received: from zns001-0m9003.yokogawa.co.jp (localhost [127.0.0.1])
	by zns001-0m9003.yokogawa.co.jp (8.12.10+Sun/8.12.10) with ESMTP id
	k3R5cjkQ027391
	for <dhcwg@ietf.org>; Thu, 27 Apr 2006 14:38:45 +0900 (JST)
Received: from EXCHANGE03.jp.ykgw.net (zex001-0m9003.jp.ykgw.net [10.0.11.23])
	by zns001-0m9003.yokogawa.co.jp (8.12.10+Sun/8.12.10) with ESMTP id
	k3R5cLcs027252
	for <dhcwg@ietf.org>; Thu, 27 Apr 2006 14:38:21 +0900 (JST)
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: Thu, 27 Apr 2006 14:38:21 +0900
Message-ID: <0260031F55435342859BFB2CCA6773D80AE5C4E6@EXCHANGE03.jp.ykgw.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Issues raised in 65th IETF from TAHI Project
Thread-Index: AcZpvMu+9wGun7o4TcSibAncRlNwQA==
From: <Hideshi.Enokihara@jp.yokogawa.com>
To: <dhcwg@ietf.org>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Subject: [dhcwg] Issues raised in 65th IETF from TAHI Project
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Hi all,

In last IETF, TAHI Project raised  issues in RFCs.
So I'd like to hear your opinions and I'd like to make the consensus.

I raised following 3 issues.

1.How to treat invalid option that does not influence interoperability?

RFC3315 15. Message Validation says,
---------------------------------------
   Clients and servers SHOULD discard any messages that contain options
   that are not allowed to appear in the received message.  For example,
   an IA option is not allowed to appear in an Information-request
   message.=20
----------------------------------------
And also says,
----------------------------------------
A. Appearance of Options in Message Types

   The following table indicates with a "*" the options are allowed in
   each DHCP message type:

           Client Server IA_NA  Option Pref  Time Relay Auth. Server
             ID     ID   IA_TA  Request            Msg.       Unica.
   Solicit   *             *      *           *           *
   Advert.   *      *      *            *                 *
   Request   *      *      *      *           *           *
   Confirm   *             *      *           *           *
   Renew     *      *      *      *           *           *
   Rebind    *             *      *           *           *
   Decline   *      *      *      *           *           *
   Release   *      *      *      *           *           *
   Reply     *      *      *            *                 *     *
   Reconf.   *      *             *                       *
   Inform.   * (see note)         *           *           *
   R-forw.                                          *     *
   R-repl.                                          *     *

   NOTE:

      Only included in Information-Request messages that are sent
      in response to a Reconfigure (see section 19.4.3).

            Status  Rap. User  Vendor Vendor Inter. Recon. Recon.
             Code  Comm. Class Class  Spec.    ID    Msg.  Accept
   Solicit           *     *     *      *                    *
   Advert.    *            *     *      *                    *
   Request                 *     *      *                    *
   Confirm                 *     *      *
   Renew                   *     *      *                    *
   Rebind                  *     *      *                    *
   Decline                 *     *      *
   Release                 *     *      *
   Reply      *      *     *     *      *                    *
   Reconf.                                            *
   Inform.                 *     *      *                    *
   R-forw.                 *     *      *      *
   R-repl.                 *     *      *      *
----------------------------------------

For example, Preference Option, this option is not allowed in Solicit,
Request and Confirm etc... message.
But, Most implementations ignore only such option rather than discarding
the entire message.

Now, our test tool follows the RFC.
Which behavior is correct? Ddiscard message or ignore option?

2.Where is the correct opsition of NotOnLink Status Code option for
Reply to a Request message?

RFC3315 18.2.1. Receipt of Request Messages  says,
---------------------------------------
   If the server finds that the prefix on one or more IP addresses in
   any IA in the message from the client is not appropriate for the link
   to which the client is connected, the server MUST return the IA to
   the client with a Status Code option with the value NotOnLink.
---------------------------------------

I think that this description "the server MUST return the IA to the
client with a ...." is unclear.
This "with" means that "in main part of message" or "in IA option" or in
"IA_address option" ?
Some implementations include this Status code option in main part of
massage, some others in IA_option or IA_Address option.=20

Mr Bernie Volz says,
For Reply to a Request, it should be in IA option.

Can it be consensus?

And I also worry that some other Status Code option's position is
unclear.

3. Is the coexistence of Success and NoBinding Status Code option in
Reply to a Renew acceptable?

Regarding this issue, RFC has no description.

But some implementations include Success Status Code option in main part
of messge and include NoBinding Status Code option in IA opiton.

Is this implementation's behavior  acceptable or not?

If this behavior is acceptable, what is the meaning of Success Status
Code?


What do you think?

Best Regards,
*****************************
Hideshi Enokihara
IPv6 Business
Network & Software Development Dept.
Yokogawa Electric Corporation

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



From dhcwg-bounces@ietf.org Thu Apr 27 08:57:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FZ630-0000xS-VF; Thu, 27 Apr 2006 08:56:42 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FZ62x-0000wp-04
	for dhcwg@ietf.org; Thu, 27 Apr 2006 08:56:39 -0400
Received: from tyholt.uninett.no ([158.38.62.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FZ62v-0002yy-MI
	for dhcwg@ietf.org; Thu, 27 Apr 2006 08:56:38 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by tyholt.uninett.no (Postfix) with ESMTP id B850E87BDE
	for <dhcwg@ietf.org>; Thu, 27 Apr 2006 14:56:20 +0200 (CEST)
Received: from tyholt.uninett.no ([127.0.0.1])
	by localhost (tyholt.uninett.no [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 29988-01-99 for <dhcwg@ietf.org>;
	Thu, 27 Apr 2006 14:56:20 +0200 (CEST)
Received: from [IPv6?2001?700?1?1?213?2ff?fe0e?7215] (unknown
	[IPv6:2001:700:1:1:213:2ff:fe0e:7215])
	by tyholt.uninett.no (Postfix) with ESMTP id 4972E87BD8
	for <dhcwg@ietf.org>; Thu, 27 Apr 2006 14:56:20 +0200 (CEST)
Message-ID: <4450BF6D.5030309@uninett.no>
Date: Thu, 27 Apr 2006 14:56:13 +0200
From: Stig Venaas <stig.venaas@uninett.no>
User-Agent: Mozilla Thunderbird 1.0.8 (X11/20060427)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Minutes from IETF65 dhc wg meeting
References: <44438F2E.1090306@uninett.no>
In-Reply-To: <44438F2E.1090306@uninett.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at uninett.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Stig Venaas wrote:
> Minutes from the IETF 65 wg meeting have been uploaded and can be found 
> at http://www3.ietf.org/proceedings/06mar/minutes/dhc.txt.
> 
> Please let Ralph and me know ASAP if you have any corrections,

I've applied a couple of requested corrections. The current minutes will 
be the final ones unless I get more corrections the next few days,

Stig

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


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



From dhcwg-bounces@ietf.org Fri Apr 28 15:28:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FZYdH-00015D-7g; Fri, 28 Apr 2006 15:28:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FZYdF-00014e-OR
	for dhcwg@ietf.org; Fri, 28 Apr 2006 15:28:01 -0400
Received: from hoemail1.lucent.com ([192.11.226.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FZYdE-0006WF-G7
	for dhcwg@ietf.org; Fri, 28 Apr 2006 15:28:01 -0400
Received: from homail.ho.lucent.com (h135-17-192-10.lucent.com [135.17.192.10])
	by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id k3SJRrKd008046; 
	Fri, 28 Apr 2006 14:27:54 -0500 (CDT)
Received: from kraken (kraken.mh.lucent.com [135.222.148.11]) by
	homail.ho.lucent.com (8.11.7p1+Sun/EMS-1.5 sol2)
	id k3SJRrQ13171; Fri, 28 Apr 2006 15:27:53 -0400 (EDT)
From: Joe Quanaim <jdq@lucent.com>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Issues raised in 65th IETF from TAHI Project
Date: Fri, 28 Apr 2006 15:27:52 -0400
User-Agent: KMail/1.8.3
References: <0260031F55435342859BFB2CCA6773D80AE5C4E6@EXCHANGE03.jp.ykgw.net>
In-Reply-To: <0260031F55435342859BFB2CCA6773D80AE5C4E6@EXCHANGE03.jp.ykgw.net>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200604281527.52631.jdq@lucent.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jdq@lucent.com
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org


Hi Hideshi...

On Thursday 27 April 2006 01:38, Hideshi.Enokihara@jp.yokogawa.com wrote:
> 1.How to treat invalid option that does not influence interoperability?
>
> RFC3315 15. Message Validation says,
> ---------------------------------------
>    Clients and servers SHOULD discard any messages that contain options
>    that are not allowed to appear in the received message.  For example,
>    an IA option is not allowed to appear in an Information-request
>    message.
> ----------------------------------------

>
> Now, our test tool follows the RFC.
> Which behavior is correct? Ddiscard message or ignore option?

Since the statement is a SHOULD, I think both are correct.  I would caution 
that if the an implementation is too aggressive in discarding an otherwise 
valid message, it may make it more difficult in the future to deploy new 
options.

> 2.Where is the correct opsition of NotOnLink Status Code option for
> Reply to a Request message?
>
> RFC3315 18.2.1. Receipt of Request Messages  says,
> ---------------------------------------
>    If the server finds that the prefix on one or more IP addresses in
>    any IA in the message from the client is not appropriate for the link
>    to which the client is connected, the server MUST return the IA to
>    the client with a Status Code option with the value NotOnLink.
> ---------------------------------------
>
> I think that this description "the server MUST return the IA to the
> client with a ...." is unclear.
> This "with" means that "in main part of message" or "in IA option" or in
> "IA_address option" ?
> Some implementations include this Status code option in main part of
> massage, some others in IA_option or IA_Address option.
>
> Mr Bernie Volz says,
> For Reply to a Request, it should be in IA option.
>
> Can it be consensus?
>
> And I also worry that some other Status Code option's position is
> unclear.

I agree with this assessment.  I think the rfc does not make it clear where 
an arbitrary status code option should be.  Is it valid on the ia_address 
options, ia_na options, or the message options?  A client probably needs 
to check all three, especially since new status codes can appear in the 
future (prefix delegation added a status code).

In a hypothetical example, what if a client made a request with two ia_na 
options, but a server could only fulfill one of them.  Where would the 
status code(s) be placed?

> 3. Is the coexistence of Success and NoBinding Status Code option in
> Reply to a Renew acceptable?
>
> Regarding this issue, RFC has no description.
>
> But some implementations include Success Status Code option in main part
> of messge and include NoBinding Status Code option in IA opiton.
>
> Is this implementation's behavior  acceptable or not?
>
> If this behavior is acceptable, what is the meaning of Success Status
> Code?

I think this question and your second question require some clarification 
to the status code option.

Thanks,
Joe Quanaim.

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



From dhcwg-bounces@ietf.org Fri Apr 28 16:55:16 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FZZzZ-0006fo-SV; Fri, 28 Apr 2006 16:55:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FZZzY-0006fS-2l
	for dhcwg@ietf.org; Fri, 28 Apr 2006 16:55:08 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FZZzW-0003VL-Qw
	for dhcwg@ietf.org; Fri, 28 Apr 2006 16:55:08 -0400
Received: from rtp-core-1.cisco.com ([64.102.124.12])
	by rtp-iport-2.cisco.com with ESMTP; 28 Apr 2006 16:55:07 -0400
X-IronPort-AV: i="4.04,164,1144036800"; 
	d="scan'208"; a="87474956:sNHT30172554"
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k3SKt6TL003353; 
	Fri, 28 Apr 2006 16:55:06 -0400 (EDT)
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Fri, 28 Apr 2006 16:55:05 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 28 Apr 2006 16:54:28 -0400
Message-ID: <9C192798F2F9454381E4811C41A4413401A64C6D@xmb-rtp-20a.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [New I-D] DHCPv6 Relay Agent Echo Request Option
Thread-Index: AcZrBfCbfFkVTShPRAOtDgae5wNihQ==
From: "Shengyou Zeng \(szeng\)" <szeng@cisco.com>
To: <dhcwg@ietf.org>
X-OriginalArrivalTime: 28 Apr 2006 20:55:06.0219 (UTC)
	FILETIME=[073F1BB0:01C66B06]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Subject: [dhcwg] [New I-D] DHCPv6 Relay Agent Echo Request Option
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

We posted a new I-D as follows.  We would appreciate your comments.

Title: DHCPv6 Relay Agent Echo Request Option
Abstract:
This memo defines a Relay Agent Echo Request option for the Dynamic Host
Configuration Protocol for IPv6 (DHCPv6). The option allows a DHCPv6
relay agent to request a list of relay agent options that the server
echoes back to the relay agent.
Author(s): Shengyou Zeng, Kim Kinnear, Bernie Volz, John Brzozowski

URL:
http://www.ietf.org/internet-drafts/draft-szeng-dhc-dhcpv6-ero-00.txt

Thanks.

-Shengyou

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



From dhcwg-bounces@ietf.org Sun Apr 30 05:01:29 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Fa7nm-0004PY-LS; Sun, 30 Apr 2006 05:01:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Fa7nl-0004OX-1J
	for dhcwg@ietf.org; Sun, 30 Apr 2006 05:01:13 -0400
Received: from szxga01-in.huawei.com ([61.144.161.53] helo=huawei.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fa7nk-0001BS-Co
	for dhcwg@ietf.org; Sun, 30 Apr 2006 05:01:13 -0400
Received: from huawei.com (szxga01-in [172.24.2.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IYJ00CHP27Q6A@szxga01-in.huawei.com> for
	dhcwg@ietf.org; Sun, 30 Apr 2006 16:57:26 +0800 (CST)
Received: from huawei.com ([172.24.1.3])
	by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTP id <0IYJ0013R27P3S@szxga01-in.huawei.com> for
	dhcwg@ietf.org; Sun, 30 Apr 2006 16:57:26 +0800 (CST)
Received: from z51809A ([10.164.5.21])
	by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25
	(built Mar
	3 2004)) with ESMTPA id <0IYJ00BTM30TQ0@szxml01-in.huawei.com> for
	dhcwg@ietf.org; Sun, 30 Apr 2006 17:15:01 +0800 (CST)
Date: Sun, 30 Apr 2006 16:56:50 +0800
From: Amy <zhaoyuping@huawei.com>
Subject: RE: [dhcwg] [New I-D] DHCPv6 Relay Agent Echo Request Option
In-reply-to: <9C192798F2F9454381E4811C41A4413401A64C6D@xmb-rtp-20a.amer.cisco.com>
To: dhcwg@ietf.org
Message-id: <000101c66c34$082a0ab0$1505a40a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
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: 244a2fd369eaf00ce6820a760a3de2e8
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Hi,all

    I just reading the draft "draft-szeng-dhc-dhcpv6-ero-00.txt", and I
have a question:
    
    In rfc 3315, section 15.14 Relay-reply Message, Page 32, there is
the following text:

	"Clients and servers MUST discard any received Relay-reply
messages."

    but in the draft , section 5.DHCPv6 Server Behavior, Page  4, there
is the following text:
	
	"A server SHOULD perform ERO processing after processing the ORO
and
   	other options processing with respect to the Relay-Reply.  For
each
   	option in the ERO:
   	a.  If the option is already in the received Relay-Reply, the
server
       	MUST ignore that option and continue to process any remaining
       	options in the ERO."
   
     Whether there is an error in above text, not ""received
Relay-Reply", but other words?

    is it right?

Thanks!

Amy
	
> -----Original Message-----
> From: Shengyou Zeng (szeng) [mailto:szeng@cisco.com] 
> Sent: Saturday, April 29, 2006 4:54 AM
> To: dhcwg@ietf.org
> Subject: [dhcwg] [New I-D] DHCPv6 Relay Agent Echo Request Option
> 
> 
> We posted a new I-D as follows.  We would appreciate your comments.
> 
> Title: DHCPv6 Relay Agent Echo Request Option
> Abstract:
> This memo defines a Relay Agent Echo Request option for the 
> Dynamic Host Configuration Protocol for IPv6 (DHCPv6). The 
> option allows a DHCPv6 relay agent to request a list of relay 
> agent options that the server echoes back to the relay agent.
> Author(s): Shengyou Zeng, Kim Kinnear, Bernie Volz, John Brzozowski
> 
> URL: 
> http://www.ietf.org/internet-drafts/draft-szeng-dhc-dhcpv6-ero-00.txt
> 
> Thanks.
> 
> -Shengyou
> 
> _______________________________________________
> 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



