Use of SRV Records for Locating Email Submission/Access Services
RFC 6186

Note: This ballot was opened for revision 05 and is now closed.

(Alexey Melnikov) Yes

(Peter Saint-Andre) Yes

Comment (2010-05-03 for -)
No email
send info
In Section 3.4, I suggest changing "lower priority value" to "smaller priority value" so that implementers are not confused by the fact that the "preferred" service has a "lower" priority. (In RFC 2782 this is called the "lowest-numbered priority".)

(Ron Bonica) No Objection

(Stewart Bryant) No Objection

Comment (2010-05-06 for -)
No email
send info
There seems to be no definition of SRV in the draft, nor is it immediately apparent in the draft which reference to look up to find the definition.

(Gonzalo Camarillo) No Objection

(Adrian Farrel) No Objection

(David Harrington) (was Discuss, No Objection, Discuss, No Objection) No Objection

Comment (2010-06-16)
No email
send info
in section 6, "transport layer security" is a MUST; is this TLS, and if so, then should there be a reference to the TLS standard? or is any transport layer security mechanism good enough to meet the MUST?

(Russ Housley) No Objection

(Dan Romascanu) No Objection

(Robert Sparks) (was Discuss) No Objection

(Sean Turner) (was Discuss) No Objection