Re: [sipcore] [stir] I-D Action: draft-ietf-sipcore-callinfo-rcd-05.txt

Chris Wendt <> Mon, 15 May 2023 12:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 34070C15256E for <>; Mon, 15 May 2023 05:54:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.893
X-Spam-Status: No, score=-1.893 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_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id pT2LB3npX3er for <>; Mon, 15 May 2023 05:54:38 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::72c]) (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 (Postfix) with ESMTPS id 6BA07C152567 for <>; Mon, 15 May 2023 05:54:38 -0700 (PDT)
Received: by with SMTP id af79cd13be357-7577ef2fa31so2643820485a.0 for <>; Mon, 15 May 2023 05:54:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20221208; t=1684155277; x=1686747277; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=4uaKy6F6ksVCqgYIexiCkSCH9WvA4qzTnrgKDuRPL9o=; b=mpgp8HAbtYUCYNqh/RIY/TEiWjkJpaJSjpfeXM13C2LbINL8v4JCmGJrEi2+zoq3iN bRB117vwY9+AZEArkW4uWNrGBivT6wWDdnXt4C4nSBSrkwXYxg4vPZmUyAD9cHNioQw+ XnIlJ3RojTpMUl+EpSYIiik+Vv3SLVWnoqI5MC3IoLVmJ7aghy8/+RYt++LRqb4GsaoQ 08uedU8Bw1UV/cDRvlFXBcbhGjzdAOA1OIiic4T4vP1Mw5C/4ZMrI7Zn8q2YwdVrHDIP Qe/fZDbHWV2FGSY6wFjFqyuP9n6udMUrfUF9u9TQXv9vcJuc2IJe6LTzA8/Iv4MvQzNk /3CQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20221208; t=1684155277; x=1686747277; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=4uaKy6F6ksVCqgYIexiCkSCH9WvA4qzTnrgKDuRPL9o=; b=TTXOrbHN6gUxbl/iIqsmKcYRfXyNJs9AgJwcoylm5QIc94zwASkZADuQvss5ol0hFt DFabe2ACxzwv/ieGyT5aDNpSh+q0fNvTiG6vmdcmZItZdcNb/iRmO+fosgCPqFxcAbOH VS0VzWRGF0gp5OcmdlSX7yeJIO5xDyjVL45rZyodu7qwyhHh+9TQPXjFmy8/ysJsMdRB 28unixXa+D7Lb/z0//rZRnZAywKtggDF7jv8PZd7BaUn5JMWppJCVPTMbBsXRG0HRAx6 eOVom4ZyW+yr1hjomBUH6orROqS6QFOIdCIvF7wUl+UnO5OGyyiixzTJubC74FwHjrrZ QLQg==
X-Gm-Message-State: AC+VfDxmgRlcEBFbxcHM8Z7BTea5rg2KXJFuyj/IC/B0up2smSRKVOhQ aBNjSmhcZiUjeMwjKF0ogD8peQ==
X-Google-Smtp-Source: ACHHUZ7TRo7t54kBWhPJQtfx6q3w3GiSoWaVeN99lXdq2puTIv7RyJ6Za20crAcTyYYrpHeHMaFuiw==
X-Received: by 2002:a05:6214:300b:b0:61b:6421:f3c3 with SMTP id ke11-20020a056214300b00b0061b6421f3c3mr57355095qvb.13.1684155276892; Mon, 15 May 2023 05:54:36 -0700 (PDT)
Received: from ( []) by with ESMTPSA id w18-20020a0cb552000000b006216ff88b27sm2688196qvd.79.2023. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 15 May 2023 05:54:36 -0700 (PDT)
From: Chris Wendt <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_05E1503B-B9E0-491F-B0C2-F3D0160CF814"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
Date: Mon, 15 May 2023 08:54:28 -0400
In-Reply-To: <>
Cc: SIPCORE <>, IETF STIR Mail List <>
To: Brian Rosen <>
References: <> <> <> <>
X-Mailer: Apple Mail (2.3731.500.231)
Archived-At: <>
Subject: Re: [sipcore] [stir] I-D Action: draft-ietf-sipcore-callinfo-rcd-05.txt
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: SIP Core Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 15 May 2023 12:54:39 -0000

Hi Brian, All, 

I didn’t see any objections, but would certainly appreciate any review from folks that are interested.  Would like to get this on a similar timing to releasing with RCD as a dependent document, so WGLC would be appreciated.



> On Mar 30, 2023, at 5:13 AM, Brian Rosen <> wrote:
> Anyone object to starting WGLC?
> Brian
>> On Mar 30, 2023, at 1:31 AM, Chris Wendt <> wrote:
>> Hi sipcore WG,
>> I wanted to come back to this document, i haven’t seen any comments about this update yet.  We discussed this in the STIR meeting yesterday about the dependency of this document for stir-passport-rcd.  So i would like to see if we can start the process to potentially last call this document in as timely a manner as possible.  Certainly if you haven’t had a chance to review, i am happy to get any comments about it. I think hopefully its pretty straight forward now that we have settled on all of the rcd claims and mechanisms in stir.
>> Thanks!
>> -Chris
>>> On Mar 2, 2023, at 3:07 AM, Chris Wendt <> wrote:
>>> Hi All,
>>> With the stir RCD draft nearing completion, it was time to align this document with where we ended up on the RCD claims etc.  I’m cross posting this to the STIR list as well for interested parties because it’s a dependent document to stir RCD.  Please review and let me know if there is comments.
>>> The major change is really to remove some of the ways we were dealing with Call-Info URI when you only used call-reason parameter and no URI.  It also better aligns with the icon, jcd/jcl, crn claims and now gives better general guidance and examples on usage.
>>> -Chris
>>>> On Mar 1, 2023, at 1:02 PM, wrote:
>>>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>>> This Internet-Draft is a work item of the Session Initiation Protocol Core WG of the IETF.
>>>>      Title           : SIP Call-Info Parameters for Rich Call Data
>>>>      Authors         : Chris Wendt
>>>>                        Jon Peterson
>>>> Filename        : draft-ietf-sipcore-callinfo-rcd-05.txt
>>>> Pages           : 22
>>>> Date            : 2023-03-01
>>>> Abstract:
>>>> This document describes a SIP Call-Info header field usage defined to
>>>> include Rich Call Data (RCD) associated with the identity of the
>>>> calling party that can be rendered to a called party for providing
>>>> more descriptive information about the caller or more details about
>>>> the reason for the call.  This includes extended information about
>>>> the caller beyond the telephone number such as a calling name, a logo
>>>> or photo representing the caller or a jCard object representing the
>>>> calling party.  The elements defined for this purpose are intended to
>>>> be extensible to accommodate related information about calls that
>>>> helps people decide whether to pick up the phone and with the use of
>>>> icon and newly defined jCard and other elements to be compatible and
>>>> complimentary with the STIR/PASSporT Rich Call Data framework.
>>>> The IETF datatracker status page for this Internet-Draft is:
>>>> There is also an htmlized version available at:
>>>> A diff from the previous version is available at:
>>>> Internet-Drafts are also available by rsync at
>>>> _______________________________________________
>>>> sipcore mailing list
>> _______________________________________________
>> stir mailing list
>> <>