Re: Should the RFC Editor publish an RFC in less than 2 months?
"Daniel Brown" <parasane@gmail.com> Mon, 03 December 2007 15:28 UTC
Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzDDW-0006Gz-9W; Mon, 03 Dec 2007 10:28:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzDDU-0005xE-2Y for ietf@ietf.org; Mon, 03 Dec 2007 10:28:16 -0500
Received: from rv-out-0910.google.com ([209.85.198.191]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IzDDR-0004sc-R6 for ietf@ietf.org; Mon, 03 Dec 2007 10:28:16 -0500
Received: by rv-out-0910.google.com with SMTP id l15so2572363rvb for <ietf@ietf.org>; Mon, 03 Dec 2007 07:28:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=DY6FEO6yYRtBhW0rP03Zkf73IbAThYfa4pr1a8ojOfU=; b=Rvl4eiiHL+eBSFVx0ltm1YVM/iiPgwaqrSb2udejO3PovyQkuqZAYpwgmZDumZ4Ke7f38CZdPB0+2KZf7qmAwTX69QVKZ6tWuY8pUrgBt6ZGNIVb7SFz3r+hGKgt9U8+aTBH3UX/sBohXMVBzRIIT1S21GIRLAfNN6DeD10Ta4I=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qNfKEIeZkGlUvPw6eAvZIm17cF8COCHFUm3k8CivpQxJBqpdNBnJdOj76tdE6n2QP/Q1DPXXEnmeSFrFN1ek3TD+M757Mp+Gte52d1trZV79jQixB+feQjd0zAT1PAL/yrCegSgXL6GmUt221QXdQ+iL41mCfolAUTeF+QguFoE=
Received: by 10.141.51.15 with SMTP id d15mr5691830rvk.1196695692390; Mon, 03 Dec 2007 07:28:12 -0800 (PST)
Received: by 10.141.52.8 with HTTP; Mon, 3 Dec 2007 07:28:12 -0800 (PST)
Message-ID: <ab5568160712030728i463088a4nac9b5a68214573f5@mail.gmail.com>
Date: Mon, 03 Dec 2007 10:28:12 -0500
From: Daniel Brown <parasane@gmail.com>
To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
In-Reply-To: <fiv9fh$ihg$1@ger.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <E1IxTPt-0006r4-ST@ietf.org> <4751F44D.3050207@isode.com> <E1Iye5A-0002sv-6J@megatron.ietf.org> <D9AE99FE-731F-4F55-B646-B26A6C8A4485@nokia.com> <7AC22E50348D3364BD9C2749@B50854F0A9192E8EC6CDA126> <D1661755189D9C66DADD5ACD@10.1.129.171> <fiur2s$64q$1@ger.gmane.org> <7C07FB6D-805E-4FF5-8F40-64BA444F065F@cs.ucla.edu> <fiv9fh$ihg$1@ger.gmane.org>
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Cc: ietf@ietf.org
Subject: Re: Should the RFC Editor publish an RFC in less than 2 months?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org
On Dec 2, 2007 4:55 PM, Frank Ellermann <nobody@xyzzy.claranet.de> wrote: > Lixia Zhang wrote: > > The remedy here may also include the cost to those people who > > acted on a published RFC in its first 2 months. > > Yes, or months earlier, for the case I have in mind more than > two years, millions of users, and a bunch of implementations. > Most happily ignoring the eventual "opt-out" remedy, I guess. Conversely, why not allow a Draft to be published as an RFC in that six-week period if there are no arguments or appeals, whereas an appeal could potentially (a) restart the six-week clock, or (b) extend the period from 42 to the full sixty days? Though again, it would be changing the rule for less than a 50% gain in minimum time to publication. I just thought I'd toss the idea out there. -- Daniel P. Brown [office] (570-) 587-7080 Ext. 272 [mobile] (570-) 766-8107 If at first you don't succeed, stick to what you know best so that you can make enough money to pay someone else to do it for you. _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- Re: Should the RFC Editor publish an RFC in less … Eric Rescorla
- Should the RFC Editor publish an RFC in less than… IETF Chair
- Re: Should the RFC Editor publish an RFC in less … Brian E Carpenter
- Re: Should the RFC Editor publish an RFC in less … John C Klensin
- RE: Should the RFC Editor publish an RFC in less … Wassim Haddad
- Re: Should the RFC Editor publish an RFC in less … Ted Hardie
- Re: Should the RFC Editor publish an RFC in less … Brian E Carpenter
- Re: Should the RFC Editor publish an RFC in less … Leslie Daigle
- Re: Should the RFC Editor publish an RFC in less … Russ Housley
- Re: Should the RFC Editor publish an RFC in less … Cullen Jennings
- Re: Should the RFC Editor publish an RFC in less … Sam Hartman
- Re: Should the RFC Editor publish an RFC in less … Eric Rescorla
- Re: Should the RFC Editor publish an RFC in less … Tim Polk
- Re: Should the RFC Editor publish an RFC in less … Paul Hoffman
- Re: Should the RFC Editor publish an RFC in less … Sam Hartman
- Re: Should the RFC Editor publish an RFC in less … Sam Hartman
- Re: Should the RFC Editor publish an RFC in less … Frank Ellermann
- Re: Should the RFC Editor publish an RFC in less … Eric Rescorla
- Re: Should the RFC Editor publish an RFC in less … Tom.Petch
- Re: Should the RFC Editor publish an RFC in less … Harald Alvestrand
- Re: Should the RFC Editor publish an RFC in less … John C Klensin
- Re: Should the RFC Editor publish an RFC in less … Norbert Bollow
- Re: Should the RFC Editor publish an RFC in less … Iljitsch van Beijnum
- Re: Should the RFC Editor publish an RFC in less … Eric Rescorla
- Re: Should the RFC Editor publish an RFC in less … Dave Crocker
- Re: Should the RFC Editor publish an RFC in less … Alexey Melnikov
- Re: Should the RFC Editor publish an RFC in less … Jari Arkko
- Re: Should the RFC Editor publish an RFC in less … Sam Hartman
- Re: Should the RFC Editor publish an RFC in less … John C Klensin
- Re: Should the RFC Editor publish an RFC in less … Paul Hoffman
- Re: Should the RFC Editor publish an RFC in less … Sam Hartman
- Re: Should the RFC Editor publish an RFC in less … Harald Alvestrand
- Re: Should the RFC Editor publish an RFC in less … Brian E Carpenter
- Re: Should the RFC Editor publish an RFC in less … Bob Hinden
- Re: Should the RFC Editor publish an RFC in less … Frank Ellermann
- Re: Should the RFC Editor publish an RFC in less … John C Klensin
- Re: Should the RFC Editor publish an RFC in less … Spencer Dawkins
- Re: Should the RFC Editor publish an RFC in less … Magnus Westerlund
- Re: Should the RFC Editor publish an RFC in less … Frank Ellermann
- Re: Should the RFC Editor publish an RFC in less … John C Klensin
- Re: Should the RFC Editor publish an RFC in less … Alexey Melnikov
- Re: Should the RFC Editor publish an RFC in less … Jari Arkko
- Re: Should the RFC Editor publish an RFC in less … Russ Housley
- Re: Should the RFC Editor publish an RFC in less … Bob Hinden
- Re: Should the RFC Editor publish an RFC in less … Harald Tveit Alvestrand
- Re: Should the RFC Editor publish an RFC in less … John C Klensin
- Re: Should the RFC Editor publish an RFC in less … Frank Ellermann
- Re: Should the RFC Editor publish an RFC in less … Bob Hinden
- Re: Should the RFC Editor publish an RFC in less … Lixia Zhang
- Re: Should the RFC Editor publish an RFC in less … Frank Ellermann
- Re: Should the RFC Editor publish an RFC in less … Iljitsch van Beijnum
- Re: Should the RFC Editor publish an RFC in less … Frank Ellermann
- Re: Should the RFC Editor publish an RFC in less … Hallam-Baker, Phillip
- Re: Should the RFC Editor publish an RFC in less … Robert Elz
- OOXML (was Re: Should the RFC Editor...) Norbert Bollow
- Re: Should the RFC Editor publish an RFC in less … Norbert Bollow
- Re: Should the RFC Editor publish an RFC in less … Tom.Petch
- Re: Should the RFC Editor publish an RFC in less … Daniel Brown
- Re: Should the RFC Editor publish an RFC in less … Brian E Carpenter
- Re: Should the RFC Editor publish an RFC in less … Harald Tveit Alvestrand
- Re: Should the RFC Editor publish an RFC in less … Scott O. Bradner
- Re: Should the RFC Editor publish an RFC in less … Robert Elz
- RE: Should the RFC Editor publish an RFC in less … Tobias Gondrom
- Re: Should the RFC Editor publish an RFC in less … Frank Ellermann
- Re: Should the RFC Editor publish an RFC in less … Henrik Levkowetz
- Re: Should the RFC Editor publish an RFC in less … Loa Andersson
- Re: Should the RFC Editor publish an RFC in less … JP Vasseur
- Re: Should the RFC Editor publish an RFC in less … Russ Housley