
From rfc-dist-bounces@rfc-editor.org  Fri Oct  9 15:08: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 6496C3A15BF for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  9 Oct 2020 15:08: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 rObS1R_ngsMY for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  9 Oct 2020 15:08:13 -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 4B0543A1597 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri,  9 Oct 2020 15:08:13 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 97302F406CA; Fri,  9 Oct 2020 15:07: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 41A1DF406C9; Fri,  9 Oct 2020 15:07: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: <20201009220757.41A1DF406C9@rfc-editor.org>
Date: Fri,  9 Oct 2020 15:07:57 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8885_on_Proxy_Mobile_IPv6_Extensions_fo?= =?utf-8?q?r_Distributed_Mobility_Management?=
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, dmm@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
IGxpYnJhcmllcy4KCiAgICAgICAgCiAgICAgICAgUkZDIDg4ODUKCiAgICAgICAgVGl0bGU6ICAg
ICAgUHJveHkgTW9iaWxlIElQdjYgRXh0ZW5zaW9ucyBmb3IgCiAgICAgICAgICAgICAgICAgICAg
RGlzdHJpYnV0ZWQgTW9iaWxpdHkgTWFuYWdlbWVudCAKICAgICAgICBBdXRob3I6ICAgICBDSi4g
QmVybmFyZG9zLAogICAgICAgICAgICAgICAgICAgIEEuIGRlIGxhIE9saXZhLAogICAgICAgICAg
ICAgICAgICAgIEYuIEdpdXN0LAogICAgICAgICAgICAgICAgICAgIEpDLiBaw7rDsWlnYSwKICAg
ICAgICAgICAgICAgICAgICBBLiBNb3VyYWQKICAgICAgICBTdGF0dXM6ICAgICBFeHBlcmltZW50
YWwKICAgICAgICBTdHJlYW06ICAgICBJRVRGCiAgICAgICAgRGF0ZTogICAgICAgT2N0b2JlciAy
MDIwCiAgICAgICAgTWFpbGJveDogICAgY2piY0BpdC51YzNtLmVzLCAKICAgICAgICAgICAgICAg
ICAgICBhb2xpdmFAaXQudWMzbS5lcywgCiAgICAgICAgICAgICAgICAgICAgZmFiaW8uZ2l1c3Qu
cmVzZWFyY2hAZ21haWwuY29tLAogICAgICAgICAgICAgICAgICAgIGouYy56dW5pZ2FAaWVlZS5v
cmcsIAogICAgICAgICAgICAgICAgICAgIGFsYWluLm1vdXJhZEBpbnRlcmRpZ2l0YWwuY29tCiAg
ICAgICAgUGFnZXM6ICAgICAgMjUKICAgICAgICBVcGRhdGVzL09ic29sZXRlcy9TZWVBbHNvOiAg
IE5vbmUKCiAgICAgICAgSS1EIFRhZzogICAgZHJhZnQtaWV0Zi1kbW0tcG1pcHY2LWRsaWYtMDYu
dHh0CgogICAgICAgIFVSTDogICAgICAgIGh0dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8v
cmZjODg4NQoKICAgICAgICBET0k6ICAgICAgICAxMC4xNzQ4Ny9SRkM4ODg1CgpEaXN0cmlidXRl
ZCBNb2JpbGl0eSBNYW5hZ2VtZW50IHNvbHV0aW9ucyBhbGxvdyBuZXR3b3JrcyB0byBiZSBzZXQg
dXAKaW4gc3VjaCBhIHdheSB0aGF0IHRyYWZmaWMgaXMgZGlzdHJpYnV0ZWQgb3B0aW1hbGx5IGFu
ZCBjZW50cmFsbHkKZGVwbG95ZWQgYW5jaG9ycyBhcmUgbm90IHJlbGllZCB1cG9uIHRvIHByb3Zp
ZGUgSVAgbW9iaWxpdHkgc3VwcG9ydC4gCgpUaGVyZSBhcmUgbWFueSBkaWZmZXJlbnQgYXBwcm9h
Y2hlcyB0byBhZGRyZXNzIERpc3RyaWJ1dGVkIE1vYmlsaXR5Ck1hbmFnZW1lbnQgLS0gZm9yIGV4
YW1wbGUsIGV4dGVuZGluZyBuZXR3b3JrLWJhc2VkIG1vYmlsaXR5IHByb3RvY29scwoobGlrZSBQ
cm94eSBNb2JpbGUgSVB2Nikgb3IgY2xpZW50LWJhc2VkIG1vYmlsaXR5IHByb3RvY29scyAobGlr
ZQpNb2JpbGUgSVB2NiksIGFtb25nIG90aGVycy4gVGhpcyBkb2N1bWVudCBmb2xsb3dzIHRoZSBm
b3JtZXIgYXBwcm9hY2gKYW5kIHByb3Bvc2VzIGEgc29sdXRpb24gYmFzZWQgb24gUHJveHkgTW9i
aWxlIElQdjYsIGluIHdoaWNoIG1vYmlsaXR5CnNlc3Npb25zIGFyZSBhbmNob3JlZCBhdCB0aGUg
bGFzdCBJUCBob3Agcm91dGVyIChjYWxsZWQgdGhlIG1vYmlsaXR5CmFuY2hvciBhbmQgYWNjZXNz
IHJvdXRlcikuIFRoZSBtb2JpbGl0eSBhbmNob3IgYW5kIGFjY2VzcyByb3V0ZXIgaXMKYW4gZW5o
YW5jZWQgYWNjZXNzIHJvdXRlciB0aGF0IGlzIGFsc28gYWJsZSB0byBvcGVyYXRlIGFzIGEgbG9j
YWwKbW9iaWxpdHkgYW5jaG9yIG9yIG1vYmlsaXR5IGFjY2VzcyBnYXRld2F5IG9uIGEgcGVyLXBy
ZWZpeCBiYXNpcy4gVGhlCmRvY3VtZW50IGZvY3VzZXMgb24gdGhlIHJlcXVpcmVkIGV4dGVuc2lv
bnMgdG8gZWZmZWN0aXZlbHkgc3VwcG9ydAp0aGUgc2ltdWx0YW5lb3VzIGFuY2hvcmluZyBzZXZl
cmFsIGZsb3dzIGF0IGRpZmZlcmVudCBkaXN0cmlidXRlZApnYXRld2F5cy4KClRoaXMgZG9jdW1l
bnQgaXMgYSBwcm9kdWN0IG9mIHRoZSBEaXN0cmlidXRlZCBNb2JpbGl0eSBNYW5hZ2VtZW50IFdv
cmtpbmcgR3JvdXAgb2YgdGhlIElFVEYuCgoKRVhQRVJJTUVOVEFMOiBUaGlzIG1lbW8gZGVmaW5l
cyBhbiBFeHBlcmltZW50YWwgUHJvdG9jb2wgZm9yIHRoZQpJbnRlcm5ldCBjb21tdW5pdHkuICBJ
dCBkb2VzIG5vdCBzcGVjaWZ5IGFuIEludGVybmV0IHN0YW5kYXJkIG9mIGFueQpraW5kLiBEaXNj
dXNzaW9uIGFuZCBzdWdnZXN0aW9ucyBmb3IgaW1wcm92ZW1lbnQgYXJlIHJlcXVlc3RlZC4KRGlz
dHJpYnV0aW9uIG9mIHRoaXMgbWVtbyBpcyB1bmxpbWl0ZWQuCgpUaGlzIGFubm91bmNlbWVudCBp
cyBzZW50IHRvIHRoZSBJRVRGLUFubm91bmNlIGFuZCByZmMtZGlzdCBsaXN0cy4KVG8gc3Vic2Ny
aWJlIG9yIHVuc3Vic2NyaWJlLCBzZWUKICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL2lldGYtYW5ub3VuY2UKICBodHRwczovL21haWxtYW4ucmZjLWVkaXRvci5vcmcvbWFp
bG1hbi9saXN0aW5mby9yZmMtZGlzdAoKRm9yIHNlYXJjaGluZyB0aGUgUkZDIHNlcmllcywgc2Vl
IGh0dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL3NlYXJjaApGb3IgZG93bmxvYWRpbmcgUkZDcywg
c2VlIGh0dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL3JldHJpZXZlL2J1bGsKClJlcXVlc3RzIGZv
ciBzcGVjaWFsIGRpc3RyaWJ1dGlvbiBzaG91bGQgYmUgYWRkcmVzc2VkIHRvIGVpdGhlciB0aGUK
YXV0aG9yIG9mIHRoZSBSRkMgaW4gcXVlc3Rpb24sIG9yIHRvIHJmYy1lZGl0b3JAcmZjLWVkaXRv
ci5vcmcuICBVbmxlc3MKc3BlY2lmaWNhbGx5IG5vdGVkIG90aGVyd2lzZSBvbiB0aGUgUkZDIGl0
c2VsZiwgYWxsIFJGQ3MgYXJlIGZvcgp1bmxpbWl0ZWQgZGlzdHJpYnV0aW9uLgoKClRoZSBSRkMg
RWRpdG9yIFRlYW0KQXNzb2NpYXRpb24gTWFuYWdlbWVudCBTb2x1dGlvbnMsIExMQwoKCl9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCnJmYy1kaXN0IG1haWxp
bmcgbGlzdApyZmMtZGlzdEByZmMtZWRpdG9yLm9yZwpodHRwczovL3d3dy5yZmMtZWRpdG9yLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL3JmYy1kaXN0Cmh0dHA6Ly93d3cucmZjLWVkaXRvci5vcmcK

From rfc-dist-bounces@rfc-editor.org  Fri Oct  9 15:28:26 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 6B8C43A1569 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  9 Oct 2020 15:28:26 -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 BF4wrlSaaYDu for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  9 Oct 2020 15:28: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 14B903A0EDB for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri,  9 Oct 2020 15:28:25 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 57881F406D8; Fri,  9 Oct 2020 15:28:10 -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 659F8F406D5; Fri,  9 Oct 2020 15:28:09 -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: <20201009222809.659F8F406D5@rfc-editor.org>
Date: Fri,  9 Oct 2020 15:28:09 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8933_on_Update_to_the_Cryptographic_Mes?= =?utf-8?q?sage_Syntax_=28CMS=29_for_Algorithm_Identifier_Protection?=
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: spasm@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 8933

        Title:      Update to the Cryptographic Message 
                    Syntax (CMS) for Algorithm Identifier Protection 
        Author:     R. Housley
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2020
        Mailbox:    housley@vigilsec.com
        Pages:      8
        Updates:    RFC 5652

        I-D Tag:    draft-ietf-lamps-cms-update-alg-id-protect-05.txt

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

        DOI:        10.17487/RFC8933

This document updates the Cryptographic Message Syntax (CMS)
specified in RFC 5652 to ensure that algorithm identifiers in
signed-data and authenticated-data content types are adequately
protected.

This document is a product of the Limited Additional Mechanisms for PKIX and SMIME 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  Fri Oct  9 16:47:41 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 0736E3A1649 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  9 Oct 2020 16:47:41 -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 gKNFY_9LjYp2 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  9 Oct 2020 16:47: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 C22343A1640 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri,  9 Oct 2020 16:47:36 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id ED7D3F406C3; Fri,  9 Oct 2020 16:47:21 -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 DD8D1F406C3; Fri,  9 Oct 2020 16:47:20 -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: <20201009234720.DD8D1F406C3@rfc-editor.org>
Date: Fri,  9 Oct 2020 16:47:20 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8924_on_Service_Function_Chaining_=28SF?= =?utf-8?q?C=29_Operations=2C_Administration=2C_and_Maintenance_=28OAM=29_?= =?utf-8?q?Framework?=
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, sfc@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 8924

        Title:      Service Function Chaining (SFC) Operations, 
                    Administration, and Maintenance (OAM) Framework 
        Author:     S. Aldrin, 
                    C. Pignataro, Ed.,
                    N. Kumar, Ed.,
                    R. Krishnan,
                    A. Ghanwani
        Status:     Informational
        Stream:     IETF
        Date:       October 2020
        Mailbox:    aldrin.ietf@gmail.com, 
                    cpignata@cisco.com, 
                    naikumar@cisco.com,
                    ramkri123@gmail.com, 
                    anoop@alumni.duke.edu
        Pages:      20
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sfc-oam-framework-15.txt

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

        DOI:        10.17487/RFC8924

This document provides a reference framework for Operations,
Administration, and Maintenance (OAM) for Service Function Chaining
(SFC).

This document is a product of the Service Function Chaining 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  Sat Oct 17 05:34:10 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 5F0623A0AD8 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sat, 17 Oct 2020 05:34:10 -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 EtYspbux_gtJ for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sat, 17 Oct 2020 05:34:07 -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 BAB663A0AE8 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Sat, 17 Oct 2020 05:34:07 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D1C81F406F7; Sat, 17 Oct 2020 05:33:44 -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 7F563F406F4; Sat, 17 Oct 2020 05:33:43 -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: <20201017123343.7F563F406F4@rfc-editor.org>
Date: Sat, 17 Oct 2020 05:33:43 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8937_on_Randomness_Improvements_for_Sec?= =?utf-8?q?urity_Protocols?=
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, cfrg@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 8937

        Title:      Randomness Improvements for Security Protocols 
        Author:     C. Cremers, 
                    L. Garratt,
                    S. Smyshlyaev,
                    N. Sullivan,
                    C. Wood
        Status:     Informational
        Stream:     IRTF
        Date:       October 2020
        Mailbox:    cremers@cispa.saarland, 
                    lgarratt@cisco.com, 
                    svs@cryptopro.ru,
                    nick@cloudflare.com, 
                    caw@heapingbits.net
        Pages:      9
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-irtf-cfrg-randomness-improvements-14.txt

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

        DOI:        10.17487/RFC8937

Randomness is a crucial ingredient for Transport Layer Security (TLS)
and related security protocols.  Weak or predictable
"cryptographically secure" pseudorandom number generators (CSPRNGs)
can be abused or exploited for malicious purposes. An initial entropy
source that seeds a CSPRNG might be weak or broken as well, which can
also lead to critical and systemic security problems. This document
describes a way for security protocol implementations to augment
their CSPRNGs using long-term private keys. This improves randomness
from broken or otherwise subverted CSPRNGs.

This document is a product of the Crypto Forum Research Group (CFRG)
in 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  Sat Oct 17 05:53:25 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 982C13A0B1D for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sat, 17 Oct 2020 05:53:25 -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 CI2VT3gA5pGH for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sat, 17 Oct 2020 05:53:23 -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 7A55E3A0B1A for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Sat, 17 Oct 2020 05:53:23 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 93E85F40712; Sat, 17 Oct 2020 05:53:00 -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 02DF3F40710; Sat, 17 Oct 2020 05:53:00 -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: <20201017125300.02DF3F40710@rfc-editor.org>
Date: Sat, 17 Oct 2020 05:53:00 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8925_on_IPv6-Only_Preferred_Option_for_?= =?utf-8?q?DHCPv4?=
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, dhcwg@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 8925

        Title:      IPv6-Only Preferred Option for DHCPv4 
        Author:     L. Colitti,
                    J. Linkova,
                    M. Richardson,
                    T. Mrugalski
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2020
        Mailbox:    lorenzo@google.com, 
                    furry@google.com, 
                    mcr+ietf@sandelman.ca,
                    tomasz.mrugalski@gmail.com
        Pages:      12
        Updates:    RFC 2563

        I-D Tag:    draft-ietf-dhc-v6only-08.txt

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

        DOI:        10.17487/RFC8925

This document specifies a DHCPv4 option to indicate that a host
supports an IPv6-only mode and is willing to forgo obtaining an IPv4
address if the network provides IPv6 connectivity. It also updates
RFC 2563 to specify DHCPv4 server behavior when the server receives a
DHCPDISCOVER not containing the Auto-Configure option but containing
the new option defined in this document.

This document is a product of the Dynamic Host Configuration 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 Oct 19 12:48:26 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 35C653A083B for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 19 Oct 2020 12:48:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level:
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[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 oDUDImp0th_8 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 19 Oct 2020 12:48: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 C88B93A0855 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 19 Oct 2020 12:48:24 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id B8CC3F4071F; Mon, 19 Oct 2020 12:48:21 -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 3FA0CF4071E; Mon, 19 Oct 2020 12:48:20 -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: <20201019194820.3FA0CF4071E@rfc-editor.org>
Date: Mon, 19 Oct 2020 12:48:20 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8818_on_Distributed_Mobility_Anchoring?=
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, dmm@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 8818

        Title:      Distributed Mobility Anchoring 
        Author:     H. Chan, Ed.,
                    X. Wei,
                    J. Lee,
                    S. Jeon,
                    CJ. Bernardos, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       October 2020
        Mailbox:    h.a.chan@ieee.org, 
                    weixinpeng@huawei.com, 
                    jonghyouk@sejong.ac.kr,
                    seiljeon.ietf@gmail.com, 
                    cjbc@it.uc3m.es
        Pages:      18
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dmm-distributed-mobility-anchoring-15.txt

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

        DOI:        10.17487/RFC8818

This document defines distributed mobility anchoring in terms of the
different configurations and functions to provide IP mobility
support. A network may be configured with distributed mobility
anchoring functions for both network-based or host-based mobility
support, depending on the network's needs. In a distributed mobility
anchoring environment, multiple anchors are available for mid-session
switching of an IP prefix anchor. To start a new flow or to handle a
flow not requiring IP session continuity as a mobile node moves to a
new network, the flow can be started or restarted using an IP address
configured from the new IP prefix anchored to the new network. If the
flow needs to survive the change of network, there are solutions that
can be used to enable IP address mobility. This document describes
different anchoring approaches, depending on the IP mobility needs,
and how this IP address mobility is handled by the network.

This document is a product of the Distributed Mobility Management 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  Wed Oct 21 16:16: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 76BF33A0B86 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 21 Oct 2020 16:16: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 vaKnqG8qYPhH for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 21 Oct 2020 16:16: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 A37203A0B7D for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 21 Oct 2020 16:16:41 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 242B8F4071E; Wed, 21 Oct 2020 16:16: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 698A5F40719; Wed, 21 Oct 2020 16: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: <20201021231634.698A5F40719@rfc-editor.org>
Date: Wed, 21 Oct 2020 16:16:34 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8921_on_Dynamic_Service_Negotiation=3A_?= =?utf-8?q?The_Connectivity_Provisioning_Negotiation_Protocol_=28CPNP=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, 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 8921

        Title:      Dynamic Service Negotiation: The Connectivity 
                    Provisioning Negotiation Protocol (CPNP) 
        Author:     M. Boucadair, Ed.,
                    C. Jacquenet, 
                    D. Zhang,
                    P. Georgatsos
        Status:     Informational
        Stream:     Independent
        Date:       October 2020
        Mailbox:    mohamed.boucadair@orange.com, 
                    christian.jacquenet@orange.com, 
                    dacheng.zhang@huawei.com,
                    pgeorgat@gmail.com
        Pages:      49
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-boucadair-connectivity-provisioning-protocol-22.txt

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

        DOI:        10.17487/RFC8921

This document defines the Connectivity Provisioning Negotiation
Protocol (CPNP), which is designed to facilitate the dynamic
negotiation of service parameters.

CPNP is a generic protocol that can be used for various negotiation
purposes that include (but are not necessarily limited to)
connectivity provisioning services, storage facilities, Content
Delivery Networks, etc.


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  Wed Oct 21 16:17:19 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 593243A0EA7 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 21 Oct 2020 16:17:19 -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 rOn7Gfhaqxp4 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 21 Oct 2020 16:17:15 -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 562AE3A0C55 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 21 Oct 2020 16:17:08 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 696D8F4073D; Wed, 21 Oct 2020 16:17:03 -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 E380DF4073A; Wed, 21 Oct 2020 16:17:02 -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: <20201021231702.E380DF4073A@rfc-editor.org>
Date: Wed, 21 Oct 2020 16:17:02 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8922_on_A_Survey_of_the_Interaction_bet?= =?utf-8?q?ween_Security_Protocols_and_Transport_Services?=
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, taps@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 8922

        Title:      A Survey of the Interaction between 
                    Security Protocols and Transport Services 
        Author:     T. Enghardt, 
                    T. Pauly,
                    C. Perkins, 
                    K. Rose,
                    C. Wood
        Status:     Informational
        Stream:     IETF
        Date:       October 2020
        Mailbox:    ietf@tenghardt.net, 
                    tpauly@apple.com, 
                    csp@csperkins.org,
                    krose@krose.org, 
                    caw@heapingbits.net
        Pages:      19
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-taps-transport-security-12.txt

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

        DOI:        10.17487/RFC8922

This document provides a survey of commonly used or notable network
security protocols, with a focus on how they interact and integrate
with applications and transport protocols. Its goal is to supplement
efforts to define and catalog Transport Services by describing the
interfaces required to add security protocols. This survey is not
limited to protocols developed within the scope or context of the
IETF, and those included represent a superset of features a Transport
Services system may need to support.

This document is a product of the Transport Services 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  Wed Oct 21 16:17: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 950393A0B86 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 21 Oct 2020 16:17: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 kOvYQIO57Tf4 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 21 Oct 2020 16:17: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 DBDF03A0EB4 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 21 Oct 2020 16:17:21 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id ADD0BF4074B; Wed, 21 Oct 2020 16:17:09 -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 87143F40745; Wed, 21 Oct 2020 16:17:08 -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: <20201021231708.87143F40745@rfc-editor.org>
Date: Wed, 21 Oct 2020 16:17:08 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8923_on_A_Minimal_Set_of_Transport_Serv?= =?utf-8?q?ices_for_End_Systems?=
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, taps@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 8923

        Title:      A Minimal Set of Transport Services for End Systems
        Author:     M. Welzl, 
                    S. Gjessing
        Status:     Informational
        Stream:     IETF
        Date:       October 2020
        Mailbox:    michawe@ifi.uio.no, 
                    steing@ifi.uio.no
        Pages:      44
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-taps-minset-11.txt

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

        DOI:        10.17487/RFC8923

This document recommends a minimal set of Transport Services offered
by end systems and gives guidance on choosing among the available
mechanisms and protocols. It is based on the set of transport
features in RFC 8303.

This document is a product of the Transport Services 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  Thu Oct 22 14:10:26 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 EDB2A3A104E for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 22 Oct 2020 14:10:26 -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 moaDElMomaRe for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 22 Oct 2020 14:10: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 9FE083A1050 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 22 Oct 2020 14:10:25 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 1FBEFF4071C; Thu, 22 Oct 2020 14:10:19 -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 6DA8AF4071A; Thu, 22 Oct 2020 14:10:18 -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: <20201022211018.6DA8AF4071A@rfc-editor.org>
Date: Thu, 22 Oct 2020 14:10:18 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8917_on_The_LoST-Validation_Straightfor?= =?utf-8?q?ward-Naming_Authority_PoinTeR_=28S-NAPTR=29_Application_Service?= =?utf-8?q?_Tag?=
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 8917

        Title:      The LoST-Validation Straightforward-Naming Authority 
                    PoinTeR (S-NAPTR) Application Service Tag 
        Author:     R. Gellens, B. Rosen
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2020
        Mailbox:    rg+ietf@coretechnologyconsulting.com, 
                    br@brianrosen.net
        Pages:      7
        Updates:    RFC 5222

        I-D Tag:    draft-gellens-lost-validation-09.txt

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

        DOI:        10.17487/RFC8917

This document adds the 'LoST-Validation' service tag to the
Straightforward-Naming Authority PoinTeR (S-NAPTR) Application
Service Tag IANA registry.  This tag can appear in a Naming Authority
Pointer (NAPTR) Domain Name System (DNS) record to assist clients of
the Location-to-Service Translation (LoST) Protocol in identifying
LoST servers designated for location validation.  This tag and the
information about its use update RFC 5222, which enables the explicit
discovery of a server that supports location validation.

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 Oct 22 15:45:14 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 687073A08C3 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 22 Oct 2020 15:45:14 -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 0N5sXG0HUZY3 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 22 Oct 2020 15:45:12 -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 DCB3F3A08CA for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 22 Oct 2020 15:45:12 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 48F53F406F5; Thu, 22 Oct 2020 15:45:06 -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 2DA48F406F5; Thu, 22 Oct 2020 15:45:05 -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: <20201022224505.2DA48F406F5@rfc-editor.org>
Date: Thu, 22 Oct 2020 15:45:05 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8919_on_IS-IS_Application-Specific_Link?= =?utf-8?q?_Attributes?=
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: lsr@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 8919

        Title:      IS-IS Application-Specific Link Attributes 
        Author:     L. Ginsberg,
                    P. Psenak,
                    S. Previdi,
                    W. Henderickx,
                    J. Drake
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2020 
        Mailbox:    ginsberg@cisco.com, 
                    ppsenak@cisco.com, 
                    stefano@previdi.net, 
                    wim.henderickx@nokia.com, 
                    jdrake@juniper.net
        Pages:      20
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-isis-te-app-19.txt

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

        DOI:        10.17487/RFC8919

Existing traffic-engineering-related link attribute advertisements
have been defined and are used in RSVP-TE deployments. Since the
original RSVP-TE use case was defined, additional applications (e.g.,
Segment Routing Policy and Loop-Free Alternates) that also make use
of the link attribute advertisements have been defined. In cases
where multiple applications wish to make use of these link
attributes, the current advertisements do not support
application-specific values for a given attribute, nor do they
support indication of which applications are using the advertised
value for a given link. This document introduces new link attribute
advertisements that address both of these shortcomings.

This document is a product of the Link State Routing 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 Oct 22 15:45:36 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 942A73A0A06 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 22 Oct 2020 15:45:36 -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 xpev6vQSr4DP for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 22 Oct 2020 15:45:35 -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 985C03A09D6 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 22 Oct 2020 15:45:33 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 92698F4072C; Thu, 22 Oct 2020 15:45:27 -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 75577F4072C; Thu, 22 Oct 2020 15:45:26 -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: <20201022224526.75577F4072C@rfc-editor.org>
Date: Thu, 22 Oct 2020 15:45:26 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8920_on_OSPF_Application-Specific_Link_?= =?utf-8?q?Attributes?=
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: lsr@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 8920

        Title:      OSPF Application-Specific Link Attributes 
        Author:     P. Psenak, Ed.,
                    L. Ginsberg, 
                    W. Henderickx,
                    J. Tantsura,
                    J. Drake
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2020
        Mailbox:    ppsenak@cisco.com, 
                    ginsberg@cisco.com, 
                    wim.henderickx@nokia.com, 
                    jefftant.ietf@gmail.com, 
                    jdrake@juniper.net
        Pages:      19
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ospf-te-link-attr-reuse-16.txt

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

        DOI:        10.17487/RFC8920

Existing traffic-engineering-related link attribute advertisements
have been defined and are used in RSVP-TE deployments.  Since the
original RSVP-TE use case was defined, additional applications (e.g.,
Segment Routing Policy and Loop-Free Alternates) that also make use
of the link attribute advertisements have been defined.  In cases
where multiple applications wish to make use of these link
attributes, the current advertisements do not support
application-specific values for a given attribute, nor do they
support indication of which applications are using the advertised
value for a given link.  This document introduces new link attribute
advertisements in OSPFv2 and OSPFv3 that address both of these
shortcomings.

This document is a product of the Link State Routing 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  Fri Oct 23 11:47:39 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 E1FBA3A10DB for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 23 Oct 2020 11:47:39 -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 Q0UwDVrEjBBK for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 23 Oct 2020 11:47: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 972C03A10E0 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 23 Oct 2020 11:47:38 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id EECAAF4073B; Fri, 23 Oct 2020 11:47:30 -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 3A7FFF4073A; Fri, 23 Oct 2020 11:47:30 -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: <20201023184730.3A7FFF4073A@rfc-editor.org>
Date: Fri, 23 Oct 2020 11:47:30 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8884_on_Research_Directions_for_Using_I?= =?utf-8?q?nformation-Centric_Networking_=28ICN=29_in_Disaster_Scenarios?=
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 8884

        Title:      Research Directions for Using Information-Centric 
                    Networking (ICN) in Disaster Scenarios 
        Author:     J. Seedorf, 
                    M. Arumaithurai,
                    A. Tagami,
                    K. Ramakrishnan,
                    N. Blefari-Melazzi
        Status:     Informational
        Stream:     IRTF
        Date:       October 2020
        Mailbox:    jan.seedorf@hft-stuttgart.de, 
                    arumaithurai@informatik.uni-goettingen.de, 
                    tagami@kddi-research.jp, 
                    kkramakrishnan@yahoo.com, 
                    blefari@uniroma2.it
        Pages:      17
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-irtf-icnrg-disaster-10.txt

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

        DOI:        10.17487/RFC8884

Information-Centric Networking (ICN) is a new paradigm where the
network provides users with named content instead of communication
channels between hosts. This document outlines some research
directions for ICN with respect to applying ICN approaches for coping
with natural or human-generated, large-scale disasters. 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  Fri Oct 23 14:15:19 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 863643A0844 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 23 Oct 2020 14:15:19 -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 mANp5WDwBQgT for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 23 Oct 2020 14:15:16 -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 C68023A08BB for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 23 Oct 2020 14:15:16 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 08C1EF4071E; Fri, 23 Oct 2020 14:15:09 -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 F0FFFF4071A; Fri, 23 Oct 2020 14:15:07 -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: <20201023211507.F0FFFF4071A@rfc-editor.org>
Date: Fri, 23 Oct 2020 14:15:07 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8914_on_Extended_DNS_Errors?=
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 8914

        Title:      Extended DNS Errors 
        Author:     W. Kumari,
                    E. Hunt,
                    R. Arends,
                    W. Hardaker,
                    D. Lawrence
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2020
        Mailbox:    warren@kumari.net, 
                    each@isc.org, 
                    roy.arends@icann.org,
                    ietf@hardakers.net, 
                    tale@dd.org
        Pages:      13
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dnsop-extended-error-16.txt

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

        DOI:        10.17487/RFC8914

This document defines an extensible method to return additional
information about the cause of DNS errors. Though created primarily
to extend SERVFAIL to provide additional information about the cause
of DNS and DNSSEC failures, the Extended DNS Errors option defined in
this document allows all response types to contain extended error
information. Extended DNS Error information does not change the
processing of RCODEs.

This document is a product of the Domain Name System Operations 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  Fri Oct 23 14:45: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 83C1A3A0112 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 23 Oct 2020 14:45: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 VacmZuBICAaf for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 23 Oct 2020 14:45: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 5E8D73A08B8 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 23 Oct 2020 14:45:55 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5F524F4071A; Fri, 23 Oct 2020 14:45:47 -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 BFFCFF4071A; Fri, 23 Oct 2020 14:45:46 -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: <20201023214546.BFFCFF4071A@rfc-editor.org>
Date: Fri, 23 Oct 2020 14:45:46 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?BCP_232=2C_RFC_8932_on_Recommendations_for_?= =?utf-8?q?DNS_Privacy_Service_Operators?=
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, dns-privacy@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.

        BCP 232        
        RFC 8932

        Title:      Recommendations for DNS Privacy Service 
                    Operators 
        Author:     S. Dickinson,
                    B. Overeinder,
                    R. van Rijswijk-Deij,
                    A. Mankin
        Status:     Best Current Practice
        Stream:     IETF
        Date:       October 2020
        Mailbox:    sara@sinodun.com, 
                    benno@NLnetLabs.nl, 
                    roland@nlnetlabs.nl,
                    allison.mankin@gmail.com
        Pages:      34
        See Also:   BCP 232

        I-D Tag:    draft-ietf-dprive-bcp-op-14.txt

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

        DOI:        10.17487/RFC8932

This document presents operational, policy, and security
considerations for DNS recursive resolver operators who choose to
offer DNS privacy services.  With these recommendations, the operator
can make deliberate decisions regarding which services to provide, as
well as understanding how those decisions and the alternatives impact
the privacy of users. 

This document also presents a non-normative framework to assist
writers of a Recursive operator Privacy Statement, analogous to DNS
Security Extensions (DNSSEC) Policies and DNSSEC Practice Statements
described in RFC 6841.

This document is a product of the DNS PRIVate Exchange Working Group of the IETF.


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  Fri Oct 23 15:38:05 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 B477C3A0A63 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 23 Oct 2020 15:38:05 -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 o7h90K3soeWg for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 23 Oct 2020 15:38:04 -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 095DB3A09F7 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 23 Oct 2020 15:38:04 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 4734EF40737; Fri, 23 Oct 2020 15:37: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 E0F33F40737; Fri, 23 Oct 2020 15:37: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: <20201023223754.E0F33F40737@rfc-editor.org>
Date: Fri, 23 Oct 2020 15:37:54 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8940_on_Extensible_Authentication_Proto?= =?utf-8?q?col_=28EAP=29_Session-Id_Derivation_for_EAP_Subscriber_Identity?= =?utf-8?q?_Module_=28EAP-SIM=29=2C_EAP_Authentication_and_Key_Agreement_?= =?utf-8?q?=28EAP-AKA=29=2C_and_Protected_EAP_=28PEAP=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, emu@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 8940

        Title:      Extensible Authentication Protocol (EAP) Session-Id 
                    Derivation for EAP Subscriber Identity Module 
                    (EAP-SIM), EAP Authentication and Key Agreement 
                    (EAP-AKA), and Protected EAP (PEAP) 
        Author:     A. DeKok
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2020
        Mailbox:    aland@freeradius.org
        Pages:      7
        Updates:    RFC 5247

        I-D Tag:    draft-ietf-emu-eap-session-id-07.txt

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

        DOI:        10.17487/RFC8940

RFC 5247 is updated to define and clarify EAP Session-Id derivation
for multiple Extensible Authentication Protocol (EAP) methods.  The
derivation of Session-Id was not given for EAP Subscriber Identity
Module (EAP-SIM) or EAP Authentication and Key Agreement (EAP-AKA)
when using the fast reconnect exchange instead of full
authentication.  The derivation of Session-Id for full authentication
is clarified for both EAP-SIM and EAP-AKA.  The derivation of
Session-Id for Protected EAP (PEAP) is also given.  The definition
for PEAP follows the definition for other TLS-based EAP methods.

This document is a product of the EAP Method Update 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  Sat Oct 24 13:47:13 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 D14803A10FC for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sat, 24 Oct 2020 13:47:13 -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 yzvazYmB8VpQ for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sat, 24 Oct 2020 13:47:11 -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 3802F3A112A for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Sat, 24 Oct 2020 13:47:08 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 6B968F4071F; Sat, 24 Oct 2020 13:46:59 -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 4F79FF4071E; Sat, 24 Oct 2020 13:46:58 -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: <20201024204658.4F79FF4071E@rfc-editor.org>
Date: Sat, 24 Oct 2020 13:46:58 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8905_on_The_=27payto=27_URI_Scheme_for_?= =?utf-8?q?Payments?=
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 8905

        Title:      The 'payto' URI Scheme for Payments 
        Author:     F. Dold, 
                    C. Grothoff
        Status:     Informational
        Stream:     Independent
        Date:       October 2020
        Mailbox:    dold@taler.net, 
                    christian.grothoff@bfh.ch
        Pages:      12
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-dold-payto-14.txt

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

        DOI:        10.17487/RFC8905

This document defines the 'payto' Uniform Resource Identifier (URI)
scheme for designating targets for payments.

A unified URI scheme for all payment target types allows applications
to offer user interactions with URIs that represent payment targets,
simplifying the introduction of new payment systems and applications.


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  Sat Oct 31 12:22:07 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 5EA113A0AEC for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sat, 31 Oct 2020 12:22:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.899
X-Spam-Level:
X-Spam-Status: No, score=-2.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_BLOCKED=0.001, 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 EcGbdn4-VxVi for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sat, 31 Oct 2020 12:22:05 -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 ADFA23A0AE8 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Sat, 31 Oct 2020 12:22:05 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 02AE8F40722; Sat, 31 Oct 2020 12:21:49 -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 F2C63F40721; Sat, 31 Oct 2020 12:21:47 -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: <20201031192147.F2C63F40721@rfc-editor.org>
Date: Sat, 31 Oct 2020 12:21:47 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8934_on_PCE_Communication_Protocol_=28P?= =?utf-8?q?CEP=29_Extensions_for_Label_Switched_Path_=28LSP=29_Scheduling_?= =?utf-8?q?with_Stateful_PCE?=
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, pce@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 8934

        Title:      PCE Communication Protocol (PCEP) Extensions 
                    for Label Switched Path (LSP) Scheduling 
                    with Stateful PCE 
        Author:     H. Chen, Ed.,
                    Y. Zhuang, Ed.,
                    Q. Wu,
                    D. Ceccarelli
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2020
        Mailbox:    huaimo.chen@futurewei.com, 
                    zhuangyan.zhuang@huawei.com, 
                    bill.wu@huawei.com,
                    daniele.ceccarelli@ericsson.com
        Pages:      23
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-stateful-pce-lsp-scheduling-27.txt

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

        DOI:        10.17487/RFC8934

This document defines a set of extensions to the stateful PCE
Communication Protocol (PCEP) to enable Label Switched Path (LSP)
path computation, activation, setup, and deletion based on scheduled
time intervals for the LSP and the actual network resource usage in a
centralized network environment, as stated in RFC 8413.

This document is a product of the Path Computation Element 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  Sat Oct 31 12:44:02 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 D47353A0D91 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sat, 31 Oct 2020 12:44:02 -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 k2qXP4VGRg0C for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sat, 31 Oct 2020 12:44:01 -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 8DA5D3A0D90 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Sat, 31 Oct 2020 12:44:01 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id DEA93F4071D; Sat, 31 Oct 2020 12:43:44 -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 856A3F4071D; Sat, 31 Oct 2020 12:43:43 -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: <20201031194343.856A3F4071D@rfc-editor.org>
Date: Sat, 31 Oct 2020 12:43:43 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8916_on_A_YANG_Data_Model_for_the_Multi?= =?utf-8?q?cast_Source_Discovery_Protocol_=28MSDP=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, pim@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 8916

        Title:      A YANG Data Model for 
                    the Multicast Source Discovery Protocol (MSDP) 
        Author:     X. Liu,
                    Z. Zhang, Ed.,
                    A. Peter,
                    M. Sivakumar,
                    F. Guo,
                    P. McAllister
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2020 
        Mailbox:    xufeng.liu.ietf@gmail.com, 
                    zhang.zheng@zte.com.cn, 
                    anish.ietf@gmail.com, 
                    sivakumar.mahesh@gmail.com, 
                    guofeng@huawei.com,
                    pete.mcallister@metaswitch.com
        Pages:      37
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pim-msdp-yang-18.txt

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

        DOI:        10.17487/RFC8916

This document defines a YANG data model for the configuration and
management of Multicast Source Discovery Protocol (MSDP) protocol
operations.

This document is a product of the Protocols for IP Multicast 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
