Re: tentative timeline for TSP (was Re: PKIX WG tentative agenda)

Tim Polk <tim.polk@nist.gov> Fri, 08 December 2000 14:22 UTC

Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA20519 for <pkix-archive@odin.ietf.org>; Fri, 8 Dec 2000 09:22:53 -0500 (EST)
Received: from localhost (daemon@localhost) by ns.secondary.com (8.9.3/8.9.3) with SMTP id GAA06858; Fri, 8 Dec 2000 06:19:40 -0800 (PST)
Received: by mail.imc.org (bulk_mailer v1.12); Fri, 8 Dec 2000 06:19:33 -0800
Received: from email.nist.gov (email.nist.gov [129.6.2.7]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id GAA06818 for <ietf-pkix@imc.org>; Fri, 8 Dec 2000 06:19:32 -0800 (PST)
Received: from st25 (st25.ncsl.nist.gov [129.6.54.67]) by email.nist.gov (8.9.3/8.9.3) with ESMTP id JAA05446; Fri, 8 Dec 2000 09:21:38 -0500 (EST)
Message-Id: <4.2.0.58.20001208091819.01c19ef0@email.nist.gov>
X-Sender: wpolk@email.nist.gov
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58
Date: Fri, 08 Dec 2000 09:19:27 -0500
To: Denis Pinkas <Denis.Pinkas@bull.net>
From: Tim Polk <tim.polk@nist.gov>
Subject: Re: tentative timeline for TSP (was Re: PKIX WG tentative agenda)
Cc: Jean-Marc Desperrier <jean-marc.desperrier@certplus.com>, ietf-pkix <ietf-pkix@imc.org>
In-Reply-To: <3A309863.5F3A6D58@bull.net>
References: <4.2.0.58.20001206163753.01d70660@email.nist.gov> <4.2.0.58.20001207130621.01c41270@email.nist.gov>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Precedence: bulk
List-Archive: http://www.imc.org/ietf-pkix/mail-archive/
List-ID: <ietf-pkix.imc.org>
List-Unsubscribe: mailto:ietf-pkix-request@imc.org?body=unsubscribe

Denis,

Thanks for the reminder!  I was simply using the IESG status listing, which 
still says "Under AD Review".  That reduces the timeline a bit...

Tim

At 09:14 AM 12/8/00 +0100, Denis Pinkas wrote:
>Tim,
>
> > Jean-Marc,
> >
> > The IESG process does not operate on a fixed schedule, so we really can't
> > predict when an RFC number might be available.  The IETF process consists
> > of repeated discussion and debate regarding the merits of a
> > specification.  At any stage, we could conceivably discover a problem that
> > needs to be resolved.  Every problem that is encountered will take
> > additional time.
> >
> > TSP has several hurdles to cross. Once the ADs are satisfied, TSP will
> > still need to go through IETF Last Call, be approved by the IESG,
>
>Wake-up ! Last call at the IESG level has already been performed on Monday,
>28 Aug 2000
>
>Here is the quoted E-mail:
>
>" The IESG has received a request from the Public-Key Infrastructure
>(X.509) Working Group to consider Internet X.509 Public Key
>Infrastructure Time Stamp Protocols (TSP)
><draft-ietf-pkix-time-stamp-09.txt> as a Proposed Standard.
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action.  Please send any comments to the
>iesg@ietf.org or ietf@ietf.org mailing lists by September 8, 2000."
>
>Denis
>
> > and wait
> > in the IETF editing queue.  After successfully completing this process, it
> > will get an RFC number.  (Note that IETF Last Call is a minimum of two
> > weeks, and documents seem to be spending at least a month in the editing
> > queue.  Many documents spend more time in each stage.)
> >
> > I expect TSP to go through the process rather cleanly.  My experience is
> > that documents which survive PKIX itself are already fairly well scrubbed.
> >
> > Tim Polk
> >
> > At 01:33 PM 12/7/00 +0100, Jean-Marc Desperrier wrote:
> > >Tim Polk wrote:
> > >
> > > > I have attached the tentative agenda for next week's PKIX 
> sessions.   As
> > > > usual, we have a rather full agenda.  Both days should be
> > > > interesting;  we'll discuss the path validation protocols on 
> Tuesday and
> > > > XML on Wednesday.  In between, we'll cover the status of our twenty 
> current
> > > > I-Ds.
> > >
> > >The agenda says the WG Last call for Time Stamp Protocols draft (TSP) is
> > >finished, and that the draft is now under Area Director Review.
> > >
> > >What would be a tentative time-line until publication as an RFC, or until
> > >attribution of a RFC number ?
> > >
> > >