Re: [rtcweb] Requiring ICE for RTC calls

"Richard Shockey" <richard@shockey.us> Fri, 30 September 2011 01:20 UTC

Return-Path: <richard@shockey.us>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 821A321F8BD5 for <rtcweb@ietfa.amsl.com>; Thu, 29 Sep 2011 18:20:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.895
X-Spam-Level:
X-Spam-Status: No, score=-99.895 tagged_above=-999 required=5 tests=[AWL=0.285, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wxpRZiUlhv5g for <rtcweb@ietfa.amsl.com>; Thu, 29 Sep 2011 18:20:15 -0700 (PDT)
Received: from oproxy9.bluehost.com (oproxy9.bluehost.com [IPv6:2605:dc00:100:2::a2]) by ietfa.amsl.com (Postfix) with SMTP id 7598321F8BD3 for <rtcweb@ietf.org>; Thu, 29 Sep 2011 18:20:14 -0700 (PDT)
Received: (qmail 12065 invoked by uid 0); 30 Sep 2011 01:23:07 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy9.bluehost.com with SMTP; 30 Sep 2011 01:23:07 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:Cc:To:From; bh=N0rAx2pn04EF78mcfDaPnwgvOmD4rcl1m2NyXt+DE+s=; b=Wj5/H5Fjb24ePSxPGGQqkxeu9FfBrrfEuylbFIgXTCiGH75+WUyRhJDtuSzWRcOR9QZVKKM/YOtj1cLFLV642oTuNX0VLBBN2a0QK7HyPxVTqaSzJQRQwd3ynTLM45Gn;
Received: from pool-71-178-24-118.washdc.fios.verizon.net ([71.178.24.118] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.76) (envelope-from <richard@shockey.us>) id 1R9Rog-0000qj-NS; Thu, 29 Sep 2011 19:23:06 -0600
From: "Richard Shockey" <richard@shockey.us>
To: "'Hadriel Kaplan'" <HKaplan@acmepacket.com>
References: <CAD5OKxtNjmWBz92bRuxka7e-BUpTPgVUvr3ahJGpmZ-U5nuPbQ@mail.gmail.com><CAD6AjGSmz5T_F+SK2EoBQm6T-iRKp7dd4j8ZAF5JKdbbyomZQA@mail.gmail.com><CALiegfmO54HC+g9L_DYn4jtXAAbLEvS++qxKa6TNrLDREs9SeA@mail.gmail.com><4E80984A.903@skype.net><CALiegfmyvTb57WVooKryS-ubfcg+w5gZ+zfO1zzBLn3609AzaA@mail.gmail.com>, <4E809EE6.2050702@skype.net>, <2E239D6FCD033C4BAF15F386A979BF510F1087@sonusinmail02.sonusnet.com> <BLU152-W62B7F2AC3F0D5B6E277CB993F00@phx.gbl> <9790CEA7-59E6-4E14-9D5D-F9669E95036E@cisco.com> <02f701cc7efe$8b44b2f0$a1ce18d0$@us> <9723F40D-0889-4DCF-B44D-99E05A3EDC69@acmepacket.com>
In-Reply-To: <9723F40D-0889-4DCF-B44D-99E05A3EDC69@acmepacket.com>
Date: Thu, 29 Sep 2011 21:23:04 -0400
Message-ID: <030f01cc7f0f$81704f80$8450ee80$@us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
thread-index: AQHMfwmGBJpjUg7wrk6AbHnaTx82fZVlHXvQ
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 71.178.24.118 authed with richard@shockey.us}
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Requiring ICE for RTC calls
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Sep 2011 01:20:16 -0000

On Sep 29, 2011, at 7:21 PM, Richard Shockey wrote:

> RS> And at the rate this discussion is going it is reasonable to assume
that
> it might be 10 years before RTCWEB might be able to reach consensus. But
for
> what it's worth the end of POTS/PSTN is under active discussion. If for no
> other reason than the  backplanes of the 5E's and DMS 500's are literally
> cracking at a increasing pace. Remember 3G mobile networks still use TDM
> Switches. Bernard's point is well taken RTCWEB shouldn't worry about
> interconnection some gateway or border element will normalize that problem
> in some way shape or form. 

But it's not "POTS" that's really the point - it's the "PSTN".  From the
perspective of this group, the "PSTN" is everything reachable through SIP
service providers: every cell/mobile phone, DSL/Cablemodem MTA, PRI trunk,
SIP Enterprise trunk, POTS landline, etc.  There are more of those right now
than there are devices on the Internet.[1]  And way more of those than
number of users and Web Browsers on the Internet.[2]


Ok but that is a distinction that is causing lots of problems in identifying
the real issue. The PSTN as you put it, is essentially a national and
internationally regulated business model of mandated interconnection for
realtime communications that uses E.164 addressing. It's a policy construct.
It's a set of national specific rules, regulations, emergency services and
cost recovery models. 

POTS, as I would prefer it to be defined, is the technical underpinning of
everything in the PSTN reachable through SIP service providers etc and
that's what we are ultimately talking about.   And yes you are right there
are more POTS end points out there than devices on the Internet, until we
get rid of POTS and fold them into the "greater good" of IP and that process
is progressing very well as far as I can tell. 

Confusing the two is going to cause everyone a lot of grief. 



-hadriel

[1] Based on several sources which claim approx 5 Billion mobile phones, 1.2
Billion POTS lines, and hundreds of millions of MTAs, and untold number of
PRI and SIP trunks; which I'm guesstimating totals about 7 Billion.
Compared to approx 5 Billion current devices on the Internet, according to
www.imsresearch.com. (though they include things like printers and cameras
in their counts)

[2] Based on ~2 Billion users, from www.internetworldstats.com and
data.worldbank.org.