Re: IESG's Review of EMSD Specification

[Brian E Carpenter <brian@hursley.ibm.com>]

I think you are failing to understand that the RFC series is
the IETF's publication mechanism, paid for by the Internet
Society on behalf of the IETF. That doesn't remove the RFC Editor's
discretion to publish non-IETF documents, but it does give the
IETF the right to comment.

    Brian

Mohsen BANAN wrote:
> 
> >>>>> On Thu, 11 Feb 1999 11:15:43 +0000, Brian E Carpenter <brian@hursley.ibm.com> said:
> 
>   Brian> Mohsen BANAN wrote:
>   Brian> ...
>   >>
>   >> After all that we have gone through in the
>   >> case of this Informational RFC, at this
>   >> point, the IESG has the RESPONSIBILITY of
>   >> doing its part towards the completion of
>   >> publication of this NON IETF, NON STANDARDS
>   >> TRACK, Informational RFC in a timely manner.
> 
>   Brian> As you have been told several times, the IETF is under
>   Brian> no obligation to publish anything for anybody at any time.
> 
> Brian,
> 
> Can you please refer me to the procedures that you think
> we should be following?
> 
> EMSD is a NON IETF Informational RFC.
> 
> RFC-2026 says something like:
> 
>    If  the IESG considers that the document proposes
>    something that conflicts with, or is actually inimical to, an
>    established IETF effort, the document may still be published as an
>    Experimental or Informational RFC.  In these cases, however, the IESG
>    may insert appropriate "disclaimer" text into the RFC either in or
>    immediately following the "Status of this Memo" section in order to
>    make the circumstances of its publication clear to readers.
> 
> The spirit of that section is to accommodate parallel
> experimentation and to introduce competition amongst
> protocols.  Right?
> 
> The idea there is that no one group has exclusivity
> on good ways and good ideas and that RFC publication
> can help parallel experimentation. Right?
> 
> ...Mohsen.