Hi Franz, The point is that in the example, PUBLISH isn't sent inside the SUBSCRIBE-established dialog. There is no subscription prerequisite to sending a PUBLISH. It just happens that in this example, the subscription precedes the publications.
Cheers, Aki > -----Original Message----- > From: ext Franz Edler [mailto:[EMAIL PROTECTED] > Sent: 11 July, 2003 11:12 > To: Khartabil Hisham (NMP/Helsinki); [EMAIL PROTECTED] > Cc: Niemi Aki (NMP/Helsinki) > Subject: RE: [Sip-implementors] Questions on URIs in SUBSCRIBE/NOTIFY > (RFC3265) > > > Yes, I agree but RFC 3261 states in 8.1.1 about the Contact Header: > ... the Contact header field value contains the URI at which > the UA would > like to receive requests, and this URI MUST be valid even if used in > subsequent requests outside of any dialogs. > > And therefore it should have an impact on the population of > the request URI > of PUBLISH in example 10 of > "draft-ietf-simple-publish-01.txt", as the > SUBSCRIBE initiated dialog is preceding the PUBLISH request. > > Regards > Franz > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Freitag, 11. Juli 2003 09:12 > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > > 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
