Re: [Ecrit] Changing the LoST Location Profile registry from Standards Action to Specification Required
Randall Gellens <rg+ietf@coretechnologyconsulting.com> Fri, 25 September 2020 21:15 UTC
Return-Path: <rg+ietf@coretechnologyconsulting.com>
X-Original-To: ecrit@ietfa.amsl.com
Delivered-To: ecrit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 351303A09C0 for <ecrit@ietfa.amsl.com>; Fri, 25 Sep 2020 14:15:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.574
X-Spam-Level: *
X-Spam-Status: No, score=1.574 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_RELAY_MUA_TO_MX=3.473, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EC8bRcGP90XJ for <ecrit@ietfa.amsl.com>; Fri, 25 Sep 2020 14:15:18 -0700 (PDT)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id E69E83A0E4B for <ecrit@ietf.org>; Fri, 25 Sep 2020 14:14:47 -0700 (PDT)
Received: from [99.111.97.181] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Fri, 25 Sep 2020 14:14:47 -0700
From: Randall Gellens <rg+ietf@coretechnologyconsulting.com>
To: Ted Hardie <ted.ietf@gmail.com>
Cc: ecrit@ietf.org
Date: Fri, 25 Sep 2020 14:14:46 -0700
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <15F97CDF-70CC-4612-B29E-80B43ED2DB35@coretechnologyconsulting.com>
In-Reply-To: <CA+9kkMAgHi=+f38nCc-KbiEwjENW4aCkR=Ww5rOQTvuaA4aOcQ@mail.gmail.com>
References: <795B3FC5-EDE8-49C2-96D9-EE785050DC2B@coretechnologyconsulting.com> <CA+9kkMAgHi=+f38nCc-KbiEwjENW4aCkR=Ww5rOQTvuaA4aOcQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_BE760295-339E-4006-9666-F7977215C973_="
Embedded-HTML: [{"HTML":[927, 2643], "plain":[579, 1743], "uuid":"E65D6A35-8278-465F-A385-3E2EB79D5E17"}]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/lhAde75wLHNrkNMdKckk3X6IN8Y>
Subject: Re: [Ecrit] Changing the LoST Location Profile registry from Standards Action to Specification Required
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ecrit/>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Sep 2020 21:15:19 -0000
Hi Ted, Thanks for your review, I appreciate it. If I understand, you're suggesting that in the IANA Considerations section it not name the expert reviewer (I thought I needed to), and to replace "The reviewer should use a criteria of a clear need and unambiguous definition for any new value" with "The reviewer should verify that any proposed value is specified by NENA or another SDO for emergency services, and meets a criteria of a clear need and unambiguous definition"? And also replace RFC 5226 with RFC 8126. --Randall On 25 Sep 2020, at 11:02, Ted Hardie wrote: > Hi Randy, > > Thanks for sharing the document. A couple of suggestions: a > citation to > RFC 8126 would be useful, since "specification required" is defined > there. > I'd also suggest that you change the IANA considerations in two ways. > At > the moment, you name an expert reviewer, which is a bit out of the > ordinary; I'd suggest removing that. Second, you currently have this > text > in the introduction: > > This document changes the registry policy to Specification > Required, > allowing other SDOs such as NENA to add values. > > "Specification required" is actually a good bit more open than this, > as it > allows the expert to permit informal specifications (like > internet-drafts). If this change is really specific to NENA and > similar > emergency services bodies, I'd suggest moving this to the IANA > considerations and making that an explicit instruction to the expert. > That > would permit standards action plus those SDOs but would support the > expert > continuing to limit the registry beyond those uses. > > best regards, > > Ted Hardie > > On Fri, Sep 25, 2020 at 9:16 AM Randall Gellens < > rg+ietf@coretechnologyconsulting.com> wrote: > >> Hi ECRIT, >> >> I have a short draft that changes the policy of the LoST Location >> Profile registry from Standards Action to Specification Required (so >> NENA can add values): >> >> https://www.ietf.org/id/draft-ecrit-location-profile-registry-policy-00.txt >> >> (The registry is at >> >> https://www.iana.org/assignments/lost-location-profiles/lost-location-profiles.xhtml >> ). >> >> Comments are requested. >> >> --Randall >> >> _______________________________________________ >> Ecrit mailing list >> Ecrit@ietf.org >> https://www.ietf.org/mailman/listinfo/ecrit >>
- [Ecrit] Changing the LoST Location Profile regist… Randall Gellens
- Re: [Ecrit] Changing the LoST Location Profile re… Ted Hardie
- Re: [Ecrit] Changing the LoST Location Profile re… Randall Gellens
- Re: [Ecrit] Changing the LoST Location Profile re… Randall Gellens