[as112-ops] Guidance requested before bringing up new AS112 server

[Rick Wesson]

The worst part of the Internet you could possibly break is your part,
so go for it. To paraphrase....

-rick

Rick Wesson
CEO, Support Intelligence, Inc.

o: 415.865.0853 x410
m: 415.215.7457

- sent from my mobile phone

On Feb 13, 2013, at 3:06 PM, "Jeremy L. Gaddis" <jeremy at as54225.net> wrote:

> Greetings,
>
> I'm relatively new to the list and, while I have read everything I can
> about the "AS112 project", I'm hoping to receive a bit of guidance.
>
> First off, I work for a fairly small ISP and already provide the "AS112
> service" to our own customers, keeping that DNS traffic localized within
> our network.
>
> I am interested in making this service available to the larger Internet
> community. My first question is if I need to obtain permission from or
> coordinate with anyone before I begin. I've already had 192.175.48.0/24
> added to our upstream's filters so I'm not sure if there's anything I
> need to do, procedurely, before "flipping the switch".
>
> While I have plenty of bandwidth to spare, I obviously won't know how
> much we "need" until our server is in use by the public. For that
> reason, my instinct was to simply bring it online, monitor resource
> usage for a while, and then make a determination regarding whether this
> is something we can continue to offer. If so, great; if not, well, I'll
> stop advertising the network.
>
> Is there something wrong with my line of thought? Other things I need to
> consider (or do) that I haven't already thought of?
>
> Thanks,
> -Jeremy
>
> --
> Jeremy L. Gaddis           e: jeremy at as54225.net
> Network Engineer           m: +1.812.865.0581
>
>
> _______________________________________________
> as112-ops mailing list
> as112-ops at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/as112-ops