
From rfc-dist-bounces@rfc-editor.org  Mon Mar  5 11:28:47 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD93412E8B0 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon,  5 Mar 2018 11:28:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 epYH9MyeTZWC for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon,  5 Mar 2018 11:28:46 -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 393F412D7F9 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon,  5 Mar 2018 11:28:43 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id E47BBB80DAC; Mon,  5 Mar 2018 11:28:26 -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 3B61BB80DAD; Mon,  5 Mar 2018 11:28:26 -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: <20180305192826.3B61BB80DAD@rfc-editor.org>
Date: Mon,  5 Mar 2018 11:28:26 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8334_on_Launch_Phase_Mapping_for_the_Ext?= =?utf-8?q?ensible_Provisioning_Protocol_=28EPP=29?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, regext@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8334

        Title:      Launch Phase Mapping for the 
                    Extensible Provisioning Protocol (EPP) 
        Author:     J. Gould,
                    W. Tan,
                    G. Brown
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    jgould@verisign.com, 
                    wil@cloudregistry.net, 
                    gavin.brown@centralnic.com
        Pages:      58
        Characters: 106211
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-regext-launchphase-07.txt

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

        DOI:        10.17487/RFC8334

This document describes an Extensible Provisioning Protocol (EPP)
extension mapping for the provisioning and management of domain name
registrations and applications during the launch of a domain name
registry.

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

This is now a Proposed Standard.

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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Tue Mar  6 14:49:29 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9B8B124B18 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  6 Mar 2018 14:49:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 OvhnMfLz1Bxx for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  6 Mar 2018 14:49:28 -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 0AD40124319 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue,  6 Mar 2018 14:49:28 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id AE174B80E3A; Tue,  6 Mar 2018 14:49:10 -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 EE0A0B80E38; Tue,  6 Mar 2018 14:49:09 -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: <20180306224909.EE0A0B80E38@rfc-editor.org>
Date: Tue,  6 Mar 2018 14:49:09 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8326_on_Graceful_BGP_Session_Shutdown?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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, grow@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 8326

        Title:      Graceful BGP Session Shutdown 
        Author:     P. Francois, Ed.,
                    B. Decraene, Ed.,
                    C. Pelsser,
                    K. Patel,
                    C. Filsfils
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    pfrpfr@gmail.com, 
                    bruno.decraene@orange.com, 
                    pelsser@unistra.fr,
                    keyur@arrcus.com, 
                    cfilsfil@cisco.com
        Pages:      12
        Characters: 21701
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-grow-bgp-gshut-13.txt

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

        DOI:        10.17487/RFC8326

This document standardizes a new well-known BGP community,
GRACEFUL_SHUTDOWN, to signal the graceful shutdown of paths.  This
document also describes operational procedures that use this
well-known community to reduce the amount of traffic lost when BGP peering
sessions are about to be shut down deliberately, e.g., for planned
maintenance.

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

This is now a Proposed Standard.

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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Tue Mar  6 14:50:20 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77C5F12DA2B for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  6 Mar 2018 14:50:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 xxEuycsl6pNu for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  6 Mar 2018 14:50:02 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9235A12D877 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue,  6 Mar 2018 14:49:47 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 24932B80E54; Tue,  6 Mar 2018 14:49:21 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 02AFBB80E53; Tue,  6 Mar 2018 14:49:20 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180306224920.02AFBB80E53@rfc-editor.org>
Date: Tue,  6 Mar 2018 14:49:20 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?BCP_214=2C_RFC_8327_on_Mitigating_the_Negati?= =?utf-8?q?ve_Impact_of_Maintenance_through_BGP_Session_Culling?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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, grow@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        BCP 214        
        RFC 8327

        Title:      Mitigating the Negative Impact of 
                    Maintenance through BGP Session Culling 
        Author:     W. Hargrave,
                    M. Griswold,
                    J. Snijders,
                    N. Hilliard
        Status:     Best Current Practice
        Stream:     IETF
        Date:       March 2018
        Mailbox:    will@lonap.net, 
                    grizz@20c.com, 
                    job@ntt.net,
                    nick@inex.ie
        Pages:      10
        Characters: 18087
        See Also:   BCP 214

        I-D Tag:    draft-ietf-grow-bgp-session-culling-05.txt

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

        DOI:        10.17487/RFC8327

This document outlines an approach to mitigate the negative impact on
networks resulting from maintenance activities.  It includes guidance
for both IP networks and Internet Exchange Points (IXPs).  The
approach is to ensure BGP-4 sessions that will be affected by
maintenance are forcefully torn down before the actual maintenance
activities commence.

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


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Tue Mar  6 15:33:10 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0BDC1200FC for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  6 Mar 2018 15:33:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 iMDwf05PT3Q7 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  6 Mar 2018 15:33:09 -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 49C19126CB6 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue,  6 Mar 2018 15:33:09 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id E58C7B80FFA; Tue,  6 Mar 2018 15:32: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 050ECB80FF8; Tue,  6 Mar 2018 15:32:51 -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: <20180306233251.050ECB80FF8@rfc-editor.org>
Date: Tue,  6 Mar 2018 15:32:51 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8338_on_Signaling_Root-Initiated_Point-t?= =?utf-8?q?o-Multipoint_Pseudowire_Using_LDP?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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, pals@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 8338

        Title:      Signaling Root-Initiated Point-to-Multipoint 
                    Pseudowire Using LDP 
        Author:     S. Boutros, Ed.,
                    S. Sivabalan, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    sboutros@vmware.com, 
                    msiva@cisco.com
        Pages:      20
        Characters: 40885
        Updates:    RFC 7385

        I-D Tag:    draft-ietf-pals-p2mp-pw-04.txt

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

        DOI:        10.17487/RFC8338

This document specifies a mechanism to signal Point-to-Multipoint
(P2MP) Pseudowire (PW) trees using LDP.  Such a mechanism is suitable
for any Layer 2 VPN service requiring P2MP connectivity over an IP or
MPLS-enabled PSN.  A P2MP PW established via the proposed mechanism
is root initiated.  This document updates RFC 7385 by reassigning the
reserved value 0xFF to be the wildcard transport tunnel type.

This document is a product of the Pseudowire And LDP-enabled Services Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


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

From rfc-dist-bounces@rfc-editor.org  Tue Mar  6 22:04:07 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5621A127058 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  6 Mar 2018 22:04:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 gwjSA-3AVM24 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  6 Mar 2018 22:04:06 -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 72B67124BE8 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue,  6 Mar 2018 22:04:06 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id CD813B80C8E; Tue,  6 Mar 2018 22:03: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 4BDE2B80C8E; Tue,  6 Mar 2018 22:03: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: <20180307060347.4BDE2B80C8E@rfc-editor.org>
Date: Tue,  6 Mar 2018 22:03:47 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8356_on_Experimental_Codepoint_Allocatio?= =?utf-8?q?n_for_the_Path_Computation_Element_Communication_Protocol_=28PC?= =?utf-8?b?RVAp?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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 8356

        Title:      Experimental Codepoint Allocation for the 
                    Path Computation Element Communication Protocol (PCEP) 
        Author:     D. Dhody, 
                    D. King,
                    A. Farrel
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    dhruv.ietf@gmail.com, 
                    d.king@lancaster.ac.uk, 
                    afarrel@juniper.net
        Pages:      7
        Characters: 14283
        Updates:    RFC 5440

        I-D Tag:    draft-ietf-pce-pcep-exp-codepoints-05.txt

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

        DOI:        10.17487/RFC8356

IANA assigns values to the Path Computation Element Communication
Protocol (PCEP) parameters (messages, objects, TLVs).  IANA
established a top-level registry to contain all PCEP codepoints and
sub-registries.  This top-level registry contains sub-registries for
PCEP message, object, and TLV types.  The allocation policy for each
of these sub-registries is IETF Review.

This document updates RFC 5440 by changing the allocation policies
for these three registries to mark some of the codepoints as assigned
for Experimental Use.


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  Tue Mar  6 22:46:47 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34FA6124BE8 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  6 Mar 2018 22:46:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 Zdh-f_t0CvgT for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  6 Mar 2018 22:46:46 -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 17D6C127444 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue,  6 Mar 2018 22:46:46 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 6AB3BB80F16; Tue,  6 Mar 2018 22:46: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 066BDB80F09; Tue,  6 Mar 2018 22:46: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: <20180307064628.066BDB80F09@rfc-editor.org>
Date: Tue,  6 Mar 2018 22:46:28 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8357_on_Generalized_UDP_Source_Port_for_?= =?utf-8?q?DHCP_Relay?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, dhcwg@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8357

        Title:      Generalized UDP Source Port 
                    for DHCP Relay 
        Author:     N. Shen, 
                    E. Chen
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    naiming@cisco.com, 
                    enkechen@cisco.com
        Pages:      10
        Characters: 21266
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dhc-relay-port-10.txt

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

        DOI:        10.17487/RFC8357

This document defines an extension to the DHCP protocols that allows
a relay agent to use any available source port for upstream
communications.  The extension also allows inclusion of a DHCP option
that can be used to statelessly route responses back to the
appropriate source port on downstream communications.


This document is a product of the Dynamic Host Configuration Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Mon Mar 12 17:08:22 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D703126D45 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 12 Mar 2018 17:08:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 uc9XXYttUTHb for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 12 Mar 2018 17:08:20 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9888124F57 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 12 Mar 2018 17:08:20 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id CAF72B81C6A; Mon, 12 Mar 2018 17:07:57 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 04ECAB81C69; Mon, 12 Mar 2018 17:07:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180313000757.04ECAB81C69@rfc-editor.org>
Date: Mon, 12 Mar 2018 17:07:57 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8358_on_Update_to_Digital_Signatures_on_?= =?utf-8?q?Internet-Draft_Documents?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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 8358

        Title:      Update to Digital Signatures on 
                    Internet-Draft Documents 
        Author:     R. Housley
        Status:     Informational
        Stream:     IETF
        Date:       March 2018
        Mailbox:    housley@vigilsec.com
        Pages:      9
        Characters: 19954
        Updates:    RFC 5485

        I-D Tag:    draft-housley-id-sig-update-03.txt

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

        DOI:        10.17487/RFC8358

RFC 5485 specifies the conventions for digital signatures on
Internet-Drafts.  The Cryptographic Message Syntax (CMS) is used to
create a detached signature, which is stored in a separate companion
file so that no existing utilities are impacted by the addition of
the digital signature.

The RFC Editor recently published the first RFC that includes non-
ASCII characters in a text file.  The conventions specified in RFC
7997 were followed.  We assume that non-ASCII characters will soon
start appearing in Internet-Drafts as well.  This document updates
the handling of digital signatures on Internet-Drafts that contain
non-ASCII characters in a text file.

This document updates RFC 5485.


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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Tue Mar 13 15:40:59 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D45C12E049 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 13 Mar 2018 15:40:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 1tKmdrTeNVJ9 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 13 Mar 2018 15:40:58 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCC9F12E852 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 13 Mar 2018 15:40:57 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D8603B81F37; Tue, 13 Mar 2018 15:40:33 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 0FDFBB81F36; Tue, 13 Mar 2018 15:40:33 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180313224033.0FDFBB81F36@rfc-editor.org>
Date: Tue, 13 Mar 2018 15:40:33 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8339_on_Definition_of_P2MP_PW_TLV_for_La?= =?utf-8?q?bel_Switched_Path_=28LSP=29_Ping_Mechanisms?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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, pals@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 8339

        Title:      Definition of P2MP PW TLV 
                    for Label Switched Path (LSP) Ping 
                    Mechanisms 
        Author:     P. Jain, Ed.,
                    S. Boutros, 
                    S. Aldrin
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    paragj@cisco.com, 
                    sboutros@vmware.com, 
                    aldrin.ietf@gmail.com
        Pages:      10
        Characters: 18964
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pals-p2mp-pw-lsp-ping-05.txt

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

        DOI:        10.17487/RFC8339

Label Switched Path (LSP) Ping is a widely deployed Operation,
Administration, and Maintenance (OAM) mechanism in MPLS networks.
This document describes a mechanism to verify connectivity of
Point-to-Multipoint (P2MP) Pseudowires (PWs) using LSP Ping.

This document is a product of the Pseudowire And LDP-enabled Services Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Tue Mar 13 15:41:53 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C17A12EB72 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 13 Mar 2018 15:41:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 uwnI7E649JxV for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 13 Mar 2018 15:41:51 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AB8D12EB17 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 13 Mar 2018 15:41:18 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5611BB81F40; Tue, 13 Mar 2018 15:40:55 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 63885B81F3F; Tue, 13 Mar 2018 15:40:54 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180313224054.63885B81F3F@rfc-editor.org>
Date: Tue, 13 Mar 2018 15:40:54 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8359_on_Network-Assigned_Upstream_Label?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, teas@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8359

        Title:      Network-Assigned Upstream Label 
        Author:     X. Zhang, Ed.,
                    V. Beeram, Ed.,
                    I. Bryskin,
                    D. Ceccarelli,
                    O. Gonzalez de Dios
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    zhang.xian@huawei.com, 
                    vbeeram@juniper.net, 
                    igor.bryskin@huawei.com,  
                    daniele.ceccarelli@ericsson.com, 
                    ogondio@tid.es
        Pages:      10
        Characters: 20447
        Updates:    RFC 3471, RFC 3473, RFC 6205

        I-D Tag:    draft-ietf-teas-network-assigned-upstream-label-12.txt

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

        DOI:        10.17487/RFC8359

This document discusses a Generalized Multi-Protocol Label Switching
(GMPLS) Resource reSerVation Protocol with Traffic Engineering
(RSVP-TE) mechanism that enables the network to assign an upstream label
for a bidirectional Label Switched Path (LSP).  This is useful in
scenarios where a given node does not have sufficient information to
assign the correct upstream label on its own and needs to rely on the
downstream node to pick an appropriate label.  This document updates
RFCs 3471, 3473, and 6205 as it defines processing for a special
label value in the UPSTREAM_LABEL object.

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

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Thu Mar 15 17:09:58 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDE4B12778D for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 15 Mar 2018 17:09:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 ia0JjNW27TZP for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 15 Mar 2018 17:09:57 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88EF1126DD9 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 15 Mar 2018 17:09:57 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 83531B80DF4; Thu, 15 Mar 2018 17:09:54 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 74981B80DF2; Thu, 15 Mar 2018 17:09:53 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180316000953.74981B80DF2@rfc-editor.org>
Date: Thu, 15 Mar 2018 17:09:53 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8337_on_Model-Based_Metrics_for_Bulk_Tra?= =?utf-8?q?nsport_Capacity?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, ippm@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8337

        Title:      Model-Based Metrics for Bulk Transport 
                    Capacity 
        Author:     M. Mathis, 
                    A. Morton
        Status:     Experimental
        Stream:     IETF
        Date:       March 2018
        Mailbox:    mattmathis@google.com, 
                    acmorton@att.com
        Pages:      55
        Characters: 138647
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ippm-model-based-metrics-13.txt

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

        DOI:        10.17487/RFC8337

This document introduces a new class of Model-Based Metrics designed
to assess if a complete Internet path can be expected to meet a
predefined Target Transport Performance by applying a suite of IP
diagnostic tests to successive subpaths.  The subpath-at-a-time tests
can be robustly applied to critical infrastructure, such as network
interconnections or even individual devices, to accurately detect if
any part of the infrastructure will prevent paths traversing it from
meeting the Target Transport Performance.

Model-Based Metrics rely on mathematical models to specify a Targeted
IP Diagnostic Suite, a set of IP diagnostic tests designed to assess
whether common transport protocols can be expected to meet a
predetermined Target Transport Performance over an Internet path.

For Bulk Transport Capacity, the IP diagnostics are built using test
streams and statistical criteria for evaluating the packet transfer
that mimic TCP over the complete path.  The temporal structure of the
test stream (e.g., bursts) mimics TCP or other transport protocols
carrying bulk data over a long path.  However, they are constructed
to be independent of the details of the subpath under test, end
systems, or applications.  Likewise, the success criteria evaluates
the packet transfer statistics of the subpath against criteria
determined by protocol performance models applied to the Target
Transport Performance of the complete path.  The success criteria
also does not depend on the details of the subpath, end systems, or
applications.

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


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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Fri Mar 16 14:28:55 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED92D12D869 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 16 Mar 2018 14:28:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 TQB_gGGTcycb for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 16 Mar 2018 14:28:53 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5112F1267BB for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 16 Mar 2018 14:28:53 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 296B6B80C80; Fri, 16 Mar 2018 14:28:49 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 77E66B80C7D; Fri, 16 Mar 2018 14:28:47 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180316212847.77E66B80C7D@rfc-editor.org>
Date: Fri, 16 Mar 2018 14:28:47 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?BCP_215=2C_RFC_8340_on_YANG_Tree_Diagrams?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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, netmod@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        BCP 215        
        RFC 8340

        Title:      YANG Tree Diagrams 
        Author:     M. Bjorklund,        
                    L. Berger, Ed.
        Status:     Best Current Practice
        Stream:     IETF
        Date:       March 2018
        Mailbox:    mbj@tail-f.com, 
                    lberger@labn.net
        Pages:      13
        Characters: 23841
        See Also:   BCP 215

        I-D Tag:    draft-ietf-netmod-yang-tree-diagrams-06.txt

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

        DOI:        10.17487/RFC8340

This document captures the current syntax used in YANG module tree
diagrams.  The purpose of this document is to provide a single
location for this definition.  This syntax may be updated from time
to time based on the evolution of the YANG language.

This document is a product of the Network Modeling Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Fri Mar 16 14:29:25 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDE56126DEE for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 16 Mar 2018 14:29:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 E0J8gIuH4gSC for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 16 Mar 2018 14:29:24 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00FBB12D954 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 16 Mar 2018 14:29:17 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 9221FB80C97; Fri, 16 Mar 2018 14:29:13 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 1A2E2B80C97; Fri, 16 Mar 2018 14:29:12 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180316212912.1A2E2B80C97@rfc-editor.org>
Date: Fri, 16 Mar 2018 14:29:12 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?STD_91=2C_RFC_8341_on_Network_Configuration_?= =?utf-8?q?Access_Control_Model?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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, netconf@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.

        STD 91        
        RFC 8341

        Title:      Network Configuration Access Control Model 
        Author:     A. Bierman,
                    M. Bjorklund
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    andy@yumaworks.com, 
                    mbj@tail-f.com
        Pages:      58
        Characters: 109849
        Obsoletes:  RFC 6536
        See Also:   STD 91

        I-D Tag:    draft-ietf-netconf-rfc6536bis-09.txt

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

        DOI:        10.17487/RFC8341

The standardization of network configuration interfaces for use with
the Network Configuration Protocol (NETCONF) or the RESTCONF protocol
requires a structured and secure operating environment that promotes
human usability and multi-vendor interoperability.  There is a need
for standard mechanisms to restrict NETCONF or RESTCONF protocol
access for particular users to a preconfigured subset of all
available NETCONF or RESTCONF protocol operations and content.  This
document defines such an access control model.

This document obsoletes RFC 6536.

This document is a product of the Network Configuration Working Group of the IETF.

This is now an Internet Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Fri Mar 16 14:29:41 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9175412D961 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 16 Mar 2018 14:29:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 ipI4H5XFW1qh for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 16 Mar 2018 14:29:40 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85E9712D94A for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 16 Mar 2018 14:29:34 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id F1A9DB80CA8; Fri, 16 Mar 2018 14:29:30 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 9B6C8B80CA7; Fri, 16 Mar 2018 14:29:29 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180316212929.9B6C8B80CA7@rfc-editor.org>
Date: Fri, 16 Mar 2018 14:29:29 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8342_on_Network_Management_Datastore_Arc?= =?utf-8?q?hitecture_=28NMDA=29?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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, netmod@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 8342

        Title:      Network Management Datastore Architecture (NMDA) 
        Author:     M. Bjorklund,
                    J. Schoenwaelder,
                    P. Shafer,
                    K. Watsen,
                    R. Wilton
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    mbj@tail-f.com, 
                    j.schoenwaelder@jacobs-university.de, 
                    phil@juniper.net, 
                    kwatsen@juniper.net, 
                    rwilton@cisco.com
        Pages:      44
        Characters: 79301
        Updates:    RFC 7950

        I-D Tag:    draft-ietf-netmod-revised-datastores-10.txt

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

        DOI:        10.17487/RFC8342

Datastores are a fundamental concept binding the data models written
in the YANG data modeling language to network management protocols
such as the Network Configuration Protocol (NETCONF) and RESTCONF.
This document defines an architectural framework for datastores based
on the experience gained with the initial simpler model, addressing
requirements that were not well supported in the initial model.  This
document updates RFC 7950.

This document is a product of the Network Modeling Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Fri Mar 16 14:30:27 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBFA612D88D for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 16 Mar 2018 14:30:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 CkZ4cCVe34oY for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 16 Mar 2018 14:30:18 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8FF712D951 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 16 Mar 2018 14:30:01 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 61712B80CDA; Fri, 16 Mar 2018 14:29:58 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id CFF94B80CD5; Fri, 16 Mar 2018 14:29:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180316212956.CFF94B80CD5@rfc-editor.org>
Date: Fri, 16 Mar 2018 14:29:56 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8343_on_A_YANG_Data_Model_for_Interface_?= =?utf-8?q?Management?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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, netmod@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 8343

        Title:      A YANG Data Model for Interface Management 
        Author:     M. Bjorklund
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    mbj@tail-f.com
        Pages:      49
        Characters: 91573
        Obsoletes:  RFC 7223

        I-D Tag:    draft-ietf-netmod-rfc7223bis-03.txt

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

        DOI:        10.17487/RFC8343

This document defines a YANG data model for the management of network
interfaces.  It is expected that interface-type-specific data models
augment the generic interfaces data model defined in this document.
The data model includes definitions for configuration and system
state (status information and counters for the collection of
statistics).

The YANG data model in this document conforms to the Network
Management Datastore Architecture (NMDA) defined in RFC 8342.

This document obsoletes RFC 7223.

This document is a product of the Network Modeling Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Fri Mar 16 14:30:55 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E10F512D953 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 16 Mar 2018 14:30:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 bw2k8LWdp31l for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 16 Mar 2018 14:30:47 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46156126DC2 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 16 Mar 2018 14:30:23 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id CFFD5B80CE5; Fri, 16 Mar 2018 14:30:19 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id B4F89B80CE7; Fri, 16 Mar 2018 14:30:17 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180316213017.B4F89B80CE7@rfc-editor.org>
Date: Fri, 16 Mar 2018 14:30:17 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8344_on_A_YANG_Data_Model_for_IP_Managem?= =?utf-8?q?ent?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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, netmod@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 8344

        Title:      A YANG Data Model for IP Management 
        Author:     M. Bjorklund
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    mbj@tail-f.com
        Pages:      34
        Characters: 59931
        Obsoletes:  RFC 7277

        I-D Tag:    draft-ietf-netmod-rfc7277bis-03.txt

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

        DOI:        10.17487/RFC8344

This document defines a YANG data model for management of IP
implementations.  The data model includes configuration and system
state.

The YANG data model in this document conforms to the Network
Management Datastore Architecture defined in RFC 8342.

This document obsoletes RFC 7277.

This document is a product of the Network Modeling Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Fri Mar 16 14:31:01 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D593012D941 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 16 Mar 2018 14:31:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 YdLJ-HERQp7G for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 16 Mar 2018 14:31:00 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B48951271FD for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 16 Mar 2018 14:30:44 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5623CB80CFA; Fri, 16 Mar 2018 14:30:41 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 51348B80CF9; Fri, 16 Mar 2018 14:30:40 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180316213040.51348B80CF9@rfc-editor.org>
Date: Fri, 16 Mar 2018 14:30:40 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8345_on_A_YANG_Data_Model_for_Network_To?= =?utf-8?q?pologies?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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, i2rs@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 8345

        Title:      A YANG Data Model for 
                    Network Topologies 
        Author:     A. Clemm,
                    J. Medved,
                    R. Varga, 
                    N. Bahadur,
                    H. Ananthakrishnan,
                    X. Liu
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    ludwig@clemm.org, 
                    jmedved@cisco.com,
                    robert.varga@pantheon.tech, 
                    nitin_bahadur@yahoo.com,
                    hari@packetdesign.com, 
                    xufeng_liu@jabil.com
        Pages:      57
        Characters: 111154
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-i2rs-yang-network-topo-20.txt

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

        DOI:        10.17487/RFC8345

This document defines an abstract (generic, or base) YANG data model
for network/service topologies and inventories.  The data model
serves as a base model that is augmented with technology-specific
details in other, more specific topology and inventory data models.

This document is a product of the Interface to the Routing System Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Fri Mar 16 14:31:17 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23D981267BB for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 16 Mar 2018 14:31:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 c0MIsA7-jwCo for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 16 Mar 2018 14:31:08 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFA72126BF0 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 16 Mar 2018 14:31:02 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id ED3BCB80CF9; Fri, 16 Mar 2018 14:30:55 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 6FE3EB80CDB; Fri, 16 Mar 2018 14:30:54 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180316213054.6FE3EB80CDB@rfc-editor.org>
Date: Fri, 16 Mar 2018 14:30:54 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8346_on_A_YANG_Data_Model_for_Layer_3_To?= =?utf-8?q?pologies?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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, i2rs@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 8346

        Title:      A YANG Data Model for 
                    Layer 3 Topologies 
        Author:     A. Clemm, 
                    J. Medved,
                    R. Varga,
                    X. Liu,
                    H. Ananthakrishnan,
                    N. Bahadur
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    ludwig@clemm.org, 
                    jmedved@cisco.com,
                    robert.varga@pantheon.tech, 
                    xufeng.liu.ietf@gmail.com,
                    hari@packetdesign.com, 
                    nitin_bahadur@yahoo.com
        Pages:      35
        Characters: 64661
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-i2rs-yang-l3-topology-16.txt

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

        DOI:        10.17487/RFC8346

This document defines a YANG data model for Layer 3 network
topologies.

This document is a product of the Interface to the Routing System Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Mon Mar 19 15:23:25 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 906B912D77E for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 19 Mar 2018 15:23:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 KYRTKoEtzhZY for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 19 Mar 2018 15:23:23 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9846712D778 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 19 Mar 2018 15:23:23 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 456BCB810E4; Mon, 19 Mar 2018 15:23:15 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 9400DB810E0; Mon, 19 Mar 2018 15:23:14 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180319222314.9400DB810E0@rfc-editor.org>
Date: Mon, 19 Mar 2018 15:23:14 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8308_on_Extension_Negotiation_in_the_Sec?= =?utf-8?q?ure_Shell_=28SSH=29_Protocol?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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, curdle@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 8308

        Title:      Extension Negotiation in the 
                    Secure Shell (SSH) Protocol 
        Author:     D. Bider
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    ietf-ssh3@denisbider.com
        Pages:      14
        Characters: 29204
        Updates:    RFC 4251, RFC 4252, RFC 4253, RFC 4254

        I-D Tag:    draft-ietf-curdle-ssh-ext-info-15.txt

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

        DOI:        10.17487/RFC8308

This memo updates RFCs 4251, 4252, 4253, and 4254 by defining a
mechanism for Secure Shell (SSH) clients and servers to exchange
information about supported protocol extensions confidentially after
SSH key exchange.

This document is a product of the CURves, Deprecating and a Little more Encryption Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Mon Mar 19 15:23:57 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6424F12E044 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 19 Mar 2018 15:23:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 ZAU7EBlttH_C for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 19 Mar 2018 15:23:48 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1904312E76A for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 19 Mar 2018 15:23:42 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id BD2F4B810FA; Mon, 19 Mar 2018 15:23:28 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id B356EB810F9; Mon, 19 Mar 2018 15:23:27 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180319222327.B356EB810F9@rfc-editor.org>
Date: Mon, 19 Mar 2018 15:23:27 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8332_on_Use_of_RSA_Keys_with_SHA-256_and?= =?utf-8?q?_SHA-512_in_the_Secure_Shell_=28SSH=29_Protocol?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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, curdle@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 8332

        Title:      Use of RSA Keys with SHA-256 and SHA-512 
                    in the Secure Shell (SSH) Protocol 
        Author:     D. Bider
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    ietf-ssh3@denisbider.com
        Pages:      9
        Characters: 17873
        Updates:    RFC 4252, RFC 4253

        I-D Tag:    draft-ietf-curdle-rsa-sha2-12.txt

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

        DOI:        10.17487/RFC8332

This memo updates RFCs 4252 and 4253 to define new public key
algorithms for use of RSA keys with SHA-256 and SHA-512 for server
and client authentication in SSH connections.

This document is a product of the CURves, Deprecating and a Little more Encryption Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Mon Mar 19 20:25:17 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C49A512D779 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 19 Mar 2018 20:25:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 taXB-7lWcUsV for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 19 Mar 2018 20:25:16 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DC4C12D7F6 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 19 Mar 2018 20:25:16 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id C2769B80C5A; Mon, 19 Mar 2018 20:25:07 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id A7B03B80C59; Mon, 19 Mar 2018 20:25:06 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180320032506.A7B03B80C59@rfc-editor.org>
Date: Mon, 19 Mar 2018 20:25:06 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8349_on_A_YANG_Data_Model_for_Routing_Ma?= =?utf-8?q?nagement_=28NMDA_Version=29?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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, netmod@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 8349

        Title:      A YANG Data Model for 
                    Routing Management (NMDA Version) 
        Author:     L. Lhotka,
                    A. Lindem,
                    Y. Qu
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    lhotka@nic.cz, 
                    acee@cisco.com, 
                    yingzhen.qu@huawei.com
        Pages:      80
        Characters: 147002
        Obsoletes:  RFC 8022

        I-D Tag:    draft-ietf-netmod-rfc8022bis-11.txt

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

        DOI:        10.17487/RFC8349

This document specifies three YANG modules and one submodule.
Together, they form the core routing data model that serves as a
framework for configuring and managing a routing subsystem.  It is
expected that these modules will be augmented by additional YANG
modules defining data models for control-plane protocols, route
filters, and other functions.  The core routing data model provides
common building blocks for such extensions -- routes, Routing
Information Bases (RIBs), and control-plane protocols.

The YANG modules in this document conform to the Network Management
Datastore Architecture (NMDA).  This document obsoletes RFC 8022.

This document is a product of the Network Modeling Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Wed Mar 21 11:40:29 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 671F6127871 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 21 Mar 2018 11:40:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 yZoxHwqaCLNV for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 21 Mar 2018 11:40:27 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE69012778D for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 21 Mar 2018 11:40:27 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 47D02B82671; Wed, 21 Mar 2018 11:40:17 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 6E942B8265C; Wed, 21 Mar 2018 11:40:15 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180321184015.6E942B8265C@rfc-editor.org>
Date: Wed, 21 Mar 2018 11:40:15 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8310_on_Usage_Profiles_for_DNS_over_TLS_?= =?utf-8?q?and_DNS_over_DTLS?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, dns-privacy@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8310

        Title:      Usage Profiles for DNS over TLS
                    and DNS over DTLS 
        Author:     S. Dickinson, 
                    D. Gillmor,
                    T. Reddy
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    sara@sinodun.com, 
                    dkg@fifthhorseman.net, 
                    tirumaleswarreddy_konda@mcafee.com
        Pages:      27
        Characters: 58893
        Updates:    RFC 7858

        I-D Tag:    draft-ietf-dprive-dtls-and-tls-profiles-11.txt

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

        DOI:        10.17487/RFC8310

This document discusses usage profiles, based on one or more
authentication mechanisms, which can be used for DNS over Transport
Layer Security (TLS) or Datagram TLS (DTLS).  These profiles can
increase the privacy of DNS transactions compared to using only
cleartext DNS.  This document also specifies new authentication
mechanisms -- it describes several ways that a DNS client can use an
authentication domain name to authenticate a (D)TLS connection to a
DNS server.  Additionally, it defines (D)TLS protocol profiles for
DNS clients and servers implementing DNS over (D)TLS.  This document
updates RFC 7858.

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

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Wed Mar 21 11:41:04 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5438127863 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 21 Mar 2018 11:41:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 uGZBa7S5kay4 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 21 Mar 2018 11:41:03 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EF9112E88F for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 21 Mar 2018 11:40:47 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id B7A27B826ED; Wed, 21 Mar 2018 11:40:28 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 42E27B826E7; Wed, 21 Mar 2018 11:40:28 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180321184028.42E27B826E7@rfc-editor.org>
Date: Wed, 21 Mar 2018 11:40:28 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8328_on_Policy-Based_Management_Framewor?= =?utf-8?q?k_for_the_Simplified_Use_of_Policy_Abstractions_=28SUPA=29?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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 8328

        Title:      Policy-Based Management Framework for the 
                    Simplified Use of Policy Abstractions (SUPA) 
        Author:     W. Liu, 
                    C. Xie,
                    J. Strassner, 
                    G. Karagiannis,
                    M. Klyus,
                    J. Bi,
                    Y. Cheng, 
                    D. Zhang
        Status:     Informational
        Stream:     Independent
        Date:       March 2018
        Mailbox:    liushucheng@huawei.com, 
                    xiechf.bri@chinatelecom.cn, 
                    john.sc.strassner@huawei.com,  
                    georgios.karagiannis@huawei.com, 
                    xmaruto@gmail.com,
                    junbi@tsinghua.edu.cn, 
                    chengying10@chinaunicom.cn,
                    dacheng.zhang@huawei.com
        Pages:      15
        Characters: 33046
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-liu-policy-based-management-framework-00.txt

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

        DOI:        10.17487/RFC8328

The Simplified Use of Policy Abstractions (SUPA) policy-based
management framework defines base YANG data models to encode policy.
These models point to device-, technology-, and service-specific YANG
data models developed elsewhere.  Policy rules within an operator's
environment can be used to express high-level, possibly network-wide,
policies to a network management function (within a controller, an
orchestrator, or a network element).  The network management function
can then control the configuration and/or monitoring of network
elements and services.  This document describes the SUPA basic
framework, its elements, and interfaces.


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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Wed Mar 21 11:48:46 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2F2B127909 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 21 Mar 2018 11:48:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 G_KGdOv0F9XT for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 21 Mar 2018 11:48:45 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC17412E886 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 21 Mar 2018 11:41:02 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 18CD6B8279B; Wed, 21 Mar 2018 11:40:51 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id AE7EDB81C43; Wed, 21 Mar 2018 11:40:49 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180321184049.AE7EDB81C43@rfc-editor.org>
Date: Wed, 21 Mar 2018 11:40:49 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8336_on_The_ORIGIN_HTTP/2_Frame?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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, ietf-http-wg@w3.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 8336

        Title:      The ORIGIN HTTP/2 Frame 
        Author:     M. Nottingham,
                    E. Nygren
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    mnot@mnot.net, 
                    erik+ietf@nygren.org
        Pages:      11
        Characters: 22168
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-httpbis-origin-frame-06.txt

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

        DOI:        10.17487/RFC8336

This document specifies the ORIGIN frame for HTTP/2, to indicate what
origins are available on a given connection.

This document is a product of the Hypertext Transfer Protocol Bis Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Mon Mar 26 16:10:25 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B14E126C0F for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 26 Mar 2018 16:10:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 UyNeAJms78tc for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 26 Mar 2018 16:10:13 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E37241277BB for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 26 Mar 2018 16:10:13 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 1D36DB83034; Mon, 26 Mar 2018 16:09:56 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 9391FB83033; Mon, 26 Mar 2018 16:09:55 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180326230955.9391FB83033@rfc-editor.org>
Date: Mon, 26 Mar 2018 16:09:55 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8348_on_A_YANG_Data_Model_for_Hardware_M?= =?utf-8?q?anagement?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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, netmod@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 8348

        Title:      A YANG Data Model for 
                    Hardware Management 
        Author:     A. Bierman,
                    M. Bjorklund,
                    J. Dong, 
                    D. Romascanu
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018 
        Mailbox:    andy@yumaworks.com, 
                    mbj@tail-f.com, 
                    jie.dong@huawei.com,
                    dromasca@gmail.com
        Pages:      60
        Characters: 108230
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-netmod-entity-08.txt

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

        DOI:        10.17487/RFC8348

This document defines a YANG data model for the management of
hardware on a single server.

This document is a product of the Network Modeling Working Group of the IETF.

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Wed Mar 28 09:29:58 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 535A912783A for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 28 Mar 2018 09:29:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 4-ASRsA-BEjP for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 28 Mar 2018 09:29:56 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C08C1243F6 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 28 Mar 2018 09:29:53 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id DA699B810BA; Wed, 28 Mar 2018 09:29:32 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 2E21BB810BB; Wed, 28 Mar 2018 09:29:31 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180328162931.2E21BB810BB@rfc-editor.org>
Date: Wed, 28 Mar 2018 09:29:31 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8347_on_A_YANG_Data_Model_for_the_Virtua?= =?utf-8?q?l_Router_Redundancy_Protocol_=28VRRP=29?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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 8347

        Title:      A YANG Data Model for the
                    Virtual Router Redundancy Protocol (VRRP) 
        Author:     X. Liu, Ed.,
                    A. Kyparlis,
                    R. Parikh,
                    A. Lindem,
                    M. Zhang
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    xufeng.liu.ietf@gmail.com, 
                    athanasios_kyparlis@jabil.com, 
                    parikhr@vmware.com,
                    acee@cisco.com, 
                    zhangmingui@huawei.com
        Pages:      45
        Characters: 79218
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtgwg-yang-vrrp-11.txt

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

        DOI:        10.17487/RFC8347

This document describes a data model for the Virtual Router
Redundancy Protocol (VRRP).  Both versions 2 and 3 of VRRP are
covered.

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

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Wed Mar 28 16:28:21 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BB46129C6E for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 28 Mar 2018 16:28:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 sVJK2_bEKG6O for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 28 Mar 2018 16:28:20 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 10EFC126CC4 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 28 Mar 2018 16:28:20 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 85395B812F7; Wed, 28 Mar 2018 16:27:59 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 44965B812F7; Wed, 28 Mar 2018 16:27:58 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180328232758.44965B812F7@rfc-editor.org>
Date: Wed, 28 Mar 2018 16:27:58 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8333_on_Micro-loop_Prevention_by_Introdu?= =?utf-8?q?cing_a_Local_Convergence_Delay?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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 8333

        Title:      Micro-loop Prevention by Introducing a 
                    Local Convergence Delay 
        Author:     S. Litkowski,
                    B. Decraene,
                    C. Filsfils,
                    P. Francois
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    stephane.litkowski@orange.com, 
                    bruno.decraene@orange.com, 
                    cfilsfil@cisco.com,
                    pfrpfr@gmail.com
        Pages:      26
        Characters: 63119
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtgwg-uloop-delay-09.txt

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

        DOI:        10.17487/RFC8333

This document describes a mechanism for link-state routing protocols
that prevents local transient forwarding loops in case of link
failure.  This mechanism proposes a two-step convergence by
introducing a delay between the convergence of the node adjacent to
the topology change and the network-wide convergence.

Because this mechanism delays the IGP convergence, it may only be
used for planned maintenance or when Fast Reroute (FRR) protects the
traffic during the time between the link failure and the IGP
convergence.

The mechanism is limited to the link-down event in order to keep the
mechanism simple.

Simulations using real network topologies have been performed and
show that local loops are a significant portion (>50%) of the total
forwarding loops.

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

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Wed Mar 28 16:29:05 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9833F12D7F3 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 28 Mar 2018 16:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 xYsOb7IW0q1e for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 28 Mar 2018 16:29:04 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B58B012D964 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 28 Mar 2018 16:28:41 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id F147CB81302; Wed, 28 Mar 2018 16:28:21 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 5FDB3B81301; Wed, 28 Mar 2018 16:28:20 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180328232820.5FDB3B81301@rfc-editor.org>
Date: Wed, 28 Mar 2018 16:28:20 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8354_on_Use_Cases_for_IPv6_Source_Packet?= =?utf-8?q?_Routing_in_Networking_=28SPRING=29?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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 8354

        Title:      Use Cases for IPv6 Source 
                    Packet Routing in Networking (SPRING) 
        Author:     J. Brzozowski,
                    J. Leddy,
                    C. Filsfils,
                    R. Maglione, Ed.,
                    M. Townsley
        Status:     Informational
        Stream:     IETF
        Date:       March 2018
        Mailbox:    john_brzozowski@cable.comcast.com, 
                    john_leddy@cable.comcast.com, 
                    cfilsfil@cisco.com, 
                    robmgl@cisco.com, 
                    townsley@cisco.com
        Pages:      9
        Characters: 18271
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-spring-ipv6-use-cases-12.txt

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

        DOI:        10.17487/RFC8354

The Source Packet Routing in Networking (SPRING) architecture
describes how Segment Routing can be used to steer packets through an
IPv6 or MPLS network using the source routing paradigm.  This
document illustrates some use cases for Segment Routing in an
IPv6-only environment.

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 Mar 28 16:29:38 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2670F12E8A9 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 28 Mar 2018 16:29:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 O9JUI2ZYhB4q for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 28 Mar 2018 16:29:30 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 236BF12E898 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 28 Mar 2018 16:29:03 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 6096CB8130E; Wed, 28 Mar 2018 16:28:43 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 37B77B8130C; Wed, 28 Mar 2018 16:28:42 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180328232842.37B77B8130C@rfc-editor.org>
Date: Wed, 28 Mar 2018 16:28:42 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8355_on_Resiliency_Use_Cases_in_Source_P?= =?utf-8?q?acket_Routing_in_Networking_=28SPRING=29_Networks?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
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 8355

        Title:      Resiliency Use Cases in Source Packet
                    Routing in Networking (SPRING) Networks 
        Author:     C. Filsfils, Ed.,
                    S. Previdi, Ed.,
                    B. Decraene,
                    R. Shakir
        Status:     Informational
        Stream:     IETF
        Date:       March 2018
        Mailbox:    cfilsfil@cisco.com, 
                    stefano@previdi.net, 
                    bruno.decraene@orange.com,
                    robjs@google.com
        Pages:      13
        Characters: 24684
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-spring-resiliency-use-cases-12.txt

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

        DOI:        10.17487/RFC8355

This document identifies and describes the requirements for a set of
use cases related to Segment Routing network resiliency on Source
Packet Routing in Networking (SPRING) networks.

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 Mar 28 16:30:11 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAAEA12EAF1 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 28 Mar 2018 16:30:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 OJCt-GJ9ORmt for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 28 Mar 2018 16:30:10 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB2EB12D77B for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 28 Mar 2018 16:29:17 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id CA5F4B81315; Wed, 28 Mar 2018 16:28:56 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 051EBB812FB; Wed, 28 Mar 2018 16:28:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180328232856.051EBB812FB@rfc-editor.org>
Date: Wed, 28 Mar 2018 16:28:56 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8364_on_PIM_Flooding_Mechanism_=28PFM=29?= =?utf-8?q?_and_Source_Discovery_=28SD=29?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, pim@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8364

        Title:      PIM Flooding Mechanism (PFM) and 
                    Source Discovery (SD) 
        Author:     IJ. Wijnands,
                    S. Venaas,
                    M. Brig,
                    A. Jonasson
        Status:     Experimental
        Stream:     IETF
        Date:       March 2018
        Mailbox:    ice@cisco.com, 
                    stig@cisco.com, 
                    michael.brig@mda.mil,
                    anders@jomac.se
        Pages:      18
        Characters: 44640
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pim-source-discovery-bsr-12.txt

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

        DOI:        10.17487/RFC8364

Protocol Independent Multicast - Sparse Mode (PIM-SM) uses a
Rendezvous Point (RP) and shared trees to forward multicast packets
from new sources.  Once Last-Hop Routers (LHRs) receive packets from
a new source, they may join the Shortest Path Tree (SPT) for the
source for optimal forwarding.  This document defines a new mechanism
that provides a way to support PIM-SM without the need for PIM
registers, RPs, or shared trees.  Multicast source information is
flooded throughout the multicast domain using a new generic PIM
Flooding Mechanism (PFM).  This allows LHRs to learn about new
sources without receiving initial data packets.

This document is a product of the Protocols for IP Multicast Working Group of the IETF.


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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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

From rfc-dist-bounces@rfc-editor.org  Thu Mar 29 18:02:01 2018
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41499127775 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 29 Mar 2018 18:02:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 nt-tcPAY5-Jk for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 29 Mar 2018 18:01:59 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBF9A126579 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 29 Mar 2018 18:01:59 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id EE02FB80D10; Thu, 29 Mar 2018 18:01:37 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 21D49B80D0E; Thu, 29 Mar 2018 18:01:36 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20180330010136.21D49B80D0E@rfc-editor.org>
Date: Thu, 29 Mar 2018 18:01:36 -0700 (PDT)
Subject: [rfc-dist] =?utf-8?q?RFC_8365_on_A_Network_Virtualization_Overlay?= =?utf-8?q?_Solution_Using_Ethernet_VPN_=28EVPN=29?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, bess@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

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

        
        RFC 8365

        Title:      A Network Virtualization Overlay Solution 
                    Using Ethernet VPN (EVPN) 
        Author:     A. Sajassi, Ed.,
                    J. Drake, Ed.,
                    N. Bitar,
                    R. Shekhar,
                    J. Uttaro,
                    W. Henderickx
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2018
        Mailbox:    sajassi@cisco.com, 
                    jdrake@juniper.net, 
                    nabil.bitar@nokia.com,
                    rshekhar@juniper.net, 
                    uttaro@att.com,
                    wim.henderickx@nokia.com
        Pages:      33
        Characters: 76766
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bess-evpn-overlay-12.txt

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

        DOI:        10.17487/RFC8365

This document specifies how Ethernet VPN (EVPN) can be used as a
Network Virtualization Overlay (NVO) solution and explores the
various tunnel encapsulation options over IP and their impact on the
EVPN control plane and procedures.  In particular, the following
encapsulation options are analyzed: Virtual Extensible LAN (VXLAN),
Network Virtualization using Generic Routing Encapsulation (NVGRE),
and MPLS over GRE.  This specification is also applicable to Generic
Network Virtualization Encapsulation (GENEVE); however, some
incremental work is required, which will be covered in a separate
document.  This document also specifies new multihoming procedures
for split-horizon filtering and mass withdrawal.  It also specifies
EVPN route constructions for VXLAN/NVGRE encapsulations and
Autonomous System Border Router (ASBR) procedures for multihoming of
Network Virtualization Edge (NVE) devices.

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

This is now a Proposed Standard.

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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC


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