From rfc-dist-bounces@rfc-editor.org Mon Dec 4 12:40:28 2017 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 2F3AC128BB6 for ; Mon, 4 Dec 2017 12:40:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AFJnZM9NDa0B for ; Mon, 4 Dec 2017 12:40: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 CF5AD128B93 for ; Mon, 4 Dec 2017 12:40:25 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 59CE5B80E32; Mon, 4 Dec 2017 12:40:08 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 2A246B80E30; Mon, 4 Dec 2017 12:40:07 -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: <20171204204007.2A246B80E30@rfc-editor.org> Date: Mon, 4 Dec 2017 12:40:07 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8275_on_Allowing_Inheritable_NFSv4_Acces?= =?utf-8?q?s_Control_Entries_to_Override_the_Umask?= 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, nfsv4@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 8275 Title: Allowing Inheritable NFSv4 Access Control Entries to Override the Umask Author: J. Fields, A. Gruenbacher Status: Standards Track Stream: IETF Date: December 2017 Mailbox: bfields@redhat.com, agruenba@redhat.com Pages: 7 Characters: 13271 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-nfsv4-umask-05.txt URL: https://www.rfc-editor.org/info/rfc8275 DOI: 10.17487/RFC8275 In many environments, inheritable NFSv4 Access Control Entries (ACEs) can be rendered ineffective by the application of the per-process file mode creation mask (umask). This can be addressed by transmitting the umask and create mode as separate pieces of data, allowing the server to make more intelligent decisions about the permissions to set on new files. This document proposes a protocol extension to accomplish that. This document is a product of the Network File System Version 4 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 Dec 4 12:41:02 2017 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 C1E12128D6F for ; Mon, 4 Dec 2017 12:41:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3zSQQMVRHuJD for ; Mon, 4 Dec 2017 12:41:01 -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 E18D0128CF0 for ; Mon, 4 Dec 2017 12:40:44 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id C984CB80E3D; Mon, 4 Dec 2017 12:40:14 -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 3F1DDB80E3B; Mon, 4 Dec 2017 12:40:14 -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: <20171204204014.3F1DDB80E3B@rfc-editor.org> Date: Mon, 4 Dec 2017 12:40:14 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8276_on_File_System_Extended_Attributes_?= =?utf-8?q?in_NFSv4?= 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, nfsv4@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 8276 Title: File System Extended Attributes in NFSv4 Author: M. Naik, M. Eshel Status: Standards Track Stream: IETF Date: December 2017 Mailbox: manoj.naik@nutanix.com, eshel@us.ibm.com Pages: 28 Characters: 59644 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-nfsv4-xattrs-06.txt URL: https://www.rfc-editor.org/info/rfc8276 DOI: 10.17487/RFC8276 This document describes an optional feature extending the NFSv4 protocol. This feature allows extended attributes (hereinafter also referred to as xattrs) to be interrogated and manipulated using NFSv4 clients. Xattrs are provided by a file system to associate opaque metadata, not interpreted by the file system, with files and directories. Such support is present in many modern local file systems. New file attributes are provided to allow clients to query the server for xattr support, with that support consisting of new operations to get and set xattrs on file system objects. This document is a product of the Network File System Version 4 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 Dec 4 15:30:21 2017 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 A2D341292AE for ; Mon, 4 Dec 2017 15:30:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ts5C8DzWTc1I for ; Mon, 4 Dec 2017 15:30:19 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BAC77128D69 for ; Mon, 4 Dec 2017 15:30:19 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 2465BB80D94; Mon, 4 Dec 2017 15:30:02 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 2548CB80D91; Mon, 4 Dec 2017 15:30:01 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20171204233001.2548CB80D91@rfc-editor.org> Date: Mon, 4 Dec 2017 15:30:01 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8273_on_Unique_IPv6_Prefix_per_Host?= 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, v6ops@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 8273 Title: Unique IPv6 Prefix per Host Author: J. Brzozowski, G. Van de Velde Status: Informational Stream: IETF Date: December 2017 Mailbox: john_brzozowski@cable.comcast.com, gunter.van_de_velde@nokia.com Pages: 10 Characters: 22867 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-v6ops-unique-ipv6-prefix-per-host-13.txt URL: https://www.rfc-editor.org/info/rfc8273 DOI: 10.17487/RFC8273 This document outlines an approach utilizing existing IPv6 protocols to allow hosts to be assigned a unique IPv6 prefix (instead of a unique IPv6 address from a shared IPv6 prefix). Benefits of using a unique IPv6 prefix over a unique service-provider IPv6 address include improved host isolation and enhanced subscriber management on shared network segments. This document is a product of the IPv6 Operations 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 Dec 5 16:28:22 2017 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 0172D128B93 for ; Tue, 5 Dec 2017 16:28:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 81F75prwh81W for ; Tue, 5 Dec 2017 16:28:20 -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 83237128B8F for ; Tue, 5 Dec 2017 16:28:20 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D84F9B81EAF; Tue, 5 Dec 2017 16:28: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 BD3C2B81EAE; Tue, 5 Dec 2017 16:28: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: <20171206002800.BD3C2B81EAE@rfc-editor.org> Date: Tue, 5 Dec 2017 16:28:00 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8270_on_Increase_the_Secure_Shell_Minimu?= =?utf-8?q?m_Recommended_Diffie-Hellman_Modulus_Size_to_2048_Bits?= 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, 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" A new Request for Comments is now available in online RFC libraries. RFC 8270 Title: Increase the Secure Shell Minimum Recommended Diffie-Hellman Modulus Size to 2048 Bits Author: L. Velvindron, M. Baushke Status: Standards Track Stream: IETF Date: December 2017 Mailbox: logan@hackers.mu, mdb@juniper.net Pages: 5 Characters: 9440 Updates: RFC 4419 I-D Tag: draft-ietf-curdle-ssh-dh-group-exchange-06.txt URL: https://www.rfc-editor.org/info/rfc8270 DOI: 10.17487/RFC8270 The Diffie-Hellman (DH) Group Exchange for the Secure Shell (SSH) transport-layer protocol specifies that servers and clients should support groups with a minimum modulus group size of 1024 bits. Recent security research has shown that the minimum value of 1024 bits is insufficient to protect against state-sponsored actors and any organization with enough computing resources. This RFC updates RFC 4419, which allowed for DH moduli less than 2048 bits; now, 2048 bits is the minimum acceptable group size. 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 Wed Dec 13 11:16:38 2017 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 F18291275F4 for ; Wed, 13 Dec 2017 11:16:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BKf9eRwsSnu7 for ; Wed, 13 Dec 2017 11:16:36 -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 8008E12778D for ; Wed, 13 Dec 2017 11:16:36 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id C28C4B813D4; Wed, 13 Dec 2017 11:16:09 -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 299BCB813D2; Wed, 13 Dec 2017 11:16: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: <20171213191609.299BCB813D2@rfc-editor.org> Date: Wed, 13 Dec 2017 11:16:09 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8259_on_The_JavaScript_Object_Notation_?= =?utf-8?q?=28JSON=29_Data_Interchange_Format?= 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, json@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 8259 Title: The JavaScript Object Notation (JSON) Data Interchange Format Author: T. Bray, Ed. Status: Standards Track Stream: IETF Date: December 2017 Mailbox: tbray@textuality.com Pages: 16 Characters: 28360 Obsoletes: RFC 7159 I-D Tag: draft-ietf-jsonbis-rfc7159bis-04.txt URL: https://www.rfc-editor.org/info/rfc8259 DOI: 10.17487/RFC8259 JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data. This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance. This document is a product of the Javascript Object Notation Update 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 Wed Dec 13 11:48:30 2017 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 73506126D45 for ; Wed, 13 Dec 2017 11:48:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mbeizt672rtP for ; Wed, 13 Dec 2017 11:48:29 -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 12701126E7A for ; Wed, 13 Dec 2017 11:48:29 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 6F5C1B80E2C; Wed, 13 Dec 2017 11:48:02 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id A5389B80E26; Wed, 13 Dec 2017 11:48:01 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20171213194801.A5389B80E26@rfc-editor.org> Date: Wed, 13 Dec 2017 11:48:01 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?Corrected_Announcement=3A_STD_90=2C_RFC_8259?= =?utf-8?q?_on_The_JavaScript_Object_Notation_=28JSON=29_Data_Interchange_?= =?utf-8?q?Format?= 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, json@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. STD 90 RFC 8259 Title: The JavaScript Object Notation (JSON) Data Interchange Format Author: T. Bray, Ed. Status: Standards Track Stream: IETF Date: December 2017 Mailbox: tbray@textuality.com Pages: 16 Characters: 28360 Obsoletes: RFC 7159 See Also: STD 90 I-D Tag: draft-ietf-jsonbis-rfc7159bis-04.txt URL: https://www.rfc-editor.org/info/rfc8259 DOI: 10.17487/RFC8259 JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data. This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance. This document is a product of the Javascript Object Notation Update 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 Wed Dec 13 12:08:57 2017 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 EBDED1275F4 for ; Wed, 13 Dec 2017 12:08:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cbty94laVRWI for ; Wed, 13 Dec 2017 12:08:56 -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 5688A126D45 for ; Wed, 13 Dec 2017 12:08:56 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id A3B9BB8164E; Wed, 13 Dec 2017 12:08:29 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 4923BB81649; Wed, 13 Dec 2017 12:08: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: <20171213200828.4923BB81649@rfc-editor.org> Date: Wed, 13 Dec 2017 12:08:28 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8268_on_More_Modular_Exponentiation_=28M?= =?utf-8?q?ODP=29_Diffie-Hellman_=28DH=29_Key_Exchange_=28KEX=29_Groups_fo?= =?utf-8?q?r_Secure_Shell_=28SSH=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, 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" A new Request for Comments is now available in online RFC libraries. RFC 8268 Title: More Modular Exponentiation (MODP) Diffie-Hellman (DH) Key Exchange (KEX) Groups for Secure Shell (SSH) Author: M. Baushke Status: Standards Track Stream: IETF Date: December 2017 Mailbox: mdb@juniper.net Pages: 8 Characters: 16318 Updates: RFC 4250, RFC 4253 I-D Tag: draft-ietf-curdle-ssh-modp-dh-sha2-09.txt URL: https://www.rfc-editor.org/info/rfc8268 DOI: 10.17487/RFC8268 This document defines added Modular Exponentiation (MODP) groups for the Secure Shell (SSH) protocol using SHA-2 hashes. This document updates RFC 4250. This document updates RFC 4253 by correcting an error regarding checking the Peer's DH Public Key. 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 Thu Dec 14 13:31:42 2017 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 1CA52128D3E for ; Thu, 14 Dec 2017 13:31:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XRJC6B8T9eqD for ; Thu, 14 Dec 2017 13:31:40 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3823B127444 for ; Thu, 14 Dec 2017 13:31:40 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5B71EB80C36; Thu, 14 Dec 2017 13:31:12 -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 505A6B80C33; Thu, 14 Dec 2017 13:31: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: <20171214213110.505A6B80C33@rfc-editor.org> Date: Thu, 14 Dec 2017 13:31:10 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8294_on_Common_YANG_Data_Types_for_the_R?= =?utf-8?q?outing_Area?= 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, 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" A new Request for Comments is now available in online RFC libraries. RFC 8294 Title: Common YANG Data Types for the Routing Area Author: X. Liu, Y. Qu, A. Lindem, C. Hopps, L. Berger Status: Standards Track Stream: IETF Date: December 2017 Mailbox: xufeng_liu@jabil.com, yingzhen.qu@huawei.com, acee@cisco.com, chopps@chopps.org, lberger@labn.net Pages: 43 Characters: 66851 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rtgwg-routing-types-17.txt URL: https://www.rfc-editor.org/info/rfc8294 DOI: 10.17487/RFC8294 This document defines a collection of common data types using the YANG data modeling language. These derived common types are designed to be imported by other modules defined in the routing area. 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 Tue Dec 19 20:52:58 2017 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 E7E76120726 for ; Tue, 19 Dec 2017 20:52:58 -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 uCiR7ZWmKmfH for ; Tue, 19 Dec 2017 20:52:57 -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 AD43112778D for ; Tue, 19 Dec 2017 20:52:57 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 6480EB81D1A; Tue, 19 Dec 2017 20:52: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 CA8E5B81D19; Tue, 19 Dec 2017 20:52: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: <20171220045254.CA8E5B81D19@rfc-editor.org> Date: Tue, 19 Dec 2017 20:52:54 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8297_on_An_HTTP_Status_Code_for_Indicati?= =?utf-8?q?ng_Hints?= 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, 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" A new Request for Comments is now available in online RFC libraries. RFC 8297 Title: An HTTP Status Code for Indicating Hints Author: K. Oku Status: Experimental Stream: IETF Date: December 2017 Mailbox: kazuhooku@gmail.com Pages: 7 Characters: 13303 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-httpbis-early-hints-05.txt URL: https://www.rfc-editor.org/info/rfc8297 DOI: 10.17487/RFC8297 This memo introduces an informational HTTP status code that can be used to convey hints that help a client make preparations for processing the final response. This document is a product of the Hypertext Transfer Protocol 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 Dec 20 14:08:45 2017 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 212C41205D3 for ; Wed, 20 Dec 2017 14:08:45 -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 NHs-f3b3PY10 for ; Wed, 20 Dec 2017 14:08: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 B96F31201F2 for ; Wed, 20 Dec 2017 14:08:43 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id BFB8FB81433; Wed, 20 Dec 2017 14:08: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 4CA65B81433; Wed, 20 Dec 2017 14:08:39 -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: <20171220220839.4CA65B81433@rfc-editor.org> Date: Wed, 20 Dec 2017 14:08:39 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8158_on_IP_Flow_Information_Export_=28IP?= =?utf-8?q?FIX=29_Information_Elements_for_Logging_NAT_Events?= 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 8158 Title: IP Flow Information Export (IPFIX) Information Elements for Logging NAT Events Author: S. Sivakumar, R. Penno Status: Standards Track Stream: IETF Date: December 2017 Mailbox: ssenthil@cisco.com, repenno@cisco.com Pages: 34 Characters: 78399 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-behave-ipfix-nat-logging-13.txt URL: https://www.rfc-editor.org/info/rfc8158 DOI: 10.17487/RFC8158 Network operators require NAT devices to log events like creation and deletion of translations and information about the resources that the NAT device is managing. In many cases, the logs are essential to identify an attacker or a host that was used to launch malicious attacks and for various other purposes of accounting. Since there is no standard way of logging this information, different NAT devices use proprietary formats; hence, it is difficult to expect consistent behavior. This lack of standardization makes it difficult to write the Collector applications that would receive this data and process it to present useful information. This document describes the formats for logging NAT events. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Thu Dec 21 10:00:25 2017 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 BF14B12D947 for ; Thu, 21 Dec 2017 10:00:25 -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 e0DNEjNHhlgJ for ; Thu, 21 Dec 2017 10:00:24 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3117B12D778 for ; Thu, 21 Dec 2017 10:00:24 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 738C7B81269; Thu, 21 Dec 2017 10:00:20 -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 B3960B81269; Thu, 21 Dec 2017 10:00:18 -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: <20171221180018.B3960B81269@rfc-editor.org> Date: Thu, 21 Dec 2017 10:00:18 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8287_on_Label_Switched_Path_=28LSP=29_Pi?= =?utf-8?q?ng/Traceroute_for_Segment_Routing_=28SR=29_IGP-Prefix_and_IGP-A?= =?utf-8?q?djacency_Segment_Identifiers_=28SIDs=29_with_MPLS_Data_Planes?= 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, mpls@ietf.org, rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: rfc-dist-bounces@rfc-editor.org Sender: "rfc-dist" A new Request for Comments is now available in online RFC libraries. RFC 8287 Title: Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data Planes Author: N. Kumar, Ed., C. Pignataro, Ed., G. Swallow, N. Akiya, S. Kini, M. Chen Status: Standards Track Stream: IETF Date: December 2017 Mailbox: naikumar@cisco.com, cpignata@cisco.com, swallow.ietf@gmail.com, nobo.akiya.dev@gmail.com, sriganeshkini@gmail.com, mach.chen@huawei.com Pages: 25 Characters: 49976 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mpls-spring-lsp-ping-13.txt URL: https://www.rfc-editor.org/info/rfc8287 DOI: 10.17487/RFC8287 A Segment Routing (SR) architecture leverages source routing and tunneling paradigms and can be directly applied to the use of a Multiprotocol Label Switching (MPLS) data plane. A node steers a packet through a controlled set of instructions called "segments" by prepending the packet with an SR header. The segment assignment and forwarding semantic nature of SR raises additional considerations for connectivity verification and fault isolation for a Label Switched Path (LSP) within an SR architecture. This document illustrates the problem and defines extensions to perform LSP Ping and Traceroute for Segment Routing IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with an MPLS data plane. This document is a product of the Multiprotocol Label Switching Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Thu Dec 21 10:01:00 2017 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 0213112D961 for ; Thu, 21 Dec 2017 10:01:00 -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 o4RqA4nshyEn for ; Thu, 21 Dec 2017 10:00:58 -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 3CF9512D77A for ; Thu, 21 Dec 2017 10:00:44 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id EB044B81273; Thu, 21 Dec 2017 10:00:33 -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 D7E60B81271; Thu, 21 Dec 2017 10:00:32 -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: <20171221180032.D7E60B81271@rfc-editor.org> Date: Thu, 21 Dec 2017 10:00:32 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8298_on_Self-Clocked_Rate_Adaptation_for?= =?utf-8?q?_Multimedia?= 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, rmcat@ietf.org, rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: rfc-dist-bounces@rfc-editor.org Sender: "rfc-dist" A new Request for Comments is now available in online RFC libraries. RFC 8298 Title: Self-Clocked Rate Adaptation for Multimedia Author: I. Johansson, Z. Sarker Status: Experimental Stream: IETF Date: December 2017 Mailbox: ingemar.s.johansson@ericsson.com, Zaheduzzaman.Sarker@ericsson.com Pages: 36 Characters: 80538 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rmcat-scream-cc-13.txt URL: https://www.rfc-editor.org/info/rfc8298 DOI: 10.17487/RFC8298 This memo describes a rate adaptation algorithm for conversational media services such as interactive video. The solution conforms to the packet conservation principle and uses a hybrid loss-and-delay- based congestion control algorithm. The algorithm is evaluated over both simulated Internet bottleneck scenarios as well as in a Long Term Evolution (LTE) system simulator and is shown to achieve both low latency and high video throughput in these scenarios. This document is a product of the RTP Media Congestion Avoidance Techniques Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Thu Dec 21 10:01:32 2017 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 03C0212DA00 for ; Thu, 21 Dec 2017 10:01:32 -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 ZPB6Oneu2KGZ for ; Thu, 21 Dec 2017 10:01:24 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDDD012D963 for ; Thu, 21 Dec 2017 10:01:00 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5763FB81282; Thu, 21 Dec 2017 10:00: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 98044B8127F; Thu, 21 Dec 2017 10:00:46 -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: <20171221180046.98044B8127F@rfc-editor.org> Date: Thu, 21 Dec 2017 10:00:46 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8305_on_Happy_Eyeballs_Version_2=3A_Bett?= =?utf-8?q?er_Connectivity_Using_Concurrency?= 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, v6ops@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 8305 Title: Happy Eyeballs Version 2: Better Connectivity Using Concurrency Author: D. Schinazi, T. Pauly Status: Standards Track Stream: IETF Date: December 2017 Mailbox: dschinazi@apple.com, tpauly@apple.com Pages: 15 Characters: 32917 Obsoletes: RFC 6555 I-D Tag: draft-ietf-v6ops-rfc6555bis-07.txt URL: https://www.rfc-editor.org/info/rfc8305 DOI: 10.17487/RFC8305 Many communication protocols operating over the modern Internet use hostnames. These often resolve to multiple IP addresses, each of which may have different performance and connectivity characteristics. Since specific addresses or address families (IPv4 or IPv6) may be blocked, broken, or sub-optimal on a network, clients that attempt multiple connections in parallel have a chance of establishing a connection more quickly. This document specifies requirements for algorithms that reduce this user-visible delay and provides an example algorithm, referred to as "Happy Eyeballs". This document obsoletes the original algorithm description in RFC 6555. This document is a product of the IPv6 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 Thu Dec 21 15:49:04 2017 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 2888A12D7FC for ; Thu, 21 Dec 2017 15:49:04 -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 XKIbouwHrsJI for ; Thu, 21 Dec 2017 15:49: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 92C48126E01 for ; Thu, 21 Dec 2017 15:49:02 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 8A1F0B81AEE; Thu, 21 Dec 2017 15:48:58 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id EC7D7B81AEC; Thu, 21 Dec 2017 15:48:56 -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: <20171221234856.EC7D7B81AEC@rfc-editor.org> Date: Thu, 21 Dec 2017 15:48:56 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8281_on_Path_Computation_Element_Communi?= =?utf-8?q?cation_Protocol_=28PCEP=29_Extensions_for_PCE-Initiated_LSP_Set?= =?utf-8?q?up_in_a_Stateful_PCE_Model?= 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, 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" A new Request for Comments is now available in online RFC libraries. RFC 8281 Title: Path Computation Element Communication Protocol (PCEP) Extensions for PCE-Initiated LSP Setup in a Stateful PCE Model Author: E. Crabbe, I. Minei, S. Sivabalan, R. Varga Status: Standards Track Stream: IETF Date: December 2017 Mailbox: edward.crabbe@gmail.com, inaminei@google.com, msiva@cisco.com, robert.varga@pantheon.tech Pages: 20 Characters: 41108 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pce-pce-initiated-lsp-11.txt URL: https://www.rfc-editor.org/info/rfc8281 DOI: 10.17487/RFC8281 The Path Computation Element Communication Protocol (PCEP) provides mechanisms for Path Computation Elements (PCEs) to perform path computations in response to Path Computation Client (PCC) requests. The extensions for stateful PCE provide active control of Multiprotocol Label Switching (MPLS) Traffic Engineering Label Switched Paths (TE LSPs) via PCEP, for a model where the PCC delegates control over one or more locally configured LSPs to the PCE. This document describes the creation and deletion of PCE-initiated LSPs under the stateful PCE model. 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 Thu Dec 21 15:49:41 2017 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 5DC9312D7F7 for ; Thu, 21 Dec 2017 15:49:41 -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 gIiNgnqOfkop for ; Thu, 21 Dec 2017 15:49:37 -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 4CAAD12DA0D for ; Thu, 21 Dec 2017 15:49:20 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 0779EB81AF9; Thu, 21 Dec 2017 15:49:12 -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 659E2B81AF8; Thu, 21 Dec 2017 15:49:11 -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: <20171221234911.659E2B81AF8@rfc-editor.org> Date: Thu, 21 Dec 2017 15:49:11 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8282_on_Extensions_to_the_Path_Computati?= =?utf-8?q?on_Element_Communication_Protocol_=28PCEP=29_for_Inter-Layer_MP?= =?utf-8?q?LS_and_GMPLS_Traffic_Engineering?= 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, 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" A new Request for Comments is now available in online RFC libraries. RFC 8282 Title: Extensions to the Path Computation Element Communication Protocol (PCEP) for Inter-Layer MPLS and GMPLS Traffic Engineering Author: E. Oki, T. Takeda, A. Farrel, F. Zhang Status: Standards Track Stream: IETF Date: December 2017 Mailbox: oki@i.kyoto-u.ac.jp, tomonori.takeda@ntt.com, afarrel@juniper.net, zhangfatai@huawei.com Pages: 22 Characters: 47899 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-pce-inter-layer-ext-12.txt URL: https://www.rfc-editor.org/info/rfc8282 DOI: 10.17487/RFC8282 The Path Computation Element (PCE) provides path computation functions in support of traffic engineering in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. MPLS and GMPLS networks may be constructed from layered service networks. It is advantageous for overall network efficiency to provide end-to-end traffic engineering across multiple network layers through a process called inter-layer traffic engineering. PCE is a candidate solution for such requirements. The PCE Communication Protocol (PCEP) is designed as a communication protocol between Path Computation Clients (PCCs) and PCEs. This document presents PCEP extensions for inter-layer traffic engineering. 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 Thu Dec 21 15:50:10 2017 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 0C70B12DA2C for ; Thu, 21 Dec 2017 15:50:10 -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 2YNieKP-mKEQ for ; Thu, 21 Dec 2017 15:50:08 -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 B816D12DA11 for ; Thu, 21 Dec 2017 15:49:34 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 64BE3B81B05; Thu, 21 Dec 2017 15:49: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 1B621B81B04; Thu, 21 Dec 2017 15:49:25 -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: <20171221234925.1B621B81B04@rfc-editor.org> Date: Thu, 21 Dec 2017 15:49:25 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8283_on_An_Architecture_for_Use_of_PCE_a?= =?utf-8?q?nd_the_PCE_Communication_Protocol_=28PCEP=29_in_a_Network_with_?= =?utf-8?q?Central_Control?= 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, 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" A new Request for Comments is now available in online RFC libraries. RFC 8283 Title: An Architecture for Use of PCE and the PCE Communication Protocol (PCEP) in a Network with Central Control Author: A. Farrel, Ed., Q. Zhao, Ed., Z. Li, C. Zhou Status: Informational Stream: IETF Date: December 2017 Mailbox: afarrel@juniper.net, quintin.zhao@huawei.com, lizhenbin@huawei.com, chao.zhou@cisco.com Pages: 25 Characters: 56368 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-teas-pce-central-control-05.txt URL: https://www.rfc-editor.org/info/rfc8283 DOI: 10.17487/RFC8283 The Path Computation Element (PCE) is a core component of Software- Defined Networking (SDN) systems. It can compute optimal paths for traffic across a network and can also update the paths to reflect changes in the network or traffic demands. PCE was developed to derive paths for MPLS Label Switched Paths (LSPs), which are supplied to the head end of the LSP using the Path Computation Element Communication Protocol (PCEP). SDN has a broader applicability than signaled MPLS traffic-engineered (TE) networks, and the PCE may be used to determine paths in a range of use cases including static LSPs, segment routing, Service Function Chaining (SFC), and most forms of a routed or switched network. It is, therefore, reasonable to consider PCEP as a control protocol for use in these environments to allow the PCE to be fully enabled as a central controller. This document briefly introduces the architecture for PCE as a central controller, examines the motivations and applicability for PCEP as a control protocol in this environment, and introduces the implications for the protocol. A PCE-based central controller can simplify the processing of a distributed control plane by blending it with elements of SDN and without necessarily completely replacing it. This document does not describe use cases in detail and does not define protocol extensions: that work is left for other documents. This document is a product of the Traffic Engineering Architecture and Signaling 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