Media Gateway Control Protocol (MGCP) Lockstep State Reporting Mechanism
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: RFC Editor <email@example.com> Cc: The IESG <firstname.lastname@example.org>, <email@example.com>, firstname.lastname@example.org Subject: Re: Informational RFC to be: draft-foster-mgcp-lockstep-02.txt The IESG has no problem with the publication of 'Media Gateway Control Protocol (MGCP) Lockstep State Reporting Mechanism' <draft-foster-mgcp-lockstep-02.txt> as an Informational RFC. The IESG would also like the IRSG or RFC-Editor to review the comments in the datatracker (https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=9728&rfc_flag=0) related to this document and determine whether or not they merit incorporation into the document. Comments may exist in both the ballot and the comment log. The IESG contact person is Jon Peterson. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-foster-mgcp-lockstep-02.txt The process for such documents is described at http://www.rfc-editor.org/indsubs.html. Thank you, The IESG Secretary
Technical Summary A Media Gateway Control Protocol (MGCP) endpoint that has encountered an adverse failure condition such as being involved in a transient call when a Call Agent failover occurred could be left in a lockstep state such that events are quarantined but not notified. The MGCP package described in this document provides a mechanism for reporting these situations so that the new Call Agent can take the necessary fault recovery procedures. Working Group Summary This document was not the product of an IETF WG. Protocol Quality This document was reviewed for IETF conflicts by Jon Peterson.