Thanks for the comments Mahesh, Responses inline:
Mahesh Jethanandani via Datatracker <[email protected]> writes: > Section 7.2, paragraph 10 > > * Update the registration policy for the [DS-IANA] registry to match > > the text describing update requirements above. > > > > * Mark values 128 - 252 as "Reserved" > > > > * Mark values 253 and 254 as "Reserved for Private Use" > > > > * Delete the (now superfluous) column "Status" from the registry > > > > Additionally, the registration policy for the [DS-IANA] registry > > should match the text describing the requirements in this document. > > I think the two statements on "registration policy for the [DS-IANA] registry > are confusing. Can we get rid of one of them? Dropped the second. > "Abstract", paragraph 2 > > the status (MUST, MAY, RECOMMENDED, etc) of any of the algorithms listed in > > ^^^ > In American English, abbreviations like "etc." require a period. fixed > "Abstract", paragraph 2 > > tus (MUST, MAY, RECOMMENDED, etc) of any of the algorithms listed in > > RFC8624; > > ^^^^^^^^^ > Consider simply using "of" instead. fixed > Section 1.1, paragraph 4 > > less of implementation status. In general it is expected that deployment of > > ^^^^^^^ > A comma is probably missing here. fixed > > Section 1.2, paragraph 2 > > thms to become used less and less over time. Once an algorithm has reached a > > ^^^^^^^^^ > Did you mean "overtime" (=time someone works beyond normal working > hours)? It should be with a space (https://writingexplained.org/over-time-vs-overtime-difference) > Section 1.2, paragraph 3 > > C2119] considers the term SHOULD equivalent to RECOMMENDED, and SHOULD NOT > > eq > > ^^^^^^^^^^ > The word "equivalent" is a noun or an adjective. A verb is missing or > misspelled, or maybe a comma is missing. "to be" was missing, thanks. -- Wes Hardaker USC/ISI _______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
