Re: [jose] Ben Campbell's No Objection on draft-ietf-jose-cfrg-curves-05: (with COMMENT)

joel jaeggli <joelja@bogus.com> Wed, 17 August 2016 16:57 UTC

Return-Path: <joelja@bogus.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1580C12D993 for <jose@ietfa.amsl.com>; Wed, 17 Aug 2016 09:57:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.147
X-Spam-Level:
X-Spam-Status: No, score=-8.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.247] 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 rgFDOZoOZZnH for <jose@ietfa.amsl.com>; Wed, 17 Aug 2016 09:57:01 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 05BB012D9E1 for <jose@ietf.org>; Wed, 17 Aug 2016 09:57:01 -0700 (PDT)
Received: from mbp.local ([IPv6:2620:11a:c081:20:602a:5e74:b376:17ff]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id u7HGuxab081339 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 17 Aug 2016 16:57:00 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host [IPv6:2620:11a:c081:20:602a:5e74:b376:17ff] claimed to be mbp.local
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, Ben Campbell <ben@nostrum.com>
References: <147140015280.19947.15915664309829411372.idtracker@ietfa.amsl.com> <063301d1f831$2408d6a0$6c1a83e0$@augustcellars.com> <2A58CE47-F942-4DC5-8719-CB3F811667FE@nostrum.com> <CAHbuEH5Qiw1MnTdHHd17uOHgDhYSny+ewCh1HWpTYmjqs7=_HA@mail.gmail.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <6e8c4169-14f5-953d-637d-3e7ece733545@bogus.com>
Date: Wed, 17 Aug 2016 09:56:58 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:47.0) Gecko/20100101 Thunderbird/47.0
MIME-Version: 1.0
In-Reply-To: <CAHbuEH5Qiw1MnTdHHd17uOHgDhYSny+ewCh1HWpTYmjqs7=_HA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/jose/7xQLK8VaZT_GsHD1LEhJtQAOks0>
Cc: Jim Schaad <ietf@augustcellars.com>, jose-chairs@ietf.org, The IESG <iesg@ietf.org>, "jose@ietf.org" <jose@ietf.org>, draft-ietf-jose-cfrg-curves@ietf.org
Subject: Re: [jose] Ben Campbell's No Objection on draft-ietf-jose-cfrg-curves-05: (with COMMENT)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jose>, <mailto:jose-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jose/>
List-Post: <mailto:jose@ietf.org>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jose>, <mailto:jose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Aug 2016 16:57:04 -0000

On 8/17/16 9:39 AM, Kathleen Moriarty wrote:
> On Tue, Aug 16, 2016 at 11:46 PM, Ben Campbell <ben@nostrum.com> wrote:
>> On 16 Aug 2016, at 21:43, Jim Schaad wrote:
>>
>>> I don't know when it needs to be done, but the other down reference in the
>>> document is also an algorithm document which I hope will get into the
>>> registry as well when it is published.
>>
>> I agree . I didn't call that out because that one _was_ mentioned in the
>> last call announcement.
> Sorry to chime in late.  I thought this was covered in the shepherd
> report, but didn't realize there were 2 downrefs.  What do I need to
> do at this point?  We don't need to do another last call anymore,
> right?  Sorry I am not remembering the new procedure.
If you belive that the downrefs to a particular document are accepted by
the community you waive them and do nothing.

   Once a specific down reference to a particular document has been
   accepted by the community (e.g., has been mentioned in several Last
   Calls), an Area Director may waive subsequent notices in the Last
   Call of down references to it.  This should only occur when the same
   document (and version) are being referenced and when the AD believes
   that the document's use is an accepted part of the community's
   understanding of the relevant technical area.  For example, the use
   of MD5 [RFC1321 <https://tools.ietf.org/html/rfc1321>] and HMAC [RFC2104 <https://tools.ietf.org/html/rfc2104>] is well known among
   cryptographers.

normative downrefs to external crypto specifications documented in informational RFCs are a normal and accepted part of the process.


>
> Thanks,
> Kathleen
>
>
>> Thanks,
>>
>> Ben.
>>
>>
>>> Jim
>>>
>>>
>>>> -----Original Message-----
>>>> From: Ben Campbell [mailto:ben@nostrum.com]
>>>> Sent: Tuesday, August 16, 2016 7:16 PM
>>>> To: The IESG <iesg@ietf.org>
>>>> Cc: draft-ietf-jose-cfrg-curves@ietf.org; Jim Schaad
>>>> <ietf@augustcellars.com>;
>>>> jose-chairs@ietf.org; ietf@augustcellars.com; jose@ietf.org
>>>> Subject: Ben Campbell's No Objection on draft-ietf-jose-cfrg-curves-05:
>>>> (with
>>>> COMMENT)
>>>>
>>>> Ben Campbell has entered the following ballot position for
>>>> draft-ietf-jose-cfrg-curves-05: 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-jose-cfrg-curves/
>>>>
>>>>
>>>>
>>>> ----------------------------------------------------------------------
>>>> COMMENT:
>>>> ----------------------------------------------------------------------
>>>>
>>>> I note that the reference to RFC7748 is a normative downref that does not
>>>> appear to be mentioned in the last call announcement. It’s not in the
>>>> downref
>>>> registry, but since it's an algorithm spec, it probably should be. I
>>>> don't suggest
>>>> any particular course of action; I merely bring it up in case people
>>>> hadn't already
>>>> noticed.
>>>>
>
>