Re: [stir] Questions about stir-certificates

Keith Drage <drageke@ntlworld.com> Thu, 23 November 2017 12:30 UTC

Return-Path: <drageke@ntlworld.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 54DA8128B8E for <stir@ietfa.amsl.com>; Thu, 23 Nov 2017 04:30:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.801
X-Spam-Level:
X-Spam-Status: No, score=-4.801 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ntlworld.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 G_IfYFpe36y2 for <stir@ietfa.amsl.com>; Thu, 23 Nov 2017 04:30:03 -0800 (PST)
Received: from know-smtprelay-omc-5.server.virginmedia.net (know-smtprelay-omc-5.server.virginmedia.net [80.0.253.69]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38A29128B88 for <stir@ietf.org>; Thu, 23 Nov 2017 04:30:02 -0800 (PST)
Received: from [192.168.0.10] ([81.97.229.170]) by know-smtprelay-5-imp with bizsmtp id dQVz1w00X3hDt9d01QW0PD; Thu, 23 Nov 2017 12:30:00 +0000
X-Originating-IP: [81.97.229.170]
X-Authenticated-User: drageke@ntlworld.com
X-Spam: 0
X-Authority: v=2.1 cv=Ku2wojiN c=1 sm=1 tr=0 a=uMkRna9mZ6QJhuoPpEZIww==:117 a=uMkRna9mZ6QJhuoPpEZIww==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=IkcTkHD0fZMA:10 a=x7bEGLp0ZPQA:10 a=48vgC7mUAAAA:8 a=k7EyZI_217I3pyfJkUsA:9 a=EJLe9liNuB9rhEnI:21 a=blqg7Aj4Rs41R4r_:21 a=QEXdDO2ut3YA:10 a=w1C3t2QeGrPiZgrLijVG:22
To: stir@ietf.org
References: <D60E0087.1EEE44%jon.peterson@neustar.biz> <CABkgnnV41djmwJ2A8WkLv1Qu_zxAKPb8EJnuoFS1Zeog3momyQ@mail.gmail.com> <E4972898-9912-456F-92E5-1A6022B26A85@sn3rd.com> <CABkgnnUNmwT_-atKHzOATOJ4SPhsC1+Gy0Q_6XLtGo7owgE-kQ@mail.gmail.com> <37424273-bd3a-a2d8-856c-44ce58be720f@alum.mit.edu> <CABkgnnXG8q1YBUTHCn=cGWxkQ_MyEvpqo-t8FScC4G0Zv0Bx8A@mail.gmail.com> <037d68c1-a6aa-fe70-ed44-987855a8fb08@alum.mit.edu> <76349F66-3A94-4E15-8C6F-5CDF16B1F41C@sn3rd.com>
From: Keith Drage <drageke@ntlworld.com>
Message-ID: <86acde9d-a350-c9ee-10e1-31016cbed152@ntlworld.com>
Date: Thu, 23 Nov 2017 12:30:02 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <76349F66-3A94-4E15-8C6F-5CDF16B1F41C@sn3rd.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ntlworld.com; s=meg.feb2017; t=1511440200; bh=fWZX7A6b12GJKn3yUT0H8kLxrsLEYyIAqQrzljY6cms=; h=Subject:To:References:From:Date:In-Reply-To; b=E8OtXhfAeAHrRRvQkfkSIMZ5B8yve02Cdpk7BTUpeljDS1LKldwbXXitNoYdg8SU/ HLil+MlsH0lT2BpRUpkQsmJGB00HGA5QiBoPqxuVmmZJUT06Wl/2rra0GYx1IhLSqZ lPloK23xAuj9+G9g3AiUJ5oGjATSQBr4VSH2zyIu3ZcBsw0DcAbsmGX1NMAKVO3U25 elXrt0p9Wz/RaBMYF638Ln3S5JMfRvWfNPJOqo4JAW6rdbGvAKofzI8ACLawROD8Af v1K7zEbwSsC8VXFE1UsVVR6N3Pon1NgKVUV/0V2V2iTivt/Tg4ITDE+7zDjEp4FgsO mIhgQagY2ipug==
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/SPPDBjoO8ei-Z29kUH8E8wNMcx4>
Subject: Re: [stir] Questions about stir-certificates
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: Thu, 23 Nov 2017 12:30:06 -0000

I would note that I did identify this issue with open numbering plans 
(i.e. that the text seemed to be limited to fixed length numbering 
plans) at least 9 months ago and it was ignored, and I did not follow up 
on it. The issue will exist in both Germany and Austria.

I note Martin has used the number 15 below, which is the length given in 
the internet-draft, but I could not find anything in the draft defining 
which format of telephone number is used. The 15 is only correct if 
prefixes are not included. If prefixes are included, then that could add 
a further 1, 2 or possibly even 3 digits.

So can someone point me to text that identifies the preferred format of 
telephone number.

Keith


On 09-Nov-17 9:25 PM, Sean Turner wrote:
>> On Nov 1, 2017, at 00:40, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>
>> On 11/1/17 12:06 AM, Martin Thomson wrote:
>>> On Wed, Nov 1, 2017 at 1:44 AM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>>>> What is supposed to be done for variable length numbering schemes?
>>> I figure that you would simply have multiple ranges, one for each
>>> possible length.  That might mean 15 ranges in the worst case, but
>>> it's probably better than any alternative I can think of.
>> That sounds unpleasant.
>>
>> How about describing the range using a RE, or something similar to an RE restricted to digits?
>>
> Honestly, I am afraid that defining some kind of RE/regex is going to run into issues with the IESG.  I’ll synch with Jon and try to figure out what we can do here to make this easier on the implementer.
>
> spt
>
> _______________________________________________
> stir mailing list
> stir@ietf.org
> https://www.ietf.org/mailman/listinfo/stir