
From rfc-dist-bounces@rfc-editor.org  Tue Jun  5 15:14:16 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C0DF130DEB for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  5 Jun 2018 15:14:16 -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 ghunf1IzkeH3 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  5 Jun 2018 15:14:15 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67242130DE2 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue,  5 Jun 2018 15:14:15 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id A9FC0B81619; Tue,  5 Jun 2018 15:13:45 -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 7E731B8160F; Tue,  5 Jun 2018 15:13:43 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180605221343.7E731B8160F@rfc-editor.org>
Date: Tue,  5 Jun 2018 15:13:43 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?Moved_to_Proposed_Standard=3A_RFC_8279_on_M?= =?utf-8?q?ulticast_Using_Bit_Index_Explicit_Replication_=28BIER=29?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.26
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: bier@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>

RFC 8279 has been reclassified as Proposed Standard.

        
        RFC 8279

        Title:      Multicast Using Bit Index Explicit 
                    Replication (BIER) 
        Author:     IJ. Wijnands, Ed.,
                    E. Rosen, Ed.,
                    A. Dolganow,
                    T. Przygienda,
                    S. Aldrin
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2017
        Pages:      43
        Characters: 97283
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bier-architecture-08.txt

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

        DOI:        10.17487/RFC8279

This document specifies a new architecture for the forwarding of
multicast data packets.  It provides optimal forwarding of multicast
packets through a "multicast domain".  However, it does not require a
protocol for explicitly building multicast distribution trees, nor
does it require intermediate nodes to maintain any per-flow state.
This architecture is known as "Bit Index Explicit Replication"
(BIER).  When a multicast data packet enters the domain, the ingress
router determines the set of egress routers to which the packet needs
to be sent.  The ingress router then encapsulates the packet in a
BIER header.  The BIER header contains a bit string in which each bit
represents exactly one egress router in the domain; to forward the
packet to a given set of egress routers, the bits corresponding to
those routers are set in the BIER header.  The procedures for
forwarding a packet based on its BIER header are specified in this
document.  Elimination of the per-flow state and the explicit
tree-building protocols results in a considerable simplification.

This document is a product of the Bit Indexed Explicit Replication Working Group of the IETF.


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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Tue Jun  5 15:14:35 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 405CD1311D3 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  5 Jun 2018 15:14:35 -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 9AfOtAxT7K2A for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  5 Jun 2018 15:14: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 AA50E1311CC for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue,  5 Jun 2018 15:14:33 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 73C73B81634; Tue,  5 Jun 2018 15:13:50 -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 80C5FB81632; Tue,  5 Jun 2018 15:13:48 -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: <20180605221348.80C5FB81632@rfc-editor.org>
Date: Tue,  5 Jun 2018 15:13:48 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?Moved_to_Proposed_Standard=3A_RFC_8296_on_E?= =?utf-8?q?ncapsulation_for_Bit_Index_Explicit_Replication_=28BIER=29_in_M?= =?utf-8?q?PLS_and_Non-MPLS_Networks?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.26
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: bier@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>

RFC 8296 has been reclassified as Proposed Standard.

        
        RFC 8296

        Title:      Encapsulation for Bit Index Explicit 
                    Replication (BIER) in MPLS and Non-MPLS 
                    Networks 
        Author:     IJ. Wijnands, Ed.,
                    E. Rosen, Ed.,
                    A. Dolganow,
                    J. Tantsura,
                    S. Aldrin,
                    I. Meilik
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2018
        Pages:      24
        Characters: 47866
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bier-mpls-encapsulation-12.txt

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

        DOI:        10.17487/RFC8296

Bit Index Explicit Replication (BIER) is an architecture that
provides optimal multicast forwarding through a "multicast domain",
without requiring intermediate routers to maintain any per-flow state
or to engage in an explicit tree-building protocol.  When a multicast
data packet enters the domain, the ingress router determines the set
of egress routers to which the packet needs to be sent.  The ingress
router then encapsulates the packet in a BIER header.  The BIER
header contains a bit string in which each bit represents exactly one
egress router in the domain; to forward the packet to a given set of
egress routers, the bits corresponding to those routers are set in
the BIER header.  The details of the encapsulation depend on the type
of network used to realize the multicast domain.  This document
specifies a BIER encapsulation that can be used in an MPLS network
or, with slight differences, in a non-MPLS network.

This document is a product of the Bit Indexed Explicit Replication Working Group of the IETF.


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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Thu Jun  7 08:24:59 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33CB8130F47 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu,  7 Jun 2018 08:24:59 -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 kceEUCdMJ0IE for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu,  7 Jun 2018 08:24:54 -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 CE69C130F3B for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu,  7 Jun 2018 08:24:53 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id BC57DB812AF; Thu,  7 Jun 2018 08:24: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 1E17BB812A4; Thu,  7 Jun 2018 08:24:20 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180607152420.1E17BB812A4@rfc-editor.org>
Date: Thu,  7 Jun 2018 08:24:20 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8401_on_Bit_Index_Explicit_Replication_?= =?utf-8?q?=28BIER=29_Support_via_IS-IS?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.26
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, bier@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 8401

        Title:      Bit Index Explicit Replication (BIER) 
                    Support via IS-IS 
        Author:     L. Ginsberg, Ed.,
                    T. Przygienda,
                    S. Aldrin,
                    Z. Zhang
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2018
        Mailbox:    ginsberg@cisco.com, 
                    prz@juniper.net, 
                    aldrin.ietf@gmail.com,
                    zzhang@juniper.net
        Pages:      12
        Characters: 24287
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bier-isis-extensions-11.txt

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

        DOI:        10.17487/RFC8401

This document defines IS-IS extensions to support multicast
forwarding using the Bit Index Explicit Replication (BIER)
architecture.

This document is a product of the Bit Indexed Explicit Replication 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 Jun  8 22:55:14 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0C451310D4 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  8 Jun 2018 22:55:14 -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 aQBQvPwT1eCd for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  8 Jun 2018 22:55: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 44DC2130E45 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri,  8 Jun 2018 22:55:13 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 9CB02B80D1C; Fri,  8 Jun 2018 22:54:39 -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 F20D9B80CF5; Fri,  8 Jun 2018 22:54:37 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180609055437.F20D9B80CF5@rfc-editor.org>
Date: Fri,  8 Jun 2018 22:54:37 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8400_on_Extensions_to_RSVP-TE_for_Label?= =?utf-8?q?_Switched_Path_=28LSP=29_Egress_Protection?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, teas@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8400

        Title:      Extensions to RSVP-TE for Label 
                    Switched Path (LSP) Egress Protection 
        Author:     H. Chen,
                    A. Liu,
                    T. Saad,
                    F. Xu,
                    L. Huang
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2018
        Mailbox:    huaimo.chen@huawei.com, 
                    hliu@ciena.com, 
                    tsaad@cisco.com,
                    fengman.xu@verizon.com, 
                    huanglu@chinamobile.com
        Pages:      21
        Characters: 46913
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-teas-rsvp-egress-protection-16.txt

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

        DOI:        10.17487/RFC8400

This document describes extensions to Resource Reservation Protocol -
Traffic Engineering (RSVP-TE) for locally protecting the egress
node(s) of a Point-to-Point (P2P) or Point-to-Multipoint (P2MP)
Traffic Engineered (TE) Label Switched Path (LSP).

This document is a product of the Traffic Engineering Architecture and Signaling Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Mon Jun 11 10:27:17 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C9D4126CB6 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 11 Jun 2018 10:27:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2YFMnQ-oxI09 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 11 Jun 2018 10:27:15 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF009130FF1 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 11 Jun 2018 10:27:15 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 26D48B80EB6; Mon, 11 Jun 2018 10:27:14 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 7EE48B80EB4; Mon, 11 Jun 2018 10:27: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: <20180611172712.7EE48B80EB4@rfc-editor.org>
Date: Mon, 11 Jun 2018 10:27:12 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8385_on_Transparent_Interconnection_of_?= =?utf-8?q?Lots_of_Links_=28TRILL=29_Transparent_Transport_over_MPLS?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.26
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, trill@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 8385

        Title:      Transparent Interconnection of Lots of 
                    Links (TRILL) Transparent Transport over MPLS 
        Author:     M. Umair, 
                    S. Kingston Smiler,
                    D. Eastlake 3rd, 
                    L. Yong
        Status:     Informational
        Stream:     IETF
        Date:       June 2018
        Mailbox:    mohammed.umair2@gmail.com, 
                    kingstonsmiler@gmail.com, 
                    d3e3e3@gmail.com,  
                    lucyyong@gmail.com
        Pages:      16
        Characters: 34248
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-trill-transport-over-mpls-08.txt

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

        DOI:        10.17487/RFC8385

This document specifies methods to interconnect multiple TRILL
(Transparent Interconnection of Lots of Links) sites with an
intervening MPLS network using existing TRILL and VPLS (Virtual
Private LAN Service) standards.  This document addresses two problems:
1) providing connection between more than two TRILL sites that are
separated by an MPLS provider network and 2) providing a single
logical virtualized TRILL network for different tenants that are
separated by an MPLS provider network.

This document is a product of the Transparent Interconnection of Lots of Links Working Group of the IETF.


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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Mon Jun 18 23:12:38 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1C57128CF3 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 18 Jun 2018 23:12:37 -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 xhCd06R66HFS for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 18 Jun 2018 23:12:37 -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 06FB7124D68 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 18 Jun 2018 23:12:37 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id AD13CB8125D; Mon, 18 Jun 2018 23:12:35 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 28249B8125B; Mon, 18 Jun 2018 23:12:33 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180619061233.28249B8125B@rfc-editor.org>
Date: Mon, 18 Jun 2018 23:12:33 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8439_on_ChaCha20_and_Poly1305_for_IETF_?= =?utf-8?q?Protocols?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, cfrg@irtf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8439

        Title:      ChaCha20 and Poly1305 for IETF Protocols 
        Author:     Y. Nir,
                    A. Langley
        Status:     Informational
        Stream:     IRTF
        Date:       June 2018
        Mailbox:    ynir.ietf@gmail.com, 
                    agl@google.com
        Pages:      46
        Characters: 88847
        Obsoletes:  RFC 7539

        I-D Tag:    draft-nir-cfrg-rfc7539bis-04.txt

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

        DOI:        10.17487/RFC8439

This document defines the ChaCha20 stream cipher as well as the use
of the Poly1305 authenticator, both as stand-alone algorithms and as
a "combined mode", or Authenticated Encryption with Associated Data
(AEAD) algorithm.

RFC 7539, the predecessor of this document, was meant to serve as a
stable reference and an implementation guide.  It was a product of
the Crypto Forum Research Group (CFRG).  This document merges the
errata filed against RFC 7539 and adds a little text to the Security
Considerations section.

This document is a product of the Crypto Forum Research Group of the IRTF.


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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Mon Jun 25 22:43:43 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D9AA130EC6 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 25 Jun 2018 22:43:43 -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 lJRzsyR8vg6l for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 25 Jun 2018 22:43:42 -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 7778E130E66 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 25 Jun 2018 22:43:42 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 7142CB81229; Mon, 25 Jun 2018 22:43:37 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 32ADDB81227; Mon, 25 Jun 2018 22:43:36 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180626054336.32ADDB81227@rfc-editor.org>
Date: Mon, 25 Jun 2018 22:43:36 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8405_on_Shortest_Path_First_=28SPF=29_B?= =?utf-8?q?ack-Off_Delay_Algorithm_for_Link-State_IGPs?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.26
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, rtgwg@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 8405

        Title:      Shortest Path First (SPF) Back-Off Delay 
                    Algorithm for Link-State IGPs 
        Author:     B. Decraene,
                    S. Litkowski,
                    H. Gredler,
                    A. Lindem,
                    P. Francois,
                    C. Bowers
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2018
        Mailbox:    bruno.decraene@orange.com, 
                    stephane.litkowski@orange.com, 
                    hannes@rtbrick.com,
                    acee@cisco.com, 
                    pfrpfr@gmail.com,
                    cbowers@juniper.net
        Pages:      14
        Characters: 28446
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtgwg-backoff-algo-10.txt

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

        DOI:        10.17487/RFC8405

This document defines a standard algorithm to temporarily postpone or
"back off" link-state IGP Shortest Path First (SPF) computations.
This reduces the computational load and churn on IGP nodes when
multiple temporally close network events trigger multiple SPF
computations.

Having one standard algorithm improves interoperability by reducing
the probability and/or duration of transient forwarding loops during
the IGP convergence when the IGP reacts to multiple temporally close
IGP events.

This document is a product of the Routing Area Working Group Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Mon Jun 25 23:00:51 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE559130E87 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 25 Jun 2018 23:00:50 -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 RuYMbuN5LLMK for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 25 Jun 2018 23:00:49 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5085B127AC2 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 25 Jun 2018 23:00:49 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 4AD18B81320; Mon, 25 Jun 2018 23:00:44 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 0F676B8131F; Mon, 25 Jun 2018 23:00:43 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180626060043.0F676B8131F@rfc-editor.org>
Date: Mon, 25 Jun 2018 23:00:43 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8382_on_Shared_Bottleneck_Detection_for?= =?utf-8?q?_Coupled_Congestion_Control_for_RTP_Media?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.26
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, rmcat@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 8382

        Title:      Shared Bottleneck Detection for
                    Coupled Congestion Control for RTP Media 
        Author:     D. Hayes, Ed.,
                    S. Ferlin,
                    M. Welzl,
                    K. Hiorth
        Status:     Experimental
        Stream:     IETF
        Date:       June 2018
        Mailbox:    davidh@simula.no, 
                    simone@ferlin.io, 
                    michawe@ifi.uio.no,
                    kristahi@ifi.uio.no
        Pages:      25
        Characters: 49095
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rmcat-sbd-11.txt

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

        DOI:        10.17487/RFC8382

This document describes a mechanism to detect whether end-to-end data
flows share a common bottleneck.  This mechanism relies on summary
statistics that are calculated based on continuous measurements and
used as input to a grouping algorithm that runs wherever the
knowledge is needed.

This document is a product of the RTP Media Congestion Avoidance Techniques Working Group of the IETF.


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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Tue Jun 26 15:37:44 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A2CB130EFF for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 26 Jun 2018 15:37:44 -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 tX6ubgh9ODj6 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 26 Jun 2018 15:37:42 -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 844F9129C6A for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 26 Jun 2018 15:37:42 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 2693EB819BD; Tue, 26 Jun 2018 15:37:37 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 2568BB819BD; Tue, 26 Jun 2018 15:37:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180626223735.2568BB819BD@rfc-editor.org>
Date: Tue, 26 Jun 2018 15:37:35 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8406_on_Taxonomy_of_Coding_Techniques_f?= =?utf-8?q?or_Efficient_Network_Communications?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.26
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, nwcrg@irtf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8406

        Title:      Taxonomy of Coding Techniques for 
                    Efficient Network Communications 
        Author:     B. Adamson, 
                    C. Adjih,
                    J. Bilbao, 
                    V. Firoiu,
                    F. Fitzek, 
                    S. Ghanem,
                    E. Lochin, 
                    A. Masucci,
                    M-J. Montpetit, 
                    M. Pedersen, 
                    G. Peralta, 
                    V. Roca, Ed., 
                    P. Saxena, 
                    S. Sivakumar
        Status:     Informational
        Stream:     IRTF
        Date:       June 2018
        Mailbox:    brian.adamson@nrl.navy.mil, 
                    cedric.adjih@inria.fr, 
                    jbilbao@ikerlan.es,  
                    victor.firoiu@baesystems.com, 
                    frank.fitzek@tu-dresden.de,  
                    samah.ghanem@gmail.com, 
                    emmanuel.lochin@isae-supaero.fr, 
                    antoniamaria.masucci@orange.com, 
                    marie@mjmontpetit.com,  
                    mvp@es.aau.dk, 
                    gperalta@ikerlan.es, 
                    vincent.roca@inria.fr, 
                    paresh.saxena@ansur.es, 
                    ssenthil@cisco.com
        Pages:      15
        Characters: 32724
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-irtf-nwcrg-network-coding-taxonomy-08.txt

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

        DOI:        10.17487/RFC8406

This document summarizes recommended terminology for Network Coding
concepts and constructs.  It provides a comprehensive set of terms in
order to avoid ambiguities in future IRTF and IETF documents on
Network Coding.  This document is the product of the Coding for
Efficient Network Communications Research Group (NWCRG), and it is in
line with the terminology used by the RFCs produced by the Reliable
Multicast Transport (RMT) and FEC Framework (FECFRAME) IETF working
groups.

This document is a product of the NetWork Coding for Efficient Network Communications Research Group of the IRTF.


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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Tue Jun 26 22:36:32 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C238130F0D for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 26 Jun 2018 22:36:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=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 JzJX9IyxjUvh for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 26 Jun 2018 22:36: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 AD061130E85 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 26 Jun 2018 22:36:30 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 28A58B8122F; Tue, 26 Jun 2018 22:36:25 -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 547FBB8122F; Tue, 26 Jun 2018 22:36:23 -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: <20180627053623.547FBB8122F@rfc-editor.org>
Date: Tue, 26 Jun 2018 22:36:23 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8351_on_The_PKCS_=238_EncryptedPrivateK?= =?utf-8?q?eyInfo_Media_Type?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.26
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 8351

        Title:      The PKCS #8 EncryptedPrivateKeyInfo Media Type 
        Author:     S. Leonard
        Status:     Informational
        Stream:     Independent
        Date:       June 2018
        Mailbox:    dev+ietf@seantek.com
        Pages:      7
        Characters: 14797
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-seantek-pkcs8-encrypted-03.txt

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

        DOI:        10.17487/RFC8351

This document registers the application/pkcs8-encrypted media type
for the EncryptedPrivateKeyInfo type of PKCS #8.  An instance of this
media type carries a single encrypted private key, BER-encoded as a
single EncryptedPrivateKeyInfo value.


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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Tue Jun 26 22:36:49 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15880131172 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 26 Jun 2018 22:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pAVon4bXswPw for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 26 Jun 2018 22:36: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 75A3C131188 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 26 Jun 2018 22:36:47 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id BBA9FB81239; Tue, 26 Jun 2018 22:36:28 -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 68605B81236; Tue, 26 Jun 2018 22:36:27 -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: <20180627053627.68605B81236@rfc-editor.org>
Date: Tue, 26 Jun 2018 22:36:27 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8395_on_Extensions_to_BGP-Signaled_Pseu?= =?utf-8?q?dowires_to_Support_Flow-Aware_Transport_Labels?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, bess@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8395

        Title:      Extensions to BGP-Signaled Pseudowires to 
                    Support Flow-Aware Transport Labels 
        Author:     K. Patel,
                    S. Boutros,
                    J. Liste,
                    B. Wen,
                    J. Rabadan
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2018
        Mailbox:    keyur@arrcus.com, 
                    sboutros@vmware.com, 
                    jliste@cisco.com,
                    bin_wen@cable.comcast.com, 
                    jorge.rabadan@nokia.com
        Pages:      10
        Characters: 17404
        Updates:    RFC 4761

        I-D Tag:    draft-ietf-bess-fat-pw-bgp-04.txt

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

        DOI:        10.17487/RFC8395

This document defines protocol extensions required to synchronize flow
label states among Provider Edges (PEs) when using the BGP-based
signaling procedures.  These protocol extensions are equally
applicable to point-to-point Layer 2 Virtual Private Networks
(L2VPNs).  This document updates RFC 4761 by defining new flags in the
Control Flags field of the Layer2 Info Extended Community.

This document is a product of the BGP Enabled Services Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Wed Jun 27 14:41:55 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D627130E39 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 27 Jun 2018 14:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ch7T-LpRR_9e for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 27 Jun 2018 14:41:53 -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 C5714130E34 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 27 Jun 2018 14:41:53 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D3A0AB80CE4; Wed, 27 Jun 2018 14:41:47 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 37C14B80CD8; Wed, 27 Jun 2018 14:41:46 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180627214146.37C14B80CD8@rfc-editor.org>
Date: Wed, 27 Jun 2018 14:41:46 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?STD_92=2C_RFC_8010_on_Internet_Printing_Pro?= =?utf-8?q?tocol/1=2E1=3A_Encoding_and_Transport?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.26
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 8010 has been elevated to Internet Standard.

        STD 92        
        RFC 8010

        Title:      Internet Printing Protocol/1.1: Encoding and 
                    Transport 
        Author:     M. Sweet,
                    I. McDonald
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2017
        Mailbox:    msweet@apple.com, 
                    blueroofmusic@gmail.com
        Pages:      51
        Characters: 115605
        Obsoletes:  RFC 2910, RFC 3382
        See Also:   STD 92

        I-D Tag:    draft-sweet-rfc2910bis-10.txt

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

        DOI:        10.17487/RFC8010

The Internet Printing Protocol (IPP) is an application-level protocol
for distributed printing using Internet tools and technologies.  This
document defines the rules for encoding IPP operations, attributes,
and values into the Internet MIME media type called "application/ipp".  It
also defines the rules for transporting a message body
whose Content-Type is "application/ipp" over HTTP and/or HTTPS.  The
IPP data model and operation semantics are described in "Internet                                     
Printing Protocol/1.1: Model and Semantics" (RFC 8011).

This is now an Internet Standard.

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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Wed Jun 27 14:42:13 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CA13130F9C for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 27 Jun 2018 14:42:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CF6CiZbF-q7s for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 27 Jun 2018 14:42: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 8894E130F96 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 27 Jun 2018 14:42:11 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 8B088B80CEE; Wed, 27 Jun 2018 14:41:50 -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 25D17B80CED; Wed, 27 Jun 2018 14:41:49 -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: <20180627214149.25D17B80CED@rfc-editor.org>
Date: Wed, 27 Jun 2018 14:41:49 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?STD_92=2C_RFC_8011_on_Internet_Printing_Pro?= =?utf-8?q?tocol/1=2E1=3A_Model_and_Semantics?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.26
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>

This is now an Internet Standard.

        STD 92        
        RFC 8011

        Title:      Internet Printing Protocol/1.1:
                    Model and Semantics 
        Author:     M. Sweet,
                    I. McDonald
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2017
        Mailbox:    msweet@apple.com, 
                    blueroofmusic@gmail.com
        Pages:      221
        Characters: 535490
        Obsoletes:  RFC 2911, RFC 3381, RFC 3382
        See Also:   STD 92

        I-D Tag:    draft-sweet-rfc2911bis-11.txt

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

        DOI:        10.17487/RFC8011

The Internet Printing Protocol (IPP) is an application-level protocol
for distributed printing using Internet tools and technologies.  This
document describes a simplified model consisting of abstract objects,
attributes, and operations that is independent of encoding and
transport.  The model consists of several objects, including Printers
and Jobs.  Jobs optionally support multiple Documents.

IPP semantics allow End Users and Operators to query Printer
capabilities; submit Print Jobs; inquire about the status of Print
Jobs and Printers; and cancel, hold, and release Print Jobs.  IPP
semantics also allow Operators to pause and resume Jobs and Printers.

Security, internationalization, and directory issues are also
addressed by the model and semantics.  The IPP message encoding and
transport are described in "Internet Printing Protocol/1.1: Encoding                                  
and Transport" (RFC 8010).

This document obsoletes RFCs 2911, 3381, and 3382.

This is now an Internet Standard.

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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Thu Jun 28 14:34:30 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A6A91310F6 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 28 Jun 2018 14:34:30 -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 zI-yEM3i9_fe for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 28 Jun 2018 14:34: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 B36C21310CC for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 28 Jun 2018 14:34:28 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 3D2F2B80DBF; Thu, 28 Jun 2018 14:34:22 -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 5E208B80DBF; Thu, 28 Jun 2018 14:34:20 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180628213420.5E208B80DBF@rfc-editor.org>
Date: Thu, 28 Jun 2018 14:34:20 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8414_on_OAuth_2=2E0_Authorization_Serve?= =?utf-8?q?r_Metadata?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.26
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, oauth@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 8414

        Title:      OAuth 2.0 Authorization Server Metadata 
        Author:     M. Jones,
                    N. Sakimura,
                    J. Bradley
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2018
        Mailbox:    mbj@microsoft.com, 
                    n-sakimura@nri.co.jp, 
                    RFC8414@ve7jtb.com
        Pages:      23
        Characters: 53831
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-oauth-discovery-10.txt

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

        DOI:        10.17487/RFC8414

This specification defines a metadata format that an OAuth 2.0 client
can use to obtain the information needed to interact with an
OAuth 2.0 authorization server, including its endpoint locations and
authorization server capabilities.

This document is a product of the Web Authorization Protocol 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
