[Trans] Fwd: The RFC Style Guide (RFC 7322)

Melinda Shore <melinda.shore@gmail.com> Fri, 26 September 2014 19:01 UTC

Return-Path: <melinda.shore@gmail.com>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 671641A1BE9 for <trans@ietfa.amsl.com>; Fri, 26 Sep 2014 12:01:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id r7ab5LYg5bNV for <trans@ietfa.amsl.com>; Fri, 26 Sep 2014 12:01:46 -0700 (PDT)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6F521A0024 for <trans@ietf.org>; Fri, 26 Sep 2014 12:01:45 -0700 (PDT)
Received: by mail-pa0-f47.google.com with SMTP id rd3so3112814pab.34 for <trans@ietf.org>; Fri, 26 Sep 2014 12:01:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=yv0+Jgpn0obT2RDKqdlYZggqORODD7eYumLZVaEriA0=; b=BLKHFx1xn0kA0tuGyQ8ekodrEuuK5xrMt5H97AfEz7WBUOxOaoSctAH9E7WhyAmii5 CmTvtIDug/4Q3kn/5a0VR8lMZ08zKsVPR9YF/IW7sMYNBBW47rGX8ccmqSZdrVwx5mET izIKXdF2zt/AtSliQ63WYj2xFanS7BW122mGJTAceI+ka/+GITCkm4Dju6Gix9CTYWca 0T/wzorfHXcB7iHY7O92l25AxXeNOdt067O7b1Ub0eBtGcAH8YqaRmOILCqL7IjDqYei x3u8JBlWn9r81W2Log6BBDGrPLtDU9+mLySwVY6WWZxmPF4jrYZMaVCY2cc5JnCqKLL6 Iuqg==
X-Received: by with SMTP id qg1mr34807242pbb.116.1411758105556; Fri, 26 Sep 2014 12:01:45 -0700 (PDT)
Received: from spandex.local (209-193-56-116-rb1.fai.dsl.dynamic.acsalaska.net. []) by mx.google.com with ESMTPSA id f2sm5613651pdd.25.2014. for <trans@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 26 Sep 2014 12:01:44 -0700 (PDT)
Message-ID: <5425B817.30903@gmail.com>
Date: Fri, 26 Sep 2014 11:01:43 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "trans@ietf.org" <trans@ietf.org>
References: <20140926185613.GA4001@rfc-editor.org>
In-Reply-To: <20140926185613.GA4001@rfc-editor.org>
X-Forwarded-Message-Id: <20140926185613.GA4001@rfc-editor.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/0s54XbXOfdgJE9sG4-7FRrS6KT0
Subject: [Trans] Fwd: The RFC Style Guide (RFC 7322)
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Sep 2014 19:01:47 -0000

As we hurtle (we hope) towards publication of the bis document,
it's a good idea to take a look at the just-published RFC Editor
style guide and make sure that the document is in alignment with
it.  Content is the core question but documents get hung up on
formal nits more often than they should.


-------- Original Message --------
Subject: The RFC Style Guide (RFC 7322)
Date: Fri, 26 Sep 2014 11:56:13 -0700
From: RFC Editor <rfc-editor@rfc-editor.org>
Reply-To: ietf@ietf.org
To: rfc-dist@rfc-editor.org, ietf-announce@ietf.org
CC: RFC Editor <rfc-editor@rfc-editor.org>


RFC 7322, "RFC Style Guide", has been published.  This document
obsoletes RFC 2223 and other style information previously provided.
Please review the complete set of style guidelines impacting the RFC
series that is available here:


With the publication of the new RFC Style Guide, the RFC Editor will
be enforcing the guidance set forth in RFC 7322.  This applies to
documents currently in process, including those in AUTH48.  The
documents will be updated and authors will be notified of that the
updates are ready for review.  Please be sure to review the udpates

Thank you,
RFC Editor Team