40 likes | 170 Views
Old MVPN Draft. d raft-rosen-vpn-mcast-00: November, 2000 First MVPN specification Contained number of proposals, including the one that was to be implemented and deployed d raft-rosen-vpn-mcast-07: May, 2004 First major update Eliminated description of non-implemented proposals
E N D
2010-03-22 Old MVPN Draft • draft-rosen-vpn-mcast-00: November, 2000 • First MVPN specification • Contained number of proposals, including the one that was to be implemented and deployed • draft-rosen-vpn-mcast-07: May, 2004 • First major update • Eliminated description of non-implemented proposals • Brought up-to-date with implementation
2010-03-22 Old MVPN Draft • draft-rosen-vpn-mcast-09, July 2008 • After remaining unchanged for several years, revised to bring up to date with Cisco’s deployment • Many parts of it implemented by multiple vendors • Now at revision 13 • Still describes most deployments • With luck, future deployments will be standards-based, won’t need to keep modifying this draft
2010-03-22 Should be Published as Historical RFC • Worth archiving: • Still describes numerous deployments • Has historical importance • I don’t want to have to keep issuing it every six months (with new boilerplate) • Needs to be called RFC ___ instead of its current informal name • MVPN standards from WG now available • Old draft is not “end run” around WG
2010-03-22 Individual vs. WG • Can be submitted as Individual Submission • RFC editor then asks IESG if it’s okay, • IESG asks WG, etc. • Saves time and work if WG approves in advance