[Ietf-carddav] charter comments

[Marc Blanchet]

my comments on charter sent by Chris (http://www1.ietf.org/mail- 
archive/web/discuss/current/msg00600.html)

...
This includes:
<MB>
An example from a customer of ours, if this may be useful to the  
charter.
* A contact database service used for sales management, where  
multiple users may access and change contacts in the database
</MB>
...

This WG will produce the following two primary outputs:

* A revision of the vCard spec (RFC 2426) likely at proposed standard
  status.  The WG will attempt to avoid adding new features, with two
  exceptions: 1. The WG may consider including other proposed  
standard vCard
  extensions (e.g., RFC 4770, RFC 2739).  2. The WG may evaluate  
extensions
  that would assist synchronization technologies (for example, a per- 
entry
  UUID or per-attribute sequence number).
<MB>
3. The WG should define a way to properly handle extensions with a  
possible central registry in an extension name space.
</MB>

* An address book access protocol leveraging the vCard data format.  The
  Internet-draft draft-daboo-carddav will be the starting point.
  The WG is explicitly cautioned to keep the base specification  
feature set
  small with an adequate extension mechanism, as failure to do so was a
  problem for previous PAB efforts (ACAP).  The WG will consider  
arguments
  of the form "feature X must be in the base feature set because ..."
  with great skepticism.


These documents will consider security implications carefully.
<MB>s/carefully//</MB>

...

<MB>
Should we have a requirement document to start with?
</MB>