Y%20A%20M - PowerPoint PPT Presentation

About This Presentation
Title:

Y%20A%20M

Description:

3461 Simple Mail Transfer Protocol (SMTP) Service Extension for Delivery Status ... 'The time has come,' the Walrus said, 'To talk of many things: ... – PowerPoint PPT presentation

Number of Views:60
Avg rating:3.0/5.0
Slides: 12
Provided by: Ton108
Learn more at: https://www.ietf.org
Category:
Tags: 20a | 20m | walrus

less

Transcript and Presenter's Notes

Title: Y%20A%20M


1
Y A M
  • Yet Another Mail
  • Working Group

2
What do the following RFCshave in common?
  • SMTP / Submit
  • 1652 SMTP Service Extension for 8bit-MIME
    transport. July 1994.
  • 3461 Simple Mail Transfer Protocol (SMTP) Service
    Extension for Delivery Status Notifications
    (DSNs). January 2003.
  • 4409 Message Submission for Mail. April 2006.
  • 5321 Simple Mail Transfer Protocol. October 2008
  • Message Format and Headers
  • 1864 The Content-MD5 Header Field. October 1995.
  • 3282 Content Language Headers. May 2002.
  • 3803 Content Duration MIME Header Definition.
    June 2004.
  • 5322 Internet Message Format. October 2008
  • MIME
  • 2045 MIME Part One Format of Internet Message
    Bodies. November 1996.
  • 2046 MIME Part Two Media Types. November 1996.
  • 2047 MIME Part Three Message Header Extensions
    for Non-ASCII Text. November 1996.
  • 2049 MIME Part Five Conformance Criteria and
    Examples. November 1996.
  • Other
  • 3462 The Multipart/Report Content Type for the
    Reporting of Mail System Administrative Messages.
    January 2003.
  • 3463 Enhanced Mail System Status Codes. January
    2003.
  • 3464 An Extensible Message Format for Delivery
    Status Notifications. January 2003.

3
Whats in common?
  • They are all currently Draft Standard
  • The oldest is 14 years old
  • 1652 SMTP Service Extension for 8bit-MIME
    transport. July 1994.
  • They are all candidates for advancement to Full
    Standard

4
2026
  • 4.1.3 Internet Standard
  • A specification for which significant
    implementation and successful operational
    experience has been obtained may be elevated to
    the Internet Standard level. An Internet
    Standard (which may simply be referred to as a
    Standard) is characterized by a high degree of
    technical maturity and by a generally held belief
    that the specified protocol or service provides
    significant benefit to the Internet community.

5
2026
  • 6.2 Advancing in the Standards Track
  • (An IESG standards action) is followed for each
    action that attends the advancement of a
    specification along the standards track.
  • A specification shall remain at the Draft
    Standard level for at least four (4) months, or
    until at least one IETF meeting has occurred,
    whichever comes later.

6
2026
  • 6.2 Advancing in the Standards Track
  • A specification may be (indeed, is likely to be)
    revised as it advances through the standards
    track.
  • At each stage, the IESG shall determine the scope
    and significance of the revision to the
    specification, and, if necessary and appropriate,
    modify the recommended action.
  • Minor revisions are expected, but a significant
    revision may require that the specification
    accumulate more experience at its current
    maturity level before progressing.
  • Finally, if the specification has been changed
    very significantly, the IESG may recommend that
    the revision be treated as a new document,
    reentering the standards track at the beginning.
  • Change of status shall result in republication of
    the specification as an RFC, except in the rare
    case that there have been no changes at all in
    the specification since the last publication.

7
Much of the work will be
  • a review
  • followed by either
  • a recommendation to the IESG to modify the status
    of the existing status, or
  • a revised document to be submitted for acceptance
    as Full Standard.
  • Repeat for next RFC

8
Revised documents
  • Limit to known errata
  • NO NEW WORK!!!!

9
An example of the strategya plan for 2821ter /
5321bis
  • Wait the appropriate number of months to see if
    theres anything major that we goofed on
  • Conservatively Feb 2009
  • depends on how time is measured
  • Drop in minor non-technical changes identified
    late in previous cycle
  • better cross referencing of ABNF productions
  • better IPv6 syntax definition
  • Post the revision
  • Insist that there be no rehashing of old
    arguments
  • Get it passed

10
Charter Discussion
  • People will be discussing charter this week
  • (starting at end of app area meeting)

11
  • "The time has come," the Walrus said,
  • "To talk of many things
  • Of shoes and ships and sealing-wax
  • Of cabbages and kings
  • And why the sea is boiling hot
  • And whether pigs have wings."
Write a Comment
User Comments (0)
About PowerShow.com