IETF Logo Mail Archive

Re: [dhcwg] Informational IPv6 prefix option for DHCPv6

"Templin, Fred L" <Fred.L.Templin@boeing.com> Mon, 07 July 2014 18:52 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 E48D91B285D for <dhcwg@ietfa.amsl.com>; Mon, 7 Jul 2014 11:52:32 -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 L0PzMuEyk2rj for <dhcwg@ietfa.amsl.com>; Mon, 7 Jul 2014 11:52:31 -0700 (PDT)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61B391B27ED for <dhcwg@ietf.org>; Mon, 7 Jul 2014 11:52:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s67IqUAu016922; Mon, 7 Jul 2014 11:52:30 -0700
Received: from XCH-PHX-210.sw.nos.boeing.com (xch-phx-210.sw.nos.boeing.com [130.247.25.65]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s67IqL4D016400 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 7 Jul 2014 11:52:22 -0700
Received: from XCH-BLV-408.nw.nos.boeing.com (2002:82f7:19a6::82f7:19a6) by XCH-PHX-210.sw.nos.boeing.com (2002:82f7:1941::82f7:1941) with Microsoft SMTP Server (TLS) id 14.3.181.6; Mon, 7 Jul 2014 11:52:21 -0700
Received: from XCH-BLV-505.nw.nos.boeing.com ([169.254.5.55]) by XCH-BLV-408.nw.nos.boeing.com ([169.254.8.228]) with mapi id 14.03.0181.006; Mon, 7 Jul 2014 11:52:21 -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+WA=
Date: Mon, 07 Jul 2014 18:52:21 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832CB7ACC@XCH-BLV-505.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D9831832CB79A3@XCH-BLV-505.nw.nos.boeing.com> <CAL10_Bq8e2DwETCNcdTzwAEsWpA46SJbj-yc3hfjePhyQ0XO=A@mail.gmail.com>
In-Reply-To: <CAL10_Bq8e2DwETCNcdTzwAEsWpA46SJbj-yc3hfjePhyQ0XO=A@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/vIJaeELuyl9D7jNc4N6Z_YbYY5I
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 18:52:33 -0000

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
> Distinguished Software Architect & Engineer
> P: 604-678-2864
> E: akostur@incognito.com
> Toll-Free: 1-800-877-1856
> 
> 
> F: 604-678-2864
> VoIP: sip:864@sip.incognito.com

v2.23.0 | Report a Bug | By Email