More editorial fixes for draft-ietf-impp-pres-00.txt

***
Last paragraph of section 3.1: We've already have a lot of confusion with
the zero-duration subscribes (used for both unsubscribe and fetch).  In the
beginning of section 3.1 we give an example that pertains to fetch.  We
should amend the last paragraph, where we give an example on unsubcribe, to
clarify that the resulting notify should be discarded.

***
Also in the paragraph before last of section 3.4.1 and in section 3.4.3 we
have the same issue as above.

Perhaps adding somewhere something like this:

Note: A subscription with a zero-duration has a dual purpose:

(a) Using it with an existing subscription identifier (i.e. that of a
previously requested and still unexpired subscription) it is used to
prematurely cancel that subscription.  In this case the resulting notify
should be discarded

(b) using it with a non-existent (i.e. not previously used, or expired)
subscription identifier will perform a one-time "fetch".  If an existing
subscription identifier is used, that subscription will be cancelled, as
described above.

***
In section 3.4.3:

   When an application wants to terminate a subscription, it issues a
   SUBSCRIBE 0 with the transID of an existing subscription.

and

   When an application wants to directly request presence information to
   be supplied immediately without initiating any persistent
   subscription, it issues a SUBSCRIBE 0 with a new transID.


transID needs to be replaced with subscriptID

***
Lastly, in Appendix B2, we probably should replace "pepp" with something
more realistic such as "simple".

Thanos
---
Thanos Diacakis
Openwave Systems
[email protected]
+1-303 385 6705






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