Transcription of USB Type-C™ Authentication
{{id}} {{{paragraph}}}
USB Developer Days October 24 25, 2017 USB Implementers Forum 2017 USB Type-C AuthenticationStephanie Wallick IntelUSB Developer Days 2017 Taipei, TaiwanOctober 24 25, 20171 USB Developer Days October 24 25, 2017 USB Implementers Forum 2017 USB Type-C Authentication Introduction Architecture Protocol Certificates2 USB Developer Days October 24 25, 2017 USB Implementers Forum 2017 Specification Overview What USB Type-C Authentication Specification does Provides primitives and protocol for one-way Authentication Verify vendor and product are what they claim to be Bus-agnostic, but specification provides mapping to USB and USB PD Authenticates USB Devices, USB PD Sources, USB PD Sinks, and USB PD Cables Defines optional normative framework products are not required to support What USB Type-C Authentication Specification does notdo Define policy or criteria to accept/reject a product Policy defined by user and/or vendor Not intended to limit interoperability just weed out untrusted devices Provide method/criteria for certificate revocation Define method for t
USB Developer Days –October 24 –25, 2017 USB Implementers Forum © 2017 USB Type-C™ Authentication •Introduction •Architecture •Protocol •Certificates 2
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document:
{{id}} {{{paragraph}}}