Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis

From: Ralph Droms <rdroms at cisco.com>
To: bob.hinden at nokia.com
Cc: IESG <iesg at ietf.org>, ietf <ietf at ietf.org>
Date: Wed, 18 Jun 2008 17:27:46 -0400
In-reply-to: <C122F91B-59B0-49AC-ABBC-6752217C4E47 at NOKIA.COM>
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>

No, you're noFrom ietf-bounces at ietf.org  Wed Jun 18 14:26:59 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 92AC03A6B6F;
	Wed, 18 Jun 2008 14:26:59 -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 1F3333A6B5E;
	Wed, 18 Jun 2008 14:26:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5
	tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Ggdhk-qW2JDj; Wed, 18 Jun 2008 14:26:58 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70])
	by core3.amsl.com (Postfix) with ESMTP id 4FA793A6914;
	Wed, 18 Jun 2008 14:26:58 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,667,1204531200"; d="scan'208";a="42363227"
Received: from sj-dkim-1.cisco.com ([171.71.179.21])
	by sj-iport-1.cisco.com with ESMTP; 18 Jun 2008 14:27:47 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m5ILRlF8018728; 
	Wed, 18 Jun 2008 14:27:47 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.13.8/8.13.8) with ESMTP id m5ILRlCD022682;
	Wed, 18 Jun 2008 21:27:47 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 18 Jun 2008 14:27:47 -0700
Received: from tky-kokawaka-871-tu0.cisco.com ([10.21.78.182]) by
	xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 18 Jun 2008 14:27:47 -0700
Message-Id: <1E25AA8B-D143-4B35-8B41-B707EFA9CB8E at cisco.com>
From: Ralph Droms <rdroms at cisco.com>
To: bob.hinden at nokia.com
In-Reply-To: <C122F91B-59B0-49AC-ABBC-6752217C4E47 at NOKIA.COM>
Mime-Version: 1.0 (Apple Message framework v924)
Subject: Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis 
Date: Wed, 18 Jun 2008 17:27:46 -0400
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>
X-Mailer: Apple Mail (2.924)
X-OriginalArrivalTime: 18 Jun 2008 21:27:47.0224 (UTC)
	FILETIME=[27213980:01C8D18A]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=900; t=1213824467; x=1214688467;
	c=relaxed/simple; s=sjdkim1004;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=rdroms at cisco.com;
	z=From:=20Ralph=20Droms=20<rdroms at cisco.com>
	|Subject:=20Re=3A=20Appeal=20against=20IESG=20blocking=20DI
	SCUSS=20on=20draft-klensin-rfc2821bis=20 |Sender:=20;
	bh=sjcdKM6yWCRsnMGa6SD0ZmU4rOto0aN8xUS68A6lP44=;
	b=UulmkIIcCLvyISE/37GrJOCJLqc5ngAS4SjON+6EuDN097vNVNzlrHVT5c
	SOKl+qKswt/laG7QaEHUDEMSVS7G4BMGk23BgYHjEQw45nHHaFEZ78Rx6eL9
	joI+4qX+3wRKxfKywSs3coOr5mGy2/NyrS4thfgLYQrF/5r4WwtG0=;
Authentication-Results: sj-dkim-1; header.From=rdroms at cisco.com; dkim=pass (
	sig from cisco.com/sjdkim1004 verified; ); 
Cc: IESG <iesg at ietf.org>, ietf <ietf 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

No, you're not the ont 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.ietf.org/mailman/listinfo/ietf

_______________________________________________
IETF mailing list
IETF at ietf.org
https://www.ietf.org/mailman/listinfo/ietf


ly 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.ietf.org/mailman/listinfo/ietf

_______________________________________________
IETF mailing list
IETF at ietf.org
https://www.ietf.org/mailman/listinfo/ietf

Follow-Ups:
- Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis
  - From: Spencer Dawkins

References:
- RE: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis
  - From: John C Klensin
- Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis
  - From: Brian E Carpenter
- Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis
  - From: Pete Resnick
- Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis
  - From: Brian E Carpenter
- Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis
  - From: Bob Hinden

Prev by Date: Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis
Next by Date: Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis
Previous by thread: Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis
Next by thread: Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.