Re: One last nit

Steve Coya <scoya@CNRI.Reston.VA.US> Fri, 17 March 1995 16:59 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04583; 17 Mar 95 11:59 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa04579; 17 Mar 95 11:59 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa10800; 17 Mar 95 11:59 EST
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa04572; 17 Mar 95 11:59 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa04568; 17 Mar 95 11:59 EST
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa10795; 17 Mar 95 11:59 EST
Received: from [127.0.0.1] by IETF.CNRI.Reston.VA.US id aa04561; 17 Mar 95 11:59 EST
To: John C Klensin <klensin@mail1.reston.mci.net>
cc: iesg@CNRI.Reston.VA.US
Subject: Re: One last nit
In-reply-to: Your message of "Fri, 17 Mar 95 10:37:12 EST." <01HO8MW2B3QI000BKG@MAIL1.RESTON.MCI.NET>
Date: Fri, 17 Mar 1995 11:59:48 -0500
X-Orig-Sender: iesg-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Steve Coya <scoya@CNRI.Reston.VA.US>
Message-ID: <9503171159.aa04561@IETF.CNRI.Reston.VA.US>

John,

>> the reason why we distinguish between two-week and four-week last
>> calls is that the latter permits members of the community who are
>> interested in the work, but surprised, to come up to speed... while we
>> presume that the existence of an active WG (note "active") acts as
>> sufficient "you better be up to speed, something may emerge" notice
>> that we can use a shorter period.

ONCRPC is still an active WG. The chair did actually submit the two
I-Ds for consideration as Proposed Standards to the IESG, but the AD
said this would not happen until the agreement had been reached.

I will also note that an AD (or the IESG) can, AT ANY TIME, decide that
an extended Last Call period be invoked. I believe this was done for
the IPNG recommendation.


Steve