Profile

Contact Details

Dr. Chia-Chang Li

This individual is no longer active. Application functionality related to this individual is limited.

Contributions

1 to 5 of 20 total
Posted By Chia-Chang Li 06-04-2021 08:55:00 PM
Found In Egroup: ATIS/SIP Forum IP-NNI Task Force
\ view thread
Submitter's message This slide deck provides summary and outline of what have been proposed in IPNNI-2021-00075R000 -- Dr. Chia-Chang Li Document Name : IPNNI-2021-00074R000.pptx Description The slide deck is a companion presentation to the proposed revision to IPNNI-2018-00083R001. Download Latest Revision ...
Posted By Chia-Chang Li 06-04-2021 08:48:00 PM
Found In Egroup: ATIS/SIP Forum IP-NNI Task Force
\ view thread
Submitter's message This contribution is meant to revive and complete the work on STIR/SHAKEN metrics. This revision to the baseline document IPNNI-2018-00083R001 proposes a set of templates and guidelines for reporting and sharing STIR/SHAKEN metrics and implementation status. -- Dr. Chia-Chang Li Document ...
Posted By Chia-Chang Li 05-11-2021 08:43:00 PM
Found In Egroup: ATIS/SIP Forum IP-NNI Task Force
\ view thread
Submitter's message As FCC 6/30 mandate is approaching and STIR/SHAKEN is being deployed, let's get together to come up with common formats of reporting and operation information sharing. -- Dr. Chia-Chang Li Document Name : IPNNI-2021-00065R000.pptx Description Provide templates and guidelines for STIR/SHAKEN ...
Posted By Chia-Chang Li 03-27-2020 02:12:00 PM
Found In Egroup: ATIS/SIP Forum IP-NNI Task Force
\ view thread
Carriers have built the infrastructure to verify calls with tokens embedded in SIP Invite messages and should NOT be required to treat Invite differently. On the origination side, in a domain that OOB tokens can be more securely managed, the OSP can put the Invite back to the SIP domain. And these non-E2E-IP ...
Posted By Chia-Chang Li 03-27-2020 01:42:00 PM
Found In Egroup: ATIS/SIP Forum IP-NNI Task Force
\ view thread
We are closing in on sunsetting TDM/SS7 and should not try to build something similar back. Especially on termination or transit sides, we should not require the service providers to build a separate structure to handle tokens not embedded in the Invite messages. From: ipnni@xxxxxxxxxxxxxxx On Behalf ...