The fifth in a series of conference calls to discuss a reliable transport protocol to be used with MoIP was held on Friday, June 29, 2001.

As agreed at the Porto Seguro, BR, meeting of ITU-T SG16, the goal of these conference calls is to develop a joint contribution to the next meeting of TR-30.1 giving requirements for the MoIP reliable transport mechanism, and possibly an evaluation of existing protocols against those requirements. Once the requirements and possible evaluations have been presented to TIA TR-30.1 and agreed to by them, the requirements and possible evaluations are, if possible, to be presented to the IETF 51 meeting in London, UK, during the week of 8/5/2001. Some parties may present a draft protocol proposal to that meeting.

On the call from The CommWorks Corp. were: - Fred Lucas; and - Jim Renkel.

From Cisco Systems were:

- Herb Wildfeuer; and - Mehryar Garakani.

The call began by discussing the draft summary of the fourth conference call. It was pointed out that the call was held Tuesday, June 26, not Friday, June 22. With that correction, the summary was accepted.

Then, two new conference calls were scheduled. The schedule for the next three calls is: - Friday, July 6, 2001, 10:30 A.M., CDT - Tuesday, July 10, 2001, 10:30 A.M., CDT - Friday, July 13, 2001, 10:30 A.M., CDT The dial-in bridge number remains +1.847.262.0999, conference ID # 06647 ("0MOIP" on a touch-tone keypad.). Because the TR-30.1 meeting is the week of July 16, 2001, these will be the last conference calls before that meeting.

Next, it was agreed that Jim Renkel will edit the joint contribution to the TR-30.1 meeting. Jim will have a first draft of the joint contribution available before the July 6 conference call, based on all language received by noon, CDT, July 5. The goal is to have all new language for the joint contribution first crafted by close-of-business July 6,2001. The two conference calls the following week will be used to review, revise, and approve the document.

It was then agreed that the reliable transport requirements will be written in the style given by IETF RFC 2119.

Finally, Mehryar Garakani's draft language for packet-based, sequenced, expedited delivery, and low latency requirements was discussed and modified. Additional requirements for robustness in the face of congestion control and transmit rate limiting, and for being light weight were discussed. Jim will include the language in the first draft of the joint contribution for the next conference call.