Re: [GROW] ISC Response to draft-ietf-grow-unique-origin-as

2011-09-30 Thread Christopher Morrow
On Fri, Sep 30, 2011 at 10:20 AM, Leo Bicknell bickn...@isc.org wrote: In a message written on Fri, Sep 30, 2011 at 12:40:24AM -0400, Christopher Morrow wrote: keep in mind that 'enterprises' may be deploying anycast services inside their wan's, NOT publicly visible... What advice would you

Re: [GROW] ISC Response to draft-ietf-grow-unique-origin-as

2011-09-30 Thread Leo Bicknell
In a message written on Fri, Sep 30, 2011 at 10:51:58AM -0400, Christopher Morrow wrote: the troubleshooting though with something like unique origin is 'simpler' for them: Oh, as27 is NYC, as37 is WDC... why is Newark seeing WDC as the best path? I'm not sure I get it. Unique origin ASN

Re: [GROW] ISC Response to draft-ietf-grow-unique-origin-as

2011-09-29 Thread Leo Bicknell
In a message written on Thu, Sep 29, 2011 at 11:22:45AM -0400, Danny McPherson wrote: With normal unicast there's a single tree for the prefix in the routing system, while anycasting inherently introduces a polytree for the prefix. However, anycasting with a common origin AS creates a

Re: [GROW] ISC Response to draft-ietf-grow-unique-origin-as

2011-09-29 Thread John Kristoff
On Thu, 29 Sep 2011 19:07:06 + Leo Bicknell bickn...@isc.org wrote: time. I think the question is if anyone else on the list cares one way or another, because if no other opinions have been changed we might as well stop. I often play contrarian or skeptic, if not an honest critic when I

Re: [GROW] ISC Response to draft-ietf-grow-unique-origin-as

2011-09-29 Thread Leo Bicknell
In a message written on Thu, Sep 29, 2011 at 03:04:03PM -0500, John Kristoff wrote: It seems to me this is VeriSign trying to document a BCP that works for them and may work for others. So perhaps it is just the BCP status that is disconcerting? That may be part of it. At the risk of