RE: Revised WG Charter Proposal

"Chris Apple" <[email protected]> Tue, 18 Mar 2003 19:49:00 -0500
Newsgroups gmane.ietf.ldup
Organization DSI-Consulting, Inc.
Message-ID <000001c2edb1$550b1860$082d390a@D7ST2111>
It was my intent to be fuzzy about the end game milestones.

This milestone is where documents would leave the WG (after they
pass through a last call successfully).

>AUG 03  Consider which documents are ready for WG Last Call and establish
sequencing.

You are correct about the additional WG Last Call for LCUP. An error that I
will correct with the next revision of the WG Charter Proposal.

My intent behind the SEP 03 milestone is that it's a drop dead date.

If all of the documents are not at least ready to enter WG Last Call by this
date, we will have missed the schedule by too much to justify continuing and
"the
plug will be pulled." I expect that we will have a number of documents that
have
Actually passed WG Last Call before then. However, given the WG's history, I
think
its prudent to have a drop dead date in mind.

We may change the wording of the milestone so that this intent is more
clear.

Chris Apple - Principal Architect

DSI Consulting, Inc.

mailto:[email protected]

http://www.dsi-consulting.com

-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Mark C Smith
Sent: Tuesday, March 18, 2003 9:17 AM
To: [email protected]
Cc: [email protected]
Subject: Re: Revised WG Charter Proposal



Chris Apple wrote:
>
> MAY 03  Revise LDAPv3 Client Update Protocol I-D.

Since LCUP has already been through one WG last call, I would expect it 
to be ready for another one, followed by submission to the IESG in the 
May or June 2003 timeframe. LCUP has no dependencies on the core LDUP 
replication documents.


> SEP 03  Reevaluate Charter and Milestones

Are the area directors going to be happy with this? I don't see any date 
on the proposed charter for when a document leaves the working group, 
which seems strange to me.

-- 
Mark Smith
Netscape Directory Product Development
My words are my own, not my employer's.