Home page logo
/

nanog logo nanog mailing list archives

Re: Notifying customers of upstream modifications
From: Michael Butler <imb () protected-networks net>
Date: Wed, 28 Dec 2011 18:30:45 -0500

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/28/11 17:59, Andy Susag wrote:

If you add or remove an upstream provider to your network, do you
provide notification to your downstream customers? Likely, it would
cause a shift in their traffic. If they are peering with multiple ISPs
themselves, they may see a traffic flux. 

I know for a fact that our upstreams do not notify us of events so we
tend to not send out these sort of notifications. Just wonder what
everyone else does or if anyone happens to know "best practice"

In an ideal world, part of a good change-management process is to notify
those who may see differences as a consequence of any proposed change
(tell the folk that care). That way, they know something is moving and
can plan accordingly. Also they can advise in a timely fashion if it
either works or not and make their own changes when appropriate.

Sadly, we do not live in an ideal world :-(

        imb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk77pqUACgkQQv9rrgRC1JKChgCeOaZ4mlcZ8OzaHdeJGL8JF4B4
vooAnje3JgJLqecM1Q4SQ3F2GqP+Uhvj
=hUhW
-----END PGP SIGNATURE-----


  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
AlienVault