Re: [stir] Stephen Farrell's Discuss on draft-ietf-stir-certificates-11: (with DISCUSS and COMMENT)

[Richard Shockey <[e-mail]>]

Fair point ..

We are working pretty hard to open up this process. These things take time negotiation lawyers etc.  

The SHAKEN Documents are here.  On a forward basis it’s the joint SIP Forum’s and ATIS plan to open up the process to as wide an audience as possible. More importantly the US telecom associations US Telecom and CTIA are opening up their process to all participants look at some of the other issues defined in the strike force report including the all-important track and trace issues.  We have to identify the networks that are injecting the malicious traffic into the network.  Looking at the existing CDR’s is just useless. 

If the IETF and the IESG can deliver this first phase of the protocols, then 3GPP and now DISPATCH can to their thing. The good news is STIR, at this stage will have wide adoption. It’s a fine set of tools. 

http://www.sipforum.org/content/view/439/312/

In case you hadn’t seen.

https://datatracker.ietf.org/doc/draft-schulzrinne-dispatch-callinfo-spam/

https://datatracker.ietf.org/doc/draft-schulzrinne-dispatch-status-unwanted

BTW IMHO these should be kept in DISPATCH and AD sponsored.  I will not support a new WG here. We have enough of those as it is. 

As you probably heard in Paris there is substantial interest in STIR/SHAKEN from multiple national jurisdictions and I will specifically be addressing some of those issues in the UK next week.

http://www.niccstandards.org.uk/meetings/forum-2016.cfm

In our defense the ATIS SIP Forum NNI TF has been looking at this for some time.  The strike force was under a very very short time line.   The strike force to the FCC enforced a non-disclosure agreement on this first phase of the work to outline what was possible and provide a roadmap to solutions.  You can argue one way or another on whether that was a good idea but in retrospect I could live with it and I was NOT a signatory to the NDA.  Lets try and keep a cooperative effort going.


— 
Richard Shockey

Shockey Consulting LLC

Chairman of the Board SIP Forum

www.shockey.us

www.sipforum.org

richard<at>shockey.us

Skype-Linkedin-Facebook rshockey101

PSTN [phone]

 

On 11/3/16, 4:34 PM, "Dave Crocker" <[e-mail]> wrote:

    On 11/3/2016 1:08 PM, Richard Shockey wrote:
    > The basics of SHAKEN was reported to the FCC by the Industry robocall strikeforce.
    >
    > https://www.fcc.gov/news-events/events/2016/10/second-meeting-industry-led-robocall-strike-force
    
    
    Basics.  Yes.  However...
    
    Small point:
    
          The Shaken activities are by a relatively small, closed group, 
    with results that are private, with no public access to the details and 
    no ability to contribute.  Were Shaken merely an effort to provide some 
    straightforward operational parameters, that might be fine.
    
          But getting STIR to be an functional service requires rather more 
    than just agreeing to some parameters.
    
          So the public IETF STIR work is inadequate for creating a useful 
    service, without the private, details specification work of Shaken.
    
    d/
    
    ps.  From a session at M3AAWG in Paris last week, I was promised that 
    the Shaken specs would be made public.  I look forward to that.
    
    -- 
    
       Dave Crocker
       Brandenburg InternetWorking
       bbiw.net