Skip to main content

Rx Security Object Providing Cleartext Peer Identity Assertions
draft-tkeiser-rxrpc-sec-clear-02

Document Type Expired Internet-Draft (individual)
Expired & archived
Author Thomas Keiser
Last updated 2010-04-17
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

RxRPC was originally designed as the remote procedure call layer for AFS-3. Today there are a number of anonymous RxRPC applications which require identity assertions in order to ensure that the desired peer receives and processes a procedure call. This memo defines a replacement for the rxnull security class which provides a means for mutually agreeing upon who is communicating, without incurring cryptographic overhead. It should be noted that, much like rxnull, this security object is not suitable for use in a distributed environment due to its inability to provide integrity protection.

Authors

Thomas Keiser

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)