[sipcore] Re: sipcore Digest, Vol 185, Issue 3

[Pierce Gorman <[e-mail]>]

"I am wondering why do you think that call-reason will be used if “subject” had low usage. I have no objection to the new parameter just wondering." - Roni Even

I think call-reason will do better because the content will be carried through the NNI in the "crn" of Rich Call Data (RCD) claims which may survive transit to the Terminating Service Provider (TSP) especially if those claims are part of a SHAKEN PASSporT protected by US law and FCC mandates.

The TSP can verify the integrity of the "crn" claim, copy the value to a call-reason to be sent to a terminal (e.g., mobile phone) as part of the UNI signaling between the network and the User Equipment (UE).

So-called "branded caller identity" services which display company name, company logo, and reason for calling already exist which do something similar (or perhaps identical if they're following the callinfo-rcd I-D).

As Rich Shockey famously said, "The answer is money.  What is the question?"


CONFIDENTIAL
-----Original Message-----
From: [e-mail] <[e-mail]>
Sent: Sunday, February 9, 2025 8:00 AM
To: [e-mail]
Subject: sipcore Digest, Vol 185, Issue 3

EXTERNAL EMAIL

Send sipcore mailing list submissions to
        [e-mail]

To subscribe or unsubscribe via email, send a message with subject or body 'help' to
        [e-mail]

You can reach the person managing the list at
        [e-mail]

When replying, please edit your Subject line so it is more specific than "Re: Contents of sipcore digest..."

Today's Topics:

   1. Genart last call review of draft-ietf-sipcore-callinfo-rcd-13
      (Roni Even via Datatracker)


----------------------------------------------------------------------

Message: 1
Date: Sun, 09 Feb 2025 05:00:51 -0800
From: Roni Even via Datatracker <[e-mail]>
Subject: [sipcore] Genart last call review of
        draft-ietf-sipcore-callinfo-rcd-13
To: <[e-mail]>
Cc: [e-mail], [e-mail],
        [e-mail]
Message-ID: <173910605105.367291.2026407971995211510@dt-datatracker-75
        c44cbbdf-pxnd6>
Content-Type: text/plain; charset="utf-8"

Reviewer: Roni Even
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair.  Please treat these comments just like any other last call comments.

For more information, please see the FAQ at

<https://wiki.ietf.org/en/group/gen/GenArtFAQ>.

Document: draft-ietf-sipcore-callinfo-rcd-??
Reviewer: Roni Even
Review Date: 2025-02-09
IETF LC End Date: 2025-02-17
IESG Telechat date: Not scheduled for a telechat

Summary:
The document is ready for publication as a standard track RFC.
 I am wondering why do you think that call-reason will be used if “subject” had  low usage. I have no objection to the new parameter just wondering.

Major issues:

Minor issues:

Nits/editorial comments:



------------------------------

Subject: Digest Footer

_______________________________________________
sipcore mailing list -- [e-mail] To unsubscribe send an email to [e-mail]


------------------------------

End of sipcore Digest, Vol 185, Issue 3
***************************************