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

[Rebecca VanRheenen <[e-mail]>]

Sriram,

No worries. We’ll wait to move forward until you, your coauthors, and AD discuss your suggestion and decide on the how to proceed.

Thank you,
RFC Editor/rv



> On Oct 3, 2022, at 1:41 PM, Sriram, Kotikalapudi (Fed) <[e-mail]> wrote:
> 
> Rebecca,
> 
> Please hold. I am sorry. I have some thoughts and I was about to hit 'send'. May be worth while considering it before we finalize.
> 
> Please see my email that follows.
> 
> Sriram 
> 
> -----Original Message-----
> From: Rebecca VanRheenen <[e-mail]> 
> Sent: Monday, October 3, 2022 4:36 PM
> To: Ben Maddison <[e-mail]>; Sriram, Kotikalapudi (Fed) <[e-mail]>; [e-mail]; [e-mail]; Job Snijders <[e-mail]>; Warren Kumari <[e-mail]>
> Cc: RFC Editor <[e-mail]>; [e-mail]; [e-mail]; Chris Morrow <[e-mail]>; [e-mail]
> Subject: [AD] Re: AUTH48: RFC-to-be 9319 <draft-ietf-sidrops-rpkimaxlen-15> for
> 
> Ben and *AD,
> 
> Ben, thank you for the clarification and for your patience as we figured this out. Per your reply, we do not believe any further changes are needed.
> 
> Warren, as *AD, please review and approve the added text at the end of Section 1 (we consider added text to be above editorial). This added text is best viewed in one of the following diff files: 
> 
>  https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9319-auth48diff.html&amp;data=05%7C01%7Ckotikalapudi.sriram%40nist.gov%7Cce027289ac28474cf14208daa57eff6b%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638004262141478944%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=uDiPvpxsMCResgenyWvfl%2BxsifMnYIYt3Zx7fj%2Fhhx8%3D&amp;reserved=0 (shows all changes made in AUTH48)
>  https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauthors%2Frfc9319-alt-diff.html&amp;data=05%7C01%7Ckotikalapudi.sriram%40nist.gov%7Cce027289ac28474cf14208daa57eff6b%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638004262141478944%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=4BS%2FyqF1Vi90OL9CWbh44k34G043odThFXHoC9mD4mA%3D&amp;reserved=0 (shows all changes).
> 
> Thank you,
> RFC Editor/rv
> 
> 
> 
>> On Oct 3, 2022, at 11:57 AM, Ben Maddison <[e-mail]> wrote:
>> 
>> 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]>
>> Sent: Monday, October 3, 2022 8:15:50 PM
>> To: Ben Maddison <[e-mail]>; Sriram, Kotikalapudi (Fed) 
>> <[e-mail]>; [e-mail] 
>> <[e-mail]>; [e-mail] <[e-mail]>; Job 
>> Snijders <[e-mail]>
>> Cc: RFC Editor <[e-mail]>; [e-mail] 
>> <[e-mail]>; [e-mail] 
>> <[e-mail]>; Chris Morrow <[e-mail]>; 
>> Warren Kumari <[e-mail]>; [e-mail] 
>> <[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://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Fauth48%2Frfc9319&amp;data=05%7C01%7Ckotikalapudi.sriram%40nist.gov%7Cce027289ac28474cf14208daa57eff6b%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638004262141478944%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=HQFcLlR4K4dTMV84NdJTC7g7fZ3ugWSDlSLgd%2FGDioo%3D&amp;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://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
>> rfc-editor.org%2Fauthors%2Frfc9319.xml&amp;data=05%7C01%7Ckotikalapudi
>> .sriram%40nist.gov%7Cce027289ac28474cf14208daa57eff6b%7C2ab5d82fd8fa47
>> 97a93e054655c61dec%7C1%7C0%7C638004262141478944%7CUnknown%7CTWFpbGZsb3
>> d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7
>> C3000%7C%7C%7C&amp;sdata=dcDyoBbSBPQh93FzxSI9cnBD65H9i1X59e6mKOCfc%2Fg
>> %3D&amp;reserved=0
>> 
>> Updated output files:
>> 
>> https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
>> rfc-editor.org%2Fauthors%2Frfc9319.txt&amp;data=05%7C01%7Ckotikalapudi
>> .sriram%40nist.gov%7Cce027289ac28474cf14208daa57eff6b%7C2ab5d82fd8fa47
>> 97a93e054655c61dec%7C1%7C0%7C638004262141478944%7CUnknown%7CTWFpbGZsb3
>> d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7
>> C3000%7C%7C%7C&amp;sdata=7n3oX2ErLTvA6ymFDxKy%2BL1YyKua0Lc1QoNBiOHgxVY
>> %3D&amp;reserved=0
>> 
>> https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
>> rfc-editor.org%2Fauthors%2Frfc9319.pdf&amp;data=05%7C01%7Ckotikalapudi
>> .sriram%40nist.gov%7Cce027289ac28474cf14208daa57eff6b%7C2ab5d82fd8fa47
>> 97a93e054655c61dec%7C1%7C0%7C638004262141478944%7CUnknown%7CTWFpbGZsb3
>> d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7
>> C3000%7C%7C%7C&amp;sdata=H%2BF87syttKLKq9DdkjUPyVQ6i0PCi%2B0BPAGTglyH3
>> 4c%3D&amp;reserved=0
>> 
>> https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
>> rfc-editor.org%2Fauthors%2Frfc9319.html&amp;data=05%7C01%7Ckotikalapud
>> i.sriram%40nist.gov%7Cce027289ac28474cf14208daa57eff6b%7C2ab5d82fd8fa4
>> 797a93e054655c61dec%7C1%7C0%7C638004262141478944%7CUnknown%7CTWFpbGZsb
>> 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%
>> 7C3000%7C%7C%7C&amp;sdata=gRV4OfWGEuKWCi30IWql%2BOp2ZNrABEnhnJLlE%2FDq
>> yHs%3D&amp;reserved=0
>> 
>> Diff file showing all changes made during AUTH48:
>> 
>> https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
>> rfc-editor.org%2Fauthors%2Frfc9319-auth48diff.html&amp;data=05%7C01%7C
>> kotikalapudi.sriram%40nist.gov%7Cce027289ac28474cf14208daa57eff6b%7C2a
>> b5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638004262141478944%7CUnknown%
>> 7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJX
>> VCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=uDiPvpxsMCResgenyWvfl%2BxsifMnYIY
>> t3Zx7fj%2Fhhx8%3D&amp;reserved=0
>> 
>> Diff files showing all changes:
>> 
>> https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
>> rfc-editor.org%2Fauthors%2Frfc9319-diff.html&amp;data=05%7C01%7Ckotika
>> lapudi.sriram%40nist.gov%7Cce027289ac28474cf14208daa57eff6b%7C2ab5d82f
>> d8fa4797a93e054655c61dec%7C1%7C0%7C638004262141478944%7CUnknown%7CTWFp
>> bGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn
>> 0%3D%7C3000%7C%7C%7C&amp;sdata=cNLRXc6Kfw5%2FCv9mecvoA%2FaflYHEjRVdRc3
>> LlqijUoA%3D&amp;reserved=0
>> 
>> https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
>> rfc-editor.org%2Fauthors%2Frfc9319-rfcdiff.html&amp;data=05%7C01%7Ckot
>> ikalapudi.sriram%40nist.gov%7Cce027289ac28474cf14208daa57eff6b%7C2ab5d
>> 82fd8fa4797a93e054655c61dec%7C1%7C0%7C638004262141478944%7CUnknown%7CT
>> WFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI
>> 6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=TWqiRuOFXg%2FntO87WPCehKVTOLygHRHQM3
>> 0AaL9CLoU%3D&amp;reserved=0 (side-by-side diff)
>> 
>> https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
>> rfc-editor.org%2Fauthors%2Frfc9319-alt-diff.html&amp;data=05%7C01%7Cko
>> tikalapudi.sriram%40nist.gov%7Cce027289ac28474cf14208daa57eff6b%7C2ab5
>> d82fd8fa4797a93e054655c61dec%7C1%7C0%7C638004262141635167%7CUnknown%7C
>> TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVC
>> I6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=0vjm0NrlApHd%2Bo48qQyCdf5NrmCfYEZCP
>> UUXEVzk67E%3D&amp;reserved=0 (shows changes where text was 
>> moved/deleted)
>> 
>> For the AUTH48 status of this document, please see:
>> 
>> https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
>> rfc-editor.org%2Fauth48%2Frfc9319&amp;data=05%7C01%7Ckotikalapudi.srir
>> am%40nist.gov%7Cce027289ac28474cf14208daa57eff6b%7C2ab5d82fd8fa4797a93
>> e054655c61dec%7C1%7C0%7C638004262141635167%7CUnknown%7CTWFpbGZsb3d8eyJ
>> WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000
>> %7C%7C%7C&amp;sdata=UmD2lIDv8m82DtNWHHKf3EK52BqP0Xoz%2FpFPaAGEi5M%3D&a
>> mp;reserved=0
>> 
>> Thank you,
>> 
>> RFC Editor/rv
>> 
>> 
>> 
>>> On Sep 29, 2022, at 11:23 PM, Ben Maddison <[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
>> 
>