Re: [stir] current draft charter

"DOLLY, MARTIN C" <md3135@att.com> Mon, 17 June 2013 18:03 UTC

Return-Path: <md3135@att.com>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BB8D21F9DA3 for <stir@ietfa.amsl.com>; Mon, 17 Jun 2013 11:03:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.51
X-Spam-Level:
X-Spam-Status: No, score=-6.51 tagged_above=-999 required=5 tests=[AWL=0.089, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 9h6ZZPr6iK5b for <stir@ietfa.amsl.com>; Mon, 17 Jun 2013 11:03:42 -0700 (PDT)
Received: from nbfkord-smmo05.seg.att.com (nbfkord-smmo05.seg.att.com [209.65.160.92]) by ietfa.amsl.com (Postfix) with ESMTP id 0B1B521F9D39 for <stir@ietf.org>; Mon, 17 Jun 2013 11:03:40 -0700 (PDT)
Received: from unknown [144.160.20.146] (EHLO nbfkord-smmo05.seg.att.com) by nbfkord-smmo05.seg.att.com(mxl_mta-6.15.0-1) with ESMTP id d7f4fb15.5042b940.303498.00-526.858452.nbfkord-smmo05.seg.att.com (envelope-from <md3135@att.com>); Mon, 17 Jun 2013 18:03:41 +0000 (UTC)
X-MXL-Hash: 51bf4f7d5f3a914e-65187b31525d46c1511b8cbae367499564711b9b
Received: from unknown [144.160.20.146] (EHLO mlpd194.enaf.sfdc.sbc.com) by nbfkord-smmo05.seg.att.com(mxl_mta-6.15.0-1) over TLS secured channel with ESMTP id 87f4fb15.0.303460.00-254.858322.nbfkord-smmo05.seg.att.com (envelope-from <md3135@att.com>); Mon, 17 Jun 2013 18:03:40 +0000 (UTC)
X-MXL-Hash: 51bf4f7c4bedc429-40b719d1cd201ff6b864ee65144ab78ed7a7fa8e
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r5HI3ZHP004117; Mon, 17 Jun 2013 14:03:36 -0400
Received: from mlpi407.sfdc.sbc.com (mlpi407.sfdc.sbc.com [130.9.128.239]) by mlpd194.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id r5HI3RcA003932 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Jun 2013 14:03:28 -0400
Received: from MISOUT7MSGHUB9C.ITServices.sbc.com (misout7msghub9c.itservices.sbc.com [144.151.223.82]) by mlpi407.sfdc.sbc.com (RSA Interceptor); Mon, 17 Jun 2013 18:03:13 GMT
Received: from MISOUT7MSGUSR9I.ITServices.sbc.com ([144.151.223.56]) by MISOUT7MSGHUB9C.ITServices.sbc.com ([144.151.223.82]) with mapi id 14.02.0342.003; Mon, 17 Jun 2013 14:03:19 -0400
From: "DOLLY, MARTIN C" <md3135@att.com>
To: "Peterson, Jon" <jon.peterson@neustar.biz>, Dan York <york@isoc.org>, Hadriel Kaplan <hadriel.kaplan@oracle.com>
Thread-Topic: [stir] current draft charter
Thread-Index: AQHOZwiVPvBwdWSMpuU+7zbFbFufQ5kxT0wAgAAL0QCAAIQHAIAAcu6AgAADDoCAABB/AP//41KAgABTd4CAAADrAIAABU0AgABkooCAAOCqgIAAU3yAgAA76gCABBp3gIAAEOyAgABhe4CAAHK1AIAAd7eAgACPXID//72T0A==
Date: Mon, 17 Jun 2013 18:03:18 +0000
Message-ID: <E42CCDDA6722744CB241677169E8365602189607@MISOUT7MSGUSR9I.ITServices.sbc.com>
References: <CDE4B900.E41A%york@isoc.org> <CDE49979.21B61%jon.peterson@neustar.biz>
In-Reply-To: <CDE49979.21B61%jon.peterson@neustar.biz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.175.86.19]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <md3135@att.com>
X-SOURCE-IP: [144.160.20.146]
X-AnalysisOut: [v=2.0 cv=EMyxJSlC c=1 sm=0 a=Qs8R1XBwmid1qBFB/a8mmA==:17 a]
X-AnalysisOut: [=CT05AzjYeewA:10 a=KIbchom90_cA:10 a=ofMgfj31e3cA:10 a=BLc]
X-AnalysisOut: [eEmwcHowA:10 a=kj9zAlcOel0A:10 a=zQP7CpKOAAAA:8 a=XIqpo32R]
X-AnalysisOut: [AAAA:8 a=UIkZVOpWgVUA:10 a=48vgC7mUAAAA:8 a=k7Ga1wGzAAAA:8]
X-AnalysisOut: [ a=qerv6Y54AAAA:8 a=yPCof4ZbAAAA:8 a=hGBaWAWWAAAA:8 a=I61F]
X-AnalysisOut: [lXWMwwx85pQ17rwA:9 a=CjuIK1q_8ugA:10 a=lZB815dzVvQA:10 a=f]
X-AnalysisOut: [cAx7uNQz4EA:10 a=7Zfzu0Ws3woA:10 a=7DSvI1NPTFQA:10 a=6_LLc]
X-AnalysisOut: [mUAZMlMHFjh:21 a=1s_B65MeIC64edA2:21]
Cc: "stir@ietf.org" <stir@ietf.org>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Subject: Re: [stir] current draft charter
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/stir>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jun 2013 18:03:49 -0000

How is this n the scope of this charter, Jon...can we focus

-----Original Message-----
From: stir-bounces@ietf.org [mailto:stir-bounces@ietf.org] On Behalf Of Peterson, Jon
Sent: Monday, June 17, 2013 2:00 PM
To: Dan York; Hadriel Kaplan
Cc: stir@ietf.org; dcrocker@bbiw.net
Subject: Re: [stir] current draft charter


I hear what you're saying, but I'd imagine there will always be a
difference in time-frame between "speeding up the web" and waiting for a
human to pick up a phone. Humans have to react to altering, get their
phone out of a pocket, etc. Nothing about how much faster we make the web
will reduce the distance (physical and psychological) between my pool and
my phone charger when a call comes in.

Now, what if we hope to make the phone never ring at all? The potential
laziness of callees is meaningful because only the caller perceives the
delay. Certainly we can play alerting back to the caller even if the
callee phone is trying to resolve authorization. In fact, in many blocking
circumstances, continuing to play alerting forever might be the right
thing to do if the callee is declining the caller.

Ultimately we are going to have to have some estimate of what the budget
is here and match it against what we hope to accomplish.

Jon Peterson
Neustar, Inc.

On 6/17/13 10:27 AM, "Dan York" <york@isoc.org> wrote:

>On 6/17/13 2:18 AM, "Hadriel Kaplan" <hadriel.kaplan@oracle.com> wrote:
>
>
>>On Jun 16, 2013, at 7:27 PM, "Peterson, Jon" <jon.peterson@neustar.biz>
>>wrote:
>>
>>> The exact amount of tolerable delay is a very interesting dimension of
>>> this problem space. I suspect we have a considerable amount of time,
>>>given
>>> all the human expectations about both post-dial delay and the wait for
>>> someone to pick up after altering. I think it's enough time to perform
>>> some non-trivial operations.
>>
>>I've been thinking about that and I'm not sure we actually have much
>>time. 
>
>+1.  As we as a society move more systems from the PSTN over to "IP
>communications" I suspect that we will see a growing expectation to have
>connections occur more quickly.  Other factors may enter in here, too, in
>feeding that expectation.  For instance, we may see WebRTC apps that
>quickly connect a calling user with another endpoint, and users may grow
>to expect that kind of quick connection.  Or there may be a new IP-based
>telco that attempts to differentiate itself by providing the fastest
>connection time.  Or there may be a major vendor that launches a campaign
>for IP communications like Google's "Speed Up The Web" that is aimed at
>providing quicker connections.
>
>I think you are right, Jon, based on *current* human expectations, but I
>could easily see those expectations changing and I think we need to be
>careful about tying a solution to current expectations. (Or at least if we
>do that needs to be a conscious choice.)
>
>>Anecdotally, I find that intra-nation calls get to ringing stage much
>>faster than international calls, so people are probably ok with
>>international caller-id verification taking longer.
>
>Agreed, based again on *current* expectations around user behavior.  On
>the other hand, when I make a call using Skype or Facetime I expect the
>call to connect quickly. With some other apps browser-based apps I expect
>to be able to pretty much push the button to initiate a call and start
>talking.
>
>I think we need to plan for the success of communication moving over to IP
>and reaping some of the benefits of IP, including no longer being shackled
>to legacy PSTN behavior.
>
>My 2 cents,
>Dan
>

_______________________________________________
stir mailing list
stir@ietf.org
https://www.ietf.org/mailman/listinfo/stir