Last Modified: 2010-02-23
Nov 2010 | Submit General Framework, General Requirements, and Priorities/Work-Plan documents to the IESG to be considered as Informational RFC | |
Nov 2010 | Submit a framework document describing protocol groups and the common techniques and interfaces that apply to them to the IESG to be considered as Informational RFC | |
Dec 2010 | ubmit a document describing best practices for creating and using protocol message authentication integrity keys as a BCP | |
Apr 2011 | Submit specification document for OSPFv2 to the IESG to be considered as a Proposed Standard | |
Apr 2011 | Submit specification document for BGP to the IESG to be considered as a Proposed Standard | |
Jul 2011 | Submit specification document for OSPFv3 to the IESG to be considered as a Proposed Standard | |
Jul 2011 | Submit specification document for LDP to the IESG to be considered as a Proposed Standard | |
Oct 2011 | Submit specification document for PIM to the IESG to be considered as a Proposed Standard | |
Oct 2011 | Submit specification document for RSVP-TE to the IESG to be considered as a Proposed Standard | |
Nov 2011 | Specify automated key management needs for routing protocols using unicast techniques | |
Jan 2012 | Submit specification document for ISIS to the IESG to be considered as a Proposed Standard | |
Jan 2012 | Submit specification document for PCE to the IESG to be considered as a Proposed Standard | |
Apr 2012 | Submit specification document for MSDP to the IESG to be considered as a Proposed Standard | |
Apr 2012 | Specify automated key management needs for routing protocols using multicast techniques | |
Apr 2012 | Submit specification document for BFD to the IESG to be considered as a Proposed Standard | |
Jul 2012 | Submit specification document for LMP to the IESG to be considered as a Proposed Standard |