IETF Logo Mail Archive

[stir] RCD vs "div"

Ben Campbell <ben@nostrum.com> Mon, 07 March 2022 20:25 UTC

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 BAE6D3A0D2D for <stir@ietfa.amsl.com>; Mon, 7 Mar 2022 12:25:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.503
X-Spam-Level:
X-Spam-Status: No, score=-0.503 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.186, MAY_BE_FORGED=1, T_SCC_BODY_TEXT_LINE=-0.01, 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 hGZ_QZoHluPa for <stir@ietfa.amsl.com>; Mon, 7 Mar 2022 12:25:14 -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 974123A0C70 for <stir@ietf.org>; Mon, 7 Mar 2022 12:25:14 -0800 (PST)
Received: from smtpclient.apple (mta-70-120-133-87.satx.rr.com [70.120.133.87] (may be forged)) (authenticated bits=0) by nostrum.com (8.17.1/8.16.1) with ESMTPSA id 227KP98I093329 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 7 Mar 2022 14:25:10 -0600 (CST) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1646684711; bh=4l547vwhuPI0SWhmT3BorNbrIlX6QjR4CIXBo9hJ45o=; h=From:Subject:Date:To; b=Y7gLejewqmIBHrxhmTy/JIZjFnnYc5KWkL6Q9s0rmgp6ZxiyGYl99X/FfBsn2jXc8 a8VzOp6ugzLftTW0OcGLfyO1/2CivsjF20OjQ9UXkhSLJglBJfAPKfKfCIOR4NcCDZ uAYo1QO+CxzNMhLB+5Ubub5PUgMj9Onoihg3MU0w=
X-Authentication-Warning: raven.nostrum.com: Host mta-70-120-133-87.satx.rr.com [70.120.133.87] (may be forged) claimed to be smtpclient.apple
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 15.0 \(3693.20.0.1.32\))
Message-Id: <4844A8E7-2B8C-463A-8EA4-0A565007FB13@nostrum.com>
Date: Mon, 7 Mar 2022 14:25:03 -0600
To: IETF STIR Mail List <stir@ietf.org>, Chris Wendt <chris-ietf@chriswendt.net>, "Peterson, Jon" <jon.peterson@team.neustar>
X-Mailer: Apple Mail (2.3693.20.0.1.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/wmf7ySOyXiremi4SKJB5AAmPYTw>
Subject: [stir] RCD vs "div"
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: Mon, 07 Mar 2022 20:25:19 -0000

Hi,

(Apologies for bringing this up late in the process for RCD, but I just thought about it over the weekend.)

Does the RCD passport draft need to talk about interactions with “div” passports?

For example, would a retargeted call inherit any RCD claims in the innermost passport? What happens if someone adds RCD claims to a “div” passport, especially if they conflict with any claims from earlier in the chain? Is the answer the same for RCD passports vs other passport types with RCD claims?

Thanks!

Ben.

v2.8.7 | Report a Bug | By Email