On Tue, 2009-04-21 at 00:42 +0200, Iñaki Baz Castillo wrote: > El Martes, 21 de Abril de 2009, Vikram Chhibber escribió: > > Yes, in all these cases, the R-URI should be considered for > > identifying the target resource, but I am not sure what the "To > > header" is doing in RFC 3842 as pointed out by Brett. > > > > If the Request-URI or To header in a message-summary subscription > > corresponds to a group or collection of individual messaging > > accounts, the notifier MUST specify to which account the message- > > summary body corresponds. > > Sincerelly, I would consider it a typo. There are no more mention to "To" URI > in all the RFC 3842, and I think we should not try to "invent" any exotic > behaviour based on a single and ambiguos phrase. Let's assume the logical > behaviour and drop any ambiguity. Let's make life easy! :)
That seems like the only reasonable interpretation. Except for REGISTER, the To header is largely documentation. And given that the original RURI may have been retargeted several times before reaching the UAS, the UAS is not guaranteed that it can automatically interpret the To URI. Dale _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
