Call for Comment: "IETF and ITU-T Standardization Sector Collaboration Guidelines"
"IAB Chair" <firstname.lastname@example.org> Wed, 25 April 2012 18:00 UTC
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2996F21F885B for <email@example.com>; Wed, 25 Apr 2012 11:00:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[AWL=0.697, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([18.104.22.168]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bg8U3K+sI4rb for <firstname.lastname@example.org>; Wed, 25 Apr 2012 11:00:24 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 840D521F885A for <email@example.com>; Wed, 25 Apr 2012 11:00:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 6F67212C89D for <firstname.lastname@example.org>; Wed, 25 Apr 2012 11:00:24 -0700 (PDT)
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 XbrAms2O7pDL for <email@example.com>; Wed, 25 Apr 2012 11:00:24 -0700 (PDT)
Received: from Asphodel (unknown [IPv6:2001:1938:2aa:0:fc98:d710:4eac:261d]) by c8a.amsl.com (Postfix) with ESMTPSA id 7586A12C97D for <firstname.lastname@example.org>; Wed, 25 Apr 2012 11:00:23 -0700 (PDT)
From: "IAB Chair" <email@example.com>
Subject: Call for Comment: "IETF and ITU-T Standardization Sector Collaboration Guidelines"
Date: Wed, 25 Apr 2012 11:00:44 -0700
Organization: Internet Architecture Board
Content-Type: multipart/alternative; boundary="----=_NextPart_000_10E3_01CD22D2.A9FD03A0"
X-Mailer: Microsoft Outlook 14.0
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: Wed, 25 Apr 2012 18:00:25 -0000
This is an IETF-wide Call for Comment on "Internet Engineering Task Force and International Telecommunication Union - Telecommunications Standardization Sector Collaboration Guidelines". 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-rfc3356bis The Call for Comment will last until May 25, 2012. Please send comments to firstname.lastname@example.org, or submit them via TRAC (see below). =============================================================== 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.