In case you haven't seen them, RFC 5630 and draft-ietf-sipcore-sec-flows might help your understanding of sips.
> -----Original Message----- > From: [email protected] [mailto:sip- > [email protected]] On Behalf Of chozhan A > Sent: Monday, November 30, 2009 4:07 AM > To: [email protected] > Subject: [Sip-implementors] SIPS scheme usage > > Hi All, > > Section 8.1.1.8 of RFC 3261 mandates the contact to be of SIPS scheme > when the nexthop is SIPS (from a UA stand point) > I believe this is applicable to all kind of SIP request message > including REGISTER. > In that case when a REGISTER is sent to sips:example.com;transport=TCP > registrar what should be the contact scheme be? > Is it correct to register a SIPS contact over a non-tls transport? > > Section 26.2.2 of RFC3261 depricates transport=tls uri parameter. Is > this parameter depricated only for SIPS URI or for SIP URI also? > > Regards > AC _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
