Re: [auth48] AUTH48: RFC-to-be 9319 <draft-ietf-sidrops-rpkimaxlen-15> for

["Sriram, Kotikalapudi (Fed)" <[e-mail]>]

Rebecca and Ben,

I see the dilemma that both RFC Editors and authors are having. I think we can set the course straight here for this document as well as for future IETF documents with respect to acronym for RPKI-based Route Origin Validation.

I am proposing leaving ROV definition like what Ben pointed out: ROV == Route Origin Validation (this is found in the existing literature).

So, in this document, I propose we use the acronym RPKI-ROV for RPKI-based Route Origin Validation. We will first use it in the abstract by replacing (ROV) with (RPKI-ROV).

I scanned and find that we have used ROV in the document in only a few places and always meant it to be RPKI-based Route Origin Validation. Therefore,

s/ROV/RPKI-ROV/   (globally)

Then, we replace the new paragraph in the Introduction as follows:

Old Text:

   Please note that the term "RPKI-based Route Origin Validation" and
   the corresponding acronym "ROV" that are used in this document mean
   the same as the term "Prefix Origin Validation" used in [RFC6811].

New Text:

   Please note that the term "RPKI-based Route Origin Validation" and
   the corresponding acronym "RPKI-ROV" that are used in this document mean
   the same as the term "Prefix Origin Validation" used in [RFC6811].

End of New Text.

Note: It is good to establish a unique acronym for RPKI-based ROV since there is also IRR-based ROV in the literature elsewhere. People may loosely use ROV for RPKI-ROV colloquially and that is OK. It does not concern us in this document.

I hope this helps.

Sriram


From: Ben Maddison <[e-mail]>
Sent: Monday, October 3, 2022 2:58 PM
To: Rebecca VanRheenen <[e-mail]>; Sriram, Kotikalapudi (Fed) <[e-mail]>; [e-mail]; [e-mail]; Job Snijders <[e-mail]>
Cc: RFC Editor <[e-mail]>; [e-mail]; [e-mail]; Chris Morrow <[e-mail]>; Warren Kumari <[e-mail]>; [e-mail]
Subject: Re: AUTH48: RFC-to-be 9319 <draft-ietf-sidrops-rpkimaxlen-15> for

Hi Rebecca,

ROV == Route Origin Validation, so in full you would have "RPKI-based ROV". However, the "RPKI-based" bit is clear from the context of the document, so I believe either/both are fine.

Hope that clarifies?

Cheers,

Ben
________________________________
From: Rebecca VanRheenen <[e-mail]<mailto:[e-mail]>>
Sent: Monday, October 3, 2022 8:15:50 PM
To: Ben Maddison <[e-mail]<mailto:[e-mail]>>; Sriram, Kotikalapudi (Fed) <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>; Job Snijders <[e-mail]<mailto:[e-mail]>>
Cc: RFC Editor <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>; Chris Morrow <[e-mail]<mailto:[e-mail]>>; Warren Kumari <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]> <[e-mail]<mailto:[e-mail]>>
Subject: Re: AUTH48: RFC-to-be 9319 <draft-ietf-sidrops-rpkimaxlen-15> for

Hi Sriram and Ben,

Ben, we have noted your approval on the AUTH48 status page for this document (see https://www.rfc-editor.org/auth48/rfc9319)<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauth48%2Frfc9319)&data=05%7C01%7Ckotikalapudi.sriram%40nist.gov%7C90bcf13c011645f2d73208daa5713493%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638004202921984225%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=CgYMYy7FGJgFU1xb%2BmbqPZ%2F0uWe9Xd7bGcUkVMVnOOk%3D&reserved=0>.

We also made the update in the Introduction as suggested by Sriram. One further question: does ROV stand for "RPKI-based Route Origin Validation" or simply "Route Origin Validation"? We'd like to clarify so that this document will be consistent and so that we can accurately update our abbreviations list (the acronym ROV has not yet been used in the RFC Series). We see instances of both "RPKI-based ROV" and "ROV" in the document. Are any further updates needed for consistency?

This should be our last question; thank you for your patience!

_______________

Updated XML file:
 https://www.rfc-editor.org/authors/rfc9319.xml<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9319.xml&data=05%7C01%7Ckotikalapudi.sriram%40nist.gov%7C90bcf13c011645f2d73208daa5713493%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638004202921984225%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1PkpmLcjbl9wRP1O6itShFBIUPQdBtiQ2S792Onw8Cg%3D&reserved=0>

Updated output files:
 https://www.rfc-editor.org/authors/rfc9319.txt<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9319.txt&data=05%7C01%7Ckotikalapudi.sriram%40nist.gov%7C90bcf13c011645f2d73208daa5713493%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638004202921984225%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VQD%2Bl8rdN6u3LrEytkUZjFYqcmjAq6bsh%2BToLcESJ5E%3D&reserved=0>
 https://www.rfc-editor.org/authors/rfc9319.pdf<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9319.pdf&data=05%7C01%7Ckotikalapudi.sriram%40nist.gov%7C90bcf13c011645f2d73208daa5713493%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638004202921984225%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9pu8Ti89EXss1y2TJOHBjMMsgC5XUFGRXweUIbiOW3Q%3D&reserved=0>
 https://www.rfc-editor.org/authors/rfc9319.html<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9319.html&data=05%7C01%7Ckotikalapudi.sriram%40nist.gov%7C90bcf13c011645f2d73208daa5713493%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638004202921984225%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Ltn69BFTM6jr9IInTuTz1cs4w9kwuxGAI122IY7OM%2BE%3D&reserved=0>

Diff file showing all changes made during AUTH48:
 https://www.rfc-editor.org/authors/rfc9319-auth48diff.html<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9319-auth48diff.html&data=05%7C01%7Ckotikalapudi.sriram%40nist.gov%7C90bcf13c011645f2d73208daa5713493%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638004202921984225%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=aLW%2FtW1fJ9DgRuh%2F1MUfnkIBDtcLEIzI2f3Y1x7mi0U%3D&reserved=0>

Diff files showing all changes:
 https://www.rfc-editor.org/authors/rfc9319-diff.html<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9319-diff.html&data=05%7C01%7Ckotikalapudi.sriram%40nist.gov%7C90bcf13c011645f2d73208daa5713493%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638004202921984225%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bvIBWw5Yo2KxbZ%2FSZNNz2wzyvo%2Baty4eXPSQMyi7HTw%3D&reserved=0>
 https://www.rfc-editor.org/authors/rfc9319-rfcdiff.html<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9319-rfcdiff.html&data=05%7C01%7Ckotikalapudi.sriram%40nist.gov%7C90bcf13c011645f2d73208daa5713493%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638004202921984225%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=teO0qodJtem1eBYeoIiUQFLxxwWSrTYdJlsXi2cE0qE%3D&reserved=0> (side-by-side diff)
 https://www.rfc-editor.org/authors/rfc9319-alt-diff.html<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9319-alt-diff.html&data=05%7C01%7Ckotikalapudi.sriram%40nist.gov%7C90bcf13c011645f2d73208daa5713493%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638004202921984225%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=IJNA%2FjsO90vrDSAXmig6i1p%2FiaX%2BVax53otSA0BEyEQ%3D&reserved=0> (shows changes where text was moved/deleted)

For the AUTH48 status of this document, please see:
 https://www.rfc-editor.org/auth48/rfc9319<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauth48%2Frfc9319&data=05%7C01%7Ckotikalapudi.sriram%40nist.gov%7C90bcf13c011645f2d73208daa5713493%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638004202921984225%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GQUJkHbq7ksbv%2F73HNt1XLd4mIBH0W6KOiGndJz1VPI%3D&reserved=0>

Thank you,

RFC Editor/rv



> On Sep 29, 2022, at 11:23 PM, Ben Maddison <[e-mail]<mailto:[e-mail]>> wrote:
>
> Hi Sriram, Rebecca,
>
> On 09/30, Sriram, Kotikalapudi (Fed) wrote:
>>> We have updated the document. We would like to check with you on one
>>> more thing. RFC 6811 is frequently cited for "RPKI-based Route Origin
>>> Validation (ROV)" and "ROV" in this document; however, RFC 6811
>>> doesn't include the acronym ROV, though it does discuss "Origin
>>> Validation". Will this cause any problems for readers?
>>
> [..]
>>
>> Just so we are on the same page: I have replaced RPKI-based ROV in the
>> first paragraph with ROV. The abstract includes 'RPKI-based Route
>> Origin Validation (ROV)' and the first use of ROV in the Introduction
>> is the paragraph cited above (Considerations....).
>
> I have no problem with this change.
>
> Subject to the above final edit, I approve for RFC publication.
>
> Cheers,
>
> Ben