Re: [OPSAWG] [Last-Call] [secdir] Secdir last call review of draft-ietf-opsawg-9092-update-09

On Jan 26, 2024, at 3:53 PM, Tim Hollebeek 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

[OPSAWG] Ben Campbell's No Objection on draft-ietf-opsawg-ipfix-bgp-community-11: (with COMMENT)

Ben Campbell has entered the following ballot position for draft-ietf-opsawg-ipfix-bgp-community-11: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however

[OPSAWG] Ben Campbell's No Objection on draft-ietf-opsawg-mud-20: (with COMMENT)

Ben Campbell has entered the following ballot position for draft-ietf-opsawg-mud-20: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https

Re: [OPSAWG] Ben Campbell's No Objection on draft-mm-wg-effect-encrypt-17: (with COMMENT)

the comments, responses and proposals are inline. > > On Wed, Feb 7, 2018 at 12:40 AM, Ben Campbell <b...@nostrum.com> wrote: >> Ben Campbell has entered the following ballot position for >> draft-mm-wg-effect-encrypt-17: No Objection >> >> When responding, please keep

Re: [OPSAWG] Ben Campbell's No Objection on draft-mm-wg-effect-encrypt-17: (with COMMENT)

> On Feb 7, 2018, at 9:08 PM, Spencer Dawkins at IETF > wrote: > > -2.2.1: Please expand "QUIC" and add a citation. > > QUIC started out as an acronym (and went through two or three variations), > but sometime during the chartering process, the expansion was

[OPSAWG] Ben Campbell's No Objection on draft-mm-wg-effect-encrypt-17: (with COMMENT)

Ben Campbell has entered the following ballot position for draft-mm-wg-effect-encrypt-17: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer