Re: [sipcore] draft on rich call data and Call-Info

Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 05 August 2020 16:16 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 B9A603A0C8E for <sipcore@ietfa.amsl.com>; Wed, 5 Aug 2020 09:16:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.951
X-Spam-Level:
X-Spam-Status: No, score=-2.951 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, NICE_REPLY_A=-0.949, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alum.mit.edu
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 mvbaEjBHvDpP for <sipcore@ietfa.amsl.com>; Wed, 5 Aug 2020 09:16:42 -0700 (PDT)
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (mail-dm6nam12on2073.outbound.protection.outlook.com [40.107.243.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E6743A0C89 for <sipcore@ietf.org>; Wed, 5 Aug 2020 09:16:42 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZikRBGXbcISKNUbE13r09wVCQK9NUSZyvjjFNm6gOzMhxIxWMtH+6LULR5y4JvPqQUWa+dPybugRXBEBZG/Gzl9CjjlTfKyOfUKOhXhEMxGKZSaJQZJ7WkXRMoiA3rShDk0Xh5zELugJ2RAct78+gJEnjWhlmlv4GO+idHVgYSUS9GN7xpiNyKohJAInG9POUFCzlRA558SH8u7mXR+hsLHBPG2omhp8svbmjS94tnZIHRdXzP0iNeQoE+agKYmN7hvrW4fzdsfT1klJY6O96pDID9dWNKRrxf/0YJ3EHLePGMWgX0kc9E/io9Jt7Dz20/wexV0VQPdZbO6VLv2/qg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Gro5idTVfKOylyc39NfdovUHC2Mn2jbiKfdHIhNv5e0=; b=UatsJnDP9vuyit/r0lzYqStIQ9+adw9JXn2INVdOclL7SCB9Q3qUiV3vfD+JchjJbhU/isB1dNf/gFy9IE27UHp6ejwWooHCmMq0xI6Ry4c1c86mcX8pInRNyrcwS01Yft7X8G4UUGCk46DGYLIbOWcGIyFnG+7epnhN6Rma6oRjphjQxOAZDrKSpxoiM2IkxUrXMDhAVzqYlQP5JVriZTiM6Wwt7bJr+F+XsV3PBGdKGWJewG33raYNft0leVliYnJl31KEqXBxuNeJwAebLA8VWoYh7hASKrr2SYgv//Y8IuBTDbPJQHyptPB899Uxhhby7mZ6RX0IARrxXdvs4w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 18.7.68.33) smtp.rcpttodomain=team.neustar smtp.mailfrom=alum.mit.edu; dmarc=bestguesspass action=none header.from=alum.mit.edu; dkim=none (message not signed); arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alum.mit.edu; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Gro5idTVfKOylyc39NfdovUHC2Mn2jbiKfdHIhNv5e0=; b=Sk7A1yN7J/oMKgTyUN6SrCF2qkM50aicTJXUazXec5ggBa+VBNBuFiXqqBnZYC7yWS880Fn9pUjq57cX9WxfZJjuIHmyIlrgJrXv4K+FPCu3ymA3srQ8U3d6B0tAQcYHrP4vjqJFx4sJPfv8jt7O+2+MEm+HV9aNsQKXrqEMLVg=
Received: from SN6PR01CA0036.prod.exchangelabs.com (2603:10b6:805:b6::49) by DM6PR12MB4171.namprd12.prod.outlook.com (2603:10b6:5:21f::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3239.20; Wed, 5 Aug 2020 16:16:41 +0000
Received: from SN1NAM02FT052.eop-nam02.prod.protection.outlook.com (2603:10b6:805:b6:cafe::5d) by SN6PR01CA0036.outlook.office365.com (2603:10b6:805:b6::49) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3239.17 via Frontend Transport; Wed, 5 Aug 2020 16:16:40 +0000
X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 18.7.68.33) smtp.mailfrom=alum.mit.edu; team.neustar; dkim=none (message not signed) header.d=none;team.neustar; dmarc=bestguesspass action=none header.from=alum.mit.edu;
Received-SPF: Pass (protection.outlook.com: domain of alum.mit.edu designates 18.7.68.33 as permitted sender) receiver=protection.outlook.com; client-ip=18.7.68.33; helo=outgoing-alum.mit.edu;
Received: from outgoing-alum.mit.edu (18.7.68.33) by SN1NAM02FT052.mail.protection.outlook.com (10.152.72.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3239.17 via Frontend Transport; Wed, 5 Aug 2020 16:16:40 +0000
Received: from Kokiri.localdomain (c-24-62-227-142.hsd1.ma.comcast.net [24.62.227.142]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.14.7/8.12.4) with ESMTP id 075GGbO1027938 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 5 Aug 2020 12:16:38 -0400
To: "Peterson, Jon" <jon.peterson@team.neustar>, "sipcore@ietf.org" <sipcore@ietf.org>
References: <87AF4B58-D947-417D-AD26-D2D47EE53338@team.neustar> <05017c3b-55e5-c74a-2730-3ba349e14a3d@alum.mit.edu> <3A143F2A-2E4D-4B08-8E61-3F32CB3FB9B4@team.neustar>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <f10862c7-361b-3042-d3f0-1f32949c8774@alum.mit.edu>
Date: Wed, 05 Aug 2020 12:16:37 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.11.0
MIME-Version: 1.0
In-Reply-To: <3A143F2A-2E4D-4B08-8E61-3F32CB3FB9B4@team.neustar>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-EOPAttributedMessage: 0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 17e9cd32-5a89-4e57-c01e-08d8395aefc7
X-MS-TrafficTypeDiagnostic: DM6PR12MB4171:
X-Microsoft-Antispam-PRVS: <DM6PR12MB4171BF14A01749A2E120CBD5F94B0@DM6PR12MB4171.namprd12.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: d6O+3T5Ob54d9kP2f7RGe75DBM+7QP2iDb1qBs1/Xjrni5zfZbad6MdMq63y3ariKGjnIsA87xVYE5bgxcvRvH2hhld0o1/wU/2+AJt0kW5Xn4bckWA2uPIyjS/vjJS8Oap798mIubMrRWPrKkPyE5ViQGFAyp+M4vravn9u6bfDuWr5Gg3Vr/9Q+nqtiEb6fKoAajTCEsIfTyiRZ/fJKVol3wVvaCZTbGuQpPqeCkfqs2eiay9lSc1DTiXjaqnVp3VtemjpZSmt9LBhHyB8cwSJnLeDNLv+sgfA1cPY/jKMRPOEHjpPRnR05MsVR6KKaxgSRABpBcte+bE1e3al6iTiRGJCeYXpMNGJ+1cOWCMIk5Yo2wy/byUKLrtmbDU2ntcfJEOb0Qoub+uUkB+W5ljkRqCcqeCy+WdLzCP2zswbX7Jh22CYEh5F61zXgJxo
X-Forefront-Antispam-Report: CIP:18.7.68.33; CTRY:US; LANG:en; SCL:1; SRV:; IPV:CAL; SFV:NSPM; H:outgoing-alum.mit.edu; PTR:outgoing-alum.mit.edu; CAT:NONE; SFTY:; SFS:(136003)(346002)(376002)(396003)(39860400002)(46966005)(110136005)(2906002)(336012)(82740400003)(36906005)(316002)(356005)(786003)(5660300002)(82310400002)(47076004)(478600001)(7596003)(956004)(31696002)(26005)(8676002)(70586007)(2616005)(86362001)(8936002)(53546011)(31686004)(83380400001)(70206006)(186003)(75432002)(43740500002); DIR:OUT; SFP:1101;
X-OriginatorOrg: alum.mit.edu
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 05 Aug 2020 16:16:40.2781 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 17e9cd32-5a89-4e57-c01e-08d8395aefc7
X-MS-Exchange-CrossTenant-Id: 3326b102-c043-408b-a990-b89e477d582f
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=3326b102-c043-408b-a990-b89e477d582f; Ip=[18.7.68.33]; Helo=[outgoing-alum.mit.edu]
X-MS-Exchange-CrossTenant-AuthSource: SN1NAM02FT052.eop-nam02.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR12MB4171
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/XR0kQmghRCVhwCnSKqapYXQTLs8>
Subject: Re: [sipcore] draft on rich call data and Call-Info
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, 05 Aug 2020 16:16:48 -0000

On 8/5/20 12:01 PM, Peterson, Jon wrote:
> 
> Thanks for taking a glance Paul. Just to the matter of call reason and Subject:
>      
>      Similarly, I think it need do discuss the need for the "call-reason"
>      parameter. As the draft notes, the contents of the Subject header could
>      be used for this purpose. I would like to some some further in
>      investigation of why it is unsuitable before giving up on it.
>      
> Broadly I imagine that call reason might eventually call for structured data to handle cases like internationalization (display the Spanish version if the UE indicates a native Spanish speaker) or broad categories of subject types ("appointment/reservation confirmation" or "IVR callback") that might be handled programmatically in some way. I guess I look at the Subject header as pretty syntactically poor, and moreover something that legacy implementations might expect to treat already in some unhelpful way (most likely by stripping/ignoring it). But I'm interested to hear what people think about this one.

This all makes sense to me. It just needs to make it into the document.

	Thanks,
	Paul