> -----Original Message----- > From: Ben Campbell <ben@xxxxxxxxxxx> > Sent: Friday, January 26, 2024 5:28 PM > To: Tim Hollebeek <tim.hollebeek@xxxxxxxxxxxx> > Cc: Randy Bush <randy@xxxxxxx>; Tim Hollebeek via Datatracker > <noreply@xxxxxxxx>; secdir@xxxxxxxx; draft-ietf-opsawg-9092- > update.all@xxxxxxxx; last-call@xxxxxxxx; opsawg@xxxxxxxx > Subject: Re: [Last-Call] [secdir] Secdir last call review of draft-ietf-opsawg- > 9092-update-09 > > On Jan 26, 2024, at 3:53 PM, Tim Hollebeek > <tim.hollebeek=40digicert.com@xxxxxxxxxxxxxx> wrote: > > > > Yes, that's the correct paragraph I was referring to. > > > > Unfortunately, RFC 2119 does actually imply that these words can't be > > used in non-2119 ways: > > > > "In many standards track documents several words are used to signify > > the requirements in the specification. These words are often > > capitalized. This document defines these words as they should be > > interpreted in IETF documents." > > > > I would also prefer it if the uncapitalized versions retained their > > original English meanings, but these sentences from 2119 are why I > > recommend avoiding such usages. > > That was updated by RFC 8174 to say “when capitalized”. > > Ben. Oh, awesome. I had somehow missed that this had gotten fixed. -Tim
<<attachment: smime.p7s>>
-- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
