Re: ANNOUNCEMENT: The IETF Trustees invite your comments on ...

"Doug Ewell" <doug@ewellic.org> Sat, 24 January 2009 17:40 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 1F14E28C1E2; Sat, 24 Jan 2009 09:40:05 -0800 (PST)
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 8905428C0F2 for <ietf@core3.amsl.com>; Sat, 24 Jan 2009 09:40:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.123
X-Spam-Level:
X-Spam-Status: No, score=-1.123 tagged_above=-999 required=5 tests=[AWL=-0.384, BAYES_20=-0.74, 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 VKxTYcLkaASV for <ietf@core3.amsl.com>; Sat, 24 Jan 2009 09:40:03 -0800 (PST)
Received: from smtpout04-02.prod.mesa1.secureserver.net (smtpout04-01.prod.mesa1.secureserver.net [64.202.165.196]) by core3.amsl.com (Postfix) with SMTP id BDED628C1E2 for <ietf@ietf.org>; Sat, 24 Jan 2009 09:40:03 -0800 (PST)
Received: (qmail 8556 invoked from network); 24 Jan 2009 17:39:46 -0000
Received: from unknown (67.177.232.210) by smtpout04-04.prod.mesa1.secureserver.net (64.202.165.199) with ESMTP; 24 Jan 2009 17:39:45 -0000
Message-ID: <B5720E65D2354F659809CA433C4D0C59@DGBP7M81>
From: Doug Ewell <doug@ewellic.org>
To: ietf@ietf.org
References: <20090124154913.53426.qmail@simone.iecc.com>
Subject: Re: ANNOUNCEMENT: The IETF Trustees invite your comments on ...
Date: Sat, 24 Jan 2009 10:39:43 -0700
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
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-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: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

John Levine <johnl at iecc dot com> wrote:

> Nonetheless, I can't help but seeing angels dancing on pins here. 
> We're worrying about situations in which someone contributes material 
> to the IETF that ended up in an RFC, then later goes to court and 
> claims to be shocked and injured that someone else used his material 
> in ways that RFCs are routinely used, i.e., someone acts like a 
> complete jerk.

It could happen.  Remember that some people who participate in a WG, and 
contribute one or two bits of information that make their way into the 
RFC, are unhappy overall with that group's rough consensus.  Not all 
"contributions" are positive or direct; an author might add wording 
specifically to ward off a rogue interpretation that someone in the WG 
"contributed."  If you think this is improbable, read some of the 
appeals that the IESG has had to address in the past 3 years or so.

--
Doug Ewell  *  Thornton, Colorado, USA  *  RFC 4645  *  UTN #14
http://www.ewellic.org
http://www1.ietf.org/html.charters/ltru-charter.html
http://www.alvestrand.no/mailman/listinfo/ietf-languages  ˆ

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