IETF Logo Mail Archive

Re: [kitten] sasl-saml-ec-18: bookkeeping changes requested

Benjamin Kaduk <kaduk@mit.edu> Mon, 26 August 2019 22:20 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F82C120013 for <kitten@ietfa.amsl.com>; Mon, 26 Aug 2019 15:20:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 fDDbvcHJGeBJ for <kitten@ietfa.amsl.com>; Mon, 26 Aug 2019 15:20:18 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2D8A120044 for <kitten@ietf.org>; Mon, 26 Aug 2019 15:20:18 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x7QMKDsh010470 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 26 Aug 2019 18:20:15 -0400
Date: Mon, 26 Aug 2019 17:20:12 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Robbie Harwood <rharwood@redhat.com>
Cc: "Cantor, Scott" <cantor.2@osu.edu>, "kitten@ietf.org" <kitten@ietf.org>
Message-ID: <20190826222012.GT84368@kduck.mit.edu>
References: <jlg1rxcsy0u.fsf@redhat.com> <A3B5AFBE-2F57-4A9A-8106-7F64A03CBE55@osu.edu> <jlgh86752yw.fsf@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <jlgh86752yw.fsf@redhat.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/57qtnESWpCptF8qNAOqjwqdh0Vs>
Subject: Re: [kitten] sasl-saml-ec-18: bookkeeping changes requested
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2019 22:20:20 -0000

On Fri, Aug 23, 2019 at 11:13:59AM -0400, Robbie Harwood wrote:
> "Cantor, Scott" <cantor.2@osu.edu> writes:
> 
> > On 8/22/19, 5:14 PM, "Robbie Harwood" <rharwood@redhat.com> wrote:
> >
> >> Additionally, it doesn't like having a separate "Normative
> >> References" and "Normative References for GSS-API Implementers"
> >> section.  While I don't know that it's technically required to name
> >> the sections a certain way, I think it would be easiest to make a
> >> single "Normative References" section.
> >
> > That was taken verbatim from the earlier GS2 mechanims, I believe, but
> > it doesn't matter to me.
> 
> Ah, okay.  Either way should be fine then; I'll just note it in the
> review.

My recollection is that the references have to be divided into normative
vs. informative, but that further subdivision is not precluded.  So,
sticking to tradition is probably okay (but we may get further comments
about it from directorate and/or IESG reviews).

-Ben

v2.23.0 | Report a Bug | By Email