Hi all, You may recall a little draft I threw together some time back to document facilities available to identify anycast nodes of the L-Root service.
There was sufficient enthusiasm expressed during earlier iterations that I proposed to the independent stream editor that this document be moved forward in that direction. Nevil graciously agreed, and this -02 is the result of a review solicited by Nevil from Paul Hoffman (thanks, Paul!) Nevil needs additional reviewers. If you have a spare ten minutes to read through this revision and send feedback to Nevil (or to this list, and I'll forward) that'd be great. Thanks, Joe Begin forwarded message: > From: "[email protected]" <[email protected]> > Subject: New Version Notification for > draft-jabley-dnsop-anycast-mapping-02.txt > Date: 24 June 2013 12:22:42 EDT > To: Joe Abley <[email protected]> > > > A new version of I-D, draft-jabley-dnsop-anycast-mapping-02.txt > has been successfully submitted by Joe Abley and posted to the > IETF repository. > > Filename: draft-jabley-dnsop-anycast-mapping > Revision: 02 > Title: A Summary of Various Mechanisms Deployed at L-Root for > the Identification of Anycast Nodes > Creation date: 2013-06-24 > Group: Individual Submission > Number of pages: 18 > URL: > http://www.ietf.org/internet-drafts/draft-jabley-dnsop-anycast-mapping-02.txt > Status: > http://datatracker.ietf.org/doc/draft-jabley-dnsop-anycast-mapping > Htmlized: > http://tools.ietf.org/html/draft-jabley-dnsop-anycast-mapping-02 > Diff: > http://www.ietf.org/rfcdiff?url2=draft-jabley-dnsop-anycast-mapping-02 > > Abstract: > Anycast is a deployment technique commonly employed for > authoritative-only servers in the Domain Name System (DNS). L-Root, > one of the thirteen root servers, is deployed in this fashion. > > Various techniques have been used to map deployed anycast > infrastructure externally, i.e. without reference to inside knowledge > about where and how such infrastructure has been deployed. > Motivations for performing such measurement exercises include > operational troubleshooting and infrastructure risk assessment. In > the specific case of L-Root, the ability to measure and map anycast > infrastructure using the techniques mentioned in this document is > provided for reasons of operational transparency. > > This document describes all facilities deployed at L-Root to > facilitate mapping of its infrastructure and serves as documentation > for L-Root as a measurable service. > > > > > The IETF Secretariat > _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
