Ongoing Call for Comment: 'Issues in Identifier Comparison for Security Purposes'

IAB Chair <iab-chair@iab.org> Fri, 08 February 2013 23:07 UTC

Return-Path: <iab-chair@iab.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64B6F21F8C03 for <ietf-announce@ietfa.amsl.com>; Fri, 8 Feb 2013 15:07:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.203
X-Spam-Level:
X-Spam-Status: No, score=-101.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
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 SjlymEIiGgpY for <ietf-announce@ietfa.amsl.com>; Fri, 8 Feb 2013 15:07:12 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 74BF821F8A4F for <ietf-announce@ietf.org>; Fri, 8 Feb 2013 15:07:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 8A6DF12A871 for <ietf-announce@ietf.org>; Fri, 8 Feb 2013 15:07:07 -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 EMuAUIXgGTKJ for <ietf-announce@ietf.org>; Fri, 8 Feb 2013 15:07:07 -0800 (PST)
Received: from [10.80.21.31] (unknown [131.107.192.220]) by c8a.amsl.com (Postfix) with ESMTPSA id 6DFF312A870 for <ietf-announce@ietf.org>; Fri, 8 Feb 2013 15:07:07 -0800 (PST)
Subject: Ongoing Call for Comment: 'Issues in Identifier Comparison for Security Purposes'
From: IAB Chair <iab-chair@iab.org>
Content-Type: text/plain; charset="us-ascii"
X-Mailer: iPad Mail (10B141)
Message-Id: <224741C3-BEE2-47BE-85BB-6851BD79A336@iab.org>
Date: Fri, 08 Feb 2013 15:05:28 -0800
To: ietf-announce@ietf.org
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Feb 2013 23:07:12 -0000

This is a reminder of an ongoing IETF-wide Call for Comment on 'Issues in Identifier Comparison for Security Purposes'. 
 
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-identifier-comparison 
 
The Call for Comment will last until February 10, 2013. Please send comments to iab at iab.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.