IETF Logo Mail Archive

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

Peter Deacon <peterd@iea-software.com> Fri, 05 April 2013 18:25 UTC

Return-Path: <peterd@iea-software.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 3493921F984E; Fri, 5 Apr 2013 11:25:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.496
X-Spam-Level:
X-Spam-Status: No, score=-2.496 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_00=-2.599]
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 G47LwWoMra8H; Fri, 5 Apr 2013 11:25:19 -0700 (PDT)
Received: from aspen.internal.iea-software.com (remote.iea-software.com [70.89.142.196]) by ietfa.amsl.com (Postfix) with ESMTP id 932BF21F9849; Fri, 5 Apr 2013 11:25:19 -0700 (PDT)
Received: from SMURF (unverified [10.0.3.195]) by aspen.internal.iea-software.com (Rockliffe SMTPRA 7.0.6) with ESMTP id <B0005878305@aspen.internal.iea-software.com>; Fri, 5 Apr 2013 11:25:19 -0700
Date: Fri, 05 Apr 2013 11:25:14 -0700
From: Peter Deacon <peterd@iea-software.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751336B3@mbx-01.win.nominum.com>
Message-ID: <alpine.WNT.2.00.1304051004200.3988@SMURF>
References: <B51C71CC-654D-43F3-A50A-321C171CD562@gmail.com> <alpine.WNT.2.00.1304041005110.3988@SMURF> <515ea42f.c521440a.26ee.ffffcc8e@mx.google.com> <alpine.WNT.2.00.1304050824570.3988@SMURF> <8D23D4052ABE7A4490E77B1A012B6307751336B3@mbx-01.win.nominum.com>
User-Agent: Alpine 2.00 (WNT 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="US-ASCII"
X-Mailman-Approved-At: Fri, 05 Apr 2013 11:53:14 -0700
Cc: "<radext@ietf.org>" <radext@ietf.org>, 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: Fri, 05 Apr 2013 18:25:20 -0000

On Fri, 5 Apr 2013, Ted Lemon wrote:

> On Apr 5, 2013, at 12:11 PM, Peter Deacon <peterd@iea-software.com> wrote:
>> Ok, my only concern here is relays tend to be "dumb" and outnumber DHCPv6 servers in number and vendors involved.  It might be difficult to ever add new attributes in production as you would have to touch all relays to allow a new attribute to pass.  My guess VSAs would likely end up filling any gaps anyway.

> What's a VSA?  Should the document specify that the list of attributes 
> to forward be customizable by the administrator?

Hi Ted Lemon,

The configuration options sound good.

VSA = Vendor Specific Attribute (Vendor-Specific in table sec 4.1)

regards,
Peter

v2.23.0 | Report a Bug | By Email