![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
One Time Password (OTP) tokens provide a convenient and secure means of user authentication. Combined with a PIN an OTP token provides a robust two factor authentication solution.
Recent developments in Internet crime, in particular credential theft (phishing) makes the widespread use of and thus development of open standards for OTP tokens and other symmetric key cryptographic systems highly desirable.
This requires a standards based key provisioning infrastructure analogous to the mechanisms provided in public key infrastructures. In particular the ability to provision symmetric keys and associated attributes dynamically to already issued devices such as cell phones and USB drives is highly desirable. The working group will develop the necessary protocols and data formats required to support provisioning and management of symmetric key authentication tokens, both proprietary and standards based.
It is the intention of the working group to create an open standard unencumbered by proprietary intellectual property claims. Essential claims required to implement the specification should be available for license according to Reasonable, Non-Discriminatory and Royalty Free terms (RAND-Z).
The scope of the working group shall be to define protocols and data formats necessary for provisioning of symmetric cryptographic keys and associated attributes.
The working group will produce the following deliverables:
· 2006 July Charter WG
· 2006 November WG last call on Portable Symmetric Key Container
· 2006 December WG last call on Dynamic Symmetric Key Provisioning Protocol
· 2007 January IETF Last call on PROPOSED status
· 2007 April Complete Interoperability testing
· 2007 July WG last call on promotion to DRAFT
· 2007 September IETF last call on DRAFT status
· 2007 December WG closes.
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.