Re: Possible RFC 3683 PR-action
"Frank Ellermann" <nobody@xyzzy.claranet.de> Tue, 01 April 2008 21:43 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 core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 08D3D28C132; Tue, 1 Apr 2008 14:43:00 -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 C146F3A6BC8 for <ietf@core3.amsl.com>; Tue, 1 Apr 2008 14:42:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.532
X-Spam-Level:
X-Spam-Status: No, score=-1.532 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_NUMERIC_HELO=2.067]
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 P3-ZArr52A-n for <ietf@core3.amsl.com>; Tue, 1 Apr 2008 14:42:58 -0700 (PDT)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by core3.amsl.com (Postfix) with ESMTP id CEC383A6B80 for <ietf@ietf.org>; Tue, 1 Apr 2008 14:42:57 -0700 (PDT)
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JgoFn-0004JL-SJ for ietf@ietf.org; Tue, 01 Apr 2008 21:42:51 +0000
Received: from 212.82.251.148 ([212.82.251.148]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Tue, 01 Apr 2008 21:42:51 +0000
Received: from nobody by 212.82.251.148 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Tue, 01 Apr 2008 21:42:51 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Subject: Re: Possible RFC 3683 PR-action
Date: Tue, 01 Apr 2008 23:45:04 +0200
Organization: <http://purl.net/xyzzy>
Lines: 17
Message-ID: <fsua8i$7hc$1@ger.gmane.org>
References: <002801c88988$bba6fda0$6801a8c0@oemcomputer><004101c88ac1$f57d2600$6801a8c0@oemcomputer><5b0cbc7c0803201738s6138a1a4m2fbb546286a9c2ed@mail.gmail.com><47e4022e.14025a0a.2c46.2519SMTPIN_ADDED@mx.google.com><5b0cbc7c0803220222x5b345773oe11dcadc448b7635@mail.gmail.com><20080322193659.527613A692F@core3.amsl.com><8EFB68EAE061884A8517F2A755E8B60A02C693ACF4@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com> <20080401204108.GA4139@sources.org>
Mime-Version: 1.0
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: 212.82.251.148
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1914
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.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-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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
Stephane Bortzmeyer wrote: > If this is true, he cannot post on IETF mailing lists and > should be banned of "Acknowledgments" sections as well! The IESG Note in RFC 5242 is perfectly clear, with a length of 11 lines it reaches a third of the IESG Note size used in RFCs 4405, 4407, 4407, and 4408. For a shorter IESG Note I'd support an appeal or recall petition, but 11 lines ought to be good enough for everybody. It would be completely unjustfied to count empty lines, and then claim that 12 of 38 is less than a third, even if the 38 lines don't include a page header added by the RFC-editor without consent of the IESG, let alone any IETF Last Call. Frank _______________________________________________ IETF mailing list IETF@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Re: [Ltru] Possible RFC 3683 PR-action LB
- Re: [Ltru] Possible RFC 3683 PR-action Randy Presuhn
- Re: [Ltru] Possible RFC 3683 PR-action Russ Housley
- Re: [Ltru] Possible RFC 3683 PR-action LB
- Re: [Ltru] Possible RFC 3683 PR-action Sam Hartman
- Re: Possible RFC 3683 PR-action Stephane Bortzmeyer
- Re: [Ltru] Possible RFC 3683 PR-action Russ Housley
- RE: [Ltru] Possible RFC 3683 PR-action Christian Huitema
- Re: [Ltru] Possible RFC 3683 PR-action Theodore Tso
- Re: [Ltru] Possible RFC 3683 PR-action Peter Constable
- Re: Possible RFC 3683 PR-action Stephane Bortzmeyer
- RE: [Ltru] Possible RFC 3683 PR-action Russ Housley
- RE: [Ltru] Possible RFC 3683 PR-action Wes Beebee (wbeebee)
- Re: [Ltru] Possible RFC 3683 PR-action LB
- RE: Possible RFC 3683 PR-action Tamir Melamed
- Re: [Ltru] Possible RFC 3683 PR-action Harald Tveit Alvestrand
- Re: Possible RFC 3683 PR-action Stephane Bortzmeyer
- Re: Possible RFC 3683 PR-action Theodore Tso
- Re: Possible RFC 3683 PR-action Frank Ellermann
- Re: Possible RFC 3683 PR-action Spencer Dawkins
- Re: Possible RFC 3683 PR-action David Conrad
- Re: Possible RFC 3683 PR-action Russ Housley
- Re: Possible RFC 3683 PR-action Theodore Tso
- Re: Possible RFC 3683 PR-action John Levine
- Re: Possible RFC 3683 PR-action Peter Constable
- Re: Possible RFC 3683 PR-action Noel Chiappa
- Re: Possible RFC 3683 PR-action Michael Thomas
- Re: Possible RFC 3683 PR-action Melinda Shore
- RE: [Ltru] Possible RFC 3683 PR-action Russ Housley
- Re: Possible RFC 3683 PR-action Noel Chiappa
- Re: Possible RFC 3683 PR-action Simon Josefsson
- RE: Possible RFC 3683 PR-action Peter Constable
- Re: Possible RFC 3683 PR-action Melinda Shore
- Re: [Ltru] Possible RFC 3683 PR-action Spencer Dawkins
- Re: Possible RFC 3683 PR-action Theodore Tso
- Re: Possible RFC 3683 PR-action Edward Lewis
- Re: Possible RFC 3683 PR-action Melinda Shore
- Re: Possible RFC 3683 PR-action Michael Thomas
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Joel Jaeggli
- Re: Possible RFC 3683 PR-action Edward Lewis
- Re: Possible RFC 3683 PR-action Frank Ellermann
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Russ Housley
- Re: Possible RFC 3683 PR-action Hallam-Baker, Phillip
- Re: Possible RFC 3683 PR-action Theodore Tso
- Re: Possible RFC 3683 PR-action Thierry Moreau
- Re: Possible RFC 3683 PR-action Simon Josefsson
- RE: Possible RFC 3683 PR-action Darryl (Dassa) Lynch
- Pseudonym side-effects [Re: Possible RFC 3683 PR-… Brian E Carpenter
- Corporate side-effect [Re: Possible RFC 3683 PR-a… Brian E Carpenter
- Re: Possible RFC 3683 PR-action Russ Housley
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action stewe
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Noel Chiappa
- Re: Possible RFC 3683 PR-action Frank Ellermann
- Re: Possible RFC 3683 PR-action Doug Ewell
- Re: Possible RFC 3683 PR-action Stephan Wenger
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Simon Josefsson
- Re: Possible RFC 3683 PR-action Bert
- Re: Possible RFC 3683 PR-action Stephane Bortzmeyer
- <draft-ietf-ipr-3978-incoming-08.txt> as a BCP (w… Frank Ellermann
- Re: Possible RFC 3683 PR-action John C Klensin
- RE: Possible RFC 3683 PR-action Hadriel Kaplan
- Re: Possible RFC 3683 PR-action Doug Ewell
- Re: Possible RFC 3683 PR-action John C Klensin
- Re: Possible RFC 3683 PR-action Stephane Bortzmeyer
- Re: Possible RFC 3683 PR-action Frank Ellermann
- Re: Possible RFC 3683 PR-action Brian E Carpenter
- Re: Possible RFC 3683 PR-action Harald Tveit Alvestrand
- Re: Possible RFC 3683 PR-action John C Klensin
- Re: Possible RFC 3683 PR-action Dean Anderson