Meeting notes from the YAM BOF, held in San Francisco on 2009-03-26.


Slides are on the meeting materials site, 

    http://www.ietf.org/proceedings/09mar/slides/yam-0.ppt  

and

    https://datatracker.ietf.org/meeting/74/materials.html#wg-yam 


Mailing list is ietf-yam@mipassoc.org

After bashing the agenda and noting well, we discussed the proposed charter and the reasons for having the working group.

The desire is to have a cooperative model with IESG, to prevent disagreements about scope during or after Last
Call.

There are also secondary goals of doing further work on protocols that need more work.

We clarified that we don't want to work on other documents not already at draft standard state until after the current batch is through, or in other working groups.

There was some bashing of the charter text; it was decided to form a design group to come up with the final wording.

The teams looking at specific documents would act similar to design teams, with most of their discussion off of the yam mailing list.



Discussion proceeded on the list of RFCs being considered

Preliminary discussion recommended that the following RFCs should move forward:

    RFC 1652 8BITMIME 
    RFC 1864 Content-MD5
    RFC 2045, 2046, 2047, 2049 MIME base specs
    RFC 3282 Content-language 
    RFC 3461 DSNs 
    RFC 3462 Multipart/Report 
    RFC 3463 Enhanced Status Codes 
    RFC 3464 Message Format for DSNs 
    RFC 4409 Message Submission 
    RFC 5321 SMTP
    RFC 5322 Internet Message Format

Preliminary discussion recommended that the following RFCs not be moved forward:

    RFC 3191 Minimal GSTN address formats 
    RFC 3192 Minimal fax addresses 
    RFC 3302 image/tiff 
    RFC 3798 Message Disposition Notification 
    RFC 3801 VPIMv2 
    RFC 3803 Content-duration 
    RFC 3949 Internet Fax file format 
    RFC 3950 image/tiff-fx 
    RFC 3964 Simple Internet fax 


One suggestion of an optimization is to try real hard to see what can be done just with errata. Others disagreed.


The question to charter or not was then raised. After discussion, a hum was held and was overwhelming in favor of chartering the WG.


Alexey Melnikov will be the sponsoring AD.

The meeting adjourned.