[j-nsp] v6 BGP Policy Bug?

[Mark Tinka]

On Wednesday 15 April 2009 11:09:18 am Stacy W. Smith wrote:

> There's a difference between a final term of:
>
> term foo {
>      then accept;
> }
>
> and the protocol-specific implicit default policy. In the
> case of BGP, the default policy is equivalent to:
>
> policy foo {
>      term bar {
>          from protocol bgp;
>          then accept;
>      }
> }

That's right, which is what we see for the export policies 
we applied to our IS-IS deployment. I guess the issue we're 
seeing with wrong behaviour for the v4 BGP export policy 
kind of threw us off with what to expect for v6.

Let me debug this. Will come back if I find anything 
interesting.

Cheers,

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20090415/aa35f17b/attachment.bin>