From rfc-dist-bounces@rfc-editor.org Wed May 2 14:44:57 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 E94F712DA70 for ; Wed, 2 May 2018 14:44:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.201 X-Spam-Level: X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8P5ewJUOTFD8 for ; Wed, 2 May 2018 14:44:56 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C37112708C for ; Wed, 2 May 2018 14:44:56 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id CEDBFB81562; Wed, 2 May 2018 14:44:50 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id C128EB8155D; Wed, 2 May 2018 14:44:49 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180502214449.C128EB8155D@rfc-editor.org> Date: Wed, 2 May 2018 14:44:49 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8372_on_MPLS_Flow_Identification_Conside?= =?utf-8?q?rations?= 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 8372 Title: MPLS Flow Identification Considerations Author: S. Bryant, C. Pignataro, M. Chen, Z. Li, G. Mirsky Status: Informational Stream: IETF Date: May 2018 Mailbox: stewart.bryant@gmail.com, cpignata@cisco.com, mach.chen@huawei.com, lizhenbin@huawei.com, gregimirsky@gmail.com Pages: 11 Characters: 26645 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mpls-flow-ident-07.txt URL: https://www.rfc-editor.org/info/rfc8372 DOI: 10.17487/RFC8372 This document discusses aspects to consider when developing a solution for MPLS flow identification. The key application that needs this solution is in-band performance monitoring of MPLS flows when MPLS is used to encapsulate user data packets. This document is a product of the Multiprotocol Label Switching Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Wed May 2 14:45: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 33F1712E037 for ; Wed, 2 May 2018 14:45:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.201 X-Spam-Level: X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bpow2lqo2Ual for ; Wed, 2 May 2018 14:45:28 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 889EC12EAB9 for ; Wed, 2 May 2018 14:45:13 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 40C8DB815E2; Wed, 2 May 2018 14:44:54 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 4A223B8159B; Wed, 2 May 2018 14:44:52 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180502214452.4A223B8159B@rfc-editor.org> Date: Wed, 2 May 2018 14:44:52 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8378_on_Signal-Free_Locator/ID_Separatio?= =?utf-8?q?n_Protocol_=28LISP=29_Multicast?= 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 8378 Title: Signal-Free Locator/ID Separation Protocol (LISP) Multicast Author: V. Moreno, D. Farinacci Status: Experimental Stream: IETF Date: May 2018 Mailbox: vimoreno@cisco.com, farinacci@gmail.com Pages: 21 Characters: 47165 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-lisp-signal-free-multicast-09.txt URL: https://www.rfc-editor.org/info/rfc8378 DOI: 10.17487/RFC8378 When multicast sources and receivers are active at Locator/ID Separation Protocol (LISP) sites, the core network is required to use native multicast so packets can be delivered from sources to group members. When multicast is not available to connect the multicast sites together, a signal-free mechanism can be used to allow traffic to flow between sites. The mechanism described in this document uses unicast replication and encapsulation over the core network for the data plane and uses the LISP mapping database system so encapsulators at the source LISP multicast site can find decapsulators at the receiver LISP multicast sites. This document is a product of the Locator/ID Separation 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 Tue May 8 15:58: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 1CADC12D7EC for ; Tue, 8 May 2018 15:58:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mf3aYshYl-af for ; Tue, 8 May 2018 15:58:31 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67A9A124234 for ; Tue, 8 May 2018 15:58:31 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 6F167B81C37; Tue, 8 May 2018 15:58:18 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 9203DB81C2E; Tue, 8 May 2018 15:58:16 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180508225816.9203DB81C2E@rfc-editor.org> Date: Tue, 8 May 2018 15:58:16 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8392_on_CBOR_Web_Token_=28CWT=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, ace@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 8392 Title: CBOR Web Token (CWT) Author: M. Jones, E. Wahlstroem, S. Erdtman, H. Tschofenig Status: Standards Track Stream: IETF Date: May 2018 Mailbox: mbj@microsoft.com, erik@wahlstromstekniska.se, erdtman@spotify.com, Hannes.Tschofenig@arm.com Pages: 25 Characters: 46316 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ace-cbor-web-token-15.txt URL: https://www.rfc-editor.org/info/rfc8392 DOI: 10.17487/RFC8392 CBOR Web Token (CWT) is a compact means of representing claims to be transferred between two parties. The claims in a CWT are encoded in the Concise Binary Object Representation (CBOR), and CBOR Object Signing and Encryption (COSE) is used for added application-layer security protection. A claim is a piece of information asserted about a subject and is represented as a name/value pair consisting of a claim name and a claim value. CWT is derived from JSON Web Token (JWT) but uses CBOR rather than JSON. This document is a product of the Authentication and Authorization for Constrained Environments 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 May 8 15:59:21 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 A310A12EB9C for ; Tue, 8 May 2018 15:59:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZRRvT3C21Qt4 for ; Tue, 8 May 2018 15:59:13 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC55412EB7D for ; Tue, 8 May 2018 15:58:50 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id E9B6CB81C5D; Tue, 8 May 2018 15:58:23 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id C7ADCB81C54; Tue, 8 May 2018 15:58:22 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180508225822.C7ADCB81C54@rfc-editor.org> Date: Tue, 8 May 2018 15:58:22 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8393_on_Operating_the_Network_Service_He?= =?utf-8?q?ader_=28NSH=29_with_Next_Protocol_=22None=22?= 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 8393 Title: Operating the Network Service Header (NSH) with Next Protocol "None" Author: A. Farrel, J. Drake Status: Standards Track Stream: IETF Date: May 2018 Mailbox: afarrel@juniper.net, jdrake@juniper.net Pages: 12 Characters: 27141 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-farrel-sfc-convent-06.txt URL: https://www.rfc-editor.org/info/rfc8393 DOI: 10.17487/RFC8393 This document describes a network that supports Service Function Chaining (SFC) using the Network Service Header (NSH) with no payload data and carrying only metadata. This is achieved by defining a new NSH "Next Protocol" type value of "None". This document illustrates some of the functions that may be achieved or enhanced by this mechanism, but it does not provide an exhaustive list of use cases, nor is it intended to be definitive about the functions it describes. It is expected that other documents will describe specific use cases in more detail and will define the protocol mechanics for each use case. 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 Wed May 9 17:19:46 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 0CCBB12D7EF for ; Wed, 9 May 2018 17:19:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.201 X-Spam-Level: X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mxyqwrychwUq for ; Wed, 9 May 2018 17:19:44 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B17FC1200A0 for ; Wed, 9 May 2018 17:19:44 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 4A3E2B80DF2; Wed, 9 May 2018 17:19:43 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id EF1AAB80DF1; Wed, 9 May 2018 17:19:41 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180510001941.EF1AAB80DF1@rfc-editor.org> Date: Wed, 9 May 2018 17:19:41 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8366_on_A_Voucher_Artifact_for_Bootstrap?= =?utf-8?q?ping_Protocols?= 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, anima@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 8366 Title: A Voucher Artifact for Bootstrapping Protocols Author: K. Watsen, M. Richardson, M. Pritikin, T. Eckert Status: Standards Track Stream: IETF Date: May 2018 Mailbox: kwatsen@juniper.net, mcr+ietf@sandelman.ca, pritikin@cisco.com, tte+ietf@cs.fau.de Pages: 23 Characters: 47891 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-anima-voucher-07.txt URL: https://www.rfc-editor.org/info/rfc8366 DOI: 10.17487/RFC8366 This document defines a strategy to securely assign a pledge to an owner using an artifact signed, directly or indirectly, by the pledge's manufacturer. This artifact is known as a "voucher". This document defines an artifact format as a YANG-defined JSON document that has been signed using a Cryptographic Message Syntax (CMS) structure. Other YANG-derived formats are possible. The voucher artifact is normally generated by the pledge's manufacturer (i.e., the Manufacturer Authorized Signing Authority (MASA)). This document only defines the voucher artifact, leaving it to other documents to describe specialized protocols for accessing it. This document is a product of the Autonomic Networking Integrated Model and Approach 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 May 9 23:08:09 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 6EA8D12EA58 for ; Wed, 9 May 2018 23:08:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D6WvGVYjoipu for ; Wed, 9 May 2018 23:08:08 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94757127078 for ; Wed, 9 May 2018 23:08:08 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id EAFDCB8469E; Wed, 9 May 2018 23:08:06 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 16959B8469D; Wed, 9 May 2018 23:08:06 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180510060806.16959B8469D@rfc-editor.org> Date: Wed, 9 May 2018 23:08:06 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8368_on_Using_an_Autonomic_Control_Plane?= =?utf-8?q?_for_Stable_Connectivity_of_Network_Operations=2C_Administratio?= =?utf-8?q?n=2C_and_Maintenance_=28OAM=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, anima@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 8368 Title: Using an Autonomic Control Plane for Stable Connectivity of Network Operations, Administration, and Maintenance (OAM) Author: T. Eckert, Ed., M. Behringer Status: Informational Stream: IETF Date: May 2018 Mailbox: tte+ietf@cs.fau.de, michael.h.behringer@gmail.com Pages: 24 Characters: 59777 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-anima-stable-connectivity-10.txt URL: https://www.rfc-editor.org/info/rfc8368 DOI: 10.17487/RFC8368 Operations, Administration, and Maintenance (OAM), as per BCP 161, for data networks is often subject to the problem of circular dependencies when relying on connectivity provided by the network to be managed for the OAM purposes. Provisioning while bringing up devices and networks tends to be more difficult to automate than service provisioning later on. Changes in core network functions impacting reachability cannot be automated because of ongoing connectivity requirements for the OAM equipment itself, and widely used OAM protocols are not secure enough to be carried across the network without security concerns. This document describes how to integrate OAM processes with an autonomic control plane in order to provide stable and secure connectivity for those OAM processes. This connectivity is not subject to the aforementioned circular dependencies. This document is a product of the Autonomic Networking Integrated Model and Approach 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 May 11 17:21:00 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 A072F12D7F3 for ; Fri, 11 May 2018 17:21:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.201 X-Spam-Level: X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M-NltoIyAbEC for ; Fri, 11 May 2018 17:20:59 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C900129C5D for ; Fri, 11 May 2018 17:20:59 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 3A1C8B82DB5; Fri, 11 May 2018 17:20:56 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 0A938B82DB4; Fri, 11 May 2018 17:20:54 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180512002055.0A938B82DB4@rfc-editor.org> Date: Fri, 11 May 2018 17:20:54 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8370_on_Techniques_to_Improve_the_Scalab?= =?utf-8?q?ility_of_RSVP-TE_Deployments?= 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 8370 Title: Techniques to Improve the Scalability of RSVP-TE Deployments Author: V. Beeram, Ed., I. Minei, R. Shakir, D. Pacella, T. Saad Status: Standards Track Stream: IETF Date: May 2018 Mailbox: vbeeram@juniper.net, inaminei@google.com, rjs@rob.sh, dante.j.pacella@verizon.com, tsaad@cisco.com Pages: 11 Characters: 21622 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-teas-rsvp-te-scaling-rec-09.txt URL: https://www.rfc-editor.org/info/rfc8370 DOI: 10.17487/RFC8370 Networks that utilize RSVP-TE LSPs are encountering implementations that have a limited ability to support the growth in the number of LSPs deployed. This document defines two techniques, Refresh-Interval Independent RSVP (RI-RSVP) and Per-Peer Flow Control, that reduce the number of processing cycles required to maintain RSVP-TE LSP state in Label Switching Routers (LSRs) and hence allow implementations to support larger scale deployments. This document is a product of the Traffic Engineering Architecture and Signaling Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Fri May 11 17:21: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 65CFE12EACB for ; Fri, 11 May 2018 17:21:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.201 X-Spam-Level: X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K5kkT8pgr35M for ; Fri, 11 May 2018 17:21:40 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85F7712E9DC for ; Fri, 11 May 2018 17:21:18 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 483E4B82DC4; Fri, 11 May 2018 17:21:12 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id ED2A5B82DC0; Fri, 11 May 2018 17:21:07 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180512002107.ED2A5B82DC0@rfc-editor.org> Date: Fri, 11 May 2018 17:21:07 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8379_on_OSPF_Graceful_Link_Shutdown?= 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: lsr@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: rfc-dist-bounces@rfc-editor.org Sender: "rfc-dist" A new Request for Comments is now available in online RFC libraries. RFC 8379 Title: OSPF Graceful Link Shutdown Author: S. Hegde, P. Sarkar, H. Gredler, M. Nanduri, L. Jalil Status: Standards Track Stream: IETF Date: May 2018 Mailbox: shraddha@juniper.net, pushpasis.ietf@gmail.com, hannes@rtbrick.com, mnanduri@ebay.com, luay.jalil@verizon.com Pages: 17 Characters: 37671 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ospf-link-overload-16.txt URL: https://www.rfc-editor.org/info/rfc8379 DOI: 10.17487/RFC8379 When a link is being prepared to be taken out of service, the traffic needs to be diverted from both ends of the link. Increasing the metric to the highest value on one side of the link is not sufficient to divert the traffic flowing in the other direction. It is useful for the routers in an OSPFv2 or OSPFv3 routing domain to be able to advertise a link as being in a graceful-shutdown state to indicate impending maintenance activity on the link. This information can be used by the network devices to reroute the traffic effectively. This document describes the protocol extensions to disseminate graceful-link-shutdown information in OSPFv2 and OSPFv3. This document is a product of the Open Shortest Path First IGP Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Tue May 15 17:15:54 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 2866A12EB45 for ; Tue, 15 May 2018 17:15:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 35mxXNF2uuxe for ; Tue, 15 May 2018 17:15:52 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EBBB12E8EB for ; Tue, 15 May 2018 17:15:52 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id EE6A6B8182D; Tue, 15 May 2018 17:15:47 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 00B06B8182E; Tue, 15 May 2018 17:15:45 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180516001546.00B06B8182E@rfc-editor.org> Date: Tue, 15 May 2018 17:15:45 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8387_on_Practical_Considerations_and_Im?= =?utf-8?q?plementation_Experiences_in_Securing_Smart_Object_Networks?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, lwip@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 8387 Title: Practical Considerations and Implementation Experiences in Securing Smart Object Networks Author: M. Sethi, J. Arkko, A. Keranen, H. Back Status: Informational Stream: IETF Date: May 2018 Mailbox: mohit@piuha.net, jari.arkko@piuha.net, ari.keranen@ericsson.com, heidi.back@nokia.com Pages: 33 Characters: 86278 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-lwig-crypto-sensors-06.txt URL: https://www.rfc-editor.org/info/rfc8387 DOI: 10.17487/RFC8387 This memo describes challenges associated with securing resource- constrained smart object devices. The memo describes a possible deployment model where resource-constrained devices sign message objects, discusses the availability of cryptographic libraries for resource-constrained devices, and presents some preliminary experiences with those libraries for message signing on resource- constrained devices. Lastly, the memo discusses trade-offs involving different types of security approaches. This document is a product of the Light-Weight Implementation Guidance 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 Thu May 17 08:42:00 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 68B7112EB59 for ; Thu, 17 May 2018 08:42:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XqrA3b4HXvFt for ; Thu, 17 May 2018 08:41:58 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A141812EB2D for ; Thu, 17 May 2018 08:41:58 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5D5A7B8126C; Thu, 17 May 2018 08:41:52 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 18621B8126B; Thu, 17 May 2018 08:41:50 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180517154150.18621B8126B@rfc-editor.org> Date: Thu, 17 May 2018 08:41:50 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8375_on_Special-Use_Domain_=27home=2Ear?= =?utf-8?q?pa=2E=27?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, homenet@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 8375 Title: Special-Use Domain 'home.arpa.' Author: P. Pfister, T. Lemon Status: Standards Track Stream: IETF Date: May 2018 Mailbox: pierre.pfister@darou.fr, mellon@fugue.com Pages: 12 Characters: 27377 Updates: RFC 7788 I-D Tag: draft-ietf-homenet-dot-14.txt URL: https://www.rfc-editor.org/info/rfc8375 DOI: 10.17487/RFC8375 This document specifies the behavior that is expected from the Domain Name System with regard to DNS queries for names ending with '.home.arpa.' and designates this domain as a special-use domain name. 'home.arpa.' is designated for non-unique use in residential home networks. The Home Networking Control Protocol (HNCP) is updated to use the 'home.arpa.' domain instead of '.home'. This document is a product of the Home Networking Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Thu May 17 08:42:30 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 3276512EB90 for ; Thu, 17 May 2018 08:42:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CBmoYh4-r4cQ for ; Thu, 17 May 2018 08:42:25 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 496F512EB8D for ; Thu, 17 May 2018 08:42:18 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 351BBB8127B; Thu, 17 May 2018 08:42:12 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 87CB9B8127A; Thu, 17 May 2018 08:42:10 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180517154210.87CB9B8127A@rfc-editor.org> Date: Thu, 17 May 2018 08:42:10 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8386_on_Privacy_Considerations_for_Prot?= =?utf-8?q?ocols_Relying_on_IP_Broadcast_or_Multicast?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, int-area@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 8386 Title: Privacy Considerations for Protocols Relying on IP Broadcast or Multicast Author: R. Winter, M. Faath, F. Weisshaar Status: Informational Stream: IETF Date: May 2018 Mailbox: rolf.winter@hs-augsburg.de, faath@conntac.net, fabian.weisshaar@hs-augsburg.de Pages: 13 Characters: 32238 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-intarea-broadcast-consider-09.txt URL: https://www.rfc-editor.org/info/rfc8386 DOI: 10.17487/RFC8386 A number of application-layer protocols make use of IP broadcast or multicast messages for functions such as local service discovery or name resolution. Some of these functions can only be implemented efficiently using such mechanisms. When using broadcast or multicast messages, a passive observer in the same broadcast or multicast domain can trivially record these messages and analyze their content. Therefore, designers of protocols that make use of broadcast or multicast messages need to take special care when designing their protocols. This document is a product of the Internet 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 Thu May 17 08:44:06 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 5530412EB77 for ; Thu, 17 May 2018 08:44:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fpgv7MBp2j2Q for ; Thu, 17 May 2018 08:44:04 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4E5012EB8F for ; Thu, 17 May 2018 08:44:04 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 1FF4AB827C6; Thu, 17 May 2018 08:44:00 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 14B44B827C6; Thu, 17 May 2018 08:43:58 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180517154358.14B44B827C6@rfc-editor.org> Date: Thu, 17 May 2018 08:43:58 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8388_on_Usage_and_Applicability_of_BGP_?= =?utf-8?q?MPLS-Based_Ethernet_VPN?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.26 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 8388 Title: Usage and Applicability of BGP MPLS-Based Ethernet VPN Author: J. Rabadan, Ed., S. Palislamovic, W. Henderickx, A. Sajassi, J. Uttaro Status: Informational Stream: IETF Date: May 2018 Mailbox: jorge.rabadan@nokia.com, senad.palislamovic@nokia.com, wim.henderickx@nokia.com, sajassi@cisco.com, uttaro@att.com Pages: 31 Characters: 76431 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-bess-evpn-usage-09.txt URL: https://www.rfc-editor.org/info/rfc8388 DOI: 10.17487/RFC8388 This document discusses the usage and applicability of BGP MPLS-based Ethernet VPN (EVPN) in a simple and fairly common deployment scenario. The different EVPN procedures are explained in the example scenario along with the benefits and trade-offs of each option. This document is intended to provide a simplified guide for the deployment of EVPN networks. This document is a product of the BGP Enabled Services Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Mon May 21 16:44:52 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 018B712DA26 for ; Mon, 21 May 2018 16:44:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.201 X-Spam-Level: X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Jj7wtFrBjAa for ; Mon, 21 May 2018 16:44:50 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C390F12DA00 for ; Mon, 21 May 2018 16:44:48 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 46985B82841; Mon, 21 May 2018 16:44:37 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 38C78B8283F; Mon, 21 May 2018 16:44:35 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180521234435.38C78B8283F@rfc-editor.org> Date: Mon, 21 May 2018 16:44:35 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8353_on_Generic_Security_Service_API_Ve?= =?utf-8?q?rsion_2=3A_Java_Bindings_Update?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: kitten@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 8353 Title: Generic Security Service API Version 2: Java Bindings Update Author: M. Upadhyay, S. Malkani, W. Wang Status: Standards Track Stream: IETF Date: May 2018 Mailbox: m.d.upadhyay+ietf@gmail.com, seema.malkani@gmail.com, weijun.wang@oracle.com Pages: 96 Characters: 204802 Obsoletes: RFC 5653 I-D Tag: draft-ietf-kitten-rfc5653bis-07.txt URL: https://www.rfc-editor.org/info/rfc8353 DOI: 10.17487/RFC8353 The Generic Security Services Application Programming Interface (GSS-API) offers application programmers uniform access to security services atop a variety of underlying cryptographic mechanisms. This document updates the Java bindings for the GSS-API that are specified in "Generic Security Service API Version 2: Java Bindings Update" (RFC 5653). This document obsoletes RFC 5653 by adding a new output token field to the GSSException class so that when the initSecContext or acceptSecContext methods of the GSSContext class fail, it has a chance to emit an error token that can be sent to the peer for debugging or informational purpose. The stream-based GSSContext methods are also removed in this version. The GSS-API is described at a language-independent conceptual level in "Generic Security Service Application Program Interface Version 2, Update 1" (RFC 2743). The GSS-API allows a caller application to authenticate a principal identity, to delegate rights to a peer, and to apply security services such as confidentiality and integrity on a per-message basis. Examples of security mechanisms defined for GSS-API are "The Simple Public-Key GSS-API Mechanism (SPKM)" (RFC 2025) and "The Kerberos Version 5 Generic Security Service Application Program Interface (GSS-API) Mechanism: Version 2" (RFC 4121). This document is a product of the Common Authentication Technology Next Generation 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 May 21 22:39:50 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 BE49712DA22 for ; Mon, 21 May 2018 22:39:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VMkwdX8WPgK0 for ; Mon, 21 May 2018 22:39:49 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60B05124B18 for ; Mon, 21 May 2018 22:39:49 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D1033B828BF; Mon, 21 May 2018 22:39:37 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 735F8B828BD; Mon, 21 May 2018 22:39:36 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180522053936.735F8B828BD@rfc-editor.org> Date: Mon, 21 May 2018 22:39:36 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8381_on_Transparent_Interconnection_of_?= =?utf-8?q?Lots_of_Links_=28TRILL=29=3A_Vendor-Specific_RBridge_Channel_Pr?= =?utf-8?q?otocol?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.26 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 8381 Title: Transparent Interconnection of Lots of Links (TRILL): Vendor-Specific RBridge Channel Protocol Author: D. Eastlake 3rd, Y. Li, W. Hao, A. Banerjee Status: Standards Track Stream: IETF Date: May 2018 Mailbox: d3e3e3@gmail.com, liyizhou@huawei.com, haoweiguo@huawei.com, ayabaner@cisco.com Pages: 11 Characters: 22410 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-trill-vendor-channel-01.txt URL: https://www.rfc-editor.org/info/rfc8381 DOI: 10.17487/RFC8381 The IETF TRILL (Transparent Interconnection of Lots of Links) protocol is implemented by devices called TRILL switches or RBridges (Routing Bridges). TRILL includes a general mechanism, called an RBridge Channel, for the transmission of typed messages between RBridges in the same campus and between RBridges and end stations on the same link. This document specifies a method to send vendor-specific messages over the RBridge Channel facility. 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 Mon May 21 23:04:46 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 AC51812EAAE for ; Mon, 21 May 2018 23:04:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zDMnBMTX3K1h for ; Mon, 21 May 2018 23:04:45 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44C5C12E3AE for ; Mon, 21 May 2018 23:04:45 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 74961B80068; Mon, 21 May 2018 23:04:33 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 3AB15B80066; Mon, 21 May 2018 23:04:32 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180522060432.3AB15B80066@rfc-editor.org> Date: Mon, 21 May 2018 23:04:32 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8380_on_Directory-Assisted_Transparent_?= =?utf-8?q?Interconnection_of_Lots_of_Links_=28TRILL=29_Encapsulation?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.26 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 8380 Title: Directory-Assisted Transparent Interconnection of Lots of Links (TRILL) Encapsulation Author: L. Dunbar, D. Eastlake 3rd, R. Perlman Status: Standards Track Stream: IETF Date: May 2018 Mailbox: linda.dunbar@huawei.com, d3e3e3@gmail.com, Radia@alum.mit.edu Pages: 10 Characters: 23882 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-trill-directory-assisted-encap-11.txt URL: https://www.rfc-editor.org/info/rfc8380 DOI: 10.17487/RFC8380 This document describes how data center networks can benefit from non-RBridge nodes performing TRILL (Transparent Interconnection of Lots of Links) encapsulation with assistance from a directory service. 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 Tue May 22 10:22:05 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 C2808128954 for ; Tue, 22 May 2018 10:22:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mRRDdlXBR43I for ; Tue, 22 May 2018 10:22:04 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D1D01201F8 for ; Tue, 22 May 2018 10:22:04 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 3917AB81DFB; Tue, 22 May 2018 10:21:52 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id B5703B81DEC; Tue, 22 May 2018 10:21:49 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180522172149.B5703B81DEC@rfc-editor.org> Date: Tue, 22 May 2018 10:21:49 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8363_on_GMPLS_OSPF-TE_Extensions_in_Sup?= =?utf-8?q?port_of_Flexi-Grid_Dense_Wavelength_Division_Multiplexing_=28DW?= =?utf-8?q?DM=29_Networks?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, ccamp@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 8363 Title: GMPLS OSPF-TE Extensions in Support of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) Networks Author: X. Zhang, H. Zheng, R. Casellas, O. Gonzalez de Dios, D. Ceccarelli Status: Standards Track Stream: IETF Date: May 2018 Mailbox: zhang.xian@huawei.com, zhenghaomian@huawei.com, ramon.casellas@cttc.es, oscar.gonzalezdedios@telefonica.com, daniele.ceccarelli@ericsson.com Pages: 17 Characters: 37332 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-ccamp-flexible-grid-ospf-ext-09.txt URL: https://www.rfc-editor.org/info/rfc8363 DOI: 10.17487/RFC8363 The International Telecommunication Union Telecommunication standardization sector (ITU-T) has extended its Recommendations G.694.1 and G.872 to include a new Dense Wavelength Division Multiplexing (DWDM) grid by defining channel spacings, a set of nominal central frequencies, and the concept of the "frequency slot". Corresponding techniques for data-plane connections are known as "flexi-grid". Based on the characteristics of flexi-grid defined in G.694.1 and in RFCs 7698 and 7699, this document describes the Open Shortest Path First - Traffic Engineering (OSPF-TE) extensions in support of GMPLS control of networks that include devices that use the new flexible optical grid. This document is a product of the Common Control and Measurement Plane 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 May 23 16:05:05 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 713C612D86D for ; Wed, 23 May 2018 16:05:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.201 X-Spam-Level: X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id grdDwoTlvjPt for ; Wed, 23 May 2018 16:05:04 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D40B12D7F0 for ; Wed, 23 May 2018 16:05:04 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 528D1B817D5; Wed, 23 May 2018 16:04:50 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 16C2DB817D3; Wed, 23 May 2018 16:04:49 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180523230449.16C2DB817D3@rfc-editor.org> Date: Wed, 23 May 2018 16:04:49 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8398_on_Internationalized_Email_Address?= =?utf-8?q?es_in_X=2E509_Certificates?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: spasm@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: rfc-dist-bounces@rfc-editor.org Sender: "rfc-dist" A new Request for Comments is now available in online RFC libraries. RFC 8398 Title: Internationalized Email Addresses in X.509 Certificates Author: A. Melnikov, Ed., W. Chuang, Ed. Status: Standards Track Stream: IETF Date: May 2018 Mailbox: alexey.melnikov@isode.com, weihaw@google.com Pages: 12 Characters: 26562 Updates: RFC 5280 I-D Tag: draft-ietf-lamps-eai-addresses-18.txt URL: https://www.rfc-editor.org/info/rfc8398 DOI: 10.17487/RFC8398 This document defines a new name form for inclusion in the otherName field of an X.509 Subject Alternative Name and Issuer Alternative Name extension that allows a certificate subject to be associated with an internationalized email address. This document updates RFC 5280. This document is a product of the Limited Additional Mechanisms for PKIX and SMIME Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Wed May 23 16:05: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 7C11C12EA93 for ; Wed, 23 May 2018 16:05:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.201 X-Spam-Level: X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HIq_4V8G-rr2 for ; Wed, 23 May 2018 16:05:25 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3515412E8C6 for ; Wed, 23 May 2018 16:05:22 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 3041DB817DA; Wed, 23 May 2018 16:04:55 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 47547B817DA; Wed, 23 May 2018 16:04:53 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180523230453.47547B817DA@rfc-editor.org> Date: Wed, 23 May 2018 16:04:53 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8399_on_Internationalization_Updates_to?= =?utf-8?q?_RFC_5280?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: spasm@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: rfc-dist-bounces@rfc-editor.org Sender: "rfc-dist" A new Request for Comments is now available in online RFC libraries. RFC 8399 Title: Internationalization Updates to RFC 5280 Author: R. Housley Status: Standards Track Stream: IETF Date: May 2018 Mailbox: housley@vigilsec.com Pages: 9 Characters: 19372 Updates: RFC 5280 I-D Tag: draft-ietf-lamps-rfc5280-i18n-update-04.txt URL: https://www.rfc-editor.org/info/rfc8399 DOI: 10.17487/RFC8399 The updates to RFC 5280 described in this document provide alignment with the 2008 specification for Internationalized Domain Names (IDNs) and add support for internationalized email addresses in X.509 certificates. This document is a product of the Limited Additional Mechanisms for PKIX and SMIME Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Thu May 24 16:50:23 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 2620D12EAA7 for ; Thu, 24 May 2018 16:50:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vQdosNc0dbpn for ; Thu, 24 May 2018 16:50:21 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C74D12E8D7 for ; Thu, 24 May 2018 16:50:21 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 3D242B828B0; Thu, 24 May 2018 16:50:06 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 715BCB828AE; Thu, 24 May 2018 16:50:04 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180524235004.715BCB828AE@rfc-editor.org> Date: Thu, 24 May 2018 16:50:04 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8373_on_Negotiating_Human_Language_in_R?= =?utf-8?q?eal-Time_Communications?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: slim@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 8373 Title: Negotiating Human Language in Real-Time Communications Author: R. Gellens Status: Standards Track Stream: IETF Date: May 2018 Mailbox: rg+ietf@coretechnologyconsulting.com Pages: 13 Characters: 27727 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-slim-negotiating-human-language-24.txt URL: https://www.rfc-editor.org/info/rfc8373 DOI: 10.17487/RFC8373 Users have various human (i.e., natural) language needs, abilities, and preferences regarding spoken, written, and signed languages. This document defines new Session Description Protocol (SDP) media- level attributes so that when establishing interactive communication sessions ("calls"), it is possible to negotiate (i.e., communicate and match) the caller's language and media needs with the capabilities of the called party. This is especially important for emergency calls, because it allows for a call to be handled by a call taker capable of communicating with the user or for a translator or relay operator to be bridged into the call during setup. However, this also applies to non-emergency calls (for example, calls to a company call center). This document describes the need as well as a solution that uses new SDP media attributes. This document is a product of the Selection of Language for Internet Media 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 May 31 16:46:21 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 6BF45126FB3 for ; Thu, 31 May 2018 16:46:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=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 uDcn94o_MtZy for ; Thu, 31 May 2018 16:46:19 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 209DC129C56 for ; Thu, 31 May 2018 16:46:19 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id A6CF9B82971; Thu, 31 May 2018 16:45:55 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 3C42FB82962; Thu, 31 May 2018 16:45:54 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180531234554.3C42FB82962@rfc-editor.org> Date: Thu, 31 May 2018 16:45:54 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8376_on_Low-Power_Wide_Area_Network_=28?= =?utf-8?q?LPWAN=29_Overview?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: lp-wan@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 8376 Title: Low-Power Wide Area Network (LPWAN) Overview Author: S. Farrell, Ed. Status: Informational Stream: IETF Date: May 2018 Mailbox: stephen.farrell@cs.tcd.ie Pages: 43 Characters: 101594 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-lpwan-overview-10.txt URL: https://www.rfc-editor.org/info/rfc8376 DOI: 10.17487/RFC8376 Low-Power Wide Area Networks (LPWANs) are wireless technologies with characteristics such as large coverage areas, low bandwidth, possibly very small packet and application-layer data sizes, and long battery life operation. This memo is an informational overview of the set of LPWAN technologies being considered in the IETF and of the gaps that exist between the needs of those technologies and the goal of running IP in LPWANs. This document is a product of the IPv6 over Low Power Wide-Area Networks 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 Thu May 31 16:46:58 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 43D4812D88F for ; Thu, 31 May 2018 16:46:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BTUZxHv-aUzV for ; Thu, 31 May 2018 16:46:49 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 495C0126B6E for ; Thu, 31 May 2018 16:46:39 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 75FE7B81DFF; Thu, 31 May 2018 16:46:16 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id DEADBB81DF3; Thu, 31 May 2018 16:46:14 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180531234614.DEADBB81DF3@rfc-editor.org> Date: Thu, 31 May 2018 16:46:14 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8383_on_Transparent_Interconnection_of_?= =?utf-8?q?Lots_of_Links_=28TRILL=29=3A_Address_Flush_Message?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.26 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 8383 Title: Transparent Interconnection of Lots of Links (TRILL): Address Flush Message Author: W. Hao, D. Eastlake 3rd, Y. Li, M. Umair Status: Standards Track Stream: IETF Date: May 2018 Mailbox: haoweiguo@huawei.com, d3e3e3@gmail.com, liyizhou@huawei.com, mohammed.umair2@gmail.com Pages: 20 Characters: 41551 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-trill-address-flush-06.txt URL: https://www.rfc-editor.org/info/rfc8383 DOI: 10.17487/RFC8383 The TRILL (Transparent Interconnection of Lots of Links) protocol, by default, learns end station addresses from observing the data plane. In particular, it learns local Media Access Control (MAC) addresses and the edge switch port of attachment from the receipt of local data frames and learns remote MAC addresses and the edge switch port of attachment from the decapsulation of remotely sourced TRILL Data packets. This document specifies a message by which a TRILL switch can explicitly request other TRILL switches to flush certain MAC reachability learned through the decapsulation of TRILL Data packets. This is a supplement to the TRILL automatic address forgetting (see Section 4.8.3 of RFC 6325) and can assist in achieving more rapid convergence in case of topology or configuration change. 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 Thu May 31 16:47:15 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 B8BBB126FB3 for ; Thu, 31 May 2018 16:47:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MZD9if22R0Do for ; Thu, 31 May 2018 16:47:14 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF77512D87C for ; Thu, 31 May 2018 16:46:56 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 2D92DB81E8C; Thu, 31 May 2018 16:46:34 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 87260B81E7F; Thu, 31 May 2018 16:46:32 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180531234632.87260B81E7F@rfc-editor.org> Date: Thu, 31 May 2018 16:46:32 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8391_on_XMSS=3A_eXtended_Merkle_Signatu?= =?utf-8?q?re_Scheme?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, cfrg@irtf.org, rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: rfc-dist-bounces@rfc-editor.org Sender: "rfc-dist" A new Request for Comments is now available in online RFC libraries. RFC 8391 Title: XMSS: eXtended Merkle Signature Scheme Author: A. Huelsing, D. Butin, S. Gazdag, J. Rijneveld, A. Mohaisen Status: Informational Stream: IRTF Date: May 2018 Mailbox: ietf@huelsing.net, dbutin@cdc.informatik.tu-darmstadt.de, ietf@gazdag.de, ietf@joostrijneveld.nl, mohaisen@ieee.org Pages: 74 Characters: 155770 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-irtf-cfrg-xmss-hash-based-signatures-12.txt URL: https://www.rfc-editor.org/info/rfc8391 DOI: 10.17487/RFC8391 This note describes the eXtended Merkle Signature Scheme (XMSS), a hash-based digital signature system that is based on existing descriptions in scientific literature. This note specifies Winternitz One-Time Signature Plus (WOTS+), a one-time signature scheme; XMSS, a single-tree scheme; and XMSS^MT, a multi-tree variant of XMSS. Both XMSS and XMSS^MT use WOTS+ as a main building block. XMSS provides cryptographic digital signatures without relying on the conjectured hardness of mathematical problems. Instead, it is proven that it only relies on the properties of cryptographic hash functions. XMSS provides strong security guarantees and is even secure when the collision resistance of the underlying hash function is broken. It is suitable for compact implementations, is relatively simple to implement, and naturally resists side-channel attacks. Unlike most other signature systems, hash-based signatures can so far withstand known attacks using quantum computers. This document is a product of the Crypto Forum Research Group of the IRTF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce, rfc-dist and IRTF-Announce lists.To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist https://www.irtf.org/mailman/listinfo/irtf-announce For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Thu May 31 16:48:18 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 088DF129C53 for ; Thu, 31 May 2018 16:48:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sRK4OTpUQL3i for ; Thu, 31 May 2018 16:48:07 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A248127698 for ; Thu, 31 May 2018 16:47:20 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id C224AB81F36; Thu, 31 May 2018 16:46:57 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id D7E8FB81F2F; Thu, 31 May 2018 16:46:56 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180531234656.D7E8FB81F2F@rfc-editor.org> Date: Thu, 31 May 2018 16:46:56 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8394_on_Split_Network_Virtualization_Ed?= =?utf-8?q?ge_=28Split-NVE=29_Control-Plane_Requirements?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.26 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 8394 Title: Split Network Virtualization Edge (Split-NVE) Control-Plane Requirements Author: Y. Li, D. Eastlake 3rd, L. Kreeger, T. Narten, D. Black Status: Informational Stream: IETF Date: May 2018 Mailbox: liyizhou@huawei.com, d3e3e3@gmail.com, lkreeger@gmail.com, narten@us.ibm.com, david.black@dell.com Pages: 26 Characters: 63300 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-nvo3-hpvr2nve-cp-req-17.txt URL: https://www.rfc-editor.org/info/rfc8394 DOI: 10.17487/RFC8394 In the Split Network Virtualization Edge (Split-NVE) architecture, the functions of the NVE are split across a server and a piece of external network equipment that is called an "External NVE". The server-resident control-plane functionality resides in control software, which may be part of hypervisor or container-management software; for simplicity, this document refers to the hypervisor as the "location" of this software. One or more control-plane protocols between a hypervisor and its associated External NVE(s) are used by the hypervisor to distribute its virtual-machine networking state to the External NVE(s) for further handling. This document illustrates the functionality required by this type of control-plane signaling protocol and outlines the high-level requirements. Virtual-machine states as well as state transitioning are summarized to help clarify the protocol requirements. 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 Thu May 31 16:48:57 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 5E98812D940 for ; Thu, 31 May 2018 16:48:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hzxxSA8Q-eU8 for ; Thu, 31 May 2018 16:48:56 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFA7012D957 for ; Thu, 31 May 2018 16:47:45 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 8770DB82A70; Thu, 31 May 2018 16:47:23 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id EB77DB82A60; Thu, 31 May 2018 16:47:21 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20180531234721.EB77DB82A60@rfc-editor.org> Date: Thu, 31 May 2018 16:47:21 -0700 (PDT) Subject: [rfc-dist] =?utf-8?q?RFC_8397_on_Transparent_Interconnection_of_?= =?utf-8?q?Lots_of_Links_=28TRILL=29_Multilevel_Using_Unique_Nicknames?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.26 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 8397 Title: Transparent Interconnection of Lots of Links (TRILL) Multilevel Using Unique Nicknames Author: M. Zhang, D. Eastlake 3rd, R. Perlman, H. Zhai, D. Liu Status: Standards Track Stream: IETF Date: May 2018 Mailbox: zhangmingui@huawei.com, d3e3e3@gmail.com, radia@alum.mit.edu, honjun.zhai@tom.com, liudx@gsta.com Pages: 16 Characters: 35028 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-trill-multilevel-unique-nickname-07.txt URL: https://www.rfc-editor.org/info/rfc8397 DOI: 10.17487/RFC8397 TRILL (Transparent Interconnection of Lots of Links) routing can be extended to support multiple levels by building on the multilevel feature of IS-IS routing. Depending on how nicknames are managed, there are two primary alternatives to realize TRILL multilevel: the unique nickname approach and the aggregated nickname approach as discussed in RFC 8243. This document specifies a unique nickname approach. This approach gives unique nicknames to all TRILL switches across the multilevel 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