A "Null MX" No Service Resource Record for Domains that Accept No Mail
draft-ietf-appsawg-nullmx-08

The information below is for an old version of the document
Document Type Active Internet-Draft (appsawg WG)
Authors John Levine  , Mark Delany 
Last updated 2014-09-03 (latest revision 2014-08-08)
Replaces draft-delany-nullmx
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Dave Crocker
Shepherd write-up Show (last changed 2014-07-06)
IESG IESG state RFC Ed Queue
Consensus Boilerplate Yes
Telechat date
Responsible AD Barry Leiba
Send notices to appsawg-chairs@tools.ietf.org, draft-ietf-appsawg-nullmx@tools.ietf.org, dhc@dcrocker.net
IANA IANA review state IANA OK - Actions Needed
IANA action state RFC-Ed-Ack
RFC Editor RFC Editor state EDIT
Details
Network Working Group                                          J. Levine
Internet-Draft                                      Taughannock Networks
Intended status: Standards Track                               M. Delany
Expires: February 9, 2015                                     Apple Inc.
                                                          August 8, 2014

 A "Null MX" No Service Resource Record for Domains that Accept No Mail
                      draft-ietf-appsawg-nullmx-08

Abstract

   Internet mail determines the address of a receiving server through
   the DNS, first by looking for an MX record and then by looking for an
   A/AAAA record as a fallback.  Unfortunately this means that the A/
   AAAA record is taken to be mail server address even when that address
   does not accept mail.  The no service MX RR, informally called null
   MX, formalizes the existing mechanism by which a domain announces
   that it accepts no mail, without having to provide a mail server,
   which permits significant operational efficiencies.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on February 9, 2015.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect

Levine & Delany         Expires February 9, 2015                [Page 1]
Internet-Draft                   Null MX                     August 2014

   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Conventions Used in This Document . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  MX Resource Records Specifying Null MX  . . . . . . . . . . .   3
   4.  Effects of Null MX  . . . . . . . . . . . . . . . . . . . . .   3
     4.1.  SMTP Server Benefits  . . . . . . . . . . . . . . . . . .   3
     4.2.  Sending Mail from Domains that Publish Null MX  . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .   6
     A.1.  Change to appsawg-nullmx-08 . . . . . . . . . . . . . . .   6
     A.2.  Change to appsawg-nullmx-07 . . . . . . . . . . . . . . .   6
     A.3.  Change to appsawg-nullmx-06 . . . . . . . . . . . . . . .   6
     A.4.  Change to appsawg-nullmx-05 . . . . . . . . . . . . . . .   7
     A.5.  Change to appsawg-nullmx-04 . . . . . . . . . . . . . . .   7
     A.6.  Change to appsawg-nullmx-03 . . . . . . . . . . . . . . .   7
     A.7.  Change to appsawg-nullmx-02 . . . . . . . . . . . . . . .   7
     A.8.  Change to appsawg-nullmx-1  . . . . . . . . . . . . . . .   7
     A.9.  Change to appsawg-nullmx-0  . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Conventions Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

   The terms RFC5321.MailFrom and RFC5322.From are used as defined in
   [RFC5598].

2.  Introduction

   This document defines the No Service MX, informally called null MX,
   as a simple mechanism by which a domain can indicate that it does not
   accept email.

   SMTP clients have a prescribed sequence for identifying a server that
   accepts email for a domain.  Section 5 of [RFC5321] covers this in

Levine & Delany         Expires February 9, 2015                [Page 2]
Show full document text