From rfc-dist-bounces@rfc-editor.org Thu Oct 6 17:34:25 2016 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 2FC62129424 for ; Thu, 6 Oct 2016 17:34:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.598 X-Spam-Level: X-Spam-Status: No, score=-105.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 lmFaNZJIqdB7 for ; Thu, 6 Oct 2016 17:34:23 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D95E21294A9 for ; Thu, 6 Oct 2016 17:34:23 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D518DB811A9; Thu, 6 Oct 2016 17:34:22 -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 C201DB811A7; Thu, 6 Oct 2016 17:34: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: <20161007003421.C201DB811A7@rfc-editor.org> Date: Thu, 6 Oct 2016 17:34:21 -0700 (PDT) Cc: drafts-update-ref@iana.org, alto@ietf.org, rfc-editor@rfc-editor.org Subject: [rfc-dist] RFC 7971 on Application-Layer Traffic Optimization (ALTO) Deployment Considerations X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 7971 Title: Application-Layer Traffic Optimization (ALTO) Deployment Considerations Author: M. Stiemerling, S. Kiesel, M. Scharf, H. Seidel, S. Previdi Status: Informational Stream: IETF Date: October 2016 Mailbox: mls.ietf@gmail.com, ietf-alto@skiesel.de, michael.scharf@nokia.com, hseidel@benocs.com, sprevidi@cisco.com Pages: 77 Characters: 188372 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-alto-deployments-16.txt URL: https://www.rfc-editor.org/info/rfc7971 DOI: http://dx.doi.org/10.17487/RFC7971 Many Internet applications are used to access resources such as pieces of information or server processes that are available in several equivalent replicas on different hosts. This includes, but is not limited to, peer-to-peer file sharing applications. The goal of Application-Layer Traffic Optimization (ALTO) is to provide guidance to applications that have to select one or several hosts from a set of candidates capable of providing a desired resource. This memo discusses deployment-related issues of ALTO. It addresses different use cases of ALTO such as peer-to-peer file sharing and Content Delivery Networks (CDNs) and presents corresponding examples. The document also includes recommendations for network administrators and application designers planning to deploy ALTO, such as recommendations on how to generate ALTO map information. This document is a product of the Application-Layer Traffic Optimization 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 Oct 6 21:47:46 2016 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 59F0A12951E for ; Thu, 6 Oct 2016 21:47:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.598 X-Spam-Level: X-Spam-Status: No, score=-105.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 N2nEfJM0SdTD for ; Thu, 6 Oct 2016 21:47: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 22BE712944C for ; Thu, 6 Oct 2016 21:47:45 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 15094B8111B; Thu, 6 Oct 2016 21:47:44 -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 D8DC2B8111A; Thu, 6 Oct 2016 21:47:42 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20161007044742.D8DC2B8111A@rfc-editor.org> Date: Thu, 6 Oct 2016 21:47:42 -0700 (PDT) Cc: drafts-update-ref@iana.org, bess@ietf.org, rfc-editor@rfc-editor.org Subject: [rfc-dist] RFC 7988 on Ingress Replication Tunnels in Multicast VPN X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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 7988 Title: Ingress Replication Tunnels in Multicast VPN Author: E. Rosen, Ed., K. Subramanian, Z. Zhang Status: Standards Track Stream: IETF Date: October 2016 Mailbox: erosen@juniper.net, karthik@sproute.com, zzhang@juniper.net Pages: 23 Characters: 55979 Updates: RFC 6513, RFC 6514 I-D Tag: draft-ietf-bess-ir-05.txt URL: https://www.rfc-editor.org/info/rfc7988 DOI: http://dx.doi.org/10.17487/RFC7988 RFCs 6513, 6514, and other RFCs describe procedures by which a Service Provider may offer Multicast VPN (MVPN) service to its customers. These procedures create point-to-multipoint (P2MP) or multipoint-to-multipoint (MP2MP) trees across the Service Provider's backbone. One type of P2MP tree that may be used is known as an "Ingress Replication (IR) tunnel". In an IR tunnel, a parent node need not be directly connected to its child nodes. When a parent node has to send a multicast data packet to its n child nodes, it does not use Layer 2 multicast, IP multicast, or MPLS multicast to do so. Rather, it makes n individual copies, and then unicasts each copy, through an IP or MPLS unicast tunnel, to exactly one child node. While the prior MVPN specifications allow the use of IR tunnels, those specifications are not always very clear or explicit about how the MVPN protocol elements and procedures are applied to IR tunnels. This document updates RFCs 6513 and 6514 by adding additional details that are specific to the use of IR tunnels. This document is a product of the BGP Enabled Services Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Thu Oct 13 20:53:36 2016 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 84FF31295C8 for ; Thu, 13 Oct 2016 20:53:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.598 X-Spam-Level: X-Spam-Status: No, score=-105.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 W7kEkciDAUOQ for ; Thu, 13 Oct 2016 20:53:35 -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 114051295B0 for ; Thu, 13 Oct 2016 20:53:35 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 16FD0B81B6F; Thu, 13 Oct 2016 20:53: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 BE0CEB81B6E; Thu, 13 Oct 2016 20:53: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: <20161014035332.BE0CEB81B6E@rfc-editor.org> Date: Thu, 13 Oct 2016 20:53:32 -0700 (PDT) Subject: [rfc-dist] RFC 7975 on Request Routing Redirection Interface for Content Delivery Network (CDN) Interconnection X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, cdni@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 7975 Title: Request Routing Redirection Interface for Content Delivery Network (CDN) Interconnection Author: B. Niven-Jenkins, Ed., R. van Brandenburg, Ed. Status: Standards Track Stream: IETF Date: October 2016 Mailbox: ben.niven-jenkins@nokia.com, ray.vanbrandenburg@tno.nl Pages: 35 Characters: 75830 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-cdni-redirection-20.txt URL: https://www.rfc-editor.org/info/rfc7975 DOI: http://dx.doi.org/10.17487/RFC7975 The Request Routing interface comprises (1) the asynchronous advertisement of footprint and capabilities by a downstream Content Delivery Network (CDN) that allows an upstream CDN to decide whether to redirect particular user requests to that downstream CDN; and (2) the synchronous operation of an upstream CDN requesting whether a downstream CDN is prepared to accept a user request and of a downstream CDN responding with how to actually redirect the user request. This document describes an interface for the latter part, i.e., the CDNI Request Routing Redirection interface. This document is a product of the Content Delivery Networks Interconnection 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 Oct 14 16:36:31 2016 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 5A5E6129603 for ; Fri, 14 Oct 2016 16:36:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.598 X-Spam-Level: X-Spam-Status: No, score=-105.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 4cwG3pZEqQXx for ; Fri, 14 Oct 2016 16:36:29 -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 928DD127ABE for ; Fri, 14 Oct 2016 16:36:29 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 91578B80929; Fri, 14 Oct 2016 16:36:28 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 15005B8090E; Fri, 14 Oct 2016 16:36:27 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20161014233627.15005B8090E@rfc-editor.org> Date: Fri, 14 Oct 2016 16:36:27 -0700 (PDT) Subject: [rfc-dist] RFC 8002 on Host Identity Protocol Certificates X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, hipsec@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 8002 Title: Host Identity Protocol Certificates Author: T. Heer, S. Varjonen Status: Standards Track Stream: IETF Date: October 2016 Mailbox: heer@hs-albsig.de, samu.varjonen@helsinki.fi Pages: 13 Characters: 26613 Obsoletes: RFC 6253 Updates: RFC 7401 I-D Tag: draft-ietf-hip-rfc6253-bis-09.txt URL: https://www.rfc-editor.org/info/rfc8002 DOI: http://dx.doi.org/10.17487/RFC8002 The Certificate (CERT) parameter is a container for digital certificates. It is used for carrying these certificates in Host Identity Protocol (HIP) control packets. This document specifies the certificate parameter and the error signaling in case of a failed verification. Additionally, this document specifies the representations of Host Identity Tags (HITs) in X.509 version 3 (v3). The concrete use cases of certificates, including how certificates are obtained and requested and which actions are taken upon successful or failed verification, are specific to the scenario in which the certificates are used. Hence, the definition of these scenario-specific aspects is left to the documents that use the CERT parameter. This document updates RFC 7401 and obsoletes RFC 6253. This document is a product of the Host Identity Protocol 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 Oct 14 16:37:00 2016 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 D1CE11296B3 for ; Fri, 14 Oct 2016 16:37:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.598 X-Spam-Level: X-Spam-Status: No, score=-105.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 1H6htX0ximCr for ; Fri, 14 Oct 2016 16:36: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 E6D7312944B for ; Fri, 14 Oct 2016 16:36:47 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 274ECB809DC; Fri, 14 Oct 2016 16:36:41 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 162EFB809D9; Fri, 14 Oct 2016 16:36:40 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20161014233640.162EFB809D9@rfc-editor.org> Date: Fri, 14 Oct 2016 16:36:40 -0700 (PDT) Subject: [rfc-dist] RFC 8003 on Host Identity Protocol (HIP) Registration Extension X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, hipsec@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 8003 Title: Host Identity Protocol (HIP) Registration Extension Author: J. Laganier, L. Eggert Status: Standards Track Stream: IETF Date: October 2016 Mailbox: julien.ietf@gmail.com, lars@netapp.com Pages: 16 Characters: 34717 Obsoletes: RFC 5203 I-D Tag: draft-ietf-hip-rfc5203-bis-11.txt URL: https://www.rfc-editor.org/info/rfc8003 DOI: http://dx.doi.org/10.17487/RFC8003 This document specifies a registration mechanism for the Host Identity Protocol (HIP) that allows hosts to register with services, such as HIP rendezvous servers or middleboxes. This document obsoletes RFC 5203. This document is a product of the Host Identity Protocol 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 Oct 14 16:37:19 2016 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 7BD5A129899 for ; Fri, 14 Oct 2016 16:37:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.598 X-Spam-Level: X-Spam-Status: No, score=-105.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 4pX2zWjtnjRz for ; Fri, 14 Oct 2016 16:37: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 ED47D129696 for ; Fri, 14 Oct 2016 16:37:02 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 6CF03B80AA4; Fri, 14 Oct 2016 16:36: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 B655FB80A26; Fri, 14 Oct 2016 16:36: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: <20161014233653.B655FB80A26@rfc-editor.org> Date: Fri, 14 Oct 2016 16:36:53 -0700 (PDT) Subject: [rfc-dist] RFC 8004 on Host Identity Protocol (HIP) Rendezvous Extension X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, hipsec@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 8004 Title: Host Identity Protocol (HIP) Rendezvous Extension Author: J. Laganier, L. Eggert Status: Standards Track Stream: IETF Date: October 2016 Mailbox: julien.ietf@gmail.com, lars@netapp.com Pages: 14 Characters: 30487 Obsoletes: RFC 5204 I-D Tag: draft-ietf-hip-rfc5204-bis-08.txt URL: https://www.rfc-editor.org/info/rfc8004 DOI: http://dx.doi.org/10.17487/RFC8004 This document defines a rendezvous extension for the Host Identity Protocol (HIP). The rendezvous extension extends HIP and the HIP Registration Extension for initiating communication between HIP nodes via HIP rendezvous servers. Rendezvous servers improve reachability and operation when HIP nodes are multihomed or mobile. This document obsoletes RFC 5204. This document is a product of the Host Identity Protocol 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 Oct 14 16:37:46 2016 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 C87F71298DD for ; Fri, 14 Oct 2016 16:37:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.598 X-Spam-Level: X-Spam-Status: No, score=-105.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 lYjH-Df_z_ll for ; Fri, 14 Oct 2016 16:37: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 D025D12988E for ; Fri, 14 Oct 2016 16:37:18 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id EDBDEB80B36; Fri, 14 Oct 2016 16:37:07 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id B24D6B80AA8; Fri, 14 Oct 2016 16:37: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: <20161014233706.B24D6B80AA8@rfc-editor.org> Date: Fri, 14 Oct 2016 16:37:06 -0700 (PDT) Subject: [rfc-dist] RFC 8005 on Host Identity Protocol (HIP) Domain Name System (DNS) Extension X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, hipsec@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 8005 Title: Host Identity Protocol (HIP) Domain Name System (DNS) Extension Author: J. Laganier Status: Standards Track Stream: IETF Date: October 2016 Mailbox: julien.ietf@gmail.com Pages: 18 Characters: 39146 Obsoletes: RFC 5205 I-D Tag: draft-ietf-hip-rfc5205-bis-10.txt URL: https://www.rfc-editor.org/info/rfc8005 DOI: http://dx.doi.org/10.17487/RFC8005 This document specifies a resource record (RR) for the Domain Name System (DNS) and how to use it with the Host Identity Protocol (HIP). This RR allows a HIP node to store in the DNS its Host Identity (HI), the public component of the node public-private key pair; its Host Identity Tag (HIT), a truncated hash of its public key (PK); and the domain names of its rendezvous servers (RVSs). This document obsoletes RFC 5205. This document is a product of the Host Identity Protocol 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 Oct 14 20:15:34 2016 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 BF29112958B for ; Fri, 14 Oct 2016 20:15:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.598 X-Spam-Level: X-Spam-Status: No, score=-105.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 76b-yXo2Hm_C for ; Fri, 14 Oct 2016 20:15:33 -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 A25B2129405 for ; Fri, 14 Oct 2016 20:15:32 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id B2934B8208D; Fri, 14 Oct 2016 20:15:31 -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 1755CB8208C; Fri, 14 Oct 2016 20:15:31 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20161015031531.1755CB8208C@rfc-editor.org> Date: Fri, 14 Oct 2016 20:15:31 -0700 (PDT) Subject: [rfc-dist] RFC 7904 on A SIP Usage for REsource LOcation And Discovery (RELOAD) X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, p2psip@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 7904 Title: A SIP Usage for REsource LOcation And Discovery (RELOAD) Author: C. Jennings, B. Lowekamp, E. Rescorla, S. Baset, H. Schulzrinne, T. Schmidt, Ed. Status: Standards Track Stream: IETF Date: October 2016 Mailbox: fluffy@cisco.com, bbl@lowekamp.net, ekr@rtfm.com, sabaset@us.ibm.com, hgs@cs.columbia.edu, t.schmidt@haw-hamburg.de Pages: 20 Characters: 41978 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-p2psip-sip-21.txt URL: https://www.rfc-editor.org/info/rfc7904 DOI: http://dx.doi.org/10.17487/RFC7904 This document defines a SIP Usage for REsource LOcation And Discovery (RELOAD). The SIP Usage provides the functionality of a SIP proxy or registrar in a fully distributed system and includes a lookup service for Address of Records (AORs) stored in the overlay. It also defines Globally Routable User Agent URIs (GRUUs) that allow the registrations to map an AOR to a specific node reachable through the overlay. After such initial contact of a Peer, the RELOAD AppAttach method is used to establish a direct connection between nodes through which SIP messages are exchanged. This document is a product of the Peer-to-Peer Session Initiation Protocol 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 Oct 19 17:16:26 2016 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 D9E931294AD for ; Wed, 19 Oct 2016 17:16:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.033 X-Spam-Level: X-Spam-Status: No, score=-103.033 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 wANjlr7HijxZ for ; Wed, 19 Oct 2016 17:16: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 38C2B1293EB for ; Wed, 19 Oct 2016 17:16:25 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5A0C1B80143; Wed, 19 Oct 2016 17:16:24 -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 4597DB80141; Wed, 19 Oct 2016 17:16: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: <20161020001622.4597DB80141@rfc-editor.org> Date: Wed, 19 Oct 2016 17:16:22 -0700 (PDT) Subject: [rfc-dist] RFC 7969 on Customizing DHCP Configuration on the Basis of Network Topology X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.21 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 7969 Title: Customizing DHCP Configuration on the Basis of Network Topology Author: T. Lemon, T. Mrugalski Status: Informational Stream: IETF Date: October 2016 Mailbox: ted.lemon@nominum.com, tomasz.mrugalski@gmail.com Pages: 20 Characters: 46674 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dhc-topo-conf-09.txt URL: https://www.rfc-editor.org/info/rfc7969 DOI: http://dx.doi.org/10.17487/RFC7969 DHCP servers have evolved over the years to provide significant functionality beyond that described in the DHCP base specifications. One aspect of this functionality is support for context-specific configuration information. This memo describes some such features and explains their operation. This document is a product of the Dynamic Host Configuration 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 Oct 19 17:17:02 2016 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 61DAB129867 for ; Wed, 19 Oct 2016 17:17:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.033 X-Spam-Level: X-Spam-Status: No, score=-103.033 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 sMKLSRmr0IVR for ; Wed, 19 Oct 2016 17:16: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 E9322129862 for ; Wed, 19 Oct 2016 17:16:46 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id CB9D6B8014D; Wed, 19 Oct 2016 17:16:46 -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 10B1AB8014C; Wed, 19 Oct 2016 17:16:46 -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: <20161020001646.10B1AB8014C@rfc-editor.org> Date: Wed, 19 Oct 2016 17:16:46 -0700 (PDT) Subject: [rfc-dist] RFC 7974 on An Experimental TCP Option for Host Identification X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.21 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 7974 Title: An Experimental TCP Option for Host Identification Author: B. Williams, M. Boucadair, D. Wing Status: Experimental Stream: Independent Date: October 2016 Mailbox: brandon.williams@akamai.com, mohamed.boucadair@orange.com, dwing-ietf@fuggles.com Pages: 20 Characters: 48381 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-williams-exp-tcp-host-id-opt-08.txt URL: https://www.rfc-editor.org/info/rfc7974 DOI: http://dx.doi.org/10.17487/RFC7974 Recent RFCs have discussed issues with host identification in IP address-sharing systems, such as address/prefix-sharing devices and application-layer proxies. Potential solutions for revealing a host identifier in shared address deployments have also been discussed. This memo describes the design, deployment, and privacy considerations for one such solution in operational use on the Internet today that uses a TCP option to transmit a host identifier. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Wed Oct 19 17:17:25 2016 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 C645212986F for ; Wed, 19 Oct 2016 17:17:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.033 X-Spam-Level: X-Spam-Status: No, score=-103.033 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 JHdaoZo90ycW for ; Wed, 19 Oct 2016 17:17:24 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4985129856 for ; Wed, 19 Oct 2016 17:17:01 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 6A3F5B80157; Wed, 19 Oct 2016 17:17:01 -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 2B228B80155; Wed, 19 Oct 2016 17:17:00 -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: <20161020001700.2B228B80155@rfc-editor.org> Date: Wed, 19 Oct 2016 17:17:00 -0700 (PDT) Subject: [rfc-dist] RFC 7981 on IS-IS Extensions for Advertising Router Information X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, isis-wg@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 7981 Title: IS-IS Extensions for Advertising Router Information Author: L. Ginsberg, S. Previdi, M. Chen Status: Standards Track Stream: IETF Date: October 2016 Mailbox: ginsberg@cisco.com, sprevidi@cisco.com, mach.chen@huawei.com Pages: 10 Characters: 20235 Obsoletes: RFC 4971 I-D Tag: draft-ietf-isis-rfc4971bis-04.txt URL: https://www.rfc-editor.org/info/rfc7981 DOI: http://dx.doi.org/10.17487/RFC7981 This document defines a new optional Intermediate System to Intermediate System (IS-IS) TLV named CAPABILITY, formed of multiple sub-TLVs, which allows a router to announce its capabilities within an IS-IS level or the entire routing domain. This document obsoletes RFC 4971. This document is a product of the IS-IS for IP Internets 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 Oct 19 17:17:55 2016 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 B9205129867 for ; Wed, 19 Oct 2016 17:17:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.033 X-Spam-Level: X-Spam-Status: No, score=-103.033 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 ruWLXcIREaGY for ; Wed, 19 Oct 2016 17:17:46 -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 293FB1294C2 for ; Wed, 19 Oct 2016 17:17:20 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id E010EB8015D; Wed, 19 Oct 2016 17:17:19 -0700 (PDT) X-Original-To: rfc-dist@rfc-editor.org Delivered-To: rfc-dist@rfc-editor.org Received: by rfc-editor.org (Postfix, from userid 30) id 94777B8015C; Wed, 19 Oct 2016 17:17:18 -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: <20161020001718.94777B8015C@rfc-editor.org> Date: Wed, 19 Oct 2016 17:17:18 -0700 (PDT) Subject: [rfc-dist] RFC 7987 on IS-IS Minimum Remaining Lifetime X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, isis-wg@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 7987 Title: IS-IS Minimum Remaining Lifetime Author: L. Ginsberg, P. Wells, B. Decraene, T. Przygienda, H. Gredler Status: Standards Track Stream: IETF Date: October 2016 Mailbox: ginsberg@cisco.com, pauwells@cisco.com, bruno.decraene@orange.com, prz@juniper.net, hannes@rtbrick.com Pages: 9 Characters: 18295 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-isis-remaining-lifetime-04.txt URL: https://www.rfc-editor.org/info/rfc7987 DOI: http://dx.doi.org/10.17487/RFC7987 Corruption of the Remaining Lifetime field in a Link State Protocol Data Unit (LSP) can go undetected. In certain scenarios, this may cause or exacerbate flooding storms. It is also a possible denial-of-service attack vector. This document defines a backwards-compatible solution to this problem. This document is a product of the IS-IS for IP Internets 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 Oct 19 17:18:28 2016 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 AFF06129876 for ; Wed, 19 Oct 2016 17:18:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.033 X-Spam-Level: X-Spam-Status: No, score=-103.033 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 8UyDt8_74Chy for ; Wed, 19 Oct 2016 17:18:16 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A67E129880 for ; Wed, 19 Oct 2016 17:17:35 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 745B6B80167; Wed, 19 Oct 2016 17:17:31 -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 2465BB80164; Wed, 19 Oct 2016 17:17:30 -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: <20161020001730.2465BB80164@rfc-editor.org> Date: Wed, 19 Oct 2016 17:17:30 -0700 (PDT) Subject: [rfc-dist] RFC 7989 on End-to-End Session Identification in IP-Based Multimedia Communication Networks X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.21 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 7989 Title: End-to-End Session Identification in IP-Based Multimedia Communication Networks Author: P. Jones, G. Salgueiro, C. Pearce, P. Giralt Status: Standards Track Stream: IETF Date: October 2016 Mailbox: paulej@packetizer.com, gsalguei@cisco.com, chrep@cisco.com, pgiralt@cisco.com Pages: 45 Characters: 103241 Obsoletes: RFC 7329 I-D Tag: draft-ietf-insipid-session-id-27.txt URL: https://www.rfc-editor.org/info/rfc7989 DOI: http://dx.doi.org/10.17487/RFC7989 This document describes an end-to-end session identifier for use in IP-based multimedia communication systems that enables endpoints, intermediary devices, and management systems to identify a session end-to-end, associate multiple endpoints with a given multipoint conference, track communication sessions when they are redirected, and associate one or more media flows with a given communication session. While the identifier is intended to work across multiple protocols, this document describes its usage in the Session Initiation Protocol (SIP). This document also describes a backwards-compatibility mechanism for an existing session identifier implementation (RFC 7329) that is sufficiently different from the procedures defined in this document. This document obsoletes RFC 7329. 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 Oct 19 17:19:02 2016 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 B13E71293EB for ; Wed, 19 Oct 2016 17:19:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.033 X-Spam-Level: X-Spam-Status: No, score=-103.033 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 vha50WYwdfap for ; Wed, 19 Oct 2016 17:19:01 -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 3BC91129887 for ; Wed, 19 Oct 2016 17:17:50 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id ED5B2B80169; Wed, 19 Oct 2016 17:17:42 -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 F3FC1B8016A; Wed, 19 Oct 2016 17:17: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: <20161020001741.F3FC1B8016A@rfc-editor.org> Date: Wed, 19 Oct 2016 17:17:41 -0700 (PDT) Subject: [rfc-dist] RFC 7999 on BLACKHOLE Community X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, grow@ietf.org, rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: rfc-dist-bounces@rfc-editor.org Sender: "rfc-dist" A new Request for Comments is now available in online RFC libraries. RFC 7999 Title: BLACKHOLE Community Author: T. King, C. Dietzel, J. Snijders, G. Doering, G. Hankins Status: Informational Stream: IETF Date: October 2016 Mailbox: thomas.king@de-cix.net, christoph.dietzel@de-cix.net, job@ntt.net, gert@space.net, greg.hankins@nokia.com Pages: 9 Characters: 16794 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-grow-blackholing-03.txt URL: https://www.rfc-editor.org/info/rfc7999 DOI: http://dx.doi.org/10.17487/RFC7999 This document describes the use of a well-known Border Gateway Protocol (BGP) community for destination-based blackholing in IP networks. This well-known advisory transitive BGP community named "BLACKHOLE" allows an origin Autonomous System (AS) to specify that a neighboring network should discard any traffic destined towards the tagged IP prefix. This document is a product of the Global Routing Operations Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC _______________________________________________ rfc-dist mailing list rfc-dist@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-dist http://www.rfc-editor.org From rfc-dist-bounces@rfc-editor.org Fri Oct 21 12:09:43 2016 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 04C931298A9 for ; Fri, 21 Oct 2016 12:09:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.033 X-Spam-Level: X-Spam-Status: No, score=-103.033 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 pYborVeTiAUI for ; Fri, 21 Oct 2016 12:09:41 -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 B194A1297D4 for ; Fri, 21 Oct 2016 12:09:41 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id C4C5EB820EF; Fri, 21 Oct 2016 12:09:40 -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 4FEB4B820EE; Fri, 21 Oct 2016 12:09:40 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20161021190940.4FEB4B820EE@rfc-editor.org> Date: Fri, 21 Oct 2016 12:09:40 -0700 (PDT) Subject: [rfc-dist] RFC 7980 on A Framework for Defining Network Complexity X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.21 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 7980 Title: A Framework for Defining Network Complexity Author: M. Behringer, A. Retana, R. White, G. Huston Status: Informational Stream: Independent Date: October 2016 Mailbox: mbehring@cisco.com, aretana@cisco.com, russw@riw.us, gih@apnic.net Pages: 24 Characters: 56510 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-behringer-ncrg-complexity-framework-02.txt URL: https://www.rfc-editor.org/info/rfc7980 DOI: http://dx.doi.org/10.17487/RFC7980 Complexity is a widely used parameter in network design, yet there is no generally accepted definition of the term. Complexity metrics exist in a wide range of research papers, but most of these address only a particular aspect of a network, for example, the complexity of a graph or software. While it may be impossible to define a metric for overall network complexity, there is a desire to better understand the complexity of a network as a whole, as deployed today to provide Internet services. This document provides a framework to guide research on the topic of network complexity as well as some practical examples for trade-offs in networking. This document summarizes the work of the IRTF's Network Complexity Research Group (NCRG) at the time of its closure. It does not present final results, but a snapshot of an ongoing activity, as a basis for future work. 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 Oct 27 22:29:25 2016 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 A47381294F0 for ; Thu, 27 Oct 2016 22:29:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.033 X-Spam-Level: X-Spam-Status: No, score=-103.033 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 nRgEsqfpjrxu for ; Thu, 27 Oct 2016 22:29:23 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E027D129466 for ; Thu, 27 Oct 2016 22:29:23 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id EDEA7B8120D; Thu, 27 Oct 2016 22:29:22 -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 42BE4B811A9; Thu, 27 Oct 2016 22:29: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: <20161028052921.42BE4B811A9@rfc-editor.org> Date: Thu, 27 Oct 2016 22:29:21 -0700 (PDT) Subject: [rfc-dist] RFC 7986 on New Properties for iCalendar X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: RFC Announcements List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: drafts-update-ref@iana.org, calsify@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 7986 Title: New Properties for iCalendar Author: C. Daboo Status: Standards Track Stream: IETF Date: October 2016 Mailbox: cyrus@daboo.name Pages: 23 Characters: 45686 Updates: RFC 5545 I-D Tag: draft-ietf-calext-extensions-05.txt URL: https://www.rfc-editor.org/info/rfc7986 DOI: http://dx.doi.org/10.17487/RFC7986 This document defines a set of new properties for iCalendar data and extends the use of some existing properties to the entire iCalendar object. This document is a product of the Calendaring 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 Thu Oct 27 22:30:07 2016 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 DD4011294F2 for ; Thu, 27 Oct 2016 22:30:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.033 X-Spam-Level: X-Spam-Status: No, score=-103.033 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.431, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 wDnE9OIt_uiK for ; Thu, 27 Oct 2016 22:29:56 -0700 (PDT) Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 853BF1296A8 for ; Thu, 27 Oct 2016 22:29:44 -0700 (PDT) Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 83A20B81238; Thu, 27 Oct 2016 22:29:36 -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 DD790B81236; Thu, 27 Oct 2016 22:29: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: <20161028052935.DD790B81236@rfc-editor.org> Date: Thu, 27 Oct 2016 22:29:35 -0700 (PDT) Subject: [rfc-dist] RFC 8009 on AES Encryption with HMAC-SHA2 for Kerberos 5 X-BeenThere: rfc-dist@rfc-editor.org X-Mailman-Version: 2.1.21 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 8009 Title: AES Encryption with HMAC-SHA2 for Kerberos 5 Author: M. Jenkins, M. Peck, K. Burgin Status: Informational Stream: IETF Date: October 2016 Mailbox: mjjenki@tycho.ncsc.mil, mpeck@mitre.org, kelley.burgin@gmail.com Pages: 19 Characters: 34935 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-kitten-aes-cts-hmac-sha2-11.txt URL: https://www.rfc-editor.org/info/rfc8009 DOI: http://dx.doi.org/10.17487/RFC8009 This document specifies two encryption types and two corresponding checksum types for Kerberos 5. The new types use AES in CTS mode (CBC mode with ciphertext stealing) for confidentiality and HMAC with a SHA-2 hash for integrity. This document is a product of the Common Authentication Technology Next Generation 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