Re: [stir] Robocall Strike Force

"DOLLY, MARTIN C" <md3135@att.com> Sat, 20 August 2016 12:05 UTC

Return-Path: <md3135@att.com>
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 4FAE512B05B for <stir@ietfa.amsl.com>; Sat, 20 Aug 2016 05:05:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.59
X-Spam-Level:
X-Spam-Status: No, score=-2.59 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham 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 JkVoQpjLdeE4 for <stir@ietfa.amsl.com>; Sat, 20 Aug 2016 05:05:31 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 C7170127077 for <stir@ietf.org>; Sat, 20 Aug 2016 05:05:31 -0700 (PDT)
Received: from pps.filterd (m0049459.ppops.net [127.0.0.1]) by m0049459.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id u7KC5MPP029700; Sat, 20 Aug 2016 08:05:30 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049459.ppops.net-00191d01. with ESMTP id 24xpg4thc7-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 20 Aug 2016 08:05:30 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u7KC5QXE001758; Sat, 20 Aug 2016 08:05:27 -0400
Received: from mlpi407.sfdc.sbc.com (mlpi407.sfdc.sbc.com [130.9.128.239]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u7KC5Ha1001586 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 20 Aug 2016 08:05:22 -0400
Received: from MISOUT7MSGHUBAF.ITServices.sbc.com (MISOUT7MSGHUBAF.itservices.sbc.com [130.9.129.150]) by mlpi407.sfdc.sbc.com (RSA Interceptor); Sat, 20 Aug 2016 12:05:07 GMT
Received: from MISOUT7MSGUSRDB.ITServices.sbc.com ([169.254.2.119]) by MISOUT7MSGHUBAF.ITServices.sbc.com ([130.9.129.150]) with mapi id 14.03.0301.000; Sat, 20 Aug 2016 08:05:07 -0400
From: "DOLLY, MARTIN C" <md3135@att.com>
To: "tony@yaanatech.com" <tony@yaanatech.com>
Thread-Topic: [stir] Robocall Strike Force
Thread-Index: AQHR+lf0Ed/hh9UbOUG3iSxY8YLToqBRBFIAgAC1LRA=
Date: Sat, 20 Aug 2016 12:05:06 +0000
Message-ID: <E42CCDDA6722744CB241677169E836563F625B9A@MISOUT7MSGUSRDB.ITServices.sbc.com>
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>
In-Reply-To: <a246b6eb-63f7-328b-80e6-4081460d3642@yaanatech.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.70.216.163]
Content-Type: multipart/alternative; boundary="_000_E42CCDDA6722744CB241677169E836563F625B9AMISOUT7MSGUSRDB_"
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-08-20_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 impostorscore=0 lowpriorityscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1608200174
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/iApDWd-8pwHmeWaBnDAzHnlM-Bk>
Cc: IETF STIR Mail List <stir@ietf.org>, Paul Najarian <NajarianPB@state.gov>, "Calme, Jim (EXT - US)" <jim.calme.ext@nokia.com>
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 12:05:34 -0000

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