ESIF 22 Agenda



TITLE:ATIS SIP Forum IP-NNI TF Meeting Notes, June 1, 2020SOURCE:Anna Karditzas, Committee Coordinator, akarditzas@LEADER(S):IP-NNI TF Co-Chair: Martin Dolly, AT&T (md3135@)IP-NNI TF Co-Chair: Chris Wendt, Comcast (chris_wendt@)NOTICEOnly documents that are final/approved by an ATIS Committee represent the consensus of that Committee. Draft documents, on the other hand, are dynamic in nature and 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. ATIS/SIP Forum IP-NNI TFVirtual Meeting – June 1, 2020 | 9:30am-12pm ETMeeting NotesWELCOME & CALL TO ORDERMartin Dolly (AT&T), IP-NNI TF Co-Chair, called the meeting to order and welcomed participants at 1:05pm ET on June 1, 2020. INTRODUCTIONS & SIGN INMr. Dolly welcomed the attendees. The meeting participants are listed below: NameCompanyEmailMartin Dolly (IP-NNI TF Co-Chair)AT&Tmd3135@Chris Wendt (IP-NNI TF Co-Chair)Comcastchris_wendt@Sam EtlerAmazon Web Servicesetlers@Kirk BurroughsApplekburroughs@Andy JurczakAT&Tajurczak@Howard LangAT&Thl1539@Joe ScivicqueCenturyLinkJoseph.Scivicque@Philip LinseCenturyLinkphilip.linse@Robert DiandaCharter Communicationsrobert.dianda@Carol-lyn TaylorCISA ECDcarol-lyn.taylor@Arye EphrathCISA ECD Supportarye@Park YangCiscoparyang@David HancockComcastdavid_hancock@Chia-Chang LiComcastchia-chang_li@Clark WhittenCox Communicationsclark.whitten@Marian HearnCST GA (Canada)marian.hearn@cstga.caBen CampbellCTIAben@Harold SaltersCTIAhms5516@Arleen ElliottEricssonarleen.elliott@Hala MowafyEricssonhala.mowafy@Terry ReeseEricssontheresa.reese@Ken CarlbergFCCkenneth.carlberg@Tracey CashFirst Oriontcash@Julie Sara FowlerFirst Orionjfowler@Michael PowersGBSD Technologiesmike.powers@Jeffrey RossGBSD Technologiesjeffrey.ross@David KayHiyadkay@Gary Richenakericonectivgrichenaker@Ray Woodiconectivrwood@Andrew GallantInCharge Systemsabgallant@Mike HamiltonInCharge Systemsmikehamilton@Doug BellowsInteliquentdoug.bellows@Timothy MoranLeidosmorantl@Peter BrownMetaswitchpeter.brown@Russ PenarMicrosoftrussp@Doug LawsNECAdlaws@P.J. LouisNECApjlouis@Douglas RanalliNetNumberdranalli@Mick MossNeustarMick.Moss@team.neustarKen Politz Neustarkpolitz@cis.Shreyas SaitawdekarNeustarshreyas.saitawdekar@team.neustarJason TorreyNeustarjason.torrey@team.neustarMohammad KhaledNokiamohammad.khaled@Chris CurrieNumber Accesschris.currie@Anis JafferNumeracleanis@Rebekah JohnsonNumeraclerebekah@Tom MorescoPerspecta Labstmoresco@Ray Singh Perspecta Labsrsingh@John WullertPerspecta Labsjwullert@James HamlinPurple & ZVRSjames.hamlin@purple.usMary BarnesRealtime Communications, LLCMLB@Tolga AsverenRibbon Communicationstasveren@Jamie GibsonRibbon Communicationsjgibson@Graham LeGeyt (guest)Shaw Communicationsgraham.legeyt@sjrb.caRichard ShockeySIP Forumrichard@shockey.usJusten DavisSomosjdavis@Mary RetkaSomosmretka@Dinko DinkovT-MobileDinko.Dinkov@t-Shaunna ForsheeT-Mobileshaunna.l.foreshee@t-Pierce GormanT-Mobilepierce.gorman@t-David HolmesT-Mobiledavid.holmes@t-Karen RiepenkrogerT-Mobilekaren.s.riepenkroger@t-Greg SchumacherT-Mobilegregory.schumacher@t-Don BeelerTDR Technologydon.beeler@Bill LaRuffaTEOCObill.laruffa@Jose Mario Miranda MartinezTNSmmiranda@Jim DaltonTransNexusjim.dalton@Alec FenichelTransNexusalec.fenichel@Mark DesterdickVerizondesterdick@Anna KarditzasATISakarditzas@Steve BarclayATISsbarclay@Ian DeakinATISideakin@Jim McEachernATISjmceachern@Brent StruthersATISbstruthers@Jackie WohlgemuthATISjwohlgemuth@REVIEW & APPROVAL OF AGENDAThe agenda was made available to participants via ATIS Workspace (AWS) as IPNNI-2020-00103R004. The agenda was approved as posted. ATIS OP, IPR, ANTITRUST AND CONTRIBUTIONS NOTICESATIS Procedures: ATIS Forum and Committee activities must adhere to the ATIS Operating Procedures (OP) for ATIS Forums and Committees.Intellectual Property Rights (IPR): In connection with the development of an ATIS deliverable that requires use of patented inventions, the ANSI Patent Policy as adopted by ATIS and as set forth in Section 10.4 of the OP shall apply. Under this policy:Disclosure of relevant patented inventions at the earliest possible time is encouraged. Neither the Forum or 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. The discussion of licensing terms is prohibited in ATIS Forums and Committees.Patent disclosure and assurance statements consistent with the ATIS OP must be submitted in writing to the ATIS General Counsel.Antitrust: Attendees are reminded that participation in industry fora involves the potential for antitrust concerns or risks. To avoid such concerns/risks, participants should carefully observe the OP. Sensitive discussion topics such as price, costs, specific contractual terms, etc., should be avoided. Contributions: In order for ATIS to facilitate, promote, and disseminate its work, each contributor must grant ATIS the rights necessary to adapt, copy, and publicly distribute any contribution or submittal. Each contribution or document therefore is subject to unlimited perpetual, non-exclusive, royalty-free, world-wide rights, and license to ATIS of any copyrights in such a contribution. As a general rule, ATIS will not consider any contribution, presentation, or other input that is subject to any requirement of confidentiality or any restriction on its dissemination. Questions: If there are any questions, comments, or concerns, participants should contact 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 NOTESIPNNI-2020-00101R000, Meeting notes from the April 28-29, 2020, IP-NNI TF virtual meeting IPNNI-2020-00102R000, Meeting notes from the May 18, 2020, IP-NNI TF virtual meeting It was noted that there were no questions or comments regarding these meeting notes and they were accepted, without objection, as published.REVIEW OF ACTION ITEMS FROM PREVIOUS MEETINGSAction Item: Martin Dolly (AT&T), Terry Reese (Ericsson), Chris Wendt (Comcast), Robert Dianda (Charter), Greg Schumacher (T-Mobile), and Jim McEachern (ATIS) will work on a proposal on STIR/SHAKEN for emergency networks to bring to IP-NNI.This Action Item remains open. Action Item: Mary Barnes (Realtime Communications) will bring in a contribution on status codes/HTTP codes. This Action Item remains open. IP-NNI TOPIC DISCUSSIONATIS-1000074.v002, Signature-based Handling of Asserted information toKENs (SHAKEN)IPNNI-2020-00008R009, Signature-based Handing of Asserted information using toKENs (SHAKEN) (Baseline)This is the approved baseline, which was accepted at the IP-NNI TF meeting on May 18, 2020. Verification Token Use Cases IPNNI-2017-00020R000, Verification Token Use Cases BaselineThere were no contributions submitted for this Issue. ATIS-1000080.v003, SHAKEN Governance Model and Certificate ManagementIPNNI-2020-00015R006, ATIS-1000080.v003, SHAKEN Governance Model and Certificate Management (Baseline)This is the approved baseline, which was accepted at the IP-NNI meeting on April 28-29, 2020. IPNNI-2020-00093R002, Proposed updates to ATIS-1000080.v003This contribution was not discussed, due to time constraints. ATIS-1000084.v002, Technical Report on Operational and Management Considerations for SHAKEN STI Certification Authorities and Policy AdministratorsIPNNI-2020-00017R001, ATIS-1000084.v002This is the accepted baseline. Robo-MetricsIPNNI-2018-00083R001, Robo-Metrics BaselineThis is the accepted baseline. SHAKEN Roadmap IPNNI-2020-00084R003, SHAKEN Roadmap [clean]This is the approved baseline, which was accepted at the IP-NNI TF meeting on May 18, 2020. SHAKEN Delegate Certificates IPNNI-2020-00022R005, SHAKEN Delegate Certificates (Baseline)This is the accepted baseline. IPNNI-2020-00022R006, SHAKEN Delegate Certificates (revmarked)This contribution was not discussed, due to time constraints. IPNNI-2020-00022R007, SHAKEN Delegate Certificates (clean)This contribution was not discussed, due to time constraints. IPNNI-2020-00098R000, Proposed editorial updates to SHAKEN Delegate CertificatesThis contribution was not discussed, due to time constraints. IPNNI-2020-00098R001, Proposed editorial updates to SHAKEN Delegate CertificatesThis contribution was not discussed, due to time constraints. SHAKEN Calling Name and Rich Call Data Handling Procedures IPNNI-2020-00025R004, SHAKEN Calling Name and Rich Call Data Handling Procedures (revmarked)This is the revmarked baseline that incorporates the changes proposed in IPNNI-2020-00080R002 as agreed upon during the April 28-29, 2020, virtual meeting. This contribution was not discussed. IPNNI-2020-00025R005, SHAKEN Calling Name and Rich Call Data Handling Procedures (clean)This contribution was not discussed. IPNNI-2020-00095R001, Proposed updates to SHAKEN Calling Name and Rich Call Data Handling ProceduresDavid Hancock (Comcast) presented this contribution, which adds descriptions of “rcd” authentication procedures for non-SHAKEN entities and OSPs. Section 5.2.3 also describes procedures when an INVITE containing an “rcd” PASSporT is retargeted. Sections 5.2.1.1 and 5.2.1.2 were added to address RCD authentication by a non-SHAKEN VoIP entity and an OSP, respectively. It was noted that the presence of base SHAKEN is mandated, and “rcd” is optional based on the relationship between interconnected peers. If RCD is going to come from multiple sources, one of which is unknown and untrusted, that will degrade the situation. The entity doing the signing is more important than the fact that it is signed. Participants agreed that the priority is to achieve maximum flexibility and minimum burden. Action Item: David Hancock (Comcast) will enumerate scenarios for OSP and TSP in the baseline for SHAKEN Calling Name and Rich Call Data Handling Procedures. Agreement Reached: This contribution was accepted as modified in IPNNI-2020-00095R002 for incorporation into the baseline. Best Current Practices on the protection of STIR/SHAKEN data between service providers and from service providers to enterprisesIPNNI-2019-00055R000, Best Current Practices on the protection of STIR/SHAKEN data between service providers and from service providers to enterprises (Baseline)This is the accepted baseline. Methods to Determine SHAKEN Attestation Levels Using Enterprise-Level Credentials and Telephone Number Letter of Authorization ExchangeIPNNI-2020-00035R000, Methods to Determine SHAKEN Attestation Levels Using Enterprise-Level Credentials and Telephone Number Letter of Authorization Exchange (Baseline)This is the accepted baseline. IPNNI-2020-00097R000, Proposed updates to draft EV Certificates/TNLoA baseline This contribution was not discussed, due to time constraints.Signature-based Handling of SIP RPH Assertion Verification Token Use Cases IPNNI-2020-00021R002, Updated Baseline Text for Draft ATIS Standard on SIP RPH Signing using PASSporT Tokens (revmarked)This contribution was not discussed, due to time constraints.IPNNI-2020-00021R003, Updated Baseline Text for Draft ATIS Standard on SIP RPH Signing using PASSporT Tokens (clean)This contribution was not discussed, due to time constraints.SIP RPH Signing in Support of Emergency CallingIPNNI-2020-00010R004, Session Initiation Protocol (SIP) Resource-Priority Header (RPH) Signing in Support of Emergency Calling (revmarked)This contribution was not discussed.IPNNI-2020-00010R005, Session Initiation Protocol (SIP) Resource-Priority Header (RPH) Signing in Support of Emergency Calling (clean)Terry Reese (Ericsson) presented this contribution, which is the clean version of the baseline. Agreement Reached: This contribution was accepted as the new baseline. IPNNI-2020-00089R000, Proposed updates to SIP RPH Signing in Support of Emergency CallingTerry Reese (Ericsson) presented this contribution, which proposes updates as a result of discussion from the IP-NNI TF meeting on April 28-29, 2020. This contribution proposes a number of changes. First, signing requests will be sent in an HTTP message: one signingRequest associated with caller identity, and one associated with RPH. Second, verification of a signed RPH will result in a separate verstat value being returned in a verificationResponse. Third, the assertion value populated in an ‘rph’ claim sent by an IBCF to the STI-AS to request signing of the RPH will, based on local policy, either be conveyed to the IBCF by the P-CSCF in a P-header, or will be derived by the IBCF based on other information. Agreement Reached: This contribution was accepted for incorporation into the baseline. There is more work required for this document before it will be ready for letter ballot. The small group needs to meet and achieve resolution for verstat details, as well as non-dialable callback numbers. A question was raised regarding how any solution generated on verstat will affect 3GPP processes; it was determined that the IP-NNI TF will make a decision and relay that decision to 3GPP. Action Item: Martin Dolly (AT&T) will coordinate with Jurgen Axell (Ericsson) to solidify work on SIP RPH signing in support of emergency calling. Central TN Database Approach to Full Attestation for Enterprises with Multi-Homing and/or Multi-TenancyIPNNI-2020-00023R000, Central TN Database Approach to Full Attestation for Enterprises with Multi-Homing and/or Multi-TenancyThis is the accepted baseline. Leveraging Model for Originating eNtity authentication – full aTtestation With an entity Identity in a Secure Token (LEMON-TWIST)IPNNI-2020-00026R002, LEveraging Model for Originating eNtity Authentication – full aTtestation With an entity Identity in a Secure Token (LEMON TWIST)This contribution is the approved baseline, accepted during the IP-NNI meeting on April 28-29, 2020.SHAKEN: Out-of-Band Token TransmissionIPNNI-2020-00058R005, Signature-based Handling of Asserted information using toKENs (SHAKEN): Out-of-Band Token Transmission (baseline)This is the clean approved baseline, which was accepted at the IP-NNI TF meeting on May 18, 2020. IPNNI-2020-00096R000, Proposed changes and additions to the OOB SHAKEN baselineThis contribution is superseded by the proposed changes in IPNNI-2020-00105R000. IPNNI-2020-00104R000, Contribution to SHAKEN OOB Token Transmission baselineThis contribution was not discussed, due to time constraints. IPNNI-2020-00105R000, Proposed changes/additions to OOB SHAKEN baselineRobert Dianda (Charter) presented this contribution, which includes suggested edits to the scope as well as the section on CPS Discovery. Due to time constraints, discussion of this document will resume during the IP-NNI TF meeting on June 2, 2020. Extending STIR/SHAKEN over TDM InterconnectsIPNNI-2020-00074R000, Extending STIR/SHAKEN over TDM InterconnectsThis contribution is the approved baseline, accepted during the IP-NNI meeting on April 28-29, 2020.IPNNI-2020-00074R001, Extending STIR/SHAKEN over TDM Interconnects [revmarked]This contribution was not discussed. IPNNI-2020-00074R003, Extending STIR/SHAKEN over TDM Interconnects [clean]This contribution was not discussed. IPNNI-2020-00074R004, Extending STIR/SHAKEN over TDM Interconnects [revmarked]Tolga Asveren (Ericsson) presented this revised contribution. There is a new section on Example Mappings with ISUP screening indicators. It was noted that there is already a PTSC standard addressing mapping into ISUP SHAKEN (ATIS-1000073). No more codes can be added to the ISUP protocol, and regardless, that work would have to be done in PTSC against strong opposition. Additionally, the use of the screening indicator in TDM is inconsistent between switches that are ISDN-based and switches that are not. The issue is that ISDN switches will process screening indicators differently than other switches. A clarification was made that this contribution does not intend to add anything to ISUP. It was noted that a network provided screening indicator should map to an A-level attestation, rather than a B attestation. It was noted that work on OOB SHAKEN related to IP interconnects will stay in the IP-NNI TF, while other documents on OOB SHAKEN will be remanded to the new PTSC Non-IP Call Authentication Task Force. This contribution was noted. IPNNI-2020-00074R005, Extending STIR/SHAKEN over TDM Interconnects [clean]Tolga Asveren (Ericsson) presented this contribution, which is the clean version of IPNNI-2020-00074R004. Agreement Reached: This contribution was accepted as the clean baseline.Agreement Reached: This baseline will be remanded to the Non-IP Call Authentication Task Force. Technical Report on Alternatives for Caller Authentication for Non-IP TrafficIPNNI-2020-00088R000, Technical Report on Alternatives for Caller Authentication for Non-IP Traffic [baseline]This contribution is the clean baseline, which was accepted during the IP-NNI TF meeting on April 28-29, 2020. Other Contributions IPNNI-2020-00092R000, Technical Report on Toll-Free Calls in the SHAKEN FrameworkThis contribution is superseded by IPNNI-2020-00092R001, and was not discussed. IPNNI-2020-00092R001, Technical Report on Toll-Free Calls in the SHAKEN FrameworkJusten Davis (Somos) presented this proposed Technical Report baseline, which addresses toll-free calls in the SHAKEN framework. It was noted that proof of possession of a TN is provided in the Multi-Homing baseline in PTSC-LB-248, and will be added to this document. It was noted that an 800 number can be used for call origination. A question was raised on how to encourage all-IP interconnection so as not to drop STIR/SHAKEN parameters when crossing a boundary. This document is intended to go hand-in-glove with the delegate certificate baseline (IPNNI-2020-00022R005), and the material in this document was initially present in that baseline before being pulled into a separate contribution. This contribution presumes that delegate certificates exist and that there is a way to do delegate certificates. It was noted that that assumption needs to be added to the principles/initial assumptions in the beginning of the document. Participants also discussed timing mismatch versus a timing functionality problem. Agreement Reached: This contribution was accepted as a new baseline, with the understanding that a future contribution will be submitted to reflect discussion from today’s meeting. REVIEW OF ISSUE STATUS/TARGET RESOLUTION DATESIPNNI-2020-00030R006, IP-NNI Document TrackerThis contribution was noted for information. IPNNI-2020-00003R001, SHAKEN Progress TrackerThis contribution was not discussed. FUTURE WORK/ASSIGNMENTS/MEETINGSThe following virtual meetings were noted:Tuesday, June 2, 9:30am-12pm ETThe following F2F meetings were noted:Q3: Week of August 10 – Denver, CO (preferred)/ Philadelphia, PA / Seattle, WA Q4: Reston, VA [TNS] Subsequent to this meeting, the IP-NNI TF agreed to meet virtually for Q3, during the week of August 10, 2020. ANY OTHER BUSINESSThere was no other business to discuss. ADJOURNMENTMr. Wendt thanked participants for attending and adjourned the meeting at 4:02PM ET on June 1, 2020. ___________________________________________________________Notes submitted by:Anna Karditzas, ATIS Committee Coordinator ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download