---- following is a DRAFT of message to be sent AFTER approval ---
From: The IESG <firstname.lastname@example.org>
To: IETF-Announce <email@example.com>
Cc: RFC Editor <firstname.lastname@example.org>,
grow mailing list <email@example.com>,
grow chair <firstname.lastname@example.org>
Subject: Protocol Action: 'Unique Per-Node Origin ASNs for Globally Anycasted Services' to BCP (draft-ietf-grow-unique-origin-as-01.txt)
The IESG has approved the following document:
- 'Unique Per-Node Origin ASNs for Globally Anycasted Services'
(draft-ietf-grow-unique-origin-as-01.txt) as a BCP
This document is the product of the Global Routing Operations Working
The IESG contact persons are Ron Bonica and Dan Romascanu.
A URL of this Internet Draft is:
This document makes recommendations regarding the use of per-node unique
origin ASNs for globally anycasted critical infrastructure services in order to
provide routing system discriminators for a given anycasted prefix. Network
managment and monitoring techniques, or other operational mechanisms may
employ this new discriminator in whatever manner fits their operating environment.
Working Group Summary
The working group has wide support. We had many different people, especially
operators which supported the document and felt the work was quite worthwhile.
The document is short, and even though it is a ‘00’ draft, comments and feedback
have been incorporated in document.
The document is straightforward, and well written. It covers the requirement
Peter Schoenmaker email@example.com is the document shepherd. Ron Bonica is
the AD responsible for the document.
RFC Editor Note
Please remove the two erroneous COPYRIGHT statements and insert the following in the correct place:
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.