FOR REVIEW: RSSAC026v2 RSSAC Lexicon version 2
Dear RSSAC Caucus Members, The RSSAC Caucus held a call on February 11th to discuss RSSAC026v2: RSSAC Lexicon. Since the call I’ve worked with Paul Hoffman to resolve all the issues brought up on the call. There are no outstanding issues remaining on this document. Please review this document and provide any feedback by Thursday February 27th. <https://docs.google.com/document/d/14Un1lCkek4aAyCi9a_oBcoRP02kJ72NtX1ic-LDl...> Please suggest any edits in the document, and for any discussion issues please reply all to this message. Thanks, Andrew
since I had few minutes this morning, I looked through it and I have a few comments: a) why does DITL rate a special mention? b) why is anycast not mentioned specifically? c) why the use of the term "root server” used as a collective noun, whereas the industry convention is to use the term “server” in a more unitary sense to denote an instance of a operating system stack. I had heard in the past the term “root letter” to denote the collection of instances operated by a root server operator, and the use of “root server” in this context is a new one on me regards, Geoff
On 14 Feb 2020, at 3:25 am, Andrew McConachie <andrew.mcconachie@icann.org> wrote:
Dear RSSAC Caucus Members,
The RSSAC Caucus held a call on February 11th to discuss RSSAC026v2: RSSAC Lexicon. Since the call I’ve worked with Paul Hoffman to resolve all the issues brought up on the call. There are no outstanding issues remaining on this document.
Please review this document and provide any feedback by Thursday February 27th. <https://docs.google.com/document/d/14Un1lCkek4aAyCi9a_oBcoRP02kJ72NtX1ic-LDl...>
Please suggest any edits in the document, and for any discussion issues please reply all to this message.
Thanks, Andrew _______________________________________________ rssac-caucus mailing list rssac-caucus@icann.org https://mm.icann.org/mailman/listinfo/rssac-caucus
_______________________________________________ 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.
On Feb 13, 2020, at 4:08 PM, Geoff Huston <gih@apnic.net> wrote:
a) why does DITL rate a special mention?
It is a term that appears in other RSSAC documents that is not widely known by all readers.
b) why is anycast not mentioned specifically?
We tried but failed. Different folks have very different views of how to define it. Do you feel that a definition of anycast is required in order to understand instances? If so, what part?
c) why the use of the term "root server” used as a collective noun, whereas the industry convention is to use the term “server” in a more unitary sense to denote an instance of a operating system stack. I had heard in the past the term “root letter” to denote the collection of instances operated by a root server operator, and the use of “root server” in this context is a new one on me
This was heavily discussed on the list over the past month. So far, there is a strong agreement not to use "root letter" or anything about letters. --Paul Hoffman
On 14 Feb 2020, at 12:52 pm, Paul Hoffman <paul.hoffman@icann.org> wrote:
On Feb 13, 2020, at 4:08 PM, Geoff Huston <gih@apnic.net> wrote:
a) why does DITL rate a special mention?
It is a term that appears in other RSSAC documents that is not widely known by all readers.
fair enough I guess - it still seems discordant to me to pick out this particular program within the scope of this document.
b) why is anycast not mentioned specifically?
We tried but failed. Different folks have very different views of how to define it. Do you feel that a definition of anycast is required in order to understand instances?
yes
If so, what part?
err - can’t parse this question. "what part” of what? Of “instances” or of “anycast” or of “”something else entirely”? Can you rephrase your question please?
c) why the use of the term "root server” used as a collective noun, whereas the industry convention is to use the term “server” in a more unitary sense to denote an instance of a operating system stack. I had heard in the past the term “root letter” to denote the collection of instances operated by a root server operator, and the use of “root server” in this context is a new one on me
This was heavily discussed on the list over the past month. So far, there is a strong agreement not to use "root letter" or anything about letters.
Even so it does seem slightly jarring to me to see technical terms that have accepted meanings in other realms be redefined in what I would say is completely different way in this context. Agreement or not, borrowing a term that means something in most other contests (a singular host of a service) to redefine it as a collective noun solely in the root server context seems to be odd. It seems to be adding subject-specific jargon rather than de-mystifying it. thanks, Geoff
On Thu, Feb 13, 2020 at 6:02 PM Geoff Huston wrote:
Even so it does seem slightly jarring to me to see technical terms that have accepted meanings in other realms be redefined in what I would say is completely different way in this context.
To be fair, your point is both valid and invalid at the same time. I think the term has been shifting, in large part due to cloud computing's blurring of the line. EG, phrases like "google's web server" are still heard, and clearly that statement involves multiple servers not one. The audience for this document is wider than just the technical community as well (or else I'd be more inclined to think you might have a strong point). -- Wes Hardaker USC/ISI
On Friday, 14 February 2020 01:52:34 UTC Paul Hoffman wrote:
On Feb 13, 2020, at 4:08 PM, Geoff Huston <gih@apnic.net> wrote:
b) why is anycast not mentioned specifically?
We tried but failed. Different folks have very different views of how to define it. Do you feel that a definition of anycast is required in order to understand instances? If so, what part?
perhaps we can just reference RFC 1546, 4786, and 7094, without copying any of their definitions, and leave it up to the reader to decide which one is right. -- Paul
participants (5)
-
Andrew McConachie -
Geoff Huston -
Paul Hoffman -
Paul Vixie -
Wes Hardaker