A Data Model for Presence
draft-ietf-simple-presence-data-model-07

[Ballot comment]
I believe publication of this document may be harmful to the Internet.
In particular I believe that this document modifies data structures
used outside the context of Simple in ways that are specific to
Simple.  The presence documents that this data model modifies are part
of CPIM and thus are used for interoperability between multiple
instant messaging systems.  While I this document takes steps to avoid
interoperability problems, There are several potentially harmful
interactions with CPIM.

1) This document doesn't give advice on how to generate presence
documents useful both to watchers who understand this data model and
to watchers who do not understand this model.


2) This document doesn't give advice sufficient to implement watchers
that can make reasonable use both of CPIM style presence documents and
that can make use of the data model documents.

3) I'm concerned that the interactions when multiple IM/communications
systems start using this model have not been fully considered.


I was not able to determine that these issues had been considered
adequately so I am abstaining.

[Ballot comment]
I believe publication of this document would be harmful to the
Internet and urge others to abstain.  In particular I believe that
this document modifies data structures used outside the context of
Simple in ways that are specific to Simple.  In particular, the
presence documents that this data model modifies are part of CPIM and
thus are used for interoperability between multiple instant messaging
systems.  However there is no significant discussion of CPIM
interoperability in this document nor does it seem that this document
was significantly reviewed beyond the Simple community.  There are
several potentially harmful interactions with CPIM.

1) This document doesn't give advice on how to generate presence
documents useful both to watchers who understand this data model and
to watchers who do not understand this model.


2) This document doesn't give advice sufficient to implement watchers
that can make reasonable use both of CPIM style presence documents and
that can make use of the data model documents.

3) I'm concerned that the interactions when multiple IM/communications
systems start using this model have not been fully considered.

As such, I believe this document has received inadequate consideration
and review.

[Ballot discuss]
The Security Considerations say:
  >
  > The presence information described by the model defined here is very
  > sensitive.  It is for this reason that privacy filtering plays a key
  > role in the processing of presence data, as described above.
  >
  Where?  A search for "privacy" will lead the reader only to the
  Security Considerations.  A search for "filter" will lead the reader
  to Section 3.3.1 and the Security Considerations.  Perhaps a better
  short description is needed.

[Ballot discuss]
This document needs an Internationalization Considerations section.  I see that the note element include a "lang" attribute, but there's no discussion of how this attribute should be used or of the larger issues associated with internationalization.

[Ballot comment]
Should note that it updates 2778 and 3863 in the Abstract.

2778 is given as an Informative reference.
Are we sure it isn't actually a downref Normative reference?

[Ballot discuss]
The W3C XML and XML Schema specs need to be added as normative references.

This document needs an Internationalization Considerations section.  I see that the note element include a "lang" attribute, but there's no discussion of how this attribute should be used or of the larger issues associated with internationalization.

IANA Last Call Comments:
Upon approval of this document the IANA will register 1 XML Namespace and 2 XML Schemas at the following registries:
http://www.iana.org/assignments/xml-registry/ns.html
http://www.iana.org/assignments/xml-registry/schema.html

This is the PROTO writeup for the submission of:
draft-ietf-simple-presence-data-model-06

1. The chairs have reviewed this version of the ID and
  ask that the IESG consider it for publication.

2. This document reflects one culmination of a debate
  spanning years withing the working group. (See
  the many instances of the "what is a tuple" discussion
  in the mailing list archives).

3. The chairs do not believe further cross-area review
  is needed. Scott Hollenbeck participated in the XML
  specific engineering done in the later part of this
  documents development.

4. There are no additional exceptional concerns to bring to the
  attention of the IESG.

5. The consensus behind this document has been forged over
  years, reflects many compromises, and is quite solid.

6. There have been no indications of intent to appeal.

7. This document adheres to ID-nits.

8. The document appropriately splits references into
  Informative/Normative.

9. Announcement Writeup

Technical Summary
 
  This document builds on the model defined in RFC 2778 clarifying
  the underlying presence data model used by Session Initiation
  Protocol (SIP) for Instant Messaging Leveraging Presence
  Extensions (SIMPLE) presence agents. In particular, the document
  clarifies what a tuple models and provides guidance on mapping
  real-world communications systems into a presence document.

Working Group Summary

  This document has been through many extensive working group
  discussions. It reflects well forged compromise, and a strong
  working group consensus.

Protocol Quality

  Hisham Khartabil was the PROTO shepherd for this document.

  Interoperable exchange of presence documents based on this
  model has been seen at several of the SIP Interoperability
  Test Events (SIPITs).