IETF Logo Mail Archive

Re: RFC Editor RFP Review Request

"todd glassey" <tglassey@earthlink.net> Sun, 23 July 2006 17:04 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G4hNW-00061W-OM; Sun, 23 Jul 2006 13:04:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G4hNV-000612-92; Sun, 23 Jul 2006 13:04:29 -0400
Received: from elasmtp-kukur.atl.sa.earthlink.net ([209.86.89.65]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G4hNU-0006ra-1S; Sun, 23 Jul 2006 13:04:29 -0400
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=gZntMsAVb4JmAxFi7yTb/7BJHJsvCPG97BjxsNke1fLshONM3aqvlC7xIs+T71UY; h=Received:Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MIMEOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [4.246.45.251] (helo=gw) by elasmtp-kukur.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1G4hNT-0001kN-37; Sun, 23 Jul 2006 13:04:27 -0400
Message-ID: <00c501c6ae7a$142a7dd0$ca2df604@home.glassey.com>
From: todd glassey <tglassey@earthlink.net>
To: Eliot Lear <lear@cisco.com>
References: <200607182242.PAA05134@gra.isi.edu><44BD71E0.5030005@levkowetz.com> <44C1D1E4.9050400@cisco.com> <002a01c6ad8e$242bf660$ca2df604@home.glassey.com> <44C24AC6.8040707@cisco.com>
Date: Sun, 23 Jul 2006 10:04:29 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1807
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79b37e7a0e8b3ee3f50037a4e833f3a09c350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 4.246.45.251
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: iaoc@ietf.org, iad@ietf.org, iab@ietf.org, ietf@ietf.org, iesg@ietf.org
Subject: Re: RFC Editor RFP Review Request
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

Eliot - BTW
What's the difference between an RFP and an RFC by the way? - don't both
require some review process for the "Request for" part of it?

Just asking as its a semantics issue .

T
----- Original Message ----- 
From: "Eliot Lear" <lear@cisco.com>
To: "todd glassey" <tglassey@earthlink.net>
Cc: <iad@ietf.org>; <iab@ietf.org>; <ietf@ietf.org>; <iaoc@ietf.org>;
<iesg@ietf.org>
Sent: Saturday, July 22, 2006 8:56 AM
Subject: Re: RFC Editor RFP Review Request


> todd glassey wrote:
> > Elliot -
> > Then you leave it up to the party providing the service and open the
IETF to
> > all kinds of trouble... By the way Elliot do you think your sponsor,
Cisco
> > and their Legal department would let Cisco negotiate a contract like
that?
> > Just curious
> >
>
> For an RFP, you bet.  Our vendors are out to compete with one another.
> Why would any sane buyer want to limit that?
>
> Eliot


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email