[stir] "jcl" key in RCD claims

Ben Campbell <ben@nostrum.com> Wed, 29 September 2021 17:16 UTC

Return-Path: <ben@nostrum.com>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id E2B323A07AA for <stir@ietfa.amsl.com>; Wed, 29 Sep 2021 10:16:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.28
X-Spam-Status: No, score=-0.28 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=1, 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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id r116Q8pBntZw for <stir@ietfa.amsl.com>; Wed, 29 Sep 2021 10:16:08 -0700 (PDT)
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 BA0843A0763 for <stir@ietf.org>; Wed, 29 Sep 2021 10:16:08 -0700 (PDT)
Received: from smtpclient.apple (mta-70-120-133-87.satx.rr.com [] (may be forged)) (authenticated bits=0) by nostrum.com (8.17.1/8.16.1) with ESMTPSA id 18THG0aW071541 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 29 Sep 2021 12:16:02 -0500 (CDT) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1632935762; bh=kZTVavKto/4ssHT0/JYaE1Z58rfDxVeRl8eZN4Jt/oo=; h=From:Subject:Date:To; b=FoHM0GunCdYilu7HETOxvK9K5jEiE9wx6zNvHdZEIvlU3v7hMX2nZxGkfl7MGyllJ rNuYKxb4i2iy+B/A+lm29RSTxruk0+OqEpx8TM6yBosfz20hyAXoZpKJAu8tfErS8R Lhjria0iFCc54ovym6h0xQ0bwLfanWAtBp0yG9EI=
X-Authentication-Warning: raven.nostrum.com: Host mta-70-120-133-87.satx.rr.com [] (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 14.0 \(3654.\))
Message-Id: <0CB65208-AC7D-4E52-8843-F3FE05E2E12F@nostrum.com>
Date: Wed, 29 Sep 2021 12:15:54 -0500
To: "Peterson, Jon" <jon.peterson@team.neustar>, Chris Wendt <chris-ietf@chriswendt.net>, IETF STIR Mail List <stir@ietf.org>
X-Mailer: Apple Mail (2.3654.
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/90DBXFeudWmYgCpz1yJFHUI0Yf8>
Subject: [stir] "jcl" key in RCD claims
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: Wed, 29 Sep 2021 17:16:13 -0000

(as individual)


Section 5.1.4 of draft-ietf-stir-passport-rcd-13 says that the “jcl” key “is defined” to contain an HTTPS URL. Does that mean to preclude the use of a “cid:” URL, which I understand to be allowed by the callinfo-rcd draft?

I thought about asking the same for a “data:” URL, but I suppose the “jcd” key already handles that case.