Status of this Memo

Status of this Memo (2001)

Cached

Download Links

by W. Ford (verisign , W. Polk (nist

BibTeX

@MISC{(verisign01statusof,
    author = {W. Ford (verisign and W. Polk (nist},
    title = {Status of this Memo},
    year = {2001}
}

Bookmark

OpenURL

Abstract

This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at

Citations

1092	Key words for use in RFCs to Indicate Requirement Levels - Bradner - 1997
675	The MD5 Message-Digest Algorithm - Rivest - 1992
586	Standard for the format of ARPA Internet text messages - Crocker - 1982
524	Domain names - concepts and facilities - Mockapetris - 1987
444	Internet protocol - Postel - 1981
314	Internet Protocol, Version 6 (IPv6) Specification", RFC 2460 - Deering, Hinden - 1998
224	The Lightweight Directory Access Protocol: X.500 Lite - Howes - 1995
189	Classless Inter-Domain Routing (CIDR): and address assignment and aggregation strategy. RFC 1519 - Fuller, Li, et al. - 1993
151	Key words for use in RFCs to indicate requirement levels. RFC 2119 (Best Current Practice - Bradner - 1997
143	Privacy enhancement for Internet electronic mail: Part II: Certificate-based key management - KENT - 1993
143	Internet X.509 public key infrastructure certificate and - Housley, Ford, et al.
141	The Kerberos Network Authentication Service (V5 - Kohl, Neuman - 1993
129	Privacy enhancement for Internet electronic mail: Part III: Algorithms, modes, and identifiers - BALENSON - 1993
125	UTF-8, a transformation format of ISO 10646 - Yergeau - 2003
61	Uniform Resource Locators (URL)", RFC 1738 - Berners-Lee, McCahill - 1994
57	UTF-8, a transformation format of Unicode and - Yergeau - 1996
56	Internet X.509 - Housley, Hoffman - 1999
55	Public Key Cryptography for Initial Authentication - Tung
49	IETF Policy on Character Sets and Languages - Alvestrand - 1998
40	The String Representation of Standard Attribute Syntaxes - Howes, Kille, et al. - 1995
28	The MD2 Message-Digest Algorithm - Kaliski - 1992
16	UTF-8, a transformation format of ISO 10646", RFC 2279 - Yergeau - 1998
10	PKCS #1: RSA Encryption Version 1.5 - Kaliski - 1998
6	Using Domains - Sataluri - 1998
5	Message Security Protocol 4.0", Revision A - 701
3	Internet X.509 public key infrastructure time-stamp protocol (TSP - Admas, Cain, et al. - 2001
2	Standard for the format of ARPA Internet text messages", RFC 822 - Postel, Protocol, et al. - 2001
2	Online Certificate Status Protocal - OCSP - Myers, Ankney, et al. - 1999
2	Message Security Protocol 4.0", Revision A, 1997-02-06. [X.208] [X.501] [X.509] [X.520] CCITT Recommendation X.208: Specification of Abstract Syntax Notation One (ASN.1 - 701 - 1988
1	87] DRAFT October 2001 The use of a single key pair for both signature and other purposes is strongly discouraged. Use of separate key pairs for signature and key management provides several benefits to the users. The ramifications associated with loss or - Housley, Polk, et al.
1	Internet Protocol, Version 6 (IPv6) Specification - Housley, Polk, et al. - 1995
1	81] DRAFT April 2001 The use of a single key pair for both signature and other purposes is strongly discouraged. Use of separate key pairs for signature and key management provides several benefits to the users. The ramifications associated with loss or d - Housley, Polk, et al.
1	UTF-8, a transformation format of ISO 10646", January 1998. 2560 - Yergeau - 1999
1	8 Intellectual Property Rights The IETF has been notified of intellectual property rights claimed in regard to some or all of the specification contained in this document. For more information consult the online list of claimed rights. The IETF takes no p - Housley, Polk, et al. - 2000
1	Using Domains in LDAP/X.500 Distinguished Names - Sataluri - 1998
1	E): Information Technology - Open Systems Interconnection - The - Housley, Polk - 1997
1	83] DRAFT June 2001 [RFC 1778 - Housley, Polk, et al. - 1995
1	Public Key Cryptography For The Financial Services Industry: Extensions To Public Key Certificates And Certificate Revocation Lists - 55-1995 - 1995
1	Public Key Cryptography for - Tung, Neuman, et al. - 2000
1	IETF Policy on Character Sets and - Alvestrand - 1998
1	80] INTERNET DRAFT January 2001 8 Intellectual Property Rights The IETF has been notified of intellectual property rights claimed in regard to some or all of the specification contained in this document. For more information consult the online list of cla - Housley, Polk, et al.
1	The compression function of MD2 is not collision free," Presented at Selected Areas in Cryptography ’95 - Housley, Polk, et al. - 1993
1	Classless Routing (CIDR): an Address Assignment and Aggregation Strategy - Fuller, Li, et al. - 1993
1	The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under suc - Housley, Polk, et al. - 2000