Skip to main content

A Property Types Registry for the Authentication-Results Header Field
RFC 7410

Revision differences

Document history

Date Rev. By Action
2015-10-14
04 (System) Notify list changed from appsawg-chairs@ietf.org, draft-ietf-appsawg-authres-ptypes-registry@ietf.org, scott@kitterman.com to (None)
2014-12-12
04 (System) IANA registries were updated to include RFC7410
2014-12-04
04 (System) RFC published
2014-12-02
04 (System) RFC Editor state changed to AUTH48-DONE from AUTH48
2014-12-01
04 (System) RFC Editor state changed to AUTH48 from RFC-EDITOR
2014-11-28
04 Jean Mahoney Closed request for Telechat review by GENART with state 'No Response'
2014-11-05
04 (System) RFC Editor state changed to RFC-EDITOR from EDIT
2014-10-24
04 (System) IANA Action state changed to RFC-Ed-Ack from Waiting on RFC Editor
2014-10-24
04 Gunter Van de Velde Request for Last Call review by OPSDIR Completed: Ready. Reviewer: Sarah Banks.
2014-10-23
04 (System) IANA Action state changed to Waiting on RFC Editor from Waiting on Authors
2014-10-23
04 (System) IANA Action state changed to Waiting on Authors
2014-10-23
04 Tero Kivinen Closed request for Last Call review by SECDIR with state 'No Response'
2014-10-21
04 Amy Vezza IESG state changed to RFC Ed Queue from Approved-announcement sent
2014-10-20
04 (System) RFC Editor state changed to EDIT
2014-10-20
04 (System) Announcement was received by RFC Editor
2014-10-20
04 Barry Leiba Notification list changed to appsawg-chairs@tools.ietf.org, draft-ietf-appsawg-authres-ptypes-registry@tools.ietf.org, scott@kitterman.com from appsawg-chairs@tools.ietf.org, draft-ietf-appsawg-authres-ptypes-registry@tools.ietf.org, scott@kitterman.com, apps-discuss@ietf.org
2014-10-20
04 Amy Vezza IESG state changed to Approved-announcement sent from Approved-announcement to be sent
2014-10-20
04 Amy Vezza IESG has approved the document
2014-10-20
04 Amy Vezza Closed "Approve" ballot
2014-10-20
04 Amy Vezza Ballot approval text was generated
2014-10-16
04 Barry Leiba IESG state changed to Approved-announcement to be sent from Approved-announcement to be sent::Point Raised - writeup needed
2014-10-16
04 Cindy Morgan IESG state changed to Approved-announcement to be sent::Point Raised - writeup needed from IESG Evaluation
2014-10-16
04 Cindy Morgan Changed consensus to Yes from Unknown
2014-10-16
04 Joel Jaeggli [Ballot Position Update] New position, No Objection, has been recorded for Joel Jaeggli
2014-10-15
04 Richard Barnes [Ballot Position Update] New position, No Objection, has been recorded for Richard Barnes
2014-10-15
04 Ted Lemon [Ballot Position Update] New position, No Objection, has been recorded for Ted Lemon
2014-10-15
04 Jari Arkko [Ballot Position Update] New position, No Objection, has been recorded for Jari Arkko
2014-10-15
04 Adrian Farrel [Ballot Position Update] New position, No Objection, has been recorded for Adrian Farrel
2014-10-15
04 Alia Atlas [Ballot Position Update] New position, No Objection, has been recorded for Alia Atlas
2014-10-15
04 Kathleen Moriarty
[Ballot comment]
I'm curious to see the response to Stephen's question, if that's possible, it may be a good way to handle security issues that …
[Ballot comment]
I'm curious to see the response to Stephen's question, if that's possible, it may be a good way to handle security issues that may arise with new ptypes.
2014-10-15
04 Kathleen Moriarty [Ballot Position Update] New position, No Objection, has been recorded for Kathleen Moriarty
2014-10-14
04 Pete Resnick [Ballot Position Update] New position, Yes, has been recorded for Pete Resnick
2014-10-13
04 Martin Stiemerling [Ballot Position Update] New position, No Objection, has been recorded for Martin Stiemerling
2014-10-13
04 Brian Haberman [Ballot Position Update] New position, No Objection, has been recorded for Brian Haberman
2014-10-13
04 Stephen Farrell
[Ballot comment]

I wondered if it'd be worthwhile asking that the
designated expert try ensure that the security and privacy
consequences of new entries also …
[Ballot comment]

I wondered if it'd be worthwhile asking that the
designated expert try ensure that the security and privacy
consequences of new entries also be documented?  That's
assuming there are cases where the header field is likely
to transit between ADMDs. I'm not sure if that's really
needed though, but 7001 does have a fairly significant set
of security considerations, so presumably new entries
might also deserve a similar level of documentation. OTOH,
I could buy that experience with 7001 means that this
isn't really needed or that demanding that level of
documentation might be counterproductive.
2014-10-13
04 Stephen Farrell [Ballot Position Update] New position, No Objection, has been recorded for Stephen Farrell
2014-10-09
04 Benoît Claise [Ballot Position Update] New position, No Objection, has been recorded for Benoit Claise
2014-10-08
04 Jean Mahoney Request for Telechat review by GENART is assigned to Russ Housley
2014-10-08
04 Jean Mahoney Request for Telechat review by GENART is assigned to Russ Housley
2014-10-01
04 (System) IANA Review state changed to IANA OK - Actions Needed from Version Changed - Review Needed
2014-10-01
04 Barry Leiba Ballot has been issued
2014-10-01
04 Barry Leiba [Ballot Position Update] New position, Yes, has been recorded for Barry Leiba
2014-10-01
04 Barry Leiba Created "Approve" ballot
2014-10-01
04 Barry Leiba IESG state changed to IESG Evaluation from Waiting for AD Go-Ahead
2014-10-01
04 Barry Leiba Placed on agenda for telechat - 2014-10-16
2014-10-01
04 Barry Leiba Notification list changed to : appsawg-chairs@tools.ietf.org, draft-ietf-appsawg-authres-ptypes-registry@tools.ietf.org, scott@kitterman.com, apps-discuss@ietf.org
2014-09-30
04 Murray Kucherawy IANA Review state changed to Version Changed - Review Needed from IANA - Not OK
2014-09-30
04 Murray Kucherawy New version available: draft-ietf-appsawg-authres-ptypes-registry-04.txt
2014-09-30
03 (System) IESG state changed to Waiting for AD Go-Ahead from In Last Call
2014-09-25
03 (System) IANA Review state changed to IANA - Not OK from IANA - Review Needed
2014-09-25
03 Pearl Liang
IESG/Authors/WG Chairs:

IANA has reviewed draft-ietf-appsawg-authres-ptypes-registry-03.  Authors should review the comments and/or questions below.  Please report any inaccuracies and respond to any questions as soon …
IESG/Authors/WG Chairs:

IANA has reviewed draft-ietf-appsawg-authres-ptypes-registry-03.  Authors should review the comments and/or questions below.  Please report any inaccuracies and respond to any questions as soon as possible.

IANA's reviewer has the following comments/questions:

IANA has questions about the action requested in the IANA Considerations section of this document.

Upon approval of this document, IANA understands that there is a single action which needs to be completed.

A new registry is to be created called the Email Authentication Property Types registry.

IANA Question --> Should this be a new sub-registry of the existing Email Authentication
Parameters located at:

http://www.iana.org/assignments/email-auth?

The new registry will be named the Email Authentication Property Types registry and will be located at [ TBD-see-above ]. The registry is maintained through Expert Review as defined by RFC 5226.

IANA Question --> IANA understands that initial reqistrations are to be made based on information in Section 2 of [ RFC 7001 ]. The Augmented Backus-Naur Form of the header field specifies ptype with the following possible options: "smtp" "header" "body" and "policy"

Is the initial registry supposed, then, to look as follows?

ptype | Description  |  Reference
---------+--------------------------------------------+-------------------
smtp |      ???            | [ RFC 7001 ]
header  |      ???            | [ RFC 7001 ]
body  |      ???            | [ RFC 7001 ]
policy  |      ???            | [ RFC 7001 }

If so, what are the "descriptions" to be used for each of the ptypes. If not, what should the initial registry look like?

QUESTION: Those new requested "ptypes" are actually mixed  between multiple header fields
RFC7001 in section 2.2.  For clarity purposes, can the author please describe the new "ptype"
values in the IC section of this draft?

IANA understands that this is the only action required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is only to confirm what actions will be performed.
2014-09-19
03 Gunter Van de Velde Request for Last Call review by OPSDIR is assigned to Sarah Banks
2014-09-19
03 Gunter Van de Velde Request for Last Call review by OPSDIR is assigned to Sarah Banks
2014-09-18
03 Jean Mahoney Request for Last Call review by GENART is assigned to Russ Housley
2014-09-18
03 Jean Mahoney Request for Last Call review by GENART is assigned to Russ Housley
2014-09-18
03 Tero Kivinen Request for Last Call review by SECDIR is assigned to Lt. Mundy
2014-09-18
03 Tero Kivinen Request for Last Call review by SECDIR is assigned to Lt. Mundy
2014-09-16
03 Amy Vezza IANA Review state changed to IANA - Review Needed
2014-09-16
03 Amy Vezza
The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce
CC:
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (A Property Types Registry for …
The following Last Call announcement was sent out:

From: The IESG
To: IETF-Announce
CC:
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (A Property Types Registry for the Authentication-Results Header Field) to Proposed Standard


The IESG has received a request from the Applications Area Working Group
WG (appsawg) to consider the following document:
- 'A Property Types Registry for the Authentication-Results Header Field'
  as Proposed
Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2014-09-30. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


  This document updates RFC7001 by creating a registry for property
  types in the Authentication-Results header field, used in email
  authentication work, rather than limiting participants to using the
  original, small set of fixed values.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-appsawg-authres-ptypes-registry/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-appsawg-authres-ptypes-registry/ballot/


No IPR declarations have been submitted directly on this I-D.


2014-09-16
03 Amy Vezza IESG state changed to In Last Call from Last Call Requested
2014-09-16
03 Barry Leiba Last call was requested
2014-09-16
03 Barry Leiba Last call announcement was generated
2014-09-16
03 Barry Leiba Ballot approval text was generated
2014-09-16
03 Barry Leiba IESG state changed to Last Call Requested from AD Evaluation
2014-09-16
03 Murray Kucherawy New version available: draft-ietf-appsawg-authres-ptypes-registry-03.txt
2014-09-15
02 Barry Leiba Ballot writeup was changed
2014-09-15
02 Barry Leiba Ballot writeup was generated
2014-09-15
02 Barry Leiba Notification list changed to : appsawg-chairs@tools.ietf.org, draft-ietf-appsawg-authres-ptypes-registry@tools.ietf.org, scott@kitterman.com
2014-09-15
02 Barry Leiba IESG state changed to AD Evaluation from Publication Requested
2014-09-15
02 Alexey Melnikov
1. Summary

The document shepherd is Scott Kitterman.  The Responsible Area Director is Barry Leiba.

RFC7001 defines the email Authentication-Results header field that presents the …
1. Summary

The document shepherd is Scott Kitterman.  The Responsible Area Director is Barry Leiba.

RFC7001 defines the email Authentication-Results header field that presents the results
of an authentication effort in a machine-readable format.  The specification in that
document enumerated a small set of types of  properties that can be reported using this
mechanism.  That constrained set of types has proven to be too narrow.  Accordingly, this
document updates the specification to allow for additional property types ("ptypes")
beyond the original set, and creates a registry where new ones can be listed and their
defining documents referenced.

As an update to RFC 7001, this document is appropriately placed on the standards track.

2. Review and Consensus

This is a simple document and WGLC was quiet (no comments).  There was significant
discussion prior to WGLC with reviews and comments from three different reviewers.
The only significant technical issue that was discussed was the possibility that the version
number of the field might need to be increased.  The unanimous conclusion was that it
does not.

This draft is a precursor to draft-martin-authentication-results-tls.

Once this document relaxes the ptype constraint, other authentication types such as TLS
(mentioned above) are expected.  Multiple participants reported plans to implement these.

3. Intellectual Property

No IPR disclosures have been submitted and the author has indicated he is not aware of
any other IPR issues.

4. Other Points

The IANA considerations appear clear and complete.

This document creates an Email Authentication Property Types registry.  The standard for
update is expert review. 
2014-09-15
02 Alexey Melnikov State Change Notice email list changed to appsawg-chairs@tools.ietf.org, draft-ietf-appsawg-authres-ptypes-registry@tools.ietf.org
2014-09-15
02 Alexey Melnikov Responsible AD changed to Barry Leiba
2014-09-15
02 Alexey Melnikov IETF WG state changed to Submitted to IESG for Publication from WG Consensus: Waiting for Write-Up
2014-09-15
02 Alexey Melnikov IESG state changed to Publication Requested
2014-09-15
02 Alexey Melnikov IESG process started in state Publication Requested
2014-09-15
02 Alexey Melnikov Tag Doc Shepherd Follow-up Underway cleared.
2014-09-15
02 Alexey Melnikov IETF WG state changed to WG Consensus: Waiting for Write-Up from Waiting for WG Chair Go-Ahead
2014-09-15
02 Murray Kucherawy Changed document writeup
2014-09-15
02 Scott Kitterman Changed document writeup
2014-09-14
02 Murray Kucherawy Tag Doc Shepherd Follow-up Underway set.
2014-09-14
02 Murray Kucherawy IETF WG state changed to Waiting for WG Chair Go-Ahead from In WG Last Call
2014-08-30
02 Murray Kucherawy WGLC ends September 14, 2014.
2014-08-30
02 Alexey Melnikov Started WGLC after checking with the document shepherd.
2014-08-30
02 Alexey Melnikov IETF WG state changed to In WG Last Call from WG Document
2014-08-26
02 Murray Kucherawy New version available: draft-ietf-appsawg-authres-ptypes-registry-02.txt
2014-08-24
01 Murray Kucherawy New version available: draft-ietf-appsawg-authres-ptypes-registry-01.txt
2014-08-11
00 Murray Kucherawy Document shepherd changed to D. Scott Kitterman
2014-08-11
00 Murray Kucherawy Intended Status changed to Proposed Standard from None
2014-08-11
00 Murray Kucherawy This document now replaces draft-kucherawy-authres-ptypes-registry instead of None
2014-08-11
00 Murray Kucherawy New version available: draft-ietf-appsawg-authres-ptypes-registry-00.txt