Media Gateway Control Protocol (MGCP) Lockstep State Reporting Mechanism
draft-foster-mgcp-lockstep-01

[Note]: 'This is supposed to be an Individual Submission via the RFC-Editor document, if I''m not mistaken. And please include this IESG note:     This document is being published for the information of the
  community.  It describes a non-IETF protocol that is currently being
  deployed in a number of products.  Implementers should be aware of
  RFC 3015, which was developed in the IETF Megaco Working Group and
  the ITU-T SG16, and which is considered by the IETF and the ITU-T to
  be the standards-based (including reviewed security considerations)
  way to meet the needs that MGCP was designed to address.
' added by Amy Vezza

[Note]: 'This is supposed to be an Individual Submission via the RFC-Editor document, if I''m not mistaken. And please include this IESG note:  
   This document is being published for the information of the
   community.  It describes a non-IETF protocol that is currently being
   deployed in a number of products.  Implementers should be aware of
   RFC 3015, which was developed in the IETF Megaco Working Group and
   the ITU-T SG16, and which is considered by the IETF and the ITU-T to
   be the standards-based (including reviewed security considerations)
   way to meet the needs that MGCP was designed to address.
' added by Jon Peterson

[Note]: 'This is supposed to be an Individual Submission via the RFC-Editor document, if I''m not mistaken.

And please include this IESG note:

   This document is being published for the information of the
   community.  It describes a protocol that is currently being deployed
   in a number of products.  Implementers should be aware of
   developments in the IETF Megaco Working Group and ITU SG16 who are
   currently working on a potential successor to this protocol.
' added by Jon Peterson

[Ballot comment]
I think we should continue to put the IESG Note for MGCP that we've used, rather than the
IESG Note for RFC Editor documents (just to be consistent).  It has similar effect.

[Ballot comment]
It would be helpful to note the normative BNF specification for the BNF used in this document.  Is it as described in RFC 2234?  2234 is a reference in RFC 3435.