Re: A request to publish draft-moskowitz-hip-arch-05.txt as an Informational RFC

[RFC Editor <rfc-editor@rfc-editor.org>]

Greetings,

Thank you for your submission.  The RFC Editor has received your
proposed RFC, and will review the document.  Once the RFC Editor has
reviewed this draft, we will send it to the IESG for a 4 week timeout,
allowing the IESG time to review and comment on this effort.

You can track the progress of your document at:

   http://www.rfc-editor.org/queue.html

Please note that your document will be removed from our queue and
treated as a new submission if we send it back to you for revisions. 

Thank you.

RFC Editor



On Mon, Oct 27, 2003 at 08:43:03AM +0200, Pekka Nikander wrote:
> Dear RFC Editor,
> 
> As discussed earlier with Bob Braden, we hereby request
> publication of draft-moskowitz-hip-arch-05.txt as an
> Informational RFC, as per RFC2026 Section 4.2.3.
> 
> The draft has undergone an unofficial Last Call at the
> hipsec mailing list <hipsec@honor.trusecure.org>, with
> all raised issues resolved, and was announced at the IETF
> discuss mailing list on Oct 23.  See
> http://www1.ietf.org/mail-archive/ietf/Current/msg22714.html
> The latter announcement has generated no comments.
> 
> While we believe that the document is mature in the sense
> that it reflects the current thinking of the people working
> with HIP, this is the first time Pekka is submitting a
> concrete draft to be published as an RFC.  Hence, there are
> probably nits that he has missed.  Furthermore, Pekka has
> requested reviews on the document from Dave Crocker and
> Spencer Dawkins, and expects to receive comments in two weeks
> or sooner.  The idea is that those review comments could be
> processed together with the comments from the RFC Editor and/or
> from the IESG.  If this does not fit in the process, please
> advice us, and accept apologies from Pekka.
> 
> The draft is enclosed in xml2rfc format.
> 
> --Pekka Nikander & Bob Moskowitz
>