IETF Logo Mail Archive

Re: [dhcwg] [radext] draft-ietf-dhc-dhcpv6-radius-opt-10

"Leaf Yeh" <leaf.yeh.sdo@gmail.com> Mon, 08 April 2013 17:31 UTC

Return-Path: <leaf.yeh.sdo@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DCAE21F97B9; Mon, 8 Apr 2013 10:31:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.39
X-Spam-Level:
X-Spam-Status: No, score=0.39 tagged_above=-999 required=5 tests=[AWL=-2.104, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_LT4=0.442, HELO_OEM=2.195, RCVD_IN_PBL=0.905, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ec4c2GRRfa89; Mon, 8 Apr 2013 10:31:48 -0700 (PDT)
Received: from mail-ia0-x231.google.com (mail-ia0-x231.google.com [IPv6:2607:f8b0:4001:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 97F5221F97B7; Mon, 8 Apr 2013 10:31:48 -0700 (PDT)
Received: by mail-ia0-f177.google.com with SMTP id w33so5309583iag.8 for <multiple recipients>; Mon, 08 Apr 2013 10:31:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language; bh=dPbvYLNyJwbN1QF1vmjIg5lPFtDipl+KUOKfqs1f0EU=; b=ujjbSLLVvChTHfXCWrCQ7jorEqZKVO9DMO9elfvB9KTlen2EfZG4GubUge9tTPQ5OE Mb4kAqi1EuioJcH+3qdqIIuoMs462PeuwF0Ku1GatzuJhM6IvSVyuFK/Mwfcprj14Cdl tNoc/I2ls2KkhtUIqYFSwiIQfl3ig6IXF9zJNVCc9UeJbNMbonG7HQVsweBl38c5dfB1 FcKl46H2czmxdytcg7USjG2zj/CYfF26G/JY982FZ9izG9QQh4/VWvDDhf1c3OcZs1Qf TvdQlCdtTgIW2yzarg/Q9uLS4YMAEfwCvFCLYlOSS12j/SeCPkofWg2ABmhpP7hFM+fh TOfw==
X-Received: by 10.50.212.74 with SMTP id ni10mr7916340igc.60.1365442307934; Mon, 08 Apr 2013 10:31:47 -0700 (PDT)
Received: from PC ([114.248.232.47]) by mx.google.com with ESMTPS id ip2sm18310754igc.5.2013.04.08.10.31.44 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 08 Apr 2013 10:31:47 -0700 (PDT)
From: Leaf Yeh <leaf.yeh.sdo@gmail.com>
To: 'Jouni Korhonen' <jouni.nospam@gmail.com>, 'Ted Lemon' <Ted.Lemon@nominum.com>
References: <B51C71CC-654D-43F3-A50A-321C171CD562@gmail.com> <515D7B4D.7090201@deployingradius.com> <515db052.24fa440a.4c16.ffff93c2@mx.google.com> <515DBD38.2020607@deployingradius.com> <8D23D4052ABE7A4490E77B1A012B630775131DB4@mbx-01.win.nominum.com> <515DE629.6070706@deployingradius.com> <8D23D4052ABE7A4490E77B1A012B630775132294@mbx-01.win.nominum.com> <515DE957.1060202@deployingradius.com> <8D23D4052ABE7A4490E77B1A012B630775132374@mbx-01.win.nominum.com> <9992DCA7-FFB3-4328-A8FC-266109BDD059@gmail.com> <8D23D4052ABE7A4490E77B1A012B630775132B92@mbx-01.win.nominum.com> <CFE49718-CB57-4D90-8843-F5E0BD57BF49@gmail.com>
In-Reply-To: <CFE49718-CB57-4D90-8843-F5E0BD57BF49@gmail.com>
Date: Tue, 09 Apr 2013 01:31:36 +0800
Message-ID: <5162ff03.e2c4320a.4c2e.4d89@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac4x/DTwlyIftvbWQ5+H5ZTlKErHfQAHyYnw
Content-Language: zh-cn
Cc: radext@ietf.org, 'Alan DeKok' <aland@deployingradius.com>, 'dhcwg' <dhcwg@ietf.org>
Subject: Re: [dhcwg] [radext] draft-ietf-dhc-dhcpv6-radius-opt-10
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 08 Apr 2013 17:31:49 -0000

Jouni - If that is a concern one can always change the "can only" to "MUST".

The draft (ver.-11) will take this point.


Best Regards,
Leaf




-----Original Message-----
From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of
Jouni Korhonen
Sent: Friday, April 05, 2013 8:51 PM
To: Ted Lemon
Cc: <radext@ietf.org>; dhcwg; Alan DeKok
Subject: Re: [dhcwg] [radext] draft-ietf-dhc-dhcpv6-radius-opt-10


On Apr 5, 2013, at 2:42 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Apr 5, 2013, at 3:19 AM, Jouni Korhonen <jouni.nospam@gmail.com> wrote:
>>  The option-data of OPTION_RADIUS is a list of one or more RADIUS  
>> attributes received in the Access-Accept message from the RADIUS  
>> server. The OPTION_RADIUS can only contain RADIUS attributes  listed 
>> in the IANA Registry of 'RADIUS attributes permitted in
>>  DHCPv6 RADIUS option'.
> 
> So you took out the normative language, right?   Was that intentional?

That was intentional. If that is a concern one can always change the "can
only" to "MUST". That works too, since the previous sentence already points
out that the option contains one or more attributes, not all.

>> The next question I have is what happens when a relay includes an 
>> attribute that the server does not understand or is not listed in the 
>> registry? There is no versioning thus it is possible that relay and 
>> server have a different understanding what the IANA registry is. Now 
>> the text in Section 6 only addresses the case where the server does not
understand the DHCP option.
> 
> Good question.   I think the right answer is that that RADIUS attribute is
silently ignored, because, as you say, the server might not be up to date.

Blindly dropping an attribute might not work in all cases. For example, in
some cases the server might not then be able to provide all information the
relay needs.. That is more of a DHCP specification issue but what I would
like to see in this I-D is some text pointing out that the server and the
relay may have a different idea of the registry and the protocol design need
to take that into account.

- Jouni




> 

_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email