Re: [sipcore] WG adoption Request

worley@ariadne.com Tue, 03 October 2023 16:11 UTC

Return-Path: <worley@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 E8B4AC151084 for <sipcore@ietfa.amsl.com>; Tue, 3 Oct 2023 09:11:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.693
X-Spam-Level:
X-Spam-Status: No, score=-1.693 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B5Pw7EkI47Qo for <sipcore@ietfa.amsl.com>; Tue, 3 Oct 2023 09:11:43 -0700 (PDT)
Received: from resqmta-c1p-024063.sys.comcast.net (resqmta-c1p-024063.sys.comcast.net [96.102.19.40]) (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 E1C23C15C509 for <sipcore@ietf.org>; Tue, 3 Oct 2023 09:11:42 -0700 (PDT)
Received: from resomta-c1p-023413.sys.comcast.net ([96.102.18.230]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resqmta-c1p-024063.sys.comcast.net with ESMTP id ndVpqnvIhFzhonhxtq2OsE; Tue, 03 Oct 2023 16:09:41 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20211018a; t=1696349381; bh=QCMXt944zPNY43O3nhs8nrKQ/ueNnpX5QkGrKl+3e6w=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID:Xfinity-Spam-Result; b=QKls6174QpX/EiMjiUW6ovSaCZs1IOogVCbG9DhOdfTC7NoVLwGG+XSyKGQYv47pT BX6FS03EWxMEekFJOiVXvo9u+ANhdMG4rKLNALPlINu3xuuB4lfPFCgF+Y65hnxsD9 gYzqLKolPSM+sBuuBEr+nUZwg8qPTW5NcRngWq3x0J13niCnnWCP8KGWDwu8pPASf+ hiRQtGCDgoBUlW3VU5VuH77wz0E5gezCv+Ip5FEqYlebHM6fDgBrvNWevMJEZTdlWM VD16+IvphyJ0Bf0jXuxazPsFKQvYq//X//khCBD3vjapKHJIgemWNYA/kwLKT9QS49 OLICbmro1Z85g==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430::fa19]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resomta-c1p-023413.sys.comcast.net with ESMTPA id nhxVqQvvoNZp5nhxVqAi4j; Tue, 03 Oct 2023 16:09:18 +0000
Received: from hobgoblin.ariadne.com (localhost [127.0.0.1]) by hobgoblin.ariadne.com (8.16.1/8.16.1) with ESMTPS id 393G9G142953572 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Tue, 3 Oct 2023 12:09:16 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.16.1/8.16.1/Submit) id 393G9Fi12953569; Tue, 3 Oct 2023 12:09:15 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Shrawan Khatri <skhatri@qti.qualcomm.com>
Cc: R.Jesske@telekom.de, br@brianrosen.net, sipcore-chairs@ietf.org, sipcore@ietf.org, lguellec@qti.qualcomm.com
In-Reply-To: <CH3PR02MB98593C43D8D79009051426FC8CFCA@CH3PR02MB9859.namprd02.prod.outlook.com> (skhatri@qti.qualcomm.com)
Sender: worley@ariadne.com
Date: Tue, 03 Oct 2023 12:09:15 -0400
Message-ID: <87v8bnu1qs.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/ITsbFTMDsvfpkeNLTT7YB_WuJoU>
Subject: Re: [sipcore] WG adoption Request
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 03 Oct 2023 16:11:47 -0000

> https://datatracker.ietf.org/doc/draft-khatri-sipcore-call-transfer-fail-response/

One point of concern is that this proposal needs to be useful within SIP
as it is deployed.  Given the discussion I've seen so far, it's not
clear operators (either PSTN or simpler SIP-over-Internet) feel
sufficient need for this functionality to deploy it.

I also have serious questions about the detailed failure codes.  Why,
after all, should "video call" or "real time text call" be causes of
failure?  SIP handles all media types symmetrically and yet the current
text wants to categorize calls according to the media they handle.  This
is especially relevant because a call transfer always in media
renegotiation, and so the active media after the transfer might be
different than the active media before the transfer.

(Thinking more about this, I can imagine the fuss that deaf/real-time
text advocate Iljitsch van Beijnum would kick up:  You can transfer
voice calls but transfers of RTT calls are rejected!  (It's actually
conceivable that being unable to transfer RTT calls would be classified
as a violation of US anti-discrimination law.))

I also object to the current use of "granular" to mean "detailed" or
"fine-grained", but that's less important.

Dale