[6bone] peering

[Michel Py]

> John Fraizier wrote:
> Others may feel differently about this but, here is how
> EnterZone operates when peering with people who want to
> announce "more specifics" or deaggregated prefixes:
> We will accept your more-specific (providing that you
> are the one shown for that prefix in the 6bone database)
> but tag it as no-export. We will use this direct path to
> you but, we won't export the route to our other eBGP peers.
> So, you get a direct path to us, we get a direct path to
> you and nobody else is any the wiser.  No global table
> pollution.

The way John does it looks good to me.

> I posted a config a week or so ago that shows how we're
> doing this.

About the config itself:

>> - There is overlap in the following two lines:
>> neighbor 3ffe:1ced:ff02::2 prefix-list AS-ARNEILLPY in neighbor 
>> 3ffe:1ced:ff02::2 route-map AS-ARNEILLPY in The prefix-list is
useless 
>> as the route-map uses it IMHO.
 
> Michel, actually, if you look at our config for your peering
> session, the prefix-list actually does do something.  Since I
> use a "canned" route-map for all peers, I have to use the
> neighbor 3ffe:1ced:ff02::2 prefix-list AS-ARNEILLPY in on your
> peering session.

Now I understand why you do it this way. I'm curious about one thing,
though. Can't you use a peer-group for transit? You could probably have
a common route-map for transit (just match the STRICT) and reserve the
canned route-map with people that require special handling.

Michel.