Re: [netmod] I-D Action: draft-chopps-netmod-geo-location-00.txt

Christian Hopps <chopps@chopps.org> Tue, 05 March 2019 19:02 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 E3FBA1200D8 for <netmod@ietfa.amsl.com>; Tue, 5 Mar 2019 11:02:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 A041xTxGTVLO for <netmod@ietfa.amsl.com>; Tue, 5 Mar 2019 11:02:24 -0800 (PST)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 5A34112D4EB for <netmod@ietf.org>; Tue, 5 Mar 2019 11:02:24 -0800 (PST)
Received: from tops.chopps.org (047-050-069-038.biz.spectrum.com [47.50.69.38]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPS id 89290604ED; Tue, 5 Mar 2019 14:02:23 -0500 (EST)
References: <sa67ede1jef.fsf@chopps.org> <CAEe_xxi4QeGbwQxXQFJE7EB9Cz1ee2ZhRLY9FOaNd3opw9M=Jw@mail.gmail.com> <sa65zsx4eay.fsf@chopps.org> <20190305.150501.1809357052440270699.mbj@tail-f.com> <CAEe_xxhp3Fqw7NrEr0ZfF+Y=SOHWS2XMz0Ha5if8QWmgH2v_jw@mail.gmail.com>
User-agent: mu4e 1.1.0; emacs 26.1
From: Christian Hopps <chopps@chopps.org>
To: William Lupton <wlupton@broadband-forum.org>
Cc: Martin Bjorklund <mbj@tail-f.com>, Christian Hopps <chopps@chopps.org>, netmod@ietf.org
In-reply-to: <CAEe_xxhp3Fqw7NrEr0ZfF+Y=SOHWS2XMz0Ha5if8QWmgH2v_jw@mail.gmail.com>
Date: Tue, 05 Mar 2019 14:02:22 -0500
Message-ID: <sa636o1401t.fsf@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/nrDBi2Uwkdiid6BOh8UmGVc9dI4>
Subject: Re: [netmod] I-D Action: draft-chopps-netmod-geo-location-00.txt
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: Tue, 05 Mar 2019 19:02:26 -0000

William Lupton <wlupton@broadband-forum.org> writes:

> On Tue, 5 Mar 2019 at 14:05, Martin Bjorklund <mbj@tail-f.com> wrote:
>
>> Christian Hopps <chopps@chopps.org> wrote:
>> >
>> > William Lupton <wlupton@broadband-forum.org> writes:
>> >
>> > >> The intent was "ascii-printable". Would be nice if there was an easier
>> > > way to specify this. :)
>> > >
>> > > Printable ASCII characters are ' ' (space) through '~' (tilde) so
>> > > naively [
>> > > -~] should work ... but perhaps that makes unacceptable assumptions
>> > > -about
>> > > the locale and/or character encoding? (Certainly it should be OK if we
>> > > can
>> > > assume UTF-8, because all printable ASCII characters retain their
>> > > ASCII
>> > > representations in UTF-8.)
>> >
>> > I think your suggestion is a good one!
>>
>> Not sure I get it.  What exactly is the suggestion?
>>
>
> Presumably the suggestion of using the [ -~] ("space through tilde")
> closure. I forgot to include other whitespace characters (CR, LF, FF) so if
> those are to be included it could be [\s!-~] ("whitespace plus exclamation
> mark through tilde").


I mis-poke earlier, it's all printable lowercase ASCII.

I'm going to use the pattern: '[ -@\[-\^_-~]*'

These 3 ranges seem to make pyang happy. I don't know why I need to break up the second range into 2 adjacent ranges like that to make pyang not complain, but complain it does if I just use: '[ -@\[-~]*'

Thanks,
Chris.