Re: Friday Hosing

2013-07-13 Thread Eric Adler
Just finished migration from a provider that I was no longer happy with to a new provider. Fully expecting them to turn me off the moment I said 'cancel', I prepared everything in advance, moved all the pointers over a few days prior to my planned day to tell them to 'shutoff', retrieved a final

Re: Webcasting as a replacement for traditional broadcasting (was Re: Wackie 'ol Friday)

2013-06-09 Thread Eric Adler
in television until 2000 or so and I wasn't doing television broadcast-related work until 2008. - Eric Eric Adler Broadcast Engineer

Re: Why are there no GeoDNS solutions anywhere in sight?

2013-04-14 Thread Eric Adler
If this is for http and similar user-accessed (not machine accessed) traffic, you could do what some large manufacturers and shipping companies do: Provide a (relatively) low-bandwidth Select where you are in the world global landing page which then redirects to a different domain/subdomain for

Re: RFC 1149

2013-04-01 Thread Eric Adler
Make sure you don't miss the QoS implementation of RFC 2549 (and make sure that you're ready to implement RFC 6214). You'll be highly satisfied with the results (presuming you and your packets end up in one of the higher quality classes). I'd also suggest a RFC 2322 compliant DHCP server for

Re: home network monitoring and shaping

2013-02-12 Thread Eric Adler
I'm quite happy with what routeros (mikrotik) provides me on my home network. - Eric Eric Adler Broadcast Engineer On 2/12/13, Michael Thomas m...@mtcc.com wrote: O oracle of nanog: unlike things like rogue processes eating tons of CPU, it seems to me that network monitoring is essentially

Re: For those who may use a projector in the NOC

2013-01-17 Thread Eric Adler
such) - Eric Adler Broadcast Engineer

Re: RFC becomes Visio

2012-10-01 Thread Eric Adler
Why not RFC 5514 over RFC 2410 encryption over RFC2549 enhanced RFC1149 with all sessions padded with a number (generated by a server compliant with RFC3091) of the packets described in RFC6592? Oh, and don't forget to set the bit described in RFC3514 as appropriate. Or, ya know, one could just