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

Hi All, (cross posting to stir mailing list as well)

Just as an update to sipcore WG, we have been doing a lot of good work on updating the stir-passport-rcd draft that goes along with this sipcore draft so just to explain why there hasn’t been as regular updates on this document.  That said, we think we have worked out most of the dependencies and are ready to move on this document.

Changes from 03->04 are as follows:

Added a “jmin” Call-Info purpose.  We realized that not all RCD calls will necessarily contain a jCard, but may want to use a call-reason.  But the constructs we had in the previous document made that a dependency, so for those scenarios, we defined a “jmin” which is essentially a minimal URI pointer to a defined “null” JSON object of “{}”  We wanted any implementation that wasn’t aware of this specification to not fail when following the URI reference in call-info.  You can read spec for more detail, but definitely would like feedback on this approach.

I simplified the “usage of multimedia data in jCard” section.  I suggest not supporting non 24-bit RGB supporting image formats because that is becoming a legacy item, devices seem to be either supporting modern formats, or just supporting text displays as far as i am aware, so I wouldn’t be opposed to removing saying anything about that. also.

Also added a security consideration for using integrity or constraints or being aware of the risk of not using those mechanisms with Call-Info based information.

Other editorial fixes etc have been included.

Please let me know if you have any comments and we can discuss on the list.  There isn’t a STIR session during formal IETF meeting this time around, but will be a virtual meeting that will be planned after that week.  We will use that to discuss this document if you are interested in being part of the live discussion, but hoping to progress this document now in parallel with the stir-passport-rcd to the extent we can.

Thanks!!

-Chris

> On Mar 7, 2022, at 2:52 PM, internet-drafts@ietf.org wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This 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-04.txt
> 	Pages           : 22
> 	Date            : 2022-03-07
> 
> Abstract:
>   This document describes a SIP Call-Info header field usage defined to
>   include rich data associated with the identity of the calling party
>   that can be rendered to a called party for providing more useful
>   information about the caller or the specific reason for the call.
>   This includes extended comprehensive information about the caller
>   such as what a jCard object can represent for describing the calling
>   party or other call specific information such as describing the
>   reason or intent of the call.  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
>   additionally, with the use of jCard and other elements, to be
>   compatible with the STIR/PASSporT Rich Call Data framework.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-sipcore-callinfo-rcd/
> 
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-sipcore-callinfo-rcd-04
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-sipcore-callinfo-rcd-04
> 
> 
> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
> 
> 
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore