{"ct_name":"Sharman Sibia","ct_title":"Director Enterprise Security Risk Management","ct_dept":"Information Security","ct_address":"660 N Capitol Street NW Suite 240 | Washington, DC DC 20001 | 79e868f3dba03600d02ffb0e0f961973","ct_tel":"7043142618","ct_email":"robocalling@brightspeed.com","bz_address":"1120 S Tryon Street | Suite 700 | Charlotte North Carolina 28203","country":"United States of America","declare":"2024-02-20","last_seen":"2024-04-28","sys_id":"4eba610b1b623050e91484cae54bcb85","is_new":0,"gw_prov":"false","gw_prov_choice":"No","combined_gw":"false","ipr_imported":"false","voice_choice":"Yes","intermed_choice":"Yes","investigated":"No","intermed_exempt_rule":"The Federal Communications Commission (FCC) implemented requirements, pursuant to Section 47 C.F.R. ?64.6304(d) of the Rules, on a suite of industry standards subsequently adopted, creating an Internet Protocol (IP) call authorization framework. The Secure Telephone Identity Revisited (STIR) and Signature-based Handling of Asserted information using toKENs (SHAKEN referenced as STIR\/SHAKEN), does not function on portions of a carrier's network that rely on technology that cannot initiate, maintain, and terminate SIP calls (\"non-IP calls\"). The deadline for implementing STIR\/SHAKEN of June 30, 2021, is subject to a continuing extension of the FCC's requirements, provided that a carrier:\no is participating, either on its own or through a representative, including third party\nrepresentatives, as a member of a working group, industry standard group, or consortium\nthat is working to develop a non-internet Protocol caller identification authentication\nsolution, or actively testing such a solution; and\no commits to continuing support for establishing an effective solution.\nBrightspeed meets each of these conditions. The company is a member of the ATIS PTSC Non-IP\nCall Authentication Taskforce and has committed to continue to work with the industry toward\nan effective solution to redress robocalling over the non-IP network.","gw_exempt_rule":"","voice_exempt_rule":"The Federal Communications Commission (FCC) implemented requirements, pursuant to Section 47 C.F.R. ?64.6304(d) of the Rules, on a suite of industry standards subsequently adopted, creating an Internet Protocol (IP) call authorization framework. The Secure Telephone Identity Revisited (STIR) and Signature-based Handling of Asserted information using toKENs (SHAKEN referenced as STIR\/SHAKEN), does not function on portions of a carrier's network that rely on technology that cannot initiate, maintain, and terminate SIP calls (\"non-IP calls\"). The deadline for implementing STIR\/SHAKEN of June 30, 2021, is subject to a continuing extension of the FCC's requirements, provided that a carrier:\no is participating, either on its own or through a representative, including third party\nrepresentatives, as a member of a working group, industry standard group, or consortium\nthat is working to develop a non-internet Protocol caller identification authentication\nsolution, or actively testing such a solution; and\no commits to continuing support for establishing an effective solution.\nBrightspeed meets each of these conditions. The company is a member of the ATIS PTSC Non-IP\nCall Authentication Taskforce and has committed to continue to work with the industry toward\nan effective solution to redress robocalling over the non-IP network.","investigate_descript":""}

{"ct_name":"Sharman Sibia","ct_title":"Director Enterprise Security Risk Management","ct_dept":"Information Security","ct_address":"660 N Capitol Street NW Suite 240 | Washington, DC DC 20001 | 79e868f3dba03600d02ffb0e0f961973","ct_tel":"7043142618","ct_email":"robocalling@brightspeed.com","bz_address":"PO Box 1330 | Fayetteville NC 28302","country":"United States of America","declare":"2024-02-20","last_seen":"2024-03-11","sys_id":"4eba610b1b623050e91484cae54bcb85","is_new":-10,"gw_prov":"false","gw_prov_choice":"No","combined_gw":"false","ipr_imported":"false","voice_choice":"Yes","intermed_choice":"Yes","investigated":"No","intermed_exempt_rule":"The Federal Communications Commission (FCC) implemented requirements, pursuant to Section 47 C.F.R. ?64.6304(d) of the Rules, on a suite of industry standards subsequently adopted, creating an Internet Protocol (IP) call authorization framework. The Secure Telephone Identity Revisited (STIR) and Signature-based Handling of Asserted information using toKENs (SHAKEN referenced as STIR\/SHAKEN), does not function on portions of a carrier's network that rely on technology that cannot initiate, maintain, and terminate SIP calls (\"non-IP calls\"). The deadline for implementing STIR\/SHAKEN of June 30, 2021, is subject to a continuing extension of the FCC's requirements, provided that a carrier:\no is participating, either on its own or through a representative, including third party\nrepresentatives, as a member of a working group, industry standard group, or consortium\nthat is working to develop a non-internet Protocol caller identification authentication\nsolution, or actively testing such a solution; and\no commits to continuing support for establishing an effective solution.\nBrightspeed meets each of these conditions. The company is a member of the ATIS PTSC Non-IP\nCall Authentication Taskforce and has committed to continue to work with the industry toward\nan effective solution to redress robocalling over the non-IP network.","gw_exempt_rule":"","voice_exempt_rule":"The Federal Communications Commission (FCC) implemented requirements, pursuant to Section 47 C.F.R. ?64.6304(d) of the Rules, on a suite of industry standards subsequently adopted, creating an Internet Protocol (IP) call authorization framework. The Secure Telephone Identity Revisited (STIR) and Signature-based Handling of Asserted information using toKENs (SHAKEN referenced as STIR\/SHAKEN), does not function on portions of a carrier's network that rely on technology that cannot initiate, maintain, and terminate SIP calls (\"non-IP calls\"). The deadline for implementing STIR\/SHAKEN of June 30, 2021, is subject to a continuing extension of the FCC's requirements, provided that a carrier:\no is participating, either on its own or through a representative, including third party\nrepresentatives, as a member of a working group, industry standard group, or consortium\nthat is working to develop a non-internet Protocol caller identification authentication\nsolution, or actively testing such a solution; and\no commits to continuing support for establishing an effective solution.\nBrightspeed meets each of these conditions. The company is a member of the ATIS PTSC Non-IP\nCall Authentication Taskforce and has committed to continue to work with the industry toward\nan effective solution to redress robocalling over the non-IP network.","investigate_descript":""}

{"ct_name":"Sharman Sibia","ct_title":"Director Enterprise Security Risk Management","ct_dept":"Information Security","ct_address":"660 N Capitol Street NW Suite 240 | Washington, DC DC 20001 | 79e868f3dba03600d02ffb0e0f961973","ct_tel":"7043142618","ct_email":"robocalling@brightspeed.com","bz_address":"PO Box 1330 | Fayetteville NC 28302","country":"United States of America","declare":"2024-02-20","last_seen":"2024-03-05","sys_id":"4eba610b1b623050e91484cae54bcb85","is_new":-10,"gw_prov":"false","gw_prov_choice":"No","combined_gw":"false","ipr_imported":"false","voice_choice":"Yes","intermed_choice":"Yes","investigated":"","intermed_exempt_rule":"","gw_exempt_rule":"","voice_exempt_rule":"","investigate_descript":""}