Re: Publication of EMSD as an Informational RFC

• To: Robert Moskowitz <rgm@htt-consult.com>
• Subject: Re: Publication of EMSD as an Informational RFC
• From: Mohsen BANAN <mohsen@neda.com>
• Date: Fri, 18 Dec 1998 12:16:27 -0800 (PST)
• Cc: Brian E Carpenter <brian@hursley.ibm.com>, rfc-ed@ISI.EDU, iesg@ISI.EDU, records@neda.com, Internet Architecture Board <iab@ISI.EDU>, "vinton g. cerf" <vcerf@mci.net>
• Content-Length: 1258
• Content-Type: text/plain; charset=US-ASCII
• In-Reply-To: <4.1.19981218121955.00c2a4e0@homebase.htt-consult.com>
• References: <199812160927.BAA23056@rostam.neda.com><367A5446.AC03EB46@hursley.ibm.com><4.1.19981218121955.00c2a4e0@homebase.htt-consult.com>

>>>>> On Fri, 18 Dec 1998 12:20:54 -0500, Robert Moskowitz <rgm@htt-consult.com> said:

  Robert> Did you catch this guy's rant on IETF that the IETF needs to take control
  Robert> of the RFC process becuase anyone can 'no longer' publish?

You seem to have completely missed the points of my "rant".

I suggest you read my messages again.

I have NEVER suggested that IETF needs to take control of
the RFC process.

Let me summarize for you the consistent points that I
have been making since Feb. of last year -- and even
before that -- in the form of simple bullets so that you
may have a better chance of understanding them:

  - The Internet technical community needs a STRONG and
    INDEPENDENT RFC Editor so that *NON-IETF*,
    *NON-standards-track* documents can be published in a
    reasonable manner.

  - The purpose and scope of the IESG review/referral
    should be limited to what RFC 2026 says its should
    be. That is: identification of conflicts of the
    document with the IESG/IETF's work. Anything more
    than that runs into IESG's  conflict of interest
    problem.

  - In practice, the RFC Editor appears too weak.

  - In practice, the IESG/I... appears too power hungry
    and out of control.


Got it?


...Mohsen.

  

Replies

Publication of EMSD as an Informational RFC, Mohsen BANAN

Re: Publication of EMSD as an Informational RFC, Brian E Carpenter

Re: Publication of EMSD as an Informational RFC, Robert Moskowitz

Re: Publication of EMSD as an Informational RFC, Robert Moskowitz

• Prev by Date: Re: Publication of EMSD as an Informational RFC
• Next by Date: Re: Publication of EMSD as an Informational RFC
• Prev by thread: Re: Publication of EMSD as an Informational RFC
• Next by thread: Re: Publication of EMSD as an Informational RFC
• Index(es):
  • Date
  • Thread