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

Chris Wendt <> Wed, 01 March 2023 18:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9B375C151AF0 for <>; Wed, 1 Mar 2023 10:07:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.894
X-Spam-Status: No, score=-6.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, 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 26gA1087GgBg for <>; Wed, 1 Mar 2023 10:07:11 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::82a]) (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 E1884C151AED for <>; Wed, 1 Mar 2023 10:07:11 -0800 (PST)
Received: by with SMTP id cf14so15228899qtb.10 for <>; Wed, 01 Mar 2023 10:07:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; 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=rNe8rhhbb/mpFE66e/n+0BVYbty+/bkLsnwoH+bbaUE=; b=n0OsheeeWJ9b6QqsJdIoBnkE45JSB5lBfXFxyBYSWeQTx18NtQPO7JRPjofGdQU1uF bFFUXncRW+y2i+0sH2sdMCdOaCSVo0o2wrSiOo07kNTYEOysB8Rqid0GwHlLlWLclmGN 3m4DE4t1mxmdTZIMy4OgeI0uxi4CiJIkHVwb7cqbP28FSDv7e/Yd2fu+1JUvIZP2fkda /jI3UR5sQhzHz0Skr1mbAIc9iyr3ylfuVcTb6/wMc3JgKE0ehn6Zxja1qjrNKyEM8h39 oBk0EFObVfUoKmSuDb9K8gYEljn47NwKVMhqJI6nXDkqjdik+VStZ4R/ozQfIHJJvpMj UDRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; 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=rNe8rhhbb/mpFE66e/n+0BVYbty+/bkLsnwoH+bbaUE=; b=6ZNIcdEqIFLT+O7LCVsbF28fNnlh20gR8WvTyfAGy78lidzYQwt1PJPPpL5PYT/41z faO4cDjZOrdRshG2wqq3sRqQLQaB4oZZgKiMe+MStws5WiZXJ8g6FVQVuB2Jj1OOe4uf SfyIRSEBuANiA+Jd2GTjwxYZMxhIBRYYIuPRQY+Uo2w7mm3388Cnw+k/8FsV8jmkod2G UZYVQu9m+tZmtCXvDfGMHImkm3Vo7d2gYoX7m1KfSudzxd3urRimmmLp3Sw9sbA3qtES h61GlDvjpVBcuXLsjJOAXhxlT+tsUr6xAxYFrJmptCDsKXs/AizSUaBYQVaMv2dV0WGA dBUQ==
X-Gm-Message-State: AO0yUKVy2PGFGXAS7iEBILLRx2FQQilZ/UnydDX/IrrD2NyzNVel0t38 jcHrRICqKszpP37xv4UthVCGE2O3pvde4NeEAQc=
X-Google-Smtp-Source: AK7set+dGeCTHVpBRylhzMKxTUJw+CS8a6wmCykEdZkzWjaG+U6gsD0tOCWvTtGnxVXPEtIH5k1UPA==
X-Received: by 2002:a05:622a:50d:b0:3bf:e2f8:c6a4 with SMTP id l13-20020a05622a050d00b003bfe2f8c6a4mr10998130qtx.61.1677694030347; Wed, 01 Mar 2023 10:07:10 -0800 (PST)
Received: from ( []) by with ESMTPSA id l9-20020ac848c9000000b003b82a07c4d6sm8728779qtr.84.2023. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Mar 2023 10:07:09 -0800 (PST)
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: Wed, 01 Mar 2023 13:07:00 -0500
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, 01 Mar 2023 18:07:12 -0000

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.


> 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