[rfc-dist] RFC 9121 on Deprecating Infrastructure "int" Domains

rfc-editor@rfc-editor.org Fri, 28 April 2023 21:17 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9695C14CE24; Fri, 28 Apr 2023 14:17:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.948
X-Spam-Level:
X-Spam-Status: No, score=-3.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gCRA85bLktfg; Fri, 28 Apr 2023 14:17:26 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C56FC1516EB; Fri, 28 Apr 2023 14:17:26 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 123A755F69; Fri, 28 Apr 2023 14:17:26 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230428211726.123A755F69@rfcpa.amsl.com>
Date: Fri, 28 Apr 2023 14:17:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/NG1WT122dJwOlPXl1ch1biUiLtY>
Subject: [rfc-dist] RFC 9121 on Deprecating Infrastructure "int" Domains
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2023 21:17:29 -0000

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

        
        RFC 9121

        Title:      Deprecating Infrastructure "int" Domains 
        Author:     K. Davies,
                    A. Baber
        Status:     Informational
        Stream:     IETF
        Date:       April 2023
        Mailbox:    kim.davies@iana.org,
                    amanda.baber@iana.org
        Pages:      6
        Obsoletes:  RFC 1528
        Updates:    RFC 1706

        I-D Tag:    draft-davies-int-historic-05.txt

        URL:        https://www.rfc-editor.org/info/rfc9121

        DOI:        10.17487/RFC9121

This document deprecates the use of any "int" domain names that were
designated for infrastructure purposes by the IETF, and it identifies
them for removal from the "int" top-level domain.  Any
implementations that involve these domains are now deprecated.  This
document also changes the status of RFC 1528 and RFC 1706 to
Historic.


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
  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/retrieve/bulk

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