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: RPSLng task force outline

  • To: Andrei Robachevsky < >
  • From: Florent Parent < >
  • Date: Fri, 5 Oct 2001 06:14:57 -0400 (EDT)

>
> Starting this discussion I think we aim at making modifications to RPSL
> (RPS-auth?) spec. I am not sure that the guidelines for RPSL
> extensibility outlined in section 10 of RFC2622 are clear enough and
> don't require more consideration as we move forward.
>
> Therefor I would like to know your opinion whether this forum is the
> right place to conduct this kind of discussion.

Your opinion is as good as mine :-)

Am I reading you correctly in saying that we should consider rfc2725
(rps-auth) as a base to our work ? If so, definitely. This was mentionned
in the original outline sent to me by Joachim, and I kept it in the
outline.

We are at the point where we need to consider all current RPSL standards,
and then work from these to identify our requirements.

We should add a reference section in the outline. Here is a start. We'll
add more as more comments come in.

References
----------
Routing Policy Specification Language (RPSL), rfc2622
Routing Policy System Security, rfc2725
The 6bone registry, draft-ietf-ngtrans-6bone-registry-xx.txt

Thanks Andrei

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