Re: [stir] New Version Notification for draft-burger-stir-iana-cert-00.txt

Eric Burger <eburger@standardstrack.com> Mon, 19 March 2018 23:02 UTC

Return-Path: <eburger@standardstrack.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 13F0012D7F4 for <stir@ietfa.amsl.com>; Mon, 19 Mar 2018 16:02:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.778
X-Spam-Level:
X-Spam-Status: No, score=-1.778 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, T_DKIM_INVALID=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=standardstrack.com
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 yo7l28rpMUsI for <stir@ietfa.amsl.com>; Mon, 19 Mar 2018 16:02:33 -0700 (PDT)
Received: from biz221.inmotionhosting.com (biz221.inmotionhosting.com [23.235.223.233]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AF6912AF84 for <stir@ietf.org>; Mon, 19 Mar 2018 16:02:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=standardstrack.com; s=default; h=Message-Id:In-Reply-To:To:References:Date: Subject:Mime-Version:Content-Type:From:Sender:Reply-To:Cc: Content-Transfer-Encoding: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=mTsOxHx3KHkO8y0wuQCv65ZYq1w9aAiJCP9cwVceVUA=; b=O0epnWDbvs40NEqd/wrF9CPZS 1tazSEUd+tdlmRMooRZJzcICnFXPFCHeUkL+LkQqvbouVmi7gJRvptkW+P2tp3YNVZTrwigRvqYlr cleIYGsTz4vNpnHlj5gm4O7oNyOyu9RaxxBKW+MzVei0eO6h/HNORWf3+88yqhG+lpCH8=;
Received: from [141.161.133.132] (port=46679 helo=[10.128.14.146]) by biz221.inmotionhosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from <eburger@standardstrack.com>) id 1ey3nF-000Hpr-4Z for stir@ietf.org; Mon, 19 Mar 2018 16:02:25 -0700
From: Eric Burger <eburger@standardstrack.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_FDFFB248-1768-4739-95D0-4D126154C4E4"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Mon, 19 Mar 2018 19:02:15 -0400
References: <152028300904.31710.8973954292655207142.idtracker@ietfa.amsl.com> <CA40963C-8447-43B3-9FEE-D1B1660F50E5@standardstrack.com> <BFBE04EA-17B9-4903-B2DB-25E577035033@ericsson.com>
To: stir@ietf.org
In-Reply-To: <BFBE04EA-17B9-4903-B2DB-25E577035033@ericsson.com>
Message-Id: <BFD4075A-2D30-4263-9F4E-E658C51B39E3@standardstrack.com>
X-Mailer: Apple Mail (2.3273)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz221.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Get-Message-Sender-Via: biz221.inmotionhosting.com: authenticated_id: eburger+standardstrack.com/only user confirmed/virtual account not confirmed
X-Authenticated-Sender: biz221.inmotionhosting.com: eburger@standardstrack.com
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/pZMzhibgM48JEY7Ugn087g8uN-w>
Subject: Re: [stir] New Version Notification for draft-burger-stir-iana-cert-00.txt
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 19 Mar 2018 23:02:35 -0000

This is covered in Section 5.1 and 5.2. It is the same model used for the time zone database. Registration will usually be obvious, like the FCC or NTIA registering for the U.S., OFCOM registering for the U.K., FICORA registering for Finland, etc. IANA can look up the national authorities via the ITU-T document normatively referenced in the text. If it is not obvious or cleared up by a phone call, e.g., asking the FCC if Neustar or iconectiv is OK for the U.S., that is why the document says to take it to the list.

One open question is that since this is something that would probably get zero traffic, I defaulted to saying “use the RAI list if there’s a dispute.” Do we need to setup a separate, “National Numbering Authorities Dispute List”? That would be easy enough if necessary.

> On Mar 6, 2018, at 1:15 AM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
> 
> Hi Eric,
> 
> The IANA policy is Expert Review. What exactly is the ER supposed to do in this case?
> 
> Regards,
> 
> Christer
> 
> Sent from my iPhone
> 
> On 6 Mar 2018, at 2.56, Eric Burger <eburger@standardstrack.com <mailto:eburger@standardstrack.com>> wrote:
> 
>> I could not stay away either.
>> 
>>> Begin forwarded message:
>>> 
>>> From: internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
>>> Subject: New Version Notification for draft-burger-stir-iana-cert-00.txt
>>> Date: March 5, 2018 at 3:50:09 PM EST
>>> To: "Eric W. Burger" <eburger@standardstrack.com <mailto:eburger@standardstrack.com>>, "Eric Burger" <eburger@standardstrack.com <mailto:eburger@standardstrack.com>>
>>> 
>>> 
>>> A new version of I-D, draft-burger-stir-iana-cert-00.txt
>>> has been successfully submitted by Eric W. Burger and posted to the
>>> IETF repository.
>>> 
>>> Name: draft-burger-stir-iana-cert
>>> Revision: 00
>>> Title: Registry for Country-Specific Secure Telephone Identity (STIR) Root Certificates
>>> Document date: 2018-03-05
>>> Group: Individual Submission
>>> Pages: 13
>>> URL:            https://www.ietf.org/internet-drafts/draft-burger-stir-iana-cert-00.txt <https://www.ietf.org/internet-drafts/draft-burger-stir-iana-cert-00.txt>
>>> Status:         https://datatracker.ietf.org/doc/draft-burger-stir-iana-cert/ <https://datatracker.ietf.org/doc/draft-burger-stir-iana-cert/>
>>> Htmlized:       https://tools.ietf.org/html/draft-burger-stir-iana-cert-00 <https://tools.ietf.org/html/draft-burger-stir-iana-cert-00>
>>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-burger-stir-iana-cert-00 <https://datatracker.ietf.org/doc/html/draft-burger-stir-iana-cert-00>
>>> 
>>> 
>>> Abstract:
>>>   This document defines an IANA registry that maps country codes to
>>>   secure telephone identity (STIR) root certificates authorized to
>>>   create signing certificates for telephone numbers under the authority
>>>   of a given country.  Some countries allow carriers to block
>>>   unsolicited, automatically generated nuisance calls commonly known as
>>>   'robocalls.'  The use of signed STIR tokens in the Session Initiation
>>>   Protocol (SIP) may be useful in such scenarios to provide positive
>>>   attestations as to call origin.  Legacy telephone numbering resources
>>>   are administrated by national policy.  Unlike the market-driven use
>>>   case of Web commerce, some nations may restrict the list of STIR root
>>>   certificate authorities acceptable for issuing signing certificates
>>>   for STIR tokens that provide attestations for their local legacy
>>>   telephone numbering resources.  The registry described in this
>>>   document enables call recipients in a first country to validate that
>>>   signaling it receives from a caller with a telephone number claiming
>>>   to be in a second country conforms to the second country's policy of
>>>   (1) having a limited list of STIR root certificate authorities (or
>>>   not) and (2) the certificate that produced the signature over the
>>>   signaling is signed by one of those authorized STIR root certificate
>>>   authorities.
>>> 
>>> 
>>> 
>>> 
>>> Please note that it may take a couple of minutes from the time of submission
>>> until the htmlized version and diff are available at tools.ietf.org <http://tools.ietf.org/>.
>>> 
>>> The IETF Secretariat
>>> 
>> 
>> _______________________________________________
>> stir mailing list
>> stir@ietf.org <mailto:stir@ietf.org>
>> https://www.ietf.org/mailman/listinfo/stir <https://www.ietf.org/mailman/listinfo/stir>