Re: IPv6 PD

<timbeck04@verizon.net> Tue, 25 July 2006 11:42 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5LJ8-0001pT-Jb; Tue, 25 Jul 2006 07:42:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G5LJ7-0001pM-A8 for ipv6@ietf.org; Tue, 25 Jul 2006 07:42:37 -0400
Received: from vms040pub.verizon.net ([206.46.252.40]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G5LJ4-0004Ba-UK for ipv6@ietf.org; Tue, 25 Jul 2006 07:42:37 -0400
Received: from vms076.mailsrvcs.net ([192.168.1.1]) by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0J2Y00GA9J6QFOB1@vms040.mailsrvcs.net> for ipv6@ietf.org; Tue, 25 Jul 2006 06:42:26 -0500 (CDT)
Received: from 129.55.200.20 ([129.55.200.20]) by vms076.mailsrvcs.net (Verizon Webmail) with HTTP; Tue, 25 Jul 2006 06:42:26 -0500 (CDT)
Date: Tue, 25 Jul 2006 06:42:26 -0500
From: timbeck04@verizon.net
X-Originating-IP: [129.55.200.20]
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Iljitsch van Beijnum <iljitsch@muada.com>
Message-id: <1797980.1415131153827746544.JavaMail.root@vms076.mailsrvcs.net>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: IPv6 PD
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Errors-To: ipv6-bounces@ietf.org

Good morning all. AFAIK, there is currently no defined way (other than via DHCPv6) to do IPv6 PD. It may well be that between a PE and CE, DHCPv6 is neither required nor desired, but PD is. 

Over the past twelve months or so there has been some interest in ICMPv6 PD expressed to me. I'm considering submitting a related draft, and seeking a co-author. Kindly reply off-line.

Best Regards,

Tim Enos
1Sam16:7

>From: timbeck04@verizon.net
>Date: 2006/07/24 Mon PM 09:06:49 CDT
>To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, 
	Iljitsch van Beijnum <iljitsch@muada.com>
>Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
>Subject: IPv6 PD

>Hi Fred/all,
>
>The former subject line became far too unwieldy, and the subject of IPv6 referred to in the attached exchange is of interest.
>
>IPv6 PD is between two routers, not a router and an end host. Using ISP parlance, the delegating router is the ISP PE (delegating) router and the requesting router is the CE router. 
>
>The abstract of RFC 3769 which defines the IPv6 PD requirements says: "This document describes requirements for how IPv6 address prefixes
>should be delegated to an IPv6 subscriber's network (or "site")." Section 1 echoes this point. It's logical to infer from Section 4 that the CPE is the requesting router (not host): "A rogue PE can issue bogus prefixes to a requesting router."
>
>Given the way RFC 3633 is written, there is reason to pre-suppose that the client will behave as a router. In DHCPv6 PD, the ISP router that serves as the DHCPv6 server is the delegating router. The CPE that serves as the DHCPv6 client is the requesting router (Section 3). Section 5.1 illustrates an example architecture wherein this is shown. The point is also made that the requesting router subnets whatever prefixes are delegated to it and assigns those longer prefixes to links within the subscriber network.
>
>a. There has neither ever been nor is there now a standard defining ICMPv6 PD. There are however at least three expired drafts (of which I am aware) on the subject:
>i) draft-haberman-ipngwg-auto-prefix-02.txt
>ii) draft-bykim-ipv6-hpd-01.txt
>iii) draft-arunt-prefix-delegation-using-icmpv6-00.txt
>b. There might need to be a separate ICMPv6 packet type defined by the IANA for ICMPv6 PD. Note that all three of the aforementioned drafts define at least one such type. None of these exist: icmpv6-parameters.
>
>
>>From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
>>Date: 2006/07/24 Mon PM 07:11:38 CDT
>>To: Iljitsch van Beijnum <iljitsch@muada.com>
>>Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
>>Subject: RE: Forward: Re: Last Call: 'IPv6 Router Advertisement OptionforDNS	Configuration' to	ExperimentalRFC(draft-jeong-dnsop-ipv6-dns-discovery)
>
>>> Prefix delegation is a feature used by routers, not by hosts.
>>
>>I don't understand this point as it relates to the question of
>>whether/not DHCPv6 will be needed, and the more I think about
>>it the more irrelevant it seems. Prefix delegation is a feature
>>used by clients of a prefix delegation server - in DHCPv6, they
>>are the DHCP client and DHCP server. What the client actually
>>*does* with any delegated prefixes is up to the client and
>>there is no reason to pre-suppose that it will necessarily
>>behave as a router.
>>
>>Again, the question is whether there is (or will be) a
>>way of doing prefix delegation w/o DHCPv6? (If so, would
>>it be any better than DHCPv6 - or just different?)
>>
>>Fred
>>fred.l.templin@boeing.com
>>
>>--------------------------------------------------------------------
>>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
--------------------------------------------------------------------