Re: [Sip] WGLC for PUBLISH

Hi,

[1] I believe it requires following changes in some headers of
    the illustrated example in section 12.

    In M1,   Contact: <sip:watcher@example.com> should be rewritten as
             Contact: <sip:watcher@10.0.0.1>

    In M2,   Contact: <sip:pa@example.com> should be
             Contact: <sip:pa.example.com>

    In M3,    NOTIFY sip:presentity@example.com SIP/2.0
              Via: SIP/2.0/UDP pa.example.com;branch=z9hG4bK8sdf2
              To: <sip:watcher@example.com>;tag=12341234
              From: <sip:presentity@example.com>;tag=abcd1234
              Call-ID: 12345678@10.0.0.1
              CSeq: 1 NOTIFY
              ....

              should be

              NOTIFY sip:watcher@10.0.0.1 SIP/2.0
              Via: SIP/2.0/UDP pa.example.com;branch=z9hG4bK8sdf2
              To: <sip:watcher@example.com>;tag=12341234
              From: <sip:presentity@example.com>;tag=abcd1234
              Call-ID: 12345678@10.0.0.1
              CSeq: 1 NOTIFY
              Contact: <sip:pa.example.com>
              ....
 
[2] It could be helpful if the following example (2) is added in 
    the document as an addition to the only example (1) illustrated 
    in section 12.

    (1) PUA <---> PA <---> WATCHER

    (2) PUA <---> proxy <---> PA

        For example:

        PUA <-----> proxy <------> PA
         |            |            |
         | M1 PUBLISH |            |
         |----------->| M2 PUBLISH |
         |            |----------->|
         |            | M3 200 OK  |
         | M4 200 OK  |<-----------|
         |<-----------|            |
 
        M1:
            PUBLISH sip:pa@example.com SIP/2.0
            Via: SIP/2.0/UDP pua.example.com;branch=z9hG4bK652hsge
            From: <sip:presentity@example.com>;tag=1234wxyz
            To: <pres:presentity@example.com>
            Call-ID: 81818181@pua.example.com
            CSeq: 1 PUBLISH
            Max-Forwards: 70
            Expires: 3600
            Event: presence
            Content-Type: application/pidf+xml
            Content-Length: ...
 
        M2:
            PUBLISH sip:pa.example.com SIP/2.0
            Via: SIP/2.0/UDP proxy.example.com;branch=z9hG4bKpx123
            Via: SIP/2.0/UDP pua.example.com;branch=z9hG4bK652hsge
            From: <sip:presentity@example.com>;tag=1234wxyz
            To: <pres:presentity@example.com>
            Call-ID: 81818181@pua.example.com
            CSeq: 1 PUBLISH
            Max-Forwards: 70
            Expires: 3600
            Event: presence
            Content-Type: application/pidf+xml
            Content-Length: ...
 
        M3:
            SIP/2.0 200 OK
            Via: SIP/2.0/UDP proxy.example.com;branch=z9hG4bKpx123
            Via: SIP/2.0/UDP pua.example.com;branch=z9hG4bK652hsge
            From: <sip:presentity@example.com>;tag=1234wxyz
            To: <pres:presentity@example.com>;tag=1a2b3c4d
            Call-ID: 81818181@pua.example.com
            CSeq: 1 PUBLISH
            SIP-ETag: dx200xyz
            Expires: 1800
            Content-Length: 0
 
        M4:
            SIP/2.0 200 OK
            Via: SIP/2.0/UDP pua.example.com;branch=z9hG4bK652hsge
            From: <sip:presentity@example.com>;tag=1234wxyz
            To: <pres:presentity@example.com>;tag=1a2b3c4d
            Call-ID: 81818181@pua.example.com
            CSeq: 1 PUBLISH
            SIP-ETag: dx200xyz
            Expires: 1800
            Content-Length: 0
 
[3] It could be better if the "Request-URI" is used as the message's
    target address and the 'Presence Resource' is specified using "To"
    header.

    It would be easy for understanding if REGISTER's location 
    registration operation like mechanism is considered.

    The same point could also be said about RFC3265. This is because,

        |3.1.5. Proxy SUBSCRIBE Behavior
        |  Proxies need no additional behavior beyond that described in SIP [1]
        |  to support SUBSCRIBE.

[4] For expressing 'Presence Resource', the pres-URI(draft-ietf-impp-pres-04)
    would be better than that of the sip-URI.

    Finally, when [3] & [4] are considered together, the various usages 
    of URI can be expressed as listed below.

+------------+-----------------------------+-----------------------------+-----------------------------+
|            | PUBLISH                     | SUBSCRIBE                   | NOTIFY                      |
+------------+-----------------------------+-----------------------------+-----------------------------+
|Request-URI | URI of PA                   | URI of PA                   | Contact-URI of SUBSCRIBE    |
|            | sip:pa@example.com          | sip:pa@example.com          | sip:watcher.example.com     |
+------------+-----------------------------+-----------------------------+-----------------------------+
|To-URI      | URI of presence resource    | URI of presence resource    | From-URI of SUBSCRIBE       |
|            | pres:presentity@example.com | pres:presentity@example.com | sip:watcher@example.com     |
+------------+-----------------------------+-----------------------------+-----------------------------+
|From-URI    | URI of presentity           | URI of watcher              | To-URI of SUBSCRIBE         |
|            | sip:presentity@example.com  | sip:watcher@example.com     | pres:presentity@example.com |
+------------+-----------------------------+-----------------------------+-----------------------------+

Regards,
shinji

Rohan Mahy wrote in <C3094B8F-4563-11D8-B291-0003938AF740@cisco.com>
>Hi,
>
>I'd like to begin Working Group Last Call for PUBLISH:
>
>	http://www.ietf.org/internet-drafts/draft-ietf-sip-publish-02.txt
>
>This WGLC will end on January 28, 2004.
>
>thanks,
>-rohan
_________________________________________________
OKUMURA Shinji        E-mail:shin@softfront.co.jp

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip