Issue Summary

I've sent out many messages lately, so I thought I would describe how
all the messages fit together.  The messages raise issues in four
categories.

1. Signed Subscription Requests

To address this issue I have:

  a. proposed a common subscription data format, and

  b. requested that CPIM be changed to make subscription IDs distinct
     from transaction IDs, and specify how subscription IDs are
     included in requests and responses.

2. Signed notification requests

To address this issue, I suggest two things be done.

  a. The CPIM document should be changed so that the NOTIFY operation
     include a parameter (or attribute if you will) called "From" and
     states that it describes the originator of the presence
     information.  Presence services that sign notifications will know
     what to do with this field.

  b. The CPIM-PIDF document should be changed to specify that presence
     information can be wrapped in CPIM-MSGFMT, and the From field in
     that format must identify the originator of the presence
     information. 

3. Gateway protocol enhancements

I have suggested to enhancements to allow more information to be
passed by a gateway.

  a. I suggest notifications receive replies, as is the case for
     SIMPLE.  The motivation for replies is the same as the one for
     replies for instant messages.

  b. A mechanism be included that allows subscribers to be notified
     when their subscription is prematurely terminated.  Again, SIMPLE
     includes this feature.  I suggest subscription state information
     be transmitted within a PIDF document by adding an attribute
     declared as follows:

       <!ATTLIST presense state (normal|terminated)  "normal">

     where state="terminated" is included in notification content only
     when a subscription is terminated prematurely.

4. Editorial requests

The issue here is that, the CPIM document seems to be internally
inconsistent.  Section 3.4.3 states there is no explicit UNSUBSCRIBE
command, but Section 8 contains XML syntax for this command.

Also don't forget Hiroyasu's comment, quoted here.

---------

There is an inconsistency between CPIM and CPIM-MSGFMT. 

In draft-ietf-impp-cpim-02.txt, section 2.3, 

     An INSTANT MESSAGE comprises a MIME
     Type="message/cpim,profile=im" object, as defined in
     XML/MIME[6] and MESSAGE/CPIM PROFILE FOR INSTANT
     MESSAGING. 

But, there is no description about the "profile" parameter in the MSGFMT doc. 
Because I believe MSGFMT has passed WGLC, the CPIM doc should be 
changed.  Section 3.3 contains similar text for presence. 

---------

I am willing to supply text for any changes to CPIM I requested.

John


  [reminder: [email protected] for non-technical discussions, please]