IETF Logo Mail Archive

Re: [dhcwg] Informational IPv6 prefix option for DHCPv6

Andre Kostur <akostur@incognito.com> Mon, 07 July 2014 18:22 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 E3B2E1A03C0 for <dhcwg@ietfa.amsl.com>; Mon, 7 Jul 2014 11:22:48 -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 ff_tavzAMEJe for <dhcwg@ietfa.amsl.com>; Mon, 7 Jul 2014 11:22:47 -0700 (PDT)
Received: from na3sys010aog102.obsmtp.com (na3sys010aog102.obsmtp.com [74.125.245.72]) by ietfa.amsl.com (Postfix) with SMTP id 408341A02D5 for <dhcwg@ietf.org>; Mon, 7 Jul 2014 11:22:47 -0700 (PDT)
Received: from mail-ve0-f173.google.com ([209.85.128.173]) (using TLSv1) by na3sys010aob102.postini.com ([74.125.244.12]) with SMTP ID DSNKU7rlduhh2E0QEZj+o8PFj2iwflWkk+Ld@postini.com; Mon, 07 Jul 2014 11:22:47 PDT
Received: by mail-ve0-f173.google.com with SMTP id db11so4453514veb.4 for <dhcwg@ietf.org>; Mon, 07 Jul 2014 11:22:46 -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=n/gn2Zm+HR8mhmTsMkvcQoD4qwELvjv7s4/cLPpN8tU=; b=Op6EpnYbNR1iXppnLsvHdRVo6k+iYKnPSeQ2VbIf+R9san2XK3o8i+op2VCQdGLJqn vAABvce1kI13W8A8JmsrBmifG0Sc0hfNmduFE4VAjQSuOeZK4eWmPgmuye40aSKCUFzx ulxf6sF1q2e/CcpsHA2J8XmePueVItGVah+5p8BoESrRqPQSFHtBOvacX5q8H0/TuXn6 F3Z2gvd+IrqYLlUUMwvG7Mhz8yCuQCZES7LegT+iTQjW+02P/PPvWbPReXJwXsubbdXn fI4DVexiwIf1IXoBZVLyVFHp2zpCA80YslRdEbAiX+EppSSgA00MqtcTF+00oRu/d2Dz 1zXw==
X-Gm-Message-State: ALoCoQk/g0bygEDX440699K6XzX5X5qnbfOavA12kJprGDVGS3fdAOyqQWDFgS8ScmWlZSbc4gDxcBGycLqko1fdgbl8qaO9oNFLp5KQt2S0lf64kpfHYd51KLB4kX2T9XFVYp9OGEre
X-Received: by 10.58.69.76 with SMTP id c12mr14160278veu.35.1404757366254; Mon, 07 Jul 2014 11:22:46 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.58.69.76 with SMTP id c12mr14160271veu.35.1404757366162; Mon, 07 Jul 2014 11:22:46 -0700 (PDT)
Received: by 10.220.147.79 with HTTP; Mon, 7 Jul 2014 11:22:46 -0700 (PDT)
In-Reply-To: <2134F8430051B64F815C691A62D9831832CB79A3@XCH-BLV-505.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D9831832CB79A3@XCH-BLV-505.nw.nos.boeing.com>
Date: Mon, 07 Jul 2014 11:22:46 -0700
Message-ID: <CAL10_Bq8e2DwETCNcdTzwAEsWpA46SJbj-yc3hfjePhyQ0XO=A@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/JmwljJSREkw6l17XCIrLqm9t_Ic
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:22:49 -0000

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