Re: [dhcwg] [homenet] PPP, DHCPv6 and Prefix Delegation

Jouni Korhonen <jouni.nospam@gmail.com> Tue, 19 November 2013 16:22 UTC

Return-Path: <jouni.nospam@gmail.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 432BE1AE071; Tue, 19 Nov 2013 08:22:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 e-O2YySbG3AO; Tue, 19 Nov 2013 08:22:48 -0800 (PST)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 7C7D01ADF70; Tue, 19 Nov 2013 08:22:47 -0800 (PST)
Received: by mail-wi0-f174.google.com with SMTP id fb10so1718524wid.1 for <multiple recipients>; Tue, 19 Nov 2013 08:22:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=TY7RFpYAqPVKhdieewYCxjra3u2evHw+2k03hC0+kMY=; b=WKwVZ0D2qhVNtl24npzBKpl9wz0jFjelUOXiaCd3+v+o8iPyNhg35IDP7stuFgGXbr hd0ZNUR34KJxhbrkBBqkBUIDFPUWnfrqUrlmXjGssSl1YYMA/xjb7CfZkV6zJBpL9pOe ucjH3H7w7S8bsRlrxilCC6Pp5YwV4VUAzJG4FPd4mLHja3sDy5p9jrc1EdA74q/86LrW /xz1QDUFoqTicON+0pIGkNzYR/jP7iSNAHGy8flSYoYJuUfnEjNNx6RJydsuchdcYuYB jzcbjteXf7Le8k8sVjmnNP5E73oy6bDK1MdC+lkel9xs1cCdUXDSyL3TTzOAG7ll2Aik UKfQ==
X-Received: by 10.180.160.240 with SMTP id xn16mr21493046wib.62.1384878160946; Tue, 19 Nov 2013 08:22:40 -0800 (PST)
Received: from [10.216.15.149] ([93.158.48.157]) by mx.google.com with ESMTPSA id uc12sm7089626wib.3.2013.11.19.08.22.39 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 19 Nov 2013 08:22:40 -0800 (PST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jouni Korhonen <jouni.nospam@gmail.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1AD9CDF7@xmb-rcd-x04.cisco.com>
Date: Tue, 19 Nov 2013 18:22:49 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B10FDF95-9612-4DD7-8C3E-9361CCBCA4E3@gmail.com>
References: <11836.1384276281@sandelman.ca> <CAKOT5Ko2OO=U_0jADb6R88JiFh59BLDSe4P0haqgaBr2M7HobA@mail.gmail.com> <3673.1384528283@sandelman.ca> <CAKOT5Kpp0dCqbZyFzwtjTh9UJ5hGHUMN0ZGQHUL35+mkO9VRrA@mail.gmail.com> <CABT9mj-rw5bsVa7UAiraxu-U2t1QGqPronYj3Fx6ZxoPWo0Zow@mail.gmail.com> <CABT9mj-sQbfiNyfUZDxVmCg7SYWaJXcp+pNbyUSj64iFSA5fuA@mail.gmail.com> <70913413-2B68-4703-84E3-F7CC47E1A0E2@cisco.com> <CABT9mj9Jg-5pM4JKKOOgqszarFj6eDHji_rHZkTw3Eknddaqdw@mail.gmail.com> <489D13FBFA9B3E41812EA89F188F018E1AD9CDF7@xmb-rcd-x04.cisco.com>
To: Bernie Volz <volz@cisco.com>
X-Mailer: Apple Mail (2.1510)
Cc: "radext@ietf.org" <radext@ietf.org>, Michael Richardson <mcr+ietf@sandelman.ca>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [dhcwg] [homenet] PPP, DHCPv6 and Prefix Delegation
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: Tue, 19 Nov 2013 16:22:50 -0000

On Nov 19, 2013, at 3:19 PM, Bernie Volz (volz) <volz@cisco.com> wrote:

> I guess from RFC 4818, Delegated-IPv6-Prefix is used for PD. Whereas it says:
>  
>    The Framed-IPv6-Prefix attribute [4] is not designed to support
>    delegation of IPv6 prefixes to be used in the user's network, and
>    therefore Framed-IPv6-Prefix and Delegated-IPv6-Prefix attributes may
>    be included in the same RADIUS packet.
>  
> But, I’m not really clear if that ends up mapping to OPTION_PD_EXCLUDE for the Framed-IPv6-Prefix. Perhaps if the case is as in your example (Framed-IPv6-Prefix is contained by Delegated-IPv6-Prefix, but not equal) then using the Framed-IPv6-Prefix for OPTION_PD_EXCLUDE makes some sense?

3GPP system uses these in the above manner i.e. Framed-IPv6-Prefix -> what you put into RA, Delegated-IPv6-Prefix -> what you delegate via DHCPv6. And in this case what was in Framed-IPv6-Prefix goes into OPTION_PD_EXCLUDE.

- Jouni



>  
> -          Bernie
>  
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Athanasios Douitsis
> Sent: Tuesday, November 19, 2013 7:40 AM
> To: Bernie Volz (volz)
> Cc: radext@ietf.org; Michael Richardson; Roberta Maglione (robmgl); dhcwg@ietf.org WG; homenet@ietf.org
> Subject: Re: [dhcwg] [homenet] PPP, DHCPv6 and Prefix Delegation
>  
> Hello (thanks for the answer),
> 
> The uplink connection between the delegating and the requesting router will be in many cases enumerated with a prefix dictated by the Framed-IPv6-Prefix value. If this uplink prefix is going to be a part of the greater prefix that will be delegated, we would in effect have to include the value of the Framed-IPv6-Prefix in the OPTION_PD_EXCLUDE.
> 
> Example, if a delegating router makes a RADIUS request and gets the following attributes in the reply:
> 
> Framed-IPv6-Prefix='2001:dead:beef::/64'
> Delegated-IPv6-Prefix='2001:dead:beef::/56'
> 
> Then the delegating router should 
> 1)send an RA in the client uplink interface with 2001:dead:beef::/64. The uplink is enumerated with that /64.
> 2)Afterwards, when requested for PD, it should reply with the 2001:dead:beef::/56 to the requesting router, but excluding the 2001:dead:beef::/64 from that /56 by putting it in the OPTION_PD_EXCLUDE.
> 
> So in effect, the Framed-IPv6-Prefix has been copied in the OPTION_PD_EXCLUDE option.
> 
> If I have misunderstood something in the RFC or the discussion, I'd be grateful if you would correct me.
> 
> Thanks very much,
> Athanasios
> 
>  
> 
> 
> 
>  
>  
>  
>  
> 
> On Tue, Nov 19, 2013 at 2:07 PM, Bernie Volz (volz) <volz@cisco.com> wrote:
> Why would it ever be copied into that option? That makes no sense to me.
> 
> - Bernie (from iPad)
> 
> On Nov 19, 2013, at 6:16 AM, "Athanasios Douitsis" <aduitsis@gmail.com> wrote:
> 
>  
>  
> (i.e. have a configuration option to use the Framed-IPv6-Prefix value in the prefix exclude option instead of an RA)
>  
> Correction, the above is incorrect, as has been rightly pointed.
> 
> Are there any cases where the Framed-IPv6-Prefix value will not be copied as-is in the OPTION_PD_EXCLUDE value?
> 
> 
> 
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
> 
> 
> 
> -- 
> Athanasios Douitsis
> 
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet