IETF IESG directorate for XML protocols --------------------------------------- Proposed charter Graham Klyne Created: 2002-07-19, Yokohama Revised: 2002-08-09 1. Problem statement The IETF is seeing a slew of proposals for protcols that use XML for protocol data and payload. It is not currently clear whether all of these need to use different mechanisms for actually moving the XML data; i.e. given the flexibility of XML to expressa different protocol content, do we really need the number of different protocols that are being proposed? When faced with a new XML-carrying protocol proposal, the IESG often don't have enough information to determine whether a new protocol is warranted, or whether an existing protocol can be used. 2. Goal of directorate The goal of this work will be to provide information that can help to guide the selection of appropriate technologies in different circumstances, and NOT to try and prescribe a unified framework for protocols delivering XML content. Also note that there is existing work that deals with how to use XML features in protocol design (currently,http://www.ietf.org/internet-drafts/draft-hollenbeck-ietf-xml-guidelines-05.txt) that has received considerable constructive review in the IETF, which it makes little sense to duplicate. 3. Work plan Initially, the plan will be to "map the territory"; any further work will depend on what such mapping may uncover. - discuss: what, if anything, is different about protocols using XML? - survey applications, user-requirements, use-cases for XML protocols. - identify functional or technical requirements and requirement-sets of XML protocols, with particular regard to where different application requirements may overlap or differ. - survey existing XML protocol technologies, and match them to the identified functional requirement-sets The result of this would be a survey document that identifies a range of usage scenarios, corresponding functional requirements, and notes, where applicable, existing IETF protocols that satisfy the functional requirements. This document is not intended to be in any way prescriptive. Depending on what this mapping uncovers, there may be work on a follow-up discussion that is more specifically advisory, dealing with a range of application protocol architecture issues that are raised (or highlighted) by use of XML. There is also a goal that the process of creating these documents would result in a standing body of folks with good awareness of how XML issues relate to IETF work, and who can provide advice as required to working group efforts. 4. People I've been advised to keep the number of people small, to move quickly. But also, I think it's important to canvas input from a wide range of potential users. Possible application areas to cover: network management, user messaging (e.g. IM), application-to-application messaging, web services, policy services, authorization services, ... [[[what else?]]] 5. Deliverables 2002-08-31: Publish initial draft of survey document. 2002-10-31: Publish revised draft incorporating feedback from reviewers. 2002-11-18: Meeting at 55th IETF, Atlanta; decide further steps (if any). 2002-12-15: Last-call survey document for RFC publication 2003-03-30: RFC publication 2003-04-??: Meeting at 56th IETF (wrap up, forward planning) 6. Further work It seems reasonable to anticipate that the surver work might lead to some kind of advisory position, suggesting where existing XML protocols might be selected, because such a document would hopefully lead to the IESG having to contend with fewer misapplied XML protocols. Assuming that such advice is felt to be desirable, a rechartering might be considered along the following lines. 2002-11-18: Meeting at 55th IETF, Atlanta; plan further steps. 2003-01-17: Publish initial draft of guideline document 2003-02-28: Publish revised draft incorporating feedback from reviewers 2003-04-??: Meeting at 56th IETF (discussion of guidelines draft) 2003-05-30: Last-call guideline document for RFC publication 2003-07-30: RFC publication 2006-07-14: Meeting/report at 57th IETF (wrap up) (Dominating the timescales here is a desire for some face-to-face time to discuss document issues prior to last-call. A more aggressive schedule would be to aim for initial discussion of a guideline document to take place at 55th IETF, with a view to last-calling the advisory document ahead of the 56th IETF. These are all details for discussion.) A desired side-effect of this work would be to draw together a suitable group and mailing list of interested people who can provide continuing advice concerning XML-related protocol issues, if needed. ----- $Log: ProtoCharter.txt,v $ Revision 1.1 2002/10/08 14:52:42 graham Moved IETF/XML files from work-in-progress Revision 1.3 2002/08/09 10:19:31 graham Minor edit Revision 1.2 2002/08/09 10:18:58 graham Added discssion of further work, beyond the initial technology survey. Revision 1.1 2002/08/09 10:02:03 graham Move to CVSWeb location Revision 1.3 2002/07/23 13:22:07 graham Enlarge structure Flesh out discussion of possible work beyond the initial survey document Revision 1.2 2002/07/23 13:08:14 graham Update to reflect IESG/IAB concerns that the initial work may appear to be prescriptive in nature.