IETF Logo Mail Archive

Re: [dhcwg] Informational IPv6 prefix option for DHCPv6

Andre Kostur <akostur@incognito.com> Mon, 07 July 2014 19:27 UTC

Return-Path: <akostur@incognito.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 16B0F1B2870 for <dhcwg@ietfa.amsl.com>; Mon, 7 Jul 2014 12:27:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.579
X-Spam-Level:
X-Spam-Status: No, score=-3.579 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-2.3, 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 WF62C6lnS498 for <dhcwg@ietfa.amsl.com>; Mon, 7 Jul 2014 12:27:30 -0700 (PDT)
Received: from na3sys010aog105.obsmtp.com (na3sys010aog105.obsmtp.com [74.125.245.78]) by ietfa.amsl.com (Postfix) with SMTP id 34B9F1B286D for <dhcwg@ietf.org>; Mon, 7 Jul 2014 12:27:29 -0700 (PDT)
Received: from mail-vc0-f179.google.com ([209.85.220.179]) (using TLSv1) by na3sys010aob105.postini.com ([74.125.244.12]) with SMTP ID DSNKU7r0oSGbrZap3wuC0NLM3wi6XugjUKCy@postini.com; Mon, 07 Jul 2014 12:27:30 PDT
Received: by mail-vc0-f179.google.com with SMTP id id10so4404690vcb.38 for <dhcwg@ietf.org>; Mon, 07 Jul 2014 12:27:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Hz5NH+FiOPd3Ciq3qGPcZ5AXKImPEJUbXLRyNSOB3nY=; b=WERGx+rtGyj1J72AuFQ2wC0XFaWLuVDH0aIoLrPkreLMjUYWwv2jpw5b1Rn6o62SWu 70VynOBc+TZzwp9OjReUa2lLTAz9nb47mD/pzP90E4V+jDLOLInS4whufM3ryagLwGvx CTH9TOi7vt8KI1LLBqUJE4/R+71HSNejml/6lcUX0esFe7VT6BXLIJuNlTMeQXhfsdEK eiMlG20a4rImU+JtjoOdqZIVJyFMPvOdAzqK3No89XrVxUuuRo12hGVuMDVn9so17itI hp+K33SJmhGNvsxOhlHzOW8Qb5jnVC7Sqb+YieBKgaZZlYCpySyZbzwxCNbubzLij9Ay rRTQ==
X-Gm-Message-State: ALoCoQkPamQlW9UxqBHp+4ZBo2d38jwPdPEPPFstVuI7gk7xDuLQATRSm3lOU0T3AnRwRsPK/bgVa2LO9nsAnJdSJJnZ06tzJbalUZEI5tvyYcMJak1OVaiGqMeyYhPXae6RxlVG4vli
X-Received: by 10.52.189.161 with SMTP id gj1mr24579221vdc.2.1404761249055; Mon, 07 Jul 2014 12:27:29 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.52.189.161 with SMTP id gj1mr24579216vdc.2.1404761248966; Mon, 07 Jul 2014 12:27:28 -0700 (PDT)
Received: by 10.220.147.79 with HTTP; Mon, 7 Jul 2014 12:27:28 -0700 (PDT)
In-Reply-To: <2134F8430051B64F815C691A62D9831832CB7ACC@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>
Date: Mon, 07 Jul 2014 12:27:28 -0700
Message-ID: <CAL10_Bo0efKP-tv66R41iqoUrc2=8e2e52JBDb-Ga30VvBwKMg@mail.gmail.com>
From: Andre Kostur <akostur@incognito.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/hsgp1wFUvK5ekicB1GKJvsiRZBc
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:27:33 -0000

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?

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

v2.23.0 | Report a Bug | By Email