Hi, My interpretation is that you resolve per typical RFC 3263 rules first (although potentially higher likelihood of failure). Then if the request's size exceeds the threshold (and not CANCEL or non-2xx ACK), attempt to use reliable transport to the same IP address and port that you would have used for UDP. If it fails (as described within RFC 3261 section 18.1.1), the device should retry using UDP (with appropriate Via adjustments).
Concerning your same priority question, the following is within RFC 2915 section 7.1. It basically means that you have no preference. "note that the values of the order and preference fields are equal in all records, so the client is free to pick any record." > -----Original Message----- > From: [email protected] [mailto:sip- > [email protected]] On Behalf Of Taisto Qvist > Sent: Friday, April 25, 2014 6:37 AM > To: [email protected] > Subject: [Sip-implementors] Transport Selection dependent on message > size and NAPTR priorities (pitting rfc3261 vs rfc3263) > > Hey Sippers, > > I would like to get everyones option on the interpretation of how to > select transport protocol in rfc3261/3. > > It mainly concerns the issue of when to allow rfc3261's rule of "if > bigger than 1300, use reliable transport", over-ride the rules of > rfc3263. > > Since I've always been of the persuasion that I want to avoid IP > fragmentation as much as possible, I've always considered the 1300-rule > to override NAPTR priorities, but discussions have made me realize that > the text in rfc3263 which refers to this rule, is referenced regarding > to scenarios with the URI containing IP address and/or port. > > So the simple question is, should the message size over-ride NAPTR > priorities? Is the rfc3261 rule of chapter 18.1.1 more "important" or > not? > > Additionally, can you see any useful scenario of using SAME priority > NAPTRs for your supported transport protocols? > > Best Regards > Taisto Qvist > (S)IP Teacher and Developer > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors -- This email is intended solely for the person or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient and have received this email in error, please notify BroadSoft, Inc. immediately by replying to this message, and destroy all copies of this message, along with any attachment, prior to reading, distributing or copying it. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
