Re: [dhcwg] Informational IPv6 prefix option for DHCPv6
"Templin, Fred L" <Fred.L.Templin@boeing.com> Mon, 07 July 2014 19:44 UTC
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C98E1B28A5 for <dhcwg@ietfa.amsl.com>; Mon, 7 Jul 2014 12:44:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level:
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pcz2H8fT1c0I for <dhcwg@ietfa.amsl.com>; Mon, 7 Jul 2014 12:44:27 -0700 (PDT)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 894631A0A88 for <dhcwg@ietf.org>; Mon, 7 Jul 2014 12:44:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s67JiQYN020402; Mon, 7 Jul 2014 14:44:26 -0500
Received: from XCH-PHX-112.sw.nos.boeing.com (xch-phx-112.sw.nos.boeing.com [130.247.25.134]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s67JiKFu020365 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 7 Jul 2014 14:44:21 -0500
Received: from XCH-BLV-104.nw.nos.boeing.com (2002:82f7:1978::82f7:1978) by XCH-PHX-112.sw.nos.boeing.com (2002:82f7:1986::82f7:1986) with Microsoft SMTP Server (TLS) id 14.3.181.6; Mon, 7 Jul 2014 12:44:19 -0700
Received: from XCH-BLV-505.nw.nos.boeing.com ([169.254.5.55]) by XCH-BLV-104.nw.nos.boeing.com ([169.254.4.243]) with mapi id 14.03.0181.006; Mon, 7 Jul 2014 12:44:19 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Andre Kostur <akostur@incognito.com>
Thread-Topic: [dhcwg] Informational IPv6 prefix option for DHCPv6
Thread-Index: Ac+aDIcGSEduQ/YyTKOMsGQeKGSdbAAPpiMAAA3A+WD//6QLAIAAdDfg
Date: Mon, 07 Jul 2014 19:44:18 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832CB7B59@XCH-BLV-505.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D9831832CB79A3@XCH-BLV-505.nw.nos.boeing.com> <CAL10_Bq8e2DwETCNcdTzwAEsWpA46SJbj-yc3hfjePhyQ0XO=A@mail.gmail.com> <2134F8430051B64F815C691A62D9831832CB7ACC@XCH-BLV-505.nw.nos.boeing.com> <CAL10_Bo0efKP-tv66R41iqoUrc2=8e2e52JBDb-Ga30VvBwKMg@mail.gmail.com>
In-Reply-To: <CAL10_Bo0efKP-tv66R41iqoUrc2=8e2e52JBDb-Ga30VvBwKMg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/u3JcsvWAiWkIDBK_T7Br9W7VZU0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Informational IPv6 prefix option for DHCPv6
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jul 2014 19:44:29 -0000
Hi Andre, > -----Original Message----- > From: Andre Kostur [mailto:akostur@incognito.com] > Sent: Monday, July 07, 2014 12:27 PM > To: Templin, Fred L > Cc: dhcwg@ietf.org > Subject: Re: [dhcwg] Informational IPv6 prefix option for DHCPv6 > > Then I'm not sure of the purpose of this information. The client got > an IPv6 address from somewhere, so it should be able to know its > prefix from that. What's the client supposed to do with this > information that it's getting from DHCP? It is for a link type on which there is no non-link-local IPv6 prefix assigned. The link connects a bunch of routers that only configure a link-local address on the link. The routers also act as DHCPv6 clients, and act as requesting routers using DHCPv6 PD to get a prefix to assign to their downstream attached links. The IPv6 prefix I want to include in the DHCPv6 option I am asking for is the aggregated prefix from which client prefixes are delegated. So, if the aggregated prefix is 2001:db8::/32, then the clients would be delegated longer prefixes such as 2001:db8:4000::/48, 2001:db8:1::/56, 2001:db8:21:31::/64, etc. So, the aggregated prefix is not assigned *to* the link, but rather tells the set of prefixes that can be reached *through* the link. This is important information that I want to provide to the clients via a DHCPv6 option. Thanks - Fred fred.l.templin@boeing.com > On Mon, Jul 7, 2014 at 11:52 AM, Templin, Fred L > <Fred.L.Templin@boeing.com> wrote: > > Hi Andre, > > > > No, this is not Prefix Delegation. For PD, the DHCPv6 server > > returns an IPv6 prefix that the client then uses to number its > > downstream-attached links. What I want is an informational > > option that pertains to the link over which the client contacts > > the server, and to my understanding PD cannot be used for that. > > > > Thanks - Fred > > fred.l.templin@boeing.com > > > >> -----Original Message----- > >> From: Andre Kostur [mailto:akostur@incognito.com] > >> Sent: Monday, July 07, 2014 11:23 AM > >> To: Templin, Fred L > >> Cc: dhcwg@ietf.org > >> Subject: Re: [dhcwg] Informational IPv6 prefix option for DHCPv6 > >> > >> Isn't that Prefix Delegation? RFC 3633. Nutshell is that the client > >> can specifically ask the server for a prefix. Part of the plan is for > >> routers deployed out at the edge, and they can ask the DHCP server for > >> a prefix that the router will then manage on its further downstream > >> links. > >> > >> On Mon, Jul 7, 2014 at 10:54 AM, Templin, Fred L > >> <Fred.L.Templin@boeing.com> wrote: > >> > Hi, > >> > > >> > I am looking for a DHCPv6 option that a server can use to report an IPv6 > >> > prefix to a client. This *would not* be used as a replacement for Router > >> > Advertisement Prefix Information Options (PIOs), and the client *would > >> > not* use the prefix for SLAAC. > >> > > >> > A DHCPv6 option that specifically returned an IPv6 prefix (along with > >> > prefix length) would be preferred. A DHCPv6 option that returned opaque > >> > data could also be used as a kludge but I would rather not have to do > >> > that. Is there a DHCPv6 option that would meet these requirements? > >> > > >> > Thanks - Fred > >> > fred.l.templin@boeing.com > >> > > >> > _______________________________________________ > >> > dhcwg mailing list > >> > dhcwg@ietf.org > >> > https://www.ietf.org/mailman/listinfo/dhcwg > >> > >> > >> > >> -- > >> Andre Kostur > > -- > Andre Kostur
- [dhcwg] Informational IPv6 prefix option for DHCP… Templin, Fred L
- Re: [dhcwg] Informational IPv6 prefix option for … Andre Kostur
- Re: [dhcwg] Informational IPv6 prefix option for … Andre Kostur
- Re: [dhcwg] Informational IPv6 prefix option for … Templin, Fred L
- Re: [dhcwg] Informational IPv6 prefix option for … Templin, Fred L
- Re: [dhcwg] Informational IPv6 prefix option for … Bernie Volz (volz)
- Re: [dhcwg] Informational IPv6 prefix option for … Templin, Fred L
- Re: [dhcwg] Informational IPv6 prefix option for … Bernie Volz (volz)
- Re: [dhcwg] Informational IPv6 prefix option for … Templin, Fred L
- Re: [dhcwg] Informational IPv6 prefix option for … Bernie Volz (volz)
- Re: [dhcwg] Informational IPv6 prefix option for … Templin, Fred L