> -----Original Message----- > From: Dean Willis [mailto:dean.wil...@softarmor.com] > Sent: Wednesday, April 01, 2009 10:47 AM > To: Dan Wing > Cc: 'Hans Erik van Elburg'; 'Elwell, John'; 'Cullen > Jennings'; sip@ietf.org; 'Francois Audet'; 'DRAGE, Keith (Keith)' > Subject: Re: [Sip] francois' comments and why RFC4474 not > used in the field > > > On Apr 1, 2009, at 12:17 PM, Dan Wing wrote: > > > > > And I doubt that every VoIP SP will be meshed with every > other VoIP > > SP. So in > > many situations there will be a transit SP or two along the path. > > The PSTN > > has transit service providers (my local phone company is > not directly > > connected with the phone company in Syria or India), and the > > Internet has > > transit service providers (some little ISP in Wyoming is > not directly > > connected with a little ISP in Switzerland). > > But the transit ISP should be routing the packets using their source > and destination IP addresses, not mucking about in the application > protocol.
The transit SIP provider has every interest in hiding the IP addresses of their own equipment and of the actual peers. Otherwise, the peers may make their own business agreement and circumvent the 'service' being provided by the transit SIP provider -- or so the argument goes. > If some backbone ISP started putting in transparent HTTP > proxies that diverted Web traffic to alternate sites, we'd have a > "peasants with torches" scenario. Using that analogy, if we were using RFC4474 with HTTPS we would all have to trust our service providers (Comcast, etc.) to reliably deliver our credit card and banking information to transit providers and finally to our bank or catalog ordering company. > Same for most of the media-steering cases: The traffic is IP. > Route it > like IP traffic and stop pretending to be a circuit switched phone! > > Doing application-sensitive packet routing is a direct path to chaos > and unmanageable operational complexity. > > Or maybe we should have just defined SIP-over-MPLS and left out the > whole IP middle layer? Acme Packet supports routing over MPLS networks. -d _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implement...@cs.columbia.edu for questions on current sip Use sipp...@ietf.org for new developments on the application of sip
