On May 28, 2025, at 13:30, Wessels, Duane via rssac-caucus <rssac-caucus@icann.org> wrote:
On May 28, 2025, at 11:40 AM, Paul Hoffman via rssac-caucus <rssac-caucus@icann.org> wrote:
Greetings again. During the RSSAC001v3 work party call yesterday, we discussed possibly combining expectations 3.1.B and 3.2.A. To do this, I propose copying the descriptive text from the beginning of 3.2 ("An RSO is expected to choose hardware, software, and other components that allow it to meet the protocol and deployment requirements specified in BCP 40.") to the end of the paragraph in 3.1 that starts "BCP 40 describes...", removing [E.3.2-A] entirely, and relettering the expectations in the rest of 3.2 up one letter.
Comments are welcome.
This would be easier to do in an editable google doc, but I’m not yet convinced 3.1.B and 3.2.A should be combined.
Note that 3.1.B applies to RSOs collectively, while 3.2.A applies to RSOs individually. I know that was intentional.
<sigh> 3.2-A says that each RSO is expected to do everything in BCP 40 as if each RSO stands alone. Thus, 3.2-A goes beyond BCP 40 to make it per-RSO. Instead of combining them, we might either: - get rid of 3.2-A because it wrongly changes the scope of BCP 40 - get rid of 3.1-B because if every RSO is doing 3.2-A, there is no need for it Thoughts? --Paul Hoffman