Re: [stir] Robocall Strike Force

Paul Kyzivat <pkyzivat@alum.mit.edu> Sat, 20 August 2016 15:17 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 2EB3D12D86C for <stir@ietfa.amsl.com>; Sat, 20 Aug 2016 08:17:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level:
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no 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 PAz7k-soGPfe for <stir@ietfa.amsl.com>; Sat, 20 Aug 2016 08:17:57 -0700 (PDT)
Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B976F12D870 for <stir@ietf.org>; Sat, 20 Aug 2016 08:17:55 -0700 (PDT)
Received: from resomta-ch2-08v.sys.comcast.net ([69.252.207.104]) by resqmta-ch2-07v.sys.comcast.net with SMTP id b81TbW1FZff8qb81zbghCU; Sat, 20 Aug 2016 15:17:55 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by resomta-ch2-08v.sys.comcast.net with SMTP id b81yb7l51eKs6b81ybD02D; Sat, 20 Aug 2016 15:17:55 +0000
To: stir@ietf.org
References: <07e0eb16-6758-cdf1-c571-1f1ed768e741@dcrocker.net> <D9E1B04E-EE62-44AD-B98E-05A264FD044C@vigilsec.com> <2D7E9FF7-6121-4E0C-BBCA-FD730F252713@brianrosen.net> <9e8d2b2c-2735-d8db-0682-755ff294f9f8@dcrocker.net> <CAOPrzE0KKxVUBwczqP7xrJ6BJHnjHu0D+f=KpqkPnHLsQorXAA@mail.gmail.com> <4cd5cefb-59a1-f8d8-5bcd-e49cdbad2132@dcrocker.net> <437A953E-7F03-4FD8-B360-40C82D194DCB@att.com> <b8be3b84-4296-95a2-0058-3e5e2d633507@yaanatech.com> <a246b6eb-63f7-328b-80e6-4081460d3642@yaanatech.com> <E42CCDDA6722744CB241677169E836563F625B9A@MISOUT7MSGUSRDB.ITServices.sbc.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <d065897d-f748-c15d-cbcb-74881e99a01c@alum.mit.edu>
Date: Sat, 20 Aug 2016 11:17:52 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <E42CCDDA6722744CB241677169E836563F625B9A@MISOUT7MSGUSRDB.ITServices.sbc.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfJIXP6crlRaZGLEw+7bN6uERHV2hZ71GU3BNTAwZe9ipY0aHvyPnAI15S/SECBVtydNjUkjUSy8gZ1lT8gb/kNhDHGLSvrsT8H63X0W6MrizCHraHQQY oC/O4xjWFweJVe+RSqsLta8Jvk3k1eIwaMH5Tu4DpRbYvvAm1x9zSqlq/dJcrn2+85Zo8mYdPNhS2Q==
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/J0FrmlJ8y7AoO0E8iGu5niDwQm0>
Subject: Re: [stir] Robocall Strike Force
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 20 Aug 2016 15:17:59 -0000

Martin,

Are these documents (both the SHAKEN stuff and the Display Framework) 
publicly available?

I looked on the sip forum web site but didn't find them.

	Thanks,
	Paul

On 8/20/16 8:05 AM, DOLLY, MARTIN C wrote:
> Tony,
>
>
>
> For deployment in the USA, this ITU work would be totally useless.
>
>
>
> The ATIS – SIP Forum is has a profile of the IETF STIR RFC drafts in the
> SHAKEN Framework document.
>
> Further, SHAKEN telecom industry framework - Signature-based Handling of
> Asserted Information using Tokens
>
> 1.      Defines the architecture and NNI dependencies around the usage
> of the PASSporT and 4474bis based framework
>
> 2.      Defines the security model around management and usage of
> certificates used to sign and assert caller identity information
>
>
>
> In addition, there is a Display Framework document, that defines the
> requirements for signaling the verification information from the network
> to the user device and the requirements for what is displayed on the
> user device independent of technology.
>
>
>
> Service Requirements to support the above is being brought into the 3GPP
> SA1 meeting in San Francisco next week, 8/22-26 (Being led by Greg
> Schumacher, Sprint).
>
>
>
> I will be bring in a discussion paper and CRs into the October CT1
> meeting in China with the support of Nokia and Ericsson (and hopefully
> the other USA companies).
>
>
>
> WRT display  on the user device, there will be a combination of vendors
> getting requirements based on the ATIS-SIP Forum Display Framework given
> to them as part of ecosystem participation in the FCC Strike Force
> and/or direct requirements from carriers. In addition, further
> documentation to in GSMA, Cable Labs, etc… specifications may/will occur.
>
>
>
> Up to now, the coordination has been with the ATIS-SIP Forum
> co-chairs/leaders and moving forward with the FCC Strike Force
> Authentication Committee (co-chairs Chris Wendt and myself, so there the
> transition should be seamless)
>
>
>
> With the above work plan I do not see a role for the ITU on the Caller
> ID Spoofing.
>
>
>
> Regards,
>
>
>
> *Martin C. Dolly*
>
> Lead Member of Technical Staff
>
> Core & Government/Regulatory Standards
>
> AT&T
>
> Cell: +1.609.903.3360
>
> Email: _md3135@att.com <mailto:md3135@att.com>_
>
>
>
>
>
> *From:*Tony Rutkowski [mailto:tony@yaanatech.com]
> *Sent:* Friday, August 19, 2016 4:48 PM
> *To:* DOLLY, MARTIN C <md3135@att.com>
> *Cc:* IETF STIR Mail List <stir@ietf.org>; Paul Najarian
> <NajarianPB@state.gov>
> *Subject:* Re: [stir] Robocall Strike Force
>
>
>
> Hi Martin et al.,
>
> It is worth noting that for the
> upcoming SG17 meeting, China's
> MIIT, China Unicom, and China mobile
> have proposed a new work item that
> is substantially related to stir work.
> Indeed, the proposal contains a useful
> comprehensive overview of related
> SDO activities, including stir, and
> a gap analysis.
>
> I expect that the usdel to the meeting
> would appreciate any views from the
> Task Force and stir participants on
> the contribution.  In addition, how does
> stir and the IETF anticipate collaborating
> with SG17 and the other SDOs going forward?
> The NWI seems almost certain to get approved,
> and may well be before WTSA 2016.
>
> best,
> --tony
>
>
>
>
>
> _______________________________________________
> stir mailing list
> stir@ietf.org
> https://www.ietf.org/mailman/listinfo/stir
>