Authentication-Results Registration for OpenPGP Signature Verification
draft-ser-authentication-results-openpgp-00
|
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Author |
|
Simon Ser
|
|
Last updated |
|
2020-10-19
(latest revision 2019-03-10)
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
htmlized (tools)
htmlized
bibtex
|
Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Independent Submission S. Ser
Internet-Draft March 11, 2019
Intended status: Informational
Expires: September 12, 2019
Authentication-Results Registration for OpenPGP Signature Verification
draft-ser-authentication-results-openpgp-00
Abstract
RFC 7601 specifies the Authentication-Results header field for
conveying results of message authentication checks. This document
defines a new authentication method to be used in the Authentication-
Results header field for PGP-related signature checks.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on September 12, 2019.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
Ser Expires September 12, 2019 [Page 1]
Internet-Draft Authentication-Results for OpenPGP March 2019
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. "pgp" Authentication Method . . . . . . . . . . . . . . . . . 2
2.1. OpenPGP Results . . . . . . . . . . . . . . . . . . . . . 2
2.2. Email Authentication Parameters for OpenPGP . . . . . . . 4
2.2.1. body.pgp-fingerprint . . . . . . . . . . . . . . . . 4
2.2.2. body.pgp-user-id . . . . . . . . . . . . . . . . . . 4
2.3. Examples . . . . . . . . . . . . . . . . . . . . . . . . 4
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6
5. Normative References . . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
[RFC7601] specifies the Authentication-Results header field for
conveying results of message authentication checks. OpenPGP
signature verification is sometimes implemented in border message
transfer agents (for instance some MTAs have their own OpenPGP PKI),
there is a need to convey signature verification status to Mail User
Agents (MUAs) and downstream filters. This document defines a new
authentication method to be used in the Authentication-Results header
field for OpenPGP-related signature checks.
2. "pgp" Authentication Method
OpenPGP signature verification is represented by the "pgp" method and
is defined in [RFC4880].
2.1. OpenPGP Results
The result values used by OpenPGP [RFC4880] are as follows:
Ser Expires September 12, 2019 [Page 2]
Internet-Draft Authentication-Results for OpenPGP March 2019
+-----------+-------------------------------------------------------+
| Result | Meaning |
| Code | |
+-----------+-------------------------------------------------------+
| none | The message was not signed. |
| pass | The message was signed, the signature or signatures |
| | were acceptable to the verifier, and the signature(s) |
| | passed verification tests. |
| fail | The message was signed and the signature or |
| | signatures were acceptable to the verifier, but they |
| | failed the verification test(s). |
| policy | The message was signed and signature(s) passed |
| | verification tests, but the signature or signatures |
| | were not acceptable to the verifier. |
| neutral | The message was signed but the signature or |
| | signatures contained syntax errors or were not |
| | otherwise able to be processed. This result is also |
| | used for other failures not covered elsewhere in this |
Show full document text