[Sidrops] Re: [WGLC] draft-ietf-sidrops-rrdp-same-origin-00 - Ends 1/July/2024

"joseph@ntt.net" <joseph@ntt.net> Thu, 20 June 2024 16:05 UTC

Return-Path: <joseph@ntt.net>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A586C14F603 for <sidrops@ietfa.amsl.com>; Thu, 20 Jun 2024 09:05:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.806
X-Spam-Level:
X-Spam-Status: No, score=-1.806 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yc_yfa8dTXqX for <sidrops@ietfa.amsl.com>; Thu, 20 Jun 2024 09:05:39 -0700 (PDT)
Received: from mail4.dllstx09.us.to.gin.ntt.net (mail4.dllstx09.us.to.gin.ntt.net [IPv6:2001:418:3ff:5::192:26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 385B5C14F5F9 for <sidrops@ietf.org>; Thu, 20 Jun 2024 09:05:39 -0700 (PDT)
Received: from SA1PR11MB6757.namprd11.prod.outlook.com (unknown [IPv6:2603:1036:305:489c::5]) by mail4.dllstx09.us.to.gin.ntt.net (Postfix) with ESMTPSA id E8685EE0147; Thu, 20 Jun 2024 16:05:37 +0000 (UTC)
From: "joseph@ntt.net" <joseph@ntt.net>
To: "sidrops@ietf.org" <sidrops@ietf.org>
Thread-Topic: [Sidrops] [WGLC] draft-ietf-sidrops-rrdp-same-origin-00 - Ends 1/July/2024
Thread-Index: AQHawyukdw9THz0D5UuzJCUifKvmGg==
X-MS-Exchange-MessageSentRepresentingType: 1
Date: Thu, 20 Jun 2024 16:05:37 +0000
Message-ID: <SA1PR11MB67578E4EE166F64F8EB1E731AEC82@SA1PR11MB6757.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator:
X-MS-Exchange-Organization-RecordReviewCfmType: 0
Content-Type: multipart/alternative; boundary="_000_SA1PR11MB67578E4EE166F64F8EB1E731AEC82SA1PR11MB6757namp_"
MIME-Version: 1.0
Message-ID-Hash: A6V67GZ3AOAFWVAIQXQ3NHDTK34CX2Y4
X-Message-ID-Hash: A6V67GZ3AOAFWVAIQXQ3NHDTK34CX2Y4
X-MailFrom: joseph@ntt.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-sidrops.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Sidrops] Re: [WGLC] draft-ietf-sidrops-rrdp-same-origin-00 - Ends 1/July/2024
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/0dBv_dZ8l7yZv-bj9LxyyRh1LGY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Owner: <mailto:sidrops-owner@ietf.org>
List-Post: <mailto:sidrops@ietf.org>
List-Subscribe: <mailto:sidrops-join@ietf.org>
List-Unsubscribe: <mailto:sidrops-leave@ietf.org>

I support publication as RFC. This document addresses a potential security hole in the original RRDP RFC, I agree that it would be beneficial to update the original RFC.

Job, I sent you a list of grammar/spelling nitpicks offlist.



Sincerely,

Joseph Nicholson





On 6/20/24, 10:59, "Keyur Patel" <keyur=40arrcus.com@dmarc.ietf.org> wrote:

Hi Folks,

A working group last call has been issued for  “Same-Origin Policy for the RPKI Repository Delta Protocol (RRDP)” https://datatracker.ietf.org/doc/draft-ietf-sidrops-rrdp-same-origin/<https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-ietf-sidrops-rrdp-same-origin/__;!!MXpALLYS!WmUnyglark0zMg_Drf5ArBHaoTbdSdViUxZae6bYhsEI9HL1c4n52gAQCJDVLdc0hbX-QYoBYOu7znmN9S5tI8lOEZjZT5iuX9aQDeCl$>.

Please send your comments to the list. The adoption call will end on July 1, 2024.

Job please reply indicating whether you’re aware of any relevant IPR that hasn’t been disclosed.

Best Regards,
Chris, Russ & Keyur