Re: [stir] current draft charter

Hadriel Kaplan <hadriel.kaplan@oracle.com> Sat, 15 June 2013 18:57 UTC

Return-Path: <hadriel.kaplan@oracle.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 B7F7E21F9E05 for <stir@ietfa.amsl.com>; Sat, 15 Jun 2013 11:57:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.57
X-Spam-Level:
X-Spam-Status: No, score=-6.57 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
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 eleMYgwCWF6Q for <stir@ietfa.amsl.com>; Sat, 15 Jun 2013 11:57:03 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id 4B18E21F9DFE for <stir@ietf.org>; Sat, 15 Jun 2013 11:57:03 -0700 (PDT)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r5FIusoZ032395 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 15 Jun 2013 18:56:55 GMT
Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r5FIutIl010900 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 15 Jun 2013 18:56:55 GMT
Received: from abhmt101.oracle.com (abhmt101.oracle.com [141.146.116.53]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r5FIusrT022705; Sat, 15 Jun 2013 18:56:54 GMT
Received: from dhcp-amer-vpn-adc-anyconnect-10-154-189-250.vpn.oracle.com (/10.154.189.250) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sat, 15 Jun 2013 11:56:54 -0700
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <CDDE4B77.1F6F8%jon.peterson@neustar.biz>
Date: Sat, 15 Jun 2013 14:56:53 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A0BB9975-24DD-4673-B5D0-8B3C206FE231@oracle.com>
References: <CDDE4B77.1F6F8%jon.peterson@neustar.biz>
To: "Peterson, Jon" <jon.peterson@neustar.biz>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Cc: "stir@ietf.org" <stir@ietf.org>, Dave Crocker <dcrocker@bbiw.net>, Brian Rosen <br@brianrosen.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: Sat, 15 Jun 2013 18:57:08 -0000

On Jun 12, 2013, at 7:46 PM, "Peterson, Jon" <jon.peterson@neustar.biz> wrote:

> The proposed STIR charter outlines two ways to secure identity: an in-band
> and an out-of-band approach. Discussion so far on this list has focused
> largely on the in-band. For the out-of-band approach, we need to be able
> to explore credentials whose authority rests on some other means than
> delegation from on high: perhaps, like in ViPR, from probing how numbers
> are routed and using this to prove possession of the number.

If you mean check return routability, Dan Wing had a draft on a return-routability check:
http://tools.ietf.org/html/draft-wing-sip-e164-rrc-01

Unfortunately, legitimate caller-ids are sourced by elements/entities that are not necessarily the same ones used for reaching the same number back.  For example the call-center scenarios, or doctor cellphone scenario, or even Skype-out scenario.

With regard to ViPR, I was under the impression ViPR's entire foundation for trust authority rested on the PSTN, with the original PSTN call and its caller-ids being part of the shared secret for later use in ViPR peer discovery and authentication.  If the caller-id's in the PSTN can be faked, ViPR would have been in very big trouble, because it would have enabled incorrectly finding and authenticating a malicious peer for that spoofed number and making all future calls back to that malicious peer for the number.  No? (maybe ViPR changed after I stopped following it)

-hadriel