Re: Assignment of RFC numbers

[Tony Jeffree <tony@jeffree.co.uk>]

Harald -

Did numbers get assigned yet for:

draft-aboba-radius-rfc2869bis-22.txt
draft-congdon-radius-8021x-29.txt

?

Regards,
Tony

At 10:00 05/06/2003 +0200, Harald Tveit Alvestrand wrote:
> Tony,
>
> the 7 month figure is, fortunately, grossly inaccurate at this point. But 
> no guarantees....
>
> What is your actual deadline for the insertion of RFC numbers?
> We have had occasions in the past where an RFC number has been circulated 
> widely before the RFC was published, leading to lots of unproductive 
> queries for the state of the "missing" RFC, so we'd prefer to keep the 
> numbers out of wide circulation before publication, if possible.
>
>                   Harald
>
>
> --On tirsdag, juni 03, 2003 18:48:10 +0100 Tony Jeffree 
> <tony@jeffree.co.uk> wrote:
>
> > To whom it may concern:
> > _______________________
> >
> > The IESG has now approved the following documents for publication:
> >
> > draft-aboba-radius-rfc2869bis-22.txt
> > draft-congdon-radius-8021x-29.txt
> > draft-chiba-radius-dynamic-authorization-20.txt
> > draft-aboba-radius-iana-07.txt
> >
> > Each of these drafts is referenced by an IEEE standards development
> > project, IEEE P802.1aa, which is reaching the point where the text will
> > need to be updated to reflect the final RFC references that will be
> > assigned to these documents.
> >
> > We understand that documents are currently taking up to 7 months or more
> > for publication as RFCs after approval.  In order to avoid delaying IEEE
> > P802.1aa, I would request to the IESG that RFC #s and final titles be
> > assigned to these documents as soon as possible, so that they can be
> > properly referenced in IEEE P802.1aa. I would be grateful if you could
> > let me know whether this is possible, and what the proper references for
> > these RFCs should be.
> >
> >
> > Regards,
> > Tony Jeffree
> > Chair, IEEE 802.1 Working Group.

Regards,
Tony