Re: [netmod] Benjamin Kaduk's Discuss on draft-ietf-netmod-geo-location-08: (with DISCUSS and COMMENT)

Christian Hopps <chopps@chopps.org> Wed, 26 May 2021 23:01 UTC

Return-Path: <chopps@chopps.org>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 349E73A0913; Wed, 26 May 2021 16:01:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 Q1IV0HZrwpjY; Wed, 26 May 2021 16:01:52 -0700 (PDT)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id E69A03A0AD4; Wed, 26 May 2021 16:01:51 -0700 (PDT)
Received: from ja.int.chopps.org.chopps.org (047-026-251-217.res.spectrum.com [47.26.251.217]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 31557803F2; Wed, 26 May 2021 23:01:51 +0000 (UTC)
References: <162146723152.27764.1299479086437558158@ietfa.amsl.com> <m2fsy9cdhl.fsf@ja.int.chopps.org>
User-agent: mu4e 1.5.13; emacs 27.2
From: Christian Hopps <chopps@chopps.org>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: The IESG <iesg@ietf.org>, draft-ietf-netmod-geo-location@ietf.org, netmod-chairs@ietf.org, netmod@ietf.org, kent+ietf@watsen.net
Date: Wed, 26 May 2021 18:56:29 -0400
In-reply-to: <m2fsy9cdhl.fsf@ja.int.chopps.org>
Message-ID: <m2cztdcd5t.fsf@ja.int.chopps.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/pj-Ql0lAbONPf6SlZDJH4goONso>
Subject: Re: [netmod] Benjamin Kaduk's Discuss on draft-ietf-netmod-geo-location-08: (with DISCUSS and COMMENT)
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 May 2021 23:01:57 -0000

Sorry missed a couple in previous reply.

Christian Hopps <chopps@chopps.org> writes:
>
> Benjamin Kaduk via Datatracker <noreply@ietf.org> writes:
>
>> Section 5.1.2
>>
>> The following subsection suggests that there is a "heading" field in the
>> W3C structure/API, but I don't see one listed in Figure 1.


Yes, there was even a blank line where it originally was, na errant D or something in vi. :)

I've put it back.

>> Section 6.1
>>
>> What are suitable references for the "me" and "mola-vik-1" geoedtic
>> systems?  I do not see how just the listed descriptions provide a "clear
>> definition" even for the two coordinate values latitude/longitude.

I've included a reference for 'me', and removed mola-vik-1 b/c it was simply too hard to find a good reference for it.

>> Section 7
>>
>> Thanks for using the template for security considerations for YANG
>> models!  I think that since some of the portions of the template do not
>> apply, they can safely be removed.  In particular, the "these are the
>> subtrees and data nodes and their sensitivity/vulnerability" lines can
>> go, and the clause about "can have a negative effect on network
>> operations" may be worth tweaking (network operations may not be the
>> most likely thing to be impacted).  I think it's also okay to drop the
>> paragraph/sentence about RPCs.

Updated.