Re: [abfab] Barry Leiba's No Objection on draft-ietf-abfab-aaa-saml-13: (with COMMENT)

Barry Leiba <barryleiba@computer.org> Mon, 11 January 2016 14:05 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: abfab@ietfa.amsl.com
Delivered-To: abfab@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A62BB1A00E1; Mon, 11 Jan 2016 06:05:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level:
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 cuPhzn5ruhaI; Mon, 11 Jan 2016 06:05:16 -0800 (PST)
Received: from mail-io0-x232.google.com (mail-io0-x232.google.com [IPv6:2607:f8b0:4001:c06::232]) (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 E30D61A00D0; Mon, 11 Jan 2016 06:05:15 -0800 (PST)
Received: by mail-io0-x232.google.com with SMTP id g73so152896335ioe.3; Mon, 11 Jan 2016 06:05:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=jWJMZMdyT0jLxN0/+o+Qpjsa0EBTxtz0Pu1srgDm1Tw=; b=QoDLREvqsLrhIz5GBsM5WXx/j2S/C1dpYIc3W6tw0avdfl3S5A4yR1o6FFpboj6D8R N/GFtd36ic0qk3EyW62ipEQ+JrpcaA6BV8VdFwJsLjkW39z2+t6G/gLl69a+RmtP8Gxd +rlQl5CnmuZhrTPwBToWGmWg32pklrwcMZWxJSp3W7IcnSHR+GSNjrPesGG2GTIzsxWn FgFfRnhmTFj6kc1n/2fUqj2B/LoSGFf0OLLXIIfwuCs4V8Q1ma9s8xRO7cwenYxP+NGE cATonztqbyOApNS0mHEUpiScM/cNda0gRki0VnwLsrJB1MhsSWkn2h6VxUCgiBljadPo UC4g==
MIME-Version: 1.0
X-Received: by 10.107.131.86 with SMTP id f83mr99796854iod.189.1452521115303; Mon, 11 Jan 2016 06:05:15 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.36.117.83 with HTTP; Mon, 11 Jan 2016 06:05:15 -0800 (PST)
In-Reply-To: <56936B91.4040508@um.es>
References: <20160107014638.22674.62959.idtracker@ietfa.amsl.com> <56936B91.4040508@um.es>
Date: Mon, 11 Jan 2016 09:05:15 -0500
X-Google-Sender-Auth: RFDrlw24_dOWMTEQlLEPDUVxnOI
Message-ID: <CALaySJLUDGyzNq7_P+sUZ6-DZ0mAcEQ6ztzLrjA79UE5nPmDMQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: =?UTF-8?B?QWxlamFuZHJvIFDDqXJleiBNw6luZGV6?= <alex@um.es>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/abfab/WPwXBvG74TVHf1-DZ0ZvEwD4ieQ>
Cc: abfab@ietf.org, abfab-chairs@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-abfab-aaa-saml@ietf.org
Subject: Re: [abfab] Barry Leiba's No Objection on draft-ietf-abfab-aaa-saml-13: (with COMMENT)
X-BeenThere: abfab@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Application Bridging, Federated Authentication Beyond \(the web\)" <abfab.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/abfab>, <mailto:abfab-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/abfab/>
List-Post: <mailto:abfab@ietf.org>
List-Help: <mailto:abfab-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/abfab>, <mailto:abfab-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2016 14:05:21 -0000

Thanks for the response, Alejandro, and for addressing my comments.

Barry

On Mon, Jan 11, 2016 at 3:45 AM, Alejandro Pérez Méndez <alex@um.es>; wrote:
> Hi Barry,
>
> thanks for your comments. See my responses inline, please.
>
> El 07/01/16 a las 02:46, Barry Leiba escribió:
>>
>> Barry Leiba has entered the following ballot position for
>> draft-ietf-abfab-aaa-saml-13: No Objection
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-abfab-aaa-saml/
>>
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> Because abfab-arch defines the terms "Client", "Relying Party", and
>> "Identity Provider", I think abfab-arch should be a normative reference.
>
>
> As per the discussion you had with Sam, I see your point and I'm not against
> it.
> On the other hand, I think that the terms "Client", "Relaying Party", and
> "Identity Provider" are common enough to don't require readers to go to the
> reference to understand them, specially when the document already contains a
> terminlogy table that matches these terms with their SAML and RADIUS
> correspondences.
>
>>
>> -- Section 3 --
>>
>>     The RADIUS SAML binding defined in Section 4 of this document uses
>>     two attributes to convey SAML assertions and protocol messages
>>     respectively [OASIS.saml-core-2.0-os]
>>
>> Nit: "respectively" is out of place here, and should be removed.  You
>> would only use "respectively" if you named the two attributes ("...uses
>> two attributes, SAML-Assertion and SAML-Protocol, to convey SAML
>> assertions and protocol messages, respectively.").
>
>
> Right, thanks. Probably the result of an edit to remove the attribute names
> from that paragraph.
>
>>
>> -- Section 7.3.5 --
>>
>>     If issued by the Identity Provider, the Relying Party MUST process
>>     the <samlp:Response> message and any enclosed assertion elements as
>>     described in [OASIS.saml-core-2.0-os]
>>
>> "If issued" is dangling, and  makes it look like the Relying Party is
>> issued by the Identity Provider.
>>
>> NEW
>>     If a <samlp:Response> message is issued by the Identity Provider,
>>     the Relying Party MUST process that message and any enclosed
>>     assertion elements as described in [OASIS.saml-core-2.0-os]
>> END
>
>
> Thanks, the text you've provided sounds much more clear. I will include it.
>
> Best regards,
> Alejandro
>
>
>>
>> -- Section 11.2 --
>> Thank you; this section is well done.
>>
>>
>