Re: [Modern] Review of draft-ietf-modern-problem-framework-00.txt

["Gorman, Pierce A [CTO]" <[e-mail]>]

I haven't read the most current version, but I think it's fair to say I've provided most of the public non-political feedback to MODERN so far.

The last comments I made advocated for the use of .name. domain name space (or a new name space) tied to telephone numbers with the concept of MODERN hosting Communications Reachability Information (CRI) and that index keys into a CRI database could be passwords which could also be telephone numbers.

The idea was cheerfully disregarded but I will bring it up again.  The MODERN "problem statement" is a solution architecture (not a problem statement), and it's inadequate, and centric to NANP telephony considerations.

If you want a globally usable telephone number routing information model for IP-based telecommunications and you want to more usefully solve problems like calling identity authentication (globally) and non-geographic number portability (for NANP), you should seriously be looking at multi-factor authentication for routing information queries.  Factors such as who do you think you're calling? And, what is the number [password] you think is associated with them?

You send a query to the CRI and you only know one factor (e.g., telephone number)?  That provides you an index into the least useful telecommunications information.  Perhaps only a telephone number into a SPAM-only voicemail box or voice-to-text-to-SPAM-text-box or whatever the user has defined that protects them from unauthorized and unauthenticated communications attempts.  Create a multi-factor communications model (which SIP and other communications protocols easily and commonly support) and you can have a meaninful impact on global robo-calling and robo-texting SPAM.

I have 3 main telephone numbers that are unique to me.  Very few people have all 3.  I compartmentalize my communications based on whether they are private, family, or business.  I could easily want or have more.  Many people do.  Very few people purposefully distribute all of their telephone numbers, e-mail addresses, social network personas, et cetera to all of their private, family, and work contacts.

If you want to give users globally, the world over, control over CRI, build a model that addresses their communications reachability needs, not their voice telephony needs.

Regards,

Pierce

From: Modern [mailto:[e-mail]] On Behalf Of Peterson, Jon
Sent: July 07, 2016 12:33 PM
To: Steve Donovan <[e-mail]>; [e-mail]
Subject: Re: [Modern] Review of draft-ietf-modern-problem-framework-00.txt


Thanks Steve, I cleaned these up.

Jon Peterson
Neustar, Inc.

From: Modern <[e-mail]<mailto:[e-mail]>> on behalf of Steve Donovan <[e-mail]<mailto:[e-mail]>>
Date: Friday, June 24, 2016 at 12:21 PM
To: "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
Subject: [Modern] Review of draft-ietf-modern-problem-framework-00.txt

I have reviewed draft-ietf-modern-problem-framework-00.txt.  This document is in great shape and I only have editorial comments as follows.

Regards,

Steve

-----

Section 1:

s /familiar from the /familiar to the/
s/ manenr/manner/
s/evolvling/evolving/

Section 2.1
s/assginees/assignees/
s/entitiy/entity/

Section 3
Need references for DRINKS and WEIRDS

Section 4.1.4
s/Aquiring/Acquiring/

Section 4.1.5
s/wtih/with/

Section 4.2.1.2
s/Regisrar/Registrar/

Section 4.1.2.3
s/could could/could/

Section 4.3.2
s/to access to this/to access this/


________________________________

This e-mail may contain Sprint proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.