Re: [dispatch] New Version Notification for draft-gundavelli-dispatch-e911-wifi-00.txt Fri, 31 March 2023 16:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BC9A1C140675 for <>; Fri, 31 Mar 2023 09:01:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.981
X-Spam-Status: No, score=-0.981 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 1o6DppiJj7F2 for <>; Fri, 31 Mar 2023 09:00:59 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5BFA8C15C513 for <>; Fri, 31 Mar 2023 09:00:58 -0700 (PDT)
Received: from ([]) by with ESMTP id iCVtpHLwkNDL9iH9UpDw90; Fri, 31 Mar 2023 15:58:56 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20211018a; t=1680278336; bh=anKGdA12IXdX6UlMvB5rv7r8F0KpS3EYTPt2wGv3oxk=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID:Xfinity-Spam-Result; b=s5TP8uDxZw5bV1TAcD4f76sIkwWQfh7IxLAnC5LVBq4/xi+H3SVYRar0KwVs1aEm9 fS6+KQcunPNQ0ibIwp/kIOkzFpDCj45/JiXPSO4AWdPtf2L60PmBBwB/l8w0AHtUuZ i/DNyNjmn42rGRAAci4e7L+IzaPF1YUM/vWhFIOwLIsOGkXn2TmLNXhJiAQiWZrF20 xBg5P7zTkF1wi2l/tOMDkSpORt/6Tzh4n90vqc/wsHHPCj91CqF6r5nnPOTGftc0vG x7QivLUlpsBT+Ww/hN5lTe6bu0a5foooAB4J9WjioTzS24POhx8QntPNjDR49v3ZKh z+raEpQQkJ9Dw==
Received: from ([IPv6:2601:192:4a00:430::94f3]) by with ESMTPA id iH9NpJ5HRqdkEiH9SpfiV5; Fri, 31 Mar 2023 15:58:55 +0000
X-Xfinity-VMeta: sc=-100.00;st=legit
Received: from (localhost []) by (8.16.1/8.16.1) with ESMTPS id 32VFwnbw3085067 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Fri, 31 Mar 2023 11:58:49 -0400
Received: (from worley@localhost) by (8.16.1/8.16.1/Submit) id 32VFwmKn3085064; Fri, 31 Mar 2023 11:58:48 -0400
X-Authentication-Warning: worley set sender to using -f
To: "Sri Gundavelli (sgundave)" <>
In-Reply-To: <> (
Date: Fri, 31 Mar 2023 11:58:48 -0400
Message-ID: <>
Archived-At: <>
Subject: Re: [dispatch] New Version Notification for draft-gundavelli-dispatch-e911-wifi-00.txt
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 31 Mar 2023 16:01:03 -0000

"Sri Gundavelli \(sgundave\)" <>
> Thanks a lot for reviewing the document. I agree, the document should
> provide the larger emergency calling context. The current art, the
> elements in the system, interfaces with the PSAPs and other touch
> points. We are familiar with the prior efforts in IETF and also
> standards bodies including 3GPP and around ATIS reports. Perhaps a
> discussion on how NG911/NG211 emergency service network are deployed
> will be useful. The document requires more work, and this is just a
> starting point. 

I am by no means an expert on emergency calling.  But two generic points
come to mind.

One is to establish connection with the people working in the area.
More subtly, make sure you've absorbed the terminology that they use, to
signal to them that your work is to be taken seriously.  In this
instance, the common emergency number in the EU is 112 (not 211).  (And
the GSM standard requires that calls dialed as 112 be forwarded to the
local emergency number, even if it isn't 112.)

Another is to establish that there is implementor interest.  There's no
point trying to perfect technology for which there is no market.
Emergency communications is an unusual situation *for the IETF* in that
it is inherently entwined with government structures, those that operate
it.  There are only a few hundred *possible* customers for this
technology.  So early in the process, you should discern that the
relevant operators would like to see the ability to carry emergency
calls over WiFi.  Or more subtly, to discern what features such an
emergency call system would need to be able to convince the operators to
be interested in it.