RFC 2726: PGP Authentication for RIPE Database Updates
In plain English — editorial summary, not part of the RFC
This document presents the proposal for a stronger authentication method of the updates of the RIPE database based on digital signatures. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2726
- Published
- December 1999
- Authors
- J. Zsako
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2540Detached Domain Name System (DNS) InformationCurrent
March 1999
- RFC 2539Storage of Diffie-Hellman Keys in the Domain Name System (DNS)Updated
March 1999
- RFC 2560X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSPObsoleted
June 1999
- RFC 2537RSA/MD5 KEYs and SIGs in the Domain Name System (DNS)Obsoleted
March 1999
- RFC 2459Internet X.509 Public Key Infrastructure Certificate and CRL ProfileObsoleted
January 1999
- RFC 2440OpenPGP Message FormatObsoleted
November 1998
- RFC 2137Secure Domain Name System Dynamic UpdateObsoleted
April 1997
- RFC 2725Routing Policy System SecurityUpdated
December 1999
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?