RFC 2243 (rfc2243) - Page 1 of 10
OTP Extended Responses
Alternative Format: Original Text Document
Network Working Group C. Metz
Request for Comments: 2243 The Inner Net
Category: Standards Track November 1997
OTP Extended Responses
Status of this Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (1997). All Rights Reserved.
Abstract
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. Codings for the two mandatory OTP data formats
using this new type of response are presented.
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.
1. Conventions, Terms, and Notation
This document specifies the data formats and software behaviors
needed to use OTP extended responses. The data formats are described
three ways: using an ad-hoc UNIX manual page style syntax, using
augmented BNF described in sections two and three of RFC 822, and by
examples. Should there be any conflict between these descriptions,
the augmented BNF takes precedence. The software behaviors are
described in words, and specific behavior compliance requirements are
itemized using the requirements terminology (specifically, the words
MUST, SHOULD, and MAY) defined in RFC 2119.
Metz Standards Track