1 / 4

Old MVPN Draft

This document discusses the evolution of the MVPN draft, highlighting key revisions and the need for a formal RFC publication. Initially introduced in November 2000 as a specification with various proposals, significant updates were made in May 2004 and July 2008 to align with practical implementations by multiple vendors. The intention is to archive this historical draft as RFC, emphasizing its importance in describing numerous current deployments. Moving forward, it seeks to ensure that future revisions follow a standards-based approach, minimizing the need for frequent updates.

werner
Télécharger la présentation

Old MVPN Draft

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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

  2. 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

  3. 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

  4. 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

More Related