
From rfc-dist-bounces@rfc-editor.org  Wed Dec 12 10:20:40 2018
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 151BE1311CF for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 12 Dec 2018 10:20:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 w779d849di98 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 12 Dec 2018 10:20:38 -0800 (PST)
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 44BC31311CC for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 12 Dec 2018 10:20:38 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 06E52B8005C; Wed, 12 Dec 2018 10:20:21 -0800 (PST)
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 29A8FB80050; Wed, 12 Dec 2018 10:20:20 -0800 (PST)
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: <20181212182020.29A8FB80050@rfc-editor.org>
Date: Wed, 12 Dec 2018 10:20:20 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8476_on_Signaling_Maximum_SID_Depth_=28?= =?utf-8?q?MSD=29_Using_OSPF?=
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 8476

        Title:      Signaling Maximum SID Depth (MSD) Using OSPF 
        Author:     J. Tantsura, 
                    U. Chunduri,
                    S. Aldrin,
                    P. Psenak
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2018
        Mailbox:    jefftant.ietf@gmail.com, 
                    uma.chunduri@huawei.com, 
                    aldrin.ietf@gmail.com,
                    ppsenak@cisco.com
        Pages:      11
        Characters: 21547
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ospf-segment-routing-msd-25.txt

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

        DOI:        10.17487/RFC8476

This document defines a way for an Open Shortest Path First (OSPF)
router to advertise multiple types of supported Maximum SID Depths
(MSDs) at node and/or link granularity.  Such advertisements allow
entities (e.g., centralized controllers) to determine whether a
particular Segment Identifier (SID) stack can be supported in a given
network.  This document only refers to the Signaling MSD as defined
in RFC 8491, but it defines an encoding that can support other MSD
types.  Here, the term "OSPF" means both OSPFv2 and OSPFv3.

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  Tue Dec 18 13:48:03 2018
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 9D2E81311EC for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 18 Dec 2018 13:48:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 8-XMfRUUJPZm for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 18 Dec 2018 13:48:02 -0800 (PST)
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 05B13130934 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 18 Dec 2018 13:48:02 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id C1F11B80C1A; Tue, 18 Dec 2018 13:47:38 -0800 (PST)
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 D7877B80C14; Tue, 18 Dec 2018 13:47:36 -0800 (PST)
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: <20181218214736.D7877B80C14@rfc-editor.org>
Date: Tue, 18 Dec 2018 13:47:36 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8509_on_A_Root_Key_Trust_Anchor_Sentine?= =?utf-8?q?l_for_DNSSEC?=
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 8509

        Title:      A Root Key Trust Anchor 
                    Sentinel for DNSSEC 
        Author:     G. Huston, 
                    J. Damas,
                    W. Kumari
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2018
        Mailbox:    gih@apnic.net, 
                    joao@apnic.net, 
                    warren@kumari.net
        Pages:      19
        Characters: 43683
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dnsop-kskroll-sentinel-17.txt

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

        DOI:        10.17487/RFC8509

The DNS Security Extensions (DNSSEC) were developed to provide origin
authentication and integrity protection for DNS data by using digital
signatures.  These digital signatures can be verified by building a
chain of trust starting from a trust anchor and proceeding down to a
particular node in the DNS.  This document specifies a mechanism that
will allow an end user and third parties to determine the trusted key
state for the root key of the resolvers that handle that user's DNS
queries.  Note that this method is only applicable for determining
which keys are in the trust store for the root key.

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  Tue Dec 18 13:48:28 2018
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 E366513133B for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 18 Dec 2018 13:48:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 pKQ2iZi-i7Mg for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 18 Dec 2018 13:48:27 -0800 (PST)
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 714C4131278 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 18 Dec 2018 13:48:20 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 58AF0B80C35; Tue, 18 Dec 2018 13:47:53 -0800 (PST)
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 4CED7B80C36; Tue, 18 Dec 2018 13:47:52 -0800 (PST)
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: <20181218214752.4CED7B80C36@rfc-editor.org>
Date: Tue, 18 Dec 2018 13:47:52 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8511_on_TCP_Alternative_Backoff_with_EC?= =?utf-8?q?N_=28ABE=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, tcpm@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 8511

        Title:      TCP Alternative Backoff with ECN (ABE) 
        Author:     N. Khademi,
                    M. Welzl,
                    G. Armitage, 
                    G. Fairhurst
        Status:     Experimental
        Stream:     IETF
        Date:       December 2018
        Mailbox:    naeemk@ifi.uio.no, 
                    michawe@ifi.uio.no, 
                    garmitage@netflix.com, 
                    gorry@erg.abdn.ac.uk
        Pages:      12
        Characters: 27408
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tcpm-alternativebackoff-ecn-12.txt

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

        DOI:        10.17487/RFC8511

Active Queue Management (AQM) mechanisms allow for burst tolerance
while enforcing short queues to minimise the time that packets spend
enqueued at a bottleneck.  This can cause noticeable performance
degradation for TCP connections traversing such a bottleneck,
especially if there are only a few flows or their bandwidth-delay
product (BDP) is large.  The reception of a Congestion Experienced
(CE) Explicit Congestion Notification (ECN) mark indicates that an
AQM mechanism is used at the bottleneck, and the bottleneck network
queue is therefore likely to be short.  Feedback of this signal
allows the TCP sender-side ECN reaction in congestion avoidance to
reduce the Congestion Window (cwnd) by a smaller amount than the
congestion control algorithm's reaction to inferred packet loss.
Therefore, this specification defines an experimental change to the
TCP reaction specified in RFC 3168, as permitted by RFC 8311.

This document is a product of the TCP Maintenance and Minor Extensions Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Tue Dec 18 21:17:44 2018
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 1A03F12F1A5 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 18 Dec 2018 21:17:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 gmYPovzLpcfn for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 18 Dec 2018 21:17:42 -0800 (PST)
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 BC3D4131012 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 18 Dec 2018 21:17:36 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 08F8DB80D4F; Tue, 18 Dec 2018 21:17:13 -0800 (PST)
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 ED931B80D4D; Tue, 18 Dec 2018 21:17:11 -0800 (PST)
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: <20181219051711.ED931B80D4D@rfc-editor.org>
Date: Tue, 18 Dec 2018 21:17:11 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8389_on_Definitions_of_Managed_Objects_?= =?utf-8?q?for_Mapping_of_Address_and_Port_with_Encapsulation_=28MAP-E=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: softwires@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 8389

        Title:      Definitions of Managed Objects for 
                    Mapping of Address and Port with 
                    Encapsulation (MAP-E) 
        Author:     Y. Fu, 
                    S. Jiang,
                    B. Liu, 
                    J. Dong,
                    Y. Chen
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2018
        Mailbox:    eleven711711@foxmail.com, 
                    jiangsheng@huawei.com, 
                    leo.liubing@huawei.com,
                    knight.dongjiang@gmail.com, 
                    flashfoxmx@gmail.com
        Pages:      16
        Characters: 30534
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-softwire-map-mib-13.txt

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

        DOI:        10.17487/RFC8389

This memo defines a portion of the Management Information Base (MIB)
for Mapping of Address and Port with Encapsulation (MAP-E) for use
with network management protocols.

This document is a product of the Softwires Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Tue Dec 18 21:18:09 2018
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 7D72D1312C7 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 18 Dec 2018 21:18:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 82ttK3ZR0wak for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 18 Dec 2018 21:18:08 -0800 (PST)
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 944FC130F84 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 18 Dec 2018 21:17:53 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id A2C8DB80D59; Tue, 18 Dec 2018 21:17:20 -0800 (PST)
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 A9C8CB80D59; Tue, 18 Dec 2018 21:17:18 -0800 (PST)
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: <20181219051718.A9C8CB80D59@rfc-editor.org>
Date: Tue, 18 Dec 2018 21:17:18 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8488_on_RIPE_NCC=27s_Implementation_of_?= =?utf-8?q?Resource_Public_Key_Infrastructure_=28RPKI=29_Certificate_Tree_?= =?utf-8?q?Validation?=
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, sidrops@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 8488

        Title:      RIPE NCC's Implementation of Resource 
                    Public Key Infrastructure (RPKI) Certificate Tree 
                    Validation 
        Author:     O. Muravskiy,
                    T. Bruijnzeels
        Status:     Informational
        Stream:     IETF
        Date:       December 2018
        Mailbox:    oleg@ripe.net, 
                    tim@nlnetlabs.nl
        Pages:      17
        Characters: 35434
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sidrops-rpki-tree-validation-03.txt

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

        DOI:        10.17487/RFC8488

This document describes an approach to validating the content of the
Resource Public Key Infrastructure (RPKI) certificate tree, as it is
implemented in the RIPE NCC RPKI Validator.  This approach is
independent of a particular object retrieval mechanism, which allows
it to be used with repositories available over the rsync protocol,
the RPKI Repository Delta Protocol (RRDP), and repositories that use
a mix of both.

This document is a product of the SIDR Operations Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Fri Dec 21 17:16:42 2018
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 D352E130F40 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 21 Dec 2018 17:16:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 XTNKF8fK9V9m for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 21 Dec 2018 17:16:41 -0800 (PST)
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 9C524130EC9 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 21 Dec 2018 17:16:41 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 53668B81A89; Fri, 21 Dec 2018 17:16:39 -0800 (PST)
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 DD3C6B81A87; Fri, 21 Dec 2018 17:16:37 -0800 (PST)
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: <20181222011637.DD3C6B81A87@rfc-editor.org>
Date: Fri, 21 Dec 2018 17:16:37 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8502_on_L2L3_VPN_Multicast_MIB?=
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, bess@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 8502

        Title:      L2L3 VPN Multicast MIB 
        Author:     Z. Zhang,
                    H. Tsunoda
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2018
        Mailbox:    zzhang@juniper.net, 
                    tsuno@m.ieice.org
        Pages:      20
        Characters: 40349
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bess-l2l3-vpn-mcast-mib-16.txt

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

        DOI:        10.17487/RFC8502

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes two MIB modules that will be used by
other MIB modules for monitoring and/or configuring Layer 2 and Layer
3 Virtual Private Networks that support multicast.

This document is a product of the BGP Enabled Services 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 Dec 21 17:17:10 2018
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 1A331130FA9 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 21 Dec 2018 17:17:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 8ZuW2vaJqGvH for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 21 Dec 2018 17:17:08 -0800 (PST)
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 523B1130F5F for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 21 Dec 2018 17:17:08 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 035CCB81A96; Fri, 21 Dec 2018 17:17:07 -0800 (PST)
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 7FCBCB81A95; Fri, 21 Dec 2018 17:17:06 -0800 (PST)
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: <20181222011706.7FCBCB81A95@rfc-editor.org>
Date: Fri, 21 Dec 2018 17:17:06 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8503_on_BGP/MPLS_Layer_3_VPN_Multicast_?= =?utf-8?q?Management_Information_Base?=
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, bess@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 8503

        Title:      BGP/MPLS Layer 3 VPN Multicast 
                    Management Information Base 
        Author:     H. Tsunoda
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2018
        Mailbox:    tsuno@m.ieice.org
        Pages:      57
        Characters: 107060
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bess-mvpn-mib-12.txt

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

        DOI:        10.17487/RFC8503

This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects to configure and/or
monitor Multicast communication over IP Virtual Private Networks
(VPNs) supported by the Multiprotocol Label Switching/Border Gateway
Protocol (MPLS/BGP) on a Provider Edge (PE) router.

This document is a product of the BGP Enabled Services 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 Dec 21 17:17:40 2018
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 632D5130FA8 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 21 Dec 2018 17:17:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 1I1qfWJpCDv1 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 21 Dec 2018 17:17:38 -0800 (PST)
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 D961C130FB1 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 21 Dec 2018 17:17:37 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 8890AB81A98; Fri, 21 Dec 2018 17:17:36 -0800 (PST)
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 2B7A6B81AA3; Fri, 21 Dec 2018 17:17:35 -0800 (PST)
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: <20181222011735.2B7A6B81AA3@rfc-editor.org>
Date: Fri, 21 Dec 2018 17:17:35 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8507_on_Simple_Internet_Protocol_=28SIP?= =?utf-8?q?=29_Specification?=
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 8507

        Title:      Simple Internet Protocol (SIP) Specification 
        Author:     S. Deering,
                    R. Hinden, Ed.
        Status:     Historic
        Stream:     Independent
        Date:       December 2018
        Mailbox:    bob.hinden@gmail.com
        Pages:      26
        Characters: 56057
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-historic-simple-ip-03.txt

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

        DOI:        10.17487/RFC8507

This document is published for the historical record.  The Simple
Internet Protocol was the basis for one of the candidates for the
IETF's Next Generation (IPng) work that became IPv6.

The publication date of the original Internet-Draft was November 10,
1992.  It is presented here substantially unchanged and is neither a
complete document nor intended to be implementable.

The paragraph that follows is the Abstract from the original draft.

This document specifies a new version of IP called SIP, the Simple
Internet Protocol.  It also describes the changes needed to ICMP,
IGMP, and transport protocols such as TCP and UDP, in order to work
with SIP.  A companion document [SIP-ADDR] describes the addressing
and routing aspects of SIP, including issues of auto-configuration,
host and subnet mobility, and multicast.


HISTORIC: This memo defines a Historic Document 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
