Re: [lamps] shepherd writeup: draft-ietf-lamps-ocsp-nonce/

Russ Housley <housley@vigilsec.com> Wed, 03 June 2020 16:15 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FEE83A07FC for <spasm@ietfa.amsl.com>; Wed, 3 Jun 2020 09:15:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 SJaY1mn4owVi for <spasm@ietfa.amsl.com>; Wed, 3 Jun 2020 09:15:50 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CA323A0E22 for <spasm@ietf.org>; Wed, 3 Jun 2020 09:15:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id BF51F300AEF for <spasm@ietf.org>; Wed, 3 Jun 2020 12:15:01 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id gYWT9QGn2tMz for <spasm@ietf.org>; Wed, 3 Jun 2020 12:14:59 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (pool-72-66-113-56.washdc.fios.verizon.net [72.66.113.56]) by mail.smeinc.net (Postfix) with ESMTPSA id AC73B300A93; Wed, 3 Jun 2020 12:14:59 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <ABF41FF5-2B17-4A39-92BF-86044980FEAE@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2175CAE6-F5DE-4BBA-9B2E-54A703D28A25"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Date: Wed, 03 Jun 2020 12:15:00 -0400
In-Reply-To: <CAEpwuw1c02cG0Z73ohbMvAAZrSURKjop=adJNbK-+F8siMPyWw@mail.gmail.com>
Cc: LAMPS <spasm@ietf.org>
To: Mohit Sahni <mohit06jan@gmail.com>
References: <79037008-09ED-4E31-BA8C-1DC4F24E1687@vigilsec.com> <16418846-B43A-45E5-BB28-B89169AE6523@akamai.com> <D3785CC2-7AFB-49C4-BDF3-52C365A2B35D@vigilsec.com> <CAEpwuw1c02cG0Z73ohbMvAAZrSURKjop=adJNbK-+F8siMPyWw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.14)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/pQ8yB6k5KFvdXrAKwQ8jWeNRspo>
Subject: Re: [lamps] shepherd writeup: draft-ietf-lamps-ocsp-nonce/
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2020 16:15:52 -0000

I was waiting to see is anyone raised concerns with the write-up.  No one did.

The document is now with the IESG.  You can see the states in the IESG process here: https://datatracker.ietf.org/help/state/draft/iesg <https://datatracker.ietf.org/help/state/draft/iesg>

Russ


> On Jun 2, 2020, at 10:09 PM, Mohit Sahni <mohit06jan@gmail.com> wrote:
> 
> {OFF LIST}
> 
> Hi Russ,
> I am sorry I am not aware of the whole process, just wanted to check what are the next steps now? Is there anything pending on my end?
> 
> Thanks
> Mohit
> 
> On Mon, May 18, 2020 at 10:02 AM Russ Housley <housley@vigilsec.com <mailto:housley@vigilsec.com>> wrote:
> Thanks for catching my failure to answer the proper question.  Now fixed:
> 
> (11) Identify any ID nits the Document Shepherd has found in this
> document.  (See http://www.ietf.org/tools/idnits/ <http://www.ietf.org/tools/idnits/> and the Internet-Drafts
> Checklist).  Boilerplate checks are not enough; this check needs to be
> thorough.
> 
>   IDnits reports:
>   -- The draft header indicates that this document updates RFC6960, but the
>      abstract doesn't seem to directly say this.  It does mention RFC6960
>      though, so this could be OK.
>   The Abstract includes "This document updates the RFC 6960"..
>   This warning seems to be the result of "the" or a missing period.
> 
> Russ
> 
> > On May 18, 2020, at 10:56 AM, Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org <mailto:40akamai.com@dmarc.ietf.org>> wrote:
> > 
> > Is the answer to #11 a non-sequiture?  (However you spell it.)
> > 
> > It also specifies a recommendation for minimum, is that worth mentioning?
> > 
> > 
> > On 5/16/20, 2:21 PM, "Russ Housley" <housley@vigilsec.com <mailto:housley@vigilsec.com>> wrote:
> > 
> >    https://datatracker.ietf.org/doc/draft-ietf-lamps-ocsp-nonce/shepherdwriteup/ <https://datatracker.ietf.org/doc/draft-ietf-lamps-ocsp-nonce/shepherdwriteup/>
> > 
> >    Please review and comment.
> > 
> >    Russ
> 
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org <mailto:Spasm@ietf.org>
> https://www.ietf.org/mailman/listinfo/spasm <https://www.ietf.org/mailman/listinfo/spasm>
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm