IETF-55

Applications area open meeting

XML directorate

My presentation: http://www.ninebynine.org/IETF/XML/IETF-55-Presentation.html

Issue really one of web-aware applications, rather than just XML?

Later, after discussion with several people, my proposed plan for further work:

A. NEXT STEPS

Unless I hear from folks that I'm on the wrong track, or I'd be wasting my time, I propose to initiate some steps along the lines below.

1. Call it something else:  "XML Technologies Directorate" has been suggested, and seems to hit the mark.  I think this better helps people to understand what we're trying to cover.

2. Reformulate the draft charter to reflect this note,  with focus along the lines of on being a source of information and resources relating to XML and related technologies in IETF protocols.

3. I'd like to be clear who are the directorate members -- Patrik told me, but I may have forgotten some names.  Should the membership be public?

4. Create a web page for the directorate, with links to useful resources (documents, presentations, etc.).  This will be some work initially, but I hope it will mean that we can direct questioners to this when an issue has already been given attention.  I see this as a living forum for dissemination of information and ideas to a wider IETF audience.

5. Publicize the mailing list archive -- I understand this is intended to be a public discussion forum, though it's not widely known at the moment.

6. Create an issue list (on the web site, of course):  a summary of topics we've considered or are considering and out conclusions to date.  I see this as (a) an aid to focus directorate discussions, and (b) part of the means to communicate our views to a wider audience.

7. When there's something to see, announce the directorate and its web site on the apps discussion list.

B. QUESTIONS FOR IESG/IAB

1. What are the expected modes of interaction between the directorate, IETF working groups and participants, IESG, IAB and other bodies?

C. INITIAL ISSUES FOR CONSIDERATION

These are some suggestions based on my own observations and discussions with other people:

1. SOAP - clarifying what it is, and deciding when it's appropriate to use.  What are the alternatives?

2. XML-RPC - is this something whos use we want to encourage (given that it overlaps some aspects of SOAP).

3. Encapsulation:  what are the options for shipping binary data with XML?

4. Namespaces:  recommendations for namespaces in IETF protocols?  What to use for stable URIs?

5. Security:  relationship between XMLDSIG, XMLENC S/MIME, OpenPGP, PKIX, XKMS, etc.  When to use what.

6. Authorization/access control:  relationship between generic XML activities (SAML, XACML) and authorization structures in specific IETF protocols (e.g. IMPP, WEBDAV).

7. Considerations for deciding to use XML (c.f. my presentation and Junoscript draft).