IETF Logo Mail Archive

[sipcore] Re: NENA registries

Richard Shockey <richard@shockey.us> Wed, 30 September 2026 21:49 UTC

Received: from omta38.uswest2.a.cloudfilter.net (omta38.uswest2.a.cloudfilter.net [35.89.44.37]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 0287A4B for <sipcore@ietf.org>; Wed, 30 Sep 2026 21:49:31 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=shockey.us header.s=default header.b=QtFuh2iu; dmarc=none; spf=pass (mx.ietf.org: domain of richard@shockey.us designates 35.89.44.37 as permitted sender) smtp.mailfrom=richard@shockey.us
Received: from eig-obgw-6002b.ext.cloudfilter.net ([10.0.30.203]) by cmsmtp with ESMTPS id C14Xx8DMev0ndC2B3xq1E2; Wed, 30 Sep 2026 21:49:25 +0000
Received: from box5527.bluehost.com ([162.241.218.19]) by cmsmtp with ESMTPS id C2A3xBKvkRC6eC2A3xCjK4; Wed, 30 Sep 2026 21:48:23 +0000
X-Authority-Analysis: v=2.4 cv=FvsF/3rq c=1 sm=1 tr=0 ts=6abd83a7 a=KXpOjjFwo8kCkgxs2x2AJQ==:117 a=KXpOjjFwo8kCkgxs2x2AJQ==:17 a=IkcTkHD0fZMA:10 a=MKtGQD3n3ToA:10 a=1oJP67jkp3AA:10 a=VdqzKS8jKosA:10 a=06TXGDuqNb8A:10 a=ll-iCDY8AAAA:8 a=M0OflfRGAAAA:8 a=48vgC7mUAAAA:8 a=kbVZKZgQYwBIBhGAbPMA:9 a=QEXdDO2ut3YA:10 a=-FEs8UIgK8oA:10 a=VpyrLIdO_Ztbr3SWPBuH:22 a=6yl0mh0s51TKORVA8GqK:22 a=jqBRFv0mrdWfL_K7jfQc:22 a=NWVoK91CQySWRX1oVYDe:22 a=fQpVk8h_2Cg9Fza1blh0:22 a=79wzPuNdQpQ7fyRVCOyA:22
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default; h=Content-transfer-encoding:Content-type:Mime-version:In-Reply-To: References:Message-ID:To:From:Subject:Date:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Unsubscribe-Post: List-Subscribe:List-Post:List-Owner:List-Archive; bh=Nkx4kVky6HwD7qERdZ7uzuN91xNhKWIvVxkr8aU0QdA=; b=QtFuh2iuRqxx6A/kgeINznb+E1 h/Y1wWd7R0XZnnF8s1GSyinhRm5oFxuV0ttLjlhTcefRscYnhKaslZP6NDPrvHugTTB7gie0/4oSf kDDySA8+qGj2dhyWyBwhaP5RV;
Received: from pool-100-36-46-50.washdc.fios.verizon.net ([100.36.46.50]:63166 helo=[192.168.1.89]) by box5527.bluehost.com with esmtpa (Exim 4.100.1) (envelope-from <richard@shockey.us>) id 1xC2A3-00000003NeB-17Wb; Wed, 30 Sep 2026 15:48:23 -0600
User-Agent: Microsoft-MacOutlook/16.113.26092012
Date: Wed, 30 Sep 2026 17:48:22 -0400
From: Richard Shockey <richard@shockey.us>
To: Brian Rosen <br@brianrosen.net>, sipcore@ietf.org
Message-ID: <BC7A2202-2684-4558-8238-57453D9C85D4@shockey.us>
Thread-Topic: [sipcore] NENA registries
References: <F532BCE0-41FE-42CD-81D4-31A299E80B42@brianrosen.net>
In-Reply-To: <F532BCE0-41FE-42CD-81D4-31A299E80B42@brianrosen.net>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box5527.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - shockey.us
X-BWhitelist: no
X-Source-IP: 100.36.46.50
X-Source-L: No
X-Exim-ID: 1xC2A3-00000003NeB-17Wb
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: pool-100-36-46-50.washdc.fios.verizon.net ([192.168.1.89]) [100.36.46.50]:63166
X-Source-Auth: richard@shockey.us
X-Email-Count: 2
X-Org: HG=bhshared;ORG=bluehost;
X-Source-Cap: c2hvY2tleXU7c2hvY2tleXU7Ym94NTUyNy5ibHVlaG9zdC5jb20=
X-Local-Domain: yes
X-CMAE-Envelope: MS4xfPH7wjTW2le0YtJTnuALXnVED7jcg1C12hEvLYr6OubNLXVB3C29lfvSYsNP2T1lcsthz4DJPPfUtrS582bxIhWojK8sZdNUKap2e5fUGvYoVc6sE+9P ufke3+wuiDSTmJ3+njKsyFOh0D5j+FRc2Ksl/nvnjB3HoS6SRx1+LwSOi42sY2f/+7A/0KVqt0WolQ==
X-Spamd-Bar: /
Message-ID-Hash: 2DG5DZL42MST32HQQLEH2EYEPPNKQLTQ
X-Message-ID-Hash: 2DG5DZL42MST32HQQLEH2EYEPPNKQLTQ
X-MailFrom: richard@shockey.us
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-sipcore.ietf.org-0; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [sipcore] Re: NENA registries
List-Id: SIP Core Working Group <sipcore.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/9ju4ecSlgG0C8egYt8FUVBTK508>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Owner: <mailto:sipcore-owner@ietf.org>
List-Post: <mailto:sipcore@ietf.org>
List-Subscribe: <mailto:sipcore-join@ietf.org>
List-Unsubscribe: <mailto:sipcore-leave@ietf.org>

Is there something the SIP Forum/ATIS and the IP NNI can do here to expedite matters?

We get asked about interoperability events quite often given the FCC All IP initiatives. We are well aware of the challenges PSAP's are having getting to NG 911.  You know the folks at FCC PSHS as well as I do.

It’s a simple ASK ! 

What do you want me to do?




Richard Shockey 
Shockey Consulting LLC 
Chairman of the Board SIP Forum 
www.shockey.us <http://www.shockey.us> 
www.sipforum.org 

richard<at>shockey.us 
Skype-Linkedin-Facebook –Twitter rshockey101 
PSTN +1 703-593-2683 





On 9/30/26, 4:49 PM, "Brian Rosen" <br=40brianrosen.net@dmarc.ietf.org <mailto:40brianrosen.net@dmarc.ietf.org>> wrote:


NENA, the North American Emergency Number Association, which is the SDO for emergency calls in US and Canada, is using SIP extensively in its standards, which are being widely deployed. It is in the process of bringing its registry listings up to date.


NENA has a number of SIP Event Packages defined, and it’s not entirely clear what to do about them. The IANA Event packages and Event template-packages Registration Procedure is RFC-Required with Designated Expert. While NENA does have a draft that does a whole bunch of registrations, which could include the current set of SIP event packages, it is a barrier that I think is too high for the value obtained by requiring NENA, or equivalent emergency call SDOs to create an RFC to register their future event packages.


NENA would like to explore the possibility of modifying the Registration Procedure so that an event package starting with the string “emergency-“ uses a document required procedure with the expert verifying that the registrant is a suitable emergency call SDO and the event package is useful for emergency calls or incidents. The current RFC required policy would remain for event packages not having that prefix. NENA would add the registration policy change to its current draft (draft-ietf-ecrit-emergency-registries). 


Does that sound reasonable?


Brian


_______________________________________________
sipcore mailing list -- sipcore@ietf.org <mailto:sipcore@ietf.org>
To unsubscribe send an email to sipcore-leave@ietf.org <mailto:sipcore-leave@ietf.org>

v2.46.0 | Report a Bug | By Email | System Status