DOCUMENT TYPE

TITLE: ATIS/SIP Forum IP-NNI Task Force Meeting Notes, June 6, 2016, Virtual Meeting

SOURCE*: ATIS Coordinator

LEADER(S): Co-Chair: Martin Dolly, AT&T,

Co-Chair: Chris Wendt, Comcast,

Co-Chair: John Barnhill, Genband,

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

ATIS/SIP Forum IP-NNI Task Force Meeting
Meeting Notes
Virtual Meeting – June 6, 2016

  1. WELCOME & CALL TO ORDER

Martin Dolly (AT&T), ATIS/SIP Forum IP-NNI Task Force Co-Chair, called the meeting to order and welcomed participants at 11:10a.m.

  1. INTRODUCTIONS & SIGN IN

The meeting participants are listed below:

Name / Company / Email
  1. Martin Dolly (PTSC Chair)
/ AT&T /
  1. Viqar Shaikh (PTSC Vice Chair)
/ ACS /
  1. Ray Singh
/ ACS /
  1. John Wullert
/ ACS /
  1. Philip Linse
/ CenturyLink /
  1. Mary Retka
/ CenturyLink /
  1. Steve Showell
/ CenturyLink /
  1. Chris Wendt
/ Comcast /
  1. Clark Whitten
/ Cox /
  1. Scott Williams
/ Department of Justice, OTD /
  1. Eric Burger
/ Georgetown University /
  1. Arleen Elliott
/ Ericsson /
  1. George Foti
/ Ericsson /
  1. Hala Mowafy
/ Ericsson /
  1. Terry Reese
/ Ericsson /
  1. John Curreri
/ iconectiv /
  1. Gary Richenaker
/ iconectiv /
  1. Mike Usry
/ iconectiv /
  1. Andrew Gallant
/ InCharge /
  1. Doug Bellows
/ Inteliquent /
  1. Ken Politz
/ Neustar /
  1. Jim Calme
/ Nokia /
  1. Gregory Bain
/ OEC /
  1. Carol-Lyn Taylor
/ OEC /
  1. Arye Ephrath
/ OEC Technical Support /
  1. Victor Pascual
/ Oracle /
  1. Richard Shockey
/ Shockey Consulting /
  1. Leigh Swindle
/ SouthernLINC Wireless /
  1. David Holmes
/ Sprint /
  1. Mark Desterdick
/ Verizon /
  1. Amy Hindman
/ Verizon Wireless /
  1. Steve Barclay
/ ATIS /
  1. Drew Greco
/ ATIS /
  1. Jim McEachern
/ ATIS /
  1. Jackie Voss
/ ATIS /
  1. REVIEW & APPROVAL OF AGENDA

It was noted that the agenda was made available to participants via the ATIS Workspace as IPNNI-2016-00026R000. The agenda was modified and approved as -00026R001.

  1. 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.

  1. APPROVAL OF PREVIOUS MEETING NOTES

It was noted that the meeting notes from the May 18-19, 2016, meeting from AMOC are not yet available for review. Approval of these meeting notes was deferred to the next meeting.

  1. IP-NNI PHASE 2

VoIP Transition SecurityWhitepaper

This agenda item was not discussed.

Update on the point-to-point video calling

This agenda item was not discussed.

  1. ANTI-SPOOFING CALLER MITIGATION TECHNIQUES

Chris Wendt (Comcast) provided a summary of the April IETF meeting in Buenos Aires, Argentina.The following points were noted:

IPNNI-2016-00028R001, Assumptions underlying the use of STIR/SHAKEN

Jim McEachern (ATIS) presented this contribution, which attempts to capture assumptions underlying the use of STIR/SHAKEN to provide a level of assurance for information pertaining to the calling party in a SIP session. It then proposes the levels of assurance that can be provided based on if/how a SIP call is signed using SHAKEN.
Mr. McEachern suggested including this contribution as an informative annex to the baseline document.
It was suggested to note that STIR/SHAKEN does not assist with traceback.

Action Item: Mr. McEachern to revise and resubmit this contribution as -00028R002 to clarify that STIR/SHAKEN does not assist with traceback if the call is not signed, but traceback may still be achieved through other means.
Action Item: Chris Wendt (Comcast) to update the baseline document to include -00028R002, as an informative appendix, for the next meeting.
Action Item: Mr. Dolly to update the Call Validation Display baseline document for the next meeting.

IPNNI-2016-00023R001, Caller ID Spoofing Potential Timeline & Dependencies

Mr. McEachern presented this contribution, which proposes a timeline for Caller ID anti-spoofing, identifying standards work and dependencies
It was noted that NGIIF is not required to wait for the Task Force to complete their work on Caller ID Spoofing, but will continue their work separately and keep the Task Force updated on their progress.
It was suggested to extend the timeline for the Display Framework Requirements to end 2Q17. There were no objections.

It was noted that the initial implementations of the STIR code to begin testing in labs is almost complete.

Action Item: Mr. McEachern to revise and resubmit this contribution as -00023R002 to update the timeline for review during the next meeting.

  1. MODERN

There was no MODERN update for this meeting.

  1. FUTURE WORK/ASSIGNMENTS/MEETINGS

The following interim meetingswere noted:

9.1Virtual

  • July 11, 2016, 10:00 am – 2:00 pm
  • Face-to-face
  • August 24-25, 2016 (Denver, CO)
  • Wednesday, August 24 1:00 pm – 5:00 pm
  • Thursday, August 25 9:00 am – 12:00 pm
  • October 26-27, 2016 (Miami, FL)
  1. ANY OTHER BUSINESS

Mr. Shockey proposed the following questions on Call Validation Display for discussion during a future meeting in an effort to develop a contribution:

  • What are the options for how call validation display can be delivered to a user agent by using the existing call header?
  • What would the data elements be?
  • How are multiple call info headers treated in the existing frameworks or is there code within the existing structure that enables only one call info header to exist?
  • Should a data object be a group of parameters or a URI by reference? If a URI by reference, why, and would XML be used?
  1. ADJOURNMENT

Mr. Dolly thanked participants for attending and adjourned the meeting at 12:08p.m.ET.

Notes submitted by:

Drew Greco, ATIS Coordinator

1