Re: [radext] [AD] AUTH48 [LB]: RFC 8044 <draft-ietf-radext-datatypes-08.txt> NOW AVAILABLE

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Fri, 13 January 2017 15:36 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.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 D6F7B1296B4; Fri, 13 Jan 2017 07:36:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 lPlESYMBRLEB; Fri, 13 Jan 2017 07:36:02 -0800 (PST)
Received: from mail-qt0-x242.google.com (mail-qt0-x242.google.com [IPv6:2607:f8b0:400d:c0d::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 668EB12948E; Fri, 13 Jan 2017 07:36:02 -0800 (PST)
Received: by mail-qt0-x242.google.com with SMTP id n13so6618300qtc.0; Fri, 13 Jan 2017 07:36:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=wVOq9YlOQsvwcvYPYpf2Mtt6fBEUW2njqK+1T7Qlxys=; b=K2jutjdbz+pXzkMMfAEU+BeEDAJp0s2YELqOFzqE6N+Wk5B2bfF49G5y3kw0WM5fMG my7Hvx2x6wLYGOEuBXUj2hv5dYfeICNITH8vwtC/7/C8X355vHcItwDtM0/lLKbYQrfJ QCOw4iG2L8Mi7gcM5Jr653NyLw5nyd3pgZpkJTMci65ApJHuNN4e1rtPw1Lkah+jzkda qRws1X1IVTA+IeBXKUcS9l7IVeEbQWjlqUIUU0vzhAvSjq3BwUFlFlMeS8E2zIVFP3lz Jv/UFhPEBC0qXT662qoZkng4W+DLkrpmZSfqIn3KKviDuf8wI4qWt5VrLw51jOl+LZnX ALPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=wVOq9YlOQsvwcvYPYpf2Mtt6fBEUW2njqK+1T7Qlxys=; b=EPE25Aw4e9RAjpbHty4FU0giJzU8rZEajxJlKF2x9SQyRiM59Y8rDZpSq+n0taV2zm AIqTY6fsJMFxl/cPu2nPooqKRWUNvwk/h0lxTuO3FlVe8QcCHEJWxxlE1iOX40Xeb+RN XySKxio+m6Qd1DGtqT6i0W0mxQsfZ/PCHnxyoEyDQqfnQteg/W7vXQ/RvQo7UY7HNoZH HOOHLZ97Af4eeMNSH6rr2HXsp2sNJlSjn7vU+F3gYiqZW+LX9Ia2cM59NTR5P7StABxO PZHmtKCQYCZ5HnX5X4gsyYHI13ltPwD7nC9YxDBmJjKb5O2RZSaQdoi0wGhwQr6g0vZa bHMQ==
X-Gm-Message-State: AIkVDXJyaeOgig27jY8Kd5CiyOIBwLMjqerHkYUQ88UNaKrYmgpU8zNOc5ItS3QXUH2hpcSYNOH8wh5Oc7EffA==
X-Received: by 10.237.45.7 with SMTP id h7mr17588983qtd.280.1484321761486; Fri, 13 Jan 2017 07:36:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.161.101 with HTTP; Fri, 13 Jan 2017 07:36:01 -0800 (PST)
In-Reply-To: <F1A445D1-C233-41AF-9E1D-8DE50E8DF092@gmail.com>
References: <20170109233022.14EE5B81304@rfc-editor.org> <CAHbuEH7A2+WyuexCVtFsk8bFGMG5nqOEDwbZY12oVgmwZtaJ5w@mail.gmail.com> <FF91E7C3-72C4-4F77-A957-ED8219B9C523@freeradius.org> <CAHbuEH7-E9VUH+ZxJdqQpr=hjhKFf0obEPLKZLwJHUZBmqF21w@mail.gmail.com> <F1A445D1-C233-41AF-9E1D-8DE50E8DF092@gmail.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Fri, 13 Jan 2017 10:36:01 -0500
Message-ID: <CAHbuEH6DjWip-Sr=0hRnKz4M5HwrW0H1pY5vAZE_sQHMDWgj9Q@mail.gmail.com>
To: Bernard Aboba <bernard.aboba@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c124a405375320545fb9707
Archived-At: <https://mailarchive.ietf.org/arch/msg/radext/MfW9WuHbUKzHkwr2hFyw3BfPzz0>
Cc: "radext@ietf.org" <radext@ietf.org>, radext-ads@ietf.org, Winter Stefan <stefan.winter@restena.lu>, "iesg@ietf.org" <iesg@ietf.org>, Alan DeKok <aland@freeradius.org>, radext-chairs@ietf.org, RFC Editor <rfc-editor@rfc-editor.org>
Subject: Re: [radext] [AD] AUTH48 [LB]: RFC 8044 <draft-ietf-radext-datatypes-08.txt> NOW AVAILABLE
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 13 Jan 2017 15:36:05 -0000

Hello,

I think we have agreement to continue moving forward, just noting the
'updates' since it is not a significant update.

Thank you,
Kathleen

On Wed, Jan 11, 2017 at 3:28 PM, Bernard Aboba <bernard.aboba@gmail.com>
wrote:

> Data types do not affect what is actually sent on the wire, they just make
> it easier for a RADIUS server to add support for an attribute without
> custom code. So the datatypes draft does not create a deployment blocker or
> backward compatibility issue, it actually may make implementation easier.
>
> On Jan 11, 2017, at 8:43 AM, Kathleen Moriarty <
> kathleen.moriarty.ietf@gmail.com> wrote:
>
> Adding the IESG and the working group to see if there are any concerns
> with the following approach... inline
>
> On Wed, Jan 11, 2017 at 10:40 AM, Alan DeKok <aland@freeradius.org> wrote:
>
>>
>> > > > a) RFCs 4072 and 7268 are not cited anywhere in this document.
>> > > > Please let us know where they should be cited; otherwise, the
>> > > > listings will be removed.
>> > >
>> > > The RFCs are referenced simply because this document is updating
>> > > attributes that they define.
>> >
>> > Can you please list the specific updates from the 2 mentioned RFCs here
>> and then I'll figure out if this needs to go back through the WG and last
>> calls or not.
>>
>> http://www.iana.org/assignments/radius-types/radius-types.
>> xhtml#radius-types-2
>>
>>   RFC 4072 defines EAP-Key-Name.  It's in the RADIUS space, but t's
>> defined to have a Diameter data type "OctetString".   We can't use
>> "OctetString" for a RADIUS data types, so the "data types" document defines
>> it as the RADIUS data type "string". Which ends up being the same for all
>> intents and purposes.
>>
>>   RFC 7268 defines a bunch of attributes.  Most are of 32-bit integers,
>> which maps well to the data types doc.  The only real "new" thing is
>> EAPoL-Announcement.  It's defined manually in RFC 7268 as "concatenate the
>> fragments together before looking at it".  The data types doc calls this
>> out as a special data type "concat", along with EAP-Message, and a few
>> others.
>>
>>   I think everyone is in agreement as to what the data types should be.
>> The "updates RFC 4072 / 7268" note is really saying "RFC 4072 / 7268 talks
>> about this attribute, but doesn't really give an adequate definition for
>> it.  So the data types document picks something, which is compatible with
>> the original definition, but uses a now-standard data type"
>>
>>   i.e. the original spec isn't so much wrong, as unclear and incomplete.
>>
>
> This seems like a small enough 'updates' that I think it should be fine to
> progress just adding the note that RFC4072 and RFC7268 are updated.
>
> Any objections?  The alternative would be to put this back through the
> last call process, but I think this looks small enough to avoid that.  It
> would really just be for process sake IMO.
>
>
>>   Alan DeKok.
>>
>>
>
>
> --
>
> Best regards,
> Kathleen
>
> _______________________________________________
> radext mailing list
> radext@ietf.org
> https://www.ietf.org/mailman/listinfo/radext
>
>


-- 

Best regards,
Kathleen