PUBLISH has nothing to do with the dialog created by SUBSCRIBE. They are orthogonal.
Regards, Hisham > -----Original Message----- > From: ext Franz Edler [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 10, 2003 5:45 PM > To: [EMAIL PROTECTED] > Cc: Niemi Aki (NMP/Helsinki) > Subject: [Sip-implementors] Questions on URIs in SUBSCRIBE/NOTIFY > (RFC3265) > > > Hi all, > > can anybody please confirm my following assumptions on some URIs in > SUBSCRIBE/NOTIFY messages: > > SUBSCRIBE is a dialog creating method and therefore the > addresses sent in > the Contact-header of the request and the response should be > used as request > URIs in subsequent requests. Therefore > > 1. A NOTIFY-request should use the URI of the Contact-header of > SUBSCRIBE-request as Request URI. > > 2. SUBSCRIPTION refresh requests should use the URI of the > Contact-header of > the 200-response to SUBSCRIBE as Request URI. > > 3. If the same UA also uses PUBLISH-requests, it should also > adhere to the > above rules and use the URIs exchanged in the Contact-headers > of existing > SUBSCRIPTION based dialogs. > > Unfortunately RFC 3265 does not address this point explicitly > and there is > also no example message flow in RFC 3265. > > Thank you for clarification or (hopefully) confirmation. > > Franz > > PS: The background of my question comes from an irritation > when I look at > the details of the examples in > "draft-ietf-simple-publish-01.txt". I think > there are some corrections necessary regarding the request > URIs and URIs in > From- and To-headers. > > > _______________________________________________ > Sip-implementors mailing list > [EMAIL PROTECTED] > http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
