RFC 3157 (rfc3157) - Page 1 of 20
Securely Available Credentials - Requirements
Alternative Format: Original Text Document
Network Working Group A. Arsenault
Request for Comments: 3157 Diversinet
Category: Informational S. Farrell
Baltimore Technologies
August 2001
Securely Available Credentials - Requirements
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved.
Abstract
This document describes requirements to be placed on Securely
Available Credentials (SACRED) protocols.
Table Of Contents
1. Introduction.................................................1
2. Framework Requirements.......................................4
3. Protocol Requirements........................................7
4. Security Considerations.....................................10
References.....................................................12
Acknowledgements...............................................12
Authors' Addresses.............................................13
Appendix A: A note on SACRED vs. hardware support..............14
Appendix B: Additional Use Cases...............................14
Full Copyright Statement.......................................20
1. Introduction
"Credentials" are information that can be used to establish the
identity of an entity, or help that entity communicate securely.
Credentials include such things as private keys, trusted roots,
tickets, or the private part of a Personal Security Environment (PSE)
[RFC 2510] - that is, information used in secure communication on the
Internet. Credentials are used to support various Internet
protocols, e.g., S/MIME, IPSec and TLS.
Arsenault & Farrell Informational