奥村です。
お疲れ様です。

以下のメールを英訳してください。

-----------------------------------------------------------------------
[1] 12. Examplesの
	M1の
	      Contact: <sip:watcher@example.com>
	は
	      Contact: <sip:watcher@10.0.0.1>
	
	M2の
	      Contact: <sip:pa@example.com>
	は
	      Contact: <sip:pa.example.com>

	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
				.....
	は
	      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] 12. Examplesの例は
       PUA <---> PA <---> WATCHER
の他に
       PUA <---> proxy <---> PA
という例も欲しい。
例えば
       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] Request-URIはメッセージの宛先として使い、プレゼンスリソースの
	指定はToヘッダで行うようにした方が良いと思う。
	REGISTERによるロケーション登録と同じ動作に方がわかりやすい。
	この点はRFC3265についても同じことが言える。
	なぜなら、RFC3256には

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

とあるからである。

[4]プレゼンスリソースをあらわすURIはsip-URIではなく、
pres-URI(draft-ietf-impp-pres-04)が良いと思う。

結局[3][4]を合わせると以下のようなURIの使い方が良いと思う。
+------------+-----------------------------+-----------------------------+-----------------------------+
|            | 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 |
+------------+-----------------------------+-----------------------------+-----------------------------+


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
___________________________________________________________
奥村 伸二 (株)ソフトフロント 〒060-0009 北9条西15丁目28-195
tel:+81-11-623-1003             mailto:shin@softfront.co.jp
fax:+81-11-623-1005                sip: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