From nobody Tue Aug 7 17:33:04 2018 Return-Path: X-Original-To: sidr@ietfa.amsl.com Delivered-To: sidr@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49448130DC4; Tue, 7 Aug 2018 17:33:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Un9pmi32s1Kv; Tue, 7 Aug 2018 17:33:00 -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 4CA3B130DC0; Tue, 7 Aug 2018 17:33:00 -0700 (PDT) Received: by rfc-editor.org (Postfix, from userid 30) id 9C4BBB81879; Tue, 7 Aug 2018 17:32:56 -0700 (PDT) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, sidr@ietf.org Content-type: text/plain; charset=UTF-8 Message-Id: <20180808003256.9C4BBB81879@rfc-editor.org> Date: Tue, 7 Aug 2018 17:32:56 -0700 (PDT) Archived-At: Subject: [sidr] =?utf-8?q?RFC_8416_on_Simplified_Local_Internet_Number_Re?= =?utf-8?q?source_Management_with_the_RPKI_=28SLURM=29?= X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Aug 2018 00:33:02 -0000 A new Request for Comments is now available in online RFC libraries. RFC 8416 Title: Simplified Local Internet Number Resource Management with the RPKI (SLURM) Author: D. Ma, D. Mandelberg, T. Bruijnzeels Status: Standards Track Stream: IETF Date: August 2018 Mailbox: madi@zdns.cn, david@mandelberg.org, tim@nlnetlabs.nl Pages: 17 Characters: 34613 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-sidr-slurm-08.txt URL: https://www.rfc-editor.org/info/rfc8416 DOI: 10.17487/RFC8416 The Resource Public Key Infrastructure (RPKI) is a global authorization infrastructure that allows the holder of Internet Number Resources (INRs) to make verifiable statements about those resources. Network operators, e.g., Internet Service Providers (ISPs), can use the RPKI to validate BGP route origin assertions. ISPs can also use the RPKI to validate the path of a BGP route. However, ISPs may want to establish a local view of exceptions to the RPKI data in the form of local filters and additions. The mechanisms described in this document provide a simple way to enable INR holders to establish a local, customized view of the RPKI, overriding global RPKI repository data as needed. This document is a product of the Secure Inter-Domain 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 From nobody Thu Aug 9 14:40:40 2018 Return-Path: X-Original-To: sidr@ietfa.amsl.com Delivered-To: sidr@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6742C130EF0 for ; Thu, 9 Aug 2018 14:40:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 snBgt9ZKIFnv for ; Thu, 9 Aug 2018 14:40:36 -0700 (PDT) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E72E130EF3 for ; Thu, 9 Aug 2018 14:40:35 -0700 (PDT) Received: by mail-wm0-x22c.google.com with SMTP id y2-v6so44589wma.1 for ; Thu, 09 Aug 2018 14:40:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=WTnIn2MToozrEJ5A7HdvNEwkVkJ3Hw600qtapQFg8kI=; b=NtVvOCSdr143z+MYKJc7bHylPDyosN8Kp6SXD+eeGFQ3IsEJtbPGeAJTuPi/eFdxuW XJRi2yDeYFJb+PtKAGkZRO4X6XMcqG+kjM1y7cdWZOSw0rGYDcME00vozzimn/CqAbDc eT4r7298z/HAgpcL5Qk3QfjHixdXz/PAwr1N1MI6VVTKEd3Dnhn0X9lvOmaSWI/b7E71 Os4j3O9h9jeY5kdA3/c4/lh12eD2zrPA271M094M9bqsaKzrjbJsXPrFpR1yI9dblkTF B5sx6pequgS2RW1hZ7E72cijJCmBcG/xI9CZDxt8UXrxgTT3onh4OYV6DNfeoevbxthK JjcQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=WTnIn2MToozrEJ5A7HdvNEwkVkJ3Hw600qtapQFg8kI=; b=X4KaGwcQqpABDn7JIt/C4FkPSeMGXfChPr79Pujof8JzdU9Z2U5yvTyO1rSO0Ihf9C m7jvgC+KIWfEpRhJWnWHz4pa/wMa0Kfo3BUfwF85udgIQZhcAhN2wcYf2IzPsk6M/YBg riYkduCAZeY2uKMCNDERGbBQeNDJVaZ2kjLPABaZo9Tj+jYeWdAVX2ADDNirL+ymKX1s 6F2ZVS5/RVgAZTa/jf9joerXrbJ4DE1umyxBO4C9xI4fXGMilOfHOEyAJLia3SQK7wud AQtDPou7PiNJFIzF6PsumBx6ejzM8psKGqqIL0AASMfdpADFDpRialkBREudH6LBRrWa 51uA== X-Gm-Message-State: AOUpUlEv5jIlcsLqu5OeOiHNez3IHWKLtH1QS75hb5xaOD3Guwv4TOZa +1WddWpMyV8Thxlbkbg8K0ePiT56joT8upGhjAvqO0px X-Google-Smtp-Source: AA+uWPwHtO2lwaY/YG6XKilVujtJ9QGK43yHGkx6L/1LJIgyQlHAZHYWs6EW8ECWhP3K6cK9pwiqlE5SnCStcva0y84= X-Received: by 2002:a1c:70b:: with SMTP id 11-v6mr10546wmh.151.1533850834066; Thu, 09 Aug 2018 14:40:34 -0700 (PDT) MIME-Version: 1.0 From: Alberto Leiva Date: Thu, 9 Aug 2018 16:40:23 -0500 Message-ID: To: sidr@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: [sidr] Endianness of RTR X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Aug 2018 21:40:38 -0000 Hi Please forgive me if this is a stupid question, but What is the endianness of the RTR protocol? (RFCs 6810 and 8210) And why does it seem like it's not specified in the RFCs? Thanks Alberto From nobody Fri Aug 10 11:12:21 2018 Return-Path: X-Original-To: sidr@ietfa.amsl.com Delivered-To: sidr@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03DBC130E69 for ; Fri, 10 Aug 2018 11:12:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.511 X-Spam-Level: X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com 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 IV3u-4BY3bXV for ; Fri, 10 Aug 2018 11:12:17 -0700 (PDT) Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19E201292AD for ; Fri, 10 Aug 2018 11:12:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=763; q=dns/txt; s=iport; t=1533924737; x=1535134337; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=HeMHTqKgP8eUiluGdM7xWFISAWQiMePEBdIVsNd7F/8=; b=DtJIQYWU9Ue0SaFnWoT0ls8g3LgPpIxARiFzaQ/r7GltI04Ri2oRD+qa ozqslJvGrAYPI4xfu51ufI5wqsgBrlL5Bs+/iXWf60Kktq/vmJXLlxSa5 OKWm0WblnfjlDyF+A29V+E6ichoKWpc8zqvAAEmtmCB48dXjSpMcPOk1f g=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DqAAAy1G1b/5xdJa1dGgEBAQEBAgE?= =?us-ascii?q?BAQEIAQEBAYNOY38oCotgjDiCDZYAgXoLGAuESQKDKCE0GAECAQECAQECbRw?= =?us-ascii?q?MhTcBAQEBAwEBODQXBAIBCA4DBAEBHxAnCx0IAgQBEgiDGYIAD60IilEFiRQ?= =?us-ascii?q?XgUE/hCSDGwEBA4c0AppWCQKGHoJvhjqBVoQqiD2KfodhAhEUgSQdOCaBLHA?= =?us-ascii?q?VO4JpixWFPm+NKYEbAQE?= X-IronPort-AV: E=Sophos;i="5.53,220,1531785600"; d="scan'208";a="218430794" Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Aug 2018 18:12:16 +0000 Received: from XCH-ALN-015.cisco.com (xch-aln-015.cisco.com [173.36.7.25]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id w7AICGCQ010328 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 10 Aug 2018 18:12:16 GMT Received: from xch-aln-014.cisco.com (173.36.7.24) by XCH-ALN-015.cisco.com (173.36.7.25) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 10 Aug 2018 13:12:15 -0500 Received: from xch-aln-014.cisco.com ([173.36.7.24]) by XCH-ALN-014.cisco.com ([173.36.7.24]) with mapi id 15.00.1320.000; Fri, 10 Aug 2018 13:12:15 -0500 From: "Jakob Heitz (jheitz)" To: Alberto Leiva , "sidr@ietf.org" Thread-Topic: [sidr] Endianness of RTR Thread-Index: AQHUMCmkuAATLMCUvESjFS1ORSuzrqS5SmSQ Date: Fri, 10 Aug 2018 18:12:15 +0000 Message-ID: <6cd7812883d64d65b94151f6b14e3ab9@XCH-ALN-014.cisco.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.32.198.216] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Outbound-SMTP-Client: 173.36.7.25, xch-aln-015.cisco.com X-Outbound-Node: rcdn-core-5.cisco.com Archived-At: Subject: Re: [sidr] Endianness of RTR X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Aug 2018 18:12:19 -0000 It's actually a good question, because it highlights that we don't even thi= nk about this anymore. Perhaps https://tools.ietf.org/html/draft-newman-network-byte-order-01 should be advanced to RFC. A: Big Endian. Regards, Jakob. -----Original Message----- From: sidr On Behalf Of Alberto Leiva Sent: Thursday, August 9, 2018 2:40 PM To: sidr@ietf.org Subject: [sidr] Endianness of RTR Hi Please forgive me if this is a stupid question, but What is the endianness of the RTR protocol? (RFCs 6810 and 8210) And why does it seem like it's not specified in the RFCs? Thanks Alberto _______________________________________________ sidr mailing list sidr@ietf.org https://www.ietf.org/mailman/listinfo/sidr From nobody Fri Aug 10 11:50:03 2018 Return-Path: X-Original-To: sidr@ietfa.amsl.com Delivered-To: sidr@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D87631310AF for ; Fri, 10 Aug 2018 11:49:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com 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 cJhLp2mCMs3e for ; Fri, 10 Aug 2018 11:49:57 -0700 (PDT) Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA12013106E for ; Fri, 10 Aug 2018 11:49:56 -0700 (PDT) Received: by mail-wr1-x436.google.com with SMTP id v14-v6so9118778wro.5 for ; Fri, 10 Aug 2018 11:49:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Fy7o9nznSkcVeKwuKitVVUYojXgc24XxL32rwThRiMI=; b=Y/g6aGB4QzD3zih4kb2KhcEVwOPt/RyAElPgUtYSmCil8Uvex+ecsx3gZCwTxXeN6a tRO6nkUv6AhzDptPHxkvGMvvVhjpEPhP80Q+GaX65hqu5lo0Ik2mIT1rk2CSEbc7Ct3C QFSC9UQz9DR2YM5xgSso3PwTffO+sSTmafELanreFuERKDG4qPjL3l73mLOO3TrpdoVt jNCa+ZQF9V/i/cozitPgJZA3C0mNHCx1erO0uAMXGlfOk+ekVL8cniJ0vaTzW520QYyX KLpA//XSQvrVn4HRNMlGBTo0pvcYUiM05jEhKodbQCyawzrINHt4ZqK+e1pt8+o8iAct QH4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Fy7o9nznSkcVeKwuKitVVUYojXgc24XxL32rwThRiMI=; b=JX2snWOxO7WBRub7qt7gLDvadMrBPauJxsIHIH51IOU0MkMhbG71lszPYlwmWkPHwI xbI3OfaZxwPPG35xR07Wtjo5G4Fu+jt83VjSXHpaDKCvKjG0duTPUhMHez0WexyJzl5X kMmJIyrMIyEcmaaR3Bz29BBQ73g0nIN59KYVhQ9lu2YfnD03rA/UGOfA5rLNHOJjEpac id6xCRlpW7L5ERKGpnt1Q1nK17bOylulAdWt2Lfm6ec10Jn9z3yInZV9TdqrtDPOSZJw PVewfQ6gNuBhVKRUKLU+MGBGfveTX8HRp1tJJkmdni9yrzBTOO2BWF8PoiXwVUGqjFd3 1C0g== X-Gm-Message-State: AOUpUlHrLGDjv9EWspN++0PxSMqNjinHQ1jizRueCOg3iAyLzgWKiA6j K5bWr0WPPVntUxbnaPfVtFIJ5q03XEXH+OM6UFYYKo+J X-Google-Smtp-Source: AA+uWPzUHUgl8H3gWdK5Q7ZNxQH4nk++m13R2YWL1nC20TR3GR/SEiRwDfmJEh2pPk8q/8r5vRr5r67wK6A82lQrtPQ= X-Received: by 2002:adf:b642:: with SMTP id i2-v6mr4724851wre.54.1533926995444; Fri, 10 Aug 2018 11:49:55 -0700 (PDT) MIME-Version: 1.0 References: <6cd7812883d64d65b94151f6b14e3ab9@XCH-ALN-014.cisco.com> In-Reply-To: <6cd7812883d64d65b94151f6b14e3ab9@XCH-ALN-014.cisco.com> From: Alberto Leiva Date: Fri, 10 Aug 2018 13:49:44 -0500 Message-ID: To: jheitz@cisco.com Cc: sidr@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [sidr] Endianness of RTR X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Aug 2018 18:50:00 -0000 Thank you! "Expires August 1999" Oops. Though the problem might be a tad more broad than just byte order. I actually came up with another question since yesterday: What is the unit of the "Length of Error Text" field from the Error Report PDU? 8-bit bytes or code points? or perhaps graphemes? On Fri, Aug 10, 2018 at 1:12 PM Jakob Heitz (jheitz) wrote: > > It's actually a good question, because it highlights that we don't even think about this anymore. > Perhaps https://tools.ietf.org/html/draft-newman-network-byte-order-01 > should be advanced to RFC. > A: Big Endian. > > Regards, > Jakob. > > > -----Original Message----- > From: sidr On Behalf Of Alberto Leiva > Sent: Thursday, August 9, 2018 2:40 PM > To: sidr@ietf.org > Subject: [sidr] Endianness of RTR > > Hi > > Please forgive me if this is a stupid question, but > > What is the endianness of the RTR protocol? (RFCs 6810 and 8210) > And why does it seem like it's not specified in the RFCs? > > Thanks > Alberto > > _______________________________________________ > sidr mailing list > sidr@ietf.org > https://www.ietf.org/mailman/listinfo/sidr From nobody Wed Aug 15 21:18:08 2018 Return-Path: X-Original-To: sidr@ietfa.amsl.com Delivered-To: sidr@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61EB0130E21 for ; Wed, 15 Aug 2018 21:18:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q6DUHzSq22Co for ; Wed, 15 Aug 2018 21:18:04 -0700 (PDT) Received: from adrilankha.hactrn.net (adrilankha.hactrn.net [IPv6:2001:418:1::19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43A15130E19 for ; Wed, 15 Aug 2018 21:18:04 -0700 (PDT) Received: from minas-ithil.hactrn.net (c-66-30-20-66.hsd1.ma.comcast.net [66.30.20.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "nargothrond.hactrn.net", Issuer "Grunchweather Associates" (not verified)) by adrilankha.hactrn.net (Postfix) with ESMTPS id D63CC8; Thu, 16 Aug 2018 04:18:02 +0000 (UTC) Received: from minas-ithil.hactrn.net (localhost [IPv6:::1]) by minas-ithil.hactrn.net (Postfix) with ESMTP id 3B4C220076DC65; Thu, 16 Aug 2018 00:17:52 -0400 (EDT) Date: Thu, 16 Aug 2018 00:17:52 -0400 From: Rob Austein To: Alberto Leiva Cc: jheitz@cisco.com, sidr@ietf.org In-Reply-To: References: <6cd7812883d64d65b94151f6b14e3ab9@XCH-ALN-014.cisco.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.1 Mule/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Message-Id: <20180816041752.3B4C220076DC65@minas-ithil.hactrn.net> Archived-At: Subject: Re: [sidr] Endianness of RTR X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 04:18:05 -0000 On Fri, 10 Aug 2018 14:49:44 -0400, Alberto Leiva wrote: > > Though the problem might be a tad more broad than just byte order. I > actually came up with another question since yesterday: > What is the unit of the "Length of Error Text" field from the Error > Report PDU? 8-bit bytes or code points? or perhaps graphemes? Octets. From nobody Thu Aug 30 11:28:54 2018 Return-Path: X-Original-To: sidr@ietf.org Delivered-To: sidr@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CE73F130E0A; Thu, 30 Aug 2018 11:28:45 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: sidr@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.83.1 Auto-Submitted: auto-generated Precedence: bulk Reply-To: sidr@ietf.org Message-ID: <153565372581.3144.14852530580888223510@ietfa.amsl.com> Date: Thu, 30 Aug 2018 11:28:45 -0700 Archived-At: Subject: [sidr] I-D Action: draft-ietf-sidr-rtr-keying-16.txt X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.27 List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Aug 2018 18:28:46 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Secure Inter-Domain Routing WG of the IETF. Title : Router Keying for BGPsec Authors : Randy Bush Sean Turner Keyur Patel Filename : draft-ietf-sidr-rtr-keying-16.txt Pages : 18 Date : 2018-08-30 Abstract: BGPsec-speaking routers are provisioned with private keys in order to sign BGPsec announcements. The corresponding public keys are published in the global Resource Public Key Infrastructure, enabling verification of BGPsec messages. This document describes two methods of generating the public-private key-pairs: router-driven and operator-driven. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-sidr-rtr-keying/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-sidr-rtr-keying-16 https://datatracker.ietf.org/doc/html/draft-ietf-sidr-rtr-keying-16 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-sidr-rtr-keying-16 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Thu Aug 30 11:30:16 2018 Return-Path: X-Original-To: sidr@ietfa.amsl.com Delivered-To: sidr@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0F02130E0A for ; Thu, 30 Aug 2018 11:30:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com 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 0A3rlX4rka83 for ; Thu, 30 Aug 2018 11:30:13 -0700 (PDT) Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04F24130DD8 for ; Thu, 30 Aug 2018 11:30:13 -0700 (PDT) Received: by mail-qk1-x733.google.com with SMTP id j7-v6so43501qkd.13 for ; Thu, 30 Aug 2018 11:30:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=EDcKlV77tfgeJkP+EItQkIHjQ9DuLSndnC/naW6AFAo=; b=YP7uTV8H3tVGQaRDJQbFG2p0TJvDyaXlVcnaJpa20Hbdlb0Qo6TBALg/Z3Djos8rln uFMBr9kj8f2j/3ZA1PEzpREplVKc470VGPm33f+QZ8sFYfSQWbZMECrOR//NQeO9UJ/N Av+30D9QMlOxm0oNVVLFHxNriMdqTbLQlfJKM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=EDcKlV77tfgeJkP+EItQkIHjQ9DuLSndnC/naW6AFAo=; b=EvEAvUsjQZL3oWSDkPU6P24q08DXmyjk7LvBuq94l1xKiU3iC63GtgNQzZrBQtPaCl q0Dj3v3vSYxciT5vf0OyvM9RgmxXN/o7A5Hdd0nWP6Y/hd9d7l2vYgYUIF/pkrKiIImu rhiv4XMz3/YuVRicx0Wdy0oJ60WcYSlusX3AtrXEe/877XeXGd/MmOm3y7+TFmUUiEzT QtgR4bIGrhcmRltJb7WeklXVAW4rIq2xCt4fZr+k6W5Ulf9wbYM+FpTbBRRn9KJfX+/p FU5u5abKpVj7BV0GU2H7zzS/ScXl++QrD7Zh+wuKFSBiWiyXYy8nGSnV5bPrd+mNLxgF 2kPQ== X-Gm-Message-State: APzg51AlNVuDAmBUd0BKcKhFVAVpLWX5zCJA84tCCNoA7Hq7p9Pq4mAI fg3zf2m591zOk79HuiF+TpU7F4KGxDc= X-Google-Smtp-Source: ANB0VdYBLThc+k7T3uTp89qimEGSV2ucRJvn45dHz+5TQW4pxtPFX3fxRRKEwVn0asjV3yDGxuPbNg== X-Received: by 2002:a37:a107:: with SMTP id k7-v6mr12445780qke.276.1535653811943; Thu, 30 Aug 2018 11:30:11 -0700 (PDT) Received: from [172.16.0.18] ([96.231.225.148]) by smtp.gmail.com with ESMTPSA id p18-v6sm5304002qtp.3.2018.08.30.11.30.10 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Aug 2018 11:30:10 -0700 (PDT) From: Sean Turner Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Date: Thu, 30 Aug 2018 14:30:09 -0400 References: <153565372581.3144.14852530580888223510@ietfa.amsl.com> To: sidr@ietf.org In-Reply-To: <153565372581.3144.14852530580888223510@ietfa.amsl.com> Message-Id: <79C7E169-D962-4328-84DD-C668DD3AA1D1@sn3rd.com> X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [sidr] I-D Action: draft-ietf-sidr-rtr-keying-16.txt X-BeenThere: sidr@ietf.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Secure Interdomain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Aug 2018 18:30:15 -0000 This version I believes addresses the two outstanding issues Sandy = raised during her review. spt > On Aug 30, 2018, at 14:28, internet-drafts@ietf.org wrote: >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts = directories. > This draft is a work item of the Secure Inter-Domain Routing WG of the = IETF. >=20 > Title : Router Keying for BGPsec > Authors : Randy Bush > Sean Turner > Keyur Patel > Filename : draft-ietf-sidr-rtr-keying-16.txt > Pages : 18 > Date : 2018-08-30 >=20 > Abstract: > BGPsec-speaking routers are provisioned with private keys in order = to > sign BGPsec announcements. The corresponding public keys are > published in the global Resource Public Key Infrastructure, enabling > verification of BGPsec messages. This document describes two = methods > of generating the public-private key-pairs: router-driven and > operator-driven. >=20 >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-sidr-rtr-keying/ >=20 > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-sidr-rtr-keying-16 > https://datatracker.ietf.org/doc/html/draft-ietf-sidr-rtr-keying-16 >=20 > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-sidr-rtr-keying-16 >=20 >=20 > Please note that it may take a couple of minutes from the time of = submission > until the htmlized version and diff are available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt