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 DEEEB21F9DCE; Wed,  3 Jul 2013 11:14:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5
 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com
 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fUY83qHiv07d;
 Wed,  3 Jul 2013 11:14:00 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com
 (Postfix) with ESMTP id 6A01821F9DDB; Wed,  3 Jul 2013 11:13:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix)
 with ESMTP id AF1A8A89E2; Wed,  3 Jul 2013 11:13:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com
 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oj0q9gihaND7;
 Wed,  3 Jul 2013 11:13:09 -0700 (PDT)
Received: from [192.168.2.109] (pool-96-241-156-29.washdc.fios.verizon.net
 [96.241.156.29]) by c9a.amsl.com (Postfix) with ESMTPSA id 1F858A896E;
 Wed,  3 Jul 2013 11:13:09 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Subject: Call for Comment on draft-iab-anycast-arch-implications-09 on
 "Architectural Considerations of IP Anycast"
Mime-Version: 1.0 (Apple Message framework v1085)
From: IAB Chair <iab-chair@iab.org>
Date: Wed, 3 Jul 2013 14:13:57 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2C891F70-34C8-441A-8085-38A9F2F13D5B@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org, IAB <iab@iab.org>
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: Wed, 03 Jul 2013 18:14:01 -0000

This is an announcement of an IETF-wide Call for Comment on =
"Architectural Considerations of IP Anycast" =
(draft-iab-anycast-arch-implications-09).=20

The document is being considered for publication as an Informational RFC =
within the IAB stream, and is available for inspection here:=20
https://datatracker.ietf.org/doc/draft-iab-anycast-arch-implications/

The Call for Comment will last until August 1, 2013. Please send =
comments to iab@iab.org or submit them via TRAC (see below).=20

Russ Housley
IAB Chair

=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D

Submitting Comments via TRAC

1. To submit an issue in TRAC, you first need to login to the IAB site =
on the tools server:=20
http://tools.ietf.org/wg/iab/trac/login=20

2. If you don't already have a login ID, you can obtain one by =
navigating to this site:=20
http://trac.tools.ietf.org/newlogin=20

3. Once you have obtained an account, and have logged in, you can file =
an issue by navigating to the ticket entry form:=20
http://trac.tools.ietf.org/wg/iab/trac/newticket=20

4. When opening an issue:=20
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).=20
b. The Priority: field is set based on the severity of the Issue. For =
example, editorial issues are typically "minor" or "trivial".=20
c. The Milestone: field should be set to milestone1 (useless, I know).=20=

d. The Component: field should be set to the document you are filing the =
issue on.=20
e. The Version: field should be set to "1.0".=20
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)=20
g. The Keywords: and CC: fields can be left blank unless inspiration =
seizes you.=20
h. The Assign To: field is generally filled in with the email address of =
the editor.=20

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".=20

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.=20

7. If you want to update an issue, go to the "View Tickets" page:=20
http://trac.tools.ietf.org/wg/iab/trac/report/1=20

Click on the ticket number you want to update, and then modify the =
ticket fields as required.=20

