> -----Original Message----- > From: Roman Danyliw via Datatracker <[email protected]> > Sent: Sunday, February 14, 2021 2:32 PM > To: The IESG <[email protected]> > Cc: [email protected]; [email protected]; > [email protected]; Jasdip Singh <[email protected]>; [email protected] > Subject: [EXTERNAL] Roman Danyliw's No Objection on draft-ietf-regext- > rfc7483bis-04: (with COMMENT) > > Caution: This email originated from outside the organization. Do not click > links > or open attachments unless you recognize the sender and know the content > is safe. > > Roman Danyliw has entered the following ballot position for > draft-ietf-regext-rfc7483bis-04: 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.)
[SAH] [snip] > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Thank you to Rich Salz for the SECDIR review, and the discussion around it is > appreciated. > > ** Section 3. handle. Per “This value is a simple string”, is this making a > statement about the JSON data type? I didn’t follow what this clarification > added on top of the original text in RFC7483. [SAH] 7483 doesn't mention the data type, so yes, some people felt it necessary to mention that this a string data type. Would "simple character string" be better? > ** Section 3. Editorial. > OLD > The "fn" member is required and MUST NOT be null > according to [RFC6350], where an empty "fn" member MAY be used when > the contact name does not exist or is redacted. > > NEW > The "fn" member is required and MUST NOT be null according to [RFC6350]. > An empty "fn" member MAY be used when the contact name does not exist > or is redacted. [SAH] OK. Scott _______________________________________________ regext mailing list [email protected] https://www.ietf.org/mailman/listinfo/regext
