Re: [Ecrit] Adoption question: Adopt ID as new ECRIT draft?
Randall Gellens <rg+ietf@coretechnologyconsulting.com> Tue, 20 October 2020 21:57 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 51AC73A13FB for <ecrit@ietfa.amsl.com>; Tue, 20 Oct 2020 14:57:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level:
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, 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 girawFsLU15n for <ecrit@ietfa.amsl.com>; Tue, 20 Oct 2020 14:56:58 -0700 (PDT)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id A471A3A13FA for <ecrit@ietf.org>; Tue, 20 Oct 2020 14:56:58 -0700 (PDT)
Received: from [169.254.46.21] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Tue, 20 Oct 2020 14:56:58 -0700
From: Randall Gellens <rg+ietf@coretechnologyconsulting.com>
To: "Caron, Guy" <g.caron@bell.ca>
Cc: Roger Marshall <roger.marshall@comtechtel.com>, ecrit@ietf.org, Allison Mankin <allison.mankin@gmail.com>, Barry Leiba <barryleiba@gmail.com>
Date: Tue, 20 Oct 2020 14:56:57 -0700
X-Mailer: MailMate (1.13.2r5673)
Message-ID: <EDE9B580-450B-4779-9C99-ADFBF8317524@coretechnologyconsulting.com>
In-Reply-To: <12208093b55c4221a0be913aae4e4d09@DG2MBX03-WYN.bell.corp.bce.ca>
References: <BY5PR09MB50766EB51513D0AA71D442D8F4030@BY5PR09MB5076.namprd09.prod.outlook.com> <12208093b55c4221a0be913aae4e4d09@DG2MBX03-WYN.bell.corp.bce.ca>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_EF2668E1-AB07-49C8-9199-1FB99D8019E9_="
Embedded-HTML: [{"HTML":[679, 8479], "plain":[348, 3256], "uuid":"06443B11-ADBF-426C-8CC5-34696813A03B"}]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/OmnVgDvf7zLO0J4QFA5GEvG3rt8>
Subject: Re: [Ecrit] Adoption question: Adopt ID as new ECRIT draft?
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: Tue, 20 Oct 2020 21:57:00 -0000
Thanks for your support and review, Guy. I'd like to better understand the value of adding "non-duplicative". If a proposed profile is duplicative then it seems obvious that there isn't a clear need (since the existing profile with which the proposed one is duplicative meets the need). --Randall On 16 Oct 2020, at 12:18, Caron, Guy wrote: > I support this. > > May I suggest a small change? > > > In the IANA Considerations section, it says: "The reviewer should > verify that any proposed new value is specified by the IETF, NENA, or > a similar SDO, and meets a criteria of a clear need and unambiguous, > interoperable definition." > > > > Which I would change to this: "The reviewer should verify that any > proposed new value is specified by the IETF, NENA, or a similar SDO, > and meets criteria of a clear non-duplicative need and unambiguous, > interoperable definition." > > Thanks, > > Guy > > De : Ecrit <ecrit-bounces@ietf.org> De la part de Roger Marshall > Envoyé : 16 octobre 2020 15:00 > À : ecrit@ietf.org > Cc : Randall Gellens <rg+ietf@coretechnologyconsulting.com>; Allison > Mankin (allison.mankin@gmail.com) <allison.mankin@gmail.com>; Barry > Leiba <barryleiba@gmail.com> > Objet : [EXT][Ecrit] Adoption question: Adopt ID as new ECRIT draft? > > There is a new Internet Draft (Randall Gellens, author) that changes > the policy of a LoST Location Profile registry from Standards Action > to Specification Required. This is being proposed in order to make it > possible for NENA to add values. > > The chairs are asking for working group adoption for this draft. > > Please let the chairs know if there is any objection to adopting this > as an ECRIT work group draft by 10/31/2020. > > Draft: > https://www.ietf.org/id/draft-ecrit-location-profile-registry-policy-01.txt<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fid%2Fdraft-ecrit-location-profile-registry-policy-01.txt&data=04%7C01%7CRoger.Marshall%40comtechtel.com%7Ccc30b87d96554c264c8b08d871fb8cb4%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C0%7C637384672503460823%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=j1BnBRIc46G%2FJjcQPYwG3ra%2FnzxWIVf1u8xid5q50%2F8%3D&reserved=0> > > Registry url: > https://www.iana.org/assignments/lost-location-profiles/lost-location-profiles.xhtml<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.iana.org%2Fassignments%2Flost-location-profiles%2Flost-location-profiles.xhtml&data=02%7C01%7Croger.marshall%40comtechtel.com%7Ca76728e45de74116e76308d861983524%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C1%7C637366653649324637&sdata=ChCvNsoEYcXConlY3oAyug9vE2uqPf6YVg%2Fn6NKUsZk%3D&reserved=0> > > -roger marshall, ECRIT co-chair > NOTICE TO RECIPIENT: This email, including attachments, may contain > information which is confidential, proprietary, attorney-client > privileged and / or controlled under U.S. export laws and regulations > and may be restricted from disclosure by applicable State and Federal > law. Nothing in this email shall create any legal binding agreement > between the parties unless expressly stated herein and provided by an > authorized representative of Comtech Telecommunications Corp. or its > subsidiaries. If you are not the intended recipient of this message, > be advised that any dissemination, distribution, or use of the > contents of this message is strictly prohibited. If you received this > message in error, please notify us immediately by return email and > permanently delete all copies of the original email and any attached > documentation from any computer or other media.
- [Ecrit] Adoption question: Adopt ID as new ECRIT … Roger Marshall
- Re: [Ecrit] Adoption question: Adopt ID as new EC… Brian Rosen
- Re: [Ecrit] Adoption question: Adopt ID as new EC… Caron, Guy
- Re: [Ecrit] Adoption question: Adopt ID as new EC… Randall Gellens
- Re: [Ecrit] Adoption question: Adopt ID as new EC… Caron, Guy
- Re: [Ecrit] Adoption question: Adopt ID as new EC… Michael Smith
- Re: [Ecrit] Adoption question: Adopt ID as new EC… Allison Mankin
- Re: [Ecrit] Adoption question: Adopt ID as new EC… Randall Gellens
- Re: [Ecrit] Adoption question: Adopt ID as new EC… Az Mankin
- Re: [Ecrit] Adoption question: Adopt ID as new EC… Randall Gellens
- Re: [Ecrit] Adoption question: Adopt ID as new EC… Az Mankin