IETF Logo Mail Archive

Re: [rtcweb] RTCWEB and emergency services

Iñaki Baz Castillo <ibc@aliax.net> Tue, 27 September 2011 19:45 UTC

Return-Path: <ibc@aliax.net>
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 436DE21F8FF2 for <rtcweb@ietfa.amsl.com>; Tue, 27 Sep 2011 12:45:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.636
X-Spam-Level:
X-Spam-Status: No, score=-2.636 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 UOgB3pBiUOXl for <rtcweb@ietfa.amsl.com>; Tue, 27 Sep 2011 12:45:33 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id A2A4021F8FEB for <rtcweb@ietf.org>; Tue, 27 Sep 2011 12:45:33 -0700 (PDT)
Received: by vws5 with SMTP id 5so8643356vws.31 for <rtcweb@ietf.org>; Tue, 27 Sep 2011 12:48:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.23.4 with SMTP id i4mr7782450vdf.514.1317152899468; Tue, 27 Sep 2011 12:48:19 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Tue, 27 Sep 2011 12:48:19 -0700 (PDT)
In-Reply-To: <CA+9kkMBAy2AXi+DwKjqJOr1yFaXYiG96iDPi1oZGuU6HwbBDkA@mail.gmail.com>
References: <BLU152-W318BAE2CE0C609B1BB45CD93F30@phx.gbl> <CA+9kkMA5zZe7D+2F_MmfJgkJCS9CRpDMN3zn=uTjMina-pGaAw@mail.gmail.com> <BLU152-W39115E9C2A50B4A634789093F00@phx.gbl> <CA+9kkMBAy2AXi+DwKjqJOr1yFaXYiG96iDPi1oZGuU6HwbBDkA@mail.gmail.com>
Date: Tue, 27 Sep 2011 21:48:19 +0200
Message-ID: <CALiegfmbTL6e1HW95QzAt-AYgMUu3sEyyR4SgRuMrNAVMqibmQ@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] RTCWEB and emergency services
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: Tue, 27 Sep 2011 19:45:34 -0000

2011/9/27 Ted Hardie <ted.ietf@gmail.com>:
> If you must describe in the terms of telephony, please circumscribe your
> terms--"For RTCWeb applications intended to provide telephony services, the
> following considerations apply...."  But generalizing the whole application
> space to telephony, even for the benefit of emergency services, is not where
> I think we ought to go.

I agree. I don't know where this topic comes from, but IMHO it makes
no sense to consider a WebRTC provider a "usual" PSTN operator. It
would be a show-stopper.

-- 
Iñaki Baz Castillo
<ibc@aliax.net>

v2.14.0 | Report a Bug | By Email