On May 26, 2011 at 09:56 -0700, S Moonesamy wrote: =>This message starts a Working Group Last Call for "Message Submission for =>Mail" (draft-ietf-yam-rfc4409bis-00). The I-D can be accessed at =>http://tools.ietf.org/html/draft-ietf-yam-rfc4409bis-00
Raising hand timidly..... 1) Is it possible to insert a blank line between data rows in Table 1? I find it hard to read with each column having something wrapped at some point. For example... | PIPELINING | Pipelining | SHOULD | [PIPELINING] | | | | | | | ENHANCEDSTATUSCO | Enhanced Status | SHOULD | [CODES-EXTENSIO | | DES | Codes | | N] | | | | | | | ETRN | Extended Turn | MUST NOT | [ETRN] | | | | | | | ... | Extended Codes | SHOULD | [SMTP-CODES] | | | | | | | DSN | Delivery Status | SHOULD | [DSN] | | | Notification | | | | | | | | Maybe since the "Name" column has just one entry that wraps (ENHANCEDSTATUSCODES), it could be made one character narrower so that the "Submission" column header wouldn't wrap? (I think that you could even make it (Name) a total of 3 characters narrower which would also allow the "Reference" column to grow by two and not wrap a cell.) 2) I am not sure if a mention to RFC 6186 - Use of SRV Records for Locating Email Submission/Access Services and its section 3.1 would be appropriate in this RFC? Say, by adding something like the following to section 3.1: A site [can|SHOULD?] publish the SRV record that provides a client the site's preferred submission port [RFC6186]. -- *********************************************************************** Derek Diget Office of Information Technology Western Michigan University - Kalamazoo Michigan USA - www.wmich.edu/ *********************************************************************** _______________________________________________ yam mailing list [email protected] https://www.ietf.org/mailman/listinfo/yam
