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

Chris Wendt <> Wed, 29 March 2023 22:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 781C6C151546 for <>; Wed, 29 Mar 2023 15:31:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.894
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, 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=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id T6JU-3hlkW1p for <>; Wed, 29 Mar 2023 15:31:32 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::630]) (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 C7539C151539 for <>; Wed, 29 Mar 2023 15:31:32 -0700 (PDT)
Received: by with SMTP id kq3so16300603plb.13 for <>; Wed, 29 Mar 2023 15:31:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; t=1680129091; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=/E77TJowaiaLF5xup4xM98L0rqPFaU3HAWaTwvSZIWk=; b=f6qJ67eaZSYs3Yyt1Kl59sfyGOTQ/tY1A2fsCWSG0eJjcSjnQxiMEAir3+6ZhMwJAS NPTjydlXg33Y8xtEcxA3URWY1urFGwC3j2DhQzw5lYQMiSIMy/WZE9bdcNUS5a+qsHc9 /82e37gV75iWmvbjfKgsUgW6AUKphlqe6fOjCtLWYymUIVZp8oijSnoU+G1W4Wa24+Tl 9MxxrryvUcV+vq130LmZoNU1HOPNeFHwkr4jDSvv8mu8fpLgKzd6DWwXXxG5+hduTjNa De2f8uRWOwu9GX6R1l3+XuemCUWQZiHozA+1fe6CaUHRYNPLajCJH1/6pmNL6DcvOgfX 66Hw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; t=1680129091; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=/E77TJowaiaLF5xup4xM98L0rqPFaU3HAWaTwvSZIWk=; b=Zppnq57WGhtqpZBZkO0iaKS/q7bfXz5ihR0oBPHYXATmc8nUAsrlXr8aQh4VdmNK18 jAN4tmw50edg8NmzulmUjgKWwqR2h3dfv+GVtKe4duKuin/UHtChWP/Cwz12M0GPQ+la WsESRtgjjNffBx0OuZj6ZWU767T+9A7bA0emPxMesDB55UgH9xnKIcn/k8B+2irapD0h FzqWX6pZYyez83VbufFgySosfp4wtU1FgzI0UhXPpOywWLsyG8LNQwexltUMuxirghSH +Al2z57CEti0eE92fKw5mxCa59JG5r24TnNnWahwpYwwvWzmop/N+oedthVInmA9PDc6 ZfMg==
X-Gm-Message-State: AAQBX9ePlRYZBzc/3uxaRv23Z4Wh5xopmwab1HE/2J7SDmF6Xq1WHEId kvXfbaFt1YbMWQnOSpTI56X78T2N4RpNPa+LU6M=
X-Google-Smtp-Source: AKy350b7PvWCIXjoFkBu0Jl3UPVj5YQjLkrR9SAG+gfS3TgJ/yG/H6fJKLA7ml5DZ4MC/qmKdIhkdQ==
X-Received: by 2002:a05:6a20:8ca9:b0:df:5e73:d78a with SMTP id k41-20020a056a208ca900b000df5e73d78amr14118762pzh.49.1680129091486; Wed, 29 Mar 2023 15:31:31 -0700 (PDT)
Received: from ( []) by with ESMTPSA id q17-20020a62ae11000000b0062607d604b2sm23534083pff.53.2023. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Mar 2023 15:31:30 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\))
From: Chris Wendt <>
In-Reply-To: <>
Date: Thu, 30 Mar 2023 07:31:23 +0900
Cc: IETF STIR Mail List <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <>
X-Mailer: Apple Mail (2.3731.400.51.1.1)
Archived-At: <>
Subject: Re: [sipcore] 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: Wed, 29 Mar 2023 22:31:36 -0000

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.



> 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