IETF Logo Mail Archive

Re: [sipcore] WGLC: draft-ietf-sipcore-callinfo-rcd-06

Brian Rosen <br@brianrosen.net> Tue, 15 August 2023 14:49 UTC

Return-Path: <br@brianrosen.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 36397C151553 for <sipcore@ietfa.amsl.com>; Tue, 15 Aug 2023 07:49:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=brianrosen.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 Dfau-SKLSmNq for <sipcore@ietfa.amsl.com>; Tue, 15 Aug 2023 07:49:01 -0700 (PDT)
Received: from mail-yw1-x112f.google.com (mail-yw1-x112f.google.com [IPv6:2607:f8b0:4864:20::112f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CFABC136127 for <sipcore@ietf.org>; Tue, 15 Aug 2023 07:48:57 -0700 (PDT)
Received: by mail-yw1-x112f.google.com with SMTP id 00721157ae682-589a6e26349so2831177b3.1 for <sipcore@ietf.org>; Tue, 15 Aug 2023 07:48:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen.net; s=google; t=1692110936; x=1692715736; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=ADrjgfm8JAWbUNIoKheejWIwTG9zIEHAUtJ86euX4uA=; b=Bc5cJYpVt6rwS0n4Lb8ByXh0NZhie5IifjN3mx4fYHkT291aGK8LnAxJ2fBAQFkGzr PfSl+4I88PIiUD/eabUeEmcOVOVY2f59Yi5/wPpyr+9ye4CCYrncEnelvwWWusKslxEm jJHH7W1Hs0K+4aTXoPWwaMIjOS+sMfbmJpSsw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692110936; x=1692715736; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ADrjgfm8JAWbUNIoKheejWIwTG9zIEHAUtJ86euX4uA=; b=LmEscMWgVkUC5Sl6oJ1p6iAPqdPIuu/yivwziApB+xs9J1FQqwvPjWBCrnELiEtue6 YNGzLh+AcMQ2CM8msCbrY5anIMd9J/zx3tbFZ3Whvbv21XlHEH5YlB4lc+BGKQEJTpgE NH8+rwMARy+8+WXBogTkpOt7FLH18xtjB7HaDyL4vvL+Xt8y92iyWgku0E1dY616gMTx BiDp52h255udIVlVCdruCIJy7Ct2D8JqVyt5Hp/gDjvC6fJsc8oCOf0PIeN+HDMCwglW cwI8SMrLZV/KLKuAoghclLahPR6lOpQaxMtBTA0XiQs+Opo6jkNeq8fulyj3olrttUtd 2DqQ==
X-Gm-Message-State: AOJu0YzDodNxuuELrETipgX0n9W4oTsCoUfsNTKNJ2JMYIqahEGcucEz SJFWFkA1mkgPS7N4cSKC01+RUYG+Uy1v/1fFa0s=
X-Google-Smtp-Source: AGHT+IE73ziWbaP0qRSp1CHWSLx9k8YeH8zh5Tj9/0Kwjb60azSVw3lVaCJ6B/IhTDDUloxuwsGvGw==
X-Received: by 2002:a81:6c92:0:b0:584:1e78:2db6 with SMTP id h140-20020a816c92000000b005841e782db6mr5585709ywc.3.1692110935964; Tue, 15 Aug 2023 07:48:55 -0700 (PDT)
Received: from smtpclient.apple (dynamic-acs-24-154-121-237.zoominternet.net. [24.154.121.237]) by smtp.gmail.com with ESMTPSA id t84-20020a815f57000000b005702bfb19bfsm3455868ywb.130.2023.08.15.07.48.55 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 15 Aug 2023 07:48:55 -0700 (PDT)
From: Brian Rosen <br@brianrosen.net>
Message-Id: <FFD22496-2030-4FA9-BA17-D10FA5F4F090@brianrosen.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F00628FD-1D14-44E7-AC56-07740BE3C7F5"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
Date: Tue, 15 Aug 2023 10:48:43 -0400
In-Reply-To: <0cc14a38-9d1b-8024-8a0c-5e61ee795837@alum.mit.edu>
Cc: sipcore@ietf.org
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
References: <da9ba37b-52a0-c8db-252b-8a6977140581@nostrum.com> <088772af-222e-1fdd-0a00-e6c49edd3d3d@alum.mit.edu> <84624ced-707b-6847-a4bf-d67f5de16c0f@ntlworld.com> <0cc14a38-9d1b-8024-8a0c-5e61ee795837@alum.mit.edu>
X-Mailer: Apple Mail (2.3731.600.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/Pw5pFlITx-VmBgFIDHTmndEGlH8>
Subject: Re: [sipcore] WGLC: draft-ietf-sipcore-callinfo-rcd-06
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, 15 Aug 2023 14:49:06 -0000

We have used new Call-Info purpose parameters in emergency services a lot.  For example, we have an Incident-Id, and a Call-IId that has different semantics to the SIP call id.
The lack of a registry is unfortunate.

I would be happy to contribute text for this document that does the registry, or write a short draft that does it, or add it to a draft we’re working on in ecrit that defines a bunch of new registries.

Brian

> On Aug 14, 2023, at 12:43 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> 
> .

v2.23.0 | Report a Bug | By Email