IETF Logo Mail Archive

Re: [stir] WGLC: draft-ietf-stir-passport-rcd-09

Russ Housley <housley@vigilsec.com> Tue, 10 May 2022 15:14 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DCCAC14EB1F for <stir@ietfa.amsl.com>; Tue, 10 May 2022 08:14:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kTQgg6MFsVtE for <stir@ietfa.amsl.com>; Tue, 10 May 2022 08:14:16 -0700 (PDT)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E72EC14F723 for <stir@ietf.org>; Tue, 10 May 2022 08:14:16 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 2F8FDED0E8 for <stir@ietf.org>; Tue, 10 May 2022 11:14:15 -0400 (EDT)
Received: from [10.0.1.2] (pfs.iad.rg.net [198.180.150.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 25A85ED527 for <stir@ietf.org>; Tue, 10 May 2022 11:14:15 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Tue, 10 May 2022 11:14:14 -0400
References: <5393b70d-bfc7-c8ac-eb8d-30c8087a1e89@nostrum.com> <6981C79A-4024-4291-B2BB-A969EF8FD930@vigilsec.com>
To: IETF STIR Mail List <stir@ietf.org>
In-Reply-To: <6981C79A-4024-4291-B2BB-A969EF8FD930@vigilsec.com>
Message-Id: <EC476731-83E2-4393-ADE8-E4D9B80D4636@vigilsec.com>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/HhOrO6gJ56m4npCLmlNl7WSYjCA>
Subject: Re: [stir] WGLC: draft-ietf-stir-passport-rcd-09
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2022 15:14:20 -0000

I am not sure that a change is needed, but I just made another pass through the document that raised a small question.

Looking at the following snippets from the document:

   Traditional telephone network signaling protocols have long supported
   delivering a 'calling name' from the originating side, ...

   ... The first data is a more
   traditional set of info about a caller associated with "display-name" ...

   ...  alternate presentation numbers often used in From Header field ...

I could use an explanation about the conventions being used to reference the various fields that are defined in other documents.  Single quote, double quote, and capital letters all play a role.

It is made more confusing to me because double quotes are used to identify claims and also around jargon (examples: "Caller ID" and "vet").

Russ

> On Apr 25, 2022, at 3:51 PM, Russ Housley <housley@vigilsec.com> wrote:
> 
> This might be the longest WG Last Call in history ....
> 
> A new version was just posted: https://www.ietf.org/id/draft-ietf-stir-passport-rcd-17.txt
> 
> Regarding the ongoing WG Last Call, we have two questions:
> 
> (1) Have any of the changes introduced new issues?
> 
> (2) Have all previously raised issues are resolved?
> 
> For the STIR WG Chairs,
>  Russ
> 
> 
>> On Dec 8, 2020, at 4:30 PM, Robert Sparks <rjsparks@nostrum.com> wrote:
>> 
>> This is a WGLC for draft-ietf-stir-passport-rcd-09.
>> 
>> Please send reviews to the list by the end of day 22 Dec 2020.
>> 
>> If you plan to provide a review but need more time, please let us know early.
>> 
>> See <https://datatracker.ietf.org/doc/draft-ietf-stir-passport-rcd/>
>> 
>> RjS
> 
> _______________________________________________
> stir mailing list
> stir@ietf.org
> https://www.ietf.org/mailman/listinfo/stir

v2.23.0 | Report a Bug | By Email