Re: [stir] Renaming E164Number

Russ Housley <housley@vigilsec.com> Fri, 14 April 2017 17:30 UTC

Return-Path: <housley@vigilsec.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 8B78C127977 for <stir@ietfa.amsl.com>; Fri, 14 Apr 2017 10:30:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 WRrTuOmR5joe for <stir@ietfa.amsl.com>; Fri, 14 Apr 2017 10:30:55 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D68821292AE for <stir@ietf.org>; Fri, 14 Apr 2017 10:30:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 4F59030043A for <stir@ietf.org>; Fri, 14 Apr 2017 13:30:54 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Dy6M5lyUeYF2 for <stir@ietf.org>; Fri, 14 Apr 2017 13:30:52 -0400 (EDT)
Received: from a860b60074bd.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 91FBD300229 for <stir@ietf.org>; Fri, 14 Apr 2017 13:30:52 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Fri, 14 Apr 2017 13:30:51 -0400
References: <A803E7B6-2848-4640-AABE-87BBFEA9ACE2@sn3rd.com> <E42CCDDA6722744CB241677169E836564AD03061@MISOUT7MSGUSRDB.ITServices.sbc.com> <1043CA0F-0D2E-4130-A4B8-8AC060D34E6B@vigilsec.com> <301EC44E-15CB-47F2-88C4-1ED91FE023E6@chriswendt.net> <8CCC018C-3BB8-48AB-9365-5C52F22174CF@neustar.biz> <00C069FD01E0324C9FFCADF539701DB3BD10819B@sc9-ex2k10mb1.corp.yaanatech.com> <D5166B9A.1D8946%jon.peterson@neustar.biz>
To: IETF STIR Mail List <stir@ietf.org>
In-Reply-To: <D5166B9A.1D8946%jon.peterson@neustar.biz>
Message-Id: <0185FA28-9D87-4833-8875-E0D343C4EF1F@vigilsec.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/_fAtorYj-RbxVR5YKf4vtOxgjLY>
Subject: Re: [stir] Renaming E164Number
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: Fri, 14 Apr 2017 17:30:58 -0000

Suggestion…

OLD w/ the addition of SIZE to TelephoneNumberRange:

     TNAuthorizationList ::= SEQUENCE SIZE (1..MAX) OF TNEntry

     TNEntry ::= CHOICE {
       spc   [0] ServiceProviderCodeList,
       range [1] TelephoneNumberRange,
       one       E164Number }

     ServiceProviderCodeList ::= SEQUENCE SIZE (1..3) OF IA5String

     TelephoneNumberRange ::= SEQUENCE SIZE (2..MAX) {
       start E164Number,
       count INTEGER  }

     E164Number ::= IA5String (SIZE (1..15)) (FROM ("0123456789#*”))

NEW:

     TNAuthorizationList ::= SEQUENCE SIZE (1..MAX) OF TNEntry

     TNEntry ::= CHOICE {
       spc   [0] ServiceProviderCodeList,
       range [1] TelephoneNumberRange,
       one       TelephoneNumber }

     ServiceProviderCodeList ::= SEQUENCE SIZE (1..3) OF IA5String

     TelephoneNumberRange ::= SEQUENCE SIZE (2..MAX) {
       start TelephoneNumber,
       count INTEGER  }

     TelephoneNumber ::= IA5String (SIZE (1..15)) (FROM ("0123456789#*”))

If this is acceptable, then I ask the authors to make the changes and post an updated I-D.

Russ


> On Apr 14, 2017, at 12:14 PM, Peterson, Jon <jon.peterson@neustar.biz> wrote:
> 
> 
> No mutual understanding of the semantics is required by the authentication
> and verification services here - though in practice, calls that are routed
> to destinations via a dial string with a * or # in it should end up going
> to fairly specialized pieces of equipment, and I'm actually less worried
> about canonicalization and so on being an issue for special dial strings
> like this than I am for ordinary E.164 numbers. We're not placing any
> restrictions on where in the dial string those non-numeric characters
> might appear, as there doesn't seem to be anything gained by doing so
> except introducing complexity.
> 
> In terms of what to call it, if we can't agree on Freddie, I do think TN
> or something similarly generic is appropriate. If we already have a group
> field for TelphoneNumberRange, why wouldn't the base element be
> TelephoneNumber? Or if we'd be overloading some existing registered name
> by using that, like TelNum or something?
> 
> Jon Peterson
> Neustar, Inc.
> 
> On 4/14/17, 10:56 AM, "Michael Hammer" <michael.hammer@yaanatech.com>
> wrote:
> 
>> Jon,
>> 
>> Can the * and # be used arbitrarily anywhere in the string?
>> 
>> Is there some semantic to those characters that needs
>> to be understood by both the sender and receiver?
>> 
>> Or does it not matter because the recipient only treats it as an opaque
>> string?
>> 
>> ________________________________
>> Michael Hammer
>> michael.hammer@yaanatech.com
>> +1 408 202 9291
>> 
>> © 2016 Yaana Technologies, LLC. All Rights Reserved. Email
>> confidentiality notice. This message is private and confidential. If you
>> have received this message in error, please notify us and remove it from
>> your system.
>> 
>> -----Original Message-----
>> From: stir [mailto:stir-bounces@ietf.org] On Behalf Of Peterson, Jon
>> Sent: Thursday, April 13, 2017 11:19 AM
>> To: Chris Wendt <chris-ietf@chriswendt.net>
>> Cc: IETF STIR Mail List <stir@ietf.org>rg>; Russ Housley
>> <housley@vigilsec.com>om>; Martin C Dolly <md3135@att.com>
>> Subject: Re: [stir] Renaming E164Number
>> 
>> Agreed. We are allowing these non-numeric characters in certs to support
>> a corner case that might arise in the future. Let's not agonize over what
>> to call the field.
>> 
>> Jon Peterson
>> Neustar, Inc.
>> 
>>> On Apr 13, 2017, at 11:11 AM, Chris Wendt <chris-ietf@chriswendt.net>
>>> wrote:
>>> 
>>> Can we just call it telephoneNumber?  I think we are mostly arguing
>>> name here, right?
>>> 
>>>> On Apr 13, 2017, at 9:47 AM, Russ Housley <housley@vigilsec.com> wrote:
>>>> 
>>>> Martin:
>>>> 
>>>> E.164 only allows digits.  What should we call a number that include
>>>> digits and * and #?
>>>> 
>>>> Russ
>>>> 
>>>> 
>>>>> On Apr 12, 2017, at 7:13 PM, DOLLY, MARTIN C <md3135@att.com> wrote:
>>>>> 
>>>>> Sean,
>>>>> 
>>>>> DTMF has no end to end meaning for routing, but is meaningful between
>>>>> the UE and the SP processing those symbols.
>>>>> 
>>>>> Therefore, I do not see this as an issue.
>>>>> 
>>>>> Regards,
>>>>> 
>>>>> Martin
>>>>> 
>>>>> -----Original Message-----
>>>>> From: stir [mailto:stir-bounces@ietf.org] On Behalf Of Sean Turner
>>>>> Sent: Wednesday, April 12, 2017 7:04 PM
>>>>> To: stir@ietf.org
>>>>> Subject: [stir] Renaming E164Number
>>>>> 
>>>>> In another thread I remember seeing a suggestion to rename E164Number
>>>>> to DTMFNumber.  I created an issue:
>>>>> 
>>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_stirwg_
>>>>> certificates_issues_4&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=G9v8uCSSQhCmp
>>>>> w7ItG0r2g&m=UhVA_2O-z5DN-Bdom_WhPcD_-4nWww1SYGSyTVjFPBA&s=DXAZMIa2681lT
>>>>> 5v97AAp36rnY1CfZpJifa2PbpimkwQ&e=
>>>>> and here's the PR showing the resulting change:
>>>>> 
>>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_stirwg_
>>>>> certificates_pull_5&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=G9v8uCSSQhCmpw7
>>>>> ItG0r2g&m=UhVA_2O-z5DN-Bdom_WhPcD_-4nWww1SYGSyTVjFPBA&s=72Ta2iS7yNcl-FC
>>>>> R5HdvXB5njEfC12k0kLz7QgCp87g&e=
>>>>> 
>>>>> What do people think?
>>>>> 
>>>>> spt
>>>>> _______________________________________________
>>>>> stir mailing list
>>>>> stir@ietf.org
>>>>> 
>>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailm
>>>>> an_listinfo_stir&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=G9v8uCSSQhCmpw7ItG
>>>>> 0r2g&m=UhVA_2O-z5DN-Bdom_WhPcD_-4nWww1SYGSyTVjFPBA&s=NSOnsQJ832JfPXkcoe
>>>>> qf68PvPzxIr21SPbpPP4dg270&e=
>>>>> _______________________________________________
>>>>> stir mailing list
>>>>> stir@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/stir
>>>> 
>>>> _______________________________________________
>>>> stir mailing list
>>>> stir@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/stir
>>> 
>>> _______________________________________________
>>> stir mailing list
>>> stir@ietf.org
>>> https://www.ietf.org/mailman/listinfo/stir
>> 
>> _______________________________________________
>> stir mailing list
>> stir@ietf.org
>> https://www.ietf.org/mailman/listinfo/stir
> 
> _______________________________________________
> stir mailing list
> stir@ietf.org
> https://www.ietf.org/mailman/listinfo/stir