Re: Publication of EMSD as an Informational RFC

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

Some facts: The IETF does commission the RFC publication service. 
The IAB, a committee of the IETF, does managerially oversee the
RFC Editor. The ISOC, the legal entity that supports the IETF,
does pay for the RFC publication service on behalf of the IETF.

  Brian Carpenter

Mohsen BANAN wrote:
> 
> Of course none of this part of these discussions is
> specifically related to EMSD in particular.
> 
> We are talking about who should be running the RFC
> Publication Service, how it is being run and how it
> should be run.
> 
> >>>>> On Fri, 18 Dec 1998 15:39:44 -0500, Steve Bellovin <smb@research.att.com> said:
> 
>   Steve> In message <199812182016.MAA26549@rostam.neda.com>, Mohsen BANAN writes:
> 
>   Mohsen>
>   Mohsen> - The Internet technical community needs a STRONG and
>   Mohsen> INDEPENDENT RFC Editor so that *NON-IETF*,
>   Mohsen> *NON-standards-track* documents can be published in a
>   Mohsen> reasonable manner.
> 
>   Steve> Why?  Why should the IETF run a publication service for you?
> 
> I don't want the IETF to run the RFC Publication
> Service for me.
> 
> It is very disturbing, but it is a fact, that at
> least some members of the IAB think that IETF is
> (or should be) running the RFC Publication Service.
> 
> It was precisely in anticipation of this which I
> had started to CC Mr. Cerf on this thread.
> 
> After all is said and done, it boils down to where
> the funding for the RFC Publication Service comes
> from and how is accountability, responsibility and
> transparency structured into the RFC publication
> service.
> 
> Based on Mr. Cerf's comments, the RFC Publication
> Service is to be funded by the ISOC funds which
> in some ways represents the Internet community. Not
> the IETF.
> 
> For as long as RFC 2026 is authoritative, the RFC
> Publication Service belongs to the entire Internet
> community, not just IETF/IESG/IAB.
> 
> By now, it should be clear to you that in addition
> to the publication of EMSD in particular I am quite
> concerned about the process of publication of
> Non-IETF, Non-standards-track documents in general.
> 
> Based on my interations with the IESG/IAB and the
> RFC Editor, it is clear to me that the letter and
> the spirit of RFC 2026 is not being respected.  Now
> in addition to IETF/IESG/IAB and the RFC Editor, I
> have brought this problem to the attention of
> Mr. Cerf as an ISOC leader.
> 
> ...Mohsen.