BCP 105, RFC 4085 on Embedding Globally-Routable Internet Addresses Considered Harmful

rfc-editor@rfc-editor.org Fri, 10 June 2005 17:06 UTC

Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dgmxy-0003lm-3i; Fri, 10 Jun 2005 13:06:46 -0400
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dgmxw-0003lh-Ex for ietf-announce@megatron.ietf.org; Fri, 10 Jun 2005 13:06:44 -0400
Received: from ietf-mx.ietf.org (ietf-mx []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09069 for <ietf-announce@ietf.org>; Fri, 10 Jun 2005 13:06:41 -0400 (EDT)
Received: from boreas.isi.edu ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DgnJe-0007lb-8H for ietf-announce@ietf.org; Fri, 10 Jun 2005 13:29:10 -0400
Received: from ISI.EDU (adma.isi.edu []) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j5AH5bL20230; Fri, 10 Jun 2005 10:05:37 -0700 (PDT)
Message-Id: <200506101705.j5AH5bL20230@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 10 Jun 2005 10:05:37 -0700
X-ISI-4-39-6-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2
Cc: grow@lists.uoregon.edu, rfc-editor@rfc-editor.org
Subject: BCP 105, RFC 4085 on Embedding Globally-Routable Internet Addresses Considered Harmful
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

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

        BCP 105
        RFC 4085

        Title:      Embedding Globally-Routable Internet Addresses
                    Considered Harmful
        Author(s):  D. Plonka
        Status:     Best Current Practice
        Date:       June 2005
        Mailbox:    plonka@doit.wisc.edu
        Pages:      10
        Characters: 22656
        SeeAlso:    BCP0105

        I-D Tag:    draft-ietf-grow-embed-addr-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4085.txt

This document discourages the practice of embedding references to
unique, globally-routable IP addresses in Internet hosts, describes
some of the resulting problems, and considers selected alternatives.
This document is intended to clarify best current practices in this

This document is a product of the Global Routing Operations Working
Group of the IETF.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
IETF-Announce mailing list