Re: [Enum] 5 years since last message

[Richard Shockey <[e-mail]>]

Well its still a big deal to the US Government. Its central to the FCC's system for providing telecommunications services for the hearing impaired.  The iTRS database still run by NeuStar BTW.  It's also used in modern SIP/IMS  internal IP Interconnection schemes at multiple carriers in place of old TDM SCP's  .  The FCC North American Numbering Council ( on which I sit)  is thinking about revisiting the issue to enhance and deploy Video Calling <sigh>. 

https://www.fcc.gov/document/itrs-numbering-report-and-order

https://www.fcc.gov/fcc-acts-improve-video-relay-service-and-direct-video-calling

We took a stab at revisiting Public ENUM in the US about 5 years ago to no consensus. 

https://www.sipforum.org/2015/07/atis-and-sip-forum-complete-new-ip-based-network-to-network-interface-nni-technical-specification/

It still pops up from time to time. Recently in relation to all IP Interconnection driven by STIR/SHAKEN mandates in the US to combat robocalls and caller ID spoofing.   I had a nightmare one night a couple of months ago that someone wanted me to restart the ENUM WG to enable 6116 over HTTPS.   Now if you think that would be a nightmare ..well the British are actively considering Distributed Ledger Technology aka Hyperledger to accomplish the ENUM like functions.

https://www.ofcom.org.uk/about-ofcom/latest/features-and-news/blockchain-technology-uk-telephone-numbers


— 
Richard Shockey

Shockey Consulting LLC

Chairman of the Board SIP Forum

www.shockey.us

www.sipforum.org

richard<at>shockey.us

Skype-Linkedin-Facebook –Twitter  rshockey101

PSTN [phone]

 

On 7/2/19, 1:43 AM, "enum on behalf of Patrik Fältström" <[e-mail] on behalf of paf=[e-mail]> wrote:

    Well, the standard is in use -- sort of -- with various modifications locally (like use of a different prefix than what is assigned here in IETF). I heard last time last week people "just saying" this is what is and should be used for routing of communication with E.164 numbers as destination in time of emergency/stress where centralized IN systems can not be reached (but locally cached DNS can).
    
    So the list is silent, but there is some kind of usage. Does this "some kind of usage" imply something should be done?
    
    I do not know.
    
    I personally did conclude after the first couple of years of discussions that NAPTR is incredibly stupid. Designing things to have so large RRSets is not very optimal, so other DNS types would be better. I suggested the simple URI. But it itself got stuck in the IETF process of creation of new RRTypes, and when it finally was approved, the interest in deployment was sort of gone :-(
    
    And people seems to have implemented NAPTR...
    
       Patrik
    
    On 2 Jul 2019, at 2:41, Livingood, Jason wrote:
    
    > So what needs to happen here? Seems indisputable that there's not much happening on the ENUM front...
    >
    > On 6/27/19, 9:48 AM, "enum on behalf of Olivier Guillard / AFNIC" <[e-mail] on behalf of [e-mail]> wrote:
    >
    >     pong :-)
    >
    >     le Tuesday 15 January à 13 H 17 , Jaap Akkerhuis a écrit :
    >     >  Bernie Hoeneisen writes:
    >     >
    >     >  > Hi Jaap
    >     >  >
    >     >  > Well, there is a dependency on this list in RFC 6117...
    >     >  >
    >     >  > On the other hand, registering new ENUM services has not been that popular
    >     >  > either for several years...
    >     >  >
    >     >  > cheers
    >     >  >   Bernie (Designated Expert of the IESG and other list maintainer)
    >     >
    >     > In that case, it would make sense that you take over the maintaining
    >     > of this list as well. Would you? If so, let's arrange that off-list.
    >     >
    >     > 	jaap
    >     >
    >     > _______________________________________________
    >     > enum mailing list
    >     > [e-mail]
    >     > https://www.ietf.org/mailman/listinfo/enum
    >
    >     --
    >     Olivier
    >
    >     _______________________________________________
    >     enum mailing list
    >     [e-mail]
    >     https://www.ietf.org/mailman/listinfo/enum
    >
    >
    > _______________________________________________
    > enum mailing list
    > [e-mail]
    > https://www.ietf.org/mailman/listinfo/enum
    _______________________________________________
    enum mailing list
    [e-mail]
    https://www.ietf.org/mailman/listinfo/enum