Hi Valery and Brian, Thank you for your replies! We have posted updated files below. We believe that there is now only one outstanding item to address (see inline).
>> I noticed that the following requesting change wasn't done: >> >>> 54) Section 4.4.1 >>> >>> CURRENT: >>> Group policies are comprised of two types: GSA policy and GW policy. >>> >>> Perhaps it is not consistent, but I think that we should re-expand GW here >>> (and perhaps GSA too). >>> GW is defined in the very beginning and is not used up to this point, thus >>> I think it would >>> be helpful for readers to remind what it is. >>> >>> NEW: >>> Group policies are comprised of two types: group SA (GSA) policy and >>> group-wide (GW) policy. >> >> While I admit that the proposed text re-expanded the terms that have already >> been expanded, >> the rationale for it is that this expansion was ~30 pages before, and terms >> were not used since that, >> so re-expansion may help readers to refresh their memory. I don't insist, >> but I think this is helpful. >> Brian, Deb, your opinion? > > I see no issue with re-expanding the terms, but if Madison thinks it isn’t > needed then let’s leave it be. 1) Thank you for pointing this out! This was actually meant to be included in the followup questions sent on 10/2, but must have gotten lost due to the number of changes in the original thread. Apologies for missing this! While making updates to this document, we noticed that there seems to be two different expansions for GSA (Group Security Association and group SA). Is this intentional, or may we make this consistent by replacing instances of "group SA" with the abbreviation "GSA"? If yes, may we also make the following adjustment to the "NEW" text as shown below? Perhaps: Group policies are comprised of two types: Group Security Association (GSA) policy and group-wide (GW) policy. Please review the document carefully to ensure satisfaction as we do not make changes once it has been published as an RFC. Contact us with any further updates or with your approval of the document in its current form. We will await approvals from each author prior to moving forward in the publication process. Updated files have been posted below (please refresh): https://www.rfc-editor.org/authors/rfc9838.txt https://www.rfc-editor.org/authors/rfc9838.pdf https://www.rfc-editor.org/authors/rfc9838.html https://www.rfc-editor.org/authors/rfc9838.xml Updated diff files: https://www.rfc-editor.org/authors/rfc9838-diff.html https://www.rfc-editor.org/authors/rfc9838-rfcdiff.html (side by side) https://www.rfc-editor.org/authors/rfc9838-auth48diff.html https://www.rfc-editor.org/authors/rfc9838-auth48rfcdiff.html (side by side) https://www.rfc-editor.org/authors/rfc9838-lastdiff.html (most recent updates only) https://www.rfc-editor.org/authors/rfc9838-lastrfcdiff.html (side by side) For the AUTH48 status page, please see: https://www.rfc-editor.org/auth48/rfc9838. Thank you! Madison Church RFC Production Center -- auth48archive mailing list -- [email protected] To unsubscribe send an email to [email protected]
