IETF Logo Mail Archive

Re: Creating an IETF Working Group Draft

Dave Crocker <dhc@dcrocker.net> Mon, 03 December 2012 14:09 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35DFD21F8651 for <ietf@ietfa.amsl.com>; Mon, 3 Dec 2012 06:09:52 -0800 (PST)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r2EyRDPRI5wy for <ietf@ietfa.amsl.com>; Mon, 3 Dec 2012 06:09:51 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C0B9221F8581 for <ietf@ietf.org>; Mon, 3 Dec 2012 06:09:48 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qB3E9ljt030776 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 3 Dec 2012 06:09:47 -0800
Message-ID: <50BCB2A0.50305@dcrocker.net>
Date: Mon, 03 Dec 2012 06:09:36 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: Creating an IETF Working Group Draft
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk> <50BBA236.9010603@dcrocker.net> <50BBB79C.40106@gmail.com> <50BBB862.8090209@gmail.com> <50BBB940.1020302@gmail.com> <m2zk1wui8h.wl%randy@psg.com> <50BBEAA7.3070600@gmail.com> <50BBEE5F.3060906@gmail.com> <50BBF121.8050400@lacnic.net> <50BC89D3.8030701@gmail.com> <3F85F6C1-7CE7-4C14-9C98-7DA1F75AEA2C@vigilsec.com> <01ca01cdd15e$4c055000$e40ff000$@olddog.co.uk>
In-Reply-To: <01ca01cdd15e$4c055000$e40ff000$@olddog.co.uk>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 03 Dec 2012 06:09:48 -0800 (PST)
Cc: 'IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Mon, 03 Dec 2012 14:09:52 -0000
X-List-Received-Date: Mon, 03 Dec 2012 14:09:52 -0000

On 12/3/2012 5:58 AM, Adrian Farrel wrote:
> We could certainly say this. It is a true statement.
>
> However, the document is trying to talk about WG I-Ds, not to provide a general
> description of everything the IETF and RFC Editor ever does.
...
> My answers are "No" and "No".

+1

The existing text was tailored to lay foundation for what comes next, 
not to provide a general introduction to I-Ds.  The suggested changes 
add unnecessary verbosity.  Anyone needing a 'complete' understanding of 
I-Ds can consult the offered citations.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

v2.23.0 | Report a Bug | By Email