Keith Moore

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages) This biography of a living person relies too much on references to primary sources. Please help by adding secondary or tertiary sources. Contentious material about living persons that is unsourced or poorly sourced must be removed immediately, especially if potentially libelous or harmful. Find sources: "Keith Moore" – news · newspapers · books · scholar · JSTOR (February 2010) (Learn how and when to remove this template message) This article includes a list of general references, but it lacks sufficient corresponding inline citations. Please help to improve this article by introducing more precise citations. (February 2010) (Learn how and when to remove this template message) This poorly sourced must be removed immediately from the article and its talk page, especially if potentially libelous. Find sources: "Keith Moore" – news · newspapers · books · scholar · JSTOR (February 2010) (Learn how and when to remove this template message ) (Learn how and when to remove this template message)

Keith Moore (born 12 October 1960) is the author and co-author of several

• RFC 1870, defining a mechanism to allow SMTP clients and servers to avoid transferring messages so large that they will be rejected;
• RFC 2017, defining a (rarely implemented) means to allow MIME messages to contain attachments whose actual contents are referenced by a
  URL
  ;
• RFC 2047 amended by RFC 2231, defining a mechanism to allow non-ASCII characters to be encoded in text portions of a message header (but not in email addresses);
• RFC 3461 obsoleting RFC 1891,
• RFC 3463 obsoleting RFC 1893,
• RFC 3464 obsoleting RFC 1894, which together define a standard mechanism for reporting of delivery failures or successes in Internet email,
• RFC 3834, standards for processes that automatically respond to electronic mail; and
• RFC 8314, recommending the use of TLS for email submission and access, and the deprecation of cleartext versions of the protocols used for those purposes.^[1]

He has also written or co-written RFCs on other topics, including

• RFC 2964, Use of
  cookies
  " to address privacy concerns);
• RFC 3205, On the use of HTTP as a Substrate (discussing the use of HTTP as a layer underneath other protocols); and
• RFC 3056, describing the
  IPv4
  network.