[Sidrops] Re: I-D Action: draft-ietf-sidrops-vrp-notation-02.txt

[MAXENCE FLECHIER <[e-mail]>]

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 range of alternative values. 
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". 
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. 

Maxence 


De: "Tim Bruijnzeels" <[e-mail]> 
À: "MAXENCE FLECHIER" <[e-mail]> 
Cc: "sidrops" <[e-mail]> 
Envoyé: 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 <[e-mail]> wrote: 
> 
> Hi, 
> 
> I was reading the *-notation drafts and, regardless of where this goes, i wanted to point a few things regarding the ABNF part: 
> - i'm pretty sure you want to use "tab = %d9" 

indeed, oops. 

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

indeed, oops, that should be wspml not wsp. 

> - 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 can be confusing to have multiple character encoding in the same ABNF specification? 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 decimal versus hex in the VRP draft for IPv4 and IPv6 respectively? 

Tim 





> 
> Maxence 
> 
> De: [e-mail] 
> À: [e-mail] 
> Cc: [e-mail] 
> Envoyé: 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. It is 
> a work item of the SIDR Operations (SIDROPS) WG of the IETF. 
> 
> Title: Human Readable Validate ROA Payload Notation 
> Authors: Tim Bruijnzeels 
> Ties de Kock 
> Oliver Borchert 
> Di Ma 
> Name: draft-ietf-sidrops-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. 
> 
> 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.ietf.org/archive/id/draft-ietf-sidrops-vrp-notation-02.html 
> 
> A diff from the previous version is available at: 
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-sidrops-vrp-notation-02 
> 
> Internet-Drafts are also available by rsync at: 
> rsync.ietf.org::internet-drafts 
> 
> 
> _______________________________________________ 
> Sidrops mailing list -- [e-mail] 
> To unsubscribe send an email to [e-mail] 
> _______________________________________________ 
> Sidrops mailing list -- [e-mail] 
> To unsubscribe send an email to [e-mail]