[stir] Paul Wouters' No Objection on draft-ietf-stir-passport-rcd-23: (with COMMENT)

Paul Wouters via Datatracker <noreply@ietf.org> Thu, 01 December 2022 02:01 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Paul Wouters via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-stir-passport-rcd@ietf.org, stir-chairs@ietf.org, stir@ietf.org, housley@vigilsec.com, housley@vigilsec.com
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Paul Wouters <paul.wouters@aiven.io>
Message-ID: <166986010556.52425.68836279540068042@ietfa.amsl.com>
Date: Wed, 30 Nov 2022 18:01:45 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/LFJFTGrPWGQOfPnoAT4nrGyRvYw>
Subject: [stir] Paul Wouters' No Objection on draft-ietf-stir-passport-rcd-23: (with COMMENT)

Paul Wouters has entered the following ballot position for
draft-ietf-stir-passport-rcd-23: 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://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-stir-passport-rcd/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

# Sec AD review of  draft-ietf-stir-passport-rcd-23

CC @paulwouters

See https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions
for more information about how to handle DISCUSS and COMMENT positions.

This review uses the format specified in https://github.com/mnot/ietf-comments/
which allows automated tools to process items (eg to produce github issues)

Please see Roman's raised issues. Additionally, I have a few very minor
comments.

## Comments

### Section 8.3 example

the example there has a jCard with:

       ["org",{},"text","MI6;Q Branch Spy Gadgets"],

and a corresponding PASSporT claims object with:

     "nam": "Q Branch Spy Gadgets",

I wasn't sure if the org text and nam of the issuer needed to match here, so I
just wanted to raise it in case this is a copy&paste error.

## odd modifier to 2119 language

I am not sure how to read:
```
        is likely NOT RECOMMENDED best practice.
```

It seems it should either not use RFC 2119 phrasing, or it should remove the
modifier "likely".

### NITS

[3GPP TS 24.229 v16.7.0] is not rendered into a proper reference

There is a few ways -> There are a few ways

Section 16 references "the IANA", instead of just "IANA".

[stir] Paul Wouters' No Objection on draft-ietf-s… Paul Wouters via Datatracker