[RSSAC Caucus] Updating RSSAC002, RSSAC023, and RSSAC026 at ICANN 66

Yoshitaka Aharen aharen at jprs.co.jp
Mon Oct 28 10:42:40 UTC 2019


Hello,

I will not be in Montreal in person.
Please let me share some suggestions on draft RSSAC002v4.

[ 3. RSO Measurement Parameters ]

- 2nd item on the list "Size of the overall root zone" should be removed.

[ 6. Interchange Format and Storage ]

- I think YAML uses Unicode character set.  Although RSSAC002 data
  consists of ASCII characters, "the number 0 (ASCII value 48)" in 6th
  item on the list would be better to be rephrased as
  "the number 0 (Unicode codepoint U+0030)".

[ 5.3 The 'traffic-volume' Metric ]

- If the intention to add a sentence "Traffic volumes with nonzero
  counts must be listed"  is to omit elements with zero values,
  it would be better to be rephrased as "Only traffic volumes with..."
  as like section 5.4.

[ 5.6 The 'unique-sources' Metric ]

- If the intention to add a sentence "Unique sources with nonzero
  counts must be listed"  is to omit elements with zero values,
  it would be better to be rephrased as "Only unique sources with..."
  as like section 5.4.

[ 5.7 URL Path Standard ]  (under section 6)

- Definition of short-service for RZM measurement parameters is needed;
  it would be "root" or "rzm".

Best Regards,

-- 
Yoshitaka Aharen <aharen at jprs.co.jp>
Japan Registry Services Co., Ltd.


On Fri, 25 Oct 2019 09:18:24 +0000
Andrew McConachie <andrew.mcconachie at icann.org> wrote:

> Dear RSSAC Caucus Members,
> 
> The RSSAC will work on updating RSSAC002, RSSAC023, and RSSAC026 at ICANN 66.
> 
> The RSSAC Admin Committee has decided not to start work parties on these efforts in order to keep them lightweight. Instead staff will take the lead on organizing these efforts along with an RSSAC Caucus member for guidance. Staff has prepared Google docs with strawman edits to all three of these documents. Please find them below along with links to each session.
> 
> 
> _RSSAC002v4_
> Ken Renard has agreed to help guide the work the work of creating RSSAC002v4.
> 
> RSSAC002v4 Statement of Work
> <https://docs.google.com/document/d/1uKeLGw-E02CYop0XaRaN8LLCw71QskI1vPf9C_iUBj8/edit?usp=sharing>
> 
> Draft version of RSSAC002v4
> <https://docs.google.com/document/d/1na7VpPYfo4VEBfQMHwix6I2Puohvc1hvwRh0aW1cmFE/edit?usp=sharing>
> 
> RSSAC002v4 will be discussed in ICANN 66 RSSAC work session 2
> <https://66.schedule.icann.org/meetings/1116777>
> 
> 
> _RSSAC023v2_
> Paul Hoffman has agreed to help guide the work of creating RSSAC023v2.
> 
> Draft version of RSSAC023v2
> <https://docs.google.com/document/d/16FaQzGJnqBsy5zk4xmLPU2v7FUqLQT8readmSYI-ve0/edit?usp=sharing>
> 
> RSSAC023v2 will be discussed in ICANN 66 RSSAC work session 1
> <https://66.schedule.icann.org/meetings/1116776>
> 
> 
> _RSSAC026v2_
> Paul Hoffman has agreed to help guide the work of creating RSSAC026v2.
> 
> Draft version of RSSAC026v2
> <https://docs.google.com/document/d/14Un1lCkek4aAyCi9a_oBcoRP02kJ72NtX1ic-LDlb58/edit?usp=sharing>
> 
> RSSAC026v2 will be discussed in ICANN 66 RSSAC work session 1
> <https://66.schedule.icann.org/meetings/1116776>
> 
> Thanks,
> Andrew





More information about the rssac-caucus mailing list