Re: draft-rfced-info-banan-00.txt (EMSD)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: draft-rfced-info-banan-00.txt (EMSD)
- To: Keith Moore <moore@cs.utk.edu>
- Subject: Re: draft-rfced-info-banan-00.txt (EMSD)
- From: Mohsen BANAN <mohsen@neda.com>
- Date: Mon, 9 Nov 1998 12:44:48 -0800 (PST)
- Cc: Fred Baker <fred@cisco.com>, scoya@ietf.org, iesg@ietf.org, RFC Editor <rfc-ed@isi.edu>, records@neda.com, Internet Architecture Board <iab@isi.edu>
- Content-Length: 910
- Content-Type: text/plain; charset=US-ASCII
- In-Reply-To: <199811092023.PAA10495@spot.cs.utk.edu>
- References: <199811080755.XAA18455@rostam.neda.com><199811092023.PAA10495@spot.cs.utk.edu>
>>>>> On Mon, 09 Nov 1998 15:23:17 -0500, Keith Moore <moore@cs.utk.edu> said: Keith> Moshen, Keith> I've already fulfilled my responsibility by reviewing your document Keith> and making a recommendation to the RFC Editor that it not be Keith> published. Keith> Further dialog with you doesn't seem likely to be constructive. As I said before, I want this done by the book. Am I correct to assume that this is an IESG position and not just yours? Further, the scope and purpose of the referral to the IESG by the RFC Editor of draft-rfced-info-banan-00.txt is well defined in RFC 2026. I am assuming that based on paragraph 3, section 4.2.3 of RFC 2026, the IESG considers that draft-rfced-info-banan-00.txt proposes something that conflicts with, or is actually inimical to, an established IETF effort. For the record, can the IESG please tell me what that is? Regards, ...Mohsen.
- Replies
- Re: draft-rfced-info-banan-00.txt (EMSD), Mohsen BANAN
- Re: draft-rfced-info-banan-00.txt (EMSD), Keith Moore
- Re: draft-rfced-info-banan-00.txt (EMSD), Keith Moore
- Prev by Date: Re: draft-rfced-info-banan-00.txt (EMSD)
- Next by Date: Re: Re: draft-rfced-info-banan-00.txt (EMSD)
- Prev by thread: Re: draft-rfced-info-banan-00.txt (EMSD)
- Next by thread: Re: draft-rfced-info-banan-00.txt
- Index(es):