IETF Logo Mail Archive

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

Stewart Bryant <stbryant@cisco.com> Wed, 25 June 2008 09:47 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 758B628C0D8; Wed, 25 Jun 2008 02:47:28 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DF9B43A69FF; Wed, 25 Jun 2008 02:47:26 -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 HQLXS7DiyvMO; Wed, 25 Jun 2008 02:47:25 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 464443A6946; Wed, 25 Jun 2008 02:47:25 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,701,1204498800"; d="scan'208";a="12612836"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 25 Jun 2008 11:47:26 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m5P9lQY5001122; Wed, 25 Jun 2008 11:47:26 +0200
Received: from stewart-bryants-computer.local (dhcp-10-61-98-218.cisco.com [10.61.98.218]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m5P9lPsS006947; Wed, 25 Jun 2008 09:47:25 GMT
Message-ID: <48621430.9040004@cisco.com>
Date: Wed, 25 Jun 2008 10:47:28 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis
References: <8832006D4D21836CBE6DB469@klensin-asus.vbn.inter-touch.net> <485590E2.3080107@gmail.com> <p06250116c47c330c7dd0@[75.145.176.242]> <4856DE3A.3090804@gmail.com> <C122F91B-59B0-49AC-ABBC-6752217C4E47@NOKIA.COM> <20080619024147.9146C3A6938@core3.amsl.com> <485A353B.30403@dcrocker.net> <20080619175645.0CA443A68C2@core3.amsl.com> <p06240601c480518c107f@[10.0.1.196]> <20080620182310.700613A6807@core3.amsl.com>
In-Reply-To: <20080620182310.700613A6807@core3.amsl.com>
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=664; t=1214387246; x=1215251246; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=stbryant@cisco.com; z=From:=20Stewart=20Bryant=20<stbryant@cisco.com> |Subject:=20Re=3A=20Appeal=20against=20IESG=20blocking=20DI SCUSS=20on=20draft-klensin-rfc2821bis |Sender:=20; bh=gWBi9L69nLCj0Q6ctT+JRE4Z0tbkQuqh//Z5eBp0NVg=; b=AA0mYPv01+lc9NOL+g52Ldh470CVg7SyPyjath46BOWk7l4XauPkhD5sHo CxUOLg1SzVRp3lTr6HMObAyWB3gd/VrXaBWFOFHukeNOuh+ljomTHVvG0r/Y 7o2MzyIzBL;
Authentication-Results: ams-dkim-1; header.From=stbryant@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; );
Cc: iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

>
> At least three ADs believe that the examples should be changed
>

I agree with them.

Use of any identifier outside the example space may cause real harm to
the owner, where that harm may range from serious harm (technical
and/or financial)  to mild embarrassment.

If anyone wants to use an identifier outside the example space, then to
protect both the owner  of the identifier and the IETF, the author really
needs to provide the IETF with evidence of  written authorization to use
it for this purpose.

In the case of this draft, have the owners of the identifiers
been contacted by the author, and do they agree to this use?

Stewart



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

v2.23.0 | Report a Bug | By Email