
From rfc-dist-bounces@rfc-editor.org  Wed Jun 10 17:30:22 2020
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A8923A0CED for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 10 Jun 2020 17:30:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 YSCeS6Goo2o2 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 10 Jun 2020 17:30:21 -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 5345F3A15CE for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 10 Jun 2020 17:30:21 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D3DE4F4075C; Wed, 10 Jun 2020 17:29:54 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 6532CF4075B; Wed, 10 Jun 2020 17:29:54 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200611002954.6532CF4075B@rfc-editor.org>
Date: Wed, 10 Jun 2020 17:29:54 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8776_on_Common_YANG_Data_Types_for_Traf?= =?utf-8?q?fic_Engineering?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, teas@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8776

        Title:      Common YANG Data Types for 
                    Traffic Engineering 
        Author:     T. Saad, 
                    R. Gandhi,
                    X. Liu,
                    V. Beeram,
                    I. Bryskin
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2020 
        Mailbox:    tsaad@juniper.net, 
                    rgandhi@cisco.com, 
                    xufeng.liu.ietf@gmail.com,
                    vbeeram@juniper.net, 
                    i_bryskin@yahoo.com
        Pages:      84
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-teas-yang-te-types-13.txt

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

        DOI:        10.17487/RFC8776

This document defines a collection of common data types and groupings
in YANG data modeling language. These derived common types and
groupings are intended to be imported by modules that model Traffic
Engineering (TE) configuration and state capabilities.

This document is a product of the Traffic Engineering Architecture and Signaling 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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Wed Jun 17 16:44:45 2020
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15BA13A0CE8 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 17 Jun 2020 16:44:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 Je94o9wsAhZ9 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 17 Jun 2020 16:44:43 -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 4EF5C3A0A24 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 17 Jun 2020 16:44:43 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id CC4CBF40713; Wed, 17 Jun 2020 16:44:37 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id EA83CF40712; Wed, 17 Jun 2020 16:44:36 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200617234436.EA83CF40712@rfc-editor.org>
Date: Wed, 17 Jun 2020 16:44:36 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8791_on_YANG_Data_Structure_Extensions?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, netmod@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

QSBuZXcgUmVxdWVzdCBmb3IgQ29tbWVudHMgaXMgbm93IGF2YWlsYWJsZSBpbiBvbmxpbmUgUkZD
IGxpYnJhcmllcy4KCiAgICAgICAgCiAgICAgICAgUkZDIDg3OTEKCiAgICAgICAgVGl0bGU6ICAg
ICAgWUFORyBEYXRhIFN0cnVjdHVyZSBFeHRlbnNpb25zIAogICAgICAgIEF1dGhvcjogICAgIEEu
IEJpZXJtYW4sIAogICAgICAgICAgICAgICAgICAgIE0uIEJqw7Zya2x1bmQsCiAgICAgICAgICAg
ICAgICAgICAgSy4gV2F0c2VuCiAgICAgICAgU3RhdHVzOiAgICAgU3RhbmRhcmRzIFRyYWNrCiAg
ICAgICAgU3RyZWFtOiAgICAgSUVURgogICAgICAgIERhdGU6ICAgICAgIEp1bmUgMjAyMAogICAg
ICAgIE1haWxib3g6ICAgIGFuZHlAeXVtYXdvcmtzLmNvbSwgCiAgICAgICAgICAgICAgICAgICAg
bWJqK2lldGZANDY2OC5zZSwgCiAgICAgICAgICAgICAgICAgICAga2VudCtpZXRmQHdhdHNlbi5u
ZXQKICAgICAgICBQYWdlczogICAgICAxNgogICAgICAgIFVwZGF0ZXM6ICAgIFJGQyA4MzQwCgog
ICAgICAgIEktRCBUYWc6ICAgIGRyYWZ0LWlldGYtbmV0bW9kLXlhbmctZGF0YS1leHQtMDUudHh0
CgogICAgICAgIFVSTDogICAgICAgIGh0dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZj
ODc5MQoKICAgICAgICBET0k6ICAgICAgICAxMC4xNzQ4Ny9SRkM4NzkxCgpUaGlzIGRvY3VtZW50
IGRlc2NyaWJlcyBZQU5HIG1lY2hhbmlzbXMgZm9yIGRlZmluaW5nIGFic3RyYWN0IGRhdGEKc3Ry
dWN0dXJlcyB3aXRoIFlBTkcuCgpUaGlzIGRvY3VtZW50IGlzIGEgcHJvZHVjdCBvZiB0aGUgTmV0
d29yayBNb2RlbGluZyBXb3JraW5nIEdyb3VwIG9mIHRoZSBJRVRGLgoKVGhpcyBpcyBub3cgYSBQ
cm9wb3NlZCBTdGFuZGFyZC4KClNUQU5EQVJEUyBUUkFDSzogVGhpcyBkb2N1bWVudCBzcGVjaWZp
ZXMgYW4gSW50ZXJuZXQgU3RhbmRhcmRzIFRyYWNrCnByb3RvY29sIGZvciB0aGUgSW50ZXJuZXQg
Y29tbXVuaXR5LCBhbmQgcmVxdWVzdHMgZGlzY3Vzc2lvbiBhbmQgc3VnZ2VzdGlvbnMKZm9yIGlt
cHJvdmVtZW50cy4gIFBsZWFzZSByZWZlciB0byB0aGUgY3VycmVudCBlZGl0aW9uIG9mIHRoZSBP
ZmZpY2lhbApJbnRlcm5ldCBQcm90b2NvbCBTdGFuZGFyZHMgKGh0dHBzOi8vd3d3LnJmYy1lZGl0
b3Iub3JnL3N0YW5kYXJkcykgZm9yIHRoZSAKc3RhbmRhcmRpemF0aW9uIHN0YXRlIGFuZCBzdGF0
dXMgb2YgdGhpcyBwcm90b2NvbC4gIERpc3RyaWJ1dGlvbiBvZiB0aGlzIAptZW1vIGlzIHVubGlt
aXRlZC4KClRoaXMgYW5ub3VuY2VtZW50IGlzIHNlbnQgdG8gdGhlIElFVEYtQW5ub3VuY2UgYW5k
IHJmYy1kaXN0IGxpc3RzLgpUbyBzdWJzY3JpYmUgb3IgdW5zdWJzY3JpYmUsIHNlZQogIGh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaWV0Zi1hbm5vdW5jZQogIGh0dHBzOi8v
bWFpbG1hbi5yZmMtZWRpdG9yLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JmYy1kaXN0CgpGb3Igc2Vh
cmNoaW5nIHRoZSBSRkMgc2VyaWVzLCBzZWUgaHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcvc2Vh
cmNoCkZvciBkb3dubG9hZGluZyBSRkNzLCBzZWUgaHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcv
cmV0cmlldmUvYnVsawoKUmVxdWVzdHMgZm9yIHNwZWNpYWwgZGlzdHJpYnV0aW9uIHNob3VsZCBi
ZSBhZGRyZXNzZWQgdG8gZWl0aGVyIHRoZQphdXRob3Igb2YgdGhlIFJGQyBpbiBxdWVzdGlvbiwg
b3IgdG8gcmZjLWVkaXRvckByZmMtZWRpdG9yLm9yZy4gIFVubGVzcwpzcGVjaWZpY2FsbHkgbm90
ZWQgb3RoZXJ3aXNlIG9uIHRoZSBSRkMgaXRzZWxmLCBhbGwgUkZDcyBhcmUgZm9yCnVubGltaXRl
ZCBkaXN0cmlidXRpb24uCgoKVGhlIFJGQyBFZGl0b3IgVGVhbQpBc3NvY2lhdGlvbiBNYW5hZ2Vt
ZW50IFNvbHV0aW9ucywgTExDCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX18KcmZjLWRpc3QgbWFpbGluZyBsaXN0CnJmYy1kaXN0QHJmYy1lZGl0b3Iub3Jn
Cmh0dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL21haWxtYW4vbGlzdGluZm8vcmZjLWRpc3QKaHR0
cDovL3d3dy5yZmMtZWRpdG9yLm9yZwo=

From rfc-dist-bounces@rfc-editor.org  Wed Jun 17 18:13:51 2020
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B0343A03F2 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 17 Jun 2020 18:13:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 LQGDfQCUWYwX for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 17 Jun 2020 18:13:49 -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 C80C23A00D6 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 17 Jun 2020 18:13:47 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 4C301F40713; Wed, 17 Jun 2020 18:13:42 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id D9037F40712; Wed, 17 Jun 2020 18:13:41 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200618011341.D9037F40712@rfc-editor.org>
Date: Wed, 17 Jun 2020 18:13:41 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8793_on_Information-Centric_Networking_?= =?utf-8?q?=28ICN=29=3A_Content-Centric_Networking_=28CCNx=29_and_Named_Da?= =?utf-8?q?ta_Networking_=28NDN=29_Terminology?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, icnrg@irtf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8793

        Title:      Information-Centric Networking (ICN): 
                    Content-Centric Networking (CCNx)
                    and Named Data Networking (NDN) 
                    Terminology 
        Author:     B. Wissingh,
                    C. Wood,
                    A. Afanasyev,
                    L. Zhang,
                    D. Oran,
                    C. Tschudin
        Status:     Informational
        Stream:     IRTF
        Date:       June 2020
        Mailbox:    bastiaan.wissingh@tno.nl, 
                    caw@heapingbits.net, 
                    aa@cs.fiu.edu,
                    lixia@cs.ucla.edu, 
                    daveoran@orandom.net,
                    christian.tschudin@unibas.ch
        Pages:      17
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-irtf-icnrg-terminology-08.txt

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

        DOI:        10.17487/RFC8793

Information-Centric Networking (ICN) is a novel paradigm where
network communications are accomplished by requesting named content
instead of sending packets to destination addresses. Named Data
Networking (NDN) and Content-Centric Networking (CCNx) are two
prominent ICN architectures. This document provides an overview of
the terminology and definitions that have been used in describing
concepts in these two implementations of ICN. While there are other
ICN architectures, they are not part of the NDN and CCNx concepts and
as such are out of scope for this document. This document is a
product of the Information-Centric Networking Research Group (ICNRG).

This document is a product of the Information-Centric Networking Research Group of the IRTF.


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, rfc-dist and IRTF-Announce lists.To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
  https://www.irtf.org/mailman/listinfo/irtf-announce

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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Wed Jun 17 18:43:40 2020
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 245713A09D6 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 17 Jun 2020 18:43:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 FSk3LdgFJzqs for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 17 Jun 2020 18:43:39 -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 2D9063A09CC for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 17 Jun 2020 18:43:39 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id A02D1F40712; Wed, 17 Jun 2020 18:43:33 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 40EEEF40711; Wed, 17 Jun 2020 18:43:32 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200618014332.40EEEF40711@rfc-editor.org>
Date: Wed, 17 Jun 2020 18:43:32 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?BCP_9=2C_RFC_8789_on_IETF_Stream_Documents_?= =?utf-8?q?Require_IETF_Rough_Consensus?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        BCP 9        
        RFC 8789

        Title:      IETF Stream Documents Require IETF 
                    Rough Consensus 
        Author:     J. Halpern, Ed.,
                    E. Rescorla, Ed.
        Status:     Best Current Practice
        Stream:     IETF
        Date:       June 2020
        Mailbox:    joel.halpern@ericsson.com, 
                    ekr@rtfm.com
        Pages:      4
        Updates:    RFC 2026
        See Also:   BCP 9

        I-D Tag:    draft-halpern-gendispatch-consensusinformational-04.txt

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

        DOI:        10.17487/RFC8789

This document requires that the IETF never publish any IETF Stream
RFCs without IETF rough consensus.  This updates RFC 2026.


BCP: 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-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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Thu Jun 18 13:59:20 2020
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA6BC3A0DD2 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 18 Jun 2020 13:59:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 mh9UAUmPKE4U for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 18 Jun 2020 13:59:19 -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 D90CB3A0F83 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 18 Jun 2020 13:59:18 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5FDE6F40721; Thu, 18 Jun 2020 13:59:12 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id F409BF40720; Thu, 18 Jun 2020 13:59:10 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200618205910.F409BF40720@rfc-editor.org>
Date: Thu, 18 Jun 2020 13:59:10 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8806_on_Running_a_Root_Server_Local_to_?= =?utf-8?q?a_Resolver?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, dnsop@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8806

        Title:      Running a Root Server Local 
                    to a Resolver 
        Author:     W. Kumari,
                    P. Hoffman
        Status:     Informational
        Stream:     IETF
        Date:       June 2020
        Mailbox:    warren@kumari.net, 
                    paul.hoffman@icann.org
        Pages:      12
        Obsoletes:  RFC 7706

        I-D Tag:    draft-ietf-dnsop-7706bis-12.txt

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

        DOI:        10.17487/RFC8806

Some DNS recursive resolvers have longer-than-desired round-trip
times to the closest DNS root server; those resolvers may have
difficulty getting responses from the root servers, such as during a
network attack. Some DNS recursive resolver operators want to prevent
snooping by third parties of requests sent to DNS root servers. In
both cases, resolvers can greatly decrease the round-trip time and
prevent observation of requests by serving a copy of the full root
zone on the same server, such as on a loopback address or in the
resolver software. This document shows how to start and maintain such
a copy of the root zone that does not cause problems for other users
of the DNS, at the cost of adding some operational fragility for the
operator.

This document obsoletes RFC 7706.

This document is a product of the Domain Name System Operations Working Group of the IETF.


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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Mon Jun 22 21:28:51 2020
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 378273A1740 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 22 Jun 2020 21:28:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 H7F3HN2amgIw for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 22 Jun 2020 21:28:48 -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 BF7683A1728 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 22 Jun 2020 21:28:48 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 840BFF40799; Mon, 22 Jun 2020 21:28:37 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 83D64F40792; Mon, 22 Jun 2020 21:28:36 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200623042836.83D64F40792@rfc-editor.org>
Date: Mon, 22 Jun 2020 21:28:36 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8764_on_Apple=27s_DNS_Long-Lived_Querie?= =?utf-8?q?s_Protocol?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8764

        Title:      Apple's DNS Long-Lived Queries Protocol 
        Author:     S. Cheshire,
                    M. Krochmal
        Status:     Informational
        Stream:     Independent
        Date:       June 2020
        Mailbox:    cheshire@apple.com, 
                    marc@apple.com
        Pages:      20
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-sekar-dns-llq-06.txt

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

        DOI:        10.17487/RFC8764

Apple's DNS Long-Lived Queries (LLQ) is a mechanism for extending the
DNS protocol to support change notification, thus allowing clients to
learn about changes to DNS data without polling the server.  From
2005 onwards, LLQ was implemented in Apple products including Mac OS
X, Bonjour for Windows, and AirPort wireless base stations.  In 2020,
the LLQ protocol was superseded by the IETF Standards Track RFC 8765,
"DNS Push Notifications", which builds on experience gained with the
LLQ protocol to create a superior replacement. 

The existing LLQ protocol deployed and used from 2005 to 2020 is
documented here to give background regarding the operational
experience that informed the development of DNS Push Notifications,
and to help facilitate a smooth transition from LLQ to DNS Push
Notifications.


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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Mon Jun 22 21:29:58 2020
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19E7A3A1755 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 22 Jun 2020 21:29:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 rppBq1c8Tl3J for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 22 Jun 2020 21:29:56 -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 76F253A17BD for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 22 Jun 2020 21:29:25 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id CAAABF4079A; Mon, 22 Jun 2020 21:29:14 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 27D0AF407A2; Mon, 22 Jun 2020 21:29:12 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200623042912.27D0AF407A2@rfc-editor.org>
Date: Mon, 22 Jun 2020 21:29:12 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8765_on_DNS_Push_Notifications?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, dnssd@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8765

        Title:      DNS Push Notifications 
        Author:     T. Pusateri,
                    S. Cheshire
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2020
        Mailbox:    pusateri@bangj.com, 
                    cheshire@apple.com
        Pages:      32
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dnssd-push-25.txt

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

        DOI:        10.17487/RFC8765

The Domain Name System (DNS) was designed to return matching records
efficiently for queries for data that are relatively static.  When
those records change frequently, DNS is still efficient at returning
the updated results when polled, as long as the polling rate is not
too high. But, there exists no mechanism for a client to be
asynchronously notified when these changes occur.  This document
defines a mechanism for a client to be notified of such changes to
DNS records, called DNS Push Notifications.

This document is a product of the Extensions for Scalable DNS Service Discovery 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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Mon Jun 22 21:30:23 2020
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E7F73A199E for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 22 Jun 2020 21:30:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 HZIOuz-0PH9S for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 22 Jun 2020 21:30:21 -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 B5C433A18D9 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 22 Jun 2020 21:29:46 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 14839F407A8; Mon, 22 Jun 2020 21:29:36 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 6B959F407A7; Mon, 22 Jun 2020 21:29:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200623042935.6B959F407A7@rfc-editor.org>
Date: Mon, 22 Jun 2020 21:29:35 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8766_on_Discovery_Proxy_for_Multicast_D?= =?utf-8?q?NS-Based_Service_Discovery?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, dnssd@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8766

        Title:      Discovery Proxy for Multicast DNS-Based 
                    Service Discovery 
        Author:     S. Cheshire
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2020
        Mailbox:    cheshire@apple.com
        Pages:      33
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dnssd-hybrid-10.txt

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

        DOI:        10.17487/RFC8766

This document specifies a network proxy that uses Multicast DNS to
automatically populate the wide-area unicast Domain Name System
namespace with records describing devices and services found on the
local link.

This document is a product of the Extensions for Scalable DNS Service Discovery 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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Thu Jun 25 11:16:51 2020
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75F753A0DA6 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 25 Jun 2020 11:16:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 ZGMm5Ft7-cLo for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 25 Jun 2020 11:16:49 -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 115873A0E0A for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 25 Jun 2020 11:16:49 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id F19DFF40710; Thu, 25 Jun 2020 11:16:34 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 588E2F4070F; Thu, 25 Jun 2020 11:16:34 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200625181634.588E2F4070F@rfc-editor.org>
Date: Thu, 25 Jun 2020 11:16:34 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8797_on_Remote_Direct_Memory_Access_-_C?= =?utf-8?q?onnection_Manager_=28RDMA-CM=29_Private_Data_for_RPC-over-RDMA_?= =?utf-8?q?Version_1?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, nfsv4@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8797

        Title:      Remote Direct Memory Access - 
                    Connection Manager (RDMA-CM) Private Data for 
                    RPC-over-RDMA Version 1 
        Author:     C. Lever
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2020
        Mailbox:    chuck.lever@oracle.com
        Pages:      12
        Updates:    RFC 8166

        I-D Tag:    draft-ietf-nfsv4-rpcrdma-cm-pvt-data-08.txt

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

        DOI:        10.17487/RFC8797

This document specifies the format of Remote Direct Memory Access -
Connection Manager (RDMA-CM) Private Data exchanged between
RPC-over-RDMA version 1 peers as part of establishing a connection.
The addition of the Private Data payload specified in this document
is an optional extension that does not alter the RPC-over-RDMA
version 1 protocol. This document updates RFC 8166.

This document is a product of the Network File System Version 4 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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Thu Jun 25 11:18:27 2020
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 446A63A0E91 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 25 Jun 2020 11:18:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 S8PP4nUgeu3V for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 25 Jun 2020 11:18:25 -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 EF0803A0EA7 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 25 Jun 2020 11:18:25 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5D38AF4070F; Thu, 25 Jun 2020 11:18:12 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 1E1DEF4070D; Thu, 25 Jun 2020 11:18:11 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200625181811.1E1DEF4070D@rfc-editor.org>
Date: Thu, 25 Jun 2020 11:18:11 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8798_on_Additional_Units_for_Sensor_Mea?= =?utf-8?q?surement_Lists_=28SenML=29?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, core@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8798

        Title:      Additional Units for Sensor Measurement 
                    Lists (SenML) 
        Author:     C. Bormann
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2020
        Mailbox:    cabo@tzi.org
        Pages:      9
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-core-senml-more-units-06.txt

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

        DOI:        10.17487/RFC8798

The Sensor Measurement Lists (SenML) media type supports the
indication of units for a quantity represented.  This short document
registers a number of additional unit names in the IANA registry for
units in SenML.  It also defines a registry for secondary units that
cannot be in SenML's main registry, as they are derived by linear
transformation from units already in that registry.

This document is a product of the Constrained RESTful Environments 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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Mon Jun 29 10:08:40 2020
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C45C3A081C for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 29 Jun 2020 10:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 scmT6cl1JmKC for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 29 Jun 2020 10:08:39 -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 3DD933A081D for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 29 Jun 2020 10:08:39 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id CBEFEF40740; Mon, 29 Jun 2020 10:08:20 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 72142F40737; Mon, 29 Jun 2020 10:08:19 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200629170819.72142F40737@rfc-editor.org>
Date: Mon, 29 Jun 2020 10:08:19 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8785_on_JSON_Canonicalization_Scheme_?= =?utf-8?b?KEpDUyk=?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8785

        Title:      JSON Canonicalization Scheme (JCS) 
        Author:     A. Rundgren,
                    B. Jordan,
                    S. Erdtman
        Status:     Informational
        Stream:     Independent
        Date:       June 2020
        Mailbox:    anders.rundgren.net@gmail.com, 
                    bret.jordan@broadcom.com, 
                    erdtman@spotify.com
        Pages:      20
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-rundgren-json-canonicalization-scheme-17.txt

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

        DOI:        10.17487/RFC8785

Cryptographic operations like hashing and signing need the data to be
expressed in an invariant format so that the operations are reliably
repeatable.  One way to address this is to create a canonical
representation of the data.  Canonicalization also permits data to be
exchanged in its original form on the "wire" while cryptographic
operations performed on the canonicalized counterpart of the data in
the producer and consumer endpoints generate consistent results. 

This document describes the JSON Canonicalization Scheme (JCS). This
specification defines how to create a canonical representation of
JSON data by building on the strict serialization methods for JSON
primitives defined by ECMAScript, constraining JSON data to the
Internet JSON (I-JSON) subset, and by using deterministic property
sorting.


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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Mon Jun 29 10:09:16 2020
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06C353A0861 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 29 Jun 2020 10:09:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 M40L40_X-Lhx for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 29 Jun 2020 10:09:14 -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 F252D3A089B for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 29 Jun 2020 10:09:13 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 1C848F40756; Mon, 29 Jun 2020 10:08:56 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 071B2F40755; Mon, 29 Jun 2020 10:08:55 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200629170855.071B2F40755@rfc-editor.org>
Date: Mon, 29 Jun 2020 10:08:55 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8792_on_Handling_Long_Lines_in_Content_?= =?utf-8?q?of_Internet-Drafts_and_RFCs?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, netmod@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8792

        Title:      Handling Long Lines in Content 
                    of Internet-Drafts and RFCs 
        Author:     K. Watsen,
                    E. Auerswald,
                    A. Farrel,
                    Q. Wu
        Status:     Informational
        Stream:     IETF
        Date:       June 2020
        Mailbox:    kent+ietf@watsen.net, 
                    auerswal@unix-ag.uni-kl.de, 
                    adrian@olddog.co.uk,
                    bill.wu@huawei.com
        Pages:      28
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-netmod-artwork-folding-12.txt

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

        DOI:        10.17487/RFC8792

This document defines two strategies for handling long lines in
width-bounded text content.  One strategy, called the "single
backslash" strategy, is based on the historical use of a single
backslash ('') character to indicate where line-folding has
occurred, with the continuation occurring with the first character
that is not a space character (' ') on the next line.  The second
strategy, called the "double backslash" strategy, extends the first
strategy by adding a second backslash character to identify where the
continuation begins and is thereby able to handle cases not supported
by the first strategy.  Both strategies use a self-describing header
enabling automated reconstitution of the original content.

This document is a product of the Network Modeling Working Group of the IETF.


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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Tue Jun 30 14:49:20 2020
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43EA93A085A for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 30 Jun 2020 14:49:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 J0mahVZg5G6J for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 30 Jun 2020 14:49:17 -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 CB4443A088F for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 30 Jun 2020 14:49:17 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 2296BF4075A; Tue, 30 Jun 2020 14:48:58 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 72E6EF40757; Tue, 30 Jun 2020 14:48:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200630214857.72E6EF40757@rfc-editor.org>
Date: Tue, 30 Jun 2020 14:48:57 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8784_on_Mixing_Preshared_Keys_in_the_In?= =?utf-8?q?ternet_Key_Exchange_Protocol_Version_2_=28IKEv2=29_for_Post-qua?= =?utf-8?q?ntum_Security?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: ipsec@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8784

        Title:      Mixing Preshared Keys in the 
                    Internet Key Exchange Protocol Version 2 
                    (IKEv2) for Post-quantum Security 
        Author:     S. Fluhrer,
                    P. Kampanakis,
                    D. McGrew,
                    V. Smyslov
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2020
        Mailbox:    sfluhrer@cisco.com, 
                    pkampana@cisco.com, 
                    mcgrew@cisco.com,
                    svan@elvis.ru
        Pages:      16
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ipsecme-qr-ikev2-11.txt

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

        DOI:        10.17487/RFC8784

The possibility of quantum computers poses a serious challenge to
cryptographic algorithms deployed widely today.  The Internet Key
Exchange Protocol Version 2 (IKEv2) is one example of a cryptosystem
that could be broken; someone storing VPN communications today could
decrypt them at a later time when a quantum computer is available. 
It is anticipated that IKEv2 will be extended to support
quantum-secure key exchange algorithms; however, that is not likely
to happen in the near term.  To address this problem before then,
this document describes an extension of IKEv2 to allow it to be
resistant to a quantum computer by using preshared keys.

This document is a product of the IP Security Maintenance and Extensions 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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Tue Jun 30 14:50:01 2020
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C97C3A0922 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 30 Jun 2020 14:50:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 t_UrkemEiMdY for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 30 Jun 2020 14:50:00 -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 A07FB3A08F9 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 30 Jun 2020 14:49:57 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 7110DF40761; Tue, 30 Jun 2020 14:49:38 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 7E28CF4075B; Tue, 30 Jun 2020 14:49:37 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200630214937.7E28CF4075B@rfc-editor.org>
Date: Tue, 30 Jun 2020 14:49:37 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8790_on_FETCH_and_PATCH_with_Sensor_Mea?= =?utf-8?q?surement_Lists_=28SenML=29?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, core@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

QSBuZXcgUmVxdWVzdCBmb3IgQ29tbWVudHMgaXMgbm93IGF2YWlsYWJsZSBpbiBvbmxpbmUgUkZD
IGxpYnJhcmllcy4KCiAgICAgICAgCiAgICAgICAgUkZDIDg3OTAKCiAgICAgICAgVGl0bGU6ICAg
ICAgRkVUQ0ggYW5kIFBBVENIIHdpdGggU2Vuc29yIAogICAgICAgICAgICAgICAgICAgIE1lYXN1
cmVtZW50IExpc3RzIChTZW5NTCkgCiAgICAgICAgQXV0aG9yOiAgICAgQS4gS2Vyw6RuZW4sCiAg
ICAgICAgICAgICAgICAgICAgTS4gTW9oYWplcgogICAgICAgIFN0YXR1czogICAgIFN0YW5kYXJk
cyBUcmFjawogICAgICAgIFN0cmVhbTogICAgIElFVEYKICAgICAgICBEYXRlOiAgICAgICBKdW5l
IDIwMjAKICAgICAgICBNYWlsYm94OiAgICBhcmkua2VyYW5lbkBlcmljc3Nvbi5jb20sIAogICAg
ICAgICAgICAgICAgICAgIG1vamFubUBob3RtYWlsLmNvbQogICAgICAgIFBhZ2VzOiAgICAgIDEx
CiAgICAgICAgVXBkYXRlcy9PYnNvbGV0ZXMvU2VlQWxzbzogICBOb25lCgogICAgICAgIEktRCBU
YWc6ICAgIGRyYWZ0LWlldGYtY29yZS1zZW5tbC1ldGNoLTA3LnR4dAoKICAgICAgICBVUkw6ICAg
ICAgICBodHRwczovL3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZvL3JmYzg3OTAKCiAgICAgICAgRE9J
OiAgICAgICAgMTAuMTc0ODcvUkZDODc5MAoKVGhlIFNlbnNvciBNZWFzdXJlbWVudCBMaXN0cyAo
U2VuTUwpIG1lZGlhIHR5cGUgYW5kIGRhdGEgbW9kZWwgY2FuIGJlCnVzZWQgdG8gc2VuZCBjb2xs
ZWN0aW9ucyBvZiByZXNvdXJjZXMsIHN1Y2ggYXMgYmF0Y2hlcyBvZiBzZW5zb3IgZGF0YQpvciBj
b25maWd1cmF0aW9uIHBhcmFtZXRlcnMuIFRoZSBDb25zdHJhaW5lZCBBcHBsaWNhdGlvbiBQcm90
b2NvbAooQ29BUCkgRkVUQ0gsIFBBVENILCBhbmQgaVBBVENIIG1ldGhvZHMgZW5hYmxlIGFjY2Vz
c2luZyBhbmQgdXBkYXRpbmcKcGFydHMgb2YgYSByZXNvdXJjZSBvciBtdWx0aXBsZSByZXNvdXJj
ZXMgd2l0aCBvbmUgcmVxdWVzdC4gVGhpcwpkb2N1bWVudCBkZWZpbmVzIG5ldyBtZWRpYSB0eXBl
cyBmb3IgdGhlIENvQVAgRkVUQ0gsIFBBVENILCBhbmQKaVBBVENIIG1ldGhvZHMgZm9yIHJlc291
cmNlcyByZXByZXNlbnRlZCB1c2luZyB0aGUgU2VuTUwgZGF0YSBtb2RlbC4KClRoaXMgZG9jdW1l
bnQgaXMgYSBwcm9kdWN0IG9mIHRoZSBDb25zdHJhaW5lZCBSRVNUZnVsIEVudmlyb25tZW50cyBX
b3JraW5nIEdyb3VwIG9mIHRoZSBJRVRGLgoKVGhpcyBpcyBub3cgYSBQcm9wb3NlZCBTdGFuZGFy
ZC4KClNUQU5EQVJEUyBUUkFDSzogVGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgYW4gSW50ZXJuZXQg
U3RhbmRhcmRzIFRyYWNrCnByb3RvY29sIGZvciB0aGUgSW50ZXJuZXQgY29tbXVuaXR5LCBhbmQg
cmVxdWVzdHMgZGlzY3Vzc2lvbiBhbmQgc3VnZ2VzdGlvbnMKZm9yIGltcHJvdmVtZW50cy4gIFBs
ZWFzZSByZWZlciB0byB0aGUgY3VycmVudCBlZGl0aW9uIG9mIHRoZSBPZmZpY2lhbApJbnRlcm5l
dCBQcm90b2NvbCBTdGFuZGFyZHMgKGh0dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL3N0YW5kYXJk
cykgZm9yIHRoZSAKc3RhbmRhcmRpemF0aW9uIHN0YXRlIGFuZCBzdGF0dXMgb2YgdGhpcyBwcm90
b2NvbC4gIERpc3RyaWJ1dGlvbiBvZiB0aGlzIAptZW1vIGlzIHVubGltaXRlZC4KClRoaXMgYW5u
b3VuY2VtZW50IGlzIHNlbnQgdG8gdGhlIElFVEYtQW5ub3VuY2UgYW5kIHJmYy1kaXN0IGxpc3Rz
LgpUbyBzdWJzY3JpYmUgb3IgdW5zdWJzY3JpYmUsIHNlZQogIGh0dHBzOi8vd3d3LmlldGYub3Jn
L21haWxtYW4vbGlzdGluZm8vaWV0Zi1hbm5vdW5jZQogIGh0dHBzOi8vbWFpbG1hbi5yZmMtZWRp
dG9yLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JmYy1kaXN0CgpGb3Igc2VhcmNoaW5nIHRoZSBSRkMg
c2VyaWVzLCBzZWUgaHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcvc2VhcmNoCkZvciBkb3dubG9h
ZGluZyBSRkNzLCBzZWUgaHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcvcmV0cmlldmUvYnVsawoK
UmVxdWVzdHMgZm9yIHNwZWNpYWwgZGlzdHJpYnV0aW9uIHNob3VsZCBiZSBhZGRyZXNzZWQgdG8g
ZWl0aGVyIHRoZQphdXRob3Igb2YgdGhlIFJGQyBpbiBxdWVzdGlvbiwgb3IgdG8gcmZjLWVkaXRv
ckByZmMtZWRpdG9yLm9yZy4gIFVubGVzcwpzcGVjaWZpY2FsbHkgbm90ZWQgb3RoZXJ3aXNlIG9u
IHRoZSBSRkMgaXRzZWxmLCBhbGwgUkZDcyBhcmUgZm9yCnVubGltaXRlZCBkaXN0cmlidXRpb24u
CgoKVGhlIFJGQyBFZGl0b3IgVGVhbQpBc3NvY2lhdGlvbiBNYW5hZ2VtZW50IFNvbHV0aW9ucywg
TExDCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcmZj
LWRpc3QgbWFpbGluZyBsaXN0CnJmYy1kaXN0QHJmYy1lZGl0b3Iub3JnCmh0dHBzOi8vd3d3LnJm
Yy1lZGl0b3Iub3JnL21haWxtYW4vbGlzdGluZm8vcmZjLWRpc3QKaHR0cDovL3d3dy5yZmMtZWRp
dG9yLm9yZwo=

From rfc-dist-bounces@rfc-editor.org  Tue Jun 30 14:58:56 2020
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37E493A0895 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 30 Jun 2020 14:58:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 YH-kO0D3hd02 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 30 Jun 2020 14:58:55 -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 20D113A08A5 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 30 Jun 2020 14:58:55 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 52969F4075A; Tue, 30 Jun 2020 14:58:35 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 3A8F7F40754; Tue, 30 Jun 2020 14:58:34 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200630215834.3A8F7F40754@rfc-editor.org>
Date: Tue, 30 Jun 2020 14:58:34 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?BCP_190=2C_RFC_8820_on_URI_Design_and_Owner?= =?utf-8?q?ship?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        BCP 190        
        RFC 8820

        Title:      URI Design and Ownership 
        Author:     M. Nottingham
        Status:     Best Current Practice
        Stream:     IETF
        Date:       June 2020
        Mailbox:    mnot@mnot.net
        Pages:      8
        Obsoletes:  RFC 7320
        Updates:    RFC 3986
        See Also:   BCP 190

        I-D Tag:    draft-nottingham-rfc7320bis-03.txt

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

        DOI:        10.17487/RFC8820

Section 1.1.1 of RFC 3986 defines URI syntax as "a federated and
extensible naming system wherein each scheme's specification may
further restrict the syntax and semantics of identifiers using that
scheme."  In other words, the structure of a URI is defined by its
scheme. While it is common for schemes to further delegate their
substructure to the URI's owner, publishing independent standards
that mandate particular forms of substructure in URIs is often
problematic.

This document provides guidance on the specification of URI
substructure in standards.

This document obsoletes RFC 7320 and updates RFC 3986.


BCP: 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-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


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org
