- From: Mark Nottingham <mnot@mnot.net>
- Date: Fri, 9 Jun 2006 13:43:16 -0700
- To: www-tag@w3.org
FYI, in case the TAG (or someone else) wants to comment. Note that comments are due 2006-06-21. > From: The IESG <iesg-secretary@ietf.org> > Date: June 7, 2006 1:07:43 PM PDT > To: IETF-Announce <ietf-announce@ietf.org> > Cc: simple@ietf.org > Subject: Last Call: 'The Extensible Markup Language (XML) > Configuration Access Protocol (XCAP)' to Proposed Standard (draft- > ietf-simple-xcap) > Reply-To: iesg@ietf.org > > The IESG has received a request from the SIP for Instant Messaging > and Presence > > Leveraging Extensions WG to consider the following document: > > - 'The Extensible Markup Language (XML) Configuration Access > Protocol (XCAP) ' > <draft-ietf-simple-xcap-11.txt> as a Proposed Standard > > On 2005-6-21, the IESG approved draft-ietf-simple-xcap-07.txt. > Prior to its > being published as an RFC, new issues were raised which required > revision. The > IESG solicits review of this new version, in particular of Sections > 7.10, 7.11 & > 8.23 where the major changes were made. > > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send any comments to the > iesg@ietf.org or ietf@ietf.org mailing lists by 2006-06-21. > > The file can be obtained via > http://www.ietf.org/internet-drafts/draft-ietf-simple-xcap-11.txt The abstract: > This specification defines the Extensible Markup Language (XML) > Configuration Access Protocol (XCAP). XCAP allows a client to read, > write and modify application configuration data, stored in XML > format on a server. XCAP maps XML document sub-trees and element > attributes to HTTP URIs, so that these components can be directly > accessed by HTTP. See: https://datatracker.ietf.org/public/pidtracker.cgi? command=view_id&dTag=10621&rfc_flag=0 for the document's history. -- Mark Nottingham http://www.mnot.net/
Received on Friday, 9 June 2006 20:43:19 UTC