IETF Logo Mail Archive

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

Julian Reschke <julian.reschke@gmx.de> Wed, 25 June 2008 10:01 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 2052528C110; Wed, 25 Jun 2008 03:01:17 -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 09FCE28C106 for <ietf@core3.amsl.com>; Wed, 25 Jun 2008 03:01:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.549
X-Spam-Level:
X-Spam-Status: No, score=-4.549 tagged_above=-999 required=5 tests=[AWL=-1.950, BAYES_00=-2.599]
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 54d78sRTPBln for <ietf@core3.amsl.com>; Wed, 25 Jun 2008 03:01:10 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id F1EFB3A687F for <ietf@ietf.org>; Wed, 25 Jun 2008 03:01:09 -0700 (PDT)
Received: (qmail invoked by alias); 25 Jun 2008 10:01:10 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.106]) [217.91.35.233] by mail.gmx.net (mp055) with SMTP; 25 Jun 2008 12:01:10 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19b3pI8/ZpbSoaYtEguBqJdW0Jo9hJAw9E7rGptMh TvuJjikif3ORk0
Message-ID: <4862175F.9020709@gmx.de>
Date: Wed, 25 Jun 2008 12:01:03 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: stbryant@cisco.com
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> <48621430.9040004@cisco.com>
In-Reply-To: <48621430.9040004@cisco.com>
X-Y-GMX-Trusted: 0
Cc: ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@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@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

Stewart Bryant wrote:
> 
>>
>> 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?

You are aware that the same examples have been in a published RFC for 
over seven years?

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

v2.23.0 | Report a Bug | By Email