Call for Comment: "RFC Format Requirements and Future Development"
IAB Chair <email@example.com> Fri, 01 February 2013 19:53 UTC
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 790B421E8044 for <firstname.lastname@example.org>; Fri, 1 Feb 2013 11:53:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Status: No, score=-101.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([22.214.171.124]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r8v90yOlSw8y for <email@example.com>; Fri, 1 Feb 2013 11:52:56 -0800 (PST)
Received: from mail.amsl.com (unknown [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 0C4B921F8488 for <firstname.lastname@example.org>; Fri, 1 Feb 2013 11:52:22 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id AB42F12A99C; Fri, 1 Feb 2013 11:52:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3t2-2g6y_RNH; Fri, 1 Feb 2013 11:52:21 -0800 (PST)
Received: from [192.168.1.107] (c-24-16-96-166.hsd1.wa.comcast.net [126.96.36.199]) by c8a.amsl.com (Postfix) with ESMTPSA id 6ECE7126834; Fri, 1 Feb 2013 11:52:21 -0800 (PST)
Subject: Call for Comment: "RFC Format Requirements and Future Development"
Mime-Version: 1.0 (1.0)
From: IAB Chair <email@example.com>
Content-Type: multipart/alternative; boundary="Apple-Mail-4B33282A-109B-4327-9A41-C0DAA0D60B54"
X-Mailer: iPad Mail (10B141)
Date: Fri, 01 Feb 2013 11:53:28 -0800
To: "firstname.lastname@example.org" <email@example.com>
Cc: "firstname.lastname@example.org" <email@example.com>
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:firstname.lastname@example.org?subject=unsubscribe>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:email@example.com?subject=subscribe>
X-List-Received-Date: Fri, 01 Feb 2013 19:53:16 -0000
This is an announcement of an IETF-wide Call for Comment on "RFC Format Requirements and Future Development". The document is being considered for publication as an Informational RFC within the IAB stream, and is available for inspection here: http://tools.ietf.org/html/draft-iab-rfcformatreq The Call for Comment will last until February 29, 2013. Please send comments to iab at iab.org or submit them via TRAC (see below). Please also cc: firstname.lastname@example.org (for membership info, see: https://www.rfc-editor.org/mailman/listinfo/rfc-interest). =============================================================== Submitting Comments via TRAC 1. To submit an issue in TRAC, you first need to login to the IAB site on the tools server: http://tools.ietf.org/wg/iab/trac/login 2. If you don't already have a login ID, you can obtain one by navigating to this site: http://trac.tools.ietf.org/newlogin 3. Once you have obtained an account, and have logged in, you can file an issue by navigating to the ticket entry form: http://trac.tools.ietf.org/wg/iab/trac/newticket 4. When opening an issue: a. The Type: field should be set to "defect" for an issue with the current document text, or "enhancement" for a proposed addition of functionality (such as an additional requirement). b. The Priority: field is set based on the severity of the Issue. For example, editorial issues are typically "minor" or "trivial". c. The Milestone: field should be set to milestone1 (useless, I know). d. The Component: field should be set to the document you are filing the issue on. e. The Version: field should be set to "1.0". f. The Severity: field should be set to based on the status of the document (e.g. "In WG Last Call" for a document in IAB last call) g. The Keywords: and CC: fields can be left blank unless inspiration seizes you. h. The Assign To: field is generally filled in with the email address of the editor. 5. Typically it won't be necessary to enclose a file with the ticket, but if you need to, select "I have files to attach to this ticket". 6. If you want to preview your Issue, click on the "Preview" button. When you're ready to submit the issue, click on the "Create Ticket" button. 7. If you want to update an issue, go to the "View Tickets" page: http://trac.tools.ietf.org/wg/iab/trac/report/1 Click on the ticket # you want to update, and then modify the ticket fields as required.