Re: [Softwires] 6rd RADIUS attribute - grouped attributes

Peter Deacon <peterd@iea-software.com> Thu, 22 December 2011 05:50 UTC

Return-Path: <peterd@iea-software.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A3D221F8B95 for <softwires@ietfa.amsl.com>; Wed, 21 Dec 2011 21:50:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_37=0.6]
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 DHOTIMbURXZd for <softwires@ietfa.amsl.com>; Wed, 21 Dec 2011 21:50:17 -0800 (PST)
Received: from aspen.internal.iea-software.com (remote.iea-software.com [70.89.142.196]) by ietfa.amsl.com (Postfix) with ESMTP id 9A71021F8B94 for <softwires@ietf.org>; Wed, 21 Dec 2011 21:50:17 -0800 (PST)
Received: from SMURF (unverified [10.0.3.195]) by aspen.internal.iea-software.com (Rockliffe SMTPRA 7.0.6) with ESMTP id <B0005781930@aspen.internal.iea-software.com>; Wed, 21 Dec 2011 08:14:22 -0800
Date: Wed, 21 Dec 2011 08:14:17 -0800
From: Peter Deacon <peterd@iea-software.com>
To: Stefan Winter <stefan.winter@restena.lu>
In-Reply-To: <4EF1E94D.2080006@restena.lu>
Message-ID: <alpine.WNT.2.00.1112210807180.2472@SMURF>
References: <4EC1BD65.4040205@restena.lu> <4EEB1014.1030307@restena.lu> <5D36713D8A4E7348A7E10DF7437A4B9218583E44@SZXEML506-MBX.china.huawei.com> <4EF047A3.5090906@restena.lu> <4EF08F63.1010600@deployingradius.com> <alpine.WNT.2.00.1112200950300.2472@SMURF> <5D36713D8A4E7348A7E10DF7437A4B9218584374@SZXEML506-MBX.china.huawei.com> <alpine.WNT.2.00.1112201948210.2472@SMURF> <4EF1A65F.9080609@restena.lu> <alpine.WNT.2.00.1112210204010.2472@SMURF> <4EF1E94D.2080006@restena.lu>
User-Agent: Alpine 2.00 (WNT 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Mailman-Approved-At: Tue, 03 Jan 2012 08:09:36 -0800
Cc: softwires@ietf.org, Alan DeKok <aland@deployingradius.com>, GuoDayong <guodayong@huawei.com>
Subject: Re: [Softwires] 6rd RADIUS attribute - grouped attributes
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Dec 2011 05:50:18 -0000

On Wed, 21 Dec 2011, Stefan Winter wrote:

>> I don't think this is correct.  The extensions document describes a
>> *data type* 'TLV'.  My suggestion simply leverages this type in the same
>> way IPv4 Address and IPv6 prefix type from existing RFCs are already
>> being leveraged.
>>
>> If you implement extensions RFC in the future your implementation
>> supports the TLV data type giving you the ability to encode and decode
>> this attribute with configuration dictionaries.  The wire format of
>> IPv6-6rd-Configuration was intentionally made to be the same as a TLV.

> Ah! I'm just looking at the -04 with this extra context. It's certainly
> close. I think there's only one thing which is not inline: 6rdprefixLen
> and 6rdPrefix immediately follow each other. In a version
> compatible/analogous to the radius-extensions draft, the former would be
> of type integer, the latter of type IPv6Address, and each would have its
> own (Subtype,SubLen) tuple.

> Any particular reason why the 6rdPrefixLen and 6rdPrefix are glued into
> one blob in -04?

If you ignore the 6rd references it is describing prefix data type defined 
a decade back in RFC3162 2.3 (Framed-IPv6-Prefix).  Logically it counts as 
one field.

regards,
Peter