RFC 8799 on Limited Domains and Internet Protocols

rfc-editor@rfc-editor.org Wed, 15 July 2020 16:58 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 0DC8F3A093B for <ietf-announce@ietfa.amsl.com>; Wed, 15 Jul 2020 09:58:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id ga6wowBjL8aJ for <ietf-announce@ietfa.amsl.com>; Wed, 15 Jul 2020 09:58:04 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97A133A08F4 for <ietf-announce@ietf.org>; Wed, 15 Jul 2020 09:58:04 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6E49FF40768; Wed, 15 Jul 2020 09:58:00 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg3OTkgb24gTGltaXRlZCBEb21haW5zIGFuZCBJbnRlcm5ldCBQcm90b2NvbHM=?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
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: <20200715165800.6E49FF40768@rfc-editor.org>
Date: Wed, 15 Jul 2020 09:58:00 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/8hDa1um0GhnVIvup1I9j7wm8EsM>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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: Wed, 15 Jul 2020 16:58:07 -0000

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

        RFC 8799

        Title:      Limited Domains and Internet Protocols 
        Author:     B. Carpenter,
                    B. Liu
        Status:     Informational
        Stream:     Independent
        Date:       July 2020
        Mailbox:    brian.e.carpenter@gmail.com, 
        Pages:      23
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-carpenter-limited-domains-13.txt

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

        DOI:        10.17487/RFC8799

There is a noticeable trend towards network behaviors and semantics
that are specific to a particular set of requirements applied within
a limited region of the Internet. Policies, default parameters, the
options supported, the style of network management, and security
requirements may vary between such limited regions. This document
reviews examples of such limited domains (also known as controlled
environments), notes emerging solutions, and includes a related
taxonomy. It then briefly discusses the standardization of protocols
for limited domains. Finally, it shows the need for a precise
definition of "limited domain membership" and for mechanisms to allow
nodes to join a domain securely and to find other members, including
boundary nodes. 

This document is the product of the research of the authors. It has
been produced through discussions and consultation within the IETF
but is not the product of IETF consensus.

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

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