SIEVE Mail Filtering WG

1
SIEVE Mail Filtering WG

• IETF 70, Vancouver
• WG Chairs Cyrus Daboo, Alexey Melnikov
• Mailing List ltmailtoietf-mta-filters_at_imc.orggt
• Jabber sieve_at_jabber.ietf.org

2
Notification Draft

• Current draft
• draft-ietf-sieve-notify-10
• Changes since -08
• Added missing IANA registry for notification
  methods
• Extended requirements for avoiding loops and
  amplification attacks (similar to the text
  3028bis)
• Other minor editorial changes as per Lisa's
  review review

3
Notification Draft status

• IETF LC has ended
• Some editorial comments received from Peter
  Saint-Andre
• Will be included in -11
• One minor comment received during GenArt review
• Suggestion to create a new IANA registry for
  notification-capability
• Also noticed in the IANA template
• Mechanism-specific tags the names of any Sieve
  notify tags that are specific to this mechanism,
  or "none"
• tags or options?
• Mechanism registration template only allows for
  Standard Track/Experimental RFC references.
  Should Informational be allowed (for vendor
  specific registrations)?

4
Notification Draft IANA issue

• IANA feedback
• Sieve Notification Mechanisms registry has no
  registration procedures!
• Suggested text (similar to 3028bis)
• IANA is requested to create a new registry
  for Sieve notification mechanisms. This registry
  contains both vendor-controlled notification
  mechanism names (beginning with "vnd.") and
  IETF-controlled notification mechanism names.
  Vendor-controlled notification mechanism names
  may be registered on a first-come, first-served
  basis, by applying to IANA with the form in the
  following section. Registration of notification
  mechanisms that do not begin with "vnd." REQUIRES
  a standards track or IESG approved experimental
  RFC.

5
Notification Draft next step

• -11 will address all known issues. Then authors
  will ask Lisa to send the document to IESG