Re: [dispatch] New Version Notification for draft-gundavelli-dispatch-e911-wifi-00.txt

Brian Rosen <br@brianrosen.net> Fri, 31 March 2023 09:02 UTC

Return-Path: <br@brianrosen.net>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F0E5C14CE55 for <dispatch@ietfa.amsl.com>; Fri, 31 Mar 2023 02:02:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.084
X-Spam-Level:
X-Spam-Status: No, score=-2.084 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 WBtlRvJmsSPb for <dispatch@ietfa.amsl.com>; Fri, 31 Mar 2023 02:02:22 -0700 (PDT)
Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (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 6FD62C14CE25 for <dispatch@ietf.org>; Fri, 31 Mar 2023 02:02:22 -0700 (PDT)
Received: by mail-qt1-x82c.google.com with SMTP id a5so21065234qto.6 for <dispatch@ietf.org>; Fri, 31 Mar 2023 02:02:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen.net; s=google; t=1680253341; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=nqLpfjU9OXRdMsIhweG8vbS5eD71Y4p27xht6n7wtck=; b=ZP2crdX6RNywTTqrGf1rE9v3RjDQho2CjjQjVznHa7KX3X+ynz0A6dkHQUH7UoXhlQ tdeo65bEll4UA4937DAGPhOVwZsh5P2ALZdTzOz77BczKCSczjLap7pJhk1o1phfgVsL zSyMeZGHEoGR2s5dLjVWjY0xz/QZWWHzkiZz0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680253341; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=nqLpfjU9OXRdMsIhweG8vbS5eD71Y4p27xht6n7wtck=; b=boqPzIdvmrMBVIPSU/N6D8YlMcpKmMzBjJwpsMcl0Jre40FpX1uguHQ1/mT2pcUo8O i7Sy/O+CvU3oO607CNKytVV1NOkGbD/sg7T82SHlkaGidQv/u5sUslMiyEu8YTml9U5Y 3MYzB2qW5ppLnG2pOvx4TBsbc6AX2mo/V5YhjvcI3bb/b73S2hPlYlPicoOlx79JWto9 hI/sGMBZf5Wcd5fR129EsiDb1DnV2scT9YlVLY8AIzwptzBPGyrDqp+qDuOb6Ov3oQGn 6YLm38h0G+UbMQnI3f1dh4JDlnCpWxSWK7PEpRGR2x7vJaht5REcUatq4ebBAZ7CsoKk f4RA==
X-Gm-Message-State: AAQBX9cb+RQE63oto5hI64R+AO8dPqgRh91ukrhW8162xwyiBmLwf9tw 2A6e3i48xVYUoy5wylO+C2QgNOdBb+YXipAonRU=
X-Google-Smtp-Source: AKy350ZVjRHj4+3ig7tfNyWDL47Un4m94dDovKfexo57+7rL/XSm83IwVI/KrtEKOl/i+Jtt1V34pA==
X-Received: by 2002:a05:622a:1802:b0:3bf:c458:5bac with SMTP id t2-20020a05622a180200b003bfc4585bacmr7392365qtc.0.1680253341423; Fri, 31 Mar 2023 02:02:21 -0700 (PDT)
Received: from smtpclient.apple ([185.199.103.122]) by smtp.gmail.com with ESMTPSA id m17-20020ae9e011000000b00746b2ca65edsm501328qkk.75.2023.03.31.02.02.20 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 31 Mar 2023 02:02:20 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.300.101.1.3\))
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <385DA58A-5118-44EF-9E8A-B8FA5F28F4EA@cisco.com>
Date: Fri, 31 Mar 2023 12:02:08 +0300
Cc: "dispatch@ietf.org" <dispatch@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E83FA22-CF07-4C38-B73C-41AC1AEEB688@brianrosen.net>
References: <167875162972.58518.19006032661356449@ietfa.amsl.com> <385DA58A-5118-44EF-9E8A-B8FA5F28F4EA@cisco.com>
To: "Sri Gundavelli (sgundave)" <sgundave=40cisco.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3731.300.101.1.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/OBnVskH_WKY7_a32wTsKnGfeQCM>
Subject: Re: [dispatch] New Version Notification for draft-gundavelli-dispatch-e911-wifi-00.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Mar 2023 09:02:26 -0000

I have read this draft.

It is totally lacking context of current and evolving standards in emergency calling, including:
1. Basic IETF emergency calling standards (/RFC4119/RFC5222/RFC5985/RFC6881)
2. NG911 and NG112 standards that are being deployed, which are based on the IETF standards
3. ETSI and ATIS standards that support the above

While I don’t know enough about WiFi or some of the 3GPP standards to comment on the technical approach in the doc, I am intimately familiar with what is deployed, and about to be deployed in emergency calling and this doc can’t begin to get considered until it deals with the issues associated with the IETF/NENA/EENA/ETSI/ATIS work.

As a really simple start, authors might consider that 9-1-1 is North America only, while the IETF is world-wide.

Brian



> On Mar 27, 2023, at 12:35 AM, Sri Gundavelli (sgundave) <sgundave=40cisco.com@dmarc.ietf.org> wrote:
> 
> Dear All:
> 
> Attached is the link to the document on Supporting emergency 911 services over Wi-Fi. The attached document proposes an approach based on WBA's Wi-Fi OpenRoaming and uses many other elements which are already in standards. 
> 
> We are looking for some technical feedback. We believe there is value in IETF identifying new methods for improving e911 service access.
> 
> Appreciate any feedback.
> 
> Regards
> Sri
> 
> 
> 
> Name: draft-gundavelli-dispatch-e911-wifi
> Revision: 00
> Title: Emergency 911 Services over Wi-Fi
> Document date: 2023-03-13
> Group: Individual Submission
> Pages: 15
> URL: https://www.ietf.org/archive/id/draft-gundavelli-dispatch-e911-wifi-00.txt <https://www.ietf.org/archive/id/draft-gundavelli-dispatch-e911-wifi-00.txt>
> Status: https://datatracker.ietf.org/doc/draft-gundavelli-dispatch-e911-wifi/ <https://datatracker.ietf.org/doc/draft-gundavelli-dispatch-e911-wifi/>
> Htmlized: https://datatracker.ietf.org/doc/html/draft-gundavelli-dispatch-e911-wifi <https://datatracker.ietf.org/doc/html/draft-gundavelli-dispatch-e911-wifi>
> 
> 
> 
> 
> Abstract:
> Proposed is an approach for supporting emergency 911 services over
> IEEE 802.11 based Wi-Fi access networks. This approach leverages the
> legal framework and the building blocks of the OpenRoaming federation
> for extending emergency 911 calling support to already deployed tens
> of thousands of OpenRoaming Wi-Fi hotspots. The proposal addresses
> the key issues in emergency calling, around discovery and
> authentication to access network supporting emergency services,
> emergency access credentials, location determination of the emergency
> caller, and delivering emergency voice service configuration to the
> device and call routing.
> 
> 
> 
> 
> 
> 
> 
> 
> The IETF Secretariat
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch