Re: [Ecrit] Adoption question: Adopt ID as new ECRIT draft?

Michael Smith <msmith@equature.com> Sat, 17 October 2020 00:22 UTC

Return-Path: <msmith@equature.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 68ACD3A0A16 for <ecrit@ietfa.amsl.com>; Fri, 16 Oct 2020 17:22:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.798
X-Spam-Level:
X-Spam-Status: No, score=-1.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=equature-com.20150623.gappssmtp.com
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 L2Ybh0799eOW for <ecrit@ietfa.amsl.com>; Fri, 16 Oct 2020 17:22:01 -0700 (PDT)
Received: from mail-io1-xd41.google.com (mail-io1-xd41.google.com [IPv6:2607:f8b0:4864:20::d41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 193C33A0A13 for <ecrit@ietf.org>; Fri, 16 Oct 2020 17:22:00 -0700 (PDT)
Received: by mail-io1-xd41.google.com with SMTP id 67so6042652iob.8 for <ecrit@ietf.org>; Fri, 16 Oct 2020 17:22:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=equature-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:thread-index:content-language; bh=MfxDc/5OFDlvqH17JVuOFfpDxQt0oBP9Gn+aSQ8BCbA=; b=bxI3imbvE1qaHMIKre8FcdmxykTvaOzUC9FfvK3JvFebj2qY7VN800dymxem5okplD 9yswH+aUH4UrQxDsRdOGwyG2vx3SkrbwAWJcz3rf58L7k62a/M5WJkr+IoPwWdFJMQ2f Y1JkO4sTzrlCgsTtF6pAI0jDVk5WTWqUg14fRb0EcL9qsDgpHUzHQEj59Rg2D6K7QCb8 sqXgGufEdmeirQq/TR1OvvFFi0itK0i7CyL4N+0/9JN/t4qRhNymFNUx0yyu5tGIoYA+ Jfl8gKA+GRkG23ZMcaohDZZFZr20NTqcmVf9rJBYBC/y0CXv1WZNHfgCpV9tFoaWzSnt QWEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=MfxDc/5OFDlvqH17JVuOFfpDxQt0oBP9Gn+aSQ8BCbA=; b=IaGfXuGBSc70o7NyNCr8linmp2LhqydKmuNwbEVRe9P7ZXUgNgVQYQOOLZRiysi7+j sx9VXLlIdsxahGKxm1jR5xtD06rGXqW8LK0hqSjXAedNtASc4/Xjbjnw+Xt0L3Ocbo3b 9sv77KuwET+OqjBmZcLdK2rgU3xqoX67cI+B61KsPnDrY4u/K50soXh1fjP172SaNfAZ dxXblqQdBN1S7A6D2u1GFvecgA/6MORbmfqEy1FFJoL2PuXkLsbEtt5yUW12gV45HFXT pqUmPbdm6G/zDf5UUdjcuyr9HIy893xa8QRja/LQx4CTpPlSISlE5TG8O881aVtKdnpH PTTw==
X-Gm-Message-State: AOAM5305C8z58kOrhsfInRBpJVUsQDTDGyGvuSE6E9eABsgnZSyAYqYR Lx51/TbadXYASF+Gf31td0KFGw==
X-Google-Smtp-Source: ABdhPJyy8wVai08kcHoY4+Cjfzt3mBTvZzW7oUhlV0LEmvg+wkenSHLVpmXhjw69FIk5g2J7KDoMdA==
X-Received: by 2002:a6b:fc18:: with SMTP id r24mr4380844ioh.127.1602894120086; Fri, 16 Oct 2020 17:22:00 -0700 (PDT)
Received: from mlsprecision ([2605:a000:64c9:3e00:68e5:4863:b55c:cdab]) by smtp.gmail.com with ESMTPSA id d14sm3292937ilo.72.2020.10.16.17.21.58 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 Oct 2020 17:21:59 -0700 (PDT)
From: Michael Smith <msmith@equature.com>
To: "'Caron, Guy'" <g.caron@bell.ca>, 'Roger Marshall' <roger.marshall@comtechtel.com>, ecrit@ietf.org
Cc: 'Randall Gellens' <rg+ietf@coretechnologyconsulting.com>, 'Allison Mankin' <allison.mankin@gmail.com>, 'Barry Leiba' <barryleiba@gmail.com>
References: <BY5PR09MB50766EB51513D0AA71D442D8F4030@BY5PR09MB5076.namprd09.prod.outlook.com> <12208093b55c4221a0be913aae4e4d09@DG2MBX03-WYN.bell.corp.bce.ca>
In-Reply-To: <12208093b55c4221a0be913aae4e4d09@DG2MBX03-WYN.bell.corp.bce.ca>
Date: Fri, 16 Oct 2020 20:21:54 -0400
Message-ID: <00aa01d6a41b$85358dc0$8fa0a940$@equature.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00AB_01D6A3F9.FE254D50"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHdRN7icVkBdT1ZQ8nYmn+tPAWjegJCf1L5qXuYa/A=
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/ecrit/x6P2hTXfRTaCZz9uOZb-Sj7GLS0>
X-Mailman-Approved-At: Sat, 24 Oct 2020 09:06:00 -0700
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: Mon, 19 Oct 2020 14:47:43 -0000

I support the change to “Specification Required”, and also support Mr.
Caron’s addition of “non-duplicative” to the IANA Considerations section. 

 

Michael Smith

Chief Technologist, Equature/DSS Corp.

Ph: 606.877.2788 | Mobile: 606.231.0243

 

From: Ecrit <ecrit-bounces@ietf.org> On Behalf Of Caron, Guy
Sent: Friday, October 16, 2020 3:19 PM
To: Roger Marshall <roger.marshall@comtechtel.com>; 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>
Subject: Re: [Ecrit] Adoption question: Adopt ID as new ECRIT draft?

 

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 <mailto:ecrit-bounces@ietf.org> > De la
part de Roger Marshall
Envoyé : 16 octobre 2020 15:00
À : ecrit@ietf.org <mailto:ecrit@ietf.org> 
Cc : Randall Gellens <rg+ietf@coretechnologyconsulting.com
<mailto:rg+ietf@coretechnologyconsulting.com> >; Allison Mankin
(allison.mankin@gmail.com <mailto:allison.mankin@gmail.com> )
<allison.mankin@gmail.com <mailto:allison.mankin@gmail.com> >; Barry Leiba
<barryleiba@gmail.com <mailto: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://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%7Ca9a26
e696ae040c1bd801ca6cc677828%7C0%7C0%7C637384672503460823%7CUnknown%7CTWFpbGZ
sb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C10
00&sdata=j1BnBRIc46G%2FJjcQPYwG3ra%2FnzxWIVf1u8xid5q50%2F8%3D&reserved=0>
https://www.ietf.org/id/draft-ecrit-location-profile-registry-policy-01.txt


Registry url:
 
<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.iana.
org%2Fassignments%2Flost-location-profiles%2Flost-location-profiles.xhtml&da
ta=02%7C01%7Croger.marshall%40comtechtel.com%7Ca76728e45de74116e76308d861983
524%7Ca9a26e696ae040c1bd801ca6cc677828%7C0%7C1%7C637366653649324637&sdata=Ch
CvNsoEYcXConlY3oAyug9vE2uqPf6YVg%2Fn6NKUsZk%3D&reserved=0>
https://www.iana.org/assignments/lost-location-profiles/lost-location-profil
es.xhtml

 

-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.