ESRO ID

• To: iesg-secretary@ietf.org, JBCheng@attws-hq1.nwest.attws.com, mohsen@neda.com, mtaylor@teledesic.com, pean@neda.com
• Subject: ESRO ID
• From: Scott Bradner <sob@harvard.edu>
• Date: Thu, 7 Aug 1997 15:43:37 -0400 (EDT)
• Cc: allyn@eng.sun.com
• Content-Length: -790
• Content-Type: text

I have exchanged mail with the ex transport co-AD about this ID.  She feels
that this ID represents a significant technical contribution and feels that
it should be advanced on the IETF standards track.

The normal way to do that with a non-working group document is to issue
a 4 week last-call to the general IETF community announcing the intention
of the IESG to evaluate the ID as a Proposed Standard and asking for 
comments.  After the end of that last-call period the IESG would
evaluate the responses and proceed.

If this is valuable technology then it would be a shame to miss
the chance to get it on the standards track by a quick publication as 
an informational RFC (yes we could publish it as an info then do the
last call but that would be unusual and potentially confusing later
on when the RFC is referred to)

So - I'd like the authors of the ID to let me know how you would like
to proceed.  I'm quite willing to be the IESG shepard for the ID if
you are interested in proceeding to a last call.

Scott

• Follow-Ups:
  • Re: ESRO ID
    • From: Mohsen Banan <mohsen@neda.com>

• Prev by Date: Re: Now: Improving the Informational RFCs Publication Process both in Theory and in Practice -- Was: Re:Unexpected and Unreasonable delays in processing of Informational
• Next by Date: Now: Improving the Informational RFCs Publication Process both in Theory and in Practice -- Was: Re:Unexpected and Unreasonable delays in processing of Informational
• Prev by thread: Re: Now: Improving the Informational RFCs Publication Process both in Theory and in Practice -- Was: Re:Unexpected and Unreasonable delays in processing of Informational
• Next by thread: Re: ESRO ID
• Index(es):
  • Date
  • Thread