Robert Table 1 shows the restrictions on the allowed values in a SIP or SIPS URI of a Contact, depending on the context of use.
It does not discuss the scheme types allowed in a Contact, based on the usage context. Specifically, I am unable to see how your conclusion below can be divined from this table. Minor nit: Table 1 does not have a caption at the bottom, unlike tables 2 and 3. Venkat -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Robert Sparks Sent: Tuesday, December 03, 2002 10:10 AM To: M. Ranganathan Cc: Prasanna Venkatesh; [EMAIL PROTECTED] Subject: Re: [Sip-implementors] Are non-sip URLs in Contact allowed? Note that Table 1 splits Contact URIs into those that appear in dialog creating/maintaining messages and those that appear in registrations and redirects. The text restricts the dialog related contacts to a single sip or sips URI. Registrations and redirection messages can contain multiple URIs of arbitrary type. I may wish to register a mailto: URI. I may wish to redirect your request to a mailto: or http: URI. RjS On Tue, 2002-12-03 at 07:15, M. Ranganathan wrote: > Thanks for your reply. > > That was indeed the reason for my confusion. I think Contact is supposed > to be sip URI for 200 OK or INVITE . > > > One should note that the original spec (2543) had Contact optinal but > now Contact is required in certain cases. Consequently it makes life > very confusing when Contact is not a SIP URI. I would be grateful if > somebody could give me an example where contact is not SIP URI and why > not just mandate that the Contact header must always be a SIP URI in the > ABNF as Prasanna is asking below? > > Thanks > > Ranga. > > > > > Prasanna Venkatesh wrote: > > >Section 8.1.1.8 mentions that the Contact should be a SIP/SIPs URI. But > >this section does not form a part of the normative definitions. However the > >ABNF in section 25 allows any URI. > >If the specs enforces the Contact to be a SIP/SIPs URI should'nt the ABNF > >also reflect it. > >Regards, > >Prasanna > > > > > >-----Original Message----- > >From: [EMAIL PROTECTED] > >[mailto:[EMAIL PROTECTED]]On Behalf Of M. > >Ranganathan > >Sent: Monday, December 02, 2002 9:58 PM > >To: [EMAIL PROTECTED] > >Subject: [Sip-implementors] Are non-sip URLs in Contact allowed? > > > > > >Hello! > > > >Does the latest spec allow non-sip urls in the contact header? If so, > >how are non-sip URIs in contact headers interpreted? > > > >Thanks for your replies. > > > >Regards > > > >Ranga > > > >-- > >M. Ranganathan > >N.I.S.T. Advanced Networking Technologies Division > >100 Bureau Drive, Stop 8920, Gaithersburg, MD 20899 > > > >tel:301-975-3664 fax:301-590-0932 > >http://w3.antd.nist.gov/index.html mailto:[EMAIL PROTECTED] > >Advanced Networking Technologies for the people! > > > > > >_______________________________________________ > >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 > > > > > > -- > M. Ranganathan > N.I.S.T. Advanced Networking Technologies Division > 100 Bureau Drive, Stop 8920, Gaithersburg, MD 20899 > > tel:301-975-3664 fax:301-590-0932 > http://w3.antd.nist.gov/index.html mailto:[EMAIL PROTECTED] > Advanced Networking Technologies for the people! > > > > _______________________________________________ > 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 _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
