Skip to main content

Media Gateway Control Protocol (MGCP) Lockstep State Reporting Mechanism
RFC 3992

Revision differences

Document history

Date Rev. By Action
2005-02-24
01 Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2005-02-24
01 Amy Vezza [Note]: 'RFC 3992' added by Amy Vezza
2005-02-18
01 (System) RFC published
2004-09-15
01 Amy Vezza State Changes to RFC Ed Queue from Approved-announcement sent by Amy Vezza
2004-09-10
01 Amy Vezza IESG state changed to Approved-announcement sent
2004-09-10
01 Amy Vezza IESG has approved the document
2004-09-10
01 Amy Vezza Closed "Approve" ballot
2004-08-20
01 (System) Removed from agenda for telechat - 2004-08-19
2004-08-19
01 Amy Vezza State Changes to Approved-announcement to be sent::Point Raised - writeup needed from Waiting for AD Go-Ahead by Amy Vezza
2004-08-19
01 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:    …
[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
2004-08-19
01 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:  
   …
[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
2004-08-19
01 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 …
[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
2004-08-19
01 David Kessens [Ballot Position Update] New position, No Objection, has been recorded for David Kessens by David Kessens
2004-08-19
01 Bert Wijnen [Ballot Position Update] New position, No Objection, has been recorded for Bert Wijnen by Bert Wijnen
2004-08-19
01 Harald Alvestrand [Ballot Position Update] New position, No Objection, has been recorded for Harald Alvestrand by Harald Alvestrand
2004-08-19
01 Allison Mankin
[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 …
[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.
2004-08-19
01 Allison Mankin [Ballot Position Update] New position, No Objection, has been recorded for Allison Mankin by Allison Mankin
2004-08-19
01 Margaret Cullen [Ballot Position Update] New position, No Objection, has been recorded for Margaret Wasserman by Margaret Wasserman
2004-08-17
01 Ted Hardie [Ballot Position Update] New position, No Objection, has been recorded for Ted Hardie by Ted Hardie
2004-08-16
01 Russ Housley [Ballot Position Update] New position, No Objection, has been recorded for Russ Housley by Russ Housley
2004-08-16
01 Jon Peterson [Note]: 'This is supposed to be an Individual Submission via the RFC-Editor document, if I''m not mistaken.' added by Jon Peterson
2004-08-13
01 Scott Hollenbeck [Ballot Position Update] Position for Scott Hollenbeck has been changed to No Objection from Undefined by Scott Hollenbeck
2004-08-13
01 Scott Hollenbeck
[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 …
[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.
2004-08-13
01 Scott Hollenbeck [Ballot Position Update] New position, Undefined, has been recorded for Scott Hollenbeck by Scott Hollenbeck
2004-08-13
01 Jon Peterson Placed on agenda for telechat - 2004-08-19 by Jon Peterson
2004-08-13
01 Jon Peterson [Ballot Position Update] New position, Yes, has been recorded for Jon Peterson
2004-08-13
01 Jon Peterson Ballot has been issued by Jon Peterson
2004-08-13
01 Jon Peterson Created "Approve" ballot
2004-08-13
01 (System) Ballot writeup text was added
2004-08-13
01 (System) Last call text was added
2004-08-13
01 (System) Ballot approval text was added
2004-07-31
01 Jon Peterson State Changes to Waiting for AD Go-Ahead from Publication Requested by Jon Peterson
2003-10-06
01 Jon Peterson Intended Status has been changed to Informational from None
2003-09-22
01 Amy Vezza Area acronymn has been changed to tsv from gen
2003-09-18
01 Jon Peterson Draft Added by Jon Peterson
2003-07-25
01 (System) New version available: draft-foster-mgcp-lockstep-01.txt
2002-12-02
00 (System) New version available: draft-foster-mgcp-lockstep-00.txt