From nobody Mon Jul 11 14:44:02 2022 Return-Path: X-Original-To: stir@ietfa.amsl.com Delivered-To: stir@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B21FC049C0E for ; Mon, 11 Jul 2022 14:44:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.893 X-Spam-Level: X-Spam-Status: No, score=-1.893 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, 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 (2048-bit key) header.d=brianrosen-net.20210112.gappssmtp.com 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 Qx02gbV4t5wI for ; Mon, 11 Jul 2022 14:43:56 -0700 (PDT) Received: from mail-il1-x130.google.com (mail-il1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) (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 7A472C16ECAC for ; Mon, 11 Jul 2022 14:43:45 -0700 (PDT) Received: by mail-il1-x130.google.com with SMTP id v2so3800200ilo.7 for ; Mon, 11 Jul 2022 14:43:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20210112.gappssmtp.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=hVUKNdQGYx5DCfJGoA7QjbhScO2o/EE/hyrMIKkUeUA=; b=Xvf+VAI8fMV5ILbuSW91M8odiCTX5KVIiRe6m9fhs0fZZeCgeAwAONwNTRu58suYTf aLDMikKLURbkekAv0ltGSvo2V6qJaUsc+TAoBP8hKkcrIJn6hfcWaPBmtx/ijpiBJQe7 YMCX2Vjax3NF/b4Cf0ZMat3u7ww5poQBBcGNZ70EqdtP2XgEZ0uEIkUo0iv5pJlbPibE SoE3KLufOJwLkcDLau1XCCTVFAZezrfA+tGfhp8vTWOJDya0A65USmSk/KkZEsUxrHBp Kz+5lKV5cizyStY6WbmlEaEOcSdFp0QWOQGH3IaTQXXs1o4cuZMLopv/rj5XOa+tBUUC VTFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=hVUKNdQGYx5DCfJGoA7QjbhScO2o/EE/hyrMIKkUeUA=; b=C/n6BJmKEaT5Y3y7ajDdO/6OraNBEvcMwkjKcAda3/jjiFD2Tnlp50yHx7pJyVQiHW Ndo8w9S1NBDLZUnHwqzav6FbT28tfOmk7HKhWRVNFZzAlOP4Mvb90SkGGdsD7pkJMb+c cbsa9BroiRpmcSOuFqV8V1WPkzU+mbP2qiABTjYvUQz22W1BxcidLB04A60PyxbVUG0F 10JhjJ+0LSKSQcmBtfwPpyuM7bMOWFTPc9N0Omo/62851n4oh9hStQlQV0UjIcEiaooa lnq/m45p3DzATdaSCUS6Lp/whitCLGuch2YlkXzOgjBHk4Oevs7um7UftfnWb2Y3lOQS 33JA== X-Gm-Message-State: AJIora/LmVw8MI4Tk30aPFIEGck1zDTKDpLiVITXrhPvxfV8oTjB0qGf 1aCZVDIkrScSVZ0f6Y46e/r8xfdTp+ZhGWhB X-Google-Smtp-Source: AGRyM1uCWwIg4U9pz4t7/CAwoWH80bZ0vW0IcMIZQScPdHkV4Fz2KNVZlx8Kr2ofM8IbuKObKLZreA== X-Received: by 2002:a05:6e02:1a0a:b0:2dc:7a5e:5869 with SMTP id s10-20020a056e021a0a00b002dc7a5e5869mr4430247ild.90.1657575824397; Mon, 11 Jul 2022 14:43:44 -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 x1-20020a02ac81000000b00339cdf821dasm3324590jan.51.2022.07.11.14.43.43 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 Jul 2022 14:43:44 -0700 (PDT) From: Brian Rosen Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_1F44A26D-0214-480C-9BA8-B8C15E8A8E3A" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.31\)) Date: Mon, 11 Jul 2022 17:43:42 -0400 In-Reply-To: <24A7B631-43DD-4C49-B69C-90AE098164B6@nostrum.com> Cc: IETF STIR Mail List , stir-chairs@ietf.org To: Ben Campbell References: <24A7B631-43DD-4C49-B69C-90AE098164B6@nostrum.com> X-Mailer: Apple Mail (2.3696.100.31) Archived-At: Subject: Re: [stir] WGLC: draft-ietf-stir-messaging-02 X-BeenThere: stir@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: Secure Telephone Identity Revisited List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Jul 2022 21:44:00 -0000 --Apple-Mail=_1F44A26D-0214-480C-9BA8-B8C15E8A8E3A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I have finally looked at this document and have only a few comments: 1. Section 3.1 seems to indicated that messaging over RFC4103 is = different from messaging defined in 5194. 5194 uses 4103, so there is = no difference. You can cite either. I=E2=80=99d probably cite 4103. = The important point is that it is signaled by INVITE, and thus existing = STIR works. 2. Would it be helpful to better describe how emergency services use = MESSAGE? It=E2=80=99s used to signal a non interactive call, for = example, an alarm, which does not have any two way interactive media but = has data crucial for emergency services to get. There is no durable = session: we use pager mode MESSAGE to get the data. Emergency services = use MSRP also, but that is covered by STIR on INVITE. Brian > On Apr 24, 2022, at 7:53 PM, Ben Campbell wrote: >=20 > Hi, >=20 > This is a 2-week STIR working group last call of = https://datatracker.ietf.org/doc/draft-ietf-stir-messaging = . >=20 > Please send feedback to the authors and the mail list by Monday, 9 May = by the end-of-business wherever you are. All feedback is welcome, = including feedback of the form of =E2=80=9CI read this and it is ready = to progress.=E2=80=9D >=20 > Thanks! >=20 > Ben (For the STIR chairs). >=20 >=20 > _______________________________________________ > stir mailing list > stir@ietf.org > https://www.ietf.org/mailman/listinfo/stir --Apple-Mail=_1F44A26D-0214-480C-9BA8-B8C15E8A8E3A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 I = have finally looked at this document and have only a few comments:
1.  Section 3.1 seems to indicated that messaging over = RFC4103 is different from messaging defined in 5194.  5194 uses = 4103, so there is no difference.  You can cite either.  I=E2=80=99= d probably cite 4103.  The important point is that it is signaled = by INVITE, and thus existing STIR works.

2. Would it be helpful to better = describe how emergency services use MESSAGE?  It=E2=80=99s used to = signal a non interactive call, for example, an alarm, which does not = have any two way interactive media but has data crucial for emergency = services to get.  There is no durable session: we use pager mode = MESSAGE to get the data. Emergency services use MSRP also, but that is = covered by STIR on INVITE.


Brian

On Apr = 24, 2022, at 7:53 PM, Ben Campbell <ben@nostrum.com> wrote:

Hi,

This is a 2-week STIR working group = last call of https://datatracker.ietf.org/doc/draft-ietf-stir-messaging&= nbsp;.

Please = send feedback to the authors and the mail list by Monday, 9 May by the = end-of-business wherever you are. All feedback is welcome, including = feedback of the form of =E2=80=9CI read this and it is ready to = progress.=E2=80=9D

Thanks!

Ben (For the STIR chairs).


_______________________________________________
stir mailing list
stir@ietf.org
https://www.ietf.org/mailman/listinfo/stir

= --Apple-Mail=_1F44A26D-0214-480C-9BA8-B8C15E8A8E3A--