![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
By now, I'm hoping that the IESG has enough public and private feedback on this topic to do the right thing (whatever that is, and yes, I also have an opinion about what the IESG should be doing, which I'm not including here). Do we need to say more? If not, perhaps we could wait for the IESG to respond, and then do the right thing from our end, if needed. If we do need to say more, by all means, keep typing... Thanks, Spencer > No, you're not the only one seeing insanity. > > - Ralph > > On Jun 18, 2008, at Jun 18, 2008,12:44 PM, Bob Hinden wrote: > >> Hi, >> >> Let me see if I understand this. >> >> - This is the specification for SMTP. It's was first used on the >> Arpanet. >> >> - It is probably as widely deployed as IP and TCP. Maybe more so. >> >> - It works (e.g., the email discussing this thread was sent via SMTP). >> >> - The IETF is now advancing it to Draft Standard. I assume this means >> that we now have enough implementation experience. >> >> - Now the IESG doesn't want to approve it for Draft Standard because >> it is using a different set of example domains instead of the official >> IETF ones. >> >> Am I the only one who sees the insanity here? >> >> Bob >> >> >> _______________________________________________ >> IETF mailing list >> IETF at ietf.org >> httpFrom ietf-bounces at ietf.org Wed Jun 18 14:46:44 2008 Return-Path: <ietf-bounces at ietf.org> X-Original-To: ietf-archive at megatron.ietf.org Delivered-To: ietfarch-ietf-archive at core3.amsl.com Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 894E73A69AC; Wed, 18 Jun 2008 14:46:44 -0700 (PDT) X-Original-To: ietf at core3.amsl.com Delivered-To: ietf at core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A6CEA3A69AC; Wed, 18 Jun 2008 14:46:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.44 X-Spam-Level: X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[AWL=0.158, BAYES_00=-2.599, STOX_REPLY_TYPE=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IPe2UYy05mNr; Wed, 18 Jun 2008 14:46:39 -0700 (PDT) Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id A2B5C3A6782; Wed, 18 Jun 2008 14:46:39 -0700 (PDT) Received: from s73602 (cpe-72-190-0-23.tx.res.rr.com [72.190.0.23]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MKp8S-1K95Uz2y2e-0003os; Wed, 18 Jun 2008 17:47:27 -0400 Message-ID: <07fb01c8d18d$0da6ac80$ad600240 at china.huawei.com> From: "Spencer Dawkins" <spencer at wonderhamster.org> To: "ietf" <ietf at ietf.org> References: <8832006D4D21836CBE6DB469 at klensin-asus.vbn.inter-touch.net><485590E2.3080107 at gmail.com><p06250116c47c330c7dd0 at [75.145.176.242]><4856DE3A.3090804 at gmail.com><C122F91B-59B0-49AC-ABBC-6752217C4E47 at NOKIA.COM> <1E25AA8B-D143-4B35-8B41-B707EFA9CB8E at cisco.com> Subject: Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis Date: Wed, 18 Jun 2008 16:48:30 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Provags-ID: V01U2FsdGVkX180N+7QeLbhEZ/eTjeRPY21fw602Re96z/StS6 sgl9G0h3wF8Y/guVzJAW4WpJnjUswJCAg/LdupXx8AbH3G2pcq OgG+KoA6A9VIJ7SxY1sZonc6BvGJyRoIlrQr5kPVY4= Cc: IESG <iesg at ietf.org> X-BeenThere: ietf at ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Discussion <ietf.ietf.org> List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request at ietf.org?subject=unsubscribe> List-Archive: <http://www.ietf.org/pipermail/ietf> List-Post: <mailto:ietf at ietf.org> List-Help: <mailto:ietf-request at ietf.org?subject=help> List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request at ietf.org?subject=subscribe> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ietf-bounces at ietf.org Errors-To: ietf-bounces at ietf.org By now, I'm hoping that the IESG has enough public and private feedback on this topic to do the right thing (whatever that is, and yes, I also have an opinion about what the IESG should be doing, which I'm not including here). Do we need to say more? If not, perhaps we could wait for the IESG to respond, and then do the right thing from our end, if needed. If we do need to say more, by all means, keep typing... Thanks, Spencer > No, you're not the only one seeing insanity. > > - Ralph > > On Jun 18, 2008, at Jun 18, 2008,12:44 PM, Bob Hinden wrote: > >> Hi, >> >> Let me see if I understand this. >> >> - This is the specification for SMTP. It's was first used on the >> Arpanet. >> >> - It is probably as widely deployed as IP and TCP. Maybe more so. >> >> - It works (e.g., the email discussing this thread was sent via SMTP). >> >> - The IETF is now advancing it to Draft Standard. I assume this means >> that we now have enough implementation experience. >> >> - Now the IESG doesn't want to approve it for Draft Standard because >> it is using a different set of example domains instead of the official >> IETF ones. >> >> Am I the only one who sees the insanity here? >> >> Bob >> >> >> _______________________________________________ >> IETF mailing list >> IETF at ietf.org >> https://www.s://www.ietf.org/mailman/listinfo/ietf > > _______________________________________________ > IETF mailing list > IETF at ietf.org > https://www.ietf.org/mailman/listinfo/ietf > _______________________________________________ IETF mailing list IETF at ietf.org https://www.ietf.org/mailman/listinfo/ietf ietf.org/mailman/listinfo/ietf > > _______________________________________________ > IETF mailing list > IETF at ietf.org > https://www.ietf.org/mailman/listinfo/ietf > _______________________________________________ IETF mailing list IETF at ietf.org https://www.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.