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

[Tim Polk <tim.polk@xxxxxxxx>]

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, 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 ?