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

Brian Rosen <> Thu, 30 March 2023 09:13 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 036E2C15C528 for <>; Thu, 30 Mar 2023 02:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.084
X-Spam-Status: No, score=-2.084 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, 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 (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id WE8IzgMQGJt9 for <>; Thu, 30 Mar 2023 02:13:38 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::f36]) (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 C0282C13AE29 for <>; Thu, 30 Mar 2023 02:13:38 -0700 (PDT)
Received: by with SMTP id t13so13616987qvn.2 for <>; Thu, 30 Mar 2023 02:13:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; t=1680167618; x=1682759618; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=utMd4e3A+ZXJnQHPXFBd05iCm60awieJbe4Mxypbp7s=; b=HfpTlYEV1gwYH6hOQK0UBcM+cNpfKyszsKzBT3XZmeK2gm+HrT5r3YfdwjbVqbp19k tp7WWM6W0thcIQN7FtYjIgibaXq5+s/QbT1yKrVKYXQ+J9KESi8UPReC5scI+k3HGzY8 IAVs+SY9Jr1qEwwzrGZLSpueuxQ8VpBoIpPH0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; t=1680167618; x=1682759618; 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=utMd4e3A+ZXJnQHPXFBd05iCm60awieJbe4Mxypbp7s=; b=VUGXcJeqhxiEiqtKmh6AmtejZ6RgTXhE+ClaIUqeA1CQIDWX5pXb/pR10C5yKP/gsy L7jYKplDAGQ4nfO5dhXY+spDV+j6SrZ/ejARJeyQ/M6unWEAF1pEde7gbTNi+tM6Z+Xl zHkj20kmipCO5PPYuz4AZwb3FR0LDOQqjafFlApD7UAqjLLAuuInSKNPHBRpW9UIMvle 8fgb8BWuVDknZJtACvl2PUm1PhWer5EP+qtHnLIvW+DzGUoOrsB1ksklDkif0aVtiuij 08azKLk/VR4qZKDJUf4g01j50JiWzXfnGrWlCE7eOUoik2p4i/VpKhZj9u0+mkr5VXrG XYYw==
X-Gm-Message-State: AAQBX9dnh7r/SWSQS5RDP5fOs1BYrDMVjSFOSAMCkzxiw0d37VEwx4on lU/AJgUyU9o30687AmxYwQHtAg==
X-Google-Smtp-Source: AKy350bGtxLFPllD2XivjZZFfOLAaaBNXqUOgH7Fih06mT75vZYkjfC7qPW8kokUkZEo7W2hbdObow==
X-Received: by 2002:a05:6214:4005:b0:5ab:af50:eb45 with SMTP id kd5-20020a056214400500b005abaf50eb45mr34693756qvb.3.1680167617514; Thu, 30 Mar 2023 02:13:37 -0700 (PDT)
Received: from ([]) by with ESMTPSA id h16-20020ac846d0000000b003e62c357781sm762593qto.86.2023. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Mar 2023 02:13:36 -0700 (PDT)
From: Brian Rosen <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8B41EBA2-CC33-48BD-88FD-BBB5A375C438"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.300.101.1.3\))
Date: Thu, 30 Mar 2023 12:13:24 +0300
In-Reply-To: <>
Cc: SIPCORE <>, IETF STIR Mail List <>
To: Chris Wendt <>
References: <> <> <>
X-Mailer: Apple Mail (2.3731.300.101.1.3)
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: Thu, 30 Mar 2023 09:13:43 -0000

Anyone object to starting WGLC?


> 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
> <>