From rfc-dist-bounces@rfc-editor.org Tue Jan 2 15:58:44 2018 Return-Path: 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 8BDCB12D84E for ; Tue, 2 Jan 2018 15:58:44 -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 KvJbpfvSOyYF for ; Tue, 2 Jan 2018 15:58:43 -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 72C65120721 for ; Tue, 2 Jan 2018 15:58:43 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 76AF2B80DA1; Tue, 2 Jan 2018 15:58: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 AC609B80D9F; Tue, 2 Jan 2018 15:58: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: <20180102235826.AC609B80D9F@rfc-editor.org> Date: Tue, 2 Jan 2018 15:58:26 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8293_on_A_Framework_for_Multicast_in_Net?= =?utf-8?q?work_Virtualization_over_Layer_3?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, nvo3@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" A new Request for Comments is now available in online RFC libraries. RFC 8293 Title: A Framework for Multicast in Network Virtualization over Layer 3 Author: A. Ghanwani, L. Dunbar, M. McBride, V. Bannai, R. Krishnan Status: Informational Stream: IETF Date: January 2018 Mailbox: anoop@alumni.duke.edu, ldunbar@huawei.com, mmcbride7@gmail.com, vbannai@gmail.com, ramkri123@gmail.com Pages: 17 Characters: 37578 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-nvo3-mcast-framework-11.txt URL: https://www.rfc-editor.org/info/rfc8293 DOI: 10.17487/RFC8293 This document provides a framework for supporting multicast traffic in a network that uses Network Virtualization over Layer 3 (NVO3). Both infrastructure multicast and application-specific multicast are discussed. It describes the various mechanisms that can be used for delivering such traffic as well as the data plane and control plane considerations for each of the mechanisms. This document is a product of the Network Virtualization Overlays Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Tue Jan 2 15:59:20 2018 Return-Path: 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 9753312D85E for ; Tue, 2 Jan 2018 15:59: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=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 RVdOajf33OWs for ; Tue, 2 Jan 2018 15:59:18 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AB1612D864 for ; Tue, 2 Jan 2018 15:59:03 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id E7C49B80DB2; Tue, 2 Jan 2018 15:58:45 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 8B49DB80DAD; Tue, 2 Jan 2018 15:58:44 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180102235844.8B49DB80DAD@rfc-editor.org> Date: Tue, 2 Jan 2018 15:58:44 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8307_on_Well-Known_URIs_for_the_WebSocke?= =?utf-8?q?t_Protocol?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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" A new Request for Comments is now available in online RFC libraries. RFC 8307 Title: Well-Known URIs for the WebSocket Protocol Author: C. Bormann Status: Standards Track Stream: IETF Date: January 2018 Mailbox: cabo@tzi.org Pages: 3 Characters: 5945 Updates: RFC 6455 I-D Tag: draft-bormann-hybi-ws-wk-00.txt URL: https://www.rfc-editor.org/info/rfc8307 DOI: 10.17487/RFC8307 RFC 5785 defines a path prefix, "/.well-known/", that can be used by well-known URIs. It was specifically defined for the "http" and "https" URI schemes. The present memo formally updates RFC 6455, which defines the URI schemes defined for the WebSocket Protocol, to extend the use of these well-known URIs to those URI schemes. 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 Jan 5 16:02:14 2018 Return-Path: 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 CDF3412D96C for ; Fri, 5 Jan 2018 16:02:14 -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 4LCnqgWGG_6M for ; Fri, 5 Jan 2018 16:02:13 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5D23126B6E for ; Fri, 5 Jan 2018 16:02:13 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id EB1B7B81EC7; Fri, 5 Jan 2018 16:01:55 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id B2B1EB81EC5; Fri, 5 Jan 2018 16:01:54 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180106000154.B2B1EB81EC5@rfc-editor.org> Date: Fri, 5 Jan 2018 16:01:54 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8289_on_Controlled_Delay_Active_Queue_Ma?= =?utf-8?q?nagement?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, aqm@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" A new Request for Comments is now available in online RFC libraries. RFC 8289 Title: Controlled Delay Active Queue Management Author: K. Nichols, V. Jacobson, A. McGregor, Ed., J. Iyengar, Ed. Status: Experimental Stream: IETF Date: January 2018 Mailbox: nichols@pollere.com, vanj@google.com, andrewmcgr@google.com, jri@google.com Pages: 25 Characters: 63404 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-aqm-codel-10.txt URL: https://www.rfc-editor.org/info/rfc8289 DOI: 10.17487/RFC8289 This document describes CoDel (Controlled Delay) -- a general framework that controls bufferbloat-generated excess delay in modern networking environments. CoDel consists of an estimator, a setpoint, and a control loop. It requires no configuration in normal Internet deployments. This document is a product of the Active Queue Management and Packet Scheduling 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 Jan 5 16:02:36 2018 Return-Path: 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 B4C01126D0C for ; Fri, 5 Jan 2018 16:02:36 -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 pbfqCpFcEcRJ for ; Fri, 5 Jan 2018 16:02:35 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDBA412D96C for ; Fri, 5 Jan 2018 16:02:32 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 764D6B81ED1; Fri, 5 Jan 2018 16:02:11 -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 62EA9B81ED0; Fri, 5 Jan 2018 16:02:10 -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: <20180106000210.62EA9B81ED0@rfc-editor.org> Date: Fri, 5 Jan 2018 16:02:10 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8290_on_The_Flow_Queue_CoDel_Packet_Sche?= =?utf-8?q?duler_and_Active_Queue_Management_Algorithm?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, aqm@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" A new Request for Comments is now available in online RFC libraries. RFC 8290 Title: The Flow Queue CoDel Packet Scheduler and Active Queue Management Algorithm Author: T. Hoeiland-Joergensen, P. McKenney, D. Taht, J. Gettys, E. Dumazet Status: Experimental Stream: IETF Date: January 2018 Mailbox: toke@toke.dk, paulmck@linux.vnet.ibm.com, dave.taht@gmail.com, jg@freedesktop.org, edumazet@gmail.com Pages: 25 Characters: 57767 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-aqm-fq-codel-06.txt URL: https://www.rfc-editor.org/info/rfc8290 DOI: 10.17487/RFC8290 This memo presents the FQ-CoDel hybrid packet scheduler and Active Queue Management (AQM) algorithm, a powerful tool for fighting bufferbloat and reducing latency. FQ-CoDel mixes packets from multiple flows and reduces the impact of head-of-line blocking from bursty traffic. It provides isolation for low-rate traffic such as DNS, web, and videoconferencing traffic. It improves utilisation across the networking fabric, especially for bidirectional traffic, by keeping queue lengths short, and it can be implemented in a memory- and CPU-efficient fashion across a wide range of hardware. This document is a product of the Active Queue Management and Packet Scheduling 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 Jan 5 16:03:13 2018 Return-Path: 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 253E312DA15 for ; Fri, 5 Jan 2018 16:03:13 -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 1UVixIMb4wQt for ; Fri, 5 Jan 2018 16:03:11 -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 43E0112D96D for ; Fri, 5 Jan 2018 16:02:49 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D3F1BB81ED8; Fri, 5 Jan 2018 16:02:24 -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 B138CB81EDB; Fri, 5 Jan 2018 16:02:23 -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: <20180106000223.B138CB81EDB@rfc-editor.org> Date: Fri, 5 Jan 2018 16:02:23 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8302_on_Transparent_Interconnection_of_L?= =?utf-8?q?ots_of_Links_=28TRILL=29=3A_ARP_and_Neighbor_Discovery_=28ND=29?= =?utf-8?q?_Optimization?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, trill@ietf.org, rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: rfc-dist-bounces@rfc-editor.org Sender: "rfc-dist" A new Request for Comments is now available in online RFC libraries. RFC 8302 Title: Transparent Interconnection of Lots of Links (TRILL): ARP and Neighbor Discovery (ND) Optimization Author: Y. Li, D. Eastlake 3rd, L. Dunbar, R. Perlman, M. Umair Status: Standards Track Stream: IETF Date: January 2018 Mailbox: liyizhou@huawei.com, d3e3e3@gmail.com, ldunbar@huawei.com, radia@alum.mit.edu, mohammed.umair2@gmail.com Pages: 18 Characters: 41883 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-trill-arp-optimization-09.txt URL: https://www.rfc-editor.org/info/rfc8302 DOI: 10.17487/RFC8302 This document describes mechanisms to optimize the Address Resolution Protocol (ARP) and Neighbor Discovery (ND) traffic in a Transparent Interconnection of Lots of Links (TRILL) campus. TRILL switches maintain a cache of IP / Media Access Control (MAC) address / Data Label bindings that are learned from ARP/ND requests and responses that pass through them. In many cases, this cache allows an edge Routing Bridge (RBridge) to avoid flooding an ARP/ND request by either responding to it directly or encapsulating it and unicasting it. Such optimization reduces packet flooding over a TRILL campus. This document is a product of the Transparent Interconnection of Lots of Links 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 Jan 12 14:53:36 2018 Return-Path: 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 F3B5312778E for ; Fri, 12 Jan 2018 14:53:35 -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 YV_Yfn7f_LD8 for ; Fri, 12 Jan 2018 14:53:34 -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 6A28C124BE8 for ; Fri, 12 Jan 2018 14:53:34 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 4659EB8214B; Fri, 12 Jan 2018 14:53: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 E9082B8214A; Fri, 12 Jan 2018 14:53:08 -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: <20180112225308.E9082B8214A@rfc-editor.org> Date: Fri, 12 Jan 2018 14:53:08 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8296_on_Encapsulation_for_Bit_Index_Expl?= =?utf-8?q?icit_Replication_=28BIER=29_in_MPLS_and_Non-MPLS_Networks?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, bier@ietf.org, rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: rfc-dist-bounces@rfc-editor.org Sender: "rfc-dist" A new Request for Comments is now available in online RFC libraries. RFC 8296 Title: Encapsulation for Bit Index Explicit Replication (BIER) in MPLS and Non-MPLS Networks Author: IJ. Wijnands, Ed., E. Rosen, Ed., A. Dolganow, J. Tantsura, S. Aldrin, I. Meilik Status: Experimental Stream: IETF Date: January 2018 Mailbox: ice@cisco.com, erosen@juniper.net, andrew.dolganow@nokia.com, jefftant.ietf@gmail.com, aldrin.ietf@gmail.com, israel@broadcom.com Pages: 24 Characters: 47866 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-bier-mpls-encapsulation-12.txt URL: https://www.rfc-editor.org/info/rfc8296 DOI: 10.17487/RFC8296 Bit Index Explicit Replication (BIER) is an architecture that provides optimal multicast forwarding through a "multicast domain", without requiring intermediate routers to maintain any per-flow state or to engage in an explicit tree-building protocol. When a multicast data packet enters the domain, the ingress router determines the set of egress routers to which the packet needs to be sent. The ingress router then encapsulates the packet in a BIER header. The BIER header contains a bit string in which each bit represents exactly one egress router in the domain; to forward the packet to a given set of egress routers, the bits corresponding to those routers are set in the BIER header. The details of the encapsulation depend on the type of network used to realize the multicast domain. This document specifies a BIER encapsulation that can be used in an MPLS network or, with slight differences, in a non-MPLS network. This document is a product of the Bit Indexed Explicit Replication Working Group of the IETF. 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 Jan 12 14:54:14 2018 Return-Path: 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 E14F412D860 for ; Fri, 12 Jan 2018 14:54:14 -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 9IZ6lwInz1dF for ; Fri, 12 Jan 2018 14:54:13 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49A0B12D830 for ; Fri, 12 Jan 2018 14:53:54 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D19EFB82156; Fri, 12 Jan 2018 14:53:23 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id DD9F9B82155; Fri, 12 Jan 2018 14:53:22 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180112225322.DD9F9B82155@rfc-editor.org> Date: Fri, 12 Jan 2018 14:53:22 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8300_on_Network_Service_Header_=28NSH=29?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, sfc@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" A new Request for Comments is now available in online RFC libraries. RFC 8300 Title: Network Service Header (NSH) Author: P. Quinn, Ed., U. Elzur, Ed., C. Pignataro, Ed. Status: Standards Track Stream: IETF Date: January 2018 Mailbox: paulq@cisco.com, uri.elzur@intel.com, cpignata@cisco.com Pages: 40 Characters: 93675 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-sfc-nsh-28.txt URL: https://www.rfc-editor.org/info/rfc8300 DOI: 10.17487/RFC8300 This document describes a Network Service Header (NSH) imposed on packets or frames to realize Service Function Paths (SFPs). The NSH also provides a mechanism for metadata exchange along the instantiated service paths. The NSH is the Service Function Chaining (SFC) encapsulation required to support the SFC architecture (defined in RFC 7665). This document is a product of the Service Function Chaining 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 Jan 12 14:54:43 2018 Return-Path: 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 6CD3912D7E5 for ; Fri, 12 Jan 2018 14:54:43 -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 RWuTYw1E_ukl for ; Fri, 12 Jan 2018 14:54:41 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8755E12D851 for ; Fri, 12 Jan 2018 14:54:09 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 3E4FBB82161; Fri, 12 Jan 2018 14:53:40 -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 5BB80B82161; Fri, 12 Jan 2018 14:53:38 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180112225338.5BB80B82161@rfc-editor.org> Date: Fri, 12 Jan 2018 14:53:38 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8309_on_Service_Models_Explained?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, opsawg@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" A new Request for Comments is now available in online RFC libraries. RFC 8309 Title: Service Models Explained Author: Q. Wu, W. Liu, A. Farrel Status: Informational Stream: IETF Date: January 2018 Mailbox: bill.wu@huawei.com, liushucheng@huawei.com, afarrel@juniper.net Pages: 23 Characters: 54082 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-opsawg-service-model-explained-05.txt URL: https://www.rfc-editor.org/info/rfc8309 DOI: 10.17487/RFC8309 The IETF has produced many modules in the YANG modeling language. The majority of these modules are used to construct data models to model devices or monolithic functions. A small number of YANG modules have been defined to model services (for example, the Layer 3 Virtual Private Network Service Model (L3SM) produced by the L3SM working group and documented in RFC 8049). This document describes service models as used within the IETF and also shows where a service model might fit into a software-defined networking architecture. Note that service models do not make any assumption of how a service is actually engineered and delivered for a customer; details of how network protocols and devices are engineered to deliver a service are captured in other modules that are not exposed through the interface between the customer and the provider. This document is a product of the Operations and Management Area Working Group Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Fri Jan 12 14:55:17 2018 Return-Path: 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 59C6612D874 for ; Fri, 12 Jan 2018 14:55:17 -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 UiXqJ3OCnvHd for ; Fri, 12 Jan 2018 14:55:15 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32B1012D87C for ; Fri, 12 Jan 2018 14:54:25 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 9CD13B8216B; Fri, 12 Jan 2018 14:53:52 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id A1028B8216A; Fri, 12 Jan 2018 14:53: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: <20180112225351.A1028B8216A@rfc-editor.org> Date: Fri, 12 Jan 2018 14:53:51 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8311_on_Relaxing_Restrictions_on_Explici?= =?utf-8?q?t_Congestion_Notification_=28ECN=29_Experimentation?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, tsvwg@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" A new Request for Comments is now available in online RFC libraries. RFC 8311 Title: Relaxing Restrictions on Explicit Congestion Notification (ECN) Experimentation Author: D. Black Status: Standards Track Stream: IETF Date: January 2018 Mailbox: david.black@dell.com Pages: 20 Characters: 48310 Updates: RFC 3168, RFC 4341, RFC 4342, RFC 5622, RFC 6679 I-D Tag: draft-ietf-tsvwg-ecn-experimentation-08.txt URL: https://www.rfc-editor.org/info/rfc8311 DOI: 10.17487/RFC8311 This memo updates RFC 3168, which specifies Explicit Congestion Notification (ECN) as an alternative to packet drops for indicating network congestion to endpoints. It relaxes restrictions in RFC 3168 that hinder experimentation towards benefits beyond just removal of loss. This memo summarizes the anticipated areas of experimentation and updates RFC 3168 to enable experimentation in these areas. An Experimental RFC in the IETF document stream is required to take advantage of any of these enabling updates. In addition, this memo makes related updates to the ECN specifications for RTP in RFC 6679 and for the Datagram Congestion Control Protocol (DCCP) in RFCs 4341, 4342, and 5622. This memo also records the conclusion of the ECN nonce experiment in RFC 3540 and provides the rationale for reclassification of RFC 3540 from Experimental to Historic; this reclassification enables new experimental use of the ECT(1) codepoint. This document is a product of the Transport 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 Fri Jan 12 14:55:33 2018 Return-Path: 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 95C2312D87F for ; Fri, 12 Jan 2018 14:55:33 -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 6szIklgDz_mF for ; Fri, 12 Jan 2018 14:55:25 -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 755E712D849 for ; Fri, 12 Jan 2018 14:54:41 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 04671B8214D; Fri, 12 Jan 2018 14:54:06 -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 43DF0B82176; Fri, 12 Jan 2018 14:54:05 -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: <20180112225405.43DF0B82176@rfc-editor.org> Date: Fri, 12 Jan 2018 14:54:05 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?BCP_213=2C_RFC_8313_on_Use_of_Multicast_acro?= =?utf-8?q?ss_Inter-domain_Peering_Points?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: mboned@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: rfc-dist-bounces@rfc-editor.org Sender: "rfc-dist" A new Request for Comments is now available in online RFC libraries. BCP 213 RFC 8313 Title: Use of Multicast across Inter-domain Peering Points Author: P. Tarapore, Ed., R. Sayko, G. Shepherd, T. Eckert, Ed., R. Krishnan Status: Best Current Practice Stream: IETF Date: January 2018 Mailbox: tarapore@att.com, rs1983@att.com, shep@cisco.com, tte+ietf@cs.fau.de, ramkri123@gmail.com Pages: 44 Characters: 98809 See Also: BCP 213 I-D Tag: draft-ietf-mboned-interdomain-peering-bcp-14.txt URL: https://www.rfc-editor.org/info/rfc8313 DOI: 10.17487/RFC8313 This document examines the use of Source-Specific Multicast (SSM) across inter-domain peering points for a specified set of deployment scenarios. The objectives are to (1) describe the setup process for multicast-based delivery across administrative domains for these scenarios and (2) document supporting functionality to enable this process. This document is a product of the MBONE Deployment 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 Jan 19 16:34:55 2018 Return-Path: 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 096C412E059 for ; Fri, 19 Jan 2018 16:34:55 -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 q603CnKBQoIL for ; Fri, 19 Jan 2018 16:34:53 -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 4DC65120713 for ; Fri, 19 Jan 2018 16:34:53 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 0210CB816D0; Fri, 19 Jan 2018 16:34:44 -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 F0216B816CE; Fri, 19 Jan 2018 16:34:41 -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: <20180120003441.F0216B816CE@rfc-editor.org> Date: Fri, 19 Jan 2018 16:34:41 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8299_on_YANG_Data_Model_for_L3VPN_Servic?= =?utf-8?q?e_Delivery?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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" A new Request for Comments is now available in online RFC libraries. RFC 8299 Title: YANG Data Model for L3VPN Service Delivery Author: Q. Wu, Ed., S. Litkowski, L. Tomotaki, K. Ogaki Status: Standards Track Stream: IETF Date: January 2018 Mailbox: bill.wu@huawei.com, stephane.litkowski@orange.com, luis.tomotaki@verizon.com, ke-oogaki@kddi.com Pages: 188 Characters: 344738 Obsoletes: RFC 8049 I-D Tag: draft-wu-l3sm-rfc8049bis-11.txt URL: https://www.rfc-editor.org/info/rfc8299 DOI: 10.17487/RFC8299 This document defines a YANG data model that can be used for communication between customers and network operators and to deliver a Layer 3 provider-provisioned VPN service. This document is limited to BGP PE-based VPNs as described in RFCs 4026, 4110, and 4364. This model is intended to be instantiated at the management system to deliver the overall service. It is not a configuration model to be used directly on network elements. This model provides an abstracted view of the Layer 3 IP VPN service configuration components. It will be up to the management system to take this model as input and use specific configuration models to configure the different network elements to deliver the service. How the configuration of network elements is done is out of scope for this document. This document obsoletes RFC 8049; it replaces the unimplementable module in that RFC with a new module with the same name that is not backward compatible. The changes are a series of small fixes to the YANG module and some clarifications to the text. 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 Jan 19 16:35:40 2018 Return-Path: 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 B884612E858 for ; Fri, 19 Jan 2018 16:35:40 -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 eLrqFEcsEluv for ; Fri, 19 Jan 2018 16:35:38 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00CE112E868 for ; Fri, 19 Jan 2018 16:35:25 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 6D7C3B816DE; Fri, 19 Jan 2018 16:35:16 -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 5693EB816DC; Fri, 19 Jan 2018 16:35:15 -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: <20180120003515.5693EB816DC@rfc-editor.org> Date: Fri, 19 Jan 2018 16:35:15 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8301_on_Cryptographic_Algorithm_and_Key_?= =?utf-8?q?Usage_Update_to_DomainKeys_Identified_Mail_=28DKIM=29?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, dcrup@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" A new Request for Comments is now available in online RFC libraries. RFC 8301 Title: Cryptographic Algorithm and Key Usage Update to DomainKeys Identified Mail (DKIM) Author: S. Kitterman Status: Standards Track Stream: IETF Date: January 2018 Mailbox: scott@kitterman.com Pages: 5 Characters: 10075 Updates: RFC 6376 I-D Tag: draft-ietf-dcrup-dkim-usage-06.txt URL: https://www.rfc-editor.org/info/rfc8301 DOI: 10.17487/RFC8301 The cryptographic algorithm and key size requirements included when DomainKeys Identified Mail (DKIM) was designed a decade ago are functionally obsolete and in need of immediate revision. This document updates DKIM requirements to those minimally suitable for operation with currently specified algorithms. This document is a product of the DKIM Crypto Update 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 Jan 24 08:00:19 2018 Return-Path: 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 3558C12DA4E for ; Wed, 24 Jan 2018 08:00:19 -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 Lvoe1v7flaJO for ; Wed, 24 Jan 2018 08:00:17 -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 1A07D12DA6E for ; Wed, 24 Jan 2018 08:00:17 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 95BA9B80CEF; Wed, 24 Jan 2018 08:00:01 -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 8D9F3B80CED; Wed, 24 Jan 2018 08:00:00 -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: <20180124160000.8D9F3B80CED@rfc-editor.org> Date: Wed, 24 Jan 2018 08:00:00 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8278_on_Mobile_Access_Gateway_=28MAG=29_?= =?utf-8?q?Multipath_Options?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, dmm@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" A new Request for Comments is now available in online RFC libraries. RFC 8278 Title: Mobile Access Gateway (MAG) Multipath Options Author: P. Seite, A. Yegin, S. Gundavelli Status: Standards Track Stream: IETF Date: January 2018 Mailbox: pierrick.seite@orange.com, alper.yegin@actility.com, sgundave@cisco.com Pages: 15 Characters: 32313 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dmm-mag-multihoming-07.txt URL: https://www.rfc-editor.org/info/rfc8278 DOI: 10.17487/RFC8278 This specification defines extensions to the Proxy Mobile IPv6 (PMIPv6) protocol that allow a mobile access gateway (MAG) to register more than one proxy care-of address (pCoA) with the local mobility anchor (LMA) and to simultaneously establish multiple IP tunnels with the LMA. This capability allows the MAG to utilize all the available access networks to route the mobile node's IP traffic. This document defines the following two new mobility header options: the MAG Multipath Binding option and the MAG Identifier option. This document is a product of the Distributed Mobility Management 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 Jan 29 16:36:14 2018 Return-Path: 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 974B2131491 for ; Mon, 29 Jan 2018 16:36:14 -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 L8ZljiN2gdJo for ; Mon, 29 Jan 2018 16:36:13 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12F24131484 for ; Mon, 29 Jan 2018 16:36:13 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id AC743B80DE3; Mon, 29 Jan 2018 16:35:50 -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 6B2D3B80DE2; Mon, 29 Jan 2018 16:35:49 -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: <20180130003549.6B2D3B80DE2@rfc-editor.org> Date: Mon, 29 Jan 2018 16:35:49 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8321_on_Alternate-Marking_Method_for_Pas?= =?utf-8?q?sive_and_Hybrid_Performance_Monitoring?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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" A new Request for Comments is now available in online RFC libraries. RFC 8321 Title: Alternate-Marking Method for Passive and Hybrid Performance Monitoring Author: G. Fioccola, Ed., A. Capello, M. Cociglio, L. Castaldelli, M. Chen, L. Zheng, G. Mirsky, T. Mizrahi Status: Experimental Stream: IETF Date: January 2018 Mailbox: giuseppe.fioccola@telecomitalia.it, alessandro.capello@telecomitalia.it, mauro.cociglio@telecomitalia.it, luca.castaldelli@telecomitalia.it, mach.chen@huawei.com, vero.zheng@huawei.com, gregimirsky@gmail.com, talmi@marvell.com Pages: 33 Characters: 84513 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ippm-alt-mark-14.txt URL: https://www.rfc-editor.org/info/rfc8321 DOI: 10.17487/RFC8321 This document describes a method to perform packet loss, delay, and jitter measurements on live traffic. This method is based on an Alternate-Marking (coloring) technique. A report is provided in order to explain an example and show the method applicability. This technology can be applied in various situations, as detailed in this document, and could be considered Passive or Hybrid depending on the application. 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 Wed Jan 31 10:26:02 2018 Return-Path: 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 58B29124207 for ; Wed, 31 Jan 2018 10:26:02 -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 9gtg3CYJhqtT for ; Wed, 31 Jan 2018 10:26:00 -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 5A26F12EBFB for ; Wed, 31 Jan 2018 10:25:57 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id B53D2B80E17; Wed, 31 Jan 2018 10:25:32 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 8F54DB80E16; Wed, 31 Jan 2018 10:25:31 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180131182531.8F54DB80E16@rfc-editor.org> Date: Wed, 31 Jan 2018 10:25:31 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8295_on_EST_=28Enrollment_over_Secure_Tr?= =?utf-8?q?ansport=29_Extensions?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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" A new Request for Comments is now available in online RFC libraries. RFC 8295 Title: EST (Enrollment over Secure Transport) Extensions Author: S. Turner Status: Standards Track Stream: IETF Date: January 2018 Mailbox: sean@sn3rd.com Pages: 54 Characters: 115713 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-turner-est-extensions-11.txt URL: https://www.rfc-editor.org/info/rfc8295 DOI: 10.17487/RFC8295 The EST (Enrollment over Secure Transport) protocol defines the Well-Known URI (Uniform Resource Identifier) -- /.well-known/est -- along with a number of other path components that clients use for PKI (Public Key Infrastructure) services, namely certificate enrollment (e.g., /simpleenroll). This document defines a number of other PKI services as additional path components -- specifically, firmware and trust anchors as well as symmetric, asymmetric, and encrypted keys. This document also specifies the PAL (Package Availability List), which is an XML (Extensible Markup Language) file or JSON (JavaScript Object Notation) object that clients use to retrieve packages available and authorized for them. This document extends the EST server path components to provide these additional services. 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 Jan 31 10:26:32 2018 Return-Path: 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 DCF6B12F2AA for ; Wed, 31 Jan 2018 10:26:31 -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 72KUgZnu2ZfI for ; Wed, 31 Jan 2018 10:26:30 -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 2903E12EC9F for ; Wed, 31 Jan 2018 10:26:17 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 348DEB80E25; Wed, 31 Jan 2018 10:25:49 -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 2A3FAB80E24; Wed, 31 Jan 2018 10:25:48 -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: <20180131182548.2A3FAB80E24@rfc-editor.org> Date: Wed, 31 Jan 2018 10:25:48 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8314_on_Cleartext_Considered_Obsolete=3A?= =?utf-8?q?_Use_of_Transport_Layer_Security_=28TLS=29_for_Email_Submission?= =?utf-8?q?_and_Access?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: uta@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: rfc-dist-bounces@rfc-editor.org Sender: "rfc-dist" A new Request for Comments is now available in online RFC libraries. RFC 8314 Title: Cleartext Considered Obsolete: Use of Transport Layer Security (TLS) for Email Submission and Access Author: K. Moore, C. Newman Status: Standards Track Stream: IETF Date: January 2018 Mailbox: moore@network-heretics.com, chris.newman@oracle.com Pages: 26 Characters: 62605 Updates: RFC 1939, RFC 2595, RFC 3501, RFC 5068, RFC 6186, RFC 6409 I-D Tag: draft-ietf-uta-email-deep-12.txt URL: https://www.rfc-editor.org/info/rfc8314 DOI: 10.17487/RFC8314 This specification outlines current recommendations for the use of Transport Layer Security (TLS) to provide confidentiality of email traffic between a Mail User Agent (MUA) and a Mail Submission Server or Mail Access Server. This document updates RFCs 1939, 2595, 3501, 5068, 6186, and 6409. This document is a product of the Using TLS in Applications 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 Jan 31 16:45:01 2018 Return-Path: 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 9FEC012EB87 for ; Wed, 31 Jan 2018 16:45:01 -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 EqE2kUJTynvG for ; Wed, 31 Jan 2018 16:44:55 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 571FE12E899 for ; Wed, 31 Jan 2018 16:44:55 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 60D24B8171C; Wed, 31 Jan 2018 16:44:30 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id CE7EFB8171B; Wed, 31 Jan 2018 16:44:29 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180201004429.CE7EFB8171B@rfc-editor.org> Date: Wed, 31 Jan 2018 16:44:29 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8317_on_Ethernet-Tree_=28E-Tree=29_Suppo?= =?utf-8?q?rt_in_Ethernet_VPN_=28EVPN=29_and_Provider_Backbone_Bridging_EV?= =?utf-8?q?PN_=28PBB-EVPN=29?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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" A new Request for Comments is now available in online RFC libraries. RFC 8317 Title: Ethernet-Tree (E-Tree) Support in Ethernet VPN (EVPN) and Provider Backbone Bridging EVPN (PBB-EVPN) Author: A. Sajassi, Ed., S. Salam, J. Drake, J. Uttaro, S. Boutros, J. Rabadan Status: Standards Track Stream: IETF Date: January 2018 Mailbox: sajassi@cisco.com, ssalam@cisco.com, jdrake@juniper.net, ju1738@att.com, sboutros@vmware.com, jorge.rabadan@nokia.com Pages: 23 Characters: 53519 Updates: RFC 7385 I-D Tag: draft-ietf-bess-evpn-etree-14.txt URL: https://www.rfc-editor.org/info/rfc8317 DOI: 10.17487/RFC8317 The MEF Forum (MEF) has defined a rooted-multipoint Ethernet service known as Ethernet-Tree (E-Tree). A solution framework for supporting this service in MPLS networks is described in RFC 7387, "A Framework for Ethernet-Tree (E-Tree) Service over a Multiprotocol Label Switching (MPLS) Network". This document discusses how those functional requirements can be met with a solution based on RFC 7432, "BGP MPLS Based Ethernet VPN (EVPN)", with some extensions and a description of how such a solution can offer a more efficient implementation of these functions than that of RFC 7796, "Ethernet-Tree (E-Tree) Support in Virtual Private LAN Service (VPLS)". This document makes use of the most significant bit of the Tunnel Type field (in the P-Multicast Service Interface (PMSI) Tunnel attribute) governed by the IANA registry created by RFC 7385; hence, it updates RFC 7385 accordingly. This document is a product of the BGP Enabled Services Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Wed Jan 31 16:55:55 2018 Return-Path: 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 3400712EB57 for ; Wed, 31 Jan 2018 16:55:55 -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=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 z1cACqmPU4os for ; Wed, 31 Jan 2018 16:55:53 -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 76A8E131456 for ; Wed, 31 Jan 2018 16:55:24 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 89F45B817F8; Wed, 31 Jan 2018 16:54:59 -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 474E0B817F8; Wed, 31 Jan 2018 16:54:58 -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: <20180201005458.474E0B817F8@rfc-editor.org> Date: Wed, 31 Jan 2018 16:54:58 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?BCP_10=2C_RFC_8318_on_IAB=2C_IESG=2C_and_IAO?= =?utf-8?q?C_Selection=2C_Confirmation=2C_and_Recall_Process=3A_IAOC_Advis?= =?utf-8?q?or_for_the_Nominating_Committee?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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" A new Request for Comments is now available in online RFC libraries. BCP 10 RFC 8318 Title: IAB, IESG, and IAOC Selection, Confirmation, and Recall Process: IAOC Advisor for the Nominating Committee Author: S. Dawkins Status: Best Current Practice Stream: IETF Date: January 2018 Mailbox: spencerdawkins.ietf@gmail.com Pages: 9 Characters: 16920 Updates: RFC 7437 See Also: BCP 10 I-D Tag: draft-dawkins-iesg-nomcom-advisor-iaoc-03.txt URL: https://www.rfc-editor.org/info/rfc8318 DOI: 10.17487/RFC8318 This specification formalizes an ad hoc practice used to provide advice to the IETF Nominating Committee (NomCom) about the operations of the IETF Administrative Oversight Committee (IAOC). This document updates RFC 7437. 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