17
1 Yet Another Mail Working Group IETF 78 July 29, 2010

1 Yet Another Mail Working Group IETF 78 July 29, 2010

Embed Size (px)

Citation preview

Page 1: 1 Yet Another Mail Working Group IETF 78 July 29, 2010

1

Yet Another MailWorking Group

IETF 78

July 29, 2010

Page 2: 1 Yet Another Mail Working Group IETF 78 July 29, 2010

2

Note WellAny submission to the IETF intended by the Contributor for publication as all or part of an

IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to:

– the IETF plenary session,– any IETF working group or portion thereof,– the IESG or any member thereof on behalf of the IESG,– the IAB or any member thereof on behalf of the IAB,– any IETF mailing list, including the IETF list itself, any working group or design team list, or any

other list functioning under IETF auspices,– the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 5378 and RFC 3979 (updated by RFC 4879).

Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 5378 and RFC 3979 for details.

A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements.

A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public.

Page 3: 1 Yet Another Mail Working Group IETF 78 July 29, 2010

3

Pass the blue sheets around

• We have a secretary to take notes • Need a jabber channeler

Page 4: 1 Yet Another Mail Working Group IETF 78 July 29, 2010

4

Finding Yammerers

• Mailing List:– [email protected]

• Jabber:– xmpp:[email protected]

• Audio Stream:– http://videolab.uoregon.edu/events/ietf/ietf785.m3u

• Meeting Materials:– https://datatracker.ietf.org/meeting/78/

materials.html#wg-yam

• WG Wiki– http://trac.tools.ietf.org/wg/yam/trac/wiki

Page 5: 1 Yet Another Mail Working Group IETF 78 July 29, 2010

5

Agenda

• 60 minutes – 15:10 – 16:10

• Note well - 1 minute

• Agenda bashing - 4 minutes

• Mime Expert Review of image/svg+xml – 10 minutes

• Two-Track/Plenary Redux – 45 minutes

Page 6: 1 Yet Another Mail Working Group IETF 78 July 29, 2010

image/svg+xml

• Mime Expert Review

6

Page 7: 1 Yet Another Mail Working Group IETF 78 July 29, 2010

Document Status

• Since IETF 77• Pre-eval IDs published

– 4409 (submit)– 5321 (smtp) – reviewed by IESG– 5322 (format)

• Additional work sidelined by Two-Track uncertainties

7

Page 8: 1 Yet Another Mail Working Group IETF 78 July 29, 2010

8

Our WG’s Goals

• Advance documents to Full Standard– Fixing things as needed

• Process Experiment– Experiment on a way to get documents moved to

Full Standard– Act as a catalyst

Page 9: 1 Yet Another Mail Working Group IETF 78 July 29, 2010

• “If you don’t know where you are going, you could end up somewhere else.”

• – Yogi Berra

9

Page 10: 1 Yet Another Mail Working Group IETF 78 July 29, 2010

Two-Track / Plenary Redux

• draft-housley-two-maturity-levels-01– Only two levels:

• Proposed Standard • Internet Standard

– 6 month wait no longer required– Existing Draft Standards moved immediately

to Full Standard

10

Page 11: 1 Yet Another Mail Working Group IETF 78 July 29, 2010

Plenary Redux

• Lots of support for going to two levels at the plenary• Not clear where discussion will continue, when

consensus would be called, or when and how the issue would be decided

11

Page 12: 1 Yet Another Mail Working Group IETF 78 July 29, 2010

If Two-Track Goes Through…

• We’re done!

• Or are we?

12

Page 13: 1 Yet Another Mail Working Group IETF 78 July 29, 2010

If Two-Track Goes Through…

• Some of the docs really do need work to be done on them– For example,– Minor clarifications for 4409, 5321, 5322– MIME– MDN

• However, republishing a “Full Standard” doc is sometimes troublesome– Can instead get the update work done by

issuing “Update documents” instead13

Page 14: 1 Yet Another Mail Working Group IETF 78 July 29, 2010

If Two-Track Goes Through…

• Yes, if we choose to do this other type of work, it does require a recharter

• We’ve also always said that after YAM’s current charter is finished, we would then consider progressing various Proposed Standard docs forward– Is now the time?

14

Page 15: 1 Yet Another Mail Working Group IETF 78 July 29, 2010

“Conditions are never just right. People who delay action until all factors are favorable do nothing.”

– William Feather

15

Page 16: 1 Yet Another Mail Working Group IETF 78 July 29, 2010

Where are we?

• Two-Track has not been adopted yet• Should indecision there prevent work

finishing up 4409bis, 5321bis, 5322bis?– These could be finished long before we get a

decision on Two-Track– Or maybe not. How’s your crystal ball?

16

Page 17: 1 Yet Another Mail Working Group IETF 78 July 29, 2010

Open Mike

• “It is a paradoxical but profoundly true and important principle…that the most likely way to reach a goal is to be aiming not at that goal itself, but at some more ambitious goal beyond it.”

– Arnold Toynbee

“It's always too early to quit.” – Dr. Norman Vincent Peale

17