Skip to main content

Media Gateway Control Protocol (MGCP) Redirect and Reset Package
draft-foster-mgcp-redirect-05

Revision differences

Document history

Date Rev. By Action
2004-09-15
05 Amy Vezza State Changes to RFC Ed Queue from Approved-announcement sent by Amy Vezza
2004-09-10
05 Amy Vezza IESG state changed to Approved-announcement sent
2004-09-10
05 Amy Vezza IESG has approved the document
2004-09-10
05 Amy Vezza Closed "Approve" ballot
2004-08-20
05 (System) Removed from agenda for telechat - 2004-08-19
2004-08-19
05 Amy Vezza State Changes to Approved-announcement to be sent::Point Raised - writeup needed from IESG Evaluation by Amy Vezza
2004-08-19
05 Amy Vezza
[Note]: 'Please include this IESG note:   This document is being published for the information of the
  community.  It describes a non-IETF protocol that …
[Note]: '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
05 Jon Peterson
[Note]: 'Please include this IESG note:

   This document is being published for the information of the
   community.  It describes a non-IETF protocol that …
[Note]: '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
05 David Kessens [Ballot Position Update] New position, No Objection, has been recorded for David Kessens by David Kessens
2004-08-19
05 Amy Vezza State Changes to IESG Evaluation from Waiting for Writeup by Amy Vezza
2004-08-19
05 Bert Wijnen [Ballot Position Update] New position, No Objection, has been recorded for Bert Wijnen by Bert Wijnen
2004-08-19
05 Harald Alvestrand [Ballot Position Update] New position, No Objection, has been recorded for Harald Alvestrand by Harald Alvestrand
2004-08-19
05 Allison Mankin [Ballot comment]
Use our MGCP IESG note rather than the RFC Editor IESG note
2004-08-19
05 Allison Mankin [Ballot Position Update] New position, No Objection, has been recorded for Allison Mankin by Allison Mankin
2004-08-19
05 Margaret Cullen [Ballot Position Update] Position for Margaret Wasserman has been changed to No Objection from Undefined by Margaret Wasserman
2004-08-19
05 Margaret Cullen [Ballot Position Update] New position, Undefined, has been recorded for Margaret Wasserman by Margaret Wasserman
2004-08-17
05 Ted Hardie [Ballot Position Update] New position, No Objection, has been recorded for Ted Hardie by Ted Hardie
2004-08-16
05 Russ Housley [Ballot Position Update] Position for Russ Housley has been changed to No Objection from Undefined by Russ Housley
2004-08-16
05 Russ Housley [Ballot comment]
Throughout the document:  s/whatever.net/example.com/
2004-08-16
05 Russ Housley [Ballot Position Update] New position, Undefined, has been recorded for Russ Housley by Russ Housley
2004-08-13
05 Scott Hollenbeck [Ballot Position Update] Position for Scott Hollenbeck has been changed to No Objection from Undefined by Scott Hollenbeck
2004-08-13
05 Scott Hollenbeck
[Ballot comment]
Example values provided in places like section 2.1 should use one of the example domain names described in RFC 2606.

It would …
[Ballot comment]
Example values provided in places like section 2.1 should use one of the example domain names described in RFC 2606.

It would also 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
05 Scott Hollenbeck [Ballot comment]
Example values provided in places like section 2.1 should use one of the example domain names described in RFC 2606.
2004-08-13
05 Scott Hollenbeck [Ballot Position Update] New position, Undefined, has been recorded for Scott Hollenbeck by Scott Hollenbeck
2004-08-13
05 Jon Peterson [Ballot Position Update] New position, Yes, has been recorded for Jon Peterson
2004-08-13
05 Jon Peterson Ballot has been issued by Jon Peterson
2004-08-13
05 Jon Peterson Created "Approve" ballot
2004-08-13
05 (System) Ballot writeup text was added
2004-08-13
05 (System) Last call text was added
2004-08-13
05 (System) Ballot approval text was added
2004-08-13
05 Jon Peterson Placed on agenda for telechat - 2004-08-19 by Jon Peterson
2004-07-31
05 Jon Peterson State Changes to Waiting for Writeup from Publication Requested by Jon Peterson
2003-09-22
05 Amy Vezza Area acronymn has been changed to tsv from gen
2003-09-22
05 Michael Lee Removed from agenda for telechat - 2003-09-18 by Michael Lee
2003-09-18
05 Jon Peterson Shepherding AD has been changed to Jon Peterson from Harald Alvestrand
2003-09-18
05 Natalia Syracuse Draft Added by Natalia Syracuse
2003-07-23
05 (System) New version available: draft-foster-mgcp-redirect-05.txt
2003-06-27
04 (System) New version available: draft-foster-mgcp-redirect-04.txt
2003-06-02
03 (System) New version available: draft-foster-mgcp-redirect-03.txt
2003-04-24
02 (System) New version available: draft-foster-mgcp-redirect-02.txt
2002-12-02
01 (System) New version available: draft-foster-mgcp-redirect-01.txt
2002-10-04
00 (System) New version available: draft-foster-mgcp-redirect-00.txt