[stir] FW: for e.164 address, who do i blame?
Richard Shockey <richard@shockey.us> Wed, 29 April 2020 00:36 UTC
Return-Path: <richard@shockey.us>
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 4428C3A09F0 for <stir@ietfa.amsl.com>; Tue, 28 Apr 2020 17:36:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.119
X-Spam-Level:
X-Spam-Status: No, score=-1.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (768-bit key) header.d=shockey.us
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7sSS7wL6CbZQ for <stir@ietfa.amsl.com>; Tue, 28 Apr 2020 17:36:01 -0700 (PDT)
Received: from gateway30.websitewelcome.com (gateway30.websitewelcome.com [192.185.144.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CE823A07D6 for <stir@ietf.org>; Tue, 28 Apr 2020 17:35:48 -0700 (PDT)
Received: from cm14.websitewelcome.com (cm14.websitewelcome.com [100.42.49.7]) by gateway30.websitewelcome.com (Postfix) with ESMTP id E9E643CA7 for <stir@ietf.org>; Tue, 28 Apr 2020 19:35:47 -0500 (CDT)
Received: from box5527.bluehost.com ([162.241.218.19]) by cmsmtp with SMTP id TahXjgr40XVkQTahXjqYeQ; Tue, 28 Apr 2020 19:35:47 -0500
X-Authority-Reason: nr=8
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:In-Reply-To :References:Message-ID:To:From:Subject:Date:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=2tFRjO237Zeif1cbeDmaDK8UckZk5GOFLeOcXQRHi6s=; b=eHphv0EmsRHu+uwHiD/09nTgMq 8BPE1CBuwTnRDizPSM79597Ltx+sJ+FQzeZYldjKBiZ+GAAJrZjV46DQT1fVZv+CnyXSyizJol5P/ rFehULBJz3s+p2V5TatnwJC22;
Received: from pool-100-36-47-17.washdc.fios.verizon.net ([100.36.47.17]:59014 helo=[192.168.1.156]) by box5527.bluehost.com with esmtpa (Exim 4.92) (envelope-from <richard@shockey.us>) id 1jTahX-001AWB-MJ for stir@ietf.org; Tue, 28 Apr 2020 18:35:47 -0600
User-Agent: Microsoft-MacOutlook/16.36.20041300
Date: Tue, 28 Apr 2020 20:35:47 -0400
From: Richard Shockey <richard@shockey.us>
To: "stir@ietf.org" <stir@ietf.org>
Message-ID: <8CF5938A-8572-429B-84EF-73EEE19AEAF9@shockey.us>
Thread-Topic: [stir] for e.164 address, who do i blame?
References: <088d1b7b-b4fc-72e6-62be-40cc22273c1f@mtcc.com> <CC8EF9D2-FD6F-4C06-9D37-6A1487FA9F15@shockey.us>
In-Reply-To: <CC8EF9D2-FD6F-4C06-9D37-6A1487FA9F15@shockey.us>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box5527.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - shockey.us
X-BWhitelist: no
X-Source-IP: 100.36.47.17
X-Source-L: No
X-Exim-ID: 1jTahX-001AWB-MJ
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-36-47-17.washdc.fios.verizon.net ([192.168.1.156]) [100.36.47.17]:59014
X-Source-Auth: richard+shockey.us
X-Email-Count: 3
X-Source-Cap: c2hvY2tleXU7c2hvY2tleXU7Ym94NTUyNy5ibHVlaG9zdC5jb20=
X-Local-Domain: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/Zgi9BJIEl44GBHanqy6qKqupMpM>
Subject: [stir] FW: for e.164 address, who do i blame?
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 29 Apr 2020 00:36:12 -0000
Apologies this should have gone to the STIR list and not IETF Discuss. — Richard Shockey On 4/28/20, 8:34 PM, "Richard Shockey" <richard@shockey.us> wrote: On 4/28/20, 7:36 PM, "stir on behalf of Michael Thomas" <stir-bounces@ietf.org on behalf of mike@mtcc.com> wrote: Forgive me because I haven't manage to get through all of the docs yet, but while I'm pretty sure I know who to blame for sip:user@domain (= domain owner), is there an equivalent for the telephone numbers? RS> Yes the Government. ( They are here to help...just remember!) Phone numbers by international treaty are the exclusive domain of National Regulatory Authorities. In the US that is the FCC and the Wireline Competition Bureau advised by yours truly and others in the North American Numbering Council. The statutory authority is Section 251 (e) 1 of the US Code. In Canada it’s the CRTC, in the UK its OFCOM etc etc. Every nation state grants total absolute and plenary authority to phone numbers in much the same way. Phone numbers work which is why they are still so popular. That is, does the cert I download have contact information for who the number(s) are delegated to? I'm not asking for anything beyond that, just whether I can find that out reliably as, say, a human being. RS> The US STIR/SHAKEN Passport within the SIP INVITE will have a OCN an Operator Carrier Number [OCN] imbedded that will permit a trace back to the carrier of record for that number issued by the NANPA. These rules are in some flux right now. The S/S system in the US , for now, is highly carrier centric. You must have direct access to the US NANP to join the club. Enterprises are, even now, demanding to sign their own calls over their own SIP Trunks. How the UK or Australia etc are planning to do this is their business. Obviously there is a lot of trace back imbedded in the system due to the requirements of Law Enforcement for wiretapping imbedded in CALEA. https://www.neca.org/business-solutions/company-codes Stay tuned...film at 11. Mike _______________________________________________ stir mailing list stir@ietf.org https://www.ietf.org/mailman/listinfo/stir
- [stir] for e.164 address, who do i blame? Michael Thomas
- [stir] FW: for e.164 address, who do i blame? Richard Shockey