Re: [sipcore] [stir] Adding categories from sipcore-callinfo-spam to draft-ietf-sipcore-callinfo-rcd-04
Samir Srivastava <srivastava_samir@hush.com> Wed, 16 March 2022 13:39 UTC
Return-Path: <srivastava_samir@hush.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDE803A188A for <sipcore@ietfa.amsl.com>; Wed, 16 Mar 2022 06:39:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.707
X-Spam-Level:
X-Spam-Status: No, score=-1.707 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (body has been altered)" header.d=hush.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IXwZSfbd-i5l for <sipcore@ietfa.amsl.com>; Wed, 16 Mar 2022 06:39:24 -0700 (PDT)
Received: from smtp1.hushmail.com (smtp1.hushmail.com [65.39.178.135]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 532D73A187F for <sipcore@ietf.org>; Wed, 16 Mar 2022 06:39:24 -0700 (PDT)
Received: from smtp1.hushmail.com (localhost [127.0.0.1]) by smtp1.hushmail.com (Postfix) with SMTP id B55DFE00E84 for <sipcore@ietf.org>; Wed, 16 Mar 2022 13:39:23 +0000 (UTC)
X-hush-tls-connected: 1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=hush.com; h=date:to:subject:from; s=hush; bh=NskY42D2HbLxQKIpY0XZT7lRrbOTzNd8pWPAuC3zIN8=; b=M71iXj2x+t9/Pk+YK4Rk6o/CI+UEl/+RiNFj8avQdjmbEIj/3KsR/Kuv8xuwKnFk7BXWffO1MbOtg6f8qL5aM4d/nXCHi0Qj387tnQwmV/7+Kv+ukEDfNkZfuPlCMTgrZ1swSjbN0z2d3utnTdzCmmbXkfOBrKjmnAciFmlfAC1PeUuMdgVMqRkNbZdcqWv+bYojXO/egNFvpMYFLG615dgvk5HI1DsAucEb0Xsa+UrlJFoHMk6Ce8a0Chcofw4IYXD11WTcwRHTilXojb1gyFtFpwBgNd59snSUAb52Zu1BjtqDGaBtJWdFQJS/tLQIK/WEnSGQFgv59uKoHqDpig==
Received: from smtp.hushmail.com (w6.hushmail.com [65.39.178.92]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp1.hushmail.com (Postfix) with ESMTPS; Wed, 16 Mar 2022 13:39:23 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 48) id 351BE80E2C5; Wed, 16 Mar 2022 13:39:23 +0000 (UTC)
MIME-Version: 1.0
Date: Wed, 16 Mar 2022 19:39:23 +0600
To: Henning Schulzrinne <hgs@cs.columbia.edu>, David Holmes <david.holmes@t-mobile.com>
Cc: stir@ietf.org, SIPCORE <sipcore@ietf.org>
From: Samir Srivastava <srivastava_samir@hush.com>
In-Reply-To: <CACgrgBYgmg1_auAkUOCuf07BF=CT_LVMpYA4-7eXSUwK0GM3og@mail.gmail.com>
References: <CACgrgBa-7pxgHygj+-bcE36AT3REBO1VDVRpyvj+auLnHN4+ug@mail.gmail.com> <MWHPR02MB287805ED59554A1C8FF99761AC0D9@MWHPR02MB2878.namprd02.prod.outlook.com> <CACgrgBYgmg1_auAkUOCuf07BF=CT_LVMpYA4-7eXSUwK0GM3og@mail.gmail.com>
Content-Type: multipart/alternative; boundary="=_3beb5ed0c4d3dc43d8ac12a257641c43"
Message-Id: <20220316133923.351BE80E2C5@smtp.hushmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/0MnJe3msq6UEh52Bt23f1rhpVnQ>
Subject: Re: [sipcore] [stir] Adding categories from sipcore-callinfo-spam to draft-ietf-sipcore-callinfo-rcd-04
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Mar 2022 13:39:29 -0000
Hi, Please analyze the SPAM in Complete Cashless Economy and Complete Multimedia Recording environment. When there is end-to-end traceability, we can know the source of income of Spammers. Spammers can not lie about the volume. This co-relation can force the penalties for spammers and spam call volume will be reduced drastically. Apart from SPAM, these fixes other malpractices also. Refer the work at https://samirsrivastava.typepad.com . ThanksSamir On 3/13/2022 at 2:15 AM, "Henning Schulzrinne" wrote:The basic idea originated in the FCC robocall strike force a few years ago, with lots of carrier participation, so you could go back to the various FCC reports that were produced at the time for the motivation and background (e.g., https://transition.fcc.gov/cgb/Robocall-Strike-Force-Final-Report.pdf and https://www.fcc.gov/file/12311/download). This I-D and requirements have been discussed since 2017, so this is hardly a new idea. The draft itself has been through IESG review - I just never got around to implement the changes requested. The basic requirement is that we want the receiving callee to make automated or semi-automated judgements. Currently, the RCD draft has a free-form field, but that doesn't really help for anything automated (or, say, displaying icons or other graphical elements). Like all spam labeling, this is probabilistic, i.e., if you're waiting for perfection, this isn't for you. Current robocall filtering services already label numbers with categories (they are in the same ballpark, but not exactly the same and each seems to differ a bit). There are at least two possible sources: * For some labels, the calling party (with signing) will insert the information, presumably for the more "positive" labels like "health" or "government" or "personal". If a carrier lies, this becomes either a reputational issue ("never trust labels from carrier X") or enforcement matter (e.g., as a potential deficiency in robocall mitigation). The label may be part of the KYC process when a carrier signs up a customer - after all, in almost all cases this is pretty obvious ("your business says Joe's Travel Agency. You are picking the healthcare designation how?") A terminating carrier may, for example, decide to only trust known carriers (say, T-Mobile) in deciding whether to convey this information to the called party. * An intermediary service used by the terminating carrier labels (signed) numbers based on honeypots, crowdsourcing or number databases, probably more focused on negative labels like "telemarketing" or "fraud". Again, versions of this exist today. Henning On Sat, Mar 12, 2022 at 3:10 PM Holmes, David wrote: Hi Henning, Interesting idea, but who could define the categories, and who would verify the claims? There may be something here, but this is a good example of where we should agree the use cases and then define requirements before leaping to solutions. BR/David Holmes/T-Mobile USA Get Outlook for Android ------------------------- From: stir on behalf of Henning Schulzrinne Sent: Saturday, March 12, 2022 9:24:47 AM To: stir@ietf.org ; SIPCORE Subject: [stir] Adding categories from sipcore-callinfo-spam to draft-ietf-sipcore-callinfo-rcd-04 [External] In trying to get back to looking at my ancient, dusty draft, a thought: I think RCD would be significantly more useful if it contained standardized categories of callers, such as the one included in callinfo-spam. This allows much better user interfaces and automated handling ("send all political calls to voicemail", "play special ringtone for personal calls"). Henning
- [sipcore] Adding categories from sipcore-callinfo… Henning Schulzrinne
- Re: [sipcore] [stir] Adding categories from sipco… Holmes, David
- Re: [sipcore] [stir] Adding categories from sipco… Henning Schulzrinne
- Re: [sipcore] [stir] Adding categories from sipco… Samir Srivastava
- Re: [sipcore] [stir] Adding categories from sipco… Samir Srivastava
- Re: [sipcore] [stir] Adding categories from sipco… Gorman, Pierce
- Re: [sipcore] [stir] Adding categories from sipco… Samir Srivastava
- Re: [sipcore] [stir] Adding categories from sipco… Gorman, Pierce
- Re: [sipcore] [stir] Adding categories from sipco… Samir Srivastava