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

Chris Wendt <chris-ietf@chriswendt.net> Fri, 09 October 2020 14:23 UTC

Return-Path: <chris-ietf@chriswendt.net>
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 C0E7A3A084A for <sipcore@ietfa.amsl.com>; Fri, 9 Oct 2020 07:23:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=chriswendt-net.20150623.gappssmtp.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 EpINfwcx3ODI for <sipcore@ietfa.amsl.com>; Fri, 9 Oct 2020 07:23:57 -0700 (PDT)
Received: from mail-qk1-x72b.google.com (mail-qk1-x72b.google.com [IPv6:2607:f8b0:4864:20::72b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCAA23A0846 for <sipcore@ietf.org>; Fri, 9 Oct 2020 07:23:57 -0700 (PDT)
Received: by mail-qk1-x72b.google.com with SMTP id x20so3705088qkn.1 for <sipcore@ietf.org>; Fri, 09 Oct 2020 07:23:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chriswendt-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Nmc8FNoPRzfTTEmZKYTwHIJVW48HZTM8eqGai9BKWPs=; b=OooxFyARdaqGw8HvpTL7eA3Id+juNxmLBn77dkoJ4o5vdpIz2wkmmwQID2WH9JW4i2 1DqbFtMtWvy0hOH4Vh9WIfqeBEdB6wvIPaqx8ORP4TcF+4/3geREYbM02eSh54D+g610 nmdtaDRo1yX+oO7KZY5GknaAtuPhROwZhwdytxkv/7/4p9QOGHhVAaF5w0L3gRvzBEgp sEEQFaB2j0j6PtHw2QhXVrrEppl5sydXeqQYNE686x4phul783qIZtaiDA9ZCnwIHOma pbPahl4qHY45HyZS6vNK2e4CrzreLHLA95GRrXUs1BDJBNNBmizplaJLEXjYX917bwvC Z8PA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Nmc8FNoPRzfTTEmZKYTwHIJVW48HZTM8eqGai9BKWPs=; b=H+S5pPj+/EB5MUdys7kwQJZ7vRatdLi7lBu8pcKyGZBoA0d9e88v1ROTl1CXL9WXy3 K0VW9nxOeqPLBI4F3i6XQ8xIFnDqZezCWbGRr9p4oL0xA5KVpcLSo6UtsduxZ7xIXps8 33okMOTK30DVqFSvaWTsW+6X9zhfi+TgFYaaffqICoJsY565tkBkGpvQ13XGcTtDXU8U A9s7La38U7N3Dkh/1ZjBduUtmr0cuoyRWi5fMHV9hlPg6pHtyZSAfHoUkqA9Fqhucy31 9eh6GLEZS3S+i+RuUUGhNgvg+DBfJX+GbSa3oMadp+JmB19YYPx8u7T3EwPHt+TK8Oqh 7OVQ==
X-Gm-Message-State: AOAM533D6VjSs6g8ii2iVf0xr1fANJPJRUvy1xuV+cYerY/36/mrbymF JnYCyMQ6esHyYKBmGhJFr9sfsTVUGeDtiuWs
X-Google-Smtp-Source: ABdhPJyVHP6aSMZPubEPZwyC0CM40u22jO7qHbrJVrM2msjW04kNJTU8o4avXn0lGESihWB8gjPqBw==
X-Received: by 2002:a05:620a:54f:: with SMTP id o15mr13250919qko.91.1602253436865; Fri, 09 Oct 2020 07:23:56 -0700 (PDT)
Received: from [192.168.0.153] (c-69-242-45-210.hsd1.pa.comcast.net. [69.242.45.210]) by smtp.gmail.com with ESMTPSA id q135sm4891387qka.93.2020.10.09.07.23.56 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Oct 2020 07:23:56 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Chris Wendt <chris-ietf@chriswendt.net>
In-Reply-To: <778633be-5252-d5e2-3272-af615f41e8a2@alum.mit.edu>
Date: Fri, 09 Oct 2020 10:23:55 -0400
Cc: "Peterson, Jon" <jon.peterson@team.neustar>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5283B43-7CAF-45AE-A128-BA46ABFA887C@chriswendt.net>
References: <87AF4B58-D947-417D-AD26-D2D47EE53338@team.neustar> <05017c3b-55e5-c74a-2730-3ba349e14a3d@alum.mit.edu> <3A143F2A-2E4D-4B08-8E61-3F32CB3FB9B4@team.neustar> <778633be-5252-d5e2-3272-af615f41e8a2@alum.mit.edu>
To: Brian Rosen <br@brianrosen.net>, "sipcore@ietf.org" <sipcore@ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/sq1jS3WmulKMqAeuZlPcCFhY5R4>
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: Fri, 09 Oct 2020 14:24:00 -0000

So, i think i’ve heard some good suggestions/comments, but not a lot of disagreement that would prevent adoption.

Could I ask for WG adoption for draft-wendt-sipcore-callinfo-rcd-03?

Thanks!

-Chris

> On Aug 5, 2020, at 12:23 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> 
> I had more thoughts after hitting send. So elaborating:
> 
> 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.
> 
> While it makes sense to me that you might want a syntactically richer call reason than what fits in the Subject header, as defined it isn't any richer - it is still just a string.
> 
> 	Thanks,
> 	Paul
> 
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
> 
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore