IETF Logo Mail Archive

Re: [radext] Extended IDs

Enke Chen <enkechen@cisco.com> Mon, 04 December 2017 19:51 UTC

Return-Path: <enkechen@cisco.com>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C41CF12894A for <radext@ietfa.amsl.com>; Mon, 4 Dec 2017 11:51:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7q4BRCQDeeht for <radext@ietfa.amsl.com>; Mon, 4 Dec 2017 11:51:14 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2E50128891 for <radext@ietf.org>; Mon, 4 Dec 2017 11:51:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2200; q=dns/txt; s=iport; t=1512417073; x=1513626673; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=pE0V6cdBJN/F73lHurkQWGPGuQnNzr45+f8HvnGUMZo=; b=R9PomCzH4O3EzD5azqg/JL80HC2o/nQMBSQF/uNRiZD36VzK+z1zm4BH qBSYOc/wpqPOFXxCEqcUXPPw6EyNHcETreu2znYs7fj/CpECC+Wn/HeSU N2f+X0jG8IiIfblrImvzRXUiYuY0mHAdNiTEHEUTJd+dw2Ej5xa7Nd3Ak o=;
X-IronPort-AV: E=Sophos;i="5.45,361,1508803200"; d="scan'208";a="317951728"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 04 Dec 2017 19:51:13 +0000
Received: from [10.156.165.134] ([10.156.165.134]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id vB4JpCZh026675; Mon, 4 Dec 2017 19:51:13 GMT
To: Stefan Winter <stefan.winter@restena.lu>
References: <fef698a5-9802-c9be-04d7-1e869651c988@restena.lu> <dfd0ff02-c9e8-7253-4fb4-1e6def3e93b2@restena.lu>
Cc: radext@ietf.org, Enke Chen <enkechen@cisco.com>, Naiming Shen <naiming@cisco.com>
From: Enke Chen <enkechen@cisco.com>
Message-ID: <8b7791e4-6328-ae4c-8dce-f77b32c321c1@cisco.com>
Date: Mon, 04 Dec 2017 11:51:12 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <dfd0ff02-c9e8-7253-4fb4-1e6def3e93b2@restena.lu>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/7hyC3xG5HryQBK_NWnsBhoN4TuE>
Subject: Re: [radext] Extended IDs
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/radext/>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Dec 2017 19:51:16 -0000

Hi, Stefan:

1) I prefer draft-chen-radext-identifier-attr-02.

2) I believe that the draft offers a simple, and straightforward solution to the problem
   without overloading any unrelated fields.

3) The implementation is pretty simple too, about 190 lines of C code for the complete
   implementation (client / server /proxy, and both UDP and TCP)) in FreeRadius as posted
   in April 2017 to the RADEXT WG:

   https://www.ietf.org/mail-archive/web/radext/current/msg09905.html  

4) For a summary of the draft, please see the slides:

   https://datatracker.ietf.org/meeting/99/materials/slides-99-radext-radius-extended-identifier-attribute/

Thanks.  -- Enke

On 11/28/17 5:54 AM, Stefan Winter wrote:
> Hello,
> 
>> thanks all for raising the awareness of these two drafts.
>>
>>
>> I think it would be good if all remaining readers of this list who care
>> enough now take some time to read both drafts and make up their mind on
>> what the preferred approach is.
>>
>>
>> In approx. two weeks' time I will start a call for adoption on both
>> drafts, and hopefully there are enough responses to make the exercise
>> meaningful. If so, the one with more votes wins.
> 
> Now that was a relaxed "two weeks" delay. My apologies, I've been on and
> off work for a while, with substantial backlogs.
> 
> This email starts a two week call for adoption of at most one of the
> following two drafts:
> 
> * draft-chen-radext-identifier-attr-02
> * draft-dekok-radext-request-authenticator-02
> 
> Since the two drafts treat the same topic, at most one can be selected
> to serve as the basis for future work.
> 
> In your reply to this call for adoption, please indicate which of the
> two drafts you think should be adopted. You can of course also indicate
> that none of the two are fit for purpose. The only thing you really
> shouldn't do is to vote for both; that wouldn't help the discussion move on.
> 
> Please reply by 12 dec 2017 2400 UTC.
> 
> Greetings,
> 
> Stefan Winter
> 
> 
> 
> _______________________________________________
> radext mailing list
> radext@ietf.org
> https://www.ietf.org/mailman/listinfo/radext
>

v2.23.0 | Report a Bug | By Email