
From nobody Tue Dec  8 09:52:35 2020
Return-Path: <session-request@ietf.org>
X-Original-To: stir@ietf.org
Delivered-To: stir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D9303A10CA; Tue,  8 Dec 2020 09:52:26 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: stir-chairs@ietf.org, superuser@gmail.com, housley@vigilsec.com, stir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.23.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160744994629.15620.13392269646004811262@ietfa.amsl.com>
Date: Tue, 08 Dec 2020 09:52:26 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/TWsyzZ68xgFButxXjeZHAZwIJiQ>
Subject: [stir] stir - New Meeting Session Request for IETF 110
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.29
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, 08 Dec 2020 17:52:34 -0000

A new meeting session request has just been submitted by Russ Housley, a Chair of the stir working group.


---------------------------------------------------------
Working Group Name: Secure Telephone Identity Revisited
Area Name: Applications and Real-Time Area
Session Requester: Russ Housley


Number of Sessions: 1
Length of Session(s):  1 Hour
Number of Attendees: 60
Conflicts to Avoid: 
 Chair Conflict: ipwave lamps suit
 Technology Overlap: sipcore ecrit
 Key Participant Conflict: dispatch secdispatch saag sipbrandy tls mls teep oauth acme perc cfrg mmusic avtcore emu





People who must be present:
  Russ Housley
  Robert Sparks
  Eric Burger
  Jon Peterson
  Martin Dolly
  Murray Kucherawy
  Brian Rosen
  Chris Wendt

Resources Requested:

Special Requests:
  
---------------------------------------------------------



From nobody Tue Dec  8 13:31:07 2020
Return-Path: <rjsparks@nostrum.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 096FC3A1199 for <stir@ietfa.amsl.com>; Tue,  8 Dec 2020 13:31:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.079
X-Spam-Level: 
X-Spam-Status: No, score=-2.079 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nostrum.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X3gW0NeZ3p3c for <stir@ietfa.amsl.com>; Tue,  8 Dec 2020 13:31:01 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 689463A110A for <stir@ietf.org>; Tue,  8 Dec 2020 13:31:01 -0800 (PST)
Received: from unformal-11.home ([47.186.0.128]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 0B8LV0eg047886 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <stir@ietf.org>; Tue, 8 Dec 2020 15:31:00 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1607463060; bh=BOdC9YtreMXIlE3FBvtYs6uEgxbcpzwB0KM3fjb2YP8=; h=To:From:Subject:Date; b=sBKi9SccnVaWII8cegKw2bTxEkABk/j0aSIB9aLnYA6Tv7UOYdAFVdKV1qbf2bofh 3vzxsyP80OoI2cIFtwQvTmxAsF7nghvXBqbyRpghcXqadZ6y62Xb9LMkc6+WsFqVgo xyzW60QYtE95mbdLK9QNGs4NcsVYgkjFN1Bn09SI=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.0.128] claimed to be unformal-11.home
To: stir@ietf.org
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <5393b70d-bfc7-c8ac-eb8d-30c8087a1e89@nostrum.com>
Date: Tue, 8 Dec 2020 15:30:55 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/PY1f_jagLQe7BYfBVC5u5GbE0uI>
Subject: [stir] WGLC: draft-ietf-stir-passport-rcd-09
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.29
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, 08 Dec 2020 21:31:06 -0000

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


From nobody Thu Dec 10 15:17:23 2020
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 E37673A132A for <stir@ietfa.amsl.com>; Thu, 10 Dec 2020 15:17:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1AaaylriIy_R for <stir@ietfa.amsl.com>; Thu, 10 Dec 2020 15:17:20 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CAE43A1329 for <stir@ietf.org>; Thu, 10 Dec 2020 15:17:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id A95C1300BC6 for <stir@ietf.org>; Thu, 10 Dec 2020 18:17:17 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id OnJs_n5F3OXK for <stir@ietf.org>; Thu, 10 Dec 2020 18:17:16 -0500 (EST)
Received: from dynamic-005-005-033-020.5.5.pool.telefonica.de (unknown [204.194.23.17]) by mail.smeinc.net (Postfix) with ESMTPSA id 13DF5300ADC; Thu, 10 Dec 2020 18:17:16 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <5393b70d-bfc7-c8ac-eb8d-30c8087a1e89@nostrum.com>
Date: Thu, 10 Dec 2020 18:17:17 -0500
Cc: IETF STIR Mail List <stir@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <04DA61EB-2662-40AF-B0AF-EDD39C019668@vigilsec.com>
References: <5393b70d-bfc7-c8ac-eb8d-30c8087a1e89@nostrum.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/nglhnIa0ZKCIcKSB5ROkUBDC4hU>
Subject: Re: [stir] WGLC: draft-ietf-stir-passport-rcd-09
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 10 Dec 2020 23:17:23 -0000

The Abstract seems a bit long.  I think these points belong in the =
Abstract:

  - Extends PASSporT from RFC 8225 to include RCD
  - Extend caller and call specific information beyond human-readable =
display
   name comparable to the telephone network "Caller ID"
 - RCD is extensible
 - RCD when coupled with STIR provides signature over the information
 - RCD can also be used with SIP Call-Info

General: This appears many times: "Rich Call Data (RCD)".  Once in the =
Introduction should be enough.

Section 2: Ha ha. Please use:

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Section 3: "Additionally, [I-D.ietf-sipcore-callinfo-rcd] also ..."  =
Please drop "also".

Section 5.1: What does "default" mean?  I think you mean that this is =
the inital set of keys, and more can be added in the future.

Section 5.1.4: Please add a reference to:

   [SHS]      National Institute of Standards and Technology (NIST),
              "Secure Hash Standard", FIPS Publication 180-4, August
              2015.

Also, I I suggest a bit or rewording::

   implementations MUST support the SHA-256, SHA-384, and SHA-512 hash =
algorithms [SHS].

Finally, if other hash algorithms MAY be supported, do we need an IANA =
registry for the strings associated with the other algorithms?

Section 6.1: Clearly the phone number should be 1-202-555-0007 ...

Russ


> On Dec 8, 2020, at 4:30 PM, Robert Sparks <rjsparks@nostrum.com> =
wrote:
>=20
> This is a WGLC for draft-ietf-stir-passport-rcd-09.
>=20
> Please send reviews to the list by the end of day 22 Dec 2020.
>=20
> If you plan to provide a review but need more time, please let us know =
early.
>=20
> See <https://datatracker.ietf.org/doc/draft-ietf-stir-passport-rcd/>
>=20
> RjS
>=20
> _______________________________________________
> stir mailing list
> stir@ietf.org
> https://www.ietf.org/mailman/listinfo/stir


From nobody Tue Dec 15 07:32:07 2020
Return-Path: <Jack.Rickard@metaswitch.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 5302B3A11E9 for <stir@ietfa.amsl.com>; Tue, 15 Dec 2020 07:32:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=metaswitch.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z9-y0sqA6wrn for <stir@ietfa.amsl.com>; Tue, 15 Dec 2020 07:32:04 -0800 (PST)
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (mail-bn8nam12on2116.outbound.protection.outlook.com [40.107.237.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A16E73A11DA for <stir@ietf.org>; Tue, 15 Dec 2020 07:32:04 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=jAj/1CAafxoALv8WTyfLbKWm/FVnP4o8v95pznTFA5gyksI7g5j1E+f6rn5dEP7F/JIxxDlA+ZpjEFU2aoVk+yLtaozWslMCR0pNJoCjk2bIpZuuIoOCtV/0ZlSPnK9xtCXf+mXoWj0BAbKhJo1vOEzjrcjt9LqP25NF3jEdWkCf4C53NOe5VcKvqftQeml7vHFdQ+ow6HaF6Ut998ygXFL3pl5JDvK283suqS0nx3ON2WGEQOepphhD57e9nkp1f9AOcVyjitKot4jobQLCgvlZDilh6RzSmNJiUpM6Q+dQhB/+fi50rFZ67pqOcB44pZ208jPIv/EHU4QOYLXhaw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uuqpdd4kXfSQlB2qMrUR2TZErABDh519inTM5afB+YA=; b=KXpuoJcnwulbPUU/95/CAHDzg2rDUtWXC/nURxLGc5GEYw2PEhagmQQxVcucCOOpSyWKl1Xl8CO4kWZ27uY1aPLRQpXZ3+YLSoWcwzXTO/B2BHybhFMwb/5pHnxFuNX5GDekz7DBIAAprsOyPAXL/y6D+sEtyek/e4ujLIwsrv8d/z8SdqW/C8mmnHxoBDszPkheN9/C8iJx5MVWP3lnvR1V2tpItW32xt0cu7cQJHnuIX/J3kApPmKYd+nbRbWRLYvAivh1TkAn4jipQ5ssVg3x6rtqbos8ZWNd8r9edgBbw8QvcD6txpS54oZSy4N2IiMAVKuSUOs/oEeFP7u74g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=metaswitch.com; dmarc=pass action=none header.from=metaswitch.com; dkim=pass header.d=metaswitch.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=metaswitch.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uuqpdd4kXfSQlB2qMrUR2TZErABDh519inTM5afB+YA=; b=OhWX9x5O63ctIVmQOSFiqsSpqWdl4uVGBGqE5updH59USU3pbhgsh7CcjleEeW+Tfdtor0Fc3AwwK42BCm3wD812ALJ/IMrIwYGpz1j3tDz42UJB6fM2Igb7GdihrsotL8LgsEGjaKLqyvQdDeH5jPZE9VipsYPcCYB191puR8c=
Received: from BYAPR02MB5189.namprd02.prod.outlook.com (2603:10b6:a03:62::29) by BY5PR02MB6611.namprd02.prod.outlook.com (2603:10b6:a03:205::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3654.12; Tue, 15 Dec 2020 15:32:01 +0000
Received: from BYAPR02MB5189.namprd02.prod.outlook.com ([fe80::5024:252e:5379:9b69]) by BYAPR02MB5189.namprd02.prod.outlook.com ([fe80::5024:252e:5379:9b69%7]) with mapi id 15.20.3654.024; Tue, 15 Dec 2020 15:32:00 +0000
From: Jack Rickard <Jack.Rickard@metaswitch.com>
To: Robert Sparks <rjsparks@nostrum.com>, "stir@ietf.org" <stir@ietf.org>
Thread-Topic: [stir] WGLC: draft-ietf-stir-passport-rcd-09
Thread-Index: AQHWzal4sl0rkqFiUkmCbI9EqdgN8qn4D1gg
Date: Tue, 15 Dec 2020 15:32:00 +0000
Message-ID: <BYAPR02MB51894A12EACDCE143C491983F3C60@BYAPR02MB5189.namprd02.prod.outlook.com>
References: <5393b70d-bfc7-c8ac-eb8d-30c8087a1e89@nostrum.com>
In-Reply-To: <5393b70d-bfc7-c8ac-eb8d-30c8087a1e89@nostrum.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: nostrum.com; dkim=none (message not signed) header.d=none; nostrum.com; dmarc=none action=none header.from=metaswitch.com; 
x-originating-ip: [84.92.33.46]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: cf339fb9-4529-4f78-b965-08d8a10e9109
x-ms-traffictypediagnostic: BY5PR02MB6611:
x-microsoft-antispam-prvs: <BY5PR02MB6611463CEE88AFBB8BE58598F3C60@BY5PR02MB6611.namprd02.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6790;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: qAbBYq5ZT2ANRnn99JzCKc/wBr+2+HF8YERIPaXeyhUBrQgQYT00RwZkXLomDBqLBUaZwQ85B8+JsOGzvDdM6juIIFOgEvUcz9Zw0Gdom1vl/EMretEs8JSVSV5ZIVwogpxzATUqwmVr2J9RWG49uX/CF678aIAJH11fzAfL7eADzyiMwKhLQmKNOL5Wzo7+8ClSr0bGMCxC9kAg4X99UGz4ZwD9mIMyr3ggAoSJkJv9GwpipsOrauxOIA+VN49QjFzepcow+4g7VOu/Wjd08kkbuHc3Skj955wZqcKSBinGuQGCGzWHa3OMW00/nrsHUgiMmM37Wlwue0ujc1ZdkmwGtn7QB4A5ibwRCAaepSmnkX21KCBMT+8g8SPpo9zCDH/Ovv0gqwe4acTfVLYkSA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:BYAPR02MB5189.namprd02.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(366004)(136003)(376002)(346002)(66476007)(64756008)(7696005)(2906002)(55016002)(66446008)(66946007)(52536014)(45080400002)(8676002)(33656002)(8936002)(508600001)(110136005)(9686003)(66556008)(86362001)(6506007)(26005)(5660300002)(53546011)(83380400001)(186003)(71200400001)(966005)(76116006); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: =?us-ascii?Q?mXs5P5k/12mANlDw7ro+AfJH4sYwHB8r9neG19z8s9nvr+UeW+TnVKFrX0nr?= =?us-ascii?Q?aYA4wP8vJJJgiOCHFLo/JHXeFQZrKcGhg81NwZodVrn7zIbE3S/QQ1OqEbcG?= =?us-ascii?Q?VOTOUIreTR5LQH2dp2frdtH6i8arIW1Ko1oxWgV3sntkg3sV7z0LC+r/4MoL?= =?us-ascii?Q?xjuFH2CFVMZKpSs0LTcCeJIhUN0N7Hnb8ibD7E3BPOmXop3K2Yg37NPHprZO?= =?us-ascii?Q?ZG086Z1up+Xc28VeHzwlIwJjP5XopKRw5x+JL15VNIDuh7vCAeT2VAMlQJwN?= =?us-ascii?Q?yh6o6yY81RmRK2IvLXlySlXnxNRXRMgQLVxwygQhugO9LgdBzr0UlBbSaNFt?= =?us-ascii?Q?cn28gO0y1iNqK2tag0GQY5+2qlslQeLgz/kEve4lXwzjIocWSKlTHKldyiI3?= =?us-ascii?Q?J/FngjYGUnyV/8m7lAyepQmFt/4+GutymALdKgWKcD93Z1kGj5nC8BrTn9jy?= =?us-ascii?Q?0CW8+kS5RuOJmPrdFctNbwkIOBwJmyfxi6Iu5HUanaTfLZNGh9+fnQgMrV9Y?= =?us-ascii?Q?zD0IFaBaE0ot+tCpMdhoIpfbiS1iHgx0PxSJml/dJnophaTdMNFgndFWsJmv?= =?us-ascii?Q?ZMK6M4XK3HC2nb4kYG4in+fRzP9Bzb+kwRF2x6rsmaImaQgBYhoNPWjkAMO4?= =?us-ascii?Q?C4gXHpT+7OI1g8Pj8lzR73DOV49VXChlz1mZ4PF8H671sIa+QN3Bp+2UXBs6?= =?us-ascii?Q?aKFqgbjd5th06G/kdWtMP45TLwhw12ivigYWsDmTat1eLOrWnd5eOKjuM8FY?= =?us-ascii?Q?OEATmgnurYbQYPv/JoNaqNtH+9UoNFINni+w9Aup/qb7t+hPjt6ia5aKsNei?= =?us-ascii?Q?HSbIYSGQ825YcRKGTBDarsMTQnhWujQeqzXdx8pcoYhFrZ19tamhFr2Xoyrx?= =?us-ascii?Q?GMeqQB4dtIVnCE4gcF2l6qTY+kGqv1yBOc1FNQGfyxhTTBt1fYNq/G8/UsWW?= =?us-ascii?Q?LLH1mM8It6PYyprMiKtpWFgmiigvPUhqrzkjA9cIR04=3D?=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: metaswitch.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BYAPR02MB5189.namprd02.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: cf339fb9-4529-4f78-b965-08d8a10e9109
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Dec 2020 15:32:00.6493 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9d9e56eb-f613-4ddb-b27b-bfcdf14b2cdb
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Om+/MK7jgQzKKzzGoL8JGU6JIMwij5+Tm0Q6z7qxDG3rsAmWNFAM2vDaJ7rmWSiDtQhm1lCF1qiyMS+LejtLrA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY5PR02MB6611
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/85TnSpJWm9wHXVshpbQZMT0bgkM>
Subject: Re: [stir] WGLC: draft-ietf-stir-passport-rcd-09
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.29
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, 15 Dec 2020 15:32:06 -0000

Comments:
Section 9.1: Is the "iss" claim meaning specified anywhere else? This part =
reads like it is referencing some existing behaviour but I am unable to fin=
d anything defining it. I ask because this doesn't feel like it should be s=
pecific to this standard and would be useful for, for example, RPH where th=
e cert identifies the source of the prioritisation.

Section 9.1: "the value of "iss" however MUST reflect the Subject Name fiel=
d" is unclear, the "MUST" is very strong but the "reflect" very vague, shou=
ld it equal it? If so in what format? I'm also not sure why this is useful,=
 you will already have the subject name of the certificate, as you have to =
have the certificate to verify the signature.

Section 10: How should the passport indicate the relationship of the genera=
tor of the PASSporT to the caller? In the first party case I think you've l=
eft this entirely unspecified, and in the third party case that is not how =
"iss" was defined in the previous section, and it isn't clear how you would=
 go from a third party organisation name to their relationship with the cal=
ler.

Section 5.1.5: The example isn't a valid base64 string (due to the # and *)=
, as JWT's use the URL safe variant of base64 encoding with no padding, it =
would be useful to clarify here which flavour of base64 encoding is being u=
sed.

Nits:
Section 6: I believe "The value of "rcd" is an array of JSON objects" is wr=
ong here, it's a JSON object containing the "name" field, etc.

Section 8: The phrase "potential values of the "rcd" array" is also wrong, =
this isn't an array, something like "potential fields in the "rcd" claim" w=
ould be clearer.

Section 11.1: the example identity here isn't valid, I think it should have=
 ".." preceeding the PASSport and no trailing "=3D".

Thanks,
Jack

-----Original Message-----
From: stir <stir-bounces@ietf.org> On Behalf Of Robert Sparks
Sent: 08 December 2020 21:31
To: stir@ietf.org
Subject: [stir] WGLC: draft-ietf-stir-passport-rcd-09

NOTE: Message is from an external sender

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 earl=
y.

See <https://nam10.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fda=
tatracker.ietf.org%2Fdoc%2Fdraft-ietf-stir-passport-rcd%2F&amp;data=3D04%7C=
01%7Cjack.rickard%40metaswitch.com%7C19f85464b15848e0637d08d89bc098dd%7C9d9=
e56ebf6134ddbb27bbfcdf14b2cdb%7C1%7C0%7C637430598808552589%7CUnknown%7CTWFp=
bGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%=
7C1000&amp;sdata=3D8Zz%2B%2BN10JP6zy4jaozXYqMqRwOdE%2BD1Om7A8Xr7SPMc%3D&amp=
;reserved=3D0>

RjS

_______________________________________________
stir mailing list
stir@ietf.org
https://nam10.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.iet=
f.org%2Fmailman%2Flistinfo%2Fstir&amp;data=3D04%7C01%7Cjack.rickard%40metas=
witch.com%7C19f85464b15848e0637d08d89bc098dd%7C9d9e56ebf6134ddbb27bbfcdf14b=
2cdb%7C1%7C0%7C637430598808552589%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwM=
DAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3DUmjwL7=
Iy4LKkqdwlMD%2Fwlmbyl5ZvhqIM7ysOkO9Gnlc%3D&amp;reserved=3D0


From nobody Thu Dec 17 20:11:15 2020
Return-Path: <ben@nostrum.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 0BF193A0E6D; Thu, 17 Dec 2020 20:11:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.279
X-Spam-Level: 
X-Spam-Status: No, score=-1.279 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.399, MAY_BE_FORGED=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dFDIgwNwt1Vl; Thu, 17 Dec 2020 20:11:12 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C1CC3A0E68; Thu, 17 Dec 2020 20:11:09 -0800 (PST)
Received: from macbook-pro.lan (mta-70-120-123-175.stx.rr.com [70.120.123.175] (may be forged)) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 0BI4B6Lx070035 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 17 Dec 2020 22:11:08 -0600 (CST) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1608264668; bh=aqsRdm4QsPmD3LXU2PW/IX+PJ+jGcuRgZkWC8D3/K7k=; h=From:Subject:Date:References:To:In-Reply-To; b=WXgaFzQFaWrxSmQZN8/kpPbmTrFc7kYg+GpfmscVmOk9jRVNTYDzepKndJPGyEZM/ hLLSNRw0wTXv3OmNWKtCDNfnygRnFCOomBZ3ifTUnQ+EL6fCQkMkfeJ79c/yJM/oku JYrp5fXGtHEBp/zFnmsCkPOI0Ouby5xjmbe551QE=
X-Authentication-Warning: raven.nostrum.com: Host mta-70-120-123-175.stx.rr.com [70.120.123.175] (may be forged) claimed to be macbook-pro.lan
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
Date: Thu, 17 Dec 2020 22:11:00 -0600
References: <5393b70d-bfc7-c8ac-eb8d-30c8087a1e89@nostrum.com>
To: IETF STIR Mail List <stir@ietf.org>, draft-ietf-stir-passport-rcd@ietf.org
In-Reply-To: <5393b70d-bfc7-c8ac-eb8d-30c8087a1e89@nostrum.com>
Message-Id: <42B8A552-400F-4DE4-9D47-DCB6080A7D6D@nostrum.com>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/_lNQqgt2-_kYCkAWMIW1_A3LYxA>
Subject: Re: [stir] WGLC: draft-ietf-stir-passport-rcd-09
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 18 Dec 2020 04:11:14 -0000

Hi,

I like this draft a lot, but I do have some WGLC comments. Apologies if =
these rehash old discussions; I=E2=80=99m feeling sort of stateless this =
season ;-)

Thanks!

Ben.

---------------

*** Substantive Comments ***

- General:=20

=E2=80=94 I think this draft needs some early explanation of what it =
means for someone (first-party or third-party) being authoritative for =
some or all of the RCD associated with a call. The draft references this =
concept many times, but I think there are some architectural assumptions =
that may not be obvious to everyone, especially those not exposed to the =
politics around who controls what gets displayed to a call recipient.. =
(Chris=E2=80=99s SIPNOC presentation might have some helpful ideas =
here.)

=E2=80=94 I=E2=80=99m a bit confused about when the rcdi JWT constraints =
are required or optional (more specifics below.)

- =C2=A71, last paragraph: "=20
This document furthermore specifies a third-party profile that would =
allow
   external authorities to convey rich information associated with a
   calling number via a new type of PASSporT=E2=80=9D

Are we talking about ppt=3Drcd, or something else? Does this suggest the =
use of RCD passports (as opposed to other passports with RCD claims) are =
not intended for first-party assertions?

- =C2=A75.1.1: "If there is no string associated with a display name, =
the claim value SHOULD then be an empty string.=E2=80=9D

Why SHOULD, not MUST (or maybe just =E2=80=9Cis=E2=80=9D)? Can we =
foresee some situation where something other than an empty string might =
be appropriate?

- =C2=A75.1.1, =C2=A75.1.2, and =C2=A75.1.2: Each of these sections =
talks about deriving data from certain SIP header fields. Nam from the =
From: display name, jcd/jcl from Call-Info. But the language around that =
derivation is different in each section in a way that might be read to =
have different strengths (e.g. =E2=80=9Cfor example=E2=80=9D, =E2=80=9Cis =
intended to represent=E2=80=9D and  =E2=80=9Cmay derive from=E2=80=9D. =
It would be helpful to be consistent and clear about how important it is =
for the RCD to match the related SIP header fields.

- =C2=A75.1.4: "The "rcdi" claim is an optional claim that SHOULD be =
included if the application requires integrity to be applied to the =
content of the "rcd=E2=80=9D claim=E2=80=9D

I=E2=80=99m confused by the global SHOULD here. For example, if I am =
including an RCD passport with no external content and no third-party =
policy control, why would I need rcdi? Maybe that is not a legitimate =
use case?=20


- =C2=A75.1.5 (and possibly Security Considerations):=20

In order to sign and verify RCD passports that have links to external =
data, one has to retrieve the target for each link. And if those links =
lead to other links, this must be recursive. Is there a potential for =
this to be used for a DoS (or other sorts of) attack? In particular, it =
seems like the draft needs some guidance about sanity checking things =
for crazy-large targets, long or looping link chains, etc. In =
particular, the VS needs to do this before verifying the signature, so =
it cannot be sure that the RCD should be trusted prior to retrieving the =
content.

- =C2=A75.1.6:=20
-- This section can be read to say the issuer must always include the =
JWT Contraints to require rcdi. Is that the intent? In either case, some =
clarification of the normative language would be helpful. (e.g. maybe =
you MAY include the constraints, but if you do you MUST do=E2=80=A6

-- Is there a use case where a CA might require the integrity mechanism =
to be used, but not require any specific value? (e.g. =E2=80=9CmustInclude=
=E2=80=9D rcdi, but no =E2=80=9CpermittedValue=E2=80=9D?)

- =C2=A76.1.1, last example: "If we were to add a "rcdi" integrity claim =
to the last example=E2=80=A6=E2=80=9D

That example has external content. That makes =E2=80=9Crcdi=E2=80=9D a =
MUST. Isn=E2=80=99t the preceding example invalid due to not having =
rcdi?

- =C2=A78: =E2=80=9C...hyperlinks to images, such as logos or pictures =
of faces, or to similar external profile information=E2=80=A6"

I may be confused on this point, but aren=E2=80=99t those already =
supported in jCard? And in general, how does the new registry here =
interact with the existing jCard/vCard extension mechanism(s)?

- =C2=A79:=20
-- General: The distinction between first-party and third-party =
passports seems a bit fuzzy. For example, does an STI-AS inserted SHAKEN =
passport that has RCD claims count as a first-party or third-party =
passport? What about a SHAKEN or RCD passport inserted by a tdm->SIP =
gateway in an OOB deployment?

-- "If the display name in the "rcd" PASSporT object matches the display =
name in the INVITE, then the name would presumably be rendered to the =
end user by the terminating user agent.=E2=80=9D

That match is not a requirement for first-party RCD passports, is it? =
Why would it be different for third-party ones?

- =C2=A79.1: " A third-party PASSporT, which contains such an "iss=E2=80=9D=
 element=E2=80=A6=E2=80=9D

This is the first mention of =E2=80=9Ciss=E2=80=9D elements in the =
draft. The wording =E2=80=9Csuch an =E2=80=9Ciss=E2=80=9D element=E2=80=9D=
 makes me wonder if there is some prior text messing that might have =
defined =E2=80=9Cthird-party PASSporTs=E2=80=9D in terms =E2=80=9Ciss=E2=80=
=9D?

- =C2=A710: " Therefore, PASSporTs that carry =E2=80=9Crcd" data SHOULD =
also carry an indication of the relationship of the generator of the =
PASSporT to the caller..=E2=80=9D

Is that true for first-party RCD passports, or just third-party?

- =C2=A711.2:=20

-- General: This section could use some guidance for VS behavior if the =
RCD in a passport conflicts with the respective SIP headers. I think the =
answer is to prefer the passport RCD if you trust it, for whatever =
definition of =E2=80=9Ctrusting it=E2=80=99 you have. Would it ever make =
sense to prefer the unauthenticated SIP header field contents to the =
contents of a verified passport?

-- " If the PASSporT is in compact form, then the verification service =
SHOULD
   extract the display-name from the =46rom header field value=E2=80=A6=E2=
=80=9D

Why not MUST? If this is indeed a SHOULD, it seems like that sort of =
SHOULD that needs some guidance about when it might be reasonable to do =
something different.

*** Editorial Comments ***

- Abstract:
-- =E2=80=9C This framework is intended to extend caller and call =
specific information beyond human-readable display name comparable to =
the "Caller ID" function common on the telephone network."

Not clear if the framework is comparable or the human readable name is =
comparable. I assume the second.

- Introduction:
-- Please expand PASSporT on first use.
-- Please expand JWT on first use.
-- Please expand STIR on first use.

- =C2=A76: =E2=80=9C=E2=80=A6 any entities verifying the PASSporT object =
will be required to understand the "ppt" extension in  order to process =
the PASSporT in question.=E2=80=9D

Should that be the =E2=80=9Crcd=E2=80=9D extension?

- =C2=A76.1,  first paragraph: s/obejct/object

- =C2=A78, last paragraph: Seems like this paragraph belongs in =C2=A79.


> On Dec 8, 2020, at 3:30 PM, Robert Sparks <rjsparks@nostrum.com> =
wrote:
>=20
> This is a WGLC for draft-ietf-stir-passport-rcd-09.
>=20
> Please send reviews to the list by the end of day 22 Dec 2020.
>=20
> If you plan to provide a review but need more time, please let us know =
early.
>=20
> See <https://datatracker.ietf.org/doc/draft-ietf-stir-passport-rcd/>
>=20
> RjS
>=20
> _______________________________________________
> stir mailing list
> stir@ietf.org
> https://www.ietf.org/mailman/listinfo/stir

