From rfc-dist-bounces@rfc-editor.org Sun Nov 4 20: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 ABCE012D7EA for ; Sun, 4 Nov 2018 20:44:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.201 X-Spam-Level: X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W0Jds4wqz7pR for ; Sun, 4 Nov 2018 20:44:50 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B99E71298C5 for ; Sun, 4 Nov 2018 20:44:50 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 93C38B815FA; Sun, 4 Nov 2018 20:44:36 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 7DA09B815E3; Sun, 4 Nov 2018 20:44:34 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20181105044434.7DA09B815E3@rfc-editor.org> Date: Sun, 4 Nov 2018 20:44:34 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8480_on_6TiSCH_Operation_Sublayer_=286t?= =?utf-8?q?op=29_Protocol_=286P=29?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, 6tisch@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 8480 Title: 6TiSCH Operation Sublayer (6top) Protocol (6P) Author: Q. Wang, Ed., X. Vilajosana, T. Watteyne Status: Standards Track Stream: IETF Date: November 2018 Mailbox: wangqin@ies.ustb.edu.cn, xvilajosana@uoc.edu, thomas.watteyne@analog.com Pages: 50 Characters: 107695 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-6tisch-6top-protocol-12.txt URL: https://www.rfc-editor.org/info/rfc8480 DOI: 10.17487/RFC8480 This document defines the "IPv6 over the TSCH mode of IEEE 802.15.4e" (6TiSCH) Operation Sublayer (6top) Protocol (6P), which enables distributed scheduling in 6TiSCH networks. 6P allows neighbor nodes to add/delete Time-Slotted Channel Hopping (TSCH) cells to/on one another. 6P is part of the 6TiSCH Operation Sublayer (6top), the layer just above the IEEE Std 802.15.4 TSCH Medium Access Control layer. 6top is composed of one or more Scheduling Functions (SFs) and the 6top Protocol defined in this document. A 6top SF decides when to add/delete cells, and it triggers 6P Transactions. The definition of SFs is out of scope for this document; however, this document provides the requirements for an SF. This document is a product of the IPv6 over the TSCH mode of IEEE 802.15.4e 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 Nov 14 12:43:51 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 4E3CA130E18 for ; Wed, 14 Nov 2018 12:43:51 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SqNHfDAuMOsP for ; Wed, 14 Nov 2018 12:43:49 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D896128CB7 for ; Wed, 14 Nov 2018 12:43:49 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id A1A61B812FF; Wed, 14 Nov 2018 12:43:25 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id EED01B812FC; Wed, 14 Nov 2018 12:43:23 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20181114204323.EED01B812FC@rfc-editor.org> Date: Wed, 14 Nov 2018 12:43:23 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8444_on_OSPFv2_Extensions_for_Bit_Index?= =?utf-8?q?_Explicit_Replication_=28BIER=29?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, bier@ietf.org, rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: rfc-dist-bounces@rfc-editor.org Sender: "rfc-dist" A new Request for Comments is now available in online RFC libraries. RFC 8444 Title: OSPFv2 Extensions for Bit Index Explicit Replication (BIER) Author: P. Psenak, Ed., N. Kumar, IJ. Wijnands, A. Dolganow, T. Przygienda, J. Zhang, S. Aldrin Status: Standards Track Stream: IETF Date: November 2018 Mailbox: ppsenak@cisco.com, naikumar@cisco.com, ice@cisco.com, andrew.dolganow@nokia.com, prz@juniper.net, zzhang@juniper.net, aldrin.ietf@gmail.com Pages: 12 Characters: 23780 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-bier-ospf-bier-extensions-18.txt URL: https://www.rfc-editor.org/info/rfc8444 DOI: 10.17487/RFC8444 Bit Index Explicit Replication (BIER) is an architecture that provides optimal multicast forwarding through a "BIER domain" without requiring intermediate routers to maintain multicast-related, per- flow state. BIER also does not require an explicit tree-building protocol for its operation. A multicast data packet enters a BIER domain at a Bit-Forwarding Ingress Router (BFIR) and leaves the BIER domain at one or more Bit-Forwarding Egress Routers (BFERs). The BFIR adds a BIER packet header to the packet. The BIER packet header contains a BitString in which each bit represents exactly one BFER to forward the packet to. The set of BFERs to which the multicast packet needs to be forwarded is expressed by the set of bits in the BIER packet header. This document describes the OSPF protocol extension (from RFC 2328) that is required for BIER with MPLS encapsulation (which is defined in RFC 8296). Support for other encapsulation types and the use of multiple encapsulation types are outside the scope of this document. This document is a product of the Bit Indexed Explicit Replication 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 Nov 14 12:44:11 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 93EB1130EE5 for ; Wed, 14 Nov 2018 12:44:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nZyPuVqmUIu6 for ; Wed, 14 Nov 2018 12:44:09 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1E6B130F3E for ; Wed, 14 Nov 2018 12:44:09 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 3878EB8130D; Wed, 14 Nov 2018 12:43:40 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 80F5CB8130E; Wed, 14 Nov 2018 12:43:39 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20181114204339.80F5CB8130E@rfc-editor.org> Date: Wed, 14 Nov 2018 12:43:39 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8468_on_IPv4=2C_IPv6=2C_and_IPv4-IPv6_C?= =?utf-8?q?oexistence=3A_Updates_for_the_IP_Performance_Metrics_=28IPPM=29?= =?utf-8?q?_Framework?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, ippm@ietf.org, rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: rfc-dist-bounces@rfc-editor.org Sender: "rfc-dist" A new Request for Comments is now available in online RFC libraries. RFC 8468 Title: IPv4, IPv6, and IPv4-IPv6 Coexistence: Updates for the IP Performance Metrics (IPPM) Framework Author: A. Morton, J. Fabini, N. Elkins, M. Ackermann, V. Hegde Status: Informational Stream: IETF Date: November 2018 Mailbox: acmorton@att.com, joachim.fabini@tuwien.ac.at, nalini.elkins@insidethestack.com, mackermann@bcbsm.com, vinayakh@gmail.com Pages: 15 Characters: 35970 Updates: RFC 2330 I-D Tag: draft-ietf-ippm-2330-ipv6-06.txt URL: https://www.rfc-editor.org/info/rfc8468 DOI: 10.17487/RFC8468 This memo updates the IP Performance Metrics (IPPM) framework defined by RFC 2330 with new considerations for measurement methodology and testing. It updates the definition of standard-formed packets to include IPv6 packets, deprecates the definition of minimal IP packet, and augments distinguishing aspects, referred to as Type-P, for test packets in RFC 2330. This memo identifies that IPv4-IPv6 coexistence can challenge measurements within the scope of the IPPM framework. Example use cases include, but are not limited to, IPv4-IPv6 translation, NAT, and protocol encapsulation. IPv6 header compression and use of IPv6 over Low-Power Wireless Area Networks (6LoWPAN) are considered and excluded from the standard-formed packet evaluation. This document is a product of the IP Performance Measurement 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 Nov 14 12:44:28 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 EF3F7130F18 for ; Wed, 14 Nov 2018 12:44:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SsOrvtl28hwQ for ; Wed, 14 Nov 2018 12:44:26 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70088130EE0 for ; Wed, 14 Nov 2018 12:44:26 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id C90AFB8131F; Wed, 14 Nov 2018 12:43:57 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 8F7F2B8131B; Wed, 14 Nov 2018 12:43:55 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20181114204355.8F7F2B8131B@rfc-editor.org> Date: Wed, 14 Nov 2018 12:43:55 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8469_on_Recommendation_to_Use_the_Ether?= =?utf-8?q?net_Control_Word?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, pals@ietf.org, rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: rfc-dist-bounces@rfc-editor.org Sender: "rfc-dist" A new Request for Comments is now available in online RFC libraries. RFC 8469 Title: Recommendation to Use the Ethernet Control Word Author: S. Bryant, A. Malis, I. Bagdonas Status: Standards Track Stream: IETF Date: November 2018 Mailbox: stewart.bryant@gmail.com, agmalis@gmail.com, ibagdona.ietf@gmail.com Pages: 9 Characters: 19138 Updates: RFC 4448 I-D Tag: draft-ietf-pals-ethernet-cw-07.txt URL: https://www.rfc-editor.org/info/rfc8469 DOI: 10.17487/RFC8469 The pseudowire (PW) encapsulation of Ethernet, as defined in RFC 4448, specifies that the use of the control word (CW) is optional. In the absence of the CW, an Ethernet PW packet can be misidentified as an IP packet by a label switching router (LSR). This may lead to the selection of the wrong equal-cost multipath (ECMP) path for the packet, leading in turn to the misordering of packets. This problem has become more serious due to the deployment of equipment with Ethernet Media Access Control (MAC) addresses that start with 0x4 or 0x6. The use of the Ethernet PW CW addresses this problem. This document RECOMMENDS the use of the Ethernet PW CW in all but exceptional circumstances. This document updates RFC 4448. This document is a product of the Pseudowire And LDP-enabled Services Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Wed Nov 14 12:44: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 CD86F130F30 for ; Wed, 14 Nov 2018 12:44:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ED6iQCfq9hhL for ; Wed, 14 Nov 2018 12:44:48 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77C2B130FCE for ; Wed, 14 Nov 2018 12:44:43 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 58B23B81333; Wed, 14 Nov 2018 12:44:13 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id A436BB8132F; Wed, 14 Nov 2018 12:44:11 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20181114204411.A436BB8132F@rfc-editor.org> Date: Wed, 14 Nov 2018 12:44:11 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8491_on_Signaling_Maximum_SID_Depth_=28?= =?utf-8?q?MSD=29_Using_IS-IS?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.29 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 8491 Title: Signaling Maximum SID Depth (MSD) Using IS-IS Author: J. Tantsura, U. Chunduri, S. Aldrin, L. Ginsberg Status: Standards Track Stream: IETF Date: November 2018 Mailbox: jefftant.ietf@gmail.com, uma.chunduri@huawei.com, aldrin.ietf@gmail.com, ginsberg@cisco.com Pages: 10 Characters: 20269 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-isis-segment-routing-msd-19.txt URL: https://www.rfc-editor.org/info/rfc8491 DOI: 10.17487/RFC8491 This document defines a way for an Intermediate System to Intermediate System (IS-IS) router to advertise multiple types of supported Maximum SID Depths (MSDs) at node and/or link granularity. Such advertisements allow entities (e.g., centralized controllers) to determine whether a particular Segment ID (SID) stack can be supported in a given network. This document only defines one type of MSD: Base MPLS Imposition. However, it defines an encoding that can support other MSD types. This document focuses on MSD use in a network that is Segment Routing (SR) enabled, but MSD may also be useful when SR is not enabled. This document is a product of the Link State Routing Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Wed Nov 14 12:45: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 F2AE7130F0B for ; Wed, 14 Nov 2018 12:45:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9xvwyMJatlVt for ; Wed, 14 Nov 2018 12:45:27 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09225131000 for ; Wed, 14 Nov 2018 12:45:00 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id E296EB8134A; Wed, 14 Nov 2018 12:44:30 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 7FD64B81348; Wed, 14 Nov 2018 12:44:29 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20181114204429.7FD64B81348@rfc-editor.org> Date: Wed, 14 Nov 2018 12:44:29 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8494_on_Multicast_Email_=28MULE=29_over?= =?utf-8?q?_Allied_Communications_Publication_=28ACP=29_142?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.29 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 8494 Title: Multicast Email (MULE) over Allied Communications Publication (ACP) 142 Author: D. Wilson, A. Melnikov, Ed. Status: Informational Stream: Independent Date: November 2018 Mailbox: david.wilson@isode.com, alexey.melnikov@isode.com Pages: 19 Characters: 40384 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-melnikov-email-over-pmul-08.txt URL: https://www.rfc-editor.org/info/rfc8494 DOI: 10.17487/RFC8494 Allied Communications Publication (ACP) 142 defines P_MUL, which is a protocol for reliable multicast suitable for bandwidth-constrained and delayed acknowledgement (Emissions Control or "EMCON") environments running over UDP. This document defines MULE (Multicast Email), an application protocol for transferring Internet Mail messages (as described in RFC 5322) over P_MUL (as defined in ACP 142). MULE enables transfer between Message Transfer Agents (MTAs). It doesn't provide a service similar to SMTP Submission (as described in RFC 6409). This document explains how MULE can be used in conjunction with SMTP (RFC 5321), including some common SMTP extensions, to provide an alternate MTA-to-MTA transfer mechanism. This is not an IETF specification; it describes an existing implementation. It is provided in order to facilitate interoperable implementations and third-party diagnostics. 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 Nov 14 12:45:37 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 13EBF130FCF for ; Wed, 14 Nov 2018 12:45:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LHleIYqHlj7g for ; Wed, 14 Nov 2018 12:45:35 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CDC7C130FB7 for ; Wed, 14 Nov 2018 12:45:15 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 78085B81357; Wed, 14 Nov 2018 12:44:48 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 7ACDDB81356; Wed, 14 Nov 2018 12:44:47 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20181114204447.7ACDDB81356@rfc-editor.org> Date: Wed, 14 Nov 2018 12:44:47 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8505_on_Registration_Extensions_for_IPv?= =?utf-8?q?6_over_Low-Power_Wireless_Personal_Area_Network_=286LoWPAN=29_N?= =?utf-8?q?eighbor_Discovery?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, 6lo@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 8505 Title: Registration Extensions for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Neighbor Discovery Author: P. Thubert, Ed., E. Nordmark, S. Chakrabarti, C. Perkins Status: Standards Track Stream: IETF Date: November 2018 Mailbox: pthubert@cisco.com, nordmark@sonic.net, samitac.ietf@gmail.com, charliep@computer.org Pages: 47 Characters: 111853 Updates: RFC 6775 I-D Tag: draft-ietf-6lo-rfc6775-update-21.txt URL: https://www.rfc-editor.org/info/rfc8505 DOI: 10.17487/RFC8505 This specification updates RFC 6775 -- the Low-Power Wireless Personal Area Network (6LoWPAN) Neighbor Discovery specification -- to clarify the role of the protocol as a registration technique and simplify the registration operation in 6LoWPAN routers, as well as to provide enhancements to the registration capabilities and mobility detection for different network topologies, including the Routing Registrars performing routing for host routes and/or proxy Neighbor Discovery in a low-power network. This document is a product of the IPv6 over Networks of Resource-constrained Nodes 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 Nov 19 08:44:44 2018 Return-Path: X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF9A31286E7 for ; Mon, 19 Nov 2018 08:44:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.201 X-Spam-Level: X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1fNm2Zl3VDuw for ; Mon, 19 Nov 2018 08:44:43 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47547130DDD for ; Mon, 19 Nov 2018 08:44:43 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id DA791B80BDB; Mon, 19 Nov 2018 08:44:14 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id E3F7CB80BCE; Mon, 19 Nov 2018 08:44:13 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20181119164413.E3F7CB80BCE@rfc-editor.org> Date: Mon, 19 Nov 2018 08:44:13 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?BCP_221=2C_RFC_8521_on_Registration_Data_Ac?= =?utf-8?q?cess_Protocol_=28RDAP=29_Object_Tagging?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, regext@ietf.org, rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: rfc-dist-bounces@rfc-editor.org Sender: "rfc-dist" A new Request for Comments is now available in online RFC libraries. BCP 221 RFC 8521 Title: Registration Data Access Protocol (RDAP) Object Tagging Author: S. Hollenbeck, A. Newton Status: Best Current Practice Stream: IETF Date: November 2018 Mailbox: shollenbeck@verisign.com, andy@arin.net Pages: 13 Characters: 22381 Updates: RFC 7484 See Also: BCP 221 I-D Tag: draft-ietf-regext-rdap-object-tag-05.txt URL: https://www.rfc-editor.org/info/rfc8521 DOI: 10.17487/RFC8521 The Registration Data Access Protocol (RDAP) includes a method that can be used to identify the authoritative server for processing domain name, IP address, and autonomous system number queries. The method does not describe how to identify the authoritative server for processing other RDAP query types, such as entity queries. This limitation exists because the identifiers associated with these query types are typically unstructured. This document updates RFC 7484 by describing an operational practice that can be used to add structure to RDAP identifiers and that makes it possible to identify the authoritative server for additional RDAP queries. This document is a product of the Registration Protocols Extensions Working Group of the IETF. BCP: This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Wed Nov 21 13:46:42 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 12CE2130F26 for ; Wed, 21 Nov 2018 13:46:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.201 X-Spam-Level: X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id crfl1XE_uCwW for ; Wed, 21 Nov 2018 13:46:39 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 775C8130F1B for ; Wed, 21 Nov 2018 13:46:39 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 09763B8090D; Wed, 21 Nov 2018 13:46:09 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 1E43FB808C7; Wed, 21 Nov 2018 13:46:07 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20181121214607.1E43FB808C7@rfc-editor.org> Date: Wed, 21 Nov 2018 13:46:07 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8415_on_Dynamic_Host_Configuration_Prot?= =?utf-8?q?ocol_for_IPv6_=28DHCPv6=29?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, dhcwg@ietf.org, rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: rfc-dist-bounces@rfc-editor.org Sender: "rfc-dist" A new Request for Comments is now available in online RFC libraries. RFC 8415 Title: Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Author: T. Mrugalski, M. Siodelski, B. Volz, A. Yourtchenko, M. Richardson, S. Jiang, T. Lemon, T. Winters Status: Standards Track Stream: IETF Date: November 2018 Mailbox: tomasz.mrugalski@gmail.com, msiodelski@gmail.com, volz@cisco.com, ayourtch@cisco.com, mcr+ietf@sandelman.ca, jiangsheng@huawei.com, mellon@fugue.com, twinters@iol.unh.edu Pages: 154 Characters: 370298 Obsoletes: RFC 3315, RFC 3633, RFC 3736, RFC 4242, RFC 7083, RFC 7283, RFC 7550 I-D Tag: draft-ietf-dhc-rfc3315bis-13.txt URL: https://www.rfc-editor.org/info/rfc8415 DOI: 10.17487/RFC8415 This document describes the Dynamic Host Configuration Protocol for IPv6 (DHCPv6): an extensible mechanism for configuring nodes with network configuration parameters, IP addresses, and prefixes. Parameters can be provided statelessly, or in combination with stateful assignment of one or more IPv6 addresses and/or IPv6 prefixes. DHCPv6 can operate either in place of or in addition to stateless address autoconfiguration (SLAAC). This document updates the text from RFC 3315 (the original DHCPv6 specification) and incorporates prefix delegation (RFC 3633), stateless DHCPv6 (RFC 3736), an option to specify an upper bound for how long a client should wait before refreshing information (RFC 4242), a mechanism for throttling DHCPv6 clients when DHCPv6 service is not available (RFC 7083), and relay agent handling of unknown messages (RFC 7283). In addition, this document clarifies the interactions between models of operation (RFC 7550). As such, this document obsoletes RFC 3315, RFC 3633, RFC 3736, RFC 4242, RFC 7083, RFC 7283, and RFC 7550. This document is a product of the Dynamic Host Configuration Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Tue Nov 27 16:29:59 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 11BBD128CFD for ; Tue, 27 Nov 2018 16:29:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nfpoSCOUt2ML for ; Tue, 27 Nov 2018 16:29:58 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36BB01288EB for ; Tue, 27 Nov 2018 16:29:58 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 0D6FDB80D0E; Tue, 27 Nov 2018 16:29:56 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 1945CB80D0D; Tue, 27 Nov 2018 16:29:55 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20181128002955.1945CB80D0D@rfc-editor.org> Date: Tue, 27 Nov 2018 16:29:55 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8495_on_Allocation_Token_Extension_for_?= =?utf-8?q?the_Extensible_Provisioning_Protocol_=28EPP=29?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, regext@ietf.org, rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: rfc-dist-bounces@rfc-editor.org Sender: "rfc-dist" A new Request for Comments is now available in online RFC libraries. RFC 8495 Title: Allocation Token Extension for the Extensible Provisioning Protocol (EPP) Author: J. Gould, K. Feher Status: Standards Track Stream: IETF Date: November 2018 Mailbox: jgould@verisign.com, ietf@feherfamily.org Pages: 17 Characters: 31441 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-regext-allocation-token-12.txt URL: https://www.rfc-editor.org/info/rfc8495 DOI: 10.17487/RFC8495 This document describes an Extensible Provisioning Protocol (EPP) extension for including an Allocation Token in "query" and "transform" commands. The Allocation Token is used as a credential that authorizes a client to request the allocation of a specific object from the server using one of the EPP transform commands, including "create" and "transfer". This document is a product of the Registration Protocols Extensions Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Tue Nov 27 16:30: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 858AE130E0E for ; Tue, 27 Nov 2018 16:30:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aM963HcaLjBr for ; Tue, 27 Nov 2018 16:30:17 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66BAC130E1E for ; Tue, 27 Nov 2018 16:30:17 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id A46D1B80D1F; Tue, 27 Nov 2018 16:30:08 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 4D99BB80D1E; Tue, 27 Nov 2018 16:30:08 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20181128003008.4D99BB80D1E@rfc-editor.org> Date: Tue, 27 Nov 2018 16:30:08 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8497_on_Marking_SIP_Messages_to_Be_Logg?= =?utf-8?q?ed?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, insipid@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 8497 Title: Marking SIP Messages to Be Logged Author: P. Dawes, C. Arunachalam Status: Standards Track Stream: IETF Date: November 2018 Mailbox: peter.dawes@vodafone.com, carunach@cisco.com Pages: 46 Characters: 106572 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-insipid-logme-marking-13.txt URL: https://www.rfc-editor.org/info/rfc8497 DOI: 10.17487/RFC8497 SIP networks use signaling monitoring tools to diagnose user-reported problems and to perform regression testing if network or user agent (UA) software is upgraded. As networks grow and become interconnected, including connection via transit networks, it becomes impractical to predict the path that SIP signaling will take between user agents and therefore impractical to monitor SIP signaling end to end. This document describes an indicator for the SIP protocol that can be used to mark signaling as being of interest to logging. Such marking will typically be applied as part of network testing controlled by the network operator and is not used in normal user agent signaling. Operators of all networks on the signaling path can agree to carry such marking end to end, including the originating and terminating SIP user agents, even if a session originates and terminates in different networks. This document is a product of the INtermediary-safe SIP session ID 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 Nov 28 07:35:04 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 D8203130E4A for ; Wed, 28 Nov 2018 07:35:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.2 X-Spam-Level: X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=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 dJi9Pf2TlTCF for ; Wed, 28 Nov 2018 07:35:02 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D18CA130DCE for ; Wed, 28 Nov 2018 07:35:02 -0800 (PST) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 0DC64B80B65; Wed, 28 Nov 2018 07:35:00 -0800 (PST) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id D6CD9B80B96; Wed, 28 Nov 2018 07:34:58 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20181128153458.D6CD9B80B96@rfc-editor.org> Date: Wed, 28 Nov 2018 07:34:58 -0800 (PST) Subject: [rfc-dist] =?utf-8?q?RFC_8501_on_Reverse_DNS_in_IPv6_for_Interne?= =?utf-8?q?t_Service_Providers?= X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, dnsop@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 8501 Title: Reverse DNS in IPv6 for Internet Service Providers Author: L. Howard Status: Informational Stream: IETF Date: November 2018 Mailbox: lee.howard@retevia.net Pages: 15 Characters: 34189 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dnsop-isp-ip6rdns-07.txt URL: https://www.rfc-editor.org/info/rfc8501 DOI: 10.17487/RFC8501 In IPv4, Internet Service Providers (ISPs) commonly provide IN-ADDR.ARPA information for their customers by prepopulating the zone with one PTR record for every available address. This practice does not scale in IPv6. This document analyzes different approaches and considerations for ISPs in managing the IP6.ARPA zone. This document is a product of the Domain Name System Operations Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org