RFC 7505 on A "Null MX" No Service Resource Record for Domains That Accept No Mail
rfc-editor@rfc-editor.org Tue, 30 June 2015 23:36 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A910E1B2A99; Tue, 30 Jun 2015 16:36:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dSC3vpnkUqU2; Tue, 30 Jun 2015 16:36:36 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 6C79D1B2A87; Tue, 30 Jun 2015 16:36:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9B834180470; Tue, 30 Jun 2015 16:33:25 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7505 on A "Null MX" No Service Resource Record for Domains That Accept No Mail
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150630233325.9B834180470@rfc-editor.org>
Date: Tue, 30 Jun 2015 16:33:25 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/b_xVcIB-isbBqlHg8NxCmaYKWyE>
Cc: drafts-update-ref@iana.org, apps-discuss@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jun 2015 23:36:40 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7505
Title: A "Null MX" No Service
Resource Record for Domains That Accept
No Mail
Author: J. Levine, M. Delany
Status: Standards Track
Stream: IETF
Date: June 2015
Mailbox: standards@taugh.com,
mx0dot@yahoo.com
Pages: 6
Characters: 12534
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-appsawg-nullmx-10.txt
URL: https://www.rfc-editor.org/info/rfc7505
DOI: http://dx.doi.org/10.17487/RFC7505
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; this permits significant operational efficiencies.
This document is a product of the Applications Area Working Group Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC