IETF Logo Mail Archive

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

Tomek Mrugalski <tomasz.mrugalski@gmail.com> Tue, 09 April 2013 14:31 UTC

Return-Path: <tomasz.mrugalski@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 DD47B21F913E; Tue, 9 Apr 2013 07:31:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.995
X-Spam-Level:
X-Spam-Status: No, score=-2.995 tagged_above=-999 required=5 tests=[AWL=0.604, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-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 BEScPioFCWNm; Tue, 9 Apr 2013 07:31:32 -0700 (PDT)
Received: from mail-ee0-f50.google.com (mail-ee0-f50.google.com [74.125.83.50]) by ietfa.amsl.com (Postfix) with ESMTP id E477421F8F39; Tue, 9 Apr 2013 07:31:31 -0700 (PDT)
Received: by mail-ee0-f50.google.com with SMTP id e53so3005951eek.9 for <multiple recipients>; Tue, 09 Apr 2013 07:31:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-tagtoolbar-keys:content-type :content-transfer-encoding; bh=Bapb3zlhrTfTh3VOs/vR8+dLWwaAJisVLMNKORPeUN8=; b=p8wBjIslg+mZzAh8xS2S4l41iA0JuZk80tYmcRS9Yf/TWXj9J3Gx3dj56NdN956fNx Lq5iTeyVarfBJervWjcw+BZj9TjXyN5jdmNEcl3HyYkEPOXMT+G//RtQh0RbSUuwd27M 2WfpLBtSpy6ZMp6+De5TtMdsfrikE20gbUad69XodqESXANwDWpQ/ltRLLJLxUsAizrl GquLi25hPOUfWL3zhpMmqohmXvp88EG0IkcpULyJJIUgjYHc+C1yTBkTdgqWx5SsNtJV yceKW+vnumuqVqcotdsFquOJHQz6BJaohA4eUd9MjtV1igj9KAyx8Ox0A9cY9kLliC8C oDJQ==
X-Received: by 10.15.21.1 with SMTP id c1mr60104763eeu.36.1365517890650; Tue, 09 Apr 2013 07:31:30 -0700 (PDT)
Received: from [10.0.0.100] (host-109-107-11-157.ip.jarsat.pl. [109.107.11.157]) by mx.google.com with ESMTPS id d47sm38332200eem.9.2013.04.09.07.31.28 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Apr 2013 07:31:29 -0700 (PDT)
Message-ID: <5164263E.50402@gmail.com>
Date: Tue, 09 Apr 2013 16:31:26 +0200
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130308 Thunderbird/17.0.4
MIME-Version: 1.0
To: dhcwg@ietf.org, "<radext@ietf.org>" <radext@ietf.org>
References: <CAC8SSWtBMyDgShEDofyUjgcBiQ_ttY_DUbDNHnhhnf531+9XXA@mail.gmail.com> <FB413294-CF61-4AD9-AF26-41EC8A30DF37@gmail.com> <5162d5aa.0794420a.2f19.fffff597@mx.google.com> <8D23D4052ABE7A4490E77B1A012B630775138825@mbx-01.win.nominum.com> <489D13FBFA9B3E41812EA89F188F018E184EBA72@xmb-rcd-x04.cisco.com> <AC349589-AC7B-442B-9CE8-D7343BC44BCC@gmail.com>
In-Reply-To: <AC349589-AC7B-442B-9CE8-D7343BC44BCC@gmail.com>
X-TagToolbar-Keys: D20130409163126087
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
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: Tue, 09 Apr 2013 14:31:33 -0000

On 09.04.2013 11:59, Jouni Korhonen wrote:
> What I am after is a note stating that a _client_ must be prepared
> for a reply from a server that does not provide adequate
> response/information for all the RADIUS attributes the client
> included in the request. This is solely meant for the future
> specifications using the OPTION_RADIUS.
When clarifying that, we must remember to be explicit about which client
or server (radius or dhcpv6) we are talking about here.

Here's DHCPv6 point of view: This DHCPv6 option will never reach DHCPv6
client. DHCPv6 client will never send it either. DHCPv6 Server will
never send this option back, just receive it from the DHCPv6 relay.

v2.23.0 | Report a Bug | By Email