RIPE-181 to RPSL, Carol Orange, RIPE NCC
Slide 1: Concerns
Stability
User support
Timeliness
Slide 2: Deployment Phases - User View
1. Write ripe-181 - Read ripe-181
2. Write ripe-181 - Read either
3. Write either - Read RPSL
4. Write RPSL - Read RPSL
Slide 3: Phase 1. RPSL Development
Started in January 1997 (ISI)
Code is nearly ready:
- testing
- incorporation in RIPE DB code
- documentation
- transition code needed
Slide 4: Phase 2. Updates in RIPE-181
Translated to RPSL
Read RIPE-181 or RPSL
Slide 5: Phase 2. Opportunities for Users
See how RPSL looks
Adapt tools to read RPSL
More user experience needed
Slide 6: Phase 2: Autnum Updates in RPSL
Locked to assure consistency
Opportunities:
- Write peering policies in RPSL
- Aut-num writing tool development
Slide 7: Phase 2: Development Efforts
Provide Documentation
Set up training
Slide 8: Phase 3: Write RIPE-181 or RPSL
Read RPSL only
Phase 3: Prerequisites (1)
- Good documentation
- User education underway
- n months stable on test-site
- tool development
- user adjustment
- problem detection
- training support
Slide 9: Phase 4:
Write RPSL/Read RPSL
Final phase.
All phase 3 prerequisites hold