From ipv6-bounces@ietf.org Sat Aug 04 20:00:52 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IHTXT-0000vg-W0; Sat, 04 Aug 2007 20:00:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IHTXS-0000va-8P
	for ipv6@ietf.org; Sat, 04 Aug 2007 20:00:06 -0400
Received: from [2002:425c:4242:0:210:5aff:fe86:1f54] (helo=cyteen.hactrn.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IHTXR-00070I-B6
	for ipv6@ietf.org; Sat, 04 Aug 2007 20:00:05 -0400
Received: from cyteen.hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id C6A0E28452
	for <ipv6@ietf.org>; Sun,  5 Aug 2007 00:00:04 +0000 (UTC)
To: ipv6@ietf.org
From: Rob Austein <sra+ipng@hactrn.net>
Date: Sun, 05 Aug 2007 00:00:04 +0000
Message-Id: <20070805000004.C6A0E28452@cyteen.hactrn.net>
X-Spam-Score: -1.4 (-)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Subject: Weekly posting summary for ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 50.00% |    1 | 50.97% |     4871 | sra+ipng@hactrn.net
 50.00% |    1 | 49.03% |     4686 | mailman-owner@ietf.org
--------+------+--------+----------+------------------------
100.00% |    2 |100.00% |     9557 | Total

Grunchweather Associates provides this automatic summary on an at-whim
basis at the request of the IPv6 WG chairs.  Your mileage may vary.
We decline responsibilities, all shapes, all sizes, all colors.
If this script produces broken output, you get to keep both pieces.

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



From ipv6-bounces@ietf.org Thu Aug 09 16:08:32 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJEGl-0003LP-5g; Thu, 09 Aug 2007 16:06:07 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJEGg-0003GA-3t
	for ipv6@ietf.org; Thu, 09 Aug 2007 16:06:02 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IJEGf-0006kK-P0
	for ipv6@ietf.org; Thu, 09 Aug 2007 16:06:02 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-3.cisco.com with ESMTP; 09 Aug 2007 13:06:01 -0700
X-IronPort-AV: i="4.19,241,1183359600"; 
	d="scan'208,217"; a="512046524:sNHT79457798"
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 l79K61h0001738
	for <ipv6@ietf.org>; Thu, 9 Aug 2007 13:06:01 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l79K5qW1018638
	for <ipv6@ietf.org>; Thu, 9 Aug 2007 20:06:00 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, 9 Aug 2007 16:05:45 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 9 Aug 2007 16:05:42 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D0382461C@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Closure of IPv6 WG and creation of IPv6 Maintenance WG
Thread-Index: AcfawKo/+d1eTejDQeSalRSOgK4GBQ==
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 09 Aug 2007 20:05:45.0533 (UTC)
	FILETIME=[ABDD46D0:01C7DAC0]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2526; t=1186689961;
	x=1187553961; 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:=20Closure=20of=20IPv6=20WG=20and=20creation=20of=20IPv6=20Maint
	enance=20WG |Sender:=20;
	bh=gSOi5TmFYYglz7jXPbx+2Aq941BDYPtUMZne/Mqwbx0=;
	b=ZkXAuVI7jpJlligtn3cjpu3suYvkbQqtTM+zyw3qCRbtBuiU+pdzUIQUQH440EfxNC4BfB+Q
	idJXYqXBh9Ii4PeL0Bqmc7gVUtqDRt73/Idmdvn01Y6nB5pvUBhClZDBSWYc8Ab3lVYBhI7mhY
	9Y/W/fVi9scy1aCiBORRYbqqg=;
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: 52f7a77164458f8c7b36b66787c853da
Subject: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1016128452=="
Errors-To: ipv6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1016128452==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7DAC0.ABB12203"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7DAC0.ABB12203
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Folks,
=20
When will a URL be available for this new IPv6 Maintenance WG? Will this
new WG have a new mailer to send emails to or will the ipv6@ietf.org
mailer continue to be used for the new WG?  If a new mailer is created,
will people subscribed to ipv6@ietf.org automatically get moved to the
new mailer? Lastly, in what timeframe can one expect to get this
administrative work out of the way?
=20
Sorry, if I missed any emails related to answers to such questions.
=20
Thanks.
=20
Hemant

------_=_NextPart_001_01C7DAC0.ABB12203
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3132" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D992545819-09082007><FONT face=3DArial=20
size=3D2>Folks,</FONT></SPAN></DIV>
<DIV><SPAN class=3D992545819-09082007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D992545819-09082007><FONT face=3DArial size=3D2>When =
will a URL be=20
available for this new IPv6 Maintenance WG? Will this new WG have a new =
mailer=20
to send emails to or will the&nbsp;<A=20
href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</A>&nbsp;mailer&nbsp;continue=
 to be=20
used for the new WG?&nbsp;&nbsp;If a new mailer is created, will people=20
subscribed to <A=20
href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</A>&nbsp;automatically get =
moved to=20
the new mailer? Lastly, in what timeframe can one expect to get this=20
administrative work out of the way?</FONT></SPAN></DIV>
<DIV><SPAN class=3D992545819-09082007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D992545819-09082007><FONT face=3DArial size=3D2>Sorry, =
if I missed=20
any emails related to answers to such questions.</FONT></SPAN></DIV>
<DIV><SPAN class=3D992545819-09082007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D992545819-09082007><FONT face=3DArial=20
size=3D2>Thanks.</FONT></SPAN></DIV>
<DIV><SPAN class=3D992545819-09082007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D992545819-09082007><FONT face=3DArial=20
size=3D2>Hemant</FONT></SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C7DAC0.ABB12203--


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

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

--===============1016128452==--




From ipv6-bounces@ietf.org Fri Aug 10 02:37:29 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJO5b-0007ME-6s; Fri, 10 Aug 2007 02:35:15 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJO5Y-0007M5-VH
	for ipv6@ietf.org; Fri, 10 Aug 2007 02:35:12 -0400
Received: from mux1.uit.no ([129.242.4.252])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IJO5Y-00074U-0w
	for ipv6@ietf.org; Fri, 10 Aug 2007 02:35:12 -0400
Received: from shimmer.student.uit.no (shimmer.student.uit.no [129.242.80.34])
	by mux1.uit.no (8.13.8/8.13.6/Mux) with ESMTP id l7A6Z765065574
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 10 Aug 2007 08:35:07 +0200 (CEST)
Received: from chandra.student.uit.no (chandra.student.uit.no [129.242.80.32])
	by shimmer.student.uit.no (8.13.1/8.13.6) with ESMTP id
	l7A6Z6XG015339; Fri, 10 Aug 2007 08:35:06 +0200
Date: Fri, 10 Aug 2007 08:35:06 +0200 (CEST)
From: Roger Jorgensen <rogerj@jorgensen.no>
X-X-Sender: rogerj@chandra.student.uit.no
To: "Hemant Singh \\(shemant\\)" <shemant@cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D0382461C@xmb-rtp-20e.amer.cisco.com>
Message-ID: <Pine.LNX.4.64.0708100833510.3244@chandra.student.uit.no>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D0382461C@xmb-rtp-20e.amer.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: : ok
X-Scanned-By: MIMEDefang 2.62 on 129.242.4.252
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: ipv6@ietf.org
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Thu, 9 Aug 2007, Hemant Singh \(shemant\) wrote:
> Folks,
>
> When will a URL be available for this new IPv6 Maintenance WG? Will this
> new WG have a new mailer to send emails to or will the ipv6@ietf.org
> mailer continue to be used for the new WG?  If a new mailer is created,
> will people subscribed to ipv6@ietf.org automatically get moved to the
> new mailer? Lastly, in what timeframe can one expect to get this
> administrative work out of the way?
>
> Sorry, if I missed any emails related to answers to such questions.

you havent missed anything since the last rounds of email... things are 
kinda slow :]


-- 

------------------------------
Roger Jorgensen              | - ROJO9-RIPE  - RJ85P-NORID
roger@jorgensen.no           | - IPv6 is The Key!
-------------------------------------------------------

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



From ipv6-bounces@ietf.org Fri Aug 10 10:15:15 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJVEY-0007tm-Hs; Fri, 10 Aug 2007 10:12:58 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJTGY-0004D2-OC
	for ipv6@ietf.org; Fri, 10 Aug 2007 08:06:54 -0400
Received: from piper.jhuapl.edu ([128.244.26.33] helo=jhuapl.edu)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IJTGY-0000rK-Cu
	for ipv6@ietf.org; Fri, 10 Aug 2007 08:06:54 -0400
Received: from ([128.244.206.192])
	by piper.jhuapl.edu with ESMTP  id 5502121.37935367;
	Fri, 10 Aug 2007 08:06:37 -0400
Message-ID: <46BC54CC.6080402@innovationslab.net>
Date: Fri, 10 Aug 2007 08:06:36 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509)
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D0382461C@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D0382461C@xmb-rtp-20e.amer.cisco.com>
X-Enigmail-Version: 0.94.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
X-Mailman-Approved-At: Fri, 10 Aug 2007 10:12:56 -0400
Cc: ipv6@ietf.org
Subject: Re: Closure of IPv6 WG and creation of IPv6 Maintenance WG
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Given the number of comments/concerns raised over the initial proposed
charter, the chairs need to revise the charter.  After that, it is
reviewed by the relevant AD (Jari in this case) and once he is satisfied
with the charter content, it is reviewed by the IESG and comments are
solicited from the IETF community.

Our intent is to re-use the existing ipv6 mailing list rather than
create a new one.

Regards,
Brian

Hemant Singh (shemant) wrote:
> Folks,
>  
> When will a URL be available for this new IPv6 Maintenance WG? Will this
> new WG have a new mailer to send emails to or will the ipv6@ietf.org
> <mailto:ipv6@ietf.org> mailer continue to be used for the new WG?  If a
> new mailer is created, will people subscribed to ipv6@ietf.org
> <mailto:ipv6@ietf.org> automatically get moved to the new mailer?
> Lastly, in what timeframe can one expect to get this administrative work
> out of the way?
>  
> Sorry, if I missed any emails related to answers to such questions.
>  
> Thanks.
>  
> Hemant
> 
> 
> ------------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

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



From ipv6-bounces@ietf.org Fri Aug 10 11:48:49 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJWhC-0005nM-Bu; Fri, 10 Aug 2007 11:46:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJWhA-0005gl-Im
	for ipv6@ietf.org; Fri, 10 Aug 2007 11:46:36 -0400
Received: from nf-out-0910.google.com ([64.233.182.187])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IJWh8-0000GO-JP
	for ipv6@ietf.org; Fri, 10 Aug 2007 11:46:36 -0400
Received: by nf-out-0910.google.com with SMTP id c10so285208nfd
	for <ipv6@ietf.org>; Fri, 10 Aug 2007 08:46:33 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type;
	b=FQDfRXKqk/n6vEXw/kx5f1SrfzaJIz3dkFlPt93gyjl6gBb/yf4sDzf9jS1qBaxOXRhB9uAxvJPyzT5Sq8rvzHoKfB0gKwWEY7GXmBQ+2rrJ0mtxF+HxNidyhtHZL9OzZtNcKzXjlZf8hKTdZbhXX/UEMJFOyb/gQJt8Dct9zVk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=NIG0ImA75bxuhGGEoRevyScShRj/mH3MRnnXYVu9XFeaXDZKKqhKSlJoTXxryJMKWgTC4cBAoU7MvMkafQZxKrg0UB1wiw6oX3vh3zpySFbAVW9aWN0HLhJ5my2wUokzTxMVf4YwNYZArXXeL0MEfEKjLssazVofZBtnRozvfIg=
Received: by 10.78.200.20 with SMTP id x20mr1413206huf.1186760793039;
	Fri, 10 Aug 2007 08:46:33 -0700 (PDT)
Received: by 10.78.11.8 with HTTP; Fri, 10 Aug 2007 08:46:32 -0700 (PDT)
Message-ID: <632b361b0708100846t1137c638ne6f951f60673ef31@mail.gmail.com>
Date: Fri, 10 Aug 2007 21:16:32 +0530
From: "ather zaidi" <syedatherzaidi@gmail.com>
To: ipv6@ietf.org
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_96678_9680180.1186760792983"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 64b72a8e61417554b4b727cb14e7034d
Subject: modifications in ipv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

------=_Part_96678_9680180.1186760792983
Content-Type: multipart/alternative; 
	boundary="----=_Part_96679_22909504.1186760792983"

------=_Part_96679_22909504.1186760792983
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Dear All,

I am a final year engineering student in India, as part of our final year
project we are working on some modifications in ipv6 header format . We have
already submitted the initial proposal at our university. I will appreciate
any comments and suggestions . We are novices in the field, so we also
expect lot of criticism.
But anything which makes the project worthwhile is most welcome. kindly read
the attachment.

thanks and regards

Ather Zaidi
f/o Engg and Tech
Jamia Millia Islamia
New Delhi

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

Dear All,<br>&nbsp;<br>I am a final year engineering student in India, as part of our final year project we are working on some modifications in ipv6 header format . We have already submitted the initial proposal at our university. I will appreciate any comments and suggestions . We are novices in the field, so we also expect lot of criticism.
<br>But anything which makes the project worthwhile is most welcome. kindly read the attachment.<br><br>thanks and regards<br><br>Ather Zaidi<br>f/o Engg and Tech<br>Jamia Millia Islamia <br>New Delhi<br>

------=_Part_96679_22909504.1186760792983--

------=_Part_96678_9680180.1186760792983
Content-Type: application/msword; name="idea for project.doc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="idea for project.doc"
X-Attachment-Id: f_f56umj8v

0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAALgAAAAAAAAAA
EAAAMAAAAAEAAAD+////AAAAAC0AAAD/////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////s
pcEAcWAJBAAA8BK/AAAAAAAAEAAAAAAABgAAmRcAAA4AYmpianFQcVAAAAAAAAAAAAAAAAAAAAAA
AAAJBBYALiQAABM6AQATOgEAmQ8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD//w8AAAAA
AAAAAAD//w8AAAAAAAAAAAD//w8AAAAAAAAAAAAAAAAAAAAAAKQAAAAAABAEAAAAAAAAEAQAABAE
AAAAAAAAEAQAAAAAAAAQBAAAAAAAABAEAAAAAAAAEAQAABQAAAAAAAAAAAAAACQEAAAAAAAA6AgA
AAAAAADoCAAAAAAAAOgIAAAAAAAA6AgAABwAAAAECQAAFAAAACQEAAAAAAAAMg0AADIBAAAkCQAA
AAAAACQJAAAAAAAAJAkAAAAAAAAkCQAAAAAAACQJAAAAAAAAJAkAAAAAAAAkCQAAAAAAACQJAAAA
AAAAsQwAAAIAAACzDAAAAAAAALMMAAAAAAAAswwAAAAAAACzDAAAAAAAALMMAAAAAAAAswwAACQA
AABkDgAAaAIAAMwQAAA+AQAA1wwAABUAAAAAAAAAAAAAAAAAAAAAAAAAEAQAAAAAAAAkCQAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAkCQAAAAAAACQJAAAAAAAAJAkAAAAAAAAkCQAAAAAAANcMAAAAAAAA
AAAAAAAAAAAQBAAAAAAAABAEAAAAAAAAJAkAAAAAAAAAAAAAAAAAACQJAAAAAAAA7AwAABYAAABM
CQAAAAAAAEwJAAAAAAAATAkAAAAAAAAkCQAACgAAABAEAAAAAAAAJAkAAAAAAAAQBAAAAAAAACQJ
AAAAAAAAsQwAAAAAAAAAAAAAAAAAAEwJAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAJAkAAAAAAACxDAAAAAAAAAAAAAAAAAAATAkAAAAAAABMCQAA
HgAAAOkLAAAYAAAAEAQAAAAAAAAQBAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAANQwAAAAAAAAkCQAAAAAAABgJAAAMAAAAkMTXoq/a
xwEAAAAAAAAAAOgIAAAAAAAALgkAAAoAAAABDAAACAAAAAAAAAAAAAAAsQwAAAAAAAACDQAAMAAA
ADINAAAAAAAACQwAACwAAAAKEgAAAAAAADgJAAAKAAAAChIAABAAAAA1DAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAoSAAAAAAAAAAAAAAAAAAAQBAAAAAAAADUMAAB8AAAAJAkAAAAAAAAkCQAAAAAAAEwJ
AAAAAAAAJAkAAAAAAAAkCQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAJAkA
AAAAAAAkCQAAAAAAACQJAAAAAAAA1wwAAAAAAADXDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAQgkAAAoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACQJAAAA
AAAAJAkAAAAAAAAkCQAAAAAAADINAAAAAAAAJAkAAAAAAAAkCQAAAAAAACQJAAAAAAAAJAkAAAAA
AAAAAAAAAAAAACQEAAAAAAAAJAQAAAAAAAAkBAAAxAQAAOgIAAAAAAAAJAQAAAAAAAAkBAAAAAAA
ACQEAAAAAAAA6AgAAAAAAAAkBAAAAAAAACQEAAAAAAAAJAQAAAAAAAAQBAAAAAAAABAEAAAAAAAA
EAQAAAAAAAAQBAAAAAAAABAEAAAAAAAAEAQAAAAAAAD/////AAAAAAIADAEAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAE5ldHdv
cmsgRm9yZW5zaWNzIGlzIHRoZSBjYXB0dXJlLCByZWNvcmRpbmcsIGFuZCBhbmFseXNpcyBvZiBu
ZXR3b3JrIGV2ZW50cyBpbiBvcmRlciB0byBkaXNjb3ZlciB0aGUgc291cmNlIG9mIHNlY3VyaXR5
IGF0dGFja3Mgb3Igb3RoZXIgcHJvYmxlbSBpbmNpZGVudHMuDSBUaGUgY3VycmVudCBwcm9jZXNz
IG9mIG5ldHdvcmsgYW5hbHlzaXMgYW5kIGZvcmVuc2ljcyBmb2xsb3dzIGEgYm90dG9tIHVwIGFw
cHJvYWNoLCB3aGVyZSB0aGUgdHJhZmZpYyBpcyB0cmFjZWQgYmFjaywgaG9wLWJ5LWhvcCBzdGFy
dGluZyBmcm9tIHRoZSB2aWN0aW0gYmFjayB0byB0aGUgc291cmNlIG9mIGF0dGFjay4NDUEgdmFy
aWV0eSBvZiBJUCB0cmFjZWJhY2sgdGVjaG5pcXVlcyBleGlzdC4gVGhleSBhcmUgYXMgZm9sbG93
czoNDTEpIEluZ3Jlc3MgRmlsdGVyaW5nDTIpIExpbmsgVGVzdGluZyANMykgSW5wdXQgRGVidWdn
aW5nDTQpIENvbnRyb2wgRmxvb2RpbmcNNSkgSUNNUCBUcmFjZSBCYWNrDQ1TdWNoIGEgdHJhY2Ug
YmFjayBpbnZvbHZlcyBoZSB1c2Ugb2YgdmFyaW91cyB0b29scyBzdWNoIGFzIHRyYWNlIHJvdXRl
LCBwaW5nIHBhY2tldHMsIHJldmVyc2UgRE5TIGxvb2t1cCBldGMuVGhpcyBtZXRob2Qgb2YgdHJh
Y2luZyB0aGUgc291cmNlIG9mIGF0dGFjayBiYWNrd2FyZHMsIHN0YXJ0aW5nIGZyb20gdGhlIHZp
Y3RpbSBub2RlLCBoYXMgaXRzIG93biBzaG9ydGNvbWluZ3MuIE9mdGVuIGZpcmV3YWxscyBpbiB0
aGUgcGF0aCBibG9jayB0aGUgdHJhY2Ugcm91dGVzLCBzbyB0aGUgbmV0d29yayBhZG1pbmlzdHJh
dG9yknMgYWJpbGl0eSB0byBhbmFseXplIHRoZSB0cmFmZmljIGlzIGxpbWl0ZWQgdG8gdGhlIG5l
dHdvcmsgaW4gaGlzL2hlciBjb250cm9sLCB0aGVyZWZvcmUgYSBzdWNjZXNzZnVsIHRyYWNlIGJh
Y2sgcmVxdWlyZXMgdGhlIGNvb3BlcmF0aW9uIG9mIGEgbnVtYmVyIG9mIGFkbWluaXN0cmF0b3Jz
Lg0gICAgICAgICAgICAgICAgICAgICAgICANSW4gSVB2NCB0aGVyZSBpcyBhbiBvcHRpb24gb2Yg
kXJlY29yZCByb3V0ZZIuIFdoZW4gdGhpcyBvcHRpb24gaXMgc2V0LCB0aGUgcm91dGVycyBpbiB0
aGUgcGF0aCBlbWJlZCB0aGVpciBJUCBhZGRyZXNzZXMgaW4gdGhlIHBhY2tldC4gVmFyaW91cyBy
ZXNlYXJjaGVycyBoYXZlIHN1Z2dlc3RlZCBwYWNrZXQgbWFya2luZywgdXNpbmcgdGhpcyBvcHRp
b24uIFRoZSB0ZWNobmlxdWUgd2lsbCBlbGltaW5hdGUgYXR0YWNrZXKScyBhYmlsaXR5IHRvIGNv
bmNlYWwgdGhlIHRydWUgc291cmNlLCBidXQgdGhlIG1ham9yIGRyYXdiYWNrIGlzIHRoYXQgYW55
IHN1Y2ggbWFya2luZyB0ZWNobmlxdWUgd291bGQgbmVlZCB0byBiZSBpbXBsZW1lbnRlZCBnbG9i
YWxseSwgaW4gb3JkZXIgdG8gYmUgZWZmZWN0aXZlLg0gICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIA1TaW5jZSB0aGUgSVB2NiBzdGFuZGFyZCBpcyBzdGlsbCB1bmRlciBkZXZl
bG9wbWVudCwgd2UgcHJvcG9zZSB0byBpbmNsdWRlIGNlcnRhaW4gZmVhdHVyZXMgaW4gdGhlIHN0
YW5kYXJkIHdoaWNoIHdpbGwgbWFrZSBuZXR3b3JrIGZvcmVuc2ljcyBmYXN0IGFuZCBlYXN5Lg1U
aGUgk1BvaW50IG9mIE9yaWdpbpQgaW5mb3JtYXRpb24gd2hpY2ggd2UgcHJvcG9zZSB0byBlbWJl
ZCBpbiB0aGUgSVB2NiBoZWFkZXIgd2lsbCBoYXZlIHR3byBjb21wb25lbnRzOg0NMSkgVGhlIGhh
cmR3YXJlIGFkZHJlc3Mgb2YgdGhlIHNvdXJjZSBub2RlLg0yKSBUaGUgSVAgYWRkcmVzcyBvZiB0
aGUgaW5jb21pbmcgaW50ZXJmYWNlIG9mIHRoZSBmaXJzdCByb3V0ZXIgd2hpY2ggdGhlIHBhY2tl
dCB3aWxsIGVuY291bnRlci4NDVdlIGludGVuZCB0byBwcm9wb3NlIHJlbGV2YW50IGZpZWxkcyBp
biB0aGUgSVB2NiBoZWFkZXIgd2hpY2ggd2lsbCBtYWtlIGl0IGEgc3RhbmRhcmQgdG8gaW5jbHVk
ZSB0aGlzIJNQb2ludCBvZiBPcmlnaW6UIGluZm9ybWF0aW9uIGluIGV2ZXJ5IHBhY2tldCBvbiB0
aGUgaW50ZXJuZXQuIFRoZSB0ZWNobmlxdWUgaGFzIG1hbnkgYWR2YW50YWdlczoNDTEpIEl0IHdp
bGwgbWFrZSBzcG9vZmluZyBkaWZmaWN1bHQgZm9yIHRoZSBhdHRhY2tlcnMgYmVjYXVzZSBub3cg
dGhleSB3aWxsIGhhdmUgdG8gc3Bvb2YsICAgICBub3Qgb25seSB0aGVpciBJUCBhZGRyZXNzIGFu
ZCBoYXJkd2FyZSBhZGRyZXNzIGJ1dCBhbHNvIHRoZSBhZGRyZXNzIG9mIHRoZSBmaXJzdCByb3V0
ZXIgd2hpY2ggdGhlIHBhY2tldCB3aWxsIGVuY291bnRlci4NVGhpcyB3aWxsIHByZXZlbnQgdGhl
IGF0dGFja2VycyBmcm9tIHRha2luZyBhZHZhbnRhZ2Ugb2YgdGhlIGFub255bWl0eSB3aGljaCBl
eGlzdHMgaW4gdGhlIGludGVybmV0IHRvZGF5Lg0NMikgSXQgd2lsbCBiZSBlZmZlY3RpdmUgaW4g
Y2FzZXMgd2hlcmUgdGhlIGF0dGFja2VyIHVzZXMgWm9tYmllcyAob3IgcmVmbGVjdG9ycyk7IHRo
ZXNlIGFyZSB0aGUgdW5zdXNwZWN0aW5nIG5vZGVzLCB3aGljaCBhcmUgdXNlZCBhcyBzbGF2ZXMg
dG8gY2Fycnkgb3V0IGEgcGFja2V0IHN0b3JtIGF0dGFjayAobGlrZSBpbiBkaXN0cmlidXRlZCBk
ZW5pYWwgb2Ygc2VydmljZSBhdHRhY2spLiBJbiBldmVudCBvZiBzdWNoIGFuIGF0dGFjayB0aGUg
k1BvaW50IG9mIE9yaWdpbpQgZmllbGQgd2lsbCBiZSB1c2VkIHRvIGlkZW50aWZ5IHRoZSB6b21i
aWVzIGFuZCB0aGUgbmV0d29ya3MgdG8gd2hpY2ggdGhleSBiZWxvbmcuIA0NMykgSXQgd2lsbCBw
cmV2ZW50IGVtYWlsIHNwb29maW5nLCBiZWNhdXNlIHRoZSByZWNlaXZlciBvZiBhIHN1c3BpY2lv
dXMgZW1haWwgY2FuIGNoZWNrIGl0cyCTUG9pbnQgb2YgT3JpZ2lulCB1c2luZyB0aGUgcHJvcG9z
ZWQgZmllbGQgaW4gdGhlIElQdjYgaGVhZGVyLiANDVNpbWlsYXJseSB0aGVyZSBhcmUgbWFueSBh
ZHZhbnRhZ2VzIG9mIHRoaXMgYXBwcm9hY2ggdmlzLeAtdmlzLCBob3AgdG8gaG9wIHRyYWNlIGJh
Y2ssIHdlIGludGVuZCB0byBleHBsb3JlIGFuZCBoaWdobGlnaHQgdGhlc2UgYWR2YW50YWdlcyBk
dXJpbmcgdGhlIGNvdXJzZSBvZiBwcm9qZWN0IHdvcmsuDVdlIGFsc28gaW50ZW5kIHRvIGFuYWx5
emUgdGhlIHNob3J0Y29taW5ncyBhbmQgZHJhd2JhY2tzIG9mIHN1Y2ggYSBzY2hlbWUsIGFuZCBz
dWdnZXN0IGFuIG9wdGltYWwgbmV0d29yayBmb3JlbnNpYyB0ZWNobmlxdWUgZm9yIGFuIElwdjYg
cGFja2V0LCB1c2luZyB0aGUgbmV3IJNwb2ludCBvZiBvcmlnaW6UIGluZm9ybWF0aW9uIHdoaWNo
IHdlIGludGVuZCB0byBlbWJlZCBpbiB0aGUgSXB2NiBzdGFuZGFyZC4NDUFzIGZhciBhcyB0aGUg
cHJhY3RpY2FsIGFzcGVjdCBvZiBvdXIgc3R1ZHkgaXMgY29uc2lkZXJlZCB3ZSB3aWxsIGF0dGVt
cHQgdG8gc2ltdWxhdGUgdGhlIElQdjYgZW52aXJvbm1lbnQgdXNpbmcgc3RhbmRhcmQgbmV0d29y
ayBzaW11bGF0b3JzLiBPbmNlIHRoaXMgaXMgYWNoaWV2ZWQgd2Ugd2lsbCBjb21wYXJlIHRoZSBl
eGlzdGluZyBmb3JlbnNpY3MgdGVjaG5pcXVlcyB3aXRoIG91ciBwcm9wb3NlZCBzb2x1dGlvbi4N
DQ0NVGhlIHN0dWR5IHdpbGwgaGF2ZSBmYXIgcmVhY2hpbmcgaW1wbGljYXRpb25zIGFzIElQdjYg
aXMgc3RpbGwgYW4gZXZvbHZpbmcgdGVjaG5vbG9neSBhbmQgaGVuY2Ugb3BlbiB0byBjaGFuZ2Vz
LiBPdXIgdGVhbSBoYXMgYWxyZWFkeSByZWdpc3RlcmVkIHdpdGggdGhlIEludGVybmV0IEVuZ2lu
ZWVyaW5nIFRhc2sgRm9yY2UgKElFVEYpIHdvcmtpbmcgZ3JvdXAgZm9yIElQdjYgZGV2ZWxvcG1l
bnQsIGFuZCB3ZSBhcmUgb24gdGhlIElFVEYgbWFpbGluZyBsaXN0LiBPbmNlIG91ciBzdHVkeSBp
cyBjb21wbGV0ZWQsIHdlIGludGVuZCB0byBjb252ZXkgdGhlIHJlc3VsdHMgdG8gYWxsIHRoZSBt
ZW1iZXJzIG9mIHRoZSB3b3JraW5nIGdyb3VwLiBXZSBob3BlIGFuZCB3ZSBwcmF5IHRoYXQgc3Vn
Z2VzdGlvbnMgd2lsbCBmaW5kIGEgcGxhY2UgaW4gdGhlIGZpbmFsIElQdjYgc3RhbmRhcmQuDQAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABgAACQgAABEIAACA
CAAAmwgAAJwIAACdCAAAyQgAANIIAADdCAAA7wgAAAYJAAARCQAAEgkAAB0JAAAwCQAANgkAAFUJ
AABWCQAAewkAAIIJAACWCQAAlwkAAJgJAACbCQAAogkAAKQJAACsCQAArQkAAK4JAACwCQAAtAkA
ALYJAAC8CQAAvgkAAMEJAADGCQAAyAkAANAJAADRCQAA1AkAANsJAADdCQAA5AkAAOUJAADoCQAA
7AkAAO0JAAD0CQAA9wkAAPgJAAD5CQAA+gkAAAAKAAAKCgAAEgoAABQKAAA0CgAAPwoAAGYKAABq
CgAAdQoAAIAKAAD8CgAACAsAAAoLAAD68u7q7uru6u7i7t7u6u7q7ure2tbe6trOycHW2rqyyarW
2rLJqtbassmq1tqyqsmy1qbW7tru6u7a7uru3u7a6gAAAAYWaAU/OAAADxVojFHoABZoNHRLADUI
gQ8VaIxR6AAWaK8kowA1CIEMFWj7VJUAFmivJKMAAA8VaPtUlQAWaDR0SwA1CIEJFmiMUegANQiB
DxVo+1SVABZorySjADUIgQYWaDR0SwAABhZorySjAAAGFmjmRpAAAA8VaCIU7wAWaFVYGwA1CIEG
Fmh7aXsAAAYWaFVYGwAADxVoqnnPABZoVVgbADUIgQkWaNI2lwA1CIEAQQAGAACcCAAAVQkAAFYJ
AACXCQAAmAkAAK0JAAC+CQAA0QkAAOUJAAD4CQAA+QkAANALAADpCwAAfQ0AAKQNAABADgAAqQ4A
AKoOAADWDgAANw8AADgPAAAAEAAAARAAANgQAABDEQAARBEAAPcAAAAAAAAAAAAAAAD3AAAAAAAA
AAAAAAAA9wAAAAAAAAAAAAAAAPcAAAAAAAAAAAAAAAD3AAAAAAAAAAAAAAAA9wAAAAAAAAAAAAAA
APcAAAAAAAAAAAAAAAD3AAAAAAAAAAAAAAAA9wAAAAAAAAAAAAAAAOcAAAAAAAAAAAAAAAD3AAAA
AAAAAAAAAAAA9wAAAAAAAAAAAAAAAPcAAAAAAAAAAAAAAAD3AAAAAAAAAAAAAAAA9wAAAAAAAAAA
AAAAAPcAAAAAAAAAAAAAAAD3AAAAAAAAAAAAAAAA9wAAAAAAAAAAAAAAAPcAAAAAAAAAAAAAAAD3
AAAAAAAAAAAAAAAA9wAAAAAAAAAAAAAAAPcAAAAAAAAAAAAAAAD3AAAAAAAAAAAAAAAA9wAAAAAA
AAAAAAAAAPcAAAAAAAAAAAAAAAD3AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAPAAADJAMP
hNACEYQw/V6E0AJghDD9YSQDZ2SMUegAAAcAAAMkA2EkA2dk+1SVAAAaAAYAAJkXAAD9AAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEBAABAQEKCwAAGQsAACgLAAA0CwAA
OwsAAEsLAABSCwAAdAsAAHULAAB2CwAAfwsAAI0LAACXCwAA0AsAAOcLAADoCwAA6QsAAOwLAADv
CwAA8AsAAAcMAAAVDAAAKwwAAC8MAABoDAAAoQwAAKIMAAD4DAAAWQ0AAGUNAAB9DQAApA0AAK4N
AACxDQAAsg0AAAIOAAAODgAARA4AAFUOAACDDgAAjg4AAKkOAACqDgAAsQ4AAMEOAADdDgAAFQ8A
ADcPAAA4DwAAaA8AAHAPAADTDwAA6w8AAAAQAAABEAAABhAAAAcQAAAREAAAIxAAAFQQAABaEAAA
WxAAAF8QAAB4EAAA1xAAAEMRAABEEQAASREAAFsRAAB9EQAA/Pj89Pz0+PT8+Pz0/PD88Ozk3Pzc
/PT88Pjw2OzY/OzQyMTAxMjEyMS8xMjEyMS8xOzE7Li8wLjssOzA7LjsuMTswOy4AAAADxVoLjp2
ABZo9DpIADUIgQYWaL0iCQAABhZoBT84AAAGFmivJKMAAAYWaCFeaAAADxVopVxJABZoIV5oADUI
gQ8VaKVcSQAWaPQ6SAA1CIEGFmjsGIkAAA8VaCIU7wAWaFVYGwA1CIEPFWgiFO8AFmj0OkgANQiB
BhZo9DpIAAAGFmg0dEsAAAYWaOZGkAAABhZoe2l7AAAGFmhVWBsARX0RAACGEQAAlBEAAJURAADt
EQAA9REAAKYSAACpEgAArhIAALQSAADCEgAAyhIAANMSAABEEwAARRMAAEYTAAByEwAAfhMAAIET
AACFEwAAhhMAAJETAACbEwAA8xMAAPQTAAA3FAAAPhQAAN4UAADfFAAA4BQAAFsVAABjFQAAbRUA
AG8VAACiFQAA0hUAANMVAADWFQAAAxYAAA8WAAAVFgAAFxYAACsWAABGFgAASBYAAEoWAABvFgAA
cBYAAJEWAACVFgAAlhYAAPIWAAD8FgAAXhcAAF8XAABvFwAAgxcAAIkXAACPFwAAmBcAAJkXAAD3
7+vn4+ff4+fv9+Pb59fb49vj28/329fL48vHw8e7s9fH18fbw9vDr9vDr8Pbr6efp9uv26/j28Pb
49sAAAAAAAAAAAAAAAAAAA8VaCIU7wAWaFpO5AA1CIEPFWgiFO8AFmjkF54ANQiBBhZo5BeeAAAP
FWgiFO8AFmghXmgANQiBDxVoIhTvABZob0m2ADUIgQYWaFVYGwAABhZob0m2AAAGFmgaY48AAA8V
aC46dgAWaFpO5AA1CIEGFmghXmgAAAYWaFpO5AAABhZo9DpIAAAGFmivJKMAAAYWaL0iCQAABhZo
71QNAAAPFWguOnYAFmi9IgkANQiBDxVoLjp2ABZorySjADUIgQA8RBEAAKgSAACpEgAARRMAAEYT
AAD0EwAA4BQAAOEUAADTFQAA1BUAANUVAADWFQAAmRcAAPcAAAAAAAAAAAAAAAD3AAAAAAAAAAAA
AAAA9wAAAAAAAAAAAAAAAPcAAAAAAAAAAAAAAAD3AAAAAAAAAAAAAAAA9wAAAAAAAAAAAAAAAPcA
AAAAAAAAAAAAAAD3AAAAAAAAAAAAAAAA9wAAAAAAAAAAAAAAAPcAAAAAAAAAAAAAAAD3AAAAAAAA
AAAAAAAA9wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAABwAAAyQDYSQDZ2T7VJUAAAwsADGQaAEfsNAvILDgPSGwCAci
sAgHI5CgBSSQoAUlsAAAF7DQAhiw0AIMkNACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIYCEQASAAEAnAAPAAQAAAAAAAAA
AAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AEAAAEDx/wIAQAAMAAAAAAAAAAAABgBOAG8AcgBtAGEAbAAAAAIAAAAYAENKGABfSAEEYUoYAG1I
CQRzSAkEdEgJBAAAAAAAAAAAAAAAAAAAAAAAAEQAQUDy/6EARAAMAQAAAAAAAAAAFgBEAGUAZgBh
AHUAbAB0ACAAUABhAHIAYQBnAHIAYQBwAGgAIABGAG8AbgB0AAAAAABWAGkA8/+zAFYADAUAAAAA
AAAAAAwAVABhAGIAbABlACAATgBvAHIAbQBhAGwAAAAgADpWCwAX9gMAADTWBgABBQMAADTWBgAB
CgNsAGH2AwAAAgALAAAAKABrAPT/wQAoAAAFAAAAAAAAAAAHAE4AbwAgAEwAaQBzAHQAAAACAAwA
AAAAAC4AWECiAPEALgAMAAAAAAAAAAAACABFAG0AcABoAGEAcwBpAHMAAAAGADYIgV0IgTYAVUCi
AAEBNgAMAAAAAAAAAAAACQBIAHkAcABlAHIAbABpAG4AawAAAAwAPioBQioCcGgAAP8AAAAAAJkP
AAAFAAAkAAAAAP////8AAAAAnAAAAFUBAABWAQAAlwEAAJgBAACtAQAAvgEAANEBAADlAQAA+AEA
APkBAADQAwAA6QMAAH0FAACkBQAAQAYAAKkGAACqBgAA1gYAADcHAAA4BwAAAAgAAAEIAADYCAAA
QwkAAEQJAACoCgAAqQoAAEULAABGCwAA9AsAAOAMAADhDAAA0w0AANQNAADVDQAA1g0AAJsPAABJ
iAAwAAAAAAAAAAABAAAAAAAAAAAAAAAAAAABSYgAMAAAAAAAAAAAAQAAAAAAAAAAAAAAAACAAUmI
ADAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAgAFJiAAwAAAAAAAAAAABAAAAAAAAAAAAAAAAAIABSYgA
MAAAAAAAAAAAAQAAAAAAAAAAAAAAAACAAUmIADAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAgAFJiAAw
AAAAAAAAAAABAAAAAAAAAAAAAAAAAIABSYgAMAAAAAAAAAAAAQAAAAAAAAAAAAAAAACAAUmIADAA
AAAAAAAAAAEAAAAAAAAAAAAAAAAAgAFJiAAwAAAAAAAAAAABAAAAAAAAAAAAAAAAAIABSYgAMAAA
AAAAAAAAAQAAAAAAAAAAAAAAAACAAUmIADAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAgAFJiAAwAAAA
AAAAAAABAAAAAAAAAAAAAAAAAIABSYgAMAAAAAAAAAAAAQAAAAAAAAAAAAAAAACAAUmIADAAAAAA
AAAAAAEAAAAAAAAAAAAAAAAAgAFJiAAwAAAAAAAAAAABAAAAAAAAAAAAAAAAAIABSYgAMAAAAAAA
AAAAAQAAAAAAAAAAAAAAAACAAUmIADAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAgAFJiAAwAAAAAAAA
AAABAAAAAAAAAAAAAAAAAIABSYgAMAAAAAAAAAAAAQAAAAAAAAAAAAAAAACAAUmIADAAAAAAAAAA
AAEAAAAAAAAAAAAAAAAAgAFJiAAwAAAAAAAAAAABAAAAAAAAAAAAAAAAAIABSYgAMAAAAAAAAAAA
AQAAAAAAAAAAAAAAAACAAUmIADAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAgAFJiAAwAAAAAAAAAAAB
AAAAAAAAAAAAAAAAAIABSYgAMAAAAAAAAAAAAQAAAAAAAAAAAAAAAACAAUmIADAAAAAAAAAAAAEA
AAAAAAAAAAAAAAAAgAFJiAAwAAAAAAAAAAABAAAAAAAAAAAAAAAAAIABSYgAMAAAAAAAAAAAAQAA
AAAAAAAAAAAAAACAAUmIADAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAgAFJiAAwAAAAAAAAAAABAAAA
AAAAAAAAAAAAAIABSYgAMAAAAAAAAAAAAQAAAAAAAAAAAAAAAACAAUmIADAAAAAAAAAAAAEAAAAA
AAAAAAAAAAAAgAFJiAAwAAAAAAAAAAABAAAAAAAAAAAAAAAAAIABSYgAMAAAAAAAAAAAAQAAAAAA
AAAAAAAAAACAAUmIADAAAAAAAAAAAAEAAAAAAAAAAAAAAAAAgAFJiAAwAAAAAAAAAAABAAAAAAAA
AAAAAAAAAIABSYgAMAAAAAAAAAAAAQAAAAAAAAAAAAAAAACAAQAGAAAKCwAAfREAAJkXAAAMAAAA
DwAAABAAAAAABgAARBEAAJkXAAANAAAAEQAAAAAGAACZFwAADgAAAAAAAACbDwAABwAAAAAAmw8A
AAcAAAAAAJsPAAAHAAAAAACbDwAABwABAIxZKwbIb+wg/w//D/8P/w//D/8P/w//D/8PEAABAAAA
FwAAAAAAAAAAAAAAAAAAAAAAAAAPGAAAD4TQAhGEmP4VxgUAAdACBl6E0AJghJj+Q0oUAE9KAQBR
SgEAbygAAQC38AEAAAAXgAAAAAAAAAAAAAAAAAAAAAAAAA8YAAAPhKAFEYSY/hXGBQABoAUGXoSg
BWCEmP5DShQAT0oDAFFKAwBvKAABAG8AAQAAABeAAAAAAAAAAAAAAAAAAAAAAAAADxgAAA+EcAgR
hJj+FcYFAAFwCAZehHAIYISY/kNKFABPSgQAUUoEAG8oAAEAp/ABAAAAF4AAAAAAAAAAAAAAAAAA
AAAAAAAPGAAAD4RACxGEmP4VxgUAAUALBl6EQAtghJj+Q0oUAE9KBABRSgQAbygAAQCn8AEAAAAX
gAAAAAAAAAAAAAAAAAAAAAAAAA8YAAAPhBAOEYSY/hXGBQABEA4GXoQQDmCEmP5DShQAT0oEAFFK
BABvKAABAKfwAQAAABeAAAAAAAAAAAAAAAAAAAAAAAAADxgAAA+E4BARhJj+FcYFAAHgEAZehOAQ
YISY/kNKFABPSgQAUUoEAG8oAAEAp/ABAAAAF4AAAAAAAAAAAAAAAAAAAAAAAAAPGAAAD4SwExGE
mP4VxgUAAbATBl6EsBNghJj+Q0oUAE9KBABRSgQAbygAAQCn8AEAAAAXgAAAAAAAAAAAAAAAAAAA
AAAAAA8YAAAPhIAWEYSY/hXGBQABgBYGXoSAFmCEmP5DShQAT0oEAFFKBABvKAABAKfwAQAAABeA
AAAAAAAAAAAAAAAAAAAAAAAADxgAAA+EUBkRhJj+FcYFAAFQGQZehFAZYISY/kNKFABPSgQAUUoE
AG8oAAEAp/ABAAAAjFkrBgAAAAAAAAAAAAAAAP///////wEAAAAAAP//AQAAABIAkK/AqWKfWM4w
XirrpO+q7PBEsDCyIkoYPtPqZ9wRFqC6D9ZiGQAAAAQAAAAIAAAA5QAAAAAAAAAYAAAAMnsBAL0i
CQDvVA0AVVgbAAU/OAD0OkgApVxJADR0SwAhXmgALjp2AHtpewDsGIkAGmOPAOZGkACNfZMA+1SV
ANI2lwDkF54ArySjAG9JtgCqec8AWk7kAIxR6AAiFO8AEVP2AP9AAIABAAAAAAAAAAAANClDAQEA
AAAAAAAAAAAAAAAAAAAAAAAAAhAAAAAAAAAAmQ8AAFAAABAAQAAA//8BAAAABwBVAG4AawBuAG8A
dwBuAP//AQAIAAAAAAAAAAAAAAD//wEAAAAAAP//AAACAP//AAAAAP//AAACAP//AAAAAAUAAABH
FpABAAACAgYDBQQFAgMEh3oAIAAAAIAIAAAAAAAAAP8BAAAAAAAAVABpAG0AZQBzACAATgBlAHcA
IABSAG8AbQBhAG4AAAA1FpABAgAFBQECAQcGAgUHAAAAAAAAABAAAAAAAAAAAAAAAIAAAAAAUwB5
AG0AYgBvAGwAAAAzJpABAAACCwYEAgICAgIEh3oAIAAAAIAIAAAAAAAAAP8BAAAAAAAAQQByAGkA
YQBsAAAAPzWQAQAAAgcDCQICBQIEBId6ACAAAACACAAAAAAAAAD/AQAAAAAAAEMAbwB1AHIAaQBl
AHIAIABOAGUAdwAAADsGkAECAAUAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAAAAAAAAgAAAAABXAGkA
bgBnAGQAaQBuAGcAcwAAACIABADxCIgYAPDQAgAAaAEAAAAA4U24huFNuIYAAAAAAgADAAAAUwIA
AEYNAAABAAcAAAAEAAMQHAAAAFMCAABGDQAAAQAHAAAAHAAAAAAAAAAhAwDwEAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAIB6AFtAC0AIGBcjQAAAAAAAAAAAAAAAAAAJIPAACSDwAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAgAA
AAAAAAAAAAUyg1EA8BAACNwDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAASFAAAAAAKPD/DwEA
AT8AAOQEAAD///9/////f////3////9/////f////3////9/5kaQAAAAAAAyAAAAAAAAAAAAAAAA
AAAAAAD//xIAAAAAAAAAfgBOAGUAdAB3AG8AcgBrACAAZgBvAHIAZQBuAHMAaQBjAHMAIABpAHMA
IAB0AGgAZQAgAGMAYQBwAHQAdQByAGUALAAgAHIAZQBjAG8AcgBkAGkAbgBnACwAIABhAG4AZAAg
AGEAbgBhAGwAeQBzAGkAcwAgAG8AZgAgAG4AZQB0AHcAbwByAGsAIABlAHYAZQBuAHQAcwAgAGkA
bgAgAG8AcgBkAGUAcgAgAHQAbwAgAGQAaQBzAGMAbwB2AGUAcgAgAHQAaABlACAAcwBvAHUAcgBj
AGUAIABvAGYAIABzAGUAYwB1AHIAaQB0AHkAIABhAHQAdABhAGMAawAAAAAAAAAIAFcAZQBiAFcA
bwByAGwAZAAEAGIAYQBiAGEAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAAABgAAAAEAAAAAAAwAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/v8AAAUBAgAAAAAAAAAAAAAAAAAAAAAAAQAAAOCF
n/L5T2gQq5EIACsns9kwAAAA6AEAABEAAAABAAAAkAAAAAIAAACYAAAAAwAAACABAAAEAAAALAEA
AAUAAABAAQAABgAAAEwBAAAHAAAAWAEAAAgAAABoAQAACQAAAHgBAAASAAAAhAEAAAoAAACkAQAA
DAAAALABAAANAAAAvAEAAA4AAADIAQAADwAAANABAAAQAAAA2AEAABMAAADgAQAAAgAAAOQEAAAe
AAAAgAAAAE5ldHdvcmsgZm9yZW5zaWNzIGlzIHRoZSBjYXB0dXJlLCByZWNvcmRpbmcsIGFuZCBh
bmFseXNpcyBvZiBuZXR3b3JrIGV2ZW50cyBpbiBvcmRlciB0byBkaXNjb3ZlciB0aGUgc291cmNl
IG9mIHNlY3VyaXR5IGF0dGFjawAAHgAAAAQAAAAAAAAAHgAAAAwAAABXZWJXb3JsZAAAAAAeAAAA
BAAAAAAAAAAeAAAABAAAAAAAAAAeAAAACAAAAE5vcm1hbAAAHgAAAAgAAABiYWJhAAAAAB4AAAAE
AAAAMgAAAB4AAAAYAAAATWljcm9zb2Z0IE9mZmljZSBXb3JkAAAAQAAAAADSSWsAAAAAQAAAAAAi
qoWv2scBQAAAAAAiqoWv2scBAwAAAAEAAAADAAAAUwIAAAMAAABGDQAAAwAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAP7/AAAFAQIAAAAAAAAAAAAAAAAAAAAAAAEAAAAC1c3VnC4bEJOX
CAArLPmuMAAAAHABAAAMAAAAAQAAAGgAAAAPAAAAcAAAAAUAAACEAAAABgAAAIwAAAARAAAAlAAA
ABcAAACcAAAACwAAAKQAAAAQAAAArAAAABMAAAC0AAAAFgAAALwAAAANAAAAxAAAAAwAAABPAQAA
AgAAAOQEAAAeAAAADAAAAFJlbGlhbmNlAAAAAAMAAAAcAAAAAwAAAAcAAAADAAAAkg8AAAMAAADm
FQsACwAAAAAAAAALAAAAAAAAAAsAAAAAAAAACwAAAAAAAAAeEAAAAQAAAH8AAABOZXR3b3JrIGZv
cmVuc2ljcyBpcyB0aGUgY2FwdHVyZSwgcmVjb3JkaW5nLCBhbmQgYW5hbHlzaXMgb2YgbmV0d29y
ayBldmVudHMgaW4gb3JkZXIgdG8gZGlzY292ZXIgdGhlIHNvdXJjZSBvZiBzZWN1cml0eSBhdHRh
Y2sADBAAAAIAAAAeAAAABgAAAFRpdGxlAAMAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAABAAAAAgAAAAMAAAAEAAAABQAAAAYAAAAHAAAACAAAAAkAAAAKAAAACwAAAAwA
AAANAAAADgAAAA8AAAAQAAAAEQAAABIAAAD+////FAAAABUAAAAWAAAAFwAAABgAAAAZAAAAGgAA
ABsAAAAcAAAA/v///x4AAAAfAAAAIAAAACEAAAAiAAAAIwAAACQAAAD+////JgAAACcAAAAoAAAA
KQAAACoAAAArAAAALAAAAP7////9////LwAAAP7////+/////v//////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
/////////////1IAbwBvAHQAIABFAG4AdAByAHkAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAWAAUB//////////8DAAAABgkCAAAAAADAAAAAAAAARgAAAAAAAAAA
AAAAAFAD8qKv2scBMQAAAIAAAAAAAAAAMQBUAGEAYgBsAGUAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA4AAgH/////BQAAAP////8AAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAATAAAAGhIAAAAAAABXAG8AcgBkAEQAbwBjAHUAbQBl
AG4AdAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAGgACAQEAAAD/////
/////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAuJAAAAAAAAAUAUwB1
AG0AbQBhAHIAeQBJAG4AZgBvAHIAbQBhAHQAaQBvAG4AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAoAAIBAgAAAAQAAAD/////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHQAA
AAAQAAAAAAAABQBEAG8AYwB1AG0AZQBuAHQAUwB1AG0AbQBhAHIAeQBJAG4AZgBvAHIAbQBhAHQA
aQBvAG4AAAAAAAAAAAAAADgAAgH///////////////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAlAAAAABAAAAAAAAABAEMAbwBtAHAATwBiAGoAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEgACAP///////////////wAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABxAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA////////////
////AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAD///////////////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAABAAAA/v//////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////
/////////wEA/v8DCgAA/////wYJAgAAAAAAwAAAAAAAAEYfAAAATWljcm9zb2Z0IE9mZmljZSBX
b3JkIERvY3VtZW50AAoAAABNU1dvcmREb2MAEAAAAFdvcmQuRG9jdW1lbnQuOAD0ObJxAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAA
------=_Part_96678_9680180.1186760792983
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

------=_Part_96678_9680180.1186760792983--




From ipv6-bounces@ietf.org Fri Aug 10 11:56:55 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJWpQ-0007Vt-On; Fri, 10 Aug 2007 11:55:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJWpO-0007Uw-Fp
	for ipv6@ietf.org; Fri, 10 Aug 2007 11:55:06 -0400
Received: from poy.chewa.net ([2002:c2f2:7249::1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IJWpO-0000Up-3u
	for ipv6@ietf.org; Fri, 10 Aug 2007 11:55:06 -0400
Received: from auguste.remlab.net (unknown
	[IPv6:2002:3e4e:969c:0:20d:60ff:fe38:6d16])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested) (Authenticated sender: remi)
	by poy.chewa.net (Postfix) with ESMTP id 3C626967DE;
	Fri, 10 Aug 2007 17:55:05 +0200 (CEST)
From: =?utf-8?q?R=C3=A9mi_Denis-Courmont?= <rdenis@simphalempin.com>
Organization: Remlab.net
To: "ather zaidi" <syedatherzaidi@gmail.com>
Date: Fri, 10 Aug 2007 18:55:04 +0300
User-Agent: KMail/1.9.7
References: <632b361b0708100846t1137c638ne6f951f60673ef31@mail.gmail.com>
In-Reply-To: <632b361b0708100846t1137c638ne6f951f60673ef31@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200708101855.05835@auguste.remlab.net>
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: ipv6@ietf.org
Subject: Re: modifications in ipv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Le vendredi 10 ao=C3=BBt 2007, ather zaidi a =C3=A9crit :
> I am a final year engineering student in India, as part of our final
> year project we are working on some modifications in ipv6 header
> format .

You're quite a bit late in the game. The IPv6 header format has been=20
frozen over 10 years ago. Also, this mailing list is about maintaining=20
the IPv6 protocol, not extending it (anymore).

=2D-=20
R=C3=A9mi Denis-Courmont
http://www.remlab.net/

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



From ipv6-bounces@ietf.org Fri Aug 10 15:17:03 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJZwr-0005Ou-RL; Fri, 10 Aug 2007 15:15:01 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJZwq-0005Om-Q7
	for ipv6@ietf.org; Fri, 10 Aug 2007 15:15:00 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IJZwp-0003Xr-T0
	for ipv6@ietf.org; Fri, 10 Aug 2007 15:15:00 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 10 Aug 2007 15:14:59 -0400
X-IronPort-AV: i="4.19,245,1183348800"; 
	d="scan'208,217"; a="67682153:sNHT94755998"
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 l7AJExDt000318; 
	Fri, 10 Aug 2007 15:14:59 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l7AJEtmd014979; 
	Fri, 10 Aug 2007 19:14:55 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, 10 Aug 2007 15:14:54 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 10 Aug 2007 15:14:54 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D03824987@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D036FEC97@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New version of draft-wbeebee-nd-implementation-pitfalls is
	available - 2nd try
Thread-Index: AcfNcNF6KgZDeLWCSYyZTOwbbpFkzwOEWGJg
References: <B00EDD615E3C5344B0FFCBA910CF7E1D036FEC97@xmb-rtp-20e.amer.cisco.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>, <ipv6@ietf.org>
X-OriginalArrivalTime: 10 Aug 2007 19:14:54.0826 (UTC)
	FILETIME=[BBEA14A0:01C7DB82]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=13153; t=1186773299;
	x=1187637299; 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=20New=20version=20of=20draft-wbeebee-nd-implementation-
	pitfalls=20is=20available=20-=202nd=20try |Sender:=20
	|To:=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>,
	=20<ipv6@ie tf.org>;
	bh=1HVPcNUyko8bBcbJN4NlKLdy3Qyo7eUA7eaFZkmpb5c=;
	b=swLr727LIQSRHfdOtPTz/3eLDvIsgJlZtqDCclmug3eYK00z/VRNCMHGbMqxR7iW2cNkk7sS
	0oBeyvUT7I5rXA+2HiVNalaDoRlumaQr6+QpKNr5bi7g3xJKVFzHFvZU;
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: 2d133cc328f58695161c98bb4f4dc213
Cc: varada@txc.com
Subject: RE: New version of draft-wbeebee-nd-implementation-pitfalls is
	available - 2nd try
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0862643619=="
Errors-To: ipv6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0862643619==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7DB82.BBCAEF55"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7DB82.BBCAEF55
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

IETF IPv6 Community,
=20
Please review the -02 version of our I-D. In particular, we'd like
reviewers to focus on our proposed changes to 2461bis.
=20
We would like to specify on-link vs. off-link determination more clearly
for ALL IPv6 hosts.  On-link vs. off-link determines data forwarding and
address resolution behavior for a host.
=20
We present a very important problem that relates to an aggregator router
network used in deployments listed below (thanks to Adeel Ahmed for
providing the list):
=20
- Wholesale Dial / Voice
- DSL / ETTH / WLAN
    - Point-to-Point Model
    - PPP Terminated Aggregation (PTA) Model
    - L2TP Access Aggregation (LAA) Model
=20
In the U.S. alone, these aggregation router deployments span more than
50 million household subscribers - translating to at least 50 million
potential IPv6 hosts in the future.
=20
First paragraph of section 3.1 of our I-D clearly explains why a routed
aggregator doesn't echo packets received on any upstream down the
downstream that corresponds to the upstream. The paragraph also explains
how hosts in such an aggregation router deployment do not directly
communicate to each other - hosts have to send traffic through the
aggregation router. This deployment connectivity topology is known as
off-link operation.  Thus, an aggregation router deployment MUST specify
that hosts even in the same prefix are off-link in the RA from the
aggregation router.=20
=20
In some cases, on-link behavior can be clearly determined as specified
in 2461bis.  Off-link is defined as the opposite of on-link.  In order
to be sure that a host is operating in off-link mode,
ALL cases in which a host should be on-link need to be clearly specified
- thus, defining on-link and off-link mode clearly.
=20
Given the fact that an aggregation router deployment needs to ALWAYS
specify off-link mode to hosts behind modems, the RA with "no PIO" case
is potentially relevant to a large number of subscribers in an IPv6
aggregation router deployment.=20
=20
-Hemant & Wes.

________________________________

From: Hemant Singh (shemant)=20
Sent: Monday, July 23, 2007 5:31 PM
To: ipv6@ietf.org
Cc: varada@txc.com; Hemant Singh (shemant); Wes Beebee (wbeebee)
Subject: New version of draft-wbeebee-nd-implementation-pitfalls is
available


Folks,
=20
Please see a new version of our I-D at the URL below.=20
=20
http://www.ietf.org/internet-drafts/draft-wbeebee-nd-implementation-pitf
alls-02.txt
=20
See change log to understand what has changed from the -01 version.
Gross changes worth highlighting are:
=20
1. A new section 7 has been added to the I-D that lists IPv6 ND
implementation problems ala RFC 2525.
2. Section 5 is complete that lists proposed changes to 24621bis.
3. Section 6 has been edited and augmented for proposed changes to
2462bis.
=20
Best Regards.
=20
Hemant

------_=_NextPart_001_01C7DB82.BBCAEF55
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3132" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft>
<DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D380134520-09082007><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN class=3D051115418-10082007>IETF =
IPv6=20
Community</SPAN>,</FONT></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D380134520-09082007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D380134520-09082007><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2>Please review the -02 version of our I-D. =
In=20
particular, we'd like&nbsp;<SPAN class=3D051115418-10082007>reviewers =
</SPAN>to=20
focus on our proposed changes to =
2461bis.</FONT></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D380134520-09082007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D380134520-09082007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><SPAN class=3D051115418-10082007>We would like =
to specify=20
on-link vs. off-link determination more clearly for ALL IPv6=20
hosts.&nbsp;&nbsp;On-link vs. off-link&nbsp;determines data forwarding =
and=20
address resolution behavior for a host.</SPAN></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D380134520-09082007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2><SPAN=20
class=3D051115418-10082007></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D380134520-09082007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>We present a very important problem that =
relates to an=20
aggregator router network&nbsp;<SPAN class=3D051115418-10082007>used in=20
deployments listed below</SPAN>&nbsp;<SPAN =
class=3D051115418-10082007>(thanks to=20
Adeel Ahmed for providing the list):</SPAN></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D380134520-09082007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D380134520-09082007><FONT =
color=3D#0000ff>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D490502016-08062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>- Wholesale Dial / Voice</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D490502016-08062007><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>- DSL / ETTH / WLAN</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D490502016-08062007><FONT =
face=3DArial><FONT=20
size=3D2>&nbsp;&nbsp;&nbsp; <FONT color=3D#0000ff>- Point-to-Point=20
Model</FONT></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D490502016-08062007><FONT =
face=3DArial><FONT=20
size=3D2>&nbsp;&nbsp;&nbsp; <FONT color=3D#0000ff>- PPP Terminated =
Aggregation (PTA)=20
Model</FONT></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D490502016-08062007><FONT =
face=3DArial><FONT=20
size=3D2>&nbsp;&nbsp;&nbsp; <FONT color=3D#0000ff>- L2TP Access =
Aggregation (LAA)=20
Model</FONT></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D490502016-08062007><FONT =
face=3DArial=20
color=3D#000000 size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D490502016-08062007><FONT =
face=3DArial=20
size=3D2><SPAN class=3D051115418-10082007>In the U.S.<SPAN =
class=3D200051119-10082007>=20
alone</SPAN>, these&nbsp;<SPAN class=3D200051119-10082007>aggregation=20
router</SPAN>&nbsp;deployments span more than 50 million household =
subscribers -=20
translating to at least 50 million&nbsp;potential IPv6 hosts in the=20
future.</SPAN></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D490502016-08062007><FONT =
face=3DArial=20
color=3D#000000 size=3D2></FONT></SPAN>&nbsp;</DIV></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D380134520-09082007>
<DIV><FONT face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D708361622-27072007>First paragraph of section 3.1 of our I-D =
clearly=20
explains why a routed<SPAN class=3D380134520-09082007>=20
aggregator</SPAN>&nbsp;doesn't echo packets received on any upstream =
down the=20
downstream that&nbsp;<SPAN class=3D051115418-10082007>corresponds=20
to</SPAN>&nbsp;the upstream. The paragraph also explains how hosts in =
such=20
a<SPAN class=3D380134520-09082007>n aggregation =
router</SPAN>&nbsp;deployment do=20
not directly&nbsp;communicate to each other - hosts have to send traffic =

thr<SPAN class=3D051115418-10082007>ough</SPAN> the&nbsp;<SPAN=20
class=3D380134520-09082007>aggregation router</SPAN>.<SPAN=20
class=3D051115418-10082007> Th</SPAN>is<SPAN=20
class=3D051115418-10082007>&nbsp;deployment&nbsp;connectivity =
topology&nbsp;is=20
known as</SPAN>&nbsp;off-link operation<SPAN=20
class=3D051115418-10082007>.</SPAN>&nbsp; </SPAN><SPAN=20
class=3D708361622-27072007>T<SPAN =
class=3D051115418-10082007>hus,</SPAN>&nbsp;a<SPAN=20
class=3D380134520-09082007>n aggregation router</SPAN>&nbsp;deployment =
MUST=20
specify&nbsp;<SPAN class=3D051115418-10082007>that hosts even in the =
same prefix=20
are </SPAN>off-link in&nbsp;<SPAN class=3D051115418-10082007>the</SPAN> =
RA=20
from&nbsp;<SPAN class=3D380134520-09082007>the aggregation =
router</SPAN>.=20
</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT color=3D#0000ff><FONT face=3DArial><FONT size=3D2><SPAN=20
class=3D708361622-27072007></SPAN><SPAN=20
class=3D708361622-27072007></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D708361622-27072007><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D380134520-09082007><SPAN class=3D051115418-10082007>In some =
cases, on-link=20
behavior can be clearly determined as specified in 2461bis.&nbsp; =
Off-link is=20
defined as the opposite of on-link.&nbsp; In order to be sure that a =
host is=20
operating in off-link mode,</SPAN></SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=3D708361622-27072007><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D380134520-09082007><SPAN class=3D051115418-10082007>ALL cases in =
which a=20
host should be on-link need to be clearly specified - thus, defining =
on-link and=20
off-link mode clearly.</SPAN></SPAN></FONT></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D708361622-27072007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D708361622-27072007>Given=20
the fact that a<SPAN class=3D380134520-09082007>n aggregation=20
router</SPAN>&nbsp;deployment needs to ALWAYS specify off-link mode to =
hosts=20
behind<SPAN class=3D380134520-09082007> modems</SPAN>, the RA with "no=20
PIO"&nbsp;<SPAN class=3D051115418-10082007>case</SPAN><SPAN=20
class=3D380134520-09082007>&nbsp;<SPAN class=3D051115418-10082007>is =
potentially=20
relevant to a large number of subscribers in an IPv6=20
aggregation</SPAN></SPAN>&nbsp;<SPAN =
class=3D051115418-10082007>router</SPAN>=20
deployment. </SPAN></FONT></DIV></SPAN></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D380134520-09082007><FONT face=3DArial><FONT =
color=3D#0000ff><FONT=20
size=3D2><SPAN class=3D200051119-10082007>-</SPAN>Hemant &amp;=20
Wes.</FONT></FONT></FONT></SPAN></DIV></DIV></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Hemant Singh (shemant) =
<BR><B>Sent:</B>=20
Monday, July 23, 2007 5:31 PM<BR><B>To:</B> ipv6@ietf.org<BR><B>Cc:</B>=20
varada@txc.com; Hemant Singh (shemant); Wes Beebee =
(wbeebee)<BR><B>Subject:</B>=20
New version of draft-wbeebee-nd-implementation-pitfalls is=20
available<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D374242621-23072007>Folks,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D374242621-23072007></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D374242621-23072007>Please =
see a new=20
version of our I-D at the URL below. </SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-wbeebee-nd-implementati=
on-pitfalls-02.txt">http://www.ietf.org/internet-drafts/draft-wbeebee-nd-=
implementation-pitfalls-02.txt</A></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D374242621-23072007><FONT face=3DArial size=3D2>See =
change log to=20
understand what has changed from the -01 version. Gross changes worth=20
highlighting are:</FONT></SPAN></DIV>
<DIV><SPAN class=3D374242621-23072007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D374242621-23072007><FONT face=3DArial size=3D2>1. A =
new section 7=20
has been added to the I-D that lists IPv6 ND implementation problems ala =
RFC=20
2525.</FONT></SPAN></DIV>
<DIV><SPAN class=3D374242621-23072007><FONT face=3DArial size=3D2>2. =
Section 5 is=20
complete that lists proposed changes to 24621bis.</FONT></SPAN></DIV>
<DIV><SPAN class=3D374242621-23072007><FONT face=3DArial size=3D2>3. =
Section 6 has=20
been edited and augmented for proposed changes to =
2462bis.</FONT></SPAN></DIV>
<DIV><SPAN class=3D374242621-23072007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D374242621-23072007><FONT face=3DArial size=3D2>Best=20
Regards.</FONT></SPAN></DIV>
<DIV><SPAN class=3D374242621-23072007><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D374242621-23072007><FONT face=3DArial=20
size=3D2>Hemant</FONT></SPAN></DIV></BODY></HTML>

------_=_NextPart_001_01C7DB82.BBCAEF55--


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

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

--===============0862643619==--




From ipv6-bounces@ietf.org Fri Aug 10 17:58:27 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJcSo-0006HF-7I; Fri, 10 Aug 2007 17:56:10 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJcSm-0006H6-Vg
	for ipv6@ietf.org; Fri, 10 Aug 2007 17:56:09 -0400
Received: from relay1.mentorg.com ([192.94.38.131])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IJcSm-0007Fp-EF
	for ipv6@ietf.org; Fri, 10 Aug 2007 17:56:08 -0400
Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58])
	by relay1.mentorg.com with esmtp 
	id 1IJcSl-0006TE-0S from tammy_leino@mentor.com 
	for ipv6@ietf.org; Fri, 10 Aug 2007 14:56:07 -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:56:06 -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:56:05 -0500
Message-ID: <7ECEF9368E169544B43882BC98EB5D92032DA834@SVR-ALH-EXC-02.mgc.mentorg.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: prefix length determination for DHCPv6
Thread-Index: AcfbmUPYFKIMJ9+7QwmXa6riJIOi/g==
From: "Leino, Tammy" <tammy_leino@mentor.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 10 Aug 2007 21:56:06.0268 (UTC)
	FILETIME=[408B03C0:01C7DB99]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Subject: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1481099544=="
Errors-To: ipv6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============1481099544==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7DB99.3FEC1CC3"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7DB99.3FEC1CC3
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.3FEC1CC3
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.3FEC1CC3--


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

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

--===============1481099544==--




From ipv6-bounces@ietf.org Fri Aug 10 18:16:09 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJckO-0007IS-5s; Fri, 10 Aug 2007 18:14:20 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJckM-0007IN-Nd
	for ipv6@ietf.org; Fri, 10 Aug 2007 18:14:18 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IJckM-0007bA-6X
	for ipv6@ietf.org; Fri, 10 Aug 2007 18:14:18 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195])
	by sj-iport-6.cisco.com with ESMTP; 10 Aug 2007 15:14:17 -0700
X-IronPort-AV: i="4.19,246,1183359600"; 
	d="scan'208,217"; a="198143160:sNHT77635971"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l7AMEHms021254; 
	Fri, 10 Aug 2007 15:14:17 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id l7AMEHa1010441;
	Fri, 10 Aug 2007 22:14:17 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, 10 Aug 2007 18:14:13 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 10 Aug 2007 18:14:12 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D038806C6@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <7ECEF9368E169544B43882BC98EB5D92032DA834@SVR-ALH-EXC-02.mgc.mentorg.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: prefix length determination for DHCPv6
Thread-Index: AcfbmUPYFKIMJ9+7QwmXa6riJIOi/gAAFaiQ
References: <7ECEF9368E169544B43882BC98EB5D92032DA834@SVR-ALH-EXC-02.mgc.mentorg.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Leino, Tammy" <tammy_leino@mentor.com>, <ipv6@ietf.org>
X-OriginalArrivalTime: 10 Aug 2007 22:14:13.0840 (UTC)
	FILETIME=[C8C95500:01C7DB9B]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4199; t=1186784057;
	x=1187648057; c=relaxed/simple; s=sjdkim3002;
	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=20prefix=20length=20determination=20for=20DHCPv6
	|Sender:=20; bh=Bqg9qCf1NZOsaL3lxmCBGydwmJssAslHSltTJZ/wG3c=;
	b=AHkAx2CcOlUXZY3Rvbq10ADbWTi8hOznehYWoDBKYHMTWDZdQe1bh1dRvxAcNqvKO8nnFXbn
	bd6n4tmxHxSmg6ZKEnaih9XHQ3OdpxqyF7/Kj//1m0KCcSr8VaO/8GRs;
Authentication-Results: sj-dkim-3; header.From=shemant@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim3002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Cc: 
Subject: RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0358579336=="
Errors-To: ipv6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============0358579336==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7DB9B.C886D27B"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7DB9B.C886D27B
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

=20
________________________________

From: Leino, Tammy [mailto:tammy_leino@mentor.com]=20
Sent: Friday, August 10, 2007 5:56 PM
To: ipv6@ietf.org
Subject: prefix length determination for DHCPv6



Hello,=20

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

<hs> One way to to send a Prefix Information Option (PIO) for the
assigned address prefix in RA to the client.  PIO includes prefix
length.

</hs>

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

<hs> I don't believe so. I'll let the DHCPv6 RFC authors like Ralph
Droms and Bernie Volz verify this one.=20

</hs>

Hemant

  If so, what RFC specifies this option?

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

Best Regards,=20
Tammy Leino=20


------_=_NextPart_001_01C7DB9B.C886D27B
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>prefix length determination for DHCPv6</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3132" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
size=3D2></FONT>&nbsp;</DIV>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Leino, Tammy=20
[mailto:tammy_leino@mentor.com] <BR><B>Sent:</B> Friday, August 10, 2007 =
5:56=20
PM<BR><B>To:</B> ipv6@ietf.org<BR><B>Subject:</B> prefix length =
determination=20
for DHCPv6<BR></FONT><BR></DIV>
<DIV></DIV><!-- Converted from text/rtf format -->
<P><FONT face=3DArial size=3D2>Hello,</FONT> </P>
<P><FONT face=3DArial><FONT size=3D2>In implementing RFC 3315, I see no =
option or=20
field in the IA_NA option for a prefix length associated with an =
assigned IPv6=20
address.&nbsp; How does the client determine the prefix length of the =
IPv6=20
address the server is assigning?<SPAN class=3D238375821-10082007><FONT=20
color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></FONT></P>
<P><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D238375821-10082007><FONT=20
color=3D#0000ff>&lt;hs&gt; One way to to send a Prefix Information =
Option (PIO)=20
for the assigned address prefix&nbsp;in RA to the client. =
</FONT>&nbsp;<FONT=20
color=3D#0000ff>PIO includes prefix =
length.</FONT></SPAN></FONT></FONT></P>
<P><FONT face=3DArial><FONT color=3D#0000ff size=3D2><SPAN=20
class=3D238375821-10082007>&lt;/hs&gt;</SPAN></FONT></FONT></P>
<P><FONT face=3DArial size=3D2>Furthermore, in the absence of a =
configured IPv6=20
router on the link, can the client use the DHCPv6 server to find a =
default=20
gateway out of the local network?&nbsp;<SPAN =
class=3D238375821-10082007><FONT=20
color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D238375821-10082007>&lt;hs&gt; I don't believe so. I'll let the =
DHCPv6 RFC=20
authors like Ralph Droms and Bernie Volz verify this one. =
</SPAN></FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D238375821-10082007>&lt;/hs&gt;</SPAN></FONT></P>
<P><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D238375821-10082007>Hemant</SPAN></FONT></P>
<P><FONT face=3DArial size=3D2><SPAN =
class=3D238375821-10082007>&nbsp;</SPAN> If so,=20
what RFC specifies this option?</FONT></P>
<P><FONT face=3DArial size=3D2>Any help or referrals to additional RFCs =
would be=20
much appreciated.</FONT> </P>
<P><FONT face=3DArial size=3D2>Best Regards,</FONT> <BR><FONT =
face=3DArial=20
size=3D2>Tammy Leino</FONT> </P></BODY></HTML>

------_=_NextPart_001_01C7DB9B.C886D27B--


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

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

--===============0358579336==--




From ipv6-bounces@ietf.org Fri Aug 10 18:22:32 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJcqV-0002I1-TE; Fri, 10 Aug 2007 18:20:39 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJcqV-0002H6-2O
	for ipv6@ietf.org; Fri, 10 Aug 2007 18:20:39 -0400
Received: from relay02.pair.com ([209.68.5.16])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IJcqU-0007iG-NG
	for ipv6@ietf.org; Fri, 10 Aug 2007 18:20:39 -0400
Received: (qmail 303 invoked by uid 0); 10 Aug 2007 22:20:37 -0000
Received: from 68.246.127.117 (HELO Inbox) (68.246.127.117)
	by relay02.pair.com with SMTP; 10 Aug 2007 22:20:37 -0000
X-pair-Authenticated: 68.246.127.117
MIME-Version: 1.0
From: "John Jason Brzozowski (JJMB)" <jjmb@jjmb.com>
Date: Fri, 10 Aug 2007 18:19:51 -0400
Importance: normal
X-Priority: 3
To: "Hemant Singh (shemant)" <shemant@cisco.com>, 
	"Leino, Tammy" <tammy_leino@mentor.com>, <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15
Cc: 
Subject: RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org
Message-Id: <E1IJcqV-0002I1-TE@megatron.ietf.org>

Hello Hemant,

There is no DHCPv6 mechabism to explicitly transmit router/gateway informat=
ion.

Regards,

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

-----Original Message-----
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Leino, Tammy" <tammy_leino@mentor.com>; ipv6@ietf.org
Sent: 08/10/07 18:14
Subject: RE: prefix length determination for DHCPv6

=20
________________________________

From: Leino, Tammy [mailto:tammy_leino@mentor.com]=20
Sent: Friday, August 10, 2007 5:56 PM
To: ipv6@ietf.org
Subject: prefix length determination for DHCPv6



Hello,=20

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

<hs> One way to to send a Prefix Information Option (PIO) for the
assigned address prefix in RA to the client.  PIO includes prefix
length.

</hs>

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

<hs> I don't believe so. I'll let the DHCPv6 RFC authors like Ralph
Droms and Bernie Volz verify this one.=20

</hs>

Hemant

  If so, what RFC specifies this option?

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

Best Regards,=20
Tammy Leino=20



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



From ipv6-bounces@ietf.org Fri Aug 10 18:30:11 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJcxy-00048v-HC; Fri, 10 Aug 2007 18:28:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJcxx-000458-9I
	for ipv6@ietf.org; Fri, 10 Aug 2007 18:28:21 -0400
Received: from relay1.mentorg.com ([192.94.38.131])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IJcxw-0000ow-2G
	for ipv6@ietf.org; Fri, 10 Aug 2007 18:28:21 -0400
Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58])
	by relay1.mentorg.com with esmtp 
	id 1IJcxv-0000dq-HS from tammy_leino@mentor.com ;
	Fri, 10 Aug 2007 15:28:19 -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:28:18 -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
Date: Fri, 10 Aug 2007 17:28:17 -0500
Message-ID: <7ECEF9368E169544B43882BC98EB5D92032DA837@SVR-ALH-EXC-02.mgc.mentorg.com>
In-Reply-To: <SVR-ORW-EXC-102hqgR00074148@SVR-ORW-EXC-10.mgc.mentorg.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: prefix length determination for DHCPv6
Thread-Index: AcfbnLD1bD7d+ihCRS6ylCpCq5HsOgAANe1w
From: "Leino, Tammy" <tammy_leino@mentor.com>
To: "John Jason Brzozowski (JJMB)" <jjmb@jjmb.com>,
	"Hemant Singh (shemant)" <shemant@cisco.com>, <ipv6@ietf.org>
X-OriginalArrivalTime: 10 Aug 2007 22:28:18.0809 (UTC)
	FILETIME=[C06D5E90:01C7DB9D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: 
Subject: RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Thank you John.

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

Best Regards,
Tammy



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


Hello Hemant,

There is no DHCPv6 mechabism to explicitly transmit router/gateway =
information.

Regards,

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

-----Original Message-----
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Leino, Tammy" <tammy_leino@mentor.com>; ipv6@ietf.org
Sent: 08/10/07 18:14
Subject: RE: prefix length determination for DHCPv6

=20
________________________________

From: Leino, Tammy [mailto:tammy_leino@mentor.com]=20
Sent: Friday, August 10, 2007 5:56 PM
To: ipv6@ietf.org
Subject: prefix length determination for DHCPv6



Hello,=20

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

<hs> One way to to send a Prefix Information Option (PIO) for the
assigned address prefix in RA to the client.  PIO includes prefix
length.

</hs>

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

<hs> I don't believe so. I'll let the DHCPv6 RFC authors like Ralph
Droms and Bernie Volz verify this one.=20

</hs>

Hemant

  If so, what RFC specifies this option?

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

Best Regards,=20
Tammy Leino=20



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



From ipv6-bounces@ietf.org Fri Aug 10 18:32:03 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJczp-0004i3-6q; Fri, 10 Aug 2007 18:30:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJczn-0004hx-H2
	for ipv6@ietf.org; Fri, 10 Aug 2007 18:30:15 -0400
Received: from relay1.mentorg.com ([192.94.38.131])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IJczm-0000r7-5w
	for ipv6@ietf.org; Fri, 10 Aug 2007 18:30:15 -0400
Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58])
	by relay1.mentorg.com with esmtp 
	id 1IJczl-0000kI-Pc from tammy_leino@mentor.com ;
	Fri, 10 Aug 2007 15:30:13 -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:30:12 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 10 Aug 2007 17:30:11 -0500
Message-ID: <7ECEF9368E169544B43882BC98EB5D92032DA838@SVR-ALH-EXC-02.mgc.mentorg.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D038806C6@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: prefix length determination for DHCPv6
Thread-Index: AcfbmUPYFKIMJ9+7QwmXa6riJIOi/gAAFaiQAAEZ7TA=
From: "Leino, Tammy" <tammy_leino@mentor.com>
To: "Hemant Singh (shemant)" <shemant@cisco.com>,
	<ipv6@ietf.org>
X-OriginalArrivalTime: 10 Aug 2007 22:30:12.0978 (UTC)
	FILETIME=[047A2D20:01C7DB9E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Cc: 
Subject: RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2008083213=="
Errors-To: ipv6-bounces@ietf.org

This is a multi-part message in MIME format.

--===============2008083213==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7DB9E.03B476B1"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7DB9E.03B476B1
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thank you Hemant.  I appreciate your comments.
=20

-----Original Message-----
From: Hemant Singh (shemant) [mailto:shemant@cisco.com]
Sent: Friday, August 10, 2007 6:14 PM
To: Leino, Tammy; ipv6@ietf.org
Subject: RE: prefix length determination for DHCPv6


=20
  _____ =20

From: Leino, Tammy [mailto:tammy_leino@mentor.com]=20
Sent: Friday, August 10, 2007 5:56 PM
To: ipv6@ietf.org
Subject: prefix length determination for DHCPv6



Hello,=20

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

<hs> One way to to send a Prefix Information Option (PIO) for the
assigned address prefix in RA to the client.  PIO includes prefix
length.

</hs>

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

<hs> I don't believe so. I'll let the DHCPv6 RFC authors like Ralph
Droms and Bernie Volz verify this one.=20

</hs>

Hemant

  If so, what RFC specifies this option?

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

Best Regards,=20
Tammy Leino=20


------_=_NextPart_001_01C7DB9E.03B476B1
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>prefix length determination for DHCPv6</TITLE>

<META content=3D"MSHTML 6.00.6000.16481" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D130093022-10082007><FONT face=3DArial size=3D2>Thank =
you=20
Hemant.&nbsp; I appreciate your comments.</FONT></SPAN></DIV>
<DIV><SPAN class=3D130093022-10082007></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> Hemant Singh =
(shemant)=20
  [mailto:shemant@cisco.com]<BR><B>Sent:</B> Friday, August 10, 2007 =
6:14=20
  PM<BR><B>To:</B> Leino, Tammy; ipv6@ietf.org<BR><B>Subject:</B> RE: =
prefix=20
  length determination for DHCPv6<BR><BR></FONT></DIV>
  <DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff=20
  size=3D2></FONT>&nbsp;</DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Leino, Tammy=20
  [mailto:tammy_leino@mentor.com] <BR><B>Sent:</B> Friday, August 10, =
2007 5:56=20
  PM<BR><B>To:</B> ipv6@ietf.org<BR><B>Subject:</B> prefix length =
determination=20
  for DHCPv6<BR></FONT><BR></DIV>
  <DIV></DIV><!-- Converted from text/rtf format -->
  <P><FONT face=3DArial size=3D2>Hello,</FONT> </P>
  <P><FONT face=3DArial><FONT size=3D2>In implementing RFC 3315, I see =
no option or=20
  field in the IA_NA option for a prefix length associated with an =
assigned IPv6=20
  address.&nbsp; How does the client determine the prefix length of the =
IPv6=20
  address the server is assigning?<SPAN class=3D238375821-10082007><FONT =

  color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></FONT></P>
  <P><FONT face=3DArial><FONT size=3D2><SPAN =
class=3D238375821-10082007><FONT=20
  color=3D#0000ff>&lt;hs&gt; One way to to send a Prefix Information =
Option (PIO)=20
  for the assigned address prefix&nbsp;in RA to the client. =
</FONT>&nbsp;<FONT=20
  color=3D#0000ff>PIO includes prefix =
length.</FONT></SPAN></FONT></FONT></P>
  <P><FONT face=3DArial><FONT color=3D#0000ff size=3D2><SPAN=20
  class=3D238375821-10082007>&lt;/hs&gt;</SPAN></FONT></FONT></P>
  <P><FONT face=3DArial size=3D2>Furthermore, in the absence of a =
configured IPv6=20
  router on the link, can the client use the DHCPv6 server to find a =
default=20
  gateway out of the local network?&nbsp;<SPAN =
class=3D238375821-10082007><FONT=20
  color=3D#0000ff>&nbsp;</FONT></SPAN></FONT></P>
  <P><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D238375821-10082007>&lt;hs&gt; I don't believe so. I'll let the =
DHCPv6=20
  RFC authors like Ralph Droms and Bernie Volz verify this one.=20
  </SPAN></FONT></P>
  <P><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D238375821-10082007>&lt;/hs&gt;</SPAN></FONT></P>
  <P><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
  class=3D238375821-10082007>Hemant</SPAN></FONT></P>
  <P><FONT face=3DArial size=3D2><SPAN =
class=3D238375821-10082007>&nbsp;</SPAN> If so,=20
  what RFC specifies this option?</FONT></P>
  <P><FONT face=3DArial size=3D2>Any help or referrals to additional =
RFCs would be=20
  much appreciated.</FONT> </P>
  <P><FONT face=3DArial size=3D2>Best Regards,</FONT> <BR><FONT =
face=3DArial=20
  size=3D2>Tammy Leino</FONT> </P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C7DB9E.03B476B1--


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

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

--===============2008083213==--




From ipv6-bounces@ietf.org Fri Aug 10 18:55:12 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJdM7-0001Sa-Rr; Fri, 10 Aug 2007 18:53:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJdM6-0001SS-88
	for ipv6@ietf.org; Fri, 10 Aug 2007 18:53:18 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IJdM2-0001ET-Nm
	for ipv6@ietf.org; Fri, 10 Aug 2007 18:53:18 -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 l7AMnhvJ043184
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Sat, 11 Aug 2007 00:49:44 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <7ECEF9368E169544B43882BC98EB5D92032DA837@SVR-ALH-EXC-02.mgc.mentorg.com>
References: <7ECEF9368E169544B43882BC98EB5D92032DA837@SVR-ALH-EXC-02.mgc.mentorg.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <1D772874-1565-4E4A-B019-898CB7E9AAEB@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Sat, 11 Aug 2007 00:51:49 +0200
To: "Leino, Tammy" <tammy_leino@mentor.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: ipv6@ietf.org, "John Jason Brzozowski \(JJMB\)" <jjmb@jjmb.com>
Subject: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

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

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

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

So I don't think we should present NOT having RAs as a valid  
configuration option. This way, we get to avoid the situations above.  
If people want to configure hosts using DHCPv6 they should have  
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  
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  
IPv6 implementations can configure an address through DHCPv6.)

Strange that a subnet size isn't included with the DHCPv6 address  
assignment. I guess this means either configuring a /128 and rely on  
router redirects to learn about directly attached neighbors, or use  
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  
requirement and why.

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



From ipv6-bounces@ietf.org Fri Aug 10 19:11:37 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJdbu-0007ps-QQ; Fri, 10 Aug 2007 19:09:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJdbt-0007pm-7Q
	for ipv6@ietf.org; Fri, 10 Aug 2007 19:09:37 -0400
Received: from relay1.mentorg.com ([192.94.38.131])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IJdbr-0001Uq-Qr
	for ipv6@ietf.org; Fri, 10 Aug 2007 19:09:37 -0400
Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58])
	by relay1.mentorg.com with esmtp 
	id 1IJdbq-00030p-8D from tammy_leino@mentor.com ;
	Fri, 10 Aug 2007 16:09:34 -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:09:33 -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:09:32 -0500
Message-ID: <7ECEF9368E169544B43882BC98EB5D92032DA83B@SVR-ALH-EXC-02.mgc.mentorg.com>
In-Reply-To: <1D772874-1565-4E4A-B019-898CB7E9AAEB@muada.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: prefix length determination for DHCPv6
Thread-Index: AcfboUHk1kkPl/zjSFmlUg6ok1IdnwAAPQ+w
From: "Leino, Tammy" <tammy_leino@mentor.com>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>
X-OriginalArrivalTime: 10 Aug 2007 23:09:33.0987 (UTC)
	FILETIME=[83BF8F30:01C7DBA3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: ipv6@ietf.org, "John Jason Brzozowski \(JJMB\)" <jjmb@jjmb.com>
Subject: RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

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



From ipv6-bounces@ietf.org Fri Aug 10 19:21:45 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJdls-00008Z-T9; Fri, 10 Aug 2007 19:19:56 -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: RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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
--------------------------------------------------------------------

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



From ipv6-bounces@ietf.org Fri Aug 10 19:30:18 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJduC-0007cM-Se; Fri, 10 Aug 2007 19:28:32 -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: RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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
--------------------------------------------------------------------

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



From ipv6-bounces@ietf.org Fri Aug 10 19:41:09 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJe4f-0001Ol-Lt; Fri, 10 Aug 2007 19:39:21 -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: RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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
--------------------------------------------------------------------

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



From ipv6-bounces@ietf.org Fri Aug 10 19:57:13 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJeKB-0007Qz-QY; Fri, 10 Aug 2007 19:55:23 -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: RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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
--------------------------------------------------------------------

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



From ipv6-bounces@ietf.org Sat Aug 11 04:53:49 2007
Return-path: <ipv6-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-0001B9-TU; 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>
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>
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Sat Aug 11 06:30:01 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJoCE-0001BM-LX; Sat, 11 Aug 2007 06:27:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJoCD-00018q-W0
	for ipv6@ietf.org; Sat, 11 Aug 2007 06:27:49 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IJoCD-00037O-E1
	for ipv6@ietf.org; Sat, 11 Aug 2007 06:27:49 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 11 Aug 2007 06:27:45 -0400
X-IronPort-AV: i="4.19,248,1183348800"; 
	d="scan'208"; a="67728990:sNHT50442568"
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 l7BARjWV021965; 
	Sat, 11 Aug 2007 06:27:45 -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 l7BARimd006587; 
	Sat, 11 Aug 2007 10:27:44 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); 
	Sat, 11 Aug 2007 06:27:44 -0400
Received: from [192.168.1.106] ([10.86.243.55]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Sat, 11 Aug 2007 06:27:43 -0400
In-Reply-To: <7ECEF9368E169544B43882BC98EB5D92032DA837@SVR-ALH-EXC-02.mgc.mentorg.com>
References: <7ECEF9368E169544B43882BC98EB5D92032DA837@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: <B91623BB-A31C-4C1A-B325-B5EBB071A268@cisco.com>
Content-Transfer-Encoding: 7bit
From: Ralph Droms <rdroms@cisco.com>
Date: Sat, 11 Aug 2007 06:28:32 -0400
To: "Leino, Tammy" <tammy_leino@mentor.com>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 11 Aug 2007 10:27:43.0704 (UTC)
	FILETIME=[40B5A580:01C7DC02]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2580; t=1186828065;
	x=1187692065; 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=20prefix=20length=20determination=20for=20DHCPv6
	|Sender:=20
	|To:=20=22Leino,=20Tammy=22=20<tammy_leino@mentor.com>;
	bh=TYkoR+A33r1rr/lHDBra63a0O6UZDRL6hXeTRhzmAiE=;
	b=u0sp50X+Z62FUjmXHXt7rTabtnvXi4blkLEzFlTiWpkIULCci51q7SnshfDDqCDZ/hnCr/cG
	3/yBcrkCt7yCik/k1ppeAzziGRKvtgC17GU+Tzf064qDUGwNw5P304+2;
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: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: ipv6@ietf.org, "John Jason Brzozowski \(JJMB\)" <jjmb@jjmb.com>
Subject: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

This issue was discussed in the dhc and v6ops WGs at the last IETF  
meeting: http://www3.ietf.org/proceedings/07jul/slides/dhc-5.pdf

- Ralph

On Aug 10, 2007, at Aug 10, 2007,6:28 PM, Leino, Tammy wrote:

> Thank you John.
>
> Has your working group considered adding this as a DHCPv6 option?   
> If the on-link router is not configured to transmit RAs, a DHCPv6  
> option advertising the default gateway would be helpful in  
> populating the routing table.
>
> Best Regards,
> Tammy
>
>
>
> -----Original Message-----
> From: John Jason Brzozowski (JJMB) [mailto:jjmb@jjmb.com]
> Sent: Friday, August 10, 2007 6:20 PM
> To: Hemant Singh (shemant); Leino, Tammy; ipv6@ietf.org
> Subject: RE: prefix length determination for DHCPv6
>
>
> Hello Hemant,
>
> There is no DHCPv6 mechabism to explicitly transmit router/gateway  
> information.
>
> Regards,
>
> John
> ######################
> John Jason Brzozowski, CISSP, RHCT
> jjmb@jjmb.com
> 484-994-6787
> ######################
>
> -----Original Message-----
> From: "Hemant Singh (shemant)" <shemant@cisco.com>
> To: "Leino, Tammy" <tammy_leino@mentor.com>; ipv6@ietf.org
> Sent: 08/10/07 18:14
> Subject: RE: prefix length determination for DHCPv6
>
>
> ________________________________
>
> From: Leino, Tammy [mailto:tammy_leino@mentor.com]
> Sent: Friday, August 10, 2007 5:56 PM
> To: ipv6@ietf.org
> Subject: 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?
>
> <hs> One way to to send a Prefix Information Option (PIO) for the
> assigned address prefix in RA to the client.  PIO includes prefix
> length.
>
> </hs>
>
> 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?
>
> <hs> I don't believe so. I'll let the DHCPv6 RFC authors like Ralph
> Droms and Bernie Volz verify this one.
>
> </hs>
>
> Hemant
>
>   If so, what RFC specifies this option?
>
> Any help or referrals to additional RFCs would be much appreciated.
>
> Best Regards,
> Tammy Leino
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

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



From ipv6-bounces@ietf.org Sat Aug 11 08:29:28 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJq3t-0004kK-37; Sat, 11 Aug 2007 08:27:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IJq3s-0004i0-9a
	for ipv6@ietf.org; Sat, 11 Aug 2007 08:27:20 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IJq3q-0005Cu-DL
	for ipv6@ietf.org; Sat, 11 Aug 2007 08:27:20 -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>
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>
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.


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



From ipv6-bounces@ietf.org Sat Aug 11 09:45:52 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IJrFp-0004qj-DJ; Sat, 11 Aug 2007 09:43:45 -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
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
Cc: ipv6@ietf.org, volz@cisco.com, iljitsch@muada.com, jjmb@jjmb.com,
	dhcwg@ietf.org
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Sat Aug 11 20:02:34 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IK0sI-0001M3-C7; Sat, 11 Aug 2007 20:00:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IK0sH-0001Lx-I1
	for ipv6@ietf.org; Sat, 11 Aug 2007 20:00:05 -0400
Received: from [2002:425c:4242:0:210:5aff:fe86:1f54] (helo=cyteen.hactrn.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IK0sH-0002fL-5z
	for ipv6@ietf.org; Sat, 11 Aug 2007 20:00:05 -0400
Received: from cyteen.hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id 9947F28463
	for <ipv6@ietf.org>; Sun, 12 Aug 2007 00:00:04 +0000 (UTC)
To: ipv6@ietf.org
From: Rob Austein <sra+ipng@hactrn.net>
Date: Sun, 12 Aug 2007 00:00:04 +0000
Message-Id: <20070812000004.9947F28463@cyteen.hactrn.net>
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Subject: Weekly posting summary for ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 27.27% |    6 | 26.13% |    53657 | tammy_leino@mentor.com
 13.64% |    3 | 17.58% |    36102 | shemant@cisco.com
  4.55% |    1 | 20.13% |    41334 | syedatherzaidi@gmail.com
  9.09% |    2 | 11.60% |    23827 | volz@cisco.com
  4.55% |    1 |  3.80% |     7803 | jinmei@isl.rdc.toshiba.co.jp
  4.55% |    1 |  3.60% |     7393 | rdroms@cisco.com
  4.55% |    1 |  2.55% |     5241 | iljitsch@muada.com
  4.55% |    1 |  2.54% |     5219 | mohta@necom830.hpcl.titech.ac.jp
  4.55% |    1 |  2.29% |     4701 | brian@innovationslab.net
  4.55% |    1 |  2.27% |     4661 | jjmb@jjmb.com
  4.55% |    1 |  2.18% |     4474 | rogerj@jorgensen.no
  4.55% |    1 |  1.89% |     3876 | rdenis@simphalempin.com
  4.55% |    1 |  1.76% |     3619 | sra+ipng@hactrn.net
  4.55% |    1 |  1.69% |     3463 | itojun@itojun.org
--------+------+--------+----------+------------------------
100.00% |   22 |100.00% |   205370 | Total

Grunchweather Associates provides this automatic summary on an at-whim
basis at the request of the IPv6 WG chairs.  Your mileage may vary.
We decline responsibilities, all shapes, all sizes, all colors.
If this script produces broken output, you get to keep both pieces.

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



From ipv6-bounces@ietf.org Mon Aug 13 05:58:17 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKWeV-0005ab-3l; Mon, 13 Aug 2007 05:55:59 -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: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.

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



From ipv6-bounces@ietf.org Mon Aug 13 06:20:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKX0i-0004uG-18; Mon, 13 Aug 2007 06:18:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IKX0h-0004u2-1M
	for ipv6@ietf.org; Mon, 13 Aug 2007 06:18:55 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IKX0g-0008SX-CQ
	for ipv6@ietf.org; Mon, 13 Aug 2007 06:18:54 -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 l7DAFNPw096056
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Mon, 13 Aug 2007 12:15:24 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <7ECEF9368E169544B43882BC98EB5D92032DA83B@SVR-ALH-EXC-02.mgc.mentorg.com>
References: <7ECEF9368E169544B43882BC98EB5D92032DA83B@SVR-ALH-EXC-02.mgc.mentorg.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Mon, 13 Aug 2007 12:17:33 +0200
To: "Leino, Tammy" <tammy_leino@mentor.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: ipv6@ietf.org, "John Jason Brzozowski \(JJMB\)" <jjmb@jjmb.com>
Subject: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 11-aug-2007, at 1:09, Leino, Tammy wrote:

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

But then, why do you need addresses when you have no external  
connectivity? A lot of stuff will work just fine over link local  
addresses, although the need to include a scope identifier gets in  
the way of some applications.

>>> (There is of course the consideration that at this time, very few
> 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?

First of all, the DHCPv6 specification was finished relatively late,  
in 2003 if I'm not mistaken. Most major vendors had already  
implemented IPv6 by then and I'm guessing that deployment levels so  
far haven't exactly given them much reason to drastically update  
their IPv6 implementations.

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.

Since address configuration has always happened and continues to  
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  
school" IPv6 users are generally happy with stateless autoconfiguration.

That leaves:

> If they are not using DHCPv6,
> how do they distribute DNS servers and other configuration  
> information?

In practice? They don't. As long as you have IPv4, you can use IPv4  
for this.

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.

In the near future we'll have draft-jeong-dnsop-ipv6-dns- 
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.

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

My opinion: DHCPv6 is a complex protocol that uses a relatively high  
number of messages. In the past, UDP-based protocols have been  
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  
default but only if RA flags indicate that they should do this, and  
DNS configuration should be possible without DHCPv6.

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.

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



From ipv6-bounces@ietf.org Mon Aug 13 09:21:45 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKZpY-0002wR-T4; Mon, 13 Aug 2007 09:19:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IKZpX-0002wG-Oa
	for ipv6@ietf.org; Mon, 13 Aug 2007 09:19:35 -0400
Received: from relay1.mentorg.com ([192.94.38.131])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IKZpW-0004gm-92
	for ipv6@ietf.org; Mon, 13 Aug 2007 09:19:35 -0400
Received: from svr-orw-exc-10.mgc.mentorg.com ([147.34.98.58])
	by relay1.mentorg.com with esmtp 
	id 1IKZpU-0005o5-Ms from tammy_leino@mentor.com ;
	Mon, 13 Aug 2007 06:19:32 -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:19:32 -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:19:30 -0500
Message-ID: <7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
In-Reply-To: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: prefix length determination for DHCPv6
Thread-Index: Acfdk13CNYyAGeSOQRaMECNPTn4pCgAGLylQ
From: "Leino, Tammy" <tammy_leino@mentor.com>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>
X-OriginalArrivalTime: 13 Aug 2007 13:19:32.0006 (UTC)
	FILETIME=[95C33460:01C7DDAC]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Cc: ipv6@ietf.org, "John Jason Brzozowski \(JJMB\)" <jjmb@jjmb.com>
Subject: RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

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.

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.

Thank you again for your time and advice.

Best Regards,
Tammy


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


On 11-aug-2007, at 1:09, Leino, Tammy wrote:

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

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.

>>> (There is of course the consideration that at this time, very few
> 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?

First of all, the DHCPv6 specification was finished relatively late, =20
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 =20
far haven't exactly given them much reason to drastically update =20
their IPv6 implementations.

Then there is the confusion about stateful and stateless DHCPv6 and =20
the whole discussion about the meaning of the M and O bits in router =20
advertisements. I think this created uncertainty in the market place =20
for some time.

Since address configuration has always happened and continues to =20
happen through stateless autoconfiguration, DHCPv6 address assignment =20
wasn't implemented widely, and you can only use this mechanism when =20
you can be sure that both the server and the clients support it. It =20
looks like now that IPv6 is gaining more widespread attention that =20
more people want this because it's the same as in IPv4, but "old =20
school" IPv6 users are generally happy with stateless autoconfiguration.

That leaves:

> If they are not using DHCPv6,
> how do they distribute DNS servers and other configuration =20
> information?

In practice? They don't. As long as you have IPv4, you can use IPv4 =20
for this.

Other than that, you mostly manually configure an address. Although =20
DHCPv6 allows you to do this automatically, the trouble is that you =20
can't be sure that there will be a DHCPv6 server everywhere you go so =20
in practice, the advantage of DHCPv6 over manual configuration is =20
limited. There was talk about using well-known anycasted addresses =20
for this but that never came off the ground.

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 =20
will have the same problem as DHCPv6: you can't be sure that someone =20
is making the info available until it's extremely widely implemented.

> I am interested in learning how well received DHCPv6 has been.  We =20
> have
> been slow to implement it in our OS because of low demand.

My opinion: DHCPv6 is a complex protocol that uses a relatively high =20
number of messages. In the past, UDP-based protocols have been =20
especially susceptible to security problems in their implementations. =20
As such, I'm very happy to do without it when I don't need it and I =20
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 =20
DNS configuration should be possible without DHCPv6.

Having said that, there can be situations where it's useful to assign =20
an address to an IPv6 host, so there is certainly a place for DHCPv6. =20
And prefix delegation is brilliant, this is a great way to provision =20
IPv6 CPEs with an address block.

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



From ipv6-bounces@ietf.org Mon Aug 13 09:22:29 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKZqg-0004FN-7u; Mon, 13 Aug 2007 09:20:46 -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: RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.

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



From ipv6-bounces@ietf.org Mon Aug 13 11:48:55 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKc7s-0006sY-O2; Mon, 13 Aug 2007 11:46:40 -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: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Mon Aug 13 11:50:02 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKc9L-0000QB-Mk; Mon, 13 Aug 2007 11:48:11 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IKc9J-0000Q1-R6
	for ipv6@ietf.org; Mon, 13 Aug 2007 11:48:10 -0400
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IKc9I-0001nd-Vz
	for ipv6@ietf.org; Mon, 13 Aug 2007 11:48:09 -0400
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-4.cisco.com with ESMTP; 13 Aug 2007 08:48:06 -0700
X-IronPort-AV: i="4.19,255,1183359600"; d="scan'208"; a="8238643:sNHT31551756"
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 l7DFm6Uc026869
	for <ipv6@ietf.org>; Mon, 13 Aug 2007 08:48:06 -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 l7DFlviX011378
	for <ipv6@ietf.org>; Mon, 13 Aug 2007 15:48:06 GMT
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 13 Aug 2007 11:47: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 11:48:38 -0400
Message-ID: <CA8EB93B28BD0F4C88392699600BD655040AFDEB@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <B91623BB-A31C-4C1A-B325-B5EBB071A268@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: prefix length determination for DHCPv6
Thread-Index: AcfcAm66WN/uknvlRwWnnmBe7kLnFQBvKRTw
From: "Wes Beebee \(wbeebee\)" <wbeebee@cisco.com>
To: "Ralph Droms \(rdroms\)" <rdroms@cisco.com>
X-OriginalArrivalTime: 13 Aug 2007 15:47:59.0781 (UTC)
	FILETIME=[5335CD50:01C7DDC1]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=4743; t=1187020086;
	x=1187884086; c=relaxed/simple; s=sjdkim1004;
	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=20prefix=20length=20determination=20for=20DHCPv6
	|Sender:=20; bh=J1soEX9vt5XXrJnfGbvs5kIhHVeIgtgZCNZCJpDzKhU=;
	b=rHu7JsFZ0Jt+38jz/e7T7zd3PY10rb6DrIW0vxCMjUvD6uYURFjLVPN6gCudCFDAW2FoMHS+
	7lq+NbSrlnX7m38aaXPdbURpQbRHFDLgKGkm2xW6nf9hSqxI87r5DB/eWG1yl6DlD7EJv5mc/G
	qrA1FuOCabmwZzKrloLQROaG8=;
Authentication-Results: sj-dkim-1; header.From=wbeebee@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac
Cc: ipv6@ietf.org
Subject: RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

As Bernie said, having two ways of doing the same thing, for example
having=20
both the RA and DHCPv6 determine the default gateway or on-link
information,=20
leads to both confusion and conflicts.  Which one do you believe?  If
you're=20
talking about security, both RA's and DHCPv6 can be spoofed - so adding=20
redundant and conflicting information solves nothing.

Others can argue that either ND (RA's) or DHCPv6 can be abolished - but=20
I would argue that separating concerns, like on-link/routing information

from address acquisition actually gives you more freedom to design your=20
network the way you want to in a very clean, and easily understandable
way.  For instance, you may choose to have two completely different=20
approaches to doling out address information (in a central repository or
DHCPv6 server, where you can easily control who gets to have access to
the
network), from routing/on-link information which is associated with the
topology of the network and should be made consistent with the routing
tables
in the routers that manage that network.  If the information is managed
and accessable from two different sources, then it makes sense to have
two different mechanisms for managing that information.  If you have two
different mechanisms, then they should be orthogonal and cleanly
separate
concerns to avoid conflicts and confusion.

Just because "that's the way they did it in IPv4" is not a good reason
to
do it in IPv6 - we're supposed to be using the opportunity which is
given
to us by the total network upgrade to IPv6 in order to designing a
better=20
system than IPv4.

- Wes Beebee

-----Original Message-----
From: Ralph Droms (rdroms)=20
Sent: Saturday, August 11, 2007 6:29 AM
To: Leino, Tammy
Cc: ipv6@ietf.org; John Jason Brzozowski (JJMB)
Subject: Re: prefix length determination for DHCPv6

This issue was discussed in the dhc and v6ops WGs at the last IETF
meeting: http://www3.ietf.org/proceedings/07jul/slides/dhc-5.pdf

- Ralph

On Aug 10, 2007, at Aug 10, 2007,6:28 PM, Leino, Tammy wrote:

> Thank you John.
>
> 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 populating=20
> the routing table.
>
> Best Regards,
> Tammy
>
>
>
> -----Original Message-----
> From: John Jason Brzozowski (JJMB) [mailto:jjmb@jjmb.com]
> Sent: Friday, August 10, 2007 6:20 PM
> To: Hemant Singh (shemant); Leino, Tammy; ipv6@ietf.org
> Subject: RE: prefix length determination for DHCPv6
>
>
> Hello Hemant,
>
> There is no DHCPv6 mechabism to explicitly transmit router/gateway=20
> information.
>
> Regards,
>
> John
> ######################
> John Jason Brzozowski, CISSP, RHCT
> jjmb@jjmb.com
> 484-994-6787
> ######################
>
> -----Original Message-----
> From: "Hemant Singh (shemant)" <shemant@cisco.com>
> To: "Leino, Tammy" <tammy_leino@mentor.com>; ipv6@ietf.org
> Sent: 08/10/07 18:14
> Subject: RE: prefix length determination for DHCPv6
>
>
> ________________________________
>
> From: Leino, Tammy [mailto:tammy_leino@mentor.com]
> Sent: Friday, August 10, 2007 5:56 PM
> To: ipv6@ietf.org
> Subject: 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=20
> does the client determine the prefix length of the IPv6 address the=20
> server is assigning?
>
> <hs> One way to to send a Prefix Information Option (PIO) for the=20
> assigned address prefix in RA to the client.  PIO includes prefix=20
> length.
>
> </hs>
>
> Furthermore, in the absence of a configured IPv6 router on the link,=20
> can the client use the DHCPv6 server to find a default gateway out of=20
> the local network?
>
> <hs> I don't believe so. I'll let the DHCPv6 RFC authors like Ralph=20
> Droms and Bernie Volz verify this one.
>
> </hs>
>
> Hemant
>
>   If so, what RFC specifies this option?
>
> Any help or referrals to additional RFCs would be much appreciated.
>
> Best Regards,
> Tammy Leino
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

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

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



From ipv6-bounces@ietf.org Mon Aug 13 13:08:35 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKdN7-00063W-Fd; Mon, 13 Aug 2007 13:06:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IKdN6-00063P-HY
	for ipv6@ietf.org; Mon, 13 Aug 2007 13:06:28 -0400
Received: from mail128.messagelabs.com ([216.82.250.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IKdN5-0003j6-2d
	for ipv6@ietf.org; Mon, 13 Aug 2007 13:06:28 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-6.tower-128.messagelabs.com!1187024785!24372676!1
X-StarScan-Version: 5.5.12.11; banners=.,-,-
X-Originating-IP: [129.188.136.8]
Received: (qmail 8173 invoked from network); 13 Aug 2007 17:06:25 -0000
Received: from motgate8.mot.com (HELO motgate8.mot.com) (129.188.136.8)
	by server-6.tower-128.messagelabs.com with SMTP;
	13 Aug 2007 17:06:25 -0000
Received: from il06exr01.mot.com (il06exr01.mot.com [129.188.137.131])
	by motgate8.mot.com (8.12.11/Motorola) with ESMTP id l7DH6Ht1017467;
	Mon, 13 Aug 2007 10:06:21 -0700 (MST)
Received: from il06vts03.mot.com (il06vts03.mot.com [129.188.137.143])
	by il06exr01.mot.com (8.13.5/Vontu) with SMTP id l7DH6GkW013312;
	Mon, 13 Aug 2007 12:06:16 -0500 (CDT)
Received: from [127.0.0.1] (zfr01-2117.crm.mot.com [10.161.201.117])
	by il06exr01.mot.com (8.13.5/8.13.0) with ESMTP id l7DH6ERq013232;
	Mon, 13 Aug 2007 12:06:14 -0500 (CDT)
Message-ID: <46C08F80.30200@gmail.com>
Date: Mon, 13 Aug 2007 19:06:08 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Leino, Tammy" <tammy_leino@mentor.com>
References: <7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
In-Reply-To: <7ECEF9368E169544B43882BC98EB5D92032DA844@SVR-ALH-EXC-02.mgc.mentorg.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 000764-7, 12/08/2007), Outbound message
X-Antivirus-Status: Clean
X-Vontu: Pass
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, ipv6@ietf.org,
	"John Jason Brzozowski \(JJMB\)" <jjmb@jjmb.com>
Subject: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

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

> 
> Thank you again for your time and advice.
> 
> Best Regards, Tammy
> 
> 
> -----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
> 
> 
> On 11-aug-2007, at 1:09, Leino, Tammy wrote:
> 
>> 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.
> 
> But then, why do you need addresses when you have no external 
> connectivity? A lot of stuff will work just fine over link local 
> addresses, although the need to include a scope identifier gets in 
> the way of some applications.
> 
>>>> (There is of course the consideration that at this time, very
>>>> few
>> 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?
> 
> First of all, the DHCPv6 specification was finished relatively late,
>  in 2003 if I'm not mistaken. Most major vendors had already 
> implemented IPv6 by then and I'm guessing that deployment levels so
>  far haven't exactly given them much reason to drastically update 
> their IPv6 implementations.
> 
> 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.
> 
> Since address configuration has always happened and continues to 
> 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 
> school" IPv6 users are generally happy with stateless
> autoconfiguration.
> 
> That leaves:
> 
>> If they are not using DHCPv6, how do they distribute DNS servers
>> and other configuration information?
> 
> In practice? They don't. As long as you have IPv4, you can use IPv4
>  for this.
> 
> 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.
> 
> In the near future we'll have draft-jeong-dnsop-ipv6-dns- 
> 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.
> 
>> 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.
> 
> My opinion: DHCPv6 is a complex protocol that uses a relatively high
>  number of messages. In the past, UDP-based protocols have been 
> 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 
> default but only if RA flags indicate that they should do this, and
>  DNS configuration should be possible without DHCPv6.
> 
> 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.
> 
> -------------------------------------------------------------------- 
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www1.ietf.org/mailman/listinfo/ipv6 
> --------------------------------------------------------------------
> 


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

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



From ipv6-bounces@ietf.org Mon Aug 13 13:27:37 2007
Return-path: <ipv6-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-00058V-CZ; 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: RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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
--------------------------------------------------------------------

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



From ipv6-bounces@ietf.org Mon Aug 13 13:34:00 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKdm2-0001Ts-GY; Mon, 13 Aug 2007 13:32:14 -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: RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.

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



From ipv6-bounces@ietf.org Mon Aug 13 14:27:24 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKebd-0003Pf-Jd; Mon, 13 Aug 2007 14:25:33 -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: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Mon Aug 13 14:29:55 2007
Return-path: <ipv6-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-00069W-Ly; 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: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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?

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



From ipv6-bounces@ietf.org Mon Aug 13 14:46:59 2007
Return-path: <ipv6-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-0007rF-W1; 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>
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>
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Tue Aug 14 09:07:57 2007
Return-path: <ipv6-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-0002iS-1Z; 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: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Tue Aug 14 09:28:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKwQF-00012c-II; Tue, 14 Aug 2007 09:26:59 -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: Tue, 14 Aug 2007 09:26:57 -0400
Cc: Bernie Volz <volz@cisco.com>
Subject: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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  From ipv6-bounces@ietf.org Tue Aug 14 09:28:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKwQF-00012c-II; Tue, 14 Aug 2007 09:26:59 -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: Tue, 14 Aug 2007 09:26:57 -0400
Cc: Bernie Volz <volz@cisco.com>
Subject: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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

From ipv6-bounces@ietf.org Tue Aug 14 09:28:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKwQG-00012j-CK; Tue, 14 Aug 2007 09:27:00 -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
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
X-Mailman-Approved-At: Tue, 14 Aug 2007 09:26:57 -0400
Cc: ipv6@ietf.org
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1030102050=="
Errors-To: ipv6-bounces@ietf.org


--===============1030102050==
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 giv 42.496N   Fax +1 781 442 1677

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

From ipv6-bounces@ietf.org Tue Aug 14 09:28:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKwQG-00012j-CK; Tue, 14 Aug 2007 09:27:00 -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
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
X-Mailman-Approved-At: Tue, 14 Aug 2007 09:26:57 -0400
Cc: ipv6@ietf.org
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1030102050=="
Errors-To: ipv6-bounces@ietf.org


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


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

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

--===============1030102050==--






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


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

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

--===============1030102050==--






From ipv6-bounces@ietf.org Tue Aug 14 11:30:01 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IKyJ8-0005C0-Ox; Tue, 14 Aug 2007 11:27:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IKyJ6-0005Ab-ME
	for ipv6@ietf.org; Tue, 14 Aug 2007 11:27:44 -0400
Received: from ranger.systems.pipex.net ([62.241.162.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IKyJ5-0004cw-AD
	for ipv6@ietf.org; Tue, 14 Aug 2007 11:27:44 -0400
Received: from pc6 (1Cust211.tnt1.lnd4.gbr.da.uu.net [62.188.130.211])
	by ranger.systems.pipex.net (Postfix) with SMTP id 50B9EE00061B;
	Tue, 14 Aug 2007 16:27:40 +0100 (BST)
Message-ID: <021501c7de7e$7bcb11e0$0601a8c0@pc6>
From: "tom.petch" <cfinss@dial.pipex.com>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>
References: <8E296595B6471A4689555D5D725EBB2104B66C24@xmb-rtp-20a.amer.cisco.com>
	<B0259697-1C66-4053-AD82-661A54733544@muada.com>
Date: Tue, 14 Aug 2007 12:38:26 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: -98.6 (---------------------------------------------------)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: ipv6@ietf.org
Subject: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: "tom.petch" <cfinss@dial.pipex.com>
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

----- Original Message -----
From: "Iljitsch van Beijnum" <iljitsch@muada.com>
To: "Bernie Volz ((volz))" <volz@cisco.com>
Cc: <dhcwg@ietf.org>; "Alexandru Petrescu" <alexandru.petrescu@gmail.com>;
<ipv6@ietf.org>; "John Jason Brzozowski (JJMB)" <jjmb@jjmb.com>
Sent: Monday, August 13, 2007 8:26 PM
Subject: Re: prefix length determination for DHCPv6


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

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

Tom Petch

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


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



From ipv6-bounces@ietf.org Tue Aug 14 19:02:33 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IL5NA-00033m-7q; Tue, 14 Aug 2007 19:00:24 -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: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.

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



From ipv6-bounces@ietf.org Tue Aug 14 19:44:27 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IL627-00039Y-EO; Tue, 14 Aug 2007 19:42:43 -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>
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
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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



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



From ipv6-bounces@ietf.org Tue Aug 14 21:21:51 2007
Return-path: <ipv6-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-0006jo-W3; Tue, 14 Aug 2007 21:19:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IL7Xy-0006jS-Mj
	for ipv6@ietf.org; Tue, 14 Aug 2007 21:19:43 -0400
Received: from necom830.hpcl.titech.ac.jp ([131.112.32.132])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IL7Xw-0005XV-Ps
	for ipv6@ietf.org; Tue, 14 Aug 2007 21:19:42 -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>
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>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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


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



From ipv6-bounces@ietf.org Wed Aug 15 09:31:58 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILIwD-0001T6-Im; Wed, 15 Aug 2007 09:29:29 -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
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
Cc: dhcwg@ietf.org
Subject: RE: [dhcwg] RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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
--------------------------------------------------------------------

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



From ipv6-bounces@ietf.org Wed Aug 15 09:41:14 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILJ5p-0007nj-8I; Wed, 15 Aug 2007 09:39:25 -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
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
X-Mailman-Approved-At: Wed, 15 Aug 2007 09:39:23 -0400
Cc: ipv6@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1819798586=="
Errors-To: ipv6-bounces@ietf.org


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


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

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

--===============1819798586==--




From ipv6-bounces@ietf.org Wed Aug 15 10:00:42 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILJOg-0006sO-GS; Wed, 15 Aug 2007 09:58:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILJOd-0006qz-UR
	for ipv6@ietf.org; Wed, 15 Aug 2007 09:58:51 -0400
Received: from smtp5.smtp.bt.com ([217.32.164.139])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ILJOc-0005bV-Fa
	for ipv6@ietf.org; Wed, 15 Aug 2007 09:58:51 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.114]) by
	smtp5.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 15 Aug 2007 14:58:49 +0100
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: Wed, 15 Aug 2007 15:00:24 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B0DBB297@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <20070815194551.e2264a08.ipng@69706e6720323030352d30312d31340a.nosense.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: prefix length determination for DHCPv6
Thread-Index: AcffQgMPnlHuRanbTe6g/X7cLJftzAAAfzWg
References: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<20070815194551.e2264a08.ipng@69706e6720323030352d30312d31340a.nosense.org>
From: <michael.dillon@bt.com>
To: <ipng@69706e6720323030352d30312d31340a.nosense.org>,
	<ipv6@ietf.org>
X-OriginalArrivalTime: 15 Aug 2007 13:58:49.0339 (UTC)
	FILETIME=[67AB2CB0:01C7DF44]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: 
Subject: RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> A fixed length network portion is also simpler and easier to=20
> administer and operate if you have the opportunity, which is=20
> why I'm an advocate for /48s for nearly everybody. Leaving=20
> the problems of dealing with the complexity of variable=20
> length prefixes to the expert employees of the network=20
> service providers, not their customers, makes good sense to me.
> Again, I think people who've worked with Novell IPX or=20
> Appletalk would also agree.

Then you need to get involved in setting RIR policy because this concept
of the fixed /48 network size is already starting to disappear. Nobody
from the IETF was available to explain why the designers of IPv6
intended for /48 to be the fixed length network size when ARIN passed a
policy to allow ISPs to allocate /56s to consumer customers. Even though
the ARIN decision was not a bad one, unless better understanding of the
IPv6 design is communicated, then the /48 boundary will fade away and
everyone will have to renumber their networks when they change
providers.

--Michael Dillon

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



From ipv6-bounces@ietf.org Wed Aug 15 10:22:09 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILJjP-0005Zl-O4; Wed, 15 Aug 2007 10:20:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILJjO-0005Ze-Ey
	for ipv6@ietf.org; Wed, 15 Aug 2007 10:20:18 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ILJjO-000699-19
	for ipv6@ietf.org; Wed, 15 Aug 2007 10:20:18 -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 l7FEGkZI057762
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Wed, 15 Aug 2007 16:16:46 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <D03E4899F2FB3D4C8464E8C76B3B68B0DBB297@E03MVC4-UKBR.domain1.systemhost.net>
References: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>
	<20070815194551.e2264a08.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<D03E4899F2FB3D4C8464E8C76B3B68B0DBB297@E03MVC4-UKBR.domain1.systemhost.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <6E52580F-951E-4760-B0A5-1601BCA0864A@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Wed, 15 Aug 2007 16:18:54 +0200
To: "<michael.dillon@bt.com>" <michael.dillon@bt.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: ipv6@ietf.org
Subject: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 15-aug-2007, at 16:00, <michael.dillon@bt.com>  
<michael.dillon@bt.com> wrote:

> Nobody from the IETF was available to explain why the designers of  
> IPv6
> intended for /48 to be the fixed length network size when ARIN  
> passed a
> policy to allow ISPs to allocate /56s to consumer customers. Even  
> though
> the ARIN decision was not a bad one,

I'm still somewhat blue in the face from explaining exactly why this  
was a bad decision.

- extremely few people need more than a /48
- /48 everywhere means that you don't have to renumber bits 48 - 63  
when you change ISPs
- a decent number of people need more than a /56
- of that number, many won't know it in advance
- with 256 subnets deployed you're already big enough that  
renumbering is painful

The right choice is to give a /48 to people who want one and a /60 to  
everyone else. If you discover that you need more than a /60 and you  
only have upto 16 subnets deployed renumbering is much easier than  
with /56 and 256. With /56 you need to think about it in advance,  
which we want to avoid because thinking hurts and usually, the  
results are wrong.

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



From ipv6-bounces@ietf.org Wed Aug 15 10:35:34 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILJwE-0007BH-Da; Wed, 15 Aug 2007 10:33:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILJwD-00077W-Cy
	for ipv6@ietf.org; Wed, 15 Aug 2007 10:33:33 -0400
Received: from mx.isc.org ([2001:4f8:0:2::1c])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ILJwC-0006mo-KP
	for ipv6@ietf.org; Wed, 15 Aug 2007 10:33:33 -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 2AA6211402A
	for <ipv6@ietf.org>; Wed, 15 Aug 2007 14:33:32 +0000 (UTC)
	(envelope-from Mark_Andrews@isc.org)
Received: from drugs.dv.isc.org (localhost.isc.org [IPv6:::1])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client CN "drugs.dv.isc.org", Issuer "ISC CA" (verified OK))
	by farside.isc.org (Postfix) with ESMTP id 8F2F2E602B
	for <ipv6@ietf.org>; Wed, 15 Aug 2007 14:33:31 +0000 (UTC)
	(envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.14.1/8.14.1) with ESMTP id l7FEXKSQ045220;
	Thu, 16 Aug 2007 00:33:20 +1000 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200708151433.l7FEXKSQ045220@drugs.dv.isc.org>
To: michael.dillon@bt.com
From: Mark Andrews <Mark_Andrews@isc.org>
In-reply-to: Your message of "Wed, 15 Aug 2007 15:00:24 +0100."
	<D03E4899F2FB3D4C8464E8C76B3B68B0DBB297@E03MVC4-UKBR.domain1.systemhost.net>
Date: Thu, 16 Aug 2007 00:33:20 +1000
X-Spam-Score: -1.4 (-)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: ipv6@ietf.org
Subject: Re: prefix length determination for DHCPv6 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


> > A fixed length network portion is also simpler and easier to=20
> > administer and operate if you have the opportunity, which is=20
> > why I'm an advocate for /48s for nearly everybody. Leaving=20
> > the problems of dealing with the complexity of variable=20
> > length prefixes to the expert employees of the network=20
> > service providers, not their customers, makes good sense to me.
> > Again, I think people who've worked with Novell IPX or=20
> > Appletalk would also agree.
> 
> Then you need to get involved in setting RIR policy because this concept
> of the fixed /48 network size is already starting to disappear. Nobody
> from the IETF was available to explain why the designers of IPv6
> intended for /48 to be the fixed length network size when ARIN passed a
> policy to allow ISPs to allocate /56s to consumer customers. Even though
> the ARIN decision was not a bad one, unless better understanding of the
> IPv6 design is communicated, then the /48 boundary will fade away and
> everyone will have to renumber their networks when they change
> providers.
> 
> --Michael Dillon

	While end sites are expected to be given a /48, that was
	expected to be divided into 65536 subnets of /64.  Whether
	you used all the 65536 subnets didn't matter.  It was enough
	subnets to cover all but the very large enterpises.

	Even if you needed more it should not be a real issue for
	ISP's to supply you with a /47 to give you 131072 subnets.
	Moving ISPs should still be easy as you are only equivalent
	to two customers.

	I suspect with /56 there will end up being a reasonable
	number of exception customers.  Enough I suspect that ISP's
	will maintain two pools.  One for /56's and one for /48's.

> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org

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



From ipv6-bounces@ietf.org Wed Aug 15 10:42:43 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILK3M-0004Qw-Sv; Wed, 15 Aug 2007 10:40:56 -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>
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
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Wed Aug 15 13:16:51 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILMS6-0006kq-VK; Wed, 15 Aug 2007 13:14:39 -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>
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
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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



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



From ipv6-bounces@ietf.org Wed Aug 15 14:07:54 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILNFt-0001qQ-Ev; Wed, 15 Aug 2007 14:06:05 -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>
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
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Wed Aug 15 14:33:48 2007
Return-path: <ipv6-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-00057J-8K; 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>
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: "David W. Hankins" <David_Hankins@isc.org>, ipv6@ietf.org, dhcwg@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Thu Aug 16 04:58:00 2007
Return-path: <ipv6-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-0003QT-Hr; 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>
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
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Thu Aug 16 05:13:35 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILbON-000527-JC; Thu, 16 Aug 2007 05:11:47 -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: Thu, 16 Aug 2007 05:11:44 -0400
Cc: "volz <volz@cisco.com>, dhcwg@ietf.org, ipv6@ietf.org,
	\"John Jason Brzozowski \(JJMB\)\" <jjmb@jjmb.com>" <Bernie>
Subject: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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 lengthFrom ipv6-bounces@ietf.org Thu Aug 16 05:13:35 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILbON-000527-JC; Thu, 16 Aug 2007 05:11:47 -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: Thu, 16 Aug 2007 05:11:44 -0400
Cc: "volz <volz@cisco.com>, dhcwg@ietf.org, ipv6@ietf.org,
	\"John Jason Brzozowski \(JJMB\)\" <jjmb@jjmb.com>" <Bernie>
Subject: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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 lengthFrom ipv6-bounces@ietf.org Thu Aug 16 05:13:35 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILbON-000527-JC; Thu, 16 Aug 2007 05:11:47 -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: Thu, 16 Aug 2007 05:11:44 -0400
Cc: "volz <volz@cisco.com>, dhcwg@ietf.org, ipv6@ietf.org,
	\"John Jason Brzozowski \(JJMB\)\" <jjmb@jjmb.com>" <Bernie>
Subject: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.

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



From ipv6-bounces@ietf.org Thu Aug 16 05:13:35 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILbOM-00050B-Dx; Thu, 16 Aug 2007 05:11:46 -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
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
X-Mailman-Approved-At: Thu, 16 Aug 2007 05:11:44 -0400
Cc: ipv6@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv 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.

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



From ipv6-bounces@ietf.org Thu Aug 16 05:13:35 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILbOM-00050B-Dx; Thu, 16 Aug 2007 05:11:46 -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
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
X-Mailman-Approved-At: Thu, 16 Aug 2007 05:11:44 -0400
Cc: ipv6@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv 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.

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



From ipv6-bounces@ietf.org Thu Aug 16 05:13:35 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILbOM-00050B-Dx; Thu, 16 Aug 2007 05:11:46 -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
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
X-Mailman-Approved-At: Thu, 16 Aug 2007 05:11:44 -0400
Cc: ipv6@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0864763719=="
Errors-To: ipv6-bounces@ietf.org


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


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

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

--===============0864763719==--


From ipv6-bounces@ietf.org Thu Aug 16 05:13:35 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILbOO-00054f-Cm; Thu, 16 Aug 2007 05:11:48 -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.286-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0864763719=="
Errors-To: ipv6-bounces@ietf.org


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


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

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

--===============0864763719==--


From ipv6-bounces@ietf.org Thu Aug 16 05:13:35 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILbOO-00054f-Cm; Thu, 16 Aug 2007 05:11:48 -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.286-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0864763719=="
Errors-To: ipv6-bounces@ietf.org


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


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

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

--===============0864763719==--


From ipv6-bounces@ietf.org Thu Aug 16 05:13:35 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILbOO-00054f-Cm; Thu, 16 Aug 2007 05:11:48 -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: Thu, 16 Aug 2007 05:11:44 -0400
Cc: "volz <volz@cisco.com>, dhcwg@ietf.org, ipv6@ietf.org,
	\"John Jason Brzozowski \(JJMB\)\" <jjmb@jjmb.com>" <Bernie>
Subject: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.

----------------------------------------------------------])
	(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: Thu, 16 Aug 2007 05:11:44 -0400
Cc: "volz <volz@cisco.com>, dhcwg@ietf.org, ipv6@ietf.org,
	\"John Jason Brzozowski \(JJMB\)\" <jjmb@jjmb.com>" <Bernie>
Subject: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.

----------------------------------------------------------])
	(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: Thu, 16 Aug 2007 05:11:44 -0400
Cc: "volz <volz@cisco.com>, dhcwg@ietf.org, ipv6@ietf.org,
	\"John Jason Brzozowski \(JJMB\)\" <jjmb@jjmb.com>" <Bernie>
Subject: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.

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





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





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





From ipv6-bounces@ietf.org Thu Aug 16 05:13:35 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILbOL-000503-B7; Thu, 16 Aug 2007 05:11:45 -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
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
X-Mailman-Approved-At: Thu, 16 Aug 2007 05:11:44 -0400
Cc: ipv6@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0108027165=="
Errors-To: ipv6-bounces@ietf.org


--===============0108027165==
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+/--


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

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

--===============0108027165==--




From ipv6-bounces@ietf.org Thu Aug 16 06:48:55 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILcs7-0003QT-Cl; Thu, 16 Aug 2007 06:46:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILcs5-0003QL-BM; Thu, 16 Aug 2007 06:46:33 -0400
Received: from postfix.iai.uni-bonn.de ([131.220.8.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILcs3-0002UD-Si; Thu, 16 Aug 2007 06:46:33 -0400
X-IAI-Env-From: <ignatios@cello.cs.uni-bonn.de> : [131.220.4.211]
Received: from theory.cs.uni-bonn.de (theory.cs.uni-bonn.de [131.220.4.211])
	by postfix.iai.uni-bonn.de (Postfix) with ESMTP
	id 50D7E5C832; Thu, 16 Aug 2007 12:46:30 +0200 (MEST)
	(envelope-from ignatios@cello.cs.uni-bonn.de)
	(envelope-to VARIOUS) (2)
	(internal use: ta=0, tu=1, te=0, am=-, au=-)
Received: from cello.cs.uni-bonn.de (cello.cs.uni-bonn.de [131.220.4.178])
	by theory.cs.uni-bonn.de (8.12.9/8.12.9) with SMTP id l7GAkUX8028665;
	Thu, 16 Aug 2007 12:46:30 +0200 (MEST)
Received: (from ignatios@cello.cs.uni-bonn.de)
	by cello.cs.uni-bonn.de (mini_sendmail/1.3.2 21nov2002 nb4 7oct2003);
	Thu, 16 Aug 2007 12:46:30 CEST (sender ignatios@cello.cs.uni-bonn.de)
Date: Thu, 16 Aug 2007 12:46:29 +0200
From: Ignatios Souvatzis <ignatios@cs.uni-bonn.de>
To: dhcwg@ietf.org, ipv6@ietf.org
Message-ID: <20070816104629.GB20352@cs.uni-bonn.de>
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
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070816071847.b1ecac48.ipng@69706e6720323030352d30312d31340a.nosense.org>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: 
Subject: Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Thu, Aug 16, 2007 at 07:18:47AM +0930, Mark Smith wrote:

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

Historical remark: To a certain degree.

Area addresses have a fixed size (6 bits), and node addresses within an
area also have a fixed size (10 bits). But Areas are not bound to a
LAN. All host addressing on a link is done via sort of neighbour
discovery (using hello packets). Areas are used for (I think) IS-IS- or
OSPF-like two-level routing, but could consist of any number of LANs
and point to point links.

(Ethernet LAN addresses were created by concatenating the full DECnet
address (16 bits) and DEC's prefix AA-00-04-00-.)


	-is

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



From ipv6-bounces@ietf.org Thu Aug 16 08:22:52 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILeLG-000587-37; Thu, 16 Aug 2007 08:20:46 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILeLE-000581-J3
	for ipv6@ietf.org; Thu, 16 Aug 2007 08:20:44 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ILeLE-0005cO-7O
	for ipv6@ietf.org; Thu, 16 Aug 2007 08:20:44 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 7E962198680
	for <ipv6@ietf.org>; Thu, 16 Aug 2007 15:20:42 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 49B631985FA
	for <ipv6@ietf.org>; Thu, 16 Aug 2007 15:20:42 +0300 (EEST)
Message-ID: <46C4411C.6000504@piuha.net>
Date: Thu, 16 Aug 2007 15:20:44 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: IETF IPv6 Mailing List <ipv6@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: de4f315c9369b71d7dd5909b42224370
Subject: Status of the ra-flags draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


I have made my AD review of this document and found no
issues. The document will be moved forward.

By the way, note that the immediate need for this may be
less pressing now than a few months before. DNA WG
who was previously planning to use more bits is now
re-considering their solution for other reasons and
the new solution may not end up needing bits at all.
Also, I saw that the WGLC response came from just
a few persons. I'm not too happy about that but
perhaps it is acceptable in this case given that the
document is merely a maintenance update to provide
more space for future extensions.

Jari


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



From ipv6-bounces@ietf.org Thu Aug 16 09:06:26 2007
Return-path: <ipv6-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-0002nM-7J; 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>
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
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Thu Aug 16 13:23:42 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILj25-0003nE-A6; Thu, 16 Aug 2007 13:21:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILj22-0003jx-3b; Thu, 16 Aug 2007 13:21:14 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1ILj20-0005RY-W4; Thu, 16 Aug 2007 13:21:14 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id DF89532896;
	Thu, 16 Aug 2007 17:20:42 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1ILj1W-0002cs-QO; Thu, 16 Aug 2007 13:20:42 -0400
X-test-idtracker: no
To: IETF-Announce <ietf-announce@ietf.org>
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <E1ILj1W-0002cs-QO@stiedprstage1.ietf.org>
Date: Thu, 16 Aug 2007 13:20:42 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: ipv6@ietf.org
Subject: Last Call: draft-ietf-ipv6-ra-flags-option (IPv6 Router 
 Advertisement Flags Option) to Proposed Standard 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

The IESG has received a request from the IP Version 6 Working Group WG 
(ipv6) to consider the following document:

- 'IPv6 Router Advertisement Flags Option '
   <draft-ietf-ipv6-ra-flags-option-01.txt> as a Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2007-08-30. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-ipv6-ra-flags-option-01.txt



IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=16067&rfc_flag=0


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



From ipv6-bounces@ietf.org Thu Aug 16 15:38:02 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILl8W-0007h6-JC; Thu, 16 Aug 2007 15:36:04 -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
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
Cc: dhcwg@ietf.org, ipv6@ietf.org
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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
--------------------------------------------------------------------

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



From ipv6-bounces@ietf.org Thu Aug 16 16:55:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILmKb-0000PF-Pm; Thu, 16 Aug 2007 16:52:37 -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
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
Cc: ipv6@ietf.org
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Thu Aug 16 17:01:23 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILmRI-0005fV-2X; Thu, 16 Aug 2007 16:59:32 -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
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
Cc: ipv6@ietf.org
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Thu Aug 16 18:12:02 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILnXY-00022X-DJ; Thu, 16 Aug 2007 18:10:04 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILn62-0004G2-73
	for ipv6@ietf.org; Thu, 16 Aug 2007 17:41:38 -0400
Received: from uillean.fuaim.com ([206.197.161.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ILn61-0006Ai-Pf
	for ipv6@ietf.org; Thu, 16 Aug 2007 17:41:38 -0400
Received: from localhost (localhost.fuaim.com [127.0.0.1])
	by uillean.fuaim.com (Postfix) with ESMTP id 1B942BD65
	for <ipv6@ietf.org>; Thu, 16 Aug 2007 14:41:07 -0700 (PDT)
Received: from uillean.fuaim.com ([127.0.0.1])
	by localhost (uillean.fuaim.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 01264-01-44 for <ipv6@ietf.org>;
	Thu, 16 Aug 2007 14:41:04 -0700 (PDT)
Received: from clairseach.fuaim.com (unknown
	[IPv6:2001:470:117:128:209:5bff:fe8e:6dd3])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(No client certificate requested)
	by uillean.fuaim.com (Postfix) with ESMTP id C30E0BF19
	for <ipv6@ietf.org>; Thu, 16 Aug 2007 14:33:59 -0700 (PDT)
Received: from [172.17.55.4] (c-76-100-31-131.hsd1.md.comcast.net
	[76.100.31.131]) (authenticated bits=0)
	by clairseach.fuaim.com (8.12.8/8.12.8) with ESMTP id l7GLP64Z002546
	for <ipv6@ietf.org>; Thu, 16 Aug 2007 14:25:07 -0700
Message-ID: <46C4C2A7.3080503@innovationslab.net>
Date: Thu, 16 Aug 2007 17:33:27 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509)
MIME-Version: 1.0
To: IPv6 WG <ipv6@ietf.org>
X-Enigmail-Version: 0.94.1.2
Content-Type: multipart/mixed; boundary="------------020302000503070402050504"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
X-Mailman-Approved-At: Thu, 16 Aug 2007 18:10:01 -0400
Subject: Revised 6MAN Charter
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

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

All,
     I have revised the charter for the proposed IPv6 maintenance WG
based on comments received.  Please review.

Regards,
Brian



--------------020302000503070402050504
Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0";
	name="6man-charter.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="6man-charter.txt"

IPv6 Maintenance Working Group (6man)
------------------------------------------------------------------------

Chair(s):

     Robert Hinden <bob.hinden@nokia.com>
     Brian Haberman <brian@innovationslab.net>


Internet Area Director(s):

     Jari Arkko <jari.arkko@piuha.net>
     Mark Townsley <townsley@cisco.com>


Internet Area Advisor:

     Jari Arkko <jari.arkko@piuha.net>


Mailing Lists: ipv6@ietf.org


Description of Working Group:

The 6man working group is responsible for the maintenance, upkeep, and advancement
of the IPv6 protocol specifications and addressing architecture.  It is not chartered to
develop major changes or additions to the IPv6 specifications.
The working group will address protocol limitations/issues discovered during
deployment and operation.  It will also serve as a venue for discussing the proper location
for working on IPv6-related issues within the IETF.

The working group's work items are as follows:

     o Shepherd completion of standardization of RA Flags Option
     o Shepherd completion of standardization of the RH0 Deprecation document
     o Complete standardization of IPv6 over PPP Compression Negotiation as a Proposed Standard
     o Complete work on Centrally Allocated Unique Local Addresses (ULA-C)

All new work items not listed above require the approval of the working
group and IESG before they will be taken on by the working group.


Goals and Milestones:

Oct 2007     Submit RH0 Deprecation specification to IESG as a Proposed Standard
Jan 2008     Submit PPP Compression Negotiation specification to IESG as a Proposed Standard
Mar 2008     Determine way forward for ULA-C specification



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

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

--------------020302000503070402050504--




From ipv6-bounces@ietf.org Thu Aug 16 18:12:02 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILnXZ-00022d-0W; Thu, 16 Aug 2007 18:10:05 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILn9N-00062b-FJ
	for ipv6@ietf.org; Thu, 16 Aug 2007 17:45:05 -0400
Received: from uillean.fuaim.com ([206.197.161.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ILn9N-0006FC-0l
	for ipv6@ietf.org; Thu, 16 Aug 2007 17:45:05 -0400
Received: from localhost (localhost.fuaim.com [127.0.0.1])
	by uillean.fuaim.com (Postfix) with ESMTP id 8AB34C266
	for <ipv6@ietf.org>; Thu, 16 Aug 2007 14:44:34 -0700 (PDT)
Received: from uillean.fuaim.com ([127.0.0.1])
	by localhost (uillean.fuaim.com [127.0.0.1]) (amavisd-new, port 10024)
	with LMTP id 01360-01-34 for <ipv6@ietf.org>;
	Thu, 16 Aug 2007 14:44:31 -0700 (PDT)
Received: from clairseach.fuaim.com (unknown
	[IPv6:2001:470:117:128:209:5bff:fe8e:6dd3])
	(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
	(No client certificate requested)
	by uillean.fuaim.com (Postfix) with ESMTP id 65EE6C018
	for <ipv6@ietf.org>; Thu, 16 Aug 2007 03:36:27 -0700 (PDT)
Received: from [172.17.55.4] (c-76-100-31-131.hsd1.md.comcast.net
	[76.100.31.131]) (authenticated bits=0)
	by clairseach.fuaim.com (8.12.8/8.12.8) with ESMTP id l7GARX4Z031276
	for <ipv6@ietf.org>; Thu, 16 Aug 2007 03:27:35 -0700
Message-ID: <46C4288A.1060408@innovationslab.net>
Date: Thu, 16 Aug 2007 06:35:54 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 1.5.0.12 (Macintosh/20070509)
MIME-Version: 1.0
To: IPv6 WG <ipv6@ietf.org>
X-Enigmail-Version: 0.94.1.2
Content-Type: multipart/mixed; boundary="------------010103040801010405060205"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
X-Mailman-Approved-At: Thu, 16 Aug 2007 18:10:01 -0400
Subject: Revised 6MAN Charter
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

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

All,
     I have revised the charter for the proposed IPv6 maintenance WG
based on comments received.  Please review.

Regards,
Brian


--------------010103040801010405060205
Content-Type: text/plain; x-mac-type="54455854"; x-mac-creator="74657874";
	name="6man-charter.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="6man-charter.txt"

IPv6 Maintenance Working Group (6man)
------------------------------------------------------------------------

Chair(s):

     Robert Hinden <bob.hinden@nokia.com>
     Brian Haberman <brian@innovationslab.net>


Internet Area Director(s):

     Jari Arkko <jari.arkko@piuha.net>
     Mark Townsley <townsley@cisco.com>


Internet Area Advisor:

     Jari Arkko <jari.arkko@piuha.net>


Mailing Lists: ipv6@ietf.org


Description of Working Group:

The 6man working group is responsible for the maintenance, upkeep, and advancement
of the IPv6 protocol specifications and addressing architecture.  It is not chartered to
develop major changes or additions to the IPv6 specifications.
The working group will address protocol limitations/issues discovered during
deployment and operation.  It will also serve as a venue for discussing the proper location
for working on IPv6-related issues within the IETF.

The working group's work items are as follows:

     o Shepherd completion of standardization of RA Flags Option
     o Shepherd completion of standardization of the RH0 Deprecation document
     o Complete standardization of IPv6 over PPP Compression Negotiation as a Proposed Standard
     o Complete work on Centrally Allocated Unique Local Addresses (ULA-C)

All new work items not listed above require the approval of the working
group and IESG before they will be taken on by the working group.


Goals and Milestones:

Oct 2007     Submit RH0 Deprecation specification to IESG as a Proposed Standard
Jan 2008     Submit PPP Compression Negotiation specification to IESG as a Proposed Standard
Mar 2008     Determine way forward for ULA-C specification


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

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

--------------010103040801010405060205--




From ipv6-bounces@ietf.org Thu Aug 16 18:12:10 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILnY8-00030Y-6K; Thu, 16 Aug 2007 18:10:40 -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
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
X-Mailman-Approved-At: Thu, 16 Aug 2007 18:10:38 -0400
Cc: ipv6@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2068136646=="
Errors-To: ipv6-bounces@ietf.org


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


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

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

--===============2068136646==--




From ipv6-bounces@ietf.org Thu Aug 16 18:13:01 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILnYh-0003jA-45; Thu, 16 Aug 2007 18:11:15 -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
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
X-Mailman-Approved-At: Thu, 16 Aug 2007 18:11:13 -0400
Cc: ipv6@ietf.org
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1684021331=="
Errors-To: ipv6-bounces@ietf.org


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


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

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

--===============1684021331==--




From ipv6-bounces@ietf.org Thu Aug 16 18:26:20 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILnlY-0004vW-92; Thu, 16 Aug 2007 18:24:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILnlX-0004vR-G6
	for ipv6@ietf.org; Thu, 16 Aug 2007 18:24:31 -0400
Received: from wx-out-0506.google.com ([66.249.82.229])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ILnlW-0005wV-1I
	for ipv6@ietf.org; Thu, 16 Aug 2007 18:24:31 -0400
Received: by wx-out-0506.google.com with SMTP id h27so317006wxd
	for <ipv6@ietf.org>; Thu, 16 Aug 2007 15:24:29 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:from:to:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language;
	b=YWCax2364Bd/BDC1XP/bVe3Ra20NqpqIhWX3bxOmH/mXrQCWYuAAF1aX7mYucWma31CzYoAhTMRWCPAFnbcN1aE104h6I2lTVongEtiDpaObx1l2sTKonwV8XbOho7HT8tALHo7qc8e9tLdfAlBZ0CWOHFuDgTN7UhtdclShGdU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:from:to:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language;
	b=VpwUTOq4y4VJiVYA9K1zSL0BIQp77ZrJC1mHctadhervZGbCf+4oZFu1WBSaCkcMwn0ztyIyi6ilR5VUyiQ1/IGv+9ItTpzq9W2TBtlGYZ8CK5oqsygYqkn2QAw9Nc+/Ch7Lgk2atLQvbtHQO/JJbwr3wVJ/pdJ7/9qZyzLgr10=
Received: by 10.70.99.9 with SMTP id w9mr3597704wxb.1187303065599;
	Thu, 16 Aug 2007 15:24:25 -0700 (PDT)
Received: from Lapci010 ( [76.21.226.168])
	by mx.google.com with ESMTPS id h15sm2114954wxd.2007.08.16.15.24.22
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Thu, 16 Aug 2007 15:24:23 -0700 (PDT)
From: "TJ" <trejrco@gmail.com>
To: <ipv6@ietf.org>
References: <8E296595B6471A4689555D5D725EBB2104B66945@xmb-rtp-20a.amer.cisco.com><8C324AEB-292B-42E5-A6B6-44017634AA59@muada.com>	<20070815194551.e2264a08.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<D03E4899F2FB3D4C8464E8C76B3B68B0DBB297@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <D03E4899F2FB3D4C8464E8C76B3B68B0DBB297@E03MVC4-UKBR.domain1.systemhost.net>
Date: Thu, 16 Aug 2007 18:26:16 -0400
Message-ID: <001201c7e054$77857c60$66907520$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcffQgMPnlHuRanbTe6g/X7cLJftzAAAfzWgAEP4ceA=
Content-Language: en-us
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Subject: RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

WRT "IPv6 design is communicated, then the /48 boundary will fade away and
everyone will have to renumber their networks when they change providers."
	... technically, they will need to renumber anyway - but now they
will also need to re-architect their network / subnet allocation.

AFAIK, the move towards /56 allocations is simply a nod towards address
conservation / efficient allocation policies.
	For my $.02 - I would hope that any client moving from one ISP's /48
would "encourage" the new ISP to match the allocation size :).
		((Or, go PI at that time ... get their own allocation ...
and not worry about it every again.))


/TJ


-----Original Message-----
From: michael.dillon@bt.com [mailto:michael.dillon@bt.com] 
Sent: Wednesday, August 15, 2007 10:00 AM
To: ipng@69706e6720323030352d30312d31340a.nosense.org; ipv6@ietf.org
Subject: RE: prefix length determination for DHCPv6

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

Then you need to get involved in setting RIR policy because this concept
of the fixed /48 network size is already starting to disappear. Nobody
from the IETF was available to explain why the designers of IPv6
intended for /48 to be the fixed length network size when ARIN passed a
policy to allow ISPs to allocate /56s to consumer customers. Even though
the ARIN decision was not a bad one, unless better understanding of the
IPv6 design is communicated, then the /48 boundary will fade away and
everyone will have to renumber their networks when they change
providers.

--Michael Dillon

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


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



From ipv6-bounces@ietf.org Thu Aug 16 18:29:45 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILnor-00081x-TY; Thu, 16 Aug 2007 18:27:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILnop-00081f-L9
	for ipv6@ietf.org; Thu, 16 Aug 2007 18:27:55 -0400
Received: from wx-out-0506.google.com ([66.249.82.225])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ILnoo-00060D-F2
	for ipv6@ietf.org; Thu, 16 Aug 2007 18:27:55 -0400
Received: by wx-out-0506.google.com with SMTP id h27so317536wxd
	for <ipv6@ietf.org>; Thu, 16 Aug 2007 15:27:54 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:from:to:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language;
	b=sgMMtPRyJAHq8kIYlPqovYVan2oRlMURkTVJUCyNdfGvk3584DcTsAMYGXWIusTVmvwIJ2N5MVroNqwKS0o27OdJf00OwjAs80QWgg4ijsV0xdveM0525g6EYn/TNgPnPGwUbiULyhR/2d2eyEaYkE7nsr65DUWwRT8+D7Jm/l8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:from:to:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language;
	b=pWqhTHC7D0KR9svTNeXpbZO8e/inMu3U0qVP5ZF0pjZ8XgcFIOcYEQ3YrX+Rt+8b/IVAwAUS+W0zHMn/87zEAwKui73VxVuR++zmwoVR2CKDS5eU7iGBMux9F3Kk5Rq+CpD+2bFmOlNvUNTEuTLzhg0Aphu5QUmL1+IplEpbZps=
Received: by 10.70.21.4 with SMTP id 4mr3615743wxu.1187303267707;
	Thu, 16 Aug 2007 15:27:47 -0700 (PDT)
Received: from Lapci010 ( [76.21.226.168])
	by mx.google.com with ESMTPS id h39sm3413477wxd.2007.08.16.15.27.41
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Thu, 16 Aug 2007 15:27:45 -0700 (PDT)
From: "TJ" <trejrco@gmail.com>
To: <ipv6@ietf.org>
References: Your message of "Wed, 15 Aug 2007 15:00:24
	+0100."	<D03E4899F2FB3D4C8464E8C76B3B68B0DBB297@E03MVC4-UKBR.domain1.systemhost.net>
	<200708151433.l7FEXKSQ045220@drugs.dv.isc.org>
In-Reply-To: <200708151433.l7FEXKSQ045220@drugs.dv.isc.org>
Date: Thu, 16 Aug 2007 18:29:35 -0400
Message-ID: <001301c7e054$efe78270$cfb68750$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcffSWmQlAyc/LqiR++1kqZ35lGJ9QBCy13Q
Content-Language: en-us
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Subject: RE: prefix length determination for DHCPv6 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

" 	I suspect with /56 there will end up being a reasonable
	number of exception customers.  Enough I suspect that ISP's
	will maintain two pools.  One for /56's and one for /48's "

... which means now the customer who got a /56 needs to renumber in order to
move to the /48 :(.  
	Not necessary if the ISP in question followed a more flexible
allocation method (a la RFC3531).


/TJ


-----Original Message-----
From: Mark Andrews [mailto:Mark_Andrews@isc.org] 
Sent: Wednesday, August 15, 2007 10:33 AM
To: michael.dillon@bt.com
Cc: ipv6@ietf.org
Subject: Re: prefix length determination for DHCPv6 


> > A fixed length network portion is also simpler and easier to=20
> > administer and operate if you have the opportunity, which is=20
> > why I'm an advocate for /48s for nearly everybody. Leaving=20
> > the problems of dealing with the complexity of variable=20
> > length prefixes to the expert employees of the network=20
> > service providers, not their customers, makes good sense to me.
> > Again, I think people who've worked with Novell IPX or=20
> > Appletalk would also agree.
> 
> Then you need to get involved in setting RIR policy because this concept
> of the fixed /48 network size is already starting to disappear. Nobody
> from the IETF was available to explain why the designers of IPv6
> intended for /48 to be the fixed length network size when ARIN passed a
> policy to allow ISPs to allocate /56s to consumer customers. Even though
> the ARIN decision was not a bad one, unless better understanding of the
> IPv6 design is communicated, then the /48 boundary will fade away and
> everyone will have to renumber their networks when they change
> providers.
> 
> --Michael Dillon

	While end sites are expected to be given a /48, that was
	expected to be divided into 65536 subnets of /64.  Whether
	you used all the 65536 subnets didn't matter.  It was enough
	subnets to cover all but the very large enterpises.

	Even if you needed more it should not be a real issue for
	ISP's to supply you with a /47 to give you 131072 subnets.
	Moving ISPs should still be easy as you are only equivalent
	to two customers.

	I suspect with /56 there will end up being a reasonable
	number of exception customers.  Enough I suspect that ISP's
	will maintain two pools.  One for /56's and one for /48's.

> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org

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


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



From ipv6-bounces@ietf.org Thu Aug 16 18:44:18 2007
Return-path: <ipv6-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-0002qQ-9h; 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>
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: "David W. Hankins" <David_Hankins@isc.org>, ipv6@ietf.org, dhcwg@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.

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



From ipv6-bounces@ietf.org Thu Aug 16 18:53:45 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILoC8-0002t1-G5; Thu, 16 Aug 2007 18:52:00 -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
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: "David W. Hankins" <David_Hankins@isc.org>, ipv6@ietf.org, dhcwg@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.

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



From ipv6-bounces@ietf.org Thu Aug 16 19:11:00 2007
Return-path: <ipv6-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-0000pB-BG; 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>
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: "David W. Hankins" <David_Hankins@isc.org>, ipv6@ietf.org, dhcwg@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.

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



From ipv6-bounces@ietf.org Thu Aug 16 19:40:28 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILovD-0007JG-BP; Thu, 16 Aug 2007 19:38:35 -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
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: "David W. Hankins" <David_Hankins@isc.org>, ipv6@ietf.org, dhcwg@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.

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



From ipv6-bounces@ietf.org Fri Aug 17 05:48:50 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILyPd-00011j-PO; Fri, 17 Aug 2007 05:46:37 -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>
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: "David W. Hankins" <David_Hankins@isc.org>, ipv6@ietf.org, dhcwg@ietf.org,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.

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



From ipv6-bounces@ietf.org Fri Aug 17 10:02:24 2007
Return-path: <ipv6-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-0001Sk-Gw; 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
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>
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Fri Aug 17 10:33:00 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM2r0-0000ZN-T8; Fri, 17 Aug 2007 10:31:10 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IM2qz-0000ZG-MU
	for ipv6@ietf.org; Fri, 17 Aug 2007 10:31:09 -0400
Received: from vms040pub.verizon.net ([206.46.252.40])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IM2qz-0000Vh-DC
	for ipv6@ietf.org; Fri, 17 Aug 2007 10:31:09 -0400
Received: from vms074.mailsrvcs.net ([192.168.1.2])
	by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01
	(built Apr
	3 2006)) with ESMTPA id <0JMX00GNV9NX7CA0@vms040.mailsrvcs.net> for
	ipv6@ietf.org; Fri, 17 Aug 2007 09:31:09 -0500 (CDT)
Received: from 129.55.200.20 ([129.55.200.20])
	by vms074.mailsrvcs.net (Verizon Webmail) with HTTP; Fri,
	17 Aug 2007 09:31:08 -0500 (CDT)
Date: Fri, 17 Aug 2007 09:31:08 -0500 (CDT)
From: Tim Enos <timbeck04@verizon.net>
X-Originating-IP: [129.55.200.20]
To: IPv6 WG <ipv6@ietf.org>
Message-id: <20212041.8416671187361069043.JavaMail.root@vms074.mailsrvcs.net>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Subject: Re: Revised 6MAN Charter
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

I think the revised charter is all right. AFAIAC, ship it.

Best Regards,

Tim Enos
Rom 8:28

>All,
>     I have revised the charter for the proposed IPv6 maintenance WG
>based on comments received.  Please review.
>
>Regards,
>Brian
>
>
>
>--------------------------------------------------------------------
>IETF IPv6 working group mailing list
>ipv6@ietf.org
>Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>--------------------------------------------------------------------


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



From ipv6-bounces@ietf.org Fri Aug 17 11:29:38 2007
Return-path: <ipv6-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-0007CD-8n; 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
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>
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Fri Aug 17 11:33:59 2007
Return-path: <ipv6-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-0000y3-G4; 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
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>
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Fri Aug 17 12:14:25 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM4RA-00044P-Mf; Fri, 17 Aug 2007 12:12:36 -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>
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>
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Fri Aug 17 12:25:56 2007
Return-path: <ipv6-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-0000Qt-RF; 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
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>
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Fri Aug 17 12:40:10 2007
Return-path: <ipv6-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-0006lX-75; 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>,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: RE: 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Fri Aug 17 12:43:35 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM4tO-00008T-CO; Fri, 17 Aug 2007 12:41:46 -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>
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
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>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Fri Aug 17 12:48:32 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM4yD-00088i-V2; 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: Re: RE: 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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
>

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



From ipv6-bounces@ietf.org Fri Aug 17 12:48:46 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM4yW-0000No-0W; Fri, 17 Aug 2007 12:47:04 -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>,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: RE: 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Fri Aug 17 12:49:24 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM4z9-0000kq-WE; Fri, 17 Aug 2007 12:47:44 -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>
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>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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
> --------------------------------------------------------------------

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



From ipv6-bounces@ietf.org Fri Aug 17 12:55:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM55A-0004D6-QX; Fri, 17 Aug 2007 12:53:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IM559-00048K-22
	for ipv6@ietf.org; Fri, 17 Aug 2007 12:53:55 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IM558-0006NW-FO
	for ipv6@ietf.org; Fri, 17 Aug 2007 12:53:54 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l7HGrjsV029919; Fri, 17 Aug 2007 19:53:52 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 19:53:49 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 17 Aug 2007 11:53:45 -0500
Received: from 172.19.244.81 ([172.19.244.81]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Fri, 17 Aug 2007 16:53:45 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Fri, 17 Aug 2007 11:53:50 -0500
From: Basavaraj Patil <basavaraj.patil@nsn.com>
To: ext Jari Arkko <jari.arkko@piuha.net>,
	IETF IPv6 Mailing List <ipv6@ietf.org>
Message-ID: <C2EB3CCE.40A9B%basavaraj.patil@nsn.com>
Thread-Topic: Status of the ra-flags draft
Thread-Index: Acfg7y9gbiTZ1kziEdyA6wARJNUNiA==
In-Reply-To: <46C4411C.6000504@piuha.net>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 17 Aug 2007 16:53:45.0834 (UTC)
	FILETIME=[2CE4B4A0:01C7E0EF]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: 
Subject: Re: Status of the ra-flags draft
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


Hi Jari,

As an FYI:
There is a need to indicate PMIP6 capability in the network via RA options.
This is being proposed in I-D: draft-damic-netlmm-pmip6-ind-discover-01.txt

-Raj


On 8/16/07 7:20 AM, "ext Jari Arkko" <jari.arkko@piuha.net> wrote:

> 
> I have made my AD review of this document and found no
> issues. The document will be moved forward.
> 
> By the way, note that the immediate need for this may be
> less pressing now than a few months before. DNA WG
> who was previously planning to use more bits is now
> re-considering their solution for other reasons and
> the new solution may not end up needing bits at all.
> Also, I saw that the WGLC response came from just
> a few persons. I'm not too happy about that but
> perhaps it is acceptable in this case given that the
> document is merely a maintenance update to provide
> more space for future extensions.
> 
> Jari
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


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



From ipv6-bounces@ietf.org Fri Aug 17 12:58:00 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM57P-0005QW-6t; Fri, 17 Aug 2007 12:56:15 -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>
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>
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Fri Aug 17 13:06:14 2007
Return-path: <ipv6-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-0000KP-G6; 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
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>
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Fri Aug 17 13:17:22 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM5Q7-0001Vh-Uz; Fri, 17 Aug 2007 13:15:35 -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
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: 
Subject: RE: [dhcwg] Re: RE: 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Fri Aug 17 13:20:35 2007
Return-path: <ipv6-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-0006yb-6T; 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
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>
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Fri Aug 17 13:30:41 2007
Return-path: <ipv6-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-0006YD-D5; 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>
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>
Subject: Re: [dhcwg] Re: RE: 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Fri Aug 17 13:39:43 2007
Return-path: <ipv6-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-0006os-Ep; 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>
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
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.


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



From ipv6-bounces@ietf.org Fri Aug 17 14:39:17 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM6h4-0002XY-QG; Fri, 17 Aug 2007 14:37:10 -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>
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>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.

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



From ipv6-bounces@ietf.org Fri Aug 17 16:11:49 2007
Return-path: <ipv6-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-0001B6-T1; 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>
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: 
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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



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



From ipv6-bounces@ietf.org Fri Aug 17 16:43:34 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IM8df-0002ch-7Y; Fri, 17 Aug 2007 16:41:47 -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>
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>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Fri Aug 17 19:48:16 2007
Return-path: <ipv6-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-0001Ak-GL; 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>
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: 
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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



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



From ipv6-bounces@ietf.org Fri Aug 17 20:33:28 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMCE8-0007PC-Cf; Fri, 17 Aug 2007 20:31:40 -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
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: 
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Fri Aug 17 21:31:09 2007
Return-path: <ipv6-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-0004ih-Kh; 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: Re: on-link determination and DHCP6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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



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



From ipv6-bounces@ietf.org Sat Aug 18 08:09:03 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMN4d-0005Lw-Eb; Sat, 18 Aug 2007 08:06:35 -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
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 08:06:34 -0400
Cc: 
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0116095262=="
Errors-To: ipv6-bounces@ietf.org


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


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

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

--===============0116095262==--




From ipv6-bounces@ietf.org Sat Aug 18 20:02:30 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMYD9-0006jc-85; Sat, 18 Aug 2007 20:00:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IMYD7-0006jX-Lr
	for ipv6@ietf.org; Sat, 18 Aug 2007 20:00:05 -0400
Received: from [2002:425c:4242:0:210:5aff:fe86:1f54] (helo=cyteen.hactrn.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IMYD7-0005nn-6A
	for ipv6@ietf.org; Sat, 18 Aug 2007 20:00:05 -0400
Received: from cyteen.hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id 880E028463
	for <ipv6@ietf.org>; Sun, 19 Aug 2007 00:00:04 +0000 (UTC)
To: ipv6@ietf.org
From: Rob Austein <sra+ipng@hactrn.net>
Date: Sun, 19 Aug 2007 00:00:04 +0000
Message-Id: <20070819000004.880E028463@cyteen.hactrn.net>
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Subject: Weekly posting summary for ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 13.92% |   11 | 19.23% |   107242 | shemant@cisco.com
 15.19% |   12 | 11.84% |    66004 | iljitsch@muada.com
 11.39% |    9 | 11.21% |    62505 | james.d.carlson@sun.com
  7.59% |    6 |  8.18% |    45596 | david_hankins@isc.org
  7.59% |    6 |  7.18% |    40026 | jhw@apple.com
  6.33% |    5 |  7.80% |    43483 | rdroms@cisco.com
  5.06% |    4 |  4.60% |    25675 | fred.l.templin@boeing.com
  2.53% |    2 |  3.69% |    20591 | volz@cisco.com
  2.53% |    2 |  3.01% |    16762 | wbeebee@cisco.com
  2.53% |    2 |  2.54% |    14183 | trejrco@gmail.com
  2.53% |    2 |  2.54% |    14168 | tammy_leino@mentor.com
  2.53% |    2 |  2.39% |    13342 | ipng@69706e6720323030352d30312d31340a.nosense.org
  2.53% |    2 |  2.29% |    12790 | brian@innovationslab.net
  1.27% |    1 |  1.80% |    10014 | alexandru.petrescu@gmail.com
  1.27% |    1 |  1.25% |     6984 | jinmei@isl.rdc.toshiba.co.jp
  1.27% |    1 |  1.18% |     6591 | michael@gargantuan.com
  1.27% |    1 |  1.08% |     6000 | mark_andrews@isc.org
  1.27% |    1 |  1.01% |     5609 | ot@cisco.com
  1.27% |    1 |  0.91% |     5070 | ignatios@cs.uni-bonn.de
  1.27% |    1 |  0.90% |     5042 | basavaraj.patil@nsn.com
  1.27% |    1 |  0.87% |     4877 | cfinss@dial.pipex.com
  1.27% |    1 |  0.85% |     4764 | michael.dillon@bt.com
  1.27% |    1 |  0.77% |     4320 | sra+ipng@hactrn.net
  1.27% |    1 |  0.77% |     4290 | mohta@necom830.hpcl.titech.ac.jp
  1.27% |    1 |  0.72% |     4042 | iesg-secretary@ietf.org
  1.27% |    1 |  0.69% |     3872 | jari.arkko@piuha.net
  1.27% |    1 |  0.68% |     3786 | timbeck04@verizon.net
--------+------+--------+----------+------------------------
100.00% |   79 |100.00% |   557628 | Total

Grunchweather Associates provides this automatic summary on an at-whim
basis at the request of the IPv6 WG chairs.  Your mileage may vary.
We decline responsibilities, all shapes, all sizes, all colors.
If this script produces broken output, you get to keep both pieces.

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



From ipv6-bounces@ietf.org Sat Aug 18 20:25:37 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMYZz-0007NB-F0; 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>
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: 
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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...
>

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



From ipv6-bounces@ietf.org Sat Aug 18 20:26:22 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMYax-0000bb-Fj; Sat, 18 Aug 2007 20:24:43 -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>
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: 
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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?
>
>


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



From ipv6-bounces@ietf.org Sat Aug 18 21:12:21 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMZJ5-0001Cm-Ov; Sat, 18 Aug 2007 21:10:19 -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
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: 
Subject: RE: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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
--------------------------------------------------------------------

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



From ipv6-bounces@ietf.org Sun Aug 19 08:19:17 2007
Return-path: <ipv6-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-0004pI-EH; 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>
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>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.

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



From ipv6-bounces@ietf.org Sun Aug 19 08:52:17 2007
Return-path: <ipv6-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-0004kN-Bf; 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: Rethinking autoconfig,
	was Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.

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



From ipv6-bounces@ietf.org Sun Aug 19 11:51:53 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IMn1x-0002HS-0b; Sun, 19 Aug 2007 11:49:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IMn1v-0002HC-E8
	for ipv6@ietf.org; Sun, 19 Aug 2007 11:49:31 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IMn1u-0007IJ-Sd
	for ipv6@ietf.org; Sun, 19 Aug 2007 11:49:31 -0400
Received: from mymb.local (s213147.ppp.asahi-net.or.jp [220.157.213.147])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 095957301F;
	Mon, 20 Aug 2007 00:49:29 +0900 (JST)
Date: Mon, 20 Aug 2007 00:48:59 +0900
Message-ID: <m27inr7ces.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: bob.hinden@nokia.com
In-Reply-To: <C5DC5429-9961-426A-A3DF-EE2341423AD4@nokia.com>
References: <C5DC5429-9961-426A-A3DF-EE2341423AD4@nokia.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: 9182cfff02fae4f1b6e9349e01d62f32
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: IPv6 WG Last Call: <draft-ietf-ipv6-deprecate-rh0-01.txt>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

At Thu, 28 Jun 2007 13:20:22 -0700,
ext Bob Hinden <bob.hinden@nokia.com> wrote:

> 	Title		: Deprecation of Type 0 Routing Headers in IPv6
> 	Author(s)	: J. Abley, et al.
> 	Filename	: draft-ietf-ipv6-deprecate-rh0-01.txt
> 	Pages		: 9
> 	Date		: 2007-6-28
> 	
> to Proposed Standard.  Please send substantive comments to the IPv6  
> mailing list. Editorial comments can be sent to the authors.
> 
> This last call will end on July 12, 2007.

Just out of curiosity, what's the current status (and planned next
step) of this last call?  It seems those who have already agreed with
the decision of deprecating RH0 generally support this draft while
some others raised an objection to the fundamental decision.  Are we
falling back to that level of discussion? (This is not a rhetorical
question; I'm just asking).

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



From ipv6-bounces@ietf.org Mon Aug 20 06:57:00 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IN4uH-0007hW-GT; Mon, 20 Aug 2007 06:54:49 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IN4uG-0007hO-JS
	for ipv6@ietf.org; Mon, 20 Aug 2007 06:54:48 -0400
Received: from owl.ecs.soton.ac.uk ([152.78.68.129])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IN4uF-0003bi-UY
	for ipv6@ietf.org; Mon, 20 Aug 2007 06:54:48 -0400
X-ECS-MailScanner-Watermark: 1188212080.76361@CgMxxk3Tlbnj07kq1cwrnA
Received: from goose.ecs.soton.ac.uk (goose.ecs.soton.ac.uk [152.78.68.131])
	by owl.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id l7KAsebw013076
	for <ipv6@ietf.org>; Mon, 20 Aug 2007 11:54:40 +0100
X-ECS-MailScanner-Watermark: 1188212054.64722@itcyZY/1BmYfF3N0C2iTwA
Received: from login.ecs.soton.ac.uk (login.ecs.soton.ac.uk [152.78.68.189])
	by goose.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id l7KAsEgb029289
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <ipv6@ietf.org>; Mon, 20 Aug 2007 11:54:14 +0100
Received: from login.ecs.soton.ac.uk (localhost.localdomain [127.0.0.1])
	by login.ecs.soton.ac.uk (8.13.8/8.11.6) with ESMTP id l7KAsTYO010133
	for <ipv6@ietf.org>; Mon, 20 Aug 2007 11:54:29 +0100
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.13.8/8.13.8/Submit) id l7KAsTKf010132
	for ipv6@ietf.org; Mon, 20 Aug 2007 11:54:29 +0100
Date: Mon, 20 Aug 2007 11:54:29 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: IPv6 WG <ipv6@ietf.org>
Message-ID: <20070820105429.GB9879@login.ecs.soton.ac.uk>
Mail-Followup-To: IPv6 WG <ipv6@ietf.org>
References: <46C4288A.1060408@innovationslab.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46C4288A.1060408@innovationslab.net>
User-Agent: Mutt/1.4.2.2i
X-ECS-MailScanner: Found to be clean, Found to be clean
X-Spam-Status: No
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Subject: Re: Revised 6MAN Charter
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

This looks OK to me.

One warm ipv6 wg topic at present that may (or may not) need adding is 
the resurgence of the issues discussed in Thomas Narten's 3177bis draft
(http://tools.ietf.org/html/draft-narten-ipv6-3177bis-48boundary-02)
which I think has expired?

Or is this being left solely as an RIR issue?

Also, could the cahirs confirm the final status of the existing eight WG
drafts as listed at:
http://www.ietf.org/html.charters/ipv6-charter.html

Four of these aren't mentioned in the revised charter; are they
expected to complete before 6MAN forms?

Tim

On Thu, Aug 16, 2007 at 06:35:54AM -0400, Brian Haberman wrote:
> All,
>      I have revised the charter for the proposed IPv6 maintenance WG
> based on comments received.  Please review.
> 
> Regards,
> Brian
> 

> IPv6 Maintenance Working Group (6man)
> ------------------------------------------------------------------------
> 
> Chair(s):
> 
>      Robert Hinden <bob.hinden@nokia.com>
>      Brian Haberman <brian@innovationslab.net>
> 
> 
> Internet Area Director(s):
> 
>      Jari Arkko <jari.arkko@piuha.net>
>      Mark Townsley <townsley@cisco.com>
> 
> 
> Internet Area Advisor:
> 
>      Jari Arkko <jari.arkko@piuha.net>
> 
> 
> Mailing Lists: ipv6@ietf.org
> 
> 
> Description of Working Group:
> 
> The 6man working group is responsible for the maintenance, upkeep, and advancement
> of the IPv6 protocol specifications and addressing architecture.  It is not chartered to
> develop major changes or additions to the IPv6 specifications.
> The working group will address protocol limitations/issues discovered during
> deployment and operation.  It will also serve as a venue for discussing the proper location
> for working on IPv6-related issues within the IETF.
> 
> The working group's work items are as follows:
> 
>      o Shepherd completion of standardization of RA Flags Option
>      o Shepherd completion of standardization of the RH0 Deprecation document
>      o Complete standardization of IPv6 over PPP Compression Negotiation as a Proposed Standard
>      o Complete work on Centrally Allocated Unique Local Addresses (ULA-C)
> 
> All new work items not listed above require the approval of the working
> group and IESG before they will be taken on by the working group.
> 
> 
> Goals and Milestones:
> 
> Oct 2007     Submit RH0 Deprecation specification to IESG as a Proposed Standard
> Jan 2008     Submit PPP Compression Negotiation specification to IESG as a Proposed Standard
> Mar 2008     Determine way forward for ULA-C specification
> 

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


-- 
Tim



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



From ipv6-bounces@ietf.org Mon Aug 20 08:28:56 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IN6LS-0000ua-8L; Mon, 20 Aug 2007 08:26:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IN6LQ-0000sH-Be
	for ipv6@ietf.org; Mon, 20 Aug 2007 08:26:56 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IN6LO-000259-TB
	for ipv6@ietf.org; Mon, 20 Aug 2007 08:26:56 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 885CF1986B7
	for <ipv6@ietf.org>; Mon, 20 Aug 2007 15:26:53 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 4FAE91985FA
	for <ipv6@ietf.org>; Mon, 20 Aug 2007 15:26:53 +0300 (EEST)
Message-ID: <46C9888E.5050705@piuha.net>
Date: Mon, 20 Aug 2007 15:26:54 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: IPv6 WG <ipv6@ietf.org>
References: <46C4288A.1060408@innovationslab.net>
	<20070820105429.GB9879@login.ecs.soton.ac.uk>
In-Reply-To: <20070820105429.GB9879@login.ecs.soton.ac.uk>
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: de4f315c9369b71d7dd5909b42224370
Subject: Re: Revised 6MAN Charter
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


> Also, could the cahirs confirm the final status of the existing eight WG
> drafts as listed at:
> http://www.ietf.org/html.charters/ipv6-charter.html
>
> Four of these aren't mentioned in the revised charter; are they
> expected to complete before 6MAN forms?
>   

http://tools.ietf.org/wg/ipv6/ gives the status of the various items.
Basically, anything that is RFC Editor's queue need not be
listed any more. Some rechartering efforts have ignored
documents in IESG Processing stage too, because it can be
assumed that the documents get approved before the charter.

Jari


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



From ipv6-bounces@ietf.org Mon Aug 20 09:10:13 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IN6zI-0002wp-FM; Mon, 20 Aug 2007 09:08:08 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IN6zG-0002vA-St
	for ipv6@ietf.org; Mon, 20 Aug 2007 09:08:06 -0400
Received: from owl.ecs.soton.ac.uk ([152.78.68.129])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IN6zG-00072d-C7
	for ipv6@ietf.org; Mon, 20 Aug 2007 09:08:06 -0400
X-ECS-MailScanner-Watermark: 1188220081.20108@CkEgZf7aJR73qoFeCw7bvg
Received: from goose.ecs.soton.ac.uk (goose.ecs.soton.ac.uk [152.78.68.131])
	by owl.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id l7KD7xEd017436
	for <ipv6@ietf.org>; Mon, 20 Aug 2007 14:08:00 +0100
X-ECS-MailScanner-Watermark: 1188220057.24107@lFqOcFdz+UlmLNES6ajILw
Received: from login.ecs.soton.ac.uk (login.ecs.soton.ac.uk [152.78.68.189])
	by goose.ecs.soton.ac.uk (8.13.1/8.13.1) with ESMTP id l7KD7YGA017249
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <ipv6@ietf.org>; Mon, 20 Aug 2007 14:07:36 +0100
Received: from login.ecs.soton.ac.uk (localhost.localdomain [127.0.0.1])
	by login.ecs.soton.ac.uk (8.13.8/8.11.6) with ESMTP id l7KD7oXj012982
	for <ipv6@ietf.org>; Mon, 20 Aug 2007 14:07:50 +0100
Received: (from tjc@localhost)
	by login.ecs.soton.ac.uk (8.13.8/8.13.8/Submit) id l7KD7mEm012981
	for ipv6@ietf.org; Mon, 20 Aug 2007 14:07:48 +0100
Date: Mon, 20 Aug 2007 14:07:48 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
To: IPv6 WG <ipv6@ietf.org>
Message-ID: <20070820130748.GH9879@login.ecs.soton.ac.uk>
Mail-Followup-To: IPv6 WG <ipv6@ietf.org>
References: <46C4288A.1060408@innovationslab.net>
	<20070820105429.GB9879@login.ecs.soton.ac.uk>
	<46C9888E.5050705@piuha.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46C9888E.5050705@piuha.net>
User-Agent: Mutt/1.4.2.2i
X-ECS-MailScanner: Found to be clean, Found to be clean
X-Spam-Status: No
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Subject: Re: Revised 6MAN Charter
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Mon, Aug 20, 2007 at 03:26:54PM +0300, Jari Arkko wrote:
> 
> > Also, could the cahirs confirm the final status of the existing eight WG
> > drafts as listed at:
> > http://www.ietf.org/html.charters/ipv6-charter.html
> >
> > Four of these aren't mentioned in the revised charter; are they
> > expected to complete before 6MAN forms?
> >   
> 
> http://tools.ietf.org/wg/ipv6/ gives the status of the various items.
> Basically, anything that is RFC Editor's queue need not be
> listed any more. Some rechartering efforts have ignored
> documents in IESG Processing stage too, because it can be
> assumed that the documents get approved before the charter.

Thanks Jari, in which case all looks well... the RFC Editor Queue drafts
were not mentioned, but as you say these should be approved before 6MAN
becomes active.

RFC-Editor's Queue:
draft-ietf-ipv6-2461bis-11
draft-ietf-ipv6-over-ppp-v2-03
draft-ietf-ipv6-privacy-addrs-v2-05
draft-ietf-ipv6-rfc2462bis-08

-- 
Tim

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



From ipv6-bounces@ietf.org Mon Aug 20 09:23:15 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IN7CD-0008Ha-Sh; Mon, 20 Aug 2007 09:21:29 -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: Re: Rethinking autoconfig,
	was Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Mon Aug 20 14:08:36 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INBdx-0001yD-8C; Mon, 20 Aug 2007 14:06:25 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INB3q-0006LC-SZ
	for ipv6@ietf.org; Mon, 20 Aug 2007 13:29:06 -0400
Received: from pilot.jhuapl.edu ([128.244.198.200] helo=jhuapl.edu)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1INB3q-0006bC-Ip
	for ipv6@ietf.org; Mon, 20 Aug 2007 13:29:06 -0400
Received: from ([128.244.206.192])
	by pilot.jhuapl.edu with ESMTP  id 5502123.42679463;
	Mon, 20 Aug 2007 13:28:48 -0400
Message-ID: <46C9CF53.6010803@innovationslab.net>
Date: Mon, 20 Aug 2007 13:28:51 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: IPv6 WG <ipv6@ietf.org>
References: <46C4288A.1060408@innovationslab.net>	<20070820105429.GB9879@login.ecs.soton.ac.uk>	<46C9888E.5050705@piuha.net>
	<20070820130748.GH9879@login.ecs.soton.ac.uk>
In-Reply-To: <20070820130748.GH9879@login.ecs.soton.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
X-Mailman-Approved-At: Mon, 20 Aug 2007 14:06:24 -0400
Subject: Re: Revised 6MAN Charter
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org



Tim Chown wrote:
> On Mon, Aug 20, 2007 at 03:26:54PM +0300, Jari Arkko wrote:
>>> Also, could the cahirs confirm the final status of the existing eight WG
>>> drafts as listed at:
>>> http://www.ietf.org/html.charters/ipv6-charter.html
>>>
>>> Four of these aren't mentioned in the revised charter; are they
>>> expected to complete before 6MAN forms?
>>>   
>> http://tools.ietf.org/wg/ipv6/ gives the status of the various items.
>> Basically, anything that is RFC Editor's queue need not be
>> listed any more. Some rechartering efforts have ignored
>> documents in IESG Processing stage too, because it can be
>> assumed that the documents get approved before the charter.
> 
> Thanks Jari, in which case all looks well... the RFC Editor Queue drafts
> were not mentioned, but as you say these should be approved before 6MAN
> becomes active.
> 
> RFC-Editor's Queue:
> draft-ietf-ipv6-2461bis-11
> draft-ietf-ipv6-over-ppp-v2-03
> draft-ietf-ipv6-privacy-addrs-v2-05
> draft-ietf-ipv6-rfc2462bis-08
> 

Tim,
      Yes, I intentionally left documents in the RFC Editor's Queue out 
of the 6MAN charter.

Regards,
Brian

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



From ipv6-bounces@ietf.org Mon Aug 20 14:15:51 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INBlM-0006Cn-MK; Mon, 20 Aug 2007 14:14:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INBlL-0006Cg-A5
	for ipv6@ietf.org; Mon, 20 Aug 2007 14:14:03 -0400
Received: from imr2.ericy.com ([198.24.6.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INBlJ-0004om-W8
	for ipv6@ietf.org; Mon, 20 Aug 2007 14:14:03 -0400
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se
	[138.85.77.51])
	by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id l7KIIH2F022092;
	Mon, 20 Aug 2007 13:18:17 -0500
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.50]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Aug 2007 13:13:55 -0500
Received: from [142.133.10.140] ([142.133.10.140]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Aug 2007 13:13:55 -0500
Message-ID: <46C9DA21.7060707@ericsson.com>
Date: Mon, 20 Aug 2007 14:14:57 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 1.5 (X11/20060313)
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>
References: <46C4C2A7.3080503@innovationslab.net>
In-Reply-To: <46C4C2A7.3080503@innovationslab.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Aug 2007 18:13:55.0466 (UTC)
	FILETIME=[DEE58EA0:01C7E355]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: Revised 6MAN Charter
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Brian,
   I would like the WG charter to be a bit more wider.e.g. Allow other 
updates to the base specs, if needed. One such item that I would like to 
be considered is the usefulness of hop by hop options.

http://tools.ietf.org/id/draft-krishnan-ipv6-hopbyhop-01.txt


Thanks
Suresh

Brian Haberman wrote:
> All,
>      I have revised the charter for the proposed IPv6 maintenance WG
> based on comments received.  Please review.
> 
> Regards,
> Brian
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> IPv6 Maintenance Working Group (6man)
> ------------------------------------------------------------------------
> 
> Chair(s):
> 
>      Robert Hinden <bob.hinden@nokia.com>
>      Brian Haberman <brian@innovationslab.net>
> 
> 
> Internet Area Director(s):
> 
>      Jari Arkko <jari.arkko@piuha.net>
>      Mark Townsley <townsley@cisco.com>
> 
> 
> Internet Area Advisor:
> 
>      Jari Arkko <jari.arkko@piuha.net>
> 
> 
> Mailing Lists: ipv6@ietf.org
> 
> 
> Description of Working Group:
> 
> The 6man working group is responsible for the maintenance, upkeep, and advancement
> of the IPv6 protocol specifications and addressing architecture.  It is not chartered to
> develop major changes or additions to the IPv6 specifications.
> The working group will address protocol limitations/issues discovered during
> deployment and operation.  It will also serve as a venue for discussing the proper location
> for working on IPv6-related issues within the IETF.
> 
> The working group's work items are as follows:
> 
>      o Shepherd completion of standardization of RA Flags Option
>      o Shepherd completion of standardization of the RH0 Deprecation document
>      o Complete standardization of IPv6 over PPP Compression Negotiation as a Proposed Standard
>      o Complete work on Centrally Allocated Unique Local Addresses (ULA-C)
> 
> All new work items not listed above require the approval of the working
> group and IESG before they will be taken on by the working group.
> 
> 
> Goals and Milestones:
> 
> Oct 2007     Submit RH0 Deprecation specification to IESG as a Proposed Standard
> Jan 2008     Submit PPP Compression Negotiation specification to IESG as a Proposed Standard
> Mar 2008     Determine way forward for ULA-C specification
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


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



From ipv6-bounces@ietf.org Mon Aug 20 16:07:07 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INDTn-0005nM-9N; Mon, 20 Aug 2007 16:04:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INDTl-0005nG-IE
	for ipv6@ietf.org; Mon, 20 Aug 2007 16:04:01 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INDTk-00088u-4o
	for ipv6@ietf.org; Mon, 20 Aug 2007 16:04:01 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l7KK3sRE007441; Mon, 20 Aug 2007 23:03:55 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Aug 2007 23:03:54 +0300
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by
	esebh103.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 20 Aug 2007 23:03:54 +0300
Received: from [172.19.74.173] (dadhcp-172019074173.americas.nokia.com
	[172.19.74.173])
	by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l7KK3pxd017716; Mon, 20 Aug 2007 23:03:52 +0300
In-Reply-To: <46C9DA21.7060707@ericsson.com>
References: <46C4C2A7.3080503@innovationslab.net>
	<46C9DA21.7060707@ericsson.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <84F99794-8DDE-42DB-8B7C-41BE3E204563@nokia.com>
Content-Transfer-Encoding: 7bit
From: Bob Hinden <bob.hinden@nokia.com>
Date: Mon, 20 Aug 2007 13:03:50 -0700
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 20 Aug 2007 20:03:54.0087 (UTC)
	FILETIME=[3BFB3770:01C7E365]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: Brian Haberman <brian@innovationslab.net>, IPv6 WG <ipv6@ietf.org>
Subject: Re: Revised 6MAN Charter
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bob.hinden@nokia.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Suresh,

On Aug 20, 2007, at 11:14 AM, ext Suresh Krishnan wrote:

> Hi Brian,
>   I would like the WG charter to be a bit more wider.e.g. Allow  
> other updates to the base specs, if needed. One such item that I  
> would like to be considered is the usefulness of hop by hop options.
>
> http://tools.ietf.org/id/draft-krishnan-ipv6-hopbyhop-01.txt

Why do you think this wouldn't be in the scope of the current charter  
text?  Other than needing AD approval, of course.

Bob


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



From ipv6-bounces@ietf.org Mon Aug 20 16:28:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INDp1-0004wH-Io; Mon, 20 Aug 2007 16:25:59 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INDR1-00043R-RU
	for ipv6@ietf.org; Mon, 20 Aug 2007 16:01:11 -0400
Received: from piper.jhuapl.edu ([128.244.26.33] helo=jhuapl.edu)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1INDR1-0002hB-AJ
	for ipv6@ietf.org; Mon, 20 Aug 2007 16:01:11 -0400
Received: from ([128.244.206.192])
	by piper.jhuapl.edu with ESMTP  id 5502121.39198523;
	Mon, 20 Aug 2007 16:00:44 -0400
Message-ID: <46C9F2EF.3090303@innovationslab.net>
Date: Mon, 20 Aug 2007 16:00:47 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
References: <46C4C2A7.3080503@innovationslab.net>
	<46C9DA21.7060707@ericsson.com>
In-Reply-To: <46C9DA21.7060707@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
X-Mailman-Approved-At: Mon, 20 Aug 2007 16:25:57 -0400
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: Revised 6MAN Charter
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Suresh,
      I believe the wording allows us to add work items that the WG 
wishes to adopt.  So, if/when this working group is formed, you can 
formally request the WG to consider adoption of that work item.

      Or are you arguing for including that work item in the initial 
charter?

Regards,
Brian


Suresh Krishnan wrote:
> Hi Brian,
>   I would like the WG charter to be a bit more wider.e.g. Allow other 
> updates to the base specs, if needed. One such item that I would like to 
> be considered is the usefulness of hop by hop options.
> 
> http://tools.ietf.org/id/draft-krishnan-ipv6-hopbyhop-01.txt
> 
> 
> Thanks
> Suresh
> 
> Brian Haberman wrote:
>> All,
>>      I have revised the charter for the proposed IPv6 maintenance WG
>> based on comments received.  Please review.
>>
>> Regards,
>> Brian
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> IPv6 Maintenance Working Group (6man)
>> ------------------------------------------------------------------------
>>
>> Chair(s):
>>
>>      Robert Hinden <bob.hinden@nokia.com>
>>      Brian Haberman <brian@innovationslab.net>
>>
>>
>> Internet Area Director(s):
>>
>>      Jari Arkko <jari.arkko@piuha.net>
>>      Mark Townsley <townsley@cisco.com>
>>
>>
>> Internet Area Advisor:
>>
>>      Jari Arkko <jari.arkko@piuha.net>
>>
>>
>> Mailing Lists: ipv6@ietf.org
>>
>>
>> Description of Working Group:
>>
>> The 6man working group is responsible for the maintenance, upkeep, and 
>> advancement
>> of the IPv6 protocol specifications and addressing architecture.  It 
>> is not chartered to
>> develop major changes or additions to the IPv6 specifications.
>> The working group will address protocol limitations/issues discovered 
>> during
>> deployment and operation.  It will also serve as a venue for 
>> discussing the proper location
>> for working on IPv6-related issues within the IETF.
>>
>> The working group's work items are as follows:
>>
>>      o Shepherd completion of standardization of RA Flags Option
>>      o Shepherd completion of standardization of the RH0 Deprecation 
>> document
>>      o Complete standardization of IPv6 over PPP Compression 
>> Negotiation as a Proposed Standard
>>      o Complete work on Centrally Allocated Unique Local Addresses 
>> (ULA-C)
>>
>> All new work items not listed above require the approval of the working
>> group and IESG before they will be taken on by the working group.
>>
>>
>> Goals and Milestones:
>>
>> Oct 2007     Submit RH0 Deprecation specification to IESG as a 
>> Proposed Standard
>> Jan 2008     Submit PPP Compression Negotiation specification to IESG 
>> as a Proposed Standard
>> Mar 2008     Determine way forward for ULA-C specification
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

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



From ipv6-bounces@ietf.org Mon Aug 20 16:37:30 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INDxZ-0004ht-LR; Mon, 20 Aug 2007 16:34:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INDxY-0004hb-A6
	for ipv6@ietf.org; Mon, 20 Aug 2007 16:34:48 -0400
Received: from smtp.nokia.com ([131.228.20.173] helo=mgw-ext14.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INDxW-0000Jz-Te
	for ipv6@ietf.org; Mon, 20 Aug 2007 16:34:48 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext14.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l7KKYhMa031545; Mon, 20 Aug 2007 23:34:45 +0300
Received: from daebh101.NOE.Nokia.com ([10.241.35.111]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Aug 2007 23:34:44 +0300
Received: from daebe101.NOE.Nokia.com ([10.241.35.113]) by
	daebh101.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Aug 2007 15:34:43 -0500
Received: from 172.19.244.162 ([172.19.244.162]) by daebe101.NOE.Nokia.com
	([10.241.35.113]) with Microsoft Exchange Server HTTP-DAV ; 
	Mon, 20 Aug 2007 20:34:42 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Mon, 20 Aug 2007 15:34:51 -0500
From: Basavaraj Patil <basavaraj.patil@nsn.com>
To: ext Brian Haberman <brian@innovationslab.net>, IPv6 WG <ipv6@ietf.org>
Message-ID: <C2EF651B.40D09%basavaraj.patil@nsn.com>
Thread-Topic: Revised 6MAN Charter
Thread-Index: AcfjaY7JzWgRKk9cEdySLAARJNUNiA==
In-Reply-To: <46C4288A.1060408@innovationslab.net>
Mime-version: 1.0
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 20 Aug 2007 20:34:43.0145 (UTC)
	FILETIME=[8A1B1390:01C7E369]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: 
Subject: Re: Revised 6MAN Charter
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


Hi Brian,

One of the tasks that the 6MAN WG is chartered for is : " Shepherd
completion of standardization of RA Flags Option"

Will this WG also standardize any new flags or options for the RA that are
currently being discussed?
The question arises from the work on specifying a flag/option in the RA for
indicating Proxy MIP6 (PMIP6) support or capability in the network (I-D:
draft-damic-netlmm-pmip6-ind-discover-01)

-Raj



On 8/16/07 5:35 AM, "ext Brian Haberman" <brian@innovationslab.net> wrote:

> All,
>      I have revised the charter for the proposed IPv6 maintenance WG
> based on comments received.  Please review.
> 
> Regards,
> Brian
> 
> IPv6 Maintenance Working Group (6man)
> ------------------------------------------------------------------------
> 
> Chair(s):
> 
>      Robert Hinden <bob.hinden@nokia.com>
>      Brian Haberman <brian@innovationslab.net>
> 
> 
> Internet Area Director(s):
> 
>      Jari Arkko <jari.arkko@piuha.net>
>      Mark Townsley <townsley@cisco.com>
> 
> 
> Internet Area Advisor:
> 
>      Jari Arkko <jari.arkko@piuha.net>
> 
> 
> Mailing Lists: ipv6@ietf.org
> 
> 
> Description of Working Group:
> 
> The 6man working group is responsible for the maintenance, upkeep, and
> advancement
> of the IPv6 protocol specifications and addressing architecture.  It is not
> chartered to
> develop major changes or additions to the IPv6 specifications.
> The working group will address protocol limitations/issues discovered during
> deployment and operation.  It will also serve as a venue for discussing the
> proper location
> for working on IPv6-related issues within the IETF.
> 
> The working group's work items are as follows:
> 
>      o Shepherd completion of standardization of RA Flags Option
>      o Shepherd completion of standardization of the RH0 Deprecation document
>      o Complete standardization of IPv6 over PPP Compression Negotiation as a
> Proposed Standard
>      o Complete work on Centrally Allocated Unique Local Addresses (ULA-C)
> 
> All new work items not listed above require the approval of the working
> group and IESG before they will be taken on by the working group.
> 
> 
> Goals and Milestones:
> 
> Oct 2007     Submit RH0 Deprecation specification to IESG as a Proposed
> Standard
> Jan 2008     Submit PPP Compression Negotiation specification to IESG as a
> Proposed Standard
> Mar 2008     Determine way forward for ULA-C specification
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


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



From ipv6-bounces@ietf.org Mon Aug 20 16:46:15 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INE5z-0002JN-O3; Mon, 20 Aug 2007 16:43:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INE5x-0002GC-KH
	for ipv6@ietf.org; Mon, 20 Aug 2007 16:43:29 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INE5v-0000Y4-US
	for ipv6@ietf.org; Mon, 20 Aug 2007 16:43:29 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l7KKhEvL018768; Mon, 20 Aug 2007 23:43:26 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Aug 2007 23:43:23 +0300
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by
	esebh103.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 20 Aug 2007 23:43:23 +0300
Received: from [172.19.74.173] (dadhcp-172019074173.americas.nokia.com
	[172.19.74.173])
	by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l7KKhKSt016982; Mon, 20 Aug 2007 23:43:21 +0300
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
Content-Transfer-Encoding: 7bit
From: Bob Hinden <bob.hinden@nokia.com>
Date: Mon, 20 Aug 2007 13:43:19 -0700
To: IPv6 WG <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 20 Aug 2007 20:43:23.0088 (UTC)
	FILETIME=[C0041500:01C7E36A]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Subject: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bob.hinden@nokia.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi,

After the reviewing the comments received during the working group  
last call on <draft-ietf-ipv6-deprecate-rh0-01.txt> and discussing it  
with our AD, the IPv6 w.g. chairs think it would be valuable to ask  
the question again.  We want to make sure there continues to be a  
consensus for deprecating RH0 as specified in the current draft as  
opposed to restricting it's usage as was suggest in several of the  
last call comments.

We would like to get your comments on the following two choices:

1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate-rh0-01.txt>.

2) Revising the draft to restrict the usage of RH0.  This would  
continue to require RH0 to be implemented but would restrict the  
functionality of RH0.  For example, require nodes to have support for  
RH0 turned off by default, limit the number of RH0 headers in a  
packet to one, limit the number of addresses in the RH0 to a smaller  
number (e.g., 6), and and a requirement that addresses can only be in  
the header once.

Please send your answer this question (including why) to the list or  
to the chairs directly.  We will review the responses and report the  
results to the w.g. early next week.  We are not trying to start a  
debate, but want to get a new measure of the consensus.

We note that if there continues to be a consensus for 1), then we  
will forward the draft to the ADs for proposed standard.

Thanks,
Bob Hinden & Brian Haberman
IPv6 w.g. Chairs


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



From ipv6-bounces@ietf.org Mon Aug 20 16:50:11 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INE9t-0005DA-PA; Mon, 20 Aug 2007 16:47:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INE9s-0005D3-Vr
	for ipv6@ietf.org; Mon, 20 Aug 2007 16:47:32 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INE9r-0000bv-JW
	for ipv6@ietf.org; Mon, 20 Aug 2007 16:47:32 -0400
Received: from esebh107.NOE.Nokia.com (esebh107.ntc.nokia.com [172.21.143.143])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l7KKlSHc022717; Mon, 20 Aug 2007 23:47:29 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh107.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Aug 2007 23:47:25 +0300
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by
	esebh103.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 20 Aug 2007 23:47:24 +0300
Received: from [172.19.74.173] (dadhcp-172019074173.americas.nokia.com
	[172.19.74.173])
	by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l7KKlI4S020869; Mon, 20 Aug 2007 23:47:19 +0300
In-Reply-To: <m27inr7ces.wl%jinmei@isl.rdc.toshiba.co.jp>
References: <C5DC5429-9961-426A-A3DF-EE2341423AD4@nokia.com>
	<m27inr7ces.wl%jinmei@isl.rdc.toshiba.co.jp>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <27B7E550-036F-4328-B01C-1B484033ADCB@nokia.com>
Content-Transfer-Encoding: 7bit
From: Bob Hinden <bob.hinden@nokia.com>
Date: Mon, 20 Aug 2007 13:47:17 -0700
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: 20 Aug 2007 20:47:24.0210 (UTC)
	FILETIME=[4FBC6120:01C7E36B]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: IPv6 WG Last Call: <draft-ietf-ipv6-deprecate-rh0-01.txt>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bob.hinden@nokia.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Jinmei,

>> to Proposed Standard.  Please send substantive comments to the IPv6
>> mailing list. Editorial comments can be sent to the authors.
>>
>> This last call will end on July 12, 2007.
>
> Just out of curiosity, what's the current status (and planned next
> step) of this last call?  It seems those who have already agreed with
> the decision of deprecating RH0 generally support this draft while
> some others raised an objection to the fundamental decision.  Are we
> falling back to that level of discussion? (This is not a rhetorical
> question; I'm just asking).


Thanks for asking!

The chairs after the reviewing the comments received during the  
working group last call and discussing it with our AD, think it would  
be valuable to ask the question again.  We just sent an email to the  
list asking the question.  Please respond to that thread.

Thanks,
Bob


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



From ipv6-bounces@ietf.org Mon Aug 20 16:53:55 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INEDU-00072g-5W; Mon, 20 Aug 2007 16:51:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INEDS-00072R-Cc
	for ipv6@ietf.org; Mon, 20 Aug 2007 16:51:14 -0400
Received: from vgateway.libertyrms.info ([207.219.45.62]
	helo=mail.libertyrms.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1INEDR-0000gN-6m
	for ipv6@ietf.org; Mon, 20 Aug 2007 16:51:14 -0400
Received: from dba3.int.libertyrms.com ([10.1.3.12]
	helo=dba3.int.libertyrms.info)
	by mail.libertyrms.com with esmtp (Exim 4.22) id 1INEDQ-0002WO-Tb
	for ipv6@ietf.org; Mon, 20 Aug 2007 16:51:12 -0400
Received: by dba3.int.libertyrms.info (ca.afilias.info, from userid 1019)
	id 6CD6A13744; Mon, 20 Aug 2007 16:51:22 -0400 (EDT)
Date: Mon, 20 Aug 2007 16:51:22 -0400
From: Andrew Sullivan <andrew@ca.afilias.info>
To: ipv6@ietf.org
Message-ID: <20070820205120.GA3315@dba3>
References: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
User-Agent: Mutt/1.5.9i
X-SA-Exim-Mail-From: andrew@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Andrew Sullivan <andrew@ca.afilias.info>
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Dear colleagues,

On Mon, Aug 20, 2007 at 01:43:19PM -0700, Bob Hinden wrote:
> 1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate-rh0-01.txt>.

I support this option, because it seems to me that the existing draft
makes the correct point: another rh[n] could be introduced to add the
desired features without exposing the same vulnerability.  Given that
the deployment so far is not extensive (compared to other things on
the Internet), it seems like this is the safest thing to do.  I have
read the alternative arguments; some of them seem to me to be
reasonably good second choices, and if we had evidence of much wider
use of RH0 today, I would probably be more persuaded by those
arguments.

Best regards,

Andrew

----
Andrew Sullivan                         204-4141 Yonge Street
Afilias Canada                        Toronto, Ontario Canada
<andrew@ca.afilias.info>                              M2P 2A8
                                        +1 416 646 3304 x4110


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



From ipv6-bounces@ietf.org Mon Aug 20 17:13:18 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INEW0-0003MA-1m; Mon, 20 Aug 2007 17:10:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INEVy-0003J5-RU
	for ipv6@ietf.org; Mon, 20 Aug 2007 17:10:22 -0400
Received: from imr2.ericy.com ([198.24.6.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INEVx-0000yb-JC
	for ipv6@ietf.org; Mon, 20 Aug 2007 17:10:22 -0400
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se
	[138.85.77.51])
	by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id l7KLEgHX024702;
	Mon, 20 Aug 2007 16:14:42 -0500
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.50]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Aug 2007 16:10:20 -0500
Received: from [142.133.10.140] ([142.133.10.140]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Aug 2007 16:10:20 -0500
Message-ID: <46CA037A.70005@ericsson.com>
Date: Mon, 20 Aug 2007 17:11:22 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 1.5 (X11/20060313)
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>
References: <46C4C2A7.3080503@innovationslab.net>
	<46C9DA21.7060707@ericsson.com>
	<46C9F2EF.3090303@innovationslab.net>
In-Reply-To: <46C9F2EF.3090303@innovationslab.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Aug 2007 21:10:20.0627 (UTC)
	FILETIME=[8424F230:01C7E36E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: Revised 6MAN Charter
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Brian,

Brian Haberman wrote:
> Hi Suresh,
>      I believe the wording allows us to add work items that the WG 
> wishes to adopt.  So, if/when this working group is formed, you can 
> formally request the WG to consider adoption of that work item.

Sounds good.

> 
>      Or are you arguing for including that work item in the initial 
> charter?

No. I think the the initial work items are fine as they are. I just 
believe it must be easy to work on other maintenance updates to the base 
specs (i.e. no recharter). If this is the case, I am fine with the 
current charter.

Thanks
Suresh


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



From ipv6-bounces@ietf.org Mon Aug 20 18:18:15 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INFXm-0001yM-St; Mon, 20 Aug 2007 18:16:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INFXl-0001si-FD
	for ipv6@ietf.org; Mon, 20 Aug 2007 18:16:17 -0400
Received: from imr1.ericy.com ([198.24.6.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INFXk-0002DW-5o
	for ipv6@ietf.org; Mon, 20 Aug 2007 18:16:17 -0400
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se
	[138.85.77.51])
	by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id l7KMM52i025496;
	Mon, 20 Aug 2007 17:22:05 -0500
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.50]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Aug 2007 17:16:14 -0500
Received: from [142.133.10.140] ([142.133.10.140]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 20 Aug 2007 17:16:14 -0500
Message-ID: <46CA12ED.8060305@ericsson.com>
Date: Mon, 20 Aug 2007 18:17:17 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 1.5 (X11/20060313)
MIME-Version: 1.0
To: Basavaraj Patil <basavaraj.patil@nsn.com>
References: <C2EF651B.40D09%basavaraj.patil@nsn.com>
In-Reply-To: <C2EF651B.40D09%basavaraj.patil@nsn.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Aug 2007 22:16:14.0723 (UTC)
	FILETIME=[B8F81D30:01C7E377]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: ext Brian Haberman <brian@innovationslab.net>, IPv6 WG <ipv6@ietf.org>
Subject: Re: Revised 6MAN Charter
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Raj,

Basavaraj Patil wrote:
> Hi Brian,
> 
> One of the tasks that the 6MAN WG is chartered for is : " Shepherd
> completion of standardization of RA Flags Option"
> 
> Will this WG also standardize any new flags or options for the RA that are
> currently being discussed?
> The question arises from the work on specifying a flag/option in the RA for
> indicating Proxy MIP6 (PMIP6) support or capability in the network (I-D:
> draft-damic-netlmm-pmip6-ind-discover-01)

My gut feel it that it should not be standardized in 6man. The WG that 
is interested in the flag (in this case, netlmm) must standardize it. 
But the document needs to end up updating 2461 bis (aka 4861).

Cheers
Suresh


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



From ipv6-bounces@ietf.org Mon Aug 20 18:51:02 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ING34-0004tU-1W; Mon, 20 Aug 2007 18:48:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ING32-0004tP-Ho
	for ipv6@ietf.org; Mon, 20 Aug 2007 18:48:36 -0400
Received: from imap.countersiege.com ([2001:240:581:69::218]
	helo=smtp1.countersiege.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ING32-0004J8-4U
	for ipv6@ietf.org; Mon, 20 Aug 2007 18:48:36 -0400
Received: from anchovy.countersiege.com (localhost [IPv6:::1])
	by smtp1.countersiege.com (Postfix) with ESMTP id 561A6192E8;
	Mon, 20 Aug 2007 22:48:32 +0000 (UTC)
Received: by anchovy.countersiege.com (Postfix, from userid 2000)
	id 6774CF26C; Tue, 21 Aug 2007 07:48:30 +0900 (JST)
Date: Mon, 20 Aug 2007 22:48:29 +0000
From: Ryan McBride <mcbride@openbsd.org>
To: Bob Hinden <bob.hinden@nokia.com>
Message-ID: <20070820224829.GE20448@countersiege.com>
References: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Mon, Aug 20, 2007 at 01:43:19PM -0700, Bob Hinden wrote:
> We would like to get your comments on the following two choices:
>
> 1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate-rh0-01.txt>.

I don't agree with all the details of this draft (particularly the
language around firewall policy), but I believe deprecation to be the
correct approach. Creating a situation where RH0 is /sometimes/ OK,
without any way of knowing if the endpoints can handle it correctly,
creates serious problems for network operators who value security over
unrestricted end-to-end connectivity.

> 2) Revising the draft to restrict the usage of RH0.  This would continue to 
> require RH0 to be implemented but would restrict the functionality of RH0.  
> For example, require nodes to have support for RH0 turned off by default, 
> limit the number of RH0 headers in a packet to one, limit the number of 
> addresses in the RH0 to a smaller number (e.g., 6), and and a requirement 
> that addresses can only be in the header once.

My understanding is that besides the requirement to disable RH0 by
default these controls would be fairly difficult to implement
efficiently in hardware. Such a draft would be either be unimplemented
or ammount to mandating another DDoS mechanism on the slow path of core
routers.

-Ryan

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



From ipv6-bounces@ietf.org Mon Aug 20 18:57:31 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ING9t-0002hN-09; Mon, 20 Aug 2007 18:55:41 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ING9s-0002hG-6Z
	for ipv6@ietf.org; Mon, 20 Aug 2007 18:55:40 -0400
Received: from monster.hopcount.ca ([199.212.90.4])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ING9r-0007zx-2o
	for ipv6@ietf.org; Mon, 20 Aug 2007 18:55:40 -0400
Received: from yxu1b28.hopcount.ca ([199.212.90.28])
	by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.67 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>)
	id 1INGFD-000BAI-56; Mon, 20 Aug 2007 23:01:17 +0000
In-Reply-To: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
References: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <E416E147-7CDE-444A-8FC3-136E06A3E00B@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Mon, 20 Aug 2007 18:55:16 -0400
To: bob.hinden@nokia.com
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


On 20-Aug-2007, at 16:43, Bob Hinden wrote:

> We would like to get your comments on the following two choices:
>
> 1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate- 
> rh0-01.txt>.

I support this option since:

1. I think it is the clearest solution to the problem (as in, easiest  
to understand). I believe clarity is important here, since ambiguity  
seems like a path to "let's block all routing headers, just to be on  
the safe side".

2. It facilitates identification of "dangerous" source-routing in a  
way that is already available on several platforms (checking the RH  
type) without requiring devices to distinguish between old and new  
semantics (as would be needed in the case of a shared codepoint  
between the original and new specification).

3. Architecturally, choosing a new codepoint for functionality which  
is different, even if it is similar, seems like the right thing.

4. It is congruent with the approach several significant  
implementations have taken (e.g. Linux, *BSD, Mac OS X).

5. Nobody has come forward with an indication that functionality  
requiring RH0 in its current form is widely deployed or required. It  
seems at least plausible that we might expect to have heard of such a  
use case given the publicity surrounding the CanSecWest presentation,  
regardless of whether you choose to classify that publicity as  
"hysteria" or "journalism" :-).

6. It seems likely that some IPv6 operators have taken the precaution  
of dropping datagrams carrying RH0, and hence the zero type might be  
considered effectively poisoned for use on the public Internet. Re- 
use of type zero would hence only be of reliable use within  
controlled networks; to be of general use, a benign source routing  
option would need a new codepoint.


Joe

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



From ipv6-bounces@ietf.org Mon Aug 20 19:11:23 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INGNN-0004cQ-LG; Mon, 20 Aug 2007 19:09:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INGNM-0004cL-Ok
	for ipv6@ietf.org; Mon, 20 Aug 2007 19:09:36 -0400
Received: from pacdcimo01.cable.comcast.com ([24.40.8.145])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INGNL-0004ls-IM
	for ipv6@ietf.org; Mon, 20 Aug 2007 19:09:36 -0400
Received: from ([10.52.116.30])
	by pacdcimo01.cable.comcast.com with ESMTP  id KP-BXT38.6828721;
	Mon, 20 Aug 2007 19:09:06 -0400
Received: from PACDCEXCMB05.cable.comcast.com ([24.40.15.116]) by
	PAOAKEXCSMTP01.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 20 Aug 2007 17:51:40 -0400
Received: from 86.202.35.65 ([86.202.35.65]) by PACDCEXCMB05.cable.comcast.com
	([24.40.15.116]) via Exchange Front-End Server
	webmail.comcast.com ([24.40.8.152]) with Microsoft Exchange
	Server HTTP-DAV ; Mon, 20 Aug 2007 21:48:48 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Mon, 20 Aug 2007 17:48:47 -0400
From: Alain Durand <alain_durand@cable.comcast.com>
To: Brian Haberman <brian@innovationslab.net>,
	Jari Arkko <jari.arkko@piuha.net>
Message-ID: <C2EF847F.B2D%alain_durand@cable.comcast.com>
Thread-Topic: Revised 6MAN Charter
Thread-Index: AcfjaGQRwhm/w3ayR+66gzqj+01v0gAC37Kn
In-Reply-To: <46C9F2EF.3090303@innovationslab.net>
Mime-version: 1.0
X-OriginalArrivalTime: 20 Aug 2007 21:51:40.0421 (UTC)
	FILETIME=[4A377B50:01C7E374]
X-Spam-Score: 4.4 (++++)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: Revised 6MAN Charter
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0270953230=="
Errors-To: ipv6-bounces@ietf.org

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

--===============0270953230==
Content-type: multipart/alternative;
	boundary="B_3270476927_1082771"

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

--B_3270476927_1082771
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

> On 8/20/07 4:00 PM, "Brian Haberman" <brian@innovationslab.net> wrote:
>
>
>    I believe the wording allows us to add work items that the WG wishes t=
o
adopt.

I believe this is the wrong thing to do for any wg in general and for a
=8Cmaintenance=B9 wg in particular.
The charter is a contract between the wg and the IETF represented by the AD
about what should and what should not be delivered,
this is not an open ended list of documents that the wg may feel like
working on.


  - Alain.

--B_3270476927_1082771
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: Revised 6MAN Charter</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:12.0px'>&gt; =
On 8/20/07 4:00 PM, &quot;Brian Haberman&quot; &lt;brian@innovationslab.net&=
gt; wrote:<BR>
&gt;<BR>
&gt;<BR>
&gt; &nbsp;&nbsp;&nbsp;I believe the wording allows us to add work items th=
at the WG wishes to adopt.<BR>
<BR>
I believe this is the wrong thing to do for any wg in general and for a &#8=
216;maintenance&#8217; wg in particular.<BR>
The charter is a contract between the wg and the IETF represented by the AD=
 about what should and what should not be delivered,<BR>
this is not an open ended list of documents that the wg may feel like worki=
ng on.<BR>
<BR>
<BR>
&nbsp;&nbsp;- Alain.</SPAN></FONT>
</BODY>
</HTML>


--B_3270476927_1082771--



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

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

--===============0270953230==--





From ipv6-bounces@ietf.org Mon Aug 20 20:30:36 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INHbi-0000sE-Ei; Mon, 20 Aug 2007 20:28:30 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INHbg-0000rm-C1
	for ipv6@ietf.org; Mon, 20 Aug 2007 20:28:28 -0400
Received: from mail-out4.apple.com ([17.254.13.23])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1INHbf-0002Sq-Tv
	for ipv6@ietf.org; Mon, 20 Aug 2007 20:28:28 -0400
Received: from relay12.apple.com (relay12.apple.com [17.128.113.53])
	by mail-out4.apple.com (Postfix) with ESMTP id 5E791F626C7
	for <ipv6@ietf.org>; Mon, 20 Aug 2007 17:28:27 -0700 (PDT)
Received: from relay12.apple.com (unknown [127.0.0.1])
	by relay12.apple.com (Symantec Mail Security) with ESMTP id 492BE28AF7
	for <ipv6@ietf.org>; Mon, 20 Aug 2007 17:28:27 -0700 (PDT)
X-AuditID: 11807135-a6765bb000000813-5e-46ca31ab5bd7
Received: from [17.206.23.199] (il0602a-dhcp71.apple.com [17.206.23.199])
	by relay12.apple.com (Symantec Mail Security) with ESMTP id 3A8F5289C3
	for <ipv6@ietf.org>; Mon, 20 Aug 2007 17:28:27 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <E416E147-7CDE-444A-8FC3-136E06A3E00B@ca.afilias.info>
References: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
	<E416E147-7CDE-444A-8FC3-136E06A3E00B@ca.afilias.info>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C90A8CFD-F2BF-4A80-9CD5-9BD9BF4CA157@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Mon, 20 Aug 2007 17:28:16 -0700
To: IPv6 WG <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Aug 20, 2007, at 15:55, Joe Abley wrote:
> On 20-Aug-2007, at 16:43, Bob Hinden wrote:
>
>> We would like to get your comments on the following two choices:
>>
>> 1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate- 
>> rh0-01.txt>.
>
> I support this option since:

I do too, and I'd like to add to what Joe has written.

> 6. It seems likely that some IPv6 operators have taken the  
> precaution of dropping datagrams carrying RH0, and hence the zero  
> type might be considered effectively poisoned for use on the public  
> Internet. Re-use of type zero would hence only be of reliable use  
> within controlled networks; to be of general use, a benign source  
> routing option would need a new codepoint.

The way we responded to the RH0 issue in the latest release of  
firmware for AirPort Extreme 802.11n base station products is to not  
forward any datagrams carrying RH0 upon receiving them on any  
interface.  I'm pretty sure we send ICMP errors in response to them,  
but that could change in the future.  There is no human interface for  
changing this behavior in the IPv6 router function.  The filter is  
always on if IPv6 routing is on.

>> 2) Revising the draft to restrict the usage of RH0.  This would  
>> continue to require RH0 to be implemented but would restrict the  
>> functionality of RH0. [...]

I predict a draft that describes a less restrictive policy for  
handling RH0 datagrams will be ignored by everyone who has already  
shipped more restrictive products.


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



From ipv6-bounces@ietf.org Mon Aug 20 21:31:06 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INIYL-0006Ab-4Y; Mon, 20 Aug 2007 21:29:05 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INIYK-0006AV-Gk
	for ipv6@ietf.org; Mon, 20 Aug 2007 21:29:04 -0400
Received: from mrout1.yahoo.com ([216.145.54.171])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1INIYJ-0003rf-Vx
	for ipv6@ietf.org; Mon, 20 Aug 2007 21:29:04 -0400
Received: from minion.local.neville-neil.com (proxy8.corp.yahoo.com
	[216.145.48.13])
	by mrout1.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id l7L1S4i4045898; 
	Mon, 20 Aug 2007 18:28:05 -0700 (PDT)
Date: Tue, 21 Aug 2007 10:28:04 +0900
Message-ID: <m2d4xhr80r.wl%gnn@neville-neil.com>
From: "George V. Neville-Neil" <gnn@neville-neil.com>
To: Bob Hinden <bob.hinden@nokia.com>
In-Reply-To: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
References: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka)
	FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.7 Emacs/22.1
	(i386-apple-darwin8.9.1) 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: 798b2e660f1819ae38035ac1d8d5e3ab
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

At Mon, 20 Aug 2007 13:43:19 -0700,
Bob Hinden wrote:
> 
> Hi,
> 
> After the reviewing the comments received during the working group  
> last call on <draft-ietf-ipv6-deprecate-rh0-01.txt> and discussing it  
> with our AD, the IPv6 w.g. chairs think it would be valuable to ask  
> the question again.  We want to make sure there continues to be a  
> consensus for deprecating RH0 as specified in the current draft as  
> opposed to restricting it's usage as was suggest in several of the  
> last call comments.
> 
> We would like to get your comments on the following two choices:
> 
> 1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate-rh0-01.txt>.
> 

I support option 1.

Best,
George

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



From ipv6-bounces@ietf.org Mon Aug 20 21:38:32 2007
Return-path: <ipv6-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-0003vf-7e; 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-0003vV-QU
	for ipv6@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-00041Z-Uo
	for ipv6@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>
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, "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>
Subject: Re: [dhcwg] Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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


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



From ipv6-bounces@ietf.org Mon Aug 20 22:21:12 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INJKt-00049k-Al; Mon, 20 Aug 2007 22:19:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INJKr-00049d-Na
	for ipv6@ietf.org; Mon, 20 Aug 2007 22:19:13 -0400
Received: from nz-out-0506.google.com ([64.233.162.225])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INJKq-0001GF-3y
	for ipv6@ietf.org; Mon, 20 Aug 2007 22:19:13 -0400
Received: by nz-out-0506.google.com with SMTP id n1so551882nzf
	for <ipv6@ietf.org>; Mon, 20 Aug 2007 19:19:11 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=W5IoakmJ9H0MCVqK+EnemkLPy+ssEN7g6dN2ZsgsGJrDxGCPP62WLU3oc2fto3oFgOxRGZsaI+Oj8DeHmKld8xRzW5vdVLpAbHH7bDv963KFvjWGcwH38zyhGfNKUAaCj18Wq+ouvS3KHddrrlZfSqEinqfgWcFhK+4IOHQ9bH8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=ov2Geyj1gGSPUhC4rE2oLm/CB3lFGR5UQB5UNYSsGuVLGVlZQsQBdZ7nLMVclV+1htyI2r1Rou+zoNnPPf3QnAcKBvUatGF+dIxXqSUtW+69TCVCZ7v7ztLGe9sPJ8oRXYi1nx7eMOzFDGT7TlZldsiS2VSpCv4mfuKvxtM5HdE=
Received: by 10.142.215.5 with SMTP id n5mr677271wfg.1187662750880;
	Mon, 20 Aug 2007 19:19:10 -0700 (PDT)
Received: by 10.142.84.8 with HTTP; Mon, 20 Aug 2007 19:19:10 -0700 (PDT)
Message-ID: <77ead0ec0708201919q3506c001vb8fc88a39adac793@mail.gmail.com>
Date: Tue, 21 Aug 2007 07:49:10 +0530
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: bob.hinden@nokia.com
In-Reply-To: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: manoj@ipinfusion.com, IPv6 WG <ipv6@ietf.org>
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Bob,

> We would like to get your comments on the following two choices:
>
> 1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate-rh0-01.txt>.
I support this option.

I think having a new header i.e. RH4, should be added with the below
mentioned functionality. I have already got a draft for the same. I
will post it today.

Thanks,
Vishwas

> 2) Revising the draft to restrict the usage of RH0.  This would
> continue to require RH0 to be implemented but would restrict the
> functionality of RH0.  For example, require nodes to have support for
> RH0 turned off by default, limit the number of RH0 headers in a
> packet to one, limit the number of addresses in the RH0 to a smaller
> number (e.g., 6), and and a requirement that addresses can only be in
> the header once.
>
> Please send your answer this question (including why) to the list or
> to the chairs directly.  We will review the responses and report the
> results to the w.g. early next week.  We are not trying to start a
> debate, but want to get a new measure of the consensus.
>
> We note that if there continues to be a consensus for 1), then we
> will forward the draft to the ADs for proposed standard.
>
> Thanks,
> Bob Hinden & Brian Haberman
> IPv6 w.g. Chairs
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

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



From ipv6-bounces@ietf.org Mon Aug 20 22:28:19 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INJRl-0001Mx-1O; Mon, 20 Aug 2007 22:26:21 -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: Is a DNS NS required,
	when a DHCPv6 Client transmits a Conform message? 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Mon Aug 20 23:38:53 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INKY5-00071e-6V; Mon, 20 Aug 2007 23:36:57 -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: RE: Is a DNS NS required,
	when a DHCPv6 Client transmits a Conform message? 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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
--------------------------------------------------------------------

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



From ipv6-bounces@ietf.org Tue Aug 21 00:32:07 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INLNY-0004hl-96; Tue, 21 Aug 2007 00:30:08 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INLNW-0004hQ-HA
	for ipv6@ietf.org; Tue, 21 Aug 2007 00:30:06 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1INLNV-0007FE-Tx
	for ipv6@ietf.org; Tue, 21 Aug 2007 00:30:06 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 399A01986B7;
	Tue, 21 Aug 2007 07:30:04 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id D21001986A6;
	Tue, 21 Aug 2007 07:30:03 +0300 (EEST)
Message-ID: <46CA6A4C.1050402@piuha.net>
Date: Tue, 21 Aug 2007 07:30:04 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: Basavaraj Patil <basavaraj.patil@nsn.com>, 
	ext Brian Haberman <brian@innovationslab.net>
References: <C2EF651B.40D09%basavaraj.patil@nsn.com>
	<46CA12ED.8060305@ericsson.com>
In-Reply-To: <46CA12ED.8060305@ericsson.com>
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: 8b30eb7682a596edff707698f4a80f7d
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: Revised 6MAN Charter
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

I also believe that the PMIP capability mechanism is something
that should come out of the discussions in NETLMM. Of course,
the IPv6 experts need to be consulted.

Jari

Suresh Krishnan kirjoitti:
> Hi Raj,
>
> Basavaraj Patil wrote:
>> Hi Brian,
>>
>> One of the tasks that the 6MAN WG is chartered for is : " Shepherd
>> completion of standardization of RA Flags Option"
>>
>> Will this WG also standardize any new flags or options for the RA
>> that are
>> currently being discussed?
>> The question arises from the work on specifying a flag/option in the
>> RA for
>> indicating Proxy MIP6 (PMIP6) support or capability in the network (I-D:
>> draft-damic-netlmm-pmip6-ind-discover-01)
>
> My gut feel it that it should not be standardized in 6man. The WG that
> is interested in the flag (in this case, netlmm) must standardize it.
> But the document needs to end up updating 2461 bis (aka 4861).
>
> Cheers
> Suresh
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>


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



From ipv6-bounces@ietf.org Tue Aug 21 00:44:15 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INLZH-0007B7-P2; Tue, 21 Aug 2007 00:42:15 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INLZF-00075b-S2
	for ipv6@ietf.org; Tue, 21 Aug 2007 00:42:14 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1INLZF-0007Ui-BW
	for ipv6@ietf.org; Tue, 21 Aug 2007 00:42:13 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id A805D1986B7;
	Tue, 21 Aug 2007 07:42:12 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 43C671986A6;
	Tue, 21 Aug 2007 07:42:12 +0300 (EEST)
Message-ID: <46CA6D25.2060707@piuha.net>
Date: Tue, 21 Aug 2007 07:42:13 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: Alain Durand <alain_durand@cable.comcast.com>
References: <C2EF847F.B2D%alain_durand@cable.comcast.com>
In-Reply-To: <C2EF847F.B2D%alain_durand@cable.comcast.com>
Content-Type: text/plain; charset=windows-1252
X-Virus-Scanned: ClamAV using ClamSMTP
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: Brian Haberman <brian@innovationslab.net>, IPv6 WG <ipv6@ietf.org>
Subject: Re: Revised 6MAN Charter
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Alain,

> >
> > I believe the wording allows us to add work items that the WG wishes
> to adopt.
>
> I believe this is the wrong thing to do for any wg in general and for
> a =91maintenance=92 wg in particular.
> The charter is a contract between the wg and the IETF represented by
> the AD about what should and what should not be delivered,
> this is not an open ended list of documents that the wg may feel like
> working on.

I fully agree with your principle, but this is tricky for a maintenance
WG. We do not know what bugs we are going to find or what spec
clarifications we are going to need!

Let me be clear: 6MAN is NOT a venue for people to develop
new features or to make major changes in the way that current
features of IPv6 work. It is strictly chartered to complete
current work and then only maintenance. As the charter
says:

It is not chartered to develop major changes or additions
to the IPv6 specifications. The working group will address
protocol limitations/issues discovered during deployment
and operation.

We also have a statement in the charter that requires IESG
approval of new work items (to be changed to AD approval
based on comments we received privately). This along with
the quoted text above is just about the right balance in
my opinion; the WG knows that it cannot do everything
but we do not need to list future bugs beforehand.

Jari


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



From ipv6-bounces@ietf.org Tue Aug 21 01:05:37 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INLuA-0006Yy-Eg; Tue, 21 Aug 2007 01:03:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INLu9-0006Ys-3k
	for ipv6@ietf.org; Tue, 21 Aug 2007 01:03:49 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INLu7-0003uk-Nl
	for ipv6@ietf.org; Tue, 21 Aug 2007 01:03:49 -0400
Received: from jmb.local (unknown [IPv6:2001:200:1b1:1010:217:f2ff:fe26:34a0])
	by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id CCD527301E;
	Tue, 21 Aug 2007 14:03:45 +0900 (JST)
Date: Tue, 21 Aug 2007 14:03:38 +0900
Message-ID: <m1wsvpxyvp.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=
	<jinmei@isl.rdc.toshiba.co.jp>
To: bob.hinden@nokia.com
In-Reply-To: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
References: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.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: 50a516d93fd399dc60588708fd9a3002
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

At Mon, 20 Aug 2007 13:43:19 -0700,
Bob Hinden <bob.hinden@nokia.com> wrote:

> We would like to get your comments on the following two choices:
> 
> 1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate-rh0-01.txt>.
> 
> 2) Revising the draft to restrict the usage of RH0.  This would  

If I were to choose one I support choice #1, but I can live with
choice #2 (but in that case just turning it off by default seems
sufficient to me).  The most important point for me is to make the
consensus as quick as possible rather than sticking to a super-perfect
solution and wasting more time.  So, if there are still a
non-negligible number of people who object to the deprecation while
the vast majority *can live with* off-by-default, I think we should go
for it.

Some detailed comments:

I prefer choice #1 because it looks cleaner resolution.  Also, since
(as far as I know) not so many people are heavily relying on RH0 right
now, I believe they can generally wait for new types of RH for their
specific purposes.

But at the same time, I guess getting new RHx deployed will take
pretty long time (e.g., one-year) realistically, especially due to the
infamous time-consuming standardization process at the IETF (I'm
afraid we're not even sure where to discuss the spec - apparently 6MAN
is not the place).  So it's understandable to me for those who prefer
choice #2 to oppose to the idea of hasty deprecation.  Thus I can also
live with choice #2.

I've heard an argument that off-by-default is not sufficient, but I
personally do not necessarily agree with that.  I stated my personal
opinion on this somewhere else before:
http://mail-index.netbsd.org/tech-net/2007/05/20/0003.html
The argument that if the node is controlled by a remote attacker the
feature may be re-enabled is not convincing to me either because in
that case the attacker can do any other evil things including even
replacing the kernel implementation or running a user-space bouncer
application that has the same effect of RH0.  I'm not arguing I prefer
choice #2 by saying this, but choice #2 certainly works for me as a
compromise if that makes a quicker decision.

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



From ipv6-bounces@ietf.org Tue Aug 21 01:11:30 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INLzs-0007UM-DB; Tue, 21 Aug 2007 01:09:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INLzq-0007UG-Pa
	for ipv6@ietf.org; Tue, 21 Aug 2007 01:09:42 -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 1INLzq-000432-BU
	for ipv6@ietf.org; Tue, 21 Aug 2007 01:09:42 -0400
Received: by coconut.itojun.org (Postfix, from userid 501)
	id 4C6A4233E8; Tue, 21 Aug 2007 14:09:37 +0900 (JST)
To: jinmei@isl.rdc.toshiba.co.jp
In-Reply-To: Your message of "Tue, 21 Aug 2007 14:03:38 +0900"
	<m1wsvpxyvp.wl%jinmei@isl.rdc.toshiba.co.jp>
References: <m1wsvpxyvp.wl%jinmei@isl.rdc.toshiba.co.jp>
X-Mailer: Cue version 0.8 (070521-1856/itojun)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20070821050938.4C6A4233E8@coconut.itojun.org>
Date: Tue, 21 Aug 2007 14:09:37 +0900 (JST)
From: itojun@itojun.org (Jun-ichiro itojun Hagino)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: ipv6@ietf.org, bob.hinden@nokia.com
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> > We would like to get your comments on the following two choices:
> > 
> > 1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate-rh0-01.txt>.
> > 
> > 2) Revising the draft to restrict the usage of RH0.  This would  
> 
> If I were to choose one I support choice #1, but I can live with
> choice #2 (but in that case just turning it off by default seems
> sufficient to me).  The most important point for me is to make the

	for me, the point is to ship the document as an RFC sooner, the better.

	there are giant companies who are waiting for RFC to be published.
	they are holding their security updates until RFC gets published.

itojun

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



From ipv6-bounces@ietf.org Tue Aug 21 02:48:27 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INNVI-0003qo-NF; Tue, 21 Aug 2007 02:46:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INNVH-0003qi-QT
	for ipv6@ietf.org; Tue, 21 Aug 2007 02:46:15 -0400
Received: from postfix.iai.uni-bonn.de ([131.220.8.4])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1INNVH-0001r3-4h
	for ipv6@ietf.org; Tue, 21 Aug 2007 02:46:15 -0400
X-IAI-Env-From: <ignatios@cello.cs.uni-bonn.de> : [131.220.4.211]
Received: from theory.cs.uni-bonn.de (theory.cs.uni-bonn.de [131.220.4.211])
	by postfix.iai.uni-bonn.de (Postfix) with ESMTP id C1D975C837
	for <ipv6@ietf.org>; Tue, 21 Aug 2007 08:46:11 +0200 (MEST)
	(envelope-from ignatios@cello.cs.uni-bonn.de)
	(envelope-to ipv6@ietf.org) (1)
	(internal use: ta=0, tu=1, te=0, am=-, au=-)
Received: from cello.cs.uni-bonn.de (cello.cs.uni-bonn.de [131.220.4.178])
	by theory.cs.uni-bonn.de (8.12.9/8.12.9) with SMTP id l7L6kBVE013466
	for <ipv6@ietf.org>; Tue, 21 Aug 2007 08:46:11 +0200 (MEST)
Received: (from ignatios@cello.cs.uni-bonn.de)
	by cello.cs.uni-bonn.de (mini_sendmail/1.3.2 21nov2002 nb4 7oct2003);
	Tue, 21 Aug 2007 08:46:11 CEST (sender ignatios@cello.cs.uni-bonn.de)
Date: Tue, 21 Aug 2007 08:46:11 +0200
From: Ignatios Souvatzis <ignatios@cs.uni-bonn.de>
Cc: IPv6 WG <ipv6@ietf.org>
Message-ID: <20070821064611.GA6515@cs.uni-bonn.de>
References: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Mon, Aug 20, 2007 at 01:43:19PM -0700, Bob Hinden wrote:

> 1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate-rh0-01.txt>.

Fine with me.

	-is

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



From ipv6-bounces@ietf.org Tue Aug 21 03:30:46 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INOAf-0001CG-1f; Tue, 21 Aug 2007 03:29:01 -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>
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: Hideshi.Enokihara@jp.yokogawa.com, dhcwg@ietf.org, ipv6@ietf.org
Subject: Re: [dhcwg] RE: Is a DNS NS required,
	when a DHCPv6 Client transmits a Conform message? 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Tue Aug 21 03:54:31 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INOXR-0000IG-OB; Tue, 21 Aug 2007 03:52:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INOXQ-0000IB-5g
	for ipv6@ietf.org; Tue, 21 Aug 2007 03:52:32 -0400
Received: from tcmail23.telekom.de ([217.6.95.237])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INOXP-0007M7-J3
	for ipv6@ietf.org; Tue, 21 Aug 2007 03:52:32 -0400
Received: from S4DE9JSAANM.ost.t-com.de (S4DE9JSAANM.ost.t-com.de
	[10.125.177.122]) by tcmail21.telekom.de with ESMTP;
	Tue, 21 Aug 2007 09:52:28 +0200
Received: from S4DE9JSAAIG.ost.t-com.de ([10.125.177.192]) by
	S4DE9JSAANM.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); 
	Tue, 21 Aug 2007 09:52:28 +0200
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 21 Aug 2007 09:52:27 +0200
Message-Id: <1E4CCB2441C5C0409AD8A929482A09F3031346D8@S4DE9JSAAIG.ost.t-com.de>
In-Reply-To: <77ead0ec0708201919q3506c001vb8fc88a39adac793@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-topic: New Consensus call on RH0 Deprecation
Thread-index: AcfjmbetLkQ6ltY2TsGuisnmrHgTDQALh06w
References: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
	<77ead0ec0708201919q3506c001vb8fc88a39adac793@mail.gmail.com>
From: "Bonness, Olaf" <Olaf.Bonness@t-systems.com>
To: <bob.hinden@nokia.com>
X-OriginalArrivalTime: 21 Aug 2007 07:52:28.0263 (UTC)
	FILETIME=[3867A770:01C7E3C8]
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: ipv6@ietf.org
Subject: RE: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Hi Bob,

> We would like to get your comments on the following two choices:
>
> 1) Deprecate RH0 as specified in =
<draft-ietf-ipv6-deprecate-rh0-01.txt>.

I vote for this option. It's a clean solution and leaves as well place =
for a future (re-)definition of additional RH functionalities if needed.

My 2 cents
	Olaf

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



From ipv6-bounces@ietf.org Tue Aug 21 05:41:00 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INQBu-00040J-L6; Tue, 21 Aug 2007 05:38:26 -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: Re: Rethinking autoconfig,
	was Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.

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



From ipv6-bounces@ietf.org Tue Aug 21 05:48:46 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INQKB-00089o-Ii; Tue, 21 Aug 2007 05:46:59 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INQK9-00089c-DR
	for ipv6@ietf.org; Tue, 21 Aug 2007 05:46:57 -0400
Received: from pacdcimo02.cable.comcast.com ([24.40.8.146])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1INQK9-0007u5-3a
	for ipv6@ietf.org; Tue, 21 Aug 2007 05:46:57 -0400
Received: from ([10.195.246.152])
	by pacdcimo02.cable.comcast.com with ESMTP  id KP-GZL85.10635159;
	Tue, 21 Aug 2007 05:46:50 -0400
Received: from PACDCEXCMB05.cable.comcast.com ([24.40.15.116]) by
	NJMDCEXCRLY01.cable.comcast.com with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 21 Aug 2007 05:46:50 -0400
Received: from 86.211.251.133 ([86.211.251.133]) by
	PACDCEXCMB05.cable.comcast.com ([24.40.15.116]) via Exchange
	Front-End Server webmail.comcast.com ([24.40.8.152]) with
	Microsoft Exchange Server HTTP-DAV ; Tue, 21 Aug 2007 09:46:50 +0000
User-Agent: Microsoft-Entourage/11.2.5.060620
Date: Tue, 21 Aug 2007 05:46:47 -0400
From: Alain Durand <alain_durand@cable.comcast.com>
To: Jari Arkko <jari.arkko@piuha.net>
Message-ID: <C2F02CC7.B72%alain_durand@cable.comcast.com>
Thread-Topic: Revised 6MAN Charter
Thread-Index: AcfjrbVGw5Uia2VIS2SPOgkARIR64gAKntBW
In-Reply-To: <46CA6D25.2060707@piuha.net>
Mime-version: 1.0
X-OriginalArrivalTime: 21 Aug 2007 09:46:50.0919 (UTC)
	FILETIME=[32DDDB70:01C7E3D8]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
Cc: Brian Haberman <brian@innovationslab.net>, IPv6 WG <ipv6@ietf.org>
Subject: Re: Revised 6MAN Charter
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1805933962=="
Errors-To: ipv6-bounces@ietf.org

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

--===============1805933962==
Content-type: multipart/alternative;
	boundary="B_3270520007_1343256"

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

--B_3270520007_1343256
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

Jari,

I would agree with the balance you suggest. It is different from what was
stated by the chair.

  - Alain.


On 8/21/07 12:42 AM, "Jari Arkko" <jari.arkko@piuha.net> wrote:

> Alain,
>=20
>>> > >
>>> > > I believe the wording allows us to add work items that the WG wishe=
s
>> > to adopt.
>> >
>> > I believe this is the wrong thing to do for any wg in general and for
>> > a =8Cmaintenance=B9 wg in particular.
>> > The charter is a contract between the wg and the IETF represented by
>> > the AD about what should and what should not be delivered,
>> > this is not an open ended list of documents that the wg may feel like
>> > working on.
>=20
> I fully agree with your principle, but this is tricky for a maintenance
> WG. We do not know what bugs we are going to find or what spec
> clarifications we are going to need!
>=20
> Let me be clear: 6MAN is NOT a venue for people to develop
> new features or to make major changes in the way that current
> features of IPv6 work. It is strictly chartered to complete
> current work and then only maintenance. As the charter
> says:
>=20
> It is not chartered to develop major changes or additions
> to the IPv6 specifications. The working group will address
> protocol limitations/issues discovered during deployment
> and operation.
>=20
> We also have a statement in the charter that requires IESG
> approval of new work items (to be changed to AD approval
> based on comments we received privately). This along with
> the quoted text above is just about the right balance in
> my opinion; the WG knows that it cannot do everything
> but we do not need to list future bugs beforehand.
>=20
> Jari
>=20
>=20



--B_3270520007_1343256
Content-type: text/html;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: Revised 6MAN Charter</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:12.0px'>Jari,=
<BR>
<BR>
I would agree with the balance you suggest. It is different from what was s=
tated by the chair.<BR>
<BR>
&nbsp;&nbsp;- Alain.<BR>
<BR>
<BR>
On 8/21/07 12:42 AM, &quot;Jari Arkko&quot; &lt;jari.arkko@piuha.net&gt; wr=
ote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STYL=
E=3D'font-size:12.0px'>Alain,<BR>
<BR>
&gt; &gt;<BR>
&gt; &gt; I believe the wording allows us to add work items that the WG wis=
hes<BR>
&gt; to adopt.<BR>
&gt;<BR>
&gt; I believe this is the wrong thing to do for any wg in general and for<=
BR>
&gt; a &#8216;maintenance&#8217; wg in particular.<BR>
&gt; The charter is a contract between the wg and the IETF represented by<B=
R>
&gt; the AD about what should and what should not be delivered,<BR>
&gt; this is not an open ended list of documents that the wg may feel like<=
BR>
&gt; working on.<BR>
<BR>
I fully agree with your principle, but this is tricky for a maintenance<BR>
WG. We do not know what bugs we are going to find or what spec<BR>
clarifications we are going to need!<BR>
<BR>
Let me be clear: 6MAN is NOT a venue for people to develop<BR>
new features or to make major changes in the way that current<BR>
features of IPv6 work. It is strictly chartered to complete<BR>
current work and then only maintenance. As the charter<BR>
says:<BR>
<BR>
It is not chartered to develop major changes or additions<BR>
to the IPv6 specifications. The working group will address<BR>
protocol limitations/issues discovered during deployment<BR>
and operation.<BR>
<BR>
We also have a statement in the charter that requires IESG<BR>
approval of new work items (to be changed to AD approval<BR>
based on comments we received privately). This along with<BR>
the quoted text above is just about the right balance in<BR>
my opinion; the WG knows that it cannot do everything<BR>
but we do not need to list future bugs beforehand.<BR>
<BR>
Jari<BR>
<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE=3D"Verdana, Helvetica, Arial"><SPAN STY=
LE=3D'font-size:12.0px'><BR>
</SPAN></FONT>
</BODY>
</HTML>


--B_3270520007_1343256--



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

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

--===============1805933962==--





From ipv6-bounces@ietf.org Tue Aug 21 06:10:18 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INQew-00021X-UO; Tue, 21 Aug 2007 06:08:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INQeu-00021R-MI
	for ipv6@ietf.org; Tue, 21 Aug 2007 06:08:24 -0400
Received: from burp.tkv.asdf.org ([212.16.99.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INQes-0003ei-TA
	for ipv6@ietf.org; Tue, 21 Aug 2007 06:08:24 -0400
Received: from burp.tkv.asdf.org (msa@localhost [127.0.0.1])
	by burp.tkv.asdf.org (8.14.1/8.14.1/Debian-8) with ESMTP id
	l7LA8L0R014362 for <ipv6@ietf.org>; Tue, 21 Aug 2007 13:08:21 +0300
Received: (from msa@localhost)
	by burp.tkv.asdf.org (8.14.1/8.14.1/Submit) id l7LA8L9l014359;
	Tue, 21 Aug 2007 13:08:21 +0300
Date: Tue, 21 Aug 2007 13:08:21 +0300
Message-Id: <200708211008.l7LA8L9l014359@burp.tkv.asdf.org>
From: Markku Savela <msa@moth.iki.fi>
To: ipv6@ietf.org
In-reply-to: <BAA24DD4-8DF1-4C72-969A-37ACF82637B7@muada.com> (message from
	Iljitsch van Beijnum on Tue, 21 Aug 2007 11:38:20 +0200)
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>
	<BAA24DD4-8DF1-4C72-969A-37ACF82637B7@muada.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Subject: Re: Rethinking autoconfig,
	was Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


> From: Iljitsch van Beijnum <iljitsch@muada.com>

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

I wouldn't trust DHCP server totally -- I've had my run of broken(?)
DHCP setups, which do give address that is already use (probably some
DHCP proxy issue). The life saver was that host did DAD, detected
duplicate and asked another address, all was fine.... until it
happened that the other address too was in use and host was stuck
because DHCP kept giving the same two alternate addresses.

I would do DAD by default on any configured address, regardless
of the way it was selected (manual, DHCP or whatever).

Even with IPv6 I see many ways of getting DCHP servers view of
addresses currently in use getting out of synch ("intelligent
switches" might be one cause, when host is moved from one segment to
another, and switch routes by learned MAC incorrectly ...)


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



From ipv6-bounces@ietf.org Tue Aug 21 06:17:04 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INQlV-0008BM-8g; Tue, 21 Aug 2007 06:15:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INQlT-0008BF-9r
	for ipv6@ietf.org; Tue, 21 Aug 2007 06:15:11 -0400
Received: from salmon.maths.tcd.ie ([2001:770:10:300::86e2:510b])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1INQlR-0003vo-Pm
	for ipv6@ietf.org; Tue, 21 Aug 2007 06:15:11 -0400
Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie)
	by salmon.maths.tcd.ie with SMTP id <aa82387@salmon>;
	21 Aug 2007 11:15:08 +0100 (BST)
Date: Tue, 21 Aug 2007 11:15:08 +0100
From: David Malone <dwmalone@maths.tcd.ie>
To: IPv6 WG <ipv6@ietf.org>
Message-ID: <20070821101508.GA81228@walton.maths.tcd.ie>
References: <46C4288A.1060408@innovationslab.net>
	<20070820105429.GB9879@login.ecs.soton.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070820105429.GB9879@login.ecs.soton.ac.uk>
User-Agent: Mutt/1.5.6i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Mon, Aug 20, 2007 at 11:54:29AM +0100, Tim Chown wrote:
> (http://tools.ietf.org/html/draft-narten-ipv6-3177bis-48boundary-02)

I note that the IPv6 tools.ietf.org seems to be down or inaccessable
since late last week. A nearby hop is returning no route to host
and address inaccessable messages. I tried mailing Kurt, but I
haven't heard back yet.

	David.

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



From ipv6-bounces@ietf.org Tue Aug 21 06:23:50 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INQs6-0004VF-Gp; Tue, 21 Aug 2007 06:22:02 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INQs4-0004Uk-MI
	for ipv6@ietf.org; Tue, 21 Aug 2007 06:22:00 -0400
Received: from salmon.maths.tcd.ie ([134.226.81.11])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1INQs4-0000S3-7P
	for ipv6@ietf.org; Tue, 21 Aug 2007 06:22:00 -0400
Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie)
	by salmon.maths.tcd.ie with SMTP id <aa85528@salmon>;
	21 Aug 2007 11:21:59 +0100 (BST)
Date: Tue, 21 Aug 2007 11:21:56 +0100
From: David Malone <dwmalone@maths.tcd.ie>
To: Bob Hinden <bob.hinden@nokia.com>
Message-ID: <20070821102156.GB81228@walton.maths.tcd.ie>
References: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
User-Agent: Mutt/1.5.6i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Mon, Aug 20, 2007 at 01:43:19PM -0700, Bob Hinden wrote:
> We would like to get your comments on the following two choices:
> 
> 1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate-rh0-01.txt>.

I would have originally supported option (2), because it would have
allowed RH0 to be used in a relatively harmless way. However, I now
believe (1) is the practical option, because as Joe says, we can
consider RH0 as "poisioned".

	David.

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



From ipv6-bounces@ietf.org Tue Aug 21 06:59:21 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INRQE-0002zQ-28; Tue, 21 Aug 2007 06:57:18 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INRQB-0002zG-Mj
	for ipv6@ietf.org; Tue, 21 Aug 2007 06:57:15 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1INRQB-0001NO-3n
	for ipv6@ietf.org; Tue, 21 Aug 2007 06:57:15 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 8CDD21986B7;
	Tue, 21 Aug 2007 13:57:13 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 4120F1986A6;
	Tue, 21 Aug 2007 13:57:13 +0300 (EEST)
Message-ID: <46CAC50A.8010807@piuha.net>
Date: Tue, 21 Aug 2007 13:57:14 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: David Malone <dwmalone@maths.tcd.ie>
References: <46C4288A.1060408@innovationslab.net>	<20070820105429.GB9879@login.ecs.soton.ac.uk>
	<20070821101508.GA81228@walton.maths.tcd.ie>
In-Reply-To: <20070821101508.GA81228@walton.maths.tcd.ie>
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: 2409bba43e9c8d580670fda8b695204a
Cc: IPv6 WG <ipv6@ietf.org>, Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

It works for me, but only in v4. Some routing issue in v6
side. Ccing Henrik who runs these sites.

Jari

David Malone kirjoitti:
> On Mon, Aug 20, 2007 at 11:54:29AM +0100, Tim Chown wrote:
>   
>> (http://tools.ietf.org/html/draft-narten-ipv6-3177bis-48boundary-02)
>>     
>
> I note that the IPv6 tools.ietf.org seems to be down or inaccessable
> since late last week. A nearby hop is returning no route to host
> and address inaccessable messages. I tried mailing Kurt, but I
> haven't heard back yet.
>
> 	David.
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>
>   


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



From ipv6-bounces@ietf.org Tue Aug 21 07:04:02 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INRV2-0007AY-Jz; Tue, 21 Aug 2007 07:02:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INRV1-0007AT-It
	for ipv6@ietf.org; Tue, 21 Aug 2007 07:02:15 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1INRV0-0001XY-PL
	for ipv6@ietf.org; Tue, 21 Aug 2007 07:02:15 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 21 Aug 2007 07:02:14 -0400
X-IronPort-AV: i="4.19,289,1183348800"; 
	d="scan'208"; a="68561032:sNHT57586678"
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 l7LB2ELA004165; 
	Tue, 21 Aug 2007 07:02:14 -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 l7LB25mj017736; 
	Tue, 21 Aug 2007 11:02:14 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); 
	Tue, 21 Aug 2007 07:02:11 -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: Tue, 21 Aug 2007 07:02:10 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB2104D4B13D@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <200708211008.l7LA8L9l014359@burp.tkv.asdf.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Rethinking autoconfig,
	was Re: prefix length determination for DHCPv6
Thread-Index: Acfj2118/9K6RgyxQMu15G1Au8m+DgABy5Mg
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "Markku Savela" <msa@moth.iki.fi>, <ipv6@ietf.org>
X-OriginalArrivalTime: 21 Aug 2007 11:02:11.0530 (UTC)
	FILETIME=[B95C5AA0:01C7E3E2]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1927; t=1187694134;
	x=1188558134; 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=20Rethinking=20autoconfig,
	was=20Re=3A=20prefix=20length =20determination=20for=20DHCPv6
	|Sender:=20
	|To:=20=22Markku=20Savela=22=20<msa@moth.iki.fi>,=20<ipv6@ietf.org>;
	bh=v24vvK5DyJM1k3ZIgAmYaDoGkL417q5j5oDWMzPAN2I=;
	b=VIjGy3NIhdZSls9CxJ/inPicosE/6URzvmK9vaPaATn63l9TXATI1YVg5D6MPKstEbLGnqPa
	AlbANc5r9F0ZBmo5/2CaITqmf85sQ6QMMn7GcEDBcKeqtAPQmlepic8M;
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: 50a516d93fd399dc60588708fd9a3002
Cc: 
Subject: RE: Rethinking autoconfig,
	was Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

And, there's always the case where the DHCP server has lost it memory
(i.e. disk) - in that case it would have no idea what was or was not
leased.

- Bernie=20

-----Original Message-----
From: Markku Savela [mailto:msa@moth.iki.fi]=20
Sent: Tuesday, August 21, 2007 6:08 AM
To: ipv6@ietf.org
Subject: Re: Rethinking autoconfig,was Re: prefix length determination
for DHCPv6


> From: Iljitsch van Beijnum <iljitsch@muada.com>

> > 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.
>=20
> Let me rephrase: making DAD more efficient. If there's a DHCP server =20
> present that knows about all addresses anyway, then obviously the =20
> DHCP server is capable of determining whether two nodes are trying to

> use the same address, which is probably more efficient than hosts =20
> doing DAD for each address.

I wouldn't trust DHCP server totally -- I've had my run of broken(?)
DHCP setups, which do give address that is already use (probably some
DHCP proxy issue). The life saver was that host did DAD, detected
duplicate and asked another address, all was fine.... until it
happened that the other address too was in use and host was stuck
because DHCP kept giving the same two alternate addresses.

I would do DAD by default on any configured address, regardless
of the way it was selected (manual, DHCP or whatever).

Even with IPv6 I see many ways of getting DCHP servers view of
addresses currently in use getting out of synch ("intelligent
switches" might be one cause, when host is moved from one segment to
another, and switch routes by learned MAC incorrectly ...)


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

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



From ipv6-bounces@ietf.org Tue Aug 21 07:05:13 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INRWB-000836-HU; Tue, 21 Aug 2007 07:03:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INRWA-0007zy-6E
	for ipv6@ietf.org; Tue, 21 Aug 2007 07:03:26 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INRW8-0005B0-Kr
	for ipv6@ietf.org; Tue, 21 Aug 2007 07:03:26 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 7D35E1986B7;
	Tue, 21 Aug 2007 14:03:23 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 3A7221986A6;
	Tue, 21 Aug 2007 14:03:23 +0300 (EEST)
Message-ID: <46CAC67C.4060900@piuha.net>
Date: Tue, 21 Aug 2007 14:03:24 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: "Hemant Singh (shemant)" <shemant@cisco.com>
References: <B00EDD615E3C5344B0FFCBA910CF7E1D038FA85B@xmb-rtp-20e.amer.cisco.com>
	<46C9C39D.6050905@innovationslab.net>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038FAB6B@xmb-rtp-20e.amer.cisco.com>
	<46C9DAC1.8000102@innovationslab.net>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038FAC0E@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D038FAC0E@xmb-rtp-20e.amer.cisco.com>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81
Cc: Thomas Narten <narten@us.ibm.com>, IETF IPv6 Mailing List <ipv6@ietf.org>,
	Hesham Soliman <hesham@elevatemobile.com>
Subject: On-link issues, draft-wbeebee, 2461bis
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hemant,

I have reviewed your draft and the discussion on the IPv6 list.

Its easy to believe that there are implementations out there
that get things wrong. I also agree with the general technical
direction about DAd and being specific about where ND on-link
assumptions and prefixes can come from. And we should
value implementation experience and document it where
it can potentially help future implementers.

However, we already had a discussion about whether the
2462bis document should change. The WG believes they
have gotten the current requirements right, and I can't really
blame them for that. Please note that once 2462bis is an RFC,
IETF's official recommendation is to do exactly what you
want to happen. Those implementations that pay attention
to such things will change (if they need to). It is unfortunate
that earlier RFCs and some implementations operated
differently. But it is something that issuing a new RFC
cannot alone fix; we just have to live with that. I would
also note that the DAD process as a whole is not bullet
proof. Dropped packets, network partition, etc. can still
cause duplicated addresses to occur. The engineering
is to get the probability of that happening reasonably
low, and I think we are there.

You also suggested that 2461bis be changed to
clarify the on/off-link rules. I thought that most
of your clarified rules were good, though I did not
perform a detailed review so there may still be
issues. I note that others had question marks
on some of them. In any case, my big question
is to what extent you are (a) making an implementation
error less likely by emphasizing and reformulating
rules that 2461bis already has or (b) making some
actual new, tighter rules. I think most of it falls
under category (a). Is there some that are in (b)?

However, the amount of new text goes beyond what
we can put in under AUTH48. Given that the group
does not seem to unanimously believe that the
rules are missing from 2461bis, I feel reluctant
to go through the approval process once more.
It is more important to have a standard than to
achieve perfection.

However, I would like to make sure that the
implementation guidance is not lost. And it
may even be that after a discussion we realize
that the on-link rules need further work. Its
completely possible that we have to clarify
some part of ND even after 2461bis has been published;
the maintenance WG has been created in order to
deal with issues like that.

Here's what I would suggest:

1) We proceed with 2461bis publication.

2) We proceed with 2462bis publication.

3) You write one document that collects the
implementation guidance/clarified rules regarding
on/off link behaviour, and offer it for the new
IPv6 maintenance WG.

4) You write another document that collects other
implementation experience, and also offer it to the
same WG.

Jari


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



From ipv6-bounces@ietf.org Tue Aug 21 07:28:51 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INRsu-0001R3-T6; Tue, 21 Aug 2007 07:26:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INRss-0001O6-Va
	for ipv6@ietf.org; Tue, 21 Aug 2007 07:26:54 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INRsr-0005j3-7E
	for ipv6@ietf.org; Tue, 21 Aug 2007 07:26:54 -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 l7LBNIif016765
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Tue, 21 Aug 2007 13:23:19 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <8E296595B6471A4689555D5D725EBB2104D4B13D@xmb-rtp-20a.amer.cisco.com>
References: <8E296595B6471A4689555D5D725EBB2104D4B13D@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: <10DEB840-AC62-4952-8FE9-9BCA86909830@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Tue, 21 Aug 2007 13:25:33 +0200
To: Bernie Volz ((volz)) <volz@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Cc: ipv6@ietf.org
Subject: Re: Rethinking autoconfig,
	was Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 21-aug-2007, at 13:02, Bernie Volz ((volz)) wrote:

> And, there's always the case where the DHCP server has lost it memory
> (i.e. disk) - in that case it would have no idea what was or was not
> leased.

Yes, the server would have to tell nodes to do DAD until all the  
leases from before the reboot have expired.

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



From ipv6-bounces@ietf.org Tue Aug 21 07:50:54 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INSEG-0000BO-GD; Tue, 21 Aug 2007 07:49:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INSEF-0000BH-3n
	for ipv6@ietf.org; Tue, 21 Aug 2007 07:48:59 -0400
Received: from burp.tkv.asdf.org ([212.16.99.49])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INSEE-0006EN-Gp
	for ipv6@ietf.org; Tue, 21 Aug 2007 07:48:59 -0400
Received: from burp.tkv.asdf.org (msa@localhost [127.0.0.1])
	by burp.tkv.asdf.org (8.14.1/8.14.1/Debian-8) with ESMTP id
	l7LBmvPL016655 for <ipv6@ietf.org>; Tue, 21 Aug 2007 14:48:57 +0300
Received: (from msa@localhost)
	by burp.tkv.asdf.org (8.14.1/8.14.1/Submit) id l7LBmvB0016652;
	Tue, 21 Aug 2007 14:48:57 +0300
Date: Tue, 21 Aug 2007 14:48:57 +0300
Message-Id: <200708211148.l7LBmvB0016652@burp.tkv.asdf.org>
From: Markku Savela <msa@moth.iki.fi>
To: ipv6@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Subject: What about changing default router rules a bit?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


It's not difficult to find even home users with multiple ISP
links. Both ISP's send RA's with different prefixes (A=1).

Host sees now two default routers on link and will have multiple
global addresses. By current rules, host can use either router for
outgoing packets regardless of the selected source address.

I think it would be more sensible to pick the default router from the
set of routers that actually advertised the prefix matching the
selected source address?

This would be a simple way to avoid hitting the filters of the ISP's,
when wrong source address (for that ISP) is used.

The IPv6 architecture assumes all routers on link "co-operate", but I
think that is too much to expect from simple "home routers", the ISP
would be supplying... it's better to put some intelligence into host
requirements?

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



From ipv6-bounces@ietf.org Tue Aug 21 07:56:02 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INSJL-0006G0-Rf; Tue, 21 Aug 2007 07:54:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INSJK-0006Fn-EA
	for ipv6@ietf.org; Tue, 21 Aug 2007 07:54:14 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INSJJ-0006LN-V8
	for ipv6@ietf.org; Tue, 21 Aug 2007 07:54:14 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 4BCDB1986B7
	for <ipv6@ietf.org>; Tue, 21 Aug 2007 14:54:13 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 09DE9198680
	for <ipv6@ietf.org>; Tue, 21 Aug 2007 14:54:13 +0300 (EEST)
Message-ID: <46CAD266.4050807@piuha.net>
Date: Tue, 21 Aug 2007 14:54:14 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: IPv6 WG <ipv6@ietf.org>
References: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
	<20070821102156.GB81228@walton.maths.tcd.ie>
In-Reply-To: <20070821102156.GB81228@walton.maths.tcd.ie>
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: 7baded97d9887f7a0c7e8a33c2e3ea1b
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

A message from your AD...

First, I would like to encourage the group to make a timely
decision on this issue, fix the specifications, and move on.
Not because this particular issue is somehow bigger or
more crucial than others (it isn't). But because we need
to deal with fixing bugs and security vulnerabilities
from our specifications in a timely manner so that corrections
actually end up in RFCs rather than staying in the
folklore of the Internet community for years :-)

And I would like to move on also because I know
there are other issues and bugs we need to deal
with in this WG and elsewhere. We will treat them
with the same careful, analytic approach to figure
out if there really is an issue and what the best way
to deal with it is. We are not affected by bloated
claims of how bad an issue is, but neither are we
neglecting our duty to correct an error if we see
one.

Let me also remind people that we are here to
make standards for the Internet, things that go
into all hosts and routers. Consenting parties
can go beyond these standards or choose to
implement additional standardized features. But
we need to be careful about how much we require
from a general Internet node, and be clear about
how widely a feature (or a fixed feature in this case)
is expected to be used when we make a decision
about it.

Finally, as someone who has personally allocated
a new RH type number (2) for his spec, I can
say that the experience was generally pleasant
and can be recommended for others -- nothing to be
afraid of if there is a need for it.

Jari


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



From ipv6-bounces@ietf.org Tue Aug 21 08:46:12 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INT5X-0005y1-8C; Tue, 21 Aug 2007 08:44:03 -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>
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: Hideshi.Enokihara@jp.yokogawa.com, dhcwg@ietf.org, ipv6@ietf.org
Subject: Re: [dhcwg] RE: Is a DNS NS required,
	when a DHCPv6 Client transmits a Conform message? 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Tue Aug 21 09:06:35 2007
Return-path: <ipv6-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-0006Hs-B5; 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: Re: Rethinking autoconfig, was Re: prefix length determination for
 DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Tue Aug 21 09:09:42 2007
Return-path: <ipv6-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-0000dR-U0; 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: Re: Rethinking autoconfig, was Re: prefix length determination for
 DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Tue Aug 21 09:51:53 2007
Return-path: <ipv6-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-0002Zu-DO; 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: Re: Rethinking autoconfig, was Re: prefix length determination for
 DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Tue Aug 21 10:16:21 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INUV4-0000nc-Pv; Tue, 21 Aug 2007 10:14:30 -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>
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
X-Mailman-Approved-At: Tue, 21 Aug 2007 10:14:29 -0400
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: shane_kerr@isc.org
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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-----

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



From ipv6-bounces@ietf.org Tue Aug 21 10:26:28 2007
Return-path: <ipv6-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-0007wJ-Ul; 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>
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
Subject: Re: [dhcwg] Re: Rethinking autoconfig,
	was Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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

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



From ipv6-bounces@ietf.org Tue Aug 21 10:50:36 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INV2F-0006GC-Bi; Tue, 21 Aug 2007 10:48:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INV2D-0006G4-JM
	for ipv6@ietf.org; Tue, 21 Aug 2007 10:48:45 -0400
Received: from postfix.iai.uni-bonn.de ([131.220.8.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INV2C-0004L7-4r
	for ipv6@ietf.org; Tue, 21 Aug 2007 10:48:45 -0400
X-IAI-Env-From: <ignatios@cello.cs.uni-bonn.de> : [131.220.4.211]
Received: from theory.cs.uni-bonn.de (theory.cs.uni-bonn.de [131.220.4.211])
	by postfix.iai.uni-bonn.de (Postfix) with ESMTP
	id CA38F5C82E; Tue, 21 Aug 2007 16:48:42 +0200 (MEST)
	(envelope-from ignatios@cello.cs.uni-bonn.de)
	(envelope-to VARIOUS) (2)
	(internal use: ta=0, tu=1, te=0, am=-, au=-)
Received: from cello.cs.uni-bonn.de (cello.cs.uni-bonn.de [131.220.4.178])
	by theory.cs.uni-bonn.de (8.12.9/8.12.9) with SMTP id l7LEmgVE026133;
	Tue, 21 Aug 2007 16:48:42 +0200 (MEST)
Received: (from ignatios@cello.cs.uni-bonn.de)
	by cello.cs.uni-bonn.de (mini_sendmail/1.3.2 21nov2002 nb4 7oct2003);
	Tue, 21 Aug 2007 16:48:42 CEST (sender ignatios@cello.cs.uni-bonn.de)
Date: Tue, 21 Aug 2007 16:48:42 +0200
From: Ignatios Souvatzis <ignatios@cs.uni-bonn.de>
To: IPv6 WG <ipv6@ietf.org>, Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <20070821144842.GA13747@cs.uni-bonn.de>
References: <46C4288A.1060408@innovationslab.net>
	<20070820105429.GB9879@login.ecs.soton.ac.uk>
	<20070821101508.GA81228@walton.maths.tcd.ie>
	<46CAC50A.8010807@piuha.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46CAC50A.8010807@piuha.net>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: 
Subject: Re: tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Tue, Aug 21, 2007 at 01:57:14PM +0300, Jari Arkko wrote:
> It works for me, but only in v4. Some routing issue in v6
> side. Ccing Henrik who runs these sites.

traceroute to tools.ietf.org (2001:698:9:31:214:22ff:fe21:bb), 30 hops max, 60 byte packets
 1  exp (2001:638:403:5050:2d0:b7ff:fe75:c02c)  5.680 ms  0.854 ms  0.767 ms
 2  2001:638:403:f01::1  4.253 ms  2.294 ms  2.286 ms

[...]

12  2001:698:9:2:208:21ff:fe87:3480  28.866 ms  27.888 ms !H 
13  * 2001:698:9:2:208:21ff:fe87:3480  28.857 ms  27.453 ms !H
14  2001:698:9:2:208:21ff:fe87:3480  3139.250 ms !A *  3025.377 ms !A

so some sort of problem near the destination host.

	-is

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



From ipv6-bounces@ietf.org Tue Aug 21 10:52:46 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INV4K-0007Tb-QJ; Tue, 21 Aug 2007 10:50:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INV4J-0007Ou-0t
	for ipv6@ietf.org; Tue, 21 Aug 2007 10:50:55 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INV4H-0004PD-RF
	for ipv6@ietf.org; Tue, 21 Aug 2007 10:50:55 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 21 Aug 2007 10:50:53 -0400
X-IronPort-AV: i="4.19,290,1183348800"; 
	d="scan'208"; a="129463749:sNHT56153448"
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 l7LEorwJ009110; 
	Tue, 21 Aug 2007 10:50:53 -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 l7LEogmf017714; 
	Tue, 21 Aug 2007 14:50:47 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); 
	Tue, 21 Aug 2007 10:50:47 -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: Tue, 21 Aug 2007 10:50:46 -0400
Message-ID: <8E296595B6471A4689555D5D725EBB2104D4B270@xmb-rtp-20a.amer.cisco.com>
In-Reply-To: <10DEB840-AC62-4952-8FE9-9BCA86909830@muada.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Rethinking autoconfig,
	was Re: prefix length determination for DHCPv6
Thread-Index: Acfj5gOaKYve0/puTteMN6onXctIMAAHFC6Q
From: "Bernie Volz \(volz\)" <volz@cisco.com>
To: "Iljitsch van Beijnum" <iljitsch@muada.com>
X-OriginalArrivalTime: 21 Aug 2007 14:50:47.0306 (UTC)
	FILETIME=[A899AEA0:01C7E402]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=889; t=1187707853;
	x=1188571853; 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=20Rethinking=20autoconfig,
	=20was=20Re=3A=20prefix=20len
	gth=20determination=20for=20DHCPv6 |Sender:=20
	|To:=20=22Iljitsch=20van=20Beijnum=22=20<iljitsch@muada.com>;
	bh=FR9fC15r6evHmMJRp7FeHhwVa3tToHq/B7EvT+C0SFk=;
	b=BFsMbK9zSGEwlCBVmxHB0OcTMR7Jfqg/2rxF5SA0RdFZT1CEp6gbTN0z8syy4sSEfnEn+DFZ
	jSOtTJcCpRcw/1vzAvoecT/vML7wCsHRF6DW2HXv21iBYeRWWQmnd3IM;
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: 7655788c23eb79e336f5f8ba8bce7906
Cc: ipv6@ietf.org
Subject: RE: Rethinking autoconfig,
	was Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Best to just always have the nodes to DAD. The cost of a DAD message is
pretty low. I'm only recommending this on Ethernet-like networks. If you
have a low-bandwidth network or don't have a shared media, your physical
link layer documents may specify not to do DAD.

- Bernie=20

-----Original Message-----
From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]=20
Sent: Tuesday, August 21, 2007 7:26 AM
To: Bernie Volz (volz)
Cc: Markku Savela; ipv6@ietf.org
Subject: Re: Rethinking autoconfig, was Re: prefix length determination
for DHCPv6

On 21-aug-2007, at 13:02, Bernie Volz ((volz)) wrote:

> And, there's always the case where the DHCP server has lost it memory
> (i.e. disk) - in that case it would have no idea what was or was not
> leased.

Yes, the server would have to tell nodes to do DAD until all the =20
leases from before the reboot have expired.

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



From ipv6-bounces@ietf.org Tue Aug 21 11:28:26 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INVcq-0002km-2p; Tue, 21 Aug 2007 11:26:36 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INVco-0002ii-D3
	for ipv6@ietf.org; Tue, 21 Aug 2007 11:26:34 -0400
Received: from vms048pub.verizon.net ([206.46.252.48])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1INVcn-0001dw-UT
	for ipv6@ietf.org; Tue, 21 Aug 2007 11:26:34 -0400
Received: from vms068.mailsrvcs.net ([192.168.1.2])
	by vms048.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01
	(built Apr
	3 2006)) with ESMTPA id <0JN4002BDQW41TWB@vms048.mailsrvcs.net> for
	ipv6@ietf.org; Tue, 21 Aug 2007 10:26:28 -0500 (CDT)
Received: from 129.55.200.20 ([129.55.200.20])
	by vms068.mailsrvcs.net (Verizon Webmail) with HTTP; Tue,
	21 Aug 2007 10:26:28 -0500 (CDT)
Date: Tue, 21 Aug 2007 10:26:28 -0500 (CDT)
From: Tim Enos <timbeck04@verizon.net>
X-Originating-IP: [129.55.200.20]
To: Joe Abley <jabley@ca.afilias.info>, bob.hinden@nokia.com
Message-id: <17300496.9183411187709988199.JavaMail.root@vms068.mailsrvcs.net>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

I would like to see the WG adopt option 1) for the same reasons as listed in Joe's e-mail.

>
>On 20-Aug-2007, at 16:43, Bob Hinden wrote:
>
>> We would like to get your comments on the following two choices:
>>
>> 1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate- 
>> rh0-01.txt>.
>
>I support this option since:
>
>1. I think it is the clearest solution to the problem (as in, easiest  
>to understand). I believe clarity is important here, since ambiguity  
>seems like a path to "let's block all routing headers, just to be on  
>the safe side".

Exactly. It protects against the potential attacks outlined in the draft while taking great pains to encourage the preservation of other RH types (and the applications that rely upon them (e.g. RH2 and MIPv6)).

>
>2. It facilitates identification of "dangerous" source-routing in a  
>way that is already available on several platforms (checking the RH  
>type) without requiring devices to distinguish between old and new  
>semantics (as would be needed in the case of a shared codepoint  
>between the original and new specification).
>
>3. Architecturally, choosing a new codepoint for functionality which  
>is different, even if it is similar, seems like the right thing.
>
>4. It is congruent with the approach several significant  
>implementations have taken (e.g. Linux, *BSD, Mac OS X).

And just as pointed out by James Woodyatt, the latest firmware for the AirPort Extreme 802.11n base station.

>
>5. Nobody has come forward with an indication that functionality  
>requiring RH0 in its current form is widely deployed or required. It  
>seems at least plausible that we might expect to have heard of such a  
>use case given the publicity surrounding the CanSecWest presentation,  
>regardless of whether you choose to classify that publicity as  
>"hysteria" or "journalism" :-).
>
>6. It seems likely that some IPv6 operators have taken the precaution  
>of dropping datagrams carrying RH0, and hence the zero type might be  
>considered effectively poisoned for use on the public Internet. Re- 
>use of type zero would hence only be of reliable use within  
>controlled networks; to be of general use, a benign source routing  
>option would need a new codepoint.
>
>
>Joe

Best Regards,

Tim Enos
Rom 8:28-39

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


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



From ipv6-bounces@ietf.org Tue Aug 21 11:37:48 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INVm3-00063s-Ah; Tue, 21 Aug 2007 11:36:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INVm2-00063m-5X
	for ipv6@ietf.org; Tue, 21 Aug 2007 11:36:06 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INVm0-0006CJ-US
	for ipv6@ietf.org; Tue, 21 Aug 2007 11:36:06 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 21 Aug 2007 11:36:05 -0400
X-IronPort-AV: i="4.19,290,1183348800"; 
	d="scan'208"; a="129468877:sNHT72789006"
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 l7LFa4jv032014; 
	Tue, 21 Aug 2007 11:36:04 -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 l7LFZkmp005497; 
	Tue, 21 Aug 2007 15:35:55 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); 
	Tue, 21 Aug 2007 11:35:54 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 21 Aug 2007 11:35:53 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D038FAF93@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <46CAC67C.4060900@piuha.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: On-link issues, draft-wbeebee, 2461bis
Thread-Index: Acfj4unDhiidWGYfSyGbrUn9wJYjNQAEc68g
References: <B00EDD615E3C5344B0FFCBA910CF7E1D038FA85B@xmb-rtp-20e.amer.cisco.com>
	<46C9C39D.6050905@innovationslab.net>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038FAB6B@xmb-rtp-20e.amer.cisco.com>
	<46C9DAC1.8000102@innovationslab.net>
	<B00EDD615E3C5344B0FFCBA910CF7E1D038FAC0E@xmb-rtp-20e.amer.cisco.com>
	<46CAC67C.4060900@piuha.net>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Jari Arkko" <jari.arkko@piuha.net>,
	"Hemant Singh (shemant)" <shemant@cisco.com>
X-OriginalArrivalTime: 21 Aug 2007 15:35:54.0746 (UTC)
	FILETIME=[F65C3DA0:01C7E408]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=6339; t=1187710564;
	x=1188574564; 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=20On-link=20issues,=20draft-wbeebee,=202461bis
	|Sender:=20 |To:=20=22Jari=20Arkko=22=20<jari.arkko@piuha.net>,
	=0A=20=20=20=20=20=20=
	20=20=22Hemant=20Singh=20(shemant)=22=20<shemant@cisco.com>;
	bh=xANEgZa00s7Ss3TZPAvbBg2hBOUYnOb7yAfiMXNVcTY=;
	b=NWwd1FZVs0mjAq+4a3R0qGN7gIZoroVYDt2kSNEosPoySkfImDIkOPiS796q0ZjBH1bj7xaM
	JazCOkH4fTF/1B9V8LkfsRuiin/AI/bbu8e+L5uaIJ3+mcF5VnG0ws+V;
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: 22bbb45ef41b733eb2d03ee71ece8243
Cc: Thomas Narten <narten@us.ibm.com>, IETF IPv6 Mailing List <ipv6@ietf.org>,
	Hesham Soliman <hesham@elevatemobile.com>
Subject: RE: On-link issues, draft-wbeebee, 2461bis
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Jari,

Wrt to this point you raised snipped in quotes below, please see our
response:

"In any case, my big question is to what extent you are (a) making an
implementation error less likely by emphasizing and reformulating rules
that 2461bis already has or (b) making some actual new, tighter rules. I
think most of it falls under category (a). Is there some that are in
(b)?"
=20
In the -02 version of our I-D, we are not making any new rule over what
has not been already specified in 2461bis or 2462bis. This is subject to
everyone agreeing with our interpretation of 2461bis. So yes, I believe
our rules fall only under (a) above. As for question marks on any text
in our I-D, so far only Jinmei and Vlad Yasevitch have reviewed our I-D.
Vlad reviewed the complete -01 version of our I-D. We closed all issues
in -01 with him in the -02 version - he can correct me if I am mistaken.
Jinmei reviewed only the portion of our -00 and/or -01 I-D that proposed
changes to 2462bis. We have also closed any question marks with him on
his review - he wanted us to back off forcing older host implementations
to change for skipping DAD - we did back off.

As to the extent of our clarification, I don't think the IPv6 community
or the RFC's were clear on how to specify off-link in RA. We found
passing references to off-link behavior in one paragraph of a general
section 3.1 in 2461bis - we mention this paragraph in section 2.1 of our
I-D. Then we found one paragraph in section 6.3.4 of 2462bis where
off-link behavior was implied. Since off-link has been specified by
2461bis as the opposite of on-link, we are saying even on-link is not
clearly specified in some cases. Therefore, it's not just stricter
language and reformatting of rules that is the output of our I-D.
2461bis does not have ANY clear rules to specify off-link - it's just
text buried in some paragraph that one has to interpret as off-link
behavior. I have gone into enough details in emails as to why specifying
on- vs. off-link is key to ND because that affects whether a host
performs address resolution or send traffic to default router. Incorrect
host behavior leads to loosing network connectivity in an aggregation
router network.

As per your guideline, here is our plan moving forward for the two
documents. We are basically breaking up our I-D into two new documents
where none of the two new documents will include sections 5 and 6 from
our existing I-D - these section relate to proposed changes to 2461bis
and 2462bis respectively.

1. We will put together a document that collects the implementation
guidance/clarified rules regarding on/off link behavior - this document
will include sections 2-4 of our current I-D. This document makes sense
to be on Standards Track or be a BCP.

2. We will put together a second document that collects other
implementation experience. This document will follow a format as
specified in section 7 of our I-D. This document makes sense to be on
Informational track. Anyone is welcome to send us logs of key ND bugs to
add to this document.=20

Best Regards.

Hemant


-----Original Message-----
From: Jari Arkko [mailto:jari.arkko@piuha.net]=20
Sent: Tuesday, August 21, 2007 7:03 AM
To: Hemant Singh (shemant)
Cc: Hesham Soliman; Wes Beebee (wbeebee); Thomas Narten; IETF IPv6
Mailing List
Subject: On-link issues, draft-wbeebee, 2461bis

Hemant,

I have reviewed your draft and the discussion on the IPv6 list.

Its easy to believe that there are implementations out there that get
things wrong. I also agree with the general technical direction about
DAd and being specific about where ND on-link assumptions and prefixes
can come from. And we should value implementation experience and
document it where it can potentially help future implementers.

However, we already had a discussion about whether the 2462bis document
should change. The WG believes they have gotten the current requirements
right, and I can't really blame them for that. Please note that once
2462bis is an RFC, IETF's official recommendation is to do exactly what
you want to happen. Those implementations that pay attention to such
things will change (if they need to). It is unfortunate that earlier
RFCs and some implementations operated differently. But it is something
that issuing a new RFC cannot alone fix; we just have to live with that.
I would also note that the DAD process as a whole is not bullet proof.
Dropped packets, network partition, etc. can still cause duplicated
addresses to occur. The engineering is to get the probability of that
happening reasonably low, and I think we are there.

You also suggested that 2461bis be changed to clarify the on/off-link
rules. I thought that most of your clarified rules were good, though I
did not perform a detailed review so there may still be issues. I note
that others had question marks on some of them. In any case, my big
question is to what extent you are (a) making an implementation error
less likely by emphasizing and reformulating rules that 2461bis already
has or (b) making some actual new, tighter rules. I think most of it
falls under category (a). Is there some that are in (b)?

However, the amount of new text goes beyond what we can put in under
AUTH48. Given that the group does not seem to unanimously believe that
the rules are missing from 2461bis, I feel reluctant to go through the
approval process once more.
It is more important to have a standard than to achieve perfection.

However, I would like to make sure that the implementation guidance is
not lost. And it may even be that after a discussion we realize that the
on-link rules need further work. Its completely possible that we have to
clarify some part of ND even after 2461bis has been published; the
maintenance WG has been created in order to deal with issues like that.

Here's what I would suggest:

1) We proceed with 2461bis publication.

2) We proceed with 2462bis publication.

3) You write one document that collects the implementation
guidance/clarified rules regarding on/off link behaviour, and offer it
for the new
IPv6 maintenance WG.

4) You write another document that collects other implementation
experience, and also offer it to the same WG.

Jari

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



From ipv6-bounces@ietf.org Tue Aug 21 15:24:26 2007
Return-path: <ipv6-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-0008Qp-Fc; 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>
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: 
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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



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



From ipv6-bounces@ietf.org Tue Aug 21 18:05:32 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INbnv-0001VJ-To; Tue, 21 Aug 2007 18:02:27 -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
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
X-Mailman-Approved-At: Tue, 21 Aug 2007 18:02:26 -0400
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] Re: Rethinking autoconfig,
	was Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0012830983=="
Errors-To: ipv6-bounces@ietf.org


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


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

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

--===============0012830983==--




From ipv6-bounces@ietf.org Tue Aug 21 20:02:49 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INddb-0005eQ-L7; Tue, 21 Aug 2007 19:59:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INdda-0005eE-1s
	for ipv6@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-0003Si-4O
	for ipv6@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
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>
Subject: Re: [dhcwg] RE: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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


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



From ipv6-bounces@ietf.org Wed Aug 22 04:14:28 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INlJf-0006In-KR; Wed, 22 Aug 2007 04:11:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INlJe-0006Eh-D7
	for ipv6@ietf.org; Wed, 22 Aug 2007 04:11:50 -0400
Received: from py-out-1112.google.com ([64.233.166.180])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INlJd-0004z3-Lb
	for ipv6@ietf.org; Wed, 22 Aug 2007 04:11:49 -0400
Received: by py-out-1112.google.com with SMTP id f31so313438pyh
	for <ipv6@ietf.org>; Wed, 22 Aug 2007 01:11:49 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=UJf47je2vKO8VCHgsH+WsZnipFY5FIOoCtQwLEFrMOiswPopG5/GwmQ6ex93ybgit0KBjyoDziW4vzYrTUyyz5QbtRNCuOp/4s1Yq9DfMrO6LRh+60fTVIKpO4TK7ZQJP+pESSzDt/euwZ/16DHv1pVS11Xad2L3tTfcQUx7mEc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=RGHiyB3ac8kr2iM8rFZVWH4SbPxHcR4+pq/omGzCIl+M28p/ks1pENc5G0I8mAxybVdJCjBJD/4V+dKp149RkxGeTYXJZkYtnc9Y5pG5wmMSNzugciSfhWpwZMTJneVwm/Y0FQiu7YzL4uNrDfBpgJ+cOHkVfHiOHFi5Zs5lsk4=
Received: by 10.65.141.18 with SMTP id t18mr420035qbn.1187770308243;
	Wed, 22 Aug 2007 01:11:48 -0700 (PDT)
Received: from ?192.168.1.58? ( [85.0.167.32])
	by mx.google.com with ESMTPS id f6sm2140181nfh.2007.08.22.01.11.45
	(version=SSLv3 cipher=RC4-MD5); Wed, 22 Aug 2007 01:11:47 -0700 (PDT)
Message-ID: <46CAC55E.4050509@gmail.com>
Date: Tue, 21 Aug 2007 12:58:38 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: bob.hinden@nokia.com
References: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
In-Reply-To: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-08-20 22:43, Bob Hinden wrote:

> 1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate-rh0-01.txt>.

This is my preference. It's the only way to be sure the problem
is definitely fixed.

> 
> 2) Revising the draft to restrict the usage of RH0.  This would continue 
> to require RH0 to be implemented but would restrict the functionality of 
> RH0.  For example, require nodes to have support for RH0 turned off by 
> default, limit the number of RH0 headers in a packet to one, limit the 
> number of addresses in the RH0 to a smaller number (e.g., 6), and and a 
> requirement that addresses can only be in the header once.

I would prefer this to be done using a new RH number. Redefining an
existing header in this way will cause operational confusion.

    Brian


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



From ipv6-bounces@ietf.org Wed Aug 22 11:01:41 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1INrgD-0000re-GZ; Wed, 22 Aug 2007 10:59:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1INrgC-0000rL-6N
	for ipv6@ietf.org; Wed, 22 Aug 2007 10:59:32 -0400
Received: from imr2.ericy.com ([198.24.6.3])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1INrgA-0005TO-SV
	for ipv6@ietf.org; Wed, 22 Aug 2007 10:59:32 -0400
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se
	[138.85.77.50])
	by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id l7MF3uKU003885;
	Wed, 22 Aug 2007 10:03:56 -0500
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.53]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Aug 2007 09:59:29 -0500
Received: from [142.133.10.140] ([142.133.10.140]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 22 Aug 2007 09:59:29 -0500
Message-ID: <46CC4F9C.7050609@ericsson.com>
Date: Wed, 22 Aug 2007 11:00:44 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 1.5 (X11/20060313)
MIME-Version: 1.0
To: bob.hinden@nokia.com
References: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
In-Reply-To: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 22 Aug 2007 14:59:29.0508 (UTC)
	FILETIME=[0A452240:01C7E4CD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Bob,
   I would go for Option 1(deprecate), though I am not sure it is 
reasonable to assume people will "unimplement" the code for RH0 for 
already deployed implementations. Option 2 is also acceptable to me.

Thanks
Suresh

Bob Hinden wrote:
> Hi,
> 
> After the reviewing the comments received during the working group last 
> call on <draft-ietf-ipv6-deprecate-rh0-01.txt> and discussing it with 
> our AD, the IPv6 w.g. chairs think it would be valuable to ask the 
> question again.  We want to make sure there continues to be a consensus 
> for deprecating RH0 as specified in the current draft as opposed to 
> restricting it's usage as was suggest in several of the last call comments.
> 
> We would like to get your comments on the following two choices:
> 
> 1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate-rh0-01.txt>.
> 
> 2) Revising the draft to restrict the usage of RH0.  This would continue 
> to require RH0 to be implemented but would restrict the functionality of 
> RH0.  For example, require nodes to have support for RH0 turned off by 
> default, limit the number of RH0 headers in a packet to one, limit the 
> number of addresses in the RH0 to a smaller number (e.g., 6), and and a 
> requirement that addresses can only be in the header once.
> 
> Please send your answer this question (including why) to the list or to 
> the chairs directly.  We will review the responses and report the 
> results to the w.g. early next week.  We are not trying to start a 
> debate, but want to get a new measure of the consensus.
> 
> We note that if there continues to be a consensus for 1), then we will 
> forward the draft to the ADs for proposed standard.
> 
> Thanks,
> Bob Hinden & Brian Haberman
> IPv6 w.g. Chairs
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


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



From ipv6-bounces@ietf.org Wed Aug 22 23:53:13 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IO3id-0003bZ-61; Wed, 22 Aug 2007 23:50:51 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IO3ic-0003bU-1p
	for ipv6@ietf.org; Wed, 22 Aug 2007 23:50:50 -0400
Received: from prometheus.interunix.net ([202.190.74.58])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IO3ib-0002Xz-2x
	for ipv6@ietf.org; Wed, 22 Aug 2007 23:50:49 -0400
Received: (qmail 24626 invoked by uid 1012); 23 Aug 2007 03:50:54 -0000
Received: from 202.129.165.26 by prometheus.interunix.net (envelope-from
	<prabu@hackinthebox.org>, uid 1010) with qmail-scanner-1.25-st-qms 
	(clamdscan: 0.87/3227. spamassassin: 3.1.8. perlscan: 1.25-st-qms.  
	Clear:RC:0(202.129.165.26):SA:0(-102.5/5.0):. 
	Processed in 6.426072 secs); 23 Aug 2007 03:50:54 -0000
X-Spam-Status: No, hits=-102.5 required=5.0
X-Spam-Report: SA TESTS
	-100 USER_IN_WHITELIST      From: address is in the user's white-list
	0.0 DK_POLICY_SIGNSOME Domain Keys: policy says domain signs some mails
	0.1 TW_BZ                  BODY: Odd Letter Triples with BZ
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	-0.0 AWL AWL: From: address is in the auto white-list
X-Antivirus-INTERUNIX-Mail-From: prabu@hackinthebox.org via
	prometheus.interunix.net
X-Antivirus-INTERUNIX: 1.25-st-qms
	(Clear:RC:0(202.129.165.26):SA:0(-102.5/5.0):. Processed in
	6.426072 secs Process 24610)
Received: from unknown (HELO ?127.0.0.1?) (prabu@interunix.net@202.129.165.26)
	by prometheus.interunix.net with SMTP; 23 Aug 2007 03:50:47 -0000
Message-ID: <46CD0408.60803@hackinthebox.org>
Date: Thu, 23 Aug 2007 11:50:32 +0800
From: Praburaajan <prabu@hackinthebox.org>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: security-basics@securityfocus.com,  ipv6@ietf.org, 
	forensics@securityfocus.com,  pen-test@securityfocus.com
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: 
Subject: Reminder: HITBSecConf2007 - Malaysia is less than 2 weeks away
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

HITBSecConf2007 - Malaysia is a mere 2 weeks away! Organized as a
community centric, non-profit effort, HITBSecConf is Asia's largest
network security event featuring 4 keynote speakers, 7 tracks of
technical training sessions and access to over 30 hours of deep
knowledge demos and presentations!

Date: 3rd - 6th September 2007
Venue: Hilton KL Sentral
Time: 0900 - 1800 What's on the menu

- 7 tracks of hands on technical training sessions (3rd & 4th)
- 4 keynote speakers (Mark 'Phiber Optik' Abene, Emmanuel Goldstein,
Mikko Hypponen and Lance Spitzner!)
- Lock Picking Village (run by members of TOOOL USA)
- Capure The Flag (team-based hacking competition with 11 teams from
around the world confirmed)
- BZFlag Area

Some of the highlight conference presentations:

- Hacking Biometric Systems
- High Security Locks - Illusion or Reality?
- How to 0wn Critical National Infrastructure - Hacking SCADA
- RDS-TMC Injection: How to Freak Out Your Sat Nav Systems
- Attacking Cisco NAC
- Hacking Hardened and Secured Oracle Servers

PLUS an exclusive presentation on WABISABILABI - The Exploit Marketplace
Project by their Director of Strategy, who will be taking questions from
the audience and speaking on the purpose of the project and it's future
plans.

Walk in registrants are accepted and the area where the lock picking
village, bzflag competition, zone-h hacking challenge and the capture
the flag 'live hacking' competition is being held is FREE AND OPEN TO
PUBLIC. So do come and check it out. :)

If you haven't registered yet, there's still time to do so but do note
that prices increase after 31st August 2007. For further details, please
see:

http://conference.hitb.org/hitbsecconf2007kl/




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



From ipv6-bounces@ietf.org Thu Aug 23 04:20:58 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IO7th-0003Mg-3j; Thu, 23 Aug 2007 04:18:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IO7tf-0003Ma-CW
	for ipv6@ietf.org; Thu, 23 Aug 2007 04:18:31 -0400
Received: from nf-out-0910.google.com ([64.233.182.186])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IO7tf-0008R5-0l
	for ipv6@ietf.org; Thu, 23 Aug 2007 04:18:31 -0400
Received: by nf-out-0910.google.com with SMTP id c10so317200nfd
	for <ipv6@ietf.org>; Thu, 23 Aug 2007 01:18:30 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:from:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id:sender;
	b=b6zRUOwYO6jvMOY1UFjKN4mjHkSayNr6bBxAJKdS2iLRpzpC5ruZ0sJnVczbm2rLXHUVSQuKITYNfHMnOjEkcNHJ4gPo5VjajgT9LVj860nuGj9TmISrl2BItuql8LYPjv1Fo/JSWJ3CkP+Mj1/fjBc2yxH2D/rLYlN45LEcb34=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:from:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id:sender;
	b=B+297OgJbqoDgqW+LRrFMmvOvocJFMqw/dyhV8833sTTEgkqvhgr3EYY/+DTx7UeCW8Jb/SPH3JHpRDQHE/A/WKG7zCkwKL/WCr0/vF9ioWRcXsDluXcPfUqsTDLQDNoYSA5b9+keAzb+3QjFwEy1QObSyStCOghituosP2d+bA=
Received: by 10.78.129.16 with SMTP id b16mr1029260hud.1187857109557;
	Thu, 23 Aug 2007 01:18:29 -0700 (PDT)
Received: from ?192.168.1.20? ( [212.119.9.178])
	by mx.google.com with ESMTPS id i4sm4416151nfh.2007.08.23.01.18.27
	(version=SSLv3 cipher=OTHER); Thu, 23 Aug 2007 01:18:28 -0700 (PDT)
From: Julien Laganier <julien.IETF@laposte.net>
To: ipv6@ietf.org
Date: Thu, 23 Aug 2007 10:18:23 +0200
User-Agent: KMail/1.9.6
References: <271CF87FD652F34DBF877CB0CB5D16FC05F80EF6@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
	<18084.55883.599274.586170@gargle.gargle.HOWL>
	<B00EDD615E3C5344B0FFCBA910CF7E1D036FEAD3@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D036FEAD3@xmb-rtp-20e.amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200708231018.23734.julien.IETF@laposte.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: Dave Thaler <dthaler@windows.microsoft.com>,
	"Ole Troan \(otroan\)" <otroan@cisco.com>, varada@txc.com,
	JINMEI Tatuya / ???? <jinmei@isl.rdc.toshiba.co.jp>
Subject: Re: Neighbor Discovery and PPP links
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hemant Singh wrote:
> James Carlson wrote:
> > Hemant Singh wrote:
> > > going to fix the bug when this peer hasn't responded to the NUD
> > > unicast NS? I have already said the source PPP client that issued
> > > the unicast NS is 2461bis complaint.
> >
> > I don't think it should "fix" the problem.  If the peer fails to
> > respond as expected, it has to declare the remote address to be
> > unreachable.
>
> But the peer is reachable in this p2p model !
>
> > I'm not sure why we'd necessarily expect the side that's working
> > right to work around bugs in the other side.  (In fact, it could be
> > argued that this is a good state of affairs: malfunctioning gear
> > may in fact have other bugs, and it's better to detect this early
> > rather than later.)
> >
> > Yes, it'd be possible to carve out a hole in NUD and say that if
> > there's _never_ a response from the peer to any NS for the life of
> > the link, and if the link is specifically point-to-point and
> > without link layer addresses, and if the link-layer is known to
> > perform keepalive- like operation, then the NS sender could
> > "assume" that the address is actually reachable.
>
> Let's not start preparing text for changes to 2461bis for PPP
> unless we can first discuss what to do about the server bug that Dave
> pointed out.

My 2 cents: Maybe the "server" vendor could fix the bug :)

--julien

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



From ipv6-bounces@ietf.org Thu Aug 23 05:23:44 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IO8rl-0003Jg-A4; Thu, 23 Aug 2007 05:20:37 -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
Cc: IETF, dhcwg@ietf.org, Iljitsch van Beijnum <iljitsch@muada.com>,
	Mailing List <ipv6@ietf.org>
Subject: Re: Rethinking autoconfig, was Re: prefix length determination for
 DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.


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



From ipv6-bounces@ietf.org Thu Aug 23 08:53:49 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IOC9z-0002vm-SO; Thu, 23 Aug 2007 08:51:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IOC9y-0002rf-38
	for ipv6@ietf.org; Thu, 23 Aug 2007 08:51:38 -0400
Received: from exprod8og54.obsmtp.com ([64.18.3.90])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IOC9w-0004nw-JT
	for ipv6@ietf.org; Thu, 23 Aug 2007 08:51:38 -0400
Received: from source ([15.133.48.47]) (using TLSv1) by exprod8ob54.obsmtp.com
	([64.18.7.12]) with SMTP; Thu, 23 Aug 2007 05:51:22 PDT
Received: from ([10.197.80.15])
	by yywatsrv54.kworld.kpmg.com with ESMTP with TLS id 5502192.38222217; 
	Thu, 23 Aug 2007 13:50:27  0100
Received: from ([10.197.80.67])
	by gowatsrv52.kworld.kpmg.com with ESMTP  id 5502165.36614493;
	Thu, 23 Aug 2007 13:50:06  0100
Received: from goamsexc40.kworld.kpmg.com ([10.197.80.66]) by
	goamsexc46.kworld.kpmg.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Aug 2007 14:50:06 +0200
Received: from GOALPEXC94.kworld.kpmg.com ([10.196.2.208]) by
	goamsexc40.kworld.kpmg.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Aug 2007 14:50:06 +0200
Received: from ARBUEEXC92.ar.kworld.kpmg.com ([10.202.1.54]) by
	GOALPEXC94.kworld.kpmg.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Aug 2007 08:50:05 -0400
Received: from mail pickup service by ARBUEEXC92.ar.kworld.kpmg.com with
	Microsoft SMTPSVC; Thu, 23 Aug 2007 09:49:21 -0300
Received: from GOALPEXC93.kworld.kpmg.com ([10.196.2.207]) by
	ARBUEEXC92.ar.kworld.kpmg.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Aug 2007 03:09:30 -0300
Received: from goamsexc46.kworld.kpmg.com ([10.197.80.67]) by
	GOALPEXC93.kworld.kpmg.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Aug 2007 02:09:28 -0400
Received: from gowatsrv51.kworld.kpmg.com ([10.197.80.14]) by
	goamsexc46.kworld.kpmg.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 23 Aug 2007 08:09:26 +0200
Received: from ([10.197.6.142])
	by gowatsrv51.kworld.kpmg.com with ESMTP with TLS id 5502146.28925052; 
	Thu, 23 Aug 2007 07:09:03  0100
Received: from ([64.18.3.176])
	by yywatsrv53.kworld.kpmg.com with SMTP  id 5502238.23911246;
	Thu, 23 Aug 2007 07:08:40  0100
Received: from source ([205.206.231.27]) by exprod8mx76.postini.com
	([64.18.7.10]) with SMTP; Wed, 22 Aug 2007 23:08:40 PDT
Received: from outgoing.securityfocus.com by outgoing.securityfocus.com
	via smtpd (for *.s8a1.psmtp.com [64.18.7.10]) with ESMTP;
	Wed, 22 Aug 2007 23:07:14 -0700
Received: from lists.securityfocus.com (lists.securityfocus.com
	[205.206.231.19]) by outgoing3.securityfocus.com (Postfix) with QMQP
	id 64C90237FEE; Wed, 22 Aug 2007 23:35:49 -0600 (MDT)
Mailing-List: contact pen-test-help@securityfocus.com; run by ezmlm
Precedence: bulk
Delivered-To: mailing list pen-test@securityfocus.com
Delivered-To: moderator for pen-test@securityfocus.com
Received: (qmail 18773 invoked from network); 23 Aug 2007 04:19:42 -0000
X-Spam-Status: No, hits=-102.5 required=5.0
X-Spam-Report: SA TESTS
	-100 USER_IN_WHITELIST      From: address is in the user's white-list
	0.0 DK_POLICY_SIGNSOME Domain Keys: policy says domain signs some mails
	0.1 TW_BZ                  BODY: Odd Letter Triples with BZ
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	-0.0 AWL AWL: From: address is in the auto white-list
X-Antivirus-INTERUNIX-Mail-From: prabu@hackinthebox.org via
	prometheus.interunix.net
X-Antivirus-INTERUNIX: 1.25-st-qms
	(Clear:RC:0(202.129.165.26):SA:0(-102.5/5.0):. Processed in
	6.426072 secs Process 24610)
Message-ID: <46CD0408.60803@hackinthebox.org>
Date: Thu, 23 Aug 2007 11:50:32 +0800
From: Praburaajan <prabu@hackinthebox.org>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: security-basics@securityfocus.com, ipv6@ietf.org,
	forensics@securityfocus.com, pen-test@securityfocus.com
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Resent-Message-Id: <20070823053549.64C90237FEE@outgoing3.securityfocus.com>
Resent-Date: Wed, 22 Aug 2007 23:35:49 -0600 (MDT)
Resent-From: pen-test-return-1078484941@securityfocus.com
X-pstn-neptune: 10/1/0.10/22
X-pstn-levels: (S:17.66382/99.90000 R:95.9108 P:95.9108 M:97.0282 C:98.6951 )
X-pstn-settings: 3 (1.0000:0.5000) s GT3 gt2 gt1 ft lt r p m c 
X-pstn-addresses: from <prabu@hackinthebox.org> [185/8] 
X-OriginalArrivalTime: 23 Aug 2007 06:09:26.0207 (UTC)
	FILETIME=[287044F0:01C7E54C]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Cc: 
Subject: Reminder: HITBSecConf2007 - Malaysia is less than 2 weeks away
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

HITBSecConf2007 - Malaysia is a mere 2 weeks away! Organized as a
community centric, non-profit effort, HITBSecConf is Asia's largest
network security event featuring 4 keynote speakers, 7 tracks of
technical training sessions and access to over 30 hours of deep
knowledge demos and presentations!

Date: 3rd - 6th September 2007
Venue: Hilton KL Sentral
Time: 0900 - 1800 What's on the menu

- 7 tracks of hands on technical training sessions (3rd & 4th)
- 4 keynote speakers (Mark 'Phiber Optik' Abene, Emmanuel Goldstein,
Mikko Hypponen and Lance Spitzner!)
- Lock Picking Village (run by members of TOOOL USA)
- Capure The Flag (team-based hacking competition with 11 teams from
around the world confirmed)
- BZFlag Area

Some of the highlight conference presentations:

- Hacking Biometric Systems
- High Security Locks - Illusion or Reality?
- How to 0wn Critical National Infrastructure - Hacking SCADA
- RDS-TMC Injection: How to Freak Out Your Sat Nav Systems
- Attacking Cisco NAC
- Hacking Hardened and Secured Oracle Servers

PLUS an exclusive presentation on WABISABILABI - The Exploit Marketplace
Project by their Director of Strategy, who will be taking questions from
the audience and speaking on the purpose of the project and it's future
plans.

Walk in registrants are accepted and the area where the lock picking
village, bzflag competition, zone-h hacking challenge and the capture
the flag 'live hacking' competition is being held is FREE AND OPEN TO
PUBLIC. So do come and check it out. :)

If you haven't registered yet, there's still time to do so but do note
that prices increase after 31st August 2007. For further details, please
see:

http://conference.hitb.org/hitbsecconf2007kl/




------------------------------------------------------------------------
This list is sponsored by: Cenzic

Need to secure your web apps NOW?
Cenzic finds more, "real" vulnerabilities fast.
Click to try it, buy it or download a solution FREE today!

http://www.cenzic.com/downloads
------------------------------------------------------------------------

***********************************************************************
The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized. If you have received this communication in error, please address with the subject heading "Received in error," send to the original sender , then delete the e-mail and destroy any copies of it. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any opinions or advice contained in this e-mail are subject to the terms and conditions expressed in the governing KPMG client engagement letter. Opinions, conclusions and other information in this e-mail and any attachments that do not relate to the official business of the firm are neither given nor endorsed by it.

KPMG cannot guarantee that e-mail communications are secure or error-free, as information could be intercepted, corrupted, amended, lost, destroyed, arrive late or incomplete, or contain viruses. 

This email is being sent out by KPMG International on behalf of the local KPMG member firm providing services to you.  KPMG International is a Swiss cooperative that serves as a coordinating entity for a network of independent firms operating under the KPMG name. KPMG International provides no services to clients. Each member firm of KPMG International is a legally distinct and separate entity and each describes itself as such.  Information about the structure and jurisdiction of your local KPMG member firm can be obtained from your KPMG representative.

This footnote also confirms that this e-mail message has been swept by AntiVirus software. . 
***********************************************************************


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



From ipv6-bounces@ietf.org Sat Aug 25 03:05:40 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IOpft-0004Cj-VX; Sat, 25 Aug 2007 03:03:13 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IOpft-0004Cd-05
	for ipv6@ietf.org; Sat, 25 Aug 2007 03:03:13 -0400
Received: from vgateway.libertyrms.info ([207.219.45.62]
	helo=mail.libertyrms.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IOpfs-0007Hl-Ey
	for ipv6@ietf.org; Sat, 25 Aug 2007 03:03:12 -0400
Received: from vgateway.int.libertyrms.com ([10.1.3.254]
	helo=look.libertyrms.com)
	by mail.libertyrms.com with esmtp (Exim 4.22) id 1IOpfo-0003jI-QR
	for ipv6@ietf.org; Sat, 25 Aug 2007 03:03:08 -0400
Received: from 74.122.168.81 (SquirrelMail authenticated user briand)
	by look.libertyrms.com with HTTP;
	Sat, 25 Aug 2007 03:03:08 -0400 (EDT)
Message-ID: <63886.74.122.168.81.1188025388.squirrel@look.libertyrms.com>
In-Reply-To: <471515FC-E1E1-4C83-99AA-A9821E0C2FF5@muada.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.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>
	<471515FC-E1E1-4C83-99AA-A9821E0C2FF5@muada.com>
Date: Sat, 25 Aug 2007 03:03:08 -0400 (EDT)
From: briand@ca.afilias.info
To: "IETF IPv6 Mailing List" <ipv6@ietf.org>
User-Agent: SquirrelMail/1.4.9a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Exim-Mail-From: briand@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Subject: History of autoconfig RFCs and siblings, please?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

I was attempting to get to the bottom of what is, to me, a mystery:

Why does IPv6 use EUI-64 for Interface Identifiers, instead of MAC-48?

The previous version of the RFCs used MAC-48. There seems to have been,
at some point, some discussion regarding the difference between EUI-48 and
MAC-48, as relate to their use in EUI-64.

And the mailing list archives only go back to some time in 2003, while the
RFCs are 1998 (current) and 1996 (replaced by 1998 versions).

As far as I can tell, synthesis of II's relies on adding a fixed 16-bit
value.

Did we collectively just throw away 16 bits of usable space from our 128,
for no good reason?

That's what it looks like to me...

If someone can explain the rationale, that'd be great.

(I suppose it's a bit late in the game to go back to MAC-48 as II?)

BTW - this isn't just a pedantic question, it bears on the policies that
depend on the autoconfiguration prefix size, for minimum prefix size that
is useable, which relates to address allocation policies by RIRs.

Thanks in advance, to anyone who can shed light on this...

Brian Dickson

P.S. 48 bits of MAC is more than enough, I believe, for a few more
centuries of network growth and device/node assignments... so why we would
jump the gun so soon, appears rather odd to me.


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



From ipv6-bounces@ietf.org Sat Aug 25 03:16:39 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IOpr8-000572-CY; Sat, 25 Aug 2007 03:14:50 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IOpr6-00052A-Gm
	for ipv6@ietf.org; Sat, 25 Aug 2007 03:14:48 -0400
Received: from vgateway.libertyrms.info ([207.219.45.62]
	helo=mail.libertyrms.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IOpr6-0007UD-06
	for ipv6@ietf.org; Sat, 25 Aug 2007 03:14:48 -0400
Received: from vgateway.int.libertyrms.com ([10.1.3.254]
	helo=look.libertyrms.com)
	by mail.libertyrms.com with esmtp (Exim 4.22) id 1IOpr5-00047X-Jl
	for ipv6@ietf.org; Sat, 25 Aug 2007 03:14:47 -0400
Received: from 74.122.168.81 (SquirrelMail authenticated user briand)
	by look.libertyrms.com with HTTP;
	Sat, 25 Aug 2007 03:14:47 -0400 (EDT)
Message-ID: <63903.74.122.168.81.1188026087.squirrel@look.libertyrms.com>
Date: Sat, 25 Aug 2007 03:14:47 -0400 (EDT)
From: briand@ca.afilias.info
To: "IPV6 Mailing List" <ipv6@ietf.org>
User-Agent: SquirrelMail/1.4.9a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Exim-Mail-From: briand@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Subject: Straw poll: autoconf vs manual conf
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

(I realize this list might not represent the bulk of the deployed IPv6
networks... nonetheless, I'm curious.)

This is an informal survey of what is deployed in terms of IPv6 networks.
Do you use autoconf only, static assignments only, or a mix?

Any additional info about what, why, etc., would be interesting.

Please include one of the lines:
straw poll: mix
straw poll: auto
straw poll: static

And if you want to give more details:
auto prefix count: <N>
static prefix count: <N>
overlap-mix count: <N> (for subnets that combine hosts doing autoconf with
hosts statically configured)

Reply directly to me, not the list, and I will summarize.

Please preface your remarks with "Confidential" if you *don't* want them
included in the summary, i.e. if they are meant only for me. :-)

Thanks,

Brian Dickson

P.S. This is to gauge the trade-off between deployed *code* and deployed
*networks* is, when considering changes to core IPv6 RFCs.

P.P.S. The original author of the unix "make" utility, knew of a bug, but
didn't fix it because of the installed user base - seven people. He later
apologized for that decision, which caused grief for hundreds of thousands
of developers over the last several decades.


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



From ipv6-bounces@ietf.org Sat Aug 25 08:48:23 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IOv1h-0004EL-C7; Sat, 25 Aug 2007 08:46:05 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IOv1g-0004EG-6I
	for ipv6@ietf.org; Sat, 25 Aug 2007 08:46:04 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IOv1f-0000gb-J0
	for ipv6@ietf.org; Sat, 25 Aug 2007 08:46:03 -0400
Received: from [IPv6:2001:1af8:6::20a:95ff:fecd:987a]
	([IPv6:2001:1af8:6:0:20a:95ff:fecd:987a]) (authenticated bits=0)
	by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id l7PChdgF005836
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Sat, 25 Aug 2007 14:43:39 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <63903.74.122.168.81.1188026087.squirrel@look.libertyrms.com>
References: <63903.74.122.168.81.1188026087.squirrel@look.libertyrms.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <4E0906FC-3C21-49D9-84F9-150EC240D7E3@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Sat, 25 Aug 2007 14:45:59 +0200
To: briand@ca.afilias.info
X-Mailer: Apple Mail (2.752.2)
X-Spam-Status: No, score=-2.2 required=3.5 tests=AWL,BAYES_00 autolearn=ham 
	version=3.0.2
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on sequoia.muada.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Cc: IPV6 Mailing List <ipv6@ietf.org>
Subject: Re: Straw poll: autoconf vs manual conf
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 25-aug-2007, at 9:14, briand@ca.afilias.info wrote:

> This is an informal survey of what is deployed in terms of IPv6  
> networks.
> Do you use autoconf only, static assignments only, or a mix?

On routers or hosts, and why?

> Please include one of the lines:
> straw poll: mix
> straw poll: auto
> straw poll: static

Does this count as auto, static or mix?

!
interface Ethernet0
  ipv6 address 2001:1AF8:6::/64 eui-64
!


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



From ipv6-bounces@ietf.org Sat Aug 25 20:02:24 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IP5Xy-0000hs-Fn; Sat, 25 Aug 2007 20:00:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IP5Xx-0000hn-Sh
	for ipv6@ietf.org; Sat, 25 Aug 2007 20:00:05 -0400
Received: from [2002:421e:11a9:0:210:5aff:fe86:1f54] (helo=cyteen.hactrn.net)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IP5Xx-0004nA-76
	for ipv6@ietf.org; Sat, 25 Aug 2007 20:00:05 -0400
Received: from cyteen.hactrn.net (localhost [127.0.0.1])
	by cyteen.hactrn.net (Postfix) with ESMTP id BFCD228452
	for <ipv6@ietf.org>; Sun, 26 Aug 2007 00:00:04 +0000 (UTC)
To: ipv6@ietf.org
From: Rob Austein <sra+ipng@hactrn.net>
Date: Sun, 26 Aug 2007 00:00:04 +0000
Message-Id: <20070826000004.BFCD228452@cyteen.hactrn.net>
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Subject: Weekly posting summary for ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.57% |    6 |  7.76% |    29256 | jari.arkko@piuha.net
  7.14% |    5 |  7.51% |    28338 | iljitsch@muada.com
  5.71% |    4 |  5.46% |    20581 | suresh.krishnan@ericsson.com
  4.29% |    3 |  5.01% |    18909 | volz@cisco.com
  4.29% |    3 |  4.99% |    18828 | james.d.carlson@sun.com
  4.29% |    3 |  4.68% |    17632 | rdroms@cisco.com
  2.86% |    2 |  5.38% |    20277 | shemant@cisco.com
  4.29% |    3 |  3.89% |    14682 | bob.hinden@nokia.com
  4.29% |    3 |  3.87% |    14606 | jinmei@isl.rdc.toshiba.co.jp
  2.86% |    2 |  3.85% |    14504 | alain_durand@cable.comcast.com
  2.86% |    2 |  3.23% |    12181 | tjc@ecs.soton.ac.uk
  2.86% |    2 |  2.94% |    11092 | brian@innovationslab.net
  2.86% |    2 |  2.91% |    10974 | jhw@apple.com
  2.86% |    2 |  2.80% |    10555 | briand@ca.afilias.info
  2.86% |    2 |  2.62% |     9897 | mohta@necom830.hpcl.titech.ac.jp
  2.86% |    2 |  2.59% |     9781 | msa@moth.iki.fi
  2.86% |    2 |  2.25% |     8495 | ignatios@cs.uni-bonn.de
  2.86% |    2 |  1.92% |     7231 | dwmalone@maths.tcd.ie
  2.86% |    2 |  1.92% |     7226 | itojun@itojun.org
  1.43% |    1 |  2.05% |     7712 | shane_kerr@isc.org
  1.43% |    1 |  1.74% |     6557 | basavaraj.patil@nsn.com
  1.43% |    1 |  1.59% |     5992 | julien.ietf@laposte.net
  1.43% |    1 |  1.57% |     5918 | timbeck04@verizon.net
  1.43% |    1 |  1.51% |     5684 | vishwas.ietf@gmail.com
  1.43% |    1 |  1.49% |     5636 | ipng@69706e6720323030352d30312d31340a.nosense.org
  1.43% |    1 |  1.45% |     5481 | prabu@hackinthebox.org
  1.43% |    1 |  1.36% |     5117 | sra+ipng@hactrn.net
  1.43% |    1 |  1.35% |     5086 | jabley@ca.afilias.info
  1.43% |    1 |  1.33% |     5031 | brian.e.carpenter@gmail.com
  1.43% |    1 |  1.32% |     4992 | david_hankins@isc.org
  1.43% |    1 |  1.25% |     4695 | mcbride@openbsd.org
  1.43% |    1 |  1.19% |     4506 | narten@us.ibm.com
  1.43% |    1 |  1.19% |     4486 | andrew@ca.afilias.info
  1.43% |    1 |  1.08% |     4085 | gnn@neville-neil.com
  1.43% |    1 |  1.07% |     4053 | olaf.bonness@t-systems.com
  1.43% |    1 |  1.06% |     3987 | hideshi.enokihara@jp.yokogawa.com
  1.43% |    1 |  0.81% |     3042 | poledg@mx1.ibm.com
--------+------+--------+----------+------------------------
100.00% |   70 |100.00% |   377105 | Total

Grunchweather Associates provides this automatic summary on an at-whim
basis at the request of the IPv6 WG chairs.  Your mileage may vary.
We decline responsibilities, all shapes, all sizes, all colors.
If this script produces broken output, you get to keep both pieces.

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



From ipv6-bounces@ietf.org Mon Aug 27 11:07:22 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPg9M-0007wN-OE; Mon, 27 Aug 2007 11:05:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPg9L-0007sO-1r
	for ipv6@ietf.org; Mon, 27 Aug 2007 11:05:07 -0400
Received: from omzesmtp03.mci.com ([199.249.17.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IPg9J-0003Oz-Nm
	for ipv6@ietf.org; Mon, 27 Aug 2007 11:05:07 -0400
Received: from pmismtp06.wcomnet.com ([166.37.158.166])
	by firewall.verizonbusiness.com (Iplanet MTA 5.2)
	with ESMTP id <0JNF00A8TTWGCV@firewall.verizonbusiness.com> for
	ipv6@ietf.org; Mon, 27 Aug 2007 15:05:05 +0000 (GMT)
Received: from pmismtp06.wcomnet.com ([127.0.0.1])
	by pmismtp06.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08
	(built Sep
	22 2005)) with SMTP id <0JNF00MFITWGLL@pmismtp06.mcilink.com> for
	ipv6@ietf.org; Mon, 27 Aug 2007 15:05:05 +0000 (GMT)
Received: from meno.corp.us.uu.net ([153.39.146.71])
	by pmismtp06.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08
	(built Sep
	22 2005)) with ESMTP id <0JNF00LB1TWGWX@pmismtp06.mcilink.com> for
	ipv6@ietf.org; Mon, 27 Aug 2007 15:05:04 +0000 (GMT)
Date: Mon, 27 Aug 2007 11:05:04 -0400 (EDT)
From: Jason Schiller <schiller@uu.net>
In-reply-to: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
X-Sender: schiller@meno.corp.us.uu.net
To: Bob Hinden <bob.hinden@nokia.com>
Message-id: <Pine.GSO.4.20.0708271100050.6917-100000@meno.corp.us.uu.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Mon, 20 Aug 2007, Bob Hinden wrote:

> We would like to get your comments on the following two choices:
> 
> 1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate-rh0-01.txt>.
> 
> 2) Revising the draft to restrict the usage of RH0.  This would  
> continue to require RH0 to be implemented but would restrict the  
> functionality of RH0.  For example, require nodes to have support for  
> RH0 turned off by default, limit the number of RH0 headers in a  
> packet to one, limit the number of addresses in the RH0 to a smaller  
> number (e.g., 6), and and a requirement that addresses can only be in  
> the header once.
> 
I am in favor of option 2.

With regard to RH0 and source routing in general I do not believe the best
approach is to deprecate this functionality.  

Feature parity between IPv4 and IPv6 is important to ease transition and
transition concerns.  I wonder how much support there would be to
deprecate IPv4 source routing.  

Also, if source routing in some sort of new and limited form turns out to
be useful, RHx could be specified and implemented in new extension header,
but the same is not true for IPv4.

I do concede on the point that almost no one uses it.  As a transit
provider, we have disabled IPv4 source routing.  We have done this to
protect our network.  We don't want our routers to do expensive software
based forwarding decisions.  We don't want to allow customers dictating
traffic engineering decisions within our network.   Unfortunately, our
only recourse is to turn off source routing and drop all packets that have
any source routing options.

It would be better if we had the capabilities to ignore source routing
options.  This way each network could make its own security decisions
instead of the transit ISPs acting like a firewall for the Internet and
deciding what traffic is good for the Internet.

How would ignoring source routing work?
------------------------------------------------------
Routers could be configured with one of three options:
1. drop all packets with source routing options. Current 
   "no-source-route" or "no ip source-route"
2. ignore source routing.  Use standard forwarding if the destination is
   not the local router.  If the destination is the local router discard
   the packet.
3. honor source routing.

This would allow for a given network to protect itself and not be used for
source routing, but would not prevent network beyond your network from
honoring source routing.  For example take customers A, B and C who are
connected to ISP1.  ISP1 does not want their routers to be used as a
source routed node, so they configure ignore-source-route. 

Customer A and customer B as two consenting adults may decide to support
source routing.  This could allow customer A to source a packet that will
be source routed inside customer B's network.  Since the packet does not
have a destination of a router in ISP1's network it will just transit ISP1
like any normal traffic.  When it reaches customer B, since they support
source routing, the traffic will be source routed.

Customer C may configure no-source routing.  Customer A may send packets
that are to be source routed inside customer C's network.  In this case
the ISP1 will transit the traffic to customer C's network where it will
get dropped.

Customer A may try to source route a packet in the middle of ISP1's
network.  In this case ISP1 will carry the traffic to the middle of the
network, where the router that is the next hop destination will discard
the traffic.

__Jason


==========================================================================
Jason Schiller                                               (703)886.6648
Senior Internet Network Engineer                         fax:(703)886.0512
Public IP Global Network Engineering                       schiller@uu.net
UUNET / Verizon                         jason.schiller@verizonbusiness.com

The good news about having an email address that is twice as long is that
it increases traffic on the Internet.



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



From ipv6-bounces@ietf.org Mon Aug 27 11:16:25 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPgIO-00045h-BU; Mon, 27 Aug 2007 11:14:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPgIL-00045b-Vp
	for ipv6@ietf.org; Mon, 27 Aug 2007 11:14:25 -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 1IPgIL-0003jS-FQ
	for ipv6@ietf.org; Mon, 27 Aug 2007 11:14:25 -0400
Received: by coconut.itojun.org (Postfix, from userid 501)
	id 0DBA9233E9; Tue, 28 Aug 2007 00:14:23 +0900 (JST)
To: schiller@uu.net
In-Reply-To: Your message of "Mon, 27 Aug 2007 11:05:04 -0400 (EDT)"
	<Pine.GSO.4.20.0708271100050.6917-100000@meno.corp.us.uu.net>
References: <Pine.GSO.4.20.0708271100050.6917-100000@meno.corp.us.uu.net>
X-Mailer: Cue version 0.8 (070521-1856/itojun)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20070827151423.0DBA9233E9@coconut.itojun.org>
Date: Tue, 28 Aug 2007 00:14:23 +0900 (JST)
From: itojun@itojun.org (Jun-ichiro itojun Hagino)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: ipv6@ietf.org
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> > We would like to get your comments on the following two choices:
> > 
> > 1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate-rh0-01.txt>.
> > 
> > 2) Revising the draft to restrict the usage of RH0.  This would  
> > continue to require RH0 to be implemented but would restrict the  
> > functionality of RH0.  For example, require nodes to have support for  
> > RH0 turned off by default, limit the number of RH0 headers in a  
> > packet to one, limit the number of addresses in the RH0 to a smaller  
> > number (e.g., 6), and and a requirement that addresses can only be in  
> > the header once.
> > 
> I am in favor of option 2.
> 
> With regard to RH0 and source routing in general I do not believe the best
> approach is to deprecate this functionality.  
> 
> Feature parity between IPv4 and IPv6 is important to ease transition and
> transition concerns.  I wonder how much support there would be to
> deprecate IPv4 source routing.  
> 
> Also, if source routing in some sort of new and limited form turns out to
> be useful, RHx could be specified and implemented in new extension header,
> but the same is not true for IPv4.

	see the text carefully.  (1) says "deprecate *RH0*", (2) says
	"restrict the usage of *RH0*".  it is not about RHx.  will your
	choice change because of this?

	and for what it's worth, IPv4 options entirely deprecated in reality.
	packets with any IPv4 options could not go through JP-US link at least
	since 1992 or so.  therefore, IPv4 equivalent of RH0 has been dead
	for 15 years.

	i'm, of course, in favor of (1), and the document has to be shipped
	as soon as possible.  there are huge vendors which holding up the
	release of security advisory until RFC gets published!

itojun

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



From ipv6-bounces@ietf.org Mon Aug 27 12:33:52 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPhVG-0007Z6-1R; Mon, 27 Aug 2007 12:31:50 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPhVE-0007Z1-Fb
	for ipv6@ietf.org; Mon, 27 Aug 2007 12:31:48 -0400
Received: from vms044pub.verizon.net ([206.46.252.44])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IPhVE-0001Kw-01
	for ipv6@ietf.org; Mon, 27 Aug 2007 12:31:48 -0400
Received: from vms229.mailsrvcs.net ([192.168.1.2])
	by vms044.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01
	(built Apr
	3 2006)) with ESMTPA id <0JNF00ANBXSYDKI0@vms044.mailsrvcs.net> for
	ipv6@ietf.org; Mon, 27 Aug 2007 11:29:22 -0500 (CDT)
Received: from 129.55.200.20 ([129.55.200.20])
	by vms229.mailsrvcs.net (Verizon Webmail) with HTTP; Mon,
	27 Aug 2007 11:29:22 -0500 (CDT)
Date: Mon, 27 Aug 2007 11:29:22 -0500 (CDT)
From: Tim Enos <timbeck04@verizon.net>
X-Originating-IP: [129.55.200.20]
To: schiller@uu.net, Jun-ichiro itojun Hagino <itojun@itojun.org>
Message-id: <17370393.16676601188232162400.JavaMail.root@vms229.mailsrvcs.net>
MIME-version: 1.0
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: ipv6@ietf.org
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


>> > We would like to get your comments on the following two choices:
>> > 
>> > 1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate-rh0-01.txt>.
>> > 
>> > 2) Revising the draft to restrict the usage of RH0.  This would  
>> > continue to require RH0 to be implemented but would restrict the  
>> > functionality of RH0.  For example, require nodes to have support for  
>> > RH0 turned off by default, limit the number of RH0 headers in a  
>> > packet to one, limit the number of addresses in the RH0 to a smaller  
>> > number (e.g., 6), and and a requirement that addresses can only be in  
>> > the header once.
>> > 
>> I am in favor of option 2.
>> 
>> With regard to RH0 and source routing in general I do not believe the best
>> approach is to deprecate this functionality.  
>> 
>> Feature parity between IPv4 and IPv6 is important to ease transition and
>> transition concerns.  I wonder how much support there would be to
>> deprecate IPv4 source routing.  
>> 
>> Also, if source routing in some sort of new and limited form turns out to
>> be useful, RHx could be specified and implemented in new extension header,
>> but the same is not true for IPv4.
>
> see the text carefully.  (1) says "deprecate *RH0*", (2) says "restrict the usage of *RH0*". 

> It is not about RHx. Will your choice change because of this?

Exactly. It (option (1), adopting the draft) is not about RHx. Strictly speaking it isn't about firewall policy either. It's merely about deprecating RH0.

RHx providing similar functionality to that of RH0 could be addressed in another draft (might be already?)

Also FWIW, I'm not sure if there's a more comprehensive treatment of IPv6 firewall policy (that has made it to RFC form). RFC 4890 recommends how to handle filtering of ICMPv6 packets. Perhaps a similar RFC could be written to address RHx (excluding type 0 of course).

>
> and for what it's worth, IPv4 options entirely deprecated in reality.
> packets with any IPv4 options could not go through JP-US link at least since 1992 or so.  therefore, IPv4 equivalent of RH0 has been dead	for 15 years.
>

Good point. This would be true even in the face of a company on the JP side and a company on the US side (of the JP-US link) agreed together to accept source-routed traffic from each other.

Just having the RH0 traffic transit the intervening ISP(s) would make the link susceptible to the attacks outlined in the draft.

> i'm, of course, in favor of (1), and the document has to be shipped as soon as possible.

I'm still also in favor of (1).

> there are huge vendors which holding up the release of security advisory until RFC gets published!
>

Here's a recent security advisory from one such huge vendor:

http://www.cisco.com/warp/public/707/cisco-sa-20070808-IOS-IPv6-leak.shtml

> itojun
>

Best Regards,

Tim Enos
Rom 8:28

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



From ipv6-bounces@ietf.org Mon Aug 27 13:11:06 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPi58-0003mw-P2; Mon, 27 Aug 2007 13:08:54 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPi57-0003mr-VF
	for ipv6@ietf.org; Mon, 27 Aug 2007 13:08:53 -0400
Received: from vgateway.libertyrms.info ([207.219.45.62]
	helo=mail.libertyrms.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IPi57-0002ay-KZ
	for ipv6@ietf.org; Mon, 27 Aug 2007 13:08:53 -0400
Received: from vgateway.int.libertyrms.com ([10.1.3.254]
	helo=look.libertyrms.com)
	by mail.libertyrms.com with esmtp (Exim 4.22)
	id 1IPi56-0004aG-WE; Mon, 27 Aug 2007 13:08:53 -0400
Received: from 74.122.168.81 (SquirrelMail authenticated user briand)
	by look.libertyrms.com with HTTP;
	Mon, 27 Aug 2007 13:08:53 -0400 (EDT)
Message-ID: <60279.74.122.168.81.1188234533.squirrel@look.libertyrms.com>
In-Reply-To: <20070820205120.GA3315@dba3>
References: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
	<20070820205120.GA3315@dba3>
Date: Mon, 27 Aug 2007 13:08:53 -0400 (EDT)
From: briand@ca.afilias.info
To: "Andrew Sullivan" <andrew@ca.afilias.info>
User-Agent: SquirrelMail/1.4.9a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Exim-Mail-From: briand@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: ipv6@ietf.org
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> On Mon, Aug 20, 2007 at 01:43:19PM -0700, Bob Hinden wrote:
>> 1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate-rh0-01.txt>.
>
> I support this option, because it seems to me that the existing draft
> makes the correct point: another rh[n] could be introduced to add the
> desired features without exposing the same vulnerability.  Given that
> the deployment so far is not extensive (compared to other things on
> the Internet), it seems like this is the safest thing to do.  I have
> read the alternative arguments; some of them seem to me to be
> reasonably good second choices, and if we had evidence of much wider
> use of RH0 today, I would probably be more persuaded by those
> arguments.

Ditto.

Brian Dickson
Afilias


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



From ipv6-bounces@ietf.org Mon Aug 27 14:10:59 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPj1J-0004MX-C1; Mon, 27 Aug 2007 14:09:01 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPj1H-0004M7-GD
	for ipv6@ietf.org; Mon, 27 Aug 2007 14:08:59 -0400
Received: from omzesmtp04.mci.com ([199.249.17.14])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IPj1G-0004TX-Ty
	for ipv6@ietf.org; Mon, 27 Aug 2007 14:08:59 -0400
Received: from dgismtp01.wcomnet.com ([166.38.58.141])
	by firewall.verizonbusiness.com (Iplanet MTA 5.2)
	with ESMTP id <0JNG00A9Z2EYCS@firewall.verizonbusiness.com> for
	ipv6@ietf.org; Mon, 27 Aug 2007 18:08:58 +0000 (GMT)
Received: from dgismtp01.wcomnet.com ([127.0.0.1])
	by dgismtp01.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08
	(built Sep
	22 2005)) with SMTP id <0JNG00HRY2EY81@dgismtp01.mcilink.com> for
	ipv6@ietf.org; Mon, 27 Aug 2007 18:08:58 +0000 (GMT)
Received: from meno.corp.us.uu.net ([153.39.146.71])
	by dgismtp01.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08
	(built Sep
	22 2005)) with ESMTP id <0JNG00H6W2EXQ1@dgismtp01.mcilink.com> for
	ipv6@ietf.org; Mon, 27 Aug 2007 18:08:58 +0000 (GMT)
Date: Mon, 27 Aug 2007 14:08:56 -0400 (EDT)
From: Jason Schiller <schiller@uu.net>
In-reply-to: <20070827151423.0DBA9233E9@coconut.itojun.org>
X-Sender: schiller@meno.corp.us.uu.net
To: Jun-ichiro itojun Hagino <itojun@itojun.org>
Message-id: <Pine.GSO.4.20.0708271348200.6917-100000@meno.corp.us.uu.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: ipv6@ietf.org, jason.schiller@verizonbusiness.com
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Tue, 28 Aug 2007, Jun-ichiro itojun Hagino wrote:

> > > 1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate-rh0-01.txt>.
> > > 
> > > 2) Revising the draft to restrict the usage of RH0.  This would  
> > > continue to require RH0 to be implemented but would restrict the  
> > > functionality of RH0.  For example, require nodes to have support for  
> > > RH0 turned off by default, limit the number of RH0 headers in a  
> > > packet to one, limit the number of addresses in the RH0 to a smaller  
> > > number (e.g., 6), and and a requirement that addresses can only be in  
> > > the header once.
> > > 
> > I am in favor of option 2.
> > 
> > With regard to RH0 and source routing in general I do not believe the best
> > approach is to deprecate this functionality.  
> > 
> > Feature parity between IPv4 and IPv6 is important to ease transition and
> > transition concerns.  I wonder how much support there would be to
> > deprecate IPv4 source routing.  
> > 
> > Also, if source routing in some sort of new and limited form turns out to
> > be useful, RHx could be specified and implemented in new extension header,
> > but the same is not true for IPv4.
> 
> 	see the text carefully.  (1) says "deprecate *RH0*", (2) says
> 	"restrict the usage of *RH0*".  it is not about RHx.  will your
> 	choice change because of this?

I am quite aware that choice 1 is Deprecate RH0 and choice 2 is restrict
usage of RH0, and neither relates to RHx.

I think maybe you are missing my point.  It relates to a more general
discussion of source routing and feature parity in IPv4 and IPv6.  If you
are going to deprecate IPv6 source routing, then you should also deprecate
IPv4 source routing.  If you think that maybe IPv6 source routing is
useful, especially in a more limited fashion, then that can easily be
defined in another IPv6 RHx extension header.  But the problem is much
more complicated if you want feature parity with IPv4 as you would need to
modify the IPv4 header.

For this reason I would prefer greater control over how to deal with
source routed packets (IPv4 and IPv6).  I am not opposed to changing the
defaults (in both IPv4 and IPv6) to prevent source routing.  I think it
would be good to require all vendors to support a single config bit to
prevent source routing.  

But if we are going to re-think source routing, I think there are better
options then either supporting source routing, or discarding all packets
with a source routing option.

> 
> 	and for what it's worth, IPv4 options entirely deprecated in reality.
> 	packets with any IPv4 options could not go through JP-US link at least
> 	since 1992 or so.  therefore, IPv4 equivalent of RH0 has been dead
> 	for 15 years.

Again, some people seem to think source routing is useful, other are
afraid of the security risks.  Each network operator will act in their own
best interest.  Currently the only options are either allow your devices
to perform source routing, or drop all packets that are transiting the
network with source routing options.

There is middle ground here.  Allow routers to be configured such that
they can ignore source routed packets that are not destined to the local
router.  This will allow routers to forward source routed packets in the
normal way without an impact on software based forwarding.  This will
allow an operator to secure their own network and not allow their network
to be used for source routing, while not preventing networks that are
reached through them to use source routing if they so desire.  This way
everyone can decide for themselves if they want to support source routing
unlike currently where all of the transit providers have made the decesion
on behalf of their customers.
 
>
> 	i'm, of course, in favor of (1), and the document has to be shipped
> 	as soon as possible.  there are huge vendors which holding up the
> 	release of security advisory until RFC gets published!
> 
> itojun

I am still in favor of choice 2.  

I would be curious how people feel about these choices if they also apply
to (as they should) IPv4 source routing.

__Jason


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



From ipv6-bounces@ietf.org Mon Aug 27 14:25:22 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPjFF-0000yB-9x; Mon, 27 Aug 2007 14:23:25 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPjFD-0000y6-GX
	for ipv6@ietf.org; Mon, 27 Aug 2007 14:23:23 -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 1IPjFC-0000jb-Vk
	for ipv6@ietf.org; Mon, 27 Aug 2007 14:23:23 -0400
Received: from coconut.itojun.org (localhost.itojun.org [127.0.0.1])
	by coconut.itojun.org (Postfix) with ESMTP id A4C0C233E8;
	Tue, 28 Aug 2007 03:23:19 +0900 (JST)
To: Jason Schiller <schiller@uu.net>
In-reply-to: schiller's message of Mon, 27 Aug 2007 14:08:56 -0400.
	<Pine.GSO.4.20.0708271348200.6917-100000@meno.corp.us.uu.net> 
X-Template-Reply-To: itojun@itojun.org
X-Template-Return-Receipt-To: itojun@itojun.org
X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD  90 5F B4 60 79 54 16 E2
From: Jun-ichiro itojun Hagino <itojun@itojun.org>
Date: Tue, 28 Aug 2007 03:23:19 +0900
Message-Id: <20070827182319.A4C0C233E8@coconut.itojun.org>
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: ipv6@ietf.org
Subject: Re: New Consensus call on RH0 Deprecation 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

>> 	see the text carefully.  (1) says "deprecate *RH0*", (2) says
>> 	"restrict the usage of *RH0*".  it is not about RHx.  will your
>> 	choice change because of this?
>
>I am quite aware that choice 1 is Deprecate RH0 and choice 2 is restrict
>usage of RH0, and neither relates to RHx.
>
>I think maybe you are missing my point.  It relates to a more general
>discussion of source routing and feature parity in IPv4 and IPv6.  If you
(snip)

	ok, i assume you have not seen this.  http://www.natisbad.org/.

	the key topic being discussed here with the draft is URGENT need to
	publish the deprecation/restriction of RH0.

	please refrain from generalizing the problem, until RH0 RFC goes
	out of the door.  we can handle your generic opinions about the
	source routing in general some other time.

	again, it is about rather serious security problem, which risked
	the DNS root name servers.  it's quite serious and really urgent.
	the RFC publication should have finished way earlier.

itojun

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



From ipv6-bounces@ietf.org Mon Aug 27 14:28:53 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPjIs-0002Yo-7T; Mon, 27 Aug 2007 14:27:10 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPjIr-0002Yf-5p
	for ipv6@ietf.org; Mon, 27 Aug 2007 14:27:09 -0400
Received: from mail-out3.apple.com ([17.254.13.22])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IPjIq-0004zu-R5
	for ipv6@ietf.org; Mon, 27 Aug 2007 14:27:09 -0400
Received: from relay14.apple.com (relay14.apple.com [17.128.113.52])
	by mail-out3.apple.com (Postfix) with ESMTP id F0354F91630
	for <ipv6@ietf.org>; Mon, 27 Aug 2007 11:27:07 -0700 (PDT)
Received: from relay14.apple.com (unknown [127.0.0.1])
	by relay14.apple.com (Symantec Mail Security) with ESMTP id 482D928470
	for <ipv6@ietf.org>; Mon, 27 Aug 2007 11:26:33 -0700 (PDT)
X-AuditID: 11807134-a2b65bb0000066ad-a6-46d317599934
Received: from [17.206.23.199] (il0602a-dhcp71.apple.com [17.206.23.199])
	by relay14.apple.com (Symantec Mail Security) with ESMTP id 31CCD28528
	for <ipv6@ietf.org>; Mon, 27 Aug 2007 11:26:33 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <Pine.GSO.4.20.0708271348200.6917-100000@meno.corp.us.uu.net>
References: <Pine.GSO.4.20.0708271348200.6917-100000@meno.corp.us.uu.net>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <927504B0-52FB-49BB-B5EB-190F95D476F6@apple.com>
Content-Transfer-Encoding: 7bit
From: james woodyatt <jhw@apple.com>
Date: Mon, 27 Aug 2007 11:26:18 -0700
To: IETF IPv6 Mailing List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Aug 27, 2007, at 11:08, Jason Schiller wrote:
>
> I would be curious how people feel about these choices if they also  
> apply to (as they should) IPv4 source routing.

I was unaware until just now that IPv4 source routing had *not* been  
deprecated by IETF already.  I must have been misinformed about  
that.  It's certainly not viewed with any favor among the circles  
I've been in most recently.


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



From ipv6-bounces@ietf.org Mon Aug 27 14:29:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPjJs-0003Ud-1L; Mon, 27 Aug 2007 14:28:12 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPjJq-0003Ta-Ej
	for ipv6@ietf.org; Mon, 27 Aug 2007 14:28:10 -0400
Received: from smtp167.iad.emailsrvr.com ([207.97.245.167])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IPjJq-00053E-2c
	for ipv6@ietf.org; Mon, 27 Aug 2007 14:28:10 -0400
Received: by relay6.relay.iad.emailsrvr.com (Authenticated sender:
	dow.street-AT-linquest.com) with ESMTP id 777206A9985; 
	Mon, 27 Aug 2007 14:28:07 -0400 (EDT)
In-Reply-To: <17370393.16676601188232162400.JavaMail.root@vms229.mailsrvcs.net>
References: <17370393.16676601188232162400.JavaMail.root@vms229.mailsrvcs.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <3B2D1D17-2272-4E3E-A557-99CA50488D6E@linquest.com>
Content-Transfer-Encoding: 7bit
From: Dow Street <dow.street@linquest.com>
Date: Mon, 27 Aug 2007 11:27:54 -0700
To: Tim Enos <timbeck04@verizon.net>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: ipv6@ietf.org
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Aug 27, 2007, at 9:29 AM, Tim Enos wrote:

> Good point. This would be true even in the face of a company on the  
> JP side and a company on the US side (of the JP-US link) agreed  
> together to accept source-routed traffic from each other.
>
> Just having the RH0 traffic transit the intervening ISP(s) would  
> make the link susceptible to the attacks outlined in the draft.

Can you (and others) clarify your position on what you consider to be  
valid traffic?  I do not work for a commercial ISP, so I'm trying to  
understand the current thinking / policy on this.

Suppose you have 4 providers, where A and B are in the US and C and D  
are in Japan (the B -- C link is the US-JP link).

A - B - - C - D

Assume A and D are interested in supporting source routing, but B and  
C are not.  Further assume that, due to A and D's support for source  
routing, they are susceptible to the kind of oscillation DOS attack  
we have been discussing.  The B - - C link is managed / protected by  
B and C - that is, they have ultimate control over what traffic  
transits this US - JP link.

In the event of an oscillation DOS attack between A and D, do B and C  
care that the traffic they are transiting is DOS traffic vs. other  
traffic?  In other words, hasn't the capacity available to A (from B)  
and the capacity available to D (from C) already been arranged?  If  
this capacity is consumed due to DOS, is it not A and D (and their  
customers) who pay the cost?

This is not to say we shouldn't think about the global aspects of  
resource use and DOS - I'm just trying to understand whether the  
approach to source routing requires a global consensus.  Several  
recent comments seem to imply that it is unacceptable even to transit  
RH0 traffic (rather than simply choose not to act on RH0 headers) -  
have I interpreted this position correctly?  If so, it would seem to  
have implications for both RH0 (as is being discussed) and any new  
source routing approach RHx.

Is DOS protection / mitigation an assumed (or explicit) service  
provided by ISPs to customers?

Thanks,
Dow



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



From ipv6-bounces@ietf.org Mon Aug 27 14:46:17 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPjZP-0003Z1-RM; Mon, 27 Aug 2007 14:44:15 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPjZO-0003Tq-IZ
	for ipv6@ietf.org; Mon, 27 Aug 2007 14:44:14 -0400
Received: from vgateway.libertyrms.info ([207.219.45.62]
	helo=mail.libertyrms.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IPjZN-0005YM-Q1
	for ipv6@ietf.org; Mon, 27 Aug 2007 14:44:14 -0400
Received: from vgateway.int.libertyrms.com ([10.1.3.254]
	helo=look.libertyrms.com)
	by mail.libertyrms.com with esmtp (Exim 4.22)
	id 1IPjZL-0008Rb-6s; Mon, 27 Aug 2007 14:44:11 -0400
Received: from 74.122.168.81 (SquirrelMail authenticated user briand)
	by look.libertyrms.com with HTTP;
	Mon, 27 Aug 2007 14:44:11 -0400 (EDT)
Message-ID: <60580.74.122.168.81.1188240251.squirrel@look.libertyrms.com>
In-Reply-To: <3B2D1D17-2272-4E3E-A557-99CA50488D6E@linquest.com>
References: <17370393.16676601188232162400.JavaMail.root@vms229.mailsrvcs.net>
	<3B2D1D17-2272-4E3E-A557-99CA50488D6E@linquest.com>
Date: Mon, 27 Aug 2007 14:44:11 -0400 (EDT)
From: briand@ca.afilias.info
To: "Dow Street" <dow.street@linquest.com>
User-Agent: SquirrelMail/1.4.9a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Exim-Mail-From: briand@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: ipv6@ietf.org
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> On Aug 27, 2007, at 9:29 AM, Tim Enos wrote:
>
>> Good point. This would be true even in the face of a company on the
>> JP side and a company on the US side (of the JP-US link) agreed
>> together to accept source-routed traffic from each other.
>>
>> Just having the RH0 traffic transit the intervening ISP(s) would
>> make the link susceptible to the attacks outlined in the draft.
>
> Can you (and others) clarify your position on what you consider to be
> valid traffic?  I do not work for a commercial ISP, so I'm trying to
> understand the current thinking / policy on this.

I have, in the past, handed just such situations and the planning/costing
and billing-model stuff, and can address your questions with a great
level of certainty and authority. If I sound like a know-it-all in this
area, it's because, well, I am. :-)

> Suppose you have 4 providers, where A and B are in the US and C and D
> are in Japan (the B -- C link is the US-JP link).
>
> A - B - - C - D
>
> Assume A and D are interested in supporting source routing, but B and
> C are not.  Further assume that, due to A and D's support for source
> routing, they are susceptible to the kind of oscillation DOS attack
> we have been discussing.  The B - - C link is managed / protected by
> B and C - that is, they have ultimate control over what traffic
> transits this US - JP link.
>
> In the event of an oscillation DOS attack between A and D, do B and C
> care that the traffic they are transiting is DOS traffic vs. other
> traffic?  In other words, hasn't the capacity available to A (from B)
> and the capacity available to D (from C) already been arranged?  If
> this capacity is consumed due to DOS, is it not A and D (and their
> customers) who pay the cost?

Absolutely not. The pricing/billing model on transit ISPs, involves some
presumptions and/or projections on usage patterns. The transit providers,
in this case B and C, need to ensure peak usage is covered by their
capacity. And they bill their customers, A and D, based on the observed
patterns of the aggregates of their customer base, and on A and D in
particular.

DOS breaks the trends, and exceeds the limits of the billing model, by
any of several methods. Bottom line is, when traffic is DOS, the cost
exceeds revenue, since all capacity *on the transit upstream* is eaten.

Traffic that exceeds the link capacity on the respective tail sections,
A-B and C-D, that crosses B-C, is traffic that must be discarded, has costs,
but generates *no* revenue.

> This is not to say we shouldn't think about the global aspects of
> resource use and DOS - I'm just trying to understand whether the
> approach to source routing requires a global consensus.  Several
> recent comments seem to imply that it is unacceptable even to transit
> RH0 traffic (rather than simply choose not to act on RH0 headers) -
> have I interpreted this position correctly?  If so, it would seem to
> have implications for both RH0 (as is being discussed) and any new
> source routing approach RHx.

I think that while there may be some value in supporting multi-hop, return
path semantic diagnostic traffic tools, I don't believe we live in a world
where the transport layer itself (IP) is the right place for it to exist.

Having higher-level protocols, or even applications/libraries, that do
what has previously been done in the IPv4 or IPv6 headers, would achieve
the desired goals, without placing a risk or burden on the infrastructure
itself.

So, having "beacon" hosts, on the networks of A and D, who speak a special
application protocol, that allows a sequence of beacon IPs in the "data"
portion of the packet to be semantically interpreted as "send a new packet
to the next IP", etc., similar to either RH0 or LSRR/SSRR, but which would
only do so for packets specific to that protocol (and possibly protected
by, for instance, some kind of key or other ID method or even ACLs),
would allow interested cooperating parties to do their testing, without
exposing the network(s) involved to DOS, or requiring the IPv4/IPv6 stacks
to support special behaviour.

> Is DOS protection / mitigation an assumed (or explicit) service
> provided by ISPs to customers?

It is something akin to a differentiator and/or self-selector.

Some provide proactive detection of DOS, and semiautomatic mitigation.
Most, if not all, respond to requests for filtering of DOS traffic.

Not filtering DOS traffic, even after a customer requests, is very bad
for an ISP's reputation and long-term business survival.

Hope this helps your understanding, and everyone to reach the consensus
required, which is that "RH0 must go."

Brian Dickson


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



From ipv6-bounces@ietf.org Mon Aug 27 14:49:09 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPjcI-00057P-I0; Mon, 27 Aug 2007 14:47:14 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPjcG-00051J-Qn
	for ipv6@ietf.org; Mon, 27 Aug 2007 14:47:12 -0400
Received: from brmea-mail-1.sun.com ([192.18.98.31])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IPjcG-0005fT-71
	for ipv6@ietf.org; Mon, 27 Aug 2007 14:47:12 -0400
Received: from dm-east-01.east.sun.com ([129.148.9.192])
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l7RIlBmo025271 for <ipv6@ietf.org>; Mon, 27 Aug 2007 18:47:11 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 l7RIlBXF055001
	for <ipv6@ietf.org>; Mon, 27 Aug 2007 14:47:11 -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
	l7RIZaCa016583; Mon, 27 Aug 2007 14:35:36 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l7RIZUve016578;
	Mon, 27 Aug 2007 14:35:30 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18131.6514.725148.165861@gargle.gargle.HOWL>
Date: Mon, 27 Aug 2007 14:35:30 -0400
From: James Carlson <james.d.carlson@sun.com>
To: Jun-ichiro itojun Hagino <itojun@itojun.org>
In-Reply-To: <20070827182319.A4C0C233E8@coconut.itojun.org>
References: <Pine.GSO.4.20.0708271348200.6917-100000@meno.corp.us.uu.net>
	<20070827182319.A4C0C233E8@coconut.itojun.org>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: ipv6@ietf.org
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Jun-ichiro itojun Hagino writes:
> 	again, it is about rather serious security problem, which risked
> 	the DNS root name servers.  it's quite serious and really urgent.
> 	the RFC publication should have finished way earlier.

Of course security problems are important.  However, fixing them in
the field is _never_ dependent on publishing an RFC, because the RFCs
themselves are not executable.

If there really are vendors that are failing to fix security problems
because they want to see an RFC published first, then I'd suggest
either taking that up directly with those vendors or simply choosing
not to buy their products.

I think that dismissing concerns about coherence and direction in the
RFCs because of a desire to rush publication is short-sighted at best.

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

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



From ipv6-bounces@ietf.org Mon Aug 27 15:24:39 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPkAT-00018F-8V; Mon, 27 Aug 2007 15:22:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPkAS-00018A-H0
	for ipv6@ietf.org; Mon, 27 Aug 2007 15:22:32 -0400
Received: from [2001:6f8:387:2057:ea05:e98a:6f83:d890] (helo=moog.chdir.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IPkAR-0002cV-Vr
	for ipv6@ietf.org; Mon, 27 Aug 2007 15:22:32 -0400
Received: from [2002:58a4:b573:1:20d:93ff:feeb:2d3]
	(helo=localhost.localdomain)
	by moog.chdir.org with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.63) (envelope-from <arno@natisbad.org>) id 1IPkAR-00047a-6G
	for ipv6@ietf.org; Mon, 27 Aug 2007 21:22:31 +0200
X-Hashcash: 1:20:070827:ipv6@ietf.org::7To33Bhk9Y20JTqf:00000Mru
From: arno@natisbad.org (Arnaud Ebalard)
To: ipv6@ietf.org
References: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
	<Pine.GSO.4.20.0708271100050.6917-100000@meno.corp.us.uu.net>
X-GnuPG-Key: 0x047A5026
Date: Mon, 27 Aug 2007 21:22:29 +0200
In-Reply-To: <Pine.GSO.4.20.0708271100050.6917-100000@meno.corp.us.uu.net>
	(Jason Schiller's message of "Mon, 27 Aug 2007 11:05:04 -0400 (EDT)")
Message-ID: <87mywcg4ui.fsf@natisbad.org>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.95 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: -0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Jason, Hi *,

Jason Schiller <schiller@uu.net> writes:

> On Mon, 20 Aug 2007, Bob Hinden wrote:
>
>> We would like to get your comments on the following two choices:
>> 
>> 1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate-rh0-01.txt>.
>>
>> 2) Revising the draft to restrict the usage of RH0.  This would  
>> continue to require RH0 to be implemented but would restrict the  
>> functionality of RH0.  For example, require nodes to have support for  
>> RH0 turned off by default, limit the number of RH0 headers in a  
>> packet to one, limit the number of addresses in the RH0 to a smaller  
>> number (e.g., 6), and and a requirement that addresses can only be in  
>> the header once.

I am in favor of option 1 for all the reasons provided by Joe in a
previous post. 


> I do concede on the point that almost no one uses it.  As a transit
> provider, we have disabled IPv4 source routing.  We have done this to
> protect our network.  We don't want our routers to do expensive software
> based forwarding decisions.  We don't want to allow customers dictating
> traffic engineering decisions within our network.   Unfortunately, our
> only recourse is to turn off source routing and drop all packets that have
> any source routing options.
>
> It would be better if we had the capabilities to ignore source routing
> options.  

And even better if we had the insurance that all devices do not process
RH0 at all. 


> instead of the transit ISPs acting like a firewall for the Internet and
> deciding what traffic is good for the Internet.

IPv6 without RH0 is good for the Internet (ISP, networks and users). It
has no specific additional prerequisites for users and operators as it
follows their expectations, i.e. it flows End-to-End.

Furthermore, its associated operational cost is null and it does not
remove any _useful_ functionality (as already discussed on the list).

Trying to secure RH0 use in the Internet has a cost (implementation,
education, configuration) and an already proven null ROI (even negative
given the time lost in past decade to specify it, implement it and ...
deactivate it). 

Having a rock solid infrastructure for IP communications (simple,
reliable and efficient) is certainly preferable to a pick-up-sticks
structure that will collapse if one of the hypothesis on which it is
built does not hold anymore.

Regards,

a+

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



From ipv6-bounces@ietf.org Mon Aug 27 15:29:13 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPkF9-00028E-CU; Mon, 27 Aug 2007 15:27:23 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPkF8-000289-6o
	for ipv6@ietf.org; Mon, 27 Aug 2007 15:27:22 -0400
Received: from vgateway.libertyrms.info ([207.219.45.62]
	helo=mail.libertyrms.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IPkF7-00079q-JO
	for ipv6@ietf.org; Mon, 27 Aug 2007 15:27:22 -0400
Received: from vgateway.int.libertyrms.com ([10.1.3.254]
	helo=look.libertyrms.com)
	by mail.libertyrms.com with esmtp (Exim 4.22)
	id 1IPkF2-0002Vr-2F; Mon, 27 Aug 2007 15:27:16 -0400
Received: from 74.122.168.81 (SquirrelMail authenticated user briand)
	by look.libertyrms.com with HTTP;
	Mon, 27 Aug 2007 15:27:16 -0400 (EDT)
Message-ID: <60717.74.122.168.81.1188242836.squirrel@look.libertyrms.com>
In-Reply-To: <18131.6514.725148.165861@gargle.gargle.HOWL>
References: <Pine.GSO.4.20.0708271348200.6917-100000@meno.corp.us.uu.net>
	<20070827182319.A4C0C233E8@coconut.itojun.org>
	<18131.6514.725148.165861@gargle.gargle.HOWL>
Date: Mon, 27 Aug 2007 15:27:16 -0400 (EDT)
From: briand@ca.afilias.info
To: "James Carlson" <james.d.carlson@sun.com>
User-Agent: SquirrelMail/1.4.9a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Exim-Mail-From: briand@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: ipv6@ietf.org
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Jun-ichiro itojun Hagino writes:
>> 	again, it is about rather serious security problem, which risked
>> 	the DNS root name servers.  it's quite serious and really urgent.
>> 	the RFC publication should have finished way earlier.
>
> Of course security problems are important.  However, fixing them in
> the field is _never_ dependent on publishing an RFC, because the RFCs
> themselves are not executable.

While this is technically true, it is a red herring.

The real question is, are there situations where revising an RFC is
necessary, where the result of the RFC *doesn't* require that a new
functionality or change in functionality be built?

The answer here is yes, and is directly on-topic.

The reason the RFC needs to be changed, is that the *default* behaviour,
not the supported kinds of behaviour, is being changed.

The RFCs specify all kinds of things, with language like MUST and MAY.

And the impediment to fixing things in the field, is that vendors need
to maintain interopability. This requires RFCs. Vendors who ignore RFCs,
cause problem for everyone. So, even if some vendors are willing to make
the change, most would prefer, and some require, that the RFC be changed
*first*, so that they do the change to maintain RFC compliance, as compared
to making a change which, while the right thing, violates the RFCs.

> If there really are vendors that are failing to fix security problems
> because they want to see an RFC published first, then I'd suggest
> either taking that up directly with those vendors or simply choosing
> not to buy their products.

The risk of RH0 requires that *all* vendors fix the issue, since it has
bearing on even those parties that have to some degree disabled processing
RH0 packets directed at their gear.

> I think that dismissing concerns about coherence and direction in the
> RFCs because of a desire to rush publication is short-sighted at best.

I agree. I also believe that well-thought out and coherent RFC proposals,
whose timely publication are needed to address actual concerns, should
be given appropriately timely consideration. I also believe that only
the technical content of the RFC should really be what we're talking about,
in any RFC discussion, rather than delaying action on it because of
abstract meta-issues which do not bear on the RFC.

(There can well be situations where the meta-issues *do* bear on the RFC
and/or other RFCs, especially when convicted monopolists are attempting
to modify RFCs to their own ends. But when no such issue exists, we should
avoid dragging those kinds of questions into the discussion.)

Do you agree that the proposal, as written, has very narrow scope?
Do you agree that adoption of the RFC may require vendors to change code
to support the RFC?
And do you agree that if code is changed, to be universally supporting
the RFC, and deployed everywhere, that the RH0 security issue goes away?

If so, I would suggest the appropriate response is to express any concerns
you have, but to also support the proposal.

And if you happen to represent a vendor of IPv6 code, that you either do
the code fix unilaterally, or support the proposal, since the general
consensus is that this needs to be fixed. Or even abstain, if you feel
conflicted. But I don't think opposing this proposal, on any of the grounds
you have suggested, is entirely appropriate -- IMHO.

Brian Dickson
Afilias


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



From ipv6-bounces@ietf.org Mon Aug 27 15:44:00 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPkTb-0007wz-3F; Mon, 27 Aug 2007 15:42:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPkTZ-0007wt-KA
	for ipv6@ietf.org; Mon, 27 Aug 2007 15:42:17 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IPkTY-0003EK-5v
	for ipv6@ietf.org; Mon, 27 Aug 2007 15:42:17 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 432DB19865B;
	Mon, 27 Aug 2007 22:42:15 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id D7563198639;
	Mon, 27 Aug 2007 22:42:14 +0300 (EEST)
Message-ID: <46D32917.4030503@piuha.net>
Date: Mon, 27 Aug 2007 22:42:15 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.13 (X11/20070824)
MIME-Version: 1.0
To: Jason Schiller <schiller@uu.net>
References: <Pine.GSO.4.20.0708271348200.6917-100000@meno.corp.us.uu.net>
In-Reply-To: <Pine.GSO.4.20.0708271348200.6917-100000@meno.corp.us.uu.net>
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: 2409bba43e9c8d580670fda8b695204a
Cc: jason.schiller@verizonbusiness.com, ipv6@ietf.org
Subject: IPv4 (was: Re: New Consensus call on RH0 Deprecation)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Jason,

> It relates to a more general
> discussion of source routing and feature parity in IPv4 and IPv6.  If you
> are going to deprecate IPv6 source routing, then you should also deprecate
> IPv4 source routing.

For the record, earlier review of the IPv4 source routing RFCs
convinced me at least that we may need to make some changes
in the IPv4 side as well.

I have been holding off to start the work while the IPv6 side
work is still in progress, mainly because its easier to deal
with one issue at a time, and because largely the same
people would be involved. But I do think we need to look at
the IPv4 side as well.

The functions are somewhat different, as is deployment
situation -- so I'm not sure complete "feature parity" will
result. But at least we should look at this with the same
technical analysis as we have done in the RH0 case. What
are the issues? What is the implementation and operational
reality vs. what the RFCs are saying? Do the RFCs (such
as 1812) need updating?

Jari


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



From ipv6-bounces@ietf.org Mon Aug 27 15:53:25 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPkcX-0006uK-Tj; Mon, 27 Aug 2007 15:51:33 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPkcV-0006uD-Rn
	for ipv6@ietf.org; Mon, 27 Aug 2007 15:51:31 -0400
Received: from imr2.ericy.com ([198.24.6.3])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IPkcV-0007uG-HA
	for ipv6@ietf.org; Mon, 27 Aug 2007 15:51:31 -0400
Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se
	[138.85.77.50])
	by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id l7RJuAlj007302;
	Mon, 27 Aug 2007 14:56:10 -0500
Received: from eusrcmw750.eamcs.ericsson.se ([138.85.77.53]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Aug 2007 14:51:29 -0500
Received: from [142.133.10.140] ([142.133.10.140]) by
	eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Aug 2007 14:51:29 -0500
Message-ID: <46D32BB2.1030908@ericsson.com>
Date: Mon, 27 Aug 2007 15:53:22 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 1.5 (X11/20060313)
MIME-Version: 1.0
To: Jason Schiller <schiller@uu.net>
References: <Pine.GSO.4.20.0708271348200.6917-100000@meno.corp.us.uu.net>
In-Reply-To: <Pine.GSO.4.20.0708271348200.6917-100000@meno.corp.us.uu.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Aug 2007 19:51:29.0264 (UTC)
	FILETIME=[A8EC7F00:01C7E8E3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: jason.schiller@verizonbusiness.com, ipv6@ietf.org
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Jason,

Jason Schiller wrote:
> I would be curious how people feel about these choices if they also apply
> to (as they should) IPv4 source routing.

I think the problems, though overlapping, are completely different in 
magnitude. The problem with IPv4 source routing is not AS SEVERE as the 
problem with RH0. The main issue I have with RH0 is the NUMBER OF 
ADDRESSES that can occur in the header, rather than the concept itself. 
I don't think there is a valid use case for this number of addresses as 
allowed for in RH0.

Cheers
Suresh

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



From ipv6-bounces@ietf.org Mon Aug 27 16:09:43 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPksL-0004jw-5i; Mon, 27 Aug 2007 16:07:53 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPksJ-0004jr-Db
	for ipv6@ietf.org; Mon, 27 Aug 2007 16:07:51 -0400
Received: from sca-ea-mail-4.sun.com ([192.18.43.22])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IPksI-0008Su-7e
	for ipv6@ietf.org; Mon, 27 Aug 2007 16:07:51 -0400
Received: from dm-east-01.east.sun.com ([129.148.9.192])
	by sca-ea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id
	l7RK7nWi024761 for <ipv6@ietf.org>; Mon, 27 Aug 2007 20:07:49 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 l7RK7gsT026897
	for <ipv6@ietf.org>; Mon, 27 Aug 2007 16:07: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
	l7RJmcYw016942; Mon, 27 Aug 2007 15:48:38 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.1+Sun/8.14.1/Submit) id l7RJmWTS016937;
	Mon, 27 Aug 2007 15:48:32 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <18131.10895.921486.860422@gargle.gargle.HOWL>
Date: Mon, 27 Aug 2007 15:48:31 -0400
From: James Carlson <james.d.carlson@sun.com>
To: briand@ca.afilias.info
In-Reply-To: <60717.74.122.168.81.1188242836.squirrel@look.libertyrms.com>
References: <Pine.GSO.4.20.0708271348200.6917-100000@meno.corp.us.uu.net>
	<20070827182319.A4C0C233E8@coconut.itojun.org>
	<18131.6514.725148.165861@gargle.gargle.HOWL>
	<60717.74.122.168.81.1188242836.squirrel@look.libertyrms.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: ipv6@ietf.org
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

briand@ca.afilias.info writes:
> > Jun-ichiro itojun Hagino writes:
> >> 	again, it is about rather serious security problem, which risked
> >> 	the DNS root name servers.  it's quite serious and really urgent.
> >> 	the RFC publication should have finished way earlier.
> >
> > Of course security problems are important.  However, fixing them in
> > the field is _never_ dependent on publishing an RFC, because the RFCs
> > themselves are not executable.
> 
> While this is technically true, it is a red herring.

I don't think it's a red herring at all.  The previous poster was
conflating RFC publication with actual code change.  The two are
distinct.

> And the impediment to fixing things in the field, is that vendors need
> to maintain interopability. This requires RFCs. Vendors who ignore RFCs,
> cause problem for everyone. So, even if some vendors are willing to make
> the change, most would prefer, and some require, that the RFC be changed
> *first*, so that they do the change to maintain RFC compliance, as compared
> to making a change which, while the right thing, violates the RFCs.

I think a vendor that prides itself on specmanship rather than
security and demonstrated interoperability is probably a lost cause
anyway.

In this case, what you're saying is effectively (also?) a red
herring.  It's not the case that vendors who shut down RH0 long ago
were somehow causing "interoperability" problems, or that having the
RFC published somehow makes any such problems go away.

It may well be the case that (with _other_ changes), a flag day is
necessary.  This clearly isn't one of those cases.

> > If there really are vendors that are failing to fix security problems
> > because they want to see an RFC published first, then I'd suggest
> > either taking that up directly with those vendors or simply choosing
> > not to buy their products.
> 
> The risk of RH0 requires that *all* vendors fix the issue, since it has
> bearing on even those parties that have to some degree disabled processing
> RH0 packets directed at their gear.

Thinking that publishing the RFC will actually cause them to change
seems like a different sort of risk to me.

> Do you agree that the proposal, as written, has very narrow scope?

Yes.

> Do you agree that adoption of the RFC may require vendors to change code
> to support the RFC?

No.  The IETF has no police and can't really force anyone to do
anything.

> And do you agree that if code is changed, to be universally supporting
> the RFC, and deployed everywhere, that the RH0 security issue goes away?

Yes.

> If so, I would suggest the appropriate response is to express any concerns
> you have, but to also support the proposal.

I wasn't expressing any lack of support for the proposal.  I was
expressing support for Jason Schiller's on-topic discussion of the
options.

I don't think that Jun-ichiro itojun Hagino's response to him was
helpful.  It's alarmist and incorrect to say that delaying RFC
publication in order to get the wording right means that people can't
deploy _today_ based on the draft.

Don't most people intentionally deploy implementations based on drafts
anyway?

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

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



From ipv6-bounces@ietf.org Mon Aug 27 16:13:04 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPkvd-00085u-3O; Mon, 27 Aug 2007 16:11:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPkvb-00083S-Li
	for ipv6@ietf.org; Mon, 27 Aug 2007 16:11:15 -0400
Received: from smtp.nokia.com ([131.228.20.172] helo=mgw-ext13.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IPkvZ-000482-VY
	for ipv6@ietf.org; Mon, 27 Aug 2007 16:11:15 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213])
	by mgw-ext13.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l7RKBBRd030808 for <ipv6@ietf.org>; Mon, 27 Aug 2007 23:11:12 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Aug 2007 23:11:10 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 27 Aug 2007 23:11:10 +0300
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by
	esebh102.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Mon, 27 Aug 2007 23:11:10 +0300
Received: from [172.19.74.173] (dadhcp-172019074173.americas.nokia.com
	[172.19.74.173])
	by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l7RKB8YS010973 for <ipv6@ietf.org>; Mon, 27 Aug 2007 23:11:09 +0300
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <C34D54B2-F58D-4721-87DD-F0B5E33EEEB3@nokia.com>
Content-Transfer-Encoding: 7bit
From: Bob Hinden <bob.hinden@nokia.com>
Date: Mon, 27 Aug 2007 13:11:10 -0700
To: IPv6 WG <ipv6@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 27 Aug 2007 20:11:10.0505 (UTC)
	FILETIME=[68FF9190:01C7E8E6]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Subject: Results from "New Consensus call on RH0 Deprecation"
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bob.hinden@nokia.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi,

On August 20, 2007, the IPv6 chairs started a new consensus call on  
RH0 Deprecation.  See:

   http://www1.ietf.org/mail-archive/web/ipv6/current/msg08477.html

Our goal was to make sure there continued to be a consensus for  
deprecating RH0 as specified in the draft <draft-ietf-ipv6-deprecate- 
rh0-01.txt>.

As of 2000 GMT August 27, 2007 we received 18 responses (public and  
private) to the consensus call.  Of these responses 16 were for

   1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate- 
rh0-01.txt>

and two were for

   2) Revising the draft to restrict the usage of RH0

Based on this response to this consensus call, the chairs conclude  
that there continues to be a strong consensus for deprecating RH0.    
Later today we will send email to the ADs requesting that <draft-ietf- 
ipv6-deprecate-rh0-01.txt> be published as a Proposed Standard RFC.

We would also like to encourage anyone interested to write a draft  
for a safer routing header that could be considered by the working  
group.

Thanks,
Bob Hinden & Brian Haberman
IPv6 Chairs






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



From ipv6-bounces@ietf.org Mon Aug 27 16:22:06 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPl4D-0007iD-A0; Mon, 27 Aug 2007 16:20:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPl4C-0007i8-N8
	for ipv6@ietf.org; Mon, 27 Aug 2007 16:20:08 -0400
Received: from pmesmtp03.mci.com ([199.249.20.32])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IPl4B-0004Fh-GK
	for ipv6@ietf.org; Mon, 27 Aug 2007 16:20:08 -0400
Received: from dgismtp04.wcomnet.com ([166.38.58.144])
	by firewall.verizonbusiness.com (Iplanet MTA 5.2)
	with ESMTP id <0JNG00M0M8HJTP@firewall.verizonbusiness.com> for
	ipv6@ietf.org; Mon, 27 Aug 2007 20:20:07 +0000 (GMT)
Received: from dgismtp04.wcomnet.com ([127.0.0.1])
	by dgismtp04.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08
	(built Sep
	22 2005)) with SMTP id <0JNG0044M8HIVL@dgismtp04.mcilink.com> for
	ipv6@ietf.org; Mon, 27 Aug 2007 20:20:07 +0000 (GMT)
Received: from meno.corp.us.uu.net ([153.39.146.71])
	by dgismtp04.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08
	(built Sep
	22 2005)) with ESMTP id <0JNG005HD8HIO7@dgismtp04.mcilink.com> for
	ipv6@ietf.org; Mon, 27 Aug 2007 20:20:06 +0000 (GMT)
Date: Mon, 27 Aug 2007 16:20:05 -0400 (EDT)
From: Jason Schiller <schiller@uu.net>
In-reply-to: <20070827182319.A4C0C233E8@coconut.itojun.org>
X-Sender: schiller@meno.corp.us.uu.net
To: Jun-ichiro itojun Hagino <itojun@itojun.org>
Message-id: <Pine.GSO.4.20.0708271521420.6917-100000@meno.corp.us.uu.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: ipv6@ietf.org, Jason Schiller <jason.schiller@verizonbusiness.com>
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Tue, 28 Aug 2007, Jun-ichiro itojun Hagino wrote:

> 	ok, i assume you have not seen this.  http://www.natisbad.org/.
> 
> 	the key topic being discussed here with the draft is URGENT need to
> 	publish the deprecation/restriction of RH0.
> 
> 	please refrain from generalizing the problem, until RH0 RFC goes
> 	out of the door.  we can handle your generic opinions about the
> 	source routing in general some other time.
> 
> 	again, it is about rather serious security problem, which risked
> 	the DNS root name servers.  it's quite serious and really urgent.
> 	the RFC publication should have finished way earlier.
> 
> itojun
> 

Itojun-san,

Thank you for the URL http://www.natisbad.org/.  

I have been closely following the RH0 discussion as it relates to ISP
network security and the implications on the specific routing gear in my
network.  I have closely examined the security bulletins from my vendors,
and have specified the required testing of their current functionality and
possible work around configurations.    

I am also quite aware of the security implications including:

1. The possibility of end-sites making traffic engineering decisions about
how traffic is forwarded across my network.

2. The possibility of a DoS attack on a link by looping traffic between a
pair of routers or hosts

3. The possibility of circumventing firewall filters by specifying a good
destination, and then source routing the packet behind the firewall to a
filtered destination.

I have only loosely followed the discussion with regard to Unix / Linux
implementation of RH0, and believe the problem to be the same as for some
router vendors who have not provided a configuration statement to discard
source routed IPv6 packets.  I do appreciate the additional links
discussing the RH0 problem wrt particular host operating systems.

I do appreciate the importance of this issue.

We can all agree that at the very least all vendors should offer the
ability to easily discard source routed packets.

I am agreeable to making that the default behavior, although I suspect
there will be some push back as people tend to be uncomfortable whenever
defaults change.  Generally people get upset when they depend on a
default, and then the upgrade their version of Cisco IOS and the default
changes and something breaks.

I understand that this work is holding up getting vendors to modify their
code.

I personally would like to see my vendors offer BOTH the ability to
discard source routed packets, as well as the ability to ignore source
routed packets.  However, if IPv6 source routing is deprecated, then it is
unlikely that they will provide this functionality as it will violate an
RFC.  This is why I prefer option 2.

With regard to generalization I think it is important that we consider
feature parity with IPv4 and IPv6 and understand the implications of
deprecating IPv6 RH0 on IPv4 source routing.

Thanks,

__Jason






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



From ipv6-bounces@ietf.org Mon Aug 27 16:35:03 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPlGc-0007jS-Kx; Mon, 27 Aug 2007 16:32:58 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPlGZ-0007jJ-4e
	for ipv6@ietf.org; Mon, 27 Aug 2007 16:32:55 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IPlGY-0000lZ-H7
	for ipv6@ietf.org; Mon, 27 Aug 2007 16:32:55 -0400
Received: from [63.251.161.155] (account sleibrand@mail.internap.com
	[63.251.161.155] verified)
	by mailserver1.internap.com (CommuniGate Pro SMTP 5.1.10)
	with ESMTPSA id 86992118; Mon, 27 Aug 2007 16:32:53 -0400
Message-ID: <46D334F2.6090008@internap.com>
Date: Mon, 27 Aug 2007 13:32:50 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Jason Schiller <schiller@uu.net>
References: <Pine.GSO.4.20.0708271521420.6917-100000@meno.corp.us.uu.net>
In-Reply-To: <Pine.GSO.4.20.0708271521420.6917-100000@meno.corp.us.uu.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632
Cc: ipv6@ietf.org, Jason Schiller <jason.schiller@verizonbusiness.com>
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Jason,

I haven't been following the RH0 deprecation discussion quite as closely 
as you have, but it seems to me that your concerns would best be 
addressed by creation of a new RH option to support a safer form of 
source routing.  My understanding is that RH0 is a lot like directed 
broadcast (smurf amp), in that if you can find two networks that support 
RH0, and ISP(s) in the middle that allow it, that opens up a DoS 
vector.  As a result, I think everyone needs to discard RH0 packets, and 
that the ability to ignore (pass-through) source-routed packets would 
best be implemented with a new RH option with tighter security.

I guess that makes me #17 in favor of option #1.

-Scott

Jason Schiller wrote:
> On Tue, 28 Aug 2007, Jun-ichiro itojun Hagino wrote:
>
>   
>> 	ok, i assume you have not seen this.  http://www.natisbad.org/.
>>
>> 	the key topic being discussed here with the draft is URGENT need to
>> 	publish the deprecation/restriction of RH0.
>>
>> 	please refrain from generalizing the problem, until RH0 RFC goes
>> 	out of the door.  we can handle your generic opinions about the
>> 	source routing in general some other time.
>>
>> 	again, it is about rather serious security problem, which risked
>> 	the DNS root name servers.  it's quite serious and really urgent.
>> 	the RFC publication should have finished way earlier.
>>
>> itojun
>>
>>     
>
> Itojun-san,
>
> Thank you for the URL http://www.natisbad.org/.  
>
> I have been closely following the RH0 discussion as it relates to ISP
> network security and the implications on the specific routing gear in my
> network.  I have closely examined the security bulletins from my vendors,
> and have specified the required testing of their current functionality and
> possible work around configurations.    
>
> I am also quite aware of the security implications including:
>
> 1. The possibility of end-sites making traffic engineering decisions about
> how traffic is forwarded across my network.
>
> 2. The possibility of a DoS attack on a link by looping traffic between a
> pair of routers or hosts
>
> 3. The possibility of circumventing firewall filters by specifying a good
> destination, and then source routing the packet behind the firewall to a
> filtered destination.
>
> I have only loosely followed the discussion with regard to Unix / Linux
> implementation of RH0, and believe the problem to be the same as for some
> router vendors who have not provided a configuration statement to discard
> source routed IPv6 packets.  I do appreciate the additional links
> discussing the RH0 problem wrt particular host operating systems.
>
> I do appreciate the importance of this issue.
>
> We can all agree that at the very least all vendors should offer the
> ability to easily discard source routed packets.
>
> I am agreeable to making that the default behavior, although I suspect
> there will be some push back as people tend to be uncomfortable whenever
> defaults change.  Generally people get upset when they depend on a
> default, and then the upgrade their version of Cisco IOS and the default
> changes and something breaks.
>
> I understand that this work is holding up getting vendors to modify their
> code.
>
> I personally would like to see my vendors offer BOTH the ability to
> discard source routed packets, as well as the ability to ignore source
> routed packets.  However, if IPv6 source routing is deprecated, then it is
> unlikely that they will provide this functionality as it will violate an
> RFC.  This is why I prefer option 2.
>
> With regard to generalization I think it is important that we consider
> feature parity with IPv4 and IPv6 and understand the implications of
> deprecating IPv6 RH0 on IPv4 source routing.
>
> Thanks,
>
> __Jason
>
>
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>   

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



From ipv6-bounces@ietf.org Mon Aug 27 16:37:45 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPlJW-0008TM-GS; Mon, 27 Aug 2007 16:35:58 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPlJU-0008T3-Q9
	for ipv6@ietf.org; Mon, 27 Aug 2007 16:35:56 -0400
Received: from smtp157.iad.emailsrvr.com ([207.97.245.157])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IPlJU-0000qG-Cd
	for ipv6@ietf.org; Mon, 27 Aug 2007 16:35:56 -0400
Received: by relay5.relay.iad.emailsrvr.com (Authenticated sender:
	dow.street-AT-linquest.com) with ESMTP id 0FA0C62E05A; 
	Mon, 27 Aug 2007 16:35:54 -0400 (EDT)
In-Reply-To: <60580.74.122.168.81.1188240251.squirrel@look.libertyrms.com>
References: <17370393.16676601188232162400.JavaMail.root@vms229.mailsrvcs.net>
	<3B2D1D17-2272-4E3E-A557-99CA50488D6E@linquest.com>
	<60580.74.122.168.81.1188240251.squirrel@look.libertyrms.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <62C7F893-3D1A-4A28-AC33-C9C08C38D087@linquest.com>
Content-Transfer-Encoding: 7bit
From: Dow Street <dow.street@linquest.com>
Date: Mon, 27 Aug 2007 13:35:39 -0700
To: briand@ca.afilias.info
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: ipv6@ietf.org
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Thanks much, Brian - comments inline:

On Aug 27, 2007, at 11:44 AM, briand@ca.afilias.info wrote:

>> Suppose you have 4 providers, where A and B are in the US and C and D
>> are in Japan (the B -- C link is the US-JP link).
>>
>> A - B - - C - D
>>
>> Assume A and D are interested in supporting source routing, but B and
>> C are not.  Further assume that, due to A and D's support for source
>> routing, they are susceptible to the kind of oscillation DOS attack
>> we have been discussing.  The B - - C link is managed / protected by
>> B and C - that is, they have ultimate control over what traffic
>> transits this US - JP link.
>>
>> In the event of an oscillation DOS attack between A and D, do B and C
>> care that the traffic they are transiting is DOS traffic vs. other
>> traffic?  In other words, hasn't the capacity available to A (from B)
>> and the capacity available to D (from C) already been arranged?  If
>> this capacity is consumed due to DOS, is it not A and D (and their
>> customers) who pay the cost?
>
> Absolutely not. The pricing/billing model on transit ISPs, involves  
> some
> presumptions and/or projections on usage patterns. The transit  
> providers,
> in this case B and C, need to ensure peak usage is covered by their
> capacity. And they bill their customers, A and D, based on the  
> observed
> patterns of the aggregates of their customer base, and on A and D in
> particular.
>
> DOS breaks the trends, and exceeds the limits of the billing model, by
> any of several methods. Bottom line is, when traffic is DOS, the cost
> exceeds revenue, since all capacity *on the transit upstream* is  
> eaten.
>
> Traffic that exceeds the link capacity on the respective tail  
> sections,
> A-B and C-D, that crosses B-C, is traffic that must be discarded,  
> has costs,
> but generates *no* revenue.

I assumed it was something like this, but thought it better to ask  
than to guess myself :-)

Is it correct to say, then, that the real problem with RH0 is that it  
creates the potential for traffic (trends) to be less predictable,  
which in turn breaks the current ISP pricing / billing model?  Is it  
also correct to say that the oscillation-DOS case is just one example  
(if perhaps, an extreme one) of how RH0 could make traffic prediction  
more difficult, and that other "legitimate" uses of loose source  
routing (whether RH0 or RHx) present similar risks to the current  
pricing / billing model?

Thanks,
Dow


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



From ipv6-bounces@ietf.org Mon Aug 27 16:51:43 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPlX2-0001qS-AQ; Mon, 27 Aug 2007 16:49:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPlX1-0001pi-7G
	for ipv6@ietf.org; Mon, 27 Aug 2007 16:49:55 -0400
Received: from omzesmtp03.mci.com ([199.249.17.11])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IPlX0-0001JM-Ju
	for ipv6@ietf.org; Mon, 27 Aug 2007 16:49:55 -0400
Received: from dgismtp04.wcomnet.com ([166.38.58.144])
	by firewall.verizonbusiness.com (Iplanet MTA 5.2)
	with ESMTP id <0JNG00CC99UKX7@firewall.verizonbusiness.com> for
	ipv6@ietf.org; Mon, 27 Aug 2007 20:49:32 +0000 (GMT)
Received: from dgismtp04.wcomnet.com ([127.0.0.1])
	by dgismtp04.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08
	(built Sep
	22 2005)) with SMTP id <0JNG00BZ89UK6E@dgismtp04.mcilink.com> for
	ipv6@ietf.org; Mon, 27 Aug 2007 20:49:32 +0000 (GMT)
Received: from meno.corp.us.uu.net ([153.39.146.71])
	by dgismtp04.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08
	(built Sep
	22 2005)) with ESMTP id <0JNG00B149UJ6S@dgismtp04.mcilink.com> for
	ipv6@ietf.org; Mon, 27 Aug 2007 20:49:32 +0000 (GMT)
Date: Mon, 27 Aug 2007 16:49:30 -0400 (EDT)
From: Jason Schiller <schiller@uu.net>
In-reply-to: <3B2D1D17-2272-4E3E-A557-99CA50488D6E@linquest.com>
X-Sender: schiller@meno.corp.us.uu.net
To: Dow Street <dow.street@linquest.com>
Message-id: <Pine.GSO.4.20.0708271626300.7167-100000@meno.corp.us.uu.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1
Cc: ipv6@ietf.org, jason.schiller@verizonbusiness.com
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Mon, 27 Aug 2007, Dow Street wrote:

> On Aug 27, 2007, at 9:29 AM, Tim Enos wrote:
> 
> > Good point. This would be true even in the face of a company on the  
> > JP side and a company on the US side (of the JP-US link) agreed  
> > together to accept source-routed traffic from each other.
> >
> > Just having the RH0 traffic transit the intervening ISP(s) would  
> > make the link susceptible to the attacks outlined in the draft.
> 
> Can you (and others) clarify your position on what you consider to be  
> valid traffic?  I do not work for a commercial ISP, so I'm trying to  
> understand the current thinking / policy on this.
> 
> Suppose you have 4 providers, where A and B are in the US and C and D  
> are in Japan (the B -- C link is the US-JP link).
> 
> A - B - - C - D
> 
> Assume A and D are interested in supporting source routing, but B and  
> C are not.  Further assume that, due to A and D's support for source  
> routing, they are susceptible to the kind of oscillation DOS attack  
> we have been discussing.  The B - - C link is managed / protected by  
> B and C - that is, they have ultimate control over what traffic  
> transits this US - JP link.
> 
> In the event of an oscillation DOS attack between A and D, do B and C  
> care that the traffic they are transiting is DOS traffic vs. other  
> traffic?  In other words, hasn't the capacity available to A (from B)  
> and the capacity available to D (from C) already been arranged?  If  
> this capacity is consumed due to DOS, is it not A and D (and their  
> customers) who pay the cost?

In most cases yes.  A is a customer of ISP B and D is a customer of ISP
C.  Customer A pays ISP B to transit its traffic.  Same for customer D and
ISP C.

If customer A and customer D desire to support source routing, and both
customer A and customer D desire to allow a large amount of traffic
to loop bettween them then so be it.  If customer A or customer D exhausts
their bandwidth and the wish to upgrade then so be it. 

If customer A or customer D consider this bandwidth exhaustive traffic to
be a DoS atack, but desire to permit some source routing, then they can
contcat their upsteam ISP and have the traffic filtered or black holed
just like any other DoS attack.

Or If customer A or customer D consider this bandwidth exhaustive traffic
to be a DoS atack, and do not require permitting source routing, then then
can turn off source routing.

If the traffic consumes all the capasity on backbone link within ISP B or
ISP C or the peering point between ISP B and C, then that ISP should treat
the traffic like any other DoS attack and filter or blackhole the traffic. 

Certainly there are other packet amplifers that are far worse that
RH0.  There is nothing special about RH0 packets that make them any harder
to filter or blackhole than other DoS traffic. 

> 
> This is not to say we shouldn't think about the global aspects of  
> resource use and DOS - I'm just trying to understand whether the  
> approach to source routing requires a global consensus.  Several  
> recent comments seem to imply that it is unacceptable even to transit  
> RH0 traffic (rather than simply choose not to act on RH0 headers) -  
> have I interpreted this position correctly?  If so, it would seem to  
> have implications for both RH0 (as is being discussed) and any new  
> source routing approach RHx.

I have concerns about transiting RH0 (or IPv4 source routed) packets in
the current implementation as many routers treat this traffic differently
and forward this traffic via software which has a greater impact of the
router than normal traffic using hardware based forwarding.  

It would be nice if a router could ignore the source routing, and simply
forward in hardware.  This way each network could protect itself, and
leave other networks free to make their own security decesions.  

Currently the only options are to allow source routing, or discard all
source routed packets.  Thus the transit providers of the Internet have
decided that no one can use source routing. 

__Jason
> 
> Is DOS protection / mitigation an assumed (or explicit) service  
> provided by ISPs to customers?
> 
> Thanks,
> Dow
> 
> 


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



From ipv6-bounces@ietf.org Mon Aug 27 17:04:42 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPljZ-00005T-2v; Mon, 27 Aug 2007 17:02:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPljX-00005M-8j
	for ipv6@ietf.org; Mon, 27 Aug 2007 17:02:51 -0400
Received: from main2.mycybernet.net ([209.222.63.140])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IPljV-0005ty-V9
	for ipv6@ietf.org; Mon, 27 Aug 2007 17:02:51 -0400
Received: from 227-54-222-209.mycybernet.net ([209.222.54.227]
	helo=phlogiston.dydns.org)
	by main2.mycybernet.net with esmtp (Exim 4.62)
	(envelope-from <ajs@phlogiston.dyndns.org>) id 1IPljL-0004hD-AK
	for ipv6@ietf.org; Mon, 27 Aug 2007 17:02:39 -0400
Received: by phlogiston.dydns.org (Postfix, from userid 1000)
	id D560E3F9E; Mon, 27 Aug 2007 17:02:33 -0400 (EDT)
Date: Mon, 27 Aug 2007 17:02:33 -0400
From: Andrew Sullivan <andrew@ca.afilias.info>
To: ipv6@ietf.org
Message-ID: <20070827210233.GA30796@phlogiston.dyndns.org>
References: <Pine.GSO.4.20.0708271348200.6917-100000@meno.corp.us.uu.net>
	<46D32BB2.1030908@ericsson.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46D32BB2.1030908@ericsson.com>
User-Agent: Mutt/1.5.9i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Andrew Sullivan <andrew@ca.afilias.info>
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Mon, Aug 27, 2007 at 03:53:22PM -0400, Suresh Krishnan wrote:

> magnitude. The problem with IPv4 source routing is not AS SEVERE as the 
> problem with RH0. 

Also (and this seems to have been overlooked up-thread), we're in
relatively early days with IPv6, so the installed base we have to go
around and tell "RH0 bad" is quite a bit smaller than whatever people
might be doing with IPv4.  I'm aware that there are significant v6
deployments, but it's still tractable.  Since someone has identified
the problem with RH0, the time to do something about it is now,
before many more people build things that might depend on it.

A

-- 
Andrew Sullivan  | ajs@crankycanuck.ca
The very definition of "news" is "something that hardly ever happens."	
		--Bruce Schneier

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



From ipv6-bounces@ietf.org Mon Aug 27 17:15:02 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPlte-0002MY-3k; Mon, 27 Aug 2007 17:13:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPltc-0002MQ-32
	for ipv6@ietf.org; Mon, 27 Aug 2007 17:13:16 -0400
Received: from ug-out-1314.google.com ([66.249.92.169])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IPlta-00064A-S2
	for ipv6@ietf.org; Mon, 27 Aug 2007 17:13:16 -0400
Received: by ug-out-1314.google.com with SMTP id u2so460972uge
	for <ipv6@ietf.org>; Mon, 27 Aug 2007 14:13:14 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=isZz/UQm8EqK26LIqdPZwxhCnTmbcKlqq/WNkCUh1xHwCi8A+BsnXv9tmB+hoqqWTwx5ueHjMZ9l7TWsYO4gPl0pxsgzF8EWJAhurfBXtEpH7lRsq+Q17vPY7HaWRMW4XsHGpcyPUe6ZU3l56ZC60TYy6HcSOQBs7bVDLkixgSk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=kdSsY3lBVlWsrbaf05/9GncwdVOfrpgFTfD+zJw4QYES+p26LURpbcCLgGYjkJ89kSol0K/KU/qjGaEpCp3QNezf641aSrYrsoB6hm3rTLTmP2xbClXIdIdQmv1jaxcZPmI9kxaTZPFnFZC9Ol62oZJdNRayUdWC5d9D2DXKfV0=
Received: by 10.142.222.21 with SMTP id u21mr334357wfg.1188249192667;
	Mon, 27 Aug 2007 14:13:12 -0700 (PDT)
Received: by 10.142.84.8 with HTTP; Mon, 27 Aug 2007 14:13:12 -0700 (PDT)
Message-ID: <77ead0ec0708271413k5c8178f0l8d95dfe33a0ba005@mail.gmail.com>
Date: Tue, 28 Aug 2007 07:13:12 +1000
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: bob.hinden@nokia.com
In-Reply-To: <C34D54B2-F58D-4721-87DD-F0B5E33EEEB3@nokia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <C34D54B2-F58D-4721-87DD-F0B5E33EEEB3@nokia.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: Results from "New Consensus call on RH0 Deprecation"
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Bob,

I have written the draft for the same, but never gotten around to
posting it. Will do that over the week.

Thanks,
Vishwas

On 8/28/07, Bob Hinden <bob.hinden@nokia.com> wrote:
> Hi,
>
> On August 20, 2007, the IPv6 chairs started a new consensus call on
> RH0 Deprecation.  See:
>
>    http://www1.ietf.org/mail-archive/web/ipv6/current/msg08477.html
>
> Our goal was to make sure there continued to be a consensus for
> deprecating RH0 as specified in the draft <draft-ietf-ipv6-deprecate-
> rh0-01.txt>.
>
> As of 2000 GMT August 27, 2007 we received 18 responses (public and
> private) to the consensus call.  Of these responses 16 were for
>
>    1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate-
> rh0-01.txt>
>
> and two were for
>
>    2) Revising the draft to restrict the usage of RH0
>
> Based on this response to this consensus call, the chairs conclude
> that there continues to be a strong consensus for deprecating RH0.
> Later today we will send email to the ADs requesting that <draft-ietf-
> ipv6-deprecate-rh0-01.txt> be published as a Proposed Standard RFC.
>
> We would also like to encourage anyone interested to write a draft
> for a safer routing header that could be considered by the working
> group.
>
> Thanks,
> Bob Hinden & Brian Haberman
> IPv6 Chairs
>
>
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

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



From ipv6-bounces@ietf.org Mon Aug 27 17:23:39 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPm1l-0004F0-MX; Mon, 27 Aug 2007 17:21:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPm1j-0004Es-JT; Mon, 27 Aug 2007 17:21:39 -0400
Received: from smtp.nokia.com ([131.228.20.171] helo=mgw-ext12.nokia.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IPm1i-0006DK-2i; Mon, 27 Aug 2007 17:21:39 -0400
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211])
	by mgw-ext12.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l7RLLXTW011322; Tue, 28 Aug 2007 00:21:34 +0300
Received: from esebh103.NOE.Nokia.com ([172.21.143.33]) by
	esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Aug 2007 00:21:33 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by
	esebh103.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Tue, 28 Aug 2007 00:21:32 +0300
Received: from mgw-int02.ntc.nokia.com ([172.21.143.97]) by
	esebh102.NOE.Nokia.com over TLS secured channel with Microsoft
	SMTPSVC(6.0.3790.1830); Tue, 28 Aug 2007 00:21:31 +0300
Received: from [172.19.74.173] (dadhcp-172019074173.americas.nokia.com
	[172.19.74.173])
	by mgw-int02.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id
	l7RLLM93003151; Tue, 28 Aug 2007 00:21:22 +0300
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <460A4920-4D82-4563-919C-45948582795C@nokia.com>
Content-Transfer-Encoding: 7bit
From: ext ext Bob Hinden <bob.hinden@nokia.com>
Date: Mon, 27 Aug 2007 14:21:24 -0700
To: Jari Arkko <jari.arkko@piuha.net>, Mark Townsley <townsley@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 27 Aug 2007 21:21:31.0990 (UTC)
	FILETIME=[3D330F60:01C7E8F0]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: IPv6 Mailing List <ipv6@ietf.org>,
	Brian Haberman <brian@innovationslab.net>,
	IESG Secretary <iesg-secretary@ietf.org>
Subject: Request to Advance:  <draft-ietf-ipv6-deprecate-rh0-01.txt>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: bob.hinden@nokia.com
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Jari & Mark,

On behalf of the IPv6 WG, the chairs request the advancement of

	Title		: Deprecation of Type 0 Routing Headers in IPv6
	Author(s)	: J. Abley, et al.
	Filename	: draft-ietf-ipv6-deprecate-rh0-01.txt
	Pages		: 9
	Date		: 2007-6-28
	
as an Proposed Standard.  This document reflects the consensus of the  
IPv6 WG.  The working group last call completed on July 12, 2007.

After the working group last call was completed, a separate consensus  
call was held on the mailing list.  This confirmed that there was a  
strong consensus to publish this document.  See:

    http://www1.ietf.org/mail-archive/web/ipv6/current/msg08546.html

Regards,
Bob Hinden & Brian Haberman
IPv6 working group chairs


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



From ipv6-bounces@ietf.org Mon Aug 27 17:49:40 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPmQs-0003Zx-ML; Mon, 27 Aug 2007 17:47:38 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPmQr-0003Zs-Eq
	for ipv6@ietf.org; Mon, 27 Aug 2007 17:47:37 -0400
Received: from omzesmtp01.mci.com ([199.249.17.7])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IPmQq-0002g2-VA
	for ipv6@ietf.org; Mon, 27 Aug 2007 17:47:37 -0400
Received: from pmismtp03.mcilink.com ([166.37.158.163])
	by firewall.verizonbusiness.com (Iplanet MTA 5.2)
	with ESMTP id <0JNG009L3CCB1A@firewall.verizonbusiness.com> for
	ipv6@ietf.org; Mon, 27 Aug 2007 21:43:23 +0000 (GMT)
Received: from pmismtp03.mcilink.com ([127.0.0.1])
	by pmismtp03.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08
	(built Sep
	22 2005)) with SMTP id <0JNG001LPCCBYF@pmismtp03.mcilink.com> for
	ipv6@ietf.org; Mon, 27 Aug 2007 21:43:23 +0000 (GMT)
Received: from meno.corp.us.uu.net ([153.39.146.71])
	by pmismtp03.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08
	(built Sep
	22 2005)) with ESMTP id <0JNG000HECCA7H@pmismtp03.mcilink.com> for
	ipv6@ietf.org; Mon, 27 Aug 2007 21:43:23 +0000 (GMT)
Date: Mon, 27 Aug 2007 17:43:22 -0400 (EDT)
From: Jason Schiller <schiller@uu.net>
In-reply-to: <20070827210233.GA30796@phlogiston.dyndns.org>
X-Sender: schiller@meno.corp.us.uu.net
To: Andrew Sullivan <andrew@ca.afilias.info>
Message-id: <Pine.GSO.4.20.0708271726220.7193-100000@meno.corp.us.uu.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 1.2 (+)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: ipv6@ietf.org
Subject: RH0 bad (for my network)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Mon, 27 Aug 2007, Andrew Sullivan wrote:

> On Mon, Aug 27, 2007 at 03:53:22PM -0400, Suresh Krishnan wrote:
> 
> > magnitude. The problem with IPv4 source routing is not AS SEVERE as the 
> > problem with RH0. 
> 
> Also (and this seems to have been overlooked up-thread), we're in
> relatively early days with IPv6, so the installed base we have to go
> around and tell "RH0 bad" is quite a bit smaller than whatever people
> might be doing with IPv4.  I'm aware that there are significant v6
> deployments, but it's still tractable.  Since someone has identified
> the problem with RH0, the time to do something about it is now,
> before many more people build things that might depend on it.
> 
> A
> 

It is one thing to say RH0 (and by extension IPv4 source routing) is bad
for my network, and therefore my network will not support source routing.

It is quite another thing to say RH0 (and by extension IPv4 source
routing) is bad for my network, and therefore no one will be able to use
source routing.

What I am advocating is that each network be able to make their own
decisions about supporting source routing and not be at the mercy of
everyone that is upstream from them.


no-ip-source-routing  = the option to turn off source routing for my
                        network and everyone down stream.

ignore-source-routing = the option to turn off source routing in my
                        network.

Deprecating RH0       = no IPv6 source routing.  And will likely lead to
                        deprecating  IPv4 source routing.


In the short term, lets make sure all vendors support
no-ip-source-routing, and in the long term add the flexibility to ignore
source routing.

And lets discuss if no-ip-source-routing should be the default action or
not. (personally I don't care either way as long as IPv4 and IPv6 are
consistent, and there is a fair amount of notification if current defaults
change).

I'm not suggesting that we hold up the draft until the
"ignore-source-routing" spec can be written.  I do think if source routing
(IPv4 and IPv6) is depricated, then we will never get this flexibility.

__Jason


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



From ipv6-bounces@ietf.org Tue Aug 28 03:56:14 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPvtg-00047R-TA; Tue, 28 Aug 2007 03:54:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPvtg-00047L-7v
	for ipv6@ietf.org; Tue, 28 Aug 2007 03:54:00 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IPvte-0003O8-Gr
	for ipv6@ietf.org; Tue, 28 Aug 2007 03:54:00 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 51C8819865B;
	Tue, 28 Aug 2007 10:53:57 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id EF9A019865A;
	Tue, 28 Aug 2007 10:53:56 +0300 (EEST)
Message-ID: <46D3D494.8060003@piuha.net>
Date: Tue, 28 Aug 2007 10:53:56 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.13 (X11/20070824)
MIME-Version: 1.0
To: IETF IPv6 Mailing List <ipv6@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: 1676547e4f33b5e63227e9c02bd359e3
Cc: Thomas Narten <narten@us.ibm.com>,
	Dave Thaler <dthaler@windows.microsoft.com>,
	16ng WG chairs <16ng-chairs@tools.ietf.org>
Subject: 2461bis AUTH48 changes
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Folks,

The 2461bis document has been for a (long) while in AUTH48. This
is also affecting other documents that are pending for the RFC to
come out.

One of the reasons why this has taken so long is that a number of
issues were raised on the list, privately to me, and in IESG review
of some other documents, all possibly requiring clarifications or
modifications to 2461bis. We also met with the people in the Cc
list in IETF-69 to talk about this.

I have now reviewed all the raised issues and would like to
report to the WG where we are. There is also one suggested
modification which I believe we should perform. If there are
any objections to this modification I'd like to hear them by
the end of the week. The other issues should be deferred
for further work or pursued in other ways.

1. Issues raised in draft-wbeebee. A number of clarifications
    in the off/on-link rules were given. I sent another mail about
    this (see link below) and suggested that at this time we
    do not have sufficient agreement that the matter indeed
    needs clarification, and the amount of changes would
    exceed something we can do in AUTH48. As a result,
    this should be pursued in separate documents and
    discussed further in the WG.

    http://www1.ietf.org/mail-archive/web/ipv6/current/msg08505.html

2. Issues raised in the IESG review of draft-ietf-16ng-ipv6-over-ipv6cs.
    This is an "IPv6 over Foo" document that wants to override
    the AdvDefaultLifetime value for this specific link layer.

    The IESG reviewers wanted to allow overriding for consenting
    link layer designers, but only if the 2461bis allowed the override
    for a specific variable. Note that the beginning of Section 6.2.1
    says the default values can be overridden by link layer specifications,
    but it is silent on limits, and the limits are given using MUST
    language.

    I do not want to go into a discussion of what makes sense for
    a specific link layer, but I do believe that this is appropriate
    under certain circumstances. For AdvDefaultLifetime, right
    now the document simply says "MUST be either zero or
    between MaxRtrAdvInterval and 9000 seconds." When we
    talked about this in a small group in Chicago, it was
    suggested that for point-to-point links the IPv6 over Foo
    documents should have more freedom to specify this
    timer, as the nature of the link tells you how many
    devices can be at the other end, and you may also have
    more information about link up/down events than in
    other link types.

    In any case, we could either allow a particular extension under
    specific conditions, or make it more generally clear that
    the IPv6 over Foo documents can override even the MUSTs
    relating to timer limits. I would suggest the former.

    The change would be as follows:

    OLD:
      MUST be either zero or between
      MaxRtrAdvInterval and 9000 seconds.  A value of
      zero indicates that the router is not to be used as
      a default router.
    NEW:
      MUST be either zero or between
      MaxRtrAdvInterval and 9000 seconds.  A value of
      zero indicates that the router is not to be used as
      a default router. These limits may be overridden
      by specific documents that describe how IPv6 operates
      over different link-layers. For instance, in a point-to-point
      link the peers may have enough information about the
      number and status of devices at the other end so that
      advertisements are needed less frequently.

    I would like the WG to OK this change. Any objections?

3. Issues raised by Thomas Narten about conflicts and
    synchronization to other RFCs.

    There was an earlier discussion of this in the WG,
    under the thread "narten's review". Thomas has
    looked at this again during AUTH48 and raised the
    issues to me. The issues included

    - Updating the document with information about
      what new bits have been allocated in the reserved
      fields, along with informative pointers to the documents
      in question.

    - The same for options.

    - Synchronizing RFC 3775 Section 7.5 new limits for
      router advertisement frequencies and 2461bis.

    I think Thomas is basically right and the document
    would be better with these folded in. I also think
    if properly written, these changes would not have
    caused normative references or DS advancement
    problems. However, at the end of the day, the
    changes are fairly big for AUTH48, were already
    discussed in the WG, and are more of editorial in
    nature than fixing a critical bug. Finally, the
    RFC 3775 synchronization would involve more
    than mere timer values; there are more items
    in Section 7.5 that would have to be folded in.

    So, I would rather move on with the RFC publication
    than re-run the discussion, even if I think I would
    personally have written the bis document in
    slightly different manner to avoid Thomas' issues.

In summary, I only see one issue (item 2) that requires
a change in AUTH48. If the WG agrees we should get
the document out next week.

Jari


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



From ipv6-bounces@ietf.org Tue Aug 28 04:02:12 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPvzp-0001hN-MW; Tue, 28 Aug 2007 04:00:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPvzo-0001Xa-8a
	for ipv6@ietf.org; Tue, 28 Aug 2007 04:00:20 -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 1IPvzn-0003dR-S4
	for ipv6@ietf.org; Tue, 28 Aug 2007 04:00:20 -0400
Received: by coconut.itojun.org (Postfix, from userid 501)
	id AF13A233E9; Tue, 28 Aug 2007 17:00:07 +0900 (JST)
To: andrew@ca.afilias.info
In-Reply-To: Your message of "Mon, 27 Aug 2007 17:02:33 -0400"
	<20070827210233.GA30796@phlogiston.dyndns.org>
References: <20070827210233.GA30796@phlogiston.dyndns.org>
X-Mailer: Cue version 0.8 (070521-1856/itojun)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20070828080007.AF13A233E9@coconut.itojun.org>
Date: Tue, 28 Aug 2007 17:00:07 +0900 (JST)
From: itojun@itojun.org (Jun-ichiro itojun Hagino)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: ipv6@ietf.org
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> > magnitude. The problem with IPv4 source routing is not AS SEVERE as the 
> > problem with RH0. 
> 
> Also (and this seems to have been overlooked up-thread), we're in
> relatively early days with IPv6, so the installed base we have to go

	"small" includes 22 million copies of MacOS X.

itojun

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



From ipv6-bounces@ietf.org Tue Aug 28 04:09:46 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPw7A-0008DW-OY; Tue, 28 Aug 2007 04:07:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPw78-0008DB-GT
	for ipv6@ietf.org; Tue, 28 Aug 2007 04:07:54 -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 1IPw78-0003t3-2l
	for ipv6@ietf.org; Tue, 28 Aug 2007 04:07:54 -0400
Received: by coconut.itojun.org (Postfix, from userid 501)
	id 5D6D2233E9; Tue, 28 Aug 2007 17:07:52 +0900 (JST)
To: james.d.carlson@sun.com
In-Reply-To: Your message of "Mon, 27 Aug 2007 15:48:31 -0400"
	<18131.10895.921486.860422@gargle.gargle.HOWL>
References: <18131.10895.921486.860422@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: <20070828080752.5D6D2233E9@coconut.itojun.org>
Date: Tue, 28 Aug 2007 17:07:52 +0900 (JST)
From: itojun@itojun.org (Jun-ichiro itojun Hagino)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: ipv6@ietf.org
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

	the last call was finished, but for a bit of nitpicking:

> I don't think that Jun-ichiro itojun Hagino's response to him was
> helpful.  It's alarmist and incorrect to say that delaying RFC
> publication in order to get the wording right means that people can't
> deploy _today_ based on the draft.
> 
> Don't most people intentionally deploy implementations based on drafts
> anyway?

	some of the major IPv6 implementation certification firm, and some
	vendros of IPv6 implementation with rather serious number of
	actual shipping/deployment, do implement RH0, and do require RH0
	to get certification, because of what is documented on the RFC.

	so the spirit of "request for comment" is not widely understood....

itojun

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



From ipv6-bounces@ietf.org Tue Aug 28 04:15:44 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPwCz-00041H-WB; Tue, 28 Aug 2007 04:13:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPwCy-00041C-Pq
	for ipv6@ietf.org; Tue, 28 Aug 2007 04:13: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 1IPwCy-0003yz-CQ
	for ipv6@ietf.org; Tue, 28 Aug 2007 04:13:56 -0400
Received: by coconut.itojun.org (Postfix, from userid 501)
	id 9C741233EC; Tue, 28 Aug 2007 17:13:54 +0900 (JST)
To: jhw@apple.com
In-Reply-To: Your message of "Mon, 27 Aug 2007 11:26:18 -0700"
	<927504B0-52FB-49BB-B5EB-190F95D476F6@apple.com>
References: <927504B0-52FB-49BB-B5EB-190F95D476F6@apple.com>
X-Mailer: Cue version 0.8 (070521-1856/itojun)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20070828081354.9C741233EC@coconut.itojun.org>
Date: Tue, 28 Aug 2007 17:13:54 +0900 (JST)
From: itojun@itojun.org (Jun-ichiro itojun Hagino)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Cc: ipv6@ietf.org
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> I was unaware until just now that IPv4 source routing had *not* been  
> deprecated by IETF already.  I must have been misinformed about  
> that.  It's certainly not viewed with any favor among the circles  
> I've been in most recently.

	packets with IPv4 options wouldn't go far because too many
	routers do not pass it, or do not support it.

itojun

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



From ipv6-bounces@ietf.org Tue Aug 28 04:33:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPwUS-0007y3-85; Tue, 28 Aug 2007 04:32:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPwUQ-0007wV-R3
	for ipv6@ietf.org; Tue, 28 Aug 2007 04:31:58 -0400
Received: from an-out-0708.google.com ([209.85.132.245])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IPwUP-0004GJ-Fv
	for ipv6@ietf.org; Tue, 28 Aug 2007 04:31:58 -0400
Received: by an-out-0708.google.com with SMTP id c17so259795anc
	for <ipv6@ietf.org>; Tue, 28 Aug 2007 01:31:57 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type;
	b=hGt9VSkJVB8iZavkFsSA68L4mdHYB0y1YfzrowDJ8/UV32i2eGWzYYueMry+EMC60hw6tQZJOlaU+F4Ge00N03ulJspB0Ds2QsAEmcVsTW8LJhqkYKj8K72X3EKIcy56FzhlNNYOPBNAMym9hDVHZni5b1ed3UY4g4KIvMxXzWs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:mime-version:content-type;
	b=GdMdDMapuvFr3oYdSBdzE2HhVlYBJQT1yDFZP4Qx6CFvLc0eGz3/nZS8nPBx+h2aOTQTH9dQsMFiN3eSlmqHZ5Jj9eLJyswxFuO5oE+UmqSxFO3dEdF1dgzZ0urR47mP8Zw6Mm1eLlwfR/IV3jo2bRudnywQrvMP2ZlKFRSvoS4=
Received: by 10.142.103.6 with SMTP id a6mr562661wfc.1188289912533;
	Tue, 28 Aug 2007 01:31:52 -0700 (PDT)
Received: by 10.142.84.8 with HTTP; Tue, 28 Aug 2007 01:31:52 -0700 (PDT)
Message-ID: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
Date: Tue, 28 Aug 2007 18:31:52 +1000
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "IPv6 WG" <ipv6@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_44349_3767356.1188289912490"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 46ad68ada464411807db2a0edd5648ae
Cc: manoj@ipinfusion.com
Subject: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

------=_Part_44349_3767356.1188289912490
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,

Based on feedback from the group, we have written a draft for a new
routing header. The functionality is the same as the RH0. The draft
will soon be posted to the IETF site.

The main differences are:

1. Maximum up to 4 addresses in the header. (the number is based on
the reply I got for the question about the usage scenarios in operator
environments).
2. Only one header in each packet.
3. Firewall policy reccomendation.
4. RPF reccomendation.

Please have a look and let us know your comments.

Thanks,
Vishwas

------=_Part_44349_3767356.1188289912490
Content-Type: text/plain; name=draft-manral-ipv6-rh4-00.txt; 
	charset=ANSI_X3.4-1968
Content-Transfer-Encoding: base64
X-Attachment-Id: f_f5w52xcv
Content-Disposition: attachment; filename="draft-manral-ipv6-rh4-00.txt"

DQoNCk5ldHdvcmsgV29ya2luZyBHcm91cCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIFYuIE1hbnJhbA0KSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIE0uIER1dHRhDQpVcGRhdGVzOiAyNDYwLCA0Mjk0
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBJUCBJbmZ1c2lvbiBJbmMuDQoo
aWYgYXBwcm92ZWQpICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0K
SW50ZW5kZWQgc3RhdHVzOiBTdGFuZGFyZHMgVHJhY2sgICAgICAgICAgICAgICAgICAgICAgICAN
CkV4cGlyZXM6IEZlYnJ1YXJ5IDI4LCAyMDA4ICAgICAgICAgICAgICAgICAgICAgICANCiAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgQXVndXN0
IDI4LCAyMDA3DQoNCg0KICAgICAgICAgICAgICAgICAgTmV3IElQdjYgVHlwZSA0IFJvdXRpbmcg
SGVhZGVyDQogICAgICAgICAgICAgICAgICAgIGRyYWZ0LW1hbnJhbC1pcHY2LXJoNC0wMA0KDQpT
dGF0dXMgb2YgdGhpcyBNZW1vDQoNCiAgIEJ5IHN1Ym1pdHRpbmcgdGhpcyBJbnRlcm5ldC1EcmFm
dCwgZWFjaCBhdXRob3IgcmVwcmVzZW50cyB0aGF0IGFueQ0KICAgYXBwbGljYWJsZSBwYXRlbnQg
b3Igb3RoZXIgSVBSIGNsYWltcyBvZiB3aGljaCBoZSBvciBzaGUgaXMgYXdhcmUNCiAgIGhhdmUg
YmVlbiBvciB3aWxsIGJlIGRpc2Nsb3NlZCwgYW5kIGFueSBvZiB3aGljaCBoZSBvciBzaGUgYmVj
b21lcw0KICAgYXdhcmUgd2lsbCBiZSBkaXNjbG9zZWQsIGluIGFjY29yZGFuY2Ugd2l0aCBTZWN0
aW9uIDYgb2YgQkNQIDc5Lg0KDQogICBJbnRlcm5ldC1EcmFmdHMgYXJlIHdvcmtpbmcgZG9jdW1l
bnRzIG9mIHRoZSBJbnRlcm5ldCBFbmdpbmVlcmluZw0KICAgVGFzayBGb3JjZSAoSUVURiksIGl0
cyBhcmVhcywgYW5kIGl0cyB3b3JraW5nIGdyb3Vwcy4gIE5vdGUgdGhhdA0KICAgb3RoZXIgZ3Jv
dXBzIG1heSBhbHNvIGRpc3RyaWJ1dGUgd29ya2luZyBkb2N1bWVudHMgYXMgSW50ZXJuZXQtDQog
ICBEcmFmdHMuDQoNCiAgIEludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRzIHZhbGlk
IGZvciBhIG1heGltdW0gb2Ygc2l4IG1vbnRocw0KICAgYW5kIG1heSBiZSB1cGRhdGVkLCByZXBs
YWNlZCwgb3Igb2Jzb2xldGVkIGJ5IG90aGVyIGRvY3VtZW50cyBhdCBhbnkNCiAgIHRpbWUuICBJ
dCBpcyBpbmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMgcmVmZXJlbmNlDQog
ICBtYXRlcmlhbCBvciB0byBjaXRlIHRoZW0gb3RoZXIgdGhhbiBhcyAid29yayBpbiBwcm9ncmVz
cy4iDQoNCiAgIFRoZSBsaXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQtRHJhZnRzIGNhbiBiZSBhY2Nl
c3NlZCBhdA0KICAgaHR0cDovL3d3dy5pZXRmLm9yZy9pZXRmLzFpZC1hYnN0cmFjdHMudHh0Lg0K
DQogICBUaGUgbGlzdCBvZiBJbnRlcm5ldC1EcmFmdCBTaGFkb3cgRGlyZWN0b3JpZXMgY2FuIGJl
IGFjY2Vzc2VkIGF0DQogICBodHRwOi8vd3d3LmlldGYub3JnL3NoYWRvdy5odG1sLg0KDQogICBU
aGlzIEludGVybmV0LURyYWZ0IHdpbGwgZXhwaXJlIG9uIERlY2VtYmVyIDI4LCAyMDA3Lg0KDQpD
b3B5cmlnaHQgTm90aWNlDQoNCiAgIENvcHlyaWdodCAoQykgVGhlIElFVEYgVHJ1c3QgKDIwMDcp
Lg0KDQpBYnN0cmFjdA0KDQogICBUaGUgZnVuY3Rpb25hbGl0eSBwcm92aWRlZCBieSBJUHY2J3Mg
VHlwZSAwIFJvdXRpbmcgSGVhZGVyIGNhbiBiZQ0KICAgZXhwbG9pdGVkIGluIG9yZGVyIHRvIGFj
aGlldmUgdHJhZmZpYyBhbXBsaWZpY2F0aW9uIG92ZXIgYSByZW1vdGUNCiAgIHBhdGggZm9yIHRo
ZSBwdXJwb3NlcyBvZiBnZW5lcmF0aW5nIGRlbmlhbC1vZi1zZXJ2aWNlIHRyYWZmaWMuICANCg0K
ICAgVGhpcyBkb2N1bWVudCB1cGRhdGVzIHRoZSBJUHY2IHNwZWNpZmljYXRpb24gdG8gdGhlIHVz
ZSBvZiBhIG5ldyANCiAgIElQdjYgVHlwZSA0IFJvdXRpbmcgSGVhZGVyLCBpbiBsaWdodCBvZiB0
aGlzIHNlY3VyaXR5IGNvbmNlcm4uIFRoaXMgDQogICBuZXcgaGVhZGVyIHByb3ZpZGVzIHRoZSBz
YW1lIGZ1bmN0aW9uYWxpdHkgb2YgdGhlIFJvdXRpbmcgSGVhZGVyDQogICBUeXBlLTAsIHdoaWxl
IHRha2luZyBjYXJlIG9mIHRoZSBtYWpvciBzZWN1cml0eSBjb25jZXJucyBkZWZpbmVkIA0KICAg
aW4gdGhlIGRyYWZ0IFtkcmFmdC1pZXRmLWlwdjYtZGVwcmVjYXRlLXJoMC0wMV0uDQoNCg0KDQpN
YW5yYWwgICAgICAgICAgICAgICAgRXhwaXJlcyBGZWJydWFyeSAyOCwgMjAwOCAgICAgICAgICAg
ICAgIFtQYWdlIDFdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICBOZXcgSVB2NiBUeXBlIDQgUm91
dGluZyBIZWFkZXIgICAgICAgICAgICBKdW5lIDIwMDcNCg0KDQpUYWJsZSBvZiBDb250ZW50cw0K
DQogICAxLiAgSW50cm9kdWN0aW9uICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIDMNCiAgIDIuICBEZWZpbml0aW9ucyAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gNA0KICAgMy4gIEZvcm1hdCBvZiBSSDQg
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgLiA0DQogICA0
LiAgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIDUNCiAgIDUuICBJQU5BIENvbnNpZGVyYXRpb25zIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gNw0KICAgNi4gIEFja25vd2xlZ2VtZW50cyAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiA3DQogICA4LiAgUmVm
ZXJlbmNlcyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIDcNCiAgICAgNi4xLiAgTm9ybWF0aXZlIFJlZmVyZW5jZXMgIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gNw0KICAgICA2LjIuICBJbmZvcm1hdGl2ZSBSZWZlcmVuY2Vz
ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiA4DQogICBBcHBlbmRpeCBBLiAg
Q2hhbmdlIEhpc3RvcnkgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDgN
CiAgIEF1dGhvcnMnIEFkZHJlc3NlcyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gOQ0KICAgSW50ZWxsZWN0dWFsIFByb3BlcnR5IGFuZCBDb3B5cmlnaHQg
U3RhdGVtZW50cyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAxMA0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQpNYW5y
YWwgICAgICAgICAgICAgICAgRXhwaXJlcyBGZWJydWFyeSAyOCwgMjAwOCAgICAgICAgICAgICAg
IFtQYWdlIDJdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICBOZXcgSVB2NiBUeXBlIDQgUm91dGlu
ZyBIZWFkZXIgICAgICAgICAgICBKdW5lIDIwMDcNCg0KDQoxLiAgSW50cm9kdWN0aW9uDQoNCiAg
IFtSRkMyNDYwXSBkZWZpbmVzIGFuIElQdjYgZXh0ZW5zaW9uIGhlYWRlciBjYWxsZWQgIlJvdXRp
bmcgSGVhZGVyIiwNCiAgIGlkZW50aWZpZWQgYnkgYSBOZXh0IEhlYWRlciB2YWx1ZSBvZiA0MyBp
biB0aGUgaW1tZWRpYXRlbHkgcHJlY2VkaW5nDQogICBoZWFkZXIuICBBIHBhcnRpY3VsYXIgUm91
dGluZyBIZWFkZXIgc3VidHlwZSBkZW5vdGVkIGFzICJUeXBlIDAiIGlzDQogICBhbHNvIGRlZmlu
ZWQuICBUeXBlIDAgUm91dGluZyBIZWFkZXJzIGFyZSByZWZlcnJlZCB0byBhcyAiUkgwIiBpbg0K
ICAgdGhpcyBkb2N1bWVudC4NCg0KICAgMTI4LWZvbGQgYW1wbGlmaWNhdGlvbiBvZiBkYXRhIHRy
YWZmaWMgY2FuIHJlc3VsdCB1c2luZyB0aGUgSVB2NiANCiAgIGFtcGxpZmljYXRpb24gYXR0YWNr
IGFzIGRlZmluZWQgaW4gW0ktRC5pZXRmLWlwdjYtZGVwcmVjYXRlLXJoMC0wMV0uDQogICBUaGlz
IGF0dGFjayBpcyBwYXJ0aWN1bGFybHkgc2VyaW91cyBpbiB0aGF0IGl0IGFmZmVjdHMgdGhlIGVu
dGlyZQ0KICAgcGF0aCBiZXR3ZWVuIHRoZSB0d28gZXhwbG9pdGVkIG5vZGVzLCBub3Qgb25seSB0
aGUgbm9kZXMgdGhlbXNlbHZlcw0KICAgb3IgdGhlaXIgbG9jYWwgbmV0d29ya3MuICANCg0KICAg
VGhlIGRyYWZ0IFtJLUQuaWV0Zi1pcHY2LWRlcHJlY2F0ZS1yaDAtMDFdIGRlcHJlY2F0ZXMgdGhl
IHVzZSBvZiB0aGUgDQogICBSSDAgaGVhZGVyLiBIb3dldmVyIG9wZXJhdG9ycyB1c2UgYW5kIHJl
cXVpcmUgdGhlIGZ1bmN0aW9uYWxpdHkgcHJvdmlkZWQNCiAgIGJ5IHRoZSBSSDAgaGVhZGVyLg0K
DQogICBUaGlzIGRyYWZ0IGRlZmluZXMgdGhlIFJvdXRpbmcgSGVhZGVyIG9mIFR5cGUtNCwgYW5k
IHJlZmVycmVkIHRvIGFzICJSSDQiIA0KICAgaGVhZGVyLiBUaGUgUkg0IGhlYWRlciBoYXMgZm9y
bWF0IGFuZCBmdW5jdGlvbmFsaXR5IHNpbWlsYXIgdG8gdGhlIFJIMCANCiAgIGhlYWRlciB3aXRo
b3V0IGhhdmluZyB0aGUgbWFqb3IgdnVsbmVyYWJpbGl0aWVzIG9mIHRoZSAiUm91dGluZyBIZWFk
ZXIiLg0KDQogICBUaGlzIGRvY3VtZW50IHVwZGF0ZXMgW1JGQzI0NjBdIGFuZCBbUkZDNDI5NF0u
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoN
Ck1hbnJhbCAgICAgICAgICAgICAgICBFeHBpcmVzIEZlYnJ1YXJ5IDI4LCAyMDA4ICAgICAgICAg
ICAgICAgW1BhZ2UgM10NCgwNCkludGVybmV0LURyYWZ0ICAgICAgIE5ldyBJUHY2IFR5cGUgNCBS
b3V0aW5nIEhlYWRlciAgICAgICAgICAgIEp1bmUgMjAwNw0KDQoNCjIuICBEZWZpbml0aW9ucw0K
DQogICBSSDQgaW4gdGhpcyBkb2N1bWVudCBkZW5vdGVzIHRoZSBJUHY2IEV4dGVuc2lvbiBIZWFk
ZXIgdHlwZSA0Mw0KICAgKCJSb3V0aW5nIEhlYWRlciIpIHZhcmlhbnQgNCAoIlR5cGUgNCBSb3V0
aW5nIEhlYWRlciIpLCBpcyBhIHR5cGUgb2YgDQogICBSb3V0aW5nIGhlYWRlciBhcyBkZWZpbmVk
IGluIFtSRkMyNDYwXS4gDQoNCiAgIFRoZSBrZXkgd29yZHMgIk1VU1QiLCAiTVVTVCBOT1QiLCAi
UkVRVUlSRUQiLCAiU0hBTEwiLCAiU0hBTEwgTk9UIiwNCiAgICJTSE9VTEQiLCAiU0hPVUxEIE5P
VCIsICJSRUNPTU1FTkRFRCIsICJNQVkiLCBhbmQgIk9QVElPTkFMIiBpbiB0aGlzDQogICBkb2N1
bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgYXMgZGVzY3JpYmVkIGluIFtSRkMyMTE5XS4NCg0K
DQozLiAgRm9ybWF0IG9mIFJINA0KDQogICBUaGUgVHlwZSA0IFJvdXRpbmcgaGVhZGVyIGhhcyB0
aGUgZm9sbG93aW5nIGZvcm1hdCAoaXQgaXMgdGhlIHNhbWUgYXMgDQogICB0aGUgUkgwIGhlYWRl
ciBleGNlcHQgZm9yIHRoZSBsaW1pdCBvbiB0aGUgIkhkciBFeHQgTGVuIiBmaWVsZC4gU29tZSAN
CiAgIGFkZGl0aW9uYWwgcmVzdHJpY3Rpb25zIGFuZCBjaGVja3MgaGF2ZSBiZWVuIGFkZGVkKToN
Cg0KICAgICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rDQogICAgfCAgTmV4dCBIZWFkZXIgIHwgIEhkciBFeHQgTGVuICB8IFJv
dXRpbmcgVHlwZT0wfCBTZWdtZW50cyBMZWZ0IHwNCiAgICArLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKw0KICAgIHwgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgUmVzZXJ2ZWQgICAgICAgICAgICAgICAgICAgICAgICAgICB8
DQogICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSsNCiAgICB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgfA0KICAgICsgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICArDQogICAgfCAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwN
CiAgICArICAgICAgICAgICAgICAgICAgICAgICAgICAgQWRkcmVzc1sxXSAgICAgICAgICAgICAg
ICAgICAgICAgICAgKw0KICAgIHwgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICB8DQogICAgKyAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICsNCiAgICB8ICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfA0K
ICAgICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rDQogICAgfCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIHwNCiAgICArICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKw0KICAgIHwgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8DQog
ICAgKyAgICAgICAgICAgICAgICAgICAgICAgICAgIEFkZHJlc3NbMl0gICAgICAgICAgICAgICAg
ICAgICAgICAgICsNCiAgICB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgfA0KICAgICsgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICArDQogICAgfCAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwNCiAg
ICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKw0KICAgIC4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgLiAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAuDQogICAgLiAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAuICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIC4NCiAgICAuICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgIC4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgLg0KICAg
ICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rDQogICAgfCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIHwNCiAgICArICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKw0KICAgIHwgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8DQogICAg
KyAgICAgICAgICAgICAgICAgICAgICAgICAgIEFkZHJlc3Nbbl0gICAgICAgICAgICAgICAgICAg
ICAgICAgICsNCiAgICB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgfA0KICAgICsgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICArDQogICAgfCAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwNCiAgICAr
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKw0KDQogICBOZXh0IEhlYWRlciAgICAgICAgICA4LWJpdCBzZWxlY3Rvci4gIElkZW50
aWZpZXMgdGhlIHR5cGUgb2YgaGVhZGVyDQogICAgICAgICAgICAgICAgICAgICAgICBpbW1lZGlh
dGVseSBmb2xsb3dpbmcgdGhlIFJvdXRpbmcgaGVhZGVyLiAgVXNlcw0KICAgICAgICAgICAgICAg
ICAgICAgICAgdGhlIHNhbWUgdmFsdWVzIGFzIHRoZSBJUHY0IFByb3RvY29sIGZpZWxkDQogICAg
ICAgICAgICAgICAgICAgICAgICBbUkZDLTE3MDAgZXQgc2VxLl0uDQoNCiAgIEhkciBFeHQgTGVu
ICAgICAgICAgIDgtYml0IHVuc2lnbmVkIGludGVnZXIuICBMZW5ndGggb2YgdGhlIFJvdXRpbmcN
CiAgICAgICAgICAgICAgICAgICAgICAgIGhlYWRlciBpbiA4LW9jdGV0IHVuaXRzLCBub3QgaW5j
bHVkaW5nIHRoZSBmaXJzdA0KICAgICAgICAgICAgICAgICAgICAgICAgOCBvY3RldHMuICBGb3Ig
dGhlIFR5cGUgNCBSb3V0aW5nIGhlYWRlciwgSGRyDQogICAgICAgICAgICAgICAgICAgICAgICBF
eHQgTGVuIGlzIGVxdWFsIHRvIHR3byB0aW1lcyB0aGUgbnVtYmVyIG9mDQogICAgICAgICAgICAg
ICAgICAgICAgICBhZGRyZXNzZXMgaW4gdGhlIGhlYWRlci4gVGhlIG1heGltdW0gdmFsdWUgb2Yg
dGhpcw0KICAgICAgICAgICAgICAgICAgICAgICAgZmllbGQgY2FuIGJlIDguIFRoYXQgbWVhbnMg
YSBtYXhpbXVtIG9mIDQgYWRkcmVzc2VzDQogICAgICAgICAgICAgICAgICAgICAgICBjYW4gYmUg
YWRkZWQgdG8gdGhlIFJvdXRpbmcgSGVhZGVyLg0KDQoNCk1hbnJhbCAgICAgICAgICAgICAgICBF
eHBpcmVzIEZlYnJ1YXJ5IDI4LCAyMDA4ICAgICAgICAgICAgICAgW1BhZ2UgNF0NCgwNCkludGVy
bmV0LURyYWZ0ICAgICAgIE5ldyBJUHY2IFR5cGUgNCBSb3V0aW5nIEhlYWRlciAgICAgICAgICAg
IEp1bmUgMjAwNw0KDQoNCg0KICAgUm91dGluZyBUeXBlICAgICAgICAgNC4NCg0KICAgU2VnbWVu
dHMgTGVmdCAgICAgICAgOC1iaXQgdW5zaWduZWQgaW50ZWdlci4gIE51bWJlciBvZiByb3V0ZQ0K
ICAgICAgICAgICAgICAgICAgICAgICAgc2VnbWVudHMgcmVtYWluaW5nLCBpLmUuLCBudW1iZXIg
b2YgZXhwbGljaXRseQ0KICAgICAgICAgICAgICAgICAgICAgICAgbGlzdGVkIGludGVybWVkaWF0
ZSBub2RlcyBzdGlsbCB0byBiZSB2aXNpdGVkDQogICAgICAgICAgICAgICAgICAgICAgICBiZWZv
cmUgcmVhY2hpbmcgdGhlIGZpbmFsIGRlc3RpbmF0aW9uLg0KDQogICBSZXNlcnZlZCAgICAgICAg
ICAgICAzMi1iaXQgcmVzZXJ2ZWQgZmllbGQuICBJbml0aWFsaXplZCB0byB6ZXJvIGZvcg0KICAg
ICAgICAgICAgICAgICAgICAgICAgdHJhbnNtaXNzaW9uOyBpZ25vcmVkIG9uIHJlY2VwdGlvbi4N
Cg0KICAgQWRkcmVzc1sxLi5uXSAgICAgICAgVmVjdG9yIG9mIDEyOC1iaXQgYWRkcmVzc2VzLCBu
dW1iZXJlZCAxIHRvIG4uIFRoZQ0KICAgICAgICAgICAgICAgICAgICAgICAgbWF4aW11bSB2YWx1
ZSBvZiBuIGlzIDQuIA0KDQogICBNdWx0aWNhc3QgYWRkcmVzc2VzIG9yIExpbmsgTG9jYWwgVW5p
Y2FzdCBhZGRyZXNzIG11c3Qgbm90IGFwcGVhciBpbiBhIA0KICAgUm91dGluZyBoZWFkZXIgb2Yg
VHlwZSA0LCBvciBpbiB0aGUgSVB2NiBEZXN0aW5hdGlvbiBBZGRyZXNzIGZpZWxkIG9mIA0KICAg
YSBwYWNrZXQgY2FycnlpbmcgYSBSb3V0aW5nIGhlYWRlciBvZiBUeXBlIDQuICAgIA0KDQogICBB
IFJvdXRpbmcgaGVhZGVyIGlzIG5vdCBleGFtaW5lZCBvciBwcm9jZXNzZWQgdW50aWwgaXQgcmVh
Y2hlcyB0aGUNCiAgIG5vZGUgaWRlbnRpZmllZCBpbiB0aGUgRGVzdGluYXRpb24gQWRkcmVzcyBm
aWVsZCBvZiB0aGUgSVB2NiBoZWFkZXIuIA0KICAgVGhlcmUgY2FuIGJlIGF0IG1vc3Qgb25lIFJI
NCBoZWFkZXIgaW4gYW55IHBhY2tldC4gQSBwYWNrZXQgd2l0aCBtb3JlDQogICB0aGFuIG9uZSBS
SDQgaGVhZGVyIGlzIGRpc2NhcmRlZC4gVGhpcyBmdW5jdGlvbmFsaXR5IGNhbiBiZSBpbXBsZW1l
bnRlZCANCiAgIGluIGEgZmlyZXdhbGwgb3IgYW55IG90aGVyIElQdjYgbm9kZS4NCg0KICAgSW4g
dGhhdCBub2RlLCBkaXNwYXRjaGluZyBvbiB0aGUgTmV4dCBIZWFkZXIgZmllbGQgb2YgdGhlIGlt
bWVkaWF0ZWx5DQogICBwcmVjZWRpbmcgaGVhZGVyIGNhdXNlcyB0aGUgUm91dGluZyBoZWFkZXIg
bW9kdWxlIHRvIGJlIGludm9rZWQsDQogICB3aGljaCwgaW4gdGhlIGNhc2Ugb2YgUm91dGluZyBU
eXBlIDQsIHBlcmZvcm1zIHRoZSBhbGdvcml0aG0gd2hpY2ggaXMgDQogICBzaW1pbGFyIHRvIHRo
ZSBhcyBzcGVjaWZpZWQgaW4gc2VjdGlvbiA0LjQgb2YgW1JGQzI0NjBdOg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCk1hbnJhbCAgICAgICAgICAgICAgICBFeHBpcmVzIEZlYnJ1YXJ5IDI4LCAyMDA4
ICAgICAgICAgICAgICAgW1BhZ2UgNV0NCgwNCkludGVybmV0LURyYWZ0ICAgICAgIE5ldyBJUHY2
IFR5cGUgNCBSb3V0aW5nIEhlYWRlciAgICAgICAgICAgIEp1bmUgMjAwNw0KDQoNCiAgIGlmIFNl
Z21lbnRzIExlZnQgPSAwIHsNCiAgICAgIHByb2NlZWQgdG8gcHJvY2VzcyB0aGUgbmV4dCBoZWFk
ZXIgaW4gdGhlIHBhY2tldCwgd2hvc2UgdHlwZSBpcw0KICAgICAgaWRlbnRpZmllZCBieSB0aGUg
TmV4dCBIZWFkZXIgZmllbGQgaW4gdGhlIFJvdXRpbmcgaGVhZGVyDQogICB9DQogICBlbHNlIGlm
IEhkciBFeHQgTGVuIGlzIG9kZCB7DQogICAgICAgICBzZW5kIGFuIElDTVAgUGFyYW1ldGVyIFBy
b2JsZW0sIENvZGUgMCwgbWVzc2FnZSB0byB0aGUgU291cmNlDQogICAgICAgICBBZGRyZXNzLCBw
b2ludGluZyB0byB0aGUgSGRyIEV4dCBMZW4gZmllbGQsIGFuZCBkaXNjYXJkIHRoZQ0KICAgICAg
ICAgcGFja2V0DQogICB9DQogICBlbHNlIHsNCiAgICAgIGNvbXB1dGUgbiwgdGhlIG51bWJlciBv
ZiBhZGRyZXNzZXMgaW4gdGhlIFJvdXRpbmcgaGVhZGVyLCBieQ0KICAgICAgZGl2aWRpbmcgSGRy
IEV4dCBMZW4gYnkgMg0KDQogICAgICBpZiBTZWdtZW50cyBMZWZ0IGlzIGdyZWF0ZXIgdGhhbiBu
IG9yIG4gaXMgZ3JlYXRlciB0aGFuIDQgew0KICAgICAgICAgc2VuZCBhbiBJQ01QIFBhcmFtZXRl
ciBQcm9ibGVtLCBDb2RlIDAsIG1lc3NhZ2UgdG8gdGhlIFNvdXJjZQ0KICAgICAgICAgQWRkcmVz
cywgcG9pbnRpbmcgdG8gdGhlIFNlZ21lbnRzIExlZnQgZmllbGQsIGFuZCBkaXNjYXJkIHRoZQ0K
ICAgICAgICAgcGFja2V0DQogICAgICB9DQogICAgICBlbHNlIHsNCiAgICAgICAgIGRlY3JlbWVu
dCBTZWdtZW50cyBMZWZ0IGJ5IDE7DQogICAgICAgICBjb21wdXRlIGksIHRoZSBpbmRleCBvZiB0
aGUgbmV4dCBhZGRyZXNzIHRvIGJlIHZpc2l0ZWQgaW4NCiAgICAgICAgIHRoZSBhZGRyZXNzIHZl
Y3RvciwgYnkgc3VidHJhY3RpbmcgU2VnbWVudHMgTGVmdCBmcm9tIG4NCg0KICAgICAgICAgaWYg
QWRkcmVzcyBbaV0gb3IgdGhlIElQdjYgRGVzdGluYXRpb24gQWRkcmVzcyBpcyBtdWx0aWNhc3Qg
DQogICAgICAgICAgICBvciBsaW5rIGxvY2FsIHVuaWNhc3QgYWRkcmVzcyB7DQogICAgICAgICAg
ICBkaXNjYXJkIHRoZSBwYWNrZXQNCiAgICAgICAgIH0NCiAgICAgICAgIGVsc2Ugew0KICAgICAg
ICAgICAgQ29tcGFyZSB0aGUgYWRkcmVzc2VzIGluIHRoZSBSb3V0aW5nIEhlYWRlciB0byBjaGVj
ayB0aGF0IA0KICAgICAgICAgICAgbm9uZSBvZiB0aGUgYWRkcmVzcyBiZWxvbmcgdG8gdGhlIHJv
dXRlcnMgc2VsZiBhZGRyZXNzDQoNCiAgICAgICAgICAgIGlmIG92ZXJsYXBwaW5nIGFkZHJlc3Mg
ZXhpc3Qgew0KICAgICAgICAgICAgICAgZGlzY2FyZCB0aGUgcGFja2V0DQogICAgICAgICAgICB9
DQogIA0KICAgICAgICAgICAgc3dhcCB0aGUgSVB2NiBEZXN0aW5hdGlvbiBBZGRyZXNzIGFuZCBB
ZGRyZXNzW2ldDQoNCiAgICAgICAgICAgIGlmIHRoZSBJUHY2IEhvcCBMaW1pdCBpcyBsZXNzIHRo
YW4gb3IgZXF1YWwgdG8gMSB7DQogICAgICAgICAgICAgICBzZW5kIGFuIElDTVAgVGltZSBFeGNl
ZWRlZCAtLSBIb3AgTGltaXQgRXhjZWVkZWQgaW4NCiAgICAgICAgICAgICAgIFRyYW5zaXQgbWVz
c2FnZSB0byB0aGUgU291cmNlIEFkZHJlc3MgYW5kIGRpc2NhcmQgdGhlDQogICAgICAgICAgICAg
ICBwYWNrZXQNCiAgICAgICAgICAgIH0NCiAgICAgICAgICAgIGVsc2Ugew0KICAgICAgICAgICAg
ICAgZGVjcmVtZW50IHRoZSBIb3AgTGltaXQgYnkgMQ0KDQogICAgICAgICAgICAgICByZXN1Ym1p
dCB0aGUgcGFja2V0IHRvIHRoZSBJUHY2IG1vZHVsZSBmb3IgdHJhbnNtaXNzaW9uDQogICAgICAg
ICAgICAgICB0byB0aGUgbmV3IGRlc3RpbmF0aW9uDQogICAgICAgICAgICB9DQogICAgICAgICB9
DQogICAgICB9DQogICB9DQoNCg0KDQoNCg0KTWFucmFsICAgICAgICAgICAgICAgIEV4cGlyZXMg
RmVicnVhcnkgMjgsIDIwMDggICAgICAgICAgICAgICBbUGFnZSA2XQ0KDA0KSW50ZXJuZXQtRHJh
ZnQgICAgICAgTmV3IElQdjYgVHlwZSA0IFJvdXRpbmcgSGVhZGVyICAgICAgICAgICAgSnVuZSAy
MDA3DQoNCiANCjQuICBTZWN1cml0eSBDb25zaWRlcmF0aW9ucw0KDQogICBUaGUgcHVycG9zZSBv
ZiB0aGlzIGRvY3VtZW50IGlzIHRvIGFkZCBhIG5ldyB0eXBlIG9mIFJvdXRpbmcgZXh0ZW5zaW9u
DQogICBoZWFkZXIgb2YgSVB2Ni4gUkgwIGhhcyBiZWVuIHNob3duIHRvIGhhdmUgdW5kZXNpcmFi
bGUgc2VjdXJpdHkgDQogICBpbXBsaWNhdGlvbnMuDQogICAgDQogICBNYW55IG9mIHRoZSBhdHRh
Y2tzIGluY2x1ZGluZyB0aGUgYW1wbGlmaWNhdGlvbiBhdHRhY2sgY2Fubm90IG9jY3VyIHdpdGgg
DQogICB0aGUgUkg0IGhlYWRlci4gQWxsIHRoZSBhZGRyZXNzZXMgaW4gdGhlIFJINCBoZWFkZXIg
bmVlZCB0byBiZSBjaGVja2VkIHdpdGgNCiAgIHRoZSBmaXJld2FsbCBwb2xpY3kgdG8gbWFrZSBz
dXJlIHRoZSBmaXJld2FsbCBpcyBhYmxlIHRvIHRyYXAgcGFja2V0cyBtZWFudCANCiAgIGZvciBh
ZGRyZXNzZXMgaW4gdGhlIGZpcmV3YWxsIHBvbGljeSBhbmQgdGFrZSByZWxldmVudCBhY3Rpb24u
DQoNCiAgIFdoZXJlZXZlciBwb3NzaWJsZSwgaW5jbHVkaW5nIHRoZSBhZG1pbmlzdHJhdGl2ZSBu
ZXR3b3JrIGVkZ2UsIFJQRiBjaGVjayANCiAgIG5lZWRzIHRvIGJlIGRvbmUuDQoNCg0KNS4gIElB
TkEgQ29uc2lkZXJhdGlvbnMNCg0KICAgVGhlIElBTkEgcmVnaXN0cnkgIkludGVybmV0IFByb3Rv
Y29sIFZlcnNpb24gNiAoSVB2NikgUGFyYW1ldGVycyINCiAgIHNob3VsZCBiZSB1cGRhdGVkIHRv
IHJlZmxlY3QgdGhhdCB2YXJpYW50IDQgb2YgSVB2NiBoZWFkZXItdHlwZSA0Mw0KICAgKCJSb3V0
aW5nIEhlYWRlciIpIGlzIGFkZGVkLg0KDQoNCjcuICBBY2tub3dsZWdlbWVudHMNCg0KICAgVGhp
cyBkb2N1bWVudCBiZW5lZml0cyBmcm9tIHRoZSBjb250cmlidXRpb25zIG9mIG1hbnkgSVBWNiBh
bmQgVjZPUFMNCiAgIHdvcmtpbmcgZ3JvdXAgcGFydGljaXBhbnRzLCBpbmNsdWRpbmcgQ2hyaXMg
TW9ycm93LCBUb255IEhhaW4sIEppbm1laQ0KICAgVGF0dXlhIGFuZCBCcmlhbiBDYXJwZW50ZXIu
DQoNCg0KOC4gIFJlZmVyZW5jZXMNCg0KOC4xLiAgTm9ybWF0aXZlIFJlZmVyZW5jZXMNCg0KICAg
W1JGQzIxMTldICBCcmFkbmVyLCBTLiwgIktleSB3b3JkcyBmb3IgdXNlIGluIFJGQ3MgdG8gSW5k
aWNhdGUNCiAgICAgICAgICAgICAgUmVxdWlyZW1lbnQgTGV2ZWxzIiwgQkNQIDE0LCBSRkMgMjEx
OSwgTWFyY2ggMTk5Ny4NCg0KDQoNCk1hbnJhbCAgICAgICAgICAgICAgICBFeHBpcmVzIEZlYnJ1
YXJ5IDI4LCAyMDA4ICAgICAgICAgICAgICAgW1BhZ2UgN10NCgwNCkludGVybmV0LURyYWZ0ICAg
ICAgIE5ldyBJUHY2IFR5cGUgNCBSb3V0aW5nIEhlYWRlciAgICAgICAgICAgIEp1bmUgMjAwNw0K
DQoNCiAgIFtSRkMyNDYwXSAgRGVlcmluZywgUy4gYW5kIFIuIEhpbmRlbiwgIkludGVybmV0IFBy
b3RvY29sLCBWZXJzaW9uIDYNCiAgICAgICAgICAgICAgKElQdjYpIFNwZWNpZmljYXRpb24iLCBS
RkMgMjQ2MCwgRGVjZW1iZXIgMTk5OC4NCg0KICAgW1JGQzQyOTRdICBMb3VnaG5leSwgSi4sICJJ
UHY2IE5vZGUgUmVxdWlyZW1lbnRzIiwgUkZDIDQyOTQsDQogICAgICAgICAgICAgIEFwcmlsIDIw
MDYuDQoNCjguMi4gIEluZm9ybWF0aXZlIFJlZmVyZW5jZXMNCg0KICAgW0NhblNlY1dlc3QwN10N
CiAgICAgICAgICAgICAgQklPTkRJLCBQLiBhbmQgQS4gRUJBTEFSRCwgIklQdjYgUm91dGluZyBI
ZWFkZXIgU2VjdXJpdHkiLA0KICAgICAgICAgICAgICBDYW5TZWNXZXN0IFNlY3VyaXR5IENvbmZl
cmVuY2UgMjAwNywgQXByaWwgMjAwNy4NCg0KICAgICAgICAgICAgICBodHRwOi8vd3d3LnNlY2Rl
di5vcmcvY29uZi9JUHY2X1JIX3NlY3VyaXR5LWNzdzA3LnBkZg0KDQogICBbSS1ELmlldGYtdjZv
cHMtc2VjdXJpdHktb3ZlcnZpZXddDQogICAgICAgICAgICAgIERhdmllcywgRS4sICJJUHY2IFRy
YW5zaXRpb24vQ28tZXhpc3RlbmNlIFNlY3VyaXR5DQogICAgICAgICAgICAgIENvbnNpZGVyYXRp
b25zIiwgZHJhZnQtaWV0Zi12Nm9wcy1zZWN1cml0eS1vdmVydmlldy0wNg0KICAgICAgICAgICAg
ICAod29yayBpbiBwcm9ncmVzcyksIE9jdG9iZXIgMjAwNi4NCg0KICAgW0ktRC5zYXZvbGEtaXB2
Ni1yaC1oYS1zZWN1cml0eV0NCiAgICAgICAgICAgICAgU2F2b2xhLCBQLiwgIlNlY3VyaXR5IG9m
IElQdjYgUm91dGluZyBIZWFkZXIgYW5kIEhvbWUNCiAgICAgICAgICAgICAgQWRkcmVzcyBPcHRp
b25zIiwgZHJhZnQtc2F2b2xhLWlwdjYtcmgtaGEtc2VjdXJpdHktMDINCiAgICAgICAgICAgICAg
KHdvcmsgaW4gcHJvZ3Jlc3MpLCBNYXJjaCAyMDAyLg0KDQogICBbSS1ELnNhdm9sYS1pcHY2LXJo
LWhvc3RzXQ0KICAgICAgICAgICAgICBTYXZvbGEsIFAuLCAiTm90ZSBhYm91dCBSb3V0aW5nIEhl
YWRlciBQcm9jZXNzaW5nIG9uIElQdjYNCiAgICAgICAgICAgICAgSG9zdHMiLCBkcmFmdC1zYXZv
bGEtaXB2Ni1yaC1ob3N0cy0wMCAod29yayBpbiBwcm9ncmVzcyksDQogICAgICAgICAgICAgIEZl
YnJ1YXJ5IDIwMDIuDQoNCiAgIFtSRkMyODI3XSAgRmVyZ3Vzb24sIFAuIGFuZCBELiBTZW5pZSwg
Ik5ldHdvcmsgSW5ncmVzcyBGaWx0ZXJpbmc6DQogICAgICAgICAgICAgIERlZmVhdGluZyBEZW5p
YWwgb2YgU2VydmljZSBBdHRhY2tzIHdoaWNoIGVtcGxveSBJUCBTb3VyY2UNCiAgICAgICAgICAg
ICAgQWRkcmVzcyBTcG9vZmluZyIsIEJDUCAzOCwgUkZDIDI4MjcsIE1heSAyMDAwLg0KDQogICBb
UkZDMzcwNF0gIEJha2VyLCBGLiBhbmQgUC4gU2F2b2xhLCAiSW5ncmVzcyBGaWx0ZXJpbmcgZm9y
IE11bHRpaG9tZWQNCiAgICAgICAgICAgICAgTmV0d29ya3MiLCBCQ1AgODQsIFJGQyAzNzA0LCBN
YXJjaCAyMDA0Lg0KDQogICBbUkZDMzc3NV0gIEpvaG5zb24sIEQuLCBQZXJraW5zLCBDLiwgYW5k
IEouIEFya2tvLCAiTW9iaWxpdHkgU3VwcG9ydA0KICAgICAgICAgICAgICBpbiBJUHY2IiwgUkZD
IDM3NzUsIEp1bmUgMjAwNC4NCg0KDQpBcHBlbmRpeCBBLiAgQ2hhbmdlIEhpc3RvcnkNCg0KICAg
VGhpcyBzZWN0aW9uIHRvIGJlIHJlbW92ZWQgcHJpb3IgdG8gcHVibGljYXRpb24uDQoNCg0KDQoN
Cg0KDQpNYW5yYWwgICAgICAgICAgICAgICAgRXhwaXJlcyBGZWJydWFyeSAyOCwgMjAwOCAgICAg
ICAgICAgICAgIFtQYWdlIDhdDQoMDQpJbnRlcm5ldC1EcmFmdCAgICAgICBOZXcgSVB2NiBUeXBl
IDQgUm91dGluZyBIZWFkZXIgICAgICAgICAgICBKdW5lIDIwMDcNCg0KDQpBdXRob3JzJyBBZGRy
ZXNzZXMNCg0KICAgVmlzaHdhcyBNYW5yYWwNCiAgIElQIEluZnVzaW9uIEluYywNCiAgIEJhbWFu
a2hvbGENCiAgIEJhbnNnYWxpDQogICBBbG1vcmEgLSBVdHRhcmFuY2hhbA0KICAgUGhvbmU6ICs5
MSA5ODQ1NiA2MTkxMQ0KICAgRW1haWw6IHZpc2h3YXNAaXBpbmZ1c2lvbi5jb20NCg0KDQogICBN
YW5vaiBEdXR0YQ0KICAgSVAgSW5mdXNpb24gSW5jLA0KICAgMTI1LCBTLiBNYXJrZXQgU3RyZWV0
LA0KICAgU2FuIEpvc2UsIENBDQogICBQaG9uZTogNDA4IDc5NCAxNTAwDQogICBFbWFpbDogbWFu
b2pAaXBpbmZ1c2lvbi5jb20NCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCk1hbnJhbCAgICAgICAgICAg
ICAgICBFeHBpcmVzIEZlYnJ1YXJ5IDI4LCAyMDA4ICAgICAgICAgICAgICAgW1BhZ2UgOV0NCgwN
CkludGVybmV0LURyYWZ0ICAgICAgIE5ldyBJUHY2IFR5cGUgNCBSb3V0aW5nIEhlYWRlciAgICAg
ICAgICAgIEp1bmUgMjAwNw0KDQoNCkZ1bGwgQ29weXJpZ2h0IFN0YXRlbWVudA0KDQogICBDb3B5
cmlnaHQgKEMpIFRoZSBJRVRGIFRydXN0ICgyMDA3KS4NCg0KICAgVGhpcyBkb2N1bWVudCBpcyBz
dWJqZWN0IHRvIHRoZSByaWdodHMsIGxpY2Vuc2VzIGFuZCByZXN0cmljdGlvbnMNCiAgIGNvbnRh
aW5lZCBpbiBCQ1AgNzgsIGFuZCBleGNlcHQgYXMgc2V0IGZvcnRoIHRoZXJlaW4sIHRoZSBhdXRo
b3JzDQogICByZXRhaW4gYWxsIHRoZWlyIHJpZ2h0cy4NCg0KICAgVGhpcyBkb2N1bWVudCBhbmQg
dGhlIGluZm9ybWF0aW9uIGNvbnRhaW5lZCBoZXJlaW4gYXJlIHByb3ZpZGVkIG9uIGFuDQogICAi
QVMgSVMiIGJhc2lzIGFuZCBUSEUgQ09OVFJJQlVUT1IsIFRIRSBPUkdBTklaQVRJT04gSEUvU0hF
IFJFUFJFU0VOVFMNCiAgIE9SIElTIFNQT05TT1JFRCBCWSAoSUYgQU5ZKSwgVEhFIElOVEVSTkVU
IFNPQ0lFVFksIFRIRSBJRVRGIFRSVVNUIEFORA0KICAgVEhFIElOVEVSTkVUIEVOR0lORUVSSU5H
IFRBU0sgRk9SQ0UgRElTQ0xBSU0gQUxMIFdBUlJBTlRJRVMsIEVYUFJFU1MNCiAgIE9SIElNUExJ
RUQsIElOQ0xVRElORyBCVVQgTk9UIExJTUlURUQgVE8gQU5ZIFdBUlJBTlRZIFRIQVQgVEhFIFVT
RSBPRg0KICAgVEhFIElORk9STUFUSU9OIEhFUkVJTiBXSUxMIE5PVCBJTkZSSU5HRSBBTlkgUklH
SFRTIE9SIEFOWSBJTVBMSUVEDQogICBXQVJSQU5USUVTIE9GIE1FUkNIQU5UQUJJTElUWSBPUiBG
SVRORVNTIEZPUiBBIFBBUlRJQ1VMQVIgUFVSUE9TRS4NCg0KDQpJbnRlbGxlY3R1YWwgUHJvcGVy
dHkNCg0KICAgVGhlIElFVEYgdGFrZXMgbm8gcG9zaXRpb24gcmVnYXJkaW5nIHRoZSB2YWxpZGl0
eSBvciBzY29wZSBvZiBhbnkNCiAgIEludGVsbGVjdHVhbCBQcm9wZXJ0eSBSaWdodHMgb3Igb3Ro
ZXIgcmlnaHRzIHRoYXQgbWlnaHQgYmUgY2xhaW1lZCB0bw0KICAgcGVydGFpbiB0byB0aGUgaW1w
bGVtZW50YXRpb24gb3IgdXNlIG9mIHRoZSB0ZWNobm9sb2d5IGRlc2NyaWJlZCBpbg0KICAgdGhp
cyBkb2N1bWVudCBvciB0aGUgZXh0ZW50IHRvIHdoaWNoIGFueSBsaWNlbnNlIHVuZGVyIHN1Y2gg
cmlnaHRzDQogICBtaWdodCBvciBtaWdodCBub3QgYmUgYXZhaWxhYmxlOyBub3IgZG9lcyBpdCBy
ZXByZXNlbnQgdGhhdCBpdCBoYXMNCiAgIG1hZGUgYW55IGluZGVwZW5kZW50IGVmZm9ydCB0byBp
ZGVudGlmeSBhbnkgc3VjaCByaWdodHMuICBJbmZvcm1hdGlvbg0KICAgb24gdGhlIHByb2NlZHVy
ZXMgd2l0aCByZXNwZWN0IHRvIHJpZ2h0cyBpbiBSRkMgZG9jdW1lbnRzIGNhbiBiZQ0KICAgZm91
bmQgaW4gQkNQIDc4IGFuZCBCQ1AgNzkuDQoNCiAgIENvcGllcyBvZiBJUFIgZGlzY2xvc3VyZXMg
bWFkZSB0byB0aGUgSUVURiBTZWNyZXRhcmlhdCBhbmQgYW55DQogICBhc3N1cmFuY2VzIG9mIGxp
Y2Vuc2VzIHRvIGJlIG1hZGUgYXZhaWxhYmxlLCBvciB0aGUgcmVzdWx0IG9mIGFuDQogICBhdHRl
bXB0IG1hZGUgdG8gb2J0YWluIGEgZ2VuZXJhbCBsaWNlbnNlIG9yIHBlcm1pc3Npb24gZm9yIHRo
ZSB1c2Ugb2YNCiAgIHN1Y2ggcHJvcHJpZXRhcnkgcmlnaHRzIGJ5IGltcGxlbWVudGVycyBvciB1
c2VycyBvZiB0aGlzDQogICBzcGVjaWZpY2F0aW9uIGNhbiBiZSBvYnRhaW5lZCBmcm9tIHRoZSBJ
RVRGIG9uLWxpbmUgSVBSIHJlcG9zaXRvcnkgYXQNCiAgIGh0dHA6Ly93d3cuaWV0Zi5vcmcvaXBy
Lg0KDQogICBUaGUgSUVURiBpbnZpdGVzIGFueSBpbnRlcmVzdGVkIHBhcnR5IHRvIGJyaW5nIHRv
IGl0cyBhdHRlbnRpb24gYW55DQogICBjb3B5cmlnaHRzLCBwYXRlbnRzIG9yIHBhdGVudCBhcHBs
aWNhdGlvbnMsIG9yIG90aGVyIHByb3ByaWV0YXJ5DQogICByaWdodHMgdGhhdCBtYXkgY292ZXIg
dGVjaG5vbG9neSB0aGF0IG1heSBiZSByZXF1aXJlZCB0byBpbXBsZW1lbnQNCiAgIHRoaXMgc3Rh
bmRhcmQuICBQbGVhc2UgYWRkcmVzcyB0aGUgaW5mb3JtYXRpb24gdG8gdGhlIElFVEYgYXQNCiAg
IGlldGYtaXByQGlldGYub3JnLg0KDQoNCkFja25vd2xlZGdtZW50DQoNCiAgIEZ1bmRpbmcgZm9y
IHRoZSBSRkMgRWRpdG9yIGZ1bmN0aW9uIGlzIHByb3ZpZGVkIGJ5IHRoZSBJRVRGDQogICBBZG1p
bmlzdHJhdGl2ZSBTdXBwb3J0IEFjdGl2aXR5IChJQVNBKS4NCg0KDQoNCg0KDQpNYW5yYWwgICAg
ICAgICAgICAgICAgRXhwaXJlcyBGZWJydWFyeSAyOCwgMjAwOCAgICAgICAgICAgICAgIFtQYWdl
IDEwXQ0KDA0K
------=_Part_44349_3767356.1188289912490
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

------=_Part_44349_3767356.1188289912490--




From ipv6-bounces@ietf.org Tue Aug 28 05:06:26 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPwzo-0005dI-OY; Tue, 28 Aug 2007 05:04:24 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPwzn-0005dA-Q6
	for ipv6@ietf.org; Tue, 28 Aug 2007 05:04:23 -0400
Received: from salmon.maths.tcd.ie ([134.226.81.11])
	by chiedprmail1.ietf.org with smtp (Exim 4.43) id 1IPwzk-0001wW-Tu
	for ipv6@ietf.org; Tue, 28 Aug 2007 05:04:21 -0400
Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie)
	by salmon.maths.tcd.ie with SMTP id <aa04023@salmon>;
	28 Aug 2007 10:04:19 +0100 (BST)
Date: Tue, 28 Aug 2007 10:04:14 +0100
From: David Malone <dwmalone@maths.tcd.ie>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Message-ID: <20070828090414.GA67414@walton.maths.tcd.ie>
References: <Pine.GSO.4.20.0708271348200.6917-100000@meno.corp.us.uu.net>
	<46D32BB2.1030908@ericsson.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46D32BB2.1030908@ericsson.com>
User-Agent: Mutt/1.5.6i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: ipv6@ietf.org, jason.schiller@verizonbusiness.com
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Mon, Aug 27, 2007 at 03:53:22PM -0400, Suresh Krishnan wrote:
> >I would be curious how people feel about these choices if they also apply
> >to (as they should) IPv4 source routing.

> I think the problems, though overlapping, are completely different in 
> magnitude. The problem with IPv4 source routing is not AS SEVERE as the 
> problem with RH0.

Actually - I've a feeling that at the time the problems with IPv4
source routing were discussed, they would have been considered more
severe. They allowed remote user (or maybe even root) level access
to many systems. At the time DoSes weren't considered so serious.
Today, a DoS, even with a magnification factor of 80 or so, is
probably less severe in my mind. YMMV...

	David.

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



From ipv6-bounces@ietf.org Tue Aug 28 05:52:35 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPxib-0005Hx-H7; Tue, 28 Aug 2007 05:50:41 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPxiZ-0005Hs-3L
	for ipv6@ietf.org; Tue, 28 Aug 2007 05:50:39 -0400
Received: from [2001:6f8:387:2057:ea05:e98a:6f83:d890] (helo=moog.chdir.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IPxiX-0005Xs-Pa
	for ipv6@ietf.org; Tue, 28 Aug 2007 05:50:39 -0400
Received: from aputeaux-152-1-72-30.w83-204.abo.wanadoo.fr ([83.204.237.30]
	helo=localhost.localdomain)
	by moog.chdir.org with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.63) (envelope-from <arno@natisbad.org>)
	id 1IPxiV-0002lF-8n; Tue, 28 Aug 2007 11:50:35 +0200
From: arno@natisbad.org (Arnaud Ebalard)
To: Vishwas Manral <vishwas.ietf@gmail.com>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
X-GnuPG-Key: 0x047A5026
X-Hashcash: 1:20:070828:vishwas.ietf@gmail.com::0Cuv3NMgEpDqOpR/:0000000000000000000000000000000000000001vDo
X-Hashcash: 1:20:070828:ipv6@ietf.org::TRnrSeedAUF6LoCF:00002i1g
X-Hashcash: 1:20:070828:manoj@ipinfusion.com::/zf787oqvr8Fq2jF:000000000000000000000000000000000000000004k3a
Date: Tue, 28 Aug 2007 11:50:33 +0200
In-Reply-To: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	(Vishwas Manral's message of "Tue, 28 Aug 2007 10:31:52 +0200")
Message-ID: <87zm0cvvh2.fsf@natisbad.org>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.95 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Cc: manoj@ipinfusion.com, IPv6 WG <ipv6@ietf.org>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Vishwas, Hi *,

Vishwas Manral <vishwas.ietf@gmail.com> writes:

> Hi,
>
> Based on feedback from the group, we have written a draft for a new
> routing header. The functionality is the same as the RH0. The draft
> will soon be posted to the IETF site.
>
> The main differences are:
>
> 1. Maximum up to 4 addresses in the header. (the number is based on
> the reply I got for the question about the usage scenarios in operator
> environments).
> 2. Only one header in each packet.
> 3. Firewall policy reccomendation.
> 4. RPF reccomendation.
>
> Please have a look and let us know your comments.

It seems the draft intends to update RFC 2460. Does it imply that RH4
would be mandatory to implement in all IPv6 stacks? It's probably me but
I don't see the point in adding complexity to IPv6 stacks (_all_
implementations shipped), especially when the functionality has already
been proven to have an almost null usefulness.


Below are commented quotes from the draft :

>  The RH4 header has format and functionality similar to the RH0 header
>  without having the major vulnerabilities of the "Routing Header". 

Efforts to get a new RH type defined will certainly require more than
having only major vulnerabilities removed compared to RH0. Having _all_
vulnerabilities mitigated would be more respectful of past discussions
regarding RH0 and time already spent on it.


>  A Routing header is not examined or processed until it reaches the 
>  node identified in the Destination Address field of the IPv6 header.  
>  There can be at most one RH4 header in any packet. A packet with more 
>  than one RH4 header is discarded. This functionality can be
>  implemented in a firewall or any other IPv6 node.

First part of that paragraph states that packets are not checked
en-route but the second part states the opposite (you clearly need to
examine the RH to get the type). The sentence "A packet ... is
discarded" is to vague. Next sentence too.


> 4.  Security Considerations
>
>   The purpose of this document is to add a new type of Routing extension
>   header of IPv6. RH0 has been shown to have undesirable security 
>   implications.
>    
>   Many of the attacks including the amplification attack cannot occur with 
>   the RH4 header. All the addresses in the RH4 header need to be checked with
>   the firewall policy to make sure the firewall is able to trap packets meant 
>   for addresses in the firewall policy and take relevent action.
>
>   Whereever possible, including the administrative network edge, RPF check 
>   needs to be done.


"Many of the attacks ... ": unlike in the IPv6 specification, the
security assessment of the mechanism (threats, impacts, mitigation)
should be done to describe what remains. 

"All the addresses need ...": what does it mean precisely ?

"Whereever possible, ...": this is a common statement. What's the
precise purpose? What if it is not done (i.e. impact in that case)?



After a first reading of the draft, my main feeling is that the
functionality is not precisely defined because the intended use is not
clearly stated: the purpose does not seem to be the addition of something
which would serve some categories of users. It's more oriented towards
the limited reduction of the level of threat associated with RH0 in
order to make it "acceptable". It's adding complexity without
considering the real need (if any).

The problem of the processing (by nodes, routers, both, default policy)
is not clearly covered. This was a problem in 2460. Who should implement
that? Will your IPv6-enabled Mobile phone have that "feature"?

Ability to source-route a packet is basically the ability to "coerce" a
remote node to send traffic towards a specific destination. In MIPv6,
final destination in RH2 (HoA) is always locally available on the
targeted node (the one the packet is sent to using the CoA). And before
a node even sends traffic to a CoA, the proof of ownership of the
address by the peer has always been made, i.e. to be able to have
someone follow you in that direction, you have to prove your ownership
of the targeted address, which is precisely your ability to _both_
receive/emit traffic at/from that address.

Having intermediate waypoints (i.e. 4 addresses) while keeping the same
level of protection as the one provided by RH2 for the Internet
infrastructure is IMHO not so easily feasible.

IMHO, you should:

 - assess the real use of your new RH (context, scope, purpose)
 - see the needs in term of checks, limitation, filtering
 - define the mechanism based on generic RH
 - check against all previously described threats (available in
   reference documents)
 - see what remains in terms of threats and impacts against the IPv6
   infrastructure and if it is worth the trouble.

A general question I have on the topic is the following: is the ability
to "bypass" anycast routing scheme considered a problem or is it ok? I'd
like to hear on that point from people that use that kind of setup for
protection against DoS in large scale deployment (DNS servers, 6to4
relay routers, ...).

Regards,

a+



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



From ipv6-bounces@ietf.org Tue Aug 28 06:25:11 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IPyE1-0003GB-BX; Tue, 28 Aug 2007 06:23:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IPyE0-0003G5-9y
	for ipv6@ietf.org; Tue, 28 Aug 2007 06:23:08 -0400
Received: from an-out-0708.google.com ([209.85.132.247])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IPyDz-00067T-3c
	for ipv6@ietf.org; Tue, 28 Aug 2007 06:23:08 -0400
Received: by an-out-0708.google.com with SMTP id c17so264564anc
	for <ipv6@ietf.org>; Tue, 28 Aug 2007 03:23:06 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=Dxz2Ydu8z9I6gXJX9S84tDJH3dEMg6rF/7aQMkkzhzYBmByv1AiS29ET9T/f+Vo41tRI7Gg3tWbvWW8em544mm2hClFWPrlxm+2ReNauth8D6VtkbDDpCxcEv+c0nuzooDnG3RDwGuESJG6KKAlNhDvnmm9rytBkWAEZmFmfa+8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=JIKyzTn9m4r3gOw1e5qUowbUTppBlpy6ioWUQ506JohDv/j/IgfCpgIPWbfTe/9+fV7+49lWUHcG9IbtbHaDh0HwnlzLwdq5eoKod+7aN1SC8o4TZY00IiAyfAcBzn4m/SuX1GESj+OwZGuGJSobPHXp2mFv5nsmmPkXW6H+nCo=
Received: by 10.142.157.15 with SMTP id f15mr375495wfe.1188296585814;
	Tue, 28 Aug 2007 03:23:05 -0700 (PDT)
Received: by 10.142.84.8 with HTTP; Tue, 28 Aug 2007 03:23:05 -0700 (PDT)
Message-ID: <77ead0ec0708280323t52e852adlfdb3133009de0b7a@mail.gmail.com>
Date: Tue, 28 Aug 2007 20:23:05 +1000
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Arnaud Ebalard" <arno@natisbad.org>
In-Reply-To: <87zm0cvvh2.fsf@natisbad.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<87zm0cvvh2.fsf@natisbad.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
Cc: manoj@ipinfusion.com, IPv6 WG <ipv6@ietf.org>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Arnaud,

> It seems the draft intends to update RFC 2460. Does it imply that RH4
> would be mandatory to implement in all IPv6 stacks? It's probably me but
> I don't see the point in adding complexity to IPv6 stacks (_all_
> implementations shipped), especially when the functionality has already
> been proven to have an almost null usefulness.
Yes, the intent is to update RFC2460 and implies its a mandatory to
implement functionality. I had thought the same too, but if you see a
past thread, I did get use cases for the RH4 functionality.

> Below are commented quotes from the draft :
>
> >  The RH4 header has format and functionality similar to the RH0 header
> >  without having the major vulnerabilities of the "Routing Header".
>
> Efforts to get a new RH type defined will certainly require more than
> having only major vulnerabilities removed compared to RH0. Having _all_
> vulnerabilities mitigated would be more respectful of past discussions
> regarding RH0 and time already spent on it.
I agree. Well in my view, we have to see what is practically possible,
and can be done without overloading the router CPU. We intend to go as
far as we can with this. In my view this is the initial version of the
draft and we do intend to update the draft as we move forward.

> >  A Routing header is not examined or processed until it reaches the
> >  node identified in the Destination Address field of the IPv6 header.
> >  There can be at most one RH4 header in any packet. A packet with more
> >  than one RH4 header is discarded. This functionality can be
> >  implemented in a firewall or any other IPv6 node.
>
> First part of that paragraph states that packets are not checked
> en-route but the second part states the opposite (you clearly need to
> examine the RH to get the type). The sentence "A packet ... is
> discarded" is to vague. Next sentence too.
I guess the point I am trying to make is the algorithm given below
should only be implemented by the destination node, however the
discarding of malicious packets can be done by a firewall. I will
clarify the text for the same.

>

> "Many of the attacks ... ": unlike in the IPv6 specification, the
> security assessment of the mechanism (threats, impacts, mitigation)
> should be done to describe what remains.
>
> "All the addresses need ...": what does it mean precisely ?
I mean the IPv6 addresses included in the routing header - RH4.

> "Whereever possible, ...": this is a common statement. What's the
> precise purpose? What if it is not done (i.e. impact in that case)?
Well the idea is RPF check cannot be done, in all scenarios. The
simple case is that routing over the internet is asymmetric, and RPF
checks cannot be applied. However such checks can be made at the edge
of the networks.

> After a first reading of the draft, my main feeling is that the
> functionality is not precisely defined because the intended use is not
> clearly stated: the purpose does not seem to be the addition of something
> which would serve some categories of users. It's more oriented towards
> the limited reduction of the level of threat associated with RH0 in
> order to make it "acceptable". It's adding complexity without
> considering the real need (if any).
>
> The problem of the processing (by nodes, routers, both, default policy)
> is not clearly covered. This was a problem in 2460. Who should implement
> that? Will your IPv6-enabled Mobile phone have that "feature"?
>
> Ability to source-route a packet is basically the ability to "coerce" a
> remote node to send traffic towards a specific destination. In MIPv6,
> final destination in RH2 (HoA) is always locally available on the
> targeted node (the one the packet is sent to using the CoA). And before
> a node even sends traffic to a CoA, the proof of ownership of the
> address by the peer has always been made, i.e. to be able to have
> someone follow you in that direction, you have to prove your ownership
> of the targeted address, which is precisely your ability to _both_
> receive/emit traffic at/from that address.
>
> Having intermediate waypoints (i.e. 4 addresses) while keeping the same
> level of protection as the one provided by RH2 for the Internet
> infrastructure is IMHO not so easily feasible.
>
> IMHO, you should:
>
>  - assess the real use of your new RH (context, scope, purpose)
>  - see the needs in term of checks, limitation, filtering
>  - define the mechanism based on generic RH
>  - check against all previously described threats (available in
>    reference documents)
>  - see what remains in terms of threats and impacts against the IPv6
>    infrastructure and if it is worth the trouble.
I agree. Infact if you see the mails from me on the list that is the
direction I have taken. I have asked questions on what are real use
scenarios for the same.

I will update the draft based on comments from you. this draft is
there to spur a discussion on the subject.

Thanks a lot for your comments,
Vishwas

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



From ipv6-bounces@ietf.org Tue Aug 28 10:30:16 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQ23E-0007Vx-4A; Tue, 28 Aug 2007 10:28:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQ23D-0007Vo-1b
	for ipv6@ietf.org; Tue, 28 Aug 2007 10:28:15 -0400
Received: from mailb.microsoft.com ([131.107.115.215] helo=smtp.microsoft.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQ23B-0003Mv-QU
	for ipv6@ietf.org; Tue, 28 Aug 2007 10:28:15 -0400
Received: from TK5-EXHUB-C101.redmond.corp.microsoft.com (157.54.70.76) by
	TK5-EXGWY-E802.partners.extranet.microsoft.com (10.251.56.168) with
	Microsoft
	SMTP Server (TLS) id 8.1.177.2; Tue, 28 Aug 2007 07:28:13 -0700
Received: from tk5-exmlt-w601.wingroup.windeploy.ntdev.microsoft.com
	(157.54.70.16) by TK5-EXHUB-C101.redmond.corp.microsoft.com
	(157.54.70.76)
	with Microsoft SMTP Server id 8.1.177.1; Tue, 28 Aug 2007 07:28:13 -0700
Received: from WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com
	(157.54.62.26) by TK5-EXMLT-W601.wingroup.windeploy.ntdev.microsoft.com
	(157.54.70.16) with Microsoft SMTP Server id 8.1.122.1; Tue, 28 Aug 2007
	07:28:12 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 28 Aug 2007 07:27:33 -0700
Message-ID: <70C6EFCDFC8AAD418EF7063CD132D06405967C24@WIN-MSG-21.wingroup.windeploy.ntdev.microsoft.com>
In-Reply-To: <77ead0ec0708280323t52e852adlfdb3133009de0b7a@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New Routing Header!!!
Thread-Index: AcfpXX753EvBMCg+R1Wnakj8cnd/lwAIZIWQ
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com><87zm0cvvh2.fsf@natisbad.org>
	<77ead0ec0708280323t52e852adlfdb3133009de0b7a@mail.gmail.com>
From: Christian Huitema <huitema@windows.microsoft.com>
To: Vishwas Manral <vishwas.ietf@gmail.com>, Arnaud Ebalard <arno@natisbad.org>
X-Spam-Score: -108.0 (---------------------------------------------------)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: manoj@ipinfusion.com, IPv6 WG <ipv6@ietf.org>
Subject: RE: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Before we invent a new header, have we looked at ways were the current
legitimate usage could be solved by dedicated applications? Something in
the spirit of traceroute, maybe with a little cooperation from the
involved players in the spirit of UDP echo? Specialized applications
open a much smaller attack surface than an IPv6 layer mechanism. They
are also easier to secure using end-to-end mechanisms.

-- Christian Huitema




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



From ipv6-bounces@ietf.org Tue Aug 28 12:13:37 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQ3f7-00048U-Bw; Tue, 28 Aug 2007 12:11:29 -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>
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: 
Subject: Re: [dhcwg] Re: Rethinking autoconfig,
	was Re: prefix length determination for DHCPv6
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-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.



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



From ipv6-bounces@ietf.org Tue Aug 28 23:47:38 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQEUb-0008Q6-SM; Tue, 28 Aug 2007 23:45:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQEUa-0008IP-DR
	for ipv6@ietf.org; Tue, 28 Aug 2007 23:45:20 -0400
Received: from wa-out-1112.google.com ([209.85.146.179])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQEUZ-0002oZ-5a
	for ipv6@ietf.org; Tue, 28 Aug 2007 23:45:20 -0400
Received: by wa-out-1112.google.com with SMTP id k40so47204wah
	for <ipv6@ietf.org>; Tue, 28 Aug 2007 20:45:16 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=ZWcIXexBwkFr1RoOXUb1Mjrvyu21WgmeZlREXpSihX2eiGTlYWBAGisvAg8ckdc04kQyAlaob30Nu5uEIDWDY/bcR9w40oUrHj1ggaV8+ontFsuRMBj9ReE4TfCqnDC9ywMhiu24sFayahq75WtbsmYcWGMEfetV74wCjCeC1L4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=q0I8vlxImGqJ0g541pGwvqW/v2djXITQpehDy4YpVAueF0u472K+SWNs3lwWUCgSYlT1featzhq3Jwz7pMuwyyzkzsHUmA0b1TdcGUzRcwrJxkms8giw8f03qbTXMV6A4m8j005w8XYJz6Z5fz/EU7mJJJVjXLOSKAkbSzkvNQY=
Received: by 10.114.199.1 with SMTP id w1mr116516waf.1188359115404;
	Tue, 28 Aug 2007 20:45:15 -0700 (PDT)
Received: by 10.114.94.12 with HTTP; Tue, 28 Aug 2007 20:45:15 -0700 (PDT)
Message-ID: <75cb24520708282045g475f32ecic7284a083cebcd3d@mail.gmail.com>
Date: Tue, 28 Aug 2007 23:45:15 -0400
From: "Christopher Morrow" <christopher.morrow@gmail.com>
To: "David Malone" <dwmalone@maths.tcd.ie>
In-Reply-To: <20070828090414.GA67414@walton.maths.tcd.ie>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <Pine.GSO.4.20.0708271348200.6917-100000@meno.corp.us.uu.net>
	<46D32BB2.1030908@ericsson.com>
	<20070828090414.GA67414@walton.maths.tcd.ie>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: ipv6@ietf.org, Suresh Krishnan <suresh.krishnan@ericsson.com>,
	jason.schiller@verizonbusiness.com
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 8/28/07, David Malone <dwmalone@maths.tcd.ie> wrote:
> On Mon, Aug 27, 2007 at 03:53:22PM -0400, Suresh Krishnan wrote:
> > >I would be curious how people feel about these choices if they also apply
> > >to (as they should) IPv4 source routing.
>
> > I think the problems, though overlapping, are completely different in
> > magnitude. The problem with IPv4 source routing is not AS SEVERE as the
> > problem with RH0.
>

The 'problem' with source-routing is that people forgot that it
exists, plain and simple. Then someone stood up and said, look! with
source-routing I can ... source-route packets! and I can do 'bad
things'.

Then people got all flakey and decided we better just turn that off
and remove it from the protocol :( people haven't removed ICMP from
the earth and it's been responsible for more 'security incidents' over
time than source-routing. The same goes for http for that matter.

> Actually - I've a feeling that at the time the problems with IPv4
> source routing were discussed, they would have been considered more
> severe. They allowed remote user (or maybe even root) level access
> to many systems. At the time DoSes weren't considered so serious.

Yup, and someone/no-one noted this as a real concern with ipv6 RH0,
everyone focused on the least interesting problem and decided to
shutdown RHO and excise it from the protocol... a blatant knee jerk
reaction. It's interesting to me that this blatant knee jerk reaction
is getting a base protocol level change, yet locator/id split isn't.
It's interesting that folks feel in this instance ipv6 is 'less used
and less critical' and thus able to be changed where in the locator/id
split discussion that argument was not acceptable.

'hypocrisy' I think is the word I'm looking for?

> Today, a DoS, even with a magnification factor of 80 or so, is
> probably less severe in my mind. YMMV...
>

and 80x magnification is a problem... but in this case (and in many
other cases of same) there are simple solutions that could/should be
used. Solutions which don't require base protocol changes.

-Chris

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



From ipv6-bounces@ietf.org Wed Aug 29 03:58:24 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQIPM-0006zQ-Tf; Wed, 29 Aug 2007 03:56:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQIPL-0006v9-MP
	for ipv6@ietf.org; Wed, 29 Aug 2007 03:56:11 -0400
Received: from [2001:6f8:387:2057:ea05:e98a:6f83:d890] (helo=moog.chdir.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQIPL-00087y-6r
	for ipv6@ietf.org; Wed, 29 Aug 2007 03:56:11 -0400
Received: from aputeaux-152-1-16-182.w82-120.abo.wanadoo.fr ([82.120.46.182]
	helo=localhost.localdomain)
	by moog.chdir.org with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.63) (envelope-from <arno@natisbad.org>)
	id 1IQIP8-0001RX-42; Wed, 29 Aug 2007 09:55:58 +0200
From: arno@natisbad.org (Arnaud Ebalard)
To: "Christopher Morrow" <christopher.morrow@gmail.com>
References: <Pine.GSO.4.20.0708271348200.6917-100000@meno.corp.us.uu.net>
	<46D32BB2.1030908@ericsson.com>
	<20070828090414.GA67414@walton.maths.tcd.ie>
	<75cb24520708282045g475f32ecic7284a083cebcd3d@mail.gmail.com>
X-GnuPG-Key: 0x047A5026
X-Hashcash: 1:20:070829:christopher.morrow@gmail.com::Z3ENvmEZUv+DxEKk:0000000000000000000000000000000005o/p
X-Hashcash: 1:20:070829:suresh.krishnan@ericsson.com::OD45OMR/ZJciw63v:0000000000000000000000000000000002BPG
X-Hashcash: 1:20:070829:dwmalone@maths.tcd.ie::BCuqUeBrcd5zxDn9:00000000000000000000000000000000000000002qlZ
X-Hashcash: 1:20:070829:ipv6@ietf.org::RZeNala617k4lhR4:00002vvf
X-Hashcash: 1:20:070829:jason.schiller@verizonbusiness.com::Ryokct1j70BRlJq3:000000000000000000000000000788M
Date: Wed, 29 Aug 2007 09:55:56 +0200
In-Reply-To: <75cb24520708282045g475f32ecic7284a083cebcd3d@mail.gmail.com>
	(Christopher Morrow's message of "Tue, 28 Aug 2007 23:45:15 -0400")
Message-ID: <873ay2ixkj.fsf@natisbad.org>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.95 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: David Malone <dwmalone@maths.tcd.ie>, ipv6@ietf.org,
	Suresh Krishnan <suresh.krishnan@ericsson.com>,
	jason.schiller@verizonbusiness.com
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi,

"Christopher Morrow" <christopher.morrow@gmail.com> writes:

> and 80x magnification is a problem... but in this case (and in many
> other cases of same) there are simple solutions that could/should be
> used. Solutions which don't require base protocol changes.

Can you describe those _simple_ solutions and compare them with the
deprecation? ;-)

IMHO, the real problem is that RH0 should not have been in the IPv6
specifications (1883 _and_ 2460) and the associated time/space could
have been used, as you wrote, for something more useful. 

locator/id split is actually one of such things, but having it directly
in IP has pros and cons. Keeping IPv6 simple and efficient allows
building on top of it (like MIPv6 does) with some insurance on resulting
stability.

Regards,

a+

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



From ipv6-bounces@ietf.org Wed Aug 29 10:11:52 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQOEd-0008PZ-6q; Wed, 29 Aug 2007 10:09:31 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQOEa-0008EY-O0
	for ipv6@ietf.org; Wed, 29 Aug 2007 10:09:28 -0400
Received: from e2.ny.us.ibm.com ([32.97.182.142])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQOEZ-0000cx-6K
	for ipv6@ietf.org; Wed, 29 Aug 2007 10:09:28 -0400
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236])
	by e2.ny.us.ibm.com (8.13.8/8.13.8) with ESMTP id l7TE97Cq027602
	for <ipv6@ietf.org>; Wed, 29 Aug 2007 10:09:07 -0400
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216])
	by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v8.5) with ESMTP id
	l7TE9741477154 for <ipv6@ietf.org>; Wed, 29 Aug 2007 10:09:07 -0400
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1])
	by d01av02.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l7TE97Z5008856 for <ipv6@ietf.org>; Wed, 29 Aug 2007 10:09:07 -0400
Received: from cichlid.raleigh.ibm.com (wecm-9-67-159-36.wecm.ibm.com
	[9.67.159.36])
	by d01av02.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l7TE96fO008818
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 29 Aug 2007 10:09:06 -0400
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 l7TE8eJO029246;
	Wed, 29 Aug 2007 10:08:45 -0400
Message-Id: <200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
To: "Vishwas Manral" <vishwas.ietf@gmail.com>
In-reply-to: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
Comments: In-reply-to "Vishwas Manral" <vishwas.ietf@gmail.com>
	message dated "Tue, 28 Aug 2007 18:31:52 +1000."
Date: Wed, 29 Aug 2007 10:08:40 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: manoj@ipinfusion.com, IPv6 WG <ipv6@ietf.org>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Sorry to interrupt, but I'd suggest that working on a new RH design is
mostly a waste of time at this point.

Can we please _first_ identify a user/customer for a proposed RH, so
we are sure we actually design something useful? And at the same time
be sure we have a transition strategy for getting it
implemented/deployed that makes sense (i.e., doesn't require upgrading
parts of the infrastructure outside of the control of those wanting to
take advantage of the RH?)

I.e., exactly what _real_ problem are we trying to solve here?

The idea that we can define something (with no clear expected use) and
get it actually implemented and deployed is mostly naive. (My guess is
this would be an _optional_ standard, and vendors mostly wouldn't
bother to implement it -- if no one actually needs it).

One can argue that the whole RH0 debacle results from designing
functionality for which there was no clear customer/use. Time and time
again, this sort of protocol design results in (at best) wasted
effort.

Thomas

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



From ipv6-bounces@ietf.org Wed Aug 29 10:25:51 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQOSe-0004fi-Fx; Wed, 29 Aug 2007 10:24:00 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQOSc-0004fa-M5
	for ipv6@ietf.org; Wed, 29 Aug 2007 10:23:58 -0400
Received: from e36.co.us.ibm.com ([32.97.110.154])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQOSc-0002UN-11
	for ipv6@ietf.org; Wed, 29 Aug 2007 10:23:58 -0400
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com
	[9.17.195.106])
	by e36.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l7TENWqu019887
	for <ipv6@ietf.org>; Wed, 29 Aug 2007 10:23:32 -0400
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169])
	by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v8.5) with ESMTP id
	l7TENT4w405688 for <ipv6@ietf.org>; Wed, 29 Aug 2007 08:23:30 -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
	l7TENTXt004825 for <ipv6@ietf.org>; Wed, 29 Aug 2007 08:23:29 -0600
Received: from cichlid.raleigh.ibm.com (wecm-9-67-159-36.wecm.ibm.com
	[9.67.159.36])
	by d03av03.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l7TENRIT004658
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 29 Aug 2007 08:23:29 -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 l7TENQZ8000329;
	Wed, 29 Aug 2007 10:23:26 -0400
Message-Id: <200708291423.l7TENQZ8000329@cichlid.raleigh.ibm.com>
To: briand@ca.afilias.info
In-reply-to: <63886.74.122.168.81.1188025388.squirrel@look.libertyrms.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.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>
	<471515FC-E1E1-4C83-99AA-A9821E0C2FF5@muada.com> <!
	63886.74.122.168.81.1188025388.squirrel@look.libertyrms.com>
Comments: In-reply-to briand@ca.afilias.info
	message dated "Sat, 25 Aug 2007 03:03:08 -0400."
Date: Wed, 29 Aug 2007 10:23:26 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: History of autoconfig RFCs and siblings, please?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

briand@ca.afilias.info writes:

> I was attempting to get to the bottom of what is, to me, a mystery:

> Why does IPv6 use EUI-64 for Interface Identifiers, instead of MAC-48?

> The previous version of the RFCs used MAC-48. There seems to have been,
> at some point, some discussion regarding the difference between EUI-48 and
> MAC-48, as relate to their use in EUI-64.

> And the mailing list archives only go back to some time in 2003, while the
> RFCs are 1998 (current) and 1996 (replaced by 1998 versions).

The IPv6 WG was (previousl) the ipng WG. See the archives at
ftp://ftp.ietf.org/ietf-mail-archive/ipngwg/

> Did we collectively just throw away 16 bits of usable space from our 128,
> for no good reason?

It kind of looks that way today. :-(

> If someone can explain the rationale, that'd be great.

Well, there were multiple ones. But the main one I recall was that it
made the address format more "friendly" to the 8+8/GSE proposal, with
the hope being that maybe we could still develop 8+8/GSE and have it
work with easily with IPv6. As we know now, that never happened.

The other factor was that there was the thought that future LAN
devices would use 64-bit MAC addresses, i.e., EUI-64
identifiers. Thus, we simply made stateless address autoconfiguration
forwards compatible.

The reality, of course, is that the Ethernet frame format continues
to dominate networking at the edges, and probably will more-or-less
forever.

> (I suppose it's a bit late in the game to go back to MAC-48 as II?)

Yes. The difficulty is figuring out how to move to something different
in a backwards-compatable way. I.e., we'd need a transition strategy.

Thomas

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



From ipv6-bounces@ietf.org Wed Aug 29 10:49:07 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQOp0-0002K0-NS; Wed, 29 Aug 2007 10:47:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQOoz-0002Ju-9V
	for ipv6@ietf.org; Wed, 29 Aug 2007 10:47:05 -0400
Received: from nz-out-0506.google.com ([64.233.162.231])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQOoy-0001hG-0X
	for ipv6@ietf.org; Wed, 29 Aug 2007 10:47:05 -0400
Received: by nz-out-0506.google.com with SMTP id n1so162178nzf
	for <ipv6@ietf.org>; Wed, 29 Aug 2007 07:47:01 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=LswO47xNFd8hltiIinLem0CzItabgfvCYLCddC8JJf3a7wvjvN3LnXdO2zkU+TrUiI76T+RLO9kN8pBAZcUoqd6IlbTyrQSLiHMxfUUrl0mVrzoYAP3WerQVyJXHPoZAusYaT2ITvJYbPpS0UAn8kL/iuFRQwy6/eKOhjy8aqTg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=qYMKJIbsX1khN6mXdWzqDmReXkCVPo4P3tusWKP5RtXfMz65IoWqUUeqMdB0yBLlnQfdifZJ3MEkUv+yU7jj4HB8m8OSGPO9TWmvRNnAtbStvGxvOU8ts6kjNTYaX8hFGJM7L9aNHbI7nv4yA8afXs5P0hGQb1LYoVppI98GUd4=
Received: by 10.141.128.19 with SMTP id f19mr388620rvn.1188398820503;
	Wed, 29 Aug 2007 07:47:00 -0700 (PDT)
Received: by 10.141.201.4 with HTTP; Wed, 29 Aug 2007 07:47:00 -0700 (PDT)
Message-ID: <75cb24520708290747m1ce82274g803db06ae53df9c6@mail.gmail.com>
Date: Wed, 29 Aug 2007 10:47:00 -0400
From: "Christopher Morrow" <christopher.morrow@gmail.com>
To: "Arnaud Ebalard" <arno@natisbad.org>
In-Reply-To: <873ay2ixkj.fsf@natisbad.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <Pine.GSO.4.20.0708271348200.6917-100000@meno.corp.us.uu.net>
	<46D32BB2.1030908@ericsson.com>
	<20070828090414.GA67414@walton.maths.tcd.ie>
	<75cb24520708282045g475f32ecic7284a083cebcd3d@mail.gmail.com>
	<873ay2ixkj.fsf@natisbad.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: David Malone <dwmalone@maths.tcd.ie>, ipv6@ietf.org,
	Suresh Krishnan <suresh.krishnan@ericsson.com>,
	jason.schiller@verizonbusiness.com
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 8/29/07, Arnaud Ebalard <arno@natisbad.org> wrote:
> Hi,
>
> "Christopher Morrow" <christopher.morrow@gmail.com> writes:
>
> > and 80x magnification is a problem... but in this case (and in many
> > other cases of same) there are simple solutions that could/should be
> > used. Solutions which don't require base protocol changes.
>
> Can you describe those _simple_ solutions and compare them with the
> deprecation? ;-)
>

Sure, if you see a problem related to the ping/pong between 2 devices
simply filter that traffic. The sky is not, in point of fact, falling.
There is no difference between this sort of security problem and
smurf-attacks or syn-floods. (speaking as someone that's had to
protect thousands of customers and a sort-of-large network for 8+
years from these sorts of issues).

> IMHO, the real problem is that RH0 should not have been in the IPv6
> specifications (1883 _and_ 2460) and the associated time/space could
> have been used, as you wrote, for something more useful.
>

Sure, the original idea was probably (I've not read the history) to
have feature parity as much as reasonably possible. I suspect that
when 1883 and 2460 were written source-routing in ipv4 was still
somewhat useful. Today, for a variety of reasons, it's become mostly
not-usable except in specific applications.

> locator/id split is actually one of such things, but having it directly
> in IP has pros and cons. Keeping IPv6 simple and efficient allows
> building on top of it (like MIPv6 does) with some insurance on resulting
> stability.
>

Certainly, doing so scalably (like making all of ipv6 MIPv6 instead of
a special class of MIPv6 capable endopints) would have been a much
better long term solution :( Essentially, as a number of presentations
I've given or vaf@cisco.com has given, the world IPv6 was designed for
didn't appear. The assumptions inherent in the design (the largest
mis-assumption being a small number of large providers with aggregate
routing and addressing) have driven us to a wierd place...

thanks,
Chris

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



From ipv6-bounces@ietf.org Wed Aug 29 10:52:55 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQOso-0003YO-MJ; Wed, 29 Aug 2007 10:51:02 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQOsm-0003Wf-Hs
	for ipv6@ietf.org; Wed, 29 Aug 2007 10:51:00 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQOsm-0003Uk-2T
	for ipv6@ietf.org; Wed, 29 Aug 2007 10:51:00 -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 l7TEmVCb026641
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Wed, 29 Aug 2007 16:48:32 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <200708291423.l7TENQZ8000329@cichlid.raleigh.ibm.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.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>
	<471515FC-E1E1-4C83-99AA-A9821E0C2FF5@muada.com> <!
	! 63886.74.122.168.81.1188025388.squirrel@look.libertyrms.com>
	<200708291423.l7TENQZ8000329@cichlid.raleigh.ibm.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <79358CCF-0A4B-424D-BA32-14099B3EF257@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Wed, 29 Aug 2007 16:50:48 +0200
To: Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: History of autoconfig RFCs and siblings, please?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 29-aug-2007, at 16:23, Thomas Narten wrote:

> The reality, of course, is that the Ethernet frame format continues
> to dominate networking at the edges, and probably will more-or-less
> forever.

Firewire has 64-bit MAC addresses but on the Mac (ha) they show up as:

fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 494
         lladdr 00:1b:63:ff:fe:7b:41:5c

(Not sure what the deal is with the MTU, normally it's 4078.)

>> (I suppose it's a bit late in the game to go back to MAC-48 as II?)

> Yes. The difficulty is figuring out how to move to something different
> in a backwards-compatable way. I.e., we'd need a transition strategy.

But what would be the point of doing that now?

The fact that we have so many local bits in the IPv6 address is our  
insurance policy against address policy screwups because a single /64  
is enough to run a network of arbitrary size if you forego stateless  
autoconfig.

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



From ipv6-bounces@ietf.org Wed Aug 29 11:20:02 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQPIs-0005gj-PY; Wed, 29 Aug 2007 11:17:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQPIp-0005gP-WC
	for ipv6@ietf.org; Wed, 29 Aug 2007 11:17:56 -0400
Received: from vgateway.libertyrms.info ([207.219.45.62]
	helo=mail.libertyrms.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IQPIo-0002ye-M4
	for ipv6@ietf.org; Wed, 29 Aug 2007 11:17:55 -0400
Received: from vgateway.int.libertyrms.com ([10.1.3.254]
	helo=look.libertyrms.com)
	by mail.libertyrms.com with esmtp (Exim 4.22)
	id 1IQPIT-0000OJ-Tu; Wed, 29 Aug 2007 11:17:33 -0400
Received: from 74.122.168.81 (SquirrelMail authenticated user briand)
	by look.libertyrms.com with HTTP;
	Wed, 29 Aug 2007 11:17:33 -0400 (EDT)
Message-ID: <61722.74.122.168.81.1188400653.squirrel@look.libertyrms.com>
In-Reply-To: <79358CCF-0A4B-424D-BA32-14099B3EF257@muada.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<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>
	<471515FC-E1E1-4C83-99AA-A9821E0C2FF5@muada.com> <! !
	63886.74.122.168.81.1188025388.squirrel@look.libertyrms.com>
	<200708291423.l7TENQZ8000329@cichlid.raleigh.ibm.com>
	<79358CCF-0A4B-424D-BA32-14099B3EF257@muada.com>
Date: Wed, 29 Aug 2007 11:17:33 -0400 (EDT)
From: briand@ca.afilias.info
To: "Iljitsch van Beijnum" <iljitsch@muada.com>
User-Agent: SquirrelMail/1.4.9a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Exim-Mail-From: briand@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Cc: Thomas Narten <narten@us.ibm.com>, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: History of autoconfig RFCs and siblings, please?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Iljitsch wrote:
> On 29-aug-2007, at 16:23, Thomas Narten wrote:
>>> (I suppose it's a bit late in the game to go back to MAC-48 as II?)
>
>> Yes. The difficulty is figuring out how to move to something different
>> in a backwards-compatable way. I.e., we'd need a transition strategy.
>
> But what would be the point of doing that now?

The point, which I have avoided making until now, is that II has direct
impact on the available range of assignments by RIRs to LIRs, for PI blocks,
that also allow for very long timescale predictive assignments.

Basically, the minimum prefix size * number of assignments * LIRs,
when projected over a timeframe of decades, while preserving a global
DFZ consisting of one PI block per LIR, has a problem fitting into the
number of bits per RIR.

Right now, RIRs are reserving only an additional 2 bits per LIR assignment,
for "growth". Alternative allocation policies (bisection) don't guarantee
the ability to assign arbitrarily large blocks indefinitely - while that
is in fact the long-term requirement. Block sizes *should* increase over
time, even as the frequency of their assignment decreases.

What works best is, a best-fit approach, where any organization gets way
more space than they need, sized according to their own best guess as to
long-term growth *potential*.

Then, reserve even more space for each, in a consistent manner.

Take all these requests, and fill them in an optimized space-packing manner.

At some point, growth requests get filled via "growing" the assignment for
a given LIR into its reserved space.

And, long-term periodic reviews of those growth patterns may result in
bisecting *some* of those reserved blocks to make more space available
for similar assignments.

This can be shown to meet the requirements of individual LIRs to within
a few orders of magnitude of their long-term projections (pretty good),
and at the same time, optimize the packing efficiency, meaning the truly
free space will not be fragmented except to the degree absolutely necessary
for the existing assignments.

This means that new assignments have the largest possible potential prefix
size available, compared to other allocation methods. This can even be
demonstrated or possibly even proven mathematically, by modeling the
problem space.

> The fact that we have so many local bits in the IPv6 address is our
> insurance policy against address policy screwups because a single /64
> is enough to run a network of arbitrary size if you forego stateless
> autoconfig.

The same would be true of /80, which is what MAC-48 would result in, for
minimum prefix size for autoconf (and thus the standard end-user assignment
size).

Of the 16 bits reclaimed via this change, I would propose to the RIRs,
that 4 bits be added to initial allocations, 4 bits to reservations above
the initial allocations (for long-term growth), and the other 8 bits add
to the total space available for the RIRs to allocate to LIRs - by adjusting
the minimum and initial allocation sizes by 8 bits.

The numbers (4 bits and 8 bits) are not accidental - they are one nibble
in size, which matches up with the boundaries for reverse address lookups,
via ip6.arpa - which uses nibbles.

It seems to me, that while it would be an uphill battle, the main two issues
are transition and compatibity, and inertia (e.g. deployed code and
networks.)

The overall benefits to address space assignment, IMHO, outweigh that cost,
especially when considering the long-term health of the DFZ and the cost
to member organizations when having to do expensive upgrades to their
entire infrastructure to support bloat in the DFZ.

Brian


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



From ipv6-bounces@ietf.org Wed Aug 29 12:13:20 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQQ8U-0002dI-46; Wed, 29 Aug 2007 12:11:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQQ8R-0002aB-Vr
	for ipv6@ietf.org; Wed, 29 Aug 2007 12:11:15 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQQ8O-0005mD-D9
	for ipv6@ietf.org; Wed, 29 Aug 2007 12:11:15 -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 l7TG7URM027947
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Wed, 29 Aug 2007 18:07:32 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <61722.74.122.168.81.1188400653.squirrel@look.libertyrms.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<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>
	<471515FC-E1E1-4C83-99AA-A9821E0C2FF5@muada.com> <! !
	63886.74.122.168.81.1188025388.squirrel@look.libertyrms.com>
	<200708291423.l7TENQZ8000329@cichlid.raleigh.ibm.com>
	<79358CCF-0A4B-424D-BA32-14099B3EF257@muada.com>
	<61722.74.122.168.81.118! 8400653.squirrel@look.libertyrms.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <A1C12A3D-50BC-468C-A5F9-3CD68047229D@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Wed, 29 Aug 2007 18:09:48 +0200
To: briand@ca.afilias.info
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 287c806b254c6353fcb09ee0e53bbc5e
Cc: Thomas Narten <narten@us.ibm.com>, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: History of autoconfig RFCs and siblings, please?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 29-aug-2007, at 17:17, briand@ca.afilias.info wrote:

>> But what would be the point of doing that now?

> Basically, the minimum prefix size * number of assignments * LIRs,
> when projected over a timeframe of decades, while preserving a global
> DFZ consisting of one PI block per LIR, has a problem fitting into the
> number of bits per RIR.

(Please note the difference between the provider aggregatable (PA)  
blocks that are _allocated_ to LIRs/ISPs and the provider independent  
(PI) blocks that are _assigned_ to end-users (which may also be  
considered "LIRs" under the definition "LIR = anyone who pays the RIR  
fee".)

Simple problems have simple solutions: if your current block is not  
big enough, get a second block.

> Right now, RIRs are reserving only an additional 2 bits per LIR  
> assignment,
> for "growth". Alternative allocation policies (bisection) don't  
> guarantee
> the ability to assign arbitrarily large blocks indefinitely - while  
> that
> is in fact the long-term requirement.

It's three bits: a /29 is reserved for each allocated /32. However,  
the problem with this approach is that a quick look at the IPv4  
routing table shows that the potential for aggregation created thusly  
isn't fully realized in practice. Reserving address space in this  
manner has two downsides:

- rapid fragmentation of relatively large amounts of address space
- increased potential for deaggregation because the maximum prefix  
length is often longer than the actual prefix length

Because of this, it's my opinion that the current practices are  
harmful and should be replaced by a new way of allocating, where all  
prefixes from a certain block have the same length, so it's possible  
to filter on this prefix length. The size of subsequent blocks is  
increased by a certain factor (I'm thinking 4 - 16) until an upper  
limit is reached beyond which the value of limiting the number of  
prefixes becomes lower than the downside of the potential address  
waste. For IPv4 this should probably be something like /12, for IPv6  
I'm thinking /24.

> What works best is, a best-fit approach, where any organization  
> gets way
> more space than they need, sized according to their own best guess  
> as to
> long-term growth *potential*.

It's a waste of time and address space if the people don't aggregate,  
and IPv4 experience shows this doesn't happen as much as it should.

>> The fact that we have so many local bits in the IPv6 address is our
>> insurance policy against address policy screwups because a single /64
>> is enough to run a network of arbitrary size if you forego stateless
>> autoconfig.

> The same would be true of /80, which is what MAC-48 would result  
> in, for
> minimum prefix size for autoconf (and thus the standard end-user  
> assignment
> size).

I guess 48 bits is enough for all private networks, too, yes.

However, if we make this move now we can't make it in the future  
anymore, so we've wasted the additional 16 bits. If we keep things  
the way they are now this has the obvious advantage of not taking  
action over taking action, and it allows us to squeeze out 16 bits  
and still have autoconfig based on 48 bit identifiers at some point  
in the future. However...

> The overall benefits to address space assignment, IMHO, outweigh  
> that cost,

I disagree. It would be pretty hard to go from 64-bit autoconfig to  
48-bit autoconfig in a backward compatible way, because the global/ 
local bit that is very important here is in the upper 16 bits. It  
also kills efforts like CGA and HBA, where the interface identifier  
bits are used for crypto purposes. ~64 bits is already not very  
strong, ~48 would be too weak. Yes, we already have legacy  
considerations in IPv6.

> especially when considering the long-term health of the DFZ and the  
> cost
> to member organizations when having to do expensive upgrades to their
> entire infrastructure to support bloat in the DFZ.

By adopting PI in IPv6, the community is saying that this isn't an  
issue.

Apart from that, what we need to control the DFZ under the current  
regime is the ability to make good prefix length filters. Currently,  
RIPE has says the maximum prefix length for 3 /8s is /29. This means  
that a filter that conforms to the RIPE policy will allow 6 million  
prefixes under full deaggregation. RIPE also gives out very large  
IPv6 blocks such as /19 and /20 from 2a01::/16 but also /32s. This  
means a filter must allow /32s so the holders of that /19 can  
fragment their block into 8192 /32s if they want. All the while, the  
utility of using a /19 over, say, 32 (or 28, or 25...) /24 for  
reasons of DFZ health is negilible because by the time 2000::/3 is  
filled up it's almost certainly possible for routers to handle 2^ 
(24-3) = 2 million prefixes. Giving out such large blocks only  
increases the potential for deaggregation while at the same time  
potentially wasting an awfully big number of addresses because the  
larger the block, the bigger the difference between the number of  
available addresses and the number of addresses actually used.

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



From ipv6-bounces@ietf.org Wed Aug 29 12:42:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQQaz-00008k-Nb; Wed, 29 Aug 2007 12:40:45 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQQaz-000050-2E; Wed, 29 Aug 2007 12:40:45 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IQQay-0008PL-Jw; Wed, 29 Aug 2007 12:40:44 -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 l7TGbqSb028472
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Wed, 29 Aug 2007 18:38:12 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <460A4920-4D82-4563-919C-45948582795C@nokia.com>
References: <460A4920-4D82-4563-919C-45948582795C@nokia.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <7B57389B-722E-4902-B822-A70278CC85C8@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Wed, 29 Aug 2007 18:40:29 +0200
To: bob.hinden@nokia.com
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6d62ab47271805379d7172ee693a45db
Cc: Brian Haberman <brian@innovationslab.net>,
	IESG Secretary <iesg-secretary@ietf.org>, IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: Request to Advance:  <draft-ietf-ipv6-deprecate-rh0-01.txt>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 27-aug-2007, at 23:21, ext ext Bob Hinden wrote:

> On behalf of the IPv6 WG, the chairs request the advancement of

That was fast.

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



From ipv6-bounces@ietf.org Wed Aug 29 12:43:19 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQQbl-0000qd-FQ; Wed, 29 Aug 2007 12:41:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQQbk-0000qX-K6
	for ipv6@ietf.org; Wed, 29 Aug 2007 12:41:32 -0400
Received: from sequoia.muada.com ([83.149.65.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQQbj-0006lR-9A
	for ipv6@ietf.org; Wed, 29 Aug 2007 12:41: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 l7TGbqSa028472
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Wed, 29 Aug 2007 18:37:52 +0200 (CEST)
	(envelope-from iljitsch@muada.com)
In-Reply-To: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
References: <85981C8D-D13D-4773-A6EF-B5794D23DC20@nokia.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F3DD28A5-52B0-456E-926E-6E5DD30E3524@muada.com>
Content-Transfer-Encoding: 7bit
From: Iljitsch van Beijnum <iljitsch@muada.com>
Date: Wed, 29 Aug 2007 18:40:09 +0200
To: bob.hinden@nokia.com
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 20-aug-2007, at 22:43, Bob Hinden wrote:

> We would like to get your comments on the following two choices:

> 1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate- 
> rh0-01.txt>.

> 2) Revising the draft to restrict the usage of RH0.  This would  
> continue to require RH0 to be implemented but would restrict the  
> functionality of RH0.  For example, require nodes to have support  
> for RH0 turned off by default, limit the number of RH0 headers in a  
> packet to one, limit the number of addresses in the RH0 to a  
> smaller number (e.g., 6), and and a requirement that addresses can  
> only be in the header once.

My objections to the draft:

- I do not consider this a security issue as such
- I don't consider this text to be proper use of the word  
"deprecate", "remove" would be more appropriate
- not specified that processing the header in a system functioning as  
a host is erroneous
- overly aggressive stance on future use of the mechanism

So if the above are my only two choices, I'm coming down in favor of 2.

However, what I'd really like to see is a clear statement that hosts  
MUST NOT send out packets not generated locally, for reasons of the  
RH0 header or otherwise, and "optional to implement" and "off by  
default" language. That leaves current and future implementations the  
freedom to implement and administrators to enable the mechanism if  
and when desired.

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



From ipv6-bounces@ietf.org Wed Aug 29 13:26:32 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQRHQ-0006Hj-E0; Wed, 29 Aug 2007 13:24:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQRHO-0006HJ-8W
	for ipv6@ietf.org; Wed, 29 Aug 2007 13:24:34 -0400
Received: from web56505.mail.re3.yahoo.com ([66.196.97.34])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1IQRHM-0008AS-Km
	for ipv6@ietf.org; Wed, 29 Aug 2007 13:24:34 -0400
Received: (qmail 75313 invoked by uid 60001); 29 Aug 2007 17:24:32 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=vAW+M2nB89TnKrZuSbMipjRERzQAIAKYtodfzp4WBf7yyRPFhM8LRnGWC/aNxF+EWMdBoiPedroXDN+f2NxLeyy7U8fcnMTCO4I3/efFxTwo985q+yydRAlWckUZjAby2dKEObFG/DmbIDwhTCCo8klMnoNDb7aHAUUKlp4Q+G4=;
X-YMail-OSG: LGcXkgMVM1m3rLyHsnpBF5y13WOSRKUZgQpl4dbstaZXns_BEseHEJQ3OquvkhRe0AVYABgylEWn4wfxsknLRw0eus7eRlZgdcMoMLmvCmuiQ_rMeB9wNYJMjodJO0VXqDsoEFqCDPeD_8P_HO3IDUg17A--
Received: from [122.164.167.213] by web56505.mail.re3.yahoo.com via HTTP;
	Wed, 29 Aug 2007 10:24:32 PDT
Date: Wed, 29 Aug 2007 10:24:32 -0700 (PDT)
From: sengottuvelan srirangan <sengottuvelan_s@yahoo.com>
To: Vishwas Manral <vishwas.ietf@gmail.com>, IPv6 WG <ipv6@ietf.org>
In-Reply-To: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
MIME-Version: 1.0
Message-ID: <404874.74926.qm@web56505.mail.re3.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea10c7a57c6f5d0512401188e6188235
Cc: manoj@ipinfusion.com
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2133386249=="
Errors-To: ipv6-bounces@ietf.org

--===============2133386249==
Content-Type: multipart/alternative; boundary="0-306235386-1188408272=:74926"
Content-Transfer-Encoding: 8bit

--0-306235386-1188408272=:74926
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi Viswas,
   
  I could not get the below comments in the draft:
   
  "
  A Routing header is not examined or processed until it reaches the node identified in the Destination Address field of the IPv6 header.
 
   There can be at most one RH4 header in any packet. A packet with
 more   than one RH4 header is discarded. This functionality can be
 implemented  in a firewall or any other IPv6 node.
  :
  :
   Whereever possible, including the administrative network edge, RPF
 check needs to be done.
  "
   
  I have following comments on the draft:
   
  1.  Draft recommends to implement the stack in  the destination nodes but also says , Whereever possible,including the administrative network edge, RPF check needs to be done. This functionality can be  implemented  in a firewall or any other IPv6 node. 
  please clarify.
   
  2. What if current IPv6 node receives RH4 header?. How do we handle the RH4 header in the current implementaions? 
   
   
  Regards
  Sengottuvelan
   
   
  

Vishwas Manral <vishwas.ietf@gmail.com> wrote:
  Hi,

Based on feedback from the group, we have written a draft for a new
routing header. The functionality is the same as the RH0. The draft
will soon be posted to the IETF site.

The main differences are:

1. Maximum up to 4 addresses in the header. (the number is based on
the reply I got for the question about the usage scenarios in operator
environments).
2. Only one header in each packet.
3. Firewall policy reccomendation.
4. RPF reccomendation.

Please have a look and let us know your comments.

Thanks,
Vishwas


Network Working Group V. Manral
Internet-Draft M. Dutta
Updates: 2460, 4294 IP Infusion Inc.
(if approved) 
Intended status: Standards Track 
Expires: February 28, 2008 
August 28, 2007


New IPv6 Type 4 Routing Header
draft-manral-ipv6-rh4-00

Status of this Memo

By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.

Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.

Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."

The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.

The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.

This Internet-Draft will expire on December 28, 2007.

Copyright Notice

Copyright (C) The IETF Trust (2007).

Abstract

The functionality provided by IPv6's Type 0 Routing Header can be
exploited in order to achieve traffic amplification over a remote
path for the purposes of generating denial-of-service traffic. 

This document updates the IPv6 specification to the use of a new 
IPv6 Type 4 Routing Header, in light of this security concern. This 
new header provides the same functionality of the Routing Header
Type-0, while taking care of the major security concerns defined 
in the draft [draft-ietf-ipv6-deprecate-rh0-01].



Manral Expires February 28, 2008 [Page 1]

Internet-Draft New IPv6 Type 4 Routing Header June 2007


Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Format of RH4 . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
6. Acknowlegements . . . . . . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.1. Normative References . . . . . . . . . . . . . . . . . . . 7
6.2. Informative References . . . . . . . . . . . . . . . . . . 8
Appendix A. Change History . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
Intellectual Property and Copyright Statements . . . . . . . . . . 10





































Manral Expires February 28, 2008 [Page 2]

Internet-Draft New IPv6 Type 4 Routing Header June 2007


1. Introduction

[RFC2460] defines an IPv6 extension header called "Routing Header",
identified by a Next Header value of 43 in the immediately preceding
header. A particular Routing Header subtype denoted as "Type 0" is
also defined. Type 0 Routing Headers are referred to as "RH0" in
this document.

128-fold amplification of data traffic can result using the IPv6 
amplification attack as defined in [I-D.ietf-ipv6-deprecate-rh0-01].
This attack is particularly serious in that it affects the entire
path between the two exploited nodes, not only the nodes themselves
or their local networks. 

The draft [I-D.ietf-ipv6-deprecate-rh0-01] deprecates the use of the 
RH0 header. However operators use and require the functionality provided
by the RH0 header.

This draft defines the Routing Header of Type-4, and referred to as "RH4" 
header. The RH4 header has format and functionality similar to the RH0 
header without having the major vulnerabilities of the "Routing Header".

This document updates [RFC2460] and [RFC4294].




























Manral Expires February 28, 2008 [Page 3]

Internet-Draft New IPv6 Type 4 Routing Header June 2007


2. Definitions

RH4 in this document denotes the IPv6 Extension Header type 43
("Routing Header") variant 4 ("Type 4 Routing Header"), is a type of 
Routing header as defined in [RFC2460]. 

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].


3. Format of RH4

The Type 4 Routing header has the following format (it is the same as 
the RH0 header except for the limit on the "Hdr Ext Len" field. Some 
additional restrictions and checks have been added):

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Next Header | Hdr Ext Len | Routing Type=0| Segments Left |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
| |
+ Address[1] +
| |
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
| |
+ Address[2] +
| |
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . .
. . .
. . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
| |
+ Address[n] +
| |
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Next Header 8-bit selector. Identifies the type of header
immediately following the Routing header. Uses
the same values as the IPv4 Protocol field
[RFC-1700 et seq.].

Hdr Ext Len 8-bit unsigned integer. Length of the Routing
header in 8-octet units, not including the first
8 octets. For the Type 4 Routing header, Hdr
Ext Len is equal to two times the number of
addresses in the header. The maximum value of this
field can be 8. That means a maximum of 4 addresses
can be added to the Routing Header.


Manral Expires February 28, 2008 [Page 4]

Internet-Draft New IPv6 Type 4 Routing Header June 2007



Routing Type 4.

Segments Left 8-bit unsigned integer. Number of route
segments remaining, i.e., number of explicitly
listed intermediate nodes still to be visited
before reaching the final destination.

Reserved 32-bit reserved field. Initialized to zero for
transmission; ignored on reception.

Address[1..n] Vector of 128-bit addresses, numbered 1 to n. The
maximum value of n is 4. 

Multicast addresses or Link Local Unicast address must not appear in a 
Routing header of Type 4, or in the IPv6 Destination Address field of 
a packet carrying a Routing header of Type 4. 

A Routing header is not examined or processed until it reaches the
node identified in the Destination Address field of the IPv6 header. 
There can be at most one RH4 header in any packet. A packet with more
than one RH4 header is discarded. This functionality can be implemented 
in a firewall or any other IPv6 node.

In that node, dispatching on the Next Header field of the immediately
preceding header causes the Routing header module to be invoked,
which, in the case of Routing Type 4, performs the algorithm which is 
similar to the as specified in section 4.4 of [RFC2460]:











Manral Expires February 28, 2008 [Page 5]

Internet-Draft New IPv6 Type 4 Routing Header June 2007


if Segments Left = 0 {
proceed to process the next header in the packet, whose type is
identified by the Next Header field in the Routing header
}
else if Hdr Ext Len is odd {
send an ICMP Parameter Problem, Code 0, message to the Source
Address, pointing to the Hdr Ext Len field, and discard the
packet
}
else {
compute n, the number of addresses in the Routing header, by
dividing Hdr Ext Len by 2

if Segments Left is greater than n or n is greater than 4 {
send an ICMP Parameter Problem, Code 0, message to the Source
Address, pointing to the Segments Left field, and discard the
packet
}
else {
decrement Segments Left by 1;
compute i, the index of the next address to be visited in
the address vector, by subtracting Segments Left from n

if Address [i] or the IPv6 Destination Address is multicast 
or link local unicast address {
discard the packet
}
else {
Compare the addresses in the Routing Header to check that 
none of the address belong to the routers self address

if overlapping address exist {
discard the packet
}

swap the IPv6 Destination Address and Address[i]

if the IPv6 Hop Limit is less than or equal to 1 {
send an ICMP Time Exceeded -- Hop Limit Exceeded in
Transit message to the Source Address and discard the
packet
}
else {
decrement the Hop Limit by 1

resubmit the packet to the IPv6 module for transmission
to the new destination
}
}
}
}





Manral Expires February 28, 2008 [Page 6]

Internet-Draft New IPv6 Type 4 Routing Header June 2007


4. Security Considerations

The purpose of this document is to add a new type of Routing extension
header of IPv6. RH0 has been shown to have undesirable security 
implications.

Many of the attacks including the amplification attack cannot occur with 
the RH4 header. All the addresses in the RH4 header need to be checked with
the firewall policy to make sure the firewall is able to trap packets meant 
for addresses in the firewall policy and take relevent action.

Whereever possible, including the administrative network edge, RPF check 
needs to be done.


5. IANA Considerations

The IANA registry "Internet Protocol Version 6 (IPv6) Parameters"
should be updated to reflect that variant 4 of IPv6 header-type 43
("Routing Header") is added.


7. Acknowlegements

This document benefits from the contributions of many IPV6 and V6OPS
working group participants, including Chris Morrow, Tony Hain, Jinmei
Tatuya and Brian Carpenter.


8. References

8.1. Normative References

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.



Manral Expires February 28, 2008 [Page 7]

Internet-Draft New IPv6 Type 4 Routing Header June 2007


[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998.

[RFC4294] Loughney, J., "IPv6 Node Requirements", RFC 4294,
April 2006.

8.2. Informative References

[CanSecWest07]
BIONDI, P. and A. EBALARD, "IPv6 Routing Header Security",
CanSecWest Security Conference 2007, April 2007.

http://www.secdev.org/conf/IPv6_RH_security-csw07.pdf

[I-D.ietf-v6ops-security-overview]
Davies, E., "IPv6 Transition/Co-existence Security
Considerations", draft-ietf-v6ops-security-overview-06
(work in progress), October 2006.

[I-D.savola-ipv6-rh-ha-security]
Savola, P., "Security of IPv6 Routing Header and Home
Address Options", draft-savola-ipv6-rh-ha-security-02
(work in progress), March 2002.

[I-D.savola-ipv6-rh-hosts]
Savola, P., "Note about Routing Header Processing on IPv6
Hosts", draft-savola-ipv6-rh-hosts-00 (work in progress),
February 2002.

[RFC2827] Ferguson, P. and D. Senie, "Network Ingress Filtering:
Defeating Denial of Service Attacks which employ IP Source
Address Spoofing", BCP 38, RFC 2827, May 2000.

[RFC3704] Baker, F. and P. Savola, "Ingress Filtering for Multihomed
Networks", BCP 84, RFC 3704, March 2004.

[RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support
in IPv6", RFC 3775, June 2004.


Appendix A. Change History

This section to be removed prior to publication.






Manral Expires February 28, 2008 [Page 8]

Internet-Draft New IPv6 Type 4 Routing Header June 2007


Authors' Addresses

Vishwas Manral
IP Infusion Inc,
Bamankhola
Bansgali
Almora - Uttaranchal
Phone: +91 98456 61911
Email: vishwas@ipinfusion.com


Manoj Dutta
IP Infusion Inc,
125, S. Market Street,
San Jose, CA
Phone: 408 794 1500
Email: manoj@ipinfusion.com







































Manral Expires February 28, 2008 [Page 9]

Internet-Draft New IPv6 Type 4 Routing Header June 2007


Full Copyright Statement

Copyright (C) The IETF Trust (2007).

This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.

This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Intellectual Property

The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.

Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.

The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.


Acknowledgment

Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).





Manral Expires February 28, 2008 [Page 10]

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


       
---------------------------------
Pinpoint customers who are looking for what you sell. 
--0-306235386-1188408272=:74926
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

<div>Hi Viswas,</div>  <div>&nbsp;</div>  <div>I could not&nbsp;get the below comments in the draft:</div>  <div>&nbsp;</div>  <div>"</div>  <div>A Routing header is not examined or processed until it reaches the&nbsp;node identified in the Destination Address field of the IPv6 header.<BR>&nbsp;</div>  <div>&nbsp;There can be at most one RH4 header in any packet. A packet with<BR>&nbsp;more&nbsp;&nbsp; than one RH4 header is discarded. This functionality can be<BR>&nbsp;implemented&nbsp; in a firewall or any other IPv6 node.</div>  <div>:</div>  <div>:</div>  <div>&nbsp;Whereever possible, including the administrative network edge, RPF<BR>&nbsp;check needs to be done.</div>  <div>"</div>  <div>&nbsp;</div>  <div>I&nbsp;have following&nbsp;comments on the draft:</div>  <div>&nbsp;</div>  <div>1.&nbsp; Draft recommends to implement&nbsp;the stack&nbsp;in&nbsp; the destination nodes but also says , Whereever possible,including the administrative network edge, RPF&nbsp;check
 needs to be done. This functionality can be&nbsp;&nbsp;implemented&nbsp; in a firewall or any other IPv6 node. </div>  <div>please clarify.</div>  <div>&nbsp;</div>  <div>2. What if current IPv6 node receives RH4 header?. How do we handle the RH4 header in the current implementaions?&nbsp;</div>  <div>&nbsp;</div>  <div>&nbsp;</div>  <div>Regards</div>  <div>Sengottuvelan</div>  <div>&nbsp;</div>  <div>&nbsp;</div>  <div><BR><BR><B><I>Vishwas Manral &lt;vishwas.ietf@gmail.com&gt;</I></B> wrote:</div>  <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Hi,<BR><BR>Based on feedback from the group, we have written a draft for a new<BR>routing header. The functionality is the same as the RH0. The draft<BR>will soon be posted to the IETF site.<BR><BR>The main differences are:<BR><BR>1. Maximum up to 4 addresses in the header. (the number is based on<BR>the reply I got for the question about the usage scenarios in
 operator<BR>environments).<BR>2. Only one header in each packet.<BR>3. Firewall policy reccomendation.<BR>4. RPF reccomendation.<BR><BR>Please have a look and let us know your comments.<BR><BR>Thanks,<BR>Vishwas<BR><BR><BR>Network Working Group V. Manral<BR>Internet-Draft M. Dutta<BR>Updates: 2460, 4294 IP Infusion Inc.<BR>(if approved) <BR>Intended status: Standards Track <BR>Expires: February 28, 2008 <BR>August 28, 2007<BR><BR><BR>New IPv6 Type 4 Routing Header<BR>draft-manral-ipv6-rh4-00<BR><BR>Status of this Memo<BR><BR>By submitting this Internet-Draft, each author represents that any<BR>applicable patent or other IPR claims of which he or she is aware<BR>have been or will be disclosed, and any of which he or she becomes<BR>aware will be disclosed, in accordance with Section 6 of BCP 79.<BR><BR>Internet-Drafts are working documents of the Internet Engineering<BR>Task Force (IETF), its areas, and its working groups. Note that<BR>other groups may also distribute
 working documents as Internet-<BR>Drafts.<BR><BR>Internet-Drafts are draft documents valid for a maximum of six months<BR>and may be updated, replaced, or obsoleted by other documents at any<BR>time. It is inappropriate to use Internet-Drafts as reference<BR>material or to cite them other than as "work in progress."<BR><BR>The list of current Internet-Drafts can be accessed at<BR>http://www.ietf.org/ietf/1id-abstracts.txt.<BR><BR>The list of Internet-Draft Shadow Directories can be accessed at<BR>http://www.ietf.org/shadow.html.<BR><BR>This Internet-Draft will expire on December 28, 2007.<BR><BR>Copyright Notice<BR><BR>Copyright (C) The IETF Trust (2007).<BR><BR>Abstract<BR><BR>The functionality provided by IPv6's Type 0 Routing Header can be<BR>exploited in order to achieve traffic amplification over a remote<BR>path for the purposes of generating denial-of-service traffic. <BR><BR>This document updates the IPv6 specification to the use of a new <BR>IPv6 Type 4 Routing
 Header, in light of this security concern. This <BR>new header provides the same functionality of the Routing Header<BR>Type-0, while taking care of the major security concerns defined <BR>in the draft [draft-ietf-ipv6-deprecate-rh0-01].<BR><BR><BR><BR>Manral Expires February 28, 2008 [Page 1]<BR><BR>Internet-Draft New IPv6 Type 4 Routing Header June 2007<BR><BR><BR>Table of Contents<BR><BR>1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3<BR>2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 4<BR>3. Format of RH4 . . . . . . . . . . . . . . . . . . . . . . . . 4<BR>4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5<BR>5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7<BR>6. Acknowlegements . . . . . . . . . . . . . . . . . . . . . . . . 7<BR>8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7<BR>6.1. Normative References . . . . . . . . . . . . . . . . . . . 7<BR>6.2. Informative
 References . . . . . . . . . . . . . . . . . . 8<BR>Appendix A. Change History . . . . . . . . . . . . . . . . . . . . 8<BR>Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9<BR>Intellectual Property and Copyright Statements . . . . . . . . . . 10<BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR>Manral Expires February 28, 2008 [Page 2]<BR><BR>Internet-Draft New IPv6 Type 4 Routing Header June 2007<BR><BR><BR>1. Introduction<BR><BR>[RFC2460] defines an IPv6 extension header called "Routing Header",<BR>identified by a Next Header value of 43 in the immediately preceding<BR>header. A particular Routing Header subtype denoted as "Type 0" is<BR>also defined. Type 0 Routing Headers are referred to as "RH0" in<BR>this document.<BR><BR>128-fold amplification of data traffic can result using the IPv6 <BR>amplification attack as defined in
 [I-D.ietf-ipv6-deprecate-rh0-01].<BR>This attack is particularly serious in that it affects the entire<BR>path between the two exploited nodes, not only the nodes themselves<BR>or their local networks. <BR><BR>The draft [I-D.ietf-ipv6-deprecate-rh0-01] deprecates the use of the <BR>RH0 header. However operators use and require the functionality provided<BR>by the RH0 header.<BR><BR>This draft defines the Routing Header of Type-4, and referred to as "RH4" <BR>header. The RH4 header has format and functionality similar to the RH0 <BR>header without having the major vulnerabilities of the "Routing Header".<BR><BR>This document updates [RFC2460] and [RFC4294].<BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR>Manral Expires February 28, 2008 [Page 3]<BR><BR>Internet-Draft New IPv6 Type 4 Routing Header June 2007<BR><BR><BR>2. Definitions<BR><BR>RH4 in this document denotes the IPv6 Extension Header type
 43<BR>("Routing Header") variant 4 ("Type 4 Routing Header"), is a type of <BR>Routing header as defined in [RFC2460]. <BR><BR>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",<BR>"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this<BR>document are to be interpreted as described in [RFC2119].<BR><BR><BR>3. Format of RH4<BR><BR>The Type 4 Routing header has the following format (it is the same as <BR>the RH0 header except for the limit on the "Hdr Ext Len" field. Some <BR>additional restrictions and checks have been added):<BR><BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>| Next Header | Hdr Ext Len | Routing Type=0| Segments Left |<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>| Reserved |<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>| |<BR>+ +<BR>| |<BR>+ Address[1] +<BR>| |<BR>+ +<BR>|
 |<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>| |<BR>+ +<BR>| |<BR>+ Address[2] +<BR>| |<BR>+ +<BR>| |<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>. . .<BR>. . .<BR>. . .<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR>| |<BR>+ +<BR>| |<BR>+ Address[n] +<BR>| |<BR>+ +<BR>| |<BR>+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR><BR>Next Header 8-bit selector. Identifies the type of header<BR>immediately following the Routing header. Uses<BR>the same values as the IPv4 Protocol field<BR>[RFC-1700 et seq.].<BR><BR>Hdr Ext Len 8-bit unsigned integer. Length of the Routing<BR>header in 8-octet units, not including the first<BR>8 octets. For the Type 4 Routing header, Hdr<BR>Ext Len is equal to two times the number of<BR>addresses in the header. The maximum value of this<BR>field can be 8. That means a maximum of 4 addresses<BR>can be added to the Routing Header.<BR><BR><BR>Manral
 Expires February 28, 2008 [Page 4]<BR><BR>Internet-Draft New IPv6 Type 4 Routing Header June 2007<BR><BR><BR><BR>Routing Type 4.<BR><BR>Segments Left 8-bit unsigned integer. Number of route<BR>segments remaining, i.e., number of explicitly<BR>listed intermediate nodes still to be visited<BR>before reaching the final destination.<BR><BR>Reserved 32-bit reserved field. Initialized to zero for<BR>transmission; ignored on reception.<BR><BR>Address[1..n] Vector of 128-bit addresses, numbered 1 to n. The<BR>maximum value of n is 4. <BR><BR>Multicast addresses or Link Local Unicast address must not appear in a <BR>Routing header of Type 4, or in the IPv6 Destination Address field of <BR>a packet carrying a Routing header of Type 4. <BR><BR>A Routing header is not examined or processed until it reaches the<BR>node identified in the Destination Address field of the IPv6 header. <BR>There can be at most one RH4 header in any packet. A packet with more<BR>than one RH4 header is
 discarded. This functionality can be implemented <BR>in a firewall or any other IPv6 node.<BR><BR>In that node, dispatching on the Next Header field of the immediately<BR>preceding header causes the Routing header module to be invoked,<BR>which, in the case of Routing Type 4, performs the algorithm which is <BR>similar to the as specified in section 4.4 of [RFC2460]:<BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR>Manral Expires February 28, 2008 [Page 5]<BR><BR>Internet-Draft New IPv6 Type 4 Routing Header June 2007<BR><BR><BR>if Segments Left = 0 {<BR>proceed to process the next header in the packet, whose type is<BR>identified by the Next Header field in the Routing header<BR>}<BR>else if Hdr Ext Len is odd {<BR>send an ICMP Parameter Problem, Code 0, message to the Source<BR>Address, pointing to the Hdr Ext Len field, and discard the<BR>packet<BR>}<BR>else {<BR>compute n, the number of addresses in the Routing header, by<BR>dividing Hdr Ext Len by 2<BR><BR>if Segments
 Left is greater than n or n is greater than 4 {<BR>send an ICMP Parameter Problem, Code 0, message to the Source<BR>Address, pointing to the Segments Left field, and discard the<BR>packet<BR>}<BR>else {<BR>decrement Segments Left by 1;<BR>compute i, the index of the next address to be visited in<BR>the address vector, by subtracting Segments Left from n<BR><BR>if Address [i] or the IPv6 Destination Address is multicast <BR>or link local unicast address {<BR>discard the packet<BR>}<BR>else {<BR>Compare the addresses in the Routing Header to check that <BR>none of the address belong to the routers self address<BR><BR>if overlapping address exist {<BR>discard the packet<BR>}<BR><BR>swap the IPv6 Destination Address and Address[i]<BR><BR>if the IPv6 Hop Limit is less than or equal to 1 {<BR>send an ICMP Time Exceeded -- Hop Limit Exceeded in<BR>Transit message to the Source Address and discard the<BR>packet<BR>}<BR>else {<BR>decrement the Hop Limit by 1<BR><BR>resubmit the
 packet to the IPv6 module for transmission<BR>to the new destination<BR>}<BR>}<BR>}<BR>}<BR><BR><BR><BR><BR><BR>Manral Expires February 28, 2008 [Page 6]<BR><BR>Internet-Draft New IPv6 Type 4 Routing Header June 2007<BR><BR><BR>4. Security Considerations<BR><BR>The purpose of this document is to add a new type of Routing extension<BR>header of IPv6. RH0 has been shown to have undesirable security <BR>implications.<BR><BR>Many of the attacks including the amplification attack cannot occur with <BR>the RH4 header. All the addresses in the RH4 header need to be checked with<BR>the firewall policy to make sure the firewall is able to trap packets meant <BR>for addresses in the firewall policy and take relevent action.<BR><BR>Whereever possible, including the administrative network edge, RPF check <BR>needs to be done.<BR><BR><BR>5. IANA Considerations<BR><BR>The IANA registry "Internet Protocol Version 6 (IPv6) Parameters"<BR>should be updated to reflect that variant 4 of IPv6
 header-type 43<BR>("Routing Header") is added.<BR><BR><BR>7. Acknowlegements<BR><BR>This document benefits from the contributions of many IPV6 and V6OPS<BR>working group participants, including Chris Morrow, Tony Hain, Jinmei<BR>Tatuya and Brian Carpenter.<BR><BR><BR>8. References<BR><BR>8.1. Normative References<BR><BR>[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate<BR>Requirement Levels", BCP 14, RFC 2119, March 1997.<BR><BR><BR><BR>Manral Expires February 28, 2008 [Page 7]<BR><BR>Internet-Draft New IPv6 Type 4 Routing Header June 2007<BR><BR><BR>[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6<BR>(IPv6) Specification", RFC 2460, December 1998.<BR><BR>[RFC4294] Loughney, J., "IPv6 Node Requirements", RFC 4294,<BR>April 2006.<BR><BR>8.2. Informative References<BR><BR>[CanSecWest07]<BR>BIONDI, P. and A. EBALARD, "IPv6 Routing Header Security",<BR>CanSecWest Security Conference 2007, April
 2007.<BR><BR>http://www.secdev.org/conf/IPv6_RH_security-csw07.pdf<BR><BR>[I-D.ietf-v6ops-security-overview]<BR>Davies, E., "IPv6 Transition/Co-existence Security<BR>Considerations", draft-ietf-v6ops-security-overview-06<BR>(work in progress), October 2006.<BR><BR>[I-D.savola-ipv6-rh-ha-security]<BR>Savola, P., "Security of IPv6 Routing Header and Home<BR>Address Options", draft-savola-ipv6-rh-ha-security-02<BR>(work in progress), March 2002.<BR><BR>[I-D.savola-ipv6-rh-hosts]<BR>Savola, P., "Note about Routing Header Processing on IPv6<BR>Hosts", draft-savola-ipv6-rh-hosts-00 (work in progress),<BR>February 2002.<BR><BR>[RFC2827] Ferguson, P. and D. Senie, "Network Ingress Filtering:<BR>Defeating Denial of Service Attacks which employ IP Source<BR>Address Spoofing", BCP 38, RFC 2827, May 2000.<BR><BR>[RFC3704] Baker, F. and P. Savola, "Ingress Filtering for Multihomed<BR>Networks", BCP 84, RFC 3704, March 2004.<BR><BR>[RFC3775] Johnson, D., Perkins, C., and J. Arkko,
 "Mobility Support<BR>in IPv6", RFC 3775, June 2004.<BR><BR><BR>Appendix A. Change History<BR><BR>This section to be removed prior to publication.<BR><BR><BR><BR><BR><BR><BR>Manral Expires February 28, 2008 [Page 8]<BR><BR>Internet-Draft New IPv6 Type 4 Routing Header June 2007<BR><BR><BR>Authors' Addresses<BR><BR>Vishwas Manral<BR>IP Infusion Inc,<BR>Bamankhola<BR>Bansgali<BR>Almora - Uttaranchal<BR>Phone: +91 98456 61911<BR>Email: vishwas@ipinfusion.com<BR><BR><BR>Manoj Dutta<BR>IP Infusion Inc,<BR>125, S. Market Street,<BR>San Jose, CA<BR>Phone: 408 794 1500<BR>Email: manoj@ipinfusion.com<BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR>Manral Expires February 28, 2008 [Page 9]<BR><BR>Internet-Draft New IPv6 Type 4 Routing Header June 2007<BR><BR><BR>Full Copyright Statement<BR><BR>Copyright (C) The IETF Trust (2007).<BR><BR>This document is subject to the
 rights, licenses and restrictions<BR>contained in BCP 78, and except as set forth therein, the authors<BR>retain all their rights.<BR><BR>This document and the information contained herein are provided on an<BR>"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS<BR>OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND<BR>THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS<BR>OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF<BR>THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED<BR>WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.<BR><BR><BR>Intellectual Property<BR><BR>The IETF takes no position regarding the validity or scope of any<BR>Intellectual Property Rights or other rights that might be claimed to<BR>pertain to the implementation or use of the technology described in<BR>this document or the extent to which any license under such rights<BR>might or might not be
 available; nor does it represent that it has<BR>made any independent effort to identify any such rights. Information<BR>on the procedures with respect to rights in RFC documents can be<BR>found in BCP 78 and BCP 79.<BR><BR>Copies of IPR disclosures made to the IETF Secretariat and any<BR>assurances of licenses to be made available, or the result of an<BR>attempt made to obtain a general license or permission for the use of<BR>such proprietary rights by implementers or users of this<BR>specification can be obtained from the IETF on-line IPR repository at<BR>http://www.ietf.org/ipr.<BR><BR>The IETF invites any interested party to bring to its attention any<BR>copyrights, patents or patent applications, or other proprietary<BR>rights that may cover technology that may be required to implement<BR>this standard. Please address the information to the IETF at<BR>ietf-ipr@ietf.org.<BR><BR><BR>Acknowledgment<BR><BR>Funding for the RFC Editor function is provided by the
 IETF<BR>Administrative Support Activity (IASA).<BR><BR><BR><BR><BR><BR>Manral Expires February 28, 2008 [Page 10]<BR><BR>--------------------------------------------------------------------<BR>IETF IPv6 working group mailing list<BR>ipv6@ietf.org<BR>Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6<BR>--------------------------------------------------------------------<BR></BLOCKQUOTE><BR><p>&#32;
      <hr size=1><a href="http://us.rd.yahoo.com/evt=48250/*http://searchmarketing.yahoo.com/arp/sponsoredsearch_v9.php?o=US2226&cmp=Yahoo&ctv=AprNI&s=Y&s2=EM&b=50">Pinpoint customers </a>who are looking for what you sell. 


--0-306235386-1188408272=:74926--


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

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

--===============2133386249==--




From ipv6-bounces@ietf.org Wed Aug 29 14:11:14 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQRyS-0004bp-LB; Wed, 29 Aug 2007 14:09:05 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQRyJ-0004S1-9H
	for ipv6@ietf.org; Wed, 29 Aug 2007 14:08:58 -0400
Received: from pmesmtp01.wcom.com ([199.249.20.1] helo=pmesmtp01.mci.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQRyI-000306-Qn
	for ipv6@ietf.org; Wed, 29 Aug 2007 14:08:55 -0400
Received: from dgismtp03.wcomnet.com ([166.38.58.143])
	by firewall.verizonbusiness.com (Iplanet MTA 5.2)
	with ESMTP id <0JNJ00KHORQTNA@firewall.verizonbusiness.com> for
	ipv6@ietf.org; Wed, 29 Aug 2007 18:08:54 +0000 (GMT)
Received: from dgismtp03.wcomnet.com ([127.0.0.1])
	by dgismtp03.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08
	(built Sep
	22 2005)) with SMTP id <0JNJ00ML2RQTTQ@dgismtp03.mcilink.com> for
	ipv6@ietf.org; Wed, 29 Aug 2007 18:08:53 +0000 (GMT)
Received: from meno.corp.us.uu.net ([153.39.146.71])
	by dgismtp03.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08
	(built Sep
	22 2005)) with ESMTP id <0JNJ00M6HRQTJO@dgismtp03.mcilink.com> for
	ipv6@ietf.org; Wed, 29 Aug 2007 18:08:53 +0000 (GMT)
Date: Wed, 29 Aug 2007 14:08:52 -0400 (EDT)
From: Jason Schiller <schiller@uu.net>
In-reply-to: <404874.74926.qm@web56505.mail.re3.yahoo.com>
X-Sender: schiller@meno.corp.us.uu.net
To: sengottuvelan srirangan <sengottuvelan_s@yahoo.com>
Message-id: <Pine.GSO.4.20.0708291350570.8423-100000@meno.corp.us.uu.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: manoj@ipinfusion.com, IPv6 WG <ipv6@ietf.org>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Wed, 29 Aug 2007, sengottuvelan srirangan wrote:

>   I could not get the below comments in the draft:
>    
>   "
>   A Routing header is not examined or processed until it reaches the node identified in the Destination Address field of the IPv6 header.
>  
>    There can be at most one RH4 header in any packet. A packet with
>  more   than one RH4 header is discarded. This functionality can be
>  implemented  in a firewall or any other IPv6 node.
>   :
>   :
>    Whereever possible, including the administrative network edge, RPF
>  check needs to be done.
>   "
>    
>   I have following comments on the draft:
>    
>   1.  Draft recommends to implement the stack in  the destination nodes
>   but also says , Whereever possible,including the administrative
>   network edge, RPF check needs to be done. This functionality can be
>   implemented  in a firewall or any other IPv6 node. 
>   please clarify.
>    
>   2. What if current IPv6 node receives RH4 header?. How do we handle
>   the RH4 header in the current implementaions? 
>    
>    

One of the poblems with the current implementation of RH0 (and IPv4 source
routed packets) is when packet transits a router that is not one of the
source routed hops, it must specially process the packet.  In otherword
forward the packet in software.

Take Host A in the diagram below who wants to send traffic to Host E, but
prefers the packet to first visit Router D.

--------   ----------   ----------   --------
|Host A|---|Router B|---|Router C|---|Host E|
--------   ----------   ----------   --------
                 \        /
                  \      /
                 ---------- 
                 |Router D|
                 ----------

Host A will build a packet with a source address of A, a destination
address of D, and loose source hops of D and E.

When this packet reaches Router B which is not the destination of the
packet, the traffic should be forwarded as normal (in hardware) based on
the destination of the packet D.

When the packet arrives at Router D, then special processing must occur to
support source routing.

The problem that someone else pointed out was there is a conflicting
requirement to apply firewall filters that match on destination address,
to also be capable to match on destinations listed in the loose source
hops.  This will likely require special handeling (i.e. packet not
forwarded in hardware).  One approach is to make both of these options
configurable.

I think possibly the problem is that there is confusion about how source
routing affects routers, and how it affects hosts.  Routers generally
carry lots of transit traffic (not destined for the local router) and
hosts do not.  In this case (where the host is not acting as a router),
the packet should always have a desination of the host.  The host
receiving a packet that has some other destination would likely only
result from a misconfigured network.  I suspect the right action in this
case is to drop the packet.

__Jason



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



From ipv6-bounces@ietf.org Wed Aug 29 14:13:47 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQS1A-0005Zh-LX; Wed, 29 Aug 2007 14:11:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQS12-0005ZM-UA
	for ipv6@ietf.org; Wed, 29 Aug 2007 14:11:47 -0400
Received: from smtp167.iad.emailsrvr.com ([207.97.245.167])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQS11-0001E5-Nq
	for ipv6@ietf.org; Wed, 29 Aug 2007 14:11:44 -0400
Received: by relay6.relay.iad.emailsrvr.com (Authenticated sender:
	dow.street-AT-linquest.com) with ESMTP id D84F86A9AA9; 
	Wed, 29 Aug 2007 14:11:42 -0400 (EDT)
In-Reply-To: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <31C51380-631F-4C72-9B28-6D84D595CFA1@linquest.com>
Content-Transfer-Encoding: 7bit
From: Dow Street <dow.street@linquest.com>
Date: Wed, 29 Aug 2007 11:11:27 -0700
To: Vishwas Manral <vishwas.ietf@gmail.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Cc: manoj@ipinfusion.com, IPv6 WG <ipv6@ietf.org>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

It is interesting to me that folks have described locator-identifier  
split as a *real* problem and source routing as a waste of time.  As  
I understand it, one driver for recent loc-id work is a concern over  
routing system scalability (# of DFZ RIB entries).  In the current  
routing model, if a multi-homed site wants to influence how their  
packets are delivered, it will often advertise multiple, more- 
specific prefixes to different peers (leveraging LPM for TE  
purposes).  Unfortunately, this approach drives a cost in the global  
routing system for which most of the nodes (in that global system)  
receive little or no benefit.  Sites are forced to do this indirect  
signaling of their routing interests through BGP because there is no  
explicit method for directing traffic over a particular path / link.   
This is precisely what source-routing gives you - an explicit method  
for signaling path preference, and it does so in a manner that  
(potentially) allows the costs to be better localized to the  
beneficiaries, rather than incurred by everyone.  I do not claim that  
the current specification or use of RH0 / RH4 is a complete solution,  
but I think it is incorrect to assume loc-id split and source routing  
are completely unrelated.

In my opinion, the RH4 draft appears to be heading in the right  
direction:

1.  Maintains a *general* source routing functionality in IPv6
2.  Makes it required functionality in IPv6 implementations

As others have mentioned (or perhaps decided not to mention), source  
routing has the potential to disrupt the current pricing / billing  
model.  I also think, though, that the use(s) of source routing and  
any corresponding evolution of pricing / billing models would be  
difficult to craft / predict outside the operational network.  This  
is one reason why I support a general source routing function that  
allows for some flexibility, rather than one specifically tailored to  
a single purpose.  Many people seemed to think RH0 provided too much  
flexibility - as I understand it, the RH4 proposal attempts to reduce  
the degree of flexibility (i.e. power) to a more acceptable level.

 From my (naive?) vantage point, maintaining source routing as a  
mandatory part of the spec will help to get the functionality into  
implementations *before* a demonstrated (profitable) use case.  In  
other words, we create an environment where innovation is possible,  
and provide a general capability.  IP seems to be the right place in  
the stack to deal with packet delivery and path selection.  If  
implementers are already visiting code to remove RH0, it seems like a  
reasonable time to add something like RH4.  Given the functional  
similarity of RH0 and RH4, it may be more a code edit than "tear out  
old, add new."

I agree that the cost to uninterested parties should be minimized -  
this issue probably needs to be considered at both the node level and  
the network (ISP) level:

Node level impacts -

The RH4 draft provides some guidance in this area, but perhaps it  
could be expanded.  Some thoughts:

Transit nodes (routers):  if the current destination address does not  
match one of your addresses, don't process the routing header

Destination nodes:  if the current destination address does match one  
of your addresses and there is a source routing header, but you do  
not have source routing enabled, drop the packet.

We may want to make a distinction between intermediate and final  
destinations - not sure.  Perhaps nodes that are only ever IPv6 hosts  
do not need the functionality to act as an intermediate destination,  
but should still accept source routed packets if they are the final  
destination.  In any case, clear implementation guidance should  
eliminate a number of the problems voiced over RH0.


Network level impacts -

Another concern raised about source routing is its potential to make  
traffic (trend) prediction more difficult, which would threaten the  
existing ISP pricing / billing model.  This concern seems to be  
fairly easy to mitigate, however.  By reducing the number of  
intermediate destinations, RH4 significantly reduces the degree of  
traffic variability resulting from oscillation DOS events (i.e. "bad"  
variability).

For traffic variability due to "legitimate" uses of source routing,  
upstream providers can simply adjust their billing model.  Returning  
to the previous example -

A - B -- C - D

If A and D want to support source routing for their customers, but B  
and C are concerned over traffic predictability, they (B and C) can  
charge A and D a higher rate.  i.e. "if your (A) traffic patterns are  
less predictable, it makes our (B) statistical capacity planning more  
difficult so we must charge you more."  If the number of source  
routed packets is low, the impact to capacity planning should be  
low.  As the number of source routed packets increases, the impact to  
capacity planning may also increase.  However, if source routing were  
to become more widely used, it may well be due to its usefulness to  
the end-user.  In this case, it is reasonable the end-user would be  
willing to pay a bit more to A for source routing service, which  
could offset the additional cost of A's connection to B.  Since the  
source route is visible in the IP header (even when encrypted), it is  
easy to enforce policy - i.e. drop the packet.

I'm sure it is more complicated than this, so I'd be interested in  
hearing from folks familiar more with the ISP / business side.

R,
Dow

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



From ipv6-bounces@ietf.org Wed Aug 29 15:01:32 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQSlO-0002B4-R6; Wed, 29 Aug 2007 14:59:39 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQSlI-0002AS-E6
	for ipv6@ietf.org; Wed, 29 Aug 2007 14:59:32 -0400
Received: from py-out-1112.google.com ([64.233.166.180])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQSlH-0004sp-Md
	for ipv6@ietf.org; Wed, 29 Aug 2007 14:59:32 -0400
Received: by py-out-1112.google.com with SMTP id d32so803674pye
	for <ipv6@ietf.org>; Wed, 29 Aug 2007 11:59:31 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:from:to:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language;
	b=E5oqsRyVhOKCvYBX+5Jv/vrKqXAqRIxPZZ7/rzBClMkJgdbMqrwPAXZqkI+ukPw78ypYGbR32r3866kLS/qcgvm/kGvYi/75vrK3mRHKf/QRNQOL4KIT6hQwzmHJoTT0e56OOpHkYB3xJfBPVN/h7ME3WBMG7YU266RWFbcUvC4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:from:to:references:in-reply-to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language;
	b=qvTPDfOt7cRXe42qBpiEBMyWSVHSG3eLfugnVTo9SoAFha22DCxBRBfN8LgUEYoOBCZoQFjKFmcMFV4uRiJwhGtTAUNMF+5J0A0XJeVb/e6d0I5zrERG32Res0oCiwXECZcvUlPro+HndJoL0NsWHlWPgpIJrIA26cEWfoIB6Ew=
Received: by 10.65.43.5 with SMTP id v5mr2004332qbj.1188413970956;
	Wed, 29 Aug 2007 11:59:30 -0700 (PDT)
Received: from Lapci010 ( [75.199.246.230])
	by mx.google.com with ESMTPS id d5sm4762918qbd.2007.08.29.11.59.15
	(version=TLSv1/SSLv3 cipher=RC4-MD5);
	Wed, 29 Aug 2007 11:59:28 -0700 (PDT)
From: "TJ" <trejrco@gmail.com>
To: "'IETF IPv6 Mailing List'" <ipv6@ietf.org>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>	<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>	<471515FC-E1E1-4C83-99AA-A9821E0C2FF5@muada.com>
	<!
	!	63886.74.122.168.81.1188025388.squirrel@look.libertyrms.com>	<200708291423.l7TENQZ8000329@cichlid.raleigh.ibm.com>	<79358CCF-0A4B-424D-BA32-14099B3EF257@muada.com>
	<61722.74.122.168.81.1188400653.squirrel@look.l ibertyrms.com>
In-Reply-To: <61722.74.122.168.81.1188400653.squirrel@look.libertyrms.com>
Date: Wed, 29 Aug 2007 15:00:55 -0400
Message-ID: <006c01c7ea6e$fbab5400$f301fc00$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcfqT+4Fbm/yoW2EQ7OukLrn8neBZwAHop3Q
Content-Language: en-us
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
Subject: RE: History of autoconfig RFCs and siblings, please?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

IIRC - The 64 bit "host piece"/IID (or conversely, "only" a 64 bit routing
prefix) is a requirement only of the 2000::/3 address space, yes?
Presumably, if we come to the collective realization that this is a bad
policy, we will know this before we grow into the next (4000::/3?) space,
and revisit it then ... without breaking all of the then-current
networks/implementations ...  reasonable?



For my $.02 (or less) - yes, I think it is just a bit late to revisit the
whole "/64 or no /64" now ...
/TJ

-----Original Message-----
From: briand@ca.afilias.info [mailto:briand@ca.afilias.info] 
Sent: Wednesday, August 29, 2007 11:18 AM
To: Iljitsch van Beijnum
Cc: Thomas Narten; IETF IPv6 Mailing List
Subject: Re: History of autoconfig RFCs and siblings, please?

Iljitsch wrote:
> On 29-aug-2007, at 16:23, Thomas Narten wrote:
>>> (I suppose it's a bit late in the game to go back to MAC-48 as II?)
>
>> Yes. The difficulty is figuring out how to move to something different
>> in a backwards-compatable way. I.e., we'd need a transition strategy.
>
> But what would be the point of doing that now?

The point, which I have avoided making until now, is that II has direct
impact on the available range of assignments by RIRs to LIRs, for PI blocks,
that also allow for very long timescale predictive assignments.

Basically, the minimum prefix size * number of assignments * LIRs,
when projected over a timeframe of decades, while preserving a global
DFZ consisting of one PI block per LIR, has a problem fitting into the
number of bits per RIR.

Right now, RIRs are reserving only an additional 2 bits per LIR assignment,
for "growth". Alternative allocation policies (bisection) don't guarantee
the ability to assign arbitrarily large blocks indefinitely - while that
is in fact the long-term requirement. Block sizes *should* increase over
time, even as the frequency of their assignment decreases.

What works best is, a best-fit approach, where any organization gets way
more space than they need, sized according to their own best guess as to
long-term growth *potential*.

Then, reserve even more space for each, in a consistent manner.

Take all these requests, and fill them in an optimized space-packing manner.

At some point, growth requests get filled via "growing" the assignment for
a given LIR into its reserved space.

And, long-term periodic reviews of those growth patterns may result in
bisecting *some* of those reserved blocks to make more space available
for similar assignments.

This can be shown to meet the requirements of individual LIRs to within
a few orders of magnitude of their long-term projections (pretty good),
and at the same time, optimize the packing efficiency, meaning the truly
free space will not be fragmented except to the degree absolutely necessary
for the existing assignments.

This means that new assignments have the largest possible potential prefix
size available, compared to other allocation methods. This can even be
demonstrated or possibly even proven mathematically, by modeling the
problem space.

> The fact that we have so many local bits in the IPv6 address is our
> insurance policy against address policy screwups because a single /64
> is enough to run a network of arbitrary size if you forego stateless
> autoconfig.

The same would be true of /80, which is what MAC-48 would result in, for
minimum prefix size for autoconf (and thus the standard end-user assignment
size).

Of the 16 bits reclaimed via this change, I would propose to the RIRs,
that 4 bits be added to initial allocations, 4 bits to reservations above
the initial allocations (for long-term growth), and the other 8 bits add
to the total space available for the RIRs to allocate to LIRs - by adjusting
the minimum and initial allocation sizes by 8 bits.

The numbers (4 bits and 8 bits) are not accidental - they are one nibble
in size, which matches up with the boundaries for reverse address lookups,
via ip6.arpa - which uses nibbles.

It seems to me, that while it would be an uphill battle, the main two issues
are transition and compatibity, and inertia (e.g. deployed code and
networks.)

The overall benefits to address space assignment, IMHO, outweigh that cost,
especially when considering the long-term health of the DFZ and the cost
to member organizations when having to do expensive upgrades to their
entire infrastructure to support bloat in the DFZ.

Brian


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


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



From ipv6-bounces@ietf.org Wed Aug 29 15:46:15 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQTSZ-0003z7-Ty; Wed, 29 Aug 2007 15:44:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQTSU-0003fD-UF
	for ipv6@ietf.org; Wed, 29 Aug 2007 15:44:10 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQTST-000594-Co
	for ipv6@ietf.org; Wed, 29 Aug 2007 15:44:10 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 77377198661;
	Wed, 29 Aug 2007 22:44:08 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 1516A19865B;
	Wed, 29 Aug 2007 22:44:08 +0300 (EEST)
Message-ID: <46D5B80F.2090106@piuha.net>
Date: Wed, 29 Aug 2007 21:16:47 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.13 (X11/20070824)
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>, Vishwas Manral <vishwas.ietf@gmail.com>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
In-Reply-To: <200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
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: cab78e1e39c4b328567edb48482b6a69
Cc: manoj@ipinfusion.com, IPv6 WG <ipv6@ietf.org>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

What Thomas says below is valid. We need to know
what problem or purpose we are building a new
safe RHx for. Once that is known, we can evaluate
if your design meets the goals, ensure that the
problem is of general interest for the Internet community
that it makes sense to recommend it be implemented,
etc.

Jari

Thomas Narten wrote:
> Sorry to interrupt, but I'd suggest that working on a new RH design is
> mostly a waste of time at this point.
>
> Can we please _first_ identify a user/customer for a proposed RH, so
> we are sure we actually design something useful? And at the same time
> be sure we have a transition strategy for getting it
> implemented/deployed that makes sense (i.e., doesn't require upgrading
> parts of the infrastructure outside of the control of those wanting to
> take advantage of the RH?)
>
> I.e., exactly what _real_ problem are we trying to solve here?
>
> The idea that we can define something (with no clear expected use) and
> get it actually implemented and deployed is mostly naive. (My guess is
> this would be an _optional_ standard, and vendors mostly wouldn't
> bother to implement it -- if no one actually needs it).
>
> One can argue that the whole RH0 debacle results from designing
> functionality for which there was no clear customer/use. Time and time
> again, this sort of protocol design results in (at best) wasted
> effort.
>
> Thomas
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>
>   



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



From ipv6-bounces@ietf.org Wed Aug 29 16:06:44 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQTmU-0005Pt-OC; Wed, 29 Aug 2007 16:04:50 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQTmO-0005Ph-Gc
	for ipv6@ietf.org; Wed, 29 Aug 2007 16:04:46 -0400
Received: from nz-out-0506.google.com ([64.233.162.233])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQTmO-0008Kw-0v
	for ipv6@ietf.org; Wed, 29 Aug 2007 16:04:44 -0400
Received: by nz-out-0506.google.com with SMTP id n1so241002nzf
	for <ipv6@ietf.org>; Wed, 29 Aug 2007 13:04:43 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=ZdIJGfVHTZc5bumaUaW5AOnGEO8lzwIT94Pej9Hzd1QkvP1pdqAmrrye6iZDVRuwJ7kNqI0FlfFBK7wMrioNR0LvfGRX/4YiPjD1YQZ/udp7DI9bRpw8pLjec6py9hjYraXmme5diI8fVgX48cpugrmqKT9BasZvN1oE9T3ZFgE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=MTeDiqbZbtzyP3dsEL2q8amQftlANxrvJozritSxuUXSENN3vAHSybODzzBxosbhW9EaEiizyiHF5GYuYDpz/vWsKB/ZRILDqYZfbYx+CWlcbEfxMt0B3AYz8Rt22QvQVi9Sv3AdR+XJse4r2TAyd6Xfv0HWF4MIDPLLv43vS2E=
Received: by 10.141.76.21 with SMTP id d21mr531636rvl.1188417882409;
	Wed, 29 Aug 2007 13:04:42 -0700 (PDT)
Received: from ?10.1.1.7? ( [222.153.2.24])
	by mx.google.com with ESMTPS id g22sm20765599rvb.2007.08.29.13.04.30
	(version=SSLv3 cipher=RC4-MD5); Wed, 29 Aug 2007 13:04:32 -0700 (PDT)
Message-ID: <46D5D148.6080701@gmail.com>
Date: Thu, 30 Aug 2007 08:04:24 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
In-Reply-To: <200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: manoj@ipinfusion.com, IPv6 WG <ipv6@ietf.org>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-08-30 02:08, Thomas Narten wrote:
> Sorry to interrupt, but I'd suggest that working on a new RH design is
> mostly a waste of time at this point.
> 
> Can we please _first_ identify a user/customer for a proposed RH, 

I agree. A use case draft should be the first step.

Incidentally, RFC 2460 is clear that unknown headers should cause the
packet to be dropped, so the transition strategy is tricky in any case.

    If, as a result of processing a header, a node is required to proceed
    to the next header but the Next Header value in the current header is
    unrecognized by the node, it should discard the packet and send an
    ICMP Parameter Problem message to the source of the packet, with an
    ICMP Code value of 1 ("unrecognized Next Header type encountered")
    and the ICMP Pointer field containing the offset of the unrecognized
    value within the original packet.

     Brian

> so
> we are sure we actually design something useful? And at the same time
> be sure we have a transition strategy for getting it
> implemented/deployed that makes sense (i.e., doesn't require upgrading
> parts of the infrastructure outside of the control of those wanting to
> take advantage of the RH?)
> 
> I.e., exactly what _real_ problem are we trying to solve here?
> 
> The idea that we can define something (with no clear expected use) and
> get it actually implemented and deployed is mostly naive. (My guess is
> this would be an _optional_ standard, and vendors mostly wouldn't
> bother to implement it -- if no one actually needs it).
> 
> One can argue that the whole RH0 debacle results from designing
> functionality for which there was no clear customer/use. Time and time
> again, this sort of protocol design results in (at best) wasted
> effort.
> 
> Thomas
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

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



From ipv6-bounces@ietf.org Wed Aug 29 16:13:23 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQTsv-0007HI-Im; Wed, 29 Aug 2007 16:11:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQTso-0007Gv-Lk
	for ipv6@ietf.org; Wed, 29 Aug 2007 16:11:24 -0400
Received: from nz-out-0506.google.com ([64.233.162.236])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQTsn-0006SW-51
	for ipv6@ietf.org; Wed, 29 Aug 2007 16:11:22 -0400
Received: by nz-out-0506.google.com with SMTP id n1so242486nzf
	for <ipv6@ietf.org>; Wed, 29 Aug 2007 13:11:20 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=djAvUDJdZA0pYk7Q0NjvWv3x09nD5FOvvQh34FqMu5dD/cnxG0e5DY6hLXo2bvoYK9rR+uBv8E+N6uM2Od4pI6EiSf4uXNGWC6MAor87+vfTX7zlB+9T2O6B+S5tKVrg7rxXjwsHx/xSzbdjDDeyCjuycKsSiCdYoz47f5522LY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=sj9k+CR9PGMft1ExWk/XKexqQgLHYKXdhwSd16XKtZMeyDPW6rqOAODkXmh0H7JSZakLeQGjjqWRVopyspIXuaQINTU4YWEyHkZ+wH9AhKInSHKjsJ91u0XzeYzHoiwNjE90gHvU+CUAI023vnylq99/ZneqXr37a15wx6zpsWo=
Received: by 10.141.42.10 with SMTP id u10mr539392rvj.1188418280045;
	Wed, 29 Aug 2007 13:11:20 -0700 (PDT)
Received: from ?10.1.1.7? ( [222.153.2.24])
	by mx.google.com with ESMTPS id l27sm20769392rvb.2007.08.29.13.11.12
	(version=SSLv3 cipher=RC4-MD5); Wed, 29 Aug 2007 13:11:13 -0700 (PDT)
Message-ID: <46D5D2DB.8000207@gmail.com>
Date: Thu, 30 Aug 2007 08:11:07 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
References: <460A4920-4D82-4563-919C-45948582795C@nokia.com>
	<7B57389B-722E-4902-B822-A70278CC85C8@muada.com>
In-Reply-To: <7B57389B-722E-4902-B822-A70278CC85C8@muada.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: IPv6 Mailing List <ipv6@ietf.org>,
	Brian Haberman <brian@innovationslab.net>, bob.hinden@nokia.com
Subject: Re: Request to Advance:  <draft-ietf-ipv6-deprecate-rh0-01.txt>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-08-30 04:40, Iljitsch van Beijnum wrote:
> On 27-aug-2007, at 23:21, ext ext Bob Hinden wrote:
> 
>> On behalf of the IPv6 WG, the chairs request the advancement of
> 
> That was fast.

Iljitsch, I think it's a fair judgement of the rough consensus
(which is obviously going to stay rough, however long we
continue to discuss).

     Brian

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



From ipv6-bounces@ietf.org Wed Aug 29 16:16:50 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQTwI-0008JM-Om; Wed, 29 Aug 2007 16:14:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQTwE-0008JF-W9
	for ipv6@ietf.org; Wed, 29 Aug 2007 16:14:54 -0400
Received: from ns.virtualized.org ([204.152.189.134] helo=mail.virtualized.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQTwD-0006Yz-Gs
	for ipv6@ietf.org; Wed, 29 Aug 2007 16:14:54 -0400
Received: from terminus.local (ns.virtualized.org [204.152.189.134])
	by mail.virtualized.org (8.12.9p1/8.12.9) with ESMTP id l7TJp0u3032776; 
	Wed, 29 Aug 2007 12:51:01 -0700 (PDT)
	(envelope-from drc@virtualized.org)
Received: from [127.0.0.1] by terminus.local (PGP Universal service);
	Wed, 29 Aug 2007 13:14:41 -0700
X-PGP-Universal: processed;
	by terminus.local on Wed, 29 Aug 2007 13:14:41 -0700
In-Reply-To: <46D5D148.6080701@gmail.com>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Message-Id: <1ED2DE65-EB5E-4B17-9125-E62E4C605BAA@virtualized.org>
From: David Conrad <drc@virtualized.org>
Date: Wed, 29 Aug 2007 13:14:40 -0700
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi,

On Aug 29, 2007, at 1:04 PM, Brian E Carpenter wrote:
> On 2007-08-30 02:08, Thomas Narten wrote:
>> Can we please _first_ identify a user/customer for a proposed RH,
> I agree. A use case draft should be the first step.

I'm not sure it matters since:

> Incidentally, RFC 2460 is clear that unknown headers should cause the
> packet to be dropped, so the transition strategy is tricky in any  
> case.

Water under the bridge and all that, but I'm curious: what was the  
rationale for this?  It would seem to imply it is impossible to do  
incremental deployment of new headers, and thus essentially freezes  
routing header development for the lifetime of IPv6.

Am I misunderstanding?

Thanks,
-drc


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



From ipv6-bounces@ietf.org Wed Aug 29 16:32:08 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQUB7-0000ef-PQ; Wed, 29 Aug 2007 16:30:17 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQUB3-0000dH-PZ
	for ipv6@ietf.org; Wed, 29 Aug 2007 16:30:13 -0400
Received: from e5.ny.us.ibm.com ([32.97.182.145])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQUB3-0002Dj-5J
	for ipv6@ietf.org; Wed, 29 Aug 2007 16:30:13 -0400
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236])
	by e5.ny.us.ibm.com (8.13.8/8.13.8) with ESMTP id l7TKUCcX005609
	for <ipv6@ietf.org>; Wed, 29 Aug 2007 16:30:12 -0400
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64])
	by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v8.5) with ESMTP id
	l7TKUCVF541726 for <ipv6@ietf.org>; Wed, 29 Aug 2007 16:30:12 -0400
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1])
	by d01av04.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l7TKUCtv009280 for <ipv6@ietf.org>; Wed, 29 Aug 2007 16:30:12 -0400
Received: from cichlid.raleigh.ibm.com (wecm-9-67-159-36.wecm.ibm.com
	[9.67.159.36])
	by d01av04.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l7TKUBqc009226
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 29 Aug 2007 16:30:12 -0400
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 l7TKUAZf023704;
	Wed, 29 Aug 2007 16:30:10 -0400
Message-Id: <200708292030.l7TKUAZf023704@cichlid.raleigh.ibm.com>
To: David Conrad <drc@virtualized.org>
In-reply-to: <1ED2DE65-EB5E-4B17-9125-E62E4C605BAA@virtualized.org>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com>
	<1ED2DE65-EB5E-4B17-9125-E62E4C605BAA@virtualized.org>
Comments: In-reply-to David Conrad <drc@virtualized.org>
	message dated "Wed, 29 Aug 2007 13:14:40 -0700."
Date: Wed, 29 Aug 2007 16:30:09 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: IPv6 WG <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi David.

> > Incidentally, RFC 2460 is clear that unknown headers should cause the
> > packet to be dropped, so the transition strategy is tricky in any  
> > case.

> Water under the bridge and all that, but I'm curious: what was the  
> rationale for this?  It would seem to imply it is impossible to do  
> incremental deployment of new headers, and thus essentially freezes  
> routing header development for the lifetime of IPv6.

The way routing headers work in IPv6, the next destination in the
routing header gets placed into the destination field of the base IPv6
packet. Thus, the packet itself (because of the routing header) is
addressed to the router in question. If that router doesn't understand
how to process it (i.e., presumably to place the next address into the
destination field -- after doing whatever other processing is
appropriate), there isn't much it can do other than drop it. Same as
any other node receiving a packet addressed to it that it doesn't know
how to handle.

The benefit of this design (compared with IPv4) is that intermediate
routers do no need to inspect packets containing routing headers,
unless the router is the actual destination. In IPv4, every router has
to look at the option, including routers that don't do anything as a
result of looking at the routing option...

Thomas

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



From ipv6-bounces@ietf.org Wed Aug 29 16:32:44 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQUBu-0000wc-Ft; Wed, 29 Aug 2007 16:31:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQUBn-0000rh-TT
	for ipv6@ietf.org; Wed, 29 Aug 2007 16:31:00 -0400
Received: from nz-out-0506.google.com ([64.233.162.234])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQUBm-0008QI-EC
	for ipv6@ietf.org; Wed, 29 Aug 2007 16:30:59 -0400
Received: by nz-out-0506.google.com with SMTP id n1so246693nzf
	for <ipv6@ietf.org>; Wed, 29 Aug 2007 13:30:57 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=O5+0JVaSelM+rXfj4WjJbbO8uWEV59XkkGaZWx9kKyENXOr5HhiNo5A+1A0MQEHGgiPCtt5DyMXTsCTgMcDCGwv5gvr6MAY9/hdKdKUdxseyOj1N6OpcTEXTN4CJavoXE7DFZRIj0xwsR9UpBwwIcwZDj5SkSZAlXQnHJZfuU+Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=NZlTlPFYdBkJ4kT+2mNh88DPNkVe9HM3jppxm22erIrN0oLJ21REjL37q2Xt4Y6M+RP0HO97RpUb/LD4bpfPfdGYWk9/Ap23dbkHakSrJYfcrzDSm3nSsB8Z0e2QKiY/I3cVPv9Ack41fFCZwArSfu9iPcV0upIncVfDw9xxSyA=
Received: by 10.140.147.5 with SMTP id u5mr537722rvd.1188419456973;
	Wed, 29 Aug 2007 13:30:56 -0700 (PDT)
Received: from ?10.1.1.7? ( [222.153.2.24])
	by mx.google.com with ESMTPS id b34sm23439811rvf.2007.08.29.13.30.51
	(version=SSLv3 cipher=RC4-MD5); Wed, 29 Aug 2007 13:30:54 -0700 (PDT)
Message-ID: <46D5D776.9030603@gmail.com>
Date: Thu, 30 Aug 2007 08:30:46 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: David Conrad <drc@virtualized.org>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com>
	<1ED2DE65-EB5E-4B17-9125-E62E4C605BAA@virtualized.org>
In-Reply-To: <1ED2DE65-EB5E-4B17-9125-E62E4C605BAA@virtualized.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-08-30 08:14, David Conrad wrote:
> Hi,
> 
> On Aug 29, 2007, at 1:04 PM, Brian E Carpenter wrote:
>> On 2007-08-30 02:08, Thomas Narten wrote:
>>> Can we please _first_ identify a user/customer for a proposed RH,
>> I agree. A use case draft should be the first step.
> 
> I'm not sure it matters since:
> 
>> Incidentally, RFC 2460 is clear that unknown headers should cause the
>> packet to be dropped, so the transition strategy is tricky in any case.
> 
> Water under the bridge and all that, but I'm curious: what was the 
> rationale for this?  It would seem to imply it is impossible to do 
> incremental deployment of new headers, and thus essentially freezes 
> routing header development for the lifetime of IPv6.
> 
> Am I misunderstanding?

I just looked this up in 2460 myself, and I'm jet lagged so I may
be confused, but indeed this seems to make it very hard to deploy any
new header except as a fork-lift upgrade among consenting systems.

    Brian

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



From ipv6-bounces@ietf.org Wed Aug 29 16:38:21 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQUHC-0004nh-6D; Wed, 29 Aug 2007 16:36:34 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQUH7-0004mO-UX
	for ipv6@ietf.org; Wed, 29 Aug 2007 16:36:30 -0400
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQUH7-0002yu-Fw
	for ipv6@ietf.org; Wed, 29 Aug 2007 16:36:29 -0400
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216])
	by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l7TKaGTf028468
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 29 Aug 2007 13:36:22 -0700 (PDT)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1])
	by blv-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id
	l7TKaGlM000190; Wed, 29 Aug 2007 13:36:16 -0700 (PDT)
Received: from XCH-NEBH-11.ne.nos.boeing.com (xch-nebh-11.ne.nos.boeing.com
	[128.225.80.27])
	by blv-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l7TKaF5r000177; Wed, 29 Aug 2007 13:36:16 -0700 (PDT)
Received: from XCH-NE-1V2.ne.nos.boeing.com ([128.225.80.43]) by
	XCH-NEBH-11.ne.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 29 Aug 2007 16:36:15 -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: Wed, 29 Aug 2007 16:35:41 -0400
Message-ID: <CA7D9B4A761066448304A6AFC09ABDA9015AD3F2@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <46D5D148.6080701@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New Routing Header!!!
Thread-Index: AcfqeNo7zMZL8RbDQZGCPju35RmbhQAAoqlQ
References: <200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
X-OriginalArrivalTime: 29 Aug 2007 20:36:15.0556 (UTC)
	FILETIME=[3EE7A040:01C7EA7C]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: manoj@ipinfusion.com, IPv6 WG <ipv6@ietf.org>
Subject: RE: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> -----Original Message-----
> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]=20
>=20
> On 2007-08-30 02:08, Thomas Narten wrote:
> > Sorry to interrupt, but I'd suggest that working on a new=20
> RH design is
> > mostly a waste of time at this point.
> >=20
> > Can we please _first_ identify a user/customer for a proposed RH,=20
>=20
> I agree. A use case draft should be the first step.

Problem is, I have no trouble seeing uses for RH0, or whatever new
scheme takes its place. The only problems I've seen mentioned repeatedly
are the potential for DOS attacks in ISP nets.

But ISP nets are not the only application for IPv6.

So why don't ISPs simply filter out any RH0 traffic from their edge
gateways, and leave it at that? And the rest of us can still make use of
this tool, with no change required to RFC 2460.

As always, there are workarounds like MPLS, if RH0 is eliminated. I'm
having a hard time understanding why edge router filters don't work
infinitely better than a mod to RFC 2460.

Bert

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



From ipv6-bounces@ietf.org Wed Aug 29 16:40:08 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQUIv-0005iJ-FW; Wed, 29 Aug 2007 16:38:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQU2J-0006Wd-PA
	for ipv6@ietf.org; Wed, 29 Aug 2007 16:21:12 -0400
Received: from nz-out-0506.google.com ([64.233.162.225])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQU2D-0007tZ-Ke
	for ipv6@ietf.org; Wed, 29 Aug 2007 16:21:11 -0400
Received: by nz-out-0506.google.com with SMTP id n1so244498nzf
	for <ipv6@ietf.org>; Wed, 29 Aug 2007 13:21:05 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=N60ARpo1ciIoixHcoiFFwDT/0vzHdoguouCzIEUiXvkStvvq2/0eG9AAFlk81iIZHsdwf5FvkyRAvrRPVecAKSo7MNvTvgaz9998qDfIXH2yY+q0rCTPkytrlil9WW+tTMzZUEA2hMEq9xHppfR71AI7DtjE7YsTntaC0XSJ+Pk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=aVGXmgzOddwHIaUygaCofijcLik2LoASlxtGIYuWf38X+dKQXakAwsICJkAnYyKvfoAhqJwxtRcGmAkPOAH6gXxtcpI9naP4L9M1tl70XItAe+WiYJYShCb4JvZ7yvdMgp2gtnD46KXpq3pAdWugBo6+9pa0c7e2lJmhZjnREqM=
Received: by 10.141.29.18 with SMTP id g18mr535071rvj.1188418864148;
	Wed, 29 Aug 2007 13:21:04 -0700 (PDT)
Received: from ?10.1.1.7? ( [222.153.2.24])
	by mx.google.com with ESMTPS id 3sm23054656rvi.2007.08.29.13.20.58
	(version=SSLv3 cipher=RC4-MD5); Wed, 29 Aug 2007 13:21:01 -0700 (PDT)
Message-ID: <46D5D525.30005@gmail.com>
Date: Thu, 30 Aug 2007 08:20:53 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: briand@ca.afilias.info
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>	<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>	<471515FC-E1E1-4C83-99AA-A9821E0C2FF5@muada.com>
	<!
	!	63886.74.122.168.81.1188025388.squirrel@look.libertyrms.com>	<200708291423.l7TENQZ8000329@cichlid.raleigh.ibm.com>	<79358CCF-0A4B-424D-BA32-14099B3EF257@muada.com>
	<61722.74.122.168.81.1188400653.squirrel@look.libertyrms.com>
In-Reply-To: <61722.74.122.168.81.1188400653.squirrel@look.libertyrms.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: Thomas Narten <narten@us.ibm.com>,
	Iljitsch van Beijnum <iljitsch@muada.com>,
	IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: History of autoconfig RFCs and siblings, please?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Brian D,

You seem to be assuming that PI will be the dominant mode.
This seems very unlikely, since the vast majority of users
(i.e. SOHO) have no interest in what their IP address is and
no motivation to pay extra for PI. We have no possible
difficulty in supporting a few million PI prefixes in the
/48 or /56 world currently planned (apart from BGP4 blowing
up, of course, but that's being discussed elsewhere).

Regards
    Brian Carpenter

On 2007-08-30 03:17, briand@ca.afilias.info wrote:
> Iljitsch wrote:
>> On 29-aug-2007, at 16:23, Thomas Narten wrote:
>>>> (I suppose it's a bit late in the game to go back to MAC-48 as II?)
>>> Yes. The difficulty is figuring out how to move to something different
>>> in a backwards-compatable way. I.e., we'd need a transition strategy.
>> But what would be the point of doing that now?
> 
> The point, which I have avoided making until now, is that II has direct
> impact on the available range of assignments by RIRs to LIRs, for PI blocks,
> that also allow for very long timescale predictive assignments.
> 
> Basically, the minimum prefix size * number of assignments * LIRs,
> when projected over a timeframe of decades, while preserving a global
> DFZ consisting of one PI block per LIR, has a problem fitting into the
> number of bits per RIR.
> 
> Right now, RIRs are reserving only an additional 2 bits per LIR assignment,
> for "growth". Alternative allocation policies (bisection) don't guarantee
> the ability to assign arbitrarily large blocks indefinitely - while that
> is in fact the long-term requirement. Block sizes *should* increase over
> time, even as the frequency of their assignment decreases.
> 
> What works best is, a best-fit approach, where any organization gets way
> more space than they need, sized according to their own best guess as to
> long-term growth *potential*.
> 
> Then, reserve even more space for each, in a consistent manner.
> 
> Take all these requests, and fill them in an optimized space-packing manner.
> 
> At some point, growth requests get filled via "growing" the assignment for
> a given LIR into its reserved space.
> 
> And, long-term periodic reviews of those growth patterns may result in
> bisecting *some* of those reserved blocks to make more space available
> for similar assignments.
> 
> This can be shown to meet the requirements of individual LIRs to within
> a few orders of magnitude of their long-term projections (pretty good),
> and at the same time, optimize the packing efficiency, meaning the truly
> free space will not be fragmented except to the degree absolutely necessary
> for the existing assignments.
> 
> This means that new assignments have the largest possible potential prefix
> size available, compared to other allocation methods. This can even be
> demonstrated or possibly even proven mathematically, by modeling the
> problem space.
> 
>> The fact that we have so many local bits in the IPv6 address is our
>> insurance policy against address policy screwups because a single /64
>> is enough to run a network of arbitrary size if you forego stateless
>> autoconfig.
> 
> The same would be true of /80, which is what MAC-48 would result in, for
> minimum prefix size for autoconf (and thus the standard end-user assignment
> size).
> 
> Of the 16 bits reclaimed via this change, I would propose to the RIRs,
> that 4 bits be added to initial allocations, 4 bits to reservations above
> the initial allocations (for long-term growth), and the other 8 bits add
> to the total space available for the RIRs to allocate to LIRs - by adjusting
> the minimum and initial allocation sizes by 8 bits.
> 
> The numbers (4 bits and 8 bits) are not accidental - they are one nibble
> in size, which matches up with the boundaries for reverse address lookups,
> via ip6.arpa - which uses nibbles.
> 
> It seems to me, that while it would be an uphill battle, the main two issues
> are transition and compatibity, and inertia (e.g. deployed code and
> networks.)
> 
> The overall benefits to address space assignment, IMHO, outweigh that cost,
> especially when considering the long-term health of the DFZ and the cost
> to member organizations when having to do expensive upgrades to their
> entire infrastructure to support bloat in the DFZ.
> 
> Brian
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

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



From ipv6-bounces@ietf.org Wed Aug 29 17:53:59 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQVS5-0005Pa-TQ; Wed, 29 Aug 2007 17:51:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQVRz-0005JE-UR
	for ipv6@ietf.org; Wed, 29 Aug 2007 17:51:47 -0400
Received: from [2001:6f8:387:2057:ea05:e98a:6f83:d890] (helo=moog.chdir.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQVRz-0003ue-En
	for ipv6@ietf.org; Wed, 29 Aug 2007 17:51:47 -0400
Received: from [2002:58a4:b573:1:20d:93ff:feeb:2d3]
	(helo=localhost.localdomain)
	by moog.chdir.org with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.63) (envelope-from <arno@natisbad.org>)
	id 1IQVRr-0007L6-Qe; Wed, 29 Aug 2007 23:51:39 +0200
From: arno@natisbad.org (Arnaud Ebalard)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com>
	<1ED2DE65-EB5E-4B17-9125-E62E4C605BAA@virtualized.org>
	<46D5D776.9030603@gmail.com>
X-GnuPG-Key: 0x047A5026
X-Hashcash: 1:20:070829:brian.e.carpenter@gmail.com::Q3xtBADpza/8INbL:00000000000000000000000000000000001bnY
X-Hashcash: 1:20:070829:ipv6@ietf.org::CQK4wsWb8TrsVRAM:00000saL
X-Hashcash: 1:20:070829:drc@virtualized.org::bOFVWBRGjDVYtozx:0000000000000000000000000000000000000000009WZl
Date: Wed, 29 Aug 2007 23:51:35 +0200
In-Reply-To: <46D5D776.9030603@gmail.com> (Brian E. Carpenter's message of
	"Thu, 30 Aug 2007 08:30:46 +1200")
Message-ID: <87ejhmqaag.fsf@natisbad.org>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.95 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: -0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Brian, Hi guys,

Brian E Carpenter <brian.e.carpenter@gmail.com> writes:

>> Water under the bridge and all that, but I'm curious: what was the
>> rationale for this?  It would seem to imply it is impossible to do
>> incremental deployment of new headers, and thus essentially freezes
>> routing header development for the lifetime of IPv6.
>>
>> Am I misunderstanding?
>
> I just looked this up in 2460 myself, and I'm jet lagged so I may
> be confused, but indeed this seems to make it very hard to deploy any
> new header except as a fork-lift upgrade among consenting systems.

End-to-End. [with the deprecation of RH0,] IPv6 packets will flow from
the source to the destination found in the IPv6 header, where the
specific implementation will have the context and the code to analyse
(filter) it and understand it (process the tiny details of the headers
and upper layer).

This leaves a simple work for the core: find the best path from the
source to the destination, i.e. route the packet based on the content of
IPv6 header destination address. End hosts then stack functionalities
on top of that. The most low level (i.e. most demanding) functionalities
start working in extension headers (MIPv6, ...)

If someone comes with a _real_ need for having the core network
providing help outside an efficient routing of its traffic to a specific
destination, it will find help to make it happen but that's not the
purpose of IP. 

Let's let people that still argue in favor of source-routing prove

- there is a need
- there is a need at L3
- there is a need at L3 to blindly process their pkts
- there is a need at L3 to blindly process their pkts and it's safe

And yes, deprecation removes blind source routing from IP stacks and
leaves little room for having it coming back.

Regards,

a+

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



From ipv6-bounces@ietf.org Wed Aug 29 18:18:44 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQVqE-0007bS-6S; Wed, 29 Aug 2007 18:16:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQVqB-0007Zs-0i
	for ipv6@ietf.org; Wed, 29 Aug 2007 18:16:47 -0400
Received: from nz-out-0506.google.com ([64.233.162.224])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQVq9-0004UG-QS
	for ipv6@ietf.org; Wed, 29 Aug 2007 18:16:47 -0400
Received: by nz-out-0506.google.com with SMTP id n1so266647nzf
	for <ipv6@ietf.org>; Wed, 29 Aug 2007 15:16:45 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:mime-version:from:subject:date:importance:x-priority:to:content-transfer-encoding:content-type:message-id;
	b=boRRx/NaJdin/Hs7ldCU8Se/zkblH1qx1mBuLP0GcgJ70toBYNacziecJ5n/JBaEn28xQPXTk4N3Fx5PTGIlZ4ZvUX3l0KGPaV1Do5uEmYmbPo91E75a9oDQrhn5hl2L8HvEH/xqGOY+0F9Su8HZ54vsynj9qM05s5aShGE+dZ0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:mime-version:from:subject:date:importance:x-priority:to:content-transfer-encoding:content-type:message-id;
	b=oFREziYXGgEHjsBpJXUsIEFrqF/A4+RWwSeIylLOPCk7dVt6v7y+XysLg76xttnmr7j/8ih5svounMZ5axV2RDIwuVVPFcQBx5Ic+AUSwzJSxLA1P8UMciRJ6XvX8Rqlm/+WMfDPyK5zMbjnHiAnG8jBCCKNQI8Yc/o4fmYBVgY=
Received: by 10.64.76.15 with SMTP id y15mr2355684qba.1188425805175;
	Wed, 29 Aug 2007 15:16:45 -0700 (PDT)
Received: from Inbox ( [70.208.213.243])
	by mx.google.com with ESMTPS id e19sm4880268qbe.2007.08.29.15.16.42
	(version=SSLv3 cipher=RC4-MD5); Wed, 29 Aug 2007 15:16:43 -0700 (PDT)
MIME-Version: 1.0
From: TJ <trejrco@gmail.com>
Date: Wed, 29 Aug 2007 18:16:43 -0400
Importance: normal
X-Priority: 3
To: IPv6 WG <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
Message-ID: <46d5f04b.131f400a.15fe.7fb3@mx.google.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Subject: RE: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Rough guess - ISPs don't like the prospect of having to look at/for ext hdr=
s of every packet ...


/TJ (mobile)

-----Original Message-----
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
Cc: manoj@ipinfusion.com; "IPv6 WG" <ipv6@ietf.org>
Sent: 8/29/07 4:35 PM
Subject: RE: New Routing Header!!!

> -----Original Message-----
> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]=20
>=20
> On 2007-08-30 02:08, Thomas Narten wrote:
> > Sorry to interrupt, but I'd suggest that working on a new=20
> RH design is
> > mostly a waste of time at this point.
> >=20
> > Can we please _first_ identify a user/customer for a proposed RH,=20
>=20
> I agree. A use case draft should be the first step.

Problem is, I have no trouble seeing uses for RH0, or whatever new
scheme takes its place. The only problems I've seen mentioned repeatedly
are the potential for DOS attacks in ISP nets.

But ISP nets are not the only application for IPv6.

So why don't ISPs simply filter out any RH0 traffic from their edge
gateways, and leave it at that? And the rest of us can still make use of
this tool, with no change required to RFC 2460.

As always, there are workarounds like MPLS, if RH0 is eliminated. I'm
having a hard time understanding why edge router filters don't work
infinitely better than a mod to RFC 2460.

Bert

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


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



From ipv6-bounces@ietf.org Wed Aug 29 19:08:49 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQWcW-0004P1-BV; Wed, 29 Aug 2007 19:06:44 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQWcQ-0004KB-TR
	for ipv6@ietf.org; Wed, 29 Aug 2007 19:06:40 -0400
Received: from stl-smtpout-01.boeing.com ([130.76.96.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQWcP-0005Yy-Nd
	for ipv6@ietf.org; Wed, 29 Aug 2007 19:06:38 -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 l7TN6Y9S005145
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Wed, 29 Aug 2007 18:06:36 -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
	l7TN6X6e008092; Wed, 29 Aug 2007 16:06:33 -0700 (PDT)
Received: from XCH-NEBH-11.ne.nos.boeing.com (xch-nebh-11.ne.nos.boeing.com
	[128.225.80.27])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l7TN6W0w008033; Wed, 29 Aug 2007 16:06:33 -0700 (PDT)
Received: from XCH-NE-1V2.ne.nos.boeing.com ([128.225.80.43]) by
	XCH-NEBH-11.ne.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 29 Aug 2007 19:06: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
Date: Wed, 29 Aug 2007 19:06:19 -0400
Message-ID: <CA7D9B4A761066448304A6AFC09ABDA9015AD3F5@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <46d5f04b.131f400a.15fe.7fb3@mx.google.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New Routing Header!!!
Thread-Index: AcfqimnNbXfw8ruhQ0eY9Sqvj4ELcAABdY1A
References: <46d5f04b.131f400a.15fe.7fb3@mx.google.com>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "TJ" <trejrco@gmail.com>, "IPv6 WG" <ipv6@ietf.org>
X-OriginalArrivalTime: 29 Aug 2007 23:06:32.0098 (UTC)
	FILETIME=[3D2EC020:01C7EA91]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: 
Subject: RE: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

-----Original Message-----
From: TJ [mailto:trejrco@gmail.com]=20
Sent: Wednesday, August 29, 2007 6:17 PM
To: IPv6 WG
Subject: RE: New Routing Header!!!

>> So why don't ISPs simply filter out any RH0 traffic
>> from their edge gateways, and leave it at that?
>
> Rough guess - ISPs don't like the prospect of having to
> look at/for ext hdrs of every packet ...

Granted, although at edges only. Thing is, the genie is out of that
bottle already. Words in an RFC can't provide protection against RH0 DOS
attacks, or any other future attack permitted today by some other
unknown mechanism.

Bert

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



From ipv6-bounces@ietf.org Wed Aug 29 19:36:04 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQX33-0007OV-P2; Wed, 29 Aug 2007 19:34:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQX30-0007OF-Ht
	for ipv6@ietf.org; Wed, 29 Aug 2007 19:34:06 -0400
Received: from smtp117.iad.emailsrvr.com ([207.97.245.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQX2z-00063H-DQ
	for ipv6@ietf.org; Wed, 29 Aug 2007 19:34:06 -0400
Received: by relay1.r1.iad.emailsrvr.com (Authenticated sender:
	dow.street-AT-linquest.com) with ESMTP id 6336944E3BE; 
	Wed, 29 Aug 2007 19:34:04 -0400 (EDT)
In-Reply-To: <87ejhmqaag.fsf@natisbad.org>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com>
	<1ED2DE65-EB5E-4B17-9125-E62E4C605BAA@virtualized.org>
	<46D5D776.9030603@gmail.com> <87ejhmqaag.fsf@natisbad.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <8CF7F46A-8231-44CF-B265-B46F38072E0D@linquest.com>
Content-Transfer-Encoding: 7bit
From: Dow Street <dow.street@linquest.com>
Date: Wed, 29 Aug 2007 16:33:49 -0700
To: arno@natisbad.org (Arnaud Ebalard)
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: IPv6 WG <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Aug 29, 2007, at 2:51 PM, Arnaud Ebalard wrote:

> Let's let people that still argue in favor of source-routing prove
>
> - there is a need

I see advertisement of specifics by multi-homed sites as a indication  
that they desire more control over how their traffic is routed.  If  
the architecture does not address that problem directly, I think it  
is likely to manifest itself indirectly at some other place (e.g. the  
RIB growth problem).

> - there is a need at L3

IP seems to be the right place in the stack to deal with issues of  
path selection and packet delivery.  Do you see a better place in a  
different layer?

> - there is a need at L3 to blindly process their pkts

Can you clarify what you mean by "blindly"?  As others have stated,  
including support for source routing in IPv6 does not necessarily  
mean that every IPv6 node in the network needs to be configured as a  
viable (intermediate) source routing destination.  I agree that a  
goal of the new draft should be to minimize the cost to uninterested  
nodes.

> - there is a need at L3 to blindly process their pkts and it's safe

Also, please clarify "safe".  Is this a question on the acceptable  
range of traffic (trend) variability?  Of the issues raised at csw07,  
which do you think are unable to be mitigated through a revised RH  
specification?  In your opinion, which issues are currently  
unmitigated in the RH4 draft?

Thanks,
Dow




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



From ipv6-bounces@ietf.org Wed Aug 29 20:59:23 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQYLP-0006MF-89; Wed, 29 Aug 2007 20:57:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQYLN-0006KC-8n
	for ipv6@ietf.org; Wed, 29 Aug 2007 20:57:09 -0400
Received: from qb-out-0506.google.com ([72.14.204.236])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQYLM-0007yW-43
	for ipv6@ietf.org; Wed, 29 Aug 2007 20:57:09 -0400
Received: by qb-out-0506.google.com with SMTP id o21so376578qba
	for <ipv6@ietf.org>; Wed, 29 Aug 2007 17:57:07 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=ft8kPMXsXFbbpTiY+EZR2D/vQPG32dLQgFygm0Ebpphl7Z7kuCZZdyaMKcFfTC3j1xjX+tdJUkFSOfYu+MUGIyguhIMZzNI3jS7JlEX639xmh0jpZuN7MBxhOkmnUrde/gEirtTa4judKKw0z9p4aKqM/OEH/fg0JAkTa4FScNU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=Jjp3c5UCvFfjakJrdBkAEIq7tFax+JazCN2/yGDZfhWOV39Q+NwVzelF5IB8LIGGj0Rg6alDEMvEmHi+nPJIkYQZPPBNAXf8/iFgh4FtDXBe7MUIKLskR0CsNuQWdww3F7t9n4OG+xWCqFglpzRQakwcDDctTWMPvP8tlrtPIVo=
Received: by 10.142.225.11 with SMTP id x11mr60322wfg.1188435427158;
	Wed, 29 Aug 2007 17:57:07 -0700 (PDT)
Received: by 10.142.84.8 with HTTP; Wed, 29 Aug 2007 17:57:05 -0700 (PDT)
Message-ID: <77ead0ec0708291757m28328d76m85f262036d54040a@mail.gmail.com>
Date: Thu, 30 Aug 2007 10:57:05 +1000
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Thomas Narten" <narten@us.ibm.com>
In-Reply-To: <200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: manoj@ipinfusion.com, IPv6 WG <ipv6@ietf.org>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Thomas,

Thanks a lot for your very kind comments.

> Sorry to interrupt, but I'd suggest that working on a new RH design is
> mostly a waste of time at this point.
I understand your point completely. It sounds very logical to have a
use case before going in for a draft, which otherwise may not even be
required.

However it seems you have probably not followed mails I have sending
carefully enough. I have raised this issue on the list way back and
got some feed back too. I have found based on feedback the main uses
of the RH header to be Explicit Traffic Engineering as well as for OAM
purposes (something the IETF has underplayed for a long time). There
is a paper by Geoff Huston (I am not totally sure it was him), that
gives some use cases for operators.

I am ok, adding a section at the beginning of the draft for the same.

> One can argue that the whole RH0 debacle results from designing
> functionality for which there was no clear customer/use. Time and time
> again, this sort of protocol design results in (at best) wasted
> effort.
Having been the one to have identified the amplification attacks
around a couple of years ago, I realize the problems and related
security issues. However I am not sure of how you say there are no use
cases. I got the information asking that very question on the list. It
would be great if you can let me know what you base your assumptions
on?

Thanks,
Vishwas

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



From ipv6-bounces@ietf.org Wed Aug 29 21:05:54 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQYS7-00070u-AS; Wed, 29 Aug 2007 21:04:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQYS0-0006qy-9S
	for ipv6@ietf.org; Wed, 29 Aug 2007 21:04:00 -0400
Received: from qb-out-0506.google.com ([72.14.204.235])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQYRy-00085v-VV
	for ipv6@ietf.org; Wed, 29 Aug 2007 21:04:00 -0400
Received: by qb-out-0506.google.com with SMTP id o21so378065qba
	for <ipv6@ietf.org>; Wed, 29 Aug 2007 18:03:58 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=lFD4d+UYFLHNfUH4RUudLbHX1EhWcXecsH2M4cVGamz5pBhG0e9y9t5x5W8bfEavqbKfFDQ1wbfhyZSCbd67ieXeFouSxK4XQxz5gt0ATNY1y6JkeDEAPtod/OAc21GLCycXB6LR86vKWJC0+McJf/QdMRXCKqpUrGTyUyurGb8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=mew/HRjqQOXP5DfbC3AEUcB88sOmKcZ+mRo8BaXrhKaPaf6ajNXJTPTkk6GXuHRozjTjLT5NpW861svypKF80Q4FuCpqVfP7gzqwGjkRjxQvVUhTzeDaxdID7QPGgv1bX79Ah3yC4Gwrue91ZuKmbYA0ARpfN/nX7C/KX48lubI=
Received: by 10.142.101.17 with SMTP id y17mr63413wfb.1188435837440;
	Wed, 29 Aug 2007 18:03:57 -0700 (PDT)
Received: by 10.142.84.8 with HTTP; Wed, 29 Aug 2007 18:03:57 -0700 (PDT)
Message-ID: <77ead0ec0708291803u41284302o3f940241ec841f6e@mail.gmail.com>
Date: Thu, 30 Aug 2007 11:03:57 +1000
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "sengottuvelan srirangan" <sengottuvelan_s@yahoo.com>
In-Reply-To: <404874.74926.qm@web56505.mail.re3.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<404874.74926.qm@web56505.mail.re3.yahoo.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92788d1b003e07b99aff407d30cf4598
Cc: manoj@ipinfusion.com, IPv6 WG <ipv6@ietf.org>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Velan,

I agree things are a bit confusing.

The idea however is very simple. A routing header is looked at only by
the node identified as the destination address in the IPv6 packet, so
the processing algorithm is to be done only on those nodes. A
firewall, any other middlebox, or even routers that do deep packet
processing (its done in a lot of ASIC's right now at line-rate) can
drop packets when they see discrepancies as identified in the draft
below.

The answer of how to process an unrecognized Routing Header is given
in page 12-13 of RFC2460. Do have a look and let me know if things are
clearer.

Thanks,
Vishwas

On 8/30/07, sengottuvelan srirangan <sengottuvelan_s@yahoo.com> wrote:
> Hi Viswas,
>
> I could not get the below comments in the draft:
>
> "
> A Routing header is not examined or processed until it reaches the node
> identified in the Destination Address field of the IPv6 header.
>
>  There can be at most one RH4 header in any packet. A packet with
>  more   than one RH4 header is discarded. This functionality can be
>  implemented  in a firewall or any other IPv6 node.
> :
> :
>  Whereever possible, including the administrative network edge, RPF
>  check needs to be done.
> "
>
> I have following comments on the draft:
>
> 1.  Draft recommends to implement the stack in  the destination nodes but
> also says , Whereever possible,including the administrative network edge,
> RPF check needs to be done. This functionality can be  implemented  in a
> firewall or any other IPv6 node.
> please clarify.
>
> 2. What if current IPv6 node receives RH4 header?. How do we handle the RH4
> header in the current implementaions?
>
>
> Regards
> Sengottuvelan
>
>
>
>
>
> Vishwas Manral <vishwas.ietf@gmail.com> wrote:
> Hi,
>
> Based on feedback from the group, we have written a draft for a new
> routing header. The functionality is the same as the RH0. The draft
> will soon be posted to the IETF site.
>
> The main differences are:
>
> 1. Maximum up to 4 addresses in the header. (the number is based on
> the reply I got for the question about the usage scenarios in operator
> environments).
> 2. Only one header in each packet.
> 3. Firewall policy reccomendation.
> 4. RPF reccomendation.
>
> Please have a look and let us know your comments.
>
> Thanks,
> Vishwas
>
>
> Network Working Group V. Manral
> Internet-Draft M. Dutta
> Updates: 2460, 4294 IP Infusion Inc.
> (if approved)
> Intended status: Standards Track
> Expires: February 28, 2008
> August 28, 2007
>
>
> New IPv6 Type 4 Routing Header
> draft-manral-ipv6-rh4-00
>
> Status of this Memo
>
> By submitting this Internet-Draft, each author represents that any
> applicable patent or other IPR claims of which he or she is aware
> have been or will be disclosed, and any of which he or she becomes
> aware will be disclosed, in accordance with Section 6 of BCP 79.
>
> Internet-Drafts are working documents of the Internet Engineering
> Task Force (IETF), its areas, and its working groups. Note that
> other groups may also distribute working documents as Internet-
> Drafts.
>
> Internet-Drafts are draft documents valid for a maximum of six months
> and may be updated, replaced, or obsoleted by other documents at any
> time. It is inappropriate to use Internet-Drafts as reference
> material or to cite them other than as "work in progress."
>
> The list of current Internet-Drafts can be accessed at
> http://www.ietf.org/ietf/1id-abstracts.txt.
>
> The list of Internet-Draft Shadow Directories can be accessed at
> http://www.ietf.org/shadow.html.
>
> This Internet-Draft will expire on December 28, 2007.
>
> Copyright Notice
>
> Copyright (C) The IETF Trust (2007).
>
> Abstract
>
> The functionality provided by IPv6's Type 0 Routing Header can be
> exploited in order to achieve traffic amplification over a remote
> path for the purposes of generating denial-of-service traffic.
>
> This document updates the IPv6 specification to the use of a new
> IPv6 Type 4 Routing Header, in light of this security concern. This
> new header provides the same functionality of the Routing Header
> Type-0, while taking care of the major security concerns defined
> in the draft [draft-ietf-ipv6-deprecate-rh0-01].
>
>
>
> Manral Expires February 28, 2008 [Page 1]
>
> Internet-Draft New IPv6 Type 4 Routing Header June 2007
>
>
> Table of Contents
>
> 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
> 2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 4
> 3. Format of RH4 . . . . . . . . . . . . . . . . . . . . . . . . 4
> 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
> 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
> 6. Acknowlegements . . . . . . . . . . . . . . . . . . . . . . . . 7
> 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
> 6.1. Normative References . . . . . . . . . . . . . . . . . . . 7
> 6.2. Informative References . . . . . . . . . . . . . . . . . . 8
> Appendix A. Change History . . . . . . . . . . . . . . . . . . . . 8
> Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 9
> Intellectual Property and Copyright Statements . . . . . . . . . . 10
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Manral Expires February 28, 2008 [Page 2]
>
> Internet-Draft New IPv6 Type 4 Routing Header June 2007
>
>
> 1. Introduction
>
> [RFC2460] defines an IPv6 extension header called "Routing Header",
> identified by a Next Header value of 43 in the immediately preceding
> header. A particular Routing Header subtype denoted as "Type 0" is
> also defined. Type 0 Routing Headers are referred to as "RH0" in
> this document.
>
> 128-fold amplification of data traffic can result using the IPv6
> amplification attack as defined in [I-D.ietf-ipv6-deprecate-rh0-01].
> This attack is particularly serious in that it affects the entire
> path between the two exploited nodes, not only the nodes themselves
> or their local networks.
>
> The draft [I-D.ietf-ipv6-deprecate-rh0-01] deprecates the use of the
> RH0 header. However operators use and require the functionality provided
> by the RH0 header.
>
> This draft defines the Routing Header of Type-4, and referred to as "RH4"
> header. The RH4 header has format and functionality similar to the RH0
> header without having the major vulnerabilities of the "Routing Header".
>
> This document updates [RFC2460] and [RFC4294].
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Manral Expires February 28, 2008 [Page 3]
>
> Internet-Draft New IPv6 Type 4 Routing Header June 2007
>
>
> 2. Definitions
>
> RH4 in this document denotes the IPv6 Extension Header type 43
> ("Routing Header") variant 4 ("Type 4 Routing Header"), is a type of
> Routing header as defined in [RFC2460].
>
> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
> document are to be interpreted as described in [RFC2119].
>
>
> 3. Format of RH4
>
> The Type 4 Routing header has the following format (it is the same as
> the RH0 header except for the limit on the "Hdr Ext Len" field. Some
> additional restrictions and checks have been added):
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | Next Header | Hdr Ext Len | Routing Type=0| Segments Left |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | Reserved |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | |
> + +
> | |
> + Address[1] +
> | |
> + +
> | |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | |
> + +
> | |
> + Address[2] +
> | |
> + +
> | |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> . . .
> . . .
> . . .
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> | |
> + +
> | |
> + Address[n] +
> | |
> + +
> | |
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> Next Header 8-bit selector. Identifies the type of header
> immediately following the Routing header. Uses
> the same values as the IPv4 Protocol field
> [RFC-1700 et seq.].
>
> Hdr Ext Len 8-bit unsigned integer. Length of the Routing
> header in 8-octet units, not including the first
> 8 octets. For the Type 4 Routing header, Hdr
> Ext Len is equal to two times the number of
> addresses in the header. The maximum value of this
> field can be 8. That means a maximum of 4 addresses
> can be added to the Routing Header.
>
>
> Manral Expires February 28, 2008 [Page 4]
>
> Internet-Draft New IPv6 Type 4 Routing Header June 2007
>
>
>
> Routing Type 4.
>
> Segments Left 8-bit unsigned integer. Number of route
> segments remaining, i.e., number of explicitly
> listed intermediate nodes still to be visited
> before reaching the final destination.
>
> Reserved 32-bit reserved field. Initialized to zero for
> transmission; ignored on reception.
>
> Address[1..n] Vector of 128-bit addresses, numbered 1 to n. The
> maximum value of n is 4.
>
> Multicast addresses or Link Local Unicast address must not appear in a
> Routing header of Type 4, or in the IPv6 Destination Address field of
> a packet carrying a Routing header of Type 4.
>
> A Routing header is not examined or processed until it reaches the
> node identified in the Destination Address field of the IPv6 header.
> There can be at most one RH4 header in any packet. A packet with more
> than one RH4 header is discarded. This functionality can be implemented
> in a firewall or any other IPv6 node.
>
> In that node, dispatching on the Next Header field of the immediately
> preceding header causes the Routing header module to be invoked,
> which, in the case of Routing Type 4, performs the algorithm which is
> similar to the as specified in section 4.4 of [RFC2460]:
>
>
>
>
>
>
>
>
>
>
>
> Manral Expires February 28, 2008 [Page 5]
>
> Internet-Draft New IPv6 Type 4 Routing Header June 2007
>
>
> if Segments Left = 0 {
> proceed to process the next header in the packet, whose type is
> identified by the Next Header field in the Routing header
> }
> else if Hdr Ext Len is odd {
> send an ICMP Parameter Problem, Code 0, message to the Source
> Address, pointing to the Hdr Ext Len field, and discard the
> packet
> }
> else {
> compute n, the number of addresses in the Routing header, by
> dividing Hdr Ext Len by 2
>
> if Segments Left is greater than n or n is greater than 4 {
> send an ICMP Parameter Problem, Code 0, message to the Source
> Address, pointing to the Segments Left field, and discard the
> packet
> }
> else {
> decrement Segments Left by 1;
> compute i, the index of the next address to be visited in
> the address vector, by subtracting Segments Left from n
>
> if Address [i] or the IPv6 Destination Address is multicast
> or link local unicast address {
> discard the packet
> }
> else {
> Compare the addresses in the Routing Header to check that
> none of the address belong to the routers self address
>
> if overlapping address exist {
> discard the packet
> }
>
> swap the IPv6 Destination Address and Address[i]
>
> if the IPv6 Hop Limit is less than or equal to 1 {
> send an ICMP Time Exceeded -- Hop Limit Exceeded in
> Transit message to the Source Address and discard the
> packet
> }
> else {
> decrement the Hop Limit by 1
>
> resubmit the packet to the IPv6 module for transmission
> to the new destination
> }
> }
> }
> }
>
>
>
>
>
> Manral Expires February 28, 2008 [Page 6]
>
> Internet-Draft New IPv6 Type 4 Routing Header June 2007
>
>
> 4. Security Considerations
>
> The purpose of this document is to add a new type of Routing extension
> header of IPv6. RH0 has been shown to have undesirable security
> implications.
>
> Many of the attacks including the amplification attack cannot occur with
> the RH4 header. All the addresses in the RH4 header need to be checked with
> the firewall policy to make sure the firewall is able to trap packets meant
> for addresses in the firewall policy and take relevent action.
>
> Whereever possible, including the administrative network edge, RPF check
> needs to be done.
>
>
> 5. IANA Considerations
>
> The IANA registry "Internet Protocol Version 6 (IPv6) Parameters"
> should be updated to reflect that variant 4 of IPv6 header-type 43
> ("Routing Header") is added.
>
>
> 7. Acknowlegements
>
> This document benefits from the contributions of many IPV6 and V6OPS
> working group participants, including Chris Morrow, Tony Hain, Jinmei
> Tatuya and Brian Carpenter.
>
>
> 8. References
>
> 8.1. Normative References
>
> [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
> Requirement Levels", BCP 14, RFC 2119, March 1997.
>
>
>
> Manral Expires February 28, 2008 [Page 7]
>
> Internet-Draft New IPv6 Type 4 Routing Header June 2007
>
>
> [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
> (IPv6) Specification", RFC 2460, December 1998.
>
> [RFC4294] Loughney, J., "IPv6 Node Requirements", RFC 4294,
> April 2006.
>
> 8.2. Informative References
>
> [CanSecWest07]
> BIONDI, P. and A. EBALARD, "IPv6 Routing Header Security",
> CanSecWest Security Conference 2007, April 2007.
>
> http://www.secdev.org/conf/IPv6_RH_security-csw07.pdf
>
> [I-D.ietf-v6ops-security-overview]
> Davies, E., "IPv6 Transition/Co-existence Security
> Considerations", draft-ietf-v6ops-security-overview-06
> (work in progress), October 2006.
>
> [I-D.savola-ipv6-rh-ha-security]
> Savola, P., "Security of IPv6 Routing Header and Home
> Address Options", draft-savola-ipv6-rh-ha-security-02
> (work in progress), March 2002.
>
> [I-D.savola-ipv6-rh-hosts]
> Savola, P., "Note about Routing Header Processing on IPv6
> Hosts", draft-savola-ipv6-rh-hosts-00 (work in progress),
> February 2002.
>
> [RFC2827] Ferguson, P. and D. Senie, "Network Ingress Filtering:
> Defeating Denial of Service Attacks which employ IP Source
> Address Spoofing", BCP 38, RFC 2827, May 2000.
>
> [RFC3704] Baker, F. and P. Savola, "Ingress Filtering for Multihomed
> Networks", BCP 84, RFC 3704, March 2004.
>
> [RFC3775] Johnson, D., Perkins, C., and J. Arkko, "Mobility Support
> in IPv6", RFC 3775, June 2004.
>
>
> Appendix A. Change History
>
> This section to be removed prior to publication.
>
>
>
>
>
>
> Manral Expires February 28, 2008 [Page 8]
>
> Internet-Draft New IPv6 Type 4 Routing Header June 2007
>
>
> Authors' Addresses
>
> Vishwas Manral
> IP Infusion Inc,
> Bamankhola
> Bansgali
> Almora - Uttaranchal
> Phone: +91 98456 61911
> Email: vishwas@ipinfusion.com
>
>
> Manoj Dutta
> IP Infusion Inc,
> 125, S. Market Street,
> San Jose, CA
> Phone: 408 794 1500
> Email: manoj@ipinfusion.com
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Manral Expires February 28, 2008 [Page 9]
>
> Internet-Draft New IPv6 Type 4 Routing Header June 2007
>
>
> Full Copyright Statement
>
> Copyright (C) The IETF Trust (2007).
>
> This document is subject to the rights, licenses and restrictions
> contained in BCP 78, and except as set forth therein, the authors
> retain all their rights.
>
> This document and the information contained herein are provided on an
> "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
> OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
> THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
> OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
> THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
> WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
>
>
> Intellectual Property
>
> The IETF takes no position regarding the validity or scope of any
> Intellectual Property Rights or other rights that might be claimed to
> pertain to the implementation or use of the technology described in
> this document or the extent to which any license under such rights
> might or might not be available; nor does it represent that it has
> made any independent effort to identify any such rights. Information
> on the procedures with respect to rights in RFC documents can be
> found in BCP 78 and BCP 79.
>
> Copies of IPR disclosures made to the IETF Secretariat and any
> assurances of licenses to be made available, or the result of an
> attempt made to obtain a general license or permission for the use of
> such proprietary rights by implementers or users of this
> specification can be obtained from the IETF on-line IPR repository at
> http://www.ietf.org/ipr.
>
> The IETF invites any interested party to bring to its attention any
> copyrights, patents or patent applications, or other proprietary
> rights that may cover technology that may be required to implement
> this standard. Please address the information to the IETF at
> ietf-ipr@ietf.org.
>
>
> Acknowledgment
>
> Funding for the RFC Editor function is provided by the IETF
> Administrative Support Activity (IASA).
>
>
>
>
>
> Manral Expires February 28, 2008 [Page 10]
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests:
> https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>
>
>  ________________________________
> Pinpoint customers who are looking for what you sell.
>
>

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



From ipv6-bounces@ietf.org Wed Aug 29 21:37:09 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQYwI-00046D-81; Wed, 29 Aug 2007 21:35:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQYwC-00045n-Px
	for ipv6@ietf.org; Wed, 29 Aug 2007 21:35:14 -0400
Received: from e35.co.us.ibm.com ([32.97.110.153])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQYwB-00008t-He
	for ipv6@ietf.org; Wed, 29 Aug 2007 21:35:12 -0400
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com
	[9.17.195.106])
	by e35.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l7U1Z0hR030223
	for <ipv6@ietf.org>; Wed, 29 Aug 2007 21:35:00 -0400
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168])
	by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v8.5) with ESMTP id
	l7U1Z0cF412886 for <ipv6@ietf.org>; Wed, 29 Aug 2007 19:35:00 -0600
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1])
	by d03av02.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	l7U1Z04Z003412 for <ipv6@ietf.org>; Wed, 29 Aug 2007 19:35:00 -0600
Received: from cichlid.raleigh.ibm.com (wecm-9-67-159-36.wecm.ibm.com
	[9.67.159.36])
	by d03av02.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l7U1Ywqt003258
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 29 Aug 2007 19:34:59 -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 l7U1YuS1013622;
	Wed, 29 Aug 2007 21:34:57 -0400
Message-Id: <200708300134.l7U1YuS1013622@cichlid.raleigh.ibm.com>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
In-reply-to: <CA7D9B4A761066448304A6AFC09ABDA9015AD3F2@XCH-NE-1V2.ne.nos.boeing.com>
References: <200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com>
	<CA7D9B4A761066448304A6AFC09ABDA9015AD3F2@XCH-NE-1V2.ne.nos.boeing.com>
Comments: In-reply-to "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
	message dated "Wed, 29 Aug 2007 16:35:41 -0400."
Date: Wed, 29 Aug 2007 21:34:56 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: manoj@ipinfusion.com, IPv6 WG <ipv6@ietf.org>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> As always, there are workarounds like MPLS, if RH0 is eliminated. 

I don't get this at all.  RH is end to end (i.e., it's part of the IP
header, and presumably added by the originating device and processed
by the ultimate destination). MPLS, on the other hand, is an L2
technology and does not involve either the original sender or the
ultimate destination (normally).

I see them providing completely different services and NOT being
interchangable in any real sense.

Thomas

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



From ipv6-bounces@ietf.org Wed Aug 29 21:45:13 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQZ44-0004u7-KW; Wed, 29 Aug 2007 21:43:20 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQZ40-0004qv-Mi
	for ipv6@ietf.org; Wed, 29 Aug 2007 21:43:16 -0400
Received: from nz-out-0506.google.com ([64.233.162.226])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQZ40-0003hy-C5
	for ipv6@ietf.org; Wed, 29 Aug 2007 21:43:16 -0400
Received: by nz-out-0506.google.com with SMTP id n1so298991nzf
	for <ipv6@ietf.org>; Wed, 29 Aug 2007 18:43:15 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=cOqje85s+jmrfjhcTl+Sauht4Z2T+DwmtutHTGywruBkNnHrKC4gKTzL2pkESnfY7Y+f4hmyvMbwsEez5qy35ETEP6ceSbPZLWuvwaFmc4N98kVQNswkcmSfixSE60gOnTbfmFc2sRX2EGsNRUPBHK49ZSyM35UjkVD1HYOm/mE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=tZ8S1PYsGffbDWBtj13CgsVpHe32in38MWXz3Uyikvcz2899bS5uZS9AISAhcfDC3mUin58+CXJpV8huIApGEONQsvRZlWQtYJC9oezd1ugo/y5+JICQYhsxqlxFtblFJM7dNjt0zYsiLrkd80A2IHMAvKOzTcRGlpeRW4+dTGw=
Received: by 10.142.211.10 with SMTP id j10mr1639wfg.1188438195108;
	Wed, 29 Aug 2007 18:43:15 -0700 (PDT)
Received: by 10.142.84.8 with HTTP; Wed, 29 Aug 2007 18:43:15 -0700 (PDT)
Message-ID: <77ead0ec0708291843i35159afcma006ffd59be6a7b@mail.gmail.com>
Date: Thu, 30 Aug 2007 11:43:15 +1000
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Thomas Narten" <narten@us.ibm.com>
In-Reply-To: <200708300134.l7U1YuS1013622@cichlid.raleigh.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com>
	<CA7D9B4A761066448304A6AFC09ABDA9015AD3F2@XCH-NE-1V2.ne.nos.boeing.com>
	<200708300134.l7U1YuS1013622@cichlid.raleigh.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: manoj@ipinfusion.com, IPv6 WG <ipv6@ietf.org>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Thomas,

I guess Bert's comparison comes from the fact we can decide the path a
packet takes, just like we can for MPLS. So if the Path Computation
Element(PCE) calculated a path using CSPF that had loops(and ence
signalled using RSVP-TE), a similar situation could arise.

However I disagree with Bert here. The difference is that MPLS is
connection oriented in nature. The path setup element(RSVP-TE or
management for T-MPLS) and the data packets are different flow. It
would require to at least hack the head end router to get a simialr
functionality. Besides off-path attacks will be harder to make.

Thanks,
Vishwas

On 8/30/07, Thomas Narten <narten@us.ibm.com> wrote:
> > As always, there are workarounds like MPLS, if RH0 is eliminated.
>
> I don't get this at all.  RH is end to end (i.e., it's part of the IP
> header, and presumably added by the originating device and processed
> by the ultimate destination). MPLS, on the other hand, is an L2
> technology and does not involve either the original sender or the
> ultimate destination (normally).
>
> I see them providing completely different services and NOT being
> interchangable in any real sense.
>
> Thomas
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

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



From ipv6-bounces@ietf.org Wed Aug 29 21:48:35 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQZ7Q-0000Re-IK; Wed, 29 Aug 2007 21:46:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQZ7L-0000Ni-JG
	for ipv6@ietf.org; Wed, 29 Aug 2007 21:46:45 -0400
Received: from nz-out-0506.google.com ([64.233.162.237])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQZ7K-0001EO-E0
	for ipv6@ietf.org; Wed, 29 Aug 2007 21:46:43 -0400
Received: by nz-out-0506.google.com with SMTP id n1so299469nzf
	for <ipv6@ietf.org>; Wed, 29 Aug 2007 18:46:42 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=ZkrNedN4l4uiooUxZRtfWoRIKHp1Uq2iTy+iTV7sGDfp+rYVJO9JwXqp2qnRHLd1ood9yHONVywv7BkFKqIJc7q5jy6w0lfQjnO2uiwcBOchsaZB2d/mHBhV6BTbAdDF2n1usFXLCkJ8TWGymMyd18sLhBgzig+tYcj9SKAmjlg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=XmFA8kujxRJpYP6D3Kk0reMitRPIPiJml2fsBrvZHeyZzuI6Fy9KeYUq/4Rw6qBVrsHMfa5tYkMnllAXFec+pHPjLVIEXNq8ObHKZk63QxYuOIUaqJANWh/vjF2CGikPTQJy10N4M85fcSft70HslYxDMmz4Xic1st+rkH3x0S0=
Received: by 10.142.232.20 with SMTP id e20mr63865wfh.1188438401432;
	Wed, 29 Aug 2007 18:46:41 -0700 (PDT)
Received: by 10.142.84.8 with HTTP; Wed, 29 Aug 2007 18:46:41 -0700 (PDT)
Message-ID: <77ead0ec0708291846l672149e3xf174bd12f3392fab@mail.gmail.com>
Date: Thu, 30 Aug 2007 11:46:41 +1000
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "David Conrad" <drc@virtualized.org>
In-Reply-To: <1ED2DE65-EB5E-4B17-9125-E62E4C605BAA@virtualized.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com>
	<1ED2DE65-EB5E-4B17-9125-E62E4C605BAA@virtualized.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Cc: manoj@ipinfusion.com, IPv6 WG <ipv6@ietf.org>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Dave,

The text for processing an unknown Routing Header is attached from
RFC2460. It is another matter that a new header may not be able to
traverse the Firewall and such packets may be dropped.

   If, while processing a received packet, a node encounters a Routing
   header with an unrecognized Routing Type value, the required behavior
   of the node depends on the value of the Segments Left field, as
   follows:

      If Segments Left is zero, the node must ignore the Routing header
      and proceed to process the next header in the packet, whose type
      is identified by the Next Header field in the Routing header.

      If Segments Left is non-zero, the node must discard the packet and
      send an ICMP Parameter Problem, Code 0, message to the packet's
      Source Address, pointing to the unrecognized Routing Type.

   If, after processing a Routing header of a received packet, an
   intermediate node determines that the packet is to be forwarded onto
   a link whose link MTU is less than the size of the packet, the node
   must discard the packet and send an ICMP Packet Too Big message to
   the packet's Source Address.

Thanks,
Vishwas

On 8/30/07, David Conrad <drc@virtualized.org> wrote:
> Hi,
>
> On Aug 29, 2007, at 1:04 PM, Brian E Carpenter wrote:
> > On 2007-08-30 02:08, Thomas Narten wrote:
> >> Can we please _first_ identify a user/customer for a proposed RH,
> > I agree. A use case draft should be the first step.
>
> I'm not sure it matters since:
>
> > Incidentally, RFC 2460 is clear that unknown headers should cause the
> > packet to be dropped, so the transition strategy is tricky in any
> > case.
>
> Water under the bridge and all that, but I'm curious: what was the
> rationale for this?  It would seem to imply it is impossible to do
> incremental deployment of new headers, and thus essentially freezes
> routing header development for the lifetime of IPv6.
>
> Am I misunderstanding?
>
> Thanks,
> -drc
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

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



From ipv6-bounces@ietf.org Wed Aug 29 22:10:45 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQZSa-0003sm-7J; Wed, 29 Aug 2007 22:08:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQZSX-0003sd-9e
	for ipv6@ietf.org; Wed, 29 Aug 2007 22:08:37 -0400
Received: from vgateway.libertyrms.info ([207.219.45.62]
	helo=mail.libertyrms.com) by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IQZSV-0002ec-W2
	for ipv6@ietf.org; Wed, 29 Aug 2007 22:08:37 -0400
Received: from vgateway.int.libertyrms.com ([10.1.3.254]
	helo=look.libertyrms.com)
	by mail.libertyrms.com with esmtp (Exim 4.22)
	id 1IQZSM-0003Pi-N3; Wed, 29 Aug 2007 22:08:26 -0400
Received: from 74.122.168.81 (SquirrelMail authenticated user briand)
	by look.libertyrms.com with HTTP;
	Wed, 29 Aug 2007 22:08:26 -0400 (EDT)
Message-ID: <60478.74.122.168.81.1188439706.squirrel@look.libertyrms.com>
In-Reply-To: <46D5D525.30005@gmail.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<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>
	<471515FC-E1E1-4C83-99AA-A9821E0C2FF5@muada.com> <! !
	63886.74.122.168.81.1188025388.squirrel@look.libertyrms.com>
	<200708291423.l7TENQZ8000329@cichlid.raleigh.ibm.com>
	<79358CCF-0A4B-424D-BA32-14099B3EF257@muada.com>
	<61722.74.122.168.81.1188400653.squirrel@look.libertyrms. com>
	<46D5D525.30005@gmail.com>
Date: Wed, 29 Aug 2007 22:08:26 -0400 (EDT)
From: briand@ca.afilias.info
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
User-Agent: SquirrelMail/1.4.9a
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-SA-Exim-Mail-From: briand@ca.afilias.info
X-SA-Exim-Scanned: No; SAEximRunCond expanded to false
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ded6070f7eed56e10c4f4d0d5043d9c7
Cc: Thomas Narten <narten@us.ibm.com>,
	Iljitsch van Beijnum <iljitsch@muada.com>,
	IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: History of autoconfig RFCs and siblings, please?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> Brian D,
>
> You seem to be assuming that PI will be the dominant mode.

Not at all. I am assuming that prefixes in the DFZ won't be deaggregated
to any significant degree. All PA are aggregated, in theory at least,
under PI prefixes.

I am in fact only assuming PI prefixes as numerous as ASNs.
And that more multihoming for true "end-users" will be enabled by
the ability to have duplicative PA blocks big enough to cover end sites
N times over.

I am assuming that the *vast* majority of networks will have PA native,
or ULA-* native and 1:1 NAT onto PA, or "unannounced" PI internally
with 1:1 NAT facing multiple upstream PA blocks.

> This seems very unlikely, since the vast majority of users
> (i.e. SOHO) have no interest in what their IP address is and
> no motivation to pay extra for PI.

(I don't disagree on the latter, making this moot. And you mis-speak
for me on what I assume.)

> We have no possible
> difficulty in supporting a few million PI prefixes in the
> /48 or /56 world currently planned (apart from BGP4 blowing
> up, of course, but that's being discussed elsewhere).

I disagree strongly.

Yes, I'm aware, and I'm participating in those discussions.

The size of the autoconf prefix is out of scope for *those* venues.

However, it *directly* impacts assignments in those areas.

Which is why I raised the question, here.

Whether autoconf uses /64 or /68 or /80, has direct implications on
the minimum prefix assignable to an end-user should be, and what the
typical minimum minimum PI block size should be.

A "few million" PI prefixes is not actually something we should plan for,
even if it fits into the range of space between /3 and /32 (as in,
2000::/3, and /32 LIR PI assignments.)

Here's why:

On the biggest iron currently deployed in most networks, the size
of the DFZ in IPv6 that can *reasonably* supported has an upper bound
dictated by deployed TCAM size and per-prefix TCAM allocation needed.

These days, for example, on an IPv6-*only* Cisco 7600 with 3BXL, will
only hold a theoretical maximum of 119,000 prefixes. Bigger iron may
support double that, but again, only as IPv6-ONLY. When you add IPv4
onto the same platform, the huge IPv4 DFZ  eats most of the capacity
for IPv6 prefixes. Most providers will need to have dual-stack for
a considerable period of time (3-5 years minimum, IMHO.)

And on that basis, how many end-user assignments fit into PI prefixes
which are sized sufficiently to grow vertically inside reserved space,
rather than multiply and bloat the DFZ, is very important.

Too big an end assignment, and it results in a squeeze play, where either
too few PI blocks can be reserved to go around (fairly), or too many small
PI blocks end up being used.

Adding 16 more bits to the range between PI block size and end-user
assignment prefix length, and the squeeze effect is relaxed considerably.

Making really big assignments (say /20 to /42) to handle end-assignments
of /80, gives a much longer life span to each PI block, and keeps the
PI per ASN down to a nice low value of "1".

Brian Dickson

> Regards
>     Brian Carpenter
>
> On 2007-08-30 03:17, briand@ca.afilias.info wrote:
>> Iljitsch wrote:
>>> On 29-aug-2007, at 16:23, Thomas Narten wrote:
>>>>> (I suppose it's a bit late in the game to go back to MAC-48 as II?)
>>>> Yes. The difficulty is figuring out how to move to something different
>>>> in a backwards-compatable way. I.e., we'd need a transition strategy.
>>> But what would be the point of doing that now?
>>
>> The point, which I have avoided making until now, is that II has direct
>> impact on the available range of assignments by RIRs to LIRs, for PI
>> blocks,
>> that also allow for very long timescale predictive assignments.
>>
>> Basically, the minimum prefix size * number of assignments * LIRs,
>> when projected over a timeframe of decades, while preserving a global
>> DFZ consisting of one PI block per LIR, has a problem fitting into the
>> number of bits per RIR.
>>
>> Right now, RIRs are reserving only an additional 2 bits per LIR
>> assignment,
>> for "growth". Alternative allocation policies (bisection) don't
>> guarantee
>> the ability to assign arbitrarily large blocks indefinitely - while that
>> is in fact the long-term requirement. Block sizes *should* increase over
>> time, even as the frequency of their assignment decreases.
>>
>> What works best is, a best-fit approach, where any organization gets way
>> more space than they need, sized according to their own best guess as to
>> long-term growth *potential*.
>>
>> Then, reserve even more space for each, in a consistent manner.
>>
>> Take all these requests, and fill them in an optimized space-packing
>> manner.
>>
>> At some point, growth requests get filled via "growing" the assignment
>> for
>> a given LIR into its reserved space.
>>
>> And, long-term periodic reviews of those growth patterns may result in
>> bisecting *some* of those reserved blocks to make more space available
>> for similar assignments.
>>
>> This can be shown to meet the requirements of individual LIRs to within
>> a few orders of magnitude of their long-term projections (pretty good),
>> and at the same time, optimize the packing efficiency, meaning the truly
>> free space will not be fragmented except to the degree absolutely
>> necessary
>> for the existing assignments.
>>
>> This means that new assignments have the largest possible potential
>> prefix
>> size available, compared to other allocation methods. This can even be
>> demonstrated or possibly even proven mathematically, by modeling the
>> problem space.
>>
>>> The fact that we have so many local bits in the IPv6 address is our
>>> insurance policy against address policy screwups because a single /64
>>> is enough to run a network of arbitrary size if you forego stateless
>>> autoconfig.
>>
>> The same would be true of /80, which is what MAC-48 would result in, for
>> minimum prefix size for autoconf (and thus the standard end-user
>> assignment
>> size).
>>
>> Of the 16 bits reclaimed via this change, I would propose to the RIRs,
>> that 4 bits be added to initial allocations, 4 bits to reservations
>> above
>> the initial allocations (for long-term growth), and the other 8 bits add
>> to the total space available for the RIRs to allocate to LIRs - by
>> adjusting
>> the minimum and initial allocation sizes by 8 bits.
>>
>> The numbers (4 bits and 8 bits) are not accidental - they are one nibble
>> in size, which matches up with the boundaries for reverse address
>> lookups,
>> via ip6.arpa - which uses nibbles.
>>
>> It seems to me, that while it would be an uphill battle, the main two
>> issues
>> are transition and compatibity, and inertia (e.g. deployed code and
>> networks.)
>>
>> The overall benefits to address space assignment, IMHO, outweigh that
>> cost,
>> especially when considering the long-term health of the DFZ and the cost
>> to member organizations when having to do expensive upgrades to their
>> entire infrastructure to support bloat in the DFZ.
>>
>> Brian
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
>



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



From ipv6-bounces@ietf.org Thu Aug 30 03:25:38 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQeMx-0002Sc-CW; Thu, 30 Aug 2007 03:23:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQeMv-0002SX-SJ
	for ipv6@ietf.org; Thu, 30 Aug 2007 03:23:09 -0400
Received: from mint.apnic.net ([202.12.29.58])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQeMu-0001VW-5e
	for ipv6@ietf.org; Thu, 30 Aug 2007 03:23:09 -0400
Received: from [203.10.60.13] (dhcp13.potaroo.net [203.10.60.13])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mint.apnic.net (Postfix) with ESMTP id 989BED5F38;
	Thu, 30 Aug 2007 17:23:06 +1000 (EST)
Message-ID: <46D670E0.7090308@apnic.net>
Date: Thu, 30 Aug 2007 17:25:20 +1000
From: Geoff Huston <gih@apnic.net>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com>
In-Reply-To: <46D5D148.6080701@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Cc: Thomas Narten <narten@us.ibm.com>, IPv6 WG <ipv6@ietf.org>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Brian E Carpenter wrote:
> 
> Incidentally, RFC 2460 is clear that unknown headers should cause the
> packet to be dropped, so the transition strategy is tricky in any case.
> 
>    If, as a result of processing a header, a node is required to proceed
>    to the next header but the Next Header value in the current header is
>    unrecognized by the node, it should discard the packet and send an
>    ICMP Parameter Problem message to the source of the packet, with an
>    ICMP Code value of 1 ("unrecognized Next Header type encountered")
>    and the ICMP Pointer field containing the offset of the unrecognized
>    value within the original packet.

So are you _really_ sure you want to drop RH0 from the IPv6 protocol 
spec, given that the practicalities of a general use 'replacement' 
header is going to present some fascinating transition issues?


Geoff





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



From ipv6-bounces@ietf.org Thu Aug 30 03:33:15 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQeUw-0001tN-0U; Thu, 30 Aug 2007 03:31:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQeUu-0001t8-Hu
	for ipv6@ietf.org; Thu, 30 Aug 2007 03:31:24 -0400
Received: from [2001:6f8:387:2057:ea05:e98a:6f83:d890] (helo=moog.chdir.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQeUt-0001iT-Qs
	for ipv6@ietf.org; Thu, 30 Aug 2007 03:31:24 -0400
Received: from aputeaux-152-1-28-86.w82-120.abo.wanadoo.fr ([82.120.90.86]
	helo=localhost.localdomain)
	by moog.chdir.org with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.63) (envelope-from <arno@natisbad.org>)
	id 1IQeUn-00022m-GW; Thu, 30 Aug 2007 09:31:17 +0200
From: arno@natisbad.org (Arnaud Ebalard)
To: Dow Street <dow.street@linquest.com>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com>
	<1ED2DE65-EB5E-4B17-9125-E62E4C605BAA@virtualized.org>
	<46D5D776.9030603@gmail.com> <87ejhmqaag.fsf@natisbad.org>
	<8CF7F46A-8231-44CF-B265-B46F38072E0D@linquest.com>
X-GnuPG-Key: 0x047A5026
X-Hashcash: 1:20:070830:dow.street@linquest.com::ehOCWKR8SHtURAfE:000000000000000000000000000000000000000XD8
X-Hashcash: 1:20:070830:ipv6@ietf.org::dXB9rFvWkUizInyS:00004l4/
X-Hashcash: 1:20:070830:brian.e.carpenter@gmail.com::25UMVGYWU2a/2y57:00000000000000000000000000000000006pm4
Date: Thu, 30 Aug 2007 09:31:15 +0200
In-Reply-To: <8CF7F46A-8231-44CF-B265-B46F38072E0D@linquest.com> (Dow Street's
	message of "Wed, 29 Aug 2007 16:33:49 -0700")
Message-ID: <87sl6132d8.fsf@natisbad.org>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.95 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Cc: IPv6 WG <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi,

Dow Street <dow.street@linquest.com> writes:

> On Aug 29, 2007, at 2:51 PM, Arnaud Ebalard wrote:
>
>> Let's let people that still argue in favor of source-routing prove
>>
>> - there is a need
>
> I see advertisement of specifics by multi-homed sites as a indication
> that they desire more control over how their traffic is routed.  If
> the architecture does not address that problem directly, I think it
> is likely to manifest itself indirectly at some other place (e.g. the
> RIB growth problem).

Operators won't help, for valid reasons, all the more when there are
protocols that have already shown great results (sorry for using MIPv6
as an example again) without even modifying the routing in the core.

The underlying problem is always the same: id and locator roles of IPv6
addresses. IMHO, if the people that specifically work on multi-homing
have a clean and safe solution that requires some mandatory extension in
IPv6 specification, IPv6 WG will be happy to consider that. Now, adding
RH4 in the spec for the fun of it in the hope that it will serve some
purpose in the future simply seems weird.

>> - there is a need at L3
>
> IP seems to be the right place in the stack to deal with issues of
> path selection and packet delivery.  Do you see a better place in a
> different layer?

If you need something working at a large scale, which creates a
_precise_ rationale to have that included at L3, it is the place and
SHOULD be put there. 

Now, if there is only a limited rationale, it COULD be put there but as
an external feature (i.e. outside 2460), to be deployed by people that
have the need. 

In other cases, their is no need for that to be at L3.

>> - there is a need at L3 to blindly process their pkts
>
> Can you clarify what you mean by "blindly"? 

What 2460 specifies for routers regarding RH0 processing and what
vendors had implemented (before the deprecation). I don't consider the
amplification here (i.e. even a limited version of RH0 with only one
address in it, processed by default by routers, fits my description).

> As others have stated, including support for source routing in IPv6
> does not necessarily mean that every IPv6 node in the network needs to
> be configured as a viable (intermediate) source routing destination.

I hope so. 

> I agree that a goal of the new draft should be to minimize the cost to
> uninterested nodes.

Minimizing the cost will be done by answering the question: "Is that
feature so useful that it should be in IPv6 specification?". i.e. need
vs. cost.

>> - there is a need at L3 to blindly process their pkts and it's safe
>
> Also, please clarify "safe".  Is this a question on the acceptable
> range of traffic (trend) variability? 

It's a question of all threats that make the internet less safe and add
useless code in stacks, increasing the attack surface. 

Less than 1 year ago, you could kill the routers of a well-known vendor
on the IPv6 internet with one single RH0 packet (per router),
i.e. collapse the core network in few seconds/packets.

One can blame the vendor but it will object with 2460-compliance ...

> Of the issues raised at csw07,
> which do you think are unable to be mitigated through a revised RH
> specification?  

None. They can all be mitigated. Best proof is RH2 (and associated
conditions of use) ...

> In your opinion, which issues are currently unmitigated in the RH4
> draft? 

... because MIPv6 designers have first defined a use, have then defined
the associated mechanism with security in mind (Do no harm to the
existing internet). 

Sorry, but i won't answer your question on non-mitigated issues of RH4
till its use is clarified and i see an interest (i.e. potential users).

Regards,

a+

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



From ipv6-bounces@ietf.org Thu Aug 30 04:49:14 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQfgB-0005IR-FW; Thu, 30 Aug 2007 04:47:07 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQfgA-0005ID-8t
	for ipv6@ietf.org; Thu, 30 Aug 2007 04:47:06 -0400
Received: from postfix.iai.uni-bonn.de ([131.220.8.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQfg8-0003aa-Pn
	for ipv6@ietf.org; Thu, 30 Aug 2007 04:47:06 -0400
X-IAI-Env-From: <ignatios@cello.cs.uni-bonn.de> : [131.220.4.211]
Received: from theory.cs.uni-bonn.de (theory.cs.uni-bonn.de [131.220.4.211])
	by postfix.iai.uni-bonn.de (Postfix) with ESMTP id 287A45C837
	for <ipv6@ietf.org>; Thu, 30 Aug 2007 10:46:59 +0200 (MEST)
	(envelope-from ignatios@cello.cs.uni-bonn.de)
	(envelope-to ipv6@ietf.org) (1)
	(internal use: ta=0, tu=1, te=0, am=-, au=-)
Received: from cello.cs.uni-bonn.de (cello.cs.uni-bonn.de [131.220.4.178])
	by theory.cs.uni-bonn.de (8.12.9/8.12.9) with SMTP id l7U8kxUo003461
	for <ipv6@ietf.org>; Thu, 30 Aug 2007 10:46:59 +0200 (MEST)
Received: (from ignatios@cello.cs.uni-bonn.de)
	by cello.cs.uni-bonn.de (mini_sendmail/1.3.2 21nov2002 nb4 7oct2003);
	Thu, 30 Aug 2007 10:46:59 CEST (sender ignatios@cello.cs.uni-bonn.de)
Date: Thu, 30 Aug 2007 10:46:58 +0200
From: Ignatios Souvatzis <ignatios@cs.uni-bonn.de>
To: IPv6 WG <ipv6@ietf.org>
Message-ID: <20070830084658.GA241@cs.uni-bonn.de>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46D5D148.6080701@gmail.com>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Thu, Aug 30, 2007 at 08:04:24AM +1200, Brian E Carpenter wrote:
> On 2007-08-30 02:08, Thomas Narten wrote:
> >Sorry to interrupt, but I'd suggest that working on a new RH design is
> >mostly a waste of time at this point.
> >
> >Can we please _first_ identify a user/customer for a proposed RH, 
> 
> I agree. A use case draft should be the first step.
> 
> Incidentally, RFC 2460 is clear that unknown headers should cause the
> packet to be dropped, so the transition strategy is tricky in any case.
> 
>    If, as a result of processing a header, a node is required to proceed
>    to the next header but the Next Header value in the current header is
>    unrecognized by the node, it should discard the packet and send an
>    ICMP Parameter Problem message to the source of the packet, with an
>    ICMP Code value of 1 ("unrecognized Next Header type encountered")
>    and the ICMP Pointer field containing the offset of the unrecognized
>    value within the original packet.

Yes, but this would only be the node addressed by the IPv6 header - or 
do I read this wrongly? So the core of the network is not affected either
way (unless explicit filtering is implemented somewhere), and only
routers of end networks that wish to participate in, say, a future RH4
routing would need to upgrade the software.

	-is

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



From ipv6-bounces@ietf.org Thu Aug 30 06:02:30 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQgp2-0002kN-Uv; Thu, 30 Aug 2007 06:00:20 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQgp1-0002kG-81
	for ipv6@ietf.org; Thu, 30 Aug 2007 06:00:19 -0400
Received: from levanto.mail.adnap.net.au ([203.6.132.83])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQgp0-0001Dt-B9
	for ipv6@ietf.org; Thu, 30 Aug 2007 06:00:18 -0400
Received: from [122.49.179.97] (helo=mail.nosense.org)
	by levanto.mail.adnap.net.au with esmtp (Exim 4.63 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1IQgol-0004sQ-GN; Thu, 30 Aug 2007 19:30:03 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id BE64FFC81;
	Thu, 30 Aug 2007 19:29:59 +0930 (CST)
Date: Thu, 30 Aug 2007 19:29:59 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: briand@ca.afilias.info
Message-Id: <20070830192959.6306bc73.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <60478.74.122.168.81.1188439706.squirrel@look.libertyrms.com>
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>
	<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>
	<471515FC-E1E1-4C83-99AA-A9821E0C2FF5@muada.com> <! !
	63886.74.122.168.81.1188025388.squirrel@look.libertyrms.com>
	<200708291423.l7TENQZ8000329@cichlid.raleigh.ibm.com>
	<79358CCF-0A4B-424D-BA32-14099B3EF257@muada.com>
	<61722.74.122.168.81.1188400653.squirrel@look.libertyrms. com>
	<46D5D525.30005@gmail.com>
	<60478.74.122.168.81.1188439706.squirrel@look.libertyrms.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: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: Thomas Narten <narten@us.ibm.com>, IETF,
	Iljitsch van Beijnum <iljitsch@muada.com>, Mailing List <ipv6@ietf.org>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: History of autoconfig RFCs and siblings, please?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Wed, 29 Aug 2007 22:08:26 -0400 (EDT)
briand@ca.afilias.info wrote:

> > Brian D,
> >
<snip>
> 
> These days, for example, on an IPv6-*only* Cisco 7600 with 3BXL, will
> only hold a theoretical maximum of 119,000 prefixes. Bigger iron may
> support double that, but again, only as IPv6-ONLY. When you add IPv4
> onto the same platform, the huge IPv4 DFZ  eats most of the capacity
> for IPv6 prefixes. Most providers will need to have dual-stack for
> a considerable period of time (3-5 years minimum, IMHO.)

I'm inclined to believe that dual-stack provider networks are going to
be relatively rare, and may not exist at all. I think it'll either be
IPv6 over MPLS (in one way or another e.g. 6PE or native IPv6 over
MPLS), or Softwires, where IPv6 is encapsulated inside IPv4 (or
vise-versa) at the edges, and tunnelled across a native IPv4 or IPv6
backbone to the egress device. I think softwires is also likely to be
the better alternative for enterprise networks as well, although the
parallel introduction of IPv6 and BGP may initially be a bit
intimidating for them. Assuming a Softwires IPv4 over a native IPv6
network, one method of avoiding having to implement BGP could be to
encode IPv4 prefix information below a reserved IPv6 prefix, and then
have the normal IPv6 IGP carry that information between the egress and
ingress nodes.

Both of these techniques push the "heavy lifting" of matching a
destination layer 3 addresses against many and specific prefixes to the
edge of the network. Once the problem can be pushed to the edge of the
network, it can typically be scaled more easily. The TCAM limit in
your high end internal devices then becomes a limit on how many
forwarding devices you have in your network, not how many prefixes the
network can forward for.

Regards,
Mark.

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



From ipv6-bounces@ietf.org Thu Aug 30 07:42:00 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQiN6-0004SF-CJ; Thu, 30 Aug 2007 07:39:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQiN4-0004Ju-PF
	for ipv6@ietf.org; Thu, 30 Aug 2007 07:39:34 -0400
Received: from nz-out-0506.google.com ([64.233.162.239])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQiN3-0000CD-J0
	for ipv6@ietf.org; Thu, 30 Aug 2007 07:39:34 -0400
Received: by nz-out-0506.google.com with SMTP id n1so358922nzf
	for <ipv6@ietf.org>; Thu, 30 Aug 2007 04:39:33 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=Cf2GRLSQBmlhvsjBSzpJZtXkdJ7TQrmkxue2kBZBaXeDFXvPeS9DqScm2xineBw3L1dEeLgClQMKyrbC3MWWbjcvI9+b2PPCdK2dukNWJjwNfuFkmJEJxlAlEgZHEZo3QMRgMUmdnPEmF+jCnXX6etpLy2A4GWGI7hkTB5pnihc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=PjozwB87dBYr1H9B1jVxMUPa3gjlxK+V8sQt4oHpekR8hwLEPvAWnPeVXuU0gkRtKUNNpHwXgfUROWhFagEcHNyDTy70/nfjuq3SbkGfzLyFzu5zUTZWtfdvxOxthXANoYJK2STB0RPZpOejOTVl/7qcYMmz3g0IhZhatFKt4Jo=
Received: by 10.143.42.3 with SMTP id u3mr17550wfj.1188473972426;
	Thu, 30 Aug 2007 04:39:32 -0700 (PDT)
Received: by 10.142.84.8 with HTTP; Thu, 30 Aug 2007 04:39:32 -0700 (PDT)
Message-ID: <77ead0ec0708300439p43028294pdbac0bdf62f9246e@mail.gmail.com>
Date: Thu, 30 Aug 2007 21:39:32 +1000
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Ignatios Souvatzis" <ignatios@cs.uni-bonn.de>
In-Reply-To: <20070830084658.GA241@cs.uni-bonn.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com> <20070830084658.GA241@cs.uni-bonn.de>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Ignatious,

Quoting the RFC2460:

   With one exception, of Hop-by-hop extension headers are not examined
   or processed by any node along a packet's delivery path, until the packet
   reaches the node (or each of the set of nodes, in the case of multicast)
   identified in the Destination Address field of the IPv6 header.

So in a way you are right, but again it we may want to test the
routing path from any router in the network to any other router in the
network.

Thanks,
Vishwas

On 8/30/07, Ignatios Souvatzis <ignatios@cs.uni-bonn.de> wrote:
> On Thu, Aug 30, 2007 at 08:04:24AM +1200, Brian E Carpenter wrote:
> > On 2007-08-30 02:08, Thomas Narten wrote:
> > >Sorry to interrupt, but I'd suggest that working on a new RH design is
> > >mostly a waste of time at this point.
> > >
> > >Can we please _first_ identify a user/customer for a proposed RH,
> >
> > I agree. A use case draft should be the first step.
> >
> > Incidentally, RFC 2460 is clear that unknown headers should cause the
> > packet to be dropped, so the transition strategy is tricky in any case.
> >
> >    If, as a result of processing a header, a node is required to proceed
> >    to the next header but the Next Header value in the current header is
> >    unrecognized by the node, it should discard the packet and send an
> >    ICMP Parameter Problem message to the source of the packet, with an
> >    ICMP Code value of 1 ("unrecognized Next Header type encountered")
> >    and the ICMP Pointer field containing the offset of the unrecognized
> >    value within the original packet.
>
> Yes, but this would only be the node addressed by the IPv6 header - or
> do I read this wrongly? So the core of the network is not affected either
> way (unless explicit filtering is implemented somewhere), and only
> routers of end networks that wish to participate in, say, a future RH4
> routing would need to upgrade the software.
>
>         -is

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



From ipv6-bounces@ietf.org Thu Aug 30 07:50:00 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQiVM-0004Oh-M4; Thu, 30 Aug 2007 07:48:08 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQiVK-0004Oc-Na
	for ipv6@ietf.org; Thu, 30 Aug 2007 07:48:06 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQiVJ-0000Rq-5d
	for ipv6@ietf.org; Thu, 30 Aug 2007 07:48:06 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id E07B6198662;
	Thu, 30 Aug 2007 14:48:03 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 9AB9019865A;
	Thu, 30 Aug 2007 14:48:03 +0300 (EEST)
Message-ID: <46D6AE73.3030303@piuha.net>
Date: Thu, 30 Aug 2007 14:48:03 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.13 (X11/20070824)
MIME-Version: 1.0
To: Christopher Morrow <christopher.morrow@gmail.com>
References: <Pine.GSO.4.20.0708271348200.6917-100000@meno.corp.us.uu.net>	<46D32BB2.1030908@ericsson.com>	<20070828090414.GA67414@walton.maths.tcd.ie>
	<75cb24520708282045g475f32ecic7284a083cebcd3d@mail.gmail.com>
In-Reply-To: <75cb24520708282045g475f32ecic7284a083cebcd3d@mail.gmail.com>
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: 25620135586de10c627e3628c432b04a
Cc: ipv6@ietf.org
Subject: Re: New Consensus call on RH0 Deprecation
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Chris,

> Yup, and someone/no-one noted this as a real concern with ipv6 RH0,
> everyone focused on the least interesting problem and decided to
> shutdown RHO and excise it from the protocol... a blatant knee jerk
> reaction. It's interesting to me that this blatant knee jerk reaction
> is getting a base protocol level change

The RH0 case is not one of the big issues facing the Internet.
As bugs and changes go, its a very small one.

This does not imply that we can forget it and do nothing. The
IETF is responsible for its specifications much the same way
as vendors are responsible for their products. When there's
a bug or a security vulnerability in our specifications, it is
our duty to take notice and take appropriate. Perhaps we
can debate what that action should be, but it most certainly
should include documentation of the issue, and in some cases
modification of the spec in question.

I realize that in many cases what has happened is that the
RFC stays unchanged, and a body of knowledge is developed
outside the RFCs (code in common implementations; papers
in conferences; discussions on lists; word of mouth) about
what should be done. I do not think this mode of operation
is appropriate, or at least not appropriate in all cases. We
owe it to the consumers of our specifications -- implementors,
for instance -- that we keep them up to date and that they
contain all the information required to implement and use
the feature in question.

I respect your opinion that this is a knee jerk reaction,
but disagree with that characterization, and so did most
of the people who were involved in the discussion. On
a personal note, I find it amusing that a couple of months
ago we had to calm people down and assure that this
is just another bug and we'd deal with it the way we deal
any other issues. Now we're using same words to argue
that we're not giving in to hysteria...

> yet locator/id split isn't.
> It's interesting that folks feel in this instance ipv6 is 'less used
> and less critical' and thus able to be changed where in the locator/id
> split discussion that argument was not acceptable.
>   

I share your frustration, there is nothing that I would like
better than getting an identifier-locator separation in
our stack. (Or having one there already, but then you have
to lend your time machine to us.)

However, the way to get there is to not block bug fixes
or other ongoing work. What we need instead is (a) work
towards identifier-locator solutions that are far enough
in the design that we can actually adopt them and (b) people
who start to use these things in their networks. As you
know, there is ongoing work in the IETF, e.g., in HIP WG/RG
and the RRG. The former has more issues in class b, the
latter has more issues in category a. I'm very hopeful that
we'll get a positive end result, but we are not there yet.

The criteria for adopting either a bug fix or a new feature
is the same that it has always been:

- We have a solution ready for adoption (no missing parts,
  does not cause major security issues)
- We understand how it can be deployed and how it affects
  backwards compatibility.
- We have agreement on adopting it.

So - I would suggest that we get to work on this, too.

Jari


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



From ipv6-bounces@ietf.org Thu Aug 30 07:52:25 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQiXi-0006yH-HB; Thu, 30 Aug 2007 07:50:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQiXg-0006xg-HO
	for ipv6@ietf.org; Thu, 30 Aug 2007 07:50:32 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQiXf-0000Yj-4s
	for ipv6@ietf.org; Thu, 30 Aug 2007 07:50:32 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 8718B198664;
	Thu, 30 Aug 2007 14:50:30 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 4591C19865A;
	Thu, 30 Aug 2007 14:50:30 +0300 (EEST)
Message-ID: <46D6AF06.3020805@piuha.net>
Date: Thu, 30 Aug 2007 14:50:30 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.13 (X11/20070824)
MIME-Version: 1.0
To: Geoff Huston <gih@apnic.net>, 
	Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>	<46D5D148.6080701@gmail.com>
	<46D670E0.7090308@apnic.net>
In-Reply-To: <46D670E0.7090308@apnic.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Cc: Thomas Narten <narten@us.ibm.com>, IPv6 WG <ipv6@ietf.org>
Subject: Deploying a new RH (Was: Re: New Routing Header!!!)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


> So are you _really_ sure you want to drop RH0 from the IPv6 protocol
> spec, given that the practicalities of a general use 'replacement'
> header is going to present some fascinating transition issues?

I suspect code changes are necessary in any case, completely
independent of whether RH0 or RHx is going to be employed
or what the IETF does.

First, given the possibility for amplification, implementations
would be well advised to at least add some checks and limits
on RH0, even if it would not be deprecated. Second, a number
of implementations already have turned the feature off, which
obviously means that we cannot expect a random node in the
Internet to always respect anyone's request to perform a RH0
operation.

But, at the end of the day, I'm not sure the above is a big
problem.

Please remember that RH works in an end-to-end fashion;
only the source and current destination of the packet needs to
process it. Not routers in between.

There have been examples where new RH types
have been specified, implemented, and used. In Mobile IPv6,
for instance, RH2 is implemented by the participants. This
is easy, as only the participants need to implement it,
and RH2 is a MUST-to-implement in the specifications
for any of the participant nodes in Mobile IPv6.

More generally, if one wants to provide a new feature based
on routing header, what we need is

- Implementation in nodes that want to use RHx for something.
  This should be easy.

- Implementation in other, consenting nodes that appear in
  a non-final destination of the routing header.

  This is not needed in all cases, e.g., not in the Mobile Ipv6
  case.

The second item is harder, but I'm not sure its an unreasonable
requirement. After all, as a manager of a network you probably
want to be in control of where re-forwarding to a new address
is used. And you probably are in control of that, already...

Jari



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



From ipv6-bounces@ietf.org Thu Aug 30 08:02:56 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQihr-0003ym-LN; Thu, 30 Aug 2007 08:01:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQihp-0003x0-6r
	for ipv6@ietf.org; Thu, 30 Aug 2007 08:01:01 -0400
Received: from postfix.iai.uni-bonn.de ([131.220.8.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQihn-0000n1-DY
	for ipv6@ietf.org; Thu, 30 Aug 2007 08:01:00 -0400
X-IAI-Env-From: <ignatios@cello.cs.uni-bonn.de> : [131.220.4.211]
Received: from theory.cs.uni-bonn.de (theory.cs.uni-bonn.de [131.220.4.211])
	by postfix.iai.uni-bonn.de (Postfix) with ESMTP id 747785C849
	for <ipv6@ietf.org>; Thu, 30 Aug 2007 14:00:58 +0200 (MEST)
	(envelope-from ignatios@cello.cs.uni-bonn.de)
	(envelope-to ipv6@ietf.org) (1)
	(internal use: ta=0, tu=1, te=0, am=-, au=-)
Received: from cello.cs.uni-bonn.de (cello.cs.uni-bonn.de [131.220.4.178])
	by theory.cs.uni-bonn.de (8.12.9/8.12.9) with SMTP id l7UC0wUo010679
	for <ipv6@ietf.org>; Thu, 30 Aug 2007 14:00:58 +0200 (MEST)
Received: (from ignatios@cello.cs.uni-bonn.de)
	by cello.cs.uni-bonn.de (mini_sendmail/1.3.2 21nov2002 nb4 7oct2003);
	Thu, 30 Aug 2007 14:00:58 CEST (sender ignatios@cello.cs.uni-bonn.de)
Date: Thu, 30 Aug 2007 14:00:57 +0200
From: Ignatios Souvatzis <ignatios@cs.uni-bonn.de>
Cc: IPv6 WG <ipv6@ietf.org>
Message-ID: <20070830120057.GC241@cs.uni-bonn.de>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com> <20070830084658.GA241@cs.uni-bonn.de>
	<77ead0ec0708300439p43028294pdbac0bdf62f9246e@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <77ead0ec0708300439p43028294pdbac0bdf62f9246e@mail.gmail.com>
User-Agent: Mutt/1.4.1i
X-Spam-Score: 1.6 (+)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Thu, Aug 30, 2007 at 09:39:32PM +1000, Vishwas Manral wrote:
> Hi Ignatious,
> 
> Quoting the RFC2460:
> 
>    With one exception, of Hop-by-hop extension headers are not examined
>    or processed by any node along a packet's delivery path, until the packet
>    reaches the node (or each of the set of nodes, in the case of multicast)
>    identified in the Destination Address field of the IPv6 header.
> 
> So in a way you are right, but again it we may want to test the
> routing path from any router in the network to any other router in the
> network.

Well, if those routers aren't *your* routers, I'm afraid you'll need
the owners' coöperation to the extend that they install RH4-capable 
firmware.

Not much different from the IPv4 situation, I guess?

	-is

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



From ipv6-bounces@ietf.org Thu Aug 30 08:47:31 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQjOr-0002vB-IM; Thu, 30 Aug 2007 08:45:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQjOq-0002ux-1Z
	for ipv6@ietf.org; Thu, 30 Aug 2007 08:45:28 -0400
Received: from ug-out-1314.google.com ([66.249.92.175])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQjOo-0002ib-QF
	for ipv6@ietf.org; Thu, 30 Aug 2007 08:45:27 -0400
Received: by ug-out-1314.google.com with SMTP id u2so770919uge
	for <ipv6@ietf.org>; Thu, 30 Aug 2007 05:45:25 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=PKVhHbpYIOUqpIh5atfB3Ql8UJptSkNNKDp2RsayHambFZDzlFwgq2s9FyQL1v75mdseZKn+IRAg6rzlhcDFokBG8+UXVdvgcjxc4K+h5FN6Jo3FtnwRSN4XtzgNC//Pou4GKouzEtDX3d51qDkZGpQkZMi9RHiw7XccFoZegw0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=GecO2F1gGqjlfOgKUyiXYZ+thEuDsMV0hA6kf2HPXWuOioY2jyVKi4AVtlqjCmvOhCiW0k8LBoZYPN/0cXc/HlFD/WB9+KPaezWDHqV9YsCsDQpHQ/fNkJzkNuhg/svOzMEBOJ/bVEz4CYtt8Cm1+IohDomi3FZGzffckgIz3zc=
Received: by 10.142.101.17 with SMTP id y17mr20527wfb.1188477924322;
	Thu, 30 Aug 2007 05:45:24 -0700 (PDT)
Received: by 10.142.84.8 with HTTP; Thu, 30 Aug 2007 05:45:24 -0700 (PDT)
Message-ID: <77ead0ec0708300545y6a9db925xcf69d80f3596da4e@mail.gmail.com>
Date: Thu, 30 Aug 2007 22:45:24 +1000
From: "Vishwas Manral" <vishwas.ietf@gmail.com>
To: "Ignatios Souvatzis" <ignatios@cs.uni-bonn.de>
In-Reply-To: <20070830120057.GC241@cs.uni-bonn.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com> <20070830084658.GA241@cs.uni-bonn.de>
	<77ead0ec0708300439p43028294pdbac0bdf62f9246e@mail.gmail.com>
	<20070830120057.GC241@cs.uni-bonn.de>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi Ignatious,

You are right, however it will depend on what uses such
implementations are used for. As such a routing header is end-to-end.

That said another thing to keep in mind is that the situation is no
different to adding some new feature to IPv6, with the advantage that
the behavior in case the RH4 header is not recognized by a node is
well defined.

Thanks,
Vishwas

On 8/30/07, Ignatios Souvatzis <ignatios@cs.uni-bonn.de> wrote:
> On Thu, Aug 30, 2007 at 09:39:32PM +1000, Vishwas Manral wrote:
> > Hi Ignatious,
> >
> > Quoting the RFC2460:
> >
> >    With one exception, of Hop-by-hop extension headers are not examined
> >    or processed by any node along a packet's delivery path, until the p=
acket
> >    reaches the node (or each of the set of nodes, in the case of multic=
ast)
> >    identified in the Destination Address field of the IPv6 header.
> >
> > So in a way you are right, but again it we may want to test the
> > routing path from any router in the network to any other router in the
> > network.
>
> Well, if those routers aren't *your* routers, I'm afraid you'll need
> the owners' co=F6peration to the extend that they install RH4-capable
> firmware.
>
> Not much different from the IPv4 situation, I guess?
>
>         -is
>

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



From ipv6-bounces@ietf.org Thu Aug 30 08:55:37 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQjWw-00045K-UI; Thu, 30 Aug 2007 08:53:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQjWw-00045F-0A
	for ipv6@ietf.org; Thu, 30 Aug 2007 08:53:50 -0400
Received: from e35.co.us.ibm.com ([32.97.110.153])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQjWu-0002wT-Ic
	for ipv6@ietf.org; Thu, 30 Aug 2007 08:53:49 -0400
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com
	[9.17.195.106])
	by e35.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id l7UCrbrJ031087
	for <ipv6@ietf.org>; Thu, 30 Aug 2007 08:53:37 -0400
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169])
	by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v8.5) with ESMTP id
	l7UCrb0h431478 for <ipv6@ietf.org>; Thu, 30 Aug 2007 06:53:37 -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
	l7UCrb7U006441 for <ipv6@ietf.org>; Thu, 30 Aug 2007 06:53:37 -0600
Received: from cichlid.raleigh.ibm.com (wecm-9-67-159-36.wecm.ibm.com
	[9.67.159.36])
	by d03av03.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id
	l7UCrYQF006296
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 30 Aug 2007 06:53:36 -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 l7UCrT2J027846;
	Thu, 30 Aug 2007 08:53:30 -0400
Message-Id: <200708301253.l7UCrT2J027846@cichlid.raleigh.ibm.com>
To: "Vishwas Manral" <vishwas.ietf@gmail.com>
In-reply-to: <77ead0ec0708291757m28328d76m85f262036d54040a@mail.gmail.com>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<77ead0ec0708291757m28328d76m85f262036d54040a@mail.gmail.com>
Comments: In-reply-to "Vishwas Manral" <vishwas.ietf@gmail.com>
	message dated "Thu, 30 Aug 2007 10:57:05 +1000."
Date: Thu, 30 Aug 2007 08:53:29 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: -4.0 (----)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: manoj@ipinfusion.com, IPv6 WG <ipv6@ietf.org>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> However it seems you have probably not followed mails I have sending
> carefully enough. I have raised this issue on the list way back and
> got some feed back too. I have found based on feedback the main uses
> of the RH header to be Explicit Traffic Engineering as well as for OAM
> purposes (something the IETF has underplayed for a long time). There
> is a paper by Geoff Huston (I am not totally sure it was him), that
> gives some use cases for operators.

What I mean by "find a use" or "find a customer", is not to point to
some generic, hand-wavy "it would be nice" from some third party. It
is to get the customer/user who has a real problem to solve to come
and explain what that problem is, so we can talk about about how to
solve it. Anything short of that risks development of a solution  in
search of a problem. The IETF has a lot of experience with that, and
it is mostly negative.

It's easy to find _possible_ uses. What we should be looking for is a
problem that needs solving, for which a routing header really is a
good/best solution, not just a "cool" or "neat" solution.

> Having been the one to have identified the amplification attacks
> around a couple of years ago, I realize the problems and related
> security issues. However I am not sure of how you say there are no use
> cases. I got the information asking that very question on the list. It
> would be great if you can let me know what you base your assumptions
> on?

RH0 has been part of IPv6 for more than a decade. Remind of _who_ has
used it or is using it, and what critical applications take advantage
of it. I believe the answer to the question is pretty much the empty
set. That is what I mean there being "no use cases".

Thomas

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



From ipv6-bounces@ietf.org Thu Aug 30 11:12:06 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQlem-0004Wb-Tv; Thu, 30 Aug 2007 11:10:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQlek-0004WJ-LS
	for ipv6@ietf.org; Thu, 30 Aug 2007 11:10:02 -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 1IQlek-0006sd-86
	for ipv6@ietf.org; Thu, 30 Aug 2007 11:10:02 -0400
Received: by coconut.itojun.org (Postfix, from userid 501)
	id C8944233E4; Fri, 31 Aug 2007 00:09:59 +0900 (JST)
To: ipng@69706e6720323030352d30312d31340a.nosense.org
In-Reply-To: Your message of "Thu, 30 Aug 2007 19:29:59 +0930"
	<20070830192959.6306bc73.ipng@69706e6720323030352d30312d31340a.nosense.org>
References: <20070830192959.6306bc73.ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Mailer: Cue version 0.8 (070521-1856/itojun)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20070830150959.C8944233E4@coconut.itojun.org>
Date: Fri, 31 Aug 2007 00:09:59 +0900 (JST)
From: itojun@itojun.org (Jun-ichiro itojun Hagino)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Cc: narten@us.ibm.com, ipv6@ietf.org, iljitsch@muada.com, IETF@itojun.org,
	brian.e.carpenter@gmail.com
Subject: Re: History of autoconfig RFCs and siblings, please?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> I'm inclined to believe that dual-stack provider networks are going to
> be relatively rare, and may not exist at all. I think it'll either be

	WIDE and two of the biggest japanese ISPs are already dual-stacked,
	and if my guess is right it has been so for more than 5 years.
	it is not economical to purchase separate trans-pafici circuit.

itojun

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



From ipv6-bounces@ietf.org Thu Aug 30 11:29:15 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQlvd-0004jT-QH; Thu, 30 Aug 2007 11:27:29 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQlvd-0004jN-1v
	for ipv6@ietf.org; Thu, 30 Aug 2007 11:27:29 -0400
Received: from mailserver1.internap.com ([63.251.68.1])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQlvc-0004G9-L7
	for ipv6@ietf.org; Thu, 30 Aug 2007 11:27:28 -0400
Received: from [74.61.128.193] (account sleibrand@mail.internap.com HELO
	[10.239.185.239])
	by mailserver1.internap.com (CommuniGate Pro SMTP 5.1.10)
	with ESMTPSA id 87081629; Thu, 30 Aug 2007 11:27:27 -0400
Message-ID: <46D6E1DB.7030403@internap.com>
Date: Thu, 30 Aug 2007 08:27:23 -0700
From: Scott Leibrand <sleibrand@internap.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Jun-ichiro itojun Hagino <itojun@itojun.org>
References: <20070830192959.6306bc73.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<20070830150959.C8944233E4@coconut.itojun.org>
In-Reply-To: <20070830150959.C8944233E4@coconut.itojun.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: narten@us.ibm.com, ipv6@ietf.org, iljitsch@muada.com, IETF@itojun.org,
	brian.e.carpenter@gmail.com
Subject: Re: History of autoconfig RFCs and siblings, please?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Jun-ichiro itojun Hagino wrote:
>> I'm inclined to believe that dual-stack provider networks are going to
>> be relatively rare, and may not exist at all. I think it'll either be
>>     
>
> 	WIDE and two of the biggest japanese ISPs are already dual-stacked,
> 	and if my guess is right it has been so for more than 5 years.
> 	it is not economical to purchase separate trans-pafici circuit.
>   

Itojun,

I believe he was referring to the *method* of supporting both IPv4 and 
IPv6, and arguing that core routers will tend to be addressed with 
either IPv4 or IPv6, but not both.  Instead, support for the second 
protocol will tend to be provided by edge routers tunneling across the 
core (using 6PE, softwires, or another method), rather than by native IP 
forwarding by core routers.  These solutions don't require separate 
circuits for IPv6 and IPv4 traffic.

Are you familiar enough with the internal addressing of those Japanese 
ISPs to say whether they address their core routers with both IPv6 and IPv4?

Another consideration is how big a given network's "core" is.  In the 
case of a geographically constrained network, it may be quite small, and 
a dual-stack core may make more sense than MPLS.  For large global 
networks, however, it appears to me that tunneling across the core is 
becoming the preferred mode of operation.


-Scott

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



From ipv6-bounces@ietf.org Thu Aug 30 11:59:56 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQmPG-0003sK-4m; Thu, 30 Aug 2007 11:58:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQmPE-0003nf-If
	for ipv6@ietf.org; Thu, 30 Aug 2007 11:58:04 -0400
Received: from smtp4.smtp.bt.com ([217.32.164.151])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQmPD-0008Fl-4K
	for ipv6@ietf.org; Thu, 30 Aug 2007 11:58:04 -0400
Received: from E03MVC4-UKBR.domain1.systemhost.net ([193.113.197.114]) by
	smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Aug 2007 16:58:00 +0100
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 16:58:33 +0100
Message-ID: <D03E4899F2FB3D4C8464E8C76B3B68B0F27007@E03MVC4-UKBR.domain1.systemhost.net>
In-Reply-To: <20070830150959.C8944233E4@coconut.itojun.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: History of autoconfig RFCs and siblings, please?
Thread-Index: AcfrGAU6F32YLBcGQMOauZu8nuIpRwABjQwg
References: <20070830192959.6306bc73.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<20070830150959.C8944233E4@coconut.itojun.org>
From: <michael.dillon@bt.com>
To: <ipv6@ietf.org>
X-OriginalArrivalTime: 30 Aug 2007 15:58:00.0255 (UTC)
	FILETIME=[8A249CF0:01C7EB1E]
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Subject: RE: History of autoconfig RFCs and siblings, please?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


> 	WIDE and two of the biggest japanese ISPs are already=20
> dual-stacked,
> 	and if my guess is right it has been so for more than 5 years.
> 	it is not economical to purchase separate trans-pafici circuit.

6PE over MPLS and v6 tunnels over Softwires do not require purchasing
separate circuits.

--Michael Dillon

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



From ipv6-bounces@ietf.org Thu Aug 30 12:40:40 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQn2R-00071d-Ip; Thu, 30 Aug 2007 12:38:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQn2Q-000700-3F
	for ipv6@ietf.org; Thu, 30 Aug 2007 12:38:34 -0400
Received: from smtp117.iad.emailsrvr.com ([207.97.245.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQn2O-0001G6-UT
	for ipv6@ietf.org; Thu, 30 Aug 2007 12:38:34 -0400
Received: by relay1.r1.iad.emailsrvr.com (Authenticated sender:
	dow.street-AT-linquest.com) with ESMTP id 54F9744C0D7; 
	Thu, 30 Aug 2007 12:38:32 -0400 (EDT)
In-Reply-To: <87sl6132d8.fsf@natisbad.org>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com>
	<1ED2DE65-EB5E-4B17-9125-E62E4C605BAA@virtualized.org>
	<46D5D776.9030603@gmail.com> <87ejhmqaag.fsf@natisbad.org>
	<8CF7F46A-8231-44CF-B265-B46F38072E0D@linquest.com>
	<87sl6132d8.fsf@natisbad.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <125869C7-B2B7-4E08-9AC7-18977CFC9B5C@linquest.com>
Content-Transfer-Encoding: 7bit
From: Dow Street <dow.street@linquest.com>
Date: Thu, 30 Aug 2007 09:38:15 -0700
To: Arnaud Ebalard <arno@natisbad.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: IPv6 WG <ipv6@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Aug 30, 2007, at 12:31 AM, Arnaud Ebalard wrote:

> Dow Street <dow.street@linquest.com> writes:
>
>> IP seems to be the right place in the stack to deal with issues of
>> path selection and packet delivery.  Do you see a better place in a
>> different layer?
>
> If you need something working at a large scale, which creates a
> _precise_ rationale to have that included at L3, it is the place and
> SHOULD be put there.
>
> Now, if there is only a limited rationale, it COULD be put there  
> but as
> an external feature (i.e. outside 2460), to be deployed by people that
> have the need.

<snip>

>> Can you clarify what you mean by "blindly"?
>
> What 2460 specifies for routers regarding RH0 processing and what
> vendors had implemented (before the deprecation). I don't consider the
> amplification here (i.e. even a limited version of RH0 with only one
> address in it, processed by default by routers, fits my description).

Are you primarily concerned with making / keeping source routing a  
*mandatory* component of IPv6 because you see this as adding attack  
vectors at every IPv6 node?

I suppose I see these as separable:

- making the functionality mandatory is to help get it into  
implementations so that interested users / operators have source  
routing as a tool.
- this does not mean (to me) that the functionality to act as an  
intermediate source routing destination (routers and/or hosts) must  
be enabled by default.  I think this question is worth discussing.


It probably also makes sense to consider architectural and  
implementation issues separately:

Architectural:  I think this is our primary area to address in any  
new RHx draft.  As I understand it, RH4 directly addresses the  
architectural issue of RH0 that was of most concern to the group -  
the number of intermediate way-points.

Implementation:  A new RHx draft can probably provide better  
implementation guidance than was present for RH0, helping to reduce  
the number of implementation problems.  I don't think concern over  
implementation problems is a valid reason for eliminating source  
routing altogether.


There also appears to be a wider philosophical debate going on (among  
list participants) over general vs. specific functionality, and the  
type of network we think the Internet should be.  Should the Internet  
be a collection of specific mechanisms, each oriented toward a known,  
narrow, and demonstrably profitable use?  Or should the Internet  
architecture (whatever that is) provide a set of general tools that  
can be used in a variety of ways?  As IETF standards go, you don't  
get much more "architectural" than IP. 
  

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



From ipv6-bounces@ietf.org Thu Aug 30 13:22:39 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQnh5-0005RW-B1; Thu, 30 Aug 2007 13:20:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQnh3-0005Qn-Px
	for ipv6@ietf.org; Thu, 30 Aug 2007 13:20:33 -0400
Received: from [2001:6f8:387:2057:ea05:e98a:6f83:d890] (helo=moog.chdir.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQnh3-00029b-A8
	for ipv6@ietf.org; Thu, 30 Aug 2007 13:20:33 -0400
Received: from aputeaux-152-1-14-147.w82-120.abo.wanadoo.fr ([82.120.44.147]
	helo=localhost.localdomain)
	by moog.chdir.org with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.63) (envelope-from <arno@natisbad.org>)
	id 1IQngl-0005ph-3g; Thu, 30 Aug 2007 19:20:15 +0200
X-Hashcash: 1:20:070830:itojun@itojun.org::KCGfslYuYwe0gZtw:000000000000000000000000000000000000000000005XeT
X-Hashcash: 1:20:070830:narten@us.ibm.com::6y06YM/6D4u4GYEU:0000000000000000000000000000000000000000000025mR
From: arno@natisbad.org (Arnaud Ebalard)
To: Dow Street <dow.street@linquest.com>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com>
	<1ED2DE65-EB5E-4B17-9125-E62E4C605BAA@virtualized.org>
	<46D5D776.9030603@gmail.com> <87ejhmqaag.fsf@natisbad.org>
	<8CF7F46A-8231-44CF-B265-B46F38072E0D@linquest.com>
	<87sl6132d8.fsf@natisbad.org>
	<125869C7-B2B7-4E08-9AC7-18977CFC9B5C@linquest.com>
X-GnuPG-Key: 0x047A5026
X-Hashcash: 1:20:070830:dow.street@linquest.com::e1QUOcLrLEOjja2C:000000000000000000000000000000000000000DK5
X-Hashcash: 1:20:070830:ipv6@ietf.org::eYZkiskUZYxp6xn0:00000NYL
X-Hashcash: 1:20:070830:brian.e.carpenter@gmail.com::REnJwclohY4SE9EZ:00000000000000000000000000000000002RVB
Date: Thu, 30 Aug 2007 19:20:12 +0200
Message-ID: <87k5rdndmb.fsf@natisbad.org>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.95 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: -1.4 (-)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: Thomas Narten <narten@us.ibm.com>, IPv6 WG <ipv6@ietf.org>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi,

Dow Street <dow.street@linquest.com> writes:

>> What 2460 specifies for routers regarding RH0 processing and what
>> vendors had implemented (before the deprecation). I don't consider the
>> amplification here (i.e. even a limited version of RH0 with only one
>> address in it, processed by default by routers, fits my description).
>
> Are you primarily concerned with making / keeping source routing a
> *mandatory* component of IPv6 because you see this as adding attack
> vectors at every IPv6 node?

No, that's not my primary concern. My primary concern is the addition of
_proven_ useless and complicated functionalities in a fundamental part
of our communication infrastructure.


> I suppose I see these as separable:
>
> - making the functionality mandatory is to help get it into
> implementations so that interested users / operators have source
> routing as a tool.
>
> - this does not mean (to me) that the functionality to act as an
> intermediate source routing destination (routers and/or hosts) must
> be enabled by default.  I think this question is worth discussing.

As soon as you have a _precise_ use and expected users for that, sure,
i'll continue the discussion. Now, i let Thomas and Itojun keep asking
for concrete uses. I consider i have already spent enough time asking
many times the same simple questions without getting any precise
answer:  

           
                 Who will use it? How? What for?


Regards,

a+

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



From ipv6-bounces@ietf.org Thu Aug 30 13:45:41 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQo3P-00014J-8i; Thu, 30 Aug 2007 13:43:39 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQo3N-00013z-V4
	for ipv6@ietf.org; Thu, 30 Aug 2007 13:43:38 -0400
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQo3N-0008W3-J7
	for ipv6@ietf.org; Thu, 30 Aug 2007 13:43:37 -0400
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4])
	by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with
	ESMTP id l7UHhW1O013352
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 30 Aug 2007 10:43:36 -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
	l7UHhVDG007947; Thu, 30 Aug 2007 10:43:31 -0700 (PDT)
Received: from XCH-NEBH-11.ne.nos.boeing.com (xch-nebh-11.ne.nos.boeing.com
	[128.225.80.27])
	by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id
	l7UHhUQn007905; Thu, 30 Aug 2007 10:43:31 -0700 (PDT)
Received: from XCH-NE-1V2.ne.nos.boeing.com ([128.225.80.43]) by
	XCH-NEBH-11.ne.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 30 Aug 2007 13:42: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
Date: Thu, 30 Aug 2007 13:42:41 -0400
Message-ID: <CA7D9B4A761066448304A6AFC09ABDA9015AD3F6@XCH-NE-1V2.ne.nos.boeing.com>
In-Reply-To: <46D6AF06.3020805@piuha.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Deploying a new RH (Was: Re: New Routing Header!!!)
Thread-Index: Acfq+/8pFO3dxpinSWuvK2naU2BQEQAL+OAg
References: <46D670E0.7090308@apnic.net> <46D6AF06.3020805@piuha.net>
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "Jari Arkko" <jari.arkko@piuha.net>
X-OriginalArrivalTime: 30 Aug 2007 17:42:58.0294 (UTC)
	FILETIME=[34111960:01C7EB2D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581
Cc: IPv6 WG <ipv6@ietf.org>
Subject: RE: Deploying a new RH (Was: Re: New Routing Header!!!)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

> -----Original Message-----
> From: Jari Arkko [mailto:jari.arkko@piuha.net]=20

> Second, a number
> of implementations already have turned the feature off, which
> obviously means that we cannot expect a random node in the
> Internet to always respect anyone's request to perform a RH0
> operation.

There are other examples of this that have not caused the protocol to be
deprecated. One obvious example would be multicast. Another example is
TELNET. Another is directed broadcast. These continue to be very useful
protocols, at least the first two are, as far as I'm concerned, even
though I wouldn't expect any random ISP node to support them.

If anything, I'd advocate what has to be the easiest solution. Leave RH0
and RFC 2460 as is, turn RH0 off by default, allow ISPs to drop RH0
packets at edges (as they do now for other valid protocols anyway), and
go ahead with RH4 or other better ideas, if there's demand for it.

Bert

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



From ipv6-bounces@ietf.org Thu Aug 30 16:14:43 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQqNU-0002DS-2f; Thu, 30 Aug 2007 16:12:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQqNT-0002DK-6J
	for ipv6@ietf.org; Thu, 30 Aug 2007 16:12:31 -0400
Received: from rv-out-0910.google.com ([209.85.198.187])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQqNR-0006FH-Re
	for ipv6@ietf.org; Thu, 30 Aug 2007 16:12:31 -0400
Received: by rv-out-0910.google.com with SMTP id l15so219163rvb
	for <ipv6@ietf.org>; Thu, 30 Aug 2007 13:12:29 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=Qf2TPsctRju7lF3pusMIVLR5YLPeY4yX5gwSlhFYi91iedcpZpnJpPxdYP8EJrAcJkOrUTjceXbeHJnoIv3KB7hxHVxyCZw4IBKzKYREsHSKn1+8h87h+G38Ob8WRSuiEjt+b7RgkernLVRtKdKsNfuUP9SkDZJpcLh9KNrPy8g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=EbazH0GBkRvm3wS9hmgD2EHrCtqvW5swARejKmkyOEE0NLK77eRusqwXbAGGT0tV2hqj7aqfg3m2b93JMsLNrD9hEGqQDy12Th9sjH4wrU6FMYcr0k0DWr9BrQ4nUxz2GfeoI8ho1CEM69/fuPQs95or/XxiglXQwsCYwvn32vQ=
Received: by 10.141.27.18 with SMTP id e18mr359507rvj.1188504745580;
	Thu, 30 Aug 2007 13:12:25 -0700 (PDT)
Received: from ?10.1.1.7? ( [222.153.2.24])
	by mx.google.com with ESMTPS id b21sm1942607rvf.2007.08.30.13.12.17
	(version=SSLv3 cipher=RC4-MD5); Thu, 30 Aug 2007 13:12:23 -0700 (PDT)
Message-ID: <46D7249C.2030200@gmail.com>
Date: Fri, 31 Aug 2007 08:12:12 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: briand@ca.afilias.info
References: <C6FE2907-79C0-4EB2-90AC-E4E889CBEEDF@muada.com>	<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>	<471515FC-E1E1-4C83-99AA-A9821E0C2FF5@muada.com>
	<!
	!	63886.74.122.168.81.1188025388.squirrel@look.libertyrms.com>	<200708291423.l7TENQZ8000329@cichlid.raleigh.ibm.com>	<79358CCF-0A4B-424D-BA32-14099B3EF257@muada.com>
	<61722.74.122.168.81.1188400653.squirrel@look.libertyrms.com>
	<46D5D525.30005@gmail.com>
In-Reply-To: <46D5D525.30005@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.3 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
Cc: Thomas Narten <narten@us.ibm.com>,
	Iljitsch van Beijnum <iljitsch@muada.com>,
	IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: History of autoconfig RFCs and siblings, please?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Just to be clear about what I meant here: I don't
believe we know *today* how to make BGP4 handle
millions of PI prefixes; but even if that is possible
some time in the future, we still have to assume that
the vast majority (billions) of end users are in PA space
for ever.

    Brian

On 2007-08-30 08:20, Brian E Carpenter wrote:
> Brian D,
> 
> You seem to be assuming that PI will be the dominant mode.
> This seems very unlikely, since the vast majority of users
> (i.e. SOHO) have no interest in what their IP address is and
> no motivation to pay extra for PI. We have no possible
> difficulty in supporting a few million PI prefixes in the
> /48 or /56 world currently planned (apart from BGP4 blowing
> up, of course, but that's being discussed elsewhere).
> 
> Regards
>    Brian Carpenter
> 
> On 2007-08-30 03:17, briand@ca.afilias.info wrote:
>> Iljitsch wrote:
>>> On 29-aug-2007, at 16:23, Thomas Narten wrote:
>>>>> (I suppose it's a bit late in the game to go back to MAC-48 as II?)
>>>> Yes. The difficulty is figuring out how to move to something different
>>>> in a backwards-compatable way. I.e., we'd need a transition strategy.
>>> But what would be the point of doing that now?
>>
>> The point, which I have avoided making until now, is that II has direct
>> impact on the available range of assignments by RIRs to LIRs, for PI 
>> blocks,
>> that also allow for very long timescale predictive assignments.
>>
>> Basically, the minimum prefix size * number of assignments * LIRs,
>> when projected over a timeframe of decades, while preserving a global
>> DFZ consisting of one PI block per LIR, has a problem fitting into the
>> number of bits per RIR.
>>
>> Right now, RIRs are reserving only an additional 2 bits per LIR 
>> assignment,
>> for "growth". Alternative allocation policies (bisection) don't guarantee
>> the ability to assign arbitrarily large blocks indefinitely - while that
>> is in fact the long-term requirement. Block sizes *should* increase over
>> time, even as the frequency of their assignment decreases.
>>
>> What works best is, a best-fit approach, where any organization gets way
>> more space than they need, sized according to their own best guess as to
>> long-term growth *potential*.
>>
>> Then, reserve even more space for each, in a consistent manner.
>>
>> Take all these requests, and fill them in an optimized space-packing 
>> manner.
>>
>> At some point, growth requests get filled via "growing" the assignment 
>> for
>> a given LIR into its reserved space.
>>
>> And, long-term periodic reviews of those growth patterns may result in
>> bisecting *some* of those reserved blocks to make more space available
>> for similar assignments.
>>
>> This can be shown to meet the requirements of individual LIRs to within
>> a few orders of magnitude of their long-term projections (pretty good),
>> and at the same time, optimize the packing efficiency, meaning the truly
>> free space will not be fragmented except to the degree absolutely 
>> necessary
>> for the existing assignments.
>>
>> This means that new assignments have the largest possible potential 
>> prefix
>> size available, compared to other allocation methods. This can even be
>> demonstrated or possibly even proven mathematically, by modeling the
>> problem space.
>>
>>> The fact that we have so many local bits in the IPv6 address is our
>>> insurance policy against address policy screwups because a single /64
>>> is enough to run a network of arbitrary size if you forego stateless
>>> autoconfig.
>>
>> The same would be true of /80, which is what MAC-48 would result in, for
>> minimum prefix size for autoconf (and thus the standard end-user 
>> assignment
>> size).
>>
>> Of the 16 bits reclaimed via this change, I would propose to the RIRs,
>> that 4 bits be added to initial allocations, 4 bits to reservations above
>> the initial allocations (for long-term growth), and the other 8 bits add
>> to the total space available for the RIRs to allocate to LIRs - by 
>> adjusting
>> the minimum and initial allocation sizes by 8 bits.
>>
>> The numbers (4 bits and 8 bits) are not accidental - they are one nibble
>> in size, which matches up with the boundaries for reverse address 
>> lookups,
>> via ip6.arpa - which uses nibbles.
>>
>> It seems to me, that while it would be an uphill battle, the main two 
>> issues
>> are transition and compatibity, and inertia (e.g. deployed code and
>> networks.)
>>
>> The overall benefits to address space assignment, IMHO, outweigh that 
>> cost,
>> especially when considering the long-term health of the DFZ and the cost
>> to member organizations when having to do expensive upgrades to their
>> entire infrastructure to support bloat in the DFZ.
>>
>> Brian
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
> 

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



From ipv6-bounces@ietf.org Thu Aug 30 16:17:09 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQqQF-0006jE-4F; Thu, 30 Aug 2007 16:15:23 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQqQD-0006j9-Ng
	for ipv6@ietf.org; Thu, 30 Aug 2007 16:15:21 -0400
Received: from smtp137.iad.emailsrvr.com ([207.97.245.137])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQqQD-00043B-D7
	for ipv6@ietf.org; Thu, 30 Aug 2007 16:15:21 -0400
Received: by relay3.r3.iad.emailsrvr.com (Authenticated sender:
	dow.street-AT-linquest.com) with ESMTP id 7FA0346AA93; 
	Thu, 30 Aug 2007 16:15:20 -0400 (EDT)
In-Reply-To: <87k5rdndmb.fsf@natisbad.org>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com>
	<1ED2DE65-EB5E-4B17-9125-E62E4C605BAA@virtualized.org>
	<46D5D776.9030603@gmail.com> <87ejhmqaag.fsf@natisbad.org>
	<8CF7F46A-8231-44CF-B265-B46F38072E0D@linquest.com>
	<87sl6132d8.fsf@natisbad.org>
	<125869C7-B2B7-4E08-9AC7-18977CFC9B5C@linquest.com>
	<87k5rdndmb.fsf@natisbad.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <14DB5C68-453B-4D93-8445-98361A1179EE@linquest.com>
Content-Transfer-Encoding: 7bit
From: Dow Street <dow.street@linquest.com>
Date: Thu, 30 Aug 2007 13:15:04 -0700
To: arno@natisbad.org (Arnaud Ebalard)
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: Thomas Narten <narten@us.ibm.com>, IPv6 WG <ipv6@ietf.org>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Aug 30, 2007, at 10:20 AM, Arnaud Ebalard wrote:

> As soon as you have a _precise_ use and expected users for that, sure,
> i'll continue the discussion. Now, i let Thomas and Itojun keep asking
> for concrete uses. I consider i have already spent enough time asking
> many times the same simple questions without getting any precise
> answer:
>
>                  Who will use it? How? What for?

In your opinion, is it sufficient to describe potential uses of an  
IPv6 source routing mechanism?  Or is it also necessary to have the  
commitment of a large organization / commercial entity who intends to  
deploy IPv6 source routing in a specific timeframe and according to a  
specific use?  There is no intended sarcasm imbedded in this question  
- I think it is a real and valid question which partly determines how  
innovation can occur in the Internet.

I have been advocating a mechanism that is general and allows for a  
variety of potential uses.  This is the nature of RH0 - and I see  
RH4 / RHx as the "safer" replacement for RH0.  In your opinion, is  
this an acceptable approach, or would you only support a RHx that is  
tailored to a specific use case?

Thanks,
Dow




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



From ipv6-bounces@ietf.org Thu Aug 30 16:33:49 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQqgI-0004p8-Qg; Thu, 30 Aug 2007 16:31:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQqgG-0004kF-Dt
	for ipv6@ietf.org; Thu, 30 Aug 2007 16:31:56 -0400
Received: from rv-out-0910.google.com ([209.85.198.190])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQqgF-0006dO-4H
	for ipv6@ietf.org; Thu, 30 Aug 2007 16:31:56 -0400
Received: by rv-out-0910.google.com with SMTP id l15so222342rvb
	for <ipv6@ietf.org>; Thu, 30 Aug 2007 13:31:54 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=MsuIUpHO5bawK5yWHdUrVGP5uL7zOCWQ12+IipK6wQSNg3XiRR5I59Cy7sj41cYoo1Hp/ZqlCNuEa13PjArLsOu1NKoeD/Y3Noh9u1q6DW/SSvJSuUoriPUN0sBzXi4rmaWf9e2MORzMV9dtIE8J5oNuWUMYVoXTEKqrlcOpZm8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=t9H4oUxLd+/uN+Kzjs9SQhheAnsvFrzaAuqIJeYtPzFTjVv+dsveOHnJ5YSkFdGrDSSv3mwrhyxnQgmwHCc89B0mKEtOUJUY5vmQUsxw1BfJTLXK9zy7L1uJ0SkWUMCcGufkO2RTGFHvVa9wKEBDLR31ue8wfpi3H+vt/CsG0rc=
Received: by 10.141.189.4 with SMTP id r4mr375389rvp.1188505913953;
	Thu, 30 Aug 2007 13:31:53 -0700 (PDT)
Received: from ?10.1.1.7? ( [222.153.2.24])
	by mx.google.com with ESMTPS id c36sm1749126rvf.2007.08.30.13.31.49
	(version=SSLv3 cipher=RC4-MD5); Thu, 30 Aug 2007 13:31:51 -0700 (PDT)
Message-ID: <46D72930.3020402@gmail.com>
Date: Fri, 31 Aug 2007 08:31:44 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Ignatios Souvatzis <ignatios@cs.uni-bonn.de>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>	<46D5D148.6080701@gmail.com>
	<20070830084658.GA241@cs.uni-bonn.de>
In-Reply-To: <20070830084658.GA241@cs.uni-bonn.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On 2007-08-30 20:46, Ignatios Souvatzis wrote:
> On Thu, Aug 30, 2007 at 08:04:24AM +1200, Brian E Carpenter wrote:
>> On 2007-08-30 02:08, Thomas Narten wrote:
>>> Sorry to interrupt, but I'd suggest that working on a new RH design is
>>> mostly a waste of time at this point.
>>>
>>> Can we please _first_ identify a user/customer for a proposed RH, 
>> I agree. A use case draft should be the first step.
>>
>> Incidentally, RFC 2460 is clear that unknown headers should cause the
>> packet to be dropped, so the transition strategy is tricky in any case.
>>
>>    If, as a result of processing a header, a node is required to proceed
>>    to the next header but the Next Header value in the current header is
>>    unrecognized by the node, it should discard the packet and send an
>>    ICMP Parameter Problem message to the source of the packet, with an
>>    ICMP Code value of 1 ("unrecognized Next Header type encountered")
>>    and the ICMP Pointer field containing the offset of the unrecognized
>>    value within the original packet.
> 
> Yes, but this would only be the node addressed by the IPv6 header - or 
> do I read this wrongly? 

Correct ... and actually I quoted the wrong text for the case of an
unknown RH number, but the result is the same - only the next-hop
router listed in the RH itself needs to understand that new RH number.
But that does create a 'consenting adults' situation; if you construct
an RHx you must know that every router listed in it understands RHx,
otherwise the packet will be dropped. That is quite a restriction on
deployment scenarios beyond experimental or local use.

     Brian

> So the core of the network is not affected either
> way (unless explicit filtering is implemented somewhere), and only
> routers of end networks that wish to participate in, say, a future RH4
> routing would need to upgrade the software.
> 
> 	-is
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 

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



From ipv6-bounces@ietf.org Thu Aug 30 17:30:35 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQrZ8-00013r-Ct; Thu, 30 Aug 2007 17:28:38 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQrZ6-0000x9-Ha
	for ipv6@ietf.org; Thu, 30 Aug 2007 17:28:36 -0400
Received: from levanto.mail.adnap.net.au ([203.6.132.83])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQrZ5-0005i2-RU
	for ipv6@ietf.org; Thu, 30 Aug 2007 17:28:36 -0400
Received: from 122-49-179-97.ip.adam.com.au ([122.49.179.97]
	helo=mail.nosense.org)
	by levanto.mail.adnap.net.au with esmtp (Exim 4.63 (FreeBSD))
	(envelope-from <ipng@69706e6720323030352d30312d31340a.nosense.org>)
	id 1IQrYt-000Dvv-JT; Fri, 31 Aug 2007 06:58:23 +0930
Received: from ubu.nosense.org (localhost.localdomain [127.0.0.1])
	by mail.nosense.org (Postfix) with SMTP id B16E6FC81;
	Fri, 31 Aug 2007 06:58:21 +0930 (CST)
Date: Fri, 31 Aug 2007 06:58:21 +0930
From: Mark Smith <ipng@69706e6720323030352d30312d31340a.nosense.org>
To: Scott Leibrand <sleibrand@internap.com>
Message-Id: <20070831065821.88a97b1b.ipng@69706e6720323030352d30312d31340a.nosense.org>
In-Reply-To: <46D6E1DB.7030403@internap.com>
References: <20070830192959.6306bc73.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<20070830150959.C8944233E4@coconut.itojun.org>
	<46D6E1DB.7030403@internap.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: 8b431ad66d60be2d47c7bfeb879db82c
Cc: narten@us.ibm.com, ipv6@ietf.org, iljitsch@muada.com, IETF@itojun.org,
	brian.e.carpenter@gmail.com
Subject: Re: History of autoconfig RFCs and siblings, please?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Thu, 30 Aug 2007 08:27:23 -0700
Scott Leibrand <sleibrand@internap.com> wrote:

> Jun-ichiro itojun Hagino wrote:
> >> I'm inclined to believe that dual-stack provider networks are going to
> >> be relatively rare, and may not exist at all. I think it'll either be
> >>     
> >
> > 	WIDE and two of the biggest japanese ISPs are already dual-stacked,
> > 	and if my guess is right it has been so for more than 5 years.
> > 	it is not economical to purchase separate trans-pafici circuit.
> >   

Oh ok. Down here in .au our perspective on things like IPv6 deployment
tends to get warped by being an English speaking country. I know Japan
has IPv6 quite widely deployed, however we rarely if ever see any
English news about it.

> 
> Itojun,
> 
> I believe he was referring to the *method* of supporting both IPv4 and 
> IPv6, and arguing that core routers will tend to be addressed with 
> either IPv4 or IPv6, but not both.  Instead, support for the second 
> protocol will tend to be provided by edge routers tunneling across the 
> core (using 6PE, softwires, or another method), rather than by native IP 
> forwarding by core routers.  These solutions don't require separate 
> circuits for IPv6 and IPv4 traffic.
> 

That's what I was trying to say. It seems to me that the relative
simplicity of a single core forwarding protocol and more general
purpose characteristics (of MPLS, GRE or L2TP) of these "edge-to-edge
tunnelling methods" might to be more appealing than dual-stack for
those who haven't already deployed dual-stack, in particular if they're
facing a hardware or software upgrade cycle to get there.

> Are you familiar enough with the internal addressing of those Japanese 
> ISPs to say whether they address their core routers with both IPv6 and IPv4?
> 
> Another consideration is how big a given network's "core" is.  In the 
> case of a geographically constrained network, it may be quite small, and 
> a dual-stack core may make more sense than MPLS.  For large global 
> networks, however, it appears to me that tunneling across the core is 
> becoming the preferred mode of operation.
> 
> 
> -Scott

Regards,
Mark.

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



From ipv6-bounces@ietf.org Thu Aug 30 17:34:39 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQrdB-0005SI-SC; Thu, 30 Aug 2007 17:32:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQrdA-0005QC-8C
	for ipv6@ietf.org; Thu, 30 Aug 2007 17:32:48 -0400
Received: from smtp147.iad.emailsrvr.com ([207.97.245.147])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQrd9-0007j2-1j
	for ipv6@ietf.org; Thu, 30 Aug 2007 17:32:48 -0400
Received: by relay4.r5.iad.mlsrvr.com (Authenticated sender:
	dow.street-AT-linquest.com) with ESMTP id 3597CD0E9; 
	Thu, 30 Aug 2007 17:32:46 -0400 (EDT)
In-Reply-To: <46D72930.3020402@gmail.com>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>	<46D5D148.6080701@gmail.com>
	<20070830084658.GA241@cs.uni-bonn.de> <46D72930.3020402@gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <77736C78-4837-4949-A732-9137504DEE6A@linquest.com>
Content-Transfer-Encoding: 7bit
From: Dow Street <dow.street@linquest.com>
Date: Thu, 30 Aug 2007 14:32:27 -0700
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: IPv6 WG <ipv6@ietf.org>, Ignatios Souvatzis <ignatios@cs.uni-bonn.de>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


On Aug 30, 2007, at 1:31 PM, Brian E Carpenter wrote:

>>> Incidentally, RFC 2460 is clear that unknown headers should cause  
>>> the
>>> packet to be dropped, so the transition strategy is tricky in any  
>>> case.
>>>
>>>    If, as a result of processing a header, a node is required to  
>>> proceed
>>>    to the next header but the Next Header value in the current  
>>> header is
>>>    unrecognized by the node, it should discard the packet and  
>>> send an
>>>    ICMP Parameter Problem message to the source of the packet,  
>>> with an
>>>    ICMP Code value of 1 ("unrecognized Next Header type  
>>> encountered")
>>>    and the ICMP Pointer field containing the offset of the  
>>> unrecognized
>>>    value within the original packet.
>> Yes, but this would only be the node addressed by the IPv6 header  
>> - or do I read this wrongly?
>
> Correct ... and actually I quoted the wrong text for the case of an
> unknown RH number, but the result is the same - only the next-hop
> router listed in the RH itself needs to understand that new RH number.
> But that does create a 'consenting adults' situation; if you construct
> an RHx you must know that every router listed in it understands RHx,
> otherwise the packet will be dropped. That is quite a restriction on
> deployment scenarios beyond experimental or local use.
>
>     Brian

Maybe this isn't a huge problem.  For source routing to be  
particularly useful, the sender probably wants / needs to know  
something about the topology.  At a minimum, the sender would  
presumably need to know the addresses of the way-points to use in the  
source route.  Whatever mechanism / process is used to determine  
these way-points could probably verify RHx support (at those  
addresses) with just a little more work.

R,
Dow

>> So the core of the network is not affected either
>> way (unless explicit filtering is implemented somewhere), and only
>> routers of end networks that wish to participate in, say, a future  
>> RH4
>> routing would need to upgrade the software.
>> 	-is
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


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



From ipv6-bounces@ietf.org Thu Aug 30 17:42:46 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQrl1-0005V5-QZ; Thu, 30 Aug 2007 17:40:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQrkz-0005SU-On
	for ipv6@ietf.org; Thu, 30 Aug 2007 17:40:53 -0400
Received: from [2001:6f8:387:2057:ea05:e98a:6f83:d890] (helo=moog.chdir.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQrkz-0007rM-5T
	for ipv6@ietf.org; Thu, 30 Aug 2007 17:40:53 -0400
Received: from [2002:58a4:b573:1:20d:93ff:feeb:2d3]
	(helo=localhost.localdomain)
	by moog.chdir.org with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.63) (envelope-from <arno@natisbad.org>)
	id 1IQrki-0007Wx-W1; Thu, 30 Aug 2007 23:40:37 +0200
From: arno@natisbad.org (Arnaud Ebalard)
To: Dow Street <dow.street@linquest.com>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com>
	<1ED2DE65-EB5E-4B17-9125-E62E4C605BAA@virtualized.org>
	<46D5D776.9030603@gmail.com> <87ejhmqaag.fsf@natisbad.org>
	<8CF7F46A-8231-44CF-B265-B46F38072E0D@linquest.com>
	<87sl6132d8.fsf@natisbad.org>
	<125869C7-B2B7-4E08-9AC7-18977CFC9B5C@linquest.com>
	<87k5rdndmb.fsf@natisbad.org>
	<14DB5C68-453B-4D93-8445-98361A1179EE@linquest.com>
X-GnuPG-Key: 0x047A5026
X-Hashcash: 1:20:070830:itojun@itojun.org::eW1jZuYm86P5PwjR:000000000000000000000000000000000000000000001dIR
X-Hashcash: 1:20:070830:ipv6@ietf.org::CWcBRIxzVmE5qXLr:00001ENM
X-Hashcash: 1:20:070830:brian.e.carpenter@gmail.com::AXHfCJPXKj8Odcnt:00000000000000000000000000000000000daq
X-Hashcash: 1:20:070830:dow.street@linquest.com::yIIl+LUspWc2cGli:000000000000000000000000000000000000000myB
X-Hashcash: 1:20:070830:narten@us.ibm.com::Yrg3uvxkZ5/flcn/:000000000000000000000000000000000000000000004eC5
Date: Thu, 30 Aug 2007 23:40:32 +0200
In-Reply-To: <14DB5C68-453B-4D93-8445-98361A1179EE@linquest.com> (Dow Street's
	message of "Thu, 30 Aug 2007 13:15:04 -0700")
Message-ID: <87d4x4n1kf.fsf@natisbad.org>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.95 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.3 (/)
X-Scan-Signature: c0bedb65cce30976f0bf60a0a39edea4
Cc: Thomas Narten <narten@us.ibm.com>, IPv6 WG <ipv6@ietf.org>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi,

Dow Street <dow.street@linquest.com> writes:

> On Aug 30, 2007, at 10:20 AM, Arnaud Ebalard wrote:
>
>> As soon as you have a _precise_ use and expected users for that, sure,
>> i'll continue the discussion. Now, i let Thomas and Itojun keep asking
>> for concrete uses. I consider i have already spent enough time asking
>> many times the same simple questions without getting any precise
>> answer:
>>
>>                  Who will use it? How? What for?
>
> In your opinion, is it sufficient to describe potential uses of an
> IPv6 source routing mechanism?  Or is it also necessary to have the
> commitment of a large organization / commercial entity who intends to
> deploy IPv6 source routing in a specific timeframe and according to a
> specific use? 

No. IMHO, if someone comes with a good idea and other people find it
useful and want to have that in their laptop/network/pda/phone ... it
seems you have support and should start working on it.

In that particular case, people put the most powerful source routing
mechanism in the specification, which then got implemented on all
routers and even some hosts. 

During the _huge_ threads after CanSecWest during the discussions on the
ietf ML, we asked many times if someone had a use or had already used
it. 

I can remember one person who knew someone that uses the mechanism for
some firewalling stuff (correct me if i'm wrong). I don't remember if I
asked about the tools that allowed to use RH0: I know only ping6 and
scapy6 (again, correction appreciated). 

What i try to show is that the mechanism has been _proven_ useless by a
past decade of full availability: you can bearly find users and tools
(at least on IETF IPv6 WG ML). 

> There is no intended sarcasm imbedded in this question
> - I think it is a real and valid question which partly determines how
> innovation can occur in the Internet.

Someone has a _good_ idea, code it / specify it. If it's real innovation
or useful enough, it gets an audience. Otherwise, it remains only an RFC
#, or some useless piece of undebugged code in millions of network
stacks.

> I have been advocating a mechanism that is general and allows for a
> variety of potential uses....

... which have not already been discovered during last decade.

> In your opinion, is  this an acceptable approach, or would you only
> support a RHx that is tailored to a specific use case?

For me, you are adding a sword to a chirurgical toolkit, in the hope
that it will be sharp enough to be used for some purpose in the
future. I just don't see the point.

You asked for my opinion, so it's just that. 

Regards,

a+

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



From ipv6-bounces@ietf.org Thu Aug 30 18:14:31 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQsFj-0003Nz-23; Thu, 30 Aug 2007 18:12:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQsFh-0003LU-9v
	for ipv6@ietf.org; Thu, 30 Aug 2007 18:12:37 -0400
Received: from rv-out-0910.google.com ([209.85.198.187])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQsFf-0008U2-AN
	for ipv6@ietf.org; Thu, 30 Aug 2007 18:12:37 -0400
Received: by rv-out-0910.google.com with SMTP id l15so239361rvb
	for <ipv6@ietf.org>; Thu, 30 Aug 2007 15:12:34 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=AlhOLOtdfSsa58Z4hZvx/+t3NzaViy/axZHvgXUauHgEIceRxc6UVtTedyAH5jacG5xN0KujhneiC3h9gsy5nQZEw27/Iq1gbbMkE4tphrHcSnzj87sGfkqX+pApQyurBm1LzBdhP6uKAYi28iCNUqglRh32dgFBmyyaojXaZhc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=tirsbXTZrUDy0If9d9NvbR2itlbe204iTW/5BxWK695GFdx7RxZCCaPKUX0SeJ0e/4M8/+2slLWlHgm9Iy2zpKYwynKeJOjwdG7bQI5J/UWfeivSQ5gWHU2OPvBQr3Ntyxdq/02alcVDHKrijNSsjGO2RCbI8KygCnABUELQARQ=
Received: by 10.141.97.5 with SMTP id z5mr402280rvl.1188511954361;
	Thu, 30 Aug 2007 15:12:34 -0700 (PDT)
Received: from ?10.1.1.7? ( [222.153.2.24])
	by mx.google.com with ESMTPS id b8sm1886260rvf.2007.08.30.15.12.30
	(version=SSLv3 cipher=RC4-MD5); Thu, 30 Aug 2007 15:12:32 -0700 (PDT)
Message-ID: <46D740C9.1050103@gmail.com>
Date: Fri, 31 Aug 2007 10:12:25 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Dow Street <dow.street@linquest.com>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>	<46D5D148.6080701@gmail.com>
	<20070830084658.GA241@cs.uni-bonn.de> <46D72930.3020402@gmail.com>
	<77736C78-4837-4949-A732-9137504DEE6A@linquest.com>
In-Reply-To: <77736C78-4837-4949-A732-9137504DEE6A@linquest.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Cc: IPv6 WG <ipv6@ietf.org>, Ignatios Souvatzis <ignatios@cs.uni-bonn.de>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Dow,

Fortunately, Bill Fenner thought things through when drafting
RFC 4727 (Experimental Values in Headers):

"3.6.  IPv6 Routing Header Routing Type

    This document assigns two values for the Routing Type field in the
    IPv6 Routing Header, 253 and 254."

So, people wanting to work on a new RH type can develop
use cases and run experiments using these values, without
further IETF action. These values are fine in a 'consenting
adults' situation if unmodified nodes implement the RFC 2460
rules correctly.

    Brian

On 2007-08-31 09:32, Dow Street wrote:
> 
> On Aug 30, 2007, at 1:31 PM, Brian E Carpenter wrote:
> 
>>>> Incidentally, RFC 2460 is clear that unknown headers should cause the
>>>> packet to be dropped, so the transition strategy is tricky in any case.
>>>>
>>>>    If, as a result of processing a header, a node is required to 
>>>> proceed
>>>>    to the next header but the Next Header value in the current 
>>>> header is
>>>>    unrecognized by the node, it should discard the packet and send an
>>>>    ICMP Parameter Problem message to the source of the packet, with an
>>>>    ICMP Code value of 1 ("unrecognized Next Header type encountered")
>>>>    and the ICMP Pointer field containing the offset of the unrecognized
>>>>    value within the original packet.
>>> Yes, but this would only be the node addressed by the IPv6 header - 
>>> or do I read this wrongly?
>>
>> Correct ... and actually I quoted the wrong text for the case of an
>> unknown RH number, but the result is the same - only the next-hop
>> router listed in the RH itself needs to understand that new RH number.
>> But that does create a 'consenting adults' situation; if you construct
>> an RHx you must know that every router listed in it understands RHx,
>> otherwise the packet will be dropped. That is quite a restriction on
>> deployment scenarios beyond experimental or local use.
>>
>>     Brian
> 
> Maybe this isn't a huge problem.  For source routing to be particularly 
> useful, the sender probably wants / needs to know something about the 
> topology.  At a minimum, the sender would presumably need to know the 
> addresses of the way-points to use in the source route.  Whatever 
> mechanism / process is used to determine these way-points could probably 
> verify RHx support (at those addresses) with just a little more work.
> 
> R,
> Dow
> 
>>> So the core of the network is not affected either
>>> way (unless explicit filtering is implemented somewhere), and only
>>> routers of end networks that wish to participate in, say, a future RH4
>>> routing would need to upgrade the software.
>>>     -is
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> 
> 

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



From ipv6-bounces@ietf.org Thu Aug 30 19:45:26 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQtfU-0001Fs-IH; Thu, 30 Aug 2007 19:43:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQtfR-0001Fa-Ne; Thu, 30 Aug 2007 19:43:17 -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 1IQtfR-0001f1-AL; Thu, 30 Aug 2007 19:43:17 -0400
Received: by coconut.itojun.org (Postfix, from userid 501)
	id 71133233D0; Fri, 31 Aug 2007 08:43:14 +0900 (JST)
To: ietf@ietf.org, ipv6@ietf.org
In-Reply-To: Your message of "Thu, 30 Aug 2007 19:29:59 +0930"
	<20070830192959.6306bc73.ipng@69706e6720323030352d30312d31340a.nosense.org>
References: <20070830192959.6306bc73.ipng@69706e6720323030352d30312d31340a.nosense.org>
X-Mailer: Cue version 0.8 (070521-1856/itojun)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20070830234314.71133233D0@coconut.itojun.org>
Date: Fri, 31 Aug 2007 08:43:14 +0900 (JST)
From: itojun@itojun.org (Jun-ichiro itojun Hagino)
X-Spam-Score: -0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: 
Subject: Re: History of autoconfig RFCs and siblings, please?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

	(sorry if it gets a duplicate)

> I'm inclined to believe that dual-stack provider networks are going to
> be relatively rare, and may not exist at all. I think it'll either be

	WIDE (AS2500) and two of the major ISPs which deploy IPv6 are running
	dual-stack.  i bet others too (Verio, Internet2, anyone?)
	it is not economical to run two separate physical link across the
	pacific ocean.

itojun

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



From ipv6-bounces@ietf.org Thu Aug 30 20:17:35 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQuAt-0007f7-1p; Thu, 30 Aug 2007 20:15:47 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQuAs-0007ZQ-1z
	for ipv6@ietf.org; Thu, 30 Aug 2007 20:15:46 -0400
Received: from smtp117.iad.emailsrvr.com ([207.97.245.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQuAq-0002Ll-Sf
	for ipv6@ietf.org; Thu, 30 Aug 2007 20:15:46 -0400
Received: by relay1.r1.iad.emailsrvr.com (Authenticated sender:
	dow.street-AT-linquest.com) with ESMTP id DAD0544CBF2; 
	Thu, 30 Aug 2007 20:15:43 -0400 (EDT)
In-Reply-To: <87d4x4n1kf.fsf@natisbad.org>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com>
	<1ED2DE65-EB5E-4B17-9125-E62E4C605BAA@virtualized.org>
	<46D5D776.9030603@gmail.com> <87ejhmqaag.fsf@natisbad.org>
	<8CF7F46A-8231-44CF-B265-B46F38072E0D@linquest.com>
	<87sl6132d8.fsf@natisbad.org>
	<125869C7-B2B7-4E08-9AC7-18977CFC9B5C@linquest.com>
	<87k5rdndmb.fsf@natisbad.org>
	<14DB5C68-453B-4D93-8445-98361A1179EE@linquest.com>
	<87d4x4n1kf.fsf@natisbad.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F9D764D2-D560-44AB-B3A3-F3F257895A18@linquest.com>
Content-Transfer-Encoding: 7bit
From: Dow Street <dow.street@linquest.com>
Date: Thu, 30 Aug 2007 17:15:26 -0700
To: Arnaud Ebalard <arno@natisbad.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: Thomas Narten <narten@us.ibm.com>, IPv6 WG <ipv6@ietf.org>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Aug 30, 2007, at 2:40 PM, Arnaud Ebalard wrote:

>> In your opinion, is it sufficient to describe potential uses of an
>> IPv6 source routing mechanism?  Or is it also necessary to have the
>> commitment of a large organization / commercial entity who intends to
>> deploy IPv6 source routing in a specific timeframe and according to a
>> specific use?
>
> No. IMHO, if someone comes with a good idea and other people find it
> useful and want to have that in their laptop/network/pda/phone ... it
> seems you have support and should start working on it.

Is that "no" to the first or second question?

> In that particular case, people put the most powerful source routing
> mechanism in the specification, which then got implemented on all
> routers and even some hosts.

Do you mean the case of RH0?

> During the _huge_ threads after CanSecWest during the discussions  
> on the
> ietf ML, we asked many times if someone had a use or had already used
> it.
>
> I can remember one person who knew someone that uses the mechanism for
> some firewalling stuff (correct me if i'm wrong). I don't remember  
> if I
> asked about the tools that allowed to use RH0: I know only ping6 and
> scapy6 (again, correction appreciated).
>
> What i try to show is that the mechanism has been _proven_ useless  
> by a
> past decade of full availability: you can bearly find users and tools
> (at least on IETF IPv6 WG ML).

RH0 may have been fully available from the perspective of IPv6  
implementations, but given the limited deployment of IPv6, I don't  
think lack of current use is *proof* that IPv6 RH0 is not useful, or  
would not be useful in the future.

R,
Dow




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



From ipv6-bounces@ietf.org Thu Aug 30 20:39:51 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQuWT-0005qZ-0F; Thu, 30 Aug 2007 20:38:05 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQuWR-0005qR-Pb; Thu, 30 Aug 2007 20:38:03 -0400
Received: from drugs.dv.isc.org ([2001:470:1f00:820:214:22ff:fed9:fbdc])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IQuWR-0002nx-7s; Thu, 30 Aug 2007 20:38:03 -0400
Received: from drugs.dv.isc.org (localhost [127.0.0.1])
	by drugs.dv.isc.org (8.14.1/8.14.1) with ESMTP id l7V0bvqC094502;
	Fri, 31 Aug 2007 10:37:57 +1000 (EST)
	(envelope-from marka@drugs.dv.isc.org)
Message-Id: <200708310037.l7V0bvqC094502@drugs.dv.isc.org>
To: itojun@itojun.org (Jun-ichiro itojun Hagino)
From: Mark Andrews <Mark_Andrews@isc.org>
In-reply-to: Your message of "Fri, 31 Aug 2007 08:43:14 +0900."
	<20070830234314.71133233D0@coconut.itojun.org> 
Date: Fri, 31 Aug 2007 10:37:57 +1000
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: ipv6@ietf.org, ietf@ietf.org
Subject: Re: History of autoconfig RFCs and siblings, please? 
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org


> 	(sorry if it gets a duplicate)
> 
> > I'm inclined to believe that dual-stack provider networks are going to
> > be relatively rare, and may not exist at all. I think it'll either be
> 
> 	WIDE (AS2500) and two of the major ISPs which deploy IPv6 are running
> 	dual-stack.  i bet others too (Verio, Internet2, anyone?)
> 	it is not economical to run two separate physical link across the
> 	pacific ocean.

	HE is according to their web pages.
 
> itojun
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org

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



From ipv6-bounces@ietf.org Thu Aug 30 20:57:49 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQuna-0000H5-Sl; Thu, 30 Aug 2007 20:55:46 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQunZ-0000Gs-Av
	for ipv6@ietf.org; Thu, 30 Aug 2007 20:55:45 -0400
Received: from smtp167.iad.emailsrvr.com ([207.97.245.167])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQunZ-0001ZZ-0f
	for ipv6@ietf.org; Thu, 30 Aug 2007 20:55:45 -0400
Received: by relay6.relay.iad.emailsrvr.com (Authenticated sender:
	dow.street-AT-linquest.com) with ESMTP id 4DB106A6563; 
	Thu, 30 Aug 2007 20:55:44 -0400 (EDT)
In-Reply-To: <46D740C9.1050103@gmail.com>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>	<46D5D148.6080701@gmail.com>
	<20070830084658.GA241@cs.uni-bonn.de> <46D72930.3020402@gmail.com>
	<77736C78-4837-4949-A732-9137504DEE6A@linquest.com>
	<46D740C9.1050103@gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <F8DF4E6C-42FB-4B42-9B2A-42D68076E324@linquest.com>
Content-Transfer-Encoding: 7bit
From: Dow Street <dow.street@linquest.com>
Date: Thu, 30 Aug 2007 17:55:28 -0700
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: IPv6 WG <ipv6@ietf.org>, Ignatios Souvatzis <ignatios@cs.uni-bonn.de>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Aug 30, 2007, at 3:12 PM, Brian E Carpenter wrote:

> Dow,
>
> Fortunately, Bill Fenner thought things through when drafting
> RFC 4727 (Experimental Values in Headers):
>
> "3.6.  IPv6 Routing Header Routing Type
>
>    This document assigns two values for the Routing Type field in the
>    IPv6 Routing Header, 253 and 254."
>
> So, people wanting to work on a new RH type can develop
> use cases and run experiments using these values, without
> further IETF action. These values are fine in a 'consenting
> adults' situation if unmodified nodes implement the RFC 2460
> rules correctly.
>
>    Brian

Thanks, Brian.  This is a good point, and I think it raises a few  
important questions for the group:

- What bounds are placed on the achievable source routing  
functionality if only consenting nodes participate, and all other  
nodes simply forward (without processing) or drop?  I don't have a  
clear idea on this yet.

- If a "consenting nodes only" model is adopted, is any arbitrary  
behavior by those consenting nodes deemed acceptable by the non- 
consenting nodes?  Previous discussions seemed to indicate that at  
least some folks would answer "no" to this question.

In other words, how is using RH 253 between consenting nodes (allowed  
to behave arbitrarily) any different than allowing consenting nodes  
to run RH0, and non-consenting nodes disabling RH0?  One difference  
(cynical hat on) is that opponents of source routing now force  
proponents to get new functionality implemented and deployed - only  
to have the same debate a few years from now when it comes time to  
standardize the functionality.

Do I have this right?

R,
Dow



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



From ipv6-bounces@ietf.org Thu Aug 30 21:44:48 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQvX9-0003O8-9Z; Thu, 30 Aug 2007 21:42:51 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQvX6-0003Cz-7j; Thu, 30 Aug 2007 21:42:48 -0400
Received: from tyholt.uninett.no ([158.38.62.9])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IQvX5-0002cn-Nv; Thu, 30 Aug 2007 21:42:48 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by tyholt.uninett.no (Postfix) with ESMTP id 7C6962BAEF1;
	Fri, 31 Aug 2007 03:37:45 +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 27323-01-28; Fri, 31 Aug 2007 03:37:45 +0200 (CEST)
Received: from [210.72.151.201] (unknown [210.72.151.201])
	by tyholt.uninett.no (Postfix) with ESMTP id 5EAE42BAE4A;
	Fri, 31 Aug 2007 03:37:44 +0200 (CEST)
Message-ID: <46D7741C.7030208@uninett.no>
Date: Fri, 31 Aug 2007 03:51:24 +0200
From: Stig Venaas <stig.venaas@uninett.no>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Jun-ichiro itojun Hagino <itojun@itojun.org>
References: <20070830192959.6306bc73.ipng@69706e6720323030352d30312d31340a.nosense.org>
	<20070830234314.71133233D0@coconut.itojun.org>
In-Reply-To: <20070830234314.71133233D0@coconut.itojun.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at uninett.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: ipv6@ietf.org, ietf@ietf.org
Subject: Re: History of autoconfig RFCs and siblings, please?
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Jun-ichiro itojun Hagino wrote:
> 	(sorry if it gets a duplicate)
> 
>> I'm inclined to believe that dual-stack provider networks are going to
>> be relatively rare, and may not exist at all. I think it'll either be
> 
> 	WIDE (AS2500) and two of the major ISPs which deploy IPv6 are running
> 	dual-stack.  i bet others too (Verio, Internet2, anyone?)
> 	it is not economical to run two separate physical link across the
> 	pacific ocean.

At least pretty much all the academic networks I know are dual-stack,
pretty big networks too, and this happened years ago.

Several years ago the operator I work for also did that. We run IS-IS
which handles both protocols with just one routing instance which is
nice. The only problem we have is that it is hard to know exactly how
much and what IPv6 traffic passes through the core. E.g. even though
the routers are Netflow v9 capable, the hardware is not capable of
creating IPv6 flow info.

Stig

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


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



From ipv6-bounces@ietf.org Thu Aug 30 21:52:08 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IQveM-0001bv-Mq; Thu, 30 Aug 2007 21:50:18 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IQveL-0001bq-Kc
	for ipv6@ietf.org; Thu, 30 Aug 2007 21:50:17 -0400
Received: from tyholt.uninett.no ([158.38.62.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IQveK-0004H2-4h
	for ipv6@ietf.org; Thu, 30 Aug 2007 21:50:17 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by tyholt.uninett.no (Postfix) with ESMTP id A03CD2BAEF1
	for <ipv6@ietf.org>; Fri, 31 Aug 2007 03:45:14 +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 27323-01-46 for <ipv6@ietf.org>;
	Fri, 31 Aug 2007 03:45:14 +0200 (CEST)
Received: from [210.72.151.201] (unknown [210.72.151.201])
	by tyholt.uninett.no (Postfix) with ESMTP id 0A7D62BAE4A
	for <ipv6@ietf.org>; Fri, 31 Aug 2007 03:45:13 +0200 (CEST)
Message-ID: <46D775DE.3080701@uninett.no>
Date: Fri, 31 Aug 2007 03:58:54 +0200
From: Stig Venaas <stig.venaas@uninett.no>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IPv6 WG <ipv6@ietf.org>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>	<77ead0ec0708291757m28328d76m85f262036d54040a@mail.gmail.com>
	<200708301253.l7UCrT2J027846@cichlid.raleigh.ibm.com>
In-Reply-To: <200708301253.l7UCrT2J027846@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at uninett.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Thomas Narten wrote:
[...]
> RH0 has been part of IPv6 for more than a decade. Remind of _who_ has
> used it or is using it, and what critical applications take advantage
> of it. I believe the answer to the question is pretty much the empty
> set. That is what I mean there being "no use cases".

I'm not arguing for keeping source routing here, but one quite useful
thing it can be used for is traceroute. You can for instance trace from
a remote point in the network towards yourself. This can be very helpful
when debugging routing problems.

Stig

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


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



From ipv6-bounces@ietf.org Fri Aug 31 03:38:19 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IR133-0006Fq-LC; Fri, 31 Aug 2007 03:36:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IR132-0006Fj-CN
	for ipv6@ietf.org; Fri, 31 Aug 2007 03:36:08 -0400
Received: from [2001:6f8:387:2057:ea05:e98a:6f83:d890] (helo=moog.chdir.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IR131-0003m8-Nf
	for ipv6@ietf.org; Fri, 31 Aug 2007 03:36:08 -0400
Received: from aputeaux-152-1-14-147.w82-120.abo.wanadoo.fr ([82.120.44.147]
	helo=localhost.localdomain)
	by moog.chdir.org with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.63) (envelope-from <arno@natisbad.org>)
	id 1IR12n-0002Vl-Tk; Fri, 31 Aug 2007 09:35:54 +0200
From: arno@natisbad.org (Arnaud Ebalard)
To: Dow Street <dow.street@linquest.com>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<46D5D148.6080701@gmail.com>
	<1ED2DE65-EB5E-4B17-9125-E62E4C605BAA@virtualized.org>
	<46D5D776.9030603@gmail.com> <87ejhmqaag.fsf@natisbad.org>
	<8CF7F46A-8231-44CF-B265-B46F38072E0D@linquest.com>
	<87sl6132d8.fsf@natisbad.org>
	<125869C7-B2B7-4E08-9AC7-18977CFC9B5C@linquest.com>
	<87k5rdndmb.fsf@natisbad.org>
	<14DB5C68-453B-4D93-8445-98361A1179EE@linquest.com>
	<87d4x4n1kf.fsf@natisbad.org>
	<F9D764D2-D560-44AB-B3A3-F3F257895A18@linquest.com>
X-GnuPG-Key: 0x047A5026
X-Hashcash: 1:20:070831:dow.street@linquest.com::kflDFGUIg3YV0Upq:000000000000000000000000000000000000001beZ
X-Hashcash: 1:20:070831:ipv6@ietf.org::WbpghBgYxYQ95vN9:00000V5o
X-Hashcash: 1:20:070831:narten@us.ibm.com::4INrSXqyWVhmcXw1:000000000000000000000000000000000000000000000jhh
X-Hashcash: 1:20:070831:brian.e.carpenter@gmail.com::oLxM5jJ5ZB+b05FE:00000000000000000000000000000000003JxF
X-Hashcash: 1:20:070831:itojun@itojun.org::473hOqJNTUibbRdh:00000000000000000000000000000000000000000000BtBX
Date: Fri, 31 Aug 2007 09:35:51 +0200
In-Reply-To: <F9D764D2-D560-44AB-B3A3-F3F257895A18@linquest.com> (Dow Street's
	message of "Thu, 30 Aug 2007 17:15:26 -0700")
Message-ID: <873ay0noko.fsf@natisbad.org>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.95 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: -1.4 (-)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc: Thomas Narten <narten@us.ibm.com>, IPv6 WG <ipv6@ietf.org>,
	Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Hi,

Dow Street <dow.street@linquest.com> writes:

> On Aug 30, 2007, at 2:40 PM, Arnaud Ebalard wrote:
>
>>> In your opinion, is it sufficient to describe potential uses of an
>>> IPv6 source routing mechanism?  Or is it also necessary to have the
>>> commitment of a large organization / commercial entity who intends to
>>> deploy IPv6 source routing in a specific timeframe and according to a
>>> specific use?
>>
>> No. IMHO, if someone comes with a good idea and other people find it
>> useful and want to have that in their laptop/network/pda/phone ... it
>> seems you have support and should start working on it.
>
> Is that "no" to the first or second question?

Respectively, the answers are "necessary" and "no".


>> In that particular case, people put the most powerful source routing
>> mechanism in the specification, which then got implemented on all
>> routers and even some hosts.
>
> Do you mean the case of RH0?

Yes.


>> During the _huge_ threads after CanSecWest during the discussions on
>> the
>> ietf ML, we asked many times if someone had a use or had already used
>> it.
>>
>> I can remember one person who knew someone that uses the mechanism for
>> some firewalling stuff (correct me if i'm wrong). I don't remember
>> if I
>> asked about the tools that allowed to use RH0: I know only ping6 and
>> scapy6 (again, correction appreciated).
>>
>> What i try to show is that the mechanism has been _proven_ useless
>> by a
>> past decade of full availability: you can bearly find users and tools
>> (at least on IETF IPv6 WG ML).
>
> RH0 may have been fully available from the perspective of IPv6
> implementations, but given the limited deployment of IPv6, I don't
> think lack of current use is *proof* that IPv6 RH0 is not useful, or
> would not be useful in the future.

It's not useful, it's funny and dangerous, hence the deprecation. At
some point, you will probably come to the conclusion that having a
source routing mechanism that does not potentially hinder others
requires that (at the very least) :

1) The forwarding routers trust you for providing them a new target
   (destination) for the packet and are ok spending time in slow path
   doing that.

2) The destination is ok with receiving source-routed traffic: note that
   this is not what 2460 mandates (i.e. RH* extension header with 0
   value in segleft should simply be skipped to process the next
   header, w.r.t. the specification). But this is how serious people
   handle RH0 (and future RH* traffic) on end entities (except for
   those for which you have a local need, like RH2 or yours).
   
   Best example is what the ISC has done for F Root DNS instances: try
   and send requests to them including RH0. It will be dropped.

As a conclusion, having RH* deployed requires to have _processing_ of
RH* performed by consenting routers, and that the packets end up on a
consenting host. The other routers will simply forward traffic based on
IPv6 header content. Other hosts will simply drop the traffic. (Please,
note the use of hosts and routers in previous sentences).

And yes, this limits your ability to bounce your traffic on every router
in the internet but this will obviously be the case (if not already
from threads on v6ops) as soon as operators get their IPv6 BCP in sync
with the IPv4 ones, i.e. as soon as "no ipv6 source route" is the
default or is forced by admins. 

Cheers,

a+

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



From ipv6-bounces@ietf.org Fri Aug 31 05:24:59 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IR2iM-00073F-Sl; Fri, 31 Aug 2007 05:22:54 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IR2iM-000736-5w
	for ipv6@ietf.org; Fri, 31 Aug 2007 05:22:54 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IR2iK-0006Ui-Kd
	for ipv6@ietf.org; Fri, 31 Aug 2007 05:22:54 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 2E8FF198662;
	Fri, 31 Aug 2007 12:22:51 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id D9D3219865A;
	Fri, 31 Aug 2007 12:22:50 +0300 (EEST)
Message-ID: <46D7DDEB.6040701@piuha.net>
Date: Fri, 31 Aug 2007 12:22:51 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.13 (X11/20070824)
MIME-Version: 1.0
To: Dow Street <dow.street@linquest.com>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>	<46D5D148.6080701@gmail.com>	<20070830084658.GA241@cs.uni-bonn.de>
	<46D72930.3020402@gmail.com>	<77736C78-4837-4949-A732-9137504DEE6A@linquest.com>	<46D740C9.1050103@gmail.com>
	<F8DF4E6C-42FB-4B42-9B2A-42D68076E324@linquest.com>
In-Reply-To: <F8DF4E6C-42FB-4B42-9B2A-42D68076E324@linquest.com>
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: 9182cfff02fae4f1b6e9349e01d62f32
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Dow,

> - If a "consenting nodes only" model is adopted, is any arbitrary
> behavior by those consenting nodes deemed acceptable by the
> non-consenting nodes?  Previous discussions seemed to indicate that at
> least some folks would answer "no" to this question.
>
> In other words, how is using RH 253 between consenting nodes (allowed
> to behave arbitrarily) any different than allowing consenting nodes to
> run RH0, and non-consenting nodes disabling RH0?  One difference
> (cynical hat on) is that opponents of source routing now force
> proponents to get new functionality implemented and deployed - only to
> have the same debate a few years from now when it comes time to
> standardize the functionality.
>
I think any proposal for special re-forwarding to new destination,
based on RH0, RHx, or anything else would have to be evaluated
by its merits. Some of the questions that would be asked in
review include, for instance, how is consent obtained from
the participants obtained, and how can the consenting nodes
ensure that they are not used as part of an attack (e.g.,
amplification).

Jari


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



From ipv6-bounces@ietf.org Fri Aug 31 11:14:41 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IR8AB-0003oe-9r; Fri, 31 Aug 2007 11:11:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IR8AA-0003jw-0O
	for ipv6@ietf.org; Fri, 31 Aug 2007 11:11:58 -0400
Received: from smtp167.iad.emailsrvr.com ([207.97.245.167])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IR8A8-0000Gm-Qp
	for ipv6@ietf.org; Fri, 31 Aug 2007 11:11:57 -0400
Received: by relay6.relay.iad.emailsrvr.com (Authenticated sender:
	dow.street-AT-linquest.com) with ESMTP id 2C4A36A9883; 
	Fri, 31 Aug 2007 11:11:55 -0400 (EDT)
In-Reply-To: <46D7DDEB.6040701@piuha.net>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>	<46D5D148.6080701@gmail.com>	<20070830084658.GA241@cs.uni-bonn.de>
	<46D72930.3020402@gmail.com>	<77736C78-4837-4949-A732-9137504DEE6A@linquest.com>	<46D740C9.1050103@gmail.com>
	<F8DF4E6C-42FB-4B42-9B2A-42D68076E324@linquest.com>
	<46D7DDEB.6040701@piuha.net>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <3CE2E174-7B18-4344-B4E4-00092B11A447@linquest.com>
Content-Transfer-Encoding: 7bit
From: Dow Street <dow.street@linquest.com>
Date: Fri, 31 Aug 2007 08:11:39 -0700
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: IPv6 WG <ipv6@ietf.org>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Aug 31, 2007, at 2:22 AM, Jari Arkko wrote:

>> - If a "consenting nodes only" model is adopted, is any arbitrary
>> behavior by those consenting nodes deemed acceptable by the
>> non-consenting nodes?  Previous discussions seemed to indicate  
>> that at
>> least some folks would answer "no" to this question.
>>
>> In other words, how is using RH 253 between consenting nodes (allowed
>> to behave arbitrarily) any different than allowing consenting  
>> nodes to
>> run RH0, and non-consenting nodes disabling RH0?  One difference
>> (cynical hat on) is that opponents of source routing now force
>> proponents to get new functionality implemented and deployed -  
>> only to
>> have the same debate a few years from now when it comes time to
>> standardize the functionality.
>>
> I think any proposal for special re-forwarding to new destination,
> based on RH0, RHx, or anything else would have to be evaluated
> by its merits. Some of the questions that would be asked in
> review include, for instance, how is consent obtained from
> the participants obtained, and how can the consenting nodes
> ensure that they are not used as part of an attack (e.g.,
> amplification).
>
> Jari

Thanks, Jari.

I was also speaking mostly about the functional aspects of the  
mechanism, not the policy aspect.  I suppose when the IETF publishes  
an RFC (or decides not to deprecate one), it essentially 1. endorses  
the described functionality and 2. implies that potentially negative  
consequences that could arise if the functionality were widely  
deployed have been considered.  Using RH 253 among consenting nodes  
allows the IETF as a body to remain silent on the merits and  
potentially negative consequences of that particular mechanism /  
use.  That is a difference.

Of course, in this case the deprecation of RH0 essentially  
establishes a position on both RH0 and sufficiently similar  
functionality.  It is sort of like case law, with the RH0 deprecation  
draft as the legal opinion.  I think this is partly why folks were so  
interested that the text in the RH0 deprecation draft focus on the  
single issue of most concern (e.g. oscillation DoS), rather than the  
merits of source routing in general.

Is this consistent with your thinking?

Thanks,
Dow

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



From ipv6-bounces@ietf.org Fri Aug 31 11:42:25 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IR8bn-0005ub-Bs; Fri, 31 Aug 2007 11:40:31 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IR8bl-0005uG-7T; Fri, 31 Aug 2007 11:40:29 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1IR8bk-0001cE-Qt; Fri, 31 Aug 2007 11:40:29 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-1.cisco.com with ESMTP; 31 Aug 2007 11:40:28 -0400
X-IronPort-AV: i="4.19,331,1183348800"; 
	d="scan'208"; a="69740010:sNHT70083832"
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 l7VFeSh7001125; 
	Fri, 31 Aug 2007 11:40:28 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l7VFe6MJ008915; 
	Fri, 31 Aug 2007 15:40: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); 
	Fri, 31 Aug 2007 11:40: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
Date: Fri, 31 Aug 2007 11:40:19 -0400
Message-ID: <B00EDD615E3C5344B0FFCBA910CF7E1D039DC361@xmb-rtp-20e.amer.cisco.com>
In-Reply-To: <4694F752.8090406@ericsson.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Fwd: WGLC for draft-ietf-dna-protocol-06.txt]
Thread-Index: AcfD0J5rK0240mUVSa+wcH+2tni9PwoE7nYA
References: <4694F752.8090406@ericsson.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "Suresh Krishnan" <suresh.krishnan@ericsson.com>, <ipv6@ietf.org>,
	<netlmm@ietf.org>, <mobopts@ietf.org>, <nemo@ietf.org>
X-OriginalArrivalTime: 31 Aug 2007 15:40:24.0469 (UTC)
	FILETIME=[3F423450:01C7EBE5]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1897; t=1188574828;
	x=1189438828; 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[Fwd=3A=20WGLC=20for=20draft-ietf-dna-protocol-06.txt
	] |Sender:=20
	|To:=20=22Suresh=20Krishnan=22=20<suresh.krishnan@ericsson.com>,
	=20<ipv6@
	ietf.org>, =0A=20=20=20=20=20=20=20=20<netlmm@ietf.org>,
	=20<mobopts@ietf.or g>,=20<nemo@ietf.org>;
	bh=CjPs8aGRR3ESWeeCvQKf/RHwDmHQFphA3ImNa+FXIVk=;
	b=FDL0rHhWzf6QrEnbTg1CG0NPBss5hdiriNVPWNiNGs4XYm4CazMufddO8hFMhMPQe9DtwWwK
	Wt5oS/IB/ciZYrJqDpMUDbrKVC6FpkmzABEN3AAj2oQ0VW0xkxL/+DnI;
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: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Cc: 
Subject: RE: [Fwd: WGLC for draft-ietf-dna-protocol-06.txt]
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Suresh,

I have few minor comments on this I-D. Wes Beebee will send more
detailed comments sometime later today. He has reviewed the I-D.

1. While reading the Abstract, I'd like to know what is the maximum
delay DNAv6 is ready to accept in a response from router? =20
2. Stateful has been deprecated for use. We should call it DHCPv6.
Therefore section 5.2.7 should change statefully to DHCPv6.

Hemant

-----Original Message-----
From: Suresh Krishnan [mailto:suresh.krishnan@ericsson.com]=20
Sent: Wednesday, July 11, 2007 11:29 AM
To: ipv6@ietf.org; netlmm@ietf.org; mobopts@ietf.org; nemo@ietf.org
Subject: [Fwd: WGLC for draft-ietf-dna-protocol-06.txt]

Hi Folks,
   We would like to hear your comments on this document as well. This
document is a significant update to ipv6 neighbor discovery and we would
like some more eyeballs. Please spare some time from your busy schedule
to give it a look.

Thanks
Suresh

-------- Original Message --------
Subject: WGLC for draft-ietf-dna-protocol-06.txt
Date: Wed, 04 Jul 2007 15:47:24 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Dna <dna@eng.monash.edu.au>
CC: Greg Daley <Greg.Daley@eng.monash.edu.au>,  Jari Arkko
<jari.arkko@piuha.net>

This mail starts a 2 week working group Last Call for comments for the
following dna working group document

draft-ietf-dna-protocol-06.txt

to be sent to the IESG for consideration as a Standards Track RFC.

Please review the document carefully, and send your feedback to the
list. Please also indicate whether or not you believe that this document
is ready to go to the IESG.

The last call will end on 2007/07/18.

Cheers
Suresh & Greg


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

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



From ipv6-bounces@ietf.org Fri Aug 31 14:22:38 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IRB6j-0001SA-HH; Fri, 31 Aug 2007 14:20:37 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IRB6h-0001Ea-PP; Fri, 31 Aug 2007 14:20:35 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IRB6g-0007HS-Fg; Fri, 31 Aug 2007 14:20:35 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159])
	by rtp-iport-1.cisco.com with ESMTP; 31 Aug 2007 14:20:10 -0400
X-IronPort-AV: i="4.20,193,1186372800"; 
	d="scan'208"; a="69777534:sNHT65952275316"
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 l7VIK92Y023542; 
	Fri, 31 Aug 2007 14:20:09 -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 l7VIK25m011743; 
	Fri, 31 Aug 2007 18:20:02 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); 
	Fri, 31 Aug 2007 14:19: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
Date: Fri, 31 Aug 2007 14:20:47 -0400
Message-ID: <CA8EB93B28BD0F4C88392699600BD655042A4729@xmb-rtp-211.amer.cisco.com>
In-Reply-To: <B00EDD615E3C5344B0FFCBA910CF7E1D039DC361@xmb-rtp-20e.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Fwd: WGLC for draft-ietf-dna-protocol-06.txt]
Thread-Index: AcfD0J5rK0240mUVSa+wcH+2tni9PwoE7nYAAAO5fiA=
From: "Wes Beebee \(wbeebee\)" <wbeebee@cisco.com>
To: "Hemant Singh \(shemant\)" <shemant@cisco.com>,
	"Suresh Krishnan" <suresh.krishnan@ericsson.com>, <ipv6@ietf.org>,
	<netlmm@ietf.org>, <mobopts@ietf.org>, <nemo@ietf.org>
X-OriginalArrivalTime: 31 Aug 2007 18:19:55.0756 (UTC)
	FILETIME=[8830B2C0:01C7EBFB]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5919; t=1188584409;
	x=1189448409; c=relaxed/simple; s=rtpdkim2001;
	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[Fwd=3A=20WGLC=20for=20draft-ietf-dna-protocol-06.txt
	] |Sender:=20
	|To:=20=22Hemant=20Singh=20\(shemant\)=22=20<shemant@cisco.com>,
	=0A=20=20
	=20=20=20=20=20=20=22Suresh=20Krishnan=22=20<suresh.krishnan@ericsson.com>
	, =20<ipv6@ietf.org>, =0A=20=20=20=20=20=20=20=20<netlmm@ietf.org>,
	=20<mobop ts@ietf.org>,=20<nemo@ietf.org>;
	bh=jjWtRWiutsvwaXHV/ZxQzqj6hGQKOgKIMrCHOaFN8Rw=;
	b=afktPId0/o+15T1JFBxz5vI369qZY1xJ/lwrd3zJELKZybqxpBnJerj1R2hUhgAjYytaKa2M
	vBJf9Mg69sZSHVSExpKyx8te94KW2bT6DIC5kG5+qytHSwaLSUkhvLLv;
Authentication-Results: rtp-dkim-2; header.From=wbeebee@cisco.com; dkim=pass (
	sig from cisco.com/rtpdkim2001 verified; ); 
X-Spam-Score: -3.7 (---)
X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8
Cc: 
Subject: RE: [Fwd: WGLC for draft-ietf-dna-protocol-06.txt]
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Here's my review of the DNA I-D:

One global concern:=20
I'm concerned that DNA may not be applicable to all networks.  There
seems to be some=20
implicit assumptions about the networks that must be true - and these
assumptions are
not necessarily going to be true on all of the networks that DNA seems
to be targeting.
In cases where DNA cannot automatically determine that the host is in
such a network,=20
it should be possible to turn DNA off manually and resort to old-style
ND.

Specific concerns:
1) What track is this Internet Draft on - Standards?
2) I'm concerned about two major deployment scenarios, each of which is
likely to affect millions of subscribers
   off of the same aggregation router:
   a) The router offers no PIO in the RA - thus, no prefix is available.
This is currently being=20
      discussed as a possible way to prevent poorly implemented host
stacks which ignore the M and A bits=20
      in the RA from doing SLAAC and force them to do DHCPv6 or not get
online.  Unfortunately, this
      case breaks DNA as there is no prefix available to identify the
link.  The "at least one router
      on a link MUST be configured with one prefix" is a limitation of
DNA.
   b) The prefix for a neighborhood is the same for all access points in
the neighborhood.  This can happen
      if home users are off of bridge modems and they are all bridging
the same prefix (which is defined=20
      on a bundle interface of the aggregation router.  This is done to
conserve address space and simplify
      network configuration by MSO's.  Unfortunately, this means that
DNA will detect every AP in the neighborhood
      as the same link.  Even worse, when DNA causes the node not to do
DHCPv6 again, the aggregation router
      which understands which home corresponds to which addresses,
causes source verify to reject traffic
      from the roaming laptop.  What should happen is that the node
should try to do DHCPv6 again when it roams
      even when the prefix is the same - this doesn't work in DNA.
3) The routers being able to advertise a prefix list as complete assumes
that they know about all the routers on the link.
   However, one of the routers could be silent for a while, and a router
may assume that it knows all of the prefixes on
   the link but may be wrong.
4) "Any future non-prefix link identifier MUST be 128 bits long." - Why?
5) Are the MAX_RTR_SOLICITATIONS and RTR_SOLICITATION_INTERVAL chosen to
scale up to 100,000 hosts off of an=20
   aggregation router?  What if multiple interfaces startup at the same
time?  Will there be an RS storm and will
   the token bucket rate limiting cause RS's to be dropped as described
in the security considerations case?
   I suspect that this case may be even more common than you might
suspect...  You may have to adjust
   UNICAST_RA_INTERVAL and MAX_UNICAST_RA_BURST to deal with interface
bringups on the aggregation router.
6) "The router MUST pick the smallest prefix of all the prefixes
configured on the routers on the link as the
    common prefix."  What if there are 2 smallest prefixes?
7) "an absence of that overlap can be used to infer link change" in
5.1.8 is repeated again in 5.1.9, and 5.1.9.1 - please
   eliminate redundancy.
8) In 5.2.6.1, one of the IF statements is missing - "{ Link change has
occurred. RETURN; }" but no IF, and occurred is
   spelled wrong.
9) Why do you need to infer upstream reachability?

- Wes

-----Original Message-----
From: Hemant Singh (shemant)=20
Sent: Friday, August 31, 2007 11:40 AM
To: Suresh Krishnan; ipv6@ietf.org; netlmm@ietf.org; mobopts@ietf.org;
nemo@ietf.org
Subject: RE: [Fwd: WGLC for draft-ietf-dna-protocol-06.txt]

Suresh,

I have few minor comments on this I-D. Wes Beebee will send more
detailed comments sometime later today. He has reviewed the I-D.

1. While reading the Abstract, I'd like to know what is the maximum
delay DNAv6 is ready to accept in a response from router? =20
2. Stateful has been deprecated for use. We should call it DHCPv6.
Therefore section 5.2.7 should change statefully to DHCPv6.

Hemant

-----Original Message-----
From: Suresh Krishnan [mailto:suresh.krishnan@ericsson.com]
Sent: Wednesday, July 11, 2007 11:29 AM
To: ipv6@ietf.org; netlmm@ietf.org; mobopts@ietf.org; nemo@ietf.org
Subject: [Fwd: WGLC for draft-ietf-dna-protocol-06.txt]

Hi Folks,
   We would like to hear your comments on this document as well. This
document is a significant update to ipv6 neighbor discovery and we would
like some more eyeballs. Please spare some time from your busy schedule
to give it a look.

Thanks
Suresh

-------- Original Message --------
Subject: WGLC for draft-ietf-dna-protocol-06.txt
Date: Wed, 04 Jul 2007 15:47:24 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Dna <dna@eng.monash.edu.au>
CC: Greg Daley <Greg.Daley@eng.monash.edu.au>,  Jari Arkko
<jari.arkko@piuha.net>

This mail starts a 2 week working group Last Call for comments for the
following dna working group document

draft-ietf-dna-protocol-06.txt

to be sent to the IESG for consideration as a Standards Track RFC.

Please review the document carefully, and send your feedback to the
list. Please also indicate whether or not you believe that this document
is ready to go to the IESG.

The last call will end on 2007/07/18.

Cheers
Suresh & Greg


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

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

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



From ipv6-bounces@ietf.org Fri Aug 31 15:23:44 2007
Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IRC3c-0002pT-6s; Fri, 31 Aug 2007 15:21:28 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IRC3b-0002pN-91
	for ipv6@ietf.org; Fri, 31 Aug 2007 15:21:27 -0400
Received: from elvis.mu.org ([192.203.228.196])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IRC3a-0000hi-O5
	for ipv6@ietf.org; Fri, 31 Aug 2007 15:21:27 -0400
Received: by elvis.mu.org (Postfix, from userid 1098)
	id 5070E1A4D80; Fri, 31 Aug 2007 12:18:48 -0700 (PDT)
Date: Fri, 31 Aug 2007 12:18:48 -0700
From: bill fumerola <billf@mu.org>
To: IPv6 WG <ipv6@ietf.org>
Message-ID: <20070831191848.GC42834@elvis.mu.org>
References: <77ead0ec0708280131q74d7041fod779e907b589b3d@mail.gmail.com>
	<200708291408.l7TE8eJO029246@cichlid.raleigh.ibm.com>
	<77ead0ec0708291757m28328d76m85f262036d54040a@mail.gmail.com>
	<200708301253.l7UCrT2J027846@cichlid.raleigh.ibm.com>
	<46D775DE.3080701@uninett.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46D775DE.3080701@uninett.no>
User-Agent: Mutt/1.4.2.3i
X-Operating-System: FreeBSD 6.2-MUORG-20070725 amd64
X-PGP-Key: 1024D/7F868268
X-PGP-Fingerprint: 5B2D 908E 4C2B F253 DAEB  FC01 8436 B70B 7F86 8268
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: Stig Venaas <stig.venaas@uninett.no>
Subject: Re: New Routing Header!!!
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>,
	<mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

On Fri, Aug 31, 2007 at 03:58:54AM +0200, Stig Venaas wrote:
> I'm not arguing for keeping source routing here, but one quite useful
> thing it can be used for is traceroute. You can for instance trace from
> a remote point in the network towards yourself. This can be very helpful
> when debugging routing problems.

engineers also can use it when setting up, debugging, or for periodic
testing of peering sessions to make sure that the other side isn't doing
anything against the contractual terms of the peer (e.g. overriding the
normal policies that result from standard RIB->FIB route selection).

examples:
http://ptd.mbo.ma.rcn.net/peerinfo/

All peers are requested to enable LSRR on router interfaces facing RCN
peering sessions to facilitate network diagnostics at least during session
activation.

http://www.via.net/support/support_peer.html 
We require that our peers permit LSR, loose source routing, at least at the border.

http://www.noc.wiscnet.net/peering/
We require that our peers permit LSR, loose source routing, at least at
the border for diagnostic purposes.

i don't have an ACM account, but:
http://portal.acm.org/citation.cfm?coll=GUIDE&dl=GUIDE&id=1016718

without comparable functionality in IPv6, we lose a feature actively in
use (through IPv4) by some networks for verification of proper peering.

if i'm out of touch with current policies on peering & LSRR, please let
me know. sure, diehards of the end-to-end principle certainly believe
that removing source routing is an assult on said principle[1]. there
are other uses for source routing in some form, beyond e2e, that is
helpful.

-- bill

1. http://www.postel.org/pipermail/end2end-interest/2007-May/006711.html

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



