
From rfc-dist-bounces@rfc-editor.org  Wed Dec  4 21:23:54 2019
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 AA3AE120981 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed,  4 Dec 2019 21:23:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=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 gOgFPGDtASPT for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed,  4 Dec 2019 21:23:52 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5758A1200BA for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed,  4 Dec 2019 21:23:52 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 975B8F4071A; Wed,  4 Dec 2019 21:23:48 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 28A39F4071A; Wed,  4 Dec 2019 21:23:47 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191205052347.28A39F4071A@rfc-editor.org>
Date: Wed,  4 Dec 2019 21:23:47 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8674_on_The_=22safe=22_HTTP_Preference?=
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 8674

        Title:      The "safe" HTTP Preference 
        Author:     M. Nottingham
        Status:     Informational
        Stream:     Independent
        Date:       December 2019
        Mailbox:    mnot@mnot.net
        Pages:      7
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-nottingham-safe-hint-11.txt

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

        DOI:        10.17487/RFC8674

This specification defines a preference for HTTP requests that
expresses a desire to avoid objectionable content, according to the
definition of that term by the origin server.

This specification does not define a precise semantic for "safe".
Rather, the term is interpreted by the server and within the scope of
each web site that chooses to act upon this information.

Support for this preference by clients and servers is optional.


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 Dec  4 21:24:43 2019
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 F02211200C3 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed,  4 Dec 2019 21:24:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GjzBbI3zeC88 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed,  4 Dec 2019 21:24:41 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17ABD12095A for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed,  4 Dec 2019 21:24:36 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id E0AB6F4071B; Wed,  4 Dec 2019 21:24:32 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 83D8CF40724; Wed,  4 Dec 2019 21:24:31 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191205052431.83D8CF40724@rfc-editor.org>
Date: Wed,  4 Dec 2019 21:24:31 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8688_on_A_Session_Initiation_Protocol_?= =?utf-8?q?=28SIP=29_Response_Code_for_Rejected_Calls?=
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 8688

        Title:      A Session Initiation Protocol (SIP) 
                    Response Code for Rejected Calls 
        Author:     E.W. Burger, B. Nagda
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2019
        Mailbox:    eburger@standardstrack.com, 
                    nagdab@gmail.com
        Pages:      22
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sipcore-rejected-09.txt

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

        DOI:        10.17487/RFC8688

This document defines the 608 (Rejected) Session Initiation Protocol
(SIP) response code. This response code enables calling parties to
learn that an intermediary rejected their call attempt. No one will
deliver, and thus answer, the call. As a 6xx code, the caller will be
aware that future attempts to contact the same User Agent Server will
likely fail. The initial use case driving the need for the 608
response code is when the intermediary is an analytics engine. In
this case, the rejection is by a machine or other process. This
contrasts with the 607 (Unwanted) SIP response code in which a human
at the target User Agent Server indicates the user did not want the
call. In some jurisdictions, this distinction is important. This
document also defines the use of the Call-Info header field in 608
responses to enable rejected callers to contact entities that blocked
their calls in error. This provides a remediation mechanism for legal
callers that find their calls blocked.

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  Fri Dec  6 13:53:24 2019
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 DCA6212011E for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 13:53:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sI-2gtI2Xz7Z for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 13:53:23 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F228712002F for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri,  6 Dec 2019 13:53:22 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 510ECF40727; Fri,  6 Dec 2019 13:53:17 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 0A405F406F6; Fri,  6 Dec 2019 13:53:16 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191206215316.0A405F406F6@rfc-editor.org>
Date: Fri,  6 Dec 2019 13:53:16 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8660_on_Segment_Routing_with_the_MPLS_D?= =?utf-8?q?ata_Plane?=
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, spring@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 8660

        Title:      Segment Routing with the MPLS Data Plane 
        Author:     A. Bashandy, Ed.,
                    C. Filsfils, Ed.,
                    S. Previdi,
                    B. Decraene,
                    S. Litkowski,
                    R. Shakir
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2019
        Mailbox:    abashandy.ietf@gmail.com, 
                    cfilsfil@cisco.com, 
                    stefano@previdi.net,
                    bruno.decraene@orange.com, 
                    slitkows.ietf@gmail.com,
                    robjs@google.com
        Pages:      29
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-spring-segment-routing-mpls-22.txt

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

        DOI:        10.17487/RFC8660

Segment Routing (SR) leverages the source-routing paradigm.  A node
steers a packet through a controlled set of instructions, called
segments, by prepending the packet with an SR header.  In the MPLS
data plane, the SR header is instantiated through a label stack. This
document specifies the forwarding behavior to allow instantiating SR
over the MPLS data plane (SR-MPLS).

This document is a product of the Source Packet Routing in Networking Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Fri Dec  6 13:53:45 2019
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 5B6DF1209C8 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 13:53:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qpLr2fsXgEhx for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 13:53:44 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B4D8120169 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri,  6 Dec 2019 13:53:40 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 91ABEF4073E; Fri,  6 Dec 2019 13:53:23 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 8F7A4F4073C; Fri,  6 Dec 2019 13:53:22 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191206215322.8F7A4F4073C@rfc-editor.org>
Date: Fri,  6 Dec 2019 13:53:22 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8661_on_Segment_Routing_MPLS_Interworki?= =?utf-8?q?ng_with_LDP?=
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, spring@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 8661

        Title:      Segment Routing MPLS Interworking with 
                    LDP 
        Author:     A. Bashandy, Ed.,
                    C. Filsfils, Ed.,
                    S. Previdi, 
                    B. Decraene,
                    S. Litkowski
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2019
        Mailbox:    abashandy.ietf@gmail.com, 
                    cfilsfil@cisco.com, 
                    stefano@previdi.net,
                    bruno.decraene@orange.com, 
                    slitkows.ietf@gmail.com
        Pages:      21 
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-spring-segment-routing-ldp-interop-15.txt

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

        DOI:        10.17487/RFC8661

A Segment Routing (SR) node steers a packet through a controlled set
of instructions, called segments, by prepending the packet with an SR
header. A segment can represent any instruction, topological or
service based. SR allows enforcing a flow through any topological
path while maintaining per-flow state only at the ingress node to the
SR domain.

The Segment Routing architecture can be directly applied to the MPLS
data plane with no change in the forwarding plane. This document
describes how Segment Routing MPLS operates in a network where LDP is
deployed and in the case where SR-capable and non-SR-capable nodes
coexist.

This document is a product of the Source Packet Routing in Networking Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Fri Dec  6 13:54:04 2019
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 5D8A8120B55 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 13:54:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V8S73w-ugtDo for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 13:54:03 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4567120A28 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri,  6 Dec 2019 13:53:53 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id CEDF0F40742; Fri,  6 Dec 2019 13:53:31 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id E1BCFF40742; Fri,  6 Dec 2019 13:53:29 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191206215329.E1BCFF40742@rfc-editor.org>
Date: Fri,  6 Dec 2019 13:53:29 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8662_on_Entropy_Label_for_Source_Packet?= =?utf-8?q?_Routing_in_Networking_=28SPRING=29_Tunnels?=
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, mpls@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 8662

        Title:      Entropy Label for Source Packet Routing 
                    in Networking (SPRING) Tunnels 
        Author:     S. Kini,
                    K. Kompella,
                    S. Sivabalan,
                    S. Litkowski,
                    R. Shakir,
                    J. Tantsura
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2019
        Mailbox:    sriganeshkini@gmail.com, 
                    kireeti@juniper.net, 
                    msiva@cisco.com,
                    slitkows.ietf@gmail.com, 
                    robjs@google.com,
                    jefftant.ietf@gmail.com
        Pages:      22
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-spring-entropy-label-12.txt

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

        DOI:        10.17487/RFC8662

Segment Routing (SR) leverages the source-routing paradigm.  A node
steers a packet through an ordered list of instructions, called
segments. Segment Routing can be applied to the Multiprotocol Label
Switching (MPLS) data plane.  Entropy labels (ELs) are used in MPLS
to improve load-balancing. This document examines and describes how
ELs are to be applied to Segment Routing MPLS.

This document is a product of the Multiprotocol Label Switching Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Fri Dec  6 13:54:25 2019
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 06A2D120B88 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 13:54:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sJlPVcDzuaSS for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 13:54:24 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B885120A30 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri,  6 Dec 2019 13:54:08 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 16563F4074C; Fri,  6 Dec 2019 13:53:39 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 697C4F4074B; Fri,  6 Dec 2019 13:53:38 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191206215338.697C4F4074B@rfc-editor.org>
Date: Fri,  6 Dec 2019 13:53:38 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8663_on_MPLS_Segment_Routing_over_IP?=
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, mpls@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 8663

        Title:      MPLS Segment Routing over IP 
        Author:     X. Xu,
                    S. Bryant,
                    A. Farrel,
                    S. Hassan,
                    W. Henderickx,
                    Z. Li
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2019
        Mailbox:    xiaohu.xxh@alibaba-inc.com, 
                    stewart.bryant@gmail.com, 
                    adrian@olddog.co.uk,
                    shassan@cisco.com, 
                    wim.henderickx@nokia.com,
                    lizhenbin@huawei.com
        Pages:      17
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-sr-over-ip-07.txt

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

        DOI:        10.17487/RFC8663

MPLS Segment Routing (SR-MPLS) is a method of source routing a packet
through an MPLS data plane by imposing a stack of MPLS labels on the
packet to specify the path together with any packet-specific
instructions to be executed on it.  SR-MPLS can be leveraged to
realize a source-routing mechanism across MPLS, IPv4, and IPv6 data
planes by using an MPLS label stack as a source-routing instruction
set while making no changes to SR-MPLS specifications and
interworking with SR-MPLS implementations.

This document describes how SR-MPLS-capable routers and IP-only
routers can seamlessly coexist and interoperate through the use of
SR-MPLS label stacks and IP encapsulation/tunneling such as
MPLS-over-UDP as defined in RFC 7510.

This document is a product of the Multiprotocol Label Switching Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Fri Dec  6 13:54:41 2019
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 5D829120AB2 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 13:54:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VKv_stnycvQh for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 13:54:40 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F21F120B4A for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri,  6 Dec 2019 13:54:23 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5462AF40752; Fri,  6 Dec 2019 13:53:43 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 672B9F4074E; Fri,  6 Dec 2019 13:53:42 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191206215342.672B9F4074E@rfc-editor.org>
Date: Fri,  6 Dec 2019 13:53:42 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8664_on_Path_Computation_Element_Commun?= =?utf-8?q?ication_Protocol_=28PCEP=29_Extensions_for_Segment_Routing?=
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 8664

        Title:      Path Computation Element Communication Protocol 
                    (PCEP) Extensions for Segment Routing 
        Author:     S. Sivabalan,
                    C. Filsfils,
                    J. Tantsura,
                    W. Henderickx,
                    J. Hardwick
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2019
        Mailbox:    msiva@cisco.com, 
                    cfilsfil@cisco.com, 
                    jefftant.ietf@gmail.com,
                    wim.henderickx@nokia.com, 
                    jonathan.hardwick@metaswitch.com
        Pages:      29
        Updates:    RFC 8408

        I-D Tag:    draft-ietf-pce-segment-routing-16.txt

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

        DOI:        10.17487/RFC8664

Segment Routing (SR) enables any head-end node to select any path
without relying on a hop-by-hop signaling technique (e.g., LDP or
RSVP-TE). It depends only on "segments" that are advertised by
link-state Interior Gateway Protocols (IGPs). An SR path can be
derived from a variety of mechanisms, including an IGP Shortest Path
Tree (SPT), an explicit configuration, or a Path Computation Element
(PCE). This document specifies extensions to the Path Computation
Element Communication Protocol (PCEP) that allow a stateful PCE to
compute and initiate Traffic-Engineering (TE) paths, as well as a
Path Computation Client (PCC) to request a path subject to certain
constraints and optimization criteria in SR networks.

This document updates RFC 8408.

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  Fri Dec  6 13:54:55 2019
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 76CE0120CBA for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 13:54:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VJ3aHhVj4TQ3 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 13:54:54 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA400120BF2 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri,  6 Dec 2019 13:54:36 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 9267AF4075A; Fri,  6 Dec 2019 13:53:51 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 75124F40737; Fri,  6 Dec 2019 13:53:50 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191206215350.75124F40737@rfc-editor.org>
Date: Fri,  6 Dec 2019 13:53:50 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8665_on_OSPF_Extensions_for_Segment_Rou?= =?utf-8?q?ting?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: lsr@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8665

        Title:      OSPF Extensions for Segment Routing 
        Author:     P. Psenak, Ed.,
                    S. Previdi, Ed.,
                    C. Filsfils,
                    H. Gredler,
                    R. Shakir,
                    W. Henderickx,
                    J. Tantsura
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2019
        Mailbox:    ppsenak@cisco.com, 
                    stefano@previdi.net, 
                    cfilsfil@cisco.com,
                    hannes@rtbrick.com, 
                    robjs@google.com,
                    wim.henderickx@nokia.com, 
                    jefftant.ietf@gmail.com
        Pages:      25
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ospf-segment-routing-extensions-27.txt

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

        DOI:        10.17487/RFC8665

Segment Routing (SR) allows a flexible definition of end-to-end paths
within IGP topologies by encoding paths as sequences of topological
subpaths called "segments". These segments are advertised by the
link-state routing protocols (IS-IS and OSPF).

This document describes the OSPFv2 extensions required for Segment
Routing.

This document is a product of the Open Shortest Path First IGP Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Fri Dec  6 13:55:14 2019
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 D696C12080F for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 13:55:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OMzWZygBF_Q4 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 13:55:13 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05894120A75 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri,  6 Dec 2019 13:54:51 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D0234F40766; Fri,  6 Dec 2019 13:54:02 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 690A4F4073B; Fri,  6 Dec 2019 13:54:01 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191206215401.690A4F4073B@rfc-editor.org>
Date: Fri,  6 Dec 2019 13:54:01 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8679_on_MPLS_Egress_Protection_Framewor?= =?utf-8?q?k?=
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, mpls@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 8679

        Title:      MPLS Egress Protection Framework 
        Author:     Y. Shen, 
                    M. Jeganathan,
                    B. Decraene, 
                    H. Gredler,
                    C. Michel,
                    H. Chen
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2019
        Mailbox:    yshen@juniper.net, 
                    minto@juniper.net, 
                    bruno.decraene@orange.com,
                    hannes@rtbrick.com, 
                    c.michel@telekom.de,
                    huaimo.chen@futurewei.com
        Pages:      25
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-egress-protection-framework-07.txt

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

        DOI:        10.17487/RFC8679

This document specifies a fast reroute framework for protecting
IP/MPLS services and MPLS transport tunnels against egress node and
egress link failures. For each type of egress failure, it defines the
roles of Point of Local Repair (PLR), protector, and backup egress
router and the procedures of establishing a bypass tunnel from a PLR
to a protector. It describes the behaviors of these routers in
handling an egress failure, including local repair on the PLR and
context-based forwarding on the protector. The framework can be used
to develop egress protection mechanisms to reduce traffic loss before
global repair reacts to an egress failure and control-plane protocols
converge on the topology changes due to the egress failure.

This document is a product of the Multiprotocol Label Switching Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Fri Dec  6 14:25:40 2019
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 E867E1209EE for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 14:25:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w57Th7CgLb6Y for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 14:25:38 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E272C120A22 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri,  6 Dec 2019 14:25:36 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 3ED5FF4073B; Fri,  6 Dec 2019 14:25:31 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id AD2BBF4073A; Fri,  6 Dec 2019 14:25:30 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191206222530.AD2BBF4073A@rfc-editor.org>
Date: Fri,  6 Dec 2019 14:25:30 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8666_on_OSPFv3_Extensions_for_Segment_R?= =?utf-8?q?outing?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: lsr@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8666

        Title:      OSPFv3 Extensions for Segment Routing 
        Author:     P. Psenak, Ed.,
                    S. Previdi, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2019
        Mailbox:    ppsenak@cisco.com, 
                    stefano@previdi.net
        Pages:      18
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ospf-ospfv3-segment-routing-extensions-23.txt

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

        DOI:        10.17487/RFC8666

Segment Routing (SR) allows a flexible definition of end-to-end paths
within IGP topologies by encoding paths as sequences of topological
subpaths called "segments". These segments are advertised by the
link-state routing protocols (IS-IS and OSPF).

This document describes the OSPFv3 extensions required for Segment
Routing with the MPLS data plane.

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

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Fri Dec  6 14:34:20 2019
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 56E0F12002F for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 14:34:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X-B-UXez6MNa for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 14:34:18 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E065D12008D for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri,  6 Dec 2019 14:34:18 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 3C260F40712; Fri,  6 Dec 2019 14:34:13 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 591A6F406F6; Fri,  6 Dec 2019 14:34:12 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191206223412.591A6F406F6@rfc-editor.org>
Date: Fri,  6 Dec 2019 14:34:12 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8667_on_IS-IS_Extensions_for_Segment_Ro?= =?utf-8?q?uting?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: lsr@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8667

        Title:      IS-IS Extensions for Segment Routing 
        Author:     S. Previdi, Ed.,
                    L. Ginsberg, Ed.,
                    C. Filsfils,
                    A. Bashandy,
                    H. Gredler,
                    B. Decraene
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2019
        Mailbox:    stefano@previdi.net, 
                    ginsberg@cisco.com, 
                    cfilsfil@cisco.com,
                    abashandy.ietf@gmail.com, 
                    hannes@rtbrick.com,
                    bruno.decraene@orange.com
        Pages:      28
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-isis-segment-routing-extensions-25.txt

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

        DOI:        10.17487/RFC8667

Segment Routing (SR) allows for a flexible definition of end-to-end
paths within IGP topologies by encoding paths as sequences of
topological sub-paths, called "segments". These segments are
advertised by the link-state routing protocols (IS-IS and OSPF).

This document describes the IS-IS extensions that need to be
introduced for Segment Routing operating on an MPLS data plane.

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

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Fri Dec  6 14:34:38 2019
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 436371209A6 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 14:34:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=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 G9CV6wkAMXBt for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 14:34:35 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A25241209D7 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri,  6 Dec 2019 14:34:34 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 7FE4EF4073E; Fri,  6 Dec 2019 14:34:29 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 6BB7FF4073E; Fri,  6 Dec 2019 14:34:28 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191206223428.6BB7FF4073E@rfc-editor.org>
Date: Fri,  6 Dec 2019 14:34:28 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8668_on_Advertising_Layer_2_Bundle_Memb?= =?utf-8?q?er_Link_Attributes_in_IS-IS?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: lsr@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8668

        Title:      Advertising Layer 2 Bundle Member 
                    Link Attributes in IS-IS 
        Author:     L. Ginsberg, Ed.,
                    A. Bashandy, 
                    C. Filsfils,
                    M. Nanduri,
                    E. Aries
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2019
        Mailbox:    ginsberg@cisco.com, 
                    abashandy.ietf@gmail.com, 
                    cf@cisco.com,
                    mohan.nanduri@oracle.com, 
                    exa@arrcus.com
        Pages:      17
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-isis-l2bundles-07.txt

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

        DOI:        10.17487/RFC8668

There are deployments where the Layer 3 interface on which IS-IS
operates is a Layer 2 interface bundle. Existing IS-IS advertisements
only support advertising link attributes of the Layer 3 interface. If
entities external to IS-IS wish to control traffic flows on the
individual physical links that comprise the Layer 2 interface bundle,
link attribute information about the bundle members is required.

This document introduces the ability for IS-IS to advertise the link
attributes of Layer 2 (L2) Bundle Members.

This document is a product of the IS-IS for IP Internets Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Fri Dec  6 14:34:52 2019
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 42E45120164 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 14:34:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QQzCrlIaM1Ko for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 14:34:49 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E614F1209B7 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri,  6 Dec 2019 14:34:48 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id C26BBF40745; Fri,  6 Dec 2019 14:34:43 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 15240F40737; Fri,  6 Dec 2019 14:34:43 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191206223443.15240F40737@rfc-editor.org>
Date: Fri,  6 Dec 2019 14:34:43 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8669_on_Segment_Routing_Prefix_Segment_?= =?utf-8?q?Identifier_Extensions_for_BGP?=
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, idr@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 8669

        Title:      Segment Routing Prefix Segment Identifier 
                    Extensions for BGP 
        Author:     S. Previdi,
                    C. Filsfils,
                    A. Lindem, Ed.,
                    A. Sreekantiah,
                    H. Gredler
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2019
        Mailbox:    stefano@previdi.net, 
                    cfilsfils@cisco.com, 
                    acee@cisco.com,
                    arjunhrs@gmail.com, 
                    hannes@rtbrick.com
        Pages:      15
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-idr-bgp-prefix-sid-27.txt

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

        DOI:        10.17487/RFC8669

Segment Routing (SR) leverages the source-routing paradigm. A node
steers a packet through an ordered list of instructions called
"segments". A segment can represent any instruction, topological or
service based. The ingress node prepends an SR header to a packet
containing a set of segment identifiers (SIDs). Each SID represents a
topological or service-based instruction. Per-flow state is
maintained only on the ingress node of the SR domain. An "SR domain"
is defined as a single administrative domain for global SID
assignment.

This document defines an optional, transitive BGP attribute for
announcing information about BGP Prefix Segment Identifiers (BGP
Prefix-SIDs) and the specification for SR-MPLS SIDs.

This document is a product of the Inter-Domain Routing Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Fri Dec  6 14:35:09 2019
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 43963120A2E for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 14:35:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=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 gZDi_AyjiSZG for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  6 Dec 2019 14:35:07 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D73CC120114 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri,  6 Dec 2019 14:35:03 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 10D62F40750; Fri,  6 Dec 2019 14:34:58 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 73152F4073B; Fri,  6 Dec 2019 14:34:57 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191206223457.73152F4073B@rfc-editor.org>
Date: Fri,  6 Dec 2019 14:34:57 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8670_on_BGP_Prefix_Segment_in_Large-Sca?= =?utf-8?q?le_Data_Centers?=
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, spring@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 8670

        Title:      BGP Prefix Segment in Large-Scale 
                    Data Centers 
        Author:     C. Filsfils, Ed.,
                    S. Previdi,
                    G. Dawra,
                    E. Aries,
                    P. Lapukhov
        Status:     Informational
        Stream:     IETF
        Date:       December 2019
        Mailbox:    cfilsfil@cisco.com, 
                    stefano@previdi.net, 
                    gdawra.ietf@gmail.com,
                    exa@arrcus.com, 
                    petr@fb.com
        Pages:      18
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-spring-segment-routing-msdc-11.txt

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

        DOI:        10.17487/RFC8670

This document describes the motivation for, and benefits of, applying
Segment Routing (SR) in BGP-based large-scale data centers. It
describes the design to deploy SR in those data centers for both the
MPLS and IPv6 data planes.

This document is a product of the Source Packet Routing in Networking Working Group of the IETF.


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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Wed Dec 11 11:01:14 2019
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 D335E120052 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 11 Dec 2019 11:01:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PvVVal6kWxb6 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 11 Dec 2019 11:01:13 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC3D8120127 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 11 Dec 2019 11:01:13 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 8FCAFF40712; Wed, 11 Dec 2019 11:01:02 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 49CC4F40710; Wed, 11 Dec 2019 11:01:02 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191211190102.49CC4F40710@rfc-editor.org>
Date: Wed, 11 Dec 2019 11:01:02 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8690_on_Clarification_of_Segment_ID_Sub?= =?utf-8?q?-TLV_Length_for_RFC_8287?=
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, mpls@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 8690

        Title:      Clarification of Segment ID Sub-TLV 
                    Length for RFC 8287 
        Author:     N. Nainar,
                    C. Pignataro,
                    F. Iqbal,
                    A. Vainshtein
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2019
        Mailbox:    naikumar@cisco.com, 
                    cpignata@cisco.com, 
                    faisal.ietf@gmail.com,
                    vainshtein.alex@gmail.com
        Pages:      7
        Updates:    RFC 8287

        I-D Tag:    draft-ietf-mpls-rfc8287-len-clarification-04.txt

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

        DOI:        10.17487/RFC8690

RFC 8287 defines the extensions to perform LSP Ping and Traceroute
for Segment Routing IGP-Prefix and IGP-Adjacency Segment Identifiers
(SIDs) with the MPLS data plane. RFC 8287 proposes three Target
Forwarding Equivalence Class (FEC) Stack sub-TLVs. While RFC 8287
defines the format and procedure to handle those sub-TLVs, it does
not sufficiently clarify how the length of the Segment ID sub-TLVs
should be computed to be included in the Length field of the
sub-TLVs. This ambiguity has resulted in interoperability issues.

This document updates RFC 8287 by clarifying the length of each of
the Segment ID sub-TLVs defined in RFC 8287.

This document is a product of the Multiprotocol Label Switching 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 Dec 11 14:35:20 2019
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 44576120019 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 11 Dec 2019 14:35:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UQbT7PhQ5gfk for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 11 Dec 2019 14:35:19 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 702491200B1 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 11 Dec 2019 14:35:19 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 12C93F40719; Wed, 11 Dec 2019 14:35:08 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id A300AF40719; Wed, 11 Dec 2019 14:35:06 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191211223506.A300AF40719@rfc-editor.org>
Date: Wed, 11 Dec 2019 14:35:06 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8692_on_Internet_X=2E509_Public_Key_Inf?= =?utf-8?q?rastructure=3A_Additional_Algorithm_Identifiers_for_RSASSA-PSS_?= =?utf-8?q?and_ECDSA_Using_SHAKEs?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: spasm@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8692

        Title:      Internet X.509 Public Key Infrastructure: 
                    Additional Algorithm Identifiers for RSASSA-PSS
                    and ECDSA Using SHAKEs 
        Author:     P. Kampanakis,
                    Q. Dang
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2019
        Mailbox:    pkampana@cisco.com, 
                    quynh.dang@nist.gov
        Pages:      14
        Updates:    RFC 3279

        I-D Tag:    draft-ietf-lamps-pkix-shake-15.txt

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

        DOI:        10.17487/RFC8692

Digital signatures are used to sign messages, X.509 certificates, and
Certificate Revocation Lists (CRLs). This document updates the
"Algorithms and Identifiers for the Internet X.509 Public Key
Infrastructure Certificate and Certificate Revocation List (CRL)
Profile" (RFC 3279) and describes the conventions for using the SHAKE
function family in Internet X.509 certificates and revocation lists
as one-way hash functions with the RSA Probabilistic signature and
Elliptic Curve Digital Signature Algorithm (ECDSA) signature
algorithms. The conventions for the associated subject public keys
are also described.

This document is a product of the Limited Additional Mechanisms for PKIX and SMIME Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Thu Dec 12 15:25:06 2019
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 5425E1208B5 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 12 Dec 2019 15:25:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=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 mg1MMn_eTgfs for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 12 Dec 2019 15:25:04 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 992AC12012A for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 12 Dec 2019 15:25:04 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 03F3CF40720; Thu, 12 Dec 2019 15:24:52 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 50E0DF4071E; Thu, 12 Dec 2019 15:24:50 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191212232450.50E0DF4071E@rfc-editor.org>
Date: Thu, 12 Dec 2019 15:24:50 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8685_on_Path_Computation_Element_Commun?= =?utf-8?q?ication_Protocol_=28PCEP=29_Extensions_for=C2=A0the=C2=A0Hierar?= =?utf-8?q?chical_Path_Computation_Element_=28H-PCE=29_Architecture?=
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="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

QSBuZXcgUmVxdWVzdCBmb3IgQ29tbWVudHMgaXMgbm93IGF2YWlsYWJsZSBpbiBvbmxpbmUgUkZD
IGxpYnJhcmllcy4KCiAgICAgICAgCiAgICAgICAgUkZDIDg2ODUKCiAgICAgICAgVGl0bGU6ICAg
ICAgUGF0aCBDb21wdXRhdGlvbiBFbGVtZW50IENvbW11bmljYXRpb24gUHJvdG9jb2wgCiAgICAg
ICAgICAgICAgICAgICAgKFBDRVApIEV4dGVuc2lvbnMgZm9ywqB0aGXCoEhpZXJhcmNoaWNhbCBQ
YXRoIAogICAgICAgICAgICAgICAgICAgIENvbXB1dGF0aW9uIEVsZW1lbnQgKEgtUENFKSBBcmNo
aXRlY3R1cmUgCiAgICAgICAgQXV0aG9yOiAgICAgRi4gWmhhbmcsIAogICAgICAgICAgICAgICAg
ICAgIFEuIFpoYW8sCiAgICAgICAgICAgICAgICAgICAgTy4gR29uemFsZXogZGUgRGlvcywgCiAg
ICAgICAgICAgICAgICAgICAgUi4gQ2FzZWxsYXMsCiAgICAgICAgICAgICAgICAgICAgRC4gS2lu
ZwogICAgICAgIFN0YXR1czogICAgIFN0YW5kYXJkcyBUcmFjawogICAgICAgIFN0cmVhbTogICAg
IElFVEYKICAgICAgICBEYXRlOiAgICAgICBEZWNlbWJlciAyMDE5CiAgICAgICAgTWFpbGJveDog
ICAgemhhbmdmYXRhaUBodWF3ZWkuY29tLCAKICAgICAgICAgICAgICAgICAgICBxdWludGluemhh
b0BnbWFpbC5jb20sIAogICAgICAgICAgICAgICAgICAgIG9zY2FyLmdvbnphbGV6ZGVkaW9zQHRl
bGVmb25pY2EuY29tLCAgCiAgICAgICAgICAgICAgICAgICAgcmFtb24uY2FzZWxsYXNAY3R0Yy5l
cywgCiAgICAgICAgICAgICAgICAgICAgZGFuaWVsQG9sZGRvZy5jby51awogICAgICAgIFBhZ2Vz
OiAgICAgIDI3CiAgICAgICAgVXBkYXRlcy9PYnNvbGV0ZXMvU2VlQWxzbzogICBOb25lCgogICAg
ICAgIEktRCBUYWc6ICAgIGRyYWZ0LWlldGYtcGNlLWhpZXJhcmNoeS1leHRlbnNpb25zLTExLnR4
dAoKICAgICAgICBVUkw6ICAgICAgICBodHRwczovL3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZvL3Jm
Yzg2ODUKCiAgICAgICAgRE9JOiAgICAgICAgMTAuMTc0ODcvUkZDODY4NQoKVGhlIEhpZXJhcmNo
aWNhbCBQYXRoIENvbXB1dGF0aW9uIEVsZW1lbnQgKEgtUENFKSBhcmNoaXRlY3R1cmUgaXMKZGVm
aW5lZCBpbiBSRkMgNjgwNS4gIEl0IHByb3ZpZGVzIGEgbWVjaGFuaXNtIHRvIGRlcml2ZSBhbiBv
cHRpbXVtCmVuZC10by1lbmQgcGF0aCBpbiBhIG11bHRpLWRvbWFpbiBlbnZpcm9ubWVudCBieSB1
c2luZyBhIGhpZXJhcmNoaWNhbApyZWxhdGlvbnNoaXAgYmV0d2VlbiBkb21haW5zIHRvIHNlbGVj
dCB0aGUgb3B0aW11bSBzZXF1ZW5jZSBvZgpkb21haW5zIGFuZCBvcHRpbXVtIHBhdGhzIGFjcm9z
cyB0aG9zZSBkb21haW5zLgoKVGhpcyBkb2N1bWVudCBkZWZpbmVzIGV4dGVuc2lvbnMgdG8gdGhl
IFBhdGggQ29tcHV0YXRpb24gRWxlbWVudApDb21tdW5pY2F0aW9uIFByb3RvY29sIChQQ0VQKSB0
byBzdXBwb3J0IEgtUENFIHByb2NlZHVyZXMuCgpUaGlzIGRvY3VtZW50IGlzIGEgcHJvZHVjdCBv
ZiB0aGUgUGF0aCBDb21wdXRhdGlvbiBFbGVtZW50IFdvcmtpbmcgR3JvdXAgb2YgdGhlIElFVEYu
CgpUaGlzIGlzIG5vdyBhIFByb3Bvc2VkIFN0YW5kYXJkLgoKU1RBTkRBUkRTIFRSQUNLOiBUaGlz
IGRvY3VtZW50IHNwZWNpZmllcyBhbiBJbnRlcm5ldCBTdGFuZGFyZHMgVHJhY2sKcHJvdG9jb2wg
Zm9yIHRoZSBJbnRlcm5ldCBjb21tdW5pdHksIGFuZCByZXF1ZXN0cyBkaXNjdXNzaW9uIGFuZCBz
dWdnZXN0aW9ucwpmb3IgaW1wcm92ZW1lbnRzLiAgUGxlYXNlIHJlZmVyIHRvIHRoZSBjdXJyZW50
IGVkaXRpb24gb2YgdGhlIE9mZmljaWFsCkludGVybmV0IFByb3RvY29sIFN0YW5kYXJkcyAoaHR0
cHM6Ly93d3cucmZjLWVkaXRvci5vcmcvc3RhbmRhcmRzKSBmb3IgdGhlIApzdGFuZGFyZGl6YXRp
b24gc3RhdGUgYW5kIHN0YXR1cyBvZiB0aGlzIHByb3RvY29sLiAgRGlzdHJpYnV0aW9uIG9mIHRo
aXMgCm1lbW8gaXMgdW5saW1pdGVkLgoKVGhpcyBhbm5vdW5jZW1lbnQgaXMgc2VudCB0byB0aGUg
SUVURi1Bbm5vdW5jZSBhbmQgcmZjLWRpc3QgbGlzdHMuClRvIHN1YnNjcmliZSBvciB1bnN1YnNj
cmliZSwgc2VlCiAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZXRmLWFu
bm91bmNlCiAgaHR0cHM6Ly9tYWlsbWFuLnJmYy1lZGl0b3Iub3JnL21haWxtYW4vbGlzdGluZm8v
cmZjLWRpc3QKCkZvciBzZWFyY2hpbmcgdGhlIFJGQyBzZXJpZXMsIHNlZSBodHRwczovL3d3dy5y
ZmMtZWRpdG9yLm9yZy9zZWFyY2gKRm9yIGRvd25sb2FkaW5nIFJGQ3MsIHNlZSBodHRwczovL3d3
dy5yZmMtZWRpdG9yLm9yZy9yZXRyaWV2ZS9idWxrCgpSZXF1ZXN0cyBmb3Igc3BlY2lhbCBkaXN0
cmlidXRpb24gc2hvdWxkIGJlIGFkZHJlc3NlZCB0byBlaXRoZXIgdGhlCmF1dGhvciBvZiB0aGUg
UkZDIGluIHF1ZXN0aW9uLCBvciB0byByZmMtZWRpdG9yQHJmYy1lZGl0b3Iub3JnLiAgVW5sZXNz
CnNwZWNpZmljYWxseSBub3RlZCBvdGhlcndpc2Ugb24gdGhlIFJGQyBpdHNlbGYsIGFsbCBSRkNz
IGFyZSBmb3IKdW5saW1pdGVkIGRpc3RyaWJ1dGlvbi4KCgpUaGUgUkZDIEVkaXRvciBUZWFtCkFz
c29jaWF0aW9uIE1hbmFnZW1lbnQgU29sdXRpb25zLCBMTEMKCgpfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXwpyZmMtZGlzdCBtYWlsaW5nIGxpc3QKcmZjLWRp
c3RAcmZjLWVkaXRvci5vcmcKaHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcvbWFpbG1hbi9saXN0
aW5mby9yZmMtZGlzdApodHRwOi8vd3d3LnJmYy1lZGl0b3Iub3JnCg==

From rfc-dist-bounces@rfc-editor.org  Wed Dec 18 20:38:49 2019
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 942F4120018 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 18 Dec 2019 20:38:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SGleTp2mwmgm for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 18 Dec 2019 20:38:48 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 893F812004F for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 18 Dec 2019 20:38:48 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D2585F40722; Wed, 18 Dec 2019 20:38:28 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id EB9C9F40721; Wed, 18 Dec 2019 20:38:27 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191219043827.EB9C9F40721@rfc-editor.org>
Date: Wed, 18 Dec 2019 20:38:27 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8694_on_Applicability_of_the_Path_Compu?= =?utf-8?q?tation_Element_to_Inter-area_and_Inter-AS_MPLS_and_GMPLS_Traffi?= =?utf-8?q?c_Engineering?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, 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 8694

        Title:      Applicability of the Path Computation 
                    Element to Inter-area and Inter-AS MPLS 
                    and GMPLS Traffic Engineering 
        Author:     D. King,
                    H. Zheng
        Status:     Informational
        Stream:     IETF
        Date:       December 2019
        Mailbox:    daniel@olddog.co.uk, 
                    zhenghaomian@huawei.com
        Pages:      24
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-inter-area-as-applicability-08.txt

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

        DOI:        10.17487/RFC8694

The Path Computation Element (PCE) may be used for computing services
that traverse multi-area and  multi-Autonomous System (multi-AS)
Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS)
Traffic-Engineered (TE) networks.

This document examines the applicability of the PCE architecture,
protocols, and protocol extensions for computing multi-area and
multi-AS paths in MPLS and GMPLS networks.

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  Wed Dec 18 21:32:51 2019
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 86A31120018 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 18 Dec 2019 21:32:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oXWkHNnKnoBP for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 18 Dec 2019 21:32:50 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A29D12004F for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 18 Dec 2019 21:32:50 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id C00FDF40722; Wed, 18 Dec 2019 21:32:30 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 4A057F40721; Wed, 18 Dec 2019 21:32:30 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191219053230.4A057F40721@rfc-editor.org>
Date: Wed, 18 Dec 2019 21:32:30 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8696_on_Using_Pre-Shared_Key_=28PSK=29_?= =?utf-8?q?in_the_Cryptographic_Message_Syntax_=28CMS=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: spasm@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8696

        Title:      Using Pre-Shared Key (PSK) in 
                    the Cryptographic Message Syntax (CMS) 
        Author:     R. Housley
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2019
        Mailbox:    housley@vigilsec.com
        Pages:      31
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-lamps-cms-mix-with-psk-07.txt

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

        DOI:        10.17487/RFC8696

The invention of a large-scale quantum computer would pose a serious
challenge for the cryptographic algorithms that are widely deployed
today.  The Cryptographic Message Syntax (CMS) supports key transport
and key agreement algorithms that could be broken by the invention of
such a quantum computer.  By storing communications that are
protected with the CMS today, someone could decrypt them in the
future when a large-scale quantum computer becomes available.  Once
quantum-secure key management algorithms are available, the CMS will
be extended to support the new algorithms if the existing syntax does
not accommodate them.  This document describes a mechanism to protect
today's communication from the future invention of a large-scale
quantum computer by mixing the output of key transport and key
agreement algorithms with a pre-shared key.

This document is a product of the Limited Additional Mechanisms for PKIX and SMIME Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Wed Dec 18 22:07:16 2019
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 1C3DC120018 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 18 Dec 2019 22:07:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id afSweL4ALgLG for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 18 Dec 2019 22:07:15 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 298CD12008B for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 18 Dec 2019 22:07:15 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 658F9F40724; Wed, 18 Dec 2019 22:06:55 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id B2C0AF40723; Wed, 18 Dec 2019 22:06:54 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191219060654.B2C0AF40723@rfc-editor.org>
Date: Wed, 18 Dec 2019 22:06:54 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8678_on_Enterprise_Multihoming_using_Pr?= =?utf-8?q?ovider-Assigned_IPv6_Addresses_without_Network_Prefix_Translati?= =?utf-8?q?on=3A_Requirements_and_Solutions?=
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, 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 8678

        Title:      Enterprise Multihoming using Provider-Assigned  
                    IPv6 Addresses without Network Prefix Translation: 
                    Requirements and Solutions 
        Author:     F. Baker,
                    C. Bowers,
                    J. Linkova
        Status:     Informational
        Stream:     IETF
        Date:       December 2019
        Mailbox:    FredBaker.IETF@gmail.com, 
                    cbowers@juniper.net, 
                    furry@google.com
        Pages:      43
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtgwg-enterprise-pa-multihoming-12.txt

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

        DOI:        10.17487/RFC8678

Connecting an enterprise site to multiple ISPs over IPv6 using
provider-assigned addresses is difficult without the use of some form
of Network Address Translation (NAT). Much has been written on this
topic over the last 10 to 15 years, but it still remains a problem
without a clearly defined or widely implemented solution. Any
multihoming solution without NAT requires hosts at the site to have
addresses from each ISP and to select the egress ISP by selecting a
source address for outgoing packets. It also requires routers at the
site to take into account those source addresses when forwarding
packets out towards the ISPs.

This document examines currently available mechanisms for providing a
solution to this problem for a broad range of enterprise topologies.
It covers the behavior of routers to forward traffic by taking into
account source address, and it covers the behavior of hosts to select
appropriate default source addresses. It also covers any possible
role that routers might play in providing information to hosts to
help them select appropriate source addresses. In the process of
exploring potential solutions, this document also makes explicit
requirements for how the solution would be expected to behave from
the perspective of an enterprise site network administrator.

This document is a product of the Routing Area Working Group 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 Dec 23 12:54:29 2019
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 7CD7B120CE8 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 23 Dec 2019 12:54:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=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 YTg-Zcwq9Wum for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 23 Dec 2019 12:54:26 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84B9B1201DB for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 23 Dec 2019 12:54:26 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 44DD2F40752; Mon, 23 Dec 2019 12:54:23 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 434EFF40751; Mon, 23 Dec 2019 12:54:22 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191223205422.434EFF40751@rfc-editor.org>
Date: Mon, 23 Dec 2019 12:54:22 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8700_on_Fifty_Years_of_RFCs?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, 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 8700

        Title:      Fifty Years of RFCs 
        Author:     H. Flanagan, Ed.
        Status:     Informational
        Stream:     IAB
        Date:       December 2019
        Mailbox:    rse@rfc-editor.org
        Pages:      22
        Updates:    RFC 2555, RFC 5540

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

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

        DOI:        10.17487/RFC8700

This RFC marks the fiftieth anniversary for the RFC Series. It
includes both retrospective material from individuals involved at key
inflection points as well as a review of the current state of
affairs. It concludes with thoughts on possibilities for the next
fifty years for the Series. This document updates the perspectives
offered in RFCs 2555 and 5540.

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 Dec 27 10:23:56 2019
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 90420120018 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 27 Dec 2019 10:23:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=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 tFZpm-L6l3mR for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 27 Dec 2019 10:23:55 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4138712013B for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 27 Dec 2019 10:23:55 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 99AFDF40743; Fri, 27 Dec 2019 10:23:45 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 7B001F40742; Fri, 27 Dec 2019 10:23:44 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20191227182344.7B001F40742@rfc-editor.org>
Date: Fri, 27 Dec 2019 10:23:44 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8691_on_Basic_Support_for_IPv6_Networks?= =?utf-8?q?_Operating_Outside_the_Context_of_a_Basic_Service_Set_over_IEEE?= =?utf-8?q?_Std_802=2E11?=
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, its@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

QSBuZXcgUmVxdWVzdCBmb3IgQ29tbWVudHMgaXMgbm93IGF2YWlsYWJsZSBpbiBvbmxpbmUgUkZD
IGxpYnJhcmllcy4KCiAgICAgICAgCiAgICAgICAgUkZDIDg2OTEKCiAgICAgICAgVGl0bGU6ICAg
ICAgQmFzaWMgU3VwcG9ydCBmb3IgSVB2NiBOZXR3b3JrcyAKICAgICAgICAgICAgICAgICAgICBP
cGVyYXRpbmcgT3V0c2lkZSB0aGUgQ29udGV4dCBvZiBhIAogICAgICAgICAgICAgICAgICAgIEJh
c2ljIFNlcnZpY2UgU2V0IG92ZXIgSUVFRSBTdGQgODAyLjExCiAgICAgICAgQXV0aG9yOiAgICAg
Ti4gQmVuYW1hciwKICAgICAgICAgICAgICAgICAgICBKLiBIw6RycmksCiAgICAgICAgICAgICAg
ICAgICAgSi4gTGVlLAogICAgICAgICAgICAgICAgICAgIFQuIEVybnN0CiAgICAgICAgU3RhdHVz
OiAgICAgU3RhbmRhcmRzIFRyYWNrCiAgICAgICAgU3RyZWFtOiAgICAgSUVURgogICAgICAgIERh
dGU6ICAgICAgIERlY2VtYmVyIDIwMTkKICAgICAgICBNYWlsYm94OiAgICBuLmJlbmFtYXJAZXN0
LnVtaS5hYy5tYSwgCiAgICAgICAgICAgICAgICAgICAgamVyb21lLmhhZXJyaUBldXJlY29tLmZy
LCAKICAgICAgICAgICAgICAgICAgICBqb25naHlvdWtAc211LmFjLmtyLAogICAgICAgICAgICAg
ICAgICAgIHRoaWVycnkuZXJuc3RAeW9nb2tvLmZyCiAgICAgICAgUGFnZXM6ICAgICAgMjkKICAg
ICAgICBVcGRhdGVzL09ic29sZXRlcy9TZWVBbHNvOiAgIE5vbmUKCiAgICAgICAgSS1EIFRhZzog
ICAgZHJhZnQtaWV0Zi1pcHdhdmUtaXB2Ni1vdmVyLTgwMjExb2NiLTUyLnR4dAoKICAgICAgICBV
Ukw6ICAgICAgICBodHRwczovL3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZvL3JmYzg2OTEKCiAgICAg
ICAgRE9JOiAgICAgICAgMTAuMTc0ODcvUkZDODY5MQoKVGhpcyBkb2N1bWVudCBwcm92aWRlcyBt
ZXRob2RzIGFuZCBzZXR0aW5ncyBmb3IgdXNpbmcgSVB2NiB0bwpjb21tdW5pY2F0ZSBhbW9uZyBu
b2RlcyB3aXRoaW4gcmFuZ2Ugb2Ygb25lIGFub3RoZXIgb3ZlciBhIHNpbmdsZQpJRUVFIDgwMi4x
MS1PQ0IgbGluay4gU3VwcG9ydCBmb3IgdGhlc2UgbWV0aG9kcyBhbmQgc2V0dGluZ3MgcmVxdWly
ZQptaW5pbWFsIGNoYW5nZXMgdG8gZXhpc3Rpbmcgc3RhY2tzLiBUaGlzIGRvY3VtZW50IGFsc28g
ZGVzY3JpYmVzCmxpbWl0YXRpb25zIGFzc29jaWF0ZWQgd2l0aCB1c2luZyB0aGVzZSBtZXRob2Rz
LiBPcHRpbWl6YXRpb25zIGFuZAp1c2FnZSBvZiBJUHY2IG92ZXIgbW9yZSBjb21wbGV4IHNjZW5h
cmlvcyBhcmUgbm90IGNvdmVyZWQgaW4gdGhpcwpzcGVjaWZpY2F0aW9uIGFuZCBhcmUgYSBzdWJq
ZWN0IGZvciBmdXR1cmUgd29yay4KClRoaXMgZG9jdW1lbnQgaXMgYSBwcm9kdWN0IG9mIHRoZSBJ
UCBXaXJlbGVzcyBBY2Nlc3MgaW4gVmVoaWN1bGFyIEVudmlyb25tZW50cyBXb3JraW5nIEdyb3Vw
IG9mIHRoZSBJRVRGLgoKVGhpcyBpcyBub3cgYSBQcm9wb3NlZCBTdGFuZGFyZC4KClNUQU5EQVJE
UyBUUkFDSzogVGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgYW4gSW50ZXJuZXQgU3RhbmRhcmRzIFRy
YWNrCnByb3RvY29sIGZvciB0aGUgSW50ZXJuZXQgY29tbXVuaXR5LCBhbmQgcmVxdWVzdHMgZGlz
Y3Vzc2lvbiBhbmQgc3VnZ2VzdGlvbnMKZm9yIGltcHJvdmVtZW50cy4gIFBsZWFzZSByZWZlciB0
byB0aGUgY3VycmVudCBlZGl0aW9uIG9mIHRoZSBPZmZpY2lhbApJbnRlcm5ldCBQcm90b2NvbCBT
dGFuZGFyZHMgKGh0dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL3N0YW5kYXJkcykgZm9yIHRoZSAK
c3RhbmRhcmRpemF0aW9uIHN0YXRlIGFuZCBzdGF0dXMgb2YgdGhpcyBwcm90b2NvbC4gIERpc3Ry
aWJ1dGlvbiBvZiB0aGlzIAptZW1vIGlzIHVubGltaXRlZC4KClRoaXMgYW5ub3VuY2VtZW50IGlz
IHNlbnQgdG8gdGhlIElFVEYtQW5ub3VuY2UgYW5kIHJmYy1kaXN0IGxpc3RzLgpUbyBzdWJzY3Jp
YmUgb3IgdW5zdWJzY3JpYmUsIHNlZQogIGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vaWV0Zi1hbm5vdW5jZQogIGh0dHBzOi8vbWFpbG1hbi5yZmMtZWRpdG9yLm9yZy9tYWls
bWFuL2xpc3RpbmZvL3JmYy1kaXN0CgpGb3Igc2VhcmNoaW5nIHRoZSBSRkMgc2VyaWVzLCBzZWUg
aHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcvc2VhcmNoCkZvciBkb3dubG9hZGluZyBSRkNzLCBz
ZWUgaHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcvcmV0cmlldmUvYnVsawoKUmVxdWVzdHMgZm9y
IHNwZWNpYWwgZGlzdHJpYnV0aW9uIHNob3VsZCBiZSBhZGRyZXNzZWQgdG8gZWl0aGVyIHRoZQph
dXRob3Igb2YgdGhlIFJGQyBpbiBxdWVzdGlvbiwgb3IgdG8gcmZjLWVkaXRvckByZmMtZWRpdG9y
Lm9yZy4gIFVubGVzcwpzcGVjaWZpY2FsbHkgbm90ZWQgb3RoZXJ3aXNlIG9uIHRoZSBSRkMgaXRz
ZWxmLCBhbGwgUkZDcyBhcmUgZm9yCnVubGltaXRlZCBkaXN0cmlidXRpb24uCgoKVGhlIFJGQyBF
ZGl0b3IgVGVhbQpBc3NvY2lhdGlvbiBNYW5hZ2VtZW50IFNvbHV0aW9ucywgTExDCgoKX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcmZjLWRpc3QgbWFpbGlu
ZyBsaXN0CnJmYy1kaXN0QHJmYy1lZGl0b3Iub3JnCmh0dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3Jn
L21haWxtYW4vbGlzdGluZm8vcmZjLWRpc3QKaHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZwo=
