From dhcwg-bounces@ietf.org Thu Aug 02 19:01:04 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGjf3-0001sW-FX; Thu, 02 Aug 2007 19:00:53 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IGjf1-0001rq-8f; Thu, 02 Aug 2007 19:00:51 -0400
Received: from mx0.starentnetworks.com ([12.38.223.203])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IGjf0-0005Ae-Ew; Thu, 02 Aug 2007 19:00:50 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx0.starentnetworks.com (Postfix) with ESMTP id B0A3A900FB;
	Thu,  2 Aug 2007 19:00:46 -0400 (EDT)
Received: from mx0.starentnetworks.com ([127.0.0.1])
	by localhost (mx0.starentnetworks.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 04566-15; Thu, 2 Aug 2007 19:00:43 -0400 (EDT)
Received: from exchtewks1.starentnetworks.com (exchtewks1.starentnetworks.com
	[10.2.4.28]) by mx0.starentnetworks.com (Postfix) with ESMTP;
	Thu,  2 Aug 2007 19:00:43 -0400 (EDT)
Received: from exchtewks2.starentnetworks.com ([10.2.4.27]) by
	exchtewks1.starentnetworks.com with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 2 Aug 2007 19:01:07 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 2 Aug 2007 19:00:17 -0400
Message-ID: <7CCD07160348804497EF29E9EA5560D7024DA3E6@exchtewks2.starentnetworks.com>
In-Reply-To: <BE4B07D4197BF34EB3B753DD34EBCD1301BA9697@de01exm67.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Mip4] draft-ietf-mip4-gen-ext-03.txt
Thread-Index: AcfTe0Ke/BKsgd15SyWMrcjFTjhBOwB2i4TA
From: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
To: "McCann Peter-A001034" <pete.mccann@motorola.com>,
	<mip4@ietf.org>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 02 Aug 2007 23:01:07.0976 (UTC)
	FILETIME=[02D66880:01C7D559]
X-Virus-Scanned: amavisd-new 2.2.1 (20041222) at mx0.starentnetworks.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: 
Subject: [dhcwg] RE: [Mip4] draft-ietf-mip4-gen-ext-03.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Hi Pete,

I think the source of the confusion is the use of DHCP options. The
initial version of this I-D did not propose to use DHCP options at all.
The proposal contained a few possible host config parameters that we
would have defined. However, someone saw the light, and suggested that
instead of redesigning the host config options from scratch, why not we
used the options and the format of the options carrying config info as
defined in DHCP. It made sense; hence we decided to accept that
approach.

Now, I see that people are mixing the use of DHCP protocol with MIP4
host config options. I think this is a digression that we should avoid.
We need to understand the scope of the I-D. It does not rule out other
ways to do host configuration when the MN is using MIP4. It defines _a_
way that is Mobile IP specific. It is also the most efficient one from
the number of round trips point of view.

When you say that running DHCP inside MIP4 tunnel allows for a single
protocol to be used whether the MN is at home or visiting, I have a
question. How is it possible for the MN to fetch config info from the
visited network when RT is negotiated and enforced at the FA?=20

BTW, the approach specified in the draft-ietf-mip4-gen-ext-03.txt allows
the use of a single protocol i.e. MIP4 to be used to fetch config info
from home and visited networks, not to mention with fewer number of
messages.

Another issue that we need to think about the use of DHCP inside MIP4
tunnel is security. We cannot prohibit the MN to run DHCPINFORM only,
right? The MN may start doing IP address config (lease and release). How
to secure these DHCP messages? If we intend to only allow the MN to send
DHCPINFORM, how do we prevent it from sending other DHCP messages?

AFAIK, RFC 3118 is not widely implemented and used. Even if it is, we
can't expect the MIP4 implementations to start implementing RFC 3118
just to get a few config info from the home domain.

Regards,
Kuntal

> -----Original Message-----
> From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com]
> Sent: Tuesday, July 31, 2007 9:01 AM
> To: mip4@ietf.org; dhcwg@ietf.org
> Subject: [Mip4] draft-ietf-mip4-gen-ext-03.txt
>=20
> A question has arisen during the last call for
> draft-ietf-mip4-gen-ext-03.txt.
>=20
> The draft includes the following text:
>=20
>     There are mechanisms
>     such as DHCP for the mobile node to configure information from the
>     foreign network, but not from the home network when the mobile
node
>     is not attached to the home network.
>=20
> However, this may not be strictly true.  In particular,
> it might be possible to use a DHCPINFORM message through
> the tunnel that was established with Mobile IP, thus eliminating
> the need to encode DHCP options inside Mobile IP messages.
> This would allow for a single configuration protocol to be
> used whether the MN is at home or visiting.
>=20
> I think we may have touched on this question during our last
> chartering discussion but we might not have explored all the
> ramifications.  Please, if you have an opinion either way
> express it now and give some background as to why you think so.
> It is possible that we might turn this draft into a BCP-like
> document for how to configure and run DHCP over the tunnel
> to the home network.
>=20
> -Pete
>=20
>=20
> --
> Mip4 mailing list: Mip4@ietf.org
>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>      Charter page: http://www.ietf.org/html.charters/mip4-charter.html
> Supplemental site: http://www.mip4.org/

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



From dhcwg-bounces@ietf.org Mon Aug 06 03:08:28 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IHwhT-0004fs-7R; Mon, 06 Aug 2007 03:08:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IHwhS-0004fm-Bl
	for dhcwg@ietf.org; Mon, 06 Aug 2007 03:08:22 -0400
Received: from m13-59.163.com ([220.181.13.59])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IHwhP-0005bh-Gk
	for dhcwg@ietf.org; Mon, 06 Aug 2007 03:08:22 -0400
Received: from 218.81.225.18 ( 218.81.225.18 [218.81.225.18] ) by
	ajax-webmail-wmsvr59 (Coremail) ; Mon, 6 Aug 2007 15:08:14 +0800 (CST)
Date: Mon, 6 Aug 2007 15:08:14 +0800 (CST)
From: coffee_ccc <coffee_ccc@163.com>
To: dhcwg@ietf.org
Message-ID: <21689950.1805341186384094476.JavaMail.coremail@bj163app59.163.com>
MIME-Version: 1.0
X-Originating-IP: [220.181.12.224 (218.81.225.18)]
X-Priority: 3
X-Mailer: Coremail Webmail Server Version XT_070725 build
	070725(3676.1195.1194) Copyright (c) 2002-2007 www.mailtech.cn 163com
X-Spam-Score: 4.3 (++++)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Subject: [dhcwg] what's the DHCP's timeout ?
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="===============2112142861=="
Errors-To: dhcwg-bounces@ietf.org

--===============2112142861==
Content-Type: multipart/Alternative; 
	boundary="----=_Part_190081_11430999.1186384094475"

------=_Part_190081_11430999.1186384094475
Content-Type: text/plain; charset=gbk
Content-Transfer-Encoding: 7bit

 Hi,all :
   Thank you for reading.
   I want to know the timeout in dhcp protocal?
   And I found little useful infomation in RFC 2131 & 2132 & so on .
  Even I don't konw the title(dhcp's timeout) whether right or not ?
 
  For example :  A ask for a IP addr from DHCP Server and how long it will  timeout if the Server has something wrong.
  Thanks for any reply.
------=_Part_190081_11430999.1186384094475
Content-Type: text/html; charset=gbk
Content-Transfer-Encoding: quoted-printable

<div>&nbsp;Hi,all :<br>&nbsp;&nbsp; Thank you for reading. <br>&nbsp;&nbsp;=
 I want to know the timeout in dhcp protocal?<br>&nbsp;&nbsp; And I found l=
ittle useful infomation in RFC 2131 &amp; 2132 &amp; so on .<br>&nbsp; Even=
 I don't konw the title(dhcp's timeout) whether right or not ?<br></div><di=
v>&nbsp; <br>&nbsp; For example :&nbsp; A ask for a IP addr from DHCP Serve=
r and how long it will&nbsp; timeout if the Server has something wrong.  <b=
r></div><div>&nbsp;</div><div>&nbsp;Thanks for any reply.<br></div><br><!--=
 footer --><br><hr>
<a style=3D"font-size:14px;line-height:15px; color:#000; text-decoration:no=
ne" href=3D"http://event.mail.163.com/chanel/xy3.htm?from=3D163_NO9" target=
=3D"_blank"><span style=3D"text-decoration:underline; color:blue">=A1=B6=B4=
=F3 =BB=B0 =CE=F7 =D3=CE 3=A1=B7 =CA=D7 =BD=EC =CD=E6 =BC=D2 =BC=FB =C3=E6 =
=BB=E1 =BC=B4 =BD=AB =D4=DA =B9=E3 =D6=DD =D5=D9 =BF=AA=A3=A1=BE=B4 =C7=EB =
=B9=D8 =D7=A2 >></span> </a>
------=_Part_190081_11430999.1186384094475--



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

--===============2112142861==--





From dhcwg-bounces@ietf.org Mon Aug 06 04:10:19 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IHxfH-0006hE-Bk; Mon, 06 Aug 2007 04:10:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IHxfF-0006VX-RC
	for dhcwg@ietf.org; Mon, 06 Aug 2007 04:10:09 -0400
Received: from tyholt.uninett.no ([2001:700:1::eecb])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IHxfF-0007ok-Hv
	for dhcwg@ietf.org; Mon, 06 Aug 2007 04:10:09 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by tyholt.uninett.no (Postfix) with ESMTP id 32429B5A76
	for <dhcwg@ietf.org>; Mon,  6 Aug 2007 10:10:08 +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 03418-01-84 for <dhcwg@ietf.org>;
	Mon, 6 Aug 2007 10:10:08 +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 0DD8BB5A6D
	for <dhcwg@ietf.org>; Mon,  6 Aug 2007 10:10:08 +0200 (CEST)
Message-ID: <46B6D75F.6040003@uninett.no>
Date: Mon, 06 Aug 2007 10:10:07 +0200
From: Stig Venaas <stig.venaas@uninett.no>
User-Agent: Thunderbird 2.0.0.5 (X11/20070731)
MIME-Version: 1.0
To: dhcwg <dhcwg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at uninett.no
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Subject: [dhcwg] Adopting draft-dhankins-dhcp-option-guidelines-01 as wg
	work item
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

There was consensus at the dhc wg meeting in Chicago to adopt
draft-dhankins-dhcp-option-guidelines-01 as a dhc wg work item.

If there are no objections posted to the wg mailing list, the
chairs will accept the draft as a wg work item on 2007-08-20.

Stig

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



From dhcwg-bounces@ietf.org Mon Aug 06 11:02:55 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1II46W-0003ff-LG; Mon, 06 Aug 2007 11:02:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1II46V-0003fa-F7
	for dhcwg@ietf.org; Mon, 06 Aug 2007 11:02:43 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1II46U-0008Rx-UT
	for dhcwg@ietf.org; Mon, 06 Aug 2007 11:02:43 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 17B845A6E5; Mon,  6 Aug 2007 08:02:41 -0700 (PDT)
Date: Mon, 6 Aug 2007 08:02:41 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] what's the DHCP's timeout ?
Message-ID: <20070806150240.GA20352@isc.org>
References: <21689950.1805341186384094476.JavaMail.coremail@bj163app59.163.com>
Mime-Version: 1.0
In-Reply-To: <21689950.1805341186384094476.JavaMail.coremail@bj163app59.163.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
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="===============0790628214=="
Errors-To: dhcwg-bounces@ietf.org


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


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

On Mon, Aug 06, 2007 at 03:08:14PM +0800, coffee_ccc wrote:
>    I want to know the timeout in dhcp protocal?
>    And I found little useful infomation in RFC 2131 & 2132 & so on .
>   Even I don't konw the title(dhcp's timeout) whether right or not ?

It depends largely on what state the client is in.  You can find
the general guidance in section 4.1 ("use an exponential backoff"),
but for example there are special rules for clients who never
received DHCPOFFERs, clients responding to DHCPOFFERs, and clients who
are RENEWING or REBINDING.

--=20
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil?	 https://secure.isc.org/store/t-shirt/
--=20
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins

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

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

iD8DBQFGtzgQcXeLeWu2vmoRAjlVAJ9OcZHXb4a6rk2tqtDoaZQXLiF0iACgpl5S
+79e6HjlWD0IrZHPntyRP2k=
=ApPe
-----END PGP SIGNATURE-----

--IS0zKkzwUGydFO0o--


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

--===============0790628214==--




From dhcwg-bounces@ietf.org Fri Aug 10 18:01:46 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJcWU-0003hn-KR; Fri, 10 Aug 2007 17:59:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJcWT-0003hg-KD
	for dhcwg@ietf.org; Fri, 10 Aug 2007 17:59:57 -0400
Received: from relay1.mentorg.com ([192.94.38.131])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IJcWS-0000Mq-73
	for dhcwg@ietf.org; Fri, 10 Aug 2007 17:59:57 -0400
Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58])
	by relay1.mentorg.com with esmtp 
	id 1IJcWR-0006er-Dd from tammy_leino@mentor.com 
	for dhcwg@ietf.org; Fri, 10 Aug 2007 14:59:55 -0700
Received: from SVR-ALH-EXC-02.mgc.mentorg.com ([134.86.110.227]) by
	SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 10 Aug 2007 14:59:54 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 10 Aug 2007 16:59:53 -0500
Message-ID: <7ECEF9368E169544B43882BC98EB5D92032DA835@SVR-ALH-EXC-02.mgc.mentorg.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: prefix length determination for DHCPv6
Thread-Index: AcfbmcxEtVg1JXy6RgihzrIyHOOAtg==
From: "Leino, Tammy" <tammy_leino@mentor.com>
To: <dhcwg@ietf.org>
X-OriginalArrivalTime: 10 Aug 2007 21:59:54.0670 (UTC)
	FILETIME=[C8AE64E0:01C7DB99]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Subject: [dhcwg] prefix length determination 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>
Content-Type: multipart/mixed; boundary="===============1135356511=="
Errors-To: dhcwg-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1135356511==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7DB99.C81711D8"

This is a multi-part message in MIME format.

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

Hello,

In implementing RFC 3315, I see no option or field in the IA_NA option =
for a prefix length associated with an assigned IPv6 address.  How does =
the client determine the prefix length of the IPv6 address the server is =
assigning?

Furthermore, in the absence of a configured IPv6 router on the link, can =
the client use the DHCPv6 server to find a default gateway out of the =
local network?  If so, what RFC specifies this option?

Any help or referrals to additional RFCs would be much appreciated.

Best Regards,
Tammy Leino

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>prefix length determination for DHCPv6</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">Hello,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">In implementing RFC 3315, I see no =
option or field in the IA_NA option for a prefix length associated with =
an assigned IPv6 address.&nbsp; How does the client determine the prefix =
length of the IPv6 address the server is assigning?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Furthermore, in the absence of a =
configured IPv6 router on the link, can the client use the DHCPv6 server =
to find a default gateway out of the local network?&nbsp; If so, what =
RFC specifies this option?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Any help or referrals to additional =
RFCs would be much appreciated.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Best Regards,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Tammy Leino</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7DB99.C81711D8--


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

--===============1135356511==--




From dhcwg-bounces@ietf.org Fri Aug 10 18:16:44 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJcl2-0007pB-5g; Fri, 10 Aug 2007 18:15:00 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJcl0-0007p1-Pp
	for dhcwg@ietf.org; Fri, 10 Aug 2007 18:14:58 -0400
Received: from relay02.pair.com ([209.68.5.16])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IJcl0-0007bs-Eq
	for dhcwg@ietf.org; Fri, 10 Aug 2007 18:14:58 -0400
Received: (qmail 98905 invoked by uid 0); 10 Aug 2007 22:14:56 -0000
Received: from 68.246.127.117 (HELO Inbox) (68.246.127.117)
	by relay02.pair.com with SMTP; 10 Aug 2007 22:14:56 -0000
X-pair-Authenticated: 68.246.127.117
MIME-Version: 1.0
From: "John Jason Brzozowski (JJMB)" <jjmb@jjmb.com>
Subject: RE: [dhcwg] prefix length determination for DHCPv6
Date: Fri, 10 Aug 2007 18:14:11 -0400
Importance: normal
X-Priority: 3
To: "Leino, Tammy" <tammy_leino@mentor.com>, <dhcwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org
Message-Id: <E1IJcl2-0007pB-5g@megatron.ietf.org>

Hello Tammy,

RAs could be configured to supply the length for prefixes valid on the link=
  Otherwise, there is no DHCPv6 option that can be used to supply this dat=
a.

Regarding, your second question why would you need information about the ro=
uter if it does not exist or is not configured to route?   Just looking for=
 a little more information.

John
######################
John Jason Brzozowski, CISSP, RHCT
jjmb@jjmb.com
484-994-6787
######################

-----Original Message-----
From: "Leino, Tammy" <tammy_leino@mentor.com>
To: dhcwg@ietf.org
Sent: 08/10/07 17:59
Subject: [dhcwg] prefix length determination for DHCPv6

Hello,

In implementing RFC 3315, I see no option or field in the IA_NA option for =
a prefix length associated with an assigned IPv6 address.  How does the cli=
ent determine the prefix length of the IPv6 address the server is assigning=
?

Furthermore, in the absence of a configured IPv6 router on the link, can th=
e client use the DHCPv6 server to find a default gateway out of the local n=
etwork?  If so, what RFC specifies this option?

Any help or referrals to additional RFCs would be much appreciated.

Best Regards,
Tammy Leino


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



From dhcwg-bounces@ietf.org Fri Aug 10 18:28:16 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJcwA-0002HJ-LN; Fri, 10 Aug 2007 18:26:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJcw9-0002HB-46
	for dhcwg@ietf.org; Fri, 10 Aug 2007 18:26:29 -0400
Received: from relay1.mentorg.com ([192.94.38.131])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IJcw8-0007qV-Le
	for dhcwg@ietf.org; Fri, 10 Aug 2007 18:26:29 -0400
Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58])
	by relay1.mentorg.com with esmtp 
	id 1IJcw7-0000Yd-NR from tammy_leino@mentor.com ;
	Fri, 10 Aug 2007 15:26:27 -0700
Received: from SVR-ALH-EXC-02.mgc.mentorg.com ([134.86.110.227]) by
	SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 10 Aug 2007 15:26:26 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] prefix length determination for DHCPv6
Date: Fri, 10 Aug 2007 17:26:25 -0500
Message-ID: <7ECEF9368E169544B43882BC98EB5D92032DA836@SVR-ALH-EXC-02.mgc.mentorg.com>
In-Reply-To: <SVR-ORW-EXC-10F7AQ40007413f@SVR-ORW-EXC-10.mgc.mentorg.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] prefix length determination for DHCPv6
Thread-Index: Acfbm+XKhq0dhXv4QFymbBSmbJv6YgAAC8oQ
From: "Leino, Tammy" <tammy_leino@mentor.com>
To: "John Jason Brzozowski (JJMB)" <jjmb@jjmb.com>,
	<dhcwg@ietf.org>
X-OriginalArrivalTime: 10 Aug 2007 22:26:26.0967 (UTC)
	FILETIME=[7DC3A270:01C7DB9D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Thank you very much for the information John.

>>RAs could be configured to supply the length for prefixes valid on the =
link  Otherwise, there is no DHCPv6 option that can be used to supply =
this data.

What if the router is configured just to inform the node to use DHCPv6 =
to obtain an address and does not specify any prefix options in the RA?  =
The only place I see to specify a prefix length in an RA is in a prefix =
option.  Is there some other way an RA could relay a prefix length to a =
node?  If not, how does the client know the prefix length of the address =
the DHCP server is assigning?  It seems to me that the DHCPv6 server =
should be sending a prefix length with the address it assigns.  Is there =
a reason this was not included in the specification?

>>Regarding, your second question why would you need information about =
the router if it does not exist or is not configured to route?   Just =
looking for a little more information.

In implementing this RFC, I am not making assumptions that there will be =
an IPv6-configured router on link.  This does not mean there is not a =
router on link that can forward IPv6 messages, it just means there might =
not be a router on link that sends RAs.  Just because a node can forward =
IPv6 traffic does not mean it will necessarily be configured to send =
RAs.

I greatly value your advice and comments in this area.

Best Regards,
Tammy






-----Original Message-----
From: John Jason Brzozowski (JJMB) [mailto:jjmb@jjmb.com]
Sent: Friday, August 10, 2007 6:14 PM
To: Leino, Tammy; dhcwg@ietf.org
Subject: RE: [dhcwg] prefix length determination for DHCPv6


Hello Tammy,

RAs could be configured to supply the length for prefixes valid on the =
link  Otherwise, there is no DHCPv6 option that can be used to supply =
this data.

Regarding, your second question why would you need information about the =
router if it does not exist or is not configured to route?   Just =
looking for a little more information.

John
######################
John Jason Brzozowski, CISSP, RHCT
jjmb@jjmb.com
484-994-6787
######################

-----Original Message-----
From: "Leino, Tammy" <tammy_leino@mentor.com>
To: dhcwg@ietf.org
Sent: 08/10/07 17:59
Subject: [dhcwg] prefix length determination for DHCPv6

Hello,

In implementing RFC 3315, I see no option or field in the IA_NA option =
for a prefix length associated with an assigned IPv6 address.  How does =
the client determine the prefix length of the IPv6 address the server is =
assigning?

Furthermore, in the absence of a configured IPv6 router on the link, can =
the client use the DHCPv6 server to find a default gateway out of the =
local network?  If so, what RFC specifies this option?

Any help or referrals to additional RFCs would be much appreciated.

Best Regards,
Tammy Leino


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



From dhcwg-bounces@ietf.org Fri Aug 10 19:05:23 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJdW4-00012H-NZ; Fri, 10 Aug 2007 19:03:36 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJdW4-00012C-2N
	for dhcwg@ietf.org; Fri, 10 Aug 2007 19:03:36 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IJdW3-0000B4-Ky
	for dhcwg@ietf.org; Fri, 10 Aug 2007 19:03:36 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 11 Aug 2007 01:03:33 +0200
X-IronPort-AV: i="4.19,246,1183327200"; 
	d="scan'208"; a="150329648:sNHT47664898"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7AN3WP6000648; 
	Sat, 11 Aug 2007 01:03:32 +0200
Received: from gpk-xdm-001.cisco.com (gpk-xdm-001.cisco.com [64.103.70.176])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7AN3Tx0005480; 
	Fri, 10 Aug 2007 23:03:30 GMT
Received: from gpk-xdm-001.cisco.com (localhost.localdomain [127.0.0.1])
	by gpk-xdm-001.cisco.com (8.13.1/8.13.1) with ESMTP id l7AN3TuY022346; 
	Sat, 11 Aug 2007 00:03:29 +0100
Received: (from otroan@localhost)
	by gpk-xdm-001.cisco.com (8.13.1/8.13.1/Submit) id l7AN3TvB022345;
	Sat, 11 Aug 2007 00:03:29 +0100
X-Authentication-Warning: gpk-xdm-001.cisco.com: otroan set sender to
	ot@cisco.com using -f
From: Ole Troan <ot@cisco.com>
To: "Leino\, Tammy" <tammy_leino@mentor.com>
Subject: Re: [dhcwg] prefix length determination for DHCPv6
References: <7ECEF9368E169544B43882BC98EB5D92032DA836@SVR-ALH-EXC-02.mgc.mentorg.com>
Date: Sat, 11 Aug 2007 00:03:28 +0100
In-Reply-To: <7ECEF9368E169544B43882BC98EB5D92032DA836@SVR-ALH-EXC-02.mgc.mentorg.com>
	(Tammy Leino's message of "Fri\, 10 Aug 2007 17\:26\:25 -0500")
Message-ID: <7t53ayruh4v.fsf@gpk-xdm-001.cisco.com>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1639; t=1186787012;
	x=1187651012; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=ot@cisco.com;
	z=From:=20Ole=20Troan=20<ot@cisco.com>
	|Subject:=20Re=3A=20[dhcwg]=20prefix=20length=20determination=20for=20DHC
	Pv6 |Sender:=20;
	bh=bur1b0farUWbK2yf49o86wAGLXCm7ysOo39RjWXhwPU=;
	b=JSoMeMp6AmO2A1u0OmbGt/ARpRMcZJ9EKUpSJR3Jqt/98tl7B1E+xfvZQl9NvoduswLvhqBo
	+wNn0sBO3eFjXimVAldjLfFKY8Sp0Gw1shp1ploJdm8OHm/n/Ygydszj;
Authentication-Results: ams-dkim-2; header.From=ot@cisco.com; dkim=pass (sig
	from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: dhcwg@ietf.org, "John Jason Brzozowski \(JJMB\)" <jjmb@jjmb.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

> Thank you very much for the information John.
>
>>>RAs could be configured to supply the length for prefixes valid on the link
>>> Otherwise, there is no DHCPv6 option that can be used to supply this data.
>
> What if the router is configured just to inform the node to use DHCPv6
> to obtain an address and does not specify any prefix options in the
> RA?  The only place I see to specify a prefix length in an RA is in a
> prefix option.  Is there some other way an RA could relay a prefix
> length to a node?  If not, how does the client know the prefix length
> of the address the DHCP server is assigning?  It seems to me that the
> DHCPv6 server should be sending a prefix length with the address it
> assigns.  Is there a reason this was not included in the
> specification?

an address does not have a prefix length. a host needs to know the
on-link prefix for on-link determination. that's done with ND.

>>>Regarding, your second question why would you need information about the
>>> router if it does not exist or is not configured to route?  Just looking
>>> for a little more information.
>
> In implementing this RFC, I am not making assumptions that there will
> be an IPv6-configured router on link.  This does not mean there is not
> a router on link that can forward IPv6 messages, it just means there
> might not be a router on link that sends RAs.  Just because a node can
> forward IPv6 traffic does not mean it will necessarily be configured
> to send RAs.

then your only option is manual configuration. which doesn't seem
optimal. what's wrong with RFC2461 router discovery?

/ot

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



From dhcwg-bounces@ietf.org Fri Aug 10 19:21:45 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJdlt-00008f-Ca; Fri, 10 Aug 2007 19:19:57 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJdlr-00008O-7J; Fri, 10 Aug 2007 19:19:55 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IJdlq-0000Ss-FB; Fri, 10 Aug 2007 19:19:55 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 10 Aug 2007 19:19:54 -0400
X-IronPort-AV: i="4.19,246,1183348800"; 
	d="scan'208"; a="67699250:sNHT84478146"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7ANJscx031558; 
	Fri, 10 Aug 2007 19:19:54 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7ANJUjc007857; 
	Fri, 10 Aug 2007 23:19:53 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 10 Aug 2007 19:19:45 -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, 10 Aug 2007 19:19:45 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB2104B6693D@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <7ECEF9368E169544B43882BC98EB5D92032DA83B@SVR-ALH-EXC-02.mgc.mentorg.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: prefix length determination for DHCPv6
Thread-Index: AcfboUHk1kkPl/zjSFmlUg6ok1IdnwAAPQ+wAAB9QeA=
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "Leino, Tammy" <tammy_leino@mentor.com>,
	"Iljitsch van Beijnum" <iljitsch@muada.com>
X-OriginalArrivalTime: 10 Aug 2007 23:19:45.0378 (UTC)
	FILETIME=[F02A6C20:01C7DBA4]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5630; t=1186787994;
	x=1187651994; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=volz@cisco.com;
	z=From:=20=22Bernie=20Volz=20\(volz\)=22=20<volz@cisco.com>
	|Subject:=20RE=3A=20prefix=20length=20determination=20for=20DHCPv6
	|Sender:=20
	|To:=20=22Leino, =20Tammy=22=20<tammy_leino@mentor.com>,
	=0A=20=20=20=20=20
	=20=20=20=22Iljitsch=20van=20Beijnum=22=20<iljitsch@muada.com>;
	bh=1XSHipOlbxTN/2Z4d425D+FCEgye4BDGU0PFet4K9WI=;
	b=lZRnowAFfq6rmmmsDOhqdTq1Q9CTCEZRnlQgYxCFGQnVcCWhqttt3v4YwIA/zoGxdb+4QG31
	3zEX/KkkWbbmtFmyQxQEziOFrikwVtP3JzsCRROM95HCt4Sl2y4aTUVF;
Authentication-Results: rtp-dkim-1; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Cc: dhcwg@ietf.org, ipv6@ietf.org,
	"John Jason Brzozowski \(JJMB\)" <jjmb@jjmb.com>
Subject: [dhcwg] RE: prefix length determination 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

The PIOs in an RA tells a node whether it can autoconfigure or not via
the A bit. If the A bit is not set, the node can not use SLAAC. But, it
CAN use the PIO information to build the table of what prefixes exist
and which are on-link.

That is why there is no need for DHCPv6 to provide default router and
prefix information because the RA does that.

Having two ways (DHCPv6 and RA) provide this information is just asking
for a lot of trouble. What if they conflict each other? Who wins?

And, if there are no routers, there's no need for anything but
link-local addresses (since you can't get off the local link).

It is far better to have the device that is providing the service (ie,
the router which is providing routing services) provide this type of
information.

- Bernie

-----Original Message-----
From: Leino, Tammy [mailto:tammy_leino@mentor.com]=20
Sent: Friday, August 10, 2007 7:10 PM
To: Iljitsch van Beijnum
Cc: ipv6@ietf.org; John Jason Brzozowski (JJMB)
Subject: RE: prefix length determination for DHCPv6

Thank you very much for your comments.

Regarding your comment:

>> So I don't think we should present NOT having RAs as a valid =20
configuration option. This way, we get to avoid the situations above. =20
If people want to configure hosts using DHCPv6 they should have =20
routers send out RAs with the M bit set and with no prefix information.

The reason I am not assuming there is a router on link configured to
send RAs with prefix options is because I don't see the point of DHCPv6
configuring addresses if a router is configured to do the same job.
Since the prefix length is carried in a prefix option of an RA, I have
to assume these will be absent on the link; otherwise, the node would
not be using DHCPv6 to obtain an address.  Furthermore, the DoD Base
Requirements for an IPv6 Capable Node also does not assume this to be
the case:

"All IPv6 Nodes MUST support at least one autonomous method for
discovering its own unique IPv6 interface address(es), either RFC 2462,
IPv6 Stateless Address Auto-configuration (SLAAC) or the client side of
RFC 3315, DHCPv6.  DHCPv6 provides for a stateful equivalent to SLAAC.
The two methods are complementary but not mutually exclusive."

>> (There is of course the consideration that at this time, very few =20
IPv6 implementations can configure an address through DHCPv6.)

Is this because of some shortcoming(s) in the specification or do
network managers find DHCPv6 unnecessary?  If they are not using DHCPv6,
how do they distribute DNS servers and other configuration information?
I am interested in learning how well received DHCPv6 has been.  We have
been slow to implement it in our OS because of low demand.

>> Strange that a subnet size isn't included with the DHCPv6 address =20
assignment. I guess this means either configuring a /128 and rely on =20
router redirects to learn about directly attached neighbors, or use =20
RFC 3513 as your guideline and make it /64:

Thank you for this advice.  I would like to request to the working group
that a new option be introduced to DHCPv6 that specifies a prefix length
either for an IA_NA or just a single IA_ADDR.  In the meantime, I will
take your advice.

Best Regards,
Tammy





-----Original Message-----
From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
Sent: Friday, August 10, 2007 6:52 PM
To: Leino, Tammy
Cc: John Jason Brzozowski (JJMB); Hemant Singh (shemant); ipv6@ietf.org
Subject: Re: prefix length determination for DHCPv6


On 11-aug-2007, at 0:28, Leino, Tammy wrote:

> Has your working group considered adding this as a DHCPv6 option?  =20
> If the on-link router is not configured to transmit RAs, a DHCPv6 =20
> option advertising the default gateway would be helpful in =20
> populating the routing table.

The problem with that would be that you either have to wait for some =20
time to be sure that there are no RAs, or you need to initiate DHCPv6 =20
always immediately. The former leads to delays for the user, the =20
latter to additional network chatter which would be unnecessary in =20
most situations. Worse, the extra chatter is multicast, I'm again =20
stressing that multicasts take up inordinate amounts of bandwidth on =20
wifi networks.

So I don't think we should present NOT having RAs as a valid =20
configuration option. This way, we get to avoid the situations above. =20
If people want to configure hosts using DHCPv6 they should have =20
routers send out RAs with the M bit set and with no prefix information.

Note that currently, it's not possible to distribute default gateway =20
information through DHCPv6, so RAs would also have to be used for that.

(There is of course the consideration that at this time, very few =20
IPv6 implementations can configure an address through DHCPv6.)

Strange that a subnet size isn't included with the DHCPv6 address =20
assignment. I guess this means either configuring a /128 and rely on =20
router redirects to learn about directly attached neighbors, or use =20
RFC 3513 as your guideline and make it /64:

    For all unicast addresses, except those that start with binary value
    000, Interface IDs are required to be 64 bits long and to be
    constructed in Modified EUI-64 format.

By the way, I would very much like to know who came up with that =20
requirement and why.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

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



From dhcwg-bounces@ietf.org Fri Aug 10 19:25:32 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJdpb-0003PP-0z; Fri, 10 Aug 2007 19:23:47 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJdpZ-0003PH-Ep
	for dhcwg@ietf.org; Fri, 10 Aug 2007 19:23:45 -0400
Received: from relay1.mentorg.com ([192.94.38.131])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IJdpY-0000Wg-VK
	for dhcwg@ietf.org; Fri, 10 Aug 2007 19:23:45 -0400
Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58])
	by relay1.mentorg.com with esmtp 
	id 1IJdpX-0003kr-OE from tammy_leino@mentor.com ;
	Fri, 10 Aug 2007 16:23:43 -0700
Received: from SVR-ALH-EXC-02.mgc.mentorg.com ([134.86.110.227]) by
	SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 10 Aug 2007 16:23:43 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] prefix length determination for DHCPv6
Date: Fri, 10 Aug 2007 18:23:41 -0500
Message-ID: <7ECEF9368E169544B43882BC98EB5D92032DA83C@SVR-ALH-EXC-02.mgc.mentorg.com>
In-Reply-To: <7t53ayruh4v.fsf@gpk-xdm-001.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] prefix length determination for DHCPv6
Thread-Index: Acfboq8LyxxqqnplTQe4aSbYu2nPaQAAOwhQ
From: "Leino, Tammy" <tammy_leino@mentor.com>
To: "Ole Troan" <ot@cisco.com>
X-OriginalArrivalTime: 10 Aug 2007 23:23:43.0517 (UTC)
	FILETIME=[7E1B8CD0:01C7DBA5]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc: dhcwg@ietf.org, "John Jason Brzozowski \(JJMB\)" <jjmb@jjmb.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

Thank you for your comments.

If I don't get a prefix length for an assigned address, I will not have
a network route for that prefix in my routing table.  When I send data
to an on-link node, all the data will go through the default router.
This will promote redirect messages for on-link destinations.  This will
get my packet to the destination in the end, but in a very ungraceful
way.  My routing table will become overpopulated with host routes that
could all have been covered by one network route if the DHCPv6 server
would tell me my prefix length.  Yes, the user should be sending data to
on-link nodes using the node's link-local address in most cases, but who
can tell what a user is going to do?

There is nothing wrong with router discovery.  I think it's a great
innovation, but my point is that there might not be a router configured
on link to sends RAs.  There might be a router on link to forward IPv6
packets, but the network implementer may be using DHCPv6 in lieu of RAs.

Best Regards,
Tammy



-----Original Message-----
From: Ole Troan [mailto:ot@cisco.com]
Sent: Friday, August 10, 2007 7:03 PM
To: Leino, Tammy
Cc: John Jason Brzozowski (JJMB); dhcwg@ietf.org
Subject: Re: [dhcwg] prefix length determination for DHCPv6


> Thank you very much for the information John.
>
>>>RAs could be configured to supply the length for prefixes valid on
the link
>>> Otherwise, there is no DHCPv6 option that can be used to supply this
data.
>
> What if the router is configured just to inform the node to use DHCPv6
> to obtain an address and does not specify any prefix options in the
> RA?  The only place I see to specify a prefix length in an RA is in a
> prefix option.  Is there some other way an RA could relay a prefix
> length to a node?  If not, how does the client know the prefix length
> of the address the DHCP server is assigning?  It seems to me that the
> DHCPv6 server should be sending a prefix length with the address it
> assigns.  Is there a reason this was not included in the
> specification?

an address does not have a prefix length. a host needs to know the
on-link prefix for on-link determination. that's done with ND.

>>>Regarding, your second question why would you need information about
the
>>> router if it does not exist or is not configured to route?  Just
looking
>>> for a little more information.
>
> In implementing this RFC, I am not making assumptions that there will
> be an IPv6-configured router on link.  This does not mean there is not
> a router on link that can forward IPv6 messages, it just means there
> might not be a router on link that sends RAs.  Just because a node can
> forward IPv6 traffic does not mean it will necessarily be configured
> to send RAs.

then your only option is manual configuration. which doesn't seem
optimal. what's wrong with RFC2461 router discovery?

/ot

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



From dhcwg-bounces@ietf.org Fri Aug 10 19:30:17 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJduD-0007dQ-Cw; Fri, 10 Aug 2007 19:28:33 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJduA-0007c3-Ky; Fri, 10 Aug 2007 19:28:30 -0400
Received: from relay1.mentorg.com ([192.94.38.131])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IJdu9-0000dk-Oc; Fri, 10 Aug 2007 19:28:30 -0400
Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58])
	by relay1.mentorg.com with esmtp 
	id 1IJdu9-0003zk-8m from tammy_leino@mentor.com ;
	Fri, 10 Aug 2007 16:28:29 -0700
Received: from SVR-ALH-EXC-02.mgc.mentorg.com ([134.86.110.227]) by
	SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 10 Aug 2007 16:28:28 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 10 Aug 2007 18:28:27 -0500
Message-ID: <7ECEF9368E169544B43882BC98EB5D92032DA83D@SVR-ALH-EXC-02.mgc.mentorg.com>
In-Reply-To: <8E296595B6471A4689555D5D725EBB2104B6693D@xmb-rtp-20a.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: prefix length determination for DHCPv6
Thread-Index: AcfboUHk1kkPl/zjSFmlUg6ok1IdnwAAPQ+wAAB9QeAAAFvVoA==
From: "Leino, Tammy" <tammy_leino@mentor.com>
To: "Bernie Volz (volz)" <volz@cisco.com>,
	"Iljitsch van Beijnum" <iljitsch@muada.com>
X-OriginalArrivalTime: 10 Aug 2007 23:28:28.0980 (UTC)
	FILETIME=[2841BF40:01C7DBA6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 827a2a57ca7ab0837847220f447e8d56
Cc: dhcwg@ietf.org, ipv6@ietf.org,
	"John Jason Brzozowski \(JJMB\)" <jjmb@jjmb.com>
Subject: [dhcwg] RE: prefix length determination 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

Thank you Bernie.

In my example case, there is a forwarding router on link, but the router
is not configured to send RAs.  The DoD seems to think a network can use
(DHCPv6 || RAs) || (DHCPv6 && RAs).

"All IPv6 Nodes MUST support at least one autonomous method for
discovering its own unique IPv6 interface address(es), either RFC 2462,
IPv6 Stateless Address Auto-configuration (SLAAC) or the client side of
RFC 3315, DHCPv6.  DHCPv6 provides for a stateful equivalent to SLAAC.
The two methods are complementary but not mutually exclusive."

>>Having two ways (DHCPv6 and RA) provide this information is just
asking
for a lot of trouble. What if they conflict each other? Who wins?

The RA should be received before DHCPv6 is even invoked.  The node
should not invoke DHCPv6 unless the RA tells the node to do so, the user
tells the node not to use the RA, or there are no RAs on link.

If there is DHCPv6 but no RA, who tells me my prefix length?

Best Regards,
Tammy



-----Original Message-----
From: Bernie Volz (volz) [mailto:volz@cisco.com]
Sent: Friday, August 10, 2007 7:20 PM
To: Leino, Tammy; Iljitsch van Beijnum
Cc: ipv6@ietf.org; John Jason Brzozowski (JJMB); dhcwg@ietf.org
Subject: RE: prefix length determination for DHCPv6


The PIOs in an RA tells a node whether it can autoconfigure or not via
the A bit. If the A bit is not set, the node can not use SLAAC. But, it
CAN use the PIO information to build the table of what prefixes exist
and which are on-link.

That is why there is no need for DHCPv6 to provide default router and
prefix information because the RA does that.

Having two ways (DHCPv6 and RA) provide this information is just asking
for a lot of trouble. What if they conflict each other? Who wins?

And, if there are no routers, there's no need for anything but
link-local addresses (since you can't get off the local link).

It is far better to have the device that is providing the service (ie,
the router which is providing routing services) provide this type of
information.

- Bernie

-----Original Message-----
From: Leino, Tammy [mailto:tammy_leino@mentor.com]=20
Sent: Friday, August 10, 2007 7:10 PM
To: Iljitsch van Beijnum
Cc: ipv6@ietf.org; John Jason Brzozowski (JJMB)
Subject: RE: prefix length determination for DHCPv6

Thank you very much for your comments.

Regarding your comment:

>> So I don't think we should present NOT having RAs as a valid =20
configuration option. This way, we get to avoid the situations above. =20
If people want to configure hosts using DHCPv6 they should have =20
routers send out RAs with the M bit set and with no prefix information.

The reason I am not assuming there is a router on link configured to
send RAs with prefix options is because I don't see the point of DHCPv6
configuring addresses if a router is configured to do the same job.
Since the prefix length is carried in a prefix option of an RA, I have
to assume these will be absent on the link; otherwise, the node would
not be using DHCPv6 to obtain an address.  Furthermore, the DoD Base
Requirements for an IPv6 Capable Node also does not assume this to be
the case:

"All IPv6 Nodes MUST support at least one autonomous method for
discovering its own unique IPv6 interface address(es), either RFC 2462,
IPv6 Stateless Address Auto-configuration (SLAAC) or the client side of
RFC 3315, DHCPv6.  DHCPv6 provides for a stateful equivalent to SLAAC.
The two methods are complementary but not mutually exclusive."

>> (There is of course the consideration that at this time, very few =20
IPv6 implementations can configure an address through DHCPv6.)

Is this because of some shortcoming(s) in the specification or do
network managers find DHCPv6 unnecessary?  If they are not using DHCPv6,
how do they distribute DNS servers and other configuration information?
I am interested in learning how well received DHCPv6 has been.  We have
been slow to implement it in our OS because of low demand.

>> Strange that a subnet size isn't included with the DHCPv6 address =20
assignment. I guess this means either configuring a /128 and rely on =20
router redirects to learn about directly attached neighbors, or use =20
RFC 3513 as your guideline and make it /64:

Thank you for this advice.  I would like to request to the working group
that a new option be introduced to DHCPv6 that specifies a prefix length
either for an IA_NA or just a single IA_ADDR.  In the meantime, I will
take your advice.

Best Regards,
Tammy





-----Original Message-----
From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
Sent: Friday, August 10, 2007 6:52 PM
To: Leino, Tammy
Cc: John Jason Brzozowski (JJMB); Hemant Singh (shemant); ipv6@ietf.org
Subject: Re: prefix length determination for DHCPv6


On 11-aug-2007, at 0:28, Leino, Tammy wrote:

> Has your working group considered adding this as a DHCPv6 option?  =20
> If the on-link router is not configured to transmit RAs, a DHCPv6 =20
> option advertising the default gateway would be helpful in =20
> populating the routing table.

The problem with that would be that you either have to wait for some =20
time to be sure that there are no RAs, or you need to initiate DHCPv6 =20
always immediately. The former leads to delays for the user, the =20
latter to additional network chatter which would be unnecessary in =20
most situations. Worse, the extra chatter is multicast, I'm again =20
stressing that multicasts take up inordinate amounts of bandwidth on =20
wifi networks.

So I don't think we should present NOT having RAs as a valid =20
configuration option. This way, we get to avoid the situations above. =20
If people want to configure hosts using DHCPv6 they should have =20
routers send out RAs with the M bit set and with no prefix information.

Note that currently, it's not possible to distribute default gateway =20
information through DHCPv6, so RAs would also have to be used for that.

(There is of course the consideration that at this time, very few =20
IPv6 implementations can configure an address through DHCPv6.)

Strange that a subnet size isn't included with the DHCPv6 address =20
assignment. I guess this means either configuring a /128 and rely on =20
router redirects to learn about directly attached neighbors, or use =20
RFC 3513 as your guideline and make it /64:

    For all unicast addresses, except those that start with binary value
    000, Interface IDs are required to be 64 bits long and to be
    constructed in Modified EUI-64 format.

By the way, I would very much like to know who came up with that =20
requirement and why.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

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



From dhcwg-bounces@ietf.org Fri Aug 10 19:30:31 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJduZ-0007qG-T3; Fri, 10 Aug 2007 19:28:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJduY-0007pC-K7
	for dhcwg@ietf.org; Fri, 10 Aug 2007 19:28:54 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IJduY-0001m5-1o
	for dhcwg@ietf.org; Fri, 10 Aug 2007 19:28:54 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 0D0005A6E5; Fri, 10 Aug 2007 16:28:53 -0700 (PDT)
Date: Fri, 10 Aug 2007 16:28:52 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: "Leino, Tammy" <tammy_leino@mentor.com>
Subject: Re: [dhcwg] prefix length determination for DHCPv6
Message-ID: <20070810232852.GG31592@isc.org>
References: <SVR-ORW-EXC-10F7AQ40007413f@SVR-ORW-EXC-10.mgc.mentorg.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA836@SVR-ALH-EXC-02.mgc.mentorg.com>
Mime-Version: 1.0
In-Reply-To: <7ECEF9368E169544B43882BC98EB5D92032DA836@SVR-ALH-EXC-02.mgc.mentorg.com>
User-Agent: Mutt/1.5.9i
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>
Content-Type: multipart/mixed; boundary="===============1358644738=="
Errors-To: dhcwg-bounces@ietf.org


--===============1358644738==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="g7w8+K/95kPelPD2"
Content-Disposition: inline


--g7w8+K/95kPelPD2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Aug 10, 2007 at 05:26:25PM -0500, Leino, Tammy wrote:
> What if the router is configured just to inform the node to use DHCPv6 to=
 obtain an address and does not specify any prefix options in the RA?

I think the expected behaviour is that the client would pass all
traffic to the RA.  That is, the clients all configure /128's, and
rather than talking to each other, talk to the router.  It would
have no subnets in its table, and so would not be able to speek to
neighbors except through the router(s).

This store and forward star topology may be desirable for example in
radio frequency networks, where you don't want to take on full ROSPF
or similar functions in clients but inter-client traffic is
unreliable.  The router would necessarily be positioned where all
clients could reliably communicate with it.

> Is there a reason this was not included in the specification?

The reason at the time I think was that IPv6 speakers were told to
assume 'on link by default' in the absence of a router
advertisement...so in the absence of a router you could still all
speak to each other without knowing the relevant prefix(es).  This
was found to have some flaws, and is currently not implemented by
most IPv6 stacks.

Anyway, since this has changed, it may be time to revisit this design.

I think more or less at IETF 69 we heard consensus that there should
be a prefix length option.  We didn't agree on the default router, in
which I think I was the only one who supported the idea?


> Just because a node can forward IPv6 traffic does not mean it will necess=
arily be configured to send RAs.

Why do you think this is the case?


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

--g7w8+K/95kPelPD2
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFGvPS0cXeLeWu2vmoRAhOrAKC2PiBJyYLrGgfTGH4nmi9M3wLRCgCfYyrG
IuCPrbOsWLGrdl8OIgYGFWw=
=f9x1
-----END PGP SIGNATURE-----

--g7w8+K/95kPelPD2--


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

--===============1358644738==--




From dhcwg-bounces@ietf.org Fri Aug 10 19:41:09 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJe4g-0001Or-7K; Fri, 10 Aug 2007 19:39:22 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJe4d-0001E7-43; Fri, 10 Aug 2007 19:39:19 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IJe4c-0000u1-2a; Fri, 10 Aug 2007 19:39:19 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 10 Aug 2007 16:39:17 -0700
X-IronPort-AV: i="4.19,246,1183359600"; 
	d="scan'208"; a="198177004:sNHT114775632"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7ANdHQ8029869; 
	Fri, 10 Aug 2007 16:39:17 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7ANdGF6003165;
	Fri, 10 Aug 2007 23:39:17 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 10 Aug 2007 19:39:16 -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, 10 Aug 2007 19:39:16 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <7ECEF9368E169544B43882BC98EB5D92032DA83D@SVR-ALH-EXC-02.mgc.mentorg.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: prefix length determination for DHCPv6
Thread-Index: AcfboUHk1kkPl/zjSFmlUg6ok1IdnwAAPQ+wAAB9QeAAAFvVoAAAPsuA
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "Leino, Tammy" <tammy_leino@mentor.com>,
	"Iljitsch van Beijnum" <iljitsch@muada.com>
X-OriginalArrivalTime: 10 Aug 2007 23:39:16.0359 (UTC)
	FILETIME=[AA1FF170:01C7DBA7]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=8554; t=1186789157;
	x=1187653157; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=volz@cisco.com;
	z=From:=20=22Bernie=20Volz=20\(volz\)=22=20<volz@cisco.com>
	|Subject:=20RE=3A=20prefix=20length=20determination=20for=20DHCPv6
	|Sender:=20; bh=lN1yOypIwXfg9urDYN9YnTSaUkygXDnfhf3BpoiU/u4=;
	b=mXhU3GpLGJHzTwerA0QzRN88C8Ih4cp4Fk86IM1rAyzA5SRqI04XXLkQIwDR+oqMsCdKsYg5
	6/k7nSqe1MI3aCrrEpDskCV9cJ6mf6ja+RY4HfrcDUhTUBH79yhoeZMLLqbCdzQeVOoeojo9ol
	gPXoh9eijlMpZBHteeu1g6j/U=;
Authentication-Results: sj-dkim-1; header.From=volz@cisco.com; dkim=pass (si
	g from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a8041eca2a724d631b098c15e9048ce9
Cc: dhcwg@ietf.org, ipv6@ietf.org,
	"John Jason Brzozowski \(JJMB\)" <jjmb@jjmb.com>
Subject: [dhcwg] RE: prefix length determination 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

If this is true, the DoD is sadly mistaken. But, I think you are not
understanding the statement correctly. The quoted statement says nothing
about RAs - it talks about discovering interface addresses.

Interface addresses are completely SEPARATE from routing information.
Please do NOT confuse the two. This has been a source of confusion for
many IPv6 implementors who know IPv4.

The configuration of addresses for an interface MUST NOT be tied to the
configuration of prefix information for routing. Just because a prefix
is on a link, does not mean the interface necessarily has an address for
that prefix (it may have none, 1, or many). Just because an interface
has an address, does not mean that the system has any prefix information
for a prefix that "contains" that address. Prefix information and
addresses assigned to interfaces are completely separate.

And, a node should support both SLACC and DHCPv6 as "The two methods are
complementary but not mutually exclusive."

A full IPv6 node needs:
- RAs for prefix information and default router information.
- SLAAC for auto-generating addresses for prefixes on which the A-bit is
set.
- DHCPv6 if the M and/or O bits are set.

Missing any of these means you can not operate on all IPv6 networks, or
you might have limited service capabilities on some.

- Bernie

-----Original Message-----
From: Leino, Tammy [mailto:tammy_leino@mentor.com]=20
Sent: Friday, August 10, 2007 7:28 PM
To: Bernie Volz (volz); Iljitsch van Beijnum
Cc: ipv6@ietf.org; John Jason Brzozowski (JJMB); dhcwg@ietf.org
Subject: RE: prefix length determination for DHCPv6

Thank you Bernie.

In my example case, there is a forwarding router on link, but the router
is not configured to send RAs.  The DoD seems to think a network can use
(DHCPv6 || RAs) || (DHCPv6 && RAs).

"All IPv6 Nodes MUST support at least one autonomous method for
discovering its own unique IPv6 interface address(es), either RFC 2462,
IPv6 Stateless Address Auto-configuration (SLAAC) or the client side of
RFC 3315, DHCPv6.  DHCPv6 provides for a stateful equivalent to SLAAC.
The two methods are complementary but not mutually exclusive."

>>Having two ways (DHCPv6 and RA) provide this information is just
asking
for a lot of trouble. What if they conflict each other? Who wins?

The RA should be received before DHCPv6 is even invoked.  The node
should not invoke DHCPv6 unless the RA tells the node to do so, the user
tells the node not to use the RA, or there are no RAs on link.

If there is DHCPv6 but no RA, who tells me my prefix length?

Best Regards,
Tammy



-----Original Message-----
From: Bernie Volz (volz) [mailto:volz@cisco.com]
Sent: Friday, August 10, 2007 7:20 PM
To: Leino, Tammy; Iljitsch van Beijnum
Cc: ipv6@ietf.org; John Jason Brzozowski (JJMB); dhcwg@ietf.org
Subject: RE: prefix length determination for DHCPv6


The PIOs in an RA tells a node whether it can autoconfigure or not via
the A bit. If the A bit is not set, the node can not use SLAAC. But, it
CAN use the PIO information to build the table of what prefixes exist
and which are on-link.

That is why there is no need for DHCPv6 to provide default router and
prefix information because the RA does that.

Having two ways (DHCPv6 and RA) provide this information is just asking
for a lot of trouble. What if they conflict each other? Who wins?

And, if there are no routers, there's no need for anything but
link-local addresses (since you can't get off the local link).

It is far better to have the device that is providing the service (ie,
the router which is providing routing services) provide this type of
information.

- Bernie

-----Original Message-----
From: Leino, Tammy [mailto:tammy_leino@mentor.com]=20
Sent: Friday, August 10, 2007 7:10 PM
To: Iljitsch van Beijnum
Cc: ipv6@ietf.org; John Jason Brzozowski (JJMB)
Subject: RE: prefix length determination for DHCPv6

Thank you very much for your comments.

Regarding your comment:

>> So I don't think we should present NOT having RAs as a valid =20
configuration option. This way, we get to avoid the situations above. =20
If people want to configure hosts using DHCPv6 they should have =20
routers send out RAs with the M bit set and with no prefix information.

The reason I am not assuming there is a router on link configured to
send RAs with prefix options is because I don't see the point of DHCPv6
configuring addresses if a router is configured to do the same job.
Since the prefix length is carried in a prefix option of an RA, I have
to assume these will be absent on the link; otherwise, the node would
not be using DHCPv6 to obtain an address.  Furthermore, the DoD Base
Requirements for an IPv6 Capable Node also does not assume this to be
the case:

"All IPv6 Nodes MUST support at least one autonomous method for
discovering its own unique IPv6 interface address(es), either RFC 2462,
IPv6 Stateless Address Auto-configuration (SLAAC) or the client side of
RFC 3315, DHCPv6.  DHCPv6 provides for a stateful equivalent to SLAAC.
The two methods are complementary but not mutually exclusive."

>> (There is of course the consideration that at this time, very few =20
IPv6 implementations can configure an address through DHCPv6.)

Is this because of some shortcoming(s) in the specification or do
network managers find DHCPv6 unnecessary?  If they are not using DHCPv6,
how do they distribute DNS servers and other configuration information?
I am interested in learning how well received DHCPv6 has been.  We have
been slow to implement it in our OS because of low demand.

>> Strange that a subnet size isn't included with the DHCPv6 address =20
assignment. I guess this means either configuring a /128 and rely on =20
router redirects to learn about directly attached neighbors, or use =20
RFC 3513 as your guideline and make it /64:

Thank you for this advice.  I would like to request to the working group
that a new option be introduced to DHCPv6 that specifies a prefix length
either for an IA_NA or just a single IA_ADDR.  In the meantime, I will
take your advice.

Best Regards,
Tammy





-----Original Message-----
From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
Sent: Friday, August 10, 2007 6:52 PM
To: Leino, Tammy
Cc: John Jason Brzozowski (JJMB); Hemant Singh (shemant); ipv6@ietf.org
Subject: Re: prefix length determination for DHCPv6


On 11-aug-2007, at 0:28, Leino, Tammy wrote:

> Has your working group considered adding this as a DHCPv6 option?  =20
> If the on-link router is not configured to transmit RAs, a DHCPv6 =20
> option advertising the default gateway would be helpful in =20
> populating the routing table.

The problem with that would be that you either have to wait for some =20
time to be sure that there are no RAs, or you need to initiate DHCPv6 =20
always immediately. The former leads to delays for the user, the =20
latter to additional network chatter which would be unnecessary in =20
most situations. Worse, the extra chatter is multicast, I'm again =20
stressing that multicasts take up inordinate amounts of bandwidth on =20
wifi networks.

So I don't think we should present NOT having RAs as a valid =20
configuration option. This way, we get to avoid the situations above. =20
If people want to configure hosts using DHCPv6 they should have =20
routers send out RAs with the M bit set and with no prefix information.

Note that currently, it's not possible to distribute default gateway =20
information through DHCPv6, so RAs would also have to be used for that.

(There is of course the consideration that at this time, very few =20
IPv6 implementations can configure an address through DHCPv6.)

Strange that a subnet size isn't included with the DHCPv6 address =20
assignment. I guess this means either configuring a /128 and rely on =20
router redirects to learn about directly attached neighbors, or use =20
RFC 3513 as your guideline and make it /64:

    For all unicast addresses, except those that start with binary value
    000, Interface IDs are required to be 64 bits long and to be
    constructed in Modified EUI-64 format.

By the way, I would very much like to know who came up with that =20
requirement and why.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

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



From dhcwg-bounces@ietf.org Fri Aug 10 19:43:35 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJe75-0003aH-7l; Fri, 10 Aug 2007 19:41:51 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJe73-0003a7-5r
	for dhcwg@ietf.org; Fri, 10 Aug 2007 19:41:49 -0400
Received: from relay1.mentorg.com ([192.94.38.131])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IJe72-0000xq-LB
	for dhcwg@ietf.org; Fri, 10 Aug 2007 19:41:49 -0400
Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58])
	by relay1.mentorg.com with esmtp 
	id 1IJe70-0004su-3O from tammy_leino@mentor.com ;
	Fri, 10 Aug 2007 16:41:46 -0700
Received: from SVR-ALH-EXC-02.mgc.mentorg.com ([134.86.110.227]) by
	SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 10 Aug 2007 16:41:45 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] prefix length determination for DHCPv6
Date: Fri, 10 Aug 2007 18:41:44 -0500
Message-ID: <7ECEF9368E169544B43882BC98EB5D92032DA83E@SVR-ALH-EXC-02.mgc.mentorg.com>
In-Reply-To: <20070810232852.GG31592@isc.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] prefix length determination for DHCPv6
Thread-Index: AcfbpjoHfSOfReGrTpCr+SbiGa8orwAADs9w
From: "Leino, Tammy" <tammy_leino@mentor.com>
To: "David W. Hankins" <David_Hankins@isc.org>
X-OriginalArrivalTime: 10 Aug 2007 23:41:45.0856 (UTC)
	FILETIME=[033B6000:01C7DBA8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
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

Thank you for your insightful comments David.  I appreciate you taking
the time to respond to me.

>>I think more or less at IETF 69 we heard consensus that there should
be a prefix length option.  We didn't agree on the default router, in
which I think I was the only one who supported the idea?

I am glad to hear this.  Perhaps you can convince others of the value in
the default router option.

>> Just because a node can forward IPv6 traffic does not mean it will
necessarily be configured to send RAs.
>Why do you think this is the case?

I do not see that the presence of RAs is necessary for an IPv6 network
to function.  Client nodes can obtain the information they need from
DHCPv6.  If DHCPv6 requires RAs, then I don't understand why RAs don't
perform all functionality of DHCPv6.  There is some overlapping
functionality, and then there is functionality that is unique to each
protocol.  Also, I'll fall back on the DoD again and quote their "either
RFC 2462 or RFC 3315" comment.

When I first began implementing the IPv6 protocol for our OS in 2001, I
could not understand why RAs did not contain all configuration
information that DHCPv6 provided.  Six years later, I am still as
perplexed :)  I have been holding off on DHCPv6 hoping you would beef up
RAs, but the time has come and customers need that configuration
information from DHCPv6, but they are also expecting DHCPv6 to assign
IPv6 addresses.

Best Regards,
Tammy




-----Original Message-----
From: David W. Hankins [mailto:David_Hankins@isc.org]
Sent: Friday, August 10, 2007 7:29 PM
To: Leino, Tammy
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] prefix length determination for DHCPv6


On Fri, Aug 10, 2007 at 05:26:25PM -0500, Leino, Tammy wrote:
> What if the router is configured just to inform the node to use DHCPv6
to obtain an address and does not specify any prefix options in the RA?

I think the expected behaviour is that the client would pass all
traffic to the RA.  That is, the clients all configure /128's, and
rather than talking to each other, talk to the router.  It would
have no subnets in its table, and so would not be able to speek to
neighbors except through the router(s).

This store and forward star topology may be desirable for example in
radio frequency networks, where you don't want to take on full ROSPF
or similar functions in clients but inter-client traffic is
unreliable.  The router would necessarily be positioned where all
clients could reliably communicate with it.

> Is there a reason this was not included in the specification?

The reason at the time I think was that IPv6 speakers were told to
assume 'on link by default' in the absence of a router
advertisement...so in the absence of a router you could still all
speak to each other without knowing the relevant prefix(es).  This
was found to have some flaws, and is currently not implemented by
most IPv6 stacks.

Anyway, since this has changed, it may be time to revisit this design.

I think more or less at IETF 69 we heard consensus that there should
be a prefix length option.  We didn't agree on the default router, in
which I think I was the only one who supported the idea?


> Just because a node can forward IPv6 traffic does not mean it will
necessarily be configured to send RAs.

Why do you think this is the case?


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

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



From dhcwg-bounces@ietf.org Fri Aug 10 19:57:10 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJeKC-0007S0-Sn; Fri, 10 Aug 2007 19:55:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJeKA-0007Qr-Cx; Fri, 10 Aug 2007 19:55:22 -0400
Received: from relay1.mentorg.com ([192.94.38.131])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IJeK9-0002AU-1i; Fri, 10 Aug 2007 19:55:22 -0400
Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58])
	by relay1.mentorg.com with esmtp 
	id 1IJeK8-0005dj-L7 from tammy_leino@mentor.com ;
	Fri, 10 Aug 2007 16:55:20 -0700
Received: from SVR-ALH-EXC-02.mgc.mentorg.com ([134.86.110.227]) by
	SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 10 Aug 2007 16:55:20 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 10 Aug 2007 18:55:18 -0500
Message-ID: <7ECEF9368E169544B43882BC98EB5D92032DA840@SVR-ALH-EXC-02.mgc.mentorg.com>
In-Reply-To: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: prefix length determination for DHCPv6
Thread-Index: AcfboUHk1kkPl/zjSFmlUg6ok1IdnwAAPQ+wAAB9QeAAAFvVoAAAPsuAAACGOpA=
From: "Leino, Tammy" <tammy_leino@mentor.com>
To: "Bernie Volz (volz)" <volz@cisco.com>,
	"Iljitsch van Beijnum" <iljitsch@muada.com>
X-OriginalArrivalTime: 10 Aug 2007 23:55:20.0356 (UTC)
	FILETIME=[E8B63640:01C7DBA9]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7698d1420ecbbce1995432e99bb6d1a1
Cc: dhcwg@ietf.org, ipv6@ietf.org,
	"John Jason Brzozowski \(JJMB\)" <jjmb@jjmb.com>
Subject: [dhcwg] RE: prefix length determination 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

Thank you Bernie.  I appreciate your advice.

When I add an address in my OS, I add a network route according to the
prefix length of the address so I know that other nodes with this same
prefix are on-link.  I don't route based on a source address.  I find a
route for a destination from the routing table based on the destination
address.  If I added a network route for my prefix, and this destination
matches that prefix, then I find that network route.  Otherwise, I find
the default route and use it.  If I receive a redirect, I will create a
host route for that destination.  If I had been able to add a network
route, I never would have received that redirect and would be saving
memory by not adding the host route.  Can you tell I work on embedded
systems?  I am very stingy with memory!

I will not have a route for a prefix if I do not have an address
assigned to a local interface containing based on that prefix.  If an
address associated with a prefix is deleted, so is the route.

I appreciate everyone's comments and advice.  I am glad to see such
passion for IPv6 and support of people in need.

I just want to voice my opinion that I feel a DHCPv6 prefix length
option and default router option would be useful.

Best Regards,
Tammy


-----Original Message-----
From: Bernie Volz (volz) [mailto:volz@cisco.com]
Sent: Friday, August 10, 2007 7:39 PM
To: Leino, Tammy; Iljitsch van Beijnum
Cc: ipv6@ietf.org; John Jason Brzozowski (JJMB); dhcwg@ietf.org
Subject: RE: prefix length determination for DHCPv6


If this is true, the DoD is sadly mistaken. But, I think you are not
understanding the statement correctly. The quoted statement says nothing
about RAs - it talks about discovering interface addresses.

Interface addresses are completely SEPARATE from routing information.
Please do NOT confuse the two. This has been a source of confusion for
many IPv6 implementors who know IPv4.

The configuration of addresses for an interface MUST NOT be tied to the
configuration of prefix information for routing. Just because a prefix
is on a link, does not mean the interface necessarily has an address for
that prefix (it may have none, 1, or many). Just because an interface
has an address, does not mean that the system has any prefix information
for a prefix that "contains" that address. Prefix information and
addresses assigned to interfaces are completely separate.

And, a node should support both SLACC and DHCPv6 as "The two methods are
complementary but not mutually exclusive."

A full IPv6 node needs:
- RAs for prefix information and default router information.
- SLAAC for auto-generating addresses for prefixes on which the A-bit is
set.
- DHCPv6 if the M and/or O bits are set.

Missing any of these means you can not operate on all IPv6 networks, or
you might have limited service capabilities on some.

- Bernie

-----Original Message-----
From: Leino, Tammy [mailto:tammy_leino@mentor.com]=20
Sent: Friday, August 10, 2007 7:28 PM
To: Bernie Volz (volz); Iljitsch van Beijnum
Cc: ipv6@ietf.org; John Jason Brzozowski (JJMB); dhcwg@ietf.org
Subject: RE: prefix length determination for DHCPv6

Thank you Bernie.

In my example case, there is a forwarding router on link, but the router
is not configured to send RAs.  The DoD seems to think a network can use
(DHCPv6 || RAs) || (DHCPv6 && RAs).

"All IPv6 Nodes MUST support at least one autonomous method for
discovering its own unique IPv6 interface address(es), either RFC 2462,
IPv6 Stateless Address Auto-configuration (SLAAC) or the client side of
RFC 3315, DHCPv6.  DHCPv6 provides for a stateful equivalent to SLAAC.
The two methods are complementary but not mutually exclusive."

>>Having two ways (DHCPv6 and RA) provide this information is just
asking
for a lot of trouble. What if they conflict each other? Who wins?

The RA should be received before DHCPv6 is even invoked.  The node
should not invoke DHCPv6 unless the RA tells the node to do so, the user
tells the node not to use the RA, or there are no RAs on link.

If there is DHCPv6 but no RA, who tells me my prefix length?

Best Regards,
Tammy



-----Original Message-----
From: Bernie Volz (volz) [mailto:volz@cisco.com]
Sent: Friday, August 10, 2007 7:20 PM
To: Leino, Tammy; Iljitsch van Beijnum
Cc: ipv6@ietf.org; John Jason Brzozowski (JJMB); dhcwg@ietf.org
Subject: RE: prefix length determination for DHCPv6


The PIOs in an RA tells a node whether it can autoconfigure or not via
the A bit. If the A bit is not set, the node can not use SLAAC. But, it
CAN use the PIO information to build the table of what prefixes exist
and which are on-link.

That is why there is no need for DHCPv6 to provide default router and
prefix information because the RA does that.

Having two ways (DHCPv6 and RA) provide this information is just asking
for a lot of trouble. What if they conflict each other? Who wins?

And, if there are no routers, there's no need for anything but
link-local addresses (since you can't get off the local link).

It is far better to have the device that is providing the service (ie,
the router which is providing routing services) provide this type of
information.

- Bernie

-----Original Message-----
From: Leino, Tammy [mailto:tammy_leino@mentor.com]=20
Sent: Friday, August 10, 2007 7:10 PM
To: Iljitsch van Beijnum
Cc: ipv6@ietf.org; John Jason Brzozowski (JJMB)
Subject: RE: prefix length determination for DHCPv6

Thank you very much for your comments.

Regarding your comment:

>> So I don't think we should present NOT having RAs as a valid =20
configuration option. This way, we get to avoid the situations above. =20
If people want to configure hosts using DHCPv6 they should have =20
routers send out RAs with the M bit set and with no prefix information.

The reason I am not assuming there is a router on link configured to
send RAs with prefix options is because I don't see the point of DHCPv6
configuring addresses if a router is configured to do the same job.
Since the prefix length is carried in a prefix option of an RA, I have
to assume these will be absent on the link; otherwise, the node would
not be using DHCPv6 to obtain an address.  Furthermore, the DoD Base
Requirements for an IPv6 Capable Node also does not assume this to be
the case:

"All IPv6 Nodes MUST support at least one autonomous method for
discovering its own unique IPv6 interface address(es), either RFC 2462,
IPv6 Stateless Address Auto-configuration (SLAAC) or the client side of
RFC 3315, DHCPv6.  DHCPv6 provides for a stateful equivalent to SLAAC.
The two methods are complementary but not mutually exclusive."

>> (There is of course the consideration that at this time, very few =20
IPv6 implementations can configure an address through DHCPv6.)

Is this because of some shortcoming(s) in the specification or do
network managers find DHCPv6 unnecessary?  If they are not using DHCPv6,
how do they distribute DNS servers and other configuration information?
I am interested in learning how well received DHCPv6 has been.  We have
been slow to implement it in our OS because of low demand.

>> Strange that a subnet size isn't included with the DHCPv6 address =20
assignment. I guess this means either configuring a /128 and rely on =20
router redirects to learn about directly attached neighbors, or use =20
RFC 3513 as your guideline and make it /64:

Thank you for this advice.  I would like to request to the working group
that a new option be introduced to DHCPv6 that specifies a prefix length
either for an IA_NA or just a single IA_ADDR.  In the meantime, I will
take your advice.

Best Regards,
Tammy





-----Original Message-----
From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
Sent: Friday, August 10, 2007 6:52 PM
To: Leino, Tammy
Cc: John Jason Brzozowski (JJMB); Hemant Singh (shemant); ipv6@ietf.org
Subject: Re: prefix length determination for DHCPv6


On 11-aug-2007, at 0:28, Leino, Tammy wrote:

> Has your working group considered adding this as a DHCPv6 option?  =20
> If the on-link router is not configured to transmit RAs, a DHCPv6 =20
> option advertising the default gateway would be helpful in =20
> populating the routing table.

The problem with that would be that you either have to wait for some =20
time to be sure that there are no RAs, or you need to initiate DHCPv6 =20
always immediately. The former leads to delays for the user, the =20
latter to additional network chatter which would be unnecessary in =20
most situations. Worse, the extra chatter is multicast, I'm again =20
stressing that multicasts take up inordinate amounts of bandwidth on =20
wifi networks.

So I don't think we should present NOT having RAs as a valid =20
configuration option. This way, we get to avoid the situations above. =20
If people want to configure hosts using DHCPv6 they should have =20
routers send out RAs with the M bit set and with no prefix information.

Note that currently, it's not possible to distribute default gateway =20
information through DHCPv6, so RAs would also have to be used for that.

(There is of course the consideration that at this time, very few =20
IPv6 implementations can configure an address through DHCPv6.)

Strange that a subnet size isn't included with the DHCPv6 address =20
assignment. I guess this means either configuring a /128 and rely on =20
router redirects to learn about directly attached neighbors, or use =20
RFC 3513 as your guideline and make it /64:

    For all unicast addresses, except those that start with binary value
    000, Interface IDs are required to be 64 bits long and to be
    constructed in Modified EUI-64 format.

By the way, I would very much like to know who came up with that =20
requirement and why.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

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



From dhcwg-bounces@ietf.org Sat Aug 11 04:53:24 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJmgy-0001B4-Jr; Sat, 11 Aug 2007 04:51:28 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJmgx-0001Aw-1a; Sat, 11 Aug 2007 04:51:27 -0400
Received: from mail1.asahi-net.or.jp ([202.224.39.197]
	helo=mail.asahi-net.or.jp)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IJmgw-0001nr-5m; Sat, 11 Aug 2007 04:51:26 -0400
Received: from mon.jinmei.org (attsi1-src.asahi-net.or.jp [220.157.253.2])
	by mail.asahi-net.or.jp (Postfix) with ESMTP
	id B0EB24FC35; Sat, 11 Aug 2007 17:51:22 +0900 (JST)
Received: from mymb.local (unknown [10.0.0.248])
	by mon.jinmei.org (Postfix) with ESMTP id A529033C37;
	Sat, 11 Aug 2007 17:51:22 +0900 (JST)
Date: Sat, 11 Aug 2007 17:51:09 +0900
Message-ID: <m2zm0ywj2a.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: "Leino, Tammy" <tammy_leino@mentor.com>
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
In-Reply-To: <7ECEF9368E169544B43882BC98EB5D92032DA840@SVR-ALH-EXC-02.mgc.mentorg.com>
References: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA840@SVR-ALH-EXC-02.mgc.mentorg.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.0 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: dhcwg@ietf.org, Iljitsch van Beijnum <iljitsch@muada.com>, ipv6@ietf.org,
	"Bernie Volz \(volz\)" <volz@cisco.com>,
	"John Jason Brzozowski \(JJMB\)" <jjmb@jjmb.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

At Fri, 10 Aug 2007 18:55:18 -0500,
"Leino, Tammy" <tammy_leino@mentor.com> wrote:

> When I add an address in my OS, I add a network route according to the
> prefix length of the address so I know that other nodes with this same
> prefix are on-link.  I don't route based on a source address.  I find a
> route for a destination from the routing table based on the destination
> address.  If I added a network route for my prefix, and this destination
> matches that prefix, then I find that network route.  Otherwise, I find
> the default route and use it.  If I receive a redirect, I will create a
> host route for that destination.  If I had been able to add a network
> route, I never would have received that redirect and would be saving
> memory by not adding the host route.  Can you tell I work on embedded
> systems?  I am very stingy with memory!
> 
> I will not have a route for a prefix if I do not have an address
> assigned to a local interface containing based on that prefix.  If an
> address associated with a prefix is deleted, so is the route.
> 
> I appreciate everyone's comments and advice.  I am glad to see such
> passion for IPv6 and support of people in need.

You still seem to be confused about the notion of separation between
address configuration and on-link prefix configuration that Bernie
already explained pretty well.  It should also be remarked that prefix
information provided by RA does not always mean address configuration
(which, again, Bernie already explained).  If one understood these
points, we could easily understand the following quote of the DoD
requirement doesn't actually indicate the need for on-link prefix
information given by DHCPv6:

  "All IPv6 Nodes MUST support at least one autonomous method for
  discovering its own unique IPv6 interface address(es), either RFC
  2462, IPv6 Stateless Address Auto-configuration (SLAAC) or the
  client side of RFC 3315, DHCPv6.  DHCPv6 provides for a stateful
  equivalent to SLAAC.  The two methods are complementary but not
  mutually exclusive."

That is, it only talks about address configuration but doesn't say
anything about on-link prefix information.

Overall, we should first share the base understanding of the protocol
design before discussing anything new.

Assuming we share the base, points to be discussed are:

- whether we need a way to provide on-link prefix information via
  DHCPv6 even if RA already has this provision.  I don't see strong
  need for this; however, as David mentioned there is a minor void due
  to the deprecation of the "on-link by default" rule, and I agree it
  at least warrants discussion on the need for this new option.  But
  even if we introduce the new option I believe it should only cover
  very rare cases and host implementation should not assume this
  information is always provided via DHCPv6.

- whether we need a way to provide default router addresses via DHCPv6
  even if RA already has this provision.  I personally don't see any
  need for this unlike the case of on-link prefix information.  For
  that matter, simply saying "there may be a case where there is a
  node that forward packets but don't send out RAs" isn't convincing
  enough to me (and I'm afraid not to many others).  A reasonable
  background should also be provided that explains why we ever need
  such a seemingly unrealistic scenario.  Again, just saying some
  authority like DoD is requiring something isn't convincing to me
  ,and I'm afraid not to many others; besides, as explained above the
  DoD statement talking about address configuration methods doesn't
  justify the need for this new option in the first place.

In any event, I hear that some DHCPv6 guys are planning to make a new
draft that covers this topic.  So I think it's better to hold off for
now and wait for the document, rather than continue this thread
with keeping possible misunderstanding or confusing about the base
protocol principles.

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

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



From dhcwg-bounces@ietf.org Sat Aug 11 08:29:08 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJq3s-0004ip-N7; Sat, 11 Aug 2007 08:27:20 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJq3r-0004hv-PA
	for dhcwg@ietf.org; Sat, 11 Aug 2007 08:27:19 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IJq3r-00066n-2u
	for dhcwg@ietf.org; Sat, 11 Aug 2007 08:27:19 -0400
Received: (qmail 69461 invoked from network); 11 Aug 2007 12:30:45 -0000
Received: from softbank219178199025.bbtec.net (HELO
	necom830.hpcl.titech.ac.jp) (219.178.199.25)
	by necom830.hpcl.titech.ac.jp with SMTP; 11 Aug 2007 12:30:45 -0000
Message-ID: <46BDAB04.10400@necom830.hpcl.titech.ac.jp>
Date: Sat, 11 Aug 2007 21:26:44 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en
MIME-Version: 1.0
To: "Leino, Tammy" <tammy_leino@mentor.com>
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
References: <7ECEF9368E169544B43882BC98EB5D92032DA840@SVR-ALH-EXC-02.mgc.mentorg.com>
In-Reply-To: <7ECEF9368E169544B43882BC98EB5D92032DA840@SVR-ALH-EXC-02.mgc.mentorg.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: dhcwg@ietf.org, Iljitsch van Beijnum <iljitsch@muada.com>, ipv6@ietf.org,
	"Bernie Volz \(volz\)" <volz@cisco.com>,
	"John Jason Brzozowski \(JJMB\)" <jjmb@jjmb.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

Leino, Tammy wrote:

> I appreciate everyone's comments and advice.  I am glad to see such
> passion for IPv6 and support of people in need.

You shouldn't.

You SHOULD remember that ND is *NOT* mandately for IPv6.

ND is, despite a lot of effort to fix it in some limited cases (an
obvious example is "7.5.  Changes to Sending Router Advertisements"
of RFC 3775), so broken that even people having passion for IPv6 can
not dare to say to mandate ND.

ND is a poorly designed protcol designed by a committee named IETF.

Instead, any IPv6 related protocols, including DHCP, should consider
*LUCKY* hosts on links *WITHOUT* any ND.

> I just want to voice my opinion that I feel a DHCPv6 prefix length
> option and default router option would be useful.

Prefix length is a health idea.

However, unfortunately for you, the concept of "default router", which
is developped by a committee named IETF, is a fatal violation of the
end to end principle of the Internet.

That is, end nodes of the Internet, definitely not so-called default
routers adjacent to them, MUST directly control the communication
without being bothered by so-called default routers.

To avoid fatal dameges of ND on links using ND, you can make your
host a router, though it will cause other problems (using default
route to shrink a routing table is another violation of the end to
end principle, which requires solutions not addressed by IPv6).

						Masataka Ohta

PS

FYI, the current multicast specification is as broken as ND that you
should avoid both of them. Eg, broken multicast requires full of
configurations that DHCP should avoid them.


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



From dhcwg-bounces@ietf.org Mon Aug 13 05:57:49 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKWeU-0005aW-Pc; Mon, 13 Aug 2007 05:55:58 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKWeS-0005aL-Ud; Mon, 13 Aug 2007 05:55:56 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IKWeS-00070V-Ce; Mon, 13 Aug 2007 05:55:56 -0400
Received: from [82.192.90.28] (nirrti.muada.com [82.192.90.28])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l7D9rbFX095561
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Mon, 13 Aug 2007 11:53:38 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
References: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Mon, 13 Aug 2007 11:55:46 +0200
To: Bernie Volz ((volz)) <volz@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: dhcwg@ietf.org, ipv6@ietf.org,
	"John Jason Brzozowski \(JJMB\)" <jjmb@jjmb.com>
Subject: [dhcwg] Re: prefix length determination 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

On 11-aug-2007, at 1:39, Bernie Volz ((volz)) wrote:

> Interface addresses are completely SEPARATE from routing information.
> Please do NOT confuse the two. This has been a source of confusion for
> many IPv6 implementors who know IPv4.

> The configuration of addresses for an interface MUST NOT be tied to  
> the
> configuration of prefix information for routing.

I disagree. For better or for worse, the notion of a subnet mask  
going along with an interface address is deeply ingrained in the way  
IP is implemented. Separating the two for no apparent reason is a bad  
idea.

> Just because a prefix
> is on a link, does not mean the interface necessarily has an  
> address for
> that prefix (it may have none, 1, or many).

Sure, that part is not a problem.

> Just because an interface
> has an address, does not mean that the system has any prefix  
> information
> for a prefix that "contains" that address.

Disagree here. How does it make sense to have an address on an  
interface and no knowledge about what other systems are directly  
connected to that interface? Note that "no knowledge" isn't the same  
thing as "assuming /128". I don't agree with the latter all that much  
either, but you still know SOMETHING in that case.

> And, a node should support both SLACC and DHCPv6 as "The two  
> methods are
> complementary but not mutually exclusive."

I'm sure there are cases where DHCPv6 is very useful, but _I_ don't  
want it on my network. IPv6 specifications and implementations  
without DHCPv6 have been around for the better part of a decade, so  
requiring DHCPv6 now seems curious at best. In other words: DHCPv6  
should be optional.

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



From dhcwg-bounces@ietf.org Mon Aug 13 07:15:48 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKXry-0003BJ-Bo; Mon, 13 Aug 2007 07:13:58 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IKXrx-0003BD-Ij
	for dhcwg@ietf.org; Mon, 13 Aug 2007 07:13:57 -0400
Received: from web30811.mail.mud.yahoo.com ([68.142.201.254])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IKXrx-0001QJ-79
	for dhcwg@ietf.org; Mon, 13 Aug 2007 07:13:57 -0400
Received: (qmail 40591 invoked by uid 60001); 13 Aug 2007 11:13:56 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=s9aa97suwS83NOVMeWEqtCiJz9ySuFJbFaqSeGiu/V2UU7yBv2HGArHXbQCt3jRB67UQ4pKD6Ck+VasNX12gnpLCUNKXWdfexl628XXTOxVI4Gvct/v4lPOLuL2y4R6ShDDRKTxO0WyX0tsJhTiBADxIChJyMlQ0LASMfNiXa7o=;
X-YMail-OSG: dsHFTzYVM1maZ23LrcjMzt54hX8wbsV9k8HM9_b_aC.KjmllKTPHohPUHDuwZPeTMg--
Received: from [209.191.118.120] by web30811.mail.mud.yahoo.com via HTTP;
	Mon, 13 Aug 2007 04:13:56 PDT
X-Mailer: YahooMailRC/651.48 YahooMailWebService/0.7.119
Date: Mon, 13 Aug 2007 04:13:56 -0700 (PDT)
From: RamaSubramanian KrishnaMurthi <ramasubbu_sk@yahoo.com>
To: dhcwg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-ID: <605161.40405.qm@web30811.mail.mud.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Subject: [dhcwg] DNS Registration for IATA address.
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Hi all, =0AI have basic question on DNS Registration  + DHCPv6.=0AFor IATA =
whether the DHCPClient should register its ipv6 address to the DNS Server ?=
=0AFor IATA whether the DHCPServer should register the client's ipv 6addres=
s to the DNS Server [FQDN ]?=0A=0ARFC 4704 doesn't talk about IANA & IATA. =
Correct/help me in this regards.=0A=0AThanks & Regards=0ARamaSubbu SK=0A=0A=
=0A       =0A______________________________________________________________=
______________________=0ANeed a vacation? Get great deals=0Ato amazing plac=
es on Yahoo! Travel.=0Ahttp://travel.yahoo.com/

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



From dhcwg-bounces@ietf.org Mon Aug 13 09:22:30 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKZqh-0004LE-3u; Mon, 13 Aug 2007 09:20:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKZqf-00049t-07; Mon, 13 Aug 2007 09:20:45 -0400
Received: from relay1.mentorg.com ([192.94.38.131])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IKZqd-0004iM-P6; Mon, 13 Aug 2007 09:20:44 -0400
Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58])
	by relay1.mentorg.com with esmtp 
	id 1IKZqd-0005sm-CH from tammy_leino@mentor.com ;
	Mon, 13 Aug 2007 06:20:43 -0700
Received: from SVR-ALH-EXC-02.mgc.mentorg.com ([134.86.110.227]) by
	SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 13 Aug 2007 06:20:42 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 13 Aug 2007 08:20:41 -0500
Message-ID: <7ECEF9368E169544B43882BC98EB5D92032DA845@SVR-ALH-EXC-02.mgc.mentorg.com>
In-Reply-To: <8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: prefix length determination for DHCPv6
Thread-Index: AcfdkCkBArq2yyYLRfmQC/rAndobKwAHIY8g
From: "Leino, Tammy" <tammy_leino@mentor.com>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>,
	"Bernie Volz ((volz))" <volz@cisco.com>
X-OriginalArrivalTime: 13 Aug 2007 13:20:42.0442 (UTC)
	FILETIME=[BFBEE2A0:01C7DDAC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: dhcwg@ietf.org, ipv6@ietf.org,
	"John Jason Brzozowski \(JJMB\)" <jjmb@jjmb.com>
Subject: [dhcwg] RE: prefix length determination 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

I agree with all your remarks Iljitsch, and I believe my customers feel
the same way as you.



-----Original Message-----
From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
Sent: Monday, August 13, 2007 5:56 AM
To: Bernie Volz ((volz))
Cc: Leino, Tammy; ipv6@ietf.org; John Jason Brzozowski (JJMB);
dhcwg@ietf.org
Subject: Re: prefix length determination for DHCPv6


On 11-aug-2007, at 1:39, Bernie Volz ((volz)) wrote:

> Interface addresses are completely SEPARATE from routing information.
> Please do NOT confuse the two. This has been a source of confusion for
> many IPv6 implementors who know IPv4.

> The configuration of addresses for an interface MUST NOT be tied to =20
> the
> configuration of prefix information for routing.

I disagree. For better or for worse, the notion of a subnet mask =20
going along with an interface address is deeply ingrained in the way =20
IP is implemented. Separating the two for no apparent reason is a bad =20
idea.

> Just because a prefix
> is on a link, does not mean the interface necessarily has an =20
> address for
> that prefix (it may have none, 1, or many).

Sure, that part is not a problem.

> Just because an interface
> has an address, does not mean that the system has any prefix =20
> information
> for a prefix that "contains" that address.

Disagree here. How does it make sense to have an address on an =20
interface and no knowledge about what other systems are directly =20
connected to that interface? Note that "no knowledge" isn't the same =20
thing as "assuming /128". I don't agree with the latter all that much =20
either, but you still know SOMETHING in that case.

> And, a node should support both SLACC and DHCPv6 as "The two =20
> methods are
> complementary but not mutually exclusive."

I'm sure there are cases where DHCPv6 is very useful, but _I_ don't =20
want it on my network. IPv6 specifications and implementations =20
without DHCPv6 have been around for the better part of a decade, so =20
requiring DHCPv6 now seems curious at best. In other words: DHCPv6 =20
should be optional.

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



From dhcwg-bounces@ietf.org Mon Aug 13 11:32:08 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKbrz-0005NR-7T; Mon, 13 Aug 2007 11:30:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IKbry-0005NK-3m
	for dhcwg@ietf.org; Mon, 13 Aug 2007 11:30:14 -0400
Received: from mx.isc.org ([2001:4f8:0:2::1c])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IKbrw-0008Va-LW
	for dhcwg@ietf.org; Mon, 13 Aug 2007 11:30:14 -0400
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "farside.isc.org", Issuer "ISC CA" (verified OK))
	by mx.isc.org (Postfix) with ESMTP id 2000711401F;
	Mon, 13 Aug 2007 15:30:12 +0000 (UTC)
	(envelope-from Shane_Kerr@isc.org)
Received: from [192.168.1.10] (hurix.ams-ix.net [193.194.136.45])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by farside.isc.org (Postfix) with ESMTP id 42D8FE6009;
	Mon, 13 Aug 2007 15:30:11 +0000 (UTC) (envelope-from shane@isc.org)
Message-ID: <46C07901.3070607@isc.org>
Date: Mon, 13 Aug 2007 17:30:09 +0200
From: Shane Kerr <Shane_Kerr@isc.org>
Organization: ISC
User-Agent: Thunderbird 2.0.0.6 (X11/20070806)
MIME-Version: 1.0
To: RamaSubramanian KrishnaMurthi <ramasubbu_sk@yahoo.com>
Subject: Re: [dhcwg] DNS Registration for IATA address.
References: <605161.40405.qm@web30811.mail.mud.yahoo.com>
In-Reply-To: <605161.40405.qm@web30811.mail.mud.yahoo.com>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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

RamaSubramanian KrishnaMurthi wrote:
> Hi all, 
> I have basic question on DNS Registration  + DHCPv6.
> For IATA whether the DHCPClient should register its ipv6 address to the DNS Server ?
> For IATA whether the DHCPServer should register the client's ipv 6address to the DNS Server [FQDN ]?
> 
> RFC 4704 doesn't talk about IANA & IATA. Correct/help me in this regards.

Good question!

There is some text about IA_TA:

   A client SHOULD NOT perform DNS updates to AAAA RRs for its non-
   Global Unicast addresses [7] or temporary addresses [6].

In general I would say that temporary addresses should not have their reverse
DNS updated. Other opinions?

You are correct that it is not explicit in the specification. :(

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

iD8DBQFGwHj8MsfZxBO4kbQRArs6AKCCl8VsUvM9Y6+nT9hZjpIgPtrtSgCeO2C9
C7/zRrPN0+3wLNKkEQ43rk8=
=sS12
-----END PGP SIGNATURE-----

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



From dhcwg-bounces@ietf.org Mon Aug 13 11:48:26 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKc7t-0006to-Ey; Mon, 13 Aug 2007 11:46:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKc7s-0006sQ-9Z; Mon, 13 Aug 2007 11:46:40 -0400
Received: from brmea-mail-4.sun.com ([192.18.98.36])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IKc7q-0000XT-L8; Mon, 13 Aug 2007 11:46:40 -0400
Received: from eastmail1bur.East.Sun.COM ([129.148.9.49])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l7DFkb8V001411; Mon, 13 Aug 2007 15:46:38 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail1bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with
	ESMTP id l7DFkbsQ002965; Mon, 13 Aug 2007 11:46:37 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l7DFd7Ru009970; Mon, 13 Aug 2007 11:39:08 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l7DFcvYp009967;
	Mon, 13 Aug 2007 11:38:57 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18112.31505.383738.265939@gargle.gargle.HOWL>
Date: Mon, 13 Aug 2007 11:38:57 -0400
From: James Carlson <james.d.carlson@sun.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>,
	"Leino, Tammy" <tammy_leino@mentor.com>
In-Reply-To: <8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: dhcwg@ietf.org, ipv6@ietf.org
Subject: [dhcwg] Re: prefix length determination 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

Iljitsch van Beijnum writes:
> On 11-aug-2007, at 1:39, Bernie Volz ((volz)) wrote:
> > The configuration of addresses for an interface MUST NOT be tied to  
> > the
> > configuration of prefix information for routing.
> 
> I disagree. For better or for worse, the notion of a subnet mask  
> going along with an interface address is deeply ingrained in the way  
> IP is implemented. Separating the two for no apparent reason is a bad  
> idea.

There's a problem with that idea.  There's no guarantee in any
deployment that the DHCPv6 server is actually the definitive source of
information about the prefixes that are on the link.  Routers are
supposed to be that source in IPv6 (via RAs), and DHCPv6 servers
needn't also be routers.

If you were to add an option to DHCPv6 to transfer routing-related
data (including prefixes and default router addresses), you'd have to
invent some way to keep the DHCPv6 server information in sync with the
actual set of routers on the network.  Otherwise, you're relying on
manual configuration of the DHCPv6 server that's continuously tweaked
to match the routers.

For that reason, I oppose adding this information to DHCPv6.  Unlike
IPv4, I think the DHCPv6 designers got this choice _right_.  For the
sake of consistency, should only be _one_ source of authoritative
information, and for prefixes and routes on hosts, RAs are it.

> > Just because an interface
> > has an address, does not mean that the system has any prefix  
> > information
> > for a prefix that "contains" that address.
> 
> Disagree here. How does it make sense to have an address on an  
> interface and no knowledge about what other systems are directly  
> connected to that interface? Note that "no knowledge" isn't the same  
> thing as "assuming /128". I don't agree with the latter all that much  
> either, but you still know SOMETHING in that case.

All that you know from DHCPv6 is the address.

> > And, a node should support both SLACC and DHCPv6 as "The two  
> > methods are
> > complementary but not mutually exclusive."
> 
> I'm sure there are cases where DHCPv6 is very useful, but _I_ don't  
> want it on my network. IPv6 specifications and implementations  
> without DHCPv6 have been around for the better part of a decade, so  
> requiring DHCPv6 now seems curious at best. In other words: DHCPv6  
> should be optional.

I think implementation of DHCPv6 can certainly be required by
consumers, including the DoD.  All they have to say is, "I don't care
what's optional in the RFC; I just won't buy any gear that doesn't
support this list of features, including DHCPv6."

Deployment and use of it, of course, is up to individual network
administrators, and is by no means required.

Leino, Tammy writes:
> Iljitsch, thank you for your comprehensive remarks.  I think my mistake
> was in believing an IPv6 router does not have to be configured to send
> RAs, but the DHCPv6 server could serve the same purpose as the RAs.  It
> appears DHCPv6 was meant to supplement RAs.

Exactly.

> As an embedded developer, there is a lot of overhead in terms of code
> space and memory requirements in the DHCPv6 protocol, particularly for
> customers wishing to just distribute DNS servers.  It would be nice if
> all the configuration options of DHCPv6 had been added to RAs.  This
> way, we would save on memory.

I think that's a mistake.

First of all, listening to RAs is no more expensive than listening to
DHCPv6 messages.  If you really feel compelled to do so, then have
your DHCPv6 implementation send RSes when setting up a new address,
and listen to the RAs and store the prefixes where they're handy.

Secondly, designing protocols to fit the limitations of today's
hardware (or, worse, the _perceived_ limitations) is an error.
Protocols last a long time, but hardware does not.  Consider, for
example, that IPv4 discussions were held over 30 years ago, when
common small computers had just a few KB of memory.

The skill in embedded implementation is in saving on memory where you
can without compromising integrity of the external interfaces.

Protocols last long enough that today's problems, unless they're
intrinsic, ought to be taken with a grain of salt.  And, yes, despite
my current employer address, my background (for the past 20 years or
so) has been in embedded systems as well.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From dhcwg-bounces@ietf.org Mon Aug 13 13:08:19 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKdNB-00064h-Vj; Mon, 13 Aug 2007 13:06:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IKdNA-00063f-CD
	for dhcwg@ietf.org; Mon, 13 Aug 2007 13:06:32 -0400
Received: from web30805.mail.mud.yahoo.com ([68.142.200.148])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IKdN9-0003jn-5B
	for dhcwg@ietf.org; Mon, 13 Aug 2007 13:06:32 -0400
Received: (qmail 49328 invoked by uid 60001); 13 Aug 2007 17:06:30 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=kXAzgKEXSkKyGPRo9OgBxa1rEUm2b4TqyiD5ElqMO+ZG+VIfu6nDtON3D5UO3jDpUSBJf20N/ARimiUJAh9CN6V5sJq0DlzzSNnMw+sVtFVKYu/bzpSDxhi/5EyAobTnLwb/xGrEWaqTPy23BelqHy3NpPel0ahAbafDFTgaUEY=;
X-YMail-OSG: ffVqIJcVM1nTJFE0OXRTg778ClyT8NOPJ0_uvS6RBh.Clkalxk8YWaQfRBmoI0SzYg--
Received: from [209.191.106.123] by web30805.mail.mud.yahoo.com via HTTP;
	Mon, 13 Aug 2007 10:06:30 PDT
X-Mailer: YahooMailRC/651.48 YahooMailWebService/0.7.119
Date: Mon, 13 Aug 2007 10:06:30 -0700 (PDT)
From: RamaSubramanian KrishnaMurthi <ramasubbu_sk@yahoo.com>
Subject: Fw: [dhcwg] DNS Registration for IATA address.
To: shane_kerr@isc.org, dhcwg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-ID: <641559.49066.qm@web30805.mail.mud.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Thanks for the reply. This means the DHCPClient should not send the FQDN op=
tions in the DHCP Packet for its non-Gobal Unicast addresses or temporary a=
ddresses and also client should not trigger DNS the update from the client =
end. am I right ?=0AIf some client still sends the FQDN option in the packe=
t, should the server do DNS update for the client ?=0A=0A=0AThanks & Regard=
s=0A-RamaSubbu SK =0A=0A=0A----- Original Message ----=0AFrom: Shane Kerr <=
Shane_Kerr@isc.org>=0ATo: RamaSubramanian KrishnaMurthi <ramasubbu_sk@yahoo=
.com>=0ACc: dhcwg@ietf.org=0ASent: Monday, August 13, 2007 9:00:09 PM=0ASub=
ject: Re: [dhcwg] DNS Registration for IATA address.=0A=0A=0A-----BEGIN PGP=
 SIGNED MESSAGE-----=0AHash: SHA1=0A=0ARamaSubramanian KrishnaMurthi wrote:=
=0A> Hi all, =0A> I have basic question on DNS Registration  + DHCPv6.=0A> =
For IATA whether the DHCPClient should register its ipv6 address to the DNS=
 Server ?=0A> For IATA whether the DHCPServer should register the client's =
ipv 6address to the DNS Server [FQDN ]?=0A> =0A> RFC 4704 doesn't talk abou=
t IANA & IATA. Correct/help me in this regards.=0A=0AGood question!=0A=0ATh=
ere is some text about IA_TA:=0A=0A   A client SHOULD NOT perform DNS updat=
es to AAAA RRs for its non-=0A   Global Unicast addresses [7] or temporary =
addresses [6].=0A=0AIn general I would say that temporary addresses should =
not have their reverse=0ADNS updated. Other opinions?=0A=0AYou are correct =
that it is not explicit in the specification. :(=0A=0A- --=0AShane=0A-----B=
EGIN PGP SIGNATURE-----=0AVersion: GnuPG v1.4.7 (GNU/Linux)=0AComment: Usin=
g GnuPG with Mozilla - http://enigmail.mozdev.org=0A=0AiD8DBQFGwHj8MsfZxBO4=
kbQRArs6AKCCl8VsUvM9Y6+nT9hZjpIgPtrtSgCeO2C9=0AC7/zRrPN0+3wLNKkEQ43rk8=3D=
=0A=3DsS12=0A-----END PGP SIGNATURE-----=0A=0A=0A       =0A________________=
____________________________________________________________________=0AGot =
a little couch potato? =0ACheck out fun summer activities for kids.=0Ahttp:=
//search.yahoo.com/search?fr=3Doni_on_mail&p=3Dsummer+activities+for+kids&c=
s=3Dbz=0A=0A=0A       =0A__________________________________________________=
__________________________________=0AGot a little couch potato? =0ACheck ou=
t fun summer activities for kids.=0Ahttp://search.yahoo.com/search?fr=3Doni=
_on_mail&p=3Dsummer+activities+for+kids&cs=3Dbz 

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



From dhcwg-bounces@ietf.org Mon Aug 13 13:27:37 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKdfr-00058o-TI; Mon, 13 Aug 2007 13:25:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKdfq-00055z-EK; Mon, 13 Aug 2007 13:25:50 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IKdfp-0005u2-5Q; Mon, 13 Aug 2007 13:25:50 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 13 Aug 2007 13:25:48 -0400
X-IronPort-AV: i="4.19,255,1183348800"; 
	d="scan'208"; a="128737524:sNHT88850510"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7DHPmNU030900; 
	Mon, 13 Aug 2007 13:25:48 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l7DHOkmt019014; 
	Mon, 13 Aug 2007 17:25:46 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Aug 2007 13:25:43 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 13 Aug 2007 13:25:42 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB2104B66C24@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <46C08F80.30200@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: prefix length determination for DHCPv6
Thread-Index: AcfdzJfGUKG96ROrSRqCW3d4AJhAJgAAbG8g
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "Alexandru Petrescu" <alexandru.petrescu@gmail.com>,
	"Leino, Tammy" <tammy_leino@mentor.com>
X-OriginalArrivalTime: 13 Aug 2007 17:25:43.0026 (UTC)
	FILETIME=[F9F9FD20:01C7DDCE]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7700; t=1187025948;
	x=1187889948; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=volz@cisco.com;
	z=From:=20=22Bernie=20Volz=20\(volz\)=22=20<volz@cisco.com>
	|Subject:=20RE=3A=20prefix=20length=20determination=20for=20DHCPv6
	|Sender:=20
	|To:=20=22Alexandru=20Petrescu=22=20<alexandru.petrescu@gmail.com>,
	=0A=20
	=20=20=20=20=20=20=20=22Leino,=20Tammy=22=20<tammy_leino@mentor.com>;
	bh=dgwJxOGhQOar9OLdPWWk9mL6fGU5HS2gK47OcOkvKGk=;
	b=iwkHTdgFF3MwuRhG8zAQpcOTQFddj6tjW1yE1hhdf1sRrBzA4DwWCZi2gR/vK2KXITGDkmaw
	73sD9E2rcxRKC3KtToNmyIVa8PyfJ0ON7LhEbSteiIBWkDxmTfOjjiwS;
Authentication-Results: rtp-dkim-1; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48
Cc: dhcwg@ietf.org, Iljitsch van Beijnum <iljitsch@muada.com>, ipv6@ietf.org,
	"John Jason Brzozowski \(JJMB\)" <jjmb@jjmb.com>
Subject: [dhcwg] RE: prefix length determination 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

DHCP server address would be useless because clients don't generally
unicast to the server/relay (and aren't allowed to unless the server has
sent a server-unicast option). And, if the server isn't on-link, unless
the client has an address of sufficient scope, it couldn't communicate
with the server directly.

And, what value does this add anyway?

If you are trying to get just get DNS server addresses, you can use
Information-Request (which is multicast) and you'll get the answer in a
Reply (which is unicast).

So, you add two messages - only one of which is multicast.

Even if you do use address assignment and thus Solicit, you can include
the Rapid Commit option which can save two messages (instead of
Solicit/Advertise/Request/Reply, you have Solicit/Reply). Only the
client's messages are multicast.

DHCPv6 messages are generally small and don't require a lot of back and
further. I really don't understand why people are objecting to one or
two request/reply exchanges (only the request of which is multicast).
Sure, it be nice if there were zero messages, but we're basically down
to as few as possible and most of these messages are tiny (especially
compared to the 300+ bytes that is the minimal size of DHCPv4 messages).

- Bernie=20

-----Original Message-----
From: Alexandru Petrescu [mailto:alexandru.petrescu@gmail.com]=20
Sent: Monday, August 13, 2007 1:06 PM
To: Leino, Tammy
Cc: Iljitsch van Beijnum; ipv6@ietf.org; John Jason Brzozowski (JJMB)
Subject: Re: prefix length determination for DHCPv6

Leino, Tammy wrote:
> Iljitsch, thank you for your comprehensive remarks.  I think my
> mistake was in believing an IPv6 router does not have to be
> configured to send RAs, but the DHCPv6 server could serve the same
> purpose as the RAs.  It appears DHCPv6 was meant to supplement RAs.
>=20
> As an embedded developer, there is a lot of overhead in terms of code
>  space and memory requirements in the DHCPv6 protocol, particularly
> for customers wishing to just distribute DNS servers.  It would be
> nice if all the configuration options of DHCPv6 had been added to
> RAs.  This way, we would save on memory.

Errr... the RAs would become larger and bandwidth would be wasted
sometimes.

I'd rather extend the RA to include the DHCP Server address such that
the mobile does not need to discover the DHCP Server address, thus
gaining time by eliminating Solicit and Advertise DHCP messages.

But these things are relatively widely implemented and modifying
anything in the existing operation risks taking a lot of time...

Alex

>=20
> Thank you again for your time and advice.
>=20
> Best Regards, Tammy
>=20
>=20
> -----Original Message----- From: Iljitsch van Beijnum
> [mailto:iljitsch@muada.com] Sent: Monday, August 13, 2007 6:18 AM To:
> Leino, Tammy Cc: John Jason Brzozowski (JJMB); Hemant Singh
> (shemant); ipv6@ietf.org Subject: Re: prefix length determination for
> DHCPv6
>=20
>=20
> On 11-aug-2007, at 1:09, Leino, Tammy wrote:
>=20
>> The reason I am not assuming there is a router on link configured
>> to send RAs with prefix options is because I don't see the point of
>>  DHCPv6 configuring addresses if a router is configured to do the
>> same job.
>=20
> :-)
>=20
>> Since the prefix length is carried in a prefix option of an RA, I
>> have to assume these will be absent on the link; otherwise, the
>> node would not be using DHCPv6 to obtain an address.
>=20
> But then, why do you need addresses when you have no external=20
> connectivity? A lot of stuff will work just fine over link local=20
> addresses, although the need to include a scope identifier gets in=20
> the way of some applications.
>=20
>>>> (There is of course the consideration that at this time, very
>>>> few
>> IPv6 implementations can configure an address through DHCPv6.)
>=20
>> Is this because of some shortcoming(s) in the specification or do=20
>> network managers find DHCPv6 unnecessary?
>=20
> First of all, the DHCPv6 specification was finished relatively late,
>  in 2003 if I'm not mistaken. Most major vendors had already=20
> implemented IPv6 by then and I'm guessing that deployment levels so
>  far haven't exactly given them much reason to drastically update=20
> their IPv6 implementations.
>=20
> Then there is the confusion about stateful and stateless DHCPv6 and
>  the whole discussion about the meaning of the M and O bits in router
>  advertisements. I think this created uncertainty in the market place
>  for some time.
>=20
> Since address configuration has always happened and continues to=20
> happen through stateless autoconfiguration, DHCPv6 address assignment
>  wasn't implemented widely, and you can only use this mechanism when
>  you can be sure that both the server and the clients support it. It
>  looks like now that IPv6 is gaining more widespread attention that
>  more people want this because it's the same as in IPv4, but "old=20
> school" IPv6 users are generally happy with stateless
> autoconfiguration.
>=20
> That leaves:
>=20
>> If they are not using DHCPv6, how do they distribute DNS servers
>> and other configuration information?
>=20
> In practice? They don't. As long as you have IPv4, you can use IPv4
>  for this.
>=20
> Other than that, you mostly manually configure an address. Although
>  DHCPv6 allows you to do this automatically, the trouble is that you
>  can't be sure that there will be a DHCPv6 server everywhere you go
> so in practice, the advantage of DHCPv6 over manual configuration is
>  limited. There was talk about using well-known anycasted addresses
>  for this but that never came off the ground.
>=20
> In the near future we'll have draft-jeong-dnsop-ipv6-dns-=20
> discovery-12.txt which is now in the RFC Editor queue. However, this
>  will have the same problem as DHCPv6: you can't be sure that someone
>  is making the info available until it's extremely widely
> implemented.
>=20
>> I am interested in learning how well received DHCPv6 has been.  We
>>  have been slow to implement it in our OS because of low demand.
>=20
> My opinion: DHCPv6 is a complex protocol that uses a relatively high
>  number of messages. In the past, UDP-based protocols have been=20
> especially susceptible to security problems in their implementations.
>  As such, I'm very happy to do without it when I don't need it and I
>  feel stronly that DHCPv6 should NOT be initiated by clients by=20
> default but only if RA flags indicate that they should do this, and
>  DNS configuration should be possible without DHCPv6.
>=20
> Having said that, there can be situations where it's useful to assign
>  an address to an IPv6 host, so there is certainly a place for
> DHCPv6. And prefix delegation is brilliant, this is a great way to
> provision IPv6 CPEs with an address block.
>=20
> --------------------------------------------------------------------=20
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www1.ietf.org/mailman/listinfo/ipv6=20
> --------------------------------------------------------------------
>=20


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email=20
______________________________________________________________________

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

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



From dhcwg-bounces@ietf.org Mon Aug 13 13:33:59 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKdm3-0001V0-4h; Mon, 13 Aug 2007 13:32:15 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKdm1-0001Tg-Dq; Mon, 13 Aug 2007 13:32:13 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IKdm0-00064y-Tl; Mon, 13 Aug 2007 13:32:13 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 13 Aug 2007 13:32:12 -0400
X-IronPort-AV: i="4.19,255,1183348800"; 
	d="scan'208"; a="67862743:sNHT65036262"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7DHWCqq001417; 
	Mon, 13 Aug 2007 13:32:12 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l7DHVvmj021800; 
	Mon, 13 Aug 2007 17:32:10 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Aug 2007 13:31:59 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 13 Aug 2007 13:31:58 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB2104B66C2C@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: prefix length determination for DHCPv6
Thread-Index: AcfdkC2wO9juwOwFS8S17xHxqdyAjQAPvXdw
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>
X-OriginalArrivalTime: 13 Aug 2007 17:31:59.0941 (UTC)
	FILETIME=[DAA2A750:01C7DDCF]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3309; t=1187026332;
	x=1187890332; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=volz@cisco.com;
	z=From:=20=22Bernie=20Volz=20\(volz\)=22=20<volz@cisco.com>
	|Subject:=20RE=3A=20prefix=20length=20determination=20for=20DHCPv6
	|Sender:=20
	|To:=20=22Iljitsch=20van=20Beijnum=22=20<iljitsch@muada.com>;
	bh=nTvFRdkvIf31eXuTe2zM/u9btasAeUEAAcNh/cBWBiw=;
	b=LbgxMx0v08HjW9UAwHrESjVZAlsGxapNCmJ7bPONCYUyCZRMqFGdBnEWrwHECw7tYxFemrM1
	kBGNnXMYbZcYdW/d+shN/M47MUrqJoL649y8sMXQOX0mUVTTyAlATKYP;
Authentication-Results: rtp-dkim-1; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: dhcwg@ietf.org, ipv6@ietf.org,
	"John Jason Brzozowski \(JJMB\)" <jjmb@jjmb.com>
Subject: [dhcwg] RE: prefix length determination 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

I guess we can agree to disagree.

I think fundamentally keeping the two things completely different will
be a far better way for people to think about this. There are
implementations that have assumed a /64 for DHCP assigned (or manually
configured) addresses when no prefix information was available
otherwise. That is clearly wrong. (A /128 is OK.)

I think "subnet mask going along with an interface address is deeply
ingrained in the way IP is implemented" is a very true statement for
IPv4. Let's not make that same assumption in IPv6, please.

---

All I was trying to clarify is that if you want to work in all IPv6
networks, you need BOTH SLAAC and stateful (DHCPv6). If you don't
implement both, you may not be able to do much on some networks (because
if they are stateless and you don't support that, you won't be able to
assign anything but a link-local address; or if they are stateful and
you don't suppor that, you may not be able to get a global address).

---

In today's world, one would hope that adding a DHCPv6 client would not
be adding a significant amount of code. The DHCPv6 client's logic isn't
that complex. Sure, it is one more thing to implement and test, but it
can't exactly take up a huge amount of memory.

- Bernie

-----Original Message-----
From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]=20
Sent: Monday, August 13, 2007 5:56 AM
To: Bernie Volz (volz)
Cc: Leino, Tammy; ipv6@ietf.org; John Jason Brzozowski (JJMB);
dhcwg@ietf.org
Subject: Re: prefix length determination for DHCPv6

On 11-aug-2007, at 1:39, Bernie Volz ((volz)) wrote:

> Interface addresses are completely SEPARATE from routing information.
> Please do NOT confuse the two. This has been a source of confusion for
> many IPv6 implementors who know IPv4.

> The configuration of addresses for an interface MUST NOT be tied to =20
> the
> configuration of prefix information for routing.

I disagree. For better or for worse, the notion of a subnet mask =20
going along with an interface address is deeply ingrained in the way =20
IP is implemented. Separating the two for no apparent reason is a bad =20
idea.

> Just because a prefix
> is on a link, does not mean the interface necessarily has an =20
> address for
> that prefix (it may have none, 1, or many).

Sure, that part is not a problem.

> Just because an interface
> has an address, does not mean that the system has any prefix =20
> information
> for a prefix that "contains" that address.

Disagree here. How does it make sense to have an address on an =20
interface and no knowledge about what other systems are directly =20
connected to that interface? Note that "no knowledge" isn't the same =20
thing as "assuming /128". I don't agree with the latter all that much =20
either, but you still know SOMETHING in that case.

> And, a node should support both SLACC and DHCPv6 as "The two =20
> methods are
> complementary but not mutually exclusive."

I'm sure there are cases where DHCPv6 is very useful, but _I_ don't =20
want it on my network. IPv6 specifications and implementations =20
without DHCPv6 have been around for the better part of a decade, so =20
requiring DHCPv6 now seems curious at best. In other words: DHCPv6 =20
should be optional.

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



From dhcwg-bounces@ietf.org Mon Aug 13 14:12:01 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKeMm-0005MW-GE; Mon, 13 Aug 2007 14:10:12 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKeMk-0005MO-2K; Mon, 13 Aug 2007 14:10:10 -0400
Received: from the.hankinsfamily.info ([204.152.186.148]
	helo=hankinsfamily.info)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IKeMj-0007WA-Ar; Mon, 13 Aug 2007 14:10:09 -0400
Received: from hcf.isc.org (c-24-6-52-101.hsd1.ca.comcast.net [24.6.52.101])
	(authenticated bits=0)
	by hankinsfamily.info (8.13.8/8.13.8) with ESMTP id l7DIA5Wb002752
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 13 Aug 2007 11:10:08 -0700
Received: by hcf.isc.org (Postfix, from userid 10200)
	id 2F03E5EEBE; Mon, 13 Aug 2007 11:10:28 -0500 (CDT)
Date: Mon, 13 Aug 2007 11:10:27 -0500
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
Message-ID: <20070813161026.GA4846@isc.org>
References: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA840@SVR-ALH-EXC-02.mgc.mentorg.com>
	<m2zm0ywj2a.wl%jinmei@isl.rdc.toshiba.co.jp>
Mime-Version: 1.0
In-Reply-To: <m2zm0ywj2a.wl%jinmei@isl.rdc.toshiba.co.jp>
User-Agent: Mutt/1.5.9i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: ipv6@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1546515426=="
Errors-To: dhcwg-bounces@ietf.org


--===============1546515426==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="82I3+IH0IqGh5yIs"
Content-Disposition: inline


--82I3+IH0IqGh5yIs
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Aug 11, 2007 at 05:51:09PM +0900, JINMEI Tatuya / =E7=A5=9E=E6=98=
=8E=E9=81=94=E5=93=89 wrote:
> In any event, I hear that some DHCPv6 guys are planning to make a new
> draft that covers this topic.  So I think it's better to hold off for
> now and wait for the document, rather than continue this thread
> with keeping possible misunderstanding or confusing about the base
> protocol principles.

I agree with everything Jinmei said, but this in particular.  Any
conclusions from these threads have a tendency to get forgotten -
it's better that we argue the position of a draft that an editor
can follow consensus.

But - before I hold my own tongue - I'd like to say that I think Tammy
has given us a kind of horse-sense wisdom that we don't often see at
the IETF;

  http://www1.ietf.org/mail-archive/web/dhcwg/current/msg07421.html

If I may expand on what I took away from that;

- RTADV and DHCPv6 do 'kind of' the same thing.  They configure knobs
  related to the network to which the host is attached.

	From the host's point of view, it is not "on the network"
	until both vehicles succeed.

	To get "on the network" reliably, both vehicles must succeed
	reliably.

	The number of corner cases to manage is staggering.

- It doesn't make a lick of difference to a host which vehicle gives
  them the configuration information.  Machines can't taste, they
  just consume the config.  Corrolaries;

	A host's user is going to call the systems admin, not the
	router operator, if one, the other, or both vehicles fail.

	Neither will a host's user appreciate the difference between
	configuring its prefix/router and its address/assist-servers.

- It doesn't really appear to make any difference at all to the
  network which vehicle gives them the configuration information.
  Clarifications;

	Ostensibly, the RTADV may be colocated on the router whereas
	DHCPv6 may be remote.

	But just as there's no reason why RTADV can't be colocated
	on a server (such as where there is no router), there is
	also no reason why DHCPv6 can't be colocated on a router
	(such as, in the home, where there is no server).

	So the "fate sharing" principle is bankrupt here: you can
	share whatever fate you want either way.  The existence of
	two separate protocols doesn't create fate.


So one thing we should consider and measure is wether or not this is
an example of "throwing spaghetti at the wall to see what sticks," and
if so wether or not it is worthwhile to make an attempt to clean up.

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

--82I3+IH0IqGh5yIs
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFGwIJycXeLeWu2vmoRAv86AJ9YqHC7IXIetDyAHRx4jEYQX1OTGwCglkx3
nAuCZBz7UbrDWpZQvwCPbZA=
=Vqsc
-----END PGP SIGNATURE-----

--82I3+IH0IqGh5yIs--


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

--===============1546515426==--




From dhcwg-bounces@ietf.org Mon Aug 13 14:21:54 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKeWN-0006Jh-Kv; Mon, 13 Aug 2007 14:20:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IKeWM-0006Jc-Tv
	for dhcwg@ietf.org; Mon, 13 Aug 2007 14:20:06 -0400
Received: from the.hankinsfamily.info ([204.152.186.148]
	helo=hankinsfamily.info) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IKeWL-0007w7-6P
	for dhcwg@ietf.org; Mon, 13 Aug 2007 14:20:06 -0400
Received: from hcf.isc.org (c-24-6-52-101.hsd1.ca.comcast.net [24.6.52.101])
	(authenticated bits=0)
	by hankinsfamily.info (8.13.8/8.13.8) with ESMTP id l7DIK2Mu002918
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <dhcwg@ietf.org>; Mon, 13 Aug 2007 11:20:04 -0700
Received: by hcf.isc.org (Postfix, from userid 10200)
	id 3DA635EEBE; Mon, 13 Aug 2007 11:20:24 -0500 (CDT)
Date: Mon, 13 Aug 2007 11:20:24 -0500
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: Fw: [dhcwg] DNS Registration for IATA address.
Message-ID: <20070813162023.GB4846@isc.org>
References: <641559.49066.qm@web30805.mail.mud.yahoo.com>
Mime-Version: 1.0
In-Reply-To: <641559.49066.qm@web30805.mail.mud.yahoo.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0765386216=="
Errors-To: dhcwg-bounces@ietf.org


--===============0765386216==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="R3G7APHDIzY6R/pk"
Content-Disposition: inline


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

On Mon, Aug 13, 2007 at 10:06:30AM -0700, RamaSubramanian KrishnaMurthi wro=
te:
> Thanks for the reply. This means the DHCPClient should not send the FQDN =
options in the DHCP Packet for its non-Gobal Unicast addresses or temporary=
 addresses and also client should not trigger DNS the update from the clien=
t end. am I right ?

Since the FQDN option is sent in the "root" options space, it may not
be obvious for which IA_* the FQDN is expected to apply.

Since the client may not know what kind of address it's going to get
=66rom the server, it's hard to ask the client not to send the option.

> If some client still sends the FQDN option in the packet, should the serv=
er do DNS update for the client ?

Probably the client may want an IA_NA but the server is only configured
to deliver IA_TA or IA_PD.

I would say it is probably enough to restrict DDNS processing to IA_NA
processing.

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

--R3G7APHDIzY6R/pk
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFGwITHcXeLeWu2vmoRAsewAJ99TLi6aURgb84KwMbNJkttIhNrTgCbBAGK
X4Ky5/ZzQFkIptvhUNkXxkI=
=+Aoe
-----END PGP SIGNATURE-----

--R3G7APHDIzY6R/pk--


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

--===============0765386216==--




From dhcwg-bounces@ietf.org Mon Aug 13 14:27:20 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKebe-0003Pn-4s; Mon, 13 Aug 2007 14:25:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKebc-0003PK-GM; Mon, 13 Aug 2007 14:25:32 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IKebY-0008DI-Vl; Mon, 13 Aug 2007 14:25:32 -0400
Received: from [82.192.90.28] (nirrti.muada.com [82.192.90.28])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l7DIM1ue009798
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Mon, 13 Aug 2007 20:22:02 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <18112.31505.383738.265939@gargle.gargle.HOWL>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Mon, 13 Aug 2007 20:24:08 +0200
To: James Carlson <james.d.carlson@sun.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: dhcwg@ietf.org, ipv6@ietf.org
Subject: [dhcwg] Re: prefix length determination 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

On 13-aug-2007, at 17:38, James Carlson wrote:

>> For better or for worse, the notion of a subnet mask
>> going along with an interface address is deeply ingrained in the way
>> IP is implemented. Separating the two for no apparent reason is a bad
>> idea.

> There's a problem with that idea.  There's no guarantee in any
> deployment that the DHCPv6 server is actually the definitive source of
> information about the prefixes that are on the link.  Routers are
> supposed to be that source in IPv6 (via RAs), and DHCPv6 servers
> needn't also be routers.

That may very well be, but if DHCP servers give out addresses, then  
this particular can of worms is already open and you have to deal  
with it. I.e., the only way a host is going to be able to use the  
address it got from the DHCP server, is if at least one router knows  
to send packets for that address to the host in question. The  
traditional way for routers to know this is to make sure that the  
addresses given to a host (through DHCP or other means) fall within  
the (well, a) subnet configured on the router's interface that the  
host connects to.

Now if we can manage for all that to happen correctly, why not finish  
the job and tell the host about the subnet size?

> If you were to add an option to DHCPv6 to transfer routing-related
> data (including prefixes and default router addresses), you'd have to
> invent some way to keep the DHCPv6 server information in sync with the
> actual set of routers on the network.  Otherwise, you're relying on
> manual configuration of the DHCPv6 server that's continuously tweaked
> to match the routers.

> For that reason, I oppose adding this information to DHCPv6.

I can go along with that for the most part.

> Unlike
> IPv4, I think the DHCPv6 designers got this choice _right_.  For the
> sake of consistency, should only be _one_ source of authoritative
> information, and for prefixes and routes on hosts, RAs are it.

Well, if you want consistency, you'll have to look elsewhere, because  
having DHCPv6 servers tell hosts their addresses breaks exactly this  
separation.

There are two reasons that I can think of to have a DHCPv6 server  
assign addresses:

1. Because it's desireable for the host to have an address that's  
based on information that the host itself doesn't know (for instance,  
a hash based address for shim6 proxy operation)

2. For authentication, authorization and control. I.e., as an ISP, I  
want to know which IPv6 belongs to which customer. The interesting  
part here is that it's not necessary for the DHCPv6 server to come up  
with the address. What we need is that some central server learns  
about all the addresses. The crucial difference here is that handing  
out addresses has the potential for routing problems, while learning  
addresses that the host got through other means (probably stateless  
autoconf) is just as useful but without the potential for trouble

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



From dhcwg-bounces@ietf.org Mon Aug 13 14:29:55 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKeeB-00068j-26; Mon, 13 Aug 2007 14:28:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKee9-00068K-RJ; Mon, 13 Aug 2007 14:28:09 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IKee8-0008IO-Gr; Mon, 13 Aug 2007 14:28:09 -0400
Received: from [82.192.90.28] (nirrti.muada.com [82.192.90.28])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l7DIOcri009864
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Mon, 13 Aug 2007 20:24:38 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <8E296595B6471A4689555D5D725EBB2104B66C24@xmb-rtp-20a.amer.cisco.com>
References: <8E296595B6471A4689555D5D725EBB2104B66C24@xmb-rtp-20a.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <B0259697-1C66-4053-AD82-661A54733544@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Mon, 13 Aug 2007 20:26:47 +0200
To: Bernie Volz ((volz)) <volz@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: dhcwg@ietf.org, Alexandru Petrescu <alexandru.petrescu@gmail.com>,
	ipv6@ietf.org, "John Jason Brzozowski \(JJMB\)" <jjmb@jjmb.com>
Subject: [dhcwg] Re: prefix length determination 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

On 13-aug-2007, at 19:25, Bernie Volz ((volz)) wrote:

> DHCPv6 messages are generally small and don't require a lot of back  
> and
> further. I really don't understand why people are objecting to one or
> two request/reply exchanges (only the request of which is multicast).
> Sure, it be nice if there were zero messages, but we're basically down
> to as few as possible and most of these messages are tiny (especially
> compared to the 300+ bytes that is the minimal size of DHCPv4  
> messages).

It adds up if you have a large number of hosts on a subnet.

Which got me thinking: wouldn't it be great if a single message from  
a host could serve as both a router solicitation and a DHCP solicit  
message?

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



From dhcwg-bounces@ietf.org Mon Aug 13 14:33:38 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKehm-0007y3-Cq; Mon, 13 Aug 2007 14:31:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IKehl-0007vx-AL
	for dhcwg@ietf.org; Mon, 13 Aug 2007 14:31:53 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IKehk-0008QE-40
	for dhcwg@ietf.org; Mon, 13 Aug 2007 14:31:53 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 13 Aug 2007 14:31:51 -0400
X-IronPort-AV: i="4.19,256,1183348800"; 
	d="scan'208"; a="67868315:sNHT57760258"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7DIVpxq027608; 
	Mon, 13 Aug 2007 14:31:51 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l7DIVpmd014770; 
	Mon, 13 Aug 2007 18:31:51 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Aug 2007 14:31:51 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Fw: [dhcwg] DNS Registration for IATA address.
Date: Mon, 13 Aug 2007 14:31:50 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB2104B66C76@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <20070813162023.GB4846@isc.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Fw: [dhcwg] DNS Registration for IATA address.
Thread-Index: Acfd1pp7YsjCdcQ4TqqBIWgPSAachgAAWwvA
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "David W. Hankins" <David_Hankins@isc.org>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 13 Aug 2007 18:31:51.0528 (UTC)
	FILETIME=[37635680:01C7DDD8]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1567; t=1187029911;
	x=1187893911; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=volz@cisco.com;
	z=From:=20=22Bernie=20Volz=20\(volz\)=22=20<volz@cisco.com>
	|Subject:=20RE=3A=20Fw=3A=20[dhcwg]=20DNS=20Registration=20for=20IATA=20a
	ddress. |Sender:=20
	|To:=20=22David=20W.=20Hankins=22=20<David_Hankins@isc.org>,
	=20<dhcwg@iet f.org>;
	bh=2l5QRUoZej3/cLCFbYeARk0uSPBqWdk7Btt+YH6JS0E=;
	b=fYNaeJPUaIUdPGoON7SWzBJTn9Od9txxexljq1gx6YYJ0Allf6sZBEK/Rsr609wlzDybd+iZ
	6i1McdYdBi1lYuGJWtFxYJiTVDnTP7pUddiDHuQcXqQj4KwdEgP+KPpl;
Authentication-Results: rtp-dkim-1; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

>I would say it is probably enough to restrict DDNS processing to IA_NA
>processing.=20

This is true today ... Though in the future there might be other IA_*
types to which it could apply.

- Bernie

-----Original Message-----
From: David W. Hankins [mailto:David_Hankins@isc.org]=20
Sent: Monday, August 13, 2007 12:20 PM
To: dhcwg@ietf.org
Subject: Re: Fw: [dhcwg] DNS Registration for IATA address.

On Mon, Aug 13, 2007 at 10:06:30AM -0700, RamaSubramanian KrishnaMurthi
wrote:
> Thanks for the reply. This means the DHCPClient should not send the
FQDN options in the DHCP Packet for its non-Gobal Unicast addresses or
temporary addresses and also client should not trigger DNS the update
from the client end. am I right ?

Since the FQDN option is sent in the "root" options space, it may not
be obvious for which IA_* the FQDN is expected to apply.

Since the client may not know what kind of address it's going to get
from the server, it's hard to ask the client not to send the option.

> If some client still sends the FQDN option in the packet, should the
server do DNS update for the client ?

Probably the client may want an IA_NA but the server is only configured
to deliver IA_TA or IA_PD.

I would say it is probably enough to restrict DDNS processing to IA_NA
processing.

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

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



From dhcwg-bounces@ietf.org Mon Aug 13 14:46:49 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKeuc-0007qf-IS; Mon, 13 Aug 2007 14:45:10 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKeub-0007pR-0j; Mon, 13 Aug 2007 14:45:09 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IKeua-00013Y-N8; Mon, 13 Aug 2007 14:45:08 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 13 Aug 2007 14:45:08 -0400
X-IronPort-AV: i="4.19,256,1183348800"; 
	d="scan'208"; a="128745321:sNHT47858486"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7DIj8fU019912; 
	Mon, 13 Aug 2007 14:45:08 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7DIitjU024027; 
	Mon, 13 Aug 2007 18:45:08 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Aug 2007 14:45:07 -0400
Received: from [192.168.1.103] ([10.86.242.95]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Aug 2007 14:45:07 -0400
In-Reply-To: <8E296595B6471A4689555D5D725EBB2104B66C24@xmb-rtp-20a.amer.cisco.com>
References: <8E296595B6471A4689555D5D725EBB2104B66C24@xmb-rtp-20a.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <3E043F9B-3E87-4722-A711-56098A24E58A@cisco.com>
Content-Transfer-Encoding: 7bit
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
Date: Mon, 13 Aug 2007 14:46:00 -0400
To: Tammy Leino <tammy_leino@mentor.com>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 13 Aug 2007 18:45:07.0571 (UTC)
	FILETIME=[11DDDC30:01C7DDDA]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=664; t=1187030708;
	x=1187894708; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rdroms@cisco.com;
	z=From:=20Ralph=20Droms=20<rdroms@cisco.com>
	|Subject:=20Re=3A=20[dhcwg]=20RE=3A=20prefix=20length=20determination=20f
	or=20DHCPv6 |Sender:=20
	|To:=20Tammy=20Leino=20<tammy_leino@mentor.com>;
	bh=XWu6KI1lHBYW1R0h9geDYIFHhud8ZNgjd48WscObaRA=;
	b=OJgBdvuVJ2IvGWRX9BoX+Ppv4PW2wOZquFk4jd7JNfXlJqVrTq6d5dYXsIkbGkMUxVPeO6sk
	uG0uO4wcuJn7/NeYvP2thlP5+9kB7FNsog3pHyesURkADGsO/H3bSgzg;
Authentication-Results: rtp-dkim-2; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: dhcwg@ietf.org, IETF List IPv6 Mailing <ipv6@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

Following up on Bernie's comments about DHCPv6 for non-address  
configuration information, take a look at RFC 3736, "stateless DHCP  
Service for IPv6" (ftp://ftp.rfc-editor.org/in-notes/rfc3736.txt) for  
a summary of the minimal implementation and deployment needed for  
DHCPv6 as a complement to SLAAC.

And, as David points out, it's perfectly feasible to colocate a  
DHCPv6 server with a router.  IOS includes a DHCPv6 server, currently  
providing Information Request (RFC 3736) and Prefix Delegation (RFC  
3633) services.  I was involved with the implementation of the  
Information Request service; trust me, it's *quite* simple.

- Ralph

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



From dhcwg-bounces@ietf.org Tue Aug 14 03:34:09 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKqt2-0003vN-Dw; Tue, 14 Aug 2007 03:32:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IKqt1-0003vG-6H
	for dhcwg@ietf.org; Tue, 14 Aug 2007 03:32:19 -0400
Received: from mx.isc.org ([2001:4f8:0:2::1c])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IKqsy-0007Po-KJ
	for dhcwg@ietf.org; Tue, 14 Aug 2007 03:32:18 -0400
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "farside.isc.org", Issuer "ISC CA" (verified OK))
	by mx.isc.org (Postfix) with ESMTP id 48B4311401F;
	Tue, 14 Aug 2007 07:32:15 +0000 (UTC)
	(envelope-from Shane_Kerr@isc.org)
Received: from [199.6.1.234] (unknown [199.6.1.234])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by farside.isc.org (Postfix) with ESMTP id 6ADE1E6022;
	Tue, 14 Aug 2007 07:32:14 +0000 (UTC) (envelope-from shane@isc.org)
Message-ID: <46C15A7C.1050209@isc.org>
Date: Tue, 14 Aug 2007 09:32:12 +0200
From: Shane Kerr <Shane_Kerr@isc.org>
Organization: ISC
User-Agent: Thunderbird 2.0.0.6 (X11/20070806)
MIME-Version: 1.0
To: "Bernie Volz (volz)" <volz@cisco.com>
Subject: Re: Fw: [dhcwg] DNS Registration for IATA address.
References: <8E296595B6471A4689555D5D725EBB2104B66C76@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <8E296595B6471A4689555D5D725EBB2104B66C76@xmb-rtp-20a.amer.cisco.com>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: dhcwg@ietf.org
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

Bernie Volz (volz) wrote:
>> I would say it is probably enough to restrict DDNS processing to IA_NA
>> processing. 
> 
> This is true today ... Though in the future there might be other IA_*
> types to which it could apply.

Actually, IA_PD seems like exactly the kind of thing you might want to process
automatically to delegate the DNS for reverse around the same time as the prefix.

I don't think this is possible with the current FQDN stuff, is it?

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

iD8DBQFGwVp3MsfZxBO4kbQRAvbDAKCZDa7gf4R+EEXGfLCOuig1yNCBSACgwQco
JEzvrkX4nYPS1aiI7VM7HFU=
=rzxT
-----END PGP SIGNATURE-----

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



From dhcwg-bounces@ietf.org Tue Aug 14 06:51:37 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKty8-0004f4-Pk; Tue, 14 Aug 2007 06:49:48 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IKty7-0004eu-Fc
	for dhcwg@ietf.org; Tue, 14 Aug 2007 06:49:47 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IKty7-0005k2-4D
	for dhcwg@ietf.org; Tue, 14 Aug 2007 06:49:47 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 14 Aug 2007 06:49:47 -0400
X-IronPort-AV: i="4.19,259,1183348800"; 
	d="scan'208"; a="67942277:sNHT56252928"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7EAnkqP019008; 
	Tue, 14 Aug 2007 06:49:46 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7EAnkjI005375; 
	Tue, 14 Aug 2007 10:49:46 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 14 Aug 2007 06:49:46 -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: Fw: [dhcwg] DNS Registration for IATA address.
Date: Tue, 14 Aug 2007 06:49:44 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB2104B66E2E@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <46C15A7C.1050209@isc.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Fw: [dhcwg] DNS Registration for IATA address.
Thread-Index: AcfeRUO5SwieVSILRCGAqK9rVx9uewAG0N6g
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: <shane_kerr@isc.org>
X-OriginalArrivalTime: 14 Aug 2007 10:49:46.0620 (UTC)
	FILETIME=[D477DBC0:01C7DE60]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1166; t=1187088586;
	x=1187952586; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=volz@cisco.com;
	z=From:=20=22Bernie=20Volz=20\(volz\)=22=20<volz@cisco.com>
	|Subject:=20RE=3A=20Fw=3A=20[dhcwg]=20DNS=20Registration=20for=20IATA=20a
	ddress. |Sender:=20 |To:=20<shane_kerr@isc.org>;
	bh=0sdrec4CojRN/vDlNcw8ZnP3xv2lJSFe2Zek3f7Zd+k=;
	b=L7WX6+01v/hrvbP3fKvraBQdGaHrtuRpkD8LqHLMo8y1K7rPfPeGEsyEaSAliDkB8Sun3Njv
	97uDgaEbjyIU1BtHicpzUCfKNsLeOHLublOD3HWKlj5rTRe0LD7NKcGY;
Authentication-Results: rtp-dkim-2; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

I think for IA_PD, there is
http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-opt-dnsdomain-
04.txt. Though this deals with the forward zone.

- Bernie=20

-----Original Message-----
From: Shane Kerr [mailto:Shane_Kerr@isc.org]=20
Sent: Tuesday, August 14, 2007 3:32 AM
To: Bernie Volz (volz)
Cc: dhcwg@ietf.org
Subject: Re: Fw: [dhcwg] DNS Registration for IATA address.

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

Bernie Volz (volz) wrote:
>> I would say it is probably enough to restrict DDNS processing to
IA_NA
>> processing.=20
>=20
> This is true today ... Though in the future there might be other IA_*
> types to which it could apply.

Actually, IA_PD seems like exactly the kind of thing you might want to
process
automatically to delegate the DNS for reverse around the same time as
the prefix.

I don't think this is possible with the current FQDN stuff, is it?

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

iD8DBQFGwVp3MsfZxBO4kbQRAvbDAKCZDa7gf4R+EEXGfLCOuig1yNCBSACgwQco
JEzvrkX4nYPS1aiI7VM7HFU=3D
=3DrzxT
-----END PGP SIGNATURE-----

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



From dhcwg-bounces@ietf.org Tue Aug 14 09:07:27 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKw5Y-0002iY-Hq; Tue, 14 Aug 2007 09:05:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKw5W-0002iJ-5W; Tue, 14 Aug 2007 09:05:34 -0400
Received: from sca-ea-mail-1.sun.com ([192.18.43.24])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IKw5Q-0000t5-D2; Tue, 14 Aug 2007 09:05:34 -0400
Received: from dm-east-01.east.sun.com ([129.148.9.192])
	by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id
	l7ED5RgC010421; Tue, 14 Aug 2007 13:05:27 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by dm-east-01.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP
	id l7ED5Q3N028475; Tue, 14 Aug 2007 09:05:26 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l7ECsDTM012576; Tue, 14 Aug 2007 08:54:13 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l7ECsDHP012573;
	Tue, 14 Aug 2007 08:54:13 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18113.42485.158453.756815@gargle.gargle.HOWL>
Date: Tue, 14 Aug 2007 08:54:13 -0400
From: James Carlson <james.d.carlson@sun.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: dhcwg@ietf.org, ipv6@ietf.org
Subject: [dhcwg] Re: prefix length determination 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

Iljitsch van Beijnum writes:
> On 13-aug-2007, at 17:38, James Carlson wrote:
> > There's a problem with that idea.  There's no guarantee in any
> > deployment that the DHCPv6 server is actually the definitive source of
> > information about the prefixes that are on the link.  Routers are
> > supposed to be that source in IPv6 (via RAs), and DHCPv6 servers
> > needn't also be routers.
> 
> That may very well be, but if DHCP servers give out addresses, then  
> this particular can of worms is already open and you have to deal  
> with it.

Not exactly.

If they provide addresses (they needn't do so), then they need to be
configured with lists and/or ranges of addresses to provide.  They
don't need to know about the full prefix extent, nor do they need to
know the IP addresses of the operable IPv6 routers on the network.

You're right that the lists of addresses are administratively related
to the prefixes, but they're not the same thing.  In fact, it's
possible for the two to be in different administrative hands -- one
group responsible for routing, and the other for address assignment
and configuration parameters.

A modified DHCPv6 protocol that hands out prefixes and default routes
(in order to subsume RA's role) will need to coordinate that _extra_
information for prefix length and lists of router addresses.

This whole line of debate seems pointless to me.  You need to support
RS/RA if you're going to operate on any normal IPv6 network.  Why
bother trying to force that data into DHCPv6?  It seems to be a desire
to support a configuration that nobody would need to use.

> I.e., the only way a host is going to be able to use the  
> address it got from the DHCP server, is if at least one router knows  
> to send packets for that address to the host in question.

Yes.

> The  
> traditional way for routers to know this is to make sure that the  
> addresses given to a host (through DHCP or other means) fall within  
> the (well, a) subnet configured on the router's interface that the  
> host connects to.

That's right, but it's not required that any DHCPv6 server "owns" all
of the addresses within any given prefix.

> Now if we can manage for all that to happen correctly, why not finish  
> the job and tell the host about the subnet size?

Because we already have a perfectly good protocol to do that -- RAs
already contain that information, so there's no need to duplicate it.

> > Unlike
> > IPv4, I think the DHCPv6 designers got this choice _right_.  For the
> > sake of consistency, should only be _one_ source of authoritative
> > information, and for prefixes and routes on hosts, RAs are it.
> 
> Well, if you want consistency, you'll have to look elsewhere, because  
> having DHCPv6 servers tell hosts their addresses breaks exactly this  
> separation.

I can almost agree with that.

I think a better deployment is to use stateless address assignment
with DHCPv6 Information Request.  That way, the DHCPv6 servers need
not have any address information, and the hosts can forge up addresses
as needed.

Having DHCPv6 servers supply addresses makes some sense to me in an
environment where you have hosts with assigned, fixed addresses, and
you use DHCPv6 to manage central control and renumbering.  It makes
less sense to me in more ad-hoc networks (where, oddly, DHCPv4 is
commonly used).

> 1. Because it's desireable for the host to have an address that's  
> based on information that the host itself doesn't know (for instance,  
> a hash based address for shim6 proxy operation)

Yes.

> 2. For authentication, authorization and control. I.e., as an ISP, I  
> want to know which IPv6 belongs to which customer. The interesting  
> part here is that it's not necessary for the DHCPv6 server to come up  
> with the address. What we need is that some central server learns  
> about all the addresses. The crucial difference here is that handing  
> out addresses has the potential for routing problems, while learning  
> addresses that the host got through other means (probably stateless  
> autoconf) is just as useful but without the potential for trouble

That sounds like IPv4 thinking to me.  If I were an ISP, I'd be
handing out customer prefixes, not addresses.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From dhcwg-bounces@ietf.org Tue Aug 14 13:37:47 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IL0JB-0007zx-V2; Tue, 14 Aug 2007 13:35:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IL0JA-0007zo-1k
	for dhcwg@ietf.org; Tue, 14 Aug 2007 13:35:56 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IL0J9-0001Ld-Ej
	for dhcwg@ietf.org; Tue, 14 Aug 2007 13:35:56 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 4113D5A6E5; Tue, 14 Aug 2007 10:35:54 -0700 (PDT)
Date: Tue, 14 Aug 2007 10:35:54 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: Fw: [dhcwg] DNS Registration for IATA address.
Message-ID: <20070814173554.GB3914@isc.org>
References: <46C15A7C.1050209@isc.org>
	<8E296595B6471A4689555D5D725EBB2104B66E2E@xmb-rtp-20a.amer.cisco.com>
Mime-Version: 1.0
In-Reply-To: <8E296595B6471A4689555D5D725EBB2104B66E2E@xmb-rtp-20a.amer.cisco.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
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="===============0994266578=="
Errors-To: dhcwg-bounces@ietf.org


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


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

On Tue, Aug 14, 2007 at 06:49:44AM -0400, Bernie Volz (volz) wrote:
> I think for IA_PD, there is
> http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-opt-dnsdomain-
> 04.txt. Though this deals with the forward zone.

A convention based upon the forward domain name (ns1.dnsdomain-option
etc) is likely to create lame delegations (clients that don't provide
addresses for the names of servers the prefix was delegated to).

A convention similar to the way CIDR delegations are sometimes made
today in IPv4 reverse dns (individual CNAMEs into a 'forward domain'
under the customer's control) is totally unworkable in IPv6.


So the most obvious thing is to allow the client to delegate reverse
dns for a prefix to a nameserver of its choosing (possibly itself,
possibly a "friendly server" which may not be nearby).  The most
flexible way to do that would be to allow the client to supply the
NS record(s) it wants (eg the server fqdn's).

I think we can't supply glue.  We'd have to create a way to transfer
either A or AAAA records, sure, and that's easy.  The problem is;

If the client wants the prefix delegated to itself.

And If the client is also being addressed (IA_NA) via DHCPv6.

Then the client cannot predict what its address will be at the time
of Request since the server can elect to change addresses without
error (Solicit, Advertise address A, Request address A, a prefix, and
to delegate reverse dns with glue for address A, Ack with address
B...).


Using the FQDN option for this is probably problematic, because you
can never be certain that the ddns update has completed (or even will
complete at some time in the future).  To place a delegation to the
client's dynamic name by default, for example, would be another way
to invite lame delegations.

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

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

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

iD8DBQFGwef6cXeLeWu2vmoRAiC0AKCTlT1/EcxHBrM/YhBYTh3H1Ox/FACfVf85
4VtWDN/ZWOiDa0XSenztS5I=
=fTGv
-----END PGP SIGNATURE-----

--ew6BAiZeqk4r7MaW--


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

--===============0994266578==--




From dhcwg-bounces@ietf.org Tue Aug 14 14:36:12 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IL1Dj-0000kc-1u; Tue, 14 Aug 2007 14:34:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IL1Dg-0000hr-6S; Tue, 14 Aug 2007 14:34:20 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IL1Df-0002bD-CQ; Tue, 14 Aug 2007 14:34:20 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 5CF455A6E5; Tue, 14 Aug 2007 11:34:18 -0700 (PDT)
Date: Tue, 14 Aug 2007 11:34:18 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
Message-ID: <20070814183418.GC3914@isc.org>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
Mime-Version: 1.0
In-Reply-To: <18113.42485.158453.756815@gargle.gargle.HOWL>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: ipv6@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0623170401=="
Errors-To: dhcwg-bounces@ietf.org


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


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

On Tue, Aug 14, 2007 at 08:54:13AM -0400, James Carlson wrote:
> > That may very well be, but if DHCP servers give out addresses, then =20
> > this particular can of worms is already open and you have to deal =20
> > with it.
>=20
> If they provide addresses (they needn't do so), then they need to be
> configured with lists and/or ranges of addresses to provide.  They
> don't need to know about the full prefix extent, nor do they need to
> know the IP addresses of the operable IPv6 routers on the network.

They effectively do, actually, one way or the other.  The server has
to give out an address that is appropriate for the link to which the
client is attached, and it needs to be able to Confirm the use of
addresses, which it may not have allocated.

So you either:

	- Know all broadcast domains.

	- For each domain, know all prefixes and their lengths.

Or:

	- Have a list of all the 'link-address' fields that all
	  operating DHCPv6 relays will use to identify a link.

	- For each 'link-address', a list of all appropriate addresses
	  for the link (possibly compacted by "contiguous range" or,
	  dare we say, prefix length).

	- A second list, this time of all appropriate addresses that
	  might be allocated by other servers operating on the
	  network.

One of these is easy, the other is rediculously menial.

I think that you will find realistically, DHCPv6 servers will know
prefix lengths.


> > Now if we can manage for all that to happen correctly, why not finish =
=20
> > the job and tell the host about the subnet size?
>=20
> Because we already have a perfectly good protocol to do that -- RAs
> already contain that information, so there's no need to duplicate it.

Surely, there must also be some need to perpetuate two protocols,
other than to simply perpetuate the need not to duplicate their
contents?


> > 2. For authentication, authorization and control. I.e., as an ISP, I =
=20
> > want to know which IPv6 belongs to which customer. The interesting =20
> > part here is that it's not necessary for the DHCPv6 server to come up =
=20
> > with the address. What we need is that some central server learns =20
> > about all the addresses. The crucial difference here is that handing =
=20
> > out addresses has the potential for routing problems, while learning =
=20
> > addresses that the host got through other means (probably stateless =20
> > autoconf) is just as useful but without the potential for trouble
>=20
> That sounds like IPv4 thinking to me.  If I were an ISP, I'd be
> handing out customer prefixes, not addresses.

Even if you delegate a prefix, you still need to know your customer's
address so that you might route packets to them.

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

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

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

iD8DBQFGwfWqcXeLeWu2vmoRAgkSAKCXGKOPEYb/lbTjfxu/aENOkZroXACeMX11
mxK6CjiE8s5mkS+2gYOyU00=
=59q/
-----END PGP SIGNATURE-----

--zx4FCpZtqtKETZ7O--


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

--===============0623170401==--




From dhcwg-bounces@ietf.org Tue Aug 14 19:02:10 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IL5N9-00033h-ND; Tue, 14 Aug 2007 19:00:23 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IL5N8-00033Y-JO; Tue, 14 Aug 2007 19:00:22 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IL5N7-0003rv-UH; Tue, 14 Aug 2007 19:00:22 -0400
Received: from [82.192.90.28] (nirrti.muada.com [82.192.90.28])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l7EMuo9Z041685
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Wed, 15 Aug 2007 00:56:51 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <021501c7de7e$7bcb11e0$0601a8c0@pc6>
References: <8E296595B6471A4689555D5D725EBB2104B66C24@xmb-rtp-20a.amer.cisco.com>
	<B0259697-1C66-4053-AD82-661A54733544@muada.com>
	<021501c7de7e$7bcb11e0$0601a8c0@pc6>
Mime-Version: 1.0 (Apple Message framework v752.3)
X-Priority: 3
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <DAF5070B-49CF-4915-BD57-D64517F9FD7B@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Wed, 15 Aug 2007 00:58:59 +0200
To: "tom.petch" <cfinss@dial.pipex.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: dhcwg@ietf.org, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: [dhcwg] Re: prefix length determination 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

On 14-aug-2007, at 12:38, tom.petch wrote:

>> Which got me thinking: wouldn't it be great if a single message from
>> a host could serve as both a router solicitation and a DHCP solicit
>> message?

> Yes, as long as the router 'server' and the DHCP server get their  
> act together
> and present a single coherent reply to the host:-)

If they tell the host the same thing then obviously we don't need two  
protocols.

I don't think there is necessarily a problem with different sources  
telling a host different things. But what we need is some rules about  
how the host is supposed to react to this situation.

Also note that today, this is already reality: you can have multiple  
routers. Hopefully, they all broadcast the same prefixes (if they  
don't, you could use a prefix from router A over router B and run  
into filters, unfortunately, for unexplained reasons, OS makers seem  
to think this is appropriate behavior) but obviously they'll be  
advertising different default gateway addresses. There are no rules  
about which a host should pick, but we do have dead neighbor  
detection which makes sure that only working ones are used.

Back to my original point: a mobile host isn't going to know whether  
a network it connects to is using stateless autoconfig, DHCPv6 or  
both. Sending discovery messages for both is probably wasteful in  
most situations, and sending discovery messages for only one will  
lead to delays if it chose the wrong one. So having one discovery  
message that can lead to replies of both kinds would be useful.  
Additionally, DHCPv6 servers could determine that a host doesn't need  
stateful information and the stateless information is in RAs, so it  
doesn't have to reply to certain request or requests from certain hosts.

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



From dhcwg-bounces@ietf.org Tue Aug 14 21:21:40 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IL7Y1-0006jj-LL; Tue, 14 Aug 2007 21:19:45 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IL7Xx-0006jP-GG
	for dhcwg@ietf.org; Tue, 14 Aug 2007 21:19:43 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IL7Xw-0001F5-Rc
	for dhcwg@ietf.org; Tue, 14 Aug 2007 21:19:41 -0400
Received: (qmail 67196 invoked from network); 15 Aug 2007 01:24:10 -0000
Received: from bmdi3192.bmobile.ne.jp (HELO necom830.hpcl.titech.ac.jp)
	(202.221.175.192)
	by necom830.hpcl.titech.ac.jp with SMTP; 15 Aug 2007 01:24:10 -0000
Message-ID: <46C2548C.4020700@necom830.hpcl.titech.ac.jp>
Date: Wed, 15 Aug 2007 10:19:08 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
References: <8E296595B6471A4689555D5D725EBB2104B66C24@xmb-rtp-20a.amer.cisco.com>	<B0259697-1C66-4053-AD82-661A54733544@muada.com>	<021501c7de7e$7bcb11e0$0601a8c0@pc6>
	<DAF5070B-49CF-4915-BD57-D64517F9FD7B@muada.com>
In-Reply-To: <DAF5070B-49CF-4915-BD57-D64517F9FD7B@muada.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: "tom.petch" <cfinss@dial.pipex.com>, dhcwg@ietf.org,
	IETF IPv6 Mailing List <ipv6@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

Iljitsch van Beijnum wrote:

> IPv6 specifications and implementations  without DHCPv6 have been
> around for the better part of a decade,

Given that IPv6 has never really been deployed, we should rather use
OSI, because it has longer history of specification and implementation.

> so  requiring DHCPv6 now
> seems curious at best. In other words: DHCPv6  should be optional.

ARP, DHCPv4, ND and DHCPv6 are all optional.

So?

> If they tell the host the same thing then obviously we don't need two  
> protocols.

That is, we don't need OSI nor IPv6.

Actually, IPv6 without ND is a little better than IPv4 that it may
worth deploying.

							Masataka Ohta


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



From dhcwg-bounces@ietf.org Wed Aug 15 06:19:17 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILFwL-0001VD-VF; Wed, 15 Aug 2007 06:17:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILFwL-0001V8-FV
	for dhcwg@ietf.org; Wed, 15 Aug 2007 06:17:25 -0400
Received: from mx.isc.org ([2001:4f8:0:2::1c])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ILFwK-0000dd-6v
	for dhcwg@ietf.org; Wed, 15 Aug 2007 06:17:25 -0400
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "farside.isc.org", Issuer "ISC CA" (verified OK))
	by mx.isc.org (Postfix) with ESMTP id 1669C11402B
	for <dhcwg@ietf.org>; Wed, 15 Aug 2007 10:17:23 +0000 (UTC)
	(envelope-from Shane_Kerr@isc.org)
Received: from [199.6.1.234] (unknown [199.6.1.234])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by farside.isc.org (Postfix) with ESMTP id 2A91FE6022;
	Wed, 15 Aug 2007 10:17:21 +0000 (UTC) (envelope-from shane@isc.org)
Message-ID: <46C2D2B0.1040108@isc.org>
Date: Wed, 15 Aug 2007 12:17:20 +0200
From: Shane Kerr <Shane_Kerr@isc.org>
Organization: ISC
User-Agent: Thunderbird 2.0.0.6 (X11/20070806)
MIME-Version: 1.0
To: "David W. Hankins" <David_Hankins@isc.org>
Subject: Re: Fw: [dhcwg] DNS Registration for IATA address.
References: <46C15A7C.1050209@isc.org>	<8E296595B6471A4689555D5D725EBB2104B66E2E@xmb-rtp-20a.amer.cisco.com>
	<20070814173554.GB3914@isc.org>
In-Reply-To: <20070814173554.GB3914@isc.org>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: dhcwg@ietf.org
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

David W. Hankins wrote:
> On Tue, Aug 14, 2007 at 06:49:44AM -0400, Bernie Volz (volz) wrote:
>> I think for IA_PD, there is
>> http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-opt-dnsdomain-
>> 04.txt. Though this deals with the forward zone.

<snip/>

> So the most obvious thing is to allow the client to delegate reverse
> dns for a prefix to a nameserver of its choosing (possibly itself,
> possibly a "friendly server" which may not be nearby).  The most
> flexible way to do that would be to allow the client to supply the
> NS record(s) it wants (eg the server fqdn's).

Another possibility is to let the client (or other devices in the prefix
delegated by IA_PD) update the reverse using dynamic DNS.

The DNS server might be willing to use an IP-based ACL (meaning, "let
1:2:3:4:5:6:7:8 update the reverse for itself"), or there may be a need to
transfer a secret to the client (like a TSIG key).

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

iD8DBQFGwtKsMsfZxBO4kbQRAocoAKDPUReKlVxGGNhE+DfoIPUswZ5YBgCdHxda
pzq4vPnEqLoSxHsmmAg2/AE=
=3OT7
-----END PGP SIGNATURE-----

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



From dhcwg-bounces@ietf.org Wed Aug 15 10:42:37 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILK3N-0004Rz-DC; Wed, 15 Aug 2007 10:40:57 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILK3L-0004Qe-Rt; Wed, 15 Aug 2007 10:40:55 -0400
Received: from sca-ea-mail-2.sun.com ([192.18.43.25])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1ILK3L-0005J3-67; Wed, 15 Aug 2007 10:40:55 -0400
Received: from eastmail1bur.East.Sun.COM ([129.148.9.49])
	by sca-ea-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id
	l7FEesbK004815; Wed, 15 Aug 2007 14:40:54 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail1bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with
	ESMTP id l7FEer57027860; Wed, 15 Aug 2007 10:40:53 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l7FEXL4N002404; Wed, 15 Aug 2007 10:33:21 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l7FEXGPm002401;
	Wed, 15 Aug 2007 10:33:16 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18115.3756.371573.103258@gargle.gargle.HOWL>
Date: Wed, 15 Aug 2007 10:33:16 -0400
From: James Carlson <james.d.carlson@sun.com>
To: "David W. Hankins" <David_Hankins@isc.org>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
In-Reply-To: <20070814183418.GC3914@isc.org>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: dhcwg@ietf.org, ipv6@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 writes:
> On Tue, Aug 14, 2007 at 08:54:13AM -0400, James Carlson wrote:
> > > That may very well be, but if DHCP servers give out addresses, then  
> > > this particular can of worms is already open and you have to deal  
> > > with it.
> > 
> > If they provide addresses (they needn't do so), then they need to be
> > configured with lists and/or ranges of addresses to provide.  They
> > don't need to know about the full prefix extent, nor do they need to
> > know the IP addresses of the operable IPv6 routers on the network.
> 
> They effectively do, actually, one way or the other.  The server has
> to give out an address that is appropriate for the link to which the
> client is attached,

If the DHCPv6 assigns addresses at all (as opposed to just providing
configuration parameters), then it needs to be able to work within the
prefixes assigned on the link.  That's true.  It needn't use *all* of
the addresses possible within the prefix, and that's the configuration
management part.

> and it needs to be able to Confirm the use of
> addresses, which it may not have allocated.

That doesn't make sense to me.  The DHCPv6 Confirm message is for
confirming an address lease.  If the server hasn't allocated the
lease, then it _cannot_ confirm anything about the address and must
Nak in response.  If it does confirm addresses it hasn't allocated,
then it's just broken.

> 	- Have a list of all the 'link-address' fields that all
> 	  operating DHCPv6 relays will use to identify a link.

I'm confused.  Why would relays be confirming anything?

> I think that you will find realistically, DHCPv6 servers will know
> prefix lengths.

None that I've worked with (including the WIDE server) seems to care.
What's needed are assignment ranges, not prefixes.

> > > Now if we can manage for all that to happen correctly, why not finish  
> > > the job and tell the host about the subnet size?
> > 
> > Because we already have a perfectly good protocol to do that -- RAs
> > already contain that information, so there's no need to duplicate it.
> 
> Surely, there must also be some need to perpetuate two protocols,
> other than to simply perpetuate the need not to duplicate their
> contents?

If you're going to deprecate DHCPv6 for address assignment and fold it
into the RA mechanism, then I'd be (somewhat weakly) in favor of that.

If you're just going to duplicate things, then I'm very much opposed.

> > > 2. For authentication, authorization and control. I.e., as an ISP, I  
> > > want to know which IPv6 belongs to which customer. The interesting  
> > > part here is that it's not necessary for the DHCPv6 server to come up  
> > > with the address. What we need is that some central server learns  
> > > about all the addresses. The crucial difference here is that handing  
> > > out addresses has the potential for routing problems, while learning  
> > > addresses that the host got through other means (probably stateless  
> > > autoconf) is just as useful but without the potential for trouble
> > 
> > That sounds like IPv4 thinking to me.  If I were an ISP, I'd be
> > handing out customer prefixes, not addresses.
> 
> Even if you delegate a prefix, you still need to know your customer's
> address so that you might route packets to them.

I don't understand that.

If you delegate a prefix, then you route to the prefix -- best match.
Why would you care about individual addresses within the prefix?

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From dhcwg-bounces@ietf.org Wed Aug 15 12:28:43 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILLhw-0005Cx-KP; Wed, 15 Aug 2007 12:26:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILLhu-0005Cq-0W
	for dhcwg@ietf.org; Wed, 15 Aug 2007 12:26:54 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ILLht-0001oQ-Ht
	for dhcwg@ietf.org; Wed, 15 Aug 2007 12:26:53 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 267C55A6E5; Wed, 15 Aug 2007 09:26:52 -0700 (PDT)
Date: Wed, 15 Aug 2007 09:26:52 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: Fw: [dhcwg] DNS Registration for IATA address.
Message-ID: <20070815162651.GA18683@isc.org>
References: <46C15A7C.1050209@isc.org>
	<8E296595B6471A4689555D5D725EBB2104B66E2E@xmb-rtp-20a.amer.cisco.com>
	<20070814173554.GB3914@isc.org> <46C2D2B0.1040108@isc.org>
Mime-Version: 1.0
In-Reply-To: <46C2D2B0.1040108@isc.org>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
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="===============1806560805=="
Errors-To: dhcwg-bounces@ietf.org


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


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

On Wed, Aug 15, 2007 at 12:17:20PM +0200, Shane Kerr wrote:
> Another possibility is to let the client (or other devices in the prefix
> delegated by IA_PD) update the reverse using dynamic DNS.
>=20
> The DNS server might be willing to use an IP-based ACL (meaning, "let
> 1:2:3:4:5:6:7:8 update the reverse for itself"), or there may be a need to
> transfer a secret to the client (like a TSIG key).

Sure, letting devices update their own PTR is done on some IPv4
networks even.

With some DHCPv6 extensions, we could provide an encrypted space to
carry something like a TSIG key.


But, where the client that's getting a prefix wants to operate as its
own DHCP (or router solicitation) server, it seems to make the most
symmetry to just operate their own DNS servers.

You're basically 'running your own mini network' at that point.


Meaning, if you wanted to keep the delegation on the prefix owner's
servers, you could just as easily use the prefix owner's DHCP servers
for the delegated prefix (the client becomes a relay), and let them
take care of DNS.

--=20
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil?	 https://secure.isc.org/store/t-shirt/
--=20
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins

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

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

iD8DBQFGwylLcXeLeWu2vmoRAoIJAJ4nB5kGPqCOcgo8Lf7sDzbtVZUAWQCgvdRB
3AZpe5JKAllXNOLw5IH8V0I=
=AaJX
-----END PGP SIGNATURE-----

--PNTmBPCT7hxwcZjr--


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

--===============1806560805==--




From dhcwg-bounces@ietf.org Wed Aug 15 13:53:33 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILN1z-0000et-Vv; Wed, 15 Aug 2007 13:51:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILN1y-0000ek-K1; Wed, 15 Aug 2007 13:51:42 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILN1x-0004AV-Oj; Wed, 15 Aug 2007 13:51:42 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 78DCC5A6E5; Wed, 15 Aug 2007 10:51:40 -0700 (PDT)
Date: Wed, 15 Aug 2007 10:51:40 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
Message-ID: <20070815175140.GC18683@isc.org>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
Mime-Version: 1.0
In-Reply-To: <18115.3756.371573.103258@gargle.gargle.HOWL>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 3a4bc66230659131057bb68ed51598f8
Cc: ipv6@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0373967010=="
Errors-To: dhcwg-bounces@ietf.org


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


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

On Wed, Aug 15, 2007 at 10:33:16AM -0400, James Carlson wrote:
> > and it needs to be able to Confirm the use of
> > addresses, which it may not have allocated.
>=20
> That doesn't make sense to me.  The DHCPv6 Confirm message is for
> confirming an address lease.  If the server hasn't allocated the
> lease, then it _cannot_ confirm anything about the address and must
> Nak in response.  If it does confirm addresses it hasn't allocated,
> then it's just broken.

I'm not sure where you got that idea - certainly not from RFC3315
section 18.2.2 ("Receipt of Confirm Messages" under "Server
Behavior").

I'll spare pasting the content to the lists - please have a read
and let me know if you still disagree.

> > 	- Have a list of all the 'link-address' fields that all
> > 	  operating DHCPv6 relays will use to identify a link.
>=20
> I'm confused.  Why would relays be confirming anything?

I'm sorry - this is a DHCPv6 protocol mechanic, something only
a DHCP geek would know.

The relay messages' 'link-address' field is central to the server's
calculation of the client's location (which "broadcast domain"
they're attached to).

Basically it's how you know which addresses are appropriate for the
client, based on what network they're attached to.

So this is a server inspecting a chain of relayed messages and
finding the link-address(es) it thinks are relevant to the client.
Then using that as a key to find the address(es) it needs to
deliver to the client.

One way to do this is to find a prefix that contains the selected
link-address (masking and comparing) and work outwards.

One other way to do this is to index the link-addresses specifically,
or some approximation of the same.

Does that make more sense now?

> > I think that you will find realistically, DHCPv6 servers will know
> > prefix lengths.
>=20
> None that I've worked with (including the WIDE server) seems to care.
> What's needed are assignment ranges, not prefixes.

I'm familiar with half of the story here, and uncomfortable with
speaking about a specific competitor's product (but it appears I will
do it anyway).  My opinion of WIDE's Confirm message processing is
that it does know the prefix length: it assumes all prefixes are /64,
by comparing the first 8 bytes of addresses.

I make no judgement here of the efficacy or correctness of this
implementation.

If there is an expert on WIDE's implementation that can describe how
it reaches a dynamic pool from relays (without relays, it appears to
follow interface definitions), I'm curious to know the rest of the
story.

> > Surely, there must also be some need to perpetuate two protocols,
> > other than to simply perpetuate the need not to duplicate their
> > contents?
>=20
> If you're going to deprecate DHCPv6 for address assignment and fold it
> into the RA mechanism, then I'd be (somewhat weakly) in favor of that.
>=20
> If you're just going to duplicate things, then I'm very much opposed.

Neither of those really sound like a good idea to me, but then I'm
also lacking the power to do either of them.  I guess the grass is
not always greener on the other side.

But let's save this discussion for a draft.  Rumor has it, someone is
writing one on this topic (or at least exploring the issues), and I
want to read what they have to say.

> > Even if you delegate a prefix, you still need to know your customer's
> > address so that you might route packets to them.
>=20
> I don't understand that.
>=20
> If you delegate a prefix, then you route to the prefix -- best match.

Yes, but how does that route get in the table, and what next-hop is
set?  You have to know your customer's address eventually.

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

--ctP54qlpMx3WjD+/
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFGwz0scXeLeWu2vmoRAicQAJ9d2oBvxaTuqX+6dkDNL9pX4ELJoACePfDm
QLQY/du8D1DnE2EncgfCmTk=
=8BGm
-----END PGP SIGNATURE-----

--ctP54qlpMx3WjD+/--


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

--===============0373967010==--




From dhcwg-bounces@ietf.org Wed Aug 15 14:07:51 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILNFu-0001uY-2B; Wed, 15 Aug 2007 14:06:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILNFr-0001ok-Sn; Wed, 15 Aug 2007 14:06:03 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILNFq-0004Vc-Gz; Wed, 15 Aug 2007 14:06:03 -0400
Received: from ams-dkim-2.cisco.com ([144.254.224.139])
	by ams-iport-1.cisco.com with ESMTP; 15 Aug 2007 20:06:02 +0200
X-IronPort-AV: i="4.19,267,1183327200"; 
	d="scan'208"; a="150671015:sNHT42734956"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7FI61d6006896; 
	Wed, 15 Aug 2007 20:06:01 +0200
Received: from gpk-xdm-001.cisco.com (gpk-xdm-001.cisco.com [64.103.70.176])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7FI5qx0010856; 
	Wed, 15 Aug 2007 18:05:57 GMT
Received: from gpk-xdm-001.cisco.com (localhost.localdomain [127.0.0.1])
	by gpk-xdm-001.cisco.com (8.13.1/8.13.1) with ESMTP id l7FI5qbn012940; 
	Wed, 15 Aug 2007 19:05:52 +0100
Received: (from otroan@localhost)
	by gpk-xdm-001.cisco.com (8.13.1/8.13.1/Submit) id l7FI5q2H012939;
	Wed, 15 Aug 2007 19:05:52 +0100
X-Authentication-Warning: gpk-xdm-001.cisco.com: otroan set sender to
	ot@cisco.com using -f
From: Ole Troan <ot@cisco.com>
To: "David W. Hankins" <David_Hankins@isc.org>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
Date: Wed, 15 Aug 2007 19:05:51 +0100
In-Reply-To: <20070815175140.GC18683@isc.org> (David W. Hankins's message of
	"Wed\, 15 Aug 2007 10\:51\:40 -0700")
Message-ID: <7t5abss7jwg.fsf@gpk-xdm-001.cisco.com>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=433; t=1187201161;
	x=1188065161; c=relaxed/simple; s=amsdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=ot@cisco.com;
	z=From:=20Ole=20Troan=20<ot@cisco.com>
	|Subject:=20Re=3A=20[dhcwg]=20Re=3A=20prefix=20length=20determination=20f
	or=20DHCPv6 |Sender:=20;
	bh=E5JMeBbF2Z+7sVV01LFQNhKohtMqDTbDWJgFkYoe5kc=;
	b=t+RXkg5l6RHnXZRrzlWnZ3dskQYAF8w9noep5TA7kiMTujPyeaffvDRh9T0zy7vLQfyw1D9W
	KLfePNJxdPycSh9KbmQZd0vqhkzu4tKEgx+8DfDTinnx37pDhhiaNZ6m;
Authentication-Results: ams-dkim-2; header.From=ot@cisco.com; dkim=pass (sig
	from cisco.com/amsdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: dhcwg@ietf.org, ipv6@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

>> > Even if you delegate a prefix, you still need to know your customer's
>> > address so that you might route packets to them.
>> 
>> I don't understand that.
>> 
>> If you delegate a prefix, then you route to the prefix -- best match.
>
> Yes, but how does that route get in the table, and what next-hop is
> set?  You have to know your customer's address eventually.

next-hop is the link-local address though.

/ot

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



From dhcwg-bounces@ietf.org Wed Aug 15 14:33:27 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILNec-00057S-O7; Wed, 15 Aug 2007 14:31:38 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILNea-00057A-M2; Wed, 15 Aug 2007 14:31:36 -0400
Received: from sca-ea-mail-3.sun.com ([192.18.43.21])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1ILNea-0003Vo-0l; Wed, 15 Aug 2007 14:31:36 -0400
Received: from eastmail1bur.East.Sun.COM ([129.148.9.49])
	by sca-ea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l7FIVZoi027677; Wed, 15 Aug 2007 18:31:35 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail1bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with
	ESMTP id l7FIVYgw009987; Wed, 15 Aug 2007 14:31:34 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l7FIGaP8006208; Wed, 15 Aug 2007 14:16:36 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l7FIGWxb006203;
	Wed, 15 Aug 2007 14:16:32 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18115.17151.731654.808164@gargle.gargle.HOWL>
Date: Wed, 15 Aug 2007 14:16:31 -0400
From: James Carlson <james.d.carlson@sun.com>
To: Ole Troan <ot@cisco.com>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
In-Reply-To: <7t5abss7jwg.fsf@gpk-xdm-001.cisco.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
	<7t5abss7jwg.fsf@gpk-xdm-001.cisco.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: ipv6@ietf.org, dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Ole Troan writes:
> >> > Even if you delegate a prefix, you still need to know your customer's
> >> > address so that you might route packets to them.
> >> 
> >> I don't understand that.
> >> 
> >> If you delegate a prefix, then you route to the prefix -- best match.
> >
> > Yes, but how does that route get in the table, and what next-hop is
> > set?  You have to know your customer's address eventually.
> 
> next-hop is the link-local address though.

Right; it's the link-local address of the router to which you've
delegated the prefix.

It's not the address of every single machine on the customer's
network.  In fact, knowing the addresses of the machines on the
customer's network is useless, as it doesn't tell you the address of
that CPE router.

Obvious sorts of ways to get this would be to keep track of your
delegations or (alternatively) use an appropriate routing protocol.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From dhcwg-bounces@ietf.org Wed Aug 15 15:03:52 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILO80-0001YP-IN; Wed, 15 Aug 2007 15:02:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILO7z-0001Y9-Un; Wed, 15 Aug 2007 15:01:59 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILO7z-0005pV-Bx; Wed, 15 Aug 2007 15:01:59 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 41AE55A6E5; Wed, 15 Aug 2007 12:01:58 -0700 (PDT)
Date: Wed, 15 Aug 2007 12:01:58 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
Message-ID: <20070815190158.GE18683@isc.org>
References: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
	<7t5abss7jwg.fsf@gpk-xdm-001.cisco.com>
	<18115.17151.731654.808164@gargle.gargle.HOWL>
Mime-Version: 1.0
In-Reply-To: <18115.17151.731654.808164@gargle.gargle.HOWL>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: ipv6@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1743065560=="
Errors-To: dhcwg-bounces@ietf.org


--===============1743065560==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="8w3uRX/HFJGApMzv"
Content-Disposition: inline


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

On Wed, Aug 15, 2007 at 02:16:31PM -0400, James Carlson wrote:
> Ole Troan writes:
> > >> If you delegate a prefix, then you route to the prefix -- best match.
> > >
> > > Yes, but how does that route get in the table, and what next-hop is
> > > set?  You have to know your customer's address eventually.
> >=20
> > next-hop is the link-local address though.
>=20
> Right; it's the link-local address of the router to which you've
> delegated the prefix.

Well, sometimes.  It depends what you're doing.

Either way:  You need to know the customer's address.  A DHCPv6 server
off in the weeds does not necessarily know what link local address the
client is using (because it might change without notification).  It
may know what global addresses the client is using (because it
allocated them), but won't if router solicition is in use.  A
router solicitation system certainly doesn't have any knowledge of
which customer is which nor what addresses global or not which they're
using.

This is but one facet of a network's operation: try not to focus on
it too much.  There are potentially a multitude of reasons to know
which of your customers are online, and how to reach them.  Testing
connectivity alone (such as during a support call).

> It's not the address of every single machine on the customer's
> network.  In fact, knowing the addresses of the machines on the
> customer's network is useless, as it doesn't tell you the address of
> that CPE router.

I'm not sure why you make this declaration (twice now), when no one
has suggested the counterpositive.  Maybe I misunderstood Iljitsch.

> Obvious sorts of ways to get this would be to keep track of your
> delegations or (alternatively) use an appropriate routing protocol.

Which I think gets us back to what Iljitsch said in the first place,
except that realistically ISPs are going to find it difficult and/or
costly to trust routing information from eg broadband customers, so
really what you're looking at is some way to provide a register of
your customers' current addresses.

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

--8w3uRX/HFJGApMzv
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFGw02mcXeLeWu2vmoRAsNTAKCz9FgD3K4jUWwV/leZB3B1Ah6DBwCgusmv
Culefni6CeIRZMEiMLZ92OU=
=6FAe
-----END PGP SIGNATURE-----

--8w3uRX/HFJGApMzv--


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

--===============1743065560==--




From dhcwg-bounces@ietf.org Thu Aug 16 04:57:39 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILb8v-0003QN-48; Thu, 16 Aug 2007 04:55:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILb8t-0003QF-IA; Thu, 16 Aug 2007 04:55:47 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILb8s-0007JD-Ln; Thu, 16 Aug 2007 04:55:47 -0400
Received: from jmb.local (unknown [IPv6:2001:200:1b1:101a:217:f2ff:fe26:34a0])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id BBE2373021;
	Thu, 16 Aug 2007 17:55:44 +0900 (JST)
Date: Thu, 16 Aug 2007 17:55:39 +0900
Message-ID: <m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: "David W. Hankins" <David_Hankins@isc.org>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
In-Reply-To: <20070815175140.GC18683@isc.org>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.0 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: -0.0 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: dhcwg@ietf.org, ipv6@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

At Wed, 15 Aug 2007 10:51:40 -0700,
"David W. Hankins" <David_Hankins@isc.org> wrote:

> > > I think that you will find realistically, DHCPv6 servers will know
> > > prefix lengths.
> > 
> > None that I've worked with (including the WIDE server) seems to care.
> > What's needed are assignment ranges, not prefixes.
> 
> I'm familiar with half of the story here, and uncomfortable with
> speaking about a specific competitor's product (but it appears I will
> do it anyway).  My opinion of WIDE's Confirm message processing is
> that it does know the prefix length: it assumes all prefixes are /64,
> by comparing the first 8 bytes of addresses.
> 
> I make no judgement here of the efficacy or correctness of this
> implementation.
> 
> If there is an expert on WIDE's implementation that can describe how
> it reaches a dynamic pool from relays (without relays, it appears to
> follow interface definitions), I'm curious to know the rest of the
> story.

I'm not an "expert" on the WIDE implementation (any more), but I know
the implementation well enough that I can clarify the points, so...

Your understanding about the Confirm message processing of the WIDE
server is correct.  (And I don't think this way of handling Confirm is
really an appropriate behavior).

The WIDE server implementation doesn't care about the link prefix when
assigning an address from a pool.  This is also not an appropriate
behavior because it could assign an address that is not valid for the
link to which the client is attached.

So, I think you're right in that realistically the DHCPv6 server
operator needs to understand the link prefixes of the addresses
assigned via DHCPv6.  This also means the DHCPv6 server will
realistically be able to provide this information for the clients.
(The server might still work properly just based on the knowledge
about its own local links and on the content of 'link address'
information of relayed messages.  But such an operation does not seem
"realistic" to me).

But I don't think this immediately justifies the introduction of
an on-link prefix option to DHCPv6.  To rely on this feature, the
DHCPv6 operator would need to know all on-link prefixes including ones
that are not used for DHCP-based address assignment, and would need to
configure them on the server.  Although the additional overhead is
minor, it can still be an unnecessary operational cost and can cause
configuration inconsistency that could actually avoided.  On the other
hand, routers should inherently know the on-link prefix information to
route packets appropriately, so providing this information via RA
still looks better than the DHCP-based approach.

IMO, this discussion is going to miss the point.  The problem is not
whether we can provide on-link prefix information via DHCPv6 (yes we
can) or whether it's reasonable per se (it might), but whether we
should do this while RA already has this provision and would actually
be better than DHCPv6-based approach.  A new draft from the dhc group
will reportedly (hopefully?) answer this main question, so, again, I
think we should hold off for a while.

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

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



From dhcwg-bounces@ietf.org Thu Aug 16 09:06:13 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILf1e-0002qt-PZ; Thu, 16 Aug 2007 09:04:34 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILf1c-0002di-OY; Thu, 16 Aug 2007 09:04:32 -0400
Received: from sca-ea-mail-4.sun.com ([192.18.43.22])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1ILf1c-0006fl-2h; Thu, 16 Aug 2007 09:04:32 -0400
Received: from eastmail2bur.East.Sun.COM ([129.148.13.40])
	by sca-ea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l7GD4UmZ006728; Thu, 16 Aug 2007 13:04:31 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail2bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with
	ESMTP id l7GD4UUI020782; Thu, 16 Aug 2007 09:04:30 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l7GCrDPG104726; Thu, 16 Aug 2007 08:53:13 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l7GCrASb104723;
	Thu, 16 Aug 2007 08:53:10 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18116.18614.155935.470468@gargle.gargle.HOWL>
Date: Thu, 16 Aug 2007 08:53:10 -0400
From: James Carlson <james.d.carlson@sun.com>
To: "David W. Hankins" <David_Hankins@isc.org>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
In-Reply-To: <20070815175140.GC18683@isc.org>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: dhcwg@ietf.org, ipv6@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 writes:
> On Wed, Aug 15, 2007 at 10:33:16AM -0400, James Carlson wrote:
> > > and it needs to be able to Confirm the use of
> > > addresses, which it may not have allocated.
> > 
> > That doesn't make sense to me.  The DHCPv6 Confirm message is for
> > confirming an address lease.  If the server hasn't allocated the
> > lease, then it _cannot_ confirm anything about the address and must
> > Nak in response.  If it does confirm addresses it hasn't allocated,
> > then it's just broken.
> 
> I'm not sure where you got that idea - certainly not from RFC3315
> section 18.2.2 ("Receipt of Confirm Messages" under "Server
> Behavior").

I don't see how the server could possibly construct a valid Reply
message otherwise.  It needs to include IA Address options, and those
need to have preferred-lifetime and valid-lifetime.

I'd agree that the language seems incomplete.

> > > 	- Have a list of all the 'link-address' fields that all
> > > 	  operating DHCPv6 relays will use to identify a link.
> > 
> > I'm confused.  Why would relays be confirming anything?
> 
> I'm sorry - this is a DHCPv6 protocol mechanic, something only
> a DHCP geek would know.

You're pardoned.  I've only implemented one commercially-shipping
and deployed DHCPv6 client implementation.  ;-}

> The relay messages' 'link-address' field is central to the server's
> calculation of the client's location (which "broadcast domain"
> they're attached to).

The link-address is:

      link-address   A global or site-local address that will be used by
                     the server to identify the link on which the client
                     is located.

I expect that to be the relay's global IPv6 address on the link on
which the client is located, if there is such an address.

> Basically it's how you know which addresses are appropriate for the
> client, based on what network they're attached to.

It's how you (as a relay) know where the client is located so that you
can reach it again when the server sends back the responses.

The server itself _can_ use link-address to determine where in the
world the client is located, but that doesn't mean that the relay is
doing this validation (which is what I had thought you were saying),
and it also doesn't mean that the client itself is on the same prefix.

Note that link-address can be 0, if the relay doesn't have a global
address on that interface, and the server will have to choose a
different means to get the information it needs.  So, it's not an
absolute identifier of the prefix.

> Does that make more sense now?

Yes.

> > If you delegate a prefix, then you route to the prefix -- best match.
> 
> Yes, but how does that route get in the table, and what next-hop is
> set?  You have to know your customer's address eventually.

If there's a delegated prefix, I'd _assume_ that there's a router in
the way.  Otherwise, delegating a prefix is a little strange.

If there's a router in the way, then it's the router's link-local
address that you need, not the customers end-node assigned addresses.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From dhcwg-bounces@ietf.org Thu Aug 16 12:33:52 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILiGQ-0007IK-LD; Thu, 16 Aug 2007 12:32:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILiGP-0007IB-8h; Thu, 16 Aug 2007 12:32:01 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILiGO-0003Hr-2i; Thu, 16 Aug 2007 12:32:01 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 16 Aug 2007 12:32:00 -0400
X-IronPort-AV: i="4.19,272,1183348800"; 
	d="scan'208"; a="129053516:sNHT51350158"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7GGVx92022103; 
	Thu, 16 Aug 2007 12:31:59 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7GGVxjI005985; 
	Thu, 16 Aug 2007 16:31:59 GMT
Received: from xmb-rtp-205.amer.cisco.com ([64.102.31.59]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Aug 2007 12:31:59 -0400
Received: from mlinsnerwxp ([10.86.240.142]) by xmb-rtp-205.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Aug 2007 12:31:58 -0400
From: "Marc Linsner" <mlinsner@cisco.com>
To: <ecrit@ietf.org>, <dhcwg@ietf.org>
Date: Thu, 16 Aug 2007 12:31:57 -0400
Message-ID: <001501c7e022$f76e7670$8ef0560a@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
Thread-Index: AcfgIvQ6BSPSGXGERqmRjbfwceynrw==
X-OriginalArrivalTime: 16 Aug 2007 16:31:59.0080 (UTC)
	FILETIME=[F7981E80:01C7E022]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=557; t=1187281919;
	x=1188145919; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=mlinsner@cisco.com;
	z=From:=20=22Marc=20Linsner=22=20<mlinsner@cisco.com>
	|Subject:=20WGLC=3A=20A=20Dynamic=20Host=20Configuration=20Protocol=20(DH
	CP)=20based=20Location-to-Service=20Translation=20Protocol=20(LoST)=20Disc
	overy=20Procedure |Sender:=20
	|To:=20<ecrit@ietf.org>,=20<dhcwg@ietf.org>;
	bh=2XPr60G8EHhBJnjBkv2vlYULqZrEBPwFQJMa8TY+WaA=;
	b=T9QABsNeApApZawx8gY/eayEraJOY/1Mdf/9ayHWFzN8SXIsxK6DjnBEHF8oRiiNH4ZB5xtE
	IYXCYshHN5JCStxhEDFJvQNMj0IK1qjgnK0wYtVLu9wGpLaXoiUqlcVu;
Authentication-Results: rtp-dkim-1; header.From=mlinsner@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: 
Subject: [dhcwg] WGLC: A Dynamic Host Configuration Protocol (DHCP) based
	Location-to-Service Translation Protocol (LoST) Discovery Procedure
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

All,

This message marks the issuance of a working group last call (WGLC) on
ECRIT's Internet Draft entitled "A Dynamic Host Configuration Protocol
(DHCP) based Location-to-Service Translation Protocol (LoST) Discovery
Procedure" (draft-ietf-ecrit-dhc-lost-discovery-02.txt).  You may view this
document at
http://www.ietf.org/internet-drafts/draft-ietf-ecrit-dhc-lost-discovery-02.t
xt.

Please post comments and questions to the ECRIT (preferred) or DHC mailing
list no later than 31 August 2007.

Thank you,

Marc Linsner
ECRIT co-chair

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



From dhcwg-bounces@ietf.org Thu Aug 16 14:14:22 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILjpi-0007uK-1j; Thu, 16 Aug 2007 14:12:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILjph-0007tF-Bl; Thu, 16 Aug 2007 14:12:33 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILjpg-0007W9-J4; Thu, 16 Aug 2007 14:12:33 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id A4ED05A6E5; Thu, 16 Aug 2007 11:12:31 -0700 (PDT)
Date: Thu, 16 Aug 2007 11:12:31 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
Message-ID: <20070816181231.GF10179@isc.org>
References: <7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
	<18116.18614.155935.470468@gargle.gargle.HOWL>
Mime-Version: 1.0
In-Reply-To: <18116.18614.155935.470468@gargle.gargle.HOWL>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Cc: ipv6@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0787961533=="
Errors-To: dhcwg-bounces@ietf.org


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


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

On Thu, Aug 16, 2007 at 08:53:10AM -0400, James Carlson wrote:
> I don't see how the server could possibly construct a valid Reply
> message otherwise.  It needs to include IA Address options, and those

The server does not include IA_*'s nor IAADDRs beneath them.  It
only MUST include a server-identifier option, and a status code
option (although there's no normative text) specifying the status of
the Confirm operation.  18.2.2 again.

> need to have preferred-lifetime and valid-lifetime.

The client MUST include the IA_*'s, and any IAADDRs within them, with
the t1, t2, preferred and valid lifetimes all set to zero.  The
server MUST ignore these fields.  18.1.2 plus 18.2.2.


This is one of the unfortunate successes of DHCPv6.  RFC3315's
format is to create a section for the specific behaviours and
requirements for each message by message type, and to have states
clearly delineated with separate messages.  Compared to DHCPv4,
which only had 4 messages for 8 or so purposes and so required that
you keep track of a state engine while you read, this was a major
improvement.

But since 'Reply' is used to reply to multiple messages, and there are
fewer sections to cover it, this gives the text a very unusual
quality...it goes from very easy to very hard with no warning.

It's quite difficult to make heads or tails of what's goig on after
you finish with the Reply message sections.


> world the client is located, but that doesn't mean that the relay is
> doing this validation (which is what I had thought you were saying),

Yes, that's where we're not communicating - in the piece of text you
were replying to, I was describing a server behaviour based upon
information supplied by relay agents.

A relay is just a relay.

> Note that link-address can be 0, if the relay doesn't have a global
> address on that interface, and the server will have to choose a
> different means to get the information it needs.  So, it's not an
> absolute identifier of the prefix.

I think this is something we talked about at the DHCPv6 bakeoff
possibly needing some clarification.  That's another draft I
anticipate reading.

Basically, absent of some "special guidance from the admin", the
anticipation is that you start from the 'clientmost' end of the
relay-forward chain, and move 'servermost' iteratively until
you find a nonzero value (this can be done in reverse while
seeking down the chain to the client's packet to process it).

If you do find a nonzero value, you use that to find the broadcast
domain (and then valid addresses somehow).

If you do not find a nonzero value, then the client is located on
the same broadcast domain as the interface upon which the server
received the packet, and you give addresses valid for that domain.

In either case if the operator has told you what you should do, you
should just do that.

The link-address field is absolutely the identifier of the broadcast
domain, which corresponds therefore to one or more prefixes.  The
administrator's will as expressed in configuration syntax is an
ultimate identifier.


I think what we decided (and what seemed to be the Prague consensus)
was that this could use some clarification.

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

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

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

iD8DBQFGxJOPcXeLeWu2vmoRAobNAJ9F6ff+rECtwJwkJ0ozr3lv849LQgCgmkg5
3/Kn8Bh4mz2vNb6eNKZ0gRA=
=G6Ga
-----END PGP SIGNATURE-----

--UnaWdueM1EBWVRzC--


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

--===============0787961533==--




From dhcwg-bounces@ietf.org Thu Aug 16 14:54:33 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILkSc-0000Dw-EM; Thu, 16 Aug 2007 14:52:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILkSZ-00005i-Q3; Thu, 16 Aug 2007 14:52:43 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILkSZ-0000Ed-58; Thu, 16 Aug 2007 14:52:43 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 7CA945A6E5; Thu, 16 Aug 2007 11:52:42 -0700 (PDT)
Date: Thu, 16 Aug 2007 11:52:42 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
Message-ID: <20070816185242.GG10179@isc.org>
References: <7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
Mime-Version: 1.0
In-Reply-To: <m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: ipv6@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1434277018=="
Errors-To: dhcwg-bounces@ietf.org


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


--4f28nU6agdXSinmL
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Aug 16, 2007 at 05:55:39PM +0900, JINMEI Tatuya / =E7=A5=9E=E6=98=
=8E=E9=81=94=E5=93=89 wrote:
> I'm not an "expert" on the WIDE implementation (any more), but I know
> the implementation well enough that I can clarify the points, so...
>=20
> Your understanding about the Confirm message processing of the WIDE
> server is correct.  (And I don't think this way of handling Confirm is
> really an appropriate behavior).

I think the authors also placed a "XXX" comment on the relevant
sources, so there appears to be some agreement with you there.

But it's not like I'm not guilty of the same thing sometimes.

> The WIDE server implementation doesn't care about the link prefix when
> assigning an address from a pool.  This is also not an appropriate
> behavior because it could assign an address that is not valid for the
> link to which the client is attached.

Thank you Jinmei, my curiosity is sated.

So my understanding is that it chooses addresses to allocate based
upon which interface it received the message on.

> IMO, this discussion is going to miss the point.

My intent is to clear up what I perceive to be technical errors
(others' or my own), not to argue the main points.

If there's some overlap, real or perceived, that is my error.

--=20
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil?	 https://secure.isc.org/store/t-shirt/
--=20
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins

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

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

iD8DBQFGxJz6cXeLeWu2vmoRAkeLAJ0WZ4V0LKPeRmW79ALCVXXO2JKrzwCgrCAk
E9d1rxjXAmAU0gOtbQbFRMo=
=/i8R
-----END PGP SIGNATURE-----

--4f28nU6agdXSinmL--


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

--===============1434277018==--




From dhcwg-bounces@ietf.org Thu Aug 16 18:44:18 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILo2w-0002qW-Ol; Thu, 16 Aug 2007 18:42:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILo2u-0002qG-Je; Thu, 16 Aug 2007 18:42:28 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1ILo2u-0007d4-4u; Thu, 16 Aug 2007 18:42:28 -0400
Received: from [82.192.90.28] (nirrti.muada.com [82.192.90.28])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l7GMdkbb093232
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Fri, 17 Aug 2007 00:39:47 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com><7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com><8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com><18113.42485.158453.756815@gargle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.103258@gargle.gargle.HOWL><20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
Date: Fri, 17 Aug 2007 00:41:55 +0200
To: Hemant Singh (shemant) <shemant@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: ipv6@ietf.org, dhcwg@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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 16-aug-2007, at 21:35, Hemant Singh (shemant) wrote:

> RA supports all
> of prefix information and on-link determination, so why have DHCPv6
> duplicate that functionality?

That's not the discussion we were having. The discussion we were  
having (or at least, _I_ was having) was whether it's a good idea to  
have a prefix LENGTH go along with the IPv6 address if a DHCPv6  
server assigns an IPv6 address to a host.

In my opinion, the answer is "of course" because otherwise life gets  
quite complex, but apparently there are people who like that kind of  
thing and who feel that an address with an unknown prefix length is  
useful.

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



From dhcwg-bounces@ietf.org Thu Aug 16 18:53:45 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILoC6-0002sS-Vt; Thu, 16 Aug 2007 18:51:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILoC6-0002sK-Ec; Thu, 16 Aug 2007 18:51:58 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILoC5-0006a8-56; Thu, 16 Aug 2007 18:51:58 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 16 Aug 2007 18:51:34 -0400
X-IronPort-AV: i="4.19,273,1183348800"; 
	d="scan'208"; a="129086277:sNHT59727009258"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7GMpZw0002250; 
	Thu, 16 Aug 2007 18:51:35 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7GMpUjI011514; 
	Thu, 16 Aug 2007 22:51:31 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Aug 2007 18:51: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] Re: prefix length determination for DHCPv6
Date: Thu, 16 Aug 2007 18:51:29 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Re: prefix length determination for DHCPv6
Thread-Index: AcfgVr3HswA41vklRzqUNdh8QK3tdQAAGN0g
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com><7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com><8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com><18113.42485.158453.756815@gargle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.103258@gargle.gargle.HOWL><20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
	<FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>
X-OriginalArrivalTime: 16 Aug 2007 22:51:30.0690 (UTC)
	FILETIME=[FC880E20:01C7E057]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1558; t=1187304695;
	x=1188168695; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20[dhcwg]=20Re=3A=20prefix=20length=20determination=20f
	or=20DHCPv6 |Sender:=20
	|To:=20=22Iljitsch=20van=20Beijnum=22=20<iljitsch@muada.com>;
	bh=AFzmqvzd0kqqNjwJ+tET5EheFPCIcHJrwKyAt5juNck=;
	b=ikyKGhoB9QW4goHrV4QDSSRzrcGYJkgfp5kX5CB86hLMtQGKe/KYIkiwb4GmnU1qhnFjLVQ0
	WALRctzUuKZZHjDDPzAygYjqjnTO5zqYEY/cRenh7AhG+iarsRUfF0KC;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: ipv6@ietf.org, dhcwg@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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

OK, Iljitsch. But hasn't Bernie already responded to this one? What if
prefix length is fat-fingered at the DHCPv6 server by the admin and a
length L1 is sent in DHCPv6 messages but the router RA sent a PIO for
the same prefix with prefix length L2. So as Bernie says, who wins? What
does the host now do?

Further, isn't sending prefix length in DHCPv6 messages duplicating what
RA PIO prefix length field already is capable of doing?

Lastly, what huge problem is sending prefix length in DHCPv6 messages
going to solve that is not solved by ND RA, RA PIO, and existing DHCPv6?

Hemant
=20

-----Original Message-----
From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]=20
Sent: Thursday, August 16, 2007 6:42 PM
To: Hemant Singh (shemant)
Cc: JINMEI Tatuya / ????; David W. Hankins; dhcwg@ietf.org;
ipv6@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6

On 16-aug-2007, at 21:35, Hemant Singh (shemant) wrote:

> RA supports all
> of prefix information and on-link determination, so why have DHCPv6=20
> duplicate that functionality?

That's not the discussion we were having. The discussion we were having
(or at least, _I_ was having) was whether it's a good idea to have a
prefix LENGTH go along with the IPv6 address if a DHCPv6 server assigns
an IPv6 address to a host.

In my opinion, the answer is "of course" because otherwise life gets
quite complex, but apparently there are people who like that kind of
thing and who feel that an address with an unknown prefix length is
useful.

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



From dhcwg-bounces@ietf.org Thu Aug 16 19:10:52 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILoSh-0000pJ-Qh; Thu, 16 Aug 2007 19:09:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILoSf-0000oz-Oe; Thu, 16 Aug 2007 19:09:05 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILoSe-000742-8y; Thu, 16 Aug 2007 19:09:05 -0400
Received: from [82.192.90.28] (nirrti.muada.com [82.192.90.28])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l7GN5QwR093670
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Fri, 17 Aug 2007 01:05:27 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com><7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com><8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com><18113.42485.158453.756815@gargle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.103258@gargle.gargle.HOWL><20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
	<FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
Date: Fri, 17 Aug 2007 01:07:35 +0200
To: Hemant Singh (shemant) <shemant@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: ipv6@ietf.org, dhcwg@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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 17-aug-2007, at 0:51, Hemant Singh (shemant) wrote:

> OK, Iljitsch. But hasn't Bernie already responded to this one? What if
> prefix length is fat-fingered at the DHCPv6 server by the admin and a
> length L1 is sent in DHCPv6 messages but the router RA sent a PIO for
> the same prefix with prefix length L2. So as Bernie says, who wins?  
> What
> does the host now do?

(Can't seem to remember what PIO stands for...)

What if someone misconfigures the dot zone file and the entire DNS  
goes down?

Mistakes happen. There is no cure for stupidity. Etc, and so on, ad  
nauseum.

The problem that I have is that if an address without a prefix length  
becomes available, what do I do? Then I need to do different things  
depending on what other information is available and redo all of this  
when new information becomes available. It's a mess.

If a DHCPv6 server tells me I have address 2003::2003/68 and then I  
get a router advertisement with a prefix option for 2003::/60 then I  
know that both 2003::/68 and 2003::/60 are directly connected to my  
interface. That the two happen to overlap is somewhat curious, but  
otherwise no big deal.

I.e., in practice, the shortest prefix "wins".

> Further, isn't sending prefix length in DHCPv6 messages duplicating  
> what
> RA PIO prefix length field already is capable of doing?

Since when is there a requirement that a piece of information may not  
be learned through two ways independently?

The point is that if a DHCPv6 server gives out addresses without a  
prefix lenght, it only does half a job. Sure, you can let another  
protocol pick up the slack and in theory that may not seem like a  
problem, but the trouble is that in practice, different protocols run  
and possibly fail at different times so the permutations increase  
rapidly while if you just put it in the DHCPv6 message and get it  
over with, life is simple and we can all go home early.

> Lastly, what huge problem is sending prefix length in DHCPv6 messages
> going to solve that is not solved by ND RA, RA PIO, and existing  
> DHCPv6?

Not a thing until someone is going to start USING DHCPv6 address  
assignment, I'd say.

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



From dhcwg-bounces@ietf.org Thu Aug 16 19:40:19 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILovC-0007IM-Tz; Thu, 16 Aug 2007 19:38:34 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILovB-0007IE-U9; Thu, 16 Aug 2007 19:38:34 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1ILovB-0001BZ-7V; Thu, 16 Aug 2007 19:38:33 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 16 Aug 2007 19:38:32 -0400
X-IronPort-AV: i="4.19,273,1183348800"; 
	d="scan'208"; a="68214042:sNHT67386580"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7GNcWso031342; 
	Thu, 16 Aug 2007 19:38:32 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l7GNcUmd001501; 
	Thu, 16 Aug 2007 23:38:30 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Aug 2007 19:38: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] Re: prefix length determination for DHCPv6
Date: Thu, 16 Aug 2007 19:38:29 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Re: prefix length determination for DHCPv6
Thread-Index: AcfgWkP2OYmN5RhnSJCi4zcUGa25SAAAeigg
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com><7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com><8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com><18113.42485.158453.756815@gargle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.103258@gargle.gargle.HOWL><20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
	<FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
	<8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>
X-OriginalArrivalTime: 16 Aug 2007 23:38:30.0120 (UTC)
	FILETIME=[8D0AEE80:01C7E05E]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4147; t=1187307512;
	x=1188171512; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20[dhcwg]=20Re=3A=20prefix=20length=20determination=20f
	or=20DHCPv6 |Sender:=20
	|To:=20=22Iljitsch=20van=20Beijnum=22=20<iljitsch@muada.com>;
	bh=532k/Yu1Yctkeh4sYjvWy0ny8nxmUkJwh0x9/zkhV8s=;
	b=l3oPGHwqL3tVTsmVMORxskpW3zKu4qejAX9RUDmk2Ld2VAMB9AXMvKIyHN8F3SzAiXfPu7cT
	jfPmzr9zUWq/4Ar4yWzgxqm1MRu5aIkwmyFHARIhtyC4A+Pn6u7ykRON;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: ipv6@ietf.org, dhcwg@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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

PIO is Prefix Information Option of RA. Let me reply to your comments
one by one.

Grossly speaking, I disagree with you on most counts.

>The problem that I have is that if an address without a prefix length
becomes available, what do I do?
=20
How can that happen with a DHCPv6 host? RA will always precede DHCPv6
transactions because unless the host sees an RA with M bit set the host
will not initiate DHCPv6. Such a RA can include a prefix and prefix
length in PIO. If RA doesn't include any PIO, then the host still
initiates DHCPv6, completes DHCPv6 and then sends all non-link-local
traffic to the default router and wait for any Redirects.

>Sure, you can let another protocol pick up the slack and in theory that
may not seem like a problem, but the trouble is that in practice,
different=20
>protocols run and possibly fail at different times so the permutations
increase rapidly while if you just put it in the DHCPv6 message and get
it over=20
>with, life is simple and we can all go home early.

All generic talk. Let's say if RA fails, then the host will never get a
signal to initiate DHCPv6. What random failures are you talking about. I
am not buying any random failures and any permutations just yet.

>Not a thing until someone is going to start USING DHCPv6 address
assignment, I'd say.

OK, I deployed DHCPv6 address assignment today. Start listing show
stopper problems to me. If you feel so strongly about it, put the show
stopper problems in an Internet-Draft document so we have all the issues
captured and not have to sift thru zillion emails that could go off to a
tangent.=20

Hemant

-----Original Message-----
From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]=20
Sent: Thursday, August 16, 2007 7:08 PM
To: Hemant Singh (shemant)
Cc: JINMEI Tatuya / ????; David W. Hankins; dhcwg@ietf.org;
ipv6@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6

On 17-aug-2007, at 0:51, Hemant Singh (shemant) wrote:

> OK, Iljitsch. But hasn't Bernie already responded to this one? What if

> prefix length is fat-fingered at the DHCPv6 server by the admin and a=20
> length L1 is sent in DHCPv6 messages but the router RA sent a PIO for=20
> the same prefix with prefix length L2. So as Bernie says, who wins?
> What
> does the host now do?

(Can't seem to remember what PIO stands for...)

What if someone misconfigures the dot zone file and the entire DNS goes
down?

Mistakes happen. There is no cure for stupidity. Etc, and so on, ad
nauseum.

The problem that I have is that if an address without a prefix length
becomes available, what do I do? Then I need to do different things
depending on what other information is available and redo all of this
when new information becomes available. It's a mess.

If a DHCPv6 server tells me I have address 2003::2003/68 and then I get
a router advertisement with a prefix option for 2003::/60 then I know
that both 2003::/68 and 2003::/60 are directly connected to my
interface. That the two happen to overlap is somewhat curious, but
otherwise no big deal.

I.e., in practice, the shortest prefix "wins".

> Further, isn't sending prefix length in DHCPv6 messages duplicating=20
> what RA PIO prefix length field already is capable of doing?

Since when is there a requirement that a piece of information may not be
learned through two ways independently?

The point is that if a DHCPv6 server gives out addresses without a
prefix lenght, it only does half a job. Sure, you can let another
protocol pick up the slack and in theory that may not seem like a
problem, but the trouble is that in practice, different protocols run
and possibly fail at different times so the permutations increase
rapidly while if you just put it in the DHCPv6 message and get it over
with, life is simple and we can all go home early.

> Lastly, what huge problem is sending prefix length in DHCPv6 messages=20
> going to solve that is not solved by ND RA, RA PIO, and existing=20
> DHCPv6?

Not a thing until someone is going to start USING DHCPv6 address
assignment, I'd say.

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



From dhcwg-bounces@ietf.org Fri Aug 17 01:41:44 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILuYu-0003km-9D; Fri, 17 Aug 2007 01:39:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILuYs-0003kb-I1
	for dhcwg@ietf.org; Fri, 17 Aug 2007 01:39:54 -0400
Received: from mail153.messagelabs.com ([216.82.253.51])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1ILuYs-0003Ga-2t
	for dhcwg@ietf.org; Fri, 17 Aug 2007 01:39:54 -0400
X-VirusChecked: Checked
X-Env-Sender: Q4997C@motorola.com
X-Msg-Ref: server-9.tower-153.messagelabs.com!1187329192!5437308!1
X-StarScan-Version: 5.5.12.11; banners=-,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 3498 invoked from network); 17 Aug 2007 05:39:52 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-9.tower-153.messagelabs.com with SMTP;
	17 Aug 2007 05:39:52 -0000
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l7H5dqUL011709
	for <dhcwg@ietf.org>; Thu, 16 Aug 2007 22:39:52 -0700 (MST)
Received: from il06vts04.mot.com (il06vts04.mot.com [129.188.137.144])
	by il06exr01.mot.com (8.13.5/Vontu) with SMTP id l7H5dpgh016719
	for <dhcwg@ietf.org>; Fri, 17 Aug 2007 00:39:52 -0500 (CDT)
Received: from ZMY16EXM66.ds.mot.com (zmy16exm66.ap.mot.com [10.179.4.26])
	by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id l7H5dnqg016697
	for <dhcwg@ietf.org>; Fri, 17 Aug 2007 00:39:50 -0500 (CDT)
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, 17 Aug 2007 13:39:48 +0800
Message-ID: <750BBC72E178114F9DC4872EBFF29A5B04E72DC8@ZMY16EXM66.ds.mot.com>
In-Reply-To: <20070816181231.GF10179@isc.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: use of dhcp3.0.6
thread-index: AcfgMQ2k2wEfSh7fRvGaQBWOutbhtAAX1nlg
From: "Aggarwal Vivek-Q4997C" <Q4997C@motorola.com>
To: <dhcwg@ietf.org>, <dhcp-users@isc.org>
X-Vontu: Pass
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: 
Subject: [dhcwg] use of dhcp3.0.6
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

Im having LINUX ES verion 4 system.

I downloaded source file dhcp-3.0.6.tar.gz from the isc site.

How can I make dhcp3.0.6 work on my system , is it possible or not

Firstly I downloaded and copied the file to the root dir

Did tar then ./configure, nut Im unable make it
It says make 1 error all

Can you please help in the matter

Basically I want to use dhcp-3.0.6 on RedHat ES Version 4, How can I do
that


Regards
Vivek Aggarwal

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



From dhcwg-bounces@ietf.org Fri Aug 17 05:48:27 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILyPe-00011p-87; Fri, 17 Aug 2007 05:46:38 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILyPc-00011a-HL; Fri, 17 Aug 2007 05:46:36 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1ILyPb-0001FY-UH; Fri, 17 Aug 2007 05:46:36 -0400
Received: from [82.192.90.28] (nirrti.muada.com [82.192.90.28])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l7H9iFGS003324
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Fri, 17 Aug 2007 11:44:17 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com><7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com><8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com><18113.42485.158453.756815@gargle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.103258@gargle.gargle.HOWL><20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
	<FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
	<8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <80301DB1-B5F2-4F92-834C-0914FD522B95@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
Date: Fri, 17 Aug 2007 11:46:24 +0200
To: Hemant Singh (shemant) <shemant@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: ipv6@ietf.org, dhcwg@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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 17-aug-2007, at 1:38, Hemant Singh (shemant) wrote:

>> The problem that I have is that if an address without a prefix length
> becomes available, what do I do?

> How can that happen with a DHCPv6 host? RA will always precede DHCPv6
> transactions because unless the host sees an RA with M bit set the  
> host
> will not initiate DHCPv6.

Sure, the information will be there MOST of the time, but it's not  
hard to come up with ways in which it won't be there.

> Such a RA can include a prefix and prefix
> length in PIO. If RA doesn't include any PIO, then the host still
> initiates DHCPv6, completes DHCPv6 and then sends all non-link-local
> traffic to the default router and wait for any Redirects.

And how is this a better way to operate than to have that prefix  
length in the DHCP message?

>> Not a thing until someone is going to start USING DHCPv6 address  
>> assignment, I'd say.

> OK, I deployed DHCPv6 address assignment today.

Well then, what happens if the DHCPv6 server gives out an address and  
the router doesn't supply prefix information for the prefix that  
address falls into? I'm not saying this will happen every day, just  
interested to learn how the implementation that you use handles this.

> Start listing show
> stopper problems to me. If you feel so strongly about it, put the show
> stopper problems in an Internet-Draft document so we have all the  
> issues
> captured and not have to sift thru zillion emails that could go off  
> to a
> tangent.

Sorry, that's too much work. I can write an email message in a few  
minutes, a draft takes hours of overhead getting all the boilerplate  
and formatting right and then it takes a week before it's published.

Also, few people tend to read random drafts, so it's not an efficient  
way to communicate a simple point.

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



From dhcwg-bounces@ietf.org Fri Aug 17 10:02:04 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM2N3-0001Se-7G; Fri, 17 Aug 2007 10:00:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM2N2-0001SV-9D; Fri, 17 Aug 2007 10:00:12 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IM2N1-0004sr-1i; Fri, 17 Aug 2007 10:00:12 -0400
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l7HE01ge012538
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 17 Aug 2007 09:00:02 -0500 (CDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l7HE01Yr012531; Fri, 17 Aug 2007 07:00:01 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l7HDxxqm012424; Fri, 17 Aug 2007 07:00:00 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 06:59:56 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
Date: Fri, 17 Aug 2007 06:59:56 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Re: prefix length determination for DHCPv6
Thread-Index: AcfgWkP2OYmN5RhnSJCi4zcUGa25SAAAeiggAB6NJEA=
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com><7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com><8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com><18113.42485.158453.756815@gargle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.103258@gargle.gargle.HOWL><20070815175140.GC18683@isc.org><m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com><FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com><B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com><8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>,
	"Iljitsch van Beijnum" <iljitsch@muada.com>
X-OriginalArrivalTime: 17 Aug 2007 13:59:56.0678 (UTC)
	FILETIME=[E4A1CA60:01C7E0D6]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Cc: dhcwg@ietf.org, ipv6@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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

> How can that happen with a DHCPv6 host? RA will always precede DHCPv6
> transactions because unless the host sees an RA with M bit set the
host
> will not initiate DHCPv6.

That doesn't make much sense; if a node doesn't hear
RAs, why wouldn't it try DHCPv6 before giving up?

Fred
fred.l.templin@boeing.com

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



From dhcwg-bounces@ietf.org Fri Aug 17 11:29:26 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM3jh-0007CP-OQ; Fri, 17 Aug 2007 11:27:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM3jf-0007Bv-Qh; Fri, 17 Aug 2007 11:27:39 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IM3je-00082P-Gc; Fri, 17 Aug 2007 11:27:39 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 17 Aug 2007 11:27:22 -0400
X-IronPort-AV: i="4.19,275,1183348800"; 
	d="scan'208"; a="68274517:sNHT41013249780"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7HFRN1v002442; 
	Fri, 17 Aug 2007 11:27:23 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l7HFREmx012986; 
	Fri, 17 Aug 2007 15:27:20 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 11:26:43 -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] Re: prefix length determination for DHCPv6
Date: Fri, 17 Aug 2007 11:26:42 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D038814CF@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Re: prefix length determination for DHCPv6
Thread-Index: AcfgWkP2OYmN5RhnSJCi4zcUGa25SAAAeiggAB6NJEAAAw1iwA==
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com><7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com><8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com><18113.42485.158453.756815@gargle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.103258@gargle.gargle.HOWL><20070815175140.GC18683@isc.org><m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com><FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com><B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com><8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>,
	"Iljitsch van Beijnum" <iljitsch@muada.com>
X-OriginalArrivalTime: 17 Aug 2007 15:26:43.0443 (UTC)
	FILETIME=[041B1430:01C7E0E3]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=858; t=1187364443;
	x=1188228443; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20[dhcwg]=20Re=3A=20prefix=20length=20determination=20f
	or=20DHCPv6 |Sender:=20
	|To:=20=22Templin, =20Fred=20L=22=20<Fred.L.Templin@boeing.com>,
	=0A=20=20=
	20=20=20=20=20=20=22Iljitsch=20van=20Beijnum=22=20<iljitsch@muada.com>; 
	bh=xvlPuORcKF5RKi7A8Vm0NhTORYYqA4uP8s073GQMDWI=;
	b=omnKmJUxMcujEYcx+bM99t0x3q+FJucHkEaBoBKPWJ9dzr1308uSgrbjJ9K3ZXFd3HnF093i
	0pAxOyT481tc/QqpqlLQotf2FaqcaJwRSBhqp3chDjnzEperXtt5d91p;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: dhcwg@ietf.org, ipv6@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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

Fred,

I have not found any information in the ND RFC's nor DHCPv6 RFC that say
a node can initiate DHCPv6 if node doesn't receive any RA. I need to see
explicit text in some document to accept what you said below.

Hemant

-----Original Message-----
From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]=20
Sent: Friday, August 17, 2007 10:00 AM
To: Hemant Singh (shemant); Iljitsch van Beijnum
Cc: ipv6@ietf.org; dhcwg@ietf.org; JINMEI Tatuya / ????
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6

> How can that happen with a DHCPv6 host? RA will always precede DHCPv6=20
> transactions because unless the host sees an RA with M bit set the
host
> will not initiate DHCPv6.

That doesn't make much sense; if a node doesn't hear RAs, why wouldn't
it try DHCPv6 before giving up?

Fred
fred.l.templin@boeing.com

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



From dhcwg-bounces@ietf.org Fri Aug 17 11:33:59 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM3o7-0000xL-17; Fri, 17 Aug 2007 11:32:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM3o6-0000wB-5V; Fri, 17 Aug 2007 11:32:14 -0400
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IM3o4-0008B7-SU; Fri, 17 Aug 2007 11:32:14 -0400
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l7HFW0YZ019537
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 17 Aug 2007 08:32:00 -0700 (PDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1])
	by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l7HFW0nI016621; Fri, 17 Aug 2007 08:32:00 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l7HFVulv016451; Fri, 17 Aug 2007 08:32:00 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 08:31:58 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
Date: Fri, 17 Aug 2007 08:31:48 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED9C8@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D038814CF@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Re: prefix length determination for DHCPv6
Thread-Index: AcfgWkP2OYmN5RhnSJCi4zcUGa25SAAAeiggAB6NJEAAAw1iwAAAKMzg
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com><7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com><8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com><18113.42485.158453.756815@gargle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.103258@gargle.gargle.HOWL><20070815175140.GC18683@isc.org><m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com><FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com><B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com><8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038814CF@xmb-rtp-20e.amer.cisco.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>,
	"Iljitsch van Beijnum" <iljitsch@muada.com>
X-OriginalArrivalTime: 17 Aug 2007 15:31:58.0756 (UTC)
	FILETIME=[C00C0640:01C7E0E3]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: dhcwg@ietf.org, ipv6@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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 have not found any information in the ND RFC's nor DHCPv6 RFC that
say
> a node can initiate DHCPv6 if node doesn't receive any RA. I need to
see
> explicit text in some document to accept what you said below.

Is there a MUST NOT somewhere that I am missing?

Fred
fred.l.templin@boeing.com
=20
> Hemant
>=20
> -----Original Message-----
> From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com]=20
> Sent: Friday, August 17, 2007 10:00 AM
> To: Hemant Singh (shemant); Iljitsch van Beijnum
> Cc: ipv6@ietf.org; dhcwg@ietf.org; JINMEI Tatuya / ????
> Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
>=20
> > How can that happen with a DHCPv6 host? RA will always=20
> precede DHCPv6=20
> > transactions because unless the host sees an RA with M bit set the
> host
> > will not initiate DHCPv6.
>=20
> That doesn't make much sense; if a node doesn't hear RAs, why wouldn't
> it try DHCPv6 before giving up?
>=20
> Fred
> fred.l.templin@boeing.com
>=20

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



From dhcwg-bounces@ietf.org Fri Aug 17 12:14:23 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM4RB-00044V-6p; Fri, 17 Aug 2007 12:12:37 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM4R8-00044F-Ms; Fri, 17 Aug 2007 12:12:34 -0400
Received: from sca-ea-mail-1.sun.com ([192.18.43.24])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IM4R3-0004fZ-Tk; Fri, 17 Aug 2007 12:12:34 -0400
Received: from eastmail2bur.East.Sun.COM ([129.148.13.40])
	by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id
	l7HGCShN012867; Fri, 17 Aug 2007 16:12:29 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail2bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with
	ESMTP id l7HGCSS2005658; Fri, 17 Aug 2007 12:12:28 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l7HFnog0109365; Fri, 17 Aug 2007 11:49:50 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l7HFnR19109360;
	Fri, 17 Aug 2007 11:49:27 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18117.50055.237218.334936@gargle.gargle.HOWL>
Date: Fri, 17 Aug 2007 11:49:27 -0400
From: James Carlson <james.d.carlson@sun.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D038814CF@xmb-rtp-20e.amer.cisco.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
	<FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
	<8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038814CF@xmb-rtp-20e.amer.cisco.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: dhcwg@ietf.org, "Templin, Fred L" <Fred.L.Templin@boeing.com>,
	Iljitsch van Beijnum <iljitsch@muada.com>, ipv6@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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

Hemant Singh (shemant) writes:
> I have not found any information in the ND RFC's nor DHCPv6 RFC that say
> a node can initiate DHCPv6 if node doesn't receive any RA. I need to see
> explicit text in some document to accept what you said below.

It does say this.  See RFC 2462 section 4:

   The next phase of autoconfiguration involves obtaining a Router
   Advertisement or determining that no routers are present. If routers
   are present, they will send Router Advertisements that specify what
   sort of autoconfiguration a host should do.  If no routers are
   present, stateful autoconfiguration should be invoked.

And then more forcefully in 5.5.2:

5.5.2.  Absence of Router Advertisements

   If a link has no routers, a host MUST attempt to use stateful
   autoconfiguration to obtain addresses and other configuration
   information. An implementation MAY provide a way to disable the
   invocation of stateful autoconfiguration in this case, but the
   default SHOULD be enabled.  From the perspective of
   autoconfiguration, a link has no routers if no Router Advertisements
   are received after having sent a small number of Router Solicitations
   as described in [DISCOVERY].

It's certainly pointless unless you also have access to some static
prefix information, but it's what the documents say to do.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From dhcwg-bounces@ietf.org Fri Aug 17 12:25:56 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM4cM-0000QJ-Gj; Fri, 17 Aug 2007 12:24:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM4cL-0000NK-65; Fri, 17 Aug 2007 12:24:09 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IM4cJ-0001Wh-Vf; Fri, 17 Aug 2007 12:24:09 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 17 Aug 2007 12:24:07 -0400
X-IronPort-AV: i="4.19,276,1183348800"; 
	d="scan'208"; a="68281233:sNHT68485630"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7HGO7fO012137; 
	Fri, 17 Aug 2007 12:24:07 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l7HGNHml004796; 
	Fri, 17 Aug 2007 16:24:05 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 12:23:55 -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] Re: prefix length determination for DHCPv6
Date: Fri, 17 Aug 2007 12:23:54 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D03881506@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <18117.50055.237218.334936@gargle.gargle.HOWL>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Re: prefix length determination for DHCPv6
Thread-Index: Acfg6GBDi124Ma9HSAS0Hm/94Q0UfgAAF6PA
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com><7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com><8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com><18113.42485.158453.756815@gargle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.103258@gargle.gargle.HOWL><20070815175140.GC18683@isc.org><m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com><FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com><B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com><8706B8AE-001D-4403-A387-5255F67557F4@muada.com><B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com><B00EDD615E3C5344B0FFCBA910CF7E1D038814CF@xmb-rtp-20e.amer.cisco.com>
	<18117.50055 .237218.334936@gargle.gargle.HOWL>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "James Carlson" <james.d.carlson@sun.com>
X-OriginalArrivalTime: 17 Aug 2007 16:23:55.0546 (UTC)
	FILETIME=[01CC6FA0:01C7E0EB]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2634; t=1187367847;
	x=1188231847; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20[dhcwg]=20Re=3A=20prefix=20length=20determination=20f
	or=20DHCPv6 |Sender:=20
	|To:=20=22James=20Carlson=22=20<james.d.carlson@sun.com>;
	bh=odkycxaHZI5W3j64QPG/mxL8yhHbdUXwXkBcuaHk0Ts=;
	b=BnJFfR7dD3CU1j42SVYo9cpfEuMewlYmgYqgWEI6frvtKGrdHNIgASQ+QAfHE1r3rrnad7AC
	nbS1zBt6+IFTppbybUYTOLeXjmV+ByeXuUIaNWpV3TwWxuRLAsM5jnUC;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: dhcwg@ietf.org, "Templin, Fred L" <Fred.L.Templin@boeing.com>,
	Iljitsch van Beijnum <iljitsch@muada.com>, ipv6@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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

Thanks, James. I agree with Fred then that a node can try DHCPv6. But
now how does the node get a prefix length? As you are saying, some
manual or static configuration can be used. I certainly don't like the
host to assume any prefix length in this scenario. Since I am not a fan
of any manual configuration, it does make sense, only for such a case of
absence of an RA, that DHCPv6 provides prefix length. Since DHCPv6
doesn't know if the network's router will issue RA's or not, then DHCPv6
has to provide prefix length all the time.

Then I am for what Iljitsch is saying. If a host see a discrepancy in
prefix lengths from RA and DHCPv6, then host has to decide based on a
union of information.

Hemant=20

-----Original Message-----
From: James Carlson [mailto:james.d.carlson@sun.com]=20
Sent: Friday, August 17, 2007 11:49 AM
To: Hemant Singh (shemant)
Cc: Templin, Fred L; Iljitsch van Beijnum; dhcwg@ietf.org;
ipv6@ietf.org; JINMEI Tatuya / ????
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6

Hemant Singh (shemant) writes:
> I have not found any information in the ND RFC's nor DHCPv6 RFC that=20
> say a node can initiate DHCPv6 if node doesn't receive any RA. I need=20
> to see explicit text in some document to accept what you said below.

It does say this.  See RFC 2462 section 4:

   The next phase of autoconfiguration involves obtaining a Router
   Advertisement or determining that no routers are present. If routers
   are present, they will send Router Advertisements that specify what
   sort of autoconfiguration a host should do.  If no routers are
   present, stateful autoconfiguration should be invoked.

And then more forcefully in 5.5.2:

5.5.2.  Absence of Router Advertisements

   If a link has no routers, a host MUST attempt to use stateful
   autoconfiguration to obtain addresses and other configuration
   information. An implementation MAY provide a way to disable the
   invocation of stateful autoconfiguration in this case, but the
   default SHOULD be enabled.  From the perspective of
   autoconfiguration, a link has no routers if no Router Advertisements
   are received after having sent a small number of Router Solicitations
   as described in [DISCOVERY].

It's certainly pointless unless you also have access to some static
prefix information, but it's what the documents say to do.

--=20
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From dhcwg-bounces@ietf.org Fri Aug 17 12:40:02 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM4q0-0006ld-Mb; Fri, 17 Aug 2007 12:38:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM4pz-0006lO-9T; Fri, 17 Aug 2007 12:38:15 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IM4px-00026L-ME; Fri, 17 Aug 2007 12:38:14 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 17 Aug 2007 12:38:14 -0400
X-IronPort-AV: i="4.19,276,1183348800"; 
	d="scan'208"; a="129158916:sNHT81710786"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7HGcDMA019617; 
	Fri, 17 Aug 2007 12:38:13 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l7HGcDmd010653; 
	Fri, 17 Aug 2007 16:38:13 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 12:38:13 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 17 Aug 2007 12:38:12 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0388150C@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <XMB-RTP-20E3cf3ednH000001f2@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Index: Acfg62hzCUWGXS2JSESb0bG1VA2xXQAAMmZA
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03881506@xmb-rtp-20e.amer.cisco.com>
	<XMB-RTP-20E3cf3ednH000001f2@xmb-rtp-20e.amer.cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Ralph Droms (rdroms)" <rdroms@cisco.com>, <ipv6@ietf.org>
X-OriginalArrivalTime: 17 Aug 2007 16:38:13.0154 (UTC)
	FILETIME=[00F90820:01C7E0ED]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5648; t=1187368693;
	x=1188232693; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20 |Sender:=20
	|To:=20=22Ralph=20Droms=20(rdroms)=22=20<rdroms@cisco.com>,
	=20<ipv6@ietf. org>;
	bh=dSnTAtL+W28LO5evAoTiubbiyO0DLanj84IYoq3c1Yo=;
	b=nIGkKmZXxILZNbm/HjSN0iYvBX10Xut8n28Il6YkStlcOCkXn/2vNVYLOS+A8+jl48XJ0a0m
	SE/f+QnqXvLklHERiLfreOejxRyzsdC+XosAdUQcmB+T0tkT+NIrvy9s;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Cc: dhcwg@ietf.org, "Templin, Fred L" <Fred.L.Templin@boeing.com>,
	Iljitsch van Beijnum <iljitsch@muada.com>,
	James Carlson <james.d.carlson@sun.com>,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: [dhcwg] RE: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Ralph,

What all information constitutes prefix information? If a node is DHCPv6
enabled in a RA-absent network, why isn't just the prefix length enough
for the node to make an on-link determination with? In comparison, a
node that is DHCPv6 enabled in a RA-present network uses prefix length
and L bit together to make an on-link determination.

Thanks.

Hemant=20

-----Original Message-----
From: Ralph Droms (rdroms)=20
Sent: Friday, August 17, 2007 12:27 PM
Subject:=20

References:
<C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com><7ECEF9368E169544B43882B
C98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com><8E296595B6471A4689555D
5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-4
4017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><FDB
98139-14EE-4D5F-B96D-C301A4859361@muada.com><18113.42485.158453.756815@g
argle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.1032
58@gargle.gargle.HOWL><20070815175140.GC18683@isc.org><m1zm0reu44.wl%jin
mei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-
rtp-20e.amer.cisco.com><FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com><
B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com><870
6B8AE-001D-4403-A387-5255F67557F4@muada.com><B00EDD615E3C5344B0FFCBA910C
F7E1D038813A2@xmb-rtp-20e.amer.cisco.com><39C363776A4E8C4A94691D2BD9D1C9
A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com><B00EDD615E3C5344B0FFCBA910CF7E1
D038814CF@xmb-rtp-20e.amer.cisco.com> <18117.50055
.237218.334936@gargle.gargle.HOWL>
<B00EDD615E3C5344B0FFCBA910CF7E1D03881506@xmb-rtp-20e.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=3DUS-ASCII; delsp=3Dyes; =
format=3Dflowed
Message-Id: <54E326BC-2027-4FC1-88C8-C0BD8918FF9B@cisco.com>
Cc: "James Carlson" <james.d.carlson@sun.com>,  dhcwg@ietf.org,
"Templin, Fred L" <Fred.L.Templin@boeing.com>,  Iljitsch van Beijnum
<iljitsch@muada.com>,  ipv6@ietf.org,  JINMEI Tatuya / ????
<jinmei@isl.rdc.toshiba.co.jp>
Content-Transfer-Encoding: 7bit
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
Date: Fri, 17 Aug 2007 12:27:46 -0400
To: "Hemant Singh (shemant)" <shemant@cisco.com>
X-Mailer: Apple Mail (2.752.2)
Return-Path: rdroms@cisco.com
X-OriginalArrivalTime: 17 Aug 2007 16:26:47.0602 (UTC)
FILETIME=3D[685A1920:01C7E0EB]

Send prefix information, not prefix lengths with assigned addresses.

The little bit of savings in assuming the tie-in between assigned
addresses and on-link prefixes is short-sighted.

- Ralph

On Aug 17, 2007, at Aug 17, 2007,12:23 PM, Hemant Singh (shemant) wrote:

> Thanks, James. I agree with Fred then that a node can try DHCPv6. But=20
> now how does the node get a prefix length? As you are saying, some=20
> manual or static configuration can be used. I certainly don't like the

> host to assume any prefix length in this scenario. Since I am not a=20
> fan of any manual configuration, it does make sense, only for such a=20
> case of absence of an RA, that DHCPv6 provides prefix length. Since=20
> DHCPv6 doesn't know if the network's router will issue RA's or not,=20
> then
> DHCPv6
> has to provide prefix length all the time.
>
> Then I am for what Iljitsch is saying. If a host see a discrepancy in=20
> prefix lengths from RA and DHCPv6, then host has to decide based on a=20
> union of information.
>
> Hemant
>
> -----Original Message-----
> From: James Carlson [mailto:james.d.carlson@sun.com]
> Sent: Friday, August 17, 2007 11:49 AM
> To: Hemant Singh (shemant)
> Cc: Templin, Fred L; Iljitsch van Beijnum; dhcwg@ietf.org;=20
> ipv6@ietf.org; JINMEI Tatuya / ????
> Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
>
> Hemant Singh (shemant) writes:
>> I have not found any information in the ND RFC's nor DHCPv6 RFC that=20
>> say a node can initiate DHCPv6 if node doesn't receive any RA. I need

>> to see explicit text in some document to accept what you said below.
>
> It does say this.  See RFC 2462 section 4:
>
>    The next phase of autoconfiguration involves obtaining a Router
>    Advertisement or determining that no routers are present. If=20
> routers
>    are present, they will send Router Advertisements that specify what
>    sort of autoconfiguration a host should do.  If no routers are
>    present, stateful autoconfiguration should be invoked.
>
> And then more forcefully in 5.5.2:
>
> 5.5.2.  Absence of Router Advertisements
>
>    If a link has no routers, a host MUST attempt to use stateful
>    autoconfiguration to obtain addresses and other configuration
>    information. An implementation MAY provide a way to disable the
>    invocation of stateful autoconfiguration in this case, but the
>    default SHOULD be enabled.  From the perspective of
>    autoconfiguration, a link has no routers if no Router=20
> Advertisements
>    are received after having sent a small number of Router=20
> Solicitations
>    as described in [DISCOVERY].
>
> It's certainly pointless unless you also have access to some static=20
> prefix information, but it's what the documents say to do.
>
> --=20
> James Carlson, Solaris Networking              =20
> <james.d.carlson@sun.com>
> Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 =20
> 2084
> MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 =20
> 1677
>
> _______________________________________________
> 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 Aug 17 12:48:31 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM4yE-0008C0-O2; Fri, 17 Aug 2007 12:46:46 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM4yC-000849-Lf; Fri, 17 Aug 2007 12:46:44 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IM4yB-0006Cz-NY; Fri, 17 Aug 2007 12:46:44 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 17 Aug 2007 09:46:43 -0700
X-IronPort-AV: i="4.19,276,1183359600"; 
	d="scan'208"; a="201957214:sNHT55318113"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7HGkhoD025235; 
	Fri, 17 Aug 2007 09:46:43 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l7HGkTVt020079;
	Fri, 17 Aug 2007 16:46:42 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 12:46:36 -0400
Received: from [192.168.1.103] ([10.86.243.75]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 12:46:35 -0400
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D0388150C@xmb-rtp-20e.amer.cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03881506@xmb-rtp-20e.amer.cisco.com>
	<XMB-RTP-20E3cf3ednH000001f2@xmb-rtp-20e.amer.cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388150C@xmb-rtp-20e.amer.cisco.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <265F98B2-3598-4320-BAAA-DA39D9DEF7D9@cisco.com>
Content-Transfer-Encoding: 7bit
From: Ralph Droms <rdroms@cisco.com>
Date: Fri, 17 Aug 2007 12:47:34 -0400
To: IETF List IPv6 Mailing <ipv6@ietf.org>, dhcwg@ietf.org
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 17 Aug 2007 16:46:35.0872 (UTC)
	FILETIME=[2C9DB600:01C7E0EE]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=6558; t=1187369203;
	x=1188233203; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rdroms@cisco.com;
	z=From:=20Ralph=20Droms=20<rdroms@cisco.com>
	|Subject:=20Re=3A=20RE=3A=20 |Sender:=20;
	bh=qEWCEVBsOk1w8dB5O8ODpgyOGn9hyJVinUywgUd7aKk=;
	b=afF144KVhlAFrMQ019/0xzuVtLnM0ZJM6f5to4V0q2mU9xH18IhtnIC7teUqIpI7cHogiBHJ
	6nIssI8D5zzClvg2heDifbBktdO1/iBCMpHZCa6R9rSRIaigSF6LGYGCg2BXBSKDxr0sV4McVZ
	pKX//JX0UY5MjcblmV5Tzz/DM=;
Authentication-Results: sj-dkim-1; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25eb6223a37c19d53ede858176b14339
Cc: 
Subject: [dhcwg] Re: RE: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Prefix information includes prefixes other than those associated with  
assigned addresses, or the case when the prefix associated with the  
address is not on link.

Admittedly, the latter case is less than useful without a default  
router.  But default router information might come from elsewhere.

Why are we discussing taking a step *backward* in entangling prefix  
information with address assignment, when the separation of those two  
not-necessarily-related functions is one of the things IPv6 actually  
got right?  Please step back from saving a couple of bits and think  
about the abstractions.

- Ralph

On Aug 17, 2007, at Aug 17, 2007,12:38 PM, Hemant Singh ((shemant))  
wrote:

> Ralph,
>
> What all information constitutes prefix information? If a node is  
> DHCPv6
> enabled in a RA-absent network, why isn't just the prefix length  
> enough
> for the node to make an on-link determination with? In comparison, a
> node that is DHCPv6 enabled in a RA-present network uses prefix length
> and L bit together to make an on-link determination.
>
> Thanks.
>
> Hemant
>
> -----Original Message-----
> From: Ralph Droms (rdroms)
> Sent: Friday, August 17, 2007 12:27 PM
> Subject:
>
> References:
> <C6FE2907-79C0-4EB2-90AC- 
> E4E889CBEEDF@muada.com><7ECEF9368E169544B43882B
> C98EB5D92032DA844@SVR-ALH- 
> EXC-02.mgc.mentorg.com><8E296595B6471A4689555D
> 5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5- 
> A6B6-4
> 4017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><F 
> DB
> 98139-14EE-4D5F-B96D- 
> C301A4859361@muada.com><18113.42485.158453.756815@g
> argle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.10 
> 32
> 58@gargle.gargle.HOWL><20070815175140.GC18683@isc.org><m1zm0reu44.wl 
> %jin
> mei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xm 
> b-
> rtp-20e.amer.cisco.com><FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com 
> ><
> B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb- 
> rtp-20e.amer.cisco.com><870
> 6B8AE-001D-4403- 
> A387-5255F67557F4@muada.com><B00EDD615E3C5344B0FFCBA910C
> F7E1D038813A2@xmb- 
> rtp-20e.amer.cisco.com><39C363776A4E8C4A94691D2BD9D1C9
> A1029ED9C6@XCH- 
> NW-7V2.nw.nos.boeing.com><B00EDD615E3C5344B0FFCBA910CF7E1
> D038814CF@xmb-rtp-20e.amer.cisco.com> <18117.50055
> .237218.334936@gargle.gargle.HOWL>
> <B00EDD615E3C5344B0FFCBA910CF7E1D03881506@xmb-rtp-20e.amer.cisco.com>
> Mime-Version: 1.0 (Apple Message framework v752.2)
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
> Message-Id: <54E326BC-2027-4FC1-88C8-C0BD8918FF9B@cisco.com>
> Cc: "James Carlson" <james.d.carlson@sun.com>,  dhcwg@ietf.org,
> "Templin, Fred L" <Fred.L.Templin@boeing.com>,  Iljitsch van Beijnum
> <iljitsch@muada.com>,  ipv6@ietf.org,  JINMEI Tatuya / ????
> <jinmei@isl.rdc.toshiba.co.jp>
> Content-Transfer-Encoding: 7bit
> From: Ralph Droms <rdroms@cisco.com>
> Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
> Date: Fri, 17 Aug 2007 12:27:46 -0400
> To: "Hemant Singh (shemant)" <shemant@cisco.com>
> X-Mailer: Apple Mail (2.752.2)
> Return-Path: rdroms@cisco.com
> X-OriginalArrivalTime: 17 Aug 2007 16:26:47.0602 (UTC)
> FILETIME=[685A1920:01C7E0EB]
>
> Send prefix information, not prefix lengths with assigned addresses.
>
> The little bit of savings in assuming the tie-in between assigned
> addresses and on-link prefixes is short-sighted.
>
> - Ralph
>
> On Aug 17, 2007, at Aug 17, 2007,12:23 PM, Hemant Singh (shemant)  
> wrote:
>
>> Thanks, James. I agree with Fred then that a node can try DHCPv6. But
>> now how does the node get a prefix length? As you are saying, some
>> manual or static configuration can be used. I certainly don't like  
>> the
>
>> host to assume any prefix length in this scenario. Since I am not a
>> fan of any manual configuration, it does make sense, only for such a
>> case of absence of an RA, that DHCPv6 provides prefix length. Since
>> DHCPv6 doesn't know if the network's router will issue RA's or not,
>> then
>> DHCPv6
>> has to provide prefix length all the time.
>>
>> Then I am for what Iljitsch is saying. If a host see a discrepancy in
>> prefix lengths from RA and DHCPv6, then host has to decide based on a
>> union of information.
>>
>> Hemant
>>
>> -----Original Message-----
>> From: James Carlson [mailto:james.d.carlson@sun.com]
>> Sent: Friday, August 17, 2007 11:49 AM
>> To: Hemant Singh (shemant)
>> Cc: Templin, Fred L; Iljitsch van Beijnum; dhcwg@ietf.org;
>> ipv6@ietf.org; JINMEI Tatuya / ????
>> Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
>>
>> Hemant Singh (shemant) writes:
>>> I have not found any information in the ND RFC's nor DHCPv6 RFC that
>>> say a node can initiate DHCPv6 if node doesn't receive any RA. I  
>>> need
>
>>> to see explicit text in some document to accept what you said below.
>>
>> It does say this.  See RFC 2462 section 4:
>>
>>    The next phase of autoconfiguration involves obtaining a Router
>>    Advertisement or determining that no routers are present. If
>> routers
>>    are present, they will send Router Advertisements that specify  
>> what
>>    sort of autoconfiguration a host should do.  If no routers are
>>    present, stateful autoconfiguration should be invoked.
>>
>> And then more forcefully in 5.5.2:
>>
>> 5.5.2.  Absence of Router Advertisements
>>
>>    If a link has no routers, a host MUST attempt to use stateful
>>    autoconfiguration to obtain addresses and other configuration
>>    information. An implementation MAY provide a way to disable the
>>    invocation of stateful autoconfiguration in this case, but the
>>    default SHOULD be enabled.  From the perspective of
>>    autoconfiguration, a link has no routers if no Router
>> Advertisements
>>    are received after having sent a small number of Router
>> Solicitations
>>    as described in [DISCOVERY].
>>
>> It's certainly pointless unless you also have access to some static
>> prefix information, but it's what the documents say to do.
>>
>> -- 
>> James Carlson, Solaris Networking
>> <james.d.carlson@sun.com>
>> Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442
>> 2084
>> MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442
>> 1677
>>
>> _______________________________________________
>> 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 Aug 17 12:48:45 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM4yV-0000NF-Lq; Fri, 17 Aug 2007 12:47:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM4yU-0000N7-1G; Fri, 17 Aug 2007 12:47:02 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IM4yS-0002J6-OI; Fri, 17 Aug 2007 12:47:02 -0400
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l7HGkru2000284
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 17 Aug 2007 09:46:54 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l7HGkrFL019187; Fri, 17 Aug 2007 11:46:53 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l7HGkkgX019079; Fri, 17 Aug 2007 11:46:52 -0500 (CDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 09:46:47 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 17 Aug 2007 09:46:22 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED9CB@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D0388150C@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Index: Acfg62hzCUWGXS2JSESb0bG1VA2xXQAAMmZAAABsKVA=
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03881506@xmb-rtp-20e.amer.cisco.com>
	<XMB-RTP-20E3cf3ednH000001f2@xmb-rtp-20e.amer.cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388150C@xmb-rtp-20e.amer.cisco.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>,
	"Ralph Droms (rdroms)" <rdroms@cisco.com>, <ipv6@ietf.org>
X-OriginalArrivalTime: 17 Aug 2007 16:46:47.0459 (UTC)
	FILETIME=[3385BF30:01C7E0EE]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Cc: dhcwg@ietf.org, Iljitsch van Beijnum <iljitsch@muada.com>,
	James Carlson <james.d.carlson@sun.com>,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: [dhcwg] RE: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

> What all information constitutes prefix information?

Why not just have DHCP return the same info as in an
RFC2461 PIO?

Fred
fred.l.templin@boeing.com

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



From dhcwg-bounces@ietf.org Fri Aug 17 12:49:24 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM4zB-0000rb-M8; Fri, 17 Aug 2007 12:47:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM4z7-0000ij-U4; Fri, 17 Aug 2007 12:47:41 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IM4z6-0002KK-LP; Fri, 17 Aug 2007 12:47:41 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 17 Aug 2007 09:47:40 -0700
X-IronPort-AV: i="4.19,276,1183359600"; 
	d="scan'208"; a="201957733:sNHT49635369"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7HGle7f026821; 
	Fri, 17 Aug 2007 09:47:40 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l7HGlTiL004979;
	Fri, 17 Aug 2007 16:47:39 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 12:47:29 -0400
Received: from [192.168.1.103] ([10.86.243.75]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 12:47:28 -0400
In-Reply-To: <A822303F-0054-4462-866F-1689EBFE9958@apple.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
	<FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
	<8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
	<A822303F-0054-4462-866F-1689EBFE9958@apple.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A28EE165-DD98-4F4D-B0D2-BEBCA9E5A294@cisco.com>
Content-Transfer-Encoding: 7bit
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
Date: Fri, 17 Aug 2007 12:48:28 -0400
To: James Woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 17 Aug 2007 16:47:28.0668 (UTC)
	FILETIME=[4C15BDC0:01C7E0EE]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1172; t=1187369260;
	x=1188233260; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rdroms@cisco.com;
	z=From:=20Ralph=20Droms=20<rdroms@cisco.com>
	|Subject:=20Re=3A=20[dhcwg]=20Re=3A=20prefix=20length=20determination=20f
	or=20DHCPv6 |Sender:=20;
	bh=BkzXG5YXROcFGmExbS+STO9tnp9ZueYSCwzfYELNAxM=;
	b=UzJ/mMFevBPrOevqzmm8hk/I0DyG4abV8Jse83l97FnprF0rELbAChumxfzgXD4ZEQUENih+
	Hi6hgKeU1flDp7x0yVcP3Z+I+4XdwJ5YoJ3wWj5lzqMPbDee2l23vjzFjE6E98ENxsU+QJbpkv
	kjMi3bQJTLfDcKiCnFREXTc/4=;
Authentication-Results: sj-dkim-1; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Templin,
	Fred L" <Fred.L.Templin@boeing.com>,
	Iljitsch van Beijnum <iljitsch@muada.com>, "ipv6@ietf.org" <ipv6@ietf.org>,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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

You're not the first person to ask that question...

- Ralph

On Aug 17, 2007, at Aug 17, 2007,12:41 PM, James Woodyatt wrote:

> On Aug 17, 2007, at 6:59 AM, "Templin, Fred L"  
> <Fred.L.Templin@boeing.com> wrote:
>
>>> How can that happen with a DHCPv6 host? RA will always precede  
>>> DHCPv6
>>> transactions because unless the host sees an RA with M bit set the
>> host
>>> will not initiate DHCPv6.
>>
>> That doesn't make much sense; if a node doesn't hear
>> RAs, why wouldn't it try DHCPv6 before giving up?
>
> It seems to me that the semantic content of RA with M=1 is to  
> signal to DHCP-capable nodes that no further delay is necessary...  
> DHCP discovery can proceed immediately.
>
> One wonders why they would bother waiting in the first place given  
> the significant probability that DHCP service is deployed without  
> any RA whatsoever.
>
> So, it seems natural to ask... what good is the M bit anyway?
>
> -jhw
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

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



From dhcwg-bounces@ietf.org Fri Aug 17 12:58:01 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM57Q-0005Re-6O; Fri, 17 Aug 2007 12:56:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM57N-0005Pj-6Z; Fri, 17 Aug 2007 12:56:13 -0400
Received: from sca-ea-mail-2.sun.com ([192.18.43.25])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IM57M-0006TI-Ih; Fri, 17 Aug 2007 12:56:13 -0400
Received: from eastmail2bur.East.Sun.COM ([129.148.13.40])
	by sca-ea-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id
	l7HGuB4g029369; Fri, 17 Aug 2007 16:56:11 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail2bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with
	ESMTP id l7HGuA7n013897; Fri, 17 Aug 2007 12:56:10 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l7HGXg3k109653; Fri, 17 Aug 2007 12:33:42 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l7HGXaVC109648;
	Fri, 17 Aug 2007 12:33:36 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18117.52704.821730.341168@gargle.gargle.HOWL>
Date: Fri, 17 Aug 2007 12:33:36 -0400
From: James Carlson <james.d.carlson@sun.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D03881506@xmb-rtp-20e.amer.cisco.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
	<FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
	<8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038814CF@xmb-rtp-20e.amer.ciisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D03881506@xmb-rtp-20e.amer.cisco.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: dhcwg@ietf.org, "Templin, Fred L" <Fred.L.Templin@boeing.com>,
	Iljitsch van Beijnum <iljitsch@muada.com>, ipv6@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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

Hemant Singh (shemant) writes:
> Thanks, James. I agree with Fred then that a node can try DHCPv6. But
> now how does the node get a prefix length? As you are saying, some
> manual or static configuration can be used. I certainly don't like the
> host to assume any prefix length in this scenario. Since I am not a fan
> of any manual configuration, it does make sense, only for such a case of
> absence of an RA, that DHCPv6 provides prefix length. Since DHCPv6
> doesn't know if the network's router will issue RA's or not, then DHCPv6
> has to provide prefix length all the time.

My view on it is that such a network is just plain broken.  V6 seems
intentionally designed to assume that networks have routers, because
routers are the _authoritative_ source of prefixes (they have to route
them).

Thus, it's a case I test for, and one I make sure "works," but I
assume that it's useless.  In my own implementation, you end up with a
/128 for that interface.  If you have a default route, everything will
go there (via the link-locals), and you'll get a pile of redirects for
the local hosts.  If you don't, then you're just sunk.  Enjoy the
address, because it's all you've got.  ;-}

> Then I am for what Iljitsch is saying. If a host see a discrepancy in
> prefix lengths from RA and DHCPv6, then host has to decide based on a
> union of information.

"Union" doesn't make much sense to me.  That just provides a needless
opportunity for error, and consequent bizarre and hard-to-diagnose
behavior out of subsets of hosts on a network that get the wrong data.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From dhcwg-bounces@ietf.org Fri Aug 17 13:05:55 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM5F4-0008Vu-MJ; Fri, 17 Aug 2007 13:04:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IM5F4-0008VW-5L
	for dhcwg@ietf.org; Fri, 17 Aug 2007 13:04:10 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IM5F2-0002rG-TL
	for dhcwg@ietf.org; Fri, 17 Aug 2007 13:04:10 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 1DA315A6E5; Fri, 17 Aug 2007 10:04:08 -0700 (PDT)
Date: Fri, 17 Aug 2007 10:04:08 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: Aggarwal Vivek-Q4997C <Q4997C@motorola.com>
Message-ID: <20070817170407.GA9648@isc.org>
References: <20070816181231.GF10179@isc.org>
	<750BBC72E178114F9DC4872EBFF29A5B04E72DC8@ZMY16EXM66.ds.mot.com>
Mime-Version: 1.0
In-Reply-To: <750BBC72E178114F9DC4872EBFF29A5B04E72DC8@ZMY16EXM66.ds.mot.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: dhcwg@ietf.org
Subject: [dhcwg] Re: use of dhcp3.0.6
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="===============0607731494=="
Errors-To: dhcwg-bounces@ietf.org


--===============0607731494==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="HcAYCG3uE/tztfnV"
Content-Disposition: inline


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

Aggarwal, I see you posted this to both dhcwg and dhcp-users - I just
wanted to ask you to make sure in future you stick to dhcp-users only.

The DHC WG is an IETF working group and is not the correct place to
ask ISC DHCP questions.

I don't have an answer to your question by the way - so far as I know,
it does compile on any linux.


On Fri, Aug 17, 2007 at 01:39:48PM +0800, Aggarwal Vivek-Q4997C wrote:
> Im having LINUX ES verion 4 system.
>=20
> I downloaded source file dhcp-3.0.6.tar.gz from the isc site.
>=20
> How can I make dhcp3.0.6 work on my system , is it possible or not
>=20
> Firstly I downloaded and copied the file to the root dir
>=20
> Did tar then ./configure, nut Im unable make it
> It says make 1 error all
>=20
> Can you please help in the matter
>=20
> Basically I want to use dhcp-3.0.6 on RedHat ES Version 4, How can I do
> that
>=20
>=20
> Regards
> Vivek Aggarwal

--=20
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil?	 https://secure.isc.org/store/t-shirt/
--=20
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins

--HcAYCG3uE/tztfnV
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFGxdUHcXeLeWu2vmoRApRRAJ4szxXHL1FHxBu46LJDZ/36zoA3EgCfS9Cl
6TeQQYEUK1smYWNaG1NrDTw=
=X6Kg
-----END PGP SIGNATURE-----

--HcAYCG3uE/tztfnV--


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

--===============0607731494==--




From dhcwg-bounces@ietf.org Fri Aug 17 13:06:13 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM5FT-0000Jh-3j; Fri, 17 Aug 2007 13:04:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM5FS-0000HG-1o; Fri, 17 Aug 2007 13:04:34 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IM5FP-0002s9-NG; Fri, 17 Aug 2007 13:04:34 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 17 Aug 2007 10:04:31 -0700
X-IronPort-AV: i="4.19,276,1183359600"; 
	d="scan'208"; a="201968186:sNHT65264877"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7HH4Spc022320; 
	Fri, 17 Aug 2007 10:04:28 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7HH4GFQ029497;
	Fri, 17 Aug 2007 17:04:27 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 13:04:24 -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] Re: prefix length determination for DHCPv6
Date: Fri, 17 Aug 2007 13:04:24 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D03881522@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <18117.52704.821730.341168@gargle.gargle.HOWL>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Re: prefix length determination for DHCPv6
Thread-Index: Acfg7nj2TVGWE731RvKWxVD8wZO0AwAAMagg
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com><7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com><8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com><18113.42485.158453.756815@gargle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.103258@gargle.gargle.HOWL><20070815175140.GC18683@isc.org><m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com><FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com><B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com><8706B8AE-001D-4403-A387-5255F67557F4@muada.com><B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com><B00EDD615E3C5344B0FFCBA910CF7E1D038814CF@xmb-rtp-20e.amer.ciisco.com><B00EDD615E3
	C5344B0FFCBA 910CF7E1D03881506@xmb-rtp-20e.amer.cisco.com>
	<18117.52704.821730.341168@gargle.gargle.HOWL>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "James Carlson" <james.d.carlson@sun.com>
X-OriginalArrivalTime: 17 Aug 2007 17:04:24.0964 (UTC)
	FILETIME=[A9D83440:01C7E0F0]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3199; t=1187370268;
	x=1188234268; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20[dhcwg]=20Re=3A=20prefix=20length=20determination=20f
	or=20DHCPv6 |Sender:=20;
	bh=XOMQ1Od8qJmEl9r7CgeM3qu8pAJwvyWZwYy+nzYVWQo=;
	b=sXHfq7+W4gMOcR/dpNtBbSMqZC0KYMco38bdQDevVpz8FrH3NMQaWemXKioyXXawmdgcdf/l
	bKV/++NNYFBiG6fOnR//9FBZ7+dKuWwY1QvaAWp6Cy3MyRGIKnBgWRJAQ5HGVzPQWBdCN+2MM+
	W6/v6k4ocLn9I6z/typTV/DBw=;
Authentication-Results: sj-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: dhcwg@ietf.org, "Templin, Fred L" <Fred.L.Templin@boeing.com>,
	Iljitsch van Beijnum <iljitsch@muada.com>, ipv6@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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

Unless anyone can mention a lot of potential IPv6 deployments that will
deploy IPv6 without a router sending RA, it's not even worth discussing
the subject. Don't tell me one will deploy DHCPv6 hosts without a router
in the deployment - don't give me private closed networks for an example
- it's a weak argument. Even a dinky home network I can build in my home
for IPv6 better have the Linksys router sending RA's to IPv6 hosts in my
home. If a router is deployed, then why disable the RA on the router? I
agree with James that such a RA-absent network is plain broken.=20

My union statement has been qualified by "if a network has RA and
DHCPv6, both, sending prefix lengths". If such a scenario happens, then
what choice does one have but to resolve discrepancies in data provided
by two sources but to use some sort of union.

>From day one, I am with James and Bernie, that DHCPv6 should not add any
more options towards prefix information or gateway. Let only RA provide
prefix information.

Hemant=20

-----Original Message-----
From: James Carlson [mailto:james.d.carlson@sun.com]=20
Sent: Friday, August 17, 2007 12:34 PM
To: Hemant Singh (shemant)
Cc: Templin, Fred L; Iljitsch van Beijnum; dhcwg@ietf.org;
ipv6@ietf.org; JINMEI Tatuya / ????
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6

Hemant Singh (shemant) writes:
> Thanks, James. I agree with Fred then that a node can try DHCPv6. But=20
> now how does the node get a prefix length? As you are saying, some=20
> manual or static configuration can be used. I certainly don't like the

> host to assume any prefix length in this scenario. Since I am not a=20
> fan of any manual configuration, it does make sense, only for such a=20
> case of absence of an RA, that DHCPv6 provides prefix length. Since=20
> DHCPv6 doesn't know if the network's router will issue RA's or not,=20
> then DHCPv6 has to provide prefix length all the time.

My view on it is that such a network is just plain broken.  V6 seems
intentionally designed to assume that networks have routers, because
routers are the _authoritative_ source of prefixes (they have to route
them).

Thus, it's a case I test for, and one I make sure "works," but I assume
that it's useless.  In my own implementation, you end up with a
/128 for that interface.  If you have a default route, everything will
go there (via the link-locals), and you'll get a pile of redirects for
the local hosts.  If you don't, then you're just sunk.  Enjoy the
address, because it's all you've got.  ;-}

> Then I am for what Iljitsch is saying. If a host see a discrepancy in=20
> prefix lengths from RA and DHCPv6, then host has to decide based on a=20
> union of information.

"Union" doesn't make much sense to me.  That just provides a needless
opportunity for error, and consequent bizarre and hard-to-diagnose
behavior out of subsets of hosts on a network that get the wrong data.

--=20
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From dhcwg-bounces@ietf.org Fri Aug 17 13:17:22 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM5Q9-0001Wk-AX; Fri, 17 Aug 2007 13:15:37 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM5Q5-0001VK-3F; Fri, 17 Aug 2007 13:15:33 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IM5Q4-0007EX-3Y; Fri, 17 Aug 2007 13:15:32 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 17 Aug 2007 13:15:31 -0400
X-IronPort-AV: i="4.19,276,1183348800"; 
	d="scan'208"; a="68285872:sNHT87353076"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7HHFV7Z022070; 
	Fri, 17 Aug 2007 13:15:31 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l7HHFVmd022620; 
	Fri, 17 Aug 2007 17:15:31 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 13:15:31 -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] Re: RE: 
Date: Fri, 17 Aug 2007 13:15:30 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0388152C@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <265F98B2-3598-4320-BAAA-DA39D9DEF7D9@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Re: RE: 
Thread-Index: Acfg7jfbSik1HHlHRiWg/XVgrl7d0wAAtU5Q
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03881506@xmb-rtp-20e.amer.cisco.com><XMB-RTP-20E3cf3ednH000001f2@xmb-rtp-20e.amer.cisco.com><B00EDD615E3C5344B0FFCBA910CF7E1D0388150C@xmb-rtp-20e.amer.cisco.com>
	<265F98B2-3598-4320-BAAA-DA39D9DEF7D9@cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Ralph Droms (rdroms)" <rdroms@cisco.com>,
	"IETF List IPv6 Mailing" <ipv6@ietf.org>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 17 Aug 2007 17:15:31.0486 (UTC)
	FILETIME=[371F63E0:01C7E0F2]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7802; t=1187370931;
	x=1188234931; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20[dhcwg]=20Re=3A=20RE=3A=20 |Sender:=20
	|To:=20=22Ralph=20Droms=20(rdroms)=22=20<rdroms@cisco.com>,
	=0A=20=20=20=2
	0=20=20=20=20=22IETF=20List=20IPv6=20Mailing=22=20<ipv6@ietf.org>,
	=20<dhcw g@ietf.org>;
	bh=AP+6kHxtIsmzOqU+M/vT6KEMYeWq3ayvco57Snu/YDA=;
	b=PROHJudSBzOCkE6AxY31GHBCO96vkgLEIMC+SLnuJSEbl8jwZJ5R+03BHFeXsFuN4wWNVJfE
	IoWz0j0daEV/ScCYxsvSgZW7D8a7yzmxKQ4E5FPd6fj2fSgb0nxEruJQ;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cdb443e3957ca9b4c5b55e78cfcf4b26
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Ralph,

I couldn't agree with you more. I don't like entangling prefix
information with address assignment. It is so IPv4 thinking. I am off
this discussion now since I don't believe in any IPv6 network that
deploys DHCPv6 without a router or deployment where the router does not
send RA's.=20

Further, I don't believe in sending prefix information that includes
prefixes other than those associated with assigned addresses, just like
I don't believe in any IPv6 network deployed without a router. A host
can just receive prefix length and then host knows from its assigned
address what is on-link for this host - I have assumed this host hasn't
seen any RA because if the host does, then L-bit from RA has to be
combined with prefix length for on-link determination. Any other prefix
will be off-link and let the host send non-link-local traffic to default
router.=20

Hemant=20

-----Original Message-----
From: Ralph Droms (rdroms)=20
Sent: Friday, August 17, 2007 12:48 PM
To: IETF List IPv6 Mailing; dhcwg@ietf.org
Subject: [dhcwg] Re: RE:=20

Prefix information includes prefixes other than those associated with
assigned addresses, or the case when the prefix associated with the
address is not on link.

Admittedly, the latter case is less than useful without a default
router.  But default router information might come from elsewhere.

Why are we discussing taking a step *backward* in entangling prefix
information with address assignment, when the separation of those two
not-necessarily-related functions is one of the things IPv6 actually got
right?  Please step back from saving a couple of bits and think about
the abstractions.

- Ralph

On Aug 17, 2007, at Aug 17, 2007,12:38 PM, Hemant Singh ((shemant)) =20
wrote:

> Ralph,
>
> What all information constitutes prefix information? If a node is =20
> DHCPv6
> enabled in a RA-absent network, why isn't just the prefix length =20
> enough
> for the node to make an on-link determination with? In comparison, a
> node that is DHCPv6 enabled in a RA-present network uses prefix length
> and L bit together to make an on-link determination.
>
> Thanks.
>
> Hemant
>
> -----Original Message-----
> From: Ralph Droms (rdroms)
> Sent: Friday, August 17, 2007 12:27 PM
> Subject:
>
> References:
> <C6FE2907-79C0-4EB2-90AC-=20
> E4E889CBEEDF@muada.com><7ECEF9368E169544B43882B
> C98EB5D92032DA844@SVR-ALH-=20
> EXC-02.mgc.mentorg.com><8E296595B6471A4689555D
> 5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-=20
> A6B6-4
> 4017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><F

> DB
> 98139-14EE-4D5F-B96D-=20
> C301A4859361@muada.com><18113.42485.158453.756815@g
> argle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.10

> 32
> 58@gargle.gargle.HOWL><20070815175140.GC18683@isc.org><m1zm0reu44.wl=20
> %jin
> mei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xm

> b-
> rtp-20e.amer.cisco.com><FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com

> ><
> B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-=20
> rtp-20e.amer.cisco.com><870
> 6B8AE-001D-4403-=20
> A387-5255F67557F4@muada.com><B00EDD615E3C5344B0FFCBA910C
> F7E1D038813A2@xmb-=20
> rtp-20e.amer.cisco.com><39C363776A4E8C4A94691D2BD9D1C9
> A1029ED9C6@XCH-=20
> NW-7V2.nw.nos.boeing.com><B00EDD615E3C5344B0FFCBA910CF7E1
> D038814CF@xmb-rtp-20e.amer.cisco.com> <18117.50055
> .237218.334936@gargle.gargle.HOWL>
> <B00EDD615E3C5344B0FFCBA910CF7E1D03881506@xmb-rtp-20e.amer.cisco.com>
> Mime-Version: 1.0 (Apple Message framework v752.2)
> Content-Type: text/plain; charset=3DUS-ASCII; delsp=3Dyes; =
format=3Dflowed
> Message-Id: <54E326BC-2027-4FC1-88C8-C0BD8918FF9B@cisco.com>
> Cc: "James Carlson" <james.d.carlson@sun.com>,  dhcwg@ietf.org,
> "Templin, Fred L" <Fred.L.Templin@boeing.com>,  Iljitsch van Beijnum
> <iljitsch@muada.com>,  ipv6@ietf.org,  JINMEI Tatuya / ????
> <jinmei@isl.rdc.toshiba.co.jp>
> Content-Transfer-Encoding: 7bit
> From: Ralph Droms <rdroms@cisco.com>
> Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
> Date: Fri, 17 Aug 2007 12:27:46 -0400
> To: "Hemant Singh (shemant)" <shemant@cisco.com>
> X-Mailer: Apple Mail (2.752.2)
> Return-Path: rdroms@cisco.com
> X-OriginalArrivalTime: 17 Aug 2007 16:26:47.0602 (UTC)
> FILETIME=3D[685A1920:01C7E0EB]
>
> Send prefix information, not prefix lengths with assigned addresses.
>
> The little bit of savings in assuming the tie-in between assigned
> addresses and on-link prefixes is short-sighted.
>
> - Ralph
>
> On Aug 17, 2007, at Aug 17, 2007,12:23 PM, Hemant Singh (shemant) =20
> wrote:
>
>> Thanks, James. I agree with Fred then that a node can try DHCPv6. But
>> now how does the node get a prefix length? As you are saying, some
>> manual or static configuration can be used. I certainly don't like =20
>> the
>
>> host to assume any prefix length in this scenario. Since I am not a
>> fan of any manual configuration, it does make sense, only for such a
>> case of absence of an RA, that DHCPv6 provides prefix length. Since
>> DHCPv6 doesn't know if the network's router will issue RA's or not,
>> then
>> DHCPv6
>> has to provide prefix length all the time.
>>
>> Then I am for what Iljitsch is saying. If a host see a discrepancy in
>> prefix lengths from RA and DHCPv6, then host has to decide based on a
>> union of information.
>>
>> Hemant
>>
>> -----Original Message-----
>> From: James Carlson [mailto:james.d.carlson@sun.com]
>> Sent: Friday, August 17, 2007 11:49 AM
>> To: Hemant Singh (shemant)
>> Cc: Templin, Fred L; Iljitsch van Beijnum; dhcwg@ietf.org;
>> ipv6@ietf.org; JINMEI Tatuya / ????
>> Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
>>
>> Hemant Singh (shemant) writes:
>>> I have not found any information in the ND RFC's nor DHCPv6 RFC that
>>> say a node can initiate DHCPv6 if node doesn't receive any RA. I =20
>>> need
>
>>> to see explicit text in some document to accept what you said below.
>>
>> It does say this.  See RFC 2462 section 4:
>>
>>    The next phase of autoconfiguration involves obtaining a Router
>>    Advertisement or determining that no routers are present. If
>> routers
>>    are present, they will send Router Advertisements that specify =20
>> what
>>    sort of autoconfiguration a host should do.  If no routers are
>>    present, stateful autoconfiguration should be invoked.
>>
>> And then more forcefully in 5.5.2:
>>
>> 5.5.2.  Absence of Router Advertisements
>>
>>    If a link has no routers, a host MUST attempt to use stateful
>>    autoconfiguration to obtain addresses and other configuration
>>    information. An implementation MAY provide a way to disable the
>>    invocation of stateful autoconfiguration in this case, but the
>>    default SHOULD be enabled.  From the perspective of
>>    autoconfiguration, a link has no routers if no Router
>> Advertisements
>>    are received after having sent a small number of Router
>> Solicitations
>>    as described in [DISCOVERY].
>>
>> It's certainly pointless unless you also have access to some static
>> prefix information, but it's what the documents say to do.
>>
>> --=20
>> James Carlson, Solaris Networking
>> <james.d.carlson@sun.com>
>> Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442
>> 2084
>> MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442
>> 1677
>>
>> _______________________________________________
>> 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

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



From dhcwg-bounces@ietf.org Fri Aug 17 13:20:33 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM5TE-0006yk-Ms; Fri, 17 Aug 2007 13:18:48 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM5TC-0006yI-Ar; Fri, 17 Aug 2007 13:18:46 -0400
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IM5TB-0007K2-Jd; Fri, 17 Aug 2007 13:18:46 -0400
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l7HHIfYQ028521
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Fri, 17 Aug 2007 10:18:42 -0700 (PDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1])
	by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l7HHIf8H029117; Fri, 17 Aug 2007 12:18:41 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com
	[130.247.55.84])
	by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l7HHIWSh028776; Fri, 17 Aug 2007 12:18:41 -0500 (CDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by
	XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 10:18:40 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
Date: Fri, 17 Aug 2007 10:17:47 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1029ED9CC@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D03881522@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Re: prefix length determination for DHCPv6
Thread-Index: Acfg7nj2TVGWE731RvKWxVD8wZO0AwAAMaggAACQ8GA=
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com><7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com><8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com><18113.42485.158453.756815@gargle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.103258@gargle.gargle.HOWL><20070815175140.GC18683@isc.org><m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com><FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com><B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com><8706B8AE-001D-4403-A387-5255F67557F4@muada.com><B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com><B00EDD615E3C5344B0FFCBA910CF7E1D038814CF@xmb-rtp-20e.amer.ciisco.com><B0!
	!0EDD615E 3C5344B0FFCB
	A910CF7E1D03881506@xmb-rtp-20e.amer.cisco.com>
	<18117.52704.821730.341168@gargle.gargle.HOWL>
	<B00EDD615E3C5344B0FFCBA910CF7E1D03881522@xmb-rtp-20e.amer.cisco.com>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>,
	"James Carlson" <james.d.carlson@sun.com>
X-OriginalArrivalTime: 17 Aug 2007 17:18:40.0209 (UTC)
	FILETIME=[A79C3C10:01C7E0F2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Cc: dhcwg@ietf.org, Iljitsch van Beijnum <iljitsch@muada.com>, ipv6@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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

> Unless anyone can mention a lot of potential IPv6 deployments that
will
> deploy IPv6 without a router sending RA, it's not even worth
discussing
> the subject.

ISATAP links have routers that send RAs, but not all nodes on
the link will necessarily receive them. A node on an ISATAP
link can always send an RS to get back an RA, but why bother
when the information is available via DHCP?
 =20
> Don't tell me one will deploy DHCPv6 hosts without a router
> in the deployment

Not hearing unsolicited RAs is not the same thing as not
having routers.

> - don't give me private closed networks for an example
> - it's a weak argument. Even a dinky home network I can build in my
home
> for IPv6 better have the Linksys router sending RA's to IPv6 hosts in
my
> home.

OK.

> If a router is deployed, then why disable the RA on the router? I
> agree with James that such a RA-absent network is plain broken.

It's not about disabling RA on the router at all; the
routers are just ordinary routers and will still send
RAs just fine.=20

Fred
fred.l.templin@boeing.com

> My union statement has been qualified by "if a network has RA and
> DHCPv6, both, sending prefix lengths". If such a scenario happens,
then
> what choice does one have but to resolve discrepancies in data
provided
> by two sources but to use some sort of union.
>=20
> From day one, I am with James and Bernie, that DHCPv6 should not add
any
> more options towards prefix information or gateway. Let only RA
provide
> prefix information.
>=20
> Hemant=20
>=20
> -----Original Message-----
> From: James Carlson [mailto:james.d.carlson@sun.com]=20
> Sent: Friday, August 17, 2007 12:34 PM
> To: Hemant Singh (shemant)
> Cc: Templin, Fred L; Iljitsch van Beijnum; dhcwg@ietf.org;
> ipv6@ietf.org; JINMEI Tatuya / ????
> Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
>=20
> Hemant Singh (shemant) writes:
> > Thanks, James. I agree with Fred then that a node can try=20
> DHCPv6. But=20
> > now how does the node get a prefix length? As you are saying, some=20
> > manual or static configuration can be used. I certainly=20
> don't like the
>=20
> > host to assume any prefix length in this scenario. Since I am not a=20
> > fan of any manual configuration, it does make sense, only=20
> for such a=20
> > case of absence of an RA, that DHCPv6 provides prefix length. Since=20
> > DHCPv6 doesn't know if the network's router will issue RA's or not,=20
> > then DHCPv6 has to provide prefix length all the time.
>=20
> My view on it is that such a network is just plain broken.  V6 seems
> intentionally designed to assume that networks have routers, because
> routers are the _authoritative_ source of prefixes (they have to route
> them).
>=20
> Thus, it's a case I test for, and one I make sure "works,"=20
> but I assume
> that it's useless.  In my own implementation, you end up with a
> /128 for that interface.  If you have a default route, everything will
> go there (via the link-locals), and you'll get a pile of redirects for
> the local hosts.  If you don't, then you're just sunk.  Enjoy the
> address, because it's all you've got.  ;-}
>=20
> > Then I am for what Iljitsch is saying. If a host see a=20
> discrepancy in=20
> > prefix lengths from RA and DHCPv6, then host has to decide=20
> based on a=20
> > union of information.
>=20
> "Union" doesn't make much sense to me.  That just provides a needless
> opportunity for error, and consequent bizarre and hard-to-diagnose
> behavior out of subsets of hosts on a network that get the wrong data.
>=20
> --=20
> James Carlson, Solaris Networking             =20
> <james.d.carlson@sun.com>
> Sun Microsystems / 1 Network Drive         71.232W   Vox +1=20
> 781 442 2084
> MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1=20
> 781 442 1677
>=20

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



From dhcwg-bounces@ietf.org Fri Aug 17 13:30:26 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM5cn-0006YK-ST; Fri, 17 Aug 2007 13:28:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM5cl-0006Xy-Hb; Fri, 17 Aug 2007 13:28:39 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IM5ck-0003g7-7d; Fri, 17 Aug 2007 13:28:39 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 17 Aug 2007 13:28:38 -0400
X-IronPort-AV: i="4.19,276,1183348800"; 
	d="scan'208"; a="129163244:sNHT77799212"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7HHSbd3007892; 
	Fri, 17 Aug 2007 13:28:38 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l7HHQMmt026267; 
	Fri, 17 Aug 2007 17:28:37 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 13:28:34 -0400
Received: from [192.168.1.103] ([10.86.243.75]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 13:28:33 -0400
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D0388152C@xmb-rtp-20e.amer.cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D03881506@xmb-rtp-20e.amer.cisco.com><XMB-RTP-20E3cf3ednH000001f2@xmb-rtp-20e.amer.cisco.com><B00EDD615E3C5344B0FFCBA910CF7E1D0388150C@xmb-rtp-20e.amer.cisco.com>
	<265F98B2-3598-4320-BAAA-DA39D9DEF7D9@cisco.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388152C@xmb-rtp-20e.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <D7EFE9B7-FA06-4715-997C-9EA17C9762A4@cisco.com>
Content-Transfer-Encoding: 7bit
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Re: RE: 
Date: Fri, 17 Aug 2007 13:29:32 -0400
To: "Hemant Singh \(shemant\)" <shemant@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 17 Aug 2007 17:28:33.0889 (UTC)
	FILETIME=[09789D10:01C7E0F4]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=9085; t=1187371718;
	x=1188235718; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rdroms@cisco.com;
	z=From:=20Ralph=20Droms=20<rdroms@cisco.com>
	|Subject:=20Re=3A=20[dhcwg]=20Re=3A=20RE=3A=20 |Sender:=20
	|To:=20=22Hemant=20Singh=20\(shemant\)=22=20<shemant@cisco.com>;
	bh=hAdBW4TVkLmqKdT37Axa4VgDO8lhTbhjY/ukc6fgHqk=;
	b=jQk18NahSwrWaOj9bt3TNec0bVweZ3012yrEYdKjLHvOfKGjDGwaakIobkhN7nRsFBDktl6P
	e0tnZUbh8gWEnDtxFmWJNSZz0jayijmiWVOeRUtvqIA2TmkVjnJEbHA0;
Authentication-Results: rtp-dkim-1; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: ce732c7d36989a1bd55104ba259c40a1
Cc: dhcwg@ietf.org, IETF List IPv6 Mailing <ipv6@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

"Beliefs" are irrelevant; we need to consider facts and requirements.

Assigned addresses have nothing intrinsically to do with on-link.  In  
the common case, an address on an interface is quite likely to be in  
a prefix that is on-link.  But on-link-ness is a property used for  
outbound traffic, while an address on an interface is used to filter  
inbound traffic.  The IPv6 design decision has been to separate those  
two notions.

I know of no "MUST NOT" that precludes hosts on a network with no RAs  
having addresses from different prefixes; i.e., host A has an address  
from 2001:0:0:1::/64 and host B has an address from 2001:0:0:ffff::/ 
64.  If host A is going to communicate with host B, one of the two  
hosts is going to have to know about the other host's prefix.  So, if  
DHCPv6 is used, DHCPv6 will need to carry other prefix information  
aside from those in the address assigned to the host.

- Ralph

On Aug 17, 2007, at Aug 17, 2007,1:15 PM, Hemant Singh ((shemant))  
wrote:

> Ralph,
>
> I couldn't agree with you more. I don't like entangling prefix
> information with address assignment. It is so IPv4 thinking. I am off
> this discussion now since I don't believe in any IPv6 network that
> deploys DHCPv6 without a router or deployment where the router does  
> not
> send RA's.
>
> Further, I don't believe in sending prefix information that includes
> prefixes other than those associated with assigned addresses, just  
> like
> I don't believe in any IPv6 network deployed without a router. A host
> can just receive prefix length and then host knows from its assigned
> address what is on-link for this host - I have assumed this host  
> hasn't
> seen any RA because if the host does, then L-bit from RA has to be
> combined with prefix length for on-link determination. Any other  
> prefix
> will be off-link and let the host send non-link-local traffic to  
> default
> router.
>
> Hemant
>
> -----Original Message-----
> From: Ralph Droms (rdroms)
> Sent: Friday, August 17, 2007 12:48 PM
> To: IETF List IPv6 Mailing; dhcwg@ietf.org
> Subject: [dhcwg] Re: RE:
>
> Prefix information includes prefixes other than those associated with
> assigned addresses, or the case when the prefix associated with the
> address is not on link.
>
> Admittedly, the latter case is less than useful without a default
> router.  But default router information might come from elsewhere.
>
> Why are we discussing taking a step *backward* in entangling prefix
> information with address assignment, when the separation of those two
> not-necessarily-related functions is one of the things IPv6  
> actually got
> right?  Please step back from saving a couple of bits and think about
> the abstractions.
>
> - Ralph
>
> On Aug 17, 2007, at Aug 17, 2007,12:38 PM, Hemant Singh ((shemant))
> wrote:
>
>> Ralph,
>>
>> What all information constitutes prefix information? If a node is
>> DHCPv6
>> enabled in a RA-absent network, why isn't just the prefix length
>> enough
>> for the node to make an on-link determination with? In comparison, a
>> node that is DHCPv6 enabled in a RA-present network uses prefix  
>> length
>> and L bit together to make an on-link determination.
>>
>> Thanks.
>>
>> Hemant
>>
>> -----Original Message-----
>> From: Ralph Droms (rdroms)
>> Sent: Friday, August 17, 2007 12:27 PM
>> Subject:
>>
>> References:
>> <C6FE2907-79C0-4EB2-90AC-
>> E4E889CBEEDF@muada.com><7ECEF9368E169544B43882B
>> C98EB5D92032DA844@SVR-ALH-
>> EXC-02.mgc.mentorg.com><8E296595B6471A4689555D
>> 5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-
>> A6B6-4
>> 4017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL>< 
>> F
>
>> DB
>> 98139-14EE-4D5F-B96D-
>> C301A4859361@muada.com><18113.42485.158453.756815@g
>> argle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.1 
>> 0
>
>> 32
>> 58@gargle.gargle.HOWL><20070815175140.GC18683@isc.org><m1zm0reu44.wl
>> %jin
>> mei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@x 
>> m
>
>> b-
>> rtp-20e.amer.cisco.com><FD512419-10D7-479E-9103-36C0C5BB32EE@muada.co 
>> m
>
>>> <
>> B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-
>> rtp-20e.amer.cisco.com><870
>> 6B8AE-001D-4403-
>> A387-5255F67557F4@muada.com><B00EDD615E3C5344B0FFCBA910C
>> F7E1D038813A2@xmb-
>> rtp-20e.amer.cisco.com><39C363776A4E8C4A94691D2BD9D1C9
>> A1029ED9C6@XCH-
>> NW-7V2.nw.nos.boeing.com><B00EDD615E3C5344B0FFCBA910CF7E1
>> D038814CF@xmb-rtp-20e.amer.cisco.com> <18117.50055
>> .237218.334936@gargle.gargle.HOWL>
>> <B00EDD615E3C5344B0FFCBA910CF7E1D03881506@xmb-rtp-20e.amer.cisco.com>
>> Mime-Version: 1.0 (Apple Message framework v752.2)
>> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>> Message-Id: <54E326BC-2027-4FC1-88C8-C0BD8918FF9B@cisco.com>
>> Cc: "James Carlson" <james.d.carlson@sun.com>,  dhcwg@ietf.org,
>> "Templin, Fred L" <Fred.L.Templin@boeing.com>,  Iljitsch van Beijnum
>> <iljitsch@muada.com>,  ipv6@ietf.org,  JINMEI Tatuya / ????
>> <jinmei@isl.rdc.toshiba.co.jp>
>> Content-Transfer-Encoding: 7bit
>> From: Ralph Droms <rdroms@cisco.com>
>> Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
>> Date: Fri, 17 Aug 2007 12:27:46 -0400
>> To: "Hemant Singh (shemant)" <shemant@cisco.com>
>> X-Mailer: Apple Mail (2.752.2)
>> Return-Path: rdroms@cisco.com
>> X-OriginalArrivalTime: 17 Aug 2007 16:26:47.0602 (UTC)
>> FILETIME=[685A1920:01C7E0EB]
>>
>> Send prefix information, not prefix lengths with assigned addresses.
>>
>> The little bit of savings in assuming the tie-in between assigned
>> addresses and on-link prefixes is short-sighted.
>>
>> - Ralph
>>
>> On Aug 17, 2007, at Aug 17, 2007,12:23 PM, Hemant Singh (shemant)
>> wrote:
>>
>>> Thanks, James. I agree with Fred then that a node can try DHCPv6.  
>>> But
>>> now how does the node get a prefix length? As you are saying, some
>>> manual or static configuration can be used. I certainly don't like
>>> the
>>
>>> host to assume any prefix length in this scenario. Since I am not a
>>> fan of any manual configuration, it does make sense, only for such a
>>> case of absence of an RA, that DHCPv6 provides prefix length. Since
>>> DHCPv6 doesn't know if the network's router will issue RA's or not,
>>> then
>>> DHCPv6
>>> has to provide prefix length all the time.
>>>
>>> Then I am for what Iljitsch is saying. If a host see a  
>>> discrepancy in
>>> prefix lengths from RA and DHCPv6, then host has to decide based  
>>> on a
>>> union of information.
>>>
>>> Hemant
>>>
>>> -----Original Message-----
>>> From: James Carlson [mailto:james.d.carlson@sun.com]
>>> Sent: Friday, August 17, 2007 11:49 AM
>>> To: Hemant Singh (shemant)
>>> Cc: Templin, Fred L; Iljitsch van Beijnum; dhcwg@ietf.org;
>>> ipv6@ietf.org; JINMEI Tatuya / ????
>>> Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
>>>
>>> Hemant Singh (shemant) writes:
>>>> I have not found any information in the ND RFC's nor DHCPv6 RFC  
>>>> that
>>>> say a node can initiate DHCPv6 if node doesn't receive any RA. I
>>>> need
>>
>>>> to see explicit text in some document to accept what you said  
>>>> below.
>>>
>>> It does say this.  See RFC 2462 section 4:
>>>
>>>    The next phase of autoconfiguration involves obtaining a Router
>>>    Advertisement or determining that no routers are present. If
>>> routers
>>>    are present, they will send Router Advertisements that specify
>>> what
>>>    sort of autoconfiguration a host should do.  If no routers are
>>>    present, stateful autoconfiguration should be invoked.
>>>
>>> And then more forcefully in 5.5.2:
>>>
>>> 5.5.2.  Absence of Router Advertisements
>>>
>>>    If a link has no routers, a host MUST attempt to use stateful
>>>    autoconfiguration to obtain addresses and other configuration
>>>    information. An implementation MAY provide a way to disable the
>>>    invocation of stateful autoconfiguration in this case, but the
>>>    default SHOULD be enabled.  From the perspective of
>>>    autoconfiguration, a link has no routers if no Router
>>> Advertisements
>>>    are received after having sent a small number of Router
>>> Solicitations
>>>    as described in [DISCOVERY].
>>>
>>> It's certainly pointless unless you also have access to some static
>>> prefix information, but it's what the documents say to do.
>>>
>>> -- 
>>> James Carlson, Solaris Networking
>>> <james.d.carlson@sun.com>
>>> Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442
>>> 2084
>>> MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442
>>> 1677
>>>
>>> _______________________________________________
>>> 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

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



From dhcwg-bounces@ietf.org Fri Aug 17 13:39:44 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM5lm-0006mj-1r; Fri, 17 Aug 2007 13:37:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM5lk-0006ev-P8; Fri, 17 Aug 2007 13:37:56 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IM5lj-0003ua-JN; Fri, 17 Aug 2007 13:37:56 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 17 Aug 2007 13:37:55 -0400
X-IronPort-AV: i="4.19,276,1183348800"; 
	d="scan'208"; a="68288387:sNHT53526422"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7HHbtlU012704; 
	Fri, 17 Aug 2007 13:37:55 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7HHbkjO027678; 
	Fri, 17 Aug 2007 17:37:46 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 13:37:42 -0400
Received: from [192.168.1.103] ([10.86.243.75]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 13:37:42 -0400
In-Reply-To: <m2zm0ywj2a.wl%jinmei@isl.rdc.toshiba.co.jp>
References: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA840@SVR-ALH-EXC-02.mgc.mentorg.com>
	<m2zm0ywj2a.wl%jinmei@isl.rdc.toshiba.co.jp>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed
Message-Id: <BF3DEC71-ED1E-4238-842E-0480E1EE4FC6@cisco.com>
Content-Transfer-Encoding: quoted-printable
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
Date: Fri, 17 Aug 2007 13:38:40 -0400
To: =?UTF-8?Q?JINMEI_Tatuya_/_=E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89?=
	<jinmei@isl.rdc.toshiba.co.jp>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 17 Aug 2007 17:37:42.0497 (UTC)
	FILETIME=[50778D10:01C7E0F5]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=782; t=1187372275;
	x=1188236275; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rdroms@cisco.com;
	z=From:=20Ralph=20Droms=20<rdroms@cisco.com>
	|Subject:=20Re=3A=20[dhcwg]=20RE=3A=20prefix=20length=20determination=20f
	or=20DHCPv6 |Sender:=20
	|To:=20=3D?UTF-8?Q?JINMEI_Tatuya_/_=3DE7=3DA5=3D9E=3DE6=3D98=3D8E=3DE9=3D
	81=3D94=3DE5=3D93=3D89?=3D=20<jinmei@isl.rdc.toshiba.co.jp>;
	bh=SCgPSzwS3E5c7pwukNT73R4CQ75b5vIfoH4luLLfiCM=;
	b=R9+W9rmwwEg28AusP4cLFlkxVrWXE2fNyR0rnulRJQ6tF4EG8egG0i7m2ibg1SEfBXTebiYJ
	htX6Nlqy2PxVOE9vGW0T6vRgxogylvAqoGpMOoX8E2uW0HfjVpuJW48A;
Authentication-Results: rtp-dkim-1; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -2.2 (--)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: ipv6@ietf.org, "Bernie Volz \(volz\)" <volz@cisco.com>,
	Iljitsch van Beijnum <iljitsch@muada.com>,
	"John Jason Brzozowski \(JJMB\)" <jjmb@jjmb.com>, 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

Jinmei-san - I fully agree that it would be a good idea to hold off =20
on this discussion until an I-D is published.

One small correction...the originators of the discussion about "rogue =20=

RAs" are network admins who have real-world experience with IPv6 =20
deployments.  I wouldn't consider them as "DHCPv6 guys" in this =20
context...

- Ralph

On Aug 11, 2007, at Aug 11, 2007,4:51 AM, JINMEI Tatuya / =E7=A5=9E=E6=98=8E=
=E9=81=94=E5=93=89 =20
wrote:
> In any event, I hear that some DHCPv6 guys are planning to make a new
> draft that covers this topic.  So I think it's better to hold off for
> now and wait for the document, rather than continue this thread
> with keeping possible misunderstanding or confusing about the base
> protocol principles.


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



From dhcwg-bounces@ietf.org Fri Aug 17 14:38:57 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM6h5-0002Xe-BP; Fri, 17 Aug 2007 14:37:11 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM6h3-0002XQ-Q7; Fri, 17 Aug 2007 14:37:09 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IM6h3-0002DJ-80; Fri, 17 Aug 2007 14:37:09 -0400
Received: from [82.192.90.28] (nirrti.muada.com [82.192.90.28])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l7HIYlY3013088
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Fri, 17 Aug 2007 20:34:47 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <A822303F-0054-4462-866F-1689EBFE9958@apple.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
	<FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
	<8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
	<A822303F-0054-4462-866F-1689EBFE9958@apple.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <979575B8-AEB8-4E22-A761-6422B9C20C51@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
Date: Fri, 17 Aug 2007 20:36:55 +0200
To: James Woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Templin,
	Fred L" <Fred.L.Templin@boeing.com>, "ipv6@ietf.org" <ipv6@ietf.org>,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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 17-aug-2007, at 18:41, James Woodyatt wrote:

> One wonders why they would bother waiting in the first place given  
> the significant probability that DHCP service is deployed without  
> any RA whatsoever.

> So, it seems natural to ask... what good is the M bit anyway?

To stop unnecessary DHCP traffic. Please don't make implementations  
do DHCP by default even without an M or O bit, as I've said before,  
multicast traffic uses up inordinate amounts of bandwidth on wifi  
links and it's even worse if there are no DHCPv6 servers (which is  
the case in 99.99% of all deployments today) so the requests will be  
retransmitted.

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



From dhcwg-bounces@ietf.org Fri Aug 17 16:11:25 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM88Z-0001B1-GS; Fri, 17 Aug 2007 16:09:39 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM88Y-0001Ao-9r; Fri, 17 Aug 2007 16:09:38 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IM88X-0004uh-Hl; Fri, 17 Aug 2007 16:09:38 -0400
Received: from relay5.apple.com (relay5.apple.com [17.128.113.35])
	by mail-out4.apple.com (Postfix) with ESMTP id A6E34F23D40;
	Fri, 17 Aug 2007 13:09:36 -0700 (PDT)
Received: from relay5.apple.com (unknown [127.0.0.1])
	by relay5.apple.com (Symantec Mail Security) with ESMTP id 9674129C019; 
	Fri, 17 Aug 2007 13:09:36 -0700 (PDT)
X-AuditID: 11807123-a5a45bb000007d99-70-46c600802f64
Received: from [17.206.23.199] (il0602a-dhcp71.apple.com [17.206.23.199])
	by relay5.apple.com (Apple SCV relay) with ESMTP id 2D24F30400B;
	Fri, 17 Aug 2007 13:09:36 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <979575B8-AEB8-4E22-A761-6422B9C20C51@muada.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
	<FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
	<8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
	<A822303F-0054-4462-866F-1689EBFE9958@apple.com> <979575B
	8-AEB8-4E22-A761-6422B9C20C51@muada.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <6354B72A-EC4E-40DB-9A50-01036B1FEE39@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
Date: Fri, 17 Aug 2007 13:09:26 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>,
 dhcwg@ietf.org
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Aug 17, 2007, at 11:36, Iljitsch van Beijnum wrote:
>
> To stop unnecessary DHCP traffic. [...]

I think what we're seeing here is a vocal faction of the community  
who believe that DHCP discovery multicasts are always necessary,  
whether RA is present or not, and whether M=0 or M=1, despite the  
text in RFC 2462.

Here's what they seem to be saying: wherever a DHCP server *may* be  
present, DHCP discovery *MUST NOT* be prevented and *SHOULD NOT* be  
delayed.  If you agree with that, then perhaps it also makes sense to  
move prefix and default gateway assignment into DHCP for the purpose  
of improving efficiency.  The DHCP advocates seem to view RA with M=1  
as basically superfluous to the process, unless it can be made to  
signal effectively that nodes *MUST NOT* perform stateless  
autoconfiguration.  Alas, unfortunately for them, RFC 2462 doesn't do  
that.  In fact, it explicitly states that a node *may* always perform  
stateless autoconf after receiving RA with M=0 containing a PIO with  
A=1, and hence the kvetching about rogue advertisers.

There is a closely related problem here in the language of RFC 2462.   
Notice how the state of the ManagedFlag conceptual variable is  
specified during processing of Router Advertisements.

> Section 5.2 Autoconfiguration-Related Variables
>
>  Hosts maintain the following variables on a per-interface basis:
>
>       ManagedFlag      Copied from the M flag field (i.e., the
>                        "managed address configuration" flag) of the  
> most
>                        recently received Router Advertisement message.
>                        The flag indicates whether or not addresses are
>                        to be configured using the stateful
>                        autoconfiguration mechanism. It starts out in a
>                        FALSE state.
[...]
> 5.5.3.  Router Advertisement Processing
>
>    On receipt of a valid Router Advertisement (as defined in
>    [DISCOVERY]), a host copies the value of the advertisement's M bit
>    into ManagedFlag. If the value of ManagedFlag changes from FALSE to
>    TRUE, and the host is not already running the stateful address
>    autoconfiguration protocol, the host should invoke the stateful
>    address autoconfiguration protocol, requesting both address
>    information and other information.  If the value of the ManagedFlag
>    changes from TRUE to FALSE, the host should continue running the
>    stateful address autoconfiguration, i.e., the change in the  
> value of
>    the ManagedFlag has no effect.  If the value of the flag stays
>    unchanged, no special action takes place. In particular, a host  
> MUST
>    NOT reinvoke stateful address configuration if it is already
>    participating in the stateful protocol as a result of an earlier
>    advertisement.

I see only one invocation of RFC 2119 requirements language in there,  
and it's to apply a curious injunction not to restart DHCP discovery  
every time RA with M=1 is received while ManagedFlag is TRUE.  All  
the rest of the verbiage about the ManagedFlag conceptual variable  
amounts to a recommendation that DHCP discovery should be deferred  
until the first receipt of RA with M=1 at the interface and should  
remain in operation until the interface disconnects.  One interesting  
consequence of this verbiage is that it recommends setting the  
ManagedFlag to FALSE upon receiving RA with M=0.  When the next RA  
arrives with M=1, the node will then be free to restart DHCP  
discovery because the above requirement will no longer apply.   
(Whether it *will* is not specified.)  This basically nullifies the  
utility of the one instance of RFC 2119 requirements language in how  
the ManagedFlag is to be handled during RA processing.

As I said, it's very curious.

I think the new 6MAN working group should take up a project of  
clarifying the requirements for processing router advertisements in  
IPv6 nodes.

On a related note, I've heard that some operators intend to deploy  
DHCP service using RA with M=1 and no PIO.  I don't understand how  
they imagine the "on-link flag" to be propagated in that scenario.   
The "on-link flag" seems to be clearly in the domain of router  
function, not dynamic node configuration.  Is that to be described in  
the forthcoming Internet draft?


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



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



From dhcwg-bounces@ietf.org Fri Aug 17 16:43:34 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM8de-0002bI-RH; Fri, 17 Aug 2007 16:41:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM8dc-0002XM-Ei; Fri, 17 Aug 2007 16:41:44 -0400
Received: from brmea-mail-2.sun.com ([192.18.98.43])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IM8db-0001EM-5Z; Fri, 17 Aug 2007 16:41:44 -0400
Received: from eastmail2bur.East.Sun.COM ([129.148.13.40])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l7HKfgZP015141; Fri, 17 Aug 2007 20:41:42 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail2bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with
	ESMTP id l7HKff2r022380; Fri, 17 Aug 2007 16:41:42 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l7HKMwcs110862; Fri, 17 Aug 2007 16:22:58 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l7HKMvfN110859;
	Fri, 17 Aug 2007 16:22:57 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18118.929.835841.63148@gargle.gargle.HOWL>
Date: Fri, 17 Aug 2007 16:22:57 -0400
From: James Carlson <james.d.carlson@sun.com>
To: james woodyatt <jhw@apple.com>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
In-Reply-To: <6354B72A-EC4E-40DB-9A50-01036B1FEE39@apple.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
	<FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
	<8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
	<A822303F-0054-4462-866F-1689EBFE9958@apple.com>
	<"979575B  8-AEB8-4E22-A761-6422B9C20C51"@muada.com>
	<6354B72A-EC4E-40DB-9A50-01036B1FEE39@apple.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: dhcwg@ietf.org, IETF IPv6 Mailing List <ipv6@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

james woodyatt writes:
> >    into ManagedFlag. If the value of ManagedFlag changes from FALSE to
> >    TRUE, and the host is not already running the stateful address
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >    autoconfiguration protocol, the host should invoke the stateful
       ^^^^^^^^^^^^^^^^^^^^^^^^^^
> >    address autoconfiguration protocol, requesting both address
> >    information and other information.  If the value of the ManagedFlag
[...]
> ManagedFlag to FALSE upon receiving RA with M=0.  When the next RA  
> arrives with M=1, the node will then be free to restart DHCP  
> discovery because the above requirement will no longer apply.   

No, it won't be free to do so.  The text quoted above makes it fairly
clear that if you're already running the stateful address protocol,
you don't restart it.  Even if the flag changes from FALSE to TRUE.

It's a one-shot event on a given interface.  If you time out waiting
to hear from routers, or if any router anywhere ever tells you to run
DHCPv6 on that interface, then that's what you do.  The only time you
_don't_ run DHCPv6 is when you (A) consistently hear from routers and
(B) those routers all tell you M=0 and O=0.

(Reserve a special place for naming a bit 'O'.  ;-})

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From dhcwg-bounces@ietf.org Fri Aug 17 19:47:56 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMBW5-0001AN-1m; Fri, 17 Aug 2007 19:46:09 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMBW3-00019K-Lu; Fri, 17 Aug 2007 19:46:07 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IMBVv-0003hU-Rt; Fri, 17 Aug 2007 19:46:07 -0400
Received: from relay8.apple.com (relay8.apple.com [17.128.113.38])
	by mail-out4.apple.com (Postfix) with ESMTP id B3FA5F2806E;
	Fri, 17 Aug 2007 16:45:33 -0700 (PDT)
Received: from relay8.apple.com (unknown [127.0.0.1])
	by relay8.apple.com (Symantec Mail Security) with ESMTP id 9FCE9400EB; 
	Fri, 17 Aug 2007 16:45:33 -0700 (PDT)
X-AuditID: 11807126-a6446bb0000007e3-46-46c6331d52ac
Received: from [17.151.89.88] (unknown [17.151.89.88])
	by relay8.apple.com (Apple SCV relay) with ESMTP id 861FC4008B;
	Fri, 17 Aug 2007 16:45:33 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <18118.929.835841.63148@gargle.gargle.HOWL>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
	<FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
	<8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
	<A822303F-0054-4462-866F-1689EBFE9958@apple.com> <"979575
	B 8-AEB8-4E22-A761-6422B9C20C51"@muada.com>
	<6354B72A-EC4E-40DB-9A50-01036B1FEE39@apple.com>
	<18118.929.835841.63148@gargle.gargle.HOWL>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <20C28D58-D9FF-40C0-A2D9-3CAF95774211@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
Date: Fri, 17 Aug 2007 16:45:23 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>,
 dhcwg@ietf.org
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Aug 17, 2007, at 13:22, James Carlson wrote:
> james woodyatt writes:
>>>    into ManagedFlag. If the value of ManagedFlag changes from  
>>> FALSE to
>>>    TRUE, and the host is not already running the stateful address
>              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>    autoconfiguration protocol, the host should invoke the stateful
>        ^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>    address autoconfiguration protocol, requesting both address
>>>    information and other information.  If the value of the  
>>> ManagedFlag
> [...]
>> ManagedFlag to FALSE upon receiving RA with M=0.  When the next RA
>> arrives with M=1, the node will then be free to restart DHCP
>> discovery because the above requirement will no longer apply.
>
> No, it won't be free to do so.  The text quoted above makes it fairly
> clear that if you're already running the stateful address protocol,
> you don't restart it.  Even if the flag changes from FALSE to TRUE.

You're right.  My mistake.  The sentence preceding the requirement  
doesn't specify an actual contingency.  The requirement applies  
regardless of the current state of the ManagedFlag.  Once the  
stateful autoconfiguration protocol starts, it's expected to continue  
without restarting until the interface disconnects from the link.

> It's a one-shot event on a given interface.  If you time out waiting
> to hear from routers, or if any router anywhere ever tells you to run
> DHCPv6 on that interface, then that's what you do.  The only time you
> _don't_ run DHCPv6 is when you (A) consistently hear from routers and
> (B) those routers all tell you M=0 and O=0.

I don't see any MUST NOT that requires stateless AddrConf to be  
deferred while the node waits "for a time" to receive of RA with  
M=1.  If the typical network with DHCP service never has any  
legitimate routers sending RA of any sort, then nodes will typically  
acquire service more quickly after connecting if they do not wait for  
packets that will never arrive.  Since there is no RFC 2119  
requirement to wait, a conforming implementation can certainly choose  
not to defer DHCP discovery while prefix discovery has not yet  
completed, despite the informative text suggesting that waiting is  
appropriate.

Whether DHCP6 must not complete until prefix discovery has completed  
is an open question, or so it seems to me after reading RFC 3315 and  
looking for guidance on the subject.  I suspect I would prefer to see  
RFC 3315 revised to define a new IA_PI (prefix information) option  
for clients to use, which would associate a list of discovered  
prefixes with their generated IAID.  Clients that send Solicit  
messages containing IA_TA or IA_NA options without an accompanying  
IA_PI option will be implying that they failed or refused to discover  
any prefixes.  Servers may then refuse to send Advertise messages to  
clients that have no acceptable prefixes.  When clients provide a  
IA_PI option, then servers are required to assign addresses from the  
specified list of prefixes.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



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



From dhcwg-bounces@ietf.org Fri Aug 17 20:33:28 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMCE9-0007PK-3t; Fri, 17 Aug 2007 20:31:41 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMCE7-0007P4-4I; Fri, 17 Aug 2007 20:31:39 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IMCE6-0004zt-81; Fri, 17 Aug 2007 20:31:39 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 17 Aug 2007 20:31:38 -0400
X-IronPort-AV: i="4.19,278,1183348800"; 
	d="scan'208"; a="68322872:sNHT77094002"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7I0VbT3001185; 
	Fri, 17 Aug 2007 20:31:37 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l7I0Vbmf015822; 
	Sat, 18 Aug 2007 00:31:37 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 20:31:37 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
Date: Fri, 17 Aug 2007 20:31:36 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0388161A@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <6354B72A-EC4E-40DB-9A50-01036B1FEE39@apple.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Re: prefix length determination for DHCPv6
Thread-Index: AcfhCpVveiWP6wG/SYWq6P/QzfnjfgAH/3Gw
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com><7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com><8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com><18113.42485.158453.756815@gargle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.103258@gargle.gargle.HOWL><20070815175140.GC18683@isc.org><m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com><FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com><B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com><8706B8AE-001D-4403-A387-5255F67557F4@muada.com><B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com><A822303F-0054-4462-866F-1689EBFE9958@apple.com>
	<979575B8-AEB8-4E22-A761-6422B9C2 0C51@muada.c
	om> <6354B72A-EC4E-40DB-9A50-01036B1FEE39@apple.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "james woodyatt" <jhw@apple.com>, "IETF IPv6 Mailing List" <ipv6@ietf.org>,
	<dhcwg@ietf.org>
X-OriginalArrivalTime: 18 Aug 2007 00:31:37.0655 (UTC)
	FILETIME=[235FEC70:01C7E12F]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=7196; t=1187397097;
	x=1188261097; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20[dhcwg]=20Re=3A=20prefix=20length=20determination=20f
	or=20DHCPv6 |Sender:=20
	|To:=20=22james=20woodyatt=22=20<jhw@apple.com>,
	=20=22IETF=20IPv6=20Maili
	ng=20List=22=20<ipv6@ietf.org>,=0A=20=20=20=20=20=20=20=20<dhcwg@ietf.org>;
	bh=zBQJwhD08vdLVYZKcQrv7J427jclQVBZrO1bzj+iNOw=;
	b=IubrP82AKj9GFhM3ogejVMeBer7JT74ImJxUQ7zlBcz900wzct/FZD61X320Zx7AvH7ZhAEo
	SeUtYFiC0kj/DCZoUKpnXiNr8TP7Gkk7i1O4s25OmLUhqbNqqo2JcyKX;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d16ce744298aacf98517bc7c108bd198
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

James,

Wrt to what you asked as follows put within square brackets by me
followed by my reply.

[On a related note, I've heard that some operators intend to deploy DHCP
service using RA with M=3D1 and no PIO.  I don't understand how =20
they imagine the "on-link flag" to be propagated in that scenario.  =20
The "on-link flag" seems to be clearly in the domain of router function,
not dynamic node configuration.  Is that to be described in the
forthcoming Internet draft?]

In an aggregation router network, all host behind broadband modems are
always off-link as we have explained in this mailer - see one of my
emails.

So there is NO NEED to propagate any on-link flag is such a network.=20

The physical connectivity of such networks prohibits hosts behind modems
to talk directly to each other even when a pair of hosts are in the same
link. The hosts have to send their traffic to the aggregation router.
That is why IPv6 hosts in an aggregation router deployment are always
off-link. So how does one signal off-link in RA? One way is to send no
PIO in RA. See section 2.1 of our I-D for how this signals off-link, and
under what conditions, and for what IPv6 addresses (link-local or
non-link-local addresses). Our I-D is at:

http://www.ietf.org/internet-drafts/draft-wbeebee-nd-implementation-pitf
alls-02.txt
=20
Do read section 3 of our I-D that described aggregation routed
deployments.=20

While I have everyone here, when will folks agree that some cases for
on-link determination are not clear in 2461bis and such cases need to be
clarified - that is the reason we wrote the I-D above. If on- vs.
off-link is not clear, data forwarding and address resolution of
behavior of hosts gets affected - these are key features of a host
operation and hence on- vs. off-link should be crystal clear! Maybe our
late-breaking I-D was a bad timing for 2461bis authors, but the facts
still remain that our I-D is worth an Implementation Guideline and be
considered as a WG item for v6man. That is why we have also collected
some bugs in IPv6 ND implementation and listed them in section 7 of our
I-D keeping the format of the bugs ala RFC 2525.

Do humor me and let I and Wes know how many other ways exist for an RA
to be specified to signal off-link mode to hosts?

Hemant=20

-----Original Message-----
From: james woodyatt [mailto:jhw@apple.com]=20
Sent: Friday, August 17, 2007 4:09 PM
To: IETF IPv6 Mailing List; dhcwg@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6

On Aug 17, 2007, at 11:36, Iljitsch van Beijnum wrote:
>
> To stop unnecessary DHCP traffic. [...]

I think what we're seeing here is a vocal faction of the community who
believe that DHCP discovery multicasts are always necessary, whether RA
is present or not, and whether M=3D0 or M=3D1, despite the text in RFC =
2462.

Here's what they seem to be saying: wherever a DHCP server *may* be
present, DHCP discovery *MUST NOT* be prevented and *SHOULD NOT* be
delayed.  If you agree with that, then perhaps it also makes sense to
move prefix and default gateway assignment into DHCP for the purpose of
improving efficiency.  The DHCP advocates seem to view RA with M=3D1 as
basically superfluous to the process, unless it can be made to signal
effectively that nodes *MUST NOT* perform stateless autoconfiguration.
Alas, unfortunately for them, RFC 2462 doesn't do that.  In fact, it
explicitly states that a node *may* always perform stateless autoconf
after receiving RA with M=3D0 containing a PIO with A=3D1, and hence the
kvetching about rogue advertisers.

There is a closely related problem here in the language of RFC 2462.  =20
Notice how the state of the ManagedFlag conceptual variable is specified
during processing of Router Advertisements.

> Section 5.2 Autoconfiguration-Related Variables
>
>  Hosts maintain the following variables on a per-interface basis:
>
>       ManagedFlag      Copied from the M flag field (i.e., the
>                        "managed address configuration" flag) of the=20
> most
>                        recently received Router Advertisement message.
>                        The flag indicates whether or not addresses are
>                        to be configured using the stateful
>                        autoconfiguration mechanism. It starts out in a
>                        FALSE state.
[...]
> 5.5.3.  Router Advertisement Processing
>
>    On receipt of a valid Router Advertisement (as defined in
>    [DISCOVERY]), a host copies the value of the advertisement's M bit
>    into ManagedFlag. If the value of ManagedFlag changes from FALSE to
>    TRUE, and the host is not already running the stateful address
>    autoconfiguration protocol, the host should invoke the stateful
>    address autoconfiguration protocol, requesting both address
>    information and other information.  If the value of the ManagedFlag
>    changes from TRUE to FALSE, the host should continue running the
>    stateful address autoconfiguration, i.e., the change in the value=20
> of
>    the ManagedFlag has no effect.  If the value of the flag stays
>    unchanged, no special action takes place. In particular, a host=20
> MUST
>    NOT reinvoke stateful address configuration if it is already
>    participating in the stateful protocol as a result of an earlier
>    advertisement.

I see only one invocation of RFC 2119 requirements language in there,
and it's to apply a curious injunction not to restart DHCP discovery
every time RA with M=3D1 is received while ManagedFlag is TRUE.  All the
rest of the verbiage about the ManagedFlag conceptual variable amounts
to a recommendation that DHCP discovery should be deferred until the
first receipt of RA with M=3D1 at the interface and should remain in
operation until the interface disconnects.  One interesting consequence
of this verbiage is that it recommends setting the ManagedFlag to FALSE
upon receiving RA with M=3D0.  When the next RA arrives with M=3D1, the =
node
will then be free to restart DHCP =20
discovery because the above requirement will no longer apply.  =20
(Whether it *will* is not specified.)  This basically nullifies the
utility of the one instance of RFC 2119 requirements language in how the
ManagedFlag is to be handled during RA processing.

As I said, it's very curious.

I think the new 6MAN working group should take up a project of
clarifying the requirements for processing router advertisements in
IPv6 nodes.

On a related note, I've heard that some operators intend to deploy DHCP
service using RA with M=3D1 and no PIO.  I don't understand how =20
they imagine the "on-link flag" to be propagated in that scenario.  =20
The "on-link flag" seems to be clearly in the domain of router function,
not dynamic node configuration.  Is that to be described in the
forthcoming Internet draft?


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



_______________________________________________
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 Aug 17 21:31:06 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMD7u-0004iU-8J; Fri, 17 Aug 2007 21:29:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMD7t-0004iL-4p; Fri, 17 Aug 2007 21:29:17 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IMD7s-0002IU-Mx; Fri, 17 Aug 2007 21:29:17 -0400
Received: from relay6.apple.com (relay6.apple.com [17.128.113.36])
	by mail-out4.apple.com (Postfix) with ESMTP id 0DFA3F29E1E;
	Fri, 17 Aug 2007 18:29:16 -0700 (PDT)
Received: from relay6.apple.com (unknown [127.0.0.1])
	by relay6.apple.com (Symantec Mail Security) with ESMTP id F0A8B100E1; 
	Fri, 17 Aug 2007 18:29:15 -0700 (PDT)
X-AuditID: 11807124-a5fb9bb0000007f3-38-46c64b6b744f
Received: from [17.206.23.199] (il0602a-dhcp71.apple.com [17.206.23.199])
	by relay6.apple.com (Apple SCV relay) with ESMTP id E0484100A4;
	Fri, 17 Aug 2007 18:29:15 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D0388161A@xmb-rtp-20e.amer.cisco.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
	<FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
	<8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
	<A822303F-0054-4462-866F-1689EBFE9958@apple.com> <6354B72
	A-EC4E-40DB-9A50-01036B1FEE39@apple.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388161A@xmb-rtp-20e.amer.cisco.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <E6C4EE3C-1D37-44E8-B2AA-6D6C5C2732D3@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Fri, 17 Aug 2007 18:29:05 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>,
 dhcwg@ietf.org
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: 
Subject: [dhcwg] Re: on-link determination and DHCP6
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 Aug 17, 2007, at 17:31, Hemant Singh (shemant) wrote:
> [I wrote:]
>> On a related note, I've heard that some operators intend to deploy  
>> DHCP
>> service using RA with M=1 and no PIO.  I don't understand how
>> they imagine the "on-link flag" to be propagated in that scenario.
>> The "on-link flag" seems to be clearly in the domain of router  
>> function,
>> not dynamic node configuration.  Is that to be described in the
>> forthcoming Internet draft?
>
> In an aggregation router network, all host behind broadband modems are
> always off-link as we have explained in this mailer - see one of my
> emails.
>
> So there is NO NEED to propagate any on-link flag is such a network.

I suppose accepting the consequences of not being able to propagate  
the "on-link flag" is one way to handle the problem.  I hope section  
2.1 of the ND Implementation Pitfalls draft will be reviewed  
carefully by everyone participating in the discussions about prefix  
length determination in DHCP6.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



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



From dhcwg-bounces@ietf.org Sat Aug 18 01:05:39 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMGTV-0007U6-Ix; Sat, 18 Aug 2007 01:03:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IMGTU-0007U1-T3
	for dhcwg@ietf.org; Sat, 18 Aug 2007 01:03:48 -0400
Received: from mail119.messagelabs.com ([216.82.241.179])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IMGTT-00081m-Lj
	for dhcwg@ietf.org; Sat, 18 Aug 2007 01:03:48 -0400
X-VirusChecked: Checked
X-Env-Sender: Q4997C@motorola.com
X-Msg-Ref: server-10.tower-119.messagelabs.com!1187413426!23964839!1
X-StarScan-Version: 5.5.12.11; banners=-,-,-
X-Originating-IP: [144.189.100.101]
Received: (qmail 12024 invoked from network); 18 Aug 2007 05:03:46 -0000
Received: from motgate2.mot.com (HELO motgate2.mot.com) (144.189.100.101)
	by server-10.tower-119.messagelabs.com with SMTP;
	18 Aug 2007 05:03:46 -0000
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate2.mot.com (8.12.11/Motorola) with ESMTP id l7I53jBv023213
	for <dhcwg@ietf.org>; Fri, 17 Aug 2007 22:03:45 -0700 (MST)
Received: from az10vts01 (az10vts01.mot.com [10.64.251.242])
	by az33exr01.mot.com (8.13.1/Vontu) with SMTP id l7I53j5o016811
	for <dhcwg@ietf.org>; Sat, 18 Aug 2007 00:03:45 -0500 (CDT)
Received: from ZMY16EXM66.ds.mot.com (zmy16exm66.ap.mot.com [10.179.4.26])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id l7I53gDI016805
	for <dhcwg@ietf.org>; Sat, 18 Aug 2007 00:03:44 -0500 (CDT)
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: Sat, 18 Aug 2007 13:03:43 +0800
Message-ID: <750BBC72E178114F9DC4872EBFF29A5B04E7312D@ZMY16EXM66.ds.mot.com>
In-Reply-To: <750BBC72E178114F9DC4872EBFF29A5B04E72DC8@ZMY16EXM66.ds.mot.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: How to install dhcp-3.0.6
thread-index: AcfgMQ2k2wEfSh7fRvGaQBWOutbhtAAX1nlgADErByA=
From: "Aggarwal Vivek-Q4997C" <Q4997C@motorola.com>
To: <dhcwg@ietf.org>, <dhcp-users@isc.org>
X-Vontu: Pass
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: 
Subject: [dhcwg] How to install dhcp-3.0.6
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

Im having LINUX ES verion 4 system.

I downloaded source file dhcp-3.0.6.tar.gz from the isc site.

How can I make dhcp3.0.6 work on my system , is it possible or not

Firstly I downloaded and copied the file to the root dir

Did tar then ./configure, nut Im unable make it
It says make 1 error all

Can you please help in the matter

Basically I want to use dhcp-3.0.6 on RedHat ES Version 4, How can I do
that


Regards
Vivek Aggarwal

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

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



From dhcwg-bounces@ietf.org Sat Aug 18 11:30:48 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEX-0000Xn-Ox; Sat, 18 Aug 2007 11:29:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKwGQ-0006db-TQ; Tue, 14 Aug 2007 09:16:50 -0400
Received: from brmea-mail-4.sun.com ([192.18.98.36])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IKwGP-0001A7-Jb; Tue, 14 Aug 2007 09:16:50 -0400
Received: from dm-east-01.east.sun.com ([129.148.9.192])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l7EDGmSW004319; Tue, 14 Aug 2007 13:16:48 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by dm-east-01.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP
	id l7EDGmYu031381; Tue, 14 Aug 2007 09:16:48 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l7ECh4wg012550; Tue, 14 Aug 2007 08:43:04 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l7ECh21u012547;
	Tue, 14 Aug 2007 08:43:02 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18113.41813.884894.99500@gargle.gargle.HOWL>
Date: Tue, 14 Aug 2007 08:43:01 -0400
From: James Carlson <james.d.carlson@sun.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <B0259697-1C66-4053-AD82-661A54733544@muada.com>
References: <8E296595B6471A4689555D5D725EBB2104B66C24@xmb-rtp-20a.amer.cisco.com>
	<B0259697-1C66-4053-AD82-661A54733544@muada.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:56 -0400
Cc: Bernie Volz <volz@cisco.com>
Subject: [dhcwg] Re: prefix length determination 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

Iljitsch van Beijnum writes:
> On 13-aug-2007, at 19:25, Bernie Volz ((volz)) wrote:
> 
> > DHCPv6 messages are generally small and don't require a lot of back  
> > and
> > further. I really don't understand why people are objecting to one or
> > two request/reply exchanges (only the request of which is multicast).
> > Sure, it be nice if there were zero messages, but we're basically down
> > to as few as possible and most of these messages are tiny (especially
> > compared to the 300+ bytes that is the minimal size of DHCPv4  
> > messages).
> 
> It adds up if you have a large number of hosts on a subnet.

I doubt it.  It's something you do just when you're configuring the
interface, and then you're done.

If you're in fact in the state where you can't even bear the load of
configuring the interfaces, then I suspect that neighbor discovery,
DNS, and plain old user data traffic will overwhelm you.  DHCPv6
(using Information Request or Rapid Commit) is just two packets when
the interface is configured.  All those other protocols are going to
add dozens, hundreds, or more for each host.

> Which got me thinking: wouldn't it be great if a single message from  
> a host could serve as both a router solicitation and a DHCP solicit  
> message?

I'm not wild about the idea of a single message getting replies from
two separate entities.  I suppose it's doable, but it seems like
needless complexity.  What is being optimized and why?

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781From dhcwg-bounces@ietf.org Sat Aug 18 11:30:48 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEX-0000Xn-Ox; Sat, 18 Aug 2007 11:29:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKwGQ-0006db-TQ; Tue, 14 Aug 2007 09:16:50 -0400
Received: from brmea-mail-4.sun.com ([192.18.98.36])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IKwGP-0001A7-Jb; Tue, 14 Aug 2007 09:16:50 -0400
Received: from dm-east-01.east.sun.com ([129.148.9.192])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l7EDGmSW004319; Tue, 14 Aug 2007 13:16:48 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by dm-east-01.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP
	id l7EDGmYu031381; Tue, 14 Aug 2007 09:16:48 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l7ECh4wg012550; Tue, 14 Aug 2007 08:43:04 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l7ECh21u012547;
	Tue, 14 Aug 2007 08:43:02 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18113.41813.884894.99500@gargle.gargle.HOWL>
Date: Tue, 14 Aug 2007 08:43:01 -0400
From: James Carlson <james.d.carlson@sun.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <B0259697-1C66-4053-AD82-661A54733544@muada.com>
References: <8E296595B6471A4689555D5D725EBB2104B66C24@xmb-rtp-20a.amer.cisco.com>
	<B0259697-1C66-4053-AD82-661A54733544@muada.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:56 -0400
Cc: Bernie Volz <volz@cisco.com>
Subject: [dhcwg] Re: prefix length determination 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

Iljitsch van Beijnum writes:
> On 13-aug-2007, at 19:25, Bernie Volz ((volz)) wrote:
> 
> > DHCPv6 messages are generally small and don't require a lot of back  
> > and
> > further. I really don't understand why people are objecting to one or
> > two request/reply exchanges (only the request of which is multicast).
> > Sure, it be nice if there were zero messages, but we're basically down
> > to as few as possible and most of these messages are tiny (especially
> > compared to the 300+ bytes that is the minimal size of DHCPv4  
> > messages).
> 
> It adds up if you have a large number of hosts on a subnet.

I doubt it.  It's something you do just when you're configuring the
interface, and then you're done.

If you're in fact in the state where you can't even bear the load of
configuring the interfaces, then I suspect that neighbor discovery,
DNS, and plain old user data traffic will overwhelm you.  DHCPv6
(using Information Request or Rapid Commit) is just two packets when
the interface is configured.  All those other protocols are going to
add dozens, hundreds, or more for each host.

> Which got me thinking: wouldn't it be great if a single message from  
> a host could serve as both a router solicitation and a DHCP solicit  
> message?

I'm not wild about the idea of a single message getting replies from
two separate entities.  I suppose it's doable, but it seems like
needless complexity.  What is being optimized and why?

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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

From dhcwg-bounces@ietf.org Sat Aug 18 11:30:48 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEW-0000Xh-Rt; Sat, 18 Aug 2007 11:29:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJrFn-0004qa-LZ; Sat, 11 Aug 2007 09:43:43 -0400
Received: from coconut.itojun.org ([2001:240:501:0:204:23ff:fecb:8908])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IJrFn-0006Zx-8K; Sat, 11 Aug 2007 09:43:43 -0400
Received: by coconut.itojun.org (Postfix, from userid 501)
	id BCC3523411; Sat, 11 Aug 2007 22:43:36 +0900 (JST)
To: mohta@necom830.hpcl.titech.ac.jp
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
In-Reply-To: Your message of "Sat, 11 Aug 2007 21:26:44 +0900"
	<46BDAB04.10400@necom830.hpcl.titech.ac.jp>
References: <46BDAB04.10400@necom830.hpcl.titech.ac.jp>
X-Mailer: Cue version 0.8 (070521-1856/itojun)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20070811134336.BCC3523411@coconut.itojun.org>
Date: Sat, 11 Aug 2007 22:43:36 +0900 (JST)
From: itojun@itojun.org (Jun-ichiro itojun Hagino)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:56 -0400
Cc: ipv6@ietf.org, volz@cisco.com, iljitsch@muada.com, jjmb@jjmb.com,
	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

> You shouldn't.
> 
> You SHOULD remember that ND is *NOT* mandately for IPv6.

	just for clarification - which part of ND (RS/RA, NS/NA, or something
	else), and under which condition?

itojun

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





 442 1677

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

From dhcwg-bounces@ietf.org Sat Aug 18 11:30:48 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEW-0000Xh-Rt; Sat, 18 Aug 2007 11:29:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJrFn-0004qa-LZ; Sat, 11 Aug 2007 09:43:43 -0400
Received: from coconut.itojun.org ([2001:240:501:0:204:23ff:fecb:8908])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IJrFn-0006Zx-8K; Sat, 11 Aug 2007 09:43:43 -0400
Received: by coconut.itojun.org (Postfix, from userid 501)
	id BCC3523411; Sat, 11 Aug 2007 22:43:36 +0900 (JST)
To: mohta@necom830.hpcl.titech.ac.jp
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
In-Reply-To: Your message of "Sat, 11 Aug 2007 21:26:44 +0900"
	<46BDAB04.10400@necom830.hpcl.titech.ac.jp>
References: <46BDAB04.10400@necom830.hpcl.titech.ac.jp>
X-Mailer: Cue version 0.8 (070521-1856/itojun)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20070811134336.BCC3523411@coconut.itojun.org>
Date: Sat, 11 Aug 2007 22:43:36 +0900 (JST)
From: itojun@itojun.org (Jun-ichiro itojun Hagino)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:56 -0400
Cc: ipv6@ietf.org, volz@cisco.com, iljitsch@muada.com, jjmb@jjmb.com,
	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

> You shouldn't.
> 
> You SHOULD remember that ND is *NOT* mandately for IPv6.

	just for clarification - which part of ND (RS/RA, NS/NA, or something
	else), and under which condition?

itojun

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





From dhcwg-bounces@ietf.org Sat Aug 18 11:30:50 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEY-0000Y6-UD; Sat, 18 Aug 2007 11:29:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILFv3-0001Mi-UX; Wed, 15 Aug 2007 06:16:05 -0400
Received: from levanto.mail.adnap.net.au ([203.6.132.83])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILFv2-0000b9-1H; Wed, 15 Aug 2007 06:16:05 -0400
Received: from 219-90-167-43.ip.adam.com.au ([219.90.167.43]
	helo=mail.nosense.org)
	by levanto.mail.adnap.net.au with esmtp (Exim 4.63 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1ILFur-000DzX-Pq; Wed, 15 Aug 2007 19:45:53 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id 0A5BCFC8B;
	Wed, 15 Aug 2007 19:45:52 +0930 (CST)
Date: Wed, 15 Aug 2007 19:45:51 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Message-Id: <20070815194551.e2264a08.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
References: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
X-Mailer: Sylpheed 2.4.4 (GTK+ 2.10.14; i686-pc-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:56 -0400
Cc: "volz <volz@cisco.com>, dhcwg@ietf.org, ipv6@ietf.org,
	\"John Jason Brzozowski \(JJMB\)\" <jjmb@jjmb.com>" <Bernie>
Subject: [dhcwg] Re: prefix length determination 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

On Mon, 13 Aug 2007 11:55:46 +0200
Iljitsch van Beijnum <iljitsch@muada.com> wrote:

<snip>
> 
> I disagree. For better or for worse, the notion of a subnet mask  
> going along with an interface address is deeply ingrained in the way  
> IP is implemented. Separating the two for no apparent reason is a bad  
> idea.
> 

I think you need to modify the following sentence as such:

"For better or for worse, the notion of a subnet mask  
 going along with an interface address is deeply ingrained in the way  
**IPv4** is implemented."

That being said, it's not quite as ingrained as you might think it is.

The original, pre-classful IPv4 address format was
Network.Node.Node.Node - see RFC760, section 3.1. In addition to
describing IPv4 addresses in this form, IEN115 also describes how a few
different layer 2 addresses can be embedded/converted directly into the
Node.Node.Node octets.

Classes A, B and C where then specified in RFC791, section 3.2.

(ARP could seem to be a "hack" to cope with not being able to squeeze an
ethernet address or any other >3, >2 or >1 octet layer 2 address into
the node portion of class A, B or C format addresses.)

Then subnets came along, and then of course CIDR was introduced.

I think all of this additional addressing complexity was the price to
be paid for scaling IPv4 addressing way beyond what was originally
expected.

Fixed length node addressing is good because it's simpler, easier to
work with, and therefore cheaper to operate. I think anybody who has
worked with Novell IPX (like me) or Appletalk would agree. Both of
those have fixed length node portions.

IPv6, at least for the node portion, is returning to the intentions of
RFC760 era IPv4 without the scaling limitations that were inherent in
IPv4's 32 bit address space.

A fixed length network portion is also simpler and easier to administer
and operate if you have the opportunity, which is why I'm an advocate
for /48s for nearly everybody. Leaving the problems of dealing with the
complexity of variable length prefixes to the expert employees of the
network service providers, not their customers, makes good sense to me.
Again, I think people who've worked with Novell IPX or Appletalk would
also agree.

Regards,
Mark.

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



From dhcwg-bounces@ietf.org Sat Aug 18 11:30:55 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEc-0000fi-Rl; Sat, 18 Aug 2007 11:29:06 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM4tM-0008Vy-Kz; Fri, 17 Aug 2007 12:41:44 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IM4tM-00067B-9d; Fri, 17 Aug 2007 12:41:44 -0400
Received: from relay7.apple.com (relay7.apple.com [17.128.113.37])
	by mail-out3.apple.com (Postfix) with ESMTP id A741EEBFE10;
	Fri, 17 Aug 2007 09:41:43 -0700 (PDT)
Received: from relay7.apple.com (unknown [127.0.0.1])
	by relay7.apple.com (Symantec Mail Security) with ESMTP id 8F74F300C6; 
	Fri, 17 Aug 2007 09:41:43 -0700 (PDT)
X-AuditID: 11807125-a1a1dbb0000007e5-14-46c5cfc7a382
Received: from et.apple.com (et.apple.com [17.151.62.12])
	by relay7.apple.com (Apple SCV relay) with ESMTP id 78AE9300B7;
	Fri, 17 Aug 2007 09:41:43 -0700 (PDT)
Received: from [10.21.59.71] ([32.151.254.168])
	by et.apple.com (Sun Java System Messaging Server 6.2-8.04 (built Feb
	28 2007)) with ESMTPSA id <0JMX002W5FPEOO40@et.apple.com>; Fri,
	17 Aug 2007 09:41:43 -0700 (PDT)
Date: Fri, 17 Aug 2007 09:41:33 -0700
From: James Woodyatt <jhw@apple.com>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
In-reply-to: <39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Message-id: <A822303F-0054-4462-866F-1689EBFE9958@apple.com>
MIME-version: 1.0
X-Mailer: iPhone Mail (1C25)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
	<FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
	<8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:57 -0400
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, "ipv6@ietf.org" <ipv6@ietf.org>,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>,
	"dhcwg@ietf.org" <dhcwg@ietf.org>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Aug 17, 2007, at 6:59 AM, "Templin, Fred L" <Fred.L.Templin@boeing.com 
 > wrote:

>> How can that happen with a DHCPv6 host? RA will always precede DHCPv6
>> transactions because unless the host sees an RA with M bit set the
> host
>> will not initiate DHCPv6.
>
> That doesn't make much sense; if a node doesn't hear
> RAs, why wouldn't it try DHCPv6 before giving up?

It seems to me that the semantic content of RA with M=1 is to signal  
to DHCP-capable nodes that no further delay is necessary... DHCP  
discovery can proceed immediately.

One wonders why they would bother waiting in the first place given the  
significant probability that DHCP service is deployed without any RA  
whatsoever.

So, it seems natural to ask... what good is the M bit anyway?

-jhw

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



From dhcwg-bounces@ietf.org Sat Aug 18 11:30:55 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEZ-0000YL-BX; Sat, 18 Aug 2007 11:29:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILIwB-0001Sv-Gk; Wed, 15 Aug 2007 09:29:27 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILIwA-0004nD-Qa; Wed, 15 Aug 2007 09:29:27 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 15 Aug 2007 09:29:26 -0400
X-IronPort-AV: i="4.19,267,1183348800"; 
	d="scan'208"; a="68058994:sNHT60735660"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7FDTQP5028221; 
	Wed, 15 Aug 2007 09:29:26 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7FDTLjU019633; 
	Wed, 15 Aug 2007 13:29:26 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Aug 2007 09:29: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="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Subject: RE: [dhcwg] RE: prefix length determination for DHCPv6
Date: Wed, 15 Aug 2007 09:29:45 -0400
Message-ID: <CA8EB93B28BD0F4C88392699600BD6550414236B@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <E2E6A987-046A-44D9-923F-F17F95AFFDD2@apple.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] RE: prefix length determination for DHCPv6
Thread-Index: AcfezO2TXoDD+pLGSOeCuz7NrDWpcwActG5w
From: "Wes Beebee \(wbeebee\)" <wbeebee@cisco.com>
To: "james woodyatt" <jhw@apple.com>, "IETF IPv6 Mailing List" <ipv6@ietf.org>
X-OriginalArrivalTime: 15 Aug 2007 13:29:05.0983 (UTC)
	FILETIME=[40B4A4F0:01C7DF40]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2413; t=1187184566;
	x=1188048566; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wbeebee@cisco.com;
	z=From:=20=22Wes=20Beebee=20\(wbeebee\)=22=20<wbeebee@cisco.com>
	|Subject:=20RE=3A=20[dhcwg]=20RE=3A=20prefix=20length=20determination=20f
	or=20DHCPv6 |Sender:=20
	|To:=20=22james=20woodyatt=22=20<jhw@apple.com>,
	=20=22IETF=20IPv6=20Maili ng=20List=22=20<ipv6@ietf.org>;
	bh=ucnErZHx5j4Mn1xh79p0OMp6rrnQPTN0PQoMwQv9o1c=;
	b=bLgDeC6V4VTvcRZM9e07qxj5tJtYO2DQBCc68GQr8CS4Ijdp+twciAaNuGmb/XZPidx0Xzi0
	olH7e9FWdqtY/Cz/d/tloiPgFSLnoN+iE8za+VEUQnh/VdeylBJFj/qC;
Authentication-Results: rtp-dkim-1; header.From=wbeebee@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:57 -0400
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

DHCPv6 is useful when MSO's want to control which CPE's get addresses and which 
do not.  It provides a simple way to do access control on a network.  Could a 
hacked-up rogue system still manage to get on?  Probably - but at least it bars
casual users from getting on a network that they're not supposed to.

- Wes

-----Original Message-----
From: james woodyatt [mailto:jhw@apple.com] 
Sent: Tuesday, August 14, 2007 7:42 PM
To: IETF IPv6 Mailing List
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6

On Aug 13, 2007, at 09:10, David W. Hankins wrote:
> On Sat, Aug 11, 2007 at 05:51:09PM +0900, JINMEI Tatuya / $B?@L@C#(J
> $B:H(J wrote:
>>
>> In any event, I hear that some DHCPv6 guys are planning to make a new 
>> draft that covers this topic.  So I think it's better to hold off for 
>> now and wait for the document, rather than continue this thread with 
>> keeping possible misunderstanding or confusing about the base 
>> protocol principles.
>
> I agree with everything Jinmei said, but this in particular.  Any 
> conclusions from these threads have a tendency to get forgotten - it's 
> better that we argue the position of a draft that an editor can follow 
> consensus.

I agree with M. Jinmei as far as the quoted excerpt above goes.

As much as I dislike DHCPv6 on general principle, I don't expect that IETF will abandon it in favor of a system that more coherently addresses the various separate concerns that DHCPv6 attempts to meet.  I hope the DHC WG will specify requirements for routers sending advertisements with the M bit set that prevent any ambiguity from arising at the node during link configuration.

p.s. I really wish IETF had deprecated DHCPv6 when it had the chance.  Every last thing DHCPv6 does belongs in one of two other, separate domains, i.e. either in the sub-IP layer, e.g. EAP, or at the sub-application layer, e.g. DNS-SD.  Instead, IETF chose a short- sighted and half-baked solution to a problem that really didn't need a rush job to solve, and the engineering community today is poorer for it.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

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



From dhcwg-bounces@ietf.org Sat Aug 18 11:30:55 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEc-0000fi-Rl; Sat, 18 Aug 2007 11:29:06 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM4tM-0008Vy-Kz; Fri, 17 Aug 2007 12:41:44 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IM4tM-00067B-9d; Fri, 17 Aug 2007 12:41:44 -0400
Received: from relay7.apple.com (relay7.apple.com [17.128.113.37])
	by mail-out3.apple.com (Postfix) with ESMTP id A741EEBFE10;
	Fri, 17 Aug 2007 09:41:43 -0700 (PDT)
Received: from relay7.apple.com (unknown [127.0.0.1])
	by relay7.apple.com (Symantec Mail Security) with ESMTP id 8F74F300C6; 
	Fri, 17 Aug 2007 09:41:43 -0700 (PDT)
X-AuditID: 11807125-a1a1dbb0000007e5-14-46c5cfc7a382
Received: from et.apple.com (et.apple.com [17.151.62.12])
	by relay7.apple.com (Apple SCV relay) with ESMTP id 78AE9300B7;
	Fri, 17 Aug 2007 09:41:43 -0700 (PDT)
Received: from [10.21.59.71] ([32.151.254.168])
	by et.apple.com (Sun Java System Messaging Server 6.2-8.04 (built Feb
	28 2007)) with ESMTPSA id <0JMX002W5FPEOO40@et.apple.com>; Fri,
	17 Aug 2007 09:41:43 -0700 (PDT)
Date: Fri, 17 Aug 2007 09:41:33 -0700
From: James Woodyatt <jhw@apple.com>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
In-reply-to: <39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Message-id: <A822303F-0054-4462-866F-1689EBFE9958@apple.com>
MIME-version: 1.0
X-Mailer: iPhone Mail (1C25)
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-transfer-encoding: 7BIT
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
	<FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
	<8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:57 -0400
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, "ipv6@ietf.org" <ipv6@ietf.org>,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>,
	"dhcwg@ietf.org" <dhcwg@ietf.org>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Aug 17, 2007, at 6:59 AM, "Templin, Fred L" <Fred.L.Templin@boeing.com 
 > wrote:

>> How can that happen with a DHCPv6 host? RA will always precede DHCPv6
>> transactions because unless the host sees an RA with M bit set the
> host
>> will not initiate DHCPv6.
>
> That doesn't make much sense; if a node doesn't hear
> RAs, why wouldn't it try DHCPv6 before giving up?

It seems to me that the semantic content of RA with M=1 is to signal  
to DHCP-capable nodes that no further delay is necessary... DHCP  
discovery can proceed immediately.

One wonders why they would bother waiting in the first place given the  
significant probability that DHCP service is deployed without any RA  
whatsoever.

So, it seems natural to ask... what good is the M bit anyway?

-jhw

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



From dhcwg-bounces@ietf.org Sat Aug 18 11:30:55 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEZ-0000YL-BX; Sat, 18 Aug 2007 11:29:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILIwB-0001Sv-Gk; Wed, 15 Aug 2007 09:29:27 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILIwA-0004nD-Qa; Wed, 15 Aug 2007 09:29:27 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 15 Aug 2007 09:29:26 -0400
X-IronPort-AV: i="4.19,267,1183348800"; 
	d="scan'208"; a="68058994:sNHT60735660"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7FDTQP5028221; 
	Wed, 15 Aug 2007 09:29:26 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7FDTLjU019633; 
	Wed, 15 Aug 2007 13:29:26 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Aug 2007 09:29: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="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
Subject: RE: [dhcwg] RE: prefix length determination for DHCPv6
Date: Wed, 15 Aug 2007 09:29:45 -0400
Message-ID: <CA8EB93B28BD0F4C88392699600BD6550414236B@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <E2E6A987-046A-44D9-923F-F17F95AFFDD2@apple.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] RE: prefix length determination for DHCPv6
Thread-Index: AcfezO2TXoDD+pLGSOeCuz7NrDWpcwActG5w
From: "Wes Beebee \(wbeebee\)" <wbeebee@cisco.com>
To: "james woodyatt" <jhw@apple.com>, "IETF IPv6 Mailing List" <ipv6@ietf.org>
X-OriginalArrivalTime: 15 Aug 2007 13:29:05.0983 (UTC)
	FILETIME=[40B4A4F0:01C7DF40]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2413; t=1187184566;
	x=1188048566; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=wbeebee@cisco.com;
	z=From:=20=22Wes=20Beebee=20\(wbeebee\)=22=20<wbeebee@cisco.com>
	|Subject:=20RE=3A=20[dhcwg]=20RE=3A=20prefix=20length=20determination=20f
	or=20DHCPv6 |Sender:=20
	|To:=20=22james=20woodyatt=22=20<jhw@apple.com>,
	=20=22IETF=20IPv6=20Maili ng=20List=22=20<ipv6@ietf.org>;
	bh=ucnErZHx5j4Mn1xh79p0OMp6rrnQPTN0PQoMwQv9o1c=;
	b=bLgDeC6V4VTvcRZM9e07qxj5tJtYO2DQBCc68GQr8CS4Ijdp+twciAaNuGmb/XZPidx0Xzi0
	olH7e9FWdqtY/Cz/d/tloiPgFSLnoN+iE8za+VEUQnh/VdeylBJFj/qC;
Authentication-Results: rtp-dkim-1; header.From=wbeebee@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:57 -0400
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

DHCPv6 is useful when MSO's want to control which CPE's get addresses and which 
do not.  It provides a simple way to do access control on a network.  Could a 
hacked-up rogue system still manage to get on?  Probably - but at least it bars
casual users from getting on a network that they're not supposed to.

- Wes

-----Original Message-----
From: james woodyatt [mailto:jhw@apple.com] 
Sent: Tuesday, August 14, 2007 7:42 PM
To: IETF IPv6 Mailing List
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6

On Aug 13, 2007, at 09:10, David W. Hankins wrote:
> On Sat, Aug 11, 2007 at 05:51:09PM +0900, JINMEI Tatuya / $B?@L@C#(J
> $B:H(J wrote:
>>
>> In any event, I hear that some DHCPv6 guys are planning to make a new 
>> draft that covers this topic.  So I think it's better to hold off for 
>> now and wait for the document, rather than continue this thread with 
>> keeping possible misunderstanding or confusing about the base 
>> protocol principles.
>
> I agree with everything Jinmei said, but this in particular.  Any 
> conclusions from these threads have a tendency to get forgotten - it's 
> better that we argue the position of a draft that an editor can follow 
> consensus.

I agree with M. Jinmei as far as the quoted excerpt above goes.

As much as I dislike DHCPv6 on general principle, I don't expect that IETF will abandon it in favor of a system that more coherently addresses the various separate concerns that DHCPv6 attempts to meet.  I hope the DHC WG will specify requirements for routers sending advertisements with the M bit set that prevent any ambiguity from arising at the node during link configuration.

p.s. I really wish IETF had deprecated DHCPv6 when it had the chance.  Every last thing DHCPv6 does belongs in one of two other, separate domains, i.e. either in the sub-IP layer, e.g. EAP, or at the sub-application layer, e.g. DNS-SD.  Instead, IETF chose a short- sighted and half-baked solution to a problem that really didn't need a rush job to solve, and the engineering community today is poorer for it.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

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



From dhcwg-bounces@ietf.org Sat Aug 18 11:31:00 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEZ-0000YB-4S; Sat, 18 Aug 2007 11:29:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILIhy-0002wN-RH; Wed, 15 Aug 2007 09:14:46 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILIhu-0004Pb-JG; Wed, 15 Aug 2007 09:14:46 -0400
Received: from [82.192.90.28] (nirrti.muada.com [82.192.90.28])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l7FDAvTi055447
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Wed, 15 Aug 2007 15:10:58 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <20070815194551.e2264a08.ipng@69706e6720323030352d30312d31340a.nosense.org>
References: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<20070815194551.e2264a08.ipng@69706e6720323030352d30312d31340a.nosense.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <6D53AB8B-0E6C-4E07-A140-A9150C4C024F@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Wed, 15 Aug 2007 15:13:06 +0200
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:58 -0400
Cc: "volz <volz@cisco.com>, dhcwg@ietf.org, ipv6@ietf.org,
	\"John Jason Brzozowski \(JJMB\)\" <jjmb@jjmb.com>" <Bernie>
Subject: [dhcwg] Re: prefix length determination 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

On 15-aug-2007, at 12:15, Mark Smith wrote:

>> I disagree. For better or for worse, the notion of a subnet mask
>> going along with an interface address is deeply ingrained in the way
>> IP is implemented. Separating the two for no apparent reason is a bad
>> idea.

> I think you need to modify the following sentence as such:

> "For better or for worse, the notion of a subnet mask
>  going along with an interface address is deeply ingrained in the way
> **IPv4** is implemented."

No, I was very careful about what I said. The only place that I can  
think of where you don't configure a mask along with an address is in  
the case of HSRP. EVERYWHERE else that I know of you need to specify  
it now that we have CIDR and obviously it was implied before we had  
CIDR. Yes, in IPv6, too.

We can talk long and hard about the pros and cons of this  
architecturally, but the simple truth is that changing this doesn't  
appear to buy as anything tangible and it will require huge amounts  
of work in implementations and then generate huge amounts of  
confusion in operations so PLEASE let's not go down this road.

And if you have to look back before RFC 791 to provide  
counterexamples that really doesn't disprove "ingrained" in my  
opinion...

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



From dhcwg-bounces@ietf.org Sat Aug 18 11:30:55 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEb-0000dh-94; Sat, 18 Aug 2007 11:29:05 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILmKa-0000P7-If; Thu, 16 Aug 2007 16:52:36 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1ILmKa-0004zo-09; Thu, 16 Aug 2007 16:52:36 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 16 Aug 2007 16:52:36 -0400
X-IronPort-AV: i="4.19,273,1183348800"; 
	d="scan'208"; a="129077272:sNHT74020464"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7GKqZZd002906; 
	Thu, 16 Aug 2007 16:52:35 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7GKqZjI003374; 
	Thu, 16 Aug 2007 20:52:35 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Aug 2007 16:52:35 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
Date: Thu, 16 Aug 2007 16:52:33 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D03881324@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <20070815190158.GE18683@isc.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Re: prefix length determination for DHCPv6
Thread-Index: Acff5Zd/2AFdANkASBCyUCSzgPEMVAAWnDvA
References: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com><18113.42485.158453.756815@gargle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.103258@gargle.gargle.HOWL><20070815175140.GC18683@isc.org><7t5abss7jwg.fsf@gpk-xdm-001.cisco.com><18115.17151.731654.808164@gargle.gargle.HOWL>
	<20070815190158.GE18683@isc.org>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "David W. Hankins" <David_Hankins@isc.org>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 16 Aug 2007 20:52:35.0036 (UTC)
	FILETIME=[5F59A9C0:01C7E047]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3998; t=1187297555;
	x=1188161555; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20[dhcwg]=20Re=3A=20prefix=20length=20determination=20f
	or=20DHCPv6 |Sender:=20
	|To:=20=22David=20W.=20Hankins=22=20<David_Hankins@isc.org>,
	=20<dhcwg@iet f.org>;
	bh=KqVqDczV7j8pcKMbWq2wcMl48L9JT+1+ojrasDmB38M=;
	b=MpxTyYpU62V+0gRSEkos5Qn8b5EUlPMMByXayPanEF8r5VZ7wTU3DDy1W7G94jjhTeajAWfr
	GHP8AL8DRoDb6u3DVNXN4DGH0s1fcbF8ak2QRC0Z3bjvC0/3XGPTklDD;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:56 -0400
Cc: ipv6@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

=20
Wrt:

>Either way:  You need to know the customer's address.  A DHCPv6 server
off in the weeds does not necessarily know what link local address the
client is=20
>using (because it might change without notification).=20

If the client performed DHCPv6 with server, and the deployment includes
a relay agent between client and server, then the peer-address between
relay and server lets the server know what is the link-local address of
the client. Also each time the link-local address of the client changes
for a DHCPv6 client, the client will reinitiate DHCPv6 which lets the
server know again what the latest link-local address is.

If you are talking about a more generalized DHCPv6 deployment, then show
us a topology and we can discuss it.

As for broadband operators and untrusted devices in residential homes,
one plan for IPv6 cable MSO's is to dole out a PD to an eRouter cable
modem. The PD is doled out by DHCPv6 server. DHCPv6 Lease Query protocol
can verify the cable modem eRouter traffic by sending a query by address
from relay to server.=20
A query by address will return the client information for either that
client that has been assigned that address *OR* been delegated a prefix
that contains that address. See the URL below for details on DHCPv6
Lease Query protocol.

http://www.ietf.org/internet-drafts/draft-ietf-dhc-dhcpv6-leasequery-01.
txt

Hemant

-----Original Message-----
From: David W. Hankins [mailto:David_Hankins@isc.org]=20
Sent: Wednesday, August 15, 2007 3:02 PM
To: dhcwg@ietf.org
Cc: ipv6@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6

On Wed, Aug 15, 2007 at 02:16:31PM -0400, James Carlson wrote:
> Ole Troan writes:
> > >> If you delegate a prefix, then you route to the prefix -- best
match.
> > >
> > > Yes, but how does that route get in the table, and what next-hop=20
> > > is set?  You have to know your customer's address eventually.
> >=20
> > next-hop is the link-local address though.
>=20
> Right; it's the link-local address of the router to which you've=20
> delegated the prefix.

Well, sometimes.  It depends what you're doing.

Either way:  You need to know the customer's address.  A DHCPv6 server
off in the weeds does not necessarily know what link local address the
client is using (because it might change without notification).  It may
know what global addresses the client is using (because it allocated
them), but won't if router solicition is in use.  A router solicitation
system certainly doesn't have any knowledge of which customer is which
nor what addresses global or not which they're using.

This is but one facet of a network's operation: try not to focus on it
too much.  There are potentially a multitude of reasons to know which of
your customers are online, and how to reach them.  Testing connectivity
alone (such as during a support call).

> It's not the address of every single machine on the customer's=20
> network.  In fact, knowing the addresses of the machines on the=20
> customer's network is useless, as it doesn't tell you the address of=20
> that CPE router.

I'm not sure why you make this declaration (twice now), when no one has
suggested the counterpositive.  Maybe I misunderstood Iljitsch.

> Obvious sorts of ways to get this would be to keep track of your=20
> delegations or (alternatively) use an appropriate routing protocol.

Which I think gets us back to what Iljitsch said in the first place,
except that realistically ISPs are going to find it difficult and/or
costly to trust routing information from eg broadband customers, so
really what you're looking at is some way to provide a register of your
customers' current addresses.

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

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



From dhcwg-bounces@ietf.org Sat Aug 18 11:31:05 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEc-0000f3-3z; Sat, 18 Aug 2007 11:29:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM444-0004GD-O3; Fri, 17 Aug 2007 11:48:45 -0400
Received: from [2001:4830:2502:8001::a00:7] (helo=phoenix.gargantuan.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IM444-0000CL-Ac; Fri, 17 Aug 2007 11:48:44 -0400
Received: by phoenix.gargantuan.com (Postfix, from userid 1001)
	id 88BD4C4; Fri, 17 Aug 2007 11:48:43 -0400 (EDT)
Date: Fri, 17 Aug 2007 11:48:43 -0400
From: "Michael W. Oliver" <michael@gargantuan.com>
To: dhcwg@ietf.org, ipv6@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
Message-ID: <20070817154843.GA27173@gargantuan.com>
Mail-Followup-To: dhcwg@ietf.org, ipv6@ietf.org
References: <B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
MIME-Version: 1.0
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
X-WWW-URL: http://michael.gargantuan.com
X-GPG-PGP-Public-Key: http://michael.gargantuan.com/gnupg/pubkey.asc
X-GPG-PGP-Fingerprint: 0881 F6F6 F92B F8A4 A1AB  B3C3 B29C 7277 AC60 0B0E
X-Home-Phone: +1-863-816-8091
X-Mobile-Phone: +1-863-738-2334
X-Mailing-Address0: 8008 Apache Lane
X-Mailing-Address1: Lakeland, FL  33810-2172
X-Mailing-Address2: United States of America
X-Guide-Questions: http://www.catb.org/~esr/faqs/smart-questions.html
X-Guide-Netiquette: http://www.ietf.org/rfc/rfc1855.txt
User-Agent: mutt-ng/devel-r804 (FreeBSD)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:56 -0400
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0428986038=="
Errors-To: dhcwg-bounces@ietf.org


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


--cWoXeonUoKmBZSoM
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 2007-08-17T06:59:56-0700, Templin, Fred L wrote:
>> How can that happen with a DHCPv6 host? RA will always precede DHCPv6
>> transactions because unless the host sees an RA with M bit set the
>> host will not initiate DHCPv6.
>=20
> That doesn't make much sense; if a node doesn't hear
> RAs, why wouldn't it try DHCPv6 before giving up?
>=20
> Fred
> fred.l.templin@boeing.com

I agree.

If you are sending RAs from your router and simultaneously need to have
a node delegated a different length prefix than what is provided by the
RA, then DHCPv6 is the place to do it.  If there is no prefix length
specified in the DHCPv6 offer then the prefix length from the RA wins,
else DHCPv6 wins.  I can't think of any reason off of the top of my head
to do so, but why forbid the option?

If you aren't sending RAs from your router (the reasons for not sending
RAs notwithstanding), as Fred eludes, then the node needs to learn the
prefix length along with the address via DHCPv6.  If DHCPv6d authors
want to make it hard to turn this knob so that admins don't
inadvertently advertise inconsistent prefix lengths, that's their
choice, but to forbid the option in the specification seems wrong.

Regards,
Mike

--=20
Mike Oliver, KI4OFU
[see complete headers for contact information]
+----------------------------------------------------------------------+
| KI4OFU      When all else fails...AMATEUR RADIO THRIVES!      KI4OFU |
+----------------------------------------------------------------------+

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

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

iD8DBQFGxcNbboLl4ADjAhARAly7AJ0VMZ5Ik+oB9feiApkpLsucj4luFwCfe3f2
jPgRCKbul2tE2avT5ViXFRU=
=h7br
-----END PGP SIGNATURE-----

--cWoXeonUoKmBZSoM--


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

--===============0428986038==--


From dhcwg-bounces@ietf.org Sat Aug 18 11:31:05 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEa-0000a5-Co; Sat, 18 Aug 2007 11:29:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILQje-0003gf-4o; Wed, 15 Aug 2007 17:49:02 -0400
Received: from levanto.mail.adnap.net.au ([203.6.132.83])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILQjb-000343-W7; Wed, 15 Aug 2007 17:49:02 -0400
Received: from 122-49-148-154.ip.adam.com.au ([122.49.148.154]
	helo=mail.nosense.org)
	by levanto.mail.adnap.net.au with esmtp (Exim 4.63 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1ILQjT-0004N1-G7; Thu, 16 Aug 2007 07:18:51 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id 23ED9FC8B;
	Thu, 16 Aug 2007 07:18:48 +0930 (CST)
Date: Thu, 16 Aug 2007 07:18:47 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Message-Id: <20070816071847.b1ecac48.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <6D53AB8B-0E6C-4E07-A140-A9150C4C024F@muada.com>
References: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<20070815194551.e2264a08.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<6D53AB8B-0E6C-4E07-A140-A9150C4C024F@muada.com>
X-Mailer: Sylpheed 2.4.4 (GTK+ 2.10.14; i686-pc-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:56 -0400
Cc: "volz <volz@cisco.com>, dhcwg@ietf.org, ipv6@ietf.org,
	\"John Jason Brzozowski \(JJMB\)\" <jjmb@jjmb.com>" <Bernie>
Subject: [dhcwg] Re: prefix length determination 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

On Wed, 15 Aug 2007 15:13:06 +0200
Iljitsch van Beijnum <iljitsch@muada.com> wrote:

> On 15-aug-2007, at 12:15, Mark Smith wrote:
> 
> >> I disagree. For better or for worse, the notion of a subnet mask
> >> going along with an interface address is deeply ingrained in the way
> >> IP is implemented. Separating the two for no apparent reason is a bad
> >> idea.
> 
> > I think you need to modify the following sentence as such:
> 
> > "For better or for worse, the notion of a subnet mask
> >  going along with an interface address is deeply ingrained in the way
> > **IPv4** is implemented."
> 
> No, I was very careful about what I said. The only place that I can  
> think of where you don't configure a mask along with an address is in  
> the case of HSRP. EVERYWHERE else that I know of you need to sFrom dhcwg-bounces@ietf.org Sat Aug 18 11:31:05 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEc-0000f3-3z; Sat, 18 Aug 2007 11:29:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM444-0004GD-O3; Fri, 17 Aug 2007 11:48:45 -0400
Received: from [2001:4830:2502:8001::a00:7] (helo=phoenix.gargantuan.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IM444-0000CL-Ac; Fri, 17 Aug 2007 11:48:44 -0400
Received: by phoenix.gargantuan.com (Postfix, from userid 1001)
	id 88BD4C4; Fri, 17 Aug 2007 11:48:43 -0400 (EDT)
Date: Fri, 17 Aug 2007 11:48:43 -0400
From: "Michael W. Oliver" <michael@gargantuan.com>
To: dhcwg@ietf.org, ipv6@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
Message-ID: <20070817154843.GA27173@gargantuan.com>
Mail-Followup-To: dhcwg@ietf.org, ipv6@ietf.org
References: <B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
MIME-Version: 1.0
In-Reply-To: <39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
X-WWW-URL: http://michael.gargantuan.com
X-GPG-PGP-Public-Key: http://michael.gargantuan.com/gnupg/pubkey.asc
X-GPG-PGP-Fingerprint: 0881 F6F6 F92B F8A4 A1AB  B3C3 B29C 7277 AC60 0B0E
X-Home-Phone: +1-863-816-8091
X-Mobile-Phone: +1-863-738-2334
X-Mailing-Address0: 8008 Apache Lane
X-Mailing-Address1: Lakeland, FL  33810-2172
X-Mailing-Address2: United States of America
X-Guide-Questions: http://www.catb.org/~esr/faqs/smart-questions.html
X-Guide-Netiquette: http://www.ietf.org/rfc/rfc1855.txt
User-Agent: mutt-ng/devel-r804 (FreeBSD)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:56 -0400
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0428986038=="
Errors-To: dhcwg-bounces@ietf.org


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


--cWoXeonUoKmBZSoM
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 2007-08-17T06:59:56-0700, Templin, Fred L wrote:
>> How can that happen with a DHCPv6 host? RA will always precede DHCPv6
>> transactions because unless the host sees an RA with M bit set the
>> host will not initiate DHCPv6.
>=20
> That doesn't make much sense; if a node doesn't hear
> RAs, why wouldn't it try DHCPv6 before giving up?
>=20
> Fred
> fred.l.templin@boeing.com

I agree.

If you are sending RAs from your router and simultaneously need to have
a node delegated a different length prefix than what is provided by the
RA, then DHCPv6 is the place to do it.  If there is no prefix length
specified in the DHCPv6 offer then the prefix length from the RA wins,
else DHCPv6 wins.  I can't think of any reason off of the top of my head
to do so, but why forbid the option?

If you aren't sending RAs from your router (the reasons for not sending
RAs notwithstanding), as Fred eludes, then the node needs to learn the
prefix length along with the address via DHCPv6.  If DHCPv6d authors
want to make it hard to turn this knob so that admins don't
inadvertently advertise inconsistent prefix lengths, that's their
choice, but to forbid the option in the specification seems wrong.

Regards,
Mike

--=20
Mike Oliver, KI4OFU
[see complete headers for contact information]
+------------------------------------------------------------------pecify  
> it now that we have CIDR and obviously it was implied before we had  
> CIDR. Yes, in IPv6, too.
> 
> We can talk long and hard about the pros and cons of this  
> architecturally, but the simple truth is that changing this doesn't  
> appear to buy as anything tangible and it will require huge amounts  
> of work in implementations and then generate huge amounts of  
> confusion in operations so PLEASE let's not go down this road.
> 

I'm don't think I'm going down it. You seemed to be questioning why
subnets were fixed length, I provided most likelyreasons why, including
evidence that the original design of IPv4, pre-classes, also followed
this model. I think that shows that when there is the opportunity to
have fixed length node addressing it is very desirable, and has been
chosen by many protocol designers (DECNET Phase IV has it too, IIRC)

I like that IPv6 can place the boundary between the network and node
portion anywhere within the address, unlike IPX and Appletalk. It
future proofs the protocol, ensuring that should the network or node
portions not be big enough they can be changed, and devices will be
able to cope with it without software upgrades.

OTOH, I don't like _unnecessary_ complexity. Currently,
we don't need to engage any of the complexity of non-fixed network and
node portion boundaries in IPv6, so let's not until we need to.
Allowing for something doesn't mean you must use it.

Simplicity is what we get when we eliminate/avoid/choose not to use
variable length subnets, and it is a very tangible property, well worth
pursuing. I could probably save 5 minutes per day at work if I didn't
having to think through or calculate variable length subnet masks in
IPv4. That's 1200 minutes or 20 hours a year. Multiply that by how many
operators there are out there spending that 5 minutes or more per day
and it's a huge amount of spent time. That's a necessary expense when
dealing with IPv4, but not a necessary one for IPv6. If it's not
necessary, then it's wasted time.


> And if you have to look back before RFC 791 to provide  
> counterexamples that really doesn't disprove "ingrained" in my  
> opinion...

That's probably a fair critism. I was mainly replying to what I've
realised was an earlier question of yours, regarding why fixed length
subnets. The ingrained bit seemed to me to suggesting that fixed length
subnets would be considered to be a radical idea and wouldn't be
acceptable to those that have led sheltered protocol lives and only
ever dealt with IPv4, post 1995.

Regards,
Mark.

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





----+
| KI4OFU      When all else fails...AMATEUR RADIO THRIVES!      KI4OFU |
+----------------------------------------------------------------------+

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

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

iD8DBQFGxcNbboLl4ADjAhARAly7AJ0VMZ5Ik+oB9feiApkpLsucj4luFwCfe3f2
jPgRCKbul2tE2avT5ViXFRU=
=h7br
-----END PGP SIGNATURE-----

--cWoXeonUoKmBZSoM--


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

--===============0428986038==--


From dhcwg-bounces@ietf.org Sat Aug 18 11:31:05 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEa-0000a5-Co; Sat, 18 Aug 2007 11:29:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILQje-0003gf-4o; Wed, 15 Aug 2007 17:49:02 -0400
Received: from levanto.mail.adnap.net.au ([203.6.132.83])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILQjb-000343-W7; Wed, 15 Aug 2007 17:49:02 -0400
Received: from 122-49-148-154.ip.adam.com.au ([122.49.148.154]
	helo=mail.nosense.org)
	by levanto.mail.adnap.net.au with esmtp (Exim 4.63 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1ILQjT-0004N1-G7; Thu, 16 Aug 2007 07:18:51 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id 23ED9FC8B;
	Thu, 16 Aug 2007 07:18:48 +0930 (CST)
Date: Thu, 16 Aug 2007 07:18:47 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Iljitsch van Beijnum <iljitsch@muada.com>
Message-Id: <20070816071847.b1ecac48.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <6D53AB8B-0E6C-4E07-A140-A9150C4C024F@muada.com>
References: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<20070815194551.e2264a08.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<6D53AB8B-0E6C-4E07-A140-A9150C4C024F@muada.com>
X-Mailer: Sylpheed 2.4.4 (GTK+ 2.10.14; i686-pc-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:56 -0400
Cc: "volz <volz@cisco.com>, dhcwg@ietf.org, ipv6@ietf.org,
	\"John Jason Brzozowski \(JJMB\)\" <jjmb@jjmb.com>" <Bernie>
Subject: [dhcwg] Re: prefix length determination 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

On Wed, 15 Aug 2007 15:13:06 +0200
Iljitsch van Beijnum <iljitsch@muada.com> wrote:

> On 15-aug-2007, at 12:15, Mark Smith wrote:
> 
> >> I disagree. For better or for worse, the notion of a subnet mask
> >> going along with an interface address is deeply ingrained in the way
> >> IP is implemented. Separating the two for no apparent reason is a bad
> >> idea.
> 
> > I think you need to modify the following sentence as such:
> 
> > "For better or for worse, the notion of a subnet mask
> >  going along with an interface address is deeply ingrained in the way
> > **IPv4** is implemented."
> 
> No, I was very careful about what I said. The only place that I can  
> think of where you don't configure a mask along with an address is in  
> the case of HSRP. EVERYWHERE else that I know of you need to specify  
> it now that we have CIDR and obviously it was implied before we had  
> CIDR. Yes, in IPv6, too.
> 
> We can talk long and hard about the pros and cons of this  
> architecturally, but the simple truth is that changing this doesn't  
> appear to buy as anything tangible and it will require huge amounts  
> of work in implementations and then generate huge amounts of  
> confusion in operations so PLEASE let's not go down this road.
> 

I'm don't think I'm going down it. You seemed to be questioning why
subnets were fixed length, I provided most likelyreasons why, including
evidence that the original design of IPv4, pre-classes, also followed
this model. I think that shows that when there is the opportunity to
have fixed length node addressing it is very desirable, and has been
chosen by many protocol designers (DECNET Phase IV has it too, IIRC)

I like that IPv6 can place the boundary between the network and node
portion anywhere within the address, unlike IPX and Appletalk. It
future proofs the protocol, ensuring that should the network or node
portions not be big enough they can be changed, and devices will be
able to cope with it without software upgrades.

OTOH, I don't like _unnecessary_ complexity. Currently,
we don't need to engage any of the complexity of non-fixed network and
node portion boundaries in IPv6, so let's not until we need to.
Allowing for something doesn't mean you must use it.

Simplicity is what we get when we eliminate/avoid/choose not to use
variable length subnets, and it is a very tangible property, well worth
pursuing. I could probably save 5 minutes per day at work if I didn't
having to think through or calculate variable length subnet masks in
IPv4. That's 1200 minutes or 20 hours a year. Multiply that by how many
operators there are out there spending that 5 minutes or more per day
and it's a huge amount of spent time. That's a necessary expense when
dealing with IPv4, but not a necessary one for IPv6. If it's not
necessary, then it's wasted time.


> And if you have to look back before RFC 791 to provide  
> counterexamples that really doesn't disprove "ingrained" in my  
> opinion...

That's probably a fair critism. I was mainly replying to what I've
realised was an earlier question of yours, regarding why fixed length
subnets. The ingrained bit seemed to me to suggesting that fixed length
subnets would be considered to be a radical idea and wouldn't be
acceptable to those that have led sheltered protocol lives and only
ever dealt with IPv4, post 1995.

Regards,
Mark.

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





From dhcwg-bounces@ietf.org Sat Aug 18 11:30:55 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEa-0000d8-Ro; Sat, 18 Aug 2007 11:29:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILR3h-0002zk-8G; Wed, 15 Aug 2007 18:09:45 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILR3d-0003kI-OG; Wed, 15 Aug 2007 18:09:45 -0400
Received: from [82.192.90.28] (nirrti.muada.com [82.192.90.28])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l7FM64Hr069137
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Thu, 16 Aug 2007 00:06:05 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <20070816071847.b1ecac48.ipng@69706e6720323030352d30312d31340a.nosense.org>
References: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<20070815194551.e2264a08.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<6D53AB8B-0E6C-4E07-A140-A9150C4C024F@muada.com>
	<20070816071847.b1ecac48.ipng@69706e6720323030352d30312d31340a.nosense.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <34EEA1F3-0404-4A00-9E32-8445DCF2E8FC@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Thu, 16 Aug 2007 00:08:13 +0200
To: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:58 -0400
Cc: "volz <volz@cisco.com>, dhcwg@ietf.org, ipv6@ietf.org,
	\"John Jason Brzozowski \(JJMB\)\" <jjmb@jjmb.com>" <Bernie>
Subject: [dhcwg] Re: prefix length determination 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

On 15-aug-2007, at 23:48, Mark Smith wrote:

> I'm don't think I'm going down it. You seemed to be questioning why
> subnets were fixed length,

How are subnets fixed in size??

The discussion we were having was whether DHCPv6 in particular or any  
mechanism in general should distribute a subnet size in the form of a  
prefix length along with IP addresses. This discussion is only  
relevant when the size isn't fixed.

Although there is that infamous line about 64-bit interface  
identifiers for everything except ::/3 in RFC 3513 (the origin of  
which nobody has been able to explain so far despite my repeated  
requests), IPv6 has always been classless with no assumptions about  
the structure of addresses.

> I think that shows that when there is the opportunity to
> have fixed length node addressing it is very desirable, and has been
> chosen by many protocol designers (DECNET Phase IV has it too, IIRC)

Note though that all these protocols were designed for networks with  
a limited scope, unlike IP which was more or less designed and then  
became the protocol for all devices in the whole world.

The problem with a fixed length is that it's always either too large  
or too small. So when we get around to designing the successor of  
IPv6, we really need to use variable length addresses for that.

> I like that IPv6 can place the boundary between the network and node
> portion anywhere within the address, unlike IPX and Appletalk. It
> future proofs the protocol, ensuring that should the network or node
> portions not be big enough they can be changed

Right. It means that whatever we do, we'll never run out of IPv6  
address space because if needed, we could run the entire network on a  
single /64. That's still 32 more bits than IPv4 has.

> OTOH, I don't like _unnecessary_ complexity. Currently,
> we don't need to engage any of the complexity of non-fixed network and
> node portion boundaries in IPv6, so let's not until we need to.
> Allowing for something doesn't mean you must use it.

"Use it or lose it." If you run a network with a defacto boundary at / 
64 for a decade, don't be surprised when you can't move that boundary  
without breaking stuff.

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



From dhcwg-bounces@ietf.org Sat Aug 18 11:31:10 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEZ-0000YR-Ir; Sat, 18 Aug 2007 11:29:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILMS4-0006dz-Vv; Wed, 15 Aug 2007 13:14:36 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILMS3-0003FM-Kr; Wed, 15 Aug 2007 13:14:36 -0400
Received: from relay8.apple.com (relay8.apple.com [17.128.113.38])
	by mail-out3.apple.com (Postfix) with ESMTP id 1FC5CE90A23;
	Wed, 15 Aug 2007 10:14:35 -0700 (PDT)
Received: from relay8.apple.com (unknown [127.0.0.1])
	by relay8.apple.com (Symantec Mail Security) with ESMTP id 0CE3C405AD; 
	Wed, 15 Aug 2007 10:14:35 -0700 (PDT)
X-AuditID: 11807126-a6446bb0000007e3-01-46c3347a54f9
Received: from [17.151.104.90] (unknown [17.151.104.90])
	by relay8.apple.com (Apple SCV relay) with ESMTP id D2656404C4;
	Wed, 15 Aug 2007 10:14:34 -0700 (PDT)
In-Reply-To: <CA8EB93B28BD0F4C88392699600BD6550414236B@xmb-rtp-211.amer.cisco.com>
References: <CA8EB93B28BD0F4C88392699600BD6550414236B@xmb-rtp-211.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C18ABF71-CE63-4318-9107-EE1F1BADAB9A@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
Date: Wed, 15 Aug 2007 10:14:26 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:57 -0400
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 Aug 15, 2007, at 06:29, Wes Beebee (wbeebee) wrote:
>
> DHCPv6 is useful when MSO's want to control which CPE's get  
> addresses and which do not.  It provides a simple way to do access  
> control on a network.

EAP is a better way to do that.  DHCPv6 is more useful for  
controlling which CPE gets what addresses from a centrally  
administered network service.  I just don't see how that solves any  
*real* problems; that's all.  Why should it matter what address each  
CPE interface is assigned, as long as it's reachable, authenticated,  
authorized and accounted?  (Answer: because there are lazy people  
using interface addresses as CPE device identifiers in security  
protocols, when there are perfectly good alternatives in IPv6 that  
have the added virtue of actually functioning properly.)

As near as I can tell, the one architecturally goodish thing DHCPv6  
has going for it is prefix delegation.  There's no way to do that  
with straight router advertisements-- more's the pity.  (Once again,  
IETF stopped short of redesigning the full Appletalk protocol stack,  
which supported ad-hoc routed internets, sort of... but, alas, I'm  
beginning to degenerate.)

> Could a hacked-up rogue system still manage to get on?  Probably -  
> but at least it bars casual users from getting on a network that  
> they're not supposed to.

Probably?  Try: absolutely.

I could tell you how I used a commercial off-the-shelf product at  
IETF 69 to bypass the hotel's stupid method of using DHCP to prevent  
me from interposing my Wi-Fi NAT gateway into the in-room Internet  
service.  It's a supported feature of the product I used, expressly  
marketed to customers for the purpose of making it easy for casual  
users to do this. If they had used aFrom dhcwg-bounces@ietf.org Sat Aug 18 11:31:10 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEZ-0000YR-Ir; Sat, 18 Aug 2007 11:29:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILMS4-0006dz-Vv; Wed, 15 Aug 2007 13:14:36 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILMS3-0003FM-Kr; Wed, 15 Aug 2007 13:14:36 -0400
Received: from relay8.apple.com (relay8.apple.com [17.128.113.38])
	by mail-out3.apple.com (Postfix) with ESMTP id 1FC5CE90A23;
	Wed, 15 Aug 2007 10:14:35 -0700 (PDT)
Received: from relay8.apple.com (unknown [127.0.0.1])
	by relay8.apple.com (Symantec Mail Security) with ESMTP id 0CE3C405AD; 
	Wed, 15 Aug 2007 10:14:35 -0700 (PDT)
X-AuditID: 11807126-a6446bb0000007e3-01-46c3347a54f9
Received: from [17.151.104.90] (unknown [17.151.104.90])
	by relay8.apple.com (Apple SCV relay) with ESMTP id D2656404C4;
	Wed, 15 Aug 2007 10:14:34 -0700 (PDT)
In-Reply-To: <CA8EB93B28BD0F4C88392699600BD6550414236B@xmb-rtp-211.amer.cisco.com>
References: <CA8EB93B28BD0F4C88392699600BD6550414236B@xmb-rtp-211.amer.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C18ABF71-CE63-4318-9107-EE1F1BADAB9A@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
Date: Wed, 15 Aug 2007 10:14:26 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:57 -0400
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 Aug 15, 2007, at 06:29, Wes Beebee (wbeebee) wrote:
>
> DHCPv6 is useful when MSO's want to control which CPE's get  
> addresses and which do not.  It provides a simple way to do access  
> control on a network.

EAP is a better way to do that.  DHCPv6 is more useful for  
controlling which CPE gets what addresses from a centrally  
administered network service.  I just don't see how that solves any  
*real* problems; that's all.  Why should it matter what address each  
CPE interface is assigned, as long as it's reachable, authenticated,  
authorized and accounted?  (Answer: because there are lazy people  
using interface addresses as CPE device identifiers in security  
protocols, when there are perfectly good alternatives in IPv6 that  
have the added virtue of actually functioning properly.)

As near as I can tell, the one architecturally goodish thing DHCPv6  
has going for it is prefix delegation.  There's no way to do that  
with straight router advertisements-- more's the pity.  (Once again,  
IETF stopped short of redesigning the full Appletalk protocol stack,  
which supported ad-hoc routed internets, sort of... but, alas, I'm  
beginning to degenerate.)

> Could a hacked-up rogue system still manage to get on?  Probably -  
> but at least it bars casual users from getting on a network that  
> they're not supposed to.

Probably?  Try: absolutely.

I could tell you how I used a commercial off-the-shelf product at  
IETF 69 to bypass the hotel's stupid method of using DHCP to prevent  
me from interposing my Wi-Fi NAT gateway into the in-room Internet  
service.  It's a supported feature of the product I used, expressly  
marketed to customers for the purpose of making it easy for casual  
users to do this. If they had used an appropriate technology, it  
wouldn't have mattered whether I was using a bridge or a router or I  
was directly connected, and they would have still been assured that  
only my one computer was permitted to access their network.  Instead,  
they were relying on my good will not to run an open Wi-Fi AP and  
allow everybody in the rooms around me to share my access.

Operators who depend on DHCPv6 alone to deter users from accessing  
their networks with unauthorized devices are just going to end up  
peeving their paying customers with needless interoperability  
complexity.  Some operators have already discovered this, and they've  
now stopped using DHCP as an access control mechanism.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



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

From dhcwg-bounces@ietf.org Sat Aug 18 11:31:10 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEY-0000Y1-Nf; Sat, 18 Aug 2007 11:29:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IL625-00039O-1d; Tue, 14 Aug 2007 19:42:41 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IL622-0001mt-7r; Tue, 14 Aug 2007 19:42:39 -0400
Received: from relay6.apple.com (relay6.apple.com [17.128.113.36])
	by mail-out4.apple.com (Postfix) with ESMTP id 971C9EDEB99;
	Tue, 14 Aug 2007 16:42:36 -0700 (PDT)
Received: from relay6.apple.com (unknown [127.0.0.1])
	by relay6.apple.com (Symantec Mail Security) with ESMTP id 80F77100C6; 
	Tue, 14 Aug 2007 16:42:36 -0700 (PDT)
X-AuditID: 11807124-a67babb0000007f3-c5-46c23dec8e7b
Received: from [17.206.23.199] (il0602a-dhcp71.apple.com [17.206.23.199])
	by relay6.apple.com (Apple SCV relay) with ESMTP id 6A5CF1008E;
	Tue, 14 Aug 2007 16:42:36 -0700 (PDT)
In-Reply-To: <20070813161026.GA4846@isc.org>
References: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA840@SVR-ALH-EXC-02.mgc.mentorg.com>
	<m2zm0ywj2a.wl%jinmei@isl.rdc.toshiba.co.jp>
	<20070813161026.GA4846@isc.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed
Message-Id: <E2E6A987-046A-44D9-923F-F17F95AFFDD2@apple.com>
Content-Transfer-Encoding: quoted-printable
From: james woodyatt <jhw@apple.com>
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
Date: Tue, 14 Aug 2007 16:42:29 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:57 -0400
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 Aug 13, 2007, at 09:10, David W. Hankins wrote:
> On Sat, Aug 11, 2007 at 05:51:09PM +0900, JINMEI Tatuya / =E7=A5=9E=E6=98=
=8E=E9=81=94=20
> =E5=93=89 wrote:
>>
>> In any event, I hear that some DHCPv6 guys are planning to make a new
>> draft that covers this topic.  So I think it's better to hold off for
>> now and wait for the document, rather than continue this thread
>> with keeping possible misunderstanding or confusing about the base
>> protocol principles.
>
> I agree with everything Jinmei said, but this in particular.  Any
> conclusions from these threads have a tendency to get forgotten -
> it's better that we argue the position of a draft that an editor
> can follow consensus.

I n appropriate technology, it  
wouldn't have mattered whether I was using a bridge or a router or I  
was directly connected, and they would have still been assured that  
only my one computer was permitted to access their network.  Instead,  
they were relying on my good will not to run an open Wi-Fi AP and  
allow everybody in the rooms around me to share my access.

Operators who depend on DHCPv6 alone to deter users from accessing  
their networks with unauthorized devices are just going to end up  
peeving their paying customers with needless interoperability  
complexity.  Some operators have already discovered this, and they've  
now stopped using DHCP as an access control mechanism.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



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

From dhcwg-bounces@ietf.org Sat Aug 18 11:31:10 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEY-0000Y1-Nf; Sat, 18 Aug 2007 11:29:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IL625-00039O-1d; Tue, 14 Aug 2007 19:42:41 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IL622-0001mt-7r; Tue, 14 Aug 2007 19:42:39 -0400
Received: from relay6.apple.com (relay6.apple.com [17.128.113.36])
	by mail-out4.apple.com (Postfix) with ESMTP id 971C9EDEB99;
	Tue, 14 Aug 2007 16:42:36 -0700 (PDT)
Received: from relay6.apple.com (unknown [127.0.0.1])
	by relay6.apple.com (Symantec Mail Security) with ESMTP id 80F77100C6; 
	Tue, 14 Aug 2007 16:42:36 -0700 (PDT)
X-AuditID: 11807124-a67babb0000007f3-c5-46c23dec8e7b
Received: from [17.206.23.199] (il0602a-dhcp71.apple.com [17.206.23.199])
	by relay6.apple.com (Apple SCV relay) with ESMTP id 6A5CF1008E;
	Tue, 14 Aug 2007 16:42:36 -0700 (PDT)
In-Reply-To: <20070813161026.GA4846@isc.org>
References: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA840@SVR-ALH-EXC-02.mgc.mentorg.com>
	<m2zm0ywj2a.wl%jinmei@isl.rdc.toshiba.co.jp>
	<20070813161026.GA4846@isc.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=UTF-8; delsp=yes; format=flowed
Message-Id: <E2E6A987-046A-44D9-923F-F17F95AFFDD2@apple.com>
Content-Transfer-Encoding: quoted-printable
From: james woodyatt <jhw@apple.com>
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
Date: Tue, 14 Aug 2007 16:42:29 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:57 -0400
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 Aug 13, 2007, at 09:10, David W. Hankins wrote:
> On Sat, Aug 11, 2007 at 05:51:09PM +0900, JINMEI Tatuya / =E7=A5=9E=E6=98=
=8E=E9=81=94=20
> =E5=93=89 wrote:
>>
>> In any event, I hear that some DHCPv6 guys are planning to make a new
>> draft that covers this topic.  So I think it's better to hold off for
>> now and wait for the document, rather than continue this thread
>> with keeping possible misunderstanding or confusing about the base
>> protocol principles.
>
> I agree with everything Jinmei said, but this in particular.  Any
> conclusions from these threads have a tendency to get forgotten -
> it's better that we argue the position of a draft that an editor
> can follow consensus.

I agree with M. Jinmei as far as the quoted excerpt above goes.

As much as I dislike DHCPv6 on general principle, I don't expect that =20=

IETF will abandon it in favor of a system that more coherently =20
addresses the various separate concerns that DHCPv6 attempts to =20
meet.  I hope the DHC WG will specify requirements for routers =20
sending advertisements with the M bit set that prevent any ambiguity =20
from arising at the node during link configuration.

p.s. I really wish IETF had deprecated DHCPv6 when it had the =20
chance.  Every last thing DHCPv6 does belongs in one of two other, =20
separate domains, i.e. either in the sub-IP layer, e.g. EAP, or at =20
the sub-application layer, e.g. DNS-SD.  Instead, IETF chose a short-=20
sighted and half-baked solution to a problem that really didn't need =20
a rush job to solve, and the engineering community today is poorer =20
for it.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



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





agree with M. Jinmei as far as the quoted excerpt above goes.

As much as I dislike DHCPv6 on general principle, I don't expect that =20=

IETF will abandon it in favor of a system that more coherently =20
addresses the various separate concerns that DHCPv6 attempts to =20
meet.  I hope the DHC WG will specify requirements for routers =20
sending advertisements with the M bit set that prevent any ambiguity =20
from arising at the node during link configuration.

p.s. I really wish IETF had deprecated DHCPv6 when it had the =20
chance.  Every last thing DHCPv6 does belongs in one of two other, =20
separate domains, i.e. either in the sub-IP layer, e.g. EAP, or at =20
the sub-application layer, e.g. DNS-SD.  Instead, IETF chose a short-=20
sighted and half-baked solution to a problem that really didn't need =20
a rush job to solve, and the engineering community today is poorer =20
for it.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



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





From dhcwg-bounces@ietf.org Sat Aug 18 11:31:15 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEY-0000Xv-Gz; Sat, 18 Aug 2007 11:29:02 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILl8U-0007gq-QJ; Thu, 16 Aug 2007 15:36:02 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1ILl8U-0002Xk-24; Thu, 16 Aug 2007 15:36:02 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 16 Aug 2007 15:36:01 -0400
X-IronPort-AV: i="4.19,273,1183348800"; 
	d="scan'208"; a="68194614:sNHT75928178"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7GJa1Ro023461; 
	Thu, 16 Aug 2007 15:36:01 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l7GJZWnD006827; 
	Thu, 16 Aug 2007 19:36:01 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Aug 2007 15:35:58 -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] Re: prefix length determination for DHCPv6
Date: Thu, 16 Aug 2007 15:35:57 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Re: prefix length determination for DHCPv6
Thread-Index: Acff404IHOGKxhRoQYiEivR4Eyh4rQAANnCA
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com><7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com><8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com><18113.42485.158453.756815@gargle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.103258@gargle.gargle.HOWL><20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "JINMEI Tatuya / ????" <jinmei@isl.rdc.toshiba.co.jp>,
	"David W. Hankins" <David_Hankins@isc.org>
X-OriginalArrivalTime: 16 Aug 2007 19:35:58.0654 (UTC)
	FILETIME=[ABB16DE0:01C7E03C]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5054; t=1187292961;
	x=1188156961; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20[dhcwg]=20Re=3A=20prefix=20length=20determination=20f
	or=20DHCPv6 |Sender:=20
	|To:=20=22JINMEI=20Tatuya=20/=20????=22=20<jinmei@isl.rdc.toshiba.co.jp>,
	=0A=20=20=20=20=20=20=20=20=22David=20W.=20Hankins=22=20<David_Hankins@isc
	.org>; bh=dGHEW5ifYoH/r5O2aXR9pZsX/sfoS7d8o5kMme2YXyk=;
	b=TH4BfNBg821wSYGRGHNm/8Mznsh7+a+FMtvWUqrfq1CPyvd7TQuX+MIaZ1V9s6iZPUII+mXH
	/NjgU+Mv+TrPIpxglFDoo6zrL8HoEwWw73G6uJ/w0bfZcV03O157d/R9;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:56 -0400
Cc: dhcwg@ietf.org, ipv6@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.From dhcwg-bounces@ietf.org Sat Aug 18 11:31:15 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEY-0000Xv-Gz; Sat, 18 Aug 2007 11:29:02 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILl8U-0007gq-QJ; Thu, 16 Aug 2007 15:36:02 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1ILl8U-0002Xk-24; Thu, 16 Aug 2007 15:36:02 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 16 Aug 2007 15:36:01 -0400
X-IronPort-AV: i="4.19,273,1183348800"; 
	d="scan'208"; a="68194614:sNHT75928178"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7GJa1Ro023461; 
	Thu, 16 Aug 2007 15:36:01 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l7GJZWnD006827; 
	Thu, 16 Aug 2007 19:36:01 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Aug 2007 15:35:58 -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] Re: prefix length determination for DHCPv6
Date: Thu, 16 Aug 2007 15:35:57 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Re: prefix length determination for DHCPv6
Thread-Index: Acff404IHOGKxhRoQYiEivR4Eyh4rQAANnCA
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com><7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com><8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com><18113.42485.158453.756815@gargle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.103258@gargle.gargle.HOWL><20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "JINMEI Tatuya / ????" <jinmei@isl.rdc.toshiba.co.jp>,
	"David W. Hankins" <David_Hankins@isc.org>
X-OriginalArrivalTime: 16 Aug 2007 19:35:58.0654 (UTC)
	FILETIME=[ABB16DE0:01C7E03C]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5054; t=1187292961;
	x=1188156961; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20[dhcwg]=20Re=3A=20prefix=20length=20determination=20f
	or=20DHCPv6 |Sender:=20
	|To:=20=22JINMEI=20Tatuya=20/=20????=22=20<jinmei@isl.rdc.toshiba.co.jp>,
	=0A=20=20=20=20=20=20=20=20=22David=20W.=20Hankins=22=20<David_Hankins@isc
	.org>; bh=dGHEW5ifYoH/r5O2aXR9pZsX/sfoS7d8o5kMme2YXyk=;
	b=TH4BfNBg821wSYGRGHNm/8Mznsh7+a+FMtvWUqrfq1CPyvd7TQuX+MIaZ1V9s6iZPUII+mXH
	/NjgU+Mv+TrPIpxglFDoo6zrL8HoEwWw73G6uJ/w0bfZcV03O157d/R9;
Authentication-Results: rtp-dkim-2; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:56 -0400
Cc: dhcwg@ietf.org, ipv6@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

I personally think all this discussion is much ado about nothing. It's
incorrect thinking to deploy an IPv6 router without RA. RA supports all
of prefix information and on-link determination, so why have DHCPv6
duplicate that functionality? Bernie already mentioned why it's
dangerous if two entities in DHCPv6 server and IPv6 router issue
duplicate information one of which could be different. I also feel
DHCPv6 WG should not take up any work item to start working on
supporting any new option that duplicates PIO of RA nor work on a
default router option. As many folks have said, please don't think IPv6
like IPv4. Also, aside of SLAAC where a default prefix length can be
assumed but cannot be used for on-link determination, no other IPv6
deployment make sense to assume any default prefix length. This is the
new property of an IPv6 network for the router to be able to assign any
prefix length to nodes the router serves.

The other discussion about routers in broadband residential homes etc.,
can be a separate discussion held in dhcpwg. IPv6 data WG has other
important problems to consider like something as basic as a host data
forwarding is broken due to misconceptions about on- vs. off-link
determination.

Hemant

-----Original Message-----
From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp]=20
Sent: Thursday, August 16, 2007 4:56 AM
To: David W. Hankins
Cc: dhcwg@ietf.org; ipv6@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6

At Wed, 15 Aug 2007 10:51:40 -0700,
"David W. Hankins" <David_Hankins@isc.org> wrote:

> > > I think that you will find realistically, DHCPv6 servers will know

> > > prefix lengths.
> >=20
> > None that I've worked with (including the WIDE server) seems to
care.
> > What's needed are assignment ranges, not prefixes.
>=20
> I'm familiar with half of the story here, and uncomfortable with=20
> speaking about a specific competitor's product (but it appears I will=20
> do it anyway).  My opinion of WIDE's Confirm message processing is=20
> that it does know the prefix length: it assumes all prefixes are /64,=20
> by comparing the first 8 bytes of addresses.
>=20
> I make no judgement here of the efficacy or correctness of this=20
> implementation.
>=20
> If there is an expert on WIDE's implementation that can describe how=20
> it reaches a dynamic pool from relays (without relays, it appears to=20
> follow interface definitions), I'm curious to know the rest of the=20
> story.

I'm not an "expert" on the WIDE implementation (any more), but I know
the implementation well enough that I can clarify the points, so...

Your understanding about the Confirm message processing of the WIDE
server is correct.  (And I don't think this way of handling Confirm is
really an appropriate behavior).

The WIDE server implementation doesn't care about the link prefix when
assigning an address from a pool.  This is also not an appropriate
behavior because it could assign an address that is not valid for the
link to which the client is attached.

So, I think you're right in that realistically the DHCPv6 server
operator needs to understand the link prefixes of the addresses assigned
via DHCPv6.  This also means the DHCPv6 server will realistically be
able to provide this information for the clients.
(The server might still work properly just based on the knowledge about
its own local links and on the content of 'link address'
information of relayed messages.  But such an operation does not seem
"realistic" to me).

But I don't think this immediately justifies the introduction of an
on-link prefix option to DHCPv6.  To rely on this feature, the
DHCPv6 operator would need to know all on-link prefixes including ones
that are not used for DHCP-based address assignment, and would need to
configure them on the server.  Although the additional overhead is
minor, it can still be an unnecessary operational cost and can cause
configuration inconsistency that could actually avoided.  On the other
hand, routers should inherently know the on-liorg?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

I personally think all this discussion is much ado about nothing. It's
incorrect thinking to deploy an IPv6 router without RA. RA supports all
of prefix information and on-link determination, so why have DHCPv6
duplicate that functionality? Bernie already mentioned why it's
dangerous if two entities in DHCPv6 server and IPv6 router issue
duplicate information one of which could be different. I also feel
DHCPv6 WG should not take up any work item to start working on
supporting any new option that duplicates PIO of RA nor work on a
default router option. As many folks have said, please don't think IPv6
like IPv4. Also, aside of SLAAC where a default prefix length can be
assumed but cannot be used for on-link determination, no other IPv6
deployment make sense to assume any default prefix length. This is the
new property of an IPv6 network for the router to be able to assign any
prefix length to nodes the router serves.

The other discussion about routers in broadband residential homes etc.,
can be a separate discussion held in dhcpwg. IPv6 data WG has other
important problems to consider like something as basic as a host data
forwarding is broken due to misconceptions about on- vs. off-link
determination.

Hemant

-----Original Message-----
From: JINMEI Tatuya / ???? [mailto:jinmei@isl.rdc.toshiba.co.jp]=20
Sent: Thursday, August 16, 2007 4:56 AM
To: David W. Hankins
Cc: dhcwg@ietf.org; ipv6@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6

At Wed, 15 Aug 2007 10:51:40 -0700,
"David W. Hankins" <David_Hankins@isc.org> wrote:

> > > I think that you will find realistically, DHCPv6 servers will know

> > > prefix lengths.
> >=20
> > None that I've worked with (including the WIDE server) seems to
care.
> > What's needed are assignment ranges, not prefixes.
>=20
> I'm familiar with half of the story here, and uncomfortable with=20
> speaking about a specific competitor's product (but it appears I will=20
> do it anyway).  My opinion of WIDE's Confirm message processing is=20
> that it does know the prefix length: it assumes all prefixes are /64,=20
> by comparing the first 8 bytes of addresses.
>=20
> I make no judgement here of the efficacy or correctness of this=20
> implementation.
>=20
> If there is an expert on WIDE's implementation that can describe how=20
> it reaches a dynamic pool from relays (without relays, it appears to=20
> follow interface definitions), I'm curious to know the rest of the=20
> story.

I'm not an "expert" on the WIDE implementation (any more), but I know
the implementation well enough that I can clarify the points, so...

Your understanding about the Confirm message processing of the WIDE
server is correct.  (And I don't think this way of handling Confirm is
really an appropriate behavior).

The WIDE server implementation doesn't care about the link prefix when
assigning an address from a pool.  This is also not an appropriate
behavior because it could assign an address that is not valid for the
link to which the client is attached.

So, I think you're right in that realistically the DHCPv6 server
operator needs to understand the link prefixes of the addresses assigned
via DHCPv6.  This also means the DHCPv6 server will realistically be
able to provide this information for the clients.
(The server might still work properly just based on the knowledge about
its own local links and on the content of 'link address'
information of relayed messages.  But such an operation does not seem
"realistic" to me).

But I don't think this immediately justifies the introduction of an
on-link prefix option to DHCPv6.  To rely on this feature, the
DHCPv6 operator would need to know all on-link prefixes including ones
that are not used for DHCP-based address assignment, and would need to
configure them on the server.  Although the additional overhead is
minor, it can still be an unnecessary operational cost and can cause
configuration inconsistency that could actually avoided.  On the other
hand, routers should inherently know the on-link prefix information to
route packets appropriately, so providing this information via RA still
looks better than the DHCP-based approach.

IMO, this discussion is going to miss the point.  The problem is not
whether we can provide on-link prefix information via DHCPv6 (yes we
can) or whether it's reasonable per se (it might), but whether we should
do this while RA already has this provision and would actually be better
than DHCPv6-based approach.  A new draft from the dhc group will
reportedly (hopefully?) answer this main question, so, again, I think we
should hold off for a while.

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

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

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

From dhcwg-bounces@ietf.org Sat Aug 18 11:31:15 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEb-0000eL-Ng; Sat, 18 Aug 2007 11:29:05 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILmRG-0005d3-7o; Thu, 16 Aug 2007 16:59:30 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1ILmRF-00057c-Cj; Thu, 16 Aug 2007 16:59:30 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-2.cisco.com with ESMTP; 16 Aug 2007 13:59:29 -0700
X-IronPort-AV: i="4.19,273,1183359600"; 
	d="scan'208"; a="392705833:sNHT70908888"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7GKxSAv012027; 
	Thu, 16 Aug 2007 13:59:28 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l7GKxGWJ009532;
	Thu, 16 Aug 2007 20:59:28 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Aug 2007 16:59:23 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
Date: Thu, 16 Aug 2007 16:59:21 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D03881335@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <20070815175140.GC18683@isc.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Re: prefix length determination for DHCPv6
Thread-Index: Acff5ZdBDwQkeZ3MTnWx13kCPHOIMgAYm48g
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com><7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com><8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com><18113.42485.158453.756815@gargle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "David W. Hankins" <David_Hankins@isc.org>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 16 Aug 2007 20:59:23.0325 (UTC)
	FILETIME=[52B59ED0:01C7E048]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4759; t=1187297968;
	x=1188161968; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20[dhcwg]=20Re=3A=20prefix=20length=20determination=20f
	or=20DHCPv6 |nk prefix information to
route packets appropriately, so providing this information via RA still
looks better than the DHCP-based approach.

IMO, this discussion is going to miss the point.  The problem is not
whether we can provide on-link prefix information via DHCPv6 (yes we
can) or whether it's reasonable per se (it might), but whether we should
do this while RA already has this provision and would actually be better
than DHCPv6-based approach.  A new draft from the dhc group will
reportedly (hopefully?) answer this main question, so, again, I think we
should hold off for a while.

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

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

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

From dhcwg-bounces@ietf.org Sat Aug 18 11:31:15 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMQEb-0000eL-Ng; Sat, 18 Aug 2007 11:29:05 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILmRG-0005d3-7o; Thu, 16 Aug 2007 16:59:30 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1ILmRF-00057c-Cj; Thu, 16 Aug 2007 16:59:30 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-2.cisco.com with ESMTP; 16 Aug 2007 13:59:29 -0700
X-IronPort-AV: i="4.19,273,1183359600"; 
	d="scan'208"; a="392705833:sNHT70908888"
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7GKxSAv012027; 
	Thu, 16 Aug 2007 13:59:28 -0700
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l7GKxGWJ009532;
	Thu, 16 Aug 2007 20:59:28 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 16 Aug 2007 16:59:23 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
Date: Thu, 16 Aug 2007 16:59:21 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D03881335@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <20070815175140.GC18683@isc.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Re: prefix length determination for DHCPv6
Thread-Index: Acff5ZdBDwQkeZ3MTnWx13kCPHOIMgAYm48g
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com><7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com><8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com><18113.42485.158453.756815@gargle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "David W. Hankins" <David_Hankins@isc.org>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 16 Aug 2007 20:59:23.0325 (UTC)
	FILETIME=[52B59ED0:01C7E048]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4759; t=1187297968;
	x=1188161968; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20[dhcwg]=20Re=3A=20prefix=20length=20determination=20f
	or=20DHCPv6 |Sender:=20;
	bh=00C/xWieAjSnZLcqMbGUEIMXTaiVFVT96YnbjLW+6T8=;
	b=Z6z+8nSAefhK4A891BrymWUoEVdQ8m0jeTdwFv4IK+EnbaWkgkKUcl5wqmsSNN1v4fYlEFxc
	1fP1UWmuuV9DTkJzcrGHfKqFYrwYfCcep7W9Bi9oknrcx+Flyn0W0SFDQlUruJBqsppnYhYP2m
	GvbXpwuZ0KIFox7IOYJ8YqHB0=;
Authentication-Results: sj-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:56 -0400
Cc: ipv6@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

Wrt:

>I'm sorry - this is a DHCPv6 protocol mechanic, something only a DHCP
geek would know.

>The relay messages' 'link-address' field is central to the server's
calculation of the client's location (which "broadcast domain"
>they're attached to).

>Basically it's how you know which addresses are appropriate for the
client, based on what network they're attached to.

David is correct about use of Link-addr by server above. Link-addr is
the equivalent of giaddr in DHCPv4.=20

Hemant

-----Original Message-----
From: David W. Hankins [mailto:David_Hankins@isc.org]=20
Sent: Wednesday, August 15, 2007 1:52 PM
To: dhcwg@ietf.org
Cc: ipv6@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6

On Wed, Aug 15, 2007 at 10:33:16AM -0400, James Carlson wrote:
> > and it needs to be able to Confirm the use of addresses, which it=20
> > may not have allocated.
>=20
> That doesn't make sense to me.  The DHCPv6 Confirm message is for=20
> confirming an address lease.  If the server hasn't allocated the=20
> lease, then it _cannot_ confirm anything about the address and must=20
> Nak in response.  If it does confirm addresses it hasn't allocated,=20
> then it's just broken.

I'm not sure where you got that idea - certainly not from RFC3315
section 18.2.2 ("Receipt of Confirm Messages" under "Server Behavior").

I'll spare pasting the content to the lists - please have a read and let
me know if you still disagree.

> > 	- Have a list of all the 'link-address' fields that all
> > 	  operating DHCPv6 relays will use to identify a link.
>=20
> I'm confused.  Why would relays be confirming anything?

I'm sorry - this is a DHCPv6 protocol mechanic, something only a DHCP
geek would know.

The relay messages' 'link-address' field is central to the server's
calculation of the client's location (which "broadcast domain"
they're attached to).

Basically it's how you know which addresses are appropriate for the
client, based on what network they're attached to.

So this is a server inspecting a chain of relayed messages and finding
the link-address(es) it thinks are relevant to the client.
Then using that as a key to find the address(es) it needs to deliver to
the client.

One way to do this is to find a prefix that contains the selected
link-address (masking and comparing) and work outwards.

One other way to do this is to index the link-addresses specifically, or
some approximation of the same.

Does that make more sense now?

> > I think that you will find realistically, DHCPv6 servers will know=20
> > prefix lengths.
>=20
> None that I've worked with (including the WIDE server) seems to care.
> What's needed are assignment ranges, not prefixes.

I'm familiar with half of the story here, and uncomfortable with
speaking about a specific competitor's product (but it appears I will do
it anyway).  My opinion of WIDE's Confirm message processing is that it
does know the prefix length: it assumes all prefixes are /64, by
comparing the first 8 bytes of addresses.

I make no judgement here of the efficacy or correctness of this
implementation.

If there is an expert on WIDE's implemenSender:=20;
	bh=00C/xWieAjSnZLcqMbGUEIMXTaiVFVT96YnbjLW+6T8=;
	b=Z6z+8nSAefhK4A891BrymWUoEVdQ8m0jeTdwFv4IK+EnbaWkgkKUcl5wqmsSNN1v4fYlEFxc
	1fP1UWmuuV9DTkJzcrGHfKqFYrwYfCcep7W9Bi9oknrcx+Flyn0W0SFDQlUruJBqsppnYhYP2m
	GvbXpwuZ0KIFox7IOYJ8YqHB0=;
Authentication-Results: sj-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
X-Mailman-Approved-At: Sat, 18 Aug 2007 11:28:56 -0400
Cc: ipv6@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

Wrt:

>I'm sorry - this is a DHCPv6 protocol mechanic, something only a DHCP
geek would know.

>The relay messages' 'link-address' field is central to the server's
calculation of the client's location (which "broadcast domain"
>they're attached to).

>Basically it's how you know which addresses are appropriate for the
client, based on what network they're attached to.

David is correct about use of Link-addr by server above. Link-addr is
the equivalent of giaddr in DHCPv4.=20

Hemant

-----Original Message-----
From: David W. Hankins [mailto:David_Hankins@isc.org]=20
Sent: Wednesday, August 15, 2007 1:52 PM
To: dhcwg@ietf.org
Cc: ipv6@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6

On Wed, Aug 15, 2007 at 10:33:16AM -0400, James Carlson wrote:
> > and it needs to be able to Confirm the use of addresses, which it=20
> > may not have allocated.
>=20
> That doesn't make sense to me.  The DHCPv6 Confirm message is for=20
> confirming an address lease.  If the server hasn't allocated the=20
> lease, then it _cannot_ confirm anything about the address and must=20
> Nak in response.  If it does confirm addresses it hasn't allocated,=20
> then it's just broken.

I'm not sure where you got that idea - certainly not from RFC3315
section 18.2.2 ("Receipt of Confirm Messages" under "Server Behavior").

I'll spare pasting the content to the lists - please have a read and let
me know if you still disagree.

> > 	- Have a list of all the 'link-address' fields that all
> > 	  operating DHCPv6 relays will use to identify a link.
>=20
> I'm confused.  Why would relays be confirming anything?

I'm sorry - this is a DHCPv6 protocol mechanic, something only a DHCP
geek would know.

The relay messages' 'link-address' field is central to the server's
calculation of the client's location (which "broadcast domain"
they're attached to).

Basically it's how you know which addresses are appropriate for the
client, based on what network they're attached to.

So this is a server inspecting a chain of relayed messages and finding
the link-address(es) it thinks are relevant to the client.
Then using that as a key to find the address(es) it needs to deliver to
the client.

One way to do this is to find a prefix that contains the selected
link-address (masking and comparing) and work outwards.

One other way to do this is to index the link-addresses specifically, or
some approximation of the same.

Does that make more sense now?

> > I think that you will find realistically, DHCPv6 servers will know=20
> > prefix lengths.
>=20
> None that I've worked with (including the WIDE server) seems to care.
> What's needed are assignment ranges, not prefixes.

I'm familiar with half of the story here, and uncomfortable with
speaking about a specific competitor's product (but it appears I will do
it anyway).  My opinion of WIDE's Confirm message processing is that it
does know the prefix length: it assumes all prefixes are /64, by
comparing the first 8 bytes of addresses.

I make no judgement here of the efficacy or correctness of this
implementation.

If there is an expert on WIDE's implementation that can describe how it
reaches a dynamic pool from relays (without relays, it appears to follow
interface definitions), I'm curious to know the rest of the story.

> > Surely, there must also be some need to perpetuate two protocols,=20
> > other than to simply perpetuate the need not to duplicate their=20
> > contents?
>=20
> If you're going to deprecate DHCPv6 for address assignment and fold it

> into the RA mechanism, then I'd be (somewhat weakly) in favor of that.
>=20
> If you're just going to duplicate things, then I'm very much opposed.

Neither of those really sound like a good idea to me, but then I'm also
lacking the power to do either of them.  I guess the grass is not always
greener on the other side.

But let's save this discussion for a draft.  Rumor has it, someone is
writing one on this topic (or at least exploring the issues), and I want
to read what they have to say.

> > Even if you delegate a prefix, you still need to know your=20
> > customer's address so that you might route packets to them.
>=20
> I don't understand that.
>=20
> If you delegate a prefix, then you route to the prefix -- best match.

Yes, but how does that route get in the table, and what next-hop is set?
You have to know your customer's address eventually.

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

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





tation that can describe how it
reaches a dynamic pool from relays (without relays, it appears to follow
interface definitions), I'm curious to know the rest of the story.

> > Surely, there must also be some need to perpetuate two protocols,=20
> > other than to simply perpetuate the need not to duplicate their=20
> > contents?
>=20
> If you're going to deprecate DHCPv6 for address assignment and fold it

> into the RA mechanism, then I'd be (somewhat weakly) in favor of that.
>=20
> If you're just going to duplicate things, then I'm very much opposed.

Neither of those really sound like a good idea to me, but then I'm also
lacking the power to do either of them.  I guess the grass is not always
greener on the other side.

But let's save this discussion for a draft.  Rumor has it, someone is
writing one on this topic (or at least exploring the issues), and I want
to read what they have to say.

> > Even if you delegate a prefix, you still need to know your=20
> > customer's address so that you might route packets to them.
>=20
> I don't understand that.
>=20
> If you delegate a prefix, then you route to the prefix -- best match.

Yes, but how does that route get in the table, and what next-hop is set?
You have to know your customer's address eventually.

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

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





From dhcwg-bounces@ietf.org Sat Aug 18 20:25:31 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMYZy-0007N6-W8; Sat, 18 Aug 2007 20:23:43 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMYZx-0007Mx-Sr; Sat, 18 Aug 2007 20:23:41 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IMYZx-0004Fb-Fu; Sat, 18 Aug 2007 20:23:41 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 18 Aug 2007 20:23:41 -0400
X-IronPort-AV: i="4.19,280,1183348800"; 
	d="scan'208"; a="129250605:sNHT46820420"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7J0NeA5031483; 
	Sat, 18 Aug 2007 20:23:40 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7J0NejI027487; 
	Sun, 19 Aug 2007 00:23:40 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 18 Aug 2007 20:23:40 -0400
Received: from [192.168.1.100] ([10.86.240.211]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 18 Aug 2007 20:23:40 -0400
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: 7bit
Message-Id: <831A19C7-9B03-4475-B532-34A23A6E50E4@cisco.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: dhcwg@ietf.org, IETF Mailing List IPv6 <ipv6@ietf.org>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
Date: Sat, 18 Aug 2007 20:24:37 -0400
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 19 Aug 2007 00:23:40.0360 (UTC)
	FILETIME=[314C3C80:01C7E1F7]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2018; t=1187483020;
	x=1188347020; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rdroms@cisco.com;
	z=From:=20Ralph=20Droms=20<rdroms@cisco.com>
	|Subject:=20Re=3A=20[dhcwg]=20Re=3A=20prefix=20length=20determination=20f
	or=20DHCPv6 |Sender:=20
	|To:=20dhcwg@ietf.org,=20IETF=20Mailing=20List=20IPv6=20<ipv6@ietf.org>;
	bh=wB1YOVghAyuZMCpQ1d2aBtPMAuzw5aM5wPRaT9iqp9A=;
	b=I/U8Wl6/Jd1+8ExfPHAuiL51NWqDYuX6QZY2uWnYl4GMdDrYBtQOd00Fk9uzTrULNEorNYwJ
	AMtR5HdB8+8wRYElQWsRNGcmhowGFFBQeRZQdFDd047ni/Phrd+XqPFE;
Authentication-Results: rtp-dkim-1; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Where you configure a mask with an address is an accident of the UI.   
Where you use the mask is based on the protocol design.  The prefix  
length is not used in any way with an address assigned to an  
interface.  The only reason a mask is specified with an address in  
IPv4 is to convey on-link prefix information.  That information is  
provided through RAs in IPv6.  Therefore there is no need to provide  
a prefix length with an assigned IPv6 address, whether that address  
is assigned through SLAAC, DHCPv6, manual assignment or divine  
intervention.

- Ralph

On Aug 15, 2007, at Aug 15, 2007,9:13 AM, Iljitsch van Beijnum wrote:


> On 15-aug-2007, at 12:15, Mark Smith wrote:
>
>
>>> I disagree. For better or for worse, the notion of a subnet mask
>>> going along with an interface address is deeply ingrained in the way
>>> IP is implemented. Separating the two for no apparent reason is a  
>>> bad
>>> idea.
>>>
>
>
>> I think you need to modify the following sentence as such:
>>
>
>
>> "For better or for worse, the notion of a subnet mask
>>  going along with an interface address is deeply ingrained in the way
>> **IPv4** is implemented."
>>
>
> No, I was very careful about what I said. The only place that I can  
> think of where you don't configure a mask along with an address is  
> in the case of HSRP. EVERYWHERE else that I know of you need to  
> specify it now that we have CIDR and obviously it was implied  
> before we had CIDR. Yes, in IPv6, too.
>
> We can talk long and hard about the pros and cons of this  
> architecturally, but the simple truth is that changing this doesn't  
> appear to buy as anything tangible and it will require huge amounts  
> of work in implementations and then generate huge amounts of  
> confusion in operations so PLEASE let's not go down this road.
>
> And if you have to look back before RFC 791 to provide  
> counterexamples that really doesn't disprove "ingrained" in my  
> opinion...
>

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



From dhcwg-bounces@ietf.org Sat Aug 18 20:26:22 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMYay-0000jC-EG; Sat, 18 Aug 2007 20:24:44 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMYav-0000aV-MA; Sat, 18 Aug 2007 20:24:41 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IMYav-0004H5-A1; Sat, 18 Aug 2007 20:24:41 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 18 Aug 2007 17:24:40 -0700
X-IronPort-AV: i="4.19,280,1183359600"; 
	d="scan'208"; a="202518465:sNHT42206094"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l7J0OeoW004381; 
	Sat, 18 Aug 2007 17:24:40 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l7J0OeiF023618;
	Sun, 19 Aug 2007 00:24:40 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 18 Aug 2007 20:24:38 -0400
Received: from [192.168.1.100] ([10.86.240.211]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 18 Aug 2007 20:24:38 -0400
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: 7bit
Message-Id: <B1EDB05B-DECC-4751-BA01-EB5962F33C4D@cisco.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: IETF IPv6 Mailing List <ipv6@ietf.org>, dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
Date: Sat, 18 Aug 2007 20:25:36 -0400
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 19 Aug 2007 00:24:38.0564 (UTC)
	FILETIME=[53FD7640:01C7E1F7]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1015; t=1187483080;
	x=1188347080; c=relaxed/simple; s=sjdkim3002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rdroms@cisco.com;
	z=From:=20Ralph=20Droms=20<rdroms@cisco.com>
	|Subject:=20Re=3A=20[dhcwg]=20Re=3A=20prefix=20length=20determination=20f
	or=20DHCPv6 |Sender:=20;
	bh=xUlBFiV9A1oNiTBPqv6QCqOP0yHpjQRdyn7FVRLZ5Lg=;
	b=fsCERGKHc7lwG9u3OyV4Wcx3YnMIXHqVHStuFrdP8nBYsubOoEm6SLaU0Rsx2RJYnc/PqsGY
	NNv16tJh9a9I05wcCu1erWB9eWKkqJY0X7ZVd3pVr/q2j1Sb1XrZKnwi;
Authentication-Results: sj-dkim-3; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

James - in the abstract, in my opinion the inference is that a prefix  
cannot be described as on-link unless it is advertised in a PIO.

Question for the list: is there a functional difference between an RA  
that includes a PIO advertising a prefix P with neither the L nor A  
bits set (no on-link, don't do SLAAC) and an RA that does not  
advertise prefix P at all?  I don't think there is, and I'm curious  
about why an RA with no PIOs is viewed as "incorrect" while an RA  
with PIOs with L and A not set is OK.

- Ralph

On Aug 17, 2007, at Aug 17, 2007,4:09 PM, james woodyatt wrote:


>
> On a related note, I've heard that some operators intend to deploy  
> DHCP service using RA with M=1 and no PIO.  I don't understand how  
> they imagine the "on-link flag" to be propagated in that scenario.   
> The "on-link flag" seems to be clearly in the domain of router  
> function, not dynamic node configuration.  Is that to be described  
> in the forthcoming Internet draft?
>
>


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



From dhcwg-bounces@ietf.org Sat Aug 18 21:12:05 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMZJ6-0001Cs-9f; Sat, 18 Aug 2007 21:10:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMZJ4-0001Ce-Hb; Sat, 18 Aug 2007 21:10:18 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IMZJ3-0007Vw-U9; Sat, 18 Aug 2007 21:10:18 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 18 Aug 2007 21:10:17 -0400
X-IronPort-AV: i="4.19,280,1183348800"; 
	d="scan'208"; a="68375944:sNHT63672116"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7J1AH5k007580; 
	Sat, 18 Aug 2007 21:10:17 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7J1AHjI007571; 
	Sun, 19 Aug 2007 01:10:17 GMT
Received: from xmb-rtp-20e.amer.cisco.com ([64.102.31.40]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 18 Aug 2007 21:10:17 -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] Re: prefix length determination for DHCPv6
Date: Sat, 18 Aug 2007 21:10:16 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D038FA858@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B1EDB05B-DECC-4751-BA01-EB5962F33C4D@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Re: prefix length determination for DHCPv6
Thread-Index: Acfh91nrqDcciedwRkuc9EZSm/6F6wAAQ7rA
References: <B1EDB05B-DECC-4751-BA01-EB5962F33C4D@cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Ralph Droms (rdroms)" <rdroms@cisco.com>,
	"IETF IPv6 Mailing List" <ipv6@ietf.org>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 19 Aug 2007 01:10:17.0185 (UTC)
	FILETIME=[B455DD10:01C7E1FD]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3763; t=1187485817;
	x=1188349817; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=shemant@cisco.com;
	z=From:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>
	|Subject:=20RE=3A=20[dhcwg]=20Re=3A=20prefix=20length=20determination=20f
	or=20DHCPv6 |Sender:=20
	|To:=20=22Ralph=20Droms=20(rdroms)=22=20<rdroms@cisco.com>,
	=0A=20=20=20=2
	0=20=20=20=20=22IETF=20IPv6=20Mailing=20List=22=20<ipv6@ietf.org>,
	=20<dhcw g@ietf.org>;
	bh=4+MhPwgXhixZk4wxTjJaCKpNks/lmsUT3cAVx5db9AY=;
	b=nkBdNuZKsxTUxmVLOFjQlGa3aWdywW+MAVSVjV/QJTWRy8mpiLsRIZozSIdbsJzrgGIuOOpU
	IMFQxCHfrP/4ZKhIGBeA9Uq3/MV7ZyagRN8y+jIop5x7qPtU27lyUX65;
Authentication-Results: rtp-dkim-1; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

I had clarified such RAs in private discussions with various folks
inside and outside Cisco.

Sorry, if I have missed any email that said RA with no PIOs is viewed as
"incorrect". It is a totally correct RA configuration that 2461bis or
even RFC 2461 makes reference to. Now an RA that includes a PIO
advertising a prefix P with neither the L nor A bits, in absence of any
other sources of on-link information, is functionally no different that
an RA with no PIO  - both lead hosts receiving such RAs to send their
non-link-local traffic to default router. Soon as a host sends traffic
to default router, that is off-link operation. The other kind of RA that
Ralph mentioned is the second way one can configure an IPv6 router to
signal off-link behavior to a host. In an IPv6 network that is using a
router, and router is issuing RA to hosts, these are the only two ways
one can configure off-link mode in RA to signal to hosts. Hence for an
aggregation routed IPv6 network, these are two possible RA
configurations that the aggregation router can be configured for.

Here is justification from 2461bis, for the RA that has L bit clear and
advertising a prefix, that such an RA is signaling off-link. Note that
2461bis , in section 6.3.4 says, if L bit is clear, the RA is not
signaling off-link in the following text:

   [Note, however, that a Prefix Information option
   with the on-link flag set to zero conveys no information concerning
   on-link determination and MUST NOT be interpreted to mean that
   addresses covered by the prefix are off-link.  The only way to cancel
   a previous on-link indication is to advertise that prefix with the
   L-bit set and the Lifetime set to zero.  The default behavior (see
   Section 5.2) when sending a packet to an address for which no
   information is known about the on-link status of the address is to
   forward the packet to a default router;]

However, then the text above continues to say, "The default behavior
(see Section 5.2) when sending a packet to an address for which no
information is known about the on-link status of the address is to
forward the packet to a default router." Soon as 2461bis said "forward
the packet to default router", off-link operation is implied. That is
why the two RAs are not functionally different.

Hemant


-----Original Message-----
From: Ralph Droms (rdroms)=20
Sent: Saturday, August 18, 2007 8:26 PM
To: IETF IPv6 Mailing List; dhcwg@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6

James - in the abstract, in my opinion the inference is that a prefix
cannot be described as on-link unless it is advertised in a PIO.

Question for the list: is there a functional difference between an RA
that includes a PIO advertising a prefix P with neither the L nor A bits
set (no on-link, don't do SLAAC) and an RA that does not advertise
prefix P at all?  I don't think there is, and I'm curious about why an
RA with no PIOs is viewed as "incorrect" while an RA with PIOs with L
and A not set is OK.

- Ralph

On Aug 17, 2007, at Aug 17, 2007,4:09 PM, james woodyatt wrote:


>
> On a related note, I've heard that some operators intend to deploy=20
> DHCP service using RA with M=3D1 and no PIO.  I don't understand how
> they imagine the "on-link flag" to be propagated in that scenario.  =20
> The "on-link flag" seems to be clearly in the domain of router=20
> function, not dynamic node configuration.  Is that to be described in=20
> the forthcoming Internet draft?
>
>


--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

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



From dhcwg-bounces@ietf.org Sun Aug 19 08:18:57 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMjiC-0004pO-TG; Sun, 19 Aug 2007 08:16:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMjiB-0004pA-Os; Sun, 19 Aug 2007 08:16:55 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IMji9-0000j2-Un; Sun, 19 Aug 2007 08:16:55 -0400
Received: from [82.192.90.28] (nirrti.muada.com [82.192.90.28])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l7JCDEsR072249
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Sun, 19 Aug 2007 14:13:15 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <EF8EA57D-E5E6-4083-9693-4C8EEABD4C85@cisco.com>
References: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<20070815194551.e2264a08.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<6D53AB8B-0E6C-4E07-A140-A9150C4C024F@muada.com>
	<EF8EA57D-E5E6-4083-9693-4C8EEABD4C85@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <E2AC76E0-8F55-40EF-8C04-FE76C1D0A691@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
Date: Sun, 19 Aug 2007 14:15:23 +0200
To: Ralph Droms <rdroms@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Cc: dhcwg@ietf.org, "ipv6@ietf.org Mailing List" <ipv6@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 18-aug-2007, at 17:37, Ralph Droms wrote:

> Therefore there is no need to provide a prefix length with an  
> assigned IPv6 address, whether that address is assigned through  
> SLAAC, DHCPv6, manual assignment or divine intervention.

Obviously we're not making progress here so I'm stopping my  
retransmissions.

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



From dhcwg-bounces@ietf.org Sun Aug 19 08:52:15 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMkEd-0004kI-1w; Sun, 19 Aug 2007 08:50:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMkEb-0004k8-Op; Sun, 19 Aug 2007 08:50:25 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IMkEb-0001OW-0k; Sun, 19 Aug 2007 08:50:25 -0400
Received: from [82.192.90.28] (nirrti.muada.com [82.192.90.28])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l7JCm4Bo072666
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Sun, 19 Aug 2007 14:48:05 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <6354B72A-EC4E-40DB-9A50-01036B1FEE39@apple.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
	<FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
	<8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
	<A822303F-0054-4462-866F-1689EBFE9958@apple.com> <979575!
	B 8-AEB8-4E22-A761-6422B9C20C51@muada.com>
	<6354B72A-EC4E-40DB-9A50-01036B1FEE39@apple.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <471515FC-E1E1-4C83-99AA-A9821E0C2FF5@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Sun, 19 Aug 2007 14:50:17 +0200
To: james woodyatt <jhw@apple.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: dhcwg@ietf.org, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: [dhcwg] Rethinking autoconfig,
	was Re: prefix length determination 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

On 17-aug-2007, at 22:09, james woodyatt wrote:

>> To stop unnecessary DHCP traffic. [...]

> I think what we're seeing here is a vocal faction of the community  
> who believe that DHCP discovery multicasts are always necessary,  
> whether RA is present or not, and whether M=0 or M=1, despite the  
> text in RFC 2462.

Right.

Over the course of this dicussion and remembering the previous ones  
about the M and O bits and what to do about DNS resolver  
configuration, I've reached the conclusion that DHCPv6 the way it is  
now is too incompatible with other aspects of IPv6 the way they are  
now. Also, even if we ignore the resulting difficulties, there are  
several needs that aren't met today. So I think it would be a good  
idea to take a leap forward and come up with something that actually  
does what we want rather than keep reinterpreting existing  
specifications and implementation behavior.

The goal is to make server-assisted autoconfiguration much more  
useful, and reduce the number of packets in general and multicast  
packets in particular, as well as any delays or timeouts in the  
autoconfiguration process.

The first step is to add an option to the router solicitation message  
that makes it possible to use this message as the start of a DHCP  
exchange. This way, a host doesn't have to know whether it will  
receive configuration through RAs or DHCP or both, and there is no  
delay if there are no RAs. I'm not sure whether the option should  
have a DUID identifier in it or that a small cookie that the DHCP  
server can recognize to see if the host needs new configuration is  
more efficient. Preferably, the option should be no larger than the  
minimum 8 bytes option size.

When the option is seen in a router solicitation, the info is  
forwarded through regular DHCP forwarders, or possibly be turned into  
an existing DHCP message for backward compatibility. Obviously DHCP  
servers on the link will listen for the messages directly. It is the  
job of the DHCP server to determine what type of configuration the  
host requires and respond with a unicast message if a response is  
needed. I'm thinking there are three types of configuration information:

- "shared" other configuration (= configuration items that are the  
same for all hosts on a link)
- host-specific but stateless configuration (i.e., if the DHCP server  
loses state it will still return the same configuration information  
later)
- stateful configuration

In most cases, the shared other configuration shouldn't be sent out  
by a DHCP server, but rather, be included in router advertisements.  
To make this simpler, router advertisements gain the capability to  
include DHCP options.

A new DHCP capability is address registration. This means that the  
host selects one or more addresses autonomously, and then tells the  
DHCP server about those addresses, for the following purposes:

- to avoid DAD
- to allow administrators to know which host uses which address at  
any given time
- to open up firewall holes
- to register addresses in the DNS

I'm not current on the work to reduce duplicate address detection,  
but unless I'm mistaken it should be possible to skip DAD on any  
address derived from an EUI-64 with the global/local bit set to  
"global". If all nodes that use these addresses do in fact derive  
them from an EUI-64 or 48-bit MAC address, then the only way a  
duplicate can happen is when there is a duplicate MAC address and  
then DAD is moot because communication can't happen anyway.

For all other addresses used on multiple access networks, i.e., ones  
where the g/l bit is set to "local" or where no 64-bit interface  
identifier was used because the subnet size is different than /64,  
it's necessary to make sure there are no duplicates. The idea here is  
that DAD and therefore several multicast packets and a timeout can be  
avoided by having a DHCP server keep track of the addresses that are  
in use on a subnet.

I'm assuming the other three uses speak for themselves.

I realize all of this requires significant extra work, but the upside  
is that it will give us a streamlined way to do autoconfiguration,  
both in the case where there is no coordination beyond a router  
advertising its presence and one or more prefixes, in the case where  
everything is managed and in the continuum inbetween, as opposed to  
the current toolbox of loosely related mechanisms that we have a hard  
time getting to work together well.

Obviously the above is only a fairly rough idea, there are lots of  
things to be worked out. If anyone is interested in working on this,  
please let me know in a private message.

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



From dhcwg-bounces@ietf.org Mon Aug 20 09:23:21 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IN7CE-0008Hl-DL; Mon, 20 Aug 2007 09:21:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IN7CC-0008HR-9D; Mon, 20 Aug 2007 09:21:28 -0400
Received: from brmea-mail-1.sun.com ([192.18.98.31])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IN7CA-0004zy-Qg; Mon, 20 Aug 2007 09:21:28 -0400
Received: from eastmail2bur.East.Sun.COM ([129.148.13.40])
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l7KDLPCu019179; Mon, 20 Aug 2007 13:21:26 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail2bur.East.Sun.COM (8.13.6+Sun/8.13.6/ENSMAIL,v2.2) with
	ESMTP id l7KDLP9x015283; Mon, 20 Aug 2007 09:21:25 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l7KD2d4q101784; Mon, 20 Aug 2007 09:02:39 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l7KD2Trf101781;
	Mon, 20 Aug 2007 09:02:29 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18121.37093.872115.212299@gargle.gargle.HOWL>
Date: Mon, 20 Aug 2007 09:02:29 -0400
From: James Carlson <james.d.carlson@sun.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <471515FC-E1E1-4C83-99AA-A9821E0C2FF5@muada.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
	<FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
	<8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
	<A822303F-0054-4462-866F-1689EBFE9958@apple.com>
	<6354B72A--EC4E-40DB-9A50-01036B1FEE39@apple.com>
	<471515FC-E1E1-4C83-99AA-A9821E0C2FF5@muada.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: dhcwg@ietf.org, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: [dhcwg] Re: Rethinking autoconfig,
	was Re: prefix length determination 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

Iljitsch van Beijnum writes:
> The first step is to add an option to the router solicitation message  
> that makes it possible to use this message as the start of a DHCP  
> exchange. This way, a host doesn't have to know whether it will  
> receive configuration through RAs or DHCP or both, and there is no  
> delay if there are no RAs. I'm not sure whether the option should  

I don't see what that fixes.  It appears to reduce the traffic from
three packets {RS, RA, DHCP Solicit} down to two {RS, RA "Enhanced"},
but I'm not sure why that's an important consideration.  Is getting
rid of one packet per link start-up a useful thing to do when it also
means that DHCPv6 servers and routers will be architecturally joined
at the hip, limiting deployment options, and when it means that
Proposed Standard documents need to be roto-tilled?

To me, that sounds like high cost with essentially no benefit.  What
am I missing?

> A new DHCP capability is address registration. This means that the  
> host selects one or more addresses autonomously, and then tells the  
> DHCP server about those addresses, for the following purposes:

You can already do that if you want.  See RFC 3315 section 18.1.1 --
you can include IAs for the addresses you want or already have in your
DHCP Request message.

> - to avoid DAD

Avoiding DAD doesn't sound like a good goal to me.  It means that the
system _assumes_ that the rest of the world is perfect and never has
any problems.

But do what you feel you must on your own networks and in your own
products.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From dhcwg-bounces@ietf.org Mon Aug 20 21:38:33 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INIfn-0003wg-Ox; Mon, 20 Aug 2007 21:36:47 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INIfl-0003vU-QS
	for dhcwg@ietf.org; Mon, 20 Aug 2007 21:36:45 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1INIfg-00041Y-Uk
	for dhcwg@ietf.org; Mon, 20 Aug 2007 21:36:41 -0400
Received: (qmail 37277 invoked from network); 21 Aug 2007 01:42:52 -0000
Received: from softbank219178199025.bbtec.net (HELO
	necom830.hpcl.titech.ac.jp) (219.178.199.25)
	by necom830.hpcl.titech.ac.jp with SMTP; 21 Aug 2007 01:42:52 -0000
Message-ID: <46CA4187.3050105@necom830.hpcl.titech.ac.jp>
Date: Tue, 21 Aug 2007 10:36:07 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com><18112.31505.383738.265939@gargle.gargle.HOWL><FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com><18113.42485.158453.756815@gargle.gargle.HOWL><20070814183418.GC3914@isc.org><18115.3756.371573.103258@gargle.gargle.HOWL><20070815175140.GC18683@isc.org><m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp><B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com><FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com><B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com><8706B8AE-001D-4403-A387-5255F67557F4@muada.com><B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com><39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com><B00EDD615E3C5344B0FFCBA910CF7E1D038814CF@xmb-rtp-20e.amer.ciisco.com><B00EDD615E3	C5344B0FFCBA
	910CF7E1D03881506@xmb-rtp-20e.amer.cisco.com>	<18117.52704.821730.341168@gargle.gargle.HOWL>
	<B00EDD615E3C5344B0FFCBA910CF7E1D03881522@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D03881522@xmb-rtp-20e.amer.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: ipv6@ietf.org, James Carlson <james.d.carlson@sun.com>, "Templin,
	Fred L" <Fred.L.Templin@boeing.com>,
	Iljitsch van Beijnum <iljitsch@muada.com>, dhcwg@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
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

Hemant Singh (shemant) wrote:

> Unless anyone can mention a lot of potential IPv6 deployments that will
> deploy IPv6 without a router sending RA, it's not even worth discussing
> the subject.

I pointed it out several times in IPv6 related WGs that RA work poorly
over links with unreliable multicast/broadcast, such as wireless LANs.

ND is designed so poorly that it barely works only over Ethernet
and PPP.

Don't expect ND reasonably work even over Ethernet.

							Masataka Ohta


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



From dhcwg-bounces@ietf.org Mon Aug 20 22:28:04 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INJRk-0001MO-Dn; Mon, 20 Aug 2007 22:26:20 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INJRk-0001MF-12; Mon, 20 Aug 2007 22:26:20 -0400
Received: from zns001-0m9003.yokogawa.co.jp ([203.174.79.161])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1INJRj-00052m-DP; Mon, 20 Aug 2007 22:26:19 -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
	l7L2QFik010684; Tue, 21 Aug 2007 11:26:15 +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
	l7L2QFYf010681; Tue, 21 Aug 2007 11:26:15 +0900 (JST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 21 Aug 2007 11:26:14 +0900
Message-ID: <0260031F55435342859BFB2CCA6773D81B898C13@EXCHANGE03.jp.ykgw.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Is a DNS NS required,
	when a DHCPv6 Client transmits a Conform message? 
Thread-Index: AcfjmqWo6+MgFrvIRz2RPMwLaZmuGQ==
From: <Hideshi.Enokihara@jp.yokogawa.com>
To: <dhcwg@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: ipv6@ietf.org
Subject: [dhcwg] Is a DNS NS required,
	when a DHCPv6 Client transmits a Conform message? 
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 all,

In the situation in which DHCPv6 clinet transmits a Conform message for
its Global address,
should the DHCPv6 Client do DAD?

When the DAD NS should be transmitted, if it is required to transmit a
DAD NS from DHCPv6 Client?
Should the DAD NS be transmitted after sending the Conform messge and
receiving the Reply? Or before sending the Conform message?

I'm waiting for your valuable replies.

Best regards,
Hideshi

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



From dhcwg-bounces@ietf.org Mon Aug 20 23:38:41 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INKY4-000713-Cb; Mon, 20 Aug 2007 23:36:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INKY1-00070v-Mg; Mon, 20 Aug 2007 23:36:53 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1INKY0-0002X3-Gf; Mon, 20 Aug 2007 23:36:53 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 20 Aug 2007 23:36:52 -0400
X-IronPort-AV: i="4.19,286,1183348800"; 
	d="scan'208"; a="129410449:sNHT57400222"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7L3aqbc029768; 
	Mon, 20 Aug 2007 23:36:52 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l7L3apmd008646; 
	Tue, 21 Aug 2007 03:36:51 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Aug 2007 23:36:51 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 20 Aug 2007 23:36:50 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB2104D4B11F@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <0260031F55435342859BFB2CCA6773D81B898C13@EXCHANGE03.jp.ykgw.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Is a DNS NS required,
	when a DHCPv6 Client transmits a Conform message? 
Thread-Index: AcfjmqWo6+MgFrvIRz2RPMwLaZmuGQACO9tg
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: <Hideshi.Enokihara@jp.yokogawa.com>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 21 Aug 2007 03:36:51.0631 (UTC)
	FILETIME=[830F53F0:01C7E3A4]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1431; t=1187667412;
	x=1188531412; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=volz@cisco.com;
	z=From:=20=22Bernie=20Volz=20\(volz\)=22=20<volz@cisco.com>
	|Subject:=20RE=3A=20Is=20a=20DNS=20NS=20required,
	when=20a=20DHCPv6=20Clie
	nt=20transmits=20a=20Conform=20message?=20 |Sender:=20
	|To:=20<Hideshi.Enokihara@jp.yokogawa.com>,=20<dhcwg@ietf.org>;
	bh=MerbJvl2kETumtlYkLK34xmUXhU/1kfPWtBuCnEg4BE=;
	b=t2wTx3tnitqMofd0AvCeLr9Oj3p7dmtEDtd9BgzlYfzE2wW+/vuutPzUb1i/xIf8pesenPRv
	+INj9vqTXeh9mVA7VzFpaVR0qLy2Dzy2uDAPJO/3bX1jjGKhMmfmT8HR;
Authentication-Results: rtp-dkim-2; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: ipv6@ietf.org
Subject: [dhcwg] RE: Is a DNS NS required,
	when a DHCPv6 Client transmits a Conform message? 
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

Hideshi:

There are really two parts to this:
1. Is DAD for the link-local done when an interface "reconnect" is
detected? This may be required before multicasting the Confirm.
2. Is DAD for done for the global addresses (AFTER a successful
indication from a DHCPv6 Confirm is received, since there's no point to
do it before as the client doesn't know yet whether the addresses are
invalid)?

I'm not sure that this is a DHCP question ... Probably should be
directed at the IPv6 WG?

- Bernie

-----Original Message-----
From: Hideshi.Enokihara@jp.yokogawa.com
[mailto:Hideshi.Enokihara@jp.yokogawa.com]=20
Sent: Monday, August 20, 2007 10:26 PM
To: dhcwg@ietf.org
Cc: ipv6@ietf.org
Subject: Is a DNS NS required,when a DHCPv6 Client transmits a Conform
message?=20

Hello all,

In the situation in which DHCPv6 clinet transmits a Conform message for
its Global address,
should the DHCPv6 Client do DAD?

When the DAD NS should be transmitted, if it is required to transmit a
DAD NS from DHCPv6 Client?
Should the DAD NS be transmitted after sending the Conform messge and
receiving the Reply? Or before sending the Conform message?

I'm waiting for your valuable replies.

Best regards,
Hideshi

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

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



From dhcwg-bounces@ietf.org Tue Aug 21 03:30:46 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INOAe-0001CB-OP; Tue, 21 Aug 2007 03:29:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INOAd-0001C2-SW; Tue, 21 Aug 2007 03:28:59 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1INOAd-0006uB-9S; Tue, 21 Aug 2007 03:28:59 -0400
Received: from jmb.local (unknown [IPv6:2001:200:1b1:101a:217:f2ff:fe26:34a0])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id A21D17301F;
	Tue, 21 Aug 2007 16:28:57 +0900 (JST)
Date: Tue, 21 Aug 2007 16:28:50 +0900
Message-ID: <m1ps1hxs5p.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: "Bernie Volz (volz)" <volz@cisco.com>
Subject: Re: [dhcwg] RE: Is a DNS NS required,
	when a DHCPv6 Client transmits a Conform message? 
In-Reply-To: <8E296595B6471A4689555D5D725EBB2104D4B11F@xmb-rtp-20a.amer.cisco.com>
References: <0260031F55435342859BFB2CCA6773D81B898C13@EXCHANGE03.jp.ykgw.net>
	<8E296595B6471A4689555D5D725EBB2104D4B11F@xmb-rtp-20a.amer.cisco.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.0 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-Spam-Score: -0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: dhcwg@ietf.org, ipv6@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

At Mon, 20 Aug 2007 23:36:50 -0400,
"Bernie Volz (volz)" <volz@cisco.com> wrote:

> There are really two parts to this:
> 1. Is DAD for the link-local done when an interface "reconnect" is
> detected? This may be required before multicasting the Confirm.
> 2. Is DAD for done for the global addresses (AFTER a successful
> indication from a DHCPv6 Confirm is received, since there's no point to
> do it before as the client doesn't know yet whether the addresses are
> invalid)?
> 
> I'm not sure that this is a DHCP question ... Probably should be
> directed at the IPv6 WG?

I don't think it's a DHCPv6 question, either.  The real question is
whether a host should perform DAD when it detects a possible change of
attached link.  Referring to Section 18.1.2 of RFC3315, those case
would include:

   o  The host (client) reboots.
   o  The host (client) is physically connected to a wired connection.
   o  The host (client) returns from sleep mode.
   o  The host (client) using a wireless technology changes access points.

I think it's reasonable to perform DAD for at least some of these
cases, but as far as I know no specification explicitly requires that.

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

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



From dhcwg-bounces@ietf.org Tue Aug 21 05:40:12 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INQBv-00040Q-5Z; Tue, 21 Aug 2007 05:38:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INQBt-000402-27; Tue, 21 Aug 2007 05:38:25 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1INQBs-0007cp-B1; Tue, 21 Aug 2007 05:38:24 -0400
Received: from [82.192.90.28] (nirrti.muada.com [82.192.90.28])
	(authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l7L9a60l014957
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Tue, 21 Aug 2007 11:36:06 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <18121.37093.872115.212299@gargle.gargle.HOWL>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
	<FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
	<8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
	<A822303F-0054-4462-866F-1689EBFE9958@apple.com> <6354B7!
	2A--EC4E-40DB-9A50-01036B1FEE39@apple.com>
	<471515FC-E1E1-4C83-99AA-A9821E0C2FF5@muada.com>
	<18121.37093.872115.212299@gargle.gargle.HOWL>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <BAA24DD4-8DF1-4C72-969A-37ACF82637B7@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Tue, 21 Aug 2007 11:38:20 +0200
To: James Carlson <james.d.carlson@sun.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: dhcwg@ietf.org, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: [dhcwg] Re: Rethinking autoconfig,
	was Re: prefix length determination 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

On 20-aug-2007, at 15:02, James Carlson wrote:

>> The first step is to add an option to the router solicitation message
>> that makes it possible to use this message as the start of a DHCP
>> exchange. This way, a host doesn't have to know whether it will
>> receive configuration through RAs or DHCP or both, and there is no
>> delay if there are no RAs. I'm not sure whether the option should

> I don't see what that fixes.  It appears to reduce the traffic from
> three packets {RS, RA, DHCP Solicit} down to two {RS, RA "Enhanced"},
> but I'm not sure why that's an important consideration.  Is getting
> rid of one packet per link start-up a useful thing to do when it also
> means that DHCPv6 servers and routers will be architecturally joined
> at the hip, limiting deployment options, and when it means that
> Proposed Standard documents need to be roto-tilled?

> To me, that sounds like high cost with essentially no benefit.  What
> am I missing?

What it does and saves is very much dependent on the circumstances.

Saving one or two packets here or there in and of itself is probably  
not compelling (but a good secondary goal because those multicasts  
can clog up wireless networks). The main benefit is that it  
simplifies the host behavior: rather than either holding off on DHCP  
depending on value of the M and O bits, which costs extra time, or  
ignoring the M and O bits and adding a fairly significant number of  
discovery packets, a host can always do the same thing and reach the  
optimum result as fast as possible, regardless of whether the network  
runs with RAs only, stateless autoconfig + DHCP for other  
configuration, stateless autoconfig + stateful config combined, RAs  
but no stateless autoconfig with DHCP, or even no RAs at all and just  
DHCP. The way things are now, host behavior will be suboptimal for at  
least some of these situations.

>> A new DHCP capability is address registration. This means that the
>> host selects one or more addresses autonomously, and then tells the
>> DHCP server about those addresses, for the following purposes:

> You can already do that if you want.  See RFC 3315 section 18.1.1 --
> you can include IAs for the addresses you want or already have in your
> DHCP Request message.

Excellent.

>> - to avoid DAD

> Avoiding DAD doesn't sound like a good goal to me.  It means that the
> system _assumes_ that the rest of the world is perfect and never has
> any problems.

Let me rephrase: making DAD more efficient. If there's a DHCP server  
present that knows about all addresses anyway, then obviously the  
DHCP server is capable of determining whether two nodes are trying to  
use the same address, which is probably more efficient than hosts  
doing DAD for each address.

Personally, I'm comfortable with foregoing DAD on EUI-64 derived  
addresses, because if the EUI-64 uniqueness fails things aren't going  
to work anyway. There is always the possibility of someone  
configuring a duplicate EUI-64 address manually, though, so there is  
still _some_ potential for trouble. So I guess no DAD for EUI-64 or  
DAD for everything is something that network administrators should be  
able to control.

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



From dhcwg-bounces@ietf.org Tue Aug 21 08:35:15 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INSvJ-0004k9-CU; Tue, 21 Aug 2007 08:33:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INSvH-0004k1-QJ; Tue, 21 Aug 2007 08:33:27 -0400
Received: from mx.isc.org ([2001:4f8:0:2::1c])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1INSvG-0007Oj-92; Tue, 21 Aug 2007 08:33:27 -0400
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "farside.isc.org", Issuer "ISC CA" (verified OK))
	by mx.isc.org (Postfix) with ESMTP id 4ECF4114027;
	Tue, 21 Aug 2007 12:33:25 +0000 (UTC)
	(envelope-from Shane_Kerr@isc.org)
Received: from [192.168.1.10] (hurix.ams-ix.net [193.194.136.45])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by farside.isc.org (Postfix) with ESMTP id 6C911E6009;
	Tue, 21 Aug 2007 12:33:24 +0000 (UTC) (envelope-from shane@isc.org)
Message-ID: <46CADB91.6050504@isc.org>
Date: Tue, 21 Aug 2007 14:33:21 +0200
From: Shane Kerr <Shane_Kerr@isc.org>
Organization: ISC
User-Agent: Thunderbird 2.0.0.6 (X11/20070806)
MIME-Version: 1.0
To: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
References: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>	<7ECEF9368E169544B43882BC98EB5D92032DA840@SVR-ALH-EXC-02.mgc.mentorg.com>	<m2zm0ywj2a.wl%jinmei@isl.rdc.toshiba.co.jp>	<20070813161026.GA4846@isc.org>
	<E2E6A987-046A-44D9-923F-F17F95AFFDD2@apple.com>
In-Reply-To: <E2E6A987-046A-44D9-923F-F17F95AFFDD2@apple.com>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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

james woodyatt wrote:
> On Aug 13, 2007, at 09:10, David W. Hankins wrote:
>> On Sat, Aug 11, 2007 at 05:51:09PM +0900, JINMEI Tatuya / =E7=A5=9E=E6=
=98=8E=E9=81=94=E5=93=89 wrote:
>>>
>>> In any event, I hear that some DHCPv6 guys are planning to make a new
>>> draft that covers this topic.  So I think it's better to hold off for
>>> now and wait for the document, rather than continue this thread
>>> with keeping possible misunderstanding or confusing about the base
>>> protocol principles.
>>
>> I agree with everything Jinmei said, but this in particular.  Any
>> conclusions from these threads have a tendency to get forgotten -
>> it's better that we argue the position of a draft that an editor
>> can follow consensus.
>=20
> I agree with M. Jinmei as far as the quoted excerpt above goes.
>=20
> As much as I dislike DHCPv6 on general principle, I don't expect that
> IETF will abandon it in favor of a system that more coherently addresse=
s
> the various separate concerns that DHCPv6 attempts to meet.  I hope the
> DHC WG will specify requirements for routers sending advertisements wit=
h
> the M bit set that prevent any ambiguity from arising at the node durin=
g
> link configuration.
>=20
> p.s. I really wish IETF had deprecated DHCPv6 when it had the chance.=20
> Every last thing DHCPv6 does belongs in one of two other, separate
> domains, i.e. either in the sub-IP layer, e.g. EAP, or at the
> sub-application layer, e.g. DNS-SD.  Instead, IETF chose a short-sighte=
d
> and half-baked solution to a problem that really didn't need a rush job
> to solve, and the engineering community today is poorer for it.

We need DHCP.

DHCP is used by administrators to do a lot more than simply assign IP
addresses. It is an extremely flexible protocol, and works for lots of
different models of network topology and administrative setup. Any
protocol which did the work that DHCP does would end up looking
suspiciously like DHCP at the end (RFC 3315 gets my vote as one of the
clearest, easiest to implement RFCs, BTW).


I know there's a lot of anti-DHCP sentiment, especially in the IPv6
crowd. I think it is misplaced; DHCP is at worst a necessary evil, and
at best an elegant solution to the problem space where it sits.

Router advertisements cannot do what DHCP does. An RA can carry a
small bit of information, but as a full replacement, the idea falls
flat. You don't always want to broadcast the same information to all
clients. Some hosts want vendor-specific information that will never
be standardized into an RA. A few people may even want to authenticate
their hosts' configurations. And on and on...


At the most basic level, a computer connecting to the network expects to
get an IP address, routing information, and DNS information. Until *last
year*, there was no standard way to get DNS information from an RA. Now
that this "problem" has been solved (*), what next? What about other
basic things like updating the reverse DNS information? What about being
able to log when a given IP was in use for legal, or (far more
importantly) billing purposes?

(*) I put "problem" in quotes because you could use DHCPv6 for this
    since 2003 or so.

It may be possible to force much of this information in to RAs, having
multiple protocols to do one thing is a bad idea, right?


We need DHCP - in IPv6 as much as in IPv4 - so can we please let this
idea that we can do everything in RA die? Please?

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

iD8DBQFGytuOMsfZxBO4kbQRAj1gAKCF2shHEhrbOU+4g8E53g1OhlHTMQCfQVfa
dgyOZkLI+EVd86rkYwmOTmM=3D
=3DDtH/
-----END PGP SIGNATURE-----

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



From dhcwg-bounces@ietf.org Tue Aug 21 08:45:48 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INT5Y-0005yA-1M; Tue, 21 Aug 2007 08:44:04 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INT5V-0005xj-Mr; Tue, 21 Aug 2007 08:44:01 -0400
Received: from e36.co.us.ibm.com ([32.97.110.154])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1INT5U-00044m-8D; Tue, 21 Aug 2007 08:44:00 -0400
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com
	[9.17.195.227])
	by e36.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l7LChxwL016130;
	Tue, 21 Aug 2007 08:43:59 -0400
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169])
	by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v8.5) with ESMTP id
	l7LChxfI258674; Tue, 21 Aug 2007 06:43:59 -0600
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1])
	by d03av03.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l7LChwf1019677; Tue, 21 Aug 2007 06:43:59 -0600
Received: from cichlid.raleigh.ibm.com (wecm-9-67-203-58.wecm.ibm.com
	[9.67.203.58])
	by d03av03.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l7LChvXr019601
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Tue, 21 Aug 2007 06:43:58 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1])
	by cichlid.raleigh.ibm.com (8.14.1/8.12.5) with ESMTP id l7LChZx4004223;
	Tue, 21 Aug 2007 08:43:35 -0400
Message-Id: <200708211243.l7LChZx4004223@cichlid.raleigh.ibm.com>
To: "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [dhcwg] RE: Is a DNS NS required,
	when a DHCPv6 Client transmits a Conform message? 
In-reply-to: <8E296595B6471A4689555D5D725EBB2104D4B11F@xmb-rtp-20a.amer.cisco.com>
References: <8E296595B6471A4689555D5D725EBB2104D4B11F@xmb-rtp-20a.amer.cisco.com>
Comments: In-reply-to "Bernie Volz \(volz\)" <volz@cisco.com>
	message dated "Mon, 20 Aug 2007 23:36:50 -0400."
Date: Tue, 21 Aug 2007 08:43:35 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Cc: dhcwg@ietf.org, ipv6@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

> I'm not sure that this is a DHCP question ... Probably should be
> directed at the IPv6 WG?

Or perhaps DNA, which is grappling with the general issue of how to
deal (quickly) with reattachments to the same link, and what should
done in such cases.

Thomas

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



From dhcwg-bounces@ietf.org Tue Aug 21 09:06:35 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INTPe-0006I3-Ql; Tue, 21 Aug 2007 09:04:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INTPd-0006Hd-3M; Tue, 21 Aug 2007 09:04:49 -0400
Received: from brmea-mail-2.sun.com ([192.18.98.43])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1INTPc-0008IC-Fs; Tue, 21 Aug 2007 09:04:49 -0400
Received: from dm-east-02.east.sun.com ([129.148.13.5])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l7LD4lYK027614; Tue, 21 Aug 2007 13:04:47 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by dm-east-02.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP
	id l7LD44i7003161; Tue, 21 Aug 2007 09:04:19 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l7LCqo9W105867; Tue, 21 Aug 2007 08:52:50 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l7LCqnU7105864;
	Tue, 21 Aug 2007 08:52:50 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18122.57377.942962.976694@gargle.gargle.HOWL>
Date: Tue, 21 Aug 2007 08:52:49 -0400
From: James Carlson <james.d.carlson@sun.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <BAA24DD4-8DF1-4C72-969A-37ACF82637B7@muada.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
	<8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<18112.31505.383738.265939@gargle.gargle.HOWL>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
	<FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
	<8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
	<A822303F-0054-4462-866F-1689EBFE9958@apple.com>
	<471515FC--E1E1-4C83-99AA-A9821E0C2FF5@muada.com>
	<18121.37093.872115.212299@gargle.gargle.HOWL>
	<BAA24DD4-8DF1-4C72-969A-37ACF82637B7@muada.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: dhcwg@ietf.org, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: [dhcwg] Re: Rethinking autoconfig,
 was Re: prefix length determination 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

Iljitsch van Beijnum writes:
> On 20-aug-2007, at 15:02, James Carlson wrote:
> > To me, that sounds like high cost with essentially no benefit.  What
> > am I missing?
> 
> What it does and saves is very much dependent on the circumstances.
> 
> Saving one or two packets here or there in and of itself is probably  
> not compelling (but a good secondary goal because those multicasts  
> can clog up wireless networks). The main benefit is that it  
> simplifies the host behavior: rather than either holding off on DHCP  

Actually, it doesn't do that either.

It doesn't do that because we _already_ have deployed implementations
of all of the existing protocols.  There are systems out there that
already have separate router discovery and DHCP, already work, and
that are unlikely to be "upgraded" at any point in the near future --
if ever at all.

Because of that, any robust implementation of the scheme you're
suggesting would need to support _both_ types of operation.  That
includes most sane vendors: they'll be forced to implement, test, and
support both modes of operation in all of their products.

The alternative leads to an interoperability problem.  A new-style
client introduced into an old-style network won't get the
all-inclusive RAs with DHCP data that it wants, and will then be
forced to drop back to the previous (now existing) mode of operation
with DHCP Solicit.

Thus, adding new features like you're suggesting is always more
complex.  It's only by _removing_ features that we can make things
simpler.

> > Avoiding DAD doesn't sound like a good goal to me.  It means that the
> > system _assumes_ that the rest of the world is perfect and never has
> > any problems.
> 
> Let me rephrase: making DAD more efficient. If there's a DHCP server  
> present that knows about all addresses anyway, then obviously the  
> DHCP server is capable of determining whether two nodes are trying to  
> use the same address, which is probably more efficient than hosts  
> doing DAD for each address.

This means that the DHCP server is perfect in its operation and
omniscient about all hosts that may be attached to the network, even
the statically-configured ones.

I've yet to meet one that is this good.

> Personally, I'm comfortable with foregoing DAD on EUI-64 derived  
> addresses, because if the EUI-64 uniqueness fails things aren't going  
> to work anyway. There is always the possibility of someone  
> configuring a duplicate EUI-64 address manually, though, so there is  
> still _some_ potential for trouble. So I guess no DAD for EUI-64 or  
> DAD for everything is something that network administrators should be  
> able to control.

I have no problem with implementations including a tunable to disable
DAD for the people who like to work without a net (both figuratively
and literally), but the default still ought to be to use DAD, and
nothing DHCPv6 does ought to discourage that.

To use a phrase from another era: "trust, but verify."

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From dhcwg-bounces@ietf.org Tue Aug 21 09:09:41 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INTSf-0000cs-Jv; Tue, 21 Aug 2007 09:07:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INTSe-0000ch-FY; Tue, 21 Aug 2007 09:07:56 -0400
Received: from coconut.itojun.org ([2001:240:501:0:204:23ff:fecb:8908])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1INTSd-00006Q-Qo; Tue, 21 Aug 2007 09:07:56 -0400
Received: by coconut.itojun.org (Postfix, from userid 501)
	id E70E4233EA; Tue, 21 Aug 2007 22:07:53 +0900 (JST)
To: dhcwg@ietf.org, ipv6@ietf.org
In-Reply-To: Your message of "Tue, 21 Aug 2007 08:52:49 -0400"
	<18122.57377.942962.976694@gargle.gargle.HOWL>
References: <18122.57377.942962.976694@gargle.gargle.HOWL>
X-Mailer: Cue version 0.8 (070521-1856/itojun)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20070821130753.E70E4233EA@coconut.itojun.org>
Date: Tue, 21 Aug 2007 22:07:53 +0900 (JST)
From: itojun@itojun.org (Jun-ichiro itojun Hagino)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 2870a44b67ee17965ce5ad0177e150f4
Cc: 
Subject: [dhcwg] Re: Rethinking autoconfig,
 was Re: prefix length determination 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

	<rant>i wonder how many of those who are voicing opinion here are
	actually using IPv6 in a daily basis.</rant>

itojun

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



From dhcwg-bounces@ietf.org Tue Aug 21 09:51:43 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INU7I-0002a0-TM; Tue, 21 Aug 2007 09:49:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INU7G-0002ZA-EA; Tue, 21 Aug 2007 09:49:54 -0400
Received: from brmea-mail-2.sun.com ([192.18.98.43])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1INU7E-0001yy-Ty; Tue, 21 Aug 2007 09:49:54 -0400
Received: from dm-east-01.east.sun.com ([129.148.9.192])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l7LDnqeJ022485; Tue, 21 Aug 2007 13:49:52 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by dm-east-01.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP
	id l7LDnpf8000507; Tue, 21 Aug 2007 09:49:51 -0400 (EDT)
Received: from phorcys.east.sun.com (localhost [127.0.0.1])
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1) with ESMTP id
	l7LDgE6N106053; Tue, 21 Aug 2007 09:42:14 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l7LDgEat106050;
	Tue, 21 Aug 2007 09:42:14 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18122.60342.174942.84674@gargle.gargle.HOWL>
Date: Tue, 21 Aug 2007 09:42:14 -0400
From: James Carlson <james.d.carlson@sun.com>
To: itojun@itojun.org (Jun-ichiro itojun Hagino)
In-Reply-To: <20070821130753.E70E4233EA@coconut.itojun.org>
References: <18122.57377.942962.976694@gargle.gargle.HOWL>
	<20070821130753.E70E4233EA@coconut.itojun.org>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Cc: dhcwg@ietf.org, ipv6@ietf.org
Subject: [dhcwg] Re: Rethinking autoconfig,
 was Re: prefix length determination 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

Jun-ichiro itojun Hagino writes:
> 	<rant>i wonder how many of those who are voicing opinion here are
> 	actually using IPv6 in a daily basis.</rant>

I am.  Does that help?

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

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



From dhcwg-bounces@ietf.org Tue Aug 21 10:26:22 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INUet-0007v1-Ck; Tue, 21 Aug 2007 10:24:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INUer-0007m9-FS; Tue, 21 Aug 2007 10:24:37 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1INUer-00039Z-1V; Tue, 21 Aug 2007 10:24:37 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 21 Aug 2007 10:24:35 -0400
X-IronPort-AV: i="4.19,290,1183348800"; 
	d="scan'208"; a="68584422:sNHT47650206"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7LEOaZW011711; 
	Tue, 21 Aug 2007 10:24:36 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7LEOZjS020979; 
	Tue, 21 Aug 2007 14:24:36 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Aug 2007 10:24:29 -0400
Received: from [161.44.65.201] ([161.44.65.201]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 21 Aug 2007 10:24:28 -0400
In-Reply-To: <20070821130753.E70E4233EA@coconut.itojun.org>
References: <18122.57377.942962.976694@gargle.gargle.HOWL>
	<20070821130753.E70E4233EA@coconut.itojun.org>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <4F5299F4-4BDD-4698-80DB-2A7D6976D3C1@cisco.com>
Content-Transfer-Encoding: 7bit
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Re: Rethinking autoconfig,
	was Re: prefix length determination for DHCPv6
Date: Tue, 21 Aug 2007 10:25:31 -0400
To: itojun@itojun.org (Jun-ichiro itojun Hagino)
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 21 Aug 2007 14:24:28.0836 (UTC)
	FILETIME=[FBC24640:01C7E3FE]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=614; t=1187706276;
	x=1188570276; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rdroms@cisco.com;
	z=From:=20Ralph=20Droms=20<rdroms@cisco.com>
	|Subject:=20Re=3A=20[dhcwg]=20Re=3A=20Rethinking=20autoconfig,
	=20was=20Re
	=3A=20prefix=20length=20determination=20for=20DHCPv6
	|Sender:=20
	|To:=20itojun@itojun.org=20(Jun-ichiro=20itojun=20Hagino);
	bh=+lSSadbs9J26oy39x+0Urnx0LaO4kfOYoHptrUl8NSw=;
	b=tlPOPtPuFhv2Qwd8QNi2bF1EtFvtoZ0ARd1ZPZJdTAxnkJORyscGydrXksN+kEvQNEw3rnVR
	WIgdV6qGipJaaixp9KABUedNMZu4AIRxHCYYy/yARBtGXlBSkjn/ZCvO;
Authentication-Results: rtp-dkim-2; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: dhcwg@ietf.org, ipv6@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

I don't use or administer IPv6 on a daily basis. I do run an IPv6  
testbed and experiment with various clients against the Cisco IOS and  
CNR DHCP servers, so I have some experience with host configuration  
using SLAAC, DHCP, SLAAC+DHCP...

- Ralph

On Aug 21, 2007, at Aug 21, 2007,9:07 AM, Jun-ichiro itojun Hagino  
wrote:

> 	<rant>i wonder how many of those who are voicing opinion here are
> 	actually using IPv6 in a daily basis.</rant>
>
> itojun
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg

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



From dhcwg-bounces@ietf.org Tue Aug 21 13:36:33 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INXcs-0002zu-QI; Tue, 21 Aug 2007 13:34:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INXcr-0002zm-Ew; Tue, 21 Aug 2007 13:34:45 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1INXcr-0001vx-4M; Tue, 21 Aug 2007 13:34:45 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 7B1025A6E5; Tue, 21 Aug 2007 10:34:44 -0700 (PDT)
Date: Tue, 21 Aug 2007 10:34:44 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: ipv6@ietf.org
Subject: Re: [dhcwg] Re: Rethinking autoconfig,
	was Re: prefix length determination for DHCPv6
Message-ID: <20070821173444.GC16213@isc.org>
References: <18122.57377.942962.976694@gargle.gargle.HOWL>
	<20070821130753.E70E4233EA@coconut.itojun.org>
Mime-Version: 1.0
In-Reply-To: <20070821130753.E70E4233EA@coconut.itojun.org>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0367991120=="
Errors-To: dhcwg-bounces@ietf.org


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


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

On Tue, Aug 21, 2007 at 10:07:53PM +0900, Jun-ichiro itojun Hagino wrote:
> 	<rant>i wonder how many of those who are voicing opinion here are
> 	actually using IPv6 in a daily basis.</rant>

ISC is native IPv6, no tunnels (except to employees' homes), dual
stack.

We are, proverbially, "soaking in it."

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

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

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

iD8DBQFGyyI0cXeLeWu2vmoRAoEMAJ9PYTPdKDs1R8TMMEKdGd7STC/r3ACfab0E
NFfDJcDv0ahNgsK4TV/hI9g=
=JLL0
-----END PGP SIGNATURE-----

--dkEUBIird37B8yKS--


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

--===============0367991120==--




From dhcwg-bounces@ietf.org Tue Aug 21 15:24:04 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INZIx-0008Qk-2k; Tue, 21 Aug 2007 15:22:19 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INZIw-0008Qb-36; Tue, 21 Aug 2007 15:22:18 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1INZIv-00019K-M9; Tue, 21 Aug 2007 15:22:18 -0400
Received: from relay12.apple.com (relay12.apple.com [17.128.113.53])
	by mail-out3.apple.com (Postfix) with ESMTP id B521DF14D76;
	Tue, 21 Aug 2007 12:22:16 -0700 (PDT)
Received: from relay12.apple.com (unknown [127.0.0.1])
	by relay12.apple.com (Symantec Mail Security) with ESMTP id 853002885C; 
	Tue, 21 Aug 2007 12:22:16 -0700 (PDT)
X-AuditID: 11807135-a5f64bb000000813-bd-46cb3b68de4a
Received: from [17.206.23.199] (il0602a-dhcp71.apple.com [17.206.23.199])
	by relay12.apple.com (Symantec Mail Security) with ESMTP id 6EF962883D; 
	Tue, 21 Aug 2007 12:22:16 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <46CADB91.6050504@isc.org>
References: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>
	<7ECEF9368E169544B43882BC98EB5D92032DA840@SVR-ALH-EXC-02.mgc.mentorg.com>
	<m2zm0ywj2a.wl%jinmei@isl.rdc.toshiba.co.jp>
	<20070813161026.GA4846@isc.org>
	<E2E6A987-046A-44D9-923F-F17F95AFFDD2@apple.com>
	<46CADB91.6050504@isc.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <2E1BF02E-EEB3-48D9-A40B-E028056306FD@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
Date: Tue, 21 Aug 2007 12:22:04 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>,
 dhcwg@ietf.org
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Aug 21, 2007, at 05:33, Shane Kerr wrote:
>
> [...] having multiple protocols to do one thing is a bad idea, right?

Yes, but having one protocol to do multiple things in cross-cutting  
problem domains is a bad idea, too.

> We need DHCP - in IPv6 as much as in IPv4 - so can we please let  
> this idea that we can do everything in RA die? Please?

I don't want to see RA get bloated out with all the functions  
currently jammed into DHCP.  That would only expand the boundaries of  
the current trouble, rather than addressing any real problems.  I'd  
prefer to see the functions of DHCP split into profiles of other  
existing protocols, e.g. EAP, IKE, DNS-SD, etc.  Any additions to RA  
needed to facilitate those operations should be strenuously avoided.

My major philosophical complaints about DHCP are that it (a) wastes  
multicast network resources doing unnecessary infrastructure  
discovery, (b) conflates interface address and node authorization  
identity for accounting purposes, and (c) complicates network  
configuration by drawing an unnecessary distinction between host  
configuration and other application data.  I realize that others have  
differing opinions, and I fully respect them.  These are mine, and if  
you don't like them, then I have others.

I don't agree that we *need* DHCP, but I'll agree that we *have* DHCP  
and it makes practical sense to use it in the interim while we  
develop a more practical alternative.  We need something better than  
DHCP.  It's just *not* a very good hammer-- and, you know what they  
say: when all you have is a hammer, everything begins to look like a  
folk singer.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering



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



From dhcwg-bounces@ietf.org Tue Aug 21 16:11:20 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INa2f-0004fY-A4; Tue, 21 Aug 2007 16:09:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INa2e-0004fS-S5
	for dhcwg@ietf.org; Tue, 21 Aug 2007 16:09:32 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INa2e-000698-By
	for dhcwg@ietf.org; Tue, 21 Aug 2007 16:09:32 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 9F1105A6E5; Tue, 21 Aug 2007 13:09:31 -0700 (PDT)
Date: Tue, 21 Aug 2007 13:09:31 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Message-ID: <20070821200931.GE16213@isc.org>
Mime-Version: 1.0
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Subject: [dhcwg] lifetime of 'peer-address'
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1174651815=="
Errors-To: dhcwg-bounces@ietf.org


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


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

I've been making an assumption, an unfounded one, based entirely upon
a lack of indication contrarywise, that the 'peer-address' field or
similarly where no relay is present the source IPv6 address of a
DHCPv6 packet is temporary state.

That is, "this is the address to send replies to this transaction" at
most and never "this is a permanent (probably link local) address you
can use now or at any time in the future to reach this endpoint."

This basic understanding was questioned on a recent discussion on
ipv6@ietf.org, and I wondered what other opinions there were.


I tend to think that any expectation that a DHCPv6 client "will
always" Renew or Rebind or even Solicit when any link local addresses
have changed or disappeared is naive, so I don't think this
information can realistically be counted on.  I don't think the
client's source address is a contract for longer than it takes to
reply to the query (same of the server's or relay agent's source
addresses).

--=20
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil?	 https://secure.isc.org/store/t-shirt/
--=20
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins

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

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

iD8DBQFGy0Z7cXeLeWu2vmoRAqLwAJ9mFL4oCMLadl2+y8gXP4SZS6hrlgCbB+u6
+CZVsskc5dU6LycnV8Tng48=
=wRF4
-----END PGP SIGNATURE-----

--cHMo6Wbp1wrKhbfi--


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

--===============1174651815==--




From dhcwg-bounces@ietf.org Tue Aug 21 20:01:31 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INddc-0005eW-4R; Tue, 21 Aug 2007 19:59:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INdda-0005eF-27
	for dhcwg@ietf.org; Tue, 21 Aug 2007 19:59:54 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1INddY-0003Sj-4Q
	for dhcwg@ietf.org; Tue, 21 Aug 2007 19:59:54 -0400
Received: (qmail 91079 invoked from network); 22 Aug 2007 00:06:23 -0000
Received: from softbank219178199025.bbtec.net (HELO
	necom830.hpcl.titech.ac.jp) (219.178.199.25)
	by necom830.hpcl.titech.ac.jp with SMTP; 22 Aug 2007 00:06:23 -0000
Message-ID: <46CB7C58.2030102@necom830.hpcl.titech.ac.jp>
Date: Wed, 22 Aug 2007 08:59:20 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP;
	rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: ja, en
MIME-Version: 1.0
To: shane_kerr@isc.org
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
References: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com>	<7ECEF9368E169544B43882BC98EB5D92032DA840@SVR-ALH-EXC-02.mgc.mentorg.com>	<m2zm0ywj2a.wl%jinmei@isl.rdc.toshiba.co.jp>	<20070813161026.GA4846@isc.org>	<E2E6A987-046A-44D9-923F-F17F95AFFDD2@apple.com>
	<46CADB91.6050504@isc.org>
In-Reply-To: <46CADB91.6050504@isc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: dhcwg@ietf.org, IETF IPv6 Mailing List <ipv6@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

Shane Kerr wrote:

> I know there's a lot of anti-DHCP sentiment, especially in the IPv6
> crowd. I think it is misplaced; DHCP is at worst a necessary evil, and
> at best an elegant solution to the problem space where it sits.

Right.

The problem is that so called "stateless autoconfiguration" has never
been a well defined concept and is no better than DHCP.

Problem space of ND is not well defined, either, which causes a lot
of troubles.

For example, timing constraints of RFC2462 are often annoying.

As a result, RFC3775 denies RFC2462 that:

   o  MinRtrAdvInterval 0.03 seconds

   o  MaxRtrAdvInterval 0.07 seconds

   RFC 2462 [13] specifies that in normal processing for Duplicate
   Address Detection, the node SHOULD delay sending the initial Neighbor
   Solicitation message by a random delay between 0 and
   MAX_RTR_SOLICITATION_DELAY.  Since delaying DAD can result in
   significant delays in configuring a new care-of address when the
   Mobile Node moves to a new link, the Mobile Node preferably SHOULD
   NOT delay DAD when configuring a new care-of address.

which is an evidence that problem space of ND excluded mobile
environment.

Like that, it is natural that DHCP people think DAD annoying.

							Masataka Ohta


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



From dhcwg-bounces@ietf.org Thu Aug 23 08:43:20 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IOC0A-000734-8Y; Thu, 23 Aug 2007 08:41:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IOC09-00072w-1Y
	for dhcwg@ietf.org; Thu, 23 Aug 2007 08:41:29 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IOC08-0004aM-Gm
	for dhcwg@ietf.org; Thu, 23 Aug 2007 08:41:29 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 23 Aug 2007 08:41:28 -0400
X-IronPort-AV: i="4.19,300,1183348800"; 
	d="scan'208"; a="68833558:sNHT62849094"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7NCfSGt021503; 
	Thu, 23 Aug 2007 08:41:28 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7NCf0G3027293; 
	Thu, 23 Aug 2007 12:41:28 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Aug 2007 08:41:26 -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] lifetime of 'peer-address'
Date: Thu, 23 Aug 2007 08:41:25 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB2104D4BAE8@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <20070821200931.GE16213@isc.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] lifetime of 'peer-address'
Thread-Index: AcfkL3m/qHUQfS14R3CpAGk6toBMQwBUmteg
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "David W. Hankins" <David_Hankins@isc.org>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 23 Aug 2007 12:41:26.0680 (UTC)
	FILETIME=[EBBBA180:01C7E582]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2380; t=1187872888;
	x=1188736888; c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=volz@cisco.com;
	z=From:=20=22Bernie=20Volz=20\(volz\)=22=20<volz@cisco.com>
	|Subject:=20RE=3A=20[dhcwg]=20lifetime=20of=20'peer-address'
	|Sender:=20
	|To:=20=22David=20W.=20Hankins=22=20<David_Hankins@isc.org>,
	=20<dhcwg@iet f.org>;
	bh=w1jNIyKQR29lcphlE9oIhVyJay3i5M9fY8Tku5fc9rM=;
	b=XgyVn7+86CQaicwru4j0emcLOy8SolKLEkErfgkiT6wI4I5DU4PuxSMR3xDv/EzCdfwY0Eej
	PqkgiyNI2kRTTmAYxKijaPGFhTBilOGmiz5Z+ddvMgATSWFS8u5rqTm5;
Authentication-Results: rtp-dkim-1; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim1001 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

There is no contract about the link-local address, but in general why
would the client ever change that? It isn't like this address has
privacy issues (or put another way, there's no need to protect it as the
mac address is already available to others on the link).

There are actually applications where using this might come in handy.
For example, a Reconfigure message when the client has no "usable"
global address (perhaps because the global address is not reachable
directly from the DHCP server). While there's no disagreement that for a
Reconfigure a global address is better to be used, there's no reason to
prohibit relayed Reconfigure messages.

And, for Reconfigure messages, the Reconfigure Key Auth. Protocol should
prevent issues if the client has changed its link-local and a different
client is now using that link-local address.

- Bernie

-----Original Message-----
From: David W. Hankins [mailto:David_Hankins@isc.org]=20
Sent: Tuesday, August 21, 2007 4:10 PM
To: dhcwg@ietf.org
Subject: [dhcwg] lifetime of 'peer-address'

I've been making an assumption, an unfounded one, based entirely upon
a lack of indication contrarywise, that the 'peer-address' field or
similarly where no relay is present the source IPv6 address of a
DHCPv6 packet is temporary state.

That is, "this is the address to send replies to this transaction" at
most and never "this is a permanent (probably link local) address you
can use now or at any time in the future to reach this endpoint."

This basic understanding was questioned on a recent discussion on
ipv6@ietf.org, and I wondered what other opinions there were.


I tend to think that any expectation that a DHCPv6 client "will
always" Renew or Rebind or even Solicit when any link local addresses
have changed or disappeared is naive, so I don't think this
information can realistically be counted on.  I don't think the
client's source address is a contract for longer than it takes to
reply to the query (same of the server's or relay agent's source
addresses).

--=20
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil?	 https://secure.isc.org/store/t-shirt/
--=20
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins

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



From dhcwg-bounces@ietf.org Thu Aug 23 13:37:53 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IOGb2-0006hc-Lo; Thu, 23 Aug 2007 13:35:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IOGb2-0006hW-0Y
	for dhcwg@ietf.org; Thu, 23 Aug 2007 13:35:52 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IOGb1-0004Vl-76
	for dhcwg@ietf.org; Thu, 23 Aug 2007 13:35:51 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 360C95A6E5; Thu, 23 Aug 2007 10:35:50 -0700 (PDT)
Date: Thu, 23 Aug 2007 10:35:50 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] lifetime of 'peer-address'
Message-ID: <20070823173550.GB10173@isc.org>
References: <20070821200931.GE16213@isc.org>
	<8E296595B6471A4689555D5D725EBB2104D4BAE8@xmb-rtp-20a.amer.cisco.com>
Mime-Version: 1.0
In-Reply-To: <8E296595B6471A4689555D5D725EBB2104D4BAE8@xmb-rtp-20a.amer.cisco.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
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="===============1084117354=="
Errors-To: dhcwg-bounces@ietf.org


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


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

On Thu, Aug 23, 2007 at 08:41:25AM -0400, Bernie Volz (volz) wrote:
> There is no contract about the link-local address, but in general why
> would the client ever change that? It isn't like this address has
> privacy issues (or put another way, there's no need to protect it as the
> mac address is already available to others on the link).

Because of the DUID and IAID abstractions, it's entirely possible
that a client might change network devices (and thus hardware
addresses, and therefore link local addresses) without changing its
DUID or IAID.

So it's encouraged that if a system were to be given a new network
device (and therefore a new link-local), that it may still Confirm for
the same IAID,DUID pair with the old addresses (and possibly even
sessions) intact.

Since such a Confirm may reach one DHCPv6 server, but not another,
and either DHCPv6 server may answer, it's entirely possible that
the link local address would change without some servers being the
wiser.  Not to mention that I think many servers will not update
recorded information about clients on processing Confirms (I
certainly hope we never have to).

So in an infinite universe, there's at least one reason it may be so.

I think it's also possible, if highly improbable, that a client
may lose its addresses to another client on the network, normally
such as over a network disconnect, or abnormally such as when a
network partition is healed.

> There are actually applications where using this might come in handy.
> For example, a Reconfigure message when the client has no "usable"
> global address (perhaps because the global address is not reachable
> directly from the DHCP server). While there's no disagreement that for a
> Reconfigure a global address is better to be used, there's no reason to
> prohibit relayed Reconfigure messages.
>=20
> And, for Reconfigure messages, the Reconfigure Key Auth. Protocol should
> prevent issues if the client has changed its link-local and a different
> client is now using that link-local address.

I agree that DHCPv6 Reconfigure is a fine place to use the link local
address and RFC3315 even gives guidance that the server could
synthesize a Relay-Reply using the client's previously known
peer-address field...I assume it can synthesize a full relay chain
based upon the most recent.  This also is dynamic information - the
server has no way of knowing whether or not the relay chain has been
changed, entire devices could be removed or replaced, resulting also
in changes in peer-address fields across the chain.

First, I think of this activity as being administrator-initiated
(directly or indirectly).  In many cases, a 'Reconfigure' tool will
probably let an operator specify the target address.  The operator can
and should be able to specify any address he knows - or thinks he
knows.  In the case of network administration systems that abstract
this - they should work well in whatever custom environments they're
tailored for.

But more importantly, Reconfigure is an operation that is accepted
to fail.  You don't need to rely on it to work - the client will
Renew eventually.  It's just an optimization.


I think it is problematic to rely upon the client's link local
address for any persistent operation where reliability is a
requirement.

For that sort of thing you really need a contract with the client
that they will continue to use an address for some length of time,
such as is implicit (and in the client's best interest) with an
addressed assigned via DHCPv6 IA_NA.

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

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

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

iD8DBQFGzcV2cXeLeWu2vmoRAiWfAKCejRnhM8m8zm3T/gTSN9tVlXvqQACgrq1L
dq/Ddp4Z6UKDsh+8P7fe4xc=
=MGoB
-----END PGP SIGNATURE-----

--/WwmFnJnmDyWGHa4--


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

--===============1084117354==--




From dhcwg-bounces@ietf.org Thu Aug 23 14:52:54 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IOHlo-0008LQ-Te; Thu, 23 Aug 2007 14:51:04 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IOHln-0008LJ-LH
	for dhcwg@ietf.org; Thu, 23 Aug 2007 14:51:03 -0400
Received: from intermail.se.dataphone.net ([212.37.1.50])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IOHln-00088S-8P
	for dhcwg@ietf.org; Thu, 23 Aug 2007 14:51:03 -0400
Received: from [213.115.152.226] (account budm@weird-solutions.com HELO
	offset.weird.se)
	by intermail.se.dataphone.net (CommuniGate Pro SMTP 4.2)
	with ESMTP id 46350272; Thu, 23 Aug 2007 20:51:00 +0200
From: Bud Millwood <budm@weird-solutions.com>
Organization: Weird Solutions, Inc.
To: dhcwg@ietf.org
Subject: Re: [dhcwg] lifetime of 'peer-address'
Date: Thu, 23 Aug 2007 20:15:05 +0200
User-Agent: KMail/1.8
References: <20070821200931.GE16213@isc.org>
	<8E296595B6471A4689555D5D725EBB2104D4BAE8@xmb-rtp-20a.amer.cisco.com>
	<20070823173550.GB10173@isc.org>
In-Reply-To: <20070823173550.GB10173@isc.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200708232015.05121.budm@weird-solutions.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bud Millwood <budm@weird-solutions.com>
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Thursday 23 August 2007 19:35, David W. Hankins wrote:
> On Thu, Aug 23, 2007 at 08:41:25AM -0400, Bernie Volz (volz) wrote:
> > There is no contract about the link-local address, but in general why
> > would the client ever change that? It isn't like this address has
> > privacy issues (or put another way, there's no need to protect it as the
> > mac address is already available to others on the link).
>
> Because of the DUID and IAID abstractions, it's entirely possible
> that a client might change network devices (and thus hardware
> addresses, and therefore link local addresses) without changing its
> DUID or IAID.
>
> So it's encouraged that if a system were to be given a new network
> device (and therefore a new link-local), that it may still Confirm for
> the same IAID,DUID pair with the old addresses (and possibly even
> sessions) intact.

You're basically saying that a server should not use a previously recorded 
link-address during a client-initiated transaction, right? Under what 
circumstances *would* a server consider using a previously recorded link 
address for a client-initiated transaction?

- Bud

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



From dhcwg-bounces@ietf.org Thu Aug 23 16:35:38 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IOJNG-0002DF-Pk; Thu, 23 Aug 2007 16:33:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IOJNF-0002D8-FU
	for dhcwg@ietf.org; Thu, 23 Aug 2007 16:33:49 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IOJNF-0001rm-2w
	for dhcwg@ietf.org; Thu, 23 Aug 2007 16:33:49 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 626715A6E5; Thu, 23 Aug 2007 13:33:48 -0700 (PDT)
Date: Thu, 23 Aug 2007 13:33:48 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] lifetime of 'peer-address'
Message-ID: <20070823203348.GL10173@isc.org>
References: <20070821200931.GE16213@isc.org>
	<8E296595B6471A4689555D5D725EBB2104D4BAE8@xmb-rtp-20a.amer.cisco.com>
	<20070823173550.GB10173@isc.org>
	<200708232015.05121.budm@weird-solutions.com>
Mime-Version: 1.0
In-Reply-To: <200708232015.05121.budm@weird-solutions.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1006510974=="
Errors-To: dhcwg-bounces@ietf.org


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


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

On Thu, Aug 23, 2007 at 08:15:05PM +0200, Bud Millwood wrote:
> You're basically saying that a server should not use a previously recorde=
d=20
> link-address during a client-initiated transaction, right? Under what=20

No...for uses totally external to DHCPv6 actually.  Any use in which
reliability beyond the current transaction is required.

The stipulation on ipv6@ietf.org was that "a DHCPv6 server 'knows'
the link-local addresses of all clients, because it can record the
'peer-address' field".  In context, they meant that this information
was reliable for a purpose that really couldn't be allowed to fail.

Where getting it wrong is substantially more expensive than failing a
Reconfigure; someone loses or can't get net.

I can find the mail in the archive if you like.  I'm really curious
if I'm missing something; the person's clarification was that the
server is always (reliably) updated in any event a link-local address
changes.

I haven't read that anywhere, so I'm wondering how we get from here
to there.

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

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

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

iD8DBQFGze8scXeLeWu2vmoRAly/AJ90wU57DnB6zy+ZKAPewx8mkCeXMwCgurR4
V1gTI/AN3AOF9KRFwzYSw9E=
=2Sjz
-----END PGP SIGNATURE-----

--QxN5xOWGsmh5a4wb--


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

--===============1006510974==--




From dhcwg-bounces@ietf.org Thu Aug 23 16:54:53 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IOJfu-0007f8-Oy; Thu, 23 Aug 2007 16:53:06 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IOJft-0007e7-31
	for dhcwg@ietf.org; Thu, 23 Aug 2007 16:53:05 -0400
Received: from intermail.se.dataphone.net ([212.37.1.50])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IOJfs-0003N2-LB
	for dhcwg@ietf.org; Thu, 23 Aug 2007 16:53:05 -0400
Received: from [213.115.152.226] (account budm@weird-solutions.com HELO
	offset.weird.se)
	by intermail.se.dataphone.net (CommuniGate Pro SMTP 4.2)
	with ESMTP id 46354226; Thu, 23 Aug 2007 22:53:03 +0200
From: Bud Millwood <budm@weird-solutions.com>
Organization: Weird Solutions, Inc.
To: dhcwg@ietf.org
Subject: Re: [dhcwg] lifetime of 'peer-address'
Date: Thu, 23 Aug 2007 22:17:06 +0200
User-Agent: KMail/1.8
References: <20070821200931.GE16213@isc.org>
	<200708232015.05121.budm@weird-solutions.com>
	<20070823203348.GL10173@isc.org>
In-Reply-To: <20070823203348.GL10173@isc.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200708232217.07065.budm@weird-solutions.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bud Millwood <budm@weird-solutions.com>
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Thursday 23 August 2007 22:33, David W. Hankins wrote:
> On Thu, Aug 23, 2007 at 08:15:05PM +0200, Bud Millwood wrote:
> > You're basically saying that a server should not use a previously
> > recorded link-address during a client-initiated transaction, right? Under
> > what
>
> No...for uses totally external to DHCPv6 actually.  Any use in which
> reliability beyond the current transaction is required.
>
> The stipulation on ipv6@ietf.org was that "a DHCPv6 server 'knows'
> the link-local addresses of all clients, because it can record the
> 'peer-address' field".  In context, they meant that this information
> was reliable for a purpose that really couldn't be allowed to fail.
>
> Where getting it wrong is substantially more expensive than failing a
> Reconfigure; someone loses or can't get net.
>
> I can find the mail in the archive if you like.  I'm really curious
> if I'm missing something; the person's clarification was that the
> server is always (reliably) updated in any event a link-local address
> changes.
>
> I haven't read that anywhere, so I'm wondering how we get from here
> to there.

Aha, I see. I don't recall anything stating that the server *must* record the 
link-local address. And as far as I know there's no standard way to query a 
DHCPv6 server for a client's link-local address. But since the DHCP server 
seems the logical place to track them for a given DUID/IAID, why not store it 
and update it with CONFIRMS? If this information is needed by another 
protocol we could, for example, extend lease-query to support asking for this 
info.

- Bud

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



From dhcwg-bounces@ietf.org Thu Aug 23 17:21:35 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IOK5m-0004e1-Bm; Thu, 23 Aug 2007 17:19:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IOK5l-0004dm-0U
	for dhcwg@ietf.org; Thu, 23 Aug 2007 17:19:49 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IOK5k-0003hF-JP
	for dhcwg@ietf.org; Thu, 23 Aug 2007 17:19:48 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 38C115A6E5; Thu, 23 Aug 2007 14:19:47 -0700 (PDT)
Date: Thu, 23 Aug 2007 14:19:47 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] lifetime of 'peer-address'
Message-ID: <20070823211947.GN10173@isc.org>
References: <20070821200931.GE16213@isc.org>
	<200708232015.05121.budm@weird-solutions.com>
	<20070823203348.GL10173@isc.org>
	<200708232217.07065.budm@weird-solutions.com>
Mime-Version: 1.0
In-Reply-To: <200708232217.07065.budm@weird-solutions.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
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="===============1933959920=="
Errors-To: dhcwg-bounces@ietf.org


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


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

On Thu, Aug 23, 2007 at 10:17:06PM +0200, Bud Millwood wrote:
> Aha, I see. I don't recall anything stating that the server *must* record=
 the=20
> link-local address. And as far as I know there's no standard way to query=
 a=20
> DHCPv6 server for a client's link-local address. But since the DHCP serve=
r=20
> seems the logical place to track them for a given DUID/IAID, why not stor=
e it=20
> and update it with CONFIRMS? If this information is needed by another=20
> protocol we could, for example, extend lease-query to support asking for =
this=20
> info.

You sound certain that DHCPv6 servers are updated reliably...why?

This is 3 opinions for and one against, so I must be missing
something.

On the continuing subject of Confirm; a different server may answer
the Confirm without all servers seeing it, so if there's more than
one server there could be differing opinions of the client's address.
If the Confirm times out entirely (CNF_MAX_RD is 10 seconds), the
client may just continue to use their old addresses - and won't emit
more messages until t1.  So no server may have the up-to-date address.

That's even if you update your database on Confirms, which rather
ruins its lightweightness (a quality I rather like since operators
can manipulate t1, but they can't control how often boxes reboot).

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

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

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

iD8DBQFGzfnzcXeLeWu2vmoRAoY6AKCP1rKgqxmblC8vzEU7daMslS4WYQCgkCcQ
Jwrs5/D1YUxP3z2Jc1S8+uk=
=jD1O
-----END PGP SIGNATURE-----

--Ms5iOKSBOB9YS8zC--


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

--===============1933959920==--




From dhcwg-bounces@ietf.org Thu Aug 23 18:20:46 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IOL10-0007VN-Jv; Thu, 23 Aug 2007 18:18:58 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IOL0y-0007V9-WE
	for dhcwg@ietf.org; Thu, 23 Aug 2007 18:18:57 -0400
Received: from intermail.se.dataphone.net ([212.37.1.50])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IOL0y-0006pc-Hf
	for dhcwg@ietf.org; Thu, 23 Aug 2007 18:18:56 -0400
Received: from [213.115.152.226] (account budm@weird-solutions.com HELO
	offset.weird.se)
	by intermail.se.dataphone.net (CommuniGate Pro SMTP 4.2)
	with ESMTP id 46356374 for dhcwg@ietf.org;
	Fri, 24 Aug 2007 00:18:55 +0200
From: Bud Millwood <budm@weird-solutions.com>
Organization: Weird Solutions, Inc.
To: dhcwg@ietf.org
Subject: Re: [dhcwg] lifetime of 'peer-address'
Date: Thu, 23 Aug 2007 23:42:57 +0200
User-Agent: KMail/1.8
References: <20070821200931.GE16213@isc.org>
	<200708232217.07065.budm@weird-solutions.com>
	<20070823211947.GN10173@isc.org>
In-Reply-To: <20070823211947.GN10173@isc.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200708232342.57972.budm@weird-solutions.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bud Millwood <budm@weird-solutions.com>
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Thursday 23 August 2007 23:19, David W. Hankins wrote:
> On Thu, Aug 23, 2007 at 10:17:06PM +0200, Bud Millwood wrote:
> > Aha, I see. I don't recall anything stating that the server *must* reco=
rd
> > the link-local address. And as far as I know there's no standard way to
> > query a DHCPv6 server for a client's link-local address. But since the
> > DHCP server seems the logical place to track them for a given DUID/IAID,
> > why not store it and update it with CONFIRMS? If this information is
> > needed by another protocol we could, for example, extend lease-query to
> > support asking for this info.
>
> You sound certain that DHCPv6 servers are updated reliably...why?

No, I=CD=84'm just thinking out loud. Your argument against is a valid=20
consideration, because it's true that multiple DHCP servers may have=20
differing data for a client's LL address, and all servers may have stale=20
data.

I see no way to guarantee that even one DHCP server has a LL address for a=
=20
client that is *definitely* known to be valid. Having said that, it may be=
=20
highly likely that it is valid. Is that useful for whoever needs the info?

Is there a better way to identify a client as being the same machine after =
it=20
changes its LL address? That's exactly what DUID gives you.

So unless there's a mechanism that mimics DUID that I'm not aware of, I gue=
ss=20
the conclusion is that you can't know for sure, but the DHCP server can giv=
e=20
you a reasonable guess. <glad to be of service folks, we'll be here all=20
week> :)

=2D Bud

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



From dhcwg-bounces@ietf.org Thu Aug 23 18:37:24 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IOLH6-0007AL-IH; Thu, 23 Aug 2007 18:35:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IOLH4-0007AE-VF
	for dhcwg@ietf.org; Thu, 23 Aug 2007 18:35:34 -0400
Received: from intermail.se.dataphone.net ([212.37.1.50])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IOLH3-00068s-Gn
	for dhcwg@ietf.org; Thu, 23 Aug 2007 18:35:34 -0400
Received: from [213.115.152.226] (account budm@weird-solutions.com HELO
	offset.weird.se)
	by intermail.se.dataphone.net (CommuniGate Pro SMTP 4.2)
	with ESMTP id 46356831 for dhcwg@ietf.org;
	Fri, 24 Aug 2007 00:35:31 +0200
From: Bud Millwood <budm@weird-solutions.com>
Organization: Weird Solutions, Inc.
To: dhcwg@ietf.org
Date: Thu, 23 Aug 2007 23:59:32 +0200
User-Agent: KMail/1.8
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200708232359.32262.budm@weird-solutions.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Subject: [dhcwg] Vendor-specific options
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bud Millwood <budm@weird-solutions.com>
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

In DHCPv4, the vendor options contained in option 43 were interpreted 
according to the free-form text of option 60. Vendors were free to put 
anything in option 60, and many of them chose different data for different 
models of their equipment.

In DHCPv6 the vendor options are interpreted according to the vendor_id field, 
but vendors are *not* free to put anything in there that they want - just 
their assigned id.

How are vendors expected to define different sets of options for different 
equipment? It seems to me that the possibilities are:

1. Vendors don't have different options, they use the 16-bit tag space to 
define all options for all devices. Seems like a bad idea for a couple of 
reasons, one being you can't easily narrow down and present to the user a set 
of options for a particular piece of equipment.

2. Vendors start defining their own free-form text fields inside the VSO, and 
we end up looking awfully similar to DHCPv4.

3. Vendors use 'vendor-sub-identifiers', hopefully modelled after the VSO.

It seems the VSO in DHCPv6 tried to solve the problem of allowing free-form 
vendor class, but just deferred the problem to parsing within the VSO - at 
least in the case where a vendor had multiple option 60 values for different 
sets of vendor-specific options (in DHCPv4).

Are we going to see all sorts of crazy schemes in the DHCPv6 VSO to denote 
different option spaces?

Are any vendors currently partitioning their VSO suboptions?

Could/should we recommend that vendors use the VSO format inside the VSO if 
they want partitioned option spaces?

- Bud

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



From dhcwg-bounces@ietf.org Thu Aug 23 19:08:47 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IOLlR-0003yb-Te; Thu, 23 Aug 2007 19:06:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IOLlQ-0003xG-Mk
	for dhcwg@ietf.org; Thu, 23 Aug 2007 19:06:56 -0400
Received: from paoakoavas10.cable.comcast.com ([208.17.35.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IOLlQ-0007Si-8N
	for dhcwg@ietf.org; Thu, 23 Aug 2007 19:06:56 -0400
Received: from ([10.195.246.152])
	by paoakoavas10.cable.comcast.com with ESMTP  id KP-TDCH7.36136560;
	Thu, 23 Aug 2007 19:06:39 -0400
Received: from NJCHLEXCMB01.cable.comcast.com ([172.24.2.44]) by
	NJMDCEXCRLY01.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 23 Aug 2007 19:06:39 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] Vendor-specific options
Date: Thu, 23 Aug 2007 19:06:38 -0400
Message-ID: <997BC128AE961E4A8B880CD7442D9480174EA5@NJCHLEXCMB01.cable.comcast.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Vendor-specific options
Thread-Index: Acfl1fkyq+S251icRwGxrknO39O0AQAA2IGl
References: <200708232359.32262.budm@weird-solutions.com>
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: "Bud Millwood" <budm@weird-solutions.com>,
	<dhcwg@ietf.org>
X-OriginalArrivalTime: 23 Aug 2007 23:06:39.0483 (UTC)
	FILETIME=[431B1CB0:01C7E5DA]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Hello Bud,

I am not sure if I am following all of the points below.  I will try to =
offer some comments, however.

Vendor class in particular in DHCPv6 includes an enterprise-id that is =
used to differentiate the values within.  Other options can be defined  =
in the vendor option space (17) which also includes an enterprise-id.  =
An example of where this has been used is in DOCSIS 3.0.

Is this what you were inquiring about?

HTH,

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



-----Original Message-----
From: Bud Millwood [mailto:budm@weird-solutions.com]
Sent: Thu 8/23/2007 5:59 PM
To: dhcwg@ietf.org
Subject: [dhcwg] Vendor-specific options
=20
In DHCPv4, the vendor options contained in option 43 were interpreted=20
according to the free-form text of option 60. Vendors were free to put=20
anything in option 60, and many of them chose different data for =
different=20
models of their equipment.

In DHCPv6 the vendor options are interpreted according to the vendor_id =
field,=20
but vendors are *not* free to put anything in there that they want - =
just=20
their assigned id.

How are vendors expected to define different sets of options for =
different=20
equipment? It seems to me that the possibilities are:

1. Vendors don't have different options, they use the 16-bit tag space =
to=20
define all options for all devices. Seems like a bad idea for a couple =
of=20
reasons, one being you can't easily narrow down and present to the user =
a set=20
of options for a particular piece of equipment.

2. Vendors start defining their own free-form text fields inside the =
VSO, and=20
we end up looking awfully similar to DHCPv4.

3. Vendors use 'vendor-sub-identifiers', hopefully modelled after the =
VSO.

It seems the VSO in DHCPv6 tried to solve the problem of allowing =
free-form=20
vendor class, but just deferred the problem to parsing within the VSO - =
at=20
least in the case where a vendor had multiple option 60 values for =
different=20
sets of vendor-specific options (in DHCPv4).

Are we going to see all sorts of crazy schemes in the DHCPv6 VSO to =
denote=20
different option spaces?

Are any vendors currently partitioning their VSO suboptions?

Could/should we recommend that vendors use the VSO format inside the VSO =
if=20
they want partitioned option spaces?

- Bud

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


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



From dhcwg-bounces@ietf.org Thu Aug 23 19:19:49 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IOLwC-0000Qx-Hz; Thu, 23 Aug 2007 19:18:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IOLwA-0000Qo-M0
	for dhcwg@ietf.org; Thu, 23 Aug 2007 19:18:02 -0400
Received: from goliath.isc.org ([2001:4f8:3:bb::72])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IOLwA-0007jg-3f
	for dhcwg@ietf.org; Thu, 23 Aug 2007 19:18:02 -0400
Received: by goliath.isc.org (Postfix, from userid 10200)
	id 9AFBD5A6E5; Thu, 23 Aug 2007 16:18:01 -0700 (PDT)
Date: Thu, 23 Aug 2007 16:18:01 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Vendor-specific options
Message-ID: <20070823231801.GO10173@isc.org>
References: <200708232359.32262.budm@weird-solutions.com>
Mime-Version: 1.0
In-Reply-To: <200708232359.32262.budm@weird-solutions.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: -0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1977127794=="
Errors-To: dhcwg-bounces@ietf.org


--===============1977127794==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="75WsOQSofUOhcSOp"
Content-Disposition: inline


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

On Thu, Aug 23, 2007 at 11:59:32PM +0200, Bud Millwood wrote:
> 1. Vendors don't have different options, they use the 16-bit tag space to=
=20
> define all options for all devices. Seems like a bad idea for a couple of=
=20
> reasons, one being you can't easily narrow down and present to the user a=
 set=20
> of options for a particular piece of equipment.

This is my understanding.

I think that DOCSIS, concerned I think about having a large number of
options in one 16-bit space, has elected to use a sub-parameter-
request-list option.  I might be thinking of something else, but I
think DOCSIS 3 specified one.

Where software supports it - the operator configures all the values
for all the different options, and they get delivered automatically
to the clients that want them.

	option vendor.foo ...;
	option vendor.bar ...;
	option vendor.baz ...;

Where software doesn't support it - the operator configures "classes"
that match individual vendor class options, and configure values
relevant to those classes of clients in one place.  The output packet
contains only that which is relevant to the class of client in
question.

	class "thingits" {
		match if vivco.example =3D "thingit";
		option vendor.foo ...;
	}
	class "whatsis" {
		match if vivco.example =3D "whatsis";
		option vendor.bar ...;
	}
	class "dongles" {
		match if vivco.example =3D "dongles";
		option vendor.baz ...;
	}

(where vivco is 'vendor identified vendor class option'...I can't
remember which is which anymore...is it "vcio" for DHCPv6?)


The worst case is that the clients get big packets.

I don't think there's a danger that vendors are going to have multiple
option spaces with one enterprise-ID...but if someone says they might,
we should listen.

--=20
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil?	 https://secure.isc.org/store/t-shirt/
--=20
David W. Hankins	"If you don't do it right the first time,
Software Engineer		     you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins

--75WsOQSofUOhcSOp
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFGzhWpcXeLeWu2vmoRAobCAJ43COsPyDL+/5E+qj9ZOjBQK0iWmACgiNd4
JMYXlt51LYhD3fXbxYSqnR8=
=8n7o
-----END PGP SIGNATURE-----

--75WsOQSofUOhcSOp--


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

--===============1977127794==--




From dhcwg-bounces@ietf.org Thu Aug 23 19:36:15 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IOMC3-0003Yb-35; Thu, 23 Aug 2007 19:34:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IOMC2-0003YW-3H
	for dhcwg@ietf.org; Thu, 23 Aug 2007 19:34:26 -0400
Received: from pacdcimo01.cable.comcast.com ([24.40.8.145])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IOMC1-0000zq-KW
	for dhcwg@ietf.org; Thu, 23 Aug 2007 19:34:26 -0400
Received: from ([10.52.116.30])
	by pacdcimo01.cable.comcast.com with ESMTP  id KP-BXT38.6987187;
	Thu, 23 Aug 2007 19:33:57 -0400
Received: from NJCHLEXCMB01.cable.comcast.com ([172.24.2.44]) by
	PAOAKEXCSMTP01.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 23 Aug 2007 19:33:57 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] Vendor-specific options
Date: Thu, 23 Aug 2007 19:33:57 -0400
Message-ID: <997BC128AE961E4A8B880CD7442D9480174EA6@NJCHLEXCMB01.cable.comcast.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] Vendor-specific options
Thread-Index: Acfl2+vTkOYMljyNTi2BP25ywECsHgAAJgjR
References: <200708232359.32262.budm@weird-solutions.com>
	<20070823231801.GO10173@isc.org>
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
To: "David W. Hankins" <David_Hankins@isc.org>,
	<dhcwg@ietf.org>
X-OriginalArrivalTime: 23 Aug 2007 23:33:57.0269 (UTC)
	FILETIME=[134D6C50:01C7E5DE]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Hello David,

You are correct we specified an ORO as part of DOCSIS 3.0.

It would be interesting to hear more about multi-enterprise-id =
scenarios.  While it seems valid (I think) I imagine it could tricky to =
organize.

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



-----Original Message-----
From: David W. Hankins [mailto:David_Hankins@isc.org]
Sent: Thu 8/23/2007 7:18 PM
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Vendor-specific options
=20
On Thu, Aug 23, 2007 at 11:59:32PM +0200, Bud Millwood wrote:
> 1. Vendors don't have different options, they use the 16-bit tag space =
to=20
> define all options for all devices. Seems like a bad idea for a couple =
of=20
> reasons, one being you can't easily narrow down and present to the =
user a set=20
> of options for a particular piece of equipment.

This is my understanding.

I think that DOCSIS, concerned I think about having a large number of
options in one 16-bit space, has elected to use a sub-parameter-
request-list option.  I might be thinking of something else, but I
think DOCSIS 3 specified one.

Where software supports it - the operator configures all the values
for all the different options, and they get delivered automatically
to the clients that want them.

 option vendor.foo ...;
 option vendor.bar ...;
 option vendor.baz ...;

Where software doesn't support it - the operator configures "classes"
that match individual vendor class options, and configure values
relevant to those classes of clients in one place.  The output packet
contains only that which is relevant to the class of client in
question.

 class "thingits" {
  match if vivco.example =3D "thingit";
  option vendor.foo ...;
 }
 class "whatsis" {
  match if vivco.example =3D "whatsis";
  option vendor.bar ...;
 }
 class "dongles" {
  match if vivco.example =3D "dongles";
  option vendor.baz ...;
 }

(where vivco is 'vendor identified vendor class option'...I can't
remember which is which anymore...is it "vcio" for DHCPv6?)


The worst case is that the clients get big packets.

I don't think there's a danger that vendors are going to have multiple
option spaces with one enterprise-ID...but if someone says they might,
we should listen.

--=20
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil?  https://secure.isc.org/store/t-shirt/
--=20
David W. Hankins "If you don't do it right the first time,
Software Engineer       you'll just have to do it again."
Internet Systems Consortium, Inc.  -- Jack T. Hankins


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



From dhcwg-bounces@ietf.org Thu Aug 23 20:22:42 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IOMv2-0005G1-RW; Thu, 23 Aug 2007 20:20:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IOMv2-0005Fw-1w
	for dhcwg@ietf.org; Thu, 23 Aug 2007 20:20:56 -0400
Received: from intermail.se.dataphone.net ([212.37.1.50])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IOMv1-000229-HG
	for dhcwg@ietf.org; Thu, 23 Aug 2007 20:20:55 -0400
Received: from [213.115.152.226] (account budm@weird-solutions.com HELO
	offset.weird.se)
	by intermail.se.dataphone.net (CommuniGate Pro SMTP 4.2)
	with ESMTP id 46359641 for dhcwg@ietf.org;
	Fri, 24 Aug 2007 02:20:53 +0200
From: Bud Millwood <budm@weird-solutions.com>
Organization: Weird Solutions, Inc.
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Vendor-specific options
Date: Fri, 24 Aug 2007 01:44:52 +0200
User-Agent: KMail/1.8
References: <200708232359.32262.budm@weird-solutions.com>
	<20070823231801.GO10173@isc.org>
In-Reply-To: <20070823231801.GO10173@isc.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200708240144.52825.budm@weird-solutions.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Bud Millwood <budm@weird-solutions.com>
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Friday 24 August 2007 01:18, David W. Hankins wrote:
> On Thu, Aug 23, 2007 at 11:59:32PM +0200, Bud Millwood wrote:
> > 1. Vendors don't have different options, they use the 16-bit tag space =
to
> > define all options for all devices. Seems like a bad idea for a couple =
of
> > reasons, one being you can't easily narrow down and present to the user=
 a
> > set of options for a particular piece of equipment.
>
> This is my understanding.
>
> I think that DOCSIS, concerned I think about having a large number of
> options in one 16-bit space, has elected to use a sub-parameter-
> request-list option.  I might be thinking of something else, but I
> think DOCSIS 3 specified one.

Nope, you're right, I just checked it. There's an ORO in the VSO options fo=
r=20
DOCSIS 3.0.

> Where software supports it - the operator configures all the values
> for all the different options, and they get delivered automatically
> to the clients that want them.
>
> 	option vendor.foo ...;
> 	option vendor.bar ...;
> 	option vendor.baz ...;

OK, I guess it's not so bad to define all options in the one 16-bit tagspac=
e.=20
=46rom the standpoint of being able to parse inbound VSO options, it's a=20
no-brainer. (Easier than vendor sub-identifiers)

I think maybe what I expect is just to be able to group sets of vendor=20
suboptions by some class name so the operator can easily locate suboptions=
=20
specific to the device he wants to consider. Should be easy enough to just=
=20
allow a class name in my option definitions.

BTW, if the vendor hasn't defined a vendor-specific ORO, I guess you'd have=
 to=20
support the method described below.

> Where software doesn't support it - the operator configures "classes"
> that match individual vendor class options, and configure values
> relevant to those classes of clients in one place.  The output packet
> contains only that which is relevant to the class of client in
> question.
>
> 	class "thingits" {
> 		match if vivco.example =3D "thingit";
> 		option vendor.foo ...;
> 	}
> 	class "whatsis" {
> 		match if vivco.example =3D "whatsis";
> 		option vendor.bar ...;
> 	}
> 	class "dongles" {
> 		match if vivco.example =3D "dongles";
> 		option vendor.baz ...;
> 	}
>
> (where vivco is 'vendor identified vendor class option'...I can't
> remember which is which anymore...is it "vcio" for DHCPv6?)

IOW in this scenario you would check option 16/vendor class data and match =
the=20
classes against the pre-defined classes of options.

> I don't think there's a danger that vendors are going to have multiple
> option spaces with one enterprise-ID...but if someone says they might,
> we should listen.

Well then until I see one I'll leave it where it is. I'd be happy to never =
see=20
vendor sub-identifiers.

=2D Bud

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



From dhcwg-bounces@ietf.org Fri Aug 24 02:25:27 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IOSa3-00088J-Js; Fri, 24 Aug 2007 02:23:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IOSa2-00088E-4c
	for dhcwg@ietf.org; Fri, 24 Aug 2007 02:23:38 -0400
Received: from outgoing.persistent.co.in ([202.54.11.87]
	helo=bmapps.persistent.co.in)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IOSZz-0007dR-6l
	for dhcwg@ietf.org; Fri, 24 Aug 2007 02:23:38 -0400
Received: from bmapps.persistent.co.in (unknown [127.0.0.1])
	by bmapps.persistent.co.in (Symantec Mail Security) with ESMTP id
	0E62E52A354
	for <dhcwg@ietf.org>; Fri, 24 Aug 2007 11:53:34 +0530 (IST)
X-AuditID: 0a4e0006-a606abb000005838-c8-46ce79650571
Received: from mail.persistent.co.in (unknown [10.78.0.1])
	by bmapps.persistent.co.in (Symantec Mail Security) with ESMTP id
	D732D4E4002
	for <dhcwg@ietf.org>; Fri, 24 Aug 2007 11:53:33 +0530 (IST)
Received: from ps0692 (ps0692.persistent.co.in [10.88.88.239])
	by mail.persistent.co.in (MOS 3.8.4-GA)
	with ESMTP id BLJ63354 (AUTH kapil_maheshwari);
	Fri, 24 Aug 2007 11:53:33 +0530 (IST)
From: "Kapil Maheshwari" <kapil_maheshwari@persistent.co.in>
To: <dhcwg@ietf.org>
References: <E1IOLwD-0000RZ-UV@megatron.ietf.org>
Date: Fri, 24 Aug 2007 11:54:33 +0530
Message-ID: <000901c7e617$6fc24f30$ef58580a@persistent.co.in>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acfl3AAQfA3TeHP7TCOtIGytaqVNqgAO2tlQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
In-Reply-To: <E1IOLwD-0000RZ-UV@megatron.ietf.org>
X-Junkmail-Whitelist: YES (by domain whitelist at mail6.persistent.co.in)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 74c8c6a39062dbfd583931efcf641276
Subject: [dhcwg] Re: Contents of dhcwg digest...
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org



-----Original Message-----
From: dhcwg-request@ietf.org [mailto:dhcwg-request@ietf.org] 
Sent: Friday, August 24, 2007 4:48 AM
To: dhcwg@ietf.org
Subject: dhcwg Digest, Vol 40, Issue 26

Send dhcwg mailing list submissions to
	dhcwg@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
	https://www1.ietf.org/mailman/listinfo/dhcwg
or, via email, send a message with subject or body 'help' to
	dhcwg-request@ietf.org

You can reach the person managing the list at
	dhcwg-owner@ietf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcwg digest..."


Today's Topics:

   1. Re: lifetime of 'peer-address' (David W. Hankins)
   2. Re: lifetime of 'peer-address' (Bud Millwood)
   3. Re: lifetime of 'peer-address' (David W. Hankins)
   4. Re: lifetime of 'peer-address' (Bud Millwood)
   5. Re: lifetime of 'peer-address' (David W. Hankins)
   6. Re: lifetime of 'peer-address' (Bud Millwood)
   7. Vendor-specific options (Bud Millwood)
   8. RE: Vendor-specific options (Brzozowski, John)
   9. Re: Vendor-specific options (David W. Hankins)


----------------------------------------------------------------------

Message: 1
Date: Thu, 23 Aug 2007 10:35:50 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
Subject: Re: [dhcwg] lifetime of 'peer-address'
To: dhcwg@ietf.org
Message-ID: <20070823173550.GB10173@isc.org>
Content-Type: text/plain; charset=3D"us-ascii"

On Thu, Aug 23, 2007 at 08:41:25AM -0400, Bernie Volz (volz) wrote:
> There is no contract about the link-local address, but in general why
> would the client ever change that? It isn't like this address has
> privacy issues (or put another way, there's no need to protect it as the
> mac address is already available to others on the link).

Because of the DUID and IAID abstractions, it's entirely possible
that a client might change network devices (and thus hardware
addresses, and therefore link local addresses) without changing its
DUID or IAID.

So it's encouraged that if a system were to be given a new network
device (and therefore a new link-local), that it may still Confirm for
the same IAID,DUID pair with the old addresses (and possibly even
sessions) intact.

Since such a Confirm may reach one DHCPv6 server, but not another,
and either DHCPv6 server may answer, it's entirely possible that
the link local address would change without some servers being the
wiser.  Not to mention that I think many servers will not update
recorded information about clients on processing Confirms (I
certainly hope we never have to).

So in an infinite universe, there's at least one reason it may be so.

I think it's also possible, if highly improbable, that a client
may lose its addresses to another client on the network, normally
such as over a network disconnect, or abnormally such as when a
network partition is healed.

> There are actually applications where using this might come in handy.
> For example, a Reconfigure message when the client has no "usable"
> global address (perhaps because the global address is not reachable
> directly from the DHCP server). While there's no disagreement that for a
> Reconfigure a global address is better to be used, there's no reason to
> prohibit relayed Reconfigure messages.
> 
> And, for Reconfigure messages, the Reconfigure Key Auth. Protocol should
> prevent issues if the client has changed its link-local and a different
> client is now using that link-local address.

I agree that DHCPv6 Reconfigure is a fine place to use the link local
address and RFC3315 even gives guidance that the server could
synthesize a Relay-Reply using the client's previously known
peer-address field...I assume it can synthesize a full relay chain
based upon the most recent.  This also is dynamic information - the
server has no way of knowing whether or not the relay chain has been
changed, entire devices could be removed or replaced, resulting also
in changes in peer-address fields across the chain.

First, I think of this activity as being administrator-initiated
(directly or indirectly).  In many cases, a 'Reconfigure' tool will
probably let an operator specify the target address.  The operator can
and should be able to specify any address he knows - or thinks he
knows.  In the case of network administration systems that abstract
this - they should work well in whatever custom environments they're
tailored for.

But more importantly, Reconfigure is an operation that is accepted
to fail.  You don't need to rely on it to work - the client will
Renew eventually.  It's just an optimization.


I think it is problematic to rely upon the client's link local
address for any persistent operation where reliability is a
requirement.

For that sort of thing you really need a contract with the client
that they will continue to use an address for some length of time,
such as is implicit (and in the client's best interest) with an
addressed assigned via DHCPv6 IA_NA.

-- 
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
-- 
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://www1.ietf.org/pipermail/dhcwg/attachments/20070823/5076299a/attachmen
t.bin

------------------------------

Message: 2
Date: Thu, 23 Aug 2007 20:15:05 +0200
From: Bud Millwood <budm@weird-solutions.com>
Subject: Re: [dhcwg] lifetime of 'peer-address'
To: dhcwg@ietf.org
Message-ID: <200708232015.05121.budm@weird-solutions.com>
Content-Type: text/plain;  charset=3D"utf-8"

On Thursday 23 August 2007 19:35, David W. Hankins wrote:
> On Thu, Aug 23, 2007 at 08:41:25AM -0400, Bernie Volz (volz) wrote:
> > There is no contract about the link-local address, but in general why
> > would the client ever change that? It isn't like this address has
> > privacy issues (or put another way, there's no need to protect it as the
> > mac address is already available to others on the link).
>
> Because of the DUID and IAID abstractions, it's entirely possible
> that a client might change network devices (and thus hardware
> addresses, and therefore link local addresses) without changing its
> DUID or IAID.
>
> So it's encouraged that if a system were to be given a new network
> device (and therefore a new link-local), that it may still Confirm for
> the same IAID,DUID pair with the old addresses (and possibly even
> sessions) intact.

You're basically saying that a server should not use a previously recorded 
link-address during a client-initiated transaction, right? Under what 
circumstances *would* a server consider using a previously recorded link 
address for a client-initiated transaction?

- Bud



------------------------------

Message: 3
Date: Thu, 23 Aug 2007 13:33:48 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
Subject: Re: [dhcwg] lifetime of 'peer-address'
To: dhcwg@ietf.org
Message-ID: <20070823203348.GL10173@isc.org>
Content-Type: text/plain; charset=3D"us-ascii"

On Thu, Aug 23, 2007 at 08:15:05PM +0200, Bud Millwood wrote:
> You're basically saying that a server should not use a previously recorded

> link-address during a client-initiated transaction, right? Under what 

No...for uses totally external to DHCPv6 actually.  Any use in which
reliability beyond the current transaction is required.

The stipulation on ipv6@ietf.org was that "a DHCPv6 server 'knows'
the link-local addresses of all clients, because it can record the
'peer-address' field".  In context, they meant that this information
was reliable for a purpose that really couldn't be allowed to fail.

Where getting it wrong is substantially more expensive than failing a
Reconfigure; someone loses or can't get net.

I can find the mail in the archive if you like.  I'm really curious
if I'm missing something; the person's clarification was that the
server is always (reliably) updated in any event a link-local address
changes.

I haven't read that anywhere, so I'm wondering how we get from here
to there.

-- 
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
-- 
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://www1.ietf.org/pipermail/dhcwg/attachments/20070823/68d0bcde/attachmen
t.bin

------------------------------

Message: 4
Date: Thu, 23 Aug 2007 22:17:06 +0200
From: Bud Millwood <budm@weird-solutions.com>
Subject: Re: [dhcwg] lifetime of 'peer-address'
To: dhcwg@ietf.org
Message-ID: <200708232217.07065.budm@weird-solutions.com>
Content-Type: text/plain;  charset=3D"utf-8"

On Thursday 23 August 2007 22:33, David W. Hankins wrote:
> On Thu, Aug 23, 2007 at 08:15:05PM +0200, Bud Millwood wrote:
> > You're basically saying that a server should not use a previously
> > recorded link-address during a client-initiated transaction, right?
Under
> > what
>
> No...for uses totally external to DHCPv6 actually.  Any use in which
> reliability beyond the current transaction is required.
>
> The stipulation on ipv6@ietf.org was that "a DHCPv6 server 'knows'
> the link-local addresses of all clients, because it can record the
> 'peer-address' field".  In context, they meant that this information
> was reliable for a purpose that really couldn't be allowed to fail.
>
> Where getting it wrong is substantially more expensive than failing a
> Reconfigure; someone loses or can't get net.
>
> I can find the mail in the archive if you like.  I'm really curious
> if I'm missing something; the person's clarification was that the
> server is always (reliably) updated in any event a link-local address
> changes.
>
> I haven't read that anywhere, so I'm wondering how we get from here
> to there.

Aha, I see. I don't recall anything stating that the server *must* record
the 
link-local address. And as far as I know there's no standard way to query a=
 
DHCPv6 server for a client's link-local address. But since the DHCP server 
seems the logical place to track them for a given DUID/IAID, why not store
it 
and update it with CONFIRMS? If this information is needed by another 
protocol we could, for example, extend lease-query to support asking for
this 
info.

- Bud



------------------------------

Message: 5
Date: Thu, 23 Aug 2007 14:19:47 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
Subject: Re: [dhcwg] lifetime of 'peer-address'
To: dhcwg@ietf.org
Message-ID: <20070823211947.GN10173@isc.org>
Content-Type: text/plain; charset=3D"us-ascii"

On Thu, Aug 23, 2007 at 10:17:06PM +0200, Bud Millwood wrote:
> Aha, I see. I don't recall anything stating that the server *must* record
the 
> link-local address. And as far as I know there's no standard way to query
a 
> DHCPv6 server for a client's link-local address. But since the DHCP server

> seems the logical place to track them for a given DUID/IAID, why not store
it 
> and update it with CONFIRMS? If this information is needed by another 
> protocol we could, for example, extend lease-query to support asking for
this 
> info.

You sound certain that DHCPv6 servers are updated reliably...why?

This is 3 opinions for and one against, so I must be missing
something.

On the continuing subject of Confirm; a different server may answer
the Confirm without all servers seeing it, so if there's more than
one server there could be differing opinions of the client's address.
If the Confirm times out entirely (CNF_MAX_RD is 10 seconds), the
client may just continue to use their old addresses - and won't emit
more messages until t1.  So no server may have the up-to-date address.

That's even if you update your database on Confirms, which rather
ruins its lightweightness (a quality I rather like since operators
can manipulate t1, but they can't control how often boxes reboot).

-- 
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
-- 
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://www1.ietf.org/pipermail/dhcwg/attachments/20070823/38348199/attachmen
t.bin

------------------------------

Message: 6
Date: Thu, 23 Aug 2007 23:42:57 +0200
From: Bud Millwood <budm@weird-solutions.com>
Subject: Re: [dhcwg] lifetime of 'peer-address'
To: dhcwg@ietf.org
Message-ID: <200708232342.57972.budm@weird-solutions.com>
Content-Type: text/plain;  charset=3D"utf-8"

On Thursday 23 August 2007 23:19, David W. Hankins wrote:
> On Thu, Aug 23, 2007 at 10:17:06PM +0200, Bud Millwood wrote:
> > Aha, I see. I don't recall anything stating that the server *must*
record
> > the link-local address. And as far as I know there's no standard way to
> > query a DHCPv6 server for a client's link-local address. But since the
> > DHCP server seems the logical place to track them for a given DUID/IAID,
> > why not store it and update it with CONFIRMS? If this information is
> > needed by another protocol we could, for example, extend lease-query to
> > support asking for this info.
>
> You sound certain that DHCPv6 servers are updated reliably...why?

No, IM=04'm just thinking out loud. Your argument against is a valid 
consideration, because it's true that multiple DHCP servers may have 
differing data for a client's LL address, and all servers may have stale 
data.

I see no way to guarantee that even one DHCP server has a LL address for a 
client that is *definitely* known to be valid. Having said that, it may be 
highly likely that it is valid. Is that useful for whoever needs the info?

Is there a better way to identify a client as being the same machine after
it 
changes its LL address? That's exactly what DUID gives you.

So unless there's a mechanism that mimics DUID that I'm not aware of, I
guess 
the conclusion is that you can't know for sure, but the DHCP server can give

you a reasonable guess. <glad to be of service folks, we'll be here all 
week> :)

- Bud



------------------------------

Message: 7
Date: Thu, 23 Aug 2007 23:59:32 +0200
From: Bud Millwood <budm@weird-solutions.com>
Subject: [dhcwg] Vendor-specific options
To: dhcwg@ietf.org
Message-ID: <200708232359.32262.budm@weird-solutions.com>
Content-Type: text/plain;  charset=3D"utf-8"

In DHCPv4, the vendor options contained in option 43 were interpreted 
according to the free-form text of option 60. Vendors were free to put 
anything in option 60, and many of them chose different data for different 
models of their equipment.

In DHCPv6 the vendor options are interpreted according to the vendor_id
field, 
but vendors are *not* free to put anything in there that they want - just 
their assigned id.

How are vendors expected to define different sets of options for different 
equipment? It seems to me that the possibilities are:

1. Vendors don't have different options, they use the 16-bit tag space to 
define all options for all devices. Seems like a bad idea for a couple of 
reasons, one being you can't easily narrow down and present to the user a
set 
of options for a particular piece of equipment.

2. Vendors start defining their own free-form text fields inside the VSO,
and 
we end up looking awfully similar to DHCPv4.

3. Vendors use 'vendor-sub-identifiers', hopefully modelled after the VSO.

It seems the VSO in DHCPv6 tried to solve the problem of allowing free-form=
 
vendor class, but just deferred the problem to parsing within the VSO - at 
least in the case where a vendor had multiple option 60 values for different

sets of vendor-specific options (in DHCPv4).

Are we going to see all sorts of crazy schemes in the DHCPv6 VSO to denote 
different option spaces?

Are any vendors currently partitioning their VSO suboptions?

Could/should we recommend that vendors use the VSO format inside the VSO if=
 
they want partitioned option spaces?

- Bud



------------------------------

Message: 8
Date: Thu, 23 Aug 2007 19:06:38 -0400
From: "Brzozowski, John" <John_Brzozowski@Cable.Comcast.com>
Subject: RE: [dhcwg] Vendor-specific options
To: "Bud Millwood" <budm@weird-solutions.com>,	<dhcwg@ietf.org>
Message-ID:
	
<997BC128AE961E4A8B880CD7442D9480174EA5@NJCHLEXCMB01.cable.comcast.com>
	
Content-Type: text/plain;	charset=3D"iso-8859-1"

Hello Bud,

I am not sure if I am following all of the points below.  I will try to
offer some comments, however.

Vendor class in particular in DHCPv6 includes an enterprise-id that is used
to differentiate the values within.  Other options can be defined  in the
vendor option space (17) which also includes an enterprise-id.  An example
of where this has been used is in DOCSIS 3.0.

Is this what you were inquiring about?

HTH,

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



-----Original Message-----
From: Bud Millwood [mailto:budm@weird-solutions.com]
Sent: Thu 8/23/2007 5:59 PM
To: dhcwg@ietf.org
Subject: [dhcwg] Vendor-specific options
 
In DHCPv4, the vendor options contained in option 43 were interpreted 
according to the free-form text of option 60. Vendors were free to put 
anything in option 60, and many of them chose different data for different 
models of their equipment.

In DHCPv6 the vendor options are interpreted according to the vendor_id
field, 
but vendors are *not* free to put anything in there that they want - just 
their assigned id.

How are vendors expected to define different sets of options for different 
equipment? It seems to me that the possibilities are:

1. Vendors don't have different options, they use the 16-bit tag space to 
define all options for all devices. Seems like a bad idea for a couple of 
reasons, one being you can't easily narrow down and present to the user a
set 
of options for a particular piece of equipment.

2. Vendors start defining their own free-form text fields inside the VSO,
and 
we end up looking awfully similar to DHCPv4.

3. Vendors use 'vendor-sub-identifiers', hopefully modelled after the VSO.

It seems the VSO in DHCPv6 tried to solve the problem of allowing free-form=
 
vendor class, but just deferred the problem to parsing within the VSO - at 
least in the case where a vendor had multiple option 60 values for different

sets of vendor-specific options (in DHCPv4).

Are we going to see all sorts of crazy schemes in the DHCPv6 VSO to denote 
different option spaces?

Are any vendors currently partitioning their VSO suboptions?

Could/should we recommend that vendors use the VSO format inside the VSO if=
 
they want partitioned option spaces?

- Bud

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




------------------------------

Message: 9
Date: Thu, 23 Aug 2007 16:18:01 -0700
From: "David W. Hankins" <David_Hankins@isc.org>
Subject: Re: [dhcwg] Vendor-specific options
To: dhcwg@ietf.org
Message-ID: <20070823231801.GO10173@isc.org>
Content-Type: text/plain; charset=3D"us-ascii"

On Thu, Aug 23, 2007 at 11:59:32PM +0200, Bud Millwood wrote:
> 1. Vendors don't have different options, they use the 16-bit tag space to=
 
> define all options for all devices. Seems like a bad idea for a couple of=
 
> reasons, one being you can't easily narrow down and present to the user a
set 
> of options for a particular piece of equipment.

This is my understanding.

I think that DOCSIS, concerned I think about having a large number of
options in one 16-bit space, has elected to use a sub-parameter-
request-list option.  I might be thinking of something else, but I
think DOCSIS 3 specified one.

Where software supports it - the operator configures all the values
for all the different options, and they get delivered automatically
to the clients that want them.

	option vendor.foo ...;
	option vendor.bar ...;
	option vendor.baz ...;

Where software doesn't support it - the operator configures "classes"
that match individual vendor class options, and configure values
relevant to those classes of clients in one place.  The output packet
contains only that which is relevant to the class of client in
question.

	class "thingits" {
		match if vivco.example =3D "thingit";
		option vendor.foo ...;
	}
	class "whatsis" {
		match if vivco.example =3D "whatsis";
		option vendor.bar ...;
	}
	class "dongles" {
		match if vivco.example =3D "dongles";
		option vendor.baz ...;
	}

(where vivco is 'vendor identified vendor class option'...I can't
remember which is which anymore...is it "vcio" for DHCPv6?)


The worst case is that the clients get big packets.

I don't think there's a danger that vendors are going to have multiple
option spaces with one enterprise-ID...but if someone says they might,
we should listen.

-- 
Ash bugud-gul durbatuluk agh burzum-ishi krimpatul.
Why settle for the lesser evil?	 https://secure.isc.org/store/t-shirt/
-- 
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://www1.ietf.org/pipermail/dhcwg/attachments/20070823/a90c00dd/attachmen
t.bin

------------------------------

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


End of dhcwg Digest, Vol 40, Issue 26
*************************************


DISCLAIMER=0A=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=0A=
This e-mail may contain privileged and confidential information which is the=
 property of Persistent Systems Pvt. Ltd. It is intended only for the use of=
 the individual or entity to which it is addressed. If you are not the inten=
ded recipient, you are not authorized to read, retain, copy, print, distribu=
te or use this message. If you have received this communication in error, pl=
ease notify the sender and delete all copies of this message. Persistent Sys=
tems Pvt. Ltd. does not accept any liability for virus infected mails.

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



From dhcwg-bounces@ietf.org Fri Aug 24 10:26:34 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IOa5c-0001ab-VH; Fri, 24 Aug 2007 10:24:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IOa5b-0001aU-Hv
	for dhcwg@ietf.org; Fri, 24 Aug 2007 10:24:43 -0400
Received: from ams-iport-1.cisco.com ([144.254.224.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IOa5a-0002Jz-5p
	for dhcwg@ietf.org; Fri, 24 Aug 2007 10:24:43 -0400
Received: from ams-dkim-1.cisco.com ([144.254.224.138])
	by ams-iport-1.cisco.com with ESMTP; 24 Aug 2007 16:24:40 +0200
X-IronPort-AV: i="4.19,305,1183327200"; 
	d="scan'208"; a="151407134:sNHT75319406"
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150])
	by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7OEOd2p016146; 
	Fri, 24 Aug 2007 16:24:39 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com
	[144.254.231.87])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7OEOb4L026949; 
	Fri, 24 Aug 2007 14:24:39 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by
	xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 24 Aug 2007 16:24:23 +0200
Received: from [10.149.25.171] ([10.61.67.15]) by xfe-ams-332.cisco.com with
	Microsoft SMTPSVC(6.0.3790.1830); Fri, 24 Aug 2007 16:24:22 +0200
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <882DE750-AC8E-4106-958B-9FA5F407E4F9@cisco.com>
Content-Transfer-Encoding: 7bit
From: Ralph Droms <rdroms@cisco.com>
Date: Fri, 24 Aug 2007 10:25:27 -0400
To: dhcwg@ietf.org
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 24 Aug 2007 14:24:22.0411 (UTC)
	FILETIME=[772B25B0:01C7E65A]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4801; t=1187965479;
	x=1188829479; c=relaxed/simple; s=amsdkim1002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rdroms@cisco.com;
	z=From:=20Ralph=20Droms=20<rdroms@cisco.com>
	|Subject:=20DRAFT=20minutes=20for=20IETF=2069=20dhc=20WG=20meeting
	|Sender:=20; bh=7SSlMzrkNOCwITYOuHozTZE4jDwfeW59K59awc0hKVc=;
	b=GT098+rPQyMwpyOpUqsQZgEEDHc4xNuTmbxYrbnjhyMiIIwUJZlU2cDjYUi9ZT5sDMxJ/Sam
	vTw6IlT3cP2589tCvK2zoVEBxLJxiCH4pNKIeeiA+WlUsZ/v2j1a+jW3;
Authentication-Results: ams-dkim-1; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/amsdkim1002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813
Cc: dhc-chairs@tools.ietf.org
Subject: [dhcwg] DRAFT minutes for IETF 69 dhc WG meeting
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

DRAFT minutes are included below.  Please respond with additions,  
corrections, deletions by 8/29.

- Ralph

		       dhc WG meeting, IETF 69
			   Meeting Minutes
		       -----------------------

Thanks to John Schnizlein for taking notes during the meeting and to
the Jabber scribe, Alexandru Petrescu.

* Draft last call and adoption announcements

The chairs gave an update on the status of dhc WG documents and noted
that two drafts are in WG last call:

   draft-ietf-dhc-vpn-option
   draft-ietf-dhc-agent-vpn-id


* Progressing two drafts under RFC 3942

The chairs announced that two drafts, which had been taken on as WG
work items before the publication of RFC 3942, will now be published
as Informational RFCs, under the guidelines of RFC 3942:

draft-ietf-dhc-subnet-alloc
draft-raj-dhc-tftp-addr-option


* Update to DHCP options guideline

draft-dhankins-dhcp-option-guidelines-00 has been published as a
revision to draft-dhankins-atomic-dhcp-00.  The revised document has
been reorganized and several sections have been extended.  The chairs
will ask the WG for consensus to take this document as a WG work item
when it is available at the IETF I-D repository.


* Using DHCPv6 and AAA Server for mobile station PD

Bechet Sarikaya gave a presentation on
draft-sarikaya-16ng-prefix-delegation-01, which requires dhc WG input
as it proposes changes to the definition of the IAID for address
assignment and prefix delegation.  The 16nf WG proposes to use DHCPv6
prefix delegation for assignment of a prefix to a mobile station.
draft-sarikaya-16ng-prefix-delegation-01 proposes changing the IAID to
6 bytes, which would accommodate the remote station MAC address as an
identifier.  David Hankins and Jari Arkko opposed redefining the
IAID.  John Schnizlein asked for a clarification about the prefix
requested through prefix delegation: does the access router request
the prefix for use on the AR<->mobile link, or for use on additional
links attached to mobile link?  The WG will be asked to discuss the
use of prefix delegation in the 16nf scenario and how to identify
clients within the 4 byte IAID.


* Layer 2 relay agent and relay agent chaining

Pavan Kurapati discussed two drafts:
draft-joshi-dhc-layer2-relay-agent-01 and
draft-kurapati-dhc-relay-chaining-dhcpv4-01.  The first of these
drafts describes guidelines for interpretations of existing DHCP
specifications to successfully allow L2 relay agents to participate in
DHCPv4 message exchanges.  Hankins commented that this draft is needed
to formalize existing deployment scenarios, which have yielded
unexpected results.

The second draft describes extensions to DHCPv4 to allow both an L2
relay agent and an L3 relay agent to insert relay agent options into a
message from a DHCP client to the server.  John Schnizlein noted that
this proposal violates RFC 3046, which allows only one set of relay
agent options, and which requires trust of the L2 relay agent on the
part of the L3 relay agent.

The members of the WG at the meeting expressed interest in continuing
discussion of these drafts of the dhc WG mailing list.

* TAHI DHCPv6 Test tool for IPv6 Ready Logo

Hideshi Enokihara gave a brief summary of the TAHI DHCPv6 test tool
and the results of DHCPv6 testing at the most recent TAHI test event.
There is now an IPv6 Ready (phase 1) logo for DHCPv6, and a phase 2
program started earlier this year.  Ted Lemon asked if there are any
common client failures.  Hideshi responded that the problem most
frequent problem with clients is sending RFC-compliant messages.

* Extensions to DHCPv6 for prefix and default router information

Tim Chown led a discussion of handling rogue RAs in an IPv6
deployment.  The motivation for this presentation is that
administrators of operational networks, mostly universities are
comfortable with DHCP, but are finding problems with 'rogue Router
Advertisments'.  One possible alternative is to avoid RAs and use DHCP
for prefix and default router information.

Bogus RAs can originate from several sources:

1) configuration error - sometimes with long lifetime
2) User-induced accidents: host acting as 6to4 router from home
3) malice

Arkko said that it's not clear DHCP is the right way to deal with
these problems.  Dave Thaler pointed out that SeND is the official
solution to this problem, so creating another solution does not
improve the situation.  Thaler also pointed out that, with the
revision to the "on-link assumption" in RFC 2461bis, there may be a
need for passing prefix information in DHCP.  Alain Durand expressed
interest in using DHCP for prefix and default router information.  Tim
Chown promised to publish a draft documenting the problem.

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



From dhcwg-bounces@ietf.org Sun Aug 26 01:25:27 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPAb4-0007ed-4A; Sun, 26 Aug 2007 01:23:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPAb2-0007ce-Gk
	for dhcwg@ietf.org; Sun, 26 Aug 2007 01:23:36 -0400
Received: from tyholt.uninett.no ([2001:700:1::eecb])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IPAb0-0002Hv-MF
	for dhcwg@ietf.org; Sun, 26 Aug 2007 01:23:36 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by tyholt.uninett.no (Postfix) with ESMTP id 25EC42BADE3;
	Sun, 26 Aug 2007 07:23:33 +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 17470-01-3; Sun, 26 Aug 2007 07:23:33 +0200 (CEST)
Received: from [192.168.0.213] (unknown [210.74.156.102])
	by tyholt.uninett.no (Postfix) with ESMTP id 5207D2BADE1;
	Sun, 26 Aug 2007 07:23:30 +0200 (CEST)
Message-ID: <46D11182.4050102@uninett.no>
Date: Sun, 26 Aug 2007 07:37:06 +0200
From: Stig Venaas <stig.venaas@uninett.no>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: dhcwg <dhcwg@ietf.org>
Subject: Re: [dhcwg] Adopting draft-dhankins-dhcp-option-guidelines-01 as
	wg	work item
References: <46B6D75F.6040003@uninett.no>
In-Reply-To: <46B6D75F.6040003@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.1 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: dhc-chairs@tools.ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Stig Venaas wrote:
> There was consensus at the dhc wg meeting in Chicago to adopt
> draft-dhankins-dhcp-option-guidelines-01 as a dhc wg work item.
> 
> If there are no objections posted to the wg mailing list, the
> chairs will accept the draft as a wg work item on 2007-08-20.

As there have been no objections this draft is now a wg work item.
Dave, please resubmit it as draft-ietf-dhc-option-guidelines-00,
or you may prefer draft-ietf-dhc-dhcp-option-guidelines-00?

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 Mon Aug 27 05:30:50 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPau7-0001ZN-PE; Mon, 27 Aug 2007 05:29:03 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPau5-0001ZF-MG
	for dhcwg@ietf.org; Mon, 27 Aug 2007 05:29:01 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IPau5-0007Cl-0Z
	for dhcwg@ietf.org; Mon, 27 Aug 2007 05:29:01 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 7573D19865A;
	Mon, 27 Aug 2007 12:28:59 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 2B5AF198659;
	Mon, 27 Aug 2007 12:28:59 +0300 (EEST)
Message-ID: <46D2995B.2080200@piuha.net>
Date: Mon, 27 Aug 2007 12:28:59 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.13 (X11/20070824)
MIME-Version: 1.0
To: Dhcwg <dhcwg@ietf.org>,  draft-ietf-dhc-pxelinux@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: 
Subject: [dhcwg] AD review of draft-ietf-dhc-pxelinux-02
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

I have made my AD review on this document.
The document is basically in good shape, but
I noticed a few places where clearer text was
needed. First, I believe it would be useful if
the abstract also stated that the code
values will be assigned for this purpose, and
not only describe what the situation is
before the approval of this document.

Second, Section 3.4 text should be improved
to avoid an apparent inconsistency (... recommend
use ... undesirable to suffer collisions ...)

There were a few other small things.

Given that the changes are small, I have simply
inserted RFC Editor notes to the tracker and
intend to take the draft to the IESG review without
asking for a new revision.

Comments on the suggested edits appreciated,
see below.

Jari

>   Please add normative reference to RFC 854 where NVT-ASCII
>   first appears.

>   Change the last sentence of Section 1 from
>
>    Each option as they are defined below carries a response to RFC3942.
>
>   to
>
>    Each option definition below provides a response to RFC3942.

>
>   Change the last paragraph of Section 3.4 from
>
>    It is not only reasonable to utilize this option code for another
>    purpose, it is recommended, except that it is undesirable for any
>    future consumer of this option code to have to suffer potential
>    collisions in legacy userbases.
>
>   to
>
>    It is reasonable to utilize this option code for another
>    purpose, but it is recommended to do this at a later time,
>    given desire to avoid potential collisions in legacy
>    userbases.

>   Change the sentence in the abstract from
>
>    These codes were historically designated 'Site Local', but
>    are presently being made available for allocation as standard
>    DHCP Options.
>
>   to
>
>    These codes were historically designated 'Site Local', but
>    are presently being made available for allocation as standard
>    DHCP Options. This document marks these codes as assigned.


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



From dhcwg-bounces@ietf.org Mon Aug 27 08:20:58 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPdYr-0003Hw-2i; Mon, 27 Aug 2007 08:19:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPdYp-0003Hq-Lz
	for dhcwg@ietf.org; Mon, 27 Aug 2007 08:19:15 -0400
Received: from szxga03-in.huawei.com ([61.144.161.55])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IPdYo-0002Fa-LC
	for dhcwg@ietf.org; Mon, 27 Aug 2007 08:19:15 -0400
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JNF00H2EM6UL0@szxga03-in.huawei.com> for
	dhcwg@ietf.org; Mon, 27 Aug 2007 20:18:30 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JNF0088TM6UTH@szxga03-in.huawei.com> for
	dhcwg@ietf.org; Mon, 27 Aug 2007 20:18:30 +0800 (CST)
Received: from SSK1548 ([10.18.5.107])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JNF00BDFM6PJ4@szxml04-in.huawei.com> for
	dhcwg@ietf.org; Mon, 27 Aug 2007 20:18:30 +0800 (CST)
Date: Mon, 27 Aug 2007 17:48:25 +0530
From: "S.SenthilKumar (Huawei)" <senthilKumars@huawei.com>
To: dhcwg@ietf.org
Message-id: <002f01c7e8a4$5e882610$6b05120a@china.huawei.com>
Organization: Huawei
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: quoted-printable
Thread-index: AcfooLtnBxB8mrtwTvCPnampzBpsoQAA2P3A
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: ssenthilkumar@gmail.com, senthilKumars@huawei.com
Subject: [dhcwg] FW: Issue/Solution for Confirm-Reply
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: senthilKumars@huawei.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

Dear All
Please suggest how to resolve this issue.
Configuration
=E3=80=80=E3=80=80Assume that IA1, IA2 and IA3 were present in the same =
interface
=E3=80=80=E3=80=80* IA1 has binding with Server S1 and K1 is the DAP key =
in use for the current session
=E3=80=80=E3=80=80* IA2 has binding with Server S2 and K2 is the DAP key =
in use for the current session
=E3=80=80=E3=80=80* IA3 has binding with Server S3 and No DAP =
Authentication (Client has accepted Advertise without Authentication =
Option as it is enabled in the local configuration)
=E3=80=80=E3=80=80* And all the IAs leased.

As per RFC, Confirm message has to be sent to the server containing all =
the IAs present in the interface. But in this case how, Which Key has to =
be used, whether DAP Option has to be present.=20

18.1.2. Creation and Transmission of Confirm Messages
The client MUST include a Client Identifier option to identify itself to =
the server.  The client includes IA options for all of the IAs assigned =
to the interface for which the Confirm message is being sent.  The IA =
options include all of the addresses the client currently has associated =
with those IAs.  The client SHOULD set the T1 and T2 fields in any IA_NA =
options, and the preferred-lifetime and valid-lifetime fields in the IA =
Address options to 0, as the server will ignore these fields.

Solution I had devised is that Confirm can be send on the basics of IA =
i.e confirm will carry only one IA (IA_NA or IA_TA)

Advantages of the solution
1. If Not on link status is received in the Reply received in response =
to Confirm, Only the address present in the IA will be released
2. Authentication =E2=80=93 Confirm-Reply transaction will also be part =
of the session (Solicit-Advertise till Release/Decline of the last =
address)
Disadvantages of the solution
1. Multiple Confirm message will be send from the client (Also loads the =
server)
2. RFC Conformance =E2=80=93 I=E2=80=99m not sure about this as =
=E2=80=9CALL=E2=80=9D is mentioned in the RFC.

Let me know your views.

Thanking you,

Regards
SenthilKumar.S


Disclaimer: This e-mail and attachments contain confidential information =
from HUAWEI, which is intended only for the person or entity whose =
address is listed above. Any use of the information contained herein in =
any way (including, but not limited to, total or partial disclosure, =
reproduction, or dissemination) by persons other than the intended =
recipient's) is prohibited. If you receive this e-mail in error, please =
notify the sender by phone or email immediately and delete it!




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



From dhcwg-bounces@ietf.org Tue Aug 28 11:29:35 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQ2yq-00084g-GH; Tue, 28 Aug 2007 11:27:48 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQ2yp-00084a-2d
	for dhcwg@ietf.org; Tue, 28 Aug 2007 11:27:47 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQ2yo-0003pB-LY
	for dhcwg@ietf.org; Tue, 28 Aug 2007 11:27:46 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 28 Aug 2007 11:27:47 -0400
X-IronPort-AV: i="4.19,316,1183348800"; 
	d="scan'208"; a="69322468:sNHT53398236"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7SFRkEM013860; 
	Tue, 28 Aug 2007 11:27:46 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7SFRjDR013111; 
	Tue, 28 Aug 2007 15:27:45 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Aug 2007 11:27:35 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [dhcwg] lifetime of 'peer-address'
Date: Tue, 28 Aug 2007 11:27:36 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB2104E034BD@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <200708232342.57972.budm@weird-solutions.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] lifetime of 'peer-address'
Thread-Index: Acfl06OP8a5eSyj0QIqgNeBMwN/xtgDs8/Yg
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "Bud Millwood" <budm@weird-solutions.com>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 28 Aug 2007 15:27:35.0746 (UTC)
	FILETIME=[F5D32220:01C7E987]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3290; t=1188314866;
	x=1189178866; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=volz@cisco.com;
	z=From:=20=22Bernie=20Volz=20\(volz\)=22=20<volz@cisco.com>
	|Subject:=20RE=3A=20[dhcwg]=20lifetime=20of=20'peer-address'
	|Sender:=20
	|To:=20=22Bud=20Millwood=22=20<budm@weird-solutions.com>,
	=20<dhcwg@ietf.o rg>;
	bh=rJqRWaGAAL4KoLEvdikpV5D5m2glNqL94nzpNtQxwuk=;
	b=PmA0LqdiXOY9O9prQiATNAC9bkpLxr5t78hkGUUdx19RYlAbubfVjoVzvsxs0JA33+fS2csw
	3J0HF240T9A3ku3p6N47NueS/7drW6wS5UJYbNfnoxaeGtx5xamgtX37;
Authentication-Results: rtp-dkim-2; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1731952368=="
Errors-To: dhcwg-bounces@ietf.org

--===============1731952368==
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: base64

SSBmdWxseSBhZ3JlZSB0aGF0IHVzZSBvZiB0aGlzIHBlZXItYWRkcmVzcyBpbmZvcm1hdGlvbiAo
YmV5b25kIHRoZSBvcmlnaW5hbCB0cmFuc2FjdGlvbikgaXMgcHJvYmxlbWF0aWMuIEl0IGlzIG1v
cmUgcHJvYmxlbWF0aWMgdGhhbiBhIGNsaWVudCdzIGFkZHJlc3NlczsgYWZ0ZXIgYWxsLCB0aGUg
Y2xpZW50IG1pZ2h0IGhhdmUgbmVnb3RpYXRlZCBkaWZmZXJlbnQgYWRkcmVzc2VzIHdpdGggYSBk
aWZmZXJlbnQgREhDUCBzZXJ2ZXIgd2l0aG91dCBoYXZpbmcgcmVsZWFzZWQgdGhlIGN1cnJlbnQg
YWRkcmVzc2VzIHNvIHRoZXkgY2FuJ3QgYmUgcmVsaWVkIG9uIGVpdGhlci4gQW55IERIQ1B2NiBy
ZWxhdGVkIGluZm9ybWF0aW9uIGlzIHBvdGVudGlhbGx5IHN0YWxlOyBzdGF0ZWZ1bGx5IGFzc2ln
bmVkIGFkZHJlc3NlcyBvciBkZWxlZ2F0ZWQgcHJlZml4ZXMgbGVzcyBzbyB0aGFuIHRoZSBsaW5r
LWxvY2FsIGFkZHJlc3NlcyAoaS5lLiwgInBlZXItYWRkcmVzcyIgb3Igc291cmNlIGFkZHJlc3Mp
Lg0KDQotIEJlcm5pZQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogQnVkIE1p
bGx3b29kIFttYWlsdG86YnVkbUB3ZWlyZC1zb2x1dGlvbnMuY29tXSANClNlbnQ6IFRodXJzZGF5
LCBBdWd1c3QgMjMsIDIwMDcgNTo0MyBQTQ0KVG86IGRoY3dnQGlldGYub3JnDQpTdWJqZWN0OiBS
ZTogW2RoY3dnXSBsaWZldGltZSBvZiAncGVlci1hZGRyZXNzJw0KDQpPbiBUaHVyc2RheSAyMyBB
dWd1c3QgMjAwNyAyMzoxOSwgRGF2aWQgVy4gSGFua2lucyB3cm90ZToNCj4gT24gVGh1LCBBdWcg
MjMsIDIwMDcgYXQgMTA6MTc6MDZQTSArMDIwMCwgQnVkIE1pbGx3b29kIHdyb3RlOg0KPiA+IEFo
YSwgSSBzZWUuIEkgZG9uJ3QgcmVjYWxsIGFueXRoaW5nIHN0YXRpbmcgdGhhdCB0aGUgc2VydmVy
ICptdXN0KiByZWNvcmQNCj4gPiB0aGUgbGluay1sb2NhbCBhZGRyZXNzLiBBbmQgYXMgZmFyIGFz
IEkga25vdyB0aGVyZSdzIG5vIHN0YW5kYXJkIHdheSB0bw0KPiA+IHF1ZXJ5IGEgREhDUHY2IHNl
cnZlciBmb3IgYSBjbGllbnQncyBsaW5rLWxvY2FsIGFkZHJlc3MuIEJ1dCBzaW5jZSB0aGUNCj4g
PiBESENQIHNlcnZlciBzZWVtcyB0aGUgbG9naWNhbCBwbGFjZSB0byB0cmFjayB0aGVtIGZvciBh
IGdpdmVuIERVSUQvSUFJRCwNCj4gPiB3aHkgbm90IHN0b3JlIGl0IGFuZCB1cGRhdGUgaXQgd2l0
aCBDT05GSVJNUz8gSWYgdGhpcyBpbmZvcm1hdGlvbiBpcw0KPiA+IG5lZWRlZCBieSBhbm90aGVy
IHByb3RvY29sIHdlIGNvdWxkLCBmb3IgZXhhbXBsZSwgZXh0ZW5kIGxlYXNlLXF1ZXJ5IHRvDQo+
ID4gc3VwcG9ydCBhc2tpbmcgZm9yIHRoaXMgaW5mby4NCj4NCj4gWW91IHNvdW5kIGNlcnRhaW4g
dGhhdCBESENQdjYgc2VydmVycyBhcmUgdXBkYXRlZCByZWxpYWJseS4uLndoeT8NCg0KTm8sIEnN
hCdtIGp1c3QgdGhpbmtpbmcgb3V0IGxvdWQuIFlvdXIgYXJndW1lbnQgYWdhaW5zdCBpcyBhIHZh
bGlkIA0KY29uc2lkZXJhdGlvbiwgYmVjYXVzZSBpdCdzIHRydWUgdGhhdCBtdWx0aXBsZSBESENQ
IHNlcnZlcnMgbWF5IGhhdmUgDQpkaWZmZXJpbmcgZGF0YSBmb3IgYSBjbGllbnQncyBMTCBhZGRy
ZXNzLCBhbmQgYWxsIHNlcnZlcnMgbWF5IGhhdmUgc3RhbGUgDQpkYXRhLg0KDQpJIHNlZSBubyB3
YXkgdG8gZ3VhcmFudGVlIHRoYXQgZXZlbiBvbmUgREhDUCBzZXJ2ZXIgaGFzIGEgTEwgYWRkcmVz
cyBmb3IgYSANCmNsaWVudCB0aGF0IGlzICpkZWZpbml0ZWx5KiBrbm93biB0byBiZSB2YWxpZC4g
SGF2aW5nIHNhaWQgdGhhdCwgaXQgbWF5IGJlIA0KaGlnaGx5IGxpa2VseSB0aGF0IGl0IGlzIHZh
bGlkLiBJcyB0aGF0IHVzZWZ1bCBmb3Igd2hvZXZlciBuZWVkcyB0aGUgaW5mbz8NCg0KSXMgdGhl
cmUgYSBiZXR0ZXIgd2F5IHRvIGlkZW50aWZ5IGEgY2xpZW50IGFzIGJlaW5nIHRoZSBzYW1lIG1h
Y2hpbmUgYWZ0ZXIgaXQgDQpjaGFuZ2VzIGl0cyBMTCBhZGRyZXNzPyBUaGF0J3MgZXhhY3RseSB3
aGF0IERVSUQgZ2l2ZXMgeW91Lg0KDQpTbyB1bmxlc3MgdGhlcmUncyBhIG1lY2hhbmlzbSB0aGF0
IG1pbWljcyBEVUlEIHRoYXQgSSdtIG5vdCBhd2FyZSBvZiwgSSBndWVzcyANCnRoZSBjb25jbHVz
aW9uIGlzIHRoYXQgeW91IGNhbid0IGtub3cgZm9yIHN1cmUsIGJ1dCB0aGUgREhDUCBzZXJ2ZXIg
Y2FuIGdpdmUgDQp5b3UgYSByZWFzb25hYmxlIGd1ZXNzLiA8Z2xhZCB0byBiZSBvZiBzZXJ2aWNl
IGZvbGtzLCB3ZSdsbCBiZSBoZXJlIGFsbCANCndlZWs+IDopDQoNCi0gQnVkDQoNCl9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpkaGN3ZyBtYWlsaW5nIGxp
c3QNCmRoY3dnQGlldGYub3JnDQpodHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9kaGN3Zw0K


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

--===============1731952368==--



From dhcwg-bounces@ietf.org Tue Aug 28 12:06:15 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQ3YM-00012U-OU; Tue, 28 Aug 2007 12:04:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IO8rj-0003Iw-KN; Thu, 23 Aug 2007 05:20:35 -0400
Received: from mistral.mail.adnap.net.au ([203.6.132.90])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IO8rj-0000k1-1p; Thu, 23 Aug 2007 05:20:35 -0400
Received: from 219-90-137-128.ip.adam.com.au ([219.90.137.128]
	helo=mail.nosense.org)
	by mistral.mail.adnap.net.au with esmtp (Exim 4.60 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1IO8sV-000AJI-CM; Thu, 23 Aug 2007 18:51:23 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id 73EB2FC83;
	Thu, 23 Aug 2007 18:50:25 +0930 (CST)
Date: Thu, 23 Aug 2007 18:50:25 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: James Carlson <james.d.carlson@sun.com>
Message-Id: <20070823185025.b326fece.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <18122.57377.942962.976694@gargle.gargle.HOWL>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
	<FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
	<8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
	<A822303F-0054-4462-866F-1689EBFE9958@apple.com>
	<471515FC--E1E1-4C83-99AA-A9821E0C2FF5@muada.com>
	<18121.37093.872115.212299@gargle.gargle.HOWL>
	<BAA24DD4-8DF1-4C72-969A-37ACF82637B7@muada.com>
	<18122.57377.942962.976694@gargle.gargle.HOWL>
X-Mailer: Sylpheed 2.4.4 (GTK+ 2.10.14; i686-pc-linux-gnu)
X-Location: Lower Mitcham, South Australia, 5062
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
X-Mailman-Approved-At: Tue, 28 Aug 2007 12:04:29 -0400
Cc: IETF, dhcwg@ietf.org, Iljitsch van Beijnum <iljitsch@muada.com>,
	Mailing List <ipv6@ietf.org>
Subject: [dhcwg] Re: Rethinking autoconfig,
 was Re: prefix length determination 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

On Tue, 21 Aug 2007 08:52:49 -0400
James Carlson <james.d.carlson@sun.com> wrote:

> Iljitsch van Beijnum writes:
> > On 20-aug-2007, at 15:02, James Carlson wrote:
> > > To me, that sounds like high cost with essentially no benefit.  What
> > > am I missing?
<snip>
> This means that the DHCP server is perfect in its operation and
> omniscient about all hosts that may be attached to the network, even
> the statically-configured ones.
> 
> I've yet to meet one that is this good.
> 

Agree, and then you also get people like me who occasionally, in a
desperate situation, do a dirty, dirty thing like steal one of the DHCP
server's dynamic addresses for a static assignment, and rely on DAD by
both the DHCP and other hosts to avoid conflicts, while I deal with
the desperate situation.

I don't like doing that sort of thing, but I like that both the DHCP
server and hosts are robust enough to handle it gracefully when I do. A
few extra packets seems to me to be a relatively small price to pay for
robustness and resilience.

Regards,
Mark.


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



From dhcwg-bounces@ietf.org Tue Aug 28 12:13:11 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQ3f6-00047u-PV; Tue, 28 Aug 2007 12:11:28 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQ3f6-00047m-4z; Tue, 28 Aug 2007 12:11:28 -0400
Received: from exprod7og51.obsmtp.com ([64.18.2.157])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IQ3f5-0005CG-LI; Tue, 28 Aug 2007 12:11:28 -0400
Received: from source ([81.200.64.181]) (using TLSv1) by
	exprod7ob51.obsmtp.com ([64.18.6.12]) with SMTP; 
	Tue, 28 Aug 2007 09:11:14 PDT
Received: from mail.nominum.com (mail.nominum.com [81.200.64.186])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by shell-ng.nominum.com (Postfix) with ESMTP id 8B27856893;
	Tue, 28 Aug 2007 09:11:14 -0700 (PDT)
	(envelope-from Ted.Lemon@nominum.com)
X-Spam-Status: No, hits=0.0 required=8.4
	tests=CUSTOM_RULE_FROM: ALLOW,TOTAL_SCORE: 0.000
X-Spam-Level: 
Received: from [10.0.1.126] ([71.162.123.207])
	(authenticated user mellon@nominum.com) by mail.nominum.com
	(using TLSv1/SSLv3 with cipher AES128-SHA (128 bits));
	Tue, 28 Aug 2007 09:11:12 -0700
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <20070823185025.b326fece.ipng@69706e6720323030352d30312d31340a.nosense.org>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<FDB98139-14EE-4D5F-B96D-C301A4859361@muada.com>
	<18113.42485.158453.756815@gargle.gargle.HOWL>
	<20070814183418.GC3914@isc.org>
	<18115.3756.371573.103258@gargle.gargle.HOWL>
	<20070815175140.GC18683@isc.org>
	<m1zm0reu44.wl%jinmei@isl.rdc.toshiba.co.jp>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038812F0@xmb-rtp-20e.amer.cisco.com>
	<FD512419-10D7-479E-9103-36C0C5BB32EE@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D0388138C@xmb-rtp-20e.amer.cisco.com>
	<8706B8AE-001D-4403-A387-5255F67557F4@muada.com>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038813A2@xmb-rtp-20e.amer.cisco.com>
	<39C363776A4E8C4A94691D2BD9D1C9A1029ED9C6@XCH-NW-7V2.nw.nos.boeing.com>
	<A822303F-0054-4462-866F-1689EBFE9958@apple.com>
	<471515FC--E1E1-4C83-99AA-A9821E0C2FF5@muada.com>
	<18121.37093.872115.212299@gargle.gargle.HOWL>
	<BAA24DD4-8DF1-4C72-969A-37ACF82637B7@muada.com>
	<18122.57377.942962.976694@gargle.gargle.HOWL>
	<20070823185025.b326fece.ipng@69706e6720323030352d30312
	d31340a.nosense.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <194D43B5-68E8-4CBE-8927-70CE508EE9DF@nominum.com>
Content-Transfer-Encoding: 7bit
From: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: [dhcwg] Re: Rethinking autoconfig,
	was Re: prefix length determination for DHCPv6
Date: Tue, 28 Aug 2007 12:11:00 -0400
To: "dhcwg@ietf.org WG" <dhcwg@ietf.org>,
 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

On Aug 23, 2007, at 5:20 AM, Mark Smith wrote:
> I don't like doing that sort of thing, but I like that both the DHCP
> server and hosts are robust enough to handle it gracefully when I  
> do. A
> few extra packets seems to me to be a relatively small price to pay  
> for
> robustness and resilience.

I'm surprised that you would manually allocate an IPv6 address,  
although I can understand why you might do that with an IPv4  
address.   The DHCPv4 server unicasts an ICMP Echo request to verify  
the address, which acts as a first-line defense against conflicts due  
to manual allocation.   The client further ARPs for the IP address  
before using it, which acts as a second line of defense.   I'd be  
surprised if either technique was required to have a working DHCPv6  
service - the likelihood of a scarcity-induced address conflict is so  
small.



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



From dhcwg-bounces@ietf.org Wed Aug 29 02:00:10 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQGZF-0008V0-Kh; Wed, 29 Aug 2007 01:58:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQGZE-0008Us-Du
	for dhcwg@ietf.org; Wed, 29 Aug 2007 01:58:16 -0400
Received: from szxga03-in.huawei.com ([61.144.161.55])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQGZD-0005Vx-FH
	for dhcwg@ietf.org; Wed, 29 Aug 2007 01:58:16 -0400
Received: from huawei.com (szxga03-in [172.24.2.9])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JNI00GU7TVY4X@szxga03-in.huawei.com> for
	dhcwg@ietf.org; Wed, 29 Aug 2007 13:57:34 +0800 (CST)
Received: from huawei.com ([172.24.1.18])
	by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JNI0049DTVXVS@szxga03-in.huawei.com> for
	dhcwg@ietf.org; Wed, 29 Aug 2007 13:57:34 +0800 (CST)
Received: from SSK1548 ([10.18.5.107])
	by szxml03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JNI008B9TVTG8@szxml03-in.huawei.com> for
	dhcwg@ietf.org; Wed, 29 Aug 2007 13:57:33 +0800 (CST)
Date: Wed, 29 Aug 2007 11:27:28 +0530
From: "S.SenthilKumar (Huawei)" <senthilKumars@huawei.com>
To: dhcwg@ietf.org
Message-id: <000001c7ea01$7bc910f0$6b05120a@china.huawei.com>
Organization: Huawei
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: AcfqAXskoS/710jnR6etqpsX3bM1ag==
X-Spam-Score: 0.5 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: ssenthilkumar@gmail.com
Subject: [dhcwg] T1 and T2 - Valid combinations
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: senthilKumars@huawei.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

>From the client point of view , Let me know the validity of the following
combinations

T1 = 0 and T2 is Not Zero - ??
T1 = 0 and T2 is Infinity - ??

T2 = 0 and T1 is Not Zero - ??
T2 = 0 and T1 is Infinity - ??

T1 = 0 and T2 = 0 - Valid


Reference : RFC 3315 : T1 and T2 related Statements from RFC

18.1.3. Creation and Transmission of Renew Messages

If T1 or T2 is set to 0 by the server (for an IA_NA) or there are no T1 or
T2 times (for an IA_TA), the client may send a Renew or Rebind message,
respectively, at the client's discretion.


22.4. Identity Association for Non-temporary Addresses Option

 the client MUST use the values in the T1 and T2 fields for the T1 and T2
parameters, unless  those values in those fields are 0.  

If the time at which the addresses in an IA_NA are to be renewed is to be
left to the discretion of the client, the server sets T1 and T2 to 0.

If a client receives an IA_NA with T1 greater than T2, and both T1 and T2
are greater than 0, the client discards the IA_NA option and processes the
remainder of the message as though the server had not included the invalid
IA_NA option.

18.1.4. Creation and Transmission of Rebind Messages

At time T2 for an IA (which will only be reached if the server to which the
Renew message was sent at time T1 has not responded), the client initiates a
Rebind/Reply message exchange with any available server.  

Thanking you,

Best regards,
S.SenthilKumar,
Technical Project Lead, IPng,



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



From dhcwg-bounces@ietf.org Wed Aug 29 07:57:17 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQM8r-0002VI-JX; Wed, 29 Aug 2007 07:55:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQM8q-0002TV-6s
	for dhcwg@ietf.org; Wed, 29 Aug 2007 07:55:24 -0400
Received: from mx.isc.org ([2001:4f8:0:2::1c])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQM8o-0004xO-Lh
	for dhcwg@ietf.org; Wed, 29 Aug 2007 07:55:24 -0400
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "farside.isc.org", Issuer "ISC CA" (verified OK))
	by mx.isc.org (Postfix) with ESMTP id 4114E11402A;
	Wed, 29 Aug 2007 11:55:21 +0000 (UTC)
	(envelope-from Shane_Kerr@isc.org)
Received: from [192.168.1.10] (hurix.ams-ix.net [193.194.136.45])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by farside.isc.org (Postfix) with ESMTP id 6E192E6009;
	Wed, 29 Aug 2007 11:55:20 +0000 (UTC) (envelope-from shane@isc.org)
Message-ID: <46D55EA5.2020102@isc.org>
Date: Wed, 29 Aug 2007 13:55:17 +0200
From: Shane Kerr <Shane_Kerr@isc.org>
Organization: ISC
User-Agent: Thunderbird 2.0.0.6 (X11/20070806)
MIME-Version: 1.0
To: senthilKumars@huawei.com
Subject: Re: [dhcwg] T1 and T2 - Valid combinations
References: <000001c7ea01$7bc910f0$6b05120a@china.huawei.com>
In-Reply-To: <000001c7ea01$7bc910f0$6b05120a@china.huawei.com>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: ssenthilkumar@gmail.com, dhcwg@ietf.org
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

S.SenthliKumar,

I assume you are talking about what a client should do when it gets various
T1/T2 values from the server. Maybe I look at it too simply, but this is my
interpretation:

S.SenthilKumar (Huawei) wrote:
>>From the client point of view , Let me know the validity of the following
> combinations
> 
> T1 = 0 and T2 is Not Zero - ??
> T1 = 0 and T2 is Infinity - ??

Then use T2 as given by the server, and the client can pick T1.

> T2 = 0 and T1 is Not Zero - ??
> T2 = 0 and T1 is Infinity - ??

Then you use T1 as given by the server, and the client can pick T2.

> T1 = 0 and T2 = 0 - Valid

The client picks both (although in testing we found some clients that used 0).

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

iD8DBQFG1V6hMsfZxBO4kbQRAsPAAJ9nqEbuuvopVZDwPRgMXjHXRnSC/gCgtyti
My5FUXx63YXKB1QxGCh/lVU=
=+H61
-----END PGP SIGNATURE-----

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



From dhcwg-bounces@ietf.org Wed Aug 29 09:49:29 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQNtU-0004Pb-7M; Wed, 29 Aug 2007 09:47:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQNtS-0004PU-HU
	for dhcwg@ietf.org; Wed, 29 Aug 2007 09:47:38 -0400
Received: from e36.co.us.ibm.com ([32.97.110.154])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQNtR-0008Sj-5s
	for dhcwg@ietf.org; Wed, 29 Aug 2007 09:47:38 -0400
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com
	[9.17.195.227])
	by e36.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l7TDlGk0025966
	for <dhcwg@ietf.org>; Wed, 29 Aug 2007 09:47:16 -0400
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170])
	by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v8.5) with ESMTP id
	l7TDlGmf501488 for <dhcwg@ietf.org>; Wed, 29 Aug 2007 07:47:16 -0600
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1])
	by d03av04.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l7TDlGKJ019332 for <dhcwg@ietf.org>; Wed, 29 Aug 2007 07:47:16 -0600
Received: from d03nm690.boulder.ibm.com (d03nm690.boulder.ibm.com
	[9.17.195.59])
	by d03av04.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l7TDlGIo019325 for <dhcwg@ietf.org>; Wed, 29 Aug 2007 07:47:16 -0600
To: dhcwg@ietf.org
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 7.0 HF277 June 21, 2006
Message-ID: <OF7C118151.11859C39-ON87257346.004B8F86-85257346.004BDA63@us.ibm.com>
From: Theodore Vojnovich <tbvojnov@us.ibm.com>
Date: Wed, 29 Aug 2007 09:47:15 -0400
X-MIMETrack: Serialize by Router on D03NM690/03/M/IBM(Release 7.0.2HF32 |
	October 17, 2006) at 08/29/2007 07:47:15,
	Serialize complete at 08/29/2007 07:47:15
X-Spam-Score: -4.0 (----)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Subject: [dhcwg] DHCP/DNS support for FCoE
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="===============0727304060=="
Errors-To: dhcwg-bounces@ietf.org

This is a multipart message in MIME format.
--===============0727304060==
Content-Type: multipart/alternative;
	boundary="=_alternative 004BDA6185257346_="

This is a multipart message in MIME format.
--=_alternative 004BDA6185257346_=
Content-Type: text/plain; charset="US-ASCII"

Is there any work going on to look FC config via DHCP/DNS/etc for FCoE?


Thanks

Ted Vojnovich


--=_alternative 004BDA6185257346_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Is there any work going on to look FC
config via DHCP/DNS/etc for FCoE?</font>
<br>
<br><font size=2 face="sans-serif"><br>
Thanks<br>
<br>
Ted Vojnovich<br>
<br>
</font>
--=_alternative 004BDA6185257346_=--


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

--===============0727304060==--




From dhcwg-bounces@ietf.org Wed Aug 29 22:11:51 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQZTs-0004WK-UH; Wed, 29 Aug 2007 22:10:01 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQZTq-0004VE-UG
	for dhcwg@ietf.org; Wed, 29 Aug 2007 22:09:59 -0400
Received: from mailout3.samsung.com ([203.254.224.33])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQZTq-0005Vr-DM
	for dhcwg@ietf.org; Wed, 29 Aug 2007 22:09:58 -0400
Received: from ep_ms7_bk (mailout3.samsung.com [203.254.224.33])
	by mailout3.samsung.com
	(iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
	with ESMTP id <0JNK00GOKE0IKO@mailout3.samsung.com> for dhcwg@ietf.org;
	Thu, 30 Aug 2007 11:09:54 +0900 (KST)
Received: from ep_spt02 (ms7.samsung.com [203.254.225.101])
	by ms7.samsung.com (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14
	2004))
	with ESMTP id <0JNK005IRE0KHB@ms7.samsung.com> for dhcwg@ietf.org; Thu,
	30 Aug 2007 11:09:56 +0900 (KST)
Content-return: prohibited
Date: Thu, 30 Aug 2007 02:09:56 +0000 (GMT)
From: =?euc-kr?B?wvfH9r/t?= <hyunwook.cha@samsung.com>
To: dhcwg@ietf.org
Message-id: <13672784.296591188439795592.JavaMail.weblogic@ep_ml19>
MIME-version: 1.0
MIME-version: 1.0
X-Priority: 3
Msgkey: 20070830020955591@hyunwook.cha
X-MTR: 20070830020955591@hyunwook.cha
X-EPLocale: ko_KR.euc-kr
X-EPWebmail-Msg-Type: personal
X-EPWebmail-Reply-Demand: 0
X-EPApproval-Locale: 
X-Spam-Score: 2.8 (++)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: =?euc-kr?Q?=C0=D3=C6=F2=BA=F3?= <pblim@samsung.com>,
	=?euc-kr?Q?=C7=D1=B1=D9=C8=C4?= <kunhoo.han@samsung.com>,
	=?euc-kr?Q?=B1=E8=C7=F6=BE=C6?= <hanet.kim@samsung.com>
Subject: [dhcwg] Questions on dhcpv6 implementations of Microsoft Server 2008
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: hyunwook.cha@samsung.com
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0354642425=="
Errors-To: dhcwg-bounces@ietf.org

--===============0354642425==
Content-return: prohibited
Content-type: text/plain; charset=euc-kr
Content-transfer-encoding: base64

DQpEZWFyLCBhbGwuDQoNCldoaWxlIEkgb2JzZXJ2ZWQgZGhjcHY2IGNsaWVudCBhbmQgc2VydmVy
IG9mIE1pY3Jvc29mdCBTZXJ2ZXIgMjAwOCBCZXRhMywgSSBoYXZlIHNvbWUgcXVlc3Rpb25zIG9u
IGl0cyBiZWhhdmlvcnMuDQoNClNlcnZlciBzaWRlLg0KMS4gV2hlbiB0aGUgc2VydmVyIHJlY2Vp
dmVzIFJlcXVlc3Qgd2l0aG91dCBPUk8gKE9wdGlvbiBSZXF1ZXN0IE9wdGlvbiksIGl0IGdpdmVz
IG5vIFJlcGx5LiBBbHRob3VnaCBpdCByZXNwb25kcyB3aXRoIEFkdmVydGlzZW1lbnQgdG8gU29s
aWNpdCB3aXRob3V0IE9STy4gDQoNCjIuIFdoZW4gdGhlIHNlcnZlciByZWNlaXZlcyBDb25maXJt
IHdpdGggdmFsaWQgSVB2NiBhZGRyZXNzKE9uLWxpbmsgcHJlZml4KSwgaXQgcmVzcG9uZHMgd2l0
aCBSZXBseSB3aXRob3V0IGFueSBzdGF0dXMgY29kZS4gIA0KDQozLiBXaGVuIHRoZSBzZXJ2ZXIg
cmVjZWl2ZXMgQ29uZmlybSB3aXRoIGludmFsaWQgSVB2NiBhZGRyZXNzKG5vdCBvbi1saW5rIHBy
ZWZpeCksIGl0IHJlc3BvbmRzIHdpdGggUmVwbHkgd2l0aCAiTm9CaW5kaW5nIiBzdGF0dXMgY29k
ZS4gDQoNCjQuIEFmdGVyIGFuIGV4aXN0aW5nIGJpbmRpbmcgaXMgcmVtb3ZlZCwgd2hlbiB0aGUg
c2VydmVyIHJlY2VpdmVzIFJlbmV3IGZvciB0aGUgZGVsZXRlZCBiaW5kaW5nLCBpdCByZXNwb25k
cyB3aXRoIFJlcGx5IHdpdGggIk5vQmluZGluZyIgc3RhdHVzIGNvZGUgd2l0aGluIElBIGFkZHJl
c3Mgb3B0aW9uIHdoaWNoIGluY2x1ZGVzIElQdjYgYWRkcmVzcyBhbmQgbGlmZXRpbWVzIHNldCB0
byB6ZXJvLg0KSQ0KQ2xpZW50IHNpZGUuICANCjUuIFdoZW4gcGh5c2ljYWwgbGluayBvZiB0aGUg
Y2xpZW50IGhvc3QgaXMgbW92ZWQgdG8gZGlmZmVyZW50IG5ldHdvcmsgYW5kIHRoZSBjbGllbnQg
cmVjZWl2ZWQgUmVwbHkgd2l0aCAiTm90T25MaW5rIiBzdGF0dXMgY29kZSB0byBpdHMgQ29uZmly
bSwgaXQgaWdub3JlcyB0aGUgUmVwbHkgYW5kIGtlZXBzIHJlbmV3aW5nLiANCiANCjYuIFdoZW4g
cGh5c2ljYWwgbGluayBvZiB0aGUgY2xpZW50IGhvc3QgaXMgcmVjb25uZWN0ZWQgYW5kIHRoZSBj
bGllbnQgcmVjZWl2ZWQgUmVwbHkgd2l0aCAiU3VjY2VzcyIgc3RhdHVzIGNvZGUgdG8gaXRzIENv
bmZpcm0sIGl0IHNlbmRzIFNvbGljaXRzLg0KDQo3LiBXaGVuIERBRCBmYWlscyBhbmQgdGhlIGNs
aWVudCBzZW5kcyBEZWNsaW5lcyBhbmQgcmVjZWl2ZXMgUmVwbHksIGl0IHNlbmRzIG5vdCBSZXF1
ZXN0IGJ1dCBTb2xpY2l0LiANCg0KOC4gQWZ0ZXIgdGhlIGNsaWVudCBvYnRhaW5zIElQdjYgYWRk
cmVzcyBhbmQgdGhlIGhvc3QgcmVib290cywgaXQgc2VuZHMgbm90IENvbmZpcm0gYnV0IFNvbGlj
aXQuIA0KDQpUaGFuayB5b3UgZm9yIGtpbmQgcmVwbGllcyBpbiBhZHZhbmNlLiANCg0KUmVnYXJk
cywgDQoNCkpvc2VwaCBIeXVuV29vayBDaGENCg0KVGhlIHRydXRoIHdpbGwgc2V0IHlvdSBmcmVl
ICEhIQ0KDQpTb2Z0d2FyZSBFbmdpbmVlciANCkRldmVsb3BtZW50IFBhcnQgMS4gSS9JbmZyYSAg
DQpOZXR3b3JrIFN5c3RlbSBEaXZpc2lvbiANCg==




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

--===============0354642425==--



From dhcwg-bounces@ietf.org Wed Aug 29 22:21:24 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQZdB-0005Ca-4o; Wed, 29 Aug 2007 22:19:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQZd8-00051p-TC
	for dhcwg@ietf.org; Wed, 29 Aug 2007 22:19:34 -0400
Received: from zns001-0m9004.yokogawa.co.jp ([203.174.79.162])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQZd6-0002pu-Nw
	for dhcwg@ietf.org; Wed, 29 Aug 2007 22:19:34 -0400
Received: from zns001-0m9004.yokogawa.co.jp (localhost [127.0.0.1])
	by zns001-0m9004.yokogawa.co.jp (8.12.10+Sun/8.12.10) with ESMTP id
	l7U2JT73011634
	for <dhcwg@ietf.org>; Thu, 30 Aug 2007 11:19:29 +0900 (JST)
Received: from EXCHANGE03.jp.ykgw.net (zex001-0m9003.jp.ykgw.net [10.0.11.23])
	by zns001-0m9004.yokogawa.co.jp (8.12.10+Sun/8.12.10) with ESMTP id
	l7U2JSAW011625
	for <dhcwg@ietf.org>; Thu, 30 Aug 2007 11:19:29 +0900 (JST)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 30 Aug 2007 11:19:27 +0900
Message-ID: <0260031F55435342859BFB2CCA6773D81B898C3B@EXCHANGE03.jp.ykgw.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: How should a client behave when the client get two addresses?
Thread-Index: AcfqrC8AeGk4IUacR8OYiLtTHPplNA==
From: <Hideshi.Enokihara@jp.yokogawa.com>
To: <dhcwg@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Subject: [dhcwg] How should a client behave when the client get two
	addresses?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

Hi all,

Thank you for your valuable comments to my questions all the time.

I have a question in a situation that DHCPv6 client want to get two
addresses from DHCPv6 server.
I think that there are two ways to do this.

One way is to use two IA_Address options in one IA_NA option.
Another one way is to use two IA_NA options.

What is difference between these two ways?
And which way is usually used in the case of getting two addresses.

Thank you for your cooperation!

Best regards,
Hideshi

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



From dhcwg-bounces@ietf.org Wed Aug 29 23:58:02 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQb8b-0005FY-AG; Wed, 29 Aug 2007 23:56:09 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQb8a-0005Dw-5B
	for dhcwg@ietf.org; Wed, 29 Aug 2007 23:56:08 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQb8Z-0008QE-Pl
	for dhcwg@ietf.org; Wed, 29 Aug 2007 23:56:08 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 29 Aug 2007 23:56:08 -0400
X-IronPort-AV: i="4.19,323,1183348800"; 
	d="scan'208"; a="69514531:sNHT58511360"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7U3u7n7009256; 
	Wed, 29 Aug 2007 23:56:07 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7U3u7Ln029544; 
	Thu, 30 Aug 2007 03:56:07 GMT
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 29 Aug 2007 23:56:07 -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] How should a client behave when the client get
	twoaddresses?
Date: Wed, 29 Aug 2007 23:56:04 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB2104ED70D7@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <0260031F55435342859BFB2CCA6773D81B898C3B@EXCHANGE03.jp.ykgw.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] How should a client behave when the client get
	twoaddresses?
Thread-Index: AcfqrC8AeGk4IUacR8OYiLtTHPplNAADXtCA
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: <Hideshi.Enokihara@jp.yokogawa.com>, <dhcwg@ietf.org>
X-OriginalArrivalTime: 30 Aug 2007 03:56:07.0061 (UTC)
	FILETIME=[B177B450:01C7EAB9]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1546; t=1188446167;
	x=1189310167; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=volz@cisco.com;
	z=From:=20=22Bernie=20Volz=20\(volz\)=22=20<volz@cisco.com>
	|Subject:=20RE=3A=20[dhcwg]=20How=20should=20a=20client=20behave=20when=2
	0the=20client=20get=20twoaddresses? |Sender:=20
	|To:=20<Hideshi.Enokihara@jp.yokogawa.com>,=20<dhcwg@ietf.org>;
	bh=M3iFnF5t892MkGL7I5seRiC6K3PwQqMvA+8QG0JGKeU=;
	b=WnNg2Y3yAQb8mhB7pjay2DI8BeqxQdRD1/J0X22aB+NCuzACsenuzx/v5Z9+poAcX+MXX+be
	LK/oaF0ERS/dtlq5egTuSnXf10jGGbKdpaY00aZjr9Ka4cjfBazAwBuc;
Authentication-Results: rtp-dkim-2; header.From=volz@cisco.com; dkim=pass (s
	ig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: 
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Errors-To: dhcwg-bounces@ietf.org

The two IA_NA options will work (unless there are restictions at the
server to give the client only one address).

The other (two IA_Address options in one IA_NA option) is not guaranteed
to work at all. For our server, if the addresses are both 0::0, we would
give you only one address (unless the configuration had multiple
prefixes from which we are to assign addresses). If the addresses are
actual values, we MIGHT give them to you IF enabled in the configuration
AND the addresses are not otherwise in use.

So, if you have a test for this, I'd suggest the two IA_NA options. This
is the "RFC 3315" way.

- Bernie=20

-----Original Message-----
From: Hideshi.Enokihara@jp.yokogawa.com
[mailto:Hideshi.Enokihara@jp.yokogawa.com]=20
Sent: Wednesday, August 29, 2007 10:19 PM
To: dhcwg@ietf.org
Subject: [dhcwg] How should a client behave when the client get
twoaddresses?

Hi all,

Thank you for your valuable comments to my questions all the time.

I have a question in a situation that DHCPv6 client want to get two
addresses from DHCPv6 server.
I think that there are two ways to do this.

One way is to use two IA_Address options in one IA_NA option.
Another one way is to use two IA_NA options.

What is difference between these two ways?
And which way is usually used in the case of getting two addresses.

Thank you for your cooperation!

Best regards,
Hideshi

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

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



From dhcwg-bounces@ietf.org Thu Aug 30 04:17:15 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQfBR-00040F-J0; Thu, 30 Aug 2007 04:15:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQfBQ-0003zw-F5
	for dhcwg@ietf.org; Thu, 30 Aug 2007 04:15:20 -0400
Received: from mx.isc.org ([2001:4f8:0:2::1c])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQfBO-00030o-TX
	for dhcwg@ietf.org; Thu, 30 Aug 2007 04:15:20 -0400
Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "farside.isc.org", Issuer "ISC CA" (verified OK))
	by mx.isc.org (Postfix) with ESMTP id 3257B11401F;
	Thu, 30 Aug 2007 08:15:18 +0000 (UTC)
	(envelope-from Shane_Kerr@isc.org)
Received: from [199.6.1.234] (unknown [199.6.1.234])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by farside.isc.org (Postfix) with ESMTP id BF0E8E6009;
	Thu, 30 Aug 2007 08:15:16 +0000 (UTC) (envelope-from shane@isc.org)
Message-ID: <46D67C92.2090600@isc.org>
Date: Thu, 30 Aug 2007 10:15:14 +0200
From: Shane Kerr <Shane_Kerr@isc.org>
Organization: ISC
User-Agent: Thunderbird 2.0.0.6 (X11/20070806)
MIME-Version: 1.0
To: hyunwook.cha@samsung.com
Subject: Re: [dhcwg] Questions on dhcpv6 implementations of Microsoft Server
	2008
References: <13672784.296591188439795592.JavaMail.weblogic@ep_ml19>
In-Reply-To: <13672784.296591188439795592.JavaMail.weblogic@ep_ml19>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=EUC-KR
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: =?EUC-KR?B?wNPG8rrz?= <pblim@samsung.com>, dhcwg@ietf.org,
	=?EUC-KR?B?x9Gx2cjE?= <kunhoo.han@samsung.com>,
	=?EUC-KR?B?sejH9r7G?= <hanet.kim@samsung.com>
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

=C2=F7=C7=F6=BF=ED wrote:
>=20
> While I observed dhcpv6 client and server of Microsoft Server 2008 Beta=
3, I have some questions on its behaviors.
>=20
> Server side.
> 1. When the server receives Request without ORO (Option Request Option)=
, it gives no Reply. Although it responds with Advertisement to Solicit w=
ithout ORO.=20

Interesting observation. The next version of our client has changed to al=
ways
include an ORO - an empty ORO if you really don't want any options.

It's not clear from RFC 3315 whether it is legal or not to send a request=
 without an
ORO. :(

> 2. When the server receives Confirm with valid IPv6 address(On-link pre=
fix), it responds with Reply without any status code. =20

This should be okay given this (from section 22.13 of RFC 3315):

                                                                     If t=
he Status
   Code option does not appear in a message in which the option could
   appear, the status of the message is assumed to be Success.

> 3. When the server receives Confirm with invalid IPv6 address(not on-li=
nk prefix), it responds with Reply with "NoBinding" status code.=20

Yup... it's a bug.

> 4. After an existing binding is removed, when the server receives Renew=
 for the deleted binding, it responds with Reply with "NoBinding" status =
code within IA address option which includes IPv6 address and lifetimes s=
et to zero.

Another bug.

> Client side. =20
> 5. When physical link of the client host is moved to different network =
and the client received Reply with "NotOnLink" status code to its Confirm=
, it ignores the Reply and keeps renewing.=20

Bug... and highly annoying! :(

> 6. When physical link of the client host is reconnected and the client =
received Reply with "Success" status code to its Confirm, it sends Solici=
ts.

The client is looking to see if there are other DHCPv6 servers on the new=
 link.
This behavior is quite okay.

> 7. When DAD fails and the client sends Declines and receives Reply, it =
sends not Request but Solicit.=20

Seems like a relatively harmless bug. Perhaps not even a bug, since it is=
 such a
rare condition (hopefully!) and RFC 3315 does not say what client s shoul=
d do
when they do detect a duplicate address, beyond sending a Decline.

> 8. After the client obtains IPv6 address and the host reboots, it sends=
 not Confirm but Solicit.=20

Well, this should be okay. Clients are not required to store their lease =
in
persistent memory are they?

- --
Shane

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

iD8DBQFG1nyNMsfZxBO4kbQRAmZHAKDXJyevDLqiV1GdZm3tEWtWm29kPACgzJhi
TDgvEyPj/wYdyrEH5aAA8C8=3D
=3DMlQx
-----END PGP SIGNATURE-----

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



From dhcwg-bounces@ietf.org Thu Aug 30 08:53:06 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQjUd-0007mu-QZ; Thu, 30 Aug 2007 08:51:27 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQjUb-0007mK-AI; Thu, 30 Aug 2007 08:51:25 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IQjUa-0007Xl-L9; Thu, 30 Aug 2007 08:51:25 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-6.cisco.com with ESMTP; 30 Aug 2007 05:51:24 -0700
X-IronPort-AV: i="4.19,325,1183359600"; 
	d="scan'208"; a="209326973:sNHT53498844"
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l7UCpOlK030008; 
	Thu, 30 Aug 2007 05:51:24 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id l7UCpE9D010317;
	Thu, 30 Aug 2007 12:51:23 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Aug 2007 08:51:14 -0400
Received: from [192.168.1.100] ([10.86.242.165]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Aug 2007 08:51:13 -0400
In-Reply-To: <7CCD07160348804497EF29E9EA5560D7024DA3E6@exchtewks2.starentnetworks.com>
References: <7CCD07160348804497EF29E9EA5560D7024DA3E6@exchtewks2.starentnetworks.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <47B81490-F3AE-4E43-80E7-683126B207F9@cisco.com>
Content-Transfer-Encoding: 7bit
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] RE: [Mip4] draft-ietf-mip4-gen-ext-03.txt
Date: Thu, 30 Aug 2007 08:51:12 -0400
To: "Chowdhury, Kuntal" <kchowdhury@starentnetworks.com>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 30 Aug 2007 12:51:13.0902 (UTC)
	FILETIME=[72A2D8E0:01C7EB04]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4176; t=1188478284;
	x=1189342284; c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rdroms@cisco.com;
	z=From:=20Ralph=20Droms=20<rdroms@cisco.com>
	|Subject:=20Re=3A=20[dhcwg]=20RE=3A=20[Mip4]=20draft-ietf-mip4-gen-ext-03
	.txt |Sender:=20;
	bh=O1AkEkn4M4uGv8XefqIXQB4iOTCEiq4x+cnhYt20mN0=;
	b=Ej1VmU++/PzCYDmfnv5v9RFJ/wb7sfI26KdqFW6Id3CHox7l34rcqOAPOWEjHQ7dzdZC0VJ8
	TnTipFL+X8EgzJuRhwOC6aa43l0LFNfWzg2ymdXH7xD1KlHQmG8Q378Md02BUfTHFy5xNUJGSf
	1c1Ov4BpJhnk0IpLvHELaB720=;
Authentication-Results: sj-dkim-1; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Cc: dhcwg@ietf.org, mip4@ietf.org,
	McCann Peter-A001034 <pete.mccann@motorola.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

Why is the use of DHCP over MIP4 a digression?  You mentioned:

* more messages
* security

Sounds to me like these issues would be worth exploring if they  
haven't been explored already.

- Ralph

On Aug 2, 2007, at Aug 2, 2007,7:00 PM, Chowdhury, Kuntal wrote:

> Hi Pete,
>
> I think the source of the confusion is the use of DHCP options. The
> initial version of this I-D did not propose to use DHCP options at  
> all.
> The proposal contained a few possible host config parameters that we
> would have defined. However, someone saw the light, and suggested that
> instead of redesigning the host config options from scratch, why  
> not we
> used the options and the format of the options carrying config info as
> defined in DHCP. It made sense; hence we decided to accept that
> approach.
>
> Now, I see that people are mixing the use of DHCP protocol with MIP4
> host config options. I think this is a digression that we should  
> avoid.
> We need to understand the scope of the I-D. It does not rule out other
> ways to do host configuration when the MN is using MIP4. It defines  
> _a_
> way that is Mobile IP specific. It is also the most efficient one from
> the number of round trips point of view.
>
> When you say that running DHCP inside MIP4 tunnel allows for a single
> protocol to be used whether the MN is at home or visiting, I have a
> question. How is it possible for the MN to fetch config info from the
> visited network when RT is negotiated and enforced at the FA?
>
> BTW, the approach specified in the draft-ietf-mip4-gen-ext-03.txt  
> allows
> the use of a single protocol i.e. MIP4 to be used to fetch config info
> from home and visited networks, not to mention with fewer number of
> messages.
>
> Another issue that we need to think about the use of DHCP inside MIP4
> tunnel is security. We cannot prohibit the MN to run DHCPINFORM only,
> right? The MN may start doing IP address config (lease and  
> release). How
> to secure these DHCP messages? If we intend to only allow the MN to  
> send
> DHCPINFORM, how do we prevent it from sending other DHCP messages?
>
> AFAIK, RFC 3118 is not widely implemented and used. Even if it is, we
> can't expect the MIP4 implementations to start implementing RFC 3118
> just to get a few config info from the home domain.
>
> Regards,
> Kuntal
>
>> -----Original Message-----
>> From: McCann Peter-A001034 [mailto:pete.mccann@motorola.com]
>> Sent: Tuesday, July 31, 2007 9:01 AM
>> To: mip4@ietf.org; dhcwg@ietf.org
>> Subject: [Mip4] draft-ietf-mip4-gen-ext-03.txt
>>
>> A question has arisen during the last call for
>> draft-ietf-mip4-gen-ext-03.txt.
>>
>> The draft includes the following text:
>>
>>     There are mechanisms
>>     such as DHCP for the mobile node to configure information from  
>> the
>>     foreign network, but not from the home network when the mobile
> node
>>     is not attached to the home network.
>>
>> However, this may not be strictly true.  In particular,
>> it might be possible to use a DHCPINFORM message through
>> the tunnel that was established with Mobile IP, thus eliminating
>> the need to encode DHCP options inside Mobile IP messages.
>> This would allow for a single configuration protocol to be
>> used whether the MN is at home or visiting.
>>
>> I think we may have touched on this question during our last
>> chartering discussion but we might not have explored all the
>> ramifications.  Please, if you have an opinion either way
>> express it now and give some background as to why you think so.
>> It is possible that we might turn this draft into a BCP-like
>> document for how to configure and run DHCP over the tunnel
>> to the home network.
>>
>> -Pete
>>
>>
>> --
>> Mip4 mailing list: Mip4@ietf.org
>>     Web interface: https://www1.ietf.org/mailman/listinfo/mip4
>>      Charter page: http://www.ietf.org/html.charters/mip4- 
>> charter.html
>> Supplemental site: http://www.mip4.org/
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg

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



From dhcwg-bounces@ietf.org Thu Aug 30 15:33:48 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQpkE-0005a2-Ln; Thu, 30 Aug 2007 15:31:58 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQpkD-0005Zw-Cv
	for dhcwg@ietf.org; Thu, 30 Aug 2007 15:31:57 -0400
Received: from relay1.mentorg.com ([192.94.38.131])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQpkC-0002sK-65
	for dhcwg@ietf.org; Thu, 30 Aug 2007 15:31:56 -0400
Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58])
	by relay1.mentorg.com with esmtp 
	id 1IQpkB-0004b0-3b from tammy_leino@mentor.com 
	for dhcwg@ietf.org; Thu, 30 Aug 2007 12:31:55 -0700
Received: from SVR-ALH-EXC-02.mgc.mentorg.com ([134.86.110.227]) by
	SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 30 Aug 2007 12:31:54 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 30 Aug 2007 14:31:53 -0500
Message-ID: <7ECEF9368E169544B43882BC98EB5D92032DA95D@SVR-ALH-EXC-02.mgc.mentorg.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: More insight on the prefix length of a DHCPv6 address offered in
	an IA_ADDR option
Thread-Index: AcfrPGxcA+IpeiveQN6qQBBiWT3GTg==
From: "Leino, Tammy" <tammy_leino@mentor.com>
To: <dhcwg@ietf.org>
X-OriginalArrivalTime: 30 Aug 2007 19:31:54.0161 (UTC)
	FILETIME=[6BBF4210:01C7EB3C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c54bc2f42d02429833c0ca4b8725abd7
Subject: [dhcwg] More insight on the prefix length of a DHCPv6 address
	offered in an IA_ADDR 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>
Content-Type: multipart/mixed; boundary="===============0271284005=="
Errors-To: dhcwg-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0271284005==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7EB3C.6B2DD731"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7EB3C.6B2DD731
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello All,

I have been testing my DHCPv6 client implementation using the phase-2 =
TAHI test suite, and I am seeing interesting behaviour that gives =
insight into how the TAHI group is interpreting on-link routing and =
prefix length in regards to RFC 3315.  When the TAHI test assigns the =
NUT a global IPv6 address, it expects the NUT to know that the prefix =
associated with that address is on link.  Here is what happens:

1 -
TAHI sends RA with link-layer addr 00:00:00:00:a6:a6 - this is =
important, as the rest of the packets are sent with a different =
link-layer address.

NUT adds Default Router with this link-layer address.

2 -
NUT invokes DHCPv6 client=20

TAHI assigns NUT IPv6 address 3ffe:501:ffff:100:2a0:7dff:fe08:1

3-
TAHI pings NUT:

source IPv6 address : 3ffe:501:ffff:100:200:ff:fe00:a1a1
source link-layer address : 00:00:00:00:a1:a1

destination address : 3ffe:501:ffff:100:2a0:7dff:fe08:1

Now, this is where things get interesting.  If I did not add a route for =
the prefix associated with the assigned address indicating that this =
prefix is on-link, the NUT will assume the destination to the echo reply =
is off-link and send the packet through the router.  When this happens, =
TAHI does not recognize receipt of this echo reply packet since it is =
sent to link-layer address 00:00:00:00:a6:a6 instead of =
00:00:00:00:a1:a1.  TAHI requires that the packet be sent to the =
link-layer address that sent the request; therefore, the NUT must know =
that the source is on-link and that the prefix associated with the =
address assigned by the DHCPv6 server is on-link.

I was previously using a prefix length of 128 for an address assigned =
through DHCPv6, per suggestions received on a previous thread, but now I =
am using 64.

I'm not trying to open a can of worms again here.  I just wanted to =
share my observations with the group.

Best Regards,
Tammy Leino


------_=_NextPart_001_01C7EB3C.6B2DD731
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>More insight on the prefix length of a DHCPv6 address offered in =
an IA_ADDR option</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">Hello All,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I have been testing my DHCPv6 client =
implementation using the phase-2 TAHI test suite, and I am seeing =
interesting behaviour that gives insight into how the TAHI group is =
interpreting on-link routing and prefix length in regards to RFC =
3315.&nbsp; When the TAHI test assigns the NUT a global IPv6 address, it =
expects the NUT to know that the prefix associated with that address is =
on link.&nbsp; Here is what happens:</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">1 -</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">TAHI sends RA with link-layer addr =
00:00:00:00:a6:a6 - this is important, as the rest of the packets are =
sent with a different link-layer address.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">NUT adds Default Router with this =
link-layer address.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">2 -</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">NUT invokes DHCPv6 client </FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">TAHI assigns NUT IPv6 address =
3ffe:501:ffff:100:2a0:7dff:fe08:1</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">3-</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">TAHI pings NUT:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">source IPv6 address : =
3ffe:501:ffff:100:200:ff:fe00:a1a1</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">source link-layer address : =
00:00:00:00:a1:a1</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">destination address : =
3ffe:501:ffff:100:2a0:7dff:fe08:1</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Now, this is where things get =
interesting.&nbsp; If I did not add a route for the prefix associated =
with the assigned address indicating that this prefix is on-link, the =
NUT will assume the destination to the echo reply is off-link and send =
the packet through the router.&nbsp; When this happens, TAHI does not =
recognize receipt of this echo reply packet since it is sent to =
link-layer address 00:00:00:00:a6:a6 instead of 00:00:00:00:a1:a1.&nbsp; =
TAHI requires that the packet be sent to the link-layer address that =
sent the request; therefore, the NUT must know that the source is =
on-link and that the prefix associated with the address assigned by the =
DHCPv6 server is on-link.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I was previously using a prefix length =
of 128 for an address assigned through DHCPv6, per suggestions received =
on a previous thread, but now I am using 64.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I'm not trying to open a can of worms =
again here.&nbsp; I just wanted to share my observations with the =
group.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Best Regards,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Tammy Leino</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7EB3C.6B2DD731--


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

--===============0271284005==--




From dhcwg-bounces@ietf.org Thu Aug 30 15:47:36 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQpxe-0001VJ-Gm; Thu, 30 Aug 2007 15:45:50 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQpxd-0001QT-6D
	for dhcwg@ietf.org; Thu, 30 Aug 2007 15:45:49 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQpxc-0003Hu-NG
	for dhcwg@ietf.org; Thu, 30 Aug 2007 15:45:49 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 30 Aug 2007 15:45:48 -0400
X-IronPort-AV: i="4.19,327,1183348800"; 
	d="scan'208"; a="130512870:sNHT51236188"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7UJjmxE005589; 
	Thu, 30 Aug 2007 15:45:48 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7UJjhLr009811; 
	Thu, 30 Aug 2007 19:45:44 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Aug 2007 15:45:41 -0400
Received: from [192.168.1.100] ([10.86.242.165]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Aug 2007 15:45:40 -0400
In-Reply-To: <7ECEF9368E169544B43882BC98EB5D92032DA95D@SVR-ALH-EXC-02.mgc.mentorg.com>
References: <7ECEF9368E169544B43882BC98EB5D92032DA95D@SVR-ALH-EXC-02.mgc.mentorg.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <91F0DB78-2E78-4A54-B9B6-5270736BD53E@cisco.com>
Content-Transfer-Encoding: 7bit
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] More insight on the prefix length of a DHCPv6 address
	offered in an IA_ADDR option
Date: Thu, 30 Aug 2007 15:45:38 -0400
To: "Leino, Tammy" <tammy_leino@mentor.com>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 30 Aug 2007 19:45:40.0961 (UTC)
	FILETIME=[588EED10:01C7EB3E]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2367; t=1188503148;
	x=1189367148; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rdroms@cisco.com;
	z=From:=20Ralph=20Droms=20<rdroms@cisco.com>
	|Subject:=20Re=3A=20[dhcwg]=20More=20insight=20on=20the=20prefix=20length
	=20of=20a=20DHCPv6=20address=20offered=20in=20an=20IA_ADDR=20option
	|Sender:=20
	|To:=20=22Leino,=20Tammy=22=20<tammy_leino@mentor.com>;
	bh=opJ15NrbrZUiCvQwx33C/7zO98nCxUiBotTbpCTPt/U=;
	b=mt1onyb+gxLGBUB21bj1mi8uG4c/szBpBl6S8vVmdadmAbMca8uhlSLbFEvSXlM0XeFt3sJO
	RAiADNUZltKe57wqNVEtZ4N962HJg71FbhZvErbQqC+jiafLvrsDmo0U;
Authentication-Results: rtp-dkim-2; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
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

Tammy - are there any prefix information options in the RA sent by  
the TAHI test suite in step 1?

- Ralph

On Aug 30, 2007, at Aug 30, 2007,3:31 PM, Leino, Tammy wrote:

> Hello All,
>
> I have been testing my DHCPv6 client implementation using the  
> phase-2 TAHI test suite, and I am seeing interesting behaviour that  
> gives insight into how the TAHI group is interpreting on-link  
> routing and prefix length in regards to RFC 3315.  When the TAHI  
> test assigns the NUT a global IPv6 address, it expects the NUT to  
> know that the prefix associated with that address is on link.  Here  
> is what happens:
>
> 1 -
> TAHI sends RA with link-layer addr 00:00:00:00:a6:a6 - this is  
> important, as the rest of the packets are sent with a different  
> link-layer address.
>
> NUT adds Default Router with this link-layer address.
>
> 2 -
> NUT invokes DHCPv6 client
>
> TAHI assigns NUT IPv6 address 3ffe:501:ffff:100:2a0:7dff:fe08:1
>
> 3-
> TAHI pings NUT:
>
> source IPv6 address : 3ffe:501:ffff:100:200:ff:fe00:a1a1
> source link-layer address : 00:00:00:00:a1:a1
>
> destination address : 3ffe:501:ffff:100:2a0:7dff:fe08:1
>
> Now, this is where things get interesting.  If I did not add a  
> route for the prefix associated with the assigned address  
> indicating that this prefix is on-link, the NUT will assume the  
> destination to the echo reply is off-link and send the packet  
> through the router.  When this happens, TAHI does not recognize  
> receipt of this echo reply packet since it is sent to link-layer  
> address 00:00:00:00:a6:a6 instead of 00:00:00:00:a1:a1.  TAHI  
> requires that the packet be sent to the link-layer address that  
> sent the request; therefore, the NUT must know that the source is  
> on-link and that the prefix associated with the address assigned by  
> the DHCPv6 server is on-link.
>
> I was previously using a prefix length of 128 for an address  
> assigned through DHCPv6, per suggestions received on a previous  
> thread, but now I am using 64.
>
> I'm not trying to open a can of worms again here.  I just wanted to  
> share my observations with the group.
>
> Best Regards,
> Tammy Leino
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg

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



From dhcwg-bounces@ietf.org Thu Aug 30 15:54:38 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQq4T-0000I8-Fd; Thu, 30 Aug 2007 15:52:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQq4R-0000A1-Uh
	for dhcwg@ietf.org; Thu, 30 Aug 2007 15:52:51 -0400
Received: from relay1.mentorg.com ([192.94.38.131])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQq4Q-0005oL-DP
	for dhcwg@ietf.org; Thu, 30 Aug 2007 15:52:51 -0400
Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58])
	by relay1.mentorg.com with esmtp 
	id 1IQq4P-00063P-Ms from tammy_leino@mentor.com ;
	Thu, 30 Aug 2007 12:52:49 -0700
Received: from SVR-ALH-EXC-02.mgc.mentorg.com ([134.86.110.227]) by
	SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 30 Aug 2007 12:52:49 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] More insight on the prefix length of a DHCPv6 address
	offered in an IA_ADDR option
Date: Thu, 30 Aug 2007 14:52:47 -0500
Message-ID: <7ECEF9368E169544B43882BC98EB5D92032DA95E@SVR-ALH-EXC-02.mgc.mentorg.com>
In-Reply-To: <91F0DB78-2E78-4A54-B9B6-5270736BD53E@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] More insight on the prefix length of a DHCPv6 address
	offered in an IA_ADDR option
Thread-Index: AcfrPmILkRCh50vDQbyizzEqe/X+cgAAJMTg
From: "Leino, Tammy" <tammy_leino@mentor.com>
To: "Ralph Droms" <rdroms@cisco.com>
X-OriginalArrivalTime: 30 Aug 2007 19:52:49.0028 (UTC)
	FILETIME=[57B4C440:01C7EB3F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
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

Hi Ralph,

Yes, there is one prefix option in the RA that corresponds to the
address that will be assigned later by the DHCP server, but part of the
test is to ignore the prefix info option of the RA since the auto flag
is not set.  Should I be "remembering" the prefix length of this prefix
option even though I am not permitted to assign this prefix to the node?

Best Regards,
Tammy


-----Original Message-----
From: Ralph Droms [mailto:rdroms@cisco.com]
Sent: Thursday, August 30, 2007 3:46 PM
To: Leino, Tammy
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] More insight on the prefix length of a DHCPv6
address offered in an IA_ADDR option


Tammy - are there any prefix information options in the RA sent by =20
the TAHI test suite in step 1?

- Ralph

On Aug 30, 2007, at Aug 30, 2007,3:31 PM, Leino, Tammy wrote:

> Hello All,
>
> I have been testing my DHCPv6 client implementation using the =20
> phase-2 TAHI test suite, and I am seeing interesting behaviour that =20
> gives insight into how the TAHI group is interpreting on-link =20
> routing and prefix length in regards to RFC 3315.  When the TAHI =20
> test assigns the NUT a global IPv6 address, it expects the NUT to =20
> know that the prefix associated with that address is on link.  Here =20
> is what happens:
>
> 1 -
> TAHI sends RA with link-layer addr 00:00:00:00:a6:a6 - this is =20
> important, as the rest of the packets are sent with a different =20
> link-layer address.
>
> NUT adds Default Router with this link-layer address.
>
> 2 -
> NUT invokes DHCPv6 client
>
> TAHI assigns NUT IPv6 address 3ffe:501:ffff:100:2a0:7dff:fe08:1
>
> 3-
> TAHI pings NUT:
>
> source IPv6 address : 3ffe:501:ffff:100:200:ff:fe00:a1a1
> source link-layer address : 00:00:00:00:a1:a1
>
> destination address : 3ffe:501:ffff:100:2a0:7dff:fe08:1
>
> Now, this is where things get interesting.  If I did not add a =20
> route for the prefix associated with the assigned address =20
> indicating that this prefix is on-link, the NUT will assume the =20
> destination to the echo reply is off-link and send the packet =20
> through the router.  When this happens, TAHI does not recognize =20
> receipt of this echo reply packet since it is sent to link-layer =20
> address 00:00:00:00:a6:a6 instead of 00:00:00:00:a1:a1.  TAHI =20
> requires that the packet be sent to the link-layer address that =20
> sent the request; therefore, the NUT must know that the source is =20
> on-link and that the prefix associated with the address assigned by =20
> the DHCPv6 server is on-link.
>
> I was previously using a prefix length of 128 for an address =20
> assigned through DHCPv6, per suggestions received on a previous =20
> thread, but now I am using 64.
>
> I'm not trying to open a can of worms again here.  I just wanted to =20
> share my observations with the group.
>
> Best Regards,
> Tammy Leino
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg

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



From dhcwg-bounces@ietf.org Thu Aug 30 16:13:40 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQqMt-0001ur-If; Thu, 30 Aug 2007 16:11:55 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQqMs-0001ul-Oo
	for dhcwg@ietf.org; Thu, 30 Aug 2007 16:11:54 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQqMs-0003yQ-6N
	for dhcwg@ietf.org; Thu, 30 Aug 2007 16:11:54 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 30 Aug 2007 16:11:53 -0400
X-IronPort-AV: i="4.19,327,1183348800"; 
	d="scan'208"; a="69643563:sNHT54335754"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7UKBrt4031804; 
	Thu, 30 Aug 2007 16:11:53 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7UKBcM9026232; 
	Thu, 30 Aug 2007 20:11:53 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Aug 2007 16:11:39 -0400
Received: from [192.168.1.100] ([10.86.242.165]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Aug 2007 16:11:38 -0400
In-Reply-To: <7ECEF9368E169544B43882BC98EB5D92032DA95E@SVR-ALH-EXC-02.mgc.mentorg.com>
References: <7ECEF9368E169544B43882BC98EB5D92032DA95E@SVR-ALH-EXC-02.mgc.mentorg.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <524684AB-3550-4A23-A2B1-2A0C0E39EB7D@cisco.com>
Content-Transfer-Encoding: 7bit
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] More insight on the prefix length of a DHCPv6 address
	offered in an IA_ADDR option
Date: Thu, 30 Aug 2007 16:11:34 -0400
To: "Leino, Tammy" <tammy_leino@mentor.com>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 30 Aug 2007 20:11:38.0623 (UTC)
	FILETIME=[F8FF48F0:01C7EB41]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=3595; t=1188504713;
	x=1189368713; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rdroms@cisco.com;
	z=From:=20Ralph=20Droms=20<rdroms@cisco.com>
	|Subject:=20Re=3A=20[dhcwg]=20More=20insight=20on=20the=20prefix=20length
	=20of=20a=20DHCPv6=20address=20offered=20in=20an=20IA_ADDR=20option
	|Sender:=20
	|To:=20=22Leino,=20Tammy=22=20<tammy_leino@mentor.com>;
	bh=Le7+z5tMrOnIjQXbTXPASNOvzEkf8idNKR4cipAczg4=;
	b=JLzFfmhW2NenQRrZ8fp0/uAM6n2B8UBdirbwyQfkBmzD3ONWe/FWwEPjVukQePiJr0jcVaxp
	VSgazdejWi32fWar2KiXNo/K1S7Pe555ZUT0L9vIAGBeL8YHmGsHxgtL;
Authentication-Results: rtp-dkim-2; header.From=rdroms@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
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

Tammy - my understanding of RFC 2461 is that the stack should install  
that advertised prefix in the Prefix List as an on-link prefix, even  
if the A bit is not set.  With the prefix in the Prefix List, the  
host should consider the prefix and the source of the ping to be on- 
link, and deliver the response to:

IPv6 address : 3ffe:501:ffff:100:200:ff:fe00:a1a1
link-layer address : 00:00:00:00:a1:a1

- Ralph

On Aug 30, 2007, at Aug 30, 2007,3:52 PM, Leino, Tammy wrote:

> Hi Ralph,
>
> Yes, there is one prefix option in the RA that corresponds to the
> address that will be assigned later by the DHCP server, but part of  
> the
> test is to ignore the prefix info option of the RA since the auto flag
> is not set.  Should I be "remembering" the prefix length of this  
> prefix
> option even though I am not permitted to assign this prefix to the  
> node?
>
> Best Regards,
> Tammy
>
>
> -----Original Message-----
> From: Ralph Droms [mailto:rdroms@cisco.com]
> Sent: Thursday, August 30, 2007 3:46 PM
> To: Leino, Tammy
> Cc: dhcwg@ietf.org
> Subject: Re: [dhcwg] More insight on the prefix length of a DHCPv6
> address offered in an IA_ADDR option
>
>
> Tammy - are there any prefix information options in the RA sent by
> the TAHI test suite in step 1?
>
> - Ralph
>
> On Aug 30, 2007, at Aug 30, 2007,3:31 PM, Leino, Tammy wrote:
>
>> Hello All,
>>
>> I have been testing my DHCPv6 client implementation using the
>> phase-2 TAHI test suite, and I am seeing interesting behaviour that
>> gives insight into how the TAHI group is interpreting on-link
>> routing and prefix length in regards to RFC 3315.  When the TAHI
>> test assigns the NUT a global IPv6 address, it expects the NUT to
>> know that the prefix associated with that address is on link.  Here
>> is what happens:
>>
>> 1 -
>> TAHI sends RA with link-layer addr 00:00:00:00:a6:a6 - this is
>> important, as the rest of the packets are sent with a different
>> link-layer address.
>>
>> NUT adds Default Router with this link-layer address.
>>
>> 2 -
>> NUT invokes DHCPv6 client
>>
>> TAHI assigns NUT IPv6 address 3ffe:501:ffff:100:2a0:7dff:fe08:1
>>
>> 3-
>> TAHI pings NUT:
>>
>> source IPv6 address : 3ffe:501:ffff:100:200:ff:fe00:a1a1
>> source link-layer address : 00:00:00:00:a1:a1
>>
>> destination address : 3ffe:501:ffff:100:2a0:7dff:fe08:1
>>
>> Now, this is where things get interesting.  If I did not add a
>> route for the prefix associated with the assigned address
>> indicating that this prefix is on-link, the NUT will assume the
>> destination to the echo reply is off-link and send the packet
>> through the router.  When this happens, TAHI does not recognize
>> receipt of this echo reply packet since it is sent to link-layer
>> address 00:00:00:00:a6:a6 instead of 00:00:00:00:a1:a1.  TAHI
>> requires that the packet be sent to the link-layer address that
>> sent the request; therefore, the NUT must know that the source is
>> on-link and that the prefix associated with the address assigned by
>> the DHCPv6 server is on-link.
>>
>> I was previously using a prefix length of 128 for an address
>> assigned through DHCPv6, per suggestions received on a previous
>> thread, but now I am using 64.
>>
>> I'm not trying to open a can of worms again here.  I just wanted to
>> share my observations with the group.
>>
>> Best Regards,
>> Tammy Leino
>>
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www1.ietf.org/mailman/listinfo/dhcwg

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



From dhcwg-bounces@ietf.org Thu Aug 30 16:19:09 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQqSC-0001T4-Ov; Thu, 30 Aug 2007 16:17:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQqSB-0001Ss-NR
	for dhcwg@ietf.org; Thu, 30 Aug 2007 16:17:23 -0400
Received: from relay1.mentorg.com ([192.94.38.131])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQqSA-0006Lf-FF
	for dhcwg@ietf.org; Thu, 30 Aug 2007 16:17:23 -0400
Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58])
	by relay1.mentorg.com with esmtp 
	id 1IQqSA-0007ZU-10 from tammy_leino@mentor.com ;
	Thu, 30 Aug 2007 13:17:22 -0700
Received: from SVR-ALH-EXC-02.mgc.mentorg.com ([134.86.110.227]) by
	SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 30 Aug 2007 13:17:21 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] More insight on the prefix length of a DHCPv6 address
	offered in an IA_ADDR option
Date: Thu, 30 Aug 2007 15:17:20 -0500
Message-ID: <7ECEF9368E169544B43882BC98EB5D92032DA95F@SVR-ALH-EXC-02.mgc.mentorg.com>
In-Reply-To: <524684AB-3550-4A23-A2B1-2A0C0E39EB7D@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] More insight on the prefix length of a DHCPv6 address
	offered in an IA_ADDR option
Thread-Index: AcfrQhXTvZJHzWXQS8a00cJV3bH88gAADSxw
From: "Leino, Tammy" <tammy_leino@mentor.com>
To: "Ralph Droms" <rdroms@cisco.com>
X-OriginalArrivalTime: 30 Aug 2007 20:17:21.0171 (UTC)
	FILETIME=[C52BF630:01C7EB42]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
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

Thanks Ralph.

I should be adding a route for this prefix when I get the RA, just not
creating an address from the prefix.  This sheds some light on comments
made by other members of the list a couple weeks ago that made no sense
then!

Many thanks for the clarification!

Best Regards,
Tammy



-----Original Message-----
From: Ralph Droms [mailto:rdroms@cisco.com]
Sent: Thursday, August 30, 2007 4:12 PM
To: Leino, Tammy
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] More insight on the prefix length of a DHCPv6
address offered in an IA_ADDR option


Tammy - my understanding of RFC 2461 is that the stack should install =20
that advertised prefix in the Prefix List as an on-link prefix, even =20
if the A bit is not set.  With the prefix in the Prefix List, the =20
host should consider the prefix and the source of the ping to be on-=20
link, and deliver the response to:

IPv6 address : 3ffe:501:ffff:100:200:ff:fe00:a1a1
link-layer address : 00:00:00:00:a1:a1

- Ralph

On Aug 30, 2007, at Aug 30, 2007,3:52 PM, Leino, Tammy wrote:

> Hi Ralph,
>
> Yes, there is one prefix option in the RA that corresponds to the
> address that will be assigned later by the DHCP server, but part of =20
> the
> test is to ignore the prefix info option of the RA since the auto flag
> is not set.  Should I be "remembering" the prefix length of this =20
> prefix
> option even though I am not permitted to assign this prefix to the =20
> node?
>
> Best Regards,
> Tammy
>
>
> -----Original Message-----
> From: Ralph Droms [mailto:rdroms@cisco.com]
> Sent: Thursday, August 30, 2007 3:46 PM
> To: Leino, Tammy
> Cc: dhcwg@ietf.org
> Subject: Re: [dhcwg] More insight on the prefix length of a DHCPv6
> address offered in an IA_ADDR option
>
>
> Tammy - are there any prefix information options in the RA sent by
> the TAHI test suite in step 1?
>
> - Ralph
>
> On Aug 30, 2007, at Aug 30, 2007,3:31 PM, Leino, Tammy wrote:
>
>> Hello All,
>>
>> I have been testing my DHCPv6 client implementation using the
>> phase-2 TAHI test suite, and I am seeing interesting behaviour that
>> gives insight into how the TAHI group is interpreting on-link
>> routing and prefix length in regards to RFC 3315.  When the TAHI
>> test assigns the NUT a global IPv6 address, it expects the NUT to
>> know that the prefix associated with that address is on link.  Here
>> is what happens:
>>
>> 1 -
>> TAHI sends RA with link-layer addr 00:00:00:00:a6:a6 - this is
>> important, as the rest of the packets are sent with a different
>> link-layer address.
>>
>> NUT adds Default Router with this link-layer address.
>>
>> 2 -
>> NUT invokes DHCPv6 client
>>
>> TAHI assigns NUT IPv6 address 3ffe:501:ffff:100:2a0:7dff:fe08:1
>>
>> 3-
>> TAHI pings NUT:
>>
>> source IPv6 address : 3ffe:501:ffff:100:200:ff:fe00:a1a1
>> source link-layer address : 00:00:00:00:a1:a1
>>
>> destination address : 3ffe:501:ffff:100:2a0:7dff:fe08:1
>>
>> Now, this is where things get interesting.  If I did not add a
>> route for the prefix associated with the assigned address
>> indicating that this prefix is on-link, the NUT will assume the
>> destination to the echo reply is off-link and send the packet
>> through the router.  When this happens, TAHI does not recognize
>> receipt of this echo reply packet since it is sent to link-layer
>> address 00:00:00:00:a6:a6 instead of 00:00:00:00:a1:a1.  TAHI
>> requires that the packet be sent to the link-layer address that
>> sent the request; therefore, the NUT must know that the source is
>> on-link and that the prefix associated with the address assigned by
>> the DHCPv6 server is on-link.
>>
>> I was previously using a prefix length of 128 for an address
>> assigned through DHCPv6, per suggestions received on a previous
>> thread, but now I am using 64.
>>
>> I'm not trying to open a can of worms again here.  I just wanted to
>> share my observations with the group.
>>
>> Best Regards,
>> Tammy Leino
>>
>> _______________________________________________
>> dhcwg mailing list
>> dhcwg@ietf.org
>> https://www1.ietf.org/mailman/listinfo/dhcwg

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



From dhcwg-bounces@ietf.org Thu Aug 30 16:32:39 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQqfF-0003LZ-W7; Thu, 30 Aug 2007 16:30:53 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQqfE-0003LR-MH
	for dhcwg@ietf.org; Thu, 30 Aug 2007 16:30:52 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQqfD-0004Sd-6q
	for dhcwg@ietf.org; Thu, 30 Aug 2007 16:30:52 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-2.cisco.com with ESMTP; 30 Aug 2007 16:30:51 -0400
X-IronPort-AV: i="4.19,327,1183348800"; 
	d="scan'208,217"; a="130522420:sNHT93637032"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l7UKUoZ1013309; 
	Thu, 30 Aug 2007 16:30:50 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7UKUXML005936; 
	Thu, 30 Aug 2007 20:30:50 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Aug 2007 16:30:45 -0400
Received: from [161.44.65.208] ([161.44.65.208]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Aug 2007 16:30:45 -0400
Message-ID: <46D728F4.3020500@cisco.com>
Date: Thu, 30 Aug 2007 16:30:44 -0400
From: Josh Littlefield <joshl@cisco.com>
Organization: Cisco Systems
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Leino, Tammy" <tammy_leino@mentor.com>
Subject: Re: [dhcwg] More insight on the prefix length of a DHCPv6 address
	offered in an IA_ADDR option
References: <7ECEF9368E169544B43882BC98EB5D92032DA95F@SVR-ALH-EXC-02.mgc.mentorg.com>
In-Reply-To: <7ECEF9368E169544B43882BC98EB5D92032DA95F@SVR-ALH-EXC-02.mgc.mentorg.com>
X-Enigmail-Version: 0.95.3
X-OriginalArrivalTime: 30 Aug 2007 20:30:45.0132 (UTC)
	FILETIME=[A45EACC0:01C7EB44]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=15482; t=1188505850;
	x=1189369850; c=relaxed/simple; s=rtpdkim2001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=joshl@cisco.com;
	z=From:=20Josh=20Littlefield=20<joshl@cisco.com>
	|Subject:=20Re=3A=20[dhcwg]=20More=20insight=20on=20the=20prefix=20length
	=20of=20a=20DHCPv6=20address=0A=20offered=20in=20an=20IA_ADDR=20option
	|Sender:=20
	|To:=20=22Leino,=20Tammy=22=20<tammy_leino@mentor.com>;
	bh=N/OCNFbQMLta59Ssmj9bwe+Nzi5BHJJ9STT2Sh7owMk=;
	b=E0gQRX26Vqoif04GfuZvErguT7d+/mc5X95/ql8hqmAFntfNtC9wARKacIHtmrhEzgheHJRl
	gBy4yNkakAZ4HKB4HxnO1gDlGZVTuXTdqSYogyhkZWnBYv4valzWHEJP;
Authentication-Results: rtp-dkim-2; header.From=joshl@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd3d702b63698072ba67a75ce9e0fc9e
Cc: dhcwg@ietf.org, Ralph Droms <rdroms@cisco.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0392327503=="
Errors-To: dhcwg-bounces@ietf.org

This is a multi-part message in MIME format.
--===============0392327503==
Content-Type: multipart/alternative;
	boundary="------------000602000700040101010906"

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

Tammy, I think Ralph was making the assumption that the 'L' bit was set
in the advertised prefixes in the RA.

RFC 2461, sec. 6 (Router and Prefix Discovery) describes the two
independent uses of prefix options:

   Prefix Discovery is the process through which hosts learn the ranges
   of IP addresses that reside on-link and can be reached directly
   without going through a router.  Routers send Router Advertisements
   that indicate whether the sender is willing to be a default router.
   Router Advertisements also contain Prefix Information options that
   list the set of prefixes that identify on-link IP addresses.

   Stateless Address Autoconfiguration must also obtain subnet prefixes
   as part of configuring addresses.  Although the prefixes used for
   address autoconfiguration are logically distinct from those used for
   on-link determination, autoconfiguration information is piggybacked
   on Router Discovery messages to reduce network traffic.  Indeed, the
   same prefixes can be advertised for on-link determination and address
   autoconfiguration by specifying the appropriate flags in the Prefix
   Information options.  See [ADDRCONF] for details on how
   autoconfiguration information is processed.


In sec. 6.3.4 it goes on to say:

   For each Prefix Information option with the on-link flag set, a host
   does the following:

      - If the prefix is the link-local prefix, silently ignore the
        Prefix Information option.

      - If the prefix is not already present in the Prefix List, and the
        Prefix Information option's Valid Lifetime field is non-zero,
        create a new entry for the prefix and initialize its
        invalidation timer to the Valid Lifetime value in the Prefix
        Information option.

      - If the prefix is already present in the host's Prefix List as
        the result of a previously-received advertisement, reset its
        invalidation timer to the Valid Lifetime value in the Prefix
        Information option.  If the new Lifetime value is zero, time-out
        the prefix immediately (see Section 6.3.5).

      - If the Prefix Information option's Valid Lifetime field is zero,
        and the prefix is not present in the host's Prefix List,
        silently ignore the option.




Leino, Tammy wrote:
> Thanks Ralph.
>
> I should be adding a route for this prefix when I get the RA, just not
> creating an address from the prefix.  This sheds some light on comments
> made by other members of the list a couple weeks ago that made no sense
> then!
>
> Many thanks for the clarification!
>
> Best Regards,
> Tammy
>
>
>
> -----Original Message-----
> From: Ralph Droms [mailto:rdroms@cisco.com]
> Sent: Thursday, August 30, 2007 4:12 PM
> To: Leino, Tammy
> Cc: dhcwg@ietf.org
> Subject: Re: [dhcwg] More insight on the prefix length of a DHCPv6
> address offered in an IA_ADDR option
>
>
> Tammy - my understanding of RFC 2461 is that the stack should install  
> that advertised prefix in the Prefix List as an on-link prefix, even  
> if the A bit is not set.  With the prefix in the Prefix List, the  
> host should consider the prefix and the source of the ping to be on- 
> link, and deliver the response to:
>
> IPv6 address : 3ffe:501:ffff:100:200:ff:fe00:a1a1
> link-layer address : 00:00:00:00:a1:a1
>
> - Ralph
>
> On Aug 30, 2007, at Aug 30, 2007,3:52 PM, Leino, Tammy wrote:
>
>   
>> Hi Ralph,
>>
>> Yes, there is one prefix option in the RA that corresponds to the
>> address that will be assigned later by the DHCP server, but part of  
>> the
>> test is to ignore the prefix info option of the RA since the auto flag
>> is not set.  Should I be "remembering" the prefix length of this  
>> prefix
>> option even though I am not permitted to assign this prefix to the  
>> node?
>>
>> Best Regards,
>> Tammy
>>
>>
>> -----Original Message-----
>> From: Ralph Droms [mailto:rdroms@cisco.com]
>> Sent: Thursday, August 30, 2007 3:46 PM
>> To: Leino, Tammy
>> Cc: dhcwg@ietf.org
>> Subject: Re: [dhcwg] More insight on the prefix length of a DHCPv6
>> address offered in an IA_ADDR option
>>
>>
>> Tammy - are there any prefix information options in the RA sent by
>> the TAHI test suite in step 1?
>>
>> - Ralph
>>
>> On Aug 30, 2007, at Aug 30, 2007,3:31 PM, Leino, Tammy wrote:
>>
>>     
>>> Hello All,
>>>
>>> I have been testing my DHCPv6 client implementation using the
>>> phase-2 TAHI test suite, and I am seeing interesting behaviour that
>>> gives insight into how the TAHI group is interpreting on-link
>>> routing and prefix length in regards to RFC 3315.  When the TAHI
>>> test assigns the NUT a global IPv6 address, it expects the NUT to
>>> know that the prefix associated with that address is on link.  Here
>>> is what happens:
>>>
>>> 1 -
>>> TAHI sends RA with link-layer addr 00:00:00:00:a6:a6 - this is
>>> important, as the rest of the packets are sent with a different
>>> link-layer address.
>>>
>>> NUT adds Default Router with this link-layer address.
>>>
>>> 2 -
>>> NUT invokes DHCPv6 client
>>>
>>> TAHI assigns NUT IPv6 address 3ffe:501:ffff:100:2a0:7dff:fe08:1
>>>
>>> 3-
>>> TAHI pings NUT:
>>>
>>> source IPv6 address : 3ffe:501:ffff:100:200:ff:fe00:a1a1
>>> source link-layer address : 00:00:00:00:a1:a1
>>>
>>> destination address : 3ffe:501:ffff:100:2a0:7dff:fe08:1
>>>
>>> Now, this is where things get interesting.  If I did not add a
>>> route for the prefix associated with the assigned address
>>> indicating that this prefix is on-link, the NUT will assume the
>>> destination to the echo reply is off-link and send the packet
>>> through the router.  When this happens, TAHI does not recognize
>>> receipt of this echo reply packet since it is sent to link-layer
>>> address 00:00:00:00:a6:a6 instead of 00:00:00:00:a1:a1.  TAHI
>>> requires that the packet be sent to the link-layer address that
>>> sent the request; therefore, the NUT must know that the source is
>>> on-link and that the prefix associated with the address assigned by
>>> the DHCPv6 server is on-link.
>>>
>>> I was previously using a prefix length of 128 for an address
>>> assigned through DHCPv6, per suggestions received on a previous
>>> thread, but now I am using 64.
>>>
>>> I'm not trying to open a can of worms again here.  I just wanted to
>>> share my observations with the group.
>>>
>>> Best Regards,
>>> Tammy Leino
>>>
>>> _______________________________________________
>>> 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
>   

-- 
=====================================================================
Josh Littlefield                                  Cisco Systems, Inc.
joshl@cisco.com                             1414 Massachusetts Avenue
tel: 978-936-1379  fax: 978-936-2226       Boxborough, MA  01719-2205


--------------000602000700040101010906
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Tammy, I think Ralph was making the assumption that the 'L' bit was set
in the advertised prefixes in the RA.<br>
<br>
RFC 2461, sec. 6 (Router and Prefix Discovery) describes the two
independent uses of prefix options:<br>
<br>
<pre>   Prefix Discovery is the process through which hosts learn the ranges
   of IP addresses that reside on-link and can be reached directly
   without going through a router.  Routers send Router Advertisements
   that indicate whether the sender is willing to be a default router.
   Router Advertisements also contain Prefix Information options that
   list the set of prefixes that identify on-link IP addresses.

   Stateless Address Autoconfiguration must also obtain subnet prefixes
   as part of configuring addresses.  Although the prefixes used for
   address autoconfiguration are logically distinct from those used for
   on-link determination, autoconfiguration information is piggybacked
   on Router Discovery messages to reduce network traffic.  Indeed, the
   same prefixes can be advertised for on-link determination and address
   autoconfiguration by specifying the appropriate flags in the Prefix
   Information options.  See [ADDRCONF] for details on how
   autoconfiguration information is processed.</pre>
<br>
In sec. 6.3.4 it goes on to say:<br>
<br>
<pre>   For each Prefix Information option with the on-link flag set, a host
   does the following:

      - If the prefix is the link-local prefix, silently ignore the
        Prefix Information option.

      - If the prefix is not already present in the Prefix List, and the
        Prefix Information option's Valid Lifetime field is non-zero,
        create a new entry for the prefix and initialize its
        invalidation timer to the Valid Lifetime value in the Prefix
        Information option.

      - If the prefix is already present in the host's Prefix List as
        the result of a previously-received advertisement, reset its
        invalidation timer to the Valid Lifetime value in the Prefix
        Information option.  If the new Lifetime value is zero, time-out
        the prefix immediately (see Section 6.3.5).

      - If the Prefix Information option's Valid Lifetime field is zero,
        and the prefix is not present in the host's Prefix List,
        silently ignore the option.</pre>
<br>
<br>
<br>
Leino, Tammy wrote:
<blockquote
 cite="mid:7ECEF9368E169544B43882BC98EB5D92032DA95F@SVR-ALH-EXC-02.mgc.mentorg.com"
 type="cite">
  <pre wrap="">Thanks Ralph.

I should be adding a route for this prefix when I get the RA, just not
creating an address from the prefix.  This sheds some light on comments
made by other members of the list a couple weeks ago that made no sense
then!

Many thanks for the clarification!

Best Regards,
Tammy



-----Original Message-----
From: Ralph Droms [<a class="moz-txt-link-freetext" href="mailto:rdroms@cisco.com">mailto:rdroms@cisco.com</a>]
Sent: Thursday, August 30, 2007 4:12 PM
To: Leino, Tammy
Cc: <a class="moz-txt-link-abbreviated" href="mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>
Subject: Re: [dhcwg] More insight on the prefix length of a DHCPv6
address offered in an IA_ADDR option


Tammy - my understanding of RFC 2461 is that the stack should install  
that advertised prefix in the Prefix List as an on-link prefix, even  
if the A bit is not set.  With the prefix in the Prefix List, the  
host should consider the prefix and the source of the ping to be on- 
link, and deliver the response to:

IPv6 address : 3ffe:501:ffff:100:200:ff:fe00:a1a1
link-layer address : 00:00:00:00:a1:a1

- Ralph

On Aug 30, 2007, at Aug 30, 2007,3:52 PM, Leino, Tammy wrote:

  </pre>
  <blockquote type="cite">
    <pre wrap="">Hi Ralph,

Yes, there is one prefix option in the RA that corresponds to the
address that will be assigned later by the DHCP server, but part of  
the
test is to ignore the prefix info option of the RA since the auto flag
is not set.  Should I be "remembering" the prefix length of this  
prefix
option even though I am not permitted to assign this prefix to the  
node?

Best Regards,
Tammy


-----Original Message-----
From: Ralph Droms [<a class="moz-txt-link-freetext" href="mailto:rdroms@cisco.com">mailto:rdroms@cisco.com</a>]
Sent: Thursday, August 30, 2007 3:46 PM
To: Leino, Tammy
Cc: <a class="moz-txt-link-abbreviated" href="mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>
Subject: Re: [dhcwg] More insight on the prefix length of a DHCPv6
address offered in an IA_ADDR option


Tammy - are there any prefix information options in the RA sent by
the TAHI test suite in step 1?

- Ralph

On Aug 30, 2007, at Aug 30, 2007,3:31 PM, Leino, Tammy wrote:

    </pre>
    <blockquote type="cite">
      <pre wrap="">Hello All,

I have been testing my DHCPv6 client implementation using the
phase-2 TAHI test suite, and I am seeing interesting behaviour that
gives insight into how the TAHI group is interpreting on-link
routing and prefix length in regards to RFC 3315.  When the TAHI
test assigns the NUT a global IPv6 address, it expects the NUT to
know that the prefix associated with that address is on link.  Here
is what happens:

1 -
TAHI sends RA with link-layer addr 00:00:00:00:a6:a6 - this is
important, as the rest of the packets are sent with a different
link-layer address.

NUT adds Default Router with this link-layer address.

2 -
NUT invokes DHCPv6 client

TAHI assigns NUT IPv6 address 3ffe:501:ffff:100:2a0:7dff:fe08:1

3-
TAHI pings NUT:

source IPv6 address : 3ffe:501:ffff:100:200:ff:fe00:a1a1
source link-layer address : 00:00:00:00:a1:a1

destination address : 3ffe:501:ffff:100:2a0:7dff:fe08:1

Now, this is where things get interesting.  If I did not add a
route for the prefix associated with the assigned address
indicating that this prefix is on-link, the NUT will assume the
destination to the echo reply is off-link and send the packet
through the router.  When this happens, TAHI does not recognize
receipt of this echo reply packet since it is sent to link-layer
address 00:00:00:00:a6:a6 instead of 00:00:00:00:a1:a1.  TAHI
requires that the packet be sent to the link-layer address that
sent the request; therefore, the NUT must know that the source is
on-link and that the prefix associated with the address assigned by
the DHCPv6 server is on-link.

I was previously using a prefix length of 128 for an address
assigned through DHCPv6, per suggestions received on a previous
thread, but now I am using 64.

I'm not trying to open a can of worms again here.  I just wanted to
share my observations with the group.

Best Regards,
Tammy Leino

_______________________________________________
dhcwg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/dhcwg">https://www1.ietf.org/mailman/listinfo/dhcwg</a>
      </pre>
    </blockquote>
  </blockquote>
  <pre wrap=""><!---->
_______________________________________________
dhcwg mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www1.ietf.org/mailman/listinfo/dhcwg">https://www1.ietf.org/mailman/listinfo/dhcwg</a>
  </pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-- 
=====================================================================
Josh Littlefield                                  Cisco Systems, Inc.
<a class="moz-txt-link-abbreviated" href="mailto:joshl@cisco.com">joshl@cisco.com</a>                             1414 Massachusetts Avenue
tel: 978-936-1379  fax: 978-936-2226       Boxborough, MA  01719-2205
</pre>
</body>
</html>

--------------000602000700040101010906--


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

--===============0392327503==--




From dhcwg-bounces@ietf.org Thu Aug 30 16:37:53 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQqkH-0001fB-JU; Thu, 30 Aug 2007 16:36:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQqkG-0001f5-6K
	for dhcwg@ietf.org; Thu, 30 Aug 2007 16:36:04 -0400
Received: from relay1.mentorg.com ([192.94.38.131])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQqkE-0006jV-L5
	for dhcwg@ietf.org; Thu, 30 Aug 2007 16:36:04 -0400
Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58])
	by relay1.mentorg.com with esmtp 
	id 1IQqkE-00019x-8W from tammy_leino@mentor.com ;
	Thu, 30 Aug 2007 13:36:02 -0700
Received: from SVR-ALH-EXC-02.mgc.mentorg.com ([134.86.110.227]) by
	SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft
	SMTPSVC(6.0.3790.1830); Thu, 30 Aug 2007 13:36:01 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [dhcwg] More insight on the prefix length of a DHCPv6 address
	offered in an IA_ADDR option
Date: Thu, 30 Aug 2007 15:36:00 -0500
Message-ID: <7ECEF9368E169544B43882BC98EB5D92032DA960@SVR-ALH-EXC-02.mgc.mentorg.com>
In-Reply-To: <46D728F4.3020500@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [dhcwg] More insight on the prefix length of a DHCPv6 address
	offered in an IA_ADDR option
Thread-Index: AcfrRK2v/5pgS+qASWyFD9ud/3HO5QAAJ4PQ
From: "Leino, Tammy" <tammy_leino@mentor.com>
To: "Josh Littlefield" <joshl@cisco.com>
X-OriginalArrivalTime: 30 Aug 2007 20:36:01.0369 (UTC)
	FILETIME=[60DC9C90:01C7EB45]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1fb4c76a9d88e8fb8b791f63f8d1b07f
Cc: dhcwg@ietf.org, Ralph Droms <rdroms@cisco.com>
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>,
	<mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1737476326=="
Errors-To: dhcwg-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1737476326==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7EB45.6041ECC4"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7EB45.6041ECC4
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Thank you Josh.  The L bit was set in the RA.  The A bit was not set.
=20
Best Regards,
Tammy
=20

-----Original Message-----
From: Josh Littlefield [mailto:joshl@cisco.com]
Sent: Thursday, August 30, 2007 4:31 PM
To: Leino, Tammy
Cc: Ralph Droms; dhcwg@ietf.org
Subject: Re: [dhcwg] More insight on the prefix length of a DHCPv6 =
address offered in an IA_ADDR option


Tammy, I think Ralph was making the assumption that the 'L' bit was set =
in the advertised prefixes in the RA.

RFC 2461, sec. 6 (Router and Prefix Discovery) describes the two =
independent uses of prefix options:


   Prefix Discovery is the process through which hosts learn the ranges

   of IP addresses that reside on-link and can be reached directly

   without going through a router.  Routers send Router Advertisements

   that indicate whether the sender is willing to be a default router.

   Router Advertisements also contain Prefix Information options that

   list the set of prefixes that identify on-link IP addresses.



   Stateless Address Autoconfiguration must also obtain subnet prefixes

   as part of configuring addresses.  Although the prefixes used for

   address autoconfiguration are logically distinct from those used for

   on-link determination, autoconfiguration information is piggybacked

   on Router Discovery messages to reduce network traffic.  Indeed, the

   same prefixes can be advertised for on-link determination and address

   autoconfiguration by specifying the appropriate flags in the Prefix

   Information options.  See [ADDRCONF] for details on how

   autoconfiguration information is processed.

In sec. 6.3.4 it goes on to say:


   For each Prefix Information option with the on-link flag set, a host

   does the following:



      - If the prefix is the link-local prefix, silently ignore the

        Prefix Information option.



      - If the prefix is not already present in the Prefix List, and the

        Prefix Information option's Valid Lifetime field is non-zero,

        create a new entry for the prefix and initialize its

        invalidation timer to the Valid Lifetime value in the Prefix

        Information option.



      - If the prefix is already present in the host's Prefix List as

        the result of a previously-received advertisement, reset its

        invalidation timer to the Valid Lifetime value in the Prefix

        Information option.  If the new Lifetime value is zero, time-out

        the prefix immediately (see Section 6.3.5).



      - If the Prefix Information option's Valid Lifetime field is zero,

        and the prefix is not present in the host's Prefix List,

        silently ignore the option.



Leino, Tammy wrote:=20

Thanks Ralph.



I should be adding a route for this prefix when I get the RA, just not

creating an address from the prefix.  This sheds some light on comments

made by other members of the list a couple weeks ago that made no sense

then!



Many thanks for the clarification!



Best Regards,

Tammy







-----Original Message-----

From: Ralph Droms [ mailto:rdroms@cisco.com]

Sent: Thursday, August 30, 2007 4:12 PM

To: Leino, Tammy

Cc:  dhcwg@ietf.org

Subject: Re: [dhcwg] More insight on the prefix length of a DHCPv6

address offered in an IA_ADDR option





Tammy - my understanding of RFC 2461 is that the stack should install =20

that advertised prefix in the Prefix List as an on-link prefix, even =20

if the A bit is not set.  With the prefix in the Prefix List, the =20

host should consider the prefix and the source of the ping to be on-=20

link, and deliver the response to:



IPv6 address : 3ffe:501:ffff:100:200:ff:fe00:a1a1

link-layer address : 00:00:00:00:a1:a1



- Ralph



On Aug 30, 2007, at Aug 30, 2007,3:52 PM, Leino, Tammy wrote:



 =20

Hi Ralph,



Yes, there is one prefix option in the RA that corresponds to the

address that will be assigned later by the DHCP server, but part of =20

the

test is to ignore the prefix info option of the RA since the auto flag

is not set.  Should I be "remembering" the prefix length of this =20

prefix

option even though I am not permitted to assign this prefix to the =20

node?



Best Regards,

Tammy





-----Original Message-----

From: Ralph Droms [ mailto:rdroms@cisco.com]

Sent: Thursday, August 30, 2007 3:46 PM

To: Leino, Tammy

Cc:  dhcwg@ietf.org

Subject: Re: [dhcwg] More insight on the prefix length of a DHCPv6

address offered in an IA_ADDR option





Tammy - are there any prefix information options in the RA sent by

the TAHI test suite in step 1?



- Ralph



On Aug 30, 2007, at Aug 30, 2007,3:31 PM, Leino, Tammy wrote:



   =20

Hello All,



I have been testing my DHCPv6 client implementation using the

phase-2 TAHI test suite, and I am seeing interesting behaviour that

gives insight into how the TAHI group is interpreting on-link

routing and prefix length in regards to RFC 3315.  When the TAHI

test assigns the NUT a global IPv6 address, it expects the NUT to

know that the prefix associated with that address is on link.  Here

is what happens:



1 -

TAHI sends RA with link-layer addr 00:00:00:00:a6:a6 - this is

important, as the rest of the packets are sent with a different

link-layer address.



NUT adds Default Router with this link-layer address.



2 -

NUT invokes DHCPv6 client



TAHI assigns NUT IPv6 address 3ffe:501:ffff:100:2a0:7dff:fe08:1



3-

TAHI pings NUT:



source IPv6 address : 3ffe:501:ffff:100:200:ff:fe00:a1a1

source link-layer address : 00:00:00:00:a1:a1



destination address : 3ffe:501:ffff:100:2a0:7dff:fe08:1



Now, this is where things get interesting.  If I did not add a

route for the prefix associated with the assigned address

indicating that this prefix is on-link, the NUT will assume the

destination to the echo reply is off-link and send the packet

through the router.  When this happens, TAHI does not recognize

receipt of this echo reply packet since it is sent to link-layer

address 00:00:00:00:a6:a6 instead of 00:00:00:00:a1:a1.  TAHI

requires that the packet be sent to the link-layer address that

sent the request; therefore, the NUT must know that the source is

on-link and that the prefix associated with the address assigned by

the DHCPv6 server is on-link.



I was previously using a prefix length of 128 for an address

assigned through DHCPv6, per suggestions received on a previous

thread, but now I am using 64.



I'm not trying to open a can of worms again here.  I just wanted to

share my observations with the group.



Best Regards,

Tammy Leino



_______________________________________________

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

 =20


--=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Josh Littlefield                                  Cisco Systems, Inc.

joshl@cisco.com                             1414 Massachusetts Avenue

tel: 978-936-1379  fax: 978-936-2226       Boxborough, MA  01719-2205


------_=_NextPart_001_01C7EB45.6041ECC4
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

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


<META content=3D"MSHTML 6.00.6000.16481" name=3DGENERATOR></HEAD>
<BODY text=3D#000000 bgColor=3D#ffffff>
<DIV><SPAN class=3D940253520-30082007><FONT face=3DArial size=3D2>Thank =
you=20
Josh.&nbsp; The L bit was set in the RA.&nbsp; The A bit was not=20
set.</FONT></SPAN></DIV>
<DIV><SPAN class=3D940253520-30082007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D940253520-30082007><FONT face=3DArial size=3D2>Best=20
Regards,<BR>Tammy</FONT></SPAN></DIV>
<DIV><SPAN class=3D940253520-30082007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Josh Littlefield=20
  [mailto:joshl@cisco.com]<BR><B>Sent:</B> Thursday, August 30, 2007 =
4:31=20
  PM<BR><B>To:</B> Leino, Tammy<BR><B>Cc:</B> Ralph Droms;=20
  dhcwg@ietf.org<BR><B>Subject:</B> Re: [dhcwg] More insight on the =
prefix=20
  length of a DHCPv6 address offered in an IA_ADDR=20
  option<BR><BR></FONT></DIV>Tammy, I think Ralph was making the =
assumption that=20
  the 'L' bit was set in the advertised prefixes in the RA.<BR><BR>RFC =
2461,=20
  sec. 6 (Router and Prefix Discovery) describes the two independent =
uses of=20
  prefix options:<BR><BR><PRE>   Prefix Discovery is the process through =
which hosts learn the ranges
   of IP addresses that reside on-link and can be reached directly
   without going through a router.  Routers send Router Advertisements
   that indicate whether the sender is willing to be a default router.
   Router Advertisements also contain Prefix Information options that
   list the set of prefixes that identify on-link IP addresses.

   Stateless Address Autoconfiguration must also obtain subnet prefixes
   as part of configuring addresses.  Although the prefixes used for
   address autoconfiguration are logically distinct from those used for
   on-link determination, autoconfiguration information is piggybacked
   on Router Discovery messages to reduce network traffic.  Indeed, the
   same prefixes can be advertised for on-link determination and address
   autoconfiguration by specifying the appropriate flags in the Prefix
   Information options.  See [ADDRCONF] for details on how
   autoconfiguration information is processed.</PRE><BR>In sec. 6.3.4 it =
goes=20
  on to say:<BR><BR><PRE>   For each Prefix Information option with the =
on-link flag set, a host
   does the following:

      - If the prefix is the link-local prefix, silently ignore the
        Prefix Information option.

      - If the prefix is not already present in the Prefix List, and the
        Prefix Information option's Valid Lifetime field is non-zero,
        create a new entry for the prefix and initialize its
        invalidation timer to the Valid Lifetime value in the Prefix
        Information option.

      - If the prefix is already present in the host's Prefix List as
        the result of a previously-received advertisement, reset its
        invalidation timer to the Valid Lifetime value in the Prefix
        Information option.  If the new Lifetime value is zero, time-out
        the prefix immediately (see Section 6.3.5).

      - If the Prefix Information option's Valid Lifetime field is zero,
        and the prefix is not present in the host's Prefix List,
        silently ignore the option.</PRE><BR><BR><BR>Leino, Tammy wrote: =

  <BLOCKQUOTE=20
  =
cite=3Dmid:7ECEF9368E169544B43882BC98EB5D92032DA95F@SVR-ALH-EXC-02.mgc.me=
ntorg.com=20
  type=3D"cite"><PRE wrap=3D"">Thanks Ralph.

I should be adding a route for this prefix when I get the RA, just not
creating an address from the prefix.  This sheds some light on comments
made by other members of the list a couple weeks ago that made no sense
then!

Many thanks for the clarification!

Best Regards,
Tammy



-----Original Message-----
From: Ralph Droms [<A class=3Dmoz-txt-link-freetext =
href=3D"mailto:rdroms@cisco.com">mailto:rdroms@cisco.com</A>]
Sent: Thursday, August 30, 2007 4:12 PM
To: Leino, Tammy
Cc: <A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</A>
Subject: Re: [dhcwg] More insight on the prefix length of a DHCPv6
address offered in an IA_ADDR option


Tammy - my understanding of RFC 2461 is that the stack should install =20
that advertised prefix in the Prefix List as an on-link prefix, even =20
if the A bit is not set.  With the prefix in the Prefix List, the =20
host should consider the prefix and the source of the ping to be on-=20
link, and deliver the response to:

IPv6 address : 3ffe:501:ffff:100:200:ff:fe00:a1a1
link-layer address : 00:00:00:00:a1:a1

- Ralph

On Aug 30, 2007, at Aug 30, 2007,3:52 PM, Leino, Tammy wrote:

  </PRE>
    <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">Hi Ralph,

Yes, there is one prefix option in the RA that corresponds to the
address that will be assigned later by the DHCP server, but part of =20
the
test is to ignore the prefix info option of the RA since the auto flag
is not set.  Should I be "remembering" the prefix length of this =20
prefix
option even though I am not permitted to assign this prefix to the =20
node?

Best Regards,
Tammy


-----Original Message-----
From: Ralph Droms [<A class=3Dmoz-txt-link-freetext =
href=3D"mailto:rdroms@cisco.com">mailto:rdroms@cisco.com</A>]
Sent: Thursday, August 30, 2007 3:46 PM
To: Leino, Tammy
Cc: <A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</A>
Subject: Re: [dhcwg] More insight on the prefix length of a DHCPv6
address offered in an IA_ADDR option


Tammy - are there any prefix information options in the RA sent by
the TAHI test suite in step 1?

- Ralph

On Aug 30, 2007, at Aug 30, 2007,3:31 PM, Leino, Tammy wrote:

    </PRE>
      <BLOCKQUOTE type=3D"cite"><PRE wrap=3D"">Hello All,

I have been testing my DHCPv6 client implementation using the
phase-2 TAHI test suite, and I am seeing interesting behaviour that
gives insight into how the TAHI group is interpreting on-link
routing and prefix length in regards to RFC 3315.  When the TAHI
test assigns the NUT a global IPv6 address, it expects the NUT to
know that the prefix associated with that address is on link.  Here
is what happens:

1 -
TAHI sends RA with link-layer addr 00:00:00:00:a6:a6 - this is
important, as the rest of the packets are sent with a different
link-layer address.

NUT adds Default Router with this link-layer address.

2 -
NUT invokes DHCPv6 client

TAHI assigns NUT IPv6 address 3ffe:501:ffff:100:2a0:7dff:fe08:1

3-
TAHI pings NUT:

source IPv6 address : 3ffe:501:ffff:100:200:ff:fe00:a1a1
source link-layer address : 00:00:00:00:a1:a1

destination address : 3ffe:501:ffff:100:2a0:7dff:fe08:1

Now, this is where things get interesting.  If I did not add a
route for the prefix associated with the assigned address
indicating that this prefix is on-link, the NUT will assume the
destination to the echo reply is off-link and send the packet
through the router.  When this happens, TAHI does not recognize
receipt of this echo reply packet since it is sent to link-layer
address 00:00:00:00:a6:a6 instead of 00:00:00:00:a1:a1.  TAHI
requires that the packet be sent to the link-layer address that
sent the request; therefore, the NUT must know that the source is
on-link and that the prefix associated with the address assigned by
the DHCPv6 server is on-link.

I was previously using a prefix length of 128 for an address
assigned through DHCPv6, per suggestions received on a previous
thread, but now I am using 64.

I'm not trying to open a can of worms again here.  I just wanted to
share my observations with the group.

Best Regards,
Tammy Leino

_______________________________________________
dhcwg mailing list
<A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</A>
<A class=3Dmoz-txt-link-freetext =
href=3D"https://www1.ietf.org/mailman/listinfo/dhcwg">https://www1.ietf.o=
rg/mailman/listinfo/dhcwg</A>
      </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE wrap=3D""><!---->
_______________________________________________
dhcwg mailing list
<A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:dhcwg@ietf.org">dhcwg@ietf.org</A>
<A class=3Dmoz-txt-link-freetext =
href=3D"https://www1.ietf.org/mailman/listinfo/dhcwg">https://www1.ietf.o=
rg/mailman/listinfo/dhcwg</A>
  </PRE></BLOCKQUOTE><BR><PRE class=3Dmoz-signature cols=3D"72">--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Josh Littlefield                                  Cisco Systems, Inc.
<A class=3Dmoz-txt-link-abbreviated =
href=3D"mailto:joshl@cisco.com">joshl@cisco.com</A>                      =
       1414 Massachusetts Avenue
tel: 978-936-1379  fax: 978-936-2226       Boxborough, MA  01719-2205
</PRE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C7EB45.6041ECC4--


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

--===============1737476326==--




From dhcwg-bounces@ietf.org Fri Aug 31 04:53:42 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IR2EK-0002Gu-AE; Fri, 31 Aug 2007 04:51:52 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IR2EI-0002DE-Eh
	for dhcwg@ietf.org; Fri, 31 Aug 2007 04:51:50 -0400
Received: from szxga02-in.huawei.com ([61.144.161.54])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IR2EH-0004n9-Az
	for dhcwg@ietf.org; Fri, 31 Aug 2007 04:51:50 -0400
Received: from huawei.com (szxga02-in [172.24.2.6])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JNM003UKR94QS@szxga02-in.huawei.com> for
	dhcwg@ietf.org; Fri, 31 Aug 2007 16:51:05 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
	by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTP id <0JNM0060YR94CP@szxga02-in.huawei.com> for
	dhcwg@ietf.org; Fri, 31 Aug 2007 16:51:04 +0800 (CST)
Received: from SSK1548 ([10.18.5.107])
	by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
	(built Aug
	8 2006)) with ESMTPA id <0JNM00MUDR8WHU@szxml04-in.huawei.com> for
	dhcwg@ietf.org; Fri, 31 Aug 2007 16:51:04 +0800 (CST)
Date: Fri, 31 Aug 2007 14:20:54 +0530
From: "S.SenthilKumar (Huawei)" <senthilKumars@huawei.com>
In-reply-to: 
To: senthilKumars@huawei.com, dhcwg@ietf.org
Message-id: <000001c7ebac$0d338150$6b05120a@china.huawei.com>
Organization: Huawei
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: quoted-printable
Thread-index: AcfooLtnBxB8mrtwTvCPnampzBpsoQAA2P3AAMHUyiA=
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: ssenthilkumar@gmail.com
Subject: [dhcwg] RE: Issue/Solution for Confirm-Reply - Remainder
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: senthilKumars@huawei.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

Dear All

I would appreciate if somebody could clarify or Provide pointers for the =
issue regarding Confirm-Reply (RFC3315) that I had sent earlier (Refer =
the attached mail).

Thanking you,

Regards
SenthilKumar.S


Disclaimer: This e-mail and attachments contain confidential information =
from HUAWEI, which is intended only for the person or entity whose =
address is listed above. Any use of the information contained herein in =
any way (including, but not limited to, total or partial disclosure, =
reproduction, or dissemination) by persons other than the intended =
recipient's) is prohibited. If you receive this e-mail in error, please =
notify the sender by phone or email immediately and delete it!

-----Original Message-----
From: S.SenthilKumar (Huawei) [mailto:senthilkumars@huawei.com]=20
Sent: Monday, August 27, 2007 5:48 PM
To: 'dhcwg@ietf.org'
Cc: 'senthilkumars@huawei.com'; 'ssenthilkumar@gmail.com'
Subject: FW: Issue/Solution for Confirm-Reply

Dear All
Please suggest how to resolve this issue.
Configuration
=E3=80=80=E3=80=80Assume that IA1, IA2 and IA3 were present in the same =
interface
=E3=80=80=E3=80=80* IA1 has binding with Server S1 and K1 is the DAP key =
in use for the current session
=E3=80=80=E3=80=80* IA2 has binding with Server S2 and K2 is the DAP key =
in use for the current session
=E3=80=80=E3=80=80* IA3 has binding with Server S3 and No DAP =
Authentication (Client has accepted Advertise without Authentication =
Option as it is enabled in the local configuration)
=E3=80=80=E3=80=80* And all the IAs leased.

As per RFC, Confirm message has to be sent to the server containing all =
the IAs present in the interface. But in this case how, Which Key has to =
be used, whether DAP Option has to be present.=20

18.1.2. Creation and Transmission of Confirm Messages
The client MUST include a Client Identifier option to identify itself to =
the server.  The client includes IA options for all of the IAs assigned =
to the interface for which the Confirm message is being sent.  The IA =
options include all of the addresses the client currently has associated =
with those IAs.  The client SHOULD set the T1 and T2 fields in any IA_NA =
options, and the preferred-lifetime and valid-lifetime fields in the IA =
Address options to 0, as the server will ignore these fields.

Solution I had devised is that Confirm can be send on the basics of IA =
i.e confirm will carry only one IA (IA_NA or IA_TA)

Advantages of the solution
1. If Not on link status is received in the Reply received in response =
to Confirm, Only the address present in the IA will be released
2. Authentication =E2=80=93 Confirm-Reply transaction will also be part =
of the session (Solicit-Advertise till Release/Decline of the last =
address)
Disadvantages of the solution
1. Multiple Confirm message will be send from the client (Also loads the =
server)
2. RFC Conformance =E2=80=93 I=E2=80=99m not sure about this as =
=E2=80=9CALL=E2=80=9D is mentioned in the RFC.

Let me know your views.

Thanking you,

Regards
SenthilKumar.S


Disclaimer: This e-mail and attachments contain confidential information =
from HUAWEI, which is intended only for the person or entity whose =
address is listed above. Any use of the information contained herein in =
any way (including, but not limited to, total or partial disclosure, =
reproduction, or dissemination) by persons other than the intended =
recipient's) is prohibited. If you receive this e-mail in error, please =
notify the sender by phone or email immediately and delete it!




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



From dhcwg-bounces@ietf.org Fri Aug 31 17:55:10 2007
Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IREQb-0007QZ-5f; Fri, 31 Aug 2007 17:53:21 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IREQZ-0007QS-B3
	for dhcwg@ietf.org; Fri, 31 Aug 2007 17:53:19 -0400
Received: from relay1.mentorg.com ([192.94.38.131])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IREQY-0004ap-NL
	for dhcwg@ietf.org; Fri, 31 Aug 2007 17:53:19 -0400
Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58])
	by relay1.mentorg.com with esmtp 
	id 1IREQX-0006QN-L2 from tammy_leino@mentor.com 
	for dhcwg@ietf.org; Fri, 31 Aug 2007 14:53:17 -0700
Received: from SVR-ALH-EXC-02.mgc.mentorg.com ([134.86.110.227]) by
	SVR-ORW-EXC-10.mgc.mentorg.com with Microsoft
	SMTPSVC(6.0.3790.1830); Fri, 31 Aug 2007 14:53:16 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 31 Aug 2007 16:53:15 -0500
Message-ID: <7ECEF9368E169544B43882BC98EB5D92032DA965@SVR-ALH-EXC-02.mgc.mentorg.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Elapsed Time Option in RFC 3315
Thread-Index: AcfsGVRq5VT9HDmTTzSgslBb75Q9tQ==
From: "Leino, Tammy" <tammy_leino@mentor.com>
To: <dhcwg@ietf.org>
X-OriginalArrivalTime: 31 Aug 2007 21:53:16.0914 (UTC)
	FILETIME=[56466520:01C7EC19]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Subject: [dhcwg] Elapsed Time Option in RFC 3315
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="===============1846306795=="
Errors-To: dhcwg-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1846306795==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7EC19.55B8F9A3"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7EC19.55B8F9A3
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello All,

Could someone kindly clarify the requirement of the Elapsed Time option =
for me.  Is it required in all packets sent by the client, or is it just =
required IF the client wants to indicate how long it has been trying to =
complete a DHCP message exchange?

   A client MUST include an Elapsed Time option in messages to indicate
   how long the client has been trying to complete a DHCP message
   exchange.

This statement in the RFC seems ambiguous to me, and any clarification =
you can offer would be greatly appreciated.

Best Regards,
Tammy Leino

------_=_NextPart_001_01C7EC19.55B8F9A3
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>Elapsed Time Option in RFC 3315</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">Hello All,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Could someone kindly clarify the =
requirement of the Elapsed Time option for me.&nbsp; Is it required in =
all packets sent by the client, or is it just required IF the client =
wants to indicate how long it has been trying to complete a DHCP message =
exchange?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Courier New">&nbsp;&nbsp; A client MUST =
include an Elapsed Time option in messages to indicate<BR>
&nbsp;&nbsp; how long the client has been trying to complete a DHCP =
message<BR>
&nbsp;&nbsp; exchange.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">This statement in the RFC seems =
ambiguous to me, and any clarification you can offer would be greatly =
appreciated.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Best Regards,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">Tammy Leino</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7EC19.55B8F9A3--


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

--===============1846306795==--




