Sieve Notification Mechanism: mailto
draft-ietf-sieve-notify-mailto-10

[Ballot comment]
The message composition guidelines in section 2.7 are very weak.  As far as I can tell, the only field that is required to be included is the "Auto-Submitted: auto-notified" header field.  Everything else is a SHOULD.  Is that really the wg's intention?

[Ballot comment]
Couple of nits about references (could be fixed with an RFC Editor
note): [IANA] should be normative, and should point to RFC 5226.
[RFC2821] and [RFC2822] have been obsoleted by 5321 and 5322.

[Ballot discuss]
It seems like the draft should include a way for a recipricant of these notifies to tell the server to stop sending them. If someone accidentally fat fingers a phone number for a SMS notify in a sieve script, how will the poor users getting all the SMS ever stop them?

[Ballot discuss]
OK, this is probably a competitor in the race for the most pedantic discuss ever, but idnits does complain about two instances of "MAY NOT", which isn't a valid RFC2119 term. I believe both can be replaced by MUST NOT.

(If Lisa sticks this change into an RFC Editor Note, I promise to clear before Thursday.)

[Ballot comment]
Two fixes I believe would improve this document:

1. It "Updates: RFC 3834" because it changes the extension rules from
  IETF consensus to Specification Required.

2. The term "URI Header" is not defined anywhere.  I assume it means
  "Header field name and value extracted from the mailto URI," but it
  might be a good idea to include that (or a similar) definition in
  this specification.

Lisa: Who are you recommending as the expert reviewer for the new
      auto-submitted extension registry this creates?

IANA Last Call comments:

IANA has questions:

Please define the registration procedures for the new registry
created in section 6.2.

Action 1 (section 6.1):

Upon approval of this document, the IANA will make the following
assignments in the "Sieve Notification Mechanisms" registry located
at
http://www.iana.org/assignments/sieve-notification

Mechanism name: mailto
Mechanism URI: RFC2368
Mechanism-specific tags: none
Standards Track/IESG-approved experimental RFC number: [RFC- ietf-sieve-notify-mailto-06.txt]
Person and email address to contact for further information:
Michael Haardt


Action 2 (sections 6.2, 6.3):

Upon approval of this document, the IANA will create the following
registry "Auto-Submitted Header Keywords" located at
http://www.iana.org/assignments/TBD

Registration Template:

To: iana@iana.org
Subject: Registration of new auto-submitted header field keyword
Keyword value: [the text value of the field]
Description: [a brief explanation of the purpose of this value]
Parameters: [list any keyword-specific parameters, specify their
meanings, specify whether they are required or optional; use "none"
if there are none]
Standards Track/IESG-approved experimental RFC number: [identifies the specification that defines the value being registered]
Contact: [name and email address to contact for further information]

Registration Procedures: UNKNOWN

Initial contents of this registry will be:

Keyword value: no
Description: Indicates that a message was NOT automatically
generated, but was created by a human. It is the equivalent to the
absence of an Auto-Submitted header altogether.
Parameters: none
Standards Track/IESG-approved experimental RFC number: RFC3834
Contact: Keith Moore

Keyword value: auto-generated
Description: Indicates that a message was generated by an
automatic process, and is not a direct response to another
message.
Parameters: none
Standards Track/IESG-approved experimental RFC number: RFC3834
Contact: Keith Moore

Keyword value: auto-replied
Description: Indicates that a message was automatically generated
as a direct response to another message.
Parameters: none
Standards Track/IESG-approved experimental RFC number: RFC3834
Contact: Keith Moore

Keyword value: sieve-notify
Description: Indicates that a message was generated by a Sieve
notification system.
Parameters: owner-email, owner-token. Both optional, both refer to
the owner of the Sieve script that generated this message. See the
relevant RFC for details.
Standards Track/IESG-approved experimental RFC number:
[RFC-sieve-notify-mailto-07]
Contact: Michael Haardt


We understand the above to be the only IANA Actions for this
document.