
From rfc-dist-bounces@rfc-editor.org  Mon Mar  9 21:50: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 DCFF43A0529 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon,  9 Mar 2020 21:50:35 -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 V2F3Qu6-y00c for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon,  9 Mar 2020 21:50:30 -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 584923A0522 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon,  9 Mar 2020 21:50:30 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 0C8CEF40709; Mon,  9 Mar 2020 21:50: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 78801F406F0; Mon,  9 Mar 2020 21:50: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: <20200310045026.78801F406F0@rfc-editor.org>
Date: Mon,  9 Mar 2020 21:50:26 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8741_on_Ability_for_a_Stateful_Path_Com?= =?utf-8?q?putation_Element_=28PCE=29_to_Request_and_Obtain_Control_of_a_L?= =?utf-8?q?abel_Switched_Path_=28LSP=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, 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 8741

        Title:      Ability for a Stateful Path Computation 
                    Element (PCE) to Request and Obtain 
                    Control of a Label Switched Path (LSP) 
        Author:     A. Raghuram,
                    A. Goddard,
                    J. Karthik, 
                    S. Sivabalan,
                    M. Negi
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    ar2521@att.com, 
                    ag6941@att.com, 
                    jakarthi@cisco.com,
                    msiva@cisco.com, 
                    mahend.ietf@gmail.com
        Pages:      11
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-lsp-control-request-11.txt

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

        DOI:        10.17487/RFC8741

A stateful Path Computation Element (PCE) retains information about
the placement of Multiprotocol Label Switching (MPLS) Traffic
Engineering Label Switched Paths (TE LSPs). When a PCE has stateful
control over LSPs, it may send indications to LSP head-ends to modify
the attributes (especially the paths) of the LSPs. A Path Computation
Client (PCC) that has set up LSPs under local configuration may
delegate control of those LSPs to a stateful PCE.

There are use cases in which a stateful PCE may wish to obtain
control of locally configured LSPs that it is aware of but have not
been delegated to the PCE.

This document describes an extension to the Path Computation Element
Communication Protocol (PCEP) to enable a PCE to make requests for
such control.

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  Mon Mar  9 21:50: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 E6C9B3A0764 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon,  9 Mar 2020 21:50: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 gCp4RpY2CD4w for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon,  9 Mar 2020 21:50:52 -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 9305E3A07D8 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon,  9 Mar 2020 21:50:52 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 4A2DBF40722; Mon,  9 Mar 2020 21:50:31 -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 93368F40721; Mon,  9 Mar 2020 21:50:30 -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: <20200310045030.93368F40721@rfc-editor.org>
Date: Mon,  9 Mar 2020 21:50:30 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8747_on_Proof-of-Possession_Key_Semanti?= =?utf-8?q?cs_for_CBOR_Web_Tokens_=28CWTs=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, ace@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 8747

        Title:      Proof-of-Possession Key Semantics for
                    CBOR Web Tokens (CWTs) 
        Author:     M. Jones, 
                    L. Seitz,
                    G. Selander, 
                    S. Erdtman,
                    H. Tschofenig
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    mbj@microsoft.com, 
                    ludwig.seitz@combitech.se, 
                    goran.selander@ericsson.com,
                    erdtman@spotify.com, 
                    Hannes.Tschofenig@arm.com
        Pages:      14
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ace-cwt-proof-of-possession-11.txt

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

        DOI:        10.17487/RFC8747

This specification describes how to declare in a CBOR Web Token (CWT)
(which is defined by RFC 8392) that the presenter of the CWT
possesses a particular proof-of-possession key. Being able to prove
possession of a key is also sometimes described as being the
holder-of-key. This specification provides equivalent functionality
to "Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs)"
(RFC 7800) but using Concise Binary Object Representation (CBOR) and
CWTs rather than JavaScript Object Notation (JSON) and JSON Web
Tokens (JWTs).

This document is a product of the Authentication and Authorization for Constrained Environments Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Tue Mar 10 13:29: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 E500C3A0C5E for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 10 Mar 2020 13:29:10 -0700 (PDT)
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 rxmYFKYJm9If for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 10 Mar 2020 13:29:09 -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 C21DB3A0C5C for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 10 Mar 2020 13:29:09 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D38DEF40721; Tue, 10 Mar 2020 13:29:05 -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 1ECF8F4071D; Tue, 10 Mar 2020 13:29:04 -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: <20200310202904.1ECF8F4071D@rfc-editor.org>
Date: Tue, 10 Mar 2020 13:29:04 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_3716_on_IETF_in_the_Large=3A__Administr?= =?utf-8?q?ation_and_Execution?=
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>

RFC 3716 has been reclassified as Historic.


RFC 8717 updates RFCs 2028, 2418, 3005, 3710, 3929, 4633, and 6702. 
In addition, with the authorization of the IAB, it requested that 
the Informational RFC 3716 be made Historic (see Section 4).

By the process documented in
https://www.ietf.org/about/groups/iesg/statements/designating-rfcs-historic-2014-07-20/?topic=22&
there should have been a Last Call for the status change and an
associated status-change document. Due to this being a somewhat
unusual case (RFC 3716 is an IAB document, and the changes was
approved by the IAB), this step was missed.

This "Moved to Historic" announcement has been reissued to note this fact.


        
        RFC 3716

        Title:      IETF in the Large: Administration 
                    and Execution 
        Author:     IAB Advisory Committee
        Status:     Historic
        Stream:     IAB
        Date:       March 2004
        Mailbox:    iab@iab.org
        Pages:      40
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-iab-advcomm-01.txt

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

        DOI:        10.17487/RFC3716

In the fall of 2003, the IETF Chair and the IAB Chair formed an IAB Advisory Committee (AdvComm), with a mandate to review the existing IETF administrative structure and relationships (RFC Editor, IETF Secretariat, IANA) and to propose changes to the IETF management process or structure to improve the overall functioning of the IETF.  The AdvComm mandate did not include the standards process itself.  This memo provides information for the Internet community. 

This document is a product of the Internet Architecture Board.


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

From rfc-dist-bounces@rfc-editor.org  Wed Mar 11 15:55:12 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 C505D3A09BD for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 11 Mar 2020 15:55:12 -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 5ZpMr-8CDUQY for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 11 Mar 2020 15:55: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 7C6613A09AB for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 11 Mar 2020 15:55:11 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 738FBF4073C; Wed, 11 Mar 2020 15:55: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 E5000F4073B; Wed, 11 Mar 2020 15:55: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: <20200311225505.E5000F4073B@rfc-editor.org>
Date: Wed, 11 Mar 2020 15:55:05 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8739_on_Support_for_Short-Term=2C_Autom?= =?utf-8?q?atically_Renewed_=28STAR=29_Certificates_in_the_Automated_Certi?= =?utf-8?q?ficate_Management_Environment_=28ACME=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, acme@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 8739

        Title:      Support for Short-Term, Automatically Renewed (STAR)
                    Certificates in the Automated Certificate 
                    Management Environment (ACME) 
        Author:     Y. Sheffer, 
                    D. Lopez,
                    O. Gonzalez de Dios, 
                    A. Pastor Perales,
                    T. Fossati
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    yaronf.ietf@gmail.com, 
                    diego.r.lopez@telefonica.com, 
                    oscar.gonzalezdedios@telefonica.com,
                    antonio.pastorperales@telefonica.com, 
                    thomas.fossati@arm.com
        Pages:      22
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-acme-star-11.txt

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

        DOI:        10.17487/RFC8739

Public key certificates need to be revoked when they are compromised,
that is, when the associated private key is exposed to an
unauthorized entity.  However, the revocation process is often
unreliable. An alternative to revocation is issuing a sequence of
certificates, each with a short validity period, and terminating the
sequence upon compromise.  This memo proposes an Automated
Certificate Management Environment (ACME) extension to enable the
issuance of Short-Term, Automatically Renewed (STAR) X.509
certificates.

This document is a product of the Automated Certificate Management Environment Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Wed Mar 11 15:55:30 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 4F6053A0A21 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 11 Mar 2020 15:55:30 -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 RnUoVZ1TZff4 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 11 Mar 2020 15:55:28 -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 ECADD3A0A1B for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 11 Mar 2020 15:55:28 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id AEEB8F40742; Wed, 11 Mar 2020 15:55:13 -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 543D2F40743; Wed, 11 Mar 2020 15:55:12 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200311225512.543D2F40743@rfc-editor.org>
Date: Wed, 11 Mar 2020 15:55:12 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8750_on_Implicit_Initialization_Vector_?= =?utf-8?q?=28IV=29_for_Counter-Based_Ciphers_in_Encapsulating_Security_Pa?= =?utf-8?q?yload_=28ESP=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: ipsec@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8750

        Title:      Implicit Initialization Vector (IV) for 
                    Counter-Based Ciphers in Encapsulating 
                    Security Payload (ESP) 
        Author:     D. Migault,
                    T. Guggemos,
                    Y. Nir
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    daniel.migault@ericsson.com, 
                    guggemos@nm.ifi.lmu.de, 
                    ynir.ietf@gmail.com
        Pages:      8
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ipsecme-implicit-iv-11.txt

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

        DOI:        10.17487/RFC8750

Encapsulating Security Payload (ESP) sends an initialization vector
(IV) in each packet. The size of the IV depends on the applied
transform and is usually 8 or 16 octets for the transforms defined at
the time this document was written. When used with IPsec, some
algorithms, such as AES-GCM, AES-CCM, and ChaCha20-Poly1305, take the
IV to generate a nonce that is used as an input parameter for
encrypting and decrypting. This IV must be unique but can be
predictable.  As a result, the value provided in the ESP Sequence
Number (SN) can be used instead to generate the nonce. This avoids
sending the IV itself and saves 8 octets per packet in the case of
AES-GCM, AES-CCM, and ChaCha20-Poly1305. This document describes how
to do this.

This document is a product of the IP Security Maintenance and Extensions Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Wed Mar 11 16:49:22 2020
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71D5F3A0C93 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 11 Mar 2020 16:49:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3pX0TXHPZfIO for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 11 Mar 2020 16:49:21 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A321A3A0C69 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 11 Mar 2020 16:49:16 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 83A31F4073C; Wed, 11 Mar 2020 16:49:11 -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 1FC88F4073B; Wed, 11 Mar 2020 16:49:10 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200311234910.1FC88F4073B@rfc-editor.org>
Date: Wed, 11 Mar 2020 16:49:10 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8752_on_Report_from_the_IAB_Workshop_on?= =?utf-8?q?_Exploring_Synergy_between_Content_Aggregation_and_the_Publishe?= =?utf-8?q?r_Ecosystem_=28ESCAPE=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 8752

        Title:      Report from the IAB Workshop on
                    Exploring Synergy between Content Aggregation 
                    and the Publisher Ecosystem (ESCAPE) 
        Author:     M. Thomson,
                    M. Nottingham
        Status:     Informational
        Stream:     IAB
        Date:       March 2020
        Mailbox:    mt@lowentropy.net, 
                    mnot@mnot.net
        Pages:      23
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-iab-escape-report-00.txt

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

        DOI:        10.17487/RFC8752

The Exploring Synergy between Content Aggregation and the Publisher
Ecosystem (ESCAPE) Workshop was convened by the Internet Architecture
Board (IAB) in July 2019. This report summarizes its significant
points of discussion and identifies topics that may warrant further
consideration.

Note that this document is a report on the proceedings of the
workshop.  The views and positions documented in this report are
those of the workshop participants and do not necessarily reflect IAB
views and positions.

This document is a product of the Internet Architecture Board.


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 Mar 13 22:24:42 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 7D0E23A0EB3 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 13 Mar 2020 22:24:42 -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 KsfQDosHbFPG for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 13 Mar 2020 22:24:39 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C05EE3A0E9F for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 13 Mar 2020 22:24:39 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 4AB24F40719; Fri, 13 Mar 2020 22:24:32 -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 9C64FF40717; Fri, 13 Mar 2020 22:24:30 -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: <20200314052430.9C64FF40717@rfc-editor.org>
Date: Fri, 13 Mar 2020 22:24:30 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8754_on_IPv6_Segment_Routing_Header_=28?= =?utf-8?q?SRH=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, ipv6@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 8754

        Title:      IPv6 Segment Routing Header (SRH) 
        Author:     C. Filsfils, Ed.,
                    D. Dukes, Ed.,
                    S. Previdi,
                    J. Leddy,
                    S. Matsushima,
                    D. Voyer
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    cfilsfil@cisco.com, 
                    ddukes@cisco.com, 
                    stefano@previdi.net,
                    john@leddy.net, 
                    satoru.matsushima@g.softbank.co.jp,                      
                    daniel.voyer@bell.ca
        Pages:      27
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-6man-segment-routing-header-26.txt

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

        DOI:        10.17487/RFC8754

Segment Routing can be applied to the IPv6 data plane using a new
type of Routing Extension Header called the Segment Routing Header
(SRH). This document describes the SRH and how it is used by nodes
that are Segment Routing (SR) capable.

This document is a product of the IPv6 Maintenance 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 Mar 14 09:45:30 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 E353C3A0781 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sat, 14 Mar 2020 09:45:30 -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 GSjMtO6ieBZf for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sat, 14 Mar 2020 09:45:29 -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 C2BD13A0780 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Sat, 14 Mar 2020 09:45:29 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id C27E0F406CA; Sat, 14 Mar 2020 09:45: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 0B10EF406C9; Sat, 14 Mar 2020 09:45:21 -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: <20200314164521.0B10EF406C9@rfc-editor.org>
Date: Sat, 14 Mar 2020 09:45:21 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8748_on_Registry_Fee_Extension_for_the_?= =?utf-8?q?Extensible_Provisioning_Protocol_=28EPP=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, regext@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 8748

        Title:      Registry Fee Extension for the 
                    Extensible Provisioning Protocol (EPP) 
        Author:     R. Carney, 
                    G. Brown,
                    J. Frakes
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    rcarney@godaddy.com, 
                    gavin.brown@centralnic.com, 
                    jothan@jothan.com
        Pages:      30
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-regext-epp-fees-20.txt

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

        DOI:        10.17487/RFC8748

Given the expansion of the DNS namespace and the proliferation of
novel business models, it is desirable to provide a method for
Extensible Provisioning Protocol (EPP) clients to query EPP servers
for the fees and credits associated with various billable
transactions and provide expected fees and credits for certain
commands and objects. This document describes an EPP extension
mapping for registry fees.

This document is a product of the Registration Protocols Extensions 
Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Wed Mar 18 11:34:42 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 7E22B3A19FD for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 18 Mar 2020 11:34:42 -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 XfRSaCA0WdgS for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 18 Mar 2020 11:34:40 -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 04CFD3A19FE for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 18 Mar 2020 11:34:40 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 08745F40738; Wed, 18 Mar 2020 11:34: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 77A00F40729; Wed, 18 Mar 2020 11:34:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200318183435.77A00F40729@rfc-editor.org>
Date: Wed, 18 Mar 2020 11:34:35 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8759_on_RTP_Payload_for_Timed_Text_Mark?= =?utf-8?q?up_Language_=28TTML=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, avt@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 8759

        Title:      RTP Payload for Timed Text 
                    Markup Language (TTML) 
        Author:     J. Sandford
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    james.sandford@bbc.co.uk
        Pages:      15
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-payload-rtp-ttml-06.txt

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

        DOI:        10.17487/RFC8759

This memo describes a Real-time Transport Protocol (RTP) payload
format for Timed Text Markup Language (TTML), an XML-based timed text
format from W3C. This payload format is specifically targeted at
streaming workflows using TTML.

This document is a product of the Audio/Video Transport Core Maintenance 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 Mar 19 10:47:33 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 AB0503A0C69 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 19 Mar 2020 10:47:33 -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 aKxx4qYJEZzn for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 19 Mar 2020 10:47:32 -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 175CC3A0C21 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 19 Mar 2020 10:47:32 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 0689BF40719; Thu, 19 Mar 2020 10:47: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 339EAF40718; Thu, 19 Mar 2020 10:47: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: <20200319174726.339EAF40718@rfc-editor.org>
Date: Thu, 19 Mar 2020 10:47:26 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8755_on_Using_Commercial_National_Secur?= =?utf-8?q?ity_Algorithm_Suite_Algorithms_in_Secure/Multipurpose_Internet_?= =?utf-8?q?Mail_Extensions?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, 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 8755

        Title:      Using Commercial National Security Algorithm 
                    Suite Algorithms in Secure/Multipurpose Internet
                    Mail Extensions 
        Author:     M. Jenkins
        Status:     Informational
        Stream:     Independent
        Date:       March 2020
        Mailbox:    mjjenki@nsa.gov
        Pages:      17
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-jenkins-cnsa-smime-profile-03.txt

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

        DOI:        10.17487/RFC8755

The United States Government has published the National Security
Agency (NSA) Commercial National Security Algorithm (CNSA) Suite,
which defines cryptographic algorithm policy for national security
applications. This document specifies the conventions for using the
United States National Security Agency's CNSA Suite algorithms in
Secure/Multipurpose Internet Mail Extensions (S/MIME) as specified in
RFC 8551. It applies to the capabilities, configuration, and
operation of all components of US National Security Systems that
employ S/MIME messaging. US National Security Systems are described
in NIST Special Publication 800-59. It is also appropriate for all
other US Government systems that process high-value information. It
is made publicly available for use by developers and operators of
these and any other system deployments.


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 Mar 19 14:59:32 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 1506C3A10A5 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 19 Mar 2020 14:59:32 -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 oz6kbJo4xkqa for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 19 Mar 2020 14:59:26 -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 395393A107C for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 19 Mar 2020 14:59:26 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id DAF41F4071F; Thu, 19 Mar 2020 14:59:20 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id AA600F4071C; Thu, 19 Mar 2020 14:59:19 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200319215919.AA600F4071C@rfc-editor.org>
Date: Thu, 19 Mar 2020 14:59:19 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8760_on_The_Session_Initiation_Protocol?= =?utf-8?q?_=28SIP=29_Digest_Access_Authentication_Scheme?=
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, sipcore@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 8760

        Title:      The Session Initiation Protocol (SIP) 
                    Digest Access Authentication Scheme 
        Author:     R. Shekh-Yusef
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    rifaat.ietf@gmail.com
        Pages:      9
        Updates:    RFC 3261

        I-D Tag:    draft-ietf-sipcore-digest-scheme-15.txt

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

        DOI:        10.17487/RFC8760

This document updates RFC 3261 by modifying the Digest Access
Authentication scheme used by the Session Initiation Protocol (SIP)
to add support for more secure digest algorithms, e.g., SHA-256 and
SHA-512/256, to replace the obsolete MD5 algorithm.

This document is a product of the Session Initiation Protocol Core 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 Mar 19 15:00:22 2020
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CABA63A119E for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 19 Mar 2020 15:00:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5l3f1mdrbXND for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 19 Mar 2020 15:00: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 579173A112E for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 19 Mar 2020 15:00:05 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 2A81BF40738; Thu, 19 Mar 2020 14:59:54 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id ABE82F40737; Thu, 19 Mar 2020 14:59:53 -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: <20200319215953.ABE82F40737@rfc-editor.org>
Date: Thu, 19 Mar 2020 14:59:53 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8762_on_Simple_Two-Way_Active_Measureme?= =?utf-8?q?nt_Protocol?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, ippm@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 8762

        Title:      Simple Two-Way Active Measurement Protocol 
        Author:     G. Mirsky,
                    G. Jun,
                    H. Nydell,
                    R. Foote
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    gregimirsky@gmail.com, 
                    guo.jun2@zte.com.cn, 
                    hnydell@accedian.com,
                    footer.foote@nokia.com
        Pages:      15
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ippm-stamp-10.txt

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

        DOI:        10.17487/RFC8762

This document describes the Simple Two-way Active Measurement
Protocol (STAMP), which enables the measurement of both one-way and
round-trip performance metrics, like delay, delay variation, and
packet loss.

This document is a product of the IP Performance Measurement 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 Mar 20 21:21:37 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 B5DDD3A1153 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 20 Mar 2020 21:21:37 -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 PsbXz4_Y1Qyi for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 20 Mar 2020 21:21:33 -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 BA2463A1154 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 20 Mar 2020 21:21:33 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 47ACAF40719; Fri, 20 Mar 2020 21:21: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 5078DF40713; Fri, 20 Mar 2020 21:21: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: <20200321042126.5078DF40713@rfc-editor.org>
Date: Fri, 20 Mar 2020 21:21:26 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8768_on_Constrained_Application_Protoco?= =?utf-8?q?l_=28CoAP=29_Hop-Limit_Option?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, core@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8768

        Title:      Constrained Application Protocol (CoAP) 
                    Hop-Limit Option 
        Author:     M. Boucadair, 
                    T. Reddy.K,
                    J. Shallow
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    mohamed.boucadair@orange.com, 
                    kondtir@gmail.com, 
                    supjps-ietf@jpshallow.com
        Pages:      8
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-core-hop-limit-07.txt

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

        DOI:        10.17487/RFC8768

The presence of Constrained Application Protocol (CoAP) proxies may
lead to infinite forwarding loops, which is undesirable. To prevent
and detect such loops, this document specifies the Hop-Limit CoAP
option.

This document is a product of the Constrained RESTful Environments Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Fri Mar 20 21:21:53 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 E6A0C3A115C for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 20 Mar 2020 21:21:52 -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 UH-uqJoZOIgI for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 20 Mar 2020 21:21:51 -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 9E0683A1158 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 20 Mar 2020 21:21:51 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 8419AF4072C; Fri, 20 Mar 2020 21:21:33 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 3D056F4071B; Fri, 20 Mar 2020 21:21:32 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200321042132.3D056F4071B@rfc-editor.org>
Date: Fri, 20 Mar 2020 21:21:32 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8769_on_Cryptographic_Message_Syntax_?= =?utf-8?q?=28CMS=29_Content_Types_for_Concise_Binary_Object_Representatio?= =?utf-8?q?n_=28CBOR=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 8769

        Title:      Cryptographic Message Syntax (CMS) Content Types
                    for Concise Binary Object Representation (CBOR)
        Author:     J. Schaad
        Status:     Informational
        Stream:     IETF
        Date:       March 2020
        Mailbox:    ietf@augustcellars.com
        Pages:      6
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-schaad-cbor-content-02.txt

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

        DOI:        10.17487/RFC8769

Concise Binary Object Representation (CBOR) is becoming a widely used
method of doing content encoding. The Cryptographic Message Syntax
(CMS) is still a widely used method of doing message-based security.
This document defines a set of content types for CMS that hold CBOR
content.


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 Mar 25 12:09: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 455D63A0DDC for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 25 Mar 2020 12:09: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 u8lbT8miSKa0 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 25 Mar 2020 12:09:34 -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 61AAC3A1089 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 25 Mar 2020 12:08:22 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 337FCF406D6; Wed, 25 Mar 2020 12:08:11 -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 03E36F406D4; Wed, 25 Mar 2020 12:08:11 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200325190811.03E36F406D4@rfc-editor.org>
Date: Wed, 25 Mar 2020 12:08:11 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8743_on_Multiple_Access_Management_Serv?= =?utf-8?q?ices_Multi-Access_Management_Services_=28MAMS=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 8743

        Title:      Multiple Access Management Services Multi-Access 
                    Management Services (MAMS) 
        Author:     S. Kanugovi, 
                    F. Baboescu,
                    J. Zhu,
                    S. Seo
        Status:     Informational
        Stream:     Independent
        Date:       March 2020
        Mailbox:    satish.k@nokia-bell-labs.com, 
                    florin.baboescu@broadcom.com, 
                    jing.z.zhu@intel.com,
                    sh.seo@kt.com
        Pages:      143
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-kanugovi-intarea-mams-framework-04.txt

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

        DOI:        10.17487/RFC8743

In multiconnectivity scenarios, the clients can simultaneously
connect to multiple networks based on different access technologies
and network architectures like Wi-Fi, LTE, and DSL.  Both the quality
of experience of the users and the overall network utilization and
efficiency may be improved through the smart selection and
combination of access and core network paths that can dynamically
adapt to changing network conditions.

This document presents a unified problem statement and introduces a
solution for managing multiconnectivity.  The solution has been
developed by the authors based on their experiences in multiple
standards bodies, including the IETF and the 3GPP.  However, this
document is not an Internet Standards Track specification, and it
does not represent the consensus opinion of the IETF.

This document describes requirements, solution principles, and the
architecture of the Multi-Access Management Services (MAMS)
framework. The MAMS framework aims to provide best performance while
being easy to implement in a wide variety of multiconnectivity
deployments.  It specifies the protocol for (1) flexibly selecting
the best combination of access and core network paths for the uplink
and downlink, and (2) determining the user-plane treatment (e.g.,
tunneling, encryption) and traffic distribution over the selected
links, to ensure network efficiency and the best possible application
performance.


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 Mar 25 18:37:00 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 8677D3A0CEF for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 25 Mar 2020 18:37:00 -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 sUAI0BePDUfy for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 25 Mar 2020 18:36:51 -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 816303A0D7B for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 25 Mar 2020 18:36:13 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 17E0DF4070B; Wed, 25 Mar 2020 18:36:02 -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 57EFCF406F7; Wed, 25 Mar 2020 18:36:01 -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: <20200326013601.57EFCF406F7@rfc-editor.org>
Date: Wed, 25 Mar 2020 18:36:01 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?Moved_to_Historic=3A_RFC_4431_on_The_DNSSEC?= =?utf-8?q?_Lookaside_Validation_=28DLV=29_DNS_Resource_Record?=
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: 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>

RFC 4431 has been reclassified as Historic.

        
        RFC 4431

        Title:      The DNSSEC Lookaside Validation (DLV) 
                    DNS Resource Record 
        Author:     M. Andrews,
                    S. Weiler
        Status:     Historic
        Stream:     IETF
        Date:       February 2006
        Pages:      4
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-andrews-dlv-dns-rr-01.txt

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

        DOI:        10.17487/RFC4431

This document defines a new DNS resource record, called the DNSSEC
Lookaside Validation (DLV) RR, for publishing DNSSEC trust anchors
outside of the DNS delegation chain.  

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

From rfc-dist-bounces@rfc-editor.org  Wed Mar 25 18:43: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 879F73A0771 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 25 Mar 2020 18:43: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 aaa1o3YUDRU0 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 25 Mar 2020 18:42:56 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C6F23A07B9 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 25 Mar 2020 18:42:22 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id B6692F4071D; Wed, 25 Mar 2020 18:41:52 -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 F4127F40716; Wed, 25 Mar 2020 18:41:51 -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: <20200326014151.F4127F40716@rfc-editor.org>
Date: Wed, 25 Mar 2020 18:41:51 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?Moved_to_Historic=3A_RFC_5047_on_DA=3A_Data?= =?utf-8?q?mover_Architecture_for_the_Internet_Small_Computer_System_Inter?= =?utf-8?q?face_=28iSCSI=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: 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>

RFC 5047 has been reclassified as Historic.

        
        RFC 5047

        Title:      DA: Datamover Architecture for the 
                    Internet Small Computer System Interface (iSCSI) 
        Author:     M. Chadalapaka,
                    J. Hufferd,
                    J. Satran,
                    H. Shah
        Status:     Historic
        Stream:     IETF
        Date:       October 2007
        Pages:      49
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ips-iwarp-da-05.txt

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

        DOI:        10.17487/RFC5047

The Internet Small Computer System Interface (iSCSI) is a SCSI
transport protocol that maps the SCSI family
of application protocols onto TCP/IP.  Datamover Architecture
for iSCSI (DA) defines an abstract model in which the
movement of data between iSCSI end nodes is logically
separated from the rest of the iSCSI protocol in order to
allow iSCSI to adapt to innovations available in new IP
transports.  While DA defines the architectural functions
required of the class of Datamover protocols, it does not
define any specific Datamover protocols.  Each such Datamover
protocol, defined in a separate document, provides a
reliable transport for all iSCSI PDUs, but actually moves the
data required for certain iSCSI PDUs without involving the
remote iSCSI layer itself.  This document begins with an
introduction of a few new abstractions, defines a layered
architecture for iSCSI and Datamover protocols, and then
models the interactions within an iSCSI end node between the
iSCSI layer and the Datamover layer that happen in order to
transparently perform remote data movement within an IP
fabric.  It is intended that this definition will help map
iSCSI to generic Remote Direct Memory Access (RDMA)-capable IP fabrics in the future
comprising TCP, the Stream Control Transmission Protocol (SCTP), and
possibly other underlying network transport layers, such as InfiniBand.  

This document is a product of the IP Storage Working Group of the IETF.

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

From rfc-dist-bounces@rfc-editor.org  Wed Mar 25 20:46:51 2020
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85E793A0DAF for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 25 Mar 2020 20:46:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5qeqkIHMQ6uS for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 25 Mar 2020 20:46:50 -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 310123A0DBC for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 25 Mar 2020 20:46:50 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id B24CFF406F7; Wed, 25 Mar 2020 20:46:38 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 6000) id D72ECF406F7; Wed, 25 Mar 2020 20:46:36 -0700 (PDT)
Date: Wed, 25 Mar 2020 20:46:36 -0700
From: RFC Editor <rfc-editor@rfc-editor.org>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Message-ID: <20200326034636.GA5356@rfc-editor.org>
References: <20200326014151.F4127F40716@rfc-editor.org>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20200326014151.F4127F40716@rfc-editor.org>
User-Agent: Mutt/1.10.1 (2018-07-13)
Subject: [rfc-dist] Correction: RFC 5047 NOT moved to Historic -- Re: Moved to Historic: RFC 5047 on DA: Datamover Architecture for the Internet Small Computer System Interface (iSCSI)
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: RFC Editor <rfc-editor@rfc-editor.org>
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>

Greetings all,

Please disregard this message - this document has not been moved to
Historic.  

Apoloiges for any confusion.

RFC Editor/sg

On Wed, Mar 25, 2020 at 06:41:51PM -0700, rfc-editor@rfc-editor.org wrote:
> RFC 5047 has been reclassified as Historic.
> 
>         
>         RFC 5047
> 
>         Title:      DA: Datamover Architecture for the 
>                     Internet Small Computer System Interface (iSCSI) 
>         Author:     M. Chadalapaka,
>                     J. Hufferd,
>                     J. Satran,
>                     H. Shah
>         Status:     Historic
>         Stream:     IETF
>         Date:       October 2007
>         Pages:      49
>         Updates/Obsoletes/SeeAlso:   None
> 
>         I-D Tag:    draft-ietf-ips-iwarp-da-05.txt
> 
>         URL:        https://www.rfc-editor.org/info/rfc5047
> 
>         DOI:        10.17487/RFC5047
> 
> The Internet Small Computer System Interface (iSCSI) is a SCSI
> transport protocol that maps the SCSI family
> of application protocols onto TCP/IP.  Datamover Architecture
> for iSCSI (DA) defines an abstract model in which the
> movement of data between iSCSI end nodes is logically
> separated from the rest of the iSCSI protocol in order to
> allow iSCSI to adapt to innovations available in new IP
> transports.  While DA defines the architectural functions
> required of the class of Datamover protocols, it does not
> define any specific Datamover protocols.  Each such Datamover
> protocol, defined in a separate document, provides a
> reliable transport for all iSCSI PDUs, but actually moves the
> data required for certain iSCSI PDUs without involving the
> remote iSCSI layer itself.  This document begins with an
> introduction of a few new abstractions, defines a layered
> architecture for iSCSI and Datamover protocols, and then
> models the interactions within an iSCSI end node between the
> iSCSI layer and the Datamover layer that happen in order to
> transparently perform remote data movement within an IP
> fabric.  It is intended that this definition will help map
> iSCSI to generic Remote Direct Memory Access (RDMA)-capable IP fabrics in the future
> comprising TCP, the Stream Control Transmission Protocol (SCTP), and
> possibly other underlying network transport layers, such as InfiniBand.  
> 
> This document is a product of the IP Storage Working Group of the IETF.
> 
> 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

From rfc-dist-bounces@rfc-editor.org  Wed Mar 25 20:49: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 90F133A0E0A for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 25 Mar 2020 20:49: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 BL_StPA5eWSf for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 25 Mar 2020 20:49: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 7425F3A0E21 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 25 Mar 2020 20:49:13 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 1E53DF406F7; Wed, 25 Mar 2020 20:49:02 -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 24F68F406F7; Wed, 25 Mar 2020 20:49:01 -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: <20200326034901.24F68F406F7@rfc-editor.org>
Date: Wed, 25 Mar 2020 20:49:01 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_5074_on_DNSSEC_Lookaside_Validation_=28?= =?utf-8?q?DLV=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: 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>

RFC 5074 has been reclassified as Historic.

        
        RFC 5074

        Title:      DNSSEC Lookaside Validation (DLV) 
        Author:     S. Weiler
        Status:     Historic
        Stream:     IETF
        Date:       November 2007
        Pages:      11
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-weiler-dnssec-dlv-04.txt

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

        DOI:        10.17487/RFC5074

DNSSEC Lookaside Validation (DLV) is a mechanism for publishing DNS
Security (DNSSEC) trust anchors outside of the DNS delegation chain.
It allows validating resolvers to validate DNSSEC-signed data from
zones whose ancestors either aren't signed or don't publish
Delegation Signer (DS) records for their children. 


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

From rfc-dist-bounces@rfc-editor.org  Fri Mar 27 10:31: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 D7DF83A0A07 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 27 Mar 2020 10:31: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=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 XV8tWfROzuBZ for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 27 Mar 2020 10:31: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 C177C3A0C25 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 27 Mar 2020 10:31:25 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id BD7F4F40722; Fri, 27 Mar 2020 10:31:12 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 5CFCDF40720; Fri, 27 Mar 2020 10:31:11 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200327173111.5CFCDF40720@rfc-editor.org>
Date: Fri, 27 Mar 2020 10:31:11 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8749_on_Moving_DNSSEC_Lookaside_Validat?= =?utf-8?q?ion_=28DLV=29_to_Historic_Status?=
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 8749

        Title:      Moving DNSSEC Lookaside Validation (DLV) 
                    to Historic Status 
        Author:     W. Mekking,
                    D. Mahoney
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    matthijs@isc.org, 
                    dmahoney@isc.org
        Pages:      6
        Updates:    RFC 6698, RFC 6840

        I-D Tag:    draft-ietf-dnsop-obsolete-dlv-02.txt

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

        DOI:        10.17487/RFC8749

This document retires DNSSEC Lookaside Validation (DLV) and
reclassifies RFCs 4431 and 5074 as Historic. Furthermore, this
document updates RFC 6698 by excluding the DLV resource record from
certificates and updates RFC 6840 by excluding the DLV registries
from the trust anchor selection.

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 Mar 27 10:46:00 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 0DA563A0F84 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 27 Mar 2020 10:46:00 -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 HMM-Z2GWkuCe for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 27 Mar 2020 10:45:58 -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 157953A0FBC for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 27 Mar 2020 10:45:56 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 016C5F40724; Fri, 27 Mar 2020 10:45:43 -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 8B8BBF40722; Fri, 27 Mar 2020 10:45:42 -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: <20200327174542.8B8BBF40722@rfc-editor.org>
Date: Fri, 27 Mar 2020 10:45:42 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8757_on_Dynamic_Link_Exchange_Protocol_?= =?utf-8?q?=28DLEP=29_Latency_Range_Extension?=
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, manet@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 8757

        Title:      Dynamic Link Exchange Protocol (DLEP) 
                    Latency Range Extension 
        Author:     B. Cheng,
                    L. Berger, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    bcheng@ll.mit.edu, 
                    lberger@labn.net
        Pages:      5
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-manet-dlep-latency-extension-05.txt

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

        DOI:        10.17487/RFC8757

This document defines an extension to the Dynamic Link Exchange
Protocol (DLEP) to provide the range of latency that can be
experienced on a link.

This document is a product of the Mobile Ad-hoc Networks 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 Mar 27 11:29: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 EA22B3A0814 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 27 Mar 2020 11:29:02 -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 iHlZwvlwtMbh for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 27 Mar 2020 11:29: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 2D76A3A0524 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 27 Mar 2020 11:29:01 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 148D6F406D1; Fri, 27 Mar 2020 11:28:48 -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 2D5E1F40725; Fri, 27 Mar 2020 11:28: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: <20200327182847.2D5E1F40725@rfc-editor.org>
Date: Fri, 27 Mar 2020 11:28:47 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8756_on_Commercial_National_Security_Al?= =?utf-8?q?gorithm_=28CNSA=29_Suite_Profile_of_Certificate_Management_over?= =?utf-8?q?_CMS?=
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 8756

        Title:      Commercial National Security Algorithm (CNSA) 
                    Suite Profile of Certificate Management over 
                    CMS 
        Author:     M. Jenkins,
                    L. Zieglar
        Status:     Informational
        Stream:     Independent
        Date:       March 2020
        Mailbox:    mjjenki@nsa.gov, 
                    llziegl@tycho.ncsc.mil
        Pages:      17
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-jenkins-cnsa-cmc-profile-05.txt

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

        DOI:        10.17487/RFC8756

This document specifies a profile of the Certificate Management over
CMS (CMC) protocol for managing X.509 public key certificates in
applications that use the Commercial National Security Algorithm
(CNSA) Suite published by the United States Government. 

The profile applies to the capabilities, configuration, and operation
of all components of US National Security Systems that manage X.509
public key certificates over CMS.  It is also appropriate for all
other US Government systems that process high-value information. 

The profile is made publicly available here for use by developers and
operators of these and any other system deployments.


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  Sun Mar 29 14:52:15 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 2CC773A0DB4 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sun, 29 Mar 2020 14:52:15 -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 Hfn3noE3m-Nw for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sun, 29 Mar 2020 14:52:14 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 064153A0DB3 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Sun, 29 Mar 2020 14:52:13 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D030CF4073E; Sun, 29 Mar 2020 14:52:11 -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 12A34F4073D; Sun, 29 Mar 2020 14:52:11 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200329215211.12A34F4073D@rfc-editor.org>
Date: Sun, 29 Mar 2020 14:52:11 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8745_on_Path_Computation_Element_Commun?= =?utf-8?q?ication_Protocol_=28PCEP=29_Extensions_for_Associating_Working_?= =?utf-8?q?and_Protection_Label_Switched_Paths_=28LSPs=29_with_Stateful_PC?= =?utf-8?q?E?=
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 8745

        Title:      Path Computation Element Communication Protocol 
                    (PCEP) Extensions for Associating Working and 
                    Protection Label Switched Paths (LSPs) with 
                    Stateful PCE 
        Author:     H. Ananthakrishnan,
                    S. Sivabalan,
                    C. Barth,
                    I. Minei,
                    M. Negi
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    hari@netflix.com, 
                    msiva@cisco.com, 
                    cbarth@juniper.net,
                    inaminei@google.com, 
                    mahend.ietf@gmail.com
        Pages:      15
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-stateful-path-protection-11.txt

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

        DOI:        10.17487/RFC8745

An active stateful Path Computation Element (PCE) is capable of
computing as well as controlling via Path Computation Element
Communication Protocol (PCEP) Multiprotocol Label Switching Traffic
Engineering (MPLS-TE) Label Switched Paths (LSPs). Furthermore, it is
also possible for an active stateful PCE to create, maintain, and
delete LSPs. This document defines the PCEP extension to associate
two or more LSPs to provide end-to-end path protection.

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  Sun Mar 29 14:52:53 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 D70113A0E60 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sun, 29 Mar 2020 14:52:53 -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 u8M091soQ37p for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sun, 29 Mar 2020 14:52:52 -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 B580B3A0E18 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Sun, 29 Mar 2020 14:52:41 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 1CDC1F40749; Sun, 29 Mar 2020 14:52:40 -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 242D1F40745; Sun, 29 Mar 2020 14:52:39 -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: <20200329215239.242D1F40745@rfc-editor.org>
Date: Sun, 29 Mar 2020 14:52:39 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8773_on_TLS_1=2E3_Extension_for_Certifi?= =?utf-8?q?cate-Based_Authentication_with_an_External_Pre-Shared_Key?=
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, tls@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 8773

        Title:      TLS 1.3 Extension for Certificate-Based 
                    Authentication with an External Pre-Shared Key 
        Author:     R. Housley
        Status:     Experimental
        Stream:     IETF
        Date:       March 2020
        Mailbox:    housley@vigilsec.com
        Pages:      11
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tls-tls13-cert-with-extern-psk-07.txt

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

        DOI:        10.17487/RFC8773

This document specifies a TLS 1.3 extension that allows a server to
authenticate with a combination of a certificate and an external
pre-shared key (PSK).

This document is a product of the Transport Layer Security 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  Mon Mar 30 21:34:31 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 A77A73A1A99 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 30 Mar 2020 21:34:31 -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 s0Fkl8g80coG for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 30 Mar 2020 21:34:30 -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 774333A1A97 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 30 Mar 2020 21:34:30 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 01D47F406CE; Mon, 30 Mar 2020 21:34: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 A4F3FF406CD; Mon, 30 Mar 2020 21:34:25 -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: <20200331043425.A4F3FF406CD@rfc-editor.org>
Date: Mon, 30 Mar 2020 21:34:25 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8684_on_TCP_Extensions_for_Multipath_Op?= =?utf-8?q?eration_with_Multiple_Addresses?=
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: multipathtcp@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 8684

        Title:      TCP Extensions for Multipath Operation 
                    with Multiple Addresses 
        Author:     A. Ford, 
                    C. Raiciu,
                    M. Handley, 
                    O. Bonaventure,
                    C. Paasch
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    alan.ford@gmail.com, 
                    costin.raiciu@cs.pub.ro, 
                    m.handley@cs.ucl.ac.uk,  
                    olivier.bonaventure@uclouvain.be, 
                    cpaasch@apple.com
        Pages:      68
        Obsoletes:  RFC 6824

        I-D Tag:    draft-ietf-mptcp-rfc6824bis-18.txt

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

        DOI:        10.17487/RFC8684

TCP/IP communication is currently restricted to a single path per
connection, yet multiple paths often exist between peers. The
simultaneous use of these multiple paths for a TCP/IP session would
improve resource usage within the network and thus improve user
experience through higher throughput and improved resilience to
network failure.

Multipath TCP provides the ability to simultaneously use multiple
paths between peers. This document presents a set of extensions to
traditional TCP to support multipath operation. The protocol offers
the same type of service to applications as TCP (i.e., a reliable
bytestream), and it provides the components necessary to establish
and use multiple TCP flows across potentially disjoint paths.

This document specifies v1 of Multipath TCP, obsoleting v0 as
specified in RFC 6824, through clarifications and modifications
primarily driven by deployment experience.

This document is a product of the Multipath TCP 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 Mar 31 11:34:49 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 F1F613A283F for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 31 Mar 2020 11:34:48 -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 3Jrz2jBKeEI5 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 31 Mar 2020 11:34:47 -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 553373A2849 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 31 Mar 2020 11:34:21 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 3C03FF40722; Tue, 31 Mar 2020 11:34:17 -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 89B39F40721; Tue, 31 Mar 2020 11:34:15 -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: <20200331183415.89B39F40721@rfc-editor.org>
Date: Tue, 31 Mar 2020 11:34:15 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8751_on_Hierarchical_Stateful_Path_Comp?= =?utf-8?q?utation_Element_=28PCE=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, 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 8751

        Title:      Hierarchical Stateful Path Computation Element (PCE) 
        Author:     D. Dhody,
                    Y. Lee,
                    D. Ceccarelli,
                    J. Shin,
                    D. King
        Status:     Informational
        Stream:     IETF
        Date:       March 2020
        Mailbox:    dhruv.ietf@gmail.com, 
                    younglee.tx@gmail.com, 
                    daniele.ceccarelli@ericsson.com,
                    jongyoon.shin@sk.com, 
                    d.king@lancaster.ac.uk
        Pages:      21
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-stateful-hpce-15.txt

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

        DOI:        10.17487/RFC8751

A stateful Path Computation Element (PCE) maintains information on
the current network state received from the Path Computation Clients
(PCCs), including computed Label Switched Paths (LSPs), reserved
resources within the network, and pending path computation requests.
This information may then be considered when computing the path for a
new traffic-engineered LSP or for any associated/dependent LSPs. The
path-computation response from a PCE helps the PCC to gracefully
establish the computed LSP.

The Hierarchical Path Computation Element (H-PCE) architecture allows
the optimum sequence of interconnected domains to be selected and
network policy to be applied if applicable, via the use of a
hierarchical relationship between PCEs.

Combining the capabilities of stateful PCE and the hierarchical PCE
would be advantageous. This document describes general considerations
and use cases for the deployment of stateful, but not stateless, PCEs
using the hierarchical PCE architecture.

This document is a product of the Path Computation Element Working Group of the IETF.


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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Tue Mar 31 15:34:01 2020
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96A323A0BFC for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 31 Mar 2020 15:34:01 -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 FdcxfTZmflgZ for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 31 Mar 2020 15:33:59 -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 A1F873A0BF9 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 31 Mar 2020 15:33:59 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5938AF40738; Tue, 31 Mar 2020 15:33:55 -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 59D67F40737; Tue, 31 Mar 2020 15:33: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: <20200331223354.59D67F40737@rfc-editor.org>
Date: Tue, 31 Mar 2020 15:33:54 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8767_on_Serving_Stale_Data_to_Improve_D?= =?utf-8?q?NS_Resiliency?=
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 8767

        Title:      Serving Stale Data to Improve DNS Resiliency 
        Author:     D. Lawrence,
                    W. Kumari,
                    P. Sood
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2020
        Mailbox:    tale@dd.org, 
                    warren@kumari.net, 
                    puneets@google.com
        Pages:      12
        Updates:    RFC 1034, RFC 1035, RFC 2181

        I-D Tag:    draft-ietf-dnsop-serve-stale-10.txt

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

        DOI:        10.17487/RFC8767

This document defines a method (serve-stale) for recursive resolvers
to use stale DNS data to avoid outages when authoritative nameservers
cannot be reached to refresh expired data. One of the motivations for
serve-stale is to make the DNS more resilient to DoS attacks and
thereby make them less attractive as an attack vector. This document
updates the definitions of TTL from RFCs 1034 and 1035 so that data
can be kept in the cache beyond the TTL expiry; it also updates RFC
2181 by interpreting values with the high-order bit set as being
positive, rather than 0, and suggests a cap of 7 days.

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
