RFC 7043 on Resource Records for EUI-48 and EUI-64 Addresses in the DNS

rfc-editor@rfc-editor.org Wed, 23 October 2013 22:00 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 332CC11E83AE for <ietf-announce@ietfa.amsl.com>; Wed, 23 Oct 2013 15:00:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.411
X-Spam-Level:
X-Spam-Status: No, score=-102.411 tagged_above=-999 required=5 tests=[AWL=0.189, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jRIq-KNa58Gs for <ietf-announce@ietfa.amsl.com>; Wed, 23 Oct 2013 15:00:48 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 4F03511E82E5 for <ietf-announce@ietf.org>; Wed, 23 Oct 2013 15:00:44 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7096F75E017; Wed, 23 Oct 2013 14:52:07 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7043 on Resource Records for EUI-48 and EUI-64 Addresses in the DNS
From: rfc-editor@rfc-editor.org
Message-Id: <20131023215207.7096F75E017@rfc-editor.org>
Date: Wed, 23 Oct 2013 14:52:07 -0700
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Wed, 23 Oct 2013 22:00:49 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7043

        Title:      Resource Records for EUI-48 and 
                    EUI-64 Addresses in the DNS 
        Author:     J. Abley
        Status:     Informational
        Stream:     IETF
        Date:       October 2013
        Mailbox:    jabley@dyn.com
        Pages:      8
        Characters: 15504
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-jabley-dnsext-eui48-eui64-rrtypes-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7043.txt

48-bit Extended Unique Identifier (EUI-48) and 64-bit Extended Unique
Identifier (EUI-64) are address formats specified by the IEEE for use
in various layer-2 networks, e.g., Ethernet.

This document describes two new DNS resource record types, EUI48 and
EUI64, for encoding Ethernet addresses in the DNS.

This document describes potentially severe privacy implications
resulting from indiscriminate publication of link-layer addresses in
the DNS.  EUI-48 or EUI-64 addresses SHOULD NOT be published in the
public DNS.  This document specifies an interoperable encoding of
these address types for use in private DNS namespaces, where the
privacy concerns can be constrained and mitigated.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://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