CPIM issues summary

"Adrian Bateman" <[email protected]> writes:

> It would be nice to focus efforts on putting to bed what we have done -
> I'm afraid I haven't had much time in the last 6 weeks to contribute to
> this, but do we still have a valid work list of the things that are
> currently outstanding?

Enclosed is a list of issues focused on the CPIM draft in no
particular order.

1. The syntax of instant inbox URIs and presence URIS should be
   defined and used consistently within the document.

2. 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.

3. Graham Klyne comments.  I don't think these have all been
   addressed.  See

   http://www.imppwg.org/ml-archive/IMPP-WG/200201/msg00004.html

4. 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. 

---------

5. The role of transaction identifiers should be made more clear by
   replacing them with conversation identifiers for IM, and
   subscription identifiers for presence.

6. At one point, I suggested there be support for a premature
   subscription termination notification, and that notifications
   receive replies, but these changes do not seem to have support.

7. A wrapper for presence information be defined that contains a name
   that identifies a presence service, and nothing else.

8. Allowance be made for the eventual addition of signed subscription
   requests.

John



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