PROTO questionnaire for: draft-ietf-sipping-toip-07.txt prepared by: Mary Barnes (mary.barnes@nortel.com) Date: 15 Sept 2006 1.a) Have the chairs personally reviewed this version of the Internet Draft (ID), and in particular, do they believe this ID is ready to forward to the IESG for publication? Which chair is the WG Chair Shepherd for this document? Yes, the WG chairs have reviewed this version and believe the ID is ready. Mary Barnes is the WG Chair Shepherd for this document. 1.b) Has the document had adequate review from both key WG members and key non-WG members? Do you have any concerns about the depth or breadth of the reviews that have been performed? The document has been reviewed by WG members, with no concerns about the depth or breadth of the review. 1.c) Do you have concerns that the document needs more review from a particular (broader) perspective (e.g., security, operational complexity, someone familiar with AAA, internationalization, XML, etc.)? No. 1.d) Do you have any specific concerns/issues with this document that you believe the ADs and/or IESG should be aware of? For example, perhaps you are uncomfortable with certain parts of the document, or have concerns whether there really is a need for it. In any event, if your issues have been discussed in the WG and the WG has indicated it that it still wishes to advance the document, detail those concerns in the write-up. No. 1.e) How solid is the WG consensus behind this document? Does it represent the strong concurrence of a few individuals, with others being silent, or does the WG as a whole understand and agree with it? There is WG consensus behind this document, with adequate time for discussion and resolution of issues raised. 1.f) Has anyone threatened an appeal or otherwise indicated extreme discontent? If so, please summarise the areas of conflict in separate email to the Responsible Area Director. (It should be separate email because this questionnaire will be entered into the tracker). Yes, one individual has continued to express discontent over a non-technical issue. 1.g) Have the chairs verified that the document checks out against all the ID nits? (see http://www.ietf.org/ID-Checklist.html). Boilerplate checks are not enough; this check needs to be thorough. Yes. 1.h) Has the document split its references into normative and informative? Are there normative references to IDs, where the IDs are not also ready for advancement or are otherwise in an unclear state? The RFC Editor will not publish an RFC with normative references to IDs (will delay the publication until all such IDs are also ready for RFC publicatioin). If the normative references are behind, what is the strategy for their completion? On a related matter, are there normative references that are downward references, as described in BCP 97, RFC 3967 RFC 3967 [RFC3967]? Listing these supports the Area Director in the Last Call downref procedure specified in RFC 3967. The references are split into normative and informative. There are two normative reference that are not yet published as RFCs: 14. G. Camarillo, "Framework for Transcoding with the Session Initiation Protocol" IETF May 2006 - Work in progress. 16. G. Camarillo, "The SIP Conference Bridge Transcoding Model," IETF, January 2006 - Work in Progress. However, these two documents have undergone IESG review and it is anticipated that they would be published as RFCs prior to the publication of this document. There are no normative references which are downward references. ------ Protocol write-up for: draft-ietf-sipping-toip-07.txt by Mary Barnes, mary.barnes@nortel.com, 15 Sept 2006 Technical Summary This document lists the essential requirements for real-time Text- over-IP (ToIP) and defines a framework for implementation of all required functions based on the Session Initiation Protocol (SIP) and the Real-Time Transport Protocol (RTP). This includes interworking between Text-over-IP and existing text telephony on the PSTN and other networks. Working Group Summary The SIPPING WG supports the development and advancement of this ocument. Protocol Quality This document defines no new protocol elements. This document was thoroughly reviewed by WG chairs and WG members. Mary Barnes is the WG chair shepherd. Jon Peterson is the responsible Area director.