[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [yam] WGLC is now over for draft-ietf-yam-rfc1652bis-pre-evaluation-00



Tony Hansen wrote:

The WGLC is now over for draft-ietf-yam-rfc1652bis-pre-evaluation-00.

Since there was *no* discussion about the two issues that were raised (IANA mail-parameters

If the WG reopens the document, then this should be done.
However this is not a big deal, and I can always talk directly to IANA.

and ABNF changes), no further changes should be made to the document at this point.

Agreed.

This means that we need to proceed to the next step with the document as it currently stands. And that next step is to get Alexey to schedule the document for the soonest IESG telechat.

I will be on holidays during the September 24th telechat, so it would be better for me to put the document on the next telechat after that date.

Alexey, SM has been collecting the deployment reports together that we've received so far. We'll be posting them to the wiki soon.

Sounds good to me.

If anyone has any objections to this plan, please speak up now.

    Tony Hansen
    co-chair

Tony Hansen wrote:

The WGLC ends soon. These are the only comments that have been made on draft-ietf-yam-rfc1652bis-pre-evaluation-00 before it goes to the IESG.

Any responses to these questions, or other issues to bring up?

    Tony Hansen
    tony at att.com

S Moonesamy wrote:

This is a summary of draft-ietf-yam-rfc1652bis-pre-evaluation-00 issues:

14 Aug 2009 - Tony made a comment about the IANA mail-parameters registry.

16 Aug 2009 - Tony started a discussion about a deployment report for 8BITMIME

17 Aug 2009 - Alexey proposed using the RFC 5234 syntax for ABNF

Please comment on the above. If there are any other issues (e.g. proposed changes, non-changes, etc.) or comments on the template layout or text, please post them to this mailing list.

The Working Group Last Call ends on ending on September 11.



Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.