Re: [dispatch] I-D Action: draft-malas-dispatch-sip-egress-route-00

Dean Willis <dean.willis@softarmor.com> Wed, 24 March 2010 18:08 UTC

Return-Path: <dean.willis@softarmor.com>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 80C0D3A6D7F for <dispatch@core3.amsl.com>; Wed, 24 Mar 2010 11:08:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.874
X-Spam-Level:
X-Spam-Status: No, score=0.874 tagged_above=-999 required=5 tests=[AWL=-0.257, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1PVxnp0W1wTN for <dispatch@core3.amsl.com>; Wed, 24 Mar 2010 11:08:16 -0700 (PDT)
Received: from nylon.softarmor.com (nylon.softarmor.com [66.135.38.164]) by core3.amsl.com (Postfix) with ESMTP id 324A73A6D88 for <dispatch@ietf.org>; Wed, 24 Mar 2010 11:08:10 -0700 (PDT)
Received: from [130.129.28.97] (dhcp-wireless-open-abg-28-97.meeting.ietf.org [130.129.28.97]) (authenticated bits=0) by nylon.softarmor.com (8.14.3/8.14.3/Debian-5) with ESMTP id o2OI7gBm025033 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 24 Mar 2010 13:07:45 -0500
Message-ID: <4BAA54EE.1050503@softarmor.com>
Date: Wed, 24 Mar 2010 13:07:42 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100317)
MIME-Version: 1.0
To: Hadriel Kaplan <HKaplan@acmepacket.com>
References: <114DAD31379DFA438C0A2E39B3B8AF5D01213F66AA@srvxchg> <564499D5-6303-4727-AD8C-996D182D9726@softarmor.com> <114DAD31379DFA438C0A2E39B3B8AF5D01213F66B8@srvxchg> <A79E5225-6DDE-4CA0-8AD3-B051FFB4086E@softarmor.com> <4B8ED7D2.8000806@nostrum.com> <7B1FAD89-E5FC-44EC-AA0A-F373CC37A407@softarmor.com> <114DAD31379DFA438C0A2E39B3B8AF5D01213F66F6@srvxchg> <74FBDCFA-9869-4809-BAC2-AAA59304B69B@softarmor.com> <114DAD31379DFA438C0A2E39B3B8AF5D01213F672D@srvxchg> <A41BE080-4142-4D50-AED6-E9072FBBE474@softarmor.com> <4B99EAD7.9090407@teigre.com> <4B9E56B7.6070009@nostrum.com> <4B9E5B9E.7030907@cisco.com> <4B9E5F47.2040604@nostrum.com> <4B9E616C.1000208@cisco.com> <4B9E6F60.1040703@nostrum.com> <430FC6BDED356B4C8498F634416644A91A79CD1CB7@mail>
In-Reply-To: <430FC6BDED356B4C8498F634416644A91A79CD1CB7@mail>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: "dispatch@ietf.org" <dispatch@ietf.org>
Subject: Re: [dispatch] I-D Action: draft-malas-dispatch-sip-egress-route-00
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2010 18:08:18 -0000

Hadriel Kaplan wrote:
> 
>> -----Original Message----- From: dispatch-bounces@ietf.org
>> [mailto:dispatch-bounces@ietf.org] On Behalf Of Adam Roach Sent:
>> Monday, March 15, 2010 1:33 PM
>> 
>> Daryl is working within the strictures of reproducing the business 
>> relationships of the PSTN in a SIP network. And the path that has
>> been taken, for better or worse, involves the heavy use of SBCs and
>> other devices that impose a rather strict control on the way things
>> are done. These devices largely ensure that the media path follows
>> the signaling path, even when that's not the optimal thing to do.
> 
> Optimal for whom, and in what way?

Optimal in the "internet" sense: the shortest/least used available
route, as would be described by the IP routing topology from address A to B.

> 
>> The chances of such networks deploying video, hi-def voice, or any
>> of the other really neat things that Greger mentions are slim to
>> none. This, of course, is NOT Daryl's fault. But it's where the
>> egress-route work comes from.
> 
> You seem to have some very odd (and typical IETF bull) preconceptions
> about what SBC's can do or are capable of doing.  SBC's in general
> support video, HD voice, or any of the other neat things Gregor
> mentions.  Policies provisioned on the SBC's may limit what media one
> can do, or in some cases if transcoding has to happen then obviously
> you're limited to whatever codecs the transcoders can handle (as any
> media gateway would be), but that's really tangential.

I believe Adam is referring to the fact that it's the old-school telecom
people who are building this sort of topology. They don't have a great
history of successful innovation. They occasionally try to offer a new
service, but only after it's been much more successfully deployed in an
"Internet" fashion by the new-school people. Does Youtube require SBCs?
How about iTunes? AOL's Instant messenger? Facebook?


> 
> 
>> Greger is speaking more towards the network you seem to have in
>> mind -- one in which end-to-end SIP calls are possible, without
>> SBCs or similar control boxes clobbering new services and mangling
>> the ability to convey novel media from one endpoint to another.
>> Networks where we don't need to define alternate connection models
>> for protocols simply to accommodate network elements that do things
>> that are explicitly disallowed by protocol specification.
> 
> As a B2BUA, what SBC's do is in no way disallowed by the protocols in
> the IETF. (although certainly I don't really care if they are ;)

Right. What they do is controlled by the policies and mindsets of those
who purchase and install them. They live in a different world, where
innovation is slow and painful. It's also a world where long-term
reliability and stability are heavily rewarded.

> 
> 
>> Which is why I support a simple, non-normative, informational draft
>>  about the form of URLs that one might want to put in ENUM. It
>> satisfies the requirements of the stagnant world, and doesn't even
>> have any normative impacts on any protocol anywhere. It's harmless,
>> and lets the people in the vibrant world concentrate on solving the
>> problem in a more general way without having to accommodate the
>> peculiarities of network elements living in the stagnant world.
> 
> If you live in this "vibrant world" the rest of us don't, what
> problems are there that need solving??  Usually one needs users and a
> population >1 to have problems.  The future always looks rosy
> compared to the present.

Why are the kids migrating towards Facebook/Youtube etc. as their
communications channels?

--
Dean