Re: [Sidrops] [internet-drafts@ietf.org: New Version Notification for draft-spaghetti-sidrops-aspa-slurm-00.txt]

Di Ma <madi@juicybun.cn> Thu, 23 February 2023 16:39 UTC

Return-Path: <madi@juicybun.cn>
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 164EDC1522B9 for <sidrops@ietfa.amsl.com>; Thu, 23 Feb 2023 08:39:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 4-49hLr-bSwv for <sidrops@ietfa.amsl.com>; Thu, 23 Feb 2023 08:39:42 -0800 (PST)
Received: from smtpbgau2.qq.com (smtpbgau2.qq.com [54.206.34.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8C23C15154C for <sidrops@ietf.org>; Thu, 23 Feb 2023 08:39:39 -0800 (PST)
X-QQ-mid: bizesmtp74t1677170368tmcix876
Received: from smtpclient.apple ( [121.8.152.202]) by bizesmtp.qq.com (ESMTP) with id ; Fri, 24 Feb 2023 00:39:27 +0800 (CST)
X-QQ-SSF: 00100000003000F0Z000B00A0000000
X-QQ-FEAT: IcCSTr/hHjOQTx9EA6A7gp2/30eYTTstnB1uWHjh3xsYIAnrmu2e35IhN/Lxj K16p9fw4tmLZvPZ9o7u3+u3p1xJ91GfRUkANkxOV4+7SklI1/t7q9Wxy3MAPOxkURDw+L1J PKqJsw4EdFuQSd54hCmlhxxxCgh6IvcK3cCbJXp6xCngG5qVfp7pOxySqRAyREFmGiMA838 BVBELTZ3cBK617rerDXPiY6lcUAg4ugLero/7Z3fY2VFcfoou6Z7PRhUIUMENUtYLAHHG5m ajG3QmmeLDluAoxVdqnw7oZNVCW6lA9udC1jHzDExs8ONKgEFFGriBKjCl4EDnALgyKNbfh TQdm8A6chbViP165fpss+Y0GjHB4rX6ioROlszZ
X-QQ-GoodBg: 0
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.300.101.1.3\))
From: Di Ma <madi@juicybun.cn>
In-Reply-To: <DB15C81D-FC28-4DA1-88FF-20D03753BFE0@nlnetlabs.nl>
Date: Fri, 24 Feb 2023 00:39:17 +0800
Cc: sidrops <sidrops@ietf.org>, Tim Bruijnzeels <tim@nlnetlabs.nl>
Content-Transfer-Encoding: quoted-printable
Message-Id: <FE047C3F-B04B-4E1B-92F2-A8B280B1389A@juicybun.cn>
References: <Y/dkK0LgV0TZvDcf@snel> <DB15C81D-FC28-4DA1-88FF-20D03753BFE0@nlnetlabs.nl>
To: Job Snijders <job=40fastly.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3731.300.101.1.3)
X-QQ-SENDSIZE: 520
Feedback-ID: bizesmtp:juicybun.cn:qybglogicsvr:qybglogicsvr6
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/KKYCAJDqIWFVoeJsF5ZWaNPHch8>
Subject: Re: [Sidrops] [internet-drafts@ietf.org: New Version Notification for draft-spaghetti-sidrops-aspa-slurm-00.txt]
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2023 16:39:44 -0000

Job,

Thanks for initiating this work.

As one of the original SLURM co-authors, I am in support of adoption of it as WG item and I volunteer to work on it as co-author. 

Di

> 2023年2月24日 00:23,Tim Bruijnzeels <tim@nlnetlabs.nl> 写道:
> 
> Hi Job, all,
> 
>> On 23 Feb 2023, at 14:03, Job Snijders <job=40fastly.com@dmarc.ietf.org> wrote:
>> 
>> Hi all,
>> 
>> While working on running code implementations to support RFC8210bis in
>> StayRTR and OpenBGPD, it dawned upon us that SLURM for ASPA wasn't
>> specified yet.
>> 
>> This below submission serves to compliment the existing body of work
>> related to ASPA, and barring any complications, it might be good to try
>> to make this part of the I-D cluster draft-ietf-sidrops-8210bis,
>> draft-ietf-sidrops-aspa-profile, & draft-ietf-sidrops-aspa-verification.
>> 
>> If the WG & chairs think this make sense, I'd like to ask for a call for
>> Working Group Adoption for draft-spaghetti-sidrops-aspa-slurm.
> 
> I think this should indeed be done.. I have mentioned this on occasion, and quite recently I asked about this explicitly here:
> https://mailarchive.ietf.org/arch/msg/sidrops/-mGfZYT7IcVSGB8vPuwkWvENy0c/
> 
> As one of the original SLURM co-authors I volunteered to work on it, and asked if the WG agrees that it's needed. I got little response to this. As a result talking to the other co-authors, and drafting a proposal did not make it to the top of my todo list yet. Given the lack of responses I am a bit surprised that there is now a document.
> 
> As for the content. It is not clear through the references how the Validated ASPA Payloads (VAPs) are made, and fed into RPKI-RTR (8210-bis). There is a reference related to VAP to draft-ietf-sidrops-aspa-profile-12, which in turn refers to draft-ietf-sidrops-aspa-verification-11 for this. The latter document does not mention VAP.
> 
> This is important if we are to understand what the format should be for the aspa filter and local assertions. In particular, we need to know whether a VAP is modelled after the 8210-bis section 5.12 ASPA PDU. Or.. that, like Validated ROA Prefixes, it's a tuple of (customer-as, provider-as, optional afi limit) in which case as single ASPA object would contain multiple VAPs, and other ASPA objects could contain some of the same VAPs, as well as additional VAPs. I would then expect these to be combined to form the appropriate ASPA rtr PDU.
> 
> I think we need clarity on this before the SLURM data format can be decided on.
> 
> 
> Kind regards,
> Tim
> 
> 
> 
> 
>> 
>> Feedback, suggestions, pull requests & text are welcome too.
>> 
>> Kind regards,
>> 
>> Job
>> 
>> ----- Forwarded message from internet-drafts@ietf.org -----
>> 
>> Date: Thu, 23 Feb 2023 04:57:19 -0800
>> From: internet-drafts@ietf.org
>> To: Ben Cartwright-Cox <ben@benjojo.co.uk>, Job Snijders <job@fastly.com>
>> Subject: New Version Notification for draft-spaghetti-sidrops-aspa-slurm-00.txt
>> 
>> 
>> A new version of I-D, draft-spaghetti-sidrops-aspa-slurm-00.txt
>> has been successfully submitted by Job Snijders and posted to the
>> IETF repository.
>> 
>> Name: draft-spaghetti-sidrops-aspa-slurm
>> Revision: 00
>> Title: Simplified Local Internet Number Resource Management (SLURM) with RPKI Autonomous System Provider Authorizations (ASPA)
>> Document date: 2023-02-23
>> Group: Individual Submission
>> Pages: 9
>> URL:            https://www.ietf.org/archive/id/draft-spaghetti-sidrops-aspa-slurm-00.txt
>> Status:         https://datatracker.ietf.org/doc/draft-spaghetti-sidrops-aspa-slurm/
>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-spaghetti-sidrops-aspa-slurm
>> 
>> 
>> Abstract:
>>  ISPs may want to establish a local view of exceptions to the Resource
>>  Public Key Infrastructure (RPKI) data in the form of local filters
>>  and additions.  This document defines an addendum to RFC 8416 by
>>  specifying a format for local filters and local assertions for
>>  Autonomous System Provider Authorizations (ASPA) for use with the
>>  RPKI.
>> 
>> 
>> 
>> 
>> 
>> The IETF Secretariat
>> 
>> 
>> 
>> ----- End forwarded message -----
>> 
>> _______________________________________________
>> Sidrops mailing list
>> Sidrops@ietf.org
>> https://www.ietf.org/mailman/listinfo/sidrops
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops
>