North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: So -- what did happen to Panix?

  • From: Josh Karlin
  • Date: Wed Feb 08 00:09:53 2006
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=AwGMkBRxpn+OOlzBYXSiDBhR5yTCd4jIk1/VV6jH3v0cC0UFe1IMTE2d+2GUFFLZkg8vQc1MQSX8sW+9tfSPWLC64zTyRKA7OiYEozH50VURp/9wqvH+fAdKKJOFE7oMKH6pPIy0HVYnOKGkZPSw+N3FIy6Wt/Kc08j8ozk9zqo=
Chris has it!

And to be clear, we only require a slow (1 day) provider changeover in
the case that you want to announce your old provider's sub-prefix at a
new provider.  For instance, if you are an AT&T customer using a 12/8
sub-prefix and change providers but keep the prefix, the prefix will
look funny coming from another originator for the first day and be
delayed.  All other methods of changing providers will not be
interfered with.

Josh



> I had thought Josh's paper (or maybe not josh, whomever it was) said
> something along the lines of:
> 1) if more than one announcement prefer 'longer term', 'older', 'more
> usual' route
> 2) if only one route take it and run!
>
> So.. provided Connexion withdraws from 'as-germany' and announces in
> 'as-atlantic ocean', and so on there would only be 1 route, and you'd fall
> to step 2.
>
> (yes, the paper was more detailed and there were more steps...)
>