Re: [stir] I-D Action: draft-ietf-stir-passport-rcd-19.txt

pierce@numeracle.com Mon, 25 July 2022 21:59 UTC

Return-Path: <pierce@numeracle.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 61278C13CCC9 for <stir@ietfa.amsl.com>; Mon, 25 Jul 2022 14:59:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=numeracle-com.20210112.gappssmtp.com
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 yL3WlfVOnbFI for <stir@ietfa.amsl.com>; Mon, 25 Jul 2022 14:59:37 -0700 (PDT)
Received: from mail-oi1-x235.google.com (mail-oi1-x235.google.com [IPv6:2607:f8b0:4864:20::235]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 7E018C13CCC0 for <stir@ietf.org>; Mon, 25 Jul 2022 14:59:37 -0700 (PDT)
Received: by mail-oi1-x235.google.com with SMTP id bb16so15071798oib.11 for <stir@ietf.org>; Mon, 25 Jul 2022 14:59:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=numeracle-com.20210112.gappssmtp.com; s=20210112; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :thread-index:content-language; bh=dWk6KmPBWLnlNR4HrqieJv4tFwNE06t8sPt8OQ3mwHY=; b=Zlu+TIMYAaRntEnhAsdAN27OnpnXN1SOXTk92TxCra9nS4Fht1yKWpD31ROOjSrJ31 d2nh0lUJ7ktaadplhTtLglKhoNyUxzrmRN3Ulohgjuf9yZTOPWEvVaCJcqwYfPPTlpWQ roesCNXInuZ1MnujVDiQQhsJ++JUTTICBsl8EcQN6ryTehHogpRw/NKLAe4UQIuCNgN+ 3ZC3nUA87TO332nqI+uStkWYcqBrLYUA1+GWSdW32Kc9wHGl2C9Ze1EuLle0sWabF/fH pbisF0hW7jb+sKkx5pPt0hXzaGjQjbJ+BUQokDIIBE5u3KG06q+SBKASEl4rEKVVKH9s 5hyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=dWk6KmPBWLnlNR4HrqieJv4tFwNE06t8sPt8OQ3mwHY=; b=nl/CUEMaIkHlMwbZWjcKk0XAW9QcAVNK5VirGHF1QIUmnjE3WpEA73n3SZh+kkuDl/ FTxXt0MkrhVp2fpLHMX1dF0XafHcDyr1mpr76mmmlzeaElf06yfjht07FerAVNItQeyR 55XRPZtxr28oXDuCTMvuR4TM3aKgeMkBA3w5SEsuheNEvOU9LJCTbmkjwI47WMKj4Ifr JPpuaMy1DT7Y/89QjOqX64nbJas+mSR3XLkRoxD/pY/czibjVCBmDHFFN141Y/rNkIhh 9chzlRFYMjT6jZxQJ6URvRbinQm1Hu2kYQe6/PLeWk3au9YTmF1PS8g8BOpkp+JSUHjF FRKQ==
X-Gm-Message-State: AJIora/gNEskUyObdl7RHFnIuVG1d6Jj6XDMaeSvFGNjOW2HPDjFEuWy T5E+iIQoLF/yZ44eDJD3V9u5Qzu+h2oiyg==
X-Google-Smtp-Source: AGRyM1uP1L81wAjq+WiJ3yE3t1B3uDu++doNEQItMBbPTn+TtO1qwht/OoNj/6kEMzHUNKW8VCKUuw==
X-Received: by 2002:a05:6808:14d0:b0:33a:a708:e01a with SMTP id f16-20020a05680814d000b0033aa708e01amr6235191oiw.148.1658786375888; Mon, 25 Jul 2022 14:59:35 -0700 (PDT)
Received: from NumeracleLegion ([2605:a601:ae1c:4300:5d67:5681:23b4:eeea]) by smtp.gmail.com with ESMTPSA id i6-20020aca2b06000000b0033a11fcb23bsm5287146oik.27.2022.07.25.14.59.34 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 25 Jul 2022 14:59:35 -0700 (PDT)
From: pierce@numeracle.com
To: stir@ietf.org, i-d-announce@ietf.org
References: <165876237843.27029.4238360154413311917@ietfa.amsl.com>
In-Reply-To: <165876237843.27029.4238360154413311917@ietfa.amsl.com>
Date: Mon, 25 Jul 2022 16:59:33 -0500
Message-ID: <03ec01d8a071$d3db41a0$7b91c4e0$@numeracle.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_03ED_01D8A047.EB0539A0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQK2LfYY4dZXQRA/e4iYsGqLAN5kzavUYjvg
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/Idzxhf0PZLapwaMMMZfD1vY8X7U>
Subject: Re: [stir] I-D Action: draft-ietf-stir-passport-rcd-19.txt
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.39
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, 25 Jul 2022 21:59:38 -0000

Two questions.

 

Section 17 indicates the IANA registry for RCD Types will be initially
populated with four values, "nam", "apn", "jcd", and "jcl".

 

Question #1: Should "icn" be included in this list?  i.e., should there be
five values initially populated in the IANA RCD Type Registry?

 

I want to make sure I understand Section 6 correctly.

 

In theory, I can create an RCD PASSporT with jcd or jcl which includes a
property such as SOURCE.

 

The example of a SOURCE vCard object URI in RFC 6350 is:

 

SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US

 

If we copy-and-paste that in place of the 2nd logo in Section 6.1.3 of
rcd-19, the example would like:

 

"rcd": {

  "jcd": ["vcard",

    [ ["version",{},"text","4.0"],

      ["fn",{},"text","Q Branch"],

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

      ["photo",{},"uri",

        "https://example.com/photos/quartermaster-256x256.png"],

      ["logo",{},"uri",

        "https://example.com/logos/mi6-256x256.jpg"],

      ["source",{},"uri",

        "
SOURCE:ldap://ldap.example.com/cn=Babs%20Jensen,%20o=Babsco,%20c=US"]

    ]

  ],

  "nam": "Q Branch Spy Gadgets"

}

 

And the corresponding rcdi example from the same section should apply.

 

"rcdi": {

  "/jcd": "sha256-tbxXX9mRY2dtss3vNdNkNkt9hrV9N1LqGST2hDlw97I",

  "/jcd/1/3/3": "sha256-RojgWwU6xUtI4q82+kHPyHm1JKbm7+663bMvzymhkl4",

  "/jcd/1/4/3": "sha256-jL4f47fF82LuwcrOrSyckA4SWrlElfARHkW6kYo1JdI",

  "/jcd/1/5/3": "sha256-GKNxxqlLRarbyBNh7hc/4lbZAdK6B0kMRf1AMRWPkSo"

  }

}

 

Question #2: Do I understand this correctly?  Or is there something inherent
in a non-HTTPS protocol accessing an unspecified data structure that
prevents this reference?  I assume not, but I might be missing something.

 

Pierce Gorman

Numeracle

 

 

-----Original Message-----
From: stir <stir-bounces@ietf.org> On Behalf Of internet-drafts@ietf.org
Sent: Monday, July 25, 2022 10:20 AM
To: i-d-announce@ietf.org
Cc: stir@ietf.org
Subject: [stir] I-D Action: draft-ietf-stir-passport-rcd-19.txt

 

 

A New Internet-Draft is available from the on-line Internet-Drafts
directories.

This draft is a work item of the Secure Telephone Identity Revisited WG of
the IETF.

 

        Title           : PASSporT Extension for Rich Call Data

        Authors         : Chris Wendt

                          Jon Peterson

  Filename        : draft-ietf-stir-passport-rcd-19.txt

  Pages           : 33

  Date            : 2022-07-25

 

Abstract:

   This document extends PASSporT, a token for conveying

   cryptographically-signed call information about personal

   communications, to include rich meta-data about a call and caller

   that can be signed and integrity protected, transmitted, and

   subsequently rendered to the called party.  This framework is

   intended to include and extend caller and call specific information

   beyond human-readable display name comparable to the "Caller ID"

   function common on the telephone network and is also enhanced with a

   integrity mechanism that is designed to protect the authoring and

   transport of this information for different authoritative use-cases.

 

 

The IETF datatracker status page for this draft is:

 <https://datatracker.ietf.org/doc/draft-ietf-stir-passport-rcd/>
https://datatracker.ietf.org/doc/draft-ietf-stir-passport-rcd/

 

There is also an htmlized version available at:

 <https://datatracker.ietf.org/doc/html/draft-ietf-stir-passport-rcd-19>
https://datatracker.ietf.org/doc/html/draft-ietf-stir-passport-rcd-19

 

A diff from the previous version is available at:

 <https://www.ietf.org/rfcdiff?url2=draft-ietf-stir-passport-rcd-19>
https://www.ietf.org/rfcdiff?url2=draft-ietf-stir-passport-rcd-19

 

 

Internet-Drafts are also available by rsync at
rsync.ietf.org::internet-drafts

 

 

_______________________________________________

stir mailing list

 <mailto:stir@ietf.org> stir@ietf.org

 <https://www.ietf.org/mailman/listinfo/stir>
https://www.ietf.org/mailman/listinfo/stir