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

"Roberta Maglione (robmgl)" <> Tue, 19 November 2013 17:10 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 30B6B1AE0EA; Tue, 19 Nov 2013 09:10:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -13.541
X-Spam-Status: No, score=-13.541 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FRT_ADULT2=1.474, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001, T_FRT_ADULT2=0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ZwlizUmzWGSq; Tue, 19 Nov 2013 09:10:50 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 119A01AE00B; Tue, 19 Nov 2013 09:10:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=8340; q=dns/txt; s=iport; t=1384881044; x=1386090644; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=nlxKWhOio5OqQQoLg/FG8KHFQckwZWJBAgHkTk/A8Io=; b=DXfSl1+wIgqvF36LlS4tk7QqknYEAfF6rU0Krf4/2gUwRY8JTHolSKIy lc9k3q/t1CCdOezjJ4zqq2NNebaLeV73t+ODY6zjBufFT3lRCz/Me05v0 gu7ltwIT56lAaPr+9I6JN37ZDsGKzHEatQmj69f/A1E88S6qYiz9+Qwy5 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos; i="4.93,730,1378857600"; d="scan'208,217"; a="283114983"
Received: from ([]) by with ESMTP; 19 Nov 2013 17:10:43 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id rAJHAhdm019230 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 19 Nov 2013 17:10:43 GMT
Received: from ([]) by ([]) with mapi id 14.03.0123.003; Tue, 19 Nov 2013 11:10:43 -0600
From: "Roberta Maglione (robmgl)" <>
To: Athanasios Douitsis <>, "Bernie Volz (volz)" <>
Thread-Topic: [homenet] [dhcwg] PPP, DHCPv6 and Prefix Delegation
Thread-Index: AQHO5UXOsn3IR999/EelIBkBsrSMwJotJp4AgAACHQD//50pQA==
Date: Tue, 19 Nov 2013 17:10:42 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_57C3345230A4F94C9B2F5CFA05D7F2BD1D4ED850xmbrcdx01ciscoc_"
MIME-Version: 1.0
Cc: Michael Richardson <>, "" <>, Jouni Korhonen <>, "" <>, " WG" <>
Subject: Re: [radext] [homenet] [dhcwg] PPP, DHCPv6 and Prefix Delegation
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 19 Nov 2013 17:10:53 -0000

I see your point. In my opinion if you would like to have all the prefixes assigned by RADIUS server in order to be able to cover the scenario you described in a clean way you would need a new RADIUS attribute for PD_EXCLUDE.
The reason why I think a new radius would be required is because you need to differentiate between the scenario where Framed-IPv6-Prefix is used to number the Wan link with a separate prefix (not included in the PD - without the PD_EXCLUDE) and the scenario you described where the prefix for the WAN link is part of the PD and you need to copy it into the PD exclude option.
Today the BNG (that in this case is acting both as RADIUS Client and Delegating Router) has no mean to know if the  Framed-IPv6-Prefix should be used for the  PD_EXCLUDE or not and in my opinion it would be better not overload the sematic of the Framed-IPv6-Prefix.
Any comment?

From: Athanasios Douitsis []
Sent: Tuesday, November 19, 2013 11:50 AM
To: Bernie Volz (volz)
Cc: Jouni Korhonen;;; Roberta Maglione (robmgl); WG; Michael Richardson
Subject: Re: [homenet] [dhcwg] PPP, DHCPv6 and Prefix Delegation

On Tue, Nov 19, 2013 at 6:42 PM, Bernie Volz (volz) <<>> wrote:
This must be done by the delegation router (if you are talking about the DHCPv6 packet itself) - as it is the one that constructs the Advertise and Reply messages to the client.

Pardon me, I meant to wonder who should make the assignment, not who should construct the packets.
When you are using the Delegated-IPv6-Prefix AV pair, the delegating router obviously constructs the packets with the delegated prefix value, but the actual assignment has been done by the RADIUS server. By the same token, I wondered whether it makes sense to do the same for the OPTION_PD_EXCLUDE value.

Kind regards,
Athanasios Douitsis