DOCUMENT TYPE
TITLE: ATIS/SIP Forum IP-NNI Task Force Meeting Notes, November 7, 2017, McLean, VA
SOURCE*: ATIS Coordinator
LEADER(S): Co-Chair: Martin Dolly, AT&T,
Co-Chair: Chris Wendt, Comcast,
NOTICE
Only documents that are final/approved by an ATIS Committee represent the consensus of that Committee. Draft documents, on the other hand, are dynamic in natureand subject to change. Draft documents therefore may not accurately reflect the consensus of the ATIS Committee.
Neither ATIS nor the Committee makes any representation or warranty, express or implied, with respect to the sufficiency, accuracy or utility of the information or opinion contained or reflected in the material utilized. ATIS further expressly advises that any use of or reliance upon the material in question is at your risk and neither ATIS nor the Committee shall be liable for any damage or injury, of whatever nature, incurred by any person arising out of any utilization of the material. It is possible that this material will at some future date be included in a copyrighted work by ATIS.
* CONTACT: Drew Greco; email: Tel: 516-796-6087
PTSC & ATIS/SIP Forum IP-NNI Task Force Meeting
Meeting Notes
McLean, VA – November 7, 2017
- WELCOME & CALL TO ORDER
Chris Wendt (Comcast), ATIS/SIP Forum IP-NNI Task Force Co-Chair, called the meeting to order and welcomed participants at 9:00a.m.ETon November 7, 2017.
- INTRODUCTIONS & SIGN IN
The meeting participants are listed below:
Name / Company / Email- Martin Dolly* (TF Co-Chair)
- Chris Wendt (TF Co-Chair)
- Andy Jurczak
- Penn Pfautz*
- Frank Shaffer
- Philip Linse*
- Steve Showell*
- Jason Torrey
- Robert Dianda*
- Harsha Bellur*
- David Hancock
- Harold Salters
- Arleen Elliott*
- Hala Mowafy*
- Terry Reese*
- Jonathan Nelson
- Mary Barnes
- Chris Drake
- Gary Richenaker
- Andrew Gallant*
- Mike Hamilton*
- Doug Bellows*
- Roxanne Ruminski
- Timothy Moran*
- David Quan
- Russ Penar
- Syed Ali
- Ken Politz
- Mohammad Khaled
- Robert Wozniak*
- Arye Ephrath
- An Nguyen
- Carol-Lyn Taylor*
- Steve Pastorkovich
- Richard Shockey
- Harold Hauser
- Catherine Palcic
- Mary Retka
- Pierce Gorman*
- Andrew Mangold
- Joe Dechant (guest)
- Ray Singh
- John Wullert*
- Mark Desterdick*
- Amy Hindman*
- Steve Barclay
- Drew Greco
- Jim McEachern
- Jackie Wohlgemuth*
*Virtual participation
- REVIEW & APPROVAL OF AGENDA
It was noted that the agenda was made available to participants via ATIS Workspace as IPNNI-2017-00109R001. The agenda was modified and approved as -00109R002.
- ATIS INTELLECTUAL PROPERTY RIGHTS (IPR) & ANTITRUST POLICIES
ATIS Procedure Notice: ATIS Forum and Committee activities must adhere to the ATIS Operating Procedures (including basic principles such as fairness, due process, respect for minority opinions, and common sense).
IPR Notice: In connection with the development of an American National Standard, or other deliverable that requires use of patented inventions, the use of patented inventions shall be governed by the ANSI Patent Policy as adopted by ATIS and as set forth in Section 10 of the "Operating Procedures for ATIS Forums and Committees." Under this policy:
- Disclosure of relevant patented inventions at the earliest possible time in the development process is encouraged. An opportunity will be provided for the members to identify or disclose patents that any member believes may be essential for the use of a standard under development.
- Neither the Committee, nor its leaders, can ensure the accuracy or completeness of any disclosure, investigate the validity or existence of a patent,or determine whether a patent is essential to the use of an ATIS deliverable.
- ATIS prohibits any discussion of licensing terms in its Forums and Committees.
Antitrust Risk Notice: The leaders further remind attendees that participation in industry fora involves the potential for antitrust concerns or risks. To avoid such concerns and risks, participants should carefully observe the "Operating Procedures for ATIS Forums and Committees". In addition, sensitive discussion topics such as price, territories, specific contractual terms, etc., should be avoided.
Questions: Participants having questions, comments, or concerns regarding any of these topics should consult with their company's legal counsel, the Committee leadership, ATIS staff, or ATIS legal counsel.
It was asked if there were any patents to identify or disclose at this time. There were no patent disclosures made by the attendees.
- APPROVAL OF PREVIOUS MEETING NOTES
The following previous meeting notes were available on the ATIS Workspace (AWS) for participant comment:
- IPNNI-2017-00099R000, Notes from the ATIS-SIP Forum IP-NNI Task Force meeting August 2, 2017, in Denver, CO
- IPNNI-2017-00107R000, Notes from the September 14, 2017, joint PTSC/ATIS-SIP Forum IP-NNI Task Force virtual meeting
It was noted that there were no questions or comments regarding these meeting notes and they were accepted, without objection, as published.
- IP-NNI PHASE 2
- VoIP Transition SecurityWhitepaper
- IPNNI-2016-00006R000, Baseline
It was noted that there were no input contributions toward this work at this time.
- ANTI-SPOOFING CALLER MITIGATION TECHNIQUES
- Verified Token Use Cases
- IPNNI-2017-00020R000, Verification Token Use Cases Clean Baseline
This contribution was noted as the current Verification Token Use Cases baseline document.
7.2Display Framework
7.2.1IPNNI-2017-00019R005, Display Framework Baseline (marked)
This contribution was approved as the current baseline documentwith changes from the September 14, 2017, virtual meeting.
7.2.2IPNNI-2017-00019R006, Display Framework Baseline (clean)
This contribution was approved as the clean existing baseline document to this meeting to which contributions will be made.
7.2.3IPNNI-2017-00106R000, FTC email on call authentication display option
This contribution was noted for information.
7.2.4IPNNI-2017-00110R000, Contribution on Display Guidelines
Jonathan Nelson (Hiya) presented this contribution, which provides study descriptions, results, and conclusions on the testing of warning phrasing and iconography.
This contribution was noted for information.
7.2.5IPNNI-2017-00111R000, Usability Test Results
Mr. Nelson presented this contribution, which provides the study descriptions, results, and conclusions on the testing of warning phrasing and iconography from contribution IPNNI-2017-00110R000 and adds them to the display guidelines.
Agreement Reached: Participants accepted this contribution as input to the baseline document.
7.2.6IPNNI-2017-00112R000, Text-Based Traditional Caller-ID Display Framework
Mr. Wendt presented this contribution, which includes aproposal for consideration of a text-based traditional Caller-IDdisplay framework.
The following items were noted:
- The use of a “+” character could be in conflict with international dialing.
- The industry could benefit if the iconography could incorporate characters such as the stop sign with the exclamation point and the triangle with the questions mark.
This contribution was noted for information.
7.3Certificate Management
7.3.1IPNNI-2017-00051R005, Managing list of CAs and other operational considerations for Certificate management (marked)
This contribution was noted as the current certificate management baseline documentwith changes from the August 2, 2017, meeting in Denver, CO.
7.3.2IPNNI-2017-00051R006, Managing list of CAs and other operational considerations for Certificate management (clean)
This contribution was approved as the clean existing baseline document to this meeting to which contributions will be made.
7.3.3IPNNI-2017-00116R000, SHAKEN certificate deployment notes
David Hancock (Comcast) presented this contribution, which provides notes on deploying STIR/SHAKEN CertificateManagement.
The following suggestions were offered:
- Retain both unique links and caching ability.
- Make this mandatory on the terminating network.
- Create a separate best practices document with its own scope rather than including this information in an appendix to the existing baseline.
Action Item: Mr. Hancock and Mr. Wendt to create a skeleton baseline best practices document for contributions.
This contribution was noted for information.
7.3.4IPNNI-2017-00119R000, Proposed revisions to baseline CM/PA operational document
Mary Barnes (iconectiv) presented this contribution, which proposes revisions to the certificate management baseline document.
Editor’s notes and additional editorial revisions were added to the document.
Agreement Reached: Participants accepted the modified contribution in 00119R001 as input to the baseline document.
7.4SHAKEN API for a Centralized Signing and Signature Validation Server
7.4.1IPNNI-2017-00021R007, Technical Report on SHAKEN API for a Centralized Signing and Signature Validation Server (marked)
This contribution was approved as the current baseline documentwith changes from the September 14, 2017, virtual meeting.
7.4.2IPNNI-2017-00021R008, Proposed Technical Report on SHAKEN API for a Centralized Signing and Signature Validation Server (clean)
This contribution was approved as the clean existing baseline document to this meeting to which contributions will be made.
7.4.3IPNNI-2017-00108R000, Proposed Changes to Technical Report on SHAKEN API for a Centralized Signing and Signature Validation Server
Ken Politz (Neustar) presented this contribution, which proposes changes to the Technical Report on SHAKEN API for a Centralized Signing and Signature Validation Server.
The following points were noted:
- HTTP error codes can be used for application specific logic.
- The HTTP specification states that if a response is sent, it will always be as a 200 OK message.
- A concern was noted with extensibility.
- To whom do we extend the APIs?
- Are there separate APIs for different verifications or one verification?
- If an RPH verification or another verification wants to use the same language, then we would want separate specific responses.
- It was suggested to add a top level object that provides extensibility.
- It was suggested to accept the contribution as SHAKEN only, but work on a revision that supports extensibility, RPH and the vendor responsibility to implement both.
- A concern was noted that there are already field tests being performed and if the code is changed, those tests would need to repeat the current cycles.
Agreement Reached: The editorial revisions in this contribution were accepted as input to the baseline document. The normative revisions were not accepted. Neustar will discuss offline if they wish to revise and resubmit their contribution to try to build toward consensus.
7.4.4IPNNI-2017-00120R000, Proposed Changes to Technical Report on SHAKEN API for a Centralized Signing and Signature Validation Server
Ms. Barnes presented this contribution, which proposes changes to the Technical Report on SHAKEN API for a Centralized Signing and Signature Validation Server.
Editor’s notes and additional editorial revisions were added to the document.
Agreement Reached: Participants accepted the modified contribution in -00120R001 as input to the baseline document.
7.5SHAKEN Attestation and Origination Identifier
7.5.1IPNNI-2017-00030R000, ATIS Technical Report on a Framework for SHAKEN Attestation and Origination Identifier
This contribution was noted as the current SHAKEN Attestation and Origination Identifier baseline document.
7.6Signature-based Handling of SIP RPH Assertion using Tokens
7.6.1IPNNI-2017-00025R003, Baseline text for the draft ATIS Standard on Signature-based Handling of SIP RPH Assertion using Tokens (marked)
This contribution was approved as the current baseline documentwith changes from the May 22, 2017, virtual meeting.
7.6.2IPNNI-2017-00025R004, Baseline text for the draft ATIS Standard on Signature-based Handling of SIP RPH Assertion using Tokens (clean)
This contribution was approved as the clean existing baseline document to this meeting to which contributions will be made.
7.6.3IPNNI-2017-00088R000, Proposed Changes to Draft ATIS Standard on SIP RPH Signing using PASSPorT Tokens
Ray Singh presented this contribution, which proposes changes to the draft ATIS standard on SIP RPH Signing using PASSPorT Tokens to align with IETF draft-ietf-stir-rph-00.
It was noted that the “origid” parameter should be included in this contribution.
Editor’s notes and additional editorial revisions were added to the document.
Agreement Reached: Participants accepted the modified contribution in -00088R001 as input to the baseline document.
7.6.4IPNNI-2017-00113R000, Status Update of draft-ietf-stir-rph-01
Mr. Singh presented an update of draft-ietf-stir-rph-01.
This contribution was noted for information.
7.6.5IPNNI-2017-00114R000, Solution for NS/EP Service Provider Credential for SIP RPH Signing
Mr. Singh presented an overview of NS/EP Service Provider Credential for SIP RPH Signing.
This contribution was noted for information.
7.6.6IPNNI-2017-00115R000, Copy of draft-ietf-stir-rph-01 for information
This contribution was noted for information.
7.7Proof-of-Possession of Telephone Numbers (TN-PoP)
7.7.1IPNNI-2017-00087R000, SHAKEN Framework for Proof of Possession of Telephone Numbers
This contribution was noted during a previous meeting. It has been superseded by IPNNI-2017-00118R000, Document for SHAKEN TN-POP, Proof-of-Possession of Telephone Numbers.
7.7.2IPNNI-2017-00117R001, Discussion of Toll Free/8YY Use Cases for TN-POP
Mr. Hancock presented this contribution, which discusses Toll Free/8YY Use Cases for TN-POP.
It was suggested to consider use cases where the telephone number provider is a RespOrg. It was noted that enterprise can be their own RespOrg and arrange for their own 800 numbers. For inbound calling, enterprise can decide on service providers.
This contribution was noted for information.
7.7.3IPNNI-2017-00118R000, Document for SHAKEN TN-POP, Proof-of-Possession of Telephone Numbers
Mr. Hancock presented this contribution, which proposes a skeleton baseline document for SHAKEN TN-POP, Proof-of-Possession of Telephone Numbers.
It was suggested to add a Proof-of-Possession use case to the Verification Token Use Cases Clean Baseline.
Agreement Reached: Participants accepted this contribution as the initial baseline document for SHAKEN TN-POP, Proof-of-Possession of Telephone Numbers
7.8Other Contributions
7.8.1IPNNI-2017-00091R000, SHAKEN - Certificate Framework – Administration using ACME/OAuth
This contribution was noted for information.
Summary of Contribution Status
IPNNI-2016-00006R000 / Current baseline
IPNNI-2017-00020R000 / Current baseline
IPNNI-2017-00019R005 / Accepted
IPNNI-2017-00019R006 / Current baseline
IPNNI-2017-00106R000 / Noted
IPNNI-2017-00110R000 / Noted
IPNNI-2017-00111R000 / Accepted
IPNNI-2017-00112R000 / Noted
IPNNI-2017-00116R000 / Noted
IPNNI-2017-00051R005 / Accepted
IPNNI-2017-00051R006 / Current baseline
IPNNI-2017-00119R000 / Revised to -R001, accepted
IPNNI-2017-00021R007 / Accepted
IPNNI-2017-00021R008 / Current baseline
IPNNI-2017-00108R000 / Editorial revisions accepted; Normative revisions not accepted
IPNNI-2017-00120R000 / Revised to -R001, accepted
IPNNI-2017-00030R000 / Current baseline
IPNNI-2017-00025R003 / Accepted
IPNNI-2017-00025R004 / Current baseline
IPNNI-2017-00088R000 / Revised to -R001, accepted
IPNNI-2017-00113R000 / Noted
IPNNI-2017-00114R000 / Noted
IPNNI-2017-00115R000 / Noted
IPNNI-2017-00087R000 / Noted; superseded by -00118
IPNNI-2017-00117R001 / Noted
IPNNI-2017-00118R000 / Current baseline
IPNNI-2017-00091R000 / Noted
IPNNI-2017-00012R004 / Noted
- FUTURE WORK/ASSIGNMENTS/MEETINGS
The following upcoming meetings were noted:
8.1Virtual Meetings
- December 8, 2017, 1pm-4pm ET (joint PTSC/IP-NNI TF)
8.2Face-to-Face Meetings
- February 6-8, 2018 (Austin, TX)
- April 30 – May 3, 2018 (Kansas City, MO; AMOC)
- August 7 – 9, 2018 (Denver, CO)
- October 30 – November 1, 2018 (TBD)
- ANY OTHER BUSINESS
- IP-NNI Document Tracker
- IPNNI-2017-00012R004, IP-NNI Document Tracker
This contribution was noted for information.
- ADJOURNMENT
Mr. Wendt thanked participants for attending and adjourned the meeting at 5:00p.m.ETon November 7, 2017.
Notes submitted by:
Drew Greco, ATIS Coordinator
1