RFC 2243: OTP Extended Responses
In plain English — editorial summary, not part of the RFC
This document provides a specification for a type of response to an OTP [RFC 1938] challenge that carries explicit indication of the response's encoding. This document also provides a specification for a response that allows an OTP generator to request that a server re-initialize a sequence and change parameters such as the secret pass phrase. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2243
- Published
- November 1997
- Authors
- C. Metz
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2246The TLS Protocol Version 1.0Obsoleted
January 1999
- RFC 2228FTP Security ExtensionsCurrent
October 1997
- RFC 2289A One-Time Password SystemCurrent
February 1998
- RFC 2137Secure Domain Name System Dynamic UpdateObsoleted
April 1997
- RFC 2104HMAC: Keyed-Hashing for Message AuthenticationUpdated
February 1997
- RFC 2085HMAC-MD5 IP Authentication with Replay PreventionCurrent
February 1997
- RFC 2401Security Architecture for the Internet ProtocolObsoleted
November 1998
- RFC 2084Considerations for Web Transaction SecurityCurrent
January 1997
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?