[as112-ops] [PeeringDB #2916]: Anycast ASN (like AS112)

[PeeringDB Support]

 Hi Clément,

 > I am running an instance of AS112 anycast node in Paris, France.
 > 
 > As you may know, AS112 is a group of volunteers, who run and announce an
 > anycast route (192.175.48.0/24 & 2620:4f:8000::0/48) according to
 > RFC6304 & 6305. Anyone could create a node, and connect it to local
 > exchange, and that's what we have done in Paris, connecting it to
 > Equinix & FranceIX. And also what has been done in other parts of the
 > globe, by other volunteers (see http://public.as112.net/node/10 for a
 > known list)
 > 
 > When I started to setup sessions on my "local" node, I was advised by
 > some peering partners to create a peeringDB entry for AS112. However,
 > since I am not responsible for this project as a whole, and since
 > PeeringDB interface is designed for classic networks, which have some
 > unique management team, I think it's better to contact you in order to
 > see what could be done for that kind of case.
 > -> Would it be possible to create that special kind of network ? 
 > It would be interesting, for potential partners to get the "local
 > peering adress" which it could contact in order to setup a session. 
 > For example, at AMS-IX, networks should contact RIPE NCC, at FranceIX,
 > they should contact Hivane (us), or at Inex, they should contact inex
 > team, etc. 
 > 
 > I think someone could have the responsability for "maintaining the
 > peeringDB entry", and that person should be contacted by the
 > node-mainainers in order to update visible peering information on
 > peeringDB. Or maybe you could see some other/better mechanism in order
 > to maintain such a "special page" ?
 > 
 
I guess it is as simple as that OARC takes care for that. Isn't it?


Best regards,
Arnold
-- 
Arnold Nipper <arnold at peeringdb.com>
PeeringDB Administrator


Ticket Details
---------------------------------
Ticket ID: 2916
Department: Support
Type: Issue
Status: Open
Priority: Normal

Support Center: http://support.peeringdb.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dns-oarc.net/pipermail/as112-ops/attachments/20111227/ebd545b3/attachment.htm>