Return-Path: 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 BC878C151524 for ; Tue, 22 Oct 2024 06:08:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.105 X-Spam-Level: X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=univ-grenoble-alpes.fr 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 yo0nVebIapKN for ; Tue, 22 Oct 2024 06:08:53 -0700 (PDT) Received: from zm-mta-out-3.u-ga.fr (zm-mta-out-3.u-ga.fr [152.77.200.56]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CE23C151083 for ; Tue, 22 Oct 2024 06:08:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=univ-grenoble-alpes.fr; s=2020; t=1729602530; bh=56rjXODdrkfm9/nv8ab7reLMZqE20yChulCtbPsFFSg=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=EmtXo6VHnwKgPiIRSwbNdQhBkMlk7gVwXrhjkd3Ks25S5DXJSoiHz1j/BwDNIySGl gcxNecl9417ElHzlzkL4G6rc+VhDMm5Jn/PoLd9j7LJiPdr+4n2HKmh8IaC5zqDaVE asEjjCRml5TKLyZbGOXdh+bTVwLU4lyjfSBZ0d4EgZNVR2AOK01dEG/FtSMG4n1IKC mpVeZSnyW4AFd8o2mkpkBDoPOP22Dui7cal0C4knHB7xkKzTUgyJZaxMJyvNVQgCZI OXE8Hqi8Ry8OjVhWmDJVEdQTEfncxqu8Hrz+BHeVzIA3d51y7+7OjDoD7LVmfHRprI qXc/8fzFgIdcQ== Received: from mailhub.u-ga.fr (mailhub-2.u-ga.fr [129.88.178.102]) by zm-mta-out-3.u-ga.fr (Postfix) with ESMTP id 1C19A402F7; Tue, 22 Oct 2024 15:08:50 +0200 (CEST) Received: from mailhost.u-ga.fr (mailhost2.u-ga.fr [129.88.177.242]) by mailhub.u-ga.fr (Postfix) with ESMTP id 1930A100068; Tue, 22 Oct 2024 15:08:50 +0200 (CEST) Received: from zm-mbx1.u-ga.fr (zm-mbx1.u-ga.fr [152.77.200.25]) by mailhost.u-ga.fr (Postfix) with ESMTP id 134246006E; Tue, 22 Oct 2024 15:08:50 +0200 (CEST) Date: Tue, 22 Oct 2024 15:08:50 +0200 (CEST) From: MAXENCE FLECHIER To: Tim Bruijnzeels Message-ID: <185186335.6257321.1729602530013.JavaMail.zimbra@univ-grenoble-alpes.fr> In-Reply-To: <2B5018E0-88F2-4F22-9019-CB4E2D7C76CC@ripe.net> References: <172949614414.1928204.13705076339855498166@dt-datatracker-78dc5ccf94-w8wgc> <1731518267.5779756.1729528461733.JavaMail.zimbra@univ-grenoble-alpes.fr> <2B5018E0-88F2-4F22-9019-CB4E2D7C76CC@ripe.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_6f707e1c-c4b6-44de-9452-b266fcbb10d5" X-Originating-IP: [129.88.55.138] X-Mailer: Zimbra 10.1.2_GA_4685 (ZimbraWebClient - FF131 (Linux)/10.1.1_GA_4660) Thread-Topic: I-D Action: draft-ietf-sidrops-vrp-notation-02.txt Thread-Index: 5Qfzu265raQ/xKsVGKCtPaxPDXON3Q== X-Greylist: Whitelist-UGA MAILHOST (SMTP non authentifie) depuis 152.77.200.25 Message-ID-Hash: D2RENJER7THF2O6BIDAQAY7BV7VAF7OX X-Message-ID-Hash: D2RENJER7THF2O6BIDAQAY7BV7VAF7OX X-MailFrom: maxence.flechier@univ-grenoble-alpes.fr 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 CC: sidrops X-Mailman-Version: 3.3.9rc6 Precedence: list Subject: =?utf-8?q?=5BSidrops=5D_Re=3A_I-D_Action=3A_draft-ietf-sidrops-vrp-notation-?= =?utf-8?q?02=2Etxt?= List-Id: A list for the SIDR Operations WG Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --=_6f707e1c-c4b6-44de-9452-b266fcbb10d5 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I am referring to the fact that ABNF states that "%d0-255" is defined as=20 > A range of alternative numeric values can be specified compactly, using a= dash ("-") to indicate the range of alternative values.=20 which would not mean a number between 0 and 255, but a character encoded by= a value between 0 and 255, which could be equivalent were we to state that= the encoding is the number, but that is not the case since we also define,= for exemple, "%d9".=20 Once again, i am not familiar with ABNF practices outside of the RFCs 5234 = and 7405 so i don't know if this is a real issue or not.=20 Maxence=20 De: "Tim Bruijnzeels" =20 =C3=80: "MAXENCE FLECHIER" =20 Cc: "sidrops" =20 Envoy=C3=A9: Mardi 22 Octobre 2024 10:50:49=20 Objet: Re: [Sidrops] I-D Action: draft-ietf-sidrops-vrp-notation-02.txt=20 > On 21 Oct 2024, at 18:34, MAXENCE FLECHIER wrote:=20 >=20 > Hi,=20 >=20 > I was reading the *-notation drafts and, regardless of where this goes, i= wanted to point a few things regarding the ABNF part:=20 > - i'm pretty sure you want to use "tab =3D %d9"=20 indeed, oops.=20 > - why the providers-multiline cannot have a wspml instead of wsp before t= he final "]"=20 indeed, oops, that should be wspml not wsp.=20 > - i understand the use of value ranges (in both drafts) to specify purely= decimal or hex ranges, but since ABNF is all character based i think it ca= n be confusing to have multiple character encoding in the same ABNF specifi= cation? or maybe i am missing something and then don't mind this question.= =20 I am not sure that I understand what you mean. Are you referring to decimal= versus hex in the VRP draft for IPv4 and IPv6 respectively?=20 Tim=20 >=20 > Maxence=20 >=20 > De: internet-drafts@ietf.org=20 > =C3=80: i-d-announce@ietf.org=20 > Cc: sidrops@ietf.org=20 > Envoy=C3=A9: Lundi 21 Octobre 2024 09:35:44=20 > Objet: [Sidrops] I-D Action: draft-ietf-sidrops-vrp-notation-02.txt=20 >=20 > Internet-Draft draft-ietf-sidrops-vrp-notation-02.txt is now available. I= t is=20 > a work item of the SIDR Operations (SIDROPS) WG of the IETF.=20 >=20 > Title: Human Readable Validate ROA Payload Notation=20 > Authors: Tim Bruijnzeels=20 > Ties de Kock=20 > Oliver Borchert=20 > Di Ma=20 > Name: draft-ietf-sidrops-vrp-notation-02.txt=20 > Pages: 5=20 > Dates: 2024-10-21=20 >=20 > Abstract:=20 >=20 > This document defines a human readable notation for Validated ROA=20 > Payloads (VRP, RFC 6811) based on ABNF (RFC 5234) for use with RPKI=20 > tooling and documentation.=20 >=20 > The IETF datatracker status page for this Internet-Draft is:=20 > https://datatracker.ietf.org/doc/draft-ietf-sidrops-vrp-notation/=20 >=20 > There is also an HTML version available at:=20 > https://www.ietf.org/archive/id/draft-ietf-sidrops-vrp-notation-02.html= =20 >=20 > A diff from the previous version is available at:=20 > https://author-tools.ietf.org/iddiff?url2=3Ddraft-ietf-sidrops-vrp-notati= on-02=20 >=20 > Internet-Drafts are also available by rsync at:=20 > rsync.ietf.org::internet-drafts=20 >=20 >=20 > _______________________________________________=20 > Sidrops mailing list -- sidrops@ietf.org=20 > To unsubscribe send an email to sidrops-leave@ietf.org=20 > _______________________________________________=20 > Sidrops mailing list -- sidrops@ietf.org=20 > To unsubscribe send an email to sidrops-leave@ietf.org=20 --=_6f707e1c-c4b6-44de-9452-b266fcbb10d5 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
I am referring to the fact that ABNF states= that "%d0-255" is defined as
> A range of alternative numeric= values can be specified compactly, using a dash ("-") to indicate the rang= e of alternative values.
which would not= mean a number between 0 and 255, but a character encoded by a value betwee= n 0 and 255, which could be equivalent were we to state that the encoding i= s the number, but that is not the case since we also define, for exemple, "= %d9".
Once again, i am not familiar with= ABNF practices outside of the RFCs 5234 and 7405 so i don't know if this i= s a real issue or not.

Maxence

= De: "Tim Bruijnzeels" <tbruijnzeels@ripe.net>
=C3=80: "MAXENCE FLECHIER" <maxence.flechier@univ-grenoble-alpes.fr>
= Cc: "sidrops" <sidrops@ietf.org>
Envoy=C3=A9: Mardi 22 = Octobre 2024 10:50:49
Objet: Re: [Sidrops] I-D Action: draft-ietf= -sidrops-vrp-notation-02.txt

> On 21 Oct 2024, at 18:34, MAXENCE FLECHIER <maxence.= flechier@univ-grenoble-alpes.fr> wrote:
>
> Hi,
> > I was reading the *-notation drafts and, regardless of where this goe= s, i wanted to point a few things regarding the ABNF part:
> - i'm pr= etty sure you want to use "tab =3D %d9"

indeed, oops.

> - = why the providers-multiline cannot have a wspml instead of wsp before the f= inal "]"

indeed, oops, that should be wspml not wsp.

> - i= understand the use of value ranges (in both drafts) to specify purely deci= mal or hex ranges, but since ABNF is all character based i think it can be = confusing to have multiple character encoding in the same ABNF specificatio= n? or maybe i am missing something and then don't mind this question.
I am not sure that I understand what you mean. Are you referring to decim= al versus hex in the VRP draft for IPv4 and IPv6 respectively?

Tim




>
> Maxence
>
> De: internet-d= rafts@ietf.org
> =C3=80: i-d-announce@ietf.org
> Cc: sidrops@ie= tf.org
> Envoy=C3=A9: Lundi 21 Octobre 2024 09:35:44
> Objet: [= Sidrops] I-D Action: draft-ietf-sidrops-vrp-notation-02.txt
>
>= ; Internet-Draft draft-ietf-sidrops-vrp-notation-02.txt is now available. I= t is
> a work item of the SIDR Operations (SIDROPS) WG of the IETF.>
>    Title:   Human Readable Validate ROA Payl= oad Notation
>    Authors: Tim Bruijnzeels
>   &= nbsp;         Ties de Kock
>      =       Oliver Borchert
>         &= nbsp;   Di Ma
>    Name:    draft-ietf-sidro= ps-vrp-notation-02.txt
>    Pages:   5
>   =  Dates:   2024-10-21
>
> Abstract:
>
> =    This document defines a human readable notation for Validated = ROA
>    Payloads (VRP, RFC 6811) based on ABNF (RFC 5234) = for use with RPKI
>    tooling and documentation.
> <= br>> The IETF datatracker status page for this Internet-Draft is:
>= ; https://datatracker.ietf.org/doc/draft-ietf-sidrops-vrp-notation/
>=
> There is also an HTML version available at:
> https://www.i= etf.org/archive/id/draft-ietf-sidrops-vrp-notation-02.html
>
>= A diff from the previous version is available at:
> https://author-t= ools.ietf.org/iddiff?url2=3Ddraft-ietf-sidrops-vrp-notation-02
>
= > Internet-Drafts are also available by rsync at:
> rsync.ietf.org= ::internet-drafts
>
>
> _______________________________= ________________
> Sidrops mailing list -- sidrops@ietf.org
> T= o unsubscribe send an email to sidrops-leave@ietf.org
> _____________= __________________________________
> Sidrops mailing list -- sidrops@= ietf.org
> To unsubscribe send an email to sidrops-leave@ietf.org
=
--=_6f707e1c-c4b6-44de-9452-b266fcbb10d5--