Re: [stir] Renaming E164Number

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>; Russ Housley <housley@vigilsec.com>; 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=G9v8uCSSQhCmpw7ItG0r2g&m=UhVA_2O-z5DN-Bdom_WhPcD_-4nWww1SYGSyTVjFPBA&s=DXAZMIa2681lT5v97AAp36rnY1CfZpJifa2PbpimkwQ&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=G9v8uCSSQhCmpw7ItG0r2g&m=UhVA_2O-z5DN-Bdom_WhPcD_-4nWww1SYGSyTVjFPBA&s=72Ta2iS7yNcl-FCR5HdvXB5njEfC12k0kLz7QgCp87g&e= 
>>> 
>>> What do people think?
>>> 
>>> spt
>>> _______________________________________________
>>> stir mailing list
>>> stir@ietf.org
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_stir&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=G9v8uCSSQhCmpw7ItG0r2g&m=UhVA_2O-z5DN-Bdom_WhPcD_-4nWww1SYGSyTVjFPBA&s=NSOnsQJ832JfPXkcoeqf68PvPzxIr21SPbpPP4dg270&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