RE: initial draft to bootstrap some discussions

[Mark Prior <]

At 4:35 AM +0200 19/10/01, Peirens, Bart wrote:
> import protocol <protocol> into <protocol> should be kept for current
>  use I think, being redistribution between  protocols. While it's true
>  that there is probably little to none public data with this people are
>  also using RPSL style databases internally.
Look at AS2764 in the RADB :-)

> I don't have a clean backwards compatible proposal for this yet except
>  not  allowing  direct references to v6 prefixes but force  people to
>  use route-set's (which tools  would understand and just ignore the
>  members6 attributes in it then)
I don't think this should be a major concern. Anyone building a 
policy with IPv6 or multicast extensions should be assumed to be 
using tools that will cope with it. There could be issues with people 
who are using other people's objects but I suspect that is a minor 
issue. In the case of Connect they use their own database to build 
their router configurations but maintain a copy of their data at 
RADB. I would suspect that anyone who is seriously using RPSL data 
would be doing likewise and so updating their own local data while 
retaining old format data in a public registry shouldn't be an issue.

Mark.
--