[Robutness] teleconferce -- March 1, 2000 11AM EST USA

[Maureen Stillman]

The next robustness teleconference will be held on March 1, 2000 at 11AM EST
USA.  Please send me e-mail at maureen.stillman at nokia.com if you plan to
attend so I can reserve sufficent resources.

The dial in number is:
(613)688-2795
The passcode is: 1235# (you must put in the pound sign)

Agenda:

1) Discussion of the Robutness Framework document outline (attached) and
2) Solicit volunteers to fill in text for the outlined sections

SG-16 Geneva meeting summary on robustness:

The robutness ad hoc working group met several times and covered the
following topics:

1) revisions to the Radvision submission on Robustness Procedure document
Delayed-460.  The revised document is WG2/TD 87
http://ties.itu.int/u/tsg16/sg16/td/wp2/2-087.doc.

TD 87 was presented at the meeting and conditionally accepted for inclusion
in H.323v4 and H.225.  We are required to supply SDL for the robustness
procedure by the SG-16 May, 2000 Rapporteur's meeting to ensure the
document's ultimate inclusion in the standard.

The robustness submission presented a robustness procedure for:

        *       Detection of a TCP based connection failure
        *       Synchronization of the two sides of the connection
concerning the call state
        *       Definition of recommended behavior in order to renew the
call signaling connection and proceed as normal with the call
        *       In the case of GK failure, the procedure allows calls to
proceed without any interruption.

2) we worked on a Robustness framework outline (attached).  The goal is to
complete the framework document in time to submit it to the SG 16 meeting
May 15-19.

Here is some text from the opening summary:

The H.323 series of Recommendations provides some support for building
robust systems recommendations (e.g. support for specification of alternate
gatekeepers and alternate endpoints). However, by themselves, these are
incomplete.  There are a number of unspecified issues such as:  How are
alternate endpoints and alternate gatekeepers used to "reconnect" calls that
were in progress when a failure occurred?  What signaling procedures are
used to reconnect such calls and which device initiates the procedures?  It
is assumed that a well-defined model and explicit signaling procedures are
needed to allow development of complete and interoperable solutions.
However, no detailed procedures are specified in H.323 for dealing with
system failures and re-establishing communication links after such a
failure.

This document proposes a framework towards providing robustness mechanisms
in H.323 followed by the definition of robustness procedures for handling
scenarios that are consistent with the framework.
 <<Robustness Framework 01.ZIP>>

-- maureen

Maureen Stillman
Member of Scientific Staff             Voice: (607)273-0724 x62
Nokia IP Telephony                      Fax: (607)275-3610
127 W. State Street                     Mobile: (607)227-2933
Ithaca, NY 14850
e-mail: maureen.stillman at nokia.com
www.nokia.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Robustness Framework 01.ZIP
Type: application/octet-stream
Size: 24709 bytes
Desc: not available
URL: <https://lists.packetizer.com/pipermail/sg16-avd/attachments/20000224/6a967e01/attachment-0003.obj>