Hi, 
I am sorry for the late reply due to seasonal vacation.

I asked my colleague Angela Dall'Ara, Policy Officer at RIPE NCC, to review the document.
She participated in the ASO/RSSAC session at the Istanbul ICANN meeting where the document was discussed.

Her remarks and thoughts are below.
Feel free to incorporate as you see fit.

-hph

---------- Forwarded message ---------
From: Angela Dall'Ara <adallara@ripe.net>
Date: Mon, 6 Jan 2025 at 09:01
Subject: Re: Fwd: [RSSAC Caucus] FOR REVIEW: RSSAC Caucus Guidelines for Changing IP Addresses
To: Hans Petter Holen <hph@ripe.net>


Hi Hans Petter,

Happy New Year to you too!
Thank you for sharing the document, I send you here below my comments as I don't think my name is supposed to appear in the google doc.

I find the document a clear and exhaustive guideline, I only have a couple of observations:
  • In the “Preface” :
1) the last sentence of the first paragraph appears to be incomplete:
In this Advisory, the RSSAC ...
2) the second sentence of the second paragraph is very long and I think it would be clearer if written as a list:
This includes
- communicating on matters relating to the operation of the root servers and their multiple instances with the technical and ICANN community,
- gathering and articulating requirements to offer to for those engaged in technical revisions of the protocols and best common practices related to the operation of DNS servers,
- engaging in ongoing threat assessment and risk analysis of the root server system and recommend any necessary audit activity to assess the current status of root servers and root zone.

  • In “2. Definitions”:
Service Address mentions RSI, which I assume is Route Server Identifier, but I did not find the acronym in RSSAC026v2

  • In “3.1 Selecting a Future Service Address” we read
RSOs are expected to ensure that a future service address does not have a negative reputation in well-known address reputation databases.
I note that RIPE NCC can now allocate via waiting list only returned IPv4 addresses for which routability cannot be guaranteed. It is then up to the RSO to “clean up” the past reputation records.

  • In “3.4 After Decommissioning the Former Service Address” 
I would highlight the fact that different operations (transfers, returns,...) are allowed by the different policies accepted by the community and implemented by the different RIRs, I would change the first sentence in the second paragraph to:
The RSO should remain in control of the former service address indefinitely, or for as long as allowed by the policies implemented by the responsible RIR.
  • Additionally, it would be handy to provide the link to the referenced documents in the notes, but as I'm not familiar with the format of RSSAC documentation, I don't know if this is usually done.

A more detailed explanation of the risks of reusing the addresses previously assigned to route servers would be beneficial if a policy proposal would be submitted for discussion. I’m happy to assist if this is still in the planning.



Kind regards,
Angela

On Thu, 2 Jan 2025 at 16:37, Ray Bellis via rssac-caucus <rssac-caucus@icann.org> wrote:
On 12/12/2024 16:02, Andrew McConachie via rssac-caucus wrote:
> Dear RSSAC Caucus Members,
>
> Duane, Ray and myself met today to discuss the RSSAC Caucus
> Guidelines for Changing IP Addresses Work Party.
>
> We are requesting the full RSSAC Caucus review this publication from
> now until January 8th, 2025.
>
> https://docs.google.com/document/
> d/1ad1aaymsaDkBdBfXYPj19_PbNeIVnu6dQ2lb2L4Asso/
>
> The document is mostly stable. We modified the final two sentences
> of Section 3.4 and marked them as modified text. Otherwise we only
> merged text from our last call.
>
> We are cancelling next week's meeting on December 19th, 2024. The
> work party's next call will be on January 9th, 2025. On that call
> the work party will review comments received in this full Caucus
> review cycle.
Here is a reminder that we're still looking for comments on this
document in advance of next Thursday's call.

Ray

_______________________________________________
rssac-caucus mailing list -- rssac-caucus@icann.org
To unsubscribe send an email to rssac-caucus-leave@icann.org

_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.


--


-hph