About RIPE | Contact  | Search | Sitemap    
Homepage RIPE  
RIPE Community Mail Archives
search  
     
RIPE Navigation Ends
About RIPE Maillists
Maillists Archive
Global Lists
Non Active Lists
RIPE NCC Navigation Ends
Next Section
<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Re: initial draft to bootstrap some discussions

  • To: Mark Prior < >
  • From: Florent Parent < >
  • Date: Thu, 18 Oct 2001 15:58:36 -0400 (EDT)

mrp@localhost wrote:

> Well the "normal" way you use it is to say things like
>
> import: protocol STATIC into BGP4
> 	from AS2764
> 	accept AS2764:RS-PROVIDER^0-30
>
> so maybe what you want would be specified as
>
> import: protocol IPv6 into RIP
> 	from AS2764
> 	accept ANY
>
> Can you explain what you are trying to do so we can attempt to be on
> the same wavelength :-)

Nothing specific in mind, but I'm looking if we can specify the same
rules in IPv6 and IPv4:

Retaking your example:

 import: protocol STATIC into BGP4
       from AS2764
       accept AS2764:RS-PROVIDER^0-30

In IPv6, would that be equivalent to the following (abstraction made for
the prefix length values)? :

 import: protocol IPv6 into BGP4
       from AS2764
       accept AS2764:RS-PROVIDER^0-30

Seems that we loose the fact that we wanted to inject static routes only.
Should the dictionary be extended to specify IPv6 to the protocol values ?
(OSPF6, RIP6, STATIC6, ...)

That was why I previously mentionned that an extra keyword may be needed:

 import: address-family IPv6 protocol STATIC into BGP4
       from AS2764
       accept AS2764:RS-PROVIDER^0-30

Keep in mind that I may fail to see something obvious here. But I can
learn ;-)

Florent.





  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>
 

Next Section
     About RIPE | Site Map | LIR Portal | About the RIPE NCC | Contact | © RIPE Community. All rights reserved.
RIPE.NET Homepage LIR Portal RIPE Community