RFC 8801 on Discovering Provisioning Domain Names and Data

rfc-editor@rfc-editor.org Wed, 29 July 2020 12:42 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 A9D383A0A73; Wed, 29 Jul 2020 05:42:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.473
X-Spam-Level:
X-Spam-Status: No, score=-1.473 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.427, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 Fano_rG-Y3qU; Wed, 29 Jul 2020 05:42:38 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2291C3A0A78; Wed, 29 Jul 2020 05:42:38 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 94FF1F4071F; Wed, 29 Jul 2020 05:42:11 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg4MDEgb24gRGlzY292ZXJpbmcgUHJvdmlzaW9uaW5nIERvbWFpbiBOYW1lcyBhbmQgRGF0YQ==?=
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, int-area@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200729124211.94FF1F4071F@rfc-editor.org>
Date: Wed, 29 Jul 2020 05:42:11 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/YDf9VXj0SM9PNyQY9beOIAiUPnY>
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, 29 Jul 2020 12:42:40 -0000

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

        
        RFC 8801

        Title:      Discovering Provisioning Domain Names and 
                    Data 
        Author:     P. Pfister,
                    É. Vyncke,
                    T. Pauly,
                    D. Schinazi,
                    W. Shao
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2020
        Mailbox:    ppfister@cisco.com, 
                    evyncke@cisco.com, 
                    tpauly@apple.com,
                    dschinazi.ietf@gmail.com, 
                    wenshao@cisco.com
        Pages:      27
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-intarea-provisioning-domains-11.txt

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

        DOI:        10.17487/RFC8801

Provisioning Domains (PvDs) are defined as consistent sets of network
configuration information. PvDs allows hosts to manage connections to
multiple networks and interfaces simultaneously, such as when a home
router provides connectivity through both a broadband and cellular
network provider.

This document defines a mechanism for explicitly identifying PvDs
through a Router Advertisement (RA) option. This RA option announces
a PvD identifier, which hosts can compare to differentiate between
PvDs. The option can directly carry some information about a PvD and
can optionally point to PvD Additional Information that can be
retrieved using HTTP over TLS.

This document is a product of the Internet 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/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